My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
TIBURON (FORMERLY COMPUDYNE - PUBLIC SAFETY - SOFTWARE LICENSE) 2006
Clerk
>
Contracts / Agreements
>
T
>
TIBURON (FORMERLY COMPUDYNE - PUBLIC SAFETY - SOFTWARE LICENSE) 2006
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/9/2014 12:54:09 PM
Creation date
4/13/2006 10:17:17 AM
Metadata
Fields
Template:
Contracts
Company Name
Compudyne Public Safety & Justice, Inc.
Contract #
A-2005-251
Agency
Fire
Council Approval Date
10/17/2005
Insurance Exp Date
4/1/2006
Notes
Amends A-2000-162
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
150
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
24SEVEN Version 2.6 CAD Services — Overview <br />CompuDyne Proprietary <br />We must get one of these values if you do not send a value. The user can always set the Address or <br />40 Location Type in the 24SEVEN RMS application to one of these values (see Figure 2 below). <br />- Streetaddress J <br />- Intersection Street Type Suffix Apt or Suite <br />-In front of Dundee AVE- Avenue r� <br />Rear of <br />- Atliacent to State Zip Code rLatitude Longitude <br />- Directions WA 999o2 I — I <br />- National <br />OK Cancel Oeocode <br />Figure 2 — Acceptable Values in Message Incident <br />2.3.5 AGENCY ID <br />An Agency ID element is not required, but if not sent, the Queue Processor sends the message to the <br />default database. For single database customers, this is not an issue. Sending different agency ID's allows <br />the customer to define different RMS databases that receive the CAD messages. Setup of the Agency ID <br />to the database is in the CAD Services Administrator; the match of defined Agency ID to CAD Agency <br />ID must be exact. <br />• 2.3.6 APPARATUS ID <br />• <br />Apparatus ID element is required with the message apparatus messages. The NFIRS ID is restricted to a <br />maximum of five characters, but the 24SEVEN CAD interface can translate the apparatus ID from CAD <br />to RMS. If RMS receives an apparatus ID that is listed in its RMS database or does not have a translation <br />for which it is configured, then it will keep the message but it will not insert it into an incident record; <br />rather, it will store the message in the 24SEVEN message history with error code of three, for invalid <br />apparatus ID. <br />2.3.7 APPARATUS TIMES - CLEARDATETIME / CANCELLED <br />DATETIME <br />The times for an apparatus record are simple to understand. The important scenario to take into account <br />is that of an EMS unit. EMS units will have a departscenedatetime when they leave the scene to go to the <br />facility or hospital. The cleardatetime for an EMS unit is the type the unit leaves the hospital and the <br />cleardatetime for a fire unit is the time the fire unit leaves the scene. This is to comply with the NFIRS 5 <br />standard, and definition of clear date time. <br />The other scenario to be aware of with apparatus records is when an apparatus is cancelled in route; you <br />will need to send the time it was cancelled, in the cancelleddatetime field. The 24SEVEN interface will <br />capture that time, fill in the proper actions taken, and update the correct times to comply with NFIRS 5. <br />CompuDyne Proprietary <br />CompuDyne December 28, 2005 Page 5 <br />Orid <br />OK Cancel Oeocode <br />Figure 2 — Acceptable Values in Message Incident <br />2.3.5 AGENCY ID <br />An Agency ID element is not required, but if not sent, the Queue Processor sends the message to the <br />default database. For single database customers, this is not an issue. Sending different agency ID's allows <br />the customer to define different RMS databases that receive the CAD messages. Setup of the Agency ID <br />to the database is in the CAD Services Administrator; the match of defined Agency ID to CAD Agency <br />ID must be exact. <br />• 2.3.6 APPARATUS ID <br />• <br />Apparatus ID element is required with the message apparatus messages. The NFIRS ID is restricted to a <br />maximum of five characters, but the 24SEVEN CAD interface can translate the apparatus ID from CAD <br />to RMS. If RMS receives an apparatus ID that is listed in its RMS database or does not have a translation <br />for which it is configured, then it will keep the message but it will not insert it into an incident record; <br />rather, it will store the message in the 24SEVEN message history with error code of three, for invalid <br />apparatus ID. <br />2.3.7 APPARATUS TIMES - CLEARDATETIME / CANCELLED <br />DATETIME <br />The times for an apparatus record are simple to understand. The important scenario to take into account <br />is that of an EMS unit. EMS units will have a departscenedatetime when they leave the scene to go to the <br />facility or hospital. The cleardatetime for an EMS unit is the type the unit leaves the hospital and the <br />cleardatetime for a fire unit is the time the fire unit leaves the scene. This is to comply with the NFIRS 5 <br />standard, and definition of clear date time. <br />The other scenario to be aware of with apparatus records is when an apparatus is cancelled in route; you <br />will need to send the time it was cancelled, in the cancelleddatetime field. The 24SEVEN interface will <br />capture that time, fill in the proper actions taken, and update the correct times to comply with NFIRS 5. <br />CompuDyne Proprietary <br />CompuDyne December 28, 2005 Page 5 <br />
The URL can be used to link to this page
Your browser does not support the video tag.