A compressor station with several units rarely needs all of them running at once. Demand rises and falls through the day and the season, and running more machines than the load requires burns fuel and wear for no benefit. Station unit sequencing is the logic layer that decides which units run, in what order they come on, and when a running unit should shut back off. This page explains the lead, lag, and standby roles, how the station adds and sheds units on demand, how run hours are balanced across the fleet, and how recycle-aware staging keeps the transitions clean.
Station Unit Sequencing in one line: Station unit sequencing is the station-level control logic that decides which compressor units run and in what order, assigning each unit a lead, lag, or standby role. The lead unit carries the base load, lag units are added as demand rises and shed as it falls, and standby units wait ready to cover a trip or a peak. The sequencer stages units in and out on demand thresholds, rotates the running order to balance run hours across the fleet, and coordinates with each unit's recycle so machines start into and shut out of the station load smoothly.
The three roles describe how a unit participates in meeting station demand at any moment. The lead unit is the one carrying the base of the load; it runs whenever the station is producing and it is the reference against which the station's pressure or flow target is held. The lag units are the additional machines brought on when the lead alone cannot meet demand, layered in one at a time as the load climbs and taken back off as it falls. A standby unit is not running but is proven ready to start, held in reserve to cover a sudden demand spike or to take over if a running unit trips.
These roles are assignments, not fixed identities. The physical machine that is lead today may be rotated to standby tomorrow so the fleet wears evenly, which is why the sequencer tracks roles separately from unit numbers. A unit that is currently lag can be promoted to lead if the sequence rotates, and a standby unit becomes the next-to-start whenever demand calls for another machine. Keeping the roles abstract lets the same staging logic work regardless of which specific units are healthy and available on a given day.
The station also has to decide the order in which units take each role, and that order is where run-hour balancing and unit availability come in. A unit that is out for maintenance is removed from the sequence entirely so it is never selected as the next to start. A unit fresh from an overhaul might be favored to take load, or deliberately held back to bed in, depending on the operator's policy. The role assignment therefore reflects both the instantaneous demand and the longer-term condition and duty history of each machine.
The heart of sequencing is deciding when to add a unit and when to shed one. The station watches an indicator of whether the running units can meet demand, commonly the position of the running machines against their capacity: when the lead and any running lag units are pushed toward their maximum and the station still cannot hold its pressure or flow target, that is the signal to start the next unit in sequence. Conversely, when the running units are throttled well back and one could be removed without the rest saturating, the sequence sheds a unit. Deliberate thresholds and time delays sit around both decisions so the station does not chase every short-lived swing.
Gas compressor staging is recycle-aware in a way that pump staging is not, and that shapes the logic. A centrifugal compressor being started or stopped passes through its recycle path so it never operates below its surge limit, which means adding or removing a unit is not instantaneous. When a new unit is staged in, it comes up on recycle, matches the station pressure, and only then closes its recycle to take real load, so the sequencer must account for the transition time and avoid double-counting capacity that is not yet loaded. When a unit is de-staged, it opens recycle and unloads before it stops, so its share of the load has to be picked up by the remaining machines as it backs out.
Because of this, well-designed staging leaves margin and uses delays so the running fleet can absorb the load handed off during each transition without tripping on surge or overpressure. Adding a unit too late leaves the running machines saturated and the station short; adding one too early wastes a start and runs an extra machine on heavy recycle. Shedding a unit too aggressively can overload the survivors. The thresholds, the hysteresis between add and shed points, and the transition timing are all tuned so the station stages up and down smoothly rather than hunting between counts.
Left alone, a fixed start order would run one unit hard and leave others idle, so the sequencer rotates the order to balance accumulated run hours across the fleet. Each time the station returns to a lower unit count or on a defined rotation event, the logic can reshuffle which unit is lead and which is next to start, favoring the machine with the fewest hours or the shortest time since last run. Over weeks this evens out the duty so maintenance intervals line up and no single machine carries a disproportionate share of the wear.
Rotation policy is a balance in itself. Rotating too eagerly means more starts and stops, and each start puts its own stress on a machine, so the sequencer weighs the benefit of even hours against the cost of extra start cycles. Some stations rotate only on natural stops rather than forcing a running unit off just to swap duty, while others rotate on a schedule. The logic also has to respect availability, skipping any unit that is locked out, in fault, or otherwise not proven ready, so the rotation never selects a machine that cannot actually start.
For the operator and for remote monitoring, the sequencing layer is best understood as a live picture of the station's intent, not just its state. A SCADA or cloud view shows which unit holds each role, how close the running units are to the next add or shed threshold, the accumulated run hours driving rotation, and which units are available to be called. A platform such as Merobix records these role transitions and staging events over time, so a station that is cycling units more often than it should, or leaning on one machine despite the rotation logic, shows up as a trend that operators can act on before it becomes uneven wear or an unexpected outage.
The lead unit carries the base of the station load and runs whenever the station is producing. Lag units are additional machines brought on one at a time as demand rises and shed as it falls. A standby unit is not running but is proven ready to start, held in reserve to cover a demand spike or to take over if a running unit trips. These are roles that rotate among the physical machines rather than fixed identities.
The station watches whether the running units can still meet demand, usually by how hard they are working against their capacity. When the running machines are pushed toward their limit and the station still cannot hold its pressure or flow target, the sequencer starts the next available unit. Time delays and thresholds sit around the decision so the station does not add a machine in response to a brief swing, and the new unit comes up on recycle before it takes real load.
Rotation balances accumulated run hours across the fleet so no single machine carries all the duty and wears out first. By periodically reshuffling which unit is lead and which is next to start, favoring the machines with the fewest hours, the sequencer keeps maintenance intervals aligned across the units. The logic weighs even hours against the cost of extra starts, and it always skips any unit that is locked out or not proven ready.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.