Chapters

21 IoT Requirements: Definition and Value Flow

applications
iot
requirements
Listen
Uses your device's voice. Tap ▶ beside any paragraph to hear just that one.
  • Podcast audio coming soon
  • Character narration audio coming soon
Lecture
Video lecture coming soon. The slides are the lecture for now.
Ask AI
Pick a prompt. We copy it for you and open an AI service; paste it there. Nothing is sent to IoTClass.

21.1 From a Physical Thing to a Useful Decision

An Internet of Things (IoT) product joins a physical thing, local computation, and a direct or indirect internet path. That combination lets everyday objects collect, exchange, and act on data. The useful question is what the connection changes about the object’s job: comfort in a home, access at a door, or protection of inventory.

Follow the smart thermostat. Its sensor reads 65 °F while you have set a target of 72 °F. The system must carry that reading to decision logic, turn on the heater, and tell you what happened. Adding a radio alone does not explain how the home becomes comfortable; we need to follow the whole flow and identify the parts responsible.

This is part 2 of 2, following IoT Requirements: Classification and Connectivity. The applications module index places these requirements among the wider application cases. Here, you will test whether a product qualifies as IoT and compare connectivity through total cost of ownership. We will first connect the definition to the thermostat’s value flow, then classify other products and compare the warehouse’s competing designs. We will make the internet claim and business outcome reviewable through an ingredient test, a layer model, and cost analysis.

KEY CONCEPTS

  • Three ingredients

    A physical thing, local computation, and internet reach form the baseline.

  • Gateway distinction

    Local wireless needs a route through a gateway to reach remote services.

  • Five-layer architecture

    Separate devices, edge logic, connectivity, cloud functions, and applications.

  • Characteristic prioritization

    Weight the eleven design qualities differently for each domain.

  • Requirements-driven connectivity

    Range, power, reporting rate, and environment guide the choice.

  • Trade-off mapping

    Make compromises explicit rather than optimizing every quality equally.

21.2 Learning Objectives

  • Test what is internet of things (iot) with a concrete scenario and pass criteria.
  • Validate iot connectivity tco with a concrete scenario and pass criteria.

21.3 Define the Complete Solution

IoT connects objects ranging from household appliances to industrial machinery with other devices, users, and services. Those connections bridge physical work and digital workflows.

Researchers and institutions define IoT in slightly different ways, with connectivity and data sharing as the common idea. A useful definition makes its scope clear, so the team can apply it consistently.

Figure 1 shows why definitions differ: each one starts from a different corner of the same picture.

IoT ecosystem framework shows Business, Market, Tech and User Experience dimensions converging around a dark rectangular CORE box. The box is labeled Integration point and Complete IoT solutions; adjacent Relationships text also converges. Each surrounding dimension lists example concerns such as revenue models, sectors, cloud services and interfaces.
This IoT ecosystem framework brings business, market, technology, and user experience together at an integration core. The framework is adapted from the Edinburgh Design Course.

The four outer blocks of Figure 1 are the places a definition can begin. Read the technology block and IoT looks like connectivity, cloud services and device enablement. Read the business block and it looks like revenue models, licensing and delivery channels. The market block frames it by sector, and the user-experience block by context awareness, device type and how a person interacts. Arrows from all four meet at the core, where relationships tie them into one complete solution. That meeting point is the chapter’s answer to the definition question. None of the four corners is wrong on its own. A definition is only incomplete when it stops at one of them.

21.4 Follow the Thermostat Value Flow

The value flow has four steps: sense, connect, process, and act.

Figure 2 follows one reading through the whole loop, from a measurement to something that changes.

Four-step IoT value loop showing Sense, Connect, Process, and Act with a feedback loop returning the system to sensing
The IoT value loop links sensing, connection, processing, and action.

Follow the worked example along the foot of Figure 2. A sensor produces a reading of 18.3 degrees. The connect step puts that state on the network. The process step compares it against a rule and concludes that heat will be needed soon. The act step opens a valve and alerts a person. Two details carry the definition. The third step is where judgement happens, so a device that only reports does not perform this whole control loop, though reporting can still be a useful IoT function. The return arrow at the bottom says the action changes what the sensor measures next, which is why this is drawn as a cycle rather than a line.

Real Example - Smart Thermostat:

  1. Sense: Temperature sensor reads 65F (you set target to 72F)
  2. Connect: Thermostat sends data to cloud via Wi-Fi
  3. Process: Cloud compares 65F vs 72F, decides “too cold”
  4. Act: Cloud sends command to turn on heater + alerts your phone

