National Information Exchange Model (NIEM) Overview and Status January 31, 2007 Kshemendra Paul NIEM Program Executive & Chief Enterprise Architect US.

Slides:



Advertisements
Similar presentations
An Overview of the Federal Segment Architecture Methodology
Advertisements

Applying the SOA RA Utah Public Safety ESB Project Utah Department of Technology Services April 10, 2008 Prepared by Robert Woolley.
NIEM OVERVIEW 2 Support Framework Technical FrameworkCommunity Formal Governance Processes Online Repositories Mission-Oriented Domains Self-Managing.
Enterprise Data Management and NIEM “Positive Impacts on Information Sharing” December 2010 DHS Enterprise Data Management and the National Information.
INFORMATION SHARING USING NIEM 1. THE IMPETUS FOR CHANGE: NIEM’S BEGINNINGS 2.
National Information Exchange Model (NIEM) Status Update April 26, 2006 Paul Embley (NIJ, XSTF Chair) Kshemendra Paul (DOJ Chief Enterprise Architect,
Connecting People With Information DoD Net-Centric Services Strategy Frank Petroski October 31, 2006.
Adopt & Adapt Tips on Enterprise Data Management Annette Pence September 10, 2009 MITRE.
1 Overview of Other Global Networks Exchange Network User Group Meeting April 2006.
National Information Exchange Model (NIEM) Status and Future September 6, 2006 Kshemendra Paul NIEM Program Manager Chief Enterprise Architect US DOJ.
Considering an Enterprise Architecture for the NSDI
The topics addressed in this briefing include:
August 2011 David Jenkins Administration for Children and Families ACF Interoperability Human Services 2.0 Overview.
0 United States Environmental Protection Agency Office of Environmental Information Enterprise Architecture Program December 2007 EA Working Group Session.
Developing Enterprise Architecture
Program Manager, Information Sharing Environment UNCLASSIFIED ISE Enterprise Architecture and Common Standards Program.
PROJECT NAME: DHS Watch List Integration (WLI) Information Sharing Environment (ISE) MANAGER: Michael Borden PHONE: (703) extension 105.
1 1 National Information Exchange Model (NIEM) OASIS Emergency Interoperability Summit: Roadmap to Emergency Data Standards Roundtable.
National Information Exchange Model (NIEM) Program Update January 11, 2007 Thomas O’Reilly NIEM Program Management Office.
National Information Exchange Model (NIEM) Executive Introduction March 6th, 2007 Donna Roy Director, DHS Enterprise Data Management Office Chair, NIEM.
National Information Exchange Model (NIEM) Executive Introduction March 28, 2007 David J. Roberts NIEM Program Management Office.
Army Net-Centric Data Strategy Center Of Excellence (ANCDS) Army Data Harmonization and Integration Working Group (ADHIWG) Sever Ciorlian ANCDS Team Lead.
NIEM Domain Awareness June 2011 Establishing a Domain within NIEM.
Information Sharing Challenges, Trends and Opportunities
Mini Kanwal Core Data Type - PERSON December 02, 2004.
C W3C Government Linked Data Working Group Cory Casanave 06/30/2011 Cory Casanave Cory-c at modeldriven dot com CEO, Model Driven Solutions Founder,
Service Oriented Architecture (SOA) at NIH Bill Jones
Public Sector NIEM Team, December 2011 NIEM Test Model Data Deploy Requirements Build Exchange Generate Dictionary XML Exchange Development National Information.
SEARCH Membership Group Systems & Technology PAC Global Justice XML Data Model (GJXDM) Update January 29, 2005.
NIEM 101 -Technical Introduction to NIEM This course will introduce business and technical architects, program analysts and information exchange designers.
Who is TIJIS? What is NIEM? What is the Texas Path to NIEM? What does it mean to me?
Cairo Corporation An Inc 500 Company ISO9001:2000 CERTIFIED 8(a) ۰ SDB ۰ WOB ۰ GSA ۰ GSA STARS The Dream of a Common Language: Extending the Role of the.
National Information Exchange Model Presented by : Mini Kanwal June, 09.
The State of the Information Sharing Union The State of the Information Sharing Union Paul Wormeli Executive Director IJIS Institute
The National Information Exchange Model at
NIEM Information Exchange Package Documentation (IEPD) Mini Kanwal NIEM Technical Advisor Department of Homeland Security September, 7 th 2006.
National Information Exchange Model (NIEM) Overview February 7, 2006 Dave Roberts NIEM Communications and Outreach.
FEA DRM Management Strategy Presented by : Mary McCaffery, US EPA.
11/7/ :20 PM National Information Exchange Model Global Justice XML Data Model Users Conference June 10, 2005 James Feagans, DOJ and Michael Daconta,
EPA Geospatial Segment United States Environmental Protection Agency Office of Environmental Information Enterprise Architecture Program Segment Architecture.
S&I Integration with NIEM (DRAFT) Standards Development Support June 8, 2011.
11/10/ :04 AM National Information Exchange Model James Feagans & Michael Daconta NIEM Project Manager GLOBAL ADVISORY COMMITTEE BRIEFING October.
1 The New York State Integrated Justice Information Exchange Project BJA Regional Information Sharing Conference: Information Exchange Modeling/Business.
Partnerships in Information Sharing California Department of Justice Bureau of Criminal Identification and Information.
National Information Exchange Model (NIEM) Data Architecture Subcommittee Status and Future September 14, 2006 Kshemendra Paul Chief Enterprise Architect.
United States Department of Justice Achieving Information Interoperability and Business Agility The Justice Reference Architecture:
1 DAS Annual Review June 2008 “Build to Share” Suzanne Acar, US DOIAdrian Gardner, US National Weather ServiceCo-Chair, Federal DAS
EGovOS Panel Discussion CIO Council Architecture & Infrastructure Committee Subcommittee Co-Chairs March 15, 2004.
National Information Exchange Model (NIEM) Executive Introduction November 29, 2006 Thomas O’Reilly NIEM Program Management Office.
The FEA Data Reference Model V2.0 Michael C. Daconta, DRM Working Group Lead Susan Turnbull, AIC Representative Mary McCaffery, FEA PMO Representative.
National Information Exchange Model (NIEM) NGA Executive Policy Forum Santa Fe, NM May 2-3, 2005 Bob Greeves Bureau of Justice Assistance U.S. Department.
United States Department of Justice Achieving Information Interoperability and Business Agility The Justice Reference Architecture:
DOT Implementing the Surface Transportation Domain Daniel Morgan 26 October 2015.
Decoding the Alphabet Soup: Global JIS Standards 101.
Exploring Service-Oriented Architecture (SOA) to Support Justice-Related Information Sharing Steven E. Correll, Chair Global Infrastructure/Standards Working.
Enterprise Architecture & Process Improvement EPIC Process Improvement Workshop April 17, 2007 Dick Burk Chief Architect and Manager, Federal Enterprise.
National Information Exchange Model (NIEM) October 24, 2006 Jeremy Warren Deputy Chief Technology Officer U.S. Dept. of Justice.
U.S. Department of Justice Law Enforcement Information Sharing Program (LEISP) Spring 06 - Global Advisory Committee (GAC) Meeting Vance Hitch, Chief Information.
Implementing the FEA DRM Michael C. Daconta Metadata Program Manager March 15, 2004.
Federal Enterprise Architecture (FEA) Architecture Plus Meeting December 4, 2007 Kshemendra Paul (Acting) Chief Architect.
1 Industry Advisory Council’s Enterprise Architecture Shared Interest Group (IAC EA SIG) Collaborative Approach to Addressing Common Government- Industry.
Armstrong Process Group, Inc. Copyright © Armstrong Process Group, Inc., All rights reserved National Information Exchange.
Overview: Spatial Data Standards for Facilities, Infrastructure and Environment (SDSFIE) Services Support FGDC Coordination Group Meeting 6 February 2007.
National Emergency Communications Plan Update National Association of Regulatory Utility Commissioners Winter Committee Meeting February 16, 2015 Ron Hewitt.
Federal Enterprise Architecture (FEA)
Implementing the Surface Transportation Domain
Achieving Justice Information Interoperability
About The Federal Data Architecture Subcommittee (DAS) 2008
CAF Quarterly Meeting Measuring the Value of an EA Practice
Michael Daconta & James Feagans
Presentation transcript:

National Information Exchange Model (NIEM) Overview and Status January 31, 2007 Kshemendra Paul NIEM Program Executive & Chief Enterprise Architect US DOJ (202)

2 Agenda Overview Scope & Fit in FEA NIEM (GJXDM) Delivered Results Goals and Status High Level Architecture Value Proposition Target Outcomes Outcome / Governance Alignment Deliverables Questions & Discussion

3 Overview 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 brings Communities of Interest (COIs) together to: –Develop (and harmonize) reusable data exchange components –Leverage (NIEM and external) data exchange components to build information exchanges –Utilize cross COI governance to maximize inter-operability and reuse –Publish and discover reusable information exchanges –Provide standards, tools, methods, training, technical assistance and implementation support services for enterprise-wide information exchange

4 Scope NIEM is Payload – Specifications for Data in Business Context

5 Fit With Federal Enterprise Architecture Policy Performance Business Data Services Technology Scope of FEA Information Exchange Architectural Profile Business – standard information exchanges –Focus on reuse and modification –Authoritative vs. non-authoritative –Discover / register exchanges via repository Data – common vocabulary for building information exchanges –Focus on reuse –Federated, hierarchical domain structure –Optional and over-inclusive augmentation Performance – measure information sharing –Use/reuse of information exchanges –Use/reuse of data components (in/out of model) –Line of sight provides actionable feedback Focus of NIEM Influenced By NIEM

6 Goals and Status Deliver NIEM –NIEM 1.0 (Delivered October 2006) –Currently working on NIEM Harmony Release (Target Beta April 2007) –Ramp-up governance, communications, and outreach activities (Underway) Catalyze NIEM adoption and usage with stakeholders –Migration of GJXDM installed base (Underway) –DOJ, DHS EA – NIEM is the standard for information exchange (Done) –DOJ, DHS Grants – use of NIEM is a special condition (Done) Enable delivery of Common Terrorism Information Sharing Standards (Target Phase 1 June 2007) Deepen partnerships with communities of interest –Update and extend MOU (Underway) –NIEM in the Federal Transition Framework (Underway) Become the standard, by choice, for government information exchange (Future)

7 NIEM (GJXDM) – Delivered Results AspectFebruary 2007 Increased Cross- Domain & Cross- Organization Inter- Operability ~1M Law Enforcement Officers in the US at the Local, State, Tribal, and Federal levels (including DOD, DHS, DOJ, DOI, Treasury) across 18K plus distinct entities DoD integrates public safety & law enforcement data for US-based force protection supported by NCIS – One DOJ inter-operation National Association of State CIOs has endorsed adoption and use of NIEM based on GJXDM track record and migration decision. Enabled Mission Improvement ~90M inter-state transactions a month across ~20 transaction types; FBI CJIS committed to NIEM in current development activity ARJIS (San Diego) was able to correlate 700K license plates from border crossing with outstanding warrants over a four day period to generate ~225 felony leads TSC / NCTC Terrorist Screening (TWPDES); Amber Alerts; National Sex Offender Registry; Cross-Jurisdiction Drivers’ License, Rap Sheets, Wants and Warrants, and Vehicle Registration; State and Federal Court Filings Cost Savings & Avoidance Single DHS people screening exchange standards are the basis for inter- operability and build once use many reuse between US Visit, CBP, Immigration, ICE, State, FBI, and other stakeholders New York has built a family of ~150 NIEM 1.0 IEPDs and reporting high levels of data component reuse and application code simplification. Multiple reports of million dollar plus savings and vendor discounts on interface development

8 Federated Domain Architecture

9 Business Driven Information Exchanges An Information Exchange Package (IEP) begins with a business need for a particular exchange. IEP Documentation (IEPD) describes how that exchange should be expressed using the NIEM. The IEPD is a key point for introducing new elements to NIEM and for reusing existing ones. An IEPD itself can also be reused in whole or in part to speed development and lower the cost of sharing information.

10 Data Model Maturity Lifecycle

11 Value Proposition Interlude – DHS (Any Federal Agency) Today Currently in development, Services rolling out to help Legacy systems Legacy systems DHS Conceptual/ Logical Data Model DHS SOA Service Bus DHS Information Sharing Environment Maybe 10% Done Extremely expensive and timely to develop Is there one? Lots of activity for defining information in between components or individual systems or inside systems, but not being captured for reuse Working on info sharing to (DHS example: connect 40+ systems/data sources related to person screening ) Enterprise Architecture Status Behind on DRM implementation Lack Information Sharing Foundation EA based SOA is ready for data exchange definition

12 Value Proposition – Accelerates Mission Driven Information Sharing NIEM Model DHS Registry of Information Exchanges Information Exchange Package Descriptions (IEPDs) Used to create Are Registered in Are used to create Interfaces for information sharing Legacy systems Legacy systems Used to help build Data Model based on Interface needs, not whole system 1) SAVE $$$$ maturing DRM DHS Conceptual/ Logical Data Model DHS SOA Service Bus 2. Builds foundation for Information Sharing Environment, providing a place to capture current activity DHS Information Sharing Environment 3.Faster and less costly connections between legacy systems by defining common exchanges to be used within common services structure Separate enclaves & registries for SBU vs. Classified

