An AI server BOM is ready for sourcing when every required assembly has an identifiable ordering code and every proposed alternative has an approval route. Accelerators and processors attract attention, but missing support components, cable variants or programmed settings can prevent an otherwise complete kit from becoming a working server.
Review the design by subsystem and connection
TI's server design overview groups requirements around power conversion, protection, density and high-bandwidth signal processing. Use a system block diagram in the same way: follow each power and data connection and verify that all supporting parts appear in the purchasing record.
Check regulators, power stages, inductors, current-sense resistors, protection devices and bulk or local decoupling. Review clocks, buffers, reset circuits, configuration flash and management interfaces. For the data path, include the correct retimers or redrivers, connectors and cable assemblies required by the approved topology.
Extend the review to fans, heatsinks, thermal materials, carriers, brackets and fasteners. Record both halves of mating connectors and any assembly-specific harness. A small mechanical omission can have the same schedule impact as a missing high-value IC.
Capture ordering and configuration details
Each line should contain manufacturer, complete part number, description, quantity per assembly, unit of measure and required condition. Add package, temperature grade and revision restrictions when they distinguish acceptable items. Separate design quantities from assembly loss, service spares and engineering samples.
Mark components that require programming, calibration or configuration before installation. Identify the approved artifact and responsible team without placing credentials or private keys in the BOM. For firmware-dependent assemblies, document the supported version and how its identity will be verified during acceptance.
Close gaps before requesting a complete kit
Assign a status to every alternative: proposed, under evaluation or approved for the stated revision. Require an owner and acceptance evidence for substitutions. Do not let a purchasing abbreviation such as equivalent replace the engineering record of what has actually been checked.
Reconcile the BOM with assembly drawings, schematics and the build configuration. Confirm dependencies between boards, cables, firmware and cooling options. Before release, review a sample kit against the planned assembly sequence and identify any items supplied separately by the customer or platform vendor.
Frequently asked questions
Does a complete BOM guarantee a working server?
No. Assembly, programming, platform compatibility and system validation still need to be completed and recorded.
Should optional configurations share one combined quantity list?
Use clearly identified variants or configuration rules so mutually exclusive options are not accidentally purchased or installed together.
Submit your server BOM for quotation with revision, build quantity and approved alternatives. Stock, price and lead time are confirmed in the quotation.