• Energy
  • 17 columns
  • 130 rows
  • 8 formats

SCADA Alarm and Event Management

This dataset provides comprehensive logs of alarms and events from SCADA systems, including priority levels, operator responses, alarm flooding detection, and root cause analysis. It enables detailed operational insights, supports compliance reporting, and facilitates advanced analytics for reliability and safety improvements in industrial environments.

  • last updated 2 Nov 2025
  • by GoMask
The brief that made it

Operational incident analysis and troubleshooting

Sample rows

preview · 8 of 130 rows · all 17 columns
alarm_event_idstringroot_cause_categorystringpriorityintegeracknowledgedbooleanalarm_typestringtimestampdatetimesource_device_idstringsource_device_namestringacknowledged_bystringacknowledged_timestampdatetimeoperator_actionstringalarm_floodedbooleanroot_cause_detailsstringclearedbooleancleared_timestampdatetimelocationstringcommentsstring
AE10001Equipment Failure1trueHigh Pressure2024-04-01T08:15:23ZDVC-PLANTA-02Boiler Pressure Sensoroperator_jwang2024-04-01T08:16:01ZPressure valve manually releasedfalseValve actuator stuck due to mechanical wear.true2024-04-01T08:17:49ZPlant AFollow-up maintenance scheduled.
AE10002Process Upset2trueBreaker Trip2024-04-01T08:23:12ZDVC-SUB5-11Substation 5 Main Breakeroperator_mlewis2024-04-01T08:24:02ZBreaker reset remotelyfalseUnexpected load increase detected.true2024-04-01T08:25:17ZSubstation 5Investigating load spike.
AE10003blank3falseLow Fuel2024-04-01T09:05:34ZDVC-PLANTA-09Fuel Supply MonitorblankblankblankfalseblankfalseblankPlant AAwaiting operator response.
AE10004Process Upset3trueHigh pH2024-04-01T09:15:08ZDVC-WTP-03Water Treatment pH Sensoroperator_ssingh2024-04-01T09:15:43ZAdjusted chemical dosingfalseIncorrect dosage calculation.true2024-04-01T09:17:28ZWater Treatment PlantMonitor dosing system.
AE10005Equipment Failure2trueMotor Overload2024-04-01T09:27:47ZDVC-PLANTB-07Conveyor Belt Motoroperator_lgomez2024-04-01T09:28:10ZMotor reset and inspectedtrueBearing lubrication insufficient.true2024-04-01T09:29:42ZPlant BLubrication maintenance scheduled.
AE10006Equipment Failure2trueMotor Overload2024-04-01T09:30:13ZDVC-PLANTB-07Conveyor Belt Motoroperator_lgomez2024-04-01T09:30:30ZMotor stopped for inspectiontrueConsecutive overloads due to flood.true2024-04-01T09:31:20ZPlant BMultiple alarms during flood period.
AE10007blank2falseMotor Overload2024-04-01T09:30:52ZDVC-PLANTB-07Conveyor Belt MotorblankblankblanktrueblankfalseblankPlant BAwaiting operator action.
AE10008Equipment Failure1trueGround Fault2024-04-01T10:00:25ZDVC-SUB5-03Substation 5 Feeder Protectionoperator_akumar2024-04-01T10:01:07ZDispatched maintenance crewfalseInsulation breakdown detected.falseblankSubstation 5Critical fault—immediate attention required.

What the 130 rows show

from the 130-row sample
  • 65%acknowledged = true
  • 2median priority
root_cause_category92 rows by value
0204035Equipm…27%9Human …7%34Proces…26%8Commun…6%6Unknown5%
priority130 rows, in bands of 0.5
02550400450301512.54priority →

Median 2, from 1 to 4.

alarm_type130 rows · top 10 of 31 values
  1. Communication Failure13
  2. Motor Overload10
  3. Low Flow10
  4. High Temperature10
  5. Manual Override8
  6. Pressure Drop6
  7. Voltage Spike6
  8. Sensor Fault6
  9. Breaker Trip5
  10. Pump Failure5
