Transport infrastructure evaluation using cost-benefit analysis: improvements to valuing the asset through residual value—a case study

Abstract

Residual value (RV) is an important component of Cost Benefit Analysis (CBA), often valued at 20% to 50% of total construction costs. It is often overlooked which can artificially depress the project?s returns. The treatment of RV is inadequate and needs further research. Residual value represents the value of the infrastructure at the end of its project lifetime and the value that the asset generates from then on. We analyze three methods for calculating RV: straight-line depreciation, annuity/perpetuity and component. The straight-line depreciation method is the most commonly used; it is simple and quick to produce and it typically uses a percent of the total construction cost rather than real value. The perpetuity/annuity method ignores the actual value of the asset. It reflects the difference of costs and benefits between economic and useful life (annuity method) or assumes an infinite economic life (perpetuity method). The component method is the most detailed and difficult to calculate method. It gives the actual value of the physical asset at the end of project appraisal by infrastructure component. We assume three scenarios for the future for the component method. We use the case study of the Portuguese High Speed Rail project to calculate and compare each method. As expected, the perpetuity has the highest RV and net present value (NPV), followed by the annuity method and then the component method. The straight-line method produces the lowest values (other than one scenario for the component method). Sensitivity analysis is performed ceteris paribus for the demand, construction cost and discount rate factors. We conclude that RV is important in situations when the benefit-cost ratio is close to 1 and the method selected can have a large impact on the size (and sign) of the NPV.

Cite this work

No public copy is stored for this record, so only the metadata is cited.

Stored only when both papers are in the corpus — 3 citations exist upstream.

Papers that cite the same references — the relational fallback while embeddings are still backfilling.