This cycle repeats continuously, keeping your home comfortable automatically. The process step can use cloud or edge logic; in this worked example it runs in the cloud.

21.5 Compare the Jobs of Connected Objects

Inspect Figure 3 to compare the physical evidence, computation, and digital workflow added to familiar objects.

Collage displaying six everyday objects that can be transformed into IoT devices: an electrical plug, microwave oven, washing machine, coffee maker, commercial truck, and recycling bin with sensors
Everyday objects can gain sensing, computation, and connectivity to support their existing jobs.

Read Figure 3 across domains and look for the same pattern. A smart plug adds remote switching, while a washing machine combines energy monitoring with a cycle-complete notice. A coffee machine uses schedule and control; a truck senses location, fuel efficiency, and maintenance state; a recycling bin reports fill level so routes can change. The connected capability differs because the original jobs differ. Each object needs a physical signal, local or remote computation, and a workflow that can use the result; connection without that outcome is only added cost and risk.

Inspect Figure 4 to see how sensing, computation, and connection change the outcome of a familiar object.

Regular thermostats and locks become smart products with sensing and connectivity. Smart thermostat features support adaptive comfort; smart lock features support auditable, remote access.
Thermostats and locks gain connected functions that support comfort and remote access.

Read Figure 4 from the ordinary thermostat into its smart version. A 65 °F reading and 72 °F target leave a 72 − 65 = 7 °F gap; computation interprets that state, connection can supply wider context, and the system acts by heating and notifying the user. The lock follows the same pattern but seeks auditable remote access rather than comfort. In both cases, the Internet link is only the middle step. The redesign earns its place when sensed evidence and a controlled action improve the object’s original job.

The microwave adds another example: a connected version can be programmed through a smartphone. A coffee machine can brew automatically at specific times, but a local schedule alone does not establish internet reach. In every case, start with the physical job, add computation, and identify the route into the wider workflow.

Across these fields, the physical job sets the purpose of the connected capability. A scheduled coffee maker and a remotely scheduled one may look alike, but the communication path changes what the user can do.

Check knowledge

IoT fundamentals — Classify the timer-only coffee maker, locate the decision step, and explain the smart bin.

Check knowledge

21.6 Locate the Work Across Five Layers

The value flow explains what happens. The layer model now assigns that work to devices and services.

Figure 5 answers where each part of an IoT system does its work, and which way information travels between those parts.

Five-layer IoT architecture stack showing Physical, Edge, Connectivity, Cloud, and Application layers with data moving upward and commands returning downward
The five-layer teaching model follows data from physical devices to user-facing applications.

Read Figure 5 from the bottom, because that is the direction a reading travels. The physical layer is the only one touching the world: sensors measure it, actuators change it. The edge, the processing close to the physical device, sits directly above and does the thinning, filtering readings and running the rules that must not wait for a network. Connectivity carries what survives, and the cloud adds storage, history, and analysis that a small device cannot hold. The top layer is where a person finally sees something useful. The line at the foot matters as much as the stack: telemetry moves up and commands move down, so a break can interrupt the end-to-end exchange even while local edge rules continue.

Complete IoT Ecosystem - Data Flow:

  • Physical layer: Sensors, actuators, and smart objects sense the environment and act on commands. Example: a thermostat sensor reads 65F.
  • Edge layer: Gateways and local processors filter data or translate protocols. Example: a gateway converts Zigbee traffic to Wi-Fi.
  • Connectivity layer: Wi-Fi, Ethernet, cellular, low-power wide-area network (LPWAN), Bluetooth, and Zigbee move data between systems. Example: Wi-Fi sends a reading to the cloud.
  • Cloud layer: Storage, analytics, ML, business logic, and APIs turn device data into decisions. Example: an ML model learns a heating schedule.
  • Application layer: Mobile apps, dashboards, automation rules, alerts, and reports deliver user value. Example: an app shows energy savings.

Data Flow: Physical -> Edge -> Network -> Cloud -> Application Command Flow: Application -> Cloud -> Network -> Edge -> Physical (actuators respond)

Figure 6 sorts the radios by how far they reach, then makes the point that reach and internet access are not the same thing.

Comprehensive IoT connectivity landscape diagram showing the full spectrum of communication technologies organized by network range. PAN includes Bluetooth, UWB, Z-Wave, Zigbee. LAN covers Wi-Fi connectivity. WAN includes cellular technologies from 2G/GSM to LTE Advanced.
IoT connectivity technologies span personal-area, local-area, and wide-area networks.

