Periodic tree pruning comes with high associated costs in all countries and it is difficult to schedule it due to the unknown growth speed of different plants. This uncertainty makes standard tree maintenance plans expensive. Because of this, a new need arises: the optimization of vegetation maintenance activities through the use of data collection and monitoring systems, to decide the proper trimming frequency for each area as a function of its peculiar kind of vegetation.
The ambition of this Challenge is to automate as much as possible the field data collection activity and to identify, with high precision and low costs, the species of vegetation and obstacles around the lines using the obtained information. Today this task is performed in a semi-automated way: helicopter assessments and local verifications.
Enel is looking for suppliers to provide specific techniques/HW/SW to allow the acquisition of data about vegetation and any possible obstacle (buildings, scaffoldings, …) which is in the surrounding area of the lines and can constitute a safety threat for the infrastructure and the obstacle itself, such information with the objective of reducing as much as possible human intervention and related costs. Expected benefits of the system include:
- Optimisation of vegetation trimming activities considering the peculiarities of each area;
- Reduction of maintenance costs as a consequence of the above mentioned benefit;
- Scheduled vegetation trimming on demand;
- Reduction and adjustment of trimming costs according to the real work done by subcontractors;
- Better control over the externalized work;
- Being able to advise timely if any threat for the infrastructure can impact operation.
In general, the Data Collection and Monitoring system must satisfy the following Solution Requirements:
- Collect vegetation data in a cost-efficient way (less expensive than taking pictures using helicopters) but with a quality level sufficient for analysis;
- Identify the different arboreal species using the above mentioned data;
- Identify any obstacle which can constitute a threat to the lines and devices of the grid, including building, provisional scaffolding …;
- Limit as much as possible human intervention;
- Improve the following Key Performance Indicators (KPI)
- OPerational EXpenses (OPEX) reduction/increase*;
- Number of failure events on the overhead lines due to vegetation;
- Number of incidents due to lack of guard distances.
*the use of this system could lead to an increase of the trimming activities w.r.t. the current periodical interventions. Even if in this case maintenance costs would increase, failure events due to vegetation could be avoided.
- Any proposed solution should have at least TRL 4 (Technology Readiness Level), which means: design, development and lab testing of components / processes. Results provide evidence that performance targets may be based on projected or modeled systems.
The submitted proposals should include:
- Video - it is appreciated if the Solvers will submit a video that summarises the proposal and allows Enel to do a quick initial screening of proposals
- Collaboration Proposal including:
- A description of the proposed data collection and monitoring system with an explanation of how the Solver proposes to address all the Solution Requirement. The Solver can withhold proprietary information, if necessary, but should provide convincing evidence for ENEL to appreciate the merits of the approach and be comfortable that the solution can effectively work;
- A brief discussion of capabilities and relevant prior experience that are relevant for the development of the solution and success of the post-Challenge collaboration;
- The Solver should explain what they can provide and what might be required of the Seeker. For example: “I can provide with the expertise, but I would need the Seeker to facilitate access to data”;
- A brief overview of the proposed path forward along with a plan for validation (e.g. deliverables, timelines, milestones, and cost estimates);
- The Solver should indicate the TRL (Technology Readiness Level) of the solution.
- General Information about the Solver including:
- The key contact person for this Challenge (including phone number and email address).
- Organization/Company name and address (including website, if available)
(NOTE: For most Challenges, Solvers are not allowed to include personal contact information; however, for an eRFP Challenge, it is required.)