Meter Based Maintenance: How to Run It With DMS and AI
By MDMS Team · 8 November 2026

Meter Based Maintenance: How to Run It With DMS and AI

Meter based maintenance schedules service when a machine has done a set amount of work, such as 250 engine hours or 10,000 kilometers, instead of when a date comes up on the calendar. For an equipment dealer or hire business, it means servicing follows how hard each machine is used. It only works if the reading reaches the system that raises the work order. That is where a dealer management system (DMS) or ERP does the heavy lifting, and where AI is starting to add real value.
This guide explains how meter based maintenance works, which readings to use, how to keep the data accurate, and how AI inside a DMS or ERP can turn readings into scheduled, costed and invoiced work.
TL;DR
- Meter based maintenance triggers service from usage (hours, kilometers, cycles), so a busy machine is serviced sooner and an idle one is not serviced for no reason.
- Always start from the manufacturer’s schedule, then adjust for your environment and duty cycle.
- Keep calendar backstops for time-driven risks such as fluids, seals and inspections, especially on hire fleets.
- The weak point is the reading itself: capture it at every service, return and delivery, or import it from telematics.
- AI adds the most when readings, work orders, parts and contracts sit in one system. We built MDMS AI for that setting.
Table of Contents
- What meter based maintenance is
- Which meter readings can trigger service
- How a meter based program works, step by step
- Meter based, calendar based and condition based compared
- Where AI fits in a DMS or ERP
- Keeping meter data accurate
- Applying meter based maintenance by business type
- Getting started in four weeks
- Putting it to work with MDMS
- Our perspective
- FAQ
- Sources
What meter based maintenance is
In a meter based program, each asset has a meter: an hour meter, an odometer or a cycle counter. Each preventive task has a threshold on that meter. When the reading reaches the threshold, the system flags the service as due. DEUTZ Australia says diesel servicing is commonly recommended every 250 to 500 operating hours, but the manufacturer’s manual stays the baseline and harsh environments can call for more frequent service.
Compare that with calendar based maintenance, where the trigger is elapsed time. A generator serviced every six months gets the same attention whether it ran 40 hours or 600. Meter based maintenance fixes that mismatch. It is sometimes called usage based maintenance, and the two terms mean the same thing in practice.

