OPTIMUS · DIGITAL TWIN
See plant and asset condition on a 3D model fed by live data
Every object in the 3D plant model is bound to the real asset and carries its operating status, condition, active alarms, running hours, and open work orders.
Platform: OPTIMUS · Operations & Visualization
The problem
A long asset list hides the physical context
In a plant with hundreds of assets, a status table gets hard to read. What goes missing is context: where the asset is, what sits next to it, and whether its fault has anything to do with the equipment around it.
Signs we usually find
- It takes time to find where an alarming asset physically sits
- Plant condition is hard to explain to non-technical people
- How equipment in one area relates to each other is not visible
- Status, condition, and open work sit on different screens
Used by
- Plant Manager
- Maintenance & Reliability Manager
- Control Room / Operations Center
- Management & Board of Directors
Data it reads
- 3D plant model with identified asset objects
- Live asset status and telemetry
- Active alarms and open work orders
- Plant, area, asset, and device hierarchy
How it works
From the machine to a decision
01
3D plant model
Asset objects registered
02
Binding
Objects tied to system assets
03
Live data
Status, condition, alarms
04
Action
Details & work orders
The system
What it looks like on screen
Capabilities
What you can do with it
3D plant overview
Every area of the plant in one view, with the status of each asset.
Status markers
Running, stopped, faulted, and offline marked right on the object.
Asset population summary
Asset count by status, read off a single compact row.
Asset context card
Area, device count, running hours, active alarms, and open work orders for the selected asset.
Live condition values
Vibration per axis and other condition parameters shown on the selected object.
Synced asset list
The list panel and the 3D model point to the same asset.
Filter by plant
Narrow the view to one plant or a specific area.
Jump to details
From the 3D object straight to the asset detail page and its history.
On the floor
How it is used day to day
01
3D asset
Object in the plant model
02
Live status
Running / fault
03
Condition
Vibration & temperature
04
Alarm
Active on the asset
05
Work order
Maintenance action
Impact
Why it matters
01
Plant condition read in seconds
One view answers which asset has a problem and where it is, without switching between screens.
02
Easier conversations across departments
Production, maintenance, and management talk about the same object, so there is no confusion about which asset is meant.
03
From finding to action in one system
An alarm on a 3D object can go straight into a work order, so the chain from detection to repair stays intact.
Start with this alone
Digital Twin needs assets that are already connected to the system. It is usually implemented after condition monitoring or CMMS is running, then extended as asset coverage grows.
In practice
Across different kinds of plants
- Oil & Gas
- Monitor compressor, separator, and heat exchanger status in one process area.
- Manufacturing
- Show the condition of all rotating equipment in the plant on one model.
- Utility & Electrical
- Flag transformers and utility equipment that are in fault.
- Control Room
- Use the plant model as the main screen for daily monitoring.
Integration
It connects to what you already have
No PLC, meter, or ERP needs replacing. Machvory reads from the equipment already installed in your plant.
01
PLCs, sensors, meters
Data at the machine
02
Edge gateway
Acquisition and buffering
03
Machvory integration layer
Modbus, OPC UA, MQTT
04
TNS / OPTIMUS
Analytics and workflow
05
ERP, SAP, BI
Enterprise reporting
- Siemens, Mitsubishi, Omron, Allen-Bradley PLCs
- Modbus TCP and Modbus RTU
- OPC UA
- MQTT
- Power and energy meters
- Vibration, temperature, current sensors
- Existing SCADA and HMI
- ERP and SAP
- REST API and SQL
Next steps
What usually comes next
Start with one need and add the rest when you actually need it.
FAQ
Questions we get a lot
Does the 3D model have to be built from scratch?
Not always. If a model exists from the plant design, it can be used once it has been simplified to run smoothly in a browser. If there is none, the model is built from layout drawings, photos, and equipment dimensions.
How many assets can it show?
The model in our public demo shows hundreds of asset objects, all bound to live data. The practical limit depends on how complex the model is and the device used to display it.
Is this Digital Twin just a visual display?
No. Every object is bound to the same asset the monitoring and CMMS modules use, so the status and values match the system exactly rather than being a separate copy.
Do we have to replace our existing PLCs or machines?
No. Machvory reads from what is already installed over Modbus, OPC UA, MQTT, or a power meter. Where a machine does not expose the data point we need, we add a sensor or gateway to that machine alone rather than touching its controls.
Can it run on-premise, with no cloud?
Yes. It can run entirely on a server inside the plant, in the cloud, or split between the two. The choice usually comes down to your IT/OT policy and what the plant network can carry.
How long does the first implementation take?
It depends on how ready the data points are and how many machines are involved. We normally start with a pilot on one line or a few critical assets to prove out data quality and the workflow, then widen once it holds up on the floor.
See Your Plant as a Live 3D Model
Our engineers look at your machines and the data you already have, then scope a pilot that is realistic to run.
- No obligation to buy
- A reply within business hours
- WhatsApp works too