Introduction to BMS: Difference between revisions
No edit summary |
|||
| Line 52: | Line 52: | ||
The head-end may be installed on a local server or accessed via a web-based interface depending on the system configuration. | The head-end may be installed on a local server or accessed via a web-based interface depending on the system configuration. | ||
=Communication protocols= | |||
=Graphics and user interface= | |||
==Alarms and events== | |||
==Trends and logs== | |||
=Commissioning and handover= | |||
=See also= | |||
Revision as of 00:21, 4 January 2026
What is BMS?
Building Management Systems (BMS) or Bulding Automation System (BAS) are control systems used to monitor, manage, and optimize the operation of mechanical, electrical, and safety systems within buildings. Commonly applied in commercial, industrial, and mission-critical facilities, a BMS integrates equipment such as heating, ventilation, and air conditioning (HVAC), lighting, power distribution, water systems, fire alarms, and security into a single platform. By using sensors, controllers, and communication networks, a BMS enables automated control, real-time monitoring, fault detection, and energy optimization, improving operational efficiency, occupant comfort, system reliability, and overall building performance.
Your role
A BMS Engineer is a job title rather than a strictly defined profession, and the skills associated with the role are largely transferable across multiple engineering disciplines. BMS engineers typically work with control logic, networking, sensors, actuators, and supervisory software - competencies that closely overlap with those used in automation engineering, industrial controls, PLC programming, SCADA systems, and facilities engineering.
Common systems
A BMS typically monitors and controls mechanical, electrical, and environmental services across a facility. The scope varies by building type and project specification, but most platforms include the following:
- Heating, ventilation and air conditioning (HVAC)
- Chilled water and heating plant
- Lighting control
- Electrical monitoring and utility metering
- Water systems and pumps
- Fire and life safety interfaces
Depending on the building's use and complexity, additional systems such as access control, lifts, escalators, solar PV, battery storage, and refrigeration may also be integrated. The extent of BMS coverage is typically defined during the design stage and documented in the project's controls specification.
System architecture
A BMS is structured in layers, typically divided into field level, automation level, and management level. This hierarchy allows data to flow from physical devices up to a central interface where operators can monitor and control building services.
Field devices
Field devices are the physical components installed throughout a building that measure conditions or perform control actions. These include:
- Sensors (temperature, humidity, pressure, CO2, occupancy)
- Actuators (valve and damper motors)
- Variable speed drives
- Meters (electricity, gas, water, heat)
- Switches and relays
Field devices connect to controllers either directly via hardwired inputs and outputs, or through a field bus network.
Controllers
Controllers are the processing units that execute control logic based on inputs from field devices. They make decisions locally, such as adjusting a valve position to maintain a setpoint, and communicate status and data to higher levels of the system.
Common controller types include:
- Plant controllers — dedicated to specific equipment such as an air handling unit or chiller
- Zone controllers — manage multiple terminal units or spaces within an area
- Unitary controllers — smaller devices for single applications such as a fan coil unit
Controllers typically operate autonomously, allowing the building to continue functioning even if the head-end is offline.
Head-end and supervision
The head-end is the central software platform where all system data is aggregated. It provides operators with a graphical interface to view live values, acknowledge alarms, adjust setpoints, and analyse trends.
Key functions of the head-end include:
- System-wide visibility through graphics and dashboards
- Alarm management and event logging
- Historical data storage and trend analysis
- User access control and audit trails
- Scheduling and calendar functions
The head-end may be installed on a local server or accessed via a web-based interface depending on the system configuration.