IoT Applications and Industry Use Cases

Introduction

The Internet of Things (IoT) connects physical objects to digital systems so that conditions can be measured, information can be exchanged, and actions can be coordinated. An IoT solution may contain sensors, actuators, communication networks, data platforms, analytics, human interfaces and operational procedures. Its value does not arise from connectivity alone. A successful solution must address a real problem in a particular environment and produce measurable improvement without creating unacceptable safety, privacy, environmental or regulatory risks.

IoT applications differ significantly across sectors. A temperature sensor in a vaccine refrigerator, a soil-moisture sensor in a farm and a vibration sensor on a factory motor may all use similar technical principles, but their design requirements are different. Healthcare demands patient safety and confidentiality; agriculture must tolerate weather and unreliable connectivity; manufacturing requires dependable, low-latency operation; and smart-city systems must serve large populations while respecting public rights.

This chapter examines major IoT application domains and presents a context-based approach to solution design. It also introduces performance measures, governance requirements, a detailed illustrative case, and contemporary developments such as edge computing, digital twins and artificial intelligence.

Learning Objectives

By the end of this chapter, the learner should be able to:

1. Explain how IoT creates value in major industry sectors.
2. Identify suitable sensors, actuators, networks and software for different contexts.
3. Relate IoT design to safety, environmental conditions, privacy and regulation.
4. Select measurable technical, operational, economic and social outcomes.
5. Evaluate limitations, risks and trade-offs in IoT deployments.
6. Propose a practical IoT solution for an industry use case.

1. A Context-Based Model of IoT Application Design

An IoT application can be viewed as a closed operational loop:

1. Sense: Capture a physical condition such as temperature, location, pressure or motion.
2. Communicate: Transfer observations through a suitable network.
3. Process: Store, filter, combine or analyse the data.
4. Decide: Apply rules, models or human judgement.
5. Act: Send a command to an actuator or initiate a work procedure.
6. Learn and improve: Compare results with objectives and refine the system.

Figure: A context-based IoT application loop.

The design begins with the use case rather than with a fashionable technology. Designers should ask: What decision must improve? Who is affected? What is the cost of an incorrect decision? What environmental conditions will the devices face? What happens if communication or power fails? Which organisation owns the data and is responsible for the outcome?

1.1 Important performance measures

IoT projects need baseline measurements before deployment. Common measures include:

• Accuracy: closeness of a measurement to the true or reference value.
• Precision: consistency of repeated measurements.
• Latency: time between an event and a usable response.
• Availability: proportion of required time that a service is operational.
• Reliability: probability that a system performs its required function for a specified period and conditions.
• Energy consumption: electricity or battery energy used by devices and infrastructure.
• Adoption and usability: whether intended users actually use the system correctly.
• Outcome measures: reduced waste, fewer injuries, lower energy use, improved crop yield or reduced waiting time.

A basic availability estimate is:

Here, A is availability, T_u is uptime and T_d is downtime; both times must use the same units and refer to the same observation period. This simple measure assumes that uptime and downtime are clearly recorded and that planned and unplanned outages are treated consistently.

A business case may use return on investment:

Here, B is the measurable benefit over a defined period and C is the total relevant cost over that period. Benefits and costs must be expressed in the same currency and time frame. A positive ROI does not by itself justify deployment if safety, privacy or legal requirements are not met.

2. Smart Homes and Buildings

Smart-home applications include automated lighting, heating and cooling, security, water-leak detection, appliance monitoring and assisted living. Sensors may measure occupancy, temperature, humidity, smoke, carbon monoxide, water flow, door status and electricity use. Actuators may control lights, locks, heating systems, blinds and valves.

The principal value is coordinated control. For example, an occupancy sensor can allow a building-management system to reduce lighting and ventilation in an empty room, while a leak detector can close a water valve and alert the resident. In buildings, occupancy and air-quality data can support demand-controlled ventilation and maintenance planning.

Design must consider different occupants, accessibility and local conditions. A smart lock must provide a safe alternative when batteries fail or connectivity is lost. A smoke alarm must not depend solely on cloud connectivity. Cameras and voice assistants raise privacy concerns because they may collect information about people who have not consented. Home devices should use strong authentication, secure updates, encryption and clear data-retention settings.

Energy savings should be verified against a baseline because weather, occupancy and user behaviour also affect consumption. Automation that frequently switches equipment on and off may reduce comfort or shorten equipment life. Human override and understandable notifications are therefore important design features.

3. Healthcare and Assisted Living

