Request a Demo
Platform InfrastructureTier-1 Hardware

IoT & Sensor Platform

The device management, real-time data ingestion, and edge computing layer for the Civic platform — every module that connects to physical sensors, meters, or smart infrastructure routes through IoT & Sensor Platform.

99.95%

Ingestion SLA

<5s

Alert Latency

100K/min

Throughput

9+

Protocols

Purpose-Built for Canadian Municipalities

Ontario Compliant
MFIPPA Ready
AODA Accessible
Bilingual Support
Canadian Hosted
SOC 2 Aligned

How It Works

The identity journey, step by step

From first registration to golden record resolution — how a resident's identity evolves across the platform.

01

Device Provisioning

An operations technician provisions a batch of new water meters across a neighborhood.

How it works

The technician uploads a CSV of 200 new AMI water meters with serial numbers, GPS coordinates, and asset IDs. The platform auto-generates certificates, assigns MQTT topics, creates device registry entries, and configures default alert rules (leak detection, inactivity). Devices begin reporting within minutes of field installation.

Step 1 of 5

Purpose & Scope

What this module owns

Clear ownership boundaries prevent duplication and ensure every capability has exactly one authoritative home.

Owns

11

Delegated to

4

AI/ML analytics on sensor data

ai-ml-engine

Map visualization of sensors

geospatial-engine

Business rules triggered by sensor data

consuming modules

Citizen notification

notification-engine

These capabilities are handled by dedicated modules and consumed via stable API contracts — keeping boundaries clean and ownership unambiguous.

Core Capabilities

What it does

5 capability groups comprising 10 discrete capabilities — each with API surface, business rules, and data ownership.

Comprehensive device registry supporting water meters, traffic sensors, air quality monitors, weather stations, parking sensors, smart streetlights, and dozens more device types.

Device Types

Water meters (AMI/AMR), traffic sensors, air quality monitors, weather stations, parking sensors, smart streetlights, flood sensors, noise monitors, waste bin sensors, EV chargers, SCADA RTUs, building automation controllers, smart locks, CCTV cameras.

Metadata

Device ID, type, model, firmware version, install date, location, assigned asset, department.

Lifecycle

Provisioned → Active → Maintenance → Decommissioned status tracking with full audit trail.

Grouping

Group devices by type, location, department, network, or project for bulk operations and reporting.

Bulk provision, configure, update, and decommission devices — manage thousands of devices at scale.

Bulk Provisioning

Import CSV/JSON device lists to provision hundreds of devices at once with automatic certificate generation.

Bulk Configuration

Push configuration changes to device groups — reporting intervals, alert thresholds, firmware versions.

Bulk Update

Schedule OTA firmware updates across device fleets with staged rollout and rollback support.

Bulk Decommission

Mass decommission devices by location, project, or type with automated cleanup.

Real-World Scenarios

Who uses this, and how

4 persona-driven scenarios showing how IoT & Sensor Platform works in practice — from resident registration to privacy compliance.

Water Utility Operator

Automated Water Leak Detection

The water utility uses AMI meters and pressure sensors to detect leaks in the distribution network before they cause road damage or water loss.

Steps

  1. 1500 AMI water meters and 50 pressure sensors report data every 15 minutes via MQTT
  2. 2The alert rules engine monitors flow rate and pressure with composite conditions
  3. 3A sudden flow spike on two adjacent meters triggers a rate-of-change alert
  4. 4Simultaneously, a nearby pressure sensor drops below the threshold — composite alert fires at critical severity
  5. 5The on-call crew receives a push notification with the exact location on a map
  6. 6Crew acknowledges the alert, isolates the section, and marks the alert resolved after repair

Outcome

Leak detected within 5 minutes of occurrence, 3 hours faster than citizen-reported. Estimated water loss reduced by 80% for this incident. Full timeline logged for asset management records.

View scenario

Environmental Compliance Officer

City-Wide Air Quality Monitoring

The municipality deploys 25 air quality monitors near schools, hospitals, and high-traffic corridors to meet new provincial air quality reporting requirements.

