iSOMS Integration

AngelTrack has integrated with the iSOMS CAD system to automatically receive trip data.

If you use iSOMS as your CAD, it can push trip data right into AngelTrack.

Configuration

  1. This integration makes use of AngelTrack's CAD NEMSIS API. As such, it requires you to activate an add-on license for the feature. To learn more about doing that, please visit the Feature Buffet Guide.
  2. Once that's done, you must issue an API key for use by iSOMS. To learn how to do that, look at the API Key Guide. The API key you issue must have "CAD Nemsis" privileges.
  3. Input that key and your AngelTrack server's URL into iSOMS.

At that point iSOMS can immediately begin pushing calls.

If you also want iSOMS to also assign your vehicles to pushed calls, which is sometimes called "toneout", follow the additional instructions below.

Toneout / Assign Vehicles from iSOMS

AngelTrack allows CAD integrations to auto-assign vehicles and crews to pushed calls. You can do this even while your own dispatchers are booking and assigning calls in-house. If you do not have your own dispatch office, and all dispatching is done in iSOMS, then be sure to put AngelTrack into Unattended Mode.

In order for iSOMS to assign a call to one of your vehicles, that vehicle record must already exist in your AngelTrack server with the correct callsign. It is easy to create these records, but take care that the callsigns exactly match the ones configured for your fleet in iSOMS.

Under some circumstances, iSOMS might be configured to auto-create these vehicle records for you; please consult your iSOMS documentation for details.

The same is true for your crew members' employee records. For iSOMS to automatically assign a vehicle and crew to a toned-out call, the matching employee records must already exist in your AngelTrack server. AngelTrack matches up the data using patch numbers, therefore you crew members' employee records must have their patch numbers properly recorded in their certificate lists, or failing that, must have their patch numbers input into their "Provider-issued ID number" datafields in their employee records.

As with vehicles, your iSOMS application must be configured to auto-create the necessary employee records in your AngelTrack server; consult the iSOMS documentation to see how.

Trip Logs and Reporting

You can review all trips pushed via iSOMS by visiting the API Trip Log page, which is accessible from the CAD API Configuration page under Settings.

If you create a tag in AngelTrack named "External API", then AngelTrack will automatically apply that tag to any trip pushed in by iSOMS. This allows you to do filtering later for iSOMS trips. You can also configure an automatic service charge for the tag, allowing you to levy a charge for every pushed trip.