BMS in Ecuador: how building automation really works
What a BMS is, how it differs from home automation, which systems it supervises, and how to scope a building automation project in Ecuador.
Office buildings, hotels and residential towers rarely fail outright. They degrade quietly: a chiller that starts at five in the morning although nobody arrives before eight, lighting running on empty floors, a switchboard nobody looks at until it trips. Each one is trivial on its own. Added up over a year, they are the difference between a building that is expensive to run and one that largely runs itself.
A BMS — Building Management System — is the layer that makes all of that visible and governable from one place.
BMS, building automation and home automation are not the same thing
Three terms get used interchangeably and shouldn’t be:
Home automation targets dwellings. Its measure of success is experience: scenes that work, a house that feels comfortable, a user who never has to think about the technology.
Building automation targets commercial and institutional buildings — offices, hotels, retail, healthcare, education. Its measure is operational: cost to run, availability of services, and measurable comfort for many occupants at once.
BMS is the concrete system that implements building automation: the software, controllers and network that supervise and command the building’s installations.
The difference is not scale but purpose. A large house on Control4 is still home automation. A three-storey building with a BMS is building automation. One optimises for experience, the other for operations.
What a BMS is made of
Four layers, bottom up:
1. Field — sensors and actuators. Temperature and humidity probes, CO₂ and occupancy sensors, energy and flow meters, status contacts. On the acting side: motorised valves, variable frequency drives, contactors, dampers, lighting drivers. This layer determines the quality of everything above it: a BMS cannot control what it does not measure, and it cannot measure well through badly placed sensors.
2. Control — DDC controllers. Direct digital control units that run the logic locally: start sequences, interlocks, safety lockouts, control loops. Local logic matters — if the supervisory server goes down, the building must keep operating.
3. Communication — protocols. BACnet (standardised as ISO 16484-5) is the most widespread in building automation; Modbus turns up constantly in meters, drives and power equipment. Depending on the project you may also see KNX for lighting and shading, or MQTT and OPC UA feeding analytics layers. This is where you decide whether the building stays open or becomes captive to one manufacturer.
4. Supervision — software. Graphics, historical trends, prioritised alarms, scheduling and reporting. It is the layer the operator sees, and usually the first thing that gets sold. In practice it is worth the least if the three layers below it are poorly resolved.
What a BMS supervises
In a typical building in Ecuador, a sensible scope covers:
- HVAC: chillers, air handling units, fan coils, VRF systems, ventilation and extraction. Almost always the largest consumer and the largest opportunity.
- Lighting: schedules, zoning, occupancy sensing and daylight harvesting — frequently over a DALI-2 layer.
- Electrical power: metering per switchboard, power factor, demand, generator, UPS and transfer switch status.
- Water and pumping: tank levels, pressure, pump run hours, consumption per zone.
- Access control and video: event integration, not replacement of the specialised platforms.
- Vertical transport: lift status and alarm monitoring.
One clarification worth making up front: the fire detection and alarm system is not “controlled” from the BMS. It is a certified, independent system for code reasons. What you do is interconnect it so the BMS receives its signal and executes what does fall to it — stopping ventilation, releasing access control, pressurising stairwells. Confusing supervision with control here is a serious design error.
Use cases by building type
Offices and coworking. Schedules per floor, zone control and metering per tenant. Automation pays off when occupancy varies, which is nearly always. It is the natural extension of what we covered in office automation.
Hotels. Integration between the reservation system and in-room control: an unsold room does not need conditioning. It is one of the cases where the return is most direct and easiest to defend.
Retail. Opening hours, display lighting, sales floor conditioning and refrigeration monitoring. Here service continuity weighs as heavily as consumption.
Residential towers and gated communities. Common areas, pumping, perimeter lighting, generators. The benefit is often as administrative as it is energetic: management stops depending on manual rounds.
Light industry and small data rooms. Critical environmental conditions, redundancy and event traceability.
New construction versus existing buildings
New build. The comfortable scenario: you specify from design that equipment must be native to an open protocol, define the network architecture alongside the structured cabling design, and reserve panel space and containment routes. It costs a fraction of what it will cost later.
Retrofit. The common scenario. The building already has equipment from different brands, eras and protocols, some of them proprietary. The work is to survey what exists and decide what gets integrated through a gateway, what gets replaced, and what stays out of scope for this phase. An honest retrofit runs in phases, starting where the metering and the consumption are — not where the graphics look best.
The same rule applies either way: integration goes well when the network infrastructure is resolved first. A BMS built on an improvised network inherits every one of its problems.
What to measure before automating
Automating without a baseline makes it impossible to demonstrate anything afterwards. Before specifying a single controller, you want:
- Historical electricity consumption: monthly kWh and, if available, peak demand in kW. At least twelve months.
- Actual operating hours versus the programmed schedules of the equipment. The gap between the two is usually the first finding.
- Current setpoints for HVAC, and how often they get changed by hand.
- Comfort complaint logs by zone: where it runs cold, where it runs hot, at what time.
- Maintenance work orders from the past year, corrective versus preventive.
- Occupancy: how many people, on which floors, in which time bands.
With those six inputs you can put together a defensible scope. Without them, any savings figure anyone quotes is a guess. We do not give savings percentages before there is a baseline, and it is worth being sceptical of anyone who does: savings depend on the building, its envelope, its equipment and how it is used — not on the BMS by itself.
Checklist for starting a BMS project
- Define the dominant objective: operating cost, comfort, service continuity or traceability. All four at once is not an objective, it is a wish.
- Survey the equipment inventory with make, model, year and available protocol.
- Establish the consumption and operations baseline.
- Decide the protocol architecture and put the openness commitment in writing.
- Define zoning: by floor, by use or by tenant.
- Size the network and the panel space.
- Specify the documentation deliverables: point lists, diagrams, control narratives and operating manuals.
- Include commissioning in the contracted scope, not as a closing courtesy.
- Define who operates the system afterwards, and under what maintenance plan.
Point 8 is the one most often dropped and the one that ruins most projects. A BMS handed over without commissioning is an alarm board nobody attends to.
Where DomuLab fits
Our work starts from engineering, not from a catalogue: building survey, point definition, network and protocol architecture, subsystem integration and documented handover. We coordinate HVAC, lighting, networking and perimeter security under a single operating logic, instead of leaving four systems that contradict each other.
And we say no when it applies: there are buildings where the right answer is not a full BMS but metering, lighting zoning and well-programmed schedules. That is automation too, and sometimes it is all the project needs.
Evaluating building automation in Ecuador? Let’s talk. We review what installations you have, what data exists, and what scope those data can actually support — before proposing equipment.
