1 / 23

James Feagans, DOJ and Michael Daconta, DHS July 26, 2005

James Feagans, DOJ and Michael Daconta, DHS July 26, 2005. James Feagans, Department of Justice. The Exchange Problem. XML exchanges are easy … too easy. SOA emergence will increase the # of XML exchanges. Without a framework for reuse, we will create XML Stovepipes .

ash
Download Presentation

James Feagans, DOJ and Michael Daconta, DHS July 26, 2005

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. James Feagans, DOJ and Michael Daconta, DHS July 26, 2005 James Feagans, Department of Justice

  2. The Exchange Problem • XML exchanges are easy … too easy. • SOA emergence will increase the # of XML exchanges. • Without a framework for reuse, we will create XML Stovepipes. • NIEM is striving towards National information sharing • Extending “grass roots” “bottom-up” approach by Global Justice Community • Synergy with the Federal Enterprise Architecture Data Reference Model (Federal framework supporting a national approach)

  3. NIEM Program Vision Practitioners at all levels of government share accurate, complete, timely and appropriately secured information to enable informed decision-making to ensure homeland security and public safety.

  4. NIEM Program Goals • Overcome obstacles to information sharing between all forms of government • Improve Shared situational awareness and collaboration • Leverage technology/lessons learned/success • To improve internal processes • To improve external sharing and productivity • Support National information sharing programs • Implementation of National FEA Data Reference Model • Operational efficiency and effectiveness • Timely Detection, Prevention, and Response to Public Safety, Terrorism, Criminal Activity and other Emergencies

  5. NIEM Program Goal Drivers NIEM Program Goal Drivers • From all Levels of Government, NIEM Leverages Re-Use of: • - Existing Standards • - Technology • - Existing Infrastructure • - Knowledge/Experience • - Organizational Interactions and Personal Relations (Culture) • (Established environment to capitalize on existing IT investments from all levels of National government) • NIEM Driver = COLLABORATION

  6. NIEM Program Principles TriggerEvent Organization A Message Organization B ResultingEvent • Trigger Event Begins with Real People • Built off existing infrastructure • Information exchange occurs at key decision points in the process • Quickly determine who makes the decisions allowing management (at all levels) to implement decisions • Technical solutions driven by functional requirements • Resulting event effects Real People

  7. Complex types 400 Simple types 150 Properties 2,209 Total Components 2,754 NIEM: Leveraging the Global Justice XML Data Model Content Release Version 3.0 Metadata 116 Misc 177 Org 94 Location 178 Activity 1216 Property 397 Person 543

  8. Major Domains Homeland Security Public Safety CORE Law Enforcement,Intelligence, etc. Courts, Probation, Parole, Corrections, etc. Emergency Management,Border Security, etc. UNIVERSALCORE CORE Welfare,Juvenile Justice,Education, etc. CORE PublicHealth, etc. Secondary Domains etc. Other Domains The Concept of Core

  9. What Makes a Core Component? • The scope of data for inclusion into the NIEM will cover multiple business domains • Initial NIEM domain examples: • Law Enforcement • Emergency Management • Intelligence • Border Security • Courts • Probation • Parole • Corrections • Public Health • Fire • EMS • Emergency Management • Disaster Management

  10. Core Data Type Example

  11. NIEM Example Exchange <amber-doc:AmberAlertDocument xmlns:amber-doc="http://www.it.ojp.gov/jxdm/3.0.2/amber-alert-document" xmlns:amber="http://www.it.ojp.gov/jxdm/3.0.2/amber-alert" xmlns:j="http://www.it.ojp.gov/jxdm/3.0.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > <j:DocumentDescriptiveMetadata> <j:DocumentID> <j:ID>AA123</j:ID> </j:DocumentID> </j:DocumentDescriptiveMetadata> <amber:AmberAlert> <amber:AmberAlertID></amber:AmberAlertID> <amber:AmberAlertTransmissionDate>2004-11-15</amber:AmberAlertTransmissionDate> <amber:AmberAlertTransmissionTime>09:15:30</amber:AmberAlertTransmissionTime> <amber:AmberAlertStatus>Active</amber:AmberAlertStatus> <j:CaveatText>Beware of general danger regarding this situation.</j:CaveatText> <amber:AmberAlertLanguageText>English</amber:AmberAlertLanguageText> <amber:AmberAlertContactInformation> <j:ContactEmailID> <j:ID>jsmith@mayberry.ci.us</j:ID> </j:ContactEmailID> <j:ContactWebsiteID> <j:ID>http://alerts.mayberry.ci.us</j:ID> </j:ContactWebsiteID>

  12. National Information Exchange Model Concept Information ExchangePackage Descriptions (IEPDs) Virtual Object Reuse Repository – types, properties, business containers, msg constructs, service metadata, … AmberAlert<AmberAlert> Transport<Transport> HomelandSecurity Health IEPDTemplate EDXL_Msg Core Universal-Core EmergencyManagement Transportation Justice IEPDs Semanticallyconsistentacross alldomains New IEPDs Tools, methods, mapping, process, training,etc. New IEPDs New components CollaborativeTools (for distributedconsensus) GovernanceBodies ExchangeRequirements New reusablecomponents

  13. NIEM: Current Status (1) • Approved by the DOJ/DHS CIO’s February 2005 • DHS/DOJ Announced on February 28th, 2005 • DOJ/DHS CIO Memorandum of Agreement • Key points: • Rename GJDXM to signify broader scope • Add DHS/DOJ Content • Rework Model and Tools (support modularity) • Status: Signed • Regular National NIEM PMO Meetings • Identify pilot projects and explore the expansion of IC involvement • DHS State and Local Government Coordination and Preparedness Office (SLGCP) Innovative Technology Evaluation Pilots (ITEP) are participating. • NASCIO promoted NIEM in recent Congressional call to action on Information Sharing

  14. Current Status (2) • Developing Project Management Plan and National Joint Governance Structure • Adding new content to the public information NIEM website, cloned GJXDM, supporting tools and development web site. • Pilot Progress: • Completed Workshop on DHS HSARPA BTS Pilot April 11-13 Phoenix, AZ • Immigration and Customs Enforcement (ICE) mapping Enterprise Logical Data Model to NIEM. • Disaster Management Initiative adds NIEM to their Standards Process • Adding NIEM Content for FBI, DEA, ATFE, USMS, Case Management-Litigation, and EOUSA. • National Institute of Standards and Technology (NIST) Partnership

  15. Overall NIEM Development Guiding Principles Intelligent Capabilities/Services { • National Services Broker • National Consensus Framework • Supports Business Modularity • Flexible and Agile Information Exchange Service Capability across all Levels of Government • Performance Metrics Continuation 3 • Incremental Pilot Development with Modular Approach: • Business Driven • Harmonized/Integrated Governance and Technical Implementation Module “Fully Loaded Plug & Play” • Reduce Transition Risk from Planning to Operational • Produce Quantifiable Return on Investment for each milestone (pre-release) { Scaling 2 Level of Complexity { • Initial Governance as a Collaborative Partnership • Leverage Expertise • Build on Current Success • Prove Concepts through Pilot Projects • Minimize Risk of Rework • Provide Benefit to Users Proof of Concept 1 Time

  16. Implementation Approach Requirements from Global domain Global XSTF GJXDM (operational) 3.N 3.0.2 3.0.3 3.0.0 3.1.0 Feedback ATFE, ICEcontent other content, features, capabilities as appropriate U.S. Marshals, BTSService content initialize and ID Core NIEM Steering Committee Key Decision Points (KDP’s) NIEM (tactical) 0.N 1.0 0.2 0.1 Business Process Modularity Governance/ TechnologyModule Insertion Lessonslearned Newrequirements Requirements frombusiness domains set-up experimental test bed NIEM (strategic) Explore good ideas: new metadata, scope/context, taxonomies/categories, federated NIEM repository, additional domains, Web Service interfaces, collaborative tools, OWL representation, …

  17. Key Objectives in Phases I/II Global XSTF Global JXDM (operational) 3.N 3.0.2 3.0.3 3.1.0 merge NIEM Steering Committee initialize NIEM Track I (tactical) 0.N 1.0 0.2 0.1 NIEM Track II (strategic) test bed Phase 1 Phase 2 Continuation Proof of Concept Scaling • Build on layers of incremental development • success • National Consensus Framework • (modularized National governance structure) Technical service oriented implementation • approach • Collaborative technologies • Information Exchange Package Automation • Performance metrics • Initial Governance as a Collaborative Partnership • Leverage Expertise • Reuse GJXDM Operational Domain • Prove Concepts through Pilot Projects • Minimize Risk of GJXDM Rework • Provide Benefit to GJXDM Users • Collaboration with Stakeholders executing • NIEM Incremental pilot development SOA • modular approach. • (participatory approach through “joint • consensus building – SME’s across • business domains)

  18. Operational and Tactical Integration Continue with GJXDM as is Global XSTF GJXDM 3.N NIEM 1.0 U-Core Justice domain+ NIEM impact evaluate for: Core HomelandSecurity Justice NIEM Steering Committee NIEM (tactical) XSTF DMWG 1.0 Other National Consensus Framework

  19. NIEM Schedule (DRAFT)

  20. NIEM Tiger Teams and Initial Messages • Governance: National Consensus Framework • Discussions with MIT and Harvard • Component Mapping Template (next slide) • Team testing template • Drafted recommendations/modifications to GTRI • Naming and Design Rules • Evaluating GJXDM NDR • Participating in Federal NDR • Concept of Operations • Establishing Team • Messaging Infrastructure and Facilitation • Establishing Team • Initial NIEM Messages • Terrorist Watchlist Person Data Exchange Standard 2.0 • Emergency Management Resource Message • Facilitation planning under way for other messages

  21. Component Mapping Template

  22. National Collaboration Success NIEM Development is Built on a Unified National Approach with “Joint Consensus” • NIEM PMO Comprised of National Representation • NIEM Facilitates Early Adopter Participation • NIEM Promotes “Participative approach vs Delegative approach” - National “Service Oriented” Modular Development - National Consensus Framework (Modular Governance) • Success = Subject Matter Experts (Business Driven) • Executing Collaboration at an “UNPRECIDENTED” National Level

  23. More Information at … NIEM Public Website: http://www.NIEM.gov Total # of hits in one month 57,558

More Related