Lead-Lag Sequencing: How to Alternate Pumps, Chillers, and Other Equipment Efficiently

What Is Lead-Lag Sequencing and Why Does It Matter

In modern building engineering and industrial automation, operational reliability and energy efficiency go hand in hand. Lead-lag sequencing is a control automation strategy designed to manage multiple identical or complementary equipment working together to meet a variable demand, such as water pumps, chillers (large-scale refrigeration units), or air compressors. In practice, the 'lead' equipment assumes the primary workload, while the 'lag' unit acts as a secondary or standby resource, kicking in only when demand exceeds primary capacity or when a failure occurs. This approach does more than keep cooling or production running smoothly; it serves as the primary defense against premature wear on expensive assets and unnecessary electrical power waste.

Imagine a central air conditioning system in a large shopping center. On the hottest days of the year, a single refrigeration unit cannot handle the load alone, requiring a second unit to start up. If this second unit is always the exact same machine, it will accumulate significantly more runtime than a third unit, causing maintenance imbalances and unexpected downtime risks. Sequencing solves this by dynamically rotating roles among available equipment. Thus, the machine serving as backup today can take the lead tomorrow, ensuring all units age uniformly and maintain their design efficiency over the years.

Operational Mechanics: How the System Makes Decisions

To understand how sequencing works behind the scenes, we must look at the brains behind the operations: PLCs (Programmable Logic Controllers), which are rugged industrial computers built to control machinery and processes in real-time. These controllers continuously receive data from field sensors, such as pressure switches (devices that measure pipeline pressure), temperature sensors, or flow meters. Based on this telemetry, the algorithm calculates whether current demand requires starting a new motor, shutting down an excess unit, or simply swapping operating priorities.

A fundamental concept in this logic is hysteresis, which acts as a safety margin to prevent equipment from frantically cycling on and off when demand hovers right at the threshold limit. For instance, if a water pumping system needs to maintain pipe pressure at 4 bar, a controller without hysteresis would command the backup pump to start the moment pressure drops to 3.9 bar, and shut it off immediately upon rising to 4.1 bar. This constant starting current would quickly destroy the motors. With hysteresis, the system dictates that the backup pump only engages if pressure drops to 3.5 bar and only disengages when it rises to 4.5 bar, ensuring smooth transitions and mechanical longevity.

Rotation Strategies: Time-Based Versus Cycle-Based

Choosing the rotation criteria defines how intelligent and adaptive your control system will be. There are two primary approaches in the building automation and industrial market: time-accumulated runtime rotation and cycle-count rotation. Each approach offers specific advantages that must be evaluated against the dynamic behavior of the load and the physical nature of the machinery involved.

Time-based rotation is the most common and intuitive method. The controller stores the total working hours of each pump or compressor. At predetermined intervals, such as a week or a month, the machine with the lowest accumulated hours is promoted to 'lead' for the subsequent cycle. This works exceptionally well for chillers and chilled water pumps operating continuously over long periods. Conversely, cycle-based rotation suits equipment that starts and stops very frequently, such as air compressors in workshops or sewage lift pumps. In this mode, the priority order shifts after each shutdown event, ensuring the next motor to run is always the one that spent the most time resting.

Practical Code Implementation: Alternation Logic

To illustrate how this logic translates to the digital world, we can look at a conceptual code block in structured text, commonly used in industrial PLCs. The following algorithm demonstrates in a simplified way how alternation between two water pumps is managed based on accumulated operating hours and pressure sensor readings.

// Conceptual example of Lead-Lag alternation logic in a PLC (IEC 61131-3 Structured Text)  PROGRAM PumpSequencing  VAR      PressureSensor : REAL;      // Current pressure sensor reading in bar      Pump1_Hours    : REAL;      // Accumulated operating hours for Pump 1      Pump2_Hours    : REAL;      // Accumulated operating hours for Pump 2      LeadPump       : INT;       // 1 for Pump 1, 2 for Pump 2      SystemDemand   : BOOL;      // True if pressure is below the setpoint  END_VAR  // Automatic determination of Lead pump based on operating hours  IF Pump1_Hours < Pump2_Hours THEN      LeadPump := 1;  ELSE      LeadPump := 2;  END_IF;  // Actuation logic based on demand and chosen lead pump  IF SystemDemand THEN      IF LeadPump = 1 THEN          StartPump(1);          If PressureSensor < CriticalThreshold THEN              StartPump(2); // Lag kicks in as critical auxiliary          END_IF;      ELSE          StartPump(2);          If PressureSensor < CriticalThreshold THEN              StartPump(1); // Lag kicks in as critical auxiliary          END_IF;      END_IF;  ELSE      StopAllPumps();  END_IF;  END_PROGRAM

This code snippet demonstrates conceptual simplicity combined with critical execution requirements. In industrial practice, software robustness relies on additional fault-handling routines, such as jammed rotor detection, overcurrent alarms, and the prevention of simultaneous startups that could overload the facility's main electrical transformer.

Common Pitfalls and How to Avoid Them in Field Engineering

Designing a lead-lag sequencing system sounds simple on paper, but field realities often present challenges that catch engineers off guard. A classic mistake is ignoring fluid dynamics when running pumps in parallel without checking the characteristic curve of the setup. If two centrifugal pumps are started simultaneously in a pipe with severe diameter restriction, the final flow rate does not double; instead, hydraulic friction consumes all extra energy, resulting in electrical waste and cavitation (vapor bubble formation that pits and destroys impeller blades).

Another frequent issue is the lack of contingency testing for sensor failures. If the primary pressure sensor fails and gets stuck sending a low-pressure signal, the controller will mistakenly interpret demand as infinite, cascading machines online until thermal breakers trip from overload. To prevent this, engineers must program cross-validation logic, comparing readings from redundant sensors or using electrical current consumption (measured via Hall-effect transducers) to confirm whether the motor is actually pumping fluid after receiving a start command.

Final Considerations

Lead-lag sequencing goes far beyond simple on-and-off alternation; it represents the backbone of efficiency and reliability in complex electromechanical systems. By integrating smart controllers, hysteresis logic, and clear load-distribution criteria, engineers and maintenance teams can extend the lifespan of expensive assets and prevent costly unplanned downtime. Adopting this approach ensures an industrial and commercial building operation that is sustainable, intelligent, and resilient against unexpected operational challenges.