Municipalities evaluating advanced metering systems in South Africa should shortlist connectivity by service area and operational requirement. Cellular can suit dispersed meters where indoor coverage is dependable; RF mesh can suit dense neighbourhoods with enough powered nodes to maintain alternative routes; power-line communication (PLC) can suit electrically coherent networks where signal quality has been demonstrated. A municipality with varied settlement patterns may need more than one communications technology.
The initial decision should remain conditional until field testing shows that the proposed architecture can deliver usable readings, execute required commands and recover after power interruptions. Coverage maps, radio range claims and successful laboratory demonstrations provide useful screening evidence. Municipal acceptance should depend on performance at installed meter locations, through the full path to billing and operational systems.
A monthly billing read, an interval-data service and a remote switching command place different demands on connectivity. A connection that eventually retrieves accumulated consumption may be adequate for one billing process but unsuitable for time-sensitive operational work. Technical teams need to define these differences before comparing proposals.
Start with the workflows the municipality intends to operate. For each, specify the required delivery window, acceptable missing-data level, retry behaviour and response to communication failure. Include the number of meters involved: retrieving one reading during a demonstration says little about whether a fleet can complete its scheduled upload within the available window.
Separate communication availability from electricity availability. A meter may continue recording locally while its communications path is unavailable. Conversely, a working network cannot provide a fresh reading from an unpowered meter unless that meter has the necessary backup capability. These distinctions determine what the municipality can reasonably expect during an interruption.
South African municipal evaluations should explicitly include load shedding and other supply interruptions as operating conditions. Check the backup arrangements for meters, collectors, gateways and backhaul equipment separately. An end-to-end service depends on every necessary link, including equipment operated by a telecommunications provider.
Direct cellular connectivity can reduce the need for municipality-owned neighbourhood communications equipment. It is a useful candidate for scattered commercial meters, remote installations and areas where building a dedicated network would be difficult to justify. Its suitability depends on the signal available to the selected modem and antenna at the actual installation position.
Outdoor handset reception provides limited evidence for a meter inside a metal cabinet, basement or service enclosure. Surveys should use representative hardware and examine connection stability, upload success and recovery after loss of service. Where alternative operators are proposed, establish how switching works, which networks the modem supports and whether the commercial agreement permits the intended roaming or fallback behaviour.
Ask bidders to identify the proposed cellular technology and its supported functions. LTE-based options, including LTE-M or NB-IoT where available and supported, have different deployment and device characteristics. Suitability for frequent reporting, remote commands and firmware transfer must be demonstrated on the offered service. Any proposal relying on older cellular generations needs a documented migration path and a clear allocation of replacement costs.
Cellular concentrates part of the operating dependency outside the municipality. Evaluate subscription management, SIM provisioning, service escalation, network changes and performance during widespread power interruptions. Direct-to-meter cellular and cellular backhaul for a group of meters also create different failure patterns: a shared backhaul failure can disconnect many otherwise functioning local links.
RF mesh allows participating devices to relay traffic through neighbouring nodes toward a gateway. Dense meter populations can provide several possible routes, making mesh a credible option for compact urban areas. The useful density is the density of reachable, operational devices; a high number of accounts within a suburb does not guarantee a reliable radio network.
Building materials, terrain, antenna placement and cabinet construction affect which nodes can communicate. A deployment may need additional routers or gateways to bridge difficult sections. Include their installation access, power supply, maintenance and replacement in the assessment, particularly where equipment must be placed outside existing municipal premises.
Mesh resilience requires specific examination during outages. If relay nodes lose power together, alternative routes may disappear at the same time. Backup energy may support an outage notification without sustaining extended forwarding. Require the supplier to explain what remains operational, for how long under the proposed configuration, and how routes rebuild when supply returns.
Capacity deserves equal attention. A network that handles routine readings may behave differently when thousands of meters reconnect, upload stored intervals or receive firmware. Test these conditions across representative numbers of hops and gateways. Additional gateways can improve capacity or resilience, but their backhaul and maintenance requirements must remain visible in the proposal.
PLC uses power conductors to carry communications and can be attractive where the electrical topology supports dependable links to a concentrator. Its performance depends on cable characteristics, connected equipment, electrical noise, branching and the position of communications equipment. These conditions can differ substantially between feeders.
Transformer boundaries, phase arrangements and coupling requirements need explicit design treatment. Ask where concentrators will be installed, which meters each will serve and what additional equipment is necessary. A supplier should explain how the design will accommodate feeder changes and how technicians will distinguish communications faults from electrical-network issues.
Test PLC while representative loads are operating, including inverter-connected equipment where present. A short trial under favourable conditions may miss disturbances that occur at other times. Local generation and storage can alter operating conditions, so trials should reflect the equipment mix expected in the service area.
PLC also requires a separate route from the concentrator into municipal systems, often through cellular or another backhaul service. Assess that complete architecture. Where part of the electrical path is de-energised, communication over that section may be unavailable; the recovery plan should explain how stored data is retrieved when supply returns.

