cad dispatcher - cfpdweb · cad dispatcher training/user’s guide version 8.0 last revised...

www.newworldsystems.com

CAD DispatcherTraining/User’s Guide

Version 8.0

Last Revised 01/13/2011

http://www.newworldsystems.com

© 1992 - 2011 New World Systems Corporation

All rights reserved. Information within this document is the sole property of New World Systems Corporation and is protected by copyright and or trade secret regulations. Some product and company names mentioned herein may be the trademarks of their respective owners. Unauthorized copying or dissemination of this information without the written permission of New World Systems is strictly prohibited. Information within this document is subject to change without notice.

Copyright Registration Number TXu 996-689

Table of Contents

Chapter 1Dispatcher Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

About Dispatcher Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Extended Unit Status Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2House Watches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Building GEO/Location Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Note Pads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Work with Incidents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Work with Quick Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13CAD Hazard Inquiry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Jacket Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 2CAD Control Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

About the CAD Control Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 3Dispatch Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

The Dispatch Entry Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23The Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23The Incident Entry Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24The Call Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Executing CAD Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

GEO Verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Executing the AA2 (At Scene2, Available) Command . . . . . . . . . . . . . . . . . . . . . 29Executing the AAP (Unit Available at Scene) Command . . . . . . . . . . . . . . . . . . 30Executing the ADN (Add Narrative) Command . . . . . . . . . . . . . . . . . . . . . . . . . 31Executing the ADS and AEN (Assist) Commands . . . . . . . . . . . . . . . . . . . . . . . . 32Executing the ALI (Alarms Inquiry) Command. . . . . . . . . . . . . . . . . . . . . . . . . . 33Executing the ALP (Alarm Panel Inquiry) Command. . . . . . . . . . . . . . . . . . . . . 34Executing the ASG (Assign Unit to Incident) and STK (Stack) Commands . . . . 35Executing the ASP (Arrive Unit) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Executing the BET (Beat Recommendation) Command . . . . . . . . . . . . . . . . . . . 38Executing the BOL M (Be on Lookout Miscellaneous) Command . . . . . . . . . . . 39Executing the BOL O (Be on Lookout Outside Alert) Command . . . . . . . . . . . . 41Executing the BOL C (Be On Lookout Crimes) Command . . . . . . . . . . . . . . . . . 43Executing the BOL V (Be on Lookout, Vehicles) Command . . . . . . . . . . . . . . . . 46Executing the BOL W (Be on Lookout Wanted Persons) Command. . . . . . . . . . 48Executing the CAP (Clear a Unit from an Incident) Command . . . . . . . . . . . . . 50Executing the CCP (Clearing an Incident) Command . . . . . . . . . . . . . . . . . . . . 52

i

