Construction Equipment Management Software

Many contractors know what a machine cost to buy. Very few know what it costs to run for an hour, which is often the only figure any decision about it needs.

Construction equipment management software holds a fleet as an operating asset rather than as a list of purchases. It carries deployment across sites, hours run and hours idle, fuel issued, preventive servicing due and performed, breakdowns and their downtime, spares consumed, operators assigned, the statutory and contractual documents each machine depends on, and what the machine actually costs per hour it works. With Pentoggle, a contractor can describe its fleet, sites and hire arrangements and generate the starting application around them.

Equipment matters differently to different contractors. For an infrastructure or road contractor the fleet is close to the business itself. For a building contractor it is a smaller set of items whose failure still stops work. Either way the questions are the same, and they are questions about hours rather than about assets.

Many contractors already use Tally or another accounting system for purchases, financing-related entries, depreciation and other financial records. What site and workshop teams often still manage outside that workflow is where the machine is, whether it ran today, how many hours it worked, and when it was last serviced.

Key takeaways

  • A useful equipment cost measure is cost per operating hour, incorporating ownership and operating costs and reflecting the effect of utilisation on fixed cost per productive hour.
  • Comparing a hire rate against a loan instalment is the wrong comparison and usually leads to owning more than is justified.
  • Deferred servicing looks like a saving because its cost is visible and the resulting breakdown cost is not.
  • Breakdown cost is mostly not the repair. It is the crew and the programme waiting on the repair.
  • Statutory documents expire on their own schedule, and a machine stopped for a lapsed paper costs the same as one that has broken down.

What the operator's log and the workshop register do well, and where they stop

Most fleets run on an operator's daily log, a workshop record of repairs, and a mechanic or fleet in charge who knows every machine personally. This is genuine expertise and it catches a lot. Someone who has run the same fleet for years can often diagnose a machine from the sound of it.

The limits are about aggregation and memory rather than skill.

Hours are recorded but rarely totalled

The log has the day. Nobody adds up the month, so nobody knows the utilisation of any individual machine over any period.

Idle hours are not recorded at all

The log captures what the machine did. Time when it was available and not working leaves no entry, which removes the denominator from every useful calculation.

Costs sit in three places

Fuel is with stores or the site. Repairs and spares are with the workshop or a vendor bill. Ownership cost is in accounting. No single record adds them up per machine.

Servicing depends on somebody remembering

Preventive schedules are usually by hours run or by interval. When hours are not totalled, the schedule quietly becomes whatever the fleet in charge recalls, and it slips when the machine is busy, which is exactly when a failure is most expensive.

The knowledge is personal

When the fleet in charge is away or leaves, the history of every machine leaves with them.

What equipment management software holds

The fleet register

Owned and hired machines with identification, capacity, ownership or hire terms, and current location.

Deployment by site and activity

Where each machine is, on what work, and since when, including transfers between projects.

Running and idle hours

Hours worked and hours available but not worked, which is the pair that makes utilisation computable.

Fuel issued per machine

Consumption against hours run and output produced, so expected and actual can be compared.

Preventive schedules and breakdowns

Servicing due by hours or interval, servicing performed, breakdowns with cause and downtime.

Spares and repair cost

Parts consumed and repair bills held against the machine rather than against a general workshop head.

Operators and their records

Who operates which machine, and the licences or authorisations required.

Statutory and contractual documents

Insurance, registration or fitness where applicable, permits and other statutory or contractual documents applicable to each machine, with expiry dates that surface early.

The machine's cost is not its instalment

The most common equipment decision is whether to own or to hire, and a common way of making it is to compare the hire rate against the monthly instalment. That comparison is missing most of the cost.

The useful comparison is cost per operating hour, using a consistent costing method. The calculation can include the machine's ownership or capital cost, fuel, operator cost, preventive servicing, spares and repairs, insurance and applicable statutory costs, together with the effect of utilisation on fixed costs. Depending on the costing method, ownership cost may be represented through depreciation, financing cost or an economic capital-cost approach; these should not simply be added together without a defined methodology.

The important point is to calculate the figure consistently across owned machines and then compare it with the relevant hire cost.

That last component is what makes the comparison flip. If ownership-related fixed costs are spread across operating hours, the fixed-cost component per operating hour rises as utilisation falls. A machine running at 40% utilisation therefore carries substantially more fixed cost per productive hour than the same machine running at 80%, before variable operating costs are considered. A contractor comparing only a loan instalment against a hire rate is leaving out several operating and ownership costs, as well as the effect of utilisation on the cost of productive hours.

