Short Summary

A containerized data center should be specified as an operating system, not as a container filled with IT racks. Define the IT load and growth path, availability objective, power architecture, cooling concept, environmental conditions, network entry, fire strategy, physical security, transport route, installation interfaces, commissioning tests, and service model before asking for a quotation.

The Short Answer

Choose a containerized data center only after the project has defined what digital services must remain available, the load those services create, and the site conditions in which the package will operate. Racks, UPS units, cooling equipment and an enclosure are only parts of the solution. A workable package must also have a credible power and heat-rejection path, network resilience, controlled access, fire detection and response, transport and lifting arrangements, and enough room to maintain critical equipment safely.

The ISO/IEC 22237 series provides a useful framework for discussing data-center facilities and infrastructure. Part 1 addresses common concepts and a classification approach based on availability, security and energy efficiency. It does not replace the project-specific engineering needed for a remote, marine or offshore installation.

1. Start with the Service, Then the IT Load

Ask what the site will lose if the data center becomes unavailable. The answer may be production data, telecommunications, process visibility, safety support functions, local edge computing, video, access control or a mix of services. Separate life-safety and control-system requirements from general business IT; their availability, cyber-security and change-control requirements may differ.

Create a load schedule that identifies installed and expected IT power, rack density, power factor where relevant, diversity, peak processing periods, growth increments and the heat released by IT equipment. Include network equipment, storage, monitoring, lighting, controls and any local support loads. A room rated by floor area or a container selected by length tells the supplier very little about real cooling and electrical demand.

Define the initial configuration and the design horizon. A package that operates efficiently at 30 kW but is expected to reach 120 kW within two years should be designed around the expansion strategy. State whether the growth will be achieved by spare rack positions, modular UPS blocks, additional cooling capacity, an external plant or a second module.

2. State the Availability Objective in Operational Terms

Avoid requesting “Tier-like” or “high availability” without explaining what that means at the site. Describe the tolerable interruption, recovery time, maintenance conditions, utility reliability, fuel logistics and which single failures must be survived.

Define the power path from source to IT load. The scope may include utility or generator incomers, switchgear, transformer, UPS, batteries, distribution boards, rack PDUs, bypass arrangements, earthing, surge protection and monitoring. State the required ride-through time, generator-start sequence, load shedding, maintenance bypass philosophy and the behavior after a failed UPS module, battery string, cooling unit, breaker or controller.

Redundancy language such as N, N+1 or 2N only becomes useful when its boundary is clear. For example, redundant UPS capacity will not maintain service if both paths depend on one upstream breaker, one room-level control panel, one fuel-transfer system or one cable route. Ask the supplier to identify shared elements and maintenance constraints in the single-line diagram and failure-mode review.

3. Engineer Cooling and Heat Rejection for the Actual Site

Every kilowatt consumed by IT becomes heat that has to leave the module. The cooling system must be selected from the site design conditions, not an annual average weather value. Specify outdoor dry-bulb and humidity ranges, solar exposure, altitude, dust, salt, driven rain, wind, corrosive contaminants, water availability, permitted water treatment and any low-temperature or icing conditions.

For air-cooled systems, confirm the location of condensers or dry coolers, airflow paths, pressure drops, discharge recirculation, salt protection, noise, access and crane-removal route. For liquid or chilled-water systems, define the water-quality boundary, freeze protection, leak detection, pumps, pipe materials, isolation, external connections, drainage and who owns the central plant.

The desired IT inlet conditions, permitted temperature and humidity range, alarm thresholds, lead-lag control, failed-unit behavior and emergency ventilation should appear in the control narrative. If the data hall contains high-density racks, specify the intended rack layout, blanking panels, containment approach, cable routing and allowable airflow obstruction. Cooling redundancy cannot compensate for uncontrolled air bypass inside the module.

4. Treat Connectivity as a Physical and Operational Interface

Remote sites need a connectivity design that is as deliberate as the power design. Provide the carrier or satellite arrangement, bandwidth, latency expectations, network demarcation, fibre or copper entry points, route diversity, cable protection, grounding, surge protection, telecom-room interfaces and requirements for out-of-band management.

Two services from the same physical landing point or mast may not deliver meaningful resilience. Map the route from each external provider to the active network device and record common ducts, cabinets, penetrations, power supplies and environmental risks. Protect cable entries against water, rodents, fire and electromagnetic exposure as appropriate to the site.