The three bands in Figure 6 widen from a personal-area group, through Wi-Fi on a local network, to cellular links covering a district. That ordering is by range, and it is the first filter a designer applies. The strip below is the part worth pausing on. A Zigbee sensor is wireless but cannot reach the internet on its own, so the figure sends its traffic through a gateway, an intermediary connecting the local device network to another network, that converts it to Wi-Fi and onward to the cloud. This is the same gateway named in the layer list above. The closing line adds the rest of the decision: power budget, reporting rate, and the physical setting all constrain the choice too.

21.7 Test the Ingredients and the Remote-Access Claim

To qualify as part of the Internet of Things (IoT), a physical object must meet three minimum requirements: it must be a physical thing, be enhanced with computational intelligence, and be equipped with internet communication capability. These components ensure the object can perform smart functions and communicate effectively within an IoT ecosystem.

Physical thing: The starting point for any IoT device is a physical object such as furniture, appliances, vehicles, or industrial machinery. These objects are made “smart” by adding computational and connectivity features.

Computation: Objects must be enhanced with computational capabilities to process data, execute tasks, and enable intelligent behavior. This often involves embedding microprocessors, sensors, and actuators into the object.

Internet Connectivity: Connectivity is the defining feature of IoT devices. It enables them to communicate with other devices, users, or cloud systems via direct or indirect internet communication channels.

Use this decision tree to classify any device you encounter:

Figure 7 turns the three-ingredient definition into four questions you can ask about any product in front of you.

Decision tree classifying a product as software service, ordinary object, embedded device, connected product, or IoT device based on whether it is physical, has local computation, can communicate, and can reach the internet directly or through a gateway
The decision tree separates software, ordinary objects, embedded devices, connected products, and IoT devices.

Work down Figure 7 one question at a time and note what happens at each no. Without a physical thing you have software. With a thing but no local computation you have an ordinary object, a plain lamp. Add computation but no outward link and you have an embedded device, the microwave with a timer. The fourth question is the one that catches the smart lock: it talks, but only to a phone beside it, so the figure calls it connected rather than IoT. Only a product that answers yes four times lands in the IoT box. Each no is a real category with a real example.

Try it

Change internet connectivity and check how the three ingredients affect the product classification.

Test the ingredients →

Figure 8 gives the shortest form of the test: three ingredients, and what you are left with when one is missing.

Three-card diagram showing the three ingredients for IoT: physical thing, computation, and internet reach, combined into an IoT system
The Three Ingredients Test classifies an IoT system by the combined presence of a physical thing, local computation, and direct or gateway-mediated internet reach.

The plus signs in Figure 8 mean all three ingredients must be present. The first card is a physical thing that can be sensed, monitored or controlled, such as a pump or a thermostat. The second is a controller that turns inputs into rules or actions, with parts like an ESP32 given as examples. The third is a path to remote services, either direct or through a gateway. The band underneath does the useful work. Remove any one ingredient and the figure names what is left: a regular object, an embedded device, or a locally connected product.

The test concerns the whole deployed system: a local radio can satisfy internet reach through a gateway, but local communication by itself cannot.

The smart lock makes this classification a business decision as well as a technical one.

Scenario: Your company is launching a smart lock product with annual revenue projections of $50M. The engineering team proposes a design with a physical deadbolt mechanism, a microcontroller for keypad control and motor operation, and Bluetooth connectivity to communicate with smartphones within 30 feet. Marketing wants to call it an “IoT smart lock” and price it at $299 (premium over $150 traditional locks).

The proposed promise of “control from anywhere” therefore needs evidence of a remote path. A competitor with Wi-Fi can offer that path; the Bluetooth-only design described here has no such route. Product positioning must match that boundary.

Current Design Status:

  • Thing: Physical deadbolt mechanism
  • Computation: Microcontroller for control logic
  • Internet: Only Bluetooth (local wireless, NOT internet)

Classification: This is a Connected Product, not a full IoT device. The example treats Bluetooth as a proximity link with a 10–100 feet range; actual coverage depends on the deployment. Internet reach enables remote access. A phone could supply gateway reach, but that is not part of this proposed design.

Real Example - August Smart Lock Evolution:

  • August Smart Lock (2017): Bluetooth local control; remote access needs a Connect bridge ($149 US launch price for the lock).
  • August Smart Lock Pro + Connect (2017): Bundled bridge provides Wi-Fi remote access ($279 US launch price).
  • August Wi-Fi Smart Lock (released 2020): Built-in Wi-Fi needs no bridge ($199.99 US list price, checked 7 October 2026).

