Skip to content

TwinEdge / Platform · Wiring it togetherThe model of the plant

Wiring it together

Model the relationships that matter.

Connect equipment models into a process. The twin follows the dependencies between assets so a local change can be understood in context.

Request a demoThe model of the plant

From source to shared context01 / SYSTEM VIEW
EquipmentHistoryDocuments
TwinEdgeShared asset context
Digital twinsAI agentsApps + APIs
01Connect02Map03Model04Publish
One asset model, reused across every consuming workflow.
What you provide, and what you do not
YouThe engine
Which machines existWhat has to be calculated first
What feeds whatWhat can run at the same time
Which model each machine usesFollowing a change through everything downstream
The units you work inRefusing a connection that does not make sense

§ 01

What it takes care of.

  • 01It works out the order for you

    You say the pump feeds the pipe and the pipe feeds the tank. Nobody has to write down that the pump must be calculated first — that falls out of the connections.

  • 02Independent parts run at the same time

    Two lines that do not touch each other are calculated side by side, which is what keeps a large plant inside the time available on a small box.

  • 03Connections that cannot be wrong

    An output in litres per second will not connect to an input expecting bar. It is refused when you wire it, not discovered as nonsense three weeks later.

  • 04Swap a model without stopping

    A better model for one machine can replace the old one while everything else keeps running, so improving one part does not mean an outage.

§ 02

Why this is worth having as a proper piece of software.

Plants get modelled in spreadsheets all the time, and it works until the plant changes. Then somebody has to find every cell that assumed the old arrangement, and usually one is missed.

When the connections are described rather than implied, a change is a change to the description. Nothing downstream has to be found by hand, because the engine already knows what depends on what.

Refusing bad connections is the underrated part. Most modelling errors are unit errors, and they are invisible until the answer is wrong by a factor you cannot explain.

“Not the physics. The afternoon somebody added a pump and forgot what it fed.”

What breaks a plant model

Describe one line and watch it resolve.

Sketch a process train on paper the way you would explain it to a new engineer. That sketch is effectively the input, and the working model can be running against your readings the same day.

Request a demoConnecting the sensors