Preventive Maintenance Schedule Rule
The codified logic that determines when preventive maintenance tasks are triggered for each asset class — including time-based intervals, usage-based thresholds (run hours, cycle counts), condition-based triggers, and the escalation rules when PMs are deferred beyond acceptable windows.
Why This Object Matters for AI
AI cannot optimize PM intervals or transition from calendar-based to condition-based maintenance without explicit schedule rules to evaluate and adjust; without them, PM frequencies are either manufacturer defaults never updated or tribal knowledge about 'we do this one monthly.'
Maintenance & Reliability Capacity Profile
Typical CMC levels for maintenance & reliability in Manufacturing organizations.
CMC Dimension Scenarios
What each CMC level looks like specifically for Preventive Maintenance Schedule Rule. Baseline level is highlighted.
Preventive maintenance schedules are tribal knowledge. 'We change the oil on the Haas every 6 months because that's what we've always done.' Nobody knows where the interval came from — was it an OEM recommendation, an engineering calculation, or just what the previous maintenance manager decided? Some equipment gets PM'd too often (waste), some not often enough (failure). The schedule exists only in the planner's head or on a handwritten calendar.
AI cannot evaluate or optimize PM intervals because no schedule rules exist in any system.
Document the PM schedule — list every asset with its PM tasks, intervals, and the basis for each interval (OEM recommendation, experience, regulation).
A PM schedule exists as a spreadsheet or wall calendar listing equipment, tasks, and frequencies — 'CNC machines: oil change every 6 months, spindle bearing inspection annually.' But intervals are all time-based, never adjusted, and the rationale isn't documented. Some intervals are OEM defaults from commissioning; others are guesses. When asked 'why is this PM monthly instead of quarterly?', the answer is 'that's how it's always been.'
AI can generate PM task lists and due dates from the schedule. Cannot evaluate whether intervals are optimal because there's no documented rationale, no link to failure data, and no usage-based alternative to calendar triggers.
Standardize the PM schedule rules — document the trigger logic for each task (time-based, usage-based, or condition-based), the source of each interval, and the escalation rules for deferred PMs.
PM schedule rules are documented with standardized logic: each task specifies the trigger type (calendar interval, run hours, cycle count), the interval value, the source justification (OEM, failure analysis, regulation), and the acceptable deferral window. The planner can see that 'CNC spindle bearing inspection is every 2,000 run hours based on manufacturer recommendation, with a 200-hour deferral window.' But rules are static documents — not linked to actual equipment run hours or condition data.
AI can manage PM scheduling from documented rules and flag approaching due dates. Cannot dynamically adjust intervals because rules don't connect to the operating data (run hours, cycles, condition readings) needed to evaluate whether the interval is appropriate.
Link PM schedule rules to live equipment data — connect run-hour meters, cycle counters, and condition monitoring so usage-based triggers fire from actual equipment operation rather than calendar estimates.
PM schedule rules connect to live equipment data. Usage-based triggers fire from actual run hours and cycle counts read from PLCs. Condition-based triggers reference health score thresholds and oil analysis results. The planner can query 'which PMs are approaching their trigger threshold in the next 30 days based on current operating rates?' and get an accurate projection. Deferral rules automatically escalate when windows are breached.
AI can manage PM scheduling dynamically based on actual equipment usage and condition. Can project future PM demand from production plans and operating rates. Can identify PMs that are consistently deferred and flag the root cause.
Formalize PM rules as machine-readable optimization logic — define the objective function (minimize total cost of PM labor + unplanned failure cost), constraint relationships, and the algorithm for computing optimal intervals from actual failure and usage data.
PM schedule rules are formal optimization models. Each rule specifies the mathematical relationship between operating conditions (load, speed, temperature, contamination level) and optimal PM timing, derived from failure probability distributions and cost functions. An AI agent can compute: 'Given Compressor 7's current operating profile and vibration trend, the optimal oil change interval is 847 hours (not the standard 1,000) because high-temperature operation accelerates oil degradation by 15%.'
AI can compute mathematically optimal PM intervals for each individual asset based on its actual operating conditions and failure history. PM scheduling becomes asset-specific optimization rather than fleet-wide standardization.
Implement self-optimizing PM rules — the optimization model continuously adjusts interval calculations based on actual PM outcomes: did the PM find the expected condition, or was it premature/overdue?
PM schedule rules are self-optimizing and continuously calibrated. After every PM execution, the system evaluates: was the equipment condition consistent with the interval prediction? When PMs consistently find equipment in good condition, intervals extend. When PMs find unexpected degradation, intervals contract. Operating condition changes automatically adjust interval projections. The PM schedule is a living optimization that learns from every maintenance event.
Fully autonomous PM interval optimization. AI maintains continuously optimal PM schedules for every asset based on self-improving models that learn from every PM execution outcome.
Ceiling of the CMC framework for this dimension.
Capabilities That Depend on Preventive Maintenance Schedule Rule
Other Objects in Maintenance & Reliability
Related business objects in the same function area.
Maintenance Work Order
EntityThe transactional record that authorizes and tracks a maintenance task — containing the target asset, problem description, work type (corrective, preventive, predictive), priority, assigned technician, parts consumed, labor hours, completion status, and root cause code upon closure.
Spare Parts Inventory
EntityThe managed stock of maintenance, repair, and operations (MRO) parts — including part numbers, criticality ratings, on-hand quantities, reorder points, lead times, interchangeability data, and the mapping of which parts serve which equipment assets.
Maintenance Procedure
EntityThe step-by-step instructions for performing a maintenance task on a specific asset type — including safety lockout/tagout requirements, tools needed, parts lists, torque specifications, inspection checkpoints, and expected completion time maintained by reliability engineers.
Equipment Failure History
EntityThe structured record of every equipment failure event — capturing failure date, asset identity, failure mode, root cause classification, affected components, time to repair, production impact, and the corrective action taken, linked to the associated work order and inspection findings.
Lubrication Schedule and Specification
EntityThe managed program defining lubrication requirements for each asset — specifying lubricant types, application points, quantities, frequencies, condition monitoring thresholds (viscosity, contamination), and the route maps that lubrication technicians follow on their rounds.
Equipment Health Score
EntityThe composite condition index maintained for each critical asset — aggregating sensor readings, inspection results, failure history, age, operating hours, and maintenance compliance into a normalized health score that reliability engineers use to prioritize attention and predict degradation trajectories.
Repair-versus-Replace Decision
DecisionThe recurring judgment point where maintenance and engineering evaluate whether to repair a degraded asset or replace it — weighing remaining useful life estimates, cumulative repair costs, replacement lead time, production impact, and capital budget availability against defined thresholds.
Maintenance Priority Decision
DecisionThe recurring judgment point where maintenance planners determine which work orders to execute first given constrained labor, parts, and production windows — applying criteria such as asset criticality, safety risk, production impact, regulatory deadline, and health score degradation rate.
Failure Mode Classification Rule
RuleThe taxonomy and classification logic that standardizes how equipment failures are categorized — defining failure mode codes, cause codes, effect codes, and the hierarchical structure (asset class → component → failure mode → root cause) that ensures consistent coding across technicians and shifts.
Work Order Lifecycle Process
ProcessThe end-to-end maintenance workflow from work request initiation through planning, scheduling, execution, quality check, and closure — defining approval gates, parts staging requirements, permit-to-work handoffs, technician sign-off steps, and the feedback loop that updates failure history and health scores upon completion.
What Can Your Organization Deploy?
Enter your context profile or request an assessment to see which capabilities your infrastructure supports.