Trip overdue
Know when a trip is running late while it is still running. A trip overdue rule fires when a trip has been in progress longer than you expected, and the asset has not arrived.
Use it to put a delivery service level in the system that watches it, to spot a vehicle stuck in traffic before the customer calls, or to escalate a shipment that has taken far too long.
Only trips in progress
This rule looks at trips that have not finished. That is what makes it different from a trip completed rule with a minimum duration: that one tells you afterwards that a trip took four hours, and this one tells you at the four-hour mark that it is still going.
Reporting both from one rule would say the same thing twice under two names, so the two are kept separate.
How it works
Blecon reads an asset's history as stops and the trips between them. A trip is in progress from the moment the asset leaves its stop until it settles somewhere new. This rule fires once the trip has been running for longer than the expected trip time you set.
Blecon comes back to the asset at exactly that moment. It does not wait for the asset to do something first, so a vehicle sitting still in a queue is still reported on time.
Each overdue trip produces exactly one notification per rule, however long the trip goes on afterwards.
The message names the asset and how long it has been out:
Van 12 has been travelling from Cambridge Depot for over 4 hours and has not arrived
The notification carries the full trip detail, plus:
| Field | Meaning |
|---|---|
max_duration_seconds |
The expected trip time that was passed |
elapsed_seconds |
How long the trip had actually been running |
last_position_at |
The last position recorded on the trip, in UTC |
Parameters
| Parameter | Required | Description |
|---|---|---|
max_duration_seconds |
Yes | Alert once the trip has run this long without arriving |
origin_zone_id |
No | Only trips that started in this zone |
min_distance_meters |
No | Only trips at least this far |
device_type |
No | Only assets of this type |
device_tags |
No | Only assets carrying at least one of these keywords |
exclude_device_tags |
No | Never assets carrying any of these keywords |
A destination filter and a minimum duration are both rejected: a trip in progress has neither.
Like every rule, you can set its severity, and limit it to chosen assets with Filter by Asset Keywords in the rule form.
See the rule types reference for the full specification.
Example: a delivery service level
A distributor promises every drop within three hours of leaving the depot.
- Create a trip overdue rule with expected trip time set to 3 hours.
- Set departing from to the depot zone, so only outbound runs are watched.
- Limit it to the "van" asset type.
- Set the severity to medium and add an email notification to the transport desk.
Notes
- A trip that goes silent becomes an abandoned trip rather than an overdue one. Once abandoned, the trip is finished, and this rule has nothing more to say about it.
- The clock starts when the trip started, not when the rule was created. Enabling a rule can report a trip that is already running late.
- Changing the trip distance or stop time changes what counts as a trip, so past trips are re-read under the new settings.