Navigating the Standards Landscape

Catherine Plummer, SEARCHMike Haslip, Blaine, WA Police Dept

2

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 JIEM, IEPDs and ComponentsWhatcom County, Washington Case StudyLEITSC Functional Standards for Law Enforcement Records Management and CADHow Do I Connect the Silos? Here is the Help!

4

The Business Case - What

Standards ProvideOn-demand real time data access by decision makersStandard products from vendors at lower costOpportunity to leverage legacy system investmentPhased evolution to emerging technologies approachIf you care about PUBLIC SAFETY, standards are important because these standards can help you deliver emergency services more quickly, with greater dependabilityIf 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

5

Justice & Public Safety Standards Landscape

No Domain-wide standards prior to September 11, 2001Each agency re-defined, and each vendor re-invented the wheel with every projectEvident and growing need to lower cost, reduce risk, speed delivery and ensure compatibilityExecutive Order 13388 andHomeland Security Presidential Directive

(HSPD-5) to improve information sharing2005 Justice and Homeland Security

partnership to develop National Information Exchange Model (NIEM)

6

Data from System 4

Data from System 3

Receiving SystemReceiving SystemProcesses the dataProcesses the data

ParserReads the data

Data from System1

Data from System 2

XML Schema defines the structureof the data

Data Exchange Standards: XML

7

Data Exchange Standards: XML

XML provides a natural way to build new vocabularies or languagesXML tools (parsers, validators, native XML databases) are abundant, relatively inexpensive and can support any and every vocabulary that conforms to the XML standardXML allows us to express information in the operating system/computer architecture/ language independent way

8

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)

9

Criminal History Record (Rap Sheet) Instance

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

Justice XML Examples

10

XML Vocabularies

Uniform Business Language (UBL)Electronic Business XML (ebXML) Extensible Access Control Markup Language (XACML)ACORD XML for Life InsuranceeXtensible Business Reporting Language (XBRL)EDXL (OASIS Emergency Management)Global Justice XML Data Model (G)JXDM)National Information Exchange Model (NIEM)

11

XML: Building blocks for information exchange

JXDM started as a “grass-roots” effort to define a common XML vocabulary for criminal justice and public safetyJXDM provides fairly large objects, reflecting the broad scope of the effort and attempts to accommodate needs of everyone across the wide spectrumJXDM includes constructs not “native” to criminal justice, such as health or intelligence – created without a benefit of the subject matter expertise

12

JXDM Evolution

ISO/IECW3C

UN/CEFACTebxml.orgASC

X12.org

XML.gov

OASISLegalXML

DublinCore.org

US DoD

IntelligenceCommunity

ICML

Standards

Nlets

AAMVADriver History

SEARCHJIEM Tool

Exchanges

Data DictionaryReconciliation:

LegalXML, RISS, and RAP

IACP

GISWG

NIJ

CrimNetCISA

NIBRS

Local, County,and State

Representatives

Communities of Interest

XSTF

13

2754 Total data components

(545 types + 2209 properties)

Activity1216

Person543

Property397

Location 178

Metadata116

Misc177Org 94

JXDM Content

14

Doc.xsdDoc.xsd

IncidentRpt

IncidentRpt

BookingRpt

BookingRpt Charge

DocCharge

Doc

CaseFile

CaseFile

ArrestWarrantArrest

WarrantArrest

RptArrest

Rpt

ProtectOrder

ProtectOrder

SentenceOrder

SentenceOrder

ActivityActivity

PersPers

LocLoc

CntCnt

PropPropOrgOrg

??????

DocDocRelateRelate

IncidentIncident

ActivityActivity

InvestigateInvestigate

ArrestArrest

BookBook ConfineConfine

ProsecuteProsecute

IndictIndict AdjudicateAdjudicate SentenceSentence

IncarcerateIncarcerate

BondBond

SuperviseSupervise

ReleaseRelease

ChargeCharge

PardonPardonParoleParole

FineFine

Information Exchange Packages

15

Reconciling XML business vocabularies

Goal is to describing data objects relevant to the business problem in a consistent and re-usable format. Two different organizations may express two different concepts with the same XML tag. Example:<dmv:Person.identification> in the DMV