Business Impact:

  • Connected: Unlock when standing at door, limited value proposition
  • IoT: Unlock remotely for a delivery, monitor access logs, and receive cloud alerts; business value depends on adoption, pricing, and support costs.

21.8 Choose Connectivity for the Warehouse Job

Once the internet path is established, the next problem is choosing a connection that suits the operating conditions. LoRaWAN illustrates the gateway pattern: a soil-moisture sensor and microcontroller can control an irrigation valve locally, while a gateway carries readings to cloud scheduling based on weather forecasts. The radio supports small packets over kilometers with low power and potentially years of battery operation. With no external service path from the gateway, local sensing and control alone do not establish internet reach.

Scenario: Your logistics company wants to monitor temperature and humidity in 50 warehouses (200,000+ sq ft each) across the country to protect sensitive pharmaceutical inventory worth $2.5B annually. Food and Drug Administration (FDA) compliance requires documented temperature control. The IT team presents two competing approaches:

Approach A (Wi-Fi): $50 sensors, $10/month/warehouse, 30-second updates, requires Wi-Fi infrastructure Approach B (LoRaWAN): $80 sensors + $200 gateway, $5/month/warehouse, 10-minute updates, 10-year battery

The $30 difference between sensor prices is only one part of a five-year decision. Temperature drift, blocked signals, and reliability across a 200,000 sq ft warehouse determine whether the readings can protect the inventory. Technology selection follows those requirements rather than the newest or fastest radio.

Warehouse Environment Challenges:

  • Large buildings (200,000+ sq ft) - Wi-Fi coverage gaps common
  • Metal racking - blocks Wi-Fi signals, creates dead zones
  • Power outlets scarce — sensors need battery power
  • Temperature changes slowly in this example — assess whether 10-minute updates meet the inventory protection requirement before rejecting 30-second updates

5-Year Total Cost of Ownership:

  • Wi-Fi: $10K sensors, $15K installation for Wi-Fi and power, $500/month operations ($30K over five years), for a five-year total of $55,000.
  • LoRaWAN: $16K sensors, $3K simple gateway placement, $250/month operations ($15K over five years), for a five-year total of $34,000 and roughly 38% savings.

Treat these as stated deployment estimates. The $10K Wi-Fi and $16K LoRaWAN sensor budgets imply 200 sensors at the quoted $50 and $80 prices. The operations budgets apply the respective $10 and $5 monthly costs to all 50 warehouses. The installation totals, $15K and $3K, are separate assumptions that need review against actual coverage and gateway placement.

The total cost of ownership (TCO) calculator lets you vary sensor count, deployment duration, sensor prices, and monthly operations costs. Its model adds hardware, installation, and operations. It assumes $30 installation per Wi-Fi sensor and one $200 LoRaWAN gateway per 100 sensors, while monthly operations are entered per warehouse. Those inputs describe a different installation model from the fleet totals above. Use a consistent warehouse or fleet scope before interpreting the savings; the model is a comparison aid, not proof that either design meets the monitoring requirement.

Try it

IoT connectivity TCO — Adjust sensor count, years, prices, and operations costs; keep the comparison scope consistent.

Compare costs

Check knowledge

Classification and connectivity decisions — Review the smart lock, irrigation gateway, and warehouse requirements.

Check knowledge

Summary

The thermostat connects a physical reading to a useful action through sense, connect, process, and act. The five-layer model locates each responsibility, from sensors and local logic to cloud analysis and the application a person uses. The ingredient test then separates ordinary objects, embedded devices, locally connected products, and IoT systems.

The smart lock shows why internet reach must support the promised use. The warehouse shows why range, battery needs, reporting rate, installation, and operating costs must be considered together. The eleven qualities of strong IoT systems are design goals to prioritize by domain, rather than qualities to maximize equally.

Start with the physical job, establish the computation and internet path, and trace the evidence to a useful outcome. Choose connectivity by requirements and a consistent cost model.

Continue with IoT Requirements: TCO and Design Trade-offs to carry these choices into a broader design comparison.

Hi, I’m Ada. What do you need?

Find help

Let’s find what you need

Find a lesson or return to your module guide.

Give feedback

Help improve this chapter

Tell us what helped or what needs fixing.

Tips

Try a small next step

A few ways to get more from this chapter.

Ask AI

Continue the conversation

Take the conversation further with your preferred assistant.

AI help is available in supported modules when enabled in Settings.

No live person answers on independent study. Feedback does not promise a personal reply.

For welfare or safety concerns, follow your school’s procedures outside IoTClass.