Operator graphics & dashboards
Floor plans, plant schematics and live values arranged around the tasks the facility team actually performs. Status colours should reflect confirmed feedback, not just commands.
Let’s talk How a BMS is put together, which communication standards it commonly uses and what has to be confirmed before systems can exchange data. Support for any specific device is confirmed at the survey stage.
Controllers should keep running local sequences even if the supervisory layer is offline.
BACnet and Modbus are common, not universal. Device capabilities and point mapping decide what is possible.
| Protocol / interface | Typical use in a BMS | What to confirm |
|---|---|---|
| BACnet/IP | Supervisory network between controllers, servers and compatible equipment such as chillers and VFDs. | Device object list, BBMD / VLAN arrangements, network segmentation. |
| BACnet MS/TP | Field-level RS-485 bus linking unitary and zone controllers. | Baud rate, device count per segment, cable topology and termination. |
| Modbus RTU / TCP | Energy meters, DG sets, UPS, power analysers and many plant-room devices. | Register maps, scaling, data types and polling load. |
| LonWorks | Existing installations that already use LON controllers. | Availability of network tools and whether to retain or migrate. |
| KNX / DALI | Room-level and lighting control where lighting systems use these standards. | Gateway capability, group address and addressing documentation. |
| OPC UA | Structured data exchange with industrial and third-party systems. | Server licences, security policy and tag exposure. |
| MQTT / REST API | Exporting data to analytics, dashboards or enterprise platforms. | Data ownership, authentication method and update frequency. |
Typical examples only. The final scope is set by the equipment survey and the agreed points list.
| Subsystem | Typical monitoring and control points |
|---|---|
| Chillers & central plant | Start/stop, supply and return temperatures, chilled-water pumps, staging, alarms, run hours. |
| AHUs, FCUs & ventilation | Fan status, filter alarms, valve and damper position, supply and zone temperatures, schedules. |
| VRF / VRV & split systems | Run status, setpoints and alarms through the manufacturer’s gateway where available. |
| Pumps, tanks & water systems | Level, pump status, flow, leak or overflow alarms, sewage-treatment-plant status. |
| DG sets, UPS & electrical | Status, load, battery state and alarms through Modbus or BACnet interfaces. |
| Energy & utility meters | kWh, kW demand, power factor, water, gas and BTU readings, trended by time and area. |
| Lighting | Schedules, zone control and occupancy-based control where the installed system allows. |
| Indoor air quality | CO₂, temperature, humidity and particulate sensors for ventilation response and reporting. |
| Fire, access & CCTV (interfaces) | Status or alarm monitoring through defined interfaces only. Dedicated fire and security systems remain independent. |
| Lifts & escalators | Status and fault monitoring through the lift supplier’s interface where one is provided. |
Features depend on the selected platform and licence. They are specified in the project scope.
Floor plans, plant schematics and live values arranged around the tasks the facility team actually performs. Status colours should reflect confirmed feedback, not just commands.
Priorities, delays and escalation rules agreed at design stage. Notifications by email, SMS or messaging apps depend on the chosen platform and its gateway services.
Scheduled reports for runtime, temperature compliance, alarm history and metered consumption by area, compared against a defined baseline.
Browser-based access where the platform supports it, provided over a secured connection that the property’s IT team has approved.
Run-hour counters, filter and fault alerts and short-cycling indicators help plan maintenance. Predictive analytics depend on the data available from each asset.
Data can be shared with analytics or enterprise systems through standard interfaces, subject to licences and data-ownership terms agreed up front.
A BMS network should be designed with the property’s IT team, not alongside it. Common measures include a segregated building-controls network, role-based operator accounts, removal of default passwords, encrypted remote access and logged configuration changes.
Security depends on the product choices and the way the site is operated. These measures are agreed per project and are not a blanket guarantee.
Start with your property, existing systems and operational priorities.