Skip to main content
Case Study 02
transportation

Railway Back Office

Reduced operator task time by 40% and onboarding time by 60%, by redesigning a legacy railway backoffice system with a component-driven design system aligned to Siemens brand standards.

period
Rail Transport
context
Safety-Critical
role
Solo Lead
tags
Enterprise UXDesign SystemWCAG
The engine and the code it reportedEight buckets: same code, same pigeonholeHold messages, e.g. Bulletin 2231's track windowHow the redesigned back office reads the line, as a sorting desk. The legacy server showed raw codes like CSX0256; the new console translates every report into plain language and files it where an operator expects to find it, so the same code always lands in the same place. Operator task time dropped by 40% and onboarding time by 60%. Trains, codes and messages here are illustrative.
−40%
operator task time
−60%
onboarding time
100%
WCAG 2.1 AA
1
solo lead
How Might We
// hmw
redesign a complex, legacy backend tool, where every UI decision has safety implications, without disrupting active railroad operations?
The Problem

The PTC Backend Admin Server was a native C++ application with no design standards, cryptic error codes like CSX0256, and zero documentation for onboarding. A train collision made digital modernization non-negotiable. The stakes weren't abstract.

The primary competitor (GE) had already set a high bar for usability. The existing interface couldn't just be iterated on. It needed to be rethought from the ground up, while operators continued to rely on it daily.

Visual Context
Design system reference sheet — colors, UI elements, typography
Design system reference — colors, UI elements, typography scale

The underlying architecture documents and Figma prototype maps are client-confidential and withheld. The interactive recreation further down shows the resulting interface without any client-identifying detail.

The Solution

Introduced Scrum to a team that had never worked with it, establishing rhythm and predictability for a high-stakes redesign. Built a Material Design UI kit aligned to Siemens brand standards and Flutter-ready component specs using Atomic Design principles.

Dark and light themes. A fully navigable prototype for desktop review. And a separate tablet solution for field workers who needed the same system in motion, on trains, on platforms, in variable light conditions.

System Architecture · D3

Component Library as Design Hub

Force-directed graph showing how Material Design, Siemens brand standards, WCAG 2.1 AA, and Atomic Design converged into a single component library, which then radiated out to screens, themes, and delivery platforms. Drag any node.

Legacy system Input frameworks Component hub UI screens Platforms
Key Decision
// design-decision

Flutter had no mature desktop export tool. Rather than block delivery, I designed for web-resolution parity and used Figma + Zeplin for handoff, documenting the gap explicitly for the next phase. Transparency about tooling constraints is a design decision.

// reflection

Doing this solo was the biggest constraint and the biggest lesson. I learned to ruthlessly prioritize what required design leadership versus what could be iterated through developer feedback. The output was cleaner for it, too. Fewer opinions meant fewer compromises.

On Site Collab · POC for Expo

One Week, One MVP, One Global Stage

During a week-long on-site sprint, the team delivered a fully functional MVP for the C&S Transportation Signals Expo 2021. The prototype ran live on both a wall-mounted display and a ruggedized tablet, drawing significant interest from railroad operators and sparking the broader vision of merging the BOS tablet capability with the existing desktop platform.

Event photography withheld. The on-site booth and demo stations were client-branded assets outside the scope of what can be shown publicly here.

Design System

BOS Tablet Design System

The Siemens Trainguard PTC BOS interface required a purpose-built component library designed for operators working in live railroad environments: dense data tables, real-time status indicators, and multi-level navigation across BOS nodes, subdivisions, and locomotives.

The palette is anchored in Siemens Petrol as the structural foundation, with a bright Interactive Teal reserved for live status and active selections. The dark sidebar creates clear spatial hierarchy, letting operators instantly orient within a complex information architecture without visual noise.

All components were designed for tablet-first use, with generous touch targets, high contrast ratios for varying light conditions, and explicit active/inactive/error state coverage across every element.

Figma Variables Design Tokens Tablet-first WCAG AA Zeplin Handoff Status System
// drag to reorder
A three-tier spatial hierarchy: dark structure, teal interaction, light surface.
Illustrative Recreation

How the Console Felt to Use

The real prototype and production screens are client-confidential. Below is an interactive recreation built for this portfolio, using the same interaction patterns and information density, but with generic labels and fictional data.

Illustrative recreation: interface rebuilt from memory in plain HTML/CSS/JS. Product name, org names, and data are fictional.

TrackWatch Rail Ops Console
All Status ▾
Work Zone Bulletins
BulletinSubdivisionTrackWindowStatus
▤2214NORTH LINEMAIN08:00–16:00Unassigned
▤2231RIVER JCTMAIN08:00–16:00Assigned
▤2258NORTH LINESIDE-210:00–18:00Unassigned
Five Current Sources of Train Information — PTC context slide showing the problem space before digital transformation (2021)
Five Current Sources of Train Information — PTC context slide showing the problem space before digital transformation (2021)