Navigating the Standards Landscape Andrew Owen, SEARCH Lt. Scott Edson, L.A. County Sheriff Navigating the Standards Landscape The Business Case: How do standards help the practitioner to develop an information sharing architecture? Data Exchange Standards: XML, JXDM and NIEM IEPDs and Components Los Angeles County Case Study LEITSC Functional Standards for Law Enforcement Records Management and CAD How Do I Connect the Silos? Here is the Help!
2 The Business Case - What Standards Provide On-demand real time data access by decision makers Standard products from vendors at lower cost Opportunity to leverage legacy system investment Phased evolution to emerging technologies approach If you care about PUBLIC SAFETY, standards are important because these standards can help you deliver emergency services more quickly, with greater dependability If you care about ACCOUNTABILITY FOR THE PUBLICS MONEY, standards are important
because they will help to significantly lower the lifecycle cost of sharing data 3 Justice & Public Safety Standards Landscape No Domain-wide standards prior to September 11, 2001 Each agency re-defined, and each vendor reinvented the wheel with every project Evident and growing need to lower cost, reduce risk, speed delivery and ensure compatibility Homeland Security Presidential Directive (HSPD5) to improve information sharing 2005 Justice and Homeland Security partnership to develop National Information Exchange Model (NIEM) Executive Order 13388 (replaced EO 13356) 4
Data Exchange Standards: XML Receiving System Processes the data Parser Reads the data XML Schema defines the structure of the data Data from System1 Data from System 2 Data from
System 3 Data from System 4 5 Data Exchange Standards: XML XML provides a natural way to build new vocabularies or languages XML tools (parsers, validators, native XML databases) are abundant, relatively inexpensive and can support any and every vocabulary that conforms to the XML standard XML allows us to express information in a way that is platform independent 6
Data Exchange Standards: XML XML can represent all parts of the information exchange Information that needs to be shared; Information about this information (who created it, when, why, etc.); Information about destination of this information (addressing, routing); Security and authorization information (sensitivity level, who can read it, how it should be disposed of, etc.); Validation and verification rules (XML schema, DTD, business rules) 7 Justice XML Examples Excerpt from a Criminal History Record (Rap Sheet)
Instance 1953-02-12MrJohnPJonesJrdragon tattoo on right forearm 8 XML Vocabularies
Uniform Business Language (UBL) Electronic Business XML (ebXML) Extensible Access Control Markup Language (XACML) ACORD XML for Life Insurance eXtensible Business Reporting Language (XBRL) EDXL (OASIS Emergency Management) Global Justice XML Data Model (G)JXDM) National Information Exchange Model (NIEM) 9 XML: Building blocks for information exchange JXDM started as a grass-roots effort to define a common XML vocabulary for criminal justice and public safety
JXDM provides fairly large objects, reflecting the broad scope of the effort and attempts to accommodate needs of everyone across the wide spectrum JXDM includes constructs not native to criminal justice, such as health or intelligence created without a benefit of the subject matter expertise 10 JXDM Evolution Communities of Interest Data Dictionary Reconciliation: LegalXML, RISS, and RAP AAMVA
Driver History Local, County, and State Representatives SEARCH JIEM Tool Exchanges IACP CrimNet CISA Nlets
Intelligence Community ICML US DoD DublinCore.org Standards 11 JXDM Content 2754 Total data components (545 types + 2209 properties) Misc Metadata Org 116 94 177 Locatio
n 178 Property 397 Activity 1216 Person 543 12 National Information Exchange Model (NIEM) 13 JXDM and NIEM
NIEM aggregates knowledge from multiple domains, where each community of interest (COI) maintains its own domain and contributes to the common set; NIEM, having much broader audience in mind from the beginning, took a different approach than the JXDM to develop core objects: Start with smallest, universally understood and usable; Specialize for the particular exchanges, common to some or many; Provide a space for additional specialization relevant to a specific area 14 National Information Exchange Model
The minimum supported set for all participating domains; universally understood; very stable; minimal or no subsetting Core: jointly governed through the NIEM governing body 15 NIEM Data Component Represent real-world objects and concepts Person Address DOB Name
City Sex Zip Code State 16 NIEM data component re-use and extension Universal Person Justice Person
Immigration Person 17 NIEM 1.0 Partitioned into multiple NIEM domains Includes Universal, Common, and Structures namespaces (Core) Re-factors data components across all namespaces Implements Associations Roles Metadata Type Augmentation Re-factors some specialization occurrences into augmentation, associations, roles, and metadata Uses original GJXDM 3.0.3 PropertyType and
ActivityType 18 NIEM 1.0 Content: Customs and Border Protection / International Trade Emergency Management Immigration and Customs Enforcement Infrastructure Protection Intelligence Justice Person Screening External standards (Geospatial, EDXL) 19 Requirements for JXDM
4.0/NIEM 2.0 release All proposed 4.0 functionality NIEM Naming and Design Rules (NDR) compliance Version independence Lessons learned from NIEM 1.0 implementations Commitment from NIEM PMO to support local and state pilots 20 NIEM 2.0/ Harmony (2007) NIEM 2.0 will converge GJXDM 3.0.3, JXDM 4.0, and NIEM 1.0 into one release with built-in migration support to subsequent NIEM releases. GJXDM 3.0.3 NIEM 1.0
JXDM 4.0 NIEM 2.0 JXDM 4.0 NIEM 2.0 summary: Multi-domain, refactored PropertyType and ActivityType; associations, roles, metadata, type augmentation, flexible code lists, URI for each component, database export, and integrated support tools 21 IEPDs An Information Exchange Package (IEP) begins with a business need for a particular exchange. IEP Documentation (IEPD) describes how that
exchange should be expressed using the NIEM. The IEPD is a key point for introducing new elements to NIEM and for reusing existing ones. An IEPD itself can also be reused in whole or in part to speed development and lower the cost of sharing information. 22 The Value of IEPDs Establish standards to ensure semantic interoperability Interoperability can dramatically reduce the cost and risk of implementing
information exchanges Interoperability increases agility 23 IEPDs as Standards IEPD 24 JXDM and NIEM Specifications Biometrics (ANSI-NIST ITL-2006) FBI Electronic Fingerprint Transmission Specification (EFTS) Uniform Rap Sheet NCIC 2000 Sex Offender, Serious Violent Offender,
Wants, Warrants, Hot Files Protection Orders OASIS Court Filing 3.0 NDeX (NIEM 1.0) 25 Los Angeles County THIS IS THE COUNTY Los Angeles, California 10 Million County Residents 88 Incorporated Cities 4,084 Square Miles 45 Independent Police Departments Over 92k Budgeted Employees 30% in Law and Justice 26
Los Angeles County Examples Business Problem: Unfunded State Propositions Message exchange among all law enforcement agencies Business Needs: DNA collection orders and proof of collection Gang registration and notification to agencies Real-time information from new and old proprietary disparate systems across multiple agencies and jurisdictions Security and accountability for access to the information Provide for future growth and connectivity to other systems 27
Implementation Strategies Expanding LA County Justice Integration Services Infrastructure for new integrated applications such as DOTS and GARDS Developing Justice XML messages and documents (Livescan Returns, FBI Rapsheets, etc) for reuse Leveraging selective legacy application functionality with WebService enablement Piloting deployment of XML Security, schema validation, auditing and monitoring as a common shared service utilizing XML Security Appliance(s) 28 Gang Affiliation Registration Database System NIST
CAL GANGS TCIS Emit GARDS Justice XML Message Broker CWS Gang Member Alert Date Ordered to Reg Date Registered Agency Registered 29
DNA Offender Tracking System Law Enforcement Criminal History Records CCHRS Superior Court Juvenile CMS. JAI Courts Sheriff LAFIS Superior Court Adult CMS.
TCIS Prosecution Prosecutors Info. System PIMS DOTS Jail Mgt. System AJIS Adult State Criminal History ACHS Justice Enterprise Integration Broker
Sheriff Message Broker JDIC FBI IAFIS Justice Enterprise EDMS FBI Federal Rapsheet FBI Cal-DOJ State
AFIS 30 DNA Offender Tracking System DOTS CA-D O J FBI -D O J AFIS Fingerprint matching Issue State ID Number Return Match State Rapsheet IAFIS Fingerprint matching Issue FBI Number
Return Match FBI Rapsheet Arrest Information Fingerprint IDs Rapsheets (Priors) CCHRS ISAB Integration Broker Arrest Information Arrest Disposition Local LAFIS Fingerprint ID Livescan Station Fingerprints Arrest Booking
Booking Photo Add Arrest Record Add D.A. Reject Local Rapsheet DNA Status (On file, Required, Court Order, Recollect,.. ) PIMS PIMS Arrest Information Prosecution Case Filing (Notice to collect DNA) D.A. Reject 19
31 Implementing Advantages Reusable components Future projects can benefit Opportunity to improve business processes Use Messaging design and modeling Opportunity to quickly add business processes Reduce future project costs 32 Standard Functional Specifications for Law Enforcement CAD & RMS http://it.ojp.gov and www.leitsc.org
33 Standard Functional Specifications for Law Enforcement CAD & RMS Serve as a starting point for law enforcement agencies to use when developing CAD or RMS RFPs. Level the playing field when working with vendors. Streamline the process and lower the cost of implementing and maintaining a CAD or RMS. Promote interoperability & information sharing. 34 Standard Functional Specifications
for Law Enforcement CAD & RMS 5 Business Functions for a CAD System Law Enforcement Dispatch CAD System Administration Support Services Call Management & Management Reporting Interfaces (internal and external) 35 Standard Functional Specifications for Law Enforcement CAD & RMS Highlights 25 Business Functions for a RMS
Master Indices Calls for Service Incident Reporting Investigative Case Management Property & Evidence Management Warrant Arrest Booking Juvenile Contact
Traffic Accident Reporting Citation Field Contact
Pawn Civil Process Protection Order & Restraints Permits & Licenses Equipment & Asset Management Fleet Management Personnel Internal Affairs Analytical Support RMS Reports RMS System Administration RMS Interfaces 36 CAD & RMS IEPDs
GJXDM 3.0.3 RMS Summary Response RMS Query CAD to RMS Transfer CAD Unit Status Update CAD Request Status Update CAD Resource Availability Query CAD Resource Availability Response CAD Request for Resource CAD Summary Call for Service CAD Detailed Call for Service 37 LEITSC Contact Information Heather Ruzbasan LEITSC Project Manager 703-836-6767 ext. 275 [email protected]
www.leitsc.org 38 How Do I Connect the Silos? Resources ! Available today OJP and NIEM web sites SEARCH JIEM IEPD Tool JXDM - NIEM Spreadsheets NCSC Wayfarer Search Tool Schema Subset Generation Tools Unified Modeling Language Tools JXDM and NIEM National Virtual Help Desk GTTAC Technical Assistance and Training 39
OJP Information Site www.it.ojp.gov 40 NIEM Information Site www.niem.gov 41 SEARCH JXDM/JIEM/NIEM Initiatives XML Structure Task Force (XSTF) Global Training and Technical Assistance Committee (GTTAC) IJIS Institute XML Committee Technical Assistance and Training (G) JXDM User Guide
Sponsor 1st Annual (G) JXDM User Conference Lead developer of Reference Information Exchange Package Documentation (IEPDs) JXDM-NIEM National Virtual Help Desk support Global and NIEM committees 42 Thank you! Andrew Owen SEARCH, The National Consortium for Justice Information and Statistics 916-215-393 [email protected] Lt. Scott Edson Los Angeles County Sheriffs Department Law Enforcement Information Sharing Program (562) 345-4305
TD3 TOP UP New & Updates * Toyota Intune (What is it?) To ensure the quality and maintenance of all our TD3 devices in Europe, TME started a roll out and training program in a software management solution (Intune) for...
Meta Tags Make sure your web includes Meta Name: Title Keywords Description. Use HTML example or Meta Tag Generator. Keywords Choose keywords related to your site. Use keyword phrases to narrow competitive keywords. Use bold font for keywords. Use each...
Introduction To Colbree. Colbree Precision Ltd is an engineering subcontract company which supplies CNC Turning. CNC Milling, CNC Fabrication, Water Jet Cutting, 3D Routing, Mechanical Assembly services and product management from concept to market launch.
SIMS 247: Information Visualization and Presentation Jeffrey Heer Visual Analytics / The InfoVis Design Space Aug 31, 2005 why does this suck? some of the reasons it sucks y-axis unlabeled y-axis at poor scale needless use of 3D bar chart...
Coast Guard FOSC-R have a tendency to apply Oil Response/Enforcement elements to Chemical spills. PQS will be covered, but will be presented from both CERCLA and OPA perspectives . All FOSC-R need to be mindful of differences. CERCLA authority and...
2007 RCI ANNUAL CONFERENCE Health & Welfare of the Equine Athletes PANELISTS Dan Fick on Welfare & Safety Summit Bill Casner on shoeing & toe grabs Dr. Mary Scollay on uniform on-track injury reporting Dr. Mick Peterson on racing surfaces...