Knowing that a value is climbing is useful, but knowing whether it is climbing the way it should is far more useful, and that comparison needs a reference. A historical overlay puts a past window of the same tag - yesterday, the last batch, a known good run - directly on top of the live trace so the operator can see current behavior against a proven baseline. When today's curve tracks the reference the operator relaxes, and when it diverges they have an early, concrete signal that something has changed. This guide explains how overlays work, what kinds of references operators use, and where the technique fits in remote monitoring.
Historical Overlay Trend in one line: A historical overlay is a past time window of a tag drawn on the same trend as its current data, aligned on a common axis so the two can be compared directly. The reference might be the previous day, the last batch, or a saved golden run, and the overlay lets an operator judge whether current behavior matches the expected pattern rather than reading the live trace in isolation.
A historical overlay works by shifting a slice of history so it lines up with the present on the chart. The operator picks a reference window - say the same tag over yesterday's shift - and the trend draws that past data over the live trace, aligning the two on the same value axis and offsetting the reference in time so their start points coincide. The result is two curves for the same measurement occupying the same chart space, one showing what is happening now and one showing what happened during the reference period, ready to be read against each other.
The comparison only means something if the axes match, so the overlaid data must share the value scale of the live trace. When both curves use the same vertical range, a gap between them is a real difference in the measurement rather than an artifact of different scaling, and the operator can read the size of a divergence directly off the chart. Distinguishing the two traces clearly, usually by color or line style with a label saying which is live and which is the reference, keeps the operator from confusing past for present.
Overlays extend naturally to more than one reference. An operator can lay several past periods over the live trace to see the normal spread of behavior, so today's curve is judged not against a single day but against a band of what is typical. Seeing the live trace sit inside or stray outside that band turns a vague sense of normal into something the operator can actually see, which is the whole point of the technique.
The value of an overlay depends entirely on choosing a meaningful reference, and different situations call for different ones. The simplest is the previous comparable period - yesterday, last week, the prior shift - which answers whether the process is behaving as it did recently. This is the everyday use: an operator glances at today against yesterday and immediately sees whether anything has shifted, without needing to remember what yesterday's numbers were.
For batch or cyclic operations the natural reference is the last batch or a previous cycle, aligned from the start of the batch rather than by clock time. Overlaying the current batch on the previous one shows whether this run is following the same profile, so a deviation in temperature ramp or a slow step is visible early enough to act on. Because batches are meant to repeat, the overlay turns each new run into a comparison against how the last one actually went.
The most powerful reference is a golden run: a saved record of an ideal or benchmark period when the process performed exactly as wanted. Overlaying the golden run on the live trace gives the operator a target profile to steer toward, and any divergence from it is a direct measure of how far current operation strays from best. Keeping a library of these reference runs - one per product, one per operating mode - lets operators compare against the right ideal for whatever the plant is doing at the moment.
Historical overlays lean heavily on stored data, which makes them a strong fit for cloud SCADA where a deep historian is always available. On a platform such as Merobix the same interface that shows the live trace can reach back for yesterday, last month, or a saved reference run and lay it over the present, because the history and the live data come through one system. The operator does not switch tools to compare against the past; the reference is a selection away on the same chart.
Overlays are especially useful when the operator is remote and cannot see or hear the process directly. Watching a distant well or compressor over a link, an operator has none of the physical cues a local operator would use to sense that something is off, so a reference overlay becomes a substitute for that intuition. When today's pressure curve drifts away from the shape it held all last week, the overlay gives the remote operator a concrete, early reason to look closer at a site they cannot walk up to.
Across a fleet of similar sites, overlays also support comparison in a way plain live trends cannot. A saved golden run for one well type can be overlaid on any well of that type to judge whether it is performing like its peers, giving a remote operator a consistent yardstick across many locations. Because the reference and the live data are both served from the cloud historian, the same comparison works from a browser, a tablet, or a phone, so the technique stays available wherever the operator is watching from.
A golden run is a saved record of a period when the process performed exactly as desired, kept as a benchmark to compare future operation against. Overlaying it on the live trend gives the operator a target profile to steer toward, and any divergence from it measures how far current operation departs from that ideal. Operations often keep a library of golden runs, one per product or operating mode, to compare against the right reference for what the plant is doing.
So that a gap between the curves reflects a real difference in the measurement rather than a difference in scaling. When the live trace and the historical overlay share the same value range, the operator can read the size of any divergence directly off the chart. If the two used different scales, the comparison would be misleading because curves could appear close or far apart for reasons that have nothing to do with the process.
No. A multi-pen trend shows several different tags together over the same current time window. A historical overlay shows the same tag over two different time windows, one live and one from the past, on one chart. The multi-pen trend compares different measurements now; the overlay compares one measurement now against how it behaved before.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.