A Building Management System in Plain Terms

On this page

1. 01Before you start
2. 02Where it sits in the project
3. 03BMS, BAS, EMS, SCADA and smart building
4. 04Three-level architecture
5. 05Main components
6. 06BMS points: design and pricing foundation
7. 07Communication protocols
8. 08Sequences of operation (SOO)
9. 09Integration methods
10. 10Network design: IP and RS-485
11. 11Pre-sales, sizing, energy classes and BOQ
12. 12Installation and commissioning
13. 13Check that it works
14. 14Common problems and how to fix them
15. 15Frequently asked questions
16. 16Talk to PSS about BMS

A Building Management System — BMS, also called BAS or BACS — brings selected building services onto a common platform for monitoring, control, alarms, scheduling, reporting and integration. It reads sensors, executes time schedules and control sequences, commands valves, dampers and drives, and records what happened.

It is not a safety system: it replaces neither a fire alarm panel nor the factory protections inside a chiller or boiler.

Think of a building as a body: mechanical and electrical equipment are the organs; sensors are the senses; controllers decide; actuators and relays act; the supervisory platform gives the operator a central view.

Meeting-room example. Occupancy and people load raise temperature. A temperature sensor and occupancy sensor feed a DDC controller. The controller follows its sequence to adjust HVAC. When the room is empty, the system may change mode to cut unnecessary energy use — if ventilation, humidity and equipment protection still allow it. Without automation, plant often runs “high” on fixed schedules alone.

Integration is three agreements under one word: a protocol agreement (transport, baud, object model), a point agreement (values, direction, units, update rate), and a behaviour agreement (sequences and alarm logic, written and signed). Skip any one and the site gets a gateway that talks perfectly and a building that still does not work.

Before you start

• Building type, plant list (AHUs, chillers, pumps, VAVs) and which OEM packages already have their own controllers.
• Monitoring versus control for each system; energy/trending scope; workstations and remote access.
• Draft points list (physical vs network vs software) and sequences of operation (SOO) — not brand names alone.
• Protocols in play: BACnet, Modbus, KNX, DALI, LonWorks, OPC UA — and which gateways are needed.
• Network: IP addressing/VLANs for BACnet/IP or Modbus TCP; RS-485 rules for MS/TP or Modbus RTU.
• Life-safety interfaces (fire, smoke control) — monitored only where approved; BMS does not replace the FACP.
• Who owns firmware, logins and vulnerability notices on every gateway; IT acceptance of the supervisory server.
• Acceptance: point-to-point tests, functional sequences, trends, as-builts and training.

Where it sits in the project

The BMS sits between equipment and operator. Upstream: mechanical schedule, electrical panels and vendors’ own controllers. Downstream: facilities — and client IT, because a supervisory server with an IP address is an IT asset.

Integration sits between vendor packages (chillers, VRV, VFDs, meters, fire, access, lifts) and the supervisory layer. Security and life-safety usually arrive on the building IP network: fire (EN 54-2, monitored only), intrusion (EN 50131), access and CCTV — which pulls PoE budgets and TIA-568 cabling into the same design.

In practice the package is defined by the points list and the sequences of operation, not the hardware brand. If those two are weak, no platform saves the project.

BMS, BAS, EMS, SCADA and smart building

Term	Meaning	Typical focus
BMS	Building Management System	Monitoring, control, alarms, scheduling, integration
BAS	Building Automation System	Equipment control and automation logic (often used interchangeably with BMS)
EMS	Energy Management System	Metering, analysis, reporting, optimisation (standalone or BMS module)
SCADA	Supervisory Control and Data Acquisition	Industrial/process visualisation and deterministic control
Smart Building Platform	Broader digital layer	Automation + analytics + occupancy and connected services

Criterion	BMS	EMS	SCADA
Primary job	Control building services	Measure, analyse, report energy	Control an industrial process
Typical protocol	BACnet, Modbus, KNX	Modbus, M-Bus, OPC UA	Modbus TCP, PROFINET, EtherNet/IP, OPC UA
Timing demand	Seconds to minutes	Minutes to months	Milliseconds, deterministic
Typical user	Facilities engineer	Energy manager	Process operator

The important question is not the platform name — it is which functions, which connected systems, and which responsibilities belong to each subsystem. A hospital can legitimately run BMS, EMS and SCADA together.

Three-level architecture

Conceptual layers — real products may combine them.

Field level

Sensors, switches, meters, actuators, VFDs and equipment interfaces. They connect via physical I/O or a network protocol (e.g. room temperature as resistance/voltage into a DDC; a meter over Modbus).

Automation level (DDC)

Direct Digital Controllers receive measurements, evaluate conditions and issue commands per configured sequences. They may run an AHU, pumps, ventilation or another application. Design which loops continue if the central server is down — resilience is not automatic; it depends on where the logic lives.

