Mixed-Vendor Optics BOM: What to Record Before You Request a Quote
Build a mixed-vendor optics BOM with exact hosts, ports, OEM references, link requirements, coding evidence, quantities, spares and validation status.
A mixed-vendor optics BOM should identify each link, not merely list quantities of SFP, SFP28 or QSFP modules. The buyer needs enough information to connect an exact port at Site A to an exact port at Site B, select the optical interface, request the appropriate coding and state what still requires validation.
That discipline matters when one project combines routers, switches, network interface cards, new equipment, installed equipment and several software releases. A spreadsheet with rows such as “10G LR, 40 pieces” may look complete to procurement while remaining unusable to engineering.
Build the BOM Around Link Records
Create one line record for every technically distinct link type. Combine quantities only after confirming that the endpoints, port mode, fiber path, optical specification and coding requirement are genuinely the same.
| Link record | What to capture |
|---|---|
| Endpoint A | Site, device vendor and model, line card or NIC, port and software version |
| Endpoint B | The same identity fields for the remote end |
| Interface | Data rate, form factor, exact port mode and required Ethernet or transport interface |
| Fiber path | Single-mode or multimode fiber, strand count, connector, route length and measured loss when available |
| Optic identity | Original OEM part number, requested replacement identity, wavelength or wavelength pair and reach class |
| Operations | DOM/DDM requirement, temperature range, spares, rollout group and validation status |
Start with the optical transceiver compatibility check when a host, card, port or software field is missing. Compatibility cannot be reviewed defensibly without an exact equipment identity.
Separate Host Identity From Optic Identity
Do not put the device model and transceiver part number into one ambiguous description. They answer different questions.
The host identity tells the reviewer which hardware and software must accept the module. Record the chassis, switch, router or server model; the line card or NIC where relevant; the exact port; the configured speed; and the running software or firmware version.
The optic identity tells the reviewer what physical and optical interface is being replaced or requested. Record the original OEM part number when available, the form factor, nominal data rate, wavelength, connector, fiber type and stated reach. For bidirectional optics, record both endpoints and the complementary transmit and receive wavelengths.
A shared form factor is not proof of support. An SFP-family cage may support more than one rate on one platform and only one configured mode on another. A QSFP-family port may require an explicit breakout profile. The BOM should therefore preserve the host-to-optic relationship rather than assuming that a generic label settles it.
Use Exact OEM References Without Treating Them as the Whole Requirement
An original OEM part number is valuable because it narrows the intended interface and coding profile. It does not replace a host and link review.
The same OEM optic may appear across different devices, while a device may support only a defined subset of modules under particular software releases. Vendor compatibility tools themselves are organized around device and optic combinations, which is why a quotation should not be approved from the transceiver label alone.
When no OEM reference is available, mark it as unknown. Add photographs of the installed label, inventory output or command-line evidence to the internal review package, but do not infer a final replacement identity from one partial clue.
Record the Fiber and Optical Conditions
Nominal reach is not an optical design. The BOM reviewer needs the installed path and the receiver operating conditions.
| Fiber question | BOM implication |
|---|---|
| Is the path single-mode or multimode? | Narrows the applicable interface family and connector plan |
| Is one strand or a duplex pair available? | Determines whether standard duplex, BiDi or a WDM architecture should be evaluated |
| What is the cable-route length? | Supports reach selection but does not replace a loss calculation |
| What connectors and passive devices are present? | Adds connector, splice and passive-component loss to the path |
| Is measured loss available? | Replaces part of the design assumption with field evidence |
| Could the path be very short and low loss? | Requires checking the maximum receiver-input or overload boundary |
If the project changes speed, fiber use or topology, use the optical transceiver upgrade checklist to connect the port audit, link budget, staging and rollback plan.
Make Coding a Controlled BOM Field
Coding should be associated with the exact host side of the link. “Cisco compatible” or “multi-vendor” is too broad for a procurement record.
For each endpoint, capture the vendor, platform, software version, original part number and any required module behavior such as readable DOM/DDM. Record whether the requested coding is based on a specification review, a supplier coding check, a controlled sample or previous evidence for the same host and software context.
Do not upgrade an evidence label merely because two devices share a vendor name. Coding recognition is one layer of compatibility. Port mode, interface, FEC, optical limits, connector, fiber path and the remote endpoint still have to match.
Add Quantity, Spares and Rollout Ownership
Procurement needs commercial quantities, but engineering needs to know how those quantities map to links.
Separate service pairs, one-sided replacements, lab samples, commissioning spares and operational spares. A BiDi deployment requires paired A-side and B-side quantities; a breakout assembly requires one parent end and every branch end; a mixed-vendor rollout may require distinct coding pools even when the physical optic specification is similar.
Add the required delivery sequence and site group. A pilot quantity should not be silently merged into the production quantity, because the production release should depend on the approved validation result.
Apply an Evidence Status to Every BOM Line
Use simple, reviewable states rather than one global “compatible” column.
| Evidence state | Meaning |
|---|---|
| Specification reviewed | Host, interface and link documents have been compared |
| Coding identified | The requested host coding profile is recorded |
| Controlled validation planned | A sample and acceptance method are defined |
| Controlled validation complete | The stated sample scope has a recorded result |
| Field evidence available | Evidence exists for the stated platform, software and link context |
| Hold | A critical host, optic, fiber or configuration field is still missing |
Evidence should remain scoped. A result from one switch, port and software version should not be generalized to every product in the vendor family.
Run the BOM Consistency Checks
Before sending the request for quotation, review the BOM horizontally and vertically.
Horizontally, confirm that every row forms a complete link: endpoint A, endpoint B, port modes, optics, fiber and configuration. Vertically, check that repeated part numbers use consistent specifications, that coding groups are not mixed accidentally, and that quantities reconcile with link counts and spare policy.
Also check for asymmetric descriptions. A row that fully describes Site A but calls Site B only “remote switch” is not deployment-ready. The remote port can create the same compatibility, FEC or optical mismatch as the near end.
Final Mixed-Vendor Optics BOM Checklist
- Every technically distinct link has its own reviewable record.
- Both endpoint devices, cards or NICs, ports and software versions are listed.
- Original OEM references and requested replacement identities are not confused.
- Speed, port mode, FEC and breakout requirements are explicit.
- Fiber type, strand availability, connector, route length and passive components are recorded.
- BiDi wavelength pairs and breakout branch counts reconcile in both directions.
- Coding requirements are tied to exact hosts, not broad vendor names.
- Sample, production and spare quantities are separated.
- Evidence status and remaining unknowns are visible to engineering and procurement.
- Delivery groups, site ownership and rollback requirements are recorded.
Frequently Asked Questions
Can one compatible optic part number be used across every device from the same vendor?
Not automatically. Support can vary by platform, line card or NIC, port and software release. Keep the exact host identity and coding evidence with each BOM line.
Should the BOM use the OEM part number or the compatible replacement number?
Record both when available. The OEM reference helps define the intended interface, while the requested replacement identity controls the supplied item and its coding or validation requirements.
Can all identical-speed links be combined into one quantity?
Only when their hosts, port modes, optical interface, fiber path, coding and evidence requirements are equivalent. Otherwise, keep separate rows even if the rate is the same.
How should BiDi optics be listed?
List the A-side and B-side modules separately with complementary transmit and receive wavelengths, then reconcile the pair quantities by link and spare policy.
Does a mixed-vendor link require the same optic brand at both ends?
Ethernet links do not generally require the same commercial brand merely because the brands differ, but both modules must implement compatible interfaces and each host must accept its installed module. Validate both ends rather than relying on brand symmetry.
What should be sent for a BOM review?
Send the endpoint equipment and ports, software versions, original optic references, link rates, fiber and connector details, route lengths, measured loss if available, coding requirements, quantities, spares and rollout schedule.
Turn the Spreadsheet Into a Reviewable Optics BOM
Share the mixed-vendor host list, port map, original part numbers, link requirements, fiber records, quantities and current evidence status. Axonode can help organize the requirement, identify missing decisions and prepare a qualified optics BOM before the quotation is finalized.
Review a mixed-vendor BOM
