Units: | - |
Mode: | Input Only |
Multi-band: | False |
Default Value: | 0 |
Validation Rule: | ≥0 |
Key Property: | No |
Description: | Maximum number of units automatically constructed in aggregate over the planning horizon |
Facility Max Units Built sets an upper limit on the number of new units that LT Plan is allowed to build in total across the entire planning horizon. For a Facility representing a discrete single-unit project this value should be set to one, as in the following example:
Property | Value | Units |
---|---|---|
Units | 0 | - |
Max Operating Level | 500 | - |
FO&M Charge | 25,000,000 | $ |
Max Units Built | 1 | - |
Build Cost | 750,000,000 | $/kW |
Economic Life | 25 | years |
WACC | 10 | % |
You can control when the new build is allowed to occur by using the Project Start Date property as in this example:
Property | Value | Units | |
---|---|---|---|
Units | 0 | - | |
Max Operating Level | 500 | - | |
FO&M Charge | 25,000,000 | $ | |
Max Units Built | 1 | - | |
Project Start Date | 1/01/2030 | - | |
Build Cost | 750,000,00 | $ | |
Economic Life | 25 | years | |
WACC | 10 | % |
In this example at most one new unit can be built in the planning horizon, but the new build cannot occur until the year 2030. You can controls whether the unit is built in particular years with Max Units Built in Year and/or Min Units Built in Year.
If the number of units that can be built varies over time, then it is best practice to model this by entering the sum total of all units that can be built in Max Units Built once and use Max Units Built in Year and Min Units Built in Year to vary how many can be built during a given time span.
Note that LT Plan does not have to run on a calendar basis. If the planning horizon begins for example in July, it will run with planning years of June through July in which case the date tags should be consistent with this definition.
See also: