Unit 6: IoT Applications for Value Creations - Subjective Questions

A future factory, also called a smart factory, is a highly connected and automated manufacturing environment in which machines, products, workers, and business systems exchange data in real time.

Its major characteristics include:

• Interconnectivity: Machines, sensors, robots, and enterprise systems communicate through industrial networks and IoT protocols.
• Automation: Production and material-handling operations are performed with minimal manual intervention.
• Real-time visibility: Sensor data provides continuous information about equipment, products, and processes.
• Decentralized decision-making: Intelligent devices and edge systems can make local decisions without always contacting a central server.
• Predictive maintenance: Analytics identify signs of equipment failure before breakdown occurs.
• Flexible production: Manufacturing lines can be reconfigured for customized products and changing demand.
• Digital twins: Virtual representations of physical assets support simulation, monitoring, and optimization.

Thus, the future factory improves productivity, product quality, flexibility, safety, and resource efficiency.

IoT technologies create value in a future factory by converting operational data into actions that improve production and business performance.

• Predictive maintenance: Vibration and temperature sensors detect abnormal machine behavior, reducing unplanned downtime.
• Quality control: Cameras and sensors identify defects during production instead of after completion.
• Asset tracking: RFID, NFC, or wireless tags locate tools, materials, and finished goods.
• Energy management: Smart meters measure energy use and help schedule energy-intensive processes efficiently.
• Production optimization: Real-time data reveals bottlenecks and supports dynamic production scheduling.
• Worker safety: Wearable devices can monitor hazardous exposure, fatigue, or entry into restricted zones.
• Mass customization: Connected machines automatically adjust process parameters for different product variants.

For example, a connected motor may report increasing vibration. An analytics system can predict bearing failure and schedule maintenance during planned downtime. The resulting value includes lower maintenance cost, increased equipment availability, improved quality, and faster delivery.

A smart object is a physical object equipped with computation, communication, sensing, or actuation capabilities so that it can interact with its environment and participate in an IoT system.

Essential components are:

• Sensors: Measure parameters such as temperature, pressure, position, light, or motion.
• Actuators: Perform physical actions such as opening a valve or controlling a motor.
• Processor or controller: Executes embedded software and processes sensor data.
• Communication interface: Connects through technologies such as Wi-Fi, Bluetooth Low Energy, NFC, Zigbee, or NB-IoT.
• Power source: May be a battery, mains supply, or energy-harvesting unit.
• Identity: A unique identifier enables discovery, addressing, and management.
• Software and storage: Store configuration and implement local intelligence.

Important properties include context awareness, connectivity, autonomous operation, programmability, and the ability to cooperate with other objects or cloud services.

An ordinary physical object performs its intended physical function but generally cannot sense, communicate, or make computational decisions. A smart object combines a physical function with embedded intelligence and network connectivity.

Smart objects create value by:

• Providing real-time operational information.
• Enabling automatic control and remote operation.
• Supporting condition monitoring and predictive maintenance.
• Improving traceability and resource utilization.
• Supplying data for analytics and new digital services.

For example, a conventional electricity meter only displays consumption, while a smart meter sends readings automatically and supports demand-response programs.

A smart IoT application uses data from connected objects to monitor conditions, make decisions, and deliver useful services. A typical architecture contains the following layers:

1. Perception layer: Sensors, RFID tags, cameras, and actuators interact with the physical environment.
2. Connectivity layer: Networks and protocols transport data between devices, gateways, and services.
3. Edge or gateway layer: Gateways aggregate data, translate protocols, filter events, and perform local analysis.
4. Platform layer: Cloud or on-premises platforms provide device management, storage, messaging, security, and analytics.
5. Application layer: Dashboards, mobile applications, alerts, and automation workflows serve users.
6. Business layer: Enterprise systems use IoT information for planning, billing, compliance, and decision-making.

Important features include context awareness, real-time processing, interoperability, scalability, security, fault tolerance, and user-centered automation. A smart irrigation application, for example, combines soil-moisture readings, weather forecasts, and crop requirements to control irrigation automatically.

A protocol for constrained session initiation establishes, modifies, and terminates communication sessions involving devices with limited memory, processing power, bandwidth, or energy. It provides functions similar to conventional session-control protocols while reducing message size and implementation complexity.

Conventional mechanisms such as SIP may be unsuitable for constrained devices because they can involve:

