Skip to main content

Policy recipes

Every setting in the wizard is explained in Create an alert policy. This page does something different: it gives whole, working rules, with every box filled in, so you can copy one and change the names.

Each recipe assumes the area it needs has already been drawn on the Geozones screen.

How to read a recipe​

The settings appear in the order the wizard asks for them:

WhereSetting
Step 1, BasicsPolicy name, Severity, Fire, Active window
Step 2, Conditionsthe condition cards, Match, and the Scope geozone
Step 3, Applies toAll vehicles, By provider or Specific vehicles

Active window is Always armed in every recipe below, because the Scheduled setting is stored but never applied — see the caution in Create an alert policy. To make a rule stop watching, switch it off on the policy list.

The one thing to get right: Direction and Fire​

Geofence conditions have no "entry" or "exit" option. Entry and exit come from combining Direction on the condition with Fire on the Basics step. Use the two combinations in the first two rows and nothing else.

What you wantDirectionFireLabel on the alert
Alert when a vehicle enters the areaInside the zoneWhen it startsGeozone entry
Alert when a vehicle leaves the areaInside the zoneWhen it endsGeozone exit
Alert on bothInside the zoneStart and endGeozone entry on the way in, Geozone exit on the way out
Do not build "leaving" out of "Outside the zone"

Outside the zone + When it starts also raises an alert when a vehicle leaves — but IFMS labels the alert by which edge fired, not by what you meant, so it arrives in the queue labelled Geozone entry. Operators then read the exact opposite of what happened. Always express both entry and exit with Inside the zone, and change Fire instead.

Outside the zone has one honest use: a standing rule that a vehicle should never be outside an area at all. Expect it to alert on nearly the whole fleet the moment you switch it on, because almost every vehicle is already outside.

Recipe 1 — A vehicle reaches a border crossing​

The command centre wants to know the moment a truck arrives at the Galafi border post, so somebody can watch the crossing.

WhereSettingValue
BasicsPolicy nameGalafi border crossing entry
BasicsSeverityHigh
BasicsFireWhen it starts
BasicsActive windowAlways armed
ConditionsCondition 1Geofence · Direction: Inside the zone
ConditionsScope → GeozoneGalafi border crossing
Applies toAll vehicles

What you get. An alert reading "Galafi border crossing entry (Start)", labelled Geozone entry, badged Critical (because High and Critical share one badge), with a 15-minute response window. The LOCATION column shows Galafi border crossing.

Watch out for. Nothing tells you when the truck leaves again. To have both, set Fire to Start and end — and note that a vehicle parked at the post across a shift change raises one entry alert, not a reminder every few minutes.

Recipe 2 — Speeding inside a dry port​

Vehicles inside the Semera dry port must keep below 40 km/h.

WhereSettingValue
BasicsPolicy nameSpeeding near Semera dry port
BasicsSeverityCritical
BasicsFireWhen it starts
BasicsActive windowAlways armed
ConditionsCondition 1Geofence · Direction: Inside the zone
ConditionsCondition 2Speeding · Speed limit: Fixed limit · Limit (km/h): 40
ConditionsMatchAll conditions (AND)
ConditionsScope → GeozoneSemera dry port
Applies toAll vehicles

What you get. An alert only when both things are true at once: the vehicle is inside the zone and doing more than 40 km/h. Critical gives it a 5-minute response window, so it will breach quickly if the shift is busy.

Watch out for.

  • Put the Geofence condition first. The alert takes its Type from the first condition, so this policy's alerts are filed under Geofence on the Events screen. If you would rather find them under Speeding, put the speed condition first instead. Either way they behave identically; only the filing changes.
  • All conditions (AND) is what makes this a zone rule. With Any condition (OR) it would alert on every vehicle in the zone and every speeding vehicle anywhere in the country.
  • Speed is worked out by IFMS from successive positions, not sent by the tracker, so a vehicle that reports rarely may cross the zone without ever showing a speed above the limit.

Recipe 3 — A vehicle sitting too long in a dry port​

A truck idling for four hours inside the Modjo dry port is a bottleneck somebody should chase.

