If you have had a controls project done on your building and nobody handed you a written sequence of operations at the end, that is a problem worth understanding. The sequence of operations (SOO) is the document that defines how your building's controlled equipment should behave under every condition. Without it, the controls programmer made assumptions, and assumptions in a controls system produce outcomes that surprise everyone except the equipment.
What a Sequence of Operations Is
A sequence of operations is a written engineering document that describes, in plain language and engineering detail, exactly how each piece of controlled equipment should operate under every relevant condition: startup, normal operation, setback mode, shutdown, alarm state, equipment failure, and seasonal changeover.
It is not a wiring diagram. It is not a programming printout. It is not the graphics on a front-end screen. It is the document that defines the intent, which the wiring diagram and programming then implement.
A well-written SOO for a variable-air-volume air handling unit, for example, will tell you:
- What conditions are required for the unit to be permitted to start (return air damper must be at least 10% open before the supply fan energizes)
- What the occupied, unoccupied, and standby setpoints are for supply air temperature, static pressure, and space temperature
- How the supply air temperature setpoint resets based on zone demand
- How the economizer damper modulates and what conditions enable and disable economizer operation
- What the freeze protection sequence does when the mixed air temperature drops below 35 degrees Fahrenheit
- What the unit does if the supply air temperature sensor fails
- What alarms are generated, at what thresholds, and with what priorities
Without a written SOO, all of those decisions still get made. They just get made by the controls programmer in the field, based on their experience, preferences, and understanding of the project, which may or may not match what the mechanical engineer designed and what the building owner actually needs.
Why It Matters More Than You Might Think
Every building is different. The AHU sequence that works well in a medical office building is not the same sequence that belongs in a school gymnasium or a hotel ballroom. Equipment characteristics, occupancy patterns, mechanical system design, and local climate all affect what the right sequence of operations looks like.
When a controls programmer works without a written SOO, they default to whatever sequence they have used before. That default may be reasonable for a typical building. It may not be right for your building. And because the assumptions are never written down, there is no clear way to identify the discrepancy until something goes wrong.
We have been called in to diagnose comfort complaints, high energy bills, and equipment cycling issues that traced back to sequences that were functionally incorrect because nobody had defined what "correct" looked like for that specific building. In every case, the programmer did their job competently. They just did not have adequate direction.
What a Complete SOO Includes
A complete sequence of operations for a single piece of equipment typically covers:
Equipment description. What the unit is (unit type, manufacturer, size), where it is located, and what it serves (zones, areas, systems).
Operating modes. Occupied, unoccupied, standby, morning warmup or cooldown, and any special modes specific to the application.
Setpoints. The specific temperature, pressure, humidity, or flow targets for each operating mode, and who has authority to adjust them.
Control loops. What sensor drives what output. The supply air temperature control loop, for example, defines the input (discharge temperature sensor), the output (chilled water valve position), and the control logic (PI loop with specific gain and integral time settings).
Interlocks. Conditions that must be satisfied before equipment starts or changes state. A cooling tower fan should not run if the basin temperature is below 55 degrees Fahrenheit. A supply fan should not start if the associated return fan has failed.
Safeties. High and low limit conditions that cause equipment to shut down or alarm. Freeze protection sequences. Smoke detector interlock responses.
Alarm conditions. What generates an alarm, at what threshold, with what priority (critical, high, medium, low), and who should be notified.
Who Writes the SOO and When
The sequence of operations should be written by the controls engineer or controls contractor during the design phase of a project, before any programming begins. It is then reviewed and approved by the mechanical engineer of record (to verify that it reflects the mechanical design intent) and ideally by the building owner or facilities manager (to verify that it reflects operational requirements).
In a well-run project, the SOO review happens at a formal submittal stage, just like equipment submittals and shop drawings. Comments get incorporated, the SOO gets reissued for approval, and the approved version becomes the binding document that the programmer uses.
In a poorly run project, the SOO is written after the programming is done, as a description of what got programmed. This is backwards. When the document describes what was built rather than defining what should be built, it loses its value as a quality control mechanism.
If your controls contractor cannot show you a written, approved sequence of operations for every piece of equipment they are programming before programming begins, that is a flag worth raising.
The SOO and Commissioning
The sequence of operations is also the primary reference document for the commissioning agent. Two weeks ago we covered ASHRAE Guideline 36, which is essentially a standardized, optimized sequence of operations for common HVAC equipment. Whether your project uses Guideline 36 sequences or custom sequences, the commissioning agent uses the SOO to develop functional performance test procedures.
The test procedures ask: does the system do what the SOO says it should do? If the SOO says the supply air temperature should reset from 55 to 62 degrees Fahrenheit when zone demand decreases, the commissioning test verifies that this happens. If the SOO says the freeze protection should close the outdoor air damper when mixed air temperature drops below 35 degrees Fahrenheit, the commissioning test verifies it.
Without a written SOO, commissioning becomes subjective. The commissioning agent has no defined standard to test against, and the process devolves into a conversation about what seems reasonable rather than a verification of defined requirements.
After the Project Is Done
The SOO should be included in the project closeout documents and kept on file by the building owner indefinitely. When equipment is modified, when a new tenant changes occupancy requirements, or when a future controls contractor is brought in to service or expand the system, the SOO is the starting point for understanding what the system was designed to do.
Buildings that maintain good SOO documentation get better service from every subsequent contractor who touches the controls system. Buildings that cannot find their SOO documentation spend the first hours of every service call figuring out what the previous contractor intended, which is billable time the owner pays for.