17 columns by typefrom the column list below
  • string 10
  • integer 1
  • datetime 3
  • boolean 3

Columns

17 columns in four groups
blueprint · 17 columns
columntypedescriptionexample
Text 10 columns
alarm_event_idstringUnique identifier for each alarm or event recorduniqueAE10001
source_device_idstringIdentifier for the SCADA device or subsystem that generated the alarm/eventDVC-PLANTA-02
source_device_namestringHuman-readable name of the device or subsystem that generated the alarm/eventoptionalBoiler Pressure Sensor
alarm_typestringType of alarm or event (e.g., High Temperature, Communication Failure, Manual Override)High Pressure
acknowledged_bystringOperator ID or name who acknowledged the alarm/eventoptionaloperator_jwang
operator_actionstringDescription of the action taken by the operator in response to the alarm/eventoptionalBreaker reset remotely
root_cause_categorystringCategory of root cause identified for the alarm/event (e.g., Equipment Failure, Human Error, Process Upset)5 values · optionalEquipment Failure
root_cause_detailsstringDetailed explanation of the root cause analysis for the alarm/eventoptionalFan blades obstructed.
locationstringPhysical or logical location of the device or event (e.g., Plant A, Substation 5)optionalPlant A
commentsstringAdditional notes or comments related to the alarm/eventoptionalMonitor dosing system.
Numbers 1 column
priorityintegerPriority level of the alarm/event (e.g., 1=Critical, 2=High, 3=Medium, 4=Low)1 to 41
Dates and times 3 columns
timestampdatetimeDate and time when the alarm or event was generated2024-04-01T08:15:23Z
acknowledged_timestampdatetimeTimestamp when the alarm/event was acknowledgedoptional2024-04-01T08:16:01Z
cleared_timestampdatetimeTimestamp when the alarm/event was cleared/resolvedoptional2024-04-01T08:17:49Z
True or false 3 columns
acknowledgedbooleanIndicates whether the alarm/event has been acknowledged by an operatortrue
alarm_floodedbooleanIndicates if the alarm/event occurred during an alarm flood (multiple alarms in short period)false
clearedbooleanIndicates whether the alarm/event has been cleared/resolvedtrue

Use it for

  • acknowledged65%85 of 130 rowsmean priority by root…1.8Equi…3.8Huma…2.3Proc…1.3Comm…

    An energy dashboard

    The acknowledged rate, priority by root_cause_category and a breakdown of alarm_type. Excel, Power BI or Tableau.

  • Why do 85 of 130 rows have acknowledged = true?

    A class exercise

    Hand out the rows and one question. Everyone works from the same 130 rows.

  • A software demo

    Believable alarm events with timestamp, source_device_id and source_device_name to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 17 columns, your size and your rules. See 20 rows before you pay.

Preview 20 rows free

1,000 rows: $1.99 · 10,000: $12.99One-time. No subscription. All prices

This dataset130 rows17 columns
Yours1,000 rows17 columnslocation: UK only

blueprint · scada-alarm-and-event-management

Behind this dataset

Same schema. As many rows as you need.

These 130 rows came out of a blueprint — 17 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.

Rules it was built with
  • Alarm ID unique per event
  • Timestamp with millisecond precision
  • Alarm priority: critical, major, minor, informational
  • Alarm state: active, cleared, acknowledged, shelved
  • Alarm type: equipment failure, limit exceeded, communication loss
  • Sequence of Events (SOE) logging
  • Operator acknowledgment timestamp and user ID
  • Operator actions taken and comments
Rows
Open the blueprint in Data Factory

1 credit per row. Preview 20 rows free. Buy rows for the full run.

Exports
CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
Licence
yours to use, including commercially
API slug
scada-alarm-and-event-management

What should your data show?

Preview 20 rows free
No signup. No card.