Known limitations
This page is here so that nothing on your screen surprises you. It lists what IFMS does not do today, and the places where a word, a number or a control means something other than it appears to.
None of this is a fault you can fix, and none of it means the data is wrong. Where something matters while you are working, the chapter it belongs to repeats the warning in place.
Finding your way
- Two screens have no menu entry. Live map is reached only from Open live map on the Overview, and Inbox only from the bell's View all. While you are on either, no menu item is highlighted.
- A link to a particular page is lost at sign-in. However you arrived, you land on the Overview and have to open the link again.
- A narrowed sidebar is not remembered. It reopens at full width every time the page is reloaded.
Names that differ from screen to screen
- Events lists things that the rest of the portal — the notifications, the Overview counter, the routing screen — calls alerts, while Alert Policies is titled Event Rules in some translations.
- The finished state of an alert is Closed on the badge, the button, the timeline and the exported file, but Resolved on the counter card and in the Status filter.
Live data
- The Events list does not refresh by itself. New alerts appear only when you reload, change a filter or turn a page — although the empty message says "wait for the live feed". The bell's count does keep up, refreshing about once a minute.
- The green Live pill is decorative. It never turns red or grey, even if the position stream has dropped and is reconnecting. When that happens, map markers simply stop moving and nothing on screen says so.
- The sparklines on the Overview counters begin with invented history. The first stretch of each line is a pattern drawn around the current value, not a record of the past. Read the number, not the line.
Counts that do not agree
- Counter cards show 0 while they load, with no loading sign, so a screen can state there is nothing to do and then fill in a moment later.
- The Events counter cards ignore the filters and count all three kinds of alert, while the list below them opens filtered to Rule events only. The Escalated card includes alerts that have since been closed.
- The red banner counts only the page in front of you, and counts High alerts as critical. Selecting Review filters to genuinely Critical alerts, so it can show fewer rows than the banner counted, or none.
- A provider's Alerts (24 h) can read 0 while its Recent events list shows alerts from a few hours ago.
Where an alert says it happened
- The Location shown on a rule event is not where the vehicle was. The LOCATION column is the name of the policy's geozone; the coordinates in the alert's panel and the marker on the Events map are the centre of that geozone.
- Alerts with no geozone all sit at the same point near Addis Ababa — speeding, ignition and idling policies without a zone, every integration-health alert.
- Treat rule-event locations as "which zone". A legality alert instead carries the last stored position and its time, when available.
Handling alerts
- There is no manual escalation, for any role, despite the built-in description of the supervisor role. Escalation is automatic, happens once, and therefore always shows as L1.
- The Breached mark disappears when you acknowledge. Only an open alert can be breached, so acknowledging a late alert removes the evidence that it was late. The L1 badge is then the only trace.
- The age of an alert keeps growing after it is closed. The column counts from when the alert was raised, not to when it was handled.
- An alert cannot be reopened, and there is no assign, comment or bulk action. Closing is final.
- Export CSV on the Events screen exports only the page you are looking at — ten rows by default — and leaves out the acknowledgement note. The Acknowledged by and Closed by columns contain an internal identifier rather than a person's name.
- The rule that raised an alert is never named on the alert. The policy's name is only visible inside the message text, followed by (Start) or (End).
- Repeat occurrences are not shown. An integration-health alert quietly updates its own text as the problem recurs; how often it has recurred is recorded but not displayed.
- Notifications about legality and integration alerts are titled in capitals — LEGALITY_VIOLATION, INTEGRATION_HEALTH — and an escalated alert arrives titled simply Alert.
- Every alert reaches every active person's Inbox, with no way to opt out, including people whose role does not let them open the Events screen. For them, selecting the notification leads to Access denied.
- If the notification service fails, nothing says so. The bell shows no count and the Inbox shows the ordinary "all caught up" message.
- The Inbox has no un-archive and no delete, and it offers Archive even on items that are already archived.
Writing alert policies
- A scheduled active window is not applied. A policy set to Scheduled, with a timetable, is still checked at all times. Until this changes, treat every policy as Always armed.
- Switching a policy on can raise a burst of alerts. Every vehicle already in the matching state counts as having just entered it, so an "Outside the zone" policy can raise an alert for nearly the whole fleet at once.
- Geofence alerts are labelled by the moment, not by the direction. An alert raised at the start of a match is always called Geozone entry and one raised at the end Geozone exit — so an "Outside the zone" policy that fires when it starts, meaning a vehicle has left, is labelled entry. Build entry and exit policies from Inside the zone, as Policy recipes describes.
- "Idle / distance" is idle time only — distance plays no part, despite the name. The alerts it raises are called Excessive idling.
- A policy set to Specific vehicles can be saved with no vehicles on it. It then shows as Active and watches nothing.
- Changes to a policy's vehicle list save immediately, before you select Save changes — and Cancel does not undo them. Switching a saved policy away from Specific vehicles and saving deletes its vehicle list.
- A failed vehicle import does not say which rows failed, only how many of how many succeeded.
- The wizard never explains why it will not continue. Next and the save button simply stay grey, and the review step leaves out the name, the timing, the active window and the conditions themselves.
- The conditions column shows raw wording such as Geofence INSIDE and Ignition ON.
- Deleting or switching off a policy leaves its alerts open. They stay in the queue and still have to be closed.
- The severity filter hides policies with no severity. They appear only under Severity: All.
Geozones
- The shape cannot be changed when editing. A circle can never become a many-sided zone; draw a new zone and delete the old one.
- There is no box for coordinates or a radius, and no address search. You find the place by moving the map, and size a circle by dragging.
- Only many-sided zones can be imported. Circles must be drawn.
- A zone's speed limit shows only in the editor, not in the list or on the map.
- A deleted group cannot be restored. Deleted zones can be; groups cannot.
- Geozone not found points you to Show deleted but has no Restore button of its own.
- The import preview does not know which names are taken. A name already in use, or two names that differ only in capitals, look fine in the preview and are refused only in the Server result.
- A restore refused because the name is taken shows only the general red message "A geo-zone with this name already exists."
- Live vehicles on this map shows only vehicles cleared for the map.
Vehicles and providers
-
Only legal vehicles are visible. A vehicle that stops being legal disappears from all vehicle views. Its history is kept but hidden. Its legality alert stays in Events without a vehicle link.
-
There is no way to add a vehicle. Vehicles appear on their own, the first time IFMS accepts a position after IFTMS says the vehicle is legal.
-
Vehicles and providers cannot be changed in the portal. A vehicle's details come from the provider and IFTMS; correct them in IFTMS.
-
A plate is reported by one provider only. If a vehicle moves to another provider, the new provider's positions are refused until IFTMS records the change of operator, or the old provider has been silent for 30 days. See One provider per plate.
-
A provider's name cannot be changed in the portal. A provider that has not sent a readable name is shown as Unnamed provider (…) and is left out of the provider lists in the policy wizard and on Alert routing.
-
Marking a provider Inactive is a label only. Its positions are still received.
-
"Last updated" is about the record, not the vehicle. It changes when IFTMS sends an update. Use Last seen for how recently the vehicle reported.
Reports
- Report figures lag a few minutes behind. A day is rebuilt about five minutes after new positions arrive; yearly totals can be up to about half an hour behind. Use the live screens for what is happening now.
- Events, speeding and event summaries start on the day reporting was switched on. Nothing earlier is in them.
- The Provider column shows today's provider name, even on old rows. The operator is the one the vehicle had at the time.
- Durations read differently on screen and in files: 3d 2h on screen, seconds in Excel, CSV and PDF. The headings say (s) in both.
- Files carry columns the screen hides — the record numbers (IDs) of vehicles, events, alerts, geozones and operators.
- CSV times are not converted to Addis Ababa time; Excel and PDF times are.
- A PDF holds at most 2,000 rows, and any export at most 1,000,000.
- The export window reads 1 rows for a single row.
- The rows-per-page choice is not kept in the page address, so a link you send opens at 10 rows per page.
Users, roles and routing
- Several areas in the list of rights change nothing a person can see. Roles and permissions marks them.
- Hovering a permission pill shows IFMS's internal names — "Read Event" on Alert policies, "Read Authz role" on Roles.
- The names in the list of rights are not translated. In the Amharic portal the bands, the areas and the pills stay in English.
- The built-in role descriptions are written for engineers, with references to the requirements document and words such as "tenant" and "scoping".
- Details and rights are saved in two steps, both for a user and for a role. If the second step is refused, an amber box says so and offers Retry roles or Retry permissions.
- A role named only in Amharic letters needs its role key typed by hand. The key fills itself in from Latin letters only; type one yourself.
- A custom role may need extra rights to use some screens. Users and Alert routing need the right to read roles; Alert routing also needs the right to read providers; the role editor needs the right to read the list of permissions. Without them, those lists simply stay empty.
- The Users search matches the first name, the last name, the email address or the sign-in name, each on its own. A full name typed with a space between the two parts finds nobody.
- An Operational manager can deactivate a System admin (unless it is the last active one) but cannot change that person's roles.
- Text messages go to the main phone only. The Alternative phone is never used, and anybody with no phone or no email is silently skipped.
- Nothing anywhere shows whether an email or a text was delivered.
- Reactivating a person restores all their roles, because deactivating keeps them.
Language, printing and times
- Some words stay in English in the Amharic portal: Cancel in every dialog, the map controls (Map, Satellite, Hybrid, Full view), the text on a map marker's hover card, the phone-number messages, the country list, Developer docs, and two of the Overview hints.
- Dates stay on the Gregorian calendar in Amharic, written in Amharic script.
- The keyboard hint in the search box always shows the Mac key, even on
Windows, where the shortcut is
Ctrl+K. - Some times can be shown a few hours out. Added, Last updated and Record changed are affected; Last checked and Last seen are correct. A vehicle can appear to have been checked after it was updated, although both happened at the same moment.
Working on a touch screen
- A marker's hover card needs a mouse. Tapping a vehicle opens its page instead, so a touch user never sees the plate, status and location card.
- Row actions in the Inbox are hidden until you hover, on anything wider than a phone.
Not switched on yet
- Administrators cannot set or see a password. New colleagues receive a link by email and choose their own, and a forgotten password is recovered with Forgot Password? — there is no reset button anywhere in the portal.
- Points of interest are held but never shown. No screen lists them.
Related pages
- Troubleshooting — what to do about the things above while you are working.
- Statuses and colours — the exact wording of every label mentioned here.
- Key concepts — why some words mean two things.