Dashboard blocks

Use it to find the devices that stopped sending data and decide what to check: coverage or battery problems, device or line failures, or devices that are possibly out of service. It lists the devices in the Not reporting state, that is, with more than 5 h without data, that have been silent longer than the time picked in From.

The big number is the total, with devices not reporting, and below it N without positions appears if some devices have no position at all. A bar with its legend splits them by range: 5 to 24 h, 1 to 7 days and Over 7 days; ranges below From are not shown. In the list, each device says X ago and, on the secondary line, its group and area.

In Settings you pick From: Over 5 h, the default, Over 24 h or Over 7 days.

Use it to follow live how the fleet is split across the states. It shows a doughnut chart with the share of the fleet in each state, only for the states that have vehicles, and it changes live.

Next to the chart, the legend gives the name of each state, its percentage with one decimal and the number of vehicles. Clicking a state in the legend opens the bottom list with those vehicles and the value Last report (X ago).

Use it to keep in sight where each vehicle is without leaving the dashboard, or only the ones that need attention. It is a map inside the block with the live position of each vehicle and the same icon it has on the Map, and it always uses the OpenStreetMap map.

The map fits itself so all vehicles are visible; with many vehicles, it leaves the few farthest ones out of the frame. Markers move with each position, and below the map a legend counts the vehicles Moving, Idling, Stopped, No recent signal and Not reporting. Vehicles without valid coordinates, such as the ones with no position, are not shown. Clicking a marker opens the Map's device window, which follows that marker. If the map cannot load, the block says The map needs an internet connection to load.

In Settings you pick what to Show: All vehicles, the default; Only with critical alerts, without signal or not reporting, that is, the ones with pending critical alerts or in Not reporting or No recent signal; or Only moving. By default it takes 8 columns.

Use it to react quickly when a vehicle goes silent while moving or with the engine on, which may be lack of coverage or a theft. It lists the vehicles in the No recent signal state: they stopped reporting 15 min ago or more while moving or with the engine on, without going past 5 h.

The big number comes with vehicles without a recent signal. If a possible general outage was detected, besides, N in a possible outage also appears, and those vehicles are not listed. In the list, the value is Time without signal (X ago).

Use it to see at a glance how the fleet is right now. It counts how many vehicles are in each state and what share of the fleet, or of the group, each one is.

It has one cell per state (Moving, Idling, Stopped, No recent signal, Not reporting and, only if there is any, No positions), each with the number of vehicles, the state name and the whole percentage. Below, a colored bar shows the proportions, together with the line N of M devices reporting (moving, idling or stopped). Clicking a state opens the bottom list with those vehicles; the value is Speed for the moving ones, Time idling for the idling ones and Last report (X ago) for the rest.

By default it takes all 12 columns, the full width of the dashboard.

Use it to see what is happening with alerts while you have the dashboard open and which types repeat the most. It counts the critical and normal alerts that arrive since you opened the dashboard, with the live positions; it has no history, so reloading the page restarts it.

At the top it says Since HH:MM, when you opened the dashboard, with two figures: critical, in red, and normal. Then comes one bar per alert type, with the type name, the number of vehicles and · critical if it is; there is no See all and the bars scroll inside the block. Clicking a bar opens the bottom list with the vehicles that have that type and the value Alerts (N alerts). Vehicle ignition on and off do not count as alerts: if there are any, at the end it shows Also, N ignitions on and off: that is activity, not alerts., except with Critical only.

In Settings you pick which Alerts to count: Critical and normal, the default, Critical only or Normal only.

Use it to watch only the alert types you care about, for example speeding or leaving an area, and see which vehicles have them. It shows, by vehicle, the alerts of the types you choose that arrived since you opened the dashboard; reloading the page restarts it. You can add it several times with different types.

At the top it says Since HH:MM, when you opened the dashboard, with two figures, alerts and vehicles, and a line with the chosen types or Every alert except ignition on and off. In the list, the value is Alerts (N alerts) and the secondary line gives the type of the last alert, with (critical) if it is, X ago and the group.

In Settings you check the Alert types in grouped check boxes. None comes checked: With none checked you see all of them, except ignition on and off. The automatic title changes with what you check: Alerts by type with no types, Alerts: type with one and Alerts: type and N more with several. The types are grouped like this:

