How to Allocate Installation and Commissioning Duties on Reserved B300 Orders

A buyer reserved a Supermicro HGX B300 system for a new AI deployment. The equipment reached the facility on schedule, but deployment stopped at the loading dock. Facilities believed the supplier would validate floor loading and complete the power connection. The supplier expected energized circuits, an approved coolant loop, and a cleared installation path before arrival. Neither party had contracted for coolant fill.

The purchase order specified the system configuration and delivery location, but not who owned the work between delivery and acceptance. The result was not a hardware shortage. It was an avoidable responsibility gap.

Procurement can prevent this outcome by attaching a site-readiness, installation, commissioning, and handoff matrix to every reserved B300 order.

Divide the deployment into explicit work packages

Do not use “installation included” as a catch-all. Break the deployment into work packages with one accountable party for each task.

At minimum, the matrix should cover:

• Structural review, floor-loading approval, and installation-path clearance
• Rack location, anchoring requirements, and physical security
• Utility-side power drops, breakers, receptacles, grounding, and energization
• Facility cooling capacity and coolant distribution infrastructure
• Coolant specification, flushing, fill, leak testing, and fluid disposal
• Receiving, unpacking, damage inspection, and packaging retention
• Rack-and-stack work, cabling, labeling, and network connections
• Firmware, management-plane, and cluster-software baselines
• Initial power-on, diagnostics, burn-in, and issue logging
• As-built drawings, serial-number records, test reports, and operational handoff

For each line, name the responsible party, the approving party, the required completion date, and the evidence that proves completion. “Buyer” and “supplier” may be too broad; identify whether facilities, the general contractor, an electrical subcontractor, an integration team, or the equipment supplier owns the task.

Teams still defining the supply path can review Pacific's reserved infrastructure capacity options before converting a capacity discussion into a purchase order.

Make site readiness a dated buyer deliverable

Reserved capacity does not eliminate buyer dependencies. The purchase order should turn those dependencies into dated, verifiable deliverables.

A site-readiness schedule should state when the buyer must provide:

• An approved room layout and equipment position
• Certified floor-loading capacity and a cleared delivery path
• Energized, tested power at the specified voltage and connector type
• Cooling interfaces that meet the supplier's documented requirements
• Network drops, addressing information, and access credentials
• Site access, safety orientation, escorts, and working-hour permissions
• Any permits, inspections, or landlord approvals under buyer control

Require a readiness package before shipment or before the supplier dispatches installation personnel. That package might include photographs, electrical test results, coolant-loop records, drawings, and a signed checklist.

The supplier should have a fixed period to review the package and identify deficiencies. Silence should not create an indefinite assumption that the site is ready.

Assign physical installation and commissioning separately

Installation and commissioning are related, but they are not the same obligation.

Installation generally includes receiving support, positioning, rack work, power and network cabling, cooling connections, and visual inspection. Commissioning begins when the installed system is energized and checked against an agreed startup procedure. It may include firmware verification, management-controller access, thermal observation, accelerator discovery, diagnostic workloads, burn-in, and generation of a commissioning report.

The order should state who supplies:

• Lifting equipment, rigging, tools, cables, hoses, fittings, and consumables
• Qualified electrical or mechanical labor
• Coolant and the approved fill procedure
• Remote or on-site technical personnel
• Burn-in software, test data, and monitoring access
• Replacement labor when an installation defect must be corrected

Do not confuse this assignment with acceptance-test design. Acceptance criteria determine whether the buyer must accept the system. The responsibility matrix determines who performs the physical and technical work needed to reach that decision point.

Define handoff evidence, not just a handoff meeting

Commissioning is not complete merely because the system powers on. Define the documentation package that transfers operational control to the buyer.

A useful handoff package for a Supermicro HGX B300 deployment can include:

• Installed-system and rack elevations
• Component serial numbers and asset labels
• Power, network, and cooling connection records
• Firmware and software version baselines
• Diagnostic and burn-in results
• Open-item and exception logs
• Administrator access transfer records
• Operating, shutdown, and escalation procedures
• Signed confirmation of training or knowledge transfer

Name the party that compiles the package and the buyer representative authorized to receive it. Also establish a short correction period for incomplete records. This keeps paperwork defects from leaving the system in operational limbo.

Organizations that need interim infrastructure while preparing a permanent deployment can also examine Pacific's bridge-capacity approach.

Allocate delay by cause and control

A responsibility matrix should connect missed tasks to schedule consequences without turning every delay into a dispute.

Use a cause-and-control framework:

• Buyer-caused delay applies when a documented buyer prerequisite is late or materially nonconforming.
• Supplier-caused delay applies when supplier labor, tools, documentation, or contracted commissioning work is unavailable or defective.
• Shared delay applies only when both parties independently prevent progress.
• Excusable delay should be limited to defined events outside the reasonable control of either party.

Require prompt written notice identifying the blocked task, evidence of the condition, mitigation steps, and the projected schedule effect. Any extension should correspond to the actual critical-path impact, not automatically reset the entire deployment schedule.

For help turning reserved capacity into an executable responsibility schedule, book a 30-minute procurement discussion with Pacific Intelligent Technologies, Inc..

FAQ

Should the supplier always own coolant fill?

No. Ownership depends on the facility design, coolant specification, equipment boundary, and available qualified labor. The order should identify who supplies the fluid, who approves it, who fills and tests the loop, and who bears responsibility for contamination or leaks caused by that work.

Can acceptance occur before documentation handoff?

Only if the contract deliberately separates technical acceptance from administrative closeout. Otherwise, specify the required handoff documents as a condition of completion while keeping the underlying acceptance criteria clear.

What should procurement finalize before releasing shipment?

Confirm the responsibility matrix, readiness evidence, installation dates, site-access rules, commissioning procedure, handoff package, and delay-notice process. Procurement teams exploring deployment options can review Pacific Intelligent Technologies, Inc. infrastructure services and available capacity pathways before finalizing the order.

The core rule is simple: break the deployment into named work packages, make site readiness a dated buyer deliverable, assign installation and commissioning separately, require a handoff package, and allocate delay by cause and control. That is how a reserved B300 order stops dying at the loading dock.