Start with an ordinary object whose condition matters to someone: a room getting too warm, a shipment arriving late, a pump vibrating differently, or a patient missing a dose. The IoT story begins when sensing, computation, and connectivity make that condition visible enough for a person, service, or controller to act.
Chapter Roadmap
First, build the closed-loop definition: a thing senses state, computation interprets it, connectivity carries it, and action changes what happens next.
Then, test familiar devices with the Three Ingredients Test so embedded, connected, and IoT examples stay distinct.
Next, connect the business case to payback, efficiency, and the Five Verbs categories rather than treating connectivity as value by itself.
Finally, use the quizzes, pitfalls, and decision examples to classify new IoT proposals without overclaiming what the system can prove.
Checkpoint callouts pause the overview flow; deep-dive sections and interactives hold calculators, audits, and verification detail you can collapse during a first pass.
2.2 IoT for Business Leaders
What IoT Delivers: The Internet of Things transforms ordinary products into data-generating assets that enable new revenue streams, operational efficiencies, and customer insights. With 18-21 billion devices deployed globally and a $1.5 trillion market (2025), IoT represents one of the most significant technology investments of the decade.
Investment Framework:
Metric
Range
Key Consideration
Global Market Size
$1.5 trillion (2025)
Growing at 14.5% CAGR through 2030
Typical ROI
6-36 months
Depends on use case complexity
Efficiency Gains
25-50%
Manufacturing, agriculture, logistics lead
Device Growth
18B to 40B+
2025 to 2034 projection
The Five Verbs Framework (Market Allocation):
Category
2030 Projection
Growth Driver
SUSTAIN (Energy, Environment)
$1.1T
Climate regulations, ESG mandates
MOVE (Transportation, Logistics)
$950B
Autonomous vehicles, last-mile delivery
MAKE (Manufacturing)
$870B
Labor shortages, quality demands
HEAL (Healthcare)
$650B
Aging populations, remote care
FEED (Agriculture)
$420B
Water scarcity, food security
When to Invest in IoT:
Operations generate data that could drive better decisions
Manual monitoring/inspection is costly or error-prone
Key Risk Factors: Security vulnerabilities (budget 15-20% for security), platform lock-in, integration complexity with legacy systems, and skills gap requiring training investment.
2.3 Learning Objectives
By the end of this chapter, you will be able to:
Define IoT and distinguish IoT devices from traditional embedded systems using the Three Ingredients Test (Thing + Computation + Connectivity)
Apply the Three Ingredients Test to determine whether any given device qualifies as an IoT device, citing which ingredient is present or missing
Classify IoT applications into the Five Verbs Framework categories (SUSTAIN, MOVE, HEAL, FEED, MAKE) and explain why solutions often span multiple verbs
Evaluate IoT market segments by comparing growth rates, market sizes, and leading companies across the Five Verbs categories
Calculate basic IoT ROI using payback period analysis for consumer and industrial IoT deployments
Identify cross-verb applications and explain how IoT solutions create cascading benefits across multiple human activity domains
This is a true entry-level chapter. You can read it without any prior IoT background, though basic familiarity with everyday networked devices (such as smartphones, Wi-Fi, and laptops) will make the examples easier to follow.
2.6 IoT Delivers a Closed Loop
IoT is useful when a physical situation can be sensed, interpreted, communicated, and acted on. The Three Ingredients Test is the starting point: there must be a physical thing, local computation, and a path to exchange data beyond the device. The value comes from the loop those ingredients create, not from connectivity alone. A connected device that only reports raw readings is less useful than a system that turns readings into a decision, response, or service improvement.
A smart thermostat illustrates the loop. A temperature sensor measures the room, a microcontroller runs control logic, Wi-Fi carries status and commands, a cloud or app interface changes schedules, and a relay or HVAC controller acts on the result. If any part is missing, the product may still be useful, but it is no longer the same IoT pattern. A programmable thermostat without networking is embedded control; a phone app without a physical device is software; a sensor tag with no computation is instrumentation rather than a complete IoT system.
Figure 2.1: A smart thermostat is valuable because sensing, computation, actuation, and feedback form a closed loop; connectivity then lets that loop publish state, accept remote changes, and improve the service over time.
This is why introductory IoT examples should always name the loop, not just the gadget. A warehouse pallet tracker senses location and shock, sends events through BLE gateways or LTE-M, and changes a logistics workflow when a shipment is delayed or mishandled. A water-level monitor senses a river or tank, sends data through LoRaWAN or cellular, and changes release schedules, pump behavior, or maintenance visits. The pattern is consistent even when the hardware, network, and business purpose differ.
Sense: Measure a physical condition such as temperature, motion, vibration, flow, location, or energy use.
Decide: Process the reading locally, at a gateway, at the edge, or in a cloud service.
Act: Notify a person, change an actuator, update a dashboard, tune a schedule, or trigger a workflow.
A good first-pass definition is therefore: IoT connects a physical system to computation and communication so that the system can be observed, controlled, improved, or monetized over time. The definition is broad enough to cover homes, factories, hospitals, farms, cities, and transport, but narrow enough to exclude ordinary websites, passive labels, and disconnected embedded controllers.
2.7 Classify Before Business Case
Before estimating ROI, classify the device path precisely. A BLE fitness tracker that syncs through a phone is still IoT if the phone acts as the gateway. A factory motor with a vibration sensor may use Modbus or IO-Link locally, then an edge gateway may publish MQTT Sparkplug or OPC UA data to maintenance systems. A soil probe may use LoRaWAN or NB-IoT because range and battery life dominate the design. These choices determine battery budget, latency, installation cost, support skill, and whether the system can operate when the wide-area connection is unavailable.
This classification prevents weak proposals. If a product only adds a dashboard to manual data entry, it is not proving the same thing as an instrumented asset. If a sensor sends data but nobody owns the alarm response, the technology does not yet deliver an operational outcome. The practitioner should ask what decision changes because the device is connected: faster dispatch, less downtime, safer care, lower energy use, better replenishment, or a new paid service.
Use the same three ingredients as a requirements checklist. For the physical thing, record the asset, environment, power source, mounting constraints, and expected life. For computation, record what runs on the microcontroller, gateway, PLC, phone, edge computer, or cloud service. For connectivity, record the protocol, payload, data rate, coverage, ownership of the network, and fallback behavior. This keeps the introductory definition tied to design decisions that matter later in the course.
Name the thing. Identify the physical asset, environment, installation point, and user or operator.
Name the compute boundary. Identify whether logic runs on a microcontroller, phone gateway, edge computer, PLC, or cloud service.
Name the connectivity path. Identify Wi-Fi, BLE, Thread, Zigbee, LoRaWAN, LTE-M, NB-IoT, Ethernet, or a gateway protocol, plus what data crosses it.
For example, a cold-room monitor can be a simple alarm, an IoT compliance system, or part of a predictive maintenance service. The difference is not the presence of a temperature sensor alone. It is whether the system timestamps readings, proves calibration, alerts the responsible person, records acknowledgement, preserves local alarm behavior, and produces audit evidence for a food-safety or medicines-storage process.
2.8 Connectivity Changes Responsibility
Adding connectivity changes who owns state, security, updates, and failure recovery. A traditional embedded controller can often fail locally. An IoT product may also fail through expired credentials, weak radio coverage, broker outages, cloud rules, app permissions, or stale cached state. The system now has to define which behavior remains local, which behavior depends on the network, and which person or service is accountable when the loop breaks.
The underlying architecture usually splits responsibilities across device firmware, radio stack, gateway, message broker, storage, analytics, application UI, identity service, and update service. Protocol choices such as MQTT, CoAP, HTTP, OPC UA, or Modbus-over-gateway do not just move bytes; they shape reliability, observability, data meaning, and support work. A system using AWS IoT Core, Azure IoT Hub, Eclipse Mosquitto, EMQX, Node-RED, Home Assistant, or an industrial SCADA gateway still has to solve the same basic problems: identity, message freshness, command authorization, and recovery.
Under the hood, the loop needs timestamps and ownership. The device should timestamp the measurement when possible; the gateway or broker should record when it received the message; the application should know whether it is showing fresh state or stale state. Commands should carry a target device, allowed actor, desired state, expiry time, and acknowledgement path. Without those details, a dashboard can show a number without knowing whether it is safe to act on it.
Identity: Decide how the device is provisioned, authenticated, transferred, and revoked.
Freshness: Track when a reading was measured, when it was received, and whether it is safe to act on.
Recovery: Preserve useful local behavior when the app, gateway, broker, or cloud path is unavailable.
The beginner lesson is that IoT is a system boundary, not a single board or app. Firmware, connectivity, backend services, analytics, user experience, security operations, and maintenance all participate in the same value loop. Later chapters separate those layers, but this first chapter should make the dependency visible from the start.
Checkpoint: Closed-Loop Boundary
You now know why the Three Ingredients Test requires a physical thing, computation, and a path to exchange data beyond the device.
You can explain why a smart thermostat is not only a connected gadget: it senses, decides, acts, publishes state, and accepts remote changes.
You can separate local responsibility from network responsibility when identity, freshness, recovery, and command ownership enter the design.
2.9 Sammy Finds IoT
Have you ever talked to a smart speaker or seen lights turn on by themselves? The Sensor Squad is here to explain how it all works!
Meet the Squad:
Sammy the Temperature Sensor – Feels when things are hot or cold
Lila the Light Sensor – Sees when it is bright or dark
Max the Motion Sensor – Notices when people and things move around
Bella the Pressure Sensor – Feels pushes, squeezes, and even the weather
2.9.1 What Makes Things “Smart”?
Regular things just sit there. But SMART things can:
Feel what is happening (too hot? too dark?)
Think about what to do
Talk to other things and to you!
Act to make things better
Squad Member
Super Power
What They Help
Sammy
Feels hot and cold
Keeps your room at the perfect temperature
Lila
Sees light and dark
Turns lights on and off automatically
Max
Notices movement
Knows when you enter a room
Bella
Feels pushing and weather
Tells you if it will rain tomorrow
2.9.2 A Day With the Sensor Squad
Morning: > You wake up. Lila notices it is bright outside and tells the blinds to open slowly. Sammy checks if your room is warm enough!
Going to School: > Your smart backpack (with a tracker inside) tells your parents’ phone you arrived safely at school. Max noticed you stopped moving – you must be at your desk!
Coming Home: > Max notices you walking up to the door. The smart lock recognizes you and unlocks automatically. Welcome home!
Bedtime: > You say “Goodnight!” to your smart speaker. It turns off the lights (Lila’s idea), plays soft music, and Sammy sets the temperature just right for sleeping. Bella checks the weather for tomorrow so you know what to wear!
2.9.3 What is “IoT”?
Internet of Things = Smart things talking to each other through the internet!
“Things” can be ANYTHING:
Light bulbs that change colors
Refrigerators that know when you’re out of milk
Watches that count your steps
Pet feeders that give treats when you’re away
Doorbells that show you who’s there
2.9.4 Why IoT is Cool
Saves time: Lights turn off by themselves when you leave
Keeps you safe: Smoke detectors call for help automatically
Helps everyone: Farmers know exactly when plants need water
Fun to use: Control your room with your voice!
2.9.5 Key Words for Kids
Word
What It Means
IoT
Internet of Things – smart stuff connected together
Smart
A thing that can feel, think, and talk to other things
Sensor
The part that feels (like eyes and ears for devices)
Internet
The invisible web that connects everything
App
A program on your phone that controls smart things
2.9.6 The Sensor Squad Song (Try Singing It!)
“Things that sense, things that think,Things that talk in just a blink!Connected to the internet they be,That’s what IoT means to me!”
2.10 Internet of Things Basics
Simple Definition: IoT = Everyday Objects Connected to the Internet
The Internet of Things (IoT) is like giving everyday objects a “digital brain” and connecting them to the internet. Imagine your coffee maker, thermostat, or even your trash can being able to communicate, think, and make decisions. It’s the transformation of ordinary “dumb” devices into “smart” ones that can sense their environment, process information, and take action automatically.
Everyday Examples You Already Use:
Device
What It Does
Why It’s IoT
Smart Thermostat
Learns your schedule and adjusts temperature automatically
Senses temperature, connects to internet, learns patterns
Fitness Tracker
Monitors heart rate, steps, and sleep patterns
Sensors on wrist, syncs data to cloud, provides health insights
IoT is revolutionizing how we live and work by making our environments more responsive and intelligent:
Convenience: Instead of manually adjusting your thermostat throughout the day, a smart thermostat learns your schedule and adjusts automatically
Efficiency: Instead of guessing when factory machines need maintenance, IoT sensors detect problems before they cause breakdowns
Insights: Instead of wondering “why is my energy bill high?”, IoT shows exactly which devices use the most power and when
Real Numbers - IoT’s Global Impact:
18-21 billion IoT devices deployed globally in 2025 (IoT Analytics/Statista), projected to reach 40+ billion by 2034
$1.5 trillion annual IoT market creating millions of new jobs
25% reduction in factory downtime with predictive maintenance
30% energy savings in smart buildings
40% improvement in agricultural yields with precision farming
50% reduction in water waste with smart irrigation
2.11 IoT Market Scale and Impact
Global deployment: 18-21 billion devices (2025) → 40+ billion (2034)
Annual device growth: 40B minus 20B over 9 years is about 2.22B additional devices per year.
Market value growth: $1.5T compounded at 14.5% for 9 years is about $5.1T by 2034.
Efficiency translation: 25% factory downtime reduction across global manufacturing ($15T sector) = $375B annual value creation. At $1.5T IoT investment, that’s a 4:1 value-to-cost ratio - explaining rapid enterprise adoption despite integration complexity.
Key Terms Table:
Term
Simple Definition
Example
Thing
Any physical object that can be equipped with sensors and connectivity
Light bulb, car, refrigerator
Sensor
A device that detects and measures something in the environment
Temperature, motion, light level
Actuator
A device that takes physical action based on commands
Turns on a motor, opens a valve, dims a light
Connectivity
The ability to send and receive data over the internet
Wi-Fi, cellular, Bluetooth
Gateway
A bridge that connects IoT devices to the internet
Your Wi-Fi router, smartphone
Cloud
Remote servers that store data and run applications
Where your fitness data is stored and analyzed
Edge Computing
Processing data close to where it’s collected rather than sending everything to distant cloud servers
Smart camera detects faces locally before uploading
Digital Twin
A virtual copy of a physical device or system used for simulation and optimization
Virtual model of a factory for testing changes
Checkpoint: Device Classification
You now know how everyday devices become IoT only when the object, processor, and internet path are all present.
You can classify the chapter’s examples: a basic microwave is embedded, a fitness tracker can use a phone gateway, and a cloud dashboard alone is software.
You can connect the scale claims to the classification: the chapter frames IoT around 18-21 billion deployed devices and a $1.5 trillion market.
The next section compresses that classification into the minimum working model you should carry into examples and exercises.
2.12 Minimum Viable Understanding
Three Ingredients Test: Every IoT device requires exactly three things – a physical “Thing” (sensor, appliance, vehicle), Computation (microprocessor that processes data), and Internet Connectivity (Wi-Fi, cellular, or gateway link). If any one ingredient is missing, the device is not IoT. A basic microwave has a Thing and Computation but no connectivity, so it is an embedded device, not IoT.
Five Verbs Framework: All IoT applications serve one or more fundamental human activities – SUSTAIN (energy and environment, $1.1T by 2030), MOVE (transportation and logistics, 16.5% CAGR), HEAL (healthcare and remote monitoring), FEED (precision agriculture and food safety), and MAKE (manufacturing and Industry 4.0). Use these verbs to categorize any IoT solution you encounter.
IoT is about human problems, not technology: The most successful IoT deployments start with a concrete human need (reduce energy waste, detect equipment failure, monitor patient vitals) and work backward to the technology. A $250 smart thermostat pays for itself in under 3 months through 30% energy savings – that human-centered ROI is what drives adoption, not the sensor specifications.
2.13 From Everyday Objects to IoT
Time: ~8 min | Level: Foundational | ID: P03.C01.U01
Key Concepts
IoT Architecture: Layered model comprising perception, network, and application tiers defining how sensors, gateways, and cloud services interact.
Edge Computing: Processing data close to the sensor source to reduce latency, bandwidth costs, and cloud dependency.
Telemetry: Time-stamped sensor readings transmitted from a device to a cloud or edge platform for storage, analysis, and visualisation.
Protocol Stack: Set of communication protocols layered from physical radio to application message format that devices must implement to interoperate.
Device Lifecycle: Stages from manufacture through provisioning, operation, maintenance, and decommissioning that IoT management platforms must support.
Security Hardening: Process of reducing attack surface by disabling unused services, applying least-privilege access, and enabling encrypted communications.
Scalability: System property ensuring performance and cost remain acceptable as the number of connected devices grows from prototype to mass deployment.
This section builds your understanding step by step - starting with devices you already know, then showing how they become “smart.”
Step 1: Start With What You Already Use
Think about devices in your home right now:
Traditional Device
What It Does
How You Control It
Regular Thermostat
Maintains temperature
Walk over and adjust dial
Basic Coffee Maker
Brews coffee
Press button manually
Standard Light Switch
Turns lights on/off
Flip switch by hand
Traditional Door Lock
Secures home
Use physical key
Question: What do all these have in common? Answer: They require you to be physically present to control them!
Step 2: Add Internet = Smart Device
Now imagine these same devices connected to the internet:
Smart Device
New Capability
Why It’s Better
Smart Thermostat
Control from anywhere via phone
Adjust temperature from work before coming home
Smart Coffee Maker
Schedule brewing time
Wake up to fresh coffee automatically
Smart Light Bulb
Turn on/off remotely
Never come home to a dark house
Smart Lock
Lock/unlock from phone
Let in guests when you’re not home
The Big Idea: IoT is like giving everyday objects the ability to talk, listen, and think.
Imagine your coffee maker could: - Talk: “I’m done brewing!” (sends you a notification) - Listen: “Alexa, start brewing coffee” (receives commands) - Think: “It’s 7am, time to brew” (makes decisions)
That’s the Internet of Things - ordinary objects connected to the internet, making them “smart.”
Figure 2.2: From traditional thermostat to smart thermostat: adding sensing, data logging, app control, and learned schedules
Step 3: The Three Essential Ingredients
Every IoT device needs exactly three things:
Ingredient
What It Means
Real Example
1. A “Thing”
Physical object you can touch
Thermostat box on your wall
2. Computation
Tiny computer chip inside
Processes temperature readings
3. Connectivity
Link to the internet
Wi-Fi connection to your router
Simple Test: If ANY ingredient is missing, it’s NOT an IoT device!
Figure 2.3: The three essential IoT ingredients: a physical thing, computation, and connectivity
Figure 2.4: Decision flowchart for the Three Ingredients Test: determining whether a device qualifies as IoT
2.14 Three Ingredients Test
Use this tool to determine whether a device qualifies as IoT by checking all three required ingredients.
Show code
viewof hasThing = Inputs.toggle({label:"1. Physical Thing (Can you touch it?)",value:true})viewof hasComputation = Inputs.toggle({label:"2. Computation (Has a processor/microcontroller?)",value:true})viewof hasConnectivity = Inputs.toggle({label:"3. Internet Connectivity (Connects to internet directly or via gateway?)",value:false})classification =!hasThing ?"Software/Cloud Service":!hasComputation ?"Passive Object":!hasConnectivity ?"Embedded Device":"IoT Device"allThree = hasThing && hasComputation && hasConnectivityhtml`<div style="background: ${allThree ?'linear-gradient(135deg, #16A085 0%, #2C3E50 100%)':'linear-gradient(135deg, #7F8C8D 0%, #2C3E50 100%)'}; padding: 24px; border-radius: 8px; color: white; margin: 20px 0; overflow: hidden;"> <div style="display: grid; grid-template-columns: repeat(auto-fit, minmax(105px, 1fr)); gap: 12px; margin-bottom: 20px;"> <div style="background: rgba(255,255,255,${hasThing ?'0.2':'0.05'}); padding: 16px; border-radius: 6px; text-align: center; border: 2px solid ${hasThing ?'#16A085':'rgba(255,255,255,0.2)'};"> <div style="font-size: 36px; margin-bottom: 8px;">${hasThing ?'✓':'✗'}</div> <div style="font-size: 11px; font-weight: 700; letter-spacing: 0.04em;">THING</div> </div> <div style="background: rgba(255,255,255,${hasComputation ?'0.2':'0.05'}); padding: 16px; border-radius: 6px; text-align: center; border: 2px solid ${hasComputation ?'#E67E22':'rgba(255,255,255,0.2)'};"> <div style="font-size: 36px; margin-bottom: 8px;">${hasComputation ?'✓':'✗'}</div> <div style="font-size: 11px; font-weight: 700; letter-spacing: 0.04em;">COMPUTE</div> </div> <div style="background: rgba(255,255,255,${hasConnectivity ?'0.2':'0.05'}); padding: 16px; border-radius: 6px; text-align: center; border: 2px solid ${hasConnectivity ?'#3498DB':'rgba(255,255,255,0.2)'};"> <div style="font-size: 36px; margin-bottom: 8px;">${hasConnectivity ?'✓':'✗'}</div> <div style="font-size: 11px; font-weight: 700; letter-spacing: 0.04em;">INTERNET</div> </div> </div> <div style="background: rgba(255,255,255,0.1); padding: 20px; border-radius: 6px; border-left: 4px solid ${allThree ?'#16A085':'#E74C3C'};"> <div style="font-size: 14px; opacity: 0.9; margin-bottom: 8px;">Classification Result:</div> <div style="font-size: 32px; font-weight: bold; margin-bottom: 12px;">${classification}</div> <div style="font-size: 13px; line-height: 1.6;">${!hasThing ?'Without a physical thing, this is pure software or a cloud service - not IoT.':!hasComputation ?'This is a passive object with no processing capability. Add a microcontroller to make it embedded.':!hasConnectivity ?'<strong>Almost there!</strong> This is an embedded device. Add Wi-Fi, Bluetooth, cellular, or a gateway connection to make it IoT.':'<strong>Congratulations!</strong> All three ingredients are present. This qualifies as a true IoT device.'} </div> </div></div>`
Common Examples:
Device
Thing
Computation
Connectivity
Result
Basic Microwave
✓
✓
✗
Embedded Device
Smart Thermostat
✓
✓
✓
IoT Device
Fitness Tracker
✓
✓
✓ (via phone)
IoT Device
Traditional Thermometer
✓
✗
✗
Passive Object
Cloud Dashboard
✗
✓
✓
Software Service
Real-World Impact
Why should you care about IoT? Because it’s already changing your life:
Water infrastructure monitoring exemplifies critical IoT applications where sensor data directly impacts public safety. Dam level systems provide real-time visibility that enables proactive flood management and optimized hydroelectric generation.
2.15 Knowledge Check: IoT Fundamentals
2.16 Interactive: IoT ROI Calculator
Calculate the payback period for your own IoT investment using this interactive calculator.
Try adjusting the sliders to see how different costs and efficiency improvements affect the payback period. Most consumer IoT devices (smart thermostats, smart lighting) pay for themselves in under 12 months, while industrial IoT investments may have 18-36 month payback periods but generate much larger absolute savings.
Understanding Check: Practice Questions
Before continuing, try thinking through these scenarios:
Scenario 1: Your basic microwave has a digital timer and heating element. Is it an IoT device? - Think about: Does it have all three ingredients? - Answer: No! It has a Thing (microwave) and Computation (timer chip), but NO internet connectivity. It’s an embedded device, not IoT.
Scenario 2: Your fitness tracker measures steps and syncs to your phone via Bluetooth, then uploads to the cloud. Is it IoT? - Think about: Does it have all three ingredients? - Answer: Yes! Thing (wristband), Computation (step counting), Connectivity (Bluetooth to Phone to Internet). It’s a true IoT device.
Scenario 3: What’s ONE way IoT could improve your daily routine? - Example answers: - Smart coffee maker starts brewing when my alarm goes off - Smart lights gradually brighten to wake me naturally - Smart car pre-heats in winter before I leave for work - Smart fridge tells me what groceries I need to buy
Checkpoint: Payback Logic
You now know that a $250 device with 30% savings on $3,900/year has a short payback because monthly savings drive the decision.
You can recompute the chapter’s result: $1,170 annual savings, $97.50 per month, and about 2.6 months to recover the device cost.
You can explain why industrial deployments may still be attractive with 18-36 month payback when the absolute savings and risk reduction are larger.
With the device test and payback logic in place, the chapter now widens from individual products to the human activities IoT supports.
2.17 The Five Verbs of IoT
Time: ~6 min | Level: Foundational | ID: P03.C01.U02
One powerful way to understand IoT’s transformative impact is through the lens of five fundamental human activities: SUSTAIN, MOVE, HEAL, FEED, and MAKE. This framework, popularized by IoT thought leaders, helps categorize the vast landscape of IoT applications into memorable categories that reflect how technology enhances essential aspects of human civilization.
Figure 2.5: The Five Verbs of IoT: SUSTAIN, MOVE, HEAL, FEED, and MAKE as human-centered application categories
2.18 Why This Framework Matters
Making IoT Memorable and Actionable:
The Five Verbs framework transforms IoT from an overwhelming landscape of thousands of applications into five memorable categories that students, designers, and business leaders can easily understand and apply. Instead of trying to memorize “smart cities,” “connected healthcare,” “precision agriculture,” and dozens of other domains, you can organize everything under five fundamental human activities.
For Students:
Categorization Tool: When you encounter a new IoT application, ask “Which verb does this serve?” This simple question helps you understand its purpose and value proposition immediately.
Design Framework: When designing your own IoT solution, start with “Which human need am I addressing?” This keeps your design grounded in real-world value rather than technology for technology’s sake.
Career Pathfinding: The five verbs map to distinct career paths - sustainability engineering (SUSTAIN), transportation tech (MOVE), health tech (HEAL), ag-tech (FEED), or industrial automation (MAKE).
For Practitioners:
Market Analysis: The verbs reveal where investment is flowing ($3.3T total market) and which sectors have the highest growth rates
Cross-Pollination: Solutions from one verb often inspire innovations in another (e.g., fleet tracking algorithms from MOVE applied to ambulance routing in HEAL)
Business Storytelling: Executives and investors understand “We help manufacturers MAKE better products” more quickly than “We provide predictive maintenance IoT solutions”
Real-World Validation:
This framework isn’t academic theory - it’s how industry leaders at companies like GE, Siemens, and Cisco organize their IoT strategy. When you understand the Five Verbs, you understand how the world’s largest IoT deployments create value.
2.18.1 Understanding the Five Verbs
Verb
What It Means
IoT Applications
Real-World Impact
SUSTAIN
Protecting our planet and managing resources wisely
Smart grids balance energy supply/demand, sensors monitor air/water quality, connected systems optimize waste collection
30% reduction in energy consumption through smart buildings, early detection of environmental hazards
The Five Verbs represent distinct market segments with varying maturity levels and growth trajectories. Understanding these economics helps guide career decisions, investment priorities, and business strategies.
Verb
2024 Market Size
2030 Projected Size
CAGR (Growth Rate)
Key Drivers
Leading Companies
SUSTAIN
$520B
$1.1T
13.2%
Climate regulations, ESG mandates, carbon taxes, renewable energy transition
Key Insight: will be the largest market by at $B, growing at % annually.
Key Insights from Market Data:
MOVE has the highest growth rate (16.5%) - Driven by the autonomous vehicle revolution and e-commerce logistics boom. If you’re entering IoT today, transportation tech offers the most explosive growth potential.
SUSTAIN has the largest market ($1.1T by 2030) - Climate change isn’t going away, and every building, factory, and city needs energy optimization. This is the most stable, regulation-driven market.
FEED has the smallest but fastest-growing market - Agriculture is traditionally slow to adopt technology, but water scarcity and climate change are forcing rapid modernization.
HEAL and MAKE are steady mid-growth markets - Healthcare and manufacturing are conservative sectors with long sales cycles, but once adopted, IoT solutions generate recurring revenue for decades.
Total IoT market doubles every 5 years - From $1.78T (2024) to $4.0T (2030), creating millions of new jobs across all five verbs.
Checkpoint: Market Verbs
You now know why the Five Verbs framework keeps IoT tied to SUSTAIN, MOVE, HEAL, FEED, and MAKE outcomes.
You can distinguish largest market from fastest growth: SUSTAIN reaches $1.1T by 2030, while MOVE carries the 16.5% CAGR.
You can use the market table to ask whether a proposal is solving a human activity or merely adding telemetry.
2.20 How to Use the Five Verbs Framework
Categorizing IoT Solutions:
When you encounter a new IoT application, ask yourself: “Which fundamental human activity does this enhance?”
Examples:
Smart thermostat -> SUSTAIN (optimizes energy use, reduces carbon footprint)
Connected ambulance -> MOVE (transports patients) + HEAL (transmits vital signs to hospital en route)
Factory robot -> MAKE (manufactures products with sensors and connectivity)
Wearable fitness tracker -> HEAL (monitors health metrics)
Why Some Applications Span Multiple Verbs:
Many IoT solutions touch multiple categories - a connected delivery truck both MOVES goods efficiently (route optimization) and FEEDS people (food delivery) or HEALS patients (medical supply logistics). This overlap demonstrates IoT’s interconnected nature.
Design Thinking Application:
When designing a new IoT product, use the Five Verbs as a brainstorming tool: 1. Which verb does your solution primarily serve? 2. Could it extend to serve additional verbs? 3. What’s the measurable impact for each verb it touches? (quantify efficiency gains, cost savings, lives saved)
Key Insight: The Five Verbs framework transforms IoT from an abstract technical concept into concrete categories that address fundamental human needs. Every successful IoT application ultimately helps us SUSTAIN our planet, MOVE more efficiently, HEAL better, FEED more people sustainably, or MAKE products smarter. This human-centered perspective keeps technology discussions grounded in real-world value.
2.20.1 Five Verbs Timeline
The following timeline shows when each IoT category reached mainstream adoption:
Figure 2.6: Timeline of IoT adoption across the Five Verbs categories, showing when each reached mainstream deployment
This timeline reveals an important pattern: MAKE (manufacturing) was the first IoT category to reach mainstream adoption, driven by industrial M2M (machine-to-machine) communication in factories. This is why Industrial IoT (IIoT) is often more mature than consumer IoT - it had a 10-15 year head start.
2.21 Knowledge Check: Five Verbs Framework
Checkpoint: Cross-Verb Reasoning
You now know that many applications span multiple verbs, such as a connected ambulance combining MOVE and HEAL.
You can classify the chapter’s precision-agriculture example as primarily FEED with a SUSTAIN benefit when herbicide use falls by 80%.
You can avoid forcing a single category when the business case depends on several stakeholders receiving measurable value.
2.22 Common Pitfalls When Learning IoT
Pitfall 1: Confusing “smart” with “IoT.” A device with a microprocessor and display (like a basic digital thermostat) is a smart embedded device, not an IoT device. The critical differentiator is internet connectivity. Without the ability to send data to the cloud or receive remote commands, a device cannot participate in the IoT ecosystem. Always apply the Three Ingredients Test before labeling something “IoT.”
Pitfall 2: Assuming IoT is only about consumer gadgets. Smart speakers and fitness trackers get the most media attention, but the largest IoT markets are industrial. SUSTAIN (energy and smart buildings) is projected at $1.1 trillion by 2030, and MAKE (manufacturing) at $870 billion. Students who focus only on consumer use cases miss the majority of career opportunities and economic value in IoT.
Pitfall 3: Treating the Five Verbs as mutually exclusive. Most real-world IoT applications span multiple verbs. A connected delivery truck both MOVEs goods and helps FEED people (cold chain monitoring for food safety). A smart hospital building SUSTAINs energy while HEALing patients. Forcing a single-verb classification misses the full value proposition and can lead to narrow designs that ignore important stakeholders.
Pitfall 4: Ignoring the business case. Technical feasibility alone does not make a viable IoT product. The smart thermostat succeeds because its $250 cost is recovered in under 3 months through energy savings. Many technically impressive IoT projects fail because they lack a clear payback period or measurable value for end users. Always quantify the ROI before building.
Pitfall 5: Underestimating security requirements. Every internet-connected device is a potential attack vector. Industry best practice recommends budgeting 15-20% of total project cost for security. A common beginner mistake is building an IoT prototype that works perfectly but has no authentication, no encryption, and no firmware update mechanism – making it unsafe for real-world deployment.
2.23 Video Resources
2.24 Recommended Videos: IoT Introduction
Foundational Understanding (Start Here):
Video
Duration
Key Topics
“What is IoT?” - IBM Technology
6 min
Clear definition, real examples, business value
“Internet of Things Explained” - TED-Ed
5 min
Animated overview suitable for all audiences
“IoT in 2025: The State of Connected Devices” - IoT Analytics
15 min
Current market data, trends, forecasts
Deep Dives by Verb Category:
Category
Recommended Video
Why Watch
SUSTAIN
“How Smart Cities Use IoT” - Cisco
Real smart city deployments with data
MOVE
“Inside Tesla’s Autopilot” - CNBC
Connected vehicle architecture
HEAL
“The Future of Digital Health” - HIMSS
Healthcare IoT challenges and solutions
FEED
“John Deere’s Precision Agriculture”
See and Spray technology in action
MAKE
“Industry 4.0 Explained” - Siemens
Factory IoT transformation
For Different Audiences:
Kids/Beginners: Search “IoT for Kids” or “Smart Home Explained for Children”
Business Leaders: “IoT ROI: Real Business Cases” - Gartner
Technical Deep Dive: “IoT Architecture Patterns” - AWS re:Invent
Note: Search these titles on YouTube. Video availability may change; look for recent uploads (2024-2026) for current market data.
2.25 Interactive Quiz: Match Concepts
2.26 Interactive Quiz: Sequence the Steps
2.27 Label the Diagram
2.28 Code Challenge
2.29 Summary
In this chapter, you learned:
IoT transforms ordinary objects by adding computation and internet connectivity
The Three Ingredients Test determines if any device is truly IoT: Thing + Computation + Internet
The Five Verbs Framework organizes all IoT applications into SUSTAIN, MOVE, HEAL, FEED, and MAKE
IoT’s global impact spans 18-21 billion devices and $1.5 trillion in market value
Market dynamics show MOVE as fastest-growing (16.5% CAGR) while SUSTAIN is largest ($1.1T by 2030)
Cross-verb applications often deliver the most value (e.g., connected ambulance = MOVE + HEAL)
2.30 Key Takeaway
The most important concept from this chapter: IoT is not about technology - it is about solving human problems. The Three Ingredients Test helps you identify IoT devices, but the Five Verbs Framework helps you understand why those devices matter. When evaluating or designing IoT solutions, always start with the human need (SUSTAIN, MOVE, HEAL, FEED, or MAKE) rather than the technology.
2.31 Smart vs IoT Confusion
The most frequent classification error in IoT is calling any device with a microprocessor “IoT.”
Example: The “Smart” Microwave That Isn’t IoT
A consumer electronics company launched a “$299 Smart Microwave” with these features:
Digital touchscreen control panel
20 preset cooking programs stored in memory
Internal sensor adjusts power based on food moisture
Voice notifications when cooking completes
Marketing labeled it “IoT-enabled smart appliance.” Customers expected remote control via smartphone and recipe suggestions from the cloud. Returns spiked to 18% (vs. 4% industry average) with complaints like “It’s not actually smart – I can’t control it from my phone.”
Internet Connectivity: ✗ No Wi-Fi, no cloud connection
2.31.1 In 60 Seconds
This introductory chapter establishes the foundational concepts and real-world context for the module, explaining why these topics matter and how they fit within the broader IoT landscape.
Classification: Embedded Device (not IoT)
The microwave has a sophisticated embedded system, but it lacks the third ingredient. Without internet connectivity, it cannot:
Receive recipe updates via OTA (over-the-air)
Learn from usage patterns across thousands of customers
Integrate with smart home ecosystems
Provide remote control or notifications
Cost of the Mistake:
Development: $2.1M for embedded software
Marketing: $850K emphasizing “smart” features
Returns and refunds: $1.8M (18% return rate on 60,000 units sold at $299)
Brand damage: 2.3-star average review (vs. 4.1 for their traditional microwaves)
Can now legitimately market as “IoT Smart Microwave”
Price justified at $299 (vs $199 traditional)
Option 2: Market Honestly (Avoid Misleading)
Call it “Digital Microwave with Smart Sensors”
Emphasize the embedded intelligence (moisture sensing, perfect popcorn)
Price at $229 (premium for convenience, not for connectivity)
Avoid “IoT” or “app-enabled” language
The Lesson:
IoT requires ALL THREE ingredients. Two out of three makes it:
Thing + Computation (no internet) = Embedded Device
Thing + Internet (no computation) = Networked Device (e.g., dumb webcam)
Computation + Internet (no thing) = Cloud Service
Only Thing + Computation + Internet = IoT Device
Test Your Understanding:
Before calling something “IoT,” apply the Three Ingredients Test. If even one ingredient is missing, find a more accurate classification. Your customers (and your return rate) will thank you.
The final decision example turns that classification rule back into an operational loop: sensing is only the start, and action is what proves the system’s value.
2.32 Sensor to Smart Decision
The big picture: IoT transforms raw sensor data into automated actions through a four-step cycle that repeats continuously – Sense, Connect, Process, Act.
Step-by-step breakdown:
Sense (Data Capture): A Nest thermostat’s temperature sensor reads 65°F (target: 72°F) – Real example: reads 10 times per minute = 14,400 readings per day
Connect (Data Transmission): The thermostat sends the reading to Google’s cloud via your home Wi-Fi – Real example: 100-byte payload transmitted in under 50 milliseconds
Process (Intelligence): The cloud compares 65°F vs. 72°F, checks your learned schedule (you prefer 72°F at 6 PM), and decides “turn on heat now” – Real example: processes data from 3 million+ Nest devices simultaneously using distributed servers
Act (Physical Response): The thermostat receives the command and activates the furnace relay while sending an alert to your phone – Real example: furnace ignites within 2 seconds, room reaches 72°F in 18 minutes
Why this matters: This sense-process-act loop distinguishes true IoT from simple “connected” devices. A remote-controlled light (Connected) only does step 4. A smart thermostat (IoT) completes all four steps autonomously, making decisions based on data patterns without constant human input. The 30% energy savings from Nest thermostats comes from this intelligent processing, not just connectivity.
Checkpoint: Closed-Loop Boundary
