Valve Data Sheets: Purpose-Specific, Not Universal

Valve data sheets work best as purpose-specific engineering records, not as one universal form for every valve. Before anything else, define the decision the sheet must support: initial procurement, replacement, spares, certification, or conversion from manual operation to an actuator. That choice controls which fields are mandatory and prevents a general template from omitting critical requirements or locking the supplier into an unnecessary construction.

1. Data-Sheet Purpose

1. Assign one primary purpose to the sheet: procurement, replacement, spares, certification, or actuator conversion.
2. Identify the valve population covered: one tagged valve, a group with identical service requirements, or a standardized family.
3. Record any secondary purposes without allowing them to dilute the primary requirement.
4. Mark fields as required, optional, or supplier-proposed according to that purpose.

A procurement sheet must communicate the service and required performance while leaving room for technically acceptable alternatives. A replacement sheet needs the installed interfaces and operating duty needed for interchangeability. A spares record must identify replaceable assemblies and the configuration to which they apply. A manual-to-actuated conversion sheet must capture operating load, available utilities, mounting interfaces, required action, and the required operating result.

Gate check: Do not move on until the primary purpose and covered valve population are stated at the top of the sheet.

2. Applicable Reference Selection

1. Identify the owner, client, industry, and jurisdiction that govern the project.
2. Check whether the project specification already mandates a data-sheet format.
3. Review NORSOK I-001, particularly Annex C, when its instrumentation framework is applicable.
4. Review the general valve data-sheet material associated with API 6D edition 2008 or ISO 14313 when the valve and project scope fall under those documents.
5. Evaluate the Shell MESC system only when it is part of the owner or procurement specification.
6. Use ISA-TR20.00.01 as a comparison point for instrument data-sheet practices, not as proof that one equivalent universal valve form exists.

These references are starting documents to verify against the project requirements. A common format can improve consistency, but it does not decide which process, performance, material, certification, or lifecycle fields a particular valve requires. Record the selected reference, its stated edition when the project specifies one, and every project-specific supplement. Never transfer a requirement merely because it appears on another owner’s form.

Gate check: Proceed only when the governing project document and any reference template are identified separately; a convenient template is not automatically the governing specification.

3. Valve Population Segmentation

1. Group valves by function and service rather than placing the entire project population on one undifferentiated form.
2. Within each function, divide the population by the process conditions that change selection or construction.
3. Separate size groups and pressure groups where those divisions change interfaces, materials, testing, actuation, or procurement strategy.
4. Create a dedicated sheet for a single tagged valve when its duty or required features differ from the group.

A compact group sheet is effective when many valves genuinely share the same service basis, materials, pressure class, certification requirements, and functional duty. It becomes unsafe when group membership hides a different fluid condition, operating case, actuator requirement, or performance criterion. Large populations of identical valves may justify a traditional standardized form; smaller projects and complicated processes usually benefit from simpler type-specific sheets linked to detailed requirements.

Give every valve or valve group a systematic identifier. The identifier must connect the data sheet to the process documents, purchase record, certificates, approved deviations, installed configuration, and maintenance record. This relationship preserves the design basis without expanding every sheet into an unmanageable form.

Gate check: Confirm that every tagged valve maps to exactly one applicable data sheet and that no grouped valve has a conflicting service or functional requirement.

4. Process and Performance Basis

1. Enter the fluid and relevant fluid condition for each operating case.
2. Record the pressure and temperature information required by the project’s valve-selection method.
3. Define the valve function and the performance expected in normal, minimum, maximum, startup, shutdown, or abnormal cases that affect selection.
4. For a regulating valve, provide the flow requirements and the process conditions paired with each required flow case.
5. State the required shutoff, directionality, operating mode, and failure response when they are part of the functional requirement.
6. Perform valve selection or sizing from the completed operating cases, then record the selected nominal size as an output.

Regulating-valve sheets commonly fail when they specify a nominal size without the flow basis. Size alone does not define controllability or capacity. The engineer needs the process states that establish required flow performance; the selected construction and size follow from that duty. When a required value is not yet available, mark the responsible source document or calculation rather than inserting a placeholder that could be mistaken for an approved design value.

