Building the preventive maintenance schedule for production lines, fleets, or facility equipment — neither too early nor too late, no unplanned downtime (known in the literature as Preventive Maintenance Scheduling).
In plain words
Sound familiar?
- The maintenance plan is built at the start of the year and never changes; real failure counts don't match the plan
- There are 1–3 'unexpected' failures per month; when a shift halts, the spare part is either missing or in transit
- Maintenance records live by location/room number, not by asset serial number; historical failure trends are untracked
- The maintenance crew spends 3–5 days a week asking 'which machine can I stop now, which one can wait'
- Some equipment is over-maintained, so the spare-part inventory is bloated; at the same time others fail
- Annual production-downtime cost has never been quantified; the maintenance budget is set as 'last year + X%'
- Maintenance records are on paper or in a local spreadsheet; there's no link to the production system
Why it matters
How it's solved
Technical depth
How it's solved
Technical depthOne-liner: For each asset, balance two costs against each other — service too early (throw away unused part life, waste labor) vs. service too late (unplanned failure + downtime). Use the history of past failures to set the optimum interval per asset; the calendar follows from there.
What the software is really doing is this: for each asset, it computes the optimum maintenance interval from its failure and usage history, then balances the maintenance crew’s weekly workload and pulls in spare-part procurement. Three stages:
1. It collects the asset and data inventory. For each asset: hours of use or cycle count, historical failure dates and causes (automatic from sensors or manual from forms), estimated mean time between failures (MTBF), maintenance duration, parts consumed, maintenance and downtime cost. The data flows from the asset management system automatically, or is entered once cleanly.
2. It computes the optimum maintenance frequency. The software doesn’t try every interval — it builds a probabilistic reliability model (a statistical method that fits past-failure history into a ‘when’s the next failure likely’ curve; in the literature it’s called a Weibull distribution) for each asset and computes the failure probability curve over time. It balances two costs: too-frequent maintenance (throwing away part life, labor cost) versus too-infrequent maintenance (failure probability, downtime cost). The result is an ‘optimum maintenance interval’ per asset (e.g. ’this pump needs maintenance every 850 operating hours’). Then it lays out a weekly schedule: which asset, which day, with which crew, with parts pre-ordered.
3. It reaches the field crew. The plan appears in the maintenance crew app as a daily task list: ‘Monday 09:00 pump 5 — oil change, parts in stock.’ When sensors catch an anomaly (e.g. rising vibration), the software flags it and suggests pulling the task forward. Spare-part procurement is triggered automatically from the maintenance calendar.
It does not replace the maintainer’s experience; think of it as a calculator that scales the maintenance frequencies they hold in their head for 20 assets up to 300, with the failure-history math built in. The decision is still yours, but the maintenance frequency is always numerical and explainable.
Alternatives
Paper logbook / spreadsheet + maintenance chief's head
FreeFree
Who it fits: 10–20 assets, stable use, simple failure modes
- + Zero cost
- + Flexible — priority change on the fly is easy
- + No capex decision
- − Past 30 assets, optimum frequency cannot be computed in someone's head
- − Failure trends invisible — same failure may be repeating
- − No link to spare-part supply chain
- − Insufficient for legal audit records
Local CMMS (computerized maintenance management system)
Enterprise$700–2,500 setup + $200–800/month (regional SMB pricing)
Who it fits: 30–100 assets, stable crew, manufacturing facility or mid-sized hotel
- + Local-language interface and support
- + Mature work-order management, record-keeping, reporting
- + Spare-part inventory integrated
- − Preventive interval is usually a fixed period — not optimized against real failure tendency
- − Probabilistic reliability modeling is limited or absent
- − IoT/sensor integration is weak
International specialized reliability / EAM software
Enterprise$30–100/asset/year, or $100,000–500,000/year licence
Who it fits: 100+ assets, continuous production or 24/7 service, sensor investment in place
- + Mature: probabilistic reliability, sensor-based condition monitoring, multi-site management fully supported
- + Integration with production and ERP ready
- + Algorithms hardened over years
- − High licence and consulting cost
- − Rollout takes 4–9 months
- − Local-language support may be limited, sensor investment may be required
Custom build on an open-source solver
Open SourceLicence free; 10–20 weeks of internal development, or $80,000–250,000 of consulting
Who it fits: Large manufacturer, multi-site chain, in-house data and engineering team
- + No licence cost
- + Fully customizable to asset types and maintenance items
- + Cloud or on your own server
- − Requires internal technical and reliability-engineering capacity
- − Ongoing maintenance is real work
- − Sensor + analytics + work order are separate disciplines; staffing all three is expensive
Recommendation
Ask in the meeting
- Is the preventive maintenance interval a fixed period, or is it computed probabilistically from each asset's failure history? Which reliability distributions are supported (e.g. Weibull)?
- How does sensor data (vibration, temperature, current) tie into the plan — is condition-based maintenance (CBM) ready out of the box?
- Is the spare-part inventory integrated with the maintenance schedule? Are parts auto-ordered against maintenance dates?
- Is workload balancing and crew assignment optimization handled by the system, or is it manual?
- Are legal-audit records (e.g. IATF, ISO 55000, GMP) generated automatically, or do they require extra documentation?
- When equipment goes into planned maintenance, is the production system (e.g. MRP, MES) notified automatically?
- How do you structure the pilot — how many assets, how many weeks, what is the success bar?
- If we stop working with you, how do we get our asset history, failure logs, and maintenance frequency data back? Is there a standard export format?
Technical details
Editor’s note
On the floor this problem is known as “the maintenance calendar”, “the periodic service”, or “the downtime plan”. The academic name is Preventive Maintenance Scheduling. It grew alongside reliability engineering in the 1960s and has since been enriched with probabilistic models, sensor-based condition monitoring, and machine learning. Without that vocabulary, in a software demo you cannot tell whether the “maintenance management module” being pitched is a real engine that computes optimum frequency from failure history, or just a fixed-interval calendar.
The point most often overlooked in this segment: many products advertise “preventive maintenance” but underneath they only run fixed-calendar logic — e.g. “this motor needs an oil change every 500 hours” as a static rule. That helps somewhat; real PM optimization sets the frequency based on a probabilistic curve derived from the asset’s failure history. High-use assets tighten, low-use assets loosen. In any demo, insist on walking through a 20-asset example with 12 months of failure data and different usage intensity, and ask ‘how do you compute the maintenance frequency per asset’.
A step-by-step path for an SMB
Stage 1 — Measure first, plan later. For at least 12 months, log four things:
- Per-asset failure date and cause (by serial number)
- Total operating hours or cycle count (sensor where possible, manual hour-meter or operator log otherwise)
- Maintenance line items and durations (oil change, filter, seal, major overhaul)
- Hourly impact of maintenance/failure downtime (lost units × unit contribution)
Without this baseline you can’t tell which software will deliver which result.
Stage 2 — Run an asset-criticality analysis. Score each asset on three axes: (1) probability of failure, (2) consequence of failure (production downtime, safety, environment), (3) is there an early-warning signal (sensor or operator-noticeable). The product is the criticality score. Group A (high criticality): tight plan; B–C: medium-simple plan. This classification is your knowledge capital — any serious vendor will ask for it first.
Stage 3 — Pilot. Start with 10–20 group-A assets for 12–16 weeks. Define the success criterion in writing, before the pilot: e.g. “in 6 months, group-A unplanned failures down 40%, planned downtime cut in half.” If the bar is missed, the pilot ends — keep that exit right in the contract.
Stage 4 — Rollout. If the pilot lands, scale to all assets over 3–6 months. Maintenance team training runs 2–3 weeks; sensor integration adds 4–12 weeks (sensor capex is separate).
Risks — what can go wrong
- Bad failure-history data. If records are only ‘broke’ / ‘fixed’, the probabilistic model is wrong. Before the pilot, standardize the failure-mode taxonomy.
- Maintenance crew resistance. “Don’t have software tell me when to do maintenance — I know” is common. In the pilot, walk through results with the chief; the software must transparently show which rule was applied and why this frequency was suggested.
- Sensor capex. Moving to condition-based maintenance (CBM) requires sensors (vibration, temperature) at $200–5,000 per asset. Calculate ROI per asset; only critical assets pay back quickly.
- Vendor lock-in. Software that stores asset history, failure logs, and maintenance rules in a proprietary format makes migration hard. Put a clause in the contract: “We can export our data in standard open formats (CSV, XML, or similar) at any time, on request.”
Related cautionary lesson (will be linked once published): “A mid-sized manufacturing facility that dropped its maintenance management software at month 14 — what they missed.”
A technical view of the solution method
This section holds what you’ll need when talking to a software team or a consultant. It is not what the maintainer sees on the daily screen — it is the engine behind the curtain.
The main approaches used for preventive maintenance scheduling:
| Approach | Typical use | Data need | Decision logic |
|---|---|---|---|
| Time-based (fixed interval) | No history yet, simple equipment | Low | “Maintain every X months” |
| Age replacement | Single part, MTBF known | Medium | Replace at optimum age |
| Block replacement | Many similar assets | Medium | Bulk-replace, economic |
| Condition-based (CBM) | Sensored equipment | High | Real-time call from sensor data |
| Prognostic (PHM) | High value + sensors + ML | Very high | Remaining-useful-life prediction |
| Multi-criteria MIP | Mixed integer programming | High | Full optimization with crew and parts |
In practice: under 30 assets with stable use, age replacement or fixed interval suffices. Above 100 assets, multi-shift operation, or sensors in place, CBM + prognostic is preferred. Multi-resource constraints (crew, parts, production) push toward MIP or hybrid approaches.
Objective function choice changes the shape of the solution:
- Total maintenance cost (preventive + repair): “Minimize the budget” — fits tight-budget facilities
- Expected production downtime: “Never stop the line” — fits continuous production
- Reliability / availability target: “99.5% line availability” — fits contract-quality service
- Workload balance: “Even load week to week” — fits cutting personnel turnover
Most real deployments use a weighted blend of all four.
Academic references
Listed in the sources block of this page’s frontmatter. Preventive maintenance has been an active intersection of reliability engineering and operations research since the 1960s; current work is enriched by IoT, machine learning, and digital-twin technology. INFORMS Interfaces and the European Journal of Operational Research archive carry deployment case studies tied to real industrial operations.
Sources
- Wang, H. (2002). A survey of maintenance policies of deteriorating systems. European Journal of Operational Research, Vol. 139 — comprehensive review of maintenance policies.
- Dekker, R. (1996). Applications of maintenance optimization models: A review and analysis. Reliability Engineering & System Safety, Vol. 51 — practitioner-oriented review.
- Nakagawa, T. (2005). Maintenance Theory of Reliability. Springer. The standard text on reliability-maintenance mathematics.
- INFORMS Interfaces — case studies of operations research deployments in maintenance and asset management. informs.org/Publications/Interfaces
Glossary
- Preventive Maintenance
- Scheduled maintenance performed before an asset fails — to avoid unplanned downtime.
- MTBF
- A reliability metric showing how long, on average, an asset operates between two consecutive failures.
- MIP
- An optimization model where some decision variables are forced to be whole numbers (e.g. number of trucks, number of shifts).
Related problems
A New Part Order Arrives — How Do I Get the Optimal Operation Sequence + Machine Choice + Setup?
If you are an SMB CNC manufacturer, tooling shop or engineering workshop producing 50-500 different parts, every new order puts the same decision in front of you: you take the customer's CAD model and have to work out on which machine, in which order, with which tool and fixture, and in how many setups the part will be made. If you simply write down the first feasible sequence that comes to mind, setup time grows 3-5x and parts that miss tolerance are reworked; finding the right sequence means comparing several alternative routings for the same part. When the decision lives only in one engineer's head, the similar-part memory walks out of the door when that engineer leaves, and routings of older parts are not refreshed when a new machine is bought. This page is for production-engineering teams who want to make the operation sequence and the machine assignment written and comparable as the bridge from design to make.
Backward from the Customer Order — Which Raw Material, When, and How Much Should I Order?
For mid-size manufacturing SMBs running 50-500 end items and 200-2,000 raw materials and sub-components (automotive Tier-2, white-goods component shops, furniture and assembly, machinery). With each product's parts list (BOM) and each part's procurement or production lead time on file, the question is: a customer orders 200 units of product X with a fixed delivery week — which raw materials in what quantity must be ordered which week, and which sub-parts must enter assembly when? Material requirements planning (academic name MRP) answers this question backwards from the delivery date and is the core logic underneath every ERP. Done on paper or by 'my supplier always takes 3 weeks' rules of thumb, you either run out and stop the line, or burn cash on excess stock.
Five Suppliers Quote the Same Part — How Much Do I Buy from Each?
You run a manufacturer with 20-200 staff and buy the same raw material or component from 4-8 different suppliers. Each supplier differs on price, quality, lead time, capacity, payment terms, and financial stability; deciding who stays on the approved list and how much of each order goes to whom are two separate calls. A wrong pick can trigger a months-long quality crisis or stop the line when a single supplier fails; the 'cheapest bid wins' approach hides quality, late-delivery, and compliance costs and ends up 15-40% more expensive. Scoring 5-15 bids across 8-12 criteria by hand in a spreadsheet becomes inconsistent fast.