From sequence of operation to control architecture

Sequences of operation are necessary and insufficient. “Modulate chilled-water valve to maintain discharge temperature” does not say which PID lives where, what the output does on sensor fail, whether the loop survives loss of the supervisory server, or how the operator commands occupancy. Control architecture is that missing layer: allocation of logic, fail positions, watchdog behaviour, and the network assumptions — see controls architecture.

How the investigation is actually run

Take one air handler or one chiller plant and allocate every clause before you scale. For each clause write the executing device, the inputs, the outputs, the fail action, the operator command path, and whether supervisory must be alive. If a package unit cannot expose a loop, write the interface you will actually get — a setpoint, a status, an alarm — and stop pretending the owner bought the PDF sequence.

Watchdog behaviour and network-loss behaviour are architecture, not “controls flair.” Loops that die when a workstation reboots are a finding. Valves that fail in place when freeze protection required fail-open are a finding. Manual overrides that do not log are a finding. These are not commissioning nits; they are the difference between a sequence and a machine that can be left alone at 2 a.m.

The allocation table is the deliverable. Restating the sequence in nicer English is not. Where vendor topology fights the campus standard, say which one wins and why, in writing, before metal is cut.

Symptoms of sequence-only design

Loops that die when a workstation is rebooted. Valves that fail in place when the designer meant fail open for freeze. Alarms that fire on every communication retry. Manual overrides that are not logged. Related points work: points and sequences.

Causes

Sequences copied from a campus standard that assumed a different vendor topology. Package units whose internal logic is opaque. No statement of what “network loss” means on each trunk. Architecture treated as a later shop drawing.

Investigation

For each clause: executing device, inputs, outputs, fail action, operator interface, and dependence on supervisory. Draw it on the same layers as BAS network architecture. Parent coordination: what Division 25 coordinates. Service home: Division 25.

The written outcome is an allocation table, not a restated sequence. Where the package cannot expose a loop, say so and specify the interface you will actually get.