Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Computer-aided dispatch
open-in-new
<h2 id="methodology">Methodology</h2> <p>Computer-assisted dispatch systems use one or more <a href="/facts/Server_(computing)/dEaYFD7r">servers</a> located in a central dispatch office, which communicate with computer terminals in a communications center or with mobile data terminals installed in vehicles. There are a multitude of CAD programs that suit different department needs, but the fundamentals of each system are the same. They include: </p><ul><li>Log on/off times of police personnel (sworn/non-sworn)</li> <li>Generating and archiving incidents that begin with a phone call from a citizen or originate from personnel in the field</li> <li>Assigning field personnel to incidents</li> <li>Updating Incidents and logging those updates</li> <li>Generating case numbers for incidents that require an investigation</li> <li>Timestamping every action taken by the dispatcher at the terminal</li></ul> <p>In an ideal setting, a call is received by a call-taker and information about the call is inputted into the CAD template. Simply, location, reporting party and incident are the main fields that have to be populated by type-codes. For example, if there was a burglary in progress, the type-code for that incident could be "BURG"; when BURG is typed out, then the program will spell out "BURGLARY (in progress)". If the location was at the 1400 block of Madison, the type-code could be "14MAD." The reporting party information would be populated by the call-taker including last name, first name, call-back number, etc. </p><p>A typical CAD printout looks something like this based on the example above: </p> ----------------------------------- LOCATION - 1400 Madison RP - Doe, John, 555-5555, 1404 Madison INCIDENT - BURGLARY (in progress) SYNOPSIS - "Caller reports a possible burglary in progress based on seeing individuals inside the residence/Caller advises 2 persons inside the location and call advises the current residents are on vacation." ----------------------------------- <p>Again, granted as it can be seen that the fields are spelled out, the call-taker uses those abbreviations that are already predetermined in order to quickly gather and transmit the information. </p><p>The dispatcher then receives the call from the call-taker and is able to dispatch the call to those available. The dispatcher's screen would show the available personnel that are dispatchable. A typical setting can be exemplified by this: </p> ----------------------------------- INCIDENT # - 110001 LOCATION - 1400 Madison RP - Doe, John, 555-5555 INCIDENT - BURGLARY (In Progress) SYNOPSIS - "Caller reports a possible burglary in progress based on seeing individuals inside the residence/Caller advises 2 persons inside the location and call advises the current residents are on vacation." UNITS - 746 (Pri), 749 (Cov) ----------------------------------- Units available - (3) Units out of service - (2) 745 - Avail. 746 - Not Avail. Inc # 554121 747 - Avail. 748 - Avail. 749 - Not Avail. Inc # 554122 ----------------------------------- <p>Everything that is gathered, dispatched and disposed is usually stored in a central server in which the type codes reside, or possibly another server. All of these calls which have incident numbers attached to them can be recalled by an internal search engine. For example, a request for a printout of all calls to Madison in the past hour could be gathered by querying the CAD program by location: </p> Search by: Location LOCATION [ ] --- Result: (Now filled in) Search by: Location LOCATION [14MAD ] --- Result: (1) Incidents <p>CAD can be used in a multitude of ways, whether it is for radio logs, call logs or statistical analysis. </p> <h2 id="consoles">Consoles</h2> <p>Typical of local government dispatching facilities, the Denver RTD's facility is one example of a transit dispatch center. Communications consoles are mounted in desk-style electronics racks. Features include multi-line telephones. Modern facilities usually include a variety of computing systems for operational and administrative purposes. </p><p>Consoles serve as a human interface and connect to push-to-talk dispatch radio systems. Audio from all channels is processed through <a href="/facts/Audio_level_compression/oVSzPxFY">audio level compression</a> circuits and is routed to two separate speakers identified as <i>select</i> and <i>unselect</i>. Each has a volume control. The select channel or channels carry the highest priority communications. To prevent missed messages on critical channels, the select volume may be configured so it cannot be set to an inaudible level. Unselect channels may be used for special events, other agencies, or purposes that do not involve dispatch and may be inaudible. By pressing a button, any channel on the console can be toggled between select and unselect status. Each channel has an independent push-to-talk button, allowing the dispatcher to talk over one channel at a time. For broadcast messages, a single button transmits over all selected channels at the same time. A digital clock and an <a href="/facts/LED/gE8x4MDb">LED</a> bar-graph or <a href="/facts/VU_meter/XfyxGXQM">VU meter</a> are included. </p><p>Each channel has a label identifying it and indicator lights and buttons to control settings. A typical channel has a busy light, a call light, select light, select button, and a transmit button. The steady, red busy light indicates another dispatch position is transmitting on the channel. The flashing yellow call light indicates a field unit is talking on the channel. The call light usually blinks for several seconds after a transmission ends allowing a busy dispatcher to look up from a telephone call and determine which channel the last message came from. </p><p>Some console dispatch panels are actually a PC-based application. Such is the case of Zetron's Acom system and Avtec's Scout system. This allows for easy customization and modification of the dispatch key layout. </p> <h2 id="service-levels-and-geographic-information">Service levels and geographic information</h2> <p><a href="/facts/Geographic_information_system/PoP1kVoa">Computerized mapping</a>, <a href="/facts/Automatic_vehicle_location/vdCICQ0b">automatic vehicle location</a>, <a href="/facts/Automatic_number_identification/wjkfAgqo">automatic number identification</a> and <a href="/facts/Caller_ID/hh9DqEEj">caller-identification technology</a> are often used to enhance the service by pinpointing the locations of both the client and the most suitable vehicle for serving the client. </p><p>Some CAD systems allow several sources of information to be combined. For example, adding automatic vehicle location (AVL) and geographic information (GIS) could improve service by getting units to a service call location faster. Ideally, CAD is connected to monitor vehicle locations provided by an AVL system. This information is used to suggest the closest vehicle to an event. How is the closest unit determined? </p> <h3>Basic zone system</h3> <p>The simplest system is a beat or zone map system. For example, in a community with four fire stations, a grid is overlaid on a community map. Each zone of the grid is identified with a progression of police beats, ambulance zones, transit zones, or fire stations.<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a> One grid might be labeled: AB241. This means fire station 2, then 4, then 1, then 3 would respond to a fire call occurring inside this zone. The predefined order is created by persons with expertise in the service being provided, local geography, traffic, and patterns in calls for service. </p><p>Since only basic GIS information is included, if AVL was available, it would simply display service vehicle locations on a map. The closest unit would be interpreted by the dispatcher looking at vehicle locations projected on the map. </p><p>Where detailed geographic data are not available, units may be assigned based on the center of a district. To make the computing problem easier, the CAD system may use <i><a href="/facts/Centroid/H6dDbg0h">centroids</a></i> to evaluate service vehicle locations. Centroids are estimated center points within a zone. The system calculates a distance from a fire station or AVL location to a centroid point. The closest fire station, according to CAD system rules, would be assigned. Systems may use centroids that are not exactly centered in order to skew or weight system decisions. Staff based at a fire station that is physically closer by drawing a straight line on the map may be slower to reach a zone. This can occur because responding units must drive around freeways, lakes, or terrain obstructions in order to reach a zone. A centroid may be moved because 200-car freight trains often block a railroad crossing used to access a particular zone. </p><p>This is the cheapest system to develop because it requires the least detailed geographic information and the simplest calculations. Another problem occurs where several services use the same system. Police and transit, for example, may have different ideas about what boundaries define the ideal zone or how centroids should be weighted. </p> <h3>CAD using geocoding</h3> <p><a href="/facts/Geocoding/KtTELe73">Geocoding</a> is a <a href="/facts/Translation/2foI82so">translation</a> system allowing addresses to be converted to X- and Y-coordinates. Someone placing a call for service has an address attached to a wired phone number or tells the dispatcher their address. For example, suppose the caller's address is <i>123 Main Street</i>. </p><p>The GIS or CAD system includes a look-up table. The table may identify odd-numbered addresses in the community as being on the north and east sides of streets. Addresses from 113 to 157 Main Street are identified as being along Main Street's center line between Broadway and Washington. 123 is estimated to be on the north side of Main Street somewhere closer to 113 than 157. This estimate produces a <a href="/facts/Latitude/IBYqkjhU">latitude</a> and <a href="/facts/Longitude/HsC61ML9">longitude</a>, or a set of <a href="/facts/Universal_Transverse_Mercator/uXdWEVV3">Universal Transverse Mercator</a> coordinates. The coordinates are close enough to identify the closest service vehicle. This system may automatically append the name of the nearest cross-street or intersecting street. </p><p>Again, the system uses a straight-line distance to determine which service vehicle is closest to a call for service. If an AVL system is used, the CAD system will look through a list of most recent reported vehicle positions. Next, the positions are compared to the service vehicle status. The CAD system may identify several of the closest units that have a status of <i>available</i>. The dispatcher makes an ideal choice from the CAD system shortlist. </p><p>This type of system is significantly more expensive than a zone system. The basic system may start with maps from the US Census Bureau or a county assessor's office. The quality of these maps may be good but will not be ideal for dispatching. There would normally be one or more persons on staff who would deal with data changes from new development, new streets, or data quality problems. The person would compile addresses and generate street centerlines in mapping software. Geocoding varies in accuracy depending on data sources and vendors. It normally takes years of work and planning before a system is implemented. Modern geocoded systems will often display service vehicle locations, the location of service calls, and the locations of callers on a map. This helps to disambiguate calls for service and reduces the likelihood of dispatching two reports of a single call for service as two separate calls. </p><p>Another problem comes from technologies using differing datums or coordinate systems. For example, suppose your AVL system uses degrees-decimal degrees format. The AVL display for a vehicle at the Heart Butte Post Office in Montana shows a latitude and longitude of 48.28333 N, -112.83583 W. The CAD system uses degrees-minutes-seconds format data and shows the same location as 481700N, 1125009W. How do you translate? This is sometimes a problem with neighboring CAD systems. Ideally, you should be able to send and receive calls to and from CAD systems in neighboring areas. What if the state or provincial government has standardized on a different coordinate system? </p> <h3>Full GIS/AVL integration</h3> <p>The most expensive and technically challenging systems fully utilize the capabilities of geographic information systems (GIS) and automatic vehicle location (AVL). In these systems, the street centerlines are described as <i>routable</i>. In addition to geocoding and accurate street centerlines, intersections have attributes or scores. Can a service vehicle turn left from eastbound Carnegie Street onto northbound Hooligan Boulevard? A scoring system is used to assess the difficulty of making the turn. At one end of the scoring system there might be an interchange where service vehicles had unrestricted access in making the turn. Perhaps both streets are one-way, making it relatively easy to turn from one onto another. In the middle scores, a left turn might be blocked occasionally by heavy traffic, a <a href="/facts/Draw_bridge/pfCQov2M">draw bridge</a>, or <a href="/facts/Street_cars/gSaKExyR">street cars</a>. At the most difficult score, the two streets may cross but the lack of any interchange does not allow service vehicles to get from one to the other. </p><p>To calculate the closest service vehicles, the CAD system does a network analysis of the road system based on these routable street centerlines. It assesses the path from the service call to the AVL location of available vehicles. The system recommends the service vehicles with the shortest path. </p><p>Routable street centerlines take into account differences between northbound and southbound lanes on a freeway or turnpike. For example, to reach a point in the southbound lanes of a turnpike, service vehicles may need to drive north to the next exit then return on the southbound side. The analysis of a routable street network takes this into account so long as the event location is accurately reported. Routable systems account for barriers like lakes by calculating the distance of the driven route rather than a straight-line distance. It is assumed the service vehicle driver knows the shortest path or that all drivers make similar numbers of wrong turns. </p> <h3>Concentration</h3> <p>CAD systems require support staff with special skills. This can lead to concentration of dispatch facilities, particularly where there is population growth or where automation is required to meet defined service objectives. </p><p>In any system, concentration of facilities increases risks of outages or massive failures. In a system where the call traffic is so high that advanced technology is needed to handle routine levels of day-to-day calls, relatively minor failures can have major effects on service levels. For example, where everyone is used to the convenience of automatic vehicle location (AVL), an AVL outage can suddenly increase staff workloads. Suppose a failure causes a condition where CAD cannot recommend a closest unit. How will the dispatcher efficiently assess which unit to assign? </p> <h2 id="data-exchange-edi">Data exchange (EDI)</h2> <p>In public safety systems, standards are under discussion to allow disparate systems to exchange call information. For example, a call taker at the county <a href="/facts/Fire_department/4N6R8YdV">fire department</a> receives a call for an auto accident inside a city limit. Evolving standards will allow CAD systems to send messages to one another for calls originating outside local jurisdiction. Some entities have arrangements that already support data exchange between systems, but standards aim to make these interconnections more common. Because of auditing trail and fail-safe needs, the problem is more complex than it sounds.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> </p><p>The usage of EDI applied to CAD is specific to the law enforcement community and should not be confused with Electronic Document Interchange (EDI) standards for eCommerce. Within law enforcement EDI is used as a buzzword to represent all electronic automated messaging. </p><p>More mature efforts to interconnect CAD can be found in the standards developed for the Intelligent Transportation Initiatives program of Department of Transportation.<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> This initiative sponsored the IEEE 1512 series of protocols for emergency management<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> which provides sophisticated means to coordinate incidents across operations centers using CAD software. </p><p>Additional work is occurring under the <a href="/facts/National_Information_Exchange_Model/SaIRWkhK">National Information Exchange Model</a><a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> to link homeland security with CAD. Also the <a href="/facts/OASIS_(organization)/a2r8y7tX">OASIS</a> international standards body has produced standards<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a> funded in part by the <a href="/facts/United_States_Department_of_Homeland_Security/jwz5gLfa">DHS</a> and the disaster management e-gov initiative<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a> to communicate in emergencies. </p><p>Other interoperability technologies can bridge disparities between the data-format, software, and hardware that constitute various computer-aided dispatch systems in various jurisdictions. <i>Middleware</i>, software and servers (data brokers), can translate and integrate various systems into a seamless automated dispatch system. One example of such middleware (provided by Utah-based FATPOT Technologies/CII)<a class="footnote-ref" id="fnref:8" href="#fn:8"><sup>8</sup></a> exists in Orange County, Calif., where the Fire Authority has integrated different emergency service answering points into a seamless dispatching network. A similar project was completed for the Silicon Valley Regional Interoperability Project (SVRIP), and is part of the Dept. of Homeland Security's CADIP report. </p><p><a href="/facts/Australia/qLHpbppq">Australia</a> and <a href="/facts/New_Zealand/4mpSlJdg">New Zealand</a> use the ICEMS protocol for messaging between different CAD systems operated by various emergency services organisations. </p> <h2 id="part-of-business-enterprise-computing-system">Part of business enterprise computing system</h2> <p>In business use of CAD, the dispatch system may be a module or part of a larger enterprise computing system. Rather than having multiple infrastructures, being able to have a single infrastructure with many applications running on it is important.<a class="footnote-ref" id="fnref:9" href="#fn:9"><sup>9</sup></a> </p><p>At the high end of enterprise integration for CAD there is SOS. SOS or <i>systems of systems</i> is a methodology and a set of technology for linking distributed independent applications into one meta-system or system of systems.<a class="footnote-ref" id="fnref:10" href="#fn:10"><sup>10</sup></a> These methods were originally being used at DOD for command and control (C2) but have now been applied to dispatch in efforts like the Department of Transportation <a href="/facts/Intelligent_transportation_system/3B6Wls8X">Intelligent Transportation System</a> at the Transportation Management Centers<a class="footnote-ref" id="fnref:11" href="#fn:11"><sup>11</sup></a> and other efforts involving DHS counterterrorism or fusion centers. Some local jurisdictions have also integrated their dispatch systems using EAI (Electronic Application Integration) software. </p> <h2 id="recent-developments">Recent developments</h2> <p><a href="/facts/Computer_aided_call_handling/4L3EePQ9">Computer aided call handling</a> (CACH) is built on the premise that effective call handling is the foundation for an efficient dispatch response. By using structured call handling and a series of risk calculations, such systems can make objective dispatch recommendations based on information provided by the caller. </p> <h2 id="see-also">See also</h2> <ul><li><a href="/facts/Emergency_medical_dispatcher/XhGxLLtY">Emergency medical dispatcher</a></li> <li><a href="/facts/EDXL_Sharp/2IXXlmAg">EDXL Sharp</a></li> <li><a href="/facts/Incident_Command_System/UBzgNhTL">Incident Command System</a></li> <li><a href="/facts/Logistics/0Hr2w55W">Logistics</a></li> <li><a href="/facts/Resource_Ordering_Status_System/wGDE20DT">Resource Ordering Status System</a></li> <li><a href="/facts/Selective_calling/ppypv7BY">Selective calling</a></li> <li><a href="/facts/Public_safety_answering_point/63tLdCY6">Public safety answering point</a></li></ul> <h3>Original article</h3> <ul><li>Horn, D. W., (2005). <i>An Integrated Public-Safety Computer-Aided Dispatch System.</i> In-press Master's Thesis Project, Regis University, Denver, CO.</li></ul> <h3>Notes</h3> <p>12.^ <a href="https://www.intrado.com/life-safety#">https://www.intrado.com/life-safety#</a> is an example of an Emergency Call Handling system that feeds CADs </p> <h2 id="external-links">External links</h2> <ul><li><a href="http://cad.chp.ca.gov/">California Highway Patrol Online CAD Logs.</a></li> <li><a href="https://humansystems.arc.nasa.gov/groups/midas/application/911midas.html">NASA research into future console designs.</a></li> <li><a href="http://www.kerkton.com/">Modern Private Security Dispatch System.</a></li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>This would work for any system including taxis or parcel pick up. <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>Associated Public-Safety Communications Officers web site, Data Transfer Committee, Focus Group III. Archived 2006-10-10 at the Wayback Machine The A.P.C.O. refers to this as Project 36. <a href="http://www.apcointl.org/about/datatransfer/index.html#Focus_Group_Three_DTC_FG3" target="_blank">http://www.apcointl.org/about/datatransfer/index.html#Focus_Group_Three_DTC_FG3</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>Intelligent Transportation Systems <a href="http://www.its.dot.gov/" target="_blank">http://www.its.dot.gov/</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>"IEEE Incident Management Working Group". Archived from the original on 2009-04-19. Retrieved 2009-02-28. <a href="https://web.archive.org/web/20090419201437/http://grouper.ieee.org/groups/scc32/imwg/index.html" target="_blank">https://web.archive.org/web/20090419201437/http://grouper.ieee.org/groups/scc32/imwg/index.html</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>NIEM.gov <a href="http://www.niem.gov" target="_blank">http://www.niem.gov</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>OASIS EM TC and EDXL Emergency Data Exchange Language <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=emergency" target="_blank">http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=emergency</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>"Egov.gov". Archived from the original on 2008-09-08. Retrieved 2019-07-08. <a href="https://web.archive.org/web/20080908004634/http://egov.gov./" target="_blank">https://web.archive.org/web/20080908004634/http://egov.gov./</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> <li id="fn:8"><p>"Fatpot.com". Archived from the original on 2018-07-10. Retrieved 2019-11-13. <a href="https://web.archive.org/web/20180710230842/https://www.fatpot.com/" target="_blank">https://web.archive.org/web/20180710230842/https://www.fatpot.com/</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></p></li> <li id="fn:9"><p>Multiple Applications with Same Infrastructure A Model for Applications, Sourced March 2007. <a href="http://www.retrievercommunications.com/index.php?option=com_content&task=view&id=59&Itemid=45" target="_blank">http://www.retrievercommunications.com/index.php?option=com_content&task=view&id=59&Itemid=45</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></p></li> <li id="fn:10"><p>System of systems System of Systems <a href="/wiki/System_of_systems" target="_blank">/wiki/System_of_systems</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></p></li> <li id="fn:11"><p>Ops.fhwa.dot.gov <a href="https://ops.fhwa.dot.gov/freewaymgmt/trans_mgmnt.htm" target="_blank">https://ops.fhwa.dot.gov/freewaymgmt/trans_mgmnt.htm</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></p></li> </ol>