1. Separate the Memory Description from the Supply Item

An inquiry for “HBM3e” can leave the recipient guessing which product layer is required. Micron's public HBM3E material describes memory cubes and their use with GPUs. NVIDIA and AMD publish accelerator configurations that include HBM. A memory technology name, an accelerator family and a finished server therefore describe different things. Start by naming the actual object that must appear on the supplier's offer.

For a design-level memory requirement, ask the engineering owner to identify the exact manufacturer device or stack, its ordering information and the relevant integration documentation. Record whether that item and its supply route have actually been qualified for the design. If the needed documentation or code is unavailable, mark the request as an engineering clarification rather than converting it into a confirmed component purchase line.

For an accelerator or system requirement, specify the complete assembly instead of requesting its internal memory as a presumed replacement. A public memory specification does not establish that an HBM stack can be removed, purchased separately or installed in an existing accelerator. This checklist uses public manufacturer documentation and procurement questions; it does not describe customer testing, component extraction or an ICULTRA rework service.

  • Name the supply layer: memory device, accelerator assembly or complete system.
  • Keep the requested item separate from its technology and capacity descriptions.
  • Assign an engineering owner to unresolved identity or integration questions.

2. Identify the Accelerator Variant or OEM Configuration

NVIDIA's H200 page lists HBM3e and publishes separate H200 SXM and H200 NVL specifications. Both list 141GB of GPU memory, while the form-factor entries distinguish SXM from PCIe. The page labels its specifications preliminary and subject to change. These examples explain why memory capacity alone cannot distinguish the required accelerator variant; check the current documentation for the proposed item.

AMD's MI300X page lists 192GB of HBM3 and an OAM module form factor. It separately identifies the PCIe bus. Keep those fields separate: a bus description does not turn an OAM module into a conventional plug-in PCIe card. The H200 and MI300X examples are published configurations, not a statement that either is available from ICULTRA or interchangeable in your platform.

For an installed server, start with the OEM model, assembly or spare-part SKU and approved configuration. Ask the system owner to identify the permitted accelerator, revision and supporting platform documentation. A family name may need further qualification to reach the actual order line. Keep required cooling, power, interconnect and software support tied to that configuration rather than carrying assumptions from another variant.

  • Capture the vendor SKU or complete ordering code and the specified revision.
  • Record form factor separately from bus interface and installed memory.
  • Link the item to the target OEM configuration and its approval reference.

3. Create a Line That Describes the Deliverable

Use one request line for each distinct supply item. Preserve all characters in a manufacturer ordering code or OEM SKU; do not replace it with a marketing family name or your internal material reference. Keep the internal reference in another field. If the request concerns a complete system, attach its approved configuration instead of treating the accelerator name as the entire server specification.

State the quantity in the unit being purchased. A memory cube, a module, a board assembly and a server are not equivalent count units. Also distinguish memory capacity per accelerator from aggregate capacity across a system. If a configuration contains several accelerators, identify the intended assembly count and configuration rather than silently translating total memory capacity into a number of parts.

Define what must accompany the item. Ask whether the offer includes the specified carrier or assembly, any required interconnect parts, installation accessories and the stated support scope. Describe required condition and available identity records at the relevant layer. A serial number can link an offered assembly to a record, but cannot substitute for confirmation of the correct SKU or acceptance requirements.

  • Include supply layer, complete identifier, revision, quantity and unit.
  • Attach the approved configuration and the current reference document.
  • List required included items and explicitly identify unknown fields.

4. Resolve Identity Differences Before Comparing Offers

Ask each supplier to identify the exact deliverable against your request. Keep differences in SKU, revision, form factor, configuration or included items on an exception list. An offer describing similar HBM capacity is not automatically an offer for the same assembly. Resolve those differences with the engineering or system owner before treating two quotes as comparable.

If the supplier suggests a different accelerator or configuration, record it as a proposal requiring review. Do not rewrite the original requirement under the candidate's name. Manufacturer product pages provide useful specification references; they do not establish approval for your server, a particular lot's condition, or a written supply commitment. Request current availability, documentation and commercial terms for the exact item separately.

For an ICULTRA sourcing review, send the identified supply layer, full ordering code or OEM SKU, approved configuration, quantity and any unresolved differences. Link the relevant public documents so the recipient can follow the identity decision. The general AI server procurement guide covers wider RFQ preparation; this checklist helps make the HBM-related item itself unambiguous.

Sources and further reading

Manufacturer documents support the technical guidance above. They do not confirm our stock, authorisation or the condition of any offered lot.