visioncad interfaces guide

VisionCAD™ Interfaces Guide Version 3.7

VisionCAD

Copyright © 2013 TriTech Software Systems

This documentation refers to version 3.7 of VisionCAD™, and was revised on 05/30/2013.

TriTech-Castle Hayne Offices are located at: 5601 Barbados Blvd. Castle Hayne, NC 28429 800-987-0911, FAX 910-602-6190 Our web site is located at: www.tritech.com

All Rights Reserved VisionCAD™ for Windows and the VisionCAD™ Interfaces Guide are protected by copyright and all rights are reserved. Reproduction or transmission in any manner is strictly forbidden without the prior written permission of TriTech Software Systems. This document refers to numerous products by their trade names. All designations are trademarks or registered trademarks of their respective companies. All of the product information contained in this document was carefully prepared based on the latest information available, and was believed to be correct at the time of printing. However, this publication could include technical inaccuracies or typographical errors. TriTech Software Systems cannot be held liable for direct, indirect, special, incidental, or consequential damages resulting from any inadvertent omissions or errors in both the software and manual.

http://www.tritech.com/

VisionCAD™ Interfaces Guide

Table of Contents

Page 1

TABLE OF CONTENTS VisionCAD ................................................................................................................. iii

Copyright ................................................................................................................... iii

CHAPTER 1. OVERVIEW ...................................................... 9

CHAPTER 2. USING MOBILE INTERFACES ............................ 11

Overview ...................................................................................................................... 11

Configuring CAD to Use Mobile Communications .................................................... 12 Both VisionMOBILE and Third-Party Configuration ................................................... 12 VisionMOBILE Only .................................................................................................. 13 Third-Party Mobile Only ............................................................................................ 13

Using CAD with VisionMOBILE .................................................................................. 14 Dispatching a Call to a VisionMOBILE Unit ............................................................... 17 Fields Transferred from VisionCAD and VisionMOBILE ............................................ 19

Fields sent from CAD Dispatch to VisionMOBILE ................................................ 19 Fields sent from a VisionMOBILE Officer Initiated Call to CAD ............................ 20

Chat .............................................................................................................................. 21

Message Center ........................................................................................................... 22 Message Center Command Line .............................................................................. 25

Query ........................................................................................................................... 26 Viewing NCIC Results in VisionCAD ......................................................................... 29

Status ........................................................................................................................... 30

Emergency Messages from VisionMOBILE ............................................................... 32

CHAPTER 3. USING MAPS ................................................. 33

Overview ...................................................................................................................... 33

Plot a Call ..................................................................................................................... 34

Plotting Wireless Calls ................................................................................................ 35

Add a Call from the Map ............................................................................................. 35


Table of Contents

Page 2

CHAPTER 4. USING RMS AND FIRE WITH CAD..................... 37

Overview ...................................................................................................................... 37 RMS ......................................................................................................................... 37 Fire 3.x ..................................................................................................................... 37 Fire 5.x ..................................................................................................................... 38

Setting up CAD to Use RMS, Fire ............................................................................... 38 CAD Configuration .................................................................................................... 45 Departments ............................................................................................................. 46 Rights ....................................................................................................................... 46

Setting up RMS or Fire to Receive CAD Data ............................................................ 46

Transferring Call Data to RMS .................................................................................... 47 RMS Auto-Create Incident ........................................................................................ 48 OCA Failover: CAD to RMS/FIRE Interface .............................................................. 49 Clearing a CAD Call.................................................................................................. 50 Assigning an OCA Number to a Call ......................................................................... 52 Assigning an RMS OCA Number to a Call ................................................................ 53 The Data in RMS ...................................................................................................... 55 Options to Transfer to Incident .................................................................................. 58

Case Only ............................................................................................................ 58 Incident w/ Upload Files for Person and Vehicle .................................................. 58 Incident w/ Person and Vehicle as Narrative ........................................................ 58 Log w/ Person and Vehicle................................................................................... 59

Fields Transferred from CAD to RMS ....................................................................... 59 RMS Incident Fields Transferred from CAD ......................................................... 59 RMS Log Fields Transferred from CAD ................................................................ 60

Searching and Viewing Information in RMS .............................................................. 61 Accessing the RMS Search Function ........................................................................ 62 Search for Person ..................................................................................................... 63 Viewing Outstanding Warrants and Civil Papers ....................................................... 65

Marking a Warrant Served in RMS ....................................................................... 68 Viewing Criminal History ........................................................................................... 70 Search for a Vehicle ................................................................................................. 72 Add CAD Subject or Vehicle from RMS Search Results ........................................... 75

Using CAD with VisionFIRE 3.x .................................................................................. 75 CAD FIRE 3.x Dispatch ............................................................................................ 76 CAD Access to FIRE 3.x Management System ........................................................ 76 CAD FIRE 3.x Configuration Option .......................................................................... 77 Setting up OCA Number Control ............................................................................... 77 Transferring Call Data to FIRE 3.x ............................................................................ 78 Transferring Fire Plans to CAD ................................................................................. 78 Showing Fire’s Closest Hydrants in CAD .................................................................. 80 FIRE 3.x Incident Fields Transferred from CAD ........................................................ 80

NIFRS-1 (Basic) ................................................................................................... 80 Apparatus/Resource/Personnel Forms ................................................................ 81


Table of Contents

Page 3

Using CAD with Fire 5.x .............................................................................................. 81 FIRE 5.x: Fire Plan Query ........................................................................................ 82

Installing the Fire Plan Query Interface ................................................................ 82 Configuring the Fire Plan Query Interface ............................................................ 86 Using the Fire Plan Query Interface ..................................................................... 86

FIRE 5.x: OCA Export .............................................................................................. 93 Configuring the OCA Export Interface .................................................................. 93 OCA Export Process ............................................................................................ 94

CHAPTER 5. USING CAD INTERFACES ................................ 99

Overview ...................................................................................................................... 99

Inform RMS and VisionFIRE Interfaces ................................................................... 100

Inform Jail and Inform FBR Interfaces (Using the Data Store) ............................... 100

Mapping Interfaces .................................................................................................... 101

NCIC Interface ........................................................................................................... 101

Third-Party RMS or Fire Interface ............................................................................ 101 File Export .............................................................................................................. 103 Export Enhancements ............................................................................................ 104 ASCII Text .............................................................................................................. 105

RMS - Main ........................................................................................................ 105 Units .................................................................................................................. 106 Person ............................................................................................................... 106 Vehicle ............................................................................................................... 107 Locations ........................................................................................................... 107

XML Text ................................................................................................................ 107 Element Structure .............................................................................................. 107 Fields Exported .................................................................................................. 108

ACS FIREHOUSE Query Interface ............................................................................ 114 FIREHOUSE Configuration Utility ........................................................................... 114 Using the FIREHOUSE Interface ............................................................................ 117

ACS FIREHOUSE Search ................................................................................. 117 Viewing Fire Plans from FIREHOUSE ................................................................ 121 FIREHOUSE Connection Failure ....................................................................... 123

Alarm Interface .......................................................................................................... 123 Set up ..................................................................................................................... 124

Set Port .............................................................................................................. 124 General Edit ........................................................................................................... 126

Complaint Types ................................................................................................ 126 Internal ALI ........................................................................................................ 126

CryWolf Interface ...................................................................................................... 126 Installing the CryWolf Interface ............................................................................... 127 Configuring the CryWolf Interface ........................................................................... 131


Table of Contents

Page 4

Using the CryWolf Interface .................................................................................... 136 VisionCAD Fields Updated from CryWolf ........................................................... 137

Monitoring the CryWolf Interface............................................................................. 139 Filtering the Monitor ........................................................................................... 142 Exception Data Messages and Troubleshooting ................................................ 142

HigherGround Logging Recorder Interface ............................................................. 144 Installing the HigherGround Logging Recorder Interface ........................................ 144 Configuring the HigherGround Logging Recorder Interface .................................... 149 Using the HigherGround Logging Recorder Interface ............................................. 153

Message Workflow ............................................................................................. 153 Monitoring the HigherGround Logging Recorder Interface ...................................... 154

Filtering the Monitor ........................................................................................... 157 Deccan LiveMUM Interface ....................................................................................... 158

Installing the Deccan LiveMUM Interface ................................................................ 158 Configuring the Deccan LiveMUM Interface ............................................................ 163 Using the Deccan LiveMUM Interface ..................................................................... 166

Deccan LiveMUM Exchange Details .................................................................. 167 Monitoring the Deccan LiveMUM Interface ............................................................. 167

Filtering the Monitor ........................................................................................... 169 Paging Interface ........................................................................................................ 170

Configuring the Paging Interface from VisionCAD .................................................. 171 Configuring the Paging Interface from PageGate ............................................... 173

Sending Calls to Units’ Pagers ............................................................................... 184 The EMD, EPD, EFD Interface ................................................................................... 184

Printrak CAD Interface .............................................................................................. 185 Record Types ......................................................................................................... 185

Event Records ................................................................................................... 185 Audit Records .................................................................................................... 185

Customer Requirements ......................................................................................... 185 File Locations ......................................................................................................... 186 Interface Installation................................................................................................ 187 Configuration .......................................................................................................... 187

Interface Configuration ....................................................................................... 187 VisionCAD Configuration ................................................................................... 188

VisionCAD Tear and Go Printing .............................................................................. 190

GTE Fire Printer Interface ......................................................................................... 192

Fire Toning - Zetron Interface ................................................................................... 196 Zetron Model 25 ..................................................................................................... 196

Set Up ................................................................................................................ 197 Zetron 25 Interface Window ............................................................................... 200

Zetron Model 26 ..................................................................................................... 200 Set Up ................................................................................................................ 201 Zetron 26 Interface Window ............................................................................... 204 Diagnostic Messages and Troubleshooting ........................................................ 205


Table of Contents

Page 5

CHAPTER 6. PROQA INTERFACE ....................................... 209

The EMD, EPD, EFD Interface (ProQA) .................................................................... 209

ProQA Interface Enhancements ............................................................................... 212 Case Entry .............................................................................................................. 213 Key Questions ........................................................................................................ 213 Additional Information ............................................................................................. 214 Dispatch or Reconfigure ......................................................................................... 215 Urgent Message ..................................................................................................... 218 Aborted Case ......................................................................................................... 218 Completed or Pending Case ................................................................................... 218 ProQA Police and Fire ............................................................................................ 219 Call Handler Commands ......................................................................................... 221 CAD Call Complaint Updates .................................................................................. 222 Multiple Cases on One Call .................................................................................... 224 Multiple Discipline Launcher ................................................................................... 225 Split Call Operation ................................................................................................. 228 Narrative Examples ................................................................................................ 231

Medical Narrative ............................................................................................... 231 Police Narrative .................................................................................................. 232

VisionCAD/ProQA Interface Settings ....................................................................... 233

CHAPTER 7. APCO MEDS INTERFACE ................................ 239

The EMD, EPD, EFD Interface (APCO MEDS) .......................................................... 239 Case Questions in APCO MEDS ............................................................................ 240 Horizontal Dispatch (APCO MEDS) ........................................................................ 241 APCO MEDS Medical, Police, and Fire .................................................................. 242 Call Handler Commands with APCO MEDS ........................................................... 244 CAD Call Complaint Updates from APCO MEDS ................................................... 245 Split Call Operation with APCO MEDS ................................................................... 248 APCO MEDS Narrative Example ............................................................................ 250 APCO MEDS Interface Messages .......................................................................... 251

VisionCAD/APCO MEDS Interface Settings ............................................................. 252

APPENDIX A. NCIC QUERIES ............................................ 259

Overview .................................................................................................................... 259 VisionMOBILE Window for NCIC Queries ............................................................... 259 Query Results ......................................................................................................... 260 Generic and State-Specific Queries ........................................................................ 261 User Rights ............................................................................................................. 261

Sending Generic Queries .......................................................................................... 261


Table of Contents

Page 6

Sending a Person Query ........................................................................................ 263 Sending a Vehicle Query ........................................................................................ 264 Sending an Article Query ........................................................................................ 266 Sending a Gun Query ............................................................................................. 268 Sending a Free-Form Text Query ........................................................................... 269 Sending an Image Query ........................................................................................ 270

Viewing Query Returns ............................................................................................. 271 Viewing Images ...................................................................................................... 273

California – LA County .............................................................................................. 274 The Vehicle Tab ..................................................................................................... 274 The Property Tab .................................................................................................... 275 The Gun Tab .......................................................................................................... 275 The Bicycle Tab ...................................................................................................... 276 The JAI Tab ............................................................................................................ 276 The Driver History Tab ............................................................................................ 277 The CCHRS Tab .................................................................................................... 277 The WANT9 Tab ..................................................................................................... 278 The Query Tab ....................................................................................................... 278

Minnesota .................................................................................................................. 279 Returns ................................................................................................................... 279 The Vehicle Tab ..................................................................................................... 279 The History Tab ...................................................................................................... 279 The QD Tab ............................................................................................................ 280 The Free Tab .......................................................................................................... 280

North Carolina ........................................................................................................... 280 Returns ................................................................................................................... 280 The Vehicle/Part/Plate Tab ..................................................................................... 281 The Drivers Tab ...................................................................................................... 282 The Boat Tab .......................................................................................................... 282 The Securities Tab ................................................................................................. 283 The Articles Tab ..................................................................................................... 283 The Gun Tab .......................................................................................................... 284 The Wanted/Missing Persons Tab .......................................................................... 284 The Missing Persons (Only) Tab............................................................................. 285 The NLETS Hazardous Material Tab ...................................................................... 285 The Free Tab .......................................................................................................... 286 The AOC for Criminal Defendant Name (ACD Tab) ................................................ 286 The AOC for Criminal Individual Record (ACI Tab) ................................................. 287 The AOC for Criminal Court Record (ACR Tab) ...................................................... 287 The AOC for Defendant and Witness Court Schedule (ACS Tab) ........................... 288

Virginia ....................................................................................................................... 288 Returns ................................................................................................................... 288 Required Fields for a Query .................................................................................... 288

QW1 Query Wanted Persons ............................................................................. 288 QV Query Vehicle .............................................................................................. 289 QVN Query vehicle registration by Name ........................................................... 289


Table of Contents

Page 7

QD Query Driver ................................................................................................ 289 QT Query Driver Transcript ................................................................................ 290 QH Query Criminal History ................................................................................. 290 QR Query Criminal Record ................................................................................ 291 RQ Query Out of State Vehicle .......................................................................... 292 QG Query Gun ................................................................................................... 292 QA Query Article ................................................................................................ 292 DQ Query Out of State Driver ............................................................................ 292

The License Tab ..................................................................................................... 293 The Wanted Tab ..................................................................................................... 294 The C.H.-C.R. Tab .................................................................................................. 294 The Article Tab ....................................................................................................... 295 The Driver Tab ........................................................................................................ 295 The Free Form Tab ................................................................................................ 296

GLOSSARY ..................................................................... 297

INDEX ........................................................................... 305


Chapter 1. Overview

Page 9

CHAPTER 1. OVERVIEW Welcome to TriTech's feature-rich computer-aided dispatch system: VisionCAD. This book explains VisionCAD’s relationship to other TriTech products as well as several useful third-party applications.

VisionCAD interfaces with other TriTech products, such as VisionMOBILE, Inform RMS and VisionFIRE, as well as many third-party applications, such as Zetron Fire Toning. Integration with GeoComm’s GeoLynx 9-1-1 mapping allows call and unit locations to be displayed on a map. Message Switch technology provides integration with VisionMOBILE, allowing voiceless dispatching and automatic status updates. Call information can automatically be transferred and used to initiate cases in Inform RMS and incidents in VisionFIRE.

Some interfaces covered in this book relate only to system administrators. The relationship will not be visible to dispatchers, nor will it interfere with their normal routines. Other interfaces relate directly to dispatch functions. For these latter interfaces, this book provides more detail than the brief mention given in the VisionCAD Telecommunicator User’s Guide and should be used in conjunction with the information in that manual. System Administrator functions are covered in the VisionCAD System Administrator User’s Guide.

System Administrator and Telecommunicator functions are covered in this book only as they relate to other products. This manual assumes a basic working knowledge of Windows and VisionCAD. A brief sketch of other TriTech products is provided as each product relates to CAD. Refer to the documentation for the secondary (non-VisionCAD) application or product for details on that side of the interface.

This book is organized into chapters by product groups in order of integration with CAD. That is, the earliest chapters cover those products, such as VisionMOBILE and TriTech’s mapping products, that are integral to VisionCAD dispatch functionality. The table of contents and the index provide quick reference to locate information.


Chapter 2. Using Mobile Interfaces

Page 11

CHAPTER 2. USING MOBILE

INTERFACES

Overview

CAD is designed to work with a mobile interface such as VisionMOBILE or other third-party mobile dispatching applications. All information sent to and from a mobile unit first goes through a message switch – either the VisionMOBILE Message Switch or a third-party message switch.

TriTech’s VisionMOBILE interfaces with VisionCAD. (Please refer to the VisionMOBILE Client User’s Guide for further details on using this application on the mobile laptop.) Third-party interfaces should be installed on your CAD server. For instructions on using these products, please consult the individual product’s documentation.

This chapter provides information on setting up a mobile interface for CAD and provides brief descriptions on how to complete operations with VisionMOBILE; for instance, how to dispatch calls to mobile units and how to send and receive messages between VisionMOBILE and your agency’s CAD Dispatch center.

The term “MCT” is used in this chapter to refer to mobile unit terminals, such as laptop computers. Although a mobile unit may use an MDT (mobile data terminal), in this chapter, MCT (mobile communications terminal) is used throughout for the purpose of simplicity. For VisionMOBILE, the application installed on a MCT is called VisionMOBILE Client.

Note: For third-party mobile interfaces, TriTech provides only the basic functions for them to interface with VisionCAD and other TriTech products. This chapter does not cover these non-supported interfaces. TriTech supports applications that interface directly with TriTech’s applications, such as VisionMOBILE. TriTech does not provide interfaces to state or local databases or third-party applications unless specifically stated within a legal contract.



Page 12

Configuring CAD to Use Mobile Communications

Before you can communicate from a CAD dispatch workstation to a mobile unit, you must configure CAD for the mobile interface. Depending on whether your installation is using TriTech’s VisionMOBILE or a third-party message switch application and mobile application, you must set different configuration options.

The Message Switch category of CAD Configuration contains options that affect how Mobile Computer Terminals (MCTs) interact with the CAD system at your installation and the state-specific National Crime Information Center (NCIC) interface. The options that allow you to select whether dispatchers are warned or need to acknowledge certain MCT-initiated actions are not listed here; only the essential options to set up communications with mobile units. Refer to the VisionCAD System Administrator User’s Guide for more details on all MCT Warn configuration options.

The following sections describe the settings that must be configured in the Message Switch category in CAD Configuration in order for CAD to communicate with a mobile interface.

Both VisionMOBILE and Third-Party Configuration Set the following options in the Message Switch category of CAD Configuration if your installation is using either VisionMOBILE or a third-party mobile system.

Option Value

MCT Status Window Indicate how you want MCT messages to display in CAD:

• Yes – Display MCT messages from the Status tab in the MCT window.

• No – Display MCT messages in pop-up boxes for every status change.

MCT Type Select Yes or No for the type of Message Switch: YES for a VisionMOBILE Message Switch or NO for a Third-party message switch.

MSGSW in Use Set this option to Yes to allow mobile units to communicate with CAD from the field. This option turns the interface on, making the VisionMOBILE window display in the CAD Dispatch module.



Page 13

Option Value

NCIC Auto Plate Set this option to Yes if you want an inquiry sent to NCIC automatically when a Traffic Stop is added. License plate and state information is sent to the state NCIC interface.

VisionMOBILE Only You must set up VisionCAD to communicate with the Message Switch, mobile clients, and the state-specific National Crime Information Center (NCIC). In the Local Configuration File menu, there is an MSG option to run the Mobile configuration utility. You must run this utility to configure the CAD workstation to connect to the Message Switch over a TCP/IP communications link. Instructions to set up the workstation are contained in the VisionCAD System Administrator User’s Guide in the Configuration chapter. The user also needs to be granted the CJIS Query user right in VisionMOBILE Message Switch Configuration. Instructions for setting up the Message Switch and Mobile Clients are contained in the VisionMOBILE documentation.

Third-Party Mobile Only Any third-party mobile interface that is to be used with CAD must be installed and started on a server, in addition to Windows Message Server. If the Message Server and the Mobile application are not running on the CAD server, mobile communications are not possible.

If your installation is using a third-party mobile system, set up the additional configuration option below, in addition to the ones from the table provided above.

Option Value

MCT Position Number Enter the computer ID on which the message switch software is installed.



Page 14

Using CAD with VisionMOBILE

After the TCP/IP connection is configured for the CAD workstation and Message Switch, the CAD Dispatch station will display a Message Switch login window and the Mobile window as shown below. Each telecommunicator is given a login password (a user ID and password is set up on the Message Switch), which logs the user into the Message Switch.

Note: The user ID on the Message Switch must match exactly the VisionCAD login name for each user.

Once logged in, the CAD Dispatch application will display the Mobile window. It can be minimized and re-displayed by clicking on the MCT button on the Main Dispatch toolbar.



Page 15

The MCT window provides access through the Message Switch to mobile communications terminals (MCT) and to any state or federal crime database set up on the Message Switch.

The following table describes the tabs of the CAD Mobile window.

Note: Only those applications set up in the MSG configuration utility will display in the CAD MCT window.

Field Description

Log On Click Logon to log onto the Message Switch. This step is necessary to communicate with mobile units and to run NCIC queries. The Logon window will display for you to enter your password.

Log Off Click Logoff to log off of the Message Switch.

Chat With the Chat function, you can communicate in real-time with VisionMOBILE users and also other VisionCAD users. The chat function allows you to send a message from your workstation to any one else logged on to the Message Switch with Chat enabled. This is similar to a conference call where everyone hears what everyone else is saying.

Msg Ctr (Message Center)

Message Center provides communication between VisionCAD and VisionMOBILE users.

There are two ways to communicate with other users in Message Center:

• Messages can only be sent to a user who is currently logged into the VisionMOBILE Message Switch.

• Notes can be sent to any user who is set up on the Message Switch, whether or not that user is logged in. If a note is sent to a user who is not currently logged into the Message Switch, the system will hold the note and deliver it the next time the user logs into the system.

Note: Message Center is only available if you are interfacing with VisionMOBILE 3.0 or higher. If your agency runs an earlier version of VisionMOBILE, you must use the Chat feature to communicate with Mobile units.

Query (Generic) Click on this tab to display the NCIC Query window to enter a query to the federal crime information database system. Clicking on this button displays the generic Query screen (for



Page 16

Field Description states other than CA, MN, NC, VA), where you can select one of the following queries:

• Personal

• Vehicle

• Article

• Gun

• Free-Form

• Image

Note: If the Query fields do not display at the top of the window, double-click the mouse pointer in the large blank section of the window. This action will display the fields.

Query/State Interface (CA, MN, NC, VA)

Click on the state-specific tab to display the Query tabs to enter a query to the state or federal crime information database system. States that have a state-specific Query screen in CAD are: CA, MN, NC, and VA. Refer to the State-Specific Crime Interfaces portion of Appendix A in this book for specific instructions on using these tabs.

Returns: The Returns contains the results from the CAD Dispatcher’s and the mobile units’ NCIC queries.

Status The Status tab displays messages sent from mobile units. However, if the CAD Configuration option MCT Status Window is set to No, mobile messages will display in pop-up boxes for every status change instead of in the Mobile window Status tab.

Refer to the appropriate sections in this chapter for more details of each feature available in the CAD MCT window.



Page 17

Dispatching a Call to a VisionMOBILE Unit The CAD Dispatcher can dispatch a VisionMOBILE unit the same as dispatching any non-mobile unit. The example below shows that Mobile Unit KMOB is dispatched to call #051603-0025.



Page 18

When a CAD dispatcher dispatches a mobile unit to a call, the Dispatch button in the VisionMOBILE terminal lights up, as shown below in VisionMOBILE.



Page 19

The Mobile officer can click on the Dispatch button to display the call information, as shown below.

If there are alerts or warrants associated with the call, these buttons light up.

Note: If a call is updated in CAD through the Edit Call window, the dispatcher must click the Save button to transmit the changes to Mobile units.

Fields Transferred from VisionCAD and VisionMOBILE Fields are transferred between VisionMOBILE and VisionCAD in many different ways. Listed below are the two main transfers: Dispatching a call from CAD to Mobile, and an officer self-initiating a call from Mobile to CAD. The lists under the headings show the fields that are sent.

Fields sent from CAD Dispatch to VisionMOBILE Call Number Location City Complaint Apt Floor



Page 20

Caller Name Phone Injuries Weapons Narrative Directions Cross Streets Alerts Time Latitude Longitude Subject Subject Statistics Vehicle BOLO

Fields sent from a VisionMOBILE Officer Initiated Call to CAD Complaint Type Location Apartment Floor City Tag Color DOB Ethnic Height OLN Race Sex State Tag State Tag Type Vehicle Owner Vehicle State Vehicle Year VIN Weapons Weight Age



Page 21

Chat

With the Chat function, you can communicate in real-time with VisionMOBILE users and also other VisionCAD users. The chat function allows you to send a message from your workstation to any one else logged on to the Message Switch with Chat enabled. This is similar to a conference call where everyone hears what everyone else is saying.

Note: The Chat tab may not display in the MCT window. Your system administrator may choose to use the Message Center communication feature instead of Chat.

The following table describes the various portions of the Chat screen.

Field Description

(Outbound) Use the unlabelled field at the top of the Chat screen to enter a text message to send to another user or group of users.

Users The Users list on the right displays a list of all users in the current chat room. By default, this is the All Users room. To send a chat message to a single user, select that user from the list. You may select multiple users with the standard



Page 22

Field Description Windows Ctrl + click (for nonconsecutive users) and Shift + click (for consecutive users) key combinations.

Existing Rooms The Existing Rooms field displays a list of all currently active chat rooms. You can join a room by double-clicking the name in the list. The Users list will display all users in the room you selected, and the title of the Chat Room field will change to the new room.

Create Room Use this field to create a new chat room. Simply type the room name and hit enter on your keyboard. The new room will display in the Existing Rooms list.

Chat Room The large field on the left of the Chat screen displays all messages sent to you or to the chat room you are in. The title of this field reflects the current room. By default, this is the All Users room.

Each message is preceded by the user name of the sender and the time the message was sent. Messages sent directly to you by user name (rather than to the entire chat room) will be marked with an asterisk (*). To clear all messages from this field, double-click anywhere within the field.

To send a Chat message, complete the following steps.

Step 1. Select the desired recipients from the Users list. To send to an entire room, simply skip to step 2.

Step 2. In the outbound field, type the text of your message.

Step 3. Hit enter on your keyboard. The message is sent to the designated recipient(s) or to the entire chat room.

Message Center

Message Center provides communication between VisionCAD and VisionMOBILE users. There are two ways to communicate with other users in Message Center:




Page 23


Note: The Msg Ctr tab may not display in the MCT window. Your system administrator may choose to use the Chat communication feature instead of Message Center.

Note: Message Center is only available if you are interfacing with VisionMOBILE 3.0 or higher. If your agency runs an earlier version of VisionMOBILE, you must use the Chat feature to communicate with Mobile units.

Click the Msg Ctr tab in the CAD MCT window to display Message Center. The screen will display as below.

When users are created on the Message Switch, they are assigned to one or more groups, such as departments and shifts. These groups are crucial to the operation of the Message Center. You may send messages and notes to individuals or to groups.

Note: Only users with Supervisor or Administrator rights may send to an entire jurisdiction.



Page 24

The In Bound Messages field displays all message sent by and to you. Each message is preceded by the user name of the sender and the time the message was sent.

The Members field shows users assigned to the group selected in the Department field. Depending on the setting of the Message/Note toggle button, this may be a list of all users in the selected group or only those members currently online. To select recipients for a message or note, double-click the user name of each desired recipient from the Members list. To deselect a user, double-click the name again to remove the check mark.

The Department field shows all jurisdictions, departments, and sub-departments created on the Message Switch. To update this list as well as the list of users, right-click in the Department field. A pop up menu displays with the option “Update Configuration”. Click this menu item to update Message Center with the most current jurisdiction, department, and user information. You must perform this update each time the user list or department list is updated on the Message Switch. To send a message or note to a group, select that group from the list in the Department field.

Note: Only users with Supervisor or Administrator rights on the Message Switch can send to an entire jurisdiction.

Use the Out Bound field to enter the text of your message. Hit enter on your keyboard or click the Xmit button to send the message to the designated recipient(s).The Out Bound field will note the last user who sent a message to you.

After you enter the message text, hit the Reply button to reply to the sender noted in the Out Bound field. The message will go to that user regardless of any other selection.

The following buttons are available in the Message Center.

Button Description

Clear All The Clear All button erases all messages from the In Bound Messages field.

Clear Message This button will clear individual messages from the window. Simply highlight the message you want to delete and click the Clear Message button.

First Highlights the first message in the window.

Prev Highlights the previous message.



Page 25

Button Description

Next Highlights the next message.

Last Highlights the last message in the window.

Reply Use the Reply button to answer the last user who sent you a message or note. When you receive a message or note, the Out Bound field shows the sender with “(Reply:sender)”. Enter text in the Out Bound field and click the Reply button. The message will go to that user regardless of any other selection.

Note: Before using the Reply button, check if the user is logged in. The Reply button will respect the setting of the Message/Note toggle button. If the user is no longer on line, make sure to toggle to Note.

Msg / Note Toggle Use this button to toggle between Messages and Notes.



Print The Print button allows you to print all messages to your default printer.

Xmit The Xmit button sends the Note or Message you have composed to the designated recipient(s). This can also be accomplished by hitting enter on your keyboard while the cursor is in the Out Bound field.

Message Center Command Line There are three Command Line options available in the Message Center screen. To use a command, simply type it into the Out Bound field and either hit Enter on your keyboard or click the Xmit (Transmit) button. Commands will rely on the Message/Note toggle button.



Page 26

The following table explains the available commands.

Action Command

Send to Officer(s) O/officerid1, officerid2, officerid3,…/message text

Send to Unit(s) U/unitid1, unitid2, unitid3,…/message text

Send to Group(s) D/dept1, dept2, dept3,…/message text

To send to a group or department, you must enter the full path to that group starting with Jurisdiction. For example, to send to SHIFT A of DEPTB in JURISDICTIONC, you must list the department as “JURISDICTIONC.DEPTB.SHIFTA”.

Query

Note: This button will not display if you do not have the CJIS Query right checked in the VisionMOBILE Message Switch Configuration utility – VisionMOBILE versions 3.7 Update 3 or higher. (If you are using an earlier version of VisionMOBILE, then VisionCAD determines if you have access to NCIC queries based on Right 46: NCIC in the Front End Security module.)

Click on the Query or Generic Q tab to display the NCIC Query window to enter a query to the federal crime information database system. Clicking on this button displays the generic Query screen (for states other than CA, MN, NC, VA), where you can select one of the following queries:

• Personal

• Vehicle

• Article

• Gun

• Free-Form

• Image

Note: If the Query fields do not display at the top of the window, double-click the mouse pointer in the large blank section of the window. This action will display the fields.



Page 27

The following table explains the fields and buttons available in the Query screen.

Field/Button Description

Person For a generic query, click on Person to display the fields to send a query based on a person. Fill in the fields that display and click Send.

Vehicle For a generic query, click on Vehicle to display the fields to send a query based on a vehicle. Fill in the fields that display and click Send.

Article For a generic query, click on Article to display the fields to send a query based on an article. Fill in the fields that display and click Send.

Gun For a generic query, click on Gun to display the fields to send a query based on a gun. Fill in the fields that display and click Send.

Free Click on Free to enter a Free-Form query. Consult with your agency for specific requirements on the format of free-form queries.

Image Click on Image to send a query based on an image number. Fill in the field that displays and click Send.



Page 28

Field/Button Description

Send Click this button to send the entered query.

Clear Click Clear to remove the message(s) sent text displaying in the window.

Prev Click on Prev to display the previous Query return.

Delete Click on Delete to delete the displayed Query return.

Print Click on Print to print the displayed Query return. (You must have rights in CAD Front-End Security to use this function.)

Copy to Call Click the Copy to Call button to save selected text to the narrative of the currently highlighted call.

Note: All comments added to the narrative with this button will use the confidential setting for [EPD – Confidential Narrative] as if the data came from a police interface.

Next Click on Next to display the next Query return.

To send a query, complete the following steps.

Step 1. From the Query screen in the MCT window, click the button that corresponds to the type of query you wish to run.

Step 2. The query form changes to reflect your selection. Complete the appropriate fields.

Step 3. Check NCIC and/or RMS to designate the data source you wish to query.

Step 4. Click the Send button.



Page 29

Viewing NCIC Results in VisionCAD At the CAD workstation, VisionMOBILE NCIC Query results also display in the VisionCAD Mobile window as shown below.

To copy query returns to the relevant call, complete the following steps.

Step 1. With the call highlighted, select the text in the return that you want to copy to the call.

Step 2. Click the Copy to Call button.

Step 3. The text you selected will be saved to the narrative of the selected call as shown below. (Remember to save these narrative changes by clicking the Save button on the Edit Call window toolbar.)



Page 30