Executing the CDA (Change Dispatch Assignment) Command . . . . . . . . . . . . 53Executing the CHS (Change Current Station Assignment) Command . . . . . . . 54Executing the CHU (Change Unit Assignment) Command. . . . . . . . . . . . . . . . 55Executing the CID (Change Dispatchers ID#) . . . . . . . . . . . . . . . . . . . . . . . . . 56Executing the CIF (Clear Incident Flag) Command . . . . . . . . . . . . . . . . . . . . . 57Executing the CLA (Clear All Assigned) Command . . . . . . . . . . . . . . . . . . . . . 58Executing the CLP (Enter/Change License Plate) Command. . . . . . . . . . . . . . 59Executing the CMT (Change Monitor Type) Command . . . . . . . . . . . . . . . . . . 61Executing the CNA (Case Number Assignment) Command . . . . . . . . . . . . . . . 62Executing the CP1 and CP2 (Copy Incident) Commands . . . . . . . . . . . . . . . . . 63Executing the DSP (Dispatch) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Executing the DS1, DS2 (Depart Scene) and AS2 (Arrive Scene) Commands . 65Executing the ENR (Enrouting) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Executing the EQP (Equipment) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Executing the EVT (Event) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Executing the EXC and EX2 (Unit Exchange) Commands . . . . . . . . . . . . . . . . 74Executing the GEO (GEO Prompt) Command . . . . . . . . . . . . . . . . . . . . . . . . . 75Executing the HZD (Hazard) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Executing the HZI (Hazard Inquiry) Command . . . . . . . . . . . . . . . . . . . . . . . . 77Executing the INC (Incident Change) Command . . . . . . . . . . . . . . . . . . . . . . . 78Executing the INQ (Incident Inquiry) Command. . . . . . . . . . . . . . . . . . . . . . . . 79Executing the LNK (Link Incidents) Command . . . . . . . . . . . . . . . . . . . . . . . . . 80Executing the MLG (Mileage) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Executing Monitor Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Executing the MOV (Move) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Executing the MV2 (Move-up2) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Executing the NAM (Add Name to Narrative) Command . . . . . . . . . . . . . . . . . 86Executing the NAR (Narrative) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Executing the NOT (Note) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Executing the NRW (Narrative Window) Command . . . . . . . . . . . . . . . . . . . . . 89Executing the OFS (Off Shift) Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Executing the OND (On Duty) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Executing the ONS (On Shift) Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Executing the PAC (Assign Incident for PACE Operators) Command. . . . . . . 95Executing the PAG (Page) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Executing the PLT (Run License Plate Locally) Command . . . . . . . . . . . . . . . 97Executing the PRC (Print Rip and Run) Command. . . . . . . . . . . . . . . . . . . . . . 98Executing the QCE (Quick Call Entry) Command . . . . . . . . . . . . . . . . . . . . . . 99Executing the QCR (Quick Call to Regular Call) Command . . . . . . . . . . . . . 101Executing the QENT (Quick Entry) Command . . . . . . . . . . . . . . . . . . . . . . . . 102Executing the RCF (Rolodex Card File) Command . . . . . . . . . . . . . . . . . . . . 103Executing the RCE (Rapid Call Entry) Command . . . . . . . . . . . . . . . . . . . . . 105Executing the RCMD (Recommending Units) Command . . . . . . . . . . . . . . . . 106Executing the RES (Resend Dispatch Information to Mobile Units) Command 107Executing the RIP (Reprint Rip & Run) Command . . . . . . . . . . . . . . . . . . . . . 108Executing the ROT & AMB (Wrecker & Ambulance Rotation) Commands . . 109Executing the RRC (Reroute, Clear) Command . . . . . . . . . . . . . . . . . . . . . . . 110Executing the RRN (Reroute, No Clear) Command . . . . . . . . . . . . . . . . . . . . 111Executing the SHD (Call Scheduling) Command . . . . . . . . . . . . . . . . . . . . . . 112

ii

Executing the SHM (Scheduled Messages) Command . . . . . . . . . . . . . . . . . . 115Executing the SKL (Skills) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Executing the SND (Send Message) Command . . . . . . . . . . . . . . . . . . . . . . . . 119Executing the SRI (Special Response Information) Command . . . . . . . . . . . . 120Executing the TIM (Time in Minutes) Command. . . . . . . . . . . . . . . . . . . . . . . 122Executing the UAP (Unit Available) Command . . . . . . . . . . . . . . . . . . . . . . . 123Executing the UBP (Unit Out of Service) Command. . . . . . . . . . . . . . . . . . . . 124Executing the UCI (Unit Check In) Command . . . . . . . . . . . . . . . . . . . . . . . . 125Executing the UCP (Unit Check In) Command . . . . . . . . . . . . . . . . . . . . . . . . 126Executing the UOP (Unit Out of Service for Repair) Command. . . . . . . . . . . 127Executing the URA (Unit Reassignment) Command . . . . . . . . . . . . . . . . . . . . 128Executing the URI (Unit Radio Log Inquiry) Command . . . . . . . . . . . . . . . . . 129Executing the URP (Unit Report Writing) Command . . . . . . . . . . . . . . . . . . . 131Executing the USP (Secondary Location) Command . . . . . . . . . . . . . . . . . . . 132Executing the WCC (Caller / Complainant) Command. . . . . . . . . . . . . . . . . . 133

Appendix ACAD Commands and Function Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

CAD Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Function Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

iii

Chapter 1 Dispatcher Functions

About Dispatcher FunctionsThis manual encompasses the main tasks that a CAD dispatcher performs during the day-to-day operations of his/her job. Most of these options are accessed via the Dispatcher Menu.

From the Computer Aided Dispatch Main Menu, select Option 1, Dispatcher Menu.

The Dispatcher Menu will appear. The first option, Dispatch Entry, is covered extensively in Chapter 3. The remaining options are covered in this chapter.

1

Chapter 1: Dispatcher Functions

Extended Unit Status DisplayThe Unit Status Display window is used to display the current status of units that are in a “on shift” status. You can limit the units that display to a combined dispatch code or dispatcher assignment. From the Dispatcher Menu select Option 2, Extended Unit Status Display.

The Extended Unit Status Display window displays. The user’s home ORI# defaults. You may enter a specific Combined Dispatch Code to include all the units in these combined juris-dictions. Or you may limit the display to a specific Dispatcher Assignment. Leave these two fields blank and all the units from the selected ORI that are in an “on shift” status will display. Press <Enter>.

The Unit Status Display window will appear. See the bullet points below for information regarding this window.

2

Extended Unit Status Display

View 1.

• Press <F5> to update the information and get a current “snapshot” of the situation.

• Press <F7> to toggle between viewing only the units that are set to display in Unit Assignments Maintenance and all units (on the Unit Assignments Maintenance window, if the Monitor field is set to “N,” then the unit will not display when the Unit Status Display window is initially accessed).

• Press <F8> to toggle between viewing all “on shift” and “off shift” units from this jurisdiction (of if you are viewing a combined ORI, then from all the jurisdictions in the combined ORI).

• Type an “X” in the field to the left of a unit and press <Enter> to display the Unit Assignments Maintenance window.

• An asterisk displayed to the right of a unit indicates it is a MCT unit.

• Press <F9> to resequence by ID#.

• Press <F11> to toggle between three different views on this window.

View 2.

3

House Watches

House WatchesThe Work with House Watches program allows you to flag a specific address for a particular type of hazard. Hazards flag for a block range, so when a dispatcher dispatches for an incident that has occurred on the same block as a previously existing hazard, the dispatcher is made immediately aware of it. Examples of house watches that can be added are guns on premise, violent, diabetic, on vacation, officer’s house, judge's house, etc.

From the Dispatcher Menu select Option 3, Work with House Watches.

The Work with House Watches window will appear. Press <F6> to add a House Watch record.

5


A house watch that has a narrative attached to it will have an asterisk preceding the address. If the current date is greater than the Thru date on a house watch, then the From and Thru dates on a house watch record will display in red on the Work with House Watches window, indicating it has expired.

The House Watch Maintenance window displays. Enter the Address and Phone number of the house to be watched. Prompt the Venue and House Watch Type fields and select the appro-priate option from each respective table. Include a date range and enter Next of Kin and Emer-gency contact information. Since names are not validated, they can be entered free-form. Press <Enter>. The fields will clear enabling you to enter another house watch. Press <F12>.

The Work with House Watches window will reappear with your new record represented therein. The example below shows an incident that has an address on it that has an attached house watch. In the call queue area, the address displays in red. Since this incident is active, note that H/W appears in the Hazard Warning field (where this field is located on the screen of course depends on the design of the Dispatch Entry window).

6

Building GEO/Location Records

Building GEO/Location RecordsBuilding/GEO Location records are used to attach information about a specific building or GEO record to an address. When an incident is created for an address that has a building hazard attached to it, in the call queue portion of the Dispatch Entry window the address will appear in red. When the incident is active on the screen, BLD will appear indicating there is a building hazard attached to the address. This information is then accessible through the hazard com-mands (HZD and HZI). Hazards are typically used by fire departments.

From the Dispatcher Menu, select Option 4, Work with Building / GEO Location.

The Work with Building / GEO Location window will appear. Press <F6>.

7


The Building / GEO Location Maintenance window displays. This window is divided into three field groupings. The Address, Venue, and Building Type fields are mandatory. The next grouping, starting with Business Info, can be used to record building and contact information. These are free form fields that can be re-labeled and rearranged by the system administrator. All of the fields in the last field grouping are user-defined. Additional user-defined fields can be displayed by pressing the <F22> key.

Enter as much information as is necessary and press <Enter>. The fields will be cleared allow-ing you to enter another record should you so desire. When you have finished entering Building / GEO Location records, press <F12>.

The names of the fields on the Building / GEO Location Maintenance window are setup via option 9 on the System Administrator Menu. See the Computer Aided Dispatch System Administrator Guide for more details.

8

Building GEO/Location Records

The Work with Building / GEO Location window will reappear with your new record repre-sented therein. The example below shows an incident that has an address on it that has building information attached to it. In the call queue area, the address displays in red. Since this incident is active, note that BLD appears in the Hazard Warning field (where this field is located on the screen of course depends on the design of the Dispatch Entry window).

9


Note PadsNote Pads in Aegis are used the same as a physical note pad: to document something. Free-form documents can be added to a notepad record making the amount of information available almost limitless.

From the Dispatcher Menu, select Option 5, Work with Note Pads.

The Work with Note Pads window displays. Press <F6>.

10

Note Pads

The Note Pad Maintenance window will appear. In the Description field, type a brief descrip-tion of the note. Prompt the Note Pad Type field and select a type for your note. The Note Pad Date and Note Pad Time fields default to the current date and time. The Created By field defaults to the user name with which you logged on to the system. If desired, documents can be attached via <F24 >. Make your entries and press <Enter> to save your record.

11


Work with IncidentsFrom the Dispatcher Menu, select Option 6, Work with Incidents.

The Work with Incidents window displays. Incidents are covered in-depth in the Law Enforce-ment Records Volume I Training / User’s Guide. Please refer to that manual for instructions regarding how to use incidents.

12

Work with Quick Calls

Work with Quick CallsFrom the Dispatcher Menu, select Option 7, Work with Quick Calls.

The Work with Quick Calls window displays. The options on this window and their function-ality are identical to the Work with Incidents window. For details, please refer to the Law Enforcement Records Volume I Training / User’s Guide.

13


CAD Hazard InquiryThis option enables a user to perform a hazard inquiry directly from this menu without access-ing the CAD Dispatch window. This option basically performs the HZI command without having to be in the Dispatch Entry window.

From the CAD Dispatcher Menu select Option 8, CAD Hazard Inquiry.

This window can also be accessed directly from a dynamic menu by executing: Call CD1805.

The CAD Hazard Inquiry window will appear. The user’s home ORI # defaults. You may per-form a search by location, cross street, venue, name, license plate #, and/or driver’s license #. Make your entry and press <Enter>.

14

CAD Hazard Inquiry

The Work with Hazard Warnings Inquiry window will appear. The hazards that appear in this window are based on what is set-up in the GEO Master File. In the example below, two hazards appear that are at different addresses. That is because the addresses of the hazards fall within the address range set-up in the GEO Master file.

15


Jacket Records The need to view but not change jacket records may arise. The instructions that follow demon-strate how to view a jacket without changing it.

From the Computer Aided Dispatch Main Menu, select Option 9, Police/Sheriff Inquiry Menu.

The Inquiry Menu displays. Select Option 20, Global Name Inquiry.

16

Jacket Records

The Resequence window displays. Jackets can be selected by a variety of criteria from last name to sex to social security number and so on. For our purpose here, enter a last name in the Name field and press <Enter>.

The Global Name Inquiry window will appear with the selected individual (or the individual most resembling the name entered in the previous step) at the top of the list of jacket records. Look to the Jckt#/ORI column for the subject’s jacket # or the ORI # under which his jacket record was initially created. Jackets created in your ORI appear in green lettering and display the jacket number, while those created in other ORIs appear in white and show the ORI #.

17


18

Chapter 2 CAD Control Window

About the CAD Control WindowAll calls and dispatching operations are processed and performed at the Dispatch Entry window. To access “Dispatch,” however, you must first set up the CAD Control window. The CAD Con-trol window allows you to do the following:

• Define which calls will appear in the Dispatch Call Queue;

• Specify which terminals will be used as monitors; and

• Determine various other Dispatch Entry operating characteristics.

To access the CAD Control window, select Option 1, Dispatch Entry, from the Dispatcher Menu.

19

Chapter 2: CAD Control Window

The CAD Control window will appear. In this window, the ORI #, Shift, ID #, and Call Queue Type fields are mandatory. See below for a detailed description of the data fields within this window. After you have made all of the necessary entries, press <Enter>. If you made an invalid entry, the field in which the invalid entry was made will “reverse highlight.” Correct the mistake and press <Enter> again.

Description of Data Fields within theCAD Control window

(Data fields preceded by an asterisk are mandatory)

*ORI# Use this field to indicate the ORI # for which you are dispatching.

Combined Dispatch Code

If you are dispatching in a multi-jurisdictional environment, type the combined dispatch code here. Combined dispatch codes represent groups of ORI #s that are set up and compiled via the Work with Sub ORIs program in CAD Jurisdiction Control. If you utilize a combined dispatch code, the calls displayed in your call queue will include all incidents that occur within the ORIs represented by the specified combined dispatch code.

Dispatcher Assignment

Use this field to specify a dispatcher assignment code. This code, set up in Work with Sub Beats and accessible in the CAD Jurisdiction Control, can represent any number of different beats. It tells CAD to display in your call queue calls that occur in a beat that is contained in the specified Dispatcher Assignment. Typically, this field is used by dispatchers in large agencies that need to limit the calls in the call queue to those pertaining to only a portion of a single jurisdiction. You cannot use both a Combined Dispatch Code and a Dispatcher Assignment; you can use only one or the other.

*Shift Use this field to indicate your shift code. This information is required for reports run by shift assignment. Prompt this field to choose from a list of valid entries.

*ID # Enter your dispatcher's ID # here.

Monitor/Device/Type/Code/DspAsn (see below for a description of Monitor Types)

20

About the CAD Control Window

Status #1 Enter here the name of the device to be used as a status monitor. The device name can be found in the upper right-hand corner of the AS/400 sign-on screen.

Type (Device) Enter here the type of device entered in the Status #1 or #2 (Device) field.

CodeIf you are dispatching in a multi-jurisdictional environment, enter the combined jurisdiction code here. If you are using this field, you cannot use the Dispatch Assignment field.

DspAsn Use this field to indicate a dispatch assignment if appropriate. If you are using this field, you cannot use the Code field.

Status #2, Status #3, and Status #4 Use these fields to start up to four status monitors.

Message Use this field to indicate the name of the device that will be used as a message monitor.

TDD This field will not appear if your agency does not use TDD (a hearing-impaired device).

*Cal Queue Type

This field dictates what kind of information displays on the Dispatch Entry window.

Option 1: The call queue will show only those calls which are pending for dispatch. This displays the same information that a user would see looking at the pending call queue monitor.

Option 2: The call queue will show all of the calls regardless of if they are pending or not.

Option 3: The call queue will show only those calls that are non-pending for dispatch. (Non-pending calls are incidents that currently have units attached to them.)

E911 Phone Position

To display E911 information at a single phone position, enter the position # here. If you would like to display all calls to the PSAP, leave this field blank.

Map Data Queue

This field is used only if the Mapping Module is used. The queue number is created and setup in the Work with Mapping Data Queues window, option 3 from the Mapping Main Menu. If a CAD Mapping data queue is in use, a message will appear stating which user ID and station is using it. This will eliminate the guesswork involved in figuring out who needs to be logged in/out correctly. The message “Map Data Queue in use by User at Workstation” will appear with “User” being the user signed on and “Workstation” being the terminal they are signed on to.

ProQA Data QueueThis field is used only if ProQA is used. Enter the number that was assigned to your PC when you were setting up the NWS ProQA Interface Maintenance window.



21

Chapter 2: CAD Control Window

When all data has been correctly entered, the Dispatch Entry window will appear.

ProQA Dispatch Type

Enter here whether the ProQA Dispatch Type is “H” for Horizontal or “V” for Vertical. Vertical should be selected if the same person is performing the functions of “Call Taker” and “Dispatcher.” In Vertical mode, the ProQA session returns to the Dispatch window immediately after the operator presses the “Send” button in order to dispatch units. Horizontal should be selected if the “Call Taker” and “Dispatcher” functions are performed by separate persons. In this mode, ProQA remains active after the “Send” button is pressed. This allows the Q/A process to be continued while the dispatcher handles dispatching units.



22

CommLin

IncidEntry A

Call Queue

Chapter 3 Dispatch Commands

The Dispatch Entry ScreenSince the Dispatch Entry screen can be customized to suit the needs of individual agencies, your Dispatch Entry screen may look slightly different than the one shown below. The elements shown in this example, however, are common to all Dispatch Entry screens.

One such commonality is its division into three main sections: The Command Line, the Incident Entry Area, and the Call Queue.

The Command Line The command line, of course, is the line on which you type the CAD command that you wish to execute. When entering a command you must indicate the incident # and, when applicable, the unit # for which the command is being executed. For example, to execute a command for a specific incident # you would use the following format:

Command_Incident#

If a unit # is involved:

Command_Unit#_Incident#

When entering a command, you must use a single space to separate each command element. The underbar separating the elements in the examples above represent one space.

Most default CAD commands are composed of three letters. DSP, for example, is used as the default “Dispatch” or “Assign a unit to a call” command and CAP for the “Clear a unit from an incident” command. For the sake of convenience, however, New World Systems software allows you to create alias commands, which can be abbreviated versions of the default com-mands. For example, you can make D your DSP command and C your CAP command.

and e

ent rea

23

Chapter 3: Dispatch Commands

The Incident Entry AreaThe incident entry area is the area in which you enter the information garnered from a call. See the table below for a description of the fields within this window.

Description of Data Fields within theIncident Entry Area of the Dispatch Entry window

CAD Command Line

This is where you type the CAD commands and their associated parameters. All CAD commands are executed from the CAD Command Line.

*Incident Type

Enter here the type of incident that has occurred or is occurring. The single-character field to the right of the Incident Type field is used to indicate the type of files the system should prompt. “P” indicates a Police incident, “F” a Fire incident, “E” an EMS incident, and “C” a Combined incident. Every agency can design this field to suit its individual needs.

*Status Use this field to indicate with a “Y” or “N” response whether or not the incident is currently in progress.

PrtyThe priority is defaulted by the incident type. This default information is set up in System Tuning. You may change the priority by simply typing over the defaulted priority.

PhoneEnter here the caller’s telephone number. The field accepts up to ten numeric characters; Alpha characters may NOT be used. A hyphen may be used when only seven digits are entered.

Location Use this field to enter the location of the incident. For information on how to enter address information, see the NWS Basics manual.

VenueThis field is used to indicate the venue in which the incident has occurred or is occurring. The information is pulled from the GEO Location index for streets and addresses. This field references Table #9.

Cross Street

This field is used to indicate the cross street at which the incident has occurred and is typically for accident information. If a cross street is used, the location type must be “X.” When making your entry, use the following format: DIRECTION, STREET NAME, SUFFIX (see the NWS Basics manual for more information about entering addresses). Your entry will then be verified against the GEO File cross streets reference. If both intersecting streets are entered in the Location field, this line should be left blank.

*Loctn Typ

Use this field to specify the location type for the information entered in the Location and Cross Street fields. Valid entries are “S” for Street Address, “C” for Common Name (e.g., McDonald's), “X” for Cross Street (e.g., 1st / Main), and “O” for Override (which allows you to by-pass the address validation process).

Nature of Call

Use this field to record a brief description of the incident and/or any miscellaneous information that you would like to document. This information is recorded in the incident record and is accessible within the Incident Maintenance program when the call is cleared.

24

The Incident Entry Area

*Call SorcIndicate here the way in which the call information was received, e.g., telephone, E911, alarm panel, walk-in, etc. Prompt this field to select from a table of valid entries. This field references Table #0081.

Caller’s Name Use this field to indicate the caller's name. Names must be entered in Standard Name Format: LAST NAME, FIRST NAME, MIDDLE INITIAL.

Asgn Beat This field indicates the dispatcher's beat assignment. The code is defaulted but may be changed. Prompt the field for a list of valid entries.

Complainant Should the complainant be someone other than the Caller, use this field to indicate his/her name.

Addtnl Info Use this line to enter any additional information relevant to the call. Once the call is cleared, information entered in this field will appear in the incident narrative.

Primary/Second

These fields are used to indicate the first and second units assigned to the call. The Single Character field to the right will accept an “A” or a “C.” “A” will dispatch and arrive a unit to the call; “C” will dispatch and arrive units and then clear the call.

Rprt This field indicates whether or not a report is to be created for the call. It defaults to “Y” but may be changed to “N.”

Wrck Dist This field indicates the Wrecker and Ambulance District rotation selection. Information within it is defaulted from the GEO file.

Responding ORIThe GEO file and the Incident Type (P/F/E) determine the ORI of the responding agency. The ORI can be set up to default in this field and may also be modified should you need to change it.

*A/S/B/Q/DFrom the GEO file, each location should have an AREA, BEAT & SECTION, QUADRANT, District. In case of an over-ride, each is a promptable field. (Tables 0003, 0071, 0063, 0064).

Cross Streets Cross Streets are displayed to a particular address.

RID Received ID. This is an informational field that indicates the ID of the operator who received the call.

DID Dispatcher ID. This is an informational field that indicates the ID of the operator who dispatched the call.

SendThis field indicates the recommended number of units that should be sent to the incident. The recommendation is based on the incident type and may be overridden.

Sent After a call is dispatched, this field will indicate the number of units sent to the call (0 to 9).


25


The Call QueueThe call queue is used to keep track of all dispatched calls and all calls waiting to be dispatched. This is a color-driven area with the following properties:

Address

• LIGHT BLUE address field has a correct GEO validated address.

• YELLOW address field has not yet been GEO validated.

• RED address field has a HAZARD attached to it.

• WHITE is a quick call or traffic stop.

Incident Type

• RED incident type indicates special response information is attached. See page 120 for instructions on how to execute the SRI command to view the information.

• LIGHT BLUE normal incident type, no additional information.

The CAD screen can be modified to display three different views of the call queue. If your call queue has been modified in this way, use the <F6> key to toggle between the different views.

Executing CAD CommandsCAD commands are the codes you use (typed on the Dispatch Entry Command Line) to execute specific actions within the CAD system. Below you will find a description of how to utilize the most commonly used commands. For a complete list of commands, see Appendix A: CAD Commands and Function Keys.

When you are in the Dispatch Entry window, if you are unsure of the syntax of a CAD com-mand, on the CAD command line simply type a question mark, a space, and the command in question. For example, ? DSP. This will display the syntax of the command on the command line.

In examples in this book, UUUUUU represents the unit that is involved in the command and iiiiii represents the incident number.

License Plate & License State These fields are input fields. The CLP command also populates these fields.


26

GEO Verification

Step-by-Step: GEO VerificationThe GEO file is simply a reference for the system to locate streets, cross streets, blocks, addresses, and common names. If you enter an address that is not defined in the GEO file, the CAD program will take you through the verification process to ensure that the correct informa-tion (Area, Section, Beat, Quadrant, etc.) gets entered. To see how this works, do the following:

1. At the Dispatch Entry screen, enter an Incident Type, an address that is NOT part of the GEO file (a new street name, an existing street name misspelled, etc.). The GEO validation process looks for a matching Address Range, Directional (N, S, E, W), Location Type (S = Street; C = Common Name; X = Cross Streets; and O = Override), and Venue. If the address entered is not an exact match to a GEO address, the system will perform GEO validation. Press <Enter>.

2. The GEO Prompt window will appear. Here you can perform one of the options listed below.

Option 1 = Select. Use this option to select the address record that should be associated with your incident. The address as you typed it at the Dispatch Entry screen will appear in the Street, Cross Street, and/or Venue fields at the top of the GEO Prompt window. The record in the GEO database that most resembles the address will appear at the top of the list of address records. If that record is the address you intended to enter, select it by typing a “1” in the Option field associated with it and pressing <Enter>. If it is not the intended address, use the <Scroll Up> and/or <Scroll Down> keys to locate the correct address.

Option 2 = Override All. Use this option to override the address range but retain the remaining location information. If you select this option, an “O” for Override appears in the Location Type field. This is typically used when the wrong range of numbers is displayed for a street, however the street is correct.

Option 3 = Override A/S/B/Q/D. This option will leave in place the street address or cross street information that you entered and input the Area, Section, Beat, Quadrant, and EMS District associated with the record you select from the GEO Prompt window. This option is extremely useful when dealing with new streets.

Option 5 = Display. Use this option to display the entire GEO record as it was originally entered into the system.

For our purposes here, select Option 3.

27


3. The Dispatch Entry window will appear with the address you entered and the Venue and A/S/B/Q/D information from the record selected from the GEO prompt window.

28

Executing the AA2 (At Scene2, Available) Command

Step-by-Step: Executing the AA2 (At Scene2, Available) Command

This command changes the status of a unit to “At Scene 2, Available,” indicating that the unit is available for other calls. You can change the status of any number of units with this command.

1. The unit must first be departed from scene 1. This can be done by using, for example, the DS1 or DS2 command.

2. On the command line at the Dispatch Entry window, type “AA2 uuuuuu” where “uuuuuu” represents the unit # you would like to make “available” and press <Enter>.

3. The unit will now be listed as available on the unit monitors.

29


Step-by-Step: Executing the AAP (Unit Available at Scene) Command

This command changes the status of a unit that is still at the scene of an incident from non-rec-ommendable to recommendable. Units must be in ASP status for the AAP status to work. The unit will appear in a lighter blue color in both the call queue and Unit Status Monitor. Monitor Style # 4 displays the AAP condition and all other “Recommendable” conditions in the center column.

1. On the command line at the Dispatch Entry window, type “AAP uuuuuu” where “uuuuuu” represents the unit # you would like to make “recommendable” and press <Enter>.

Like the DSP and other commands, the AAP command can be executed for multiple units at a time by typing all of the units, one after another, separated by a comma. For example: AAP 2A10,2A20,2A30.

2. The unit’s status will be changed. No further action is required.

30

Executing the ADN (Add Narrative) Command

Step-by-Step: Executing the ADN (Add Narrative) CommandIt is often necessary to add narrative to an incident after it has been logged. The ADN command allows you to do this from the command line.

1. On the command line at the Dispatch Entry screen, type “ADN iiiixx narrative” where iiiixx represents the incident # to which you would like to add narrative and narrative is the actual free-form text. Narrative may be up to 40 characters in length. When you have finished typing your command, press <Enter>.

You may perform this command for a chain of incidents provided the narrative applies to all of them. Use the following format: ADN 0154AP,0155AP,0161AP NARRATIVE.

2. The narrative is now added to the incident and can be viewed via the NRW page 89 command.

31


Step-by-Step: Executing the ADS and AEN (Assist) CommandsThe ADS and AEN commands are used to dispatch or en route units to another call. These com-mands will not clear the original call that a unit is on.

ADS: Assist DispatchAEN: Assist En route

If on a call, the current incident that a unit is on will automatically be placed at the top of a unit’s call stack. Any unit statuses other than Off Shift or Out of Service Repair are valid statuses that the unit can be in when the command is executed. This enables a dispatcher to send units to assist another unit regardless of their status.

The format of the commands is:

ADS uuuuu1,uuuuu2,… uuuuu3 (secondary location)AEN uuuuu1,uuuuu2,… uuuuu3 (secondary location)

In the examples above, unit 1 (uuu1) and unit 2 (uuu2) are assisting unit 3 (uuu3). The unit receiving assistance, in this case Unit 3, must already be active on a call or an error message will be generated. The secondary location information is optional. If no secondary location information is entered, the secondary location of all sent units will be blanked out.

1. On the command line type “ADS” or “AEN” followed by the units you would like to send to assist another unit, separated by commas. The unit they are being sent to assist should be separated from them by a space. You may enter secondary information if desired. Press <Enter>.

The secondary location will be written to narrative if the Unit Secondary Location field in CAD System Tuning window CD0970S2 is set to Yes.

2. The units will be assigned to the new incident and will be in a stacked status for the previous incident.

32

Executing the ALI (Alarms Inquiry) Command

Step-by-Step: Executing the ALI (Alarms Inquiry) CommandThis command displays the Alarm Permit Inquiry window.

1. On the command line at the Dispatch Entry screen, type “ALI” and press <Enter>.

2. The Alarm Permit Inquiry window will appear. From this window you can resequence by permit number, type, or status. You may make an entry or simply press <Enter> to display all permits in the default order.

3. The Work with Alarm Permits window will appear. Information associated with the alarms can be viewed.

33


Step-by-Step: Executing the ALP (Alarm Panel Inquiry) Command

When an alarm panel is activated, you can use the ALP command to display business informa-tion, which will then be defaulted to the CAD work screen. The alarm must have the “In Ser-vice” field in the Alarm Permit Maintenance window set to Yes, otherwise the message “Permit not in Service” will appear when the command is executed.

1. On the command line at the Dispatch Entry screen, type “ALP panel” where “panel” represents the panel # and press <Enter>.

When using this command, the panel number must be entered exactly as it was on the Alarm Permit. If entered as “2,” enter “ALP 2.” If entered as “002,” enter “ALP 002.”

2. The alarm information including the address will display in the Dispatch Entry window.

34

Executing the ASG (Assign Unit to Incident) and STK (Stack) Commands

Step-by-Step: Executing the ASG (Assign Unit to Incident) and STK (Stack) Commands

CAD users who have our Mobile Interface to Mobile Data Terminals (MDTs) or Mobile Com-puter Terminal (MCTs) use the ASG (Assign Unit) command to transfer a CAD incident to a unit or group of units.

1. On the command line at the Dispatch Entry screen, type “ASG uuuuuu iiiixx” where “uuuuuu” represents the unit # and “iiiixx” the incident #. Press <Enter>.

2. In the call queue, the unit will appear in amber lettering as dispatched to the incident. On the status monitor, the unit and the incident will appear in amber.

With the “Call Stacking” feature, the operator has the ability to “stack” a number of calls for a unit to handle during the course of his/her shift. Once an incident is cleared, the “Auto Dispatch Stack” feature (set-up in CAD System Tuning) tells the system to automatically execute the DSP & ENR command for the next incident, the incident at the top of a unit’s stack.

3. To stack a call, use the ASG command with the unit # and incident # to put a call in a unit’s stack.

When the Auto Dispatch to Stacked Call field in System Tuning is set to Yes, the first inci-dent assigned to a unit is immediately dispatched and placed in an enroute status unless the unit is not in the “Available” status.

4. Stacked calls appear in the call queue with the unit reverse highlighted in green characters. Stacked calls do NOT appear on the Status Monitor.

35


5. A unit can be assigned to a Quick or Rapid call while already assigned to an incident. When this occurs, the incident to which it was initially attached will be automatically stacked. If the Auto Dispatch Unit to Stacked field in CAD System Tuning is set to “Yes,” the unit will return to the original call as soon as the Quick or Rapid call is cleared. If the Auto Dispatch Unit to Stacked field is set to “No,” the call will remain stacked until an operator reassigns it.

6. Incidents must be added to a stack one at a time. However, a string of units may be stacked to the same incident using the following format: ASG uuuu01,uuuu02,uuuu03 iiiixx. In the call queue, stacked calls appear with the unit in green reversed highlight. Stacked calls do NOT appear on the status monitor.

7. To view or work with a unit’s stacked calls, type “STK uuuuuu” where “uuuuuu” represents the unit # and press <Enter>.

8. The Work with Stacked Calls screen displays with a list of all calls stacked for the designated unit. Here you can perform the following options:

• The “R=Remove from Stack” option removes the selected call from this unit’s stack and places it in the call queue in active status.

• The “T=Move to Top” option moves the selected call to the top of the stack. This feature is only available when the “Auto Dispatch Unit to Stacked” field in CAD System Tuning is set to “Y.”

• The “A=Arrive” option allows you to “arrive” the selected unit to any incident within its stack.

• The “H=On/Off Hold” option toggles a call on or off hold. When used with the “Auto Dispatch Unit to Stacked” field, an incident placed on hold will be skipped over until the hold is removed.

36

Executing the ASP (Arrive Unit) Command

Step-by-Step: Executing the ASP (Arrive Unit) CommandUse this command to show a unit as having arrived at the scene of an incident.

1. On the command line at the Dispatcher Entry screen, type “ASP uuuuxx” where “uuuuxx” represents the unit you wish to indicate as having arrived at an incident and press <Enter>.

Like the DSP and some other commands, the ASP command can be executed for multiple units at a time by typing all of the units, one after another, separated by a comma. For example: ASP 2A10,2A20,2A30.

A unit need NOT be dispatched or enrouted before it is arrived at a scene using the ASP command.

2. The unit will then appear in the call queue and status monitor in blue lettering.

37


Step-by-Step: Executing the BET (Beat Recommendation) Command

If your agency is utilizing the New World Systems Police Unit Recommendations feature, the system will display a logical sequence of units that should be dispatched to an incident based on various factors including available units, unit types, beat and beat back-up.

1. On the command line at the Dispatch Entry screen, type “BET iiiixx” where “iiiixx” represents the incident # for which you would like the recommendation and press <Enter>.

You can achieve the same effect using the INC command. At the command line, type INC followed by the incident # and press <Enter>. The incident will appear. Press <F10>. The Police Recommendations window will appear. Go to Step 2.

2. The Police Recommendations window will appear. Information such as the beat, incident # and # of units recommended (based on incident type) appears at the top of the screen. Below this information you will find a list of “recommendable” units. To select one, type a “D” in the Opt field associated with the unit you would like to select and press <Enter>. You can select as many units as you wish in this manner. The selected unit or units will then be dispatched to the incident.

38

Executing the BOL M (Be on Lookout Miscellaneous) Command

Step-by-Step: Executing the BOL M (Be on Lookout Miscellaneous) Command

The BOL M (be on the lookout, miscellaneous items) command can be used to input informa-tion that will be sent to MCT units and/or CAD users.

Entering the command “BOL ?” access table 3513. This table is used to select the type of BOL command you would like to use, C=Personal/Property Crimes, M=Miscellaneous, O=Outside Alerts, V=Vehicles, and W=Wanted/Missing Persons. The entries in this table should not be changed.

1. On the command line at the Dispatch Entry window, type “BOL M” and press <Enter>.

2. The Work with Briefing Notes window will appear. Press <F6>.

3. The Briefing Notes Maintenance window displays. See below for a description of the data fields in this window. Make your entries and press <Enter>.

39


4. The Free Form Document window displays. This window is used to clarify the description on the previous window. Make your entries and press <Enter>.

5. The Work with Briefing Notes window will reappear with the new item represented therein. Press <F3> to return to the Dispatch Entry window.

Description of Data Fields within theBriefing Notes Maintenance window

Item # This field is auto-incremented to the next available number. These numbers cannot be changed. Numbers can and are reused.

Start Date & Time Use these fields to indicate the date and time that the message is to begin appearing. Defaults to current.

Created by This field defaults to the user who is inputting the item and cannot be changed.

Desc Use this field to enter a description of the item.

PIN#A valid PIN# must be entered in this field. Each user must have a PIN# added in Work with User PIN#s, Option 4 from the Briefing Summary Administrator Menu (BS0004S1).

Priority This is an informational field.

Appear for day(s) Enter the number of days that this item should appear. This field is informational; items must be manually deleted at the appropriate time.

Send to CAD Messaging Set this field to “Y” if the message is to be sent to CAD messaging units.

Send to all MCT Units Set this field to “Y” if the message is to be sent to MCT units.

40

Executing the BOL O (Be on Lookout Outside Alert) Command

Step-by-Step: Executing the BOL O (Be on Lookout Outside Alert) Command

The BOL O (be on the lookout, outside alerts) command can be used to input information that will be sent to MCT units and/or CAD users.


1. On the command line at the Dispatch Entry window, type “BOL O” and press <Enter>.

2. The Work with Outside Alerts window displays. Press <F6>.

3. The Outside Alerts Maintenance window will appear. See below for a description of the data fields. Make the necessary entries. To add additional narrative to this alert record, press <F24>.

41


4. The Free Form Document window will appear. Enter a more detailed description of the alert. Press <Enter> to save your work.

5. The Work with Outside Alerts window will reappear with the new alert listed. Alerts are listed by message number.

Description of Data Fields within theOutside Alerts Maintenance window


Authority Use this field to enter the name of the person who is authorizing this alert. This is a free form text field and is not validated.

*Offense/Desc Use this free form text field to enter a description of the offense or event that is or has taken place.

Appear for Use this field to enter the number of days that this alert should appear. This field is not validated and is used for reference only.

*Send to CAD Scheduled Messages

Use this field to indicate if this event is to be included in the scheduled CAD messages.

Send message to all MCT Units Use this field to indicate if this event is to be sent to all MCT units.

42

Executing the BOL C (Be On Lookout Crimes) Command

Step-by-Step: Executing the BOL C (Be On Lookout Crimes) Command

The BOL C (be on the lookout, crimes against persons or property) command can be used to input information that will be sent to MCT units and/or CAD users.


1. On the command line at the Dispatch Entry window, type “BOL C” and press <Enter>.

2. The Work with Personal/Property Crimes window displays. Press <F6>.

43


3. The Person/Property Crimes Maintenance window will appear. See below for a description of the data fields. Press <F6> to add a suspect.

Description of Data Fields within thePerson/Property Crimes Maintenance window


*ORI # The user’s home ORI # defaults in this field.

Ref#/Type Use these fields to link the event to a case or incident.

*Reported Date Use this field to indicate the date the event was reported.

*Offense Use this free form text field to enter a description of the event that occurred.

*Type of Crime Use this field to indicate if the event involved a person or property.

From Date/Time Use these fields to enter the earliest possible date and time that this event could have taken place.

Thru Date/Time Use these fields to enter the latest possible date and time that this event could have taken place.

Address/Sector Use these fields to indicate the location the event took place.

Place Name Use these fields to indicate, if applicable, the name of the location.

Remarks Use this field to give a description of the event that took place.

*Send to CAD Scheduled Messages

Use this field to indicate if this event is to be included in the scheduled CAD messages.

Send message to all MCT Units Use this field to indicate if this event is to be sent to all MCT units.

44

Executing the BOL C (Be On Lookout Crimes) Command

4. The Suspect Maintenance window will appear. Make your entries and press <Enter>.

5. The Person/Property Crimes Maintenance window will reappear with the suspect listed. Press <Enter> to save your event.

45


Step-by-Step: Executing the BOL V (Be on Lookout, Vehicles) Command

The BOL V (be on the lookout, vehicles) command can be used to input information that will be sent to MCT units and/or CAD users.


1. On the command line at the Dispatch Entry window, type “BOL V” and press <Enter>.

2. The Work with Vehicles window displays. Press <F6>.

46

Executing the BOL V (Be on Lookout, Vehicles) Command

3. The Vehicle Maintenance window will appear. The Plate/ST, Plt Type, and V Type fields are mandatory. Make your entries and press <Enter>.

To access the Global Vehicle window, press <F11>.

4. The Work with Vehicles window will reappear with the new entry listed.

47


Step-by-Step: Executing the BOL W (Be on Lookout Wanted Persons) Command

The BOL W (be on the lookout, wanted/missing persons) command can be used to input infor-mation that will be sent to MCT units and/or CAD users.


1. On the command line at the Dispatch Entry window, type “BOL W” and press <Enter>.

2. The Work with Wanted/Missing Persons window displays. Press <F6>.

48

Executing the BOL W (Be on Lookout Wanted Persons) Command

3. The Wanted/Missing Persons Maintenance window displays. The Subj Type and Name fields are mandatory. The Name is verified through the Global Name Search/Update window. Make your entries and press <Enter>.

To use a jacket that is already in the jacket file, press the <F10> key.

4. The Work with Wanted/Missing Persons window will reappear with the new entry displayed.

49


Step-by-Step: Executing the CAP (Clear a Unit from an Incident) Command

Use the CAP command to clear a unit from an incident.

1. On the command line at the Dispatch Entry screen, type “CAP uuuuuu disp” where “uuuuuu” represents the unit # and “disp” the disposition code of the unit you would like to clear and press <Enter>.

You may use the following format to execute this command for a string of units: CAP 2A10,2A11,2A12 OA. If your agency requires a disposition code, the same disposition code must be used on all units cleared with the CAP command.

2. If only one unit is attached to an incident, both the unit and the incident will be removed from the CAD screen. The unit will be changed to available (green) status and the incident will be sent to the Cleared Call File. Press <F11>.

3. The Work with Cleared Calls window will appear. From here you can select from a variety of processing options that will allow you to, among other things, change, display, and print a selected cleared call record.

• Option 10 can be used to create a new incident from a closed incident.

• Option 11 to recall, reopen, and re-dispatch a closed incident.

• Option 14 to add, view, or change the status and disposition.

• Option 15 to add vehicle information to a record.

• Option 16 allows you to add caller, complainant, and other such names to a record.

• Option 18 allows you to view Radio Log information.

• Option 19 can be used to view dispatch information for a call, including the name of the operator.

• Option 20 allows you to view, add, or modify license information (license plate and drivers license).

50

Executing the CAP (Clear a Unit from an Incident) Command

• Option 22 is used to record additional information pertinent to the call. This access an Additional Information Maintenance window that enables up to six lines of narrative to be added.

• Option 24 allows you to create and maintain associated documents. If you have system tuning set to do so, Dispatch Narrative (displays dispatch, arrive, clear, enroute, depart scene information, etc. regarding units assigned to a call) and CAD System Narrative (displays incident changes, recalled incidents, ProQA information, rerouting information, incident copied, and unit secondary location information) can be accessed via this option.

51


Step-by-Step: Executing the CCP (Clearing an Incident) Command

Clearing an incident makes available all units attached to the cleared incident.

1. On the command line at the Dispatch Entry window, type “CCP iiiixx disp” where “iiiixx” represents the incident # and “disp” the disposition code and press <Enter>.

You may use the following format to execute this command for a string of incident num-bers: CCP uuuu01,uuuu02, uuuu03 disp.

2. The call will be cleared from the monitors and all units attached to the call will be changed to available (green) status.

52

Executing the CDA (Change Dispatch Assignment) Command

Step-by-Step: Executing the CDA (Change Dispatch Assignment) Command

This command is used to over-ride an incident’s GEO beat. You many need to do this if, for example, a unit is dispatched to pick up a subject on warrant who is out of the normal patrol beat. The CDA command tells the system that, for this incident only, the patrol beat will be reas-signed and the unit(s) that would normally be assigned to the call will be changed.

1. On the command line at the Dispatch Entry screen, type “CDA iiiixx beat” where “iiiixx” represents the incident # and “beat” represents the beat to which the incident is to be reassigned. Press <Enter>.

2. No other action is required.

53


Step-by-Step: Executing the CHS (Change Current Station Assignment) Command

The CHS command can be used to change the current station assignment for a unit. This com-mand should be used with caution; it affects the run card recommendations and which stations are toned out when using the tone interface.

Once the command is executed, the Unit Assignments Maintenance window will show the change in the Current Station field.

1. On the command line at the Dispatch Entry window, type “CHS uuuuuu station” where “uuuuuu” represents the incident number and “station” represents the station code to which the unit is to be “currently” assigned. Press <Enter>.

2. If this command is run without a station (CHS uuuuuu), then the unit’s current station will revert to its assigned station.

3. No further action is required.

54

Executing the CHU (Change Unit Assignment) Command

Step-by-Step: Executing the CHU (Change Unit Assignment) Command

The CHU command allows you to make changes to a unit assignment during the course of a shift without taking the unit out of service.

1. At the Dispatch Entry window, type “CHU uuuuuu” where “uuuuuu” represents the unit whose assignment you would like to change and press <Enter>.

2. The Unit Assignments Maintenance window will appear in “Change” mode. Make the desired changes and press <Enter> to save your work. No further action is required.

If your agency consistently has the same units on duty, you can make personnel changes for multiple units by typing CHU followed by all of the units you would like to change. For example: CHU Unit01,Unit02,Unit03,Unit04 … etc.

55


Step-by-Step: Executing the CID (Change Dispatchers ID#)This command is used to changed the ID of the dispatcher who is doing the dispatch functions.

1. At the Dispatch Entry window, type “CID ID#” where “ID#” represents the ID# of the personnel who you want to be dispatching and press <Enter>.

In lieu of the ID#, you may also enter a question mark to access the Personnel Prompt.

2. The dispatcher’s ID# is changed.

56

Executing the CIF (Clear Incident Flag) Command

Ex

S

Step-by-Step: Executing the CIF (Clear Incident Flag) CommandUse this command to clear an update flag from an incident. Update flags are one character fields (SCHGD) located in the call queue portion on the Dispatch Entry window and are used to indi-cate to a dispatcher that the incident has been changed. The possible flags are: I = Incident Changed; N = Narrative Changed; C = Both Narrative and Incident Changed.

1. On the command line at the Dispatch Entry screen, type “CIF iiiixx” where “iiiixx” represents the incident number and press <Enter>.

2. The flag will then clear. No further action is required.

ample of field CHGD

57


Step-by-Step: Executing the CLA (Clear All Assigned) CommandThe CLA (clear all assigned) command is used in conjunction with station dispatch. This com-mand clears all assigned units from a station. For example, if a runcard is setup to allow station dispatch and that station is then assigned to an incident, the units that are assigned but not dis-patched may be cleared by using the CLA command.

This command is most likely to be used by rural or volunteer agencies. If the dispatcher does not know which unit is going to respond first to an incident, the entire station may be assigned. When the first unit arrives, the dispatcher may assign that unit to the incident. The remaining units may be cleared from the incident using the CLA command.

1. On the command line at the Dispatch Entry window, type “CLA iiiixx station” where “iiiixx” represents the incident number and “station” represents the station code. Press <Enter>.

2. The units that were assigned to this incident will now be available for other calls.

58

Executing the CLP (Enter/Change License Plate) Command

Step-by-Step: Executing the CLP (Enter/Change License Plate) Command

The License Plate and License State fields are INPUT fields, enabling the operator to add a license plate and state as a call is taken. The License Plate field also functions as a display for the last plate attached to the incident. The software takes all the various plates attached to an incident and places them in the same queue, i.e., the Work with Plates window. When you pro-cess a license plate or drivers license number that has been previously processed it will carry with it a PLT, DL, SV, or STV hazard notification.

1. On the command line at the Dispatch Entry screen, type “CLP iiiixx” where “iiiixx” represents the incident # to which you would like to add a plate record and press <Enter>.

2. The Work with Plates window displays. Press <F6>.

3. The Plate Maintenance window displays. Here you can enter license plate and/or driver’s license information. Type in as much information as possible and press <Enter>. The fields will clear allowing you to enter another license plate if you should so desire. When you have finished making entries in this window, press <F12>.

59


4. The Work with Plates window will reappear with your new record represented therein. License plate information will appear under the Plate column and Drivers License information will appear under the Drivers License column. The Run column indicates whether a State/NCIC record is attached to the associated incident. It references the NWS Online State / NCIC module.

To return to the Dispatch Entry screen, press <Enter>.

For quicker entry, a license plate or drivers license can be included in the CLP command using the following format: CLP iiiixx LICENSE PLATE# The license plate or drivers license will be automatically added to the incident. To view the license plate or drivers license record, use the CLP command without the end param-eter: CLP iiiixx This will take you to the Work with Plates window. From there you can select the plate or license record for display, modification, or deletion.

60

Executing the CMT (Change Monitor Type) Command

Step-by-Step: Executing the CMT (Change Monitor Type) Command

This command enables a user to change the monitor type from the command line.

1. On the command line at the Dispatch Entry screen, type “CMT 1 2” where “1” represents the current monitor being used and “2” represents the type to be changed to.

2. A combined dispatch code or dispatcher assignment may also be added on to the end of the command, if desired.

3. In the screenshot that follows, only one status monitor is active and it uses a type of “U” with a Combined Dispatch Code of “AD.” If the command “CMT W X NM” is entered, the following will happen.

• Status # 1 will be changed from “U” to “W.”

• The combined dispatch code will change from “AD” to “NM.”

61


Step-by-Step: Executing the CNA (Case Number Assignment) Command

The CNA (Case Number Assignment) command takes the information from a CAD incident and creates a “shell” of a case. This case can then be accessed via Work with Cases. The first officer in the primary unit on which the incident is created will be pulled into the case as the reporting officer.

1. On the command line at the Dispatch Entry window, type “CNA uuuuuu” where “uuuuuu” represents a unit that is currently assigned to an incident. Press <Enter>.

If the CNA command is executed for an incident that has already had a case created, the message “Case already exists for ORI(s)” will appear. Also, the Incident Narrative Entry window will contain a system message indicating a case number has been assigned.

2. The CAD command line will clear. A case with the information contained in the incident will now be created. Whether or not the case # is the same as the incident # is dictated by if the Incident# is equal to Case# field on the Jurisdiction Control File Maintenance window #5 is set to “Y.”

If the Incident# is equal to Case# field on the Jurisdiction Control File Maintenance window #5 is set to “N,” then the Display Additional Incident #’s window will appear with the case number and incident number for this call (as displayed below).

62

Executing the CP1 and CP2 (Copy Incident) Commands

Step-by-Step: Executing the CP1 and CP2 (Copy Incident) Commands

Situations occur in which you might want to make a copy of a current incident. The need for this might arise if, for example, there is another incident of the same type and location as an existing incident. CAD offers two copy commands, CP1 and CP2. These commands are essen-tially the same. The former, however, retains the times associated with the original incident, while the latter does not. If you need to record multiple occurrences of vandalism in the same parking lot, for example, you might want to use the CP1 command so that the same time is maintained for all occurrences. If a police unit on an accident report requests a fire and/or EMS unit, you may want to use the CP2 command to display a realistic call time.

1. On the command line at the Dispatch Entry screen, type “CP1 iiiixx ORI#” where “iiiixx” represents the incident number and “ORI#” the agency in which you would like the incident to be created. If you are unsure of the ORI#, you may instead enter a question mark which will therefore access the CAD Jurisdiction Control Prompt enabling you to select the ORI#. Press <Enter>.

2. No further action is required. The new incident will appear in the call queue with a new incident number.

It may happen that the incident type of a copied incident is not the incident type needed for the new incident. There are two things one can do to correct this problem: 1) Copy the incident and use the INC command to bring the incident back into the work area and make the necessary changes to the Incident Type field, or 2) Change the incident type on the command line while doing the CP1/CP2 command: CP1 iiiixx ORI# IncidentType P (Where the P is for Police opposed to F for Fire, E for EMS, or C for combined).

63


Step-by-Step: Executing the DSP (Dispatch) CommandUse the DSP command to dispatch one or more units to an incident.

1. On the command line at the Dispatch Entry window, type “DSP uuuuuu iiiixx” where “uuuuuu” represents the unit number you would like to dispatch and “iiiixx” the incident number to which it will be dispatched. Press <Enter>.

Multiple units may be dispatched together by typing all of the units together, one after the other, separated from the each other by one comma. For example: DSP 2A10,2A20,2A25 0156AP. Notice that the last unit does NOT have a comma separating it from the incident number.

Should you have the incident already displayed in your work area (in either INC or INQ mode, for example), you can omit the incident number from the DSP command.

If you would like to assign a backup unit to a unit already assigned to an incident, you can use the DSP command with the backup unit # rather than the incident #. When doing this, you must type the letter U in front of the unit to which the backup unit is to be assigned. For example: DSP uuuuuu Uuuuuuu. This tells the system that you are using a unit num-ber in place of an incident #.

2. Once you have dispatched a unit to an incident, the unit will appear on the Unit Status Monitor in Yellow colored characters and next to the associated incident in the call queue. No further action is required.

64

Executing the DS1, DS2 (Depart Scene) and AS2 (Arrive Scene) Commands

Step-by-Step: Executing the DS1, DS2 (Depart Scene) and AS2 (Arrive Scene) Commands

The DS1, DS2, and AS2 commands are used to indicate a unit’s departure from an initial scene and the arrivals and departures to and from subsequent scenes. These commands work very much as does the USP command, allowing you to type a note in the Location field that describes what the unit is doing. This set of commands may be executed an unlimited amount of times before a unit is cleared from an incident. For example, unit 2A10 may depart scene 1 (DS1) before arriving at scene 2 (AS2), which it may also depart (DS2), and so on. Fire and EMS agen-cies use these commands to log a unit’s progress from the incident, to the hospital, and back to the station.

1. On the command line at the Dispatch Entry screen, type “DS1 uuuuuu narrative” where “uuuuuu” represents the departing unit number followed by a free-form description of the location being departed. Press <Enter>.

The DS1 command may be executed only after the unit has been “arrived” at an incident with the ASP command. The DS1 command may be executed for multiple units at a time as long as all of the units in question are in “arrived” status. All units do not have to be attached to the same inci-dent, but they will all display the same note: DS1 2A10,2A20,2A30 Hospital.

The secondary location will be written to narrative if the Unit Secondary Location field in CAD System Tuning window CD0970S2 is set to Yes.

2. The unit will appear in the call queue and on the status monitor in turquoise characters and underlined.

3. Only after a unit has been “departed” from one scene can it be “arrived” at another. To arrive your unit, type “AS2 uuuuuu narrative” where “uuuuuu” represents the unit number followed by a description of the scene at which the unit has arrived. Press <Enter>.

The unit will appear in the call queue and on the status monitor in dark blue characters. In the CAD Dispatch window, the unit will appear in blue and be underlined.

4. If the unit becomes available at scene 2, you may execute the AA2 (available at scene 2) command. This command works much like the AAP (available at scene) command. However, the AA2 command cannot be executed unless the AS2 command has been performed first. On the command line at the Dispatch Entry screen, type “AA2 uuuuuu narrative” where “uuuuuu” represents the unit number and “narrative” is a free-form note describing the unit’s situation. Press <Enter>.

The unit will appear in the call queue and on the status monitor in turquoise characters and underlined.

65


5. To depart scene 2, type “DS2 uuuuuu narrative” where “uuuuuu” represents the unit number followed by a brief note describing the unit’s situation. Press <Enter>.

The DS2 command will not work unless the associated unit has already been “arrived at” a scene or made “available at” a scene with the AS2 and AAP commands respectively.

6. The unit will appear in the call queue and on the status monitor in light blue characters. There is no arrive command for scenes beyond scene two. All further location changes should be indicated with the USP command (see page 132).

66

Executing the ENR (Enrouting) Command

Step-by-Step: Executing the ENR (Enrouting) CommandUse this command to change a unit’s status to enroute to an incident. It can also be used for a secondary location.

1. The ENR command can be entered in four different formats:

ENR uuuuuu

ENR uuuuuu(secondary location)

ENR uuuuuu iiiixx

ENR uuuuuu iiiixx text (secondary location)

Whereas “uuuuuu” represents the unit number; “iiiixx” represents the incident number, and “secondary location” is the free form secondary location that is entered.

2. On the command line at the Dispatch Entry window, type “ENR uuuuuu” where “uuuuuu” represents the unit you would like to show as enroute to an incident and press <Enter>.

Like the DSP and other commands, the ENR command can be executed for multiple units at a time by typing all of the units, one after another, separated by a comma.

3. The unit will now appear in the Call Queue and Unit Status Monitor underlined in amber colored characters. In the Unit Log Inquiry, if the location was secondary, press <F11> to view the secondary locations.

67


Step-by-Step: Executing the EQP (Equipment) CommandUse this command to search for units assigned a specific type of equipment.

1. On the command line at the Dispatch Entry screen, type “EQP equip” where “equip” represents the equipment code associated with the specific type of equipment you would like to search for. Press <Enter>.

If you do not know the equipment code, enter a question mark in lieu of the code and you may select from the list provided.

2. The Display Unit Equipment window appears displaying listing all units supplied with the requested equipment type. Press the <F11> key to view additional information, such as the displayed unit’s Type, Station/Beat, and Status (dispatched, arrived, etc.).

When you have finished viewing the information, press <Enter> or <F12> to return to the Dispatch Entry screen.

Including a numeric value can further refine searches for many equipment types. For example, if a fire inspector was searching for a unit in possession of a ladder at least 16 feet long, he could enter the command as “EQP LAD 16” where “LAD” is the equipment command for ladder. Instead of getting a listing of all units with ladders, he or she would get a listing of units with ladders at least 16 feet long. Keep in mind that the more parameters you include with your command, the less information will be processed and the more time you will save.

Another way to refine your search is to eliminate units that possess the desired equipment but fall outside a specific geographical area. To execute this type of search, however, Police Beats and/or Fire Stations must be divided into Zones.

68

Executing the EQP (Equipment) Command

When executing the EQP command, do it without parameters, by typing “EQP” by itself and pressing <Enter>. The Unit Equipment Subset window will appear. You can now limit your search by zone by prompting the Zone field and selecting the zone to which you would like to restrict your search. Searching by incident will accomplish much the same thing, as the system will search for equipment only within the zone of the selected incident.

69


Step-by-Step: Executing the EVT (Event) CommandThe EVT command enables a time/date stamp to be added to an incident for a fire specific, user-defined activity and also adds a note to the radio log of a call, unit log, monitors and/or second-ary location.

1. On the command line at the Dispatch Entry screen, enter

“EVT eeee iiiixx text”

or

“EVT eeee Uuuuuuu text”

Where “eeee” represents the event code, “iiiixx” the incident number, “uuuuuu” the unit number, and “text” is a note to be attached to the record. Notice that in the second example, an uppercase “U” is entered before the unit number, indicating to the system a unit is being entered instead of an incident. Press <Enter>.

2. The EVT command attaches a record to the radio log and unit log. The unit information is displayed based on the 2nd location field value and how the event code is set up.

To see how the radio log inquiry is updated, from the Work with Incidents window, type an “18” in the Opt field associated with an incident and press <Enter>. The Radio Log Inquiry window will appear. Note the entry generated by the EVT command. Press <F11> to display view 2 and a third time for view 3.

Radio Log Inquiry View 1

70

Executing the EVT (Event) Command



71


CAD Monitors with a secondary location will also display the text in the Secondary Location column.

The Unit Status Display will show the text in the Secondary Location column when using the EVT command in the unit format.

72

Executing the EVT (Event) Command

In the Unit Log Inquiry, the CAD Event will also display in the Secondary Location column. This is accessed via Option 18 on the Work with Unit Assignments window (press <F11> for View 2).

If the event being used is to update Fire incidents, in the Incident Report Maintenance window FR0110S1, the Controlled date and time fields will be updated with the time and date the EVT command was used.

73


Step-by-Step: Executing the EXC and EX2 (Unit Exchange) Commands

CAD offers two unit exchange commands: EXC and EX2. The purpose of these commands is to allow you to change the unit sent to an incident with another, one that is perhaps closer to the incident's location. The only difference between the two commands is that the EX2 command will also make the new unit on the call the primary unit, which, as the first unit assigned, has the responsibility of handling the incident report.

1. On the command line at the Dispatch Entry screen, type “EXC uuuu01 uuuu02” where “uuuu01” represents the new unit (the replacing unit) followed by the unit # of the unit that has already been dispatched, enrouted, or arrived at an incident. Press <Enter>.

2. The first unit in the command string will replace the second as the responding unit and will appear in amber characters on the monitor and on the call queue.

The EX2 command works much the same way as the EXC command except that it also makes the new unit (the first in the command string) the primary unit.

74

Executing the GEO (GEO Prompt) Command

Step-by-Step: Executing the GEO (GEO Prompt) CommandThis command allows you to view GEO records, which is useful when reviewing Cross Streets or responses to a given location.

1. On the command line at the Dispatch Entry screen, type “GEO” and press <Enter>.

2. The GEO Prompt will appear. If the street whose GEO file you would like to view does not appear on the first page of GEO files, you can do one of two things: 1) Press <Page Down> to scroll through the street names until you locate the desired file, or 2) Type the name of the file you would like to view in the Street field at the top of the screen and press <Enter>. This will reset the list of files with yours in the top (first) position.

