API 6D and valve maintenance

1. What API 6D governs

API 6D belongs mainly to the manufacturing and acceptance stage of a pipeline valve. It supports a defined basis for supplying and accepting that valve.

That scope matters because acceptance is a controlled snapshot. It describes evidence gathered before service, not every condition the valve will face later.

The standard should therefore appear clearly in procurement and handover records. The record should identify the applicable document edition and the accepted valve configuration.

For the wider life-cycle view, read our valve integrity management guide. It separates design, acceptance, operation, testing and maintenance evidence.

2. What API 6D does not prove

A supplied valve can meet its acceptance basis and later deteriorate in service. Wear, contamination, corrosion, movement history and service conditions can change its behaviour.

Factory acceptance does not prove that an installed valve closes fully today. It also does not confirm present seat leakage, stem sealing or operating torque.

Pressure rise, continuing flow and noise are useful screening signs. They suggest a possible problem but do not confirm valve condition or cause.

A suitable in-service test must confirm the required function under recorded conditions. The API 598 acceptance guide explains a related factory-test boundary.

3. Where the maintenance interval comes from

API 6D does not provide one maintenance calendar for every installed valve. The operating organisation must build a defensible interval from relevant evidence.

1. Identify the valve duty and consequence if its function fails.
2. Review service conditions, movement history and earlier test results.
3. Apply relevant regulation, site procedures and current OEM guidance.
4. Set review triggers for changes in leakage, movement or external condition.
5. Record who approved the interval and what evidence supported it.

Industry practice includes cycling valves at least twice yearly to reduce seizing risk. This is reported practice, not a universal API 6D requirement.

Operations permission, valve condition and OEM limits still govern each movement. Our ASME B31.8 overview explains how operating procedures fit this decision.

4. Build evidence around the installed asset

Operators typically evidence maintenance decisions through a traceable record for each critical valve. The record should connect identity, duty, inspections, tests, work and follow-up actions.

Keep factory evidence and field evidence in separate fields. This prevents an acceptance result being mistaken for a current condition statement.

1. Keep the purchase and acceptance basis linked to the valve identity.
2. Record each in-service test method, boundary, conditions and result.
3. Separate screening observations from confirmed defects.
4. Trend movement, leakage and repeated maintenance findings over time.
5. State the next action when evidence is incomplete or conflicting.

Our ISO 5208 leakage guide explains how class-based acceptance evidence should be read.

5. Use the standard without overstating it

The sound question is not whether API 6D covers maintenance completely. It is which life-cycle evidence API 6D contributes, and which evidence must come elsewhere.

Use the standard text for its exact requirements and definitions. Use regulators, site procedures and OEM documents for the applicable operating context.

If a valve shows changing condition, assess the installed asset directly. Our field services cover surveys, controlled treatment and retesting where the valve is suitable.

Any treatment recommendation needs clear gates first. Injection fittings must be in good condition, the design and service must suit injection, OEM guidance applies, and operations must permit the work.