environment could mean driver’s license.<immigration:Person.identification> in the

ICE environment could mean passport.Business vocabularies should be reconciled for the purpose of the information exchange

16

National Information Exchange Model (NIEM)

17

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

18

NIEM Data Component

19

NIEM data component re-use and extension

Universal Person

Justice Person

Immigration Person

20

NIEM Core (a collection of namespaces)

Justicenamespace

Justicenamespace

Emergency Mgt namespace

Emergency Mgt namespace

Immigration namespaceImmigration namespace

IntelligencenamespaceIntelligencenamespace

Universal namespaceUniversal

namespace

Common namespaceCommon

namespace

StructuresnamespaceStructuresnamespace

BloodTypeCode

BloodTypeCodeType

Governed by XSTF-like committees that coordinate and cooperate with

the NIEM governing body

NIEM Participants: (1) Bring domain content to NIEM.(2) Conform to NIEM NDR.(3) Agree to NIEM governance

policies and procedures.(4) Participate in NIEM governance.

Core: jointly governed through the NIEM governing body

The minimum supported set for all participating domains;universally understood; very

stable; minimal or no subsetting

Where tiger teams operate

Domains

Core

National Information Exchange Model

21

JXDM 3.1 Vision

First major revision of JXDM Implements associations and roles with metadata Implements flexible metadata containers Structures namespace PropertyType and ActivityType completely

refactored No proxy schemas are used for code lists External enumeration updates

NCIC: break some table dependencies (e.g., make/model)

New content NHTSA crash data Intelligence

22

NIEM 1.0

Partitioned into multiple NIEM domains (including Justice)Includes Universal, Common, and Structures namespaces (Core)Re-factors data components across all namespacesImplements Associations Roles Metadata Type Augmentation

Re-factors some specialization occurrences into augmentation, associations, roles, and metadataUses original GJXDM 3.0.3 PropertyType and ActivityType

23

NIEM 1.0

Content – (in addition to Justice): Immigration and Customs EnforcementCustoms and Border Protection /

International Trade IntelligenceEmergency Management Infrastructure ProtectionPerson ScreeningExternal standards (Geospatial, EDXL)

24

Requirements for JXDM 4.0/NIEM 2.0 release

All proposed 4.0 functionalityNIEM Naming and Design Rules (NDR) complianceVersion independenceLessons learned from NIEM 1.0 implementationsCommitment from NIEM PMO to support

local and state pilots

25

NIEM 2.0/ Harmony (2007)

GJXDM 3.0.3

JXDM 4.0

NIEM 1.0

NIEM 2.0

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.

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

JXDM 4.0

26

NIEM IEPD Lifecycle

27

How JIEM and SSGT interoperate

Schema Subset Generation Tool (SSGT)

JIEM SSGT Mapping Tool

.XMI

ArgoUML

Wantlist

Mapping Report

SSGT

Subset.zip

28

JXDM and NIEM Specifications

Biometrics (ANSI-NIST ITL-2006)FBI Electronic Fingerprint Transmission

Specification (EFTS)Uniform Rap SheetNCIC 2000

Sex Offender, Serious Violent Offender, Wants, Warrants, Hot Files Protection Orders

OASIS Court Filing 3.0NDeX (NIEM 1.0)

29

WENET: Addressing a disconnected reality

Whatcom County Washington Over 2 million justice records and names, spread

across a dozen city, county, tribal, and state university agencies on disparate, proprietary systems

Several systems over 15 years old County ‘system’ a loose collection of programs and

