Advanced Metering Infrastructure: A Property Owner's Guide
Canada's smart-meter market is already mature. Natural Resources Canada estimated that 82% of Canadian electricity meters were smart meters by the end of 2018, while industry reporting placed the installed base at 15.5 million meters in 2024, with penetration still about 82% (Canadian smart-meter adoption data). For a multi-family or commercial property owner, that changes the question. You're not deciding whether networked metering is a futuristic utility concept. You're deciding what the infrastructure behind your building's meters can do.
Vendors may use terms such as advanced metering infrastructure, smart metering, automated billing, or submetering interchangeably. They don't always mean the same thing. A meter that stores consumption is different from a meter that communicates hourly, and both are different from a complete system that validates data, detects events, supports billing, and keeps a portfolio visible.
This guide translates AMI into property-owner language. It explains the equipment, compares AMI with AMR and manual reads, shows where the system affects tenant billing and net operating income, and addresses the less comfortable questions around phased installation, legacy-meter compliance, cybersecurity, and data control. If you're reviewing a residential and commercial submetering overview, start by understanding the infrastructure rather than focusing only on the meter mounted in a suite.
Table of Contents
- Why Advanced Metering Infrastructure Matters to Your Building
- How Advanced Metering Infrastructure Actually Works
- AMI Versus AMR and Legacy Meters
- AMI Use Cases for Multi-Family and Commercial Properties
- The Data and Analytics Layer Behind the Meters
- Phased Rollouts, Compliance, and Common AMI Misconceptions
- What AMI Means for Your Submetering Program
Why Advanced Metering Infrastructure Matters to Your Building
Suppose a condominium corporation receives one bulk electricity bill. The property manager allocates the cost across units, residents question the calculations, and the corporation absorbs common-area consumption without a clear view of which loads are driving it. A commercial landlord faces a similar problem when tenant spaces, elevators, parking equipment, HVAC systems, and lobbies share a billing structure that wasn't designed for detailed cost recovery.
The owner's problem isn't just that someone has to read a meter. The problem is that decisions are being made with incomplete information.
Advanced metering infrastructure, or AMI, is the connected system that turns meter readings into usable operational data. It can support automated collection, interval-level consumption records, billing workflows, exception handling, and visibility into unusual usage. For a building, that can mean fewer manual processes and a clearer relationship between consumption and charges. It can also create new responsibilities, especially when tenant-level data moves through several systems.
The five questions owners should ask
A practical AMI review should answer five questions:
- What is installed? Is the proposal for individual electricity, water, gas, thermal energy, common-area meters, or a combination?
- How does data move? Does the system collect readings remotely through a fixed network, or does someone still need to pass near the meter?
- How often is usage recorded? Monthly totals and hourly interval reads support very different decisions.
- Who turns readings into bills and alerts? The meter is only one part of the process.
- Who controls the data and manages compliance? A phased rollout can leave old and new systems operating together.
These questions connect directly to building outcomes. Better interval data can make tenant invoicing more transparent, help identify unusual consumption, and separate shared loads from tenant usage. But AMI doesn't automatically produce savings. The owner still needs sound meter placement, approved equipment, clear billing rules, reliable communications, and a service process that handles exceptions.
Practical rule: Treat AMI as building infrastructure, not as a smart gadget. The communications and data-management layers determine whether the meter produces dependable value.
How Advanced Metering Infrastructure Actually Works
The easiest way to understand AMI is to compare it with a phone network. The smart meter is the phone. It records consumption and sends a message. A collector is similar to a cell tower, the communications network carries the message, and the head-end or data-management environment receives, stores, checks, and distributes the information.
Ontario's policy definition makes the same point in more formal language. It describes AMI as a complete system of meters, communication devices, collectors, wide-area network links, and control computers, after setting targets for smart-meter installation in homes across the province (Ontario's AMI functional specification)).
The main layers
The meter measures. A suite or tenant meter records consumption and attaches a time reference to the reading. In a multi-family property, that endpoint may serve one apartment. In a commercial building, it may measure a tenant panel, a mechanical load, or a common-area circuit.
The communication device transmits. The meter needs a way to send its information beyond the electrical room. Depending on the design, communications may use radio, a wired connection, cellular service, or another network approach. The important property-owner question isn't the technical label. It's whether the connection works consistently through concrete, basements, electrical rooms, and dense tenant spaces.
Collectors gather local messages. A collector receives information from multiple endpoints in its coverage area. The cell-tower analogy helps here. A meter may be working perfectly while the collector, antenna, or local connection has a problem, so the complete system needs health monitoring rather than occasional meter inspection.
The wide-area network carries the information. The WAN links the local collection point to the utility or submetering operator's central systems. If the network is interrupted, the meter may continue recording locally, but the operator may not receive the information until communications resume.
The head-end and data-management systems process it. The head-end system communicates with the meters and manages the network connection. A meter data management system, or MDMS, stores and processes readings so they can support billing, reporting, and analysis. Owners evaluating broader connectivity projects may also find IoT deployment help by Networking2000 useful for understanding how connected devices depend on communications planning.
One reading from suite to bill
Ontario's specification requires hourly reads from deployed devices, with each reading time-stamped to the minute and transferred to the meter data repository by 5:00 a.m. local time after the daily read period. It also requires collectors to retain a rolling 60 days of meter reads (Ontario Auditor General material on smart metering).
In practical terms, a suite meter records usage during an hour, assigns the reading its time information, sends it to a collector, and travels through the network to the central system. The data layer can then check whether the reading is complete, associate it with the correct account, and pass it into billing or reporting. A property owner wanting a visual explanation of the endpoint-to-system journey can review how networked metering works.
AMI Versus AMR and Legacy Meters
“Remote meter reading” can refer to different systems. Automatic meter reading, or AMR, usually automates collection without creating a fully interactive network. A device may store a reading until a worker or vehicle passes nearby and retrieves it. That reduces manual entry, but it may not provide AMI's regular two-way communication, event reporting, or approved remote commands.
A legacy meter relies on someone visiting the site and recording the register. It can suit a small property with simple access and limited billing requirements. The process becomes harder when access is restricted, tenants change often, charges are disputed, or several utility loads must be allocated across suites and common areas.
Capability
Manual Reading
AMR
AMI
Read collection
A person records the register on site
A device collects a stored read during walk-by or drive-by activity
A fixed network collects readings automatically
Read frequency
Depends on visits
Depends on collection routes and schedules
Can support regular interval data, including hourly reads where specified
Data granularity
Usually a cumulative register at the visit
More automated, but still dependent on the collection process
Time-stamped interval records support load profiling
Outage visibility
Usually discovered during a visit or customer report
Limited by the next collection event
Network and meter events can be monitored centrally
Remote control
Not available
Generally limited
May support two-way communications and approved remote functions
Tenant billing
Manual processing and greater transcription risk
Better collection efficiency
Stronger fit for automated billing, exceptions, and consumption analysis
Ontario's smart-metering requirements show the operational difference between a stored read and interval data. The specification calls for hourly readings, minute-level timestamps, transfer to the central repository by 5:00 a.m. local time after the daily read period, and collector storage for a rolling 60 days. These requirements are summarized in the Ontario smart-metering requirements.
Choosing the right level
AMR can be a sensible choice. A small property with straightforward access and limited reporting needs may not need the communications and data-management systems that AMI requires. Manual reads can also remain practical for isolated equipment or temporary verification.
AMI fits buildings that need repeatable billing, interval visibility, remote collection, common-area allocation, usage alerts, or portfolio-level reporting. For a multi-family or commercial owner, the decision also includes governance and rollout risk. Confirm which endpoints the system can communicate with, how often readings are captured, what happens when a read is missing, and whether the service includes data validation. Ask how tenant data is assigned, retained, and shared, especially when installation is phased across a portfolio.
A provider should also clarify whether AMI installation is scheduled to continue through December 31, 2027, where that timeline applies. Those answers show whether the proposal is AMR, AMI, or a hybrid arrangement, and whether the system can support the building's compliance and billing process as it expands.
AMI Use Cases for Multi-Family and Commercial Properties
AMI becomes easier to evaluate when you tie it to a building decision. The same networked meter can support different outcomes depending on how the owner structures billing, operations, and tenant communications.
Converting bulk charges into unit-level visibility
A multi-family owner paying a bulk electricity bill may have limited insight into suite consumption. Installing unit-level meters and collecting readings remotely can support a cost-recovery model where charges reflect measured use rather than a broad allocation. The value is not only financial. Residents can see how their bills relate to actual consumption, and managers can investigate a disputed charge with a reading history instead of relying on a single manual visit.
The same approach can apply to water, thermal energy, or gas where permitted and where the building's physical and regulatory conditions support it. A provider should explain which utility is being measured, how meters are commissioned, and how tenant accounts connect to the correct endpoint.
Separating tenants from common areas
A commercial landlord may need to distinguish tenant consumption from elevators, lobby lighting, pumps, parking equipment, and mechanical systems. Common-area metering creates a separate measurement boundary. AMI then supplies a consistent stream of readings for each boundary, giving the owner a clearer basis for budgeting, lease administration, and investigation of unexpected loads.
That separation can also reveal operational questions. If a common-area profile changes sharply, the property team can check equipment schedules, controls, or maintenance conditions. The system doesn't diagnose every cause on its own, but it gives staff a time-based pattern to investigate.
Resolving disputes and spotting leaks
Student housing and affordable housing operators often manage residents with different move-in dates, billing questions, and account changes. A time-stamped data history can help the operator confirm whether a bill reflects an actual read, a transition between occupants, or a data exception requiring review.
Water presents another useful example. A slow leak may create a sustained usage pattern outside the building's normal profile. An alert process can bring that pattern to the manager's attention before visible damage occurs. That's why leak detection should be evaluated as part of the metering program, not treated as an unrelated add-on.
For a practical discussion of connected utility monitoring, this video provides additional context:
Matching the system to the property
The right design depends on the number of units, meter locations, access conditions, utility types, and billing rules. Modern submetering programs can serve properties ranging from smaller buildings to large portfolios, but the owner still needs a site-specific plan.
Ontario's smart-meter initiative shows why lifecycle thinking matters. The Auditor General reported $1.9 billion in implementation costs by May 2014, while broader commentary estimated that total program costs could ultimately reach about $50 billion (Ontario Auditor General report on the smart-meter initiative). A building-level business case should therefore look beyond the hardware price and assess collection, data management, billing accuracy, maintenance, and long-term operational gains.
The Data and Analytics Layer Behind the Meters
The meter is visible. The data layer does the quieter work that determines whether the system is useful. A reading becomes valuable only after the platform connects it to the right unit, checks its quality, stores it securely, and presents it in a form a manager can act on.
An AMI record may include an interval value, a timestamp, a meter identifier, and an event or communication status. A billing system needs more than raw numbers. It needs a dependable relationship between the meter, the premises, the account, the billing period, and the applicable rules.
From readings to management decisions
Interval data helps a manager see the building's normal pattern. Electricity may rise during occupancy, water may show a steady overnight flow, and a mechanical system may operate outside its intended schedule. The manager can compare the observed pattern with expected operations and decide whether to inspect equipment, review tenant communication, or adjust a maintenance plan.
Leak detection follows the same logic. A system can flag sustained or unusual consumption, then send that exception to a person or workflow. The alert doesn't replace inspection. It shortens the time between an abnormal pattern and a useful response.
Owners can also use AMI data for:
- Billing review: Match invoices to actual interval records and investigate missing or irregular reads.
- Load profiling: Compare tenant, common-area, and building-level patterns across operating periods.
- Budget planning: Use observed consumption behaviour to support more informed forecasting.
- Service verification: Check whether a meter is communicating and whether an endpoint needs attention.
Businesses building broader reporting processes may find data management analytics for SMBs helpful as background on organising operational information. For submetering-specific workflows, usage-based billing with Axis Meter Solutions shows how consumption records can feed tenant billing and reporting.
Governance is part of the design
AMI creates a larger information system, and that system can contain sensitive tenant-level usage data. Canadian security guidance identifies increased risks involving customer privacy, data security, and cyberattacks across meters, head-end systems, MDMS platforms, and communications networks. The same guidance notes that Ontario processes reads from over 5.3 million smart meters daily (Canadian AMI security and governance guidance).
Property owners should ask who can access raw readings, who can export them, how accounts are segmented, and how the provider handles employee and contractor permissions. They should also ask what happens when communications fail. A resilient program should explain local data retention, recovery procedures, read estimation rules, escalation contacts, and the process for correcting a bad meter-to-suite association.
Data is an operating asset, but it's also a responsibility. The owner needs clear answers about access, retention, corrections, security, and continuity before residents depend on the resulting bills.
Phased Rollouts, Compliance, and Common AMI Misconceptions
The most common AMI misconception is that deployment is a clean cutover. A contractor removes an old meter, installs a smart meter, activates communications, and the building moves forward. That can happen in some projects. Large or complex portfolios often have old and new endpoints operating together while crews work through access limits, equipment availability, approvals, and system integration.
The difficult question is often not installation logistics. It's how the owner keeps the remaining legacy meters compliant, safe, and readable during the transition.
Legacy equipment can outlast the project plan
Toronto Hydro asked for temporary dispensation for 121,011 electricity meters whose seals were due to expire at the end of 2025, while AMI installation continued through December 31, 2027 (AMI project status and regulatory filing). The example matters because it shows how meter compliance deadlines can extend beyond the date a project was first approved.
For a property owner, that creates practical questions. Which meters remain in service? Who tracks inspection or seal dates? What happens to a tenant's bill if an endpoint is removed, replaced, or temporarily unavailable? Can the provider distinguish a genuine zero-use period from a communications failure?
A phased plan should document the old system and the new system together. It should identify the meter at each location, the account it serves, the approved replacement, the installation status, and the fallback billing process.
Data authority can change during deployment
Ontario's Smart Metering Entity received exclusive authority over bi-directional smart-metering data as of January 1, 2025, according to the same filing. That development illustrates a broader governance reality. Deployment doesn't end the policy conversation. Regulators and system operators may continue defining who controls, handles, and accesses new categories of metering information.
Property owners should make these checks part of procurement:
- Confirm equipment approval: Verify that the proposed meters and installation process meet the requirements of the applicable jurisdiction, including Measurement Canada requirements where relevant.
- Define account ownership: Put in writing who owns the meter, who maintains it, and who is responsible for replacement.
- Map the transition: Ask how old and new readings are reconciled when a building migrates in phases.
- Protect billing continuity: Require a documented process for missed reads, communications outages, tenant moves, and meter exchanges.
- Clarify data access: Identify who can view, export, correct, and retain suite-level consumption information.
- Set escalation rules: Establish who responds when a meter stops communicating or a resident challenges a charge.
AMI is not risky because it's connected. It's manageable when the owner understands the connections, responsibilities, and failure procedures before the first installation.
What AMI Means for Your Submetering Program
For a building owner, AMI capability is increasingly a baseline requirement rather than a technical luxury. Interval data, remote collection, usage alerts, and a dependable billing workflow turn a meter from a monthly register into an operating tool. The result can be clearer cost recovery, more transparent tenant communication, and earlier visibility into unusual consumption.
Before signing a submetering agreement, ask:
- What is measured? Confirm the utility types, suite meters, common-area meters, and allocation boundaries.
- How often is data collected? Ask whether the system provides interval reads and how missing records are handled.
- Who manages the platform? Clarify responsibility for communications, data validation, billing, maintenance, and resident support.
- How are leaks identified? Request the alert thresholds, notification process, and response expectations.
- How is compliance maintained? Verify equipment approvals, commissioning, permits, and transition procedures.
- What happens at contract end? Establish ownership, data portability, meter removal, and replacement obligations.
A turnkey program can combine equipment, installation, commissioning, tenant billing, monitoring, and ongoing maintenance under a long-term agreement. Axis Meter Solutions offers these submetering services for multi-family, condominium, mixed-use, and commercial properties, including electricity, water, gas where permitted, thermal energy, common-area metering, and leak and flood detection.
If your building still relies on bulk utility costs, manual reads, or unclear common-area allocations, review the meter locations, current billing process, and compliance requirements before choosing a provider. Visit Axis Meter Solutions to discuss an AMI-based submetering program that connects measurement, tenant billing, monitoring, and ongoing service.
Ready to Optimize Your Utility Management?
Tell us about the property, utility, number of units, and your billing or monitoring goals. We'll help you identify the right next step.
Book a Call