A delivery coordinator and the person preparing maintenance may look at the same van and ask different questions. One needs to understand what is happening during a service; the other is considering the next inspection. In Plaspy, you can organize several dashboards with different blocks to support those tasks. The benefit comes from giving each view a clear purpose, so the information that matters is close at hand when a decision needs to be made.
Consider a fictional company that uses its vehicles throughout the day and takes advantage of gaps between services to arrange inspections. This is an illustrative example, not a customer case study. Its difficulty is not a complete lack of information: locations, alerts and usage data are available. The problem arises when everything is presented together and each person repeatedly has to separate the information relevant to their own work.
Two responsibilities lead to different readings of the same fleet
During a delivery day, a recent change can alter the coordinator's next conversation. A vehicle that has stopped reporting, an outstanding alert or a location that needs context usually calls for a view close to the present. Bringing those service-related signals together helps that person reach the vehicle they need to inspect without first working through information unrelated to the immediate decision. The view earns its place by supporting that task.
A maintenance conversation can begin elsewhere. An approaching reminder, the usage information available or a condition worth checking may help someone prepare an inspection. The responsible person needs to relate that information to the maintenance plan the company actually follows. The dashboard helps locate data and reminders; it does not independently determine the intervention each vehicle needs or replace the manufacturer's recommendations and the workshop's assessment.
Both people are working with the same fleet. What differs is the question guiding their reading. Trying to handle every task through one composition can give considerable space to information one person rarely needs. Separate purposes allow attention to be organized without artificially dividing the underlying information or presenting incompatible accounts of what happened. The dashboard's role is to make the relevant context easier to find.
The company in this example might keep one view for supervising services and another for preparing maintenance discussions. Those names describe why someone opens each view. They do not make Plaspy assign responsibilities automatically, decide who must inspect each vehicle or switch dashboards when it detects a task. People still choose the view appropriate to the work in front of them and coordinate their responsibilities through the operation's usual arrangements.
A view becomes clearer when each block has a reason to be there
Before adding an indicator, it helps to imagine the conversation it will support. If a block helps identify the devices that need a check, its place in the view has a purpose. If it offers an interesting number but you cannot explain what you would do differently after seeing it, it may be able to wait. Designing a dashboard means connecting information with work, rather than showing how many figures can fit on one screen.
For the operational view in the example, current states, critical alerts and locations may help explain a situation during a service. For the maintenance view, reminders and available usage information can support preparation for an inspection. The particular combination depends on the devices, what they report and the company's processes. Vehicles do not necessarily provide the same measurements, even when they appear together in a dashboard.
It also matters which information is normally read together. If you often consult a reminder and then open the corresponding vehicle, the arrangement should support that reading. If one figure needs another reference to be understood, placing them far apart may make comparison harder. Block order and size should reflect those relationships, rather than being chosen entirely for the appearance of the overall composition or the amount of empty space remaining.
Plaspy lets you change the position and size of blocks. That flexibility can adapt the view to how it is used, but a larger block does not make the situation it describes more important. Priority still depends on context. A good arrangement helps people find information; it should not become an undeclared risk classification or a guarantee that anything lower down the screen can safely be left until later.
Copying a view also carries its earlier decisions forward
Once a composition is useful, another view does not have to be designed entirely from the beginning. Plaspy allows a dashboard to be copied with its blocks and configuration through Save as. You can also create a new dashboard, which begins with the Main dashboard's default blocks. The distinction matters: a copy carries earlier choices forward, while a new dashboard provides a different starting point that still needs to suit its intended purpose.
In the illustrative company, a view used for morning departures could provide a starting point for reviewing vehicles as they return. The copy does not know that the purpose has changed, however. It may retain a fixed group, a title chosen for another situation or a threshold that no longer suits the new question. Adapting it means checking which earlier decisions still apply and which belonged specifically to the original view.
Concrete names make that purpose easier to recognize. A name such as “Maintenance preparation” explains the expected conversation more clearly than several copies called “New dashboard.” Even so, the name does not configure the contents on its own. Calling a view “Night shift” does not make it recognize a schedule, select a different set of vehicles or appear automatically when that shift begins. The label describes a choice that still needs to be made.
The same principle applies to block titles. A custom title should continue to describe what the block shows after its options are changed. If it keeps an older reference, it can encourage a mistaken interpretation even while the data is calculated correctly. Clarity depends on more than whether a setting was saved successfully. The visible label also needs to explain the configuration that is actually in use.
A dashboard group and a block's group can differ
The general group filter lets you focus the dashboard on a set of devices. It offers a practical way to move from the whole account to one part of the operation, but it does not necessarily change every block in the same way. A block may follow that filter, be fixed to a particular group or show the whole account. A label identifying its own group helps make that choice visible within the view.
Imagine the coordinator is looking at delivery vans while retaining a separate block for vehicles undergoing a particular review. That combination may be deliberate and useful. The difficulty begins if another person interprets all the figures as belonging to the delivery group. The composition does not necessarily need to be removed. Its relationship between groups needs to be visible and have a reason the person using it can understand.
A straightforward way to evaluate the view is to consider what should change when another general group is selected. Blocks that follow that filter should reflect the selection; those with their own group retain their scope. This check can explain a figure that does not change without immediately attributing it to an error or missing information. First establish which set of vehicles the block is actually representing.
The guide to arranging Plaspy dashboards explains group and configuration options. When several people discuss a view, include the group name and the block's purpose in the conversation. A screenshot alone may omit some of that context. Explaining what was being compared adds information that the image cannot necessarily convey, especially when a colleague is familiar with a different dashboard configuration.
Personalization belongs to the user working with the view
Dashboards and their block settings are saved to the user. Each subuser has their own dashboards and works with the devices they are allowed to access. Organizing a view in your account therefore does not distribute that design automatically to every colleague. Team coordination needs to distinguish an agreed way of working from a configuration that different people may arrange in different ways to suit their responsibilities.
This also explains why two colleagues can open Plaspy and find different compositions without any change having been lost. One may have chosen an operational view and the other a maintenance view. In addition, the general group filter is kept in that browser. When changing devices or environments, recognize the scope currently in view, even though your saved dashboards are available through your user account.
The fictional company can agree which questions each responsible person should be able to answer without requiring identical screens everywhere. What matters is a shared understanding of the information and a clear way to move from a figure to the relevant vehicle. A personal arrangement may work well as long as it does not silently change the group or interpretation on which a shared operational decision is based.
Personalization also does not grant additional permissions. If someone cannot access particular devices, adding or copying a block does not extend that access. The Dashboard is available to accounts and subusers with more than ten devices visible on the Map. The demo provides examples that can be viewed but not arranged. Understanding those conditions prevents a routine from being designed around the assumption that everyone sees exactly the same fleet.
A phone changes how a composition is read
A view that is comfortable on a monitor can read differently on a phone. On narrow screens, blocks occupy the full width and appear one below another. A relationship that seemed obvious on a desktop because two blocks were close together now depends on their vertical order and what fits on screen. It is worth reviewing that difference on the device that will actually be used during the work.
For someone checking information between other activities, finding the relevant block first may matter more than preserving a symmetrical layout. If they need to scroll a long way to connect two readings they always consult together, the order may deserve another look. There is no universal composition. The view should support that person's task within the available screen space and the way they can realistically consult it.
Changing devices can also affect the continuity of some counters. In the application, returning after leaving the page in the background for more than ten minutes causes a reload. Figures counted from opening start again, while daily figures follow a different calculation. Arranging a dashboard for mobile consultation therefore involves understanding what you want to observe and which period its figures represent, as well as making the blocks visible.
Before relying on a mobile view, picture the person opening it between activities. Consider which question they need to answer, whether they can recognize the group being shown and how far they must scroll to find the relevant context. That short review can reveal a layout problem that was difficult to notice while designing the dashboard on a larger display.
A composition is tested through a real task
After arranging the view, a useful test is to return to a familiar task. The operations coordinator can try to locate the vehicle involved in an outstanding query. The maintenance planner can check whether the available information for an upcoming review is easy to find. The purpose is to identify missing context, blocks that add little to that task and relationships between readings that are difficult to understand in the current arrangement.
Suppose the maintenance planner repeatedly returns to the operational dashboard to check a vehicle’s latest data. That pattern may reveal a missing reference in the maintenance view. It does not require copying every operational block: identify the particular question and consider whether including that reference makes inspection planning easier. Conversely, if a figure never contributes to preparation, retaining it simply because it came with the original copy can displace information that people actually use.
That review may lead to small changes: a clearer name, a block that follows the general group or a position that makes information easier to compare. Plaspy allows block changes to be undone while the page remains open, although not every action involving dashboards has that option. The documentation explains the distinction. Check it before deleting a view or assuming that every type of change can be recovered in the same way.
The configuration also deserves another look when the operation changes. Reorganized groups, a new vehicle type or a different responsibility can leave a previously useful view out of step with its purpose. Keeping it useful means checking whether it still answers the question for which it is opened. It does not necessarily mean adding another block whenever a new figure becomes available or keeping every earlier choice indefinitely.
If operations and maintenance currently share a crowded screen, begin by describing what each person needs to decide. Those two questions provide a basis for choosing what belongs in each view. The Dashboard guide explains the general behavior, and the block catalogue describes individual data. The appropriate composition is the one that supports your team's actual work and makes the meaning of the information clear to the person reading it.