Skip to content
Request Demo

Asset Management Plans

Technical Guide • Intermediate • 3 min read

Audience
Government Agencies • Asset Owners • CFOs • Advisory Firms
Last Reviewed
July 2026
Updated
Version 1.0

Executive Summary

An asset management plan (AMP) is the document, and underlying financial model, through which an asset owner sets out how a portfolio of infrastructure assets will be operated, maintained, renewed, and funded over a defined planning horizon, typically ten to thirty years. This guide covers how the financial projections in an asset management plan should be structured: the link from the asset register and condition assessment to a funded forecast, the level-of-service targets the plan is built to sustain, and the funding gap analysis that distinguishes a credible plan from an aspirational one.

Key Takeaways

  • An asset management plan's financial projections should be built from the asset register and condition assessment data for the actual portfolio, not a generic percentage-of-replacement-value assumption applied uniformly across dissimilar assets.
  • The plan should be structured around defined level-of-service targets, since renewal and maintenance funding requirements are a function of the service standard the owner has committed to sustain, not a fixed budget independent of any stated outcome.
  • A funding gap analysis, comparing the technically required renewal and maintenance spend against the funding actually available or committed, is the analytical core that distinguishes a credible asset management plan from an aspirational one.
  • Renewal and maintenance forecasts should be built at the individual asset or asset-group level from condition data, then aggregated to the portfolio, rather than starting from a portfolio-level budget and working backwards.
  • An asset management plan should be treated as a living financial model, updated as condition data, service standards, or funding availability change, rather than a static document produced once and left unrevised for the full planning horizon.

Objective

This guide covers how the financial projections within an asset management plan (AMP) should be structured, within Infrastructure Asset Management Financial Modelling, for a portfolio of infrastructure assets held by a government agency, utility, or other institutional asset owner.

From Asset Register to Funded Forecast

An asset management plan's financial projections should be built bottom-up from the asset register — the inventory of individual assets and their attributes — combined with condition assessment data for each asset or asset group. A generic percentage-of-replacement-value assumption, applied uniformly across a portfolio regardless of actual age, condition, or criticality, is a common shortcut that produces a plan disconnected from the portfolio's real renewal timing.

Level-of-Service Targets Drive the Funding Requirement

Renewal and maintenance funding is not an independent budget figure — it is a function of the level of service the asset owner has committed to sustain. A plan that presents a funding requirement without reference to a stated service standard cannot be tested for whether the proposed spend is sufficient, excessive, or correctly targeted, since the same portfolio can require materially different funding depending on the service outcome being pursued.

The Funding Gap Analysis

The analytical core of a credible asset management plan is its funding gap analysis: the technically required renewal and maintenance spend, derived from condition data and level-of-service targets, compared against funding actually available or committed from the owner's budget or revenue base. See Renewal Gap for the specific metric this comparison produces. Where a gap exists, the plan should present it explicitly, together with the service-level or asset-condition consequence of leaving it unfunded, rather than presenting only the funded scenario.

Bottom-Up Aggregation

Renewal and maintenance forecasts should be built at the individual asset or asset-group level, then aggregated to the portfolio total, rather than starting from a portfolio-level budget figure and working backwards into implied per-asset assumptions. Bottom-up aggregation preserves the traceability between the plan's total funding requirement and the specific condition and criticality data underlying each contributing asset.

The Plan as a Living Model

An asset management plan covering a ten-to-thirty year horizon should be updated as new condition survey data, revised level-of-service targets, or changed funding availability become known, rather than produced once at the start of the planning period and left unrevised. Treating the plan as a static document undermines its usefulness as the basis for ongoing renewal and maintenance budgeting decisions.

Common Construction Pitfalls

Generic percentage-of-replacement-value assumption. Applying a flat renewal funding percentage across a dissimilar asset portfolio, rather than condition-based bottom-up forecasting, produces a plan disconnected from actual renewal timing.

Funding requirement with no stated service outcome. Presenting a funding figure without reference to the level-of-service target it is intended to sustain makes the figure impossible to test for adequacy.

Static plan never updated. Leaving the plan unrevised for its full planning horizon, despite new condition data or changed funding availability, allows the plan to diverge materially from the portfolio's actual position.

  • Build renewal and maintenance forecasts bottom-up from the asset register and condition assessment data.
  • State the level-of-service target each funding scenario is built to sustain.
  • Present the funding gap explicitly, together with the consequence of leaving it unfunded.
  • Update the plan as condition data, service targets, or funding availability change.

Continue Reading

