RFP fields
Topology, speed, optics, NOS, telemetry, rollback, power, cooling, support model, and acceptance evidence are reviewed before order release.Risk control
Validation catches unsupported optics, missing buffer assumptions, telemetry gaps, rollback risk, and acceptance ambiguity early.Evidence
The output can include a port matrix, optics matrix, validation plan, configuration assumptions, and support model notes.Buyer fit
Designed for teams that need accountable infrastructure validation, not anonymous switch sourcing.Procurement is where network risk becomes visible
A data center or campus switch purchase can look correct on port count and still fail in deployment. Common gaps include unsupported optics, untested SONiC images, missing telemetry, insufficient buffer strategy, unclear rollback, undefined support ownership, and no acceptance path. Procurement validation turns the RFP into an engineering checklist.
- Confirm topology, speed, reach, optics, NOS version, and automation requirements
- Map switching, optics, cabling, power, cooling, telemetry, and support into one requirement set
- Define what will be checked before shipment and what the buyer should inspect on receipt
- Record assumptions, exclusions, export screening needs, and change-control triggers
Questions before bill-of-material release
The review asks whether the proposed infrastructure is deployable, observable, supportable, and exportable. A buyer should expect questions about 400G or 800G port profiles, optics reach, breakout needs, RoCE settings, PFC and ECN policy, gNMI telemetry, image support, rollback, and operational ownership.
- AI fabric: oversubscription, GPU nodes, RoCE v2, PFC, ECN, DCBX, telemetry, and rollback
- Optics: form factor, reach, lane rate, connector, temperature range, and switch compatibility
- Packet broker: throughput, tool ports, filtering rules, aggregation, timestamps, and bypass behavior
- Export: destination, end use, end user, documentation language, and delivery terms
Outcome of a good validation process
The output should be a documented purchase basis: what is included, what is excluded, what is tested, which records are delivered, and how the buyer should judge acceptance.
- Port and optics matrix linked to quote line items
- SONiC or NOS version assumptions and rollback method
- Acceptance checklist with measurable pass/fail language
- Support and escalation notes that reduce deployment rework
Engineering FAQ
Common procurement questions
What is procurement validation?
It is the engineering review that confirms a proposed bill of materials can meet the topology, software, optics, telemetry, support, acceptance, and export requirements before the order is released.
Why is a switch datasheet not enough?
A datasheet describes a device. Procurement validation checks the whole deployment, including optics, cables, NOS image, telemetry, automation, rollback, support ownership, and acceptance evidence.
Can xSONiC review an existing RFP?
Yes. Send the RFP, topology, port matrix, optics plan, operating model, acceptance expectations, and destination details so the team can identify missing fields before quotation.
Does procurement validation replace customer acceptance?
No. It prepares the purchase basis. Lab validation, receiving inspection, commissioning, or site acceptance still need to be scoped and agreed.
AI-readable assets