What is IoT? The Internet of Things explained

What is IoT? A plain definition

The Internet of Things — IoT — is the network of physical objects that have been given sensors, processing power and a network connection so they can collect data about themselves or their surroundings and share it with other devices and software over the internet. That is the IoT meaning in one sentence: everyday things made measurable, connected and remotely monitorable.

The phrase was coined in 1999, but the idea is simple. A pump, a water meter, a delivery truck or a cold-storage unit has always produced useful information — how hard it is working, how full it is, where it is, how warm it is. IoT technology is what captures that information automatically and puts it somewhere a person or another system can use it, instead of leaving it locked inside the object until someone walks up and checks.

Crucially, IoT is not one product you buy. It is an architecture — devices, networks, edge hardware and software working together. When people ask "what is IoT," they are usually really asking how those pieces fit, so let us walk through how IoT works.

How IoT works: the four layers

Almost every IoT system, from a smart doorbell to a mine-wide monitoring platform, is built from the same four layers. Understanding them is the fastest way to cut through the marketing.

1. Devices and sensors. This is where the physical world is turned into data. A sensor measures something — flow, vibration, level, temperature, position — and the device digitises it. This is the bottom layer that gives IoT its name: the "things".
2. Connectivity. The data has to travel. Depending on the use case that might be 4G, LoRaWAN, NB-IoT, Sigfox, Wi-Fi or a wired link. Choosing the right network for range, power and cost is one of the most important early decisions — we cover it in the connectivity guide.
3. Edge. A gateway or edge device on site collects readings from many sensors, does first-pass processing, and — importantly in South Africa — buffers data locally so nothing is lost when power or connectivity drops. The trade-offs between processing on site and in the cloud are covered in edge vs cloud.
4. Platform and applications. Finally the data lands in software that stores it, analyses it and turns it into something useful: a live dashboard, an alert, a report, a trend, or an automated action. This is where IoT applications actually deliver value.

The value of any IoT system is never the data itself — it is the decision the data enables: a pump fixed before it fails, a leak caught in hours instead of weeks, a truck rerouted, a cold-chain breach flagged before stock spoils.

IoT devices and IoT sensors: what they actually are

An IoT device is any physical object that can connect to a network and exchange data. It pairs one or more sensors (and sometimes actuators that act back on the world) with a small processor and a radio or wired link. IoT sensors are the measuring components inside those devices — the part that converts a physical quantity into an electrical signal that can be digitised and sent.

In industrial settings, the IoT sensors that matter most are concrete and unglamorous:

• Flow sensors — measure how much water, effluent or fluid is moving through a pipe; the backbone of leak and non-revenue-water detection.
• Vibration sensors — detect the early signature of bearing and pump failure on rotating equipment, often weeks before it breaks.
• Level sensors — track how full a tank, reservoir, silo or sump is.
• Temperature sensors — monitor motors, bearings, processes and cold chains.
• GPS / location — track vehicles, trailers and mobile assets across a fleet or a site.
• RFID tags and readers — identify and count stock, tools and assets as they move.

These same building blocks appear everywhere from a home thermostat to a mine. What changes is the ruggedness, the network, and how much you trust the decision the data drives.

Consumer, enterprise and Industrial IoT (IIoT)

Not all IoT is the same. It helps to split it into three tiers, because the engineering, the stakes and the budgets are very different. This is also where the difference between IoT and industrial IoT (IIoT) becomes clear.

Industrial IoT is IoT applied to the assets that run a business — and engineered to a far higher bar for ruggedness, reliability and integration. A consumer sensor that drops a reading is a nuisance; an IIoT sensor that misses a developing pump failure can shut a line or flood a reservoir. If you operate plant, water infrastructure or mining equipment, IIoT is the tier that matters. We go deeper in the Industrial IoT in South Africa guide, and the addaNet platform is built specifically for it.

Real-world IoT applications by sector

IoT examples are easiest to grasp by sector. Here is where the technology earns its keep in South Africa:

• Water. Smart metering, flow and pressure monitoring, leak and non-revenue-water detection, reservoir levels and effluent/DWS compliance — see water management.
• Mining. Equipment condition monitoring, ventilation and environmental sensing, and asset tracking underground and across remote sites — see mining optimisation.
• Manufacturing. OEE and downtime tracking on production lines, energy monitoring and machine health — see OEE management and asset monitoring.
• Agriculture. Soil moisture and irrigation control, tank and borehole levels, and livestock and cold-chain monitoring across large, low-connectivity farms.
• Fleet and logistics. GPS tracking, fuel and driver-behaviour monitoring, and cold-chain temperature assurance for goods in transit.
• Smart metering and energy. Remote reads of water, electricity and gas, plus demand monitoring to manage tariffs and peaks.

Notice the pattern: in every case the IoT application turns something previously invisible — a slow leak, a hot bearing, a cooling truck, an idle line — into a timely, actionable signal.

IoT in the South African context

The Internet of Things works the same way physically everywhere, but the conditions it has to survive in South Africa are unusual, and they shape good design:

• Load shedding. A cloud-only system goes blind the moment power drops — and often that is exactly when conditions get interesting. The fix is edge buffering plus a small UPS on the gateway so readings are captured locally and synced when power returns. This must be designed in, not bolted on.
• Connectivity. Many industrial sites are remote or have patchy mobile coverage. Long-range, low-power networks like LoRaWAN and NB-IoT often beat 4G for scattered sensors, while 4G suits high-bandwidth needs. There is no single right answer — it depends on the use case.
• Cost and skills. Budgets are in Rand and scrutinised. The pragmatic path is to read equipment you already own rather than rip-and-replace, start with one high-value problem, and choose a system your existing team can run — backed by a local partner who answers the phone.

How to evaluate an IoT project

If you are considering IoT for your operation, judge any proposal against a few simple tests:

1. Start from the decision, not the device. Name the specific, expensive problem you are solving and who will act on the output, then work back to the minimum sensing required. Sensor-first projects become costly wallpaper.
2. Can the vendor explain it in the four layers? Devices, network, edge, platform. If they cannot, be cautious.
3. Is it designed for outages and your connectivity? Edge buffering and backup power are not optional extras in South Africa.
4. Does it work with what you already own? A good system reads your existing sensors, instruments and PLCs instead of forcing a replacement.
5. Can your team actually use it? Clear alerts to named owners and simple trends beat a system that needs a flown-in specialist to interpret every reading.
6. Can you prove payback on a small pilot first? One line, one site, one quarter. A successful pilot funds and de-risks the rollout.

The Internet of Things is not magic and it is not a buzzword to chase. At its best it is a practical way to connect the assets you already run, make one expensive problem visible, and act on it sooner — on infrastructure engineered for the conditions you actually operate in.

Frequently asked questions