TWIN
One model of the plant.
Start at the part, not the tag.
A reading, a drawing, a manual, a test record and a work order land on the same named part, so nobody starts from a tag name. The twin is checked before it is trusted, and then the work runs against it.
The product
The twin and Observe, side by side, on a solar farm. A demo site, a replayed day, with the names taken off.
Plant export against its setpoints and the curtailment limit, irradiance at the array, grid frequency, and each inverter now. The split opens from the twin, so the chart is never a tag name on its own.
Closer
Closer in: the point of connection and one inverter station, on the same model.
Two switchrooms and the metering cabinets on their pad, the MV cable run to the site boundary, the existing overhead line behind. Named in the quick-nav, one tap away from the whole site.
INV04 selected: the cabinet in the model, and beside it the card the readings land on. Observe values for the last day, the record of what the cabinet holds, and how sure the model is of its own placement.
What the twin holds
Three things on one model.
The readings, on their parts
Each reading sits on the tracker block, inverter, met station or point of connection it comes from, so a number on a chart is the reading of a named part in a named plant.
The documents, on the same parts
The same model holds the inspection data, schematics, CAD, manuals and test records for each piece of equipment, found from the part rather than from a folder.
The work, against it
Once the twin is validated, commissioning, testing and inspection work against it: what was checked, on which part, by which document.
Talk to us
A first conversation covers what your controller already publishes, what your network lets out, and what a probe on your rail would read.