A cement turnaround rarely fails because the original plan was poor. It fails because the plan quietly grows. A cracked kiln tyre pad is found on day two, a mill gearbox inspection adds a bearing change, and an operations request squeezes in a cooler modification. Each addition looks reasonable alone, but together they stretch the critical path and delay restart. Scope change control makes growth visible, priced and approved, and a cement turnaround maintenance management system keeps the approved scope and its work orders in one place.
Shutdowns and Turnarounds | Scope Change Control
Cement Turnaround Scope Change Control and Production Risk
Decide what enters the shutdown, what waits, and what each addition costs in days of lost clinker, so restart dates are defended with evidence and not argued from memory.
The later a change arrives, the more it disrupts (qualitative view)
Where Scope Growth Comes From
Discovery work
Opening a mill, kiln shell section, cooler or preheater cyclone reveals damage no inspection could confirm beforehand. This is the most legitimate source of growth and the hardest to eliminate.
Deferred backlog
Repairs held back since the last stop arrive in a rush as people notice a stopped kiln is the only time to fix them. Unmanaged, the backlog becomes a flood of requests.
Opportunity work
Improvement projects, upgrades and modifications get attached to the stop because access is available. They compete with essential work for crews, cranes and time.
Quality and regulation
Audit findings, safety actions or environmental requirements may need fixes before restart. Some are mandatory and need a clear route into scope.
The Change Request Gate
1
Raise
Anyone can submit a request with asset, reason, evidence and the person asking.
2
Assess
Planner estimates labour, parts, access, permits and effect on the critical path.
3
Rate risk
Operations and engineering judge production, safety and quality risk of doing it or deferring it.
4
Decide
Authority level depends on cost and schedule effect. Result is approve, defer or reject.
5
Record
Decision, reason and updated plan are logged, and affected work orders are changed.
What every request must show
- The asset, the defect or need, and evidence such as photos, measurements or inspection records.
- The consequence of not doing the work, stated as a production, safety or quality outcome.
- Estimated duration, crew, parts and special equipment, with lead times where relevant.
- Whether the job sits on the critical path or can run in parallel with other tasks.
Classify Changes by Production Risk and Schedule Effect
Risk if deferred / effect on schedule
No critical path effect
Extends critical path
High risk if deferred
Approve
Run in parallel. Confirm crew and parts so it does not become critical later.
Escalate
Needed work that costs restart days. Shutdown manager and production decide together.
Low risk if deferred
Fit if capacity allows
Add only when spare crew and time exist. Otherwise move to the next planned window.
Defer or reject
Move to backlog with a date and owner. Do not let it enter by informal request.
Decision Authority by Size of Change
| Change size | Typical effect | Who approves | Information required |
|---|---|---|---|
| Minor | Small task on an open work front, no critical path effect | Area lead and planner | Work order with reason and resources |
| Moderate | Additional crew or parts, limited float used | Shutdown manager | Estimate, float check and risk note |
| Major | Critical path extended or significant cost added | Shutdown manager with production and maintenance heads | Revised schedule, restart impact and options |
| Strategic | Restart date moves or capital project is added | Plant leadership | Business case with lost production estimate |
Every Added Job Should Arrive With a Price and a Decision
Log requests, impacts and approvals against the shutdown scope, then work from one approved list.
Translating Scope Change into Production Risk
Restart delay
Every day a critical path job adds is a day of lost clinker and delayed dispatch. Express each change in days on the critical path, not only in hours of labour.
Float consumed
Jobs off the critical path still use float. When float runs out, a small slip elsewhere turns a parallel task into a critical one. Track remaining float as scope grows.
Resource clashes
Two approved jobs may need the same crane, scaffolding crew or specialist at the same time. A scope list without a resource view hides this until the day it bites.
Quality and safety exposure
Rushed late jobs often skip planning steps such as permits, lifting plans and parts checks. Late scope should not bypass any safety control.
Restart reliability
Cutting verification steps to recover time can cause early failure after restart, costing far more than the days saved.
Cost growth
Contractor standby, expedited parts and overtime accumulate quietly. Cost per change, recorded when approved, shows the true effect of late requests.
Before and After a Formal Change Process
Informal additions
- Requests arrive by phone, radio and conversation
- Supervisors add jobs to keep crews busy
- No one knows the current scope on any given day
- Restart date slips with no clear cause
Controlled additions
- Every request follows the same gate
- Decisions use schedule and risk evidence
- Approved scope is a single live list
- Slips are traced to specific approved changes
Daily Rhythm During the Shutdown
Start of day
Review the approved scope, today's critical path jobs and any open findings from the night shift. Confirm crews, parts and permits for the day's key tasks.
Mid day
Hold a short change meeting. Decide pending requests, record each decision and update schedules, so afternoon crews work from the new plan.
End of day
Record progress, new findings and remaining float. Send the restart forecast to production and note what could still move it.
Signals that scope is getting out of control
- Approved scope changes faster than the plan can be updated.
- Crews wait for decisions, parts or access on jobs that were already approved.
- Requests are accepted verbally with no record of the reason.
- Float on key paths shrinks every day without a plan to recover it.
- Production asks for restart dates that the current plan cannot support.
Typical Cement Turnaround Changes and Questions to Ask
| Finding | Possible added work | Question before approving |
|---|---|---|
| Kiln shell hot spot or lining thinner than expected | Extra brick zone, shell repair | Can it be run to the next stop safely, and what is the failure consequence? |
| Mill gearbox bearing wear | Bearing change, alignment, oil flush | Is a spare ready, and does it extend the critical path? |
| Cooler grate plate damage | Additional plate replacement | Do the parts exist on site, and does work run in parallel with kiln work? |
| Cyclone or duct build-up and wear | Cleaning, liner repair | Is access available, and what is the effect on heat consumption if deferred? |
| Fan impeller wear or imbalance | Repair or replacement | Is balancing capacity booked, and what lead time applies? |
| Dust collector or conveyor defects | Bag change, belt or idler work | Can this run after restart without risk to emissions or safety? |
Contingency and Float: Planning for Growth You Cannot Name
Scope contingency
Hold an agreed allowance of hours and budget for discovery work, based on previous stops on the same equipment. Spend it through the same gate as any other change, so use is visible.
Schedule float
Protect float on the longest paths, such as kiln refractory and mill work. When a request would consume it, the decision makers should see the remaining margin before they approve.
Parts and tools buffer
Keep common wear items and special tools near the work front. A small buffer for likely discoveries avoids losing a day to an urgent order.
How production should take part in the decision
- Present each major change as days of restart delay and the lost output they represent, not just labour hours.
- Offer options such as a temporary repair, a staged repair or deferral, with the risk of each.
- Agree in advance which production targets are fixed and which can move, so decisions are not improvised under pressure.
- Share the restart forecast with sales and dispatch early, so customers are not surprised by slips.
Contractors, Contracts and Commercial Control
| Issue | Why it matters in a turnaround | Control to apply |
|---|---|---|
| Verbal instructions to contractors | Work starts with no approved record, and later cost claims are hard to dispute | Issue only approved work orders and reject unrecorded requests |
| Standby time | Crews wait while decisions or parts are pending | Track waiting reasons and decide urgent items quickly |
| Unit rates and variations | Added work may follow different rates from the base scope | Agree variation rules before the stop starts |
| Quality records | Late jobs often miss inspection and sign-off steps | Attach checklists to every work order, including added ones |
Safety controls that stay in force for late scope
- Permits, isolations and lifting plans are required for added jobs exactly as for planned ones.
- Added work must be checked for conflicts with other crews in the same area, including work at height and confined spaces.
- Pressure to recover time is a risk factor in itself, so supervisors should report it as an issue, not hide it.
- Any change that alters access, scaffolding or isolation boundaries triggers a fresh safety review for the affected area.
How Oxmaint Supports Scope Control
- Work orders hold each shutdown task with its asset, tasks, estimated hours, parts and status.
- Requests raised from inspections or findings can be reviewed and approved before entering the scope.
- Asset management shows past failures and repairs, helping decide whether a deferral is safe.
- Scheduling and planning views help link tasks to the shutdown timeline and available crews.
- Inventory and parts tracking show whether items for a new job are in stock or need ordering.
- Mobile workflows let technicians record findings in the equipment, with photos, as they are discovered.
- Reports compare planned and actual scope, deferred items and completed work for the post-shutdown review.
What a good scope change log looks like
- A unique reference for each request, linked to the work order it creates or changes.
- The date, requester, asset and evidence, so decisions can be reviewed later.
- The estimated effect on cost, critical path days and float at the time of the decision.
- The decision, the approver and the reason, including why a request was deferred or rejected.
- The actual effect once the work is done, so estimates improve from one stop to the next.
- Any follow-up needed after restart, such as monitoring, re-inspection or a planned repair.
Measures That Show Scope Is Under Control
Scope growth
Added hours or jobs after the freeze, as a share of baseline
Late-request share
Requests raised after the freeze, against all requests
Decision time
Time from request to approve, defer or reject
Remaining float
Float on key paths, tracked each day
Restart variance
Planned against actual restart, with causes
Handling deferred work responsibly
- Record the risk of deferral in plain terms, such as the likely failure mode and its effect on production.
- Set a review date and a monitoring task, for example a temperature check or visual inspection at each round.
- Name an owner who is accountable for either closing the item at the next window or renewing the decision.
- Make sure the deferred list appears in the next turnaround planning meeting, not only in the closed shutdown file.
- Reassess any deferral immediately if operating conditions or the equipment condition change.
After the Restart: Learn From the Changes
A
Sort changes by cause
Discovery, backlog, opportunity, regulation or poor planning. Each cause needs a different fix for the next stop.
B
Check the deferrals
Review whether deferred items stayed safe, and move them into the next scope with a date and owner.
C
Improve inspection timing
Repeated surprises in one area suggest earlier inspection, online monitoring or longer lead time for parts.
D
Update templates and contingency
Use real growth data to set contingency allowances and refresh job plans for the next turnaround.
Scope Control Checklist
Before freeze
- Backlog reviewed and sorted
- Inspection findings included
- Contingency agreed
After freeze
- One change form and gate
- Authority levels published
- Daily change meeting set
After restart
- Changes analysed by cause
- Deferred items re-planned
- Lessons stored as templates
Frequently Asked Questions
When should scope be frozen?
Early enough that parts, contractors and permits can be arranged, and late enough to include inspection findings. Many plants set the freeze by supplier lead times.
Should every change need senior approval?
No. Set authority levels by cost and schedule effect so minor changes move quickly. You can set up change tracking to match your levels.
How do we handle discovery work that cannot wait?
Use a fast path with the same record: evidence, risk, estimate and decision. Speed should not remove the audit trail.
Can deferred work stay in the system?
Yes, deferred items should remain with an owner, risk note and review date. Book a demo to see backlog tracking.
What is the best early warning of scope trouble?
Shrinking float with rising late requests. Track both daily and discuss them in the change meeting.
Protect the Restart Date With Controlled Scope
Use Oxmaint to track every shutdown task and change from request to closeout, so production risk is visible before it costs clinker.
