Fixed platforms and jackets
Offshore hook-up planned against evidence, not against optimism.
Bed space and weather decide how much can be finished offshore. Deskely makes onshore completion provable subsystem by subsystem, so the offshore campaign is spent only on work that genuinely could not be closed at the quayside.
- Certification level
- Subsystem
- Constraint
- POB and weather
- Execution
- Offline on tablets
- Gate
- RFSU before first gas
Choose your project type
Two economies, one register
What changes between the yard and the platform is the cost of an hour, not the standard.
- Onshore labour cost per hour
- Baseline
- Unconstrained crew size
- Offshore labour cost per hour
- 3–5x baseline
- Bunk-limited crew size
- Typical bed space (POB) for hook-up
- 40–120 people
- Shared across all disciplines
- Weather downtime on a North Sea campaign
- 20–30% of days
- Non-negotiable, not schedulable
- Onshore mechanical completion target
- 95%+ of subsystems before sail-away
The problem
Every offshore man-hour is bought twice, and re-testing spends it for nothing.
A fixed platform is completed in two very different economies. Onshore, at the fabrication yard, labour is cheap, access is easy and there is no real limit on how many people can work a scope in parallel. Offshore, the same work costs multiples, competes for a bunk, and stops the moment the weather turns.
The whole discipline of hook-up planning is deciding what has already been proven and what has not. When that decision is made against four spreadsheets and a folder of scanned test packs, the safe answer is always to re-walk and re-test — which is how an offshore campaign quietly absorbs weeks of work that was already finished in the yard.
The second cost is the punch list. Items raised during load-out that were never given an owner reappear offshore as discovery work, at the exact point in the schedule where there is no slack left to absorb them.
Setting up the register
Subsystems that survive load-out, because they never changed shape.
The subsystem breakdown is set once, from the P&IDs and single line diagrams, and it stays stable from fabrication through load-out, lift and hook-up. Nothing is re-mapped when the scope moves offshore, because nothing about the structure was tied to where the work was happening.
The register is drafted from the drawing set rather than typed: line lists, cable schedules, equipment lists and vendor package documents become tags with their source drawing kept behind them, then reviewed by a completions engineer before anything is issued.
A jacket, a topsides module and a vendor skid all report through the same structure, so the readiness view the hook-up manager reads before sail-away is the same one the offshore construction lead reads afterwards.
What travels offshore
The record a yard subsystem carries onto the barge with it.
Onshore mechanical completion certificate
Static test packs closed and A/B records signed before load-out.
Issued at the yard, ahead of sail-away.
Load-out punch list
Every outstanding item at the point of transport, owned and categorised.
Frozen at load-out; carried, not restarted, offshore.
Sea-fastening and transport inspection
The module survived transit undamaged.
On arrival at the installation site.
Offshore walkdown record
Subsystem condition matches the yard hand-off before commissioning starts.
First POB rotation after hook-up begins.
RFSU certificate
Commissioning complete and Category A punch clear.
Immediately before first hydrocarbon.
Walkdowns and POB
Walkdowns run at the tag with the people actually on board.
Offshore walkdowns are constrained by who is on the platform that week. A subsystem walkdown is raised and executed on a tablet at the tag, with punch created in the same pass rather than transcribed onto a list at the end of the shift.
Connectivity on a platform is patchy by design. Records, photographs and signatures are captured offline and synchronise when the device is back in coverage, keeping the time the work was actually signed rather than the time it reached shore.
Because every item has an owner and a category from the moment it is raised, the morning meeting runs from a filtered list — what blocks certification today, and who among the current POB is able to clear it.
Certification
Mechanical completion onshore, RFSU offshore, on the same ladder.
A subsystem that earned mechanical completion at the yard carries that certificate offshore with the signed records beneath it. It is not re-issued, and it does not need to be re-proven — the evidence chain is the same one the operator will audit.
RFSU is then issued offshore once commissioning is complete and Category A punch is clear. The gate is enforced by the data: the certificate cannot be issued while an unsigned record or a blocking punch item sits underneath it.
Readiness for first hydrocarbon is derived upward from those certificates, so the number in the operator's meeting onshore and the number in the offshore installation manager's report are the same number.
Terminology
The vocabulary of a hook-up campaign, defined the way an OIM actually uses it.
- POB
- Persons on board — the hard ceiling on how many people can work the platform at once, and the constraint every walkdown schedule is built against.
- Hook-up and commissioning (HUC)
- The offshore phase connecting completed modules together and proving them as one live system.
- SIMOPS
- Simultaneous operations — the matrix governing which activities (drilling, hot work, lifting, diving) can run together on a live platform.
- Sail-away
- The point a module or jacket leaves the fabrication yard, after which onshore mechanical completion is effectively frozen.
- First hydrocarbon
- The point gas or oil is first introduced to the process system, gated by RFSU across every subsystem in its path.
- OIM
- Offshore installation manager — the person with ultimate authority over what runs on the platform on a given day, including the SIMOPS matrix.
SIMOPS on a producing asset
Brownfield work happens around production, so every ITR carries an operational consequence as well as a technical one.
On a live platform, drilling, hot work, crane lifts and diving cannot all proceed at once. The simultaneous operations matrix decides what runs together and what waits, and that matrix is enforced day by day by the offshore installation manager, not by the project schedule written onshore.
A tie-in on the test separator may reroute a well; an ESD valve replacement may need a partial process shutdown; a flare tip inspection needs a flare-out window. Each of those is a production decision attached to a piece of completions scope.
Brownfield ITRs and work orders carry the production impact of the work they cover, so the campaign is sequenced against what the asset can actually accommodate — and the offshore team plans from the same register the project reports from.
How it runs
How a platform hook-up is set up in Deskely.
The aim is that the offshore campaign inherits proof, not paperwork. Everything that makes that possible is decided onshore.
- 01
Structure by subsystem, not location
Topsides, jacket, marine and utility scopes are broken into subsystems that stay stable through fabrication, load-out and hook-up.
- 02
Draft the register from drawings
P&IDs, single line diagrams and equipment lists are parsed into a tag register with drawing references retained for engineer review.
- 03
Close what can be closed onshore
Mechanical completion is earned at the yard wherever the scope allows, so the offshore workload is defined by evidence rather than assumption.
- 04
Carry punch with owners through load-out
Items raised at the yard keep their category, photograph and owner offshore instead of restarting as discovery work.
- 05
Execute offshore offline
Walkdowns, ITRs and punch are completed on tablets at the tag with no connectivity assumed, synchronising when back in coverage.
- 06
Issue RFSU and export the dossier
Certificates are issued from signed records, and the handover dossier exports per subsystem as each one is earned.
FAQ
Questions about Fixed platforms scopes.
Keep reading
Oil and gas commissioning
The full sector view: certification ladder, preservation, handover and the terminology behind them.
Read morePunch lists
Category A and B punch raised at the tag, carried with an owner, and blocking certification where it should.
Read moreCertificates
MC, RFSU and handover certificates issued from signed records, with the gates enforced by the data.
Read moreOther oil and gas scopes: LNG trains and gas processing, FPSO and floating production, Brownfield tie-ins and turnarounds, Subsea tie-backs, Refineries and petrochemical, Pipelines and compressor stations, Terminals, tank farms and jetties, Hydrogen, ammonia and carbon capture, Decommissioning and late life.