How to Set Remediation Windows After Failed Site Acceptance on Reserved B300

Consider an illustrative procurement failure: a reserved Supermicro HGX B300 delivery reaches the buyer’s facility, but a witnessed site acceptance test (SAT) fails. The seller promises a technician “next week.” Two weeks later, replacement parts remain in transit, the acceptance invoice is disputed, and nobody agrees whether troubleshooting restarted the clock.

The missing term was not another technical specification. It was a bounded remediation process.

For procurement, the rule is straightforward: negotiate failure handling before shipment. Factory acceptance testing (FAT) covers testing at the factory; it does not replace the contracted site acceptance gate.

1. Start the clock with the failed witnessed SAT

Define Day 0 as the date the failed witnessed SAT is recorded and the failure notice is delivered through the contract’s specified notice channel. Require prompt delivery so paperwork cannot extend the schedule.

The record should identify the tested units, configuration, failed test references, witnesses, and supporting logs. A seller’s refusal to countersign should not stop the clock where the agreed witness procedure was followed.

An illustrative schedule—not an industry standard—is:

• Day 1: Seller acknowledges the notice and names its remediation lead.
• Day 3: Seller supplies a corrective-action plan, parts requirements, and retest booking.
• Day 14: Seller completes rework and passes the witnessed retest.
• Day 15: Buyer may exercise the agreed failed-cure remedies.

Specify calendar days, the governing time zone, and deadline times. Fourteen days is a negotiating example; choose a period supported by credible parts and technician availability. Holidays, subcontractor delays, and parts orders should not automatically pause it.

2. Make one counterparty own rework

The contracting seller should remain accountable even when an OEM, integrator, carrier, or field-service subcontractor performs the work. Procurement should not have to coordinate a chain of vendors to obtain a passing retest.

For seller-responsible failures, allocate diagnostics, replacement parts, technician labor, travel, removal, packaging, return freight, redelivery, reinstallation, and retesting to the seller. Address duties and nonrecoverable taxes where relevant rather than leaving them inside “reasonable repair costs.”

Distinguish seller defects from documented buyer-caused conditions. A claimed power, cooling, or network issue should require evidence against the agreed site prerequisites—not merely an assertion.

Any extension should require a signed change recording the cause, affected work, cost allocation, and revised deadline. Limit tolling to demonstrable buyer-caused delay. See the installation and commissioning responsibility guide for the underlying responsibility split.

3. Clear the gate with a passing retest

“Repair completed” is not acceptance. Neither is a service ticket marked closed.

Require a retest package containing:

• The original failure record and corrective-action summary.
• A serial-number mapping for repaired or substituted units.
• Relevant configuration and firmware changes.
• Timestamped retest results against the previously agreed SAT criteria.
• A witnessed acceptance record signed by the buyer’s authorized approver.

Give the buyer or its designated independent witness the right to attend. Set notice requirements and an expedited scheduling process so neither party can indefinitely defer the retest.

Allow reasonable repeat attempts within the original cure window. A new technician, replacement component, or failed retest should not restart Day 0. Define whether related tests must be repeated when rework could affect previously passing results.

Keep this evidence focused on clearing the recorded failure; use the reserved B300 acceptance criteria guide to establish the baseline before delivery.

4. Put payment and title consequences on dates

During remediation, state whether the affected acceptance payment remains unearned, withheld, or unreleased from escrow. Do not assume a failed SAT overrides contradictory invoice terms.

If cure expires without a passing retest, give the buyer an election: reject affected units and terminate that portion, demand compliant replacement by a fixed date, or approve a written extension. Partial rejection requires clear unit-level boundaries.

For example, a buyer electing rejection on Day 15 might be entitled to repayment within five calendar days after its election notice. Identify which deposits and affected-unit payments are refundable.

Treat title separately from payment and possession. If title already passed, define how rejection, repayment, collection, and any retransfer work together. Address removal costs and risk of loss during collection; failure alone should not be assumed to reverse title.

Coordinate remedies explicitly:

• LDs: State whether applicable delay damages continue during cure, their endpoint, and how overlapping recovery is avoided.
• Escrow: Make release conditions and disputed-funds handling consistent with the failed-SAT process.
• Extension: Preserve accrued remedies unless expressly waived.

Compare reserved-delivery requirements with Pacific’s capacity options. If remediation threatens the operating schedule, assess bridge capacity for interim compute needs without assuming substitute capacity is immediately available.

5. Replace “seller will fix it” with bounded language

A drafting starting point:

This excerpt needs the notice definition, evidence requirements, refund deadline, and title provisions described above. Ask counsel to review proposed contractual language, including enforceability and consistency across the purchase order, MSA, warranty, LD, and escrow documents.

Bring the proposed cure timeline and responsibility matrix to a procurement planning call with Pacific Intelligent Technologies, Inc..

6. FAQ: What should procurement resolve before signing?

Does a factory pass override a site failure?

Not where the contract requires separate SAT acceptance. Keep the gates distinct; see factory acceptance test evidence.

Should escrow release when repairs are reported complete?

Tie release to the contracted evidence, not an unsupported repair notice. See escrow and witnessed acceptance.

Can delay damages continue through remediation?

Only as the agreement provides. Align the cure deadline with late-delivery liquidated damages.

Where can our team start a broader procurement discussion?

Explore Pacific Intelligent Technologies, Inc. and bring the failed-SAT timeline—not just the delivery date.