Management level

Server or supervisory controller, database/historian, workstations, web graphics, floor plans, alarms, schedules, trends, reports, permissions, energy dashboards and selected integrations. The management layer presents and coordinates; field controllers and plant do the real-time work.

Logical flow: Field devices → DDC / equipment controllers → communication network (BACnet, Modbus, IP, RS-485, gateways) → BMS server / supervisory software → operator interface (graphics, alarms, trends, schedules, reports). Paths are often bidirectional; some equipment may connect straight to supervisory systems or gateways.

Main components

Sensors

Convert a physical condition into a signal or digital value.

Sensor	Typical application
Temperature	Room, supply/return air, chilled/hot water
Humidity / CO₂ / occupancy	IAQ, humidity control, demand ventilation
Pressure / ΔP / airflow	Filters, ducts, pressure relationships, ventilation
Leak / level / power	Plant rooms, tanks, electrical loading

Select for range, accuracy, response, environment, output type and controller compatibility. A good sensor in a bad location (sun, heat source, no airflow) still misleads control.

Actuators

Move valves, dampers or other mechanisms. Verify supply voltage, control signal, torque, travel time, fail position, mechanical fit and feedback. A 0–10 V command alone does not prove compatibility — signal type, common, loading and operating requirements must match.

DDC controllers and panels

Fixed-I/O, expandable, application-specific or freely programmable. Match I/O mix (not only total points), signal types, protocols, ports, expansion, panel space, power, environment and local recovery. Panels hold controllers, PSUs, terminals, interface relays, protection and network gear — with segregation, grounding, labelling, heat dissipation and clear I/O/terminal schedules. Where a controller cannot safely drive a load, use a suitable interface relay.

BMS points: design and pricing foundation

A point is a named item the system monitors, commands, calculates or manages. Points drive available information, control scope, controller sizing, configuration and testing — but point count alone does not set the full price (hardware, licences, integration, graphics, install, commissioning also matter).

Four physical I/O types

• DI / BI — discrete status (fan run, pump fault, filter dirty, leak contact).
• DO / BO — discrete command via a suitable interface (fan enable, pump start). Verify ratings.
• AI — variable measurement (temperature, humidity, pressure, 0–10 V or 4–20 mA, resistance sensors where supported).
• AO — variable command (valve, damper, VFD speed reference). Do not assume every modulator accepts 0–10 V.

Physical, network and software points

Physical I/O uses controller terminals. Network points arrive over a protocol (chiller status, VFD speed feedback, meter kWh). Software points are calculated or created (setpoints, ΔT, timers, occupancy flags, derived alarms). One VFD may expose many network values without many terminals — yet hardwired safeties/permissives may still be required.

Worked AHU example (illustrative)

Point	Type	Function
Supply / return air temperature	AI ×2	Monitor
Filter ΔP	AI	Filter condition
Fan run / fault	DI ×2	Status and alarm
Fan enable	DO	Request operation
CHW valve / damper	AO ×2	Modulate

Physical I/O = 3 AI + 2 DI + 1 DO + 2 AO = 8. A real AHU often adds fan speed, duct static, freeze protection, valve feedback, smoke interfaces, etc. BACnet/Modbus may move some values to network points — the approved design decides.

Typical hardwired planning counts: 15–20 points per VFD AHU, 4–6 per VAV, 3–6 per pump, 8–12 per chiller if safeties are hardwired. Spare 10–25% per point type per controller (ASHRAE Guideline 13 practice; 20% commonly specified). Spare is local — AHU-01 spare does not help AHU-04.

A useful record: equipment tag, point name/function, category, physical vs network, signal/units, range, alarm limits/delays, R/W, source device/protocol, sequence reference, test requirements. The I/O schedule adds controller, module, terminal, cable, field tag and panel location — coordinated with drawings and SOOs.

Communication protocols

Openness is a claim until you see paper: PICS and BIBBs for BACnet (ANSI/ASHRAE 135 / ISO 16484-5), register maps for Modbus, ETS/group addresses for KNX, XIF for LonWorks. Prefer COV over blind polling where available; add a BBMD when BACnet/IP crosses IP subnets.

Protocol / interface	Typical use	Hard limits / checks
BACnet/IP · MS/TP	Controllers, chillers, AHUs	UDP 47808; MS/TP 32 devices / 1,200 m per RS-485 segment; verify objects, writable properties, BTL where claimed
Modbus RTU · TCP	Meters, VFDs, generators, UPS, PLCs	247 slaves, 32/segment; port 502; no native security; exact register map, scaling, word order
KNX	Lighting, blinds, room control	TP1 9,600 bps; 64 devices/line segment, 15 lines/area; group addresses + DPT
DALI	Digital lighting	Often via KNX–DALI or other gateway; verify addressing, dimming, faults, licences
LonWorks	Legacy plant, VAV	FT-10 78 kbps; 128 devices/channel; SNVT typing
OPC UA	Historian, ERP, analytics	IEC 62541; TCP 4840 + TLS; defined information model
ONVIF / vendor API / SIP	Selected CCTV, access, intercom	Not a universal BMS protocol — confirm events, commands, licences

