Integrating Complex Regional Information Sharing Programs in the

Transcription

Integrating Complex Regional Information Sharing Programs in the
Integrating Complex Regional
Information Sharing Programs in the National Capital Region
in the National Capital Region
Dave Russell Fairfax County, VA Police
1st Sgt Ross Randlett
Prince William County, VA Police
Captain Mitch Cunningham
M t
Montgomery County, MD Police
C
t MD P li
Biometric Systems National Capital Region
Slide 2
National Capital Area Regional AFIS Systems
Slide 3
NCR Population
Total population 5.4 million
A few jurisdictions in the area include:
Fairfax County
Prince William County
Prince George’s County
’
Washington D.C.
1,000,000
365,000 820,000
591,000 (
(2008 Census)
)
Fairfax: 1,406 sworn officers Slide 4
Washington D.C. 4,050 sworn officers
History of the Region
 RAFIS - late 70’s
 DCAFIS - 1982
 NOVARIS - 1984
 Connection of RAFIS - DCAFIS - NOVARIS
 Regional AFIS Collaboration Components:
 Fingerprints
 Facial recognition
 Mobile AFIS
 NCR N
Network
t
k
 Isolation
Slide 5
Regional AFIS Network
US
Park Police
FBI
AFIS
Montgomery County
VPN
US
Capital Police
Prince George’s County Maryland
AFIS
RAFIS
Washington DC
DCAFIS
VPN
(MugShot)
Town of Vienna
Town of Herndon
City of Fairfax
N th
Northern VA Regional
VA R i
l
Identification System
NOVARIS
Fairfax County
Alexandria
City
U. S. Secret Service
VPN
Virginia State
AFIS Loudoun
County
Slide 6
Prince William
County
Arlington
County
VA VA
Forensics
National Capital Region Biometrics Governance Board Developed to:
 Focus Regional Collaboration
 Provide Regional Procurement Leveraging
 Provide
P
id Guidance
G id
for
f Technology
T h l
Direction
Di ti
 Identify Cost Savings and Efficiencies
 Develop Funding Strategies – Urban Area
Security Initiative (UASI) Grant
 Discuss MOU design requirements
 Technical Working Groups for Specific
Components
Slide 7
The Many Shades of Interoperability
and Integration of Systems
 Cross database search in the Region ‐ States – Federal
“Enter once, search many”
 Extending search capability out to officer at the first E t di
h
bilit
t t ffi
t th fi t
point of contact
 Mobile AFIS
 Information search and additional databases





LInX
MugShot Databases
DMV
RISC
Local Record Management System
 Cooperation between agencies to develop information y
systems
 Pinellas County Florida
Slide 8
Watch for “Vendor Lock” with too much integration
Mobile AFIS  Military Registry and Rapid ID
 Law Enforcement Application
 First Responder Identification
Fi t R
d Id tifi ti
Privacy Concerns ? Search:  Local
 Regional
(
)
 Federal (RISC)
Slide 9
Product Development
Law Enforcement Requirements
 Is it worth the investment
 Time – People ‐Technical resources
Vendor(s) Participation
 Is it worth their investment
Is it worth their investment
Slide 10
Product Development
We need a $100 “throw away”
$
y
It needs to use existing resources already
It
needs to use existing resources already
available to the street officer Make it the size of a “Snickers Bar”
Slide 11
Mobile AFIS
Functional Architecture
Slide 12
Mobile AFIS Goals
Cruiser Laptop compatibility Self contained software
Self contained software
Use existing components of
Police Agencies
Police Agencies
No recurring costs
Return can launch another
Return can launch another
database search
Prince William
VA
Police
Department
p
District of
Columbia PD
AFIS
 LInX
Device can’t be “weaponized”
 Data is not stored on the device
D
i
d
h d i
Slide 13
Northern
Virginia AFIS
Montgomery
County, MD and
Prince George’s
County, MD PD
AFIS
Database Search Strategy
Prince William
County VA
Police
Department
District of
C l bi PD
Columbia
AFIS
Northern Virginia
AFIS
Montgomery County,
MD PD and Prince
George’s County,
MD PD AFIS
Slide 14
Mobile AFIS Configuration
Firewall
 PWCPD provided Windows 2008 Web Server
 Mobile software was configured to submit and receive NIST files using HTTPs
 DES was setup to support HTTPs submission and AFIS
Database
responses through the PWCPD Web Server
 NOVARIS opened the appropriate ports to enable NOVARIS opened the appropriate ports to enable