Use the <F11> key to display alternate “views” of this screen. Each view displays slightly different information. View 1 below, for example, displays the street names, their address ranges, and cross-streets for each record. View 2 displays street name, address range, and the responding agency for each ORI. View 3 displays street name, address range, venue, cross-street, and map. To view a file, type a “5” in the Option (O) field associated with the file you would like to view and press <Enter>.

3. On the GEO Prompt, press <F7> to display the Street Prompt. This displays all streets from the GEO database. An asterisk to the left of the street name indicates a document is attached. Option 24 allows the street to be viewed in display mode only. A valid street that is selected will then be pulled back into the GEO Prompt.

75


Step-by-Step: Executing the HZD (Hazard) CommandWhen an incident has a hazard attached to it, the address will appear with red lettering in the call queue. To see the hazard, do the following:

1. On the command line at the Dispatch Entry screen, type “HZD iiiixx” where “iiiixx” represents the incident # whose hazard information you would like to view and press <Enter>.

You can also enter the incident number and press the associated F key (for example <F7>).

2. The Hazard Display window will appear. Hazards can be viewed via option 1. Because there are different types of hazards, the type of window that appears next varies by what is selected.

76

Executing the HZI (Hazard Inquiry) Command

Step-by-Step: Executing the HZI (Hazard Inquiry) CommandThis command functions much as the HZD command does. The difference is, with the HZI command, you can search for hazards with any of the following criteria: location, common name, cross street, venue, name, license plate #, and/or drivers license #.