How OXXON tests thisRun a free structural check with FMAE

Frequently Asked Questions

What is an asset management plan?

A document, and the underlying financial model supporting it, through which an asset owner sets out how a portfolio of infrastructure assets will be operated, maintained, renewed, and funded over a defined planning horizon, typically ten to thirty years.

How should an asset management plan's financial projections be built?

From the asset register and condition assessment data for the actual portfolio of assets, rolled up from the individual asset or asset-group level, rather than a generic percentage-of-replacement-value assumption applied uniformly regardless of each asset's actual age, condition, or criticality.

What is a funding gap analysis, and why is it central to an asset management plan?

A comparison of the technically required renewal and maintenance spend, derived from condition data and level-of-service targets, against the funding actually available or committed — the presence or absence of an unfunded gap is what distinguishes a credible plan from an aspirational one.

How do level-of-service targets affect the plan's financial projections?

Renewal and maintenance funding requirements are a direct function of the service standard the owner has committed to sustain — a higher level-of-service target generally requires more frequent or more extensive renewal spend, and the plan's projections should make this relationship explicit rather than presenting a funding figure with no stated service outcome attached.

Should an asset management plan be a static document?

No. It should be treated as a living financial model, updated as condition data, level-of-service targets, or funding availability change, since a plan built once and left unrevised for a ten-to-thirty year horizon diverges materially from the actual condition and funding position of the portfolio over time.

Related Articles

Infrastructure Asset Management Financial Modelling

Infrastructure asset management financial modelling is the discipline of modelling an infrastructure asset's ongoing operation, maintenance, and renewal across its full economic life, from the perspective of the owner or operator responsible for that asset once it is in service, rather than the transaction-close or lender perspective covered elsewhere. This page is the hub for the Knowledge Centre's asset management and operations modelling content: how a lifecycle model is structured across planning, construction, operations, renewal, and disposal, how whole-life cost and lifecycle cost analysis compare competing options, and how maintenance, renewal, and capital replacement should be planned and funded. Sector-specific operations models, performance and reliability modelling, and institutional assurance practice for this domain are indexed here as it expands.

Asset Lifecycle Financial Models

An asset lifecycle financial model represents an infrastructure asset's full economic life — planning and design, construction or acquisition, the operating phase, one or more renewal or major refurbishment cycles, and eventual disposal or decommissioning — as a single connected structure, rather than treating each phase as an independent model. This guide covers how to architect a lifecycle model: the phase transitions that must be explicitly modelled, how renewal cycles recur across the asset's life, and why a model scoped to a single phase systematically understates total cost of ownership.

Whole-Life Cost Modelling

Whole-life cost (WLC) modelling discounts every cost an infrastructure asset incurs across its full lifecycle, acquisition or construction, operating cost, routine and major maintenance, renewal capital, and disposal or decommissioning cost, to a single present-value figure, so that competing asset or design options can be compared on total economic cost rather than initial capital cost alone. This guide covers how a whole-life cost model should be built: the cost categories it must include, the discount rate question, and why comparing options on capital cost alone systematically favours the option with the highest deferred cost.

Capital Replacement Planning

Capital replacement planning takes the component-level renewal forecast produced by an asset renewal model and turns it into a prioritised, funding-constrained multi-year capital plan: which replacements proceed on schedule, which are deferred, and what risk that deferral creates. This guide covers how to build that prioritisation and constraint logic, connecting the technical renewal timeline to the capital budget an owner actually has available in a given year.

Asset Register

An asset register is the structured inventory of an owner's infrastructure assets, recording each asset's identity, location, original cost, installation date, condition, and criticality, among other attributes. It is the foundational data source from which asset management plans, whole-life cost models, and renewal forecasts are all built, and its completeness and accuracy directly determine the reliability of every downstream financial model that depends on it.

Level of Service (LOS)

Level of service (LOS) is the defined standard of performance, availability, or condition an asset owner commits to sustain for a given infrastructure asset or portfolio, expressed in specific, measurable terms rather than a general aspiration. It is the key driver of an asset management plan's renewal and maintenance funding requirement, since a higher committed service standard generally requires more extensive or more frequent intervention than a lower one.

Renewal Gap

The renewal gap is the shortfall between the technically required renewal and major maintenance spend, derived from condition data and level-of-service targets, and the funding actually committed by the asset owner over the same planning horizon. It is the central quantitative output of an asset management plan's funding gap analysis, and its trend over time is a key indicator of whether a portfolio's overall condition is likely to improve, hold steady, or deteriorate.

Request Demo