A number on a dashboard is only half a story until you know what it was supposed to be. Today's production is 480 barrels - is that good? You cannot say until you know the target. A target-vs-actual KPI tile answers that by showing the measured value and its target side by side, along with the gap between them, so a glance tells you not just where things stand but whether they are on plan. This guide explains what such a tile shows, how the variance is presented, and how it converts raw measurements into an immediate are-we-on-track signal.
Target-vs-actual KPI tile in one line: A target-vs-actual KPI tile is a dashboard element that displays a measured actual value alongside its planned target and shows the variance between them. Rather than presenting a bare number, it frames that number against what it was supposed to be, so the viewer sees at a glance whether performance is ahead of, on, or behind plan. It is a comparison visual, distinct from the target definition itself and from a plain value tile.
The defining feature of a target-vs-actual tile is that it never shows the actual in isolation. It always pairs the measured value with the target it is being judged against and makes the relationship between them visible. At minimum that means three pieces of information on one tile: the actual value, the target value, and the variance - the difference between them, often shown as both an absolute gap and a percentage. The viewer does not have to remember the target or do the subtraction; the tile has already framed the number in the terms that make it meaningful.
This matters because a raw value cannot be interpreted without a reference. A production figure, an uptime percentage, or a cost number is neither good nor bad on its own; it only becomes good or bad relative to what was expected. By carrying the target with the actual, the tile supplies exactly the reference the viewer needs, transforming a number that requires context into one that comes with its context attached. The judgement - are we where we should be - is made possible on the tile itself rather than in the viewer's head.
The variance is the payload of the tile, because it is the part that carries the answer. A variance near zero says on plan; a favorable variance says ahead; an unfavorable one says behind, and its size says by how much. Well-designed tiles make the direction and magnitude of the variance instantly legible - a sign, a color, or a small bar - so that the on-or-off-plan verdict registers before the viewer has consciously read the numbers. The whole design serves the goal of making the gap, not just the value, the thing you notice first.
It is worth being precise about what a target-vs-actual tile is not, because it sits close to two related ideas. First, it is not the same as the definition of a KPI target and its thresholds. That definition is the act of deciding what the goal and the acceptable limits are - setting the target of 500 barrels and the threshold below which performance counts as poor. The target-vs-actual tile consumes that definition; it takes the target as given and its job is to display the current actual against it. One establishes the yardstick, the other holds the measurement up to it.
Second, it is a specific kind of KPI tile, not the general concept of a tile. A KPI tile in the broad sense is simply the format - a compact panel presenting a single metric on an HMI or dashboard. A plain value tile of that kind might show only the actual number, or the actual with a trend. The target-vs-actual tile is the particular variety whose whole purpose is the comparison: it is defined by carrying the target and the variance, not just the value. Every target-vs-actual tile is a KPI tile, but not every KPI tile makes the comparison.
This precision matters for a dashboard designer choosing what to show. A bare value tile is right when the number speaks for itself or when the goal is just current status. A target-vs-actual tile is right when the question is not what is the value but are we meeting the plan - and that is a common question for metrics with an explicit goal, such as production against a daily target, actual downtime against a budget, or throughput against a committed rate. Choosing the target-vs-actual form is choosing to answer the on-plan question directly on the tile rather than leaving the viewer to answer it themselves.
In oil and gas operations, a great many of the metrics that matter are inherently plan-versus-reality questions, which makes the target-vs-actual tile a natural fit. Daily or monthly production is measured against a forecast or an allocation; runtime and uptime are measured against a target; injection, throughput, and chemical usage all have planned rates they are supposed to hold. For each of these, the interesting fact is rarely the bare number but the gap between what was planned and what actually happened, which is exactly what the tile is built to surface.
Placing these comparisons on a monitoring dashboard turns a scattered reconciliation exercise into an at-a-glance check. Instead of pulling the actuals into a report and comparing them to plan after the fact, an operator or supervisor sees the variance live: this well is behind its target, that facility is ahead of its uptime goal, this route is over its chemical budget. The tile makes the on-plan status of each metric continuously visible, so a shortfall is noticed as it develops rather than discovered at month-end when it is too late to do much about it.
On a cloud SCADA platform such as Merobix, a target-vs-actual tile is fed by live field data on the actual side and by the operation's own targets on the plan side, so the variance it shows reflects the true current state across many sites. A supervisor scanning a fleet dashboard can see, tile by tile, which sites are on plan and which are drifting, without doing any arithmetic themselves - the comparison has already been made and rendered. For an operation that runs to production and performance targets, that continuous, self-interpreting are-we-on-plan signal is precisely what turns a wall of measurements into a view someone can actually manage from.
A KPI target and threshold is the definition of the goal and the acceptable limits - deciding what the target value is and where the boundary between acceptable and poor performance lies. A target-vs-actual tile is the display that consumes that definition, showing the current measured actual against the given target and the variance between them. One sets the yardstick; the other holds the live measurement up to it and shows how far off it is.
The variance is the difference between the actual and the target, and it carries the tile's real message: whether performance is ahead of, on, or behind plan, and by how much. A variance near zero means on plan, a favorable variance means ahead, and an unfavorable one means behind, with its size showing the magnitude of the gap. Good tiles make the direction and size of the variance instantly legible so the on-or-off-plan verdict registers before you have consciously read the numbers.
Use a target-vs-actual tile when the important question is not what is the value but are we meeting the plan - which is the case for any metric with an explicit goal, such as production against a daily target or uptime against a budget. A plain value tile is enough when the number speaks for itself or you only want current status. The target-vs-actual form is the right choice when you want the tile itself to answer the on-plan question rather than leaving the viewer to do the comparison.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.