• Security: SOS button, Tracker disconnected, Device offline, GPS without signal, GPS off, Low battery, Battery voltage and Vibration.
• Driving: Speeding, Harsh braking, Harsh acceleration, Speed below, Minutes idling and Minutes without moving.
• Zones and routes: Forbidden area, Leaving an allowed area, Check area, Checkpoint and Off the route.
• Sensors: Vehicle ignition on, Vehicle ignition off, Input 2 on, Input 2 off, High temperature, Low temperature, Sudden fuel drop and Low fuel.
• Maintenance: Mileage reached and Date reached.

Use it to review and attend the most important alerts from the dashboard, without going to the Map. It lists the vehicles with critical alerts not attended in the last 24 h, including the ones that were already pending before you opened the dashboard; critical alerts are the ones set up with Critical alert, highlight on the map, and new ones arrive live. The Attend button works as on the Map: it only attends the alerts you see, and the ones that arrive later stay pending. As the block's note says, Once attended here or on the Map they stop being pending for every user of the account.

The big number is the number of vehicles, with vehicles with alerts not attended, and below it N alerts in the last 24 h. With Category set to All, one button per category appears with its number (Security, Operation and Driving); clicking one opens the bottom list with that category. In the list, the value is Alerts (N alerts) and the secondary line gives the types (the alert text or the type name, with ×N if it repeats), already reporting again if its alerts are only offline alerts and the device has reported since, the area and X ago for the most recent one. Each row has its own Attend button and, when there is more than one row, Attend all of the list appears at the bottom and asks for confirmation: You are about to attend N alerts of N vehicles. They stop being pending for every user of the account. If something fails, it shows Some alerts could not be attended. They remain pending; refresh and try again. While the pointer is over the list, the rows do not change places.

In Settings you pick the Category: All, the default, Security, Operation or Driving. Security covers SOS, GPS disconnected, offline, GPS without signal, GPS off, forbidden area, low battery, battery voltage and vibration; Driving, speeding, harsh braking, harsh acceleration and speed below; and Operation, every other type. A vehicle takes the most important category of its alerts: Security, then Operation, then Driving. It needs alerts set up as critical on the devices.

Use it to see whether problems concentrate in one place, for example an area with poor coverage. It groups by the area of the last position (as Secure GPS locates it) the vehicles with pending critical alerts or in Not reporting.

Each row has the area name, N with alerts · N not reporting, the total and a proportional bar. Vehicles without a known area do not appear. Clicking an area opens the bottom list with its vehicles and the value Alerts or last report (N alerts or X ago), and See all opens the All areas list, with the columns Area and Devices.

Use it to spot engines left running for no reason, which burn fuel without moving the vehicle. It lists the vehicles stopped with the engine on right now (Idling state) and for how long.

The big number comes with vehicles idling and, below it, X with the engine on without moving, in total. Each row shows the time idling and, on the secondary line, the group and area.

In Settings you pick Show from, in minutes: it starts at 10 and accepts 10 to 240.

Use it to see who is working right now and how long each trip has lasted. It lists the vehicles moving at this moment, with their speed and how long they have been on this trip.

The big number comes with vehicles moving. Each row shows the current speed, which is the block's value (Speed), and on the secondary line trip of X, the time on the current trip, the area and the group.

Use it to know which vehicles are parked and for how long, for example to see who has been stopped for too long. It lists the vehicles in the Stopped state, usually with the engine off, and how long the current stop has lasted.

The big number comes with vehicles stopped. Each row shows the stop duration, or no stop data when it is not known, and on the secondary line the area and group.

In Settings you pick Stops of at least, in minutes: it starts at 0 and accepts 0 to 1440. Vehicles without stop data only show with 0.

Use it to see how the fleet is moving right now and who is going fastest or slowest. It shows the current speed of the moving vehicles.

The big number is the number of vehicles, with vehicles moving and average N, the current average speed. The histogram counts how many are in each range: 5–20, 20–40, 40–60, 60–80, 80–100 and +100 km/h; bars are green up to 80, amber from 80 to 100 and red from 100, and in an account with the imperial system the ranges show in mph with one decimal. The list shows the current speed of each vehicle and, on the secondary line, the group and area.

Use it to identify who brakes or accelerates harshly, a way of driving that wears the vehicle and raises the risk. It is a day block: it counts the harsh brakings and accelerations of each vehicle since midnight, with the device counters against its first position of the day, as in Statistics, and when you open the dashboard it shows Working out the day… If the device does not send those counters, it counts its harsh braking and harsh acceleration alerts since you opened the dashboard.

