Clause 8.5.1.5 of IATF 16949 asks every certified supplier to keep a documented total productive maintenance system. It is also the most frequently raised minor nonconformity in IATF audits anywhere in the world, at 4.28% of all minor findings, ahead of control plans and contingency plans.
The commercial side carries a number too. Deloitte estimates that poor maintenance strategy costs a plant between 5 and 20 percent of its productive capacity, with unplanned downtime costing industrial manufacturers around $50 billion each year.
Three questions worth sitting with before you read further:
- When your CNC went down last Tuesday, could anyone tell you the last time its scheduled service was actually completed, not just planned?
- If an auditor asked today for twelve months of maintenance history on your most loaded machine, how many hours would that take to assemble?
- Do you know which of your machines is quietly eating the most repair spend, or only which one broke most recently?
If those answers came slowly, the gap is not your maintenance team. It is that the maintenance record lives in a register, a WhatsApp group and one supervisor's memory. This article covers what preventive maintenance software does, how it runs on a live shop floor, what the audit actually demands, and why these rollouts fail in Indian MSME plants more often than any vendor will tell you.
TL;DR
- The audit clause most plants fail is maintenance documentation, not maintenance work itself.
- Preventive maintenance software matters less for scheduling than for proving a schedule was followed.
- Machine history built over months is what turns replace-or-repair arguments into a settled answer.
- Operator adoption, not features, decides whether a rollout survives past the first quarter.
- A system that copies your existing register format gets used. One that demands a new process gets abandoned.
- Spare parts linked to maintenance jobs stop the quiet stockouts that stretch a two-hour repair into two days.
What Is Preventive Maintenance Software?
Preventive maintenance software is a digital system that schedules, tracks and records recurring equipment maintenance before a failure happens. It is usually one part of a CMMS, or Computerised Maintenance Management System, which handles assets, work orders and spare parts together.
The shift it makes is small to describe and large in practice. Instead of a maintenance plan sitting in a file and its completion sitting in a register, both live in one record that anyone can pull up.
The asset register
Every machine gets a permanent record: make, model, location, its priority in the process, and its full service history. This is the base layer, and IATF specifically wants the list of equipment on which process capability depends.
The maintenance schedule
Each machine carries its own tasks and intervals, set by elapsed time or by meter reading such as running hours, cycles or units produced. The system raises the job when it falls due rather than waiting for someone to remember.
The completion record
A job is not closed because it was planned. It is closed when the technician records what was done, when, with which parts, and signs it off digitally.
That last point is where most paper systems quietly break, and it is also where audits go wrong. Understanding how the software behaves during an actual shift explains why.
How Preventive Maintenance Software Works on the Shop Floor
Vendors describe this as automation. On a working floor it is closer to a relay, where each step hands off cleanly to the next without anyone chasing a piece of paper. The sequence below is what a single preventive maintenance job looks like end to end.
The steps involved are:
The value is in step six, not step three. Scheduling is the easy part, and most plants already have a schedule that looks fine on paper. What they lack is the closed loop that proves the schedule was followed, which is exactly the evidence an auditor asks to see.
This is the same closed-loop thinking behind production tracking that supervisors actually adopt, and it fails for the same reasons when it is bolted on rather than built in.
Core Features of Preventive Maintenance Software
Feature lists from global vendors read alike because the underlying functions genuinely are standard. What differs is how much each one changes on an Indian MSME shop floor, which is the column vendors leave out.
|
Feature |
What it does |
What it changes on the floor |
|
Automated scheduling |
Raises tasks by calendar interval or by meter reading |
Nobody tracks due dates on a wall chart |
|
Work order generation |
Creates a digital job card when the interval is reached |
The job reaches a named technician, not a group |
|
Digital checklists |
Attaches the procedure, safety steps and manual to the task |
The same job is done the same way on every shift |
|
MRO inventory control |
Links required spares to the job and deducts on completion |
Key spares do not run out halfway through a repair |
|
Sensor and IoT alerts |
Reads vibration, temperature or power draw from hardware |
Early warning arrives before the breakdown does |
|
Mobile access |
Photos, scanning and job closure at the machine itself |
Entry happens at the machine, not three hours later |
Read that last column again, because it is the honest test of any system. A feature that does not change operator behaviour on a Tuesday afternoon is a feature you paid for and will not use.
Before comparing products, it helps to be clear about which maintenance approach you are actually buying software for.
Is your quality data ready for an audit or scattered across notebooks?
Tell us what your plant records look like today. We'll show you what the digital version looks like mapped to your process, not a template.
Preventive, Reactive and Predictive Maintenance Are Not the Same Purchase
Most plants run all three at once without naming them. Getting the distinction right decides how much software you actually need, and stops you paying for sensor infrastructure you are not ready to use.
Reactive maintenance
You fix the machine after it stops. It costs nothing to plan and the most to absorb, because the failure picks its own timing and it is rarely convenient.
Preventive maintenance
You service on a fixed interval whether or not anything looks wrong. It is the approach IATF 16949 is built around, and it is where a plant on paper records gets the fastest return.
Predictive maintenance
You service based on live condition data from sensors, so the work happens only when the machine signals it needs it. It delivers the most and demands the most, in sensors, integration and a maintenance team ready to act on data.
"Poor maintenance strategies can reduce a plant's overall productive capacity between 5 and 20 percent."
Ed Deuel, Mahesh Chandramouli, Chris Coleman and Satish Damodaran, Deloitte Insights. The same research puts predictive maintenance at a 5 to 10 percent cut in overall maintenance costs and a 10 to 20 percent rise in equipment uptime.
The practical read for a mid-sized component plant is to get preventive maintenance recorded properly first. Sensors added on top of an undocumented process only produce data nobody trusts, and we have seen that order get reversed at real cost.
What Actually Changes After You Digitize Maintenance
The benefit worth buying is not fewer breakdowns in the first month. It is that arguments inside your plant start getting settled with a record instead of an opinion.
The changes that show up first:
Point three is where auto component suppliers feel it hardest, and it deserves its own section because the clause behind it is more specific than most plants realise.
Preventive Maintenance Software and IATF 16949 Clause 8.5.1.5
Clause 8.5.1.5 does not ask whether you maintain your machines. It asks you to prove it with a documented system, and this is the precise point where well-run plants lose marks.
The clause expects a documented total productive maintenance system covering the equipment your process capability depends on, defined maintenance tasks and their frequency, a calendar programme for those tasks, and documented maintenance objectives measured over time.
Clause 8.5.1.5, Total Productive Maintenance, is the single most cited minor nonconformity in IATF 16949 audits worldwide, at 4.28% of all minor findings.
IATF Global Oversight, Top Ten Minor Nonconformities, rolling twelve-month data. It ranks above manufacturing process design output (4.03%), control plan (3.91%) and contingency plans (3.90%).
What auditors typically ask for:
- The equipment list, with the reasoning for which machines are on it
- Maintenance objectives that are measured, commonly OEE, MTBF, MTTR and PM compliance
- Evidence that scheduled tasks were completed on time, not merely scheduled
- Records showing what changed when objectives were missed
Notice that three of those four are records, not activity. A plant can maintain its machines diligently and still take a finding, purely because completion evidence lives in a register nobody can reconstruct twelve months back. This is the same documentation logic that governs quality management records and traceability, and it is why we treat maintenance as a records problem before we treat it as a scheduling problem.
Knowing what the clause wants narrows the software question considerably.
Choosing Preventive Maintenance Software: Three Options, One Fit
Search results for this keyword are dominated by global subscription platforms built for facilities teams in North America. They are capable products. They are also built for a buyer who is not you, which shows up during implementation rather than during the demo.
|
Consideration |
Off-the-shelf CMMS |
ERP maintenance module |
Custom-built system |
|
Fit to your process |
You adapt to the software |
Limited, follows ERP logic |
Built around your existing register |
|
Setup effort |
Fast to switch on, slow to adopt |
Long, tied to ERP rollout |
Moderate, mapped before built |
|
Cost pattern |
Per user, per month, forever |
Bundled into licence cost |
One-time build, then support |
|
Operator adoption |
Hardest, unfamiliar workflow |
Poor, designed for office users |
Highest, mirrors current practice |
|
IATF documentation |
Generic, needs configuration |
Often incomplete |
Built to the clause |
|
Best suited to |
Multi-site facilities teams |
Plants already deep in ERP |
MSME plants on paper or Excel |
There is no universally right column. If you run twelve sites with a standing maintenance department, a subscription platform is sensible. If you run one plant with forty machines, three technicians and a register that works, the honest answer is that you need that register digitised faithfully, not replaced with someone else's process. We have written separately about when it makes sense to move a factory off Excel and why off-the-shelf ERP tends to fail smaller manufacturers.
That choice matters less than what happens after go-live, which is where most of these projects quietly end.
Why Preventive Maintenance Software Rollouts Die in the First 90 Days
No vendor publishes this section, so here is what we see on real shop floors in and around Pune. Roughly speaking, the software rarely fails. The rollout does, and it usually fails the same five ways.
A technician who wrote four fields on paper is asked to fill fourteen on a screen. Entry quality collapses within weeks. The fix: start with the fields your register already has, then add.
If the technician has to walk to an office computer, entries get batched at shift end and written from memory. The fix: entry happens at the machine on a phone, or it does not happen honestly.
The system raises work orders and no one is accountable for overdue ones, so the overdue list grows until people stop opening it. The fix: one named owner and a weekly overdue review, from week one.
Machines that were scrapped, moved or renamed carry forward, and the reports stop matching the floor. The fix: a physical walk of the plant before a single record is created.
Management gets dashboards while the person doing the work gets extra typing and nothing back. The fix: give technicians their own view, including what their completion record looks like.
We build for the fifth point deliberately, because a maintenance system that only serves the top of the plant loses the floor within a quarter. When dashboards are built for the people who actually use them, the data underneath stays honest.
Is your quality data ready for an audit or scattered across notebooks?
Tell us what your plant records look like today. We'll show you what the digital version looks like mapped to your process, not a template.
Why Should You Choose Edhaas Digisoft for Preventive Maintenance Software?
Auto component plants need maintenance records that hold up in an IATF audit, not a subscription built for a facilities team in another country. Your register already reflects how your line runs. The work is to make it digital without asking your technicians to learn someone else's process.
How we build it:
Custom-built preventive maintenance systems mapped to your existing schedule and machine list. Barcode and QR based job closure at the machine, with machine and IoT data integration where sensors exist. Modular rollout sized to MSME budgets, starting with your highest-loaded line.
Proven on the shop floor:
Retrieval speed, with any machine's full history available in seconds instead of hours of file searching. Record integrity, with zero missing records and audit-ready documentation. Dispatch confidence, demonstrated when we verified a disputed batch in minutes for a component supplier facing a customer complaint.
We map your workflow first and build the software to fit it, which is why our systems survive the ninety-day window described above. Founded by Prritaa Pirulkar and delivered by a team of fifteen, we work hands-on with plants across Pune, Chakan and Ranjangaon, and we stay reachable after go-live.
Ready to make your maintenance records audit-ready? Schedule a Consultation
Conclusion
Preventive maintenance software earns its place on two fronts that a plant head and an MD feel differently. On the floor it moves breakdowns from surprise to schedule, and it gives technicians a job card that tells them what to do rather than a register that asks what they did. In the boardroom it turns twelve months of machine history into a single screen, which is what settles a replace-or-repair decision and what an IATF auditor asks to see.
The clause that fails most often is a documentation clause, and documentation is the one part of maintenance that software fixes completely. If your last audit produced a maintenance finding, or your next surveillance is inside six months, the record you need is the one being created on your floor today. Our work with auto component manufacturers starts by looking at the register you already keep.
Questions