Use cases
Use cases on top of the SCADA
Four cases that work today, read-only. For each: what it reads, what it returns and what it doesn't do. The third matters as much as the second.
6.1
From alarm floods to diagnosis
- Who it's for
- Control room, night shift.
- The question
What's really going on?- What it reads
- AlarmsEventsP&IDSOPOpen WOs
- What it returns
- Alarms grouped by cause from the alarm list, probable root and recommended action citing the procedure.
- What it doesn't do
- It doesn't suppress or acknowledge alarms. It prioritises and explains. The alarm is still yours.
Cause 1 · Compressed air pressure118 alarms
Cause 2 · Safety door St. 254 alarms
Cause 3 · Drive M7 communication28 alarms
Probable root: pressure drop in the main header at 02:14. Station 3–5 alarms are a consequence. Action: check compressor C2 per procedure.
Alarms 02:10–02:40P&ID-03 sheet 2SOP-207 §4
Illustrative mock-up, not a customer screenshot.
6.2
Operator copilot
- Who it's for
- Line operator, shift handover.
- The question
- What's the torque for the part I'm assembling?
- What it reads
- active recipeSOPmachine manualprevious shift report
- What it returns
- The answer with the document page, contextual instructions and the shift summary drafted for you to validate.
- What it doesn't do
- It doesn't change the recipe or the setpoint.
Current partR-2210
For R-2210, the torque is 24 ± 1.5 Nm on the four cover screws, in a cross pattern.
SOP-114 §3.2active recipe · R-2210
Shift summary
Draft ready to validate: 2 changeovers, 1 stop of 14 min at St. 4.
In production, this requires an identified user and is recorded in the audit trail.
Illustrative mock-up, not a customer screenshot.
6.3
Performance analysis
- Who it's for
- Production manager, continuous improvement.
- The question
- Why did line 3's OEE drop on the night shift?
- What it reads
- Reports (SQL / GraphQL)HistorianMES
- What it returns
- The diagnosis, with the charts it builds for that question and the evidence next to the data.
- What it doesn't do
- It doesn't replace the official report. It explains it.
Station 4 accumulates 23 micro-stops on the night shift, always within 20 minutes of a changeover.
GraphQL · OEE_L3Historian · L3_ST4_STOP
Illustrative mock-up, not a customer screenshot.
6.4
Maintenance with memory
- Who it's for
- Maintenance.
- The question
- Has this failure happened before?
- What it reads
- IO-LinkdrivesCMMSJira / Zendesk / ServiceNow
- What it returns
- The seven-month-old ticket, how it was fixed, and a proposed work order with an approval button.
- What it doesn't do
- It doesn't create the work order without someone approving it.
Valve V-31 · switching time+38 %
This happened seven months ago on V-28: degraded seal. It was fixed by replacing the seal and cleaning the inlet filter (2 h job).
IO-Link · V-31 diagOT-4812Jira MNT-233
Proposal
Create WO: replace V-31 seal at the next planned stop.
In production, this requires an identified user and is recorded in the audit trail.
Illustrative mock-up, not a customer screenshot.
Sectors
Automotive and components
MES, part-level traceability“Which part number has the most micro-stops after changeover?”
Food and beverage
Batch, CIP, OEE“Why did line 2's CIP run long?”
Pharma and life sciences
Batch, audit trail, 21 CFR Part 11“What deviations occurred in batch 4471?”
Energy and BESS
EDMS, electrical SCADA“How much peak did we shave today with the battery?”
Chemicals and process
DCS, historian, NAMUR NOA“Is reactor 3's temperature normal at this hour?”
Logistics and automated warehouse
WMS, sorter PLC“Why did the zone B sorter jam?”