TwinEdge / Platform · Working with what you havePlatform overview
Works with the systems you already run
Keep SCADA and CMMS. Add the missing layer.
TwinEdge reads the control system, historian, and maintenance system you already run. It explains what changed, suggests the next job, and waits for a person. Nothing is ripped out.
What never changes without your say-so
| Stays exactly as it is | Why |
|---|---|
| Your control system | It runs the plant. TwinEdge is not in that loop. |
| Your historian | It stays the system of record. |
| Your maintenance system | Keep it, or move at your own pace. |
| Writing to equipment | Off by default. Enabled per machine, if ever. |
§ 01
Why adding beats replacing.
Replacing a control system is a two-year project with a real chance of hurting production. Almost nobody needs to do it to get the thing they actually want.
- 01Nothing gets ripped out
Your control system still runs the plant. TwinEdge reads from it. It is not in the control loop, so it cannot become the reason the plant stops.
- 02It reads. It does not drive.
The connection to your control system, your historian, and your maintenance system runs one way. Writing back is off, and stays off until you switch it on deliberately, machine by machine, with an approval behind it.
- 03It works on the data you already have
You have been collecting readings for years. Point TwinEdge at them and the modelling, the fault detection, and the analysis start on that history. You do not need to fit a single new sensor to begin.
- 04The data stays yours
Run it at the site, in your own cloud, or both. Your historian is still the system of record; TwinEdge never becomes the only place something is written down.
“You are not short of data. You are short of the layer that turns it into a decision somebody will sign for.”
The honest version
§ 02
How it sits on top, in four steps.
TwinEdge does not go into the control loop. It reads what you already collect, names the equipment, explains the change, and waits for a person before any work is raised.
§ 03
What it reads from.
Most sites are a mix built up over twenty years: a control system from one decade, a historian from another, a maintenance system chosen by somebody who has since left, and a great deal of it held together by spreadsheets.
That mix is normal, and it is not a problem to be fixed first. TwinEdge reads what is there. Where something has no interface at all, the edge runtime can read the equipment directly instead.
- OPC UA
- Modbus
- MQTT and Sparkplug B
- OSIsoft PI and AVEVA
- Ignition
- Wonderware
- Rockwell PLCs
- Siemens PLCs
- SQL historians
- IBM Maximo
- SAP PM
- Esri GIS
- Files and folders
- REST APIs
Watch it read your own data.
Give us read access to one historian and a list of the equipment behind it. We will show you what it finds in your own history, before you change anything at all.