 End of Course
Impetus for Change
NIEM as the information exchange framework of choice
-2-
National Information Exchange Model
Evolution of the NIEM Program
Since it’s inception in 2005, the US NIEM community has grown to include all
50 states,19 US Federal agencies, and continuously evolving domains.
Addition of 3
new domains
3.0 Release
2005: NIEM is
launched as a
result of
Executive Order
13388
2007: NIEM
2.0 released
2006: First
major
release
published
2012: Donna Roy
testimony and H.R.
3130/ H.R. 2146
enacted
Addition of 3
new domains;
totaling 14 +
domains
FUTURE
Simplified and
increased NIEM
adoption
NOW
THEN
2009:
NIEM 2.1
released
and
inaugural
NTE held
2010: NIEM
LinkedIn
group
reaches
1000
members
All 50 states and
18 federal
agencies
2011: H.R. 2883 committed to use
enacted and
trilateral MOU
signed at North
America Day
-3-
International
partners across
the EU, Canada,
etc.
Broader industry
engagement and
offerings
Implementation of
NIEM mobile
strategy and
increased cyber
security and
privacy
Reinhardt Video.
-4-
Understanding Each Other
I say “last name”, you say “surname”, but we are saying
the same thing
-5-
National Information Exchange Model
What is NIEM?
NIEM a community-driven, government-wide, standards-based approach to
exchanging information.
NIEM may sound complex, but the premise of it is simple. NIEM connects
communities of people who share a common need to exchange information in
order to advance their mission.
NIEM provides a Common Language
NIEM provides a Structured Approach
NIEM users define agreed upon terms, definitions,
and formats - independent of individual agency
systems.
NIEM provides a repeatable, reusable process for
business users to document information exchange
requirements in an implementation ready format.
-6-
How Does NIEM Work?
NIEM facilitates interoperability by ensuring that a basic set of information is
well understood by both the sender and receiver and carries the same
consistent meaning across various communities.
-7-
What is Interoperability?
Interoperability is the ability for many diverse systems to work together. By
increasing interoperability between mission areas and jurisdictions, government
can enhance its services across key functional areas such as law enforcement
and emergency response.
NIEM establishes interoperability through the use of:
Common Language and
Vocabulary
Agnostic Implementation
Eliminates confusion by providing
consistency of data definitions
between agencies
NIEM does not dictate how
agencies’ systems are
implemented, but enables these
systems to work together
-8-
The NIEM Framework
Much more than a data model, NIEM offers an active user community as well as a
technical and support framework.
Community
Support
Resources
Technical
Infrastructure
Governance
Processes
Tools for Development
and Discovery
Data Model
Mission-Oriented
Domains
Established
Training Program
XML Design Rules
Self-Managing
Domain Stewards
Implementation
Support
Development
Methodology
Repositories
Help Desk &
Knowledge Center
Consistently
Structured
Artifacts (IEPDs)
-9-
How Does NIEM Standardize Data Transfer?
NIEM intentionally does not address standardizing data inside legacy systems.
COMMONLY
FORMATTED
DATA
I N T E R FA C E
LEGACY
DATABASES
I N T E R FA C E
Scope-of-NIEM
LEGACY
DATABASES
Translation
NIEM serves as a translation layer (providing a common understanding)
between and across disparate systems.
- 10 -
What is an IEPD?
To begin exchanging information, information exchange partners must first
develop a data exchange.
In NIEM, a “data exchange” is also known as an Information Exchange
Package (IEP), a description of specific information exchanged between a
sender and a receiver.
The IEPD includes additional documentation, sample (XML)
instances, business rules, and more. An IEPD is the final
product of the NIEM exchange development process, also
known as the IEPD Lifecycle.
- 11 -
Overview of the IEPD Lifecycle
Repeatable, Reusable Process
(Exchange Specification Lifecycle)
- 12 -
Governance
NIEM is open source, but is structured and managed
- 13 -
National Information Exchange Model
NIEM is a User-Driven Model
The value of information-sharing and exchange efforts can best be achieved through the active
participation and collaboration of the many organizations involved in protecting and serving our
nation.
NIEM enables information sharing by defining the information that will be shared using XML-based
exchanges. These exchanges leverage a “Common Language” which works as a data dictionary
defining elements that are commonly used within a particular mission space.
Information relevant to most NIEM users is built into the NIEM Core
NIEM has multiple mission-based Domains each with its own Stewarding Owner (e.g., Cyber, Justice)
Domains are Community of Interests, groups of practitioners and technical representatives who have
a stake in NIEM information exchanges
The data elements within the domains are defined by the user communities
Identification of New Content
 Not all exchanges align completely to the existing NIEM Model. It is the unmapped content that
