210 likes | 284 Views
National Information Exchange Model. NIEM: Leveraging Global JXDM. Robust, mature framework Rich, flexible, and extensible Effective governance mechanism GXSTF joins government, industry, and practitioners Widespread recognition and use Substantially installed base
E N D
NIEM: Leveraging Global JXDM • Robust, mature framework • Rich, flexible, and extensible • Effective governance mechanism • GXSTF joins government, industry, and practitioners • Widespread recognition and use • Substantially installed base • Especially among state and local agencies • Multidisciplinary functionality
CORE Value Propositions • Facilitate growth of data model through harmonization of new data components • Coordinate independent project teams within DOJ and DHS • Provide effective support and assistance for practitioners • Facilitate discovery of reusable data components • Facilitate assembly of exchange packages • Future work will maintain compatibility with Global JXDM
Core U-Core Data Domain Intersection Density Domains Only
IntraXchg Pkg InterXchg Pkg Core U-Core Domains Only Data Domain Architecture
Institutionalizing Information Sharing • Business Information Exchange Reference Model • Incorporates XML Messaging, Federated Query, and Business Rule Execution to solve business problems
CORE Pilot Objectives • NIEM • Integrate DOJ and DHS data into NIEM • Implement compatible modularity • Enhance tools • Explore governance evolution • Explore framework evolution • Collaborative funding by DOJ and DHS
BTS Pilot Objective Border and Transportation Security Data Element Dictionary and XML-based Reference Schema CanonicalStandard Point-to-Point Mapping --- n(n-1) Canonical Standard Approach --- 2n
Governance 201 • Previous efforts have focused on “delegative governance” • XML namespaces to divide up data elements among “owners” • Ownership does not address overlaps or context • The GXSTF uses a “participative” approach • The Core must stay semantically accurate for the entire community • Domain owners form tiger teams on behalf of the community
U-Core COIs UC Committee Core User Organizations Governance View
Identifying DOJ Projects • U.S. Marshals Service • Justice Detainee Information System (JDIS) • U.S. Drug Enforcement Administration • Concorde Program • Federal Bureau of Investigation • National Data Exchange (N-DEx) • Regional Data Exchange (R-DEx) • Litigation Case Management • Law Enforcement Information Sharing Program (LEISP)
Identifying DHS Projects • Information Analysis and Infrastructure Protection • HSIN/JRIES • Border and Transportation Security (BTS) Pilots • BTS DED • BTS Net • Immigration and Customs Enforcement (ICE) Pilot
Information Sharing Use Case (1) • Markle Report—http://www.markle.org/ • “Creating a Trusted Network for Homeland Security” • Vignette 3 • Scenario—terrorists planning an attack using rail lines and chlorine gas
Terrorist Organization + name Rail Yard Zoo Incident + when + where + what + who Chemical Plant Terrorist Organization: + name: “Al Qaeda” Terrorist Chemical + name Chemical + name: “Chlorine” Person Information Sharing Use Case (2) • Agency X collects data • Using the DRM, Agency X creates metadata that describes this data in an unambiguous manner
LOB Indicators Intel InfrastructureProtection Vulnerability Capability Law Enforcement Lethal Agent Target Facility Organization Information Sharing Use Case (3) • Agency Y needs data to perform analysis • Agency Y discovers Agency X has the data it needs
Incident Report + who + what + when + where + activity Humint Report Threat Report Police Incident Infrastructure Incident Target Capability Critical Noncritical Chemical Plant Rail Yard Zoo Information Sharing Use Case (4) • Agency Y and Agency X assemble exchange packages
Intel Threat Report CIA States Industry Analysis Center Incident Rail Yard DHS InfrastructureProtection Incident Zoo DHS Incident Law Enforcement Chemical Plant DHS NCTC Law Analysis Center Incident Police Dept. Shared Space Information Sharing Use Case (5) • Data is exchanged
Shared Space Threat Report 1 Target: Rail Lines Capability: Chlorine Gas Incident 1: Zoo Incident 2: Police Incident 3: Chemical Incident 4: Rail Yard Information Sharing Use Case (6) • Data is associated in a shared space