Name the operator
Every change has a person behind it. The model shows who decided, who was told, and who owns the next step.
Nadi / Operations infrastructureConcept 05
Every systemhas a pulse.
Nadi is a fictional operations platform for the people who keep critical systems running. It turns live signals, field notes, and decisions into one shared model.
Signal field / illustrativeTrace 04
01 / The argument
The room needs a shared picture.
Most operations teams are not short of screens. They are short of a model that holds the system, the shift, and the next decision in the same place.
Nadi starts with the work a control room already does: watch a signal, find what depends on it, make a call, and hand the reason to the next person. The interface follows that sequence.
Designed for the handover, not the demo02 / Shared model
A model built from the work, not the dashboard.
The model connects the signal to the site, the crew, the open action, and the person who owns the next step. It stays visible when the room changes pace.
Sources keep their names and times. Decisions keep their reasons. The map is useful because it can explain itself during a handover.
Nadi is not a replacement for the systems that run the grid, the plant, or the fleet. It is the layer that helps the room read them together.
Dependency visibleSource, owner, and time attached
03 / The room
Three surfaces, one shift.
The product is organised around what an operator has to do next, not around the data source that produced the last alert.
01
Map
What is connected to what.The live model shows systems, sites, crews, and open actions on the same plane. It does not flatten them into a list of alerts.
02
Trace
What a change touches.Select a signal and follow its dependencies through the model. The trace keeps the source, the time, and the owner attached.
03
Handover
What the next shift needs.Every action leaves a short, plain-language note. The next operator can read the decision, not reconstruct it from a dashboard.
04 / Signal lab
Trace a signal before it becomes an incident.
The Signal Lab is a small, illustrative model of how Nadi follows a change through the room. Choose a scenario and run the trace.
No live system is connected. The point is to show the shape of the handover, not to simulate a real network.
Trace / sequenceA handover is part of the model
05 / Principles
Four rules for the room.
A screen is only useful if it can survive a difficult shift. These are the constraints we design against.
Keep the model visible
The shared picture stays on screen during the escalation, not only at the start of the shift.
Record the decision
A dashboard shows a state. A handover needs the reason, the assumption, and the thing that changed.
Design for 03:00
The hardest shift gets the clearest language. If a screen needs a manual to read at night, it is not finished.
A dashboard shows a state. A handover needs the reason.
Start a conversation