Healthcare IoT, often called the Internet of Medical Things, includes wearable monitors, connected infusion pumps, asset-tracking systems, remote patient monitoring, cold-chain monitoring and hospital environmental controls. Measurements can include heart rate, oxygen saturation, blood pressure, temperature, location and equipment status.

The consequences of error are especially serious. A sensor reading may be affected by motion, poor placement, skin condition, electromagnetic interference or calibration drift. Clinical decisions should not be based on an unvalidated device or an unexplained algorithm. IoT systems should support, rather than obscure, professional judgement.

A healthcare design should address:

• patient identification and correct association of data;
• clinical validation and calibration;
• alarm prioritisation to reduce alarm fatigue;
• confidentiality, access control and audit trails;
• informed consent and appropriate data sharing;
• availability during network or power failure;
• cybersecurity of devices connected to clinical networks;
• applicable medical-device, privacy and health-record regulations.

Remote monitoring can improve access for people with chronic conditions, but it can also widen inequality if patients lack reliable connectivity, digital skills or suitable devices. A responsible project includes training, accessibility provisions and a process for responding when data are missing or abnormal.

4. Agriculture and Environmental Monitoring

IoT in agriculture supports precision irrigation, greenhouse control, livestock monitoring, pest management, weather observation and supply-chain traceability. Soil-moisture, temperature, humidity, leaf-wetness, light and nutrient sensors can inform irrigation or fertilisation. GPS and connected machinery can support field mapping and variable-rate operations.

Agricultural environments are demanding. Devices may be exposed to rain, dust, mud, chemicals, animals, extreme temperatures and mechanical vibration. Enclosures should be selected according to the required ingress protection, and sensors should be mounted where they represent the relevant field rather than a misleading local spot. Battery life and network coverage are important because fields may be remote.

A simple irrigation rule might open a valve when soil moisture falls below a threshold, but a robust system also considers rainfall forecasts, crop growth stage, soil type, water restrictions and equipment status. Automatic action should include limits that prevent overwatering and a manual override for unusual conditions.

Environmental IoT can monitor river levels, air quality, forests, wildlife and waste sites. Such systems support early warning and scientific observation, but measurements require calibration, documented sampling methods and awareness of spatial and temporal bias. A few sensors cannot automatically represent an entire ecosystem or city.

5. Manufacturing and Industrial IoT

Industrial IoT connects production equipment, programmable logic controllers, supervisory systems, enterprise software and maintenance processes. Typical applications include condition monitoring, predictive maintenance, quality inspection, production traceability, worker safety and energy management.

Vibration, temperature, acoustic, current and pressure sensors can reveal changes in machine condition. However, predictive maintenance is not simply the installation of sensors. It requires labelled failure history, suitable sampling, domain knowledge and a maintenance workflow. If a warning produces no practical maintenance action, its operational value is limited.

Manufacturing systems often require deterministic behaviour and high availability. A safety function should not depend on an uncertain internet connection or an opaque cloud model. Industrial networks should be segmented, with controlled gateways between operational technology and enterprise or cloud systems. Read-only data collection may be appropriate before remote control is introduced.

Quality applications may use cameras and machine learning to identify defects. Performance should be evaluated using representative products and operating conditions. A model that performs well on training images may fail when lighting, materials or camera position change. False positives create waste, whereas false negatives may allow unsafe or defective products to proceed.

6. Logistics and Supply Chains

IoT improves visibility across transportation, warehousing and distribution. Common devices include GPS trackers, RFID tags, barcode readers, temperature loggers, shock sensors, door sensors and vehicle telematics. Applications include fleet optimisation, route monitoring, cold-chain assurance, inventory accuracy and proof of delivery.

A cold-chain system should record temperature, time, location and handling events. The important outcome is not merely a dashboard but evidence that goods remained within their required conditions. Alerts need escalation rules: a brief sensor excursion may require review, whereas a prolonged excursion may require quarantine and quality assessment.

Logistics data are often shared among manufacturers, carriers, warehouses, retailers and regulators. Data ownership, access rights and interoperability should be defined contractually. Device replacement, battery failure, inaccurate location and loss of network coverage must be included in operating procedures. Optimising only distance or fuel may create unacceptable delivery delays or service failures; objectives must reflect the whole supply chain.

7. Energy and Utilities

IoT is used in smart metering, distribution automation, renewable-energy management, demand response, building energy control and water networks. Smart meters provide more frequent consumption information, while grid sensors help detect faults and balance supply and demand. Connected solar inverters, batteries and electric-vehicle chargers can coordinate distributed energy resources.

Energy systems are critical infrastructure. A cyberattack or incorrect control signal can affect large numbers of users. Strong identity management, network segmentation, secure firmware, monitoring and recovery plans are essential. Systems should fail safely and retain local control where appropriate.

