Turnaround readiness gates the inspection team owns

A turnaround has a planner, a schedule and a set of gates: scope freeze, schedule approval, materials on site, permits ready. Inspection usually appears in those gates as a line item ("inspection scope confirmed") signed by someone who was not asked what it meant. Then the unit comes down, and the questions start: why is this vessel in scope, who is qualified to run PAUT on that circuit, why are three tablets not syncing, and how far behind is the crew on day four. Each of those is a readiness gate the inspection team should have owned and passed before the first blind went in. This paper sets out those four gates, what each one checks, and how turnaround readiness software should support them.

What is a turnaround readiness gate?

A gate is a defined point where specific criteria must be met and formally reviewed before the event proceeds. Planners use gates because turnarounds are expensive by the hour and most overruns trace back to something that was not ready when it needed to be.

The inspection team's problem is that the planner's gates are written from the planner's side. "Scope frozen" means the list of items is agreed. It does not mean each item has a defensible reason. "Resources confirmed" means the contractor has committed a number of people. It does not mean the person assigned to the PAUT circuit holds a current qualification. "Kit ready" means the tablets have been charged.

The inspection team needs its own gates, run on the same calendar as the planner's, with criteria the inspection lead can actually verify. Four are enough:

1. Scope: every work pack item is traceable to inspection history and standards logic.
2. Crew: the assigned people are qualified for the methods in scope and dispatched to specific work.
3. Field kit: capture works offline and instruments feed the record.
4. Progress capture: daily progress, delays and cost land in the same record as the inspections.

The rest of this paper takes each in turn.

Which gates belong to inspection, not to the planner?

The test for ownership is simple: who can tell, from the evidence, whether the gate has passed?

A planner can verify that a permit exists. A planner cannot verify that a vessel is in scope for the right reason, because the reason lives in the inspection history: a due interval under API 510, a corrosion rate that has moved, an RBI rank, a damage mechanism flagged at the last internal. Only the inspection team can read that evidence.

Equally, the planner can verify that a crew of twelve has been booked. Only the inspection lead can verify that the twelve include two Level II UT technicians with current certifications and one API 510 inspector who is not already double-booked on another unit.

Ownership does not mean isolation. The inspection gates should feed the planner's gate review, with the inspection lead presenting evidence rather than a checkbox. What changes is that the evidence exists.

Gate one: the scope is traceable to inspection history

A turnaround inspection scope tends to be assembled from three sources: the previous turnaround's list, whatever the planner has heard is a problem, and a late addition from an engineer who remembers something. Each has a place. None is a basis.

The scope gate passes when every item in the work pack carries its reason:

• Interval due. Equipment whose inspection interval, computed under API 510 or API 570 rules and capped at half the remaining life, falls within the turnaround window or the period before the next opportunity.
• Rate driven. CMLs whose governing corrosion rate has shortened remaining life enough to pull the next inspection forward.
• Risk driven. Equipment whose RBI ranking (probability by consequence) places it high enough that the operator's program calls for inspection at this opportunity.
• Mechanism driven. Equipment with an active damage mechanism, such as CUI on a circuit where suspect areas were flagged but insulation was not removed last time.
• Deferred. Items deferred from a prior event, with the deferral recorded.

Items with none of these reasons get a decision: justify or remove. The gate output is a scope where every line points at a record, which also means a scope that can be defended when an item is cut for budget. Software supports this gate if the turnaround activity can reference the equipment, the CML and the calculation that put it there, rather than carrying a free-text "reason" field.

Gate two: the crew is qualified and dispatched

Turnaround inspection is method-specific. A visual internal on a vessel, a PAUT scan on a weld and a DFT verification on a recoated exchanger need different people with different paper.

The crew gate checks four things:

• Qualification against method. Each work pack item names its methods; each assigned person holds the qualification those methods require. The check is per assignment, not per crew.
• Currency through the event. Certifications, training and medicals that expire mid-turnaround are a stoppage waiting to happen. Check the expiry date against the event end date, not today's date.
• Availability. Known unavailability (leave, other events, rest rules) is recorded before dispatch, not discovered on the day.
• Dispatch to work, not to pool. People are assigned to specific work packs and shifts. A pooled crew of the right size still produces a first morning spent working out who goes where.

