API 14B function testing for surface-controlled valves

API RP 14B provides the recommended framework for subsurface safety valves (SSVs) and the surface control systems used on surface-controlled wells. It links valve design, sensing, control logic, actuation and documented testing into one well-control package.

Function testing goes beyond a pressure or leak check. It demonstrates that a simulated well-control signal is detected, interpreted and carried through to the intended valve closure, with objective evidence that every part of the safety response performed as specified.

Scope and purpose

API RP 14B covers SSVs and associated surface-control equipment for wells controlled from the surface, including actuated safety valves and the systems that command them. Its scope includes design, testing, operation and documentation rather than providing a universal field procedure for every installation.

The terminology matters. A surface-controlled well is a well whose well-control functions are operated from the surface. A surface-controlled subsurface safety valve, or SCSSV, is a specific subsurface device actuated through a surface control line. Equipment boundaries and responsibilities should therefore be stated clearly in the test package.

What function testing proves

A function test examines the complete cause-and-effect chain. Testers simulate the approved abnormal-flow or abnormal-pressure condition, verify the input and set points, confirm transmission of the command, observe actuator movement and valve closure, and record the result. Depending on the design, the command may be electrical, hydraulic, pneumatic or a combination.

Static pressure testing, a seat-leakage test or an actuator test may be necessary without proving automatic operation. Conversely, a closure signal alone does not demonstrate adequate seat integrity. The approved API 14B sequence should combine functional response, pressure-boundary and leakage checks with post-test operability and reset arrangements.

Testing may also follow installation, overhaul, modification, recalibration or a change to control components. Frequency should reflect the current standard, manufacturer instructions, equipment condition and the site risk program.

Signals, valves and control logic

The sensing and logic package may include wellhead pressure and flow sensors, a logic controller, alarms, an emergency shutdown function and a surface control panel. Correct response depends on calibration, wiring or hydraulic continuity, stored set points, software configuration and the final actuator. Each interface needs a defined owner in the test script.

Broader technical reference resources can help teams map terms such as set pressure, pilot operation and fail-safe closure, but the purchased API document and manufacturer instructions remain the governing references. Decisions should follow the applicable edition, approved well-control program and site operating limits.

Comparing the main test scenarios

Test activities should be matched to the failure they are intended to detect. The comparison below provides a practical evidence framework; exact procedures, acceptance criteria, test pressures and response times must come from the applicable edition and approved test plan.

Test activity	Primary objective	Typical evidence
Simulated well-control event	Verify sensing, logic and command transmission	Simulated input, set points, timestamps and command status
Valve closure and timing	Confirm actuator movement, seating and required response	Valve-position indication, feedback and elapsed time
Pressure and seat leakage	Check the pressure boundary against leakage criteria	Test medium, pressure, duration and measured leakage
Post-test operability	Confirm the required valve condition and reset sequence	Functional result, instrument readings and authorised release

Together, these checks support a defensible chain of evidence. A valve that closes but leaks may still fail the pressure boundary; a tight valve that receives no command has not demonstrated the automatic function. Deviations require formal disposition before the equipment or well is accepted.

Building an Australian test program

In Australia, API 14B commonly enters projects through engineering specifications, procurement packages and well-control philosophies rather than standing alone as legislation. Onshore obligations are administered by the relevant state or territory, while offshore safety arrangements operate within the National Offshore Petroleum Safety and Environmental Management framework. Teams in Perth, Brisbane and Adelaide should reconcile API evidence with the approved well-control program, applicable AS/NZS requirements and work-health-and-safety laws adopted from the Safe Work Australia model.

Project teams must also plan for practical delivery. Physical standards shipments may involve GST, customs clearance and freight, whereas a digital PDF is available immediately and creates no physical consignment. Purchasers should retain invoices and confirm their tax obligations. The store’s multi-currency options and major payment methods suit Australian buyers, while guidance on using the code helps teams check edition, revision and document-control needs before deployment.

Preparation and test records

A controlled test package should be ready before tools or test media reach site. It should assign competent personnel, isolate hazards and link every step to an acceptance criterion.

Readiness checks should cover:

• The applicable standard edition and any addenda.
• Equipment tags, calibration status and test boundaries.
• The cause-and-effect diagram and approved procedures.
• Barriers, communications and test-media controls.

The resulting record should include:

• Simulated inputs, set points and timestamps.
• Actuator movement and valve-position indication.
• Pressure, leakage results and test duration.
• Deviations, approvals and return-to-service status.

Results should be traceable to the serial number, well, operating condition and personnel involved. Unresolved discrepancies belong in the well-control deviation process, not in informal notes at the end of a shift.

Obtain the standard and brief the team

Document Bays sells downloadable PDF copies of industry standards and engineering codes, including API publications. Search the catalogue for API 14B, verify the title and edition, and check whether the project contract requires a particular revision, addendum or amendment.

Make the purchase part of the project workflow: register the file under document control, limit access to authorised users, brief the well-control team and link acceptance criteria to the current site procedure. Immediate download supports crews working across Perth, Brisbane, Adelaide and remote Australian facilities without waiting for physical delivery. Order the correct copy, schedule the briefing and prepare the function-test package before equipment acceptance.