Refer to the section in this book, “NCIC Queries” for detailed information on using the NCIC interface with CAD.

Status

The Status tab displays messages sent from the Message Switch regarding mobile unit status. If the CAD Configuration option MCT Status Window is set to No, mobile messages will display in pop-up boxes for every status change instead of in the Mobile window Status tab.

The Status screen will also display message regarding your connection to the Message Switch. The following table describes some common status messages you may see in the Status field.

Message Description

Auto Time Out in X Minutes.

This warning appears based on the settings in Max Online Time and Cut Off Notice on the Security tab in VisionMOBILE Message Switch Configuration. This serves to warn you that your session on the Message Switch is about to time out. Complete any work in progress, log out of the Message Switch, and then log back in to reset your session timer.



Page 31

Message Description

User Dropped or System Restarted

This message appears any time communication with the Message Switch is lost. This may be due to a Message Switch restart, a session timeout as defined in the Max Online Time setting on the Security tab in VisionMOBILE Message Switch configuration, or an inactivity timeout as defined in the Time Out setting on the Vision tab in VisionMOBILE Message Switch configuration. Simply log in to the system again.

Password Expires in X Days Please Change Soon.

When you receive an expiration notice, click Log On to change your system password as soon as possible.

Password Expired. Please Change Immediately.

Click Log On to change your system password immediately.

Password Can not be changed at this time.

This message appears if you attempt to change your password earlier than allowed by the Frequency setting on the Security tab in VisionMOBILE Message Switch configuration. If your password must be changed to avoid a security breach, consult your system administrator to change the password on the Message Switch.

Invalid PWD Size must be between X and Y.

This message appears if your password exceeds the maximum or does not meet the minimum number of characters as defined in the Length settings on the Security tab in VisionMOBILE Message Switch configuration. Enter a new password of appropriate length as specified in this message.

Password has been used before.

This message appears if you attempt to use a password that has been used too recently as defined in the Reuse setting on the Security tab in VisionMOBILE Message Switch configuration. Enter a different password.



Page 32

Emergency Messages from VisionMOBILE

VisionMOBILE provides and Emergency button, which when selected sends an emergency alert to all currently logged on mobile and dispatch terminals depending upon the Message Switch Configuration settings.

For the VisionCAD clients receiving the emergency message, the mobile unit is highlighted in the All Units window and flashes red. Additionally, the mobile unit number flashes in red in the banner near the top of the window. Depending upon your VisionCAD configuration settings, the emergency message will automatically display or you may have to double-click on this flashing unit number to display the message.

If the mobile unit sending the emergency message is using AVL, then the window includes its GPS coordinates. Click on this information to display the location on a Google map.

Click on the flashing unit number to display a menu from which you can view the unit detail or unit department windows. To clear the message, select the Clear Unit option. (This action will add a TC Log Entry indicating when it was cleared. The unit will remain on this marquis banner for 5 more minutes.)


Chapter 3. Using Maps

Page 33

CHAPTER 3. USING MAPS

Overview

VisionCAD integrates seamlessly with GeoComm’s GeoLynx 9-1-1 mapping. You can plot calls on the map from within CAD, add new calls from the map, and assign units. The two products work even more closely together for wireless calls. When VisionCAD and GeoLynx are used together, they meet all standards of FCC Phase II for wireless calls.

The following configuration options must be set in the Map/GEO category in CAD Configuration to enable the interface between VisionCAD and GeoLynx.

Parameters Setting

Auto Map Set this option to Yes to plot a call location as soon as you click the New button to pull in data from the ALI stream. Set this option to No if you want to manually plot calls.

Map Station Position Enter the CAD workstation's position number (from the Position.ini file) to which map data should be sent. It does not have to be the CAD workstation where call data is entered; the CAD mapping data can be sent to that workstation or any other CAD workstation for plotting on the map. The valid range for this value is 1-299. The default is set to 15.

Mapping Enabled Set this option to Yes if your system is using GeoLynx; otherwise, set this option to No.

You must install GeoLynx and your agency’s map data files on each CAD workstation that will be using mapping with CAD. You must also install GeoRelay to enable communication between the two applications.

This chapter covers GeoLynx mapping only insofar as it directly relates to VisionCAD calls and units. For information on the full functionality of GeoLynx, refer to the documentation provided with that product.



Page 34

Plot a Call

To plot an existing CAD call to the map in GeoLynx, complete the following steps.

Step 1. In the All Calls window, select the call you want to display on the map.

Step 2. Click the Map button in the All Calls toolbar.

Step 3. CAD sends the call address to GeoLynx, which plots the call on the map.



Page 35

Plotting Wireless Calls

For Phase II compliancy, TriTech recommends enabling the Auto Map configuration option. This will plot a call as soon as the dispatcher clicks the New button to bring in data from the ALI stream. For wireless calls, CAD will send the X and Y coordinates from the ALI data to GeoLynx. The call will be plotted on the map based on X and Y coordinates rather than by any address contained in the ALI stream.

Note: A call will not be treated as a wireless call unless there is data in the ALI stream in the position defined for Class of Service AND this value matches one of the CAD Codes for Wireless COS Designator.

When the ALI feed is received at the CAD position, the New button in CAD dispatch turns red. The dispatcher presses the New button to populate a new call with the data from that stream. The New Call window opens, and the call is plotted on the map based on the X and Y coordinates contained in the ALI feed.

The call is displayed on the map. GeoLynx uses the X and Y coordinates to calculate the closest actual address and send that address back to CAD. The nearest address provided by GeoLynx is stored in the Call Narrative in CAD.

Note: Even if there is no street address contained in the ALI feed for a wireless call, GeoLynx will still display the call on the map and send the nearest address to CAD.

Note: If there is no address within 100 meters of the call latitude and longitude, no nearest address will be provided.

Add a Call from the Map

To add a call from the map, complete the following steps.

Step 1. Right click on the call location on the map.



Page 36

Step 2. From the flyout menu, select CAD Call for Service. The following window will display.

Step 3. Select Traffic Stop, Miscellaneous Call, or New Call. GeoLynx will send the location to VisionCAD and launch the appropriate add call window.

Note the location information in the call narrative.

Step 4. Complete the add call fields as described in the VisionCAD Telecommunicator User’s Guide.


Chapter 4. Using RMS and Fire with CAD

Page 37

CHAPTER 4. USING RMS

AND FIRE WITH CAD

Overview

CAD provides an interface to TriTech’s Records Management System (Inform RMS) and VisionFIRE software. Using this interface, you can create RMS cases and incident records, transfer vehicle and person information from CAD to RMS records, and view RMS civil papers, warrants, property, arrests, and citations (criminal history) from master indices. Information in the master indices may have been entered for RMS or Fire 3.x. This section refers to all master indices by “RMS,” whether they were entered in either of the records applications.

RMS The CAD to RMS interface allows you to:

• Create incidents in RMS from CAD calls using the CAD Incident button in RMS.

• Create read-only calls for services records in RMS to view the original CAD calls as they were during the time they were transferred from CAD.

• Search any RMS master index from CAD Dispatch.

Fire 3.x The CAD to Fire 3.x interface allows you to:

• Create incidents in Fire from CAD calls. If units are set up to match exactly, the Incident will include Apparatus and Crew information.

• Pull site plan summaries from VisionFIRE 3.x to VisionCAD.

• Pull data on the four closest water sources from VisionFIRE 3.x to VisionCAD using the Hydrants function.



Page 38

Fire 5.x The CAD to Fire 5.x interface allows you to:

• Query site data from the FIRE 5.x software system.

• Export OCA information from VisionCAD to VisionFIRE using the FIRE 5.x system’s CAD Listener feature.

Setting up CAD to Use RMS, Fire

Note: Fire references in this section refer to the FIRE 3.x interface.

The first step to enabling these interfaces is to create the connection from the CAD workstation to the RMS or Fire server. This requires creating ODBCs on each machine that will use the interface.

Set up the following ODBCs:

For Inform RMS

• CAD_RMS

• CAD_RMS_SYSTEM

For VisionFIRE

• CAD_FIRE

• CAD_FIRE_SYSTEM

Complete the following steps to create these connections. Two methods are available to create these connections. Both are described below.

Method 1: Step 1. Place the VisionCAD Installation CD in the CD-ROM drive of the CAD workstation.

Step 2. The Installation CD should automatically start up the Installation program. Once it does, press Exit Installation.

Step 3. Using Windows Explorer, navigate to the Utilities folder of the Installation CD.

Step 4. Double click the rmsdsn.exe.



Page 39

Step 5. Fill in the fields as appropriate for your integration and click OK. (SQL Security must be selected as the security type.)

Step 6. The window automatically closes and this process is complete.

Method 2: Step 1. From your Start menu, select Settings, then Control Panel.

Step 2. Locate Data Sources (ODBC) and double click to open it.

Step 3. The following screen displays.



Page 40

Step 4. Select the System DSN tab.

Step 5. Click the Add button to create the first data source.



Page 41

Step 6. The following window displays.

Step 7. Select SQL Server and click Finish.




Page 42

Step 9. Enter the database name in the name field and select the appropriate server for that data source (either your Inform RMS or VisionFIRE server).

For Inform RMS: (Both entries below must point to the same SQL Server.)

CAD_RMS

CAD_RMS_SYSTEM

For VisionFIRE: (Both entries below must point to the same SQL Server.)

CAD_FIRE

CAD_FIRE_SYSTEM

Note: For backwards compatibility, if these do not exist, then VisionCAD attempts to locate data sources using the following names: For Inform RMS: VSI_DATA and VSI_SYSTEM For VisionFIRE: VSI_FIRE and VSI_FIRE_SYSTEM

Step 10. Click Next.


Step 12. Select the appropriate login method, either network login or SQL login. This choice depends on the rights granted on the target server.

Step 13. If you choose SQL logins, enter your Login ID and Password at the bottom of the screen.



Page 43

Step 14. Click Next.


Step 16. Accept all defaults and click Next.


Step 18. Accept all defaults and click Next.




Page 44

Step 20. Click Test Data Source.

Step 21. If the test is successful, the following window displays.



Page 45

Step 22. Click OK.

Step 23. If the test failed, double check all your settings for the data source and check that the target server is on line and running. Consult the ODBC help files or contact technical support for more information.

Step 24. Complete this set up process for each data source necessary for the interfaces at your agency.

CAD Configuration In order to use all functions available from the RMS/Fire interface, the following options must be set in CAD Configuration.

Category Option Scope Value

RMS/FIRE RMS Interface Global Yes

RMS/FIRE FIRE 3x Interface Global Yes

Warn Warn Criminal History Global Yes



Page 46


Warn Warn RMS Alerts Global Yes

Warn Warn Warrant Global Yes (if you have the Warrant module)

Departments In addition, you can set up the RMS and FIRE ORIs (Originating Routing Identifier) and departments in CAD General Edit - Departments table. This is where you set up the OCA option, also. Refer to the chapter “Using General Edit” in the VisionCAD System Administration User’s Guide for instructions on setting up RMS and FIRE ORIs (jurisdictions), departments, and OCAs in CAD.

Rights Inform RMS users interfacing to CAD must be added to the Telecommunicators group on the CAD PDC (Primary Domain Controller), and granted basic telecommunicator rights in CAD Front End Security as well.

Setting up RMS or Fire to Receive CAD Data


Please refer to your Inform RMS System Administration User’s Guide to perform these additional requirements:

Each CAD user, as defined in CAD Front End Security, must be added to RMS (or Fire). Your user login and password should be identical in both applications to avoid having to type in your RMS user ID and password when accessing RMS (or Fire) from CAD.

The user must be given “ADD” and “VIEW” rights in the RMS Folder module, as well as “ADD” rights to the NIFRS_Apparatus table in Fire. For Fire, the user must have these rights for the Fire module as well.

To pull Fire Plans from VisionFIRE, CAD Users must have view rights to the following tables in VisionFIRE.

• Site_Main



Page 47

• Site_Hazmat

• Site_Tactical

The OCA number must be configured in RMS System Administration using number control for RMS Case or Fire Incident.

Transferring Call Data to RMS


If the RMS interface is enabled in CAD Configuration, CAD can transfer call data to TriTech’s Records Management System (RMS). Depending on the OCA options selected in the department set up in General Edit, CAD may transfer the data automatically, or dispatchers may initiate the transfer manually. See the chapter “Using General Edit” in the VisionCAD System Administrator User’s Guide for more information on this set up.

The automatic transfer methods are:

• When you assign a unit to a call, an RMS OCA number is generated and call data transferred to RMS.

• When you clear a call with a primary unit from an RMS department, an OCA number is generated and call data transferred to RMS.

The manual transfer methods are:

• With the call highlighted in the All Calls window, click the OCA number from the All Calls toolbar. If the appropriate department does not appear in the department field, select it from the drop down list.

• When you clear the call, check the Create OCA option in the clear call window. The Create OCA window will appear, and you can create the OCA as described above.

• With the call highlighted in the Historical Calls window, click the OCA button. The Create OCA window will appear, and you can create the OCA as described above.

All methods can create cases or master name records in RMS, depending on how you set up your CAD configuration. An incident form can also be created in RMS, and as much data as possible is transferred to the form.

The “Case Only” and “Incident w/ Person & Vehicle as Narrative” methods also create Calls for Services records in RMS when the OCA numbers are created in VisionCAD. When the calls are cleared the Calls for Services records in RMS are also updated.



Page 48

In RMS, master records are stored by person’s name, property, or location. When a case is created in RMS, these items can be used for searching to find a case. If a case is not created, these items cannot be searched. Other ways to bring information into RMS are into the log module or as a narrative. Then, using RMS, you can create the Master Name, Property, and Location records.

Note: Property in RMS includes the vehicle information sent from CAD. Vehicles are considered Property.

Based on the Transfer Option selection in the department record, call data is transferred to RMS in one of three ways:

• Create case only. (CAD pulls the case number for RMS only; no other data is transferred.)

• Create incident record with person and vehicle as narrative.

• Create log with person and vehicles.

The “Case Only” and “Incident w/ Person & Vehicle as Narrative” methods also create Calls for Services records in RMS when the OCA numbers are created in VisionCAD. When the calls are cleared the Calls for Services records in RMS are also updated.

In order for this function to work, the dispatcher creating the Case must have security access rights to RMS. Specifically, the dispatcher needs “ADD” and “VIEW” rights in the RMS Folder module.

RMS Auto-Create Incident You can automatically create an RMS or Fire case record or RMS log record when a unit is dispatched to a call or when a call is cleared (this provides the most information through the interface). You can select the way OCAs are created under the OCA section of the Departments window in CAD General Edit.



Page 49

The same RMS ORI can be used for more than one Department record, but only one Case or Log record will be created for each different jurisdiction. If you choose CAD Internal OCA, no ORI (jurisdiction) is required, as this department will not be tied to RMS or Fire.

If a unit belongs to a FIRE department, a dispatcher can create Fire Incidents and OCAs. A Fire Incident record is created if the unit assigned to the call is FIR category; otherwise a Case or Log record is created. When a unit is dispatched, only the main Log, Case, or Fire Incident records are created. When the call is cleared, the Log record is updated and a narrative added, and the Fire Incident is updated and a narrative added. Refer to the section “Using CAD with VisionFIRE 3.x” for complete details on the CAD to Fire interface.

If no unit is assigned to the call, dispatchers can manually create an OCA so an RMS/Fire incident can be created. In the same situation, an OCA number will be generated automatically if the complaint type for the call requires an incident report.

Note: The Auto Create function is also affected by the “Report Required” field in the General Edit - Complaint Types table. The Auto Create OCA rules are explained extensively in the chapter “Using General Edit” in the VisionCAD System Administrator User’s Guide.

OCA Failover: CAD to RMS/FIRE Interface VisionCAD will create OCA numbers as defined per Department when an interface to RMS or Fire is successfully connected. When the interface is unavailable, VisionCAD will create OCA numbers based on an Internal OCA Source mask.

Note: In order to ensure a distinction between an OCA issued from RMS and a CAD Internal OCA, which will be generated when CAD and RMS have lost their connection, we recommend making the numbering mask in CAD unique so your users can immediately tell the difference. TriTech suggests adding a character at the beginning of the mask (“C” as the first character, for example) to clearly denote the OCAs origin. Example: CYYYY-000000



Page 50

OCA Number Setup

VisionCAD will make connection attempts to the interface every 5 minutes for 20 minutes. Afterwards, attempts will be made every 15 minutes for 1 hour. Final attempts are made every hour thereafter. Resetting VisionCAD will reset the attempts.

VisionCAD searches every hour upon initial login for stranded OCAs. VisionCAD attempts this “rescue” every 5 minutes until stranded OCAs are processed successfully.

If an OCA is created by VisionCAD and fails in RMS, that workstation “owns” the OCA number until the user resets VisionCAD. No other logged workstation will attempt to create the CASE during unsuccessful connection times.

Note: If VisionCAD loses its database connection (due to network issues, SQL server issues, etc.) the system displays a connection error that informs you that you must exit and restart the VisionCAD application. This only displays once while the CAD Notification dialog is displayed, which prevents the messages from stacking up continuously from automatic refreshes if the workstation is unattended. However, other messages are not prevented from displaying. For example, when CAD attempts to process the PTT events, you will see an ExecuteSQL error regarding the attempt to clean the Active_PTT table.

Clearing a CAD Call When you clear a CAD call, you can transfer the call data to RMS. The data is placed into a folder named CadReports in RMS.



Page 51

Use the following steps to transfer call data when you clear a call.

Step 1. In the All Calls window, highlight the call you want to clear.

Step 2. Click the Clear button.

Step 3. The Clear Call Confirm window displays.

Step 4. Click the Create OCA checkbox.

Step 5. Click Clear.

Step 6. The Create OCA Number window displays. Continue with the steps in “Assigning an RMS OCA Number to a Call.”

Note: If the primary department on the call is set up to Auto Create an OCA or the complaint type requires a report, then dispatchers do not need to create the OCA manually on clearing the call.



Page 52

Assigning an OCA Number to a Call If this option is enabled for Departments in General Edit, you can use the OCA function to assign one or more OCA numbers to a call. You have the option of assigning one of the following as the OCA number for each department assigned to a call:

• CAD call number as OCA

• CAD internal OCA

• RMS OCA

• Fire OCA

To assign an OCA number to a call, use the following instructions.

Step 1. With the call to which you want to assign an OCA number highlighted, click the OCA button. (An alternate method of selecting the call is to click OCA first, then select the call number from the Call Number pull-down selection menu within the Create OCA Number window).

Step 2. The Create OCA Number window displays.



Page 53

Step 3. The default Department that displays is the call’s primary unit department. (If a unit has not been assigned to the call, no departments display in the department list.) To change it, select the department or jurisdiction for which you are assigning the OCA number from the pull-down list. The source of the OCA number is determined by the department set up in CAD General Edit. See the chapter “Using General Edit” in the VisionCAD System Administrator User’s Guide for details on setting up OCA numbers in CAD.

Step 4. Select the number of OCA numbers you want to create in the Create # OCA Number(s) field.

Step 5. Click the Create button. An OCA number is assigned. All OCA numbers assigned display in the Existing OCA Numbers area of the window.

Step 6. To create more OCA numbers, repeat steps 3 through 5.

Step 7. Click Finished when you are done.

When you create an OCA number for RMS or Fire, some CAD fields may be transferred from the call to an incident record.

Note: If the primary department on the call is set up to Auto Create an OCA on dispatch, then manually creating an OCA could result in duplication. However, the Create OCA window will contain the existing OCA to alert the dispatchers to possible duplication.

Assigning an RMS OCA Number to a Call If this option is enabled for Departments in General Edit, you can use the OCA function to assign an RMS OCA number to a call. The procedure to transfer the call data is the same for all departments regardless of set up and ultimate destination:

Step 1. With the call to which you want to assign an OCA number highlighted, click the OCA button. (An alternate method of selecting the call is to click OCA first, then select the call number from the Call Number pull-down selection menu within the Create OCA Number window).



Page 54

Step 2. The Create OCA Number window displays.

Step 3. The default Department that displays is the call’s primary unit department. To change it, select the department for which you are assigning the OCA number from the pull-down selection menu or click in the field and type one.

Step 4. Select the number of OCA numbers to create in the Create # OCA Number(s) field.

Step 5. Click the Create button. The next available RMS OCA number (case number) is assigned. The new OCA Number displays in the list at the bottom of the Create OCA Number window.

Note: If RMS is unavailable, VisionCAD will use the OCA number mask set up on the department record.

Step 6. To create more OCA numbers, repeat steps 4 through 5.

Step 7. Click Finished when you are done.



Page 55

Note: If the primary department on the call is set up to Auto Create an OCA on dispatch, then manually creating an OCA could result in duplication. However, the Create OCA window will contain the existing OCA to alert the dispatchers to possible duplication.

The Data in RMS Eventually, the CAD data is transferred to RMS in one form or another, depending on which Transfer Option you select on the department record. This section shows an example of how the data displays in RMS when an RMS case is created.

When CAD Data is transferred to RMS, the data is always placed into a Folder in RMS with a Folder Number of “CadReports”. The Folder Description is “CAD Reports – Records from CAD.” For instance, if you select a Master Name in RMS for a person in CAD, the name is linked to the CadReports folder and any other folders the name may already be linked to in RMS.

Shown below is the Folder window of the RMS application with the CadReports folder listed and highlighted.

RMS Folder Window



Page 56

If you click on the Case button in the RMS Folder window, the Case Records window displays with the CAD cases listed as shown below. Note that CAD cases are created as “not reportable” miscellaneous case types.

RMS Case Window



Page 57

If you click on the Calls for Service button in the RMS Case window, the Calls for Service window displays with the CAD data listed as shown below.

RMS Calls for Services Window

RMS Calls for Services Person Window



Page 58

RMS Calls for Services Vehicle Window

RMS Calls for Services GEO Window

Options to Transfer to Incident The following sections describe what is transferred to RMS when using each of the four choices in the Transfer Option field on the VisionCAD department record.

Case Only This method creates a new case in RMS for the call. CAD pulls the case number for RMS only no other data is transferred. The person, vehicle, and location information is not transferred to RMS. This is the least extensive method of transferring call data to RMS. It transfers the least amount of information.

Incident w/ Upload Files for Person and Vehicle OBSOLETE

Incident w/ Person and Vehicle as Narrative With this method, you create a case number and an incident record with any person and vehicle information stored in the Narrative in RMS.



Page 59

Log w/ Person and Vehicle Using this method, you create a case number and entries in the RMS Log. The log entry includes the person, property, and location. No master files are created.

Fields Transferred from CAD to RMS

RMS Incident Fields Transferred from CAD The two incident options for RMS upload create Incidents in RMS and push information from the CAD call to the RMS Incident. Case Only creates a case number in RMS, and then the RMS user pulls information from the CAD call into RMS. The fields that are transferred from a CAD call to an RMS incident are shown in the following table.

CAD Field RMS Incident Field

Complaint Description

Date Received Date Report

Date Received Date Incident

Actual Incident City City

Actual Incident Location Address

Actual Incident Apartment Apartment

Street Street Name

Tract Offense Tract

Block Block

The following fields can be pulled into the appropriate RMS Incident Fields using the CAD Incident button in RMS with Create Case.


Vehicle Tag Plate Number

Vehicle State Plate State

Vehicle Color Color

Vehicle Year Year



Page 60


Vehicle Make Make

Vehicle Model Model

Vehicle VIN VIN

Vehicle Owner Name (Last, First, Middle)

Last Name, First Name, Middle Name

Comments Comments

Subject Name (Last, First, Middle)

Last Name, First Name, Middle Name

Category Involvement Type

Age Min Age

Age Max Age 2

Sex Sex

Race Race

Ethnic Ethnic

Height Height

Weight Weight

OL State License State

OL Number License Number

DOB Date Born

Note: These Person and Vehicle fields are inserted in the Narrative of the RMS Incident with the option Incident w/ Person and Vehicle as Narrative.

RMS Log Fields Transferred from CAD The option Log w/ Person and Vehicle creates a Log record in RMS. The fields that are transferred from a CAD call to an RMS log are shown in the following table.



Page 61

CAD Field RMS Log Field

Complaint Complaint Type

Date Received Date Offense

Date Received Date Received

Time Complete Date Complete

Time Dispatched Time Dispatched

Time Destination Time Arrived

Call Owner Received By

How Received How Received

Call Class Class

Call Status Status

Call Ten Code Ten Code

Actual Incident City City

Actual Incident Address Address

Street Street Name

Block Block

Searching and Viewing Information in RMS

The following sections describe how to search for and view information on a person or property by accessing TriTech’s Records Management System, or RMS.

Fields for which you can search for a person are:

last name first name middle name alias/moniker block number street name



Page 62

social security number sex date of birth race driver’s license number driver’s license state

Fields for which you can search for property (vehicle only) are:

vehicle identification number (VIN) vehicle plate number vehicle plate state serial number hull number

Accessing the RMS Search Function There are several ways to access the RMS Search function throughout the CAD Dispatch module. These methods are listed below.

From the main CAD Dispatch screen:

• Select View from the CAD menu bar, then RMS Search.

• With a call highlighted, select Call from the CAD menu bar, then select View Warrants.

• From the All Calls window toolbar, click the RMS button.

• From the All Calls window toolbar, click Lookup, select All or Limited, and then select Warrants or Civil. (If you select Limited, highlight the call before clicking on Lookup. Civil is not available for the Limited function.)

The Search RMS window displays -- from which you can search for warrants, civil papers, and criminal history -- based on a person or vehicle property.

Search RMS window



Page 63

Search for Person Follow these steps in CAD to search RMS for a person.

Step 1. Access the RMS Search function. (See "Accessing the RMS Search Function.")

Step 2. To do a search based on a person, click on the Search Person tab if it is not displayed in front.

Step 3. Fill in as much information as you know in the fields. All fields are not required to perform a search.

To search for a person, you must at least enter a partial first and last name.

Search Person Tab

Step 4. Click on the desired button to start the search. The options are RMS, NCIC, or Both (NCIC & RMS).

Note: The NCIC and BOTH buttons will be disabled if you do not have the CJIS Query right checked in the VisionMOBILE Message Switch Configuration utility – VisionMOBILE versions 3.7 Update 3 or higher. (If you are using an earlier version of VisionMOBILE, then VisionCAD determines if you have access to NCIC queries based on Right 46: NCIC in the Front End Security module.)



Page 64

Step 5. The Matching Names tab displays with one or more matches, depending on the search results. If there is more than one match, the cursor is positioned as close as possible to the name or property matching your search criteria, as shown below.

Search RMS Window

The color-coding corresponds to Inform RMS master name groupings so linked aliases are shown together. Criminal history records are tied to true names rather than to aliases.

Note: Scroll to the right to view other fields, such as the Table Name. The Table Name columns are important in this window; they define the nature of the record (warrant, civil paper, property, citation, incident, evidence, etc.) and where it was entered in RMS.

Step 6. If there are images associated with a record, a thumbnail image will display on the right side of the window as shown above. Double click the thumbnail to view additional information. If there are additional images, you will be able to scroll through them using the arrows on the new image window.

Step 7. At this time, you may perform an NCIC person query for the selected individual. When the NCIC button is pressed, CAD will execute a person search through the MCT VisionMOBILE connection using the following data fields: race, sex, date born, last name, first name, middle name, and SSN.

Note: Refer to the section in this book, “NCIC Queries” for detailed information on using the NCIC interface with CAD.



Page 65

Note: The NCIC button will be disabled if you do not have the CJIS Query right checked in the VisionMOBILE Message Switch Configuration utility – VisionMOBILE versions 3.7 Update 3 or higher. (If you are using an earlier version of VisionMOBILE, then VisionCAD determines if you have access to NCIC queries based on Right 46: NCIC in the Front End Security module.)

Step 8. Continue with the section “Viewing Outstanding Warrants and Civil Papers” or “Viewing Criminal History.”

Viewing Outstanding Warrants and Civil Papers Use this function to show a person’s unserved civil papers and warrants. Use the steps below to view this information.

Unserved warrants from Inform RMS will be listed based on the following criteria:

• The name’s Involvement Type is Subject.

• The Warrant Inactive field is NOT checked.

• The Date Served field does NOT contain data.

• The Expire Date field does NOT contain data, OR the Expire Date field contains a date greater than today’s date.

• The Date Returned field does NOT contain data.

Unserved civil papers from Inform RMS will be listed based on the following criteria:

• The name’s Involvement Type is Defendant.

• The Civil Status is Attempted or Assigned.

• The Expiration Date field does NOT contain data, OR the Expiration Date field contains a date greater than today’s date.

Step 1. Follow the instructions in the sections “Accessing the RMS Search Function” and “Search for Person.”

Step 2. When the Matching Names tab displays, select the record for the person whose outstanding warrants, civil papers, and/or arrests you want to view.



Page 66

Search RMS – Matching Names Window

Step 3. Click the Outstanding Warrant/Civil button.

Step 4. The Search RMS window displays with a Synopsis Description showing records of the person’s outstanding warrants and civil papers.

Search RMS – Warrants and Civil Papers Window

Step 5. To view the details of a civil paper or warrant, select the item and click Show Detail.



Page 67

Step 6. The details for the outstanding civil paper or warrant display in the RMS Forms window as shown below.

RMS Forms - Warrant Window

Step 7. Click the Civil Name or Warrant Name tab (depending on which window, Civil or Warrant, is displayed).

Step 8. The details for the civil name or warrant name display as shown below.

RMS Forms - Warrant Name Window



Page 68

Step 9. For warrants, you may also view the charge details.

RMS Forms - Warrant Charge Window

Step 10. To close the RMS Forms - Civil Paper or Warrant window, click Finished.

Marking a Warrant Served in RMS In the RMS Forms - Warrant Window, the information on whether the warrant was served, when it was served, and how it was served displays. If a warrant is not yet served, these fields are blank.

The following steps describe how to serve a warrant.

Step 1. Follow the instructions in the sections “Accessing the RMS Search Function,” “Search for Person,” and “Viewing Outstanding Warrants and Civil Papers.”

Step 2. With the RMS Forms – Warrant window displayed, you can view the details for the warrant as shown below.



Page 69

RMS Forms

Step 3. You can mark a warrant served from this window by clicking on the Served button. The Warrant Served pop-up window displays for you to select an Officer ID and select an option for how the Warrant was served.

Warrant Served

Step 4. Once these items are selected, click on the Served button to serve the warrant, or click Cancel in the pop-up window not to serve the warrant.



Page 70

Step 5. Once the warrant is served, the information, including the Officer ID and the date/time the served button is selected, displays in the Warrant tab window as shown below.

Warrant Tab

Viewing Criminal History Use the Criminal History function to view a person’s criminal history (citations, arrests, warrants, and jail confinements). Use the steps below to view this information.

Step 1. Follow the instructions in the sections “Accessing the RMS Search Function” and “Search for Person.”

Step 2. From the Matching Names tab, select the record for the person whose criminal history you want to view.

Search RMS – Matching Names Window



Page 71

Step 3. Click the Criminal History button.

Step 4. The Search RMS window displays with a synopsis showing records of the person’s criminal history.

RMS Forms Criminal History - Summary Window

Step 5. Select the item you want to view and click Show Detail.

Step 6. The details for the item display in the RMS Forms window as shown below.

RMS Forms – Criminal History Detail Window



Page 72

Step 7. You can click the first or second tab to view different details about the item.

Step 8. More details for the item display as shown below.

RMS Forms – Criminal History – Detail Window

Step 9. To close the RMS Forms - Warrant window, click Finished.

Search for a Vehicle Follow these steps in CAD to search RMS for a vehicle.

Step 1. Follow the instructions in the section “Accessing the RMS Search Function.”

Step 2. To do a search based on vehicle property, click on the Search Property tab if it is not displayed in front.

Step 3. Enter an exact match of a VIN to search by vehicle number; or, if searching by license plate, enter an exact Plate Number and State or enter a serial number or hull number on the property.



Page 73

Search RMS - Search Property Window

Step 4. Click on the desired button to start the search. The options are RMS, NCIC, or Both (NCIC & RMS).

Note: The NCIC and BOTH buttons will be disabled if you do not have the CJIS Query right checked in the VisionMOBILE Message Switch Configuration utility – VisionMOBILE versions 3.7 Update 3 or higher. (If you are using an earlier version of VisionMOBILE, then VisionCAD determines if you have access to NCIC queries based on Right 46: NCIC in the Front End Security module.)

Step 5. The Results tab displays.

Search Property Tab

Note: Scroll to the right to view other fields, such as the Table Name. The Table Name columns are important in this window; they define the nature of the record (warrant, civil paper, property, citation, incident, evidence, etc.) and where it was entered in RMS.

Step 6. Select the item you want to view and click Show Detail.



Page 74

Step 7. The details for the item display in the RMS Forms window as shown below.

RMS Forms - Incident Property - Detail Window

Step 8. To show the Incident related to the item, click the Incident tab.

Step 9. The details of the Incident display as shown below.

RMS Forms - Incident Window

Step 10. To close the RMS Forms – Criminal History window, click Finished.



Page 75

Add CAD Subject or Vehicle from RMS Search Results After selecting Show Detail from the RMS Search Results tab, the details for the item display in the RMS Forms window. The RMS Forms window that displays includes an Import button if the data being displayed is one of the following person or vehicle types:

• Warrant (Person)

