Commercial building and HVAC controls
BMS, Controls and Automation
If schedules, set points, alarms or trend data no longer support day-to-day operations, or new equipment needs to join an existing system, start by mapping the installed controllers, point list, interfaces, access rights and operational constraints before defining the works and tests.
Concept image of BMS and HVAC controls integration; not a record of a customer project.
A useful controls review connects screen data
with field conditions
Controls issues can cross equipment, schedules, sensors, communications and operator actions. Describe what is happening first, then decide whether the next step is a setting change, equipment repair, missing-data review or a defined integration project.
Operating times no longer match the site
Plant starts too early, runs after closing, or a temporary override never expires. Compare the live schedule with operating hours and control ownership.
Alarm volume hides the important issue
Separate the source, priority, recipient and acknowledgement path instead of clearing messages without addressing the cause.
New equipment must join an older system
A shared protocol name does not prove compatibility. Check controllers, software versions, gateways, points and read or write permissions.
Trend data is needed for a decision
Confirm timestamps, units, gaps, sensor condition and retention before relying on the data to compare operation.
Find out what is already there before deciding what to add
Legacy controllers, a central BMS, manufacturer controls and manual operation can all coexist. You can enquire before every record is complete, provided the gaps are identified in the quotation and testing plan.
- Equipment and controllersSystems, models, locations, controllers, gateways, workstations and software versions.
- Drawings and point listsControl diagrams, point schedules, sequences of operation, alarm lists, graphics and change records.
- Data and sensorsTrend intervals, retention, gaps, time sync, units, calibration history and meter data.
- Access and supportAccounts, passwords, licences, engineering tools, backups, vendor support and current owners.
A clear controls scope answers four practical questions
A fair quotation for BMS integration identifies the equipment, points, permissions, responsibilities and acceptance method for each requirement.
Point list and sequence
Identify commands, status, feedback, alarms, interlocks, meters, set points and schedules, together with who supplies, wires, configures and tests each item.
Alarms, schedules and overrides
Set alarm priorities, recipients and acknowledgement, then define weekly schedules, holidays and when temporary overrides expire.
Trends and measurement
Name the points, intervals, retention and export method. If the data is not reliable, do not assume it can support an outcome claim.
Interfaces, access and support
Define protocols, gateways, read or write permissions, network ownership, remote access, backups, rollback and future maintenance responsibility.
Completion needs more evidence than “the system is online”
- 01
Confirm the starting point
Map equipment, controllers, networks, drawings, points, accounts, licences, backups and operating constraints.
- 02
Assign responsibilities
Separate field wiring, panels, programming, graphics, gateways, IT, equipment and third-party work.
- 03
Test against the point list
Check commands, feedback, alarms, schedules, trends, interlocks, permissions and communications, with witness testing where required.
- 04
Hand over usable records
Update drawings, points, settings, backups, account arrangements, test records, operating information and outstanding actions.
Testing depth depends on the project: a point check, full functional acceptance and measured-performance verification are different levels and should be stated separately in the RFQ and quotation.
Trend data can reveal an issue,
but it does not prove savings by itself
Temperature, pressure, valve position, run status, power or flow data can help compare schedules, loads and equipment response. The conclusion still depends on sensor condition, timestamps, units, gaps, a suitable baseline and the measurement method.
Where statutory energy audits, retro-commissioning or consultant acceptance requirements apply, confirm the current requirements against the building and project scope. A BMS is also not the only possible store for measurement data.
- 01Is the data trustworthy?
Check time sync, sensor condition, units and gaps first.
- 02What is being compared?
Define the period, equipment, conditions and baseline.
- 03Were changes recorded?
Separate settings, programming, maintenance and operational changes.
- 04How will results be verified?
Compare before and after through an agreed method, not one dashboard view.
Controls can connect several disciplines;
each task remains separately scoped
You can describe the whole requirement in one RFQ. The quotation should then separate each discipline, supplier and site owner’s responsibility.
Fixed electrical work and field wiring
Power, protection, isolation, distribution, fixed wiring and related tests remain a separate work scope. See electrical and HVAC supporting works.
HVAC equipment and mechanical systems
Equipment condition, repair and replacement for VRV or VRF, chillers, AHUs, PAUs, FCUs, pumps and valves stay with the relevant equipment scope. Learn about VRV or VRF systems where appropriate.
IT, OT and remote access
Networks, account privileges, remote access, Internet gateways, logs, backups and change control need the site IT or OT owner’s approval. No connection method should be assumed.
Fire and other building interfaces
Interlocks or data exchange with fire, lifts, security, access control, tenant or landlord systems must follow the original design, responsible owner, approval and testing procedure.
Installed-system information helps us
define the scope sooner
- Site and operationsUse, floors, operating hours, critical zones, available work period and test windows.
- Equipment and architectureHVAC or M&E systems, controllers, gateways, workstations, networks and current vendors.
- Documents and accessDrawings, point lists, control sequences, alarm lists, accounts, licences, backups and O&M information.
- Issue and objectiveAlarm, schedule, data, interface or operational problems and the first decision you need to make.
- Trends and measurementAvailable exports, intervals, retention, meters, sensors and existing audit or RCx requirements.
- Acceptance and handoverWitnessed functions, reports, as-builts, backups, training, access arrangements and handover format.
BMS, controls and automation FAQ
If a system says BACnet, can it connect directly?
A protocol name alone does not confirm direct connection. Check device capabilities, software versions, networks, gateways, point mapping, read or write permissions, licences and field-test results.
Which controls information can we provide first?
Start with the installed controllers, BMS screens, equipment information and main issue. The quotation can separate discovery, point verification and information required from other owners.
Does adding trend data prove energy savings?
No. Confirm data quality, the baseline, comparison conditions, actual changes and the measurement method before drawing a conclusion.
Are remote monitoring or mobile alerts automatically included?
No. Remote access, cloud connections, accounts, notifications, networks, security, support arrangements and fees all need to be confirmed for the site and system.
Must every legacy controller be replaced?
Not always. Review condition, supportability, licences, backups, spare parts, interfaces and the project objective before comparing retention, partial renewal, gateways or full replacement.
What should the handover include?
Based on the works, it can include updated point lists, sequences, alarm and schedule lists, as-builts, settings, backups, account arrangements, test records, operating information, training and open actions.
Tell us what is installed and which decision you need to make
Share the site, equipment, controllers, point list, alarms, schedules, trend data and shutdown constraints. We can review the available information first, then identify what site, interface and test information is still needed.