Start with the shift
The interface begins with the work an operator has to do, not with the data source that happens to be available.
Company / 04
Built for the handover.
Nadi is a fictional operations software company. The site is a design concept, not a product announcement. The argument is simple: the room needs a model that survives the shift.
01 / Why this exists
We started with the part that usually gets lost.
Control rooms are full of signals. The difficult part is not seeing more of them. It is keeping the reason for a decision attached when the shift ends.
The concept follows a single operational moment from source to handover. That constraint shapes the model, the language, and the interface. It also keeps the product from becoming a generic dashboard.
Nadi is not claiming a customer base, a certification, or a live deployment. It is a portfolio concept for a different kind of operations software site.
Keep the source attached
A value without a source is a rumour. Every change keeps its origin, time, and owner in the model.
Write for the next person
A handover note is part of the product, not a report exported after the fact.
Leave room for doubt
The model shows what is known, what is assumed, and what still needs a field check. Confidence is not a decoration.
The work