1. 9/10/2015 1:46 AM National Information Exchange Model James Feagans, DOJ and Michael Daconta, DHS July 26, 2005 James Feagans, Department of Justice

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

4.  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

5.  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

6.  Trigger Event Begins with Real People  Built off existing infrastructure  Information exchange occurs at key decision points in the process  Quickly determine who makes the decisions allowing management (at all levels) to implement decisions  Technical solutions driven by functional requirements  Resulting event effects Real People NIEM Program Principles Organization A TriggerEvent Organization B ResultingEvent Message

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

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

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

10. Core Data Type Example

11. NIEM Example Exchange AA123 2004-11-15 09:15:30 Active Beware of general danger regarding this situation. English jsmith@mayberry.ci.us http://alerts.mayberry.ci.us

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

13. 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  Identify pilot projects and explore the expansion of IC involvement –DHS State and Local Government Coordination and Preparedness Office (SLGCP) Innovative Technology Evaluation Pilots (ITEP) are participating.  NASCIO promoted NIEM in recent Congressional call to action on Information Sharing

14. Current Status (2)  Developing Project Management Plan and National Joint Governance Structure  Adding new content to the public information NIEM website, 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. –Disaster Management Initiative adds NIEM to their Standards Process –Adding NIEM Content for FBI, DEA, ATFE, USMS, Case Management-Litigation, and EOUSA.  National Institute of Standards and Technology (NIST) Partnership

15. Overall NIEM Development Guiding Principles 3 2 1 Proof of Concept Continuation Scaling Level of Complexity Time  Initial Governance as a Collaborative Partnership  Leverage Expertise  Build on Current Success  Prove Concepts through Pilot Projects  Minimize Risk of Rework  Provide Benefit to Users {  Incremental Pilot Development with Modular Approach: Business Driven Harmonized/Integrated Governance and Technical Implementation Module “Fully Loaded Plug & Play” Reduce Transition Risk from Planning to Operational Produce Quantifiable Return on Investment for each milestone (pre-release) {  National Services Broker  National Consensus Framework  Supports Business Modularity  Flexible and Agile Information Exchange Service Capability across all Levels of Government  Performance Metrics { Intelligent Capabilities/ Services

16. Implementation Approach Lessons learned New requirements Governance/ Technology Module Insertion Governance/ Technology Module Insertion Feedback NIEM Steering Committee Global XSTF GJXDM (operational) NIEM (tactical) Requirements from Global domain Requirements from business domains ATFE, ICE content 3.0.0 3.0.2 3.1.0 3.0.3 3.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 0.2 0.N 1.0 NIEM (strategic) Key Decision Points (KDP’s) Business Process Modularity Business Process Modularity

17. NIEM Steering Committee Global XSTF Global JXDM (operational) NIEM Track I (tactical) 3.0.2 3.1.0 3.0.3 3.N 0.1 test bed 0.2 0.N 1.0 NIEM Track II (strategic) initialize merge Key Objectives in Phases I/II Initial Governance as a Collaborative Partnership Leverage Expertise Reuse GJXDM Operational Domain Prove Concepts through Pilot Projects Minimize Risk of GJXDM Rework Provide Benefit to GJXDM Users Phase 1Phase 2 Proof of Concept Scaling Continuation Collaboration with Stakeholders executing NIEM Incremental pilot development SOA modular approach. (participatory approach through “joint consensus building – SME’s across business domains) Build on layers of incremental development success National Consensus Framework (modularized National governance structure) Technical service oriented implementation approach Collaborative technologies Information Exchange Package Automation Performance metrics

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

19. NIEM Schedule (DRAFT)

20. NIEM Tiger Teams and Initial Messages  Governance: National Consensus Framework –Discussions with MIT and Harvard  Component Mapping Template (next slide) –Team testing template –Drafted recommendations/modifications to GTRI  Naming and Design Rules –Evaluating GJXDM NDR –Participating in Federal NDR  Concept of Operations –Establishing Team  Messaging Infrastructure and Facilitation –Establishing Team  Initial NIEM Messages –Terrorist Watchlist Person Data Exchange Standard 2.0 –Emergency Management Resource Message –Facilitation planning under way for other messages

21. Component Mapping Template

22. National Collaboration Success  NIEM PMO Comprised of National Representation  NIEM Facilitates Early Adopter Participation  NIEM Promotes “Participative approach vs Delegative approach” - National “Service Oriented” Modular Development - National Consensus Framework (Modular 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”

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