Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. Practical Integrated Justice and Public Safety Overcoming Obstacles to Information Sharing at the City of Seattle NAJIS 2007 Conference October 17, 2007 Bryan Lepine Delivery Manager, Justice and Public Safety Solutions blepine@obsglobal.com (503) 221-4515
  2. 2. 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.
  3. 3. Seattle Legacy Architecture • Multiple Legacy Systems some in process for change out others not Point to Point Interface Paper Paper Process multiple disparate technologies Direct Access • Extensive Manual/Paper processes SPD Parking In Development LiNX redundant data entry Northwest Citations duplication MCIS Limited and untimely access to data RAIN SPD RMS Pape r DAMION Pa pe r (Courts) • (Law) Reliance on point-to-point interfaces modification to end point systems almost always required to support new er Pa Fire CAD p p SPD Pa Paper er CAD/ data exchanges PSAP Net MCAD FIRE RMS • High cost of ownership Regional PSAPS WA State Switch Jail high support costs Criminal History Booking Finger- prints limited flexibility DOL WA State Criminal Mug- limited ability to adapt or grow the Prose- cutor shots District Court business. NCIC/III
  4. 4. A Model for Information Sharing • Seattle Justice Information Sharing (SeaJIS) Police, Fire, Law and Court Establish automated exchanges of information • Seattle Police Incident, Dispatch & Electronic Reporting (SPIDER) Replace legacy CAD and RMS systems Replace all data interfaces with a modern ESB architecture. • Separate Projects with common goals Improve access to information Enhance the quality of the information received Improve security and reliability Provide an open, flexible and standards based technology architecture for current and future business requirements.
  5. 5. An Integrated J&PS Vision
  6. 6. Seattle J&PS Message Exchanges
  7. 7. SOA Realized…The Common Query
  8. 8. The Common Query User Interface
  9. 9. Seattle Message Architecture • Overview of Message Architecture Support for endpoint native formats NIEM/GJXDM Canonical model in the mediation layer Data transformations via standard transformations (XSLT) NIEM becomes the Rosetta Stone between systems Endpoint Systems no longer need to understand multiple message architectures (Publish once, subscribe many) Endpoint only knows about its own native message architecture and formats
  10. 10. Seattle Message Architecture • NIEM /GJXDM as inputs to Message Exchange Development E-Booking Booking Confirmation, Charge Update, Completed Booking, Liar Notification, 72 Hour Release, Booking Recap Common Query Court Case Initiation, Dispositions, Hearings, Warrants, Obligations • Lessons Learned – The Case for NIEM Initial costs are higher than traditional Point-to-Point exchanges Improves future Interoperability with NIEM compliant systems Improves Interoperability with existing systems through the use of a common vocabulary (King County) Simpler migration path to emerging standards/implementations – LEXS-SR Lower cost of change over the life of the program – New data sources/systems • Participation in the NIEM Community of Interest Status: Adding IEPDs to NIEM portal. Remaining: Addition of Metadata, approval from internal stakeholders
  11. 11. Thank you