06 / Braincord Systems

Open protocols. Defined interfaces. Documented points.

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.

System architecture

From field device to operator screen.

Controllers should keep running local sequences even if the supervisory layer is offline.

1 · FIELD LEVEL Temperature & humidity sensorsCO₂ / air-quality sensorsValves, dampers, actuatorsEnergy & utility metersEquipment status inputs 2 · CONTROLLERS Run control sequences locallyKeep running if the networkor server is unavailableBACnet MS/TP · Modbus RTULocal manual override 3 · SERVER / GATEWAY Protocol gatewaysTrend & alarm databaseScheduling & user rolesBACnet/IP · OPC UA · MQTTBackups & audit logs 4 · OPERATORS Operator graphics & dashboardsAlarm notificationsReports & energy trendsSecured remote accessThird-party / API export Illustrative architecture. The actual topology is defined after the equipment survey and agreed with the property’s IT team.
Protocols & integration

Standards help. Testing proves it.

BACnet and Modbus are common, not universal. Device capabilities and point mapping decide what is possible.

Common BMS communication protocols and what to confirm for each
Protocol / interfaceTypical use in a BMSWhat to confirm
BACnet/IPSupervisory network between controllers, servers and compatible equipment such as chillers and VFDs.Device object list, BBMD / VLAN arrangements, network segmentation.
BACnet MS/TPField-level RS-485 bus linking unitary and zone controllers.Baud rate, device count per segment, cable topology and termination.
Modbus RTU / TCPEnergy meters, DG sets, UPS, power analysers and many plant-room devices.Register maps, scaling, data types and polling load.
LonWorksExisting installations that already use LON controllers.Availability of network tools and whether to retain or migrate.
KNX / DALIRoom-level and lighting control where lighting systems use these standards.Gateway capability, group address and addressing documentation.
OPC UAStructured data exchange with industrial and third-party systems.Server licences, security policy and tag exposure.
MQTT / REST APIExporting data to analytics, dashboards or enterprise platforms.Data ownership, authentication method and update frequency.
Connectable subsystems

What a BMS can monitor and control.

Typical examples only. The final scope is set by the equipment survey and the agreed points list.

Building subsystems a BMS can commonly connect to
SubsystemTypical monitoring and control points
Chillers & central plantStart/stop, supply and return temperatures, chilled-water pumps, staging, alarms, run hours.
AHUs, FCUs & ventilationFan status, filter alarms, valve and damper position, supply and zone temperatures, schedules.
VRF / VRV & split systemsRun status, setpoints and alarms through the manufacturer’s gateway where available.
Pumps, tanks & water systemsLevel, pump status, flow, leak or overflow alarms, sewage-treatment-plant status.
DG sets, UPS & electricalStatus, load, battery state and alarms through Modbus or BACnet interfaces.
Energy & utility meterskWh, kW demand, power factor, water, gas and BTU readings, trended by time and area.
LightingSchedules, zone control and occupancy-based control where the installed system allows.
Indoor air qualityCO₂, 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 & escalatorsStatus and fault monitoring through the lift supplier’s interface where one is provided.
Platform capabilities

What operators and owners get.

Features depend on the selected platform and licence. They are specified in the project scope.

01

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.

02

Alarm management

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.

03

Trends, reports & energy analytics

Scheduled reports for runtime, temperature compliance, alarm history and metered consumption by area, compared against a defined baseline.

04

Remote and mobile access

Browser-based access where the platform supports it, provided over a secured connection that the property’s IT team has approved.

05

Maintenance insight

Run-hour counters, filter and fault alerts and short-cycling indicators help plan maintenance. Predictive analytics depend on the data available from each asset.

06

Open data export

Data can be shared with analytics or enterprise systems through standard interfaces, subject to licences and data-ownership terms agreed up front.

Cybersecurity & access control

Connected buildings need
a defined security model.

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.

  • Network segmentation between BMS, corporate and guest networks
  • Role-based permissions and individual operator accounts
  • Secured remote access, with no direct exposure of controllers to the internet
  • Audit logs, configuration backups and a patching and change-control process

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.

Define the right BMS scope for your building.

Start with your property, existing systems and operational priorities.

Discuss your project