Skip to main content

Watch a new area

Who this is for: corridor and fleet staff, usually with an administrator for the last step.

What you will achieve: IFMS will raise an alert when vehicles do something you care about at a place you care about, and the right people will hear about it.

Before you start: you need the right to create areas and to create policies. For the routing step you need an administrator. See What each role can do.

Doing this in the order below saves the most backtracking, because a policy cannot point at an area that does not exist yet.

1. Decide what you are actually watching​

Write the rule out in one sentence before touching the portal. "Tell the duty supervisor when a vehicle enters the Galafi border crossing" is a rule you can build. "Watch Galafi" is not.

Your sentence needs four things:

  • A place - which becomes the area you draw in step 2.
  • A thing that happens there - entering, leaving, speeding, staying too long.
  • How serious it is - which becomes the severity.
  • Who needs to know - which becomes the routing in step 5.

2. Draw the area​

  1. In the sidebar, under Configuration, select Geofencing.
  2. Create the area and draw it, following Draw a geozone.

Two decisions here matter later:

  • The name. You will be choosing this area from a list when you write the policy, and it appears on every alert the policy raises. Name it as an operator would say it out loud. Each name can only be used once: IFMS refuses a name another zone already uses.
  • The speed limit. If the policy will check speed against the zone's own limit (Use zone's limit), fill in Speed limit (km/h) on the zone. Without it the policy has nothing to compare with and never fires.
  • The size. Draw the area a little larger than the physical site. A boundary drawn tight to a gate can be crossed by a vehicle driving past it, or missed entirely between two position reports.

If you have several areas of the same kind, put them in a group - see Geozone groups. A policy can then watch the whole group at once. Creating many areas at once is quicker from a file: Import geozones from a CSV file.

Check before moving on: the area appears in the list without an Inactive badge, and its outline sits where you expect on the map.

3. Write the policy​

  1. In the sidebar, under Configuration, select Alert Policies.
  2. Create the policy, following Create an alert policy.

The step that decides whether this works at all is the condition: which area, and which direction - entering or leaving. Getting that backwards produces a policy that looks right and fires at the wrong moment, or never.

Rather than working it out from scratch, start from the matching example in Policy recipes, which gives the exact settings for entering an area, speeding inside one, staying too long, and leaving one.

Decide the severity honestly. Severity drives the response window and the escalation described in Response times and escalation, so marking everything Critical does not make things happen faster - it makes the Critical banner useless.

4. Choose which vehicles it applies to​

A policy that applies to every vehicle on a busy corridor can produce hundreds of alerts a day. Narrow it where you can - to one operator's fleet, for instance - as described in Create an alert policy.

Start it switched off, or narrow

A new policy on a busy area is the most common cause of an unusable alert queue. Point it at a handful of vehicles first, watch what it produces for a day, then widen it.

5. Decide who is told​

Everyone who can see alerts will see these in the portal and in their Inbox - that happens automatically and needs no configuration.

Email and SMS do not. If somebody needs to be told away from their screen, an administrator must add a rule under Alert Routing, matching the severity or kind of alert this policy raises to the role that should receive it.

Tell the administrator two things: the severity your policy raises, and which role needs the message.

6. Check it actually fires​

A policy is not finished until you have seen it work.

  1. Wait for a vehicle to do the thing at the place - or watch a vehicle approaching the area on the Live map.
  2. Open Events and filter by the vehicle, or search for the policy's name.
  3. Confirm an alert appeared, with the severity you chose and the area named on it.

If nothing arrives, work through it in this order:

  1. Is the policy switched on? See Alert Policies.
  2. Is the area switched on? A zone marked Inactive is not watched.
  3. Does it apply to the vehicle that moved?
  4. Is the direction the right way round - entering where you meant entering?
  5. Did the vehicle actually report a position inside the area? A vehicle whose tracker went quiet crossing the boundary produces nothing. Check its last report time on its page.

If far too many alerts arrive instead, narrow the vehicles or raise the threshold rather than deleting the policy - the history it has already produced is worth keeping.