WhereSettingValue
BasicsPolicy nameLong stay at Modjo dry port
BasicsSeverityMedium
BasicsFireWhen it starts
BasicsActive windowAlways armed
ConditionsCondition 1Geofence · Direction: Inside the zone
ConditionsCondition 2Idle / distance · Idle minutes: 240
ConditionsMatchAll conditions (AND)
ConditionsScope → GeozoneModjo dry port
Applies toAll vehicles

What you get. One alert per truck once it has been idling inside the port for four hours, labelled Geozone entry (the first condition is the geofence), badged Warning, with a 60-minute response window.

Watch out for.

  • Idling here means the engine reported on or unknown, speed at or below 3 km/h, and recent reports. A truck whose driver switched the engine off is Parked, not idling, and this rule will not notice it.
  • The count is only re-checked when a new position arrives. A tracker that stops reporting will never trip the rule, however long the truck stands there.
  • Closing the alert lets the same truck raise a new one if it goes on idling, which is usually what you want for a bottleneck report.

Recipe 4 — A vehicle leaves a controlled area​

A yard manager wants to know when a truck leaves the Addis yard.

WhereSettingValue
BasicsPolicy nameAddis yard departure
BasicsSeverityMedium
BasicsFireWhen it ends
BasicsActive windowAlways armed
ConditionsCondition 1Geofence · Direction: Inside the zone
ConditionsScope → Geozonethe yard's geozone
Applies toBy provider, or Specific vehicles for a named list

What you get. An alert reading "Addis yard departure (End)", labelled Geozone exit.

Watch out for. Read Fire twice. When it ends is the setting that makes this a departure rule; with When it starts the same policy becomes an arrival rule and the name on every alert will be wrong.

Recipe 5 — Engine left running overnight, on one provider's fleet​

One operator keeps leaving engines idling at rest stops.

WhereSettingValue
BasicsPolicy nameEngine idling over 90 minutes
BasicsSeverityLow
BasicsFireWhen it starts
BasicsActive windowAlways armed
ConditionsCondition 1Idle / distance · Idle minutes: 90
Applies toBy provider → the operator

What you get. An alert per vehicle after 90 minutes of idling anywhere in the country. There is no Scope box on this policy, because no condition needs an area — so SCOPE and the LOCATION column read "—", and the alert is drawn at the fallback point over Addis Ababa on the Events map.

Watch out for. Low severity means the alert never breaches a response window and is never escalated. That is deliberate for a housekeeping rule: it should sit in the queue to be counted, not chase anybody. It also means no routing rule with a minimum severity above Low will email or text it.

Recipe 6 — A short-lived rule for one investigation​

A provider disputes that its vehicles speed on the corridor. You want two weeks of evidence about four plates.

WhereSettingValue
BasicsPolicy nameInvestigation — corridor speeding, <provider>
BasicsSeverityInfo
BasicsFireWhen it starts
BasicsActive windowAlways armed
ConditionsCondition 1Speeding · Speed limit: Fixed limit · Limit (km/h): 80
Applies toSpecific vehicles → tick the four plates

What you get. A quiet record: Info alerts never breach, are never escalated, and are below the minimum severity of any sensible routing rule, so nobody is emailed. Export the evidence with Export CSV on Events — filter by Vehicle, set Rows per page to 100 first, and see Export the alert list.

Watch out for. When the investigation is over, switch the policy off rather than deleting it, so the alerts still name a rule somebody can look up. Remember that the alerts it raised stay in the queue and still have to be closed either way.

Things to avoid​

Do notWhy
Use Outside the zone to mean "left the area"The alerts arrive labelled Geozone entry, the opposite of what happened.
Use Use zone's limit on a zone with no speed limitThe condition has nothing to compare with and never matches. Set Speed limit (km/h) on the zone first.
Rely on ScheduledThe schedule is stored but never applied; the policy fires at all hours.
Set every policy to CriticalEverything then carries a five-minute window, everything breaches, everything escalates and the escalation notifications stop meaning anything.
Switch off a geozone a policy watchesThe policy stops raising anything for that area until the zone is switched back on.
Create a fleet-wide policy without watching the queueEvery vehicle already matching alerts at once.