1. The Law Enforcement Information Exchange (LInX)
Unclassified

2. The Law Enforcement Information Exchange
What LInX is
History of the LInX projects
How LInX works
Current Status of the LInX projects
Capabilities
Lessons Learned—Success Factors
Success Stories
Screenshots

3. What LInX Is
The Law Enforcement Information Exchange (LInX) is an advanced information sharing system conceived, funded and built by the United States Naval Criminal Investigative Service, but not owned or controlled by NCIS

4. What LInX Is
Transports, normalizes, indexes then consolidates data from member law enforcement agencies’ RMS systems on a nightly basis into a data warehouse & allows users to search all contributed data with several search & analysis tools
LInX is NOT an original system of records but a replication of many original systems of records
LInX is populated with law enforcement data only and is NOT an intelligence system

5. What LInX Is
Not just another database or computer system, but an advanced investigative tool for the law enforcement community
It allows you to know things you couldn’t know before
Another tool in an officer’s/investigator’s toolbox

6. History of LInX
What is NCIS & why is DoD building an IS system for law enforcement?
After the bombing of the USS Cole and the events of September 11, 2001 NCIS mission priorities changed
Information sharing was critical to new agency priorities

7. LInX Status- June 2007 7 Regional LInX Systems Planned
Operational in 6 Regions
Developmental in 1 Regions in FY 07
Navy/NCIS Programmed in 2 Regions FY’08
** Discussions re development of Los Angeles LInX Region for FY’07
IOC-Oct’04
100%
New London,CT
IOC-Feb’07
100%
IOC-Apr’06
IOC-Jun’07
IOC-Jun‘05
100%
Los Angeles
San Diego
IOC-Sep‘05
100%
IOC-Jun‘05
100%

8. How LInX Works Existing Network Existing Network Individual Agency RMS
Shared RMS FP FP
Data Warehouse FP FP
This diagram depicts the multiple types of systems that the front porch allows to access the data warehouse. The Washington LInX has all of the various system configurations in the region connected successfully to the data warehouse through the front porches. An example of an existing network with shared RMS systems accessing the data warehouse are the ILEADS and SNOPAC systems. An example of an existing network with individual agency RMS accessing the data warehouse would be the King County RAIN system, with the Washington State Patrol and the Federal agencies accessing the data warehouse through various individual front porches.
This configuration will allow any level of agency records system to connect to the data warehouse regardless of configuration or brand thus allowing any agency to contribute at a minimal cost.
Federal FP
Other
State

9. LE Users LInX Data Data is accessed by the users Warehouse
FBI Field Office
USER
LInX Data
Warehouse
Data is accessed by the users
from a web browser using SSL
USER
Login & password required
USER
256 bit encryption
Firewall
LE DATA
Arrest Records
Investigations
Traffic Reports
CAD Data
Booking Records
Warrants
Front Porch
1024 bit encryption
4- Dell 6650 Servers with Applications
Firewall
Agency
RMS System
Data is pushed
to the Front Porch
then into LInX
LInX LE Agency

10. Types of Data in LInX Types of electronic data in the system:
Law Enforcement RMS data: (Structured & Unstructured)
incident fields, incident narratives, supplemental investigative narratives, field interviews, suspicious incidents, arrests, outstanding warrants and mugshots
Computer-Aided Dispatch (CAD) data
Pawn shop records

11. Types of Data in LInX Jail booking records Traffic Crash Reports
Traffic Summons data
Parking ticket data
Sex Offender Registry
Adult Criminal History
Statewide mugshots

12. LInX Capabilities Tactical functions and operation
Tactical Search Screens
Search by name, partial name, nickname, address, vehicle, SSN, OL#, telephone #, FBI#, record # or type, date range, etc.
Exact or Assisted Search and use of wildcard
Local warrants & mugshots
Analytical functions and operation
Advanced search
Tactical + incident narratives, date ranges, individual agency search, etc.
Free text search (Google®-like; conceptual)
Link analysis (visual representation of relationships)
Pawned Property
search by name, article, description, serial #, pawn shop, date range, etc.

13. Success Factors Strategy Governance Funding Source Data Capabilities
Technology
Long Term Support
Evaluation Methodology
Program Management

14. Success Factors Strategy (2)
The project must have the ability to address specific critical issues as well as reconcile the various interests of the participating agencies.
Common Vision must be established
Develop a Comprehensive Strategic Plan

15. Success Factors Governance
The project must establish a strong governance infrastructure to support policy and operational decisions for the long-term survival of the project.

16. Success Factors Data The goal is to share all legally sharable data
More data, not less
This would include structured and unstructured data in records systems and investigative files.

17. Success Factors Capabilities Easy to use query and analysis tools
Robust security & audit standards
A system by law enforcement personnel for law enforcement

18. Success Factors Technology Open standards, affordable and capable
Easy to enhance and scale up
The system must build upon existing capabilities and not force agencies to buy new systems or change business practices—i.e., seamless integration.

19. Success Factors Support
CEO long term buy-in with associated policies on system use
Becomes a part of training curriculum with necessary policies in place
Comprehensive training and user manuals
Long-term financial support
Technical support from vendors and/or in-house experts for long-term maintenance

20. Success Factors Evaluation Component
The project must have identified evaluation criteria to gauge the effectiveness of the system to its stated goals.
Define success

21. Success Factors Program Management
Strong program management is important in order to achieve success.
“Champion” to push the process

22. Lessons Learned An Operational project not an IT project
Built from the ground up, not top down—every level involved
Structure governance to get agency CEOs to the table
Keep agency CEOs directly & consistently involved
Law enforcement information only
Investigative system not intelligence
Strong rules of use and administrative policies
Not a cookie-cutter approach; each system is different according to the priorities, needs, issues and laws
Start small, minimal agency impact, get it up and working then add more capabilities & additional agencies
Feedback loop from users with continuous improvement

23. Success Stories Homicide of a police officer in VA Gang rape in VA
Homicide Suspects in NW
Identity Thefts in NE Florida
Attempted Child Abduction in NW
Theft Rings at Norfolk Intrn’l Airport
Many many instances of recovered stolen property
Serial Burglary, Robbery & Check cases
International Money Laundering in NW

24. Questions or additional information:
Dennis A. Mook, Chief of Police (Ret.)
(757)