The gate is easier to pass when the crew roster is a structured record: members, teams, skills, qualifications, training and unavailability as data, and dispatch as an assignment that references a work pack. It is nearly impossible to pass from a spreadsheet emailed by the contractor a week before.

Gate three: the field kit works offline and the instruments feed the record

Turnarounds compress months of inspection into weeks, and they happen inside steel where there is no signal. Any friction in capture multiplies by every crew and every shift. The field kit gate is a test, and it should be run weeks before the event on the actual devices with the actual work packs.

The test:

• Put a tablet in airplane mode. Open a real work pack for the unit. Capture a reading, a photo, a finding and a signature. Leave it in airplane mode for the whole shift. Sync at the end and confirm every item arrived.
• Connect the UT gauge or coating thickness gauge over Bluetooth and take readings directly into the CML record. Confirm nothing was retyped.
• Open the drawing for a circuit and confirm the CML points are on it, not in a separate list.
• Hand the device to a second technician mid-shift and confirm their capture and signature carry their identity, not the first technician's.
• Confirm prior readings and the last survey are visible at the CML without a connection.

Anything that fails in this test would have failed on day one with the unit down and forty people waiting. The gate also surfaces the questions nobody asks in a demo: does the local store expire and delete unsynced work, are the offline data encrypted on the device, what does a sync conflict look like when two technicians touched the same record.

Gate four: daily progress, delays and cost are captured in the same record

The last gate is about what happens once the event starts, and it has to be set up before. A turnaround generates daily progress reports, delay events and cost entries. Where they are captured determines whether the inspection team can answer "where are we" with evidence.

The common pattern is that inspections land in one system, progress in a spreadsheet the planner keeps, delays in emails and costs in the contractor's invoicing. On day ten the three disagree and the argument about why is the day's work.

The gate passes when:

• Each turnaround activity is linked to the inspection work it represents, so completion of the inspection is the progress.
• Daily progress is recorded against activities, not retyped into a summary.
• Delay events name the activity, the cause and the duration, at the time they occur.
• Cost entries reference the activity, so scope growth has a number attached before the invoice.
• The gate review itself is a record with attendees, decisions and outstanding items.

A readiness gate is not a meeting. It is a set of criteria, the evidence for each, and a recorded decision. The meeting is where the evidence is read.

How intelliSPEC handles it

intelliSPEC gives the inspection team the records the four gates need in one place.

intelliPROJECTS models the turnaround as structured entities: event, activity, crew, daily progress, delay event, gate review and cost entry. Activities reference the inspection work they represent, so progress is the inspection's completion, and the gate review is itself a record.

The scope gate draws on intelliINTEGRITY: CML points carry the engineering fields needed to compute tMin by design code (ASME B31.3, ASME VIII Division 1 or API 653 by equipment type, returning the code and formula with the number), short-term, long-term and maximum corrosion rates with the maximum governing, remaining life as (t minus tMin) divided by rate, API 510 and API 570 intervals capped at half the remaining life, and API 580/581 semi-quantitative RBI scoring on a 1 to 5 rank. Damage mechanisms are first-class records, and the CUI wizard family covers visual, suspect area, insulation removal, NDE UT, advanced NDE, repairs, recoat, ITP and frequency assessment.

The crew gate runs on intelliCREW: member, team, dispatch, unavailability, inspector qualification, skills and training as records, so qualification is checked per assignment.

The field kit gate is met by the offline field app: full offline capture of forms, images and workflows for all inspection modules with no time limit on the local store, offline data encrypted on the device, field-level conflict records at sync, seven instrument profiles over Bluetooth or keyboard wedge (including DeFelsko PosiTector 6000 and UTG, Elcometer 224T and MTG, Evident 38DL Plus and a TSL RFID reader) so readings enter the record without retyping, drawing annotation with automatic CML point detection, and a signature widget with per-signer identity on a shared device.

For how the scope itself is built from history, see the companion paper on scoping a turnaround from inspection history. Industry context for refinery and chemical events is on the oil and gas page.