Before any quote,
the questions get asked first.

The label is awarded to a building by assessors; no system can substitute for that process. What the system can do is twofold: actually implement the items the manual examines — open protocols, interlock control, sub-metering, equipment history and maintenance scheduling, and a standard data interchange interface — and produce an acceptance report that lists the real figures for protocols, points, alarms, history and audit records on one printable page. That report deliberately shows only what is genuinely configured: unset items read “not configured”, and it never declares itself compliant, because that judgement belongs to the assessor.

No. The server sits inside the building on the same network as the controllers; losing the internet only means losing remote access. The server writes a periodic heartbeat into the PLC — if the server crashes or loses power, the PLC detects the silence and reverts to local control. The direction is deliberate: a system that has crashed cannot send an “I am down” message.

It depends on the interface. We support Modbus TCP (including RS485 converters), Siemens S7, BACnet/IP, MQTT and SOAP / Web Service, which covers most controllers, meters and existing system interfaces on the market. BACnet devices can have their object list read and points created in bulk. If none of these fit, adding a protocol means implementing five driver methods — nothing above the driver layer changes.

Not by default. One server per site runs the polling, the database and the screens locally. Remote viewing is an option we can enable, not a prerequisite.

Three roles — admin, operator, viewer — enforced on every backend API; hiding buttons in the UI is only a convenience. Every write and every alarm acknowledgement is recorded in the audit log, including rejected attempts.

No. A site package carries devices, points, alarms, schedules and every screen including background images; you preview it on the new site, apply it, then adjust for the differences. Built-in screen templates are also available.

Priced by the size of the site: how many controllers connect, how many points in total, and how many monitoring screens need building. Mixing the five protocols carries no surcharge. From the second building onward the configuration and screens clone across, so the cost drops noticeably. A quote always comes after the site survey and a confirmed point list — a price given before the points are counted always changes later.