11/7/ :20 PM National Information Exchange Model 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.  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)

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. NIEM Program Vision

 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 NIEM Program Goals

 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 NIEM Program Goal Drivers

 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 NIEM Program Principles Organization A TriggerEvent Organization B ResultingEvent Message

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

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

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

Core Data Type Example

Tools, methods, mapping, process, training, etc. New IEPDs IEPDs New IEPDs New reusable components National Information Exchange Model Concept Justice Homeland Security Core Universal-Core Transportation Health AmberAlert Transport EDXL_Msg Virtual Object Reuse Repository – types, properties, business containers, msg constructs, service metadata, … Emergency Management IEPD Template Information Exchange Package Descriptions (IEPDs) Governance Bodies Exchange Requirements Collaborative Tools (for distributed consensus) Collaborative Tools (for distributed consensus) New components Semantically consistent across all domains

NIEM Example Exchange AA :15:30 Active Beware of general danger regarding this situation. English

NIEM: Current Status (1)  Approved by the DOJ/DHS CIO’s February 2005  DHS/DOJ Announced on February 28 th, 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

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 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

Overall NIEM Development Guiding Principles Proof of Concept Continuation Scaling Level of Complexity Time  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 {  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 {  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 { Intelligent Capabilities/ Services

Implementation Approach Lessons learned New requirements Technology insertion Feedback NIEM Steering Committee Global XSTF GJXDM (operational) NIEM (tactical) Requirements from Global domain Requirements from DHS + DoJ domain ATFE, ICE content N 0.1 initialize and ID Core set-up experimental test bed Explore good ideas: new metadata, scope/context, taxonomies/categories, federated NIEM repository, additional domains, Web Service interfaces, collaborative tools, OWL representation, … U.S. Marshals, BTS Service content other content, features, capabilities as appropriate N 1.0 NIEM (strategic) Key Decision Points (KDP’s)

NIEM Steering Committee Global XSTF Global JXDM (operational) NIEM Track I (tactical) N 0.1 test bed N 1.0 NIEM Track II (strategic) initialize merge Key Objectives in Phases I/II 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 Phase 1Phase 2 Proof of Concept Scaling Continuation 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 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

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

NIEM PROJECT MANAGEMENT DEVELOPMENT AND OPERATION  1.1 Create NIEM Agreement  1.2 Staff NIEM Project Team and Governance Structure  1.3 Establish Initial NIEM Operational Environment 1 Establish NIEM Operational Domain 0 Perform NIEM Development 2 Identify NIEM Content 3 Review and Adopt NIEM Core Component 4 Maintain and Support NIEM 5 Implement and Disseminate NIEM Content  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

Evolution of the Repository and Metadata GJXDM Other Namespaces WantLists JIEM Reference Model Extensions Business containers & msg constructs IEPDs GJXDM External Namespaces (code tables) AS-ISTO-BE Expand the types of artifacts that can be stored, registered, and related within the repository. 1 Expand the repository metadata to support the addition of new artifacts. 2 Establish relationships between artifacts based on context, scope, and other attributes. 3 Service Oriented Architecture

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.

Component Mapping Template

National Collaboration Success  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 NIEM Development is Built on a Unified National Approach with “Joint Consensus”

More Information at … NIEM Public Website: Total # of hits in one month 57,558