Cyber security is not created by the container shell. Agree who owns network hardening, remote access, logging, patching, asset inventory, configuration backups and incident response. The module should provide controlled physical interfaces and environmental monitoring, while the wider system needs an operating model.

5. Define the Enclosure and Safety Boundaries

The enclosure should be selected around the installation and operating environment. Confirm structural support, floor loading, access doors, roof openings, cable and pipe penetrations, weather protection, corrosion system, insulation, vapor control, lighting, emergency lighting, drainage, noise and site-specific wind or seismic criteria where applicable.

Fire strategy must be agreed with the authority having jurisdiction, insurer, operator and relevant project standards. State the detection technologies, alarm interfaces, shutdown cause and effect, suppression approach if required, manual release or abort arrangements, emergency power, signage, evacuation, service access and post-event recovery plan. A suppression system inside the container is not a substitute for site-wide emergency coordination.

Specify access control, CCTV, intrusion alarms, key management and the interface to the site security system. Also plan human factors: safe maintenance clearances, lifting points for replacement equipment, emergency exits, safe isolation points, ergonomic rack access and a clear route for failed batteries, UPS modules and network equipment.

6. Plan Transport, Installation and Commissioning Before Fabrication

Determine whether the package must travel by road, sea, rail or air and define the transport configuration. Dimensions, mass, center of gravity, lifting points, forklift restrictions, sea fastening, shock limits, preservation, humidity control and removable external equipment must be known early. A custom data-center module is not automatically a freight container certified for international container transport merely because it has a container shape.

For an ISO series 1 freight-container transport basis, ISO 1496-1 covers specifications and testing for general-purpose containers, and the International Maritime Organization explains that the CSC addresses testing, approval, inspection and maintenance for most freight containers in international transport. Project-specific equipment modules can have a different certification boundary; clarify this rather than assuming a CSC plate approves the installed IT system or the final site installation.

Prepare a site-interface schedule covering foundations or deck support, anchoring, cable routes, network entries, power incomers, external cooling connections, drainage, access platforms, fire and gas signals, earthing, lightning protection and commissioning authority. Factory acceptance testing should prove the agreed package functions before shipment. Site acceptance testing should then confirm the interfaces and operating scenarios that could not be fully reproduced in the factory.

Information the Buyer Should Provide with the RFQ

• Site location, application, installation date and operating life
• Critical services, availability objective, recovery expectation and expansion plan
• Initial and final IT load, rack count, rack density and equipment heat load
• Electrical single-line diagram, supply quality, utility or generator arrangement, autonomy and earthing basis
• Ambient conditions, corrosion category, dust, salt, wind, solar load, altitude and water availability
• Cooling preference, external plant boundary, noise limit and water-treatment constraints
• Network providers, entry points, route-resilience requirements and remote-management approach
• Fire, gas, security, hazardous-area and emergency-system interfaces where applicable
• Transport route, lifting method, installation support, access restrictions and certification basis
• Required FAT, SAT, documentation, training, spares, warranty and service-response expectations

Procurement Takeaway

The right containerized data center is one whose service objectives, power, cooling, connectivity, safety and maintenance design remain credible after it reaches the actual site. TLS can configure containerized data center solutions around the project-defined electrical, mechanical and IT scope. Send the service description, load schedule, site conditions, interface drawings and testing requirements for a focused technical review before fabrication.

FAQ

Can a containerized data center be deployed outdoors?

Yes, if the enclosure, cooling and external interfaces are engineered for the local temperature, humidity, contamination, wind, rain, solar and corrosion conditions. Outdoor placement does not remove the need for foundations or supports, drainage, secure access, cable protection and service clearances.

Does N+1 power capacity guarantee service continuity?

No. It only describes a capacity relationship within a defined boundary. Review shared upstream distribution, control systems, cooling, network paths, fuel systems, cable routes and maintenance procedures to understand the real single points of failure.

Is a standard freight-container approval enough for a data-center module?

No. A transport approval or CSC plate applies to the stated container transport scope. It does not automatically approve installed IT equipment, electrical distribution, cooling, fire systems or the final installation.

What is the most important input for cooling design?

