What Does API MPMS Chapter 21 Cover?
When a measurement dispute turns on 'who changed this and when,' the answer lives in MPMS Chapter 21. This page explains what Chapter 21 covers - electronic gas and liquid measurement, and the audit-trail and configuration discipline behind them - for the measurement tech or SCADA engineer who owns a flow computer. It frames the chapter as a whole and points to its two parts rather than duplicating them.
MPMS Chapter 21 Scope in one line: API MPMS Chapter 21 covers electronic measurement of hydrocarbons, split into electronic gas measurement (Part 21.1) and electronic liquid measurement (Part 21.2). It governs how a flow computer records data - configuration logs, event logs, audit trails, alarm handling, and the averaging of live inputs - so a quantity can be independently reconstructed and defended, rather than governing a physical meter.
What Chapter 21 Is For
Chapter 21 is the part of the MPMS that governs the electronics, not the pipe. Where other chapters cover proving, sampling, and correction physics, Chapter 21 covers how a flow computer handles the measurement data - capturing inputs, computing quantities, logging changes, and preserving an audit trail. It exists because in modern measurement the disputes are usually about data integrity, not the meter.
It sits within the broader manual mapped in which MPMS chapter covers what task. Reaching for Chapter 21 is the right move whenever the question is about configuration, historical changes, averaging, or the defensibility of an electronic quantity rather than the physical measurement itself.
Its Two Parts: Gas and Liquid
Chapter 21 splits by phase. Part 21.1 governs electronic gas measurement - the configuration, logging, and averaging for gas flow computers - and is explained under API 21.1 electronic gas measurement. Part 21.2 governs electronic liquid measurement, explained under API 21.2 electronic liquid measurement.
The two share a philosophy - preserve the ability to reconstruct a quantity - but differ in the physics they wrap. Gas measurement leans on the gas correlations and averaging periods; liquid measurement leans on meter factors and volume correction. When you cite Chapter 21, specify the part, because the requirements and the data they govern are not identical.
Why the Audit Trail Matters
The heart of Chapter 21 is auditability. A configuration change - a new K-factor, an edited base pressure, a modified alarm limit - must be logged with what changed, when, and by whom, so the quantity can be reconstructed after the fact. This is exactly the evidence a measurement audit reconstructs, and it is why the quantity transaction record and configuration log are so central.
For SCADA engineers the practical implication is that you cannot treat a flow computer like an ordinary RTU whose config you tweak freely. Changes to a Chapter 21 device are measurement events with contractual weight. The audit trail is not overhead - it is the thing that lets a disputed ticket be defended months later.
Common Misconceptions
A common misconception is that Chapter 21 defines the meter or the flow equation. It does not - the physics lives in other chapters and in AGA reports. Chapter 21 governs how the electronic device records and preserves the measurement, not how the flow is physically sensed.
Another is that any data historian satisfies Chapter 21. General historians capture trends; Chapter 21 requires a specific audit trail of configuration and events tied to the measured quantity, retained so the quantity is reconstructable. A generic trend archive is not the same as a compliant configuration and event log.
Frequently Asked Questions
What is the difference between MPMS 21.1 and 21.2?
Part 21.1 covers electronic gas measurement and Part 21.2 covers electronic liquid measurement. They share the same audit-trail philosophy but wrap different physics - gas correlations and averaging for 21.1, meter factors and volume correction for 21.2. Cite the part, not just the chapter.
Does Chapter 21 define the flow equation?
No. The flow physics lives in other MPMS chapters and in AGA reports. Chapter 21 governs how the electronic device records, logs, and preserves the measurement data so a quantity can be reconstructed and defended.
Is a data historian enough to meet Chapter 21?
Not by itself. Chapter 21 requires a specific audit trail of configuration changes and events tied to the measured quantity, retained so the quantity is reconstructable. A general trend historian does not automatically provide that configuration and event record.
Sources and verification
This page references the standards, specifications, and official documentation published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
- API Manual of Petroleum Measurement Standards (MPMS) - American Petroleum Institute
Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Automation services
Need help turning this into a working system?
Merobix integrates SCADA, programs Allen-Bradley and Siemens PLCs, and designs and fabricates industrial control panels.
Meeting requests are reviewed before confirmation.