Factory IoT Device Error Logs

This dataset provides granular, real-time logs of error events from IoT devices across a manufacturing shop floor, including device details, error codes, severity, operational context, and resolution status. It enables predictive maintenance, downtime analysis, and root cause investigations, supporting operational efficiency and continuous improvement initiatives.

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

Predictive maintenance scheduling and optimization

Sample rows

preview · 8 of 121 rows · all 15 columns
error_idstringseverity_levelstringdowntime_minutesfloatresolvedbooleandevice_typestringdevice_idstringdevice_locationstringtimestampdatetimeshiftstringerror_codestringoperator_idstringresolution_timestampdatetimeproduction_batch_idstringerror_descriptionstringmaintenance_action_takenstring
ERR202406A1B2warning27truesensordev-15Line 3 - Station 72024-02-13T08:17:23ZASEN014op-11232024-02-13T08:44:23ZPBATCH-20240213-A01Temperature sensor reported readings out of range, indicating possible calibration drift.Calibration performed and readings rechecked by operator.
PLC404-2024JUNinfo5trueplcdev-22Line 1 - Control Room2024-06-15T15:02:07ZBPLC404blank2024-06-15T15:07:07ZPBATCH-20240615-B02PLC communication lost with downstream actuator. System auto-recovered.blank
CB002-CRITcritical45trueconveyor beltdev-04Line 2 - Station 42024-04-29T20:52:00ZNightCB002op-25092024-04-29T21:37:00ZPBATCH-20240429-N03Conveyor belt jam detected by sensor. Emergency stop triggered.Cleared jam and inspected belt for damage.
RA2024BATCH18warning15truerobot armdev-37Line 4 - Station 22024-03-19T13:45:00ZBROB112op-23452024-03-19T14:00:00ZPBATCH-20240319-B04Robot arm misalignment detected during batch changeover.Arm realigned and sensors recalibrated.
UNREG-0001infoblankfalseunregisteredghost-999Unknown2024-05-22T02:17:00ZNightUNK001blankblankblankUnregistered device reported an error. Device not found in inventory.blank
SENSOR20240619info4truesensordev-02Line 1 - Station 12024-06-19T07:36:40ZASEN002blank2024-06-19T07:40:40ZPBATCH-20240619-A09Humidity sensor readings dropped below threshold. Possible environmental fluctuation.blank
ACT-0022-WRNwarning15trueactuatordev-29Warehouse 2 - Dock D2024-03-02T12:07:57ZCACT022op-11892024-03-02T12:22:57ZPBATCH-20240302-C01Actuator torque threshold exceeded; possible obstruction.Checked actuator for physical obstructions; reset threshold.
EGW-2024-06info5trueedge gatewaydev-XYZ99IT Room - Rack 32024-06-28T04:01:00ZNightEGW003blank2024-06-28T04:06:00ZblankNetwork packet loss detected at edge gateway. No production impact.blank

What the 121 rows show

from the 121-row sample

Critical (severity level) stands out: mean downtime_minutes is 21.0, against 5.1 for the rest.

  • 91%resolved = true
  • 5.8median downtime_minutes
  • 4shifts
Mean downtime_minutes by severity_level110 rows
0204021.0critical35 rows7.0warning47 rows2.0info28 rows
downtime_minutes110 rows, in bands of 5
02550432213128352202545downtime_minutes →

Median 5.8, from 0.0 to 45.0.

device_type121 rows · top 10 of 13 values
  1. sensor25
  2. plc16
  3. packager13
  4. robot arm9
  5. feeder8
  6. conveyor belt7
  7. unregistered7
  8. camera vision7
  9. extruder7
  10. actuator6
15 columns by typefrom the column list below
  • string 11
  • float 1
  • datetime 2
  • boolean 1

Columns

15 columns in four groups
blueprint · 15 columns
columntypedescriptionexample
Text 11 columns
error_idstringA unique identifier for each error event log entry.uniqueERR202406A1B2
device_idstringUnique identifier for the IoT device reporting the error.dev-15
device_typestringType or model of the IoT device (e.g., sensor, actuator, robot arm).sensor
device_locationstringPhysical location or zone of the device within the factory (e.g., 'Line 2 - Station 5').Line 3 - Station 7
shiftstringFactory shift during which the error occurred (e.g., 'A', 'B', 'C', 'Night').A · B · C · NightA
error_codestringStandardized code representing the type of error encountered.SEN014
error_descriptionstringDetailed description of the error event.Temperature sensor report…
severity_levelstringSeverity classification of the error (e.g., 'critical', 'warning', 'info').critical · warning · infowarning
operator_idstringIdentifier for the operator or technician on duty when the error occurred.optionalop-1123
maintenance_action_takenstringSummary of any immediate maintenance action taken in response to the error.optionalCalibration performed and…
production_batch_idstringIdentifier for the production batch affected by the error, if any.optionalPBATCH-20240213-A01
Numbers 1 column
downtime_minutesfloatTotal downtime in minutes caused by this error event (if applicable).0 or more · optional27
Dates and times 2 columns
timestampdatetimeDate and time when the error event occurred (in UTC).2024-02-13T08:17:23Z
resolution_timestampdatetimeDate and time when the error was resolved, if applicable.optional2024-02-13T08:44:23Z
True or false 1 column
resolvedbooleanIndicates whether the error has been resolved (true) or is still open (false).true

Use it for

  • resolved91%110 of 121 rowsmean downtime minutes…21.0critic…7.0warning2.0info

    A manufacturing dashboard

    The resolved rate, downtime_minutes by severity_level and a breakdown of device_type. Excel, Power BI or Tableau.

  • Why do the 35 critical rows have a mean downtime_minutes of 21.0?

    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 errors with device_id, device_type and device_location to fill a screen in front of a buyer.

Not quite right?

Make it yours.

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

Preview 20 rows free

10,000 rows of yours: $12.99One-time. No subscription. All prices

This dataset121 rows15 columns
Yours10,000 rows15 columnsdevice_location: UK only

blueprint · factory-iot-device-error-logs

Behind this dataset

Same schema. As many rows as you need.

These 121 rows came out of a blueprint — 15 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
  • Each row represents a unique device error event
  • Event timestamps must reflect operational hours
  • Include device type, error code, severity, and location
  • Link error events to manufacturing process stages
  • Only devices active on the shop floor are included
Rows
Open the blueprint in Data Factory

1 credit per row. New accounts start with 25 free credits.

Exports
CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
Licence
yours to use, including commercially
API slug
factory-iot-device-error-logs

What should your data show?

Preview 20 rows free
No signup. No card.