Energy projects should distinguish between reduced consumption and shifted consumption. A demand-response programme may lower peak demand without reducing total energy use. Evaluation should therefore measure both total energy and the timing of demand, while accounting for weather, occupancy and production levels.

Water utilities use pressure, flow, level and quality sensors to detect leakage, contamination and equipment problems. Sensors must be calibrated and maintained because false alarms can waste resources and missed alarms can threaten public health.

8. Retail and Customer Experience

Retail IoT includes electronic shelf labels, inventory sensors, smart vending, beacons, connected payment systems, robotic warehouses and cold-storage monitoring. RFID can improve stock visibility, while cameras or weight sensors may support shelf availability and loss prevention.

Customer-facing systems must balance convenience with privacy. Location analytics and personalised recommendations should have a clear purpose, appropriate transparency and proportionate data collection. Retailers should avoid treating inferred behaviour as certain fact. Automated pricing must also be checked for accuracy, fairness and compliance with consumer-protection requirements.

Operational outcomes include fewer stock-outs, lower shrinkage, faster replenishment and reduced refrigeration energy. Measurement should compare performance with a baseline and account for seasonal demand. A technically accurate inventory system is not useful if staff cannot interpret alerts or if the replenishment process is not redesigned.

9. Smart Cities and Public Infrastructure

Smart-city systems apply IoT to traffic management, public transport, street lighting, parking, waste collection, air-quality monitoring, flood warning, public safety and municipal services. The scale and public nature of these systems create special responsibilities.

A smart street-lighting system may dim lights when appropriate and increase illumination when movement is detected. It must still meet safety standards, maintain predictable behaviour and provide a maintenance process for failed lamps. Smart parking may reduce search time, but it can also encourage driving unless integrated with wider transport planning.

City data may reveal movement patterns, household conditions or vulnerable locations. Governance should include purpose limitation, data minimisation, retention controls, public communication, procurement transparency and independent oversight. Biometric surveillance and automated decision systems require particularly careful legal and ethical evaluation.

Smart-city projects should define public outcomes, such as reduced emergency response time, improved accessibility, lower energy consumption or reduced congestion. The presence of a dashboard or large number of connected devices is not itself evidence of public benefit.

10. Selecting Technology for Context

Technology selection follows requirements rather than the reverse. Important questions include:

Edge computing processes data near the source. It can reduce latency, bandwidth use and exposure of raw data, but edge devices have limited resources and must still be secured. Cloud platforms provide scalability and centralised analytics, but dependence on connectivity, vendor contracts and data location must be assessed. Hybrid architectures are often practical: urgent control remains local while historical analysis occurs centrally.

11. Safety, Regulation and Responsible Governance

IoT safety includes physical safety, functional safety, cybersecurity and human factors. A system can be technically secure yet unsafe if an alarm is confusing or an actuator behaves unexpectedly. Risk assessment should identify hazards, estimate likelihood and severity, define controls and verify that controls work.

Regulatory requirements vary by country and sector. Designers may need to consider radio-spectrum rules, electrical safety, product liability, occupational safety, medical-device regulation, environmental law, data-protection law and sector-specific standards. Compliance is not achieved by adding a privacy statement after deployment; it must influence architecture, procurement, testing and operations.

Responsible governance includes:

• collecting only data needed for a defined purpose;
• obtaining appropriate consent or another lawful basis;
• protecting data in transit and at rest;
• separating identities from analytical data where feasible;
• documenting model limitations and decision authority;
• providing correction, appeal or human review where decisions affect people;
• planning secure decommissioning and deletion;
• monitoring suppliers and software dependencies.

Environmental responsibility includes energy-efficient protocols, durable hardware, repairability, responsible battery management and electronic-waste recovery. A system that saves energy during operation but becomes rapidly obsolete may have an undesirable lifecycle impact.

12. Illustrative Case: Smart Cold-Chain Monitoring for a Regional Clinic Network

Background

A fictional regional clinic network receives temperature-sensitive vaccines from a central distributor. Staff currently record refrigerator temperatures manually twice each day. Records are sometimes incomplete, and a refrigerator failure may remain unnoticed overnight.

Problem analysis

The network identifies four risks: undetected temperature excursions, incorrect association of records with refrigerators, weak escalation procedures and unreliable connectivity at two rural clinics. The target outcomes are fewer unassessed excursions, faster notification and complete audit records. The project team establishes a baseline from three months of manual records and maintenance logs.

Approach and solution

