Industrial IoT in Zimbabwe — one platform, from the sensor to the number your board reads.
addaNet is our own platform: hardware, firmware and software built in-house rather than assembled from three vendors' products. On a Zimbabwean site that matters for one practical reason — when something needs to change, it changes, because the people who built it are the people who support it. It reads the PLCs, meters and instruments you already own, adds measurement where it is genuinely missing, and holds a continuous record through the network faults that still interrupt an ageing distribution grid.
Four places the platform earns its keep.
Production and downtime
With manufacturing running near 56% of capacity and about a third of firms investing in expansion, the most valuable number on a Zimbabwean plant is where the other 44% goes. Counts, run state, stop events and reasons, per line.
Capacity & lost output →Energy, sub-metered
One incoming meter tells you the bill. Sub-metering tells you which line, department or drive earned it — and makes energy per tonne a measured figure rather than an allocation. It is also the fastest way to find plant that runs when nothing is being produced.
Energy monitoring →Condition on rotating equipment
Vibration, temperature and current on mills, pumps, fans, compressors and conveyors. Continuous trending turns a bearing failure from a weekend emergency into a planned repair with the part already ordered.
Condition monitoring →Water, effluent and boreholes
Abstraction and discharge flows, quality proxies, tank and borehole levels, pump behaviour. On a licensed site this is compliance evidence as well as operating data.
EMA effluent monitoring →Engineered for Zimbabwean site conditions.
- Unplanned interruptions, not scheduled ones. Zimbabwe has run roughly 188 consecutive days without national load shedding — recorded during a June 2026 parliamentary oversight visit to Kariba South — but an ageing transmission and distribution network still produces local faults. Unplanned events are harder to record than scheduled ones, because nobody is standing by when they happen. Nodes are battery-buffered, log locally and back-fill, so an interruption appears in the record as an event rather than as missing data.
- Supply concentrated on one river. Kariba South supplies about 45% of annual generation, and ZESA is co-managing lake drawdown with Zambia's ZESCO against El Niño risk while developing solar capacity. A plant that meters its own consumption can respond early if that picture changes.
- Connectivity that varies by site. Cellular where it is reliable, LoRaWAN for sites spread beyond it, wired where the plant supports it — with local storage under all three, so a connectivity gap costs latency rather than history.
- Dust, heat and vibration. The hardware is built for Southern African industrial conditions because that is where it was developed and where it runs every day, a border away.
- No published industrial tariff to plan against. Zimbabwe does not publish a reliable current industrial electricity rate, and the most recent figure we could find is a 2022 mining rate that would mislead if reused. Sub-metering gives you your own effective cost per kWh and per tonne, measured from your own bills and your own consumption, which is the only version that survives a tariff review.
What an addaNet deployment in Zimbabwe looks like.
- Remote assessment. Plant layout, panel photographs, nameplates, and what can already be read electronically. Most sites have more available signal than they expect.
- Written scope and cost band before anything is ordered, separating what is read from existing equipment from what needs a new instrument.
- Hardware pre-configured in Johannesburg, shipped overland, arriving ready to commission.
- Installation by your electricians or a local contractor under live remote guidance, in your own time zone.
- Dashboards and alerts set up around the decisions people actually make — the screen a supervisor opens at shift start, and the alert that should wake someone.
- Remote support and iteration from the team that built the platform, with firmware and features adapted as the site's questions change.
First deployments are typically live within two to six weeks of the assessment call. See instrumentation and control in Zimbabwe for what sits underneath the platform.
Zimbabwean sites, and the first signal
| Site type | First measurement | Who reads the record |
|---|---|---|
| Manufacturer at 55.9% capacity utilisation (CZI 2025) | Counts + run state → where the missing time is | Plant management |
| Plant with a good control house | Existing 4–20 mA and Modbus read, not replaced | Engineering |
| Licensed discharger (EMA bands) | Flow + concentration → mass flow, quarterly returns | EMA |
| Mine or steelworks (Manhize) | Rotating-asset vibration + energy per tonne | Operations |
| Borehole under ZINWA permit | Abstraction + level | ZINWA, sub-catchment council |
| Harare prepaid water zone (600,000-meter programme) | Bulk vs sum-of-units | The council and residents in dispute |
Where this lands first in Zimbabwe.
Agro-processing — sugar, beverages, grain milling and tobacco, where the season sets the stakes on throughput · Steel, cement and building materials — drive-heavy and energy-intensive, where sub-metering and condition monitoring pay first · Mining and minerals processing — comminution and pumping loads, water balance and the compliance record · Fertiliser and chemicals — process variables, batch records and discharge obligations in one view · Packaging and plastics — fast lines where a small stoppage rate compounds into real tonnage · Water utilities and estates — borehole, tank and prepaid-metering telemetry, including independent verification around Harare's prepaid rollout.
Industrial IoT in Zimbabwe — common questions
Can addaNet read our existing PLCs and meters?
That is the normal starting point. Modbus, OPC, pulse outputs and analogue signals are all read directly, and on most plants a substantial share of what you want to see already exists somewhere in the control system without being retained. New instruments go in where a measurement is genuinely absent — which keeps a first project to the size of the gap rather than the size of the plant.
Does monitoring keep recording during a power interruption?
Yes, and on a network that still faults locally this is the feature that decides whether the data is worth having. Nodes are battery-buffered and store readings locally, back-filling to the platform when the link returns. The interruption itself is logged as an event with a start, an end and whatever the plant was doing on either side of it.
Cloud or on-premise?
Cloud for most sites, because it removes a server, its backups and its patching from a plant that has enough to maintain. On-premise or hybrid where a client's policy requires data to stay on site, or where a mine's connectivity makes local-first the sensible architecture. Because we build the platform, both are configurations rather than different products.
Can we monitor several sites on one platform?
Yes — group operations, contractors managing plant across client sites, and utilities with distributed assets all run this way. Sites roll up to a comparison view and drill down to individual equipment, with access controlled per site so a contractor's client sees only their own.
How does support work in Zimbabwe?
Our engineering team is in Johannesburg, a border away and in the same time zone, with support on WhatsApp during working hours. Installation is done by your technicians or a local partner under live remote guidance, and hardware moves overland. Zimbabwe is among the more straightforward markets we support for exactly those reasons.
What does a first deployment cost?
Driven by how many measurement points, how many can be read from equipment you already own, whether power and network reach each point, and how much integration is needed. We quote a written cost band after a remote assessment. Starting with one line or one system is both cheaper and more informative than instrumenting a whole site, because it produces a complete picture of one thing rather than a partial picture of everything.
See your Zimbabwean site on one dashboard.
Tell an engineer what you run and what you can already read. You'll get an honest view of what to monitor first and what it would cost.