← Back to the chapter · Next detail →
Technical detail · IoT Decision Validation
Go/No-Go as Systems Contract
A validation decision is not only a product choice. It is a contract between device behavior, network behavior, data governance, security, operations, and user workflow. If any layer lacks an owner or acceptance condition, the decision is not ready for pilot.
Make the contract inspectable. Narrowband Internet of Things (NB-IoT) and LTE for Machines (LTE-M) are cellular network services designed for connected devices; check whether each is available where the device will operate. Gateway backhaul is the link from a local gateway to the wider network or cloud service. A payload schema is the agreed description of each message field, its meaning, units, and format. Device evidence covers sensor tolerance, warm-up, fault state, battery or power supply, firmware version, watchdog behavior, and OTA rollback. Network evidence covers Wi-Fi coverage, LoRaWAN airtime, NB-IoT or LTE-M availability, MQTT, quality of service (QoS, the delivery level for a messaging exchange), retry behavior, TLS certificates, and gateway backhaul. Service evidence covers schema validation, timestamp quality, alert latency, dashboard freshness, access control, retention, and incident response.
Under the hood, validation fails when the acceptance record cannot be traced to runtime evidence. This agreed message-field description should identify units, timestamp source, device identifier, firmware version, and fault fields. A cloud ingestion path in AWS IoT Core, Azure IoT Hub, ThingsBoard, or a self-hosted broker should preserve rejection logs and versioned rules. A dashboard should show stale data differently from normal data, and an alerting path should distinguish sensor fault, network outage, rule misconfiguration, and operator non-response. Those distinctions matter because each failure has a different owner.
The validation contract should also test reversal. If the team chooses to stop, narrow, or simplify, the evidence should say which assumption failed and what will be retired or deferred. If the team proceeds, the same record should name pilot limits, data retention, certificate lifecycle, update responsibility, privacy review, support queue, and the trigger for retest. A connected product that cannot be safely narrowed or retired is already carrying technical debt before launch.
- Proceed: The connected path changes the user decision and each lifecycle owner accepts a measurable responsibility.
- Narrow: One connected behavior is justified, but analytics, automation, or fleet expansion should wait.
- Simplify: A local display, NFC/QR workflow, BLE logger, scheduled inspection, or CSV batch import meets the need with less burden.