The big number is the total, with harsh brakings and accelerations today, and below it N harsh brakings · N harsh accelerations · N vehicles. Each row shows the vehicle's total of events and, on the secondary line, N harsh brakings · N harsh accelerations, or alerts since HH:MM when alerts are counted, and the group. It needs a device that reports harsh events.

Use it to compare at what pace each vehicle traveled today. It is a day block: it calculates the average of each vehicle as the distance of the day divided by the moving time of the day, and when you open the dashboard it shows Working out the day…

The big number is the fleet average, the total distance divided by everyone's moving hours, with fleet average and N vehicles. Each row shows the vehicle's average and, on the secondary line, the distance and the time, for example 85 km in 2 h 10 min, and the group. Only vehicles with 5 km or more today, or the equivalent in miles, are shown.

Use it to measure how much time the vehicles spent today with the engine on without moving, a fuel cost you can reduce. It is a day block: it adds up that time since midnight, with the device's idling counter against its first position of the day, and when you open the dashboard it shows Working out the day…

The big number is the total in hours with one decimal, with idling today and N vehicles. Each row shows the duration of today's idling for each vehicle.

Use it to keep speeding under control with the limit you use in your operation. It shows the vehicles above the limit you choose, now and since you opened the dashboard. It only uses the live positions, so the “since you opened the dashboard” part restarts when you reload the page, and speeding with the ignition off does not count, because it is GPS drift. You can add it several times with different limits, for example one for the city and another for the highway.

At the top there are two figures: over it now, in red, and went over it since HH:MM, in amber. With the Over it now list, it shows the vehicles moving, with the ignition not off and above the limit, and each row shows the current speed with top N below it. With the Went over it since you opened the dashboard list, it shows the ones that went over the limit since opening or are over it now, and each row shows the higher of the top speed and the current speed, with N now below it if it is still moving or its state if not; the secondary line ends with the group. In the bottom list, the value is called Current speed with the Over it now list and Top speed with the other one. The top speed only counts when going faster than 5 km/h, with the ignition not off and without a frozen reading, and readings above 200 km/h do not count.

In Settings you pick the Limit, in km/h: it starts at 100 and accepts 20 to 200, in steps of 5. In List you pick Went over it since you opened the dashboard, the default, or Over it now. The automatic title is Speeding over and the limit, for example Speeding over 100 km/h, in mph with one decimal in an account with the imperial system.

Use it to see who has gone fastest while you have the dashboard open. It shows the top speed of each vehicle since you opened the dashboard; reloading the page restarts it.

The big number is the highest of all, with the highest since HH:MM and N vehicles. Each row shows the vehicle's top speed. Only vehicles that went faster than 5 km/h are shown.

Use it to know what share of the fleet worked today and how many hours each vehicle had the engine on. It is a day block: it adds up, by vehicle, the hours with the engine on today, moving and idling.

The big number is the share of the fleet used today, that is, the vehicles with more than 0.5 km today among the ones with figures for today; it comes with of the fleet was used today and N of M with figures for today. A bar compares the used vehicles with the unused ones. Each row shows the total time and, on the secondary line, X moving · X idling.

Use it to know how far each vehicle has traveled today and how much the whole fleet adds up to. It is a day block: for each vehicle it subtracts the odometer of its first position of the day from the current one.

The big number is the fleet total, with traveled today and N vehicles. Each row shows the vehicle's distance, and only the ones that traveled some distance are shown.

Use it to track how much each vehicle is used in engine hours, which helps with maintenance and with comparing against the distance traveled. It is a day block: it shows the time with the ignition input (ACC, input 1) on today, like the ignition sensor activity in Statistics.

The big number is the total in hours with one decimal, with with the engine on today and N vehicles. Each row shows the duration. If no device reports it, the block says No device reports engine hours. It needs a device that reports the ignition input.

Use it to find the vehicles that burn the most fuel for the distance they travel. It is a day block: it calculates the distance traveled today per tank consumed, according to the device sensor.

The big number is the total distance divided by the total tanks, with one decimal and the distance unit, with per tank, across the fleet and N vehicles. Each row shows N km/tank (or mi/tank) and, on the secondary line, the distance and the tanks, for example 85 km with 1.5 tanks, and the group. Only vehicles with 5 km or more and 0.5 tanks or more consumed today are shown, and a note explains Uses the accumulated tank fraction reported by the device. It needs a fuel sensor.

Use it to know how much fuel each vehicle used today according to its sensor. It is a day block: it subtracts the accumulated consumption of the device's first position of the day from the current one. It is measured in tanks, that is, the whole tanks and fractions of a tank that the device reports, without converting to liters or gallons.

