Loading...

Recurring Fleet Alerts: What the Dashboard Count Really Means

Make sense of recurring fleet alerts in Plaspy. Separate alert and vehicle counts, compare observation windows, and understand what each view can show.

Cover illustration; not a screenshot of Plaspy.

Plaspy's Alerts block helps you recognize which warnings recur while you monitor a fleet. Its figures make sense when you connect three things: when the dashboard was opened, which vehicles it covers, and whether a number represents alerts or vehicles. Repetition can point you toward a useful investigation, but a count alone does not explain the cause or summarize everything that happened that day.

This becomes apparent when two colleagues compare screens. One has received eight alerts; the other sees only three. Before looking for an error, it helps to understand what each person has been observing. Both may be reading different time windows correctly. They may also be watching the same period with different settings.

The count starts with your observation window

In this block, alerts are counted from information arriving after the page finishes loading. The heading keeps that reference visible: “Since HH:MM, when you opened the dashboard.” That time marks the start of the observation in front of you. Opening Plaspy partway through the morning does not make this counter reconstruct earlier alerts into a complete daily total.

“We received these alerts while monitoring” is therefore a more accurate description than “this is everything that happened today.” The first statement can help investigate an emerging pattern. The second gives the screen a scope this counter does not have. A partial observation can be useful; the difficulty arises when its boundaries disappear from the conversation.

Reloading the page or returning to it restarts these figures. This also matters in the app: leaving it in the background for more than ten minutes causes the page to reload when you return. A number that goes back to zero after that change does not demonstrate a reduction in the activity behind the alerts. The beginning of the count has changed.

The Dashboard blocks documentation distinguishes this observation window from the other periods used by the dashboard. Some figures are calculated for the day, while pending critical alerts have their own scope. Displaying these figures on the same page does not turn them into a single report covering an identical period.

Knowing where the window begins also helps you use it well. If the question is which alerts are arriving during a particular review, the counter is relevant. Reconstructing an earlier working day requires records covering that day. Watching a live screen for a while does not turn its count into a complete historical query.

Eight alerts can involve four vehicles

Imagine a delivery review in an account with fourteen vehicles visible on the Map. The block is being used to observe a group of six. This is a hypothetical example for interpreting the figures, not a report from a real operation or a claim about a customer's results.

A coordinator opens the dashboard at 09:10. By 09:50, she has observed five allowed-area exit alerts and three speeding alerts. In this example, the area-exit alerts are configured as normal and the speeding alerts as critical. The block therefore shows five normal and three critical alerts: eight warnings during a forty-minute observation window.

That total does not yet tell her how many vehicles are involved. The bars group alerts by type and show the corresponding number of vehicles. Opening the area-exit bar reveals two devices: vehicle A has three alerts and vehicle B has two. There are five alerts of that type spread across two vehicles.

The speeding bar contains vehicles A, C, and D, each with one alert. That makes three alerts involving three vehicles. Across both types there are four distinct vehicles: A, B, C, and D. Adding the two vehicles from the first bar to the three in the second would produce five, counting vehicle A twice.

The distinction changes the question worth investigating. Five alerts of one type concentrated in two vehicles may lead you to examine their journeys and the rule's conditions. Five different vehicles would represent a different operational reach. Neither interpretation establishes five independent incidents, five drivers, or five separate causes.

The vehicle detail helps connect a quantity with a recognizable case. Selecting a bar in Plaspy opens the list for that type, including the alert count for each device. You can then open the vehicle's information to continue the review. The value lies in keeping the total, the type, and the vehicles connected, without treating one kind of count as another.

The coordinator can now communicate something specific: she received eight alerts of two types during that window and identified four different vehicles by checking both lists. That last number comes from comparing the names in the example. It does not assume that adding the bars automatically produces a unique vehicle count across every alert type.

Overlapping sessions cannot simply be added together

Return to the colleagues who saw eight and three. In the same example, the second person opened the dashboard at 09:30. Assume both are watching the same group and categories, and receiving the same alerts from that point onward. By 09:50, his session contains two area-exit alerts and one speeding alert: three warnings over twenty minutes.

