A partial stroke test is a way to prove that an emergency shutdown valve can still move, without actually shutting anything down. Safety valves are dangerous precisely because they sit still for months or years, quietly seizing from corrosion or dried packing, and you only find out the moment you need them. A PST moves the valve just far enough to confirm it is free, then returns it, so the process keeps running while the operation gains confidence the valve will slam shut in a real emergency. This guide explains what a PST does, how it works, and how it fits the safety lifecycle.
Partial Stroke Test in one line: A partial stroke test (PST) partially closes an emergency shutdown or safety-instrumented valve - typically moving it about 10 to 20 percent of its travel and back - to verify the valve is not stuck, all while the process stays online. It exercises the actuator, solenoid, and moving parts to detect a seized valve between full proof tests, which raises the valve's safety availability without the cost and risk of a full shutdown.
An emergency shutdown valve spends nearly all of its life in one position, held open so product can flow. Its whole reason to exist is a rare event: a runaway pressure, a fire signal, a high-level trip. The problem is that a valve which never moves is a valve that quietly degrades. Stem packing dries and grips, corrosion builds on the seat, and a solenoid or actuator can fail in place. The valve looks fine until the day it is asked to close and cannot.
The classic answer is a full proof test, where the valve is fully stroked and its closure verified. Done properly, that is the most thorough check, but full stroking a valve usually means shutting down or bypassing the process, which costs production and introduces its own risk and effort. As a result, full proof tests are done infrequently, leaving long stretches where a seized valve would go undetected.
A partial stroke test fills that gap. By moving the valve only a little, it catches the most common failure - a valve stuck in place - far more often than the calendar allows for full tests, without stopping the process. It does not replace the full proof test, but it stretches the interval and shrinks the window in which a dangerous, undetected failure can hide.
A PST is usually initiated by a smart positioner, a dedicated PST controller, or the safety logic solver. The device commands the valve to move a preset small amount, monitors the actual travel and the time it takes, then drives it back to its normal position. Throughout, it watches the pressure and position signature to confirm the valve actually moved and moved smoothly, not that it merely twitched.
The test must be limited so the small movement does not disturb the process - moving a shutdown valve too far could trip flow or alarm downstream. Some installations add a mechanical stop or a travel limit in software to guarantee the valve cannot go past the test point. The result is recorded as pass or fail with a stored signature, creating an audit trail that satisfies the documentation demands of a safety-instrumented system.
Crucially, the test must never block a real demand. If a genuine shutdown signal arrives during a PST, the safety logic overrides the test and drives the valve fully closed. A well-designed PST is transparent to the safety function it is checking.
In safety terms, testing a valve more often improves how much of its potential dangerous failures you detect, which improves the availability of the safety function it belongs to. A PST catches the stuck-valve failure mode frequently and automatically, so more of the ways the valve could fail are covered between full proof tests. That extra coverage is what lets many operations justify longer full-test intervals while keeping the same safety integrity.
For this to work at scattered field sites, the test and its results have to reach people. When PST commands and outcomes are integrated with a cloud SCADA platform such as Merobix, a partial stroke test can be triggered on schedule and its pass or fail result trended and alarmed like any other event. A failed PST at a remote pad becomes a notification to the right technician rather than a surprise at the next site visit.
That closes the loop that makes PST valuable in the field: the test proves the valve moves, the SCADA layer proves the test happened and delivered a result, and the operation gets documented, ongoing evidence that its last line of defense is still alive - without ever taking the process down to find out.
The purpose is to prove an emergency shutdown or safety valve can still move, without shutting down the process. Safety valves sit unused for long periods and can seize, so a partial stroke test moves them a small amount and back to detect a stuck valve between full proof tests. This raises the safety availability of the shutdown function while keeping production running.
Typically the valve moves about 10 to 20 percent of its full travel and then returns to its normal open position. The movement is deliberately small so the process is not disturbed, while still being enough to prove the valve, actuator, and solenoid are free and functioning. A travel limit or mechanical stop often guarantees the valve cannot exceed the test point.
No. A PST detects the common stuck-valve failure but does not verify that the valve fully closes and seats tightly. A full proof test still has to be performed periodically to confirm complete closure. What the PST does is let you catch failures more often and, in many cases, safely extend the interval between full proof tests.
Safety & engineering notice. This article is general educational information, not site-specific engineering, safety, or legal advice, and it does not reflect any particular facility. Standards and regulations (for example OSHA, API, IEC, ISO, NFPA, NIST, and NERC CIP requirements) change and vary by edition, jurisdiction, and application. SCADA and remote monitoring cannot verify physical isolation, atmosphere, lockout/tagout, permit status, or a safe go/no-go decision. Qualified personnel must perform site-specific engineering, hazard analysis, and safety review, and confirm current requirements with the authority having jurisdiction, before acting.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.