Washington’s Approach to Justice Integration Global Justice Users’ Conference August 22, 2007 Chicago, IL Mo West, JIN Program Manager Steven Scott, JIN Developer

Information Sharing  A necessary requirement in the criminal justice system.  Crosses jurisdictional lines and levels of government.  Information is found in multiple systems with multiple user requirements

The Problem Collecting and sharing data from multiple sources is:  Time consuming  Inaccurate  Incomplete  Outdated  Just plain frustrating  The mission of the JIN Program is to make justice information  Timely  Accurate  Complete CJIA-RCW passed in 1984

The Justice ‘System’

Alternative Approaches  Point-to-point connections  Central repository  Decentralized exchanges

The Solution: The Justice Information Network Data Exchange (JINDEX) Decentralized Exchanges: SOA Creating access and automation among multiple systems that results in information that is:  Timely  Accurate  Complete  Up-to-date

JIN Applications  Possible Criminal History and Case and Criminal History (PCH/CACH)-increased access  Statewide Electronic Collision Ticket Online Reporting (SECTOR)-automated workflow  The Justice Information Network Data Exchange (JINDEX): the common denominator

PCH/CACH  Searches disparate data sources with a singe query  Exchanges information regardless of the existing technology infrastructure  Increases access to additional data sources and end-users

Overview JINDEX Criminal History Protection Orders Warrants Case History Court Information JIS Driver Info 3 4 JIS 5 JINDEX ACCESS

Local Queries – Yakima County Interface

Query Results – Yakima County Interface

Local Queries – King County Interface

Query Results – King County Interface

SECTOR  Automates the traffic citation and collision reporting process between WSP, AOC, DOL, and DOT  Common ticket and collision specification between participants  Prior to SECTOR collision reporting could take weeks -- now completed in seconds

SECTOR Workflow

SECTOR Results  Went live on April 3, 2007 with tickets and collisions  Over 15,000 tickets, collisions, and dispositions processed through the JINDEX  10 courts processing tickets; all courts scheduled to go live in July

Development Review  We needed to address our development process  Applications achieved goal but lacked consistent development approach  Established IEPD Policy-identified the use of standards  Assist with operational components not included in IEPDs

Next Steps for JINDEX  Legislative support to expand services statewide  Goal is to begin services in:  15 counties over FY08  22 remaining counties in FY09  Support development of new applications that further automate and share justice information

The ‘How’ Steven Scott, JIN Program Applications Development

JIN Service Architecture

Providing JIN Services  Standardize the services we provide.  Define services that support the JIN Mission, Goals, and Objectives  Standardize the creation and enhancement of services.  IEPD Process, Development Tools, Applications, Systems Architecture  Standardize service integration with data consumers and providers.  Define system integration requirements for interfacing to centralized services  Standardize System administration.  Define and enforce policies that support systems integration, service governance, Service Level Agreements

JIN Service Model

Benefits and Impact  Reliance on standards  Reusable  Business Input  Loose Coupling  Provides context and predictable outcomes  No need to start from scratch  End user involvement = effective results  Minimize changes among participant agencies; responsive to changing policies

Questions? Mo West, JIN Program Manager Steven Scott, JIN Developer (360) Justice Information Network Program Thank you!