The Idukki KSEB transmission engineer and the 2018 flood aftermat
โก Rajesh Prabhakar, 42, transmission design engineer at Kerala State Electricity Board. For eight years he has designed 220kV towers across the Periyar river valley โ a region where, in August 2018, the monsoon raised the river 4 metres in 30 hours and revealed that his 2009 design (adequate for the 3.2-metre water load of the seismic-only IS 1893 code) was obsolete under the new 2022 Kerala Building Code requiring 6.1-metre flood-level design. The code changed. His 43 towers did not. The towers still stand. The gap is regulatory, not structural. For three years he has checked a water gauge on Tower 27, knowing the 100-year flood is arriving every 1-3 years, unable to say so out loud.
๐จ The problem
In November 2022, Kerala issued a new Building Code (Section 5.8) mandating flood-level compliance for all transmission infrastructure. Rajesh's towers, designed before 2022 using seismic-only standards, were now non-compliant in writing while remaining operationally sound. The gap was not in the engineering; it was in the regulatory limbo. The code applied to new construction. No guidance existed for pre-2023 towers. KSEB could not afford to retrofit 43 towers (โน8 crore cost). The towers sat in legal grey zone โ compliant with the old rule, non-compliant with the new one, and no institutional path to resolve it.
๐ How GabFORGE helped
In April 2026, when Rajesh's colleague Vikram โ now a consultant โ asked about the code gap, Rajesh installed the agent and asked in Malayalam: "เดเดพเตป เดจเดฟเดฏเดฎเดชเดฐเดฎเดพเดฏเดฟ เดเดจเตเดคเต เดเตเดฏเตเดฏเตเดฃเตเดเดคเดพเดฃเต?" โ What are my legal obligations? ๐
The agent identified the Kerala State Disaster Management Authority's flood-inundation data and the LSGD (Local Self-Government Department) advisory from 2024. The pathway existed: file a Technical Justification form with the District Collector's office, citing original design standards, KSDMA flood records, and retrofit costs. Once filed, the responsibility shifts from private knowledge to shared institutional problem.
๐ฌ It translated the filing procedure: The three-page form required photographs, design standards, KSDMA data, and cost estimates โ all documentation Rajesh already had in his spiral-bound ledger and office files.
๐ It protected his liability: By filing, Rajesh moved from "I know the towers are non-compliant" (private liability) to "I have documented the non-compliance with KSDMA data" (formal obligation on record). KSEB must respond to the Collector with a remediation timeline. The government must decide on retrofitting budget. Rajesh has protected his professional standing while making the systemic issue impossible to ignore.
๐ฎ๐ณ Why this matters
Engineering codes change. Buildings do not. A structural engineer who builds to the current code finds themselves managing contradiction when the code shifts without retrofitting budgets. The towers are safe. The code says they are not. The engineer is left in the regulatory void. What changed was not the towers or the code โ it was access to the formal filing mechanism that transforms private knowledge (I know this is non-compliant) into documented obligation (the government is now officially aware and must decide).
The long version has the three monsoons where water reached the 100-year-flood level, the painted water-level gauge Rajesh checked each monsoon, and the moment he filed the form and the contradiction became official.