01 / 03
Case file
Open-protocol BMS frameworks — HVAC, lighting, fire and access integrated to a single graphical front-end with operator analytics and alarm escalation.
— 24 hours, on the dashboard
The building, in numbers.
Drag the timeline. Watch HVAC, lighting, IT and other loads stack — plus BESS discharge for peak-shave and the chiller-2 anomaly the BMS catches at 14:00.
Time
13:00
Live at 13:00
566kW
- HVAC308
- Lighting80
- IT130
- Other48
BESS
0 kW
Hot-standby
Day total8,587 kWh
Peak demand592 kW @ 14:00
Anomalies caught1
/ The discipline, in detail
How we approach building management system (bms).
A BMS is justified the day it spots a chiller drawing 12% more current than the same chiller drew last month. We design BMS deployments to the building's actual operating priorities — comfort, plant health and compliance — and we specify an analytics layer that turns logs into decisions. Trend graphs, alarm escalation, mobile dashboards and a documented operations runbook are built into the commissioning, not added later.
On record
Every building management system (bms) engagement is documented end-to-end — design, programming, commissioning, calibration — and handed over with the files our successors would need if we were never to return.
/ Three lenses on the same system
Read it the way you actually need it.
Three short readings of building management system (bms) — for a non-engineer who needs the picture, an engineer who needs the spec, and a buyer who needs to see the system in operation.
/ In simple terms
A Building Management System (BMS) is the supervisory dashboard that runs a building's mechanical and electrical plant — chillers, air-handling units, lighting, sub-metering — from a single screen. It tells the facilities team what is running, what is alarming, and what is using how much energy. The good systems pay for themselves in 18–36 months on energy savings alone.
/ Technical explanation
A BMS runs on a supervisory cluster (Honeywell EBI, Siemens Desigo, Johnson Controls Metasys), with DDC controllers distributed across the building handling AHU, chiller, lighting and sub-meter logic on BACnet/IP and BACnet/MS-TP. Sequence-of-operations programming, sub-metering granularity and cause-and-effect interlocks (fire-to-AHU, BMS-to-UPS) are the engineering decisions; alarm-management and offline configuration baselines are the operational discipline.
/ Real project usage
On the Unity Mall Guwahati deployment we are programming the chiller sequence against the mall's actual occupancy curve (F&B opens earlier, retail trades a longer envelope, weekend differs from weekday), with sub-metering granular at the lease-clause level for tenant-billing, and an integration pathway already engineered for phase-two fire-alarm and access-control integration. The mall opens with a working dashboard, named alarms in plain English and escalation routing — not a vendor handover that needs three months of stabilisation.
/ System architecture
The layers, named.
Every layer below is engineered as one piece of the integrated stack. Each carries its own commissioning artefact and its own AMC inclusion.
- 01
Supervisory layer — the BMS server cluster running the brand's supervisory software (Honeywell EBI, Siemens Desigo CC, Johnson Controls Metasys). The supervisory layer hosts the dashboard, the alarm-management engine, the trend-data archive, the schedule engine and the reporting engine.
- 02
Field controllers — DDC controllers distributed through the building, one per AHU, chiller, lighting circuit, sub-meter group. Each controller carries its own logic and continues to operate even if the supervisory layer is unavailable.
- 03
Field devices — sensors (temperature, humidity, CO₂, occupancy, lux, pressure), actuators (damper, valve, relay), sub-meters (electrical, water, BTU). Cabling is typically 18 AWG twisted-pair on a Modbus or BACnet bus, with the field device addresses mapped to the controller's I/O.
- 04
Network — BACnet/IP over the building's structured cabling backbone (segregated VLAN), with BACnet/MS-TP or Modbus RTU on field-bus segments where required. Gateways translate between protocols where the field devices are not native BACnet.
- 05
Mobile and remote access — dashboard exposed via secure VPN or HTTPS to authorised mobile clients; alarm escalation routed to nominated facilities-team mobiles via SMS/push.
/ Design considerations
The decisions we take early.
- Sub-metering granularity — the data layer drives demand-charge analysis, tenant cross-charging and fault detection. We typically meter at chiller plant, AHU, lift bank, lighting circuit, tenant-zone level plus any load above 25 kW.
- Sequence-of-operations programming — the chiller and AHU sequences are programmed against the building's actual occupancy curve (mall hours differ weekday from weekend; hospital ICU runs 24/7; office tower has morning ramp-up). The sequence is documented in the as-built and reviewable by the facilities team.
- Alarm management — every alarm has a name in plain English, a priority level (critical / urgent / informational), an escalation path (which mobile, after how long), and an acknowledgement workflow. Alarms without these are noise.
- Cause-and-effect interlocks — fire-alarm to AHU damper, BMS to UPS, BMS to access-control evacuation mode. Each interlock is documented in the matrix and tested on commissioning.
- Future-readiness — the controller capacity, the dashboard real-estate and the network design must accommodate phase-two systems (additional AHUs, sub-meters, fire-alarm integration, access-control integration) without re-cabling.
/ Integration logic
How it talks to the rest.
- Fire-alarm to BMS — on a fire-alarm trigger, the BMS closes AHU dampers per the matrix, with hospital-OT acknowledgement window where applicable. The BMS dashboard surfaces the fire event with the affected zone highlighted.
- BMS to UPS/BESS — the UPS reports its state (online / on-battery / fault) to the BMS via SNMP or Modbus. The BMS dashboard surfaces UPS state and triggers escalation on prolonged on-battery operation.
- BMS to access-control — on access-control evacuation mode, the BMS dashboard surfaces the evacuation event and the BMS may interlock dependent plant (e.g. lift homing).
- BMS to lighting — daylight-harvesting and occupancy-driven dimming through DALI gateways, programmed against the building's actual usage pattern.
- BMS to sub-metering — the BMS aggregates sub-metering data into demand-charge analysis and tenant cross-charging feeds.
/ Failure scenarios
What goes wrong, in practice.
- Controller battery failure — DDC controllers carry a battery to retain configuration on power loss. Battery degradation causes configuration loss on the next power event. Mitigated by quarterly battery-state monitoring and 3-year proactive replacement.
- Schedule drift — the chiller and AHU schedules drift from the building's actual occupancy curve over months and years (occupancy patterns change, the schedule does not). Mitigated by quarterly schedule review against actual occupancy data.
- Sub-meter calibration drift — electrical sub-meters drift in calibration over 3–5 years, producing tenant-billing disputes. Mitigated by annual sub-meter calibration against a reference standard.
- Alarm flood — a single fault produces hundreds of cascading alarms, masking the root cause. Mitigated by alarm-management with priority levels and root-cause grouping.
- Network segmentation breach — the BMS VLAN is bridged to the general office network during a network change, exposing the BMS to lateral attack. Mitigated by network-security audit on every BMS network change.
/ Maintenance expectations
What the AMC actually delivers.
- Monthly chiller-sequence verification, quarterly damper-actuator function test, quarterly alarm-management review, annual sub-metering calibration.
- Annual full sequence-of-operations review with the facilities team, with sequence updates pushed to controllers per the review.
- Configuration baselines stored offline — every controller's configuration captured to versioned storage, recoverable in hours.
- Spares-on-hand — DDC controllers, common sensor types, common actuator types, sub-meters, sized against the manufacturer's MTBF data.
- Quarterly review of alarm patterns and escalation effectiveness; alarms that fire without operations-team action are re-tuned or retired.
/ Where we deploy this
Active across 6 sectors.
Building Management System (BMS) is rarely a standalone brief — it sits inside a wider sector practice with its own codes, expectations and operating rhythm.
Hospitality
Guest experience, engineered.
Commercial & Corporate
Workplaces that begin meetings on time.
Education & Institutions
Schools, colleges and universities.
Healthcare
Hospitals where systems serve the patient.
Retail & Malls
Footfall, loyalty, footprint.
Industrial & Warehousing
Operations that don't take a day off.
/ Sister services
The rest of bms.
A serious brief usually crosses two or three of these. Read across the discipline — we deliver them as one contract.
- 02
Online UPS
Clean power, isolated from grid reality.
Double-conversion online UPS — continuous AC-to-DC-to-AC rectification that delivers regulated sine to your load with zero transfer time and complete isolation from grid sag, surge, harmonics and frequency drift.0 - 03
Battery Energy Storage (BESS)
Power as an asset, not a cost.
Lithium-ion Battery Energy Storage Systems — installed alongside online UPS, paired with rooftop solar, or stand-alone — for peak-shave, demand-response, off-peak tariff arbitrage and ride-through.1
/ Where this system has been deployed
Building Management System (BMS) on the ground.
The reference projects below carry a building management system (bms) layer engineered as part of an integrated stack. Each case study walks through the engineering challenges that were solved, the standards the work was held to, and the operational outcome on the day-two team.
/ Integration with
How building management system (bms) talks to the rest.
A serious deployment of this system rarely operates in isolation. The disciplines below most commonly share its cabling pathways, its controller logic, and its cause-and-effect matrix.
Fire Alarm System
Detection that pinpoints. Response that is coordinated.
Addressable fire detection and alarm — Honeywell, Bosch, Notifier and Siemens panels — integrated with PA, BMS, access control and emergency lighting per NBC, IS 2189 and NFPA 72.Online UPS
Clean power, isolated from grid reality.
Double-conversion online UPS — continuous AC-to-DC-to-AC rectification that delivers regulated sine to your load with zero transfer time and complete isolation from grid sag, surge, harmonics and frequency drift.
/ Read deeper
The engineering, in long form.
Each article below goes deeper than this service page can — a full walk-through of the engineering decisions, written by the team that delivers this work.
- BMS · 13 min
BMS retrofit playbook for occupied hospitals
A BMS retrofit in an occupied hospital is unlike any other commercial BMS retrofit. Patient-care continuity, NABH compliance, infection-control zoning and theatre uptime turn what would be a 12-week commercial project into a 28-week clinical exercise. The playbook we have learned across multiple projects, including the Tinsukia Medical College & Hospital delivery for NCC Limited.
Read article - BMS · 10 min
BMS vs smart automation: the bright line nobody draws — and why it matters at year three
Smart automation runs comfort layers on a homeowner's terms; a BMS runs operational and energy layers on a facilities team's terms. The line between them is a discipline boundary, not a marketing one — and crossing it is what produces the residential buildings whose 'BMS' fails on the third year and the commercial buildings whose 'automation' is unmanageable on the first.
Read article - BMS · 9 min
Lithium-ion BESS vs VRLA: the eight-year economics for mission-critical UPS
Cycle life, footprint, depth of discharge, payback windows — why we now specify lithium for almost every new mission-critical install above 20 kVA, and what the migration audit looks like for an existing VRLA bank.
Read article
/ Frequently asked
Building Management System (BMS) — what buyers ask first.
What energy savings does a BMS deliver?
A well-designed BMS typically delivers 10–22% energy savings on HVAC and lighting in year one, with payback in 18–36 months. Typically delivers 10–22% reduction in HVAC and lighting energy in the first year, depending on the building's existing control maturity. Payback is usually 18–36 months.
What does a good BMS actually do for the building?
It optimises the things that drive the operational bill — chiller schedules against occupancy, AHU dampers against CO₂, lighting against daylight, hot-water against demand, energy against tariff. The right BMS pays back in 18–36 months on energy savings alone, then continues to pay back annually.
Which BMS framework is right for a building?
The right BMS framework follows the building's HVAC vendor, protocol requirements, operating team and reporting goals. For multi-vendor environments we favour open-protocol, agnostic architectures; for campuses with deep HVAC integration, the controls stack must be matched to the equipment and long-term support model.
Can a BMS be retrofitted to an existing building?
Yes — almost always. We stage retrofits in zones, run new and legacy controls in parallel during cutover windows, schedule controller swaps for off-hours, and verify against historical operational data. A typical commercial-tower retrofit takes 8–14 weeks with no operational shutdown.
How does the BMS report to the facilities team?
Through a customised dashboard that surfaces only the alarms and KPIs that need action — not the noise from every minor event. Facilities receive weekly summaries, daily exception reports, and real-time critical alerts to mobile. We design the dashboard with the operations lead during commissioning so it reflects how they actually work.
What's the AMC for a BMS?
Quarterly health-check (controller temperature, network latency, alarm-log review, software-licence renewal), annual full re-tune (PID loops, schedules, sensor calibration), firmware patching on schedule, and analytics-driven optimisation reports. AMC runs 8–12% of installed value annually.
· Begin
Begin a
building management system (bms)
brief.
Tell us about the building, the timeline, and what success looks like a year after handover. We will reply within two working days with a written response, not a sales pitch.