The global AI infrastructure boom is driving unprecedented investment in AI data centers (AIDC). Across Southeast Asia and other rapidly growing digital markets, developers are securing large power capacities—often 50MW, 100MW or more—to support next-generation GPU clusters.

But for a billion-dollar AI infrastructure project, one question is becoming increasingly important:

How quickly can invested capital begin generating cash flow?

Traditional data center development focuses heavily on construction cost, often measured in CAPEX per MW. For AI factories filled with expensive GPUs, however, construction cost alone does not determine investment performance.

Time-to-Revenue and Capital Efficiency can be equally important.

Consider a hypothetical 48MW AIDC project with 16,384 NVIDIA B300 GPUs. Instead of constructing the entire facility before starting operations, the project can be divided into 16 standardized 3MW modular AI Pods.

This changes not only how the data center is built, but also how capital is deployed and recovered.

What Does a 48MW AI Data Center Look Like?

For this model:

48MW = 16 × 3MW Modular AI Pods

Each 3MW Pod contains approximately:

• 128 eight-GPU AI servers
• 1,024 B300 GPUs
• Dedicated power infrastructure
• High-speed networking
• Liquid cooling infrastructure
• Monitoring and control systems

The complete 48MW AI factory therefore contains:

2,048 AI servers + 16,384 B300 GPUs

Assuming each eight-GPU server together with its associated high-speed networking infrastructure costs approximately $700,000, total server and networking investment reaches approximately $1.434 billion.

If modular AIDC infrastructure costs approximately $208 million, total project CAPEX reaches approximately $1.642 billion.

A conventional facility benefiting from larger-scale civil construction might reduce infrastructure CAPEX by approximately 5%, resulting in total investment of around $1.631 billion.

Therefore, conventional construction appears approximately $10.4 million cheaper.

But that comparison ignores one of the most valuable assets in an AI data center:

time.

Every Month of Earlier GPU Operation Has Financial Value

Assume GPU computing capacity is monetized at:

$4.80 per GPU-hour

with average utilization of:

85%

Once all 16,384 GPUs are operational, monthly revenue could reach approximately $48.1 million.

After electricity, cooling, bandwidth, maintenance and other operating expenses—with assumptions including a PUE of 1.15 and electricity price of $0.07/kWh—the project could potentially generate approximately $44.8 million in monthly NOI.

At this scale, bringing computing capacity online even one month earlier can represent tens of millions of dollars in potential cash flow.

That makes construction speed a financial variable rather than simply an engineering KPI.

Traditional AIDC: Build Everything Before Monetization

A conventional hyperscale data center typically follows a sequential development process:

Design → Civil Construction → MEP Installation → Testing → Commissioning → Server Installation → Commercial Operation

Suppose an aggressively managed 48MW project can be completed within 12 months.

During months 1–12, significant capital is continuously invested in buildings, electrical infrastructure, cooling systems, servers and networking equipment.

However, there may be little or no GPU revenue.

Only after the entire facility is ready does the complete 16,384-GPU cluster enter commercial operation.

The problem is therefore not necessarily that conventional construction is too expensive.

The problem is that a very large amount of capital can remain non-revenue-generating during construction.

Modular AIDC: Build One, Operate One, Monetize One

Modularized AIDC changes the deployment philosophy.

Instead of treating 48MW as one enormous facility, it can be treated as:

16 × standardized 3MW AI computing units.

Each Pod can potentially be independently manufactured, integrated, tested, delivered, commissioned and placed into operation.

For example, Pod 1 could enter construction in Month 1, followed by Pod 2 in Month 2 and Pod 3 in Month 3.

Once Pod 1 is commissioned, its 1,024 GPUs can begin generating computing revenue while later Pods remain under construction.

The investment model changes from:

Build everything → Commission everything → Start earning

to:

Build → Commission → Earn → Expand

This creates what can be described as a Rolling CAPEX Model.

Rolling CAPEX Can Reduce Peak Funding Requirements