Keep process requirements distinct from mechanical interface data. Both are necessary, but they answer different questions: process data establishes whether the valve can perform the duty, while interface data establishes whether it can be installed and connected.

Gate check: Do not release a regulating-valve sheet until every sizing case can be traced to a defined process condition and the selected size is traceable to the sizing result.

5. Construction, Materials, and Certification

1. Translate the fluid conditions and project rules into required materials, pressure class, and certification requirements.
2. Identify which construction features are mandatory because they control safety, compatibility, installation, maintainability, or client acceptance.
3. Move preferred but nonessential details into a clearly labeled preference field.
4. Leave construction open to supplier proposals where multiple designs can meet the required service and performance.
5. Require the supplier to identify every proposed deviation or alternative against the stated requirement.

A data sheet that records too little cannot establish the required quality. A sheet that prescribes every legacy construction detail may block competitive alternatives and product improvements without improving the operating result. The useful boundary is functional: specify the result and the interfaces that must not change, then prescribe internal construction only where the project has a documented reason.

Gate check: Confirm that every mandatory construction restriction has a service, interface, certification, or project basis and that alternatives have a defined acceptance path.

6. Procurement and Technical Bid Comparison

1. Issue the same revision of the requirement set to every bidder.
2. Require each bidder to complete the offered-data fields rather than merely acknowledge the specification.
3. Compare mandatory requirements, offered construction, certification, exceptions, and lifecycle deliverables in separate columns.
4. Return incomplete operating-case responses for clarification before technical acceptance.
5. Record the accepted alternative and its engineering basis in the tag-linked data record.

The request document should permit competition in price and quality without making unlike offers appear equivalent. A clear separation between purchaser requirements and supplier data makes the comparison auditable. It also prevents an accepted supplier alternative from being lost when the purchase description is later used for replacement or spares.

Do not accept a regulating-valve offer based only on stated nominal size. Compare the offered selection against each required flow case and the specified functional behavior. For other valves, compare the offered service suitability, interfaces, materials, pressure classification, certification, and operating arrangement against the fields identified as mandatory.

Gate check: Place the order only after every exception has a recorded disposition and the accepted supplier data is attached to the correct tag or valve group.

7. Replacement, Spares, and Actuator Conversion

1. Preserve the as-purchased and as-installed configuration separately from the original requirement.
2. For replacement, compare process duty, pressure classification, materials, certification, installation interfaces, and operating behavior.
3. For spares, tie each spare description to the valve configuration and revision for which it is valid.
4. For manual-to-actuator conversion, add the operating load basis, mounting connection, required motion, available utility, control action, failure response, and installation constraints.
5. Update the central record after any rebuild, substitution, or actuator installation.

A purchase description alone is not a reliable replacement record because the installed valve may include approved deviations or later modifications. Conversely, copying the installed construction without retaining the service basis can perpetuate a poor selection. Keep requirement, offered data, approval, and installed state as related but distinct records.

An actuator conversion changes more than the operating method. The completed assembly must still deliver the required valve motion and operating result under the stated service conditions. Obtain missing loads and interface details from the valve documentation or a documented engineering assessment; do not infer them from nominal size alone.

Gate check: Confirm that a replacement, spare, or conversion can be traced both to the current installed configuration and to the functional requirement it must satisfy.

8. End-to-End Data-Sheet Verification

1. Select a representative tag from each valve type, size group, pressure group, and special-service group.
2. Trace each tag from its process requirement to the applicable data sheet.
3. Verify that the sheet contains the operating cases, mandatory materials, classification, certification, interfaces, and functional requirements needed for selection.
4. Trace the accepted supplier offer and every approved deviation back to the same tag.
5. Compare the delivered or installed configuration with the accepted supplier data.
6. Test retrieval by locating the information needed for procurement, replacement, spares, and actuator conversion without relying on undocumented knowledge.
7. Correct the template and all affected records when a required decision cannot be made from the retrieved data.

The final test is practical: another engineer must be able to identify what the valve must do, what was accepted, what was installed, and which alternatives remain permissible. Do not move on until every representative tag completes that trace without an unexplained gap.

Frequently Asked Questions