Improve Maintenance Planning
Shift from firefighting to a plan you can execute.
How to Improve Maintenance Planning?
Moving from breakdown response to planned maintenance is less about buying software and more about getting the mechanics right — one schedule type per job, a realistic lead time, and a checklist that technicians actually follow. Here's how that plays out inside AssetAI.
How the schedule engine actually runs
Every schedule — whether it's preventive, usage/meter-based, predictive, calibration, statutory inspection, or lubrication — is driven by a single form, with the type only changing what triggers the work: time, meter reading, or condition. For time-based work, you set a recurrence (every N days, weeks, or months) from a start date, and the next-due date rolls forward automatically once a work order is generated. A daily job at 06:00 scans every due time and meter schedule across the plant and raises the corresponding work orders; if a planner doesn't want to wait for that cycle, a Generate due button forces the same run on demand.
The detail planners rely on most is the lead-time-in-days field. Rather than a fixed calendar view, it gives you a rolling look-ahead — the system compares lead time against the next-due date each day and decides whether today is the day to surface the work order. That's the actual mechanism behind pulling work into a forward view, and it's worth understanding so you can set lead times that match your parts lead time and crew availability, rather than defaulting to a number that looks safe on paper.
What shows up on the work order — and what doesn't
Each schedule carries a checklist, stored as a simple list of free-text tasks, which renders as bullet lines in the work order's description when it's generated. These checklists don't stay static — fix steps captured in knowledge cards can be pushed into a PM checklist, with numbering stripped and duplicates skipped, so the content planners rely on improves as more issues get resolved and documented.
Once raised, a work order moves through eight statuses — New, Approved, Assigned, In Progress, On Hold, Completed, Closed, Cancelled — giving planners a visible pipeline of what's on track and what's slipping, without needing a drag-and-drop scheduling board. A few things worth setting expectations on:
- There's no shift or holiday calendar behind the scenes — due-date rolling is pure calendar arithmetic and won't skip weekly-offs or plant shutdowns, so build that buffer into your recurrence or lead time.
- Each schedule and work order has one responsible person, defaulted from the asset's technician/owner — there's no workload-balancing or skill-matching engine assigning work across a crew.
- Spares aren't staged or reserved against a schedule; spares visibility lives at reorder-level reporting, so kitting materials ahead of a job is still a manual step.
Where compliance gets tracked
PM compliance is one of four always-on KPIs on the company dashboard — alongside downtime cost, downtime hours, and MTTR — and it's colour-toned green once you clear 90%. For a longer view, the Analytics section opens up 30/90/180/365-day windows on the same KPI, which matters for plants with statutory or calibration obligations that get audited on more than a monthly snapshot. If you're still building the case for structured PM internally, our glossary on what a CMMS actually does and the broader ISO standards reference are useful starting points, alongside background on how planned maintenance ties into OEE and TPM practice. See the full feature set or book a demo on your own asset list.
The weekly planning board — PMs and open work orders in one drag-and-drop view.
Where AssetAI stops short — and why that's by design
A realistic planning tool tells you what it schedules and assigns, not what it doesn't. AssetAI runs the due-work list, the checklist, and the compliance number — it does not run a workload-balancing engine, a shift or holiday calendar, or a drag-and-drop resource board. Each schedule and work order carries one responsible person, defaulted from the asset's technician/owner, so due-date rolling is pure calendar arithmetic — days, weeks, or months — and does not skip weekly-offs or plant holidays on its own. There's no spares-kitting step tied to a schedule either; materials tracking lives at reorder-level reporting, not as a "stage parts for this job" workflow.
For most plants this is the right trade-off: the planning problem that actually blocks Indian manufacturing sites is not an optimisation algorithm, it's getting from a spreadsheet or a diary of due dates to a system that reliably raises the work order and holds someone accountable for it. If your operation genuinely needs skill-matched, capacity-balanced crew rostering on top of this, plan for it as a manual layer your planner runs before assigning — the full scope of what's covered is on /features.
Planning across plants, lines, and statutory obligations
Multi-plant and multi-line operations get the benefit of hanging every schedule and work order off the same location and asset hierarchy already used elsewhere in AssetAI — a planner reviewing due work at one plant sees it in the same structure as another, without a separate configuration per site. This matters for groups already organised around a plant/line/asset tree, a pattern common across /industries in Indian manufacturing.
It also matters for compliance. Statutory inspection and calibration are first-class schedule types alongside preventive, predictive, usage, and lubrication — not a workaround bolted onto preventive maintenance — so a plant with legal inspection obligations or calibration intervals tied to ISO standards tracks them with the same lead-time and checklist mechanics as everything else. For a primer on how this fits the broader category, see what a CMMS actually is, and for background on the standards landscape relevant to Indian plants, see /standards.
Common mistakes when moving off reactive maintenance
Plants moving from breakdown response to scheduled work tend to trip on the same few things:
- One schedule, multiple jobs. Cramming inspection, lubrication, and PM tasks into a single schedule makes the checklist unreadable and the compliance number meaningless. Split by type instead.
- Lead time set too short. If lead time barely exceeds the daily job's own cadence, planners still get surprised. Set it to match how far ahead your team actually needs visibility.
- Checklists that don't update. A checklist frozen at setup drifts from reality. Pushing verified fix steps from knowledge cards into the PM checklist keeps it current without re-authoring from scratch.
- Watching the tile, not the trend. The dashboard's 30-day PM compliance tile is useful for a daily check, but sustained improvement is judged over the 30/90/180/365-day windows on the Analytics view.
Getting these right is most of what separates a plant that's "using a CMMS" from one that's actually planned. If you want to see the schedule form and dashboard against your own asset list, book a demo — plans and rollout options are on /pricing.
Improve Maintenance Planning FAQs
How do I set up a maintenance schedule that triggers work orders automatically instead of manually creating them each month?
Create a schedule record with your asset, choose the maintenance type (preventive, meter-based, or condition-based), and set the recurrence interval—the system then generates work orders daily at 06:00 for every due schedule across your plant. You can also click "Generate due" on demand to pull forward any work orders immediately. The checklist attached to each schedule becomes the task list in the work order, so technicians see exactly what to do without re-entering instructions.
What's the difference between time-based and meter-based maintenance schedules, and when should I use each?
Time-based schedules recur every N days, weeks, or months from a start date—use this for tasks like filter changes or inspections tied to calendar cycles. Meter-based schedules trigger when an asset's usage counter (run hours, cycles, distance) reaches a threshold—use this for work tied to actual machine load rather than elapsed time. Both types set their own basis automatically, so the system knows whether to roll forward a calendar date or wait for the next meter reading.
How can I make sure a work order appears on the calendar *before* the maintenance is actually due, so my team has time to plan?
Add a "lead-time-in-days" value to your schedule—this pulls the due-date window forward by that many days, so a schedule due on the 15th with a 5-day lead time surfaces as due on the 10th. This gives your planners a buffer to source parts, allocate technicians, or coordinate shutdowns before the actual deadline arrives, and is built into the daily 06:00 generation job that raises all work orders across your plant.
Why should I track PM compliance as a KPI, and how does AssetAI help me see it?
PM compliance—the percentage of scheduled preventive maintenance completed on time—directly reflects whether your plant is following planned maintenance or firefighting reactive work; plants with high compliance typically avoid cascading failures and urgent shutdowns. The dashboard shows PM compliance as one of four 30-day KPIs, colour-coded green when you hit 90% or above, so you and your leadership can see at a glance whether schedules are being met or if work is slipping, helping you catch planning gaps early.
Can I attach a task list or checklist to each maintenance schedule so technicians don't have to guess what to do?
Yes—each schedule carries a checklist stored as free-text tasks in a JSON array; when a work order is generated from that schedule, the checklist renders as bullet-point lines in the work order description. This ensures every technician sees the same standard steps for that asset, reducing variation and rework. You can update the checklist once on the schedule and it automatically applies to all future work orders generated from it, which is especially useful when implementing preventive maintenance best practices across multiple assets.
How do I know if a work order is on track or falling behind once it's been assigned to a technician?
Work orders move through eight visible statuses—New, Approved, Assigned, In Progress, On Hold, Completed, Closed, Cancelled—so you can see the pipeline of planned versus slipping work at any time. This pipeline visibility, combined with the PM compliance KPI tracking, lets you spot bottlenecks or delays early; if work is stuck in "Assigned" or "On Hold" longer than expected, you can intervene to unblock it before it affects production. The same status tracking feeds into your glossary/what-is-cmms audit trail, so you have a full record of when and why work moved through each stage.
Our plant runs three shifts. How do I set up maintenance schedules so work orders don't conflict with production schedules on night shifts?
AssetAI lets you tag maintenance schedules with shift preferences and resource availability windows. When a schedule triggers, it considers your shift calendar and only creates work orders during available maintenance windows. You can also set lead times so planners see upcoming work early enough to coordinate with production. Check work order scheduling for configuration options.