1 / 16

National Information Exchange Model (NIEM) Status and Future September 6, 2006

National Information Exchange Model (NIEM) Status and Future September 6, 2006. Kshemendra Paul NIEM Program Manager Chief Enterprise Architect US DOJ. Web Site ( www.niem.gov ) Activity. Web site activity for the period from June 1, 2006 to August 31, 2006

rosa
Download Presentation

National Information Exchange Model (NIEM) Status and Future September 6, 2006

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. National Information Exchange Model (NIEM)Status and FutureSeptember 6, 2006 Kshemendra Paul NIEM Program Manager Chief Enterprise Architect US DOJ

  2. Web Site (www.niem.gov) Activity • Web site activity for the period from June 1, 2006 to August 31, 2006 • Downloads refer to the 0.3, 1.0 Beta 1, and 1.0 Beta 2 release packages • Average hits / day • 1,842 pre-beta • 10,923 currently • Average downloads / day • 11 pre-beta • 160 currently

  3. What is NIEM? • 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 • Publish and discover reusable information exchanges • Provide public domain standards and technical tools to support the above • Provide training, technical assistance and implementation support services for enterprise-wide information exchange

  4. Built on the Global JXDM • NIEM is deeply rooted in the GJXDM and Global Justice Community, and committed to maintaining and growing that relationship • The Global Justice XML Data Model (Global JXDM) has • A robust, mature framework that is rich, flexible, and extensible • An effective governance mechanism • Widespread recognition and use, especially among state and local agencies • NIEM builds on the demonstrated success of the GJXDM • NIEM is rooted in the GJXDM (GJXDM 3.0.3) • The Global JXDM will form the justice domain of NIEM (the jxdm namespace) • The GXSTF will continue to represent the Global JXDM within NIEM

  5. NIEM Goals and Objectives • Deliver NIEM • Publish NIEM 1.0 • Ramp up and implement governance • Develop validated and vetted product roadmap • Catalyze NIEM adoption and usage with stakeholders • State/Local/Tribal practitioners • Federal Agency information technology initiatives • Authoritative bodies that can sponsor reference information exchanges for their COI • Support the program manager – Information Sharing Environment • National priority counter-terrorism information exchange standards leveraging NIEM • Deepen partnerships with communities of interest • Update and extend DOJ / DHS MOA to other federal agencies & their state/local/tribal partners • Finalize and implement NIEM / GJXDM convergence • Become the standard, by choice, for government information exchange • Follow information exchange requirements from current to future stakeholders • For example, fusion centers as an information exchange nexus

  6. Fit With Federal Enterprise Architecture • 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 Information Exchange Architectural Profile Policy Performance Influenced By NIEM Business Focus of NIEM Scope of FEA Data Services Technology

  7. NIEM Federated Domain Architecture Data component - fundamental building block of NIEM. Data components are either Universal, Common, or Domain-specific. Universal components - data components commonly understood and reused among all domains; subject to NIEM governance. Common components - data components understood and potentially reused between two or more domains; subject to NIEM governance. Domain-Specific - components managed by a specific Community of Interest (may be reused with COI, available for reuse by others).

  8. Business-driven Approach Disaster Management Homeland Security BRM Border & Transport Security Emergency Response LoBs Dispatch Services Person Screening Subfunctions Business processes many-to-many IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD IEPD Library Consistent Classification Independent Development NIEM

  9. Organization Model: External View

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

  11. Status • NIEM 1.0 Beta 1 was released on June 30, 2006 • Structural enhancements • Updated tools • New documentation (Introduction, Concept of Operations) • Beta releases leading to 1.0 Release Candidate • NIEM 1.0 Beta 2 was released on August 8, 2006 • Content insertions from pilots • NIEM 1.0 Beta 3 to be released in early September • Content insertions from pilots • Updated documentation including Naming and Design Rules • Governance • The NBAC will be engaged with Paul Embley as lead • Tom O’Reilly on board as Director of Outreach and Communications • The NTAC will be engaged with Tom Clarke as lead

  12. Lessons Learned • GJXDM Usage Base and Governance Structure Enables NIEM • Governance and policy are the critical path, not technology • They are both also really hard • Process cannot replace relationships and trust • Balance between: DC and the Field; academic/architectural and operational • We are making good progress • State and local involvement as first rank partners • As practitioners, stakeholders, thought leaders • Role of industry, academic partners • Success = adoption and use • Never forget that the best way to get this is the simplest – listen!

  13. We Need Your Help • Number one priority – engagement from practitioners • Pilot projects – analysis through to implementation • Number two priority – feedback on products • NIEM beta 2 / 3 • 1.0 release candidate • Tools – available now • Introduction, Concept of Operations, & Naming and Design Rules • Number three priority – XSTF “mentoring” of NBAC • Global is a community of communities • NIEM extends one more level • Hard won expertise within GXSTF will jump start NBAC effectiveness

  14. Next Steps • NIEM 1.0 Release Candidate in October • Scale Up Governance Activities • Catalyze Conversion of GJXDM IEPDs by Authoritative • 54 IEPDs in OJP IEPD Clearinghouse (http://it.ojp.gov/iepd/) • PM-ISE national priority target outcomes • Counter-Terrorism Information Sharing Standards • Encourage and seed other independent adoption and use by COIs • Sponsored by Authoritative Bodies within a Communities of Interest • Driven by Practitioners with specific (inter-domain) information exchange requirements • Technical support • Help desk • Expand FAQ topics • Develop NIEM training materials • Expand communications and outreach efforts • Within existing COIs • Follow adoption to new domains and COIs • Executive, legislative, and judicial branches at the State, Local, Tribal and Federal levels

  15. Overview of NIEM Related Presentations • Thursday 9:00 a.m.–10:15 a.m. • NIEM and GJXDM—What Does This Really Mean? • Paul Embley, NIJ, DOJ • Thomas O’Reilly, Director of Business and Outreach, NIEM Program • Thursday 10:45 a.m.–12:30 p.m. • NIEM Exchanges, Real-Life Examples • Thomas O’Reilly, Director of Business and Outreach, NIEM Program—Moderator • Bard Laabs, Regional Data Exchange (R-DEx)/Automated Regional Justice Information System (ARJIS), San Diego Police Department • Tim Grapes, Evolution Technologies, Inc.–Disaster Management eGov Initiative, DHS • Anthony Hoang, Office of the Director of National Intelligence, DHS • Thursday 12:30 p.m.–1:30 p.m. • Lunch on the Lanai • Vance Hitch, Chief Information Officer, DOJ • Thursday 1:30 p.m.–3:15 p.m. • Building a NIEM IEPD—the NIEM IEPD Lifecycle and Tools • John Wandelt, Senior Research Scientist, GTRI • Mark Kindl, Research Scientist, GTRI

  16. Conclusion • For more information visit the NIEM web site (http://www.niem.gov) • Contact NIEM by email at information@niem.gov • Questions and Discussion

More Related