The design IT heat load and the site design conditions. Include the load growth profile, rack arrangement, permitted inlet conditions, outdoor temperature and humidity, contamination, available utilities and the location of external heat rejection equipment.

Further Reading

• ISO/IEC 22237-1:2021 — Data centre facilities and infrastructures

• ISO 1496-1:2013 — Series 1 freight containers: general-purpose containers

• IMO — International Convention for Safe Containers (CSC)

• TLS — Containerised solutions for energy data centers and offshore operations

Short Summary

An effective factory acceptance test (FAT) proves the agreed package before shipment: identity, construction, interfaces, functional performance, protective devices, alarms, documentation and outstanding actions. It does not replace site acceptance testing, transport inspection or project approvals. Start with a traceable FAT plan linked to the purchase order, approved drawings, risk controls and site operating scenarios.

The Short Answer

Plan the FAT before fabrication is complete and use it to verify the package the customer actually ordered. The test should identify the unit, approved documents and configuration; inspect workmanship; verify dimensions, interfaces and markings; test functional and protective systems; record results; and close or clearly classify every outstanding item before shipment. The FAT is strongest when it follows the project’s real operating scenarios rather than a generic checklist.

For containerized packages, the FAT boundary can include the enclosure, structural items, electrical distribution, HVAC, controls, fire and gas interfaces, equipment skids, doors, lifting provisions and documents. It must be agreed explicitly. A successful FAT does not automatically prove final installation, transport suitability, statutory approval or operation at the customer’s site.

1. Define the Acceptance Boundary and Evidence Before Testing

Begin with the contractual scope. Freeze the documents that establish what is being accepted: purchase order, technical specification, approved general arrangement, interface drawings, electrical single-line diagram, equipment datasheets, bill of materials, control narrative, inspection and test plan, inspection records and approved deviations.

Use the FAT plan to distinguish three conditions:

• Requirements that can be physically tested in the factory
• Requirements that can be inspected or verified by document review only
• Requirements that must be verified after transport or site installation

This prevents a common problem: attempting to declare a module “fully accepted” when external utility connections, host alarms, weather exposure, foundation support, communications and operating loads do not exist in the factory.

Every test should state the precondition, test method, expected result, record, witness requirement, acceptance criterion and action if it fails. Where a simulated signal or temporary test supply is used, mark it clearly so it is not mistaken for the final site condition.

2. Confirm the Physical Package Matches the Approved Design

Verify the equipment identity, serial numbers where applicable, dimensions, mass basis, center-of-gravity marking if required, door configuration, access openings, cable and pipe entries, external interfaces, labels, coating, internal fixtures, lighting, drainage and enclosure sealing. Compare these with the latest approved drawings, not superseded sketches.

Structural and handling features require special attention. Confirm the intended lifting points, rated markings, lifting-set scope, forklift restrictions, tie-down or sea-fastening points, transport configuration and any removable items. Do not assume that corner castings or an enclosure shape establish transport approval. For freight containers used in international transport, the CSC framework covers specific testing, approval, inspection and maintenance provisions; a custom equipment package can have a different approved handling and certification basis.

Check maintainability while access is available in the factory. Open doors and panels, remove designated covers where practical, and verify access to filters, batteries, pumps, valves, control panels, service points and replaceable components. A FAT is the cheapest time to identify a blocked maintenance route or an unsafe working position.

3. Test Systems Through Realistic Operating Scenarios

The strongest FAT follows the way the package will be used. Prepare operating cases such as energization, startup, normal operation, local and remote control, loss of normal supply, emergency stop, shutdown, restart, alarm response, maintenance isolation and recovery after a component fault.

For electrical systems, confirm supply characteristics, protective-device settings, phase identification, continuity, insulation testing as applicable, functional operation of breakers and interlocks, emergency stops, UPS or battery functions where included, lighting, sockets, earthing and alarm indications. Verify that drawings, terminal labels and field devices agree.

For HVAC and ventilation, test fan rotation, airflow indication where supplied, temperature control, dampers, alarms, heaters or cooling equipment, condensation management, door interlocks and any shutdown signal. Do not claim a site-temperature performance guarantee from a brief factory run unless the agreed test conditions reproduce that duty.

For controls and automation, test each input and output in the cause-and-effect matrix. Demonstrate local controls, remote commands, permissives, alarm priority, time delays, fail-safe states, communications and manual fallback. A well-recorded input/output check is more valuable than a demonstration that only shows the system starting once.

