P1246341504lcTSi

1
Law Enforcement National Data Exchange An
Overview of the N-DEx Program IEPD
Development September, 2006
2
N-DEx MISSION
3
Two Complementary Tools
Approximately 100 connections
N-DEx
Local Systems, Contribute at own pace
R-DEx
Regional Sharing Systems, Managed Locally
VA
CA
PA
WA
Bedford County VA
Phoenix PD
Boston PD
Miccosukee Tribal PD
LInX
ARJIS
JNET
Others
Structured Unstructured Data
Protected SSL Point to Point Connection, Web
Services Standard Interface
NorWest
Mid-Atl

CJISWAN/LEO
Mid-West
Mid-West
So-West
Structured Data Only
National Repository N-DEx
200,000 possible users
Federated Search Across Systems
FUTURE
Entity Resolution Correlation
Regional Partitions
OneDOJ
Structured Unstructured Data
DHS/USSS
R-DEx Fed
DOJ
NCIS
DHS/CBP
DOI
OneDOJ
DEA
ATF
Web Services Standard Interface
USMS
BOP
Partnering Strategy
FBI
N-DEx Federally funded, federally hosted
maintained (CJIS). Multi-agency federal, state
and local data available to the authorized user.
Regional Systems Grant funded, locally hosted
and maintained, national standards accessing DOJ
data through R-DEx.
4
Current Data Dictionary

• Reviewed a large number of Incident reports from
  around the country.
• NIBRS

5
Early work

• Fixed field
• CSV
• XML
• Others

6
XML only

• 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.

7
NDEx XML Bundle

• Beta Version 1.0.4
• From GJXDM 3.0.2
• Data element user guide, data dictionary.
• Problems discovered during test and construction.
• Limited distribution

8
Incident IEPD _at_ SEARCH.org

• 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.

9
Next Steps

• 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

10
NDEx IEPD

• 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.

11
Future

• 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.

12
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)

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

16
Key Assumptions

• 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

17
N-DEx Services and Capabilities

• Services relate and organize data into useful
  information for searching and querying in support
  of investigations and analyses
• 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
• Search
• Subscription
• Visualization
• Analytical/Reporting
• Collaboration
• Notification

18
N-DEx Concept
19
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)

20
Non-Interactive Data Source Examples
21
N-DEx Functional Integration

• End-User Browser
• LEA users will be provided the ability to access
  N-DEx directly through a web browser
• Web Services
• 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

22
N-DEx Functional Integration
23
Network Connectivity

• 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

24
Los Angeles

• 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

25
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 [phone] ewaigand_at_leo.gov