If two systems do not share a row, price a gateway and a mapping sheet. Check capacity, R/W, scaling, update rate, licences, diagnostics and failure behaviour — not just matching protocol names.

Sequences of operation (SOO)

An SOO defines behaviour in normal operation, startup/shutdown, demand changes and faults: enables, schedules, setpoints/limits, order, modulation/staging, alarms/delays, interlocks/permissives, failure/recovery, overrides, and behaviour on communication or power loss. “Provide BMS control for the AHU” is not a sequence. ASHRAE Guideline 36 is a useful HVAC reference and point-list reality check.

Illustrative AHU sequence

1. Check schedule and permissives.
2. Start dampers/fan per mechanical design.
3. Confirm run status within time — else alarm and approved response.
4. Modulate CHW valve from supply-air temperature vs setpoint (PID/deadband as designed).
5. Monitor points, trends and alarms.
6. Ordered shutdown on schedule end or authorised stop.
7. Fault handling and recovery only under defined conditions.

May also include economizer, frost protection, minimum ventilation and smoke interlocks.

Economizer / free cooling

Do not enable solely because outdoor air is below a fixed temperature. Typical checks: AHU enabled; outdoor conditions suitable (dry-bulb, enthalpy and/or humidity per strategy); cooling needed; OA quality allows; dampers modulate per sequence; mechanical cooling reduced only when economizer can meet demand and equipment protection allows. Do not shut the chiller on an arbitrary outdoor threshold alone.

Lead/lag pump

Determine circulation need → select duty pump → command → confirm status → start standby on approved failure → alarm/record → rotate by hours/priority. Respect minimum flow, chiller permissives, valves, ΔP and OEM limits.

VFD points (example)

Start/stop, run, fault, speed reference, speed feedback, current/power, fault code — via hardwire, BACnet or Modbus. Define which are writable and behaviour on comms loss.

Integration methods

• Hardwired — dry contacts / enables / faults. Simple, but more wiring and fewer values.
• Protocol-based — many values on one link when the OEM exposes them.
• Gateway — when protocols differ; map points, R/W and failure mode.
• API / software — dashboards, analytics, selected security; plan auth, versions, security and long-term support.

External system	Example data to BMS	Possible BMS command
Chiller / VFD / meter	Status, temps, alarms, energy	Approved enable/setpoint/speed where supported
Lighting (KNX/DALI)	Status, occupancy, faults	Switching, dimming, scenes where supported
Access / CCTV	Selected events or links	Only documented, approved functions
Fire alarm	Selected status/events	Only approved life-safety interfaces — BMS does not replace FACP

Also record source/destination, method, R/W, update rate, interface owner, licences, failure behaviour and acceptance tests. Life-safety (smoke control, dampers, pressurisation) follows the fire strategy and specialists — never assume a generic BMS command is suitable.

Split ACs: possible via OEM interface/gateway (preferred when feedback is needed), IR gateway (command ≠ confirmed execution), or third-party thermostat — check warranty, safety and feedback. Do not treat IR-only as equal to wired/network confirmation.

Network design: IP and RS-485

IP (BACnet/IP, Modbus TCP): addressing, VLANs/segmentation, routes/firewalls, naming, remote access, diagnostics, cybersecurity roles. Do not expose controllers to the public internet or treat them as fully trusted because they are “inside the building.” IEC 62443 zones and conduits remain the working security frame.

RS-485 (MS/TP, Modbus RTU): cable, polarity, baud/parity, addressing, daisy-chain topology, termination at the two physical ends only, biasing, grounding, loading and length. Star wiring, wrong termination or mismatched settings cause intermittent faults. Device A/B labels are not universal — use the OEM manual.

Two devices can share a protocol name and still miss objects, registers, write rights, drivers or licences. Verify interoperability against PICS / register maps / group addresses — not brochure logos.

Pre-sales, sizing, energy classes and BOQ

1. Understand building type, plant, OEM packages, existing BMS, monitoring vs control, energy/trending, integrations, workstations/remote access, standards and acceptance.
2. Collect drawings, schedules, schematics, SOOs, point lists, network architecture, manuals and licence requirements — list clarifications; do not invent scope to fill a quote.
3. Build the point list (physical vs network vs software; R/W; test method).
4. Select controllers for I/O mix, signals, expansion, ports, panel/power, spare and local failure behaviour.
5. Define hardwired vs protocol vs gateway; drivers, maps, PICS, R/W and contractor responsibilities.
6. Price the complete job — not points alone.

