Purpose
- To provide overview of the Dispatch Email Link interface.
Description
- A notification is generated upon dispatch and is sent to a First Due email address in txt or html format. In order to ensure we have the necessary information, we require dispatches to be parsed correctly.
- Pros
- Quick and easy to set-up.
- Often a fast delivery method.
- Most CAD software systems have the ability to quickly install.
- Cons
- Limited ability to customize if CAD software has limitations on what can be sent.
- Often unable to send updates, call notes, narratives, and other information. (First Due can process all of these fields if CAD is unable to send)
Data Attributes
- In order to ensure we have the necessary information, we require dispatches to be parsed correctly. Please see the below list of requested fields (not all are required).
- Time Zone for Department (Required)
- Time Zone CAD sends Date and Time in (Required)
- Incident Date (Required)
- Incident ID (Required)
- Apparatus / Unit ID (Required)
- Agency Identifier
- Call Notes / Narrative
- Caution Notes
- Common Place
- Date / Time of Dispatch
- Dispatch Type Code
- Dispatch Type Description
- Dispatch Units Assigned
- Incident Date
- Incident Number
- Initial Street Address
- Secondary Address
- Cross Streets
- City/ County Code
- Latitude / Longitude
Parsing Dispatches
Below is an example of our preferred message format. We always want to make sure to use a delimiter between each field. The semi-colon (;) is our preferred delimiter since there is less chance of it appearing in other places (such as address and notes).
Format:
Call Type;Call Address;Fire District;First Unit Dispatch Date/Time;Units assigned;Incident number;Narrative
Sample Result:
MOTOR VEHICLE ACCIDENT;01;12 MAIN STREET;RICHMOND;PERSON REPORTED MULTIPLE CARS INVOLVED IN ACCIDENT IN FRONT OF SULLIVANS;06/05/2019;E12,E13,R12,BC12;123000000009