IoT & Smart Infrastructure
IoT architecture for municipal water systems
- Discipline
- IoT & Smart Infrastructure
- Markets
- Building & Infrastructure · Business Services · Cities & Government · Environment · Industry · Resources & Waste · Transportation · Water & Utilities
Overview
An IoT project starts with the measurement and operating requirement. Select pressure, flow, level or quality observations according to the decision they support. Agree installation constraints, reading intervals, calibration responsibilities and acceptance checks before selecting a communication method.
Describe the route from sensor to gateway, platform, API and operational dashboard. Review power availability, communication coverage, buffering, time synchronisation and the handling of missing readings. Document identity, credential provisioning and access control for devices and service accounts. Confirm protocol compatibility for the specific device and project.
Pilot the architecture in representative field conditions. Test data quality, communication gaps, maintenance access and how operators respond to alerts. Synthetic chart activity is useful for demonstrations but does not demonstrate sensor performance or field uptime. Establish a service owner, change process and incident escalation route.
The measurement specification should identify the physical quantity, required unit, expected operating range and the decision threshold. It should also explain calibration, maintenance and how measurement uncertainty is reported. A high-frequency reading stream is not automatically useful if readings cannot be matched to an asset, compared in a consistent unit or distinguished from a device fault.
Plan failure behaviour as part of the interface design. Define what the gateway buffers, what happens after a network outage, how duplicate readings are detected and how delayed data is marked. Test a sensor disconnect, an interrupted connection and a service restart during the pilot. The dashboard should distinguish a measured condition from a stale reading or missing device message.
NIST publishes an IoT cybersecurity capability baseline that can inform a project-specific review. Include device identity, configuration, data protection, access, updates and status reporting in that review. Assess the actual device and deployment rather than assuming that a communication technology or a vendor label establishes the necessary controls. Record who maintains the device credentials and who can authorise a configuration change.
Further reading
Key considerations
- Define the operating question and asset boundary.
- Record input quality, units, ownership and revision.
- Agree review responsibilities and acceptance criteria.
- Verify project-specific requirements before implementation.
Related solutions
Product capabilities
- Define the operating question and asset boundary.
- Record input quality, units, ownership and revision.
- Agree review responsibilities and acceptance criteria.
- Verify project-specific requirements before implementation.
