A Building Management System (BMS) is the controls layer that decides when chillers run, how dampers modulate, whether lighting circuits energise, and when an access door releases. On a well-designed site it disappears into the background. On a poorly designed site it is the reason the air handlers fight each other and the chilled water plant runs to maintain a set-point no occupant cares about.

This page covers what a BMS controls and what it deliberately does not, the protocols and head-end architectures EcoXplore deploys, the retrofit pattern for overlaying a BMS on a legacy installation, and how a BMS integrates with EMS and PQMS data.

What a BMS controls

A typical BMS scope:

• HVAC. Chilled-water plants (chillers, pumps, cooling towers), air-handling units, variable air volume terminals, exhaust systems, dehumidification.
• Lighting. Daylight harvesting, occupancy-driven dimming, scheduled circuits. Increasingly the lighting scope is split into a dedicated controls system that talks to the BMS via BACnet/IP rather than living inside it.
• Access and life safety integration. Door status, lift status, generator status, smoke control. The BMS reads these; it does not own them. Fire alarm control panels (FACPs) remain governed by SS 575, NFPA 72, or the local equivalent and must not be replaced by a BMS function.
• Plumbing systems. Booster pump status, water tank levels, leak alarms.
• Submeter polling. Where an integrated EMS is not deployed, the BMS often acts as a meter aggregator for utility submeters.

A BMS does not run a Fire Alarm Control Panel. The boundary matters in Singapore where SCDF requires the FACP to be a listed, certified, standalone system. A BMS that supervises FACP status via a relay contact is fine. A BMS that issues fire alarm commands is non-compliant.

Open vs proprietary head-ends

A BMS head-end is the supervisory software layer where points are visualised, schedules are set, and trends are stored. The head-end choice drives every later decision about expansion, integration, and contractor lock-in.

Open head-ends speak BACnet/IP, BACnet MS/TP, Modbus TCP, and OPC UA natively. A new contractor can connect new equipment without paying a license fee for each integration. Niagara Framework, Tridium-based head-ends, and several Schneider EcoStruxure variants fall in this category.

Proprietary head-ends speak the vendor's protocol natively (e.g. Johnson Metasys N2, Siemens APOGEE FLN, Honeywell C-Bus). Integrating a foreign device requires a translator gateway, which raises maintenance cost and creates a single point of failure.

For new builds, EcoXplore recommends open head-ends in nearly all cases. The vendor will recover their margin on hardware, commissioning, and service. The customer keeps the right to pick a different integrator on the next refresh.

Why BACnet matters

BACnet (ASHRAE 135) is the dominant open protocol for building controls in Southeast Asia, North America, and Europe. The protocol defines:

• Standard object types (analogue input, binary output, schedule, trend log, etc.) so a controller from Vendor A can be read by a head-end from Vendor B without custom drivers.
• BIBBs (BACnet Interoperability Building Blocks) that specify exactly which services a device must support to claim conformance at a given level.
• A test framework through BACnet International so conformance claims are verifiable.

Modbus is older, simpler, and very common at the meter and VFD level, but Modbus has no built-in object model. Every Modbus integration is a custom register-map exercise. BACnet integrations are repeatable.

For specifying BMS work in Singapore, the standard reference is ASHRAE Guideline 13 (specifying DDC controls) and BCA's Green Mark mechanical and electrical handbooks.

Retrofit pattern — overlaying on legacy installations

Most BMS work in mature buildings is retrofit. The pattern that succeeds:

1. Survey what exists. Walk the panels with the existing maintenance team. Map every controller, gateway, and protocol. Photograph the wiring at each cabinet. Older Honeywell or Siemens installations often have undocumented field wiring that nobody alive remembers.
2. Decide what to keep. A working AHU controller with three years of life is not a candidate for replacement. A failing fan-coil controller with no spares might be. Keep what works.
3. Pick an integration boundary. Usually at the floor or zone controller layer, leaving terminal-unit controllers intact and overlaying a new supervisory head-end. BACnet/IP at the boundary; whatever the existing field protocol is below it.
4. Run parallel. Bring the new head-end up in monitor-only mode for two to four weeks. Compare its commands against the existing system before transferring control.
5. Cut over and decommission. Move each system zone-by-zone. Keep the old head-end running in read-only for another two weeks as a safety net.

Skipping step 4 is how cutover days become CNN moments.

Integration with EMS and PQMS

A BMS is the operations system. An EMS is the energy reporting system. A PQMS is the supply-quality monitoring system. The three integrate at well-defined seams:

• BMS ↔ EMS. BACnet/IP for live point sharing (kW, kWh, status). The EMS may also pull historian data directly from the BMS where the BMS head-end exposes its trend logs over a SQL or REST interface.
• BMS ↔ PQMS. Less common at the live-control layer because PQ events are sub-cycle and the BMS scan rate is in seconds. Where it matters (e.g. a generator transfer scheme), PQ events trigger a discrete alarm output to the BMS rather than streaming PQ data.
• EMS ↔ PQMS. Shared revenue meters where the hardware supports both. See the EMS vs PQMS comparison.

Specifying the integration in the project requirements, not as a change order during commissioning, is the difference between a working system and a series of relays patched together at handover.

EcoXplore's approach

EcoXplore's BMS practice runs on a small set of opinions:

1. Open head-ends as default. Closed systems only where a specific tenant requirement or existing-vendor contract makes them mandatory.
2. BACnet-first specifications. Modbus where it makes sense (meters, VFDs), BACnet/IP everywhere else.
3. Documented commissioning. Point-by-point tests with signed records, sequence-of-operation tests against the design intent document, training delivered to the on-site maintenance team.
4. Local capability. BCA ME02 L4 means the team is qualified to lead M&E work in Singapore. ISO 9001 quality controls extend to commissioning records, not just office processes.

Frequently asked questions

Can I use the BMS as an Energy Management System? Partially. A BMS captures live meter data and can produce dashboards. It does not usually produce ISO 50001-shaped reports or normalise consumption against driver variables. For compliance use, layer a dedicated EMS on top.

What is the difference between a BMS and an EMS? A BMS controls equipment. An EMS measures and reports. They are usually distinct systems that share data over BACnet/IP.

Do I need a head-end replacement, or can the existing system be extended? Often the existing system can be extended via a gateway. Replacement is justified when the existing head-end is end-of-life (no spares, no firmware support) or when proprietary lock-in is blocking required integrations.

How long does a retrofit take? A floor-by-floor retrofit on a mid-size commercial building runs four to nine months from kick-off to full cutover, depending on tenant cooperation and after-hours work windows.

Is BACnet secure? BACnet/IP runs over standard IP networks and inherits standard network security practices. Segmentation onto a dedicated controls VLAN with firewall rules is the baseline. BACnet/SC (BACnet Secure Connect) adds TLS at the protocol layer for new installations.

Talk to EcoXplore's controls team

For BMS retrofit assessments, new-build specifications, or open-head-end migrations, contact the EcoXplore team.