• Large text-based headers and messages.
• Multiple request-response exchanges.
• Significant parsing and memory requirements.
• Persistent state and retransmission overhead.
• Security procedures that consume processing power and bandwidth.

A constrained session-initiation approach may therefore use:

• Compact or binary message encoding.
• Fewer signaling exchanges.
• Lightweight resource discovery.
• Efficient transport over constrained networks.
• Gateway or proxy support for communication with conventional systems.
• Lightweight authentication and authorization.

The objective is to establish reliable application sessions while preserving battery power, bandwidth, and memory. Such a protocol can support voice, alarm, monitoring, and device-control sessions in constrained IoT environments.

A typical constrained session-initiation procedure consists of the following stages:

1. Discovery: The initiating device discovers the destination endpoint or an appropriate service through a registry, resource directory, or gateway.
2. Session request: It sends a compact request containing the endpoint identity, required service, content format, and session parameters.
3. Authentication and authorization: The recipient, proxy, or authorization service validates the requester and checks permissions.
4. Negotiation: The endpoints agree on parameters such as transport method, data format, timing, and security context.
5. Session establishment: The destination accepts the request and returns a success response. Required resources are reserved or initialized.
6. Data exchange: Application data is transferred directly or through a proxy.
7. Modification or termination: Either endpoint may update parameters or close the session and release resources.

Endpoints generate or consume application data. Proxies forward requests, cache information, enforce policy, or reduce communication overhead. Gateways connect constrained networks to IP or enterprise networks and may translate addressing, message formats, and protocols. Reliability can be provided through acknowledgements, message identifiers, retransmission timers, and duplicate detection.

Near-Field Communication (NFC) is a short-range wireless technology that enables data exchange between compatible devices placed within a few centimetres of each other. It commonly operates at and is based on inductive coupling.

NFC supports three principal operating modes:

• Reader/writer mode: An active device reads from or writes to an NFC tag.
• Card-emulation mode: A device behaves like a contactless smart card for payment, ticketing, or access control.
• Peer-to-peer mode: Two active NFC devices exchange information directly.

Common IoT applications include:

• Device pairing and network configuration.
• Contactless payment and electronic ticketing.
• Smart locks and identity cards.
• Product authentication and anti-counterfeiting.
• Maintenance records attached to industrial equipment.
• Patient or medicine identification in healthcare.
• Reading passive sensor tags.

NFC is easy to use and offers physical proximity as an additional security condition. However, it has a very short communication range and relatively low data throughput.

NFC, Bluetooth Low Energy, and RFID serve different IoT communication and identification requirements.

NFC is preferable when deliberate close-range interaction and simple setup are needed. Bluetooth Low Energy is suitable for battery-powered sensors and wearables requiring greater range and repeated data transfer. RFID is appropriate for identifying many tagged items rapidly, especially in supply chains and warehouses. Selection depends on range, power, security, interaction model, and cost.

NB-IoT is a cellular Low-Power Wide-Area Network technology standardized by 3GPP for applications that transmit small amounts of data and require wide coverage, long battery life, and support for many devices.

Its major features are:

• Approximately of radio bandwidth.
• Strong indoor and underground coverage.
• Low device complexity and cost.
• Massive device connectivity per cellular coverage area.
• Power-saving mechanisms such as Power Saving Mode and extended Discontinuous Reception.
• Licensed-spectrum operation, providing managed interference and operator-controlled security.
• Support for low-throughput, delay-tolerant applications.

NB-IoT may be deployed in three modes:

• Standalone: Uses a dedicated carrier, including refarmed cellular spectrum.
• In-band: Operates within an LTE carrier using one resource block.
• Guard-band: Uses the unused spectrum at the edge of an LTE carrier.

Its architecture includes NB-IoT devices, cellular base stations, the mobile operator's core network, IoT platforms, and application servers. Typical applications include smart meters, parking sensors, environmental monitoring, and utility infrastructure.

NB-IoT is designed for low-data-rate devices that must operate reliably over large areas.

Advantages:

• Wide cellular coverage and improved penetration inside buildings.
• Long battery life, potentially lasting several years for infrequent transmissions.
• Support for a large number of devices.
• Use of licensed spectrum with managed quality and interference.
• SIM-based identity and cellular security mechanisms.
• Reuse of mobile operator infrastructure.

Limitations:

