Embed Size (px)
Citation preview
Bill Hobgood, Project Coordinator, APCO InternationalMike Roosa, Chief Information Officer, Maryland State Police
David Roberts, Senior Program Manager, IACP
June 14, 2011
Introduction to The Unified CAD (UCAD) Project A Public Safety Information Sharing & Interoperability Program
2
Agenda
UCAD DeliverablesBackground
LE CAD SpecificationPSDI Project / Revision Assessment
UCADFRWhy a Standard?The ProcessHow it was developedA Look at the Draft UCADFR Standard
Other Potential Unified Initiatives
Integrated Standard for all of Public Safety
3
UCAD Project
Funded in 2010 by DoJ/BJA (Grant # 2010-DB-BX-K147)Co-managed by the IJIS Institute and APCO Internationala collaborative effort to create the “Unified Computer Aided Dispatch (CAD) Functional Requirements document to include Law Enforcement, Fire, and EMS functionalityThe project team includes representatives from public safety practitioners, industry, APCO, and IJIS
From 2010 to 2011
4
UCAD Deliverables
Unified CAD Functional Requirements (UCADFR)Recommendations for Maintenance of the UCADFRNational Information Sharing Standards (NISS) Help Desk supportRecommendations for Cross-Discipline Information Sharing Efforts for the First Responder Domains
5
LEITSC LE CAD Specification Project
Law Enforcement Information Technology Standards Council (LEITSC) Member organization of IACP, NOBLE, NSA and PERF
Originally funded in 2002 by DoJ/BJA (Grant # 2002–LD-BX-0002) and continued in 2003 (Grant # 2003-MU-BX-0068)
The Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems was created by LEITSC with the assistance of the IJIS Institute
Designed as a template to “provide guidance to agencies when developing an RFP
From 2003 to 2006
7
Public Safety Data Interoperability (PSDI) Project
From 2007 to 2010
Funded in 2007 by DoJ/BJA (Grant # 2007-DD-BX-K155)Co-managed by the IJIS Institute and APCO Internationalto advance information exchange within the local communication center and first responder communities (Law Enforcement, Fire, EMS, Emergency Management, and Transportation)The project team included representatives from public safety practitioners, industry APCO, and IJIS
99
PSDI – Priority Data ExchangesPublished at www.ijis.org and www.apcointl.orgApr 08 to Aug 0947 draft versions59 exchanges identified
Provides an overview of the many data exchanges that are of potential value to the Communications Center. Communications Center Directors and other planners may use this document to assess the current strengths, weaknesses and growth potential of their facilities.
1010
PSDI – Guide to Information SharingPublished at www.ijis.org and www.apcointl.orgApr 08 to Aug 0931 draft versions
Provides managers of Public Safety Communications Centers with an overview of the issues and opportunities related to information sharing; also provides practical insights and action-oriented advice for managers looking to enhance data interoperability at their facilities.
12
Revision Assessment
A deliverable of the IJIS/APCO Public Safety Data Interoperability (PSDI) Project with members of the practitioner and vendor communitiesPurpose: to assess the level of effort required to incorporate Fire and EMS functionality into the LE CAD specification
13
How the Revision Assessment was Developed
Assembled both industry and practitionerorganizationsHeld a face-to-face workshop and conference callsStarting with the LE CAD Specification, the twoworking groups identified functional requirementsthat were unique to Fire/EMSAlso looked at global language changes andcontent updates that needed to be made to makethe document all hazard, all serviceFinal document was published openly for no costAvailable for download from numerous websites
http://www.prlog.org/10525474-revision-assessment-of-cad-functional-specifications-complete.htmlhttp://www.ijis.org/docs/ijis_CADFS_Rev_Assm_20100128.pdfhttps://www.rkb.us/download.cfm?id=5562
14
Relevance Matrix (LE CAD)
Requirements from the Functional Specifications for Law Enforcement
Computer Aided Dispatch (CAD) Systems
Law Enforcement Fire EMS
Business Function: Law Enforcement Dispatch Call Taking X X X Dispatch Decision Support X X X BOLO XDispatch Units X X X Unit Status Management X X X Call Management X X X Supplemental Resources Tracking X X X Call Disposition X X XBusiness Function: CAD System Administration Geofile Maintenance X X X Security X X X Logging X X X Configuration X X X Table Maintenance X X X Communication Center Relocation X X X CAD Catch‐Up X X XBusiness Function: Support Services BOLO XEmergency Operations Center X X XBusiness Function: Call Management and Management Reporting Dispatch Supervisor Support X X X CAD Management Reporting X X X Training and Testing X X XBusiness Function: Interfaces Primary X X X Additional Interfaces X X X Locational Systems Interfaces X X X Administration Interfaces X X X Communications Interfaces X X X Public Awareness Messaging X X X Emergency Operations Interface X X X Additional Business Functions X X X
15
Relevance Matrix (Fire/EMS)
REQUIREMENTS FROM THE REVISION ASSESSMENT FOR THE INCORPORATION OF FIRE
AND EMS FUNCTIONS INTO THE LAW ENFORCEMENT CAD FUNCTIONAL SPECIFICATIONS
Law Enforcement Fire EMS
Add Destination Locations X X XAlerting X X Move Up (“Fill‐In” and “Station Fill”) X X Staffed versus Unstaffed Units X X Cross‐Staffing/Crew Counting/Shared Staffing X X System Status Management (Dynamic Resource Deployment) XStation Dispatch (versus Unit Dispatch) X X Run Cards/Response Plans X X Adjustable Dispatch Levels X X Adjustable Response Plans X X Hospital Status/Availability and Hospital Recommendation X XAdditional Attributes X X XCAD Incident Type X X XUnit Recommendation Based on Input from Other Jurisdictions X XPredetermined and User Defined Timers X X XUnit Status Timers X X XPatient Tracking X X XAdditional Unit Status X X XStrike Team/Task Force Designations X X XUnit Rotation (aka Unit Load Balancing) X X XConditional Availability of Apparatus X X XAbility to Route to a “Decision Dispatcher” XLinking an Audio File to the CAD Dispatch Record X X XRostering X X XMileage Tracking X X XHydrant Location and Status XAdditional Unit Dispositions X X XException Reason Tracking X X XAdd Next Generation Functions X X XMultiple Simultaneous Calls to Single Unit X X X
16
Relevance Matrix (Fire/EMS) (Cont’d)
Law Enforcement Fire EMSNotifications X X XContact List X X XScheduled Events X X XSpecial Dispatch Areas X X XEMD/Call Triage X X XPremises Information/Hazards X X XPublic Safety Flight Tracking X X XChannel Designations X X XSuspicious Activity Reporting Functionality XGeo‐fencing X X XCommunications Center Standard Operating Procedures X X XIncident/Premises/Unit Standard Operating Procedures X X XSnapshot/Incident Replay X X XPre‐Release or Pre‐Alerting X X XRemote Access X X XIntegration/Interfaces with Other Systems X X XCAD Workstation‐to‐CAD Workstation Messaging X X XSecondary Incident Location X X XVehicle/Unit Change X X XAutomatic Routing X X XScheduling X X XIncident Command Support X X XSingle Discipline Call to a Combined Discipline Call X X XNarrative Field “Shorthand” (Auto Text) X X XCommand Line/GUI X X XTime Stamps X X XBypassed Units X X XPost Dispatch Response Re‐evaluation X X XUnit Status Transition Matrix X X X
17
Status of UCADFR
In a November 3, 2010 press announcement,APCO reported that along with the IJISInstitute, they had received a federal grant “tosupport the development of a set of computeraided dispatch (CAD) functionalspecifications for law enforcement, fireservice, and medical services applications.”APCO and the IJIS Institute have noted thatthe majority of local emergencycommunications centers dispatch for multiplefirst responder services – a combination oflaw enforcement, fire, and EMS practitionerswriting RFPs for CAD systems to supportthese centers will benefit from the revisedCAD functional specifications document.”“Using the Revision Assessment as a guide,the new project deliverable publication willserve as a multi-service CAD functionalspecification for the development andimplementation of integrated CAD systemsthat are responsive to fire and EMS needs inaddition to those of law enforcement.”
18
How the UCADFR is Being Developed
Assembled both industry and practitioner organizations (LE, Fire, EMS, Communications, Industry, DoJ, APCO, IJIS)Held conference calls and a combined face-to-face workshopUsing the Revision Assessment, participants were divided into three working groups and assigned specific requirements to define, describe, and craft sample RFP languageFirst combined draft has been createdOn-going task force work to finalizeWill be published for public comment
19
The UCADFR Development Process
20
Why a Standard?
“Provide significant guidance to agencies when developing a request for proposal (RFP) for purchasing or upgrading CAD systems…”
LEITSC press release July 3, 2006
Created to be generic so as not to favor any one vendor or platformDesigned to set standard minimal functional requirements for a CAD system, establishing a baseline from which to start the requirements or RFP process
A Look at the Draft UCADFR Standard
22
Other UCAD Deliverables
Recommendations for Maintenance of the UCADFRNational Information Sharing Standards (NISS) Help Desk supportRecommendations for Cross-Discipline Information Sharing Efforts for the First Responder Domains
23
Other Potential Future Unified Initiatives
Unified RMSCurrently exists in some vendor solution suites, but not according to a standard
Unified Mobile Computing StandardsUnified Field Reporting
Field InterviewAccident ReportingUCR/NIBRSePCRNFIRSInspection/Permitting
24
Questions?
Thank You for Attending!!!
25
For More Information: Bill Hobgood, Project Coordinator, APCO International&Project Manager, Public Safety Teamc/o City of Richmond (VA) – Dept. of Information Technology 900 E. Broad St., Room G-2Richmond, Va. 23219Direct # 804 240-0744 or 804 [email protected] or [email protected]
Paul Holcombe, Project Manager, IJIS Institute44983 Knoll Square Ashburn, VA 20147Office # 703.726.1095Cell # [email protected]
