How IFMS works
Everything you see in IFMS starts with one small message: a position report — a vehicle's plate, the time, and where it was. This page follows that message all the way to your screen. You do not need any of this to use the portal, but knowing it explains why a number is what it is, and why some vehicles do not appear on the map.
The journey at a glance
Step by step
1. A provider sends positions
Licensed GPS and fleet-management companies — IFMS calls them providers — run the tracking boxes fitted to the vehicles. Their systems send IFMS a stream of position reports: plate number, time, latitude and longitude, and sometimes whether the ignition is on and which device sent it.
Providers do this themselves, through their own systems. They are guided by a separate public site, the IFMS Developer Docs at ifms-developer.kairosinnovations.dev, which explains how to connect and what to send. Nothing on that site is part of your daily work; it is the address to give a provider who asks how to start.
2. The gateway checks who is sending
Everything arrives through a single, guarded entrance. That entrance identifies the provider from its own credentials and stamps the data with the provider identity IFMS approved. Providers cannot claim to be someone else, and an unknown sender gets nowhere.
This is also why you never create a provider in IFMS. A provider appears in the Providers list by itself, the first time data arrives from it.
3. IFMS stores every accepted position
Each position is checked on its own. IFMS stores it only if it is usable and IFTMS says the vehicle is legal:
- A report that is too old (more than 30 days) or more than 5 minutes ahead of server time is rejected.
- The same report sent twice is recognised as a duplicate and not stored again.
- A new plate is first refused while IFMS asks IFTMS in the background. The provider must send it again later. No vehicle or position is created from that refused position.
Positions are kept for 90 days, which is what makes vehicle history and reporting possible.
Refused positions are never stored. A batch still returns HTTP 202. Each refusal has outcome: REJECTED and a reason: VEHICLE_NOT_REGISTERED, VEHICLE_NOT_LEGAL or VEHICLE_NOT_CHECKED. Sending telemetry explains what the provider should do.
4. IFMS works out what the vehicle is doing
IFMS compares each new position with the one before it and settles on one movement state. The rules are applied in this order, and the first one that fits wins:
| State | When IFMS chooses it |
|---|---|
| No signal | The newest report is more than 10 minutes old |
| Moving | The speed works out at more than 3 km/h, whatever the ignition |
| Parked | Stationary, with the ignition reported as off |
| Idling | Stationary, with the ignition on or not reported |
Speed is worked out by IFMS from the distance and time between two reports, not sent by the provider. Impossible jumps (over 220 km/h) are treated as GPS error and discarded, and a move of less than five metres counts as standing still.
5. IFTMS decides whether the vehicle is legal
IFTMS is the Ministry's vehicle register. Verified and legal mean the same thing: IFTMS says the vehicle may operate. IFMS holds that answer. A new plate triggers one background lookup. Daily updates and change notices keep the answer current.
6. IFMS handles a loss of legality
When a legal vehicle stops being legal, IFMS refuses its new positions and hides it from every vehicle view. Its stored history is kept but hidden. IFMS raises one Critical Legality violation alert for that loss. The alert stays in Events without a vehicle link. A plate that was never legal raises no legality alert.
If the vehicle becomes legal again, its next position can be accepted. A later loss raises a new alert.
7. Alert policies are tested on every position
An alert policy is a rule you write: one or more conditions (inside or outside an area, over a speed, ignition on or off, idling for N minutes), joined with and / or, limited to a place, a time window and a set of vehicles, with a severity.
Every stored position is tested against the active policies. When a condition starts (or ends, if the policy says so), IFMS raises an alert. While that alert is still open, the same condition on the same vehicle does not raise a second one; it counts as another occurrence of the first.
Two kinds of alert are raised by IFMS itself, not by your policies:
- a Legality violation when a legal vehicle stops being legal (raised Critical);
- an Integration health alert when IFMS cannot get an answer it needs (raised High). This one is about IFMS's own plumbing, never about the operator.
8. The portal, the inbox and the messages
- Every vehicle view shows only legal vehicles. This includes Fleet, search, vehicle details, maps and provider counts.
- Every alert lands in the Inbox of every active IFMS user, automatically.
- Email and SMS are sent only where an alert routing rule says so — for example, "Critical alerts to supervisors". Routing adds email and SMS; it never takes the inbox away.
- An open alert that is not acknowledged within its response window is marked SLA breached and escalated once: the notifications are sent again and the alert is pushed back to the front of the queue.
What this means for you
| You notice | The reason |
|---|---|
| A vehicle disappears from all vehicle views | Its legality may have changed. Check Events for a legality alert |
| The Overview counters look lower than the fleet you know | They count only the vehicles the map shows (step 8) |
| A vehicle shows No signal | Nothing has been reported for it for over 10 minutes (step 4) |
| Speed is 0 km/h for a vehicle you know is moving | Speed is derived from consecutive positions; with no new position there is nothing to derive (step 4) |
| A new vehicle appears that nobody added | IFTMS confirmed it is legal and IFMS accepted a position (step 3) |
| An alert repeats in its Occurrences count instead of arriving again | The first alert is still open (step 7) |