Manufacturing Machine Downtime Logs
This dataset provides detailed logs of manufacturing machine downtime events, including timestamps, causes, resolutions, and production impact. It enables predictive maintenance, root cause analysis, and process optimization by offering granular insights into machine reliability and operational efficiency.
Sample rows
preview · 8 of 200 rows · all 16 columns| downtime_idinteger | downtime_typestring | duration_minutesfloat | scheduled_maintenanceboolean | locationstring | machine_idstring | machine_namestring | downtime_startdatetime | downtime_enddatetime | cause_descriptionstring | resolved_bystring | resolution_actionsstring | parts_replacedstring | production_impactstring | reported_bystring | report_datedate |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | mechanical | 48 | false | Assembly Line A | MX-1001 | Press Alpha | 2024-06-03T08:14:00 | 2024-06-03T09:02:00 | Main drive belt slipped off spindle during morning shift. | tech_jroberts | Adjusted belt alignment and tension; tested startup. | belt | 24 units delayed, 48 min lost | op_cmartin | 2024-06-03 |
| 2 | electrical | 25 | false | Welding Bay | MX-2002 | Welder Sigma | 2024-06-04T14:35:00 | 2024-06-04T15:00:00 | Voltage drop detected; automatic shutdown triggered. | team_electric | Reset breaker and checked wiring. | blank | 10 units lost, minor delay | op_rkhan | 2024-06-04 |
| 3 | mechanical | 80 | false | Cutting Room | MX-3006 | Cutter Theta | 2024-06-05T10:10:00 | 2024-06-05T11:30:00 | Blade jammed due to improper material feed. | tech_egreen | Cleared jam, lubricated blade, tested cut. | blade | 36 units delayed, 80 min lost | op_dgomez | 2024-06-05 |
| 4 | operator_error | 30 | false | Assembly Line B | MX-4009 | Press Delta | 2024-06-06T07:45:00 | 2024-06-06T08:15:00 | Forgot to reset machine after maintenance break. | op_jreed | Restarted machine and verified settings. | blank | No units lost, minor delay | op_jreed | 2024-06-06 |
| 5 | scheduled_maintenance | 110 | true | Cutting Room | MX-5003 | Cutter Zeta | 2024-06-07T13:20:00 | 2024-06-07T15:10:00 | Quarterly preventive check and calibration. | maintenance_team | Cleaned and replaced filter, calibrated blade system. | filter | Planned downtime, no impact | scheduler_bnelson | 2024-06-05 |
| 6 | mechanical | 50 | false | Assembly Line C | MX-1002 | Press Beta | 2024-06-08T16:00:00 | 2024-06-08T16:50:00 | Hydraulic leak from rear actuator. | tech_slim | Replaced seal and tested hydraulic pressure. | seal | 22 units delayed | op_rpatel | 2024-06-08 |
| 7 | electrical | 7 | false | Welding Bay | MX-2004 | Welder Kappa | 2024-06-09T09:35:00 | 2024-06-09T09:42:00 | Fuse tripped during operation. | tech_lmurphy | Replaced fuse, restarted system. | fuse | No measurable impact | op_lmurphy | 2024-06-09 |
| 8 | mechanical | 75 | false | Assembly Line D | MX-4001 | Press Gamma | 2024-06-10T11:22:00 | 2024-06-10T12:37:00 | Gear set worn, causing misalignment. | tech_egreen | Replaced gear set, adjusted alignment. | gear set | 30 units lost, 75 min delay | op_lcastro | 2024-06-10 |
| 9 | operator_error | 5 | false | Cutting Room | MX-5008 | Cutter Omega | 2024-06-11T17:00:00 | 2024-06-11T17:05:00 | Incorrect material loaded, auto-stop triggered. | op_kwhite | Removed incorrect material, resumed operation. | blank | No units lost | op_kwhite | 2024-06-11 |
| 10 | mechanical | 57 | false | Cutting Room | MX-3003 | Cutter Lambda | 2024-06-12T06:50:00 | 2024-06-12T07:47:00 | Coolant system failure, blade overheated. | tech_slim | Replaced coolant pump, tested blade temperature. | coolant | 28 units delayed | op_rpatel | 2024-06-12 |
| 11 | electrical | 33 | false | Welding Bay | MX-2007 | Welder Tau | 2024-06-13T12:00:00 | 2024-06-13T12:33:00 | Sensor misread caused premature shutdown. | team_electric | Reset sensor, updated firmware. | blank | 8 units delayed | op_mharris | 2024-06-13 |
| 12 | mechanical | 18 | false | Assembly Line E | MX-1004 | Press Epsilon | 2024-06-14T15:10:00 | 2024-06-14T15:28:00 | Minor jam in feed tray. | op_swright | Cleared jam and resumed operation. | blank | 5 units delayed | op_swright | 2024-06-14 |
| 13 | other | 90 | false | Test Lab | MX-6001 | Test Lab Proto | 2024-06-15T10:30:00 | 2024-06-15T12:00:00 | Software update and testing. | test_team | Installed update, monitored system. | blank | Lab test; no production affected | test_team | 2024-06-15 |
| 14 | scheduled_maintenance | 100 | true | Assembly Line A | MX-1003 | Press Zeta | 2024-06-16T13:45:00 | 2024-06-16T15:25:00 | Annual preventive maintenance. | maintenance_team | Cleaned and replaced filter, tested systems. | filter | Planned downtime, no impact | scheduler_dtran | 2024-06-14 |
| 15 | mechanical | 85 | false | Cutting Room | MX-3001 | Cutter Alpha | 2024-06-17T11:10:00 | 2024-06-17T12:35:00 | Motor overheated due to blocked vent. | tech_jroberts | Cleared vent, replaced motor. | motor | 35 units lost | op_dgomez | 2024-06-17 |
| 16 | electrical | 30 | false | Welding Bay | MX-2001 | Welder Beta | 2024-06-18T07:30:00 | 2024-06-18T08:00:00 | Short circuit at controller board. | tech_lmurphy | Replaced circuit board, tested controls. | circuit_board | 12 units delayed | op_mharris | 2024-06-18 |
| 17 | operator_error | 10 | false | Assembly Line C | MX-4003 | Press Theta | 2024-06-19T09:00:00 | 2024-06-19T09:10:00 | Operator paused machine for unscheduled check. | op_tlee | Resumed operation after verification. | blank | No impact | op_tlee | 2024-06-19 |
| 18 | mechanical | 135 | false | Cutting Room | MX-5004 | Cutter Kappa | 2024-06-20T15:50:00 | 2024-06-20T18:05:00 | Feeder tray motor failed. | tech_slim | Replaced tray motor, tested feed. | motor | 60 units delayed | op_rpatel | 2024-06-20 |
| 19 | electrical | 18 | false | Welding Bay | MX-2006 | Welder Pi | 2024-06-21T08:00:00 | 2024-06-21T08:18:00 | Voltage regulator error. | team_electric | Adjusted regulator, tested weld. | blank | No measurable impact | op_lmurphy | 2024-06-21 |
| 20 | other | 180 | false | Offsite Facility | MX-6002 | Remote Test | 2024-06-22T13:00:00 | 2024-06-22T16:00:00 | Power outage due to grid failure. | facility_mgr | Restored backup power and restarted systems. | blank | All production suspended | facility_mgr | 2024-06-22 |
What the 200 rows show
from the 200-row sample- 8%scheduled_
maintenance = true - 35median duration_
minutes - 25parts replaceds
Median 35, from 5 to 720.
- string 10
- integer 1
- float 1
- date 1
- datetime 2
- boolean 1
Columns
16 columns in four groups| column | type | description | example |
|---|---|---|---|
| Text 10 columns | |||
machine_id | string | Unique identifier for the machine experiencing downtime | MX-1001 |
machine_name | string | Human-readable name of the machineoptional | Press Alpha |
location | string | Physical location or area of the machine within the facilityoptional | Assembly Line A |
downtime_type | string | Category or type of downtime (e.g., mechanical, electrical, scheduled maintenance, operator error)5 values | mechanical |
cause_description | string | Detailed description of the cause of the downtime eventoptional | Minor jam in feed tray. |
resolved_by | string | Name or identifier of the technician or team who resolved the issueoptional | tech_jroberts |
resolution_actions | string | Actions taken to resolve the downtime eventoptional | Restored network access. |
parts_replaced | string | Comma-separated list of parts replaced during resolution (if any)optional | belt |
production_impact | string | Description of the impact on production (e.g., units lost, delays)optional | 22 units delayed |
reported_by | string | Name or identifier of the person who reported the downtime eventoptional | op_cmartin |
| Numbers 2 columns | |||
downtime_id | integer | Unique identifier for each machine downtime eventunique · 1 or more | 1 |
duration_minutes | float | Total duration of the downtime event in minutes0 or more | 48 |
| Dates and times 3 columns | |||
downtime_start | datetime | Timestamp when the downtime event began | 2024-06-03T08:14:00 |
downtime_end | datetime | Timestamp when the downtime event ended | 2024-06-03T09:02:00 |
report_date | date | Date when the downtime event was reportedoptional | 2024-06-03 |
| True or false 1 column | |||
scheduled_maintenance | boolean | Indicates if the downtime was due to scheduled maintenance | false |
15 SQL practice questions for the Manufacturing Machine Downtime Logs
Written for this data and checked against it: 12 SQL and 3 Power BI exercises from beginner to advanced. Try the first three free; the practice kit has all 15, a starter .sql file and an answer key with every expected result.
Longest downtime events
Return downtime_id, machine_id, machine_name and duration_minutes for the 10 events with the longest duration_minutes. Sort by duration_minutes from highest to lowest, then by downtime_id ascending.
Tables: manufacturing_machine_downtime_logs · your result: 4 columns, 10 rowsDistinct parts replaced
Return the distinct non-null values of parts_replaced as a single column named parts_replaced, sorted alphabetically.
Tables: manufacturing_machine_downtime_logs · your result: 1 columns, 25 rowsEvents and minutes by downtime type
For each downtime_type, return downtime_type, the number of events as events, and the total duration_minutes as total_minutes. Sort by total_minutes from highest to lowest, then by downtime_type.
Tables: manufacturing_machine_downtime_logs · your result: 3 columns, 5 rows
- 04Long scheduled maintenance eventsBeginner
- 05Average downtime card by typePower BI
- 06Locations with repeated downtimeIntermediate
- 07Duration bucketsIntermediate
- 08Events longer than the overall averageIntermediate
- 09Monthly downtime by typeIntermediate
- 10Types above the overall averagePower BI
- 11Worst machine in each locationAdvanced
- 12Gap since previous downtime per machineAdvanced
- 13Running total of downtime by monthAdvanced
- 14Percent of total downtime by typeAdvanced
- 15Anomalous downtime eventsPower BI
Get the practice kit: the full dataset, all 15 exercises, a starter .sql and the answer key. One-time $3.99.
Get the practice kit · $3.99Use it for
A manufacturing dashboard
The scheduled_
maintenance rate, duration_ minutes by downtime_ type and a breakdown of location. Excel, Power BI or Tableau. Why do 15 of 200 rows have scheduled_
maintenance = true? A class exercise
Hand out the rows and one question. Everyone works from the same 200 rows.
- Rows200148mechanic…5110schedule…14100schedule…
A software demo
Believable rows with machine_
id, machine_ name and location to fill a screen in front of a buyer.
This dataset200 rows16 columns
Yours1,000 rows16 columnslocation: UK only
blueprint · manufacturing-machine-downtime-logs
Behind this dataset
Same schema. As many rows as you need.
These 200 rows came out of a blueprint — 16 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
- Include machine ID and type
- Track downtime duration and frequency
- Segment by shift and operator
- Flag repeated failure events
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-machine-downtime-logs