drives the domain development
 With all new domains, existing standards are reviewed to determine interoperability and
coordination with NIEM
- 14 -
NIEM Governance Processes
Three governance models structure and guide the NIEM Program:
1 – Operational Governance
How is the infrastructure of the program organized to support the continued
growth and scaling of the NIEM Program?
2 – Domain Independence
How are mission based domains organized to advance their priorities and
interests?
3 – Model Management
How does the model evolve and change over time in response to community
needs?
- 15 -
1 – Operational Governance
NIEM’s governing structure is comprised of Federal, State, Local and private
organizations.
NIEM is jointly managed at an executive level by the Department of Homeland
Security (DHS), Department of Justice (DOJ), and Department of Health and
Human Services (HHS).
ESC
Provides
executive
direction for the
NIEM program.
Executive Steering Council
NIEM PMO
Executive Director
Managing Director
NTAC
NIEM Technical
Architecture
Committee
Coordinates
Domains and
gathers new
model
requirements.
Execute technical
model
requirements.
- 16 -
Lead day to day
operations and
engage with
strategic
partners.
NBAC
NIEM Business
Architecture
Committee
2 – Domain Independence
Each Domain is governed by a Domain Steward who represents the community
on the NBAC.
Domain
Executive Steward
Justice
Global Justice (State & Local)
Screening
DHS Screening Coordination Office
 Immigration
Immigration
DHS/ICE & USCIS
 Intelligence
Chem/Bio/Rad/Nuc
DHS/DNDO
 Chem/Bio/Rad/Nuc
Maritime
DOD/DON/MDA
 Maritime
Cyber
DHS/NPPD/CS&C
 Cyber
Family Services
HHS/ACFS & DOJ
 Family Services
Emergency Management
DHS/FEMA, DHS/S&T (state & local)
 Emergency Management
Infrastructure Protection
DHS/NPPD
 Infrastructure Protection
International Trade
DHS/CBP
 International Trade
Biometrics
DHS/NPPD, DOJ/FBI, DOD, NIST
 Biometrics
Health
HHS/ONC & HHS/OCIO
 Government Resource
Management
Human Services
HHS/ACFS & HHS/ONC
Government Resource
Management
GSA
Agriculture
USDA
 Justice
 Screening
 Agriculture
- 17 -
3 – Model Management
What are
NIEM
Domains?
Common Language
(Data Model Lifecycle)
Built and governed by the business users at
Federal, State, Local, Tribal and Private
Sectors
- 18 -
NIEM domains
are communities
of interest, that
are formally
established, with
an executive
steward, to
officially manage
and govern a
portion of the
NIEM data
model
Program Planning and
Prioritization
- 19 -
National Information Exchange Model
FY13 NIEM Program Plan and Priorities
The FY13 NIEM Program Plan’s five major initiatives are supported by
several tasks listed below and explained in detail in the following slides.
NIEM 3.0 Release
3.0 Project Management  90 Day Activities  Communications  Content
Submission
Technology Priorities
and Management
NIEM Tools Strategy  NIEM UML Roll-Out  NIEM Technical Training 
Geospatial  Federal Digital Strategy, Big Data, and ACA  Privacy
Program Priorities and
Management
DoD Support  Review and Enhance the NIEM ConOps  Leadership Rotational
Program  Strategic Plan  Center of Excellence  NIEM Grants  NIEM
Challenges  Document Updates  Trademark & IP Rights  Help Desk 
Formalize Governance Rosters  Formalize Governance Charters
Domain Outreach and
Coordination
Emerging Domain Roundtables  Focused Workshops  Domain Maturity Metrics
 Collaboration Zone  Institutionalize Periodic State of Model Review 
Institutionalize Harmonization  Inactive Domain Outreach  Domain Messaging
Strategic
Communications
Bi-Annual Town Halls  Digital Communications  Community Champion Program
 We Are NIEM-ified Campaign  Communications Boot Camp  International
