Transcript Document

National Information Exchange Model
James Feagans, DOJ and Michael Daconta, DHS
July 26, 2005
James Feagans, Department of Justice
7/17/2015 6:56 PM
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)
National Information Exchange
Model
Canonical
Standard
Point-to-Point
Mapping --- n(n-1)
Canonical Standard
Approach --- 2n
NIEM Program Vision
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 Goals
 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 Goal Drivers
 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 Principles
 Trigger Event Begins with Real People
TriggerEvent
 Built off existing infrastructure
Organization A
 Information exchange occurs at key
decision points in the process
 Quickly determine who makes the
decisions allowing management (at all
levels) to implement decisions
Message
Organization B
 Technical solutions driven by functional
requirements
 Resulting event effects Real People
ResultingEvent
NIEM: Leveraging the
Total Components
Global Justice XML Data
Model Content
Release Version 3.0
1%
3%
6%
Property
397
4%
6%
Complex types
Simple types
Properties
Total Components
Misc Metadata
116
177
1216 Activity
Activity
1216
Person
543
400
150
2,209
2,754
45%
543 Person
397 Property
178 Location
33 Contact Information
94 Organization
14%
177 Miscellaneous
21%
116 Metadata
The Concept of Core
Major Domains
Homeland
Security
Emergency Management,
Border Security, etc.
CORE
Public
Health, etc.
Secondary
Domains
CORE
Law
Enforcement,
Intelligence, etc.
Public
Safety
Courts, Probation,
Parole, Corrections, etc.
UNIVERSAL
CORE
CORE
Welfare,
Juvenile Justice,
Education, etc.
etc.
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 Name
Person Address
Person Date Of Birth
Person Gender
Person Ethnicity
Person Race
TWPDES-PERSON
DOJ-PERSON
ICE-PERSON
DOD-PERSON
IAIP-PERSON
Person Id (FK)
Person Id (FK)
Person Id (FK)
Person Id (FK)
Person Id (FK)
Person Education
Person Physical Description
Person Kinship
Person Medical
Person Skill
Person Agency Interest
Person Driving Incident
Person Drivers License
Person Acquaintance
Person Day Contact
Person Evening Contact
Person Adopted Child
Person Adoptive Parent
Person Gang Affiliation
Person Affiliation Organization
Person Charge
Person Detained Location
Alien Number
Alert Code
Photo Code
Finger Print
Entry Date
Family Health
Family Detail
Employment Authorization
Person Eye Color
Person Usual Weight
Person Hair Color
Person Birth Time
Person Total Dependent Quantity
Person Adult Dependent Quantity
Person Personal Attributes
Person Physical Descriptors
Person Employment
Person Capabilities
Person Affiliations
Person 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>[email protected]</j:ID>
</j:ContactEmailID>
<j:ContactWebsiteID>
<j:ID>http://alerts.mayberry.ci.us</j:ID>
</j:ContactWebsiteID>
National Information Exchange Model Concept
Information Exchange
Package Descriptions (IEPDs)
AmberAlert
Virtual Object Reuse Repository –
types, properties, business containers,
msg constructs, service metadata, …
<AmberAlert>
IEPD
Template
Transport
<Transport>
EDXL_Msg
Homeland
Security
Health
Universal-Core
Core
Exchange
Requirements
Transportation
Justice
IEPDs
Semantically
consistent
across all
domains
Emergency
Management
Tools,
methods,
mapping,
process,
training,
etc.
New IEPDs
New reusable
components
Collaborative
Tools
(for distributed
consensus)
New components
Governance
Bodies
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
{
{




Continuation
Level of Complexity
3
Scaling
2
1
{
Proof of
Concept
Time






Intelligent
Capabilities/
Services
National Services Broker
National Consensus Framework
Supports Business Modularity
Flexible and Agile Information
Exchange Service Capability across all
Levels of Government
 Performance Metrics
 Incremental Pilot Development with Modular
Approach:
Business Driven
Harmonized/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)
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
Implementation Approach
Requirements from Global domain
Global XSTF
3.0.0
3.0.2
3.0.3
GJXDM (operational)
ATFE, ICE U.S. Marshals, BTS
initialize
content
Service content
and ID Core
Key
Decision
Points
(KDP’s)
0.1
0.2
3.N
3.1.0
other content, features,
capabilities as appropriate
NIEM Steering Committee
NIEM (tactical)
0.N
1.0
Requirements from
business domains
set-up
experimental
test bed
NIEM (strategic)
Explore good ideas: new metadata, scope/context, taxonomies/categories, federated NIEM
repository, additional domains, Web Service interfaces, collaborative tools, OWL representation, …
Key Objectives in Phases I/II
Global XSTF
3.0.2
Global JXDM (operational)
3.0.3
3.N
3.1.0
merge
NIEM Steering Committee
initialize
0.2
0.1
0.N
NIEM Track I (tactical)
1.0
NIEM Track II (strategic)
test bed
Phase 1
Proof of
Concept
•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 2
Scaling
•Collaboration with Stakeholders executing
NIEM Incremental pilot development SOA
modular approach.
(participatory approach through “joint
consensus building – SME’s across
business domains)
Continuation
•Build on layers of incremental development
success
National Consensus Framework
(modularized National governance structure)
Technical service oriented implementation
approach
•Collaborative technologies
•Information Exchange Package Automation
•Performance metrics
Operational and Tactical Integration
Continue with GJXDM as is
Global XSTF
3.N
GJXDM
NIEM 1.0
U-Core
evaluate for:
Justice domain
+ NIEM impact
1.0
Core
Justice
Homeland
Security
XSTF
DMWG
NIEM (tactical)
Other
NIEM Steering
Committee
National Consensus
Framework
NIEM Schedule (DRAFT)
2006
2005
Jul
Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul
Release 3.0.3
3.1.0a
Release
3.0.4a
3.0.4 Release
Aug Sep Oct Nov Dec
GJXDM Track 0 (operational)
GJXDM User Conference
merge GJXDM + NIEM
Analyze, ID, mark U
-Core
Analyze dependencies, refactor, partition (UC, Core, domain spec
)
Pilot agencies test NIEM .1, .2,
… .n and feedback
NIEM 0.1a
0.1 Release………………………………
.2
.n
.
NIEM 1.0a
1.0 Release
Gather, analyze, vet, insert new content
Revise tools (for partitioned NIEM) Add new metadata
New outputs (e.g. UML, XMI,…)
Domain groups use gap
analysis template to
consolidate and vet
new content inputs.
Revise tools for metadata
(as required) technical assistance, presentations, training
Project management
NIEM Track I (pilot)
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 Development is Built on a Unified
National Approach with “Joint Consensus”





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
More Information at …
NIEM Public Website: http://www.NIEM.gov
Total # of hits
in one month
57,558