An offshore-certified container is not automatically suitable for a hazardous area. Offshore container certification, hazardous-area protection and fire resistance address different risks. A buyer must verify the scope of each approval against the intended location, equipment and operating conditions.


For example, a container may have evidence supporting offshore lifting while its internal electrical installation has no assessed protection for an explosive atmosphere. The lifting evidence remains useful, but it does not answer the hazardous-area question.


What does offshore container certification establish?

DNV-ST-E271, commonly referred to as DNV 2.7-1, addresses offshore containers and their lifting sets, including design, manufacture, testing and inspection. Read the actual certificate and associated documentation to identify the unit and approved scope.


A statement that a unit is “designed to” a standard is different from a certificate issued for the applicable unit or design. Check the issuer, identification, limitations and inspection records. Do not infer certification from a logo, a drawing note or the appearance of the lifting frame.


Structural and handling evidence should be reviewed alongside the requirements for the module's installed function.


What information defines hazardous-area suitability?

Start with the site's hazardous-area classification and intended application. Provide the zone, relevant gas or dust hazards, required equipment protection level or category, temperature requirements and ambient conditions.


DNV's IECEx certification guidance explains the relationship between equipment protection levels or ATEX categories and suitable zones. The applicable regulatory and acceptance route also depends on the project location.


“Zone 2” alone is an incomplete equipment specification. The proposal must also address the relevant substance group, temperature limitations, installation conditions and the protection method selected for the equipment or room.


Tell the supplier whether the process introduces a flammable substance inside the container. An external hazardous atmosphere and an internal release create different design questions.


How can pressurisation protect equipment inside a container?

Room pressurisation can form part of an engineered protection strategy by limiting ingress of the surrounding hazardous atmosphere. Its suitability depends on the room arrangement, protective air supply, monitoring and safety actions.


IEC 60079-13 addresses rooms protected by pressurisation and artificial ventilation within its defined scope. The project should identify the applicable edition and any local adoption or additional requirements.


Useful procurement questions include where protective air is drawn from, how pressure is monitored, whether purging is required and what happens when protection is lost. The answers belong in the approved control philosophy and cause-and-effect documentation.


A fan or a positive-pressure reading alone does not demonstrate a complete protection system. Detection, alarms, interlocks, shutdown actions and any equipment that must remain energised need to be considered together.


Does an A60 fire rating mean explosion protection?

No. A60 concerns fire resistance under the applicable marine fire-test framework. It does not, by itself, establish suitability for an explosive atmosphere or resistance to blast loading.


The IMO 2010 FTP Code provides the relevant marine fire-test framework. Evidence must match the construction and installation being supplied, including applicable doors, windows, ducts, penetrations and joints.


Avoid treating separate labels as interchangeable: offshore handling, fire resistance, hazardous-area protection and any specified blast resistance each need an appropriate design basis and evidence.


Which documents should a buyer request?

Ask for a project-specific documentation schedule before order placement. Depending on scope, it should identify:

  • Container and lifting-set certification and identification.
  • Hazardous-area design basis and applicable certification or conformity documents.
  • Equipment schedule with protection markings and certificate references.
  • Conditions or limitations attached to certificates.
  • Pressurisation, ventilation, detection and shutdown documentation.
  • Fire-resistance evidence for the specified assemblies.
  • Factory test plan, installation instructions and site inspection requirements.

Certificates for individual components do not establish acceptance of the complete installed module. Ask who assesses the assembled system and who verifies its connection to the host facility.


Frequently asked questions

Can a container with offshore lifting certification be used in Zone 1?

Only if the complete proposed arrangement also satisfies the applicable Zone 1 requirements and project approval conditions. Lifting certification alone is insufficient.


Is an ATEX or IECEx certificate enough for every project?

Check its scope, conditions, equipment identity and acceptance under the applicable local rules. A component certificate does not replace installation assessment.


Does every electrical item inside a pressurised room need the same Ex protection?

The approved protection concept determines equipment selection and permitted operating conditions. Items that remain energised when room protection is lost require specific consideration.


Discuss Your Hazardous Area Container with TLS

TLS pressurised container solutions support project-specific offshore and hazardous-area applications. Send the intended function, area classification, equipment list, host interfaces and approval requirements to sales@tls-containers.com so the proposed configuration and documentation scope can be reviewed together.

To specify a containerised data center, provide the IT load, rack layout, cooling requirements, power architecture, site conditions and required supply scope. The quotation should also define external connections, testing and responsibility for installing and commissioning customer-supplied equipment.


