From FID to Class Approval: How a Skid Supplier Collaborates on an FPSO Program — A Case Study (2026)

In 2026, the FPSO order book is no longer just a forecast — it is signing. SBM Offshore advanced FEED work on the Longtail program offshore Guyana, and Petrobras moved the P-81 and P-87 units toward and through final investment decision offshore Brazil. After a quiet stretch, several large floaters have crossed FID, and the procurement clock has started on the modules that fill their decks.

When a program crosses FID, something changes for everyone downstream. The owner and the EPC stop debating concepts and start committing dates. A topsides package that was a block on an early plot plan becomes a real purchase order with a real class-approval milestone behind it. And the skid supplier — the company that will actually weld, assemble, certify and ship those modules — stops being a line on a bid tab and becomes a partner whose cadence the whole program now depends on.

This is a case study about that transition. The names are removed on purpose — this was an FPSO support package built for an overseas owner, integrated by an overseas engineering company, with hull work at a domestic shipyard. What we can talk about is the part that generalizes: what it actually takes for a skid supplier to collaborate well on an FPSO program, from the moment FID lands to the moment the class society signs the approval drawings. If you are evaluating who builds your modules for the next FID, this is the behavior to look for.

Project Snapshot (Anonymized)

Item	Detail
Program type	FPSO topsides support package (process / utility skids)
Owner	An overseas owner (anonymized)
Integrator	An overseas engineering company (topsides systems integrator)
Hull / integration	A domestic shipyard (hull and deck integration)
Lmart scope	Design → fabrication → integration → testing → documentation of skid modules, delivered as a series
Classification	Marine class society approval (society named per project; one of DNV / ABS / BV / CCS / LR / NK)
Delivery model	Series cadence — repeated, version-controlled units against a single program
Lmart role	Self-performed design, manufacture, integration, test and MRB documentation in-house

Specific vessel names, hull numbers, the owner's identity and any commercial figures are withheld. The credentials cited below — 600+ PQR, 8,000 m² assembly workshop, multi-society certification, documented series deliveries of six and twelve reliquefaction units and eight-skid BOG compressor sets — are published Lmart credentials and are the only concrete numbers used here.

Background: Why FID Changes the Supplier's Job

Before FID, a skid supplier mostly answers questions: budget pricing, indicative weights, a rough lead time. The work is reversible. After FID, the work is committed — and the cost of being wrong moves from "revise a spreadsheet" to "redo a lifting plan on a module already on a barge."

On this program, FID meant three things landed on the supplier's desk almost at once:

• A frozen interface basis. The integrator's interface register stopped being a draft. Every tie-in, every termination, every structural connection to the deck now had to be reconciled against a controlled document — and held there through fabrication.
• A class-approval milestone with the vessel behind it. The skids' approval drawings were now on the critical path of a floater that could not be certified until every module's documentation was in order.
• A series cadence, not a one-off. Because the package was a repeated set of units, the supplier was committing not to "build one" but to "build the Nth one identical to the first, on a schedule the integration sequence depended on."

A supplier who treats post-FID work the way they treated the pre-FID quote — reactively, one drawing at a time — becomes the program's problem. The collaboration described below is what it looks like to treat it the other way.

The Challenge

Three pressures defined this package, and they pulled in different directions.

Schedule coupling. The skids were not the long pole on their own, but they were coupled to two things that were: the class society's drawing-review queue, and the shipyard's deck-integration window. A late approval drawing would not just delay a skid — it would ripple into the vessel certification plan. A skid that missed its integration slot would have to wait for the next one, weeks away.

Interface stability across a series. When the same module repeats, an interface change discovered on unit three is not one change — it is a change that has to propagate backward to units one and two and forward to the rest. Without disciplined version control, a series amplifies every mistake.

Multi-stakeholder alignment. The owner cared about certification and total schedule. The integrator cared about interfaces and weight/CoG fitting the topsides model. The shipyard cared about lift plans and sea-fastening. The class society cared about rule compliance and documentation. Four parties, four priorities, one set of skids that had to satisfy all of them simultaneously.

The challenge, in one sentence: deliver a repeatable series of certifiable modules, on a cadence locked to a class queue and a deck window, while keeping four stakeholders aligned to one moving truth.

