Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
API MPMS 20.1 (1993 / Addend. 2013): The Definitive Guide to Allocation Measurement in the Upstream Sector
Unpacking the Technical Requirements, Uncertainty Protocols, and Compliance Strategies of the Manual of Petroleum Measurement Standards
The American Petroleum Institute’s Manual of Petroleum Measurement Standards (API MPMS) is the cornerstone of hydrocarbon measurement globally. Chapter 20, Section 1 (API MPMS 20.1), originally published in 1993 and significantly enhanced by its 2013 Addendum, specifically addresses the complex technical and administrative requirements of allocation measurement. While custody transfer focuses on the commercial exchange at a singular point, allocation measurement governs the fair and equitable distribution of a commingled hydrocarbon stream back to its multiple contributing sources. This article provides a detailed technical breakdown of this critical standard, its scope, its demanding technical requirements, and the key compliance considerations for operators in 2026.
1. Scope and Foundational Principles of API MPMS 20.1
The scope of API MPMS 20.1 is explicitly defined to provide a consistent methodology for the measurement and allocation of bulk liquid hydrocarbons and gas. The original 1993 edition established the basic principles of allocation. It defined the different methods—such as proportional allocation based on quality or quantity—and stressed the importance of measurement at the “point of determination.”
The 2013 Addendum was a landmark revision that fundamentally shifted the focus from simply “taking a measurement” to rigorously quantifying and managing the uncertainty of the entire allocation process.
Critical Observation: A common pitfall is treating API MPMS 20.1 solely as a metering standard. In reality, it is a system engineering and fiscal management standard. The 2013 Addendum emphasizes that the uncertainty of the final allocation result is driven by the uncertainty of all input measurements (flow rate, temperature, pressure, density, composition) combined mathematically according to the allocation method.
The standard applies to:
- Production platforms and subsea tie-backs.
- Onshore gathering systems and processing plants.
- Pipeline batch delivery allocation.
- Liquefied Natural Gas (LNG) cargo allocation.
It distinctly separates the concepts of “Pareto Optimality” and “Individual Risk” in allocation, a nuance critical for the 2013 framework.
2. Technical Deep Dive: The 2013 Uncertainty Framework
The 2013 Addendum introduced formal requirements for an Allocation Measurement Performance Standard (AMPS). This requires operators to calculate Global Allocation Uncertainty (GAU) and ensure it does not exceed a predetermined target. The method is heavily based on the “Guide to the Expression of Uncertainty in Measurement” (GUM), adapted specifically for the allocation scenario.
The standard requires a layered approach to uncertainty modeling:
- Input Uncertainty: The error of individual meters and laboratory analyses (e.g., composition, BTU value).
- Allocation Method Variance: The mathematical sensitivity of the chosen allocation method to input errors.
- Global Uncertainty: The total uncertainty of the final allocated volumes or energy quantities.
Table 1: Example Contributors to Allocation Uncertainty
| Measurement Component | Common Standard / Technology | Typical Input Uncertainty Band | Impact on Allocation (High/Med/Low) |
|---|---|---|---|
| Liquid Custody Transfer Meter | API MPMS Ch. 5 / Ch. 4 (Provers) | ±0.15% of Reading | High |
| Gas Ultrasonic Meter (USM) | API MPMS Ch. 14.8 | ±0.5% to ±1.0% of Flow | High |
| Gas Chromatograph (GC) | GPA 2177 / ISO 6974 | ±0.25% to ±0.5% (Mol %) | Medium |
| Density Transmitter (Coriolis) | API MPMS Ch. 14.6 | ±0.5 to ±2.0 kg/m³ | High |
| Water Cut Analyzer | API MPMS Ch. 10 / Ch. 12 | ±0.1% to ±2.0% (BS&W) | Critical |
Implementation Tip: When building your AMPS model, pay close attention to the covariance between input meters. If two streams use the same meter type calibrated by the same entity, their errors are partially correlated. API MPMS 20.1 (2013) requires this correlation to be mathematically modeled.
3. Implementation and Operational Highlights
Successfully implementing API MPMS 20.1 (1993 / 2013) requires a systemic approach that goes beyond field hardware.
- Meter Proving: The standard mandates a rigorous proving schedule (e.g., weekly or monthly) based on the stability of the meter and the value of the fluid. Data from prover runs must be statistically validated.
- Software Validation: The 2013 Addendum explicitly calls for the validation of flow computers and allocation software. This is often the most overlooked aspect. The software must demonstrate that it implements the allocation equations and uncertainty calculations correctly.
- Data Reconciliation: Mass balance checks are required. A “shrinkage” or “unaccounted for” (UAF) value must be calculated and reported. If UAF exceeds a threshold defined in the AMPS, an investigation is mandatory.
Best Practice 2026: Leading operators are integrating API MPMS 20.1 requirements directly into their Digital Twin models. This allows real-time monitoring of allocation uncertainty and automated alerts when uncertainty limits are approached due to a failing meter or changing fluid properties.
4. Compliance, Auditing, and Documentation
Compliance with API MPMS 20.1 is typically a contractual requirement between partners (e.g., in a Joint Venture or Unitization agreement) or a regulatory requirement for production reporting. The key document produced under the standard is the Allocation Measurement Performance Standard (AMPS) document.
An auditor will typically look for:
- Traceability: Can every allocated barrel be traced back to a meter reading and a set of lab results?
- Uncertainty Budget: Is there a formal, documented uncertainty budget that follows the GUM methodology? Are the calculations reproducible?
- Periodic Verification: Are meters and analyzers proved/calibrated within the required intervals?
- Exception Management: Is there a procedure for handling missing, frozen, or erroneous meter data? The standard requires a robust “bad data” handling procedure.
Compliance Risk: Failure to maintain an up-to-date AMPS or to properly calculate GAU can lead to legal disputes among partners or regulatory fines. The 2013 Addendum made it significantly harder to simply “assume” a measurement is good enough without rigorous mathematical proof.
Conclusion
API MPMS 20.1 (1993 / Addend. 2013) remains the definitive standard for allocation measurement. The 2013 Addendum moved the industry from a prescriptive “this meter is good enough” mindset to a performance-based “prove your allocation system uncertainty is acceptable” framework. For engineers and auditors working in 2026, mastering the AMPS, the uncertainty propagation mathematics, and the rigorous documentation requirements of this standard is non-negotiable for fair and compliant hydrocarbon allocation.
This technical guide reflects the key principles and compliance requirements as applied in the industry in 2026.
Frequently Asked Questions (FAQs)
Q: What is the main difference between the 1993 edition and the 2013 Addendum of API MPMS 20.1?
A: The 1993 edition laid the foundational principles and methods for allocation measurement. The 2013 Addendum introduced a mandatory performance-based framework requiring operators to calculate a Global Allocation Uncertainty (GAU) target and prove their measurement systems meet this target using rigorous mathematical methodologies derived from the ISO GUM. It shifted the focus from “taking a good measurement” to “proving the allocation result is fair and accurate.”
A: The 1993 edition laid the foundational principles and methods for allocation measurement. The 2013 Addendum introduced a mandatory performance-based framework requiring operators to calculate a Global Allocation Uncertainty (GAU) target and prove their measurement systems meet this target using rigorous mathematical methodologies derived from the ISO GUM. It shifted the focus from “taking a good measurement” to “proving the allocation result is fair and accurate.”
Q: Does API MPMS 20.1 apply to custody transfer meters?
A: While it heavily relies on custody transfer standards (Ch. 5, 14.8, etc.), API MPMS 20.1 is specifically for allocation. It applies to the network of meters used to divide volumes, not just a single fiscal point. A single meter can serve both purposes, but the uncertainty analysis and performance targets are different. Allocation uncertainty focuses on the equity of division, while custody transfer uncertainty focuses on the absolute accuracy of value exchange.
A: While it heavily relies on custody transfer standards (Ch. 5, 14.8, etc.), API MPMS 20.1 is specifically for allocation. It applies to the network of meters used to divide volumes, not just a single fiscal point. A single meter can serve both purposes, but the uncertainty analysis and performance targets are different. Allocation uncertainty focuses on the equity of division, while custody transfer uncertainty focuses on the absolute accuracy of value exchange.
Q: How often should the Allocation Measurement Performance Standard (AMPS) be reviewed?
A: The standard recommends the AMPS be a living document. It should be reviewed and updated whenever there is a significant change in the facility, such as a new well tie-in, a choke change that affects fluid phase, decommissioning a meter, or changing the allocation method itself. An annual review is considered the industry minimum best practice as of 2026.
A: The standard recommends the AMPS be a living document. It should be reviewed and updated whenever there is a significant change in the facility, such as a new well tie-in, a choke change that affects fluid phase, decommissioning a meter, or changing the allocation method itself. An annual review is considered the industry minimum best practice as of 2026.
Q: What happens if my global allocation uncertainty is higher than the target?
A: This demands immediate deep investigation. The operator must first confirm the uncertainty model is correct and the meters are properly proved. If the GAU remains high, it can invalidate the allocation results. Partners typically agree on a “High Uncertainty” threshold. If breached, manual reconciliation, pro-ration based on well tests, or even a mechanical shutdown of production might be triggered until the root cause (e.g., a faulty water cut meter or gas chromatograph) is resolved.
A: This demands immediate deep investigation. The operator must first confirm the uncertainty model is correct and the meters are properly proved. If the GAU remains high, it can invalidate the allocation results. Partners typically agree on a “High Uncertainty” threshold. If breached, manual reconciliation, pro-ration based on well tests, or even a mechanical shutdown of production might be triggered until the root cause (e.g., a faulty water cut meter or gas chromatograph) is resolved.
© 2026. This technical article is provided for informational purposes and reflects standard industry practices related to API MPMS Chapter 20.1.