October 12, 2005

1. October 12, 2005 Michael Daconta & James Feagans NIEM Project Manager

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. What is NIEM? • An interagency initiative to provide the foundation and building blocks for national-level interoperable information sharing and data exchange. • Initiated as a joint venture between the U.S. Department of Homeland Security (DHS) and the U.S. Department of Justice (DOJ) with outreach to other departments and agencies. • Formally announced at the Global Justice XML Data Model (Global JXDM) Executive Briefing on February 28, 2005. www.niem.gov

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

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

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

7. NIEM Transition NIEM Pilots Add Content Harmonize Re-engineer Technical Architecture NIEM GJXDM Broaden Governance Re-Work Process Expand Collaboration Increase User Base Review and Comment

8. NIEM Initial Business Domain Scope • 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. What Does NIEM Include? • Data Access and Exchange Framework • A Repository of … • Reusable components for constructing Information Exchange Package (IEP) specifications • Reusable IEP descriptions (IEPD’s) • Specifications for … • Building IEP’s from NIEM components • Reusing NIEM IEPD’s • Extending and adapting NIEM components and IEP’s for domain-specific applications • Processes for … • Submitting new content, change requests, and trouble reports • Collaborative shared governance • Support infrastructure • Support Tools

10. NIEM Technical Architecture • NIEM Model • Modular Component-Based Model • Reusable Core and Domain-specific Components: Building Blocks for Exchange Messages (Payloads) • Reusable Exchange Message Templates (IEPD’s) • NIEM Technical Framework • Technical Framework for building Reusable Components and Exchange Messages • Technical Specifications • Namespaces • Naming and Design Rules

11. NIEM Technical Architecture - Modular data model • Modular data model, derived from GJXDM • The three layers are: • Universal Core: entities and attributes common across most or all domains. • Common Core: entities and attributes common across two or more domains. • Domain-specific: entities and attributes specific to a single domain.

12. NIEM Model - Core and Domain-Specific Components Major Domains Homeland Law COMMON CORE Security Enforcement Border Security, Emergency Management, Courts, Probation, Intelligence, etc. Transportation Security, etc. Parole, Corrections, etc. UNIVERSAL COMMON CORE COMMON CORE CORE Juvenile Justice, Immigration Public Health, etc. Education, etc. Secondary etc. Domains Other Domains

13. BloodTypeCode BloodTypeCodeType Modular Data Model – “The Core” NIEM Core (a collection of namespaces) Core: Joint governance through NIEM Core Universal namespace Structuresnamespace The minimally supported set for all participating domains;universally understood; very stable; minimal or no subsetting Common namespace Requires central governance and reconciliation; but relatively stable Where the tiger teams operate • NIEM Participants: • Bring domain content to NIEM • Conform to NIEM NDR • Agree to NIEM governance policies and procedures • Participate in NIEM governance Intelligence namespace Justicenamespace EmergencyMgtnamespace Other namespace Domains Governed by XSTF-like committees that coordinate and cooperate with NIEM SC

14. NIEM Technical Architecture - Template Library • Exchange Package Template Library • Set of reusable message types and a message type hierarchy. • Message type hierarchy will begin with the most generic communications transactions (e.g., alert, request, response, update, etc.) and extend down to more specialized templates for specific transactions

15. NIEM Technical Architecture - Tools • Developing and adapting tools that will build a comprehensive NIEM Tool Suite and viewing tools that support collaborative development and deployment of data access and exchange capabilities. • Selected GJXDM tools will be adapted and extended for use with the NIEM. • NIEM open standards architecture will enable and facilitate the use of off-the-shelf commercial and shareware tools, and will encourage vender development of new tools to support the NIEM processes.

16. Exchange Development Process • Structured approach to defining the protocol and methodology that domain users and stakeholders will follow to participate in NIEM • Transforms business requirements into extensible markup language (XML) documents for use in data sharing architectures.

17. NIEM Overall 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

18. NIEM Development Approach Global XSTF Global JXDM (operational) 3.N 3.0.2 3.0.3 3.1.0 merge NIEM Governance initialize NIEM 0.N 1.0 0.2 0.1 Sustainable Scaleable Strong Foundation • Supporting National Governance Framework • with Collaborative Technologies • Re-usable Technical Implementation • Process (well defined & tested) • Information Exchange Package Automation • Performance Metrics • 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 • Rapid Incremental Development • Collaboration with Stakeholders Executing • NIEM Incremental Pilot Development • Built on Layers of Incremental Development • Success

19. 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 Interim NIEM Governance NIEM XSTF DMWG 1.0 Other Robust NIEM Governance

20. NIEM Governance – “The Challenge” Current Vertical “SILO” View (Federal) Federal CIO Council DOJ CIO DHS CIO DNI CIO OMB FEA PMO IC Information Sharing Working Group DHS Information Sharing Working Group DOJ Information Sharing Working Group State, Local, Tribal Advisory Council Organization CIO Chief Architects Forum (CAF) DOJ Chief Architect DHS Chief Architect IC Chief Architect Funding Programs DHS Community of Practice DOJ Community of Practice IC EA Community of Practice Guidance Organization Chief Architect

21. NIEM Governance Structure

22. NEIM Executive Steering Committee Other Partner CIO DOJ CIO DHS CIO NIEM Program Management Council NIEM Technical Committee DHS Chief Architect DOJ Chief Architect Chief Architect Communities of Practice DOJ Communities of Practice DHS Communities of Practice NIEM Governance “The Horizontal Glue”

23. NIEM Support Infrastructure • A Repository of … • Reusable components for constructing Information Exchange Package (IEP) specifications • Reusable IEP descriptions (IEPD’s) • NIEM IEP Library, … • Specifications and Guides for … • Building IEP’s from NIEM components • Reusing NIEM IEPD’s • Extending and adapting NIEM components and IEP’s for domain-specific applications, … • User Help … • Training, Workshops, Conferences • User/Discussion Groups, Helpdesk, … • Support Tools … • Configuration Management • IEP Development, …

24. Shaping NIEM 1.0 • Reviewing and providing Feedback on NIEM Deliverables • NIEM 0.n Releases • Technical Architecture • Content • Functional ConOps • Interim Governance Plan • NIEM NDR • Other Deliverables • NIEM Public Website: http://www.niem.gov • Establishing a NIEM Pilot Project • Developing and implementing NIEM exchange messages • Technology Evaluation • Adding Content • Participating on NIEM Workings, Committees, and Tiger Teams