Law Enforcement National Data Exchange An Overview of

  • Slides: 25
Download presentation
Law Enforcement National Data Exchange An Overview of the N-DEx Program IEPD Development September,

Law Enforcement National Data Exchange An Overview of the N-DEx Program IEPD Development September, 2006 1

N-DEx MISSION N-DEx will provide law enforcement agencies with a powerful new investigative tool

N-DEx MISSION N-DEx will provide law enforcement agencies with a powerful new investigative tool to search, link, analyze and share criminal justice information such as, incident/case reports, incarceration data, and parole/probation data on a national basis to a degree never before possible. 2

Two Complementary Tools Approximately 100 connections R-DEx WA VA LIn. X Regional Sharing Systems,

Two Complementary Tools Approximately 100 connections R-DEx WA VA LIn. X Regional Sharing Systems, Managed Locally CA PA ARJIS JNET Nor. West Structured & Unstructured Data Protected SSL Point to Point Connection, Web Services Standard Interface Bedford County VA Boston PD Miccosukee Tribal PD CJISWAN/LEO Structured Data Only FL Dept. LE FUTURE Regional Partitions 200, 000 possible users National Repository Entity Resolution & Correlation N-DEx GA State Police One. DOJ Structured & Unstructured Data ATF NY State Police Mid-West So-West Federated Search Across Systems Phoenix PD Others Mid-Atl N-DEx Local Systems, Contribute at own pace R-DEx Fed DHS/USSS DOJ DEA DHS/CBP NCIS DOI One. DOJ Web Services Standard Interface USMS FBI BOP Regional Systems – Grant funded, locally hosted and maintained, national standards; accessing DOJ data through R-DEx. Partnering Strategy N-DEx – Federally funded, federally hosted & maintained (CJIS). Multi-agency federal, state and local data available 3 to the authorized user.

Current Data Dictionary n n Reviewed a large number of Incident reports from around

Current Data Dictionary n n Reviewed a large number of Incident reports from around the country. NIBRS 4

Early work n n Fixed field CSV XML Others 5

Early work n n Fixed field CSV XML Others 5

XML only n n n During early piloting it was discovered that working with

XML only n n n During early piloting it was discovered that working with CSV, or fixed field and doing the mapping at CJIS proved to be a failure. Agencies understand their data. GJXDM was a national justice standard and the decision was made to use the GJXDM. 6

NDEx XML Bundle n n n Beta Version 1. 0. 4 From GJXDM 3.

NDEx XML Bundle n n n Beta Version 1. 0. 4 From GJXDM 3. 0. 2 Data element user guide, data dictionary. Problems discovered during test and construction. Limited distribution 7

Incident IEPD @ SEARCH. org n n n NDEx participated in the development of

Incident IEPD @ SEARCH. org n n n NDEx participated in the development of the incident IEPD. NDEx was used as the base for Incident IEPD. NDEx will be able to work with the Search Incident IEPD now and in the future, if kept current. 8

Next Steps n n n NDEx working on first public IEPD Will be based

Next Steps n n n NDEx working on first public IEPD Will be based on NIEM The data elements will be refined Style sheets will be included in the IEPD Tools for mapping 9

NDEx IEPD n n n n n GTRI working with NDEx on creation. Data

NDEx IEPD n n n n n GTRI working with NDEx on creation. Data element refinement 8/7 -21/06. Domain Modeling 8/21 -26/06. Mapping 8/21 -9/2/06. Schema Building 9/4/06 -10/21/06. NIEM public release 9/30/2006. LEXS 3. 0 release 10/31/2006. Packaging 10/21/2006 -10/31/2006. Will be completed 11/17/2006. 10

Future n n n December of 2006 or January of 2007 NDEx will start

Future n n n December of 2006 or January of 2007 NDEx will start working on next release of the NDEx IEPD. Refinements and comments from the testing of the NDEx NIEM IEPD will be incorporated. Summer 2007 NDEx operational IEPD due. 11

N-DEx Data Standards Participation N-DEx PMO actively participates in the following GJXDM/NIEM groups: •

N-DEx Data Standards Participation N-DEx PMO actively participates in the following GJXDM/NIEM groups: • National Information Exchange Model (NIEM) Stakeholders • NIEM Technical Architecture Committee (NTAC) • NIEM Business Architecture Committee (NBAC) • NIEM Committee for Issues, Requirements, and Quality (NCIRQ) • Global Justice XML Data Model (GJXDM) • Global Advisory Committee • Global Justice XML Structure Task Force (XSTF) • GJXDM Training and Technical Architecture Committee (GTTAC) • GTTAC IEPD Subcommittee • Department of Defense (DOD) • DOD Counterintelligence Information Technology Council (CIC) 12

N-DEx Acquisition Timeline SME Meeting Executive CONOPS Review APB Process Task Force Executive CONOPS

