120 likes | 224 Views
SEPR-CTTF Law Enforcement Justice Information System. JNET 2007 1 st Quarter Meeting – Status Report. The Law Enforcement Justice Information System (LEJIS) allows for better data sharing to Increase Officer and Public Safety Improve Decision Making Abilities at the Local Level
E N D
SEPR-CTTFLaw Enforcement Justice Information System JNET 2007 1st Quarter Meeting – Status Report
The Law Enforcement Justice Information System (LEJIS) allows for better data sharing to Increase Officer and Public Safety Improve Decision Making Abilities at the Local Level Reduce or Eliminate of Redundancy, Inaccuracy and Inefficiency in Justice Information Handling LEJIS will share CAD records from county dispatch center’s CAD systems Incident/Person/Vehicle/Property records from police department’s RMSs Warrant records from AOPC web service What is the LEJIS?
Guiding Principles • Use federal funds to offset expenses • Use federal IT and data transfer standards • Don’t introduce new system, use existing • CAD/RMS vendors part of team + get paid • Share information between PD’s and others in the justice community from local to federal level • Give police chiefs control over data release
Record Types • Blotter Information • Standard, public data released to press Public Police • Investigative Information • More sensitive data between law enforcement and justice personnel, what is known • Intelligence Information • Most sensitive type regarding ongoing investigations, narrative, what is suspected
LEJIS – Step 1: Systems send basic summaries to LEJIS pointer-index Index cards Local CAD or RMS JNET/LEJIS End User • Index • Security • Auditing
LEJIS – Step 2: users search by their CAD/RMS Interface Standard Search Screen
LEJIS – Step 3: users review hits via CAD/RMS Interface Enhanced Record Review Screen
LEJIS – Other steps • Users can click on hit and bring back the investigative details from origin PD • Users can view investigative details • Users can request intelligence details/narrative • If permission granted from origin PD, users can view incident record narrative
LEJIS Status • Ongoing design discussions between LEJIS contractors and JNET technical team • LEJIS will use JNET PKI security architecture for credentialing and identity management • LEJIS will use JNET Logging/Auditing infrastructure to comply with 28 CFR Part 23 and CHRIA • LEJIS staging servers will be located at JNET facilities • LEJIS production servers will be located at the Commonwealth Technology Center
LEJIS Status • Reference Implementation • A mock-up hybrid CAD/RMS for demonstration and testing • Developed using best practices • Code delivered to CAD/RMS vendors to streamline their effort, keeping cost and risk down • Nearing 50% completion
LEJIS Status • LEJIS System Core • Development environment operational • Pointer-index database operational • Federally-compliant index record formats completed • Components to submit, update, expunge index records in final testing stage • Components to accept user search requests and send back results nearing final testing stage
LEJIS Status • RMS vendors • Metro Tech, Cody, Informant • Scope of Work submitted to vendors • User group meetings to begin week of 2/26 • First product will be screen mock ups and storyboards