How to Require Dual-Source Optics Without Breaking Reserved B300 BOM Freeze

Consider a hypothetical procurement handoff: a founder approves a reserved Supermicro HGX B300 deployment, including its associated network optics. A week before shipment, the integrator reports that the specified transceiver is unavailable. Another manufacturer offers the same advertised speed and reach. Can it ship?

Not safely on those facts alone. Matching headline specifications does not establish switch compatibility, acceptable power consumption, or interoperability with the optic at the opposite end. Yet reopening the entire BOM would defeat the schedule protection procurement intended.

The better award defines a bounded A/B optical choice before configuration freeze. Here is the procurement playbook Pacific Intelligent Technologies, Inc. recommends.

1. Define dual-source optics by optical role

For this award, dual-source optics means two qualified manufacturer/part-number pairs for the same optical role. It does not mean “equivalent optics permitted,” an approved distributor list, or two resellers supplying the same manufacturer’s part.

Define each role by its actual endpoints: switch or adapter model, port mode, link speed, fiber type, connector, reach, and breakout arrangement where applicable. These are deployment-network components; do not assume every optical role is inherent to the Supermicro HGX B300 platform itself.

For each role, freeze:

• Source A manufacturer and exact part number.
• Source B manufacturer and exact part number.
• Permitted hardware revisions and firmware/EEPROM identity constraints.
• Applicable endpoint software versions and qualification evidence.
• Whether A/B mixing across opposite ends or within port groups is allowed.

Two listed sources create an approved sourcing option, not proof that both hold available inventory.

2. Put A/B qualification before the freeze gate

Attach an Optical Role and Approved Pair Schedule to the award’s frozen BOM. Give each role a stable identifier and quantity. Reference A and B as enumerated alternatives under that role rather than silently replacing a single fixed SKU.

Set three explicit gates: evidence submission, technical approval, and configuration freeze. Assign a buyer-authorized technical reviewer and record the approval date and evidence revision.

If B lacks approval at freeze, label it “unapproved candidate,” not “approved alternate.” Its later introduction must follow the agreed change-control process.

Also freeze the selection rule: may the supplier choose either approved source, must it prefer A, or does choosing B require buyer acknowledgment? Record any price treatment in advance without assuming the two parts cost the same.

For deployment scope and reservation discussions, use the reserved GPU capacity planning page; the optical schedule should describe the network equipment actually included in that scope.

3. Require evidence beyond speed and reach

Equivalence is role-specific. Procurement should require an evidence pack that engineering can approve, not just two product sheets with similar marketing labels.

Link budget: Document transmitter and receiver limits, expected channel loss, connector and splice allowances, operating margin, and receiver overload considerations. Include environmental assumptions relevant to the deployment.

Form factor and electrical fit: Confirm module form factor, host electrical interface, lane mapping, connector and fiber compatibility, power class, and thermal limits. Physical insertion alone is not qualification.

Firmware and EEPROM identity: Record expected manufacturer identification, part and revision fields, host coding requirements, and firmware versions where applicable. A and B need not report identical identities; each must match its own approved baseline and be recognized correctly by the host.

Interoperability notes: Identify tested endpoint hardware/software, FEC settings, link training, diagnostics behavior, and sustained traffic results under stated conditions. Specify which A/A, B/B, and A/B combinations are supported. Do not infer mixed-end interoperability from separate successful tests.

Require confirmation of applicable integrator and equipment-vendor support terms. A working link is not automatically a supported configuration.

4. Treat ship-time selection as controlled execution

Suppose only B is available at shipment. If B, its revision, the endpoint configuration, and the proposed pairing are already approved, selecting it can be execution of the frozen schedule—not a reopening of freeze.

Require a shipment-specific source-selection record: optical role, selected manufacturer/part, quantities, approved evidence reference, and confirmation that the permitted pairing rules remain satisfied. Reconcile that record with the as-shipped BOM.

If neither source is available, or B arrives with an unapproved revision or identity, stop treating the decision as routine selection. Apply the agreed hold, change request, or other contractual remedy. Shortage does not authorize Source C.

Proposed language:

For each Optical Role, Supplier may furnish only the approved Source A or Source B configuration identified in the frozen schedule, subject to its selection and pairing rules. Any other manufacturer, part number, revision, or configuration outside that schedule requires prior written approval through the agreed change-control process.

Ask counsel to review this proposed contractual language, including its interaction with delivery obligations and remedies.

5. Keep the boundary narrow

This schedule answers one question: which qualified optical configurations may fulfill each frozen role?

It complements—not replaces—the broader second-source options framework. Exceptions belong in configuration-freeze change orders; shipment identity belongs in named-SKU traceability; notice timing belongs in the late-change notification SLA.

Before award, schedule a procurement working session with Pacific Intelligent Technologies, Inc. Bring the network BOM, freeze date, and proposed A/B evidence matrix.

FAQ

Does dual-source approval guarantee uninterrupted delivery?

No. Qualification and availability are separate. If hardware timing threatens the workload schedule, discuss bridge-capacity options separately; they do not satisfy the optical BOM obligation.

Must procurement require both sources in every shipment?

No. Unless the contract requires a sourcing split, an approved all-A or all-B shipment may comply. Make the rule explicit and align verification with the factory acceptance evidence requirements.

Where should founders start if the deployment scope is still unsettled?

Start with Pacific Intelligent Technologies, Inc.’s infrastructure overview, then define the reserved system and network scope before qualifying optical alternatives. Freeze only what the award actually includes.