Technology
Real-time data: streaming and IoT platforms for cities and utilities
How agencies collect and act on data from sensors, meters, vehicles, and signals as it happens.
Traffic signals, water meters, air quality sensors, transit vehicles, and building systems generate data continuously. Batch reporting the next morning is not enough for operations that need to respond now. Streaming data platforms process events as they occur and feed dashboards, alerts, and automated actions.
Components
Devices and gateways. Sensors and controllers, often on cellular or low-power wide-area networks, sending readings to a gateway.
Ingestion. A message broker or streaming service that receives events at scale and buffers them.
Processing. Stream processing that validates, enriches, aggregates, and detects conditions such as thresholds and anomalies.
Storage. Time-series storage for recent, high-resolution data and a data platform for history and analysis.
Action. Alerts to operators, work orders, control signals where appropriate, and dashboards for operations centers.
Agency uses
- Leak and pressure anomaly detection in water systems
- Signal performance and congestion monitoring
- Air quality and flood sensor networks with public alerts
- Transit vehicle location and arrival predictions
- Building energy monitoring and fault detection
- Fleet telematics for public works and public safety
Design considerations
Security. Devices are an attack surface. Unique credentials, encrypted transport, network segmentation, and firmware update capability are requirements, not options.
Data quality. Sensors fail and drift. Validation and gap handling are part of the pipeline.
Retention. High-resolution data is large; retention policy decides what is kept at what resolution.
Privacy. Cameras and location data need adopted policies.
Openness. Standard protocols and data formats avoid lock-in to a single device vendor.
Cost. Cloud streaming services charge by volume; design for the resolution operations actually needs.
Procurement
Separate the device purchase from the platform where possible, require open protocols and data export, and require security features in device specifications.
Where HQT fits
Platform architecture, ingestion and processing pipelines, integration with operations and work order systems, and dashboards.