Getting scope, access and crews settled before the window opens
Offshore, a turnaround window is fixed by a vessel offtake or a system shutdown, and the binding constraint is bed space, not calendar days. An inspection scheduling module has to convert scope into man-hours, then into beds, scaffold, permits and helicopter seats, and show readiness against a scope-freeze gate weeks before the window opens.
Onshore you can add a crew. Offshore you cannot: every NDT technician on the platform displaces a fitter, a scaffolder or a permit signatory, and the bed count is fixed by the accommodation module and lifeboat capacity. A plan of 900 inspection man-hours in a fourteen-day window is not a plan until it is expressed as roughly nine people for ten productive days, allowing for flight days, weather standby and a helicopter that flies half the time in November. Method choice is a scheduling decision too. Gamma radiography clears an exclusion zone and stops adjacent work, so choosing phased array or digital radiography can buy back more window than adding a technician. Then the discovery problem: stripping insulation for corrosion under insulation work to API RP 583 reliably grows scope, and a readiness model with no contingency line moves the overrun to the last three days.
Source: Sources: 30 CFR Part 250 Subpart S (Safety and Environmental Management Systems) and API RP 75 for offshore US OCS operations; UK Offshore Installations (Offshore Safety Directive) (Safety Case etc.) Regulations 2015 and the independent verification scheme for safety-critical elements; API 510, API 570 and API RP 580/581 for interval setting, deferral and risk-based inspection; API RP 571 for damage mechanisms; API RP 583 for corrosion under insulation; ANSI/ASNT CP-189, ASNT SNT-TC-1A and ISO 9712 for personnel qualification; ASME Section V and Section VIII Division 1 for method and pressure equipment requirements; ISO 15156 / NACE MR0175 for sour service materials.
| Gate | What must be true | Clear by | Failure mode if it slips |
|---|---|---|---|
| Scope freeze | Every inspection task has an asset, a method, an estimated duration and a written reason it cannot be done on stream | T minus 12 weeks | Late scope arrives without a scaffold or an isolation, and consumes window time that was already committed |
| Access method decided | Each task is assigned to scaffold, rope access, permanent platform, UAV or subsea intervention, with the lead time that implies | T minus 10 weeks | Scaffold design and materials miss the last supply boat, and a fully manned crew waits on staging |
| Isolation and permit pack drafted | Isolation boundaries identified, permits pre-written, confined space entries identified with standby requirements | T minus 8 weeks | Permit desk becomes the bottleneck; crews burn morning hours queuing instead of inspecting |
| Manning plan reconciled to POB | Man-hours converted to bodies and bed-nights, checked against accommodation and lifeboat capacity for every night of the window | T minus 6 weeks | The plan is unmannable and is discovered by the logistics coordinator, who cuts scope arbitrarily |
| Crew currency verified | Survival and helicopter escape training, offshore medical, and each NDT certificate valid on every day the person is planned to work | T minus 4 weeks | A technician is turned back at the heliport, or a certificate lapses mid-window and the readings are contestable |
| Contingency allocated | A named reserve of man-hours and beds held against discovery scope, with a rule for who releases it | T minus 4 weeks | Discovery scope is absorbed by deleting planned scope silently, and the deletions are never dispositioned |
The window is fixed and everything else has to bend
Onshore turnaround dates move. Offshore they mostly do not, because the date is not set by maintenance. It is set by a tanker offtake, a pipeline system shutdown affecting several operators, a heavy lift vessel's availability, or a weather season that closes. Miss it and the next opportunity is twelve to twenty-four months away, with the deferred scope still on the register and the risk still accumulating. That single fact reorganises what a scheduling module has to do.
In a movable-date world, the schedule is a plan of work and the useful question is how long it will take. In a fixed-window world, the schedule is a capacity problem and the useful question is what fits. Those need different data. Duration estimates are necessary but not sufficient; you also need the resources each task consumes, the access it depends on, and the earliest date each of those can be committed. Without that, the plan is a wish list sorted by date.
The consequence is that most of the value of the module is delivered before the window opens, not during it. By the time the shutdown starts, the scope is what it is and the crews are on board. The scheduling work that mattered happened at the twelve, ten, eight and six week gates, and the question the system exists to answer is whether those gates were actually met or merely reported as met.
Personnel on board is the real capacity constraint
Every offshore inspection plan should be expressed twice: in man-hours, because that is how work is estimated, and in bed-nights, because that is what is scarce. The conversion is where plans die. Nine hundred inspection man-hours in a fourteen-day window looks comfortable until you account for the shape of the window. Two days go to mobilisation and demobilisation flights. Weather standby takes a variable slice, and in a North Sea or Atlantic Canada winter that slice is not small. Toolbox talks, permit collection and walk-to-work time remove one to two hours from every shift.
Run the arithmetic honestly and the same nine hundred hours needs roughly nine or ten technicians present for ten productive days, at twelve-hour shifts with realistic on-tools time. Those nine or ten beds have to exist alongside the mechanical crew, the scaffolders who are also inspection's dependency, the electrical and instrument teams, the catering increment and the marine crew. On many installations the inspection allocation is four to six beds, which means either the scope is wrong or the window is wrong, and it is better to know that at twelve weeks than at day three.
There is a further trap in rotation length. A technician who lands on day twelve of a fourteen-day window has contributed two days and consumed a helicopter seat both ways. Systems that schedule people by date range rather than by productive days on the installation will happily produce plans full of these. The module should show productive days per person against seats consumed, because that ratio is what a logistics coordinator will challenge.
Access method is a scheduling input, not a field decision
Onshore, deciding between scaffold and rope access is often a foreman's call on the day. Offshore it is a planning decision with a ten-week lead time, because scaffold materials arrive by supply boat and scaffolders occupy the same beds the inspection crew wants. Every inspection task therefore needs an access method assigned before scope freeze, along with the erection and dismantling time that method implies and the crew it consumes.
The economics are not obvious. Rope access removes scaffold lead time and beds, but it constrains the methods that can realistically be performed at height and the duration a technician can work on rope. Permanent platforms and existing walkways are free but limited. Unmanned aerial survey removes access cost entirely for external and structural visual work, at the cost of resolution and the inability to do anything contact-based. Subsea scope brings a different constraint set again: diver spread or remotely operated vehicle availability, splash-zone conditions, and for flooded member detection on jacket nodes a vessel that is booked months ahead.
A scheduling module that treats access as a text note on a task cannot help with any of this. What it needs is access as a resource with a lead time, a cost in beds and a dependency link, so that when a task moves, the scaffold moves with it and the conflict shows up in the plan rather than in a phone call from the deck.
Method choice buys or spends window time
Choosing an NDT method offshore is partly a technical question about the damage mechanism and partly a logistics question about what the method does to everyone else. Radiography is the clearest case. A gamma source requires an exclusion zone, and on a platform where process, drilling and construction activity are stacked within tens of metres, that zone stops work well beyond the inspection scope. The true cost is measured in other disciplines' lost hours.
The alternatives are real and worth planning around. Phased array ultrasonics and time-of-flight diffraction cover much weld inspection scope without an exclusion zone, at the cost of technician qualification and procedure qualification effort that has to be arranged in advance. Digital radiography with a lower-activity source or an X-ray crawler reduces the zone but not to zero. Clustering all radiography into a defined night window concentrates the disruption where it costs least. All three are scheduling decisions taken weeks out, not preferences expressed on the day.
This is also where simultaneous operations constraints bite. When drilling, production and construction share the installation, the permit regime restricts what may happen adjacent to what and when. An inspection schedule that does not carry those restrictions will produce a plan that the offshore installation manager rejects on arrival, and the rejection will cost a shift.
Upstream damage mechanisms decide what cannot be deferred
Not all offshore scope is equal, and the readiness discussion should be weighted by mechanism. Sweet carbon dioxide corrosion and sour service under ISO 15156 drive internal wall loss on production piping at rates that make the interval genuinely binding. Sand production adds erosion-corrosion concentrated at bends, tees and choke downstream spools, which is location-specific and rewards precise condition monitoring locations rather than general surveys. Water injection systems bring microbiologically influenced corrosion with a pitting morphology that a grid of thickness readings can miss entirely.
External mechanisms follow their own logic. Splash zone corrosion and coating breakdown on the jacket, corrosion under insulation on deck piping and vessels, and fatigue at welded nodes on fixed structures each need a different method and a different access. For a floating production unit, hull and mooring scope answers to class society survey requirements and a continuous survey programme, because the vessel does not drydock, and those dates are set by the class calendar rather than by your integrity plan.
The scheduling implication is that the deferral conversation must be mechanism-aware. Deferring a corrosion under insulation survey on a warm deck line and deferring a thickness survey on a sour service riser are not comparable decisions, even when both show as one overdue task. A module that presents overdue as a single count invites exactly the wrong trade-off at the moment the window is being cut.
Readiness is a set of gates with owners
The common failure in turnaround readiness reporting is the percentage. A number like eighty-seven per cent ready is comfortable and tells you nothing, because it averages a fully prepared scaffold plan against a missing isolation that will stop everything. Gates behave better. Each gate is binary, has a single owner, and has a date by which it must be clear. Scope frozen. Access method assigned. Isolation identified. Permits drafted. Manning reconciled to beds. Crew currency verified. Contingency allocated.
Reporting then becomes an exception list rather than a dashboard: which gates are not clear, who owns them, and how many days remain. That is a five-minute meeting instead of an hour. It also forces the uncomfortable conversation at the right time, because a manning gate that cannot be cleared at six weeks means the scope must be cut at six weeks, when the cut can be made on risk grounds by an integrity engineer rather than on convenience grounds by whoever is standing at the heliport.
The gates also give a scheduling module something honest to measure itself against afterwards. At the end of the window, the questions worth asking are which gates were late, what the late gates cost in lost hours, and how much discovery scope appeared against the reserve. Three turnarounds of that data will change your planning lead times more than any software feature.
Deferral is an engineering decision with a paper trail
Some scope will not fit. That is normal and it is not a failure, provided the decision is made and documented properly. A deferral needs the equipment identity, the inspection that was due, the mechanisms credited, the evidence that supports continued operation, a revised date tied to a realistic next access, and the signature of someone competent under the operating regime to make that call. Where the programme is risk-based to API RP 580 and 581, it should also record the effect on calculated risk, because that is the number the assessment framework exists to manage.
What must not happen is silent deferral, where scope is deleted from the plan under time pressure and simply reappears as overdue afterwards with no reasoning attached. This is the single most common finding when an integrity programme is audited under a safety and environmental management system to 30 CFR 250 Subpart S or examined against a verification scheme for safety-critical elements in the UK regime. The equipment is usually fine. The record of the decision is what is missing.
A scheduling module supports this by making deferral a transaction rather than a status change: it requires the justification fields, it stamps the approver, it sets the new date, and it keeps the original due date visible in the history. If a system lets a planner drag a task to next year without any of that, it is not a mechanical integrity tool no matter what it is called.
What to test before you commit
Give the vendor a fixed fourteen-day window, six inspection beds and a scope of nine hundred man-hours, and ask them to show the plan. If the product cannot express the bed constraint, the demonstration ends there. If it can, ask what it does when you add two hundred hours of discovery scope on day four: does it show what must be displaced, and does the displacement route through a deferral record?
Then test the currency logic. Put a technician on the plan whose certificate expires on day nine of the window and see whether the system flags it at planning time. Most will flag an expired certificate. Fewer will flag a certificate that is valid today and expires mid-scope, which is the case that actually occurs. Do the same with a procedure revision that is superseded halfway through the campaign.
Finally, ask to see last year's window replayed: planned versus actual hours, gates cleared late, discovery against reserve, and scope deferred with the justification attached. A product that cannot reconstruct a past turnaround will not improve the next one. If it would help to run this evaluation against your own scope and manning numbers rather than a demonstration dataset, Atlantis will do that as a consulting session; the contact is info@atlantisndt.com.
How many inspection technicians can a platform actually accommodate?
Fewer than the plan assumes, because the number is not an inspection decision. Beds are allocated across mechanical, electrical, instrument, scaffold, catering and marine crews, and the ceiling is set by the accommodation module and lifeboat capacity. Inspection typically gets a negotiated share. A scheduling module that plans in crew-days without a bed constraint produces a plan that logistics later cuts by judgement, usually by deleting whatever is easiest to defer rather than what carries least risk.
When should offshore turnaround inspection scope be frozen?
Early enough that scaffold design, isolation planning and material calls can follow it, which in practice means around twelve weeks out for a routine window and longer where subsea or heavy lift is involved. Freezing does not mean nothing changes. It means changes after the gate go through a named approver and consume the contingency line, so growth is visible as a number rather than absorbed invisibly by deleting other scope.
Why does radiography cost more window time offshore than other methods?
Because a gamma source establishes an exclusion zone, and an exclusion zone on a congested platform stops adjacent work, sometimes across a deck. The cost is not the technician hour, it is everyone else's stopped hour. Scheduling therefore has to treat method as a driver of access cost. Moving welds to phased array or digital radiography, or clustering radiography into night shifts, often recovers more window than adding people you have no beds for.
What crew currency checks belong in an offshore inspection schedule?
Three layers that expire independently: offshore survival and helicopter escape training, the offshore medical, and the NDT qualification itself by method and level. Each must be valid on every day the individual is planned to work, not merely on the mobilisation date. Fourteen-day rotations and back-to-back campaigns make mid-window expiry common. The check should also cover procedure revision and equipment calibration, which lapse on their own clocks.
How should scope growth from insulation removal be planned for?
As an expected quantity, not a surprise. Corrosion under insulation work to API RP 583 reliably reveals more than the survey predicted, particularly in splash zone and deck penetration areas, and the discovery rate on a given installation is knowable from history. Reserve man-hours and beds explicitly, define who releases the reserve, and track consumption daily. A readiness model with no contingency line simply relocates the overrun to the final three days.
What does a defensible inspection deferral look like offshore?
A dated engineering assessment, not a status change. It names the equipment and the missed inspection, states the damage mechanisms credited, cites the evidence supporting continued operation, sets a revised date tied to the next realistic access, and carries the signature of someone competent to make the call. Under a risk-based programme built on API RP 580 and 581 the deferral should also record what it does to the calculated risk, because that is what an auditor or verifier will ask.
Built for any business that runs on operations
Most companies do not fail at their craft. They lose time, margin and goodwill in the gaps between the tools they use to run the place — a quoting spreadsheet that does not talk to the job sheet, a job sheet that does not reach accounts, and a compliance folder nobody can search when a client asks. Atlantis closes those gaps by putting the whole operation on one platform, so information is entered once and everything downstream stays in step.
What you can run on it
- Sales and CRM — leads, quotes, follow-ups and the pipeline that tells you what next month looks like.
- Projects and job costing — plan the work, track the hours and materials against it, and see the margin while the job is still live rather than at final account.
- Field and service teams — dispatch, schedules, mobile capture that works with no signal, and sign-off from site.
- Inventory and purchasing — stock, suppliers, reorder points and goods receipt, joined to the jobs that consume them.
- People — records, qualifications and licences with renewal reminders, timesheets, leave and payroll.
- Quality and documents — procedures and forms under revision control, with the audit trail an inspection or accreditation body actually asks for.
- Accounts — invoicing, expenses, multi-currency and the reporting your accountant stops chasing you for.
Affordable, accessible, fully customizable — and we mean each word
Affordable because the whole suite is included rather than sold to you a module at a time, and because implementation is done by people who have run operations rather than by a chain of subcontractors. Accessible because it runs in a browser and on a phone, works for a small team on day one, and does not need a specialist on staff to keep it alive. Fully customizable because your process is the thing that makes you competitive — the software should bend to it, not the other way round.
Industries we configure for
Service businesses and contractors, manufacturing and fabrication, trading and distribution, laboratories and testing houses, engineering consultancies, construction and facilities, and asset owners across energy, marine, aerospace and infrastructure. Inspection and testing is where we started, and it remains the sector we go deepest in — but the platform underneath is general-purpose, and most of what it does has nothing to do with inspection at all.
What happens when you get in touch
A short conversation, not a sales sequence. We ask how the business runs today and where it hurts, show you the platform doing that work, and send a written quote shaped to your region, your team size and the scope you actually need. No obligation, nothing to install first, and no pressure to decide on the call. Reach out and tell us what you are trying to fix.
Related: business management platform · inspection management software · choosing the right category of software · modules · by industry · asset integrity platform. Book a free consultation.