Why dealers and hire businesses care
Equipment dealers service customer machines under warranty, maintenance contracts and ad hoc work orders. Hire businesses run fleets where one excavator might work double shifts for a month and then sit in the yard. In both cases:
- Hours drive wear, so hours should drive the service schedule.
- Warranty terms often reference hours or time, whichever comes first, so the reading matters commercially as well as mechanically.
- Service revenue is predictable when you can see which machines are approaching their next interval.
Which meter readings can trigger service
The right meter depends on the asset. Typical triggers are:
| Asset type | Common meter | Typical use |
|---|---|---|
| Diesel engines, generators, pumps, compressors | Engine or run hours | Oil, filters, coolant, belts |
| Trucks, utes, mobile plant on the road | Odometer kilometers | Drivetrain, brakes, tyres |
| Forklifts and material handling | Hours, sometimes lift cycles | Hydraulics, mast, battery checks |
| Presses, conveyors, packaging lines | Cycle counts | Wear parts, seals |
| Critical rotating equipment | Condition values (temperature, pressure, vibration) | Early warning |
Cummins’ published maintenance schedule is a good example of how manufacturers mix measures. It lists service by hours, distance, fuel burn or elapsed time and says to perform maintenance at whichever interval occurs first. Your system should be able to do the same: hold more than one rule per task and fire on the first one reached.
Setting the threshold
Start with the manufacturer’s interval. Then adjust for:
- Environment. Dust, heat, wet conditions and heavy loads shorten intervals. DEUTZ Australia notes that harsh environments may need more frequent servicing.
- Duty cycle. A machine idling for long periods accumulates hours without equal wear, while one under load wears faster than its hours suggest.
- Fluid and filter findings. If your fitters keep finding oil in poor condition at the scheduled service, shorten the interval. If it is consistently fine, review it with the manufacturer’s guidance in mind.
- Warranty and contract terms. Never set an interval longer than the warranty requires.
Treat every interval as a starting point you review against actual wear, not a rule set once and forgotten.
How a meter based program works, step by step
The flow is the same whether you run it in a spreadsheet or a DMS:
- Define the meter on each asset. One primary meter per asset, with the unit (hours, kilometers) clearly recorded.
- Attach service rules. For example, a minor service every 250 hours, a major service every 1,000 hours, plus a calendar backstop.
- Capture readings. Manually at check-out, return, service or fuel-up, or automatically from telematics.
- Compare reading to threshold. The system calculates hours remaining to the next service, and ideally projects a due date from recent average use.
- Generate and assign the work order. The job lands in the workshop or field service queue with the right checklist and parts.
- Complete and record. The fitter records the actual reading at service, parts used, fluids replaced and observations.
- Reset the next interval. The next threshold is calculated from the actual service reading, not the planned one.
- Review. Compare findings over time and tune intervals.
The records matter. One Australian report on using hour meters to plan servicing for civil contractors recommends keeping the hour-meter reading at service, checked against tracking history, along with the work site and type, parts and fluids replaced, fitter observations, reported defects and the hours at which the next service is due.
Meter based, calendar based and condition based compared
Most fleets end up using all three in some form. The skill is knowing which belongs where.
| Approach | Trigger | Strength | Watch out for |
|---|---|---|---|
| Calendar based | Elapsed time | Simple, good for inspections and compliance | Over-services idle machines, under-services busy ones |
| Meter based | Accumulated usage | Follows real workload, needs only a counter | Needs reliable, regular readings |
| Condition based | Direct health signals (vibration, temperature, oil condition) | Acts on actual condition | Needs sensors, analysis and skills |
For mobile fleets and variable-use equipment, meter based maintenance is usually the practical middle ground. It reflects workload without the instrumentation that full condition monitoring needs. Condition monitoring earns its cost on critical assets where degradation can be sensed directly. Even the national training framework treats it as its own skill: the MEM18010 unit covers selecting a condition-monitoring technique, plotting results and reporting deviations from specification.
Keep a calendar backstop on hire fleets
A machine sitting in the yard still ages. Fluids degrade, seals dry out and corrosion sets in whether or not the hour meter moves. Hire fleets also carry inspection and compliance obligations that are time-driven. So pair every meter rule with a calendar rule, for example “250 hours or 6 months, whichever comes first”. That mirrors the way manufacturers write their own schedules.
Where AI fits in a DMS or ERP
Meter based maintenance generates exactly the kind of structured, repetitive data AI is good at working with: readings over time, service history, parts consumption, job durations. But AI is only as useful as the data underneath it. A standalone maintenance tool sees readings. A DMS or ERP sees readings, work orders, parts stock, supplier lead times, rental contracts, warranty terms and invoices. That wider view is what makes AI practical for a dealership.
Here is where AI inside an integrated system can help a dealer or hire business:
- Projecting due dates. Instead of showing “120 hours to service”, AI can use a machine’s recent usage pattern to estimate the week the service falls due, so the workshop can book the slot and the customer can be contacted early.
- Spotting bad readings. A reading that drops below the last one, or jumps by an implausible amount in a day, is likely a data entry error. Flagging it before it triggers or suppresses a work order protects the whole schedule.
- Preparing the job. When a service comes due, AI can help assemble the likely parts list from past services on the same model, so the parts department can check stock before the machine arrives.
- Highlighting patterns. If a particular model keeps showing filter issues well before the interval, that is a signal to review the threshold.
- Answering questions in plain language. Service managers can ask which machines are due in the next two weeks, rather than building a report.
These are the kinds of jobs we designed MDMS AI to support across the dealership’s own data. It is offered as an add-on to the MDMS modules, and you can see the current pricing on the MDMS site: MDMS AI is 449 AUD per month, and each AI-enabled user is 29 AUD per month per seat. Because AI works from the records in your system, the quality of your meter data decides how much you get out of it.
A practical test for any AI claim
When you evaluate AI in any DMS or ERP, ask where it gets its data. If service readings, parts, warranty and rental contracts live in separate tools, the AI is working with fragments. If they live in one database with a single asset record, it can connect a high-hours machine to its warranty status, the parts on the shelf and the customer’s maintenance contract. This is the principle behind keeping data traveling once instead of being retyped across systems.
Keeping meter data accurate
A meter based program fails quietly. A missed reading means a missed service, and nobody notices until a breakdown. Build habits and checks into the process:
- Make the reading a required field. Check-out, return, delivery and every work order should capture the current hours or kilometers.
- Reject impossible values. The system should block a reading lower than the previous one unless a supervisor confirms a meter replacement.
- Record meter replacements. When a faulty hour meter is swapped, log the offset so history stays continuous.
- Choose the right meter per asset. Some machines have several counters. We cover this in our guide to picking the right meter per asset with telematics import.
- Reconcile regularly. Compare logged hours with telematics or tracking history, as the contractor guidance above recommends.
- Use automatic hours where the fleet justifies it. A Fleetware case study is not needed to make the point: any fleet that depends on drivers writing down numbers will have gaps.
Telematics and tracking
Automatic capture removes the weakest link. Large Australian fleets already do this at scale. Telstra’s case study on Kennards Hire reports a fleet of 120,000 assets, more than 3,200 daily hires across over 180 branches, and a platform that combines IoT inputs with ERP data to generate operational alerts. Most dealers are far smaller, but the principle scales down: live asset data feeding the business system that runs the work.
For smaller equipment, a tracker can supply location, mileage and maintenance reminders. A guide to small equipment GPS tracking explains the options. For checks that are not tied to a meter at all, such as safety inspections on site, a digital logbook for recurring checks can keep records and reminders in one place.
![]()
Applying meter based maintenance by business type
Equipment dealers and workshops
The service department benefits most. Hours on customer machines drive service reminders, warranty checks and parts forecasting. Pair the meter reading with the machine’s serial number and warranty record so that a service due at 500 hours is also a warranty-compliant service. Our equipment asset lifecycle software page shows how the asset record ties these together, and the maintenance contract software page covers contract-based servicing where you commit to intervals for the customer.
Hire and rental businesses
Hire fleets turn assets over daily, so readings must be taken at every return, not only at service. Compare check-out and check-in hours to bill excess usage where the contract allows, and trigger servicing before the next hire goes out. Our equipment hire management software is built around this loop of contract, return, inspection and service.
Generators, pumps and compressors
Run hours are the classic trigger here, often with an annual calendar backstop. See how we handle this on the generator and pump service software page.
Mining and resources
Harsh duty shortens intervals and downtime is expensive, so thresholds need regular review against findings. The mining equipment maintenance software page covers this setting.
Parts departments
When the system knows which services are coming, parts can be picked and reserved ahead of time. That turns the parts counter from reactive to planned. See parts and inventory management software.
Getting started in four weeks
You do not need to convert the whole fleet at once. A staged start works better:
- Week 1: List assets, choose one primary meter each and gather manufacturer service schedules.
- Week 2: Enter service rules, with calendar backstops, for your top five machine models by volume.
- Week 3: Train workshop, yard and counter staff to capture readings at every touchpoint.
- Week 4: Review the first due list, check for missing or odd readings and adjust thresholds.
For a broader view of planned servicing, our preventive maintenance plans guide walks through the plan structure that meter rules sit inside.
Putting it to work with MDMS
MDMS is a dealer management system built for equipment dealerships, with modules you can adopt one at a time. For meter based maintenance, most teams begin with Service Workshop, then add Rental, Parts or Field Service as the program matures. Each of those modules is 59 AUD per month, and the full list, including the Equipment Dealer Suite at 259 AUD per month, is on the pricing page. Optional services include a data upload at 259 AUD one-off per module and a training package at 499 AUD one-off per module. Setup is designed to take under an hour, and your data stays yours.

