A self-initiated redesign of an energy grid analytics tool. Same data, a calmer way to the asset that matters.
This is a self-initiated concept, not a client project. I analysed a public screenshot of gaia, the digital twin platform by Enersis, against eight UI design principles, then designed new screens for its asset analysis in Figma. The original screenshot comes from the Enersis website. Enersis was not involved and has not reviewed this work.
Client
Self-initiated · not a client project
Year
2025
Services
UX analysis · Concept · Interface design

Redesign concept: asset analysis, desktop
New screens designed in Figma, map visual generated with Midjourney, sample data
01 Context
A digital twin for the energy transition.
Enersis builds gaia, a platform that brings data on grid infrastructure, buildings, energy and climate together in one digital twin. Municipalities and utilities use it to make bottlenecks visible, simulate scenarios and plan the expansion of renewables and the grid. That is a lot of information, and the interface carries much of it at once. I wanted to see how much calmer one core workflow, the analysis of a single grid asset, could get without losing any of the data.
02 Analysis
Eight principles, one screenshot.
The starting point was a public screenshot of the gaia asset analysis on the Enersis website. I reviewed it against eight UI design principles: discoverability, affordance, comprehensibility, responsive feedback, predictability, efficiency, forgiveness and explorability, plus contrast, alignment, repetition and proximity. What works: the 3D map makes assets easy to find, and the scrolling side panel reads clearly. What could be better: settings, time range and measured object compete for attention, several different input styles create a false hierarchy, the iconography feels restless, and header and footer take up a lot of space.

Annotated analysis of the original screen
Original screenshot from the Enersis website, my annotations
03 The redesign
Find the station first, then the numbers.
In the redesign, the asset analysis starts with a search and a short list of the stations in the current map view, each with its name and description. Selecting a station opens a heatmap of load values over time: the maximum load across phases L1 to L4, by hour and calendar week. Peaks are visible at a glance before you dig into a single day.

Station detail with load heatmap
Redesign concept in Figma, sample data
04 Design
Quiet interface, loud data.
Navigation moved into one light sidebar with plain labels: dashboard, infrastructure, analytics, data, connections, time analysis, assets, reports. One input style, one button style, generous white space. Colour is reserved for the data: green for load intensity in the heatmap, red markers for assets on the map. The map stays large and keeps the spatial overview that already worked well in the original.
05 The details
From the whole area to a single phase.
A static and a dynamic mode switch between a fixed selection and free exploration on the map. Numbered markers connect positions on the map with the list. In the detail view the heatmap condenses into a compact strip, transformers can be switched one by one, and a line chart shows the current per phase, with exact values on hover.

Detail: transformers and current per phase
Redesign concept, sample data

Dynamic mode with numbered markers
Redesign concept, sample data
06 Before and after
Same task, less noise.
On the left, the original asset analysis as shown on the Enersis website. On the right, my redesign of the same step. This is an outside-in concept based only on public material: I had no access to the product, its users or its data. It is a proposal to start a conversation, not a tested solution.
Left: original, public screenshot from enersis.ch. Right: redesign concept
Self-initiated, not affiliated with Enersis
Next case
uhub Social Inbox
Every comment, DM and mention from every channel in one inbox, designed and built by me.
Work with nanquim
Planning a digital tool for your organisation?
I design and build it in one go, from the first screen to the database.