Each refrigerator receives two calibrated temperature sensors: one primary and one independent cross-check. A local gateway stores readings during network outages. Readings are transmitted at regular intervals, and the gateway generates a local alert when temperature exceeds the approved operating range for a defined period. A cloud service provides authenticated access, trend graphs and an audit trail. Alerts are sent to the responsible nurse, the maintenance team and a manager according to an escalation schedule.

The system does not automatically declare vaccines unusable. Instead, it records the excursion and directs staff to follow the clinical cold-chain procedure. This preserves professional decision-making and avoids unsafe automation. Sensors are labelled to prevent data from being assigned to the wrong refrigerator. Calibration checks are scheduled, batteries are replaced proactively and staff practise the outage procedure.

Evaluation

The team measures alert delivery time, percentage of complete records, number of excursions discovered only through manual inspection, false-alert rate and avoided product loss. Availability is calculated using consistent uptime and downtime records. Costs include hardware, installation, connectivity, calibration, training and support. Benefits include avoided spoilage and staff time, but the evaluation also considers patient safety and regulatory evidence.

Outcome and learning points

After a pilot, the network finds that the greatest benefit comes not from the dashboard but from local buffering, clear escalation and defined human procedures. The pilot also reveals that one sensor was poorly positioned near a cooling outlet, demonstrating why installation and validation matter. The case shows that an IoT solution is a socio-technical system: devices, software, people, procedures and governance must work together.

13. Contemporary Developments and Limitations

Artificial intelligence can classify anomalies, forecast demand and support predictive maintenance. Its use requires representative data, monitoring for drift, explainable outputs where appropriate and human responsibility for consequential decisions. AI cannot compensate for poor sensors or missing operational processes.

Digital twins combine physical assets with data and models to support simulation, diagnosis and optimisation. Their usefulness depends on model validity and data quality. Digital twins should not be treated as exact copies of reality; they are representations with defined purposes and limitations.

Other developments include energy harvesting, private cellular networks, interoperable data spaces, autonomous robots and increasingly capable edge devices. These developments may reduce cost or improve responsiveness, but they also increase software complexity, attack surfaces and dependence on vendors.

Common limitations across IoT projects include inaccurate sensing, interoperability problems, cybersecurity vulnerabilities, poor connectivity, battery constraints, unclear ownership, vendor lock-in, insufficient skills and uncertain return on investment. Pilot projects should therefore test the complete operational workflow, not just whether a sensor can transmit data.

Best-Practice Design Checklist

1. Define the operational problem and measurable outcome.
2. Establish a baseline before installing devices.
3. Select sensors according to accuracy, placement and environmental conditions.
4. Design for power loss, network loss, device failure and incorrect data.
5. Use secure identity, least-privilege access and signed updates.
6. Keep safety-critical decisions local and fail-safe where necessary.
7. Provide human override, training and clear escalation procedures.
8. Plan calibration, maintenance, replacement and end-of-life disposal.
9. Document data purpose, retention, ownership and sharing.
10. Evaluate technical, economic, social and environmental outcomes.
11. Test interoperability and avoid unnecessary dependence on one supplier.
12. Review the system after deployment and monitor for changing conditions.

Chapter Summary

IoT applications connect sensing, communication, processing, decision-making and action to improve real-world operations. Their design must be adapted to context: smart homes emphasise convenience and privacy; healthcare emphasises clinical safety and confidentiality; agriculture must tolerate environmental variability; manufacturing requires reliable and secure operational control; logistics depends on traceability; energy and utilities require critical-infrastructure protection; retail combines inventory and customer experience; and smart cities must demonstrate public value while protecting citizens’ rights.

Effective evaluation uses baselines and measurable outcomes such as availability, latency, energy use, accuracy, waste reduction, safety improvement and service quality. Technology choices must account for range, power, data volume, environment, security, integration and lifecycle. IoT is a socio-technical system, so people, procedures, governance and maintenance are as important as sensors and software. Responsible solutions incorporate safety engineering, privacy, cybersecurity, regulation, accessibility and environmental stewardship from the beginning.

Key Terms

Actuator: A device that produces a physical action in response to a command.

Availability: The proportion of required time during which a service is operational.

Cold chain: Controlled-temperature storage and transportation for sensitive products.

Digital twin: A data-connected representation of a physical asset, process or system.

Edge computing: Processing data near the device or physical source.

Internet of Medical Things: Connected devices and systems used in healthcare.

Interoperability: The ability of systems to exchange and use information correctly.

Latency: The delay between an event and the resulting observation or response.

Predictive maintenance: Maintenance planned using evidence about likely equipment failure.

