Navigating the Standards LandscapeBJA Regional Information Sharing ConferenceJacksonville, FloridaJune 4, 2007
Chief Mike HaslipBlaine, WA, and IACP
Scott CameSEARCH
Agenda
What are standards? Why do we care?Industry standardsJustice and Public Safety Standards
XML VocabulariesMessage SpecificationsMetadata StandardsMethodologies and GuidelinesFunctional Standards
Case Study: Whatcom CountyIACP and LEITSC
Expectations
This session is not a tutorial or course in using standards successfullyWe will not teach you how to build NIEM IEPDs or Web Services (we have courses for that!)Goal is to provide you with a high-level overview of standards relevant to justice information sharing
Resource sheet
What are standards?
Why Standards?
Foundations: Industry Standards
Standards BodiesOASIS, W3C, IETF, IEEE, Open Group, WS-I
What does “open standard” mean to you?
XML
eXtensible Markup Language (XML)Mechanism for tagging data with context“Mark up” data with enclosing tags that define what the data mean
XML SchemaXML application that defines the structure of an XML document
eXtensible Stylesheet Language Transformations (XSLT)
XML application that transforms one XML document into another
XML Examples
<Person>
<PersonBirthDate>1953-02-12</PersonBirthDate>
<PersonName type=”Primary”>
<PersonGivenName>John</PersonGivenName>
<PersonSurName>Wayne</PersonSurName>
</PersonName>
</Person>
<xsd:element name=“Person”>
<xsd:complexType>
<xsd:complexContent>
<xsd:sequence>
<xsd:element name=“PersonGivenName” type=“xsd:string”/>
<xsd:element name=“PersonSurName” type=“xsd:string”/>
</xsd:sequence>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
XML
XML Schema
<xsl:template match=“Person”>
<Name>
<xsl:attribute name=“name”>
<xsl:value-of select=“PersonSurName”/><xsl:text>, </xsl:text>
<xsl:value-of select=“PersonGivenName”/>
</xsl:attribute>
</Name>
</xsl:template> XSLT
Web Services
SOAPMessage Transport StandardMessage Envelope Standard (generic)
WS-*SOAP add-ons for security, reliable messaging, addressing, and more
WS-Interoperability ProfilesMore constraints to ensure vendor compatibility
WSDLService description standard
Justice Info Sharing Standards
NIEM
National Information Exchange ModelComprehensive set of XML Schema components used to specify interoperable messages for justice, public safety, intelligence, and homeland securityProcesses and tools to assistBuilds on success of GJXDMCollaborative governance (Federal, state, local, tribal) through DOJ/DHS/Global partnership
NIEM at 50,000 Feet
People
Person Organization
People
Person Organization
Places
Location
Places
Location
Things
Property Contact Info
MetaData
Things
Property Contact Info
MetaData
EventsActivity
EventsActivity
InternationalTrade
Immigration
Screening
InfrastructureProtection
CriminalJustice
EmergencyManagement
Intelligence
NIEM Core
NIEM Domains
NIEM Roadmap and Tools
NIEM 1.0 released in November 2006NIEM 2.0 released in Q2 2007
Usability improvementsIncreased flexibilityHarmonizationMigration support
ToolsSearchingExtracting needed elements from the modelAssembling IEPDsLinks to other tools
Other vocabularies
IEEE 1512Transportation standardHas been mapped to GJXDM (and therefore to NIEM)
OASIS VocabulariesUniversal Business LanguageExtensible Access Control Markup LanguageEmergency Data Exchange Language
OthersGeography Markup Language
Message Specifications
NIEM is like Webster’s Dictionary: standard spellings and definitions of wordsExchange specification is like a novel: brings together specific words to provide contextual meaningReading the dictionary isn’t very interesting!NIEM “novels” are called Information Exchange Package Documentation (IEPD)IEPDs define local standards for exchange
NIEM IEPD Lifecycle
Reference IEPDs
National associations/organizations have created IEPDs from common/typical requirementsReference IEPDs can be used as-is, or as a starting point for defining a local IEPD to meet unique local requirementsReference IEPDs (and IEPDs created by individual jurisdictions) available in the clearinghousehttp://it.ojp.gov/iepd
Other Message Specifications
Emergency Data Exchange Language (EDXL)
Hospital Availability Exchange (HAvE)Common Alerting Protocol (CAP)
Rap Sheet StandardNlets messagesElectronic Court Filing specificationsSuspicious Activity Reporting (SAR) specification (NIEM IEPD)More…
Metadata Standards
Metadata standards assist in the transport of messages or the enforcement of rulesJust a couple of examples:
EDXL Distribution ElementGlobal Federated Identity and Privilege Management (GFIPM) Assertions
Methodologies/Guidelines
Global Justice Reference ArchitectureGlobal Security Policy GuidelinesGlobal Privacy Policy GuidelinesGlobal Fusion Center GuidelinesJustice Information Exchange Modeling (JIEM) MethodologyNASCIO Enterprise Architecture Toolkit
http://it.ojp.gov
Functional Standards
Functional standards govern the requirements, design, and implementation of line-of-business systemsPrincipal justice examples:
Corrections Technology Association—standards for corrections IT systemsNational Center for State Courts—Court Case Management functional standardsLaw Enforcement Information Technology Standards Council (LEITSC)—RMS and CAD functional standards
Q&A
WENET: Addressing a disconnected reality
Whatcom County WashingtonOver 2 million justice records and names, spread across a dozen city, county, tribal, and state university agencies on disparate, proprietary systemsSeveral systems over 15 years oldCounty ‘system’ a loose collection of programs and applications (DB2 on system 36 and AS400Wide variety of platforms and applications in outlying agenciesLittle / No connectivityLimited fundingNo Statewide RMS capacityA Strong Desire to Share
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 definitions
Business 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 jurisdictionsMaintain or improve security and accountability for access to current informationProvide for future growth and connectivity to other / larger systems (ARJIS, LINx, N-DEx, etc)
WENET – Game Plan and Technical Concept
Whatcom Exchange NETwork (WENET)Utilizes information sharing standards
to maximize available resources and ensure future compatibility
allows 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/
WENET Topology
ClientPrivate
Extranet
AS400
LongarmCMI JusticeNewWorld
Etc
HTTP Server
HTTP Server
Proxy /HTTP Server
Whatcom CountyOther Agencies
HTTP GET
XMLresponse
HTTP GET
XMLresponse
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.
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
Successful Project metrics
Jail and prosecutor record lookups:Over 15 minutes each of three people’s time, reduced to seconds by one person
GJXDM compliance and mapping benefits2 million + records15+ years of casesProjects subsequent to mapping estimated at much lower costs of legacy
Design, build and implementation of countywide pawn program completed in months
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 prosecutor
Full connectivity to all member agenciesTwo way query accessInformation capture, automated update, alerts
Implementing Advantages
Reusable components Future projects can benefit
Opportunity to improve business processes
Use Case design and modelingImproved communication between information provider and project teamReduce overall project delivery time
Conversions are now averaging 6 to 9 months
Reduce overall project costs
JXDM Building Blocks
Justice XML Data Dictionary
Court Filing
Court Document
Arrest Warrant
Incident Report
Driver’s License
Court DataDictionary
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
IACPIACP NOBLENOBLE NSANSA PERFPERF
Matt Snyder
Matt Snyder
Joe Akers
Joe Akers
TomRhatigan
TomRhatigan
Terry Chowanec
Terry Chowanec
Chief Michael Haslip
Chief Michael Haslip
MorrisRoberson
MorrisRoberson
Sheriff Paul Fitzgerald
Sheriff Paul Fitzgerald
ChiefLarry Boyd
ChiefLarry Boyd
LEITSC Project Manager
LEITS Council
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 NIJ
Grant No. 2003-MU-BX-0068
LEITSC is currently funded by BJAGrant No. 2003-MU-BX-0068
Standard Functional Specifications for Law Enforcement CAD & RMS
http://it.ojp.gov and www.leitsc.org
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.
Standard Functional Specifications for Law Enforcement CAD & RMS
5 Business Functions for a CAD SystemLaw Enforcement DispatchCAD System AdministrationSupport ServicesCall Management & Management ReportingInterfaces (internal and external)
Master IndicesCalls for ServiceIncident ReportingInvestigative Case ManagementProperty & Evidence ManagementWarrant ArrestBookingJuvenile ContactTraffic Accident ReportingCitation
Field ContactPawn Civil ProcessProtection Order & RestraintsPermits & LicensesEquipment & Asset ManagementFleet ManagementPersonnelInternal AffairsAnalytical Support RMS ReportsRMS System AdministrationRMS Interfaces
Highlights 25 Business Functions for a RMS
Standard Functional Specifications for Law Enforcement CAD & RMS
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 ResourceCAD Summary Call for Service CAD Detailed Call for Service
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’ ConferenceIACP Communications & Technology Committee Meeting & the IACP CJIS Committee Meeting
2006 – 2007 BJA Regional Information Sharing Conferences
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
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
LEITSC Contact Information
Heather Ruzbasan CotterLEITSC Project Manager703-836-6767 ext. [email protected]://www.leitsc.org
Thank You!
Scott CameSEARCH
Mike HaslipBlaine, Washington Police Department
LEITSC Representative IACP360-332-6769