Most industrial monitoring is assembled: someone else's sensors, someone else's gateway, someone else's cloud, integrated by a fourth party. It works, until something doesn't — and then the diagnosis crosses three support contracts and two time zones. addaNet is built in-house at every layer, which is not a boast about capability so much as a decision about accountability: when a reading looks wrong, one team can follow it from the terminal block to the chart.
Flow, level, pressure, temperature, vibration, current, energy, water quality proxies. Our own low-power sensor hardware where a measurement is genuinely absent — and nothing new where it isn't.
PLCs, drives, MCCs, energy meters, flow meters and generator controllers, over 500+ industrial protocols including Modbus, OPC-UA and MQTT. On most plants a substantial share of the data you want already exists and simply is not retained.
Store-and-forward, battery-buffered, with local logging that survives an outage and back-fills when the link returns. Connectivity chosen per site: LoRaWAN or 4G, according to coverage rather than preference.
Retention, trending, reconciliation, threshold and rate-of-change alerting, role-based access across sites, and export in the shape a regulator's return or a board pack actually needs. Usable on a phone over 3G.
A real addaNet screen rather than a mock-up: a water-quality device on a demonstration line at our Johannesburg base, with live values, three-hour trends and the raw record table — the same layout a production line, a borehole or a generator site gets, with its own parameters.
Building in-house has one more consequence worth naming. When a site needs something the product does not do — a protocol nobody expected, a report in a regulator's format, an alert rule with local logic — it becomes a development task rather than a feature request to a vendor abroad. That is why our country pages can promise export "in the shape the return needs": we can actually change the shape.
Production and downtime — counts, run state, stop events and reasons per line · Energy — sub-metering by line, department and source, separating grid from generator · Condition — vibration, temperature and motor current trended on rotating plant · Water — abstraction, zone metering, night flow, tanks, boreholes and pumps · Effluent and compliance — discharge flow with quality proxies, and the continuous record regulators increasingly require · Standby power — generator run hours, fuel, changeover timing and start-failure detection.
Those are not six products. They are six views of one dataset, which is why sites that start with one line or one water system tend to extend rather than replace.
See solutions by market, or the technical write-up on our South African site: addanode.co.za technology.
Send an engineer a few panel photographs and your meter models. The answer to "what can be read without buying anything" is usually more than expected.