Factory IoT Sensor Fault Logs

This dataset provides detailed logs of IoT sensor faults in manufacturing environments, including fault codes, severity, sensor readings, environmental conditions, and maintenance actions. It enables anomaly detection, predictive maintenance, and operational efficiency analysis by offering rich contextual and event-driven data for each fault occurrence.

  • opened 5 times
  • last updated 28 Nov 2025
  • by GoMask
The brief that made it

Anomaly detection and root cause analysis in factory operations

Sample rows

preview · 8 of 121 rows · all 22 columns
log_idstringseverity_levelstringrecovery_time_minutesfloatmaintenance_requiredbooleanproduction_line_idstringtimestampdatetimefactory_idstringmachine_idstringsensor_idstringsensor_typestringfault_codestringwarning_codestringfault_statusstringoperator_idstringenvironment_temperature_cfloatenvironment_humidity_pctfloatenvironment_pressure_kpafloatsensor_reading_valuefloatsensor_reading_unitstringmaintenance_ticket_idstringfault_descriptionstringcommentsstring
LOG-1A2B3C4Dmajor12.7truePL-01A2024-04-08T10:17:32ZNEU-PLANT-01MC-0001SENS-0000011temperatureFC-TEMP-001blankresolvedOP-100153.448.298.758.6CMT-104750Temperature exceeded safe operating range.Manual cooldown performed, system restored.
LOG-5F6E7G8HcriticalblanktruePL-02B2024-04-08T02:58:43ZSOUTH-PLANT-02MC-0002SENS-0000023vibrationFC-VIB-014WRN-VIB-010escalatedOP-102329.157.6101.217.8mm/sMT-104751Vibration amplitude above threshold.Escalated to engineering. Safety stop triggered.
LOG-9I0J1K2LmajorblanktruePL-01B2024-04-09T23:50:02ZNEU-PLANT-01MC-0003SENS-0000035pressureFC-PRS-021blankdetectedOP-104133.844.993.693.6kPaMT-104752Pressure dropped below 95 kPa.Immediate attention required for leak check.
LOG-3M4N5O6Pminor1.3falsePL-04A2024-04-10T06:22:15ZWEST-PLANT-04MC-0004SENS-0000047humidityFC-HUM-008WRN-HUM-003resolvedblank24.667100.668.3%RHblankHumidity spike detected in enclosure.Automated system vented area.
LOG-7Q8R9S0TwarningblankfalsePL-03B2024-04-11T00:00:00ZEAST-PLANT-03MC-0005SENS-0000059proximityFC-PROX-015blankdetectedblank18.435.197.60cmblankProximity sensor failed to detect object.Sensor reset remotely.
LOG-1U2V3W4XmajorblanktruePL-01A2024-04-11T16:47:13ZNEU-PLANT-01MC-0006SENS-0000061currentFC-CUR-003WRN-CUR-001in_progressOP-110227.551.299.342.3AMT-104753Current spike detected on line.Technician investigating power surge.
LOG-5Y6Z7A8Bminor0.33falsePL-02C2024-04-12T13:35:08ZSOUTH-PLANT-02MC-0007SENS-0000073voltageFC-VOLT-021blankresolvedOP-120332.130.2102.8187.5VblankVoltage dropped below acceptable threshold.Brief power dip, auto-compensated.
LOG-9C0D1E2FcriticalblanktruePL-01B2024-04-13T05:08:45ZNEU-PLANT-01MC-0008SENS-0000085temperatureFC-TEMP-003WRN-TEMP-999escalatedblank10007.82021000CMT-104754Extreme temperature detected (1000 C).Extreme outlier for system test.

What the 121 rows show

from the 121-row sample

Major (severity level) stands out: 39 of its 39 rows have maintenance_required = true, against 26 of 82 for the rest.

  • 54%maintenance_required = true
  • 0.39median recovery_time_minutes
  • 4fault statuses
  • 8sensor types
  • 8sensor reading units
  • 13factories
Maintenance required rate by severity_levelmaintenance_required = true
0%50%100%100%critical26 of 26100%major39 of 390%minor0 of 310%warning0 of 25
recovery_time_minutes34 rows, in bands of 5
015302721011100102550recovery_time_minutes →

