Transcript Navigating the Standards Landscape

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!
1
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
PUBLIC’S MONEY, standards are important
because they will help to significantly lower the
lifecycle cost of sharing data
2
Justice & Public Safety
Standards Landscape
No Domain-wide standards prior to
September 11, 2001
Each agency re-defined, and each vendor
re-invented the wheel with every project
Evident and growing need to lower cost,
reduce risk, speed delivery and ensure
compatibility
 Homeland Security Presidential Directive
(HSPD-5) to improve information sharing
 2005 Justice and Homeland Security
partnership to develop National Information
Exchange Model (NIEM)
 Executive Order 13388 (replaced EO 13356)
3
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
4
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
5
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)
6
Justice XML Examples
Excerpt from a Criminal History Record (Rap Sheet)
Instance
<Person>
<PersonBirthDate>1953-02-12</PersonBirthDate>
<PersonName type=”Primary”>
<PersonPrefixName>Mr</PersonPrefixName>
<PersonGivenName>John</PersonGivenName>
<PersonMiddleName>P</PersonMiddleName>
<PersonSurName>Jones</PersonSurName>
<PersonSuffixName>Jr</PersonSuffixName>
</PersonName>
<PersonPhysicalFeature>
<PhysicalFeatureDescriptionText>dragon tattoo on right
forearm</PhysicalFeatureDescriptionText>
</PersonPhysicalFeature>
</Person>
7
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)
8
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
9
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
XSTF
GISWG
NIJ
NIBRS
OASIS
LegalXML
ISO/IEC
W3C
ASC
X12.org
XML.gov
UN/CEFACT
ebxml.org
Intelligence
Community
ICML
US DoD
DublinCore.org
Standards
10
Total Components
JXDM Content
2754 Total data components
(545 types + 2209 properties)
1%
3%
6%
Property
397
4%
6%
1216 Activity
Misc Metadata
116
177
Activity
1216
Person
543
45%
543 Person
397 Property
178 Location
33 Contact Information
94 Organization
14%
177 Miscellaneous
21%
116 Metadata
11
National Information Exchange
Model (NIEM)
12
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
13
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
14
NIEM Data Component
Represent real-world objects and concepts
Person
Address
Zip
Code
DOB
Name
City
Sex
State
15
NIEM data component re-use
and extension
Universal
Person
Justice
Person
Immigration
Person
16
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
17
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)
18
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
19
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
20
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.
21
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
22
IEPDs as Standards
IEPD
23
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)
24
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
25
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
26
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)
27
Gang Affiliation Registration
Database System
NIST
TCIS
CAL GANGS
GARDS
Emit
Justice XML
Message Broker
CWS
Gang Member Alert
Date Ordered to Reg
Date Registered
Agency Registered
28
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
29
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 ID’s
 Rapsheets (Priors)
CCHRS
AJIS
Arrest Information
Arrest Disposition
Local LAFIS Fingerprint ID
Livescan Station
Fingerprints
Arrest Booking
Booking Photo
ISAB
Integration
Broker
 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
30
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
31
Standard Functional Specifications
for Law Enforcement CAD & RMS
http://it.ojp.gov and www.leitsc.org
32
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.
33
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)
34
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
35
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
36
LEITSC Contact Information
Heather Ruzbasan
LEITSC Project Manager
703-836-6767 ext. 275
[email protected]
www.leitsc.org
37
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
38
OJP Information Site
www.it.ojp.gov
39
NIEM Information Site
www.niem.gov
40
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
41
Thank you!
Andrew Owen
SEARCH, The National Consortium
for Justice Information and Statistics
916-215-393
[email protected]
Lt. Scott Edson
Los Angeles County Sheriff’s Department
Law Enforcement Information Sharing Program
(562) 345-4305
[email protected]
42
Questions ?
XM
L
43