How machine downtime tracking cuts breakdowns before they happen

Why unplanned stops hurt more than the repair bill

An hour of unplanned downtime on a loom or extruder costs more than the mechanic’s time and the spare part. The line stops, operators stand idle, downstream processes starve, and customer shipments slip. In a plant running three shifts, a single breakdown can cascade into overtime, air freight, and lost contracts. The real cost is not the repair; it is the lost throughput and the working capital tied up in stalled work-in-progress.

Preventive maintenance is supposed to stop these failures before they happen. Yet many plants still schedule it by calendar—every 500 hours or every six months—regardless of how hard the machine has worked. Without machine downtime tracking, the maintenance team is flying blind. They replace parts that still have life left, miss components that are about to fail, and leave the plant exposed to the next unplanned stop.

What machine downtime tracking actually captures

Machine downtime tracking is not a stopwatch on the shop floor. It is a structured log that answers four questions for every stop:

• The machine, shift, and operator are recorded so the data can be sliced by asset and team.
• The start and end times are stamped to the second, giving true duration and shift overlap.
• The reason code—mechanical, electrical, material, operator, or external—is selected from a controlled list to prevent vague entries like “breakdown”.
• The production order or cost centre is linked so the stop can be charged to the right job and margin analysis is accurate.

In Facteno, the log is a single screen that operators complete in under thirty seconds. The system timestamps the start when the machine stops and prompts for the reason when it restarts. There is no manual spreadsheet to update, no paper ticket to lose, and no end-of-shift guesswork. Every entry posts automatically to the production ledger, the finance module, and the maintenance backlog.

How the data reveals which machines need attention

Once the plant has logged a few weeks of stops, the data shows patterns that calendar-based maintenance misses. A Pareto chart of downtime hours by machine and reason code typically reveals that 80 % of the lost time comes from 20 % of the assets and causes. For example, a dyeing machine might show:

The chart tells the maintenance team to focus on pump seals and control valves, not on the entire machine. The same data can be sliced by shift, operator, or production order to spot training gaps or material issues. Without machine downtime tracking, these patterns stay hidden in anecdotes and end-of-shift reports.

Illustration: cost of one unplanned stop versus scheduled maintenance

Consider a weaving line that stops for two hours because a bearing seizes. The direct costs are:

• The mechanic’s time: 2 hours × £25/hour = £50.
• The bearing: £120.
• Lost production: 2 hours × 120 metres/hour × £1.80/metre margin = £432.

Total direct cost: £602.

Indirect costs often exceed the direct ones:

• Downstream stitching lines idle for 1 hour: 10 operators × £12/hour = £120.
• Overtime to recover the lost metres: 3 hours × 120 metres/hour × £2.20/metre (overtime rate) = £792.
• Air freight to meet customer deadline: £350.

Total indirect cost: £1,262. Combined cost: £1,864 for one unplanned stop.

If the bearing had been replaced during a scheduled 30-minute stop, the costs would have been:

• Mechanic’s time: 0.5 hours × £25/hour = £12.50.
• Bearing: £120.
• Lost production: 0.5 hours × 120 metres/hour × £1.80/metre = £108.

Total cost: £240.50, or 13 % of the unplanned stop.

How to turn downtime data into a preventive maintenance schedule

With the data in hand, the maintenance team can build a schedule that targets the real failure modes. The steps are:

1. Rank machines by total downtime hours and mean time between failures (MTBF).
2. For each machine, rank reason codes by frequency and duration.
3. Set trigger points: replace the pump seal after 300 hours of runtime, not after six months.
4. Schedule the work during planned production stops or between orders.
5. Update the trigger points every month as new data arrives.

Facteno automates the ranking and trigger points. The system calculates MTBF for each machine and reason code, then flags the next maintenance date on the business control centre. The planner sees the upcoming stops alongside production orders and can slot the work into the least disruptive window.

What to log beyond the stop itself

The stop log is the foundation, but three additional fields turn the data into actionable intelligence:

• The operator’s name is recorded so training gaps can be addressed without blame.
• The shift supervisor’s initials are captured so accountability is clear.
• A free-text note field is provided for details that reason codes miss—“valve stuck open, cleaned with solvent, no parts replaced”.

These fields feed into the quality control module, where defect trends can be correlated with operator training and machine condition. They also feed into the HR module, where attendance and shift patterns can be reviewed if a particular team shows higher downtime.

When software is not the answer

Machine downtime tracking starts with discipline, not with software. If the plant does not log every stop today, an ERP will not magically create the habit. Before investing in any system, run a one-week trial on a single line:

• Assign one operator per shift to log every stop on a paper sheet.
• Require the shift supervisor to sign off the sheet at shift end.
• Review the sheets with the maintenance team the next morning.

If the sheets are incomplete or the reasons are vague, the problem is culture, not technology. Fix the culture first. Once the habit is established, software like Facteno removes the friction and turns the data into decisions.

What to do next week

Pick one production line that has frequent unplanned stops. For seven days:

• Log every stop on a paper sheet or a simple spreadsheet—machine, start time, end time, reason code, operator, shift supervisor.
• At the end of each shift, review the log with the team and ask why the stop happened.
• After seven days, calculate total downtime hours by machine and reason code.
• Identify the top two reasons and schedule a root-cause analysis meeting with maintenance, production, and quality.
• Decide whether the next step is a process change, a training session, or a software trial.

No new system, no capital expenditure—just seven days of data that will show where the real problems lie.