Inputs
Telemetry, schedules, field notes, open actions, and the messages that usually live beside the system.
Platform / 01
One model. Every operator.
Nadi connects the signals a system already produces with the people who have to act on them. The model stays visible during the shift, the escalation, and the handover.
02 / Architecture
The model sits between the source and the decision.
It is a working layer, not a presentation layer. The room can see where a value came from, which action depends on it, and who owns the next step.
Model
A shared state of what exists, what depends on what, and which source is carrying the latest value.
Action
Assign, annotate, escalate, or close. Every action updates the model and leaves a readable trace.
Record
A shift log built from decisions, not screenshots. The next person can see why the room moved.
03 / Interfaces
The screen follows the shift.
Map, trace, and handover are not separate products. They are three moments in the same operational sequence.
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 / Boundaries
What Nadi does not do.
A clear boundary makes a control room easier to trust. Nadi is deliberately not the system of record for physical control.
- Not a SCADA replacement. Nadi reads the operational picture; it does not issue switching commands.
- Not an autonomous operator. The room makes the decision. The model keeps the reasoning attached.
- Not a dashboard builder. The interface is designed around the shift, not around a library of widgets.
See it in motion