From data to decision: how a City Brain coordinates municipal services

Each municipal service has added its own technology over the years, with its own supplier, its own screen and its own team. That works as long as a problem stays inside one service. But a city’s problems rarely respect those boundaries: a traffic accident affects mobility, safety, public transport and the information residents need.

When each system reacts on its own, coordination depends on phone calls, emails and the experience of whoever is on duty. The information exists, but it does not reach the people who need it in time.

A City Brain is a layer of intelligence that sits above the city’s systems. It does not replace them: it connects them. It receives their signals, interprets them together and proposes responses that involve several services at once.

At Equilia we design it in three layers:

• Data: the Equilia City Data Platform brings together information from IoT sensors, APIs, GIS mapping, municipal systems and external sources.
• Modules: each solution, such as Mobility AI, Water AI or Communication AI, handles one specific area and also works on its own.
• Intelligence: Equilia City Brain interprets the information from every module, makes predictions and proposes or carries out authorised actions.

This is how a response is coordinated when the systems are connected:

• A camera detects a possible incident at a junction and raises an alert for human review.
• Mobility AI identifies the congestion that is starting to build and proposes alternatives.
• The City Command Center receives the prioritised alert, with information from both systems on one screen.
• Communication AI tells residents about alternative routes through the council’s channels.

None of these steps is new on its own. What is new is that they happen as one coordinated response, instead of four separate reactions that someone has to join up by hand.

A system that coordinates public services has to be reliable and explainable. That is why City Brain is built on three principles:

• Every recommendation comes with its reasoning, so the person responsible can approve or reject it with full knowledge.
• Automatic actions only run if they have been authorised in advance, and each one is logged.
• Every system keeps its own controls, permissions and operational owners.

The result is a city that anticipates instead of reacting, without technology replacing the judgement of the people who know the municipality.

A council does not need all 17 solutions for coordination to pay off. Connecting two services that work separately today is enough. For example, infrastructure sensors and citizen services: when a sensor detects a fault, affected residents can be informed as soon as it is confirmed, without waiting for them to call.

Our process always starts with an assessment of the municipality’s challenges, its current systems and its data. From there we design the architecture and a phased roll-out plan, so the platform grows at the city’s pace.

Equilia City Brain is part of our strategic catalogue and is rolled out in phases, as the municipality connects its modules.