13 Target Outcomes Priority One – Enable Fusion Center Inter-Operability via CTISS –Crosses DNI, DHS, DOJ, and Local/State/Tribal Public Safety –Deliverable is specific CTISS exchange standards Priority Two (Shorter Term) – Establish Standards Adoption Process –IC, DHS, and DOJ via Enterprise Architecture activities –State & Local Fusion Centers via special condition language –Deliverable is clear, consistent, & detailed processes and guidance for implementation Priority Two (Longer Term) – Domain (Signatory) Specific Exchanges –Global – Rap Sheet, Critical Infrastructure, CANDLE w/Photo (Real ID) –DOJ/DHS/IC – EA-based adoption, prioritization, creation, & implementation Executive Steering Committee & Phase 2 ISE Implementation Plan Mandate –Driving mission and program alignment (target outcomes & resource allocation) –Expansion to other domains such Defense, Transportation, & Environmental Protection

14 Governance/Outcome Alignment NIEM Infrastructure Standards Adoption Process CTISS Outcome Areas Governance Bodies NIEM National Priority Exchange Panel (NPEP) working under ISC Domain-specific activity in consultation with NIEM NPEP NIEM Committees with deadlines and escalation process to insure timely decisions Domain Specific Exchanges NIEM Policy Advisory Panel base lining current processes Outcomes Focused Mandate Governance Style Community Consensus

15 Deliverables Documentation Introduction to NIEM Concept of Operations User Guide NIEM Naming and Design Rules Standards NEIM 1.0 / Harmony Reference Exchanges Training and Technical NIEM website Training materials Help desk Tools Component Mapping Template Schema Subset Generation Tool Graphical Browser Exchange Repository Governance and Processes The structure to manage and maintain NIEM and the processes and procedures behind its operations.

16 Questions and Discussion For more information visit the NIEM web site ( Contact NIEM by at