FPSO and floating production
FPSO completions where the record travels with the module.
Topsides in one yard, hull in another, integration in a third and hook-up offshore. Deskely keeps a package's history attached to the package itself, so what was tested at the fabricator is still provable after sail-away.
- Certification level
- Module and subsystem
- Locations
- Yard to offshore
- Parties
- EPC, yards, vendors
- Constraint
- POB and sail-away
Choose your project type
The problem
The record is built in one country and audited in another.
A topsides module is fabricated and tested at one yard, shipped to an integration yard, lifted onto a hull built somewhere else, then sailed to field and hooked up offshore. At each of those moves the scope changes hands, and traditionally so does the paperwork format.
What gets lost in the moves is not usually the certificate. It is the layer beneath it: the calibration sheet from the vendor's works test, the punch item raised at the fabricator that quietly disappeared from the integration yard's list, the preservation cycles that lapsed during the tow.
The offshore hook-up campaign then runs against a fixed number of berths and a limited weather window, and every hour spent re-verifying something already proven onshore is an hour not spent on the tie-in work that genuinely could not be done at the quayside.
Contract chain
Six parties, one hull, and no single owner of the register.
An FPSO scope splits cleanly along yard and vendor lines, and each party needs to work in its own lane without inheriting someone else's paperwork format.
EPC / integrator
Overall completions schedule and RFSU sequencing
Signs
Rolled-up module and subsystem readiness across all yards
Topsides fabrication yard
Module construction, static and loop testing
Signs
MC certificates and A/B ITRs per module before load-out
Hull yard
Marine systems, structural completion, ballast and mooring
Signs
Class-witnessed test records and hull MC packages
Integration yard
Module mating, interconnecting piping and cabling
Signs
Tie-in ITRs referencing both module registers
Vendor package suppliers
Skid-mounted equipment — compression, power generation, water treatment
Signs
Works test certificates carried forward into the project register
Offshore commissioning team
Hook-up, live commissioning, RFSU and first oil
Signs
C records, punch closure and PSSR evidence pack
One register, many locations
Scopes split by yard and vendor, records held in one place.
Every party on an FPSO — the EPC, each yard, each vendor package supplier — needs to work on their own scope without seeing or editing everyone else's. That requirement is exactly why projects end up with four registers in the first place.
In Deskely the split is done with access rights instead of files. A vendor completes and signs only the records for its own package; a fabrication yard sees only the modules it is building. Progress still rolls up into the project register with no import step, because there was never a separate file to import.
So when a module leaves the yard, nothing has to be handed over. The module's tags, records, punch items and preservation history are already in the register the offshore team will use.
Certification ladder
From module MC to first oil, each gate names its evidence.
The same ladder recurs at module, subsystem and system level, which is why it has to be enforced by the data rather than tracked by memory.
- 01
Module MC
A and B records signed, static testing complete, no open Category A punch
Fabrication yard QC lead
- 02
Load-out release
Module MC issued, preservation routines initiated, structural sea-fastening verified
Yard marine warranty surveyor
- 03
Integration acceptance
Interconnecting tie-in ITRs signed, module punch reconciled against fabricator list
Integration yard completions manager
- 04
RFSU (per subsystem)
C records for the subsystem signed, Category A punch closed, preservation current
Offshore commissioning manager
- 05
PSSR
RFSU issued on all safety-critical subsystems, operating procedures reviewed, evidence pack exported
Operator PSSR chair
- 06
First oil
PSSR closed, process safety systems proven live, marine class endorsement current
Operator representative
Sail-away and hook-up
Decide what sails with punch open, with the list in front of you.
Sail-away is a judgement made under commercial pressure: which subsystems are genuinely complete, which can be finished offshore, and which items are being accepted as carry-over. That judgement is only as good as the punch list it is made against.
Punch in Deskely is raised at the tag, with photographs, split by category and owned by a named party. Category A blocks the certificate above it outright. Category B is carried forward, still visible after sail-away, still assigned, and still counted in the offshore workload rather than forgotten in a closed-out spreadsheet.
The offshore campaign is then planned against evidence: subsystems that already earned mechanical completion onshore are not re-walked, and the limited bed space is spent on hook-up, live testing and the punch that was always going to be offshore work.
What actually slips
The failure modes are the moves, not the testing itself.
None of these are technical problems. They are handover problems, which is exactly where a paper-and-spreadsheet process is weakest.
Punch item lost between yards
A Category B item raised at the fabricator does not reappear on the integration yard's list, and resurfaces offshore as a surprise.
Punch stays attached to the tag across every yard move, with no re-entry step.
Preservation lapses during tow
Rotating equipment and instrumentation sit idle for weeks during the sail from integration yard to field with no one routine covering the whole voyage.
Preservation cycles run per tag on their own cadence and flag as overdue automatically, tow or no tow.
Vendor test data never reaches the project register
A works test certificate is filed by the vendor and referenced by a document number that means nothing to the offshore team.
Vendor packages complete their own ITRs directly in the shared register under access control.
Offshore re-testing to be safe
Without confidence in the onshore record, the offshore team re-walks subsystems that were already proven, burning bed-days and weather window.
Signed A/B records with signatory and timestamp travel with the module, so re-testing is a choice, not a default.
Handover to operations
The dossier assembles itself from the record that was already there.
By first oil, an FPSO handover dossier has to reconcile records from four or five yards, dozens of vendor packages and an offshore campaign, into a single package the operator's asset team can rely on for the life of the field.
Because every one of those records was signed against the same tag in the same register, the dossier is a filtered export rather than a reconstruction project. It carries the fabrication yard's works test, the integration yard's tie-in ITR and the offshore commissioning team's C record for that tag as one continuous chain.
That continuity is what an insurer or a class society actually wants to see when a warranty question comes up years into operation: not a summary, but the original signed record from wherever it was created.
Typical scale
The numbers behind a floating production project.
3–5
yards and integration sites
fabrication, hull, integration and offshore
40–80
vendor package scopes
each with its own works test record
12–18 mo
typical preservation duration
from load-out to first oil
6–10 wk
offshore hook-up and commissioning window
fixed by vessel and POB constraints
How it runs
How an FPSO scope is set up in Deskely.
The organising principle is that the record belongs to the module, not to the location or the contractor currently holding it.
- 01
Structure by module and subsystem
Topsides modules, hull systems and marine systems are broken into subsystems that stay stable from fabrication through to offshore, so nothing has to be re-mapped after a move.
- 02
Scope each party with access rights
Yards, vendors and subcontractors are given edit and signature rights over their own packages only, while progress still rolls up to the project register.
- 03
Capture vendor package records in place
Works test results, calibration sheets and certificates from vendor packages are attached to the tags they belong to rather than filed as a separate document set.
- 04
Run preservation through the tow
Routines continue across yard moves and the transit, so the gap that normally appears during sail-away is visible if it happens and provable if it does not.
- 05
Agree carry-over at sail-away
Punch is reviewed by category with owners assigned, so what sails with open items is a decision on record rather than a discovery offshore.
- 06
Close out offshore against evidence
Hook-up and commissioning work from subsystems that already hold mechanical completion, and the handover dossier exports per subsystem as it is earned.
FAQ
Questions about FPSO 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 moreITR records
A, B and C records completed on tablets in the field and signed against the tag they belong to.
Read moreOther oil and gas scopes: LNG trains and gas processing, Brownfield tie-ins and turnarounds, Fixed platforms and jackets, Subsea tie-backs, Refineries and petrochemical, Pipelines and compressor stations, Terminals, tank farms and jetties, Hydrogen, ammonia and carbon capture, Decommissioning and late life.
