Exception Event Handling

IoT FM can notify OTM when there is a an exception event, such as deterioration in the cargo condition or violation of the rule predicates set up in IoT FM; these include situations such as temperatures inside the container falling out of set thresholds, violating a geo-fence, truck speeds exceeding acceptable limits, etc. These exception events are sent to OTM as tracking events.

To support exception event handling in OTM, clients should create custom status codes which IoT FM will use when sending the tracking events. These custom status codes should be created in the PUBLIC domain in OTM.

You should also create custom reference number qualifiers in OTM that match exception attributes or rule predicates such as sensor attributes or metric name in IoT FM.

When exception events flow in, clients can set up agents in OTM to copy over relevant event details to the appropriate OTM objects such as shipment, equipment, or driver. Depending on the type of the exception event such as cargo temperature conditions or vehicle breakdown, agents can set different indicators that are easily visualized on a workbench. For higher severity exceptions, agents can send critical alert notifications for intervention services or drive additional workflows such as re-planning with another vehicle.

Example agent setup for exception event handling is listed in the Seeded Data chapter.