04/20/23 06:39 04/20/23 06:39

National Information Exchange Model

Global Justice XML Data ModelUsers Conference

June 10, 2005

James Feagans, DOJ and Michael Daconta, DHS

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 Drivers

Trigger Event Begins with Real People

Built off existing infrastructure

Information exchange occurs at key decision points in the process

Technical solutions driven by functional requirements

Appropriate Security & Privacy

Protections

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

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

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

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

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

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

Identified Pilot Projects:– ATFE, DEA, FBI, USMS– HSARPA BTS Net, ICE– DHS State and Local Government Coordination and

Preparedness Office (SLGCP) Innovative Technology Evaluation Pilots (ITEP) are participating.

Future Expansion of IC Involvement:– Intelligence Community Metadata Working Group (ICMWG)

Partnership

Current Status (2)

NIEM Public Information Website New Content

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. Fully participating in the effort.

– Discussions with IAIP and FEMA

National Institute of Standards and Technology (NIST) Partnership

Overall NIEM Development Guiding Principles

3

2

1

Proof of Concept

Continuation

Scaling

Le

ve

l o

f C

om

ple

xit

y

Time

Initial Governance as a Collaborative Partnership Leverage XSTF Expertise Build on Current Success of GJXDM (Reuse GJXDM Operational Domain) Prove Concepts through Pilot Projects & Component Analysis Minimize Risk of GJXDM Rework Provide Benefit to GJXDM Users{

Initial NIEM Program Management Office Implement Vetting Process Implement Help Desk & Training Program Incorporate Key Core Data Virtual Input Into Model Begin Automated Harmonization Extend GJXDM Content and Architecture Buy-in of Stakeholders{

NIEM National Program Management Office National Exchange Vision National Governance Program GJXDM/NIEM Integration Expanded Tools and Capabilities Virtual Help Desk & Training Program Collaborative Technologies Automated Harmonization Information Exchange Package

Automation

{IntelligentCapabilities/Services

Implementation Approach

Lessons

learned

Lessons

learned

New

requirements

New

requirements

Tech

nolo

gy

inse

rtio

n

Tech

nolo

gy

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 fromDHS + DoJ domainRequirements fromDHS + DoJ domain

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 bedExplore 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)

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 PartnershipLeverage XSTF ExpertiseReuse GJXDM Operational DomainProve Concepts through Pilot Projects& Component AnalysisMinimize Risk of GJXDM ReworkProvide Benefit to GJXDM Users

Phase 1 Phase 2

Proof of Concept

ScalingContinuation

Initial NIEM Program Management OfficeImplement Vetting ProcessImplement Help Desk & Training ProgramIncorporate key core dataVirtual Input Into ModelBegin Automated HarmonizationExtend GJXDM Content and ArchitectureBuy-in of Stakeholders

NIEM National Program Management OfficeNational Exchange VisionNational Governance ProgramGJXDM/NIEM IntegrationExpanded Tools and CapabilitiesVirtual Help Desk & Training ProgramCollaborative TechnologiesAutomated HarmonizationInformation Exchange Package Automation

NIEM Steering Committee NIEM Steering Committee

NIEM (tactical) NIEM (tactical)

Global XSTF Global XSTF

Core

U-Core

NIEM 1.0

1.01.0

NIEM National Governance

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 PROJECT MANAGEMENT DEVELOPMENT AND OPERATION

1.1 Create NIEM Agreement

1.2 Staff NIEM Project Team and Governance Structure

1.3 Establish Initial NIEM Operational Environment

1

Establish NIEMOperational

Domain

0

Perform NIEM Development

2

Identify NIEM

Content3

Review and Adopt NIEM

Core Component 4

Maintain and Support NIEM

5

Implement and Disseminate NIEM Content

2.1 Collect NIEM Components

2.2 Validate NIEM Components

2.3 Identify Existing Standard

2.4 Develop NIEM Data Component Proposal

3.1 Establish Review Project

3.2 Coordinate and Review NIEM Component Draft Proposal

3.3 Document and Approve NIEM Standard

4.1 Plan and Control NIEM

4.2 Maintain NIEM Content and Configuration

4.3 Support NIEM Users

5.1 Create XSD Subset 5.2 Create & Catalog Information Exchange Package Description 5.3 Disseminate NIEM Products

Evolution of the Repository and Metadata

GJXDM

OtherNamespaces

WantLists

JIEMReference

Model

Extensions

Businesscontainers

& msgconstructs

IEPDs

GJXDM

ExternalNamespaces(code tables)

AS-IS TO-BE

Expand the types of artifacts that can be stored, registered,

and related within the repository.

1

Expand the repository metadata to support the addition of new artifacts.

2 Establish relationships between artifacts based on context, scope,

and other attributes.

3

Service Oriented Architecture

NIEM: Next Steps

Creating standard format for Component Mapping Template. – Project Tiger team (consisting of all pilot projects) was formed to

develop and test component mapping template. – Product will be posted to the NIEM web site.

Create NIEM National Collaboration Tiger Teams (Development via Unified Consensus Building)– Project Tiger teams (consisting of all levels of government)

formed to develop:• Interim and National Governance with Collaboration Tool

Suite• CORE Components/Naming & Design Rules (NDR)

NIEM CONOPS DRAFT released for NIEM Committee Review.

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 Joint Development

- National 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