Home / CPHEEO / Chapter 1
CHAPTER 1

Introduction and Design Considerations for Urban Drainage

Design Philosophy & Return Periods

Establishes the framework for designing urban storm water drainage systems — design return periods by land use, design philosophy (separate vs combined), planning horizon, climate-resilient sizing, integration with sewerage and SUDS. Covers institutional framework (ULB, AMRUT 2.0, Smart Cities Mission) and outlines the difference between conveyance-based and source-control approaches.

📋 Planning & Design ConsiderationsManual on Storm Water Drainage Systems1st Edition (2019), with AMRUT 2.0 + Smart Cities Mission updates referenced

Key formulas

  • Design Discharge Q (m³/s) = C × i × A / 360 (Rational Method, A in hectares, i in mm/hr)
  • Allowable risk of failure = 1 − (1 − 1/T)^n where T = return period (years), n = design life
  • Overland time + Pipe time = Time of concentration tc
  • Climate change adjustment factor: 1.10–1.30 multiplier on design rainfall (per Smart Cities CSR 2.0)
  • Combined sewer overflow (CSO) trigger = 3-6× dry weather flow

Key values & thresholds

return period residential
2-5 years
return period commercial business
5-10 years
return period arterial road
10-25 years
return period critical infra
50-100 years (hospitals, metro, power)
return period underpass
25-50 years
design life main drains
30-50 years
design life inlets appurtenances
15-25 years
climate adjustment factor
1.10 to 1.30 on design intensity
min separation from water main
300 mm vertical, 600 mm horizontal
ulb drainage responsibility
Master plan + design + O&M; AMRUT 2.0 funded

Clause-level requirements

  • Separate storm water drainage is the preferred approach for new towns + extensions; combined sewers acceptable only where retrofit cost is prohibitive.
  • Return period must reflect consequences of flooding — life safety > property damage > inconvenience.
  • Design rainfall must include a climate-change uplift factor of 10-30 % on historical IDF curves.
  • All storm water designs must be coordinated with the city sewerage master plan + road geometric design + sanitary drainage.
  • Source-control measures (SUDS, rainwater harvesting) shall be explored before sizing conveyance for the full peak.
  • Drainage districts shall be delineated based on natural catchments, not administrative boundaries.

Practitioner notes — what goes wrong in the field

  • Most Indian cities still operate combined sewers in older cores (Delhi, Mumbai, Kolkata) — separation projects under AMRUT 2.0 are slow + expensive (₹3-8 crore/km).
  • For master planning, divide city into 10-50 ha drainage districts and design network bottom-up from each district outfall.
  • If you have only 5-10 years of rainfall data for a city, supplement with regional IDF + apply higher climate uplift (1.25-1.30).
  • Detention storage typically reduces required pipe diameter by 30-50 % — always evaluate before sizing for full peak.
  • Check intersection of storm sewer with water mains and sewer mains BEFORE finalising vertical alignment — 300 mm vertical separation minimum.
  • Critical underpasses (railway, metro) need 25-50 yr design + dedicated pump station + standby genset + level alarm to traffic management.
  • Plan O&M access (manholes every 30 m for ≤ 600 mm dia; every 60 m for > 600 mm dia) at design stage; retrofit is brutal.
  • AMRUT 2.0 demands GIS-based drainage master plan as deliverable — budget for hydraulic model (SWMM, MIKE URBAN, or similar).
  • For coastal cities, account for tidal lock at outfalls — design HTL + 0.5 m freeboard for outfall invert.
  • Storm water must NOT discharge into sanitary sewer (causes treatment plant overload + CSO). Separate to outfall.

FAQs

What return period should I use for storm water drainage in an Indian city?
2-5 years for residential, 5-10 years for commercial/business areas, 10-25 years for arterial roads, 25-50 years for underpasses, 50-100 years for critical infrastructure (hospitals, metro). Increase by climate-uplift factor of 1.10-1.30 per AMRUT 2.0 / Smart Cities guidance.
Should I design separate or combined sewers?
Separate is mandatory for new development per CPHEEO 2019. Combined is grandfathered only where retrofit is economically infeasible — and even then, AMRUT 2.0 funds gradual separation. CSO controls (storage, screening, disinfection) required where combined remains.
What's the climate change uplift factor?
10-30 % multiplier on historic design rainfall intensity. Lower end for inland cities with stable rainfall trends; higher end for coastal + cyclone-prone (Mumbai, Chennai, Bhubaneswar, Visakhapatnam).
Is SUDS mandatory in India?
Recommended (not yet mandatory) per CPHEEO 2019 + Smart Cities Mission. AMRUT 2.0 incentivises permeable paving, rain gardens, bioswales, green roofs in city plans. Mandatory for buildings > 300 m² per most municipal building bye-laws (rainwater harvesting).
Who is responsible for storm water drainage in India?
Urban Local Body (ULB) — municipal corporation, council, or nagar palika. State PWD typically handles arterial road drains. AMRUT 2.0 funds capex for state-approved master plans; O&M is ULB responsibility.

Cross-references

IS 1742:1983 (drainage building)IS 12251:1987 (surface drains)IRC SP 50:2013 (urban drainage)AMRUT 2.0 Operational Guidelines (MoHUA 2021)NDMA Urban Flooding Guidelines (2010)Smart Cities Mission strategic plan

Tags

design return periodurban drainage philosophyAMRUT 2.0climate adaptationseparate vs combined sewerdrainage districtsmart cities drainagedesign lifeconsequence-based design

Engineer's notes

Storm water drainage is one of the most under-invested municipal services in Indian cities — and one of the most visible when it fails. Every monsoon brings news of waterlogged underpasses, marooned colonies, and traffic chaos. The CPHEEO Manual on Storm Water Drainage Systems (2019, the first dedicated edition) finally gave engineers a unified design framework after decades of mixing IRC SP 50, IS codes, and ad-hoc municipal practice.

The core design decision is the return period — how often the system is allowed to be overwhelmed. A 2-year design accepts overflow every monsoon for residential streets where flooding is inconvenient but not catastrophic; a 100-year design protects underpasses, hospitals, and substations where failure costs lives or critical service. Pick the return period before you size anything — overdesigning a residential drain wastes ₹crores; underdesigning a metro underpass kills people.

The separate vs combined debate is largely settled in CPHEEO 2019 — separate is the future. Combined sewers were a 19th-century convenience that became a 21st-century liability: they overwhelm sewage treatment plants in monsoon, cause combined sewer overflows that pollute receiving waters, and complicate O&M. AMRUT 2.0 explicitly funds separation in legacy areas, though the ₹3-8 crore/km cost means it'll take decades.

Climate uplift is the new normal. Cities that historically saw 50-60 mm/hr peak intensities now record 80-120 mm/hr events almost every monsoon. Designing to 1980s IDF curves is professional negligence in 2026 — apply at least 10 % uplift, more for coastal/cyclone zones. The CPHEEO 2019 manual is explicit on this; AMRUT 2.0 reinforces it.

Where this chapter sits: it's the first decision in any drainage project — return period × climate uplift × separation philosophy define the entire downstream design. Get this wrong and no amount of clever hydraulic detail saves you.

Download full manual from MoHUA →
Manual on Storm Water Drainage Systems · 1st Edition (2019), with AMRUT 2.0 + Smart Cities Mission updates referenced · Central Public Health and Environmental Engineering Organisation (CPHEEO), Ministry of Housing and Urban Affairs, Government of India.
InfraLens provides chapter summaries for search — full manual is the authoritative reference.