NIEM Overview.ppt - EAPMO Status _ Plans by wulinqing


									National Information            Jeremy Warren
Exchange Model (NIEM)   Deputy Chief Technology Officer
                             U.S. Dept. of Justice
October 24, 2006
Web Site ( Activity

Web site activity for the period from June 1, 2006 to August 31, 2006

                                                               Average hits / day
                                                               • 1,842 pre-beta
                                                               • 10,923 currently

                                                               Average downloads / day
                                                               • 11 pre-beta
                                                               • ~100 currently

What is NIEM?

• 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

   – Publish and discover reusable information exchanges

   – Provide public domain standards and technical tools to support the above

   – Provide training, technical assistance and implementation support services
     for enterprise-wide information exchange
NIEM Use Cases

    • To effectively exchange information, there must be
      a common semantic understanding of data among
      participants, and the data must be formatted in a
      consistent manner.
    • NIEM provides reusable components and IEPDs
      for exchanges
       • Between NIEM domains (inter-domain).
       • Within NIEM domains (intra-domain)
         (where multiple sub communities exist
         within a single NIEM domain, e.g. justice).

Built on the Global JXDM

• NIEM is deeply rooted in the GJXDM and Global Justice Community,
  and committed to maintaining and growing that relationship

• The Global Justice XML Data Model (Global JXDM) has
   – A robust, mature framework that is rich, flexible, and extensible
   – An effective governance mechanism
   – Widespread recognition and use, especially among state and local agencies

• NIEM builds on the demonstrated success of the GJXDM
   – NIEM 0.1 is based upon GJXDM 3.0.3
   – The Global JXDM will form the justice domain of NIEM (the jxdm
   – The GXSTF will continue to represent the Global JXDM within NIEM

Built on the Global JXDM, continued

  NIEM = GJXDM + Expanded Scope + Lessons Learned

  • Incremental changes to GJXDM to address specific issues and
    expanded scope
  • A few examples:
     – Expanded Domains (Intel, International Trade, Emergency Mgt,
       Infrastructure Protection, etc.)
     – Better Modularity
     – Improve Reusability - Leveraging work of others – Discovery of IEPDs
       and components
     – Capturing Business Context
     – Incorporating feedback into the model - Model Refinement through use
     – Support for components from external standards
     – IEPD consistency
NIEM Federated Domain Architecture

Data component - fundamental building
block of NIEM. Data components are
either Universal, Common, or Domain-

Universal components - data
components commonly understood and
reused among all domains; subject to
NIEM governance.

Common components - data
components understood and potentially
reused between two or more domains;
subject to NIEM governance.

Domain-Specific - components
managed by a specific Community of
Interest (may be reused with COI,
available for reuse by others).

NIEM Domains

           NIEM                  NIEM Domains:
                                 • Represent a subset of components expected
         NIEM Core                  to be used in NIEM for inter-domain,
 Universal         Structures       intra-domain exchanges or both

                                 • Are governed by a cohesive group of data
         Common                    stewards who are domain experts, have some
                                   level of authority over the domain and
                                   harmonize semantic conflicts
  J                     Intel
         Im                      • Govern their own content under guidelines
                   Sc              established by NIEM PMO
 IT IP        EM            ZN
      NIEM Domains               • Are wrapped in a namespace to facilitate
                                   governance and to serve as the primary

External Domains

             NIEM                      External Domains:
                                       • Represent a data standardization initiative
         NIEM Core                       outside of NIEM

  Universal        Structures          • Do NOT fall under NIEM NDR or governance

         Common                        • Can be leveraged to create a new NIEM domain

                                       • May participate in NIEM in the following ways:
                                            • Total migration (the special case of GJXDM)
   J                    Intel               • Wrap / refer (how an external standard is used)
                   Sc                       • Translate / map (NIEM set maps to original
 IT IP        EM            ZN                data set)
       NIEM Domains                         • Extract / use (translate and move original
                                              data set)
                                            • Adopt (becomes a candidate for a new
                                              NIEM domain)
  External                  External
  Domain                    Domain

IEPD Development vs the Model

      IEPD Development                                                 The Model –
      • National priorities (e.g. NDEx, TWPDES)                       NIEM reusable
      • Authoritative sources (e.g. Rap Sheet)
      • Local requirements                                             components
                            0 Scenarios,
                          BRM taxonomies

                                               1 Info exchg

     reuse /             5 Publish +
                         implement         IEPD
     revise                                               2 Map +
                                            Life           model        reuse

                add /                      Cycle                     add /
               replace                                              replace
                             4 Assemble             3 Build +
                            to IEPD spec            validate

     IEPD Library

IEPDs and Data Components

            External 0                                      External 1
                4                                               6
                                    4     5      6

                                                     External domains or standards
External domains or standards
           External 3               2            3          External 2


                                2                3        1, 5 – create
                                        NIEM              2, 4 – wrap / refer
                                                          3 – translate / map
                                                          6 – adopt

Organization Model: External View

IEPD Lifecycle

Executive orders,                            Specific information exchange,
mission statements,                               high-level business
business requirements,                        requirements, existing IEPDs
                            0 Scenarios,
business context,
                           BRM Taxonomy
policies/procedures                                                                NIEM

                 IEPD for                          1 Info exchange       Data requirements,
               reuse library                        requirements         business context,
                                                                         exchange model

                         5 Publish +                                                  Submission
                                                                                      of candidate
                                       NIEM IEPD                   2 Map +

                 Complete IEPD
                                       Life Cycle                   model
                                              Existing                                   context
                                           IEPD artifacts

                             4 Assemble                     3 Build +         Gap analysis, specs
                            to IEPD spec                    validate          for new components
       IEPD artifacts
      to share/reuse,
        metadata for
         discovery                  Valid IEPD schemas, example
                                 instances, documentation, metadata                                  13
IEPD Life Cycle Feeds the Data Model
Maturity Life Cycle

  Top          Bottom
 down            up         IEPDs

    0 Scenarios,                                                         NBAC / NTAC:
  BRM taxonomies                                                         vet, harmonize,

                  1 Info exchg
                                                                        NIEM Governance
                                                   Staging Area
 5 Publish +
               NIEM IEPD          2 Map +
 implement     Life Cycle          model
                                                   Early Awareness
                                                    & coordination
       4 Assemble            3 Build +
      to IEPD spec           validate

          New component candidates
                                            Groups with common data interests
             & business context


• Documentation
    • Introduction to NIEM
    • Concept of Operations
    • User Guide
    • NIEM Naming and Design Rules

• Standards
     • NIEM 1.0
     • IEPD requirements specs

• Training and Technical
     • NIEM website
     • Training materials
     • Help desk

• Tools
    • Component Mapping Template
    • Schema Subset Generation Tool
    • Graphical Browser
    • IEPD Repository

• Governance and Processes
    • The structure to manage and maintain
       NIEM and the processes and procedures
       behind its operations.
NIEM Pilots Based on Business Scenarios

•   Content Contributor Pilots                  •   Early Adopter Pilots
     – DHS Immigration and Customs                   – Intelligence Community Watchlist
       Enforcement                                     Message Pilot
         • ICE Enterprise Data Model mapping
                                                         • Terrorist Watchlist Person Data
           to NIEM
                                                           Exchange Standard (TWPDES)
     – DHS Customs and Border Protection                   Working group, OCIO Watchlist and
         • United Nations Trade Data Elements              NCTC actively participating
           Directory (UNTDED)
                                                     – National Capital Region Data
     – DHS Emergency Management                        Exchange Hub Pilot
         • Adding Disaster Management,
           Resource Message contents                     • Virginia, DC, and Maryland
                                                           representatives leading the pilot
     – Geospatial Community of Interest
                                                         • In partnership with the Disaster
         • Adding Geospatial contents
                                                           Management eGov initiative
     – DHS Team 5 Pilot                                  • Initial target: First responder
         • People Screening data elements                  resource request messages
           from five DHS components
     – DHS Infrastructure Protection                 – OCIO ITEP Pilots (kickoff in
       (NADB)                                          August 2006)
         • Adding infrastructure protection              • Data model validation using semantic
           contents                                        web techniques
                                                         • JIEM Tool for business stakeholder

• NIEM 1.0 Release Candidate 2 later this week

• Scaling up and implementing Governance structures

• Pilot projects underway

• GJXDM convergence plan promulgated

• Cross Federal alignment discussions underway

Web site –

Training and Technical


Tools: Graphical Browser

Tools: Schema Subset Generation Tool

Tools: IEPD Tool

Tools: IEPD Tool

Lessons Learned

•   GJXDM Usage Base and Governance Structure Enables NIEM

•   Governance and policy are the critical path, not technology
     –   They are both also really hard
     –   Process cannot replace relationships and trust
     –   Balance between: inside / outside the beltway; architectural / operational
     –   We are making progress – lots more to do

•   State and local involvement as first rank partners
     – As practitioners, stakeholders, thought leaders

•   Role of industry, academic partners

•   Success = adoption and use
     – Never forget that the best way to get this is the simplest – listen!


• For more information visit the NIEM web site (

• Contact NIEM by email at

• Questions and Discussion


To top