Why the Owner and Integrator Selected Lmart

Selection on a post-FID FPSO package is not a price auction. The integrator and owner were buying down risk, and they evaluated the supplier on the ability to collaborate, not just to fabricate. Three things carried weight.

A single in-house chain. Lmart performs design, fabrication, integration, testing and documentation in-house. On a program where interface changes and class comments have to turn around in days, a supplier whose design team sits in the same building as its welders can close a loop that a supplier juggling subcontractors cannot. There is no "let me check with the fabrication shop" — the fabrication shop is down the hall.

Demonstrated series delivery. The package was a series, and the question "can you repeat a module N times without drift?" is answered by track record, not promises. Lmart had delivered marine skids in true multi-unit series before — reliquefaction units in batches of six and twelve against a single vessel program, and BOG compressor skids supplied in sets of eight across sister hulls. That is the difference between a supplier who has solved repeatability and one who is about to discover it on your program.

Multi-society fluency. The skids had to clear a marine class society, and Lmart's programs have been certified across DNV, ABS, BV, CCS, LR and NK. A supplier who already speaks a surveyor's language inherits that fluency to the program as schedule certainty — the approval clock runs shorter when the drawings arrive in the form the society expects.

Capacity to hold cadence. An 8,000 m² assembly workshop and 600+ qualified welding procedures (PQR) meant the series could be held on a steady beat without subcontracting quality away to hit a date.

None of these is a slogan. Each is the answer to a specific question the integrator asked before the award.

The Engineering and Manufacturing Approach

Once the package was awarded, the collaboration moved through a sequence designed to keep the four stakeholders on one truth.

Lock the interface basis before cutting steel

The first work was not fabrication — it was reconciliation. The skid battery limits, tie-ins and tagged terminations were mapped directly onto the integrator's interface register and tag philosophy, and the open questions (who supplies first-fit vs. loose-shipped spools, gaskets and fasteners) were closed in writing. Only when the interface basis was locked were fabrication drawings released. A flange that points the wrong way is cheap to fix on a drawing and very expensive to fix on a module already on the deck — so the cheap fix happened first, by design.

Design to the class society's expectations from drawing one

The approval drawings were prepared to the named society's review expectations from the start, not reworked into them after the first round of comments. Because the in-house design team had worked directly with the major societies, class comments were turned around in days rather than weeks — which is what keeps a module off the vessel's critical path.

Manage weight and CoG as a tracked quantity

Each skid carried a maintained MTO-based weight and center-of-gravity report, tracking as-designed against as-built so the integrator's topsides model and the shipyard's lifting plan never drifted from reality. Lifting lugs were designed and certified for the actual load case, with sling angles and hook positions worked out; sea-fastening provisions for the voyage to the integration yard were designed into the frame, not bolted on later.

Freeze and version-control the series

For a repeated package, the fabrication drawings were frozen and version-controlled so unit N matched unit one. A change accepted late was propagated across the series under control, not patched silently on whichever unit happened to be on the bench. This is the discipline that lets a series stay a series.

Execution, QC and Delivery

The build phase was run as a series with checkpoints, not as a sequence of independent jobs.

• Material and Ex traceability up front. Pressure-part materials carried mill certs (EN 10204 3.1 / 3.2 as specified) with heat-number traceability from plate to weld; hazardous-area equipment was certified to the project's required Ex protection level and zone. The documentation spine was built as the steel was built — not chased afterward.
• Welding behind every joint. The mix of carbon steel, stainless and other alloys on offshore work means every joint needs a qualified procedure behind it; Lmart's 600+ PQR library is exactly what lets a series like this proceed without stopping to qualify a new procedure mid-run.
• Structured FAT against an agreed ITP. Each unit passed a Factory Acceptance Test with the client and class present, run against an agreed inspection and test plan — so acceptance was a milestone, not a negotiation.
• MRB closeout per unit. Each module shipped with a complete Manufacturing Record Book — certs, NDT reports, test records, as-built drawings — so the integrator was not chasing paper during hook-up, and the vessel's certification could close on schedule.
• Cadence held to the deck window. Because production capacity could hold the beat, units arrived aligned to the integration sequence rather than bunched or late.

The Result

