Asset & Infrastructure Management

Everything starts with an honest answer to a deceptively hard question: what does the city own, where is it, and what do we know about it? For most cities the honest answer is 'we are not sure,' and that ignorance is expensive. Records are scattered across departments, held on paper or in incompatible systems, often wrong about buried infrastructure whose as-built location drifted from the drawing decades ago. You cannot maintain, budget for or protect what you cannot find.

An asset-management twin's first job is therefore to be a single, spatial, authoritative-enough register: each asset - a length of main, a bridge, a pump, a building - represented on the city model with a consistent set of attributes. Typical attributes include what it is and what it is made of, when it was installed and its expected life, its size and capacity, its current condition and its maintenance and failure history. Crucially, each asset sits in its real place and in relation to the others, so you can see a water main under the road you are about to dig up, or every asset in the ward about to flood.

This is where the twin connects to the rest of the course. The city model (Module 2) provides the geometry and the place; GIS and as-built data, BIM models of public buildings, and reality capture of what is actually there (Module 3) provide the content; and increasingly a public building handed over with a BIM model carries its asset data straight into facility management. But two honesty checks matter immediately. First, the register is only as good as the data poured into it - a twin full of wrong or missing asset records is worse than useless because it looks authoritative. Second, the authoritative record of legal ownership, boundaries and survey remains with the official custodians (including Survey of India) and the relevant authorities; the twin is an operational working register, not the legal record of title or cadastre. Built well, though, simply *knowing what you have and where* is already transformative - it is the foundation everything else in this lesson stands on, and many cities do not yet have it.

A register tells you what exists; condition monitoring tells you how it is doing. Assets age, wear and degrade, and the central question of asset management is knowing the state of each one well enough to act at the right time. The twin becomes the place where condition information lands and is seen in context.

Condition data comes from two broad sources. The first is inspection - people (or increasingly drones and imaging) examining assets on a schedule and recording a condition rating: the cracking and spalling of a bridge, the state of a road surface, the corrosion in a pump house. The twin holds these ratings against each asset and over time, so you can see not just today's condition but the *trajectory* - what is degrading fast and what is stable. The second is sensors: continuous or periodic instrumentation on selected assets - strain and vibration on a critical bridge, pressure and flow across the water network to localise leaks, vibration on major pumps, flood level in drains. This is the cyber-physical link (Module 1) applied to infrastructure: the physical asset's state streaming into its digital record.

The realism here matters enormously, and it echoes Lesson 7.1. You cannot and should not instrument everything - sensors cost money to install, power and maintain, and most assets will never carry one. So condition monitoring is overwhelmingly periodic inspection for the many, with continuous sensing reserved for the critical few whose failure would be catastrophic or expensive. Much of the condition data in any real asset twin is therefore months or years old, or estimated from age and type rather than measured - and, exactly as before, the twin must be honest about this, showing when each asset was last inspected and flagging stale or assumed condition rather than painting a confident colour over a guess. And the binding judgement - is this bridge safe, must this building be closed, what load can this structure carry - is a structural and engineering assessment made by qualified engineers under the applicable codes. The twin organises and surfaces the evidence; it does not certify that anything is safe.

Put a register and condition trajectories together and the twin can support the real prize: maintaining assets *at the right time*. It helps to see maintenance as a ladder of maturity. At the bottom is reactive maintenance - fix it when it breaks - which is how under-resourced cities mostly run, and which is the most expensive and disruptive way to operate: failures are sudden, collateral damage is high, and the burst main floods the street it was cheapest to have relined quietly last year. One rung up is preventive maintenance - servicing on a fixed schedule regardless of condition - which is better but wasteful, replacing things that had life left and occasionally still missing early failures. Higher still is condition-based maintenance - acting when monitoring shows an asset actually needs it. And at the top sits predictive maintenance - using condition trends, age, type, loading and failure history to estimate which assets are most likely to fail and when, so intervention is planned just ahead of failure.

A twin is a natural home for climbing this ladder, because it holds the register, the condition history and the spatial relationships in one place, and can rank assets by risk - combining likelihood of failure with the consequence of failure, so a deteriorating main under a hospital outranks the same main under a quiet lane. That risk-ranking is the genuinely useful output: not a crystal ball, but a defensible, transparent way to prioritise scarce maintenance budgets toward where they prevent the most harm.

The honesty, again, is essential. 'Predictive' is the most over-sold word in this field. A prediction of remaining life rests on data (often sparse) and models (often generic), and it carries real uncertainty; treating a predicted failure date as fact is its own kind of false confidence. Predictive maintenance is best understood as *informed prioritisation under uncertainty*, not prophecy. And the decision to close, repair or replace an asset - with its budget, safety and service consequences - is an engineering and management decision made by accountable people, informed by the twin's risk ranking but owned by them. Used this way, the twin's real gift is moving a city, asset by asset, from fixing what already broke toward tending what is about to.

Step back from the single asset and the twin supports lifecycle management: thinking about the whole life of the city's stock - from planning and construction through operation, maintenance and renewal to eventual replacement - and the long-run cost of keeping it all working. This is where asset management meets the hard economics of a city. Infrastructure has a huge, mostly invisible *maintenance backlog* - the accumulated deferred renewal of ageing networks - and the decisions are genuinely difficult: with a fixed budget, which of ten thousand ageing assets do you renew this year? A twin that holds condition, risk and cost across the whole estate can turn that from a political guess into a more transparent, evidence-based prioritisation, and can show the long-term consequence of under-investing (the backlog, and the failures, growing).

It also supports better whole-life decisions at the single-asset scale: is it cheaper over the asset's life to keep patching this road or to rebuild it; to refurbish this public building or replace it; to run this pump to failure or overhaul it now. Seeing capital and operating cost together, against condition and risk, is exactly what a good asset twin makes possible - and it connects directly to the sustainability questions of the next lesson, since the greenest asset is often the one you maintain rather than demolish and rebuild.

But the honest ledger cuts both ways, and this lesson must end where Module 9 will insist: an asset twin is itself an asset with a lifecycle and a cost. It must be populated (expensive), kept current (more expensive), and maintained as software and data forever, or it decays into exactly the kind of authoritative-looking, out-of-date register that is worse than none. Many asset twins are bought, populated once, admired, and abandoned - twin-washing in its most wasteful form, because the whole value of an asset register is that it is *current*. And throughout, the binding results stay put: condition and structural safety assessments with qualified engineers; official ownership, boundary and survey records with the legal custodians including Survey of India; budgets and statutory asset decisions with the accountable authorities. Any life expectancy, condition score, failure probability or cost in the twin is illustrative and context-dependent, a support to judgement, never a specification. The twin's real, sober promise is a city that knows what it has and tends it wisely - if, and only if, it keeps the register honest and alive.