Slide1 l.jpg
This presentation is the property of its rightful owner.
Sponsored Links
1 / 14

National Information Exchange Model (NIEM) OASIS Emergency Interoperability Summit: Roadmap to Emergency Data Standards Roundtable PowerPoint PPT Presentation


  • 166 Views
  • Uploaded on
  • Presentation posted in: General

National Information Exchange Model (NIEM) OASIS Emergency Interoperability Summit: Roadmap to Emergency Data Standards Roundtable. What is NIEM?. NIEM is a joint DOJ / DHS / S&L program, started in 2005 to promote the standardization of XML information exchanges. NIEM provides:.

Download Presentation

National Information Exchange Model (NIEM) OASIS Emergency Interoperability Summit: Roadmap to Emergency Data Standards Roundtable

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Slide1 l.jpg

National Information Exchange Model (NIEM)OASIS Emergency Interoperability Summit:Roadmap to Emergency Data Standards Roundtable


What is niem l.jpg

What is NIEM?

NIEM is a joint DOJ / DHS / S&L program, started in 2005 to promote the standardization of XML information exchanges. NIEM provides:

  • A Common Vocabulary with terms, definitions, and formats - independent of an individual agency’s database management systems

  • A Structured Approach to developing the reference documentation that expresses the NIEM information exchange’s requirements in an implementation ready format – the Information Exchange Package Documentation (IEPD) development process


Niem provides a common language l.jpg

NIEM provides a Common Language

  • NIEM Infrastructure

  • NIEM has several mission based domains

  • The data elements within the domains are defined by the respective Communities of Interest (COIs)

  • Information relevant across domains is built into a NIEM Core

  • Domain Governance

  • Each domain has its own stewarding organization comprised of relevant stakeholders to manage updates and minor releases

  • The NIEM Program Management Office (PMO) supports cross domain harmonization and maturation of the core for major releases

Built and governed by the business users at Federal, State, Local, Tribal and Private Sectors


Niem provides a consistent approach l.jpg

An IEPD is a specification that defines a particular data exchange

An IEPD must be portable, self-contained, and self-documented

They must be designed to allow for sharing and reuse

IEPDs are developed with a core set of artifacts in a prescribed format and organizational structure to allow for consistency

NIEM provides a Consistent Approach

  • IEPD Artifacts Include:

    • Domain Model

    • Component Mapping Template

    • Schemas

    • IEPD Main Document:

      • - Business Rules

        • - Business Requirements

        • - Process flows

        • - Use Cases

Repeatable, reusable process for business users to document information exchange requirements


Slide5 l.jpg

Program Updates


Niem 2 1 release due 30 sep 2009 l.jpg

NIEM 2.1 release (due 30 Sep 2009)

  • Infrastructure Protection

  • Emergency Management(note: EDXL implements NIEM)

  • Immigration

  • Screening(people, cargo, conveyance)

  • Maritime

  • Family Services

  • Justice(law enforcement, courts,detentions, case mgmt)

  • Biometrics

  • CBRN(currently focused on Rad-Nuc)

  • Intelligence

  • International Trade

  • Geospatial(using GML) (No changes to NIEM Core)


New niem training courses l.jpg

New NIEM training courses


Looking ahead key focus areas l.jpg

Looking ahead, key focus areas.

  • Controlled growth

    • Health (primarily biosurveillance & public health alerting)

    • Transparency with XBRL (XML Business Reporting Language)

    • S&L asking for Environmental and Transportation

  • Domain independence

    • via increased self-service/self-management capabilities

  • NIEM tools RFI and architecture

    • Increased tool support & commercial software industry coord.

    • DHS tools: IEPD Factory, CAM (Content Assembly Mechanism), DHS S&T-developed Synthetic XML Data Generator

  • Exploratory areas

    • Supporting Web-oriented/ feed-based Architecture per lessons learned from American Recovery & Reinvestment Act (ARRA)

    • Maturing NIEM usage in government e-forms applications


Slide9 l.jpg

NIEM and EDXLin DHS Information Sharing Environment


The dhs information sharing environment ise l.jpg

The DHS Information Sharing Environment (ISE)


Background on dhs esbs l.jpg

Background on DHS ESBs

Original strategy:“One DHS ESB”

New strategy: “Interoperable Component ESBs”

NPPD ESB

NPPD ESB

US CIS ESB

ICE ESB

CBP ESB

FEMA ESB

USCG ESB

FLETC ESB

FLETC ESB

US CIS ESB

ICE ESB

CBP ESB

USCG ESB

FEMA ESB

FLETC ESB

NPPD ESB

FEMA ESB

USCG ESB

CBP ESB

Centralized DHS ESB

ICE ESB

TSA ESB

S&T ESB

US CIS ESB

USSS ESB

OPS ESB

I&A ESB

TSA ESB

S&T ESB

USSS ESB

OPS ESB

I&A ESB

DNDO ESB

F/S/L/PS partners

DNDO ESB

F/S/L/PS partners

F/S/L/PS - Federal, State, Local and Private Sector


Interoperable dhs component esbs l.jpg

Interoperable DHS Component ESBs

  • Enabling interconnected, peer ESBs in the DHS ISE requires Interoperability, Audit-ability, and Maintain-ability.

1. Interoperability

between Component ESBs via an enterprise messaging framework at the Transport layer, Service layer , Functional layer, and Data layer.

2. Audit-ability

across Component ESBs for DHS Enterprise Services. Transactional-auditing must be enabled across independent Component-level audit logs.

DHSESBs

3. Maintain-ability

of message headers used by DHS ESB-enabled services. Without an SOA Enterprise Message Header Framework, there would be a proliferation of incompatible message headers across DHS services resulting in increased integration costs, maintenance costs and decreased interoperability.


Dhs soa enterprise message header framework l.jpg

DHS SOA Enterprise Message Header Framework

TRANSPORT

LAYER

HEADER

JMS

IBM MQ

Tibco EMS

Oracle AQ

HTTP

SERVICE

LAYER

HEADER

SOAP and WS-standards

WSDL

Service Header

Logical Model

Fixed-length Format

FUNCTIONAL

LAYER

HEADER

EDXL-DE

LEXS

EDXL-DE

Screening

Functional Header

Logical Model

UCore

ANSI X12 /

EDIFACT

CAMIR /CATAIR

PAYLOAD

NIEM

IEPD

EDI

Binary

XML


Slide14 l.jpg

More information

http://www.NIEM.gov

Twitter: @NIEMExecDir

Help desk: 1-877-333-5111

Contact Information

Anthony HoangDHS OCIO/Enterprise Data Management [email protected]: 202-447-3726cell: 202-306-7787

Questions?


  • Login