How to Allocate Machine Downtime Costs in ERP for Real Profit

Downtime costs are not just idle machines

Most factories track machine uptime, but few allocate the full cost of downtime to the right production lines. When a loom or stitching line stops, the cost isn’t just the machine sitting idle—it’s the wages of operators waiting, the energy still being drawn, and the maintenance crew called in to fix it. These costs get buried in overheads or spread across all products, hiding where real losses occur.

If your ERP only flags downtime as a time-lost event, you’re missing the chance to pinpoint which machines and shifts are dragging profits. The result? Overhead recovery rates that don’t match reality, and no way to prove whether a new maintenance schedule or shift adjustment actually saves money.

Facteno’s ERP ties downtime events to cost centres, so you can see which machines are the biggest drain—and which operators or supervisors are prolonging stops unnecessarily.

What actually stops a machine, and when does the cost hit?

Downtime has three cost drivers, and each lands at a different time:

• The immediate cost is labor and energy during the stoppage. Operators are paid for the shift, even if the machine isn’t running, and utilities keep flowing to idle equipment.
• The near-term cost is maintenance and repairs. A broken belt or clogged nozzle might take hours to fix, and the crew pulling double shifts to cover the loss adds to the bill.
• The hidden cost is the backlog that builds up. If a dyehouse machine is down for two days, the stitching line sits waiting for fabric, and the finished goods pile up in stores—tying up working capital.

Most ERP systems treat these as separate issues, but Facteno links them. For example, if a stitching line stops for a jam, the system logs the downtime, flags the maintenance ticket, and notes the delayed orders. The cost of the stoppage isn’t just the mechanic’s time—it’s the wages of the operators who couldn’t start their next batch, plus the energy used while the line cooled down.

Use the Production module to record downtime codes (e.g., “mechanical failure,” “material shortage”) and tie them to cost centres. This ensures every stoppage is charged to the right department.

Labor costs during downtime are not just wages

When a machine stops, the obvious cost is the wages of the operators standing by. But if you’re using piece rates or shift-based pay, the calculation gets messy. For instance:

Illustration: Say your own scrap rate is 3 per cent, and you pay operators $8 per hour plus a $0.50 bonus per good piece. If a stitching line stops for an hour due to a thread break, you’ve lost:

• Operator wages: $8 × 2 operators = $16
• Lost piece-rate earnings: $0.50 × (expected 40 pieces/hour × 2 operators) = $40
• Supervisor time: $12 × 0.5 hours (they’re called to investigate) = $6
• Total labor cost for that hour: $62

If your ERP only logs “machine idle” without breaking down labor types, you’re undercounting by at least 75 per cent.

Facteno’s HR and Payroll module integrates with production logs so you can allocate wages by role, shift and even individual operator. For example, you might find that supervisors spend 20 per cent of their time troubleshooting stops—time that could be better spent on scheduling or quality checks.

Furthermore, if your factory runs multiple shifts, the cost of downtime varies by time of day. A stoppage at 3 a.m. might mean calling in an overtime mechanic, while a daytime stop could be covered by the regular crew. Facteno’s shift scheduling tools let you model these variations and see which shifts are most efficient.

Energy costs during downtime are often ignored

Energy is the most overlooked downtime cost. Even when a machine is idle, it may still draw power—motors cooling down, lights on in the work area, or backup systems running. In some plants, energy costs exceed labor costs for certain machines.

Here’s how to capture it:

• Check your utility bills for demand charges. Many suppliers charge extra for peak usage, even if the machine isn’t running at full capacity during a stoppage.
• Log standby power for each machine. Use a clamp meter to measure the current draw when the machine is off but plugged in.
• Allocate shared energy costs fairly. If a compressor or chiller serves multiple machines, downtime on one should reduce its share of the bill.

Facteno’s energy costing tools let you tie utility bills to machine usage patterns. For example, if a dyehouse machine stops for two hours, the system can calculate the avoided energy cost (based on your own historical usage) and subtract it from the downtime total.

Trade-off: Some plants turn off machines entirely during downtime to save energy, but this can cause longer start-up times when they restart. Facteno’s downtime logs let you track this trade-off by recording “cold start” vs. “warm standby” events.

Maintenance backlogs turn downtime into a chain reaction

