A valve integrity management programme identifies every valve, ranks its duty and risk, records condition, plans suitable tests and tracks action. It uses per-valve evidence to find deterioration early and prove whether important isolation functions remain available.
Valve integrity management for pipelines
Turn surveys, tests and service records into defensible valve decisions.
A programme connects valve condition to pipeline risk
Valve integrity management is more than a list of maintenance visits. It creates evidence that each important valve can perform its required duty.
That duty may include flow control, emergency isolation, sectionalising or safe maintenance isolation. Different duties need different evidence and response times.
The programme begins with a complete asset picture. It then combines criticality, current condition, test history and operating context.
Failure data helps explain why this work matters, but it cannot set local priorities alone. The source is the published study Risk-Based Approach Toward Pipeline Valve Integrity Management, from Valve World (read the study at valve-world.net). It covered upstream and midstream facilities. Passing valves formed 61 percent of faults, while seized valves formed 28 percent in that study population.
Those distributions vary by population. External leakage, service conditions, valve types and inspection methods can change the local result. Use the figures as context, then build decisions from your own survey evidence.
Our passing valves pillar explains internal seat leakage. The hard-to-operate valves pillar covers torque and movement problems.
Start with a survey, not a maintenance assumption
A survey provides the baseline for every later decision. Without it, teams may service accessible valves while missing critical or deteriorated ones.
The first survey should identify each valve and capture the evidence available. Common fields include the following items.
- Asset identifier, location, valve type, size and service duty.
- Isolation role, normal position and operational consequence of failure.
- Nameplate details, OEM information and known pressure or temperature limits.
- Stem, body, bonnet, fittings, actuator and gearbox condition.
- Travel result, torque observation and position indication where measurement is permitted.
- External leak screening, seat test status and the method used.
- Existing cleaner, lubricant or sealant history, where records exist.
- Access limits, chamber condition, operating restrictions and safety concerns.
Pressure rise, flow indication and noise can screen for passing. They do not prove the diagnosis. Confirmation needs an approved seat test suited to the valve arrangement.
Likewise, full travel does not prove tight shut-off. Position, operability, seat integrity and external containment are separate evidence fields.
See what a valve condition survey covers. Networks with poor history can also use the unknown-history baseline guide.
Give every valve a record that survives staff changes
A programme depends on traceable per-valve records. A network total cannot show which valve repeatedly passes, stiffens or loses an injected seal.
Each service or test entry should record what was observed, what was done and what changed. Keep measured values separate from judgement.
- Identity and duty. Use one stable asset identifier and describe the required function.
- Operating context. Record service, valve position, line condition and relevant restrictions.
- Inspection evidence. Note the leak path, movement, fittings, corrosion and other visible condition.
- Test evidence. Record the test method, boundary conditions, result and acceptance basis.
- Maintenance action. Name the product category, equipment, controlled quantity and staff involved.
- Response. Record torque change, pressure response, leakage result and any stop-work event.
- Decision. Set the next inspection, test, treatment, isolation or replacement action.
Trend fields matter because deterioration can begin before failure. Rising torque, shorter seal life or repeated seat leakage can move a valve into a higher review tier.
Records also prevent temporary controls becoming forgotten permanent arrangements. Any injected seal needs a clear owner, monitoring trigger and future decision.
Our per-valve service records guide gives a practical field structure. Turning records into replacement forecasts explains how trends support planning.
Standards leave an important cadence decision with operators
Standards describe different parts of the valve life cycle. They do not provide one universal maintenance interval for every installed pipeline valve.
API 6D addresses manufacture and acceptance. API 598 provides valve inspection, pressure-testing and allowable leakage criteria. ISO 5208 defines leakage rate classes and corresponding test requirements. These documents do not replace an operating programme for each installed asset.
ASME B31.8 requires operating and maintenance procedures but does not prescribe one universal exercise or closure-test interval for every installed valve. Operators must set defensible intervals using applicable regulation, valve duty, risk, history and OEM guidance. That creates a real cadence gap rather than permission to avoid testing.
In Indian city gas distribution, PNGRB T4S sets sectionalising valve spacing limits. It also sets annual tests for regulators, slam-shut valves and relief valves. It remains silent on a universal interval for mainline ball valves.
The operator must therefore build a defensible interval from several inputs. Common inputs include valve duty, consequence, service severity, OEM guidance, failure history and evidence quality.
Industry practice includes cycling valves at least twice yearly to reduce seizing risk. This is reported practice, not a universal rule. Operations permission, valve condition and OEM limits still govern every exercise.
Read the ASME B31.8 maintenance overview and PNGRB T4S gap guide for the boundaries. Standards compliance and valve readiness are related, but they are not identical.
Use criticality to decide where evidence must be strongest
Criticality ranks the consequence of failure alongside the chance and detectability of deterioration. It directs inspection effort without declaring low-ranked valves unimportant.
A practical review considers several questions. The answers should come from operations, engineering and safety, not maintenance alone.
- What happens if the valve cannot close, open or contain pressure?
- Does another independent isolation point exist, and is it proven?
- Could failure increase release, downtime, exposure or emergency response difficulty?
- How often does the valve move, and when was its function last confirmed?
- Does its service increase fouling, wear, corrosion or seal compatibility concerns?
- Is the evidence current, measured and repeatable, or only based on position indication?
- Can the valve be accessed and treated safely under present conditions?
Criticality does not diagnose a fault. It sets the urgency and evidence standard for confirming condition.
A high-consequence valve with poor records may need an earlier survey. A lower-consequence valve with a clear adverse trend may also need prompt action.
The valve criticality guide develops this principle. The isolation readiness guide focuses on evidence for emergency duty.
Design the programme as a repeating control cycle
A useful programme repeats the same core cycle while allowing valve-specific intervals. It keeps screening, confirmation, maintenance and acceptance clearly separated.
- Define scope. Build the asset register and assign each valve its required duty.
- Set criticality. Rank consequence, condition uncertainty and available isolation.
- Survey condition. Inspect the valve, fittings, operator, access and visible pressure boundary.
- Plan tests. Choose methods that confirm movement, seat integrity or external containment as required.
- Select treatment. Use cleaner, lubricant or sealant only after design, fitting, service, OEM and operational gates pass.
- Control execution. Stay within equipment and fitting ratings, watch pressure response and apply stop-work conditions.
- Verify acceptance. Repeat the approved test and compare evidence with the defined acceptance basis.
- Record and review. Update the per-valve history, trend changes and set the next action.
In-service treatment is not possible for every valve. Severe damage, unsafe fittings, unknown compatibility or poor access may require isolation or replacement.
The programme should show overdue actions and unresolved uncertainty. Hiding missing data behind a green status weakens operational decisions.
Management review should examine trends, repeated failures and evidence gaps. It should also confirm that temporary repairs remain monitored, clearly owned and linked to dated follow-up actions.
Our valve survey and field services can support this cycle. The knowledge hub provides focused guides for diagnosis, injection, records and standards.
Valve integrity programme questions, answered directly
What is a valve integrity management programme?
It is a controlled system for identifying valves, setting criticality, surveying condition, planning tests, recording work and acting on trends. The programme connects evidence to maintenance and isolation decisions.
How often should pipeline valves be tested?
No single interval suits every valve. Applicable regulation and code requirements come first. Operators should then set valve-specific intervals using duty, risk, service, history, test evidence and OEM guidance.
Why are per-valve records necessary?
Network totals hide repeated faults and weak isolation points. Per-valve records show torque, leakage, treatment response, test results and overdue actions for each asset.
Does a closed position prove valve integrity?
No. Position shows travel, not seat tightness or pressure-boundary condition. Seat testing, external leak checks and condition evidence are separate parts of integrity assessment.
Send your network scope. An engineer replies within 24 hours.
Include valve count, service, locations, records available and priority isolation duties.