Please have your system administrator return reply our support team to activate this feature. We will reach out once it's enabled.
The IamResponding External Integration page is where users can configure their IaR system to integrate with external vendors.
Our "Universal HTTP Post" external integration automatically exports CAD incident data from IamResponding to third-party services (such as Alpine Software).
Take notice:
- HTTP post currently only works for CAD data received via the CAD API. It will not work with CAD data received via SMTP or SNPP.
This is currently the exclusive integration option for all venders, excluding ESO.
The example below uses an ESO integration:
Navigation
User can access the external integrations page by navigating to the administrative functions page.
From the “Settings” sidebar menu option, users will then be able to select “External Integrations”.
Generating an External Integration
To configure IamResponding to integrate with an external vendor, users will need to create a new integration.
By selecting “Add New”, users will generate a new external integration, and will be able to select the type of integration they would like to configure.
Basic Information
This section contains basic fields for any external integration being created.
Integration Type:
Currently “ESO RMS” and “ESO Properties” are the only external integrations supported by IaR.
ESO RMS: IaR will automatically export incident data to ESO RMS.
ESO Properties: IaR will populate ESO property data as pre-plans within IaR.
Description:
Users will be asked to provide a description of the integration (i.e. “Export incident data to ESO RMS”).
Active:
Users may activate or deactivate an integration by utilizing this switch. Integrations
ESO Properties - Integration Type Fields
This section contains fields that are specific to the ESO Properties integration.
Key:
Users will need to input the IamResponding key provided by ESO. This will link the
IamResponding and ESO systems for an agency.
Show Info:
This switch will show/hide the text that has been entered within the “Key” field.
Accessing ESO Properties Key
To utilize the ESO Properties integration within IaR, agencies will first need to have purchased the Properties and Fire Properties API through ESO.
Within ESO, users will need to access the Subscriptions page by navigating to “API Management” within the ESO admin page, and then selecting “Subscriptions”.
If not already visible, agencies will need to request to enable the IamResponding subscription within ESO by contacting APISupport@eso.com.
Once enabled, users will be able to generate keys for IamResponding. Users may utilize either the primary
or secondary key, which they will need to paste into the “Key” field of the ESO Properties integration page
within IaR.
To verify your agency has purchased the ESO Properties & ESO Fire Properties API, users will see “Agency Fire API” listed within the ESO Subscriptions page. If a subscription has not been purchased,
please contact esoam@eso.com to connect with your ESO sales
rep.
ESO RMS - Integration Type Fields
This section contains fields that are specific to the ESO RMS integration.
CAD Registry ID:
Users will need to input a CAD Registry ID provided by ESO. This will link the IamResponding and ESO systems for an agency.
Show Info:
This switch will show/hide the key that has been entered within the “Key” field.
Structure Plain Text Incident Data:
Select whether to automatically organize plain text incident data from CAD and export it to ESO RMS.
Please note the limitations of plain text data structuring – results may not always be fully accurate.
Original plain text CAD data will be displayed within the ESO CAD notes.
Accessing ESO RMS Export CAD Registry ID
To utilize the ESO RMS integration within IaR, agencies will first need to have purchased a CAD integration through ESO.
Agencies will then need to contact the ESO CAD Interface Staff to obtain their “CAD Registry ID”.
To begin the process of obtaining the CAD Registry ID, agencies will need to contact ESO Success, at
success@eso.com, where they will then be directed to the ESO CAD team to obtain their CAD Registry ID.
Once provided by the ESO CAD team, agencies will need to enter their ESO “CAD Registry ID” into the “CAD Registry ID” field within the IaR ESO RMS integration page.
Save Changes
Once all required fields have been completed, users will then need to select “Save Changes” at the top right corner of the page.
Users will then see the newly created integration listed.
Note:
Users may edit or delete an external integration by selecting the three dots at the right side of the integration list.
Access
Agency:
The external integrations page will not be visible to users unless it has been enabled for your agency by IamResponding.
Note:
All agencies transitioning from Rover who currently utilize ESO should already have this functionality enabled within IaR. If you do not see the External Integrations Page, please contact us.
Users:
The external integrations page will not be accessible to users unless they have the permission, “Permitted to edit System Functions”, enabled within their individual member profile.
Note:
User permissions are managed by the agency IaR administrator.