This distinction is particularly important for investors.

The conventional project may require peak funding approaching the entire $1.631 billion CAPEX before meaningful operating cash flow begins.

Under the modular scenario described above, early Pods generate cash while subsequent Pods are still being deployed.

Based on the model assumptions, this could reduce peak external funding requirements by approximately $244 million, or nearly 15%.

This does not mean modular AIDC reduces total project CAPEX by $244 million.

Instead, it means investors may not need to have the entire project capital committed simultaneously.

For infrastructure funds, private equity investors, data center developers and AI cloud operators, this difference can be extremely important.

Higher CAPEX Can Still Produce Better Returns

Interestingly, modular construction can cost slightly more.

In our model:

MetricTraditional AIDCModular AIDCTotal CAPEX$1.631B$1.642BPeak Funding$1.631B$1.387B5-Year Net Profit$518.6M$575.4M5-Year CAPEX ROI31.79%35.05%Peak Funding ROI31.79%41.49%Estimated Annualized IRR~12.0%~14.9%

The modular project requires approximately $10.4 million more CAPEX, yet the model indicates approximately $56.8 million more five-year net profit.

Why?

Because GPU capacity begins generating revenue earlier.

The objective is therefore not simply to minimize CAPEX.

It is to optimize the relationship between:

CAPEX + deployment speed + revenue timing + capital utilization.

The New AIDC Metrics: Beyond $/MW

Traditional data center development frequently uses $/MW as a key benchmark.

For AI infrastructure, that is no longer enough.

Three additional metrics should become central to project evaluation.

1. CAPEX per GPU

How much infrastructure investment is required to bring one GPU into commercial operation?

For AI factories, the GPU—not the building—is ultimately the revenue-generating asset.

2. Time-to-Revenue

How many months pass between the first dollar invested and the first GPU-hour sold?

Reducing this period can materially change project economics.

3. Capital Efficiency

How much operating cash flow can be generated relative to peak capital employed?

A modular project that begins producing revenue progressively can potentially outperform a lower-cost project that requires all capital to be deployed before monetization.

Standardized 3MW Pods Can Transform the AIDC Supply Chain

The deeper advantage of modular AIDC is not simply the use of containers.

The real advantage is standardization and repeatability.

Imagine defining one standardized product:

3MW AI Pod = 128 servers = 1,024 GPUs

The supporting infrastructure can be engineered around that repeatable architecture, including:

• MV/LV electrical distribution
• Switchgear and transformers
• UPS and backup power architecture
• High-density busway or power distribution
• Direct-to-chip liquid cooling
• CDU systems
• Heat rejection equipment
• Network infrastructure
• Fire detection and suppression
• Environmental monitoring
• DCIM and intelligent control systems

Once standardized, significant portions of the system can be factory manufactured and pre-integrated in parallel with site preparation.

This reduces dependency on sequential on-site construction.

Factory production also enables standardized quality control, repeatable testing procedures and faster replication across multiple projects and countries.

TLS Energy Provides Modularized AIDC Solutions

TLS Energy is developing modularized infrastructure solutions for next-generation AI data centers and AI factories.

Instead of viewing the data center as one large customized building, TLS Energy applies a product-oriented approach to AI infrastructure.

The objective is to create standardized, factory-integrated modular systems that can support high-density GPU computing environments.

A modular AIDC architecture can include GPU/IT modules, liquid-cooling modules, power distribution modules, MV/LV electrical modules and other supporting infrastructure, depending on project requirements.

For large projects, standardized modules can be manufactured and integrated in controlled factory environments while foundations, grid connections and other site works proceed simultaneously.

This parallel construction strategy can significantly shorten project schedules compared with purely sequential construction.

More importantly, the modular architecture allows developers to deploy capacity according to actual demand.

A project does not necessarily need to start with 48MW.

It could begin with:

3MW → 6MW → 12MW → 24MW → 48MW

Each stage can add standardized computing capacity as customer demand, power availability and financing develop.

