Resource Settings

Timeout

How long a resource can go without a status update and a timeout event is triggered. This is useful for ensuring that resources are not left in a status that is no longer accurate.

This number is measured in seconds. By default, it is 300 to represent 5 minutes without a status update.

UI Heartbeat

This enables sending a heartbeat (status update) to the Helix server while the Helix interface is open. This will ensure the user does not time-out while having Helix open. Integrations and third parties can also send heartbeat events, which is covered in the Developers section of this documentation.

Book of on Timeout

This will automatically book a resource off (remove them as an available unit/resource) when they time out.

Note that if the resource is currently assigned to an incident, they will not be booked off until cleared from said incident.

Alert Dispatcher on Timeout

This will send an alert to the dispatcher when a resource times out. This can be combined with the Book off on Timeout option to ensure that the dispatcher is aware of the timeout.

Note that this will trigger no matter the reason for the timeout (e.g. the UI has been closed, or the resource GPS has been lost).

Allow self-booking

This allows resources (with Helix access) to book themselves on and off assets rather than a dispatcher doing it for them. A dispatcher can still override this action.