• Civil (Person)

• Citation (Person)

• Arrest (Person)

• Jail Inmate (Person)

• Incident Vehicle (Vehicle)

RMS Forms – Example with Add to Call button

To add person or vehicle information to the CAD call based on the data returned from RMS, press the Import button. A new subject or vehicle will be added to the currently selected CAD call in Edit Call window.

Using CAD with VisionFIRE 3.x

CAD provides an interface to TriTech’s FIRE 3.x software. Using this interface, you can create a FIRE 3.x incident from CAD call data and view FIRE 3.x master indices. Information in the master indices may have been entered for RMS or Fire. This section refers to all master indices by “RMS.”



Page 76

CAD FIRE 3.x Dispatch When the CAD system administrator sets up the Fire Units’ Department records, they deisgnate the department as Fire and enter an RMS/Fire jurisdiction. This way, CAD Dispatch knows to create the OCA/Incident for a Fire server instead of an RMS server. The same RMS/Fire jurisdiction can be used in more than one CAD department record, but only one incident will be created for each different jurisdiction.

In CAD, Fire units are suggested for calls by Unit ID, Special Type, Function, or Type and Function.

If a unit is assigned to a Fire department, a dispatcher can create Fire Incidents and Fire OCAs.

A Fire Incident/OCA can be created automatically either when the first Fire unit is dispatched to the call or when the call is cleared. Alternatively, your installation may choose to create all OCAs for a department manually. These options are available from the Departments Database in CAD General Edit. Refer to the chapter, “Using General Edit,” in the VisionCAD System Administrator User’s Guide for more information on this set up.

To use the CAD to Fire interface to its fullest potential, each FIRE department should be set up for Auto Create OCAs on Dispatch. With this setting, a Fire Incident with Narrative will be created for each Department as the first unit from that Department is assigned to the call. Then, as each unit is removed from the call, a Fire Apparatus record is created with full details for that unit. See the section “FIRE 3.x Incident Fields Transferred from CAD” for more information on call and unit details transferred to VisionFIRE.

If the Fire Department is set to Auto Create on Clear or No Auto Create, then only one Fire Incident will be created and no Appartus records will be created.

Note: CAD Units MUST be set up the same as the Fire Apparatus. If this is not set up properly (matching) then the data that transfers from CAD to Fire will not be accurate.

CAD Access to FIRE 3.x Management System If a CAD user will be working with TriTech's Fire Management System (VisionFIRE 3.x), the CAD user must also be set up with a login userid and password in RMS System Administration. It is best to use the same login ID and password for both CAD and Fire to avoid the additional RMS login window. The user must be given “ADD” and “VIEW” rights in the RMS Folder module. Please refer to the RMS System Administration Guide for instructions on setting up users for Fire access.

To create OCAs from VisionFIRE, CAD Users must have add rights to the NFIRS_Apparatus table in VisionFIRE.



Page 77

To pull Fire Plans from VisionFIRE, CAD Users must have view rights to the following tables in VisionFIRE.

• Site_Main

• Site_Hazmat

• Site_Tactical

Note: If Fire and RMS are on the same server, you will need to use RMS Central Configuration to use one login for two jurisdictions on the same server. If Fire and RMS are on different servers, you can use the same login for both jurisdictions.

CAD FIRE 3.x Configuration Option Under the RMS/FIRE category, you must set the Configuration option FIRE 3x Interface to Yes.

Note: If Fire and RMS are on the same server, you will need to use RMS Central Configuration to use one login for two jurisdictions on the same server. If Fire and RMS are on different servers, you need to use the same login for both jurisdictions. Please refer to the Inform RMS System Administration User’s Guide for instructions on setting up users for Fire access.

Option Definition

FIRE 3x Interface (RMS/FIRE)

Set this option to Yes if CAD is interfacing to Fire, otherwise set this option to No. When this option is set to Yes, CAD can use Fire OCA numbers instead of CAD Internal OCA numbers.

Before performing a Fire Update, you must set this option to NO and do a File/Reset in CAD. This is necessary to avoid disturbing Fire during the Update process. After the Update, set the option back to Yes.

Setting up OCA Number Control For the interface, set up Fire Departments in CAD General Edit to retrieve OCA numbers from VisionFIRE 3.x and enter the appropriate ORI/Fire Jurisdiction. Refer to the General Edit chapter in the VisionCAD System Administrator User’s Guide for details on this set up. Please refer to your Inform RMS System Administration User’s Guide to perform this requirement: The OCA number must be configured in RMS System Administration using number control for Fire Incident.



Page 78

Transferring Call Data to FIRE 3.x If the FIRE 3.x interface is enabled in CAD Configuration, CAD can transfer call data to TriTech’s Fire Management System (RMS). Depending on the OCA options selected in the department set up in General Edit, CAD may transfer the data automatically, or dispatchers may initiate the transfer manually. See the chapter “Using General Edit” in the VisionCAD System Administrator User’s Guide for more information on this set up.

The automatic transfer methods are:

• When you assign a Fire unit to a call, a Fire OCA is created, and the Fire incident is created.

• When you clear a call whose primary unit is a Fire unit, a Fire OCA is created, and the Fire incident is created.

The manual transfer methods are:

• With the call highlighted in the All Calls window, click the OCA number from the All Calls toolbar. If the appropriate department does not appear in the department field, select it from the drop down list. Click Create, the Fire OCA is created, and the Fire incident is created.

• When you clear the call, check the Create OCA option in the clear call window. The Create OCA window will appear, and you can create the OCA as described above. A Fire OCA is created, and the Fire incident is created.

• With the call highlighted in the Historical Calls window, click the OCA button. The Create OCA window will appear, and you can create the OCA as described above.

Note: In order for data to transfer, the CAD dispatcher must have at least “ADD” and “VIEW” rights to the Fire module of RMS.

Transferring Fire Plans to CAD When the CAD to Fire interface is set up with VisionFIRE 3.x, CAD will send a message to the Fire application to send back the Fire Plan for the address of a call. The dispatcher can then view the plans by clicking on Fire Plan in the Edit Call window.

The following figure is an example of fire plans from VisionFIRE. If the address has an Internal ALI record in CAD with Fire Plans, those plans are still accessible. Display these plans by clicking once on the Fire Plan field in the New Call or Edit Call window.



Page 79



Page 80

Showing Fire’s Closest Hydrants in CAD When the CAD to Fire interface is set up with VisionFIRE 3.x, CAD will send a message to the Fire application to send back the five closest fire hydrants for the address of a call. The dispatcher can then view the Hydrants by right-clicking on Fire Plan in the Edit Call window or by clicking the Hydnt (Hydrants) button in the Edit Call window. (CAD must have Mapping for this feature to be available.)

FIRE 3.x Incident Fields Transferred from CAD The fields that are transferred from a CAD call to a FIRE 3.x Incident are described below and are organized by the NFIRS form and section.

NIFRS-1 (Basic) Section A: In Section A, the Agency FDID, State, Date (Date Received), and Incident Number will transfer from CAD. (Based on the State as set up in CAD Local/Global Configuration Profile category, on the jurisdiction attached to the fire unit, and the OCA number created). The Exposure Number is automatically filled in by the Fire module.

Section B: The Address, Apt/Suite/Room, City, and State fields are transferred from CAD based on the address information entered into the transferred call.

Section E: Alarm Date/Time = earliest Date/Time DIS or ENR for all FIR, EMS, or FRE units for this department.

Arrived Date/Time = earliest Date/Time ONS (OnScene) for all FIR, EMS, or FRE units for this department.

Units Cleared Date/Time = latest “cleared” time.



Page 81

Section G1: The following fields on Section G1 are filled in automatically by the Fire module based on the number of Fire/EMS units from CAD: Apparatus or Personnel form used, Suppression Apparatus/Personnel, EMS Apparatus/Personnel, and Other Apparatus/Personnel.

Section L: A narrative is automatically generated from the CAD call with the following information: Call Number, Complaint Type, Complaint Description, Caller Name, and CAD Narrative attached to the transferred call.

Apparatus/Resource/Personnel Forms The apparatus and personnel records are automatically generated based on the units attached to the transferred CAD call.

Apparatus Record: Apparatus ID, Apparatus Name, Apparatus Type, Number of People, and Use fields are filled based on the attached CAD units. A separate record is generated for each Unit as it is removed from the call. Additionally, the Dispatch Date/Time, Enroute Date/Time, Arrival Date/Time, and Cleared Date/Time is filled in for each apparatus from the corresponding CAD fields. Action Taken fields are to be filled in manually.

Note: The Cleared Date/Time field in VisionFIRE will come from the Clear/Removed field in VisionCAD.

Personnel Record: Based on each Unit attached to the transferred CAD call, the Fire system automatically enters a personnel record for each personnel on shift for that apparatus at the time of the call. The Apparatus ID, Apparatus Use, Personnel ID, Name, and Rank fields will be filled. Again, Action Taken fields are to be entered manually.

Using CAD with Fire 5.x

CAD provides interfaces to TriTech’s FIRE 5.x software. These interfaces enable the following tasks.

• Fire Plan Query – This interface queries site data from the FIRE 5.x software system.

• OCA Export – This interface exports OCA information from VisionCAD to Fire using the FIRE 5.x system’s CAD Listener feature.

This section covers the configuration and use of each interface. This document does not describe the FIRE 5.x application. Consult the documentation that came with that product for those instructions.



Page 82

FIRE 5.x: Fire Plan Query

Installing the Fire Plan Query Interface The following steps describe how to install the query interface service.

Step 1. Place the Installation CD in the CD-ROM drive of the machine that will contain this interface.

Step 2. Locate and manually start up FireQueryInstall.exe from the CD.

Step 3. A preparing to install window displays. Simply wait for the next window.

Step 4. The Welcome window displays.

Step 5. Click on Next.



Page 83

Step 6. The License Agreement form displays. Read and accept the License Agreement and click Next to continue the installation process.

Step 7. Enter your configuration options.

VisionFIRE Hosted Service Endpoint – Enter the URL that points to the remote hosted service provided by the VisionFIRE database server. For example, http://gateway.visualfire.com/ETIPrePlan/ETIPrePlanService.svc

TCP Port Number – Enter the port number to use for accepting connections on the local machine from CAD workstations on the network. The default value is 6009.

Log File Location – This is the folder where the query service log file will be written.



Page 84


Step 9. To begin the installation, click Install.



Page 85

Step 10. The files will be installed. The following window displays to show you the progress of the install.

Step 11. You will receive the following notification that the installation is complete.

Step 12. Select Finish.



Page 86

At this point, there will a new “Fire Query Service” in the Windows Service Control window.

Configuring the Fire Plan Query Interface In order to use the FIRE 5.x Query interface, the following option must be set in CAD Configuration.


RMS/FIRE FIRE 5x Query TCP Address

Global or Local

Enable the query interface by entering the TCP/IP address of the machine to which the Fire Query Service was installed, and the port configured for the service. This must be in hostname:port format, such as 192.168.0.22:6009 or CADQuerySrv:6009. This address is used for querying site data.

RMS/FIRE FIRE 5x Database Name Global or Local

Enter the database name to access when querying for Fire 5.x site data.

Using the Fire Plan Query Interface The Fire Plan Query Interface provides the following main functions:

• Manual Searches: From the View menu in CAD Dispatch, a FIRE Search option is enabled to access the FIRE 5.x query screen.

• Automatic Searches: From calls windows in CAD Dispatch, the automatic Fire Plan alert is enabled to search the FIRE 5.x database.

FIRE Search From the main CAD Dispatch screen, select View from the CAD menu bar, then FIRE Search. The interface window displays from which you can search FIRE data based on either occupancy ID or address.

Note: The manner and method of searching is controlled by the FIRE 5.x server. This search window merely provides a graphical interface to access the FIRE 5.x server and query routine. The Fire query routine appears to search by begins with matches on most supplied fields.



Page 87

From the Search tab:

• To do a search based on occupancy ID, enter a value into the Occupancy ID field. Then simply select the Search button or press Enter. (Typing in this field disables the remaining fields. To enable all fields and perform an address based search press the Clear All button.)

• To do a search based on address, enter an address number and street name, and if desired as much of the remaining address fields. Select the Search button or press Enter. (Typing in any address field disables the occupancy field. To enable all fields and perform an occupancy based search press the Clear All button.)

This interface window also includes Clear All and Cancel buttons. Press Clear All to clear the values entered in the search fields. Use Cancel to close the window without searching.

Search tab

After pressing Search, if site data is found, the Results tab is automatically displayed; otherwise, a message displays informing you that no search results were found. The Results tab displays a summary list of sites matching your search criteria. For each site, summary lists of any contacts, hazards, and connections attached to the selected site also display.

Note: Again, please note the data fields displayed are controlled by the FIRE 5.x server and query routine.



Page 88

Results tab (Summary Results)

From the Results tab you can double-click (or press Enter) on any summary record (site, contact, hazards, or connections) to quickly access its more detailed information on the Site, Contact, Hazard, or Connection tabs.

The detail tabs show all the field detail in text form with field name listed on the left and actual data for each field listed on the right. If a field has no data, it is not displayed.



Page 89

Site tab (Detailed Results)

The Contact tab shows the contact data for the Site currently selected on the Site grids.

Contact tab (Detailed Results)



Page 90

The Hazard tab shows the hazard data for the Site currently selected on the Site grids.

Hazard tab (Detailed Results)



Page 91

The Connection tab shows the fire hydrant connection data for the Site currently selected on the Site grids.

Connection tab (Detailed Results)

Viewing Fire Plans from FIRE 5.x With this interface, you will be alerted if the VisionCAD call location matches FIRE 5.x Site records. From the various call windows (Edit Call, Miscellaneous, Traffic Stop, etc.) click the Fire Plan field to view these preplans.

Note: Potentially you may receive several different windows to view fire plans. 1) VisionCAD Fire Plans window – CAD retrieves any matching CAD Internal ALI Fire Plans. 2) Site Browse (VisionFIRE 3.x) window – If your installation integrates with VisionFIRE 3.x, CAD displays any matching VisionFIRE 3.x Site records. 3) ACS FIREHOUSE Interface window – If your installation integrates with ACS FIREHOUSE, CAD also returns any matching FIREHOUSE records. 4) FIRE 5.x Interface window – With this interface, CAD also returns any matching FIRE 5.x records.



Page 92

Essentially, the system automatically performs an address search (based on call location) and goes directly to the Results tab of the FIRE 5.x Interface.


Refer to the previous section for more information on using this window.

Please note the method by which VisionCAD parses the call location value for the FIRE 5.x address search fields.

FIRE 5.x Search VisionCAD Call Location Data

Address/House Number

If the first word in the Call Location field is a valid CAD house number, the numeric portion of the number will be passed to the FIRE 5.x query for the Address Number parameter.

Street Prefix If the next word in the Call Location field (after house number) is a recognizable directional quadrant (N, NE, E, SE, S, SW, W, NW), then it will be passed to the FIRE 5.x query for the Street Prefix parameter.

Street Name All words in the Call Location field between the Street Prefix and Street Type are sent to the FIRE 5.x query for the Street Name parameter.

Street Type If the word in the Call Location field before Street Suffix is a recognizable US Postal Service street type, it is passed to



Page 93

FIRE 5.x Search VisionCAD Call Location Data FIRE 5.x as the Street Type parameter.

The US Postal Service street type list is taken from the USPS Postal Addressing Standards, Publication 28, July 2006, Appendix C: Street Abbreviations. The recognized values will be limited to the Postal Service Standard Suffix Abbreviation column of this publication.

Note: Please review these abbreviations in comparison to your street types conversions database, as this may be affected.

Street Suffix If the last word in the Call Location field is a recognizable directional quadrant (N, NE, E, SE, S, SW, W, NW), then it will be passed to the FIRE 5.x query for the Street Suffix parameter.

FIRE 5.x Connection Failure If the FIRE 5.x server connection fails when performing an automatic address search for Fire Plan alerts, CAD displays an error message to the user and disables the interface. Subsequent alert searches will no longer search FIRE 5.x or display the error message.

If you select the FIRE Search item from the View menu when the connection is disabled, a message is displayed on the query window. You can still attempt these searches even if the automatic search interface is disabled. If the connection fails, CAD displays an error message. You can attempt to re-enable the interface with new searches as often as desired. (A reset of CAD will not be necessary to re-enable the interface.)

Once the FIRE 5.x server connection is successful from the manual FIRE Search method, the interface is then re-enabled for both manual and automatic searches. (Subsequent alert searches will begin searching FIRE 5.x again.)

FIRE 5.x: OCA Export

Configuring the OCA Export Interface In order to use the FIRE 5.x OCA Export interface, the following option must be set in CAD Configuration.


RMS/FIRE FIRE 5x Export TCP Address

Global or Local

Enter the TCP/IP address and port number of the TCP server being hosted by the FIRE 5.x system’s CAD Listener server.



Page 94

Category Option Scope Value This should be entered in hostname:port format. This address is used for the OCA export of call data.

You must also complete the Export File Setup tab in the Department record for each department whose data you wish to export.

Export File Setup

To export VisionCAD call data to FIRE 5.x, place a checkmark in the Enabled field and the VisionFIRE 5.x Export field.

Note: For file export to occur, an OCA must be created. This requires that the OCA Number Setup tab be setup correctly. Refer to the Departments database set up in the chapter “General Edit” in the VisionCAD System Administrator User’s Guide for more information on this set up.

OCA Export Process CAD exports the call information to the TCP connection as specified in the “FIRE 5x Export TCP Address” configuration option. For each call exported, CAD emits the XML document types “INC01” (containing call information) and “INC02” (containing unit information). If multiple units from the same OCA-emitting department were assigned to the call, multiple unit records are exported within one INC02 document to the interface.



Page 95

This export occurs when:

• An OCA is created regardless of whether it is created manually or by one of the Auto Create options: On Dispatch or On Call Clear.

• A unit in a department with an OCA is assigned to the call. Assigning a unit from another department will not update the OCA files unless that department has an OCA.

• A unit is statused with BUS – Busy but Available.

• A unit is removed from the call.

• The call is cleared.

The following tables show the CAD fields exported with their associated XML element names used in the export.

Call Information (INC01) CAD Element XML Tag

call_oca_number.oca_number master_incident_number

active_calls.received_time response_date

active_calls.landmark location_name

active_calls.actual_incid_location address

-not used- Address2

active_calls.actual_incid_location (parsed) house_number

active_calls.actual_incid_location (parsed) prefix_directional

active_calls.actual_incid_location (parsed) name_component

active_calls.actual_incid_location (parsed) street_type

active_calls.actual_incid_location (parsed) post_directional

active_calls.floor building

active_calls.cross_street1 cross_street

active_calls.cross_street2 cross_street2

active_calls.actual_incid_city city

active_calls.actual_incid_state state



Page 96

CAD Element XML Tag

active_calls.actual_incid_zip postal_code

active_calls.ycoord latitude

active_calls.xcoord longitude

active_calls.caller_name caller_name

active_calls.phone_number call_back_phone

active_calls.caller_location +caller_apartment +caller_floor

caller_address

active_calls.complaint incident_type

agency_type

active_calls.time_dispatched time_first_unit_assigned

active_calls.time_enroute time_first_unit_enroute

active_calls.time_onscene time_first_unit_arrived

active_calls.time_complete time_callclosed

active_calls.narrative commentlist\comment

-generated- packageid

Unit Information (INC02) CAD Element XML Tag

active_calls.call_number master_incident_number

callunitdata.unit radio_name

callunitdata.dis time_assigned

callunitdata.enr time_enroute

callunitdata.ons time_arrivedatscene

callunitdata.lef time_depart_scene

callunitdata.arr time_arrive_destination



Page 97

CAD Element XML Tag

callunitdata.com time_call_cleared

callunitdata.rem time_cancelled

-generated- ackid

-generated- packageid

-generated- inc01packageid


Chapter 5. Using CAD Interfaces

Page 99

CHAPTER 5. USING CAD

INTERFACES

Overview

VisionCAD provides an interface to other TriTech applications and third-party applications. CAD Configuration options must be set and the external application must be installed and on the same network for the interface to function properly. Each interface has different setup requirements – read this chapter and the CAD Configuration chapter in the VisionCAD System Administrator User’s Guide.

This chapter includes information on the following TriTech and third-party interfaces:

• Third-Party RMS or Fire

• ACS FIREHOUSE Query Interface

• Alarm Interface

• CryWolf Interface

• HigherGround Logging Recorder Interface

• Paging

• EMD, EPD, EFD

• Printrak CAD

• VisionCAD Tear and Go Printing

• GTE Fire Interface

• Zetron Model 25

• Zetron Model 26



Page 100

Inform RMS and VisionFIRE Interfaces

VisionCAD works with TriTech’s RMS product, Inform RMS, as well as with VisionFIRE. You can transfer incident data and you can also perform searches of Warrants, Civil papers, and Incident information in the RMS database by clicking on the RMS button in CAD. Refer to the chapter in this book, “Chapter 4. Using RMS and Fire with CAD” for detailed information on using the RMS/Fire interface with CAD.

Inform Jail and Inform FBR Interfaces (Using the Data Store)

VisionCAD data may be published for reuse in TriTech’s JAIL product, Inform Jail, as well as with Inform FBR. This is available via the Data Store.

The Data Store is a SQL Server database that provides a central location for working with data while it is active in the VisionCAD Incident, VisionMOBILE, Inform FBR, or Inform Jail workflow. The key benefit of the Data Store is to provide the ability to reuse data from an event, person, property and vehicle that has been captured in one application, but has not completed the workflow process and therefore may not currently be available in another TriTech application.

Specifically, if your Data Store Server is set up in CAD Configuration, VisionCAD publishes call activity, person, and vehicle data to the Data Store for each OCA that is created and when a call is cleared.

Note: VisionCAD publishes data to the Data Store only for calls that have an OCA number assigned AND if the department sent a POL, SHE, or OTH unit category to the call.

The OCA Destination option must also be set to either RMS or CAD Internal. If the OCA Destination is set to RMS, then in addition to transferring information into Inform RMS Case and Calls for Services records, the CAD data is also published to the Data Store. If you wish to ONLY publish this information to the Data Store, then set the OCA Destination option to CAD Internal.

At this point, Inform Jail and Inform FBR users may access the data through the Data Selection Window to retrieve this data for reuse.



Page 101

Note: The Data Selection Window accessed from Inform FBR includes filters for user name and department. In order for these filters to properly display your data, you must consistently set up your users’ officer IDs, names, jurisdictions, and departments across each of the products that publish to the Data Store (Inform FBR, VisionCAD, VisionMOBILE, and Inform Jail).

Note: The remaining Public Safety Suite applications (VisionMOBILE, Inform RMS, and VisionFIRE) use more direct interfaces with VisionCAD, which are detailed in “Chapter 2. Using Mobile Interfaces” and “Chapter 4. Using RMS and Fire with CAD.”

Mapping Interfaces

VisionCAD works with GeoLynx mapping to provide a graphical tool for displaying call data. Refer to “Chapter 3. Using Maps” in this book for detailed information on using mapping with CAD.

NCIC Interface

VisionCAD can be set up to send NCIC (or some state-specific) queries and receive query returns based on the information related to a call. All NCIC activity is performed from the VisionMOBILE window, accessible by clicking on the MCT button on the main CAD Dispatch toolbar.

Refer to the section in this book, “NCIC Queries” for detailed information on using the NCIC interface with CAD.

Third-Party RMS or Fire Interface

You may use a third-party (non-TriTech) RMS or Fire interface, such as RAIN, with VisionCAD.

Note: In addition to the function this section describes, if you have purchased the ACS FIREHOUSE Interface then refer to the “ACS FIREHOUSE Query Interface” section for details on searching this third-party Fire system.



Page 102

To set up the interface, you must set the following CAD Configuration options:


RMS/FIRE RMS Interface Global No

You must also complete the Export File Setup tab in the Department record for each department whose data you wish to export.

Export File Setup

If you are exporting data to a third-party RMS or Fire, follow these steps to properly setup exports:

Step 1. To export VisionCAD call data into a file on the network for upload into a third-party application, click Enabled.

Step 2. In the Export File Output Path field, specify the full path to the network location where you want to store the exported data. For example, to store the files locally, you may set the path to C:\CAD Data. The folder must exist before you create an OCA number and export data. VisionCAD does not create this folder for you.

Step 3. Select the type of file you would like exported from the drop down menu: ASCII Text or XML. This option depends on the upload capabilities of the third-party application. Consult the documentation for that application or interface to determine the appropriate choice.



Page 103

Note: For file export to occur, an OCA must be created. This requires that the OCA Number Setup tab be setup correctly. File export occurs for any of the OCA destinations: CAD Internal, RMS, or Fire.

CAD creates a file of call data for transfer to the RMS or Fire system for every OCA number created in CAD. Files are named by the OCA number and a file type of OCA. For example, for a call with an OCA number of 12345, the file name would be 12345.oca and is located in the directory on the network specified in the Export File Output Path on the department record. Departments interfacing with a third-party RMS or Fire system should be set up with CAD Internal OCA numbers. You may choose to use the CAD Call number as OCA number. Refer to the Departments database set up in the chapter “General Edit” in the VisionCAD System Administrator User’s Guide for more information on this set up.

File Export A file is first exported when an OCA is created regardless of whether it is created manually or by one of the Auto Create options: On Dispatch or On Call Clear.

Whenever an OCA is created, all OCA files exported previously for that call are replaced. A new file is created for the new OCA. The file is named with the OCA number and the extension .xml for XML files or .oca for ASCII text files; the file is written in the directory configured for the department’s Export File Output Path.

After an OCA has been created for a department, all OCA files for the call are updated when:

• A unit in a department with an OCA is assigned to the call. Assigning a unit from another department will not update the OCA files unless that department has an OCA.

• A unit is statused with BUS – Busy but Available.

• A unit is removed from the call.

• The call is cleared.

The OCA files can be read simultaneously by third-party interfaces, as well as be written by multiple CAD workstations. Conflicts can potentially result if a file is locked for reading when CAD attempts to update it. If an error occurs while writing a file, CAD will wait for one second and then try again. This will occur up to two additional times. If VisionCAD fails to write the file, it presents an error message, “An error occurred while exporting the OCA file”, indicating the reason for failure. The message is the standard VisionCAD notification that can be acknowledged at a later time.



Page 104

OCA Export Error Message

When this occurs, warning and error messages are also emitted to the VSICAD.LOG file. If a call has multiple OCAs, the error does not prevent VisionCAD from updating the remaining files.

Export Enhancements To better facilitate operations in third-party RMS and Fire products, VisionCAD exports additional information in the OCA Export file. These extensions apply only to the XML formatted file. Because the ASCII file contains fixed-length fields, it cannot be changed without breaking third-party applications that read it; however, both kinds of files are updated when the units on the call change. Beginning with VisionCAD version 3.5 Update 3, the OCA Export feature provides the following enhancements:

• All Units within the OCA’s department participating in a call are exported. (XML)

• The BUS timestamp is exported for each unit. (XML)

• The OCA file is updated when a unit is assigned to the call, when a unit is statused BUS, and when a unit is removed. (XML or ASCII) Existing behavior updates the file when an OCA is created and when the call is cleared.

• The earliest timestamp of each distinct USR4 status is exported for each unit and for the call. (XML)

• The entire narrative and press release text is exported. (XML)

• All dispositions applied to the call are exported. (XML) All Persons attached to the call are exported. (XML) All Vehicles attached to the call are exported. (XML) The entire CLoc location history is exported. (XML)

• The first unit exported is the primary unit for the call, consistent with the ASCII export. (XML)

• Special characters in the narrative do not corrupt the XML. (XML)

• In case of file locking conflicts with a third-party receiver, CAD attempts to write the file up to three times. (XML or ASCII)

• Unit Log activity is displayed in the Call Log window and the Call Log pane of Full Call / Historical Edit



Page 105

ASCII Text The ASCII Text file is a fixed-format file that cannot be changed without affecting the external applications that read this file. The officers are exported to this file in a backward compatibility mode, where only one or two officers can be exported.

The officers exported are those provided by the backward compatibility feature in VisionCAD 3.5. VisionCAD will export as many name parts as will fit in the 40-character space defined for the officer names in Last, First, Middle, Suffix format.

This third-party transfer data dump consists of a main call record and related sub-records. The following list shows the fields included in the main record for the call and provides the maximum number of characters in each field. If a field does not contain a value it will be filled in with spaces.

Certain fields in this list are actually sub-records of the call and contain more information. For these fields, the number indicates the maximum number of sub-records that can be included in the data dump. The details of each sub-record are presented in lists following the main.

The following list shows the fields included in the third-party data dump from CAD in the order they occur and provides the maximum number of characters in each field. If a field does not contain a value it will be filled in with spaces.

RMS - Main Call (11) Jurisdiction (10) Department (5) Complaint (15) Priority (1) Ten Code (3) Caller (40) Phone (12) Location (60) Apt (8) Floor (5) City (18) Call Owner (16) Call Taker (3) How (7) Alarm (12) Fire Grade (10) IRA (5) ESN (5) Run Fire (10)



Page 106

Run EMS (10) Tract (5) Dispatch Zone (5) First Unit (5) Time Received (19) Time Completed (19) Category (30) Press Release (255) Narrative (500) Alarm Type (20) * Units (5) * Person (5) * Vehicle (5) Disposition1 (4) Disposition2 (4) Disposition3 (4) Disposition4 (4) Disposition5 (4) OCA Number (20) Time OnScene (19) * Location (1)

Units Unit (5) Department (4) Shift (5) Officer ID (11) Officer Name (40) Station (10) Dispatch (19) Enroute (19) Onscene (19) Left Scene (19) Arrived Scene (19) Remove from Call (19)

Person Name (40) Sex (1) Race (1) DOB (10) Category (10)



Page 107

Vehicle Make (10) Model (10) Year (4) Plate (10) Plate State (2) Plate Year (4) VIN (20)

Locations Location (60) City (18)

XML Text The XML format is not fixed-length and extra officer data can be written to the file without breaking external applications that read this file. VisionCAD will export all officer IDs and Names attached to the unit in the existing officer ID and officer name elements, separated by slashes.

Element Structure This section describes the element structure of the XML format file. The root element of the file is cadcall and contains the other elements as described here.

Element Description

cadcall The root element of the file. It contains all other elements.

call Contains the call data in its attributes.

units Contains a sub-element for each unit assigned to the call.

unit1 The primary unit of the call. Contains the unit data in attributes.

unit2, unit3, etc. Additional units are numbered in alphabetical order.

persons Contains a sub-element for each person attached to the call.

person1 Contains the person data in attributes.

person2, person3, etc.

Additional persons are numbered in the order created.



Page 108

Element Description

vehicles Contains a sub-element for each vehicle attached to the call.

vehicle1 Contains the vehicle data in attributes.

vehicle2, vehicle3, etc.

Additional vehicles are numbered in the order created.

location Contains a sub-element for each location in CLoc history.

location1 Contains the location data in attributes.

location2, location3, etc.

Additional locations are numbered in the order created.

Fields Exported The following tables list the fields that are exported during the XML export process and describe the XML attributes according to the element with which they are associated.

Call The following table examines the call elements found in the Active_Calls table.

Attribute Description

callnumber The call number.

jurisdiction The CAD jurisdiction being exported from.

department The OCA department.

complaint The complaint type code.

priority The CAD Code for Priority.

calltencode The Ten Code associated with the complaint.

callername The caller name as entered in the Caller Name field.

phonenumber The caller phone number.

altphonenumber The alternate phone number.

actualincidlocation The incident’s street address.

actualincidapartment The incident’s apartment.



Page 109


floor The incident’s floor.

actualincidcity The incident’s city.

actualincidstate The incident’s state.

actualincidzip The incident’s zip.

lowercrossstreet The lower cross street according to the GEO database for the incident location.

uppercrossstreet The upper cross street according to the GEO database for the incident location.

ycoord The Y-coordinate of the address.

xcoord The X-coordinate of the address.

zcoord The Z-coordinate of the address.

callowner The CAD login ID of the call owner.

calltaker The CAD login ID of the call creator.

howreceived The CAD Code for How Received.

alarmcode The residential alarm code.

firegrade The CAD Code for Alarm Grade.

ira The IRA code determined from geo-validation.

esn The Emergency Service Number.

runzonefire The Fire Run Zone code determined from the IRA.

runzoneems The EMS Run Zone code determined from the IRA.

tract The Reporting Tract code determined from the IRA.

dispzone The CAD Code for Dispatch Zone.

firstunit The Unit ID of the primary unit.

timeali The timestamp when the call data was received from the ALI/AN I feed. If the call is manually entered without an ALI receipt, the timestamp is the date that the call was created,



Page 110

Attribute Description e.g. 01/17/2008 00:00:00. If the call is a Misc Call, the timestamp is blank. (A future release may make this blank for all non-ALI calls.)

For this and following timestamps, if there is no time, the attribute is present but empty.

All timestamps are in the format of mm/dd/yyyy hh:mm:ss, 24-hour time.

datereceived The timestamp when the call was received (when the operator begins entering data).

timetransmitted The timestamp when the call was first saved, whether by the Xmit button or Save button.

timedispatched The earliest dispatch time of any unit.

timeenroute The earliest enroute time of any unit.

timeonscene The earliest onscene time of any unit.

timedepart The earliest LEF status time of any unit.