A useful shortlist follows these boundaries: assess cellular first for dispersed sites with verified coverage, mesh for dense areas with viable radio paths, and PLC for suitable electrical networks supported by feeder-level measurements. Exceptions should follow evidence from the site. A hybrid deployment can accommodate these differences, provided the municipality can manage its integration and support requirements.
Connectivity determines how information travels; interoperability determines whether municipal systems can use it consistently. A successful meter read still needs the correct account association, timestamp, unit and validation status before it becomes billable data. Missing or inconsistent mappings can create manual work even when the communications network performs well.
Require bidders to describe the complete path from meter to head-end system, meter-data management and billing. Where DLMS/COSEM is proposed, identify the supported profiles, objects, security settings and tested combinations. Support for a named standard does not establish that every meter function will work across different suppliers’ systems.
Demonstrate the workflows that matter: meter replacement, account reassignment, clock synchronisation, missing-data recovery, tariff updates and export of historical records. If embedded generation is within scope, include import and export registers and their treatment in downstream systems. Communication cannot compensate for a meter configuration or billing interface that omits required data.
Remote disconnection and reconnection warrant particular care. The system should authenticate and authorise the command, preserve an audit trail and distinguish command receipt from confirmed execution. Procedures also need to address delayed commands, repeated requests and uncertain device status. A timeout must lead to a defined exception process rather than an assumed successful action.
Security requirements should cover device identity, protected communications, key management, administrator access and firmware updates. Private network arrangements can reduce exposure, but they do not replace application security. Establish who controls credentials and cryptographic material, how compromised devices are handled and how access is removed when contractors change.
Meter records linked to identifiable customers also require appropriate handling under South Africa’s Protection of Personal Information Act. Procurement should establish data-access responsibilities, hosting arrangements, retention rules and support access. Ask who can export the information and whether the municipality can retain usable records when a service contract ends.
A pilot should test the conditions most likely to affect the rollout decision. Include difficult cabinets, weak coverage locations, different building types and representative feeders. For mesh, include sparse edges and obstructed paths. For PLC, include electrically challenging sections. Assess all technologies through supply interruptions and restoration where these conditions can be observed or safely simulated.
Agree acceptance measures before installation. Average read success alone can conceal a persistent group of unreachable meters. Report performance by location, feeder and installation type, alongside the effort required to resolve failures. The municipality needs to know whether exceptions can be handled within its staffing and billing constraints.
Price the architecture that passes these tests over the municipality’s chosen evaluation period. Include modems, antennas, gateways, concentrators, backhaul, subscriptions, software licences, hosting, security maintenance and replacement work. Allow for firmware distribution and recurring diagnostics as well as normal readings. A low communications tariff can be outweighed by frequent site visits; shared infrastructure can become expensive if it serves fewer reliable connections than expected.
Compare costs per meter delivering the required service, alongside total expenditure. Also test the effect of network expansion, operator changes and supplier exit. Contract terms should make data export, replacement equipment, configuration access and migration responsibilities explicit. A hybrid architecture remains manageable when interfaces and ownership are clear; fragmented operating tools can erode its local performance advantages.
The final selection should connect each service area to demonstrated performance, defined recovery behaviour and an affordable support model. Where a pilot reveals a small cluster of persistent failures, resolve the cluster’s cause before extending the same design. That evidence is more useful for rollout approval than a favourable municipality-wide average that leaves the hardest meters unread.
Questions about market trends? Contact Market Scope Live for deeper business insights.
We respect your privacy. Your information is strictly confidential.
Related News