Median 0.39, from 0.05 to 45.1.

production_line_id121 rows · top 10 of 23 values
  1. PL-04A11
  2. PL-03A10
  3. PL-01B9
  4. PL-04B9
  5. PL-03C9
  6. PL-04C9
  7. PL-02B8
  8. PL-02A8
  9. PL-01A7
  10. PL-03B7
22 columns by typefrom the column list below
  • string 15
  • float 5
  • datetime 1
  • boolean 1

Columns

22 columns in four groups
blueprint · 22 columns
columntypedescriptionexample
Text 15 columns
log_idstringUnique identifier for each sensor fault log entryuniqueLOG-1A2B3C4D
factory_idstringUnique identifier for the factory where the sensor is locatedNEU-PLANT-01
production_line_idstringIdentifier for the specific production line within the factoryPL-01A
machine_idstringUnique identifier for the machine or equipment monitored by the sensorMC-0001
sensor_idstringUnique identifier for the IoT sensor reporting the faultSENS-0000011
sensor_typestringType of sensor (e.g., temperature, vibration, pressure, humidity, etc.)8 valuestemperature
fault_codestringStandardized code representing the type of fault detectedFC-TEMP-001
fault_descriptionstringHuman-readable description of the fault eventHumidity exceeded 90%.
warning_codestringWarning code associated with the fault, if any (blank if not applicable)optionalWRN-VIB-010
severity_levelstringSeverity classification of the fault (e.g., critical, major, minor, warning)critical · major · minor · warningmajor
fault_statusstringCurrent status of the fault (e.g., detected, in_progress, resolved, escalated)detected · in_progress · resolved · escalatedresolved
operator_idstringIdentifier for the operator or technician who handled the fault (blank if automated)optionalOP-1001
sensor_reading_unitstringUnit of measurement for the sensor reading value (e.g., C, Pa, mm/s, %RH)8 units · optionalC
maintenance_ticket_idstringReference to the maintenance ticket created (blank if not applicable)optionalMT-104750
commentsstringAdditional notes or comments about the fault eventoptionalSensor reset remotely.
Numbers 5 columns
recovery_time_minutesfloatTime taken (in minutes) to recover from the fault, if resolved0 or more · optional12.7
environment_temperature_cfloatAmbient temperature (in Celsius) at the time of the faultoptional53.4
environment_humidity_pctfloatAmbient humidity (percentage) at the time of the fault0 to 100 · optional48.2
environment_pressure_kpafloatAmbient pressure (in kilopascals) at the time of the faultoptional98.7
sensor_reading_valuefloatSensor reading value at the time of the fault (unit depends on sensor_type)optional58.6
Dates and times 1 column
timestampdatetimeDate and time when the fault was detected by the sensor2024-04-08T10:17:32Z
True or false 1 column
maintenance_requiredbooleanIndicates if maintenance was required as a result of the faulttrue

Use it for

  • maintenance re…54%65 of 121 rowsmaintenance required …100%crit…100%major0%minor0%warn…

    A manufacturing dashboard

    The maintenance_required rate, recovery_time_minutes by severity_level and a breakdown of production_line_id. Excel, Power BI or Tableau.

  • Why do 65 of 121 rows have maintenance_required = true?

    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 logs with timestamp, factory_id and production_line_id to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 22 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 dataset121 rows22 columns
Yours1,000 rows22 columns

blueprint · factory-iot-sensor-fault-logs

Behind this dataset

Same schema. As many rows as you need.

These 121 rows came out of a blueprint — 22 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 IoT sensor event on a factory floor
  • Include timestamp, sensor ID, fault type, and severity
  • Environmental readings (temperature, vibration) must reflect abnormal conditions for fault events
  • Recovery time varies by fault severity, longer for critical faults
  • Fault frequency is higher during peak production shifts
  • Include a flag for whether fault was auto-resolved or required technician intervention
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
factory-iot-sensor-fault-logs

What should your data show?

Preview 20 rows free
No signup. No card.