Manufacturing IoT Incident Alerts

This dataset provides real-time, granular records of IoT sensor-triggered incident alerts in a smart manufacturing environment. Each alert includes sensor and equipment context, incident classification, severity, status, and response metrics, enabling operations teams to monitor anomalies, safety events, and equipment failures, and to optimize incident response processes.

  • last updated 2 Jan 2026
  • by GoMask
The brief that made it

Real-time monitoring and triage of production anomalies and safety events

Sample rows

preview · 8 of 60 rows · all 18 columns
alert_idstringstatusstringresponse_time_secondsintegerlocation_zonestringtimestampdatetimesensor_idstringsensor_typestringequipment_idstringequipment_namestringincident_typestringseveritystringsensor_valuefloatsensor_unitstringthreshold_valuefloatoperator_idstringresolution_time_secondsintegerdescriptionstringresolution_notesstring
ALRT-8G2X7B1Jopen45Zone A2024-06-01T08:17:13SNS-0015temperatureEQP-1002Conveyor Oven 2anomalyhigh87.5Celsius80OPR-431blankTemperature exceeded normal operating threshold.blank
ALRT-1J9R5N8Cresolved30Zone C2024-06-01T09:03:44SNS-0021vibrationEQP-1023Lathe Machine 3equipment_failurecritical12.8mm/s10OPR-4181200Vibration levels indicate potential bearing failure.Bearing replaced and machine recalibrated.
ALRT-3D2H6Q4Zacknowledged70Zone D2024-06-01T09:20:31SNS-0032pressureEQP-1011Hydraulic Press 1anomalymedium155.2psi150OPR-406blankPressure slightly above configured range.blank
ALRT-6F7P1K9Tresolved58Zone B2024-06-01T09:44:57SNS-0018proximityEQP-1027Material Feedersafety_eventhigh0.2meters0.5OPR-427345Unexpected object detected near feeder chute.Object removed, safety protocols reviewed.
ALRT-2U3K5W1BopenblankZone E2024-06-01T10:11:04SNS-0043humidityEQP-1015Cooling Tunnelenvironmentalmedium65%RH60blankblankHumidity levels above standard for this process.blank
ALRT-7Q4L9S3Mdismissed23Zone F2024-06-01T10:40:39SNS-0026currentEQP-1009Packaging Line Aanomalylow13.8A15OPR-408blankCurrent spike detected, but within safe margin.No further action needed.
ALRT-5T8B6E2Vacknowledged66Zone G2024-06-01T11:03:12SNS-0051voltageEQP-1034Press Brakequality_issuemedium450.6V440OPR-419blankVoltage readings outside optimal range.blank
ALRT-9Y3X4L2NopenblankZone H2024-06-01T11:23:40SNS-0014temperatureEQP-1020Dryer Unitenvironmentallow40.2Celsius38blankblankDryer temperature slightly above environmental limits.blank

What the 60 rows show

from the 60-row sample

Acknowledged status stands out: mean response_time_seconds is 48.4, against 29.9 for the rest.

  • 33.5median response_time_seconds
  • 4severities
  • 5incident types
  • 8sensor types
  • 9sensor units
  • 69.2median sensor_value
Mean response_time_seconds by status54 rows
0408031.5open11 rows48.4acknowle…20 rows31.7resolved18 rows19.6dismissed5 rows
response_time_seconds54 rows, in bands of 10
071413111254432105090response_time_seconds →

Median 33.5, from 10 to 85.

location_zone60 rows · top 10 of 21 values
  1. Zone D5
  2. Central Bay5
  3. Zone C4
  4. Zone E4
  5. Zone F4
  6. Zone G4
  7. West Line C4
  8. South Hall4
  9. Zone A3
  10. Zone B3
18 columns by typefrom the column list below
  • string 13
  • integer 2
  • float 2
  • datetime 1

Columns

18 columns in three groups
blueprint · 18 columns
columntypedescriptionexample
Text 13 columns
alert_idstringUnique identifier for each incident alert.uniqueALRT-8G2X7B1J
sensor_idstringUnique identifier for the IoT sensor that triggered the alert.SNS-0015
sensor_typestringType of sensor (e.g., temperature, vibration, pressure, proximity).8 valuestemperature
equipment_idstringUnique identifier for the equipment or machine associated with the alert.EQP-1002
equipment_namestringHuman-readable name of the equipment or machine.optionalConveyor Oven 2
location_zonestringZone or area within the facility where the incident occurred.Zone A
incident_typestringType of incident detected (e.g., anomaly, safety_event, equipment_failure, environmental).6 valuesanomaly
severitystringSeverity level of the incident (e.g., critical, high, medium, low).critical · high · medium · lowhigh
statusstringCurrent status of the alert (e.g., open, acknowledged, resolved, dismissed).open · acknowledged · resolved · dismissedopen
sensor_unitstringUnit of measurement for the sensor value (e.g., Celsius, psi, mm/s, %RH).9 units · optionalCelsius
descriptionstringDetailed description of the incident alert.optionalTemperature exceeded norm…
operator_idstringIdentifier for the operator or staff member assigned to the alert.optionalOPR-431
resolution_notesstringNotes or summary of actions taken to resolve the incident.optionalBearing replaced and mach…
Numbers 4 columns
sensor_valuefloatValue measured by the sensor at the time of the alert.87.5
threshold_valuefloatConfigured threshold value that triggered the alert.optional80
response_time_secondsintegerTime in seconds taken to acknowledge or respond to the alert.0 or more · optional45
resolution_time_secondsintegerTime in seconds taken to resolve the incident after it was acknowledged.0 or more · optional1200
Dates and times 1 column
timestampdatetimeDate and time when the alert was generated.2024-06-01T08:17:13

Use it for

  • median respons…33.554 rowsmean response time se…31.5open48.4ackn…31.7reso…19.6dism…

    A manufacturing dashboard

    Response_time_seconds by status and a breakdown of location_zone. Excel, Power BI or Tableau.

  • Why do the 20 acknowledged rows have a mean response_time_seconds of 48.4?

    A root-cause class exercise

    Hand out the rows and one question. The answer is in the data, not in the brief.

  • A software demo

    Believable alerts with timestamp, sensor_id and sensor_type to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 18 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 dataset60 rows18 columns
Yours1,000 rows18 columnslocation_zone: UK only

blueprint · manufacturing-iot-incident-alerts

Behind this dataset

Same schema. As many rows as you need.

These 60 rows came out of a blueprint — 18 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
  • All incidents are generated by active IoT sensors with unique IDs.
  • Each alert includes a timestamp, incident severity (Low/Medium/High), and affected machine type.
  • Response time must be logged and flagged if above SLA threshold (15 minutes for High severity).
  • Incident type must be categorized (e.g., Overheat, Vibration, Power Surge, Safety Stop).
  • Resolution status (Resolved, Escalated, Pending) is required for each alert.
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
manufacturing-iot-incident-alerts

What should your data show?

Preview 20 rows free
No signup. No card.