Digital infrastructure
Why digital is the one layer that crosses all six, how ducts, backbone and data centres are delivered through a company of their own at the sector-delivery layer like any other asset, and why the data and the integration layer stay with the city's own entities.
Overview
Digital infrastructure is treated as a layer that crosses the whole structure rather than as one sector among ten, because every other sector depends on it. Ducts belong in the street before it is surfaced. Meters belong in the water network as it is laid. Signalling and fare collection are part of a transport system, not an addition to it. Procured sector by sector, these arrive as a collection of systems that cannot exchange data; planned as a layer, they arrive as one.
The categories above are described in general terms deliberately. What a given programme actually includes — how much connectivity, whether a data centre is warranted, which administrative services are in scope — depends on the host jurisdiction, its existing capability and its own priorities. Those are matters for the host state to determine, and the sector is presented here as a field of work rather than as a list of systems.
The structural question is ownership. A platform holds the registries, identity records and operating data a city needs for decades, while the companies that build and run software change on much shorter cycles. The arrangement therefore keeps the data and the integration layer with the city’s own entities, defines interfaces and exit terms at the outset, and treats long-term interoperability as a condition of entry rather than a feature to be negotiated later.
Schematic
The parts and how they connect
- 01Duct bank, backbone and chambers
- 02Access nodes and connections to premises
- 03Data centre and its rack rows
- 04Exchange and interconnection points
- 05Shared platform and digital public services
- From the data centre through the exchange to a public service
What this covers
Scope of work in digital infrastructure
- Connectivity: fibre backbone and ducts laid with the street network, fixed access and mobile infrastructure
- Data centres and edge facilities, together with the power, cooling and water they require
- Shared city platforms: the common data layer, identity and integration services on which sector systems run
- Digital public services as a category of work: administrative registries, licensing and service channels, and public revenue systems
- Interoperability and data standards written into the development framework, so that later systems can connect to earlier ones
- Network and information security, and the operating arrangements that keep systems available
In the structure
How the sector is held
Digital is the one crosscutting layer: it runs vertically through all six. Standards and data rules are set at layers 1 and 3, in the enabling framework and the development standards, because they have to exist before any sector procures a system. Physical assets — ducts, backbone, data centres — are delivered through a special-purpose company at layer 4 like any other infrastructure. Platforms and services are operated at layer 6, alongside the utilities and city services they support. The practical consequence is that a duct is laid once, with the road, rather than three times by three sectors.
Partners and capital
How partners and capital enter
Specialist technology partners enter at the level of an individual vehicle or service, under terms that separate the supply of a system from the ownership of what runs through it. The structure is drafted so that data, identity records and the integration layer remain with the city's own entities, with export formats, interface specifications and exit obligations stated in the contract rather than discovered at renewal. Connectivity and data-centre assets are assessed by financiers much like other infrastructure; platform and service work is shorter-dated and usually contracted rather than project-financed, and the structure keeps the two apart.
Crosscutting
Sustainability and resilience in digital infrastructure
Data centres are among the most energy- and water-intensive assets a city can host, so siting, cooling choice, grid capacity and the reuse of waste heat are settled with the energy and water sectors at planning stage, not left to the operator. In the other direction, the digital layer is what makes demand management possible elsewhere: metering, load and traffic data are the precondition for reducing consumption in water, energy and transport. Standards favour open interfaces and long service life over replacement cycles, and the same environmental and social standards applied by development finance institutions govern facility siting and community impact.
Related