This makes modularized AIDC particularly attractive for rapidly expanding AI cloud providers, hyperscalers, sovereign AI infrastructure projects and GPU-as-a-Service operators.

From Data Center Construction to AI Factory Manufacturing

The traditional data center industry thinks primarily in terms of construction.

The modular AIDC industry can increasingly think in terms of manufacturing.

That distinction is important.

Construction tends to be project-specific. Manufacturing focuses on standardization, repeatability, supply-chain optimization, factory testing and production capacity.

Once a 128-server / 1,024-GPU / 3MW Pod becomes a standardized product, suppliers can reserve components earlier, optimize production lines and shorten delivery schedules.

Instead of asking only:

“How cheaply can we build 48MW?”

AI infrastructure investors can ask:

“How quickly can we manufacture and activate the next 3MW of revenue-generating computing capacity?”

Conclusion: The Real Competition Is Capital Speed

The 48MW, 16,384-GPU example demonstrates an important principle.

Traditional construction may save approximately $10.4 million in infrastructure CAPEX.

But modular deployment could potentially reduce peak capital requirements by approximately $244 million, generate approximately $56.8 million more five-year profit, and increase estimated IRR from around 12.0% to 14.9% under the assumptions used in this model.

The numbers will naturally vary by GPU pricing, utilization, electricity cost, financing structure, PUE, construction schedule and computing rental rates.

But the underlying principle remains:

For AIDC, speed has financial value.

The future AI factory may therefore not be one enormous building constructed all at once.

It could be a network of standardized, independently deployable 3MW computing units, manufactured in factories and brought online progressively.

For TLS Energy, modularized AIDC represents this transition—from building data centers to manufacturing scalable AI infrastructure.

Because in the AI era, the winner may not be the company that builds the cheapest MW.

It may be the company that converts capital into revenue-generating GPU capacity the fastest.

As battery energy storage systems (BESS) grow in capacity and energy density, fire safety has become one of the most important considerations for developers, manufacturers, EPC contractors and authorities having jurisdiction (AHJs). In 2026, three important standards — ISO 3941:2026, UL 9540A 6th Edition and NFPA 855:2026 — are reshaping how lithium-ion battery fire risks are classified, tested and managed.

Together, these standards create a clearer safety framework for modern containerized BESS projects.

ISO 3941:2026: Recognizing Lithium-Ion Battery Fires

ISO 3941 provides an international system for classifying fires according to the nature of the fuel. The 2026 edition is particularly relevant to the energy storage industry because it recognizes Class L for lithium-ion battery fires.

This distinction is important because lithium-ion battery fires behave differently from conventional fires. A battery failure can involve thermal runaway, high-temperature vent gases, jet flames, toxic emissions, re-ignition and propagation from cell to cell.

Class L should also not be confused with Class D fires involving combustible metals. Typical BESS technologies such as LFP and NMC use lithium-ion cells rather than metallic lithium.

For the BESS industry, the new classification reinforces an important principle: lithium-ion battery fire protection requires dedicated risk assessment and mitigation strategies rather than simply applying conventional fire-extinguishing concepts.

UL 9540A 6th Edition: Moving Toward Large-Scale Fire Testing

Published on March 13, 2026, UL 9540A 6th Edition represents a major development in BESS fire testing.

UL 9540A evaluates thermal runaway and associated fire and explosion hazards. Cell-level testing examines thermal runaway characteristics and vent-gas flammability, while module-level testing evaluates cell-to-cell propagation, heat release, gas release and potential ignition or deflagration hazards.

The major change in the sixth edition is the stronger focus on Installation-Level Large-Scale Fire Testing.

For non-residential BESS, the testing sequence generally progresses from cell and module testing toward installation-level large-scale testing. During the large-scale test, gases released from batteries undergoing thermal runaway are intentionally ignited to establish a developed fire condition.

The test can therefore evaluate critical questions:

