How to Require Factory Acceptance Test Evidence Before Reserved B300 Ship

Consider an illustrative procurement snag: a founder receives a “FAT passed” PDF for a reserved Supermicro HGX B300 system. The report names the product family, but not the chassis serial, installed components, firmware versions, or test scripts. Pickup is scheduled for tomorrow. Nobody can show that the machine being loaded is the machine that passed.

The problem is not necessarily failed hardware. It is missing proof—and no agreed rule preventing shipment while that proof is incomplete.

Use the checklist below to make evidence review part of ship authorization. These are procurement requirements for counsel to review, not legal advice.

1. Agree on the FAT evidence package before testing

Factory acceptance testing should follow an approved, versioned plan tied to the reserved order. Do not accept a generic factory checklist as the complete deliverable.

Require the plan to identify:

• System under test: order reference, exact Supermicro HGX B300 configuration, and configuration-freeze revision.
• Test coverage: component enumeration, hardware health, GPU and interconnect diagnostics, memory checks, storage and network checks, and agreed workload testing.
• Execution details: test tools and versions, commands or scripts, duration, load profile, and factory operating conditions.
• Pass/fail rules: measurable thresholds, allowed exceptions, and how incomplete tests are reported.
• Evidence outputs: logs, result summaries, inventory exports, photographs where useful, and operator sign-off.

Set these requirements before the test window. “Factory standard” is not a substitute for a named procedure that procurement can inspect.

For broader sourcing context, review reserved GPU capacity options, then make the FAT package specific to the proposed order.

2. Prove the tested configuration matches the frozen order

The evidence package needs an identity chain: reserved order → approved configuration → physical system → test results.

Ask the supplier to provide a machine-readable inventory export alongside the signed report. Record chassis identity and available component identifiers for GPUs, network adapters, storage, and other specified parts. Include SKU or part-number mappings where serials alone do not establish the ordered specification.

Also capture BIOS, BMC, GPU firmware, driver, and relevant software versions. A photo of a chassis label helps establish physical identity; it does not prove what was installed during testing.

Require timestamps and a manifest connecting each log to the tested system. Checksums can help detect later file changes, but they do not independently prove that a test occurred.

Define what happens after testing. A component substitution, firmware change, or configuration correction should trigger a documented impact review and the agreed retest scope. The outgoing manifest must reconcile with the configuration covered by the approved FAT evidence.

3. Choose witnessed, remote, or documented FAT deliberately

Witnessing and documentation are different controls. Neither should be left to an informal invitation.

On-site witnessed FAT: Name the authorized observer, notice period, access arrangements, and tests the observer must see. Record attendance and any limits on observation.

Remote witnessed FAT: Require a live identity check, visibility into test execution, and access to the underlying results. Agree on recording permissions and retention. A video call showing a dashboard is not equivalent to receiving the logs.

Documented FAT: Specify who executes and signs the tests, what evidence procurement receives, and how questions or missing files are resolved before release.

For every option, distinguish “witnessed execution” from “approved results.” An observer’s attendance does not automatically authorize shipment. If a required witness cannot attend, use an expressly approved alternative rather than silently treating nonattendance as acceptance.

4. Put a written ship-hold gate into the workflow

Evidence requirements matter only if the supplier’s release process recognizes them.

Have counsel review an order-specific workflow with these checkpoints:

• 1. Supplier submits: the complete evidence package, identified by system and revision.
• 2. Buyer reviews: a named technical reviewer checks results; procurement checks completeness and unresolved exceptions.
• 3. Supplier cures: missing evidence, failures, and discrepancies receive corrective action and any required retesting.
• 4. Buyer authorizes: the designated release authority issues written ship approval referencing the approved package.
• 5. Supplier releases: dispatch proceeds only after that authorization reaches the responsible shipping team.

Define the review window, submission channel, escalation contacts, and treatment of silence. Avoid a workflow in which an unanswered email or scheduled pickup becomes implicit approval.

Separate administrative omissions from test failures, but require explicit disposition of both. Any waiver should identify the affected system, missing requirement, approver, and remaining obligation.

Need help turning a reserved-system proposal into an evidence checklist? Schedule a procurement planning call with Pacific Intelligent Technologies, Inc..

5. Preserve the FAT baseline for site acceptance

FAT establishes what was demonstrated before shipment under recorded factory conditions. It does not establish successful operation after transport, installation, or integration at the destination.

Carry the approved configuration, test versions, results, and open-item register into the receiving and site-acceptance handoff. That baseline helps teams distinguish a factory exception from a subsequent change or installation issue.

Keep payment mechanics separate: an escrow holdback does not replace a technical ship-release gate. If remediation threatens the operating schedule, explore bridge GPU capacity options rather than approving incomplete evidence solely to preserve a pickup date.

FAQ: FAT evidence before reserved B300 shipment

Is a supplier’s pass certificate enough?

Not by itself if it lacks system identity, test scope, results, and exception records. Attach the evidence requirements to the order for the reserved capacity being procured.

Must procurement attend the factory?

No. Remote witnessing or documented FAT may fit the purchase, provided the agreed evidence and release controls remain intact.

Where should founders start?

Review Pacific Intelligent Technologies, Inc.’s infrastructure offerings, then ask the proposed supplier for a sample FAT plan and redacted evidence package before finalizing order requirements.