Quick answer
Heavy equipment management software keeps a register of every machine and tracks its engine hours, location, maintenance, repairs, fuel, operator and cost per project. For construction companies, the payoff is knowing which machines are earning, which are idle, which are due for service, and what each one really costs per engine hour. Data comes from hour-meter readings, fuel records and, where machines support it, telematics feeds such as the ISO 15143-3 (AEMP) standard. Start with an accurate register and hour readings, then add telematics machine by machine.
Why heavy equipment needs its own approach
Trucks are managed by kilometres. Excavators, loaders, dozers, rollers, cranes and generators are managed by engine hours. A backhoe can run all day without moving a kilometre, so distance-based fleet tools miss most of what matters.
Construction equipment is also spread across sites, moved between projects, sometimes rented in or rented out, and operated by different people on different shifts. Without a system, the answers to basic questions sit in site logbooks, fuel slips and the equipment manager’s phone. Owners then decide on purchases, rentals and project bids without knowing the real cost of their machines.
Core functions of heavy equipment management software
Equipment register
One record per machine: asset number, type, make, model, serial number, year, capacity, attachments, acquisition cost, ownership status (owned, financed, rented in), current site and current status (working, idle, under repair, in transit). Attach manuals, insurance and permits.
Utilisation by engine hours
Engine-hour readings show how much each machine works. Combined with available hours, they show utilisation, the single most useful number for deciding whether to buy, rent, move or sell a unit. Readings can come from the operator’s daily log, from a supervisor’s hour-meter photo, or automatically from telematics.
Preventive maintenance by hour-meter intervals
Equipment manufacturers schedule service by operating hours. Caterpillar, for example, describes planned maintenance at 250, 500, 1,000 and 2,000 service hours for its machines, notes that exact requirements vary by machine, and tells owners to follow each machine’s Operation and Maintenance Manual. Your software should store each machine’s intervals from its manual, compare them with current hour readings, and warn you before service is due.
Repair history and downtime
Every breakdown, work order, part and labour cost, logged against the machine. Record when the machine went down and when it returned to work. Over time this shows which units, brands or components keep failing and how many working days you lose.
Fuel per machine and per project
Fuel issued from tankers, depots or stations, recorded per machine and charged to the project where it worked. Litres per engine hour is the key ratio. A machine that suddenly uses much more fuel per hour than its usual rate, or than similar units, deserves a look.
Operator assignment
Which operator ran which machine, on which shift and site. This supports accountability for damage and fuel, helps match certified operators to machines, and gives payroll the data for operator pay or allowances where you use them.
Project and job costing
Every hour, litre and repair is charged to a project. Project managers see the true equipment cost of a job, and estimators can use real cost-per-hour figures for the next bid.
Rental vs owned equipment
Rented-in machines need rental periods, rates and return dates tracked so you do not pay for idle rentals. If you rent machines out, you need utilisation and hour readings at release and return, plus maintenance between rentals.
Managing trucks or heavy equipment?
See how NexLogistics supports fleet operations.
Telematics data sources
Manual readings are a valid starting point. Telematics removes the delay and the guesswork. The most useful data points for equipment are:
- Engine hours, including idle hours on many machines.
- Location, to confirm which site a machine is on and to detect unauthorised movement.
- Fuel used or fuel level, for litres-per-hour ratios.
- Fault and diagnostic codes, so the workshop knows about a problem before the operator calls it in.
There are three common ways to get this data:
- Manufacturer (OEM) telematics. Many newer machines leave the factory with telematics. The data sits on the manufacturer’s platform and can sometimes be pulled into other software through an API.
- Aftermarket devices. A tracker wired to power and ignition can record location and run hours on almost any machine. Some devices can also connect to the machine’s engine data network; many heavy machines use the SAE J1939 standard, which carries signals such as total engine hours, fuel level and diagnostic trouble codes.
- Manual input. Daily hour-meter readings and fuel slips, ideally with a photo for verification.
The ISO 15143-3 (AEMP) telematics standard
Mixed-brand fleets have a practical problem: each manufacturer has its own telematics portal. ISO 15143-3 exists to address this.
What it is. ISO/TS 15143-3, “Earth-moving machinery and mobile road construction machinery — Worksite data exchange — Part 3: Telematics data”, specifies a communication schema for sending machine status data from a telematics provider’s server to customer applications over the internet. The Association of Equipment Management Professionals (AEMP) describes it as the AEMP Telematics Standard, based on an API standard AEMP originally developed and later updated together with the Association of Equipment Manufacturers (AEM). It is often called “AEMP 2.0”.
What it covers. The standard deals with data such as location, operating hours, fuel used, distance, idle time and caution or diagnostic codes. One implementation we reviewed exposes data points such as cumulative operating hours, cumulative idle hours, cumulative fuel used, fuel remaining, last known location and fault codes.
What it does not cover. According to ISO, the standard does not cover on-board data collection, on-board protocols such as CAN bus, or the wireless link from the machine to the provider’s server. It standardises the server-to-application step only.
Current status. The 2020 edition (ISO/TS 15143-3:2020) is the published version. ISO lists it for revision, and a new edition (ISO/DTS 15143-3) was in the approval stage as of October 2026. Check iso.org for the current edition before writing it into a tender.
What it means for you. If a manufacturer or telematics provider offers an ISO 15143-3 feed, your equipment software can pull hours, location, fuel and fault data from several brands into one view. Access still has to be arranged with each provider. Caterpillar, for example, documents an ISO 15143-3 API that requires a subscription request and API credentials.
Compatibility caveats for mixed and older fleets
- Not every machine has OEM telematics, and older units often have none. An aftermarket device can usually provide location and run hours, but engine data depends on what the machine exposes.
- Not every OEM portal offers ISO 15143-3, and those that do may require a subscription or dealer activation.
- Data fields differ. Some feeds include fuel used; others do not. Some report idle hours separately; others do not.
- Update timing differs. Some feeds update near real time; others update a few times a day.
- Hour meters drift. A replaced controller or a faulty meter can reset or skew readings. Keep a way to record corrections.
The safe approach is a machine-by-machine discovery: list every unit, check what data it can provide and how, and test before committing to hardware for the whole fleet.
Key KPIs, with example calculations
Example
All figures below are illustrative, not benchmarks.
1. Utilisation %. Engine hours worked ÷ available hours × 100. An excavator is available 26 days × 8 hours = 208 hours in a month and records 146 engine hours. Utilisation = 146 ÷ 208 × 100 = about 70%.
2. Idle ratio. Idle hours ÷ total engine hours × 100. If 40 of those 146 hours were idle, the idle ratio is 40 ÷ 146 × 100 = about 27%. Those are hours of fuel and wear with no productive work.
3. Fuel per engine hour. Litres issued ÷ engine hours. 2,190 litres ÷ 146 hours = 15 litres per hour. Compare with the same machine’s previous months and with similar units.
4. Cost per engine hour. Total monthly cost ÷ engine hours. Suppose fuel is ₱131,400, maintenance and repairs ₱38,000, operator cost ₱30,000 and monthly ownership cost (depreciation, financing, insurance) ₱95,000, a total of ₱294,400. Cost per engine hour = ₱294,400 ÷ 146 = about ₱2,016 per hour.
5. Maintenance compliance. PM services done on time ÷ PM services due × 100. 9 of 10 on time = 90%.
Cost per engine hour is the number that connects the field to finance. It tells you whether a rental quote is cheaper than using your own unit, what rate to bid on a project, and which machines are costing more than they earn. Caterpillar’s own guidance on total cost of ownership follows the same logic: add purchase, financing, insurance, fuel, maintenance, repairs and depreciation, and divide by operating hours to estimate an hourly cost.
Utilisation is just as important on the other side. A low-utilisation machine may be better rented out, moved to another site, or sold, and a consistently over-utilised one may justify another unit.
A practical rollout plan
- Build the register. Walk every yard and site. Record every machine with asset number, serial number, current hour-meter reading and condition. This alone often finds forgotten or misplaced units.
- Load maintenance intervals. Enter service intervals from each machine’s Operation and Maintenance Manual and the date and hours of the last service.
- Start daily hour readings. Operators or site supervisors record hours and fuel each day, with a photo of the hour meter where possible.
- Set up project codes. Every machine-day, litre and repair is charged to a project from day one.
- Run telematics discovery. List which machines have OEM telematics, which offer ISO 15143-3 access, and which need aftermarket devices. Pilot on a few units of each type.
- Connect feeds gradually. Replace manual readings with telematics as each machine is connected and verified against the hour meter.
- Review KPIs monthly. Utilisation, idle ratio, fuel per hour, cost per hour and maintenance compliance, by machine and by project.
- Act on the numbers. Redeploy idle machines, end idle rentals, adjust bids and plan replacements.
Most construction companies also run trucks for hauling and deliveries. Our fleet management system buying guide covers dispatch, POD and trip costs, and our article on truck GPS tracking for business fleets covers device types and driver privacy.
Where NexLogistics fits
NexLogistics manages heavy equipment and trucks in one platform: equipment is measured in engine hours and trucks in kilometres. It covers maintenance and fuel cost control, along with dispatch, trips and proof of delivery for the hauling side of the business.
- Fuel depot management (optional): for companies that run their own fuel depot or tanker, an optional module charges fuel at a weighted-average cost per litre to the vehicle, equipment or project. It is scoped during implementation.
- Telematics: connects to compatible devices and provider platforms, including GPS location, engine data via OBD-II, CAN or J1939, and fuel level sensors. Available data depends on the device, equipment model, protocol support, provider and integration, and compatibility is confirmed during discovery before hardware is quoted.
- Integrations: NexHRIS via API for approved allowances and incentives data, and NexCRM AI for turning won quotations into customers, rates and transport orders. Rental and contracting businesses tracking quotations may find our guide to choosing CRM software useful.
- Data and support: role-based access, cloud hosting with backups, activity history, data export at any time with no exit fee, handling aligned with the Data Privacy Act of 2012, and Philippine-based support.
Pricing is by proposal. Hardware, installation and connectivity are quoted separately.
Want to know what each machine really costs per hour?
See how NexLogistics supports fleet operations.
Frequently asked questions
What is the difference between heavy equipment management software and fleet management software?
Fleet software is usually built around vehicles that travel, measured in kilometres. Heavy equipment software is built around machines measured in engine hours, with project costing, site assignment and hour-based maintenance. Some platforms handle both.
Can I use equipment management software without telematics?
Yes. Daily hour-meter readings, fuel slips and work orders entered by operators and supervisors are enough to start tracking utilisation, maintenance and costs. Telematics makes the data faster and harder to dispute.
What is AEMP 2.0?
It is the common name for the ISO 15143-3 telematics standard, which defines how machine data such as hours, location, fuel and fault codes is sent from a telematics provider’s server to other software. It helps mixed-brand fleets see data in one place.
Will older machines work with telematics?
Often partly. An aftermarket device can usually record location and run hours on older machines. Engine data such as fuel and fault codes depends on what the machine’s electronics provide, so test each model first.
How do I calculate cost per engine hour?
Add a machine’s fuel, maintenance, repairs, operator cost and ownership costs for a period, then divide by the engine hours it recorded in that period. Use the same method every month so you can compare machines and projects.
Sources
- ISO/TS 15143-3:2020, Earth-moving machinery and mobile road construction machinery — Worksite data exchange — Part 3: Telematics data — International Organization for Standardization, checked 24 Oct 2026
- ISO/DTS 15143-3 (draft, Edition 3) — International Organization for Standardization, checked 24 Oct 2026
- Publications: AEMP Telematics Standard, ISO 15143-3 — Association of Equipment Management Professionals, checked 24 Oct 2026
- New Mixed-Fleet Telematics Standard Earns ISO Approval — Utility Contractor Magazine, checked 24 Oct 2026
- ISO-15143-3 (AEMP) API documentation — Proemion, checked 24 Oct 2026
- ISO 15143-3 (AEMP 2.0) API — Caterpillar Digital, checked 24 Oct 2026
- How To: 250-Hour Planned Maintenance on a Cat Dozer — Caterpillar, checked 24 Oct 2026
- How to Calculate Total Cost of Ownership — Caterpillar, checked 24 Oct 2026
- J1939 Explained: A Simple Intro — CSS Electronics, checked 24 Oct 2026
