A building management system should help your team find a fault and know what to do next. We start with the plant and the points it can actually expose, then plan controls, alarms and the screens operators need.
Quick answer
A building automation system reads sensors and equipment status, applies control logic, sends commands and presents alarms or trends to operators. BACnet can carry data between compatible systems, but a protocol name does not prove that a required point is exposed or writable.
Project management consultancy (PMC)
BMS project management consultancy needs a clear line between controls work and mechanical responsibility. We can help define the point list, coordinate vendors and plan witnessed tests.
A clear view of one troublesome plant area may be more useful than a building-wide dashboard full of unverified readings.
Separate commands, readings and alarms; name the contractor responsible for each connection.
Review controller schedules, gateway licences and plant access before procurement.
Test agreed operating modes against the controls description and record outstanding seasonal checks.
Mechanical safeties remain with the plant controls. A BMS review is not statutory approval or a promise of energy savings.
Discuss the scope with usUnderstand
Read the adjacent technical page before choosing equipment. It may change the wiring, network or control method that belongs in the brief.
The BMS is closer to an instrument panel than a magic brain. It shows what the connected equipment reports and can issue only the commands that designers, vendors and operators have agreed to make available.
The points list names every value, state, alarm and command exchanged with the system. It records units, read or write access, update behaviour and the responsible equipment package.
Without it, integration pricing is guesswork. A glossy dashboard cannot recover a point that the chiller or meter never exposes.
Field controllers should continue their essential sequences when the supervisory interface is unavailable, subject to the equipment design. Operator workstations, servers and gateways sit above that local layer.
Network zones, credentials, time synchronisation and backups belong in the controls documentation. Connecting everything to the office LAN without ownership is a brittle shortcut.
BACnet defines messages and objects for building controls. The project still needs a device-specific point list and conformance information because two BACnet products may expose different capabilities.
An alarm needs a condition, delay, priority, recipient, acknowledgement rule and return-to-normal state. Flooding an operator with repeated low-value alerts is a design failure, even if every alert is technically correct.
Inputs are forced or simulated, commands are observed at the equipment interface, trends are checked for units and intervals, and offline behaviour is recorded. Screenshots alone do not count as functional verification.
The major cost drivers are the number of physical and software points, plant interfaces, control panels, field devices, network segments, graphics, trends, alarms and integration licences. Reusing an existing BMS may save field work, but obsolete controllers or undocumented proprietary links can make a clean subsystem replacement easier to own. A supervisory dashboard is not an alternative to dependable equipment-level control.
A typical programme includes a controls description, point list, panel and network drawings, factory or bench checks, installation, point-to-point testing, sequence testing, trend review and operator training. Plant availability and seasonal conditions can move final tuning beyond practical completion. Local equipment safeties remain with the manufacturer controls. If the head end or wider network fails, agreed local loops should continue, while alarms, trends and remote commands may be unavailable until service is restored.
| Layer | Primary job | Failure question |
|---|---|---|
| Field device | Measure or act | Can it be read or operated locally? |
| Controller | Run local logic | Which sequences continue alone? |
| Supervisory layer | Graphics, trends and coordination | How is it restored from backup? |
Evaluate
Bring the floor plan, reflected ceiling plan or equipment schedule. We can mark assumptions, interfaces and unresolved choices before procurement.
Independent learning
These optional references are published by the organisation named below. They are linked rather than embedded, so the page does not load a video player or start playback.
A standards-body webinar comparing conventional wiring with a KNX bus and explaining sensors, actuators and reprogrammable links. Opens on YouTube in a new tab.
Written by: SmartR Spaces
Technical review: M&M Smarter Automation LLP
Content updated:
Next step
A useful proposal starts with the property, expected behaviour and handover standard. Product names come after those decisions.