Wrong destination
Know when an asset ends up somewhere it should not. A wrong destination rule lists the places a trip is meant to end, and reports every trip that ends anywhere else.
Use it to catch a wrong drop, a vehicle taken off its route, or equipment that left the sites you own.
Listing what is normal
A trip completed rule can filter on one destination zone, which tells you when a trip ends in a place you named. This rule is the inverse: you name the places that are fine, and it tells you about everything else. That is the shorter list for most fleets, and it is the one that catches what you did not think of.
How it works
Blecon reads an asset's history as stops and the trips between them. When a trip finishes, its destination is resolved to a zone if the asset stopped inside one. If that zone is not in your list, the rule fires.
The rule waits for the destination to settle. A vehicle pausing for two minutes is not an arrival, so nothing is reported until the asset has been still for the workspace's stop time.
Each arrival somewhere unlisted produces exactly one notification per rule.
The message names the asset and where it ended up:
Van 12 finished a trip at 52.4501, -1.8002, which is not an expected destination
The notification carries the full trip detail, plus:
| Field | Meaning |
|---|---|
allowed_zone_ids |
The zones the rule accepts |
destination_zone_id |
The zone the trip actually ended in, or empty when it ended outside every zone |
Arrivals outside every zone
An asset can finish a trip in no zone at all: parked in a field, at a roadside, at an address nobody has drawn. By default those are reported, because that is usually the case the rule exists for.
Turn Also alert when a trip ends outside every zone off when only your own sites are drawn as zones. Otherwise every trip that ends on a public road alerts.
Parameters
| Parameter | Required | Description |
|---|---|---|
allowed_zone_ids |
Yes | Zones where the trip is expected to end, up to 10 |
alert_on_unknown |
No | Also alert when the trip ends outside every zone. On by default. |
origin_zone_id |
No | Only trips that started in this zone |
min_distance_meters |
No | Only trips at least this far |
min_duration_seconds |
No | Only trips that took at least this long |
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 |
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: keeping plant on its own sites
A hire company wants to know when a tagged machine finishes a move at a site it does not own.
- Draw a zone for each depot and each active hire site.
- Create a wrong destination rule and add all of those zones to expected destinations.
- Leave also alert when a trip ends outside every zone on, so an arrival at an undrawn address is reported too.
- Set the severity to high and add a webhook notification to the asset management system.
Notes
- The zone list is capped at 10. For a larger set of sites, use a geofence containment rule with zone keywords instead.
- A trip that goes silent becomes an abandoned trip and is not reported here: it has no destination to judge.
- Changing the trip distance or stop time changes what counts as a trip, so past trips are re-read under the new settings.