Reimagining a Fire & Life Safety Control System
Original Hardware Control Panel
Redesigned Touchscreen Interface
From hardware-constrained control panel to touchscreen-first life-safety platform.
Notifier's fire and life-safety control platform had accumulated decades of technical complexity without producing a current map of its own structure. Its architecture reflected hardware-era engineering logic, device hierarchies, and layered configuration rules — not how operators respond to events, locate devices, or navigate under pressure.
I led the UX redesign, reconstructing the system's underlying architecture and translating its engineering logic, device hierarchies, system states, and hardware-era navigation into an operator-facing product structure organized around events, points, status, and action. The work required interpreting a dense, fragmented legacy model and producing a shared structure that design, product, and engineering teams could build from.
A retrospective audit of project artifacts indicates that I consolidated approximately 128 unique functional nodes into 66 task-oriented destinations—a 48% reduction in information-architecture complexity—while preserving the platform's core operational and programming capabilities.
The Challenge
Original Hardware Interface – Key Components
The panel required operators to navigate life-critical functions through a small LCD, fixed hardware controls, soft keys, and a programming keypad. New capabilities had been layered in over time without a clear organizing model.
- Critical functions were buried in deep navigation paths
- Operators relied on memorized sequences and changing soft-key behavior
- The interface reflected implementation logic more than operator decision-making
From Multi-Step Navigation to Single-Screen Response
Before: Multi-step alarm response
After: Single-screen alarm response
| Before | After |
|---|---|
| ~6–7 actions to acknowledge | 1 in-context action |
| 2+ context shifts | 0 screen changes |
| 1 event visible at a time | Multiple events visible together |
| Repeated Next/Previous actions | 1 direct selection |
Action counts are approximate; exact paths varied by event position and whether detail was reviewed.
The redesign translated a fragmented hardware-era command sequence into a persistent response state where alarm priority, event context, and acknowledgement remained visible together.
Reconstructing and Reframing the System
The first design problem was interpretive: no current model of the system existed. Before interface design could begin, I reconstructed its features, menu paths, duplicate functions, and access hierarchies into a shared functional model that made the platform understandable across design, product, and engineering.
New Information Architecture
Legacy architecture
Redesigned architecture
The reduction reflects a translation from fragmented technical paths into recognizable product domains — not the removal of necessary capability.
Why the legacy structure was difficult to use
Buried individual tasks
Common tasks were buried across multiple branches.
Sequential list navigation
Operators navigated events sequentially using Next/Previous.
The largest reductions came from separating routine work from specialist programming and consolidating settings, reporting, and duplicate paths. Event-response logic changed less because required safety-critical states were preserved.
Testing Led to a Point-Centric Model
Early concepts explored task-first entry points, but testing showed that operators oriented themselves around affected system points. They first identified the detector, module, zone, node, or location involved, then determined what action to take.
I translated that observed behavior into a point-centric interaction model in which the selected point, its status, and its available actions stayed together. The architecture clarified where capabilities belonged; the point-centric model clarified how operators accessed them, replacing sequential Next/Previous navigation with visible point lists and direct selection.
ObservedOperators oriented around affected points — detectors, modules, zones, nodes — rather than abstract task categories.
ChangedShifted from task-first entry points to a point-centric interaction model.
ResultPoint lists, point details, and available actions remained connected within one workflow, without losing orientation.
Point list presentation
Scrolling list of points within the selected Node, Loop, or Zone — a contextual set within a region of the system.
Point selection
Selecting a point surfaces its status, detail, and available functions in context.
Point-specific functions
Point detail expands inline with status, information, and relevant actions. Task is performed without leaving the list view.
Updated point status
Operator returns to the updated list. Context and orientation are preserved.
The point-centric model converted Next/Previous navigation into direct list selection — point, status, and action remaining together without context switching.
The Resulting Product
The translated architecture became a cohesive operational interface — one where system state, event priority, and point-level detail are organized by how operators work rather than how the hardware is built. Persistent navigation and status give operators continuous awareness. A prioritized event list surfaces what matters without requiring menu traversal. Each row carries enough context to orient the operator before they act.
Impact
For operators
Less system structure to learn, with event context and actions kept together throughout response workflows.
For the product
A retrospective audit of project artifacts indicates a 48% reduction in information-architecture complexity — 128 destinations consolidated into 66 — while preserving core operational and programming capability.
For the team
A shared language and architecture that design, product, and engineering could use to discuss, prioritize, and extend the platform.
Reflection
The most valuable work happened before the screens. I reconstructed an undocumented safety-critical system, translated it into a measurable, test-informed product architecture, and carried that model through research into a point-centric interaction framework. The result preserved the depth of a life-safety system while making that complexity more usable for operators and more actionable for the teams building it.