01.12.2016 Views

EVALUATION

evaluation_of_the_lcnf_0

evaluation_of_the_lcnf_0

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

AN INDEPENDENT <strong>EVALUATION</strong> OF THE LCNF<br />

benefits where the results are identifiable and credible. For this evaluation work we<br />

have defined ‘future benefits’ as being those that accrue between 1 April 2016 and 31<br />

March 2031 (the end of the RIIO-ED2 period) 22 .<br />

2.5.3.1 Analysing the data<br />

Given the uncertainty associated with measuring the potential benefits associated with<br />

innovation, we have discussed above, we have only monetised the potential benefits<br />

where we believe the results are robust and credible and can be defended.<br />

Following receipt of the information from the DNOs we have undertaken analysis and<br />

validation of the results. Given the nature and stage of the LCNF projects there are no<br />

independent sources of information available by which to verify the quantitative data. As a<br />

result, our analysis has been undertaken based on a review of other DNO submissions,<br />

for example this includes the reports published as part of the LCNF process and<br />

benchmarking between comparable projects. Specifically this process has included:<br />

• cross-checking the results against other publically available data, such as project<br />

‘Close Down’ reports and bid submission, to make sure that the estimated benefits<br />

had consistency;<br />

• ensuring consistency within, and between, the DNO submissions. For example we<br />

looked at LCNF projects with similar innovation initiative to check for any major<br />

difference in the benefits estimated; and<br />

• analysing the results to understand the different types of initiative being investigated<br />

by the LCNF projects. In doing this we drew on the academic classification system<br />

developed by the University of Strathclyde in its report on the LCNF 16 .<br />

Finally, we spoke individually with each of the DNOs to resolve any questions we had on<br />

the original information provided. During these discussions we resolved a number of<br />

potential issues 23 and through the clarifications we were able increase the robustness of<br />

the information provided. We are reasonably comfortable with the veracity of the data<br />

provided by the DNOs – recognising that these numbers would change if the DNOs had<br />

more time to undertake a more comprehensive assessment.<br />

2.5.4 Defining a robust baseline<br />

Essentially the quantitative element of this evaluation has attempted to identify any<br />

‘additionality’ from the LCNF scheme. That is, what has been, or is expected to be,<br />

delivered in addition to what might reasonably be expected to have happened anyway.<br />

To understand this additionality we have established a ‘counterfactual’ position based on<br />

what we would have expected to happen if the LCNF has not been implemented.<br />

Establishing such a counterfactual is challenging, since by definition it cannot be observed<br />

– it is what would have happened if the policy had not gone ahead. A strong evaluation is<br />

one which is successful in isolating the effect of the policy from all other potential<br />

influences, thereby producing a good estimate of the counterfactual.<br />

22<br />

23<br />

This assessment period is, in general, shorter than the assessment period used by DNOs in<br />

their project closedown reports.<br />

For example we identified examples of double counting of benefits between projects and<br />

differences in the potential benefits between the questionnaire response and other publically<br />

available reports.<br />

PÖYRY MANAGEMENT CONSULTING<br />

October 2016<br />

713_Poyry_Report_Evaluation_of_the_LCNF_FINAL_Oct_2016_v700.docx<br />

19

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!