Those three alerts are already included in the coordinator's eight. Adding the two screens and announcing eleven would count all three from the shared period twice. Recording that two people took part does not solve the problem; each person was observing some of the same activity.

Nor does the smaller number establish that the second colleague's operation had fewer problems. His window began later. The comparison places forty minutes from one session beside twenty minutes from another, even though both people are looking at their screens at the same moment. A common end time does not guarantee a common start time.

For a follow-up discussion, it is clearer to keep the observations separate and explain how they relate. The first begins at 09:10; the second begins at 09:30. In this hypothetical case, we already know which alerts overlap. In a real operation, the available records would need checking before declaring that two quantities can be added or that one is entirely contained within the other.

Now imagine that the coordinator reloads at 09:50. Her next session begins there. The initial zero does not invalidate the eight alerts she previously observed, but the counter in front of her no longer retains that window. To communicate it, she would need to have kept the relevant reference in her normal work record or consult a source covering that period afterward.

That note belongs to the team's working arrangements. This article does not assume that the block stores a case file for each session or a permanent shift log. Keeping an observation's time and scope makes it explainable; it does not add a historical feature that the documentation does not assign to this counter.

The settings are part of the meaning

The Alerts block can count critical and normal alerts, critical only, or normal only. In the example, a view covering both categories shows eight warnings; one limited to critical alerts shows three. That difference could occur even if both sessions started together. Before interpreting the discrepancy, establish what each view counts.

The selection helps focus attention. If your responsibility is to follow critical alerts, normal alerts need not occupy the same space in that review. But an empty critical-only view does not establish that no normal alerts arrived. The filter is answering a narrower question.

The group matters as well. A block can follow the dashboard's group, cover the whole account, or use its own group. A label identifies a block with a group of its own. In our example, the six vehicles being observed are not the same as the fourteen visible to the account. A total for that group does not automatically describe the remaining vehicles.

The guide to arranging dashboards explains these choices. Every conversation about a number does not require an inspection of every control. Checking them is useful when people compare results, take over a responsibility, or expect to find a vehicle missing from the list.

Ignition-on and ignition-off events have a different meaning here. The block presents them as additional activity, separately from alerts, except in the critical-only view. Adding them to the warning total to produce a larger figure would mix concepts. Starting a vehicle for an assigned job does not, by itself, amount to another operational warning.

A custom block title does not replace these checks either. “Morning deliveries” may help a colleague recognize the view, but the label does not certify that the group, categories, or session start match that description. Interpret the number through its actual settings and time window as well as its title.

A recurring pattern still needs an explanation

Vehicle A has three area-exit alerts in the example. That repetition warrants examining the case, but several questions remain open. Expected movements may cross the configured boundary, the area may not fit the operation well, or another situation may require checking. The count does not choose between those explanations.

The investigation becomes meaningful when the alert is related to what was supposed to happen. Leaving an area during an authorized job has a different interpretation from a departure nobody expected. The data may show that an alert condition was met; the working agreement supplies information absent from the number of times it appeared.

Avoid the opposite shortcut as well: repetition does not make an alert irrelevant. Frequency and consequence are different dimensions. A less common signal may need attention before a more numerous one. The configured criticality and your operation's procedure help guide that decision; the most prominent bar does not establish priority on its own.

If the rule does not reflect what you intend to monitor, any adjustment should address that need. Reducing alerts simply to make the dashboard look quieter can hide information that was useful. First establish which situation the rule was meant to detect and why the observed cases do not match that purpose.

A change also affects later interpretation. A smaller count after changing a condition does not, on its own, prove that drivers changed their behavior. What is detected, what is displayed, or the length of the observation may have changed. Assessing an operational improvement requires comparable conditions and enough relevant information.

Even two forty-minute windows can cover different levels of activity. Suppose several vehicles in the same group of six make deliveries during the first window, while most wait at the depot during the second. A lower count in the second window does not establish better driving on its own: there was also less activity that could produce those alerts. The duration and selection match, but the work performed still matters. That comparison needs operational context; the counter alone does not provide a rate adjusted for distance, journeys, or active vehicles.