Container length and rack count are useful starting points, but they cannot establish the electrical capacity, cooling duty or operational resilience the facility needs.


Start with the workload and rack power

Describe whether the project supports edge computing, enterprise servers, AI inference, training or another workload. Provide rack dimensions, equipment weights, expected operating power and maximum design power. Identify any racks with unusually high demand.


For illustration, ten racks at a design load of 5 kW each represent 50 kW of IT load; ten at 30 kW each represent 300 kW. These are hypothetical planning examples, not TLS product ratings. The same rack count can therefore imply very different infrastructure.


Distinguish IT power from total facility power. Cooling, UPS losses, lighting and other support loads also need to be included when sizing the site supply. State the initial deployment and planned future capacity separately.


Define the cooling interfaces

Provide the server manufacturers' environmental and cooling requirements. For air-cooled equipment, identify airflow direction, inlet conditions and the proposed arrangement for controlling recirculation. For liquid-cooled equipment, identify the required fluid conditions and connection points.


ASHRAE's liquid cooling white paper explains the interfaces between IT cooling and facility heat removal. A liquid-cooled rack still needs a defined path for its heat to leave the facility.


For the enquiry, request agreement on supply and return temperatures, flow, pressure, fluid quality, cooling distribution units and external heat-rejection equipment where applicable. Establish whether part of the IT heat remains in the room and needs air cooling.


Define which party supplies each part of that cooling chain. “Liquid cooling included” is too broad to describe an installation boundary.


State the power and resilience requirements

Provide available voltage, frequency, phases, earthing arrangement and the location of the incoming supply. Identify whether transformers, switchgear, UPS equipment, batteries, rack distribution and backup generation belong in the container supplier's scope.


Describe the operational requirement in practical terms: how long must the IT load continue during a supply interruption, and which maintenance activities must be possible while it operates?


If the specification calls for N+1 capacity, state which systems are covered and at what design load. If dual power paths are required, describe their boundaries and how they connect to the IT equipment. A redundancy label without an agreed architecture leaves room for different quotations.


Explain the site and installation constraints

Provide the project location, outdoor design conditions, altitude, corrosion exposure and any wind, seismic, noise or access restrictions relevant to the design.


The layout needs to show more than rack positions. Include electrical and cooling service areas, maintenance access, equipment replacement routes, cable entries and escape arrangements. Confirm the floor loading and transport restraint requirements for equipment shipped inside the module.


For remote sites, explain the availability of maintenance personnel, spare parts and reliable utilities. These inputs help determine what can be supported in operation rather than only at factory testing.


Make the supply boundary explicit

TLS containerised data center solutions include enclosure and integrated-system approaches. The selected offer should identify the equipment and services included for the particular project.


Ask the proposal to distinguish enclosure works, electrical systems, cooling, fire detection or suppression, monitoring, racks, servers, network equipment and software configuration. State who supplies, installs, connects and tests each item.


For customer-supplied equipment, agree when dimensions, weights, drawings and interface data must be available. Late equipment changes can affect the rack arrangement, penetrations, cooling distribution and electrical design.


Agree how performance will be demonstrated

Before ordering, define factory tests and the tests that remain for the final site. State whether the factory demonstration uses actual IT equipment, load banks, simulated signals or a combination, and record the limitations of each method.


As a procurement recommendation, specify the intended electrical loading, cooling demonstration, alarm checks and relevant failure-response scenarios. Identify which external systems must be available for site acceptance and who will conduct the tests.


Energy-efficiency targets also need measurement boundaries, load conditions and environmental assumptions. A generic efficiency figure cannot establish performance at every site or operating load.


Frequently asked questions

Can I request a quotation before choosing the servers?

Yes, for preliminary planning. Provide an estimated load range and mark unresolved equipment details. A firm design needs confirmed dimensions, weights, electrical demand and cooling interfaces.


Does a containerised data center include servers and networking?

Only where the quotation expressly includes them. An enclosure or infrastructure package may leave IT equipment and its configuration to the customer or integrator.


Can capacity be expanded later?

Expansion should be designed into the power, cooling, controls, connections and site arrangement. Space for additional racks alone does not establish spare infrastructure capacity.


Send TLS a Clear Data Center Enquiry

Send your intended workload, rack schedule, power and cooling requirements, site conditions and preferred supply scope to sales@tls-containers.com. Include available layouts and equipment data so TLS can review a container arrangement and the interfaces needed for the deployment.


