Turnaround / plant shutdown service SOP
A turnaround and plant shutdown service SOP for instrumentation: scope and resource the shutdown window with the customer, coordinate safety, isolate, calibrate, repair and certify every covered instrument before the final report.
What the turnaround / plant shutdown service SOP process is
A plant turnaround is not a bigger version of a routine calibration visit; it is a different kind of event. Normally-running equipment is deliberately taken down for a fixed number of days, the customer's own shutdown team is running plant-wide safety coordination for dozens of contractors at once, and Insatech has to get through many instruments in a compressed window instead of the one-instrument-at-a-time cadence of a Preventive Maintenance & Calibration Planning visit. That is why this chart puts "Define scope with customer", "Identify process-critical instruments to cover" and "Plan technicians and reference equipment for the shutdown window" in their own phase, owned end to end by the Project Manager lane, before a single instrument is isolated. Getting the crew size and the reference-standard count wrong is not a minor scheduling slip on a turnaround: the window does not extend to let Insatech catch up, so the resourcing decision has to be made, and gotten right, days before the outage starts.
The chart is also deliberate about whose safety framework applies. "Safety coordination with customer's shutdown team" sits in the Customer lane rather than being folded into Insatech's own field-service process, because a turnaround runs under the plant's shutdown permit-to-work and isolation procedures, not Insatech's standard site rules; "Isolate instruments under customer's permit-to-work" names that explicitly rather than leaving it implied. From there the process reads like a compressed version of the core calibration workflow, but it is not a copy of it: "Calibrate and test covered instruments" tests many instruments as one planned crew effort rather than one work order at a time, and the "Instruments pass as-found check?" decision keeps a fast pace honest by routing failures to "Repair defects found during testing" instead of letting a defect get lost in the volume of a shutdown week.
The last phase is where the shutdown's real deliverable gets assembled: a customer does not just want their instruments working again, they want proof every result is traceable, because a turnaround's calibration record is often the evidence an auditor or the customer's own QA team checks months later. "Verify traceability of all results" and the "Traceability gap found?" decision exist because a reference standard that lapses mid-shutdown, or a certificate that never got attached, would otherwise reach "Issue final report" unnoticed; "Resolve traceability gap with Calibration Lab" loops back rather than letting the gap ride through. Every row also carries a named owner and an hours figure through the built-in People and Workload columns, so the workload BI panel can show that Daniel Cole's Calibration Lab hours concentrate hard in the testing window while Martin Hoyer's Project Manager hours span the full width of the chart, from the first scoping call to the report the customer actually reads.
What this flowchart covers
In this template
- Upfront resourcing and scope, all three owned by the Project Manager lane before a single instrument is isolated: "Define scope with customer", "Identify process-critical instruments to cover" and "Plan technicians and reference equipment for the shutdown window"
- Safety coordination inside the customer's own framework rather than Insatech's site rules: "Safety coordination with customer's shutdown team" in the Customer lane, followed by "Isolate instruments under customer's permit-to-work" in Field Service
- Compressed calibration and testing across the shutdown window: "Calibrate and test covered instruments" feeds the "Instruments pass as-found check?" decision, which routes a Fail to "Repair defects found during testing" before the instrument's data is collected
- Data integrity after testing: "Collect test data" and "Verify traceability of all results", gated by the "Traceability gap found?" decision, which routes a gap to "Resolve traceability gap with Calibration Lab" before anything is certified
- Named owners and hours on every row via the People and Workload columns, so the workload BI panel can show Daniel Cole's Calibration Lab hours concentrated in the compressed testing window while Martin Hoyer's Project Manager hours run the full width of the chart from scope to final report
When to use this template
- You're planning Insatech's coverage for an upcoming plant turnaround and want the resourcing decisions, technicians, reference equipment and scope, fixed on one chart before the outage window starts rather than worked out on the fly once the plant is already down
- You need to show a customer's shutdown coordinator exactly where Insatech's process plugs into their own permit-to-work and isolation procedures, instead of leaving the safety handoff as an assumption on both sides
- A turnaround is covering dozens of process-critical instruments in a fixed number of days and you want a single record of which ones failed as-found, which were repaired, and which passed clean
- You're closing out a shutdown and need every result traceable to a certified reference standard before the final report goes to the customer, including any reference certificate that needs replacing mid-window
- You're onboarding a project manager or field technician to turnaround work and want a reference that makes clear how this differs from a routine, one-instrument-at-a-time Preventive Maintenance & Calibration Planning visit
How it works
Match the lanes to your own shutdown crew
This chart uses Project Manager, Field Service, Calibration Lab, QA and Customer. If a turnaround is large enough that Insatech fields a dedicated shutdown coordinator separate from the account's usual project manager, give that role its own lane rather than folding it into Project Manager — a turnaround's resourcing decisions are exactly where that distinction matters.
Put real numbers on the resourcing steps
"Plan technicians and reference equipment for the shutdown window" is only useful as a plan if it names a headcount and a list of reference standards, not just "crew booked". Write the actual numbers into the row's comment field so anyone checking coverage mid-shutdown can see what was planned against what showed up.
Decide what counts as a Fail on the as-found check
"Instruments pass as-found check?" needs a stated tolerance, the same acceptance criteria used on a routine calibration, not a looser bar because the window is short. Write the criteria into the row's comment so the pace of a shutdown week never becomes a reason to wave through a borderline reading.
Set People and Workload on every row before you rely on the BI panel
The workload panel can only total hours for rows that carry them. Fill in People and Workload for each step as you adapt the chart, using realistic effort hours for a compressed window rather than elapsed calendar time, so a demanding shutdown week actually shows up as one in the right person's totals.
Decide what counts as a traceability gap
"Traceability gap found?" is only consistent if QA and the Calibration Lab agree in advance on what triggers it, a reference certificate that lapsed during the window, one that was never attached, or a standard substituted without being logged. List the examples directly in "Resolve traceability gap with Calibration Lab" so it isn't interpreted differently by whoever is on the shutdown that week.
Frequently asked questions
How is a turnaround SOP different from Insatech's routine Preventive Maintenance & Calibration Planning SOP?
Preventive Maintenance & Calibration Planning works one instrument at a time against a standing service-agreement schedule. A turnaround is a fixed, short, high-pressure window where normally-running equipment is deliberately down and many instruments have to be tested by a planned crew in a compressed timeframe, working inside the customer's own shutdown safety coordination rather than Insatech's own site rules — which is why this chart puts scope, instrument coverage and crew and equipment planning upfront as their own phase, rather than starting straight at the first instrument.
Why does safety coordination sit in a Customer lane instead of Insatech's own process?
"Safety coordination with customer's shutdown team" and "Isolate instruments under customer's permit-to-work" both name the reality that during a turnaround, the plant's own shutdown team runs safety coordination for every contractor on site, not just Insatech's crew. Drawing that lane explicitly stops the handoff from being assumed, and makes clear which procedures govern isolation before a technician ever reaches an instrument.
What happens when an instrument fails the as-found check during a shutdown?
The "Instruments pass as-found check?" decision routes a Fail to "Repair defects found during testing" before the instrument's data is collected. Keeping this as a real branch, rather than a note added after the fact, matters more on a turnaround than on a routine visit, because the volume and pace of a shutdown week is exactly the condition under which a failed reading is most likely to get carried forward unaddressed.
Why is there a separate decision for traceability gaps after the data is already collected?
"Verify traceability of all results" checks every reference standard used during the window against its own valid calibration certificate, not just the instruments under test. A reference that lapses mid-shutdown invalidates every result taken with it, so "Traceability gap found?" catches that before "Issue final report", routing a gap to "Resolve traceability gap with Calibration Lab" rather than letting it reach the customer's record unnoticed.
Who typically carries the most hours across a turnaround, and does that show up in the chart?
In this template, Daniel Cole's Calibration Lab hours concentrate in the compressed "Calibrate and test covered instruments" step, while Martin Hoyer's Project Manager hours span the whole chart, from "Define scope with customer" through "Issue final report". Because every row carries the People and Workload columns, the workload BI panel can total both patterns directly instead of requiring a separate spreadsheet to see who a shutdown week actually falls on.