applications (DB2 on system 36 and AS400 Wide variety of platforms and applications in

outlying agencies Little / No connectivity Limited funding No Statewide RMS capacity A Strong Desire to Share

30

Whatcom County Washington Example

Business Problem: A dozen agencies and millions of records connected

by people, telephones and notepads. Different data models, data integrity rules, and

definitionsBusiness Needs: Provide lookup of real-time justice case, arrest,

booking and case management information from a variety of proprietary disparate systems across multiple agencies and jurisdictions

Maintain or improve security and accountability for access to current information

Provide for future growth and connectivity to other / larger systems (ARJIS, LINx, N-DEx, etc)

31

WENET – Game Plan and Technical Concept

Whatcom Exchange NETwork (WENET) Utilizes information sharing standards to maximize available resources and ensure future compatabilityallows inquiry of XML data based on the Justice XML Data Dictionary

3.0 via HTTP utilizing XPath queries Secured with client authenticated SSL and

digital certificates.FOR MORE INFO...

Project specs:http://www.whatcomcounty.us/apps/wenet/

32

WENET Topology

Client

PrivateExtranet

AS400

LongarmCMI JusticeNewWorld

Etc

HTTP Server

HTTP Server

Proxy /HTTP Server

Whatcom CountyOther Agencies

HTTP GET

XMLresponse

HTTP GET

XMLresponse

33

WENET Phased implementation

1. Define a technical specification and means to inquire disparate law and justice records management systems.2. Implement services using the technical specification for the disparate SQL and IBM RMS, and connect the services.3. Create clients that take advantage of the shared data. Extend existing applications to allow searching of shared data.4. Develop methods to import retrieved data into the RMSes to better utilize data.

34

Pre-WENET Development Environment

Prior to implementing GJXDM, custom conversion programming was required for each legacy system: Limited code reuseExtended (multi-year) development timeSerial development activity

35

Successful Project metrics

Jail and prosecutor record lookups:Over 15 minutes each of three people’s

time, reduced to seconds by one personGJXDM compliance and mapping benefits2 million + records15+ years of casesProjects subsequent to mapping estimated

at much lower costs of legacyDesign, build and implementation of countywide pawn program completed in months

36

Future GJXDM Projects

Extend access outside county region Sharing record query with vetted local, tribal,

county, state and federal partners LINx-NW, ARJIS, N-DEx

E-Filing Electronic transmission of case information

from law enforcement to prosecutorFull connectivity to all member agenciesTwo way query access Information capture, automated update,

alerts

37

Implementing Advantages

Reusable components Future projects can benefit

Opportunity to improve business processesUse Case design and modeling

Improved communication between information provider and project teamReduce overall project delivery timeConversions are now averaging 6 to 9

monthsReduce overall project costs

38

JXDM Building Blocks

Justice XML Data Dictionary

Court Filing

Court Document

Arrest Warrant

Incident Report

Driver’s License

Court DataDictionary

39

Standards for Courts and Law Enforcement

Consolidated Case Management System Functional Standards JTC of COSCA and NACM

Civil Case Management Functional Requirements Domestic Relations Case Management Functional Requirements Criminal Case Management Functional Requirements BJA

Juvenile Case Management Functional Requirements OJJDP

Law Enforcement Records Management Systems Standards LEITSC

40

Levels of Standards

Choose and review the level of standard applicable to the exchange

NIEM

JXDM

Tech Stds: OASIS ECF 3.01Functional Stds: LEITSC

41

Standards for Courts available via NCSC

Traffic Functional Requirements NHTSA

Electronic Filing Processes (Technical and Business Approaches)SJI

LegalXML Member Section XML Court Document JTC of COSCA and NACM

Electronic Court Filing XML Standard JTC of COSCA and NACM

42

OASIS Electronic Filing 3.01 Specification

Began in 1999; First Specification in 2002; Latest revision August 2006Scope expanded in latest versionComponents currently include: Bankruptcy Civil filing Criminal filing Court policy ECF 3.01 Domestic filing Service information Queries Docket information Traffic citation

43

Law Enforcement Information Technology Standards Council

Funded by the Bureau of Justice Assistance until 2008IACP, NSA, NOBLE, and PERF Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems & Records Management Systems (RMS)Completion of CAD and RMS IEPDs

44

IACPIACP NOBLENOBLE NSANSA PERFPERF

Matt Snyder

Matt Snyder

Joe Akers

Joe Akers

TomRhatigan

TomRhatigan

Terry Chowanec

Terry Chowanec

Chief Michael Haslip

Chief Michael Haslip

Morris Roberson

Morris Roberson

Sheriff Paul Fitzgerald

Sheriff Paul Fitzgerald

ChiefLarry Boyd

ChiefLarry Boyd

LEITSC Project Manager

LEITS Council

45

Sponsors of LEITSC

2002: LEITSC  was createdGrant No. 2002-LD-BX-0002) from BJA

