Case Study · 2026
NDA Platform Summary
One operating model for assets, incidents, and governance
Assets. Incidents. One model.
RoleLead Product Designer
ScopeAsset Modeling · Incident Management · Reporting · Administration · Design System
DomainIndustrial IoT / Energy Infrastructure
PartnerBaker Hughes & Sibintek (GE Predix)
Platform Montage
Overview interface
01 · Domain Discovery
Mapping Industrial Workflows
The platform handled critical operations, but workflows were split across services and mirrored system architecture instead of operator mental models.
Operators, field engineers, and administrators needed one language for assets, alerts, permissions, and reports.
To redesign the experience, I:
- 01/Defined operator, engineer, and admin archetypes.
- 02/Mapped workflows from alert to maintenance closure.
- 03/Linked assets, alerts, permissions, and reports.
- 04/Built modular IA for future platform growth.
Ecosystem Mapping Diagram
Asset Registry (Physical)↔Telemetry Signals (IoT)
Incident Triage (Logic)↔Governance Policies (Admin)
Incident Response Journey Map
Stage 1Telemetry Alert
Stage 2Asset Hierarchy Lookup
Stage 3Triage & Escalation
Stage 4Resolution Log
02 · Pillar 1
Asset Modeling Digital Infrastructure Map
Asset Modeling became the platform foundation: a digital map of equipment, facilities, and dependencies.
I linked physical assets to sensor models so operators could trace failures through the network.
What I Designed
Asset hierarchiesRelationship managementAsset lifecycle workflowsConfiguration interfacesValidation states
Embedded prototype
Telemetry Studio
Loading live prototype
If the embed is blocked by the prototype host, open it in a new tab.
03 · Pillar 2
Incident Management From Alert to Resolution
Operators needed a structured path from alert to resolution.
I replaced noisy alert feeds with investigation flows that combine history, telemetry, and work orders.
Key Outcome
Faster triage with a repeatable operating process.
What I Designed
Incident creationTriage workflowsEscalation pathsStatus managementResolution tracking
04 · Pillar 3
Operational Visibility Dashboards & Reports
Teams had telemetry, but not a clear view of asset performance.
I designed dashboards and reporting flows that turned sensor data into decisions.
Highlights
Performance dashboardsAsset monitoringKPI trackingTrend analysisExecutive reporting
Primary operational dashboard views
Operational Data
BackAlex ShternUfachim21.10.21 13:30 (Msc)⌕◌
20.09.21-20.10.21Updated 21.10.21 05:33:12
Investigation Statistics
QuantityIncidentsFalseIn ProgressNew
Reliability statistics
Quantity96%Average Performance
↓-11,2%Reliability Trend
Operational Data
BackAlex ShternUfachim21.10.21 13:30 (Msc)⌕◌
20.09.21-20.10.21Updated 21.10.21 05:33:12
Incidents by Measurement Systems
QuantityInvestigation Statistics
QuantityIncidentsFalseIn ProgressNew
Reliability statistics
Quantity96%Average Performance
↓-11,2%Reliability Trend
Live signal feed
A filterable sample of the telemetry events these dashboards are built from.
Showing 14 of 14 events
- EVT-882132026-03-14 06:12:04ZSCADAPUMP-P114 — Vibration threshold exceededEscalated
- EVT-882142026-03-14 06:14:41ZDigital TwinTRF-06 — Model drift vs. live sensor feedInvestigating
- EVT-882152026-03-14 06:20:09ZAsset MgmtCMP-22 — Maintenance window scheduledScheduled
- EVT-882162026-03-14 06:24:57ZObservabilityGATEWAY-04 — Ingest latency above SLAMonitoring
- EVT-882172026-03-14 06:31:18ZGovernanceRULE-SET-A12 — Automation rule deployed to prodDeployed
- EVT-882182026-03-14 06:38:52ZSCADAVALVE-118 — Pressure differential spikeEscalated
- EVT-882192026-03-14 06:44:03ZDigital TwinPUMP-P114 — Digital twin resynced with asset registryResolved
- EVT-882202026-03-14 06:51:27ZAsset MgmtTRF-06 — Dependency hierarchy updatedUpdated
- EVT-882212026-03-14 06:58:14ZObservabilityDASH-KPI-02 — Anomalous trend in throughput KPIUnder review
- EVT-882222026-03-14 07:05:36ZGovernanceROLE-OPERATOR — Permission scope changedAudited
- EVT-882232026-03-14 07:11:49ZSCADACOMP-09 — Temperature sensor offlineField dispatch
- EVT-882242026-03-14 07:19:22ZAsset MgmtVALVE-118 — Asset record reclassifiedUpdated
- EVT-882252026-03-14 07:26:08ZObservabilityGATEWAY-04 — Weekly report export completedDelivered
- EVT-882262026-03-14 07:33:45ZGovernanceRULE-SET-B03 — Rule rollback triggered by operatorRolled back
05 · Pillar 4
Industrial Rule IDE Governance Layer
Industrial IDE for digital twin operations.
A model-driven workspace connecting telemetry, asset relationships, and automation logic.
It sits between SCADA, Digital Twin, Asset Management, and Observability.
Operational intelligence flow
SCADA
Digital Twin
Asset Mgmt
Observability
Industrial Rule IDE
Unified model, logic, and operations layer
01
Monitor
Asset health
02
Model
Relationships
03
Define
Automation logic
04
Investigate
Incidents
05
Deploy
Rules safely
06 · Design Infrastructure
Design System Shared Product Foundations
I led a shared design system to support multiple industrial products and teams.
We standardized tables, filters, telemetry charts, warnings, and layout rules into reusable patterns.
Faster deliveryReusable layouts for browser prototypes
Consistent UXOne language across microservices
Engineering collaborationTokens connected design to implementation
Rapid validationOperators tested flows before build
07 · Impact
Platform Impact
Before
Fragmented tools, hidden dependencies, inconsistent UI.
After
One operating model for assets, incidents, reporting, and governance.
01
Unified
Asset, incident, and reporting flows
02
Faster
Reusable patterns for product teams
03
Safer
Inline hierarchy and dependency context
04
Scalable
Shared standards for future modules