Pilots are becoming platforms
Cities are moving from single-purpose pilots to shared platforms that several agencies use.
What it means for deliveryCommon data models and open interfaces matter more than any single application.
Cities are connecting transport, utilities and public services, and need the data those systems produce to be shared safely between agencies and suppliers. We help public bodies and their partners build that foundation and the services on top of it.
The question we hear most
Most smart-city estates are built one project and one supplier at a time. The result is a set of capable systems that cannot share data, each with its own contract — and a city that depends on its suppliers to tell it what its own infrastructure is doing.
We help public bodies build the shared foundation first: a common data model, access rules written for each purpose, and open interfaces documented as they are built. The applications on top can then change supplier without the city losing its data or its history.
The shifts changing what good delivery looks like here, and what each one asks of the teams doing the work.
Cities are moving from single-purpose pilots to shared platforms that several agencies use.
What it means for deliveryCommon data models and open interfaces matter more than any single application.
Data protection law and public scrutiny apply to every camera, sensor and citizen record.
What it means for deliveryPurpose limits and access rules have to be enforceable in the platform itself.
Integrated command and control centres bring traffic, safety, utilities and services into one operations room.
What it means for deliveryReal-time integration across suppliers becomes the critical path.
Infrastructure bought today has to stay serviceable for decades, through several changes of supplier.
What it means for deliveryDocumented interfaces and handover artefacts protect the city’s options.
The pressures differ inside an industry too. These are the parts of it our teams work in, and what sets each one apart.
Property, permits, sanitation and grievance services that touch every resident.
Buses, metro and traffic systems sharing schedules, positions and incidents.
Water, power and gas networks with metering and SCADA data to put to work.
Command, dispatch and video systems where minutes and privacy both matter.
Special-purpose vehicles running multi-supplier programmes on fixed budgets.
Partners delivering city programmes who need a governed platform to build on.
Each offering runs on its own or as part of a wider programme, and draws on the AI services, consulting practices and products listed with it.
A shared platform where agencies publish and use data under rules the city sets, built on open standards such as NGSI-LD.
Buses, service vehicles and transit feeds in one live view, with service reliability reported from the data rather than from paperwork.
Assistants that answer from published information in the languages residents use, and grievances routed to the right department with a person deciding.
One record of scope, interfaces, milestones and acceptance across every supplier, so the city can see progress and change suppliers later.
We do not certify compliance — your auditors and assessors do. We make sure the evidence each framework asks for is produced by the delivery process itself.
Common first engagements in this sector. Most begin with a two-week, fixed-price discovery that leaves you with a costed plan whatever you decide next.
Every vehicle, reporting in real time.
View productA whiteboard that stays attached to the work.
Included with SyncupHUBView productThe delivery platform for the AI era.
View productLiving documents, right beside the work they describe.
Included with SyncupHUBView productYes. Our approach is zero training on your data, with private model routing for hosted models. Where the data cannot leave your control at all, we build the whole stack on your own hardware, air-gapped if required.
We keep the design model-agnostic and document interfaces as we build, with handover artefacts produced continuously — so another supplier, or your own team, can take over.
Routinely. We are often brought in to make a multi-supplier programme cohere, with shared interfaces, quality gates and telemetry.
Yes. Where a command and control centre already exists, we connect it to the shared data platform through documented interfaces, so it gains data from more agencies without being rebuilt.
Running models inside your own boundary solves real problems — data that cannot leave, cost at volume, control over versions — and creates others. A practical way to decide, workload by workload.
The EU’s NIS2 Directive extended cybersecurity duties to thousands of organisations in manufacturing, transport, health, digital services and more. Most of its ten minimum measures are things engineering teams build and run.
Tell us the constraint and the systems behind it. We will put an engineer who has worked with both on the call, not the nearest salesperson.
What the first call covers