1 / 33

Kshemendra Paul Chief Architect U.S. Department of Justice Kshemendra.paul@usdoj

DOJ Information Sharing Segment Architecture and NIEM 2.0 Update Presentation to the Data Architecture Subcommittee July 12, 2007. Kshemendra Paul Chief Architect U.S. Department of Justice Kshemendra.paul@usdoj.gov (202) 616-9676. Agenda. NIEM update

lynne
Télécharger la présentation

Kshemendra Paul Chief Architect U.S. Department of Justice Kshemendra.paul@usdoj

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. DOJ Information Sharing Segment Architecture and NIEM 2.0 UpdatePresentation to the Data Architecture SubcommitteeJuly 12, 2007 Kshemendra Paul Chief Architect U.S. Department of Justice Kshemendra.paul@usdoj.gov (202) 616-9676

  2. Agenda • NIEM update • DOJ Information Sharing Segment Architecture • What’s new in NIEM 2.0? • NIEM Tools

  3. Federated Domain Architecture

  4. Business Driven Information Exchanges

  5. NIEM 2.0 Release Status • RC1 was released on June 4th, 2007 • RC2 was released July 3, 2007 • Tools are in Beta now • See me if you want to be a Beta Tester • NIEM 2.0 will go Production on July 30th, 2007

  6. Why NIEM Now? 1.NIEM Is Tested, Ready, and in Production. 2. Documentation and Tools Are Available. 3. Training and Technical Assistance Are Available. 4. NIEM Governance is in Place and Working 5. Future Grants Will Mandate NIEM Conformance. 6. DOJ & DHS Internal Use NIEM Mandates 6. Reference IEPDs Are Being Developed. 7. NIEM Is a Key Means for Intergovernmental Information Sharing. 8. For Many, There is no Better Solution Available for Use Today.

  7. Next Steps for Using NIEM • Choose to make NIEM the basis for information exchanges • Adopt a service oriented architecture for your information systems • Arrange for training for your developers • Identify key exchanges with other organizations & jurisdictions • Use NIEM tools to develop exchange documentation • Design and implement the exchanges using web services

  8. Tools and Support Services • Documentation • Introduction to NIEM • Concept of Operations • User Guide • Naming and Design Rules • Standards • NEIM 2.0 • Documentation specs • Training and Technical Assistance • NIEM website • Training materials • Help desk and knowledge base • National and regional training • Tools • Subset & IEPD generator • Browse the model • IEPD Clearinghouse • Migration • More under development All available through www.niem.gov

  9. Sign up for NIEM News

  10. NIEM Helpdesk www.IT.OJP.Gov

  11. NIEM IEPD Clearinghouse www.IT.OJP.Gov

  12. NIEM and Enterprise Architecture

  13. NIEM (CTISS) Mission Focus Areas Color Coding Indicates Focus Areas for NIEM (CTISS)

  14. DOJ Segment Architectures

  15. As-Is DOJ Information Sharing Segment Architecture (ISSA) • Rooted in DOJ Mission • Assimilating Input / Guidance from DOJ Partners / Oversight • OMB / GAO / DOJ OIG • PM-ISE • DHS OCIO & OCIO • Legal, Security, Privacy • Global (NIEM & JRA), CJIS APB • Covers the entire architectural stack • Stronger in Business & Data, weaker in Performance & Technology • Descriptive & Informative • Meaningful both internally and externally

  16. To-Be DOJ ISSA • Focus on Specific Business Scenarios • Complete (Make Prescriptive) Information Sharing Architecture • Develop an exchange inventory (As Is and To Be) • Expand on policies and strategies • Internal (i.e., LEISP and OneDOJ) • External (i.e., National Information Sharing Strategy) • Add Details on Reconciliation of External Guidance • Develop Information Sharing Strategies for each Mission Segment • Leverage NIEM based federated query & link analysis for LE info sharing • Use NIEM as the model for defining exchange data elements • Develop reusable data elements and exchanges (IEPDs)

  17. Target Information Sharing Scenario Categories • CTISS/Fusion Center Interoperability (e.g. FBI FIG and JTTF) • Types of exchanges: Suspicious Activity Reports (SARs), Watch List, alerts and warnings • Supporting functions: Validating/processing SARs, link analysis, search • Law Enforcement Information Sharing Across LSTF Partners and Internally • OneDOJ/LEISP – R-DEx, N-DEx • CJIS/NLETS – NCIC, NICS, IAFIS/NGI, State CJIS • Cross-Federal LE Information Sharing • LE Wireless Access / SBU Mobility • Process Automation around the Justice Lifecycle • Identify Lead > Investigate Person/Organization > Arrest or Referral > Prosecute > Disposition/Fine, Incarceration > Release, Parole • Tactical Situation Assessment and Response • Intel information analysis and sharing with Federal and LST agencies

  18. Information Exchange Key Existing Exchange SAR IEPD Future SAR IEPDs ?? Suspicious Activity 911/PSAP Private Industry Dispatched LE Observer Baseline SAR Business Scenario Dispatch (CAD) System Intel System Record Mgt System (RMS) Law Enforcement Investigation or Intelligence Local Law Enforcement Law Enforcement Dispatch Fusion Center Systems State Designated Fusion Center Local Fusion Center* Other State Fusion Centers JTTF / FIG Information Sharing Environment (ISE) • The Local Fusion Center may refer to local intel analytical centers, UASIs, state regional fusion centers, etc..

  19. ISSA Perspectives As-Is To-Be Performance Performance Performance • Target Capabilities • Target Requirements • Implementation Guidance • and Recommendations Business Business Business Scenario Data Data Data Scenario 2 Scenario 1 Scenario 3 Service Service Service Technology Technology Technology Individual Scenario As-Is Views Feed Enterprise As-Is View • ISSA Reference Model • ISSA Reference Architecture • ISSA Service Patterns • NIEM Services • NIEM IEPDs Performance Enterprise Business Data Cross-Cutting Enterprise View Service Technology

  20. ISSA Enterprise View Growth Scenario 4 Enterprise-View Growth … Scenario 3 Scenario 2 Scenario 1

  21. ISSA Framework

  22. Information Sharing Governance

  23. NIEM 2.0 Changes

  24. NIEM 2.0 Changes • Re-modeled many components: Date, Time, Measure, & others. • Standard definition formats for (type, abstract, role, etc.) and many revised Core definitions. • Added new key word, usage description, and example fields for component discovery; and populated many. • Reviewed Core components for conformance with draft NDR 1.1 (re ISO Std 11179 naming/definitions). • Several namespace adjustments (e.g., justice, geo, others). • Differentiated Identifiers (IDs) from IdentificationTypes. • Added new URI representation term and URIType. • Integrated the Global JXDM 3.1beta. • Integrated ~30 resolved NBAC/NTAC NCCT issues. • Inserted ANSI-NIST Biometrics into new namespace. • Reintegrated domains to new Core. • Corrections to specializations and augmentations. • Many new code lists and updates to existing lists. • Integrated 26 FBI NDEx issues. • Fixed many technical concerns expressed by DNI. For more information on NIEM 2.0 updates, please reference the NIEM June 8th newsletter at: http://niem.gov/news.php

  25. NIEM Tools

  26. IEPD Development Lifecycle

  27. Tool Support for IEPD Development Lifecycle

  28. Information Exchange Modeling Tool

  29. Schema Subset Generation Tool

  30. Component Mapping Tool

  31. IEPD Tool

  32. Migration Tool

  33. Tool Migration Roadmap • Develop a federated repository • Web-based interactive user interface to support search/discovery of NIEM • Federation with DOD Metadata Registry and DISR • Further updates to migration tools • Support backwards compatibility of future releases of NIEM • Implementation support tools • Model management tools

More Related