• Low throughput compared with LTE, Wi-Fi, or 5G broadband services.
• Higher latency, especially when power-saving modes are enabled.
• Unsuitable for video, large files, or strict real-time control.
• Dependence on network-operator coverage and subscription arrangements.
• Mobility and handover support may be more limited than in conventional cellular services, depending on deployment and release.

Suitable applications include smart water and gas meters, street lighting, waste-bin monitoring, parking sensors, pipeline monitoring, and low-rate agricultural sensors. It is unsuitable for autonomous vehicle control or high-resolution video surveillance.

Sigfox is a Low-Power Wide-Area Network technology designed for simple IoT devices that send small and infrequent messages over long distances. It uses ultra-narrowband radio communication in unlicensed sub-GHz spectrum.

A typical Sigfox architecture contains:

• End devices: Sensors or trackers that transmit compact radio messages.
• Base stations: Receive messages from any device within range. A single message may be received by multiple stations.
• Backhaul network: Transfers received messages to the Sigfox cloud infrastructure.
• Cloud platform: Removes duplicates, authenticates devices, manages messages, and provides service interfaces.
• Application server: Receives device data through callbacks or APIs and performs application-specific processing.

Sigfox communication is primarily optimized for uplink traffic. A device usually sends the same message more than once on different frequencies, improving the probability of reception without establishing a conventional connection. Downlink communication is more restricted and normally occurs in response to an uplink transmission. Sigfox is suitable for alarms, meter readings, asset status, and simple environmental measurements.

Sigfox and NB-IoT are both intended for long-range, low-power IoT applications, but they use different network models and radio technologies.

Sigfox is appropriate for simple sensors that send only a few small status messages. NB-IoT is more suitable when reliable bidirectional communication, stronger service management, remote configuration, or larger data volumes are required. The choice should consider local coverage, subscription cost, payload limits, latency, battery life, regulatory restrictions, and application criticality.

The Industrial Internet of Things (IIoT) is the use of connected sensors, machines, controllers, software platforms, and analytics in industrial sectors such as manufacturing, energy, transportation, mining, and utilities.

IIoT differs from consumer IoT in several ways:

IIoT systems must integrate operational technology with information technology while maintaining safety, real-time performance, security, and compatibility with legacy equipment.

The Industrial Internet of Things developed through the gradual convergence of industrial automation, networking, embedded computing, and internet technologies.

• Early industrial automation: Relays and analog instruments were used for machine and process control.
• PLC era: Programmable Logic Controllers introduced reliable programmable control on factory floors.
• SCADA and DCS development: Supervisory Control and Data Acquisition and Distributed Control Systems enabled centralized monitoring of industrial processes.
• Industrial networking: Fieldbus technologies and industrial Ethernet connected controllers, instruments, and machines.
• Machine-to-Machine communication: Remote devices began exchanging telemetry through wired, cellular, and proprietary networks.
• Internet and cloud integration: IP networking, web services, and cloud platforms enabled remote storage, management, and analytics.
• Industry 4.0 and IIoT: Cyber-physical systems, smart factories, digital twins, edge computing, artificial intelligence, and interoperable platforms became central concepts.
• Current stage: 5G, time-sensitive networking, edge AI, and advanced cybersecurity support increasingly autonomous industrial systems.

This evolution transformed isolated automation systems into connected environments where operational data can be analyzed across machines, plants, and enterprises.

An IIoT system is composed of interacting physical, communication, computing, and application components.

• Industrial assets: Machines, motors, pumps, production lines, vehicles, and other physical equipment.
• Sensors and actuators: Sensors measure operating conditions, while actuators modify physical processes.
• Controllers: PLCs, Remote Terminal Units, and embedded controllers execute control logic.
• Industrial networks: Fieldbus, industrial Ethernet, wireless links, and cellular systems transport data.
• Edge devices and gateways: Aggregate data, translate protocols, enforce security, and run low-latency applications near the equipment.
• IIoT platform: Provides device registration, message handling, data storage, rules, digital twins, and device management.
• Analytics and AI: Detect anomalies, predict failures, optimize processes, and support decisions.
• Applications and interfaces: Dashboards, alarms, mobile applications, and enterprise integrations present information and control workflows.
• Security services: Identity management, encryption, access control, monitoring, and secure updates protect the system.

Together, these components form a path from physical measurement to analysis, decision-making, and controlled action.

