The National Electrichttps://engineeringreview.com.pk/ Power Regulatory Authority (Nepra) issued a show cause notice to K-Electric on Tuesday due to excessive load-shedding. Nepra has also decided to take action against two other distribution companies of the federal government operating in Sindh.
The decision was taken after a day-long public hearing, which was held a few days ago.An investigation team of Nepradone a field visit in Karachi and looked into the matter of excessive load-shedding in Karachi.
The investigation committee submitted its findings, which shows discrepancies in the work of KE. It compels Nepra to issue a show cause notice which is also according to under sections 28 and 29 of the Nepra Act and licencing rules for failing to ensure uninterrupted power supply to consumers and maintain service quality.
In the meantime, the Nepra held public hearings into protests against the Hyderabad Electric Supply Company (Hesco) and the Sukkur Electric Power Company (Sepco) over load-shedding and overbilling. A surge of objections rolled in from customers during the public hearingspresided over by Chairman Tauseef H. Farooqi.
In the result of this public hearings, two more companies Hesco and Sepco were taken on board and were asked the reasons for excessive load-shedding.
CEO of Hesco Abdul HaqMemonrevealed that five to six hours of normal load-shedding while remote areas were oppressed as long as 12 hours of power cuts. Whereas unannounced load-shedding has been ended.
Sindh Energy Minister Imtiaz Shaikh told the Nepra that load-shedding in Hesco and Sepco zones had now gone as long as 18 hours and expressed gratitude toward the controller for holding a formal conference. He proposed that the regulatorproceed an investigationinto the Hesco and Sepco’sperformance on the example of K-Electric. The Minister said he would not like to give a political shading to the individuals’ torment, however, the reality was that load-shedding was an intense issue in Sindh and the two organizations (Hesco and Sepco) had not had the capabilityto resolve the issue.
