Job to be done · SCADA / Controls Engineer and SCADA Manager

Cut the alarm flood to what matters

See it in the graph

When operators are explaining nuisance alarms to management and ignoring the rest, I want alarm counts, chattering points and standing alarms by area, so I can rationalise limits and make the audible alarms mean something.

Apps that fit

  • Board
  • Report

Measured by

  • alarms per operator per hour
  • standing alarms over 24 h
  • chattering points
  • acknowledgement time

What an app needs to see

  • alarm and event journal
  • alarm configuration (thresholds/tolerances and audible vs. pop-up alarms)
  • operator acknowledgement actions
  • alarm ranking by frequency and time active, each alarm linked to its SCADA tag, PLC address and P&ID ID, to target nuisance alarms

Pain points

  • Operators enter wrong values and set off alarms that must be explained to management, so limits are loosened (eng-tips)
  • NERC's lesson from seven EMS outages: mandatory operator response to alarms should be reinforced and audible alarms are necessary for acknowledgement
  • State estimator mismatch thresholds need periodic evaluation to balance sensitivity against false alarms (NERC)

Who else wants this

Cross-cutting and portfolio roles

Data center

Education campuses

Laboratories and life-science facilities

Manufacturing plants and industrial sites

Sources

More jobs for the SCADA / Controls Engineer and SCADA Manager

Every kind of facility

Every job category

See it in the graphAll of PersonaDBBuild an app for this job with Rivet

From PersonaDB, Mapped’s directory of who works in a facility and what they’re trying to get done. Every sourced entry links to the page it came from. PersonaDB’s words are free to reuse under CC BY 4.0 with credit to Mapped; the pages it cites keep their own terms. Cite as: “Cut the alarm flood to what matters”, PersonaDB, Mapped, https://rivet.mapped.com/personas/job/utilities-infrastructure/scada-controls-engineer/cut-the-alarm-flood-to-what-matters