connection between the PWCPD Web Server and NOVARIS DES
 PWCPD provided HTTPs certificate for the Web PWCPD provided HTTPs certificate for the Web
Server
Slide 15
Number
u be o
of
Tenprint
Records
NOVARIS
545,264
DC AFIS
596,897
RAFIS
543,342
Mobile to LInX Query
Slide 16
What is the Law Enforcement
Information Exchange Program?
Northwest
Northeast
NCR
Virginia
Southern
California
North
Carolina
Rio Grande
Gulf Coast
Southeast
Hawaii
Slide 17
17
 A cooperative regional system for sharing law enforcement data among participating local, state and federal law enforcement agencies
 10 LInX Regions plus DoD LInX (D‐DEx)
NCR‐LInX Governance & Membership
NCR‐LInX Governance
 124
124 Member agencies
Member agencies
 NCR‐ LInX Memorandum of U d t di
Understanding
 Executive Committee
 Legal Committee
Legal Committee
 Oversight Committee
 Strategic Funding g
g
Committee
NCR‐LInX Operational P li
Policy and Rules
dR l
NCR‐LInX Annual Audit Slide 18
LInX Regions Summary
*Trained Active Users = Non disabled, non deleted user accounts with a non null Last Login Date.
Slide 19
What’s In NCR‐LInX?
NCR‐LInX Record Types
Slide 20
Almost 95 Million Event Records
Over 9 Million Mugshots
Over 65 Million Narratives
NCR‐LInX System Components
Slide 21
LInX Meets Federal
NIJ Standards
U.S. DOJ GJXDM / DHS NIEM compliant & open architecture
 Federal & State FOIA, Privacy Act & disclosure requirements‐compliant
 DOD DIACAP certification standards & security accreditation achieves data and transmission security
Slide 22
NCR‐LInX Success Stories
“NCR‐LInX was instrumental in the identification, capture, and arrest of the so‐called “East Coast Rapist.” Through ongoing efforts, a short list of suspects was generated from NCR‐LInX.
p
g
A detailed tip generated by a public pg
y p
outreach campaign led to the identification of the suspect and to his arrest.
Slide 23
Connection Between NCR‐LInX
and NCR‐Biometrics
 Pilot Project with Motorola DataStrip Devices
 Officer uses biometric enabled handheld
device to capture print and submits search
to regional AFIS
to regional AFIS
 If a hit is generated, authorized NCR‐LInX
users can initiate LInX Mobile session
(browser‐based) on handheld device.
 LInX Mobile application parses hit return
LI X M bil
li i
hi
from AFIS, and performs a name search against
the NCR‐LInX system
 Led to Development of LInX Handheld Solution
 Differences between MorphoIDent/Cogent and Datastrip
Interfaces to NCR‐LInX
 NIST‐compliant transaction files used to transfer NIST
li
i fil
d
f
information with MorphoIDent/Cogent. DataStrip
devices used custom/one‐off format.
 MDTs/Laptops used for display of results, instead of DataStrip
f D t St i device / LInX Mobile application.
d i / LI X M bil
li ti
Slide 24
Connection with Newer Devices
Slide 25
How The Connection Works
How The Connection Works
Mobile AFIS Result List
How The Connection Works
LInX Search Results
Overview of Mobile AFIS / NCR‐LInX Interface
Workflow
Slide 29
 Officer uses MorphoIDent / Cogent device to capture print
 Bluetooth connection from device to MDT
 If a ‘hit’ is found on the Regional AFIS system, NIST file returned to MDT from regional AFIS system with person
returned to MDT from regional AFIS system with person demographic information
 Officer uses MDT to review a list of ‘hits’, and can select a name by clicking on it to initiate a query of the NCR‐LInX b li ki
it t i iti t
f th NCR LI X
system
,
y
 If NCR‐LInX session exists, search will be automatically executed and results returned to user.
 If no NCR‐LInX session exists, user will be prompted for login prior to executing query
login prior to executing query.
 Officer can navigate from hit list to NCR‐LInX application using MDT
Benefits of the Connection
Officer Safety and Situational Awareness
 Results
Results from LInX are displayed showing subject’s law from LInX are displayed showing subject’s law
enforcement activity in the region
Ability to return results from all LInX systems y
y
and Partner systems
NIST files (standards) returned to mobile are used to initiate query to NCR‐LInX system
Can be replicated in other LInX regions i l
implementing these devices
ti th
d i
Easily portable to regions implementing connections with state / federal RISC systems
connections with state / federal RISC systems
Slide 30
Any ADDITIONAL Questions?
Slide 31