HVAC & plant
Chillers, AHUs, FCUs, pumps and VRF gateways. Temperatures, status, valve and damper feedback, schedules and alarms.
Let’s talk A connected screen is the beginning, not the outcome. Define the operating sequence, test the equipment response and give the facility team the information to run the building.
Switch system layers on and off to see how HVAC, energy, lighting, access interfaces and water services each reach the same operator view. Drag to rotate, double-click to reset.
Illustrative model, not a customer site. Real topology, device counts and communication paths are defined after the site survey.
Typical examples only. Scope is set by the equipment survey and points list.
Chillers, AHUs, FCUs, pumps and VRF gateways. Temperatures, status, valve and damper feedback, schedules and alarms.
Electricity, water, gas and thermal meters, plus DG sets and UPS. Consumption by area and time, demand and power-factor trends.
Zone schedules and occupancy-based control where the installed lighting system supports it, with manual override kept distinct.
Status and alarm monitoring through defined interfaces. Dedicated access, fire and CCTV systems remain independent.
Tank levels, pump status, leak and overflow alarms, STP and other utility plant where connected.
Good controls connect a measurable operating problem with a practical response—not a dashboard alone.
Trend metered consumption alongside plant schedules. Investigate equipment running outside occupancy hours and compare results against a defined baseline.
Review temperature trends and repeated comfort complaints together. Check sensors, setpoints and equipment response before changing the control strategy.
Prioritize equipment exceptions and define who responds. Repeated nuisance alarms and persistent overrides deserve investigation, not permanent acknowledgement.
Establish equipment, existing controls, occupancy hours and the problems the facility team needs to solve. For an occupied site, identify access constraints and acceptable shutdown windows.
Agree the points to monitor and control, operating sequences, alarm priorities and integration boundaries. Check communication capabilities and responsibilities before specifying hardware.
Test sensor readings, commands, feedback, schedules and alarms against the approved sequence. Record exceptions and retest corrections before accepting the system.
Set out operator access, drawings, configuration backups and routine tasks. Review operating trends after the building is in use and document any changes to schedules or setpoints.
Open communication standards such as BACnet help compatible building devices exchange information. They do not remove the need to check device capabilities, point mapping, software licences and integration testing.
Agree network access with the property’s IT team. Define operator permissions, remote-access arrangements, backups and change records. Independent equipment protections and dedicated life-safety controls must remain intact.
The principles are the same. The discipline matters more as the point count grows.
Design one standard sequence, graphic and alarm set for each equipment type (AHU, chiller, meter). Reuse it across buildings so operators see the same thing everywhere.
Prove the design on one building or floor, correct what the pilot teaches, then replicate in agreed phases. This reduces risk on occupied sites.
Separate field buses, building-level networks and the campus backbone. Define bandwidth, redundancy and how each building behaves if the backbone is unavailable.
Controllers run their own sequences. A loss of the central server should not stop plant from operating or manual override from working.
One operator view across buildings with roles per site, tenant or contractor, so people see and change only what they are responsible for.
For owners with buildings in several cities, consistent naming, graphics and reporting make comparison possible and allow a central team to support local sites.
Large installations succeed or fail on consistency. Agree these rules before the first point is wired.
Open tagging approaches such as Project Haystack or Brick Schema can help structure data for analytics. Whether they are used is agreed per project.
The more points a system has, the more important it is to filter what reaches people.
Group related alarms, set delays and priorities, and review nuisance alarms regularly. Operators should be shown what needs action, not everything that changed.
Highlight equipment running out of hours, persistent overrides, drifting sensors and comfort complaints by zone, rather than expecting people to read every trend.
Agree who reviews consumption against the baseline, how often, and what actions follow. Record changes so results can be traced to causes.
Summaries for owners and boards: availability, alarm response, energy against baseline and open actions, in language that does not need a controls background.
Exact documents are listed in the project scope. This is a typical set.
| Stage | Typical deliverables | What we need from you |
|---|---|---|
| 1 · Survey | Equipment inventory, existing-controls assessment, site constraints and a list of operating problems to solve. | Site access, existing drawings, operating hours, a facility contact. |
| 2 · Control strategy | Points list, control sequences, alarm priorities, network architecture and integration boundaries. | Review and sign-off, IT network requirements, tenant and safety constraints. |
| 3 · Install & prove | Installed field devices and panels, point-to-point and functional test records, an exceptions log with retests. | Shutdown windows, coordination with other trades, witness attendance for key tests. |
| 4 · Handover & review | As-built drawings, configuration backups, operator instructions, training record and a post-occupancy trend review. | Named operators for training, agreement on support and review arrangements. |
Agree these at kick-off and record them in the scope.
Provide access, drawings and decisions on schedules and setpoints. Nominate who can approve changes and who responds to alarms.
Survey, design the control strategy, install and integrate the BMS, commission it, document it and train the operators within the agreed scope.
Mechanical and electrical contractors supply equipment interfaces. IT approves network access. Suppliers confirm protocol support and licences for their devices.
Each item is tested against the approved sequence and recorded, not assumed from a screen colour.
Raising them early keeps the project on track.
Drawings often differ from what is installed. The survey verifies equipment and wiring before design is fixed.
Proprietary or obsolete controllers may need a gateway or replacement. Licences and access rights are checked up front.
Late IT approval is a common cause of delay. Network requirements are shared at the strategy stage.
Controls depend on plant being installed and running. Test dates are planned with the other contractors.
Work in occupied buildings is phased around operating hours and agreed shutdown windows.
Start with your property, existing systems and operational priorities.