# Presentation: 168169

## National Information Exchange Model (NIEM)Status UpdateApril 26, 2006

**Paul Embley (NIJ, XSTF Chair)**
**Kshemendra Paul (DOJ Chief Enterprise Architect, NIEM PM)**

## Agenda

- Vision for NIEM
- Goals & Objectives
- NIEM Defined in Context
- Benefits of NIEM
- Governance
- Organization Model
- Roles & Responsibilities
- Target Concept of Operations
- Upcoming Milestones
- State/Local/Tribal Involvement
- Risks
- Questions & Discussion

## Vision for NIEM

**NIEM will be the Standard, by Choice, for Government Information Exchange**
**Scope is Cross-Government**
- Local / State / Tribal / Federal
- Build from initial partnership led by DOJ, DHS, and Global Justice
- Expand to include Intelligence Community and then other aspects of Government
**Business Driven Focus on Data Layer Inter-Operability**
- Harmonize most commonly used data elements
- Organized by mission and interoperation requirements (domains and communities of interest - COIs)
- Clear inter-operation, not replacement, with existing standards
**Widespread Reuse of Information Exchanges to Reduce Cost and Improve Inter-Operation**
- Practitioner starting point is reuse of existing Information Exchanges
- Basis for vendors to build support for Information Exchange into products
**Championing Innovation in Information Exchange**
- NIEM anticipates major evolution in its lifecycle
- Change will be incremental, vetted, and evolutionary
- Change will be accompanied by a clear roadmap and value proposition

## Goals & Objectives for NIEM (CY 2006)

- Executive Sponsorship and Funding
- Deepen commitment and put in place accompanying structures
- Extend Federal participation through the ODNI Information Sharing Council (ISC)
- Secure enhanced multi-year funding commitment from Federal Stakeholders
- Enhance Current Organizational, Program, and Governance
- Refine, get buy-in, and launch current structures
- Put in place permanent management team
- Deliver NIEM into production via community process in 2006
- Executive communication including roadmap, value proposition, concept of operations
- v1.0 Product, including documentation, governance, and formal communications
- Migration strategy (jointly with Global Justice) for existing GJXDM Users
- Rollout Practitioner Outreach and Support (4Q CY2006)
- Leveraging partner’s outreach and communication channels

## NIEM Defined in Context

**Policy**

**Performance**

**Business**

**Data**

**Services**

**Technology**

**Operations**

**Scope**
**of **
**FEA**

**Information Exchange**
**Architectural Profile**

**Business** – Standard Information Exchanges
- Focus on reuse
- Discover / register exchanges via repository
**Data** – *Common Vocabulary* for Building Information Exchanges
- Organized by business domains
- Harmonize cross domain data
- Domain specific data management
- Interoperate with external standards
**Performance** – Measure Information Sharing
- Number of registered information exchanges
- Reuse of registered information exchanges
- Line of sight to/from data, business domains

**Focus of**
**NIEM**

**Influenced**
**By NIEM**

## Benefits Enabled by NIEM 

- Practitioners can understand one another
- Across levels of government
- Between mission areas
- Information Sharing Comes Built into Products and Applications
- Faster & Lower Risk Information Exchange, at Lower Cost
- Direct Ability to Frame Information Sharing in Business and Policy Terms

**Note – Full realization of benefits requires complementary efforts targeting other architectural layers**

## NIEM Organization Model

**NIEM Organization Model**

**Exec Steering Committee**
- Ken Bouche (GJXDM), Scott Charbo (DHS), Van Hitch (DOJ)**,**
- Kent Holtgrewe (DOJ),  TBD (HSOC). TBD (ODNI/IC)

**Federal Practitioner**
**Relations Director**

**Technical **
**Director**

**NIEM Executive Director**

**Business**
** ****Development Director**

**NIEM PMO Sponsorship**

**NIEM Technical Architecture **
**Committee (NTAC)**

**Technical Development**

**Training, Outreach, Technical **
**Assistance, Program Support**

**NIEM Business Architecture**
**Committee (NBAC)**

