James Feagans & Michael Daconta NIEM Project Manager

1. GLOBAL ADVISORY COMMITTEE BRIEFING October 20, 2005 James Feagans & Michael Daconta NIEM Project Manager

2. NIEM Evolution • Global Justice Information Sharing Initiative • National commitment to sharing critical information across this diverse national landscape. • Global and DOJ have committed considerable time and energy making national justice information sharing a reality. • NIEM seeks to capture the benefits of this considerable effort and expand under the current MOA • Expansion shall include Law enforcement and broader justice exchanges (focus of the GJXDM), Public safety and Homeland security related exchanges. • NIEM Goal • Ultimately, in a few years, the technical framework that emerges will allow agencies across all levels of government and groups to adopt the NIEM approach making it a true national model for the full range of information sharing activities within the United States.

3. NIEM Transition NIEM Pilots Add Content Harmonize Re-engineer Technical Architecture NIEM Global Broaden Governance Re-Work Process Expand Collaboration Increase User Base Review and Comment

4. NIEM Governance – The Impossible Challenge? • Governance is HARD! • Governance that includes a heavy IT component is even harder. • Governance on a National scale that respects and accommodates the diversity of organizational entities, communities of interests, jurisdictions, levels and branches of government is unprecedented and almost impossible. • But, we are not shy about trying to do the impossible; and this is our task.

5. NIEM Governance Model *Full governance structure prior to implementation is not feasible. • Incremental Governance Model Development • Grow and evolve as the NIEM matures and as the diversity of organizations and exchanges grows. • Component based/ modular governance structure that supports pieces can be swapped out or added as needed. • The GJXDM and NIEM models suggest an approach.

6. Governance Development Focus • Focus only on specific business problems (specific information exchange) • Identify a business problem and the desired outcome. • For example: Identification of a small number of key exchanges of information desired by the Communities of Interest (the business problem) • Focus on the minimal set of processes necessary to solve the problem • Information Exchange Pilot projects would provide the business problem sets • Enrich the governance process with subsequent information exchange pilots

7. NIEM Pilot Approach • Start small • Limit the number of information exchanges, organizations, domains, etc.) • Identify two or three pilot information sharing projects and focus on developing the structures necessary to make those pilots succeed. • This practical, business case focused approach will force people to focus on “just enough governance” to get the job done. • Exchange pilot selection • Carefully selected to reflect the diversity of organizations currently participating in these efforts. • Identified exchange pilots • Intelligence Community: Terrorist Watchlist Person Data Exchange Standard (TWPDES) • DHS, Disaster Management: The National Capital Region Data Exchange Hub for first responders. (Initial focus is resource inventory, availability and request.) • Global Justice - Passing warrant information

8. Exchange Pilot Approach Summary • TWPDES offers the opportunity to solve a business problem. • It extends the ability to share terrorist information (in a narrow scope) to state, local, and tribal councils (or, it gets info to the cop on the beat and first responders). • Solution for the business problem: • Produce the Information Exchange Packages (IEPs) necessary to facilitate the key exchanges of information associated with the business problem (technical solution). • Governance is one enabling process to solve the problem • Our goal is "just enough Governance" to solve the problem. • We will enrich the Governance process with subsequent pilots.

9. NIEM Governance Structure

10. BloodTypeCode BloodTypeCodeType National Information Exchange Model NIEM Core (a collection of namespaces) Core: joint governance through NIEM Core Universal namespace Structuresnamespace The minimally supported set for all participating domains;universally understood; very stable; minimal or no subsetting Common namespace Requires central governance and reconciliation; but relatively stable Where the tiger teams operate Justice namespace • NIEM Participants: • Bring domain content to NIEM • Conform to NIEM NDR • Agree to NIEM governance policies and procedures • Participate in NIEM governance Healthnamespace Transportation namespace Domainspecific Homeland Security namespace Governed by XSTF-like committees that coordinate and cooperate with NIEM TC

11. BloodTypeCode BloodTypeCodeType National Information Exchange Model NIEM Core (a collection of namespaces) NIEM Universal Governance Core Universal namespace Structuresnamespace Common namespace NIEM Common Governance XSTF “like” Governance XSFT Governance Justice namespace Healthnamespace Domain Governance Domain Governance Transportation namespace Domainspecific Homeland Security namespace

12. NIEM Timeline 2005 2006 Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec GJXDM RC RC + NDR 3.0.3 3.1.1a/b 3.1a/b NIEM New features in NIEM 0.2 based on GJXDM 3.1 (NOT dependent on XSTF approval of 3.1) Spreadsheet marks GJXDM for NIEM partitioning Begin to buildtest msgs 1.0 RC 1.n RC ………….…………………………………………………………………………….. NIEM 1.n .xls 0.3 NIEM 0.1 0.2 1.0 feedback feedback NIEM workshops (in Jan and May) digest feedback collected by conference calls and NIEM Configuration Control Tool Based on refactoredGJXDM 3.0.3 Analyze dependencies, refactor, partition Domain groups use component mapping template (CMT) to consolidate and vet new content inputs. Pilot agencies test NIEM .1, .2, … .n and feedback Gather, analyze, vet, insert new content Tools ……………………………………………………….…………….………………. 0.2 SSGT 0.1 toward an IEPD Tool NIEM Tools 1.0 NIEM Tools 1.n Formal governance in place governance planning Interim NIEM governance RC = Release Candidate

13. Shaping NIEM 1.0 • Reviewing and providing Feedback on NIEM Deliverables • NIEM 0.n Releases • Technical Architecture • Content • Functional ConOps • Interim Governance Plan • NIEM NDR • Other Deliverables • NIEM Public Website: http://www.niem.gov • Establishing a NIEM Pilot Project • Developing and implementing NIEM exchange messages • Technology Evaluation • Adding Content • Participating on NIEM Workings, Committees, and Tiger Teams