Public sector
Smart cities and urban data platforms
Sensor and vendor data in one place, alerts that become work orders and city dashboards people can trust.

The problem
What breaks today, and what we usually build
What breaks today
Every vendor's sensors come with their own dashboard, so nobody sees the city in one view. An alert from a flooded underpass or a failed streetlight never becomes a work order, and open data is published by hand when someone remembers.
What we usually build
A data layer that pulls from vendor APIs into a cloud store, rules that turn alerts into work orders in the maintenance system, dashboards for departments and the command center, and scheduled publishing of open datasets.
Automations worth building
Sensor thresholds raising work orders with location and asset, repeat faults grouped for the contractor, and open datasets refreshed and published on a schedule.
What we measure in discovery
Alerts that never became work orders, time from alert to fix, vendor systems feeding the shared view, datasets published on schedule.
Systems it usually connects to
- IoT and sensor vendor APIs (MQTT, REST)
- Integrated command and control center platforms
- GIS (ArcGIS, QGIS)
- Video management systems (alerts only)
- Open data portals
- Contractor maintenance systems
Rules
Rules your systems have to follow
What each rule means for your systems. Your counsel and accountants confirm what applies to you; we build the controls and reports.
CERT-In directions of April 2022 (India)
Cyber incidents must be reported within six hours and ICT system logs kept for 180 days, so logging, retention and an incident runbook are part of the design.
National Data Sharing and Accessibility Policy (India)
Non-sensitive government data is meant to be published as open data, so datasets are classified at design time and published through the open data portal.
NIS2 Directive (EU)
Public administration and essential services such as water and energy face security and incident-reporting duties, which apply to the platforms that collect their data.
GDPR for cameras and license plates (EU)
Video analytics and number plate data are personal data, so retention periods, access and an impact assessment are settled before the feed is connected.
Where we fit
We connect the data that sensors and vendor systems produce to dashboards, alerts and work orders, usually as a software subcontractor to the master system integrator. We do not install sensors, cameras or networks, and we do not build SCADA or traffic signal control.
Modules
The business modules we usually start with
- Maintenance (CMMS)Planned maintenance before the breakdown happens
- Helpdesk & SupportOne queue for email, portal and chat
- Project ManagementTimesheets, budgets and live project margin
- Automated Exception Routing & Approval EnginesAI automation with human approval
- Enterprise Knowledge & Policy AssistantAI automation with human approval
- Omnichannel Unified AI InboxAI automation with human approval
Platforms
Platforms that usually fit
A data platform on AWS, Azure or a MeitY-empaneled Indian cloud, with Odoo or ERPNext for maintenance work orders and Dynamics 365 for citizen service where it is the approved platform.
- 01 Odoo Enterprise A modular, highly customizable all-in-one business ERP
- 02 ERPNext & Frappe Clean, framework-first open-source ERP where you keep full control of data and code
- 03 Microsoft Dynamics 365 Deep integration with Microsoft 365, Azure, and enterprise supply chain ecosystems
- Not sure which one? Compare platforms side by side · Platform selection
Where to start
Fixed-scope offers to begin with
Each ends with a written deliverable you can use with any vendor, including us.
More in Public sector
Other public sector sectors
- Digital governanceApplications, approvals, beneficiaries and grant spend tracked in one auditable system, with status citizens can check themselves.
- Municipal bodiesGrievances routed by ward, works contracts measured and billed in stages, and an asset register the accounts can rely on.
- Public healthField data captured once and offline, medicine and vaccine stock visible at every facility and program indicators without monthly spreadsheets.
Can you bring data from several sensor vendors into one view?
Yes, where each vendor provides an API or data export. The contract should require one; where it does not, that becomes the first item in the roadmap.
Who owns the data the platform collects?
The city should, and the architecture assumes it: data lands in a store the city controls, and vendors read from it rather than holding the only copy.
Which platform fits smart cities and urban data platforms?
A data platform on AWS, Azure or a MeitY-empaneled Indian cloud, with Odoo or ERPNext for maintenance work orders and Dynamics 365 for citizen service where it is the approved platform. We confirm the fit in a platform selection, with written reasons for and against each option.
Where do we start?
With the Cloud Architecture & Security Review: check your cloud setup against good practice before an incident does it for you. It ends with a written deliverable you can use with any vendor, including us.
Next step
Not sure what to fix first?
Book a 30-minute consultation. We look at how your operation runs and tell you what we would do first, including when the answer is a simpler tool.