For fire, gas, leak or other protective systems, follow the agreed safety procedure and manufacturer instructions. Demonstrate detection, alarm, shutdown and interface signals only within safe and authorized test limits. Record any functions that require final-site testing because their release, suppression, alarm or emergency-system interface cannot be fully energized in the factory.

4. Inspect Workmanship, Documentation and Configuration Control

The FAT should inspect more than performance. Check weld and fabrication records where required, coating condition, corrosion protection, penetrations, cable management, gland installation, pipe supports, insulation, guards, signage, nameplates, warning labels, housekeeping and protection of sharp edges or hot surfaces.

Review the documentation pack before shipment. It may include approved drawings, data sheets, manuals, certificates, inspection reports, material records, electrical test results, software and parameter backups, calibration certificates, spare-parts lists, packing list, preservation instructions, transport instructions, lifting information, maintenance schedule and as-built deviations.

Configuration control is essential. Record the software and firmware versions, control parameters, setpoints, password-transfer process, installed device identities and any temporary test links that must be removed. Otherwise the unit that leaves the factory may not be the configuration that passed the FAT.

5. Manage Non-Conformities Without Hiding Risk

Use a punch-list process that identifies the item, requirement, impact, responsible party, corrective action, evidence required and target closure date. Classify items by their effect on safety, performance, documentation and shipment readiness.

Do not allow a list of minor-looking open points to obscure a serious interface or safety issue. Examples of shipment blockers can include an inoperative emergency stop, missing protective-device test evidence, unverified lifting arrangement, incorrect equipment configuration, a failed leak test, inaccessible maintenance isolation, or a fire-and-gas signal that has no agreed final verification route.

If the customer accepts an item for closure after shipment, record the exact limitation and the site test or inspection that will resolve it. The goal is transparency, not a perfect-looking report.

6. Link FAT to Transport and Site Acceptance Testing

Prepare the unit for shipment only after the FAT configuration is preserved. Record loose items, removed external equipment, transport braces, door locks, preservation, desiccants, fluid levels, battery isolation, protected interfaces, packing, lifting instructions and required arrival inspection.

Site acceptance testing (SAT) should take the FAT records as its starting point. It verifies damage-free arrival and the final interfaces: foundations or deck support, site power, earthing, utilities, external pipework, network communications, remote alarms, host fire and gas connections, environmental performance, noise and operator procedures.

The handover should explicitly state what the FAT proved, what SAT must prove, what remains open and who owns each action. That boundary protects both the buyer and supplier from using a factory test as evidence for an untested site condition.

Information the Buyer Should Provide with the RFQ

• Approved technical specification, drawings, interface list and applicable standards or client requirements
• Required FAT attendance, witness points, notice period, language, location and report format
• Required functional scenarios, performance limits, alarm philosophy and cause-and-effect matrix
• Electrical, HVAC, control, fire-and-gas, security and utility tests required at the factory
• Required inspection records, certificates, calibration evidence, software backups and as-built documents
• Transport configuration, lifting and preservation requirements and arrival-inspection expectations
• Site conditions and interfaces that must be transferred to SAT
• Punch-list classification, shipment-release authority and closure process

Procurement Takeaway

A FAT is a decision-quality record, not a showroom demonstration. It should prove that the manufactured package matches the agreed design and behaves correctly in the factory-testable operating scenarios, while making every site-dependent verification visible. TLS develops custom containerised solutions with structural, electrical, HVAC and controls interfaces coordinated around the project scope. Send the test requirements, drawings, cause-and-effect logic, witness plan and site-interface list to build a focused FAT and SAT sequence.

FAQ

What is the difference between FAT and SAT?

FAT verifies the package at the factory before shipment. SAT verifies the delivered package after installation and connection to the real site systems. FAT reduces site risk; SAT confirms the conditions that cannot be fully tested in the factory.

Should the customer attend the FAT?

Attendance depends on the project’s risk and contract. Even when the customer does not attend, the FAT plan, records, photographs where appropriate, deviations and signed report should provide traceable evidence. Critical witness points should be agreed before fabrication is complete.

Can a FAT prove transport or offshore suitability?

Only if the test scope specifically covers a defined handling or transport requirement and the relevant approval basis. A functional factory test alone does not prove a package is suitable for every road, marine or offshore lift or installation.