Engagement Support  Conferences and Speaking Engagements  Peer Review
Service  NIEM Classroom Training  Messaging  SalesForce Updates
- 20 -
NIEM Success Stories
- 21 -
National Information Exchange Model
NIEM Federal Adoption Success Story:
Core Biographic
Background:
The Core Biographic Person Identify Data Elements (CBPIDE) IEPD developed
established a standard set of core biographic data elements for reuse in all identity
oriented information exchanges across DHS.
Results:
CBPIDE has been approved by all DHS CIOs as the de facto
standard base for identity related information exchanges
Allows other organizations who are not directly involved in an
exchange to reuse the IEPD in order to “understand” the data
Serves as a valuable resource for other agencies outside of DHS
with the common need to exchange person-related data
As a result of reusing this IEPD, DHS realizes….
 Cost avoidance in the development of these exchanges
 Decreased risk associated with inconsistency in data definitions
- 22 -
NIEM State Adoption Success Stories
Background: Although all states have adopted NIEM through RISS (Regional Information
Sharing Standards), a couple of states have had broader adoption at other agencies. A sample
of these states are listed below.
New York:

Adopted NIEM through its New York Statewide Police Information Network (NYSPIN).

50,000 users in the law enforcement, judicial, and other state agencies.

Includes More than 20 IEPDs, provides data from many justice systems.
Texas:

Built the Texas Integrated Justice Information System (TIJIS) to enable jurisdictions to
effectively exchange information using NIEM.

Includes 28 IEPDs that were tested and published to both national and state repositories.

Implemented IEPS and stood up governance authorities to monitor the system.

Over 30 Texas agencies will use TIJIS.
All 50 States have agreed to use NIEM!
- 23 -
Justice Consortium for the Exchange of Criminal Justice
Information Technology (CONNECT)`
OBJECTIVE:
Applying NIEM to Interstate Sharing
CHALLENGE
Create investigative and tactical data portals that involve intrastate data sharing as
opposed to interstate sharing
RESULTS
SOLUTION
Development of a business
requirements document and the
ultimate creation of three NIEM 2.0
conformant IEPDs including:
• Develop business requirements for
sharing portal data between states
• Design system and development plan
• Develop several rapid prototype
components to provide proof of concept
• Develop NIEM 2.0-conformant IEPDs to
transmit data for sharing with other states
through CONNECT.
 A driver’s license query
 A driver’s license simple search and
return
 A detailed driver’s license return
- 24 -
New Jersey Data Exchange
OBJECTIVE:
NIEM-GJXDM for New Jersey Law Enforcement Information Sharing
CHALLENGE
New Jersey has more than 500 law enforcement agencies, which requires improved
information sharing methods among the many individual agencies.
RESULTS
SOLUTION
• Implementation of NJ-Dex is under
way
• CrimeTrack v1.0 will continue to
be used and CrimeTrack 2.0 will
be delivered in the near uture
• New version will have expanded
data exchange capabilities for
monitoring gangs
• Incorporate NIEM to
accommodate different industry
solution providers.
• Create an IEPD and a set of
Data sharing Extract Guidance
rules to facilitate exchanges
• Develop NJ-CrimeTrackv1.0
- 25 -
Massachusetts Gang Data Sharing
OBJECTIVE:
Unify statewide gang data sharing using NIEM
CHALLENGE
Massachusetts’ local, regional, and state law enforcement and public safety lacked an
effective mechanism to capture and share gang-related data statewide.
RESULTS
SOLUTION
• Created a streamlined gang data
management process
• Implemented a single, unified way
for agencies to share gang
intelligence information within
Massachusetts
• Implement a centralized webbased gang data management
application called MassGangs
• Use NIEM-conformant schema
and IEPD to exchange
information entered into
MassGangs
- 26 -
Support Infrastructure
- 27 -
National Information Exchange Model
Available NIEM Resources
Abundant tools are available for use
 IEPD Lifecycle / NEP artifact
templates
 Exchange Repositories
 Model Navigation Tools
 UML Profile
 NIEM Tools Catalog
Many resources are available to provide support and assistance
 NIEM website offers recorded
sessions and lecture material
 Free, modular, online NIEM
Training curriculum
 National Information Sharing
Standards (NISS) Knowledge
Base and Help desk
NIEM.gov contains a collection of essential NIEM documents
 Introduction to NIEM
 NIEM Naming and Design Rules
 Concept of Operations
 Many other documents
 User Guide
- 28 -
Training Curriculum
 Available online for free for anyone to take
NIEM
100
NIEM
101
NIEM
200
NIEM
300
Executive Managers
Program & Project Managers
Architects
Implementers
= Required
= Optional depending on role
- 29 -
NIEM
301
NIEM
302
NIEM
303
Q&A
Comments
- 30 -