How to Freeze Config After Awarding Reserved B300 Capacity

The award was signed for named Supermicro HGX B300 capacity. Weeks later a “minor” change order arrived: different NICs, different storage, and an allegedly equivalent GPU. The NVSwitch topology was no longer explicit. Engineering first saw the differences on the crate list.

That is a configuration-freeze failure, not a surprise of the supply chain. Freeze the awarded build immediately after award, before packing documents and verbal substitutions become the new contract.

Freeze a complete baseline, not a product name

“Supermicro HGX B300” is a family, not a bill of materials. The freeze should name chassis, GPU count, NVSwitch topology, NIC model and count, fabric and optics, CPU, memory, storage, power and cooling interfaces, management path, and the firmware and driver revisions that matter to the workload.

Put a revision number on that baseline and put the same revision on the purchase order. If later documents omit the revision, they do not amend the freeze. If later documents use a new revision without a signed change, they are a drafting error, not a new build.

The baseline is what both parties will reconcile against when crates arrive. A product name that can absorb silent NIC, storage, or topology changes is not a reserved configuration.

Put the freeze date in writing

Silence does not amend a freeze. Packing lists do not amend a freeze. A supplier email that says “equivalent” does not amend a freeze. The freeze date is the moment the awarded configuration becomes the controlled baseline.

Write that date into the order package so later change orders have something to redline against. This playbook is not inventory diligence, milestone drafting, liquidated damages, or acceptance testing. Those are separate commercial sequences. This one is narrower: after award, what exactly is frozen?

Procurement teams sourcing reserved GPU capacity from Pacific should treat the freeze as part of buying named compute, not as optional engineering paperwork.

Remove “equivalent” as a unilateral escape hatch

A substitution that the supplier can make alone is not a freeze. Require a written change, a reason, a redline against the frozen revision, a statement of effects (performance, topology, power, cooling, lead time, acceptance), a designated approver, and a new revision number.

“Allegedly equivalent GPU” is the phrase that most often erases the reservation. If the GPU, NVSwitch topology, or host fabric changes, the reserved system has changed. The change may still be acceptable. It is not automatic, and it is not minor because the supplier called it minor.

Unavailability of a frozen part should trigger the same change process. It does not authorize a silent swap. If the supplier cannot hold the frozen build, they request a change. If the buyer does not approve it, the frozen build remains the commitment.

Name who can approve a change

Procurement owns the commercial record. Infrastructure engineering owns the technical review. Both should appear on the approval path. A buyer-side engineer who was not on the award should not discover the new NIC on the loading dock. A procurement owner who never saw the topology should not be the only signature on a “minor” swap.

Keep the change-order form short: frozen revision, proposed revision, reason, redline, effects, requested by, approved by, date. No signature means no change. Verbal agreement in a status call is not a revision.

Reconcile later documents to the frozen build

When packing lists, serial files, factory records, or installation drawings arrive, reconcile them to the frozen revision before accepting them as the as-built. Differences are either errors or unsigned changes. Do not let the crate list become revision n+1 by default.

If the reserved environment is late while a change is under review, treat any temporary cover as a separate commercial object. Pacific's bridge capacity is designed for the interval before longer-term capacity becomes usable. It should not silently rewrite the frozen B300 baseline.

Pacific Intelligent Technologies, Inc. structures reserved capacity around a named, usable configuration. If your team is turning an awarded B300 build into a controlled baseline, book 30 minutes with Harper.

FAQ

What if some configuration items are still open at award?

Enumerate them. An open item that is written down is a known gap. An open item that is left inside a product name becomes a unilateral substitution later. Freeze what is known, list what is not, and require the same change process when an open item is closed.

Should firmware and drivers be in the freeze?

Yes, if they are material to the workload, topology, or acceptance suite. A firmware move that changes NVSwitch behavior, NIC offload, or supported driver versions is a configuration change. If a later patch is expected, write the allowed range rather than leaving the field blank.

What if a frozen part becomes unavailable?

Unavailability triggers the change process. It does not authorize a silent equivalent. The supplier proposes a redline, engineering reviews effects, procurement records the new revision, and only then does the baseline move.

Does a freeze prove that reserved allocation exists?

No. A freeze controls what you are buying. It does not prove that quantity has been allocated, that inventory exists, or that a delivery date is holdable. Those are diligence questions on Pacific's reserved GPU capacity offering and the broader model at Pacific Intelligent Technologies, Inc..

Who owns the freeze after award?

Procurement owns the record: revision number, signatures, and the order package. Engineering owns the technical review of any redline. Neither role should be able to move the baseline alone. When that package is ready to walk, schedule 30 minutes with Harper.

The core rule is simple: freeze a complete baseline, date it, remove unilateral equivalents, name the approvers, and reconcile later documents to that revision. That is how a reserved Supermicro HGX B300 award stays the system you reserved.