Copyright  2006 Crossflo Systems, Inc. All Rights Reserved Reuse of GJXDM Components and IEPDs for Incident Report Exchanges Presented by: Winfield Wagner Joe Ramirez Scott Edson September 7, 2006

Copyright  2006 Crossflo Systems, Inc. All Rights Reserved 2Overview What is a Reference Model IEPD? What is a Reference Model IEPD? Development and implementation history of the Incident Report Reference Model Development and implementation history of the Incident Report Reference Model Reference Model IEPD development life cycle concepts and components Reference Model IEPD development life cycle concepts and components Reuse of the reference model approach across domains Reuse of the reference model approach across domains

Copyright  2006 Crossflo Systems, Inc. All Rights Reserved 3 Incident Reference Model Time Line RISA Implementation RISA Pilot NJSP Installation LASO Components NIEM IEPD N-DEx Validation SEARCH\COPS Workshop Review OLLESIN Components Initial Incident IEPD

Copyright  2006 Crossflo Systems, Inc. All Rights Reserved 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”

Copyright  2006 Crossflo Systems, Inc. All Rights Reserved 5 Reference IEPD Definition One Process A IEP Process B Reference Schema A Extension Schema A Subset Schema A EventActivity 1 IEP Process C Activity 2 IEP Etc. Reference IEPD

Copyright  2006 Crossflo Systems, Inc. All Rights Reserved 6 Reference Schema Definition Two Process A IEP 1 Process B Document Schema A Process C IEP 2 Process D Document Schema B Extension Schema Subset Schema Exchange 1 Reference IEPD Exchange 2

Copyright  2006 Crossflo Systems, Inc. All Rights Reserved 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 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 General Incident, Field Interview & Call for Service Sources Sources ARJIS ( Automated Regional Justice Information System ) ARJIS ( Automated Regional Justice Information System ) Los Angeles Sheriffs Department Los Angeles Sheriffs Department OLLESIN ( Ohio Local Law Enforcement Information Sharing Network ) OLLESIN ( Ohio Local Law Enforcement Information Sharing Network ) New Jersey State Police New Jersey State Police FBI-NDEx Project FBI-NDEx Project SEARCH/COP Reference IEPD Workshops SEARCH/COP Reference IEPD Workshops

Copyright  2006 Crossflo Systems, Inc. All Rights Reserved 8 IEPD Implementation Benefits Only one subset schema and extension schema for multiple exchanges (Consistency) Only one subset schema and extension schema for multiple exchanges (Consistency) Reusable and understandable across jurisdictions and exchanges Reusable and understandable across jurisdictions and exchanges Speeds up exchange development and implementation Speeds up exchange development and implementation Expandable without little or no impacting earlier installations of the IEPD Expandable without little or no impacting earlier installations of the IEPD

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

Copyright  2006 Crossflo Systems, Inc. All Rights Reserved 10 Incident Reference Model Time Line RISA Implementation RISA Pilot NJSP Installation (Arrest) LASO Components (General Incident) NIEM IEPD N-DEx Validation SEARCH\COPS (N-DEx) OLLESIN Components (Asset and M/O) Initial Incident IEPD (FI)

Copyright  2006 Crossflo Systems, Inc. All Rights Reserved 11 Regional Information Sharing and Analysis (RISA) Objective: Provide a predictive analysis capability to mitigate potential criminal and terrorist events Objective: Provide a predictive analysis capability to mitigate potential criminal and terrorist events Benefits: 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. HIGHLIGHTS Disparate data sources including: Oracle, DB2, MS Access GJXDM conforming Operational < 45 days First multi-jurisdictional data sharing project using GJXDM.

Copyright  2006 Crossflo Systems, Inc. All Rights Reserved 12 Regional Information Sharing and Analysis (RISA) HPD UPSD GJXDM XML Data LAPP LBPD DataExchange Server Intel Analysis GJXDM XML Data SD Harbor Police Dept. USCG Agent

Copyright  2006 Crossflo Systems, Inc. All Rights Reserved 13 New Jersey State Police Data Augmentation Objective: Extract Incident and Arrest data from NJSP Record Management System Objective: Extract Incident and Arrest data from NJSP Record Management System Benefits: 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. HIGHLIGHTS Oracle 8i data source GJXDM conforming MQ Series Interface ≈ 500,000 records Complex mapping Supports NIEM and other national standards.

Copyright  2006 Crossflo Systems, Inc. All Rights Reserved 14 New Jersey State Police Data Augmentation JDBC DataExchange Agent MQ Adapter RMS NJSP RMS.xml File API SIMS.xml File NJSP SIMS MQ Series

Copyright  2006 Crossflo Systems, Inc. All Rights Reserved 15 Incident Reference Model Time Line RISA Implementation RISA Pilot NJSP Installation (Arrest) LASO Components (General Incident) NIEM IEPD N-DEx Validation SEARCH\COPS (N-DEx) OLLESIN Components (Asset and M/O) Initial Incident IEPD (FI)

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

Copyright  2006 Crossflo Systems, Inc. All Rights Reserved 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 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”. 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 Person may have Name, Identification and Residence (Components) A Residence and Offense (Context Location are of object type Location 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 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

Copyright  2006 Crossflo Systems, Inc. All Rights Reserved 18 IEPD Reference Repository Objects Objects Base UML Object or Component Diagrams Base UML Object or Component Diagrams Base Properties and Types Spreadsheets Base Properties and Types Spreadsheets Subset Schema Subset Schema GJXDM or Extension Context Objects GJXDM or Extension Context Objects Base UML Context Object or Component Diagrams Base UML Context Object or Component Diagrams Base Context Properties and Types Spreadsheets Base Context Properties and Types Spreadsheets Subset Schema Subset Schema Extension Schema Extension Schema Activities and event are captured as a separate Activity Object Activities and event are captured as a separate Activity Object

Copyright  2006 Crossflo Systems, Inc. All Rights Reserved 19 Best Practices Include objects and attributes the exchange will need today and in the future (logical not physical) 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 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 Always progress down to the base objects Base Objects, Context Objects, Exchange Objects should be reused or added to the IEPD Repository 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 If new attributes are identified for an existing Object update the Object in the repository

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

Copyright  2006 Crossflo Systems, Inc. All Rights Reserved 21 In Conclusion Use of a Reference Schema: Enables reusability Enables reusability Provides a standard model for information sharing Provides a standard model for information sharing Reduces development/implementation timelines for IEPDs and exchanges Reduces development/implementation timelines for IEPDs and exchanges Provides a framework for addressing future needs and strategies Provides a framework for addressing future needs and strategies

Copyright  2006 Crossflo Systems, Inc. All Rights Reserved 22 Questions? Winfield J. Wagner Director of Integrated Justice Information Systems Crossflo Systems, Inc El Camino Real, Suite 302 San Diego, California Office: Fax: Mobile: Scott Edson, Lieutenant Los Angeles County Sheriff's Department Law Enforcement Information Sharing Project E. Imperial Hwy., Suite 650 Norwalk, CA Office: