Sustainability and Innovation

Water, sustainability, and context

Water is indispensable to life, but its sustainability significance extends beyond drinking, cooking, and crops. It shapes culture (rain songs, Holi, Chhath, and Kumbh), food, clothing, power generation, mobile phones, and the internet. Although about $74\%$ of Earth’s surface is water-covered and water continually cycles through the planet, usable water services depend on where, when, and how water is managed.

Availability is not service delivery

Growing up in Bharatpur, Rajasthan ($800$ mm average rainfall), households carried buckets upstairs repeatedly each day; in Bikaner ($300$ mm), supply was regular enough to fill first-floor tanks. The lesson is fundamental: resource availability and resource management are different problems. More rainfall does not automatically produce better water service.

A water crisis is therefore not only shortage; it can also be flooding, and climate change is making rainfall more concentrated in intense downpours. The appropriate storage response—more structures, fewer structures, or larger structures—must be assessed locally.

Here, $1\ \text{m}^3 = 1000$ litres. Local research and local translation are therefore prerequisites for useful innovation—not an afterthought.

Efficiency, augmentation, and the hidden water footprint

Water sustainability requires both increasing effective supply and reducing waste:

• China reportedly grows about $3$ kg of rice with the water used elsewhere for about $1$ kg: an illustration of the potential value of water-use efficiency.
• Air-to-water technologies condense atmospheric moisture, much like water dripping from an air-conditioner pipe. They may augment supply where context makes them sensible.
• Producing a typical meal takes roughly $2000$ litres of water. Food waste is therefore also water waste.

Exam tip: Do not treat a technology as universally transferable. The $11{,}000$ mm versus $250$ mm rainfall contrast is evidence for context-specific design.

Key takeaways

• Water sustains ecological, economic, social, and cultural systems.
• Availability, timing, distribution, and management jointly determine water security.
• Flooding as well as shortage can be a water crisis.
• Efficiency and demand reduction matter alongside supply augmentation.

Classifying water bodies

The same water body can fall into several classifications at once; these are complementary lenses rather than mutually exclusive categories.

Groundwater is not simply “water below ground”: rain percolates through soil and is stored according to the underlying rock formation. Taps, handpumps, and tubewells are equipment at the end of a supply line, not automatically the ultimate source. Water users should know the source supplying their home, school, or workplace.

Monsoon seasonality creates a storage imperative

Much of India receives annual rainfall in only about $100$–$120$ days—chaumasa, the roughly four-month rainy period. If a household earned its entire annual income during those days, it would need to save and spread the money across the remaining $265$ days. Water needs the same treatment.

Traditional bawris, man-made lakes, and tankas embody this logic. South Asia can consequently be understood as a storage civilization: the monsoon pattern makes storage central to year-round water security.

Distinguishing shortage, scarcity, and stress

These terms are often used loosely, but they refer to different diagnoses.

At roughly $1400\ \text{m}^3$ per person per year, India is water-stressed, while some locations are water-scarce. Demand-driven stress arises when growing demand—for example from urbanisation or industry—outpaces supply.

A water-rich planet with little directly usable water

The apparent abundance of water conceals a severe availability constraint:

$$97.5\%\ \text{saline water} \quad\rightarrow\quad 2.5\%\ \text{fresh water} \quad\rightarrow\quad <1\%\ \text{free-flowing, accessible fresh water}$$

Most fresh water is locked in glaciers and icecaps. Ocean water cannot be consumed directly and is unsuitable for most agricultural and industrial uses. Geographic variation, seasonal rainfall, and the small accessible share explain why scarcity can coexist with a water-covered planet.

Key takeaways

• Classify water by ownership, salinity, location, origin, and flow; categories can overlap.
• Monsoon concentration makes storage indispensable.
• Shortage is individual-level, scarcity is source-versus-demand, and stress signals depletion risk.
• Only a very small fraction of total planetary water is accessible fresh water.

Where water is used

The precise shares vary with the denominator used (for example, whether rainfall or only surface and groundwater is counted), but the broad pattern is clear.

India’s supply norms are about $135$ litres per capita per day (LPCD) in urban areas and $55$ LPCD under the rural Jal Jeevan Mission goal. The difference invites scrutiny: it should not be accepted as proof that rural people need less water.

Within agriculture, rice, sugarcane, wheat, and cotton together use almost $90\%$ of annual irrigation water. The water question is therefore not only about reducing consumption or exports, but also about crop choice and productivity. The shift from jowar, ragi, and bajra toward wheat and rice has water implications. The terms blue water, green water, and grey water identify further ways of thinking about water use. Artificial intelligence also has a substantial water footprint that merits attention.

Exam tip: Household savings are valuable, but agriculture’s roughly $91\%$ share means agricultural efficiency and crop choice have the largest system-level leverage.

Water is also a gender and equality issue

Water practices structure daily life and opportunity. Around 2018, about $42\%$ of rural Indian women reportedly walked at least $500$ metres to fetch water daily. This affects women’s labour, girls’ education, and gender equality. A drinking-water intervention that leaves people walking for bathing, cleaning, and other daily needs has not eliminated the underlying drudgery.

Water quality is fit-for-purpose

Water quality must be assessed relative to its intended use. Drinking water requires stricter quality than water for bathing or watering plants. Water changes form rather than disappearing, which makes reuse possible, but only when quality is appropriate to its next use. Poor drinking-water quality causes waterborne disease, including cholera and typhoid; illness can be fatal, especially for young children. Improvements associated with Swachh Bharat Mission and Jal Jeevan Mission have reduced this burden.

The 1854 investigation in which John Snow traced cholera to water is a foundational episode in epidemiology.

Smell, taste, and colour are common screening tools but are highly inadequate. Household supply should meet Indian Standard IS 10500, though routine local testing cannot be assumed.

How surface water becomes contaminated

1. Poor sanitation can compromise ponds and other surface waters.
2. Untreated industrial effluent harms people and aquatic life.
3. Agricultural runoff is a decentralised source of pollution: in some places fertiliser application is reported at $4$–$6$ times what is required. Rain carries excess nutrients to water bodies, contributing to algal blooms.

NABL-accredited laboratories conduct testing; the Central Pollution Control Board (CPCB) and state pollution control boards regulate pollution. An important governance question is whether these institutions adequately monitor village ponds and agricultural contamination.

Water testing and treatment are growing business opportunities, but there is no universal treatment: arsenic removal, fluoride removal, and bacteriological treatment require different technologies.

Key takeaways

• Agriculture dominates water use; crop choice and efficiency are strategic sustainability choices.
• Water access affects gender equality, education, and the burden of unpaid work.
• Quality is use-dependent; sensory checks do not establish safety.
• Pathogenic and geogenic contaminants differ in source, time-to-harm, and treatment.

Sarvajal: decentralised safe-water service and governance

Sarvajal (“water for all”) sought to reduce disease burden by supplying safe drinking water of packaged-water quality that was affordable, accessible, and financially self-sustaining. The target setting included Jhunjhunu in Rajasthan’s Shekhawati region, where groundwater fluoride was far above permissible levels and a survey suggested that about half of doctor visits were related to waterborne disease. In 2008–09, about $160$ million people in India were estimated to face water-quality risk; India’s diarrhoeal-death burden was compared with countries such as Angola, Vanuatu, and Afghanistan. Nearly two-thirds of India lacks a perennial river, leaving groundwater as the dependable source for many drinking-water solutions. Sarvajal sought locations where the alternative water quality was around $1500$–$2000$ ppm, compared with a WHO-recommended level of about $150$ ppm.

Why a community-scale service model?

Water must be transported in liquid form; it cannot be “powdered” for transport. Moving it by pipes and pumps is generally cheaper than by tanker, while transport remains energy-intensive.

