Overview
Maintenance planning and maintenance scheduling are separate disciplines that depend on each other. Planning determines what the job requires and whether it is ready. Scheduling determines when ready work will be performed and which resources will be committed.
Planning and Scheduling Governance controls the handoff between those disciplines. It defines who decides that work is schedule-ready, who can challenge that decision, who selects work into the schedule, how frozen-schedule changes are authorized, and how shared CMMS definitions remain consistent.
Without this control layer, planner-scheduler disagreements are often settled informally. Jobs sit in limbo, work enters the schedule before it is ready, status definitions drift, and break-in work bypasses normal controls.
What It Is
Planning and Scheduling Governance is the decision-rights and data-control layer connecting Maintenance Planning and Maintenance Scheduling.
It does not tell planners how to build job plans or schedulers how to load crews. It governs the points where the two processes meet.
The key states are:
- Planned: the job package meets planning-quality requirements.
- Schedule-ready: the planner has determined that preventable execution constraints are resolved.
- Scheduled: the scheduler has selected ready work into a defined day, shift, crew, or window.
- Frozen: the committed schedule has reached its controlled change point.
These states represent different decisions and should not be collapsed into one generic “ready” status.
Why It Matters
Strong governance reduces:
- work entering schedules before it is ready;
- planner-scheduler conflict;
- informal status changes;
- unapproved schedule break-ins;
- inconsistent CMMS field definitions;
- conflicting planning and scheduling KPIs;
- schedule disruption caused by unclear decision rights.
The result is a cleaner work-management flow and clearer accountability when a handoff fails.
When to Use It
Use formal Planning and Scheduling Governance when an organization has separate or partially separate planning and scheduling responsibilities, a schedule-ready backlog, frozen schedules, multiple work centers, or recurring disputes over readiness and priority.
A small organization may use the same principles with fewer roles, but it should still distinguish the decisions even when one person performs multiple functions.
Core Principles
- The planning-to-scheduling handoff is a decision supported by evidence, not merely a status change.
- The planner determines readiness against defined criteria.
- The scheduler validates readiness before committing work.
- A scheduler may dispute readiness but should not silently redefine the readiness standard.
- Disputes need a defined escalation path.
- Frozen-schedule changes require authority proportional to consequence.
- Shared CMMS fields require controlled definitions.
- Safety and work authorization remain separate from schedule status.
Process or Lifecycle
- Planned Work leads to Planner Applies Readiness Criteria.
- Planner Applies Readiness Criteria leads to Marked Schedule-Ready.
- Marked Schedule-Ready leads to Scheduler Accepts Readiness?.
- Scheduler Accepts Readiness?, when Yes, leads to Schedule-Ready Backlog.
- Scheduler Accepts Readiness?, when No, leads to Readiness Dispute Logged.
- Readiness Dispute Logged leads to Planning and Scheduling Leads Review.
- Planning and Scheduling Leads Review leads to Resolved?.
- Resolved?, when Yes, leads to Schedule-Ready Backlog.
- Resolved?, when No, leads to Escalate to Governance Authority.
- Escalate to Governance Authority leads to Correct, Accept Exception, or Defer.
- Correct, Accept Exception, or Defer leads to Schedule-Ready Backlog.
- Schedule-Ready Backlog leads to Scheduler Selects Work.
- Scheduler Selects Work leads to Schedule Frozen.
- Schedule Frozen leads to Break-In Requested?.
- Break-In Requested?, when No, leads to Execute.
- Break-In Requested?, when Yes, leads to Apply Approval Tier.
- Apply Approval Tier leads to Record Reason and Displaced Work.
- Record Reason and Displaced Work leads to Execute.
Roles and Responsibilities
| Role | Responsibility |
|---|---|
| Maintenance Manager | Owns overall handoff governance and chairs escalated review |
| Planning Lead | Represents planning standards and resolves readiness disputes |
| Scheduling Lead | Represents scheduling requirements and validates readiness before selection |
| Operations Leader | Represents production/access constraints and participates in material freeze-break decisions |
| Reliability Engineer | Provides risk and consequence context |
| CMMS/Data Steward | Implements approved shared-field and status changes |
| Site Leadership | Resolves high-consequence exceptions and unresolved escalations |
Required Inputs
- Current planning-quality criteria
- Schedule-ready checklist
- Scheduling selection criteria
- Priority definitions
- Frozen-schedule rules
- Break-in reason codes
- Shared CMMS status and field definitions
- Readiness-dispute history
- Break-in history
Required Outputs
- Readiness validation record
- Readiness-dispute record
- Dispute resolution
- Frozen schedule baseline
- Freeze-break approval and reason
- Displaced-work record
- Controlled shared-field definitions
- Governance action list
Step-by-Step Implementation
1. Define the states
Create clear definitions for planned, schedule-ready, scheduled, frozen, and complete. Avoid parallel definitions owned independently by planners and schedulers.
2. Define readiness evidence
The planner should be able to show why a job is ready. Typical evidence may include scope, labor, materials, tools, safety requirements, access, and technical information as defined by the Maintenance Planning process.
3. Separate readiness from selection
A schedule-ready job is eligible for scheduling. It is not automatically entitled to a schedule slot.
The scheduler selects work based on capacity, priority, operations windows, dependencies, and schedule strategy.
4. Create a dispute path
If the scheduler believes a job marked schedule-ready is not executable:
- log the dispute;
- identify the specific readiness criterion in question;
- review it with planning;
- correct the package, accept a documented exception, or defer it;
- escalate unresolved disputes.
5. Define freeze-break authority
Use consequence-based approval tiers rather than allowing any role to modify a frozen schedule freely.
6. Control shared CMMS fields
Fields used by both disciplines—especially status, schedule-ready, and priority—should have one controlled meaning and a documented change process.
7. Review patterns
Review dispute frequency, freeze-break approvals, action closure, and CMMS definition changes to identify systemic problems.
Decision Rules
Readiness decision
- Planner: marks work schedule-ready when planning criteria are met.
- Scheduler: accepts or disputes readiness before schedule selection.
- Planning/Scheduling Leads: resolve first-level disputes.
- Governance authority: resolves disputes that cannot be closed at working level.
Freeze-break tiers
| Tier | Example condition | Approval posture |
|---|---|---|
| Tier 1 — Low consequence | Minor resequencing within existing capacity | Scheduler with supervisor concurrence |
| Tier 2 — Moderate consequence | Displaces committed work, adds overtime, or changes a production window | Maintenance Manager with Operations concurrence |
| Tier 3 — High consequence | Safety, regulatory, or major production consequence | Site/Plant Leadership with appropriate specialist review |
Sites define their own detailed thresholds. Every break-in should have a reason and a displaced-work record.
CMMS Considerations
The CMMS should support controlled fields for:
- planning status;
- schedule-ready flag;
- scheduler accept/dispute decision;
- dispute reason;
- priority;
- scheduled state;
- frozen baseline reference;
- break-in flag;
- break-in approval tier;
- displaced work;
- status-change audit history.
Do not allow planning and scheduling teams to create conflicting meanings for the same status field.
SAP PM Considerations
SAP PM implementations should map these governance states to the site’s actual order statuses, user statuses, planner groups, work centers, priorities, revisions, and scheduling processes. User-status design can support distinctions such as planned, ready, disputed, and scheduled when configured appropriately.
Exact SAP configuration varies. The governance process should be agreed before technical status configuration is changed.
Metrics and KPIs
Schedule-Ready Dispute Rate
Definition: Frequency with which the scheduler disputes work marked schedule-ready.
Formula:
Disputed Schedule-Ready Work Orders ÷ Total Schedule-Ready Work Orders Reviewed × 100
Units: Percent
Interpretation: A rising rate may indicate weak readiness criteria, inconsistent planning application, or scheduler interpretation problems.
Limitations: A low rate is not automatically good if schedulers are reluctant to challenge weak packages.
Freeze-Break Approval Compliance
Definition: Share of schedule break-ins approved at the correct authority tier.
Formula:
Freeze-Breaks Approved at Correct Tier ÷ Total Freeze-Breaks × 100
Units: Percent
Interpretation: Tests whether frozen-schedule change control is being followed.
Limitations: Does not measure whether the break-in itself was a good operational decision.
Governance Board Action Closure Rate
Definition: Share of assigned governance board actions completed by their due dates.
Formula:
Actions Closed by Due Date ÷ Total Actions Assigned × 100
Units: Percent
Interpretation: Indicates whether governance decisions turn into action.
Limitations: Closing weak actions quickly can inflate the metric without improving the process.
Shared CMMS Field Change Control Compliance
Definition: Share of detected shared-field or status changes completed through the approved change process.
Formula:
Approved-Process Shared-Field Changes ÷ Total Shared-Field Changes Detected × 100
Units: Percent
Interpretation: Tests master-data and workflow governance.
Limitations: Requires a reliable configuration-change record.
Common Failure Modes
- Planner marks work ready without evidence.
- Scheduler silently rejects ready work without documenting why.
- Scheduler redefines readiness instead of raising a dispute.
- Planning and scheduling use different definitions for the same status.
- Readiness disputes remain unresolved.
- Every break-in is treated as low consequence.
- Frozen schedules are changed without recording displaced work.
- CMMS status values are added informally.
- Governance meetings become reporting meetings instead of decision forums.
Best Practices
- Keep readiness criteria visible and objective.
- Make schedule-ready and scheduled separate states.
- Log disputes so patterns can be fixed upstream.
- Keep the escalation path short and explicit.
- Review break-in patterns by reason and consequence.
- Require controlled approval for shared CMMS field changes.
- Keep governance focused on handoffs and exceptions, not routine scheduling detail.
- Treat rising dispute rates as process signals rather than individual performance failures.
Maturity Levels
| Level | Practice |
|---|---|
| 1 — Ad hoc | Readiness and schedule changes handled informally |
| 2 — Defined | Decision rights, dispute path, and break-in tiers documented |
| 3 — Managed | Disputes and break-ins logged and reviewed on a defined cadence |
| 4 — Integrated | Shared data and change control actively enforced |
| 5 — Learning | Governance rules improve based on dispute and break-in evidence |
Real-World Example
A manufacturing site finds that approximately one in ten work orders marked schedule-ready is being rejected during the weekly scheduling meeting. Contractor jobs and jobs requiring production access are the most common problem.
Instead of letting planners and schedulers argue job by job, the site logs each dispute against the readiness criterion that failed. The pattern shows that the material and contractor-readiness definition is interpreted differently by the two groups.
The site corrects the shared readiness definition once, updates the CMMS workflow, and uses the same rule going forward. The goal is not to eliminate legitimate disputes; it is to stop repeatedly debating the same undefined boundary.
Audit Questions
- Are planned, schedule-ready, and scheduled clearly distinguished?
- Is every schedule-ready mark supported by evidence?
- Can the scheduler formally dispute readiness?
- Are disputes logged and resolved?
- Is there an escalation path?
- Are break-ins approved according to consequence?
- Does every break-in identify displaced work?
- Are shared CMMS fields governed by one controlled definition?
- Are status changes auditable?
- Are governance actions assigned and closed?
- Do recurring disputes drive process changes?
Related Reliability Method Topics
- Maintenance Planning
- Maintenance Scheduling
- Schedule Compliance
- Backlog Management
Related Tools and Assets
Potential future assets include:
- Planning-Scheduling Governance Charter
- Schedule-Ready Dispute Log
- Freeze-Break Authority Matrix
- Planning-Scheduling Handoff Audit Checklist
- Governance KPI Dashboard
These assets are not created by this document.
References
- RM-MKS-6014 — Planning & Scheduling Governance
- RM-MKS-6002 — Maintenance Planning
- RM-MKS-6003 — Maintenance Scheduling
- RM-MKS-6013 — Schedule Compliance
- RM-MKS-6007 — Backlog Management
Public derivative source: Draft. Publication status: Not Authorized.