From Notification to Work: Maintenance Orders
Maintenance Notifications capture that something might be wrong.
Maintenance Orders define what will actually be done.
A Maintenance Order is the point where maintenance becomes real work:
assigned to technicians,
executed on the shopfloor,
measured, logged, and evaluated.
At the end of this step, you will understand when an issue becomes work.
What is a Maintenance Order?
A Maintenance Order is a work order.
It represents:
an approved maintenance task,
assigned to a technician or team,
ready to be executed and logged.
A Maintenance Order typically contains:
affected Equipment,
clear description of work to be done,
type (corrective, breakdown, preventive),
assigned technician or team,
execution and logging capabilities.
Unlike a Maintenance Notification:
a Maintenance Order can be started,
execution time is recorded,
spare parts and actions are logged,
KPIs are calculated from it.
Think of it as:
Maintenance Notification = problem
Maintenance Order = approved work
Why Notifications and Orders are separated
This separation is one of the most important concepts in P4 maintenance.
It allows you to:
validate issues before starting work,
control priorities and workload,
prevent unnecessary maintenance,
keep clean and reliable reporting.
If every notification became an order immediately:
technicians would be overloaded,
planning would lose control,
MTTR and MTBF would be distorted by noise.
The rule is simple:
Not every problem needs work.
But every work must have an order.
How Maintenance Orders are created
Maintenance Orders can be created in several ways.
All result in the same type of object - only the trigger differs.
1. Creating a Maintenance Order from a Notification (manual)
This is the most common and controlled scenario.
Typical use:
planner reviews a Maintenance Notification,
confirms the issue is valid,
decides that work is required.
The Notification is then:
converted into a Maintenance Order,
linked to the original notification,
ready for assignment and execution.
This preserves traceability:
when the issue was detected,
when work was approved,
how long resolution really took.
2. Automatic Maintenance Order creation from Notification
For critical equipment, waiting for evaluation may be too slow.
In these cases:
a Maintenance Notification automatically creates a Maintenance Order,
no manual approval step is required.
Typical use:
breakdowns,
safety-related equipment,
assets where downtime is unacceptable.
Important:
automation skips decision, not control,
the order is still assigned, executed, and logged normally.
3. Creating a Maintenance Order directly (without Notification)
In some situations, work is clear immediately.
Typical examples:
technician identifies a clear fault during inspection,
preventive maintenance triggered by schedule,
corrective action decided on the spot.
In these cases:
a Maintenance Order can be created directly,
no Maintenance Notification is required.
This is valid - but should be used deliberately, not as default.
Understanding the Maintenance Order lifecycle
Once created, a Maintenance Order moves through a clear lifecycle.
Typical statuses include:
Created – order exists, not yet assigned
Assigned / Assigned to Team – responsibility defined
In Progress – work has started
Paused – work temporarily stopped
Completed – work finished
Redbox – urgent attention required
Statuses reflect real execution, not planning intent.
A key rule:
Execution always happens on Maintenance Orders, never on Notifications.
Assignment: who will do the work
Before execution starts, the order must be assigned:
to a technician, or
to a team.
Assignment can be:
manual (planner decision),
automatic (based on equipment responsibility).
Assignment answers one simple question:
Who is responsible for fixing this?
Execution does not start until this is clear.
Common first issues (and what they mean)
Too many Maintenance Orders created
Often caused by skipping the Notification evaluation step.
Orders exist but nothing happens
Orders must be assigned before work can start.
Confusion between Notification and Order statuses
Only Orders reflect execution progress.
Using Orders as problem reports
Problem description belongs to Notifications; Orders describe work.
These issues are normal and usually disappear once the separation is understood.
What you should be able to do now
After completing this step, you should:
understand what a Maintenance Order represents,
know when to create an order from a notification,
understand when direct order creation makes sense,
recognize that execution happens only on orders.
Next step
Planning & Assignment: Who does the work and when
This is where Maintenance Orders are assigned, prioritized, and prepared for execution.