Executing Maintenance: From assigned to completed
Planning defines what should be done.
Execution defines what actually happens.
Executing maintenance means:
technicians start working on Maintenance Orders,
real time and actions are recorded,
maintenance data is created.
This is the point where maintenance becomes visible, measurable work.
What does “execution” mean in P4 maintenance?
Maintenance execution is the process where:
a technician or team starts a Maintenance Order,
the order status reflects real work,
time, actions, and materials are recorded.
Execution always happens on a Maintenance Order.
Notifications and planning data do not execute work.
Only Maintenance Orders do.
Think of it as:
planning answers what should happen,
execution answers what is happening right now.
Where execution happens
Maintenance execution is performed in the Maintenance Shopfloor View.
This view is designed for:
technicians,
team leaders,
anyone performing maintenance work.
From here, technicians:
see assigned Maintenance Orders,
start and manage work,
log progress and results.
This separation keeps:
planners focused on coordination,
technicians focused on execution.
Starting a Maintenance Order
Execution begins when a technician:
opens a Maintenance Order,
clicks Start Maintenance Order.
At this moment:
the order status changes to In Progress,
execution time starts,
the order becomes real work.
If the order was assigned to a team:
starting it assigns the technician automatically,
responsibility becomes explicit.
From now on:
planned assumptions are confronted with reality.
Working on a Maintenance Order
While a Maintenance Order is In Progress, technicians can:
perform maintenance actions,
inspect equipment,
replace parts,
adjust settings.
Execution is not a single step — it is a process.
P4 supports this by allowing:
pauses,
partial logging,
continuous updates.
Pausing and resuming work
Maintenance work is often interrupted.
Typical reasons:
waiting for spare parts,
production constraints,
safety conditions,
shift changes.
In these cases, the order can be:
Paused with a reason,
later Resumed.
Pause is not a failure.
It is part of realistic maintenance execution.
Logging work: creating maintenance data
Execution is valuable only if it is recorded.
During execution, technicians log work using Completion Confirmation.
This includes:
time spent,
executed actions,
spare parts used,
notes and comments,
media files (photos, audio, video).
Logging can happen:
multiple times during execution,
once at the end,
depending on how the work is performed.
The goal is simple:
Capture what really happened.
Finishing a Maintenance Order
A Maintenance Order is finished when:
all required work is done,
final logging is completed,
the order is marked as Completed.
At completion:
execution stops,
total time is fixed,
data becomes available for reporting.
Completion closes the loop between:
detected issue,
planned work,
executed maintenance.
Planned vs. actual maintenance
It is normal for execution to differ from the plan.
Differences may include:
longer or shorter duration,
additional work discovered,
unexpected pauses.
P4 does not hide these differences.
Instead:
actual execution data is stored,
plans can be adjusted,
Execution reveals reality.
Interaction between planners and technicians
Execution creates a natural role boundary.
Planners:
monitor progress,
react to delays,
adjust priorities.
Technicians:
execute work,
log reality,
focus on the current order.
Both roles work with the same Maintenance Orders —
from different perspectives.
Common first execution issues
Work not started despite assignment
Execution starts only when the technician actively starts the order.
Missing or incomplete logging
Unlogged work cannot be analyzed later.
Fear of pausing orders
Pausing is normal and often improves accuracy.
Expecting execution to follow plan exactly
Maintenance rarely does.
These issues disappear once execution is understood as data creation.
What you should be able to do now
After completing this step, you should:
understand how maintenance execution works in P4,
know how to start, pause, and complete orders,
understand the importance of logging,
see how execution creates data for planning and reporting.
Next step
Preventive Maintenance: Staying ahead of failures
This is where maintenance moves from reacting to problems to preventing them.