Contact us to learn more


Enabling and Simplifying Mutual Aid

In mutual aid arrangements, jurisdictions want to enter an incident in their respective CAD system and then have the ability to dispatch a unit without having to make a telephone call to the other agency’s dispatch. If a secondary unit is called, they want the system to know if the unit is available. With a plethora of CAD alternatives in the marketplace it is rare that two jurisdictions in a mutual aid arrangement have the same CAD system in place. That is where the robust and efficient technology of EvolutionC2CTM can be of use.


Click to enlarge

EvolutionC2C™ Functions

The C2C Exchange delivers features through a web service API. The web service API provides operations to deliver functionality.

The C2C Exchange operational functions delivered in the API include:

1. Unit Status Update (USU): A synchronous, request-response operation between a CAD system and the C2C Exchange. With this, CADs systems send to and receive from the Exchange Unit Statuses, Unit Locations, and Unit Assigned/Home Stations at regular intervals.

2. Request for Resource with Incident Information (R2I2): When a CAD system must respond to a Call for Service and determines (with the utilization of USU, above) that remote, mutual aid units managed by a neighboring, remote CAD system can/could respond more efficiently, it uses the R2I2 function to request the mutual aid. The C2C Exchange can interface with multiple remote CAD systems simultaneously and aggregate the responses for the original requesting CAD system to complete the R2I2 request-response. Local and remote incident participants are continually updated throughout the incident lifecycle.

The mutual aid provided by the remote CAD system can be provided as:

Mutual Aid: Incident created is in pending state, dispatcher must dispatch.
Automatic Aid: Incident creation and dispatch occurs automatically.

The capability to deliver Mutual Aid or Automatic Aid is a dependency on what the CAD system vendor can offer in terms of their CAD functionality.

3. Request for Resource Update (R2I2U): The R2I2U function is used when an operator determines that units should not be provided to a request CAD system that asked for mutual aid via an R2I2 request. If automatic aid is not configured by the CAD system, the remote CAD operator would have the ability to rescind units requested before ultimately dispatching.

4. Incident Detail (IDTL): The IDTL function has multiple actions which designate the type of IDTL message operation being requested of the C2C Exchange, namely:

 CREATE:   An incident is created in CAD.
 UPDATE:  An incident is updated in CAD.
 CLOSE:  An incident is closed in CAD.
 TRANSFER:  An incident transfer is executed in CAD.

The IDTL function links incidents where mutual aid is provided and allows either agency to update incidents and provide the remote agency with that update. This is facilitated by the C2C Exchange.

5. Notification (NTIF): The NTIF function has multiple flavors which designate the type of NTIF message operation being requested of the C2C Exchange, namely:

UNIT-LOGON: A unit is logged-on (placed in service) in CAD.
UNIT-LOGOFF: A unit is logged-off (taken out of service) in CAD.
UNIT-MOVE: A unit is moved to a new assigned/home station in CAD.
GENERAL: A CAD operator wants to issue a broadcast type message.
OPERATIONAL STATUS MODE: A CAD operator wishes to change the OSM.

These actions and the resulting NTIF message request issued to the C2C Exchange are triggered by various actions or conditions within the CAD system. For example, when a unit is logged-on or placed in service, an NTIF UnitLogon request is issued to the C2C Exchange with the identification of the unit being placed in service. Unit Logoff works synonymously with Unit Logon. When a unit is moved to a new home station or assigned station in a CAD system, an NTIF UnitMove request is issued to the C2C Exchange with the identification of the unit and the new station to which it is assigned. Similarly, when the incident fields are modified or updated or the units encumbered are adjusted, an IDTL UPDATE request is issued to the C2C Exchange. Finally, when an incident is closed, an IDTL CLOSE request is issued.

The C2C Exchange will forward pertinent NTIF requests to all other CAD systems which need to know that unit was placed back in service, or a unit was taken out of service, or moved, etc.
NTIF General notification requests are issued to the C2C Exchange when a CAD system operator wishes to disseminate a message to all other CAD system operators. The CAD systems receive these ‘broadcast’ type requests and propagate the information in a manner that will be viewed/received by the remote CAD operators. The manner in which the information is presented to the CAD system operators upon receipt of a C2C Exchange forwarded NTIF General notification request is up to the CAD system and how they integrate it into their UX/UI.

6. Instant Messaging (IMSG): IMSG is a fire-and-forget, one-way operation between a requesting CAD system and the C2C Exchange. This function allows point-to-point or distributed message distribution to participating CAD systems. IMSG functions similarly to the NTIF General notification, but allows for specific addressing among the C2C Exchange participants.

All of these C2C Exchange functions are bi-directional and perform communication between multiple CAD systems with the exception of the USU function. The full operations set works to deliver desired customer functionality when integrated with the participating CAD systems.

EvolutionC2C™ Deployment Options

EvolutionC2CTM can be deployed in two models; a standalone, hosted model or a solution as a service, subscription model.