Anatomy of an Instrument Specification Package for Competitive Quoting

A weak instrument specification package costs you twice: once when vendors quote against ambiguous requirements, and again when the “cheap” bid turns out to exclude something you needed. Here’s what a package needs before it goes out the door.

The datasheet is the contract

Every instrument datasheet should unambiguously specify:

• Process conditions: normal, min/max operating, and design pressure/temperature
• Fluid properties relevant to the measurement (density, viscosity, phase, corrosivity)
• Materials of construction, including wetted parts
• Area classification and required certification (e.g., Class I Div 1/2, ATEX zone)
• Required accuracy, turndown, and output signal type
• Process connection size/rating and mounting requirements

If a vendor can legitimately quote two different products against your datasheet, it’s not specific enough yet.

Group by type, not by tag

Forty individual RFQs to forty different vendor contacts is a scheduling disaster. Group instruments by type (flow, level, pressure, control valves) so each vendor family gets one coherent package. This also makes bid comparison much easier later.

Build the evaluation criteria before the bids come back

Decide up front what “acceptable” looks like: which specification deviations are absolute rejects (wrong area classification, wrong material) versus which are negotiable (delivery lead time, minor accuracy differences). Evaluating bids without this decided in advance invites inconsistent decisions under schedule pressure.

Track exceptions explicitly

Vendors will take exceptions to your spec — that’s normal. What matters is capturing every exception in a single tracked list, evaluating each one against process requirements (not just cost), and getting sign-off on any exception before award. This is the step most likely to get rushed, and the one most likely to bite you during commissioning if it is.