Reuse of GJXDM Components and IEPDs for Incident Report Exchanges Presented by: Winfield Wagner Joe Ramirez Scott Edson

1. Reuse of GJXDM Components and IEPDs for Incident Report Exchanges Presented by: Winfield Wagner Joe Ramirez Scott Edson September 7, 2006

2. Overview • What is a Reference Model IEPD? • Development and implementation history of the Incident Report Reference Model • Reference Model IEPD development life cycle concepts and components • Reuse of the reference model approach across domains

3. Incident Reference Model Time Line OLLESIN Components Initial Incident IEPD NJSP Installation LASO Components RISA Implementation SEARCH\COPS Workshop Review N-DEx Validation RISA Pilot NIEM IEPD 2005 2004 2007 2006

4. Reference IEPD “An expandable Information Exchange Package Document that represents all possible information collected over the life span of a specific document type and/or service and can represent the collected knowledge about the document or service, its initiating event or ongoing activities, and its state at any given point over its process life span.” “A accepted general representation or IEPD template of a document type and/or service that can be used as a component library for initiating the development of many different exchanges that represent pieces or part of the document type or service”

5. Reference IEPD Definition One Event Activity 1 Activity 2 IEP Process C Process A IEP Process B IEP Etc. Reference IEPD Reference Schema A Extension Schema A Subset Schema A

6. Reference Schema Definition Two Exchange 1 IEP 1 Process B Process A Document Schema A Reference IEPD Subset Schema Extension Schema Exchange 2 Document Schema B Process D IEP 2 Process C

7. Incident Reference IEPD Scope • Capture all possible information about an event and subsequent related law enforcement activities in which a law enforcement field officer or representative is required to respond to and document for the purpose of future review, analysis, investigation and/or adjudication • General Incident, Field Interview & Call for Service • Sources • ARJIS (Automated Regional Justice Information System) • Los Angeles Sheriffs Department • OLLESIN (Ohio Local Law Enforcement Information Sharing Network) • New Jersey State Police • FBI-NDEx Project • SEARCH/COP Reference IEPD Workshops

8. IEPD Implementation Benefits • Only one subset schema and extension schema for multiple exchanges (Consistency) • Reusable and understandable across jurisdictions and exchanges • Speeds up exchange development and implementation • Expandable without little or no impacting earlier installations of the IEPD

9. IEPD Implementation Benefits • Easier to convert to new standard’s versions or other standards such as NIEM • Reduces development costs • Can support different exchange implementation strategies service, transaction, document, etc. • Approach can be utilized for different business domains (PMP, Emergency Services, etc.)

10. Incident Reference Model Time Line LASO Components (General Incident) OLLESIN Components (Asset and M/O) NJSP Installation (Arrest) RISA Implementation Initial Incident IEPD (FI) SEARCH\COPS (N-DEx) N-DEx Validation NIEM IEPD RISA Pilot 2005 2004 2007 2006

11. Regional Information Sharing and Analysis (RISA) • Objective: Provide a predictive analysis capability to mitigate potential criminal and terrorist events • Benefits: • Cross-reference field incidents across multiple, regional data sources • Single, reusable, and scalable data interface for intelligence analysis engine HIGHLIGHTS • Disparate data sources including: Oracle, DB2, MS Access • GJXDM conforming • Operational < 45 days • First multi-jurisdictional data sharing project using GJXDM.

12. Regional Information Sharing and Analysis (RISA) Agent LAPP Agent LBPD SD Harbor Police Dept. DataExchange Server GJXDM XML Data GJXDM XML Data Agent HPD Agent Intel Analysis UPSD Agent USCG

13. New Jersey State PoliceData Augmentation • Objective: Extract Incident and Arrest data from NJSP Record Management System • Benefits: • Leverages core Incident Reference Model to create IEPD for NJSP and local/state/federal agencies • Provides reusable data sharing interface • Enhances critical SIMS time-sensitive decision processes • Minimal footprint to IT systems HIGHLIGHTS • Oracle 8i data source • GJXDM conforming • MQ Series Interface • ≈ 500,000 records • Complex mapping • Supports NIEM and other national standards.

14. New Jersey State Police Data Augmentation MQ Series NJSP RMS DataExchange Agent RMS JDBC MQ Adapter .xml File NJSP SIMS SIMS API .xml File

15. Incident Reference Model Time Line LASO Components (General Incident) OLLESIN Components (Asset and M/O) NJSP Installation (Arrest) RISA Implementation Initial Incident IEPD (FI) SEARCH\COPS (N-DEx) N-DEx Validation NIEM IEPD RISA Pilot 2005 2004 2007 2006

16. IEPD Life Cycle = Technicians Define the Exchange Mission Statement/ Implementation Guide = Practitioners Define Who, Where, When, Why, How Proof the Exchange Schema Validation Tool/ Application Test ConOps Use Cases JIEM Objects Initialization Testing and Implementation Business Process Model IEPD Repository Objects & Components IEPDs & Schemas Business Data Model Schema Package Development Standards Transformation Define What Create Exchange Structures UML Diagram / Object Type Listing / Content Rules Standards Model/ Properties & Types Listing Define Standards Models Standards Dictionaries/ Properties & Types Listing

17. Component or Object Analysis • Subject , who has a Name, Identification and Description, commits an reported offense, at a specific Location against a Victim who has a Name, Identification and Resident Address and was observed by a Witness, who has a Name and Identification • An Incident has a reported Subject, Victim and Witness (Context) who all of object type “Person”. • A Person may have Name, Identification and Residence (Components) • A Residence and Offense (Context Location are of object type Location • At the time the Officer (Who is a Person object type) reports (activity) the Incident, there is an Event (offense) and activities of a victim’s statement and witness’s statement

18. IEPD Reference Repository • Objects • Base UML Object or Component Diagrams • Base Properties and Types Spreadsheets • Subset Schema • GJXDM or Extension Context Objects • Base UML Context Object or Component Diagrams • Base Context Properties and Types Spreadsheets • Subset Schema • Extension Schema • Activities and event are captured as a separate Activity Object

19. Best Practices • Include objects and attributes the exchange will need today and in the future (logical not physical) • Consider all forms of data representation as a starting point to define attributes (database formats, forms, screen shots) and transform into real world descriptors • Always progress down to the base objects • Base Objects, Context Objects, Exchange Objects should be reused or added to the IEPD Repository • If new attributes are identified for an existing Object update the Object in the repository

20. Prescription Monitoring Program (PMP) • Prescription Data • Filled and reported by a pharmacy (Dispenser) • Internal and external activity associated with a Prescription • Investigative augmentation of information (Lint) • Patient, Prescriber, Dispenser, Drug and Subject • Processes (Transactions) • Request and Response • Alert • Prescription Record Transport • PMP Contacts and Requestors • Multiple Standards (GJXDM, NIEM, ASAP, etc.

21. In Conclusion Use of a Reference Schema: • Enables reusability • Provides a standard model for information sharing • Reduces development/implementation timelines for IEPDs and exchanges • Provides a framework for addressing future needs and strategies

22. Questions? Winfield J. Wagner Director of Integrated Justice Information Systems Crossflo Systems, Inc. 11995 El Camino Real, Suite 302 San Diego, California 92130 Office: 858-583-0333 Fax: 858-724-7224 Mobile: 858-525-1447 Email: wwagner@crossflo.com Scott Edson, Lieutenant Los Angeles County Sheriff's Department Law Enforcement Information Sharing Project 12440 E. Imperial Hwy., Suite 650 Norwalk, CA 90650 Office: 562-345-4305 Email: edson@LASD.org