Building Automation

What is a BMS points list?

Requirements come first. 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. The points list must confirm each exposed command, status and alarm before graphics or integration work receives a dependable price on site.

How are controllers and networks separated?

Failure needs a tested path. 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.

The network is part of it. Network zones, credentials, time synchronisation and backups belong in the controls documentation; connecting everything to the office LAN without ownership is a brittle shortcut.

What can BACnet integration prove?

Requirements come first. 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.

How are alarms made useful?

Requirements come first. 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.

What is tested at handover?

Interfaces need proof. 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.

What determines BMS scope, delivery time and resilience?

Scope sets the budget. 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.

Failure needs a tested path. 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.