1 / 24

Global Justice XML Data Model Users Conference June 10, 2005

Global Justice XML Data Model Users Conference June 10, 2005. James Feagans, DOJ and Michael Daconta, DHS. The Exchange Problem. XML exchanges are easy … too easy. SOA emergence will increase the # of XML exchanges. Without a framework for reuse, we will create XML Stovepipes .

coopermary
Download Presentation

Global Justice XML Data Model Users Conference June 10, 2005

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Global Justice XML Data Model Users Conference June 10, 2005 James Feagans, DOJ and Michael Daconta, DHS

  2. The Exchange Problem • XML exchanges are easy … too easy. • SOA emergence will increase the # of XML exchanges. • Without a framework for reuse, we will create XML Stovepipes. • NIEM is striving towards National information sharing • Extending “grass roots” “bottom-up” approach by Global Justice Community • Synergy with the Federal Enterprise Architecture Data Reference Model (Federal framework supporting a national approach)

  3. NIEM Program Vision Practitioners at all levels of government share accurate, complete, timely and appropriately secured information to enable informed decision-making to ensure homeland security and public safety.

  4. NIEM Program Goals • Overcome obstacles to information sharing between all forms of government • Improve Shared situational awareness and collaboration • Leverage technology/lessons learned/success • To improve internal processes • To improve external sharing and productivity • Support National information sharing programs • Implementation of National FEA Data Reference Model • Operational efficiency and effectiveness • Timely Detection, Prevention, and Response to Public Safety, Terrorism, Criminal Activity and other Emergencies

  5. NIEM Program Goal Drivers • From all Levels of Government, NIEM Leverages Re-Use of: • - Existing Standards • - Technology • - Existing Infrastructure • - Knowledge/Experience • - Organizational Interactions and Personal Relations (Culture) • (Established environment to capitalize on existing IT investments from all levels of National government) • NIEM Driver = COLLABORATION

  6. NIEM Program Principles TriggerEvent Organization A Message Organization B ResultingEvent • Trigger Event Begins with Real People • Built off existing infrastructure • Information exchange occurs at key decision points in the process • Technical solutions driven by functional requirements • Appropriate Security & Privacy Protections • Resulting event effects Real People

  7. Complex types 400 Simple types 150 Properties 2,209 Total Components 2,754 NIEM: Leveraging the Global Justice XML Data Model Content Release Version 3.0 Metadata 116 Misc 177 Org 94 Location 178 Activity 1216 Property 397 Person 543

  8. What Makes a Core Component? • The scope of data for inclusion into the NIEM will cover multiple business domains • Initial NIEM domain examples: • Law Enforcement • Emergency Management • Intelligence • Border Security • Courts • Probation • Parole • Corrections • Public Health • Fire • EMS • Emergency Management • Disaster Management

  9. Major Domains Homeland Security Public Safety CORE Law Enforcement,Intelligence, etc. Courts, Probation, Parole, Corrections, etc. Emergency Management,Border Security, etc. UNIVERSALCORE CORE Welfare,Juvenile Justice,Education, etc. CORE PublicHealth, etc. Secondary Domains etc. Other Domains The Concept of CORE

  10. Core Data Type Example

  11. National Information Exchange Model Concept Information ExchangePackage Descriptions (IEPDs) Virtual Object Reuse Repository – types, properties, business containers, msg constructs, service metadata, … AmberAlert<AmberAlert> Transport<Transport> HomelandSecurity Health IEPDTemplate EDXL_Msg Core Universal-Core EmergencyManagement Transportation Justice IEPDs Semanticallyconsistentacross alldomains New IEPDs Tools, methods, mapping, process, training,etc. New IEPDs New components CollaborativeTools (for distributedconsensus) GovernanceBodies ExchangeRequirements New reusablecomponents

  12. NIEM Example Exchange <amber-doc:AmberAlertDocument xmlns:amber-doc="http://www.it.ojp.gov/jxdm/3.0.2/amber-alert-document" xmlns:amber="http://www.it.ojp.gov/jxdm/3.0.2/amber-alert" xmlns:j="http://www.it.ojp.gov/jxdm/3.0.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > <j:DocumentDescriptiveMetadata> <j:DocumentID> <j:ID>AA123</j:ID> </j:DocumentID> </j:DocumentDescriptiveMetadata> <amber:AmberAlert> <amber:AmberAlertID></amber:AmberAlertID> <amber:AmberAlertTransmissionDate>2004-11-15</amber:AmberAlertTransmissionDate> <amber:AmberAlertTransmissionTime>09:15:30</amber:AmberAlertTransmissionTime> <amber:AmberAlertStatus>Active</amber:AmberAlertStatus> <j:CaveatText>Beware of general danger regarding this situation.</j:CaveatText> <amber:AmberAlertLanguageText>English</amber:AmberAlertLanguageText> <amber:AmberAlertContactInformation> <j:ContactEmailID> <j:ID>jsmith@mayberry.ci.us</j:ID> </j:ContactEmailID> <j:ContactWebsiteID> <j:ID>http://alerts.mayberry.ci.us</j:ID> </j:ContactWebsiteID>

  13. NIEM: Current Status (1) • Approved by the DOJ/DHS CIO’s February 2005 • DHS/DOJ Announced on February 28th, 2005 • DOJ/DHS CIO Memorandum of Agreement • Key points: • Rename GJDXM to signify broader scope • Add DHS/DOJ Content • Rework Model and Tools (support modularity) • Status: Signed • Regular National NIEM PMO Meetings • Identified Pilot Projects: • ATFE, DEA, FBI, USMS • HSARPA BTS Net, ICE • DHS State and Local Government Coordination and Preparedness Office (SLGCP) Innovative Technology Evaluation Pilots (ITEP) are participating. • Future Expansion of IC Involvement: • Intelligence Community Metadata Working Group (ICMWG) Partnership

  14. Current Status (2) • NIEM Public Information Website New Content • Cloned GJXDM, supporting tools and development web site. • Pilot Progress: • Completed Workshop on DHS HSARPA BTS Pilot April 11-13 Phoenix, AZ • Immigration and Customs Enforcement (ICE) mapping Enterprise Logical Data Model to NIEM. Fully participating in the effort. • Discussions with IAIP and FEMA • National Institute of Standards and Technology (NIST) Partnership

  15. Overall NIEM Development Guiding Principles Intelligent Capabilities/Services { • NIEM National Program Management Office • National Exchange Vision • National Governance Program • GJXDM/NIEM Integration • Expanded Tools and Capabilities • Virtual Help Desk & Training Program • Collaborative Technologies • Automated Harmonization • Information Exchange Package Automation Continuation 3 { • Initial NIEM Program Management Office • Implement Vetting Process • Implement Help Desk & Training Program • Incorporate Key Core Data • Virtual Input Into Model • Begin Automated Harmonization • Extend GJXDM Content and Architecture • Buy-in of Stakeholders Scaling 2 Level of Complexity { • Initial Governance as a Collaborative Partnership • Leverage XSTF Expertise • Build on Current Success of GJXDM (Reuse GJXDM Operational Domain) • Prove Concepts through Pilot Projects & Component Analysis • Minimize Risk of GJXDM Rework • Provide Benefit to GJXDM Users Proof of Concept 1 Time

  16. Implementation Approach Requirements from Global domain Global XSTF GJXDM (operational) 3.N 3.0.2 3.0.3 3.0.0 3.1.0 Feedback ATFE, ICEcontent other content, features, capabilities as appropriate U.S. Marshals, BTSService content initialize and ID Core NIEM Steering Committee Key Decision Points (KDP’s) NIEM (tactical) 0.N 1.0 0.2 0.1 Lessonslearned Newrequirements Technologyinsertion Requirements fromDHS + DoJ domain set-up experimental test bed NIEM (strategic) Explore good ideas: new metadata, scope/context, taxonomies/categories, federated NIEM repository, additional domains, Web Service interfaces, collaborative tools, OWL representation, …

  17. Key Objectives in Phases I/II Global XSTF Global JXDM (operational) 3.N 3.0.2 3.0.3 3.1.0 merge NIEM Steering Committee initialize NIEM Track I (tactical) 0.N 1.0 0.2 0.1 NIEM Track II (strategic) test bed Phase 1 Phase 2 Continuation Proof of Concept Scaling NIEM National Program Management Office National Exchange Vision National Governance Program GJXDM/NIEM Integration Expanded Tools and Capabilities Virtual Help Desk & Training Program Collaborative Technologies Automated Harmonization Information Exchange Package Automation Initial Governance as a Collaborative Partnership Leverage XSTF Expertise Reuse GJXDM Operational Domain Prove Concepts through Pilot Projects & Component Analysis Minimize Risk of GJXDM Rework Provide Benefit to GJXDM Users Initial NIEM Program Management Office Implement Vetting Process Implement Help Desk & Training Program Incorporate key core data Virtual Input Into Model Begin Automated Harmonization Extend GJXDM Content and Architecture Buy-in of Stakeholders

  18. Operational and Tactical Integration Continue with GJXDM as is Global XSTF GJXDM 3.N NIEM 1.0 U-Core Justice domain+ NIEM impact evaluate for: Core HomelandSecurity Justice NIEM Steering Committee NIEM (tactical) XSTF DMWG 1.0 Other NIEM National Governance

  19. Establish NIEM Operational Domain 1 2 5 4 NIEM PROJECT MANAGEMENT DEVELOPMENT AND OPERATION Perform NIEM Development 0 Review and Adopt NIEM Core Component Identify NIEM Content Maintain and Support NIEM Implement and Disseminate NIEM Content 3 • 1.1 Create NIEM Agreement • 1.2 Staff NIEM Project Team and Governance Structure • 1.3 Establish Initial NIEM Operational Environment • 2.1 Collect NIEM Components • 2.2 Validate NIEM Components • 2.3 Identify Existing Standard • 2.4 Develop NIEM Data Component Proposal • 3.1 Establish Review Project • 3.2 Coordinate and Review NIEM Component Draft Proposal • 3.3 Document and Approve NIEM Standard • 4.1 Plan and Control NIEM • 4.2 Maintain NIEM Content and Configuration • 4.3 Support NIEM Users • 5.1 Create XSD Subset • 5.2 Create & Catalog Information Exchange Package Description • 5.3 Disseminate NIEM Products

  20. 1 Expand the types of artifacts that can be stored, registered, and related within the repository. 3 Establish relationships between artifacts based on context, scope, and other attributes. 2 Expand the repository metadata to support the addition of new artifacts. Evolution of the Repository and Metadata AS-IS TO-BE Businesscontainers& msgconstructs OtherNamespaces ExternalNamespaces(code tables) IEPDs GJXDM GJXDM JIEMReferenceModel WantLists Extensions Service Oriented Architecture

  21. NIEM: Next Steps • Creating standard format for Component Mapping Template. • Project Tiger team (consisting of all pilot projects) was formed to develop and test component mapping template. • Product will be posted to the NIEM web site. • Create NIEM National Collaboration Tiger Teams (Development via Unified Consensus Building) • Project Tiger teams (consisting of all levels of government) formed to develop: • Interim and National Governance with Collaboration Tool Suite • CORE Components/Naming & Design Rules (NDR) • NIEM CONOPS DRAFT released for NIEM Committee Review.

  22. Component Mapping Template

  23. National Collaboration Success NIEM Development is Built on a Unified National Approach with “Joint Consensus” • NIEM PMO Comprised of National Representation • NIEM Facilitates Early Adopter Participation • NIEM Promotes “Participative approach vs Delegative approach” - National Joint Development - National Governance • Success = Subject Matter Experts (Business Driven) • Executing Collaboration at an “UNPRECIDENTED” National Level

  24. More Information at … NIEM Public Website: http://www.NIEM.gov Total # of hits in one month 57,558

More Related