Logística Marítima Offshore Angola: Base de Apoio

# Offshore Marine Logistics and Supply Bases in Angola: From the Cargo Manifest to the Container Nobody Can Find

TL;DR: Angolan offshore logistics runs through three real supply bases — SONILS in Luanda, the Kwanda Logistics Base in Soyo, and the Malongo terminal in Cabinda — and every handoff between warehouse, cargo manifest, vessel and offshore unit is a point where a container stops showing up in the system, even though it is still inventory with a value and an owner.

The real geography: three bases, one shared problem

Anyone running offshore operations in Angola works, in practice, with three logistics support points that each have a different profile.

In Luanda, SONILS — Sonangol Integrated Logistics Services has run an onshore supply base for the sector since 1995 (an integrated logistics centre in Boavista). SONILS describes itself as providing logistics support to more than 60% of the country's daily oil production, serving more than 80 clients across oil majors, national and international oil companies, and service companies (SONILS). It is the dominant supply base for the blocks off Luanda and for the bulk of materials, crew and heavy-equipment traffic.

In Soyo, at the mouth of the Congo River, the Kwanda Logistics Base sits on Kwanda Island: built in 1983 as a base for oil-industry service companies, it is today under concession to Kwanda Lda and, according to the port authority, serves around 50 companies (Port of Soyo). The Angola LNG plant sits on a 240-hectare site on the same island (Angola LNG). Soyo has its own profile: part of the traffic is gas and condensate, part is conventional platform logistics.

In Cabinda, the Malongo terminal, about 17 km north of Cabinda city, is operated by Cabinda Gulf Oil Company (CABGOC), a Chevron subsidiary, and exports Block 0 crude (Cabinda and Nemba grades) through single-buoy moorings (SBMs), with oil arriving from the onshore tank farm via submarine pipeline; LPG leaves by ship-to-ship transfer from floating storage units ( Wadmar Maritime). Malongo functions as base and terminal at once, historically tied to Block 0 operations and, more recently, to projects such as South N'Dola, which produced first oil on 25 December 2025, sending its crude to the Malongo terminal and associated gas to Angola LNG (Chevron Angola).

Three bases, three geographies — but the same operational cycle: material leaves an onshore warehouse, is bundled into a cargo manifest, boards a supply vessel, sails to an FPSO, a fixed platform or a drilling unit, is offloaded — and, often, part of it returns to base weeks or months later. Somewhere in that cycle, the system that is supposed to know where every item is, at every moment, is usually the first thing to lose the trail.

What an offshore cargo manifest actually is

A cargo manifest is not an ordinary delivery note. In an offshore operation, it has to identify every Cargo Carrying Unit (CCU) — every container, basket, gas bottle or skid — by its certification number, gross weight, declared contents (including dangerous goods under the IMDG Code, where applicable) and exact destination: which platform, which well, which cost centre.

What sets this apart from onshore logistics is that every CCU has to be, itself, a trackable, certified asset. The applicable international standard — the ISO 10855 series, "Offshore containers and associated lifting sets" — sets out design, manufacturing and periodic-inspection requirements for these containers, with Part 3 defining the intervals and criteria for mandatory inspection throughout the equipment's operating life (ISO 10855-3:2018). Containers certified under the earlier DNV 2.7-1 or EN 12079 standards remain valid by equivalence (ISO/TC 67), but they remain subject to periodic inspection — meaning a container has a certification expiry date as real as that of a fire extinguisher.

IMCA (International Marine Contractors Association), the reference body for the offshore marine sector, publishes specific guidance on loading and securing cargo and containers, insisting on pre-planning of loading to enable safe unloading at destination and warning against the common practice of leaving loose items on top of a CCU during transport (IMCA — Loading and securing of cargo).

That means a properly built offshore cargo manifest carries three layers of information at once: marine safety (what it is, how much it weighs, whether it is dangerous), certification compliance (is the container fit to sail) and accounting ownership (who it belongs to, against which purchase order or material requisition it was dispatched, and which cost centre should be charged). Most systems in use handle the first layer well and leave the other two to paper on the side.

1. Warehouse to quay

Material leaves the warehouse as a picking line against a requisition — often one that has already gone through quotation, approval and purchase order, as we described in detail when covering procurement automation in Angola. Up to this point, the warehouse management system generally knows exactly what left. The problem starts when that picking line is bundled, alongside dozens of others, into a single cargo manifest prepared for a specific vessel. If the manifest is assembled on a spreadsheet separate from the ERP — which still happens often at Angolan supply bases — the link between "this item left warehouse X" and "this item is on manifest Y" starts depending on manual re-entry.

2. Quay to vessel

Physical loading rarely matches the planned manifest perfectly: one CCU stays ashore due to excess weight, another is swapped out for lack of deck space, a gas bottle is replaced with a different serial number because the original failed inspection. These last-minute changes happen at the quay, under the pressure of a tide window and offshore weather, and are not always reported back to the originating system. The result is an "official" manifest describing what was supposed to load, not what actually did.

3. Vessel to the offshore unit