timedestination The earliest ARR status time of any unit.

timecomplete The time that the call is cleared.

usrXXX The earliest time of all distinct user statuses of all units. There is a usrXXX attribute for each distinct status where XXX is a user status CAD Code.

Note: Punctuation characters and spaces cannot be used in an XML attribute name, so the code used for the status should contain only letters and numbers. The VisionCAD Code screen will not restrict the input (so as not to affect existing codes), but punctuation in the codes will affect the export.

categories The categories of the call separated by a period, e.g. POL.SHE.FIR. Possible categories are: POL, SHE, FIR, EMS, RES, FIR, OTH.

nature The press release text of the call.

narrative The narrative text of the call.



Page 111


alarmtype The CAD Code for Alarm Type. This is associated with the alarm code.

ocanumber The OCA number.

dispositionX There is a numbered disposition attribute for every disposition applied to the call. The dispositions are numbered in the order they were created, e.g. disposition_1=REPT, disposition_2=WARN, disposition_3=TICK

XML Call Attributes

Unit The following table examines the unit elements found in the Units table and Units window.


unit The unit code.

department The department to which this unit belongs.

shift The work shift that this unit is assigned to.

officerid All officer IDs attached to the unit separated by a slash.

officername All officer names attached to the unit in Last-First-Middle format separated by a slash, e.g. SCHNAUSER, LEO/LACEY, MARY/TOODY, GUNTHER/MULDOON, FRANCIS

station The unit station.

dis The earliest timestamp for Dispatch status. For this and the following timestamps, if a status does not occur, the corresponding attribute is missing from the XML file.

enr The earliest timestamp for Enroute status.

ons The earliest timestamp for Onscene status.

lef The earliest timestamp for Left Scene status.

arr The earliest timestamp for Arrived Secondary Location status.



Page 112


bus The earliest timestamp for Busy But Available status.

com The earliest timestamp for the Complete status, which occurs if the unit is on a call when it is cleared.

rem The earliest timestamp for the Removed status, which occurs when a unit is removed. If the unit is restored to the call and statused “Complete”, the REM timestamp does not appear; only the COM timestamp does.

usrXXX

The earliest timestamp for all distinct user statuses where XXX is any distinct user status applied to the unit. If the same status is used multiple times, the earliest timestamp is exported, consistent with the standard timestamps DIS, ENR, etc.

For example, a user status of “PAT” is exported using an attribute of usrpat

Note: Punctuation characters and spaces cannot be used in an XML attribute name, so the code used for the status should contain only letters and numbers. The VisionCAD Code screen will not restrict the input (so as not to affect existing codes), but punctuation in the codes will affect the export.

XML Unit Source Attributes

Person The following table examines the person elements found in the Call_Persons table and Subjects/Locations/Vehicles windows.


name The person’s name in first-last format, containing just the first name and the last name. If no name is specified, the Business Name field is exported here.

sex The sex CAD Code.

race The race CAD Code.

ethnic The ethnicity CAD Code.

dob The date of birth in mm/dd/yyyy format.



Page 113


category The person category CAD Code as specified in the Role field.

location The person’s street address.

apartment The person’s apartment.

floor The person’s floor.

city The person’s city.

state The person’s state.

zip The person’s zip.

phone The person’s phone number.

XML Person Source Attributes

Vehicle The following table examines the vehicle elements found in the Call_Vehicles table and Subjects/Locations/Vehicles windows.


vmake The vehicle make.

vmodel The vehicle model.

vyear The vehicle year.

vtag The vehicle tag.

vstate The vehicle state.

vtagyear The vehicles tag year.

vvin The vehicles VIN.

XML Vehicle Source Attributes

Location The following table examines the Location elements found in the Call_Locations table and Subjects/Locations/Vehicles windows.



Page 114


location The call’s street address before the location change. If the call has apt/floor values, they are part of the location text, e.g. 205 MAIN STREET, Apt/Ste 210, Flr/Bldg 2

city The call’s city before the location change.

XML Location Source Attributes

ACS FIREHOUSE Query Interface

This interface queries site data from the third-party ACS FIREHOUSE Software system.

This section covers the configuration and use of the query interface. This document does not describe the FIREHOUSE Software application. Consult the documentation that came with that product for those instructions.

Note: Before you begin, you will need the authorized license key provided by TriTech for each workstation that will query FIREHOUSE.

FIREHOUSE Configuration Utility To enable the communications between each CAD workstation and the FIREHOUSE SQL server, the FIREHOUSE Configuration Utility must be set up on each CAD workstation. The Configuration Utility is automatically installed with each installation of the VisionCAD Installation CD and is available from the Local Configuration, File menu.

Use the following procedure to set up CAD workstations to query FIREHOUSE data.

Note: This option is only available from Local Configuration.

Step 1. From Local Configuration, choose File, then Interfaces.

Step 2. The Configuration window displays.



Page 115

Step 3. Click on the FIREHOUSE tab to display the Interfaces Configuration Console.

Note: If this is the first time accessing this window a message displays informing you that the associated registry key could not be opened. Merely click OK. After completing the remainder of these steps, this message will no longer be applicable.

Step 4. Use the following descriptions to enter parameters.

Field Description

Enabled Check this field if interfacing with FIREHOUSE. If enabled, the item “ACS FIREHOUSE Search” is added to the View menu in CAD Dispatch, which displays the FIREHOUSE query screen. Additionally, this option enables the automatic Fire Plan alert search of the FIREHOUSE database.

Note: In addition to setting this option you must also have an authorized license key to enable this interface.

SQL Server Enter the name of the Microsoft SQL Server that holds the FIREHOUSE data. (The dropdown is filled with SQL Server names visible from the workstation. The entry field will fill with the closest match as you type, but you are not restricted to items in the list for a server name.)



Page 116

Field Description

Database Name Enter the name of the database in the FIREHOUSE server that contains the stored procedure (FH_QueryOccup) provided by ACS.

Connect Using Enter the authentication method for connection with the FIREHOUSE SQL server. Choose the method that is recommended by ACS for their server.

Login Name, Password

If the recommended method of authentication is SQL Server, enter the login name and password of the FIREHOUSE server.

License Key, Set Button

Click the Set button and paste the license key into this field. An authorized license key will be provided by TriTech. (The License Key field is read-only until you press the Set button. This extra step prevents inadvertently changing the key value.)

Note: You must have an authorized license key to enable this interface. A license key must be generated per workstation. The license is tied to the machine name and to one or more jurisdictions. This prevents the interface from being used on a different machine in the same jurisdiction or on another machine with the same name at a different jurisdiction (agency).

All Users? Check this field to save this configuration for all users of the machine. You may need administrative rights to save for all users. Uncheck this field to save this configuration in the registry for only the current user.

Note: When CAD Dispatch loads this configuration, it will first attempt to load a configuration for the current user. If there is none, it will load the configuration for all users. This allows for a custom configuration for a single user, if desired.

Step 5. Click Save. This is stored in the registry based on the All Users field.



Page 117

Note: To remove this configuration from the registry, press the Remove button. This removes from the registry based on the All Users field. If you have accidentally saved with All Users checked and then again with All Users unchecked please note that two separate configurations will now exist in the Windows registry. As previously noted, when CAD Dispatch loads this configuration, it will first attempt to load a configuration for the current user. Since you have both keys accidentally created the current user configuration will be used, ignoring the all users configuration. Therefore, if the all users configuration is the desired method you MUST delete the erroneous configuration. To do so, make sure the All Users field is unchecked and press Remove.

Step 6. If you choose to open Local Configuration from within CAD Dispatch, you must reset CAD to invoke any changes you have made. If CAD does not prompt you to reset, then select Reset from the File menu to do so.

Using the FIREHOUSE Interface The FIREHOUSE Interface provides the following main functions:

• Manual Searches: From the View menu in CAD Dispatch, an ACS FIREHOUSE Search option is enabled to access the FIREHOUSE query screen.

• Automatic Searches: From calls windows in CAD Dispatch, the automatic Fire Plan alert is enabled to search the FIREHOUSE database.

ACS FIREHOUSE Search From the main CAD Dispatch screen, select View from the CAD menu bar, then ACS FIREHOUSE Search. The interface window displays from which you can search FIREHOUSE data based on either occupancy ID or address.

Note: The manner and method of searching is controlled by the FIREHOUSE server. This search window merely provides a graphical interface to access the ACS FIREHOUSE server and query routine. The ACS FIREHOUSE query routine appears to search by exact match on the supplied fields.

From the Search tab:

• To do a search based on occupancy ID, enter a value into the Occupancy ID field. Then simply select the Search button or press Enter. (Typing in this field disables the remaining fields. To enable all fields and perform an address based search press the Clear All button.)

• To do a search based on address, enter an address number and street name, and if desired as much of the remaining address fields. Select the Search button or press



Page 118

Enter. (Typing in any address field disables the occupancy field. To enable all fields and perform an occupancy based search press the Clear All button.)

This interface window also includes Clear All and Cancel buttons. Press Clear All to clear the values entered in the search fields. Use Cancel to close the window without searching.

Search tab

After pressing Search, if site data is found, the Results tab is automatically displayed; otherwise, a message displays informing you that no search results were found. The Results tab displays a summary list of sites matching your search criteria. For each site, summary lists of any contacts and preplans attached to the selected site also display.

Note: Again, please note the data fields displayed are controlled by the ACS FIREHOUSE server and query routine.



Page 119


From the Results tab you can double-click (or press Enter) on any summary record (site, contact, or preplan) to quickly access its more detailed information on the Site, Contact, or Preplan tabs.

The detail tabs show all the field detail in text form with field name listed on the left and actual data for each field listed on the right. If a field has no data, it is not displayed. Many of the fields provided by FIREHOUSE are combined into one line on the display for better readability. For example, the Location field actually combines from multiple location fields: number, st_prefix, street, st_type, st_suffix. Similarly, code/description fields are also paired on one line for better readability. In the figure below, Response District actually displays the response district code (HQ) together with the description (HEADQUARTERS).



Page 120

Site tab (Detailed Results)

The Contact tab shows the contact data for the Site currently selected on the Site grids.

Contact tab (Detailed Results)



Page 121

The Preplan tab shows the preplan data for the Site currently selected on the Site grids.

Preplan tab (Detailed Results)

Note: The Preplan Notes field is a free-form text field in the FIREHOUSE server. The field text displayed on the detailed preplan results tab will be shown with the line-breaks and spacing as formatted in the FIREHOUSE database.

Viewing Fire Plans from FIREHOUSE With this interface, you will be alerted if the VisionCAD call location matches FIREHOUSE Site records. From the various call windows (Edit Call, Miscellaneous, Traffic Stop, etc.) click the Fire Plan field to view these preplans.

Note: Potentially you may receive several different windows to view fire plans. 1) VisionCAD Fire Plans window – CAD retrieves any matching CAD Internal ALI Fire Plans. 2) Site Browse (VisionFIRE 3.x) window – If your installation integrates with VisionFIRE 3.x, CAD displays any matching VisionFIRE 3.x Site records. 3) ACS FIREHOUSE Interface window – With this interface, CAD also returns any matching FIREHOUSE records. 4) FIRE 5.x Interface window – If your installation integrates with Fire 5.x, CAD also returns any matching FIRE 5.x records.



Page 122

Essentially, the system automatically performs an address search (based on call location) and goes directly to the Results tab of the ACS FIREHOUSE Interface.


Refer to the previous section for more information on using this window.

Please note the method by which VisionCAD parses the call location value for the FIREHOUSE address search fields.

FIREHOUSE Search VisionCAD Call Location Data

Address Number If the first word in the Call Location field is a valid CAD house number, the numeric portion of the number will be passed to the FIREHOUSE query for the Address Number parameter.

Street Prefix If the next word in the Call Location field is a recognizable directional quadrant (N, NE, E, SE, S, SW, W, NW), then it will be passed to the FIREHOUSE query for the Street Prefix parameter.

Street Name All words in the Call Location field between the Street Prefix and Street Type are sent to the FIREHOUSE query for the Street Name parameter.

Street Type If the word in the Call Location field before Street Suffix is a recognizable US Postal Service street type, it is passed to FIREHOUSE as the Street Type parameter.



Page 123

FIREHOUSE Search VisionCAD Call Location Data

The US Postal Service street type list is taken from the USPS Postal Addressing Standards, Publication 28, July 2006, Appendix C: Street Abbreviations. The recognized values will be limited to the Postal Service Standard Suffix Abbreviation column of this publication.

Note: Please review these abbreviations in comparison to your street types conversions database, as this may be affected.

Street Suffix If the last word in the Call Location field is a recognizable directional quadrant (N, NE, E, SE, S, SW, W, NW), then it will be passed to the FIREHOUSE query for the Street Suffix parameter.

FIREHOUSE Connection Failure If the FIREHOUSE server connection fails when performing an automatic address search for Fire Plan alerts, CAD displays an error message to the user and disables the interface. Subsequent alert searches will no longer search FIREHOUSE or display the error message.

If you select the ACS FIREHOUSE Search item from the View menu when the connection is disabled, a message is displayed on the query window. You can still attempt these searches even if the automatic search interface is disabled. If the connection fails, CAD displays an error message. You can attempt to re-enable the interface with new searches as often as desired. (A reset of CAD will not be necessary to re-enable the interface.)

Once the FIREHOUSE server connection is successful from the manual ACS FIREHOUSE Search method, the interface is then re-enabled for both manual and automatic searches. (Subsequent alert searches will begin searching FIREHOUSE again.)

Alarm Interface

Before you can use the Alarm Interface in VisionCAD, you must configure the workstation. The following section details the steps required to set up the interface and CAD.



Page 124

Set up There is no extra installation required for the Alarm Interface, it is installed automatically with the CAD Client Installation. It would be beneficial, however, to add the Interface to the list of programs launched at start up for the workstation(s) taking alarm calls. Consult your Windows Documentation or Online Help files for instructions.

Once the installation is complete, you must configure the interface. The following sections detail this configuration process.

Set Port Step 1. Use the shortcuts provided to start the Alarm Interface.

Step 2. The Alarm Interface will default to minimized, so select the application from your task bar to maximize the window.

Step 3. The Alarm Interface window displays.



Page 125

Step 4. From the Configure menu, select Set Port. The following box displays.

Step 5. Use this table to complete this portion of the set up.

Option Description

In Use Place a checkmark in this box if this is the primary workstation for alarm calls. This will notify the CAD Dispatch module to look for the dump file from the intermediate machine. For details on this function see the chapter "Dispatch" in the VisionCAD Telecommunicator User's Guide.

Port Enter the Port to which the intermediate machine is connected via the RS232 cable.

Default is 2.

Baud Select the Baud rate from the drop down menu.

Default is 9600.

Data Bits Select the Data Bits from the drop down menu.

Default is 8.

Parity Select the Parity from the drop down menu.

Default is pNone.



Page 126

Option Description

Stop Bits Select the Stop Bits from the drop down menu.

Flow Control Select the Flow Control from the drop down menu.

Step 6. When you have finished, click OK. To exit without making changes, click Cancel.

General Edit The following sections describe how you can use the General Edit module in VisionCAD to get the most out of the interface between the Alarm System and VisionCAD Dispatch.

Complaint Types The system administrator should follow the instructions in the VisionCAD System Administrator User’s Guide to create Complaint Types in General Edit that directly correspond to the codes for each Alarm Type. This may or may not include setting up Run Cards and Special Units for each new Complaint Type.

Internal ALI You may wish to create Internal ALI records for each Alarm location in your system. Internal ALI keys off of the phone number and the alarm code as entered in the New Call window. If you want additional information for alarm locations, create the Internal ALI record and enter the information there. For further instructions, consult the VisionCAD System Administrator User’s Guide.

CryWolf Interface

Note: The CryWolf interface is an add-on that is not available unless your agency has purchased this feature. This section covers the CryWolf interface only. This document does not describe the third-party Public Safety Corporation’s CryWolf software application. Consult the documentation that came with that product for those instructions.

This interface enables the transfer of alarm and premise data between VisionCAD and the third-party CryWolf False Alarm system. This interface is an optional, configurable Windows service.



Page 127

This interface consists of the following two data exchanges:

• VisionCAD Alarm Incident data is exported for reuse by the CryWolf system.

This data is exported into a comma-separated text file, which is delivered to a specific network directory folder location that is accessible by both VisionCAD and CryWolf. This data transfer process will be scheduled to export daily VisionCAD data, at a set time each day.

• CryWolf Alarm Site data is transferred to VisionCAD’s Internal ALI database.

CryWolf will provide access to VisionCAD to transfer selected alarm permit data.

Installing the CryWolf Interface The following steps describe how to install the CryWolf interface services.


Step 2. Locate and manually start up VSICIEInstall.exe from the CD.






Page 128


Step 7. On the Customer Information form, enter your user name and organization.




Page 129

Step 9. The Setup Type form displays.

Step 10. Choose your setup type (typically Complete) and click Next to continue the installation process. Choosing Complete installs both the CryWolf Interface and its Monitoring application.

CryWolf Interface – This feature installs two Windows services and the configuration program.

VisionCAD Access Portal – This is a required, supporting Windows service for the VisionCAD CryWolf service.

VisionCAD CryWolf – This is the Windows service that interfaces with the third-party Public Safety Corporation’s CryWolf application.

CAD Interface Engine (CIE) Monitor – This feature installs a program that can be used to monitor the operation of these Windows services. This feature can be installed on any machine on the network and is able to monitor the operation of an interface machine remotely.



Page 130





Page 131



At this point, if you chose complete as your setup type there will be two new services in the Windows Service Control window and both a configuration and monitoring tool will be accessible from your start menu.

• VisionCAD Access Portal

• VisionCAD Crywolf Interface

You must use the configuration tool at this point to configure the operation of the two new services and ensure they are started. Without configuration, the services will just sit dormant waiting for operational parameters.

Note: The following additional services may also be installed: “VisionCAD Deccan LiveMUM Interface,” “VisionCAD GenSpout Interface,” “VisionCAD Higher Ground Interface,” and “VisionCAD M/A COM CADLink Interface.” If started, these should be stopped, unless you are also using these interfaces.

If you did not check the box on the final install screen to launch this configuration tool, then refer to the next section for details.

Configuring the CryWolf Interface The following figures and tables describe how to configure the VisionCAD Access Portal (CAP) and VisionCAD CryWolf Interface services.



Page 132

From the Windows Start menu, select VisionAIR, VisionCAD CIE, then Vision CIE Config.

Field Description

Default Jurisdiction Enter the live jurisdiction in VisionCAD. Third-party requests submitted to the VisionCAD Access Portal (CAP) may contain a Jurisdiction parameter in the event that the external system interfaces with two live jurisdictions. However, the parameter is optional. CAP requests that do not contain a jurisdiction will operate on the default jurisdiction specified here. This removes the need to configure third-party interfaces with a jurisdiction when it is intended to work with the only existing live jurisdiction.

CAP Server Port The VisionCAD Access Portal (CAP) service hosts a TCP server port to accept third-party connections to the interface. The port number is specified here. The default value is 6002. It may be changed if 6002 conflicts with a server port number used by another application on the same computer.

SQL Server Enter the SQL Server name containing the VisionCAD databases. The dropdown is filled with SQL Server names visible to the configuration program at the time it is run. The edit field prefills with the closest match as you type, but you are not restricted to using entries in the server list.



Page 133

Field Description

Connect Using Select the connection method for connecting to SQL Server.

Note: A service is executed using a Windows system account. When using the Windows authentication option, you must ensure that the SQL Server’s authentication list is configured to allow the actual system account being used or set the service properties in the Service Control Manager to logon as a specified user. For whichever method chosen, ensure that the SQL Server account being used has the necessary SQL permissions to operate on the VisionCAD tables for assigning units, updating statuses, adding to the unit log, etc. Consider using the CADSupers or CADDisps group for this purpose.

Login Name Enter the login name if SQL Server authentication method is chosen. This field is disabled if Windows authentication is selected.

Password Enter the password if SQL Server authentication method is chosen. The password is stored in an encrypted form. This field is disabled if Windows authentication is selected.

Save the changes before closing this window. The settings are stored into the Windows registry. (The remove button deletes this registry key.)

Whenever the configuration is changed, you must stop and restart the VisionCAD Access Portal (CAP) service for it to recognize the new values. The Stop/Start buttons are provided for this purpose. You can also do this in the Windows Services window available through the Control Panel. If the service is running when the Save button is clicked, you are prompted with a confirmation dialog.

Clicking Yes will save the configuration changes. You must stop and restart the service for the new values to take effect. Clicking No will not save the changes, which allows you to stop the service before saving the changes.



Page 134

Field Description

Remote CAD Access Hostname

Enter the IP address or name of the computer hosting the VisionCAD Access Portal (CAP) service. The CryWolf service connects to this address to send CAP requests. This value defaults to localhost for the local computer. However, the services may be activated on different computers if circumstances dictate such.

Remote CAD Access Port

Enter the port number of the VisionCAD Access Portal (CAP) TCP Server port. This value must match the value configured on the CAP page for CAP Server Port (on the machine where the CAP service is operating).

Import Time This displays the time of day when the CryWolf service should import the previous day’s updates. The format is 24-hour time. (For example, 1PM should be entered as 13:00.) The default value is noon.

Note: This value does not limit when the import will occur. If the service is behind by more than a day, it will import each day’s data continuously until it is caught up. Once caught up, it will not import the prior day’s updates until this time of day is reached. In normal, successful operation, the import will occur once every day at the configured time to import the prior day’s updates.



Page 135

Field Description

Last Successful Import Date

This displays the date of the last successful data import. This value controls what day’s updates the service will ask for on its next request. Records updated on this date are considered already imported into the VisionCAD database. The default value is the prior day so that the service will get “today’s” updates when the import time is reached “tomorrow.”

Note: When installing the service at a site where there is a backlog of CryWolf history, this value can be set to the day before the earliest updated date in CryWolf to cause the service to request updates on all the prior days. Be aware that when the service is started with a past date configuration, it will request data continuously from the PSC webservice for each past day until it is caught up. To validate a new installation when there is a backlog, you may want to set the date one day prior (the day before yesterday) to verify that the service will operate properly without hanging it up on a long series of import requests. It will not harm anything to import the same records twice. Note that as the service continually checks and changes this value during operation, you should stop the service before changing it. If the service is in the middle of a batch, any change you make will be lost when the batch finishes and the date is updated.

CryWolf SOAP Service URL

Enter the URL of the webservice provided by PSC (Public Safety Corporation). It will be a value like http://webservername/CWWebService/Service.asmx.

The webservice is installed and maintained by PSC for access into their CryWolf database. The URL is determined by how it is configured and installed on the web server used for the purpose. The CryWolf service will access this URL using the SOAP protocol (Simple Object Access Protocol). The machine on which the CryWolf service is installed must have the ability to reach the PSC’s webservice using the standard HTTP networking protocol. The URL can be tested with the Test URL button. If the URL is operating correctly, the test button displays a dialog with the version information of the webservice.

Debug Server Port Enter the port number of the debug server socket. The CryWolf service provides a TCP server port to which a debug monitoring utility can connect. Informational messages are sent over this connection which will be useful for monitoring the operation of the interface. The default value is 6004. It may be changed if 6004 conflicts with a server port used by



Page 136

Field Description another application on the same computer.


Whenever the configuration is changed, you must stop and restart the CryWolf service for it to recognize the new values. The Stop/Start buttons are provided for this purpose. You can also do this in the Windows Services window available through the Control Panel. If the service is running when the Save button is clicked, you are prompted with a confirmation dialog.

Clicking Yes will save the configuration changes. You must stop and restart the service for the new values to take effect. Clicking No will not save the changes, which allows you to stop the service before saving the changes. If you are changing the Last Successful Import Date, you should stop the service before changing it. Otherwise, the running service may possibly overwrite the date that you set as it processes the daily batches.

Using the CryWolf Interface Once configured, there is no additional user interface for these services. While operating, the CryWolf service checks once per minute to see if it needs to request a day’s updates from the PSC (Public Safety Corporation) webservice. The Last Successful Import Date determines whether it is “behind” or not.

For example, the machine may inadvertently be off for a few days. If the service is behind, it will immediately request the subsequent day’s updates and import the records into the Internal ALI table, one at a time, until the entire batch is imported. It will repeat this process until all data is imported and it must wait until the following day’s Import Time to arrive to request the current day’s updates. For example, if the service is started at 8:00 AM on 11/19/2008 and the Last Successful Import Date is 11/14/2008 with an Import Time of 12:00 (noon), the following actions will occur.

Step 1. On its next periodic check (each minute), the service will request the CryWolf updates for 11/15/2008.



Page 137

Step 2. All records returned from the webservice will be submitted, one at a time, to the VisionCAD Access Portal (CAP) service to be imported in the Internal ALI table. If an error occurs, the CryWolf service will resubmit the CAP request up to three times before discarding the batch. If the batch is discarded, it will try again on its next periodic check.

Step 3. After a batch is successfully imported, the Last Successful Import Date is updated to 11/15/2008.

Step 4. The above process is repeated for 11/16 and 11/17, but not 11/18. (It’s not yet noon.)

Step 5. When the Import Time of noon passes (on 11/19), the service will request the CryWolf updates for 11/18/2008 and import the records as described above.

Step 6. The service will sit dormant until the next day’s Import Time passes, and the import process is repeated again to obtain the data for 11/19.

VisionCAD Fields Updated from CryWolf The following fields are updated in VisionCAD based on the data transferred from CryWolf.

VisionCAD Internal ALI Field CryWolf Field

Alarm Code

Note: This field should not be updated by a VisionCAD user as it will cause the Internal ALI record to become out-of-sync with the CryWolf data.

Alarm Account Number (Permit Number)

Note: The CryWolf Account Number controls how records are identified. For each imported record, the service looks for an existing record holding the account number. If the account number is not found, a new Internal ALI record is created. Otherwise, the existing record is updated. The CryWolf Account Number is stored in the Alarm Code field of Internal ALI.

Location The primary street address of the CryWolf registration record.

Apt/Suite The Suite number for the registration record.

City, State, Zip The City, State, Zip of the primary address



Page 138

VisionCAD Internal ALI Field CryWolf Field of the registration record.

Special Comment Contains the registration status, the number of false alarm counts, and the last updated date of the registration.

Alarm Company Alarm company listed as the monitoring company in CryWolf.

Alarm Type Type of the registration record as stored in CryWolf. This can be “Residential,” “Commercial,” etc. according to the custom values used in CryWolf.

Type The text “Interfaced” to provide a way to filter on CryWolf interfaced records.

Business Name The Registration name of the CryWolf record. CryWolf stores a person’s last name or a business name in the same field. Hence, this field in Internal ALI can be either a company or a person. If the First Name field is filled in CryWolf, the CryWolf interface combines them together so that the business name field in Internal ALI can be values like:

WACHOVIA BANK (business) or SMITH,JOHN (person)



Page 139

Note: The phone number field is not filled in. The registered phone number in CryWolf can be anything entered by the user. It is not controlled for uniqueness and serves a different purpose than the Internal ALI phone number. The Internal ALI phone number must be unique, because it supports the phone number locator feature whereby the location of a new call can be set by querying on the phone number.

The newly imported Internal ALI records will not be visible to CAD workstations until a Global Refresh is performed. The service does not automatically perform a Global Refresh to avoid interfering with a CAD Administrator who may be cleaning up Geo data or performing some other Geo-related work for an extended period of time.

A Global Refresh must be performed daily or as desired to make the new CryWolf updates visible to CAD workstations. A future update of CAD may show when there is updated geo/internal-ALI data that needs to be refreshed, perhaps by highlighting the Global Refresh button or by showing a balloon notification.

Monitoring the CryWolf Interface A monitoring utility allows for troubleshooting the operation of the CryWolf interface services by displaying activity messages emitted by the debugging server sockets of those services. This utility may be placed on any network-accessible computer to observe the activity from a remote location.

From the Windows Start menu, select VisionAIR, VisionCAD CIE, and then Vision CIE Monitor.



Page 140

The monitor may be connected to each service independently.

• For the CAD Access Port section, fill in the IP address or name of the computer that is hosting the CAD Access Port service. The port number must match the port number configured in CAD Server Port on the CAP configuration tab. Click the Connect button to connect to the service. Thereafter, the CAD Access Port service sends activity messages of its operation over the connection.

• For the CryWolf section, fill in the IP address or name of the computer that is hosting the CryWolf interface service. As the two services are currently bundled together, this will usually be the same as the CAD Access Port IP address used above. The port number must match the port number configured in Debug Server Port on the CryWolf configuration tab. Click the Connect button to connect to the service.

When the monitor first connects to any service, the service emits the most recent 50 messages stored in its buffer. This allows for starting the monitor utility after observing an anomaly and seeing the event messages that may explain its occurrence, reducing the need to duplicate the anomaly again to see the causes. Afterwards, the monitor continues to collect event messages as they are emitted from the services. The monitor displays up to 2,000 events before it begins deleting the oldest entries in favor of new entries.

The VisionCAD Access Portal (CAP) service logs events to a local VSICIE.LOG data file using the standard logging mechanism also used by VisionCAD. The LOG file is stored in the same directory as the VSICIE.EXE file. The data will be logged until the file reaches its maximum configured size, default 512K. After reaching this size, the logging will wrap around to the beginning of the file. The CryWolf service stores its log file in VSICryWolf.LOG in the same directory as the VSICryWolf.EXE file.



Page 141

The data values shown for an event message are described in the table below.

Field Description

Time The time displays in the ISO 8601 standard, yyyy-mm-ddThh:mm:ss.zzz. The grid is kept sorted by this data column. Consequently, if you connect to one service, receive some messages for a while, then connect to the other service, you don’t see the most recent 50 messages from the second service appearing all at the end. They will be inserted into the grid record in order of time.

Source The source of the event. This may be CAP, CryWolf, or VSICIEMon. The monitor itself shows its own errors as events sourced from VSICIEMon so that error dialogs won’t popup while it is left running unattended.

Context This is for troubleshooting error messages, and typically displays the involved code function name that is meaningful for programming engineers.

Text The descriptive text of the event. In addition to error messages described in the “Exception Data Messages and Troubleshooting” section, many other activity messages may display.

Data If the event has associated binary data, the data is shown here in printable form. This is typically used to show the raw data received from the CryWolf product.

If the Follow checkbox is checked, the grid record selector will track each new message as it is received from the services. Unchecking this checkbox allows you to browse the grid without having the record selector jumping to the end on each new message.

The Clear button clears the activity messages currently being displayed from the grid. If a filter is active, it does not clear the records hidden by the filter.



Page 142

Filtering the Monitor

The filter button ( ) displays a dialog that can be used to filter the display by desired criteria.

This dialog can be used to filter for particular error text in the event data, filter the events by a particular source, and other such troubleshooting needs.

When a filter is active, the filter button is highlighted red.

To fully clear the filter, open the filter dialog and clear the items from the filter field list.

(Press the button, and then from the filter dialog that displays press

and .) If activities on the services are not showing event messages like you expect, verify that a filter setting is not excluding the messages from displaying.

Filter settings do not affect the 2,000 entry limit on the monitor display. If the filter is currently allowing only one record to be displayed, for example, the monitor utility still holds up to 2,000 total messages internally, visible or invisible.

Exception Data Messages and Troubleshooting This section details common error and warning messages, each followed by a description.

• Error Message: The jurisdiction "xxx" is not valid.

The default jurisdiction set in the configuration is not a jurisdiction listed in the CAD Jurisdictions table or an external service provided an incorrect jurisdiction in a VisionCAD Access Portal (CAP) request.



Page 143

• Error Message: Batch "mm/dd/yyyy" was aborted while processing record xx of yy

The CryWolf service was unable to complete the processing of a batch. This may occur because the VisionCAD Access Portal (CAP) network socket was disconnected or there were excessive retries on a single record. The batch will be attempted again on a later periodic check.

• Error Message: Webservice returned error response: xxxx

The CryWolf webservice returned an error in the SOAP (Simple Object Access Protocol) call to get a batch of updates. There will be additional descriptive text, such as “HTTP/1.1 500 Internal Server Error” and perhaps the SOAP XML fault data providing details of the error.

• Error Message: Maximum retry limit exceeded. Batch processing is being discontinued.

The VisionCAD Access Portal (CAP) service returned an excessive number of errors while attempting to import a CryWolf record. The entire batch will be aborted and the CryWolf service will retry the batch later.

• Warning Message: Unable to import record alarm number xxx: <message>

The VisionCAD Access Portal (CAP) service returned an error while attempting to import a CryWolf record. The CryWolf service will retry the record up to three times before aborting the batch.

• Error Message: The SOAP URL is missing. Unable to query CryWolf services.

There is no SOAP (Simple Object Access Protocol) URL configured for the CryWolf service. Ensure that there is a URL configured on the CryWolf configuration tab.

• Error Message: The CAP socket is not opened. Unable to query CryWolf services.

The CryWolf service network connection to the VisionCAD Access Portal (CAP) service is not open. The CAP service could be stopped. The CryWolf service will attempt to reopen the connection periodically.

• Error Message: Exception occurred: Socket Error # 11001 Host not found.

The server name is incorrect in the SOAP (Simple Object Access Protocol) URL for the CryWolf service, or the server is down.



Page 144

HigherGround Logging Recorder Interface