Sarvajal instead installed a decentralised, community-level purifier, typically for a settlement with roughly $1000$–$2000$ households. It converted a product into a pay-per-use service, analogous to buying a ride rather than a car: users paid a tiny amount for safe water rather than buying a purifier. The operating model needed a suitable source, power, sufficient throughput, a local entrepreneur, affordable pricing, remote monitoring, and technology flexibility so the treatment could match nitrate, fluoride, or bacteriological contamination.

Economics, quality assurance, and aligned incentives

Selling water at about $25$ paise per litre required volume. In early adoption, roughly $20\%$ of a community could be expected to buy the service; a village of $1000+$ households (about $5000$ people) could yield about $200$ daily-buying households, above an approximate break-even of $125$. Demand also varied by season: a five-person household might buy a $20$-litre container daily in summer but once every two days in winter.

Early machines were foundation-funded because entrepreneurs would not initially take the risk. Once revenue was proven, franchisees could buy the machine and retain more revenue: at $25$ paise per litre, Sarvajal’s share was $10$ paise; when the price later became $30$ paise and the franchisee owned the machine, its share fell to $20\%$, or $6$ paise per litre.

Community-scale purification is also more water-efficient than household RO: approximately one glass was rejected for every eight glasses produced, versus about one rejected for every glass produced by a small household purifier. However, franchisees may be tempted to raise price or compromise quality. Revenue sharing, quality assurance, information from source to service, and reliable repair capacity align business viability with wider coverage of safe water.

Value chain and differentiated models

A purifier, operator, and remote-sensing black box form the core value chain. The black box records membrane pressure, pump RPM, power consumption, TDS, UV status, and other process data, enabling scheduled, proactive, and breakdown maintenance. Water may be fetched at the machine, delivered by franchisee vehicle, or collected from a $24\times7$ water ATM.

In the 2011 census, only about $25{,}000$ of India’s roughly $650{,}000$ villages were A-sized, while about $393{,}000$ had fewer than $1000$ people. This makes one rural business model untenable. The 2013 CSR law made CAPEX support especially relevant for B-category villages. Sarvajal also contributed its decentralised-water experience to design discussions during the year-long experiment preceding Jal Jeevan Mission. Its own service addressed drinking water, not the broader household-water drudgery that piped supply can address.

Exam tip: Category B needs a one-time/temporary CAPEX bridge; Category C needs ongoing support. Do not treat “rural India” as one homogeneous market.

Hub-and-spoke, information layering, and resilient design

In dense slums, one borewell may serve a population of roughly $10{,}000$, while limited space makes a purifier at every point impossible. A central hub purifies water and a vehicle with a no-touch transfer mechanism refills distributed ATM spokes. Sensors can notify a driver, for example when a $1000$-litre ATM falls to $100$ litres; the system maintained timely refills.

Soochak was Sarvajal’s 2009 remote-monitoring system, created before “IoT” was common terminology and patented in the US for centralised management of distributed operations. It initially monitored machine health, while ATMs added last-mile quantity and quality assurance. This source-to-service information layering makes performance, payment, consumption, and maintenance visible.

Design choices were social as well as technical:

• Solar-powered, $24\times7$ ATMs let workers collect drinking water outside shop and tanker hours.
• A card interface eliminated touch: the user shows the card to start and again to stop. Earlier models had $5$-, $10$-, and $20$-litre buttons; later versions had none.
• Coin interfaces in Bhubaneswar served passers-by wanting one litre and, based on coin collection estimates, avoided tonnes of plastic-bottle waste.
• Accessible, simple interfaces allow children and people with physical disabilities to use the service.

Reliable assurance can change behaviour: orderly queues at ATMs contrasted with conflict around tanker supply. The point is not that communities are inherently disorderly, but that dependable, dignified systems reduce fear of missing out.

Evidence from disruptions

Key takeaways

• Sarvajal made purified water a decentralised, pay-per-use service rather than a household product.
• Viability depends on settlement size, adoption, seasonality, and the CAPEX/OPEX mix.
• Technology must be contaminant-specific, while the operating model can remain treatment-technology agnostic.
• Information layering, off-grid ATMs, and no-touch design improve reliability, resilience, and dignity.

