Practical Procedure · Safety Systems Control Valve Partial Stroke Testing (PST) for Safety Valves Applies to: Emergency shutdown (ESD) valves and safety instrumented function (SIF) final elements | Equipment needed: PST-capable positioner/logic solver, position feedback monitoring, coordination with process/operations Full Stroke vs. Partial Stroke — Why PST Exists Tap a tab to see the difference between a full functional test and a partial stroke test, and why PST lets you test without shutting down. Full Stroke Test Partial Stroke Test (PST) ESD Valve — Process Running 0% → 100% → 0% process fully interrupted during test ESD Valve — Process Running ...
Get link
Facebook
X
Pinterest
Email
Other Apps
Calibration Frequency and Risk-Based Scheduling
Get link
Facebook
X
Pinterest
Email
Other Apps
-
Part 5, Chapter 3 — Calibration Frequency and Risk-Based Scheduling
Part 5, Chapter 3 · Process Instrumentation Mastery
Calibration Frequency and Risk-Based Scheduling
Risk-based scheduling isn't really a story about doing less work — it's a story about a custody transfer meter finally getting checked four times as often as a utility tank gauge that never drifts.
Live · Same Six Instruments, Fixed vs Risk-Based Intervals
Chapter 2 established what As-Found data genuinely reveals about an instrument's real drift behavior. This chapter uses that information for something practical — deciding how often each instrument actually needs to be calibrated.
Fixed Interval: Simple, But Genuinely Not Optimal
The simplest approach calibrates every instrument on the same fixed schedule — say, every 12 months — regardless of actual behavior. This is easy to manage, but genuinely wastes effort on stable instruments that rarely drift, while potentially leaving faster-drifting instruments out of tolerance for meaningful stretches between calibrations, undetected.
The Genuine Result Isn't "Less Work" — It's Better-Targeted Work
Look at the simulation above: risk-based scheduling extends the interval for low-criticality, stable instruments (genuine savings there) while dramatically SHORTENING it for the high-criticality, actively-drifting custody transfer meter — from 12 months down to just 3. The total number of calibration events across this particular population actually goes UP under risk-based scheduling, not down. The real benefit isn't a smaller total workload; it's directing that workload toward the instruments where it genuinely matters most.
As-Found Data Driving the Adjustment
Chapter 2's As-Found trend history is exactly what feeds this decision for a specific instrument — one that consistently shows minimal drift can genuinely have its interval extended, while one showing significant, worsening drift should have its interval shortened, rather than applying a generic schedule uniformly to instruments with genuinely different real-world behavior.
Factor
Genuine Effect on Interval
High criticality (safety, custody transfer)
Shorter interval, regardless of past drift behavior
High observed drift (from As-Found history)
Shorter interval — the instrument has shown it needs closer attention
Low criticality + low observed drift
Interval can genuinely be extended beyond a generic fixed schedule
Regulatory Minimums Can Override Pure Risk-Based Optimization
Custody transfer and legal-for-trade applications, echoing Weighing Systems Mastery's legal-for-trade content, may carry MANDATED minimum calibration frequencies regardless of how stable an instrument's observed drift history actually is — a genuine constraint that overrides pure risk-based optimization in specific regulated contexts.
Field Practice
A genuine, practical criticality tiering used in real risk-based programs:
Safety-critical — instruments tied to a Safety Instrumented Function or interlock. Interval driven by the site's safety documentation, not by observed drift alone.
Custody transfer / quality-critical — instruments affecting billing, product quality release, or regulatory reporting. Interval may have a genuine contractual or regulatory minimum (Part 5's own point above).
Process-critical — instruments feeding an active control loop where a bad reading causes a real process upset, but no safety or financial consequence.
Monitoring-only — instruments providing trend/awareness information with no direct control or safety function. Genuinely the safest place to extend intervals based on demonstrated stability.
Review the SCHEDULE itself periodically, not just individual instruments. A genuine annual (or similar) program review — looking across all accumulated As-Found history — catches instruments that have quietly earned a longer interval, and flags any that have started trending toward needing a shorter one, rather than leaving every interval decision frozen at its original commissioning-time assumption.
Check Your Understanding
Why doesn't risk-based scheduling necessarily reduce the total number of calibration events across a facility?
Answer: Risk-based scheduling shortens intervals for high-criticality or fast-drifting instruments while extending them for stable, low-criticality ones — if a facility has several genuinely high-risk instruments, the increased frequency for those can outweigh the savings from extending intervals elsewhere, so total events can actually increase even as risk coverage improves.
Why would a custody transfer instrument's calibration interval potentially stay fixed even if its As-Found history showed excellent stability?
Answer: Regulatory or contractual minimums for custody transfer and legal-for-trade applications can mandate a minimum calibration frequency regardless of observed drift behavior — pure risk-based optimization based on stability alone doesn't override a genuine regulatory requirement.
CHAPTER RECAP
Fixed interval calibration is simple but genuinely suboptimal — wasting effort on stable instruments while under-protecting fast-drifting ones
Risk-based scheduling adjusts intervals by criticality and observed drift, using Chapter 2's As-Found history as real input
The genuine benefit is better-targeted effort, not necessarily fewer total calibration events — high-risk instruments may need MORE frequent attention
Regulatory or contractual minimums can override pure risk-based optimization for custody transfer and legal-for-trade applications
Fault Log · Field Report Schenck Weigh Feeder — Zero and Span Drift, Two Different Root Causes Plant: Cement | System: Schenck weigh feeder, belt scale, hopper load cells | Downtime: None Symptom A Schenck weigh feeder started showing both zero drift and span drift at the same time. Two separate accuracy problems showing up together made this a two-part investigation from the start — zero and span errors don't always share the same root cause, even when they appear together. Investigation — Zero Drift Started with the load cell loop and mechanical side of the belt scale: Load cell loop — checked the full loop, cleaned the load cell area. Idlers/rollers — checked the rollers for wear or misalignment. Belt tracking — with the belt empty, noticed it was drifting to one side. Zero was being tared in that empty, drifted position. Once material loaded onto the belt, the belt tracked back closer to center — meaning the zero reference had been tak...
Practical Procedure · Calibration Load Cell Calibration for Weigh Feeders — Dead-Load, Test-Weight, and Why Shunt Calibration Isn't Enough Applies to: Belt weigh feeders, weigh hoppers with load cell-based measurement | Equipment needed: Certified test weights or a dead-load/material reference, shunt calibration resistor (if supported), digital indicator/weigh controller access Before You Start Confirm the feeder/hopper is mechanically free — check idlers, belt tension, and load cell mounting for anything that could add friction or false load before assuming a load cell problem. Check load cell cabling and junction box connections for corrosion or loose terminations, especially in dusty or humid plant environments. Note whether the system uses a single load cell or multiple load cells summed together — multi-cell systems need each cell checked individually, not just the combined output. Method 1 — Shunt Calibration Shunt calibration simulates a known load...
Fault Log · Field Report Zirconia Oxygen Analyzer Reading Maximum O2 — Not the Cell, a Rusted Outlet Plant: Cement | System: Zirconia oxygen analyzer, sample extraction system | Downtime: None Symptom The zirconia oxygen analyzer started reading maximum oxygen — pegged at the top of the range rather than tracking the actual process value. A reading stuck at maximum on a zirconia cell usually means the cell is seeing something close to ambient air instead of process gas, which points straight at a sample delivery problem before you even think about the analyzer itself. Investigation Started at the sample path, from the process side inward: Probe, extractor filter, sampling line, pump — checked the full sample path from the probe through the extraction filter and sampling line, including the sample pump. Performed a leakage test across this section. All found ok. Panel-side tubing and membrane filter — checked all tubing inside the panel along...
Comments
Post a Comment