Insight / Metering
Technik Intelligent Systems
Technik Intelligent Systems
Commercial & Industrial Metering · Data & Systems
Installing the meters is only half the job. The readings still have to be collected, time-stamped, stored and made usable, reliably, and to a standard that holds up for billing, ESG reporting and audits. The right solution is an independent AMR (Automatic Meter Reading) system that reads every meter on a fixed schedule and owns the record, with the BMS reading from that data layer, not the other way round. This piece explains why, the on-premises versus cloud trade-off, and why wiring meters straight into the BMS is a non-desirable method.
01 · The AMR
An Automatic Meter Reading system sits independently of every other building system and does one job well: it polls each meter on a fixed schedule, time-stamps the reading and logs it to the required standard, typically at 30-minute (half-hourly) intervals.[4]
Why independent, and why half-hourly? Independence means your metering record is not hostage to another system's uptime, upgrades or quirks: the data keeps flowing even when the BMS is down for maintenance. Half-hourly granularity is the de-facto standard for energy settlement and reporting in the UK, and it is fine-grained enough to expose load profiles, out-of-hours consumption and demand peaks rather than just a monthly total. Complete, consistent, time-stamped half-hourly data is exactly what fair tenant billing, NABERS UK, SECR and ESG reporting and ISO 50002 audits depend on.[2]
02 · Delivery model
AMR software comes in two broad shapes: on-premises software you run yourself, or a hosted and cloud service you subscribe to. Both work. They fail in different ways.
On-premises means specific hardware on site, plus a software stack with licence and maintenance fees, costs that usually add up to more than a modern subscription once you total them. Access is often tied to a single terminal in a plant room, and that is the root of the real problem: on-site systems tend to get neglected, used infrequently and quietly degrade, with missed readings, unpatched software and gaps in the record, until no one fully trusts the data.
Hosted and cloud is a subscription, but it avoids most of those failure modes. The software is delivered as a service with SLAs and uptime guarantees, automatic updates, error-checking and configurable data-retention options, and it is reachable securely from anywhere rather than from one PC. Retention varies by provider, but three months to one year is typical, with multi-year retention on some contracts.
On a good platform, every reading is yours: exportable in full, any time, at no extra cost, and a reputable provider will often send you all of your data on request, even if the platform is no longer available or you are out of contract. On some others, the moment your data lands on the provider's servers it can quietly become theirs, to lock behind a paywall, or sell back to you. Read the contract before the meters go in.
03 · Outputs
Whichever model you choose, the platform should turn raw readings into something usable. Grouping by area, circuit or tenancy is what makes fair recharging and per-occupier reporting possible; export and analytics are what turn the data into decisions. Look for:
04 · Integration
So where does the BMS fit? It reads the metering data as a consumer, never as the record. The gateways present the readings over Modbus or BACnet; the AMR polls and logs them independently as the system of record; and the BMS takes a live copy of the same data for control, dashboards and alarms. The AMR, not the BMS, stays the authoritative, validated source.
This is the separation CIBSE TM39 points to: a dedicated metering and monitoring layer that owns the record, with the BMS integrated alongside it rather than underneath the meters.[1]
05 · What to avoid
It is common to see the opposite: meters cabled directly into the BMS, with custom logic used to present, and sometimes bill from, the raw values. It usually works at first, which is why it persists. It is also strongly discouraged, and TM39's separation of metering from control is exactly the reason.
The problems are structural, not cosmetic:
Exposing the data to third parties (auditors, billing bureaus, tenants) is awkward, because it lives inside a control system that was never designed to share it.
Controller maintenance, firmware upgrades and reboots stop collection. Half-hourly data with holes in it fails for billing and reporting.
The metering database often sits on the same machine as live control, tangling backups and capacity. When readings are missed, backfilling them is usually difficult or impossible.
BMS platforms are rarely security-hardened and are often reached over remote-desktop tools, lacking the controls expected of anything internet-facing that handles commercial data.[5]
An attacker or rogue insider can inject falsified or fixed additive values straight into the metering database, producing incorrect tenant bills or fraudulent environmental reporting.[6]
Flatliners (stale, unchanging values) and API timeouts corrupt the dataset quietly, and one central server or network outage halts all collection at once.
In governance terms, the two big exposures are data manipulation (falsified consumption) and a single point of failure (one outage halting collection). Either undermines billing, ESG reporting and energy-efficiency compliance.
06 · The rule
Anywhere billing, compliance or ESG reporting is in play, use a dedicated AMR with billing-suitable, approved meters, and integrate the BMS with the metering layer rather than wiring the meters into the BMS.[3] It is also the path CIBSE TM39 sets out. Keep metering as an independent data system, and let every other system read from it.[1]
In short
Meters produce readings; an AMR turns them into a reliable, owned, half-hourly record; the BMS and everything else reads a clean feed from that layer. That separation is what keeps billing defensible, reporting auditable and the data yours.
Planning a metering and AMR strategy, or untangling meters from a BMS? Talk to us about getting the topology right.
info@technik-ims.net www.technik-ims.netReferences
Best practice for the design, specification, installation, commissioning, data export and use of metering and sub-metering data, including the integration of metering systems with the BMS. cibse.org
Statutory guidance under Part L. Supports sub-metering and automatic meter reading so that energy consumption can be assigned to end-use and effectively managed in non-domestic buildings. gov.uk
Explains that the Measuring Instruments Regulations 2016 apply to meters used for trade, the basis for using approved, billing-suitable meters wherever a reading drives a charge. gov.uk
The industry programme moving electricity settlement to half-hourly data, context for why 30-minute interval data is the working standard for metering and reporting. mhhsprogramme.co.uk
UK National Cyber Security Centre guidance on securing connected building and place infrastructure, relevant to the security of metering, BMS and the systems that handle their data. ncsc.gov.uk
UK guidance on Streamlined Energy and Carbon Reporting and greenhouse-gas reporting, where accurate, tamper-evident energy data underpins the figures companies must disclose. gov.uk