On arrival at the platform or FPSO, discharge is confirmed by the offshore crew — often on paper, over radio, or on a shift log — before that confirmation is keyed back into the onshore system days later, whenever a communication window opens. In that interval, the item is already physically installed, consumed, or stored in an onboard container, but the central system still shows it "in transit" or, worse, still "in warehouse." It is the same kind of lag we discussed when covering offshore MRO and maintenance inventory: the part physically exists, but the system does not know it.

4. The return trip — where most gets lost

The most neglected point is backload: empty containers, equipment sent for repair, used gas bottles, or surplus material returning to base weeks later, often on a different vessel than the one that carried it out, and sometimes diverted to a different base for operational convenience (a container that left Luanda can come back via Soyo). Without a single reference that survives the round trip — a manifest number, a CCU code, a work order — the system simply loses that item until someone finds it physically in a yard and re-enters it as "new," duplicating inventory that already existed.

The regulatory layer on top of logistics: local content and certification

In Angola, this chain is not purely operational — it is also subject to oversight. Presidential Decree No. 271/20, of 20 October 2020, established the new legal regime for local content in the oil sector, giving ANPG — the National Agency for Petroleum, Gas and Biofuels — as National Concessionaire, the job of drawing up the lists of goods and services under the exclusivity and preference regimes, updated annually and published after ministerial approval (Article 18), as well as registering and certifying suppliers; oversight of local-content management falls to the Ministry of Mineral Resources, Petroleum and Gas (Article 22). Violations carry fines between the equivalent of USD 50,000 and USD 300,000 (Article 26, with caps of USD 300,000, 200,000 or 150,000 depending on the type of violation, Article 27), combinable with ancillary penalties such as a one-to-two-year activity ban, suspension of the operating permit, or a bar on signing new contracts (Article 28) (Presidential Decree No. 271/20 — Angolex; ANPG — Local Content).

That means marine transport, supply-base management and cargo-handling services contracted by an operator fall within the scope of local content themselves — the supply vessel provider, just as much as the pipe supplier, has to be certified and reported. We covered how to turn that requirement into a system workflow in qualifying suppliers under local content. On the marine-logistics side, the practical implication is that the cargo manifest stops being purely a safety document and becomes a compliance record too: which transport provider was used, whether it is ANPG-certified, and whether the volume of cargo moved by national providers is being correctly counted for local-content reporting.

What a well-designed system has to do

Fixing this is not a matter of team discipline — it is a matter of data model. The underlying problem is that most systems treat "warehouse," "manifest" and "offshore unit" as three separate modules connected by manual re-entry, instead of treating every CCU and every material line as a single entity whose state changes location but never changes identity.

An energy-sector ERP designed properly for this cycle needs:

A unique identifier per CCU, linked to its ISO 10855/DNV 2.7-1 certificate and its next inspection date, that survives every round trip — and that fires an automatic alert when certification is about to expire.
State tracking, not just location tracking — an item should be able to sit in an explicit "confirmed on board, awaiting discharge" state, distinct from "in warehouse" or "installed," so inventory never sits in no-man's-land between two systems.
A direct link between the material requisition, the purchase order, the manifest and the offshore receipt confirmation, so an audit can follow a specific bolt from quotation to supplier to installation on a well, without gaps in intermediate spreadsheets.
Offline capture of offshore confirmation, because the satellite link on a platform is not always available at the moment cargo is discharged — a problem we covered in detail when discussing offline-first synchronization on FPSOs.
A transport-provider and supply-base field attached to every manifest, so the volume moved by certified Angolan logistics operators feeds directly into local-content reports, instead of being manually rebuilt every quarter.

None of these points is complex in isolation. What makes them hard is that they require designing the data model around the cargo's physical life cycle — warehouse, manifest, vessel, offshore unit, backload — rather than around the organizational modules of whoever manages each step. That design choice, more than any single feature, is what separates an off-the-shelf system from one built to fit the real Angolan operation, which is the kind of work we do in custom software for operators and service companies in the sector.

FAQ

Does a container certified under DNV 2.7-1 need recertification to comply with ISO 10855?

No. Containers and lifting sets certified under DNV 2.7-1 or EN 12079 are considered equivalent to ISO 10855, so existing certifications remain valid without recertification — but they remain subject to the periodic inspections required under ISO 10855-3 (ISO 10855-3:2018).

Is SONILS the only offshore supply base in Angola?

No. SONILS, in Luanda, has operated since 1995 and states that it supports more than 60% of the country's daily production, but Soyo has the Kwanda Logistics Base (tied to Angola LNG) and Cabinda has the Malongo terminal, operated by CABGOC/Chevron, each serving a different set of block geographies (SONILS; Port of Soyo).

Does a marine transport supplier fall within the scope of Angolan local content?

Yes. Presidential Decree 271/20 applies to suppliers of goods and services to the oil sector in general, not only to operators themselves, which includes supply vessel operators, supply-base managers and cargo-handling companies, subject to registration and certification by ANPG (Lexology).

Is it worth digitizing the cargo manifest if the offshore crew still confirms everything on paper?

The value is exactly in closing that gap: capturing discharge confirmation offline on the offshore crew's device and syncing it as soon as the satellite link comes back, instead of waiting days for manual onshore re-entry — which is what prevents the same item from showing up, at the same time, as "in transit" in the ERP and "installed" in physical reality.

Offshore Marine Logistics and Supply Bases in Angola: From the Cargo Manifest to the Container Nobody Can Find