By Zhang Binghua, Chief Technology Officer, Bridge Data Centres
The defining challenge of AI infrastructure is bringing capacity online at the right time, in the right configuration, with room to evolve. As campuses grow and hardware cycles accelerate, this requires a closer connection between resources, engineering and operations.
At Bridge Data Centres (BDC), we are working towards more than 2 GW of regional capacity by 2030. Across Southeast Asian markets such as Malaysia and Thailand, growth at this scale makes land, power, water, fuel and fibre part of one development challenge.
Customers also need facilities that can accommodate cloud services, AI training and inference across multiple hardware generations. At the same time, delivery expectations are moving from more than 24 months towards around 10 months. Buildings must last for decades; the infrastructure inside them must adapt much faster.
My view is that these demands have to be addressed together. Faster construction alone cannot resolve a delayed power connection, and a flexible building is of limited value if its power and cooling systems cannot support the next generation of equipment.
That is the thinking behind Bridge’s Omni Platform, our modular, intelligent infrastructure framework for AI data centres. It connects three layers: i-Resource Base for campus resources, the i-Cube engineering family for physical infrastructure, and i-OmniSight for operations and orchestration.
What the Name Says About Our Design Philosophy
For me, the name Omni expresses a fundamental engineering choice: to view the campus as a whole. “Omni” means all-encompassing. Resources establish the foundation for growth, engineering turns those resources into usable capacity, and operations sustain performance while feeding experience back into design. These layers are interdependent. A decision about power availability affects the delivery sequence; a change in rack density affects cooling and building configuration. By bringing them into one framework, we can assess those consequences earlier and coordinate decisions around shared campus objectives.
“Cube” describes how we make that integrated approach adaptable. Inspired by the Rubik’s Cube, the i-Cube family gives each module a defined role and standard interfaces while allowing different configurations. The engineering principle matters more than the analogy: flexibility depends on the discipline of the connections. With consistent interfaces, i-Building, i-Pod, i-Power and i-Cooling can be combined to suit different sites and customer requirements, and capacity can expand without redesigning every connection. This gives us LEGO-like flexibility within a coherent engineering system.
The “i” stands for intelligence, integration and innovation. I see these as three connected responsibilities. Integration makes information and capabilities usable across systems. Intelligence helps teams interpret that information, anticipate conditions and connect decisions to controlled action. Innovation turns what we learn into better designs and operating practices. i-OmniSight brings these responsibilities together as the operations and orchestration hub linking the Resource Base and the Cubes.
Together, these names describe what we mean by full-stack convergence: distinct capabilities coordinated around the same campus outcomes. The purpose is practical: to deliver usable capacity sooner, operate it with better insight, and retain the ability to adapt as AI infrastructure evolves.
From Design Philosophy to Customer Value
i-Resource Base gives growth a credible foundation by aligning resource availability with each phase of development. The question is whether the resources a campus requires will be ready when customers need capacity, in a way that respects local constraints and community interests.
The i-Cube family carries that thinking into engineering. i-Building provides a lasting structure, while i-Pod allows capacity within it to evolve. i-Power and i-Cooling support changing workload needs. Together, they help us deliver repeatable solutions while preserving the choices each site and customer requires.
For me, this is the practical value of modularity: decisions made today should leave room for tomorrow. Customers need a clear path to expand and adopt new hardware without reconsidering the entire campus each time their requirements change.
i-OmniSight connects the Resource Base and the Cubes through a shared view of operations. As campuses grow across regions, AI helps teams anticipate issues and coordinate informed responses, with people retaining oversight. Experience from daily operations then informs future designs, so each deployment contributes to a better platform.
A Shorter Path from Resources to Usable Capacity
For customers, the value of Omni lies in how its layers work together: resource planning supports a credible delivery sequence, modular engineering reduces repeated work, and connected operations sustain dependable performance.
This approach also preserves options. Capacity can be added in phases, engineering configurations can respond to site conditions, and infrastructure can adapt as customer workloads and hardware evolve.
This is the next step in AI infrastructure: treating the campus as a connected system, with resources, engineering and operations planned around shared outcomes. Bridge’s Omni Platform gives that approach a practical form: a bridge from land and energy to AI-ready capacity, built to grow and evolve with our customers.