The big number is the total with one decimal, in tanks, with used today in total and N vehicles. Each row shows N tanks, and a note reminds you Accumulated consumption in whole tanks and fractions of a tank. If no device has consumption, the block says No device has recorded consumption today; only the ones with a fuel sensor measure it. It needs a fuel sensor that reports the accumulated consumption.

Use it to know how long each vehicle has been on the move today. It is a day block: it shows how long each vehicle has moved since its first position of the day, like the activity time in Statistics.

The big number is the total in hours with one decimal, with moving today in total and N vehicles. Each row shows the duration.

Use it to see how much time the vehicles spent parked today, for example to review idle time between jobs. It is a day block: it shows how long each vehicle has been stopped since its first position of the day.

The big number is the total in hours with one decimal, with stopped today in total and N vehicles. Each row shows the duration.

Use it to know at what time each vehicle started working and to spot the ones that turn on before a time you choose, for example outside working hours. It lists the vehicles whose ignition (input 1) went from off to on since you opened the dashboard, with the time of the first ignition; reloading the page restarts it.

The big number comes with vehicles turned on since HH:MM and, below it, N before HH:MM, according to the time you picked. Each row shows the time of the first ignition and, on the secondary line, before HH:MM if it turned on before the time you picked, N times if it turned on more than once, and the group. A vehicle that was already on when you opened the dashboard does not count until it turns off and on again.

In Settings you pick Warn if it turns on before, which starts at 05:00. It needs a device that reports the ignition input.

Use it to find long stops that started while you have the dashboard open, for example a delivery that is taking too long. It shows the longest stop of each vehicle among the ones that started since you opened the dashboard, including the one still in progress; reloading the page restarts it.

The big number is the number of vehicles, with vehicles with stops of X or more and since HH:MM. Each row shows the duration of the stop. The stop that already existed when you opened the dashboard is not counted here: it shows in Devices stopped.

In Settings you pick From, in minutes: it starts at 5 and accepts 0 to 1440.

Use it to see how many stops each vehicle makes, for example on a delivery route. It counts, by vehicle, the stops of 5 minutes or more that started since you opened the dashboard; reloading the page restarts it.

The big number is the total, with stops since HH:MM and N vehicles. Each row shows N stops and, on the secondary line, the longest X and the group. A stop counts when the vehicle moves again; the one in progress also counts if it has already lasted 5 minutes.

Use it to count how many trips each vehicle makes while you have the dashboard open. It counts the trips that started since you opened the dashboard; reloading the page restarts it.

A trip starts when the vehicle moves (faster than 5 km/h, with the ignition not off) after a stop of 5 minutes or more, and ends with another stop of 5 minutes or more; the trip in progress when you opened the dashboard does not count. The big number is the total, with trips since HH:MM and N vehicles, and each row shows N trips.

Use it to watch whatever you have connected to the device inputs, such as doors, power take-off or refrigeration. It shows whether inputs 2, 3 and 4 are on or off right now, on the devices that report them and are not Not reporting or No positions.

There is one figure for each input that some device reports: the number that are on, with Input 2 · of N, where N is the number of devices that report it. The list of the chosen input shows on or off on each row, which is the value State, and the group on the secondary line.

In Settings you pick the List: Input 2, the default, Input 3 or Input 4. It needs a device with inputs 2 to 4 connected and reported.

Use it to know which vehicles need to refuel soon. It shows the fuel level (%) of the devices with a sensor and how many are below the level you choose.

The big number tells how many are below that level (below N %) and, next to it, N devices with a sensor. The list shows each vehicle with its level (N %). It only counts the devices that have ever reported a level above 0 and leaves out the ones in Not reporting or No positions; a note reminds you: Only the devices that report a level above 0 count; check on each device that it has a fuel sensor set up.

In Settings you pick the value of Warn below: it starts at 20 % and accepts 1 to 90 %. It needs a fuel sensor set up on the device.

Use it to see which vehicles have the engine on or off right now and how long it has been on today. It takes the ignition from input 1 (ACC) and leaves out the vehicles in Not reporting or No positions.

A doughnut shows N on, N off and N without an ignition input. In the chosen list, each row shows X on today, the time with input 1 on today (or 0 min if it is less than a minute), Working it out… while the day is being worked out, or “—”. The secondary line gives the state, turned on X ago or turned off X ago if it changed with the dashboard open, and the group.