N-DEx Acquisition Timeline SME Meeting Executive CONOPS Review APB Process Task Force Executive CONOPS Review APB Executive CONOPS Approval SME Meeting Scenario Review Full CONOPS Task Force Executive CONOPS Review Task Force Meeting Full CONOPS INSH Subcommittee Full CONOPS Review APB Working Groups Due Diligence Period to include SMEs/Task Force Fall Working Group Fall INSH Subcommittee Fall APB Privacy Act Council APB September October November December January February March April May June July August September October November December January 2005 2006 2006 2006 2007 Acquisition Process Establish Integrated Solutions Team Release RFI Draft PIA sent to OGC and DOJ Finalize SOO And RFP Conduct Market Research Sessions Privacy Release System RFP of Records Notice Due Diligence Period Award Contract Evaluate Proposals Final Proposals Due Note: Timeline may vary based upon number of vendors participating and acquisition approval process 13

N-DEx Program Timeline 14

N-DEx Program Timeline 14

Phased Agency Deployment Agencies: Prototype activities will support the following program initiatives: • Support

Phased Agency Deployment Agencies: Prototype activities will support the following program initiatives: • Support and establish the N-DEx data set and data submission guidelines through GJXDM/NIEM • Support the evolution of N-DEx business and policy rules through the APB • Provide law enforcement active participation and submission/validation of existing RMS data. 15

Key Assumptions n n n The Key Success Factor - ensuring that N-DEx meets

Key Assumptions n n n The Key Success Factor - ensuring that N-DEx meets the real-world needs of law enforcement N-DEx will be deployed incrementally based on user priorities The effectiveness of N-DEx is dependent upon widespread participation N-DEx is an information sharing system, not a statistical reporting system N-DEx is not an intelligence system Management of data shared in N-DEx will remain with the LEA that provided it An objective of the N-DEx implementation is to reduce the points of integration from a data and functionality perspective N-DEx will offer a range of options for LEAs to integrate their systems Existing standards, systems and networks will be leveraged MOUs will be the mechanism N-DEx will use to document agreements between N-DEx and its information-sharing partners N-DEx will be designed and built in consultation with its local, state, tribal and other federal partners in a collaborative manner Only data classified as Sensitive but Unclassified (SBU) or below will be permitted within N-DEx 16

N-DEx Services and Capabilities n Services relate and organize data into useful information for

N-DEx Services and Capabilities n Services relate and organize data into useful information for searching and querying in support of investigations and analyses: n n n Entity Resolution Entity Correlation Incident/Case Correlation Service Automated Processing Service Capabilities that users can employ to benefit from the vast amounts of information available to the system: n n n Search Subscription Visualization Analytical/Reporting Collaboration Notification 17

N-DEx Concept 18

N-DEx Concept 18

N-DEx Data Integration • N-DEx provides view of full record • No need to

N-DEx Data Integration • N-DEx provides view of full record • No need to “pull” from the source • Example - incident reports from RMSs • N-DEx is an index/pointer • N-DEx can request a “pull” from source • Example – R-DEx • N-DEx not aware of their information • Legacy transactional system that must be queried • Example - NCIC and III (via NCIC) 19

Non-Interactive Data Source Examples 20

Non-Interactive Data Source Examples 20

N-DEx Functional Integration n End-User Browser n n LEA users will be provided the

N-DEx Functional Integration n End-User Browser n n LEA users will be provided the ability to access N-DEx directly through a web browser Web Services n n All N-DEx user level capabilities will be available to external LEA systems through web service interfaces Example - RMS or regional system may wish to integrate N-DEx capabilities into the local system's user interface 21

N-DEx Functional Integration 22

N-DEx Functional Integration 22

Network Connectivity n n CJIS will deliver N-DEx on the CJIS Wide Area Network

Network Connectivity n n CJIS will deliver N-DEx on the CJIS Wide Area Network (WAN) Connectivity will be through any means authorized per CJIS Advisory Policy Board (APB) policies/guidelines and state policies Methods of connectivity to the CJIS WAN from secondary locations (e. g. , NLETS, RISS. NET, state network, etc. ) LEAs will also be able to connect to N-DEx via secure Internet connections using the LEO system 23

Los Angeles n Level of effort to incorporate the N-DEx XSD to participate in

Los Angeles n Level of effort to incorporate the N-DEx XSD to participate in testing. • Mapped to N-DEx XSD • Successfully submitted data for validation • 800 man hours committed to N-DEx • Current near real-time submissions via CJIS WAN 24

Questions SSA Edward C. Waigand N-DEx Program Support Manager Criminal Justice Information Services Division

Questions SSA Edward C. Waigand N-DEx Program Support Manager Criminal Justice Information Services Division Policy, Administrative, & Liaison Branch 1000 Custer Hollow Road Clarksburg, WV 26306 (304) 625 -4232 ewaigand@leo. gov 25