An IoT product may include the device, local gateway, companion application, network services, cloud platform, data stores, and administrative functions that deliver its purpose — not only the visible object.
IoT appears in homes, enterprises, cities, healthcare, agriculture, transportation, and industry. Devices may connect directly or indirectly, operate with limited power or processing, and remain deployed longer than their software or supporting services are maintained.
Key points
Physical interactionSensors collect environmental or operational data, while actuators can change equipment or conditions; some devices perform both roles and may continue limited local operation when disconnected.
Ecosystem behaviorDevices exchange data and commands with gateways, applications, platforms, users, and other devices, creating dependencies on identity, protocols, service availability, data handling, and supplier support.
Lifecycle considerationsAcquisition should address ownership, interoperability, configuration, updates, vulnerability reporting, support duration, inventory, maintenance, safe failure, data deletion, transfer, and decommissioning.
Important limitationIoT has no universally enforced boundary or architecture. Network connectivity alone does not establish that a product is IoT, and calling something “smart” reveals nothing about its security, privacy, safety, interoperability, or continued support.