This page shows the design concept of the dashboard which is mostly based on the wiki page User Research.

Table of Contents

• 1. List of Dashboard Views
  • 1.1. Important views
  • 1.2. Optional views
• 2. Information Architecture
• 3. Design Mockup
• 4. Additional features
  • 3.1. Customizable Dashboard
  • 3.2. Email altert

1. List of Dashboard Views

These are the possible views of the dashboard:

1.1. Important views

1. Overview: collection of most important visualizations

2. Controlling: revenue, profit, vehicles capacity, fuel costs, maintenance costs, insurance costs, vehicles on down, vehicles with late deliveries

3. Downtimes: Average fleet downtime, maintained vehicles, idle (parked) vehicles, vehicles in traffic jams, vehicles in accidents, vehicles that (excessive acceleration, speeding, breaking, oldest vehicles (increased potential for problems), vehicles lifespan, vehicles' schedule, overview of maintenance status, average accidents

   3.1. Maintenance Calendar (future, past, show duration of maintenance service)

   3.2. Realtime Map (vehicle status, vehicle position, zooming feature)

4. Vehicles Table: vehicles-id, vehicle type, driver, build year, status, ...

   4.1. Drivers Table: name, driven vehicles, evaluation (speeding, acceleration, consumption, ...)

   4.2. Deliveries Table: delivery product, customer, scheduled time

1.2. Optional views

• Sustainability: excessive acceleration, speeding, breaking, carbon footprint, engine load
• Customer Service: most important customers, product delivery goals reached, late deliveries, vehicles on side routes

2. Information Architecture

Our User Research conclusion was that we have two Main Target Groups for using the dashboard. On one side the Fleet Manager and on the other side the decision Maker. This also means that both user groups need different representations to make business relevant decisions. That's why we thought about creating different views. This way, the decision maker can see all relevant controlling data such as cost, carbon footprint, revenue and profit on his home page. The Fleet Manager can see in the Downtimes View which status the vehicles in the fleet have and how likely they are to break down or when they have to be serviced and can then make his decisions. The vehicle view serves both target groups. There you can search for specific vehicles or drivers depending on the business case.

This show the information architecture for the dashboard:

3. Design Mockup

The design mockup was created with the mockup tool Balsamiq. It is based on the wiki page User Research.

Note: During the programming process, individual views were adjusted a little bit, because we noticed during this process that we could reduce a view. We decided to turn the Controlling View into the Home View and to add important key figures to the top of the maps. This creates more efficiency and is easier to understand and use from a usability perspective.

1. Overview

2. Controlling

3. Downtimes

3.1. Maintenance Calendar

3.2. Realtime Map

4. Vehicles Table

4.1. Drivers Table

4.2. Deliveries Table

Brainstorming These diagrams were created at the start of the design mockup to have all possibilities laid out

4. Additional features

3.1. Customizable Dashboard

It would be create if users could customize their dashboard based on their preferences. For example select, add, or delete certain data visualizations or create completely new views.

3.2. Email altert

If there are problems, users automatically get an email (e.g. vehicle stolen)