1. On the command line at the Dispatch Entry screen, type “HZI” and press <Enter>.

2. The CAD Hazard Inquiry window will appear. The user’s home ORI # defaults. Make an entry in any of the available search fields and press <Enter>.

3. The Work with Hazard Warnings Inquiry window will appear. Select the hazard you would like to view by typing a “1” in the Opt field associated with the hazard you would like to view and press <Enter>.

Information for that hazard will appear. Once you have viewed the record, press <F12> twice to return to the Dispatch Entry screen.

77


Step-by-Step: Executing the INC (Incident Change) CommandIt is sometimes necessary to make changes to an incident after it has been created. To do this, use the INC command.

1. On the command line at the Dispatch Entry window, type “INC iiiixx” where “iiiixx” represents the incident you would like to modify and press <Enter>.

2. The incident information will be displayed. Make the desired changes and press <Enter> to save your work. Pressing <F3> or <F5> here will NOT save your changes.

In the (SCHGD) Other - Inc/Nar Change Flag status field of the incident that was changed, an “I” will appear indicating that a change has occurred to the incident. The next time the incident is accessed, the “I” will go away. This field only appears if it has been added when the screen was designed in the CAD Call Queue Design window. This alerts dispatchers that a change has occurred to the type of incident.

78

Executing the INQ (Incident Inquiry) Command

