Skip to main content

solution.monitoring()

Monitoring & Supervision

operating context

When supervision shows everything but supports no decisions

Industrial supervision systems are often inherited collections of mimics: everything is shown, nothing is really readable under pressure.

01

Wall of mimics without hierarchy

Issue

The operator sees hundreds of tags and indicators with no clear hierarchy between overview and machine detail.

Solution

Without a level model (plant → line → machine), people on shift spend minutes hunting where a problem started.

02

Alarms without priority

Issue

Everything is "red": dozens of simultaneous alarms, no severity distinction, no criterion to silence secondaries.

Solution

Alarm management must be rethought around severity, context and recipient — otherwise the system trains operators to ignore it.

03

Same views for different roles

Issue

Operator, maintenance and line leader all share the same screen: each one has to filter mentally what actually matters.

Solution

Views should be designed per role and per shift, with information relevant to the moment and responsibility of the viewer.

operating method

How we work: 4 phases in sequence

01

HMI design

Design of supervision interfaces: plant overview, machine detail, alarm management.

Screen auditHierarchyLevel model
02

Plant connection

Connection to PLCs and field devices. Tag configuration, scaling and alarm conditions.

Alarm designSeveritySuppression
03

SCADA development

Implementation of supervision system with animated graphics, real-time trends and alarm history.

RolesShiftsDedicated views
04

Commissioning

On-site testing, alarm calibration, operator training and start-up.

RolloutTrainingMeasurement
expected output

What makes a well-built supervision layer

Not a wall of mimics, but a decision and reading system that reflects the real work of the department.

Aggregate views, drill-down and quick paths to move from symptom to intervention point.

tech spec

Technical spec

explorer
architecture/ 2
operations/ 2
level-model.ts
// hierarchical view model

Level model

Levels: Plant → line → machine
Drill-down: One click per level
References: ISA-101
ISA-101Hierarchy
// alarm philosophy

Alarm philosophy

Severity: 4 levels + suppressible
Recipients: Per role and shift
Standard: ISA-18.2
ISA-18.2Alarms
// role-based operational views

Role views

Operator: State + quick actions
Maintenance: Diagnostics + history
Line leader: KPIs + critical alarms
Operator UXShift
// new HMI adoption plan

Operational rollout

Pilot: Single line
Training: Hands-on + runbook
Metrics: MTTR + active alarms
RolloutTraining
architecture/level-model.ts Markdown
next_step.initialize

Need a supervision system that actually supports decisions?

Screen model, prioritized alarms, role-based views — less noise, more action.