Are IoT devices really necessary, or are they just a trend?

Are IoT devices really necessary, or are they just a trend?

The value lies in the problem solved

Hello, IoT devices offer substantial benefits in some applications and add costs to simple tasks in others. An internet connection does not prove that a product is necessary or efficient. The useful question is: Which problem does connectivity solve, and how will we measure the result?

Making daily life easier is a valid benefit; not every improvement needs a financial return. However, pressing a button on a phone does not always justify replacing a device. Monitoring several sites or obtaining information from hard-to-reach equipment addresses a different need. When assessing IoT and IIoT, consider the application's importance and the consequences of interruptions.

When does it help?

For example, notifying a responsible person when a remote storage room exceeds its temperature limit may be useful. The value comes from identifying a problem in time to act, rather than from the sensor continuously producing data. If nobody monitors the alarm or can respond, more notifications may not deliver the expected benefit.

Monitoring a workshop compressor's operating hours and energy consumption to investigate unnecessary running can also be a worthwhile trial. Define data collection, analysis and the resulting action first. Test energy-saving claims by comparing consumption before and after installation under similar operating conditions. Internet connectivity alone does not produce savings.

When does it become an extra burden?

Replacing a reliable product that already does the job solely because a new one has an app is a weak justification. Unused features, repeated notifications and compulsory accounts may create more work than value. Assess ease of use against the person's needs: an app that improves access for one user may create an unnecessary obstacle for another.

Compare simple timers, local control, existing automation and unconnected products first. Moving an entire system to the cloud needs a separate justification when remote access is unnecessary. Preserving users' practical skills and the ability to intervene manually also belongs in the design decision.

Calculate total cost, not just purchase price

Include equipment, installation, gateways, data plans, subscriptions, maintenance and possible replacements in the total cost of ownership. The support period and update policy can also affect useful life. The FTC advises buyers to investigate how long software support will last and which functions remain when it ends. Software updates are therefore more than a technical detail.

In a purely illustrative calculation, suppose installation costs TRY 12,000, the monthly gross benefit is TRY 800 and additional operating expenses are TRY 200. The net monthly benefit is TRY 600, giving a simple payback period of 20 months. These are not market prices or promised returns; the example excludes financing, taxes, failures and future price changes. Use your own measurements for an actual decision.

What happens if the internet or cloud service fails?

If the internet connection drops, does the device continue its basic task, or does only remote monitoring stop? Can it operate locally if the manufacturer closes the service? Can you export the data? Compatibility with other systems and documented interfaces may reduce dependence on one provider, but are not available in every product.

Verify local operation, manual use and data export before buying. In industrial applications especially, do not treat a cloud notification as equivalent to on-site control and protection. The behaviour required to keep a critical task running needs its own design and testing.

Account for privacy and security

Device security is part of operating a connected product. Assess access permissions, secure configuration and update capability. NIST's IoT cybersecurity baseline provides a starting point for identifying the security capabilities of devices being purchased or integrated. A “smart” label is not a security certificate.

Data breach risk and privacy are different issues. A product can collect more information than you need without being hacked. Are its microphone, camera and location features necessary? Can continuous monitoring be disabled? Assess the access paths created by continuous connectivity and who receives the data. Treating every product as a hidden surveillance tool is no substitute for examining the actual design either.

Measure environmental benefits too

Digitalisation can improve energy use, while additional devices and data infrastructure also consume energy. The IEA highlights the need to consider both sides. Assuming that “a connected product is environmentally friendly” is insufficient. Extending the life of existing equipment differs from unnecessarily replacing working devices. Consider repairability, battery replacement and electronic waste as well.

Decide through a small trial

Try one location before covering an entire home or facility. Record the existing problem, then compare setup time, useful alarms, false alerts, maintenance effort and measured benefits. If the result falls short, simplifying the solution makes more sense than adding more connections.

Editor's note: An automatic system does not necessarily need internet access. An IoT project should demonstrate the additional value of connectivity. “I can see it on my phone” describes a feature; “I can identify a problem early and respond” describes a benefit that can be assessed. Use this distinction when choosing equipment.

Related topics: Is IoT a bubble? | Long-term costs | IoT security