Deprecated: Return type of Symfony\Component\HttpFoundation\ParameterBag::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home1/escue264/vendor/symfony/http-foundation/ParameterBag.php on line 213

Deprecated: Return type of Symfony\Component\HttpFoundation\ParameterBag::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home1/escue264/vendor/symfony/http-foundation/ParameterBag.php on line 223

Deprecated: Return type of Symfony\Component\HttpFoundation\HeaderBag::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home1/escue264/vendor/symfony/http-foundation/HeaderBag.php on line 282

Deprecated: Return type of Symfony\Component\HttpFoundation\HeaderBag::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home1/escue264/vendor/symfony/http-foundation/HeaderBag.php on line 292

Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in /home1/escue264/web/core/lib/Drupal/Core/DrupalKernel.php on line 1008

Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in /home1/escue264/web/core/lib/Drupal/Core/DrupalKernel.php on line 1009

Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in /home1/escue264/web/core/lib/Drupal/Core/DrupalKernel.php on line 1010

Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in /home1/escue264/web/core/lib/Drupal/Core/DrupalKernel.php on line 1013

Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in /home1/escue264/web/core/lib/Drupal/Core/DrupalKernel.php on line 1015

Deprecated: Return type of Drupal\Core\Render\Markup::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home1/escue264/web/core/lib/Drupal/Component/Render/MarkupTrait.php on line 71

Deprecated: Return type of Drupal\Core\Render\Markup::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home1/escue264/web/core/lib/Drupal/Component/Render/MarkupTrait.php on line 61

Deprecated: Creation of dynamic property Drupal\Core\Database\Driver\mysql\Connection::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Creation of dynamic property Drupal\Core\Logger\LogMessageParser::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Creation of dynamic property Drupal\dblog\Logger\DbLog::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Creation of dynamic property Drush\Log\DrushLog::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Creation of dynamic property Drupal\Core\Logger\LoggerChannelFactory::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Creation of dynamic property Drupal\Core\Session\AccountProxy::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Return type of Drupal\Core\Database\Query\Insert::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home1/escue264/web/core/lib/Drupal/Core/Database/Query/InsertTrait.php on line 182

Deprecated: Creation of dynamic property Drupal\Core\Site\Settings::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Creation of dynamic property Drupal\Core\Cache\CacheFactory::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Creation of dynamic property Drupal\Core\Cache\ChainedFastBackendFactory::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Creation of dynamic property Drupal\Core\Cache\DatabaseCacheTagsChecksum::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Creation of dynamic property Drupal\Core\Cache\DatabaseBackendFactory::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Creation of dynamic property Drupal\Core\Cache\ApcuBackendFactory::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Creation of dynamic property Drupal\Core\Cache\ChainedFastBackend::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Creation of dynamic property Drupal\Core\Config\CachedStorage::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Creation of dynamic property Drupal\Core\Config\ExtensionInstallStorage::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Creation of dynamic property Drupal\Core\Cache\ChainedFastBackend::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Creation of dynamic property Drupal\Core\Cache\ChainedFastBackend::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Creation of dynamic property Drupal\Core\Extension\ModuleHandler::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Creation of dynamic property Drupal\Core\DependencyInjection\ClassResolver::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Creation of dynamic property ArrayObject::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Creation of dynamic property Drupal\Core\Validation\ConstraintManager::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Creation of dynamic property Drupal\Core\Config\TypedConfigManager::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Creation of dynamic property Drupal\Core\Language\LanguageDefault::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Creation of dynamic property Drupal\language\Config\LanguageConfigFactoryOverride::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288

Deprecated: Creation of dynamic property Drupal\Core\Config\ConfigFactory::$_serviceId is deprecated in /home1/escue264/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 288
Electricity Loss Reduction | IADB
Taxonomy Area
Area relation
Descripción de actividad

Assesses the degree of productivity and efficiency of the transmission and distribution systems and it is analyzed to design a plan to improve the technical and non-technical (commercial) losses. 

Descripción Simulation

This toll facilitates comparing the performance of an individual utility with the database of utilities in the Latin America and Caribbean region. The users can enter their individual performance on the indicator and the chart will display its performance against the database.

Gráfica indicators
Gráfica simulation
Imagen actividad
electricity loss reduction
Imagen overview
Medidor
Imagen Self assessment
Self assesment
Orden
1
Sub area relation
Subtitulo best practices
Projects and publications
Texto banner self

