Introduction
A "duplicate alert" is an alert that is sent to us by your dispatch more that than once. Dispatch centers do this for a variety of reasons. Sometimes it is just an accident. At other times, they are trying to advise you of changes that have been made to the original alert - for example, they may be adding additional units to the alarm, or changing the location.
...
What should we do with duplicate alerts?
Discard: Silently throw the duplicate away
Update: Compare the new (duplicate) alarm with the old one
...
and update the notes section of the existing alarm with a descriptive comment. You will
...
receive an additional notification for every update to an existing alert.
Passthru: Every message from your dispatch results in a new alert.
EX: If your dispatch sends us three messages for the same call, you will receive three separate alerts. One for each message.
What criteria determine what is a duplicate?
CAD # Compare the CAD code or number that your dispatch is sending us. Identical CAD numbers mean the two alerts must be related. This works for calls within approximately 30 minutes of each other. The time frame can be changed to any length of time, 24 hours is the default.
Location Any alarm within 10 minutes of a previous alarm, within 0.05 miles, is considered a duplicate. The time frame can be changed to any length of time, 10 minutes is the default.
Loc/Title Any alarm within 10 minutes of a previous alarm, within 0.05 miles, with the same title, is considered a duplicate. The time frame can be changed to any length of time, 10 minutes is the default.
| Info |
|---|
Note: Using CAD numbers to determine connected alerts only works if your dispatch center is sending us CAD codes. Please check some of your old alerts to make sure those codes are coming through before selecting this option. |
...
An agency's JSON options are something that can only be adjusted by an Active911 support technician. The JSON options can be used to accomplish many different things. Some of the more common applications include:
Having a specific field update with new information, rather than placing that new information the notes.
Discarding calls based on a certain value within a specific field (description, unit, etc.)
Completely replacing the original information in the field when an update to the information is received from dispatch (address, description, etc.)
JSON Fields
Some of the specific fields we can use within the JSON options include, but are not limited to:
Description
Priority
Cross Street
Units
ID
Map Code
Details
Time
Date
Address
JSON Update Options
When updating within those fields we can apply the following options:
Append — The new information is added to the end of the field
Prepend — The new information is added to the start of the field
Append with newline — adds a newline, then the new information to the end
Append with space — adds a space, then adds the new information to the end
Replace — completely replaces the old information with the new information
Append with space filter — sorts the items, looks for duplicates, and only adds new information
Mention (Default) — Makes a note that something changed in the details/notes field