How to specify a server for quote.
A specification is not a shopping list. It is the set of constraints that lets several people price the same thing. This is what to include, and what to deliberately leave open.
Start with the workload, not the part numbers
The first two lines of a good specification describe what the machine has to do: the application, the number of concurrent users or jobs, and the environment it joins. Everything downstream is a consequence of that, and anyone quoting can offer a better alternative when they know the intent.
A part number without intent is a dead end. If the quoted CPU is unavailable, the person quoting cannot substitute sensibly, so you get a delay instead of an option.
The eight fields that decide the quote
| Field | State it as |
|---|---|
| Quantity | Systems now, plus any planned follow-on phase. |
| Form factor | Rack units available, chassis depth limits, density needs. |
| CPU | Socket count plus core-count or frequency priority and workload. |
| Memory | Total capacity and preferred module size, or population intent. |
| Storage | Tier, interface, exact capacity per drive, drive count, protection. |
| Networking | Port count and speed, OCP or PCIe, optics in or out of scope. |
| Power | Redundancy, input voltage, kW available per rack. |
| Commercial | Delivery window, support term, and where flexibility exists. |
Mark what is open
Every field you are not certain about should be explicitly marked as open to recommendation. This is the single highest-value habit in server specification. It converts a guess — which silently narrows what can be offered — into an invitation for a better option.
State constraints the datasheet cannot know
- Rack power and cooling actually available at the destination
- Physical depth and rail requirements of the existing rack
- Firmware or management platform the fleet standardizes on
- Existing switching the system must connect to
- Compliance or country-of-origin requirements, if any
Ask for what you will need to compare
Tell the responders the format you want back: itemized configuration, lead time per line, support term pricing separated from hardware, and any alternative they would recommend. A quotation that arrives as a single total cannot be compared against one that itemizes.
Put this into a specification.
The configurator asks for exactly these fields.