• Can fire propagate from one BESS enclosure to another?
• Is the specified separation distance sufficient?
• Can the enclosure withstand severe fire conditions?
• Are nearby equipment and structures adequately protected?
• Are fire suppression and protection measures effective?

This moves BESS fire evaluation closer to realistic worst-case installation scenarios.

NFPA 855:2026: Safer Installation of Stationary Energy Storage Systems

While UL 9540A provides the test methodology, NFPA 855 addresses how stationary energy storage systems should be installed and protected.

NFPA 855:2026 strengthens its focus on fire and large-scale fire testing. Annex G.11 provides guidance for evaluating scenarios in which fire could spread between BESS units.

For containerized BESS projects, NFPA 855 considerations can influence container spacing, fire detection, gas detection, ventilation, explosion protection, emergency shutdown, fire suppression and emergency response planning.

UL 9540A test results can consequently become critical evidence when determining acceptable installation configurations and separation distances.

What Do the 2026 Standards Mean for BESS Manufacturers?

The three standards can be understood as one connected safety framework:

ISO 3941:2026 → Fire Classification

UL 9540A 6th Edition → Fire and Thermal Runaway Testing

NFPA 855:2026 → ESS Installation and Fire Safety

For BESS manufacturers, compliance is increasingly moving beyond simply installing fire detectors and suppression equipment. Safety must be engineered into the complete system, including battery racks, enclosure design, thermal management systems (TMS), battery management systems (BMS), fire suppression systems (FSS), combustible gas detection, ventilation and explosion protection.

As energy density continues to increase, validated system-level fire performance will become increasingly important.

TLS Energy and TLS Offshore Containers International provide containerized BESS solutions for global energy storage projects. By integrating battery racks, liquid cooling, BMS, fire detection and suppression, gas detection, ventilation, electrical systems and customized container enclosures, TLS supports customers in developing safer and more reliable energy storage systems for international markets.

The direction of the 2026 standards is clear: future BESS safety will depend not only on preventing thermal runaway, but also on demonstrating how the complete energy storage system performs when a serious fire actually occurs.

ISO 3941:2026 official standard page · UL 9540A 6th Edition overview · NFPA 855:2026 official preview

Direct Answer

Modular power and cooling infrastructure is most suitable for an AI data center when the project needs phased capacity, repeatable designs, or reduced onsite installation work. It can also be useful where the site has limited construction space or where electrical and mechanical equipment must be assembled and tested before delivery.

It is not automatically faster, cheaper or more efficient than a conventional facility. The result depends on transport limits, site utilities, equipment interfaces, local approvals and how much work is actually completed in the factory. A modular solution should be selected only after comparing the same technical scope with a site-built alternative.

What Is Included in a Modular Approach?

For this article, modular infrastructure means factory-built enclosures for defined data center functions. TLS supplies high-spec enclosures and fully integrated systems for applications including:

• electrical rooms or E-Houses containing switchgear, transformers or distribution equipment;
• UPS and battery rooms;
• generator enclosures;
• cooling or mechanical-equipment modules;
• IT modules containing racks and related support systems.

The exact supply boundary varies by contract. “Modular” does not necessarily mean that every item is installed, tested and ready to operate when the unit arrives onsite.

When Is a Modular Solution a Reasonable Choice?

1. Capacity Will Be Added in Defined Phases

A modular design can support phased development if each block has a clear IT load, electrical capacity and cooling capacity. The site must also reserve the required utility connections, foundations, cable routes and heat-rejection capacity for later phases.

Adding another enclosure is not enough if the incoming power, cooling plant or network cannot support it.

2. The Same Design Will Be Repeated

Factory-built modules are more useful when a project can reuse an approved layout across several units or sites. Repetition can reduce redesign and make test procedures more consistent.

If every module has a different voltage, equipment list, cooling arrangement or control interface, much of this benefit is lost.

3. Onsite Work Must Be Limited

Projects in remote locations or congested sites may benefit from moving equipment installation, wiring and part of the testing into a factory. This can reduce the number of activities performed onsite, but it does not eliminate foundations, external cabling, utility connections or final commissioning.