Developing a comprehensive and sustainable electricity reduction program requires a "holistic view" integrating several activities. This section prompts the user to assess its degree of readiness on these activities that can be followed by the best practices in each activity.

Texto Case studies

For more information regarding the financial management and sustainability, please consult the Case Studies:

Texto indicators

Data and statistics from the energy sector, including indicators on electricity losses can be found at the IDB energy hub.
The energy hub is constantly updated with new information.

Texto overview 1

While there are different definitions of electricity losses, these usually converge to the difference between the amount of electricity that enters the network and the amount that is not paid by consumers. In the case of a utility that it is vertically integrated, the losses represent the difference between its generation injected into the grid and the amount not paid by consumers. For the case of distribution companies, it refers to the power that was purchased by the utility but not paid by the consumers. In a few cases, it may include the electricity billed to consumers but not collected after a reasonable amount of time (usually 180 days). This represents a financial loss in the account receivable as part of the provision for bad debt (or allowance for uncollectable accounts), and thus for the purpose of this toolkit it is considered an accounting or financial loss (dependent on the accounting rules of each country), and not an electricity commercial loss.

Texto overview 2

Electricity losses can happen in the transmission or distribution activities. There are different ways to calculate electricity losses, and the section on best practices presents some of these.Most of the electricity losses (around 70-80 percent) are related to the distribution end-user activities, as the transmission losses are usually between 20-30 percent of the total. In LAC for example a study estimated that 18% of losses are in transmission while 81% are in distribution3 This ratio however is not constant when compared to other regions. Other studies identified transmission losses in the USA were around 50% of total losses4.

Electricity losses is an important consideration in the LAC region as they represent an estimated financial cost for the electricity industry that ranged from US$11 to US$17 billion in 2012, equivalent to 0.2 to 0.3 percent of the region’s GDP. Total losses in LAC are around 17%, while for example in the USA it is around 5%5 . Estimates from the IDB study indicate that after allowing for a conservative level of technical losses, the percentage of losses translated into 100 TWh lost in 2012, and without substantial reductions in the future, losses can go up to 182 TWh in 2030.

In this context, the reduction in electricity losses brings important financial benefit to the distribution utility but they cannot be an isolated activity. The reduction of losses is usually part of a strategic transformation of the utility with other performance improvement activities as it requires prioritization of investments and allocation of teams. These are described later in the best practice section.

Electricity losses can be divided in two parts:

  • Technical losses: correspond to all the energy dissipated in the transport of electrical current in conductors, equipment, and connections due to resistance in the distribution network. Technical losses can be further divided into: (i) fixed technical losses (caused by physical inefficiencies such as hysteresis, Eddy Currents losses in the iron core of transformers, and the corona effect in transmission lines) and (ii) variable technical losses (which can happen when power current flows through the lines, cables, and transformers of the network. These are also called load losses, or series losses).

  • Non-technical losses or commercial losses are those usually associated with the sale of energy supplied to the end user. There is a part of the energy that is produced, transported and supplied; however, it is not invoiced, or it is invoiced but not paid. These losses can be caused by internal or administrative problems (such as errors in measurement, accounting or record keeping) but they are usually associated with the consumer's own illegal intervention, such as thefts, fraud, alteration of meters, or unmetered supply (when the consumer is responsible).

The reduction of losses is a key activity in the transmission and distribution sub-sectors. However, due to the elasticity of demand, the implementation of a loss reduction program can also affect the generation due to the overconsumption. This is due to the electricity “subregistry” corresponding to the energy consumed by the client that does not circulate through the meter, which is actually reduced from the moment a customer is required to pay for its consumption. By promoting the rational, productive, and efficient use of electricity by consumers, it is estimated that after regularization of the customer, approximately 1/3 of the unregistered consumption does not need to be generated.

At the same time, the regularization of electricity services improves the wellbeing of customers as residential consumption of modern energy sources is correlated with per capita income6. The regularization of services also enables the possibility of using electricity for productive activities and further economic development.

Based on available methodologies and definitions, it is possible to calculate the indicators of electricity losses by country, utility, and further segmentation by geography based on the availability of data. Whenever possible these indicators must consider the distributional impact of the losses, in particular to those parts of the society which are more vulnerable and have less resources.

