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
Maintenance | IADB
Actividad Card Taxonomy
Activity Relation Card Self
Descripción Card Self

The maintenance activity must be considered not only from technical aspects, but also the costs of realization and the costs of non-realization must be evaluated. Utilities can use a new methodology Reliability Centered Maintenance to optimize maintenance resources and to develop maintenance plan for distribution networks and substations. Some practices for utilities to have in place are:


a. Computerized maintenance management system (CMMS): Utilities use a management software that performs functions in support of management and tracking of O&M activities, with some minimal functionality such as work order generation, prioritization, and tracking by equipment/component, historical tracking of all work orders generated, tracking of maintenance activities, storing of maintenance procedure and of all technical documentation or procedures by component, real-time reports, calendar or run-time-based preventive maintenance work order generation, capital and labor cost tracking by component and others;


b. Training and standards: There is an annual training and recycling plan for maintenance crews. It is defined the reporting requirement for O&M activities and its frequency, also there are Operations and Maintenance Manual including written operations procedures and preventive maintenance work procedures and checklists.


c. work orders: All types of work to be performed must be created in the system like a work order. The work orders can be into one of two categories: planned work and unplanned work. Work orders must have the minimum information to guarantee the safety and quality of the work, such as: Geographic location, reference equipment, standards, contact of the Operation Center, and among others.


d. Management of field work: Remote dispatch should be used and dynamic dispatch of crews to reduce travel time and improve response to emerging jobs.


e. Human Resources Management: It is important to reduce the non-productive time of the crews (late out, early return, extended breaks) to optimize field force utilization. In addition, processes should be created to use field forces to close work plans when completing work, eliminating additional administrative costs;


In addition to these practices on the maintenance process, it is also important to highlight that maintenance can be performed reactively in emergency situations (corrective maintenance) or planned to act preventively (preventive and predictive maintenance).

 

For preventive maintenance some recommended practices are:


• Job Planning: Every activity must have a planning stage that must be carried out in advance and, if possible, by different personnel who will carry out the activity. The plan must contain all the necessary resources: materials, equipment and labor.


• Job Scheduling: optimize work schedules over a period of several months, smoothing peaks/valleys for equipment and labor, minimizing the impact of limited resources;


• Workstations: Jobs: It is important to work with a plan considering several workstations in different regions. This improves flexibility for resource sharing, rather than artificially restricting labor and equipment to a single operations center or territory;


• Supply Chain: Look for an improvement in the materials staging to eliminate the impact in other stages of the process. The supply chain should never "command" the all operation.


• Resource Availability: All resource options (contractors or employees) should be considered based on demand and cost. When the workload associated is constant, it is an ideal task to outsource work with a fixed amount.


For corrective maintenance some recommended practices are:


• Trend: It is possible to check the volume trend of this work in recent years to realize that the volume can be predicted based on environmental events. As such, model work plans must be created and made available for application in this work, minimizing planning and maximizing standardization.


• On-call staff: It is necessary to maintain a minimum number of crews, of different types, available in the regions with the highest incidence of events or the highest density of consumers.

Orden
1
Pregunta Self Assesment

The maintenance activity must be considered not only from technical aspects, but also the costs of realization and the costs of non-realization must be evaluated

Translate Activity
managemen-costs
Translate Name
maintenance