Water ethics and collective action

Water is a rival resource: the water used by one person, farm, or industry is unavailable to another. Education contrasts with it: when two students listen to the same teacher, one student’s learning does not diminish the other’s. Water’s benefits are also immediate, measurable, and monetisable, increasing the scope for contestation among farmers, fisherfolk, rural users, and urban users.

Formal institutions alone do not create cooperation. Opinion leaders can mobilise sections of a village; neighbouring villages can experience sharply different outcomes. With household taps, people may become service consumers rather than collective custodians, so governance of common sources remains important.

Exam tip: Water’s rivalry explains both higher conflict and the greater need for collective action. Collective action must be built; it is not automatic.

From traditional knowledge to an ecosystem approach

Anupam Mishra’s The Radiant Raindrops of Rajasthan highlights traditional water practices, including the claim that Jaisalmer was a net wheat exporter until the late eighteenth century despite little change in monsoon. This encourages learning from civilisational water knowledge, not only contemporary technology. Tushar Shah and Brahma Chellaney influenced systems-level thinking; experience at Pratham with Madhav and Rukmini reinforced scale, trust, and team-building.

Founded around 2001–02 by Rohini Nilekani, Arghyam—a word associated with “giving water forward”—evolved into a water-focused organisation after an initial broader exploration. For roughly its first $8$–$10$ years, it supported participatory organisations, took risks, and accepted failure. It then became an ecosystem builder: connecting work on water quality, conservation, community mobilisation, measurement, markets, and government engagement.

In the 2005–07 period, the India Water Portal became an early open digital knowledge repository for NGO work, IMD data, and sector information. Arghyam has supported roughly $140$ projects, $100+$ partners, and work across $22$ states; direct funded projects are estimated to have reached $6$–$7$ million people. India Water Portal’s annual peak was about $3$ million hits, with more recent traffic around $1$ million as content consumption changes.

Samaaj, Sarkaar, Bazaar—and why government matters

The Samaaj–Sarkaar–Bazaar frame treats society, government, and markets as complementary forces; society creates the latter two to serve itself. Philanthropic and CSR resources are small relative to government development spending—described as roughly $100$ times larger. Government must pursue equity and reach every citizen, but its scale can make experimentation difficult. Innovation is therefore most powerful when civil society/business proves an approach and government adapts it for population-scale delivery.

Digital tools support this transition when data is a by-product of service design: they can improve visibility of intended actions, delivery, outcomes, planning, coordination, transparency, and accountability; reduce rent-seeking and corruption; and enable communities to make scientifically informed decisions without a separate supervision bureaucracy.

Businesses are not uniformly anti-sustainability. Their potential contributions include daily service delivery, efficiency, risk-taking, innovation, technology investment, measurement, networks, long-term strategic thinking, and access to capital. A social enterprise can make outcomes visible through input, process, and output metrics. For adoption and support, solving a problem $90\%$ well in $10$ places may be more useful than solving it perfectly in one place.

For personal and professional development: read widely, develop listening as a practical skill (to users and stakeholders as well as peers), protect time and attention from endless digital distraction, stay healthy, and experiment. Academic performance alone is no longer the only route to a rounded, useful career.

Key takeaways

• Water governance must handle rivalry, inequality, and conflicting legitimate uses.
• Traditional systems offer technical and social knowledge, but collective action needs active stewardship.
• Arghyam moved from participatory grant-making toward ecosystem building and digital, government-enabled scale.
• Social impact at scale combines community knowledge, government capacity, business capabilities, and measurable evidence.

Digital Public Infrastructure: removing friction at population scale

Digital Public Infrastructure (DPI) is an approach to solving socioeconomic problems at scale through minimal, reusable technology building blocks, public–private governance, and market innovation. Intuitively, it is a set of open, interoperable, population-scale digital rails—like roads or power lines: public by design, private by innovation.

