Introduction to The Unified CAD (UCAD) Project A Public Safety Information Sharing & Interoperability Program

Transcription

1 Introduction to The Unified CAD (UCAD) Project A Public Safety Information Sharing & Interoperability Program Bill Hobgood, Project Coordinator, APCO International Mike Roosa, Chief Information Officer, Maryland State Police David Roberts, Senior Program Manager, IACP June 14, 2011

2 Agenda UCAD Deliverables Background LE CAD Specification PSDI Project / Revision Assessment UCADFR Why a Standard? The Process How it was developed A Look at the Draft UCADFR Standard Other Potential Unified Initiatives Integrated Standard for all of Public Safety 2

3 UCAD Project Funded in 2010 by DoJ/BJA (Grant # 2010-DB-BX-K147) Co-managed by the IJIS Institute and APCO International a collaborative effort to create the Unified Computer Aided Dispatch (CAD) Functional Requirements document to include Law Enforcement, Fire, and EMS functionality The project team includes representatives from public safety practitioners, industry, APCO, and IJIS From 2010 to

4 UCAD Deliverables Unified CAD Functional Requirements (UCADFR) Recommendations for Maintenance of the UCADFR National Information Sharing Standards (NISS) Help Desk support Recommendations for Cross-Discipline Information Sharing Efforts for the First Responder Domains 4

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

6 Public Safety Data Interoperability (PSDI) Project Funded in 2007 by DoJ/BJA (Grant # 2007-DD-BX-K155) Co-managed by the IJIS Institute and APCO International to 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 From 2007 to

7 PSDI Priority Data Exchanges Published at and Apr 08 to Aug draft versions 59 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. 9

8 PSDI Guide to Information Sharing Published at and Apr 08 to Aug 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. 10

9 Revision Assessment A deliverable of the IJIS/APCO Public Safety Data Interoperability (PSDI) Project with members of the practitioner and vendor communities Purpose: to assess the level of effort required to incorporate Fire and EMS functionality into the LE CAD specification 12

10 How the Revision Assessment was Developed Assembled both industry and practitioner organizations Held a face-to-face workshop and conference calls Starting with the LE CAD Specification, the two working groups identified functional requirements that were unique to Fire/EMS Also looked at global language changes and content updates that needed to be made to make the document all hazard, all service Final document was published openly for no cost Available for download from numerous websites

11 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 X Dispatch 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 X Business 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 X Business Function: Support Services BOLO X Emergency Operations Center X X X Business Function: Call Management and Management Reporting Dispatch Supervisor Support X X X CAD Management Reporting X X X Training and Testing X X X Business 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 14

12 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 X Alerting 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) X Station 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 X Additional Attributes X X X CAD Incident Type X X X Unit Recommendation Based on Input from Other Jurisdictions X X Predetermined and User Defined Timers X X X Unit Status Timers X X X Patient Tracking X X X Additional Unit Status X X X Strike Team/Task Force Designations X X X Unit Rotation (aka Unit Load Balancing) X X X Conditional Availability of Apparatus X X X Ability to Route to a Decision Dispatcher X Linking an Audio File to the CAD Dispatch Record X X X Rostering X X X Mileage Tracking X X X Hydrant Location and Status X Additional Unit Dispositions X X X Exception Reason Tracking X X X Add Next Generation Functions X X X Multiple Simultaneous Calls to Single Unit X X X 15

13 Relevance Matrix (Fire/EMS) (Cont d) Law Enforcement Fire EMS Notifications X X X Contact List X X X Scheduled Events X X X Special Dispatch Areas X X X EMD/Call Triage X X X Premises Information/Hazards X X X Public Safety Flight Tracking X X X Channel Designations X X X Suspicious Activity Reporting Functionality X Geo fencing X X X Communications Center Standard Operating Procedures X X X Incident/Premises/Unit Standard Operating Procedures X X X Snapshot/Incident Replay X X X Pre Release or Pre Alerting X X X Remote Access X X X Integration/Interfaces with Other Systems X X X CAD Workstation to CAD Workstation Messaging X X X Secondary Incident Location X X X Vehicle/Unit Change X X X Automatic Routing X X X Scheduling X X X Incident Command Support X X X Single Discipline Call to a Combined Discipline Call X X X Narrative Field Shorthand (Auto Text) X X X Command Line/GUI X X X Time Stamps X X X Bypassed Units X X X Post Dispatch Response Re evaluation X X X Unit Status Transition Matrix X X X 16

14 Status of UCADFR In a November 3, 2010 press announcement, APCO reported that along with the IJIS Institute, they had received a federal grant to support the development of a set of computer aided dispatch (CAD) functional specifications for law enforcement, fire service, and medical services applications. APCO and the IJIS Institute have noted that the majority of local emergency communications centers dispatch for multiple first responder services a combination of law enforcement, fire, and EMS practitioners writing RFPs for CAD systems to support these centers will benefit from the revised CAD functional specifications document. Using the Revision Assessment as a guide, the new project deliverable publication will serve as a multi-service CAD functional specification for the development and implementation of integrated CAD systems that are responsive to fire and EMS needs in addition to those of law enforcement. 17

15 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-toface workshop Using the Revision Assessment, participants were divided into three working groups and assigned specific requirements to define, describe, and craft sample RFP language First combined draft has been created On-going task force work to finalize Will be published for public comment 18

16 The UCADFR Development Process 19

17 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 platform Designed to set standard minimal functional requirements for a CAD system, establishing a baseline from which to start the requirements or RFP process 20

18 A Look at the Draft UCADFR Standard

19 Other UCAD Deliverables Recommendations for Maintenance of the UCADFR National Information Sharing Standards (NISS) Help Desk support Recommendations for Cross-Discipline Information Sharing Efforts for the First Responder Domains 22

20 Other Potential Future Unified Initiatives Unified RMS Currently exists in some vendor solution suites, but not according to a standard Unified Mobile Computing Standards Unified Field Reporting Field Interview Accident Reporting UCR/NIBRS epcr NFIRS Inspection/Permitting 23

21 Questions? 24

22 Thank You for Attending!!! For More Information: Bill Hobgood, Project Coordinator, APCO International & Project Manager, Public Safety Team c/o City of Richmond (VA) Dept. of Information Technology 900 E. Broad St., Room G-2 Richmond, Va Direct # or hobgoodb@apcointl.org or Bill.Hobgood@richmondgov.com Paul Holcombe, Project Manager, IJIS Institute Knoll Square Ashburn, VA Office # Cell # Paul.Holcombe@IJIS.org 25