The API Manual of Petroleum Measurement Standards, universally shortened to MPMS, is the master reference for how petroleum liquids and gases are measured for custody transfer. It is not a single standard but a large, chaptered manual that covers every part of the measurement problem: how to meter a flowing stream, how to prove that a meter is accurate, how to take a representative sample, and how to correct a measured volume to standard conditions. When two parties buy and sell hydrocarbons and money changes hands based on the measured quantity, the MPMS is the common rulebook that makes the number trustworthy to both sides. It is the framework that unifies the many individual measurement practices used in the field.
API MPMS (measurement manual) in one line: API MPMS, the Manual of Petroleum Measurement Standards, is the master collection of standards published by the American Petroleum Institute governing how petroleum is measured for custody transfer. Organized into numbered chapters covering metering, proving, sampling, temperature and volume correction, and calculation, it provides the agreed methods that make a measured quantity accurate and defensible when hydrocarbons are bought and sold.
The MPMS is organized into numbered chapters, each dealing with a distinct part of the measurement problem, and understanding that structure is the key to using it. Rather than a single monolithic document, it is a library in which one chapter addresses metering technology, another addresses proving, another addresses sampling, and others cover the calculations and correction factors that turn a raw meter reading into a settled volume. This modularity is deliberate: measurement is made up of separable steps, and each step deserves its own detailed treatment.
Because the manual is chaptered, the individual measurement topics an operator deals with in the field each map to a place within it. Meter proving, temperature correction of volumes, sampling of a stream to determine its quality, and the calculation of net standard volume are all covered by their own portions of the MPMS. This is what makes the manual valuable as a unifying reference: the separate practices that might otherwise seem like a disconnected collection of procedures all live under one governing structure, cross-referencing each other where they connect.
The chaptered approach also means the MPMS can evolve piece by piece. As a measurement technology matures or a calculation method is refined, the relevant chapter can be updated without rewriting the whole manual. For an operator, the practical takeaway is that citing the MPMS usually means citing a specific chapter for a specific task, and that the manual is best thought of as the umbrella under which all those specific measurement standards sit rather than as a single procedure to follow end to end.
The reason the MPMS treats measurement as a set of connected steps is that an accurate custody-transfer volume depends on all of them working together. A meter alone gives an indicated volume, but that number is only as good as the meter's proven accuracy, so proving - comparing the meter against a known reference to establish a correction factor - is what anchors the meter's reading to reality. Without proving, a meter's output is an assertion; with proving, it becomes a measurement with a known correction applied.
Sampling and quality determination address a different question: what is actually flowing. A volume of liquid is not the whole story when the stream carries water or when its composition affects value, so representative sampling lets the parties determine quality alongside quantity. The MPMS covers how to take a sample that truly represents the flowing stream, because a sample drawn badly gives a misleading picture of what was delivered. Quantity and quality together are what a custody transfer ultimately settles on.
Volume correction is the step that makes measured volumes comparable. A liquid's volume changes with temperature and pressure, so a barrel measured at field conditions is not the same as a barrel at standard reference conditions. The MPMS provides the correction methods that bring every measurement to a common basis, so that a volume measured on a hot afternoon and one measured on a cold morning can be compared and settled fairly. Proving establishes that the meter is accurate, sampling establishes what the stream is, and correction establishes a common basis for the volume - and the MPMS is what ties those three into one coherent measurement.
In the field, the MPMS is the standard behind the LACT unit - the lease automatic custody transfer skid where produced crude is metered, sampled, and measured as it leaves a lease. A LACT unit exists precisely to perform, automatically and repeatably, the measurement the MPMS defines: it meters the flow, takes samples, and produces the data that determines how much crude was transferred and therefore how much is owed. The MPMS is why a LACT unit is built and operated the way it is, and why its measurement can be trusted by both the producer and the purchaser.
A cloud SCADA platform such as Merobix intersects the MPMS at the data layer rather than at the measurement itself. The metering, proving, and sampling are performed by the field equipment to the manual's methods; SCADA reads the resulting measurements - meter totals, temperatures, proving results, and alarms - and carries them off the site to where they are used. It is important not to overstate this: SCADA does not replace a prover or perform the custody measurement, and the accuracy that makes a number defensible comes from the equipment and procedures the MPMS governs, not from the monitoring layer.
What monitoring adds is visibility and continuity around a measurement that has real financial weight. Because a custody-transfer number determines payment, an operator wants to know promptly if a meter is behaving abnormally, if a proving is overdue, or if a reading has stalled, and cloud monitoring surfaces those conditions from remote and unmanned sites. Historizing the measurement data also creates a timestamped record that supports reconciliation and dispute resolution. The MPMS makes the measurement accurate; cloud SCADA makes that accurate measurement visible, continuous, and recorded across a fleet of sites no one is standing next to.
API MPMS stands for the Manual of Petroleum Measurement Standards, published by the American Petroleum Institute. It is the master collection of standards that governs how petroleum is measured for custody transfer, meaning the buying and selling of hydrocarbons where money depends on the measured quantity. It provides the agreed methods for metering, proving, sampling, and volume correction so a measured number is accurate and defensible to both parties.
The MPMS is organized into numbered chapters, each covering a distinct part of the measurement problem such as metering, proving, sampling, temperature and volume correction, and calculation. It is a library of standards rather than a single document, which lets individual chapters be updated as technologies and methods evolve. Citing the MPMS usually means citing a specific chapter for a specific task, with the manual acting as the umbrella over all those measurement standards.
A LACT, or lease automatic custody transfer, unit is the field skid that automatically meters, samples, and measures crude as it leaves a lease, and it is built to perform the measurement the MPMS defines. The manual is why a LACT unit meters, proves, samples, and corrects volumes the way it does, so that both the producer and the purchaser can trust the transferred quantity. The MPMS provides the methods, and the LACT unit is the equipment that carries them out automatically.
Primary references from the standards bodies and regulators that define this topic:
Safety & engineering notice. This article is general educational information, not site-specific engineering, safety, or legal advice, and it does not reflect any particular facility. Standards and regulations (for example OSHA, API, IEC, ISO, NFPA, NIST, and NERC CIP requirements) change and vary by edition, jurisdiction, and application. SCADA and remote monitoring cannot verify physical isolation, atmosphere, lockout/tagout, permit status, or a safe go/no-go decision. Qualified personnel must perform site-specific engineering, hazard analysis, and safety review, and confirm current requirements with the authority having jurisdiction, before acting.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.