Connecting First Due to CAD
Purpose
- This article reviews the various types of connections that First Due uses when setting up CAD links
Importance of Connecting First Due to CAD
The following are just a few of the many benefits of enabling First Due to receive dispatches from your CAD dispatch center:
- First Due automatically connects each dispatch to a Pre-Plan, pulling up all the assembled information on the address of the incident.
- Allows for notification through the mobile application
- Enables Quick Route navigation or Route Overview to incidents through the app.
- Display Call Notes and other incident details.
Connection Methods
The following methods are options for connecting First Due to your local CAD in order to receive dispatches.
Dispatch Email Link
A notification is generated upon dispatch and is sent to a First Due email address in txt or html format. This option is often quick to set-up and available through most CAD systems.
Click here for more information about setting up a Dispatch Email Link between CAD and First Due.
Pros
- Quick and easy to set-up.
- Fast delivery method.
- Most CAD systems have the ability to quickly set-up.
- Least amount of work for CAD.
- No intrusion or connection to CAD required. Outbound messages only.
Cons
- CAD software will often have limitations of what information can be sent. These CAD limitations will sometimes restrict call notes, updates and more. (Note, First Due has no limitations around this process. When limitations arise, they are on CAD's side.
Live Database View / CAD Mirror
Connection
Live database view into a CAD mirror or a copy of CAD's database (read-only). First Due would access via a VPN or install a Connector. First Due would write the code to extract the dispatch information. CAD would be responsible for making the read-only view or CAD mirror accessible and timely.
In order complete the development of a dispatch connector for First Due we require the following information:
- Provide a list of views that First Due Will be able to access for CAD data
- Confirm the Database Type (MSSQL, PostgreSQL, MySQL etc)
- Provide the schema/configuration for each view and there corresponding columns
- Provide a dump of each of the views data (full dump is preferred but at a minimum 1000 records)
- Confirm the method in which we can detect if a call is closed or open status (is_closed column, date_closed, etc).
Pros
- Enables First Due to access all or most of the information CAD has of the incident.
- As a "Mirror" or "View Only", it does not require us to intrude into CAD neutralizing security concerns.
Cons with
- Requires a little bit of work from CAD to set-up but often less work than the below options.
- Latency. CAD should push the data every 5 - 15 seconds. Longer gaps need to be avoided.
NOTE - Any work required from CAD often requires approval. This approval process sometimes takes time. Please work on introducing First Due to your CAD connect ASAP.
XML to SFTP Connection
Connection
Each incident and call update pushes a JSON, XML, TXT or other standard file format to a SFTP (Secure File Transfer Protocol) site for First Due to access and extract.
Pros
- Enables First Due to access all or most of the information CAD has of the incident.
- Does not require us to intrude into CAD neutralizing security concerns.
- This export format is often used by CAD to push call information to Incident Reporting and RMS systems. Copy's of previous work can be utilized if they are sending call information in a timely enough interval (5 - 15 seconds).
Cons
Requires more work for CAD to set-up.
- Latency. CAD should push the data every 5 - 15 seconds. Longer gaps need to be avoided.
NOTE - Any work required from CAD often requires approval. This approval process sometimes takes time. Please work on introducing First Due to your CAD connect ASAP.
API Connection
Connection
First Due supports CAD IT teams in connecting to First Due with APIs. CAD IT would be responsible for writing code to post to API based on CAD data.
For additional information regarding this format, please visit our First Due REST API Documentation article.
Dispatch API article here.
Pros
- Allows for complete local control of what information from the CAD is shared with First Due.
Cons
- Requires development work for local CAD IT to set-up.
NOTE - Any work required from CAD often requires approval. This approval process sometimes takes time. Please work on introducing First Due to your CAD contact ASAP
Related Articles
Using First Due to Dispatch Incidents
The First Due platform integrated with many different Computer Aided Dispatch (CAD) systems. With the creation of an incident our system matches the address and shows the relevant pre-plan information for that location. There are a numerous ...
First Due Reports (FDR)
Purpose: To illustrate the function and use case of First Due Reports (FDR). Information: First Due Reports live within Ad-hoc Reporting, and are created by the First Due Reporting Team. FDR are organized by module and searchable by module within ...
Dispatch Email Link
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 ...
Live Database View / CAD Mirror
Purpose To understand the Live Database View / CAD Mirror process Related Article Understanding the First Due CADLink Connector Description Live database view into a CAD mirror or a copy of CAD's database (read-only). First Due would access via a VPN ...
Dispatch Incident Types: Creating and Customizing
Purpose To demonstrate how to create and customize a Dispatch Incident Type. Video Directions 1. Navigate to Response Module then Click on Dispatch Incident Types. 2. Click on New Dispatch Incident Type. 3. Fill in the following fields. Department ...