Equipment Breakdown Log

Construction equipment breaks down — that is engineering reality. A tower crane runs 2,500-3,500 hours per year; a batching plant runs 1,800-2,400 hours; transit mixers do 4,000-5,000 km annually. Wear, fatigue, contamination, operator error, and pure component lottery all contribute to unplanned downtime.

The Breakdown Log is the per-event record that turns these reality events into actionable data. Without it: - Same problem recurs because no one tracks recurrence - Warranty claims fail because no contemporaneous record - Insurance claims rejected for lack of timeline - Maintenance budget guesses high or low; no historical basis - Fleet replacement decisions made on gut feel

With it, the project gains: - Trend analysis — which equipment / which component fails most - Root-cause patterns — operator error vs manufacturing vs wear - Cost data — actual repair + downtime cost per equipment - Fleet decisions — informed hire-vs-own, replace-vs-rebuild - Safety triggers — critical breakdowns auto-flag RCA

Governed by ISO 9001:2015 Clause 7.1.3 (infrastructure) + manufacturer's operating manual + Project Equipment Management Plan (PEMP).

Standard fields per event:

Event header: - Equipment ID + type + make + model + capacity - Breakdown date + time (down to the minute) - Reported by (name + designation) - Location (site / area / activity) - Operator on duty (if applicable) - Activity in progress at time of breakdown

Problem description: - Symptoms — what the operator observed (sound / smoke / leak / vibration / stall) - Suspected cause — first guess from operator + mechanic - Severity classification: - Critical — safety risk + complete stoppage + repair > 24h - Major — productivity impact > 8h - Minor — < 4h impact, no safety issue - Safety implications — was anyone at risk? Was area cleared? - Productivity impact estimate (hours / shift / day)

Repair action: - Diagnostic performed (mechanic's verdict) - Root cause confirmed (different from suspected; common) - Parts replaced (with part numbers + cost) - External service required (manufacturer / authorised service) - Repair cost — labour + parts + service charges - Date + time of restoration - Operator inspection + acceptance

Downtime + impact: - Total downtime hours (breakdown to back-in-service) - Activity affected (slab pour delayed, BBS work halted, etc.) - Schedule impact in days - Cost of production loss (idle labour + delayed milestone penalty) - Replacement equipment used (Y/N — own / hired / borrowed from sister site)

Preventive action: - Root cause category — operator error / manufacturing / wear / contamination / lack of maintenance / aging - Preventive measure (retraining / spare-parts pre-stock / shorter maintenance interval / equipment replacement) - Action owner + target date

Warranty + insurance: - Equipment within warranty period (Y/N) - Insurance coverage — CAR / Equipment / Workmen's Comp - Claim filed (yes/no, reference) - Recovered amount

Monthly review — failure pattern dashboard surfaces the equipment + components needing fleet-level intervention.

1. Verbal reporting only — operator tells supervisor, supervisor tells mechanic; nothing written; pattern undetectable.

2. Symptoms not described — log says "crane down"; no useful information for trend analysis.

3. Root cause = 'misuse' — generic blame put on operator; manufacturing defect or wear pattern missed; same breakdown recurs.

4. Cost not captured — repair done by company workshop; cost not allocated; equipment looks cheap to run.

5. Warranty period missed — within warranty but claim not filed within stipulated days; project pays for what manufacturer should have covered.

6. No downtime calculation — log shows "breakdown" + "restored" but no hours; can't compute MTBF (mean time between failures) or MTTR (mean time to repair).

7. Same equipment breaks down 6 times in 2 months — log has 6 entries but no aggregation; no decision to replace.

8. Safety implications skipped — crane bracket fails; no one investigates; happens again with worker underneath; near-miss / accident.

9. No mechanic accountability — repair done quickly, equipment fails again in 2 days; no link between events.

10. Manufacturer not notified — repeated failures of same component; OEM has technical service bulletin (TSB) for the issue; project doesn't know because didn't escalate.

11. No spare parts stocking decision — same part fails 4 times; not added to spare inventory; equipment down each time waiting for procurement.

12. No fleet-level summary — each project keeps own log; same equipment model fails across projects; company doesn't share data; no fleet improvement.

Companion PMC formats: - Equipment Log (PMC-EQP-LOG-003) — utilisation tracking - Equipment Calibration Register (PMC-EQP-LOG-004) — calibration maintenance - Hire vs Own Analysis (PMC-EQP-RPT-001) - Daily Utilization Report (PMC-EQP-RPT-002) - Near-Miss Register (PMC-SAF-REG-001) — for safety-related breakdowns

Standards + references: - ISO 9001:2015 Clause 7.1.3 — Infrastructure - ISO 55001:2014 — Asset Management Systems - OEM Operating + Maintenance Manuals — primary reference for diagnostics + repair procedures - CMA India Equipment Productivity Norms — benchmarks for MTBF / MTTR - NABL / Auto OE warranty terms — claim documentation requirements - Insurance policies — CAR / Equipment policies typically require event log + photos within 24-48h