A trend chart is far more useful when the right tags are already on it and scaled sensibly, and that is what a trend group gives you. Configuring a trend group means deciding which related tags belong together, how each should be scaled and colored, and over what time span they should be shown, then saving the whole arrangement under a name an operator can recall in one action. Done well, it turns a blank chart into a diagnostic tool that is ready the moment it opens. This guide walks through what goes into a trend group, how to build and manage standing groups, and how they fit a cloud historian.
Trend Group Configuration in one line: A trend group is a saved, named set of related tags configured to be viewed together on one trend chart, with each tag assigned a scale, an axis, and a color, plus a default time span. Configuring one means selecting the tags that tell a story together, setting sensible scales and axes so the traces are readable, and saving the arrangement so operators can recall it instantly instead of rebuilding it each time.
The first decision in configuring a trend group is which tags belong in it. A useful group collects values that tell a story together, such as the controlled variable, its setpoint, and the controller output for one loop, or the temperatures across the stages of a column. The aim is that seeing these traces on one chart reveals a relationship a single trace could not, so the operator diagnoses cause and effect at a glance rather than opening several separate trends and comparing them in their head.
Once the tags are chosen, each needs a scale and an axis. Tags that share units and a similar range can sit on a common axis, while a tag with a very different range - a pressure alongside a flow, for instance - usually needs its own axis so it is not flattened into a useless line at the top or bottom of the chart. Setting each scale to the meaningful operating band, rather than the full instrument range, is what makes small but important changes visible. Assigning distinct, consistent colors to each trace keeps the group readable when several traces overlap.
The last configuration choices are time and defaults. A trend group carries a default time span - a few hours for watching a loop settle, a shift or a day for spotting drift - chosen to match what the group is for. Some groups also fix which axis labels show, whether values are displayed live at the cursor, and how the traces are ordered in the legend. Saving all of this under a clear name is the step that turns a one-off chart into a reusable group the operator can summon by that name.
Standing trend groups are the handful of groups an operation defines once and uses constantly, and building them is a design task rather than an ad hoc one. The people who know the process decide which groups matter - one per critical loop, one per major unit, one for the utilities - and configure each carefully so that any operator who opens it gets a chart that is immediately meaningful. Naming them by what they show, so the operator recalls the compressor group or the reactor temperature group by an obvious name, is part of what makes them fast to reach.
Managing these groups over time keeps them useful. As the process changes, tags are added or renamed and ranges shift, so a standing group that was well scaled a year ago can drift into being misleading if no one maintains it. Treating the group library the way you treat any other part of the application, with periodic review and clear ownership, prevents the slow accumulation of stale or duplicated groups that confuse operators rather than help them. A small, well-curated set of groups beats a sprawling list nobody trusts.
There is usually a place for operator-built groups alongside the standing ones. An operator investigating an unusual problem may assemble an ad hoc group of tags on the fly, and a good system lets them save that arrangement if it proves useful, either privately or for promotion into the shared library after review. The distinction worth keeping is between the curated standing groups everyone relies on and personal or temporary groups, so the shared set stays trustworthy while operators retain the freedom to explore.
Trend groups become even more valuable when the underlying data lives in a cloud historian, because the same configured group can pull recent live values and deep history through one interface. On a platform such as Merobix, a saved group defined by its tags and scales can show the last hour or the last month simply by changing the time span, without the operator reselecting or rescaling anything. The configuration is the durable part; the time window is what the operator moves around within it.
A cloud-hosted group library also travels with the operator across devices and sites. Because the group definition is stored centrally rather than on one console, the same named group opens the same way whether the operator is at the control room screen, on a tablet, or on a phone during a callout, and it can be shared across an operating team so everyone diagnoses the same loop the same way. For an operation spread over many remote sites, having a standard group per site or per equipment type gives operators a consistent starting point wherever they look.
Working over cloud links puts a premium on sensible defaults. Pulling a very long span for many tags at full resolution is heavy, so a well-configured group sets a default time span appropriate to its purpose and relies on the historian to serve reduced-resolution data for wide views and full detail when the operator zooms in. Configuring the group with that in mind means it opens quickly and stays responsive even when the operator is on a modest remote connection.
A multi-pen trend is any chart showing several traces at once. A trend group is a saved, named configuration of a specific set of tags with their scales, axes, colors, and default time span, so it is the reusable definition behind a multi-pen chart. Every trend group is displayed as a multi-pen trend, but the group is the stored configuration an operator recalls by name rather than a chart built from scratch each time.
Enough to tell a coherent story and no more. A group focused on one loop might hold three or four related tags, while a unit overview group might hold several, but crowding a dozen unrelated traces onto one chart makes it hard to read and defeats the purpose. The right number is whatever lets an operator see the relationship the group exists to show without the traces becoming an unreadable tangle.
Usually yes, alongside the curated standing groups. Letting operators assemble and save ad hoc groups supports investigation of unusual problems, and a useful personal group can later be promoted into the shared library after review. The key is keeping the curated standing groups that everyone relies on distinct from personal or temporary ones, so the shared set stays trustworthy and well scaled.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.