1 / 25

Case Study on the Regional Information Sharing and Analysis (RISA) Project

Case Study on 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.

javierpage
Download Presentation

Case Study on the Regional Information Sharing and Analysis (RISA) Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Case Studyon theRegional Information Sharing and Analysis (RISA) Project Presented by Winfield Wagner and Scott Edson June 8, 2005

  2. 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

  3. 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.

  4. GJXDM Quarantine Area Cubicles (Empty) (Empty) Warning Sign (Empty) Winnie World

  5. 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…

  6. 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

  7. 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

  8. Data Interface LAC Booking Publication GJXDM XML CCHRS DataExchange Server LAJDIG LASD Network SD HPD Agent Agent Agent Installed on “LA-DEX” Server FI Publication Memex Intelligence Engine GJXDM XML GJXDM XML RMS Subscriptions Memex Client DMZ LAPP FI Publication GJXDM XML RMS • 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 • 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 RISA Proof of Concept Architecture

  9. 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

  10. Getting Started • Education • Mind Your Own Business First (MYOB First) • Know Your Data (Warts and All) • Depend on the Kindness of Others • Identify Partners

  11. 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

  12. 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

  13. 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

  14. 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

  15. 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)

  16. Methodology for Building a GJXDM Schema

  17. Methodology for Building a GJXDM Schema • Identify the domain objects and their elements using the GJXDM XML Tags

  18. Methodology for Building a GJXDM Schema • 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>

  19. 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

  20. 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

  21. 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 approachto data integration • User and practitioner participation is critical • 95% Sharing Rule (walk before you can run)

  22. 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

  23. Future Considerations • Privacy and Security • GJXDM Database Structures • Data Integrity • SOA • Real-time Transaction vs. Document Publications • Data Ownership vs. Stewardship

  24. 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

  25. 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 Director of Law Enforcement Integration Services Los Angeles County, Information Systems Advisory Body 12700 Center Court Drive Suite 500 Cerritos, CA 90703 Office: 562-345-4305 Email: edson@LASD.org

More Related