EAPMO Status Plans by jennyyingdi


									                            Kshemendra Paul

National Information    NIEM Program Executive &
Exchange Model (NIEM)   Chief Enterprise Architect
                                 US DOJ
Overview and Status
                              (202) 616-9676
January 31, 2007        kshemendra.paul@usdoj.gov


•   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


• 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


  NIEM is Payload – Specifications for Data in Business Context
Fit With Federal Enterprise Architecture

    Information Exchange           •   Business – standard information exchanges
     Architectural Profile              – Focus on reuse and modification
                                        – Authoritative vs. non-authoritative
                                        – Discover / register exchanges via repository

                     Performance   •   Data – common vocabulary for building
         By NIEM
                                       information exchanges
                      Business          – Focus on reuse
        Focus of                        – Federated, hierarchical domain structure
Scope    NIEM
                        Data            – Optional and over-inclusive augmentation

                      Services     •   Performance – measure information sharing
                                        – Use/reuse of information exchanges
                     Technology         – Use/reuse of data components (in/out of model)
                                        – Line of sight provides actionable feedback

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)
NIEM (GJXDM) – Delivered Results

         Aspect                                       February 2007
 Increased Cross-      • ~1M Law Enforcement Officers in the US at the Local, State, Tribal, and Federal
                       levels (including DOD, DHS, DOJ, DOI, Treasury) across 18K plus distinct entities
 Domain & Cross-
 Organization Inter-   •DoD integrates public safety & law enforcement data for US-based force protection
 Operability           supported by NCIS – One DOJ inter-operation

                       •National Association of State CIOs has endorsed adoption and use of NIEM based
                       on GJXDM track record and migration decision.

 Enabled Mission       • ~90M inter-state transactions a month across ~20 transaction types; FBI CJIS
                       committed to NIEM in current development activity
                       •ARJIS (San Diego) was able to correlate 700K license plates from border crossing
                       with outstanding warrants over a four day period to generate ~225 felony leads

                       • TSC / NCTC Terrorist Screening (TWPDES); Amber Alerts; National Sex Offender
                       Registry; Cross-Jurisdiction Drivers’ License, Rap Sheets, Wants and Warrants, and
                       Vehicle Registration; State and Federal Court Filings

 Cost Savings &        • Single DHS people screening exchange standards are the basis for inter-
                       operability and build once use many reuse between US Visit, CBP, Immigration, ICE,
 Avoidance             State, FBI, and other stakeholders

                       • New York has built a family of ~150 NIEM 1.0 IEPDs and reporting high levels of
                       data component reuse and application code simplification.

                       •Multiple reports of million dollar plus savings and vendor discounts on interface
Federated Domain Architecture

Business Driven Information Exchanges

•   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
Data Model Maturity Lifecycle

Value Proposition Interlude – DHS (Any
Federal Agency) Today

   DHS             Maybe 10% Done
                                                    Enterprise Architecture Status
Conceptual/      Extremely expensive
  Logical        and timely to develop              •       Behind on DRM implementation
Data Model
                                                    •       Lack Information Sharing
                                                    •       EA based SOA is ready for data
                                                            exchange definition

                                                                            Is there one? Lots of activity for
                                           Currently in
Legacy                                    development,                      defining information in between
              Working on info                                             components or individual systems or
systems       sharing to (DHS
                                         Services rolling
                                                                             inside systems, but not being
                                           out to help
                  example:                                                         captured for reuse
                connect 40+
               systems/data                                                          DHS
              sources related             DHS SOA
Legacy            to person                Service
                 screening )                                                       Sharing
systems                                      Bus
Value Proposition – Accelerates Mission
Driven Information Sharing

   DHS             Used to help build                                              Separate enclaves &
Conceptual/       Data Model based on

                  Interface needs, not            NIEM                             registries for SBU vs.
                     whole system
Data Model                                        Model                            Classified
                     1) SAVE $$$$
                     maturing DRM

                                                     Used to create

                                                                                    Registry of
                                                Package                            Information
                                           Descriptions (IEPDs)
              3.Faster and less costly
              connections between
              legacy systems by defining                                                      2. Builds foundation for
Legacy        common exchanges to be
                                                                                              Information Sharing
              used within common                                                              Environment, providing a
systems       services structure
                                         used to create
                                          Interfaces for                                      place to capture current
                                         information sharing                                  activity

                                         DHS SOA                                          Information
Legacy                                    Service                                           Sharing
systems                                     Bus                                           Environment

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

Governance/Outcome Alignment

Governance       Outcome                      Governance
   Style          Areas                         Bodies

                                      NIEM National Priority Exchange
                   CTISS              Panel (NPEP) working under ISC

               Domain Specific          Domain-specific activity in
                 Exchanges             consultation with NIEM NPEP

             Standards Adoption    NIEM Policy Advisory Panel base lining
                  Process                    current processes

 Community                            NIEM Committees with deadlines
 Consensus   NIEM Infrastructure      and escalation process to insure
                                             timely decisions


• 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.
Questions and Discussion

• For more information visit the NIEM web site (http://www.niem.gov)

• Contact NIEM by email at information@niem.gov


To top