top of page

Overview

Sensproducts® is a web-based B2B IoT application that ensures digital intelligence for Siemens energy assets. By securely collecting and transmitting sensor data, it enables operators and engineers to monitor, manage, and optimize transformers and other assets in real time. The platform empowers users with dashboards, diagnostics, alarms, analytics, and reporting tools to ensure reliability, reduce downtime, and optimize energy operations.

Problem Statement

Energy operators and engineers lacked a centralized, intuitive system to monitor and manage Siemens transformers deployed globally. Existing processes were siloed, with raw data difficult to interpret, leading to:

  • Delays in detecting performance issues or failures

  • Reactive (instead of proactive) maintenance

  • Time-consuming compliance reporting

  • Limited ability to simulate “what-if” scenarios for risk planning

Goals

  1. Provide operators a real-time overview of all assets across geographies.

  2. Create a single asset view for configuration, monitoring, diagnostics, and simulations.

  3. Enable alarm management workflows (acknowledge, act, resolve) to reduce downtime.

  4. Deliver analytics & reporting for smarter decision-making and compliance.

  5. Build an interface that simplifies complex IoT data into actionable insights.

My Role

User Research, Wire-framing, Information Architecture, Interaction, Visual design, Prototyping & Testing

Project Duration

130

Weeks

150+

App screens

Tools Used

Figma

XD

Miro

Google Form

Zoom

Design Process

Discover

Difine

Ideate

Design

Test

User Research

Empathy Map

User Flow

Wireframes

Feedbacks

Test & Iterate

Test & Iterate

User Interviews

User Personas

User Journey Maps

Information Architecture

Hi-Fi Designs

Prototype

Conclusion

01 DISCOVER

Quantitative Analysis

During the initial stages of the project, I collaborated with Product/Project Managers (PRMs) to gather insights into general user behavior and their thought process around the application and its core concepts. Since this is a B2B platform and I did not have direct access to end-users, I worked through PRMs who engaged with customers. Questionnaires were also shared with selected customers to capture their feedback on the product’s functionalities and overall expectations

​

Couple of questions shared in the questionnaire:

​    

  • How long does it take users to locate a specific transformer in the dashboard?

  • What percentage of users can successfully acknowledge an alarm without errors?

  • How many errors (e.g., misconfigured alarm thresholds) occur during setup?

  • What is the average number of steps/clicks taken to complete common tasks (e.g., adding a sensor, configuring alarm rules)?

  • How often do users access the simulation and analytics features?

  • What is the System Usability Score (SUS) before redesign?

  • What percentage of users export reports successfully on the first attempt?

  • How many alarms per day are being generated, and what percentage are acknowledged within SLA?

Qualitative Analysis

For the qualitative analysis, I conducted discussions with Product/Project Managers (PRMs) to better understand recurring user pain points, usability challenges, and feature adoption issues. Since direct access to end-users was not possible due to the B2B nature of the product, I relied on PRMs who regularly interacted with customers and gathered their feedback. This helped me capture valuable insights about real-world challenges, unmet needs, and expectations from the platform.”

​

  1. How easy or difficult is it to understand the dashboard at first glance?

  2. What challenges do you face when trying to configure alarm rules?

  3. When you see multiple alarms, how do you decide which one to act on first?

  4. How useful do you find the analytics tab for your daily decision-making?

  5. Have you ever used the simulation feature? If not, why?

  6. What kind of reports would be most valuable for your role (Engineer vs. Owner vs. Admin)?

  7. What’s the most frustrating part of monitoring or configuring transformers in the current system?

  8. If you could change one thing in the platform, what would it be?

User Journey Mapping

I created a customer journey map based on user research to better understand the key pain points, challenges, behaviors, and overall journey users may have when making appointments. also, make a list of the opportunities

Power Sbbstation monitoring (1).png

03

 IDEATE

User Flow

A user flow is a path taken by a typical user on an app or website so they can complete a task from start to finish, The goal is to map how users achieve a specific goal as they move through a product

Power substation monitoring application.png

Information Architecture

Information architecture organizes and defines the overall structure of the app or the site & it provides a high-level view of a product. The goal of IA is to arrange content so that users can quickly become familiar with the product's functionality and find whatever they need.

Information Architecture (imli) (2).png

04

 DESIGN

Wireframing

As this was a sensitive enterprise project (Siemens Energy IoT platform), I am unable to disclose original designs or mockups because of strict company security policies. Instead, I have documented my research approach, design rationale, user journey mapping, and usability testing insights to showcase my contribution.

Hi-Fi UI Design

As this was a sensitive enterprise project (Siemens Energy IoT platform), I am unable to disclose original designs or mockups because of strict company security policies. Instead, I have documented my research approach, design rationale, user journey mapping, and usability testing insights to showcase my contribution.

05

 TEST

Usability Test

I evaluated how effectively Engineers, Owners, and Admins can navigate the platform, complete asset management tasks, and respond to alarms/alerts.

Method:

  • Remote moderated usability testing (due to B2B enterprise context).

  • Conducted with proxy users (Product Managers, internal SMEs, PRMs) since direct end-users weren’t available.

  • Test sessions focused on critical workflows.

Assigned Tasks & Scenarios

1. Check Equipment Health

  • Task: Log in and view the health status of transformers in the dashboard.

  • Goal: Determine if users can quickly understand the overall system state.

​

2. Respond to an Alarm

  • Task: A critical fault alert appears. Acknowledge it and check details.

  • Goal: Assess if users can effectively view alarm details and next steps.

​​

3. View Historical Analytics

  • Task: Explore the analytics section to check device uptime and fault trends.

  • Goal: Confirm that long-term insights are discoverable and useful for planning.

​

4. Generate Compliance Report

  • Task: Export a monthly performance and maintenance report.

  • Goal: Test ease of finding reporting features and generating usable reports.

Findings

1. Strengths

  • Users appreciated the central dashboard and real-time view of multiple devices.

  • The alarm acknowledgment flow was straightforward and reduced response time.

  • Reporting and export functionality was highly valued for audits.

​

2. Pain Points

  • Some users struggled to locate specific device data (navigation needed clearer IA).

  • Analytics graphs were too data-heavy; needed simplified visualisations.

  • Report customisation was limited — users wanted filtering by date/asset.

​

3. Improvements Identified

  • Simplify Information Architecture (group alarms, devices, reports more clearly).

  • Add role-based views (Owner vs Engineer vs Admin).

  • Improve visual hierarchy in analytics (highlight KPIs, trends).

bottom of page