Building Command Center

The problem

Facility teams run several buildings from spreadsheets and vendor portals, with no common dashboard, alarm list or API for the tenant and management systems.

Solution overview

MILESGO gateways collect data from air handling units (AHU), chillers, electricity meters, indoor air quality sensors (CO2, PM2.5, TVOC, T/RH), lift controllers, fire alarm panels (read-only) over OPC UA / BACnet/IP / Modbus TCP / MQTT, and deliver it to the operations / command centre, large-screen dashboards (HDMI), a cloud platform (MQTT), third-party platforms (HTTP API), SMS, email and messaging alarms as OPC UA / MQTT. Field equipment keeps its own protocol and control logic; integration is done by configuration and point mapping, not custom code.

Typical scope

air handling units (AHU)
chillers
electricity meters
indoor air quality sensors (CO2, PM2.5, TVOC, T/RH)
lift controllers
fire alarm panels (read-only)

Protocol path

OPC UA / BACnet/IP / Modbus TCP / MQTT → OPC UA / MQTT

Implementation checklist for the project manager

List dashboard users and roles, and configure user permissions accordingly.
Fix a site / asset naming convention before the first site so data from all sites can be compared.
Define an alarm matrix (priority, recipient, escalation) and test every alarm end to end at SAT.
Keep OT networks segregated and use VPN for remote access instead of opening ports to the internet.
Agree KPI definitions (for example OEE components or kWh per unit) with operations before building dashboards.
Roll out in phases: pilot one site or area, confirm data quality, then replicate.
Hand over configuration backups, point table, IP plan and as-built drawings, with a short operator training.

Project deliverables

Signed point table and protocol mapping
Gateway configuration files and backups
IP address plan and network drawing
FAT and SAT test records
As-built documentation and operator training

System architecture

Field layer: air handling units (AHU), chillers, electricity meters, indoor air quality sensors (CO2, PM2.5, TVOC, T/RH), lift controllers, fire alarm panels (read-only), connected over OPC UA / BACnet/IP / Modbus TCP / MQTT. Edge and integration layer: MILESGO protocol gateways and edge controllers, mounted on DIN rail in existing panels, polling each device, time-stamping values and buffering them locally. Upper layer: the operations / command centre, large-screen dashboards (HDMI), a cloud platform (MQTT), third-party platforms (HTTP API), SMS, email and messaging alarms, which receives the data as OPC UA / MQTT. Remote access for maintenance runs over VPN rather than open internet ports.

System composition

Field devices: air handling units (AHU), chillers, electricity meters, indoor air quality sensors (CO2, PM2.5, TVOC, T/RH), lift controllers, fire alarm panels (read-only)
Edge / integration: MILESGO protocol gateways and edge controllers
Upper systems: the operations / command centre, large-screen dashboards (HDMI), a cloud platform (MQTT), third-party platforms (HTTP API), SMS, email and messaging alarms (OPC UA / MQTT)
Tools and commissioning: Web-based configuration, point table import/export (Excel), off-site simulation and on-site diagnostic tools

Software and AI capabilities

Configuration screens generated from a natural-language description (SCADA gateway AI assistant)Pilot
Alarm noise reduction and root-cause groupingRoadmap
Natural language questions over site dataRoadmap

Delivery steps

1
Site survey and point list
Inventory devices, protocols, register maps, panel space, power and network paths.
2
Design and point table sign-off
Map every point to the target protocol and system; agree it with the client and the upper-system contractor.
3
Configuration and FAT
Build the gateway configuration off site, simulate it and test against the signed point table.
4
Installation and wiring
Mount gateways on DIN rail, wire RS-485 / I/O / Ethernet, apply the IP plan.
5
SAT and alarm tests
Verify values against local readings, test every alarm and command end to end.
6
Handover and support
Hand over configuration backups, point table and as-built documents; train operators.

Customer value

One view of all subsystems instead of separate vendor consoles
Alarms reach the right person by SMS, email or messaging apps
Data ready for cloud platforms and analytics
Remote diagnosis and fewer site visits

Tell us about your project

Send the protocols, point count and target system. A sales and engineering pair reviews every submission.

Discuss Your Project