Storage and Offloading Without an FPSO — FSOs, CALM Buoys, and Shuttle Tankers

Introduction

An FPSO carries its own answer to the storage question — the hull is the tank. A MOPU or a fixed platform does not. When such a facility develops a field with no export pipeline, the produced crude has to go somewhere between leaving the process and reaching the refinery: it has to be stored on the water and offloaded to a tanker.

That storage-and-offloading system is not an afterthought bolted onto a production concept. It is a major piece of marine and process engineering in its own right, and its constraints — storage volume, offloading availability, tanker parcel size — propagate back into the production facility and frequently set the limit on what the field can actually deliver. A MOPU that can produce 30,000 bpd is worth nothing if the offloading system can only evacuate 20,000 bpd on an average-weather year.

This post covers the storage-and-offloading options that pair with a non-storing production unit, how the system is sized, and the marine and custody constraints that decide whether it works.

The Split-Function Architecture

The defining choice is whether to combine production and storage (FPSO) or split them. A MOPU development splits them:

• Production unit (MOPU / fixed platform) — processes the well stream to export spec.
• Storage unit (FSO) — a Floating Storage and Offloading vessel: a tanker or converted hull that holds the stabilised crude. Like an FPSO but without the process plant — storage and offloading only.
• Shuttle tanker — periodically comes alongside and lifts a cargo to market.

Splitting functions trades the integral simplicity of an FPSO for flexibility: the FSO can be a cheaper converted hull, the units can be leased separately, and the storage can be sized and redeployed independently. The cost is two marine assets to moor, two sets of marine systems, and a crude-transfer line between them.

Offloading Configurations

How the stored crude reaches the shuttle tanker is the heart of the system. The mainstream configurations:

The dominant driver is metocean. In open, exposed waters the tanker must be free to weathervane — to swing into the prevailing wind, wave, and current — which favours tandem or single-point mooring. In sheltered waters, side-by-side is simpler and faster.

Sizing the Storage

Storage volume is set by the gap between continuous production and intermittent offloading. The logic:

Storage required ≈ Production rate × Cycle time × Weather-downtime factor + working/dead volume

The drivers:

• Shuttle tanker parcel size. Crude is lifted in economic parcels — a tanker is not sent half-empty. The storage must hold at least one full parcel plus the production that accumulates while the tanker is in transit and being loaded.
• Offloading frequency. How often a tanker can be scheduled — a function of parcel size, production rate, and tanker availability.
• Weather downtime. Offloading cannot proceed above a limiting sea state. In a rough season, days can pass with no offloading window — the storage must absorb that production or the facility must shut in. This weather-downtime factor is the most commonly underestimated input.
• Working margin. Dead-bottom volume, slop, and a buffer against schedule slip.

A common rule of thumb is storage sized for 5–10 days of plateau production, tuned to the local weather statistics and tanker logistics. Undersize it and the production facility shuts in every time the weather closes the offloading window — the storage tank becomes the field's choke.

Crude-on-Water Specification

Crude that will sit in a storage tank and be loaded onto a tanker carries specifications that reach back into the production process:

• Vapour pressure (RVP/TVP). The stored crude must have a true vapour pressure below atmospheric at storage temperature, or the tank breathes and vents hydrocarbons on every thermal cycle and during loading. This is why the production unit must stabilise the crude before it reaches storage — see our piece on crude stabilisation and RVP/TVP control.
• H₂S. Sour crude in a confined tank is both a toxicity and a corrosion problem; the tank vapour space and loading operations are governed by it. Sweetening or vapour management may be required.
• BS&W and salt. Basic sediment and water, and salt content, are cargo-quality specs — off-spec crude is rejected or discounted at the refinery gate.
• Pour point / wax. A waxy crude that gels in an unheated tank or transfer line is unliftable. Storage and transfer lines may need heating.

The offloading system does not just move crude — it imposes a quality discipline on everything upstream of it.

Custody Transfer and Allocation

Offloading is a custody-transfer event — ownership and value change hands. That brings fiscal metering and measurement obligations:

• Tank gauging on the FSO (level, temperature, density) establishes the volume and quality of each parcel.
• Fiscal metering at the offloading point, or a calibrated tank-gauging measurement, quantifies the cargo for sale and royalty.
• Allocation back to individual wells or partners, where the field has multiple stakeholders.
• Loading documentation — bill of lading, certificates of quality and quantity — for the marine cargo.

Getting the measurement architecture wrong is expensive in a way that does not show up until the first cargo is disputed.

Marine and Safety Constraints

The offloading operation is the most marine-intensive activity on a non-FPSO development, and it concentrates risk:

• Mooring loads and weathervaning — the FSO and connected tanker must hold station and swing safely under the design metocean; mooring failure during a connected transfer is a major accident scenario.
• Floating-hose management — the transfer hose between FSO and tandem tanker is a frequent leak and failure point; condition monitoring and handling procedures matter.
• Emergency disconnect — connected transfers need a quick-disconnect / emergency-release system so the tanker can break away in a sudden weather or station-keeping event without rupturing the line.
• Green water and collision — two large hulls in proximity in a seaway carry collision and green-water risk; the limiting sea state for connection and transfer is set by these.
• Vapour and inert gas — loading displaces tank vapour; the tanker's inert-gas system and any vapour recovery govern the flammability and emissions of the transfer.

Worked Example — MOPU + FSO in Moderate Metocean

Scenario: a jack-up MOPU producing 25,000 bpd of stabilised crude, no export pipeline, moderate open-water metocean with a notable monsoon season. Shuttle tankers of ~600,000 bbl parcel size are available.

Cycle: at 25,000 bpd, a 600,000 bbl parcel accumulates in 24 days — so offloadings are roughly monthly, comfortably within tanker scheduling.

Storage sizing: the binding constraint is not parcel accumulation but weather downtime. If the monsoon can close the offloading window for up to 7 consecutive days, the storage must absorb 7 × 25,000 = 175,000 bbl on top of working volume and the buffer against tanker-arrival slip. A storage capacity around 400,000–500,000 bbl (a converted Aframax-class FSO) gives a workable margin — roughly 16–20 days of production — without shutting in the MOPU during typical weather closures.

Offloading: open-water site → tandem offloading via floating hose, with emergency-release coupling, limiting sea state defined for connection and transfer. The MOPU stabilises the crude to a storage-safe vapour pressure before it is pumped to the FSO.

The feedback to production: if a cheaper, smaller FSO were chosen, the MOPU would shut in during every extended monsoon closure — the storage tank, not the reservoir or the process, would cap the field's annual output. The storage size is a production decision dressed as a marine one.

Common Pitfalls

• Sizing storage on average weather. The binding case is the worst plausible offloading-window closure, not the mean. Undersized storage turns weather into deferred (or lost) production.
• Treating offloading availability as 100%. Every limiting sea state is downtime. The weather-downtime factor belongs in the storage sizing and the production forecast.
• Forgetting that storage imposes a crude spec. Unstabilised or sour crude in a tank vents, corrodes, and may be unliftable. The offloading system reaches back into the process design.
• Underspecifying custody measurement. The first disputed cargo reveals the gaps. Get tank gauging, fiscal metering, and allocation defined early.
• Ignoring emergency disconnect. A connected transfer with no quick-release is a major-accident waiting for the wrong weather.
• Decoupling the FSO decision from the MOPU. The two are one system. Choosing them separately, on separate budgets, produces a mismatch that the weather then exposes.

Conclusion

For a development without an export pipeline, storage and offloading is not a downstream utility — it is a co-equal part of the production system, and frequently the part that sets the achievable throughput. The FSO holds the gap between continuous production and intermittent lifting; the offloading configuration is chosen by the metocean; the storage volume is set by the worst offloading-window closure, not the average; and the whole system imposes a stabilisation and measurement discipline back onto the process plant.

Size it on the bad-weather case, pair the FSO decision tightly with the production unit, and design the marine transfer for the day the weather turns while the tanker is still connected. Done well, the offloading system is invisible. Done poorly, it is the choke the reservoir never sees.