API MPMS 20.1 1993 (2011): A Technical Guide to Allocation Measurement

Understanding the Framework for Equitable Distribution of Petroleum Fluids in Multi-Owner Systems

Scope of API MPMS 20.1 1993 (2011)

The American Petroleum Institute (API) Manual of Petroleum Measurement Standards (MPMS) serves as the global authority for the accurate measurement of hydrocarbon fluids. Chapter 20.1, designated as API MPMS 20.1 (1993, Reaffirmed 2011), establishes the critical framework for allocation measurement. This standard specifically addresses the equitable distribution of petroleum production, receipts, and deliveries among multiple owners or participants in joint ventures, units, and production sharing agreements.

Allocation measurement is required whenever commingled streams from various sources are produced through shared facilities before they reach a fiscal or custody transfer point. The scope of API MPMS 20.1 encompasses:

  • Design and operational requirements for allocation measurement systems.
  • Formal quantification of measurement uncertainty for allocated quantities.
  • Protocols for data collection, validation, editing, and reporting.
  • Handling and distribution of “Lost and Unaccounted For” (LUAF) volumes.
  • Reconciliation of allocated volumes against total measured production.
Foundation of Equity: API MPMS 20.1 emphasizes that allocation must achieve “equity,” meaning the measurement system and resulting distribution of product must be fair and transparent to all parties involved. This principle governs every technical requirement in the standard.

Core Technical Requirements: Allocation Methods and Uncertainty

The technical core of API MPMS 20.1 focuses on two fundamental concepts: the method of allocation employed and the rigorous quantification of measurement uncertainty across the entire system.

Methods of Allocation

The standard recognizes three primary methodologies for determining each entity’s share of production:

  1. Direct Measurement: The highest standard of accuracy, where each owner’s stream is independently metered without commingling. This is preferred for high-value or large-volume streams.
  2. Proration: The total commingled volume is measured at a central point, and individual shares are assigned based on mutually agreed factors derived from periodic well tests, separator splits, or production logs.
  3. Engineering Estimation: Used where direct measurement or continuous proration is impractical. This relies on periodic well tests, PVT (Pressure-Volume-Temperature) analysis, and reservoir engineering models to estimate individual contributions.

Measurement Uncertainty in Allocation Systems

API MPMS 20.1 was a pioneering document in mandating formal uncertainty analysis for non-fiscal metering applications. It requires operators to define a total system uncertainty, accounting for every measurement point, sampling operation, and laboratory analysis contributing to the final allocation.

Allocation Point Type Fluid Typical Uncertainty Target (±%) Common Technologies
Sales / Custody Transfer Oil 0.25% Coriolis, PD meters, Turbine
Central Allocation Oil 0.5% – 1.0% Coriolis, Turbine, V-cone
Well / Platform Allocation Gas 1.0% – 2.0% Orifice, Ultrasonic, Turbine
Injection / Disposal Water 5.0% – 10.0% Magnetic, Ultrasonic
Well Test (Proration) Oil & Gas 2.0% – 5.0% Test Separator, Multiphase
Warning on LUAF: “Lost and Unaccounted For” volumes resulting from leaks, flaring, tank vapors, or meter drift must be distributed proportionally according to each party’s measured or allocated share. API MPMS 20.1 explicitly prohibits the arbitrary assignment of such losses to a single entity.

Implementation Highlights for Allocation Systems

Successfully implementing API MPMS 20.1 requires a systematic, data-driven approach to measurement management and system design.

  • Data Validation and Reconciliation: A cornerstone of the standard is the requirement for timely data validation. This includes checking meter factors against proving results, verifying water cut samples, and reconciling total facility balance on a predetermined schedule (typically monthly).
  • System Design for Low Uncertainty: Allocation networks should be designed to minimize the number of measurement points required for the calculation. Fewer inputs generally mean lower total system uncertainty, though redundancy for critical high-value streams may be justified.
  • Handling Data Gaps: The standard requires pre-established procedures for estimating volumes during meter failures or data outages. These procedures must be documented in the Joint Operating Agreement (JOA) or operating manual.
Design Tip: When designing a new facility or modifying an existing allocation system, model the entire allocation network in software that traces measurement uncertainty from each input meter to the final allocation output. This identifies the largest contributors to total uncertainty and directs investment in metering upgrades most effectively.

Compliance and Auditing Considerations

Compliance with API MPMS 20.1 is typically driven by regulatory requirements (such as those from the U.S. Bureau of Land Management) and the specific terms of Joint Operating Agreements. Key focus areas for auditors include:

  • Written Procedures: Operators must maintain and follow documented procedures covering meter proving, sampling, laboratory analysis, allocation calculations, and data management.
  • Accuracy Verification: Periodic audits must verify that the actual measurement uncertainty of the allocation system meets the targets defined in the governing agreements.
  • Audit Trails: Thorough records must be maintained for all missing data estimates, method overrides, and adjustments to allocation factors. This transparency is essential for partner confidence and dispute resolution.
Regulatory Risk: Non-compliance with allocation measurement standards can result in significant financial exposure, including royalty underpayments, partner penalties, and loss of operator designation in federal and state-regulated units. Strict adherence to API MPMS 20.1 provides the operator with a robust defense against claims of inequitable distribution.

Frequently Asked Questions

Q: What is the difference between a Measurement Point and an Allocation Point as defined in API MPMS 20.1?
A: A Measurement Point is a physical location where a flow meter and associated equipment are installed to quantify flow rate and volume. An Allocation Point is a logical or physical point in the system where a quantity or quality (e.g., API gravity, sulfur content) is determined for the purpose of distributing production among parties. Every Allocation Point relies on data from one or more Measurement Points.
Q: Is API MPMS Chapter 20.1 specific to upstream production operations?
A: While the standard heavily addresses upstream allocation (wells, platforms, production units), its principles apply universally to any shared processing or transportation system. This includes refineries, natural gas processing plants, and pipelines where products from multiple shippers are commingled.
Q: How does API MPMS 20.1 interface with other chapters in the MPMS?
A: API MPMS 20.1 acts as the framework standard for allocation. It references other chapters for detailed technology specifications: Chapter 4 (Proving), Chapter 5 (Metering), Chapter 14 (Natural Gas Fluids), and Chapter 20.3 (Measurement Uncertainty). The allocation methodology defined in 20.1 dictates how these technologies are applied to achieve equity.
Q: Given the standard was originally issued in 1993 and reaffirmed in 2011, is it still considered technically current?
A: Yes. The reaffirmation in 2011 recognized that the core principles of allocation measurement are mature and remain valid. However, users of the standard must integrate the requirements with more recent chapters, such as API MPMS Chapter 20.3 (Uncertainty) and Chapter 21.1 (Electronic Flow Measurement), which address modern computational and technological capabilities. The framework of 20.1 continues to serve as the industry benchmark for allocation contract language.

Analysis based on industry practice as of 2026. Standard Reference: API MPMS 20.1 (1993, Reaffirmed 2011).

📥 Standard Documents Download

🔒
Please wait 10 seconds, the download links will appear after the ad loads

Leave a Reply

Your email address will not be published. Required fields are marked *