04/19/23 13:23 04/19/23 13:23

National Information Exchange Model

James Feagans, DOJ and Michael Daconta, DHS

July 26, 2005

James Feagans, Department of Justice

The Exchange Problem

XML exchanges are easy … too easy.– SOA emergence will increase the # of XML exchanges.– Without a framework for reuse, we will create XML Stovepipes.

NIEM is striving towards National information sharing– Extending “grass roots” “bottom-up” approach by Global Justice Community– Synergy with the Federal Enterprise Architecture Data Reference Model

(Federal framework supporting a national approach)

Point-to-Point Mapping --- n(n-1)

Canonical Standard Approach --- 2n

CanonicalStandard

National Information Exchange Model

Point-to-Point Mapping --- n(n-1)

Canonical Standard Approach --- 2n

CanonicalStandard

National Information Exchange Model

Practitioners at all levels of government share accurate, complete, timely and appropriately secured information to enable informed decision-making to ensure homeland security and public safety.

NIEM Program Vision

Overcome obstacles to information sharing between all forms of government

Improve Shared situational awareness and collaboration

Leverage technology/lessons learned/success

– To improve internal processes

– To improve external sharing and productivity

– Support National information sharing programs

– Implementation of National FEA Data Reference Model

Operational efficiency and effectiveness Timely Detection, Prevention, and Response to

Public Safety, Terrorism, Criminal Activity and other Emergencies

NIEM Program Goals

From all Levels of Government, NIEM Leverages Re-Use of:

- Existing Standards

- Technology

- Existing Infrastructure

- Knowledge/Experience

- Organizational Interactions and Personal Relations (Culture)

(Established environment to capitalize on existing IT investments from all levels of National

government)

NIEM Driver = COLLABORATION

NIEM Program Goal DriversNIEM Program Goal Drivers

Trigger Event Begins with Real People

Built off existing infrastructure

Information exchange occurs at key decision points in the process

Quickly determine who makes the decisions allowing management (at all levels) to implement decisions

Technical solutions driven by functional requirements

Resulting event effects Real People

NIEM Program Principles

Organization A

TriggerEvent

Organization B

ResultingEvent

Message

Activity1216

Person543

Property397

Location 178

Metadata116

Misc177Org 94

Complex types 400Simple types 150Properties 2,209Total Components 2,754

NIEM: Leveraging the Global Justice XML Data Model Content

Release Version 3.0

The Concept of Core

CORELaw

Enforcement,Intelligence, etc.

COREPublic

Health, etc.

COREWelfare,

Juvenile Justice,Education, etc.

Emergency Management,Border Security, etc.

Courts, Probation, Parole, Corrections, etc.

etc.

UNIVERSALCORE

Homeland Security

PublicSafety

Major Domains

Secondary Domains

Other Domains

What Makes a Core Component?

The scope of data for inclusion into the NIEM will cover multiple business domains

– Initial NIEM domain examples:

• Law Enforcement• Emergency Management• Intelligence• Border Security• Courts• Probation• Parole• Corrections• Public Health• Fire• EMS• Emergency Management• Disaster Management

Core Data Type Example

PERSON

Person Id

Person NamePerson AddressPerson Date Of BirthPerson GenderPerson EthnicityPerson Race

TWPDES-PERSON

Person Id (FK)

Person EducationPerson Physical DescriptionPerson KinshipPerson MedicalPerson SkillPerson Agency Interest

DOJ-PERSON

Person Id (FK)

Person Driving IncidentPerson Drivers LicensePerson AcquaintancePerson Day ContactPerson Evening ContactPerson Adopted ChildPerson Adoptive ParentPerson Gang AffiliationPerson Affiliation OrganizationPerson ChargePerson Detained Location

ICE-PERSON

Person Id (FK)

Alien NumberAlert CodePhoto CodeFinger PrintEntry DateFamily HealthFamily DetailEmployment Authorization

DOD-PERSON

Person Id (FK)

Person Eye ColorPerson Usual WeightPerson Hair ColorPerson Birth TimePerson Total Dependent QuantityPerson Adult Dependent Quantity

IAIP-PERSON

Person Id (FK)

Person Personal AttributesPerson Physical DescriptorsPerson EmploymentPerson CapabilitiesPerson AffiliationsPerson Possessions

NIEM Example Exchange

