Saga Telecom

For most procurement teams, the evaluation ends at unit price and lead time. But in telecom hardware — especially at the access and aggregation layer — there's a third variable that rarely appears on the RFQ: supply continuity risk.

Chipset allocation is not linear. Marvell and CENTEC silicon, like most semiconductors, moves in cycles. During tight allocation periods, factories that don't hold buffer stock simply can't ship — regardless of how good the unit price was when you signed the PO. The cost of a delayed network rollout, a stalled OEM product launch, or a missed project deadline dwarfs any savings made at the per-unit level.

Access layer switching is often treated as a commodity purchase. The logic is straightforward: a 24-port managed switch is a 24-port managed switch. Standardize on price, move on. This logic breaks down in practice — usually at the worst possible moment.

Not all managed switches are built on the same silicon. The chipset underneath determines what the switch can actually do — not just today, but across its entire operational life. Generic and white-label switches frequently use silicon with limited feature roadmaps, minimal vendor support, and firmware that receives infrequent updates if any.

The RFQ process optimizes for the wrong variable. Unit price is easy to compare — it fits neatly into a spreadsheet column, it responds to negotiation, and it produces a clear winner. The problem is that unit price is rarely where procurement decisions actually go wrong.

The real cost shows up later: in delayed shipments when a supplier can't fulfill during a shortage, in deployment friction when firmware doesn't behave as documented, in re-qualification costs when a chipset platform reaches end-of-life. None of these costs appear on the original RFQ.

These four terms appear on supplier capability sheets constantly, and they're often used interchangeably in ways that obscure meaningful differences. For buyers planning a hardware product roadmap, the distinctions matter — they determine how much control you have, how much risk you carry, and what your unit economics look like.

OEM — Original Equipment Manufacturing

The question comes up on almost every project that involves networking hardware outside a standard office or data center environment: does this deployment actually need industrial-grade switches, or will commercial-grade hardware do the job?

The answer is not always obvious, and getting it wrong in either direction is expensive. Over-specifying adds cost without adding value. Under-specifying creates failures that are far more expensive to remediate than the equipment savings were worth.

PoE switches are sold with a total power budget number: 370W, 520W, 740W. Most deployments treat this number as the limit they’re working within. The problem is that the nameplate budget and the power actually available to connected devices are not the same number — and the gap is large enough to cause deployment failures.

Where the power goes

This is not a theoretical risk. It has happened repeatedly — in 2020, 2021, 2022, and in smaller cycles since. The pattern is consistent enough that it is worth walking through what actually occurs at the project level when chipset allocation tightens, so that procurement teams can assess their own exposure before the next cycle hits.

The scenario

OEM switch agreements are not all equivalent. The contract terms, the supplier relationship, and the technical depth behind the customization capability vary enormously between suppliers who describe themselves using the same language. These five questions separate suppliers who can actually deliver on OEM commitments from those who are rebranding catalogue products with a label change and calling it OEM.

1. Who owns the firmware roadmap, and what is your update cadence?