What should block shipment after a FAT?

Any unresolved issue that affects safety, required performance, legal or contractual compliance, transport readiness, protective functions or the ability to commission the package as agreed should be resolved or formally dispositioned by the authorized parties before shipment.

Further Reading

• IMO — International Convention for Safe Containers (CSC)

• ISO 1161:2016 — Freight-container corner and intermediate fittings

• ISO 10855-1:2024 — Offshore containers and associated lifting sets

• TLS — Factory Acceptance Test for a pressurised offshore container

Shipping a battery energy storage system (BESS) overseas requires more than arranging freight. Exporters must coordinate dangerous goods classification, battery safety, container integrity and carrier acceptance. For international sea transport, the IMDG Code 2024 Edition, incorporating Amendment 42-24, became mandatory on 1 January 2026. International Maritime Organization

Which UN number applies to BESS shipments?

Containerized lithium batteries installed in a cargo transport unit solely to supply external power generally fall under UN 3536, Class 9. Separately shipped lithium-ion batteries or batteries accompanying equipment may require UN 3480 or UN 3481. Classification depends on configuration, not simply the description “BESS container.” IMO

What does UN 38.3 require?

Lithium cells and batteries must satisfy applicable UN Manual of Tests and Criteria, subsection 38.3, requirements. Manufacturers and subsequent distributors must make the prescribed test summary available. Match it to the supplied battery model and review assembled battery provisions; a cell report alone does not automatically establish compliance for every battery assembly. PHMSA

The summary identifies the manufacturer, laboratory, tested product, report reference and test results. A Safety Data Sheet (SDS) does not replace the required test summary. Keep test reports accessible for additional technical review.

The summary must be available, but does not automatically need to accompany every shipment. Nevertheless, obtain the carrier’s document checklist early to satisfy its acceptance requirements. PHMSA

How must the system be prepared?

Special Provision 389 requires secure battery attachment, short-circuit prevention and protection against accidental operation or significant movement. Systems must prevent overcharge and overdischarge. Necessary firefighting or air-conditioning dangerous goods may remain properly secured; unrelated dangerous goods must not be added. IMO

Document a manufacturer-approved transport configuration before dispatch. Confirm electrical isolation, protective system status and state of charge with the carrier. Do not assume that air transport’s familiar 30% charge limit is a universal IMDG requirement for UN 3536. IMO

What maritime and structural rules apply?

UN 3536 has stowage Category D: on deck only on cargo ships, protected from heat sources and clear of living quarters. Apply the required Class 9 placards and UN number markings. IMO

Where the enclosure falls within the International Convention for Safe Containers, verify CSC approval and examination status. Confirm rated gross mass, lifting arrangements and securing design. For packed containers covered by SOLAS, provide verified gross mass before loading. Electrical safety certification cannot replace these checks. International Maritime Organization

For heavy systems, obtain written confirmation that terminal equipment, lifting arrangements and inland transportation can accommodate the actual unit weight and dimensions.

Which documents and approvals are needed?

Prepare an accurate dangerous goods transport document and the container/vehicle packing certificate where applicable. Coordinate the declaration with commercial shipping documents, battery identification and the physical shipment. The shipper’s declaration and packing certification have distinct responsibilities, even when combined on one form. GOV.UK

Obtain carrier dangerous goods approval before dispatch. Confirm destination and transshipment port acceptance, documentation deadlines and terminal dwell restrictions. Booking details must match the final declaration; changes can require renewed approval. Maintain accessible emergency contacts and share handling instructions with logistics partners. Maersk

Port policies also matter. Hapag-Lloyd’s London Gateway notice introduces additional charges from April 2026 when UN 3536 units remain uncollected beyond 24 hours after discharge. Such restrictions require coordinated customs clearance and collection planning. Hapag-Lloyd

Does shipping compliance authorize overseas installation?

No. Transport compliance and destination approval serve different purposes. UL 9540 addresses energy storage system safety, while UL 9540A evaluates thermal runaway fire propagation. Neither replaces dangerous goods transport requirements. Assess local installation, electrical and fire safety obligations separately. UL Solutions

Build transportation compliance into product design and procurement, rather than treating it as a final logistics task. Assign clear ownership for classification, documentation and release approval before the first shipment.