Draw the city architecture first. Talk equipment second.
The deliverable is a city intelligence system that can be built in phases, changed supplier by supplier and operated for years: an operations centre that sees the whole city, a platform layer that governs data and interfaces, and applications for transport, public safety, emergency and municipal services that launch one by one.
Four traps city projects fall into
Most of them sit in procurement structure, not in technology.
Every department buys its own
Transport, emergency and municipal teams build separate platforms. Data never meets, and the command centre ends as a wall of screens.
Locked to one vendor
Closed interfaces and no data export make a phase-two supplier change a rebuild.
Nobody screened the equipment list
Camera and network sources are complicated. Supply-chain compliance surfaces after the bid, when it is expensive.
Built, then unoperated
Acceptance day is the peak. Watch, re-verification and upgrades have no budget line, and the system ages out in two years.
Architecture
One centre, one platform, N applications. Each layer is accepted on its own.
Intelligent operations centre
The IOC runs on the situational core for city awareness, event distribution and emergency command. Operators see events to act on, with evidence attached.
- Citywide event intake and distribution
- Awareness and evidence on one screen
- Emergency command workflows
- Watch handovers on record
City platform layer
Shared identity, data catalogue, API standards and a message backbone. Department systems connect to the standard instead of rebuilding a base.
- Shared identity and role permissions
- Data catalogue and definitions
- API standards and a message backbone
- A connection standard departments are accepted against
Digital twin module
Facilities, road networks and events mapped into a queryable city model, serving dispatch and exercises first, planning later.
- Facilities and road networks modelled
- Events mapped and queryable
- Dispatch and exercises first
- Planning uses follow
Application groups
Transport signals and incidents, public-safety awareness, emergency resource dispatch and municipal service work orders, each scoped and accepted separately.
- Transport signals and incidents
- Public-safety awareness
- Emergency resource dispatch
- Municipal service work orders
Modules that can be ordered separately
The architecture is one system; procurement is by module. Each item signs and accepts on its own, and later modules connect along the same platform layer.
| Module | What is included | Acceptance deliverable |
|---|---|---|
| Intelligent operations centre (IOC) | Event intake and dispatch, situation map and evidence on one screen, command workflow, duty hand-over logging | IOC acceptance sheet and duty procedure |
| City platform layer | Unified identity and role permissions, data catalogue, API standards and message bus, department onboarding rules | Interface standard documents and onboarding acceptance records |
| Digital twin module | Facility and road-network modelling, event mapping and query, serving dispatch and exercises first | Model inventory and query acceptance record |
| Transport pack | Signal coordination and transport incident handling workflows | Scenario acceptance sheet and handling record samples |
| Emergency dispatch pack | Emergency resource register, dispatch workflow and exercise support | Dispatch procedure and exercise records |
| Municipal work-order pack | Work-order intake, assignment, completion and follow-up workflow | Workflow acceptance sheet |
| Data governance & export pack | Data dictionary, statistical definitions and export verification, so a supplier change takes the data along | Data dictionary and export verification record |
How the platform connects
City programmes reuse the shared foundation.
Situational core
IOC events, entities and timelines come from one core. Intelligence and warning products can feed it directly.
Institutional One ID
Departments, roles and operator accounts are partitioned. Citizen-facing entry points stay separate from internal workspaces.
ONE operations foundation
Post-launch monitoring, response and re-verification run as a logged operation, reported to the city monthly.
Delivery route
Design can be bought alone, or credited into the build. Every step leaves something you can inspect.
Current-state survey
Inventory existing systems, data and equipment. Compliance screening runs alongside.
Deliverables: the current-state report: system, data and equipment inventories with screening conclusions.
Master design
Architecture, interface standards, data governance, phase list and operating terms fixed in one pass.
Deliverables: the master design pack: architecture, interface standards, data governance, phase list and operating terms.
Phased build
Applications are built and accepted one by one. Each phase ships a data dictionary and an export test.
Deliverables: per phase, the application, a data dictionary, an export test record and an acceptance sheet.
Managed operation
IOC watch routines, re-verification and upgrades enter long-term operation. Replaceable points are reviewed yearly.
Deliverables: monthly operating reports, re-verification records and an annual review of replaceable points.
- Design can be contracted alone. Build is signed by phase, operations by year.
- Every package carries a localisation set: local partner, local deployment and local content sources.
- Overseas city work enters through a prime integrator or local partner supply chain, with export and local-law review per deal.
Openness & compliance
City systems run for a decade. The contract should think about year ten.
Anti-lock-in terms
Open APIs, data export and exit assistance go into the contract. Phase two is not held hostage by phase one.
Screened equipment
Equipment and components are checked line by line against Section 889 and kept on record, with ownership diligence on sensitive suppliers.
Data residency
City data resides by jurisdiction. Local or dedicated-network deployment is available, and key arrangements are set at design time.
Use limits in the contract
Public-safety applications are designed without facial-recognition template generation and without mass personal-surveillance functions. The limits are written into the contract.
Questions, answered
How do our existing department systems connect?
To the platform standard, not to a rebuild. The platform layer fixes shared identity, the data catalogue and API standards first. Department systems connect one by one, and new applications are built on the standard instead of rebuilding a base.
How should the phases be cut so nothing is wasted?
Platform layer and IOC first, applications one at a time after. Each phase is accepted on its own and ships a data dictionary and an export test, so phase two never has to undo phase one. The phase list is fixed once, in the master design.
Who reports on the equipment screening?
The conclusions land in the current-state report. Equipment and components are checked line by line against Section 889 and kept on record, with ownership diligence on sensitive suppliers, and the findings are delivered with the survey.
Whose people staff the IOC watch?
Either side, or a mix. It is settled in the operating terms. The city team can staff the watch, we can run it as a managed operation, or shifts can be shared. Either way, actions and handovers stay on record and are reported monthly.
Who owns the city data?
The city does, resident in its jurisdiction. Local or dedicated-network deployment is available, key arrangements are set at design time, and data export and exit assistance go into the contract.
Can we buy the design only?
Yes. Design stands alone, unbundled from the build. Build is signed by phase and operations by year. How the design fee credits into a later build is written into the design contract.
Where to next
Trust & compliance
Deployment models, data sovereignty, security operations, supply-chain screening and use limits, in one place.
Intelligence & awareness core
IOC awareness comes from the public-source intelligence network. See how the data is organised.
Hazard & public safety warning
Emergency is the IOC first high-frequency use case. Start by connecting warning.
Start with a current-state inventory
Send the city scale, the current system list and the two use cases that matter most. The reply covers an architecture outline and phasing.