<amber-doc:AmberAlertDocument xmlns:amber-doc="http://www.it.ojp.gov/jxdm/3.0.2/amber-alert-document" xmlns:amber="http://www.it.ojp.gov/jxdm/3.0.2/amber-alert" xmlns:j="http://www.it.ojp.gov/jxdm/3.0.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > <j:DocumentDescriptiveMetadata> <j:DocumentID>  <j:ID>AA123</j:ID>   </j:DocumentID>  </j:DocumentDescriptiveMetadata> <amber:AmberAlert> <amber:AmberAlertID> </amber:AmberAlertID>  <amber:AmberAlertTransmissionDate>2004-11-15</amber:AmberAlertTransmissionDate>   <amber:AmberAlertTransmissionTime>09:15:30</amber:AmberAlertTransmissionTime>   <amber:AmberAlertStatus>Active</amber:AmberAlertStatus>   <j:CaveatText>Beware of general danger regarding this situation.</j:CaveatText>   <amber:AmberAlertLanguageText>English</amber:AmberAlertLanguageText> <amber:AmberAlertContactInformation> <j:ContactEmailID>  <j:ID>jsmith@mayberry.ci.us</j:ID>   </j:ContactEmailID> <j:ContactWebsiteID>  <j:ID>http://alerts.mayberry.ci.us</j:ID>   </j:ContactWebsiteID>

Tools, methods, mapping, process, training,

etc.

New IEPDs

IEP

Ds

New IEPDs

New reusablecomponents

National Information Exchange Model Concept

Justice

HomelandSecurity

CoreUniversal-Core

Transportation

Health

AmberAlert<AmberAlert>

AmberAlert<AmberAlert>

Transport<Transport>

Transport<Transport>

EDXL_MsgEDXL_Msg

Virtual Object Reuse Repository – types, properties, business containers,

msg constructs, service metadata, …

EmergencyManagement

IEPDTemplate

IEPDTemplate

Information ExchangePackage Descriptions (IEPDs)

GovernanceBodies

ExchangeRequirements

CollaborativeTools

(for distributedconsensus)

CollaborativeTools

(for distributedconsensus)

New components

Semanticallyconsistentacross alldomains

NIEM: Current Status (1)

Approved by the DOJ/DHS CIO’s February 2005

DHS/DOJ Announced on February 28th, 2005

DOJ/DHS CIO Memorandum of Agreement– Key points:

• Rename GJDXM to signify broader scope• Add DHS/DOJ Content• Rework Model and Tools (support modularity)

– Status: Signed

Regular National NIEM PMO Meetings

Identify pilot projects and explore the expansion of IC involvement

– DHS State and Local Government Coordination and Preparedness Office (SLGCP) Innovative Technology Evaluation Pilots (ITEP) are participating.

NASCIO promoted NIEM in recent Congressional call to action on Information Sharing

Current Status (2)

Developing Project Management Plan and National Joint Governance Structure

Adding new content to the public information NIEM website, cloned GJXDM, supporting tools and development web site.

Pilot Progress:– Completed Workshop on DHS HSARPA BTS Pilot April 11-13

Phoenix, AZ– Immigration and Customs Enforcement (ICE) mapping

Enterprise Logical Data Model to NIEM. – Disaster Management Initiative adds NIEM to their Standards

Process– Adding NIEM Content for FBI, DEA, ATFE, USMS, Case

Management-Litigation, and EOUSA.

National Institute of Standards and Technology (NIST) Partnership

Overall NIEM Development Guiding Principles

3

2

1Proof of Concept

Continuation

Scaling

Le

ve

l o

f C

om

ple

xit

y

Time

