GRA Demonstration Meetings - Kickoff

GRA Demonstration Meetings - KickoffScott Came

Deputy Executive DirectorSEARCH

MAJIC Agency Stakeholders

Anchorage, Alaska

December 17, 2012

SEARCH, The National Consortium for Justice Information and Statistics | www.search.org

Agenda and Introductions

2

http://www.search.org/


GRA Background

Reference Architecture for justice information exchangeDeveloped by Global Justice Information Sharing Initiative 2007-2011Grew out of architectures in jurisdictionsWashingtonPennsylvaniaElectronic Court Filing standard

Leverages industry standards and methodologies (IBM, Microsoft, others)



Sample GRA Exchange



Why should I conform?

Acquire open, non-proprietary systemsGreater ability to share data with a wider

range of sourcesLower lifetime cost, less lock-in

Benefit of industry standards without as much hard workRFPs are easier to writeInteroperate with other conformant systems/jurisdictionsMore grant opportunities (3 of 6 categories in this year’s BJA JIS solicitation mentioned the GRA)



GRA Conformance Targets

ServicesExchanges (service “actions”)Infrastructure (“execution context”)



Services

Component that provides access to a capability through one or more closely related information exchangesA conformant service: Is properly identified (follows the guidelines

in the GRA Guidelines for Identifying and Designing Services)

Is properly documented (follows the structure and conventions in the Service Specification Package Guidelines)



General Information Flow Model

8



Information Flow Model Archetypes

9



Event-Driven

Event-Driven Archetype Information exchange begins with the

occurrence of a real-world business event that is either citizen-initiated (e.g., an arrest) or procedural (e.g., sentencing an offender).

The composite response under this archetype represents the enterprise response or “handling” of this event, which generally involves orchestrating individual agency component responses.

10



Event-Driven Information Flow Model

11



Event-Driven ModelComponent Actions

12

Event-Driven Component Actions

Action Description ExamplesFile Deposit of information for the purpose of establishing

some sort of case or request.File Criminal Case, File Felony Charges, File Complaint

Update To change or modify stored information Update Criminal History

Record To store information for future access. Record Arrest Warrant, Record Booking Report

Remove The termination of an individual’s association with an organization or process, etc.

Remove Warrant, Remove Arrest Report

Issue To formally distribute information expecting that some sort of physical action will be taken.

Issue Arrest Warrant, Issue Summons, Issue Warning

Notify To distribute information based on a need for awareness. Notify of Intake, Notify of Booking

Submit To provide information to the power or authority of another through policy (process) or law. Submit is usually associated with a deference to a judgment, opinion, decision or analysis.

Submit Arrest Report, Submit Progress Report



Citation EventExample

13



Query-Driven

Query-Driven Archetype Information flow begins with a practitioner’s or

citizen’s desire to know information about the state or history of the justice system (including events that occurred and any responses to those events).

The composite response under this archetype represents the enterprise effort to gather the requested information from one or more component data sources and assemble the component responses into a single, enterprise response to the requestor.

14



Query-Driven Information Flow Model - Query

15

Trigger(consumer system)

Composite Event Response(intermediary system)

Component Event Response(provider system)

Query Query [Subject]

ComponentAction A

dapt

er [Subject]SearchService

Serv

ice In

terfa

ce

Ada

pter [Subject]

SearchService

Serv

ice In

terfa

ce

Handle[Subject]

QueryService

Serv

ice In

terfa

ceComponent

Action

QueryResponse

Query Response

[Subject]Query

AssemblyClient Co

nnec

tor



Query-Driven Information Flow Model – Query Response

16




QueryResponse Query

[Subject]Response

Ada

pter

Provide [Subject]

Query ResponseService

Serv

ice

Inte

rfac

e

[Subject]Query

ResponseClient C

onne

ctor

ComponentAction

[Subject]Query

ResponseClient C

onne

ctor

QueryResponse

Handle [Subject]

Query Response Service

Serv

ice

Inte

rfac

eQuery

{Subject]Response

Note: A message ID or Transaction ID ties the ‘Query Message’ to the ‘Query Response Message’



Query-Driven Information Flow Model – Component Actions

17

Query-Driven Component Actions

Query Actions Query Response Actions

Action Description Examples Action Examples[Subject]Query

An Query to a single system for information on a subject (person, place, thing) based on initial criteria.

Query Location [Subject]QueryResponse

Query Location Response

[Subject]FederatedQuery

A Query to multiple systems for information on a subject (person, place, thing) based on initial criteria.

Person Federated Search, Automobile Federated Search

[Subject]Federated QueryResponse

Person Search Response, Automobile Search Response

Identify [Subject]

To confirm or deny the identity of a subject.

Identify Person, Identify Organization

[Subject] Identification

Person Identification, Organization Identification

Verify [Subject]

To confirm or deny the identity of a subject through a comparison of 2 or more data.

Verify Person with Fingerprints

[Subject] Verification

Person with Fingerprints Verification

Note: Each Query must have a Query Response



Person Federated QueryExample

18



Request-Driven

Request-Driven Archetype Exchange is triggered by a practitioner’s

desire to effect some state change in the collective environment.

The initial exchange is with a composite request intermediary, which in turn exchanges information with component request services.

These exchanges could be one-way or request-response, and if request-response could be synchronous or asynchronous.

19



Request-Driven Information Flow Model

20




Request Request[Subject] A

dapt

er

Receive [Subject]RequestService

Serv

ice

Inte

rfac

e

Handle[Subject]RequestService

Serv

ice

Inte

rfac

e

Request[Subject]

Response

Ada

pter

Provide[Subject]Request

ResponseService

Serv

ice

Inte

rfac

e

[Subject]Request

Response

[Subject]Request

AssemblyServiceClient C

onne

ctor

[Subject]ResponseServiceClient C

onne

ctor

Response

Handle[Subject]ResponseService

Serv

ice

Inte

rfac

e

SubjectRequest

Response



Warrant Request/ReplyExample

21



Exchange

Action that a service performsProtocol for interaction with a serviceA conformant exchange (action):Follows the rules expressed in a GRA

Service Interaction Profile (SIP); in practice, this means “WSDL first” web services

Has a NIEM-conformant information model



Infrastructure

In GRA terms, “execution context”Network, hardware, and software that supports service interactionConformant execution context provides:A container environment for connectors

(consumer or initiator of interaction)A container environment for adapters

(provider or recipient of interaction)A container environment for intermediariesSecurity, availability, performance, and

reliability



Global Information Sharing Toolkit (GIST)

Collection of Global’s “normative” products:Global Reference Architecture (GRA)Global Federated Identity and Privilege

Management (GFIPM) toolsGlobal Technical Privacy FrameworkReference Service Specifications

Template for a state’s justice information sharing architecture

NIEM and IEPDs are not enough to ensure interoperability and reuse!

24



GIST Conformance in a NutshellNIEM conformant exchangesGRA conformanceUse “WSDL first” WS-*Avoid point-to-point exchangesEnterprise-wide infrastructure that supports

the standardsServices conform to design principles

GFIPM conformanceAvoid new centralized user / credential

storesServices and applications trust users’

agencies’ authentication25



Thank you!

Scott Came

Deputy Executive Director

SEARCH

[email protected]

916-212-5978


mailto:[email protected]

Documents

GRA Demonstration Meetings - Kickoff