Steps

  1. 125 air quality sensors (PM2.5, PM10, NO₂, O₃) provisioned via bulk import with GPS coordinates
  2. 2Sensors report every 5 minutes via LoRaWAN to the city's network server
  3. 3Time-series data is stored with automatic 5-min, hourly, and daily aggregations
  4. 4Threshold alerts configured: PM2.5 > 35 µg/m³ triggers a warning; > 55 µg/m³ triggers critical
  5. 5Monthly compliance reports are generated from the hourly aggregation tier
  6. 6Real-time air quality index is published to the citizen portal via integration-bus

Outcome

Provincial reporting requirements met with automated data collection. Two high-pollution zones identified, leading to traffic calming measures. Real-time AQI data available to residents.

View scenario

Parking Operations Manager

Smart Parking Occupancy

Downtown parking garages and on-street spaces are equipped with occupancy sensors to provide real-time availability and optimize enforcement patrols.

Steps

  1. 13,000 parking sensors (in-ground magnetometers) provisioned across downtown core
  2. 2Sensors report occupancy changes in real-time via Sigfox (ultra-low-power, battery lasts 5+ years)
  3. 3Real-time occupancy data feeds the parking guidance system and mobile app
  4. 4Inactivity alerts flag sensors that stop reporting — maintenance crew dispatched
  5. 5Historical occupancy data analyzed to optimize time limits and pricing

Outcome

Average time-to-park reduced by 30%. Enforcement efficiency improved 40% with data-driven patrol routes. Sensor fleet maintained proactively with < 2% downtime.

View scenario

Emergency Management Coordinator

Flood Early Warning System

The municipality deploys water level sensors and rain gauges in flood-prone areas to provide early warning and trigger automated response protocols.

Steps

  1. 120 flood gauges and 15 rain gauges deployed at critical waterways and stormwater infrastructure
  2. 2Sensors report every 2 minutes during normal conditions, every 30 seconds during storm events
  3. 3Rate-of-change alerts detect rapidly rising water levels — warning issued at 1m, critical at 1.5m
  4. 4Edge gateway triggers automatic floodgate control without waiting for cloud processing
  5. 5Emergency management receives geofenced alerts with affected area maps
  6. 6Sensor data feeds the emergency operations dashboard for real-time situational awareness

Outcome

30-minute advance warning for flash flood events. Automated floodgate response reduces property damage. Post-event sensor data supports insurance claims and infrastructure investment decisions.

View scenario

Internal Architecture

How it's built

4 architectural layers comprising 25 components — from API gateway to data quality engine.

4 layers · 25 total components

IoT & Sensor Platform

Every module owns a single bounded context, exposes stable APIs, and can be composed into any Civic product — that's the architecture that scales.

Krutik Parikh

Creator of Civic

Data Model

Entity Architecture

4 entities with 4 relationships — the authoritative schema for this bounded context.

Entities

Select an entity to explore its fields and relationships

API Surface

Integration Endpoints

10 RESTful endpoints across 3 resource groups — plus 6 domain events for async integration.

|
GET

/api/v1/iot/devices

List devices (filtered by type, location, status)

POST

/api/v1/iot/devices

Provision new device

GET

/api/v1/iot/devices/{id}

Get device detail with latest reading

GET

/api/v1/iot/devices/{id}/readings

Get time-series data (with time range, aggregation)

Ecosystem

Products that depend on this module

16 Civic products consume IoT & Sensor Platform — making it one of the most critical platform services in the ecosystem.

Technical Specifications

Performance, Compliance & Configuration

Availability

Target99.95% for ingestion pipeline

Ingestion Latency

Target< 500ms from device to time-series store

Alert Latency

Target< 5 seconds from reading to alert trigger

Throughput

Target100,000 readings/minute sustained

Device Scale

TargetSupport 50,000 registered devices per municipality

Time-Series Storage

TargetPlan for 1 billion readings/year; tiered retention

Edge Resilience

TargetEdge gateways operate independently during 72-hour cloud outage

FAQ

Frequently Asked Questions

Ready to Integrate

Build on IoT & Sensor Platform

Request an architecture brief, integration guide, or live demo environment for your team.