Initial Governance as a Collaborative Partnership Leverage Expertise Build on Current Success Prove Concepts through Pilot Projects Minimize Risk of Rework Provide Benefit to Users{

Incremental Pilot Development with Modular Approach:

Business DrivenHarmonized/Integrated Governance and

Technical Implementation Module “Fully Loaded Plug & Play”

Reduce Transition Risk from Planning to Operational

Produce Quantifiable Return on Investment for each milestone (pre-release)

{

National Services Broker National Consensus Framework Supports Business Modularity Flexible and Agile Information

Exchange Service Capability across all Levels of Government

Performance Metrics{IntelligentCapabilities/Services

Implementation Approach

Lessons

learned

Lessons

learned

New

requirements

New

requirements

Gov

erna

nce/

Tech

nolo

gy

Mod

ule

Inse

rtio

n

Gov

erna

nce/

Tech

nolo

gy

Mod

ule

Inse

rtio

n

Feedback

Feedback

NIEM Steering CommitteeNIEM Steering Committee

Global XSTFGlobal XSTF

GJXDM (operational) GJXDM (operational)

NIEM (tactical) NIEM (tactical)

Requirements from Global domainRequirements from Global domain

Requirements frombusiness domains

Requirements frombusiness domains

ATFE, ICEcontent

3.0.03.0.0 3.0.23.0.2 3.1.03.1.03.0.33.0.3 3.N3.N

0.10.1

initializeand ID Core

set-upexperimental

test bed

Explore good ideas: new metadata, scope/context, taxonomies/categories, federated NIEM repository, additional domains, Web Service interfaces, collaborative tools, OWL representation, …

U.S. Marshals, BTSService content

other content, features, capabilities as appropriate

0.20.2 0.N0.N 1.01.0

NIEM (strategic)NIEM (strategic)

Key Decision Points(KDP’s)

Busin

ess

Proce

ss

Mod

ular

ity

Busin

ess

Proce

ss

Mod

ular

ity

NIEM Steering CommitteeNIEM Steering Committee

Global XSTFGlobal XSTFGlobal JXDM (operational)Global JXDM (operational)

NIEM Track I (tactical) NIEM Track I (tactical)

3.0.23.0.2 3.1.03.1.03.0.33.0.3 3.N3.N

0.10.1

test bed

0.20.2 0.N0.N 1.01.0

NIEM Track II (strategic)NIEM Track II (strategic)

initialize

merge

Key Objectives in Phases I/II

•Initial Governance as a Collaborative Partnership•Leverage Expertise•Reuse GJXDM Operational Domain•Prove Concepts through Pilot Projects•Minimize Risk of GJXDM Rework•Provide Benefit to GJXDM Users

Phase 1 Phase 2

Proof of Concept

ScalingContinuation

•Collaboration with Stakeholders executing NIEM Incremental pilot development SOA modular approach. (participatory approach through “joint consensus building – SME’s across business domains)

•Build on layers of incremental development successNational Consensus Framework (modularized National governance structure)Technical service oriented implementation approach•Collaborative technologies•Information Exchange Package Automation•Performance metrics

NIEM Steering Committee NIEM Steering Committee

NIEM (tactical) NIEM (tactical)

Global XSTF Global XSTF

Core

U-Core

NIEM 1.0

1.01.0

National Consensus Framework

HomelandSecurity

DMWG

Other

Continue with GJXDM as isContinue with GJXDM as is

GJXDM GJXDM3.N3.N

Justice domain+ NIEM impact

Justice domain+ NIEM impact

evaluate for:

XSTF

Justice

Operational and Tactical Integration

NIEM Schedule (DRAFT)

2005 2006

(as required) technical assistance, presentations, training

Project management

Release 3.0.3

GJXDM User Conference

0.1 Release ……………………………….

Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

3.1.0a Release

Gather, analyze, vet, insert new content

NIEM 0.1a

New outputs (e.g. UML, XMI, …)

GJXDM Track 0 (operational)

1.0 ReleaseNIEM 1.0a

Revise tools for metadata

Analyze, ID, mark U-Core

Analyze dependencies, refactor, partition (UC, Core, domain spec)

(for partitioned NIEM)Revise tools

merge GJXDM + NIEM

3.0.4 Release3.0.4a

Domain groups use gapanalysis template to consolidate and vetnew content inputs.Add new metadata

.2 .n NIEM Track I (pilot)

Pilot agencies test NIEM .1, .2, … .n and feedback

2005 2006

(as required) technical assistance, presentations, training

Project management

Release 3.0.3

GJXDM User Conference

0.1 Release ……………………………….

Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

3.1.0a Release

Gather, analyze, vet, insert new content

NIEM 0.1a

New outputs (e.g. UML, XMI, …)

GJXDM Track 0 (operational)

1.0 ReleaseNIEM 1.0a

Revise tools for metadata

Analyze, ID, mark U-Core

Analyze dependencies, refactor, partition (UC, Core, domain spec)

(for partitioned NIEM)Revise tools

merge GJXDM + NIEM

3.0.4 Release3.0.4a

Domain groups use gapanalysis template to consolidate and vetnew content inputs.Add new metadata

.2 .n NIEM Track I (pilot)

Pilot agencies test NIEM .1, .2, … .n and feedback

NIEM Tiger Teams and Initial Messages

Governance: National Consensus Framework– Discussions with MIT and Harvard

Component Mapping Template (next slide)– Team testing template– Drafted recommendations/modifications to GTRI

Naming and Design Rules– Evaluating GJXDM NDR– Participating in Federal NDR

Concept of Operations– Establishing Team

Messaging Infrastructure and Facilitation– Establishing Team

Initial NIEM Messages– Terrorist Watchlist Person Data Exchange Standard 2.0– Emergency Management Resource Message– Facilitation planning under way for other messages

Component Mapping Template

National Collaboration Success

NIEM PMO Comprised of National Representation NIEM Facilitates Early Adopter Participation NIEM Promotes “Participative approach vs Delegative approach”

- National “Service Oriented” Modular Development

- National Consensus Framework (Modular Governance) Success = Subject Matter Experts (Business Driven) Executing Collaboration at an “UNPRECIDENTED” National Level

NIEM Development is Built on a Unified National Approach with

“Joint Consensus”

More Information at …

NIEM Public Website: http://www.NIEM.gov

Total # of hitsin one month

57,558