The package was delivered as a controlled series of certifiable modules, with approval drawings cleared on the class society's terms and MRB documentation closed unit by unit. Because the interface basis was locked before steel was cut and the series was version-controlled throughout, the modules arrived at the weights and interfaces the integrator's model expected — which is what lets a deck-integration window stay a window instead of becoming a rework campaign.

The generalizable outcome is the one that matters to anyone planning the next FID:

• No surprises on the critical path — the skids stayed off the vessel's certification critical path because the drawings cleared on the society's terms.
• A series that stayed a series — version control meant the last unit matched the first, so integration learned-once applied to all.
• A clean documentation hand-off — MRB closeout per unit meant the integrator and class inherited a complete package, not a paper chase.
• One supplier accountable end to end — design through documentation under one roof meant one phone number for every interface and class question.

In the Customer's Words (Generalized)

Specific quotes and the customer's identity are withheld by agreement. Generalized, the feedback from programs of this kind comes down to a single theme that recurs across our marine and offshore work:

"What we valued was not that the modules were well built — we expect that. It was that the supplier behaved like part of the program: interfaces locked early, class comments turned around fast, the same unit delivered again and again on cadence, and a clean documentation package at hand-off. After FID, that is the difference between a vendor and a partner."

That is the bar a post-FID FPSO package sets, and it is the bar this collaboration was built to clear.

What This Case Study Generalizes To

If you are an EPC, integrator or owner preparing a topsides package for the next FID, the takeaways transfer directly:

Program need	What to look for in a skid supplier
Stay off the vessel critical path	Demonstrated class-drawing fluency with your society; in-house design to turn comments in days
Hold a series without drift	A delivered multi-unit series with version-controlled drawings — not a single prototype
Keep interfaces aligned	A supplier who locks the interface register before cutting steel and holds it across the series
Protect the deck window	Production capacity to hold cadence; weight/CoG and sea-fastening managed as tracked quantities
Close certification cleanly	Per-unit MRB closeout and structured FAT against an agreed ITP
One accountable partner	Design → fabrication → integration → test → documentation under one roof

A supplier who can show you a real, delivered program against these points is not the cheapest line on your bid tab. They are the one whose cadence you can build a vessel schedule on — which, after FID, is what you are actually buying.

FAQ

What does "supplier collaboration on an FPSO program" actually mean after FID?
It means the skid supplier behaves as part of the program rather than as an order-taker: locking the interface register with the integrator before fabrication, designing approval drawings to the class society's expectations from the start, turning class comments around in days, managing weight and CoG as tracked quantities, holding a series on a version-controlled cadence, and closing MRB documentation per unit so the vessel's certification stays on schedule.

Why is the class approval-drawing timeline so critical on an FPSO?
Because the vessel cannot be certified until every module's drawings and documentation clear the class society. A skid supplier slow on drawing approval can put the entire floater on the critical path. A supplier who has worked directly with the relevant society and keeps an in-house design team can turn comments around in days, which keeps the module — and the vessel — off the critical path.

How do I verify a supplier can deliver a series, not just a prototype?
Ask for a delivered multi-unit series: how many identical units, over what period, under which class society, with what drawing version-control. A supplier who has shipped, for example, six or twelve identical reliquefaction units against one program, or eight BOG compressor skids across sister hulls, has demonstrably solved the repeatability problem.

Why does an in-house design-to-documentation chain matter for collaboration?
Because post-FID work lives on fast loops — interface changes and class comments have to turn around quickly and propagate across a series under control. A supplier whose design, fabrication, integration, testing and documentation sit under one roof can close those loops in days; a supplier coordinating subcontractors usually cannot.

Further Reading

• Modular Skid Packages: Workshop to Sea Trial
• Reliquefaction Skids: A Decade of Series Delivery
• BOG Compressor Skids for LNG-Fuelled Vessels
• Lmart Marine & Offshore Project References

---

Lmart (Suzhou Lmart Energy Equipment Co., Ltd.) designs, fabricates, integrates, tests and documents modular process skids for marine and offshore programs in-house, certified across DNV, ABS, BV, CCS, LR and NK. If you're preparing a topsides skid package for an upcoming FID, we're happy to walk through how this collaboration would map to your program.