Skip to main content

Energy Asset Monitoring · Siemens Energy

Unifying fragmented asset experiences into one scalable monitoring platform

Separate monitoring interfaces for transformers, circuit breakers and other assets made the portfolio hard to scale and inconsistent to use.

Energy Asset Monitoring is an industrial IoT platform that helps engineers and operators monitor critical electrical assets, understand equipment conditions and investigate operational issues.

I led the UX — from discovery with product-line managers and domain experts to information architecture, interaction design and developer handoff.

Company
Siemens Energy
Product
Energy Asset Monitoring
Role
Lead UX Designer
Domain
Industrial IoT / Electrical Asset Monitoring
Users
Engineers, operators and maintenance teams
Platform
Enterprise web application
Overview

One consistent experience, without losing technical depth

When I joined, each electrical asset type had its own monitoring interface, with its own navigation, data structures and specialized requirements. The question that framed the work was:

How could we create one consistent experience while preserving the technical depth of different electrical assets?

Challenge

Fragmented products, specialized requirements

Different product lines had specialized requirements, navigation structures and technical data. Requirements were ambiguous: it was not yet defined what should be shared and what had to remain equipment-specific.

One major discovery was that users needed a fleet-level overview in addition to detailed monitoring of individual assets.

01

Users

Recognize which equipment needs attention, then investigate specific asset conditions and history.

02

Business

Scale one platform across asset types instead of maintaining separate experiences.

03

Technical

Preserve equipment-specific measurements and diagnostics within a shared structure.

An earlier transformer-specific interface — each asset type had its own separate experience.
Approach

Mapping what was common and what was essential

I proactively engaged more than ten product-line managers, domain experts and engineers to understand what was common across products and where equipment-specific behavior was essential.

Direct access to end users was limited in this B2B environment, so I worked through stakeholders who regularly engaged with customers. Customer questionnaires were also shared through project stakeholders.

I mapped shared and asset-specific needs, structured the information architecture and iterated designs through reviews with domain specialists and engineers.

Understanding the people behind the monitoring workflows

Persona journey map for an asset owner: tasks, feelings and improvement opportunities from checking equipment status to reviewing substation performance.

Structuring a scalable monitoring experience

Application information architecture: fleet-level entry points lead into equipment drill-down, shared monitoring, diagnostics, analytics and reporting.
Solutions

Key design decisions

Decision 01

A modular architecture

Problem
Each asset type had its own interface, so shared tasks behaved differently from product to product.
Alternatives & constraints
Fully separate products were costly to scale; forcing everything into one generic view would have lost essential equipment detail.
Decision
I proposed a modular experience: a shared platform with common capabilities — fleet visibility, navigation patterns, equipment status, notifications and reusable interface elements — plus specialized modules for equipment-specific monitoring and diagnostics.
Rationale
It balanced consistency, scalability and technical flexibility.
Shared platform
Common capabilities
  • Fleet visibility
  • Navigation patterns
  • Equipment status
  • Notifications
  • Reusable UI elements
Equipment-specific modules
  • Transformers
    Equipment-specific monitoring
  • Circuit breakers
    Equipment-specific monitoring
  • Diagnostics
    Specialized technical analysis
  • Further asset types
    Added as modules
Conceptual reconstruction of the modular UX approach — not an original design deliverable.
Decision 02

Fleet-to-asset investigation

Problem
Users needed to see which equipment across many locations needed attention, then reach the technical detail behind it.
Decision
The interface supports movement from fleet-level status to specific asset details, through complementary table and map views. Status, connectivity and notification awareness sit at fleet level; equipment drill-down leads into dedicated monitoring views.
Rationale
Keeping deep technical data in asset views stops the fleet overview from becoming overloaded.
Fleet-level monitoring brings equipment status and notifications into a geographic overview.
Equipment-level monitoring connects fleet-wide visibility with detailed diagnostic information.
Decision 03

Lightweight notification-state management

Problem
Expert interviews identified the need to understand how notifications were being handled.
Alternatives & constraints
A complete workflow-management system introduced cost and implementation concerns.
Decision
I proposed a lighter state model — New → Noted / Disregarded. Disregarding a notification required capturing a reason.
Rationale
It provided clearer awareness without requiring a complete task-assignment system.
Result
The solution received positive stakeholder feedback and informed reusable notification patterns.
Decision 04

Shared UI components

Problem
The team initially had brand guidelines rather than a mature product design system.
Decision
I worked with developers to establish shared components and interaction patterns used across the platform.
Rationale
Shared patterns kept modules consistent as new asset types were added. This was a shared component foundation, not a fully mature design system.
Reusable component patterns keep tiles, tabs and status indicators consistent across asset types.
Configurable analytics let engineers compare trends without leaving the monitoring context.
Outcome

A shared direction across asset types

What was delivered

  • A shared modular direction across asset types.
  • Fleet visibility linked to asset-level details.
  • Reusable notification patterns.
  • Component consistency and closer engineering collaboration.

Reflection

The hardest part was not the screens; it was deciding what should be common and what had to stay specialized. Making that line explicit with product-line managers turned a set of separate products into one platform direction.

Past project at Siemens Energy. Brand and data points have been anonymised for confidentiality.

Next project

SIMIT Rapid Tester

Back

Selected Work