Professional Documents
Culture Documents
Plex Os Tutorial
Plex Os Tutorial
2
horizon. That is, to simultaneously solve a generation
and transmission capacity expansion problem and a
dispatch problem from a central planning, long-term
perspective. Planning horizons for the LT Plan model
are user-defined and are typically expected to be in the
range of 10 to 30 years. LT Plan appropriately deals
with discounting and end-year effects. The following
types of features are supported:
o Building new generating plant
o Retiring existing generating plant
o Multi-stage projects
o Building new AC or DC transmission lines
o Retiring existing AC or DC transmission lines
o Multi-stage transmission projects
o Expanding capacity on transmission interfaces
o Taking up new physical generation contracts
o Taking up new physical load contracts
o Deterministic or stochastic optimization
• PASA/Preschedule: PASA is “projected assessment of
system adequacy.” It distributes and optimizes available
generation capacity between regions. Preschedule is a
model of discrete, distributed maintenance, and random
(forced) outage of generators and transmission lines.
PASA and Preschedule are run together.
• MT Schedule: This is a model based on load duration
curve analysis that can be run on a week-by-week or
month-by-month basis, with full representation of the
generation and transmission system.
3
• ST Schedule: This is a full trading-period level dispatch
and pricing optimization with (optional) thermal unit
commitment.
These tools can be used as stand-alone applications, but
they may also be used in an integrated way. Plexos
provides automatic integration of these tools so that
information can be fed from one tool to the next. But
there are only certain sequences in which such tool-
information-flow may take place, as shown below.
Technical
Ramp limits, minimum stable levels
Constraints
5
Water Value Multi-band water value functions for
Curves long-term storages
4. Outcome database and log file
7
2.0 Object-oriented design
Plexos uses an object-oriented programming design. If
you are familiar with object-oriented programming
(OOP), then you have a head start. If not, then it is OK,
but you will need to consider with a few ideas:
• Main concept: Whereas traditional programming
focuses on procedures or instructions, OOP focuses on
classes and objects. OOP is a programming language
model organized around objects rather than actions and
data rather than logic.
• Class: A set of rules and definitions that specify how
objects of that class behave and what data can be
defined on those objects. A class encapsulates data and
operations that belong together, and it controls the
visibility of both data and operations. Class behavior
specifies what collections objects are allowed to belong
to, what collections they must belong to, and how those
objects interact with other objects of the same and other
types. The class Dog would consist of traits shared by
all dogs, such as breed and fur color (characteristics),
and the ability to bark and sit (behaviors). Examples of
Plexos classes include System, Company, Region,
Zone, Node, Line, Transformer, Contingency, Fuel,
Emission, Generator, and Data File.
• Object: A particular instance of a class. The class Dog
defines all possible dogs by listing the characteristics
and behaviors they can have; the object Lassie is one
8
particular dog, with particular versions of the
characteristics. A Dog has fur; Lassie has brown-and-
white fur. We may speak of a “class of an object.”
• File (object model): A file is a Microsoft Database
(.mdb) that describes a single System object, which
generally represents the power system being studied.
This is the root object to which all other objects belong.
• Collection: The System has a set of collections, one for
each class of object. All other objects belong primarily
to these System collections e.g. Companies, Generators,
Fuels, Storages, etc. For example,
o To define a generator, one adds a new Generator
object to the System's Generators collection. To
represent ownership of a generator by a company,
one adds the Generator object to the Generators
collection of the Company object that owns it.
So classes are also collections. But whereas an object
can exist in only 1 class, it may belong to several
collections and it may have several collections. For
example,
o Generator G injects at node N: Generator object G
belongs to Node N Generators collection;
o Generator G uses fuel F: Fuel object F belongs to
Generator G Fuels collection, and so Generator
object G has a Fuel collection.
9
o Transmission line A-B flows between nodes A and B:
Both Node objects A and B belong to the Nodes
collection of Line A-B.
In the figure below, the object “3node” in class “region”
(left-hand pane) has collections Reference Node,
Exporting lines, etc. (right-hand pane).
10
we need to edit the membership of either object so that
the parent object is B and the child object is A.
• Properties: Properties are used to store the physical
values associated with an object. For example, the
properties of an object “lines” include reactance,
resistance, max flow, min flow, etc.
11
Parham Jamasen pl11
Persinger Thomas pl12
Pham Hieu pl13
Quinn Patrick pl14
Reid Krysten pl15
Sun Wei pl16
VanDelinder Mike pl17
Vijayan Pradip pl18
Coakley Troy pl19
Odo Ejiofor pl20
Cronier Micheal pl21
12
5
2
4
3
1
13
2 ~ Hydro
500MW
8GWh/day
L2-3
L1-2 Max flow 1000
Max flow 1000 Max flow back 1000
Max flow back 1000
Gen_11 L1-3
600MW Max flow 1000
$15.00/MWh Max flow back 1000
1 3
Gen_3
Gen_12 200MW
300MW $85/MWh
$35/MWh
We will do seven types of operations:
• Set configuration
• Create objects (regions, nodes, lines, generators)
• Add objects to collections
• Set properties
• Set memberships
• Execute
• Examine solution
14
the screen, click in the empty box beside “Is slack
bus.”
b. Click on the word “Generator” under the “Supply
and Demand” category in the left-hand-side
“Classes” area of the screen. On the right-hand-
side “Properties” area of the screen, click on the
folder “Outages.” Then under this folder, click in
the boxes labeled “Forced outage rate,” “Outage
rating,” and “Mean time to repair.”
c. Click on the word “Data File” under the “Data”
category in the left-hand-side “Classes” area of the
screen. On the right-hand-side “Properties” area of
the screen, click in the box labeled “Attributes,” so
that the following get activated: “Enabled,”
“Growth Period,” “Method,” “Relative growth at
min,” and “Decimal places.”
d. Click on “OK” at the bottom right-hand-corner of
the screen. A message will pop up indicating that
“The changes you have made will cause the
database to be closed and reopened. Press OK to
close and reopen the database now.” Then press
OK. The database will close and reopen.
6. Create a region: Right click on “Region” (from main
tree) and select “New Region.”
15
A dialog box will appear, where you will need to
provide your new region with a name. I will assume in
what follows the new region name given is “3node.”
Click “Next,” and you will see a warning of “There is
no object in this control.” Click “OK,” and a “3node”
Properties window will appear. Close out of this
window.
7. Create node 1: Right click on “Nodes” from main tree
and select “New node.”
16
Properties window will appear. Close out of this
window.
8. Create node 2: Repeat step 7 except name the new
node “2”
9. Create node 3: Repeat step 7 except name the new
node “3”
10. Create Lines: Right click on “Lines” from main tree
and select “New line.” A dialog box will appear, where
you will need to provide your new line with a name.
Name your new line “L12” Click “Next,” and you will
see a warning of “There is no object in this control.”
Click “OK,” and a “L12” Properties window will
appear. Close out of this window. Repeat this process to
create lines L13 and L23.
11. Create generators: Right click on “Generators” from
main tree and select “New generator.” A dialog box will
appear, where you will need to provide your new
generator with a name. Name your new generator
“Gen_11”. Click “Next,” and you will see a warning of
“There is no object in this control.” Click “OK,” and a
“Gen_11” Properties window will appear. Close out of
this window. Repeat this process to create generators
Gen_12 and Gen_3.
12. Add nodes 1, 2, 3 to node collection of region:
a. Left click on “Regions” in main tree.
b. Left click on “Nodes” in membership tree.
c. Left click in first row of “Node” column in data
grid. When you do this, you will see a drop-down
17
menu appear on the right-side of the cell. Left-click
on it, and select “1”.
d. Left click in the first row of the “Region” column
in data grid. When you do this, you will see a drop-
down menu appear on the right-side of the cell.
Left click on it, and select “3node”.
e. Repeat steps c and d except use row 2, selecting
“2” and “3node” for the node and region columns,
respectively.
f. Repeat steps c and d except use row 3, selecting
“3” and “3node” for the node and region columns,
respectively.
The screen should appear as below.
19
16. Add node 1 to line L13’s from node collection:
Repeat steps 14-c and d, except select L13 in step 14-c
and select “1” in step 14-d. The screen should appear as
below.
f_Attributes
Max VOM Forced Outage Mean Time
Fuel Price Heat Rate Min Stable
Generator Units Capacity Charge Outage Rate Rating to Repair
($/MMBTU) (BTU/kWh) Level (MW)
(MW) ($/MWh) (%) (MW) (hrs)
Gen_11 1 700 2 10000 0 0 5 0 100
Gen_12 1 400 7 9000 0 0 2 0 80
Gen_3 1 200 7 1200 0 0 1 0 40
22
It is of interest that the outage date provided above
enables one to compute MTTF via
MTTR MTTR
FOR MTTF MTTR
MTTF MTTR FOR
For example, Gen_11 would have MTTF of
100
MTTF 100 1900hrs
0.05
from which we can also obtain transition rates λ ,µ from
1 1
0.00052632/
1900
1 1
0.01/
100
23
24. Create or obtain a load data file: To create a load
data file, use Excel and create a .csv file having the
following format:
Year Month Day 1 2 3 4 … 24
26
29. End case construction: You have completed
constructing the case. If you click on “System” at the
top of the main tree, and then click on the “Objects” tab
at the top of the data grid, it should appear as below.
27
This will lead to the page at
www.plexos.info/wiki/index.php?n=Main.STSchedule,
where you can read the following information (yellow
shading is added to highlight some statements).
Short Term (ST) Schedule
Main Trail Page | Class Reference | ST Schedule Class
Description: ST Schedule simulation phase
Detail:
1. ST Schedule
ST Schedule is mixed-integer programming (MIP) based chronological optimization.
It can emulate the dispatch and pricing of real market-clearing engines, but it
provides a wealth of additional functionality to deal with:
unit commitment;
constraint modeling;
financial/portfolio optimization; and
Monte Carlo simulation.
28
Typical Week
One week is modeled each per month in the horizon and results are applied
to the other weeks.
When selecting the planning horizon, the step type is chosen from years, months,
weeks, or days. But the ST Schedule Step Type must be either weeks, days, hours,
or minutes. The reason for this is related to the way in which PLEXOS sets up and
solves the ST Schedule problem. At runtime PLEXOS:
Note further, that the outcome of the simulation can be influenced by the size of the
ST step when there are significant intertemporal aspects. This is because the state
of the system, e.g. generator unit commitment, is recorded and carried over from
one step to the next, but each step does not look-ahead to the next. Hence unless
the model has no intertemporal elements, e.g. when performing a pure market-
clearing emulation, it is recommended that the ST be run in steps of no less than
one day at a time.
29
To further improve the optimization of unit commitment decisions you can configure
ST Schedule to use a look-ahead period ahead of each step. This allows the step
size of ST Schedule to be kept small (e.g. a day at a time) but sufficient look-ahead
maintained for unit commitment decisions.
2.2. Typical Week
When ST Schedule is run in typical week mode, the horizon options are simplified.
The simulation will always run across the whole planning horizon, and the only
option to chose is the size of each step of the ST Schedule i.e. how many trading
periods should be ‘solved’ at once. Typically, large models should be run in daily or
evenly hourly steps, smaller models can run in weekly steps.
Running in this mode reduces the amount of simulation work for ST Schedule by
more than a factor of four, but PASA and MT Schedule are still run in exactly the
same manner.
Note that solution data for the typical week is written into the solution database, and
the PLEXOS interface will explode those data out so that a full chronology can be
viewed. This means that the size of the solution database is also reduced when ST
Schedule is run in this mode. Summary data (daily, weekly, monthly, annual) are all
calculated based on the mapping of typical weeks to trading periods i.e. the daily
data for a day that was not part of a typical week, is taken from the day of the same
type in the typical week that was run. Thus, summary data are complete, but may
not match input data such as total energy, and peak demand.
The selection of week inside the month is controlled by the option Typical Week.
The beginning day of week is set by the Week Beginning option. When set to
automatic, the week begins on the same day of week as the first day of the planning
horizon.
31
Model Initialization Started -->
- Random Number Seed = 1719307187 (enter this number to repeat this sequence).
- Discount Rate = 0.00 %
Secondary Compilation Started:
Secondary Compilation Completed. Time: 0:00:02.560
Horizon is 1 day in duration.
Requesting licenses:
- MOSEK 5.0.0.93
- PLEXOS 5.100 R01
- PLEXOS Version 5
- MOSEK Base Product
- PLEXOS Support for MOSEK
- Machine Name: PLEXOS
- Physical Memory: 3.93 GB
- CPU Type: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz
- CPU Count: 2
Licenses received.
In-Memory Cache Setup Started
----------------------------------------------------------------------------
File Periods Bands Total Time
per Day Records (sec.)
----------------------------------------------------------------------------
load.csv 24 1 24 0.05
----------------------------------------------------------------------------
In-Memory Cache Setup. Time: 0:00:00.499:
- 0 reallocations
- 10000.00 kB
- 0.00 % efficiency
<-- Model Initialized. Time: 0:00:05.429
Preschedule -->
Preschedule step 1 of 1: Tuesday, January 01, 2002 - Tuesday, January 01, 2002 -->
<-- Preschedule step 1 of 1. Time: 0:00:00.051
----------------------------------------------------------------------------
Minimization Objective Function:
Linear:....................................... 0.0000000000e+000
----------------------------------------------------------------------------
Component Time (sec.) Contrib. (%)
----------------------------------------------------------------------------
Setup..................................... 0:00:00.157 64.88 %
Modify.................................... 0:00:00.000 0.00 %
Solution.................................. 0:00:00.000 0.00 %
Write..................................... 0:00:00.000 0.00 %
Other..................................... 0:00:00.085 35.12 %
----------------------------------------------------------------------------
Peak Memory............................... 44.22 MB
Current Memory............................ 43.40 MB
----------------------------------------------------------------------------
Preschedule Completed. Time: 0:00:00.243
<-- Preschedule
32
ST Schedule -->
----------------------------------------------------------------------------
OPF Element Count
----------------------------------------------------------------------------
Slack Bus................................................................"3"
Nodes (busbars)............................................................3
Nodes in Service...........................................................3
Load Points................................................................1
Generation Injection Points................................................2
Total Injection Points.....................................................3
Lines (branches)...........................................................3
Lines in Service...........................................................3
AC Lines...................................................................3
Flow Limits >= 0 kV........................................................3
Flows Modeled >= 0 kV......................................................3
DC Lines...................................................................0
Phase Shifters.............................................................0
Phase Shifters in Service..................................................0
Generators.................................................................3
Generators in Service......................................................3
Unique AC Paths............................................................3
Modeled AC Paths...........................................................3
Required PTDF..............................................................9
Finished 3 Projections. Stored 6 PTDFs out of 9. Time: 0:00:00.062
Automatic zonal compression of shift factors:= 0.00%
Started ST Schedule Step 1 of 1: Jan 1, 2002 12:00:00 AM - Jan 1, 2002 11:59:00 PM
----------------------------------------------------------------------------
Task Size:
Columns (variables)..................................... 192
Integers................................................ 0
Rows (constraints)...................................... 144
Non-zero coefficients................................... 432
Memory (MB estimated)................................... 32.90
----------------------------------------------------------------------------
Completed ST Schedule Step 1 of 1. Time: 0:00:01.116
------------------------------------------------------------------------------------------------
Regional Summary:
------------------------------------------------------------------------------------------------
Region/Area Demand Generation Net Export Gen. Cost Load Cost USE/Dump Price
(GWh) (GWh) (GWh) ($Mln's) ($Mln's) (MWh)
------------------------------------------------------------------------------------------------
3node 29.41 29.41 0.00 868.52 294.13 354.07 $10,000.00
------------------------------------------------------------------------------------------------
33
Linear Relaxation:............................ 9.0392566099e+008
Cost of Integerization:....................... 0.0000000000e+000
Relative Cost of Integerization:.............. 0.00 %
----------------------------------------------------------------------------
Component Time (sec.) Contrib. (%)
----------------------------------------------------------------------------
Setup..................................... 0:00:00.762 44.65 %
Modify.................................... 0:00:00.028 1.69 %
MOSEK 5.0.0.93:........................... 0:00:00.001 0.11 %
----------------------------------------------------------------------------
- Dual Simplex........................... 0:00:00.001 100.00 %
----------------------------------------------------------------------------
Solution.................................. 0:00:00.233 13.69 %
Write..................................... 0:00:00.468 27.42 %
Other..................................... 0:00:00.212 12.44 %
----------------------------------------------------------------------------
Peak Memory............................... 61.37 MB
Current Memory............................ 60.76 MB
----------------------------------------------------------------------------
Summary Solution Cached. Time: 0:00:00.006
<-- Model "Base" Completed. Time: 0:00:09.340
34
The system load level can be observed by itself as below:
35
The generation level of the three units may also be
observed:
36
This result may be assessed in comparison to the
generator input data, repeated below for convenience.
f_Attributes
Max VOM Forced Outage Mean Time
Fuel Price Heat Rate Min Stable
Generator Units Capacity Charge Outage Rate Rating to Repair
($/MMBTU) (BTU/kWh) Level (MW)
(MW) ($/MWh) (%) (MW) (hrs)
Gen_11 1 700 2 10000 0 0 5 0 100
Gen_12 1 400 7 9000 0 0 2 0 80
Gen_3 1 200 7 12000 0 0 1 0 40
37
And the price may be observed.
38
4. LT Plan Formulation Description
The Plexos description of the LT Plan model formulation
is below.
LT Plan Formulation
The capacity expansion problem is formulated in PLEXOS as a Mixed-Integer Linear
Program (MILP or MIP for short).
To illustrate the very core of this formulation, we develop the following simplified
formulation.
NOTE: The following description is illustrative only, and shows only the core of the
LT Plan MIP formulation.
Definitions
D Discount rate
39
Unitsg Existing number of generating units g
Optimization problem
40
of the economic life of the unit. The discount rate used will be a system discount
rate, whereas the WACC will be project-specific.
End-year Treatment
It is important in the LT Plan formulation that the model does not inappropriately
consider the end of the planning horizon to also be the 'end of time'. In the above
basic formulation we have implicitly assumed that LT Plan has an infinite horizon. In
practice, the model will have a finite horizon such as 20 or 30 years. We therefore
have to take account of so-called end year effects.
Without some method for dealing with end-year effects, the model will in the last
years of the horizon only build generators with low build costs (even if their marginal
generation costs are high). This is because the average cost of generation between
build year and the end of the planning horizon - including build costs - will be lower
for such generators.
We therefore assume that the last year of the horizon is repeated an infinite number
of times. The objective function is expanded by the cost of the years after the final
horizon year, which equals the sum of the present values of generation costs.
Solution approach
Problem Size Reduction
The capacity expansion 'sub-problem' uses annual build/retire decisions. Thus the
number of these elements in the formulation is relatively small. No problem size
reduction is required to these elements. However, if all decisions are integer (as
controlled by the Optimality option), then the problem can become very hard to
solve. You can reduce the number of integers by selectively turning off integer
optimization at the Generator level using the Generator . Expansion Optimality
property.
LT Plan (by default) spans the whole simulation planning horizon in a single
optimization 'step'. For realistically-sized power systems and long planning horizons
this may lead to extremely big problems in the production cost sub-problem. To
make this problem tractable, two problem size reduction techniques can be used:
LT Plan always uses a LDC approach. The controls for the level of detail in this
method are Step Type, and Blocks.
Solution method
The key LT Plan variables (whether to build or retire generators, or build/retire lines)
are integer. As a result a mixed-integer solver is required to obtain an integer
optimal build/retirement solution.
PLEXOS also allows LT Plan to be solved using a Linear Relaxation. This has the
advantage of faster execution, as well as the ability to report the shadow price of
capacity. For longer terms (>20yr) analysis, a Linear Relaxation may be sufficient.
However the Linear solution is not suitable for passing through to MT/ST, as these
require integer units.
=======================
Generation Expansion
- Defining a Generation Project
- Timing Constraints
- Generation Cost
- Firm Capacity
- Forced Outages and Maintenance
- Hydro Model
- Retirements
- Planned Retirements
- Economic Retirements
- Plant Staging
- Mututally Exclusive Projects Constraint
- Project Staging Constraint
Defining a Generation Project
To correctly define a generation expansion candidate you must define all of the
following:
42
Max Capacity in MW
Max Units Built
Build Cost which in $/kW
Economic Life in years
WACC which is the discount rate applied to the project's costs
This is in addition to the properties that define the production cost of the generator,
such as Heat Rate, Fuel Price and VO&M Charge.
Here is an example:
Property Value Unit
WACC 12 %
You may optionally define the Technical Life if the project's life is limited.
If some units already exist at the power station, or are scheduled to come into
service at known times, you can defined Units as well. These 'incubent' units are
then in addition to those that might be added from the Max Units Built
Where a project starts and finishes within the horizon, the entire build cost is
incurred within the horizon (in the year of the build), otherwise an annuity is
computed, and the last year assumed to continue in perpetuity. The properties
Economic Life and WACC are used to compute this annuity. To change this
behaviour adjust the property End Effects Method.
Timing Constraints
The earliest possible start date of a project is set using the Project Start Date
property. The number of units that can be built is set by the property Max Units Built,
and this can vary across time to vary the total number of units built in aggregate.
The property Max Units Built in Year limits the number of units built in any particular
year.
43
Any number of units (up to the Max Units Built) can be forced into service using the
Min Units Built. You can also force a minimum number of units to be built in a
particular year using the Min Units Built in Year property.
More complex timing constraints are possible, including linking the build/retire
decisions of different generators by using generic Constraints, the section Plant
Staging.
Generation Cost
The production cost model of LT Plan is identical to that of MT Schedule, and thus is
fully featured including fuels, emissions, and ancillary services modeling.
Firm Capacity
If your model includes constraints on capacity reserves (generation capacity over
and above peak load), you may need to account for the firm capacity of generators,
which can be different to the 'raw' installed capacity e.g. for wind plant. This is
controlled by the Generator property Firm Capacity.
Forced Outages and Maintenance
Generation capacity in LT Plan Capacity Sub-problem is derated by the forced
outage rate. Capacity in the Production Cost Sub-problem is derated by the
maintenance rate. For example, if a 100 MW plant has an average maintenance rate
of 7.5%, and forced outage rate of 2%, then the LT Plan production cost model will
assume:
There are two options for how forced outages are accounted for in the Production
Cost Sub-problem:
Hydro Model
44
LT Plan includes the same hydro storage optimization as MT Schedule. Thus it is
possible to model any number of storages, waterways, junctions, headponds etc, in
cascading networks. Storage can be optimized over the long term, with hydro
balance occuring each LDC (e.g. monthly).
Units 1 -
Units 0 - 1/01/2016
In this example the generator is in service from the start of the planning horizon (no
date given for Units = 1), and goes out of service on January 1, 2016.
The retirement cost is optional in this case, so the following data are valid:
Property Value Unit Date From
Units 1 -
45
Note how a date can be applied to the Max Units Retired so that LT Plan does not
retire the unit before that time.
Plant Staging
Often a "project" consists of multiple stages and there is a defined staging order and
unique performance parameters for each stage. This is modeled in LT Plan using
one Generator object per stage, and with the setting of appropriate build and retire
inputs, and finally with generic constraints to link the stages.
Assume also that the open-cycle stage can be built "immediately" whereas the
combined-cycle can only be in service at or after 1/01/2012.
Firstly we create generator objects to represent the two stages (GT and CCGT), and
a generator to represent the option to build the CCGT in one step.
Generator Property Value Unit Date From
CCGT_stage1 Units 0 -
CCGT_stage1 WACC 12 %
46
Generator Property Value Unit Date From
CCGT_stage2 Units 0 -
CCGT_stage2 WACC 12 %
CCGT Units 0 -
CCGT WACC 12 %
Note that the heat rate is allowed to change over time, as is the build cost and any
other parameter, however for this example we assume static data. Note also that the
"CCGT_stage1" generator must allow retirement by setting the Max Units Retired
property. This is so that it can be superceded by the stage 2 plant.
47
t GenBuildi t + t GenBuildj t 1
CCGT_mutually_exclusive RHS 1 -
Units Built
CCGT_mutually_exclusive.Generators.CCGT_stage1 1.0 -
Coefficient
Units Built
CCGT_mutually_exclusive.Generators.CCGT 1.0 -
Coefficient
Here we create the Constraint object "CCGT_staging", then add the Generators
"CCGT_stage1" and "CCGT_stage2" to the Constraint.Generators collection. We
then define the following data:
Membership Property Value Unit Date From
CCGT_staging RHS 0 -
Note the use of Units Built in Year Coefficient and Units Retired in Year Coefficient,
which creates constraints for each year, rather than summing across all years as in
the mututally exclusive projects case above.
48
=========================
Transmission Expansion
- Building Transmission Lines
- Expanding Interfaces
Building Transmission Lines
Transmission line expansion, retirement and multi-stage projects in LT Plan works in
much the same way as Generation Expansion with the following restriction:
The Transmission option OPF Method must be set to "Variable Shift Factor
OPF". This is because the dynamic addition/deletion of lines from the system
is supported only by that OPF method. Note that this procludes transmission
expansion from being used on very large transmission systems over long time
periods (though snapshot studies of large systems are possible).
Expanding Interfaces
Expansion of existing transmission interfaces is a feature available to both OPF
methods in PLEXOS (i.e. it can be done on any sized system). Expansion is done in
continuous units of megawatts, thus the only data required are:
5. HW Assignment
Your HW assignment is due Friday, Nov 7. This HW is a
“warm-up” to the project I will ask you to perform.
49
1. Go through the above steps to perform construction
of the case, then execute the ST Schedule, and
observe the solution. You should get exactly what is
shown above. There is no need to turn anything in for
this step. I am simply asking you to do it in order to
become familiar with the software.
2. I have loaded the final case I obtained onto the course
website. You may use it to begin work on this step (if
you did #1 correct above, this will be a duplicate
copy to what you developed). Go through the below
steps to perform a LT Plan study. Report your
solution in terms of what units were added and how
much it cost.
50
b. Build a new object “LTP setttings” which belongs to “LT
Plan” class.
We can set the properties for the long term planning
model.
51
C. Add “LTP setting” into model “LTP.”
52
d. Build .csv file that contains 20‐year load level. Then
build a new load file object in the same way as before.
Then build a scenario and add the data file to the
scenario by setting its property.
Add the new scenario “LTP scenario” to the model “LTP”.
e. Add possible new generators that we are going to build
in the planning horizon. Add them to the region “3node.”
Edit their properties.
53
f. Build a new object in the “Horizon” class. Set the
horizon to be 7305 steps of I day to run a 20‐year long
term planning.
54
g. Execute and explore solution.
55