The before-and-after case for DPI

This friction imposed time, waste, and exclusion; as late as 2014, only about $35\%$ of people had a formal bank account. Digital payments also produce a ledger and credit trail that can support a small merchant’s microloan application.

Three foundational rails and the India Stack

The paperless layer—e-Sign and DigiLocker—sits between identity and payment, enabling tamper-proof digital documents to be shared in one click. Together, the four layers are India Stack: identity, documents, payments, and data control.

India’s scale illustrates the reach of these public rails: about $1.3$ billion Aadhaar IDs, more than $2$ billion authentications per month, and over $17$ billion UPI payments per month; Brazil’s Pix was described as the next-largest at just over $6$ billion payments per month.

Exam tip: Remember both versions of the framework: three foundational capabilities (identity, money, consented data) and four India Stack layers (presence-less, paperless, cashless, consent).

What turns rails into public value?

1. Policy and governance: privacy rules, data-fiduciary duties, strong cybersecurity, and agile regulation form the trust architecture.
2. Ecosystem building: government lays core rails; industry builds services; civil society protects equity. Hackathons, grants, documentation, first-mile digital literacy, affordable devices, and dependable connectivity broaden participation.
3. Innovation on the rails: zero or very low API fees lower the barrier to start-ups. Payment trails can enable nano-credit, portable health records can support telemedicine, and IoT-linked water stacks can support pay-as-you-go irrigation.

Key takeaways

• DPI collapses weeks of documentary friction into seconds of inclusion.
• India Stack combines presence-less identity, paperless documents, cashless payments, and consent-led data sharing.
• Technology alone is insufficient: public value requires policy, ecosystem capacity, and innovation.

Participation is more than technology adoption

Technology use has expanded, but ordinary people remain under-involved as contributors and decision-makers. Open governance means making data and decision-making more accessible and inclusive. When government releases open data, communities can use it to inform decisions in their own wards, towns, and local institutions.

The e-Governance Foundation began by helping governments improve municipal service delivery rather than merely demanding better service. Its trajectory shows three necessary perspectives: improve the supply side with government; understand the demand side—what citizens want; then work at their intersection with civil society and government together.

Arghyam’s 2018 pivot followed a recognition that the water problem was outpacing grant-based efforts. Its three linked commitments became: leverage technology, work with government for saturation and scale, and retain participatory governance roots. Meghalaya demonstrated Samaaj, Sarkaar, Bazaar working together.

CLART: bringing hydrology science to community planning

CLART, developed by the Foundation for Ecological Security (FES), simplifies hydrology expertise that would normally require a professional with $10$–$15$ years’ experience. Its roughly $8$–$10$ layers help a smartphone-using villager distinguish recharge areas from water-retention areas and choose appropriate structures.

In Meghalaya, a state that faces seasonal water problems even though it includes very wet areas such as Sohra/Cherrapunji, government functionaries and community members were trained to use CLART in NREGA planning. In about $18$ months, more than $6000$ community-participatory plans were made across roughly $6500$ areas.

The gain was not simply more plans. An engineer can prepare top-down plans more quickly from an office, but these may have little local buy-in. Community-made, science-based plans are more likely to locate structures appropriately, last longer, and be maintained.

Capacity and civic muscle

The ECHO model treats training as the start of capacity-building, not its endpoint. Instead of ending with a cascade from master trainer to field staff, it forms a community of practice where people facing field problems share attempts, receive expert support, and collectively improve solutions.

In Goa, long-term partner InRe used an open-source chatbot platform to nudge students to act on water-quality issues. In around a year, more than $40{,}000$ students were trained and more than $2$ lakh actions taken. Data fed back into service delivery, and school committees engaged with local problems. The model was being replicated by government; exposure builds civic muscle—the habit and capacity of participating as a citizen.

For young people, the implication is twofold: engage with local data and local problems as citizens, and bring technology, policy, or management skills into the social sector early enough to build grounded understanding. DPI handles shared “plumbing,” leaving innovators to add value in agriculture, health, education, water, and less-attended sectors.