Note: The HigherGround Logging Recorder interface is an add-on that is not available unless your agency has purchased this feature. This section covers the interface only. This document does not describe the third-party recorder. Consult your third-party documentation for those instructions.

This interface provides a two-way interface to HigherGround’s Logging Recorder to detect a Recording ID (RID#) message and sends the VisionCAD call number to the Logging Recorder. This interface is an optional, configurable Windows service.

Installing the HigherGround Logging Recorder Interface The following steps describe how to install the HigherGround Logging Recorder interface services.






Page 145






Page 146






Page 147

Step 10. Choose your setup type (typically Complete) and click Next to continue the installation process. Choosing Complete installs both the HigherGround Logging Recorder Interface and its Monitoring application.

HigherGround Logging Recorder Interface – This feature installs two Windows services and the configuration program.

VisionCAD Access Portal – This is a required, supporting Windows service for the VisionCAD HigherGround Logging Recorder service.

VisionCAD Higher Ground Interface – This is the Windows service that interfaces with the third-party HigherGround Remote API.





Page 148






Page 149



• VisionCAD Higher Ground Interface


Note: The following additional services may also be installed: “VisionCAD Crywolf Interface,” “VisionCAD Deccan LiveMUM Interface,” “VisionCAD GenSpout Interface,” and “VisionCAD M/A COM CADLink Interface.” If started, these should be stopped, unless you are also using these interfaces.


Configuring the HigherGround Logging Recorder Interface The following figures and tables describe how to configure the VisionCAD Access Portal (CAP) and VisionCAD HigherGround Logging Recorder Interface services.




Page 150

Field Description





Note: A service is executed using a Windows system



Page 151

Field Description account. When using the Windows authentication option, you must ensure that the SQL Server’s authentication list is configured to allow the actual system account being used or set the service properties in the Service Control Manager to logon as a specified user. For whichever method chosen, ensure that the SQL Server account being used has the necessary SQL permissions to operate on the VisionCAD tables for assigning units, updating statuses, adding to the unit log, etc. Consider using the CADSupers or CADDisps group for this purpose.








Page 152

Field Description


Enter the IP address or name of the computer hosting the VisionCAD Access Portal (CAP) service. The HigherGround Logging Recorder service connects to this address to send CAP requests. This value defaults to localhost for the local computer. However, the services may be activated on different computers if circumstances dictate such.



Remote HGLogRecorder Hostname

Enter the IP address or name of the computer hosting the HigherGround Remote API Connector. The Higher Ground Interface service connects to this address to receive Recording Start event messages and to reply back with Call Number Information updates. This operation requires that HigherGround is configured to use TCPLISTEN in its Connection configuration.

Remote HGLogRecorder Port

Enter the port number of the Logging Recorder API server port. This value must match the value configured for Port Number in the TCPLISTEN configuration.

Debug Server Port Enter the port number of the debug server socket. The Higher



Page 153

Field Description Ground Interface service provides a TCP server port to which a debug monitoring utility can connect. Informational messages are sent over this connection which will be useful for monitoring the operation of the interface. The default value is 6005. It may be changed if 6005 conflicts with a server port used by another application on the same computer.


Whenever the configuration is changed, you must stop and restart the Higher Ground Interface service for it to recognize the new values. The Stop/Start buttons are provided for this purpose. You can also do this in the Windows Services window available through the Control Panel. If the service is running when the Save button is clicked, you are prompted with a confirmation dialog.


Using the HigherGround Logging Recorder Interface Once configured, there is no additional user interface for these services.

A field for the Recording ID (RID#) will be available in the Active Calls grid in the VisionCAD module. This is an optional field for the grid and will only show data if the agency is using the interface and the data is filled out. Once the association between the call and the recorder is made this field will display the RID#.

Message Workflow When the dispatcher picks up the phone, the ANI /ALI controller will send the ALI data to ACID and on to the VisionCAD workstation. The HigherGround controller will send an IDENT message to the connected interface.



Page 154

The Station/Channel (position), RID#, and a received timestamp will be written to a tracking table on the VisionCAD server. The table will also contain a unique index field, a Processed field and a Call Number field. When a new record is saved to the table, the Processed field will be set to 0 and the Call Number field will be set to <blank>.

When the ANI/ALI information goes to VisionCAD, the new call button will turn red. When the dispatcher saves the new call, a message is sent to Databus that a call has been added/saved.

The CAD Interface Engine (CIE) listens to Databus messages and when it receives a new call or saved call message, it will check the tracking table for a record containing the position information for that VisionCAD workstation as well as matching the TimeALI from CAD to the timestamp in the table where the processed field = 0. It will then update the Call Number field with the proper call number.

The CAD Interface Engine (CIE) will then send a SetInfo message to the Remote API Controller containing the updated Call Number.

Monitoring the HigherGround Logging Recorder Interface A monitoring utility allows for troubleshooting the operation of the HigherGround Logging Recorder interface services by displaying activity messages emitted by the debugging server sockets of those services. This utility may be placed on any network-accessible computer to observe the activity from a remote location.



Page 155




• For the HigherGround Logging Recorder section, fill in the IP address or name of the computer that is hosting the Higher Ground Interface service. As the two services are currently bundled together, this will usually be the same as the CAD Access Port IP address used above. The port number must match the port number configured in Debug Server Port on the HigherGround Logging Recorder configuration tab. Click the Connect button to connect to the service.


The VisionCAD Access Portal (CAP) service logs events to a local VSICIE.LOG data file using the standard logging mechanism also used by VisionCAD. The LOG file is stored in the same directory as the VSICIE.EXE file. The data will be logged until the file reaches its maximum configured size, default 512K. After reaching this size, the logging will wrap around to the beginning of the file. The HigherGround Logging Recorder service stores its log file in HGLogRecorder.LOG in the same directory as the HGLogRecorder.EXE file.



Page 156


Field Description


Source The source of the event. This may be CAP, HigherGround Logging Recorder, or VSICIEMon. The monitor itself shows its own errors as events sourced from VSICIEMon so that error dialogs won’t popup while it is left running unattended.

Context This is for troubleshooting error messages, and typically displays the involved code function name that is meaningful for programming engineers.

Text The descriptive text of the event.

Data If the event has associated binary data, the data is shown here in printable form. This is typically used to show the raw data received from the HigherGround Logging Recorder product.





Page 157











Page 158

Deccan LiveMUM Interface

Note: The Deccan LiveMUM interface is an add-on that is not available unless your agency has purchased this feature. This section covers the interface only. This document does not describe the third-party Deccan LiveMUM application. Consult your third-party documentation for those instructions.

This interface provides a two-way exchange between VisionCAD and the third-party Deccan LiveMUM system. This interface is an optional, configurable Windows service.

This interface consists of the following two data exchanges:

• VisionCAD provides Deccan with unit and event information in real time in XML format.

• Deccan provides VisionCAD with the "committed" Move-Up recommendations.

Installing the Deccan LiveMUM Interface The following steps describe how to install the Deccan LiveMUM Interface services.






Page 159






Page 160






Page 161

Step 10. Choose your setup type (typically Complete) and click Next to continue the installation process. Choosing Complete installs both the Deccan LiveMUM Interface and its Monitoring application.

Deccan LiveMUM Interface – This feature installs two Windows services and the configuration program.

VisionCAD Access Portal – This is a required, supporting Windows service for the VisionCAD Deccan LiveMUM Interface service.

VisionCAD Deccan LiveMUM Interface – This is the Windows service that interfaces with the third-party Deccan LiveMUM application.





Page 162






Page 163



• VisionCAD Deccan LiveMUM Interface


Note: The following additional services may also be installed: “VisionCAD Crywolf Interface,” “VisionCAD GenSpout Interface,” “VisionCAD Higher Ground Interface,” and “VisionCAD M/A COM CADLink Interface.” If started, these should be stopped, unless you are also using these interfaces.


Configuring the Deccan LiveMUM Interface The following figures and tables describe how to configure the VisionCAD Access Portal (CAP) and VisionCAD Deccan LiveMUM Interface services.




Page 164

Field Description





Note: A service is executed using a Windows system account. When using the Windows authentication option, you must ensure that the SQL Server’s authentication list is configured to allow the actual system account being used or set the service properties in the Service Control Manager to logon as a specified user. For whichever method chosen, ensure that the SQL Server account being used has the necessary SQL permissions to operate on the VisionCAD tables for assigning units, updating statuses, adding to the unit log, etc. Consider using the CADSupers or CADDisps group for this purpose.



Use DataBus? Check if using DataBus.



Page 165




Field Description


Enter the IP address or name of the computer hosting the VisionCAD Access Portal (CAP) service. The VisionCAD Deccan LiveMUM Interface service connects to this address to send CAP requests. This value defaults to localhost for the local computer. However, the services may be activated on different computers if circumstances dictate such.



Page 166

Field Description



Remote Deccan Hostname

Enter the IP address or name of the computer hosting the Deccan LiveMUM application.

Remote Deccan Port Enter the port number of the computer hosting the Deccan LiveMUM application.

Debug Server Port Enter the port number of the debug server socket. The VisionCAD Deccan LiveMUM Interface service provides a TCP server port to which a debug monitoring utility can connect. Informational messages are sent over this connection which will be useful for monitoring the operation of the interface. The default value is 6010. It may be changed if 6010 conflicts with a server port used by another application on the same computer.


Whenever the configuration is changed, you must stop and restart the VisionCAD Deccan LiveMUM Interface service for it to recognize the new values. The Stop/Start buttons are provided for this purpose. You can also do this in the Windows Services window available through the Control Panel. If the service is running when the Save button is clicked, you are prompted with a confirmation dialog.


Using the Deccan LiveMUM Interface Once configured, there is no additional user interface for these services.



Page 167

Deccan LiveMUM Exchange Details Sending: VisionCAD shall send Unit messages to Deccan LiveMUM anytime a unit's status changes, station changes, or event type changes. (Upon the initial connection all of the unit statuses shall be sent.) VisionCAD shall also send Event messages for each event that occurs to Deccan LiveMUM. These messages shall be sent from the VisionCAD client to the CAD Integration Engine (CIE) with limited data. However, the CIE shall inflate the message (Unit, as well as Event), and publish it. A Deccan LiveMUM Interface shall be listening for Unit and Event messages. This interface shall arrange the data into the proper XML format and send it to the LiveMUM server with STX and ETX framing characters. This send shall be over TCP with a socket connection to the designated port.

Receiving: Deccan shall send Relocate messages to VisionCAD when move-up recommendations from Deccan have been "committed". The Deccan LiveMUM Interface shall receive these messages on the same TCP socket connection as it is sending the Unit and Event messages. Once received, these messages shall be arranged into the proper XML format and sent to the CIE. The CIE shall update the Unit record in VisionCAD to reflect the received Station ID. The CIE shall also update the Patrol field in tandem with the same information.

Monitoring the Deccan LiveMUM Interface A monitoring utility allows for troubleshooting the operation of the VisionCAD Deccan LiveMUM Interface services by displaying activity messages emitted by the debugging server sockets of those services. This utility may be placed on any network-accessible computer to observe the activity from a remote location.




Page 168



• For the Deccan section, fill in the IP address or name of the computer that is hosting the VisionCAD Deccan LiveMUM Interface service. As the two services are currently bundled together, this will usually be the same as the CAD Access Port IP address used above. The port number must match the port number configured in Debug Server Port on the Deccan LiveMUM configuration tab. Click the Connect button to connect to the service.


The VisionCAD Access Portal (CAP) service logs events to a local VSICIE.LOG data file using the standard logging mechanism also used by VisionCAD. The LOG file is stored in the same directory as the VSICIE.EXE file. The data will be logged until the file reaches its maximum configured size, default 512K. After reaching this size, the logging will wrap around to the beginning of the file. The VisionCAD Deccan LiveMUM Interface service stores its log file in VSIDeccanLiveMUM.LOG in the same directory as the VSIDeccanLiveMUM.EXE file.


Field Description


Source The source of the event. This may be CAP, Deccan, or VSICIEMon. The monitor itself shows its own errors as events sourced from VSICIEMon so that error dialogs won’t popup while it is left running unattended.

Context This is for troubleshooting error messages, and typically



Page 169

Field Description displays the involved code function name that is meaningful for programming engineers.

Text The descriptive text of the event.

Data If the event has associated binary data, the data is shown here in printable form. This is typically used to show the raw data received from the Deccan LiveMUM product.











Page 170



Paging Interface

VisionCAD provides an interface to paging applications (such as PageGate), where CAD call data can be sent to officers’ mobile alphanumeric pagers.

The paging interface is automatically installed on your workstation during the VisionCAD installation, and a file named PAGING.INI is installed in the Windows directory.

You must also configure the VisionCAD to paging interface from within Dispatch in order to use the paging feature. The setup of the VisionCAD to paging interface determines what call information is included in the page. This must be done on each and every CAD workstation that will be using the paging function.

You must purchase the actual paging software (such as PageGate) separately. Refer to your Paging application documentation for detailed instructions on installing, configuring, and using your paging software.

Paging numbers are set up based on officer ID instead of unit ID, so that when a page is sent to a unit, it is sent to the appropriate officers on that shift in that unit. Agencies must set up (PageGate) paging numbers by officer ID in the paging application according to the documentation for that application.



Page 171

Configuring the Paging Interface from VisionCAD To set up Paging:

Step 1. In VisionCAD Dispatch, select Configure Paging from the Edit menu.

Step 2. The Paging Setup window displays.

Step 3. At the top of the window, click In Use to activate the paging function.

Step 4. If you would like for calls to be sent to units’ pagers automatically, then you should also check Auto Page. The call data will be sent to the unit’s pager as soon as the unit is dispatched to a call.

Step 5. When a call is sent using the Page button in the Units Assigned window in VisionCAD, an ASCII file is created and stored on the Paging server. In the Path field type the complete path to the directory on the paging server where these files are to be stored; for example, C:\ascii\.

Step 6. The Page Fields are those particulars of a call that may be included in the page. You may select any number of these fields by checking the box to the left of the field name. Once you have selected a field here, that call



Page 172

information will be included in all pages sent after the change, in the following order. The available fields are:

Call Number

Location

Apt / Suite

Flr / Bldg

City

Lower Cross Street

Upper Cross Street

Grid

Location Comment

Complaint

Complaint Description

Caller Name

Phone Number

Unit(s) Assigned

Internal ESN

Medical

Hazard

Narrative

Step 7. When you have completed this set up to your satisfaction, click Done. Click Cancel to exit the Paging Setup window and discard any changes you have made.

Step 8. If you have made any changes to the paging interface configuration, you must reset VisionCAD for those changes to take effect.

Note: CAD will write a page file for each officer assigned to the unit who has a value stored in the Pager field of the Officer record. This will send a page to every officer in a unit without sending a page to officers (or ridealongs) that do not have a pager. The file is named with the call number and the officers Pager ID. For example, a page sent to MARY BETH LACEY for call 060616-0001 is named MLACEY060616-0001.wba.



Page 173

Note: Pages are sent by officer ID. Each unit assigned to a call should have at least one officer ID associated with the unit. Each officer ID should be set up as a user in your paging application. See the documentation that came with your paging application for instructions on setting up users.

Configuring the Paging Interface from PageGate Note: This section is provided to assist in setting up the PageGate software to use VisionCAD’s paging interface. Because PageGate is third party software, owned by NotePage, Inc., the following is meant to be only an example. For more detailed instructions on installing, configuring, and using your paging software, refer to your specific Paging application’s documentation.

To set up PageGate for VisionCAD’s paging interface:

Step 1. If the PageGate software has not yet been installed, access the system that will host the database and main paging program for PageGate.

Step 2. Browse to the NotePage, Inc. website: http://www.notepage.net.

Step 3. Click on the Download button under the PageGate section.

Step 4. Save the pgsetup.exe file to your desktop.

Step 5. From your desktop, double-click the pgsetup.exe file.

Step 6. From the installation options window, select Install PageGate Server.

Step 7. Review and click next on each installation dialog that displays.

Recommendation: From the Choose Destination Location install prompt, browse and change the folder to C:\PageGate\.

Step 8. Once the installation process is complete, access your Start menu and select PageGate, then PageGate Admin.

http://www.notepage.net/



Page 174

Step 9. The first time this is accessed the PageGate Setup window displays.

Accept the default directory locations.

Verify Scheduler, GetAscii, and Connector1 are checked.

Check/uncheck the remaining options per your PageGate instructions.

Press the Apply button.

Step 10. For each directory that does not exist (database, log, and archive) confirmation messages display. Press Yes to create each directory.

Step 11. Finally, a confirmation message displays informing you that the database has been created and PageGate must be restarted. Press OK.

Step 12. From your Start menu, select PageGate, then PageGate Admin.



Page 175

Step 13. From your PageGate Admin window, expand the PageGate tree list.

Step 14. Navigate to Program, then Settings.

For Run PageGate as, select Windows Service.

Verify the remaining defaults as shown below.


Step 15. You will be prompted to enter a username and password. Leave these blank and press Apply.



Page 176

Step 16. Navigate to Interfaces, GetAscii, then Settings.

Enter the location of the shared ASCII folder. Once you tab out of this field, a prompt displays verifying that you wish to create this directory. Press Yes.

Place a check in the Enabled box.

Accept default of 5 for Polling Interval.


Step 17. From the confirmation window that displays, press Yes.



Page 177

Step 18. Navigate to Interfaces, GetAscii, Settings, Advanced Polling, then Files.

Step 19. From the Advanced Polling Files window that displays, click the Add button.

Step 20. From the Add Polling Entry window that displays, enter the following:

Recipient: *

From:

File(s): *.wba

Path: c:\ASCII

File Type: Custom


Step 21. Once returned to the Advanced Polling Files window, press the Apply button.



Page 178

Step 22. Navigate to Interfaces, GetAscii, Settings, Advanced Polling, then Symbols.

Single Character Wildcard: ?

Multiple Character Wildcard: |

End of Record Symbol: ~

Ascii Value Delimiter: \




Page 179

Step 23. Navigate to Interfaces, GetAscii, Settings, Advanced Polling, then Record.

Start Pattern: |

Start Offset: 0

End Pattern: ~

End Offset: 0




Page 180

Step 24. Navigate to Interfaces, GetAscii, Settings, Advanced Polling, then Recipient.

Select Dynamic Recipient.

Start Pattern: SubscriberName=

Start Offset: 15

End Pattern: [Message]

End Offset: -10




Page 181

Step 25. Navigate to Interfaces, GetAscii, Settings, Advanced Polling, then Sender.

Select Static Sender.

Sender: PageGate




Page 182

Step 26. Navigate to Interfaces, GetAscii, Settings, Advanced Polling, then Message.

Select Dynamic Message.

Start Pattern: Line1=

Start Offset: 6

End Pattern: ~

End Offset: 0

Check the Use Lookup Table and for the data in, use |Line1=|, |Line2=|, |Line3=|, etc. For the data out, use nothing. This way “Line1=” and so forth will not actually show up in the body of the message.




Page 183

Step 27. Access the PageGate Client Setup window. (This displays the first time the PageGate Client is accessed.)

Enter the shared location of the PageGate Server Database file: pagegate.mdb.




Page 184

Sending Calls to Units’ Pagers In VisionCAD Dispatch, click the Page button in the Units Assigned window to send call data to an officer’s alphanumeric pager.

When a call is sent using the Page button in the Units Assigned window in VisionCAD, an ASCII file is created and stored on the Paging server. This ASCII file is named with the call number and the unit assigned (on-shift officers) and contains the data for the call dispatched.

The Paging application polls the Paging directory for the ASCII files, and if it finds any, it sends the data in the files to the mobile units’ pagers. The frequency of this poll would be determined by your Paging application/vendor.

Each field sent is separated by an asterisk in the pager display. You decide the fields that are included in a page when you configure VisionCAD for the paging interface.

The EMD, EPD, EFD Interface

CAD provides the interface to an Emergency Management, Emergency Police, or Emergency Fire databases, such as ProQA or APCO MEDS.

• Depending upon your interface, refer to “Chapter 6. ProQA Interface” in this book for detailed information.

• Depending upon your interface, refer to “Chapter 7. APCO MEDS Interface” in this book for detailed information.



Page 185

Printrak CAD Interface

This interface transfers data from a Printrak CAD system to VisionCAD for use in reporting and uploading information to an RMS or Fire system. The data is uploaded from the Printrak system into text files, which are then loaded to the interface. The interface translates Printrak fields to VisionCAD fields and loads the data into the appropriate tables.

This document covers the installation and setup of the interface as well as its operation and some instructions for accessing and using the data in VisionCAD. The VisionCAD instructions are generalized to cover versions 2.5 and higher. Consult the documentation for the version installed at your agency for more detailed instructions, or simply access the online help available in each module of VisionCAD.

This document does not cover the process to create the upload text files from Printrak. Consult the documentation that came with that product for those instructions.

Record Types The upload text files contain two different kinds of records. The record types are Audits and Events. The following sections explain the kinds of information included in each record type.

Event Records An Event Record contains all data related to and included in the initial entry of a call. Information such as the event number, call location, call complaint type, and initial unit dispatch time would be included in the Event Record for the call.

Audit Records All modifications or additions made to call information after the initial entry are contained in an Audit Record. Actions such as the addition of call persons, or a change in call location are included in this record type. Non-call related unit activity also transmits as an Audit Record.

Customer Requirements This section details settings necessary to upload files, run reports on the uploaded data, and send the data to an RMS or Fire system. You may also view the call data in the VisionCAD Dispatch module and perform a few very basic functions with the data.

If you want more flexibility and control over the data in VisionCAD, you must have the appropriate licensing for full use, and complete the full set up of VisionCAD databases.



Page 186

Consult your Project Manager or Sales Representative and the documentation for your version of VisionCAD.

Your agency must meet the following requirements to use the interface:

• Must be on VisionCAD version 2.5 or higher

• Must install CAD Server

• Must install CAD Client on at least one workstation

• The workstation running CAD Client and the workstation running the Interface must both have access to the CAD Server via ODBC connection.

• Windows Security is not required.

• Must create a jurisdiction for use exclusively with this interface. If VisionCAD is used to handle calls in the normal way, the agency must create another jurisdiction to handle Printrak information.

Note: The VisionCAD Server Installation and the creation of a new jurisdiction must be performed by qualified TriTech personnel using the appropriate installation guide. Agency personnel may install the VisionCAD Client, but this is not recommended.

File Locations Before loading the executable, you should create a directory for it. The interface should be the only thing in the directory you create. The recommended directory is:

C:\Program Files\VisionAIR\ VisionCAD\PTrak\VSI_Ptrak2CAD.exe

The C:\Program Files\VisionAIR\VisionCAD directory is created during the VisionCAD Client installation. If the machine onto which you load the interface is not the same machine running VisionCAD, you will not see this directory. You may create any directory you like to contain the interface.

If you use a subdirectory such as the PTrak above, you can put another directory beneath that for the data files from Printrak.

ex: C:\Program Files\VisionAIR\VisionCAD\PTrak\Data

Note: DO NOT put the upload files directly in the C:\Program Files\VisionAIR\VisionCAD directory!! You must put them in a subdirectory.



Page 187

Interface Installation Load executable onto a machine with access to VisionCAD databases through ODBCs. The machine DOES NOT have to be running VisionCAD client. Simply save the executable in the directory you created for it.

Configuration You must configure the interface and VisionCAD in order to use the interface effectively and access the data in VisionCAD.

Interface Configuration Complete the following steps to configure the interface.

Step 1. Open the file VSI_Ptrak2CAD.exe. The first launch will prompt for configuration.

Step 2. Click OK.

Step 3. The Configuration window will display.

Step 4. Enter the Jurisdiction you created EXACTLY as it is entered in CAD.



Page 188

Step 5. Enter your User Name and Password as your rights are granted to the appropriate server. Even if you are using Windows Security, you must enter a User Name and Password. TriTech recommends simply entering your Windows Login information in these fields.

Step 6. Enter the Extension for the text files from Printrak. Do NOT enter the dot (.) only the extension itself, in this case “urt”.

Step 7. Select which version of VisionCAD is installed at your agency. Select 2 digit year if your version of Printrak uses a two digit year and 4 digit for a four digit year.

Step 8. Click Save to activate these configuration settings or click Close to exit without setting the configuration.

Step 9. After you have set your configuration, you will be prompted to restart the interface.

Step 10. Click OK, then open the Interface again. This time you will not be asked to set configuration. You will instead be taken directly to the main interface window.

VisionCAD Configuration You must set the following configuration option in CAD.

Category / Tab Option Setting

Profile Jurisdiction Select the Jurisdiction created specifically for Printrak data.

This configuration must be set through the Local Configuration module on the workstation running VisionCAD Client. Consult the VisionCAD System Administrator User’s Guide for instructions on setting configuration options.

You must also configure VisionCAD for interface with an RMS or Fire system if you wish to upload files to that system. The following are the relevant settings for interface with RMS or Fire.



Page 189

Option Description

FIRE 3x Interface Select Yes if interfacing with VisionFIRE 3.x, otherwise select No.

RMS Interface Set this option to Yes if CAD is interfacing to RMS, otherwise set this option to No. When this option is set to Yes, and the RMS server is valid, the Create OCA window automatically uses the RMS OCA button instead of Internal Department OCA.

Before doing an RMS Update, you must set this option to NO and do a File/Reset in CAD. This is necessary to avoid disturbing RMS during the Update process. After the Update, set the option back to Yes.

You must also set up the relevant ODBCs for Inform RMS and/or VisionFIRE 3.x. Refer to the chapter in this book “Chapter 4. Using RMS and Fire with CAD” for information on creating these data sources.



Page 190

VisionCAD Tear and Go Printing

VisionCAD Tear and Go Printing allows you to send call data to a printer at a remote location. You must install the VisionCAD Tear and Go application on a designated workstation on the network. The CAD workstations send the print jobs through a network computer to the printers on a TCP/IP network.

The following information is sent to the printer:

Call Number Jurisdiction Caller Name Location, Apartment, Floor City Cross Street Location Comment Directions IRA, ESN, Tract Dispatch Zone Units Assigned Complaint, Fire Grade Complaint Instructions Complaint Type Complaint Type Description Narrative Medical Hazard Fire Plan Department, OCA Number, RMS Jurisdiction Department, Department Number, Unit(s)

This information is sent to the appropriate Tear and Go Printer when a unit is assigned to a call with a status of Dispatched. Information will not be sent for any other status. The send is triggered by the Station Assignment in each unit record. Call information will be sent only once to each Station involved in a call.

To use the VisionCAD Tear and Go application, you must set up a workstation on the TCP/IP network with the CAD workstations. Here you configure which print jobs go to the printers at the stations.

To configure and set up the interface, follow these steps.

Step 1. Install the VisionCAD Tear and Go interface on the designated workstation with network connection to the Tear and Go Printer. Set up all printers on the network, also.



Page 191

Step 2. On the printer workstation, run the VisionCAD Tear and Go configuration utility.

Step 3. The VisionCAD Tear and Go window displays.

Step 4. To add a station printer, click on the Add Record button.

Step 5. Select the station from the Station drop-down list. The jurisdiction should fill in automatically.

Step 6. Select a printer on the network from the Printer drop-down list.

Step 7. Select whether or not the printer is a dot matrix printer.

Step 8. Select whether to print Tear and Go per unit or per station.

Step 9. Click on the Save (checkmark) button to save the record.

Step 10. Repeat this process for each station printer you want to send CAD call data.

Step 11. When finished, select Exit from the File menu.

The application must be running on the CAD workstation and the printer workstation for the application to operate. Remember to set the two CAD configuration options for VisionCAD Tear and Go printing and turn all printers on at the stations. If all CAD workstations will use the Tear and Go feature, set the configuration options globally.

Category Option Setting

Print/Fax VisionCAD Tear Yes



Page 192

Category Option Setting and Go

Print/Fax VisionCAD Tear and Go Machine

Enter the IP address of the machine running VisionCAD Tear and Go. The port used on this machine will be 6001.

GTE Fire Printer Interface

The GTE Fire Printer interface allows you to send call data and the Unit Status of Dispatched in report format to a printer located at a fire station, a pager, or a toner. The call data is sent in the form of a “page” such as is sent to a pager.

Dispatched is the only status that a unit is sent a page to a GTE Fire Printer. The call data that is sent in the page includes:

• Location

• Complaint Type

• Cross Streets

• Units Responding

• Narrative

• Phone Number

• Caller Name

Remember to set the CAD configuration options for GTE Fire Printing.


Interfaces GTE Fire Printing Yes

Interfaces GTE Fire Printing Machine Name

Enter the name of the machine on which GTE Fire Printing is running.

To use the GTE Fire Printer interface, you must set up CAD units to receive pages using the GTE Fire Printer Configuration and Setup utility.



Page 193

To configure and set up the interface, follow these steps.

Step 1. Open the GTE Fire program at the CAD workstation where it was installed.

Step 2. The PowerTCP application starts up to enable communications and runs minimized on the CAD workstation:

Step 3. Also, the GTE Fire Printer Network window displays.

From this window on the CAD workstation, you can monitor what messages are being sent to the station(s).

Step 4. For each unit, set up a station for the unit in CAD General Edit.

Step 5. To set up the INI file on the GTE Fire Printer Network window, click on the Cfg button.

Step 6. The INI window displays.



Page 194

Step 7. Enter the computer's name that has GTE’s application (GTE Fire) on it.

Step 8. Enter the same GTE Fire computer’s port that it is listening on.

Step 9. Enter the CAD jurisdiction.

Step 10. Enter the default pager width of 32 characters.

Step 11. Click OK. The INI window closes.

Step 12. On the GTE Fire Printer Network window, click on Setup to set up the units that will warrant sending the call data to the station.

Step 13. The Setup window displays for you to add, delete, or change unit details.

Step 14. To add a unit, click on the button. A blank line displays for the new unit.

Step 15. Select a unit from the pull-down Unit list.



Page 195

Step 16. Select a tone or page from the pull-down Tone or Page list. T= Tone and P=Page or Printer.

Step 17. Enter a number in the Number field: 1=printer; any other alpha or numeric is used for a pager.

Step 18. Click on the button to save the new unit record.

Step 19. The unit displays in the list.

Step 20. To delete a unit, select the unit by clicking its line and select the button.

Step 21. When you are finished, click on the close box in the upper right corner of the window.



Page 196

Fire Toning - Zetron Interface

Using the Zetron interface in CAD, you can send unit statuses to a station’s Zetron unit Model 25 or Model 26. You must set up the Zetron interface so that it recognizes tones and their equivalent unit statuses. Then, whenever a call is dispatched from CAD, the Zetron unit at the station of the dispatched unit(s) automatically receives an alert tone or tones.

The Model 25 sends tones from CAD to the Zetron unit at the station (one-way). For the Model 26, any changes made to unit status by either a CAD command or a Zetron unit causes both CAD and the Zetron system to reflect the updated unit status (two-way).

The dispatched station or unit alert can be performed in CAD either from the main windows or from the Command Line. The Zetron application must be started and running in the background at any CAD workstations that will be dispatching unit statuses to a Zetron unit. In CAD General Edit, you should have stations and units defined. Then, before running Zetron on a CAD workstation, you must set up units, statuses, and their associated tones on the CAD workstation using Fire Toning setup. Each section below – “Zetron Model 25 - Setup” and “Zetron Model 26 - Setup” explain this setup procedure.

Remember to also set the CAD configuration options for Fire Toning.


Interfaces Fire Toning In Use Yes (This option should be set locally unless all workstations at your installation will use Fire Toning.)

Interfaces Fire Toning Machine IP Address

Enter the IP address of the CAD workstation on which Fire Toning is running. If more than one station at your agency will use Fire Toning, you should set this option locally. If only one station will use Fire Toning, you can set this globally. If this option is set locally, you should not enter any value here unless you have selected Yes for the option Fire Toning in Use.

Interfaces Fire Toning Model “Zetron25” or “Zetron26”

Zetron Model 25 CAD Dispatch can send tones to a Zetron Model 25 for a single unit or for multiple units. With Model 25, the communication is one-way between CAD and the Zetron unit. So,



Page 197

whenever a unit’s status changes, notification is sent from CAD (where it is displayed on the CAD workstation) to the Zetron unit.

With the Model 25, if multiple units are at the same station, only one tone will sound per station per call. In CAD General Edit in the Units table, units are assigned to stations. The Fire Toning interface looks at the multiple units on a call that are assigned to the same station, and if one tone has already been sent to that station for that call, no more tones will be sent. This way, the Fire Toning unit is not constantly sending out tones for units assigned to the same call.

This section describes how to set up the Zetron Model 25 interface. It then shows how to use the Zetron window that runs the interface.

Set Up To set up units for toning to a Zetron Model 25, you must run the Zetron Model 25 Interface Utility. After the units are set up, you must keep the Zetron Interface window open, but minimized, on every CAD workstation that will be sending status tones to Zetron.

Shown below is the main Zetron25 Interface Utility window:

Setting up the Port You must first set up the Comm port for the machine to which the Zetron Model 25 is physically attached. To do this, select File, Ports from the menu of the main Zetron Model 25 Interface window. The following window displays.



Page 198

The following table explains the fields in this window.

Field Description

Port Use this field to set up the Comm port for the machine to which the Zetron Model 25 is physically attached. Enter a Comm port number of either “1” or “2”.

Baud The default setting is 4800. Consult Zetron 25 documentation to find the appropriate setting for your installation.

Data Bits The default setting is 8. Consult Zetron 25 documentation to find the appropriate setting for your installation.

Parity The default setting is N (None). Consult Zetron 25 documentation to find the appropriate setting for your installation.

Stop Bits The default setting is 1. Consult Zetron 25 documentation to find the appropriate setting for your installation.

Click OK to enact the changes you have made, or click Cancel to return to the Zetron 25 Interface window and discard any changes.

Setting up Units All CAD units can receive Zetron tones, however you need to specify which tones the units will receive by entering tone codes. A tone code is the actual sound the Zetron unit puts out.

Only one status can be sent to a Zetron Model 25 (for instance "Dispatched"), but the station can make the sound of the tone whatever it wants it to be by setting up the tone code(s) specifically for a particular unit.



Page 199

The types of tones must be set up on the Zetron unit. Refer to your Zetron documentation to set up the tones on that end.

To set up the Zetron tones that will be sent from CAD for a particular unit, from the Configure menu, select Units. The following window displays.

To add a unit and its tones, click on Add or +. Enter the Unit ID, the tone code, and the jurisdiction. If the unit should receive more than one tone code, separate them with a slash mark: 0112/0147.

Note: The values entered in the Tone Code field are derived from Zetron’s button numbers. For example, valid button numbers from the first panel of Zetron Model 25 would be numbers in the range from 0100—0159.



Page 200

Zetron 25 Interface Window As stated earlier, the CAD workstation using Zetron Model 25 toning must keep the Zetron Interface window running, minimized, on the Windows Desktop.

This window is a monitoring (debug) window, and simply displays some CAD call data (unit, jurisdiction, etc.) that was sent from CAD and the tone code that was sent to Zetron.

Zetron Model 26 CAD Dispatch can send tones to a Zetron Model 26. Model 26 functions very much like Zetron Model 25 with a few exceptions. In CAD General Edit in the Units table, units are assigned to stations. A tone is sent from CAD for every status of every unit at every station.



Page 201

Set Up This section describes how to set up the Zetron Model 26 interface. It then shows how to use the Zetron window that runs the interface.

Setting up the Port You must first set up the Comm port for the machine to which the Zetron Model 26 is physically attached. To do this, select Configure, Setup Port from the menu of the main Zetron Model 26 Interface window. The following window displays.

Enter a Comm port number of either "1" or "2" and click OK. (Enter only the number of the port here, such as “1” for COM1:, “2” for COM2: etc.) If you change the port, you must stop and restart the interface to enact the change.

Setting up Units All CAD units can receive Zetron tones, however you need to specify which tones the units will receive by entering tone codes. A tone code is the actual sound the Zetron unit puts out.

Only one status can be sent to a Zetron Model 26 (for instance "Dispatched"), but the station can make the sound of the tone whatever it wants it to be by setting up the tone code(s) specifically for a particular unit.

The types of tones must be set up on the Zetron unit. Refer to your Zetron documentation to set up the tones on that end.



Page 202

The Zetron interface uses the Units configuration list to convert a VisionCAD unit ID to an ID that is recognized by the Zetron Dispatcher. Each unit that can be statused with the Zetron Dispatcher must be entered in this list. The Zetron unit list configured here must be separately maintained along with VisionCAD as units are added and deleted from VisionCAD.

Step 1. To set up the Zetron tones that will be sent from CAD for a particular unit, select Setup Units from the Configure menu. The following window displays.

Step 2. To add a new unit, press the Add button to and enter the fields as described in the following table.

Field Description

UnitID from CAD Enter the unit identifier as it is defined in VisionCAD. Each CAD unit within a Jurisdiction must be unique.

Unit from Zetron Enter the unit identifier that is presented to the Zetron when the VisionCAD unit is statused. The value must be a single digit within the range 0 to 4 or 7. “0” indicates “All Units” to the Zetron Dispatcher; “7” indicates the station.

Station Enter the station address that is presented to the Zetron when the VisionCAD unit is dispatched. The value must be a



Page 203

Field Description numeric value between 1 and 1023.

Jurisdiction Enter the jurisdiction of the unit as it is defined in VisionCAD.

CAD Status, Zetron Status

These read-only fields display the status information last sent to the Zetron Dispatcher for that unit. Initially these fields are empty.

Step 3. Click Save to save the new record. Each CAD unit within a Jurisdiction must be unique. If you attempt to add or modify a record that creates a duplicate Jurisdiction and CAD Unit, the message “Unable to save record” is displayed.

Step 4. Repeat these steps or use the following functions to set up your remaining units.

Function Description

Modify An existing record can be modified by selecting it from the list, modifying the fields, and clicking Save. Each CAD unit within a Jurisdiction must be unique. If you attempt to add or modify a record that creates a duplicate Jurisdiction and CAD Unit, the message “Unable to save record” is displayed.

Copy The Copy button copies a unit record to a new jurisdiction. The Unit identifiers and station identifier of the selected record are copied to a new record with the jurisdiction “Jurisdiction?”. The correct code must be entered in the Jurisdiction field and the record saved.

Undo The Undo button restores the data that existed at the time of the last save, including undoing any deletions.

Delete The Delete button deletes the currently selected record if “Yes” is answered to the “Are you sure?” prompt window. Selecting the Undo button restores the record.

Finish Selecting the Finish button closes the window. The window does not close if the data has not been saved or undone. If changes are made to the data without selecting Save or Undo, a prompt window displays “Changes have not been saved. You must save or undo first”.



Page 204

Zetron 26 Interface Window As stated earlier, the CAD workstation using Zetron Model 26 toning must keep the Zetron Interface window running, minimized, on the Windows Desktop.

This window is a monitoring (debug) window, and simply displays some CAD call data (unit, jurisdiction, etc.) that was sent from CAD and the tone code that was sent to Zetron.

When the Zetron PA system is ON, the CAD Dispatch workstation will receive an acknowledgment by displaying a message to the telecommunicator. The telecommunicator must click OK to remove the message from the CAD Dispatch screen. The message will display the Station number in it.

A tone is sent to and from CAD for every status of every unit at every station. Following are the corresponding statuses between CAD and the Zetron Model 26 unit.

Number CAD Status Zetron Status

0 SIS – In Station (Available + In Station)

Available In for CAD 3.6 and later

0 REM, COM Available In for CAD 3.5 and prior



Page 205

Number CAD Status Zetron Status

1 AVA – In Service (Available + Out of Station)

Available Out

2 ENR – Enroute Responding

3 ONS – On Scene On Scene

4 LEF – Left Scene Transporting

5 ARR – Arrived Scene Facility

7 OUT – Out of Service Out of Service

14 DIS – Dispatched Alert On, PA Control On

Diagnostic Messages and Troubleshooting If the Debug option is selected from the Configure menu, diagnostic messages appear in the three memo frames of the Interface Window during operation. A memo field is cleared when its contents reach 256 lines of text.

If the Log To File checkbox is checked, in addition to the debug option, the messages are also exported to text files. When a message file reaches 2 megabytes in size, it is cleared and the messages continue to be exported. The Log To File option can be left on indefinitely without filling up the machine’s hard disk. It is recommended that diagnostic messages be saved to a file during normal operation so that they can be reviewed if any problems are reported.

This section details common error and warning messages, each followed by a description.

Inbound Diagnostic Messages • Error Message: Input packet overflow

The Zetron Dispatcher is sending a packet that is too large. CadZetron accepts a maximum packet size of 256 bytes; otherwise, the packet is ignored.

• Error Message: Received empty packet

The Zetron Dispatcher sent an empty packet, essentially an STX ETX2 character pair. No data is lost, but this message may indicate the Zetron Dispatcher is malfunctioning.



Page 206

• Error Message: Received short ALARM packet, length = x

CadZetron received an Alarm Status packet (Command 10) that is too short to process. This may indicate that the Zetron Dispatcher is malfunctioning since the command was correctly received, but is malformed.

• Error Message: Received short STATUS packet, length = x

CadZetron received a Station Full Status packet (Command 3) that is too short to process. This may indicate that the Zetron Dispatcher is malfunctioning since the command was correctly received, but is malformed.

• Error Message: Received short data packet, length = x

CadZetron received a packet that is too short to contain a command code. This may indicate that the Zetron Dispatcher is malfunctioning since the command was correctly received, but is malformed.

• Warning Message: HL NAK received for packet $xx$xx…

CadZetron received a High Level Acknowledgment from the Zetron Dispatcher that indicates the Zetron device did not process the command. Since the command was successfully sent and answered, CadZetron does not resend the command to prevent the possibility of constantly resending a command that the Zetron Dispatcher is unable to process.

• Warning Message: STX encountered during packet

The start of a new packet was received while currently receiving a previous packet. This warning may occur if the Zetron Dispatcher is reset while sending a packet, or if interference exists on the communication cable.

• Warning Message: Invalid checksum received

Incorrect data was received. CadZetron is requesting a resend of the same packet. This warning may occur if interference exists on the communication cable.

• Warning Message: Received duplicate packet

CadZetron received a packet with the same Low Level Sequence as the previous packet. The packet is acknowledged, but not processed. This warning may occur if interference exists on the communication cable.

• Warning Message: Received short HLACK packet, length = x

CadZetron received a High Level Acknowledgment packet (Command 9) that does not contain the ACK/NAK indicator. CadZetron processes this as a successful acknowledgment. This may indicate that the Zetron Dispatcher is malfunctioning since the command was correctly received, but is malformed.

Outbound Diagnostic Messages • Error Message: Output com buffer is full

The serial communications sending buffer is full. Characters are being discarded. In normal operation, the Zetron Dispatcher should respond with a NAK for which CadZetron resends the packet.



Page 207

• Error Message: Timeout elapsed, Retry limit is reached; packet is removed from queue Error Message: LLAck (Nak) Received, Retry limit is reached; packet is removed from queue

The Zetron Dispatcher did not respond to the command after retrying multiple times. CadZetron continues processing with the next command in the queue.

• Warning Message: Timeout elapsed, Retrying x

The Zetron Dispatcher did not respond to the command within the time limit. CadZetron is resending the command.

• Warning Message: LLAck (Nak) Received, Retrying x

The Zetron Dispatcher answered a command with a Low Level Acknowledgment that indicated a failed transmission. CadZetron is resending the command.

Miscellaneous Diagnostic Messages • Error Message: CAD status value is unrecognized

The string value in field 5 received from a CAD workstation was not one of the defined status values.

• Error Message: Invalid CAD status string was received

The first field of a CAD workstation message was not the string ‘ZS’.

• Error Message: SQL exception on update

An error occurred attempting to update the database. This error may occur when the status values AVAI or AVAO are received in a message. The text of the exception message is also displayed with this message.

• Error Message: Station address ''xxx'' is invalid in Fire_Toning.Station

The value for a station address in the Units configuration table is not a valid number.

• Error Message: Station address is invalid xxx

The station address in the Units configuration table is not a value between 1 and 1023.

• Error Message: Unit jur/unit was not found in Fire Toning configuration

The jurisdiction and unit code received in a CAD workstation message was not found in the Units configuration table.

• Error Message: Zetron Unit Value is unrecognized xxx

The Zetron unit ID from the Units configuration table is not a value between 0 and 4 or 7.



Page 208

• Error Message: A CAD communication error occurred. Event xxx code xxx on connection aaaa(xx.xx.xx.xx:xx), description

An error occurred on a TCP network connection between a CAD workstation and the Zetron interface. The error description and the IP address of the affected machine are displayed.

• Error Message: Application Exception name occurred at xxxx from source: description

An unexpected application error occurred. In prior revisions of CADZetron, these errors would display a pop-up box that must be acknowledged. The current revision of CADZetron captures these and records them in the miscellaneous diagnostic messages.


Chapter 6. ProQA Interface

Page 209

CHAPTER 6. PROQA

INTERFACE

The EMD, EPD, EFD Interface (ProQA)

CAD provides the interface to an Emergency Management, Emergency Police, or Emergency Fire databases, such as ProQA. Refer to your third-party documentation for more detailed instructions on using this application.

Note: If, the first time you start ProQA, it displays a login window asking for an Operator ID and password, enter DEMO as the login, with no password. Thereafter, this login window should not display. If you have problems with the application, please call ProQA Technical Support.

In the New Call and All Calls windows, click the EMD/EPD/EFD buttons to access the Emergency Management, Police, or Fire database for procedural instructions on emergency care. In the New Call and All Calls windows, you can open or reopen an EMD/EPD/EFD case, or view the case summary associated with the current call if a case exists. In the Edit Call, Full Call Edit, and Historical Calls windows, you can only view the case summary for the current call in the Narrative section for the call.

With a call highlighted in the All Calls window, you can select the EMD/EPD/EFD buttons and open or reopen a case or view the case summary if a case exists for the highlighted call. The following window displays when you click on the EMD/EPD/EFD buttons.



Page 210

If the highlighted call has already had a case opened for it, the Reopen Case and Case Summary buttons are active. If no case has been used for the call, the New Case button is active.

Select New Case, Reopen Case, or Case Summary and the ProQA window displays with questions to ask and instructions to give the caller.

The following figures show some examples of the ProQA application windows.



Page 211

Dispatchers and call takers with appropriate responsibilities will receive Alert messages concerning the call situation as reported in the EMD/EPD/EFD windows.

If an alert message displays on the other CAD dispatch stations, an additional unit may need to be dispatched. Click OK or press the Enter key to close the message. Alternately, press the Select Call button to automatically select the referenced call in the Browse Call window.



Page 212

You can also view the EMD/EPD/EFD case summary in the Narrative section of the Edit Call, Full Call Edit, View Historical, and Edit Historical windows, as shown below.

ProQA Interface Enhancements

The ProQA interface feature complies with Priority Dispatch’s Certified level of integration. Beginning with VisionCAD version 3.5 Update 3, the following new benefits are provided:

• Improved call narrative population with less duplicate information;

• Handling of the M-flag from ProQA that contains the initial Case Entry information;

• Handling of the K-flag that contains follow-up Key Question information;

• Handling of the Additional Information data and the * flag;

• Interoperation with the ProQA Police and Fire;

• Co-operation with the Discipline Launcher that allows one discipline to recommend opening a case in another discipline;

• Updating the call complaint from ProQA’s CAD Incident Code.



Page 213

Beginning with VisionCAD version 3.6 Update 2, the following new benefits are provided:

• TCP can be used in addition to DDE as a communication method;

• XML can be used in addition to the native legacy format as a file format;

• Hotkeys are defined for the EMD/EPD/EFD buttons on Browse Active Calls;

• The Vertical Dispatch alert message was removed to stop interruptions;

• The Horizontal Dispatch alert message was improved for better workflow;

• Unit Responsibilities are properly used when controlling whether a dispatching workstation displays the Horizontal Dispatch alert message.

Case Entry When the initial Case Entry step is finished in ProQA, VisionCAD posts only the following when it receives the M flag from ProQA. At this point in the process, the call taker has determined only the Four Commandments and a chief complaint to associate with the case.

** EMD Case Entry Finished **

• 13:Chief complaint number

• 30:Responder Script (Key questions)

Note: These numbers are identifiers for the fields Priority Dispatch uses in their Technical Specifications Manual.

Case Entry Screen

Key Questions When the Key questions are completed, VisionCAD posts only the following when it receives the K flag. This occurs only when additional questions are answered after the dispatch has occurs in ProQA. If all questions are answered before a dispatch is recommended, the Key Questions information is transferred to VisionCAD in the Dispatch recommendation; in which case the Key Questions event does not occur.



Page 214

** EMD Key Questions Finished **


Key Questions Screen

Additional Information When ProQA posts additional information in the * flag, such as for Persons or Vehicles, VisionCAD posts the following to the narrative. ProQA may also transmit additional information as part of a normal event, such as with the Dispatch flag. In either case, VisionCAD posts the information to the narrative; however, the * flag posts separately with its own timestamp.

ProQA Medical Infection Information 01



Page 215

ProQA Medical Infection Information 02

VisionCAD accepts CBRN, Hazmat, Person, Vehicle, Aircraft, and Vessel information from ProQA version 3.4, as well as the newer Business, Bomb, Bomb Threat Caller, and Suspicious Package information from ProQA Paramount (version 5).

Dispatch or Reconfigure When the case is dispatched or reconfigured, VisionCAD posts only the following when it receives the D or R flags.

** EMD Recommended Dispatch **

• 23:Response text

• 14:Dispatch Level and 22: Suffix

• 28:CAD Incident code


When the case is reconfigured, VisionCAD posts the following.

** EMD Reconfigure **

• 23:Response text

• 15:Reconfigure Level and 22: Suffix

• 28:CAD Incident code




Page 216

Dispatch Screen

The CAD Incident Code and the Dispatch Level are the same by default. In this example, they are both 04B01; however, ProQA allows an agency to configure custom CAD codes for each dispatch determinant. If this done, the ProQA determinant (e.g. “04B01”) will also be visible along with the custom CAD code (e.g. “ASSAULT”) and will aid ProQA on the complaint code configuration.

If the ECH Updates Complaint option is Yes, the call’s complaint code is updated to contain the CAD Incident code as supplied by ProQA. For more information, see the section CAD Call Complaint Updates.

VisionCAD on the dispatching workstations displays the alert window according to the CALLS – ExD Horizontal Dispatch configuration option to notify VisionCAD users of the change in response level.

• If the option is No, the ProQA interface will not broadcast alert notices of dispatch recommendations.

• If the option is Yes (the user is a call taker), an alert is broadcast to other VisionCAD workstations for the dispatchers’ attentions: a “Horizontal Dispatch.” From the alert window, click OK or press the Enter key to close the message. Alternately, press the Select Call button to automatically select the referenced call in the Browse Call window.



Page 217

EMD/EPD/EFD Dispatch Alert

For the Horizontal Dispatch alert message to appear on dispatching workstations, all of the following conditions must be met:

• ProQA must send a Dispatch or Reconfigure status message. (This is the trigger for the alert.)

• On the machine using ProQA, the CAD configuration option must be set to “Yes” for CALLS – ExD Horizontal Dispatch. (This causes it to send the alert.)

Note: If ProQA sends an Urgent status message, an alert is always triggered regardless of the value of the CALLS – ExD Horizontal Dispatch option. However, the remaining conditions determine whether other workstations receive this message.

• DataBus must be running on all machines. (This allows the alert to be transmitted and received.)

• On the dispatch machine, the CAD configuration option must be set to “No” for CALLS – Separation of Call Taker/Dispatcher. (This indicates that the workstation is a dispatching workstation.)

• The affected call must be in the dispatcher’s call responsibility however the call responsibility feature is being used – by zones, by categories, etc. (If the call is not available in the dispatcher’s Browse Active Calls, then the alert message will not display either.)

• The dispatcher’s unit responsibility must be set as follows:

The options for [All], [Zone], [Dept], [Zone + Dept], or [Patrol] will allow the dispatcher to see alert messages from any discipline of ProQA

For the options of [Category] or [Category + Dept], the dispatcher must be configured for unit responsibility categories as follows:

EMS or FIR to see alerts from ProQA Medical

POL or SHE to see alerts from ProQA Police

FIR or FRE to see alerts from ProQA Fire



Page 218

Urgent Message When the ProQA user sends an Urgent Message, VisionCAD posts only the following to the narrative.

• 32:Urgent Message

Urgent Message Screen

Note: For the conditions under which users receive the Urgent Message alert refer to the previous section.

Aborted Case When the case is aborted, CAD posts only the following when it receives the A flag.

** EMD Case Aborted **

• 24:Abort text


Aborted Case Screen

Completed or Pending Case When the case is closed in ProQA, CAD posts only the following when it receives the C flag.

** EMD Case Complete **


When the case is pended, CAD posts the following when it receives the P flag.

** EMD Case Pending **



Page 219


Pending Case Screen

ProQA Police and Fire The ProQA interface in VisionCAD also simultaneously supports the use of ProQA Police and Fire. Two new buttons, EPD and EFD, appear next to the EMD button on various call windows. The Configuration has an option that enables each of them.

• INTERFACES – EFD in Use

• INTERFACES – EPD in Use

In the figure below, the EFD interface is disabled and the EMD and EPD interfaces are enabled.

Add New Call Window

Each button transmits the call to the database, opens the corresponding ProQA discipline, and presents the user with ProQA’s Case Entry window.

The following fields are passed from VisionCAD to ProQA for the initial case entry.



Page 220

ProQA Field VisionCAD Field

Incident (Case) Number

VisionCAD Call Number – This is only sent to ProQA if using XML format. (COMMFILE Format = XML)

2: Operator Number CAD Login ID (Up to 10 characters)

4: Location of incident

Incident Location

5: Call back phone number

Telephone

6: Problem Description

Complaint

7: Number of patients Inj. (Injuries)

31: Caller Name Caller Name (Police and Fire only)

VisionCAD Fields to ProQA Case Entry

The following windows in VisionCAD contain the EPD and EMD buttons:

• Add New Call

• Full Call / Historical Edit

• Historical Calls View Only

• Browse Active Calls

On each window, these buttons appear alongside of the EMD button.

Historical Calls Window

On the Historical Calls – View Only window, the call handler buttons open the ProQA case summary for the call.

Full Call / Historical Edit Window



Page 221

On the Full Call / Historical Edit window, if a historical call is viewed, the call handler buttons open the ProQA case summary. If an active call is viewed, the call handler buttons present the ProQA Case Entry choice window.

ProQA Case Entry Choice Window

A button is disabled if it is not appropriate for the call.

Button Description

New Case Creates a new case in ProQA. This button is disabled if a case has already been created for the call.

Reopen Case Reopens an existing case in ProQA. This also reopens a pending case in ProQA. This button is disabled if a case has not been created for the call.

Case Summary Displays the case summary in ProQA. This button is disabled if the case has not been created for the call.

Cancel Closes the window without taking action.

ProQA Case Entry buttons

On the Browse Active Calls, window the call handler buttons present the ProQA Case Entry choice window.

Call Handler Commands The VisionCAD command line provides commands for accessing the ProQA call handler applications:

• EMDN call#

• EPDN call#

• EFDN call#

These commands create a new case in the indicated ProQA discipline: Medical, Police, and Fire. If a case has already been created for the call, an error message displays “An



Page 222

XXX case already exists for call number xxxx”, where XXX is the ProQA discipline: EMD, EPD, or EFD.

• EMDR call#

• EPDR call#

• EFDR call#

These commands reopen an existing case in the indicated ProQA discipline. If a case has not been created for the call, an error message displays “No XXX case exists for call number xxxx”.

• EMDS call#

• EPDS call#

• EFDS call#

These commands display the case summary in ProQA for the call. If a case has not been created for the call, an error message displays “No XXX case exists for call number xxxx”.

The normal commandline features continue to work. The partial call number feature works for the call# parameter. The “X” feature uses the selected call in the Browse Active Calls window.

The New case and Reopen case commands cannot be used against closed calls. If these commands are issued against a closed call, an error message displays “The XXX command cannot be run on closed call xxxxxx”.

CAD Call Complaint Updates VisionCAD provides an option that allows ProQA to update the complaint code of the call when it determines the CAD Incident Code/Dispatch Level. VisionCAD Global and Local Configurations contain the following option in the item list:

INTERFACES – ECH Updates Complaint – Do you want the Emergency Call Handler interfaces (EMD, EPD, EFD) to update the call complaint when a CAD incident code is determined?

If this option is set to Yes, then a Dispatch or Reconfigure by ProQA updates the call’s complaint to the CAD Incident Code provided by ProQA.

ProQA can be configured to contain CAD Complaint Codes according to the dispatch determinants. These are set in ProQA’s Response Configuration utility.



Page 223

ProQA Response Configuration

A CAD administrator can edit the CAD codes column (in the ProQA Response Configuration utility) to contain the desired CAD Complaint Code as defined in General Edit in the Complaint table. These values can be as detailed as necessary for an agency’s operation and reporting purposes. If detailed statistics on the kinds of calls are desired, there can be a CAD complaint for each condition code defined in ProQA. Or, if only basic reporting is required, the same CAD Complaint could be entered for every condition code within a Chief Complaint.

In the example figure above, there is a CAD code entered for each level of response: Alpha, Charlie, and Delta.

By default, if the ProQA CAD codes are not configured, the CAD code and the Condition codes are the same. An agency can choose to configure General Edit Complaints to contain the ProQA condition codes, 01A01, 01A02, etc or they can choose to configure ProQA to contain the CAD Complaint codes.

When VisionCAD updates the complaint of a call, it also updates the complaint-related data in the call as defined in the Complaints table. The following fields are updated when the complaint is changed.

• Categories

• Ten Code

• Priority – if Complaint record is blank, the Config priority is used (CALLS – Priority).

• Class – if Complaint record is blank, the Config class is used (CALLS – Call Class).

• Warn Units Overdue – if Complaint Timeout is blank, the Config default is used (UNITS – Default Overdue Time).

• Warn No Dispatch

• Warn By Complaint



Page 224

• Default Fire Grade

• Report Reqd

• Subject Reqd

If ProQA supplies a CAD code that does not exist in the Complaints table, the call’s complaint is updated anyway. This is consistent with the command line operation that populates a new miscellaneous call with an unknown complaint code that may have been mistyped. When the call is cleared with an invalid complaint, VisionCAD presents an error notification to the dispatcher. The dispatcher must correct the complaint before the call can be cleared.

Error - Invalid Complaint

The complaint history for the call is also maintained. As ProQA dispatches and reconfigures a particular call, the call’s existing complaint is entered into the complaint history as it is changed. The figure below, displayed from the Call – View Complaints menu, shows the history of reconfigures for a call.

Call Complaints Window

Multiple Cases on One Call If two or more ProQA cases are opened for one call, only the first case opened will update the complaint of the call. The second or third cases will not update the complaint



Page 225

whether it is started manually from a call window or it is opened on the same call in the Secondary Case window using the “Open New Case” button. For more information, please see the sections on Secondary Case window.

Note: If two cases are opened for one call and both are closed, a reopened case does not update the complaint of the call. After the cases are closed, each case can no longer detect if it is able to update the complaint; each case will “see” another case attached to the call. However, a single case will update the complaint after it is reopened.

Multiple Discipline Launcher VisionCAD supports ProQA’s multiple discipline launcher. If so configured, ProQA can recommend launching a ProQA application of another discipline, depending on how certain questions are answered.

In the Multi-Discipline Launcher Utility, a CAD administrator can provide discipline recommendations for the specific answers to the questions. For example, in the following figure, a Police response is recommended if the assailant in an assault case is still on the scene.

Multi-Discipline Launcher Utility

If a question is answered that triggers a second discipline’s response, ProQA recommends a secondary discipline to be opened. VisionCAD responds by displaying the Secondary Case window.



Page 226

Secondary Case Window

This window is not modal; it doesn’t take over the screen so the user can attend other business and come back to it later. If a safety issue requires sending a recommended police response first for a medical case, the call taker can initiate the police call/case before finishing the medical case.

The buttons perform the following behaviors:

Button Description

Clone call and open case

This button opens the Clone Call window to allow a new call to be created by cloning the existing one. After the call is cloned, VisionCAD launches the recommended ProQA discipline. This option allows an agency to manually split a call based on ProQA’s recommendation.

Open new case VisionCAD launches the recommended ProQA discipline using the existing call. The narrative postings submitted by both disciplines end up in the same narrative for the one call. This option allows an agency to use a single call record to coordinate all responses to the incident. The case that is started from this button will not update the complaint of the call, even if the ECH Updates Complaint option is turned on.

Open case with selected call

If the call was split based on the initial complaint type, this option allows a user to select a desired call and open the recommended ProQA discipline against that call. The grid shows all calls that are related to the first call; if no calls are related, the button is disabled. Typically, the list contains only SPLIT references, but if CLONE references or other manual



Page 227

Button Description references were made before the recommendation occurred, those calls will show up as well. This option allows an agency to work with Split Calls in CAD.

Cancel (ESC) Closes the window without taking any action.

Secondary Case buttons

The three buttons that open a new case will also cause the associated call to be selected in the call browse window. The Clone button will open the Clone Call window and wait for the cloned call to be created before continuing:

Secondary Case Window - Waiting

While in waiting mode, the window is not responsive. It can not be closed and the buttons can not be clicked; however, the window can be moved to any part of the screen.



Page 228

Clone Call Window

If the call is cloned, both windows will close and the recommended ProQA discipline is launched. If the Clone Call window is canceled, the user returns to the Secondary Case window for another chance to choose an action.

If a ProQA discipline that was recommended by another discipline recommends opening a new case for that discipline, VisionCAD does not provide the Secondary Case prompt. This prevents circular prompts, for example, when Medical recommends a Police response and the resulting Police case recommends a Medical response.

Split Call Operation VisionCAD’s ProQA interface allows for and cooperates with the Split Call feature. Whether an agency uses Split Calls or not, the VisionCAD user has full discretion on whether to split a call based on ProQA’s recommendation. The interface does not automatically split calls.

VisionCAD’s Split Call feature splits the call based on the categories in the complaint at the moment it is saved, so when ProQA is activated from the Add New Call window, the call is split and saved, and the ProQA discipline is launched. When this occurs, the ProQA interface selects the call with the best category according to the launched discipline.

For example, if a multi-category complaint is chosen in Add New Call, such as TERRORIST in the following figure, the call splits into multiples for the POL, FIR, EMS, RES, and FRE categories.



Page 229

Add New Call Window, Multi Category

If the EMD button is clicked to open ProQA Medical, the case is associated with the EMS call. Likewise, a ProQA Police case will be associated with the POL call and a ProQA Fire case will be associated with the FIR call. No matter how the call is split, the discipline being launched will associate with the best category according to the type of discipline.

Each discipline chooses the best category according to the ranking shown in this table.

Medical Police Fire

EMS POL FIR

FIR SHE FRE

FRE FIR RES

RES FRE EMS

POL RES POL

SHE EMS SHE

OTH OTH OTH

Category Rankings by Discipline



Page 230

As according to the table, if the Medical discipline is launched, CAD posts the ProQA narrative entries to the EMS call, if there is one. If not, it looks for a FIR call. If there’s no FIR call, it looks for an FRE call, and so on until it finds one. When using the Police discipline, CAD looks for POL first, SHE second, etc.

For example, if a call splits into EMS, POL, and FIR, the Medical interface will choose the EMS call, the Police interface will choose the POL call, and the Fire interface will choose the FIR call. On the other hand, if a call splits into EMS, FRE, and RES calls, then the Medical interface will choose the EMS call, the Police and Fire interfaces will choose the FRE call.

Split Call Categories

Medical Choice Police Choice Fire Choice

EMS, POL, FIR EMS POL FIR

EMS, FRE, RES EMS FRE FRE

FIR, SHE, RES FIR SHE FIR

Discipline Choices for Split Call Examples

This operation allows the ProQA interfaces to work flexibly with agencies that categorize in different ways, such as those that dispatch medical responses from their fire departments, or law enforcement responses from their sheriff departments, etc.

Using the example shown in Add New Call Window, Multi Category, the Medical discipline selects the EMS call in the Browse Active Call window.

Browse Active Calls



Page 231

If ProQA recommends a secondary discipline to be launched, the Secondary Case window shows the split calls.

Secondary Case, Split Calls

From this window, the call taker can select the desired call and open a new case.

Narrative Examples The following shows an example of a complete narrative as populated from ProQA Medical and Police.

Medical Narrative [8/30/2007 12:19:07 : pos1 : tc01] [Calls 070830-0009,070830-0010 are related.] [8/30/2007 12:17:43 : pos1 : tc01] ** EMD Case Complete ** Key Questions: Not alert (Assault). [8/30/2007 12:17:05 : pos1 : tc01] ** EMD Additional Info ** CBRN Info:Severe Respiratory Infection (Flu-Like) Symptoms * a persistent cough * sore throat * a runny nose * has or had a fever (clearly hot to touch) [8/30/2007 12:15:39 : pos1 : tc01] ** EMD Reconfigure ** Response Text: Delta



Page 232

Dispatch Level: 04D02 Suffix: A CAD Incident Code: 04D02 Key Questions: 6.He is not completely awake (alert). -Comments: ASSAILANT HAS AGGRESSIVE DOG- [8/30/2007 12:15:08 : pos1 : tc01] EMD Urgent Message: ASSAILANT HAS AGGRESSIVE DOG [8/30/2007 12:13:39 : pos1 : tc01] ** EMD Recommended Dispatch ** Response Text: Bravo Dispatch Level: 04B01 Suffix: A CAD Incident Code: 04B01 Key Questions: POSSIBLY DANGEROUS body area (Assault). 1.The patient was assaulted. 2.This happened now (less than 6 hours ago). 3.The assailant is inside the same structure. 4.The assailant is not armed. 5.There is some bleeding, not serious. 6.He is completely awake (alert). 7.He is breathing normally. 8.The injury is to a POSSIBLY DANGEROUS area. [8/30/2007 12:12:47 : pos1 : tc01] ** EMD Case Entry Finished ** Chief Complaint Number: 4 Key Questions: 25 year old, Male, Conscious, Breathing. Assault / Sexual Assault. Caller Statement: FIGHTING IN BOB'S TAVERN. [8/30/2007 12:12:00 : pos1 : tc01] Cross streets: SANTIAGO ST//VALENCIA AV NBH: 799F6 92706 33.77154,-117.861515

Police Narrative ProQA Medical recommended a Police dispatch in the above example and the call was cloned. The following shows an example of a complete ProQA Police narrative with additional information regarding the suspect/victim descriptions and the suspect’s vehicle.

[8/30/2007 12:22:38 : pos1 : tc01] ** EPD Case Complete ** [8/30/2007 12:22:19 : pos1 : tc01] ** EPD Key Questions Finished ** Key Questions: 6.The caller is not in immediate danger. 7.The caller was advised to report if s/he feels unsafe at any time. 8.No one else is in immediate danger. 9.The suspect/person responsible is on scene. 10.The suspect's description is: 11.The suspect arrived in a vehicle. 12.The vehicle description is: 13.The location of the vehicle is: TAVERN PARKING LOT 14.The victim's description is: 15.The location of the victim is: ON SCENE 16.Someone is injured or sick. 17.One person is injured or sick. --Comments: TAVERN PARKING LOT- --Comments: ON SCENE-



Page 233

[8/30/2007 12:22:01 : pos1 : tc01] ** EPD Additional Info ** Person Info:[Type]Victim[Race]WHITE[Gender]MALE[Clothes]GREEN SHIRT/SHORTS[Age]25 [8/30/2007 12:21:23 : pos1 : tc01] ** EPD Additional Info ** Vehicle Info:[Type]Suspect[Year]1996[Color]TAN[Make]JEEP/CHEROKEE[Body]4-DOOR [8/30/2007 12:20:37 : pos1 : tc01] ** EPD Additional Info ** Person Info:[Type]Suspect[Race]WHITE[Gender]MALE[Clothes]RED SHIRT/BLUE JEANS[Age]30 [8/30/2007 12:20:06 : pos1 : tc01] ** EPD Recommended Dispatch ** Response Text: Delta Dispatch Level: 106D04 CAD Incident Code: 106D04 Key Questions: 1.The caller is on scene and is the victim/suspect (1st party). 2.This incident is in progress. 3.The victim was ASSAULTED. 4.Weapons were not involved or mentioned. 5.One person is reportedly involved. [8/30/2007 12:19:40 : pos1 : tc01] ** EPD Case Entry Finished ** Chief Complaint Number: 106 Key Questions: Assault / Sexual Assault. Caller Statement: FIGHT AT BOB'S TAVERN. [8/30/2007 12:19:07 : pos1 : tc01] [Calls 070830-0009,070830-0010 are related.]

VisionCAD/ProQA Interface Settings

The following configuration options must be set in the Interfaces category in CAD Configuration to enable and optimize the interface between VisionCAD and ProQA.

Parameters Setting

EMD/EPD/EFD In Use Options

Set these options to Yes for each Emergency Call Handler interface that is in use.

• Set the EMD In Use option to Yes if you are using ProQA’s Emergency Medical Dispatch program.



Page 234

Parameters Setting

• Set the EPD In Use option to Yes if you are using ProQA’s Emergency Police Dispatch program.

• Set the EFD In Use option to Yes if you are using ProQA’s Emergency Fire Dispatch program.

EMD/EPD/EFD Data Format Options

For each ProQA program in use, enter its corresponding configuration option.

If the value is set to “XML,” CAD will send XML-formatted data for ProQA’s COMMFILE and expect to receive XML-formatted data from ProQA in response. XML can be used only in ProQA Paramount (version 5). If the value is set to anything but “XML” or “APCO,” CAD will use the native file format, which for ProQA is the legacy COMMFILE file format used by ProQA version 3.4.

EMD/EPD/EFD TCP Port Options

For each ProQA program in use, enter its corresponding configuration option.

If the Emergency Medical/Police/Fire Dispatch program uses TCP/IP as the communication method, enter the port number necessary to connect in this field. This number should match the port number setup in the configuration for the call handling program. For example, in the ProQA setup, where a COMMFILE name is set to “127.0.0.1 7500,” the port number used in this option must be 7500.

TCP functionality for ProQA is enabled by entering a non-zero value in this field. TCP can be used for either ProQA version 3.4 or Paramount (version 5).

A value of 0 (zero) will attempt to use an alternative communication method, such as DDE.

ECH Updates Complaint

Set this option to Yes if you want the Emergency Call Handler interfaces (EMD, EPD, EFD) to update the call complaint when a CAD incident code is determined?

ExD Horizontal Dispatch (Calls category in CAD Configuration)

This option should be set at a local workstation, based on whether the user initiates EMD, EPD or EFD and also dispatches responders from the same workstation (vertical) or if the user is solely a call taker (horizontal).



Page 235

The following additional configuration options may be set in the ProQA category in CAD Configuration for the interface between VisionCAD and ProQA.

Parameters Setting

Key Questions Bullets

Select Yes if you want to format the ProQA Key Questions Text in bulleted form.

Key Questions Filter Enter how the ProQA Key Questions should be filtered/sorted. You can filter the text so that only Pertinent (P) and safety answers are imported, Pertinent/Important (I) and safety answers are imported, or all (A) answers are imported. Enter P, I, or A.

Key Questions Short Text

Select Yes if you want to import the short form of the Key Questions answer text.

The following configuration options must be set in the ProQA Configuration Utility to enable the interface between VisionCAD and ProQA. This section only includes ProQA items that affect the VisionCAD/ProQA interface. All other configuration options should be set up as per your Priority Dispatch configuration recommendation. Refer to your third-party documentation for more detailed instructions on using this application.

Parameters Setting

Paths and Files Tab

COMMFILE Name For DDE mode, this field is not used.

For TCP mode, this field should contain the IP address of ProQA, which is typically 127.0.0.1 to indicate the local machine, followed by a space and then the port number. Example: 127.0.0.1 7500

COMMFILE Format Set this configuration option to “XML” or “Legacy”. These values must correspond to those set in the INTERFACES – EMD/EPD/EFD Data Format CAD configuration options described in the previous table.

Configuration Tab – User Interface Sub-Tab

Check all options on this tab unless otherwise indicated by your Priority Dispatch configuration recommendation.

Configuration Tab – Print on Send Sub-Tab

Enable the Print on Send options as suggested by your Priority Dispatch configuration recommendation.



Page 236

Parameters Setting

Configuration Tab – Print on Close Sub-Tab

Enable the Print on Close options as suggested by your Priority Dispatch configuration recommendation.

Configuration Tab – CAD (misc.) Sub-Tab

These are the most important configuration settings for the VisionCAD/ProQA interface.

Update Passed CE Fields

If unchecked, the call taker cannot update the case entry fields passed to ProQA from VisionCAD. Because CAD passes the complaint code for the Problem Description, it may be desirable to allow updates so the caller’s words can be recorded for the problem description. If the Display Problem Text option is checked on the Responder Script tab, these words will appear in the call narrative as part of the Responder Script text.

Write COMMFILE On Initialize Case

If checked, ProQA sends the ‘N’ flag with the newly initialized case number to CAD. This provides CAD with the earliest opportunity to record the case number in its Call_Emd_Number table. If unchecked, CAD records the case number when it receives any flag from ProQA. The complaint code update feature relies on this option being checked. When VisionCAD starts a new case, it checks to see if a ProQA case number has been created for the case. If a case has not been created, then the new case can update the complaint type of the CAD call. If this option is unchecked, VisionCAD can start two ProQA cases without receiving a case number for either one. This will incorrectly allow two cases to update the same CAD call. See also the section on Multiple Cases on One Call.

Write COMMFILE On KQ End

If checked, ProQA sends the ‘K’ flag if the call taker answers additional questions after the dispatch has been recommended. VisionCAD populates the narrative with the new answers under the headline ** Key Questions Finished **.

Send Responder Script to CAD

If checked, ProQA sends the case summary text to CAD in the responder script field. This shows up in the CAD narrative with the tag “Key Questions”.

Notify CAD On Shutdown

If checked, ProQA sends the ‘T’ flag when it shuts down to CAD. VisionCAD logs a warning in the VSICAD.LOG file that ProQA has stopped running.



Page 237

Parameters Setting

Configuration Tab – CAD Polling Sub-Tab

Communications File Mode

This must be set to DDE or TCP to operate with the CAD interface. Use the drop down menu to select “DDE” or “TCP.”

• For DDE, the INTERFACES – EMD/EPD/EFD TCP Port CAD configuration options should be zero.

• For TCP, the INTERFACES – EMD/EPD/EFD TCP Port CAD configuration options should be set to a non-zero value, which matches the port number setup in the configuration for the call handling program. (The Paths & Files tab, in the COMMFILE name field should contain the IP address of ProQA, which is typically 127.0.0.1 to indicate the local machine, followed by a space and then the port number. Example: 127.0.0.1 7500)

Urgent Message If the Urgent Message option is checked, ProQA will allow the call taker to send an Urgent Message to the CAD call from ProQA. This shows up in the call narrative with the tag “Urgent Message”.

Configuration Tab – Responder Script Sub-Tab

The checkboxes on the Responder Script tab indicate which pieces of information should appear in the Responder Script field whenever ProQA sends the information to VisionCAD. CAD displays the Responder Script with the tag name “Key questions” in the narrative. An agency may choose to uncheck any items they don’t need to appear in the CAD narrative.

Check all of the options on this tab and select the “Display All Key Questions” option unless the Priority Dispatch configuration recommendation suggests otherwise.

Display Updates (for this section only)

If Display Updates is unchecked, the entire case description is repeated in the narrative each time ProQA transmits any data. This quickly bloats the CAD narrative with excessive and repetitive text.

Abort Reasons Tab

Using the free-text window, type (in a column) any reasons users are allowed to abort, e.g. Caller Hung Up, Call dropped, etc.

Restricted Tab

Display Updates (for this section only)

This option enables ProQA Medical to send CBRN (Chemical, Biological, Radiological, Nuclear) and HAZMAT



Page 238

Parameters Setting information to VisionCAD in the “Additional Information” format. This appears in the narrative along with the other case data or it may appear with a separate ** Additional Information ** title if ProQA sends the information separately. The sub-options must be checked for CBRN or HAZMAT as desired.

Use Optional CAD Fields

This option enables the Multi-Discipline Launching and the Police additional info data for Persons and Vehicles.

Multi-Discipline Launching

If checked and the ProQA Multi Discipline Launcher utility has been configured with the desired disciplines for the corresponding questions, ProQA recommends a secondary case to be opened and VisionCAD displays the Secondary Case window.

Immediate Descriptor Information (Person and Vehicle)

If checked, ProQA Police sends Person and Vehicle data immediately after it is entered using the ‘*’ flag, which CAD posts to the narrative with a ** Additional Information ** title.

Restricted Tab – Fire Control, Medical Control, and Police Control

The following three fields are common for Fire, Medical, Police:

Allow Passing Of Problem Description

If unchecked, ProQA does not populate the problem description field with the complaint type when VisionCAD opens a case.

Pass CAD Case Entry Information On Display Of Key Questions

If checked, ProQA sends the ‘M’ flag to CAD when the case entry screen is finished. VisionCAD posts the information to the narrative under the title ** Case Entry Finished **.


Chapter 7. APCO MEDS Interface

Page 239

CHAPTER 7. APCO MEDS

INTERFACE

The EMD, EPD, EFD Interface (APCO MEDS)

VisionCAD provides the interface to an Emergency Management, Emergency Police, or Emergency Fire databases, such as the APCO Institute’s Multi-purpose Emergency Dispatch System (MEDS™). Refer to your third-party documentation for more detailed instructions on using this application.

Note: When VisionCAD opens a connection with APCO MEDS, it logs into MEDS using the VisionCAD user ID. Please note, MEDS does not validate the user ID and the user ID does not need to be entered into MEDS.

In the New Call and All Calls windows, click the call handler (EMD/EPD/EFD) buttons to access the MEDS database for procedural instructions on emergency care. With a call highlighted, you can select the EMD/EPD/EFD buttons to open or reopen a case. The following window displays when you click on these buttons.

If the highlighted call has already had a case opened for it, the Reopen Case is active. If no case has been used for the call, the New Case button is active. The Case Summary button is not applicable for this interface and will always be inactive.

Select New Case or Reopen Case and the MEDS window displays with questions to ask and instructions to give the caller.



Page 240

Dispatchers and call takers with appropriate responsibilities will receive Alert messages concerning the call situation as reported in the EMD/EPD/EFD windows.

If an alert message displays on the other VisionCAD dispatch stations, an additional unit may need to be dispatched. Click OK or press the Enter key to close the message. Alternately, press the Select Call button to automatically select the referenced call in the Browse Call window.

Case Questions in APCO MEDS After initializing a case, VisionCAD accumulates answers as they are received until it encounters an answer from a different section. The accumulated answers are added to the call narrative and the answers from the new section are accumulated. This means that after the last general question is answered, the text will not appear in the narrative until a vital point question is answered or a priority type is selected.

The answers to the general questions appear in the narrative under a heading of ** General Question Update **.

The answers to the vital points appear under a heading of ** Vital Points Update **.

If the MEDS narrative feature is used, the narrative text is accumulated with whatever question text is being answered at that time. This typically appears with the word NARRATIVE prefixing the user’s content.

A priority selection appears under a heading of ** Dispatch Priority **. If a priority had been previously set and a new one is selected, the heading is ** Reconfigure Priority **.

Finally, when a case is ended in MEDS, VisionCAD adds the text “MEDS Case Ended” to the narrative.



Page 241

Horizontal Dispatch (APCO MEDS) A horizontal dispatch is a situation where the person using MEDS to take the information from the caller is a different person than the one dispatching the unit. VisionCAD on the dispatching workstations displays the alert window to the CALLS – ExD Horizontal Dispatch configuration option to notify VisionCAD users of the change in response level.

• If the option is No, the MEDS interface will not broadcast alert notices of dispatch recommendations.

• If the option is Yes (the user is a call taker), an alert is broadcast to other VisionCAD workstations for the dispatchers’ attentions: a “Horizontal Dispatch.” From the alert window, click OK or press the Enter key to close the message. Alternately, press the Select Call button to automatically select the referenced call in the Browse Call window.

EMD/EPD/EFD Dispatch Alert

From this message, the dispatcher is able to see the vital data about the affected call: the call number, address, complaint type, and the MEDS-defined priority text. Note that there is a limit of how many characters can be transmitted in the message. The full text will appear in the narrative.

If MEDS sets a priority where there had been a prior priority assignment, the alert window will indicate ** Reconfigure ** in place of ** Dispatch **.

For the Horizontal Dispatch alert message to appear on dispatching workstations, all of the following conditions must be met:

• MEDS must send a Priority status message. (This is the trigger for the alert.)

• On the machine using MEDS, the VisionCAD configuration option must be set to “Yes” for CALLS – ExD Horizontal Dispatch. (This causes it to send the alert.)

• DataBus must be running on all machines. (This allows the alert to be transmitted and received.)

• On the dispatch machine, the VisionCAD configuration option must be set to “No” for CALLS – Separation of Call Taker/Dispatcher. (This indicates that the workstation is a dispatching workstation.)



Page 242

• The affected call must be in the dispatcher’s call responsibility however the call responsibility feature is being used – by zones, by categories, etc. (If the call is not available in the dispatcher’s Browse Active Calls, then the alert message will not display either.)

• The dispatcher’s unit responsibility must be set as follows:

The options for [All], [Zone], [Dept], [Zone + Dept], or [Patrol] will allow the dispatcher to see alert messages from any category of a MEDS call.

For the options of [Category] or [Category + Dept], the dispatcher must be configured for unit responsibility categories as follows:

EMS or FIR to see alerts in the medical category (Med)

POL or SHE to see alerts in the police category (LE)

FIR or FRE to see alerts in the fire category (Fire)

APCO MEDS Medical, Police, and Fire The MEDS interface in VisionCAD supports the use of MEDS for emergency medical, police, and fire. The EMD, EPD, and EFD buttons enable on various call windows.

In the figure below, the EFD interface is disabled and the EMD and EPD interfaces are enabled.

Add New Call Window

All three buttons will initialize a case in the same single instance of MEDS that is running. However, each button will set the category type of the case according to the button used:

• The EMD button sets the MEDS category to “Med.”

• The EPD button sets the MEDS category to “LE.”

• The EFD button sets the MEDS category to “Fire.”

Note: If the referenced category is not defined in MEDS, the case will open with its default category unchanged. The categories in MEDS are not limited to these three. Custom categories can be created for whatever policies and procedures your agency has.



Page 243

If the category is changed in MEDS, VisionCAD will attempt to update its active category according to the category selected in MEDS. Thus, if you start a case with the EMD button, but change the category in MEDS to Fire, and then select a priority, VisionCAD will send an EFD (Fire) dispatching alert that requires the FIR or FRE category responsibilities to see.

If the MEDS category is changed to a type unknown to VisionCAD (like MEC), VisionCAD will leave the active category unchanged. Thus, if MEDS is started with the EPD button and the category is changed to MEC, VisionCAD will send a Police dispatching alert, based on the last known category determined by the button used.

The following fields are passed from VisionCAD to MEDS for the initial case entry.

• Call Number

• Location

• Caller Name

• Telephone Number

The following windows in VisionCAD contain the EMD, EPD, and EFD buttons:

• Add New Call – From this screen, the call handler buttons accesses MEDS and initializes a new case (after saving the the VisionCAD call).

• Full Call / Historical Edit – If an active call is viewed, the call handler buttons present the MEDS Case Entry choice window. If a historical call is viewed, the call handler buttons display a message informing you that the case summary option is not applicable for this interface.

• Historical Calls View Only – From this screen, the call handler buttons display a message informing you that the case summary option is not applicable for this interface.

• Browse Active Calls – From this screen, the call handler buttons present the MEDS Case Entry choice window.



Page 244

APCO MEDS Case Entry Choice Window

A button is disabled if it is not appropriate for the call.

Button Description

New Case Creates a new case in MEDS. This button is disabled if a case has already been created for the call.

Reopen Case Reopens an existing case in MEDS. This also reopens a pending case in MEDS. This button is disabled if a case has not been created for the call.

Case Summary This button is not applicable and is always disabled.

Cancel Closes the window without taking action.

APCO MEDS Case Entry buttons

Call Handler Commands with APCO MEDS The VisionCAD command line provides commands for accessing the MEDS call handler applications:

• EMDN call#

• EPDN call#

• EFDN call#

These commands create a new case in MEDS with the corresponding category: Medical (Med), Police (LE), and Fire. If a case has already been created for the call, an error message displays “An XXX case already exists for call number xxxx,” where XXX corresponds to the call handler option used (EMD, EPD, or EFD).

• EMDR call#

• EPDR call#

• EFDR call#

These commands reopen an existing case in MEDS with the corresponding category. If a case has not been created for the call, an error message displays “No XXX case exists for call number xxxx.”

• EMDS call#

• EPDS call#

• EFDS call#

These commands are not applicable for this interface and will generate an error message if used, “The MEDS interface does not allow reviewing a case from CAD.”



Page 245

The normal commandline features continue to work. The partial call number feature works for the call# parameter. The “X” feature uses the selected call in the Browse Active Calls window.

The New case and Reopen case commands cannot be used against closed calls. If these commands are issued against a closed call, an error message displays “The XXX command cannot be run on closed call xxxxxx.”

CAD Call Complaint Updates from APCO MEDS VisionCAD provides an option that allows MEDS to update the CAD complaint code of the call when MEDS sets the Priority Code. VisionCAD Global and Local Configurations contain the following option in the item list:

INTERFACES – ECH Updates Complaint – Do you want the Emergency Call Handler interfaces (EMD, EPD, EFD) to update the call complaint when a CAD incident code is determined?

If this option is set to Yes, then a Dispatch or Reconfigure by MEDS updates the call’s complaint to the priority code provided by MEDS.

MEDS Priorities can be configured to contain CAD Complaint Codes according to the dispatch determinants. An administrator can set these in MEDS Guide Card Editor via the Priority page. (MEDS refers to the top level of this tree list as the “Priorities” and the sub-levels as “Symptoms.”)

Guide Card Editor – Priority



Page 246

Note that if the individual symptom (like Uncontrolled Bleeding) does not have a priority code, the priority code of the parent (like ALS Priority) is sent. If neither level has a priority code, the text of the option selected is sent. In any case, if the ECH Updates Complaint option is turned on in VisionCAD configuration, VisionCAD will use whatever text it receives from MEDS on a priority change to update the complaint of the call.

When a priority symptom does not have a priority code, you must click in the space after the diagram line to enable the Edit Code button for editing.

Adding the First Priority Code

Note: While VisionCAD attempts to use the priority code for setting the complaint, the text in the call narrative will always be the text of the option chosen in MEDS. For example, for “Uncontrolled Bleeding,” VisionCAD will show in the call narrative the text “ALS Priority: Uncontrolled Bleeding.”

A VisionCAD administrator can edit the MEDS Priority Codes to contain CAD Complaint Codes as defined in General Edit in the Complaint table. These values can be as detailed as necessary for an agency’s operation and reporting purposes. If detailed statistics on the kinds of calls are desired, there can be a CAD complaint for each symptom in MEDS. Or, if only basic reporting is required, a CAD Complaint could be entered only for the parent priority on the guide card.

When VisionCAD updates the complaint of a call, it also updates the complaint-related data in the call as defined in the Complaints table. The following fields are updated when the complaint is changed.

• Categories

• Ten Code

• Priority – if Complaint record is blank, the Config priority is used (CALLS – Priority).

• Class – if Complaint record is blank, the Config class is used (CALLS – Call Class).

• Warn Units Overdue – if Complaint Timeout is blank, the Config default is used (UNITS – Default Overdue Time).



Page 247

• Warn No Dispatch

• Warn By Complaint

• Default Fire Grade

• Report Reqd

• Subject Reqd

If MEDS supplies a CAD code (priority) that does not exist in the Complaints table, the call’s complaint is updated anyway. This is consistent with the command line operation that populates a new miscellaneous call with an unknown complaint code that may have been mistyped. When the call is cleared with an invalid complaint, VisionCAD presents an error notification to the dispatcher. The dispatcher must correct the complaint before the call can be cleared.

Error - Invalid Complaint

The complaint history for the call is also maintained. As MEDS dispatches and reconfigures a particular call, the call’s existing complaint is entered into the complaint history as it is changed. The figure below, displayed from the Call – View Complaints menu, shows the history of reconfigures for a call.

Call Complaints Window



Page 248

Split Call Operation with APCO MEDS VisionCAD’s MEDS interface allows for and cooperates with the Split Call feature. Whether an agency uses Split Calls or not, the VisionCAD user has full discretion on whether to split a call based on MEDS’ recommendation. The interface does not automatically split calls.

VisionCAD’s Split Call feature splits the call based on the categories in the complaint at the moment it is saved, so when MEDS is activated from the Add New Call window, the call is split and saved, and MEDS is launched. When this occurs, the MEDS interface selects the call with the best category according to MEDS.

For example, if a multi-category complaint is chosen in Add New Call, such as TERRORIST in the following figure, the call splits into multiples for the POL, FIR, EMS, RES, and FRE categories.

Add New Call Window, Multi Category

If the EMD button is clicked to open a MEDS Medical case, the case is associated with the EMS call. Likewise, a MEDS Police case will be associated with the POL call and a MEDS Fire case will be associated with the FIR call. No matter how the call is split, the case being initialized will associate with the best category according to the type of MEDS case.



Page 249

Each MEDS category chooses the best category according to the ranking shown in the following table.

Medical Police Fire

EMS POL FIR

FIR SHE FRE

FRE FIR RES

RES FRE EMS

POL RES POL

SHE EMS SHE

OTH OTH OTH

Rankings by Category

As according to the table, if a MEDS Medical case is initialized, VisionCAD posts the MEDS narrative entries to the EMS call, if there is one. If not, it looks for a FIR call. If there’s no FIR call, it looks for an FRE call, and so on until it finds one. When using a MEDS Police case, VisionCAD looks for POL first, SHE second, etc.

For example, if a call splits into EMS, POL, and FIR, the EMD button will choose the EMS call, the EPD button will choose the POL call, and the EFD button will choose the FIR call. On the other hand, if a call splits into EMS, FRE, and RES calls, then the EMD button will choose the EMS call, the EPD and EFD buttons will choose the FRE call.

Split Call Categories

Medical Choice Police Choice Fire Choice

EMS, POL, FIR EMS POL FIR

EMS, FRE, RES EMS FRE FRE

FIR, SHE, RES FIR SHE FIR

Category Choices for Split Call Examples

This operation allows the MEDS interfaces to work flexibly with agencies that categorize in different ways, such as those that dispatch medical responses from their fire departments, or law enforcement responses from their sheriff departments, etc.

Using the example shown in Add New Call Window, Multi Category, a MEDS Medical case selects the EMS call in the Browse Active Call window.



Page 250

Browse Active Calls

APCO MEDS Narrative Example The following shows an example narrative that results when starting MEDS from the EMD button and changing the type of the case to Fire while answering questions. Note in the “General Questions Update” section that the change in the emergency type is indicated.

[05/04/2011 11:39:31 : pos99 : tc01] MEDS Case Ended [05/04/2011 11:36:47 : pos99 : tc01] ** Reconfigure Priority ** 2nd Alarm [05/04/2011 11:36:10 : pos99 : tc01] ** Dispatch Priority ** Initial Alarm: Garage Fire - Report of fire or smoke from an unattached garage with no exposure to the main house [05/04/2011 11:36:10 : pos99 : tc01] ** Vital Points Update ** Are you in a safe place? YES Can you escape? YES What is the exact location? GARAGE IN BACK OF HOUSE Is there just a fire or just smoke? Smoke only What part of the building is on fire? FRONT WINDOW If garage: Is it attached to another structure? NO Is it close to any other structures? NO



Page 251

Are there any vehicles, propane tanks, chemicals, gas cans, or other hazards inside? NO Any hazardous materials stored in or near the structure? NO NARRATIVE: CPLT ADV PETS NOT IN HOUSE Was there an explosion? NO Is there anyone inside? NO Any known injuries? NO Any suspicious people or vehicles seen in the area? NO Have they left the area? NO [05/04/2011 11:35:10 : pos99 : tc01] ** General Questions Update ** Emergency Type: Fire Do you see smoke or fire? Smoke What is the color of the smoke? BLACK Where are you in relation to the incident? ACROSS STREET AT RESIDENCE Chief Complaint Structure Fires [05/04/2011 11:32:49 : pos99 : tc01] Cross streets: E OAK ST//W PINE RD

APCO MEDS Interface Messages The following are messages that the MEDS interface may display.

• A case in MEDS is still open. Please close the case first. A second MEDS case was started in VisionCAD without closing the prior case. Close the case in MEDS and then create a new case from the case entry dialog that pops up from the call handler (EMD/EPD/EFD) buttons on Browse Active Calls.

• The MEDS interface does not allow reviewing a case from CAD. Although the Case Summary button is disabled to prevent reviewing a MEDS case from VisionCAD, the EMDS command from the command-line will display this error. Also, EPDS, and EFDS do not work with MEDS.

• A case (xxxxx) was begun in MEDS that cannot be captured to a CAD Call. A new case was started in MEDS. VisionCAD has no call associated with it and will not accumulate the question text. The case can be worked in MEDS if desired, but the text won’t be in VisionCAD. The same thing would occur without any error messages if MEDS was started without VisionCAD running or connected and cases were entered.

• The APCO MEDS interface failed to login. Please ensure that MEDS is not already logged in. This can occur if MEDS is logged in when VisionCAD tries to initialize a new connection with a new case. VisionCAD will fail to connect in this case. Log out of MEDS and try opening the call again.



Page 252

• MEDS reported a command failure for xxxxx. This possibly indicates a program error on the interface. The name of the command encountering the error is displayed in the message.

• MEDS returned error code xx for opCode yy. MEDS reported an error event with the indicated operation code number. This likely indicates a program error.

• CAD cannot communicate to MEDS using TCP. VisionCAD could not open the TCP port. Ensure that the VisionCAD configuration for TCP port matches the number in the Configure MEDS utility for Default TCP Port within the CAD Interface setting.

VisionCAD/APCO MEDS Interface Settings

The following configuration options must be set in the Interfaces category in VisionCAD Configuration to enable and optimize the interface between VisionCAD and APCO MEDS.

Parameters Setting

EMD/EPD/EFD In Use Options

Set these options to Yes for each APCO MEDS emergency category in use.

• Set the EMD In Use option to Yes if you are using MEDS for Emergency Medical Dispatch.

• Set the EPD In Use option to Yes if you are using MEDS for Emergency Police Dispatch.

• Set the EFD In Use option to Yes if you are using MEDS for Emergency Fire Dispatch.

EMD/EPD/EFD Data Format Options

For each APCO MEDS emergency category in use, enter its corresponding configuration option.

If the value is set to “APCO,” the MEDS interface is activated via the EFD/EMD/EPD button(s) in VisionCAD.

EMD/EPD/EFD TCP Port Options

For each APCO MEDS emergency category in use, enter its corresponding configuration option.

TCP functionality is enabled by entering a non-zero value in this field. This number should match the port number setup in the configuration for the call handling program. A value of 0



Page 253

Parameters Setting (zero) will not activate this interface.

If using more than one option, these three options must use the same port number for accessing MEDS. Multiple instances of MEDS may not be started; however, depending upon the button selected (EFD, EMD, or EPD) a different category is set for the MEDS case.

ECH Updates Complaint

Set this option to Yes if you want the Emergency Call Handler interfaces (EMD, EPD, EFD) to update the call complaint when a CAD incident code is determined?

ExD Horizontal Dispatch (Calls category in CAD Configuration)

This option should be set at a local workstation, based on whether the user initiates EMD, EPD or EFD and also dispatches responders from the same workstation (vertical) or if the user is solely a call taker (horizontal).

The following configuration options must be set in the APCO Configure MEDS utility to optimize the interface between VisionCAD and APCO MEDS.

Configure MEDS – CAD Interface

• The Default TCP Port controls what port is used by MEDS. The default is 2021, which should be changed if another application on the machine is also configured to use 2021. The value in VisionCAD configuration should match the value here. The port number should not be set to anything less than 1024.



Page 254

• The Connected and Disconnected fields are useful to visibly show whether VisionCAD is connected to MEDS or not. VisionCAD will automatically attempt to connect to MEDS when it initiates a new case in MEDS. Note that when MEDS is reconfigured, it will drop the TCP connection. VisionCAD will reconnect the next time it creates a new case.

Configure MEDS – Call Buttons

• The Start Call button should be disabled to help prevent accidentally starting a new case in MEDS without a VisionCAD call to associate it with. A call must be started in VisionCAD to assign the new call number and create the call to hold the MEDS narrative text. If a case is started in MEDS while VisionCAD is connected, VisionCAD will display an error message: A case (xxxxxxxx) was begun in MEDS that cannot be captured to a CAD Call.

Note: A case can still be manually started in MEDS by using hotkeys and/or the menu options. For proper operation in VisionCAD, these options must be avoided. While VisionCAD has the ability to lock the interface so that a new case can’t be created, this also locks the End Case function. Requiring the operator to switch over to VisionCAD to perform one last little step to end the case after the phone call could be a bigger disruption in the workflow. If this step was forgotten, then the operator would be interrupted when trying to start a new call in VisionCAD that goes to MEDS.



Page 255

Configure MEDS – Continue Case

• To use the Reopen Case option in VisionCAD, the Continue Case option must be enabled in MEDS. This option is disabled by default.

• Note that the Look Back time controls how old a case can be and still be reopened. If more time has elapsed, the Reopen Case option in VisionCAD will actually cause MEDS to initialize a new case.



Page 256

Configure MEDS – General Questions Narrative

• The question type should be set to Question + Entry so that the VisionCAD narrative will show the question and answer text.

• The option for Notify CAD when entries are cleared should be set if you want an indication that an existing answer was deleted. If this option is not set, then when an answer is cleared, the former answer remains in the VisionCAD narrative as VisionCAD will get no indication that it was deleted.

When an answer to a question is deleted, the VisionCAD narrative will show <TEXT ENTRY CLEARED> for the question.

Note that if an answer is changed, VisionCAD will show the new answer in the narrative after the old answer that occurred earlier.



Page 257

Configure MEDS – Vital Point Narrative

• The question type must be set to Question + Entry Type + Entry so that VisionCAD can recognize the vital questions separately from the answers. When a vital point answer is changed during the data entry, VisionCAD can detect the change and update the question rather than repeat the question/answer text in the narrative. Without this setting, VisionCAD can only do what it does for general questions by appending each question/answer combination to the narrative as they occur.

As with General Questions, the Notify CAD when entries are cleared option will show <TEXT ENTRY CLEARED> for vital point fields that the user clears out.


Appendix A. NCIC Queries

Page 259

APPENDIX A. NCIC QUERIES

Overview

If your NCIC query interface is set up in CAD Configuration, when a call is saved or transmitted, the query is sent to your state’s crime information database. You may also enter a query from the CAD VisionMOBILE window, Query screens. These screens provide for the following queries: Person, Vehicle, Article, Gun, Image, and Free-form text. State-specific query screens provide additional customized queries, such as Missing Person, Hazard, and Bicycle.

Note: This chapter refers to all queries as “NCIC.” Your agency may be using a different database to query criminal records, such as CLETS, or FCIC.

VisionMOBILE Window for NCIC Queries If your agency uses TriTech’s VisionMOBILE software, you can also communicate with Mobile users from this window. The following buttons in the VisionMOBILE window are used for Mobile only: Chat and Status. The buttons Login, Logoff, and Query are used for NCIC queries. CAD users can also view the returns from VisionMOBILE queries in the CAD Query window.

To display the VisionMOBILE window, click on the MCT button on the main toolbar of CAD Dispatch. A login popup window displays for you to enter your login password to the VisionMOBILE Message Switch.



Page 260

Once the login is successful, the VisionMOBILE window displays in CAD, as shown below.

Note: If the query screen does not display immediately in the MCT window, click the Query button.

Query Results After you click Send (or if the query is sent automatically) the results are returned in the lower portion of CAD’s VisionMOBILE (Query) window. (Some states have a separate “Results” tab for their query screen.)

Note: If the option to send queries automatically when a call is saved is set up in CAD Configuration, the telecommunicator has only to view the results in the VisionMOBILE window; the telecommunicator does not have to send the query. The VisionMOBILE window displays the NCIC results with information related to the current call. If there are multiple NCIC responses for the current call, all responses are displayed in the window.

See the section “Viewing Query Returns” later in this chapter for details on this function.



Page 261

Generic and State-Specific Queries When CAD is installed, your agency will either use the generic Query screen or a state-specific Query screen (CA, MN, NC, and VA). In Local Configuration, choose File, then MSG. From the Vision tab, enter the code for your state or county query interface in the Interface Query Type field. (For example: NC or CA_LA.) This option determines which Query screen is available to you: the Generic or a customized version.

You can also set up in CAD Configuration whether or not to automatically send NCIC queries once a call is entered and saved. If this option is set up, the Query is automatically sent when the call is saved, and the results can be viewed in the VisionMOBILE window.

This chapter provides an overview of sending queries and viewing query returns. This includes the customized state-specific screens listed below. These customized query screens are presented after the “Generic” section in alphabetical order, and include the following states:

• California – Los Angeles County (CA_LA)

• Minnesota (MN)

• North Carolina (NC)

• Virginia (VA)

See the section in this chapter on the specific type of query you want to perform for details on this function (Person, Vehicle, etc. or CA – Los Angeles County, Minnesota, etc.)

User Rights To enable users to perform NCIC queries, you must check the CJIS Query rights for them in the VisionMOBILE Message Switch Configuration utility. If you do not have this user right the NCIC query options will be disabled. This applies if you are using VisionMOBILE versions 3.7 Update 3 or higher.

If you are using an earlier version of VisionMOBILE, then VisionCAD will determine if you have access to perform NCIC queries based on Right 46: NCIC in the Front End Security module.

Sending Generic Queries

For states other than California, Minnesota, North Carolina, and Virginia, the “generic” NCIC Query screens display for you to enter information in the fields for the queries. Once all information is entered, you can click on Send to send the queries to NCIC.



Page 262

The list below defines the types of generic queries you may send to NCIC.

Button Definition

Person Use the Person button to enter a query on a person.

Vehicle Use the Vehicle button to enter a query on a vehicle.

Article Use the Article button to enter a query on an article.

Gun Use the Gun button to enter a query on a gun.

Free-Form Use the Free button to enter text in a standard format for a free-form query to NCIC. Your agency should provide the format of the information for you to enter.

Image Use this button to search for an image.

Tables describing the fields for each query are provided in the appropriate section for that query: Person, Vehicle, Article, Gun, Image, and Free-Form.

For each query performed, there are two buttons you can use: Send and Clear:

Button Definition

Send After you have filled in the fields in the upper portion of the window, select the Send button to submit a Query request to NCIC.

Clear To clear the data from all the fields in the current Query, click on Clear. You can then begin to enter a new query by entering data in the cleared fields.

The Query returns display in the lower portion of the VisionMOBILE window, Query screen. If the fields do not display for you to enter data, double-click the mouse in the center of the white area in the VisionMOBILE window, Query screen. This action toggles the view between field entry/results to only results in a larger window.



Page 263

Sending a Person Query Step 1. With the call for which you want to send an NCIC query highlighted in the All

Calls window, click on the MCT button on the main CAD Dispatch toolbar.

Step 2. The VisionMOBILE window displays. In the VisionMOBILE window, click on the Query button.

Step 3. If the query fields are not displayed at the top of the window, double-click in the large white space in the window. The Person fields should display at the top of the window.

Step 4. Click on the Person button and enter information in the fields.

Step 5. The fields for the Person Query are described in the following list.

Field Definition

ORI Enter or select the ORI (jurisdiction) in this field. This is for Pennsylvania users.

Last Name Enter the last name of the subject in this field. * This field is required.



Page 264

Field Definition

First Name Enter the first name of the subject in this field. * This field is required.

Middle Name Enter the middle name of the subject in this field.

State Select the state that issued the operator license from this drop-down box.

OLN Enter the operator license number in this field.

SSN Enter the person’s social security number.

Sex Select the sex of the query subject from this drop-down box. * This field is required.

DOB Enter the date that the query subject was born in this field. * This field is required.

Step 6. Place a checkmark in NCIC and/or RMS to specify the data source you want to search.

Step 7. Then, click on the Send button. Returned results display in the white area of the window. Click on the Query button to redisplay the results.

Step 8. Refer to the section “Viewing Query Returns”.

Sending a Vehicle Query Step 1. With the call for which you want to send an NCIC query highlighted in the All






Page 265

Step 4. Click on the Vehicle button and enter information in the fields.

Step 5. The fields for the Vehicle Query are described in the following list.

Field Definition


State Select the name of the state that issued the license from this drop down box.

License Plate Enter the license number of the vehicle in this field.

License Year Enter the year that the license tag was issued.

License Type Select the type of vehicle/license plate from this drop-down box.

VIN Enter the Vehicle Identification Number in this field. * This field is required.

Make Enter the name of the company that manufactured the vehicle in this field.



Page 266

Field Definition

Vehicle Year Enter the year of the vehicle in this field.




Sending an Article Query Step 1. With the call for which you want to send an NCIC query highlighted in the All






Page 267

Step 4. Click on the Article button and enter information in the fields for the article, or property.

Step 5. The fields for the Article Query are described in the following list.

Field Definition


Type Enter the type of article.

NIC Enter the NCIC-generated number for the stolen article.

Ser Enter the article’s serial number.

OAN Enter the Owner Applied Number of the article. The owner generates this number.





Page 268


Sending a Gun Query Step 1. With the call for which you want to send an NCIC query highlighted in the All




Step 4. Click on the Gun button and enter information in the fields.

Step 5. The fields for the Gun Query are described in the following list.

Field Definition




Page 269

Field Definition

NIC Enter the NCIC-generated number for the stolen gun.

Make Enter the make of the gun.

Ser Enter the gun’s serial number.

CAL Enter the gun’s caliber.




Sending a Free-Form Text Query Step 1. With the call for which you want to send an NCIC query highlighted in the All




Step 4. Click on the Free button and type text in the white area of the window. Additionally, enter or select an ORI (jurisdiction) Pennsylvania users, if desired.




Page 270


Sending an Image Query Step 1. With the call for which you want to send an NCIC query highlighted in the All



Step 3. If the query fields are not displayed at the top of the window, double-click in the large white space in the window. The query fields should display at the top of the window.



Page 271

Step 4. Click on the Image button and enter the image number you want to retrieve. Additionally, enter or select an ORI (jurisdiction) Pennsylvania users, if desired.



Viewing Query Returns

To access the VisionMOBILE window to view Query results, complete the following steps.

Step 1. With the call for which you want to display NCIC information highlighted in the All Calls window, click on the MCT button on the main CAD Dispatch toolbar.



Page 272

Step 2. If results have been returned, they will display in the white area of the VisionMOBILE window.

Step 3. The Query returns display in the lower portion of the VisionMOBILE window, Query screen. If the fields do not display for you to enter data, double-click the mouse in the center of the white area in the VisionMOBILE window, Query screen. This action toggles the view between field entry/results to only results in a larger window.

Step 4. The options available from the NCIC Query/Results window are described in the following list.

Option Definition

Prev Select this option to view the previous return.

Next Select this option to view the next return.

Delete Select this option to delete the currently displayed record in the NCIC Responses window.

Print Select this option to print the currently displayed record in the NCIC Responses window.

Copy to Call Highlight the desired call record and then select the text in



Page 273

Option Definition the NCIC Responses window. Press the Copy to Call option and the selected text will be copied to the highlighted call’s narrative.

Note: This is not applicable for CA, MN, NC, and VA agencies due to the state specific query functions.

Step 5. Select the option you want to perform, by clicking the appropriate button.

Viewing Images Images returned will display on the Images pane of the MCT window. Click the Image button to bring that section into focus.

The counter at the bottom of the screen will show how many images are available and which image is currently displayed.



Page 274

The following table explains the buttons available on this screen.

Button Description

Prev Click this button to move to the previous image.

Stretch Image Click this button to stretch the image to cover more of the available window space.

Delete Click this button to delete the currently displayed image.

Next Click this button to move to the next image.

California – LA County

The Vehicle Tab



Page 275

The Property Tab

The Gun Tab



Page 276

The Bicycle Tab

The JAI Tab



Page 277

The Driver History Tab

The CCHRS Tab



Page 278

The WANT9 Tab

The Query Tab



Page 279

Minnesota

Returns Click on the Query tab in the Mobile window to view Query results.

The Vehicle Tab

The History Tab



Page 280

The QD Tab

The Free Tab

North Carolina

Returns The Returns tab displays on top in the DCI window. Click on the Returns tab at any time to view query results previously sent. From the Returns screen, you can Print, or Acknowledge (Ack) receipt of returns.



Page 281

Note: If using VisionMOBILE Message Switch 3.5 update 6, then acknowledging (Ack) receipt of returns is no longer necessary.

The Vehicle/Part/Plate Tab



Page 282

The Drivers Tab

The Boat Tab



Page 283

The Securities Tab

The Articles Tab



Page 284

The Gun Tab

The Wanted/Missing Persons Tab



Page 285

The Missing Persons (Only) Tab

The NLETS Hazardous Material Tab



Page 286

The Free Tab

The AOC for Criminal Defendant Name (ACD Tab)



Page 287

The AOC for Criminal Individual Record (ACI Tab)

The AOC for Criminal Court Record (ACR Tab)



Page 288

The AOC for Defendant and Witness Court Schedule (ACS Tab)

Virginia

Returns Click on the Query tab in the Mobile window to view Query results.

Required Fields for a Query

QW1 Query Wanted Persons Name*

Sex*

Race*

DOB*

SSN



Page 289

OLN

MNU

FBI

QV Query Vehicle QV1 By Plate

Plate*

State*(either Blank or ‘VA’)

Year

Type*

Purpose

QV2 by Vin

VIN*

Purpose

QVN Query vehicle registration by Name Name*

SSN

Title

Purpose*

QD Query Driver QD1 by Name

Name*

DOB*

Sex*



Page 290

Purpose

Code or Badge

Commonwealth attorney

County or City of Jurisdiction

QD2 by SSN

SSN*

Purpose

Code or Badge

Common Wealth

Count or City of Jurisdiction

QT Query Driver Transcript QT1 by Name

Name*

DOB*

Sex*

Requester

Purpose*

QT2 by SSN

SSN*

Requester*

Purpose

QH Query Criminal History Name*



Page 291

Sex*

Race*

DOB*

Purpose*

ATN*

Search of Sex Offender Registry (Blank or ‘Y’)

QR Query Criminal Record QR1 by SID

SID*

Purpose*

Attention*

Department

Building

Address

City

Zip

-QR2 by FBI

FBI*

Purpose*

Attention*

Department

Building

Address

City



Page 292

Zip

RQ Query Out of State Vehicle RQ1 by Plate

Plate*

State*

Year

Type*

RQ2 By Vin

State

VIN

QG Query Gun Serial Number*

Make

Caliber

QA Query Article Serial*

Type*

DQ Query Out of State Driver DQ1 by Name

Name*

DOB*

Sex*

State*



Page 293

DQ2 by OLN

OLN*

State*

The License Tab



Page 294

The Wanted Tab

The C.H.-C.R. Tab



Page 295

The Article Tab

The Driver Tab



Page 296

The Free Form Tab


Glossary

Page 297

GLOSSARY The glossary contains definitions of some basic terms used in the Computer-Aided Dispatch (CAD) system. Since each agency has its own naming conventions and refers to things with its own set of terms, the following definitions are provided to help you clearly understand the meanings of CAD terms and correlate them with those you are accustomed to using.

Term Definition

Alarm Grade Instructions

Instructions the dispatcher should follow for each Alarm Category. For example: Fires of different grades or levels require that the dispatcher follow specific sets of instructions. These instructions should be entered in the Alarm Grade Instruction database, in the General Edit module.

ALI Automatic Location Identifier

Alias An alias is a name other than what is recorded on a birth certificate by which the individual may be known.

ANI Automatic Number Identifier.

Audit Trail An audit trail allows you to view which database and fields have changed, what change has been made, who made the change, and when they made it.

AVL Automatic Vehicle Location

B & E Breaking and Entering

Bitmap Picture representation that displays on the screen instead of text or numeric characters.

BOLO Be On the Lookout

CAD Computer Aided Dispatch

Call An incident phoned into a police, fire, or EMS dispatch center.

Call Number Sequence numbers set up by the agency to track and record


Glossary

Page 298

Term Definition Sequence CAD calls.

Call Taker The person in an agency that receives a call for an incident. This person may or may not be a dispatcher.

Category A type of responding agency, such as Police, Fire, Sheriff, First Responder, Rescue, or Emergency Medical Service (EMS). These are sometimes referred to as groups.

Complaint Types Complaint Types convey far more than just a description of the complaint. Each type has an associated priority, class, ten code, and responding departments. Your agency should determine the information for each complaint type and enter them into the system.

Department A specific department of a responding agency, such as Any City Police Department, Any County Sheriff, and Any District Fire Department. Departments are defined in the General Edit Departments Database.

Dispatcher The person in an agency that enters a call for an incident into the CAD system. This person may or may not be a call taker.

Dispatch Zone A zone or area to which dispatchers are assigned dispatch responsibilities. This might include an entire city or county, or it might include only certain regions. How the area for which your agency is responsible is divided depends on things such as call activity and the size of the agency. If dispatchers are assigned responsibility by dispatch zones, they will take only calls from the dispatch zone or zones assigned to them. The dispatch zones and their boundaries are defined in General Edit Dispatch Zones.

DMV Department of Motor Vehicles

DOB Date of Birth

DOT Department of Transportation

E911 Enhanced 911

EMS Emergency Medical Service

EMS (Run) Zone A specific area by which EMS responsibilities are defined. EMS Zones or Run Zones are defined and used in the EMS Run Card Database. They are associated with an Internal Response Area (IRA) in the IRA database, and the IRA is


Glossary

Page 299

Term Definition associated with GEO (geographic) entries for specific addresses. This is how EMS Run Zones are applied to specific locations.

ESN Emergency Service (Area) Number. ESNs are set up by the telephone company in conjunction with your input and transmitted along with the E911 data. You should be familiar with the system your phone company uses in assigning these ESNs. ESNs are not always available in the E911 ALI feed.

Evacuation Route This is a route for a specific geographic area that dispatchers can use to instruct citizens in case of an evacuation.

Fax Server The computer, or server, through which faxes are processed.

Filter Filters display a subset of records defined and sorted by the criteria that the user provides.

Fire Plans The Fire Plan database contains detailed information about a specific site for use in a fire or other emergencies. This information will help your agency respond quickly and efficiently to situations that are dangerous or have the potential to become dangerous. Using a fire plan, you can create and store address-specific information that includes data crucial to those responding to a fire.

Fire (Run) Zone A specific area by which fire responsibilities are defined. Fire Zones or Run Zones are defined and used in the Fire Run Card Database. They are associated with an IRA in the IRA database, and the IRA is associated with GEO entries for specific addresses. This is how Fire Run Zones are applied to specific locations.

Format Mask Displays the mask being used to create call numbers. The following table describes the possible format masks you can use and shows examples of the results each produces.

Type of Data Format Mask Formatted CAD

Number Only 0000 00001

Literal & Number “WPD”0000 WPD0001

Year & Number yy-00000 97-00001

Year & Month &


Glossary

Page 300

Term Definition Number yymm-0000 9701-0001

Year, Month, Day, & Number yymmdd-0000 970112-0001

GEO Geographical file database

Global Configuration Global Configuration settings affect all workstations in a jurisdiction. These are maintained by the System Administrator.

GPM Gallons per Minute

Group See Category

HazMat Hazardous Materials

Internal ALI If your agency’s CAD system interfaces with Enhanced 911 (E911), your dispatchers will be provided complete caller information and you will not need to set up an Internal ALI database. (However, even if your agency interfaces with E911, you can use the Internal ALI database for other information.) If your agency does not use E911 you can set up an internal ALI database so dispatchers will receive more detailed information than just the caller’s phone number.

IRA Internal Response Area. Internal Response Areas define response scenarios which indicate the groups or agencies (Police, Fire, EMS) that should respond to calls in specific areas. They also specify which departments should send units (Police Department A, Fire Department D, EMS Department C for example). IRAs include Fire and EMS Run Zones and Tracts. Multiple scenarios can be defined for an area to provide for a primary scenario and as many backups as you would like to have planned. IRAs are defined by your installation.

Jurisdiction A jurisdiction is an overall area of responsibility. An installation could provide service for one, or more than one jurisdiction. For example, an installation could be responsible for just one small county so it would need only one jurisdiction. Another installation could provide service for the county and the major city within that county. This installation could use two jurisdictions, one for the county, and one for the city.


Glossary

Page 301

Term Definition

Landmark A prominent or identifiable feature of a landscape, such as buildings, stores, churches, schools, historic markers, etc.

LEO Law Enforcement Officer

Local Configuration Local Configuration settings affect one workstation. These settings are accessible through the CAD home screen.

Mask See Format Mask

MDT Mobile Data Terminal

MO Method of Operation

Move-Ups Move-Ups provide dispatchers with information when handling various types of calls, such as EMS. For example: When a dispatcher requests to view EMS move-ups, the system checks this database to see if the current situation matches any situations in the database. If a match is found, the instructions are displayed to the dispatcher. These instructions can indicate what station should move up a unit to provide back-up coverage. They should also include whatever information your agency normally expects a dispatcher to have access to when dealing with a particular EMS situation.

MSAG Master Street Address Guide

Narratives This is a record of notes and any other text you would like associated to a record.

NCIC National Crime Information Center

NIBRS National Incident-Based Reporting System

NOK Next Of Kin

OCA Case File Number

OCC Number The number of Occupants at a location.

Patrol Areas Patrol Areas are geographical areas of your jurisdiction that a unit works. These areas may float, or may be standard. The patrol area is assigned when a unit is brought on duty or at any time during a shift by using the Patrol Area Change option. These must be built previous to building the IRAs


Glossary

Page 302

Term Definition since they are the core of the Unit Suggestion option.

PSAP Public Safety Answering Point

Quad Enter the quadrant for the address, if applicable (N for North, etc.).

Realtime Printer A printer that is set up to print calls as they are entered in the system.

RMS Records Management System

Run Cards Run Cards are sets of instructions for dispatchers to follow based on given situations. Each run card contains one set of instructions. You may have one run card for each combination of Complaint Type, Alarm Grade Level, and Run Zone. These instructions are set up in the General Edit module.

Run Zones Run Zones (such as Fire Zones and EMS Zones) are defined and used in the EMS and Fire Run Card features. Run Zones are completely independent of the patrol zone. They provide a way to assign fire and EMS responsibilities and responses. Run Zones are then associated with an IRA in the IRA database, and GEO entries are assigned IRAs for specific addresses. In this way, Fire and EMS Run Zones become associated with specific areas or addresses.

Service Areas Service areas are used by CAD only for wrecker rotations. They are usually large and not necessarily strictly defined. They provide a way to determine available wrecker companies for a location.

SQL Structured Query Language

SSR Residence checks (safety and security ride-by’s)

Sub-Patrols Sub-patrols are sub-patrol areas that are set up to allow an installation to have geographically different patrol areas at different times and to automatically change between them. Sub-patrols are defined in the Units database, and changes between patrol areas are done using the CAD Mass Patrol Change option.

Suggest Unit CAD function that suggests units to dispatch based on the call type.


Glossary

Page 303

Term Definition

Ten Codes Each agency must enter its own ten codes and complaint types individually to ensure the integrity of the information with which CAD interacts.

Tract A division of a jurisdiction that is used for statistical purposes only. A jurisdiction might be divided into North, South, East, and West tracts to help agencies keep statistics on crimes or accidents. Tracts could also be defined by neighborhood or any other breakdown you might need. Tracts are defined in the General Edit Internal Response Area (IRA) database.

Units Units are entities dispatched using a single code. A unit might be one officer, a patrol car, an EMS station, or even a fire station.

Validation Process that ensures that the data entered meets your IBASE or UCR reporting requirements.

VIN Vehicle Identification Number

Warrant A judicial writ authorizing an officer to make a search, seizure, or arrest, or to execute a judgment.

Wrecker One that is used in recovering or removing a wreck, especially a truck with a hoist and towing apparatus used in towing disabled or wrecked vehicles.

Wireless Indicator The character in the ALI feed that designates a wireless call. This field should be set in ALI Layout based on your compliance with APCO Project 31.


Index

Page 305

INDEX * Flag ....................................................... 214 A Flag ...................................................... 218 Aborted Case ........................................... 218 ACS FIREHOUSE Query Interface ......... 114

Configuring ......................................... 114 Using .................................................. 117

ACS FIREHOUSE Search ....................... 117 Alarm Interface ........................................ 123

General Edit ........................................ 126 Set Up ................................................. 124

APCO MEDS ........................................... 239 Call Handler Commands .................... 244 Case Questions .................................. 240 Complaint Updates ............................. 245 Horizontal Dispatch ............................ 241 Interface Messages ............................ 251 Interface Settings ............................... 252 Narrative Example .............................. 250 Split Calls ............................................ 248 Using .................................................. 242

Assign OCA Number .................................. 52, 53

Baud ........................................................ 198 C Flag ...................................................... 218 CAD

Configuring Mobile Interfaces ............... 12 Creating an RMS OCA Number ..... 52, 53 EMD, EPD, EFD Interface .......... 209, 239 Fields Transferred to VisionMOBILE .... 19 Fire Toning Zetron .............................. 196 GTE Fire Printer Interface .................. 192 Interfaces .............................................. 99 Interfaces, Overview ............................. 99 JAIL, FBR Interfaces .......................... 100 NCIC Interface .................................... 101 Paging Interface ................................. 170 RMS CadReports Folder ...................... 50 RMS Third-Party Interface .................. 101 RMS, Fire Interfaces .......................... 100 Searching in RMS ................................ 61 Transfer to Incident Options ................. 58 Using with Fire ...................................... 75 Using with RMS .................................... 37 Using with VisionMOBILE .................... 14

VisionCAD Tear and Go Interface ..... 190 CAD, Mobile

Communications .................................. 12 CadReports Folder.................................... 55 Call

Transfer to RMS Setting ...................... 47 Call Browse Window

Create OCA ................................... 52, 53 Call Handler Commands ................. 221, 244 Case Entry .............................................. 213 Case Questions ...................................... 240 Chat .......................................................... 21 Civil Papers

Search in RMS ..................................... 65 Clear Call

RMS OCA Number .............................. 50 Clear Message Button .............................. 24 Command Lines .............................. 221, 244 Complaint Updates ......................... 222, 245 Completed Case ..................................... 218 Configuration

Mobile Interfaces ................................. 12 Printrak .............................................. 187 RMS Transfer Call Data ...................... 47 Using RMS ........................................... 45

Configure MEDS CAD Interface .................................... 253 Call Buttons ....................................... 254 Continue Case ................................... 255 General Questions Narrative ............. 256 Vital Point Narrative ........................... 257

Configure Paging .................................... 171 PageGate ........................................... 173

copyright ..................................................... iii Create OCA ........................................ 52, 53 Criminal History

Search in RMS ..................................... 70 CryWolf Interface .................................... 126

Configuring ........................................ 131 Errors and Troubleshooting ............... 142 Filtering the Monitor ........................... 142 Installing ............................................. 127 Monitoring .......................................... 139 Using .................................................. 136


Index

Page 306

VisionCAD Fields................................ 137 D Flag ...................................................... 215 Data Bits .................................................. 198 Data Store ................................................ 100 Deccan LiveMUM Interface ..................... 158

Configuring ......................................... 163 Exchange Details ............................... 167 Filtering the Monitor ............................ 169 Installing ............................................. 158 Monitoring ........................................... 167 Using .................................................. 166

Dispatch ................................................... 215 EFD Interface ................................... 209, 239 EMD Interface .................................. 209, 239 EMD, EPD, EFD ...................................... 184 Emergency Messages ............................... 32 EPD Interface .................................. 209, 239 Export ...................................................... 101 False Alarm Interface .............................. 126 FBR

Interface .............................................. 100 Fields

Transferred ........................................... 19 Transferred from CAD .......................... 59

File Export ................................................ 103 ASCII .................................................. 105 XML .................................................... 107

Fire ............................................................ 37 Access from CAD ................................. 76 Configuring CAD for Fire Interface . 77, 78 Fields Transferred from CAD ............... 80 Interface .............................................. 100

FIRE NFIRS ................................................... 80

FIRE 5.x ..................................................... 81 Fire Plan Query Automatic Searches ... 91 Fire Plan Query Configure .................... 86 Fire Plan Query Connection Failure ..... 93 Fire Plan Query Install .......................... 82 Fire Plan Query Manual Searches ....... 86 Fire Plan Query Using .......................... 86 OCA Export Configure .......................... 93 OCA Export Process ............................ 94

Fire Closest Hydrants ................................ 80 Fire Dispatch .............................................. 76 Fire Plans ................................................... 78

From FIREHOUSE ............................. 121 Fire Toning

Zetron Interface .................................. 196 Fire, with CAD

Overview ............................................... 75 FIREHOUSE Connection Failure ............ 123 FIREHOUSE Query Interface .................. 114

Configuring ........................................ 114 Using .................................................. 117

Flags * .................................................... 214 A .................................................... 218 C .................................................... 218 D .................................................... 215 K .................................................... 213 M .................................................... 213 P .................................................... 218 R .................................................... 215

Glossary .................................................. 297 GTE Fire Printer

Interface ............................................. 192 Guide Card Editor ................................... 245 HigherGround Logging Recorder Interface

.......................................................... 144 Configuring ........................................ 149 Filtering the Monitor ........................... 157 Installing ............................................. 144 Message Workflow ............................ 153 Monitoring .......................................... 154 Using .................................................. 153

Horizontal Dispatch APCO MEDS ..................................... 241 ProQA ................................................ 215

Interface, Fire Overview .............................................. 75

Interface, RMS Overview .............................................. 37

Interfaces to CAD...................................... 99 JAIL

Interface ............................................. 100 K Flag ...................................................... 213 Key Questions ......................................... 213 M Flag ..................................................... 213 Mapping .................................................... 33

Add Call from Map ............................... 35 Interface ............................................. 101 Plot a Call ............................................ 34 Plot a Wireless Call.............................. 35

Maps, Using .............................................. 33 MCT Interface ........................................... 11 MEDS ...................................................... 239

Call Handler Commands ................... 244 Case Questions ................................. 240 Complaint Updates ............................ 245 Horizontal Dispatch ........................... 241 Interface Messages ........................... 251 Interface Settings ............................... 252 Narrative Example ............................. 250 Split Calls ........................................... 248 Using .................................................. 242


Index

Page 307

Message Center ........................................ 22 Button

Clear Message ................................ 24 Reply ............................................... 25

Command Line ..................................... 25 Department ........................................... 24 Groups .................................................. 24 In Bound ............................................... 24 Jurisdiction ............................................ 24 Members ............................................... 24 Messages ....................................... 22, 25 Notes .............................................. 23, 25 Update Configuration ........................... 24 Update User List ................................... 24 Users .................................................... 24

Mobile ........................................................ 11 Communications ................................... 12 Configuration in CAD ............................ 12 Interfaces, Configuration ...................... 12 User Rights for Queries ...................... 261

Mobile Data Terminal Interface ................. 11 Mobile Interfaces

Configuring CAD for Use With .............. 12 Using VisionMOBILE with CAD ............ 14

Multiple Cases ......................................... 224 Multiple Disciplines .................................. 225 NCIC

California LA County ...................................... 274

Generic and State-Specific Queries ... 261 Generic Query Screens ...................... 261 Interface to CAD ................................. 101 Minnesota ........................................... 279 North Carolina .................................... 280 Overview ............................................. 259 Queries ............................................... 259 Query Article ....................................... 266 Query Free-Form Text ........................ 269 Query Gun .......................................... 268 Query Image ....................................... 270 Query Person ..................................... 263 Query Results ..................................... 260 Query Returns .................................... 271 Query Vehicle ..................................... 264 Virginia ................................................ 288 VisionMOBILE Window ...................... 259

NCIC Returns Save to Call .......................................... 29

New Call OCA ................................................ 52, 53

NFIRS ........................................................ 80 OCA Failover ............................................. 49 OCA Number

(RMS) Clear Call.................................. 50 Create ............................................ 52, 53 Creating for RMS ........................... 52, 53

Overview ..................................................... 9 P Flag ...................................................... 218 Page Button ............................................ 184 PageGate ................................................ 170 Pager

Sending Call Data to .......................... 184 Paging

Configuring PageGate ....................... 173 Configuring Paging Interface ............. 171 Interface ............................................. 170

Parity ....................................................... 198 Pending Case ......................................... 218 Person

Search in RMS ..................................... 63 Port ......................................................... 198 Printrak

Audit Record ...................................... 185 Configuration ............................. 187, 188 Configuration ..................................... 187 Event Record ..................................... 185 File Locations ..................................... 186 Interface Installation .......................... 187 Requirements .................................... 185

Printrak CAD ........................................... 185 ProQA ............................................. 209, 212

Aborted Case ..................................... 218 Call Handler Commands ................... 221 Case Entry ......................................... 213 Complaint Updates ............................ 222 Completed Case ................................ 218 Fire .................................................... 219 Interface Settings ............................... 233 Key Questions ................................... 213 Multiple Cases ................................... 224 Multiple Disciplines ............................ 225 Narrative Examples ........................... 231 Pending Case .................................... 218 Police ................................................. 219 Split Calls ........................................... 228 Urgent Message ................................ 218

Queries NCIC .................................................. 259

Query ........................................................ 26 Article ................................................. 266 Free-Form .......................................... 269 Gun .................................................... 268 Image ................................................. 270 Person ............................................... 263 Results ................................................. 29 Save Returns to Call ............................ 29


Index

Page 308

Vehicle ................................................ 264 Viewing Returns ................................. 271

Query Returns Save to Call .......................................... 29

R Flag ...................................................... 215 RAIN Interface ......................................... 101 Reconfigure ............................................. 215 Reply Button .............................................. 25 RMS ........................................................... 37

CadReports Folder ......................... 50, 55 Creating an OCA Number .............. 52, 53 Data ...................................................... 55 Interface .............................................. 100 Setting Up for CAD ............................... 46 Third-Party Interface ........................... 101

RMS Auto-Create Incident ......................... 48 RMS, OCA Number

Clear Call .............................................. 50 RMS, Search

Accessing ............................................. 62 Criminal History .................................... 70 Import ................................................... 75 Overview ............................................... 61 Person .................................................. 63 Vehicle .................................................. 72 Warrants and Civil Papers .................... 65

RMS, Serve Warrant ................................. 68 RMS, Serve Warrant in RMS ..................... 68 RMS, Transfer Call Setting ........................ 47 RMS, with CAD

Configuring CAD................................... 45 Configuring CAD Departments ............. 46 Configuring CAD Rights ....................... 46 Overview ............................................... 37 Setting Up ............................................. 38

RMS/Fire Interface OCA Failover ........................................ 49

Secondary Case ...................................... 226 Split Calls ......................................... 228, 248 Status ......................................................... 30 Stop Bits .................................................. 198 Subject

Import from RMS ................................. 75 Third-Party Export ................................... 101 Transfer to Incident Options ..................... 58 Transfer to Incident, Configuration ........... 47 Transferred Fields from CAD .................... 59 Units

Assigned Functions – Pager .............. 184 Urgent Message ...................................... 218 Vehicle

Import from RMS ................................. 75 Search in RMS ..................................... 72

VisionCAD Tear and Go Interface ............................................. 190

VisionFIRE ................................................ 80 VisionMOBILE

Dispatching a Call ................................ 17 Fields Transferred to CAD ................... 19 Using with CAD.................................... 14

Warrant, Serve in RMS ............................. 68 Warrants

Search in RMS ..................................... 65 XML Enhancements................................ 104 XML Exporting ........................................ 107

Call element ....................................... 108 Fields ................................................. 108 Location element ............................... 113 Person element.................................. 112 Unit element ....................................... 111 Vehicle element ................................. 113

Zetron Baud .................................................. 198 Data Bits ............................................ 198 Parity .................................................. 198 Port .................................................... 198 Stop Bits ............................................ 198

Zetron Model 25 ...................................... 196 Interface Window ............................... 200 Set Up ................................................ 197

Zetron Model 26 ...................................... 200 Interface Window ............................... 204 Messages and Troubleshooting ........ 205 Set Up ................................................ 201

visioncad interfaces guide

Documents