Corrections Application Advanced Interfaces

1
Corrections Application Advanced Interfaces

• Presented by Arkansas Department of Community
  Correction
• Marquis Software Development

2

• Agenda
• Project background
• Integrated application concepts
• External Interface Examples
• Using Global Justice XML (JXML) Data Model and
  Data Dictionary
• Critical success factors
• Question and answer session

3
Arkansas Goal - January 2000

• Goal New integrated corrections system
• Requirements
• Improved user interface
• for better user productivity
• Single integrated system to serve both agencies
• Reduced data entry
• Provided more accurate information
• Implement best corrections application practices
  
• Implement modern computer technology
• Reduce costs to maintain and operate system
• Provide better integration with partner agencies
  
• Improve interfaces with many external agencies
• Support the States IJIS project

4
Arkansas Corrections Information Technology
History

• Separate agencies (ADC and DCC)
• Different IT goals and strategy (prior to 2000)
• Separate information systems
• Disparate technology
• No direct data exchange
• Significant duplicate data entry
• Lack of offender information available to staff
  for decision making

5
Arkansas Department of Information Systems (DIS)
Significant Changes

• DIS committed to support web-based applications
• DIS set standards for Open Systems
• JAVA (J2EE), relational DBMS, thin client, etc.
• DIS offered web server hosting and support
• Eliminated use-based pricing (mainframe concept)
• Provided system software support
• Provided network management
• Provided physical and network security
• Provided external application interface support
• Batch File Transfer, Real Time Queued Message
  Services, other

6
Corrections and Community Corrections Partnership

• Two separate agencies (ADC DCC)
• IT goals, strategy and budgets aligned
• Focused on corrections staff productivity
• Focused on corrections staff and public safety
• Solution Common Information System
• Common business function
• Common offender data
• Agency unique offender data
• Common external interfaces
• Agency unique interfaces

7
Integration Between Department of Correction
Department of Community Correction

• Capture information at offenders first contact
  with either agency
• Append information as needed over offenders
  lifetime photographs, cautions and warnings,
  etc.
• View and reuse information entered by either
  agency

8
Functional Support for Integration and Data
Exchange

• Offender identification
• Agency Specific Identification Numbers
• Unlimited Number of Names
• Unlimited Number of Addresses
• Unduplicated party ID concept
• Persons, Addresses, Organizations, Telephone
  Numbers, etc.
• Expanded Data Dictionary Support
• Code table values
• Common and unique code values
• Code Value Relationships
• Role Based User security profiles
• Protect the data
• Administered by each agency

9
eOMIS Functional Architecture
Common Offender Functions
Inmate Management
Field Services
Common Infrastructure Functions
External Operating Interfaces
External Applications
10
(No Transcript)
11
Arkansas Crime Information Center (ACIC) Interface

• Old Approach
• Both Agencies on same computer platform
• Direct access to the ADC database
• New Approach
• Separate and disparate systems
• Request/response mode
• Using IBM MQ Series message queuing protocol
• GJXML format (a future objective)
• Officer receives instant email notice of inquiry,
  ORI, and contact information
• Chronological record is automatically created

12
(No Transcript)
13
Post Prison Transfer Board Interface

• Identify inmates eligible for parole hearing
• View inmate record
• Incarceration history
• Program referrals
• Disciplinary history
• Process inmates to be released
• Scheduling hearings
• Vote monitoring, notification, and follow-up
• Board actions reported to Governors office
• Facilitates return of parole violators to prison

14
VINE Network Interface

• Victim Information and Notification Everyday
  (VINE)
• Designed by Appriss, Inc
• Hourly data transfer from eOMIS to VINE
• Movements (relocation of offender)
• Status changes (level of supervision)
• Parole board actions
• Releases
• VINE places telephone call to victims, relatives
  and others

15
JusticeXChange Interface

• Offender information from Arkansas and twelve
  other states
• Jail bookings trigger JXML transaction to eOMIS
• eOMIS instantly emails supervising officer with
  charges, location and contact information
• eOMIS returns cautions, warnings and contact
  information to law enforcement and jails
• Booking photographs routed to eOMIS

16
(No Transcript)
17
(No Transcript)
18
(No Transcript)
19
(No Transcript)
20
(No Transcript)
21
(No Transcript)
22
(No Transcript)
23
Clemency Application Processing for the
Governor's Office

• Old Approach
• Manual forms, FAX, and paper copies
• Standalone PC based applications
• New Approach
• Fully integrated with eOMIS
• Request/review/approve or deny
• Includes support for adding new offenders
• Expanded felony database to include misdemeanors
  
• Everyone working with same data
• Data entered once

24
Integrating Courts Prosecutors

• Faulkner County Pilot Project
• Sends Commitment and Disposition information from
  the court system, using extended GJXML to eOMIS
• Benefits
• Universal, standard format for data
• Semantic meaning of data is better
• (Less Difficult to Understand)
• Challenges
• New technology to learn
• Standards are evolving

25
Workforce Opportunity Tax Credit Interface
Operational May 2, 2003. Old process
Verification mailed to Probation/Parole Officer,
completed and mailed back to Employment Security
Department (a week or more) New process ESD
staff access eOMIS directly, and obtain
verification (in seconds, not days) Benefits
Faster tax credits to employers Thank you for
assisting us with obtaining verification
capability for the WOTC ex-felon target group.
We used the file successfully yesterday and
issued 139,200 in potential tax credits.
Ruthie Pippins, Arkansas Employment Security
Division
26
GIS Interface

• Geographic Information System (GIS) capabilities
• Easily export eOMIS information
• Offender name, address, offense type, DNA
  information, etc
• Import into mapping software
• Microsoft MapPoint
• ArcView

27
(No Transcript)
28
GIS Interface

• Import shape files of schools, daycare centers,
  etc
• Plot offenders living within specific distances
  of schools and day care centers or other
  specified areas

29
(No Transcript)
30
(No Transcript)
31
(No Transcript)
32
(No Transcript)
33
(No Transcript)
34

• Critical Success Factors
• For Existing Interfaces

• Existing interfaces can be enhanced
• New products available
• New approaches
• Schedule can be rapid provided both parties have
  the initiative and the technology.

35

• Critical Success Factors
• New Interfaces

• Expect BIG results
• It will take longer than anticipated
• Be conservative on timeline expectations
• Expect more coordination issues than anticipated
• Multiple vendors and agencies
• Results will conform to lowest common denominator
  
• Truths to remember
• Cant exchange data that doesnt exist.
• Cant achieve accurate results from inaccurate
  or missing data.

36
Integration Challenges

• Agencies have similar but different data
• Data capture based on internal use
• Code value translation conversion
• Justice XML Data Dictionary
• Data accuracy
• Inaccurate or missing data creates down-stream
  problems
• Newer technology may not be available to all
  partners

37
Essential Ingredients for All Interfaces

• Top management awareness and support
• Motivated actors
• Involved parties must see the potential benefits
• Time savings
• Monetary savings
• Protection of human life

38
Questions Answers

• The End