Key takeaways

• Inclusive governance needs citizen participation as well as improved government systems.
• CLART turns specialist hydrology knowledge into community-useful planning capability.
• Capacity lasts when training becomes an ongoing community of practice.
• Chatbots and open platforms can create civic participation while improving water-quality outcomes.

DPG versus DPI

A digital public good (DPG) is a value-based category of digital artefact—software, data, standards, specifications, or content—that is open, available, extensible, non-rival, and non-excludable in the relevant sense. “Free” software does not mean all use is costless: users may still need a device, electricity, internet, and operating capability. Linux is a useful open building-block example; Google Maps, although widely usable at no direct charge, is proprietary and therefore not a DPG.

DPI is purpose-driven: it solves a large-scale socioeconomic problem with minimal reusable building blocks. A DPI may combine DPG components with proprietary software. DPGs are often the reusable “bricks”; DPI is the system or platform assembled to solve a public problem.

The people layer of public digital value

Community-driven platforms are bottom-up infrastructure that contributes lived data, local knowledge, and contextual maps that formal systems miss.

Examples include Gram Vaani (local-language news and grievances by phone), Digital Green (farmer-made how-to videos), and OpenAQ (open PM2.5 data).

Wikipedia: an open knowledge commons

Wikipedia is a free encyclopedia anyone can edit. It has about $6.8$ million English-language articles and content in more than $300$ languages. Reliability rests on verifiability: volunteer administrators enforce cited sources, edits are logged, and changes remain traceable. Local-language editions such as Odia and Santali improve inclusion. At roughly $90$ billion page views a year, it supplies a vast open knowledge base used by learners, media, and AI systems.

OpenStreetMap: a people’s map

OpenStreetMap (OSM) is a free, editable map created by volunteers using laptops, smartphones, or GPS devices. Roads, footpaths, kiosks, and local features can be added and published live under an open licence. During the 2015 Nepal earthquake and 2018 Kerala floods, missing roads were mapped within hours to guide relief. Mapbox, Facebook, and Grab reuse the base map; rural paths, Dharavi alleys, and wheelchair-friendly ramps may appear there before proprietary maps.

Generative AI: accelerator and landmine

The response is to pair speed with safeguards: clear attribution, limits on bot uploads, misinformation filters, and renewed community rituals that keep humans engaged.

Exam tip: Open licences and code alone do not make a commons durable. Transparent peer governance and sustained human motivation are equally necessary.

Key takeaways

• DPG is defined by openness and reusability; DPI is defined by problem-solving purpose at scale.
• Community platforms add contextual “people-layer” data to public digital value.
• Wikipedia and OSM demonstrate open contribution, transparent history, and peer governance at scale.
• AI can increase output but can also erode quality, attribution, and participation.

Sectoral DPIs and the Water Stack

Sectoral DPI combines foundational rails—identity, payments, and consented data exchange—with domain-specific registries, standards, and APIs. Foundational rails make inclusion possible; sectoral rails make it practical, granular, and action-ready.

Why water needs a stack

India’s water landscape is fragmented across more than $18$ ministries, state departments, and local institutions. Siloed IT systems, paper records, and conflicting numbers lead to duplicated data, stalled decisions, and mismatches such as overdrawn aquifers beside tanker delivery. A Water Stack provides a common structured grid.

Each new sensor or data source should create a network effect: it adds value to all participants rather than only one dashboard. Sectoral infrastructure lets innovators focus on value creation rather than rebuilding the plumbing.

Key takeaways

• Sectoral DPIs add domain registries, standards, and APIs to foundational digital rails.
• Agri and health stacks illustrate how shared infrastructure reduces friction in specialised workflows.
• The Water Stack addresses fragmentation through registries, standards, shared utilities, and an innovation layer.
• Public rails are bigger than individual apps: shared, trustworthy infrastructure enables inclusive growth.