Electric Vehicle Fleet Dashboard: Metrics That Lead to Action

An electric vehicle fleet dashboard brings together the information you need to make specific fleet decisions: vehicles ready for service, charging sessions awaiting assignment, data gaps and upcoming tasks. Every metric should have a reporting period, a transparent calculation and a responsible person. These are what turn an overview into a working tool.

You do not need as many charts as possible to get started. Choose the questions your team needs to answer regularly. A dispatcher needs different information in the morning from the person preparing the charging invoice at month-end. A shared dataset can support several views, provided your software supports the necessary data and permissions.

Start with three operational decisions

First, describe the task each view should support. “Which planned jobs need clarification today?” calls for a different presentation from “Which charging sessions cannot yet be assigned to a vehicle?” The task determines which data is required and how current it needs to be.

For many electric fleets, three perspectives are useful:

• Daily operations: planned departures, available vehicles and unresolved requirements for a job.

• Charging administration: received charging sessions, missing assignments and cases awaiting review.

• Data maintenance: missing data deliveries, incomplete master data and changes that have not yet been confirmed.

State of charge, vehicle location or departure forecasts should only appear when suitable data is actually available. An older value needs a visible timestamp. When data is missing, the status is “unknown”. A green indicator based solely on the last known value would be a poor basis for a decision.

Give every metric a clear meaning

Create a short data sheet for each metric: name, operational question, formula, population, source, update schedule and follow-up action. This prevents two teams from using the same term to mean different things.

Make the denominator visible when showing percentages. “98 per cent complete” is of little use if nobody knows whether it refers to vehicles, charging sessions or individual data fields. The article on data quality in fleet software explains the rules for useful inputs.

Practical example: Reading a charging overview correctly

Illustrative calculation: During the period being reviewed, 240 charging sessions have been received. Vehicle assignments are confirmed for 228, while twelve remain unresolved. The confirmed assignment rate is 228 ÷ 240 × 100 = 95 per cent.

The dashboard therefore shows “12 unresolved assignments out of 240 received sessions”. It also shows the cutoff time for imported data. Ten sessions arriving later change the population; they are not proof that the team has performed worse.

To work through the unresolved list, the team needs the session identifier, charging time, available assignment information and responsible person. Once a case has been handled, the basis for the assignment is documented. A blanket notification to all employees would do little to improve the process.

Connect signals to a workflow

A yellow or red status needs a specific meaning. Define who takes ownership of the case, which information is checked first and when the next person is notified. For example, if a required vehicle assignment remains unresolved for more than three working days, the responsible administration team receives a task. This deadline is an operational decision, not a universal standard.

Distinguish receiving a notification from resolving the issue. “Seen”, “in progress” and “resolved” are different states. Document false alarms too. If a signal is repeatedly closed without action, review the data source, threshold or recipients.

For rules involving events and deadlines, see the further steps in the article on electric fleet notifications.

Check what the data actually supports

Vehicle data can provide information on use and charging. However, the fields available depend on how data is collected and connected. The US Department of Energy describes telematics as a possible basis for utilisation analysis and acquisition planning; this does not establish the availability of particular data in your system. Source: FEMP telematics guide.

Ask to see a real sample dataset for every planned display. Check data age, missing values and what happens when a connection is interrupted. An overview needs to present these situations clearly before it influences decisions in everyday operations.

Checklist for initial dashboard acceptance

Use five typical working days and one day with a data gap as test cases. Review the following points with the people who will use the dashboard:

1. Every display answers a named operational question.

2. The reporting period, data cutoff and calculation rule can be found.

3. Missing values remain identifiable as missing.

4. An unusual value leads to a list that can be worked through.

5. Case ownership and completion are defined.

6. The view shows only the information required for the task.

StromNow provides a central overview of charging sessions and their assignments in a fleet context. Discuss with StromNow for fleets which information you need today and which additional dashboard requirements should be assessed separately.