proprietary copyright 2003-2005 crossflo systems, inc. all rights reserved case study on the...

PROPRIETARYCopyright 2003-2005 Crossflo Systems, Inc. All Rights Reserved

Case Studyon the

Regional Information Sharing and Analysis (RISA) Project

Presented by Winfield Wagner and Scott Edson

June 8, 2005


Before the project was started, the following mysterious warning was placed on an office whiteboard:

You have entered GJXDM land.

Enter @ your own risk and proceed with caution*

* The surgeon general has advised against prolong exposure to GJXDM


Symptoms

Speaking in a strange tongue where all the words start with J, G or X.

Mindlessly searching for a mythical land called “Namespace”

Answering all questions with “It all depends on what is “IS”?

Constantly screaming the words “Context” over and over again.


GJXDM Quarantine Area

Cubicles

(Empty)

(Empty)

(Empty)

Warning Sign

Winnie World


Attempt to Find a Cure

Send me on a SEARCH for a cure Found rest for me at a place called “OASIS”

(Tender Care) It was so bad that they “institutionalized”

me in IJIS Determined that there was no cure and it was

best that I help others at the First Annual GJXDM “USERS” conference If you don’t get this slide, there is still hope for

you yet…


Proof of Concept Overview

Integration of Law Enforcement and Port Activity Data for Anti-terrorism

Data sharing using Global Justice XML Data Model (GJXDM)

“Reusable” and standardized schemas (publication formats)

Concept-to-implementation in ~30 days


Proof-of-Concept Goals

Identify proven and reusable IT architecture and methodology for exchanging data

Implement reusable GJXDM schemas exchange standard

Demonstrate data sharing between: Local State Federal


RISA Proof of Concept Architecture

RMSAgent Memex

IntelligenceEngine

RMS

LAPP

Agent

CCHRSAgent

LAJDIG

GJXDMXML

GJXDMXML

GJXDMXML

LAC

SD HPD

DMZ

LASD Network

DataExchange Server

Installed on “LA-DEX” ServerFI Publication

FI Publication

Booking Publication

Subscriptions

GJXDMXML

MemexClient

Data Interface

KEY• CCJRS: Consolidated Criminal History Reporting System• DMZ: De-Militarized Zone • FI Publication: Field Interview Publication• GJXDM: Global Justice XML Data Model (Version 3.02)• LA-DEX: LASD Network Server• RMS: Records Management System

AGENCIES• LAC: Los Angeles County Sheriff’s Office• LAJDIG: Los Angles Joint Drug Intelligence Group• LAPP: Los Angeles Port Police• LASD: Los Angeles Sheriffs Department• SD HPD: San Diego Harbor Police


Reusable Publication Approach Start with a Generic Field Interview Publication Model

Review documentation from seven different agencies Create reference and subset schema with no extentions Test and implement at SDHPD Seven days

Reuse Publication Model for additional participating agencies One day No Changes to the reference and subset schema

Apply Publication Model approach to other document types and systems Booking Reports from LA County (two types) Reuse of Field Interview components of Standardized

representation of documents Three weeks


Getting Started

Education

Mind Your Own Business First (MYOB First)

Know Your Data (Warts and All)

Depend on the Kindness of Others

Identify Partners


Getting Started (Education)

Basic XML Office of Justice Programs Web Site:

http://www.it.ojp.gov Developer’s Workshops:

http://justicexml.gtri.gatech.edu/developerworkshop/

Oasis Technical Committees and Work Groups:http://www.oasis-open.org

Best Practices


Getting Started (MYOB First)

Solve a business problem first Identify data exchange in business terms Insure people talk before systems do Justice Information Exchange Model (JIEM):

http://www.search.org


Getting Started (Know Your Data)

Database structures and data elements

Input and output screens

Content to tag relations

Validation codes

Data problems and errors

Identify Core Components


Depend on the Kindness of Others

What has been done before by other agencies? Identify leaders that can assist you Contact agencies or organizations that support

the GJXDM IJIS Institute: http://www.ijis.org


Methodology for Building a GJXDM Schema

Analyze data required in Field Interview Document

Identify the domain model

Identify the relationships between the Domain Model and the GJXDM types

Identify basic core components between documents (reuse)



Field Interview Document

Incident

Reporting Organization

Activity Official.

Incident LocationLocation Address

Location Cross Street

Location Beat

Inciden Subject

Person Name

Person Alternative Name

Person Physical Details



Identify the domain objects and their elements using the GJXDM XML Tags

FieldInterview\Incident\IncidentSubject\PersonName\PersonFullName

Complete Name of the Primary Subject being Interviewed

FieldInterview\Incident\IncidentSubject\PersonName\PersonGivenName

First Name of the Primary Subject being Interviewed

FieldInterview\Incident\IncidentSubject\PersonName\PersonSurName

Last Name of the Primary Subject being Interviewed

FieldInterview\Incident\IncidentSubject\PersonName\PersonMiddleName

Middle Name of the Primary Subject being Interviewed

FieldInterview\Incident\IncidentSubject\PersonName\PersonSuffixName

Suffix added to the Name of the Primary Subject being Interviewed, such as Jr. III, etc.



Use the GJXDM Sub-schema Generator Tool to create document subset schema(s)

Validate subset schema Create instances of schema to validate content <PersonName>

<PersonGivenName>SMITH</PersonGivenName> <PersonMiddleName>JOHN</PersonMiddleName> <PersonSurName>MICHAEL</PersonSurName>

<PersonFullName> SMITH, MICHAEL JOHN</PersonFullName>

</PersonName>


Lessons Learned

Rely on a reusable Methodology Make the reference document schema

all inclusive Stay within the GJXDM vocabulary

(no extensions) Stay within the GJXDM grammar (hierarchy) Keep the schema application neutral


Lessons Learned

Use a publish/subscribe model, not point-to-point

Include text and code type elements for the same information

Consider data transformation Attempt to reuse “core component” packets from

one reference schema to another


Critical Success Factors

Availability of a leader in GJXDM Start off with a simple document or exchange Keeping within the GJXDM model One schema for all agencies (standard

reference document publication) Use a building block or component approach

to data integration User and practitioner participation is critical 95% Sharing Rule (walk before you can run)


GJXDM . . . Next Steps Institutionalization of a Development Methodology Development of a suite of GJXDM publication models Horizontal Conformity of Objects

(NIEMS Core Components) Cross Pollination of GJXDM and Other Standards

UBL and GJXDM Emergency Services Transportation DoD

Object Structures and Transaction Suites under the Reference Documents

New Version 3.0.3 and Beyond


Future Considerations

Privacy and Security GJXDM Database Structures Data Integrity SOA Real-time Transaction vs. Document

Publications Data Ownership vs. Stewardship


Since the project was completed, the following additional warning was added to the office whiteboard:

You have entered GJXDM land.

Enter @ your own risk and proceed with caution*

Have you had your NIEMS shot today?

* The surgeon general has advised against prolong exposure to GJXDM


Questions?

Winfield J. WagnerDirector of Integrated Justice Information SystemsCrossflo Systems, Inc.11995 El Camino Real, Suite 302San Diego, California 92130Office: 858-583-0333Fax: 858-724-7224Mobile: 858-525-1447Email: [email protected]

Scott Edson, LieutenantDirector of Law Enforcement Integration ServicesLos Angeles County, Information Systems Advisory Body12700 Center Court DriveSuite 500Cerritos, CA 90703Office: 562-345-4305Email: [email protected]

mailto:[email protected]

