Multi-Utility Metering

The problem

Water, electricity, gas and heating/cooling meters use different protocols and are managed by different teams, so there is no single consumption record per building or tenant.

Solution overview

MILESGO gateways collect data from electricity meters, water meters, gas meters, BTU / heat meters, M-Bus meters over M-Bus / Modbus RTU / DL/T 645, and deliver it to the energy management system, the billing system, the BMS as Modbus TCP / BACnet/IP / MQTT. Field equipment keeps its own protocol and control logic; integration is done by configuration and point mapping, not custom code.

Typical scope

electricity meters
water meters
gas meters
BTU / heat meters
M-Bus meters

Protocol path

M-Bus / Modbus RTU / DL/T 645 → Modbus TCP / BACnet/IP / MQTT

Implementation checklist for the project manager

M-Bus: check unit loads and cable length per segment; 2-wire M-Bus gateways need a 24 V DC supply.
Record CT ratios, meter IDs and multipliers in the point table; wrong multipliers are the usual cause of billing errors.
Fix a site / asset naming convention before the first site so data from all sites can be compared.
Configure NTP so trends, alarms and meter readings carry consistent timestamps.
Agree data retention and the report format needed for audits with the quality team at the start.
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: electricity meters, water meters, gas meters, BTU / heat meters, M-Bus meters, connected over M-Bus / Modbus RTU / DL/T 645. 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 energy management system, the billing system, the BMS, which receives the data as Modbus TCP / BACnet/IP / MQTT. Remote access for maintenance runs over VPN rather than open internet ports.

System composition

Field devices: electricity meters, water meters, gas meters, BTU / heat meters, M-Bus meters
Edge / integration: MILESGO protocol gateways and edge controllers
Upper systems: the energy management system, the billing system, the BMS (Modbus TCP / BACnet/IP / MQTT)
Tools and commissioning: Web-based configuration, point table import/export (Excel), off-site simulation and on-site diagnostic tools

Software and AI capabilities

Consumption baseline and deviation alertsPilot
Automatic report drafting from collected 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

Manual readings replaced by scheduled automatic collection
Consumption attributable by tenant, department or cost centre
Timestamped records for compliance and reporting
Consumption visible by area, system and time period

Tell us about your project

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

Discuss Your Project