9.3 Work Orders Configuration, Work Order Settings, and Maintenance Capacity Management
Key Takeaways
- Work order lifecycle states govern the execution workflow (Created, Scheduled, In progress, Completed, Closed) and control journal creation, journal posting, and checklist completion.
- Work order types categorize maintenance activities (Preventive, Corrective, Inspection, Emergency) and establish rules for auto-scheduling, priority, and mandatory fault logging.
- Work order pools group work orders for collective batch processing, plant shutdowns, or contractor dispatching.
- Maintenance capacity planning matches estimated work order labor hours against maintenance worker group working time calendars to evaluate overload and resource utilization.
- Fault management utilizes a four-tier taxonomy (Symptoms, Areas, Causes, Remedies) configured in the Fault designer to build reliability datasets and calculate MTBF.
9.3 Work Orders Configuration, Work Order Settings, and Maintenance Capacity Management
Quick Answer: A Work Order in D365 SCM represents an authorized maintenance job containing job lines, asset assignments, resource requirements, checklists, and spare part reservations. Work orders progress through sequential Work Order Lifecycle States (e.g., Created, Scheduled, In progress, Completed, Closed) governed by Lifecycle Models, which enforce stage gates such as mandatory checklist sign-offs and journal posting permissions. Work orders are classified by Work Order Types (Preventive, Corrective, Inspection, Emergency) and aggregated via Work Order Pools. Maintenance capacity planning compares estimated work order labor requirements against Maintenance Worker Groups and their working time calendars to identify workload deficits before dispatching.
Work Order Lifecycle States and Models
A Work Order Lifecycle Model (Asset management > Setup > Work orders > Lifecycle models) defines the valid progression of operational and financial stages for maintenance jobs. Every work order type is assigned a default lifecycle model.
[Created] ──> [Scheduled] ──> [In progress] ──> [Completed] ──> [Closed]
│
└──> [On Hold / Waiting for Parts]
Stage-Gate Controls on Lifecycle States
Each Work Order Lifecycle State (Asset management > Setup > Work orders > Lifecycle states) controls execution rules via parameter toggles:
| Parameter Toggle | System Function | Operational Governance |
|---|---|---|
| Active | Flags the work order as open and requiring operational attention. | Enabled from Created through In progress. Cleared when Completed or Closed. |
| Set actual start | Automatically timestamps the work order's actual start date/time with the system timestamp when transitioning into this state. | Configured on the transition to In progress. |
| Set actual end | Automatically timestamps the work order's actual completion date/time when transitioning into this state. | Configured on the transition to Completed. |
| Create journal | Enables technicians and clerks to create consumption journals (Hours, Items, Expenses) against the work order. | Typically enabled only when the work order reaches In progress or Completed. |
| Post journal | Permits posting of consumption journals to inventory and the General Ledger. | Prevents premature financial postings while work is still in Created or Scheduled. |
| Close work order | Finalizes the work order, preventing further journal entries, line additions, or cost adjustments. | Enabled exclusively on the final Closed state. |
| Checklists | Requires all mandatory maintenance checklists to be signed off before advancing to this state. | Typically enforced before entering Completed. |
Work Order Types: Categorization and Operational Routing
A Work Order Type (Asset management > Setup > Work orders > Work order types) classifies the operational nature and urgency of maintenance jobs:
1. Core Work Order Types
- Preventive: Scheduled recurring servicing generated automatically by maintenance plans or rounds (e.g., 500-hour oil change, quarterly filter swap).
- Corrective: Unplanned repair jobs created to restore equipment that has broken down or degraded below acceptable operational thresholds.
- Inspection: Non-destructive examination, safety compliance audits, vibration analysis, or condition measurement tasks.
- Emergency: Critical, high-priority breakdown repairs where production lines are stopped or safety hazards exist, bypassing normal scheduling queues.
2. Work Order Type Configuration Settings
- Lifecycle model: Specifies the allowable state transition flow for work orders of this type.
- Mandatory fault management: Enforces capturing fault symptoms, areas, causes, and remedies before a corrective or emergency work order can be completed.
- Auto-schedule: Determines whether work orders generated from preventive maintenance plans are automatically scheduled upon creation.
- Project type: Dictates whether associated Project Management and Accounting projects are configured as
Time and materialorInternal.
Work Order Pools and Maintenance Worker Groups
Managing hundreds of active work orders across an enterprise requires grouping mechanisms for scheduling, dispatching, and execution.
1. Work Order Pools
A Work Order Pool (Asset management > Setup > Work orders > Work order pools) is a logical grouping mechanism used to batch work orders for operational convenience. Typical pool implementations include:
- Shutdown 2026: All preventive and overhaul jobs reserved for execution during an annual plant turnaround.
- Electrical Shop: Work orders routed specifically to the high-voltage bench.
- Contractor Services: Work orders requiring specialized third-party technician execution.
- Weekend Maintenance: Routine jobs deferred to non-production weekend shifts.
2. Maintenance Worker Groups and Workers
A Maintenance Worker Group (Asset management > Setup > Workers > Maintenance worker groups) categorizes maintenance personnel by trade, skill set, certification, or department (e.g., Electricians, Mechanical Fitters, Instrument Techs, Lubrication Techs).
- Worker Setup: Maintenance workers are linked directly to Human Resources worker profiles (Asset management > Setup > Workers > Workers).
- Group Assignment: Workers are assigned to one or more maintenance worker groups, establishing their availability for work order job line scheduling.
Maintenance Capacity Planning and Load Analysis
Maintenance capacity planning ensures that maintenance departments do not schedule more work order jobs than available technician hours allow (Asset management > Inquiries > Capacity load).
+-------------------------------------------------------------------------+
| MAINTENANCE CAPACITY LOAD ENGINE |
+------------------------------------+------------------------------------+
| CAPACITY DEMAND | CAPACITY SUPPLY |
| - Work Order Job Lines | - Maintenance Worker Groups |
| - Estimated Hours (Forecast) | - HR Working Time Calendars |
| - Unscheduled Maintenance Plans | - Standard Shift Hours (40h/wk) |
| - Work Order Types Filtered | - Less: Holidays & Planned Leaves |
+------------------------------------+------------------------------------+
| ▼ |
| CAPACITY UTILIZATION REPORT |
| [ Week 42: Available = 160h | Required = 192h | Overload = +20% ] |
| Resolution: Defer preventive rounds or authorize overtime shifts |
+-------------------------------------------------------------------------+
1. Integrating Working Time Calendars
Maintenance worker groups link to Working Time Calendars configured in Organization Administration. The calendar defines standard working hours (e.g., 5 days x 8 hours = 40 hours/week per worker), public holidays, plant downtime, and scheduled shift patterns.
2. Calculating Capacity Load
The Capacity load inquiry calculates labor demand by reading the Estimated hours defined on work order job lines and unreleased maintenance schedule lines across a specified date interval:
- Capacity supply: Total available technician hours = (Number of active workers in group) x (Calendar working hours minus absences).
- Capacity demand: Sum of estimated labor hours on scheduled and unscheduled maintenance jobs assigned to the group.
- Capacity load percentage:
(Capacity Demand / Capacity Supply) * 100.
3. Load Resolution Strategies
When the capacity load inquiry reveals an overload (>100% capacity utilization):
- Reassign Worker Groups: Transfer non-specialized jobs from overloaded mechanical fitters to general utility technicians.
- Adjust Scheduled Dates: Shift low-priority preventive work order lines to subsequent calendar weeks.
- Engage External Contractors: Assign overloaded jobs to a Contractor work order pool backed by external service agreements.
Fault Management Architecture and Reliability Analytics
To drive continuous reliability engineering, D365 SCM incorporates a structured four-tier Fault Management taxonomy (Asset management > Setup > Faults):
[1. Fault Symptom] ──> What abnormal condition was observed?
│ (e.g., Excessive Vibration, Motor Overheating, Oil Leak)
▼
[2. Fault Area] ──> Which subsystem or component failed?
│ (e.g., Drive Bearing, Hydraulic Seal, Inverter Board)
▼
[3. Fault Cause] ──> Why did the failure occur?
│ (e.g., Lubrication Starvation, Thermal Fatigue, Misalignment)
▼
[4. Fault Remedy] ──> What corrective action resolved the issue?
(e.g., Replace Bearing, Flush Hydraulic Lines, Realign Shaft)
1. The Fault Designer
The Fault Designer (Asset management > Setup > Faults > Fault designer) creates relational matrices linking valid symptoms, areas, causes, and remedies. Rather than allowing technicians to enter arbitrary text, the designer guides users through valid engineering combinations based on asset types.
2. Mandatory Fault Registration
On the Work Order Type setup, the Fault management parameter can be set to:
- Not mandatory: Technicians can complete work orders without logging fault entries.
- Mandatory: Technicians are strictly blocked from transitioning the work order to
Completeduntil a complete fault sequence (Symptom -> Area -> Cause -> Remedy) has been registered on the work order job line.
3. Reliability Metrics: MTBF and MTTR
Captured fault data feeds directly into Asset Management reliability analytics:
- Mean Time Between Failures (MTBF):
Total Operating Run Hours / Number of Breakdown Failures. - Mean Time to Repair (MTTR):
Total Corrective Maintenance Repair Hours / Number of Breakdown Failures.
Implementation Scenarios and Common Exam Traps
[!TIP] Exam Tip — Mandatory Checklist Completion: If an exam question asks how to prevent technicians from completing a work order before safety and quality inspections are verified, specify the Checklists validation toggle on the target work order lifecycle state (
Completed).
[!IMPORTANT] Exam Tip — Capacity Load vs. Scheduling Engine: The Capacity load inquiry is an analytical planning tool that evaluates labor availability against demand across time horizons. It does not assign specific workers to jobs. Worker assignment and schedule dispatching are performed by the Work order scheduling engine.
[!WARNING] Exam Trap — Unposted Journals and Work Order Closure: A work order cannot be moved to a lifecycle state where Close work order is enabled if unposted consumption journals exist. All hour, item, and expense journals must be posted or deleted before closing.
A maintenance manager notices that technicians are closing corrective work orders without entering what caused the machine breakdown or how they repaired it. This lack of data prevents the reliability engineering team from calculating Mean Time Between Failures (MTBF) and analyzing root causes. How should the functional consultant enforce mandatory fault capture in Dynamics 365 Supply Chain Management?
A chemical processing facility is preparing for a planned two-week plant shutdown during which 180 preventive and inspection work orders must be executed. The maintenance planner needs to analyze whether the on-site electrical technician group has sufficient available labor hours to complete all assigned electrical work order jobs during the shutdown window. Which Asset Management feature should the planner use?
An enterprise wants to ensure that maintenance technicians cannot post hours, items, or expense journals to a work order while it is still in the "Created" or "Scheduled" state, but allows journal posting as soon as the work order transitions to "In Progress". Which configuration controls this behavior?