Precision agriculture: Data-supported management of crops, soil and resources at fine spatial or temporal scales.

Sensor: A device that detects and measures a physical, chemical or environmental condition.

Smart city: An urban environment using digital technologies to improve services and resource management.

Telemetry: Automated measurement and transmission of data from a remote location.

Threshold: A specified value used to trigger an alert or action.

Uptime: The period during which a system is functioning and available.

Operational technology: Hardware and software that monitors or controls physical processes.

Data minimisation: Collecting and retaining no more personal data than is necessary.

False positive: An alert indicating a condition that is not actually present.

Review Questions

Short Answer Questions

1. What are the main stages of an IoT operational loop?
2. Why is a baseline important when evaluating an IoT project?
3. Identify two environmental challenges faced by agricultural IoT devices.
4. Why should a healthcare IoT alarm not automatically determine clinical action?
5. State two security measures appropriate for industrial IoT.

Long Answer Questions

1. Explain how IoT creates value in manufacturing and discuss the limitations of predictive maintenance.
2. Compare the design requirements of a smart home and a smart city.
3. Discuss the role of privacy, consent and data minimisation in retail IoT.
4. Explain how IoT can support energy management while introducing cybersecurity risks.
5. Describe a complete evaluation plan for a logistics cold-chain monitoring system.

Analytical / Application Questions

1. A rural clinic has unreliable connectivity and temperature-sensitive medicines. Design an IoT architecture that continues to protect the medicines during a network outage. Justify your choices.
2. A factory wants to use an AI camera to identify product defects. Analyse the technical, operational, safety and governance issues that should be tested before deployment.
3. A city proposes connected cameras and mobile-phone data to reduce congestion. Evaluate the proposal using public benefit, privacy, equity, cybersecurity and measurable-outcome criteria.

Multiple Choice Questions with Answers

Question 1

Which sequence best represents the IoT operational loop?

A. Sense, communicate, process, decide and act

B. Purchase, advertise, sell, invoice and archive

C. Encrypt, print, package, ship and recycle

D. Design, manufacture, export, insure and audit

Correct Answer: A. Sense, communicate, process, decide and act

Question 2

In the availability formula A = T_u ÷ (T_u + T_d), what does T_d represent?

A. Total data volume

B. Downtime

C. Device temperature

D. Detection threshold

Correct Answer: B. Downtime

Question 3

Which feature is especially important for a healthcare IoT system?

A. Unrestricted public access to patient data

B. Clinical validation and audit trails

C. Automatic deletion of all abnormal readings

D. Dependence on cloud connectivity for every safety function

Correct Answer: B. Clinical validation and audit trails

Question 4

Why is local buffering useful in agricultural or rural IoT deployments?

A. It eliminates the need for sensors

B. It allows data retention during network outages

C. It guarantees perfect measurement accuracy

D. It prevents all battery depletion

Correct Answer: B. It allows data retention during network outages

Question 5

Which application is most directly associated with industrial IoT?

A. Predictive maintenance using machine vibration data

B. Personalised online advertising only

C. Manual filing of paper invoices

D. Unconnected household decoration

Correct Answer: A. Predictive maintenance using machine vibration data

Question 6

A cold-chain monitoring system should primarily provide evidence about which combination?

A. Temperature, time, location and handling events

B. Employee salaries, tax records and advertising reach

C. Screen brightness, speaker volume and font size

D. Weather forecasts without product measurements

Correct Answer: A. Temperature, time, location and handling events

Question 7

What is a major reason for using edge computing?

A. To increase latency deliberately

B. To process data near its source and reduce dependence on connectivity

C. To remove the need for cybersecurity

D. To guarantee unlimited storage on a sensor

Correct Answer: B. To process data near its source and reduce dependence on connectivity

Question 8

Which practice best supports responsible IoT data governance?

A. Collecting all available data indefinitely

B. Using data minimisation and defined retention periods

C. Sharing data with every third party by default

D. Removing access controls to improve convenience

Correct Answer: B. Using data minimisation and defined retention periods

Question 9

If benefits are 30,000 currency units and costs are 20,000 currency units, what is the ROI using ROI = (B − C) ÷ C × 100%?

A. 10%

B. 33.3%

C. 50%

D. 66.7%

Correct Answer: C. 50%

Question 10

Why should a smart-city project be evaluated against public outcomes?

A. The number of connected devices alone proves success

B. Dashboards are always more important than services

C. Technology must demonstrate measurable public benefit and acceptable risks

D. Public projects do not require privacy assessment

Correct Answer: C. Technology must demonstrate measurable public benefit and acceptable risks