1

Law EnforcementNational Data Exchange

An Overview of the N-DEx ProgramIEPD Development

September, 2006

2

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.

N-DEx MISSION

3

N-DExN-DEx

Two Complementary Tools

National Repository

N-DEx

National Repository

N-DEx

DOJ DHS/CBP

Bedford County VA

Phoenix PD Boston PD Miccosukee Tribal PD

NCIS DOI

Structured Data Only

Local Systems, Contribute at own pace

200,000 possible users

OneDOJ

DHS/USSS

Entity Resolution & Correlation

Structured & Unstructured Data

CJISWAN/LEOMid-WestMid-West

R-DExR-DEx

Protected SSLPoint to Point Connection,

Web Services Standard Interface

Protected SSLPoint to Point Connection,

Web Services Standard Interface

LInX

CACA

ARJIS

PAPA

JNET Others

Regional Sharing Systems, Managed Locally

VAVA

Approximately 100 connections

WAWA

Federated Search Across Systems

NorWestNorWest Mid-AtlMid-Atl

So-WestSo-West Mid-WestMid-West

Regional Partitions

R-DEx Fed

R-DEx Fed

ATF

USMS BOP

DEA

FBI

OneDOJStructured & Unstructured Data

Web Services Standard Interface

Regional Systems – Grant funded, locally hosted and maintained, national standards; accessing DOJ data through R-DEx.

N-DEx – Federally funded, federally hosted & maintained (CJIS). Multi-agency federal, state and local data available to the authorized user.

Partnering Strategy

FUTURE

NY State Police

FL Dept. LE

GA State Police

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

N-DEx Data Standards Participation

13

N-DEx Acquisition Timeline

July

2006

AcquisitionProcess

APBProcess

Establish Integrated Solutions

TeamConductMarket

Research Sessions

Finalize SOO

And RFP

Release RFP

FinalProposals

Due

AwardContract

Task Force

ExecutiveCONOPSReview

SME Meeting

ExecutiveCONOPS Review

Task Force

ExecutiveCONOPSReview

APBExecutive CONOPS Approval

SME Meeting

Scenario Review

Full CONOPS

TaskForce

MeetingFull

CONOPS

APBWorking Groups

INSHSubcommitteeFull CONOPS

Review FallINSH

Subcommittee FallAPB

FallWorking

Group

September

2005

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

APB

Due Diligence Period

to includeSMEs/Task Force

Due Diligence

Period

EvaluateProposals

Release RFI

Note: Timeline may vary based upon number of vendors participating and acquisition approval process

Privacy Act Council

Privacy System

of Records Notice

Draft PIA sent to OGC and DOJ

14

N-DEx Program Timeline <Process Name>

<Fun

ctio

n>

Phase II – Second Deployment

* Increasing System/Fail-over Capabilities * Add data sets Incarceration data and Arrest/Booking Data* Correlation (Advanced) * Visualization (Advanced)* Subscription/Notification (Advanced)* Analytical/Reporting (Basic)* 100,000 Users

Phase III – FOC

* Implement Fully Redundant System and Environments* Add Data Sets-Probation/Parole Data * Enhancements and Modifications previously deployed* Analytical/Reporting (Advanced)* Rolled out nationally to participants* 250,000 Users

O&M

3 42 2

Phase I – Initial Deployment

434 13 143 1

* Sharing of Incident/Case Report Information* Search * Correlation (Basic)* Visualization (Basic)* Subscription/Notification (Basic)* Limited Fail-Over Capability* Initial support 50,000

1 2 2

FY 08FY 07 FY 09 FY 10

15

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.

Phased Agency Deployment

West Coast East Coast Arizona NebraskaLas Vegas, NV Alabama Colorado NevadaLos Angeles County, CA Delaware Florida OhioOrange County, CA Georgia Illinois OklahomaSan Diego, CA Maryland Kansas Pennsylvania

South Carolina Michigan Rhode IslandFederal Agency Tennessee Minnesota Texas Air Force OSI Virginia Missouri

West Virginia

First Phase Second Phase

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

Franklin CountyAuto Thefts

January

0600- 1000-1400- 1800- 2200- 0200-1000 1400 1800 2200 0200 0600

987654321

February

0600- 1000-1400- 1800- 2200- 0200-1000 1400 1800 2200 0200 0600

987654321

Auto TheftPickaway, Fairfield, Union, Licking,

2004 - 2005

Time

#

2

Corruption Case XYZ

SelectSelect

OKOKShare:

Do Not Share:

Conditional Share Options:

Name: John England

SSN: 123-45-6789

Sharing Attributes

Subscribe: NextNext

Entity Relationships

Entity InquiryJames Bluefield 04/15/1968

Recent AddressRecent Address

142 WashburnSeattle Wa 12345 Recent PhoneRecent Phone

123-456-7890

DispositionDispositionParole

AliasesAliases

Other AddressesOther Addresses

Other Phone #sOther Phone #s

J. Blueman

Jesse Bluefield

John Bluefield

Jamie Bluefield

RecordsRecords

AssociatesAssociates

MoreMore

Map ItMap It

Incident – Bank Robbery

Arrest Report - Tacoma

Arrest Report – Seattle

Incident - DUI

Jesse James02-28-2003

MugMug

MoreMore NextNextMoreMore

OR

Crime Characteristics

Offense: Forcible Rape

Suspect: Male

Race:

Sex:

Age:

Height:

Weight:

Hair:

NextNext

Female

White

55 to 65

64to

Blonde

0

Victim:

to

Find Similar:

Subscribe:

1300

Data

Data SubmittedData Submitted Information ReturnedInformation Returned

Collabora-tion

Sub-scription

Visualization

Analytical/Reporting

Search

Notification

ServicesServices CapabilitiesCapabilities

Incident/Case

Correlation

AutomatedProcessing

Entity Resolution

Entity Correlation

N-DExNN--DExDEx

People, Places, Things, Relationships, CharacteristicsPeople, Places, Things, Relationships, Characteristics

Catalog/Catalog/IndexIndex

EntitiesEntities

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-DExN-DEx

Network

NetworkNetwork

LEA System

End-User Browser Integration

Web Services

Integration

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

QuestionsSSA Edward C. Waigand

N-DEx Program Support ManagerCriminal Justice Information Services

DivisionPolicy, Administrative, & Liaison

Branch1000 Custer Hollow RoadClarksburg, WV 26306

(304) 625-4232ewaigand@leo.gov