A4TechLogo_Truecolor.png

AFour Solar keeps a tab on all of the running services at multiple production sites. It gathers metrics from solar sites, visualizes data and alerts on-site operators if things seem to go wrong.

hero-image.png

Operations Monitoring System

for clients in the solar energy domain

PROJECT HIGHLIGHTS

Timeline:  July-October '18

My Role:   UX Researcher and PM

Team:         1 UX Researcher (me), 1 UX/UI Designer, 
                       2 Frontend Developers, 2 Backend                                                       Developers, and Product Manager (me)

OVERVIEW

Obtaining insights about the health and performance of a system is often crucial in maintaining its reliability and security. One of the best ways to do this is to use a robust operation-monitoring system. This is where AFour Solar comes in.

EFFECTIVENESS

The product should be effective for both admins and site-operators and should be able to address all their needs. Coming up with an architecture that keeps their primary tasks from conflicting proved crucial for this.

Project Goals

The design should empower all users to achieve their goals as quickly as possible. Rethinking the information and visual hierarchy of the product made this happen.

EFFICIENCY

The product should be visually consistent across all devices to avoid users from feeling disbanded and confused. Creating components using the atomic design philosophy helped achieve this.

VISUAL CONSISTENCY

Formative Research

They say any research is better than no research. The strict timeline of the project called for a rapid research process and for that I did a simple thing: I talked to the users.

We knew that the product has two types of users: site administrators and on-site operators. Speaking to them helped us identify who they are and why do they use our system.

Yield Graph.png

Key Insights

1. FREQUENCY OF USE

Admins, more interested in cumulative health and performance of inverters, use it once or twice a day. On-site operators use it all through the day to keep track of incoming alerts.

2. PRIMARY TASKS

Admins generally are more focused on the trends in production and reporting features while operators are more likely to use the notifications and ticketing features.

3. BEHAVIORAL ATTRIBUTES

Operators show a goal-oriented behavior while using the system whereas administrators are browsers who look for anomalies in the functioning of the system.

Information Architecture

Wireframes

UI Design

Primary Screens