If you want AI on top of your meter data, MDMS AI sits alongside the modules and is described on the MDMS homepage. If you run a hire fleet, start with the rental contract and fleet software.
Our perspective
Most dealerships we talk to already know what a meter based schedule should look like. The gap is rarely the theory. It is that the hour reading lives on a paper job card, the warranty sits in another system and the parts are ordered after the machine arrives.
We believe meter based maintenance should be a by-product of running the dealership, not a separate project. When the reading is captured on the work order, the rental return and the telematics import, and all of it lands on one asset record, the next service falls out of the data. Nobody has to hunt for it.
That is also why we think AI belongs inside the DMS and ERP rather than beside it. AI that sees the asset, its readings, its history, its parts and its contract can help a service manager plan the week. AI that sees only a spreadsheet export cannot. MDMS AI is designed around that idea, and the modular approach means you can bring in the workshop first and add AI when your data is ready for it.
ModernDMS
FAQ
What is the difference between meter based and preventive maintenance?
Meter based maintenance is one type of preventive maintenance. Preventive maintenance covers any planned servicing done before failure, whether triggered by the calendar, by usage or by condition. The meter based version triggers it when readings such as hours or kilometers reach a set threshold.
How often should diesel equipment be serviced by hours?
DEUTZ Australia says 250 to 500 operating hours is commonly recommended for diesel engines. Your manufacturer’s manual is the applicable baseline, and harsh conditions may need shorter intervals. Confirm the figure for each model and set your system rules to match.
Can AI replace meter readings?
No. AI works from the readings and records in your system, so accurate meters remain the foundation. What AI can do is flag odd readings, project when a service falls due and help prepare the job. Automatic telematics capture reduces the manual effort of getting readings in.
Do I still need calendar-based servicing?
Yes, for time-driven risks. Fluids, seals and corrosion can deteriorate while equipment sits idle, and inspections or compliance checks run on dates. Most fleets use “hours or months, whichever comes first” for exactly that reason.
Can I start with one department?
Yes. MDMS is modular, so a workshop can start with Service Workshop and add Rental, Parts or Field Service later. The meter data you capture in the first module carries over to the others on the same asset record.
Sources
- How Often Should You Service Your Diesel Engine in Australia (DEUTZ Australia)
- Recommended Maintenance Schedule (Cummins)
- Maintenance by the hour: using asset tracking to plan servicing for civil contractors (Blayney Chronicle)
- MEM18010 Perform equipment condition monitoring (training.gov.au)
- Kennards Hire transforming asset management (Telstra)
- Digital logbook for business checks