xScale 360 · Enterprise data-centre operations
A product system for IBX Operations Leads to understand what is happening, identify what matters, and act without navigating across fragmented operational systems.
01 · Context
IBX Operations Leads worked across multiple operational systems to understand the state of physical data-centre infrastructure. Information was available, but fragmented across tools, alerts and operational workflows.
The user doesn't think in terms of individual systems. They think in terms of operational state, exceptions, impact and action.
The interface needed to answer these questions in sequence, rather than expose the complexity of the systems underneath.
The operational challenge was not finding more data. It was connecting signals, context and impact quickly enough to decide what needed attention.
02 · The product model
Instead of exposing the structure of the underlying systems, xScale 360 organised information around the decisions the Operations Lead needed to make.
Instead of organising the interface around the systems generating the data, I organised it around the decisions the Operations Lead needed to make.
The product became an abstraction layer between fragmented systems and operational decisions.
Each step reduced the gap between fragmented operational information and the decision the Operations Lead needed to make.
01 · Exception-first
Surface what changed before asking the operator to scan the system.
The Operations Lead should not have to search a healthy system to find the unhealthy part.
Exceptions became the primary entry point into investigation.
The operator starts with what requires attention, rather than scanning the entire system.
02 · Context beside the signal
The operator can investigate without reconstructing the situation across systems.
Keep the evidence needed to understand an event close to the event itself.
The operator should not have to reconstruct the situation across multiple systems. Relevant context was brought into the investigation path.
03 · Progressive detail
Expose more information only when the decision requires it.
The interface showed what was needed for the current decision first, while keeping deeper operational detail available when required.
Detail is introduced when it becomes relevant to the decision.
03 · The connected workflow
The system surfaces what changed.
The Operations Lead traces the signal back to its operational context.
The operator has enough context to determine the next operational action.
Something changes.
The system identifies what requires attention.
The Operations Lead explores the relevant context.
The interface connects the underlying information.
The operator has enough context to determine the appropriate operational action.
The interface reduces the distance between signal and decision.
04 · Reflection
The challenge wasn't making a complex enterprise system look simpler. It was creating a model that matched how the operator already understood the operation.
Complexity didn't disappear. It became organised around the user's decisions.
05 · Prototype
A real working build rather than a clickable mockup, so everything in it actually works. Best on a laptop or larger.
Acknowledge the ATS-3B alarm, and watch the banner move to the next one.
Open it and read the correlation. The evidence is there before you ask.
Drill from the hall down to a part inside the switch.