Lastly the assessment to develop an electricity loss reduction program needs to acknowledge that the level of effort and activities would be different depending on the level of losses of the utility. For illustration purposes, the following chart7 presents the electricity losses in LAC (technical and non- technical) at country level, which already combines of one or more utilities in a country. For example, Brazil is represented with the average of 17% but the electricity los across the 52 utilities range from 7% to 32%. The wide dispersion at country and regional levels exemplifies that the starting point for each country is different and therefore the activities selected in the toolkit have to be tailored to each country (and utility) situation.

Texto principal best practices

International experience in the management and reduction of electricity losses indicates that a company must have a “holistic view” of this activity since it integrates several units, and the results have a large impact on its financial and operational results. The LAC region has implemented successful electricity loss programs, and these are illustrated in the next section of references. Considering the indicators calculated for this company compared to external references, and the good practices described below, it is possible to establish an action plan with the activities to reduce electricity losses.

For each practice, the main “insights” found in companies that have been successful in this field are listed. These insights are not authoritative, since each company must adapt the practices to its reality, however they serve as general guidelines to assist the company to advance its respective good practice.

The practices of electricity losses are organized in 10 items across three main groups which are presented next: (i) public actions and State leadership; (ii) operations, commercial, and financial practices part of a distributing company (core part of the activities of a distribution utility), and (iii) social and equity considerations.

Texto secundario best

Data and statistics from the energy sector, including indicators on electricity losses can be found at the IDB energy hub.
The energy hub is constantly updated with new information.

Texto inside self

Designing an Action Plan

The development of an action plan is an important result from the review of the indicators and best practices of the processes for the utility. As an additional functionality of the toolkit this chapter presents the main activities to be considered to support the identification and prioritization of what are the most relevant practices to the utility and what are the best ways to develop and implement an action plan.

The definition of a comprehensive and well thought action plan is essential to attract investment opportunities and communicate the expected results. While there are different methodologies to design an action plan, most of them converge to similar activities, which are presented next as the steps in developing the plan.

Step 1 - Define problem and analyze data

Action plans usually start by clearly defining the main problem facing the utility andpolitical willingness to address it. This is done by collecting and analyzing the data and verifying previous assumptions of the problems that triggered the review. The toolkit can be an important methodology to identify areas where the indicators of the utility are below the references, benchmarks, or regulatory standards, and what are the best practices the utility can introduce. Still within this first step, usually teams define the goal and targets the utility would like to achieve, which in turn defines the level of ambition of the action plan.

Step 2 - Prioritize activities

Subsequent to the definition of the problem and expected results, the utility will need to prioritize the areas of intervention. This prioritization is done by segmenting the activities in different dimensions of: (i) impact or effectiveness (i.e., which activities Will deliver the highest impacts or benefits); (ii) timeframe (i.e., what is the best sequence of activities in the short, medium, and long term considering the expected benefits); and (iii) efficiency (i.e., based on quantitative measures such as cost benefit analysis, which of these activities will deliver the highest returns for similar levels of investment). Lastly, this prioritization should also identify synergies and complementarities among the activities to be consolidated in a single action plan.

Step 3 - Identify resources

Based on the action plan previously defined, it will be important for the utility to seek the financial and knowledge/expertise resources, as usually these activities need investments. Some utilities may have their own teams and financial resources to implement the action plan, while others will need to seek external financing and/or bringing technical expertise (example of new technology). Some sources of financing can be concessional with favorable commercial terms, which can make the action plan more feasible to be implemented. In this step it is also important to proactively seek and obtain support from the relevant country stakeholders (e.g., government authority, regulators, industry association, etc.) and clear understanding on the expected impacts and benefits of this action plan.

Step 4 - Prepare to implement

Lastly, the utility needs to develop a detailed implementation plan, not only including the activities previously defined, but also the governance model of the implementation (e.g., definition of team responsibilities and authorities, level of dedication, etc.) and how progress will be monitored and evaluated. Adaptability becomes a key ingredient of the plan, and an important reminder is to keep into perspective that11 “a business/action plan can't be a tightly crafted prediction of the future but rather a depiction of how events might unfold and a road map for change”. The results from the readiness to implement, together with seeking the political support and securing the financial resources are the last activities before implementation.

In sum, this chapter presented in general terms how utilities can develop a robust action plan and increase the likelihood of successful implementation, using the results from the areas of this toolkit.

Taxonomy Subarea