1 / 16

National Information Exchange Model (NIEM) Overview and Status January 31, 2007

National Information Exchange Model (NIEM) Overview and Status January 31, 2007. Kshemendra Paul NIEM Program Executive & Chief Enterprise Architect US DOJ (202) 616-9676 kshemendra.paul@usdoj.gov www.niem.gov. Agenda. Overview Scope & Fit in FEA NIEM (GJXDM) Delivered Results

glaufer
Download Presentation

National Information Exchange Model (NIEM) Overview and Status January 31, 2007

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. National Information Exchange Model (NIEM)Overview and StatusJanuary 31, 2007 Kshemendra Paul NIEM Program Executive & Chief Enterprise Architect US DOJ (202) 616-9676 kshemendra.paul@usdoj.gov www.niem.gov

  2. Agenda • Overview • Scope & Fit in FEA • NIEM (GJXDM) Delivered Results • Goals and Status • High Level Architecture • Value Proposition • Target Outcomes • Outcome / Governance Alignment • Deliverables • Questions & Discussion

  3. Overview • NIEM was launched on February 28, 2005, through a partnership agreement between the U.S. Department of Justice (DOJ) and the U.S. Department of Homeland Security (DHS) • NIEM brings Communities of Interest (COIs) together to: • Develop (and harmonize) reusable data exchange components • Leverage (NIEM and external) data exchange components to build information exchanges • Utilize cross COI governance to maximize inter-operability and reuse • Publish and discover reusable information exchanges • Provide standards, tools, methods, training, technical assistance and implementation support services for enterprise-wide information exchange

  4. Scope NIEM is Payload – Specifications for Data in Business Context

  5. Fit With Federal Enterprise Architecture • Business – standard information exchanges • Focus on reuse and modification • Authoritative vs. non-authoritative • Discover / register exchanges via repository • Data – common vocabulary for building information exchanges • Focus on reuse • Federated, hierarchical domain structure • Optional and over-inclusive augmentation • Performance – measure information sharing • Use/reuse of information exchanges • Use/reuse of data components (in/out of model) • Line of sight provides actionable feedback Information Exchange Architectural Profile Policy Performance Influenced By NIEM Business Focus of NIEM Scope of FEA Data Services Technology

  6. Goals and Status • Deliver NIEM • NIEM 1.0 (Delivered October 2006) • Currently working on NIEM Harmony Release (Target Beta April 2007) • Ramp-up governance, communications, and outreach activities (Underway) • Catalyze NIEM adoption and usage with stakeholders • Migration of GJXDM installed base (Underway) • DOJ, DHS EA – NIEM is the standard for information exchange (Done) • DOJ, DHS Grants – use of NIEM is a special condition (Done) • Enable delivery of Common Terrorism Information Sharing Standards (Target Phase 1 June 2007) • Deepen partnerships with communities of interest • Update and extend MOU (Underway) • NIEM in the Federal Transition Framework (Underway) • Become the standard, by choice, for government information exchange (Future)

  7. NIEM (GJXDM) – Delivered Results

  8. Federated Domain Architecture

  9. An Information Exchange Package (IEP) begins with a business need for a particular exchange. IEP Documentation (IEPD) describes how that exchange should be expressed using the NIEM. The IEPD is a key point for introducing new elements to NIEM and for reusing existing ones. An IEPD itself can also be reused in whole or in part to speed development and lower the cost of sharing information. Business Driven Information Exchanges

  10. Data Model Maturity Lifecycle

  11. Value Proposition Interlude – DHS (Any Federal Agency) Today DHS Conceptual/ Logical Data Model Maybe 10% Done Extremely expensive and timely to develop • Enterprise Architecture Status • Behind on DRM implementation • Lack Information Sharing Foundation • EA based SOA is ready for data exchange definition Legacy systems Is there one? Lots of activity for defining information in between components or individual systems or inside systems, but not being captured for reuse Currently in development, Services rolling out to help Working on info sharing to (DHS example: connect 40+ systems/data sources related to person screening ) DHS SOA Service Bus DHS Information Sharing Environment Legacy systems

  12. Value Proposition – Accelerates Mission Driven Information Sharing DHS Conceptual/ Logical Data Model Separate enclaves & registries for SBU vs. Classified Used to help build Data Model based on Interface needs, not whole system 1) SAVE $$$$ maturing DRM NIEM Model Used to create DHS Registry of Information Exchanges Information Exchange Package Descriptions (IEPDs) Are Registered in 3.Faster and less costly connections between legacy systems by defining common exchanges to be used within common services structure Legacy systems 2. Builds foundation for Information Sharing Environment, providing a place to capture current activity Are used to create Interfaces for information sharing DHS Information Sharing Environment DHS SOA Service Bus Legacy systems

  13. Target Outcomes • Priority One – Enable Fusion Center Inter-Operability via CTISS • Crosses DNI, DHS, DOJ, and Local/State/Tribal Public Safety • Deliverable is specific CTISS exchange standards • Priority Two (Shorter Term) – Establish Standards Adoption Process • IC, DHS, and DOJ via Enterprise Architecture activities • State & Local Fusion Centers via special condition language • Deliverable is clear, consistent, & detailed processes and guidance for implementation • Priority Two (Longer Term) – Domain (Signatory) Specific Exchanges • Global – Rap Sheet, Critical Infrastructure, CANDLE w/Photo (Real ID) • DOJ/DHS/IC – EA-based adoption, prioritization, creation, & implementation • Executive Steering Committee & Phase 2 ISE Implementation Plan Mandate • Driving mission and program alignment (target outcomes & resource allocation) • Expansion to other domains such Defense, Transportation, & Environmental Protection

  14. Governance/Outcome Alignment Governance Style Outcome Areas Governance Bodies CTISS NIEM National Priority Exchange Panel (NPEP) working under ISC Domain Specific Exchanges Domain-specific activity in consultation with NIEM NPEP Outcomes Focused Mandate Standards Adoption Process NIEM Policy Advisory Panel base lining current processes Community Consensus NIEM Infrastructure NIEM Committees with deadlines and escalation process to insure timely decisions

  15. Deliverables • Documentation • Introduction to NIEM • Concept of Operations • User Guide • NIEM Naming and Design Rules • Standards • NEIM 1.0 / Harmony • Reference Exchanges • Training and Technical • NIEM website • Training materials • Help desk • Tools • Component Mapping Template • Schema Subset Generation Tool • Graphical Browser • Exchange Repository • Governance and Processes • The structure to manage and maintain • NIEM and the processes and procedures • behind its operations.

  16. Questions and Discussion • For more information visit the NIEM web site (http://www.niem.gov) • Contact NIEM by email at information@niem.gov

More Related