Justice Reference Architecture

1
Justice Reference Architecture

• Sharad Rao
• Tetrus Consulting Group, LLC

2
Agenda

• Presentation Objectives
• Service Oriented Architecture (SOA) Concepts
• Need for an SOA
• Justice Reference Architecture and its components
• Implications on Corrections practitioners
• Example of utilizing SOA Concepts Massachusetts
  Department of Correction

3
Presentation Objectives

• Present Service Oriented Architecture Concepts
• Discuss the need for Global Justice Reference
  Architecture
• Present the components of the Global Justice
  Reference Architecture
• Discuss how Correctional Agencies could leverage
  these concepts to improve operational
  efficiencies and participate in the Integrated
  Justice environment.

4
Service Oriented Architecture Concepts

• Service Oriented Architecture
• The paradigm for organizing and utilizing
  distributed capabilities that may be under the
  control of different organizations
• Key Concepts for the SOA Paradigm are
• Visibility The capacity for those with needs
  and those with capabilities to see each other.
• Interaction The activity of using a capability.
• Effect The result produced by using a
  capability.

5
Spaghetti Integration

• Proprietary technologies
• Multiple infrastructures
• High cost of operation
• Organizational/ Control issues

6
Spaghetti Integration
7
Integrated Justice Spaghetti

• Custom integration
• Silos of information
• Difficult to change
• A complex, costly approach that really isnt
  integrated

8
Silos of Data and Processes
Applications deployed in different business units
or agencies become silos of data and process
9
Breaking down the silos
SOA allows us to incorporate data and processes
from across the enterprise
10
A Service Oriented Enterprise
11
A better way
12
Scalable
13
Focus on the Business Process and Services
Application a
Application c
Application b
Application logic
Source Service-Oriented Architecture, Thomas Erl
14
Focus on the Business Process and Services
Business process layer
Business-oriented services
Services interface layer
Application-oriented services
Application layer
.NET
J2EE
Legacy
Source Service-Oriented Architecture, Thomas Erl
15
Focus on the Business Process and Services
Business process layer
Services interface layer
Application layer
.NET
J2EE
Legacy
Source Service-Oriented Architecture, Thomas Erl
16
Architecture Requirements

• How should decisions be made?
• Planning decisions
• Investment decisions
• System design decisions
• Decision-making tools
• Principles
• Environmental Trends
• Business Drivers

17
System Integration Principles

• Minimize the dependencies between integrated
  information systems (loose coupling).
• Favor technologies that leverage open industry
  standards.
• Promote the treatment of integration interfaces
  as sharable enterprise assets.
• Promote the one-time entry (or update) of
  information.

18
Environmental Trends

• Decisions about system integration should reflect
  the following trends
• Open standards for integration are stabilizing
• The market for integration infrastructure remains
  diverse, with many viable players

19
System Integration Business Drivers

• The enterprise will implement technology
  capabilities incrementally.
• Enterprise solutions will continue to exhibit a
  mix of commonly-provisioned and agency-unique
  capabilities.
• The enterprise will continue to rely on a diverse
  set of software platforms and development
  technologies.

20
Conceptual Reference Architecture

• A reference architecture establishes key
  concepts, relationships, and high-level
  components to support integration
• Identifies specific areas where we need more
  work, but demonstrates how everything fits
  together to satisfy requirements

21
Solution Design Guidelines

• Favor solution designs that
• Separate user interface from business logic and
  persistence logic (separate software interfaces)
• Integrate with other systems across an interface
  (not directly)
• Integrate (inbound and outbound) using
  open-standard technologies

22
Capabilities and Services
23
Interfaces and Interaction
24
Service Interaction Profiles
25
Policies, Contracts, Agreements
26
Execution Context
27
Business Processes / Service-Capability Hierarchy
28
Edge vs. Common Capabilities
29
(No Transcript)
30
Implications

• At least 9 groups are working on different pieces
  of the architecture.
• One of those groups doesnt yet exist.
• Some pieces of the architecture are not yet being
  worked on by anyone.
• There are at least 8 different points of
  potential technical interoperability issues.
• There are 3 broader points of disconnect.

31
Status

• This is a work in progress.
• The concepts may change incrementally, but the
  basic approach is set.
• Unofficial efforts to collaborate with broader
  communities.
• Official efforts to brief broader communities.

32
Implications to Corrections

• The Justice Reference Architecture can provide
  substantial benefits to Correctional Agencies
  both as Providers and Consumers
• Overall Benefits
• Reduces integration expense
• Increases asset reuse
• Increases business agility
• Reduces business risk and exposure
• Enhanced operational efficiencies
• Ability to develop solutions faster due to reuse
• Ability to service external constituents more
  efficiently
• As Consumers
• Allows Correctional Agencies to quickly consume
  services created by other agencies such as
  Criminal Histories, Courts, etc
• As Providers
• Allows Correctional Agencies to develop services
  that can enhance information sharing in the
  integrated justice environment

33
Implications to Corrections

• Some Examples of services for Corrections

Services Corrections Can Provide
Services Corrections Can Consume
Classification Service Sentence Calculation
Service Victim Notification Service Inmate
Lookup Service Inmate Details Service Inmate
Tracking Service
Criminal History Service Warrant Service RMV
Service Official Version Service Inmate Health
Care Service
34
Implications to Corrections

• Massachusetts Department of Correction is
  currently in the process of piloting the
  provision and consuming of services. Examples of
  these are
• Criminal History Service
• Q2 Service (Warrant Management and NCIC)
• Q5 Service (Suicide History)
• Inmate Release Service

35
What Corrections Can Do?
Business process layer
Services interface layer
Application layer
.NET
J2EE
Legacy
36
Questions Answers
37
Resources

• OASIS SOA Reference Model Technical Committee,
  www.oasis-open.org
• Global Justice Infrastructure and Standards
  Working Group
• Dr. Tom Clarke, tclarke_at_ncsc.dni.us
• Thomas Erl, Service-Oriented Architecture
  concepts, technology and design.