A sequence of operation is a written document that describes exactly how a mechanical system should behave under every condition it will encounter. Most commonly used in HVAC and building automation, it spells out the step-by-step logic for starting, stopping, and controlling equipment like air handling units, boilers, chillers, and ventilation systems. Think of it as the instruction manual that tells a building’s control system what to do and when to do it.
While the concept applies broadly to any engineered system, you’ll encounter sequences of operation most often in commercial buildings, where they serve as the bridge between what a design engineer intends and what a controls contractor actually programs.
What a Sequence of Operation Covers
A sequence of operation defines the complete behavior of a piece of equipment across all its operating modes. For an air handling unit, that means describing what happens at startup, how the unit maintains temperature, how it responds to changing outdoor conditions, and what triggers a shutdown. Every input the system reads (sensors, schedules, occupancy signals) and every output it controls (valves, dampers, fan speeds) gets documented with specific logic.
A typical sequence includes several core elements:
- Startup and shutdown procedures: The conditions that must be met before equipment turns on, and the order in which components activate. For example, a unit might require confirmation that all safety circuits are clear before a fan starts through its variable frequency drive.
- Setpoint control logic: How the system maintains desired conditions. An air handling unit sequence might specify that a chilled water valve modulates to hold discharge air at 50°F during cooling, while a preheat coil maintains 60°F during heating.
- Operating modes: How the system behaves differently during occupied hours versus unoccupied hours, or during heating season versus cooling season.
- Economizer logic: When the system can use outdoor air for free cooling instead of running mechanical cooling. This is often based on comparing outdoor and return air conditions.
- Safety interlocks and alarms: The conditions that force equipment to shut down or prevent it from starting, plus what gets flagged to building operators.
How It Works in Practice
To see what a sequence of operation actually looks like, consider a real air handling unit sequence from a federal building project. The document specifies that the unit starts automatically through the building’s digital control system, subject to fire alarm relays, safeties, and overloads. During occupied mode, the outdoor air damper opens to a balanced position and the fan runs continuously within specified setpoints.
For temperature control, the sequence states that the control system modulates a chilled water valve and a hot water valve as needed to maintain the discharge air temperature at setpoint. Fan speed adjusts to maintain constant static pressure measured by a duct-mounted sensor. None of this is left to interpretation. The sequence defines which sensor drives which output, and under what conditions.
The economizer logic in this same sequence gets equally specific: during cooling season, an energy recovery wheel runs continuously when outdoor air has more heat energy than exhaust air. When outdoor conditions drop below that threshold, the wheel shuts off. In winter, the wheel’s speed modulates to prevent frost buildup. Each of these behaviors is a discrete instruction that a controls programmer translates into code.
Safety Interlocks and Alarms
The safety portion of a sequence of operation defines the non-negotiable rules that override normal operation. These interlocks protect both equipment and people. In simple HVAC systems, this might mean a freezestat shutting down an air handler if coil temperatures drop dangerously low. In complex industrial systems, the interlock logic becomes far more detailed.
Safety interlocks work on a permissive basis: certain conditions must be true before an action is allowed. A pump might be automatically tripped offline if pressure conditions indicate it could be damaged by running dry or cavitating. Valves might be locked in position until pressure and temperature drop below acceptable thresholds. When redundant systems exist, interlocks prevent configurations that would compromise that redundancy, such as connecting two backup cooling trains to the same supply header simultaneously.
Alarms are defined alongside these interlocks. The sequence specifies what triggers an alarm (a valve position conflict, a safety threshold breach, a permissive signal changing state) and what information the operator receives. This ensures that when something goes wrong, the building operator sees a meaningful alert rather than a cryptic error code.
Why Standardization Matters
Historically, every engineer wrote sequences of operation differently. The same type of system could be described in dozens of ways depending on who designed it, leading to confusion during installation, commissioning, and maintenance. ASHRAE Guideline 36, titled “High-Performance Sequences of Operation for HVAC Systems,” was created specifically to solve this problem.
Guideline 36 provides uniform, optimized control sequences that have been engineered to minimize energy use while maximizing comfort and indoor air quality. The 2021 version expanded beyond variable air volume systems to include fan-coil units and central hot and chilled water plants, with the long-term goal of covering all common air and hydronic distribution systems.
The benefits of standardization go beyond energy performance. Using a common set of sequences reduces engineering time, simplifies programming and commissioning, and makes it easier for specifiers, contractors, and operators to communicate. A facilities manager who inherits a building controlled by Guideline 36 sequences can understand the logic without deciphering a custom document. Standardized sequences also enable real-time fault detection and diagnostics, because the expected behavior is consistent and predictable enough to flag deviations automatically.
Energy Impact of Good Sequences
The way a sequence of operation is written directly affects how much energy a building consumes. Optimized sequences that adjust setpoints based on actual occupancy rather than fixed schedules achieve around 20% energy savings on average. Occupancy-driven control algorithms have demonstrated reductions of up to 36.8% for heating and 33.9% for cooling compared to fixed, pre-programmed approaches.
Even modest optimization pays off. Research on setpoint strategies found that simply allowing the control system to relax temperature targets by a few degrees when spaces are unoccupied saves roughly 15% on energy while actually improving occupant comfort during occupied hours. These savings come entirely from how the sequence is written, not from upgrading any physical equipment.
Who Writes and Uses Them
The design engineer typically writes the initial sequence of operation as part of the construction documents for a building. It lives alongside mechanical drawings and equipment schedules, giving the controls contractor the logic they need to program the building automation system. During commissioning, a third-party agent tests the installed system against the written sequence to verify that every mode, setpoint, and interlock works as described.
After the building is occupied, the sequence of operation becomes a reference document for facility managers and service technicians. When a system isn’t behaving correctly, the first troubleshooting step is comparing actual behavior to what the sequence says should happen. Over the life of a building, sequences may be revised as spaces change use, equipment gets replaced, or energy targets shift. Keeping the written sequence current with the actual programming is one of the most common challenges in building operations, and one of the most important for maintaining performance.