Brownfield IoT refers to adding IoT capabilities to an existing facility, machine, or infrastructure rather than designing a completely new connected system. It is common in industry because machines may remain operational for several decades.

Major challenges include:

• Legacy equipment without digital communication interfaces.
• Proprietary or undocumented protocols.
• Different equipment ages, vendors, and data formats.
• Strict uptime requirements that limit installation opportunities.
• Safety and certification constraints.
• Weak authentication or encryption in older control systems.
• Difficulty obtaining clean and consistent data.

Common implementation methods are:

• Attaching non-invasive vibration, current, acoustic, or temperature sensors.
• Connecting protocol gateways to interfaces such as Modbus or serial links.
• Reading PLC or SCADA data through controlled, preferably read-only, integration.
• Performing preprocessing and protocol translation at an edge gateway.
• Segmenting operational and enterprise networks with firewalls and secure zones.
• Introducing the system through a pilot project before scaling.

A successful brownfield project begins with asset inventory and risk assessment, followed by data acquisition, secure integration, validation, and gradual deployment. It preserves existing investments while enabling monitoring and analytics.

IoT enables precision agriculture, in which farm inputs are applied according to measured field conditions rather than uniform estimates.

A smart agriculture system may contain:

• Soil-moisture, temperature, humidity, pH, and nutrient sensors.
• Weather stations that measure rainfall, wind, and solar radiation.
• Cameras, drones, or satellite data for crop-health monitoring.
• GPS-enabled equipment and livestock tracking devices.
• LPWAN, cellular, mesh, or satellite connectivity.
• Edge gateways and cloud platforms for storage and analytics.
• Pumps, valves, and fertigation controllers as actuators.

For precision irrigation, sensors periodically report soil moisture. The application combines this data with crop type and weather forecasts. When moisture falls below a crop-specific threshold and rain is not expected, the controller opens the required irrigation valve. Flow sensors verify water delivery and identify leakage.

The system reduces water and fertilizer use, improves crop yield, detects disease or stress earlier, and lowers labor requirements. Challenges include rural connectivity, sensor calibration, weather exposure, power availability, maintenance cost, and protection of farm data.

IoT in healthcare connects medical devices, patients, caregivers, and information systems to improve monitoring and service delivery.

Important applications include:

• Remote monitoring of heart rate, blood pressure, oxygen saturation, glucose, and temperature.
• Wearable fitness and rehabilitation devices.
• Medication reminders and connected drug dispensers.
• Tracking of medical equipment and staff.
• Smart hospital beds and fall-detection systems.
• Cold-chain monitoring for vaccines and medicines.
• Emergency alerts and elderly-care systems.

A remote patient-monitoring architecture includes medical sensors, a wearable or bedside device, a smartphone or home gateway, a secure network, an IoT platform, an electronic health-record interface, and a clinician dashboard. Sensor readings are validated and encrypted before transmission. The platform stores and analyzes data, and a rules engine generates an alert when readings exceed clinically defined limits. Clinicians review the patient's history and decide whether intervention is required.

The system can reduce hospital visits and support early treatment, but it must address accuracy, availability, informed consent, privacy, interoperability, and regulatory compliance.

IoT applications create value by collecting and acting on real-world data, but they also introduce significant risks.

Security challenges:

• Weak credentials, insecure interfaces, and unpatched firmware may allow unauthorized access.
• Compromised actuators can affect industrial machinery, irrigation systems, or medical devices.
• Appropriate controls include unique identities, least-privilege access, encryption, secure boot, signed updates, network segmentation, and continuous monitoring.

Privacy challenges:

• Healthcare data can reveal medical conditions, while agricultural and industrial data can expose commercially sensitive operations.
• Data collection should follow purpose limitation, minimization, retention controls, and informed consent where applicable.

Reliability and safety challenges:

• Sensor failure, packet loss, cloud outages, or incorrect analytics can produce unsafe decisions.
• Systems require validation, redundancy, local fail-safe behavior, audit logs, and manual override mechanisms.

Ethical challenges:

• Continuous monitoring may enable unfair surveillance of workers or patients.
• Automated decisions may be biased or difficult to explain.
• Ownership of device data and responsibility for failures may be unclear.

Risk management must consider the complete lifecycle, from device procurement and deployment to maintenance, incident response, and secure decommissioning.