Step-by-Step: Executing the INQ (Incident Inquiry) CommandThe Incident Inquiry command is similar to the INC command in that it will display the incident record associated with the command. When a record is displayed using the INQ command, however, it is for viewing only and cannot be modified in any way.

1. On the command line at the Dispatch Entry screen, type “INQ iiiixx” where “iiiixx” represents the incident record you would like to view and press <Enter>.

2. The incident information will appear on the screen in “Inquiry” mode. View the information and press <F12> to clear the information and return to incident entry mode.

79


Step-by-Step: Executing the LNK (Link Incidents) CommandThis command allows incidents to be linked together. The LNK command is similar to the ADN command (page 31) in that it allows you to add text to the narrative of multiple incidents. When using this command a minimum of two incident numbers are required. Unlike the ADN com-mand, the text is not mandatory. If using the command without text, a message will be written to the narrative of each incident stating that they have been linked together; if text has been entered it will appear on the line following the message.

1. On the command line at the Dispatch Entry window, type “LNK iiiixx,iiiixx text” where “iiiixx” represents the incidents to be linked followed by a text entry. As long as one incident is open, the incident it is linked to can be open or closed. Press <Enter>.

Use the following format to link the incidents without a text entry: LNK 0767AP, 0768AP

2. The incidents are now linked and the text that was entered appears as in the Incident Narrative Entry window (see the example below) for both incidents.

3. The command can also be used to link an active call with a cleared incident using the following format “LNK iiiixx,?” where “iiiixx” is the incident to be linked.

4. The Cleared Incident Prompt window will appear displaying a list of cleared incidents. You may either type an incident number in the Select Number/Code field or you may locate the incident and type a “1” in the corresponding Opt field and press <Enter>.

80

Executing the MLG (Mileage) Command

Step-by-Step: Executing the MLG (Mileage) CommandThis command allows you to track a unit’s mileage during the course of its shift. This is useful in the case of transporting prisoners, stranded motorists, etc.

1. On the command line at the Dispatch Entry screen, type “MLG uuuuuu” where “uuuuuu” represents the unit # whose miles you would like to work with and press <Enter>.

2. The Work with Unit Mileage window will appear. Press <F6>.

3. The Unit Mileage Maintenance window will appear. The Date/Time field (defaulted to the current), and either one of the Odometer fields or the Mileage field are mandatory. Fill in as many fields as possible and press <Enter> to save your work.

The information you entered will clear allowing you to enter another mileage record should you so desire. When you have finished making entries, press <F12>.

4. The Work with Unit Mileage window will reappear with your new mileage record represented therein. From here you can select your record for display, modification, or deletion. You can also use the <F6> key to add another record.

When you have completed work in this window, press <Enter> or <F12> to return to the Dispatch Entry screen.

81


You can also enter beginning and ending mileage for a unit via one command at the dis-patch entry screen, thereby skipping the multiple screen entry process described above. To do this, simply type the MLG command followed by the unit # followed by either S or E (for Starting or Ending mileage respectively) followed by the actual mileage. For exam-ple, “MLG 2A10 E 14750.”

82

Executing Monitor Commands

Step-by-Step: Executing Monitor CommandsNew World Systems status monitors can display 21 units or incidents at a time. Large agencies with too many units to display on one screen must use the ROL (roll) commands to view their entire fleet or incidents that exist beyond the first screen.

1. On the command line at the Dispatch Entry screen, type “ROL” and press <Enter>.

2. The monitor screen will “roll” downward, displaying the next page/screen of units. This command rolls all columns and can be repeated as many times as is necessary to work your way down the list. You can also execute this command to roll to a specific unit #. To do this, simply type the command followed by the unit # to which you would like to roll and press <Enter>.

There are variations of the ROL command that allow you to roll with specific qualifications.

To roll to a specific unit while rolling only the Additional Unit column, enter the command as “ROA uuuuuu” where “uuuuuu” represents the unit number and press <Enter>.

To roll to a specific unit while rolling only the Incident column, enter the command as “ROI uuuuuu” where “uuuuuu” represents the unit number and press <Enter>.

To roll the call queue monitor, “ROQ” or “ROQ uuuuuu” where “uuuuuu” represents the unit number and press <Enter>. This command only works for monitor #2. Without the unit #, this command will simply roll up the next 21 incidents.

To roll to a specific unit on all monitors, except for the call queue monitor, “ROU uuuuuu” where “uuuuuu” represents the unit number and press <Enter>.

To return a status monitor to its original state after executing one of the above commands, simply type the ROL command by itself and press <Enter>.

83


Step-by-Step: Executing the MOV (Move) CommandIt is sometimes necessary to assign or “move” a Fire/EMS unit or units from one agency to another in order to cover a fire station whose units are occupied with a resource heavy incident. The MOV command was designed for this purpose. The command will also change the recom-mendations on Fire/EMS Run Cards to reflect such a move.

1. On the command line at the Dispatch Entry window, type “MOV uuuuuu iiiixx station” where “uuuuuu” represents the unit # that will be temporarily assigned to another station and “iiiixx” is the incident # with which the other station is occupied, and “station” is the other agency’s station number. Press <Enter>.

2. The unit is moved. When the incident is cleared, you can use the CAP or UAP command to remove the MOV command.

Which command should be used, MOV or MV2 depends on what is set in the Use MV2 on Runcard field in CAD System Tuning window CD0970S5. If set to Yes, MV2. If set to No, MOV.

84

Executing the MV2 (Move-up2) Command

Step-by-Step: Executing the MV2 (Move-up2) CommandThis command updates station information for a unit for the time the specified incident is active. The unit’s status changes to “Moveup,” and the Current Station in Unit Assignments Mainte-nance reflects the station specified. Typically, this is used when a fire unit moves to another sta-tion to cover for units from that station that are busy with a call. This differs from the regular MOV command in that the unit being moved will show as attached to the incident on the mon-itors and in the unit log.

1. On the command line at the Dispatch Entry window, type “MV2 uuuuuu iiiixx station” where “uuuuuu” represents the unit # that will be temporarily assigned to another station and “iiiixx” represents the incident in which the other station is occupied and “station” represents the other agency’s station number. Press <Enter>.

2. The unit will be moved. When the incident is cleared, you can use the CAP or UAP command to remove the MV2 command.

Which command should be used, MOV or MV2 depends on what is set in the Use MV2 on Runcard field in CAD System Tuning window CD0970S5. If set to Yes, MV2. If set to No, MOV.

85


Step-by-Step: Executing the NAM (Add Name to Narrative) Command

The NAM command provides another way for you to add name information to an incident. This command requires that you do a global names inquiry on the subject to display and view prior contacts.

1. On the command line at the Dispatch Entry screen, type “NAM iiiixx caller” where “iiiixx” represents the incident # and “caller” is the caller’s name entered in a last name,first name format. Press <Enter>.

Executing the NAM command will set the “incident update” flag to “N” in the call queue.

2. The Global Name Inquiry window displays allowing you to check for previous contacts by the above subject. If there has been previous contact, the subject’s name will appear here. Use the available options to view, print, check activity or read existing documentation attached to the subject’s record. When you are finished with this screen, press <F12>.

3. The Dispatch Entry window will reappear. To view the names added to an incident, use the NRW (page 89) command.

86

Executing the NAR (Narrative) Command

Step-by-Step: Executing the NAR (Narrative) CommandThe NAR command works similar to the NRW command but enables a user to input a much larger narrative. The text can also be edited after it has been added by executing the same com-mand. This command is not time stamped.

1. On the command line at the Dispatch Entry screen, type “NAR iiiixx” where “iiiixx” represents the incident number to which you would like to attach a narrative. Press <Enter>.

2. A window will appear enabling you to enter a narrative. If you use all the lines on the window, page down for more space to type. When you have finished your narrative, press <Enter> twice to save your work.

87


Step-by-Step: Executing the NOT (Note) CommandThis command allows you to view existing notes and add new notes to the note pad.

1. On the command line at the Dispatch Entry screen, type “NOT” and press <Enter>.

2. For information on how to use the Note Pad function, see the section on “Note Pads” on page 10 of this manual.

If the NOT command is mapped to a function key, the note can be entered from the dispatch entry line. For example, if “HP” is a Note Pad Type, the command could be entered as: HP SAMPLE TEXT (function key). When the function key is pressed, the notepad record will be created using the current date, time, and user.

88

Executing the NRW (Narrative Window) Command

Step-by-Step: Executing the NRW (Narrative Window) CommandThis command allows you to attach narrative to an incident beyond the 40 characters to which you are restricted when using the ADN command (page 31). The command also leaves a time stamp and user name.

1. On the command line at the Dispatch Entry screen, type “NRW iiiixx” where “iiiixx” represents the incident number to which you would like to attach a narrative followed by the free-form text. Press <Enter>.

2. The Incident Narrative Entry window will display with your cursor at the beginning of the Narrative field. Here you can enter your text. Once your entry reaches the end of the line it will immediately jump upward to display in the main body of the window. The window that defaults shows only narrative entered by users. Press <F5> to display the latest entries of narrative including any added by another dispatcher. If there is text on the Narrative line when <F5> is pressed, it will be added to the narrative, just as if <Enter> had been pressed.

Press <F16> to view the system messages.

The user that entered the narrative line will only appear if the Show User Name in Narr field in CAD System Tuning CD0970S2 is set to Yes.

3. The Incident Narrative Entry window will display the system messages as well as the changes made to the Nature of Call field (the Track Changes in Narrative field must be set to Yes in CAD System Tuning window CD0970S2). Press <F16> to toggle between user entered narratives and system messages. Press <Enter> to exit back to the Dispatch Entry window.

89


4. Once narrative is entered, an “N” will appear in association with the incident to which the narrative was attached. The “N” is referred to as the “incident update” flag and will appear in both the call queue and on the CAD screen when the incident is viewed with either the INC or INQ command. Its function is to alert dispatchers to changes that have been made to an incident. If a change other than the addition of narrative is made, an “I” will appear in association with the incident.

The Incident Update field must be designed into the call queue by your agency (SCHGD is the field name, whereas I=Incident Changed, N=Narrative Changed, and C=Both Changed). When setting this feature up, your agency must decide whether to use the “Auto Clear Change Flag” feature or not. If you decide in the affirmative, whenever a narrative is added to an incident, dispatchers will need only view the narrative with the NRW command to reset the incident update flag. Should you decide NOT to use the “Auto Clear Change Flag” feature, dispatchers will have to execute the CIF command to clear the flag (see page 57).

The narratives of the first seven users to enter narratives in the Incident Narrative Entry window will display in different colors, therefore differentiating the users (as shown below). The assigning of a color is based on the chronological order of narratives entered. The first user to add narrative is displayed in White, the second in Green, third in pink, then turquoise, yellow, blue, and red. The next seven users will duplicate the process, with any more shown in standard white.

90

Executing the OFS (Off Shift) Command

Step-by-Step: Executing the OFS (Off Shift) CommandThe OFS or Off Shift command removes a unit or units from service and your monitor.

1. On the command line at the Dispatch Entry screen, type “OFS uuuuuu” where “uuuuuu” represents the unit you would like to off shift and press <Enter>.

To off shift multiple units as a time, separate the units with a comma. Example: OFS 1S10,1S11

2. No further action is necessary - the unit is now off shift.

91


Step-by-Step: Executing the OND (On Duty) CommandThe OND command is used to display a list of personnel and their current status. The current status consists of being logged on a terminal/PC or in a unit (indicating whether or not the unit is a MDT unit). The individual may then have a message sent to them.

This command requires that each user on the system have a unique AS/400 user profile.

If the recipient of the message is using a MDT unit then the message will be sent to the unit. If they are logged on to a terminal/PC then an AS/400 message will be sent. If they are not on a MDT unit or on a terminal then an email message will be sent. The default email address is set up in the employee's personnel file.

To use the OND command, it must be added to the Work with Commands/Function Keys win-dow. In addition, a new field, User Profile, has been added to the Personnel Maintenance win-dow. This field is mandatory and must be populated with the employee’s user profile or the employee may not show up on the Work with Personnel Status window.

1. On the command line at the Dispatch Entry window, type “OND” and press <Enter>.

2. The Work with Personnel Status window will appear. Personnel will display as being logged on to a terminal/PC or in a unit (indicating whether or not the unit is a MDT unit). Any persons who are logged into Dispatch will have a “Y” display in the “Dsp” column.

92

Executing the OND (On Duty) Command

3. Type an “8” in the Opt field corresponding to the name of the employee that you would like to send a message to and press <Enter>. The Send Message window will appear. Type the information you would like to send to the unit in the Message field. If the recipient of the message is using an MDT unit then the message will be sent to the unit. If they are logged on to a terminal/PC then an AS/400 message will be sent (the Terminal field will automatically be populated). If they are not on a MDT unit or on a terminal then an email message will be sent. The email address is set up in the personnel file but may also be overwritten on this window. Make your entries and press <Enter> to send the message.

