Every FMCG plant shutdown is a collision between two opposing pressures: the production plan that demands every available hour of run time, and the maintenance plan that requires the plant to stop before critical equipment fails. The gap between what the schedule allows and what the assets need is where shutdown planning lives — and where most plants lose both time and money. A well-planned shutdown delivers higher post-turnaround OEE, extended equipment life, and regulatory compliance without last-minute scope cuts. A poorly planned one generates rework, safety incidents, schedule overruns, and startup quality failures that erase the shutdown's intended benefits within the first week of production. The difference is not the quality of the maintenance team — it is the quality of the planning system that supports them.
Pre-Shutdown Preparation and Scope Definition
The quality of a shutdown is determined before the first tool is locked out. The pre-shutdown phase — typically spanning four to six weeks for a major FMCG turnaround — is where scope is defined, resources are secured, and the schedule is built on a critical path that reflects the plant's actual equipment condition, not a generic maintenance template. iFactory's Shutdown Planning module structures this phase around three deliverables that every FMCG plant needs before a shutdown can proceed with confidence.
The first deliverable is the scope register — a comprehensive list of every task, inspection, replacement, and modification planned for the shutdown window, linked to the equipment asset register and prioritised by criticality. Each scope item carries a work hour estimate, a required skill set, a parts list, and a risk classification. The second deliverable is the resource plan — internal maintenance crews, external contractor teams, specialist inspectors, and equipment vendors mapped against the scope register to identify gaps before the shutdown window opens. The third deliverable is the risk register — identifying the top operational, safety, and schedule risks associated with the shutdown scope, with mitigation plans assigned and tracked through completion.
iFactory's platform integrates these three deliverables into a single dashboard that the shutdown planning team works from throughout the pre-shutdown phase. Scope changes are recorded with their impact on budget, schedule, and resources. Risk mitigation tasks are tracked alongside scope tasks. When a planning assumption changes — a critical spare part delivery is delayed, a contractor crew is reduced, an inspection reveals additional scope — the platform surfaces the impact before the planning team would discover it through manual reconciliation of separate spreadsheets.
Task Scheduling and Critical Path Management
The shutdown schedule is the single point of failure in most FMCG turnarounds. Every task in the scope register has a duration, a set of predecessor tasks that must be completed before it can begin, a resource requirement, and a safety lockout or isolation dependency. The critical path — the sequence of tasks that determines the shutdown's minimum duration — is the schedule's structural skeleton. When a critical path task slips, the shutdown end date slips. iFactory's Shutdown Planning module maintains the critical path as a live model that updates automatically when task progress, resource availability, or scope changes are recorded.
The module surfaces critical path tasks with a distinct visual indicator, so every planner and supervisor knows which tasks drive the shutdown duration and which have schedule float. Resource allocation conflicts — two high-priority tasks requiring the same contractor crew simultaneously — are flagged before they create delays. When a critical task is reported as complete, the schedule recalculates forward, updating dependent task start times and the projected shutdown end date. The shutdown team does not need to wait for the daily planning meeting to know whether they are on track. The schedule is always current, always visible, and always linked to the resource and scope data that determines whether the planned end date is achievable.
Contractor Coordination and Resource Planning
Contractor crews represent the largest variable in FMCG shutdown planning. They bring specialist skills — welding, NDT, electrical, controls, rigging — that internal maintenance teams do not maintain continuously. They also bring scheduling complexity: contractor availability windows, shift preferences, skill mix requirements, and site induction logistics that must be resolved before the shutdown window opens. iFactory's Resource Management module is built to handle this complexity at the scale of a major FMCG turnaround.
The module maintains a resource register that includes internal crews, contractor teams, specialist inspectors, and equipment vendors — each with their own availability calendar, skill profile, certification requirements, and cost rate. When the planning team assigns resources to shutdown tasks, the module checks availability, skill match, and certification currency automatically. Conflicts surface immediately: a rigging crew assigned to two critical path tasks simultaneously, an NDT technician whose certification expires during the shutdown window, a contractor whose previous site induction has expired. Resolving these conflicts during the planning phase — when alternative resources can still be secured — is what converts a reactive shutdown into a planned one.
We ran our annual shutdown with iFactory's Shutdown Planning module for the first time this year. The most visible change was that our planning team stopped working from different versions of the schedule. Everyone — our maintenance manager, the contractor supervisors, the parts coordinator, the quality inspector — was looking at the same critical path model, the same resource assignments, the same scope register. When a scope change came through at week three, the impact on budget, schedule, and contractor hours was calculated in the platform and visible to everyone within minutes. The previous year, that same scope change would have required a planning meeting, three email threads, and a revised spreadsheet that was already outdated by the time it was distributed. The shutdown finished two days ahead of the original schedule.
— Plant Maintenance Manager, Multinational FMCG Company, Sauce and Dressing Production Facility, 8 Lines, Annual TurnaroundPost-Shutdown Validation and Ramp-Up
The shutdown is not complete when the last task is signed off. It is complete when the plant reaches stable production at or above pre-shutdown OEE levels. The post-shutdown phase — startup, quality validation, performance ramp-up — is where the shutdown's true return on investment is confirmed or disputed. A shutdown that delivers every task on time but generates startup quality failures that take three weeks to resolve has not delivered its intended value.
iFactory's platform supports post-shutdown validation through automated comparison of pre-shutdown and post-shutdown performance data. OEE trends, quality test results, energy consumption patterns, and equipment condition readings from before and after the shutdown are displayed side by side in the post-shutdown dashboard. CAPA items identified during shutdown inspections are tracked through closure. Lessons learned from the turnaround — what went well, what did not, what should change for the next shutdown — are captured in a structured template that feeds directly into the next planning cycle. The result is a continuous improvement loop where each shutdown is better planned than the last, not because the planning team has more experience, but because they have better data from every prior turnaround.
The Analytics Advantage in Shutdown Planning
The FMCG plants that execute the most predictable turnarounds share a common characteristic: they treat shutdown planning as an analytics problem rather than a scheduling exercise. The distinction matters because scheduling assumes that durations, dependencies, and resource availability are known inputs. Analytics recognises that they are estimates — and that the quality of the estimate, the variance around it, and the sensitivity of the schedule to that variance are the inputs that matter most for shutdown reliability.
iFactory's Shutdown Planning module embeds this analytics perspective directly into the planning workflow. Task duration estimates carry a confidence range drawn from historical shutdown data — not a single-point estimate that the planning team knows will be wrong but uses anyway. Critical path sensitivity analysis identifies which tasks, if delayed, would have the largest impact on the shutdown end date. Resource utilisation trends from previous turnarounds inform contractor crew sizing decisions for the current one. The analytics layer does not replace the planner's judgement — it gives the planner better data to apply that judgement against.