In Settings you pick the List: Ignitions, the default, with the vehicles that have the ignition on, or Off. It needs the ignition input connected and reported by the device.

Use it to measure how long whatever you have connected to input 2, such as a door, a pump or a crane, was used today. It is a day block: it shows how long input 2 of each device has been on today, like the activity of specific functions (sensor 2) in Statistics, and when you open the dashboard it shows Working out the day…

The big number is the total in hours with one decimal, with with input 2 on today and N vehicles. Each row shows the duration. It needs something connected to input 2 of the device.

Use it to protect the cold chain or any load that is sensitive to temperature. It shows the current temperature of the devices with a sensor and how many are outside the range you choose, not counting the ones in Not reporting or No positions.

The big number tells how many are outside the range (outside MIN to MAX) and, next to it, N devices with a sensor. Each row shows the temperature with one decimal and, on the secondary line, out of range if it is, and the group.

In Settings you pick the Lowest allowed, which starts at -20 °C and accepts -40 to 60 °C without going above the highest, and the Highest allowed, which starts at 8 °C and accepts -40 to 80 °C without going below the lowest; in an account with the imperial system they are edited in °F. It needs a temperature sensor.

Use it to catch vehicles with a weak battery in time, before the vehicle does not start or the device stops reporting. It shows the battery voltage the trackers report and how many vehicles are below the value you choose.

The big number tells how many are below that value (below N V) and, next to it, how many devices report voltage (N devices report voltage). The list shows each vehicle with its voltage, with one decimal. It only counts the devices that have ever reported voltage and leaves out the ones in Not reporting or No positions.

In Settings you pick the value of Warn below: it starts at 11.5 V and accepts 5 to 30 V, in steps of 0.1. It needs a tracker that reports the battery voltage.

Use it so you do not miss a maintenance, an insurance renewal or an inspection. It lists the device reminders that are already overdue or coming up soon; they come from each device's active mileage and date alerts that have their value set, which in Alerts by type are called Mileage reached and Date reached.

At the top there are two figures: overdue, in red, and coming up, in amber. Each row shows the alert name and the value (Due): by mileage, N km to go or passed N km ago; by date, due in N days, due in less than a day, overdue by less than a day or overdue by N days. The secondary line gives the reminder name and the group. Only the ones less than 20,000 km or 180 days away are considered; mileage reminders are compared with the current odometer, which updates live, and date reminders with the current time. A vehicle with no position at all shows no reminders, and mileage reminders need the odometer.

In Settings you pick the Type: Mileage and date, the default, Mileage only or Date only. In Upcoming by date: at most you pick how many days ahead a reminder appears: it starts at 30 and accepts 1 to 180. In Upcoming by mileage: at most you pick how many kilometers: it starts at 1000 and accepts 100 to 20,000, in steps of 100. Overdue reminders always show. It needs reminders set up as mileage or date alerts on the devices, and new ones appear when you reload the page.

Use it to know which devices stopped showing on the Map because they expired, so you can renew them in time. It lists the account's devices that expired in the last 180 days: their Secure GPS license expired or their Expires date, the one the reseller sets, has passed. It does not include deleted or deactivated devices, and they do not show on the Map until renewed.

At the top there are two figures: License expired, in red, and Your “Expires” date, in amber. Each row shows the device name (or its identifier if it has no name) and N days ago since it expired; the secondary line gives the reason and the groups. The rows do not open the device window, because they have no position on the Map, and there is no See all: the list scrolls inside the block. The account administrator sees all of the account's devices; a subuser or a shared access with its own group only sees the ones of its group and, without a group, the ones of the whole account. The dashboard's Group filter also applies, and the block only updates when you reload the page.

Made for resellers: use it to see at a glance which customers have something pending. It treats each group as a customer and lists the groups with devices not reporting for more than 24 h, with critical alerts or with expired devices.

The big number comes with customers with something pending. The block's table has the columns Group, Devices (the group's devices), Not reporting 24 h+ (devices in Not reporting for more than 24 h), With critical alerts (vehicles with pending critical alerts) and Expired (the group's expired devices), and only the groups with at least one device in any of the last three columns are shown. There is no See all: the table scrolls inside the block, and on a phone each row shows as a card. Clicking a customer name changes the Group filter of the whole dashboard to that group and shows its name in a message.

The block only works with Whole account: with a group picked on the dashboard, or with its own group in Settings, it stays empty. It needs the account's devices organized in groups, and anyone who sees the dashboard can add it. By default it takes 6 columns.