Subsea tie-backs and SURF
Subsea completions where the interface is not where evidence disappears.
Umbilicals, jumpers, control systems and the host topsides interface are tested in stages by different parties. Deskely holds those records under one subsystem so SIT results, offshore installation checks and topsides commissioning read as a single chain.
- Certification level
- Interface and subsystem
- Test stages
- FAT, SIT, offshore
- Parties
- SURF, SPS, host
- Constraint
- Vessel window
Choose your project type
The problem
Four contractors, one flow path, and no shared record.
A tie-back is delivered by parties that barely share a document format. The subsea production system supplier tests trees and control modules at the works. The SURF contractor tests flowlines, jumpers and umbilicals. The installation contractor proves continuity offshore. The host platform team commissions the topsides interface and the master control station.
Each of them produces good records. What no one owns is the join. The umbilical passed continuity at the quayside and the control module passed FAT, but the question the operator asks at first oil is whether that specific electrical and hydraulic path was proven end to end, and by whom.
When the answer lives across four registers, closing it out means reconciliation — usually days of cross-referencing document numbers during the one vessel-days-limited window when the answer actually matters.
Working vocabulary
The words this scope actually uses, defined once, used consistently.
Subsea projects carry more overlapping test terminology than most scopes. Deskely records keep these distinct rather than collapsing them into a generic 'test complete' status.
- FAT
- Factory acceptance test — the SPS supplier proves a tree, manifold or control module against spec before shipment.
- SIT
- System integration test — control system, umbilical and SPS hardware proven together, usually onshore, before offshore installation.
- EFAT
- Extended FAT run alongside SIT, exercising the full control loop from topsides MCS to subsea actuator.
- Continuity test
- Offshore verification that an installed umbilical or jumper's electrical, hydraulic and fibre cores match the as-built and have not been damaged in transit or lay.
- MCS
- Master control station — the topsides system that commands and monitors the subsea production system.
- Tie-in
- The mechanical and hydraulic connection between a flowline or jumper and a host structure, tree or manifold, proven by leak and pressure test.
- Vessel window
- The scheduled period a construction or IMR vessel is on station, which fixes how much offshore testing can be attempted before demobilisation.
- RFSU (subsea)
- Readiness for start-up applied to a subsea drainage point once its full flow path — well to host — has been proven and signed.
Proving the loop before it goes subsea
SIT is where four suppliers' equipment has to behave as one system.
System integration testing brings the subsea control modules, umbilical and topsides master control station together, usually onshore at an integration facility, before anything is installed. It is the one point in the project where the full control loop can be exercised without a vessel on station.
The value of SIT depends entirely on whether its results are usable later. If the SIT record for a control module sits in the SPS supplier's own system and the umbilical's SIT record sits in the SURF contractor's, an offshore fault six months later still means two phone calls and a document search before anyone can rule the loop in or out.
Recording SIT results against the same tag structure the offshore continuity test will later use means a control fault at first oil can be traced straight back to the SIT result for that exact module, no reconciliation required.
Contract chain
Three contractors and a host operator, one interface each.
SPS supplier
Trees, manifolds, control modules — design, FAT and offshore installation support
Signs
FAT certificates and offshore commissioning check sheets
SURF contractor
Flowlines, jumpers, umbilicals — fabrication, lay and tie-in
Signs
FAT, continuity test and tie-in leak test records
Host operator commissioning team
Topsides interface, MCS configuration, RFSU sequencing
Signs
C records and the signed end-to-end flow path certificate
The interface itself
The flow path is the subsystem, not any one party's scope.
A conventional subsystem breakdown puts trees under the SPS package and flowlines under SURF, which is administratively convenient and operationally useless — the operator does not commission a tree in isolation, it commissions a drainage point, and a drainage point is a well, a jumper, a flowline, an umbilical and a topsides riser interface acting together.
Deskely lets the register hold both views. Tags roll up under the contractual package for progress reporting, and separately under the flow path for readiness. A single control umbilical can sit inside three different flow-path subsystems if that is how the field is actually drained, without triplicating the tag.
The interface record itself — continuity proven, hydraulic function tested, control signal verified end to end — is captured once, referenced by every subsystem that depends on it, and signed by whichever party actually witnessed the test.
Certification ladder
From works test to RFSU, each gate crosses a different contractor.
Every gate on a tie-back sits at a handover between parties, which is exactly why each one needs an explicit prerequisite rather than an assumed one.
- 01
FAT
Equipment built and function-tested against spec at the vendor works
SPS or SURF supplier QA
- 02
SIT
FAT complete on all modules in the loop, control system software finalised
Integration test lead
- 03
Offshore installation acceptance
Equipment received undamaged, pre-installation checks signed
Installation contractor superintendent
- 04
Continuity test
Umbilical or jumper landed and terminated, as-built cores verified
SURF commissioning engineer
- 05
Tie-in verified
Continuity test passed, pressure and leak test signed on the connection
Host commissioning engineer
- 06
RFSU (drainage point)
Full flow path proven well to host, Category A punch closed
Host operator commissioning manager
What actually costs vessel days
Every one of these is a record problem wearing a schedule problem's clothes.
None of these risks come from difficult engineering. They come from evidence that exists but cannot be found or trusted when it is needed.
Offshore fault traced back through paper
A continuity fault offshore triggers a manual search through SIT records held in a different contractor's system to establish whether the fault is new or pre-existing.
SIT and continuity records live against the same tag, so the prior result is one lookup away.
Duplicate testing across the interface boundary
Both the SPS and SURF teams re-test the same umbilical termination because neither trusts the other's paperwork.
Shared register with access control lets each party see the other's signed result without editing rights.
Vessel remobilised for a closed punch item
A Category B punch item from the installation campaign is not visible to the follow-up IMR campaign planning team.
Punch stays open and assigned in the register until formally closed, visible to whichever team plans the next vessel trip.
RFSU delayed by an untraceable subsystem boundary
The drainage point cannot be signed off because no single document shows the full well-to-host chain.
The flow-path view rolls every contractor's record for that path into one readiness figure.
What a drainage point is signed against
The records that carry a flow path from the works floor to first oil.
A subsea drainage point is accepted well to host, so its dossier has to hold results from four different contractors under one tag structure. These are the six an operator asks for first when a fault has to be traced.
FAT record
A tree, manifold or control module meets its design specification before leaving the works
At the vendor works, ahead of shipment
EFAT run log
The full control loop, from MCS to subsea actuator, behaves correctly under simulated field conditions
Alongside SIT, before offshore mobilisation
SIT report
Control modules, umbilical and topsides master control station operate together as one system
Onshore, before offshore installation
ROV interface verification
Subsea connectors and intervention points are accessible and function correctly to an ROV
During offshore installation
Flowline pre-commissioning dewatering record
A flowline is dry to specification before it is placed into service
After hydrotest, before first flow
Continuity test record
An installed umbilical or jumper's cores match the as-built after lay
Immediately after landing and termination offshore
Typical scale
The numbers behind a subsea tie-back campaign.
3–6
drainage points per tie-back
each with its own end-to-end flow path
20–40
vessel days for SURF installation
fixed window, weather-dependent
150+
umbilical and jumper cores per continuity test
electrical, hydraulic and fibre
3
contractors per flow path
SPS, SURF and host, minimum
How it runs
How a subsea tie-back is set up in Deskely.
The organising decision is to structure by flow and control path rather than by contract, so interfaces have a home before anyone tests them.
- 01
Define subsystems by flow path
Flowlines, risers, umbilicals, control modules and the topsides interface are grouped by the path they serve rather than by supplier.
- 02
Scope each contractor with access rights
SPS, SURF, installation and host teams sign only their own records while progress rolls up into one register.
- 03
Record FAT and SIT against the tag
Works and integration test results are attached to the equipment tag so later stages read as a continuation rather than a new document set.
- 04
Preserve between stages
Routines run on equipment waiting in yards between SIT and installation, with overdue cycles surfaced as they happen.
- 05
Prove continuity offshore
Installation and function checks are captured offline at the tag and close the interface records opened during SIT.
- 06
Certify and export per subsystem
RFSU is gated on signed records and clear Category A punch, and the dossier exports in the operator's retention structure.
FAQ
Questions about Subsea tie-backs scopes.
Keep reading
Oil and gas commissioning
The full sector view: certification ladder, preservation, handover and the terminology behind them.
Read moreITR records
A, B and C records completed on tablets in the field and signed against the tag they belong to.
Read morePreservation
Per-tag routines on their own cadence, with overdue cycles surfaced continuously rather than at handover.
Read moreOther oil and gas scopes: LNG trains and gas processing, FPSO and floating production, Brownfield tie-ins and turnarounds, Fixed platforms and jackets, Refineries and petrochemical, Pipelines and compressor stations, Terminals, tank farms and jetties, Hydrogen, ammonia and carbon capture, Decommissioning and late life.
