{"id":45039,"date":"2026-06-17T19:04:39","date_gmt":"2026-06-17T13:34:39","guid":{"rendered":"https:\/\/www.verdantis.com\/?p=45039"},"modified":"2026-06-29T16:40:06","modified_gmt":"2026-06-29T11:10:06","slug":"planning-and-scheduling","status":"publish","type":"post","link":"https:\/\/www.verdantis.com\/fr\/work-order-management\/planning-and-scheduling\/","title":{"rendered":"Gestion des ordres de travail : planification et ordonnancement"},"content":{"rendered":"
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Work order management is the discipline that turns a maintenance requirement into completed, documented work. Its operational core is planning and scheduling: preparing each work order with the right scope, parts, crew, and time window before a technician ever picks up a tool.<\/p>\n

In asset-intensive industries the gap between a planned operation and a reactive one is measured in millions of dollars. This guide covers work order management end to end: what a work order is and the types you will run, the work order management process and lifecycle, who owns each stage, how planning and scheduling divide, the sourced cost of getting it wrong, and the capabilities that separate a basic work order management system from an AI-native orchestration layer.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Foundations of Work Order Management<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

What it is<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Work order management is the end-to-end process of creating, approving, planning, scheduling, executing, and closing the work orders that maintain physical assets. A work order itself is the system record that authorizes, scopes, and tracks a single unit of maintenance work. Done well, work order management is the bridge between a maintenance need (a failure, an inspection finding, a preventive task) and the physical work on the floor, with a complete audit trail at the end.<\/p>\n

Planning establishes the content of the job. Scheduling establishes when it runs against finite capacity. A work order management system, whether a CMMS, an EAM, or an ERP maintenance module, exists to hold that record and coordinate the handoffs, but the quality of the outcome is set by the discipline applied at each stage, not by the software alone.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Who manages it<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Five roles own different parts of this process. Their KPIs differ, and a healthy operation keeps the roles distinct rather than collapsing them into one overloaded planner.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Maintenance Planner<\/span>

Owns the \"what\" and \"how.\" Scopes future jobs, builds the work package, defines steps, parts, tools, and SOPs. Works one to four weeks ahead, removing barriers before execution.<\/p><\/div>

Scheduler<\/span>

Owns the \"when\" and \"who.\" Levels the planned backlog against crew capacity and shift structures, negotiates equipment downtime windows, and finalizes the daily and weekly schedule.<\/p><\/div>

Reliability Engineer<\/span>

Owns \"why it fails and what matters.\" Defines failure modes, asset criticality, and the predictive strategy. Drives defect elimination and root cause analysis, feeding better jobs back into planning.<\/p><\/div>

Storeroom \/ MRO Manager<\/span>

Owns material readiness. Maintains inventory accuracy, BOM data, and reservations, and assembles kits. A planned job is only executable if the storeroom can guarantee the parts.<\/p><\/div>

Maintenance Supervisor<\/span>

Owns daily execution. Leads the crew, manages schedule break-ins safely, and returns completion feedback and actuals that calibrate the next planning cycle.<\/p><\/div>

Operations \/ Production<\/span>

Owns the asset window. Controls when equipment can be released for maintenance, the constraint that scheduling must reconcile against maintenance demand.<\/p><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Relevant industries<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The discipline matters most where assets are capital-intensive, failure is expensive, and safety or environmental exposure is high.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Oil & Gas<\/b>Continuous process units where an unplanned trip carries safety, flaring, and restart consequences measured per hour in six figures.<\/span><\/div>
Produits chimiques<\/b>Reaction-critical equipment with strict isolation and permit regimes; off-spec product and batch loss compound downtime cost.<\/span><\/div>
Mining & Metals<\/b>Remote sites, heavy rotating equipment, and long lead-time parts make any unplanned stoppage a throughput crisis.<\/span><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Utilities<\/b>Power and water assets with regulatory availability mandates and limited, tightly negotiated outage windows.<\/span><\/div>
Heavy Manufacturing<\/b>High-volume lines where a single failure cascades across the plant and idles entire crews and downstream stages.<\/span><\/div>
Pharmaceuticals<\/b>Validated equipment where an unplanned stoppage can invalidate a batch and trigger costly re-validation and documentation.<\/span><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Types of work orders<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Work order management has to handle several work order types, and the type drives how much planning lead time the job gets and where it sits in the schedule. Most CMMS and EAM systems classify work orders into the categories below.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Work order type<\/th>Trigger<\/th>Typical use case<\/th><\/tr><\/thead>
Corrective<\/th>Raised after a fault or failure is reported<\/td>Breakdown repairs, restoring a degraded asset to service<\/td><\/tr>
Preventive<\/th>Time or usage-based schedule<\/td>Routine inspections, lubrication, filter and seal replacement<\/td><\/tr>
Predictive \/ condition-based<\/th>Sensor, prognostic, or inspection signal<\/td>Acting on a developing failure mode before breakdown<\/td><\/tr>
Emergency<\/th>Urgent safety or operational risk<\/td>Critical failures that break into and displace the schedule<\/td><\/tr>
Inspection \/ compliance<\/th>Regulatory or audit requirement<\/td>Safety checks, statutory inspections, calibration records<\/td><\/tr>
Installation \/ project<\/th>New equipment or modification<\/td>Commissioning, upgrades, multi-craft turnaround scope<\/td><\/tr><\/tbody><\/table><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The planned categories (preventive, predictive, and most inspection work) are where mature operations want the majority of their effort, because planned work is cheaper, safer, and schedulable. Emergency and unplanned corrective work is the load that disciplined work order management is trying to shrink.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

A real-world anchor<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Worked example: centrifugal slurry pump, mineral processing plant<\/div>

Consider a centrifugal slurry pump feeding a grinding circuit in a mining facility. The pumped slurry is abrasive, so the impeller, throatbush, shaft sleeve, mechanical seal, and bearings wear on a predictable curve. If the pump sits on a single train with no installed spare, its asset criticality is high: when it stops, the mill stops.<\/p>

Planning this rebuild means defining the full job: the BOM line items with exact part numbers (impeller, liners, seal kit, bearing set), the step-by-step SOP, the torque specifications for the casing and gland bolting, the lifting plan for the heavy casing, and the isolation protocol for both the slurry line and the motor.<\/p>

Scheduling it means fitting the work into a negotiated mill downtime window, sequencing riggers, mechanical fitters, and electricians so each craft arrives when its predecessor finishes, and confirming the storeroom has staged every part beforehand. The same logic governs a reciprocating compressor in a refinery, where valve kits, piston rings, packing, confined-space permits, and hot-work permits define the package and a turnaround defines the window.<\/p><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Architectural requirement<\/span>

Planning and scheduling are distinct functions owned by distinct roles. The work package is built by the planner and made executable by the storeroom; the scheduler commits it against the asset window controlled by operations. Asset criticality, set by reliability, decides what gets that window first.<\/p><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

The Functional Line: Planning vs Scheduling<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The most common process error in maintenance is treating planning<\/a> and scheduling as one activity. They answer different questions, run on different horizons, and fail in different ways.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Dimension<\/th>Planning, the \"what\" and \"how\"<\/th>Scheduling, the \"when\" and \"who\"<\/th><\/tr><\/thead>
Core question<\/th>What work is required and how is it performed safely?<\/td>When does it run and which crew executes it?<\/td><\/tr>
Primary activities<\/th>Job scoping, step-by-step SOPs, tool and material lists, safety isolation protocols<\/td>Calendar assignment, crew and shift leveling, downtime-window negotiation, daily and weekly finalization<\/td><\/tr>
Time horizon<\/th>One to four weeks ahead of execution<\/td>Daily and weekly, against current capacity<\/td><\/tr>
Key output<\/th>A 100 percent complete, executable work package<\/td>A committed, resource-leveled schedule<\/td><\/tr>
Failure mode<\/th>Incomplete scope; missing parts or permits surface at the tool<\/td>Over- or under-committed crews; low schedule compliance<\/td><\/tr><\/tbody><\/table><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The dependency is one-directional. Scheduling cannot rescue a poorly planned job; it can only commit a placeholder to a slot. If the planner omits a part or the wrong craft is specified, the scheduler optimizes against false constraints and the failure surfaces during execution, at the most expensive possible moment.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Architectural requirement<\/span>

Plan first, schedule second, never in reverse. Planning defines a complete, resource-specified work package; scheduling commits it against capacity and the asset window. Quality flows downstream, so a defect in planning becomes an execution failure that scheduling cannot correct.<\/p><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Current Operational Challenges in EAM and MRO<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Problems with manual and legacy work order management<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Many plants still run work order management on paper, spreadsheets, email threads, or a legacy module bolted onto an ERP. These manual processes share a predictable set of failures: work orders that are never properly closed, no reliable history of parts consumed or time spent, slow distribution of jobs to technicians, and no objective way to prioritize competing requests. The record exists, but it is incomplete, so every downstream decision is made on partial information.<\/p>\n

Maintenance modules inside SAP, other ERPs, and most CMMS platforms solve the system-of-record problem: they centralize work order creation, assignment, and tracking. What they rarely solve is data quality and cross-silo coordination. Work order management in SAP, for example, is only as good as the material master, asset hierarchy, and BOM data feeding it, and those are exactly the records that drift over time. The result is a digitized but still unreliable process, which is why a dedicated work order software solution<\/a> and a clean data layer sit on top of, not instead of, the system of record.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

The silo problem<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Work order planning and scheduling spans three organizations that historically run on separate systems and separate data definitions: maintenance execution, operations and production scheduling, and the warehouse and MRO procurement function.<\/p>\n

Each silo optimizes locally. Maintenance wants the asset now; operations protects production throughput; the storeroom manages stock against a budget. Without a shared data layer, the handoffs between them rely on email, spreadsheets, and phone calls, and every handoff is a point where information is lost or distorted.<\/p>\n

The most damaging break sits between maintenance and the storeroom. A planner reserves a part by material number; the storeroom fulfills against that number. When the same physical part exists under duplicate records, the reservation can point to a record showing zero on hand while identical stock sits under another number. The job stalls on a part the plant already owns.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

The reactive culture<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The second challenge is cultural. In a reactive operation, emergencies set the schedule. Planners spend their time expediting parts and chasing breakdowns rather than preparing future work, which guarantees the next emergency.<\/p>\n

This is measurable. Leading organizations target at least 85 percent planned work and under 15 percent reactive, yet many departments operate near a 50-50 split, which industry analysts treat as a clear signal that firefighting is in control. (Sockeye, 2025)<\/a><\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Architectural requirement<\/span>

The core failure is structural and cultural: siloed systems break the maintenance-operations-storeroom handoff, and a reactive culture spends planning capacity on firefighting. Both are solved only by a shared, accurate data layer that lets planned work displace emergencies.<\/p><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

End-to-End Components and Workflow Linkages<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

What a 100 percent complete work package contains<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

A work package is "complete" only when a technician can execute it without leaving the job to find anything. That standard is exacting.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t