Most factories treat maintenance as a separate cost centre, but unplanned stops often stem from deferred repairs. For example:

Illustration: A loom breaks down twice a month for belt adjustments. Each stop costs $120 in labor and lost output. If you fix it immediately, the total annual cost is $2,880. But if you defer the repairs for three months, the loom fails catastrophically, requiring a $1,500 part and two days of downtime—costing $1,200 in lost production. Total deferred cost: $2,700.

The deferred repair was cheaper in the short term, but the hidden cost was the accumulated backlog. Facteno’s Purchase module can flag parts that are frequently backordered, while the Production module shows which machines have the highest unplanned stoppage rates.

To break the chain:

• Set predictive maintenance thresholds in Facteno. For example, if a pump’s vibration exceeds 0.5 mm/s for three shifts in a row, auto-generate a work order.
• Track mean time to repair (MTTR) by machine type. If your MTTR for stitching lines is 4 hours but should be 1.5 hours, you’ve got a training or parts issue.
• Allocate preventive maintenance costs to the machines they protect. If a $200 service keeps a $50,000 loom running, that $200 is an investment, not an expense.

Use the Business Control Centre to set alerts for machines approaching their MTTR target. This stops small issues from becoming costly stoppages.

Indirect costs: where downtime hides in overheads

Labor, energy and maintenance are the direct costs of downtime, but the biggest losses often lurk in overheads. For example:

Facteno’s Finance module lets you allocate these indirect costs to the machines causing the delays. For instance, if a dyehouse stoppage delays 500 meters of fabric, the system can:

• Calculate the storage cost of that fabric (rack space, insurance, handling) until it’s shipped.
• Track the expedited transport cost if the customer demands rush delivery.
• Log the customer penalty and tie it to the original production order.

Most plants write these off as “general overhead,” but Facteno lets you trace them back to the machine and shift where the downtime occurred. This is critical for proving whether a new maintenance schedule or operator training actually pays off.

How to start allocating downtime costs this week

You don’t need a full ERP overhaul to begin. Start with these steps:

1. Audit one machine’s downtime logs. Pick a critical machine (e.g., your most expensive loom or stitching line) and review its downtime records for the past three months. Note:
   • The duration of each stoppage (was it 10 minutes or 10 hours?).
   • The root cause (mechanical, material, operator error, maintenance).
   • The cost impact (labor, energy, delayed orders).
2. Map the costs to your cost centres. Use a spreadsheet to allocate wages, energy and maintenance to the machine’s cost code. For example:

   Illustration: If a stitching line stops for 2 hours:

   • Labor: $8/hour × 2 operators × 2 hours = $32
   • Energy: $0.15/kWh × 5 kW × 2 hours = $1.50
   • Maintenance: $60/hour × 1 mechanic × 1.5 hours = $90
   • Delayed order: $200 expedited shipping fee
   • Total downtime cost: $324
3. Compare to your current allocation. If you’ve been writing this off as $50 in “general overhead,” you’re missing $274 in hidden losses.
4. Run a trial in Facteno. Use the live demo to test how the system handles your downtime data. Import your audit results and see how Facteno allocates costs across cost centres.

Once you’ve tested the process, roll it out to your top 3–5 machines. Focus on the ones with the highest downtime rates first—they’re the biggest drag on profits.

What to do next week

Pick one of these actions based on your audit:

• If operator errors are the top cause, run a shift-level report in Facteno to see which operators have the highest stoppage rates. Use the Activity Tracking module to review their production logs for patterns (e.g., frequent thread breaks, misaligned fabric). Schedule a 30-minute training session with the worst-performing operators.
• If maintenance backlogs are the issue, generate a preventive maintenance schedule in Facteno. Set thresholds for vibration, temperature and cycle counts, and auto-generate work orders before failures occur.
• If energy costs are hidden, install sub-meters on your top 10 machines. Use Facteno’s energy costing tools to allocate utility bills by machine usage, then compare to your current estimates.
• If indirect costs (WIP, storage, penalties) are the biggest surprise, run a “cost of delay” report in Facteno. This shows how much each hour of downtime costs in finished goods storage, overtime and lost sales.

Start small. Allocating downtime costs accurately takes time, but the first machine you audit will show you where the biggest gaps are.