4. Equipment Interfaces Can Be Frozen Early

Modular fabrication works best when major equipment dimensions, weights, heat loads and connection points are known before manufacturing begins. Late changes to racks, switchgear, transformers or cooling equipment can affect structure, cable routing, access and transport weight.

When May Conventional Construction Be More Suitable?

A site-built electrical or mechanical building may be more suitable when:

• the project has one stable, long-term capacity rather than phased growth;
• equipment is too large or heavy for practical module transport;
• local fabrication and construction resources are readily available;
• the site requires extensive building integration or unusual layouts;
• central cooling or electrical plants provide a simpler whole-site design;
• local approval rules make modular permitting no easier than conventional construction.

The decision should be based on the complete installed system, not on enclosure price alone.

 What Must Be Defined Before Selecting the Module?

These inputs should be agreed before the module layout is frozen. A generic request for an “AI-ready container” is not sufficient for design or quotation.

How Should Power and Cooling Capacity Be Matched?

The project should define the usable capacity of each block under the same operating and redundancy assumptions.

For example, a module may contain enough electrical equipment for a stated IT load, but that load is not deployable if the cooling system cannot remove the corresponding heat at the site design temperature. Similarly, cooling capacity does not solve a shortage in utility power or distribution capacity.

The design review should therefore confirm:

1. usable IT load;

2. electrical capacity after required redundancy and derating;

3. cooling capacity at the stated outdoor and coolant conditions;

4. the largest permitted equipment failure;

5. capacity available during maintenance;

6. limits imposed by external site systems.

The lowest available capacity determines how much IT load the module can support.

What Can Be Tested Before Delivery?

Factory acceptance testing can verify equipment and functions that are complete within the module boundary. Depending on the supply scope, this may include:

• equipment identity and installation checks;
• electrical continuity, insulation and grounding;
• switchgear and control-panel functions;
• HVAC, pumps or cooling-control logic;
• alarm and emergency-stop signals;
• communications point checks;
• simulated transfer or failure sequences.

Factory testing cannot confirm the performance of incomplete external systems. Incoming utility power, external cooling equipment, field cables, network connections and integrated load performance must be tested after installation.

What Should Be Compared in the Commercial Evaluation?

Compare modular and conventional proposals using the same scope:

• engineering and approval work;
• enclosure or building construction;
• installed electrical and cooling equipment;
• factory testing;
• transport and lifting;
• foundations and external services;
• site installation and commissioning;
• spare capacity for later phases;
• maintenance access and equipment replacement;
• responsibility for interface failures.

A modular quotation may appear lower if foundations, external cables, cooling plant or commissioning are excluded. The exclusions and responsibility matrix should be reviewed with the price.

Frequently Asked Questions

1. Is a modular AI data center always quicker to deploy?

No. Factory fabrication can run in parallel with some site work, but the overall schedule still depends on design approval, equipment lead times, utilities, foundations, transport and commissioning.

2. Does factory integration make the system plug-and-play?

Not in the literal sense. External power, cooling, communications, fire systems and controls still require connection and testing onsite.

3. Does every AI data center require liquid cooling?

No. The cooling method should follow the selected server equipment, heat density and operating conditions. Air, liquid or hybrid cooling may be appropriate.

4. Can a standard module be used for different server generations?

Only within its structural, electrical, cooling and dimensional limits. A major change in rack power, weight, coolant conditions or connections may require redesign.

5. What is the most important procurement document?

The supply-boundary and interface-responsibility matrix is critical. It should state who designs, supplies, installs, connects, tests and approves each system.

Conclusion

Modular power and cooling infrastructure is a practical option when capacity is phased, designs are repeatable and equipment interfaces can be defined early. It is less suitable when transport restrictions, one-off layouts or central site systems dominate the design. Selection should follow a like-for-like comparison of installed scope, schedule, interfaces and lifecycle operation.

CONTACT US TODAY