EAPMO Status & Plans

Download Report

Transcript EAPMO Status & Plans

National Information
Exchange Model (NIEM)
Executive Introduction
March 28, 2007
David J. Roberts
NIEM Program Management
Office
Information Sharing—A National Imperative
Detecting, preventing, responding to and
investigating crimes, disasters and terrorist acts
requires the exchange of information among
multiple engaged agencies.
Exchanges must be timely and accurate and
therefore highly automated.
Most existing computer systems are not designed to
facilitate information sharing across disciplines and
jurisdictions.
Automated information sharing between agencies
requires common standards for sharing information
between disparate systems.
Local, state, tribal, and federal agencies need to adopt
common information sharing standards to facilitate
information sharing
2
Information Exchanges Help Do The Job
• Exchanges using a national standard will make it easier to:
– Forward incident and arrest data from police to prosecutors
– Determine the status of beds, staff, and resources at hospitals to
allow EOC’s and EMS personnel to allocate resources better
– Send call data from a 9-1-1 center to multiple dispatch centers
– Report suspicious activities from field officers to investigators at state
and national levels and from one fusion center to another
– Report the status of emergency response teams and resources
– Identify units and status of resources in adjacent communities in
support of mutual aid agreements
– Screen persons or cargo entering the country
– And in many other scenarios
3
Objective of NIEM
Replace this
approach
Individual interfaces
With a simpler
approach
One standard
4
NIEM IS:
• A data standard for enabling information
exchanges across multiple communities of interest,
using agreed-upon terms, definitions, and
formats independent of the way data are stored in
individual systems.
• A way to achieve consensus on the content of
specific exchanges
• A structured and disciplined approach to data
interoperability
5
The Historical Perspective
•
•
•
•
•
•
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 was initially populated by the work from the highly successful Global
Justice XML Data Model, including data elements, structure, and the governance
model
NIEM was expanded in its first release by additional communities of interest
including the intelligence community, disaster management, infrastructure
protection, and international trade
The Program Manager of the Information Sharing Environment fostered the
further national emphasis on the use of NIEM in support of counter-terrorism
initiatives
Pilot projects in DOJ and DHS have tested the utility of the initial release of
NIEM, and efforts are underway to create pilot projects in state and local
governments
The production release of NIEM 1.0 is now available at www.niem.gov.
6
Participating Communities and Governance
Defining Data Components
Defining data components unique to
a domain will be done by subject
matter experts who are
representatives of the domain
following basic rules for definitions
and terms
A group representing all
participating domains will define
those data components that are
universal or commonly used by
more than one domain again using
the same basic rules
7
Governance Structure of NIEM
8
How NIEM works to support information
sharing
•
•
•
•
•
Create a scenario to reflect the
need for information sharing
between organizations
Define the requirements
including the data components
that should be included
Use the data component
standards from NIEM to build the
exchange, extending them
where needed
Document the exchange using
technology standards
Implement the exchange
9
Scenario Description
The 911 Emergency Operations Center (EOC) of a mid-sized urban
jurisdiction begins receiving telephone calls from residents regarding
what is variously described as a fire, an explosion, and a partial building
collapse of a 25-story building in city center. The calls quickly escalate in
number and urgency and are received from residents of the affected
office building, local residents of other nearby buildings, and cellular
telephone calls from pedestrians and passing motorists.
The EOC dispatches police, fire units, and emergency medical
personnel. The cause of the damage and the fire, as well as the extent
of the damage and scope of the emergency, takes time to establish.
First responders arriving on scene begin reporting back to the
EOC on the nature and scope of the damage, which is extensive and
may well result in a catastrophic collapse of the entire building and
potentially extensive damage to surrounding buildings. Initial on-scene units find the aftermath of a significant explosion
with several ongoing fires and many “walking wounded” wandering throughout the incident scene.
Police and fire initiate a command post across the street from the incident location. Police units establish a critical
perimeter for public safety entry only and begin initiation of a secondary perimeter using Geographic Information Systems
(GIS) mapping. Emergency Medical Services (EMS) set up an initial triage contiguous to the police and fire command
post. Initial injured are assessed, and information is forwarded to area hospitals via devices that are tracking
hospital capacities, services available, and patient transports.
Real-time video feeds are transmitted from the scene to the command post. Personnel location technology is in
use providing 2D/3D location and biotelemetry of fire and police personnel to their command staffs, as well as
monitoring of immediate air quality in proximity to the explosion site. Upon completion of the first search, the scene
is declared unsafe and messages are sent to all on-scene personnel to remain outside of the critical perimeter
until the scene is cleared by the bomb squad. The media is kept informed of progress, as appropriate.
10
Identify Information Exchanges
The scenario describes in narrative form an operational situation, business
context, legislative, judicial or executive mandate, or other circumstance
which must be addressed. From this scenario individual, discrete information
exchanges are identified for subsequent analysis.
Exchange 1:
The EOC dispatches police, fire
units, and emergency medical
personnel.
11
Identify Information Exchanges
Exchange 2:
First responders arriving on scene begin reporting back to
the EOC on the nature and scope of the damage.
12
Identify Information Exchanges
Exchange 3:
Initial injured are assessed, and information is forwarded to
area hospitals via devices that are tracking hospital capacities,
services available, and patient transports.
13
Analyze Requirements
for Business Exchange
Detailed information identifying triggering events, agencies
involved, conditions surrounding the exchange, and documenting
the actual data exchanged is captured for analysis and mapping
This detailed analysis of all dimensions of the information exchange can then be analyzed, graphically
displayed, and mapped to NIEM to discover and reuse IEPDs and universal & common components
14
Tools Available to Support NIEM
15
The NIEM Value Proposition
• Agencies and organizations that adopt NIEM will be able to:
– Gain faster access to critical information from other participating agencies
and organizations using NIEM
– Create automated information exchanges with partners in multiple
jurisdictions and disciplines at substantially less cost
– Leverage existing systems and avoid high costs of system replacement or
expensive single interface development
– Engage additional information exchange partners in the future without
incurring substantial new costs
– Tailor specific exchanges to meet their own needs and the needs of mission
critical partners using NIEM and related technologies
– More easily participate in regional, state, and national information sharing
systems that are or will be based on NIEM standards
– Participate in and contribute to shaping national standards for information
sharing
– Contribute to helping solve the national information sharing problem
16
Relating NIEM to Other Information Sharing
Mandates and Initiatives
• Homeland Security Presidential Directive (HSPD-5)
• Homeland Security Act 2002
• Intelligence Reform and Terrorism Prevention Act—2004
• Executive Order 13388—Guidelines and Requirements for the
Information Sharing Environment (ISE)—2005
• Law Enforcement Information Sharing Program (LEISP)
17
The Future of NIEM
•
Agencies can begin now to implement information exchanges based on NIEM by
participating communities of interest involving local, state, tribal and federal
agencies and organizations in support of homeland security, justice and public
safety missions
•
NIEM is being used to create national priority exchanges for suspicious activity
reporting, incident reporting, case management, person and cargo screening,
disaster management and other critical areas of national significance
•
A new release—Harmony—with additional improvements will be issued in 2007.
•
There will be expanded training and technical assistance efforts to help
participants implement NIEM-based exchanges
•
Eventually, the intent is to expand the participating communities of interest to
include health care, transportation, education and others, creating parallel
governance structures to include representation in the expansion of the data model
18
Lessons learned from past experience
• All exchanges should be derived from operational needs for
information
• Subject matter experts should be used to define the
requirements for each information exchange from the
beginning
• The right enterprise architecture is critical to success
• Maximize the use and application of existing standards for
information sharing, particularly open standards such as
XML, web services, etc.
• Build on past successes in comparable jurisdictions
• Seek advice from technical experts to design exchanges
once the operational requirements are determined
19
Next Steps
• Choose to make NIEM the basis for information
exchanges
• Adopt a service oriented architecture for your
information systems
• Arrange for training for your developers
• Identify key exchanges with other organizations
• Use NIEM tools to develop exchange
documentation
• Design and implement the exchanges using web
services
20
Tools and Support Services
•
Documentation
• Training and Technical
• Introduction to NIEM
Assistance
• Concept of Operations
–
NIEM website
• User Guide
–
Training materials
• Naming and Design Rules
–
Help desk and knowledge base
• Standards
• NIEM 1.0
• Documentation specs
–
•
National and regional training
Tools
–
Automated documentation
generator
–
Tools to browse the model
–
IEPD Clearinghouse
All available through
www.niem.gov
21
Conclusion
• For more information visit the NIEM web site
(http://www.niem.gov)
• Contact NIEM by email at [email protected]
Questions and Discussion
22