Users can now take advantage of Halligan's advanced Apparatus Management Platform in tandem with the Emergency Reporting Record Management System with the Halligan Emergency Reporting Integration. This article is intended to help users understand how the two systems work together.
If Emergency Reporting is the brain of the Firehouse where all data is stored, then Halligan is the arm and hand enabling tasks to get completed effectively. This analogy drives the direction of how data flows between the two systems. Departments using the integration should anticipate creating and managing their equipment and apparatus in Emergency Reporting. Inside Halligan, departments should plan on performing checks and working maintenance tickets.
Data Synced From Emergency Reporting into Halligan
Halligan will pull in the following emergency reporting data:
- Apparatus - The following fields are pulled in: Apparatus ID, NFIRS Apparatus Type
- Equipment - Emergency reporting stores their data in a hierarchical category structure while Halligan has the concept of an Equipment Pool. The sync will create Equipment Pools in Haligan named by the Emergency Reporting Category Hierarchy. i.e. SCBA -> Bottles -> BOTTLE-1 inside of Emergency Reporting will become an Equipment Pool named SCBA - Bottles with an Equipment Item with Identifier BOTTLE-1 inside of it.
Users must allow Halligan to pull in that data in order to see Halligan writing Maintenance Records back into Emergency Reporting
Data Synced from Halligan into Emergency Reporting
Halligan will write/update Maintenance Records back into Emergency Reporting for the following actions taken inside of Halligan:
- Apparatus Check Completed
- Work Order Ticket Created
- Work Order Ticket Updated
Note on Daily Log: If you have Emergency Reporting configured so that Maintenance's show up on the Daily Log then the Maintenance's Halligan creates will show up in the Daily Log. Currently the user who setup the integration will show up as the user who made the log entry. In a not-so-distant future release the user who actually took the action will be the one that shows up in the Daily Log assuming that user leveraged the Emergency Reporting Single Sign On for Halligan.
Setting up the Integration and Integration Configurations
You first must authenticate Halligan against Emergency Reporting so the two systems can converse. This username and password is not stored anywhere on the Halligan side for security purposes and is just needed once to enable the integration.
After successful authentication you will see a few more configuration boxes come up. You will see a set of fields in a panel called 'Configurations'
Here you can configure the following options:
- Check Report Maintenance Type: The type of Emergency Reporting Maintenance to be created when an Apparatus Check is completed in Halligan
- Maintenance Mileage: If the last check report completed in Halligan has the configured Numeric step in it, the integration will populate the 'Mileage' field in the Emergency Reporting Maintenance.
- Maintenance Engine Hours: If the last check report completed in Halligan has the configured Numeric step in it, the integration will populate the 'Engine Hours' field in the Emergency Reporting Maintenance.
If you are currently using Halligan and already have Apparatus setup, you can map your Emergency Reporting Apparatus to your Halligan Apparatus before running your first sync in the 'Map Existing Apparatus' panel:
Map Ticket Types
Halligan Ticket Types can map into Emergency Reporting Maintenance Types. If you would like some or all of your ticket types to sync to Emergency Reporting on creation and update then you must map your ticket types to an Emergency Reporting Maintenance Type.
Running your first Sync and Sync Reporting
After setting up your integration configurations you can run your first sync on the 'Sync' Tab
As your integration runs and certain sync activities happen between Halligan and Emergency Reporting, the Integration will record logs of these events for you to audit. The team at Halligan is always monitoring for failed Sync events, but please reach out to our support team here if you see any failures or have any questions!