Secure connection
Agree the approved remote-access method: Niagara access, VPN, secure gateway, remote desktop by approval, alarm email routing or cloud dashboard access.
Remote Building Intelligence
How Remote Building Intelligence Works
A clear process for connecting to a site securely, reviewing the system, configuring alarms, responding to issues and producing monthly engineer-led reports.
Initial site review
Check controllers, sensors, schedules, alarms, trend logs, graphics, meters, backups, critical areas and existing site documentation.
Monitoring setup
Configure alarms and review rules for temperatures, humidity, CO₂, pressure, energy, plant faults, offline controllers, sensor faults and out-of-hours runtime.
Optional LoRaWAN sensors
Where the BMS does not have enough data, wireless sensors can be added for health, comfort, occupancy, air quality, status or energy evidence without major wiring works.
Response process
When an alarm or abnormal trend is found, investigate remotely, advise the site team, adjust approved settings or escalate to the nominated contact or contractor.
Monthly engineer report
A person reviews the full month of history and trend data, then writes a risk-based report with findings and suggested improvements.
Continuous improvement
The service improves as better alarms, trends and site standards are added, giving the customer clearer visibility and better long-term value.
Year-end report
After 12 months, the monthly findings are combined into a yearly improvement report showing which areas should be improved first.
Typical inputs needed
- Site platform details, such as Niagara, Trend, Siemens, Schneider, Distech or Priva.
- Approved remote-access method and site authorisation.
- Known critical areas and agreed condition limits.
- Site contact list and escalation process.
- Current alarm routing, trend logs and meter availability.
- Any areas where extra LoRaWAN sensors may be needed to close data gaps.