A KPI turns a pile of raw measurements into a single number that tells an operator whether the business is winning or losing. In oil and gas, KPIs distill the flood of SCADA tags - pressures, flows, run statuses - into figures that a superintendent or executive can act on: barrels per day, uptime, cost per barrel. This guide explains what a KPI is, how it differs from a plain metric, and where the data behind it comes from.
KPI (Key Performance Indicator) in one line: A key performance indicator (KPI) is a quantified measure tied to a specific business or operational goal, tracked over time to show whether performance is on target. Unlike a raw reading, a KPI is deliberately chosen to reflect something that matters - production, availability, efficiency - and is compared against a target or baseline.
A metric is any number you can measure - a tank level, a tubing pressure, a motor run time. A KPI is a metric that has been elevated because it is tied to an objective and has a target. The distinction is intent: you measure hundreds of things, but you manage against a handful of KPIs. A wellhead pressure of 420 psi is a metric; well availability of 97.5 percent against a 98 percent target is a KPI because it answers a question someone is accountable for.
Good KPIs share a few traits. They are quantifiable, so there is no argument about the value. They have a target or threshold, so the number has meaning - 92 percent is only good or bad relative to a goal. And they are actionable, meaning a person can do something to move them. A KPI nobody can influence is just a statistic.
Upstream operations lean on a familiar set. Production KPIs include barrels of oil per day (BOPD), gas volume (MCF or MMCF/day), and water cut. Availability and reliability KPIs include well uptime, run time versus scheduled time, and downtime hours by cause. Efficiency KPIs include lease operating expense per barrel, energy cost per unit produced, and pump or compressor efficiency. Safety and environmental KPIs track spills, flaring volume, and emissions.
Most of these are ratios or rates rather than instantaneous readings, which is why they are computed from historized data over a period - a day, a month, a rolling window - rather than read off a single tag. Availability, for example, needs total run time and total scheduled time accumulated across an interval, not a snapshot.
KPIs are only as trustworthy as the measurements underneath them. Production and availability KPIs are calculated from tags that a SCADA system collects from the field: flow totals from meters and flow computers, run status from pumps and motors, and volumes from tank gauges. The SCADA platform historizes these values so a reporting or analytics layer can aggregate them into the KPI over the right time window.
A cloud-native SCADA like Merobix reads those underlying tags from PLCs, RTUs, and flow computers over Modbus, DNP3, or OPC UA and stores them with timestamps. That historized data is the raw material a KPI dashboard consumes - the platform supplies clean, contextualized measurements, and the KPI calculation aggregates them against targets so operations can see performance at a glance.
A metric is any measured value; a KPI is a metric chosen because it maps to a business goal and is tracked against a target. Every KPI is a metric, but only a few metrics rise to KPI status - the ones you actively manage, like uptime or cost per barrel, rather than merely observe.
Typical production KPIs include barrels of oil per day, gas volume, and water cut; reliability KPIs include well uptime and downtime by cause; and cost KPIs include lease operating expense per barrel. Most are rates or ratios computed from historized SCADA data over a day, month, or rolling window.
The SCADA system collects and historizes field tags - flow totals, run status, volumes - then a reporting layer aggregates those values over a defined period and compares them to a target. For example, availability equals accumulated run time divided by scheduled time across the period, expressed as a percentage.
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.