Version 7.5 build 140 Released June 13, 2017
Dayzer Change Log
New Features:
1. Download real time binding constraints mapping and shadow prices into the RT_BCName and RT_BCPrice table in the input DB. Allow to add real time binding constraints mapping in the User DB ISO_BCName table.
2. Added battery as pump storage units in Dayzer to allow battery to charge and discharge. Battery units are controlled by three parameters: starting energy, ending energy, and max storage capacity.
3. Use multiple cores (see run option FMC ) to calculate shift factor (SF). Dayzer default is to use FMC=4 cores for large pools that can reduce SF calculation time around 50% compared with FMC= 1. When combined with run option HTL >1, additional time reduction can be achieved with additional CPU and memory usage for HTO >0 cases. We suggest that the value of FMC times HTL should not exceed the number of cores on the machine.
4. Parallel calculation of line outage distribution factor (LODF) while processing mixed integer programming (MIP). This can reduce the processing time of Constraint Impact Report (F5) for large markets by 50%.
5. Allow user to (1) add new zones in the default DZR, (2) choose zone submarket to assign reserves in the default DZR, and (3) change units into a different zone in the User DB Unit_Modifications table. Note that the modification date should be before the first date of the simulation period.
6. Added in DZ script to enable user to (1) set hourly wind generation schedule, (2) scale zonal capacity factor, and (3) modify load zone temperature.
7. Added a new speed-up heuristic to reduce the time in branch-and-bound algorithm such that the mixed integer programing (MIP) simulation time can be reduced.
8. Updated shift factor DZ script to report (1) the subset of constraints that binds in the day-ahead and real time market, and (2) shift factors of inactive units.
9. Added in the Dayzer short term GUI Constraint Monitor Line Outage History Report that provides the outage history of the monitor line (lines) that is (are) defined on line constraint, contingency constraint, or interface constraint. User should pick the specific constraint and press F8 to access this report.
10. Added a new script ftrPathMinCut_IUP.dzs to solve for the minimum cut from a source node to a sink node such that if all the cut lines are on outages, there will be no flow between the two nodes.
New Run Option:
1. Added new run option FMC (Shift Factor Max Core). If set FMC =n, dayzer will use n cores to calculate shift factors. Default FMC =4.
2. Added new run option SRF (Shift Factor Report Float Percentage). If set SRF =n and SFR >0,dayzer will save shift factors of constraints having max flow percentage >= n for the corresponding hour in the Shift_Factors_Report table.
3. Updated run option VDP (Virtual DC Line Par Logic). If VDP =2, dayzer will solve for optimal fixed schedules for ALL PARs in the system (ignore given PAR schedules).
4. Updated run option IBC (ISO Binding Constraints). If IBC =2, dayzer will use ISO real time binding constraints shadow prices to calculate LMPs.
5. Updated run option OLS (Loss Factor Switch). If OLS= 3, real time loss factor will be downloaded and used in Dayzer simulation.
Improvements:
1. Added transmission related (TR) partial unit outage when line outages isolate part of the unit.
2. Reduce waiting time to sort items in different tabs in Dayzer short term GUI .
3. Check for incompletely saved PFD file when loading Dayzer short or long term simulation and show error messages.
4. Adjust contingency constraint shift factor calculation on aggregate (unit) when part of the aggregate (unit) is isolated due to the contingency element(s).
5. Allow user to search partial string in the 'Find' functionality in Dayzer short term GUI.
6. Allow user to set DMC and FMC run options in Dayzer short term GUI.
7. Show unit capacity and unit bid cost in the inactive unit report in Dayzer short term GUI.
8. Added ID to virtual import/export loop flow in constraint flow decomposition report (when right clicking on a constraint) in Dayzer short term GUI.
9. Show line flows on each element when double clicking on an interface constraint in Dayzer short term GUI.
10. Refresh day-ahead and real-time ISO binding constraint when opening a saved DZR in Dayzer short term GUI.
11. Allow user to search for specific node when adding virtual bids in Dayzer short term GUI.
12. Added inactive unit shift factor results in the Shift_Factors_Report table in the output database when using IUR =1 and SFR=1.
13. Allow user to run a unit at maximum capacity by checking the Must-Run box in Dayzer short term GUI. To enable this feature, the user must check the Must-Commit box.
14. In the Constraint Impact report (F5), emphasize the impact of hourly outages with red color.
15. Allow user to calculate ISO day-ahead or real-time LMP automatically when user adds binding constraint mapping in Dayzer short term GUI with IBC >0.
16. Change Dayzer to switch to MUC=1 if DZSCUC (MUC= 3 or 4) fails to solve. This change also applies to contingency analysis.
17. Show if a unit is defined as a zonal unit in Dayzer short term GUI when user clicks the 'View Mapping' button.
18. Fixed bugs to improve the functionality of (1) DZSCUC, (2) various run options, and (3) Dayzer/Tranzer GUI .
Dayzer User/Input-DB template updates:
1. Added the ZoneID column to the Unit_Modifications table in the following files
a) dayzer_userdb_PL.sql
b) dayzer_userdb.sql
c) template_input.dat
d) UserDB.mdb
e) UserDB_PJM_EXAMPLE.mdb
2. Added RT_BCName and RT_BCPrice tables into the inputAccess database format and dayzer_userdb.sql
3.AddedCSWS_AR to validation rule for LMP_HistoryTablelmpname column in the UserDB.mdb
4.Change database version from 3.4 to 3.5
Dayzer Output DB template updates:
1. Changed the ConstraintId Column length of the ILODF Table in the template_result.dat database file form integer to Long integer.
Default DZR updates:
a) ERCOT
1. Changed the Native load zone Disptchable Demand unit capacity to 2500 MW and named the unit 'Private Network DR' with fuel type Purchase and Heat Rate 30000. Effective bid by block is as follows:
|
Private Network DR, Unit ID 9079 |
|
|
|
BLOCK PARAMETER |
Capacity (MW) |
Cost ($/MWH) |
|
Block 1 |
0 |
0 |
|
Block 2 |
1000 |
40 |
|
Block 3 |
500 |
325 |
|
Block 4 |
1000 |
365 |
2. Changed DRC=0.95 as default option.
Tranzer Change Log
New Features:
1. Tranzer allows to define unit contingency nomogram constraint as regular contingency constraint if the unit is located at radial bus(es) in the transmission topology. The user needs to find the radial line(s) that isolate the unit, and add the line(s) as the contingency element in the contingency constraint. The contingency constraint will be the unit contingency on the monitored line.
Improvements:
1. Check incomplete nomogram definition and log error messages. If the new Tranzer is used to save previously released PFD file, the user need to look into the save PFD log and locate the error messages for 'Unit(Aggregate) contingency xxx has a unit/agg on idx = 1'. To fix the error, the user needs to open the Tranzer database in MS Access, and then go to the NOMOGRAM table to properly change the IDX value so that for TYPE = 6 or TYPE = 7 rows, the IDX value is not the smallest for the constraint ID. This is required because the first element in the nomogram must be a line or contingency constraint instead of a unit or an aggregate contingency. If the constraint has only one element, the user should either delete the constraint, or redefine it in Tranzer as unit contingency nomogram.
2. Change the default overload cost of new constraint from 99999 to 999.
3. Allow user to merge summer ratings from a summer data raw file to a winter data database when using the 'Merge Data by Raw File.' functionality.
4. Automatically suggest a new Unit ID when adding a new unit.
Databases:
a) NEPOOL
1. New load flow database 'NEPOOL Transmission Database 2017-18.mdb' based on EMS version 2613 as of October 2016.
2. Added new units and new Binding Constraints
3. Redefined some existing Pnodes
b) PJMRTO
1. New load flow database: 'PJMRTO Transmission Database 2017-18_Updated.mdb' based on 2017-18 'annual-pjm-network-model' raw file.
2. Added new units and new Binding Constraints
3. Added several flat-shape Industrial load units (INDL) corresponding with large datacenter load in Northern Virginia (DOM) and also the emerging datacenter area in Ohio (AEP).
c) ERCOT
1. New load flow database: 'ERCOT Transmission Database MAY 2017 CRR AUCTION.mdb' based on ERCOT MAY 2017 Monthly CRR Network Model.
2. Added new units and new Binding Constraints
3. Updated Planning Transmission Model 'ERCOT_PLANNING_2019_TPIT_PROJECTS_UP_II.zip' for ERCOT based on 2019 Planning network Model.
d) CAISO
1. New load flow database: 'APSSE20161122120000_WINTER_W_ITC_2017_CAISO_DB80_updated.mdb' based on CAISO DB80 CRR Model.
2. Added new units and new Day Ahead Binding Constraints.
3. Added new Interface Constraints.
4. Changed default hydro scenario to be wet year called EIA_2006.
e) MISO
1. Modified load flow database: 'MISO Transmission database 2017-18_Allocation_Updated.mdb' based on 2017-18 Annual Allocation Model.
2. Added new units and new Day Ahead Binding Constraints.
3. Updated the definition of some loop flows Aggregates.
4. Updated the definition of the PJM/MISO interface and added a pricing aggregate to preserve the definition of PJM/MISO interface as the ISO.
f) WECC
1. Modified load flow database: 'WECC Transmission Database 2013-2015.mdb'.
2. Added new units
3. Changed default hydro scenario to be wet year called EIA_2006.
g) NYPP
1. Modified Load flow database: 'NYPP Transmission Database Spring_2016.mdb' based on spring 2016 TCC Model.
2. Modified default load flow database: 'NYPP Transmission Database Summer 2015 Planning.mdb'.
3. Added new units and new Day Ahead Binding Constraints.
h) SPP
1. Modified Load flow database: 'SPP Trans Database 2016-2018_Updated_II.mdb'
2. Added new units and new Day Ahead Binding Constraints.
3. Added latest Hubs and Pnodes published by SPP.
i) PJM_MISO
1. Modified Load flow database: ' PJM_MISO Transmission Database Winter 2017.mdb based on PJMRTO Transmission Database OCTOBER 2016_updated.mdb'and 'MISO Transmission database 2016-17_Allocation_Updated_II.mdb'
2. Added new units and Day Ahead Binding Constraints.
j) ONTARIO
1. Modified Load flow database: 'ONTARIO Transmission Database_SUM_2015_REDUCED_AUG15.mdb' based on summer 2015 case.
2. Added new units.
k) PJM_NYPP
1. Modified Load flow database: 'PJM_NYPP Transmission Database 2016-17.mdb'.
2. Added new units and Day Ahead Binding Constraints.
l) SPP_MISO
1. New Load flow database: ' SPP_MISO Transmission Database 2017-18.mdb' based on 'MISO Transmission database 2017-18_Allocation_Updated.mdb'and 'SPP Trans Database 2016-2018_Updated_II.mdb'