Electric Fleet Management

Foundational work on Oxium Energy’s Fleet Management Solution

Role

Product Design

Software used

Figma

Duration

1 month

Overview

This case study covers the development of a fleet management software solution for Oxium Energy, an early-stage startup focused on building products for the EV infrastructure. The project aims to provide a comprehensive tool for managing electric vehicle (EV) fleets, enhancing operational efficiency, and delivering real-time analytics. While the project remains in its conceptual phase, significant progress has been made in defining the problem, outlining solutions, and establishing a robust framework to guide future development.This project was initiated so that Oxium Energy can offer a complete, integrated solution to its clients and position itself as a key player in the EV ecosystem.

Goal

The goal is to create an efficient solution that optimises charging schedules, ensure smooth operations, and facilitate easy tracking and management of charging activities.

My Role

I was responsible for;

Brainstorming the concept.
Crafting user flows.
Developing the information architecture.
Creating initial user interface for the system

Despite the designs being at an early stage, my work established the foundational framework for the fleet management software, setting the stage for further refinement and development.

Limitation

The primary limitation encountered during this project was the absence of a detailed process. Due to the startup's early-stage nature and time constraints, we adopted a rapid, experimental approach to design, focusing more on getting a working prototype rather than iterating through multiple design versions. This approach, while effective for quick experimentation, presented challenges in ensuring that all issues were anticipated and addressed.

UX Design Process

The design process was characterised by a focus on core functionalities and flexibility in design. Given the constraints, we prioritised solving key user problems, ensuring that the foundation was solid, making room for further improvisation.

Identifying and Defining

How might we

Who

Entities involved:

What

When

Where

Note: CMS - Charging management system

Why

Task flow

Identifying use cases

Some situations among the n no.of use cases developed;

Click on the link below to view an elaborate brainstorming for the product;

https://www.figma.com/board/tjWAHXCdXL7CUo14t1MUdd/FLEET-MANAGEMENT_PRELIM?node-id=0-1&t=zgI59Dpyb9tVVUIz-1

Secondary research

Competitor analysis

Identified Product categories

In our approach, we embraced a strategic trial-and-error methodology, deliberately focusing on implementing the minimal viable features essential for the product's initial functionality. This allowed us to prioritise the core elements needed to launch and sustain the product, ensuring it met the immediate needs of our users. By doing so, we created a flexible foundation that could easily adapt to changes based on real user feedback.

Overview

Goal

The goal is to create an efficient solution that optimises charging schedules, ensure smooth operations, and facilitate easy tracking and management of charging activities.

My Role

I was responsible for;

Brainstorming the concept.
Crafting user flows.
Developing the information architecture.
Creating initial user interface for the system

Despite the designs being at an early stage, my work established the foundational framework for the fleet management software, setting the stage for further refinement and development.

Limitation

UX Design Process

Identifying and Defining

How might we

Who

Entities involved:

What

When

Where

Note: CMS - Charging management system

Why

Task flow

Identifying use cases

Some situations among the n no.of use cases developed;

Click on the link below to view an elaborate brainstorming for the product;

https://www.figma.com/board/tjWAHXCdXL7CUo14t1MUdd/FLEET-MANAGEMENT_PRELIM?node-id=0-1&t=zgI59Dpyb9tVVUIz-1

Secondary research

Competitor analysis

Identified Product categories

Design and Development Process

My process before developing the UI screens involved organising and listing down contents in detail on every page and creating rough wireframes for it.

While developing the wireframes , a clear picture stared shaping up regarding the user interface for each of the screens.
Based on this, iterations were made in the Information architecture and Site map.

Product Features

Real-time monitoring

The "Active Session" section plays a critical role in monitoring and managing ongoing vehicle charging. This section was developed through a comprehensive design process that began with site mapping, followed by wire-framing, and culminating in the final mockup.

There were two considerations;
- Monitor charging of vehicles in the fleet.
- Monitor the battery level of vehicles.
We visualised all kinds of status indicators required and how these would interact within the system.
For doing this, we needed information on;
- Vehicle location.
- Information about the driver with the vehicle.

Charging Management

This involves assigning vehicles to appropriate charging stations based on their battery status and the proximity of the available charging stations.

Task involved;

Track the Fleet.
Assign Charge Stations.

User Flow involved for the process is depicted below:

View Fleet Status: Begin by reviewing the battery levels and statuses of all fleet vehicles.
Select Vehicle: Choose the vehicle(s) that need charging based on the criticality of their battery levels.
Assign Charging Station: Select an appropriate charging station from the list, considering the vehicle’s location and the station’s availability.
Confirm Assignment: Once a vehicle is assigned to a charging station, the system will track the charging process and update the vehicle’s status accordingly.

Vehicle Management

This section is designed to provide comprehensive details about each vehicle within the fleet, helping administrators and managers keep track of vital information and make informed decisions.

Task involved;

Tracking the Fleet.
Assigning Charging Stations.
Monitoring Vehicle Health.

Payment management

The wallet feature is designed to serve as a centralised financial hub within the fleet management system, enabling seamless and efficient management of monetary transactions. This section is accessible to both drivers and administrators, ensuring that the financial operations are transparent, trackable, and easy to manage.

Key Features:

Centralised Wallet Access
- Functionality: The wallet is a shared resource that drivers can access for transaction purposes, while administrators or concerned managers have the authority to deposit funds into this wallet. This centralisation ensures that all financial activities related to fleet operations are streamlined and managed from a single point.
Primary Call-to-Action (CTA) - "Add Money"
- Design and Placement: The wallet section features a prominent CTA labeled "Add Money," designed to allow administrators to quickly and easily deposit funds into the wallet.
Analytics Dashboard
- Overview and Insights: The wallet section includes a comprehensive analytics dashboard that provides an overview of the wallet’s financial activities. This includes key metrics such as the total amount available, money debited, and money credited.
Transaction History
- To ensure transparency and easy tracking, all transactions carried out through the wallet are recorded in a detailed transaction history.
- Filtering and Sorting: The transaction history also allows for filtering and sorting by different parameters, such as date or transaction type, transaction status etc.

Site Map:

Designed a comprehensive site map to visualize the app's structure and ensure logical navigation pathways.

Design system

Future considerations

Through continuous user testing, we aim to derive valuable insights that will guide our iterative design process.This approach not only ensured that the product remained relevant and user-centric but also demonstrated our commitment to evolving the product intelligently, adding new features only when they truly added value. In essence, our process was as much about learning and adapting as it was about building, resulting in a product that is both practical and poised for growth.