[PRESENTATION]

Practical Integrated Justice and Public Safety

Overcoming Obstacles to Information Sharing at the City of Seattle

NAJIS 2007 ConferenceOctober 17, 2007

Bryan LepineDelivery Manager, Justice and Public

Safety Solutions

blepine@obsglobal.com(503) 221-4515

Presentation Objectives• Profile the information sharing initiatives at the City of Seattle

• Describe the benefits of a Service Oriented Architecture (SOA) guided, and Enterprise Service Bus (ESB) enabled implementation platform for Justice and Public Safety (J&PS) information sharing

• Elaborate upon the implementation specifics of NIEM/GJXDM compliant message exchanges and the value of data standards to the enterprise.

Seattle Legacy Architecture• Multiple Legacy Systems

some in process for change out others notmultiple disparate technologies

• Extensive Manual/Paper processesredundant data entryduplicationLimited and untimely access to data

• Reliance on point-to-point interfaces

modification to end point systems almost always required to support new data exchanges

• High cost of ownershiphigh support costslimited flexibilitylimited ability to adapt or grow the business.

PSAP Net

NCIC/III

SPD RMS

Finger-prints

Jail Booking

Mug-shots

LiNX Northwest

WA State Switch

DOL

RAIN

WA State Criminal

MCIS (Courts)

Fire CAD

DAMION (Law)

SPD CAD/

MCADFIRE RMS

Criminal History

Regional PSAPS

Prose-cutor

District Court

SPD Parking Citations

Paper

Paper

Paper

Pa

pe

r Pape

r

Paper

Point to Point Interface

Paper Process

Direct Access

In Development

A Model for Information Sharing• Seattle Justice Information Sharing (SeaJIS)

Police, Fire, Law and CourtEstablish automated exchanges of information

• Seattle Police Incident, Dispatch & Electronic Reporting (SPIDER)

Replace legacy CAD and RMS systemsReplace all data interfaces with a modern ESB architecture.

• Separate Projects with common goalsImprove access to informationEnhance the quality of the information receivedImprove security and reliabilityProvide an open, flexible and standards based technology architecture for current and future business requirements.

An Integrated J&PS Vision

Seattle J&PS Message Exchanges

SOA Realized…The Common Query

The Common Query User Interface

Seattle Message Architecture• Overview of Message Architecture

Support for endpoint native formatsNIEM/GJXDM Canonical model in the mediation layerData transformations via standard transformations (XSLT)NIEM becomes the Rosetta Stone between systemsEndpoint Systems no longer need to understand multiple message architectures (Publish once, subscribe many)Endpoint only knows about its own native message architecture and formats

Seattle Message Architecture• NIEM /GJXDM as inputs to Message Exchange Development

E-BookingBooking Confirmation, Charge Update, Completed Booking, Liar Notification, 72 Hour Release, Booking Recap

Common QueryCourt Case Initiation, Dispositions, Hearings, Warrants, Obligations

• Lessons Learned – The Case for NIEM Initial costs are higher than traditional Point-to-Point exchangesImproves future Interoperability with NIEM compliant systemsImproves Interoperability with existing systems through the use of a common vocabulary (King County)Simpler migration path to emerging standards/implementations – LEXS-SRLower cost of change over the life of the program – New data sources/systems

• Participation in the NIEM Community of InterestStatus: Adding IEPDs to NIEM portal.Remaining: Addition of Metadata, approval from internal stakeholders

Thank you