An empty view makes a limited statement

Alerts depend on their configuration and on the information Plaspy receives. Adding the block provides a way to consult them; it does not replace setting up rules or produce data that a tracker or sensor does not send. Monitoring depends on devices and service conditions that support the required information.

The screen's own connection matters too. The dashboard shows its live connection status and indicates when it is reconnecting. During an interruption, an unchanged number is insufficient evidence that relevant situations stopped occurring across the fleet. A lack of new entries needs to be read alongside the availability of information.

This limitation does not make the block unhelpful. It makes the result more precise: no new alerts have been observed within a particular selection and window, under the reception conditions you have been able to check. That statement supports continued monitoring while making clear what has not been established.

Your account or subuser needs access to more than ten devices on the Map for the Dashboard to be available. Each subuser keeps their own scope and dashboards. Someone continuing a review therefore needs to know which vehicles they can consult, as well as the number shared by the previous colleague.

The Dashboard guide explains that access and the view's connection. The demo offers example dashboards for exploring the layout. With a real fleet, conclusions must be based on its own reports, permissions, and rules. Demonstration information is not evidence of what happened in that operation.

Turn repetition into a useful conversation

At the end of the example, the useful result is more than announcing the largest number. It is explaining what was observed and what needs attention: eight alerts between 09:10 and 09:50, within the selected group, with four distinct vehicles identified by checking the lists. The next question concerns the individual cases behind those figures.

If someone else takes over, they can open a new session and continue watching. They need to keep what has already been reviewed separate from what is arriving now. A new screen supplies a new counting window; continuity in the work also depends on how the people involved share their information.

This makes a practical difference when an investigation continues beyond a single screen session. A colleague can understand why a vehicle was selected for review even if the current counter has restarted. The previous observation remains a described piece of evidence with a time and scope, rather than an unexplained total everyone is expected to remember.

The next time an Alerts bar draws your attention, open its vehicles and read the figure alongside its start time and selection. That context moves the discussion from “too many things are happening” toward an observation that can be checked and a concrete question for the person who follows up. The relevant block description provides the detail when you need to confirm what a figure includes.

Home

Ready to get started with Plaspy?

Buy your GPS tracker or subscribe to our satellite tracking platform.
We are currently offline, but don’t worry.
Leave us your contact details and we’ll get back to you as soon as possible via phone or WhatsApp to +57 (601) 580-3299.


How to check when a truck left the yard after ignition

Separate ignition, movement inside the yard and the truck’s departure. Give dispatch a time it can confirm before updating the receiver.

How long did a truck stop when its GPS reports have gaps?

Separate observed timestamps from the start and end of a truck stop. Use the Plaspy timeline to work out what the available reports can establish.

Truck movement alerts: how to confirm an authorized yard move

Match the unit, yard instruction and Plaspy event to verify an authorized truck move with a Ruptela Eco5 Lite and confirm where the vehicle ended up.

How to check whether a truck used a detour in GPS history

Look at the reports before, within and after a detour to see what Plaspy can establish about the route and where another trip record may help.

How to hand over a shift while a truck is still on the road

Build a dispatch handover around the truck’s last reported location, its timestamp and the action the next shift needs to take before updating a customer.

Boxtrack 4G: Understanding Its Installation Demonstration

Understand the Boxtrack 4G demonstration: its tester, relay and different panic inputs. Prepare a clear discussion about your installation and its checks.

Billing GPS Customers Across Different Platforms

Bring together billing for Plaspy devices, external trackers and phone lines. Understand each item and which actions remain with other providers.

GPS Payments: What to Expect from a Reminder

Start organizing GPS customer reminders with clear expectations. Distinguish sending notices, receiving payments and improving payment timeliness.

Installing a GS1000: What a Handover Check Establishes

A map position does not verify an entire GS1000 installation. Understand each observed response and what to agree when your motorcycle is handed back.

GS1000 Cost: A Monthly Average Is Not a Monthly Payment

Budget three years of GS1000 use without counting the included first year twice. Separate monthly averages, actual payments, renewal and installation.