CITIES & INFRASTRUCTURE SYSTEM 29 OF 58

Infrastructure Failure Database

Turn every failure into root-cause evidence and reusable learning.

01 · PLACE

Define the settlement, network, corridor or asset before diagnosing it.

Record India → State/UT → District → City/Block → Village/Ward → Street/asset only to the resolution supported by evidence. Include boundary version, coordinates at a privacy-safe precision, urban/rural classification, date, season, land context, affected population, operator and linked infrastructure.

Local context gate

A photo proves an observed condition at a time and place; it does not by itself prove scale, cause or responsibility. Preserve original date and location evidence, consent and redaction.

02 · PROBLEM

Describe the failed outcome—not just the missing project.

Failures repeat when reports stop at the visible defect and do not connect design, procurement, operation and maintenance causes.

Quantify who or what is affected, frequency, duration, severity, service standard, safety consequence, household or business cost, environmental effect and whether the failure is chronic, seasonal or event-driven.

03 · ROOT CAUSES

Test land, design, capacity, operations, finance and governance together.

01Fragmented infrastructure failure database responsibilities, records and standards

Check records, field condition, interviews and competing explanations before confirming this cause.

02Capital delivery is measured more often than service quality, inclusion and lifecycle condition

Check records, field condition, interviews and competing explanations before confirming this cause.

03Local land, demand, climate, finance and operating capacity are insufficiently tested

Check records, field condition, interviews and competing explanations before confirming this cause.

Separate the visible trigger from the underlying system: rain may trigger flooding, but undersized drains, paved catchments, encroachment, blocked outlets, wetland loss or unsafe land use may determine the result.

04 · EVIDENCE

Build a traceable decision record.

QuestionMinimum evidence

Where and when?Boundary/resolution, coordinates, date, season and duration

What failed?Asset or service, standard, unit, frequency and severity

Who is affected?Population, vulnerability, household/business and distribution

Why?Inspection, capacity, flow, maintenance, land and competing causes

What exists now?Owner, project, budget, contractor, condition and grievance history

Did action work?Baseline, target, actual, cost, reliability, equity and harm

Project sanctioned ≠ project completed. Asset completed ≠ service reliable. Service coverage ≠ safe and affordable outcome.

05 · COMPLETE SYSTEM

What must function as one chain.

01Collapse, damage and defects

Define demand, capacity, design standard, asset, operating owner, finance, maintenance, monitoring, risk and public accountability.

02Leakage, overflow and service loss

Define demand, capacity, design standard, asset, operating owner, finance, maintenance, monitoring, risk and public accountability.

03Delay, cost overrun and under-use

Define demand, capacity, design standard, asset, operating owner, finance, maintenance, monitoring, risk and public accountability.

04Repeated repair and maintenance failure

Define demand, capacity, design standard, asset, operating owner, finance, maintenance, monitoring, risk and public accountability.

06 · INDIA-FIT SOLUTIONS

Compare protection, repair, upgrade and structural reform.

Record failure, evidence, root cause, current response, better option, pilot, KPI, review and repeat-risk decision.

BOUNDED PILOT

Select one ward, corridor or settlement; verify the baseline, compare alternatives, assign an operating owner and publish a time-bound before/after evaluation.

Pre-register baseline, comparison, intended users, technical and non-technical alternatives, procurement, full lifecycle cost, operations owner, safety and displacement safeguards, measurement period and stop/redesign conditions.

07 · ROADMAP

Move from immediate protection to durable capacity.

010–30 days

Protect people, verify the place and route urgent safety/service failure

0230–90 days

Inspect assets, establish baseline, causes, owners and alternatives

033–12 months

Pilot the selected repair, service or planning intervention

041–3 years

Evaluate reliability, affordability, access, safety and maintenance

053–5 years

Integrate networks, finance, workforce, standards and governance

065+ years

Renew or scale only after capacity, resilience and transfer review

08 · MEASURED RESULTS

Track the outcome residents and operators actually experience.

01Coverage with definitionBaseline → target → actual → confidence → decision

02Service quality and reliabilityBaseline → target → actual → confidence → decision

03Safety and inclusionBaseline → target → actual → confidence → decision

04Lifecycle cost and conditionBaseline → target → actual → confidence → decision

05Outcome, equity and durabilityBaseline → target → actual → confidence → decision

ScaleVerified benefit, affordable lifecycle, safe delivery and capable owner.ModifyUseful partial result but design, equity, cost or maintenance needs repair.StopNo credible benefit, unacceptable harm, repeated failure or stronger alternative.

09 · RISKS & SAFEGUARDS

Better infrastructure must not transfer cost or harm.

Prevent unsafe eviction, livelihood loss and exclusion
Audit accessibility, gendered safety and emergency access
Protect water, wetlands, farms, biodiversity and hazard buffers
Publish land, procurement, contractor, payment and conflict records
Budget operation, maintenance, renewal and end-of-life before construction
Protect citizen privacy; redact faces, homes and exact sensitive locations

← National Infrastructure Asset Registry All 58 systems Government Land & Urban Development →