Trend storage honesty: trends × samples/hour × retention. One thousand trends at one-minute resolution → 1.44 million samples/day.

Energy classes: EN ISO 52120-1 (formerly EN 15232) rates BACS A–D with C as baseline. Published factors place class A roughly 25–30% below C on thermal energy and ~13% on electricity; class B ~15–20% thermal. Planning ranges, not guarantees — they describe control capability, not commissioning quality.

Typical BOQ buckets: DDC + modules; sensors/actuators; relays; panels/PSUs; switches/gateways; server/workstation; software/licences; graphics/programming/SOO; integration engineering; cabling; testing/commissioning; documentation/training. State inclusions, exclusions, assumptions and who supplies OEM sensors/panels/network gear.

A 500-point project can cost more per point than a 5,000-point one when integration and engineering dominate.

Installation and commissioning

Pre-commissioning: models, panel wiring vs drawings, device locations, actuator mechanical checks, power/protection, network addressing, final point list/SOO, licences/tools, safe test windows.

Point-to-point: for a temperature sensor — model/wiring, reference instrument, input config, units, change under approved test, alarms/trends, record. For outputs — command, interface, equipment response, feedback. For network points — source vs BMS, mapping, scaling, update rate.

Functional tests: schedule start/stop, fan confirm, temperature response, alarm ack, simulated fault and recovery, behaviour on comms/power loss where required. Document expected vs actual, deficiencies and retests.

Handover: as-builts, final point list/I/O, controller and network backups, final SOOs, addressing/integration info, register maps, alarm/trend config, test records, licences, training. Transfer credentials securely.

Check that it works

• Every critical point passes point-to-point with correct units, scaling and direction (R/W).
• Sequences start, modulate, alarm and shut down as written — including economizer, lead/lag and VFD behaviour where specified.
• Local DDC loops that must survive server loss are defined and tested.
• Trends and alarms are usable (no flood; meaningful delays/deadbands).
• Gateways and network points match the mapping sheet; failure behaviour is documented.
• As-builts, backups, licences and operator training are complete before handover.

Common problems and how to fix them

Modbus offline

Baud/parity/address/polarity/termination/driver. Check both ends; if online but wrong, check register map and data format.

RS-485 intermittent

Star topology, branches, termination, interference, grounding, loading. Terminate only as designed.

Wrong temperature

Sensor type, wiring, location, scaling, calibration. Software offset must not hide a wiring/sensor fault.

Pump ignores stop

HOA in Hand, local/VFD override, wrong interface, delayed status, interlock. Never bypass required protection.

BACnet visible, points missing

Unsupported objects, R/O, IDs, driver/licence. Review PICS.

Wrong Modbus values

Address, signed/unsigned, scale, 16/32-bit, word order, units.

No response to command

Permissives, interlock, manual mode, bad wiring, non-writable point, incomplete SOO. Trace BMS → controller/gateway → plant.

Alarm flood

Thresholds, missing delays/deadbands, bad sensors, unstable comms, alarms during normal transitions.

Classic commercial mistakes

Pricing before a points list; one gateway as plant SPOF; duplicate BACnet device instances; MS/TP star or wrong baud; swapped Modbus words; spare capacity only at the server; SOO “as per manufacturer”; handover without trend-based verification; BMS sold as fire-alarm control.

Frequently asked questions

BMS vs BAS?

Often interchangeable; BAS stresses automation, BMS stresses central management — follow the project wording.

BMS vs EMS?

BMS covers building services; EMS focuses on energy measure/analyse/report — separate or as a module.

How do pre-sales estimate?

From schedules, points, SOOs, network and integration — then controllers, field devices, licences, gateways, programming, install, test and handover. Points are one factor, not the only one.

Does every BMS need a server?

No — small systems may use compact supervisory devices; large ones need servers, databases, workstations or redundancy.

Does BACnet guarantee multi-brand compatibility?

No — verify objects, properties, commands, drivers and config.

Is a network point the same as physical I/O?

No — separate them for sizing and BOQ.

Can BMS control fire?

It may receive approved status/events; it does not replace the FACP or life-safety control.

What is the most important document set?

Point list + I/O schedule + SOO + network/integration pack together.

Does it work if the server fails?

Only if local DDC holds the logic and field devices stay live — define and test it.

Monitor vs control?

Reading vs commanding; many projects mix both by system.

Talk to PSS about BMS

PSS designs, installs, and maintains building management systems (BMS), from points lists and sequences through BACnet, Modbus and KNX integration. Contact the PSS team to book a first site survey.