Demonstration

Live control room

A fictional bottled-water plant: water treatment then PET 1.5 L bottling. Inject a fault, acknowledge alarms, change profile, browse the trends with the keyboard.

Enable JavaScript to start the simulation. Below is the nominal state of the plant.

Why?

0Urgent0High0Medium0Low

No alarm to acknowledge

Shift OEE80.8%OEE = A 91.0% × P 90.0% × Q 98.7%
A · availability—
P · performance—
Q · quality—
Good bottles—
Shift energy—
Treated water—

Process mimic

Click an item, or Tab then Enter, to open its details.
Panel A — Water treatment
BOREHOLEP-101AT-101P-102AP-103ALT-10162.4%FT-10122.0m³/hTT-10261.8°CTT-10334.0°CFT-20124.0m³/hPT-2023.20barF-201PDT-2010.35barAIT-4010.22NTUUV-301AIT-30190.1%T-102LT-10271.3%
Panel B — Line 2, PET 1.5 L
SB-01RunningARB-02RunningAIN-03RunningAET-04RunningAFD-05RunningAST-50011,840bt/hSolid = running · outline = stoppedPET 1.5 L · 12,000 bt/h nominal
Panel C — Power
MAINSPresentGE-01StoppedATS-01RTGBT · JT-300255kW

Alarms

Example alarms (one per state)

PriorityTagMessageState
HighTT-102P-102 motor temperature highUnacknowledged
MediumPDT-201F-201 filter fouled — backwash dueAcknowledged
HighAIT-401High turbidity at filter outletReturned to normal — acknowledge
Displayed prioritiesPriorities

No alarm in this list.

Trends

Window

Live measurements

Text alternative to the mimic.

Live measurements
TagDescriptionValueUnitSetpointLimitsStateTrendDetails
LT-101Tank T-101 level62.4%55–85LL 10.0 · L 25.0Normalsteady
FT-101Borehole flow22.0m³/h22—Normalsteady
FT-201Transfer flow24.0m³/h24—Normalsteady
PT-202Discharge pressure3.20bar3.2L 1.50Normalsteady
PDT-201F-201 pressure drop0.35bar< 0,8H 0.80 · HH 1.20Normalsteady
AIT-401Filter outlet turbidity0.22NTU< 0,5H 0.80Normalsteady
AIT-301UV intensity90.1%> 85LL 55.0 · L 70.0Normalsteady
LT-102Tank T-102 level71.3%45–90LL 15.0 · L 30.0Normalsteady
TT-102P-102 motor temperature61.8°C58–64H 85.0 · HH 95.0Normalsteady
TT-103P-103 motor temperature34.0°C58–64H 85.0 · HH 95.0Normalsteady
ST-500Line 2 speed11,840bt/h11,400–12,000—Normalsteady
JT-300Total active power255kW≈ 255—Normalsteady

Event log

Show the last 50 events (0 / 500)
TimeEventTagMessageProfile

Equipment

Alarm

Shelve

Duration (simulated time)

A reason is required to shelve an alarm.

Inject a fault

Pick a scenario. It runs in simulated time (indicative duration at ×1 speed) and you can stop it at any time.

Scenario

Grey first

How to read this screen

This screen follows two industry standards: ISA-101 for the interface and ISA-18.2 for alarms.

Grey first (ISA-101)

Neutral grey background, grey equipment: no decorative colour. When a colour appears, something is abnormal. No green for “running” or red for “stopped”: state is read from the fill (solid = running, outline = stopped) and from a label.

Equipment states: Running · Stopped · Tripped · Starved · Blocked · Locked out.

Priorities

  • Urgent — respond within 2 min
  • High — respond within 10 min
  • Medium — respond within 30 min
  • Low — respond within 60 min

Colour is never alone: every priority also has a shape, a number and a word.

Alarm states (ISA-18.2)

  • Unacknowledged — blinking icon, bold row.
  • Acknowledged — steady icon.
  • Returned to normal — acknowledge — hollow icon.
  • Latched — stays after the return until reset.
  • Shelved — hidden for a while, with a reason, never at priority 1.

Some consequences deliberately have no alarm (“Starved”, “Blocked”): they are not causes and would flood the operator.

OEE (overall equipment effectiveness) multiplies three rates: A, availability (run time ÷ planned time); P, performance (bottles produced ÷ what the line would produce at its maximum rate of 13,000 bottles/h); Q, quality (good bottles ÷ bottles produced). The target shown under the bottle count is an 85% OEE, a common goal for a well-tuned bottling line.

What is simulated, what would be real

Here, a deterministic mathematical model (seed 2026) runs a fictional bottled-water plant: “Reset” replays exactly the same sequence. In a real project, measurements come from the PLCs over OPC UA, MQTT or Modbus TCP.

  • Read-only by default.
  • Network split into zones and conduits, following IEC 62443 principles.
  • Strong authentication and logging for every command.

Demonstration: this interface is not connected to any plant. In a real project, any remote command requires strong authentication, logging and a segmented network.

A dashboard like this at your site?

Describe your plant: an engineer tells you what is realistic, and in what time.