IamResponding provides three primary methods for integrating with your Computer-Aided Dispatch (CAD) system. Our goal is to give your field responders secure, reliable, and real-time access to critical dispatch information.
Integration Methods: A Technical Overview
1. API Integration (Preferred Method)
This is our most robust and secure integration method. It creates a direct, real-time connection between your CAD system and the IamResponding platform, ensuring your responders have the most comprehensive and current information available.
How It Works:
- Direct API Connection (Method A): We establish a secure HTTPS POST connection (using TLS 1.2) directly with your CAD system's API. This is the most efficient way to transfer data.
- CADConnect Software (Method B): If your CAD system can export XML or JSON files, our custom CADConnect software can monitor a specified folder for new incident files. It then securely sends that data to our API. In some cases, it can also query an SQL database to pull incident data.
Key Advantages:
- Live CAD Updates: Responders get critical updates in real-time, including new CAD comments and unit status changes.
- Structured Data: The data is transferred in a clean, organized format (XML/JSON), making it easy for responders to read.
- Enhanced Security: Using HTTPS POST (TLS 1.2) provides significantly better security than traditional email or pager methods.
- No Hardware Needed: This is a purely software-based integration, so there's no need for additional physical equipment.
Examples of Current API Integrations:
- Direct API Connections with: Caliber, CentralSquare Pro Suite, EForce, GeoConex, Hexagon OnCall, Oracle, Pulsiam, Southern Software
- CADConnect Integrations with: CentralSquare Enterprise/IMC/ONESolution, Motorola Spillman Flex (via the Spillman DataExchange API), ShieldWare, Tyler Enterprise/Public Safety Pro, Valor Systems
2. SMTP (Email) Integration
This is a straightforward method that works with any CAD system that can send automated emails.
How It Works: Your CAD system is configured to send an incident dispatch email to a unique IamResponding email address. Our system then parses the email to create an incident.
Key Limitations:
- Initial Dispatch Only: This method only provides data at the time of the initial dispatch. While an "end of incident" report may be sent by the CAD system, it depends on the CAD's capabilities.
- No Live Updates: You will not receive live updates, comments, or status changes from the CAD system.
3. SNPP Integration
This method is an alternative for centers that use Simple Network Paging Protocol for dispatch alerts, which is common for centers that use PageGate.
How It Works: Your CAD system sends a dispatch alert to our SNPP gateway, which then generates an incident in the IamResponding system.
Key Limitations:
- Initial Dispatch Only: Similar to SMTP, this method only provides data at the time of the initial dispatch.
- No Live Updates: This method does not support the transmission of live CAD comments or status changes.
Why Choose IamResponding's API?
The IamResponding CAD Incidents API is the most secure and reliable way to get critical dispatch data to your field responders. By choosing this method, you ensure your first responders have the most accurate and up-to-date information available, enabling faster, safer, and more effective emergency response.
Want to learn more about setting up a CAD integration for your agency? Contact our dispatch team at iar-dispatch@rapidsos.com