Skip to main content

Start your shift

Who this is for: Operator, Supervisor.

What you will achieve: you will know whether IFMS is actually receiving data, what happened while you were away, and which alerts need you first.

1. Sign in and check the data is live​

  1. Sign in. You land on Overview.
  2. Look at Last updated, at the top right.

This is the single most important check of the day. Last updated is the time of the most recent report from any vehicle, and it should read seconds, not minutes.

A green "Live" badge is not evidence

The Live badge in the header is always green. It is not connected to the data feed, so it stays green during an outage. Last updated is the only honest indicator on the screen. If it is minutes old, reload the page; if it is still old after reloading, tell whoever supports IFMS before you trust anything else on this screen. See Troubleshooting.

2. Take in the shape of the fleet​

Still on Overview, read the four cards:

  • Moving now, against "of N tracked" - how much of the fleet is under way.
  • Idling - engines running while standing still.
  • Events today - alerts raised since midnight. This is your workload.

These counts cover only vehicles IFTMS says are legal. Fleet, search and all maps use the same rule. Check Events for a legality alert if a vehicle disappears.

3. Open the alert queue​

  1. In the sidebar, select Events.

If a red banner sits at the top saying a number of critical alerts need attention, start there: select Review on the banner, which filters the list to exactly those. See Events.

4. Work the queue in this order​

Take the alerts in this order rather than top to bottom:

  1. Critical, still open. Filter Severity to Critical and Status to Open.
  2. Anything marked Breached or L1. These have already missed their response window or been escalated - see Response times and escalation.
  3. Everything else still open, oldest first. The Age column tells you which those are.

For each alert, follow Handle an alert: open it, read the panel, acknowledge it with a note saying what you are doing, and close it with a note saying what happened.

Acknowledge early, close honestly

Acknowledging is not the same as fixing. Acknowledge as soon as you pick an alert up - it stops the response clock and tells everyone else it is yours. Close it only when the matter is genuinely finished.

5. Check what came in overnight​

Select the bell in the header, then View all, to open your Inbox. The Unread tab is what arrived while you were away.

Reading a message here does not acknowledge anything - the work still happens on Events. Use the Inbox as a list of what you might have missed, not as a queue.

An empty Inbox can mean the service is down

If the notification service is unavailable, the Inbox shows "You're all caught up" - exactly as it would if nothing had arrived. Cross-check against Events today on Overview: alerts there but nothing in the Inbox means messages are not being delivered.

6. Glance over the fleet itself​

Open Overview → Open live map for the Live map, and look for:

  • Grey cars - vehicles nothing has been heard from for more than 10 minutes (No signal). One or two is normal; a cluster suggests a provider has stopped sending.
  • Orange cars standing in the same place across the shift - vehicles idling with the engine on for a long time. Red cars are parked with the ignition off.

Switch to the Table tab and set the Status filter to No signal for a countable list. Use Status and Provider only - the Type, Region and GPS filters will empty the table, for the reasons explained in Live map.

If a whole provider has gone quiet, check Providers to see when it last sent anything.

What "done" looks like​

  • Last updated is seconds old.
  • No critical alert is still unacknowledged.
  • You have read the overnight messages in your Inbox.
  • You know which vehicles are silent and whether a provider is behind it.