# Equipment Maintenance Log

> The service and inspection history of a machine — the record that keeps equipment safe, warranty-valid, and running, and that reveals when a unit costs more to keep than to replace.

- Source: https://briq.ai/acu/object/equipment-maintenance-log
- Department: Workforce, Equipment & Supply Chain (https://briq.ai/acu/department/workforce)
- Catalog code: WRK 204 · Level: Practitioner · Track: Operations · 11 min read
- Also known as: Service log, Maintenance history, PM log, Equipment service record, Fleet maintenance record

## Definition

An equipment maintenance log is the maintained record of every inspection, preventive service, repair, and safety check performed on a piece of equipment, together with the meter reading, date, parts, labor, and cost of each event. It exists to keep equipment safe and legal to operate, to preserve warranty and resale value, and to make the economic life of each machine visible. It is not the same as an equipment utilization report or a telematics feed: utilization measures how much a machine is used and telematics streams live operating data, while the maintenance log is the authoritative history of what was done to the machine and what it cost. That history is what distinguishes a well-maintained asset from a liability that happens to still turn on.

## Why it matters

Maintenance is a safety and legal obligation before it is an economic one. Cranes, aerial lifts, hoists, and many other machines carry mandated inspection regimes, and operating them without current inspections is both a citation risk and a genuine hazard. When a machine is involved in an incident, its maintenance log is the first record examined, and a gap in it turns a mechanical failure into evidence that the equipment should never have been in service.

Deferred maintenance is borrowed money at a punishing rate. A skipped preventive service is cheap today and expensive later: a missed oil change becomes an engine, a deferred hydraulic inspection becomes a ruptured line and a contaminated system. The log is where a fleet manager sees whether PM is actually being done on schedule or quietly deferred, and deferral is almost always the leading cause of the catastrophic failures that strand crews and blow schedules.

The log governs the buy-versus-repair and own-versus-rent decision. Every machine reaches a point where its accumulating repair cost per hour exceeds the cost of replacing or renting, and only the maintenance history reveals where a given unit sits on that curve. Without a cost-loaded log, fleet decisions are made on gut feel, and contractors routinely pour money into units that should have been sold two seasons ago.

Maintenance discipline directly protects the schedule. An unplanned breakdown does not just cost a repair; it idles the crew and the work face that depended on the machine, and a critical-path activity waiting on a down excavator loses float exactly like one waiting on an unanswered RFI. Preventive maintenance done on schedule converts unplanned downtime, which is uncontrollable and expensive, into planned downtime, which can be sequenced around the work.

## Lifecycle

1. **Asset commissioning** — A machine enters the fleet with its manufacturer service schedule, warranty terms, and required inspections loaded, and a baseline meter reading recorded. A unit brought into service without its PM schedule defined will simply never be maintained on plan.
2. **Operator daily inspection** — The operator performs and logs a pre-use walkaround — fluids, tires or tracks, leaks, safety devices — before the machine works. Skipped or pencil-whipped daily checks are where developing problems go unnoticed until they fail.
3. **Preventive maintenance scheduling** — Service intervals are tracked by meter hours or calendar, and PM is scheduled before the interval is exceeded. Scheduling that reacts after the interval passes is already deferral, just deferral with a smaller number.
4. **Service execution** — The scheduled service is performed and logged with meter reading, parts, fluids, labor, and findings. A service done but not logged, or logged without the meter reading, breaks both the warranty trail and the interval tracking for the next service.
5. **Repair and unplanned events** — Breakdowns and defects found during inspection are repaired and logged with cause, parts, cost, and downtime. The cause coding here is what later distinguishes a unit with bad luck from a unit that is simply worn out.
6. **Regulatory and safety inspection** — Mandated periodic inspections — annual crane, lift, and similar — are performed by qualified inspectors and the certificates filed against the asset. A lapsed mandated inspection takes the machine out of legal service regardless of its mechanical condition.
7. **Cost accumulation and analysis** — Maintenance and repair costs accumulate against the asset and its operating hours, producing cost per hour over the machine's life. This is the analytical output that feeds ownership-cost and replacement decisions.
8. **Disposition** — When a unit is sold, traded, or scrapped, its complete maintenance history transfers or is archived. A documented service history materially raises resale value; a missing one discounts the machine or kills the sale.

## Anatomy

- **Asset identifier** — The unit number or serial the log belongs to, tied to the equipment master so history follows the specific machine, not a class of machine.
- **Meter reading (hours / miles)** — The engine hours or odometer at the event. The primary basis for interval-based maintenance, and a missing reading breaks the schedule for the next service.
- **Event type** — Daily inspection, preventive service, repair, or regulatory inspection. Distinguishes planned from unplanned events, which is essential for downtime and reliability analysis.
- **Date and downtime** — When the event occurred and how long the machine was out of service. Downtime is the field that links maintenance to the schedule and crew impact.
- **Service / PM interval** — Which scheduled service this satisfies and when the next is due. The forward-looking field that turns the log into a scheduler rather than a diary.
- **Parts and fluids** — What was replaced, with part numbers and quantities. Feeds parts inventory, warranty claims, and the cost detail behind cost per hour.
- **Labor and provider** — Hours and whether the work was done in-house or by a vendor, with the technician or shop. Determines cost and whether warranty labor should have been claimed.
- **Cost** — Parts plus labor plus outside charges for the event, posted against the asset. The accumulation that ultimately drives replacement economics.
- **Findings / defect and cause** — What was found and why it failed. Cause coding is what separates random failure from a wear-out pattern and points to operator or environmental abuse.
- **Warranty status** — Whether the event was covered and whether a claim was filed. Unclaimed warranty repairs are pure lost money, and the log is where they are caught or missed.
- **Regulatory certificate** — For mandated inspections, the inspector, result, and certificate. The proof that keeps the machine in legal service and satisfies auditors.
- **Fault / telematics reference** — Any linked fault code or telematics alert that prompted the event. Ties the streamed operating data to the physical work performed on the machine.

## Failure modes

- **PM deferred until it becomes a repair** — Preventive services are pushed because the machine is busy, and a cheap scheduled service becomes an expensive unplanned failure. The log shows the pattern in hindsight — intervals consistently exceeded before the breakdown — but by then the engine or the hydraulic system is already gone.
- **Service done but not logged** — The work is performed but never entered, or entered without the meter reading. The interval tracking now thinks the service is overdue and either double-services the machine or, worse, the warranty and resale history has a gap that costs real money at claim or sale.
- **Daily inspections pencil-whipped** — Operators sign off the pre-use checklist without actually performing it. Developing defects — a slow hydraulic leak, a cracked weld, a worn safety device — go unseen until they cause a failure or an incident, and the falsified checklist becomes its own liability.
- **Lapsed mandated inspection** — An annual crane or lift inspection lapses because nobody tracked its calendar date, and the machine keeps working. It is now operating out of legal service regardless of mechanical condition, and any incident during the lapse is indefensible.
- **Warranty claims never filed** — A covered repair is performed and paid for out of pocket because no one checked warranty status against the log. Across a fleet this leaks a meaningful sum, and the manufacturer will not backdate a claim that was never submitted in time.
- **Cost not accumulated against the asset** — Repairs are expensed to the job or a generic maintenance account rather than to the specific unit. Cost per hour by machine becomes unknowable, so the fleet cannot tell which units are money pits and replacement decisions are made blind.
- **History lost at transfer or sale** — A machine moves between yards or is sold and its maintenance history does not travel with it. The receiving crew maintains a machine with no known baseline, and a buyer discounts or walks away from a unit that cannot prove how it was cared for.

## Metrics

- **PM compliance rate** — Share of preventive services completed within their interval window. The leading indicator of whether the fleet is being maintained or gradually run into the ground.
- **Planned versus unplanned downtime** — Ratio of scheduled maintenance downtime to breakdown downtime. Rising unplanned downtime signals deferred PM catching up with the fleet.
- **Mean time between failures** — Operating hours between unplanned repairs by unit or class. Falling values flag a machine approaching the end of its economic life.
- **Maintenance cost per operating hour** — Accumulated maintenance cost divided by meter hours, by unit. The core input to repair-versus-replace and own-versus-rent decisions.
- **Regulatory inspection currency** — Share of mandated inspections current and unexpired across the fleet. A pass/fail safety and legal metric, not a trend to watch casually.
- **Warranty capture rate** — Share of eligible repairs actually claimed under warranty. Directly measures money left on the table.
- **Repair reopen rate** — Share of repairs that recur on the same component within a short window. High rates indicate misdiagnosis or a symptom being treated instead of the cause.

## The AI shift

- **Conversational** — A fleet manager asks which units are overdue or approaching a PM interval, which have a mandated inspection lapsing this month, and which machines have a maintenance cost per hour trending past the point where renting would be cheaper — and gets specific units, meter readings, and cost curves with the events cited, instead of paging through service records.
- **Generative** — From a technician's rough repair notes, or from photos of paper service tickets, a model drafts structured log entries — meter reading, event type, parts, labor, cause coding, warranty flag — and drafts the warranty claim where the repair appears covered. The manager confirms extracted values rather than transcribing tickets, which is where meter readings and warranty flags usually get lost.
- **Orchestrated** — The maintenance log stops standing alone. Telematics fault codes and meter hours push into it to trigger and pre-populate service events; downtime posts against the schedule and crew assignments so the field sees which work faces are affected; costs accumulate against the equipment master and job cost; and mandated-inspection dates are monitored and surfaced alongside the certification and safety programs so nothing lapses unseen.
- **Autonomous** — The routine loop runs unattended: PM scheduled and reminders escalated as intervals approach by meter or calendar, mandated-inspection dates watched, telematics faults triaged into recommended service events, warranty eligibility checked on every repair, and cost per hour tracked against replacement thresholds — with a work-order queue and an exception list for the manager. Humans authorize repairs, approve any machine returning to or leaving service, and make the replace-versus-repair call; the system never clears a unit for service on a lapsed mandated inspection and never approves a repair spend on its own.

## Prompts

### Conversational — Weekly fleet review before allocating equipment to next week's work.

```text
Review the fleet's maintenance status. Tell me which units are overdue for preventive service or will exceed their interval within the next 50 operating hours or 10 days, which have a mandated inspection expiring this month, and which units are trending past a maintenance cost per hour that makes renting cheaper than continuing to run them. For each, give me the unit number, the current meter reading, the specific service or inspection due, and the downtime it will require. Then flag any unit with a repair that has recurred on the same component in the last 90 days.
```

**Expected output:** A unit-level status list with meter readings, specific due services, downtime, cost-per-hour flags, and recurring-repair warnings — an actionable fleet picture, not a dump of service history.

**Follow-ups:**

- For the units needing service, what is the least-disruptive window given next week's crew assignments that depend on them?
- Which of the high-cost-per-hour units should I put on the replacement list this quarter?
- Are any of these overdue services under warranty, and are the claims filed?

### Generative — Turning a shop's paper service tickets into structured records.

```text
I am uploading photos of this week's paper service tickets from the shop. For each, draft a structured maintenance log entry: unit number, meter reading, event type (PM, repair, inspection), the parts and fluids used with quantities, labor hours and whether in-house or vendor, total cost, a plain-language finding and probable cause, and a warranty-coverage flag. Flag any ticket missing a meter reading or unit number, and for every repair that looks warranty-eligible, draft the warranty claim with the details needed to submit it. Set the next PM due date for each unit based on the interval and the recorded meter reading.
```

**Expected output:** Structured log entries extracted from the ticket images with missing-field flags, next-PM dates set from meter readings, and drafted warranty claims — records to confirm, not tickets to re-key.

**Follow-ups:**

- Which of these repairs share a cause code and might indicate a systemic problem across similar units?
- Update the cost-per-hour figure for each unit with these entries included.
- List the warranty claims in priority order by dollar value and filing deadline.

### Orchestrated — Connecting telematics faults, the log, and the schedule.

```text
The telematics feed is throwing fault codes on several units. For each fault, tell me what it likely indicates, whether it warrants an immediate service event or can wait for the next scheduled PM, and pre-populate a draft work order tied to the affected unit's maintenance log with the meter reading from the feed. Then cross-check each affected unit against next week's crew assignments and schedule: which crews and activities depend on a machine that needs to come down, and what is the schedule impact of the downtime. Flag any unit that a fault indicates is unsafe to keep operating until serviced.
```

**Expected output:** Fault-by-fault triage with draft work orders pre-populated from telematics, each cross-referenced to dependent crews and schedule impact, and safety-critical faults called out — the equipment data, the log, and the field connected, not siloed.

**Follow-ups:**

- Sequence the required services to minimize total schedule and crew impact across all jobs.
- Draft the notice to the affected superintendents about the equipment that must come down.
- Which of these faults have appeared before on the same unit, and what was done last time?

### Autonomous — Standing policy for continuous fleet maintenance management.

```text
Run our fleet maintenance loop continuously under these rules. Track every unit's PM intervals by meter hours and calendar, and generate a work order and escalate reminders before an interval is exceeded rather than after. Monitor every mandated inspection date and alert well ahead of expiration. Triage incoming telematics fault codes into recommended service events, drafting work orders pre-populated with the current meter reading, and mark any fault that indicates an unsafe condition. On every repair, check warranty eligibility and draft the claim when covered. Accumulate cost per hour against each asset and alert when a unit crosses the replacement threshold. Never clear a unit for service on a lapsed mandated inspection, never authorize a repair spend or return a machine to service on your own, and route every replace-versus-repair decision and every safety-critical fault to me.
```

**Expected output:** A continuously managed fleet with interval-driven work orders, inspection monitoring, fault triage, warranty capture, and replacement flags — where the system schedules and drafts but humans authorize repairs, clear machines for service, and make replacement calls.

**Follow-ups:**

- Show me this week's generated work orders, warranty claims drafted, inspection alerts, and replacement-threshold flags.
- Which units repeatedly slip their PM window, and is that a scheduling or a capacity problem?
- Report total warranty dollars captured versus estimated eligible this quarter.

## Maturity ladder

- **Level 0 — Level 0 — Fix on failure** — Machines run until they break, maintenance is reactive, and records are scattered receipts. Cost per hour is unknown and mandated inspections lapse unnoticed until an incident or audit.
- **Level 1 — Level 1 — Logged and scheduled** — A maintenance log exists with PM intervals tracked by meter or calendar and services recorded. Scheduling and warranty checking are manual, and cost accumulation is partial.
- **Level 2 — Level 2 — Cost-loaded and integrated** — Maintenance cost accumulates against each asset, warranty is checked routinely, mandated inspections are tracked to date, and downtime is connected to the schedule and crews.
- **Level 3 — Level 3 — Assisted** — Log entries are extracted from tickets, telematics faults triage into service events, warranty claims and cost-per-hour analysis are drafted, and replacement candidates are surfaced for review.
- **Level 4 — Level 4 — Operated** — The maintenance loop runs unattended — interval scheduling, inspection monitoring, fault triage, warranty capture, and replacement flagging — while humans authorize repairs, clear machines for service, and decide replacements.

## FAQ

### Is preventive maintenance really cheaper than fixing things when they break?

Almost always, and the log is what proves it for your own fleet. A scheduled service is planned, cheap, and can be sequenced around the work; the unplanned failure it prevents is expensive, damages related components, and idles the crew and the work face that depended on the machine. The economic case is not just the repair cost — it is the avoided downtime and schedule impact, which usually dwarf the service. The units that suffer catastrophic failures are overwhelmingly the ones whose logs show PM intervals repeatedly exceeded.

### Why accumulate maintenance cost against each specific machine?

Because the buy-versus-repair and own-versus-rent decisions can only be made from cost per operating hour by unit, and you cannot compute that if repairs are expensed to jobs or a generic account. Every machine reaches a point where its rising repair cost per hour exceeds the cost of replacing or renting, and the only way to see where a given unit sits on that curve is a cost-loaded log tied to meter hours. Fleets that do not accumulate cost by asset routinely keep pouring money into units that should have been sold, simply because the pattern was never visible.

### How does the maintenance log relate to telematics?

They are complementary, not the same thing. Telematics streams live operating data — location, hours, fault codes, idle time — and is excellent at signaling when something needs attention. The maintenance log is the authoritative record of what was actually done to the machine and what it cost. The strongest setups feed telematics into the log so a fault code triggers and pre-populates a service event, but the log remains the system of record for service history, warranty, and cost, because a data stream is not a documented repair.

## Related objects

- [Fleet Telematics](https://briq.ai/acu/object/fleet-telematics)
- [Equipment Utilization Report](https://briq.ai/acu/object/equipment-utilization)
- [Crew Assignment](https://briq.ai/acu/object/crew-assignment)
- [Certification & Training Record](https://briq.ai/acu/object/certification-training-record)
- [CPM Schedule](https://briq.ai/acu/object/cpm-schedule)
- [Inventory & Warehouse](https://briq.ai/acu/object/inventory-warehouse)