Window FY2028–FY2033Scenario

Dimensions

11 dimensions · 178 valuesscenario: fit inside 1m

The cuts are yours. Add a dimension and it appears on the projects rail and the analysis page without anybody writing code. Some carry a role — the model reads those, so they can be renamed but not removed.

Revenue base

funding sources · one value · 28 tagged

What ultimately pays. The affordability model counts only what falls on the levy.

The model reads this one. The affordability model counts only what rolls up to a Tax-supported value. Rename it, add values, group them — all fine. It cannot be deleted, and no value may carry a meaning the engine does not know.

Values

a total at a parent includes everything beneath it
ValueSits beneathMeansRows using it
Tax-supportedFalls on the tax rate0 + 15 below
└ Property taxesTax-supportedFalls on the tax rate15
Rate-supportedPaid by a rate or fee0 + 8 below
└ Dedicated feeRate-supportedPaid by a rate or fee1
└ Parking fundRate-supportedPaid by a rate or fee2
└ Sewer user feesRate-supportedPaid by a rate or fee3
└ Water user feesRate-supportedPaid by a rate or fee2
Outside the TownComes from outside the Town0
Not identifiedNothing identified yet0 + 1 below
└ Not statedNot identifiedNothing identified yet1

Nothing is deleted in a hurry. A value in use is retired — it leaves the pickers and every existing tag survives. When two values are the same thing, merge them: every row is retagged and the old name is kept as an alias. Every one of these writes a row to Activity.