4. From the Work with Personnel Status window type a “7” in the Opt field associated with a user that has a “Y” in the DSP column and press <Enter>. The Terminal Display window displays up to four terminals that the user is active on as well as indicates which ones are being used in Dispatch.

93


Step-by-Step: Executing the ONS (On Shift) CommandThe ONS or On Shift command puts a unit (or units) On Shift, making it available for dispatch-ing.

1. At the Dispatch Entry command line, type “ONS uuuuuu” where “uuuuuu” represents the unit number of the unit you would like to on-shift (along with any other associated variables you would like to include) and press <Enter>.

This command can be done for multiple units at a time. For example: ONS 1D10,1D11,1C10

2. The Unit Assignments Maintenance window will appear. As a minimum you will want to add personnel (ID#’s) to the unit (if they are not already assigned). Make the necessary entries (for details on the fields and functions in this window, see the CAD System Administrator Guide). If all you want to do is on-shift a unit, press <Enter> (if you entered multiple units on the command per the note above, simply press <Enter> through the Unit Assignments Maintenance window for each unit).

3. The Dispatch Entry window will re-display. Your unit will now have “On Shift” status and be available for dispatching.

“On shifted” units appear in green lettering on CAD monitor styles 1, 4, 6, 7, 8, & 9.

94

Executing the PAC (Assign Incident for PACE Operators) Command

Step-by-Step: Executing the PAC (Assign Incident for PACE Operators) Command

If your agency has purchased the PACE optional Module, you can use this command to create a PACE record from an incident (iiiixx) for use by the PACE operators.

1. On the command line at the Dispatch Entry window, type “PAC iiiixx” where “iiiixx” represents the incident number you would like to send to PACE. Press <Enter>.

2. The incident should now appear as a PACE incident on the Work with PACE Incidents window.

95


Step-by-Step: Executing the PAG (Page) CommandExecuting the PAG command displays the Send Page window (PG0100).

1. On the command line at the Dispatch Entry window, type “PAG” and press <Enter>.

2. The Send Page window displays. In the Pager ID field, type the pager number to which you would like to send a page or prompt this field and select the number / individual from a list of valid entries.

Use the Alpha Message lines to type an alphabetical free form message and the Numeric Message field to type a numeric message.

If the Incident # field is populated, the Alpha Message field must be left blank. In this situation the incident information will be sent to the indicated pager.

The Retain Message field requires a Yes or No response. If set to Yes, after pressing <Enter> the page will be sent, the Pager ID field will be blanked out, and information in the message field(s) will be retained in order that it may be sent to another pager ID. If the Retain Message field is set to No, the page will be sent upon hitting <Enter> and you will return to the CAD Dispatch window.

For ROBOT/Alert software, table 3519 must have a table entry Code of “ROBO.” In the Enter/Change System Control window, the Pager Software Vendor field must be populated with the correct vendor (pulled from table 3519).

96

Executing the PLT (Run License Plate Locally) Command

The “S”indicatand Im

vehrespecthey agreen lopposeusual case h

clo

Step-by-Step: Executing the PLT (Run License Plate Locally) Command

You can check on license plates without having to add one to the system by using the PLT com-mand.

1. On the command line at the Dispatch Entry screen, type “PLT” and press <Enter>.

To resequence the Vehicles Inquiry window to a specific license plate #, type the following: “PLT licenseplate# type” and press <Enter>. “Type” represents the type of vehicle and pulls from table 0127 (example: AUTO).

2. The Global Vehicle Inquiry window will appear. Use the reset fields to resequence the list of license plates by license #, state, year, or type. Use the processing options to view a record, its activity, documents, and NCIC Transactions.

When you have finished viewing license plate information, press <Enter>. The Dispatch Entry screen will reappear.

and “I” e Stolen pounded icles tively. If ppear in ettering, d to the red, the as been sed.

97


Step-by-Step: Executing the PRC (Print Rip and Run) CommandThe PRC command can be used to send a snapshot of information to the unit’s station on a rip and run. The command sends a transmission to the unit’s station in the “cleared” format.

1. On the command line at the Dispatch Entry window, type “PRC iiiixx uuuuuu” where “iiiixx” represents the incident you would like the information sent and “uuuuuu” the particular unit. Press <Enter>.

2. The printer will print the information; no further action is needed.

98

Executing the QCE (Quick Call Entry) Command

Step-by-Step: Executing the QCE (Quick Call Entry) CommandThe QCE command allows you to quickly dispatch a unit to an incident without having to val-idate address information, any location can be entered provided that it is clearly stated. Quick calls also differ from normal calls/incidents in that:

• Quick calls are tracked with a different numbering system than incidents,

• Quick calls are displayed in white or yellow lettering (see the note below) in the call queue and on the status monitor,

• Quick calls have only one status; the Time of Call and Dispatch / Arrival Times are all the same.

In CAD Jurisdiction Control File Maintenance window CD0910S2, in the QCE Defaults section, is the GEO Search field. If this field is set to Yes, an address using the QCE com-mand will be GEO verified and the quick call will appear in yellow lettering in the call queue and on the status monitor. If set to No, it will not be GEO verified and the quick call will appear in the call queue and status monitor in white lettering.

1. On the command line at the Dispatch Entry screen, type “QCE” and press <Enter>.

2. The Quick Call Entry Prompt will appear. In this window, only the Incident Type and Location fields are mandatory. Whether the location is validated against the GEO database is dependent on what is set in CAD Jurisdiction Control (see the note above). If it is not, you can enter anything here, provided that you state it clearly.

If you enter a plate # and your agency utilizes the On Line CAD interfaces to State & NCIC, the plate information will be automatically sent to those systems. The Description field is used in the same way that the Nature of Call field in the CAD screen is used, allowing a description of up to 45 characters in length. The <F10> key allows you to add up to five license plates and/or drivers licenses to a quick call. When you have finished making your entries, press <Enter>.

In step 1 you can execute the command with the unit # and incident type information included, e.g., QCE 2A10 ANIM. This may speed things up even further, for when the Quick Call Entry Prompt appears, only the Location field will require attention and the

99


blinker will be positioned there already awaiting your entry. The address can also be added in step 1 by using the following format: QCE 2A10 BOMB; WILLOW ST. Note that the semicolon must be added before the address.

3. The quick call will display in the call queue and on the monitor. When the unit is cleared, the quick call may be cleared with either the CAP or CCP command. Executing these commands will send the quick call to the “Cleared Quick Call” file. All information relating to a cleared quick call is retained and available in the Work with Quick Calls accessed via Option 7 on the Dispatcher Menu.

100

Executing the QCR (Quick Call to Regular Call) Command

Step-by-Step: Executing the QCR (Quick Call to Regular Call) Command

The QCR command allows you to turn a quick call into a normal incident. For recording keep-ing purposes, the original quick call is retained in the Work with Quick Calls window.

1. On the command line at the Dispatch Entry screen, type “QCR iiiiqp” where “iiiiqp” represents the quick call number and press <Enter>.

2. The number will automatically be converted to the next available incident number; both the monitor and call queue will reflect this change. A message will be sent from CAD to any Mobile units on the call.

No further action is required.

If after the conversion to a regular call the address field appears in amber lettering, the address will have to be GEO validated, otherwise the incident cannot be cleared from the call queue. To validate an address, do the following: 1.Use the INC command to bring the incident up into the work area; 2.Using the standard address format, type a valid address in the Location field; 3.Type the appropriate code in the Location Type field: S for Street Address, C for Com-mon Name, X for Intersection. If an O for Override is left in this field, you will either have to enter an Area, Section, Beat, Quadrant, and District, or you will have to override each field.

3. The Radio Log Inquiry window will display an entry showing the quick call was converted to an incident. From the Dispatcher Menu, select Option 7, Work with Quick Calls. Locate a quick call that has been converted into an incident and type an “18” in the associated Opt field and press <Enter>.

4. Press <F11> to display view 3. The notes show the specific incident number the quick call was changed to.

101


Step-by-Step: Executing the QENT (Quick Entry) CommandThe QENT (Quick Entry) command is the equivalent of creating an incident and then pulling it back up via the INC command. This allows the incident to be quickly entered into the system for dispatch yet allows further information to be added to it.

This command can also be setup as a function key that executes when the corresponding “F” key is pressed rather than the command entered and <Enter> being pressed.

1. At the Dispatch Entry screen, enter the incident type, location, and unit that you would like to dispatch to the incident. On the dispatch entry command line type “QENT” and press <Enter>.

2. The incident will now be created and units dispatched to it. The incident will also remain in “change” mode so that additional information can be added to it.

102

Executing the RCF (Rolodex Card File) Command

Step-by-Step: Executing the RCF (Rolodex Card File) CommandThis command provides dispatchers with a simple means of maintaining frequently called phone numbers.

1. On the command line at the Dispatcher Entry screen, type “RCF name” where “name” represents the business name or last name of the individual whose card file you would like to view or modify and press <Enter>.

2. The Work with Card File window will appear with your selected subject (business/individual) or its closest match at the top of the list. The card file type, contact, and phone number are listed to the right of each subject. A number of processing options are available that allow you to modify, copy, display, print, and delete existing card files. Option 11 allows you to add a new contact or modify existing contact information.

To add a new card file, press <F6>.

Had the RCF command been executed by itself in step 1, without parameters, the Work with Card File window would appear just as it does below but at the very top of the card file list.

3. The Card File Maintenance window will appear. The Business/Person Name, Card File Type, and State fields are mandatory. Enter as much information as is possible and press <Enter> to save your work.

103


4. The Work with Card File window will reappear with your new record represented therein. To add the contact name and telephone number to the card file, type an “11” in the Opt field associated with the file and press <Enter>.

5. The Work with Card File Contacts window will appear. Press <F6>.

-

6. The Card File Contact Maintenance window will appear. If individuals associated with this card file must be contacted in sequence, type the sequence # associated with this particular contact in the Sequence # field. Enter a contact name, a phone number, and, if available, an extension #. In the Phone Type field, indicate whether this is a business, home, cell phone, pager, etc. Only the Contact Name field is actually mandatory.

When you have finished making entries, press <Enter> to save your work. The fields clear enabling you to enter another contact, which you may do or press <F12> to exit. The Work with Card File Contacts window will reappear with your new contact record represented therein. Press <F12> again.

7. The Work with Card File window will reappear with the contact name and phone number now displayed.

104

Executing the RCE (Rapid Call Entry) Command

Step-by-Step: Executing the RCE (Rapid Call Entry) CommandThis command allows you to enter a “rapid call,” a call entered with a minimum amount of information in order that it may be processed as quickly as possible. Rapid Calls function much as Quick Calls do. They track a regular incident number and require GEO validation before they may be cleared from the call queue.

As with the QCE command, you may enter the RCE command with a unit number, incident type, and address: RCE 1D10 BOMB; 300 WILLOW ST (it is important to note the semi-colon between the incident type and address). If you exclude the address, when the com-mand is executed, the rapid call entry window will appear with your cursor positioned in the Location field ready for your entry. Here, too, the <F10> key can be used to attach up to five additional license plates and/or five drivers license numbers to the rapid call.

1. On the command line at the Dispatch Entry screen, type “RCE” and press <Enter>.

2. The Rapid Call Entry Prompt will appear. Type in a Unit, Incident Type, and Location and press <Enter>. No further action is required.

105


Step-by-Step: Executing the RCMD (Recommending Units) Command

This command, RCMD, must be set up as a function key.

1. A call must be pulled up on the Dispatch Entry window. Press the function key you have assigned (typically <F10>).

2. If the call was a police call, the Police Recommendations window will appear. The incident type entered will determine the Recommendation window that will appear. If no units are available, the message “No Units found to Recommend” will appear at the bottom of the window and the Recommendations window will not appear. The incident will remain on the screen. Use option “D” to dispatch units to a call.

3. View 1, shown below, has station 2 as the assigned station (this is implied and not displayed). It shows Station 6 and an “M” indicating that station 6 is the move to station. Press <F6> to display the second view.

4. The second view shows the assigned station (STA2) and move to station (STA6) abbreviated rather than completely spelled out. The TOGD command can also be used from this window to toggle between the two views.

The codes used to dispatch, put a unit on standby, etc, are all set-up ahead of time and will therefore vary by customer.

106

Executing the RES (Resend Dispatch Information to Mobile Units) Command

Step-by-Step: Executing the RES (Resend Dispatch Information to Mobile Units) Command

Use this command to resend dispatch information to mobile units.

1. On the command line at the Dispatch Entry screen, type “RES uuuuuu” where “uuuuuu” represents the active unit # to which you would like the unit sent. Press <Enter>.

2. The information will be sent. The command can be used with multiple units (each unit will be sent a dispatch command). This command is most useful when using field reporting, as it requires a “Dispatch message” to create a case report.

107


Step-by-Step: Executing the RIP (Reprint Rip & Run) CommandUse this command to reprint a rip & run.

1. On the command line at the Dispatch Entry screen, type “RIP iiiixx station” where “iiiixx” represents the incident number and “station” the station to which you would like the printout sent. Press <Enter>.

2. The Rip & run will be sent to that station’s designated printer. Nothing more needs to be done.

108

Executing the ROT & AMB (Wrecker & Ambulance Rotation) Commands

Step-by-Step: Executing the ROT & AMB (Wrecker & Ambulance Rotation) Commands

These commands will recommend a wrecker or ambulance for a call based on geographical location or specific services required.

1. On the command line at the Dispatch Entry screen, type “ROT iiiixx code” for wrecker or “AMB iiiixx code” for ambulance where “iiiixx” represents the incident # and “code” represents the sub-type code of vehicle requested, e.g., LARG for large wrecker, VAN for medical van, etc. Press <Enter>.

If you do not know what code you need, type a “?” in lieu of the code and table 2987 will be accessed.

2. The Wrecker Selection or Ambulance Selection window will appear with a list of vehicles from which you can choose. Select one by typing a “1” in the Opt field associated with the vehicle you would like to recommend and press <Enter>.

109


Step-by-Step: Executing the RRC (Reroute, Clear) CommandLike the RRN command, the RRC is a rerouting command. It is distinguished from the former in that the unit’s initial incident is cleared before the unit is rerouted to the second incident. It also allows for a disposition code.

1. On the command line at the Dispatch Entry screen, type “RRC uuuuuu iiiixx” where “uuuuuu” represents the unit # and “iiiixx” represents the incident to which it is to be rerouted. You can also add a disposition to the end of the string that will be added to the incident that is being cleared. Press <Enter>.

2. The unit/incident will appear in both the call queue and status monitor in amber characters (Dispatched mode). The initial incident will be removed from the call queue and sent to the cleared call file.

Some departments require dispatchers to use Disposition codes. If this is the case at your agency, an incident will not be cleared until the Disposition Code is applied. Disposition codes can be entered at the end of a command stream. For example “RRC uuuuuu iiiixx DC” where “DC” represents the disposition code.

110

Executing the RRN (Reroute, No Clear) Command

Step-by-Step: Executing the RRN (Reroute, No Clear) CommandUse this command to reroute a unit from one incident to another without clearing the unit’s ini-tial incident.

1. On the command line at the Dispatch Entry screen, type “RRN uuuuuu iiiixx” where “uuuuuu” represents the unit # and “iiiixx” the incident # to which you would like the unit sent. Press <Enter>.

2. The unit will appear in the call queue in amber characters (Dispatched) attached to the new incident. Call stacking will automatically “Stack” the call for the unit that has been removed. In the event that another unit is sent to take the call, the incident will have to be removed from the stack of the original unit. When a call is “stacked” it does not display on the status monitor.

111


This cindicatcall hacreat

Step-by-Step: Executing the SHD (Call Scheduling) CommandThis command allows you to schedule a call for a later date/time. Many police agencies use this command to schedule funeral escorts, abandoned vehicle checks, etc.

1. On the command line at the Dispatch Entry screen, type “SHD” and press <Enter>.

2. The Work with Scheduled Calls window will appear. Active calls, i.e. scheduled but not yet created, default on this window. Press <F6>.

The <F17> key enables you to print a listing of scheduled calls within a user-defined date and time range.

3. The Call Scheduling Maintenance window displays. The Schedule Date, Event Date, Incident Type, Location, Location Type, and Call Source fields are mandatory. Enter these and as many of the remaining fields as you like and press <Enter>. See below for a description of all fields within this window.

olumn es if the s been

ed yet

112

Executing the SHD (Call Scheduling) Command

Description of Data Fields within theCall Scheduling Maintenance window


Creation Date/Time

The date and time the incident will be created. This is not mandatory if the Time Delay field is populated with “1” or more. If no Creation Date/Time is entered, the program will take the Time Delay entry (which must therefore be at least one minute) and add it to the current date and time to come up with the creation date and time.

Retain EntryA Yes in this field will retain the entry after the call(s) have been created. If it is set to No, then once the call is created, it will no longer exist in the Work with Scheduled Calls window.

Create # Calls Use this field to create multiple calls. This field defaults to “1.” If greater then “1,” the Time Delay field will be mandatory.

Time Delay Enter the amount of time to pass between creation of calls. This field is mandatory if the Create # Calls field is greater than one.

Auto Create CallUse this field to indicate whether you would like the call to be created automatically on the given date and time or if an operator is to create one manually: Y=automatically, N=manually by operator.

User to Receive Message

Indicate here the name of the operator/user that is to receive a message. To manually activate the call this field is then mandatory if the Auto Create field is set to No.

*Incident Type Police, Fire, EMS, and Combined incident type groups are all valid.

Status Status will default to “Y” (in progress) but may be changed by the operator.

Prty The priority will automatically populate based on the incident type you choose.

Report This field will automatically populate based on the incident type you choose.

*Location, Location Type, Cross Street

The address entered in this window requires GEO validation. It can be over-ridden as long as a venue and assigned beat are filled in.

Venue The operator can either fill in this field or wait for the address to be GEO validated, at which time the Venue field will be automatically filled in.

Phone Number If there is a phone number associated with the scheduled call, enter it here.

Asgn Beat This field allows the operator to override the incident’s beat assignment.

Responding ORI # This field is automatically populated with the default ORI # but may be overridden.

*Call Source Use this field to indicate the source of the incident information.

Received ORI# This field is automatically populated but may be overridden.

Primary Unit This field allows the operator to assign a unit to the scheduled call.

113


4. The Work with Scheduled Calls window will appear with your new scheduled call represented therein. From here your record can be selected for modification, deletion, and viewing. It can also be selected for activation (Option 10), which overrides the timer and allows you to activate a call at any time. Press <F16> to toggle between scheduled (Active) and created (Done) calls.

Completed Calls

5. Use Option 3 to copy a scheduled call (the new call retains all the entries in the original call). Use Option 10 to immediately activate a call and override the timer.

Received ID# This field is automatically populated by the ID of the user creating this call.

Quick Call This field will automatically default to “N.” If, however, you would like to generate a quick call, type a “Y” in this field.

Received Shift Indicate here the shift this call came in on.

Nature of Call Use this field to enter free-form text pertaining to the incident.

Additional InfoThe number and length of the lines will be the same as on the Dispatch Entry window, making for a smooth transfer of data. The lines are either 45 or 70 characters long.

Description of Data Fields within theCall Scheduling Maintenance window


114

Executing the SHM (Scheduled Messages) Command

Oncehas bewill bfrom

Step-by-Step: Executing the SHM (Scheduled Messages) Command

The SHM (Scheduled Messages) command accesses the Work with Scheduled Messages window and displays all scheduled CAD messages.

1. On the command line at the Dispatch Entry window, type “SHM” and press <Enter>.

2. The Work with Scheduled Messages window will appear. Messages on this window are pending or on hold. Similar to when these messages were created with their respective CAD commands, they can be changed, deleted, or displayed. Press <16> to view all sent messages.

3. The sent messages will now display. You may press <F16> again to toggle back to the pending messages. Press <F6> to add a message.

a message en sent, it

e removed this view

115


4. The Scheduled Message Maintenance window will appear. See the table that follows for a definition of the fields in this window. Make your entries and press <Enter> to save the new record.

Description of Data Fields within theScheduled Message Maintenance window

To Enter a specific user the message is intended for.

ORI/Code/Dispatcher Assignment

These fields may be entered instead of a user ID in the To field and indicates what group of dispatchers the message will be sent to. You may enter an ORI, combined dispatch code, or dispatcher assignment. (If a combined dispatch code is used in the second field, then the corresponding ORI field will need to be entered as well. If a dispatcher assignment is entered, the corresponding ORI must be entered as well.) An entry in the dispatcher assignment will send a message to all users viewing any of the beats contained within the assignment.

Hold Message A Yes in this field prevents the message from being sent until this field is set to No.

Time IntervalIf the message is to be sent multiple times, the time between each time it is to be sent. Defaults from what is set in the Message Reminder Delay field in CAD System Tuning window CD0970S2.

Times to Send This is the number of times to send this message. The message will remain in pending status until the final time it has been sent. This field defaults to “1.”

Next Date/TimeIf nothing is entered in this field, the program will take the entry in the Time Interval field and add it to the current date and time to come up with the next time the message will be sent.

Subject Line Defaults from CAD System Tuning window CD0970S2 in the “Incident Reminder Text” field.

Message Use these lines to enter the message that will be sent.

116

Executing the SHM (Scheduled Messages) Command

5. Messages, both sent and pending, can be copied by using Option 3 on the Scheduled Message Maintenance window. When a message is copied, the Scheduled Message Maintenance window will appear in “Add” mode with the data carried over from the copied message.

117


Step-by-Step: Executing the SKL (Skills) CommandThe SKL command can be used to display all personnel who match the desired keyword and are on-shift. In order for the employee to display, two things must be setup in the Personnel Maintenance window. The employee must be in an active status in the Status field and the par-ticular course needs to be assigned to the employee. This is accomplished via <F7> on the Per-sonnel Maintenance window and adding the desired skill. These skills are setup in table 0400 and are assigned to the individual courses.

1. On the command line at the Dispatch Entry window, type “SKL skill” where “skill” represents the skill code. Press <Enter>.

If you don’t know the skill code, you may enter a question mark to prompt table 0400.

2. The Skill Set Prompt window will display. All personnel who are on-shift and have the selected skill will display. Prompt the Skill field to select other skills and the personnel who match. Press <Enter> to return to the Dispatch Entry window.

118

Executing the SND (Send Message) Command

Step-by-Step: Executing the SND (Send Message) CommandThis command allows an operator to send another operator a message. The message displays on the same line as the Incident Created messages display. An Incident Created message will overwrite a CAD operator message, so it is possible that the latter may never reach its intended reader.

1. On the command line at the Dispatch Entry screen, type “SND signon message” where “signon” represents the user’s Sign-on and “text” is the message you would like to send him/her (up to 55 characters in length). Press <Enter>.

2. You can also send a message to everyone within a specific ORI or sub-ORI. To do this, do the following:

SND ORI# message (Up to 55 characters)

Or

SND Sub-ORI# message (Up to 55 characters)

If you are uncertain of the ORI#, you may instead type a question mark in its place which will then access the CAD Jurisdiction Control Prompt window.

119


Step-by-Step: Executing the SRI (Special Response Information) Command

A red Incident Type field in the call queue indicates that special response information exists for that particular incident type. To view the special response information, do the following:

1. On the command line at the Dispatch Entry window, type “SRI inci” where “inci” represents the incident type whose special response information you would like to view. Press <Enter>.

2. If more than one document is attached to the special response, then the Documents Inquiry window will appear enabling you to select the document you would like to view. If only one document is attached, then the Free Form Document window will appear. If no documents are attached to the incident type, then the Incident Type Inquiry window will appear.

120

Executing the SRI (Special Response Information) Command

121


Step-by-Step: Executing the TIM (Time in Minutes) CommandIt is occasionally necessary to leave a unit in a particular status for an extended period of time. A unit, for example, may be sent to pick up a prisoner from another agency far away. Typically, the unit would be placed in Dispatch status until it reached its destination, at which time the ASP command would be executed. As soon as the unit is assigned the prisoner pick-up, a dis-patcher may reset the unit timer with the TIM command. The timer will remain in over-ride mode until the designated time has elapsed or another command is executed.

The Unit Check In (UCP) and CHU command are the only commands that will not remove the TIM over-ride command.

1. On the command line at the Dispatch Entry screen, type “TIM uuuuuu time” where “uuuuuu” represents the unit to which this command applies and “time” is the time (in minutes) that the unit is to remain in “over-ride” mode. Press <Enter>.

2. The timer will remain in over-ride mode until the designated time has elapsed or another command is executed.

122

Executing the UAP (Unit Available) Command

Step-by-Step: Executing the UAP (Unit Available) CommandWith this command you can remove a unit from an incident without removing the incident from the call queue.

1. On the command line at the Dispatch Entry window, type “UAP uuuuuu” where “uuuuuu” represents the unit # you would like to remove from an incident and press <Enter>. No further action is required.

Use the following format to execute this command for a string of units: UAP uuuuuu,uuuuuu,uuuuuu.

2. The unit should now appear as available (in green characters) on your monitor and the incident will display with a light blue rectangle in the Unit field.

123


Step-by-Step: Executing the UBP (Unit Out of Service) CommandUse this command to indicate that a unit is out of service. This command can be used only for units in the “Available” status.

1. On the command line at the Dispatch Entry screen, type “UBP uuuuuu text” where “uuuuuu” represents the unit that will be put out of service and “text” represents the location of the unit (in free-form text) or the unit’s situation, for example. Press <Enter>.

Use the following format to executed the UBP command for a string of units: UBP uuuuuu,uuuuuu,uuuuuu text. Keep in mind, however, that all units within the string will share the same notation.

2. The unit will display on the unit status monitor in red lettering.

124

Executing the UCI (Unit Check In) Command

Step-by-Step: Executing the UCI (Unit Check In) CommandWhen executed, this command will “check in” all units associated with an incident. That is, the unit timer will be updated for all these units, as if the UCP command had been used for each of the units on the case.

1. On the command line at the Dispatch Entry window, type “UCI iiiixx” where “iiiixx” represents the incident number and type and press <Enter>.

2. No further action is required.

125


Step-by-Step: Executing the UCP (Unit Check In) CommandUse the UCP command to log an incident of voice contact with your officer. In addition to log-ging the time of contact, this command will also reset the system timer.

1. On the command line at the Dispatch Entry window, type “UCP uuuuuu” where “uuuuuu” represents the unit # checking in and press <Enter>. No further action is required.

Use the following format to execute this command for a series of unit numbers: UCP uuuuuu,uuuuuu,uuuuuu.

2. If the time has expired, the incident or unit will appear reverse-highlighted. The UCP command resets the timer.

CAD features a set of command timers that alert dispatchers when a unit has been in a single status (Available, Dispatched, Arrived, etc.) for an extended period of time. The amount of time to expire before the timer “goes off” is determined by your department and may be changed at any time. To accommodate the priority system used to categorize calls, each command may have up to nine status times. For example, a Priority 1 dispatch com-mand may be set to 10 minutes, Priority 2 to 15, and so on. In this example, a unit respond-ing to a priority 1 call that has spent more than 10 minutes in Dispatched status will appear reverse highlighted in the status monitor. The same is true of the incident attached to the unit. The reverse highlight will remain until the dispatcher uses the UCP command (or some other command that resets the timer, like ASP) for this unit.

126

Executing the UOP (Unit Out of Service for Repair) Command

Step-by-Step: Executing the UOP (Unit Out of Service for Repair) Command

This command is not used regularly because it removes the associated unit from most monitors (#1, #4-9). Monitor #3 and the Static Display Monitor will still display the unit. It is necessary to use this command, however, when using replacement units on fire run cards.

1. On the command line at the Dispatch Entry screen, type “UOP uuuuuu text” where “uuuuuu” represents the unit number and “text” is the free-form text describing the unit’s situation. Press <Enter>. No further action is required.

2. The unit will be removed from both the monitor and the call queue. To view the status of this unit you must use the Static Unit Display (<F8> from CAD or Option 2 from the Dispatcher’s Menu), reference the Unit Radio Log (URI), or execute the CHU (Change Unit Information) command for the unit in question.

You can clear the UOP status by executing either the UAP or CAP command. Once this is done the unit will reappear on the monitors.

127


Step-by-Step: Executing the URA (Unit Reassignment) CommandUse this command to change a secondary (or third or whatever) unit to the primary unit assigned to an incident. The unit must already be assigned to the incident; this command makes them the primary unit assigned to the incident.

1. On the command line at the Dispatch Entry screen, type “URA uuuuuu” where “uuuuuu” represents the unit you would like displayed in the first ranked position and press <Enter>. No further action is required.

2. The unit that you entered will now be the primary unit assigned to the incident.

128

Executing the URI (Unit Radio Log Inquiry) Command

Step-by-Step: Executing the URI (Unit Radio Log Inquiry) Command

Use this command to do a quick check on unit history, an incident #, or a quick call.

1. On the command line at the Dispatch Entry screen, type “URI” and press <Enter>.

2. The Unit/Radio Log Inquiry window will appear. Here you can collect information on a particular unit, incident #, or quick call. Enter the necessary information and press <Enter>.

This screen can be bypassed by entering a specific request after the URI command. For example, to request information on a particular unit, you could enter the following at the command line: URI 2A20. The next window to appear would be the Unit Log Inquiry win-dow for unit 2A20.

3. The window that appears next will depend on what information you requested in the previous step. In the example, we entered unit number B1A in the Unit field and the Unit Log Inquiry window appeared. Notice that pressing the <F11> key will provide you with alternate views of this window, i.e., screens with additional information. The alternate views are shown in the following four screenshots.

129


130

Executing the URP (Unit Report Writing) Command

Step-by-Step: Executing the URP (Unit Report Writing) Command

Another way to show a unit as being out of service is to use the URP command. Unlike the UBP command, the URP command can be executed for a unit attached to an incident. This command can also be used to indicate lunch breaks, prisoner transports, fuel stops, and the like.

1. On the command line at the Dispatch Entry screen, type “URP uuuuuu free form text” where “uuuuuu” is the unit number that is writing a report and “free form text” is the free-text entry. Press <Enter>.

2. The unit will appear in the unit status monitor in pink lettering. If the unit was attached to an incident, it will appear in the call queue in pink lettering as well.

3. The secondary location will be written to narrative if the Unit Secondary Location field in CAD System Tuning window CD0970S2 is set to Yes.

131


Step-by-Step: Executing the USP (Secondary Location) CommandUse this command to show a unit as being at a location other than the primary incident location. The secondary location is entered in free-form text, e.g., McDonald's or Big Al'’ Car Wash. Dis-patchers commonly use this feature as a “notes” field for an incident or a unit.

1. A unit can be in any status prior to executing this command and there is no limit to the amount of times it can be executed. On the command line at the Dispatch Entry screen, type “USP uuuuuu text” where “uuuuuu” represents the unit number and “text” is the new location (in free form text) and press <Enter>. No further action is required.

To execute this command for a series of unit numbers, use the following format: USP uuuuuu uuuuuu uuuuuu text.

2. The free form text will now be attached to the:

• Incident as a narrative document

• Radio log inquiry

• Incident report

Your free-text note will appear in the Unit Secondary Location field on the status monitor. Depending on which monitor style you’ve selected, only the first 8-20 characters of the note will actually appear. This depends on the Unit Secondary Location field in CAD Sys-tem Tuning window CD0970S2 being set to Yes.

132

Executing the WCC (Caller / Complainant) Command

Step-by-Step: Executing the WCC (Caller / Complainant) Command

The WCC command allows you to do one of two things, depending on whether or not you spec-ify an incident number. If you execute this command by itself, without an incident number, the Names Inquiry window will be displayed. This window will list all of the names from all of the ORIs to which you are assigned.

If you do specify an incident number, as we do in the example below, executing the command will prompt the Work with Names program, which enables you to add and maintain name records associated with the specified incident.

1. On the command line at the Dispatch Entry screen, type “WCC iiiixx” where “iiiixx” represents the incident # and press <Enter>.

You can also execute this command by entering a U to indicate a unit and then entering the unit name. Example: WCC U1E10

2. The Work with Names window will appear. Press <F6> to add a record.

133


3. The Name Maintenance window will appear. The Type and Name fields are mandatory. Prompt the former and select the type of caller. In the Name field, type the name of your caller / complainant in the Last,First,Middle,suffix format. A full name is not necessary; it will not be validated against the name database. If the subject is the primary caller and this record was automatically created, the Contact field will be populated if the CAD Dispatch window was designed to include the associated field (INCNTC) and was populated. Once you have finished making entries, press <Enter>.

4. The Work with Names window will reappear with your new name record represented in the list of records. Press <Enter> to return to the Dispatch Entry screen.

134

UD

Co

on

ng

up

c

.

Appendix A CAD Commands and Function Keys

CAD CommandsWhen you are in the Dispatch Entry window, if you are unsure of the syntax of a CAD com-mand, on the CAD command line simply type a question mark, a space, and the command in question. For example, ? DSP. This will display the syntax of the command on the command line.

The table below displays the various commands available in CAD. Some may be setup differ-ently on your system than what is shown here. On some, a shorter version of the command may be setup. For example, many agencies use the D command in lieu of the DSP command. Use the first column in the table to record your own version of the command.

ser-efined mmand Command Description

Parameters/Examples/Helpful Information

AAP At Scene Available AAP_uuuuuu

ADN Add Narrative ADN_iiiixx_text (for short narratives: electric Co. isthe way, etc.)

ADS Assist Dispatch ADS_uuuuuu,uuuuuu_uuuuuuAEN Assist En Route ADS_uuuuuu,uuuuuu_uuuuuuAIN Additional Incident Number AIN_iiiixxAS2 Arrive Scene Two AS2_uuuuuu_locationASG Assign Unit to Incident ASG_uuuuuu_ iiiixxASP Arrive ASP_uuuuuu_(iiiixx)BET Beat Command BET_iiiixx (gives units assigned to beat of call)BOL BOLO Command BOL_? (Accesses table to select type of bolo)

CAP Clear Unit CAP_uuuuuu_(disposition if desired. Use ? to briup table)

CCP Clear Incident CCP_iiiixx_(disposition if desired. Use ? to bring table)

CDA Change Dispatch Assignment CDA_iiiixx_BEAT

CHS Change Unit’s Current Station Assignment CHS_uuuuuu_station#

CHU Change Unit CHU_uuuuuu (to change information on a specifiunit)

CID Change Dispatchers ID CID_ID#CIF Clear Incident Flag CIF_iiiixxCLRCR Clear Screen Resets to top of call queue. Typically set up as F5

135

Appendix A: CAD Commands and Function Keys

s

r

an ism

(or)

UD

Co
CLCS Clear Screen Does not reset to top of call queue. Typically F5. CLP Enter/ Change License Plate CLP_iiiixx_plate_stateCLRS Clear Screen Typically F5
CMDS CAD Commands Displays the Work with Commands/Function Keyscreen.

CMT Change Monitor Type CMT_status1_status2_combined dispatch code odispatcher assignment

CNA Case Number Assignment CNA_uuuuuu

CP1 Copy Incident (original times)CP1_iiiixx_ORI/ORI code_incident type_P/F/E (ifofficer needs multiple incident numbers for vandalin a neighborhood)

CP2 Copy Incident (updated times) CP2_iiiixx_ORI/ORI code_incident type_P/F/EDOT Department of Trans. DOT_DOT# (interfaces to DOT)DS1 Depart Scene One DS1_uuuuuu_locationDS2 Depart Scene Two DS2_uuuuuu_locationDSP Dispatch DSP_uuuuuu_iiiixx

ENR EnrouteENR uuuuuu or ENR uuuuuu(secondary location) ENR uuuuuu iiiixx (or) ENR uuuuuu iiiixx text (secondary location)

EQP Equipment Search EQP_equipment_quantityEVT Event EVT eeee iiiixx text or EVT eeee Uuuuuuu textEXC Exchange Unit EXC uuuu01 uuuu02 GEO GEO Inquiry GEO_locationHZD Check for Hazards HZD_iiiixxHZI Hazard Inquiry HZIINC Work with Incidents INC_iiiixxINQ View Incident INQ_iiiixxLNK Link Calls LNK_ iiiixx, iiiixx_textMLG Mileage MLG_uuuuuuNAM Add Name to Narrative NAM_iiiixx_last,first,middleNAR Large Narrative Window NAR_iiiixxNOT Notepad NOTNRW Narrative Window NRW_iiiixxOFS Off Shift OFS_uuuuuuOND On Duty OND ONS On Shift ONS_uuuuuuPLT Run License Plate Locally PLT_plate_type

QCE Quick Call Entry QCE_uuuuuu_incident type,plate,state; location/cross;description



136

CAD Commands

it

,

ng

e

for

UD

Co
QCR Quick Call to Regular Call QCR_iiiixxQENT Quick Entry QENT
RCE Rapid Call Entry RCE_uuuuuu_incident type,plate,state; location/cross;description

RCF Rolodex Card File RCF

RES Resend dispatch info to mobile unit(s) RES_uuuuuu

ROA Roll Additional Unit Column ROA_uuuuuuROI Roll Incident Column ROI_uuuuuuROL Roll Monitors (all columns) ROL_uuuuuuROM Roll One Page ROMROM T Reposition to top ROM_TROQ Roll Call Queue ROQ_uuuuuuROU Roll Units ROU_uuuuuuRRC Reroute, Clear RRC_uuuuuu_iiiixxRRN Reroute, No Clear RRN_uuuuuu_iiiixxSHD Call Scheduling SHDSHM Scheduled Messages SHMSND Send Message SND_ori_message (or) SND_signon_messageSRI Special Response Info SRI_incident typeSTK Stack Unit STK_uuuuuu

TIM Reset Unit Timer TIM_uuuuuu_minutes (temporary override for uncheck in timers)

TOGM Toggle MonitorUAP Unit Available UAP_uuuuuu

UBP Admin Out of Service UBP_uuuuuu_location (court day, warrant pickupTransport, etc.)

UCI Unit Check In UCI_iiiixx

UCP Unit Check In UCP_uuuuuu_(disposition if desired. Use ? to briup table)

UNT Unit Notes UNT uuuuuu,uuuuuu_notesUOP Repair Out of Service UOP_uuuuuu_location

URA Unit Reassignment URA_uuuu01_ uuuu02 (changes ownership of thincident for reporting purposes)

URI Unit Radio Log Inquiry URI_uuuuuu

URP Report Writing/ Admin Status URP_uuuuuu_location (what most agencies use lunches, walk thrus, etc.)

USP Secondary Location USP_uuuuuu_location (changes loc. without changing status)



137


Fire

Ala

MDT

TDD

Wre

UD

Co

Function Keys

WCC Caller/ Complainant WCC_iiiixx_caller/complainant Commands

IND Dispatch Units IND iiiixxINS In Station INS MOV Move Up MOV uuuuuu iiiixx stationMV2 Move Up 2 MV2 uuuuuu iiiixx stationSBY Stand By SBY uuuuuuSRN Run Card Narrative SRN iiiixx

rmsALI Alarm Inquiry ALIALP Alarm Location Name ALP panel#

ASG Assign Unit to Incident ASG uuuuuu iiiixx grpMDT Send MDT Message MDT

TDD Send TDD Message TDD textcker Rotation

AMB Rotate Ambulances AMB iiiixx typeROT Rotate Wreckers ROT iiiixx type

Function Key Purpose

F1 Help Text. Position your cursor in any given field and press this key to display information pertaining to that field’s purpose and usage.

F2 Global Name Search. Use this key to access the Global Name Search screen and view jacket information. You cannot, however, create a jacket via this function.

F3 Exit.F4 Prompt.F5 Clears the Call Screen; refreshes most other screens; returns the cursor to the home position. F6 Toggle Call QueueF7 Displays incident Hazards; brings the incident up on the screen. F8 Extended Unit Status Display.F9 Displays Next Undispatched Incident. F10 Unit Recommendation.



138

Function Keys

F11Cleared Incident File. Use this function key if you need to dispatch a unit to an incident that has already been cleared. It also allows you to view Dispatch and Unit times for previous incidents and add supplemental narratives.

F12 E911 Call Display. When an E911 call comes in, simply press <F12> to bring the call information up on the screen. If there is more than one E911 call that has not been worked with, you will see a yellow square containing the letter “E” at the top of the page.

F13 Places Call On Hold. Once a call has been placed on hold, a yellow square containing the letter “H” will appear at the top of the page.

F14Takes Call Off Hold. If there is only one call on hold, the call information will appear in the dispatch entry area. If there is more than one call on hold, you will be taken to the Work with Calls On Hold screen.

F15 CAD Control Screen. This screen allows you to change the type of monitor that you are using, the shift that you are working, and the ID# of the person using the workstation.

F16This key takes you to the Work With Cleared Quick Calls window. From this window, you can perform maintenance on cleared Quick Calls and create Regular Calls from cleared Quick Calls.

F17 Clears Command Line. F18 Retrieves Previous Commands.

F19 Work With House Watches. From here you can create and perform maintenance on House Watches.

F20Arrive Unit at Scene. Once you have an incident up on the screen in either inquiry or change mode, type the unit# on the command line and press <F22>. Or you can simply type unit# followed by the incident# and press <F22>.

F21 Same as F9 but in Inquiry.

F22 Dispatches a Unit. Once you have the incident up in inquiry or change mode, type the unit# on the command line & press <F22>. Or you can simply type unit#_incident# & then press <F22>.

F23 Use With Fire Run Card.

F24Narrative Window. To access the narrative window you can either type the incident# & press <F24> or you can have the incident up on the screen in inquiry or change mode and then press <F24>.

Function Key Purpose

139


140

IndexIndex

A

AA2 ................................................29AAP ................................................30Add Name to Narrative .....................86Add Narrative ...................................31ADN ................................................31ADS ................................................32Alarm Panel Inquiry .........................34Alarms Inquiry .................................33ALI .................................................33ALP .................................................34AMB .............................................109Arrive Scene ....................................65Arrive Unit .......................................37AS2 .................................................65ASG ................................................35ASP .................................................37Assign Incident for PACE Operators ..95Assign Unit to Incident .....................35Assist ...............................................32At Scene2, Available ........................29

B

Be On Lookout Crimes .....................43Be on Lookout Miscellaneous ............39Be on Lookout Outside Alert .............41Be on Lookout Wanted Persons .........48Be on Lookout, Vehicles ...................46Beat Recommendation ......................38BET .................................................38BOL C .............................................43BOL M ............................................39BOL O .............................................41BOL V .............................................46BOL W ............................................48

Briefing Notes Maintenance ..............39Building GEO/Location Records .........7

C

Call Queue .......................................26Call Scheduling ..............................112Caller / Complainant .......................133CAP ................................................50Card File Maintenance ....................103Case Number Assignment .................62CCP ................................................52CDA ................................................53Change Current Station Assignment ..54Change Dispatch Assignment ............53Change Dispatchers ID# ...................56Change Monitor Type .......................61Change Unit Assignment ..................55CHS ................................................54CHU ................................................55CID .................................................56CIF ..................................................57CLA ................................................58Clear a Unit from an Incident ............50Clear All Assigned ...........................58Clear Incident Flag ...........................57Cleared Incident Prompt ...................80Clearing an Incident .........................52CLP .................................................59CMT ...............................................61CNA ................................................62Command Line .................................23Computer Aided Dispatch Main Menu .1Copy Incident ...................................63CP1 .................................................63CP2 .................................................63

141

D

Depart Scene ....................................65Dispatch ...........................................64Dispatch Entry Screen .......................23Dispatcher Functions ..........................1Display Unit Equipment ....................68DS1 .................................................65DS2 .................................................65DSP .................................................64

E

ENR ................................................67Enrouting .........................................67Enter/Change License Plate ...............59EQP .................................................68Equipment .......................................68Event ...............................................70EVT ................................................70EX2 .................................................74EXC ................................................74Executing CAD Commands ..............26Extended Unit Status Display ..............2

G

GEO ................................................75GEO Prompt ....................................75GEO Verification .............................27

H

Hazard .............................................76Hazard Display .................................76Hazard Inquiry .................................77House Watches ...................................5HZD ................................................76HZI .................................................77

I

INC .................................................78Incident Change ...............................78

Incident Entry Area ..........................24Incident Inquiry ................................79Incident Narrative Entry ....................89INQ .................................................79

L

Link Incidents ..................................80LNK ................................................80

M

Mileage ...........................................81MLG ...............................................81Monitor Commands ..........................83MOV ...............................................84MOV or MV2 ..................................84Move ...............................................84Move-up2 ........................................85MV2 ................................................85

N

NAM ...............................................86NAR ................................................87Narrative ....................................87, 89NOT ................................................88Note ................................................88NRW ...............................................89

O

Off Shift ..........................................91OFS .................................................91On Duty ...........................................92On Shift ...........................................94OND ...............................................92ONS ................................................94Outside Alerts Maintenance ..............41

P

PAC ................................................95PAG ................................................96

142

Page ................................................96Person/Property Crimes Maintenance 44,

45Plate Maintenance ............................59PLT .................................................97Police Recommendations ..................38PRC .................................................98Print Rip and Run .............................98

Q

QCE ................................................99QCR ..............................................101QENT ............................................102Quick Call Entry ...............................99Quick Call Entry Prompt ...................99Quick Call to Regular Call ..............101Quick Entry ....................................102

R

Radio Log Inquiry ..........................101Rapid Call Entry .............................105Rapid Call Entry Prompt .................105RCE ..............................................105RCF ...............................................103RCMD ...........................................106Recommending Units ......................106Reprint Rip & Run ..........................108Reroute, Clear ................................110Reroute, No Clear ...........................111RES ...............................................107Resend Dispatch Information to Mobile

Units ........................................107RIP ................................................108ROA ................................................83ROL ................................................83Rolodex Card File ...........................103ROQ ................................................83ROT ..............................................109ROU ................................................83RRC ..............................................110

RRN ..............................................111Run License Plate Locally .................97

S

Scheduled Message Maintenance .....116Scheduled Messages .......................115Secondary Location ........................132Send Message ..........................93, 119SHD ..............................................112SHM .............................................115Skills .............................................118SKL ..............................................118SND ..............................................119Special Response Information .........120SRI ................................................120Street Prompt ...................................75Suspect Maintenance ........................45

T

TIM ...............................................122Time in Minutes .............................122

U

UAP ..............................................123UBP ..............................................124UCI ...............................................125UCP ..............................................126Unit Assignments Maintenance ...55, 94Unit Available ................................123Unit Available at Scene .....................30Unit Check In .........................125, 126Unit Equipment Subset .....................69Unit Exchange ..................................74Unit Mileage Maintenance ................81Unit Out of Service .........................124Unit Out of Service for Repair .........127Unit Radio Log Inquiry ...................129Unit Reassignment .........................128Unit Report Writing ........................131

143

UOP ..............................................127URA ..............................................128URI ...............................................129URP ..............................................131USP ...............................................132

V

Vehicle Maintenance ........................47

W

Wanted/Missing Persons Maintenance 49

WCC .............................................133Work with Card File .......................103Work with Card File Contacts .........104Work with Cleared Calls ...................50Work with Personnel Status ..............92Work with Plates ..............................59Work with Scheduled Calls .............112Work with Scheduled Messages ......115Work with Unit Mileage ...................81Work with Vehicles ..........................46Work with Wanted/Missing Persons ..48Wrecker & Ambulance Rotation ......109

144