# Lifecycle & funding

> The lifecycle forecast and Capital Brief - projected replacement costs, keep-pace vs. catch-up reinvestment, and the funding gap by system class.

Source: https://app.assetlab.ca/docs/asset-management/lifecycle

The **Lifecycle** tab of the [dashboard](/docs/asset-management/dashboards) turns the lifecycle fields on your [asset records](/docs/asset-management/assets) into the capital story: what reaches end-of-life and when, what it costs to hold condition steady or work down the backlog, and where funding still falls short.

An asset counts as **due for replacement** when it passes the end of its expected life (install year + useful life) or when its condition score falls to the condition threshold - whichever comes first. When the [Infrastructure module](/docs/infrastructure) is enabled, infrastructure features ride through the same forecast alongside facility assets, so linear and vertical assets appear in one picture.

## The headline numbers

Five cards summarize the current scope:

| Card | What it means |
|---|---|
| Total assets | Assets in the current filter scope |
| Requiring replacement | Assets due within the forecast horizon, by age or condition |
| Replacement value | Today's replacement value (CRV) of the whole scope |
| Total replacement cost | Inflation-adjusted cost of the assets due within the horizon, in future dollars |
| Annual average | Total replacement cost divided by the horizon - the level-funding number |

## Simulation parameters

The **Filters** panel is a live simulator - every chart recomputes as you drag:

| Parameter | What it does |
|---|---|
| Forecast period | Horizon in 5-year steps; extends past 20 years when asset lifecycles run longer |
| Inflation rate | 0-10%, seeded from your organization setting |
| Lifespan modifier | Stress test: 0.5x-2.0x on every useful life ("what if everything lasts 20% longer?") |
| Condition threshold | Assets at or below this condition count as due regardless of age |
| Sustainable reinvestment rate | The keeping-pace target as a % of replacement value per year (default 5%); saved per organization |
| Fiscal year | Which year's recorded spend the Capital Brief reports |

Below the parameters, scope filters narrow everything to a site, building, system class, or system group.

### Show: facilities, infrastructure, or both

If your organization manages [infrastructure](/docs/infrastructure), a **Show** dropdown sits at the top of the scope filters with three choices - **Facilities & Infrastructure** (the default), **Facilities**, and **Infrastructure**. It applies to everything on the tab: the five cards, the projected replacement chart, the Capital Brief, and the replacement table.

Two things follow from it:

- Picking **Infrastructure** clears and disables the site, building, system class, and system group filters. Network features are not attached to a facility site or system, so those filters would empty the page.
- The Capital Brief's recorded-spend sections follow the same choice, so a Facilities view reports facility spend only.

The dropdown is hidden when there is only one estate to show - either infrastructure is switched off for your organization, or your workspace is scoped to a single module.

## Projected replacement costs

The main chart stacks projected replacement cost per year, split by system class. Click a year to see exactly which assets drive that bar.

Infrastructure features stack alongside facility system classes, one segment per network. Clicking a year lists facility assets individually; infrastructure appears as a single line per network with the number of features behind it, because a network is summarised rather than loaded feature by feature. The replacement table below still lists every feature individually, and each row opens that feature.

A toggle switches between two views:

- **Lifecycle** - the projected need, computed from install dates and useful lives.
- **Planner** - only the replacements actually scheduled on the replacement calendar.

Planner covers whichever estates the **Show** dropdown includes: facility assets scheduled in the facilities planner, and infrastructure features scheduled in the infrastructure planner, each priced the way its own calendar prices it. A year with nothing scheduled is empty here, however much lifecycle need it carries.

The difference between the two views is your plan's coverage: need the [replacement planner](/docs/projects/replacement-planner) hasn't scheduled yet.

## The Capital Brief

Below the chart, the **Capital Brief** presents the same data as a resident-facing narrative - the sections read like a capital-plan summary rather than an analytics screen. It follows the simulation parameters and filters above, and is available on AssetLab 360 and Enterprise plans.

### Current situation

Where the portfolio stands today: the overall condition grade, [FCI](/docs/asset-management/risk-and-fci) by system class and by system group (replacement value of overdue assets divided by total replacement value - under 10% is healthy), and how condition grades distribute within each class, so you can see where the worst-rated assets concentrate.

### What it takes to bring up our FCI

The reinvestment requirement at 5, 10, and 20-year horizons, per system class:

- **Backlog today** - the replacement value already overdue.
- **Keep pace** - renew assets as they reach end-of-life; enough to hold each class's FCI roughly steady.
- **Catch up** - keep pace plus clearing today's backlog, driving FCI toward 0%.

The gap between keep pace and catch up is the deferred maintenance already on the books.

### What we do about it

Whether current spending keeps pace, and where funding falls short:

- **What you invest in** - money actually spent this fiscal year (recorded replacement, repair, and PM costs), rolled up the system hierarchy.
- **Are we keeping pace?** - capital delivered per year (replacement and PM spend plus the budgets of projects reaching completion) against the sustainable target: your reinvestment rate times replacement value. Repairs are excluded - reactive maintenance isn't renewal.
- **Maintain ahead, or repair behind** - this year's maintenance spend split into [preventive](/docs/cmms/preventive-maintenance) versus reactive.
- **Funding gap by system class** - the need at your chosen horizon against the funding already lined up.

### Where the funding-gap figures come from

Each figure traces to a specific set of records, so the gap is auditable rather than an estimate:

| Figure | Data source |
|---|---|
| Need | The forecast's catch-up figure: the summed replacement value of every asset due by the horizon, today's backlog included. Driven by install date, useful life, replacement cost, and your inflation setting |
| Planned | [Replacement calendar](/docs/projects/replacement-planner) entries whose planned year falls within the horizon. Each entry is valued at the asset's current replacement value, falling back to the plan's estimated cost when the asset has no cost data |
| Committed | Budgets of [projects](/docs/projects) in planning, in progress, or on hold - completed and cancelled projects never count. Each budget is split evenly across every system class and infrastructure network the project is linked to, and counts toward a horizon once the project is due to finish inside it |
| Funded | Planned + Committed - the money already lined up against the need |
| Gap | Need - Funded; a positive number is work with no money behind it yet |

Two consequences of that model worth knowing:

- A project contributes to Committed only if it's linked to at least one system class or infrastructure network - the links are what tell the brief which class the money belongs to. An unlinked budget is invisible here.
- Because a project's budget is split across everything it touches, a project spanning facilities and infrastructure credits each side proportionally - the total is conserved, never double-counted.

Planned tracks *scheduled work*, Committed tracks *allocated money* - together against Need they answer "is the plan funded?", which is a different question from the [Budget page's](/docs/asset-management/budget) "did we set an envelope and are we inside it?"

> [!note] Organizations using the depreciation metric instead of FCI see a Net/Gross PP&E version of the brief - same structure, age-based financial figures.

## Assets requiring replacement

The closing table lists every asset due within the horizon - past-due assets flagged - with its location, system, original cost, and estimated replacement cost at its replacement year.

> [!tip] The whole tab is only as good as three fields: install date, useful life, and replacement cost. Populate them for your high-value systems first - [import](/docs/start/importing-data) is the fastest way - and the forecast becomes defensible.