National Information Exchange Model (NIEM)

Overview and StatusJanuary 31, 2007

Kshemendra Paul

NIEM Program Executive &Chief Enterprise Architect

US DOJ

(202) 616-9676kshemendra.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

Policy

Performance

Business

Data

Services

Technology

Scopeof

FEA

Information ExchangeArchitectural Profile

• 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

Focus ofNIEM

InfluencedBy NIEM

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

Aspect February 2007

Increased Cross-Domain & Cross-Organization Inter-Operability

• ~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

•DoD integrates public safety & law enforcement data for US-based force protection 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 Improvement

• ~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 & Avoidance

• Single DHS people screening exchange standards are the basis for inter-operability and build once use many reuse between US Visit, CBP, Immigration, ICE, 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 development

8

Federated Domain Architecture

9

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

10

Data Model Maturity Lifecycle

11

Value Proposition Interlude – DHS (Any Federal Agency) Today

Currently in development, Services rolling

out to help

Legacy systems

Legacy systems

DHSConceptual/

Logical Data Model

DHS SOA Service

Bus

DHS Information

Sharing Environment

Maybe 10% Done

Extremely expensive and timely to develop

Is there one? Lots of activity for defining information in between

components or individual systems or inside systems, but not being

captured for reuse

Working on info sharing to (DHS

example: connect 40+ systems/data

sources related to person

screening )

Enterprise Architecture Status

• Behind on DRM implementation

• Lack Information Sharing Foundation

• EA based SOA is ready for data exchange definition

12

Value Proposition – Accelerates Mission Driven Information Sharing

NIEM Model

DHS Registry of Information Exchanges

Information Exchange Package

Descriptions (IEPDs)

Used to create

Are Registered

in

Are used to create Interfaces for

information sharing

Legacy systems

Legacy systems

Used to help buildData Model based on Interface needs, not

whole system

1) SAVE $$$$ maturing DRM

DHS Conceptual/

Logical Data Model

DHS SOA Service

Bus

2. Builds foundation for Information Sharing Environment, providing a place to capture current activity

DHS Information

Sharing Environment

3.Faster and less costly connections between legacy systems by defining common exchanges to be used within common services structure

Separate enclaves & registries for SBU vs. Classified

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

NIEM Infrastructure

Standards AdoptionProcess

CTISS

OutcomeAreas

GovernanceBodies

NIEM National Priority Exchange Panel (NPEP) working under ISC

Domain-specific activity in consultation with NIEM NPEP

NIEM Committees with deadlines and escalation process to insure

timely decisions

Domain SpecificExchanges

NIEM Policy Advisory Panel base lining current processes

OutcomesFocusedMandate

GovernanceStyle

Community Consensus

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