TLS Energy provides DSX POD enclosures with an integrated delivery approach: supply the enclosure, install the racks, connect the internal systems, flush and pressure-test the cooling loop, then power on and test the assembled unit before shipment. This sequence brings assembly and verification into the factory, helping customers receive a coordinated package with clearly defined interfaces. For projects involving liquid cooling and interconnected racks, the value lies in checking how the components work together before the enclosure reaches its destination.

A DSX POD enclosure provides the physical structure around the equipment and its supporting infrastructure. The enclosure design must account for equipment placement, service access, cable routing and cooling connections. These requirements influence each other. Rack positions affect pipe routes, while access requirements influence the location of doors and internal clearances. Addressing these relationships during enclosure integration helps avoid installation conflicts later. TLS Energy’s delivery scope should therefore be defined around the complete assembly and the customer’s agreed project requirements.

Rack installation establishes the internal arrangement of the DSX POD enclosure. Racks need suitable mounting positions and secure attachment, with sufficient space for connections and maintenance. The layout should also accommodate the equipment that will occupy each rack. Dimensions, loading requirements and access arrangements must be confirmed against the project design. Installing racks at the factory allows the enclosure and rack arrangement to be checked together, giving the integration team an opportunity to resolve physical mismatches before dispatch.

Connecting the racks turns the enclosure into an integrated assembly. Depending on the agreed scope, this work can include electrical distribution, grounding, communications, control wiring and cooling connections. Each connection should follow approved drawings and component requirements. Clear identification of cables, pipes and connection points supports inspection and later maintenance. NVIDIA describes factory integration as a central feature of the DSX POD approach, moving cabling, wiring, piping and functional validation into the manufacturing stage. NVIDIA DSX POD overview

The cooling loop requires particular attention because installation quality affects fluid circulation and equipment cooling. Pipework, manifolds, valves and rack connections must form a circuit that matches the approved design. Connections also need to remain accessible for inspection and service. Before commissioning begins, the integration team should confirm component compatibility and the boundaries of the supplied cooling system. Establishing those boundaries clarifies which cooling functions belong inside the enclosure and which depend on infrastructure provided at the installation site.

Flushing the cooling loop prepares the assembled circuit for operation. Fabrication and installation can leave particles or other contamination inside pipework. A controlled flushing procedure helps remove this material before normal circulation begins. The procedure should follow the requirements of the installed components and the specified coolant system. Cleanliness acceptance criteria, flushing arrangements and fluid handling need to be agreed for the project. Completing this work at the factory gives the team access to the assembled loop while corrective work remains practical.

Pressure testing checks the cooling loop’s integrity before the unit is switched on. The test procedure must specify a suitable medium, pressure, duration and acceptance criteria based on the system design and component limits. Inspection focuses on joints, fittings and other potential leakage points. Any defect identified during testing requires correction and appropriate verification before the assembly proceeds. Flushing and pressure testing serve different purposes: flushing addresses internal cleanliness, while pressure testing checks whether the circuit meets its specified integrity requirements.

After the cooling loop passes the required checks, the assembled unit can proceed to controlled startup and functional testing. Switching on provides an opportunity to verify the operation of the equipment included in TLS Energy’s contracted scope. The test plan should define the required checks, operating conditions and acceptance criteria. Where applicable, these checks may cover controls, sensors, alarms and cooling circulation. The extent of operational testing depends on the installed equipment and the utilities available at the factory test location.

Factory testing provides useful evidence for shipment acceptance and subsequent commissioning. Test records should identify the inspected assembly, describe the procedures performed and document results against agreed criteria. Outstanding items need clear ownership and resolution requirements. Customers should distinguish between testing the enclosure’s integrated infrastructure and validating a complete computing workload. The purchase specification should state which equipment is installed, which functions are demonstrated and which activities remain for site commissioning. This clarity helps align delivery expectations with the actual supplied package.

For customers considering TLS Energy DSX POD enclosures, procurement discussions should begin with the required delivery boundary. Confirm the enclosure configuration, rack arrangement, internal connections, cooling loop scope and factory acceptance requirements before manufacturing starts. Site teams can then prepare the external services and receiving arrangements around those interfaces. An enclosure that has been assembled, connected, flushed, pressure-tested and powered on under an agreed test plan gives the receiving team a documented starting point for installation and commissioning at the destination.