Illustrative cover image.
The Map block in Plaspy's Dashboard lets you locate a selection of vehicles and open their details from a marker. Understanding that view means checking the block's group, its filter, the available coordinates, and the area currently in frame. A vehicle missing from the view may still belong to the fleet. A displayed position also needs its timestamp before it becomes a statement about where that vehicle is now.
Imagine the morning review. You have already seen an alert and want to locate the vehicle concerned. Several markers appear around an industrial area, but you cannot identify the one you need. It is tempting to suspect a device problem or call for a location immediately. Sometimes the useful first question is simpler: which part of the operation is this map showing?
The block connects a geographical overview with the details of an individual vehicle while keeping the dashboard in view. Understanding that relationship helps you avoid treating an incomplete view as an incomplete fleet. It also gives you a more specific question when you do need to speak with the person responsible.
The dashboard group and the map group can be different
A dashboard often supports a particular responsibility: vehicles at a branch, a customer's fleet, or a specific operation. The Group filter in its toolbar helps select that population. However, reading the name at the top is not enough to establish that every block follows the same selection.
Each Plaspy block can use The dashboard's group, Whole account, or a group of its own. The dashboard's option follows the toolbar selection. A block with its own group retains that choice when you select another group above; a green label beside its title identifies the separate group. Whole account broadens the population within the user's access, without granting access to devices outside that user's permissions.
This supports a useful arrangement: keeping a broader map beside information about a particular group. It also explains a scene that otherwise appears contradictory. You have selected the northern branch in the toolbar, but the map still includes vehicles elsewhere because its group is independent. The difference does not necessarily indicate an incorrect tracker location.
Before interpreting the distribution, establish which population belongs to that block. If you want to review the northern branch, the map should represent that selection. If you intentionally keep a broader view, retain that context when describing its markers instead of calling them all vehicles from the group shown in the toolbar.
The dashboard blocks documentation explains the relationship between a dashboard group and a block's own group. It matters because the picture can change without any physical movement. Selecting a different population and receiving new positions are different events, even when both change what you see on the screen.
When reviewing the map with a colleague, naming the group is more useful than pointing to a corner of the screen. Users may have different access or differently configured blocks. Looking at Plaspy at the same time does not establish that both people are looking at the same vehicles.
Eighteen vehicles do not always mean eighteen visible markers
Consider a hypothetical example with no customer data. Your selected group contains 18 accessible vehicles. You have checked that the block uses this group and is set to show all vehicles. Sixteen have valid coordinates; the other two do not yet have a position that can be represented on the map.
Now suppose the area you are looking at contains 15 of those 16 vehicles with coordinates. The remaining one is outside the current frame. The count is therefore 15 visible, one with a position outside the frame, and two without valid coordinates. All 18 remain members of the group in this example.
The difference between 18 and 15 does not establish that three vehicles have been removed. Nor does it show that all three stopped reporting for the same reason. We have described two distinct situations: lacking a point that can be placed on the map, and having a point outside the area currently visible.
The Map block adjusts its view to show vehicles and, with many vehicles, can leave the few most distant ones outside the frame. This example does not identify 18 as a threshold for that behavior or reproduce a test of automatic fitting. It illustrates a possible view and the need to distinguish the selected population from the visible area.
That distinction changes the investigation. For the vehicle with coordinates, you want to locate its position and open its details. For the two without coordinates, viewing a wider area cannot create missing geographical information. You need another way into their records and must work with whatever information is available, even when it does not include a map point.
Counting markers can help you get your bearings, but it should not replace identifying the vehicles you are looking for. “Where are the three I cannot see?” contains three individual cases. Keeping their names attached to the review helps you check each one instead of turning a visual difference into an unsupported common explanation.
Even an unchanged count can conceal a change in which vehicles are visible. Suppose one of the 15 points leaves the frame while the previously out-of-view point enters: you would still see 15, but not exactly the same vehicles. This extends the hypothetical example; it is not a test of map fitting. When following a particular vehicle, identify it and check its position as well as counting the markers.
A marker provides a place and a time reference
The Map block uses OpenStreetMap and the same vehicle icons as Plaspy's main Map. Markers move as positions arrive. Selecting a marker opens the device window, which follows that marker. You can therefore connect the point to the vehicle's information without losing the surrounding geographical context during the review.
Having the map open now does not mean every point belongs to the present moment. For a device without new information, the received position is its last known location. The data's timestamp helps you recognize that distinction before saying the vehicle is still beside a warehouse or has reached its destination.
Return to the alert you were reviewing. You find the marker near a facility. That proximity provides a reference for a conversation, but it does not confirm a delivery or explain why the vehicle is there. The map places received information; operational knowledge establishes which service was taking place and what happened on site.
Keep the vehicle's position separate from the location of an earlier event, too. An alert may concern a different moment in the journey. Opening the details now and seeing a marker beside the warehouse does not establish that the event occurred there. Connecting the two requires checking their times and the information associated with the event.
This distinction is not a reason to disregard the screen. It helps you use each piece of information for the question it can answer. A recent position may help place a conversation in context; an older reference may help reconstruct what happened. Confusion arises when those purposes are exchanged without recognizing the difference.
A specific description preserves the context: “The latest available position appears near the facility; I am checking its time and the alert.” The recipient can understand what you observed and what remains to be confirmed. That is more useful than presenting the point as a physical check that the vehicle is present.
Showing vehicles needing attention changes the map's question
The Show option offers All vehicles, Only moving, or Only with critical alerts, without signal or not reporting. The last option brings together vehicles with pending critical alerts or classified as No recent signal or Not reporting. It focuses the review on the cases described by that selection.
That view serves a different purpose from a general overview. When preparing a call about an alert, it can help keep relevant vehicles in view. When examining the distribution of the whole group, remember that a filtered view excludes vehicles that do not meet its condition, even if they have valid coordinates.
Suppose you recognize a stopped vehicle in the general view and then select Only moving. Its disappearance does not mean it was deleted from the account or lost its coordinates. You changed the question the block is answering. Being absent from the new view is consistent with the selection you just made.
The attention filter works on the same principle. A less populated screen can simply mean that you are now examining part of the fleet. That visual reduction does not measure an operational improvement by itself. Describing a change over time requires a consistent scope and suitable data, rather than a comparison between two differently configured maps.
States help guide the review, but they do not independently explain the cause of a situation. Here, the relevant issue is their effect on the visible selection. The definitions and conditions for each state remain available in the blocks documentation, where you can consult them without turning this map discussion into another incident catalog.
When several views serve different purposes, a clear block title helps you recognize the intended question. The guide to arranging dashboards explains the title, group, and configuration options. A useful arrangement lets you understand what you are asking as soon as you open the dashboard, rather than having to infer it from the markers alone.
A list lets the review continue when there is no map point
In the 18-vehicle example, the two vehicles without coordinates still need attention. The map cannot place them somewhere it does not know. Lists in the relevant dashboard blocks provide another route to their information: clicking a row opens the device window, linking a recognizable vehicle name to the details available for it.
When the vehicle has no position, Plaspy opens a summary containing its state, last report, and daily figures. That allows the review to continue without inventing a location. It does not mean every block lists every vehicle. The list you use must also match the group and condition you are examining.
Map and list provide complementary perspectives. One shows spatial relationships; the other lets you recognize a vehicle by name and inspect available information. Using both helps distinguish “I cannot see its marker” from “I cannot find this vehicle within the selection I am allowed to view.” Those are different questions and may need different follow-up.
If the name is also missing from where you expected it, leave the scope of the query open for investigation. Establish the relevant group and access with the person managing the operation. An empty view does not establish that a device was removed, and there is no reason to change permissions before understanding the difference.
To keep the review understandable, record the specific situation you confirmed: a position outside the frame, no valid coordinates, or exclusion by the selection. These are descriptions of that inquiry, not universal fault labels. If you have not established which applies, saying so keeps the next inquiry focused on the missing evidence.
Locating a vehicle helps you prepare a better conversation
Once you identify the device, geographical context can improve the question you ask. Instead of requesting all the information again, you can refer to the vehicle, the available location reference, and the alert under review. The responsible person can then confirm the operational circumstances that the screen does not show.
Visual proximity does not make the resulting decision automatic. A vehicle that looks close may already have another assignment, face an access restriction, or have a location that needs updating. Choosing whom to send requires information about availability and the journey as well as the point represented on the map.
The documented role of this block is to display positions and open details. This article does not attribute optimal routing, automatic nearest-vehicle selection, or an estimated arrival time to it. If your decision depends on those results, obtain them through the appropriate tools and checks rather than treating geographical appearance as the missing calculation.
The same care applies when sharing a screenshot. The image preserves a view of one inquiry, with the group, filter, and frame used at that moment. By itself, it neither contains every vehicle nor explains the age of each position. Including the relevant context helps another person avoid reading the screenshot as a complete inventory.
A useful review can end with a simple explanation: you found the vehicle outside the visible area, confirmed that a selection excluded it, or established that no coordinates were available. Each finding leads to a different conversation. None requires automatically treating a missing marker as evidence of a device failure.
A useful view starts with a specific question
The Dashboard is available to accounts and subusers with more than 10 devices visible on the Map, within their access. Each user works with their own dashboards. If the menu is missing, consult the Dashboard access requirements before interpreting that difference as a problem with your vehicles.
The demo provides example dashboards to view, but their arrangement cannot be edited. Interpreting a real operation requires access to that operation's information. New positions depend on the device, its communication, and configuration; the map also needs an internet connection to load. An example view cannot establish the condition of your own fleet.
Start with a vehicle you already need to review and connect its group, map view, and details. The aim is to explain why it appears where it does, or what limits its representation. That explanation is more useful than moving between markers without a defined question, because it identifies what you know and what you still need.
When you return to the overview, retain one useful distinction: the vehicles in your selection, those with valid coordinates, and those inside the current frame are not necessarily the same set. Recognizing the difference lets the map place information in context while keeping the cases that need another form of inquiry in view.