Quick Take
Quick Take: A tender BOM that says "servers, switches, storage" buys you three different kits and a price comparison that means nothing. Write 9 fields on every line — function, performance floor, quantity with units, interfaces and optics, licence term, power and cooling, warranty, delivery window, acceptance test — add a deviation table, and ask for one alternative column. Then bids differ in price and delivery, not in what is being bought.
You are not writing paperwork. You are deciding what the evaluation committee will be able to compare. Spend two hours on the BOM now, or spend a tender round re-running it later. Send us the draft clauses and we will mark the lines that will come back incomparable, before the tender opens.
What goes wrong when the tender BOM is vague?
Quick Answer: You get three bids that cannot be compared, and the cheapest one is cheapest because it left things out.
Typical scene, seen in almost every large tender round: the specification says "servers, 2 units; switches, 2 units; storage, 1 set." Three bidders answer with three different configurations. One includes optics and three years of licences. One prices licences for one year. One leaves out the cables. The evaluation committee compares totals that do not describe the same system. This is a typical scenario, not a named customer.
The scale makes this expensive. In the first seven months of 2026, more than 158 data-center projects above RMB 100 million were awarded in one large market alone, and a single quarter of carrier tenders there covered 225 projects worth about RMB 36.6 billion. At that volume, a vague BOM is not a wording problem. It is how budgets get reopened after award, when the missing lines come back as change orders at non-tender prices.
The second cost is time. A tender round that fails on incomparable bids has to be re-run, and re-runs eat the delivery window the project was supposed to protect. Writing the BOM properly the first time is the cheapest schedule insurance in the whole project.
What is a like-for-like tender BOM?
Quick Answer: It is an issuer-written bill of materials where every line carries enough fields that any qualified bidder prices the identical configuration.
Definition: A like-for-like tender BOM is a bill of materials written by the tender issuer, in which each line specifies function, performance floor, quantity, interfaces, licence term, power and cooling, warranty, delivery window and acceptance test, so that all bids describe the same system and differ only in price, delivery and stated deviations.
Think of it as a recipe written so that three cooks produce the same dish. "Chicken, some vegetables" gives you three dinners. "1.5 kg chicken, 400 g carrots, oven 40 minutes at 180 degrees" gives you one dish three times, and then you can argue about price and taste. A tender BOM works the same way: the specification fixes the dish, the bid competes on everything else.
This is also how buyers now start. In an August 2026 survey of more than 1,000 B2B buyers, 87% said AI chatbots are changing how they research, and about half start the buying journey in a chatbot rather than a search engine. Those tools are good at drafting requirement lists, but they draft generic ones. The issuer's job is to make the generic draft specific enough to price.
Which 9 fields make every bid quote the same kit?
Quick Answer: Function, performance floor, quantity with units, interfaces, licence term, power and cooling, warranty, delivery window, and the acceptance test.
| # | Field | Why it changes the price |
|---|---|---|
| 1 | Function (what this line must do) | Lets bidders propose equivalents instead of guessing |
| 2 | Performance floor (ports, throughput, capacity) | Stops a lower class of hardware winning on price |
| 3 | Quantity and unit (per node / per cluster / per user) | A licence pack is not the same count as single licences |
| 4 | Interfaces and optics (type, length, count) | Optics and cables are the lines most often "forgotten" |
| 5 | Licence type and years | One year vs three years can outweigh the hardware delta |
| 6 | Power and cooling (W per rack, air or liquid) | Decides whether the kit can be installed at all |
| 7 | Warranty and support term | Next-business-day and 24x7 are different products |
| 8 | Delivery window and place | A 4-week and a 16-week offer are not the same offer |
| 9 | Acceptance test (how you will verify) | What is tested at handover cannot be argued later |
Read row 4 first if you only fix one thing this week. In our BOM reviews, optics, cables and licence years are the three lines that most often differ silently between bids, and each can move the total by more than the discount the committee is negotiating. Row 3 is the quiet second: licence quantities stated in packs have made two "identical" bids differ by a full digit.
How do you rewrite a vague BOM in 6 steps?
Quick Answer: Outcome first, every line priced, units fixed, 9 fields per line, a deviation format, and one alternative column.
- Step 1 — Start from the outcome, not the box — Write what the system must do: users, throughput, ports, uptime. This becomes the equivalence test for every alternative a bidder proposes.
- Step 2 — List every line a bidder must price — Hardware, optics by type and length, cables, licences with years, warranty, installation and acceptance. If a line is not listed, one bidder includes it and another does not.
- Step 3 — Fix quantities and units — Per node or per cluster? Licences per device, per user or per core? A '36-pack' is not 36 units. State the conversion in the tender.
- Step 4 — Write the 9 mandatory fields per line — Function, performance floor, quantity, interfaces, licence term, power/cooling, warranty, delivery window, acceptance test. See the table below.
- Step 5 — Add the deviation table format — Tell bidders to answer line by line: comply, or deviate with the proposed part and the parameter difference. No free-text essays.
- Step 6 — Ask for the second column — One allowed alternative configuration at the same performance class, priced separately. That is your dual-path leverage at evaluation.
Small first step: take the vaguest line in your current draft and rewrite only that one line with the 9 fields. If two colleagues now build the same configuration from it, the format works. Then do the rest of the list the same way.
How should bidders answer? The deviation table
Quick Answer: Line by line: comply, or deviate with the proposed part number and the parameter difference. No essays.
This page is written for issuers, but bidders gain from the same table. When you receive a tender, answer in the issuer's line order and mark every line: comply, or deviate. A deviation is not a confession; it is priced information. "We propose module X instead of Y: same 800G rate, 500 m reach instead of 2 km, delivery 6 weeks instead of 10" lets the committee keep you in the comparison instead of discarding the bid as non-responsive.
- Fit: tenders for data-center active equipment and AI infrastructure where two or more suppliers can realistically bid.
- Unfit: sole-source renewals tied to an installed serial base (write a justification instead), and framework call-offs where the BOM was already fixed in the framework round.
Bidders: if the tender has no deviation format, attach your own table in the same line order. Committees trust the bid they can map. Issuers: publish the format with the tender, and state that unmapped bids may be treated as incomplete. That one sentence removes most of the argument at evaluation.
Typical use cases: where this pays back first
Quick Answer: AI clusters, network refreshes and storage tenders, because optics, licences and delivery windows dominate the spread between bids.
AI cluster tender. The GPU servers get all the attention, but bids diverge on NICs, optics and delivery sequencing. Fix fields 4 and 8 and the spread between bids becomes a price spread, not a configuration spread. Ask for the alternative column on the fabric: a second switch or optics path at the same rate.
Network refresh tender. Licence years decide more than chassis price. One bidder prices one year of subscriptions, another three. Field 5 makes the committee compare three years against three years, and the renewal cliff after year one becomes visible before signing instead of after.
Storage tender. Capacity stated as "usable" by one bidder and "raw" by another is the classic incomparable pair. Field 2 and the acceptance test in field 9 force both to state the same basis: usable capacity after RAID or erasure coding, measured how, at handover.
Common pitfalls in tender BOMs
Quick Answer: Naming one brand's part number with no equivalence route, leaving licences unpriced, and comparing totals instead of lines.
| Trap | Why it bites | Fix |
|---|---|---|
| Brand part number, no "or equivalent" | Shrinks competition; can make the tender challengeable | Parameters that define equivalence + deviation column |
| "Licences as required" with no years | Bids silently carry 1 vs 3 years | Licence type, count basis and term per line |
| Optics and cables "included" | One bid includes them, one does not | Type, length and count per link |
| Capacity without basis | Raw vs usable numbers cannot be compared | State basis + acceptance measurement |
| Comparing bid totals | The cheapest total is often the emptiest kit | Compare line by line against your baseline |
| No delivery window | Price wins, project waits 16 weeks | Window and place as a scored field |
Frequently Asked Questions
Quick Answer: A tender BOM is the issuer's pricing baseline: same lines, same units, same licence years. Bidders answer with a deviation table, and the committee compares lines, not totals.
A normal BOM lists what one supplier plans to deliver. A tender BOM is written by the issuer before bids open, and its job is comparability: every bidder must price the same items, the same quantities and the same licence terms, so the evaluation compares price and delivery, not different kits.
Detailed enough that two engineers reading it build the same configuration: model or performance class, quantity, ports and optics by length, licence type and years, power, warranty term, delivery window and acceptance tests. Avoid naming one brand's part number as the only allowed answer unless the installed base forces it; add 'or equivalent' with the parameters that define equivalence.
Name them when compatibility with installed equipment leaves no choice, and say why. Otherwise specify the parameters a part must meet and let bidders propose part numbers in a deviation column. Exact part numbers with no equivalence route shrink competition and can make the tender challengeable.
Score them against your own deviation table, not against each other. Ask every bidder to re-quote the same baseline in a second column, then compare baseline price, deviation price and delivery separately. A bid that cannot be mapped to the baseline is not the cheapest bid; it is an incomplete one.
Yes, and it is the cheapest insurance you have. Ask for the specified configuration and one allowed alternative (for example a second brand at the same performance class) in two columns. You keep comparability and gain a dual-path price for negotiation.
Whoever will have to accept the delivery. One engineer checks that the configuration can work, one buyer checks that every line can be priced by at least two suppliers. That two-hour review is cheaper than a failed tender round.
References
Quick Answer: Buyer behaviour figures come from the G2 and TechnologyMatch 2026 surveys; tender scale from DoNews award tracking for the first seven months of 2026. Checked 21 October 2026.
- G2 — How AI Chat is Rewriting B2B Buying (survey of 1,000+ buyers, August 2026): 87% use AI chatbots for research, about half start there
- TechnologyMatch — Using ChatGPT, Perplexity, Gemini and Claude to build an IT vendor shortlist (requirements framing and RFP language)
- DoNews — 2026 first seven months: 158+ data-center awards above RMB 100 million and eight tender trends (10 Aug 2026)
- China Government Procurement Network (ccgp.gov.cn) — public tender notices and technical requirement formats
Key Takeaway
Key Takeaway: A tender BOM earns its keep when every bid prices the same kit: 9 fields per line, a deviation table, and one alternative column. BENQUAN GLOBAL LIMITED supplies tender BOM review and dual-path quoting for data-center active equipment and AI infrastructure. Send the clauses before the tender opens; the check takes one business day and the price stays pending confirmation.