Hiring has its own arithmetic. Hire is generally paid against the agreed hire period or usage terms, so an idle hired machine can represent direct cash outflow without productive output, and the discipline of releasing hired plant promptly is worth real money. Owned plant that sits idle feels free because no new invoice arrives, but its ownership cost continues to accrue.

None of this argues automatically for hiring over owning or the reverse. It argues for making the decision using a consistent cost-per-operating-hour calculation based on the contractor's actual utilisation and costs. Tax treatment and the accounting treatment of depreciation or financing are separate questions for your CA.

Preventive maintenance loses an argument it should win

Preventive maintenance is intended to reduce the likelihood and impact of breakdowns, yet many fleets still end up operating reactively, and the reason is a reporting asymmetry rather than ignorance.

A preventive service has a visible cost. It has a bill, it takes the machine out for a day, and it happens on a day somebody chose, which usually turns out to be a day the machine was wanted. Deferring it produces an immediate, visible saving.

A breakdown has an invisible cost. The repair bill is visible and is usually the smaller part. The larger part is the crew that could not work, the pour that was rescheduled, the hired machine brought in at short notice at a poor rate, and the days added to a programme that had no float. None of those are booked against the machine. They dissolve into general site cost, so the machine's record shows a modest repair and nothing else.

Over a year the fleet in charge therefore accumulates evidence that deferring is cheap, because the system only measures one side of it.

Correcting this is not complicated. Record downtime, not only repairs. Hours lost, work stopped and what had to be brought in. Once breakdown downtime is attached to the machine, the comparison becomes visible, and preventive schedules stop being the first thing sacrificed in a busy month. It also makes the case for replacing a particular machine, which is otherwise an argument nobody can win with data.

Applicable documents expire on their own schedules

A machine stopped because a document lapsed is as unproductive as a machine with a failed engine, and considerably more avoidable.

Insurance and any applicable registration, fitness, permits, certifications and operator authorisations each run on their own dates, held in a file or a folder, and typically noticed when somebody needs them. On a fleet of any size the dates are numerous enough that memory is not a system. Requirements differ by state, by machine type and by whether the machine travels on public roads, so what applies to your fleet is worth confirming rather than assuming.

The software contribution is small and reliable. Documents held against the machine with expiry dates that surface in advance, and a view of what is lapsing in the next month across the fleet. It is one of the least interesting things to build and one of the easiest to justify operationally, because the cost avoided is a machine and a crew standing still.

Where equipment management looks different by business type

Why contractors choose Pentoggle for equipment management

Hours recorded with the denominator

Running and idle hours both, which is what makes utilisation and true cost computable.

Every cost against the machine

Fuel, spares, repairs and downtime held per machine rather than in three separate places.

Servicing driven by hours actually run

Preventive schedules that follow the machine's real usage rather than a remembered interval.

Documents that surface before they lapse

Insurance, fitness and permits with expiry visible across the fleet.

Sits around your accounting

Purchases, financing and depreciation records can stay in the accounting system. Pentoggle provides the operational record of deployment, hours, fuel, maintenance, repairs and machine utilisation.

A useful number for equipment management

Cost per operating hour, by machine.

It answers more decisions than any other figure in this area. Whether to hire or own the next one. Whether to keep or replace this one. What to charge a project internally for using it. Whether a hire rate being quoted is reasonable. All of these are usually decided by judgement, and all of them have a computable answer sitting in records the business already generates.

Read it per machine rather than per category, because within any category the spread between the best and worst machine is usually wide, and the average hides both. Read it over a year rather than a month, since maintenance is lumpy and a single expensive repair distorts a short period.

The figure needs idle hours recorded and all costs attributed to the machine. Neither is difficult and both are usually absent, which is why so many fleets are managed on the basis of what the instalment looks like.

Ready to build equipment management software?

An idle machine you own does not feel expensive. It is.

Related resources

Frequently asked questions

Software that tracks a fleet as an operating asset. It typically covers deployment by site, running and idle hours, fuel, preventive servicing and breakdowns, spares and repair cost, operators, statutory and contractual documents and cost per operating hour.

You write. We build.

Your idea, live on the web today. Start with a single sentence.

Start building