Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
1. Scope and Applicability of API MPMS Chapter 22.1
“content”: “
1. Scope and Applicability of API MPMS Chapter 22.1
The API Manual of Petroleum Measurement Standards (MPMS) Chapter 22.1, Second Edition (2015), formally titled ‘Testing Protocol for Pressure, Differential Pressure, and Temperature Instrumentation’, establishes uniform laboratory and field test procedures for verifying the performance of primary measurement elements. It provides a standardized framework to ensure that the instruments used in fiscal metering, allocation measurement, and process control meet the necessary accuracy and reliability standards.
This standard specifically applies to pressure transmitters, differential pressure (DP) transmitters, temperature transmitters, resistance temperature detectors (RTDs), and thermocouples. It defines the how of testing—detailing the metrological protocols, minimum test points, acceptance criteria, and uncertainty calculations. By providing a consistent methodology, API MPMS 22.1 ensures equivalence of measurement across different operators, locations, and jurisdictions, which is critical for custody transfer agreements.
Who should use this standard? This standard is indispensable for metering engineers, calibration technicians, and quality auditors involved in the verification of transmitters and sensors used in custody transfer and allocation measurement systems.
2. Core Technical Requirements and Metrological Protocols
Chapter 22.1 outlines a rigorous set of procedures designed to minimize measurement uncertainty and maintain traceability to national standards.
2.1 Instrument Selection and Test Uncertainty Ratio (TUR)
The standard mandates a minimum Test Uncertainty Ratio (TUR) of 4:1 between the reference standard and the Device Under Test (DUT). This means the reference standard must be at least four times more accurate than the instrument being tested. If a 4:1 TUR cannot be achieved, the standard allows for acceptance using a ‘guard band’ method where the acceptance limits for the DUT are narrowed to account for the higher uncertainty of the reference standard.
2.2 DP and Pressure Transmitter Testing
The protocol requires a complete ‘As-Found / As-Left’ sequence. A minimum of five equally spaced test points are required across the calibrated span. The test must be conducted in both ascending and descending directions to quantify hysteresis and repeatability. Table 1 below illustrates the typical data capture format for a pressure transmitter calibration.
| Test Point (% Span) | Applied Pressure (psi) | Ideal Output (mA) | As-Found Error (%) | As-Left Error (%) |
|---|---|---|---|---|
| 0% | 0.00 | 4.00 | +0.05 | +0.01 |
| 25% | 250.00 | 8.00 | -0.08 | +0.02 |
| 50% | 500.00 | 12.00 | +0.12 | -0.01 |
| 75% | 750.00 | 16.00 | -0.10 | +0.02 |
| 100% | 1000.00 | 20.00 | +0.15 | +0.01 |
Pro Tip: Always allow sufficient warm-up time for the DUT and the reference standard to stabilize. A minimum of 30 minutes is generally recommended by the standard to ensure thermal equilibrium is reached before recording data.
2.3 Temperature Sensor Verification
For RTDs and thermocouples, the standard emphasizes the importance of immersion depth. Insufficient immersion is a primary source of measurement error known as ‘stem conduction’. The standard specifies a minimum immersion depth of 10 diameters for thermowell probes. Verification is typically performed at 0°C (ice bath) and the nominal operating temperature using a dry-block calibrator or temperature bath.
Critical Check: The reference thermometer must have a valid calibration certificate with traceability to a national metrology institute (e.g., NIST). The entire measurement chain, including the readout device and connection wires, must be considered in the uncertainty budget.
3. Implementation Best Practices and Field Integration
Integrating the protocols of API MPMS 22.1 into a daily maintenance schedule requires thoughtful planning and an understanding of modern field device capabilities.
3.1 Calibration Intervals
The standard does not explicitly prescribe specific intervals (e.g., monthly, quarterly). Instead, it promotes a method based on historical performance. A drift analysis over consecutive verifications can be used to optimize the interval while maintaining acceptable risk and minimizing operational downtime.
3.2 Smart Transmitter Digital Trims
A significant update in the 2015 edition is the focus on digital communications. The standard distinguishes between Sensor Trim (calibrating the sensing element) and Analog Output Trim (calibrating the 4-20 mA D/A converter). Both procedures are detailed to ensure the full range of modern field devices is covered, including HART, Foundation Fieldbus, and Profibus protocols.
Common Pitfall: Failing to document whether a digital trim or an analog trim was performed can lead to significant confusion during audits. Ensure your calibration records explicitly state the type of adjustment made and the resulting effect on the measurement loop.
4. Compliance, Audits, and Regulatory Context
Adherence to API MPMS Chapter 22.1 is frequently incorporated by reference in contractual agreements for hydrocarbon custody transfer. Regulatory bodies such as the Bureau of Land Management (BLM) in the US and Measurement Canada require evidence of compliance with recognized standards as part of their metrological oversight.
An audit against API MPMS 22.1 typically involves verification of reference standard traceability certificates, a thorough review of field calibration reports (As-Found / As-Left data), confirmation of TUR calculations, and evaluation of the environmental conditions during testing. Failure to adhere to the specific testing sequences can lead to disputed measurement quantities during custody transfer allocations, potentially resulting in significant financial reconciliation costs.
Compliance Strategy: A robust calibration management software system that aligns with the data requirements of API MPMS 22.1 is the most efficient way to demonstrate compliance during an audit. Automating the As-Found/As-Left workflow reduces human error and ensures data integrity.
Frequently Asked Questions
Q: Does API MPMS 22.1 apply to flow computers and gas chromatographs?
A: No, Chapter 22.1 specifically covers pressure, differential pressure, and temperature instrumentation. Flow computers are addressed under MPMS Chapter 21 (Flow Measurement Using Electronic Metering Systems), while gas chromatographs are covered in MPMS Chapter 14 (Natural Gas Fluids Measurement).
A: No, Chapter 22.1 specifically covers pressure, differential pressure, and temperature instrumentation. Flow computers are addressed under MPMS Chapter 21 (Flow Measurement Using Electronic Metering Systems), while gas chromatographs are covered in MPMS Chapter 14 (Natural Gas Fluids Measurement).
Q: What is the main difference between the 2006 and 2015 editions of Chapter 22.1?
A: The 2015 edition introduced much more detailed protocols for testing smart transmitters with digital outputs (HART, Foundation Fieldbus, Profibus). It also clarified requirements for calculating measurement uncertainty and provided stricter guidelines for temperature sensor immersion depth testing.
A: The 2015 edition introduced much more detailed protocols for testing smart transmitters with digital outputs (HART, Foundation Fieldbus, Profibus). It also clarified requirements for calculating measurement uncertainty and provided stricter guidelines for temperature sensor immersion depth testing.
Q: What happens if an instrument fails the “As-Found” test?
A: The standard dictates a specific procedure. First, document the as-found error. Second, perform an adjustment (calibration) to bring the instrument within tolerance. Finally, perform an “As-Left” test to verify the correction. The as-left data becomes the official benchmark for the next calibration interval.
A: The standard dictates a specific procedure. First, document the as-found error. Second, perform an adjustment (calibration) to bring the instrument within tolerance. Finally, perform an “As-Left” test to verify the correction. The as-left data becomes the official benchmark for the next calibration interval.
Published 2026. This technical analysis is for informational purposes and does not replace the official API document. Always consult the latest published edition for authoritative requirements.
“