When a valve standard revision is in ballot or publication, the immediate buyer task is not to guess what changed. It is to make the RFQ and every quotation unambiguous about which controlled documents govern the order.
API’s public Balloting System currently lists API Std 623, 3rd Edition — Steel Globe Valves — Flanged and Butt-welding Ends, Bolted Bonnets with a ballot window ending 30 October 2026. That public status is a timely reason to audit RFQ language. It is not a basis to infer requirements, declare a new edition effective, or certify a valve.
1. Put the governing edition on the RFQ cover sheet
For each standards reference, record the document number, edition, addenda or corrigenda where relevant, the date or revision used by the project, and the order of precedence. If the purchaser allows an alternative edition, say who must approve it and before which milestone.
Avoid “latest edition” where quotation comparability matters. Two suppliers can interpret it on different dates, leaving a hidden scope difference.
| Control point | Buyer instruction | Evidence to retain |
|---|---|---|
| Governing reference | State the required edition and any approved amendments | Controlled RFQ / data sheet |
| Change trigger | Define what happens if a cited document is revised | Deviation or change note |
| Scope boundary | List project-specific pressure, material, end and service requirements separately | Valve schedule and requisition |
| Supplier response | Require an explicit compliance/deviation statement against the issued revision | Quotation and deviation register |
| Release gate | Identify who approves substitutions before manufacture | Approved technical query / PO change |
2. Separate a standards reference from the valve’s actual scope
A globe-valve quotation still needs its own line-item data: tag, quantity, size, pressure class, ends, body/trim materials, service conditions, inspection and documentation requirements. A generic reference does not fill those gaps.
An XHVAL high-pressure globe valve product page can help identify a product family for discussion. It cannot establish the ordered valve’s material, rating, end connection, test result, approved drawing or conformance. Require those items in controlled order documents.
3. Make the supplier show assumptions and deviations early
Ask each bidder to state the document edition used, every assumption, every exception and whether any proposed substitution affects the valve, operator, end connection, inspection or records. If a revision becomes relevant after technical bid evaluation, use a documented change-control step; compare the issued requirement, line-item effect, cost/lead-time impact and the project approver’s decision.
4. Keep records linked to the purchase-order line
At order handover, tie the approved data sheet, general-arrangement drawing, inspection/test plan, material and test records where required, and final deviation disposition to the tag or line item. Put document revision and approval status on the transmittal.
Copyable RFQ wording
Quote against the edition and controlled documents listed in this requisition. Identify the edition used for every cited reference, all assumptions and each deviation. Do not substitute a later edition or alternative requirement without written purchaser approval. Submit the requested line-item data sheet, drawings and order-specific records with revision status. A catalogue page, image or general standards reference is not by itself evidence of compliance for this purchase order.
Before sending the RFQ
- Freeze the edition/revision field and document precedence.
- Separate standards references from line-item service and construction data.
- Require a supplier compliance/deviation statement and a controlled approval path.
For an enquiry, send the valve schedule and controlled requirements through the XHVAL contact page. A clean revision trail makes bid comparison more reliable.
Sources and claim limits
- API Balloting System publicly lists the API Std 623, 3rd Edition ballot title and dates cited above. It does not disclose the draft’s requirements; this article does not infer them.
- API Standards Plan provides public context for valve standards activity; it is not a project specification.
- XHVAL high-pressure globe valve page is used only as a first-party product-family/image source. Order-specific data must be independently reviewed.