INFINITE SYSTEMS INSIGHTS:
BMS Sequence of Operations: Control Logic, Points Coordination and Commissioning
A BMS sequence of operations turns mechanical design intent into explicit control logic: when equipment starts, what it modulates, which safeties override normal operation, and what the operator sees when conditions change. A clear sequence connects mechanical design, controls programming, system integration and commissioning.
PLANNING PRINCIPLE
A points list tells the BMS what it can see and command. The sequence of operations tells the system what to do, when to do it, and how it should respond when conditions change.
ENABLE
Schedules, occupancy, demand and equipment permissives.
CONTROL
Setpoints, PID loops, staging and modulation requirements.
PROTECT
Trips, interlocks, safeties and priority overrides.
REPORT
Statuses, alarms, trends and operator response.
01 / PROJECT CONTEXT
What Is a BMS Sequence of Operations?
A BMS sequence of operations is a written description of how controlled building equipment should operate under normal, scheduled, abnormal and emergency conditions. It translates engineering intent into logic that controls programmers, commissioning teams and building operators can understand and verify.
Depending on the project, a sequence may describe equipment enable conditions, start and stop logic, operating setpoints, control loops, staging, interlocks, alarm behavior, failure responses, operator overrides and recovery after abnormal events.
02 / SEQUENCE CONTENT
What a Good Sequence Should Define
Enable Logic
Define schedules, occupancy states, demand conditions, manual commands and permissives required before equipment can operate.
Control Logic
Document setpoints, PID control, valve or damper modulation, fan-speed control, staging and lead-lag requirements.
Safeties & Interlocks
Identify trips, permissives, shutdown conditions and priority overrides that take precedence over normal control.
Alarms & Response
Define alarm conditions, delays, deadbands, priorities, acknowledgements and the expected operator response where applicable.
03 / EQUIPMENT EXAMPLE
Example: Air Handling Unit Sequence
An AHU sequence may define occupied schedules, fan start permissives, proof-of-status timing, supply-air temperature control, chilled-water valve modulation, filter alarm thresholds, smoke or fire shutdown interfaces and recovery behavior after a power interruption.
The sequence may also identify how the system behaves during unoccupied periods, what happens when a temperature setpoint is changed, and how the BMS reports equipment failure or loss of required feedback.
DESIGN NOTE
The exact AHU sequence must be coordinated with the approved mechanical design, equipment submittals, control devices and life-safety interfaces. BMS logic should not override dedicated safety functions unless the approved design specifically defines the interface.
04 / POINTS COORDINATION
Coordinate the Sequence with the Points List
Every required command, status, sensor, alarm and feedback signal referenced by the sequence should have a corresponding physical or network point. A control sequence that depends on unavailable feedback cannot be fully tested or commissioned.
Command
What does the BMS need to start, stop, enable, disable or modulate?
Feedback
How does the system confirm that equipment actually responded to the command?
Condition
Which temperatures, pressures, flows, statuses or other values influence the logic?
The sequence should therefore be reviewed together with I/O schedules, BMS points lists, network integrations, equipment submittals and control panel documentation.
05 / COMMISSIONING
Why Sequences Matter During Commissioning
Commissioning should test cause and response, not simply confirm that values appear on BMS graphics. The team should verify whether the programmed system behaves according to the approved sequence under representative operating conditions.
Schedules
Verify occupied, unoccupied and exception schedules.
Setpoints
Confirm setpoint changes and control responses.
Equipment Proof
Verify commands against actual equipment feedback.
Failure Response
Test alarms, trips, interlocks and recovery behavior.
06 / RETROFIT PROJECTS
Retrofit Projects Need an Existing-Condition Review
In an existing building, the intended sequence may differ from the way equipment currently operates. Before rewriting control logic, the project team should document existing field devices, controllers, network protocols, available points and actual mechanical operation.
The BMS solution should be evaluated against the existing system so that proposed sequences are realistic and compatible with available equipment and interfaces.
07 / MAINTAINABILITY
Keep the Sequence Maintainable After Turnover
A BMS project does not end when programming and commissioning are complete. Operators need current sequences, points lists, graphics, controller information and configuration backups so future troubleshooting and modifications can be performed against an accurate engineering record.
Changes made during operations should be controlled, tested and documented. Periodic review of the programmed logic, alarms, trends and equipment behavior can also form part of preventive maintenance services.
DOCUMENTATION NOTE
The final sequence, points list and as-built BMS documentation should remain consistent with the commissioned system. Undocumented logic changes can make future troubleshooting and expansion more difficult.
08 / PROJECT WORKFLOW
BMS Sequence Development Workflow
01 — Survey
Review equipment, existing controls, field devices, drawings and available documentation.
02 — Define
Establish operating modes, setpoints, schedules, alarms, interlocks and required responses.
03 — Design
Coordinate the sequence with points, controllers, network interfaces and equipment capabilities.
04 — Program
Translate the approved sequence into controller logic, graphics, alarms and operator functions.
05 — Test
Verify commands, feedback, setpoints, alarms, interlocks and abnormal operating conditions.
06 — Commission
Document final results, resolve exceptions and hand over the commissioned system.
09 / PROCUREMENT CHECKLIST
What to Review Before BMS Programming
Sequence
Approved operating modes, enable conditions, setpoints, control logic, interlocks and failure responses.
Points
Commands, statuses, sensors, alarms, feedback signals and network integration points.
Commissioning
Functional testing, alarm verification, interlock testing, documentation and final acceptance requirements.
PROCUREMENT NOTE
When comparing BMS proposals, review the sequence and commissioning scope—not only controller quantities and points counts. Two proposals with similar hardware quantities can have different programming, integration, testing and documentation scopes.
10 / RELATED SOLUTIONS
Related Building Automation Solutions
Building Management System
Coordinate building equipment monitoring, control logic, alarms, trends, graphics and system integration.
Preventive Maintenance Services
Support ongoing system inspection, verification, documentation and maintenance after BMS turnover.
11 / FAQ
Frequently Asked Questions
Who writes the BMS sequence?
Responsibility varies by project. Mechanical designers, controls engineers, consultants and BMS integrators may contribute. The final sequence should be coordinated and approved before programming.
Is a points list enough?
No. A points list identifies data and commands, but it does not fully define operational logic, priorities, interlocks or failure behavior.
Should alarm delays be documented?
Yes. Where applicable, alarm conditions, delays, deadbands and priorities should be defined so nuisance alarms and ambiguous system behavior can be reduced.
Can a sequence change after turnover?
Yes. Changes may be required as building operation evolves, but they should be controlled, tested and documented to maintain system reliability and an accurate engineering record.
What happens if a required point is unavailable?
The sequence should be reviewed against the available hardware and interfaces. Missing feedback may require a design change, additional point, alternative signal or revised sequence before commissioning.
Why is the sequence important for commissioning?
It provides the basis for testing whether commands, feedback, setpoints, alarms, interlocks and recovery behavior match the approved operational requirements.
PLAN YOUR BMS PROJECT
Define the Controls Before Programming
Infinite Systems can coordinate BMS points, sequences, interfaces, graphics and commissioning around the actual building equipment and project requirements.
