Offshore containers operate under multiple overlapping standards, and the confusion costs time. Projects get held up in certification because the specification referenced one standard while the contract required another. Engineers spend days reconciling conflicting requirements that a clear understanding of the offshore container standards landscape would have avoided from the start.
This article cuts through the noise: where these standards came from, what each one actually covers, which applies in which jurisdiction, and how to write a specification that satisfies the applicable requirements without over-engineering.
Why Three Standards Exist for the Same Equipment
The offshore container standards that matter today emerged from three different institutional tracks, not from a coordinated effort to standardise the industry.
DNV 2.7-1 originated with Det Norske Veritas (now DNV) as a classification society standard for offshore containers used in the North Sea. Its roots are in the Norwegian Continental Shelf regulatory framework, and it became the de facto standard across the North Sea through operator adoption rather than legislation.
EN 12079 arrived through the European Committee for Standardization (CEN) and is the harmonised European standard for offshore containers. It was developed to provide a European alternative that could be used for CE marking under relevant EU directives — a requirement that DNV 2.7-1 alone cannot satisfy.
ISO 10855 is the international counterpart, developed under the International Organization for Standardization to provide a globally applicable standard aligned with EN 12079. The two documents are closely harmonised, though ISO 10855 is structured differently and does not carry the CE marking relationship that makes EN 12079 mandatory in EU jurisdictions.
The practical result is that these offshore container standards coexist, not because the industry chose complexity, but because they grew from different regulatory systems with different mandates. Most projects end up needing to satisfy more than one simultaneously, not by accident, but by design.
What Each Standard Actually Covers
All three standards address the design, manufacture, and testing of offshore containers for use in the petroleum and natural gas industries. The core structural requirements are broadly similar — DNV 2.7-1, EN 12079, and ISO 10855 all require proof load testing, design verification, material traceability, and documentation packages. The differences lie in how those requirements are expressed, what gets prioritised, and what each standard assumes about the operating environment.
DNV 2.7-1 tends to be more prescriptive about certain structural details and lifting arrangements, reflecting its origins in North Sea classification practice. EN 12079 and ISO 10855 are written more around performance criteria and reference external standards for specific aspects of structural design.
For practical purposes, if an offshore container is designed and certified to DNV 2.7-1 by a recognised certification body, it will typically satisfy the structural intent of EN 12079. But satisfying the intent is not the same as satisfying the contract. If the contract requires EN 12079, you need EN 12079 — a DNV 2.7-1 certificate alone will not discharge that obligation.
Which Standard Applies to Your Project
Jurisdiction and client requirements determine which offshore container standard you need, and they do not always point in the same direction.
For the North Sea, DNV 2.7-1 is effectively mandatory on Norwegian and UK installations. The Norwegian Petroleum Safety Authority and the UK Health and Safety Executive both reference DNV 2.7-1 in their guidance. You may also be asked for EN 12079, particularly if the vessel is EU-flagged or the project involves EU-based procurement.
For EU-flagged vessels or EU installations, EN 12079 is required for CE marking purposes. This is not optional — it is a regulatory requirement for placing the equipment into service within the EU.
In the US Gulf of Mexico, no single standard is federally mandated. DNV 2.7-1 is widely accepted and often specified by operators, but projects should confirm with the specific operator what they will accept.
In Angola, Brazil, Kazakhstan, and other markets where international operators run projects, the requirement is typically operator-driven. Major operators like TotalEnergies, Equinor, or Petrobras maintain approved vendor lists and specify offshore container certification requirements in their internal standards. The certification body — DNV, Lloyd’s Register, Bureau Veritas — is also often specified.
The certification body itself can be a deciding factor. DNV will certify to DNV 2.7-1. Lloyd’s Register and Bureau Veritas will certify to EN 12079 and DNV 2.7-1. Know which body your project requires before you start engineering.
What This Means for Your Engineering Specification
The most common specification error is referencing a single offshore container standard when the project actually requires compliance with two. A specification written only to DNV 2.7-1 may satisfy an operator’s classification requirement but fail a procurement contract that specifies EN 12079 for CE marking purposes.
The solution is straightforward: identify all applicable standards at the specification stage. If the offshore container will be used on a UK installation, fabricated in an EU yard, and delivered to a vessel flagged in an EU member state, you may need to demonstrate compliance with DNV 2.7-1, EN 12079, and whatever operator-specific standard applies. Write the specification to address all of them explicitly.
Avoid the temptation to specify the highest common denominator as a workaround. Over-specifying is not the same as specifying correctly — it drives cost and can create certification difficulties when the testing or documentation requirements of different standards conflict in their specifics.
Engaging an offshore container engineering firm early to clarify the certification path is not a luxury. It is how you avoid the situation where a container arrives at the certification body and the design submission package is missing half the required documentation because the specification never called for it.
Before you finalise your specification, talk to us about which standard actually applies to your project and jurisdiction. Getting this wrong at specification stage causes delays and cost overruns at certification that a short conversation upfront would have prevented.
Share your project requirements below. We’ll review your specifications and respond with a detailed engineering proposal.