**State, Local, & Tribal **
**Practitioner Relations**
**Director**

**NIEM Committee for**** ****Issues, Requirements, and Quality (NCIRQ)**

**Help Desk**

**Ad-Hoc **
**Tiger Teams**

## Roles and Responsibilities - Committees

**NIEM Committee for Issues, Requirements, and Quality (NCIRQ)**
- Actionable practitioner advocacy
- Capture and frame requirements, bugs, and issues
- Working with data contribution sources through standards adoption processes
- Insure quality of releases and associated documentation
- Coordination, tracking, and implementation of priorities
**NIEM Business Architecture Committee (NBAC)**
- Domain architecture, IEPD template & registry, concept of operations, governance
- Umbrella group for Universal & Common Core Management
- Community of Interest Liaison
**NIEM Technical Architecture Committee (NTAC)**
- Core structure and architecture including Naming and Design Rules
- Coordinating architecture with domain partners to insure continued inter-operability
- Coordination with external data standards bodies
- Coordination with parallel information exchange efforts

## Roles and Responsibilities – Tiger Teams

**IEPD Template & Pilot Requirements**
- IEPD Template & Repository
- Structured definition of current Pilots
**Concept of Operations**
- Roles-based view of operation: Practitioner, Data Steward, Data Architect, Government Manager
- Define how business value is realized
**Governance**
- Define requirements for target governance structure
- Develop roadmap for evolution to meet target requirements
**Business Domains**
- Based on FEA BRM, put forward straw man structure harmonizing DOJ & DHS
- Iterate with Local, State, and other Federal stakeholders
**Issues and Planning**
- Identify, consolidate and frame all known issues for resolution
- With appropriate (development team, NTAC, NBAC, tiger teams) input develop recommendations
- Help drive resolution of 1.0 scope

## NIEM Straw Man Concept of Operations – Mainline Operational & Governance View

**Exec Steering Committee**

**NBAC**

**NCIRQ**

**Technical Development**

**Help Desk**

**NTAC**

**PMO**

- Requirements
- Issues / Ideas,
- & New Data

- Operational
- Issues

- Escalated Trouble
- Tickets

- Agenda

- Issues / Ideas

- Agenda

- Issues / Ideas

- Recommendations

- Recommendations

- Bugs

- Data Ingest / Release QC / Minor
- Requirements

- Roadmap
- &
- Tasking

- Recommendations

- Strategy, Policy, Funding,
- Vision,  Goals & Objectives

- Priorities

**Practitioners**

**Training, Communications, Program Support**

- Outreach

## Upcoming Milestones

**NTAG in Atlanta in May**
**Start community review of Tiger Team Work Products in May**
**NIEM 0.4 Released End of May**
**NIEM 1.0**
- Release for public comment (Beta) end of June
- Production release 4Q06
**NIEM 1.1**

## State/Local/Tribal Involvement

- List of those involved, and in what
- Mike Hulme – NTAC, IEPD Tiger Team co-lead, Global Tech Team
- Tom Carlson – NTAC, IEPD Tiger Team, Global Tech Team Lead
- Ken Bouche – Executive Steering Committee
- Paul Embley – NTAC, NCIRQ co-lead, Global Tech Team
- Scott Came – NTAC, Global Tech Team
- Andrew Owen – Global Tech Team
- Scott Fairholm – NBAC co-lead
- Dave Roberts – Concept of Operations
- Ashwini Jarral – IEPD
- Winfield Wagner – IEPD
- Paul Wormeli – Governance
- Multiple individuals from DHS, DOJ, DNI

## Risks

**Schedule** – Aggressive dates with need to maintain quality while building processes and community
**Growth** – Very large and have a very diverse group of stakeholders
**Funding** – Currently, no dedicated funding
**Federal & National Balance** – need to mandate with some constituents while encouraging voluntary participation by those not “mandatable”
**Other Initiatives** –large number uncoordinated initiatives and standards
**GJXDM** – how do we migrate existing users, education
**TA & Training** – need a plan & resources

## Questions & Discussion