Tanker to FPSO, jack-up, module integration

    Conversion project software for a hull that already has systems on it, and a scope that keeps changing.

    A conversion starts with an existing hull, an as-built that never quite matched reality, and a new topsides or module scope layered on top. Deskely tracks what is kept, what is removed and what is new, so the register reflects the vessel as it actually is at every stage of the conversion.

    Scope
    Legacy hull plus new topsides
    Parties
    Yard, integrator, owner, class
    Order
    Strip, reinstate, integrate
    Gate
    Class re-classification
    FPSO CONVERSION — TOPSIDES MODULE T-3CONVERSION SPEC · REV CRETAINEDNEW PROCESS MODULEMOD-CONV-04LIFT POINTTie-in group T-2CUT-OUT AND STRENGTHENING ZONE — 8 M SPANTAG REGISTERCT1-IGC-VLV-11Inert gas control valveRecords signedHULL-BLST-04Ballast tank, legacy hullIn testT3-SEP-101Production separatorPreservationT3-FLR-STKFlare stack supportPunch open180 sheetsunder one system hierarchy

    The problem

    The as-built drawing says one thing, the hull says another.

    A conversion inherits decades of prior repairs, class notations and modifications, few of which are fully reflected in the drawings the yard is handed at the start.

    New topsides, modules and systems are being integrated onto that uncertain baseline on a schedule set before the true condition of the hull was known.

    Deskely lets the register be corrected as the hull is surveyed, so the plan of record reflects reality rather than an assumption made before steel was opened up.

    LEGACY SYSTEMS MEET NEW SCOPETanker → FPSO conversionOriginal build records are decades old, incomplete, or simply goneORIGINAL BUILD, 1998Ballast system — assumed sound, unverifiedCargo piping — assumed sound, unverifiedHull structure — assumed sound, unverifiedNEW SCOPE, TODAYTurret mooring — fully specified, fully testedProcess modules — fully specified, fully testedLiving quarters — fully specified, fully testedUnknownwhether legacy ballast and cargo systems still meet class after conversionWHAT RE-CLASSIFICATION ACTUALLY NEEDSEvery legacy system re-verified against current class rules, alongside every new moduleOne register, not a paper trail split across two build erasDeskely carries legacy and new-build tags in the same register, both proven before delivery.

    Setting up the register

    Legacy systems, removed scope and new scope are tracked as three separate populations.

    Existing systems that are retained, systems that are being removed or made redundant, and new systems being installed each need a different verification approach.

    General arrangements, legacy system diagrams and new module equipment lists are parsed into one register, tagged by which population they belong to.

    That separation is what stops a retained system being re-tested unnecessarily, and stops a new system being assumed proven because it sits next to something that already was.

    1 · SOURCE DOCUMENTSConversion GA rev C9 modulesLegacy hull drawings180 sheetsTopsides P&IDs62 systemsStructural strengthening…34 sheetsPARSE + MATCHtag · description · drawing ref2 · ONE TAG REGISTERCT1-IGC-VLV-11Inert gas control valveMODULE T-3HULL-BLST-04Ballast tank, legacy hullHULLT3-SEP-101Production separatorMODULE T-3T3-FLR-STKFlare stack supportTOPSIDESTWO DOCUMENTS DISAGREEConversion GA rev…Ballast tank, legacy hullLegacy hull drawi…Abbreviated descriptionEngineer picks the sourcedecision loggedWeeks of transcription become a draft an engineer reviews.

    Execution

    Module integration and interface testing leave a signed record at every tie-in.

    As modules land and are integrated onto the hull, interface tie-ins between new and legacy systems are recorded against both sides of the connection.

    Field teams capture hook-up, hydrotest and functional records on tablet, with photos mandatory at every tie-in point.

    Punch raised at an interface is visible to both the module contractor and the yard, rather than being owned by whichever side notices it first.

    LEGACY AUDIT THROUGH REDELIVERYVessel conversionLegacy system audit against current class rules142 legacy systems reviewedStrip-out and demolition sign-offCompartments released for new worksNew module installation and hook-up68 of 90 modules completeRe-classification surveyClass surveyor on siteSea trials on converted systemsAwaiting survey close-outRedelivery to ownerAwaiting sea trial certificateLegacy and new-build tags share the same gate ladder, not two separate tracking systems.

    Re-classification and trials

    Class treats a conversion as a new vessel in almost every respect that matters.

    Re-classification typically requires the same rigour as a newbuild survey programme for the converted and new scope, layered on top of whatever retained class notations still apply.

    Harbour and sea trials for a conversion focus on the new and modified systems, but still have to demonstrate the vessel as a whole functions as intended.

    Deskely holds class survey status alongside yard and owner acceptance so a single view shows what is left before re-delivery.

    Module T-3 — conversion acceptance ladderNew topsides scope gates on both new and legacy hull recordsMCMechanical completionIssued 02 MayModule fit-out records612 / 612Hull strengthening verifiedcompleteHATHarbour acceptance testBlocked — module T-3Process loop checkout418 / 480Flare system validationnot startedSATSea acceptance testBlocked — HAT openHAT certificatenot issuedBlocking punch7 open

    Handover

    The owner receives a hull with two histories that both need to survive into operations.

    The as-converted dossier has to reconcile legacy documentation with new construction records, in a form the operating crew and class can both use.

    Because both populations live in the same register throughout the project, the final export merges them rather than requiring a separate reconciliation exercise.

    Every signature keeps a name, role and timestamp, which matters more on a conversion than almost anywhere else given the mixed provenance of the documentation.

    AUDIT QUERYCT1-IGC-VLV-11Module T-3 · inert gas system · control valveFull history retrieved in one queryINSTMechanical installationTopsides subcontractor20 JanHOOKPiping tie-inYard fitter02 FebIOLoop checkoutControls engineer14 FebFUNCFunctional testEquipment maker28 FebCERTIFICATEMCMechanical completion02 MayYard project managerPrerequisites demonstratedThe dossier ties legacy hull history to new topsides records under one tag.

    Stability recalculation after the conversion

    The hull that floated fine as a tanker has to float fine again as an FPSO, a jack-up or whatever it becomes.

    Adding a full new topsides, a drilling package or accommodation modules onto an existing hull changes displacement, centre of gravity and trim in ways the original vessel's stability book never accounted for, and class will not re-issue a stability certificate on an assumption.

    A second inclining experiment, or an equivalent lightweight survey, is normally required once the new scope is substantially installed, and it depends on an accurate as-converted weight record covering both what was removed from the original hull and what has been added.

    Deskely tracks removed, retained and new weight against the same population tags used for commissioning, so the as-converted weight and centre of gravity submission to class is assembled from signed installation records rather than reconstructed from two separate project files at the last minute.

    AS-CONVERTED DOSSIERLegacy and new build, one recordOriginal build records reconciled against the new conversion scopeRECONCILED EVIDENCE SETLegacy hull and ballast systems re-verifiedNew modules commissioned and testedInterfaces between legacy and new systems testedRe-classification survey report attachedDOSSIER TRACES BOTH BUILD ERAS1998 original build records2024 conversion scope recordsBoth referenced from the same tag, not two archives2 erasone traceable asset register at redeliveryThe class surveyor reads one dossier, not a reconciliation exercise between two archives.

    How it runs

    From an existing hull to a re-classed, re-delivered vessel.

    Conversions reward a register that can absorb correction, because the true condition of the vessel is discovered as the project proceeds.

    1. 01

      Survey and baseline the hull

      Legacy systems tagged and reconciled against as-built drawings as they are confirmed by survey.

    2. 02

      Separate the three populations

      Retained, removed and new scope tracked distinctly within one register.

    3. 03

      Parse the new scope

      Module and topsides equipment lists and diagrams drafted into the register alongside legacy tags.

    4. 04

      Template interface records

      Tie-in, hook-up and hydrotest records defined for every point where new meets legacy.

    5. 05

      Track class re-classification

      Survey status held against the same tags as yard and owner acceptance.

    6. 06

      Export the as-converted dossier

      Legacy and new-build records merged into one handover package for the owner and class.

    FAQ

    Questions about Vessel conversions scopes.

    Ready to digitize
    commissioning and
    handover?

    We use cookies to improve your experience.
    You can opt out of certain cookies.
    Find out more in our privacy policy.