2003: LEITSC received new funding through a collaborative effort between BJA and NIJGrant No. 2003-MU-BX-0068

LEITSC is currently funded by BJAGrant No. 2003-MU-BX-0068

46

Standard Functional Specifications for Law Enforcement CAD & RMS

http://it.ojp.gov and www.leitsc.org

47

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.

48

Standard Functional Specifications for Law Enforcement CAD & RMS

5 Business Functions for a CAD SystemLaw Enforcement DispatchCAD System AdministrationSupport ServicesCall Management & Management Reporting Interfaces (internal and external)

49

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

Highlights 25 Business Functions for a RMS

Standard Functional Specifications for Law Enforcement CAD & RMS

50

CAD & RMS IEPDsGJXDM 3.0.3

RMS Summary ResponseRMS Query CAD to RMS TransferCAD Unit Status UpdateCAD Request Status UpdateCAD Resource Availability QueryCAD Resource Availability ResponseCAD Request for Resource CAD Summary Call for Service CAD Detailed Call for Service

51

LEITSC Outreach Activity

E-mail to full membership: IACP, NSA, NOBLE, PERFPeripheral assistance: BJA, IJIS Institute, Nlets, Recent Presentations: NSA, NOBLE, PERF, and IACP Annual Conferences as

well as the APCO Annual Conference & the GJXDM Users’ Conference

IACP Communications & Technology Committee Meeting & the IACP CJIS Committee Meeting

2006 – 2007 BJA Regional Information Sharing Conferences

52

LEITSC Collaboration

IACP, NSA, NOBLE, and PERF Association for Public Communications Officers (APCO)Global: GISWG, GXSTF, GTTACNIEM Business Architecture Committee (NBAC)Institute Intergovernmental Research (IIR) IJIS InstituteNletsSEARCHNational Criminal Justice Association (NCJA)National Center for State Courts (NCSC)ARJISUS Department of Justice, Office of Justice Programs

BJA and NIJ

53

LEITSC Next Steps

Distribute CAD & RMS Standard Functional SpecificationsProvide Technical Assistance to Law EnforcementImplement IEPD’s for CAD and RMSEducate, outreach, and inform the law enforcement community on LEITSC and the impact of IT standardsIdentify areas of need within law enforcement IT standardsRepresent the law enforcement community in ongoing IT standards initiativesHost Standards related workshopsPresentations to committees, sections, working groups, etc.Publications

54

LEITSC Contact Information

Heather RuzbasanLEITSC Project Manager703-836-6767 ext. 275ruzbasan@theiacp.orgwww.leitsc.org

55

How Do I Connect the Silos? Resources !

Available todayOJP and NIEM web sitesSEARCH JIEM IEPD Tool JXDM - NIEM SpreadsheetsNCSC Wayfarer Search Tool Schema Subset Generation ToolsUnified Modeling Language Tools JXDM and NIEM National Virtual Help DeskGTTAC Technical Assistance and Training

56

OJP Information Site www.it.ojp.gov

57

NIEM Information Site www.niem.gov

58

SEARCH JXDM/JIEM/NIEM Initiatives

XML Structure Task Force (XSTF)Global Training and Technical Assistance Committee (GTTAC) IJIS Institute XML CommitteeTechnical Assistance and Training(G) JXDM User GuideSponsor 1st Annual (G) JXDM User ConferenceLead developer of Reference Information Exchange Package Documentation (IEPDs)JXDM-NIEM National Virtual Help Desk supportGlobal and NIEM committees

59

Thank you!

Catherine PlummerSEARCH, The National Consortium

for Justice Information and Statistics

916-392-2550 x 301catherine@search.org

Mike Haslip Blaine Washington Police Department

LEITSC representative IACP(360)332-6769

mhaslip@cityofblaine.com

60

Questions ?

XML