Water Supply Engineering Bc Punmia Pdf 266 -

Three days later, water flowed for two hours. An old woman filled her matka and smiled at him. Arjun didn’t tell her about Hardy-Cross or iterative corrections. He just pointed to the repaired joint and said, “Page 266.”

And somewhere in the ghost of that textbook, B.C. Punmia’s equations did what they were meant to do: bring water to the thirsty, one node at a time.

Arjun grabbed his torch and a wrench. The night air was cool, smelling of dust and marigolds from the temple. He crawled under the concrete slab at Node 12. There it was: a longitudinal crack in the 150mm cast-iron pipe, half-hidden by a banyan root. Water wasn't gushing; it was weeping—twenty liters per minute, day and night, for maybe ten years. Enough to starve two thousand homes.

The pages of Dr. B.C. Punmia’s Water Supply Engineering were older than Arjun’s father. The PDF on his battered laptop, specifically page 266, was a ghost—scanned from a 1981 edition, complete with coffee stains and a handwritten note in the margin that said “Check Example 8.4, leak suspect.” water supply engineering bc punmia pdf 266

Arjun, a junior engineer in the arid district of Shekhawati, had been staring at that page for three hours. Page 266 contained the chapter on Design of Distribution Networks , specifically the Hardy-Cross method for balancing flow in looped pipes. But he wasn't solving a textbook problem. He was solving a crisis.

Punmia’s example 8.4 showed a classic case: a hidden leak in a secondary branch, impossible to find by listening, but mathematically obvious if you calculated the nodal residuals. The margin note— “leak suspect” —was from some long-dead student, but for Arjun, it was prophecy.

Two weeks ago, the ancient gravity-fed pipeline from the Bandi river had started losing pressure. The town of 40,000 received water for only twenty minutes every third day. The politicians blamed the drought. The villagers blamed Arjun. But page 266 had given him an idea. Three days later, water flowed for two hours

That morning, he had borrowed the only ultrasonic flow meter in the district and walked six kilometers of pipeline, recording data at every valve. Now, back in his office—a tin shed with a flickering tube light—he punched the numbers into a spreadsheet he’d built from Punmia’s iterative method.

The first iteration failed. Residuals scattered like frightened birds. The second, worse. By the fourth, a pattern emerged. Node 12, a junction near the old Hanuman temple, showed a correction term of +0.32 m³/hr—small but persistent. According to Punmia’s logic, that meant water was leaving the system there, not reaching the end users.

Back at his desk, he opened Punmia’s PDF again. Page 266, the same scan, the same coffee stain. He added his own margin note in his mind: “It’s never the big pipe. It’s the leak you can’t hear. Trust the residuals.” He just pointed to the repaired joint and said, “Page 266

He radioed the repair crew. As they clamped the leak at 2 AM, he heard a sound he hadn’t heard in weeks: a distant, rising gurgle in the overhead tank. Pressure was returning.

She nodded, not understanding, but grateful.