Preventive maintenance is the work you do before something fails. The software generates those visits from the contract, gives the engineer a checklist and keeps the completed record as evidence you can show.
Preventive maintenance, usually shortened to PM, is planned work carried out on a machine at intervals to keep it running: cleaning, inspection, adjustment, calibration and the replacement of wear items. Preventive maintenance software creates those visits automatically from the contract or the machine's usage, assigns them, gives the engineer a checklist to complete and stores the result against the serial number.
The point is that nobody has to remember. A contract signed in April produces a visit in July without a coordinator scanning a folder, and a completed visit leaves behind a record that can be shown to a customer or an auditor a year later.
Every service department does both. The ratio between them is one of the more honest measures of how well the department is run.
| Breakdown maintenance | Preventive maintenance | |
|---|---|---|
| Starts with | A customer ringing in distress | A date generated from the contract |
| Timing | Whenever it happens, often the worst moment | Planned into the route in advance |
| Parts | Whatever is needed, possibly not in stock | Known wear items, carried on the visit |
| Cost to you | Emergency travel and an unplanned day | A scheduled slot on a planned route |
| Effect on the customer | Downtime, and a difficult renewal conversation | A visit they can see they paid for |
| Can it be eliminated | No | It is the thing that reduces the other |
A department consumed by breakdowns quietly stops delivering preventive visits, which produces more breakdowns. Software does not break that loop by itself, but it makes the loop visible: due visits sit on a list and stay there, in plain sight, until somebody either attends or decides not to.
The schedule should be a consequence of something already recorded, never a separate diary that a coordinator maintains by hand.
A maintenance contract states how many visits are included and over what period. The moment that contract is created, the visits for its whole term should exist as planned jobs on that machine. If the contract is renewed, the next set follows. The contract side is covered in what is AMC software.
Machines outside a contract may still need fixed-interval attention, either because you promised it at installation or because the manufacturer recommends it. These are date-driven schedules tied to the asset rather than to an agreement.
Some equipment is better serviced on hours run, cycles completed or another meter reading than on a calendar. Meter and usage-based schedules raise the visit when the reading crosses a threshold, which the engineer records on the previous job.
Once generated, a preventive visit is assigned like any other job, planned into a technician's route with nearby calls, and closed with a job card. Because it competes for the same people as breakdown calls, seeing both on one schedule is what makes the week plannable.
A visit that produces no record is worth very little three months later, when the customer says the machine was never attended.
A useful preventive visit produces four things:
Calibration records deserve a particular mention. Where a machine's readings matter, the calibration performed and the date it is next due belong on the asset itself, not in a file. Hospitals and laboratories being audited will ask for them, and finding them quickly is the difference between a short conversation and a long one. What any specific audit or regulation requires of your business is something to confirm with your own advisers.
Aura Business generates preventive maintenance schedules from service contracts, supports calibration and compliance checklists, meter and usage-based scheduling, technician allocation and mobile job cards with photo proof and offline working. The product page is preventive maintenance software, and the surrounding workflow is in how service management works.
Preventive maintenance: planned work performed at intervals to keep a machine running, such as inspection, cleaning, adjustment, calibration and replacing wear items, as opposed to repairing a fault after it has occurred.
It is a commercial decision based on the machine, the site conditions and what the market expects for that product. Whatever number you promise, the schedule should be generated from the contract so the promise is delivered rather than remembered.
Yes, where a meter reading reflects wear better than the calendar does. The reading is captured by the engineer on the previous visit, and the next job is raised when it crosses the agreed threshold.
The steps specific to that model, the readings to record, the wear items to inspect or replace, any calibration to perform and a place for the customer signature. Model-specific checklists are what make two different engineers produce the same visit.
Strongly. A customer who has seen every promised visit renews as a matter of routine. A customer who only ever sees an engineer during a breakdown treats the renewal as an expense to question, because from their side the contract produced nothing visible.
A maintenance management system is usually built for a factory maintaining its own machines. A dealer maintaining machines at customer sites also needs contracts, chargeability, spares consumption and invoicing, which is why service contract and field service modules sit alongside the schedules.
Where the visits come from.
The surrounding workflow.
The asset the schedule hangs on.
What the fee has to cover.
Schedules, checklists, calibration.
Contracts that raise the visits.
Tell us how your centre or business works today and we will tell you plainly which parts of this apply to you, and which do not.
Founder-led · Chennai, India · Built and supported by the person who wrote it