Stacy Lu
Support Team
Feedback:
support@nextpcb.comThe AI hardware industry has historically been dominated by proprietary accelerator interfaces. NVIDIA's SXM socket, for example, is an NVIDIA-defined standard that locks GPU modules, baseboards, and server chassis into NVIDIA's own ecosystem. For hyperscale cloud providers and ODMs building their own AI infrastructure, this creates supply chain constraints, limits design flexibility, and makes it difficult to mix accelerators from different vendors in a common server platform.
The Open Accelerator Module (OAM) standard was created to address exactly this problem. Developed under the Open Compute Project (OCP), OAM defines a vendor-neutral mechanical and electrical interface for AI accelerator modules, allowing different GPU and AI chip vendors to build accelerators that plug into a common baseboard design. For PCB engineers and server hardware designers, OAM introduces a standardized but highly demanding set of board-level requirements that are worth understanding in detail.
An OAM (Open Accelerator Module) is a standardized form-factor AI accelerator module defined by the Open Compute Project's Open Accelerator Infrastructure (OAI) workgroup. An OAM module contains one or more AI accelerator dies (GPU, NPU, or custom ASIC), high-bandwidth memory (typically HBM), power management components, and a standardized edge connector that plugs into a Universal Base Board (UBB).
The OAM standard defines:
The complementary component is the Universal Base Board (UBB)—the PCB into which OAM modules plug. The UBB provides power, PCIe connectivity to the host CPU, high-speed inter-accelerator links, and thermal management infrastructure. Because the UBB interface is standardized, a UBB designed to the OAM specification can in principle accept OAM modules from any compliant vendor.
The Open Compute Project (OCP) is a collaborative engineering community founded by Facebook (now Meta) in 2011, focused on developing open-source hardware standards for data center infrastructure. OCP contributions cover server chassis, rack architecture, network switches, storage, and increasingly, AI accelerator hardware.
The Open Accelerator Infrastructure (OAI) project within OCP was established to define open standards for AI accelerator modules and their host boards. The OAM specification emerged from OAI as the primary module standard, with contributions from AMD, Intel, Google, Qualcomm, Graphcore, and several ODMs and system integrators. NVIDIA has not adopted the OAM standard for its primary data center GPU products, preferring its proprietary SXM interface.
OCP specifications are publicly available and royalty-free, enabling any hardware vendor to design OAM-compliant modules or UBBs without licensing fees.
Before OAM, each major AI accelerator vendor defined its own module form factor and baseboard interface:
The proprietary approach creates several problems for cloud providers and ODMs:
OAM addresses these problems by separating the module design (accelerator vendor's responsibility) from the baseboard design (ODM's or cloud provider's responsibility) through a published, vendor-neutral interface specification.
The OAM ecosystem consists of two complementary components:
| Component | Description | Designed By |
|---|---|---|
| OAM Module | The accelerator module containing AI chip(s), HBM, and power management; plugs into UBB via edge connector | Accelerator vendor (AMD, Intel, etc.) |
| Universal Base Board (UBB) | The host PCB that accepts up to 8 OAM modules; provides power, PCIe, inter-module links, and management | ODM, cloud provider, or system integrator |
| OAM Carrier / Server Chassis | Rack-mount enclosure housing the UBB, power supplies, and cooling infrastructure | ODM or cloud provider |
The OAM specification also defines two module size classes:
The OAM edge connector carries the following signal categories:
| Signal Category | Interface | Notes |
|---|---|---|
| Host interface (CPU to accelerator) | PCIe Gen4 or Gen5 ×16 | Primary data path from host CPU; Gen5 in current generation |
| Inter-module high-speed links | Vendor-defined high-speed serial (e.g., AMD Infinity Fabric) | Enables accelerator-to-accelerator communication through UBB; equivalent function to NVLink in NVIDIA systems |
| Management interface | I2C, SMBus, MCTP over PCIe | Out-of-band management: power sequencing, thermal monitoring, firmware update |
| Power rails | 12 V (legacy), 48 V (preferred in OAM Gen2+) | High-current power delivered from UBB power planes through edge connector pins |
| Auxiliary signals | GPIO, UART, reset, presence detect | System management and hot-plug support |
The edge connector in the OAM specification uses a high-density, high-current connector capable of handling the combined signal and power requirements of a 700–1,000 W accelerator module. Connector contact pitch is in the 0.5–0.8 mm range depending on signal type, with power pins sized for the required current capacity.
OAM module mechanical dimensions are tightly specified to ensure compatibility across vendors and UBB designs:
A standard UBB accepts up to 8 OAM modules arranged in two rows of four, with defined module-to-module pitch to maintain airflow channels or cold plate alignment.
OAM modules in current AI accelerator applications consume 400–750 W per module. The OAM specification supports two primary power architectures:
OAM modules interface with the chassis thermal management system through a defined contact area on the top surface of the module. The specification defines:
OAM-compliant chassis may use air cooling (heatsinks with forced airflow) or direct liquid cooling (cold plates). At 700 W+ per module and 8 modules per UBB (5,600 W+ total), direct liquid cooling is strongly preferred for sustained operation.
| Parameter | OAM (Open Standard) | NVIDIA SXM (Proprietary) |
|---|---|---|
| Governing body | Open Compute Project (OCP) | NVIDIA |
| Specification access | Public, royalty-free | Licensed; NDA required for full spec |
| Compatible accelerators | AMD MI series, Intel Gaudi, others | NVIDIA GPUs only (A100, H100, B200) |
| UBB / baseboard design | Any ODM or cloud provider can design a compliant UBB | NVIDIA-designed or NVIDIA-licensed HGX baseboard |
| Inter-module interconnect | Vendor-defined (AMD Infinity Fabric, etc.); routed on UBB | NVLink 4.0 / 5.0; routed on NVIDIA baseboard |
| Host interface | PCIe Gen4 / Gen5 (standardized) | PCIe Gen5 (SXM5) / PCIe Gen6 (SXM6) |
| Power bus | 12 V (Gen1) or 48 V (Gen2+) | 12 V (SXM4/5) / 48 V (SXM6 / GB200) |
| Module generations | OAM Gen1, Gen2; evolving | SXM4 (A100), SXM5 (H100/H200), SXM6 (B200) |
| Cross-generation compatibility | OAM Gen1 and Gen2 maintain connector compatibility (with caveats) | SXM4, SXM5, SXM6 are mutually incompatible |
| Primary users | AMD MI300X deployments, cloud providers building open AI servers | DGX, HGX, and OEM NVIDIA AI server programs |
OAM adoption is concentrated among cloud providers seeking supply chain flexibility and accelerator vendors who are not NVIDIA:
NVIDIA does not currently ship products in OAM form factor. NVIDIA's equivalent of the OAM ecosystem is its HGX platform, which uses NVIDIA-proprietary SXM sockets and NVIDIA-designed or NVIDIA-licensed baseboards.
The UBB is the most complex PCB in an OAM-based AI server. A UBB designed for 8 OAM modules must simultaneously accommodate:
Typical UBB layer counts range from 16 to 28 layers, depending on the inter-module interconnect bandwidth and PCIe generation. UBBs designed for AMD MI300X with Infinity Fabric inter-module links and PCIe Gen5 host interfaces commonly use 20–24 layers.
The UBB must route high-speed signals across relatively long board distances (200–400 mm from one module slot to another in an 8-slot configuration). Signal integrity requirements:
At 700 W per module × 8 modules, a fully loaded UBB must deliver up to 5,600 W of accelerator power. Power delivery architecture on the UBB:
The UBB itself operates in a high-temperature environment (8 OAM modules dissipating 700 W each produce significant radiant heat). Board-level thermal requirements:
The OAM module itself is a highly complex PCB assembly within the standardized mechanical envelope. Module PCB design requirements depend on the specific accelerator die(s) and HBM configuration, but common characteristics include:
| Parameter | OAM Gen1 | OAM Gen2 |
|---|---|---|
| Host interface | PCIe Gen4 ×16 | PCIe Gen5 ×16 |
| Primary power bus | 12 V | 48 V (preferred) |
| Module max TDP | ~400 W | ~700 W+ (roadmap to 1,000 W) |
| Inter-module links | Vendor-defined; lower bandwidth | Vendor-defined; higher bandwidth (e.g., Infinity Fabric Gen4) |
| Management | I2C / SMBus | MCTP over PCIe + I2C / SMBus |
| Connector backward compatibility | Gen1 connector baseline | Mechanically compatible with Gen1 slot (with power caveats) |
| Representative products | AMD MI250X | AMD MI300X, Intel Gaudi 3 |
Both OAM modules and UBBs require PCB manufacturing capabilities well above commodity standards:
OAM Module Manufacturing:
UBB Manufacturing:
Does NVIDIA support the OAM standard?
No. NVIDIA uses its proprietary SXM form factor (SXM4, SXM5, SXM6) for its data center GPU modules. NVIDIA has not adopted the OAM standard for its H100 or B200 GPU lines. NVIDIA's HGX platform is the proprietary equivalent of the OAM ecosystem—a standardized baseboard and module system, but controlled by NVIDIA rather than an open standards body.
What is the difference between OAM and HGX?
OAM is an open standard governed by the Open Compute Project, usable by any accelerator vendor. HGX is NVIDIA's proprietary equivalent—a baseboard and module specification controlled by NVIDIA that supports only NVIDIA GPUs. Both achieve a similar goal (standardizing the accelerator-to-baseboard interface within a vendor's ecosystem), but OAM does so across multiple vendors while HGX is NVIDIA-exclusive.
Can an AMD MI300X OAM module be used in an NVIDIA HGX baseboard?
No. OAM and HGX/SXM are physically and electrically incompatible. An AMD MI300X OAM module requires an OAM-compliant UBB; it cannot be installed in an NVIDIA SXM5 or SXM6 socket.
How many OAM modules fit in a standard server?
A standard OAM UBB accommodates 8 OAM modules. A 2U server chassis can typically house one UBB (8 modules), making 8 accelerators per server the common configuration for OAM-based AI servers.
What is the maximum power per OAM module?
OAM Gen1 supports up to approximately 400 W per module. OAM Gen2 supports up to 700 W per module today, with the specification roadmap extending toward 1,000 W per module for future accelerator generations. The 48 V power bus in OAM Gen2 is essential for managing the high currents at these power levels.
Is OAM used for inference or training workloads?
OAM modules are used for both training and inference. AMD's MI300X, which ships in OAM form factor, is deployed for both large-scale training (competing with H100) and high-throughput inference. The OAM standard itself does not specify the workload—it defines only the physical and electrical interface between module and baseboard.
OAM modules and Universal Base Boards demand precision fabrication: large-format PCBs, heavy copper power planes, low-loss laminates, fine-pitch BGA assembly, and rigorous post-assembly inspection. NextPCB's advanced PCB manufacturing capabilities support the full OAM hardware stack—from prototype module PCBs to production UBBs.
Related Articles:
Still, need help? Contact Us: support@nextpcb.com
Need a PCB or PCBA quote? Quote now