Skip to main content
Cartegraph Campus

About Scenario Plan Years

You must have administrator rights to access this feature.

This feature may not be available in every package. Not sure if you have this feature or you want to learn more about it? Send us a message at

Scenarios are used to identify projected activities with their cost and impact based on a defined maintenance approach for an asset type. Scenarios can be projected over one or more years using factors such as budget limitation or targeted OCI. These yearly projections are known as plan years.

When a scenario is created, the scenario's plan year records are created based on the value entered in the Number of Years field. Number of years is between 1 and 100.

Each plan year record has a sequential and unique plan year value that begins at 1. Year 1 of the scenario starts on the date indicated in the scenario start date, with subsequent plan years having a start date one year after the previous plan year. Each plan year's end date is calculated as the last day of that year. This prevents having gaps between years.

The scenario type determines which plan year fields are populated:

  • Budget Limitation: The amount entered for the Total Budget during the scenario creation is copied to each plan year. This value can be edited in each plan year once the scenario is added.
  • OCI Target: The value entered for the End Target OCI field will populate the Target OCI field for each plan year. This value can be edited in each plan year once the scenario is added.
  • Unlimited: Neither the Budget nor the Target OCI is populated in the plan year for this scenario type. With this type, all your protocols/triggers are executed, for all of your plan years, regardless of budget or target OCI.

When plan years are edited, the parent fields are updated if necessary. For example, if the budget of a plan year is increased, the total budget value of the scenario also increases.

When plan years are deleted from a scenario, the remaining plan years might adjust themselves to remove any gaps in dates and/or years. For example, if year 3 is deleted from a scenario that has 5 plan years, year 4 moves to year 3 and year 5 moves to year 4. The start date and end date values also change for these years, and the scenario Years field decreases from 5 to 4.