Bureau of Justice Assistance National Institute of Justice Office of Justice Programs U.S. Department of Justice NIJ The Research, Development, and Evaluation Agency of the U.S. Department of Justice
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems
Developed by the
Law Enforcement Information Technology Standards Council (LEITSC) Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems
Developed by the
Law Enforcement Information Technology Standards Council (LEITSC)
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems This document was prepared with the guidance, leadership, and funding of the Bureau of Justice Assistance, Office of Justice Programs, U.S. Department of Justice, in collaboration with the Law Enforcement Information Technology Standards Council. This project was supported by Grant No. 2003-MU-BX-0068, awarded by the Bureau of Justice Assistance.
ii Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems Acknowledgements
LEITSC Governance LEITSC Functional Standards Committee Larry Boyd, Chairman Joe Cassa Chief of Police Bureau Commander Irving (TX) Police Department Wheat Ridge (CO) Police Department Police Executive Research Forum (PERF) Mitchell Ray Davis, III Joe Akers Chief of Police LEITSC Staff Liaison Dixmoor (IL) Police Department National Organization of Black Law Enforcement Executives (NOBLE) Debbie Fox Information Technology Administrator Terry Chowanec Louisville (KY) Metro Police Department LEITSC Staff Liaison PERF Michael Haslip Chief of Police Ted Kamatchus, Vice Chair City of Blaine (WA) Police Department Sheriff Marshall County (IA) Sheriff’s Office Linda Hill National Sheriffs’ Association (NSA) Consultant IJIS Institute Mark Marshall Chief of Police J. B. Hopkins Smithfield (VA) Police Department Division Commander/Jail Administrator International Association of Chiefs of Police Story County (IA) Sheriff’s Office (IACP) Dina Jones Morris Roberson CAD Manager U.S. Postal Service (Retired) Story County (IA) Sheriff’s Office NOBLE Bruce Kelling Heather Ruzbasan Bask Enterprises, LLC LEITSC Project Manager Managing Principal
G. Matthew Snyder Daniel Murray LEITSC Staff Liaison IT Management Section Commander IACP Arlington County (VA) Police Department
Fred Wilson LEITSC Staff Liaison NSA
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems iii Beverly Muse J. Patrick McCreary Technology Manager Associate Deputy Director City of Chattanooga (TN) Bureau of Justice Assistance Office of Justice Programs Morris Roberson U.S. Department of Justice Postal Inspector (Retired) U.S. Postal Service Harlin McEwen Chief of Police (Retired) Jim Slater Ithaca (NY) Police Department Chief Information Officer Massachusetts Executive Office of Public Safety David Mulholland Lieutenant Mark Steigemeier U.S. Park Police Vice President IACP Motorola Jennifer Zeunik Darrell True Former LEITSC Project Manager (2002–2005) IT Administrator IACP Wrentham (MA) Police Department
Gary Vest Project Manager Chief of Police Heather Ruzbasan Powell (OH) Police Department LEITSC International Association of Chiefs of Police Paul Wormeli 515 North Washington Street Executive Director Alexandria, VA 22314 IJIS Institute (703) 836-6767, ext. 275 [email protected] Advisors and Other Program Contacts www.leitsc.org
William Cade, Jr. Special Thanks to Our Partners Director, 911 Services and Communications Operations Center Association of Public Safety Communications Officials
Joe Estey Chief of Police Hartford (VT) Police Department Former LEITSC Governance Member IJISwww.ijis.or Instituteg IACP
Joe Heaps Communications Technology Portfolio Manager National Institute of Justice This document is the result of an extraordinary Office of Justice Programs collaboration between many justice practitioners and U.S. Department of Justice industry experts. Thank you all for your commitment, time, energy, and patience. Dustin Koonce Policy Advisor Bureau of Justice Assistance Office of Justice Programs U.S. Department of Justice
iv Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems Table of Contents
Acknowledgements...... iii Table of Contents...... v Executive Summary: CAD...... vii Business Function: Law Enforcement Dispatch...... 1 1.1 Description: ...... 1 1.2 Use Case Diagram...... 1 1.3 Use Case Specification: Call Taking...... 1 1.4 Use Case Specification: Dispatch Decision Support...... 6 1.5 Use Case Specification: BOLO...... 7 1.6 Use Case Specification: Dispatch Units...... 7 1.7 Use Case Specification: Unit Status Management...... 10 1.8 Use Case Specification: Call Management...... 12 1.9 Use Case Specification: Supplemental Resources Tracking...... 14 1.10 Use Case Specification: Call Disposition...... 15 Business Function: CAD System Administration...... 17 2.1 Description: ...... 17 2.2 Use Case Diagram...... 17 2.3 Use Case Specification: Geofile Maintenance...... 17 2.4 Use Case Specification: Security...... 17 2.5 Use Case Specification: Logging...... 18 2.6 Use Case Specification: Configuration...... 18 2.7 Use Case Specification: Table Maintenance...... 19 2.8 Use Case Specification: Communication Center Relocation...... 19 2.9 Use Case Specification: CAD Catch-Up...... 19 Business Function: Support Services...... 21 3.1 Description: ...... 21 3.2 Use Case Diagram...... 21 3.3 Use Case Specification: BOLO...... 21 3.4 Use Case Specification: Emergency Operations Center...... 22 Business Function: Call Management and Management Reporting...... 23 4.1 Description: ...... 23 4.2 Use Case Diagram...... 23 4.3 Use Case Specification: Dispatch Supervisor Support...... 23 4.4 Use Case Specification: CAD Management Reporting...... 23 4.5 Use Case Specification: Training and Testing...... 24
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems Business Function: Interfaces...... 25 5.1 Description: ...... 25 5.2 Use Case Diagram...... 25 5.3 Use Case Specification: Primary...... 25 5.4 Use Case Specification: Additional Interfaces...... 25 5.5 Use Case Specification: Locational Systems Interfaces...... 27 5.6 Use Case Specification: Administration Interfaces...... 27 5.7 Use Case Specification: Communications Interfaces...... 28 5.8 Use Case Specification: Public Awareness Messaging...... 28 5.9 Use Case Specification: Emergency Operations Interface...... 28 5.10 Additional Business Functions...... 29 Conclusion...... 31 Properties: Activity...... A:1 Properties: Actor...... A:7 Properties: Business Function...... A:11 Properties: State...... A:13 Properties: Use Case...... A:15
vi Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems Executive Summary: CAD
History With these goals in mind, the LEITSC Functional Standards Committee, composed of law enforcement The Law Enforcement Information Technology Standards practitioners and industry experts from around the country, Council (LEITSC) was created in 2002 with funding (Grant was appointed to develop the Standard Functional Number 2002-LD-BX-0002) from the U.S. Department Specifications for Law Enforcement CAD Systems. The of Justice, Bureau of Justice Assistance and continued baseline document was developed from common elements in 2003 with funding (Grant Number 2003-MU-BX-0068) found in requests for proposals, technical documentation, through a collaborative effort between the Bureau of and other CAD-related research. The document was Justice Assistance and the National Institute of Justice. then validated by the group using a modeling tool. Once LEITSC is currently funded under the Bureau of Justice developed and validated, the specifications were vetted Assistance (Grant Number 2003-MU-BX-0068) and through the law enforcement community via each of continues to work in cooperation with the National Institute the participating associations, as well as through other of Justice. LEITSC brings together representatives from stakeholder communities in an effort to gain input from a the International Association of Chiefs of Police (IACP), number of different perspectives. National Sheriffs’ Association (NSA), National Organization of Black Law Enforcement Executives (NOBLE), and Police Executive Research Forum (PERF) to address law enforcement information technology standards National Initiatives: Law Enforcement issues. The mission of the group is to foster the growth of Information Sharing Program strategic planning and implementation of integrated justice (LEISP), Law Enforcement National systems through the development and implementation of information technology standards. Data Exchange (N-DEx), and Law Enforcement Regional Data Exchange Purpose (R-DEx) As law enforcement agencies move toward the In 2003, LEITSC identified the need for a national procurement of computer aided dispatch (CAD) and law standard for computer aided dispatch (CAD) functional enforcement records management systems (RMS), it specifications. They believed that the standard would is vital to recognize and consider the Law Enforcement accomplish the following goals: Information Sharing Program (LEISP) developed by the U.S. Department of Justice (DOJ). The LEISP is designed Provide a starting point for law enforcement agencies to promote information sharing among all levels of the law to use when developing CAD requests for proposal enforcement community and to guide the investment of (RFP); resources in information systems that will further this goal. Level the playing field when working with vendors; and The goals of LEISP are supported through the proliferation Promote system interoperability (for example, CAD to of the Global Justice Information Sharing Initiative (Global) CAD). Extensible Markup Language (XML) Data Model (Global JXDM). For additional information on the Global JXDM, visit www.it.ojp.gov. The Global JXDM is an XML standard
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems vii designed specifically for justice information exchanges. It is expected that the process of defining detailed It provides law enforcement, public safety agencies, information exchanges in a CAD system will be addressed prosecutors, public defenders, and the judicial branch in future phases of this project. In addition, these with a tool to effectively share data and information in a specifications are intended to be used in conjunction with timely manner. There are several ongoing DOJ initiatives technical standards, including the Global JXDM, in order to incorporated into the LEISP. streamline the process of sharing information.
One program currently being developed jointly between It is intended that these standards will be updated and the Federal Bureau of Investigation (FBI) and state and augmented on a regular basis. local law enforcement is the Law Enforcement National Data Exchange (N-DEx) System. A second program— the Law Enforcement Regional Data Exchange (R-DEx) Introduction System—has been developed and implemented by the CAD systems allow public safety operations and FBI. Both programs are new law enforcement information communications to be augmented, assisted, or partially sharing systems based upon the above critical standards. controlled by an automated system. It can include, among other capabilities, computer-controlled emergency vehicle dispatching, vehicle status, incident reporting, and Document Scope management information. This document presents standard functional specifications for law enforcement CAD systems. The specifications All aspects of a CAD system must be optimized for rapid found in this document are intended to be generic in nature response time and system reliability. Since time is of the rather than favor one particular system or approach over essence, the CAD system must accurately provide a data another; they are at the functional level, meaning that they and time stamp for every activity. define what is to be accomplished versus how it should be accomplished. These specifications were developed to CAD systems collect the initial information for an incident depict the minimal amount of functionality that a new law and then provide the information to one or more RMS enforcement CAD system should contain. They are not systems. intended to simply be substituted for an RFP but should be tailored to fit the specific needs of each agency or group The CAD system also supports other activities that assist of agencies looking to purchase a new or upgrade an old in the effective use of public safety resources, including CAD system. These specifications should be used as a shift change roll call, “Be on the lookout” (BOLO) files, and starting point to build a fully functional (based on agency the ability to schedule a call in the future. needs) CAD system that is based on open standards in order to efficiently interface and share information with This document addresses the following business functions: other systems both internally and externally. Law Enforcement Dispatch CAD System Administrators Support Services Call Management and Management Reporting Interfaces EMS Dispatch Fire Dispatch Intelligent Transportation The N-DEx Program is an incident- and case-based information sharing system (e.g., RMS) for local, state, tribal, and federal law Properties enforcement agencies that securely collects and processes crime data in support of the investigative and analytical process and will provide law enforcement agencies with strategic and tactical capabilities that do not currently exist on a national scale. An N-DEx concept of operations (ConOps) document is being finalized to aid in the design of the N-DEx system and to ensure that stakeholders understand and share the N-DEx vision.
The R-DEx Project seeks to securely share sensitive but unclassified crime information between federal agencies, while allowing for connection with several existing regionally based local and state information sharing systems to impede criminal and terrorist activities. R-DEx is now operational in several metropolitan areas.
viii Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems Business Function: 1 Law Enforcement Dispatch
1.1 Description: consists of receiving the call, obtaining sufficient and accurate information from the caller, determining whether Law enforcement agencies use CAD to facilitate incident this is a duplicate of a call in progress, and recording or response and communication in the field. CAD systems, updating the CFS in the CAD system. The call taker may in many cases, are the first point of entry for information also apply procedures and guidelines to verify, analyze, coming into the law enforcement system. Typical CAD classify, and prioritize the call prior to routing the CFS to system functions include resource management, call the dispatcher. A CFS may also be generated by a unit in taking, location verification, dispatching, unit status the field. The unit can contact the dispatcher or the call management, and call disposition. Additionally, mapping taker, or he may actually create the call electronically using functionality, interface with mobile data computers (MDC), the optional mobile data terminal (MDT) interface. and interfaces with other external local, state, and federal A CFS may be forwarded to a telephone reporting unit and information systems may be included. Call takers, be received from the telephone reporting unit. This may dispatchers, and their supervisors are primary users include the ability to create a CFS for future scheduled of CAD. Units in the field may interact via mobile data events. computers. Associated Relationship Description Actor 1.2 Use Case Diagram (see page 2) Caller calls In jurisdictions with an E911 interface, the 1.3 Use Case Specification: Call Taking call taker still talks to Calls for service (CFS) initiate the CAD process. Callers the caller, but the data are citizens or other agencies requesting services from from the E911 interface the agency or giving notification of events or activities of reduces call entry time. concern. A CFS may come from many different points of Unit initiates origin, such as alarm systems, E911 systems, direct calls Alarm initiates Business alarm or (7- or 10-digit numbers), walk-ins, CAD-to-CAD interfaces, other optional interface or Web-based systems. provides data only. The service requested by callers will consist of both External CAD calls An external CAD may emergency and nonemergency priorities. Call taking communicate with a call center in another URL Integration collaborated with LEITSC to assist in the development jurisdiction if those of the functional standards. URL Integration used an alternative method jurisdictions are under to requirements analysis with their RequirementsModeler software. RequirementsModeler is based on Unified Modeling Language (UML), an agreement to work which is the de facto standard for documenting functional requirements. together and have a UML was created by the Object Management Group (OMG) in 1997 as CAD-to-CAD interface. a standard for visual object-oriented modeling. RequirementsModeler, consistent with UML principles, automatically generates diagrams and Call Taker receives In smaller agencies, the process flow (Use Case and Activity diagrams). URL Integration’s Use call taker may be the Case and Activity diagrams were reproduced for use in this report. dispatcher.
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems 1.2 Use Case Diagram iniatiates Caller alarm calls
Call Taking*
receives transfers External Agency Call Taker transfer calls
sends Dispatch External Decision Support transfer CAD Telephone Reporting Unit
initiates <
Dispatch Units Unit dispatched performs Unit Status records Management Dispatcher maintains
records Call Management
<
Associated Relationship Description Flow of Events Actor 1.3.1 Update CFS Data External transfers This may be a call taker [If duplicate] Information related to an open call will be Agency from another agency updated as information becomes available. Multiple transferring the original callers provide potential witnesses to the call and may call to the receiving provide additional or supportive information. This may agency. result in reclassification and prioritization of the call. The Telephone transfer dispatcher will need the ability to enter narrative data at Reporting Unit any time prior to closing the CFS. 1.3.1.1 Notes Detail Call may have already been dispatched.
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems Call Taking Retrieve Activity Incoming Call Diagram
Take (person (alarm) Retrieve Alarm Caller Data called) Location
Capture Location
Verify Assign Call Location Classification and Priority
Check for Duplicate Calls
Create Call (first call) (duplicate) Update CFS for Service Data
Retrieve Correlate to Preraise Hazard Sector and History
Retrieve (if person information Person is available) Information (if no person information is available) Retrieve Vehicle Information
Determine Dispatch Need
(resource dispatch not warranted) Utilize Call Disposition
(appropriate to dispatch) Routed
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems 1.3.2 Determine Dispatch Need more motorists or a fire alarm reported from an electronic A decision is made to dispatch a unit or direct the CFS for monitoring system or a witness reporting smoke coming disposition. from a business. The call may be determined to be unique, but there should be a capability of linking the call 1.3.2.1 Notes to another existing call. Detail This analysis will determine whether a new CFS is This flow assumes that the call taker is also the recorded in CAD or whether an existing CFS is to be dispatcher, which is common practice in small and updated with information not yet captured. medium-size agencies. In larger agencies, call takers route calls to dispatchers, who handle the incident 1.3.5.1 Notes management from that point forward. Detail
1.3.3 Utilize Call Disposition [Description] The call taker may have the ability to reopen a call but may not be able to close the call once it [If resource dispatch not warranted] A call taker may close has been reopened. a CFS that does not require the dispatch of resources.
A CFS will be closed when the units at the scene have 1.3.6 Take Caller Data completed the assignment. Depending on the agency [If person caller] The call taker requests basic information standard operating procedures (SOP), the primary of the caller. Many 911 systems provide information about unit may close the call with a status. The dispatcher is the phone account (ANI) originating the call, which may or notified by assigned units of their status change using may not be verified immediately, depending on the nature voice or mobile data computer (MDC) transactions. MDC and priority of the call. transactions may update CAD to record the unit status and close the CFS, if the data received indicates the CFS The basic information needed to open and initiate a CFS is complete. The CFS will be classified with a specific is the type of call (nature of the complaint), the priority, and disposition, generally provided by the primary unit. the location of the CFS. Depending upon the priority of the call, when basic information has been entered, the CFS When a call is closed, information collected during the can be routed to the appropriate dispatcher for handling. CFS may be automatically transferred from the CAD system to the records management system (RMS). Any 1.3.7 Capture Location updates made by the CAD operators on reopened calls will In many instances, the call taker has access to the call be automatically transferred to the RMS, subject to agency origination location (ALI/ANI) data using the 911 system. policies. If not, the CFS location must be elicited from the caller. In some incidents, the caller’s location may not be the In instances where a duplicate call is identified, one call is location of the call for service. disposed with a cross-reference to the original CFS. The calls will be linked for future retrievability. 1.3.7.1 Alternative Flows Detail 1.3.4 Assign Call Classification and Priority If the call is generated from the 911 system, the location Assign a nature code, which may include general may be available from ANI/ALI, if such an interface classification and subtypes of the call, based upon agency exists. Phase I cellular calls may give the location policy. of the nearest tower. Phase II cellular may give the The call will be prioritized based upon type, applying coordinates of the caller. established guidelines and procedures, to determine the Beyond latitude and longitude, the altitude may be appropriate dispatch and response needs. captured.
1.3.5 Check for Duplicate Calls 1.3.8 Verify Location The system automatically evaluates the CFS location (and The caller location will be checked against current address potentially other site parameters) to determine whether a listings in the system. Locations that are not verified call is a duplicate. The call taker evaluates the information provide an indication to the call taker that information presented by the system with that obtained from the caller received may be inaccurate, providing additional to make the final decision regarding duplicate calls. Calls information for the dispatcher to relay to the responder. for service may be received by many sources for the same CFS, such as a traffic accident witnessed by two or The location format can be a street address (blockface address), intersection, or common place name. Location
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems information for a common place, such as the City Hall, has 1.3.11.1 Alternative Flows a street address listing cross-reference that will provide Detail the legal street address. Information will be contained in a geofile, which must include latitude and longitude. Altitude This flow assumes that the call taker is also the would be optional. dispatcher, which is common practice in small and medium-size agencies. In larger agencies, call takers The geofile will: route calls to dispatchers, who handle the incident management from that point forward. 1. Validate that the street name is an actual street in the service area. 1.3.12 Retrieve Premise Hazard and History 2. Resolve ambiguities while accounting for spelling Relevant historical and tactical information about specific variations and duplications. and neighboring premises is obtained from internal and/or . Validate intersections. external sources for decision support. This information may include information about previous calls for service 4. Validate address range. at the premise, whether the premise has records of 5. Relate common place names to actual addresses. registered firearms, hazardous materials stored at the 6. Relate X/Y/Z coordinates to an actual address. site (usually business sites), serious medical information concerning individuals residing at the premise, and other 7. Transform latitude and longitude to map coordinates relevant information. for display. 8. Translate call location to agency reporting area. 1.3.13 Create Call for Service 9. Translate alias names to actual street names. [If first call] A new call for service is recorded in the CAD using information compiled to date. A unique call number 1.3.9 Retrieve Incoming Calls is assigned. Incoming calls by phone are answered in the order that they come in. Calls from the 911 system are given a 1.3.14 Correlate to Sector priority over calls from direct phone lines. The center’s The location information obtained from the caller and operating procedures will determine whether any call is verified by the geofile will be checked to identify the patrol allowed to go to voice mail or be put on hold. area assignment in which the call is located.
1.3.9.1 Alternative Flows 1.3.14.1 Alternative Flows Detail Detail The call taker answers calls from the public from a 911 line, a 7- or 10-digit phone number, or a TDD/TTY device In larger agencies, it is the call taker’s function to simply for the hearing-impaired. determine the nature of the call and the call location and then route the call to the dispatcher so that units can be placed en route. 1.3.10 Retrieve Person Information [If person information is available] Person information 1.3.15 Retrieve Alarm Location may include history, protection orders, warrants, mental or health issues, gang information, sex offender registry [If alarm] Obtain the location of an electronic-generated information, etc. call from the call source information. Location and contact information from electronic sources may be received This could be automatically queried based upon from data exchanges to CAD or may be obtained from a information entered into fields, if available. database of common addresses maintained by the agency.
1.3.11 Retrieve Vehicle Information Postconditions Postcondition Descriptions Any pertinent information of a vehicle. This could be Routed Information in voice, paper, or automatically queried based upon information entered into electronic form was recorded and fields, if available. sent or distributed to intended recipients.
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems Dispatch Decision Retrieve CFS Retrieve from Call Resource Support Pending Queue Recommendations Activity Diagram Determine Determine Resource Proximity of Availability Resources
Review Call Dispatch Background Resource (recommended Information Decision requirement appropriate)
Override Resource Requirement (recommended requirement appropriate)
CFS Resource Assigned
1.4 Use Case Specification: Dispatch Associated Relationship Description Decision Support Actor The dispatcher is presented with the recommended Telephone transfer resources for the selected CFS, based upon preset criteria Reporting Unit for the type and priority of CFS. Further information will be considered, such as the history of the location, suspect, Flow of Events and the possibility that hazardous materials may be involved. The recommended resources may be overridden 1.4.1 Review Call Background Information by the dispatcher based on the additional information The information associated with the location and /or or requests by officers on the scene. The system may affiliated person is considered to determine whether the have the capability to perform dispatch decision support, recommended resources are adequate. The decision to such as assigning an incident number without human override the resource requirement should be made if it is intervention. determined that the recommendation is inadequate.
Units available will be considered as well as the available 1.4.2 Dispatch Resource Decision unit proximity to the CFS. The final decision is which Recommended resources are assigned based on SOPs specific units to dispatch. that factor workload and unit capability with regard to skills and equipment required for the CFS, unit availability, and Associated Relationship Description the proximity of resources. Actor 1.4.3 Retrieve CFS From Call Pending Queue Call Taker calls The next CFS on the call pending queue is retrieved. Dispatcher performs The call will contain all information collected during the
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems call up to the point it is retrieved. Additional information and departmental SOP. Proximity determination can be may continue to be added to the call by call takers and supported by an optional AVL interface. dispatchers while the CFS is open. Calls in the queue are stacked by agency-defined priority, 1.5 Use Case Specification: BOLO often based on SOP. The CAD system allows the agency to determine the sort order of the call pending queue. BOLO (Be on the Lookout) can be an optional part of a CAD application or a part of an RMS system. BOLOs in 1.4.3.1 Alternative Flows CAD are created and maintained in a data file in CAD. These may be entered by a dispatcher or may be created Detail by anyone who has been given the required security In the event of an officer-initiated call, the unit can initiate clearance to create or maintain the file. a call by reporting the event to the dispatcher, who creates a new call for dispatch and places the officer on- Both an RMS interface and the mobile data terminal scene at an initiated call. interface should support the creation and transmission Based on SOP, the officer may directly initiate the call of a BOLO. A BOLO should be assigned an expiration through a mobile device, if available. date, either by the person who creates it or by the system, based on department policy and available system 1.4.3.2 Notes resources. A typical BOLO file would include the nature of the BOLO, priority, date, range of effectiveness, subject Detail person and subject vehicle information, and contact Events are stacked by agency-defined priority, often information. There should be a mechanism to search the based on SOP. BOLO and to print it in a report and to purge the BOLOs out of the date range. 1.4.4 Retrieve Resource Recommendations Resource recommendations are initially determined based on the call type, priority and location information, 1.6 Use Case Specification: Dispatch and other characteristics of the specific CFS. The call Units type and priority level are used based on agency policy The units specifically recommended or selected for a CFS and procedure. The dispatcher must review resources will be dispatched and their acknowledgment recorded. recommended by the system. In selecting appropriate Other units not dispatched may be notified of an event in resources, the dispatcher may consider a number of progress if the CFS warrants. When multiple units are factors, such as proximity to the call location, number of dispatched, one unit will be designated as the primary units available, special skills or equipment, and the number responder responsible for the CFS until it is completed. and type of other CFS to which officers are responding. These factors may or may not have been considered in the initial system recommendation. Associated Relationship Description Actor 1.4.5 Override Resource Requirement Unit dispatched [If recommended requirement appropriate] The initial recommendation based upon known criteria may be Dispatcher performs adjusted based upon additional information that becomes available, such as learning that the suspect is known to be armed and dangerous. Override must be recorded. Flow of Events 1.4.6 Determine Resource Availability 1.6.1 Record Unit Activity Available resources are displayed based upon unit status, The unit status will be updated to associate the dispatched which would include unassigned as well as assigned with unit or units with the CFS, including location and time. a lower priority status of call to which a unit is assigned. The units may be currently unassigned or assigned to a 1.6.2 Place Call on Unassigned Status CFS with a designated type and priority level. Unassigned [If unit pulled off of call] The unit is reassigned to a new call units are available to be dispatched. and automatically unassigned from the previous call.
1.4.7 Determine Proximity of Resources Resource proximity can be based on a closeness calculation, which can be distance or driving time. Any unit suggestion must respect dispatch control areas
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems Dispatch Units Activity Assign Diagram Units
(alert or notify) Recognize (dispatch) Utilize Acknowledgement BOLO
Record Alert/Notify Unit Units Activity
(unit pulled Place Call on off of call) Unassigned Status
(no call affected)
Record CFS Activity
Resources Dispatched
1.6.2.1 Notes information. This may be done by voice communication or through mobile data computers. Detail If all units are removed from the call, then the CFS is 1.6.5 Alert/Notify Units placed in the pending dispatch queue. This is often The dispatcher will relay information pertaining to calls referred to as a preempted call. for service to the appropriate units. This notification has the purpose of informing and raising the awareness of 1.6.3 Record CFS Activity designated teams or all officers. The CFS record will be updated to associate the unit or 1.6.5.1 Alternative Flows units dispatched as responding units to the call. Detail 1.6.4 Recognize Acknowledgement Alerting other units or command may not occur and is [If dispatch] The unit assigned to the call will respond likely based on SOP. to the dispatcher to confirm receipt of the dispatch
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems 1.6.6 Assign Units 1.6.6.1 Notes The dispatcher will assign a CFS and relay pertinent Detail information to the appropriate units in the field for the Decision point. Unit may be diverted en route while purpose of dispatching a responder. An optional MDC encountering incident. This would return to officer- interface supports this activity. initiated dispatch. Assigned but available units may be pulled off of current [Description] Decision to alert or notify is based upon assigned status based on priority levels and the resource SOP. needs of the CFS. If all the units are pulled off of a call, the call will be added back into the dispatch queue. 1.6.7 Utilize BOLO [If alert or notify] BOLO (Be on the Lookout) can be an optional part of a CAD application or a part of an RMS
Unit Status Management Display Unit Activity Dispatch Status Diagram
(en route) Record Arrival on Scene
(unassigned) Timed Record Alerts Unit Location
Maintain Status
(unit cleared from call) Reassign to Available
(unit remains on scene)
Update Unit Status
Status Recorded
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems system. BOLOs in CAD are created and maintained in a 1.7.1.1 Notes data file in CAD. These may be entered by a dispatcher Detail or may be created by anyone who has been given the required security clearance to create or maintain the file. [Description] Decision point. Unit may be diverted en route while encountering an incident. This would Both an RMS interface and the mobile data terminal return to officer-initiated dispatch. interface should support the creation and transmission of a BOLO. A BOLO should be assigned an expiration 1.7.2 Record Arrival on Scene date, either by the person who creates it or by the [If en route] Units responding to the scene communicate system, based on department policy and available system to dispatch that they have arrived at the location. This resources. A typical BOLO file would include the nature communication may occur verbally or through an MDC of the BOLO, priority, date, range of effectiveness, subject transmission that may automatically update CAD to reflect person and subject vehicle information, and contact the current status of the responding unit, including time of information. There should be a mechanism to search the arrival on scene. BOLO and to print it in a report and to purge the BOLOs out of the date range. There may be a need to record multiple arrival times; an example would be the arrival at the location and another arrival at the scene. For example, a unit may arrive at 1.7 Use Case Specification: Unit Status the location of a high-rise building and at a later time will Management arrive at the scene located within the building. The system should provide for the setting of different timers based Unit status must be continually monitored, updated, and upon time-of-arrival type. recorded by the dispatcher. This information may be made available by voice communication or through mobile data 1.7.2.1 Notes computers. In addition to recording the unit status and Detail destination, the CFS number and times (action) will also be recorded by the system. The recording of status changes [Description] The system should maintain a date- and is representative of a unit’s work activity during a time time-stamped unit log that includes all changes in unit interval. This information is essential to running standard status. CFS reports. 1.7.3 Timed Alerts The system should maintain the elapsed time between The system must be able to alert the dispatcher to the status changes/checks and alert the dispatcher when expiration of the timer associated with any status change. agency-defined thresholds are met. The alert to the dispatcher may be in the form of a tone and/or a visual prompt. This should be configurable based Associated Relationship Description upon the type of CFS. The system should record the Actor acknowledgement or action of the dispatcher in response Unit records to the prompt, which will automatically reset the timer.
Dispatcher maintains 1.7.4 Record Unit Location Any change in unit location is captured along with time stamps, including changes of location associated with the same CFS. Flow of Events 1.7.1 Display Unit Dispatch Status 1.7.5 Maintain Status The current status of units will be available at all times. [If unassigned] Information is continually displayed in CAD The display will indicate the unit’s status and assigned to reflect the current status of units that are monitored by calls for service (if any). The display can also show the the dispatcher. location or last known location of the unit. In the absence of AVL, the location may be the current call location, the 1.7.6 Reassign to Available last call location, or the location entered by the dispatcher [If unit cleared from call] When a unit has cleared from a or MDC. In the case of assigned units, the display may scene and is no longer assigned to the CFS, the unit will show any alert timer, the CFS type, and priority. be reassigned to an available status. Data received from MDC transmissions may update CAD and reflect the new Examples include arrived on scene, available, unavailable, status of the unit. The unit may remain on scene and have and unavailable but assignable. More status types should an available on-scene status. be configurable.
10 Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems Call Assign RMS Management Incident Activity Number Diagram (RMS requires incident data) Transfer Basic Incident Data to RMS (no additional information)
Display CFS Data
(additional information Display available) Additional CFS Data (closed CFS identified) Reopen CFS
(open call)
Update CFS Data
Dispatch (resource requirement changed) Resource Decision
(additional resources needed) Assign Units (less resources (supplemental resources needed) (supplemental needed) Utilize resources not Supplemental needed) Resources Update Tracking Assigned Resources (resource requirement not changed) (additional information)
Update Call Status
Call Monitored
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems 11 1.7.6.1 Notes 1.8.2.1 Alternative Flows Detail Detail Clearing the call may have the capability of clearing all In some jurisdictions, dispatchers may not always make units assigned to the CFS when all units simultaneously the decision as to whether the event has adequate are reassigned to available status. resources. In those instances, it is most likely a commander on scene that makes this determination and 1.7.7 Update Unit Status the dispatcher will respond by sending more units when [If unit remains on scene] Information is continually requested by those on scene. updated in CAD to reflect the current status of units that are monitored by the dispatcher. 1.8.3 Dispatch Resource Decision [If resource requirement changed] Recommended resources will be assigned based on SOP that factor Postconditions workload and unit capability with regard to skills and equipment required for the CFS, unit availability, and the Postcondition Description proximity of resources.
Status Recorded The status of the unit is recorded in 1.8.4 Update Assigned Resources the CAD system. [If less resources needed] When required resources for the call have changed, this will be adjusted and recorded on 1.8 Use Case Specification: Call predetermined criteria. Management 1.8.5 Utilize Supplemental Resources Tracking The call is managed by continually updating the CFS [If supplemental resources needed] For example, in data with any additional information reported by callers or cases where a vehicle has been confiscated or found to officers on scene. The resource recommendations may be be disabled, the dispatcher needs the ability to request revised based on additional information and may be added the services of a towing company. This request may or reassigned. be made by company name (owner requested) or by rotation. In cases where the owner does not have a Postcondition Relationship Description preferred company, the system will select a company from the towing rotation. A towing rotation prevents any one Dispatcher records company from being favored over another.
If resources other than those recommended by the rotation Flow of Events are selected, the system should capture the reason for the exception. 1.8.1 Display CFS Data [If no additional information] The CFS will need to be 1.8.6 Assign Units displayed and monitored through CAD. This includes [If additional resources needed] The dispatcher will activities such as additional call information and activities assign a CFS and relay pertinent information to the reported by the officers. Immediate access to all open appropriate units in the field for the purpose of dispatching calls (including unassigned) should be provided on a responder. An optional MDC interface supports this the CFS status display. When a call is closed, it will activity. automatically be removed from the call display. Assigned but available units may be pulled off of current 1.8.2 Update Call Status assigned status based on priority levels and the resource [If no additional information, resource requirement needs of the CFS. If all the units are pulled off of a call, unchanged, supplemental resources not needed] The the call will be added back into the dispatch queue. status of the call is updated as new information is received. This should include updating the reported CFS type to 1.8.7 Update CFS Data the actual CFS type. For example, once the immediate [If open call] Information related to an open call will be incident is resolved, the responding unit will communicate updated as information becomes available. Multiple to the dispatcher that the scene is secured. callers provide potential witnesses to the call and may provide additional or supportive information. This may result in reclassification and prioritization of the call. The dispatcher will need the ability to enter narrative data at any time prior to closing the CFS.
12 Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems 1.8.8 Assign RMS Incident Number 1.8.11.1 Notes In addition to the CAD CFS number, an RMS incident Detail number (case number) may be assigned before the call [Description] A CFS may be reopened by a dispatcher is transferred to the RMS system. This may happen at or call taker, but the call taker may not have the ability to any time prior to sending the report but most likely after close a reopened call. the determination that it will be sent. The RMS number may be assigned from a data file of incident numbers maintained in the CAD system in coordination with the RMS system. Department policies in this area must be Supplemental supported by the CAD system. Resources Request 1.8.9 Transfer Basic Incident Data to RMS Tracking Supplemental [If RMS requires incident data] Basic incident data that Resource can be modified will be transferred to the agency records Activity section for its use. It will be transferred in an editable Diagram format.
Retrieve This function relates to the transfer from CAD to RMS (service unavailable) of the CFS data elements normally contained in a law Supplemental Resource enforcement incident report. In fact, the Justice XML Rotation List reference document for a law enforcement incident report should provide an excellent standard for the transfer.
The following are examples of the types of data found in an incident report: report number, CAD call type, nature Notify of call, date/time of call, location of incident, and persons Supplemental and vehicles involved. The CAD CFS number should be Resource included to provide a cross-reference between the CFS Service and the subsequent incident report.
Incident transfer is normally triggered and takes place automatically. Within the framework of this standard, it would happen (optionally) as an incident report number is Enter assigned and at the time of final disposition of the CFS. Supplemental Service Record The CAD systems should include a feature whereby administrative commands can be executed to transfer either a specific incident or a series of incidents based upon parameters.
1.8.10 Display Additional CFS Data [If additional information available] As additional information is made available, the dispatcher will be (supplemental alerted and have the ability to view the new information; service available) for example, any information entered by a call taker or another dispatcher. Update 1.8.10.1 Notes Supplemental Service Record Detail There needs to be a means to easily display recently closed calls.
1.8.11 Reopen CFS [If closed CFS identified] An existing CFS is reopened for update. Changes are traced for audit purposes. Supplemental Resource Dispatched
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems 13 1.9 Use Case Specification: If resources other than those recommended by the rotation are selected, the system should capture the reason for the Supplemental Resources Tracking exception. For example, in cases where a vehicle has been confiscated or found to be disabled, the dispatcher needs the ability to request the services of a towing company. Flow of Events This request may be made by company name (owner- 1.9.1 Request Supplemental Resource requested) or by rotation. In cases where the owner does not have a preferred company, the system will select A law enforcement official requests that a supplemental a company from the towing rotation. A towing rotation resource service be dispatched to a specified location. prevents any one company from being favored over 1.9.2 Retrieve Supplemental Resource Rotation List another. [If supplemental service unavailable] The agency will obtain the contact information from the system in order to contact and request service from the next eligible service.
Call Disposition Active Call Activity for Service Diagram
Determine Call Status
(services rendered) Determine Reportability
(call in progress) (report required) Assign RMS Incident Number
Utilize Call (nonreportable CFS) Management
Record Disposition
Send Data to RMS
Call Closed
14 Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems The system may provide a list of one or more services. updates made by the CAD operators on reopened calls will This could be based on geographical requirements. be automatically transferred to the RMS, subject to agency policies. 1.9.3 Notify Supplemental Resource Service The supplemental resource will be contacted to provide Instances where a duplicate call is identified, one call is dispatch information by the dispatcher and will be provided disposed with a cross-reference to the original CFS. The information about the incident to which it is requested to calls will be linked for future retrievability. respond. The availability of the service to provide services will be recorded. A supplemental service that cannot be Associated Actor Relationship Description contacted or informs the agency of its inability to respond within a prescribed time is considered unavailable to Dispatcher records provide the service. A supplemental resource will be selected from the list until one is found that is available. Flow of Events 1.9.4 Enter Supplemental Service Record 1.10.1 Determine Call Status A record of supplemental service request is established The CFS will remain open and monitored. The status of to reflect the instance of the selection from the service the CFS may change as the situation is resolved. The rotation list. This triggers the rotation to the next resource optional MDT interface would allow the office to enter CFS in the rotation. The rotation occurs regardless of the disposition. resource ability to respond to the request. 1.10.1.1 Alternative Flows 1.9.5 Update Supplemental Service Record Detail [If supplemental service available] The supplemental resource response will be recorded in the system to reflect The optional MDT interface would allow the office to the services provided. enter CFS disposition.
Postcondition Description 1.10.2 Utilize Call Management [If call in progress] The call is managed by continually Supplemental A supplemental resource was updating the CFS data with any additional information Resource contacted with dispatch information reported by callers or officers on scene. The resource Dispatched and confirmed its availability to recommendations may be revised based on additional provide the service. information and may be added or reassigned.
1.10.3 Determine Reportability Postconditions [If services rendered] CFS may vary in the need to report beyond the CAD system. Guidelines are defined by the agency policy based upon a combination of call type and 1.10 Use Case Specification: Call call disposition. Disposition 1.10.3.1 Alternative Flows A call taker may close a CFS that does not require the dispatch of resources. Detail If the CFS is reportable, the assignment of an incident A CFS will be closed when the units at the scene have number from the RMS system may occur when the completed the assignment. Depending on the agency incident number is sent back with CAD report data to the SOP, the primary unit may close the call with a status. RMS. This may happen at any time prior to sending the The dispatcher is notified by assigned units of their status report but most likely after the determination that it will be change using voice or mobile data computer (MDC) sent. transactions. MDC transactions may update CAD to record the unit status and close the CFS, if the data 1.10.4 Record Disposition received indicates the CFS is complete. The CFS will be classified with a specific disposition, generally provided by [If nonreportable CFS] Record the disposition of the call for the primary unit. service. This may include a narrative in addition to the type of disposition. When a call is closed, information collected during the CFS may be automatically transferred from the CAD 1.10.5 Send Data to RMS system to the records management system (RMS). Any Call history (complete details on closed calls) is typically maintained in a CAD system for a relatively short time
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems 15 frame. While in CAD, the CAD system provides access 1.10.6 Assign RMS Incident Number based on a series of retrieval keys and/or parameters, [If report required] In addition to the CAD CFS number, including but not limited to call number, location, date/ an RMS incident number (case number) may be assigned time range, etc. Call history applies to the complete call, before the call is transferred to the RMS system. This including initial call information, unit assignments, status may happen at any time prior to sending the report but changes, imbedded inquiries and responses, triage most likely after the determination that it will be sent. The requests and results, comments, cross-references, etc. RMS number may be assigned from a data file of incident In other words, it contains everything that was recorded numbers maintained in the CAD system in coordination during the taking and handling of the CFS. with the RMS system. Department policies in this area must be supported by the CAD system. Long-term storage of call history records is normally relegated to either an RMS or a stand-alone calls-for- 1.10.6.1 Notes service system. The CFS history system is used for data Detail look-up and information retrieval, plus it supports extended statistical processes based on types of events, times to [Description] An RMS incident number included in data respond, calls by area, date/time, and so on. Because of sent to an RMS will trigger the creation of an instance of the need for statistical analysis, call history data needs to an incident report to relevant information captured from be structured so as to facilitate identifying specific types of CAD. data, such as events and associated dates and times.
16 Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems Business Function: 2 CAD System Administration
2.1 Description: The reporting area defined above should be used to define beats, sectors, command areas, neighborhoods, System administration encompasses a wide array of communities, etc. general requirements that law enforcement agencies need from CAD systems in order to be able to query information The geofile contains the geographic information that is the effectively; ensure appropriate access to information and basis for many decisions in a communications center. The systems security; and ensure effective information, image, system needs to provide the ability for an agency to enter and document management. and update all geofile data, including the physical address and the X/Y/Z coordinates. There are several distinct requirements associated with system administration: The creation of a comprehensive geofile is a significant undertaking. The system should support the creation and 1. Table maintenance maintenance of the geofile using an available mapping/GIS 2. Security and data management database. Geofile information in CAD and RMS should be . Geofile maintenance synchronized, based on established parameters. 4. Error logging Associated Actor Relationship Description 5. Customization System provides 2.2 Use Case Diagram (see page 18) RMS supplies 2.3 Use Case Specification: Geofile Maintenance 2.4 Use Case Specification: Security Systems should allow tiered access to information based The geofile is used to validate and standardize location on passwords and other authentication and nonrepudiation and address information. It is also used to cross-reference practices. Role-based authentication and authorization addresses and locations with law enforcement-defined must be a part of the RMS. Other identification reporting areas, X/Y/Z coordinates, ZIP codes, and other technologies—such as biometrics, ID card, security token, identifiers. The geofile contains sufficient information to etc.—are emerging standards. ensure that an address is valid. Furthermore, it provides cross-references to addresses and locations using Systems should apply appropriate edits to all entered data common place names (e.g., business names, parks, to ensure data integrity and maintain activity logs and audit hospitals, and schools) and street aliases. It includes trails. information such as direction of travel on particular streets and can identify the side of a street for a specific address. It is assumed that all addresses in the RMS are validated using the system geofile.
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems 17 2.2 CAD System supplies Geofile RMS Administration Maintenance Use Case Diagram provides
Security
provides Logging
provides
provides performs System System Table Maintenance Administrator
initiates allows
Configuration
supports
Communication Center Relocation
performs Call Taker CAD Catch-Up
performs
Dispatcher
Associated Actor Relationship Description Associated Actor Relationship Description
System provides System provides Administrator
2.6 Use Case Specification: 2.5 Use Case Specification: Logging Configuration CAD will log all actions, including security violations and attempted breeches, errors, changes, and updates. The CAD should be configurable to allow for the Logs should be viewable and searchable by the system enforcement of agency SOPs. Examples would include administrator. resource allocation algorithms and dispatch policies.
18 Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems The system should be configurable to determine screen Associated Actor Relationship Description parameters, color choices, font size, screen layout, and user preferences. Systems provides
Associated Actor Relationship Description System performs Administrator System allows 2.8 Use Case Specification: Communication Center Relocation 2.7 Use Case Specification: Table The support of an emergency that requires that the Maintenance dispatch center be moved to an off-site secure location must include a hardware system and network connectivity The flexibility needed in a CAD system requires that that will support the creation of an off-site, real-time the data used to support system recommendations or backup server at the relocated communication center. decisions be maintained in tables that can be supported and changed by the agency. Each department will have their own set of Standard Operating Procedures (SOPs) Associated Actor Relationship Description that must be followed with regard to table maintenance. System supports In addition, the CAD system must be flexible enough to allow the system setup to reflect the SOPs at the time the system is initially installed and to be changed when the 2.9 Use Case Specification: CAD department SOPs change. SOPs are typically defined and maintained in a separate document or they may be Catch-Up available for reference online as a CAD help file. The ability to recover from the interruption of CAD services, allowing the agency to enter activity data Examples of common tables include but are not limited to: performed during the interruption of service. 1. Units Associated Actor Relationship Description 2. Call types and priorities . Unit Status Types, e.g., assigned, unassigned, and System initiates assigned but available Administrator 4. Personnel, including emergency contact information Call Taker performs and current assignment Dispatcher performs 5. Service Providers 6. Patrol and command area definitions 7. Timers 8. Commands
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems 19 Business Function: 3 Support Services
3.1 Description: 3.3 Use Case Specification: BOLO In addition to the handling of calls for service, the CAD BOLO (Be on the Lookout) can be an optional part of a system should support the effective management of the CAD application or a part of an RMS system. BOLOs in available resources. The need for the optional items will CAD are created and maintained in a data file in CAD. be based on the agency size, the population served by the These may be entered by a dispatcher or may be created department, and other aspects of the specific department by anyone who has been given the required security or departments served by the CAD system. clearance to create or maintain the file.
Both an RMS interface and the mobile data terminal 3.2 Use Case Diagram interface should support the creation and transmission of a BOLO. A BOLO should be assigned an expiration Support Services Use Case Diagram date, either by the person who creates it or by the system, based on department policy and available system resources. A typical BOLO file would include the nature of the BOLO, priority, date, range of effectiveness, subject person and subject vehicle information, and contact information. There should be a mechanism to search the BOLO and to print it in a report and to purge the BOLOs out of the date range.
3.2 Support Services Use Case Diagram
provides System BOLO
provides Emergency Operations Center
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems 21 Associated Actor Relationship Description by the CAD system in support of EOC operation includes remote CAD dispatching capability and support for System provides multiagency event coordination.
These two optional features provide benefits to the CAD system even if the dispatcher does not have to be moved. 3.4 Use Case Specification: Emergency Multiagency event coordination usually requires that Operations Center support agreements be negotiated and in place among all of the agencies. Another desirable feature in support of The support of an emergency that requires that the an EOC would be the ability to add additional agencies “on dispatch center be moved to an off-site, secure location the fly” during an emergency operation. must include a hardware system and network connectivity that will support the creation of an off-site, real-time Associated Actor Relationship Description backup at servers located at the Emergency Operations Center (EOC). Other functionality that can be provided System provides
22 Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems Business Function: Call Management and 4 Management Reporting
4.1 Description: Associated Actor Relationship Description Command must be able to generate reports and manage the workflow of the call takers and dispatchers in the System provides Dispatch Center.
4.4 Use Case Specification: CAD 4.2 Use Case Diagram Management Reporting Call Management and Management Reporting Use Case Diagram It is essential that the CAD system include standard reports that can be run using flexible parameters. New reports should be defined either through the CAD system 4.3 Use Case Specification: Dispatch or a third-party reporting tool and then be stored as a standard report available through the CAD system. Supervisor Support The CAD system should provide the supervisor with the The functionality needs to include the ability to report any ability to monitor the activity on any dispatcher workstation. data element by any other data element in the system. If necessary, a supervisor needs to have the ability to take This may include the ability to export data for use in third- direct control over a dispatch position remotely, without party tools. A wizard may be provided that allows for user- leaving the supervisor console. generated reports.
4.2 Call Management and
Management Dispatch Reporting Use Supervisor Case Diagram provides Support
provides CAD System Management Reporting
Training and Testing
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems 23 Examples of typical CAD reports include the following maintenance testing, as well as training of new personnel. reports that can be run by any user-defined date and time This function may be referred to as a CAD training mode. range: To the greatest extent possible, the training environment 1. Daily log showing all calls received for the prior 24 should be identical to the production region, thus allowing hours from time of printing accurate testing and training to occur without impacting the production environment. The following are examples of 2. Activity Analysis by specified geographical area and by the types of items to include in the training environment: time period . CFS Summary by specified geographical area and by 1. Definition of the types of agencies being utilized; i.e., time period Law, Fire, EMS 4. Activity Analysis by day of the week 2. Tables defined to include unit names, recommendation 5. Activity Analysis by hour of the day patterns, premise information, personnel information, security permissions, etc. 6. Activity Analysis by day and hour . Separate test E911 connection or a canned script of 7. Response Time Analysis by specified geographical E911 information area and by time period 4. Separate test mobile connection or a canned script of 8. Response Time Analysis by call type mobile information 9. Time Consumed by call type by hour of the day 5. Access to audible radio transmissions 10. Workload Activity by resource The training environment should have its own start-and- 11. Workload Activity by group stop sequence that is independent of the production 12. Time Consumed by day of the week and hour of the environment. The training environment does not have to day be active at all times and can be started as needed. 1. Time Consumed by specified geographical area and By having the training environment established and by time period defined, the agency can develop a robust training 14. Attempted breaches in security program that simulates the live environment to include the 15. Error messages by type for identifying system associated interfaces and radio traffic. The personnel can problems enter incidents and “mock” live incidents that are occurring Customizing reports to meet department needs should on the radio without the production environment data being also be an option. affected. Additionally, any programmatic change or changes to Associated Actor Relationship Description file maintenance records can be thoroughly tested and any issues resolved prior to being implemented in the System provides production environment.
Associated Actor Relationship Description 4.5 Use Case Specification: Training and Testing System This function relates to the necessity of having a region on the CAD system that is isolated from the production environment for the purposes of program testing and file
24 Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems Business Function: 5 Interfaces
5.1 Description: Associated Actor Relationship Description CAD systems will interface with one or more systems, some of which are considered more essential than others. E911 Factors such as agency size, number of sworn officers, Messaging System agency budget, and unique community factors will affect whether agencies wish to adopt these optional interfaces. RMS
5.2 Use Case Diagram (see page 26) 5.4 Use Case Specification: Additional 5.3 Use Case Specification: Primary Interfaces These CAD interfaces are considered to be essential for conducting primary law enforcement business functions. It is often desirable to have a direct interface between the The four primary CAD interfaces are with the messaging CAD system and other key law enforcement systems, such system, the local RMS, Regional/State/NCIC Warehouses, as other CAD systems in the area, RMS systems, alarm and E911. systems, and mobile data terminals.
E911. This interface imports subscriber information CAD to CAD. The CAD will act as a peer in a multi- (ANI and ALI) for each E911 caller, as provided by the CAD environment. The CAD system will accept a new telephone company, into CAD-compliant entry process, call for service from a participating CAD system, in an eliminating the need for redundant data entry. As an agreed-upon structure. The CAD system can generate option, the E911 data can be simultaneously imported into and transfer a request for service to a peer CAD agency. the mapping system for immediate centering and display. The CAD system logs all communication between peer agencies. Regional/State/NCIC. Query to state, local, and national databases. Queries to the state, local RMS, and national Mobile Data Terminal (MDT). Mobile terminals in law databases will occur automatically from selected CAD enforcement vehicles provide an extension to the CAD commands using the messaging system interface. In dispatch services. The CAD system must interface with addition, the operator (e.g., dispatcher or officer) will have one or more mobile communications infrastructures to the ability to use stand-alone query screens, eliminating which the mobile units are attached. The CAD system can redundant data entry. Responses to such queries should provide silent dispatch orders to a mobile unit, in addition be stored with the call record. to providing the unit with details of the call and premise history information. The mobile unit can change its status, RMS: See RMS Interfaces. query CAD information, and query local and national databases, such as wanted-person checks. The queries may not go through CAD but may be part of a separate mobile system.
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems 25 Interfaces
Use Case E911 Primary Messaging Diagram System
RMS
Prearrival System External CAD
Additional Interfaces Mobile Data
Alarms
Push-to-Talk Communications Interfaces
Internet Call E-Mailing Generation Mobile Mapping
Faxing Paging
Locational Systems Interfaces GIS
null Clock Real-Time Synchronization Mapping AVL Administration Interfaces
Resource Scheduling System
Public Reverse 911 Awareness Messaging
Emergency Emergency Operations Operations Media Interface Center
26 Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems Prearrival Instruction System. The call taker answers to Mobile Mapping. Dispatch information sent to the mobile the questions posed by a prearrival system are written to can be mapped on the mobile itself. The map may provide CAD record of the call. Based on the capabilities of the the unit with driving instructions to the location. prearrival system, the call taker may be prompted by the prearrival system based on the CAD call type. Real-Time Mapping. Using the jurisdictional GIS information and the law enforcement map layers, the Alarm. The CAD system can automatically recognize dispatcher has a tactical view of the city and/or dispatch and accept notification of a business alarm. The system area. The map can be controlled by specific CAD coordinates the alarm input with a key-holder to present commands, such as zoom-and-pan, or preset commands, information to a call taker. Based upon business rules, the such as zooming to the address of a selected call for call taker can accept the alarm call and generate a call for service. The dispatcher can map/view all units and open service or manually handle the call. calls for service for an area or the city. Units and calls are labeled on the map. RMS. Whenever a case (report) number is generated for a CAD call for service, a basic set of CAD information is Associated Actor Relationship Description extracted and transferred to the RMS system to create the RMS incident shell. In addition, the CAD system may Mobile Mapping inquire into the RMS data files (e.g., master name index, master location index, warrants, or protective orders) for AVL null information that relates to the call. AVL A discussion of the business functions and situations that warrant CAD - RMS interface is explored in the LEITSC Real-Time Mapping RMS functional specification. GIS Associated Actor Relationship Description
Mobile Data 5.6 Use Case Specification: Prearrival System Administration Interfaces The Administration CAD interfaces assist the law Alarms enforcement team of units, dispatchers, call takers, and command in working together. The key interfaces External CAD include Push-to-Talk, master time interface, and Resource Push-to-Talk Scheduling System: Push-to-Talk. Import and display in a marquee fashion the radio ID (and optionally the Officer ID) information to the 5.5 Use Case Specification: Locational dispatcher by those keying mobile radios.
Systems Interfaces Interface and synchronize all servers and CAD Locational systems provide automated access to address, workstations with the Master Time Clock. This ensures geographic, and mapping information for law enforcement. that each workstation and server provides an accurate The primary locational systems include AVL, GIS, and time stamp. Mobile and Real-Time Mapping: Resource Scheduling System. A scheduling system AVL. The CAD system will accept input from an Automatic provides the ability for the agency to schedule personnel, Vehicle Location system. CAD converts the vehicle including communication center personnel and officers. geographical location (e.g., X/Y/Z coordinates) to a street This system is often found in the agency RMS. address, records the vehicle’s location in the unit history, and automatically performs a change location for the Typically, the system has the ability to factor in many vehicle, if necessary. of the departmental rules for scheduling personnel for regular assignments and for overtime. The interface GIS. Interface with the jurisdiction GIS to support with the CAD system may include the ability to have one maintenance of the CAD map; the law enforcement map point of maintenance for the names and assignments layers, such as reporting districts/areas; and the creation of all personnel. An interface may also include the roll- of the CAD geofile. call list for each shift change for dispatcher review and confirmation as units log on to the shift.
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems 27 Associated Actor Relationship Description Associated Actor Relationship Description
Clock Synchronization Paging
Resource Scheduling Faxing System E-Mailing 5.7 Use Case Specification: Internet Call Generation Communications Interfaces Messaging System There are several communications-based interfaces that allow CAD-generated information to be transmitted to others via e-mail, messaging, and the Internet. 5.8 Use Case Specification: Public Awareness Messaging Internet Call Generation. The CAD system will accept Public awareness messaging is the ability to broadcast, nondispatchable calls across the Internet. Calls accepted publish, and send messages to individuals or agencies across the Internet will be of a general nature, in which that need to be aware of critical events. Examples a case (report) number may be needed for insurance include Amber Alert, critical incident occurrences, utilities, purposes. The case number is generated and recorded. transportation, hospitals, or the public at large via the The call is recorded in the calls for service for statistical Internet. reporting. Reverse 911. This capability is typically a part of the Messaging System. The messaging system is often telephone system used in the communication center. The provided through a messages switch that can be interfaced system maintains a list of all callers who have elected to to the CAD system. The messaging system supports unit- be a part of this community alert system. An information to-unit messaging and unit-to-dispatcher messaging via message can be created. The system then calls every the MDT system. Optionally, the messaging system may person on the list and plays the voice message. There also support external messaging to other agencies. is usually not actually an interface between the CAD system and the Reverse 911 system unless the call list is Paging. The CAD system will automatically perform an maintained in the CAD database. The Web interface is an alphanumeric page for selected CAD calls and dispatches. option to provide citizens with the ability to add their name A dispatcher may initiate an alphanumeric page for to the call list for noncritical incidents. any paging group. The information sent in the page is configurable by the agency but generally contains the call number, type of call, and location of the call. There is an Associated Actor Relationship Description administrative mechanism to define paging groups. Reverse 911 Faxing. The CAD system will automatically format and Media send a FAX for selected CAD calls and dispatches. A dispatcher may initiate a FAX for any call/CFS. The information sent in a FAX is configurable by the agency but 5.9 Use Case Specification: Emergency generally contains the call information or a list of open calls meeting certain search criteria. There is an administrative Operations Interface mechanism to define FAX groups. The operation of an emergency center requires the multidirectional exchange of information between CAD E-mailing. The CAD system will automatically format and and EOC. Units may be assigned to the EOC, at which send an e-mail for selected CAD calls and dispatches. A point the EOC will take control of the unit until released. dispatcher may initiate an e-mail for any call/CFS. The CAD will maintain the ability to monitor the unit availability information sent in an e-mail is configurable by the agency status. CAD will continually update EOC with call but generally contains the call information or a list of information. open calls meeting certain search criteria. There is an administrative mechanism to define e-mail groups.
28 Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems Associated Actor Relationship Description
Emergency Operations Center
5.10 Additional Business Functions The CAD system should have the capability to communicate with one or more subsystems (i.e., EMS Dispatch, Fire Dispatch, and/or Intelligent Transportation). It is common for external agencies to become involved in a law enforcement call for service. Reasons such as agency size, number of sworn officers, agency budget, and unique community factors will affect whether agencies wish to communicate with external subsystems.
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems 29 6 Conclusion
LEITSC had a mission to create a national standard for law The functional standards found in this document are enforcement CAD systems and has succeeded in carrying intended to be generic in nature and do not favor one out this task. particular system or approach over another; they are at the functional level, meaning that they define what is to be The CAD functional standards are meant to describe the accomplished versus how it should be accomplished. minimal amount of functionality that a CAD system for law enforcement should contain. These standards should The CAD functional standards were developed by the be used as a starting point to build a fully functional CAD LEITSC Functional Standards Committee and are now system, based on agency needs and open standards, available to all law enforcement agencies. to efficiently interface and share information with other systems both internally and externally. They are designed to serve as a guiding tool for law enforcement agencies and should be tailored to fit the specific needs of each law enforcement agency or group of agencies looking to upgrade or purchase a new CAD system. Although the CAD functional standards were not developed to substitute for an RFP, they can be used to supplement an RFP.
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems 31 Appendix A Properties: Activity
Alert/Notify Units If not, the CFS location must be elicited from the caller. The dispatcher will relay information pertaining to calls In some incidents, the caller’s location may not be the for service to the appropriate units. This notification has location of the call for service. the purpose of informing and raising the awareness of designated teams or all officers. Check for Duplicate Calls The system automatically evaluates the CFS location (and Assign Call Classification and Priority potentially other site parameters) to determine whether a Assign nature code that may include general classification call is a duplicate. The call taker evaluates the information and subtypes of the call based upon agency policy. presented by the system with that obtained from the caller to make the final decision regarding duplicate calls. Calls The call will be prioritized based upon type, applying for service may be received by many sources for the established guidelines and procedures, to determine the same CFS, such as a traffic accident witnessed by two or appropriate dispatch and response needs. more motorists or a fire alarm reported from an electronic monitoring system and a witness reporting smoke coming Assign RMS Incident Number from a business. The call may be determined to be In addition to the CAD CFS number, an RMS incident unique, but there should be a capability of linking the call number (case number) may be assigned before the call to another existing call. is transferred to the RMS system. This may happen at any time prior to sending the report but most likely after This analysis will determine whether a new CFS is the determination that it will be sent. The RMS number recorded in CAD or an existing CFS is to be updated with may be assigned from a data file of incident numbers information not yet captured. maintained in the CAD system in coordination with the RMS system. Department policies in this area must be Correlate to Sector supported by the CAD system. The location information obtained from the caller and verified by the geofile will be checked to identify the patrol Assign Units area assignment in which the call is located. The dispatcher will assign a CFS and relay pertinent information to the appropriate units in the field for the Create Call for Service purpose of dispatching a responder. An optional MDC A new call for service is recorded in CAD using information interface supports this activity. compiled to date. A unique call number is assigned.
Assigned but available units may be pulled off of current Determine Call Status assigned status based on priority levels and the resource The CFS will remain open and monitored. The status of needs of the CFS. If all the units are pulled off of a call, the CFS may change as the situation is resolved. The the call will be added back into the dispatch queue. optional MDT interface would allow the office to enter CFS disposition. Capture Location In many instances, the call taker has access to the call origination location (ALI/ANI) data using the 911 system.
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems A:1 Determine Dispatch Need Examples include arrived on scene, available, unavailable, A decision is made to dispatch a unit or direct the CFS for and unavailable but assignable. More status types should disposition. be configurable.
Determine Proximity of Resources Enter Supplemental Service Record Resource proximity can be based on a closeness A record of supplemental service request is established calculation, which can be distance or driving time. Any to reflect the instance of the selection from the service unit suggestion must respect dispatch control areas rotation list. This triggers the rotation to the next resource and departmental SOP. Proximity determination can be in the rotation. The rotation occurs regardless of the supported by an optional AVL interface. resource ability to respond to the request.
Determine Reportability Maintain Status CFS may vary in the need to report beyond the CAD Information is continually displayed in CAD to reflect the system. Guidelines are defined by the agency policy current status of units that are monitored by the dispatcher. based upon a combination of call type and call disposition. Notify Supplemental Resource Service Determine Resource Availability The supplemental resource will be contacted to provide Available resources are displayed based upon unit status, dispatch information by the dispatcher and will be which includes unassigned as well as assigned with a provided information about the incident to which they are lower priority status of call to which a unit is assigned. The requested to respond. The availability of the service to units may be currently unassigned or assigned to a CFS provide services will be recorded. A supplemental service with a designated type and priority level. Unassigned units that cannot be contacted or informs the agency of their are available to be dispatched. inability to respond within a prescribed time is considered unavailable to provide the service. A supplemental Dispatch Resource Decision resource will be selected from the list until one is found Recommended resources to be assigned based on SOP, that is available. which factor workload, unit capability with regard to skills and equipment required for the CFS, unit availability, and Override Resource Requirement the proximity of resources. The initial recommendation based upon known criteria may be adjusted based upon additional information that Display Additional CFS Data becomes available, such as learning that the suspect is As additional information is made available, the dispatcher known to be armed and dangerous. Override must be will be alerted and have the ability to view the new recorded. information; for example, any information entered by a call taker or another dispatcher. Place Call on Unassigned Status The unit is reassigned to a new call and automatically Display CFS Data unassigned from the previous call. The CFS will need to be displayed and monitored through CAD. This includes activities such as additional Reassign to Available call information and activities reported by the officers. When a unit has cleared from a scene and is no longer Immediate access to all open calls (including unassigned) assigned to the CFS, the unit will be reassigned to an should be provided on the CFS status display. When a available status. Data received from MDC transmissions call is closed, it will automatically be removed from the call may update CAD and reflect the new status of the unit. display. The unit may remain on scene and have an available on- scene status. Display Unit Dispatch Status The current status of units will be available at all times. Recognize Acknowledgement The display will indicate the unit’s status and assigned The unit assigned to the call will respond to the dispatcher calls for service (if any). The display can also show the to confirm receipt of the dispatch information. This may location or last known location of the unit. In the absence be done by voice communication or through mobile data of AVL, the location may be the current call location, the computers. last call location, or the location entered by the dispatcher or MDC. In the case of assigned units, the display may Record Arrival on Scene show any alert timer, the CFS type, and priority. Units responding to the scene communicate to dispatch that they have arrived at the location. This communication may occur verbally or through an MDC transmission that
A:2 Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems may automatically update CAD to reflect the current status priority over calls from direct phone lines. The center’s of the responding unit, including time of arrival on scene. operating procedures will determine whether any call is allowed to go to voice mail or be put on hold. There may be a need to record multiple arrival times; an example would be the arrival at the location and another Retrieve Person Information arrival at the scene. For example, a unit may arrive at the Person information may include history, protection orders, location of a high-rise building and at a later time will arrive warrants, mental or health issues, gang information, sex at the scene located within the building. The system should offender registry information, etc. provide for the setting of different timers based upon time of arrival type. This could be automatically queried based upon information entered into fields, if available. Record CFS Activity The CFS record will be updated to associate the unit or Retrieve Premise Hazard and History units dispatched as responding units to the call. Relevant historical and tactical information about specific and neighboring premises is obtained from internal and/or Record Disposition external sources for decision support. This information Record the disposition of the call for service. This may may include information about previous calls for service include a narrative in addition to the type of disposition. at the premise, whether the premise has records of registered firearms, hazardous materials stored at the Record Unit Activity site (usually business sites), serious medical information The unit status will be updated to associate the dispatched concerning individuals residing at the premise, and other unit or units with the CFS, including location and time. relevant information.
Record Unit Location Retrieve Resource Recommendations Any change in unit location is captured along with time Resource recommendations are initially determined stamps, including changes of location associated with the based on the call type, priority and location information, same CFS. and other characteristics of the specific CFS. The call type and priority level are used based on agency policy Reopen CFS and procedure. The dispatcher must review resources An existing CFS is reopened for update. Changes are recommended by the system. In selecting appropriate traced for audit purposes. resources, the dispatcher may consider a number of factors, such as proximity to the call location, number of Request Supplemental Resource units available, special skills or equipment, and the number A law enforcement official requests that a supplemental and type of other CFS to which officers are responding. resource service be dispatched to a specified location. These factors may or may not have been considered in the initial system recommendation. Retrieve Alarm Location Obtain the location of an electronic-generated call from the Retrieve Supplemental Resource Rotation List call source information. Location and contact information The agency will obtain the contact information from the from electronic sources may be received from data system in order to contact and request service from the exchanges to CAD or may be obtained from a database of next eligible service. The system may provide a list of one common addresses maintained by the agency. or more services. This could be based on geographical requirements. Retrieve CFS From Call Pending Queue The next CFS on the call pending queue is retrieved. Retrieve Vehicle Information The call will contain all information collected during the This includes any pertinent information about a vehicle. call up to the point it is retrieved. Additional information This could be automatically queried based upon may continue to be added to the call by call takers and information entered into fields, if available. dispatchers while the CFS is open. Review Call Background Information Calls in the queue are stacked by agency-defined priority, The information associated with the location and /or often based on SOP. The CAD system allows the agency affiliated person is considered to determine whether the to determine the sort order of the call pending queue. recommended resources are adequate. The decision to override the resource requirement should be made if it is Retrieve Incoming Call determined that the recommendation is inadequate. Incoming calls by phone are answered in the order that they come in. Calls from the 911 system are given a
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems A:3 Send Data to RMS The following are examples of the types of data found in Call history (complete details on closed calls) is typically an incident report: report number, CAD call type, nature maintained in a CAD system for a relatively short time of call, date/time of call, location of incident, and persons frame. While in CAD, the CAD system provides access and vehicles involved. The CAD CFS number should be based on a series of retrieval keys and/or parameters, included to provide a cross-reference between the CFS including but not limited to call number, location, date/ and the subsequent incident report. time range, etc. Call history applies to the complete call, including initial call information, unit assignments, status Incident transfer is normally triggered and takes place changes, imbedded inquiries and responses, triage automatically. Within the framework of this standard, it requests and results, comments, cross-references, etc. would happen (optionally) as an incident report number is In other words, it contains everything that was recorded assigned and at the time of final disposition of the CFS. during the taking and handling of the CFS. The CAD systems should include a feature whereby administrative commands can be executed to transfer Long-term storage of call history records is normally either a specific incident or a series of incidents based relegated to either an RMS or a stand-alone calls for upon parameters. service system. The CFS history system is used for data look-up and information retrieval, plus it supports extended Update Assigned Resources statistical processes based on types of events, times to When required resources for the call have changed, this respond, calls by area, date/time, and so on. Because of will be adjusted and recorded on predetermined criteria. the need for statistical analysis, call history data needs to be structured so as to facilitate identifying specific types of Update CFS Data data, such as events and associated dates and times. Information related to an open call will be updated as information becomes available. Multiple callers Take Caller Data provide potential witnesses to the call and may provide The call taker requests basic information of the caller. additional or supportive information. This may result Many 911 systems provide information about the phone in reclassification and prioritization of the call. The account (ANI) originating the call, which may or may not be dispatcher will need the ability to enter narrative data at verified immediately, depending on the nature and priority any time prior to closing the CFS. of the call. Update Call Status The basic information needed to open and initiate a CFS The status of the call is updated as new information is is the type of call (nature of the complaint), the priority, and received. This should include updating the reported the location of the CFS. Depending upon the priority of the CFS type to the actual CFS type. For example, once the call, when basic information has been entered, the CFS immediate incident is resolved, the responding unit will can be routed to the appropriate dispatcher for handling. communicate to the dispatcher that the scene is secured.
Timed Alerts Update Supplemental Service Record The system must be able to alert the dispatcher to the The supplemental resource response will be recorded in expiration of the timer associated with any status change. the system to reflect the services provided. The alert to the dispatcher may be in the form of a tone and/or a visual prompt. This should be configurable based Update Unit Status upon the type of CFS. The system should record the Information is continually updated in CAD to reflect the acknowledgement or action of the dispatcher in response current status of units that are monitored by the dispatcher. to the prompt, which will automatically reset the timer. Verify Location Transfer Basic Incident Data to RMS The caller location will be checked against current address Basic incident data that can be modified will be transferred listings in the system. Locations that are not verified to the agency records section for its use. It will be provide an indication to the call taker that information transferred in an editable format. received may be inaccurate, providing additional information for the dispatcher to relay to the responder. This function relates to the transfer from CAD to RMS of the CFS data elements normally contained in a law The location format can be a street address (blockface enforcement incident report. In fact, the Justice XML address), intersection, or common place name. Location reference document for a law enforcement incident report information for a common place, such as the City Hall, has should provide an excellent standard for the transfer. a street address listing cross-reference that will provide the legal street address. Information will be contained in a
A:4 Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems geofile, which must include latitude and longitude. Altitude would be optional.
The geofile will:
1. Validate that the street name is an actual street in the service area. 2. Resolve ambiguities while accounting for spelling variations and duplications. . Validate intersections. 4. Validate address range. 5. Relate common place names to actual addresses. 6. Relate X/Y/Z coordinates to an actual address. 7. Transform latitude and longitude to map coordinates for display. 8. Translate call location to agency reporting area. 9. Translate alias names to actual street names.
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems A:5 Appendix A Properties: Actor
AVL Dispatcher The CAD system will accept input from an Automatic Agency official responsible for the deployment of Vehicle Location system. CAD converts the vehicle resources in response to calls for service. geographical location (e.g., XY coordinates) to a street address, records the vehicle location in the unit history, E911 and automatically performs a change location for the This interface imports subscriber information (ANI and vehicle, if necessary. ALI) for each E911 caller, as provided by the telephone company, into CAD-compliant entry process, eliminating Alarm the need for redundant data entry. As an option, the E911 Business alarm or other optional interface provides data data can be simultaneously imported into the mapping only. system for immediate centering and display.
Alarms E-Mailing The CAD system can automatically recognize and accept The CAD system will automatically format and send an notification of a business alarm. The system coordinates e-mail for selected CAD calls and dispatches. A dispatcher the alarm input with a key-holder to present information to may initiate an e-mail for any call/CFS. The information the call taker. Based upon business rules, the call taker sent in an e-mail is configurable by the agency but can accept the alarm call and generate a call for service or generally contains the call information or a list of open calls manually handle the call. meeting certain search criteria. There is an administrative mechanism to define e-mail groups. Call Taker Any individual employed or contracted by the agency that Emergency Operations Center is designated the first point of contact with the agency. In A location where emergency incident management takes most agencies, this will be via a 911 emergency services place requiring incident and unit status information from system or the law enforcement officer initiating the call. CAD. Control of specific units may be relinquished to the EOC. Caller Any individual or electronic monitoring and notification External Agency system establishing contact with the law enforcement A high-level representation of any local, state, federal, or agency for the purpose of communicating. This county agency external to the law enforcement agency. communication may be a call for service (CFS), to notify or provide information regarding an event in progress, or for External CAD other business-related purposes. CAD systems between jurisdictions must be able to send/ receive data to facilitate dispatching of services defined in Clock Synchronization jurisdictional service agreements. This integration includes Interface and synchronize all servers and CAD the ability to receive event data and/or transmit event data. workstations with the Master Time Clock (Netclock). This ensures that each workstation and server provides an accurate time stamp.
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems A:7 External CAD Mobile Mapping The CAD will act as a peer in a multi-CAD environment. Dispatch information sent to the mobile can be mapped The CAD system will accept a new call for service from a on the mobile itself. The map may provide the unit with participating CAD system, in an agreed-upon structure. driving instructions to the location. The CAD system can generate and transfer a request for service to a peer CAD agency. The CAD system logs all Paging communication between peer agencies. The external CAD The CAD system will automatically perform an system may be other public service or safety systems. alphanumeric page for selected CAD calls and dispatches. A dispatcher may initiate an alphanumeric page for Faxing any paging group. The information sent in the page is The CAD system will automatically format and send a FAX configurable by the agency but generally contains the call for selected CAD calls and dispatches. A dispatcher may number, type of call, and location of the call. There is an initiate a FAX for any call/CFS. The information sent in a administrative mechanism to define paging groups. FAX is configurable by the agency but generally contains the call information or a list of open calls meeting certain Prearrival System search criteria. There is an administrative mechanism to The answers to the questions posed by the call taker in define FAX groups. a prearrival system are written to CAD record of the call. Based on the capabilities of the prearrival system, the call GIS taker may be prompted by the prearrival system based on Interface with city/county GIS to support maintenance the CAD call type. of a CAD map; the law enforcement map layers, such as reporting districts/areas; and the creation of the CAD Push-to-Talk geofile. Import and display in a marquee fashion the radio ID (and optionally the Officer ID) information to the dispatcher by Internet Call Generation those keying mobile radios. The CAD system will accept nondispatchable calls across the Internet. Calls accepted across the Internet will be RMS of a general nature where a case (report) number may Whenever a case (report) number is generated for CAD be needed for insurance purposes. The case number is call for service, a basic set of CAD information is extracted generated and recorded. The call is recorded in the calls and transferred to the RMS system to create the RMS for service for statistical reporting. incident shell. In addition, the CAD system may inquire into the RMS data files (e.g., master name index, master Media location index, warrants, and protective orders) for Media sources that have the ability to alert the public of information that relates to the call. critical situations or other more specific alerts. Real-Time Mapping Messaging System Using the city/county GIS information and the law The messaging system is often provided through a enforcement map layers, the dispatcher has a tactical messages switch that can be interfaced to the CAD view of the city and/or dispatch area. The map can be system. The messaging system supports unit-to-unit controlled by specific CAD commands, such as zoom-and- messaging and unit-to-dispatcher messaging via the MDT pan, or preset commands, such as zooming to the address system. Optionally, the messaging system may also of a selected call for service. The dispatcher can map/ support external messaging to other agencies. view all units and open calls for service for an area or the city. Units and calls are labeled on the map. Mobile Data Mobile terminals in law enforcement vehicles provide an Resource Scheduling System extension to the CAD dispatch services. The CAD system A scheduling system provides the ability for the agency must interface with one or more mobile communications to schedule personnel, including communication center infrastructures to which the mobile units are attached. The personnel and officers. Typically, the system has the CAD system can provide silent dispatch orders to a mobile ability to factor in many of the department rules for unit, in addition to providing the unit with details of the scheduling personnel for regular assignments and for call and premise history information. The mobile unit can overtime. The interface with the CAD system may include change its status, query CAD information, and query local the ability to have one point of maintenance for the names and national databases, such as wanted-person checks. and assignments of all personnel. An interface may also include the roll-call list for each shift change for the dispatcher review and confirmation as units log on to the shift.
A:8 Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems Reverse 911 This capability is typically a part of the telephone system used in the communication center. The system maintains a list of all callers who have elected to be a part of this community alert system. An information message can be created. The system then calls every person on the list and plays the voice message. There is usually not actually an interface between the CAD system and the Reverse 911 system unless the call list is maintained in the CAD database. The Web interface is required to provide citizens the ability to add their name to the call list.
System The CAD and RMS systems.
System Administrator Telephone Reporting Unit An agency may employ a telephone reporting unit that takes incident reports without requiring dispatch resources.
Unit An identifier is assigned to the car that will be used to identify the vehicle throughout the shift. Dispatchers will know the specialty of the unit (e.g., evidence tech, K-9 unit). A unit may initiate a call either by observing and reporting an incident to the dispatcher or by placing the unit on a call, such as a traffic stop.
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems A:9 Appendix Properties: A Business Function
CAD System Administration Interfaces System administration encompasses a wide array of CAD systems will interface with one or more systems, general requirements that law enforcement agencies need some of which are considered more essential than others. from CAD systems in order to be able to query information Factors such as agency size, number of sworn officers, effectively; ensure appropriate access to information and agency budget, and unique community factors will affect systems security; and ensure effective information, image, whether agencies wish to adopt these optional interfaces. and document management. Law Enforcement Dispatch There are several distinct requirements associated with Law enforcement agencies use CAD to facilitate incident system administration: response and communication in the field. CAD systems, in many cases, are the first point of entry for information 1. Table maintenance coming into the law enforcement system. Typical CAD 2. Security and data management system functions include resource management, call . Geofile maintenance taking, location verification, dispatching, unit status management, and call disposition. Additionally, mapping 4. Error logging functionality, interface with mobile data computers (MDC), 5. Customization and interfaces with other external local, state, and federal information systems may be included. Call takers, Call Management and Management Reporting dispatchers, and their supervisors are primary users Command must be able to generate reports and manage of CAD. Units in the field may interact via mobile data the workflow of the call takers and dispatchers in the computers. dispatch center. Support Services EMS Dispatch In addition to the handling of calls for service, the CAD This represents the EMS Dispatch subsystem of CAD. system should support the effective management of the available resources. The need for the optional items will Fire Dispatch be based on the agency size, the population served by the This represents the Fire Dispatch subsystem of CAD. department, and other aspects of the specific department or departments served by the CAD system. Intelligent Transportation This represents the Intelligent Transportation subsystem of CAD.
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems A:11 Appendix A Properties: State
Active Call for Service Resources Dispatched A CFS was created in CAD and is currently active. The completion of assigning appropriate resources to a CFS. CFS Resource Assigned Resources appropriate for the CFS have been determined Routed and assigned. Information in voice, paper, or electronic form was recorded and sent or distributed to intended recipients. Call Closed Record the disposition of the CFS. Status Recorded The status of the unit is recorded in the CAD system. Call Monitored Dispatchers monitor the CFS as it unfolds to ensure that Supplemental Resource Dispatched adequate resources are available to secure the scene and A supplemental resource was contacted with dispatch ensure public safety. Dispatchers also act on requests for information and confirmed their availability to provide the resources that are received from the scene. service.
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems A:13 Appendix A Properties: Use Case
Additional Interfaces RMS. Whenever a case (report) number is generated for It is often desirable to have a direct interface between the a CAD call for service, a basic set of CAD information is CAD system and other key law enforcement systems, such extracted and transferred to the RMS system to create as other CAD systems in the area, RMS systems, alarm the RMS incident shell. In addition, the CAD system may systems, and mobile data terminals. inquire into the RMS data files (e.g., master name index, master location index, warrants, and protective orders) for CAD to CAD. The CAD will act as a peer in a multi- information that relates to the call. CAD environment. The CAD system will accept a new call for service from a participating CAD system, in an A discussion of the business functions and situations that agreed-upon structure. The CAD system can generate warrant CAD - RMS interface is explored in the LEITSC and transfer a request for service to a peer CAD agency. RMS functional specifications. The CAD system logs all communication between peer agencies. Administration Interfaces The Administration CAD interfaces assist the law Mobile Data Terminal (MDT). Mobile terminals in law enforcement team of units, dispatchers, call takers, enforcement vehicles provide an extension to the CAD and command in working together. The key interfaces dispatch services. The CAD system must interface with include Push-to-Talk, master time interface, and Resource one or more mobile communications infrastructures to Scheduling System: which the mobile units are attached. The CAD system can provide silent dispatch orders to a mobile unit, in addition Push-to-Talk. Import and display in a marquee fashion the to providing the unit with details of the call and premise radio ID (and optionally the Officer ID) information to the history information. The mobile unit can change its status, dispatcher by those keying mobile radios. query CAD information, and query local and national databases, such as wanted-person checks. The queries Interface and synchronize all servers and CAD may not go through CAD but may be part of a separate workstations with the Master Time Clock. This ensures mobile system. that each workstation and server provides an accurate time stamp. Prearrival Instruction System. The call taker answers to the questions posed by a prearrival system are written to Resource Scheduling System. A scheduling system CAD record of the call. Based on the capabilities of the provides the ability for the agency to schedule personnel, prearrival system, the call taker may be prompted by the including communication center personnel and officers. prearrival system based on the CAD call type. This system is often found in the agency RMS.
Alarm. The CAD system can automatically recognize Typically, the system has the ability to factor in many and accept notification of a business alarm. The system of the departmental rules for scheduling personnel for coordinates the alarm input with a key-holder to present regular assignments and for overtime. The interface information to a call taker. Based upon business rules, the with the CAD system may include the ability to have one call taker can accept the alarm call and generate a call for point of maintenance for the names and assignments service or manually handle the call. of all personnel. An interface may also include the roll-
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems A:15 call list for each shift change for dispatcher review and 7. Response Time Analysis by specified geographical confirmation as units log on to the shift. area and by time period 8. Response Time Analysis by call type BOLO 9. BOLO (Be on the Lookout) can be an optional part of a Time Consumed by call type by hour of the day CAD application or a part of an RMS system. BOLOs in 10. Workload Activity by resource CAD are created and maintained in a data file in CAD. 11. Workload Activity by group These may be entered by a dispatcher or may be created 12. Time Consumed by day of the week and hour of the by anyone who has been given the required security day clearance to create or maintain the file. 1. Time Consumed by specified geographical area and Both an RMS interface and the mobile data terminal by time period interface should support the creation and transmission 14. Attempted breaches in security of a BOLO. A BOLO should be assigned an expiration 15. Error messages by type for identifying system date, either by the person who creates it or by the problems system, based on department policy and available system resources. A typical BOLO file would include the nature Customizing reports to meet department needs should of the BOLO, priority, date, range of effectiveness, subject also be an option. person and subject vehicle information, and contact information. There should be a mechanism to search the Call Disposition BOLO and to print it in a report and to purge the BOLOs A call taker may close a CFS that does not require the out of the date range. dispatch of resources.
CAD Catch-Up A CFS will be closed when the units at the scene have The ability to recover from the interruption of CAD completed the assignment. Depending on the agency services, allowing the agency to enter activity data SOP, the primary unit may close the call with a status. performed during the interruption of service. The dispatcher is notified by assigned units of their status change using voice or mobile data computer (MDC) CAD Management Reporting transactions. MDC transactions may update the CAD It is essential that the CAD system include standard to record the unit status and close the CFS, if the data reports that can be run using flexible parameters. New received indicates the CFS is complete. The CFS will be reports should be defined either through the CAD system classified with a specific disposition, generally provided by or a third-party reporting tool and then be stored as a the primary unit. standard report available through the CAD system. When a call is closed, information collected during the The functionality needs to include the ability to report any CFS may be automatically transferred from the CAD data element by any other data element in the system. system to the records management system (RMS). Any This may include the ability to export data for use in third- updates made by the CAD operators on reopened calls party tools. A wizard may be provided that allows for user- will be automatically transferred to RMS, subject to agency generated reports. policies.
Examples of typical CAD reports include the following In instances where a duplicate call is identified, one call is reports that can be run by any user-defined date and time disposed with a cross-reference to the original CFS. The range: calls will be linked for future retrievability.
1. Daily log showing all calls received for the prior 24 Call Management hours from time of printing The call is managed by continually updating the CFS data with any additional information reported by callers or 2. Activity Analysis by specified geographical area and by officers on scene. The resource recommendations may be time period revised based on additional information and may be added . CFS Summary by specified geographical area and by or reassigned. time period 4. Activity Analysis by day of the week Call Taking 5. Activity Analysis by hour of the day Calls for service (CFS) initiate the CAD process. Callers are citizens or other agencies requesting services from 6. Activity Analysis by day and hour the agency or giving notification of events or activities of concern. A CFS may come from many different points of
A:16 Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems origin such as alarm systems, E911 systems, direct calls Faxing. The CAD system will automatically format and (7- or 10-digit numbers), walk-ins, CAD-to-CAD interfaces send a FAX for selected CAD calls and dispatches. A or Web-based systems. dispatcher may initiate a FAX for any call/CFS. The information sent in a FAX is configurable by the agency but The service requested by callers will consist of both generally contains the call information or a list of open calls emergency and nonemergency priorities. Call taking meeting certain search criteria. There is an administrative consists of receiving the call, obtaining sufficient and mechanism to define FAX groups. accurate information from the caller, determining whether this is a duplicate of a call in progress, and recording or E-mailing. The CAD system will automatically format and updating the CFS in the CAD system. The call taker may send an e-mail for selected CAD calls and dispatches. A also apply procedures and guidelines to verify, analyze, dispatcher may initiate an e-mail for any call/CFS. The classify, and prioritize the call prior to routing the CFS to information sent in an e-mail is configurable by the agency the dispatcher. A CFS may also be generated by a unit in but generally contains the call information or a list of the field. The unit can contact the dispatcher or the call open calls meeting certain search criteria. There is an taker, or he may actually create the call electronically using administrative mechanism to define e-mail groups. the optional MDT interface. Configuration A CFS may be forwarded to a telephone reporting unit and The CAD should be configurable to allow for the be received from the telephone reporting unit. enforcement of agency SOPs. Examples would include resource allocation algorithms and dispatch policies. This may include the ability to create a CFS for future scheduled events. The system should be configurable to determine screen parameters, color choices, font size, screen layout, and Communication Center Relocation user preferences. The support of an emergency that requires that the dispatch center be moved to an off-site secure location Dispatch Decision Support must include a hardware system and network connectivity The dispatcher is presented with the recommended that will support the creation of an off-site, real-time resources for the selected CFS, based upon preset criteria backup server at the relocated communication center. for the type and priority of CFS. Further information will be considered, such as the history of the location, suspect, Communications Interfaces and the possibility that hazardous materials may be There are several communications-based interfaces that involved. The recommended resources may be overridden allow CAD-generated information to be transmitted to by the dispatcher based on the additional information others via e-mail, messaging, and the Internet. or requests by officers on the scene. The system may have the capability to perform dispatch decision support, Internet Call Generation. The CAD system will accept such as assigning an incident number without human nondispatchable calls across the Internet. Calls accepted intervention. across the Internet will be of a general nature where a case (report) number may be needed for insurance Units available will be considered as well as the available purposes. The case number is generated and recorded. unit proximity to the CFS. The final decision is which The call is recorded in the calls for service for statistical specific units to dispatch. reporting. Dispatch Supervisor Support Messaging System. The messaging system is often The CAD system should provide the supervisor with the provided through a messages switch that can be interfaced ability to monitor the activity on any dispatcher workstation. to the CAD system. The messaging system supports unit- If necessary, a supervisor needs to have the ability to take to-unit messaging and unit-to-dispatcher messaging via direct control over a dispatch position remotely, without the MDT system. Optionally, the messaging system may leaving the supervisor console. also support external messaging to other agencies. Dispatch Units Paging. The CAD system will automatically perform an The units specifically recommended or selected for a CFS alphanumeric page for selected CAD calls and dispatches. will be dispatched and their acknowledgment recorded. A dispatcher may initiate an alphanumeric page for Other units not dispatched may be notified of an event in any paging group. The information sent in the page is progress if the CFS warrants. When multiple units are configurable by the agency but generally contains the call dispatched, one unit will be designated as the primary number, type of call, and location of the call. There is an responder responsible for the CFS until it is completed. administrative mechanism to define paging groups.
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems A:17 Emergency Operations Center database. Geofile information in CAD and RMS should be The support of an emergency that requires that the synchronized, based on established parameters. dispatch center be moved to an off-site secure location must include a hardware system and network connectivity Locational Systems Interfaces that will support the creation of an off-site, real-time Locational systems provide automated access to address, backup at servers located at the Emergency Operations geographic, and mapping information for law enforcement. Center (EOC). Other functionality that can be provided The primary locational systems include AVL, GIS, and by the CAD system in support of EOC operation includes Mobile and Real-Time Mapping: remote CAD dispatching capability and support for multiagency event coordination. AVL. The CAD system will accept input from an Automatic Vehicle Location system. CAD converts the vehicle These two optional features provide benefits to the CAD geographical location (e.g., X/Y/Z coordinates) to a street system even if the dispatcher does not have to be moved. address, records the vehicle’s location in the unit history, Multiagency event coordination usually requires that and automatically performs a change location for the support agreements be negotiated and in place among all vehicle, if necessary. of the agencies. Another desirable feature in support of an EOC would be the ability to add additional agencies “on GIS. Interface with the jurisdiction GIS to support the fly” during an emergency operation. maintenance of the CAD map; the law enforcement map layers, such as reporting districts/areas; and the creation Emergency Operations Interface of the CAD geofile. The operation of an emergency center requires the multidirectional exchange of information between CAD Mobile Mapping. Dispatch information sent to the mobile and EOC. Units may be assigned to the EOC, at which can be mapped on the mobile itself. The map may provide point the EOC will take control of the unit until released. the unit with driving instructions to the location. CAD will maintain the ability to monitor the unit availability status. CAD will continually update EOC with call Real-Time Mapping. Using the jurisdictional GIS information. information and the law enforcement map layers, the dispatcher has a tactical view of the city and/or dispatch Geofile Maintenance area. The map can be controlled by specific CAD The geofile is used to validate and standardize location commands, such as zoom-and-pan, or preset commands, and address information. It is also used to cross-reference such as zooming to the address of a selected call for addresses and locations with law enforcement-defined service. The dispatcher can map/view all units and open reporting areas, X/Y/Z coordinates, ZIP codes, and other calls for service for an area or the city. Units and calls are identifiers. The geofile contains sufficient information to labeled on the map. ensure that an address is valid. Furthermore, it provides Logging cross-references to addresses and locations using common place names (e.g., business names, parks, CAD will log all actions including security violations and hospitals, and schools) and street aliases. It includes attempted breeches, errors, changes, and updates. information such as direction of travel on particular streets Logs should be viewable and searchable by the system and can identify the side of a street for a specific address. administrator. It is assumed that all addresses in the RMS are validated Primary using the system geofile. CAD interfaces considered to be essential for conducting The reporting area defined above should be used to primary law enforcement business functions. The four define beats, sectors, command areas, neighborhoods, primary CAD interfaces are with the messaging system, communities, etc. the local RMS, Regional/State/NCIC Warehouses, and E911. The geofile contains the geographic information that is the basis for many decisions in a communications center. The E911. This interface imports subscriber information system needs to provide the ability for an agency to enter (ANI and ALI) for each E911 caller, as provided by the and update all geofile data, including the physical address telephone company, into CAD-compliant entry process, and the X/Y/Z coordinates. eliminating the need for redundant data entry. As an option, the E911 data can be simultaneously imported into The creation of a comprehensive geofile is a significant the mapping system for immediate centering and display. undertaking. The system should support the creation and maintenance of the geofile using an available mapping/GIS
A:18 Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems Regional/State/NCIC. Query to state, local, and national Table Maintenance databases. Queries to the state, local RMS, and national The flexibility needed in a CAD system requires that databases will occur automatically from selected CAD the data used to support system recommendations or commands using the messaging system interface. In decisions be maintained in tables that can be supported addition, the operator (e.g., dispatcher or officer) will have and changed by the agency. Each department will have the ability to use stand-alone query screens eliminating their own set of Standard Operating Procedures (SOPs) redundant data entry. Responses to such queries should that must be followed with regard to table maintenance. be stored with the call record. In addition, the CAD system must be flexible enough to RMS: See RMS interfaces. allow the system setup to reflect the SOPs at the time the system is initially installed and to be changed when the Public Awareness Messaging department SOPs change. SOPs are typically defined The ability to broadcast, publish, or send messages to and maintained in a separate document, or they may be individuals or agencies that need to be aware of critical available for reference online as a CAD help file. events. Examples include Amber Alert, critical incident occurrences, utilities, transportation, hospitals, or the Examples of common tables include but are not limited to: public at large via the Internet. 1. Units Reverse 911. This capability is typically a part of the 2. Call types and priorities telephone system used in the communication center. The . system maintains a list of all callers who have elected to Unit Status Types; e.g., assigned, unassigned, or be a part of this community alert system. An information assigned but available message can be created. The system then calls every 4. Personnel, including emergency contact information person on the list and plays the voice message. There and current assignment is usually not actually an interface between the CAD 5. Service providers system and the Reverse 911 system unless the call list is 6. Patrol and command area definitions maintained in the CAD database. The Web interface is an option to provide citizens with the ability to add their name 7. Timers to the call list, for noncritical incidents. 8. Commands
Security Training and Testing Systems should allow tiered access to information based This function relates to the necessity of having a region on passwords and other authentication and nonrepudiation on the CAD system that is isolated from the production practices. Role-based authentication and authorization environment for the purposes of program testing or file must be a part of the RMS. Other identification maintenance testing, as well as training of new personnel. technologies—such as biometrics, ID card, security token, This function may be referred to as a CAD training mode. etc.—are emerging standards. To the greatest extent possible, the training environment Systems should apply appropriate edits to all entered data should be identical to the production region, thus allowing to ensure data integrity and maintain activity logs and audit accurate testing and training to occur without impacting the trails. production environment. The following are examples of the types of items to include in the training environment: Supplemental Resources Tracking For example, in cases where a vehicle has been 1. Definition of the types of agencies being utilized; i.e., confiscated or found to be disabled, the dispatcher needs Law, Fire, EMS the ability to request the services of a towing company. 2. Tables defined to include unit names, recommendation This request may be made by company name (owner patterns, premise information, personnel information, requested) or by rotation. In cases where the owner does security permissions, etc. not have a preferred company, the system will select . a company from the towing rotation. A towing rotation Separate test E911 connection or a canned script of prevents any one company from being favored over E911 information another. 4. Separate test mobile connection or a canned script of mobile information If resources other than those recommended by the rotation 5. Access to audible radio transmissions are selected, the system should capture the reason for the exception. The training environment should have its own start-and- stop sequence that is independent of the production
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems A:19 environment. The training environment does not have to be active at all times and can be started as needed.
By having the training environment established and defi ned, the agency can develop a robust training program that simulates the live environment to include the associated interfaces and radio traffi c. The personnel can enter incidents and “mock” live incidents that are occurring on the radio without the production environment data being affected.
Additionally, any programmatic change or changes to fi le maintenance records can be thoroughly tested and any issues resolved prior to being implemented in the production environment.
Unit Status Management Unit status must be continually monitored, updated, and recorded by the dispatcher. This information may be made available by voice communication or through mobile data computers. In addition to recording the unit status and destination, the CFS number and times (action) will also be recorded by the system. The recording of status changes is representative of a unit’s work activity during a time interval. This information is essential to running standard CFS reports.
The system should maintain the elapsed time between status changes/checks and alert the dispatcher when agency-defi ned thresholds are met.
A:20 Standard Functional Specifi cations for Law Enforcement Computer Aided Dispatch (CAD) Systems Acronyms: CAD
ALI Automatic Location Identifier ANI Automatic Number Identification AVL Automatic Vehicle Location BOLO Be on the Lookout BJA Bureau of Justice Assistance CAD Computer Aided Dispatch CFS Calls for Service E911 Enhanced 9-1-1 EMS Emergency Medical Services EOC Emergency Operations Center FAX Facsimile GIS Geographic Information System Global JXDM Global Justice XML Data Model IACP International Association of Chiefs of Police ID Identification IJIS Integrated Justice Information System Institute LEITSC Law Enforcement Information Technology Standards Council MDC Mobile Data Computer MDT Mobile Data Terminal NIJ National Institute of Justice NOBLE National Organization of Black Law Enforcement Executives NCIC National Crime Information Center NSA National Sheriffs’ Association PERF Police Executive Research Forum RFP Request for Proposal RMS Records Management System SOP Standard Operating Procedures TDD/TTY Telecommunication device for the hearing- and speech-impaired XML Extensible Markup Language Bureau of Justice Assistance National Institute of Justice Office of Justice Programs U.S. Department of Justice NIJ The Research, Development, and Evaluation Agency of the U.S. Department of Justice
Standard Functional Specifications for Law Enforcement Computer Aided Dispatch (CAD) Systems
Developed by the
Law Enforcement Information Technology Standards Council (LEITSC)