How to Define Spare-Pool Ownership Across Multi-Site Reserved B300 Awards

Imagine two sites buying reserved Supermicro HGX B300 capacity under one award. A failure at Site A triggers a request for a replacement module. Site B has the spare, but its operator will not release it: nobody agreed whether that module belongs to Site B, the buyer, or a shared reserve. The hardware exists; the authority to move it does not.

Procure the spare pool as an operating arrangement, not a reassuring line item. Evaluate ownership, physical custody, allocation rights, and replenishment separately. This is an award-structure checklist, not a warranty deep-dive or a claim that a particular B300 module is available or interchangeable.

1. Define the spare before defining the pool

“B300 spares included” is too broad to evaluate. Require a schedule of covered assemblies for the proposed Supermicro HGX B300 configuration. The replaceable unit, approved service procedure, and compatibility constraints determine whether a spare is useful at another site.

• Identify each covered assembly by part number or an agreed configuration-controlled specification. State any revision, firmware, or platform restrictions.
• Disclose whether the reserve contains complete systems, field-replaceable assemblies, or components requiring an authorized service workflow.
• Distinguish physical spare equipment from reserved replacement capacity. A right to another compute allocation is not title to a replacement module.
• List eligible sites and excluded configurations. Require technical approval before treating a substitute as equivalent.

Compare proposals against the same covered-unit schedule. Otherwise, one supplier may be pricing local hardware while another is offering access to an off-site service reserve.

2. Separate ownership, custody, and control

The party holding legal title does not necessarily store the spare or authorize its release. Give each role a named organization and an accountable contact. Avoid using “owner” as shorthand for all three.

• Title holder: identify who owns unused spare equipment, and whether ownership changes upon payment, delivery, acceptance, withdrawal, or installation.
• Custodian: identify who stores, secures, inspects, and records the equipment, including any third-party warehouse or site operator.
• Allocation controller: identify who can approve a draw, resolve competing requests, and prevent unauthorized reassignment.
• Service authority: identify who may transport, handle, install, and validate the replacement under the agreed support procedure.
• Record keeper: designate the inventory system of record and who can reconcile serial numbers, reservations, withdrawals, and returns.

If the supplier retains title, disclose whether the buyer has an exclusive reservation or only a contractual access right. If the buyer owns the spare, document any limits on moving it or changing its service provider.

3. Choose shared, site-local, or hybrid placement

A shared pool can serve multiple sites, but its physical location still matters. A site-local pool reduces some transfer dependencies, but only if the relevant spare is actually allocated to that site. A hybrid arrangement needs explicit boundaries between local minimums and the shared reserve.

• Shared pool: name the storage location, eligible sites, allocation priority, and any permitted commitments to customers outside your award.
• Site-local pool: name the site's protected allocation and whether another site may borrow it. State who can approve an exception.
• Hybrid pool: define local minimums separately from shared quantities. Do not count one physical unit as two independently guaranteed allocations.
• Transfer readiness: disclose dispatch windows, carrier arrangements, access restrictions, and cross-border dependencies where applicable.

Request evidence of the proposed allocation method and a dated readiness record before coverage starts. Do not treat a proposed pool schedule as proof that equipment is already stocked.

4. Write draw rights for simultaneous failures

The hardest case is not the first request. It is two eligible sites requesting the last compatible spare. Decide the priority rule during procurement rather than leaving an incident manager to negotiate it during an outage.

• Trigger: define what evidence opens an eligible request and whether diagnosis must be confirmed before release.
• Authorization: name primary and backup approvers, after-hours contacts, and the escalation path when an approver is unavailable.
• Priority: establish an agreed order, such as protected site allocations followed by incident severity and request time.
• Timing: separate acknowledgment, authorization, dispatch, delivery, installation, and restoration targets. Define the clock and permitted pauses for each.
• Exception: state what happens when the pool cannot satisfy concurrent requests, including notice, alternatives, and any negotiated remedies.

