No single picture
Health, state, alerts, work orders and flow sit in different screens, so nobody can say at a glance which line starves when one machine stops.
The MIRA Plant Twin draws every machine with live layers for health, state, alerts, work orders and flow, answers “what does a stop hold up?”, and marks anything it could not establish as grey instead of drawing it calm. No CAD model needed.
The answer usually takes three phone calls and a spreadsheet, because the picture of the plant lives in four systems.
Health, state, alerts, work orders and flow sit in different screens, so nobody can say at a glance which line starves when one machine stops.
An asset MIRA could not read is shown grey and never calm, and its drawer names what is missing.
A dashboard that draws an unread machine green is the most dangerous thing you can put on a wall.
See what starves downstream and the loss at your declared rate, with every input and source on screen.
A bearing warning needs a decision, and the cost per hour and the downstream impact are guessed from memory.
Assets with an open prescription ranked by urgency and by what sits downstream.
A scenario never acts. Apply opens a prescription and the normal approval.
Health, state, alerts, work orders and flow sit in different screens, so nobody can say at a glance which line starves when one machine stops.
A dashboard that draws an unread machine green is the most dangerous thing you can put on a wall.
A bearing warning needs a decision, and the cost per hour and the downstream impact are guessed from memory.
An asset MIRA could not read is shown grey and never calm, and its drawer names what is missing.
See what starves downstream and the loss at your declared rate, with every input and source on screen.
Assets with an open prescription ranked by urgency and by what sits downstream.
A scenario never acts. Apply opens a prescription and the normal approval.
Switch layers on and off to ask a different question of the same plant. Each layer states how fresh it can be, and shows grey wherever MIRA could not establish it.
The daily 0–100 health score with its reasons, and condition readings against the limits your engineers declared.
Running, idle, stopped or breakdown, refreshed every five minutes, with OEE for the line. A silent feed is shown as unknown, never as stopped.
What is open on each asset, what MIRA prescribes and by when, and whether the spare is in stock.
The line flow you declare, so you can see what feeds what, plus the energy drawn by each machine.
Open permits and isolations on each asset, and the procedures that apply to it.
How critical each asset is and whether the parts to keep it running are in stores.
Every asset drawer tells you how much to believe the picture, so a confident-looking colour never hides a gap.
A count of the layers MIRA established, refused, or holds but are older than their source allows.
Stated in metres on the site frame, drawn as a schematic from your ISA-95 hierarchy and declared flow, or not placed. Nothing in between is invented.
A sensor stuck at one value is flagged as an instrument problem, not drawn as a healthy machine.
See what changed since the last shift, compare two moments, or replay a period read-only. Replay is always marked as replay.
Four data-driven scenarios, each showing its inputs and where they came from, a backtest where one exists, and the label “scenario — not a forecast of record”.
If this machine stops, which downstream assets starve, and what the loss is at your declared rate.
Line output from your declared flow and cycle times. The model shows its own backtest, and says so when it fails.
When to take a machine down against its open degradation. It refuses when an asset has no open degradation.
An energy-shift scenario with its inputs and their sources shown, like every other what-if.
Assets with an open prescription ranked by urgency and downstream impact, priced at your declared cost of an hour of downtime. Unpriced is never zero.
Apply opens the prescription and the normal approval path, like every other action in MIRA.
From the control room to the shop floor to the head office.
Save a view for each role, search for any asset, and work from a needs-attention queue with notes on each asset.
A round for the technician and a planner’s view of what is due, on a tablet as well as at the desk.
Export a snapshot, or schedule a morning snapshot so the shift starts from the same picture.
Declare positions, upload a placement sheet, or upload a glTF/GLB model and bind its nodes to assets. MIRA suggests, a person confirms.
A read-only wall display with large type that reconnects by itself, for the twin-kiosk role only.
All the sites you may read, on a map or a list, compared side by side on the same measures.
We say this plainly, because a picture you can trust is worth more than one that looks impressive.
It is a digital shadow with data-driven what-if models. It has no physics, CFD or finite-element solver, no AR/VR and no walkable model.
Health is a daily assessment, machine state a five-minute sweep and prescriptions hourly. The legend says so. Without Redis, the twin is one 5-second poll behind and the page says it.
The line-throughput model shows its backtest. On the demo estate it fails, and the screen says so, rather than hiding it.
Book a demo and we will walk through the twin on a simulated plant running live, clearly labelled as simulated. Bring your equipment list and we will show how it would be drawn.