“Latency is not merely a measure of time in a network, it is a measure of consequence. In electricity systems, every millisecond gained or lost defines the boundary between awareness and action, between stability and disruption.” – MJ Martin
Defining Latency versus Delay
Latency is the elapsed time between the initiation of a data transmission and the moment that data is received and becomes usable at its destination. It is typically measured in milliseconds and represents an end to end performance metric across a communications network. Delay, by contrast, is a broader term that refers to the individual components that contribute to latency. These components include processing delay within devices, queuing delay at intermediate nodes, transmission delay across a medium, and propagation delay dictated by the physical distance and speed of the signal.
In practical engineering discourse, latency is often treated as the aggregate of all delays. Therefore, while the terms are related, they are not identical. Delay is granular and component specific, whereas latency is holistic and system level. In AMI 2.0 networks, particularly those based on mesh architectures such as Wi-SUN, this distinction is critical because each hop introduces incremental delay that accumulates into total latency.
Latency in AMI 2.0 Smart Metering
Advanced Metering Infrastructure 2.0 networks are designed primarily for telemetry, billing, and operational awareness rather than real time control. In a Canadian electricity distribution context, smart meters typically transmit interval data at fifteen minute or hourly granularity. As a result, the tolerance for latency is relatively high. End to end latency in the range of one to several seconds is generally acceptable, and in many cases even tens of seconds does not materially affect billing accuracy or system analytics.
Mesh network behaviour must be considered. Each hop in a radio frequency mesh may introduce latency on the order of 10 to 50 milliseconds under nominal conditions. A network with five to ten hops may therefore accumulate latency in the range of 50 to 500 milliseconds before accounting for backhaul and headend processing. When congestion, retries, or interference are introduced, this can extend into multi second ranges. For standard AMI use cases in Canadian electricity utilities, such latency remains within acceptable operational thresholds.
Latency Requirements for Smart Grid Applications
The introduction of smart grid functions onto the same communications fabric significantly alters latency requirements. Applications such as fault detection, isolation, and service restoration, distributed energy resource coordination, and voltage regulation operate on time scales tied to electrical cycles. In North America, including Canada, the grid operates at 60 Hz, meaning one cycle of power is approximately 16.67 milliseconds.
Protection and control systems often require responses within one to four cycles, corresponding to approximately 16 to 67 milliseconds. Even less time is desirable for high speed protection schemes. This creates a fundamental constraint when attempting to leverage AMI networks for grid control. A multi hop mesh network with cumulative latency exceeding 100 milliseconds is generally unsuitable for time critical grid operations. Consequently, utilities typically segregate networks or deploy parallel low latency communication channels, such as fibre or private LTE, for protection grade applications.
Constraining Hop Count to Control Latency
One of the most effective engineering controls for managing latency in a mesh AMI network is the deliberate constraint of hop count. Because latency increases approximately linearly with each additional hop under steady state conditions, limiting the maximum number of permitted hops imposes a deterministic ceiling on worst case latency. In practice, many utilities target a design envelope of no more than five to seven hops between endpoint and data collector for electricity AMI networks.
Constraining hop count is not simply a configuration parameter but a network design discipline. It requires strategic placement of collectors, access points, or gateways to ensure adequate coverage while minimizing path length. Densification of infrastructure, including additional pole mounted routers or relays, can materially reduce hop depth and improve both latency and reliability. There is a direct trade off between capital expenditure and network performance, and Canadian utilities often favour a moderate increase in infrastructure density to ensure predictable latency across geographically diverse service territories.
Routing algorithms also play a role. Cost based routing metrics can be tuned to penalize excessive hop counts, even if signal strength appears acceptable. This encourages the network to select paths that are not only robust but also efficient in terms of latency. Without such constraints, mesh networks may converge on stable but sub-optimal long paths that degrade performance under load.
Implications of Excessive Latency
Excessive latency introduces both operational and strategic risks. In the context of electricity smart metering, high latency can degrade the timeliness of interval data availability, delay outage detection, and reduce the effectiveness of near real time load monitoring and demand response signals. While these impacts are often manageable, they can erode the value proposition of AMI investments if not properly controlled.
In smart grid applications, the consequences are more severe. Latency beyond acceptable thresholds can lead to delayed fault isolation, increased outage durations, and reduced effectiveness of distributed energy resource coordination. In extreme cases, protection systems may fail to operate within required timeframes, increasing the risk of equipment damage or cascading failures.
Summary
From a Canadian utility perspective, where networks often span large and environmentally challenging regions, managing latency is both a technical and economic imperative. Constraining hop count, optimizing routing behaviour, and aligning network architecture with application requirements are essential to ensuring that AMI 2.0 systems deliver reliable performance for both metering and evolving grid applications.
About the Author:
Michael Martin is the Vice President of Technology with Metercor Inc., a Smart Meter, IoT, and Smart City systems integrator based in Canada. He has more than 40 years of experience in systems design for applications that use broadband networks, optical fibre, wireless, and digital communications technologies. He is a business and technology consultant. He was a senior executive consultant for 15 years with IBM, where he worked in the GBS Global Center of Competency for Energy and Utilities and the GTS Global Center of Excellence for Energy and Utilities. He is a founding partner and President of MICAN Communications and before that was President of Comlink Systems Limited and Ensat Broadcast Services, Inc., both divisions of Cygnal Technologies Corporation (CYN: TSX).
Martin served on the Board of Directors for TeraGo Inc (TGO: TSX) and on the Board of Directors for Avante Logixx Inc. (XX: TSX.V). He has served as a Member, SCC ISO-IEC JTC 1/SC-41 – Internet of Things and related technologies, ISO – International Organization for Standardization, and as a member of the NIST SP 500-325 Fog Computing Conceptual Model, National Institute of Standards and Technology. He served on the Board of Governors of the University of Ontario Institute of Technology (UOIT) [now Ontario Tech University] and on the Board of Advisers of five different Colleges in Ontario – Centennial College, Humber College, George Brown College, Durham College, Ryerson Polytechnic University [now Toronto Metropolitan University]. For 16 years he served on the Board of the Society of Motion Picture and Television Engineers (SMPTE), Toronto Section.
He holds three master’s degrees – in business (MBA), communication (MA), and education (MEd). As well, he has three undergraduate diplomas and seven certifications in business, computer programming, internetworking, project management, media, photography, and communication technology. He has completed over 80 next generation MOOC (Massive Open Online Courses) [aka Micro Learning] continuous education programs in a wide variety of topics, including: Economics, Python Programming, Internet of Things, Cloud, Artificial Intelligence and Cognitive systems, Blockchain, Agile, Big Data, Design Thinking, Security, Indigenous Canada awareness, and more.