Require a draw record with the affected site, approved replacement, authorizer, release timestamp, and resulting pool balance. An emergency release should still leave an auditable trail.

5. Make replenishment a separate obligation

A successful replacement can leave the remaining sites exposed. Define replenishment independently of the failed unit's repair or return path. Do not assume a warranty process automatically restores the contracted pool balance.

• Assign refill responsibility and cost responsibility, including transport, inspection, and any approved substitute.
• Define when the refill clock begins: draw authorization, physical withdrawal, installation, or another recorded event.
• Specify the replenishment target and required status updates. Identify any dependencies rather than presenting uncertain supply as guaranteed.
• Require interim coverage and escalation proposals when the pool falls below its agreed minimum.
• Close replenishment only after compatibility, condition, location, and allocation records are verified—not merely when a purchase order is issued.

Keep failed-unit disposition and warranty eligibility in the supporting service schedule. For that adjacent review, use the reserved B300 warranty, RMA, and spares checklist. Here, the procurement question is who restores coverage for every site left in the pool.

6. Allocate title, loss risk, and exit rights

Title and risk of loss should have separate clauses. A buyer can own a spare while another party bears agreed storage or transit risks. Specify the handoff events rather than assuming possession, ownership, and insurance always move together.

• Map loss and damage responsibility during storage, picking, packing, transit, receipt, installation, and return shipment.
• Name the party responsible for insurance, claims handling, deductibles, and replacing a spare lost before installation.
• Document permitted use, substitution, lending, and relocation. Require approval before a protected reserve is diverted to another obligation.
• Address identification and segregation of buyer-owned property, inventory access, and recovery rights if the custodian or supplier relationship fails.
• Define exit treatment for unused spares, installed replacements, failed units, and any outstanding replenishment obligations.

7. Attach a pool schedule to every award

Use one governing pool schedule with site-specific annexes where needed. Cross-reference it in each award that relies on shared coverage. State document precedence so a site order cannot silently promise rights that conflict with the shared arrangement.

• Pool identity: pool ID, covered assemblies, compatibility baseline, eligible sites, and effective coverage date.
• Rights matrix: title holder, custodian, allocation controller, service authority, and buyer audit or reporting rights.
• Allocation table: agreed quantities, physical locations, protected local minimums, shared rights, and outside commitments.
• Operating rules: draw triggers, priority, escalation, transfer responsibilities, replenishment targets, and shortage procedures.
• Commercial terms: cost allocation, title events, risk handoffs, remedies, change control, and termination treatment.
• Acceptance evidence: reconciled inventory records, approved contacts, documented release workflow, and a tabletop test of competing site requests.

Tie the coverage start to explicit evidence and agreed acceptance conditions. Use the reserved B300 acceptance-criteria checklist to keep pool readiness distinct from delivery and compute acceptance.

When evaluating reserved GPU capacity procurement with Pacific, bring the site map, proposed covered-unit list, and draft allocation table. Ask which obligations can be committed in writing and which remain dependencies.

FAQ

Does the buyer need to own every spare?

Not necessarily. Supplier-owned spares can support a defined access arrangement, while buyer-owned spares may provide different control rights. Evaluate enforceable allocation, custody, release, refill, and exit terms—not ownership alone. Neither structure establishes availability without supporting evidence.

Can one shared pool cover several site awards?

Yes, if the awards reference a consistent pool schedule and disclose how competing requests are handled. Identify the aggregate commitment, any protected site minimums, and whether outside customers can draw from the same stock. Avoid counting shared access as an independent dedicated reserve at every site.

What should procurement resolve before signing?

Resolve who owns each covered spare, where it sits, who may release it, how simultaneous requests are prioritized, who restores the pool, and who bears loss during each handoff. Attach those answers to the award, with acceptance evidence and change-control rules.

For a procurement discussion with Pacific Intelligent Technologies, Inc., schedule a 30-minute reserved-capacity review. Bring the draft pool schedule so the conversation starts with accountable rights and obligations rather than an undefined promise of spares.