jROS UG HTC

History
Spectrum Power Preface
Hydro-Thermal Hydro Thermal Coordination 1

Coordination (HTC)
Operations 2
6.1
Power System Model 3
User Guide
Appendices 4
References 5
Note
Please observe safety notes and warnings for your own safety.
Disclaimer of Liability Copyright

Siemens AG shall not be liable for any incidental or consequential Copyright © Siemens AG 2010. All rights reserved
damages resulting from the performance or use of this product. This document is protected by German Copyright law and international
This document has undergone extensive technical approval before being contracts as intellectual property of the Siemens AG. The document
released. We review this document at regular intervals, and include contains confidential information of Siemens AG which is protected by
appropriate amendments in subsequent issues. While every effort has patent, copyright, trademarks or otherwise as inventions, trademarks or
been made to keep the information herein as accurate and up to date as creations of Siemens AG. The reproduction, duplication, transmission or
possible, Siemens AG assumes no responsibility for errors or omissions use of these documents or its contents is not permitted without express
or for damages resulting from the use of the information contained herein. prior written consent of the Siemens AG.
The content of this document is for information only and in consequence,
Siemens AG cannot take over liability resulting in any way from the use of Registered Trademarks
this document or parts thereof. Spectrum Power(TM) 4® is a registered trademark of Siemens AG. An
These contents shall not become part of or modify any prior or existing unauthorized use is not permitted.
agreement, commitment or relationship. The sales contract contains the The remaining descriptions in this documentation/information could be
entire obligations of Siemens AG. The warranty contained in the contract trademarks, the use of which by third parties for their aims could infringe
between the parties is the sole warranty of Siemens AG. Any statements upon the owner’s rights.
contained herein do not create new warranties or modify the existing
warranty.
Siemens AG reserves the right to update this documentation from time to
time and especially to adapt it to the current status of the product
Spectrum Power(TM) 4 or to change it without prior notice.
Document version: 3.0
Date of issue: 06.2011
Product version: 1.0
History
History
Date Modification
1.0 06.2010 initial version
2.0 07.2010 Update after FAT
2.01 12.2010 Appendices added, minor text changes.
2.1 02.2011 CRs included
3.0 06.2011 MILP Description added to Appendixes, attributes updated, user setting
and run manager progress added
3.1 01.2012 Update for Patch 12
4.0 04.2012 Update for Patch 13
5.0 08.2012 Update for Patches 14 & 15
5.1 11.2012 Finalize Patches 14 & 15 etc
5.2 01.2013 Reviewed and finalized
6.0 08.2013 Updated with features for Patch 16
6.1 08.2013 Updated for PLN SAT
2 Hydro Thermal Coordination (HTC), User Guide

Edition 08.2013
Preface
Preface
Safety Notes
This manual does not constitute a complete catalog of all safety measures required for operating the product
in question because special operating conditions might require additional measures. For application specific
safety measures refer to the respective project documentation. However, it does contain notes that must be
adhered to for your own personal safety and to avoid damage to property. These notes are highlighted with a
warning triangle and different keywords indicating different degrees of danger as stated in the Warning
Conventions.
Warning
WARNING indicates a potentially hazardous situation which, if not avoided, could result in death or serious
injury.
 Please follow all advice instructions to prevent death or serious injury.
Caution
CAUTION used with the safety alert symbol indicates a potentially hazardous situation which, if not avoided,
may result in minor or moderate injury.
 Please follow all advice instructions to prevent minor or moderate injury.
Note
NOTE used without the safety alert symbol indicates a potential situation which, if not avoided, may result in
an undesirable result or state.
Qualified Personnel
Only competent and authorized personnel should work with this product after becoming thoroughly familiar
with all warnings, safety notices, operating instructions and maintenance procedures.
Use As Described
The product must not be used for any other purposes than that described in the technical documentation. If it
is used together with third-party devices and components, these must be recommended or approved by
Siemens AG. The successful and safe operation of this product is dependent on adequate transportation and
proper handling, storage, installation, operation and maintenance.
Hydro Thermal Coordination (HTC), User Guide 3

Edition 08.2013
Preface
Scope
This Reference Guide provides specific and detailed information on how to use a particular product or product
component:
 Typical workflows and operations
 Description of all user interfaces and displays
Note
Please note that the screenshots used in this document contain sample data which may not be available in
some systems.
Typical Users
This Reference Guide is designed for users that are already familiar with operational and technical aspects of
power generation and power transmission and distribution as well as Spectrum Power product concepts:
 System Engineers
The System Engineer is able to install and to customize the system. He needs deep knowledge about
the internal structures and processes of the HTC-software component.
 Operators
The Operator is using the HTC-software. Therefore he needs to know how the HTC has to be operated.
 Data Engineers
The Data Engineer translates the real generation plants and/or energy market components to the data
model of the HTC-software. He maintains the HTC data model.
 Key Users
The Key User is responsible for a special technical area which is related to the HTC-software. The Key
User has to know the specific functions of the HTC-software in detail.
Structure of this Manual
 Introduction:
Basic information about the HTC-software
 Workflow / Operations:
Main use cases, workflows and operational steps for optimal use of the HTC-software
 References:
Reference to other documents

Edition 08.2013
Preface
Documentation Conventions
Example Meaning
File > Open Selecting the menu item Open on the File menu
F1 Pressing the F1 function key on the keyboard
Control+o Holding down the Ctrl key and pressing the letter o on the keyboard
Control+Shift+o Holding down the Ctrl key and the Shift key and pressing the letter o on the keyboard
Left-click Clicking the left mouse button
Right-click Clicking the right mouse button
Shift-Left-click Holding down the Shift key on the keyboard and clicking the left mouse button

Edition 08.2013
Table of Contents
Table of Contents
History................................................................................................................................................................................ 2
Preface ............................................................................................................................................................................... 3
Table of Contents.............................................................................................................................................................. 6
1 Hydro Thermal Coordination .............................................................................................................................. 10

1.1 Introduction ........................................................................................................................................... 10
1.2 Keyboard Shortcuts .............................................................................................................................. 11
1.3 Application User Interface ..................................................................................................................... 13
2 Operations ............................................................................................................................................................ 16
2.1 Starting to Work with HTC..................................................................................................................... 16
2.2 Performing a calculation........................................................................................................................ 18
2.3 System Tuning ...................................................................................................................................... 23
2.4 Application Tuning ................................................................................................................................ 24
2.5 Inspection of results via user interface .................................................................................................. 26
2.6 Export of Results to Excel ..................................................................................................................... 30
2.7 Manual Update of Input Data via User Interface ................................................................................... 32
2.8 Update of Input Data via Excel.............................................................................................................. 34
2.9 Modifying Charts Settings in the User Interface .................................................................................... 36
2.10 Creating User UI displays ..................................................................................................................... 38
2.11 Modifying User UI displays.................................................................................................................... 40
2.12 Modifying the Data Model ..................................................................................................................... 43
2.13 Creating the Data Set (Variant)............................................................................................................. 46
2.14 Saving the Data Set (Variant) to a File.................................................................................................. 47
2.15 Restoring the Data Set (Variant) from a File ......................................................................................... 48
2.16 Deleting the Data Set (Variant) ............................................................................................................. 50
2.17 Variant Management............................................................................................................................. 51
2.18 Workspaces, Roles and Role Assignment ............................................................................................ 54
2.19 Other Administrative Tasks ................................................................................................................... 59
3 Power System Model ........................................................................................................................................... 60

3.1 Notation................................................................................................................................................. 60
3.2 Data Model and Data Types ................................................................................................................. 61
3.3 Power System Model Overview ............................................................................................................ 62
3.3.1 General Components ........................................................................................................... 62
3.3.2 Thermal Topology ................................................................................................................ 63
3.3.3 Hydro Topology.................................................................................................................... 65
3.4 General Parameters.............................................................................................................................. 69
3.4.1 Time Steps ........................................................................................................................... 69
3.4.2 Planning Horizons ................................................................................................................ 69
3.5 System Features ................................................................................................................................... 70

Edition 08.2013
Table of Contents
3.5.1 Areas and Exchanges Among Areas ................................................................................... 70

3.5.2 Regulation Services and Reserves ...................................................................................... 71
3.5.3 Area and System Costs........................................................................................................ 75
3.6 Thermal Subsystem Features ............................................................................................................... 77
3.6.1 FuelTypes ............................................................................................................................ 77
3.6.2 FuelContracts....................................................................................................................... 77
3.6.3 FuelStocks ........................................................................................................................... 79
3.6.4 Fuel Restrictions on More than One Fuel............................................................................. 79
3.6.5 ThermalGeneratingUnits ...................................................................................................... 80
3.6.6 Energy Consumption of ThermalGeneratingUnits during Operation .................................... 80
3.6.7 Starting and Stopping of ThermalGeneratingUnits............................................................... 84
3.6.8 Iterpretation of the start-up power curve .............................................................................. 87
3.6.9 Stable Operation of ThermalGeneratingUnits ...................................................................... 88
3.6.10 Limited Ramp Rate .............................................................................................................. 89
3.6.11 Fuel Consumption of Thermal Units During Stable Operation.............................................. 90
3.6.12 Fuel Consumption Limitations for Co-firing .......................................................................... 90
3.6.13 Fuel Consumption of Thermal Units During Start-up............................................................ 90
3.6.14 Cost Determination of ThermalGeneratingUnits................................................................... 91
3.6.15 Thermal Plants ..................................................................................................................... 92
3.6.16 Common Steam Header Plants............................................................................................ 93
3.7 Hydro Subsystem Features................................................................................................................... 95
3.7.1 Management of Hydro Chains.............................................................................................. 95
3.7.2 The Economic Value of Water.............................................................................................. 98
3.7.3 Starting and Stopping of Hydro Units ................................................................................. 101
3.7.4 Start-up Cost of Hydro Units .............................................................................................. 101
3.7.5 Stable Operation of Hydro Units......................................................................................... 101
3.7.6 Simultaneous operation of turbines and pumps ................................................................. 103
3.7.7 Hydro Plants....................................................................................................................... 103
3.7.8 Hydro Valleys ..................................................................................................................... 104
3.8 Market Features .................................................................................................................................. 105
3.8.1 Electricity Contracts ........................................................................................................... 105
3.9 Other Features .................................................................................................................................... 109
3.9.1 Initial Conditions................................................................................................................. 109
3.9.2 Consecutive Planning ........................................................................................................ 111
3.9.3 Final Conditions / Coupling to Resource Optimization (RO) .............................................. 112
3.9.4 UnitRestrictionGroups with Specific Limitations ................................................................. 112
3.9.5 Tuning of the HTC-algorithm .............................................................................................. 114
3.9.6 Constraint Priorities, Hard and Soft Constraints................................................................. 115
3.9.7 Cplex infeasibility in RunManager messages..................................................................... 116
4 Appendixes......................................................................................................................................................... 117
4.1 Classes ............................................................................................................................................... 117
4.2 Attributes............................................................................................................................................. 117
4.2.1 Area ................................................................................................................................... 117
4.2.2 Channel.............................................................................................................................. 119
4.2.3 CogenInterchange.............................................................................................................. 120

Edition 08.2013
Table of Contents
4.2.4 CogenStorage .................................................................................................................... 121

4.2.5 CogenZone ........................................................................................................................ 121
4.2.6 CombinedCyclePlant.......................................................................................................... 122
4.2.7 CommonSteamHeader ...................................................................................................... 123
4.2.8 EmissionRestrictionGroup.................................................................................................. 123
4.2.9 EnergyContract .................................................................................................................. 124
4.2.10 FuelContract....................................................................................................................... 125
4.2.11 FuelMarket ......................................................................................................................... 126
4.2.12 FuelRestrictionGroup ......................................................................................................... 127
4.2.13 FuelStock ........................................................................................................................... 128
4.2.14 FuelType ............................................................................................................................ 128
4.2.15 HydroGeneratingUnit ......................................................................................................... 128
4.2.16 HydroPlant ......................................................................................................................... 132
4.2.17 HydroValley........................................................................................................................ 133
4.2.18 MPROFstep ....................................................................................................................... 133
4.2.19 PowerLine .......................................................................................................................... 134
4.2.20 Reservoir............................................................................................................................ 135
4.2.21 SAParam............................................................................................................................ 137
4.2.22 Spillway .............................................................................................................................. 139
4.2.23 SpotMarket......................................................................................................................... 140
4.2.24 System ............................................................................................................................... 141
4.2.25 ThermalGeneratingUnit ...................................................................................................... 143
4.2.26 ThermalPlant...................................................................................................................... 151
4.2.27 UnitRestrictionGroup .......................................................................................................... 151
4.3 Enumerations ...................................................................................................................................... 153
4.3.1 EnumAvailability................................................................................................................. 154
4.3.2 EnumAvailabilityHGU ......................................................................................................... 155
4.3.3 EnumAvailHRSGSF ........................................................................................................... 155
4.3.4 EnumBoolean..................................................................................................................... 155
4.3.5 EnumCgiState .................................................................................................................... 156
4.3.6 EnumCommitment ............................................................................................................. 156
4.3.7 EnumContractDirection ...................................................................................................... 156
4.3.8 EnumContractProduct ........................................................................................................ 157
4.3.9 EnumContractQuality ......................................................................................................... 157
4.3.10 EnumContractState............................................................................................................ 157
4.3.11 EnumContractType ............................................................................................................ 157
4.3.12 EnumDate .......................................................................................................................... 158
4.3.13 EnumDateTime .................................................................................................................. 158
4.3.14 EnumDateTimeSec ............................................................................................................ 158
4.3.15 EnumErgModelType .......................................................................................................... 158
4.3.16 EnumFuelMix ..................................................................................................................... 158
4.3.17 EnumFuelMode.................................................................................................................. 158
4.3.18 EnumFuelSelector.............................................................................................................. 159
4.3.19 EnumGenerationType ........................................................................................................ 159
4.3.20 EnumGenerationTypeHGU ................................................................................................ 160
4.3.21 EnumGenerationTypeTGU................................................................................................. 160

Edition 08.2013
Table of Contents
4.3.22 EnumHTCCalcMode .......................................................................................................... 160

4.3.23 EnumMIPGapSelector ....................................................................................................... 161
4.3.24 EnumOptimizationType ...................................................................................................... 161
4.3.25 EnumPlanHoriz .................................................................................................................. 161
4.3.26 EnumPlantType.................................................................................................................. 161
4.3.27 EnumPowerLinePolicy ....................................................................................................... 162
4.3.28 EnumProgramState............................................................................................................ 162
4.3.29 EnumReservoirContentUoM .............................................................................................. 163
4.3.30 EnumRsrvClEnergy............................................................................................................ 163
4.3.31 EnumRsrvCont................................................................................................................... 163
4.3.32 EnumRsrvModule............................................................................................................... 164
4.3.33 EnumSpillwayType............................................................................................................. 164
4.3.34 EnumSpotPolicy................................................................................................................. 164
4.3.35 EnumStartCond.................................................................................................................. 164
4.3.36 EnumSUPsel...................................................................................................................... 165
4.3.37 EnumSwitch ....................................................................................................................... 165
4.3.38 EnumSwitchConstraint ....................................................................................................... 165
4.3.39 EnumSwitchingPolicy ......................................................................................................... 165
4.3.40 EnumSwitchRegimes ......................................................................................................... 166
4.4 Data Types.......................................................................................................................................... 167
4.4.1 Numeric values .................................................................................................................. 167
4.4.2 Enumerations ..................................................................................................................... 167
4.4.3 Date/Time........................................................................................................................... 167
4.4.4 Schedules .......................................................................................................................... 168
4.4.5 Curves................................................................................................................................ 169
4.5 Linear Programming............................................................................................................................ 170
4.5.1 Variables ............................................................................................................................ 170
4.5.2 Constraints ......................................................................................................................... 171
4.5.3 Penalties ............................................................................................................................ 176

Edition 08.2013
1 Hydro Thermal Coordination
1.1 Introduction

1.1 Introduction
The tool Hydro-Thermal-Coordination (HTC) supports the tasks of day ahead scheduling and short term
scheduling, intraday scheduling, and final scheduling. It is part of the package joint Resource Optimization
and Scheduler (jROS) of Spectrum Power. HTC is a decision support system that minimizes the cost of
power system operation and maximizes the profits on the energy markets by suggesting the generation
schedule for all power plants and trade volumes considering the constraints of the resources in the power
system. These generation schedules are results of a mathematical optimization in the field of operations
research, derived by mixed integer linear programming (MILP). It combines the tasks known as Unit
Commitment, Hydro Scheduling and Hydro Thermal Co-ordination into one optimization, resulting in better
overall performance of operation.
This document is intended for end-users, who work with the tool (day-ahead planer, dispatcher, study
engineers).
Detailed information on the HTC data model is given in the document ‘Technical Specification HTC’.

Edition 08.2013
1.2 Keyboard Shortcuts
Note
Keys may be all lowercase, all uppercase or mixed lowercase and uppercase unless explicitly described.
Base Frame is the HTC applications main window, in which the application parts – panels – are placed.
Base Panel is the HTC applications main part of the window, where the context information is displayed.
Base Frame
To display Press
Refresh F5
New Window F12
Set Focus on Tree CTRL+T
Show / Hide Tree F8
Base Panel
To Perform Press
Cancel Edit Object CTRL+Q
Edit Object CTRL+E
New Object CTRL+N
Quick Save Object (without comment) CTRL+S
Export to Excel Right Click
Navigating in object tree
To Press
Move Down ↓
Move Up ↑
Open Sub-tree RETURN, or Right click
Close Sub-tree Double click right
Toggle between Result and Model pane CTRL+J
Navigating in tables
To Press
Move Down ↓
RETURN
Move Up ↑
SHIFT+RETURN
Move Left 
SHIFT+TAB
Move Right 
TAB

Edition 08.2013
Editing in tables
To Press
Insert new row CTRL+’+’
Delete row CTRL+’-‘
Accessing Help Information
To view Press
Help topics F1
CTRL+H
About Button ?
CTRL+?

Edition 08.2013
1.3 Application User Interface
First look at the user interface
HTC application main window (Base Frame) is the container for the application main parts – panels. There
are 4 basic panels located within base frame: Menu bar, Tool bar, Navigation Tree (Object Browser), and
Object Panel (Base Panel). Following picture shows the location of the panels:
Menu Bar
Tool Bar
Object Browser Object Panel
In the Status bar on the bottom of application window you can find the name of the currently logged-in user,
actual time, and an icon for the connection state. If you hover over this icon (if it is in a connected state), you
will see a name of the connected server.
The name of the HTC environment is displayed at the bottom of the window frame in a configurable color.
htc-dev.gdfsuez.net
Menu bar
Menu includes standard menu items – File, Tools, Window and Help, and the HTC menu items, which you
can use to directly start the desired functionality.
Tool bar
You can use the tool bar for manipulating current selected object. You can create new object, copy and paste
objects, rename and delete them. For editing object details you have to select Change Data button. After you
have altered object details you can save or discard changes using button in the toolbar.
In the tool bar there is also a combo box for selecting a variant.

Edition 08.2013
Object Browser
Basic nodes of the tree view are the basic parts of the HTC functionality. Every of this nodes can be
expanded to browse through the object hierarchy.
Object panel
After you have selected an object in the object browser, here you can find detailed information about the
selected object.
On the top you can see the name of the selected object in the drop down box. You can quickly change the
objects on the same hierarchy level.
Detailed information is displayed below. In cases when there are many details, they are organized in tab
control. You can select the tab to see desired category of detailed information.
To have a better view if the display is a Result- or Model-display the line with the Component name has
different colors green for Result- and blue for Model-Displays. With the short key <CTRL>+J the user can
switch between Result- and Model- Display.
Colors
In the result displays the colors of the generation schedules of the units are set according to the availabilities
of the units. They shall help user to analyze the results:
Green The unit is available
Grey The unit is set to not-available
Pink The unit is must-on (explicitly or implicitly)
dark-blue The unit is on FixP.
In the input displays the colors are used for different purpose:

Edition 08.2013
Blue The value is entered manually (or from import)
Red The value is invalid (to be ignored)
Grey The value is not renewed (to be ignored)
In general the colors represent the 'quality-flags' of the values.
User Defined Attributes
Select “User > Change Attributes” from the tree or from the application menu. User can set following
attributes of the user interface behavior in the displayed “Color” and “Miscellaneous” tabs:
 Colors
User can customize what colour different user interface elements will use
 Startup
User can set the start-up conditions for the jROS UI – the preloaded variant, the size of the window and
the display on which the jROS application window will be displayed (for the multi-display environments
only).
 Layout
- Name Display
User can choose whether to use short or long names of the objects in the jROS UI
Note
Please note, that in the table headings and in the graphs, the short name will be used regardless of these
setting, because of the maximum space reserved for the text on the display.
- Reverse Message Order
User can set if the messages in the message list should be displayed in the reverse order
- Sorted Chart Legend
The legend of the chart can be displayed in the standard order or alphabetically sorted
 Schedule
- Freeze Date Column
If the user sets this option, the date column in the schedule view will be frozen, so this column stays
displayed on the left, regardless of the horizontal scrolling of the screen
- Additional rows settings
The user can set the number of the rows viewed in the past and/or in the future of the current
displayed time interval (maximum 4 rows are enabled), if this rows are separated by a line, and the
color of these rows
Note
Please note, that the advanced rows are provided only for informational purposes, and does not affect the
summaries (e.g. Sum, Min, Max). Summaries are build-up only over the planning horizon.

Edition 08.2013
2 Operations
2.1 Starting to Work with HTC
2 Operations
The goal of this task is to start HTC user interface.
Starting the HTC
Connect to the jROS/HTC server via your browser. Alternatively you can start the HTC from a shortcut on
your desktop. The jROS start window opens. The Object browser user interface allows you to navigate
through the available displays.
Note
You can open multiple instances of the HTC on multiple clients - which are all connected to the same HTC
server.
Logging On
HTC is equipped with Single Sign On (SSO). No extra login is required. Your access rights are given by the
roles you are assigned to in the LDAP system.

Edition 08.2013
2 Operations
Note
For detailed information on user access rights, refer to the chapter 2.18.
Navigate in the selection tree
 Variants
This part is related to the handling of variants (independent datasets).
 HTC Administration
This part is related to administrative displays.
 HTC Execution
This part is related to the displays activating interfaces and the HTC-algorithm including relevant
parameters of the algorithm.
 HTC UserUI
This part is related to displays that can be customized by the user and the configuration tool to do that.
 HTC Results
This part is related to the pre-configured result displays. All results of HTC that are stored in the
database can be seen there.
 HTC Model
This part is related to the model editor of HTC. All input data of HTC are visible there and may be
modified. New components may be added, existing components may be deleted.
 HTC Variant Comparison
This part is related to the comparison of variants (independent datasets). It contains a tool to configure
multi-variant displays and the tree of already configured multivariant displays.

Edition 08.2013
2 Operations
2.2 Performing a calculation

The goal of this task is to activate the HTC-algorithm.
Note
Before modifying any of the HTC Parameters you must press the button ‘Change Data’ in the tool bar.
HTC Program Parameters
Program parameters determine the horizon and other general aspects of planning. Be sure to modify them
correctly before you import data or start the calculation.
The planning horizon is used as the default display horizon of all tabular displays and also as the time horizon
for import and export of data (except import from intraday).
You can set the following HTC program parameters

 Planning horizon manual; you can choose one of the following options:
- ManualEntry (BeginTime and EndTime are defined by user) or
 Begin Time (of planning horizon)

 End Time (of planning horizon)
 Calculation Mode; options are:
- Costing (a simulation and cost calculation without optimization)
- FullPlanning (a full optimization and subsequent costing)
- ThermalFixed (a re-dispatch of the thermal units with fixed commitment and a fullplanning of all other
components)
- RePlanning (like ThermalFixed, but sync-/desync times of thermal units can be shifted slightly)
- FullPlanning2step (a full optimization in two steps and subsequent costing)
- RePlanning2step (for HTC internal use only)
 Time Step (time grid of planning)

- 15 Minutes
- 30 Minutes
- Hour
 Start Condition
- FromMeasVal (calculation of schedules starts from measured values)
- FromSchedule (calculation of schedules starts from previously determined schedules)

Edition 08.2013
2 Operations
- FromTarget (calculation of schedules starts from target values)
HTC Consideration
In this section you can switch ON/OFF specific features of HTC as:
 R1 on (Switch on/off reserve class 1 planning to be performed)
 MPROFon (determination of Market Profiles/Sensitivity Analysis)
 SMon (consideration of electricity spot markets on)
 FMon (consideration of fuel markets on)
Note
If you move your mouse cursor over one of the input fields a tool tip appears with the detailed explanation of
the field or button.
Remember to save the HTC program parameters before starting the HTC engine
Note
For the mode ‘ ThermalFixed’ the schedules ‘PowerProdSched0’ (P) are read for all thermal units.
For P>0 the unit will be planned as committed, for P=0 the unit will be planned as not committed.
Activate engine of the HTC database
Select “HTC Execution > Run Manager” from the application menu or “jROS Optimization > HTC
Execution > Run Manager” from tree menu, the Run Manager view is displayed, then scroll down to the
section HTC.
With the green button you can activate the HTC-engine for the given set of parameters. The field next to this
button shows the actual state of the calculation engine. All possible states are described below. The other
fields give date/time of last activation and the planning horizon of this activation.
With the red button you can stop and abort an ongoing calculation.
Fields in the second and third row gives detailed information about the progress of the optimization.
MIP-gap and Best integer solution are the current optimization results Elapsed time field shows the time since
the optimization was started. Bound is the best theoretically achievable solution.

Edition 08.2013
2 Operations
There are two progress bars in the third row of the execution part of the jROS. The first progress bar shows
graphically the current optimization step status. The bar shrinks and changes the color from orange through
yellow and lightgreen into darkgreen with the converging to optimal solution. The second progress bar is a
graphical depiction of the elapsed time – the bar expands over time and changes the color from darkgreen
over lightgreen and yellow into orange as the time comes close to timeout of the calculation.
In the optimization steps (MILP 1 – MILP 3) there is a possibility to interrupt the calculation pressing the
“Interrupt” button on the right. If the button is pressed, the Optimization system stops at the current step
(which may take several seconds) and takes the best value until then as result.
With the yellow button you can open the list of messages. For details on the messages see below.
HTC actual state can have one the following options
State Description
Waiting HTC-engine is inactive in this variant
Active HTC-engine is activated in this variant (but has not really started)
Read HTC-engine reads data
Check HTC-engine performs the advanced input check
Start HTC-engine performs start solution (first phase of algorithm)
MILP 1 HTC-engine determines optimal commitment (second phase of algorithm), stage 1
MILPAbort HTC engine is going to interrupt at current optimization stage. Calculation sequence
goes on with the best result until then.
Dispatch HTC-engine determines optimal dispatch (third phase of algorithm)
Write HTC-engine writes results to database
OK HTC-engine has finished with a feasible solution (and input check has not given any
warning)
Message HTC-engine has found some data errors and calculated based on assumptions. The
assumptions are given as warnings in the message list.
DataError HTC-engine has stopped after input check, because the problem is infeasible or the
data are erroneous. The sources for infeasibility or erroneous data are given as error
messages in the message list.
Stopped HTC-engine was stopped by the user.
Note
Depending on the complexity of the problem, the total calculation time (especially the phases Start, MILP,
Dispatch) can be several minutes.

Edition 08.2013
2 Operations
HTC messages
To check the messages press Detailed Messages button and then you can see the message list as
given below.
You can identify the severity (error class) of the message by a color and by a range of the Error No as
described below:
Color Error No. Range Description
 Black 0 to 99999 Information message
 Blue 100000 to 149999 Warning (input check)
 Green 150000 to 199999 Warning (soft constraint violation)
 Yellow 200000 to 249999 Data error
 Orange 250000 to 299999 Warning (hard constraint violation)
 Red 300000 to 349999 System errors
The Component name tells you where the error/warning is related to.
The Message Text gives in clear text the detailed message information, e.g.
 Information text for information messages
 Warning explanation for situations, where HTC modified the data internally as part of the input check.
 Working explanation for situations, where HTC violated a soft constraint.
 Data error explanation for situations, where HTC detects a data error within the input check.
 System error explanation for situations, where HTC faces a problem with the system.
Start date and End date columns are used by messages where the time interval is important.
There are few operations, which can be performed with the message list, using the buttons on the bottom.
Message list can be cleared by use of the ‘Clear’ button. You can use the ‘Previous Session’ and the ‘Next
Session’ buttons to show cleared messages again, where session means a time between two clear
operations. The ‘Refresh’ button loads current messages in the message list. Finally, the ‘Close’ button
closes the messages window.

Edition 08.2013
2 Operations
Note
The Warning messages for constraints are subject to tolerances. These tolerances are given in a
configuration file (CONFIG00.dat) and can only be modified by a system administrator.
Standard settings for the tolerances are as follows:
cLoadTolerance 1. /* [MW] load condition tolerance */
cRsrvTolerance 5. /* [MW] reserve condition tolerance */
cCSHTolerance 0.5 /* [MWth] tolerance f.balance steam header */
cHeatTolerance 0.5 /* [MWth] cogeneration tolerance */
cEnergyTolerance 0.01 /* [1] tolerance as factor to energy limits */

Edition 08.2013
2 Operations
2.3 System Tuning
2.3 System Tuning

The goal of this task is to set parameters for all reserves.
Select “jROS Optimization > HTC execution > System Tuning” from tree menu or from
“HTC execution > System Tuning” in application menu, then click on the change data button to
configure the system.
 R1 time = Time for activation for reserve class 1

Critical for units with ramp limit dependent reserve mechanisms, like Spinning and Standby.
 R1 excl = Switch ”Exclusive” for reserve class 1
Defines whether the power assignment is exclusive for the reserve class, or can be part of another
reserve class as well.
 R1 on = Switch the reserve class 1 on/off
Defines if the reserve class is used or not.
You can set the parameters for all reserves.

Edition 08.2013
2 Operations
2.4 Application Tuning

The goal of this task is to set the application parameters. These parameters are depending on the selected
variant, so you can use different settings for different variants.
Select “HTC execution > Application Tuning” from tree menu or from the application menu then click on the
“Change Data” button to configure the application.
You can set the application parameters which are:
Parameter Description
MIP gap Rel 1, 2, 3 relative MIP (tolerance) limit search phase 1,2,3
MIP gap Abs 1, 2, 3 absolute MIP (tolerance) limit search phase 1,2,3
MIP gap selector Selector to switch between absolute and relative MIP limits
MILP sol Number of integer solutions to break-off
MILP nodes Maximum number of nodes to break-off
MILP time Maximum time limit of MILP per search phase
max it.slph Maximum iteration in sLP hydro
fac.sLPh Contraction factor sLP hydro
perc.sLPh Percentage factor sLP hydro
max it.slpt Maximum iteration in sLP thermal
fac.sLPt Contraction factor sLP thermal
debug Debug level
base pen. Basic penalty
exec. Time Execution time of last HTC run
MIP gap rel Achieved relative MIP gap
MIP gap abs Achieved absolute MIP gap
Cplex Default If marked, the default-parameters of CPLEX are used (e.g. for small cases),
otherwise the tuned parameters are used (e.g. for large cases)
Heuristic off: This switch can be used for test purposes in order to analyze variances in
calculation time
MPROF demand Variations Make sure to cover in any case the demand. This could be necessary if the
calculation time grid is bigger than the given demand schedule.
MPROF freeze Electricity Freeze Electricity Contracts schedules in MPROF runs
Contracts
MPROF freeze Powerlines Freeze Power Lines exchange in MPROF runs
MPROF freeze SpotMarket Freeze SpotMarkets schedules in MRPF runs
MPROFon Switch to activate Market Profiles analysis
MPROF ramp limit Obey modified ramp constraints in MPROF runs

Edition 08.2013
2 Operations
Caution
Modifying application tuning requires deep know how on the HTC algorithm and should only be done by
qualified persons.
The MIP gap limits are measures for the accuracy that should be achieved. The settings shall be as follows:
MIP gap rel 1 = 0.005; MIP gap rel 2 = 0.01; MIP gap rel 3 = 0.05
The relative MIP gap 1/2/3 are applied to the so-called “relative MIP gap” which measured in relative units
(range 0.0 … 1.0). The MIP break criteria can also be provided in absolute units of the objective function (ie.
in EUR). A selector determines which set of break criteria (absolute or relative) is applied.
The parameter ‘MILP time’ must be adapted according to the complexity of the problem and depend on the
performance of the program. The desired figures are given as part of the release notes.
The other parameters should not be modified.

Edition 08.2013
2 Operations
2.5 Inspection of results via user interface

The goal of this task is to browse through the HTC-results.
Browse through displays of the HTC Results tree
Select “HTC Results” from the application menu or from tree menu, and check the results by:
 System Overview
 System Reserves
 Area Overview
 Area Reserves
 Area MPROF
 Power Lines
 Cogen Zones
 Cogen Storages
 Thermal Plants
 Thermal Units
 Common Steam Headers
 Unit Restriction Groups
 Fuel Contracts
 Fuel Markets
 Fuel Restriction Groups
 Hydro Plants
 Hydro Units
 Hydro Reservoirs
 Hydro Channels
 Hydro Spillways
 Energy contracts
 Electricity Markets
In general, displays are given per component type and contain several panes for different kind of data.
Additional to the component type results displays, there are displays, which contain all results of the
components assigned to these displays.
In particular:
 System Overview
Contains results of all areas and power lines (connections between the areas).
 Area Overview
Contains results of all plants in the area.
 Thermal Plants and Hydro Plants
Contains results of all units of this plant.

Edition 08.2013
2 Operations
Note
No edit of the results data is possible.
System Overview
You can see the all over the system results, cost overview and Charts.
You can analyze all results and print the results which you want using the print functionality (can be accessed
over a pop-up menu using the “Right mouse button”).
Analogically to the System Overview you can check the Area Overview, Thermal Plants and Hydro Plants
overview displays.
Overview Display
Cost Overview Display

Edition 08.2013
2 Operations
Chart Overview Display

Edition 08.2013
2 Operations
Note
With CTRL + Click-left on one line, this line is marked as hot (bring to front).
This is a toggle function and not saved in the chart settings.
You can also check total cost summaries as shown as below:
 Total sum of cost

 Cost/Revenue from fuelmarkets over planing horizon(not supported yet)
 Cost/Revenue from spotmarkets over planing horizon
 Total costs of optimizable contracts over planing horizon
 Total cost due to shadow prices
Last three lines show the minimum, maximum and the total sum of the values of the result table.
Note
There are two kinds of schedules within HTC. Power-like and Volumetric-like. The Power-like are to be
interpreted as mean values for the next hour, the Volumetric as the value at the end of the interval.

Edition 08.2013
2 Operations
2.6 Export of Results to Excel

The goal of this task is to export the HTC-results via the Excel interface.
Open a table display
Select a view displaying results data from the tree menu by left mouse click on the view name.
These views are under default results “HTC Results” or under custom results “HTC UserUI”
Export to Excel
After the results view is displayed right mouse click on the tabular data and select “Export to Excel” from the
popup menu. HTC opens the ‘Save File’ dialog and waits for user to specify directory and file name of the
export file to be created. The data displayed on the view are exported after user presses ‘Save’ button in the
‘Save File’ dialog.
HTC remembers the user’s directory and file name preference for the view as long as the view remains
active, as a result, all consecutive ‘export to Excel’ operations on the same view overwrites the file specified
during first “export To Excel” operation.

Edition 08.2013
2 Operations
Note
Data exported via the Excel interface are stored on the client and not on the HTC server.

Edition 08.2013
2 Operations
2.7 Manual Update of Input Data via User Interface

The goal of this task is to change the input data directly via the user interface.
Navigate in “jROS Optimization > HTC Model > …” tree menu to the desired component display.
Change data
Use the “Change Data” button to lock the data set and enter edit mode.
After updating the data by manual editing, you can use Save Data, Save Data with Comments or Cancel
button from the tool bar.
Save data
Click the “Save Data” button to store the data in the database or use the “Save Data with Comments”
button to store the data and give comment to your modification. This comment is given in the Variant Log
display.
Note
In case of schedule data, after save button is pressed, a post processing will be performed to check and
remove equal values of subsequent steps which results in an aperiodic schedule that is saved (only value
changes are stored in the database).
Cancel
Any data modification can be interrupted by use of the “Cancel” button to discard the update.
Input check of data
After clicking the “Save Data” button or the “Save Data with Comments” to store the data in the database an
input check is performed and gives a warning if the data are implausible.

Edition 08.2013
2 Operations

Edition 08.2013
2 Operations
2.8 Update of Input Data via Excel

The goal of this task is to import HTC-data via the Excel interface.
Navigate in “jROS Optimization > HTC Model > …” tree menu to the desired component display.
Change Data
Use the “Change Data” button to Update the Input Data.
Import from Excel
Right mouse click on the table which will be changed, and select the “Import from Excel” option.
Choose the Excel document where the new data is stored. Then the Excel document will be opened. Check
your data once more then close the document. Finally you can see the new data in the table.

Edition 08.2013
2 Operations
Note
The Excel file must be stored on the client and not on the HTC server. Furthermore it must contain in the first
worksheet exactly the data that you want to import.
Best practice operation is to export a table first by use of Excel export and use this file for the import.
Caution
Date/Time values in the -to be imported- Excel file must perfectly match the Date/Time values of the selected
period. Non corresponding Date/Time values results in a rejection of the complete import procedure
Save Data
Click the “Save Data” button to store the data in the database or use the “Save Data with Comments” button
to store the data and give comment to your modification. This comment is given in the Variant Log display.
Or “Cancel” button to discard the import.
Cancel
Any Excel import can be interrupted by use of the “Cancel” button to discard the update.

Edition 08.2013
2 Operations
2.9 Modifying Charts Settings in the User Interface

The goal of this task is to modify the layout of charts according to your requirements.
Chart Menu
HTC results may be analyzed using the chart displays available in the results views; the charts can be
adapted in order to modify their format to the most useful one for analysis.
Use the “Right mouse click” button to open the chart menu.
The chart menu is opened allowing the following actions:
 Normal Line modifies all displayed curves to normal line mode.
 Step Line modifies all displayed curves to step line mode.
 Stacked Step Line modifies all displayed curves to stacked areas with step lines.
 Stacked Area modifies all displayed curves to stacked areas with normal lines.
 Change Settings opens the advanced modification dialogue.
 Save Settings for this Object saves the chart settings for this Object.
 Reset Settings for this Object restores the original settings for this Object.
 Save Settings for this Type saves the chart settings for this Type.
 Reset Settings for this Type restores the original settings for this Type.
 Print prints the chart.
Note
Save settings for this type modifies the settings for all objects of this type.

Edition 08.2013
2 Operations
Change Settings
Chart settings are modified using the ‘Change Settings’ window. The ‘Change Settings’ dialog window allows
the following actions (alternatively you can click-left on one line of the chart):
 A mouse click on a ‘Chart Line’ in the chart area or in the legend, this makes the ‘Chart Line’ active in the
opened “Change Settings” window.
 Right mouse click on empty space, then select “Change Settings” from the opened popup menu.
The ‘Chart Settings’ dialog window is composed of two parts:
 ‘Chart Lines’ contains the list of values (value series) available for displaying on the chart
 ‘Line Properties’ is used to specify the display attributes of each ‘Chart Line’
The ‘Chart Lines’ part of the window is used for:

 Inclusion/exclusion of value from the chart. To include a value in the chart mark the checkbox in front of
the value name
 Changing the order 1 of the ‘Chart Line’ using the ‘Up’ and ‘Down’ buttons. The order of a Chart Line
determines its drawing order; the Chart Line at the top of the list is drawn first, then the second … As a result,
each Chart Line is overwritten by the Chart Line coming after it in the list order.
The ‘Line Properties’ part of the window is used for:
 Selection of a line type (Normal, Step Line, Scatter)
 Selection of a line style (Solid, Dot, Dash, Dot Dash, Alt Dash)
 Activation/Deactivation of filling, if activated the area below the line is filled with the color of the line
 Activation/Deactivation of stacking, if activated all the values of the activated lines are displayed on the
top of each other (stacked)
 Selection of line size (1, 2, 3, 4, 5)
 Selection of line color
 Transparency
Depending on the setting of the User Attributes ‘Sort Chart Legend’ the default order is either equal to the
1
order in the tabular view, or alphabetically sorted.

Edition 08.2013
2 Operations
2.10 Creating User UI displays

The goal of this task is to create new displays according to user’s requirements.
UI Configurator
HTC comes with built-in standard views for data input and output, these views display all single values (static
data), schedule values (dynamic data) and results available in the HTC database.
Users are not allowed to make any changes on the built-in standard views of HTC, but they may define their
custom views in HTC User UI.
To define new custom views in HTC follow the steps below:
 Select “HTC User UI > UI Configurator” in the tree menu or from application menu.
 Press the ‘New Data’ button .
 Specify a name and short name for the new view and press the ‘OK’ button.
The name has to be unique. If a user tries to set a name which is already existing he gets an HTC
message and has to set a unique name. Once the UI Name and Short Name are saved they can not be
changed.
 Define the content and layout of the view as described in chapter 0.
After updating the configuration press the ‘Save Data’ button to store the changes.
If you have once saved a UI Name and Short Name it can no longer be changed by Edit.
Note
When a new UI display is created, all roles get read permission for the UI display automatically. If the UI
display is editable, an administrator needs to give write permission for the display to roles
You need the “Create UI” permission to create a UI display.
Access Permissions for User UI
You can set the permission for the user UI on role basis. Select “HTC Administration > Roles” from the tree
menu or from the application menu. Select the role for which you want to set the permission. Select the
“Configured Displays Permissions” tab. Use the “Change Data” button to access the permissions list.
Set the read and / or write permissions of the user displays.

Edition 08.2013
2 Operations
Use the ‘Save Data’ button to store the changes

Edition 08.2013
2 Operations
2.11 Modifying User UI displays

The goal of this task is to modify the layout of displays according to your requirements.
UI Configurator
To modify a custom view configuration select “HTC User UI > UI Configurator” in the tree menu or from the
application menu, then select one custom view configuration and press the ‘Change Data’ button .
After updating the configuration press ‘Save Data’ button to store the changes.
UI Configurator is composed of three main parts:
Options part is at the top of the view, using this part you can:
 Modify the type of the view (Configuration Type)
- Mixed – view contains both single and schedule values
- Schedule – view contains only schedule values
- Values – view contains only single values.
 Make the view editable.

 Import/Export the view configuration to/from a XML (Extended Markup Language) file.
The content definition part allows a user to modify the view’s content and layout.
The Filter part is used for the selection of the components and attributes to be added/removed to/from the
view content. User should follow the following steps to add/remove an attribute to/from the view
 Select the type of the HTC component
 Select HTC component(s)
 Select attribute(s) to be added/removed
Note
Right click on the title ‘Selected’ opens a menu to ‘Check all’ / ‘Uncheck all’ elements of the list.

Edition 08.2013
2 Operations
Note
The views content is always the cross product component / attributes.
Different component types are allowed to be combined in one view.
The User display has to be updated manually every time you add a component to the model because this
new component will not be visible in the user interface automatically.
The Selection part is used for formatting the view content. It contains the list of components/attributes and
formulas as well as their format information. You may add/remove formulas to/from the list by right mouse
click selecting ‘Insert Formula’/’Delete Formula’ from the popup menu.
Specifying data format
User is allowed to modify the following format information:
 Digits – number of precision digits to be displayed, for instance a value of 95,123456 is displayed as
95.12 with 2 digits precision and 95.123456 with 6 digits precision
 Column Index – display order of the columns, values must start from one and increased by steps of one,
the values must be consecutive, i.e. skipping of a value is not allowed.
 Width – width of the column displaying the values of the attribute in the UI display
 Header – header of the column displaying the attribute in the UI display
 Chart – check box used to add the attribute to the chart display of the view in the UI display
 Formula – formula specification
Note
Use the order by function at the bottom to define the order of your columns.
Formula Specification
User may specify formulas using the four basic arithmetic operations, parentheses are not supported.
A formula has the following syntax:

Edition 08.2013
2 Operations
Column Operator Column Operator Column….
Where:
Column: is composed of the capital letter ‘C’ and the column index of an attribute column;
i.e. C1, C12, C14
Operator: one of the four basic arithmetic operators;

i.e. addition (+), subtraction (-), multiplication (*) and division (/)
Note
After adding / removing columns all column indices need to be updated.

Edition 08.2013
2 Operations
2.12 Modifying the Data Model

The goal of this task is to modify the data model of HTC.
For details on the data model itself please refer to chapter 3.
For details and dependencies on the thermal topology please refer to chapter 3.3.2.
For details and dependencies on the hydro topology please refer to chapter 3.3.3.
New Component
Select “HTC Model” ” from the application menu or from the tree menu, then decide which components you
want to add. For example add a new thermal unit. Select “Thermal Units”, the Thermal Units view is
displayed, then Press “New Data” button. Enter the name and short name of the components and press
“OK”.
Enter at least the mandatory data and use “Save Data” button to add the components.
The new components automatically appear in the selection tree on two places:
 HTC Model (as new leaf in the given component type)
 HTC Results (as new leaf in the given component type)

Edition 08.2013
2 Operations
Caution
Creating new components requires deep know how on the model of HTC and should only be done by
qualified persons. If you are not familiar with details of modeling you may create models, where HTC engine
detects ‘DataError’ and you cannot use this data set for calculations unless the erroneous component is
corrected.
Note
A detailed description of the HTC model is given in the document ‘Technical Specification HTC’. Please
consult the chapter ‘Data Model’ for the available components, the attributes and the topological relations.
A short description of the attributes and topological relations is given as a tooltip, if you move your mouse
over the input field.
Copy component
Another possibility to create a new object is the use of “Copy Data” button. All data of the selected
component are copied and a new component is created under the given name. Also all topological relations
to predecessors are copied.
Note
Copy component copies all topological links to predecessor components.
Copy component does not copy topological links to successor components.
Copy component does not copy successor components. Hence copying a plant does not create units.
Rename component
Existing components can be renamed by use of “Rename Data” button.
Delete component
Existing components can be deleted by use of the “Delete Data” button. Confirm the deletion in the
displayed dialog box.
Caution
Deleting components cannot be undone. If you are not familiar with details of the model you may create
models, where HTC engine detects ‘DataError’ and you cannot use this data set for calculations unless the
erroneous component is corrected.

Edition 08.2013
2 Operations
Note
Delete components deletes all topological links that are connected to the component.
Delete component does not delete any predecessor or successor component.
E.g. deleting a plant will not delete the units of this plant but leave there plant field ‘empty’.
It is recommended to save the variant (data set) before you make significant modifications.

Edition 08.2013
2 Operations
2.13 Creating the Data Set (Variant)
2.13 Creating the Data Set (Variant)

The goal of this task is to copy a data set (Variant) of HTC from a variant.
New variant
Select “Variants > Variant Management” from tree menu, then press “New Data” and define:
 New Variant ID
 Name
 Description
 Workspace
 Private check box
If the Private check box is activated, only the user who created the Variant can see it and has access to it.
Now you should select “Copy from Variant” and choose the variant name from the variant list. For the quick
selection of source variant you can use the Filter Options.
Finally press “OK” to create your data set from a variant.

Edition 08.2013
2 Operations
2.14 Saving the Data Set (Variant) to a File
2.14 Saving the Data Set (Variant) to a File

The goal of this task is to save a data set (variant) of HTC to a dump file.
Save variant
Select “> Variants > Variant Management” from tree menu, then press “Save Data” button.
The .dmp file is saved on the client.
Select the variant from drop down menu and define the name of the .dmp file as shown as below.
Finally press “OK” to save your data set to a file.
Note
Depending on the size of the data set saving may take a few minutes.

Edition 08.2013
2 Operations
2.15 Restoring the Data Set (Variant) from a File

The goal of this task is to restore a data set (variant) of HTC from a file.
Restore variant
Select “Variants > Variant Management” from tree menu, then press “New Data” and define:
 New Variant ID
 Name
 Description
 Workspace
 Private check box
If the Private check box is activated, only the user who created the Variant can see it and has access to it.
Now you should select “Copy from File” and choose the file name from the drop down menu.
Finally press “OK” to restore your data set from a file.

Edition 08.2013
2 Operations
There are two folders for the “.dmp” files. One is used for the files you have created by saving a variant to a
file. The other one is used for the automatic storage function to ‘archive’.
To restore a variant from the archive, please use ‘Copy from Archive’ to access these dmp-files.
Note
If you have copied the file from another system to the directory of the server, an administrator must update
the table variant dump files before file appears in the list of available files.

Edition 08.2013
2 Operations
2.16 Deleting the Data Set (Variant)
2.16 Deleting the Data Set (Variant)

The goal of this task is to delete a data set (variant) of HTC.
Delete variant
Select “> Variants > Variant Management” from tree menu then press “Delete Data” .
Now you should select the variants you want to delete by use of the check boxes.
Pressing the ‘OK’ button deletes the selected variant(s).
Online variant
Note
One variant is marked as the so-called ‘online’ variant. This variant cannot be deleted. It may serve as a
master variant for all structural modifications of the data model.
The online variant is set by use of the ‘Change Data’ button of the variant manager .

Edition 08.2013
2 Operations
2.17 Variant Management

The goal of this task is to perform managing tasks with Variants.
Set the detailed Variants Log
Select “> Variants > Variant Settings” from tree menu then press “Change Data” button.
Look in the “Variant Logging” group of settings. Now check the “Extended Logging” check box to enable the
detailed logging functionality. You can also set the automatic deletion of logging data after a certain amount
of days
Then press the “Save Data” button.
Caution
The data needed for the logging functionality can increase to a huge amount, so it is a good practice to set an
Automatic deletion of this data, or check the disk capacity in a periodical manner.
Note
The “Automatic deletion” setting is used also for the archived schedule data and messages from the
message list after “Export Interface with Archiving” has been executed.
Database Cleanup
Select “> Variants > Variant Settings” from tree menu then press “Change Data” button.
Look in the Database Cleanup group of settings. You can set the automatic deletion of schedule data after a
certain amount of days.
Additionally you can find a button “Start” for the deletion of the redundant records in schedules. After this
button is pressed a clean-up operation is started. jROS checks all the variant schedule data and deletes the
redundant records (where values are equal in the subsequent time steps) from the database which results in
aperiodic schedules. The number of deleted records are recorded in the variant log.

Edition 08.2013
2 Operations
Then press the “Save Data” button.
Check the detailed Variant Log
Select “> Variants > Variant Logs” from tree menu.

You can check all changes in the selected variants, including following data:
 Variant Name
 Change Date
 Number of details
 Type of action
 Type and name of the changed object
 Description of the change if the user has provided a comment
 User name of the user who made the action
If there is a number displayed in the “Details” column for some action, selecting this action provides in the
lover part of the window extended information of every schedule and value changed in this action including
following data:
 Number of detail change
 Type of action
 Component and attribute short name
 Date in case of schedule values
 Old and new value
 Component and Attribute Name.

Edition 08.2013
2 Operations
Delete the detailed Variant Log
In the “Variant Logs” display press the “Delete Data” button. All log data will be deleted.
Note
The calculation of the number of passed days is: server system date (Application-Server) minus number of
days specified in the settings dialog.
Note: 0 days also means that automatic deletion is disabled.
The check for deletion and the effective deletion happen before a log entry is written to the database. There
is no automatic process running in the background, since this would mean unnecessary server load. This
means that the deletion happens only per variant. We recommend that automatic deletion is enabled since of
course a lot of logging information means higher storage consumption on the database.
If you create a new variant based on a dumpfile, then the logging content of the dumpfile will be imported as
well. If autodelete is active in the imported dump, the logging information will be deleted whenever the next
log entry is written. If you want to keep the logging information, you need to disable autodelete after the
import.
The deletion of log records is triggered any time when a new log record is written. As long as you do not
make any changes (save data, start a calculation run, import XML-files...) the outdated log records are not
removed.
Note
The “Automatic Deletion” in the archived variants is set to 0, the reason for that is, that the restored variants
should remain in the database, and should not be deleted automatically.

Edition 08.2013
2 Operations
2.18 Workspaces, Roles and Role Assignment

The goal of this task is to define / modify the access rights of the users.
Workspaces
Select “HTC Administration > Workspaces” from the application menu or “> HTC Administration > >
Workspaces” from tree menu, the Workspaces view is displayed, then press “New Data” button and
enter the name of the workspace. Define a description and press “Save Data” button to save your
workspace.
The Workspace Name and Description can be changed at later date even when it contains variants.
Note
Workspaces are groups of variants. Typically they represent a group of similar data sets to which a group of
users is allowed to access.
Note
Only administrators are allowed to modify and create workspaces, roles, and role assignments.
Roles
Select “HTC Administration  Roles” from the application menu or from tree menu. To add a new role use
“New Data” button and enter the role name, to modify use “Change Data” button.
Define the access rights in the pane:

 General for defining the rights of the role.
 Interface Permission for import and export interfaces.
 Configured Displays for the user specific displays

Edition 08.2013
2 Operations
In the first pane, role decision part welcomes us. You can use check boxes to add/remove the permission to
the role:
 Read permission is required to view model and result data. However, for configured UI displays the
permissions are defined separately in the pane "Configured Displays Permissions".
 Write permission is required to modify model data.
 Create permission is required to create components in the model.
 Delete permission is required to delete components in the model.
 Execute permission is required to activate the HTC algorithm.

 Create Variant permission is required to create a new data set (Variant) and to save a data set
(Variant) to a file.
 Delete Variant permission is required to delete a data set (Variant).

 Create UI permission is required to create UI displays.
 Delete UI permission is required to delete UI displays.
 Administration permission is required for administrative tasks like definition of workspaces, interfaces,
and roles.
In the second pane, you can give import permission to the role as below.

Edition 08.2013
2 Operations
In the third pane, you can give export permission to the role as below.
In the fourth pane, you can give pre-defined display permissions in a specific variant to the role.
Use drop down menu to select the specific variant.

Edition 08.2013
2 Operations
Finally use “Save data” button to store the new role.
Role Assignment
Select “HTC Administration  Roles Assignment” from the application menu or from the tree menu, to
modify a role assignment use Change Data button.

Edition 08.2013
2 Operations
Note
The values correspond to the groups defined in LDAP.
The combination of roles and workspace is defined in the central access system and must be consistent with
the information obtained via LDAP.

Edition 08.2013
2 Operations
2.19 Other Administrative Tasks
2.19 Other Administrative Tasks

In the chapter below you have administrated the workspaces, the roles and the role assignment. The goal of
this chapter is to perform all other possible administrative tasks. All these tasks are allowed only for users in
the administrator role.
Manage Variant Dumpfiles
Select “Variants  Variant Dumpfiles” from the application menu or from the tree menu, to open the list of
dumpfiles. To modify the list of dumpfiles use the Change Data button. Now you are able to change the
dumpfile list. You can change the entries of saved dumpfiles by directly editing them.
Right click with a mouse on the list brings a pop-up menu with the functionality to delete dumpfile entries or to
insert new dumpfile entries (e.g. archived before, and now restored).
Finally use the “Save data” button to store the changes or dismiss the changes using the “Cancel”
button.
Cancel Active Users
Select “Users  Active Users” from the application menu or from the tree menu, to open the list of active
users Disconnect active users from HTC Server. Use the “Change Data” button to enter the list. Select
the checkbox “Terminate Session” on the left of the user you want to disconnect from the server. You can
also select more than one user.
To disconnect the user use the “Save data” button. All selected users are now disconnected from the
server. Every disconnected user gets a hint, that he is disconnected and the jROS UI ends automatically for
him. User must start the application again, if he wants to continue to work with jROS.

Edition 08.2013
3 Power System Model
3.1 Notation

The Power System Model is built up of components like power plants and generation units that reflect the
conditions of the physical counterparts of the power system. These components belong to the two natural
parts of a power system, the thermal subsystem and the hydro subsystem, and are described in chapter 3.6
and 3.7, respectively.
Attributes of all these components have one of the data types as described in chapter 3.2. Chapter 3.3 shows
how the components are put together to build a complete power system model by specifying the power
system’s topology.
Furthermore, in chapter 3.4 and 3.5 two sets of attributes describe the power system’s constraints and its
optimization parameters, respectively.
3.1 Notation
The character ’€’ is used for the currency unit, that is the base for all price and cost related data.
Electrical power is always measured in MW, electrical energy in MWh.
Other types of energy or power (e.g. primary energy from fossil fuels, steam production/consumption by
ThermalGeneratingUnits etc.) are measured in GJ or GJ/h, respectively. This is also true for quantities related
3
to these types of energy/power; e.g. the calorific value of a FuelType is given in GJ/ton, or GJ/Nm etc.
However, it is up to the user to enter a certain quantity in units that are not derived from GJ, as long as this is
done consistently, i.e. for all data points in the system where this quantity or a derived quantity is used.
Example:
 If the calorific value of a FuelType is entered in BTU/barrel,
- then the fuel’s (FuelContract's, FuelSpotMarket's) price must be given in €/barrel
- the Y-axis of the PrimaryEnergyPowerCurve (cf. Figure 13 in chapter 3.6.6) of all

ThermalGeneratingUnits burning this fuel must be in BTU/h
- the respective quantities of other fuels that are subject to a common constraint or that can be burned
by such a TGU must also be based on BTU
- etc.
Steam production is measured in MWth (energy in MWhth) and all related data (values, schedules,
characteristics etc.) are rescaled accordingly in a consistent way.

Edition 08.2013
3.2 Data Model and Data Types
3.2 Data Model and Data Types

All input and output data are stored in the Oracle database of jROS. The data model is structured in classes
and attributes. Their definition follows the rules of CIM (Common Information Model), wherever appropriate.
The user model is created by making instances (objects) of these classes and topological references among
the objects.
Throughout this document, the names of such classes or their attributes are written in italic , e.g.:
ThermalGeneratingUnit or MaximumMW.
The following basic types of attributes are used by HTC:
 time independent data:
This type is used for e.g. static input data. These attributes are named like Name.
 time dependent input data:
This type stores values including time-information in a so-called non-periodic schedule. As a general rule this
data are valid FROM time stamp, which allows simple preset of input data. These attributes are named like
NameSched.
 time dependent result data:
The type is used for all result schedules and has the time steps of the planning function. However, as the
calculations can be performed with different time steps, these schedules are also non-periodic. These
attributes are named like NameSched1.
 2 dimensional curves:
describes functional dependencies like "YValues dependent on Xvalues".
Curves are approximated by a sequence of linear segments. These attributes are named like
YNameXNameCurve2D.
 3 dimensional curves:
describes functional dependencies like "YValues dependent on XValues and a ZParameter".
Curves are approximated by a sequence of linear segments and grouped according to the ZParameter.
These attributes are named like YNameXNameCurve3D.
 tables:
describes relations between more than 3 attributes of an object or relations that cannot easily be seen as
functional dependencies
These attributes are named like NameTable.
The following chapters describe in detail all relevant input and output data considered by HTC. They are
structured according to major features and they explain major interdependencies of them.

Edition 08.2013
3.3 Power System Model Overview

The power system model is defined by its components and their interrelation. These components contain
thermal units or hydro units which are interrelated by a topology that defines the flow of energy between
these components. The thermal topology basically reflects the flow of heat, whereas the hydro topology
reflects the water flow between the hydro components. In addition to these ‘technical oriented’ components
there are general components to give a structure to the power system model (System  Area  Plant 
Unit).
Some component types are only relevant with optional HTC modules or features.The following figure gives an
overview of all component types and topological relations between them.
CGS
EC
CGZ CGI
SM CCP FM FRG
PL Area TP TGU FS FC FT
CSH
ERG
SYS URG
RES
SW
HV HP HGU
CH
RES
Figure 1: Components of the HTC data model
3.3.1 General Components
The power system model is structured as follows:

 System (SYS), which is simply the total model. This is subdivided into
 Areas as balance node for electrical demand and reserves.
 PowerLines (PL) limiting the exchange among areas.
 UnitSummingGroups (USG) hold the summed up results over the units of the System, Areas,
HydroValleys, HydroPlants, ThermalPlants and UnitRestrictionGroup 2
 SpotMarkets (SM) allow to exchange energy on spot.
 EnergyConstracts (EC) allow to exchange energy bilateral.
2
USGs are created automatically with the component assigned to them

Edition 08.2013
3.3.2 Thermal Topology
The model of the thermal power generation subsystem can be built of the following components:
 FuelTypes (FT) describe the kind of fuels.
 FuelContracts (FC) describe the contracts to buy fuel.
 FuelMarkets (FM) allow to exchanges fuel on spot.
 FuelStocks (FS) serve as balance nodes for one kind of fuel.
 FuelRestrictionGroups (FRG) define constraints on fuel contracts and markets.
 ThermalGeneratingUnits (TGU) are equipments for energy conversion with specific unit types (fuel to
power, fuel to power / steam, steam to power / heat).
 ThermalPlants (TP) are aggregating ThermalGeneratingUnits.
 CommonSteamHeaders (CSH) serve as balance nodes for steam in the plant.
 CogenZones (CGZ) serve as balance node for heat demand.
 CogenStorages (CGS) are storage devices for heat.
 CogenerationInterchanges (CGI) limit the transfer of heat between CGZs
 CombinedCyclePlants (CCP) are an alternative model for combined cycles
 UnitRestrictionGroups (URG) model constraints on ThermalGeneratingUnits
 EmissionRestrictionGroups (ERG) model constraints on emission
Fuel
Gas turbine
Boiler
Common steam header
Steam turbine
Steam reducer
Cogen storage
Cogen interchange
Cogen zone
Figure 2: Example of a common steam header plant feeding a cogeneration network
The following table lists all possible and mandatory connections:

Edition 08.2013
Table 1: General and thermal topology
Component Predecessor Components Successor Components
System (SYS) - n Areas
Area SYS ECs

n PLs n SMs
n PLs
n TPs
PowerLine (PL) 1 Area 1 Area
SpotMarket (SM) 1 Area -
EnergyContract (EC) 1 Area -
FuelType (FT) - n FCs

n FMs
n FSs
FuelContract (FC) 1 FT n FS
n FRG
FuelStock (FS) n FCs n TGUs

0/1 FM 0/1 FM
FuelMarket (FM) - n FS
FuelRestrictionGroup (FRG) - n FSs

n FMs
EmissionRestrictionGroup (ERG) - n TGUs

n FSs
ThermalGeneratingUnit (TGU) n FSs 0/1 CSH

n URGs 0/1 CGZ
0/1 CSH
ThermalPlant (TP) 1 Area 0/1 CCP

n CSHs
n TGUs
CommonSteamHeader (CSH) n TGUs n TGUs
CogenZone (CGZ) n TGUs n CGIs
CogenStorage (CGS) - 1 CGZ
CogenInterchange (CGI) 1 CGZ 1 CGZ
CombinedCyclePlant (CCP) 1 TP -
UnitRestrictionGroup (URG) - n TGUs

Edition 08.2013
3.3.3 Hydro Topology
The hydro system model is built of the following types of components:

 HydroGeneratingUnits for energy conversion to and from electric energy
 HydroPlants (HP) are aggregating HydroGeneratingUnits
 HydroValleys (HV) are aggregating HydroPlants
 Reservoirs (RES) for storage of energy
 Channels (CH) to reflect the time delay of water running along a river bed and
 Spillways (SW) that drain water from Reservoirs without electric energy generation.
A HydroGeneratingUnit (HGU) represents a system of turbine and generator, pump and motor or
pump/turbine and motor/generator. Figure 3 shows the hydro components and their symbols used in hydro
topology pictures throughout this document.
G M
Reservoir Turbine Unit Pump Unit
G/M
Channel Spillway Pump Turbine

Figure 3: The hydro topology's components
M G/M G G G
Within a hydro topology model, the interconnection between the components must satisfy certain restrictions.
A HydroGeneratingUnit must always have a Reservoir connected upstream. On the downstream side, an
HGU may have another Reservoir, a Channel or it may be left open-ended, as shown in Figure 4. Pump units
or pump turbine units must be connected to a downstream Reservoir (except for Pumped Storage Plants).
Figure 4: Interconnections of HydroGeneratingUnits
The restriction that an HGU must have a Reservoir on the upstream side also holds for models of run-of-river
plants. In this case the respective Reservoir is modeled with its attributes minimum level and maximum level
set equal. The power plant’s inflow is an attribute of the Reservoir as well, as illustrated in Figure 5, or may
come from another upstream hydro system component.

Edition 08.2013
inflow
minimum level =
maximum level
G G
Figure 5: Model of a run-of-river power plant
A Reservoir may be fed from several HGUs, Spillways or Channels. Its discharge may contain several HGUs
or Spillways as shown in Figure 6.
G M G/M
G M G/M
Figure 6: Interconnections of Reservoirs
Channels receive their water flow from any number of Spillways, turbine units or other Channels as depicted
in Figure 7. Their water output may be connected to a single Channel or Reservoir or may be left
unconnected.
G G
Figure 7: Interconnections of Channels

Edition 08.2013
Spillways always have a Reservoir in their upstream and may have a Channel or another Reservoir on the
downstream side as indicated in Figure 8. The downstream may be left unconnected.
Figure 8: Interconnections of Spillways
Table 2 gives an overview of the above topological restrictions. Based on these hydro-power system
components, models of any hydro-power system can be built up. The components’ parameterization is done
using their attributes, which are described in detail in chapter 3.7.
Table 2: Overview of topological restrictions
Element Upstream elements Downstream elements
Area - n HPs
HydroPlant (HP) 1 Area n HGUs

1 HV
HydroValley (HV) - n HPs
Reservoir (RES) n HGUs n HGUs

n CHs n SWs
n SWs
Spillway (SW) 1 RES 0/1 RES or

0/1 CH
Channel (CH) n HGUs 0/1 RES or

n SWs 0/1 CH
n CHs
Turbine unit (HGU/T) 1 RES 0/1 RES or

0/1 CH
Pump unit (HGU/P) 1 RES 1 RES 3
Pump turbine unit (HGU/PT) 1 RES 1 RES3
3
Except for Pumped Storage Plants

Edition 08.2013
If they are part of a Pumped Storage Plant, pump units and pump turbine units do not require a downstream
reservoir.

Edition 08.2013
3.4 General Parameters
3.4 General Parameters
3.4.1 Time Steps
HTC is calculating with a fixed time step for the given planning horizon. The user can select the length of the
time step before start of the optimization between:
 time step 6 hour,
 time step 30 minutes,
 time step 15 minutes,
Input Data are read from non-periodic schedules at the corner points.
P [MW]
time grid
limit
effective
limit
t [time steps]
Figure 9: Reading of non-periodic schedules in HTC
Electrical demand is determined as mean value over the time step.
3.4.2 Planning Horizons
HTC is calculating on a planning horizon given by:


4
begin time
 end time4
The user can define the planning horizon freely in the defined time step. The number of time steps is given by
planning horizon and the length of a time step and has, of course, a strong influence on the calculation time.
4
Must be integer multiples of the selected time step

Edition 08.2013
3.5 System Features
3.5 System Features
3.5.1 Areas and Exchanges Among Areas
Each unit and each contract is assigned to one area of supply. Each of these Areas has its own demand and
can be connected to other Areas by limited interconnections. This model can be used for an optimization with
a simplified model of the electrical grid. It can also be used for an optimization on different markets with the
possibility to transfer power from one Area to another.
area A
area C
area B
area D
Figure 10: Example of area model wit 4 areas and 4 exchanges
One basic feature of HTC is to balance the total demand in each Area by use of the units’ generation,
optimizable power contracts, spot markets and the possibilities to transfer power from one Area to another.
The major results on Area level are total generation, total contracted power and the flows to other Areaa, as
given in Table 3. The results are subject to the direct constraints shown in Table 4.
Table 3: The Area's result
Description Type Unit Name
Total generation Schedule MW PowerProdSched1
Total contracted power (from optimizable Schedule MW PowerContractSched1

contracts and spot markets)
Power flows to other areas Schedule MW PowerTransferSched1

Edition 08.2013
3.5 System Features
Table 4: The Area's constraints
Total demand in the area Schedule MW LoadForecastSched
Total fixed power contracts in the area Schedule MW PowerIntchgSched
Total predefined generation in area Schedule MW PredefinedGenSched
Table 5: The PowerLine’s constraints
Limited transfer from one to another Area Schedule MW TransferMaxSched
Cost of the transfer from one to another Area Schedule €/MWh CostFacTransferSched
Limited transfer of R1/2/3/4/5Up from one to Schedule MW TransferR1/2/3/4/5UpMaxSched

another Area
PowerLine transfer change policy Value TransferChangePolicy
Cost of the transfer from one to another Area Schedule €/MWh CostFacTransferSched
The following implicit limits are also imposed:

The sum over the transferred power plus all exclusive reserves plus the biggest non-exclusive reserve must
be smaller equal to the TransferMaxSched as this schedule describes the over-all limit of transfer.
Note: the PowerLine is uni-directional. If the exchange should be bidirectional, two components of the type
PowerLine must be modeled.
If the TransferChangePolicy is set to AtFullHour, the PowerTransferSched1 can change only at full hours,
even for optimizations on a shorter time grid (15 min or 30 min ).
3.5.2 Regulation Services and Reserves
Regulation services and reserves are requirements on the units' ability to rapidly change their power output
due to incidents within the power system that need fast countermeasures.
These rapid changes influence the power output of the units' optimal generation schedule. For every time
horizon, the change in power output is desired, there are particularly equipped units that contribute to the
respective regulation services and reserves. Depending on the power system characteristics, there are
primary and secondary regulation and other regulation reserves like spinning reserve and minute’s reserve.
With HTC, all types of regulation services and reserves are treated in the same way; the specific needs are
respected by the time the rapid changes in the units’ power output are to take effect and by the units'
contribution to the respective regulation services and reserves. HTC provides five reserve classes that
represent any of the specific regulation services.
For every reserve class, the regulation requirements are given separately for every area and for upwards and
downwards regulation. These requirements must then be fulfilled by the units.
HTC determines the contribution of the units to the reserve classes as part of the overall optimization. It
considers reserves as transferable from one area to another respecting the free transfer capacities.

Edition 08.2013
3.5 System Features
The major results on area level are the regulation capability in all reserve classes and transfer of regulation
reserve between the areas, as shown in Table 6. These results are subject to the direct constraints of total
required regulation capability (Table 7). Some further input data are given only for the entire generation
system (Table 8)
Table 6: Regulation results on Area level
Regulation capability upwards Schedule MW Rsrv1/2/3/4/5UpSched1

for class 1/2/3/4/5
Regulation capability downwards Schedule MW Rsrv1/2/3/4/5DoSched1

for class 1/2/3/4/5
Transfer of reserve for class 1/2/3/4/5 Schedule MW Rsrv1/2/3/4/5UpTransferSched1

upwards regulation to other areas
Transfer of reserve for class 1/2/3/4/5 Schedule MW Rsrv1/2/3/4/5DoTransferSched1

downwards regulation to other areas
Table 7: Regulation constraints on Area level
Total required available reserve Schedule MW Rsrv1/2/3/4/5UpAmountSched

for class 1/2/3/4/5 up
Total required available reserve Schedule MW Rsrv1/2/3/4/5DoAmountSched

for class 1/2/3/4/5 down
Table 8: Regulation input data on System level
Time of activation for class 1/2/3/4/5 Value s Rsrv1/2/3/4/5Time
Switch ‘exclusive’ for class 1/2/3/4/5 Value {On,Off} Rsrv1/2/3/4/5Exclusive
Switch ‘on/off’ for class 1/2/3/4/5 Value {On,Off} Rsrv1/2/3/4/5On
For each unit the user can specify the contribution to the five reserve classes independently by selecting a
reserve mechanism. This reserve mechanism defines the strategy the unit contributes to the respective
reserve class. The following strategies are available:
 NoReserve
The unit does not contribute to the reserve class.
 PrimaryReg
The unit contributes to the reserve class if primary regulation is switched to On. The contribution is either
zero within a range between min/max limits. The constraints given in Table 9 are additionally observed
for the respective unit. A unit cannot contribute to more than one reserve class with reserve mechanism
PrimaryReg.

Edition 08.2013
3.5 System Features
 SecondaryReg
The unit contributes to the reserve class if secondary regulation is switched to On. The constraints given
in Table 10 are additionally observed for the respective unit. A unit cannot contribute to more than one
reserve class with reserve mechanism SecondaryReg.
 Spinning
The unit contributes to the reserve class if it is committed and its generation is not below minimum
power. The reserve contribution upwards is the difference between maximum generation and scheduled
generation; reserve contribution downwards is the difference between scheduled and minimum
generation.
Ramping limits/activation time and a user defined maximum contribution are additional constraints on
both reserve contributions.
 Standby
With this reserve mechanism, reserve contribution upwards is the difference between maximum and
scheduled generation; reserve contribution downwards is equal to the scheduled generation.
Ramping limits/activation time and a user defined maximum contribution are additional constraints on
both reserve contributions.
 StbyPump
StbyPump is for pumps and pump turbines. For units in turbine mode it works the same way as StandBy.
Units in pump mode contribute to the upwards reserve with their pumping power (absolute value). Pump
turbines that are offline contribute to the downward reserve with the (possible) pumping power.
Table 9: Primary regulation mechanism constraints
Maximum reserve contribution upwards Schedule MW PRupMaxMWSched
Minimum reserve contribution upwards Schedule MW PRupMinMWSched
Maximum reserve contribution downwards Schedule MW PRdoMaxMWSched
Minimum reserve contribution downwards Schedule MW PRdoMinMWSched
Upper generation limit reduced Schedule MW DeltaMaxPRSched
Lower generation limit increased Schedule MW DeltaMinPRSched
Table 10: Secondary regulation reserve constraints
Minimum upwards contribution to SR Schedule MW SRupMinMWSched
Maximum upwards contribution to SR Schedule MW SRupMaxMWSched
Minimum downwards contribution to SR Schedule MW SRdoMinMWSched
Maximum downwards contribution to SR Schedule MW SRdoMaxMWSched
Current contribution to SR Value MW SRcurrent

(measured value)
Symmetry condition for SR Value boolean SRsymmetryCondition

Edition 08.2013
3.5 System Features
To avoid schedules where the allocation of SR contributions frequently changes between (equal or very
similar) units, a tuning parameter (SAParam.SRchangePenalty) allows to penalize a change of the SR status
of a unit (similar to startup costs). To consider these “switching costs” In the first time interval of an
optimization, a unit’s current SR contribution is taken into account. If this measured value is not available, this
decision in the beginning of the planning horizon will be free (“of penalty costs”).
Table 11: Constraints for all reserve mechanisms (except prim. and sec.)
Maximum reserve contribution upwards Value MW Rsrv1/2/3/4/5UpMax
Maximum reserve contribution downwards Value MW Rsrv1/2/3/4/5DoMax
An example illustrates the relationship between reserve class, activation time and reserve mechanism:
consider five reserve classes assigned for primary regulation, secondary regulation, spinning reserve, minute
reserve and free capacity, which are served by the units hydro turbine, pump, pump turbine, run-of-river, gas
turbine, steam turbine and nuclear turbine. Their assignment to the reserve classes are then specified as
shown in Table 12: the unit 'hydro turbine' is assigned to Class 1 with reserve mechanism PrimaryReg, etc.
Table 12: Example of unit assignment to reserve classes by reserve mechanism settings
Class 1 Class 2 Class 3 Class 4 Class 5
Usage primary reg secondary reg spinning minutes free capacity
Activation Time n/a n/a >> >> >>
exclusive yes yes no no no
hydro turbine PrimaryReg SecondaryReg Spinning Standby Standby
pump NoReserve NoReserve StbyPump StbyPump StbyPump
pump turbine PrimaryReg SecondaryReg Spinning StbyPump StbyPump
run-of-river NoReserve NoReserve NoReserve NoReserve NoReserve
gas turbines PrimaryReg SecondaryReg Spinning Standby Standby
steam turbine PrimaryReg SecondaryReg Spinning Standby Standby
nuclear turbine PrimaryReg NoReserve Spinning Spinning Standby
The user can switch on/off the regulation requirements for specific reserve classes. A time value defines the
activation of the regulation (‘Activation Time’), which is critical for units assigned with ramp limit dependent
reserve mechanisms, like Spinning and Standby. A very long activation time means that ramp limits are no
restriction for this reserve class.
Another switch defines whether the power assigned to a specific reserve class is part of another reserve
class as well or whether power assignment is exclusive for the respective reserve class.
HTC determines the contributions of all units to the respective reserve classes as shown in Table 13.

Edition 08.2013
3.5 System Features
Table 13: Reserve results for units and plants
Available contribution upwards Schedule MW Rsrv1/2/3/4/5UpSched1

for class 1/2/3/4/5
Available contribution downwards Schedule MW Rsrv1/2/3/4/5DoSched1

for class 1/2/3/4/5
3.5.3 Area and System Costs
HTC minimizes the overall costs (and penalties of soft constraints) if operated under mode ‘FullPlanning’ and
maximizes the overall revenue if operated under the mode ‘Trade Optimizing Scheduler’. These costs are the
sum of costs of thermal units as defined in chapter 3.6.14, hydro units as defined chapter 3.7.2 and electricity
contracts 3.8.1. They are summarized for the user as given in Table 14, where the total sum of costs is the
sum of fuel costs, operating and maintenance costs and start-up costs.
Additionally, HTC provides the dual variables for all Area constraints, which can be interpreted as marginal
costs for these constraints, as given in Table 15.
Table 14: Cost overview data
Sum costs Schedule €/h CostSumSched1
Total sum costs (over planning horizon) Value € CostSum
Fuel costs (from FuelContracts) Schedule €/h CostFuelSched1
Total fuel costs (from FuelContracts) Value € CostFuel
Fuel costs (from FuelMarkets) Schedule €/h CostFuelMarketSched1
Total fuel costs (from FuelMarkets) Value € CostFuelMarket
Operating and maintenance costs Schedule €/h CostOMSched1
Total operating and maintenance costs Value € CostOM
Start-up costs Schedule €/h CostStartUpSched1
Total start-up costs Value € CostStartUp
Cost/revenue from EnergyContracts Schedule €/h CostContractSched1
Total cost/revenue from EnergyContracts Value € CostContract

Edition 08.2013
3.5 System Features
Table 15: Dual variables
Duals of demand in each area Schedule €/MWh DualDemandSched1
Duals of heat balance equation in zone Schedule €/MWth DualCogenSched1

Edition 08.2013
3.6 Thermal Subsystem Features
3.6.1 FuelTypes
A (fossil) fuel type describes a type of primary energy source, which is characterized by a (constant) calorific
value. Its HTC attribute definition is given in Table 16.
Table 16: Fuel attributes definition
Type Value Name FuelType

5
Calorific value Value GJ/Dim FuelHeatContent
3.6.2 FuelContracts
A FuelContract describes a contract on primary energy, which is characterized by a fuel type and a (time
dependent) price. One FuelContract can supply an arbitrary number of thermal units. The usage of a fuel can
be limited in flow and volumes over the time.
Long-term fuel limitations are supported by a fuel target schedule, a target value for the accumulated
consumption. It defines the amount of fuel to be used within the planning horizon as difference between the
value at the end of the planning horizon and the current consumed volume. If the long-term limitation ends (or
"is reset") within the planning horizon, the accumulated target has to be reset to zero, and two limits are
respected in HTC, the first from the beginning of the planning horizon to the end of limit 1, the second from
beginning of limit 2 to the end of the planning horizon (cf. Figure 11).
The target limit can be specified as minimum, maximum, target (minimum + maximum) or open. Alternatively,
the user can use a shadow price, which is added to the fuel price but not part of the cost determination.
In addition to the target conditions the flow can be limited by a minimum and maximum schedule.
A major feature of HTC is the management of the available FuelContracts in the thermal generation system.
The main result attributes per fuel contract are shown in Table 17, their direct constraints in Table 18 and
further input data is given in Table 19.
Dim’ is used for Dimension, it may be any desired fuel dimension as ton, MBTU, SKE, …
5

Edition 08.2013
HTC-plan
Target schedule
HTC-limit
current
time
Figure 11: Usage of fuel targets in HTC
Table 17: FuelContract result attributes
Consumed fuel flow Sched Dim/h FuelConsumptionSched1
Accumulated consumption Sched Dim AccConsumptionSched1
Table 18: FuelContract constraints
Minimum fuel flow Sched Dim/h FuelMinSched
Maximum fuel flow Sched Dim/h FuelMaxSched
Fuel target schedule Sched Dim FuelTargetSched
Table 19: FuelContract input data
Fuel price schedule Sched €/Dim FuelPriceSched
Shadow price schedule Sched €/Dim FuelShadowPriceSched
Current accumulated fuel consumption Value Dim CurrentAmount
Switch for fuel management Value {Open, OptimizationType

(Flow limits are always active) Min,
Max, Target,
Shadow}

Edition 08.2013
3.6.3 FuelStocks
A FuelStock serves as balance node for a specific type of fuel (cf. chapter 3.6.1).
A FuelStock can be connected to
 ThermalGeneratingUnits (TGUs) to supply their fuel consumption
 FuelContracts for import/purchase of fuel through bilateral contracts
 FuelMarkets for import and export of fuel
3.6.4 Fuel Restrictions on More than One Fuel
Fuel restrictions on several FuelContracts are handled by means of Fuel Restriction Groups. Combined limits
(several groups on one fuel contract) are supported as well. This feature is also used to model pipeline
constraints. This allows the user to handle
 flow limits
 daily fuel amount limits
 limited amount on freely defined period
for a group of FuelContracts (of the same fuel type) 6 . The respective fuel group attributes are summarized in
Table 21.
HTC will determine the total consumption of the fuel group respecting these limits.
Table 20: FuelRestrictionGroup results
Fuel flow Sched Dim/h FlowSched1
Accumulated flow Sched Dim AccFuelSched1
Daily accumulated flow Sched Dim AccDailyFuelSched1
Table 21: FuelRestrictionGroup attributes
Current accumulated fuel Value Dim CurrentAmount

consumption
Accumulated fuel consumption on Value Dim DailyCurrentAmount

day of begin of the planning horizon
Minimum fuel flow Sched Dim/h MinFlowSched
Maximum fuel flow Sched Dim/h MaxFlowSched
Minimum daily fuel amount Value Dim DailyMinSched
Maximum daily fuel amount Value Dim DailyMaxSched
6
. The group may also contain only one FuelContract

Edition 08.2013
Begin time of limited period Value Date/Time BeginTime
End time of limited period Value Date/Time EndTime
Minimum amount in limited period Value Dim MinAmount
Maximum amount in limited period Value Dim MaxAmount
3.6.5 ThermalGeneratingUnits
A ThermalGeneratingUnit (TGU) is used to model a set of machines that convert primary energy (Pin) into
electrical energy (Pel) and/or a cogeneration product (Pth). This model applies for single units. It is also used
to model the components of a combined cycle plant that convert primary energy into electrical energy and/or
high pressure steam, components that convert high pressure steam into electrical energy and/or low pressure
steam and components that convert low pressure steam into the cogeneration product.
The unit type determines the underlying unit model. The following types are supported:
 CombustionBoiler (also auxiliary boilers)
 CombustionUnit (combustion turbine + generator)
 CombustionUnit_HRSG: combustion unit with heat recovery steam generator
 CombustionUnit_HRSG_BP: combustion unit with HRSG and bypass
 CombustionUnit_HRSG_SF: combustion unit with HRSG and supplementary fire
 CombustionUnit_HRSG_SF_BP: combustion unit with HRSG, supplementary fire and bypass
 SteamReducer: (reduction valve,)
 SteamDump
 SteamTurbineBackPressure: steam turbine – type back pressure
 SteamTurbineCondensing: steam turbine – type condensing
 SteamTurbineExtraction: steam turbine with extraction


7
SteamUnit: steam unit (boiler + steam turbine condensing + generator)
 Distiller (desalination, MED, MSF, or similar….): consumes power and steam, produces desal. water
 ReverseOsmosis: consumes power, produces desal. water

 ElectricalHeater: consumes power, produces steam / heat
Some TGU types are only relevant with optional HTC modules or features.
3.6.6 Energy Consumption of ThermalGeneratingUnits during Operation
The energy consumption of TGUs during operation is determined by a three-dimensional characteristic, the
PrimaryEnergyPowerCurve3D (PEP). The characteristic is represented by an array of points. HTC
7
Nuclear units are modeled as steam units

Edition 08.2013
determines the energy consumption by linear interpolation. The envelope of the characteristic defines the
operating range for the mode On, as depicted in Figure 15. In order to span a region as operation range, two
points with equal Pth must be provided. Mismatching Pth result in fixed operation, illustrated by the points A
and B in Figure 12. Examples of PEPs for various unit types are given in Figure 13 and Figure 14. The
attribute definition of the PEP (PrimaryEnergyPowerCurve3D) is shown in Table 22.
Pth
A
B
Pel
Figure 12: PEP’s operating range
Pin(Pel,Pth)
Pth3
Pth2
Pth1
Pth0
Pel
Figure 13: Example of a PEP for an extraction Steam Turbine (operating range is shaded)

Edition 08.2013
Pin(Pel)
Pth4
Pth3
Pth2
Pth1
Pel
Figure 14: Example of a PEP for CUHRSG (operates on a curve in space)
Table 22: The TGU's PEP attribute
3 dimensional curve 3D Curve PrimaryEnergyPowerCurve3D

generated Pel MW
consumed fuel/steam Pin GJ/h / MWth
produced heat/steam Pth MWth
The following table gives an overview of the unit types and some characteristics of their PEP curves (some
unit types are only available with the optional module “Cogeneration”):
Table 23: Interpretation of axis of PEP depending on unit type
Unit type Pel Pin Pth Comment
CombustionBoiler - fuel steam / heat Pin is a monotonic

consumption production function of Pth
CombustionUnit electricity fuel - Pin is a monotonic

production consumption function of Pel
CombustionUnit_HRSG electricity fuel steam / heat Pin, Pth are monotonic

production consumption production functions of Pel
CombustionUnit_HRSG_BP electricity fuel steam / heat Pin, Pth are monotonic

Pth zero is allowed

(HRSG off)
CombustionUnit_HRSG_SF electricity fuel steam / heat Pth is a second

production consumption production independent variable
Pin is a function of Pel

and Pth

Edition 08.2013
Unit type Pel Pin Pth Comment
CombustionUnit_HRSG_SF_BP electricity fuel steam / heat Pth is a second

Pth zero is allowed

(HRSG off)

and Pth
SteamReducer - steam steam / heat Pin is a monotonic

consumption production function of Pth
SteamDump - steam 0 No output, only steam

consumption consumption
SteamTurbineBackPressure electricity steam steam / heat Pin, Pth are monotonic

SteamTurbineCondensing electricity steam 0 Pin is a monotonic

production consumption function of Pel
SteamTurbineExtraction electricity steam steam / heat Pth is a second


and Pth
SteamUnit electricity fuel steam / heat Pth is a second


and Pth
Distiller electricity steam water

consumption consumption production
(< 0)
ReverseOsmosis electricity 0 water

consumption production
(< 0)
ElectricalHeater electricity 0 steam / heat

consumption production
(< 0)
For gas turbines with bypass stack (CombustionUnit_HRSG_BP and CombustionUnit_HRSG_SF_BP), the
PEP curve has two distinct branches:
Pth = 0 for bypass operation (open cycle mode
Pth > 0 HRSG in operation (closed cycle mode
Setpoints (Pel|Pth) between these two branches are not allowed, except during startup or shutdown.

Edition 08.2013
3.6.7 Starting and Stopping of ThermalGeneratingUnits
One of the main results of HTC is the determination of the unit commitment schedules, the
CommitmentSched1, of the thermal units. The commitment is given as an enumeration.
 Off: the unit is off
 StartPrepHot: the unit is prepared for a hot-start and not yet synchronized
 StartHot: the unit is synchronized and following its hot-start procedure while running up to minimum
generation
 StartRestHot: the unit is above minimum generation but still limited due to recent start-up
 On: the unit is above minimum generation and can be dispatched without limitations from the start-up
 StopPrepare: the unit is prepared for shutdown but above minimum generation
 Stop: the unit is ramping down (below minimum generation) but still synchronized
Two more start-up procedures – warm-start, cold-start – are supported in the same way as hot-start resulting
in the options StartPrepWarm, StartWarm, StartRestWarm, StartPrepCold, StartCold and StartRestCold.
Table 24 gives a summary, with ‘X’ representing ‘Hot’, ‘Warm’ and ‘Cold’.
Table 24: The TGU’s commitment schedule attribute
TGU’s commitment Schedule {Off, CommitmentStateSched1

StartPrepX,
StartX,
StartRestX,
On,
StopPrepare,
Stop}
The StartUpTable (SUT) determines the start-up procedure; i.e. it defines limitations for generation (electrical
and/or thermal) and fuel/steam consumption from the beginning of the resp. startup sequence of a TGU, until
stable operation is reached. 3 procedures are supported; depending on the downtime, HTC will select the
hot-, warm- or cold-start procedure. The downtime is defined as the time between last de-synchronization and
the next scheduled synchronization during start-up. The downtime before synchronization gives the upper
limits for the procedure (zero refers to the hot-start procedure, …). The SUT is defined by a set of data points
composed of time and power values. A linear interpolation between those data points make up the SUT. The
first data point is <0 h, 0 MW. 0 GJ/h> by convention. The TGU’s current minimum and maximum generation
limits of stable operation, Pmin and Pmax (cf. chapter 3.6.9), determine the SUT’s impact on the TGU’s
operation range, as depicted in Figure 15. The part of the SUT below Pmin is treated as strict limit, whereas
the SUT’s fragment between Pmin and Pmax is treated as upper limit on the power output. For
CombustionBoilers the SUT defines the limits on the output of steam / heat.

Edition 08.2013
P (MW)
Pmax
Pmin
S t
StartPrepX StartX StartRestX On

Fixed power output Constraints of stable operation
Operating range Start-up power restriction
SUP data points
Figure 15: Start-up power curve with power restriction in operation range
Since optimization is done in discrete time steps, the SUT is converted to time steps as well. The conversion
starts at the point of synchronization, ‘S’ in Figure 15, which is, by convention, put at the beginning of a time
step. The value assigned to the time steps is the integral of the SUT’s linear interpolation over the interval of
the respective time step. Figure 16 gives an illustration for Pel. The details of this integral are described the
Technical Specification.
P (MW)
Pmax
Pmin
S t
Time step interpolation Constraints

Constraints of stable operation
Linear interpolation Operating range
Figure 16: Time step discretization of the start-up power curve
The ShutDownPowerCurve2D (SDP) determines the shutdown procedure from begin of ramping down until
de-synchronization. It serves as an upper limit for the output power (strict limit below minimum generation), as
illustrated by Figure 17. For CombustionBoilers it defines the limits on the output steam / heat.
The value assigned to the time steps is the integral of the SDP’s linear interpolation over the interval of the
respective time step.

Edition 08.2013
Table 25 shows the attribute definitions of these two characteristics.
Table 25: The TGU's SUT and SDP
Start-up table Table StartupTable

time after initiating start-up h
Pel: (upper limit on) produced power MW
Pin: fuel / steam consumption GJ/h
Pth: (upper limit on) produced thermal output MW
downtime before synchronization h
Shutdown power curve 2D Curve ShutDownPowerCurve2D

time after initiating shutdown h
upper limit on produced Pel or Pth MW
P [MW]
Pmax
Pmin
On StopRest Stop t [time steps]

Figure 17: Example of an SDP and its consequences on the commitment
Furthermore, the commitment schedule is subject to the direct constraints of minimum downtime, minimum
uptime and the TGU's availability.
Minimum uptime is the minimum time that a TGU has to remain online after synchronization (i.e., minimum
time between synchronization and de-synchronization). Minimum downtime, is the minimum time that a TGU
has to remain offline after de-synchronization (i.e., minimum time between de-synchronization and
synchronization). Table 26 gives a summary.
The availability schedule, GenUnitOpSched, restricts the possible commitment states of a unit. Its values are:
 NotAvail: the unit must be de-synchronized,
 Avail: the unit can be scheduled freely,
 MustOn: the unit must be synchronized,
 FixP: the unit must follow user defined schedule or

Edition 08.2013
 FixPReserve: like FixP but the unit still can contribute to the reserves.
 MustOnPR MustOn with PR contribution enforced
 MustOnSR MustOn with PR contribution enforced
 MustOnPRSR MustOn with PR and SR contribution enforced
 FixPPR FixP with PR contribution enforced
 FixPSR FixP with PR contribution enforced
 FixPPRSR FixP with PR and SR contribution enforced
FixP overrules the constraints on minimum power, ramps, and if set for the whole planning horizon also the
minimum up- and downtime. It also overrules the reserve mechanisms, i.e. a unit on FixP does not contribute
to any reserve.
Table 26: The TGU's direct start-up constraints
Minimum downtime Value min DownTimeMin
Minimum uptime Value min UpTimeMin
Availability Schedule NotAvail, GenUnitOpSched

Avail,
MustOn,
FixP,
FixPReserve,
MustOnPR,
MustOnSR,
MustOnPRSR,
FixPPR,
FixPSR,
FixPPRSR
3.6.8 Iterpretation of the start-up power curve
HTC supports two types of start-up power curves, depending on the start-up power curve selection
(StartUpPowerCurveSel, see Table 27). In case ‘WithRest’ is selected, the SUP is treated as described in
section 3.6.7. In the case ‘WithoutRest’, the SUP is treated as fixed generation limit up to its last data point,
which lies between Pmin and Pmax, as depicted in Figure 18. When the last data point of the SUP is
reached, the unit is free to be scheduled for stable operation, as described in section 3.6.1.
Table 27: The TGU's Start-up power curve selection.
Start-up power curve selection Value WithRest StartUpPowerCurveSel

WithoutRest

Edition 08.2013
P (MW)
Pmax
Pmin
S t
StartPrepX StartX On
Fixed power output Constraints of stable operation

Operating range SUP data points
Figure 18: Start-up power curve without power restriction in operation range
Table 28: The TGU's Re-Planning time windows
Maximum time shift forward for sync Value min MaxSyncShiftForward
Maximum time shift backward for Value min MaxSyncShiftBackward

sync
Maximum time shift forward for de- Value min MaxDeSyncShiftForward

sync
Maximum time shift backward for de- Value min MaxDeSyncShiftBackward

sync
3.6.9 Stable Operation of ThermalGeneratingUnits
The main result of HTC are the generation schedules. Table 29 gives a summary for thermal units. In addition
to the availability schedule (GenUnitOpSched, cf. chapter 3.6.7) and the operating range defined by the PEP
(cf. chapter 3.6.6) the unit’s power output is restricted by the limits of minimum capacity (MinimumMW) and
maximum capacity (MaximumMW) and the limits of minimum derated capacity (GenUnitDerMinSched) and
maximum derated capacity (GenUnitDerMaxSched) as shown in Table 30, arising from unit maintenance.
The minimum and maximum capacity limits are the outermost technical limits and serve as input check for the
time-dependent derated capacity limits. For TGU types that (also) produce a cogen product (steam etc.),
corresponding restrictions also apply to this product.

Edition 08.2013
Table 29: The TGU's results
Electric power generation Schedule MW PowerProdSched1
Thermal power generation Schedule MWth CogenProdSched1
Table 30: The TGU's direct constraints
Maximum capacity Value MW MaximumMW
Minimum capacity Value MW MinimumMW
Maximum derated capacity Schedule MW GenUnitDerMaxSched
Minimum derated capacity Schedule MW GenUnitDerMinSched
Maximum cogen capacity Value MWth CogenProdMax
Minimum cogen capacity Value MWth CogenProdMin
Maximum derated cogen capacity Schedule MWth CogenProdMaxSched
Minimum derated cogen capacity Schedule MWth CogenProdMinSched
3.6.10 Limited Ramp Rate
Generation rate limits define the maximum change of power output of a unit between two time steps. The
limits can be different for generation increase and decrease. The limits are only active within the operating
range. Below minimum power output HTC follows strictly the curves for start-up or shutdown (cf.
chapter 3.6.7). Depending on the unit type additional rate limits on the thermal production are given as shown
in Table 31.
In addition to the ramp rate limits any change in generation and/or thermal production can be penalized to
achieve smooth operation schedules. These penalties are given unit type dependent during system tuning.
Modification of these values is restricted to special users.
Table 31: The TGU's ramp rate limits
Maximum ramp up for electricity Value MW/min RampRateUp

output
Maximum ramp up for electricity Value MW/min RampRateUpSched

output
Maximum ramp down for electricity Value MW/min RampRateDown

output

Edition 08.2013
Maximum ramp down for electricity Value MW/min RampRateDownSched

output
Maximum ramp up for thermal output Value MWth/min RampRateCogenUp
Maximum ramp down for thermal Value MWth/min RampRateCogenDown

output
3.6.11 Fuel Consumption of Thermal Units During Stable Operation
For a thermal unit that consumes fuel the user must assign FuelStocks. Up to five FuelStocks can be
assigned to the unit. HTC allocates the energy consumption as calculated from the PEP (cf. chapter 3.6.6) to
the available contracts and determines the individual fuel consumptions as shown in Table 32. X = 1…5
represents the assigned fuels in alphabetical order. The allocation is optimized using the assigned fuel
constraints.
Table 32: The TGU’s fuel consumption results
Consumption of FuelContract X Schedule GJ/h FuelXConsumptionSched1
3.6.12 Fuel Consumption Limitations for Co-firing
The fuel rates during co-firing can be limited for each TGU to a user-defined minimum and maximum value
for the assigned fuels. This is a direct constraint on the consumption of fuels as described in chapter 0. The
limits must allow the resulting fuel rates to add up to 1.
Table 33: The TGU’s fuel rate limits
Minimum rate of fuel X Schedule 1 FuelMinRateXSched
Maximum rate of fuel X Schedule 1 FuelMaxRateXSched
3.6.13 Fuel Consumption of Thermal Units During Start-up
The fuel consumption of a TGU during the startup procedure differs from the consumption during stable
operation. While the latter is determined by the PEP curve (ch. 3.6.6) or the FCP table curve (ch. Error!
Reference source not found.), the former is given by the Pin column of the SUT table (ch. 3.6.7)
This start-up fuel consumption is especially significant for big steam units and relevant as some units use
another more expensive fuel for start-up than the fuel(s) used for stable state operation. Even more, these
units use the start-up fuel also during the ramp up phase, i.e. during the commitment states StartPrepX and
StartX (until a minimum stable generation or the end of the SUT curve is reached).

Edition 08.2013
Therefore HTC allows to define a specific start-up fuel. The fuel consumption during operation (and also
during ramp-up) is determined from the PEP (cf. chapter 3.6.6).
The additional fuel consumption - as determined from the SUT - is given in the time step(s) before
synchronization and is distributed over the preparation phase of the start-up, as defined in the start-up power
table (cf. chapter 3.6.7).
Table 34: The TGU’s start-up fuel consumption results
Consumption of the start-up fuel. Schedule GJ/h FuelSUConsumptionSched1
The following data are relevant for the determination of start-up fuel:
 name of FuelStock used as the start-up fuel
If no separate start-up fuel is specified, the first assigned fuel of this unit will be taken.
3.6.14 Cost Determination of ThermalGeneratingUnits
A major part of the objective and a main result of HTC is the determination of the costs for operating the
thermal units like fuel costs, operating and maintenance cost and start-up cost, as well as the sum over all of
them. Table 35 gives a summary. The fuel costs are determined as sum of the fuel consumption(s) of the unit
and the prices of the corresponding fuel contract(s).
Table 35: TGU's cost results
Sum costs Schedule €/h CostSumSched1
Fuel costs Schedule €/h CostFuelSched1
Operating and maintenance costs Schedule €/h CostOMSched1
Start-up costs Schedule €/h CostStartUpSched1
The operation and maintenance costs are determined from the produced energy and a time-dependent
factor. Depending on the unit type the factor is multiplied with the produced electric energy (for all units that
produce electricity) or is multiplied with the produced thermal energy (CombustionBoilers and
SteamReducers).
Optionally, also fixed operation and maintenance costs are added as result of hours of operation (hours with
electric and/or thermal production) and a time dependent factor. Table 36 shows a summary of the cost
relevant attributes.
Start-up costs are determined as sum of fixed start-up costs and the costs for the additional fuel consumption
due to the start-up as described in chapter 3.6.12.
Optionally, shadow start-up costs can be considered (as an addition to the fixed start-up costs). They are
counted in the objective function of the optimizing algorithm, but not considered in the cost results. This is a
simple way to model e.g. a "risk premium" to avoid a shut-down/start-up cycle of a TGU.

Edition 08.2013
As a further option, additional costs that arise from the usage of a particular fuel with a particular unit are
considered by a fuel price adder.
Table 36: TGU's cost attributes
Operation and maintenance cost Schedule €/MWh GenUnitOMFactSched

factor
fixed operation OM cost factor Schedule €/h GenUnitFixOMFactSched
Additional start-up costs Value € StartupCostAddition
Shadow start-up costs Value € StartupCostShadow
Price adder for FuelContract X Value €/Dim FuelXPriceAdder
3.6.15 Thermal Plants
Thermal plants are either groups of conventional thermal units (CombustionUnits or SteamUnits) or Common
Steam Header Plants (see chapter 3.6.16) or Combined Cycle Plants (see chapter Error! Reference source
not found.). HTC determines the sums (as sum over the units of the plant) of generation and contribution to
reserve classes as defined in Table 37.
Table 37: Thermal plant’s results
Scheduled plant generation Schedule MW PowerProdSched1
Contribution upwards to class Schedule MW Rsrv1/2/3/4/5UpSched1

1/2/3/4/5
Contribution downwards to class Schedule MW Rsrv1/2/3/4/5DoSched1

1/2/3/4/5
Scheduled fuel costs Schedule €/h CostFuelSched1
Total fuel costs Value € CostFuel
Scheduled operation & maintenance Schedule €/h CostOMSched1

costs
Total operation & maintenance costs Value € CostOM
Scheduled start-up costs Schedule €/h CostStartupSched1
Total start-up costs Value € CostStartUp
Scheduled sum of costs Schedule €/h CostSumSched1
Total sum of costs Value € CostSum

Edition 08.2013
3.6.16 Common Steam Header Plants
A CommonSteamHeaderPlant is used to model combined cycle plants or complex thermal plants as

combination of the components of the plant. Each component is modeled as a unit. For the unit types within
the plant please refer to chapter 3.6.5 above.
Fuel
Gas turbine Gas turbine
Common steam header
Steam turbine
Figure 19: Common steam header plant model of a 21 combined cycle plant
The CommonSteamHeader (CSH) serves as balance node between the units producing steam (upstream)
and consuming steam. As HTC models the steam flow as flow of thermal energy only there are no specific
parameters for the common steam header.
Multiple pressure and temperature levels within a plant can be modeled as well by several
CommonSteamHeaders. Figure 20 gives an example of a plant with 4 levels. The number of levels
(CommonSteamHeaders) per plant is unlimited.
Different stages of one steam turbine (e.g. high-pressure, medium-pressure and low-pressure) can be
modeled by separate components, if the intermediate extraction shall be subject of optimization. Additional
constraints (simultaneous run) connect the different stages, cf. chapter 3.9.4.
Fuel
Gas turbine
Boiler
Common steam header

Steam reducer
Steam turbine

Edition 08.2013
Figure 20: Example of a complex common steam header plant

Edition 08.2013
3.7 Hydro Subsystem Features

The base of all electric hydro generation is a natural hydrological system beginning with the precipitation in
the catchment area of the topmost river or lake used as reservoir. Therefore, apart from electrically and
economically optimal solutions, the purpose of HTC is to provide management support of an entire hydro
system including its ecologic conditions and legal clauses, which is further described in chapter 3.7.1.
Under consideration of these ecologic conditions, the water used for electric energy generation can be
assigned an economic value in terms of revenue or cost, driven by the hydro units’ energy conversion, as
described in chapter 3.7.2.
Ecologic and economic aspects, technical and operational limits and constraints form the conditions under
which cost optimal operation of the hydro units is being requested from HTC. These technical and operational
limits belong to two categories, constraints on starting and stopping the hydro units and constraints on the
level of generated electricity, as described in chapter 3.7.3 and 3.7.5, respectively. The optimal solution
calculated by HTC then contains schedules for both categories as well, a schedule for commitment state and
the scheduled electricity generation.
Power plants are then composed out of hydro units and Reservoirs, as described in chapter 0.
3.7.1 Management of Hydro Chains
The topmost element of a hydro chain is the water reservoir. The height of its dam gives the maximum level
the water reservoir can be filled up to without overflow. The minimum level results from hydrological
considerations like minimum water for fishery or reliability considerations like energy reserve. Due to the
geological structure of its basin the water reservoir’s content depends on the level. This dependency is
modeled by a curve, the ContentLevelCurve3D, which describes the water content as a function of the water
level and, optionally, of the water release as illustrated by Figure 21 and Figure 22. The level is measured in
meters above main sea level, the Reservoir’s content is given in Mm3. Table 38 gives a summary of the
Reservoir’s hydrological attributes.
content (Mm3)
max
min
level (m)
min max
Figure 21: Reservoir’s ContentLevelCurve3D

Edition 08.2013
content (Mm3)
max
min
level (m)
min max
Figure 22: Release dependent ContentLevelCurve3D
Table 38: Reservoir’s hydrological attributes
3D content-level curve 3D Curve ContentLevelCurve3D

level m
content Mm3
discharge (optional) m3/s
Minimum Reservoir level Schedule m LevelMinSched
Maximum Reservoir level Schedule m LevelMaxSched
Natural inflow Schedule m3/s InflowForecastSched
The Reservoir’s water balance is driven by its inflow and discharge. While inflow results from natural inflow
reflecting the amount of water coming from the Reservoir’s catchment area or upstream rivers, the discharge
has a more elaborate set of causes. Apart from discharge due to hydrologic reasons like evaporation and
percolation, there is discharge resulting from power system operation as well. Furthermore, water may be
drawn for agricultural purpose. The hydrological factors and legal clauses are modeled by use of Spillways,
which release water from the Reservoir without generating electric energy. The amount of water released are
limited by minimum and maximum discharge constraints as shown in Table 40. The optimal discharge is
calculated by HTC (cf. Table 39).
The optimal discharge is calculated by HTC (cf. Table 39). Overflow Spillways are a special case protecting
the dam against overflow or excess pressure. Their amount of water released by these Spillways is
determined by the Reservoir’s level with a given characteristic modeled by a curve, the
DischargeLevelCurve2D
Table 39: Spillway’s result
Discharge Schedule m3/s DischargeSched1

Edition 08.2013
Table 40: Spillway’s attributes
Type of spillway Value {Controlable, SpillwayType

Overflow}
Minimum spilled water Schedule m3/s DischargeMinSched
Maximum spilled water Schedule m3/s DischargeMaxSched
Discharge level curve 2D Curve DischargeLevelCurve2D

level m
discharge m3/s
Further requirements for a model of hydrological conditions are minimum flow rate on a river for fishery or
minimum water gauge for shipping. These constraints are respected with the HTC topology element Channel.
They are employed to model water flow time delays, level limits or flow limits.
The water flow time delay is the time difference between water entering the Channel and leaving the
Channel. During HTC optimization it is rounded to an integer multiple of the time step. Limits on the water
flow are given by means of minimum and maximum water flow rate and minimum and maximum water level
at the beginning of the Channel. Flow rate and water level are interdependent due to the geological structure
of the river Channel, which the HTC model incorporates by the Channel characteristic, a 3-dimensional curve
specifying their interrelation, the DischargeLevelCurve3D. This curve is further used to compute net heads for
turbines discharging into the Channel.
A summary of the Channel's attributes is given in Table 42. The attributes optimized by HTC are discharge
and level as shown in Table 41.
Table 41: Channel’s results
Level Schedule m LevelSched1
Table 42: Channel’s attributes
Level of Channel versus flow in 3D Curve DischargeLevelCurve3D

Channel m
level m3/s
discharge m
level of downstream Reservoir
(optional)
Water flow time delay Value min WaterRunTimeDelay
Forecasted inflow Schedule m3/s InflowForecastSched
Minimum flow rate Schedule m3/s DischargeMinSched

Edition 08.2013
Maximum flow rate Schedule m3/s DischargeMaxSched
Minimum level of Channel Schedule m LevelMinSched
Maximum level of Channel Schedule m LevelMaxSched
3.7.2 The Economic Value of Water
HTC manages the hydro chain for optimal use of water contained in the Reservoirs, by considering the size of
the Reservoirs, their inflow and discharge together with the time delay the water needs to run through a
Channel. Spillways are used wherever water needs to follow specific paths without generation or do manage
high inflow situations, where more water is available than can be used in generation.
For optimal hydro management the Reservoir’s level are treated in one of two possible ways, starting from an
initial level at the beginning of the planning period. The first strategy defines a Reservoir target level that is
matched at the end of the planning period within a given range. If deviations from the target level exceed this
range, they are treated with cost penalty. The second planning strategy offered by HTC manages the
Reservoir’s level by shadow prices, which reflect a financial value of the Reservoir’s content at the end of the
regarded planning horizon.
Shadow prices as well as target levels may be provided by a preceding mid term planning procedure of jROS.
In this case the topmost, big Reservoirs are usually managed by shadow prices, while the smaller
downstream Reservoirs are treated with target levels in order to let HTC take care of optimal short term water
management.
Based on above attributes (summarized in Table 44) HTC calculates optimal schedules for Reservoir content,
Reservoir level, water release through turbines and water release without generation of electricity (see Table
43).
Table 43: Reservoir’s results
Content Schedule Mm3 ContentSched1
Level Schedule m LevelSched1
Sum of water releases Schedule m3/s DischargeSched1
Turbinated water release Schedule m3/s TurbSched1
Spilled water release Schedule m3/s SpillSched1
Pumped water Schedule m3/s PumpSched1
Table 44: Reservoir’s attributes
Initial Reservoir level Value m LevelCurrent
Reservoir target level Schedule m LevelTargetSched

Edition 08.2013
Allowed deviation from target volume Value Mm3 ContentDiffToFinalLimit
Penalty for deviation from target Value €/Mm3 PenaltyCostFinalContent

volume
Reservoir shadow price Schedule €/Mm3 ShadowPriceSched
Electric energy generated by hydro units depends on the three factors discharge, net head and turbine
efficiency, where discharge is optimized by HTC. The net head results from the level difference between
upstream Reservoir and downstream Reservoir or downstream Channel in case the unit is equipped with
Kaplan or Francis turbines. For Pelton turbines, the downstream level is given by the turbine’s reference
level. The reference level for Francis and Kaplan turbines is set to -1.
The turbine unit’s efficiency is itself a function of discharge and net head, modeled by a 3D Curve as shown
in Figure 23. In pumping mode, the units run at constant power. The pump efficiency is a function of the head,
as depicted in Figure 24.
efficiency [1]
head [m] 350m
300m
250m
q [m3/s]
Figure 23: Hydro turbine’s power efficiency diagram
efficiency [1]
head [m]
Figure 24: Pump unit’s power efficiency diagram
Based on the generated electric energy, the hydro unit’s costs are determined. They originate from the two
sources, water cost and energy dependent cost. Water costs are given by the shadow price of the upstream

Edition 08.2013
Reservoir. In case this Reservoir is parameterized for target level instead of shadow price, there are no water
costs for the HGU. A penalty on the Reservoir’s target level is used instead.
Energy dependent costs are further composed of the two parts transport costs and operation and
maintenance costs, where the former represent costs resulting from electricity transport, e.g. network fees
and the latter include all additional energy dependent costs. Both cost factors are considered within a single
attribute, the GenUnitOMFactSched. Generation and pump operation have a separate set of cost coefficients,
as indicated by Table 45. The costs resulting from HTC optimization are given in Table 46.
In pump operation, the costs result from the source of electric energy used for pumping, i.e. a thermal
generation unit or an import contract. HTC optimization decides pump operation for two reasons. Either there
are hydrologic reasons to do so, e.g. the target level of a Reservoir must be reached, or there is a financial
benefit, because an increase in the value of the water stored in Reservoirs is higher than additional cost of
pump operation.
Table 45: Hydro unit’s consumption and cost attributes
Reference level Value m LevelReference
Efficiency curve 3D Curve EffiDischargeCurve3D

discharge m3/s
efficiency 1
head m
Specific additional operation cost Schedule €/MWh GenUnitOMFactSched
Efficiency curve 2D Curve PumpEfficiencyHeadCurve2D

head m
efficiency 1
Power demand Value MW PumpMW
Specific additional operation cost Schedule €/MWh GenUnitOMFactPumpSched

for operation as pump
Table 46: Hydro unit’s cost related results
Operation and maintenance cost Schedule €/h CostOMSched1
Total operation and maintenance Value € CostOM

cost
Startup costs Schedule €/h CostStartupSched1
Total startup costs Value € CostStartup
Sum of costs Schedule €/h CostSumSched1

Edition 08.2013
3.7.3 Starting and Stopping of Hydro Units
For the operator of a hydro system it is essential to know when to switch on the hydro units and whether the
hydro unit should be operated in turbine or pump mode. HTC optimizes these switch-on and switch-off
decisions by defining the commitment schedule. In contrast to thermal units (see chapter 3.6.7) the
commitment schedule of hydro units has three options:
 the unit is operated as turbine,
 the unit is operated as pump or
 the unit is switched off
and there are no start-up procedures that need to be taken into consideration, as ramping limits can be
neglected within the HTC time steps.
In order to force HTC to select a specific decision due to operational restrictions, an availability schedule can
be given, specifying whether a particular unit is available for optimization, whether it must run or whether it is
shut down due to maintenance or forced outage. Furthermore, the commitment schedule is subject to the
constraints of minimum uptime and downtime. A summary of these direct constraints is given in chapter 3.7.4.
3.7.4 Start-up Cost of Hydro Units
Hydro units are assigned start-up cost on a per start-up base, in €/start-up. Pump units and turbine units have
separate set start-up cost coefficients.
Table 47: Hydro unit’s commitment constraints and cost parameters
Availability Schedule {Available, GenUnitOpSched

Must Run,
Not Available}
Minimum downtime Value min DownTimeMin
Minimum uptime Value min UpTimeMin
Startup costs for pumping Value € StartupCostPump
Startup costs for turbination Value € StartupCostTurb
3.7.5 Stable Operation of Hydro Units
Now, that the decision is taken whether a unit is used as turbine or pump and whether it is switched on, the
decision of the generation schedule can be prepared. This generation schedule is expressed in terms of
water consumption, the scheduled discharge, and in terms of generation, the power production schedule. In
addition to the electricity output, the unit can be assigned to contribute to regulation services and reserves.
For every reserve class it is assigned to, there is a contribution schedule optimized by HTC. An overview of
these optimized schedules is given in Table 48.

Edition 08.2013
Table 48: Hydro unit’s results
Electric power generation Schedule MW PowerProdSched1

1/2/3/4/5

1/2/3/4/5
The optimization of above schedules is subject to hydrological and electrical constraints. They are considered
for the time a unit is scheduled for operation in either turbine or pump mode. A hydrological constraint is the
discharge of water, which has to be within a given operation range, the minimum and maximum discharge.
Electrical constraints are given by the physical limits of turbine/generator or pump/motor, like minimum
capacity and maximum capacity. Time dependent capacity limits resulting from, e.g. maintenance work, may
be defined using the schedules for minimum and maximum derated capacity. An overview of these direct
generation limits is given in Table 49. The operating range is further reduced due to the regulating ranges and
additional limits when operating primary and/or secondary regulation, as described in chapter 3.6.7. The
regulation range in case of regulation activities follows the same characteristic as depicted in Error!
Reference source not found. for thermal units.
Reserve contributions of hydro units (turbines, pumps, pump turbines) are described in chapter 3.5.2
“Regulation Services and Reserves“.
Short circuit operation for turbination/pumping can be allowed or disabled for all reservoirs via a tuning
parameter (global switch) or via a particular UnitRestrictionGroup (cf chapter 3.9.4).
Table 49: Hydro unit’s constraints
Minimum discharge Schedule m3/s DischargeMinSched
Maximum discharge Schedule m3/s DischargeMaxSched
Minimum capacity Value MW MinimumMW
Maximum capacity Value MW MaximumMW
Minimum derated capacity Schedule MW GenUnitDerMinSched
Maximum derated capacity Schedule MW GenUnitDerMaxSched
The Attribute AllowPartialPumping (Boolean, default = FALSE/FullPumping) defines if partial pumping (details
below) is allowed. This feature is effective only for HGUs of type “pump” (not for pump turbines, and not for
turbines, of course).

Edition 08.2013
Table 50: Pump power modulation
Selector to activate partial pumping Value Checkbox AllowPartialPumping

(Boolean)
When the option “partial pumping” is selected, the static and dynamic Pmin and Pmax (MinimumMW,
MaximumMW, GenUnitDerMinSched, GenUnitDerMaxSched) will be used for all hours in a single
commitment period instead of the PumpMW value.
The static and dynamic pumping Pmin cannot be “0” (at least 1 MW) if the unit is available. If the unit is
unavailable, the dynamic value can be put at 0 MW
The start-up costs and the min up/down times (cf. Techspec 3.8.3/4) are only applied to each pump
commitment period (thus not when HTC merely modulates the pump power). No ramp constraints are
applied.
3.7.6 Simultaneous operation of turbines and pumps
UnitRestrictionGroup.AllowSimPumpTurb (CheckBox, default: FALSE) allows to control the simultaneous

operation of pumps and turbines for HGUs that belong to this UnitRestrictionGroup.
If UnitRestrictionGroup.AllowSimPumpTurb = FALSE, simultaneous operation of any pump/turb pair in this
URG is not allowed.
If UnitRestrictionGroup.AllowSimPumpTurb = TRUE, simultaneous operation is allowed (unless it is
prohibited by another similar constraint, of course).
Table 51: Simultaneous pumping and turbining
Selector for simultaneous pumping Value Checkbox AllowSimPumpTurb

and turbining (Boolean)
Note: This is a hard constraint and can – in certain cases – cause the violation of constraints like target levels,
demand or reserve requirements.
3.7.7 Hydro Plants
HydroPlants are groups of hydro units. For these groups, a sum over the individual units’ schedules gives the
schedule for the power plant, summarized in Table 52. As described with the hydro topology in chapter 3.3.3,
a hydro unit always has an upstream Reservoir and may have a downstream Reservoir. The nature of these
Reservoirs and the hydro units’ specifications make up the type of the hydro power plant: in case the
upstream Reservoir is parameterized to have constant level, the power plant is a run-of-river plant. If there is
significant storage capacity of the upstream Reservoir, then the power plant is a Reservoir plant.

Edition 08.2013
Table 52: Hydro power plants’ results
Plant generation Schedule MW PowerProdSched1

1/2/3/4/5

1/2/3/4/5
Operation & maintenance costs Schedule €/h CostOMSched1
3.7.8 Hydro Valleys
HydroValleys are groups of hydro plants. For these groups, a sum over the individual plants’ results gives the
results of the hydro valley, as summarized in Table 53.
Table 53: Hydro valleys’ results
Valley generation Schedule MW PowerProdSched1

1/2/3/4/5

1/2/3/4/5
Operation & maintenance costs Schedule €/h CostOMSched1

Edition 08.2013
3.8 Market Features
3.8 Market Features

Besides the production assets as described above, the markets and their specific rules are another major
focus of optimization. The following chapters are dedicated to describe the features that HTC offers to
maximize the revenue on the markets.
3.8.1 Electricity Contracts
Optimizable electricity contracts (EnergyContracts) are used to model bilateral contracts. The user can add
contracts to areas (cf. chapter 3.5.1). They are characterized by a name, begin and end time, the type and
the contract specific parameters.
The costs are determined from two price schedules, which give the fix hourly prices the volume prices (for
energy or reserve).
Furthermore the user may set contracts to Forced, if he wants to exclude them from optimization (i.e. the
volume schedule is taken as fixed).
HTC supports the following contract Types:
 Fix: the purchase/sale volume is given as fixed power schedule and HTC determines whether the
contract shall be taken or not
 Flex: the purchase/sale volume is determined by HTC within limits
 Block: the purchase/sale volume is determined by HTC within limits without variation of the volume over
time
 For all Types of EnergyContracts the Direction determines:
 Sell: Energy / reserve is sold with this contract
 Buy: Energy / reserve is bought with this contract
The Product determines if the sold/purchased volume is energy (default value for all EnergyContracts) or
reserve of one of the available (5) reserve classes, and the attribute Quality determines if a given
EnergyContract (Product RsrvCl<N>) delivers reserve only in one direction (up/down) or symmetrically in
both directions
For Flex contracts, several parameters define or limit the contract. Most important are BeginTime and
EndTime which determine the validity of the contract.
With the SwitchingPolicy the user can decide whether HTC is allowed to switch On and Off the
EnergyContract (put the power to zero) and whether this is allowed at any time or only at full hours. The
switching may be subject to a MinimumDuration time (minimum up time of the power). Additionally, the user
can define a must interval, where the power must be above minimum limit, and the switching On must be
before this interval and switching Off after this interval. The volume itself is optimized within given minimum
and maximum power limits. Optionally, energy limits can restrict the total volume of the contract. Optionally,
energy limits can restrict the total volume of the contract, if its Product is ‘Energy’. If the planning horizon is
not fully contained in the validity period of the contract, min. and max. energy are scaled down proportionally.
Block contracts are similar to Flex contracts, but they can be scheduled at only one constant value
(flat/rectangular profile) for each single activation.
Table 54: Contract results
Scheduled volume Schedule MW PowerSched1

Edition 08.2013
3.8 Market Features
Scheduled revenue (costs are Schedule €/h RevenueSched1

negative)
Table 55: Contract parameters
Contract begin Time YYYYMMDDhhmm BeginTime
Contract end Time YYYYMMDDhhmm EndTime
Contract type Value { Fix Type

Flex
Block}
Contract direction Value {Sell, Direction

Buy}
Contract state Value {Optional, State

Forced}
Contract switching policy Value {NotAllowed, SwitchingPolicy

AllowedAtFullHour,
Allowed}
Contract minimum duration Value min MinimumDuration
Contract must begin Time Date/Time MustBeginTime
Contract must end Time Date/Time MustEndTime
Contract fix price per hour Schedule €/h FixPriceSched
Contract energy price Schedule €/MWh EnergyPriceSched
Contract minimum volume Schedule MW ContractMinSched
Contract maximum volume Schedule MW ContractMaxSched
Contract minimum energy Value MWh ContractMinEnergy
Contract maximum energy Value MWh ContractMaxEnergy
Contract product Value Energy [Default] Product

RsrvCl1
RsrvCl2
RsrvCl3
RsrvCl4
RsrvCl5

Edition 08.2013
3.8 Market Features
Contract quality Value Symmetric Quality

Up
Down
Contract minimum downtime Value min MinDownTIme
Contract maximum uptime Value min MaxDuration
Some of the above attributes (SwitchingPolicy, MinimumDuration, MustBegin/EndTime, ContractMinSched,

ContractMin/MaxEnergy ) are only relevant for Flex- and/or Block-contracts.
A few more explaining remarks:

State ‘Forced’ overrules all other constraints (within validity period)
many input checks are by-passed, no warnings are written.
SwitchingPolicy ‘NotAllowed’ is similar to the TGU’s availability mode ‘MustRun’
Table 56: Schematic overview of effect of contract parameters Type/State/SwitchingPolicy
Type State Policy Remarks
Fix Forced n/a Vol=Min for all t

Flex
Block
Fix Optional n/a Vol = 0 for all t or Vol = Min for all t
Flex Optional AllowedAtFulHour Vol(t) = 0 or Vol(t) = Min

Allowed switching and ‘must’ constraints apply
Flex Optional NotAllowed Min(t) ≤ Vol(t) ≤ Max(t)
Block Optional AllowedAtFulHour Vol=0 for all t or Min(t) ≤ Vol ≤ Max(t)

Allowed same Vol for all t
Block Optional NotAllowed Min(t) ≤ Vol ≤ Max(t)

same Vol for all t
Fix Forced n/a Vol=Min for all t

Flex
Block
“for all t” means “for all time intervals that are both within the planning horizon and the definition period of the
contract”:
FuelMarkets
A FuelMarket is a possibility to sell and buy fuel of one specific FuelType at a given price (schedule). HTC will
use the spot markets as source or sink of fuel and determine the optimal volume to be put on or taken from
the market. The user can assign FuelStocks (cf. chapter 3.6.7 ) to the spot market, to optimize possible
exports towards the market.

Edition 08.2013
3.8 Market Features
The determining parameter for the optimization is the (expected) price of the fuel on the market. The total flow
to and from the FuelMarket can be limited by maximum schedules. HTC will determine the optimal flow and
the revenue/costs as a result of the export/import to the market.
Table 57: FuelSpotMarket results
Scheduled flow Schedule Dim/h FlowSched1
Scheduled revenue Schedule €/h RevenueSched1
Table 58: FuelSpotMarket parameters
Market price schedule Schedule €/Dim FuelPriceSched
Spread between buy and sell Schedule €/Dim SpreadFuelPriceSched
Maximum flow to market Schedule Dim/h MaxFlowToSched
Maximum flow from market Schedule Dim/h MaxFlowFromSched

Edition 08.2013
3.9 Other Features
3.9 Other Features

Besides the production assets and the markets, other conditions like ecologic, logistic and human resource
conditions influence the optimization and may result in constraints on a group of units. Initial conditions are
relevant for schedules starting in the near future and final conditions are relevant to consider medium and
long term optimization results. The following chapters are dedicated to the description of these features.
3.9.1 Initial Conditions
The correct consideration of ramping limits, minimum up- and downtime, and other limits (as described later
in this chapter) requires data to define the initial conditions of units, reservoirs and other objects of the power
system model.
The user has the possibility to run HTC under three different kinds of initial conditions:
 FromMeasuredValue
 FromSchedule
 FromTarget
Depending on the setting, HTC will use different sources to determine the values for the initial conditions.
FromMeasuredValue
The values used under starting condition ‘FromMeasuredValue’ are taken from single value attributes (which
may be linked from a SCADA system). A typical set of values for calculations that determine the schedules in
the near future for intraday market and/or operation purpose contains the actual generation of the units in
operation and, date and time of their last synchronization or desynchronization, the actual level of hydro and
cogeneration storages and the accumulated consumption of FuelContracts, as summarized in Table 59.
FromSchedule
The values under starting condition ‘FromSchedule’ are obtained from schedules, which usually are
determined by HTC in a previous calculation. This is especially useful for day-ahead scheduling or scheduling
of consecutive planning horizons. These schedules are, for example, the scheduled generation of generating
units (see chapter 3.6.5), the scheduled level of reservoirs (see chapter 3.7.2), the scheduled content in
cogeneration storages (see chapter Error! Reference source not found.) or the scheduled accumulated fuel
consumption of FuelContracts (see chapter 3.6.2), as shown in Table 60. Date and time of last
synchronization and desynchronization are set in a way that they fit to the generation.
FromTarget
The values under starting condition ‘FromTarget’ are obtained from target values, which are regularly used for
the end of the planning horizon, like the target level of hydro reservoirs (see chapter 3.7.2), the target level of
cogeneration storages (see chapter Error! Reference source not found.) and the fuel target of FuelContracts
(see chapter 3.6.2) as shown in Table 61. Start values for fuel, emission and energy limits are derived
proportional. Actual generation of units is assumed to be minimum generation for available units and zero for
not available units. Date and time of last synchronization and desynchronization are set in a way that they fit
to the generation. Primary and secondary regulation is assumed to be off since times longer than the
minimum off-time to allow immediate switch on. This mode is particularly useful for studies of any future
planning horizon.

Edition 08.2013
3.9 Other Features
Table 59: Start conditions for ‘FromMeasuredValue’
Generation of units Value MW, ActivePowerCurrent,

MWth CogenProdCurrent
Last synchronization Value time StartUpDate
Last desynchronization Value time ShutDownDate
Date/Time of last PR On Value time PROnDate
Date/Time of last PR Off Value time PROffDate
Level for hydro reservoirs Value m LevelCurrent
Level for cogeneration storages Value m CogenContentCurrent
Accumulated fuel consumption of Value fuel FuelCurrent

FuelContracts dependent
Amount of fuel in limited period Value fuel CurrentAmount

dependent
Accumulated emission volume of Value kg EmissionCurrent

EmissionRestrictionGroups
Table 60: Start conditions for ‘FromSchedule'
Generation of units Schedule MW PowerProdSched1
Last synchronization Schedule time StartupDateSched1
Last desynchronization Schedule time ShutdownDateSched1
Date/Time of last PR On Schedule time PROnDateSched1
Date/Time of last PR Off Schedule time PROffDateSched1
Level of hydro Reservoirs Schedule m LevelSched1
Content for heat cogeneration Schedule MWhth CogenContentSched1

storages
Accumulated fuel consumption of Schedule fuel AccConsumptionSched1

FuelContracts dependent
Accumulated daily amount of fuel of Schedule fuel AccDailyFuelSched1

FuelRestrictionGroup dependent
Accumulated amount of fuel in limited Schedule fuel AccFuelSched1

period of FuelRestrictionGroup dependent
Content of energy Reservoirs Schedule MWh ContentSched1

Edition 08.2013
3.9 Other Features
Scheduled accumulated emission Schedule kg AccEmissionSched1

volume of EmissionRestrictionGroups
Last time entering primary regulation Value time derived from Rsrv1UpSched1
Last time leaving primary regulation Value time derived from Rsrv1UpSched1
Last time entering secondary Value time derived from Rsrv2UpSched1

regulation
Last time leaving primary regulation Value time derived from Rsrv2UpSched1
Table 61: Start conditions for ‘FromTarget’
Generation of units Schedule MW GenUnitOpSched
Level of hydro reservoirs Schedule m LevelTargetSched
Level for cogeneration storages Schedule m CogenContentTargetSched
Accumulated fuel consumption Schedule fuel FuelTargetSched

dependent
Last synchronization Value time derived from GenUnitOpSched
Last desynchronization Value time derived from GenUnitOpSched
3.9.2 Consecutive Planning
The start conditions FromSchedule are used to split the optimization over the full planning horizon into
multiple optimizations of shorter planning horizon. The resulting schedules of one HTC run give the start
conditions of the subsequent calculation.
HTC provides automatic splitting of the planning horizon: the user specifies a desired approximate maximum
size (in days) of the planning of a single optimization and a desired time of the day [hh:mm] when the split
should occur.
If the desired (total) planning horizon exceeds the specified maximum, the horizon will be split:
 the first "slice" from beginning of the total planning horizon until the first "split time" after reaching the
max. length
 the following slices have the have the specified max. length
 the last slice covers the remaining period until the end of the total planning horizon (but not shorter than
the max. length)
As a final step, a Costing or a Re-Planning calculation is run over the total planning horizon to ensure
consistent results and correct total figures.

Edition 08.2013
3.9 Other Features
02:00-06:00
06:00-06:00
06:00-06:00
06:00-02:00
Costing 02:00-02:00 360h
Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo Tu
Figure 25: Consecutive planning: splitting a 15 day planning horizon
Figure 25 above illustrates how a total planning horizon of 15 days (360 hrs) is split (at 6 am) into shorter
horizons of approx. 4 days each.
The computations of the individual “slices” follow all rules and constraints for HTC runs of the same type, with
the following exceptions:
Initial condition for the “slices” 2, 3 etc. is always ‘FromSchedule’ (based on the result of the previous “slice”)
Reservoir targets are obeyed during the computation of each individual slice, but they are not binding for the
final Re-Planning
3.9.3 Final Conditions / Coupling to Resource Optimization (RO)
The consideration of final conditions allows the user to follow mid term plans as determined by Resource
Optimization or other mid term planning functions. In general two approaches are supported and can be
chosen on an individual object level:
 Final target condition: allows to use results of RO as minimum, maximum or target condition used as a
soft limit in HTC.
 Shadow price: RO is determining shadow prices, which are considered in the objective function of HTC,
but not part of cost determination. The shadow price is a more flexible but “looser” coupling mechanism than
target conditions.
Coupling between HTC and RO is established for the following variables:
 Fuel targets (as described in chapter 3.6.2 and 3.6.3)
 Energy targets of Unit Groups (as described in chapter 3.9.4) and Pumped Storage Plants
 Emission limits (as described in chapter Error! Reference source not found.)
 Hydro Reservoir targets (as described in chapter 3.7.2)
3.9.4 UnitRestrictionGroups with Specific Limitations
In some cases it can be required to force a specific limitation on a group of units. HTC supports the following
group constraints:
 minimum / maximum power production
 minimum / maximum electric energy produced over a defined period

Edition 08.2013
3.9 Other Features
 maximum number of simultaneously starting units

(TGUs simultaneously in preparation phase, cf. chapter 3.6.7)
 simultaneous run of units

(all TGUs in group must be in the same commitment state)
 minimum/maximum number of simultaneously synchronized TGUs
 commitment priority of TGUs
Constraint groups on min/max power production and on min/max electrical energy can also be defined for
HGUs. “Mixed” groups (containing both TGUs and HGUs) are not supported.
For energy limitations outside the HTC planning horizon, the same principles as for fuel limitations are
adopted, i.e. a current value defines the initial value of energy produced and a target schedule (from RO)
defines the desired final conditions. Alternatively, a shadow price can be used for coupling to RO.
The option 'commitment priority' to enforce for a group of (two or more) TGUs a fixed order in which they
have to be committed: i.e. a TGU with lower priority can only be committed if all TGUs with higher priority in
the same group are committed at the same time as well.
Table 62: Unit restriction group results
Scheduled group generation Schedule MW PowerProdSched1
Scheduled energy in period Value MWh Energy
Number of units in preparation phase Schedule 1 StartingSched1
Number of units running in parallel Schedule 1 RunningSched1
Table 63: Unit restriction group parameters
Minimum group generation Schedule MW MinPowerSched
Maximum group generation Schedule MW MaxPowerSched
Maximum number of simultaneous Schedule 1 MaxStartingSched

units starting
Begin of energy period Time Date/Time BeginTime
End of energy period Time Date/Time EndTime
Minimum energy in period Value MWh MinEnergy
Maximum energy in period Value MWh MaxEnergy
Current energy Value MWh CurrentEnergy
Target schedule from RO Schedule MWh TargetEnergySched
Minimum/Maximum number of units Schedule 1 MinSimRunSched,

simultaneously synchronized MaxSimRunSched
Commitment priority (TGU attribute) Value 1 StartupPriority

Edition 08.2013
3.9 Other Features
StartupPriority is an attribute of a ThermalGeneratingUnit; priority 0 (zero) means, the resp. TGU is not part of
the limitation. Each TGU can be part of not more than one commitment priority restriction.
3.9.5 Tuning of the HTC-algorithm
The HTC algorithm performs the solution process in several steps:

1. Rule based verification of data
2. Linear Programming optimization to verify constraints
(if this fails because of infeasibility, slack variables are introduced and used for algorithmic base
verification of data)
3. Mixed Integer Linear Programming optimization to find commitment decisions
4. successive Linear Programming optimization for final dispatch
5. final cost determination
Phases 3 and 4 usually are the most time consuming phases. The computations can be tuned according to
specific customer data sets by the parameters listed in Table 64. Please note that – in order to safely obtain
reproducible results – the time limit should not be used as the only break-off criterion. Variations to this
process can be applied in specific implementations.
However, to allow a compromise between accuracy and computation time, the break criterion "MIP-gap" can
be relaxed with increasing runtime, e.g.
start with criterion of "MIP-gap ≤ 0.2 %" (best accuracy)
if after 500 sec no solution with MIP-gap ≤ 0.2 % found, continue with MIP-gap ≤ 0.5 % (extended accuracy
limit)
if after another 500 sec no solution with MIP-gap ≤ 0 5 % found, continue with MIP-gap ≤ 1 % (last accuracy
limit)
Table 64: Tuning parameters of HTC
Name Type Unit Default
MIP-gap for search 1 (for best accuracy) Value % 0.2
MIP-gap for search 2 (for extended accuracy) Value % 0.5
MIP-gap for search 3 (last accuracy limit) Value % 1.0
Number of integer solutions to break-off Value 1 20
Maximum number of nodes to break-off Value 1 1000000
Maximum time limit of MILP (per search) Value s 500
Maximum iterations in sLP Value 1 20
Start area for sLP Value % 100
Contraction factor for sLP Value 1 0.8

Edition 08.2013
3.9 Other Features
3.9.6 Constraint Priorities, Hard and Soft Constraints
For cases, where there is no feasible solutions that satisfies all technical and all hard constraints (cf. below),
HTC will stop after the Pre-Processing/DataCheck phase and write error messages specifying the problem(s).
No optimization is started and no results are written.
Technical unit constraints are:
 ’Unit Availability’
 ’Generation and Production Limits’
 Fuel Rate limits

 ’Minimum Down-time’
 ’Minimum Up-time’
 ’Limited Ramp Rate’
 ’Startup tables’
Other hard constraints are:
 ‘Area load demand’
 ‘Common steam header balances’
 ‘Water balance in Hydro System or Pumped Storage’
 ‘Combined Cycle Plant constraints’
 ‘Area exchange limits’
 ‘Cogeneration Interchange limits’
In cases, where a feasible solution that satisfies all technical and all hard constraints does exist, the
optimization will be started. If no solution is possible, that fulfills ALL constraints, a relaxed solution will be
determined by HTC, according to a defined priority (high, medium, low). The search for a relaxed solution is
more time-consuming and does not necessarily yield to a practicable solution. Nevertheless it is helpful to find
the source of infeasibility.
If a constraint is relaxed, a full information message is written to the message list and the state of program
signals ’Message’ instead of ’OK’.
The following constraints may be relaxed for cases, when no feasible solution exists:
 Group constraints – high priority

- ’Minimum/Maximum generation limit (type ‘PowerProd’)’
- ’Maximum number of units which can be started up simultaneously (type ‘SimStart’)’
- ’Electrical Energy Constraints (type ‘SecEnergy’)’

- ’Fuel Constraints (type ‘PrimEnergy’)’
- ‘Emission Constraints’
 Reserve constraints (cf. chapter 3.5.2) - medium priority

- ’Required Reserve class 1’

Edition 08.2013
3.9 Other Features
 target conditions for reservoirs – low priority

- ’Cogeneration Storage' (cf. chapter Error! Reference source not found.)
- Hydro / PumpedStorage Reservoir (cf. chapters Error! Reference source not found., 3.7.2)
Furthermore, constraints can be switched off individually (e.g. reserve constraints). By comparing costs of two
runs (unconstrained/constraint calculation) he can determine the costs of the individual constraints.
3.9.7 Cplex infeasibility in RunManager messages
If in the course of the optimization an infeasible LP/MILP problem occurs, the probable cause of the
infeasibility is reported in the MessageList of HTC. If applicable, the message(s) contain the following
information:
Name and Type of the component(s) involved, eg.: “ThermalGeneratingUnit NLEEMS_TH__5EC__5OMNG0”
time/time interval/period where the problem occurs
Variable/constraint/restriction/… that is involvedeg.: “Rsrv2UpRqmtSched”
In the event of an infeasible LP/MILP problem, the log information of the applied LP/MILP solver (*_cplex.log)
will be parsed to identify the “critical” variable or constraint and – if possible – the related objects of the data
model will be indicated.
If an infeasibility cannot be associated with a single data object, the message will simply indicate an “unkown
cause of infeasibility”.
In a majority of practical cases, the cause of an infeasibility can indeed be traced down to one single
object/variable/constraint and usually this information helps to either identify directly a single infeasibility or a
combinatory infeasibility of input data or it gives at least an indication in which part of the system such a
bottleneck could be found.
However, it has to be noted that - due to the complexity of the underlying mathematical model - it cannot be
guaranteed, that the cause of an infeasibility can be traced back to one in object/variable/constraint in all
cases.

Edition 08.2013
4 Appendixes
4.1 Classes
4 Appendixes
The next chapters describe the complete list of classes, their attributes, and values for the enumeration types
used in the jROS-HTC system.
4.1 Classes
Table 65: List of all jROS classesError! Cannot open data source.
4.2 Attributes
4.2.1 Area
Area includes also all attributes from the Error! Reference source not found. see chapter Error! Reference
source not found..
Input Attributes
Table 66: Input Attributes of the Area

Name
Type Dimension Description
LoadAdder1Sched Schedule MW Load Adder 1 Schedule
LoadForecastSched Schedule MW Total demand in the area
PowerInterchgSched Schedule MW Total fixed power contracts in the area
PredefinedGenSched Schedule MW Total generation in area from other resources
PRsymmetryCondition Value EnumBoolean Symmetry condition for primary reserve contribution
Input/Output Attributes
Table 67: Input/Output Attributes of the Area
Output Attributes
Table 68: Output Attributes of the Area

Name
Type Dimension Description
CostContract Value EUR Total costs of optimizable contracts over planning horizon
CostContractSched1 Schedule EUR/h Total costs of optimizable contracts per hour
CostFuelMarket Value EUR Cost/revenue from FuelMarkets over planning horizon

Edition 08.2013
Appendixes
4.2 Attributes
CostFuelMarketSched1 Schedule EUR/h Cost/revenue from FuelMarkets
CostSpotMarket Value EUR Cost revenue from SpotMarkets over planning horizon
CostSpotMarketSched1 Schedule EUR/h Cost/revenue from SpotMarkets
CostSumShadow Value EUR Total costs due to shadow prices
CostSumShadowSched1 Schedule EUR/h Scheduled costs due to shadow prices
DualDemandSched1 Schedule EUR/MWh Duals of demand in each area
DualRsrv1DoSched1 Schedule EUR/MWh Duals of reserve down for class 1
DualRsrv1UpSched1 Schedule EUR/MWh Duals of reserve up for class 1
LoadForecastAvgSched1 Schedule MW Total demand in the area, average over time interval
PowerContractSched1 Schedule MW Total contracted power
PowerSpotMarketSched1 Schedule MW Total power on SpotMarkets
PowerTransferNetSched1 Schedule MW Total net transfer over PowerLines
Rsrv1DoContractSched1 Schedule MW Total net Rsrv 1 Do from EnergyContracts
Rsrv1DoDeliveredSched1 Schedule MW Actually delivered reserve downwards in class 1
Rsrv1DoNetTransferSched1 Schedule MW Total net transfer over PowerLines of Rsrv Do 1
Rsrv1DoRqmtSched1 Schedule MW Total required available reserve for class 1 down
Rsrv1UpContractSched1 Schedule MW Total net Rsrv 1 Up from EnergyContracts
Rsrv1UpDeliveredSched1 Schedule MW Actually delivered reserve upwards in class 1
Rsrv1UpNetTransferSched1 Schedule MW Total net transfer over PowerLines of Rsrv Up 1
Rsrv1UpRqmtSched1 Schedule MW Total required available reserve for class 1 up

Edition 08.2013
Appendixes
4.2 Attributes
4.2.2 Channel
Input Attributes
Table 69: Input Attributes of the Channel
Name Type Dimension Description
DischargeLevelCurve3D 3DCurve m, m3/s Level of Channel versus flow in Channel level

discharge level of downstream Reservoir or
Channel (optional)
DischargeMax Value m3/s Maximum discharge
DischargeMaxSched Schedule m3/s Maximum discharge

Edition 08.2013
Appendixes
4.2 Attributes
DischargeMin Value m3/s Minimum discharge
DischargeMinSched Schedule m3/s Minimum discharge
InflowForecastSched Schedule m3/s Natural inflow
LevelMax Value m Maximum level of Channel
LevelMaxSched Schedule m Maximum level of Channel
LevelMin Value m Minimum level of Channel
LevelMinSched Schedule m Minimum level of Channel
WaterRunTimeDelay Value min Water run time delay
Table 70: Input/Output Attributes of the Channel
Output Attributes
Table 71: Output Attributes of the Channel
DischargeSched1 Schedule m3/s Discharge
LevelSched1 Schedule m Level
4.2.3 CogenInterchange
Input Attributes
Table 72: Input Attributes of the CogenInterchange
CogenInterMaxSched Schedule MWth Upper transfer limit from zone P to S
CogenInterMinSched Schedule MWth Lower transfer limit from zone P to S
CogenInterStateSched Schedule EnumCgiState CommonSteamHeader interconnection
Table 73: Input/Output Attributes of the CogenInterchange

Edition 08.2013
Appendixes
4.2 Attributes
Output Attributes
Table 74: Output Attributes of the CogenInterchange
CogenInterSched1 Schedule MWth Scheduled heat interchange from zone to zone
4.2.4 CogenStorage
Input Attributes
Table 75: Input Attributes of the CogenStorage
CogenContentCurrent Value MWhth Initial content of of cogen resrvoir
CogenContentMax Value MWhth Maximum content of CGS (static)
CogenContentMaxSched Schedule MWhth Maximum content of CSR
CogenContentMinSched Schedule MWhth Minimum content of CSR
CogenContentTargetSched Schedule MWhth Target content of CSR
CogenLoadMaxSched Schedule MWth Maximum Scheduled heat loading of CGS
CogenUnloadMaxSched Schedule MWth Maximum Scheduled heat unloading of CGS
Table 76: Input/Output Attributes of the CogenStorage
Output Attributes
Table 77: Output Attributes of the CogenStorage
CogenContentSched1 Schedule MWhth Scheduled heat content of CGS
CogenProdSched1 Schedule MWth Scheduled heat loading /unloading of CGS
4.2.5 CogenZone
Input Attributes
Table 78: Input Attributes of the CogenZone

Edition 08.2013
Appendixes
4.2 Attributes
CogenForecastSched Schedule MWth Forecasted heat demand per zone
Table 79: Input/Output Attributes of the CogenZone
Output Attributes
Table 80: Output Attributes of the CogenZone
CogenInterNetSched1 Schedule MWth Scheduled total net interchange in zone
CogenProdSched1 Schedule MWth Scheduled heat production in zone
DualCogenSched1 Schedule EUR/MWhth Dual value of forecast constraint in zone
StorageProdSched1 Schedule MWth Scheduled heat out of CGS in zone
4.2.6 CombinedCyclePlant
Input Attributes
Table 81: Input Attributes of the CombinedCyclePlant
CCPOpSched Schedule EnumAvailabilityHGU Availability
DownTimeMin Value min Minimum downtime
ShutdownDate Value EnumDateTime Last desynchronization
StartupDate Value EnumDateTime Last synchronization
TransitionTable TransitionTable Transition table: FromTGU or Off,

ToTGU or Off , Allowed, Costs
UpTimeMin Value min Minimum uptime
Table 82: Input/Output Attributes of the CombinedCyclePlant
ShutdownDateSched1 Schedule EnumDateTime Last desynchronization
StartupDateSched1 Schedule EnumDateTime Last synchronization

Edition 08.2013
Appendixes
4.2 Attributes
Output Attributes
Table 83: Output Attributes of the CombinedCyclePlant
CCPModeSched1 Schedule 1 Scheduled plant configuration
4.2.7 CommonSteamHeader
Input Attributes
Table 84: Input Attributes of the CommonSteamHeader
Table 85: Input/Output Attributes of the CommonSteamHeader
Output Attributes
Table 86: Output Attributes of the CommonSteamHeader
CogenBalanceVioSched1 Schedule MWth Scheduled imbalance on CSH
4.2.8 EmissionRestrictionGroup
Input Attributes
Table 87: Input Attributes of the EmissionRestrictionGroup
AccMaxEmissionSched Schedule kg Accumulated maximum emission

volume
EmissionCurrent Value kg Accumulated emission volume of

EmissionGroups
EmissionFactorTable EmissionFactorTable Unit-specific emission factor for fuel

X
EmissionMaxSched Schedule kg/h Maximum emission flow
EmissionModel Value EnumEmissionModel Specify the emission model
PriceEmissionSched Schedule EUR/kg Price for emission certificate
Table 88: Input/Output Attributes of the EmissionRestrictionGroup

Edition 08.2013
Appendixes
4.2 Attributes
Output Attributes
Table 89: Output Attributes of the EmissionRestrictionGroup
AccEmissionSched1 Schedule kg Scheduled accumulated emission volume

of EmissionGroups
CostEmission Value EUR Total Emission costs
CostEmissionSched1 Schedule EUR/h Scheduled emission costs
EmissionSched1 Schedule kg/h Scheduled group emission flow
4.2.9 EnergyContract
Input Attributes
Table 90: Input Attributes of the EnergyContract
BeginTime Value time Contract begin
ContractDirection Value EnumContractDirection Direction of contract
ContractMaxEnergy Value MWh Contract maximum energy
ContractMaxPower Value MW Contract maximum power
ContractMaxSched Schedule MW Contract maximum power
ContractMinEnergy Value MWh Contract minimum energy
ContractMinPower Value MW Contract minimum power
ContractMinSched Schedule MW Contract minimum power
ContractProduct Value EnumContractProduct Contract product
ContractQuality Value EnumContractQuality Contract quality
ContractState Value EnumContractState Optimization state of contract
ContractType Value EnumContractType Type of contract
EndTime Value time Contract end
FixPriceSched Schedule EUR/h Contract fix price per hour
MaxDuration Value min Contract maximum uptime - duration
MinDownTime Value min Contract minimum downtime
MinimumDuration Value min Contract minimum duration

Edition 08.2013
Appendixes
4.2 Attributes
MustBeginTime Value time Contract must begin
MustEndTime Value time Contract must end
PriceSched Schedule EUR/MWh Contract price
SwitchingPolicy Value EnumSwitchingPolicy Contract switching policy
Table 91: Input/Output Attributes of the EnergyContract
Output Attributes
Table 92: Output Attributes of the EnergyContract
RevenueSched1 Schedule EUR/h Scheduled revenue
VolumeSched1 Schedule MWh Contract energy volume
4.2.10 FuelContract
Input Attributes
Table 93: Input Attributes of the FuelContract
CurrentAmount Value Dim Current accumulated fuel

consumption of target schedule
FuelCurrent Value Dim Current accumulated fuel

consumption in period of zoned fuel
contracts
FuelMaxSched Schedule Dim/h Maximum fuel flow
FuelMinSched Schedule Dim/h Minimum fuel flow
FuelPricePeriod Value EnumPricePeriod Accounting price period
FuelPriceSched Schedule EUR/Dim Fuel priceSchedule
FuelPriceTable FuelPriceTable Fuel price table: Start, Price,

Consumption
FuelShadowPriceSched Schedule EUR/MWh Fuel shadow price
FuelTargetSched Schedule Dim Fuel targetSchedule
OptimizationType Value EnumOptimizationType Switch for fuel management

Edition 08.2013
Appendixes
4.2 Attributes
ZonedPricesEnabled Value EnumBoolean Switch to enable zoned FuelPrice

Feature
Table 94: Input/Output Attributes of the FuelContract
Output Attributes
Table 95: Output Attributes of the FuelContract
AccConsumptionSched1 Schedule Dim Accumulated consumption
FuelConsumption Value Dim Consumed fuel
FuelConsumptionSched1 Schedule Dim/h Consumed fuel flow
4.2.11 FuelMarket
Input Attributes
Table 96: Input Attributes of the FuelMarket
FuelPriceSched Schedule EUR/Dim Fuel priceSchedule
FuelSpreadPriceSched Schedule EUR/Dim Spread between buy and sell
MaxFlowFromSched Schedule Dim/h Maximum flow from market
MaxFlowToSched Schedule Dim/h Maximum flow to market
Table 97: Input/Output Attributes of the FuelMarket
Output Attributes
Table 98: Output Attributes of the FuelMarket
FlowSched1 Schedule Dim/h Scheduled flow

Edition 08.2013
Appendixes
4.2 Attributes
4.2.12 FuelRestrictionGroup
Input Attributes
Table 99: Input Attributes of the FuelRestrictionGroup
BeginTime Value time Begin of energy period
CurrentAmount Value Dim Current amount of fuel in limited period
DailyCurrentAmount Value Dim Current amount of fuel for 1st day of planning
horizon
DailyMaxSched Schedule Dim Maximum daily fuel amount
DailyMinSched Schedule Dim Minimum daily fuel amount
EndTime Value time End of energy period
MaxAmount Value Dim Maximum amount in limited period
MaxFlowSched Schedule Dim/h Maximum fuel flow
MinAmount Value Dim Minimum amount in limited period
MinFlowSched Schedule Dim/h Minimum fuel flow
PrimEnergyConstr Value EnumBoolean Limited amount on freely defined period
PrimEnFlowConstr Value EnumBoolean Flow limits
PrimEnPerDayConstr Value EnumBoolean Daily fuel amount limits
Table 100: Input/Output Attributes of the FuelRestrictionGroup
Output Attributes
Table 101: Output Attributes of the FuelRestrictionGroup
AccDailyFuelSched1 Schedule Dim Accumulated daily amount of fuel of

FuelRestrictionGroup
AccFuelSched1 Schedule Dim Accumulated amount of fuel in limited period

of FuelRestrictionGroup
FlowSched1 Schedule Dim/h Scheduled flow

Edition 08.2013
Appendixes
4.2 Attributes
4.2.13 FuelStock
Input Attributes
Table 102: Input Attributes of the FuelStock
Table 103: Input/Output Attributes of the FuelStock
Output Attributes
Table 104: Output Attributes of the FuelStock
4.2.14 FuelType
Input Attributes
Table 105: Input Attributes of the FuelType
EmissionFactor Value kg/Dim CO2 emission factor
FuelHeatContent Value GJ/Dim CalorificValue
Table 106: Input/Output Attributes of the FuelType
Output Attributes
Table 107: Output Attributes of the FuelType
4.2.15 HydroGeneratingUnit
Input Attributes
Table 108: Input Attributes of the HydroGeneratingUnit
AllowPartialPumping Value 1 Selector to activate partial / continues

pumping
DeltaMaxPRSched Schedule MW Upper generation delta limit for

primary regulation
DeltaMinPRSched Schedule MW Lower generation delta limit for

primary regulation
DischargeMax Value m3/s Maximum flow rate

Edition 08.2013
Appendixes
4.2 Attributes
DischargeMaxSched Schedule m3/s Maximum flow rate
DischargeMin Value m3/s Minimum flow rate
DischargeMinSched Schedule m3/s Minimum flow rate
DownTimeMin Value min Minimum downtime between desync

and sync
EffiDischargeCurve3D 3DCurve m3/s, 1, m Efficiency curve (discharge,

efficiency, head)
GeneratingUnitTypeHGU Value EnumGenerationTypeHGU Type of hydro unit
GenUnitDerMaxSched Schedule MW Maximum derated capacity
GenUnitDerMinSched Schedule MW Minimum derated capacity
GenUnitOMFactPumpSched Schedule EUR/MWh Specific additional operation cost for

pumping
GenUnitOMFactSched Schedule EUR/MWh Specific additional operation cost
GenUnitOpSched Schedule EnumAvailability Availability
LevelReference Value m Reference level (= -1... downstream)
MaximumMW Value MW Maximum capacity
MinimumMW Value MW Minimum capacity
PPumpMin Value MW PumpTurbine - Minimum pump

power
PRDownTimeMin Value min Primary regulation minimum

downtime
PrimaryDoMWSched Schedule MW Fixed reserve contribution

downwards
PrimaryUpMWSched Schedule MW Fixed reserve contribution upwards
PROffDate Value EnumDateTime Last time of switch off primary

regulation
PROnDate Value EnumDateTime Last time of switch on primary

regulation
PRUpTimeMin Value min Primary regulation minimum uptime
PumpEfficiencyHeadCurve2D 2DCurve m, 1 Pump Efficiency curve (head,

efficiency)
PumpMW Value MW PumpTurbine - Maximum pump

power
RampRateDown Value MW/min Maximum ramp down for electricity

output

Edition 08.2013
Appendixes
4.2 Attributes
RampRateUp Value MW/min Maximum ramp up for electricity

output
Rsrv1DoMax Value MW Maximum reserve contribution

downwards for class 1
Rsrv1Mechanism Value EnumRsrvModule Reserve mechanism for class 1
Rsrv1UpMax Value MW Maximum reserve contribution

upwards for class 1


upwards for class 2


upwards for class 3


upwards for class 4


upwards for class 5
SRcurrent Value EnumBoolean Current contribution to SR
SRdoMaxMWSched Schedule MW Maximum downwards contribution to

SR
SRdoMinMWSched Schedule min Minimum downwards contribution to

SR
SRDownTimeMin Value min Secondary regulation minimum

downtime
SROffDate Value EnumDateTime Last time of switch off secondary

regulation

Edition 08.2013
Appendixes
4.2 Attributes
SROnDate Value EnumDateTime Last time of switch on secondary

regulation
SRsymmetryCondition Value EnumBoolean Symmetry condition for SR

contribution
SRupMaxMWSched Schedule min Maximum upwards contribution to SR
SRupMinMWSched Schedule min Minimum upwards contribution to SR
SRUpTimeMin Value min Secondary regulation minimum

uptime
StartupCostPump Value EUR/start Startup costs for pumping
StartupCostTurb Value EUR/start Startup costs for turbination
Table 109: Input/Output Attributes of the HydroGeneratingUnit
CommitmentStateSched0 Schedule EnumCommitment Units commitment master (for Re-Planning)
PowerProdSched0 Schedule MW Fix electric power generation
PrimaryRegSched0 Schedule 1 Master primary regulation (master for Re-

Planning)
PROffDateSched1 Schedule EnumDateTime Last time of switch off primary regulation
PROnDateSched1 Schedule EnumDateTime Last time of switch on primary regulation
SecondaryRegSched0 Schedule 1 Master secondary regulation (master for Re-

Planning)
Output Attributes
Table 110: Output Attributes of the HydroGeneratingUnit
CostMargDoSched1 Schedule EUR/MWh Marginal costs downwards
CostMargUpSched1 Schedule EUR/MWh Marginal costs upwards
CostOM Value EUR Total operation and maintenance cost

Edition 08.2013
Appendixes
4.2 Attributes
CostOMSched1 Schedule EUR/h Operating and maintenance costs
CostSpecPminSched1 Schedule EUR/MWh Specific costs at Pmin
CostSpecSched1 Schedule EUR/MWh Specific costs
CostStartup Value EUR Total startup costs
CostStartupSched1 Schedule EUR/h Scheduled sum of costs
CostSum Value EUR Total sum of costs
CostSumSched1 Schedule EUR/h Scheduled sum of costs
PowerProdSched1 Schedule MW Electric power generation
Rsrv1DoSched1 Schedule MW Regulation capability downwards for class 1
Rsrv1UpSched1 Schedule MW Regulation capability upwards for class 1
4.2.16 HydroPlant
HydroPlant includes also all attributes from the Error! Reference source not found. see chapter Error!
Reference source not found..
Input Attributes
Table 111: Input Attributes of the HydroPlant
Table 112: Input/Output Attributes of the HydroPlant
Output Attributes
Table 113: Output Attributes of the HydroPlant

Edition 08.2013
Appendixes
4.2 Attributes
4.2.17 HydroValley
HydroValley includes also all attributes from the Error! Reference source not found. see chapter Error!
Input Attributes
Table 114: Input Attributes of the HydroValley
Table 115: Input/Output Attributes of the HydroValley
Output Attributes
Table 116: Output Attributes of the HydroValley
4.2.18 MPROFstep
Input Attributes
Table 117: Input Attributes of the MPROFstep
Ddemand Value MW Delta demand for step
MPbuyPriceSched Schedule EUR/MWh Price at which energy can be bought to satisfy

demand profile in MPROF
MPMarkUpSched Schedule EUR/MWh Mark up price
MPROFChangePolicy Value EnumMPSPolicy MPROF step power delta sched change policy
MPsellPriceSched Schedule EUR/MWh Price at which energy can be sold to satisfy

demand profile in MPROF
MPstepActive Value EnumBoolean Activity flag for MPROF step
MPstepType Value EnumMPSStepType Type of MPROF step
Table 118: Input/Output Attributes of the MPROFstep
Output Attributes
Table 119: Output Attributes of the MPROFstep
MPstepSched1 Schedule EUR/MWh Marginal price for extra step

Edition 08.2013
Appendixes
4.2 Attributes
PowerDeltaSched1 Schedule MW Extra generation achieved
4.2.19 PowerLine
Input Attributes
Table 120: Input Attributes of the PowerLine
TransferCapacity Value MW Maximum Power flows to other area
TransferChangePolicy Value EnumPowerLinePolicy Hourly market in qh planning steps
TransferEmergencyMaxSched Schedule MW Maximum Power flows to other area
TransferMaxSched Schedule MW Maximum Power flows to other area
TransferR1DoMaxSched Schedule MW Limited transfer of R1 Down from

one to another area
TransferR1UpMaxSched Schedule MW Limited transfer of R1 Up from one

to another area

one to another area

to another area

one to another area

to another area

one to another area

to another area

one to another area

to another area
Table 121: Input/Output Attributes of the PowerLine

Edition 08.2013
Appendixes
4.2 Attributes
Output Attributes
Table 122: Output Attributes of the PowerLine
PowerTransferSched1 Schedule MW Power flows to other areas
Rsrv1DoTransferSched1 Schedule MW Transfer of reserve for class 1 downwards

regulation to other areas
Rsrv1UpTransferSched1 Schedule MW Transfer of reserve for class 1 upwards regulation

to other areas


to other areas


to other areas


to other areas


to other areas
4.2.20 Reservoir
Input Attributes
Table 123: Input Attributes of the Reservoir
ContentCurrent Value Mm3 Initial energy or water content
ContentDiffToFinalLimit Value Mm3 Allowed deviation from target

volume
ContentLevelCurve3D 3DCurve m, Mm3, m3/s 3D content-level curve: level,

Edition 08.2013
Appendixes
4.2 Attributes
content, discharge (optional)
ContentMax Value Mm3 Maximum energy or water content
ContentMaxSched Schedule Mm3 Maximum energy or water content
ContentMin Value Mm3 Minimum energy or water content
ContentMinRsrvSched Schedule Mm3 Minimum Rsrv energy or water

content
ContentMinSched Schedule Mm3 Minimum energy or water content
ContentTargetSched Schedule Mm3 Energy or water target content
ContentUoM Value EnumReservoirContentUoM Switch for type of reservoir: water

(regular), energy (pumped storage)
InflowForecastSched Schedule m3/s Natural inflow
LevelCurrent Value m Initial Reservoir level
LevelMax Value m Maximum Reservoir level
LevelMaxSched Schedule m Maximum Reservoir level
LevelMin Value m Minimum Reservoir level
LevelMinSched Schedule m Minimum Reservoir level
LevelTargetSched Schedule m Reservoir target level
OptimizationType Value EnumOptimizationType Switch for coupling mode (to

longterm results)
PenaltyCostFinalContent Value EUR/Mm3 Penalty for deviation from target

volume
RsrvClassEnergy Value EnumRsrvClEnergy Reserve Class Energy
RsrvUpHoldingTime Value h RsrvUp Holding Time
ShadowPriceSched Schedule EUR/Mm3 Reservoir shadow price
Table 124: Input/Output Attributes of the Reservoir
Output Attributes
Table 125: Output Attributes of the Reservoir
ContentSched1 Schedule Mm3 Energy or water content

Edition 08.2013
Appendixes
4.2 Attributes
LevelSched1 Schedule m Level of hydro Reservoirs
PumpSched1 Schedule m3/s Pumped water
SpillSched1 Schedule m3/s Spilled water release
TurbSched1 Schedule m3/s Turbinated water release
4.2.21 SAParam
Input Attributes
Table 126: Input Attributes of the SAParam
CalcMode Value EnumHTCCalcMode Calculation mode for HTC planning
ConsecutiveDays Value maximum size in days for the

planning of a single optimization
ConsecutiveSplitTime Value desired time of the day [hh:mm]

when the split should occur
ContractionHys Value 1 Contraction factor sLP hydro
ContractionThermal Value 1 Contraction factor sLP thermal
CplexDefault Value EnumBoolean Use Cplex default parameter
DebugLevel Value debug level (for logging

intermediate results)
IBOfractionMILPMaxMIPGap Value 1 Fraction of MIP gap delta for

intelligent breakoff
IBOfractionMILPTimeLimit Value 1 Fraction of TimeLimit for intelligent

breakoff (>1 means “no IBO”)
MaxIterationSLPHys Value 1 Maximum iterations in sLP hydro
MaxIterationSLPThermal Value 1 Maximum iterations in sLP thermal
MILPMaxMIPGapAbs1 Value EUR Break criterion (tolerance) to limit

MIP search phase 1 found
MILPMaxMIPGapAbs2 Value 1 Break criterion (tolerance) to limit

MILPMaxMIPGapAbs3 Value 1 Break criterion (tolerance) to limit

MILPMaxMIPGapRel1 Value 1 Break criterion (tolerance) to limit


Edition 08.2013
Appendixes
4.2 Attributes

MILPMaxMIPGapSelector Value EnumMIPGapSelector Select which MIP gap should be

applied as break criterion
MILPNrIntegerSol Value 1 Number of integer solutions to

break-off
MILPNrNodes Value 1 Maximum number of nodes to

break-off
MILPTimeLimit Value 1 Maximum time limit of MILP per

search phase
MPROFdemandVariations Value EnumBoolean Consider demand variations in

MPROF runs
MPROFfreezeEC Value EnumBoolean Freeze EnergyContracts in MPROF

runs
MPROFfreezePL Value EnumBoolean Freeze Powerlines power and

reserve exchange in MPROF runs
MPROFfreezeSM Value EnumBoolean Freeze SpotMarkets in MPROF

runs
MPROFon Value EnumBoolean Market Profiles/Sensitivity Analysis

activated
MPROFrampLimit Value EnumMPSRampLimit Obey modified ramp constraints in

MPROF runs
PenBase Value 1 basic penalty
PercentAreaHys Value 1 Percentage factor sLP hydro
PlanHorizAddiHours Value time Hours to be added at end of

planning horizon if
PlanHorizSel=EndOfXYZDays
PlanHorizBeginTime Value time Begin date and time of planning

horizon (input
PlanHorizEndTime Value time End date and time of planning

horizon
RampsRestrictReserves Value EnumBoolean RampUp times ReserveTime

considered in RsrvContribution
SpotMarketsOn Value EnumBoolean SpotMarkets activated
SRchangePenalty Value EUR/Change Penalty for change in SR status
StartCondition Value EnumStartCond Start condition for HTC planning

Edition 08.2013
Appendixes
4.2 Attributes
TimeStep Value min Time step for HTC planning
Table 127: Input/Output Attributes of the SAParam
MIPAbort Value 1 Abort current calculation phase
Output Attributes
Table 128: Output Attributes of the SAParam
CalcDuration Value s Execution time of last HTC run
DisplayBeginTime Value time Begin time in HTC-displays
HTCCalcState Value EnumProgramState HTC activation state
HTCLastCalcTime Value time Last activation time of HTC
MIPBestNodeObjective Value EUR Objective Function of Best Node

solution
MIPElapsedTime Value s MIP elapsed realtime
MIPGapAbs Value EUR Absolute MIP-gap of the best integer

solution found
MIPGapRel Value 1 Relative MIP-gap of the best integer

solution found
MIPObjective Value EUR Objective Function of MILP Integer

solution
PlanHorizBeginTimeConsecutive Value time Begin date and time of planning horizon

for consecutive activation
PlanHorizEndTimeConsecutive Value time End date and time of planning horizon

for consecutive activation
4.2.22 Spillway
Input Attributes
Table 129: Input Attributes of the Spillway

Edition 08.2013
Appendixes
4.2 Attributes
DischargeLevelCurve2D 2DCurve m, m3/s Discharge level curve (level, discharge)
DischargeMax Value m3/s Maximum spilled water
DischargeMaxSched Schedule m3/s Maximum spilled water
DischargeMin Value m3/s Minimum spilled water
DischargeMinSched Schedule m3/s Minimum spilled water
SpillwayType Value EnumSpillwayType Type of spillway
Table 130: Input/Output Attributes of the Spillway
Output Attributes
Table 131: Output Attributes of the Spillway
4.2.23 SpotMarket
Input Attributes
Table 132: Input Attributes of the SpotMarket
ChangePolicy Value EnumSpotPolicy Hourly market in qh planning steps
MarketProduct Value EnumSpotProduct Type of market
MaxBuySched Schedule MW Maximum buy from spot market
MaxSellSched Schedule MW Maximum sell at spot market
RsrvEnergyPriceSched Schedule EUR/MWh Energy price for reserve to be delivered
RsrvFractionSched Schedule 1 Fraction of provided reserve, that will

probably be called
RsrvQuality Value EnumSpotQuality Reserve quality
SpotMarketPriceSched Schedule EUR/MWh Spot market price for electricity
SpreadMarketPriceSched Schedule EUR/MWh Spread between buy and sell
Table 133: Input/Output Attributes of the SpotMarket

Edition 08.2013
Appendixes
4.2 Attributes
Output Attributes
Table 134: Output Attributes of the SpotMarket
SpotMarketEnergySched1 Schedule MW Optimal market volume
4.2.24 System
System includes also all attributes from the Error! Reference source not found. see chapter Error! Reference
source not found..
Input Attributes
Table 135: Input Attributes of the System
Rsrv1Exclusive Value EnumBoolean Switch exclusive for class1
Rsrv1On Value EnumBoolean Switch On/Off for class1
Rsrv1Time Value s Time of activation for class 1
Table 136: Input/Output Attributes of the System

Edition 08.2013
Appendixes
4.2 Attributes
Output Attributes
Table 137: Output Attributes of the System
CostContract Value EUR Total costs of optimizable contracts over

planning horizon
CostContractSched1 Schedule EUR/h Total costs of optimizable contracts per hour
CostEmission Value Total Emission costs
CostEmissionSched1 Schedule Scheduled emission costs
CostFuelMarket Value EUR Cost/revenue from FuelMarkets over planning

horizon
CostFuelMarketSched1 Schedule EUR/h Cost/revenue from FuelMarkets
CostPowerLine Value Total powerline costs
CostPowerLineSched1 Schedule Scheduled powerline costs
CostSpotMarket Value EUR Cost revenue from SpotMarkets over planning

horizon
CostSpotMarketSched1 Schedule EUR/h Cost/revenue from SpotMarkets
CostSumPenalty Value EUR total costs due to penalties
CostSumPenaltySched1 Schedule EUR/h Scheduled costs due to penalties
CostSumShadow Value EUR Total costs due to shadow prices
CostSumShadowSched1 Schedule EUR/h Scheduled costs due to shadow prices
DSTFlagSched1 Schedule 1 Lag to mark DST time (0 in winter, 1 in summer)
HTCTimeStepIndexSched1 Schedule 1 Index of time step in last HTC calculation
HTCUniversalTimeSched1 Schedule 1 UniversalTime (HTC internal time stamp)
PowerContractSched1 Schedule MW Total contracted power
PowerSpotMarketSched1 Schedule MW Total power on SpotMarkets

Edition 08.2013
Appendixes
4.2 Attributes
4.2.25 ThermalGeneratingUnit
Input Attributes
Table 138: Input Attributes of the ThermalGeneratingUnit
ActivePowerCurrent Value MW Initial generation of unit
CogenProdCurrent Value MWth Initial cogen production

of unit
CogenProdMax Value MWth Max cogen production

of unit
CogenProdMaxSched Schedule MWth Max cogen production

of unit
CogenProdMin Value MWth Min cogen production of

unit
CogenProdMinSched Schedule MWth Min cogen production of

unit
CommitmentPriority Value 1 Commitment or

decommitment priority
of TGUs in a unit group
DeltaMaxPRSched Schedule MW Upper generation delta

limit for primary
regulation
DeltaMinPRSched Schedule MW Lower generation delta

limit for primary
regulation
DownTimeMin Value min Minimum downtime from

desync to sync
EmissionFactorOper Value kg/h Operating hours related

emission factor
EmissionFactorPower Value kg/MWh Power related emission

factor

Edition 08.2013
Appendixes
4.2 Attributes
ForbiddenRangeEnabled Value EnumBoolean orbidden range enabled

for the machine
ForbiddenRangeLowerMW Value MW Forbidden range lower

MW-value.
ForbiddenRangeUpperMW Value MW Forbidden range upper

MW-value.
Fuel1Id Value FuelStock Used for FuelStock

selection of the Unit
Fuel1MaxRateSched Schedule 1 Maximum rate of fuel 1
Fuel1MinRateSched Schedule 1 Minimum rate of fuel 1
Fuel1PriceAdder Value EUR/Dim Fuel price adder of fuel

1


2


3


4


5

Edition 08.2013
Appendixes
4.2 Attributes
FuelConsPowerTable FuelConsPowerTabl Fuel consumption table:

e gen Pel, consumed fuel
1, consumed fuel 2,
consumed fuel 3,
consumed fuel 4,
consumed fuel 5, prod
heat/steam Pth
FuelMixingType Value EnumFuelMix Selector for fuel mix

model
FuelSUId Value FuelStock Used for Startup of the

Unit
FuelSUPriceAdder Value EUR/Dim Fuel price adder of

startup fuel
GeneratingUnitTypeTGU Value EnumGenerationTypeTG Unit type: _HRSG heat

U recovery steam
generator _SF
supplementary fire _BP
bypass
GenUnitDerMaxSched Schedule MW Maximum derated

capacity
GenUnitDerMinSched Schedule MW Minimum derated

capacity
GenUnitFixOMFactSched Schedule EUR/h Fixed operation OM cost

factor (option)
GenUnitOMFactSched Schedule EUR/MWh Specific additional

operation cost
GenUnitOpSched Schedule EnumAvailability Availability
GenUnitOpSchedHRSGSF Schedule EnumAvailHRSGSF Availability for

HRSG_SF
MaxCrossingsPerDay Value 1 Max number of

crossings per day
MaxDeSyncShiftBackward Value min MaximumTime shift

backward for de-sync.
MaxDeSyncShiftForward Value min MaximumTime shift

forward for de-sync.
MaximumMW Value MW Maximum capacity
MaximumMWPrimarySched Schedule MW Upper generation limit

reduced
MaxSyncShiftBackward Value min MaximumTime shift

Edition 08.2013
Appendixes
4.2 Attributes
backward for sync.
MaxSyncShiftForward Value min MaximumTime shift

forward for sync.
MinimumMW Value MW Minimum capacity
MinimumMWPrimarySched Schedule MW Lower generation limit

increased
PRchangeDate Value EnumDateTime last date/time of primary

regulation change
PRcurrent Value MW Current contribution to

Primary regulation
PRdoMaxMWSched Schedule MW Maximum reserve

contribution downwards
PRdoMinMWSched Schedule MW Minimum reserve

PRDownTimeMin Value min Primary regulation

minimum downtime
PrimaryEnergyPowerCurve3D 3DCurve MW, GJ/h, MWth 3 dimensional curve -

generated Pel -
consumed fuel/steam Pi
-nproduced heat/steam
Pth
PRMinDuration Value min Minimum duration for

Primary Reserve
contribution
PRMinDurationOn Value EnumBoolean Selector for activation of

Primary Reserve
MinDuration
PROffDate Value EnumDateTime Last time of switch off

primary regulation
PROnDate Value EnumDateTime Last time of switch on

primary regulation
PRupMaxMWSched Schedule MW Maximum reserve

contribution upwards
PRupMinMWSched Schedule MW Minimum reserve

contribution upwards
PRUpTimeMin Value min Primary regulation

minimum uptime
RampRateCogenDown Value MWth/min Maximum ramp down

for thermal output

Edition 08.2013
Appendixes
4.2 Attributes
RampRateCogenUp Value MWth/min Maximum ramp up for

thermal output
RampRateDown Value MW/min Maximum ramp down

for electricity output
RampRateDownSched Schedule MW/min Maximum ramp down
RampRateUp Value MW/min Maximum ramp up for

electricity output
RampRateUpSched Schedule MW/min Maximum ramp up
RegimeTable RegimeTable Regime table: gen Pel,

max Ramp upwards,
max Ramp downwards,
additional OM costs
Rsrv1DoMax Value MW Maximum reserve

for class 1
Rsrv1Mechanism Value EnumRsrvModule Reserve mechanism for

class 1
Rsrv1UpMax Value MW Maximum reserve

contribution upwards for
class 1

for class 2

class 2

class 2

for class 3

class 3

class 3

for class 4

Edition 08.2013
Appendixes
4.2 Attributes

class 4

class 4

for class 5

class 5

class 5
ShutdownPowerCurve2D 2DCurve h, MW Shutdown power

curvetime after initiating
shutdownupper limit on
produced Pel or Pth
SRcurrent Value EnumBoolean Current contribution to

SR
SRdoMaxMWSched Schedule MW Maximum downwards

contribution to SR
SRdoMinMWSched Schedule min Minimum downwards

contribution to SR
SRDownTimeMin Value min Secondary regulation

minimum downtime
SROffDate Value EnumDateTime Last time of switch off

SR
SROnDate Value EnumDateTime Last time of switch on

SR
SRsymmetryCondition Value EnumBoolean Symmetry condition for

SR contribution
SRupMaxMWSched Schedule min Maximum upwards

contribution to SR
SRupMinMWSched Schedule min Minimum upwards

contribution to SR
SRUpTimeMin Value min Secondary regulation

minimum uptime
StartupCostAddition Value EUR Additional start-up costs

Edition 08.2013
Appendixes
4.2 Attributes
StartupCostShadow Value EUR Shadow costs for start-

up are penalties to
reduce the number of
starts.
StartupHeatConsumptionCurve2 2DCurve h, GJ Start-up heat

D consumptiontime from
last de-
synchronizationaddition
al heat required for
start-up
StartupPowerCurve3D 3DCurve h, MW, h Start-up power curve -

time after initiating start-
up -upper limit on
produced Pel or Pth -
downtime before
synchronization
StartupPowerCurveSel Value EnumSUPsel Start-up power curve

selection
StartupTable StartupTable Startup table: Time, Pel,

Pin, Pth, Downtime
SwitchRegimes Value EnumSwitchRegimes Selector for regime
Table 139: Input/Output Attributes of the ThermalGeneratingUnit
CommitmentStateSched0 Schedule EnumCommitment Units commitment master (for Re-Planning)
PowerProdSched0 Schedule MW Fix electric power generation
PRchangeDateSched1 Schedule EnumDateTime last time of primary regulation change
PrimaryRegSched0 Schedule 1 Master primary regulation (master for Re-

Planning)
PROffDateSched1 Schedule EnumDateTime Last time of switch off primary regulation
PROnDateSched1 Schedule EnumDateTime Last time of switch on primary regulation
SecondaryRegSched0 Schedule 1 Master secondary regulation (master for Re-

Planning)

Edition 08.2013
Appendixes
4.2 Attributes
Output Attributes
Table 140: Output Attributes of the ThermalGeneratingUnit
CogenProdSched1 Schedule MWth Thermal power generation
CommitmentStateSched1 Schedule EnumCommitment Units commitment
CostFuel Value EUR Total fuel costs
CostFuelSched1 Schedule EUR/h Fuel costs
CostMargDoSched1 Schedule EUR/MWh Marginal costs downwards
CostMargUpSched1 Schedule EUR/MWh Marginal costs upwards
CostOM Value EUR Total operation and maintenance cost
CostOMSched1 Schedule EUR/h Operating and maintenance costs
CostSpecPminSched1 Schedule EUR/MWh Specific costs at Pmin
CostSpecSched1 Schedule EUR/MWh Specific costs
CostStartup Value EUR Total start-up costs
CostStartupSched1 Schedule EUR/h Scheduled startup costs
Fuel1ConsumptionSched1 Schedule GJ/h Consumption of fuel 1
FuelSUConsumptionSched1 Schedule GJ/h Consumption of startup fuel
GenUnitRampSched1 Schedule MW/min Generation unit ramping

Edition 08.2013
Appendixes
4.2 Attributes
4.2.26 ThermalPlant
ThermalPlant includes also all attributes from the Error! Reference source not found. see chapter Error!
Input Attributes
Table 141: Input Attributes of the ThermalPlant
PlantType Value EnumPlantType Type of ThermalPlant, relevant for topological associations
Table 142: Input/Output Attributes of the ThermalPlant
Output Attributes
Table 143: Output Attributes of the ThermalPlant
4.2.27 UnitRestrictionGroup
UnitRestrictionGroup is a pseudo class for general attributes used in Error! Reference source not found.,
Error! Reference source not found., Error! Reference source not found., Error! Reference source not found. and
Error! Reference source not found. classes.
Input Attributes
Table 144: Input Attributes of the UnitRestrictionGroup
AllowSimPumpTurb Value EnumBoolean Selector to allow simultaneous pumping and

turbining

Edition 08.2013
Appendixes
4.2 Attributes
BeginTime Value Date/Time Begin time of limited period
CommitPrioConstr Value EnumBoolean Commitment priority of units
CurrentEnergy Value MWh Current energy in period
EndTime Value Date/Time End time of limited period
MaxEnergy Value MWh Maximum energy in period
MaxPowerSched Schedule MW Maximum group generation
MaxSimRunSched Schedule 1 Maximum number of units simult. synchronized
MaxStartingSched Schedule 1 Maximum number of simultaneous units starting
MinEnergy Value MWh Minimum energy in period
MinPowerSched Schedule MW Minimum group generation
MinSimRunSched Schedule 1 Minimum number of units simult. synchronized
PowerProdConstr Value EnumBoolean Minimum / maximum power production
SecEnergyPeriodConstr Value EnumBoolean Minimum / maximum electric energy produced over

a defined period
SimRunConstr Value EnumBoolean Minimum / maximum number of simultaneously

synchronized units
SimStartConstr Value EnumBoolean Maximum number of simultaneously starting units
SimSyncRunConstr Value EnumBoolean Synchronized run of units (all in same commitment

state)
TargetEnergySched Schedule MWh Target schedule from RO
Table 145: Input/Output Attributes of the UnitRestrictionGroup
Output Attributes
Table 146: Output Attributes of the UnitRestrictionGroup
Energy Value MWh Scheduled energy in period
RunningSched1 Schedule 1 Number of units synchronized
StartingSched1 Schedule 1 Number of units in preparation phase

Edition 08.2013
Appendixes
4.3 Enumerations
4.3 Enumerations
Table 147: List of all jROS Enumeration Types
Name
EnumAvailability
EnumAvailabilityHGU
EnumAvailHRSGSF
EnumBoolean
EnumCgiState
EnumCommitment
EnumConsecDays
EnumContractDirection
EnumContractProduct
EnumContractQuality
EnumContractState
EnumContractType
EnumDate
EnumDateTime
EnumDateTimeSec
EnumEmiCertTradeModel
EnumEmissionModel
EnumFuelMix
EnumFuelMode
EnumFuelSelector
EnumGenerationType
EnumGenerationTypeHGU
EnumGenerationTypeTGU
EnumHTCCalcMode
EnumMIPGapSelector
EnumMPSPolicy
EnumMPSRampLimit
EnumMPSStepType
EnumOptimizationType

Edition 08.2013
Appendixes
4.3 Enumerations
EnumPlanHoriz
EnumPlantType
EnumPowerLinePolicy
EnumPowerLineVolume
EnumPricePeriod
EnumProgramState
EnumReservoirContentUoM
EnumRsrvClEnergy
EnumRsrvCont
EnumRsrvModule
EnumSpillwayType
EnumSpotPolicy
EnumSpotProduct
EnumSpotQuality
EnumStartCond
EnumSUPsel
EnumSwitch
EnumSwitchConstraint
EnumSwitchingPolicy
EnumSwitchRegimes
4.3.1 EnumAvailability
Table 148: Enumeration Type EnumAvailability Values
Text Value
NotAvailable 1
Available 2
FixP 3
MustOn 4
FixPrsrv 5
MustOnPR 20
MustOnSR 21

Edition 08.2013
Appendixes
4.3 Enumerations
MustOnPRSR 22
FixPPR 23
FixPSR 24
FixPPRSR 25
MustOff 30
IntendedOn 31
4.3.2 EnumAvailabilityHGU
Table 149: Enumeration Type EnumAvailabilityHGU Values
Text Value
NotAvailable 1
Available 2
MustOn 4
4.3.3 EnumAvailHRSGSF
Table 150: Enumeration Type EnumAvailHRSGSF Values
Text Value
OpenCycle 0
ClosedCycle 1
ClosedCycleSF 2
4.3.4 EnumBoolean
Table 151: Enumeration Type EnumBoolean Values
Text Value
FALSE 0
TRUE 1

Edition 08.2013
Appendixes
4.3 Enumerations
4.3.5 EnumCgiState
Table 152: Enumeration Type EnumCgiState Values
Text Value
Open 0
Closed 1
4.3.6 EnumCommitment
Table 153: Enumeration Type EnumCommitment Values
Text Value
Invalid -1
Off 0
On 1
StartPrepCold 2
StartPrepWarm 3
StartPrepHot 4
StartCold 5
StartWarm 6
StartHot 7
StartRestCold 8
StartRestWarm 9
StartRestHot 10
StopPrepare 11
Stop 12
4.3.7 EnumContractDirection
Table 154: Enumeration Type EnumContractDirection Values
Text Value
Purchase 0
Sale 1

Edition 08.2013
Appendixes
4.3 Enumerations
4.3.8 EnumContractProduct
Table 155: Enumeration Type EnumContractProduct Values
Text Value
Energy 0
R1 1
R2 2
R3 3
R4 4
R5 5
4.3.9 EnumContractQuality
Table 156: Enumeration Type EnumContractQuality Values
Text Value
Sym 0
Up 1
Down 2
4.3.10 EnumContractState
Table 157: Enumeration Type EnumContractState Values
Text Value
Optional 0
Forced 1
4.3.11 EnumContractType
Table 158: Enumeration Type EnumContractType Values
Text Value
Fix 10
Flex 11
Block 12

Edition 08.2013
Appendixes
4.3 Enumerations
4.3.12 EnumDate
Table 159: Enumeration Type EnumDate Values
Text Value
Date 0
4.3.13 EnumDateTime
Table 160: Enumeration Type EnumDateTime Values
Text Value
DateTime 0
4.3.14 EnumDateTimeSec
Table 161: Enumeration Type EnumDateTimeSec Values
Text Value
DateTimeSec 0
4.3.15 EnumErgModelType
Table 162: Enumeration Type EnumErgModelType Values
4.3.16 EnumFuelMix
Table 163: Enumeration Type EnumFuelMix Values
Text Value
UsePEP 0
UseFCP 1
4.3.17 EnumFuelMode
Table 164: Enumeration Type EnumFuelMode Values
Text Value
BaseOnly 1
FixedRate 2
OptimRate 3

Edition 08.2013
Appendixes
4.3 Enumerations
BaseTopping 4
4.3.18 EnumFuelSelector
Table 165: Enumeration Type EnumFuelSelector Values
Text Value
NoFuel 0
Fuel1 1
Fuel2 2
Fuel3 3
Fuel4 4
Fuel5 5
4.3.19 EnumGenerationType
Table 166: Enumeration Type EnumGenerationType Values
Text Value
CombustionUnit 0
HydroPump 1
HydroPumpTurbine 2
HydroTurbine 3
CombustionUnit_HRSG 4
CombustionUnit_HRSG_SF 5
CombustionUnit_HRSG_BP 6
CombustionUnit_HRSG_SF_BP 7
SteamUnit 8
CombustionBoiler 9
SteamTurbine 10
SteamTurbineExtraction 11
SteamTurbineBackpressure 12
Reducer 13
Distiller 14
SteamDump 18

Edition 08.2013
Appendixes
4.3 Enumerations
4.3.20 EnumGenerationTypeHGU
Table 167: Enumeration Type EnumGenerationTypeHGU Values
Text Value
HydroPump 1
HydroPumpTurbine 2
HydroTurbine 3
4.3.21 EnumGenerationTypeTGU
Table 168: Enumeration Type EnumGenerationTypeTGU Values
Text Value
CombustionUnit 0
CombustionUnit_HRSG 4
CombustionUnit_HRSG_SF 5
CombustionUnit_HRSG_BP 6
CombustionUnit_HRSG_SF_BP 7
SteamUnit 8
CombustionBoiler 9
SteamTurbine 10
SteamTurbineExtraction 11
SteamTurbineBackpressure 12
Reducer 13
Distiller 14
SteamDump 18
4.3.22 EnumHTCCalcMode
Table 169: Enumeration Type EnumHTCCalcMode Values
Text Value
FullPlanning 2
ThermalFixed 5

Edition 08.2013
Appendixes
4.3 Enumerations
RePlanning 8
FullPlanning2Step 9
RePlanning2Step 10
4.3.23 EnumMIPGapSelector
Table 170: Enumeration Type EnumMIPGapSelector Values
Text Value
Relative 0
Absolute 1
4.3.24 EnumOptimizationType
Table 171: Enumeration Type EnumOptimizationType Values
Text Value
Shadow 0
Target 1
Min 2
Max 3
Open 4
4.3.25 EnumPlanHoriz
Table 172: Enumeration Type EnumPlanHoriz Values
Text Value
ManualEntry 0
4.3.26 EnumPlantType
Table 173: Enumeration Type EnumPlantType Values
Text Value
Simple 0
CombinedCycle 1
CommonSteamHeader 2

Edition 08.2013
Appendixes
4.3 Enumerations
4.3.27 EnumPowerLinePolicy
Table 174: Enumeration Type EnumPowerLinePolicy Values
Text Value
Free 0
AtFullHour 1
4.3.28 EnumProgramState
Table 175: Enumeration Type EnumProgramState Values
Text Value
Waiting 0
Finished 1
Active 2
OK 3
Message 4
DataError 5
Error 6
WriteDetails 7
Stopped 8
Cancelled 9
Read 10
Check 11
StartDispatch 12
MILP 13
Dispatch 14
Write 15
MILP1 16
MILP2 17
MILP3 18
MILPaccept 19
MPROF 20

Edition 08.2013
Appendixes
4.3 Enumerations
Aux1 51
Aux2 52
Aux3 53
4.3.29 EnumReservoirContentUoM
Table 176: Enumeration Type EnumReservoirContentUoM Values
Text Value
Water 0
Energy 1
4.3.30 EnumRsrvClEnergy
Table 177: Enumeration Type EnumRsrvClEnergy Values
Text Value
Energy 0
RsrvCl1 1
RsrvCl2 2
RsrvCl3 3
RsrvCl4 4
RsrvCl5 5
4.3.31 EnumRsrvCont
Table 178: Enumeration Type EnumRsrvCont Values
Text Value
LargestInput 1
LargestUnit 2
LargestTransaction 3
PartnerEmergency 4

Edition 08.2013
Appendixes
4.3 Enumerations
4.3.32 EnumRsrvModule
Table 179: Enumeration Type EnumRsrvModule Values
Text Value
NoReserve 0
Spinning 5
StbyPump 6
Standby 7
PrimaryReg 8
SecondaryReg 11
StandByOff 12
Online 13
4.3.33 EnumSpillwayType
Table 180: Enumeration Type EnumSpillwayType Values
Text Value
Overflow 0
Controllable 1
4.3.34 EnumSpotPolicy
Table 181: Enumeration Type EnumSpotPolicy Values
Text Value
Free 0
AtFullHour 1
AtFourHour 2
4.3.35 EnumStartCond
Table 182: Enumeration Type EnumStartCond Values
Text Value
FromMeasVal 0
FromSchedule 1

Edition 08.2013
Appendixes
4.3 Enumerations
FromTarget 2
4.3.36 EnumSUPsel
Table 183: Enumeration Type EnumSUPsel Values
Text Value
WithRest 0
WithoutRest 1
4.3.37 EnumSwitch
Table 184: Enumeration Type EnumSwitch Values
Text Value
Off 0
On 1
4.3.38 EnumSwitchConstraint
Table 185: Enumeration Type EnumSwitchConstraint Values
Text Value
NotActive 0
SoftConstraint 1
HardConstraint 2
4.3.39 EnumSwitchingPolicy
Table 186: Enumeration Type EnumSwitchingPolicy Values
Text Value
NotAllowed 0
Allowed 1
AllowedAtFullHour 2

Edition 08.2013
Appendixes
4.3 Enumerations
4.3.40 EnumSwitchRegimes
Table 187: Enumeration Type EnumSwitchRegimes Values
Text Value
UseValues 0
UseRegimes 1

Edition 08.2013
Appendixes
4.4 Data Types
4.4 Data Types

In this chapter you can find a description of the editing of the different data types in the user interface,
together with some examples.
4.4.1 Numeric values
Attributes with a numeric value can be edited directly in an edit box. You can find two types of values –
integer values and real values. Some basic value checks are performed directly after entering them in the edit
box For example for the integer value it is not possible to enter decimal point and decimal numbers or enter
letters.
Following figure shows an example of floating point numeric value in the user interface.
Figure 26: Entering a value
4.4.2 Enumerations
Enumerations are presented in the UI as dropdown boxes. You can only select a value from the list of
possible values of the corresponding enumeration.
You can see a dropdown box example on the following figure.
Figure 27: Entering an enumeration type value
4.4.3 Date/Time
There is a special dialog box for entering the values of the Date/Time type. You can access it over the small
calendar icon on the left of the value box. This dialog allows you to comfortable enter the Date/Time values.
You can select the day from a calendar view and direct enter the time.

Edition 08.2013
Appendixes
4.4 Data Types
An example of entering the Date/Time value you can find on following figure
Figure 28: Entering a Date/Time value
4.4.4 Schedules
Schedules are scalar type values entered over a time period in a table form. The desired time period is
selectable from the dropdown box above the attributes tab control. You can enter the desired values in the
table as you will enter another numeric values, just for every displayed time slice. It is not possible to change
the time period after you enter the edit mode, so please choose the correct period before.
An example of entering schedules is shown in the figure below.
Figure 29: Entering schedules
Caution
Modifying the time step shorter to longer value (e.g. from 15 min to an hour), causes by editing the schedule
data a deletion of all values, that are not according to a new time step (e.g. values for 15, 30 and 45 min of
every hour). You will be informed about this behavior, and all schedule data, which have to be deleted, will be
displayed. You have to approve this deletion before you can enter new schedule data.

Edition 08.2013
Appendixes
4.4 Data Types
4.4.5 Curves
Curves (2D or 3D) are entered in a tabular form. You can enter 2 or 3 values per row regardless of the type of
the curve. On the left of the curve table all rows are displayed in a graph as points, so you can directly see
what you are entered.
The figure below shows an example of entering curve data.
Figure 30: Entering curve data

Edition 08.2013
Appendixes
4.5 Linear Programming
Conventions:
Table 188: Letters used in Variable and Constraint names
Letter Meaning
X or XX or XXX Index 1
Y or YY or YYY Index 2
Z or ZZ or ZZZ Index 3
4.5.1 Variables
Table 189: List of jROS Variables used in MILP
Variable Index 1 Index 2 Index 3 Unit Description
CcpActXXX_YYY CCP Time - binary Combined cycle plant state(1 - Active)
CcpPelXXX_YYY CCP Time - MW (el) Electrical production of a Combined

cycle plant
CcpTrXXX_YYY_ZZZ From To Time binary Combined cycle plant mode transition

(1 - active transition)
ConActXXX_YYY Contract Time - binary Contract state (1 - Active)
ConPelXXX_YYY Contract Time - MW (el) Contracted electric power
FuPinXXX_YYY Fuel Time - GJ/h Total consumption of a fuel per time
HpgActXXX_YYY HGU Time - binary HGU state (1 - Active)
HpgVolXXX_YYY HGU Time - MWh Hydro Pump volume
HtgActXXX_YYY HGU Time - binary Hydro Turbine state (1 - Active)
HtgVolXXX_YYY HGU Time - MWh Hydro Turbine volume
PumpInSys_XXX Time - - binary Pump operation state of the whole

system (1 - Active) for SimTurbPump
needed
RelVolXXX_YYY Reservoir Time - Reservoir Release Volume
ResTarLowXXXSl Reservoir - - Reservoir Target Volume downwards

(slack variable)
ResVolXXX_YYY Reservoir Time - Reservoir Volume
RgCgPowProdXXX_YYY CogenZone Time - Range of power production restriction

group (Min/MaxPowerSched)
RgCgPrimPowXXX_YYY CogenZone Time - Range of primary power restriction

group (FuelMin/MaxSched)
RsTNoExLoX_YYY_ZZZ ReserveClass TGU Time Reserve class max non exclusive

downwards contribution for a TGU
RsTNoExUpX_YYY_ZZZ ReserveClass TGU Time Reserve class max non exclusive

upwards contribution for a TGU

Edition 08.2013
Appendixes
TguActXXX_YYY TGU Time - binary TGU state (1 - Active)
TguDPelDoXXX_YYY TGU Time - TGU delta downwards rate
TguDPelUpXXX_YYY TGU Time - TGU delta upwards rate
TguPelXXX_YYY TGU Time - MW (el) Electrical production of a Thermal

Generation Unit
TguPHoffXXX TGU - - binary Binary to decide if TGU is off for entire

planning horizon
TguPinFX_YYY_ZZZ Fuel TGU Time GJ/h TGU Fuel consumption from a specific
Fuel Stock (1-5)
TguPinStUpXXX_YYY TGU Time - GJ/h TGU Start-up fuel consumption from

the Startup Fuel Stock
TguPinXXX_YYY TGU Time - GJ/h Total consumption of fuel of a TGU

per time
TguRLoX_YYY_ZZZ ReserveClass TGU Time MW (el) TGUs Reserve contribution

downwards for a specific reserve
class
TguRStX_YYY_ZZZ ReserveClass TGU Time TGUs Reserve step for a reserve

class
TguRUpX_YYY_ZZZ ReserveClass TGU Time MW (el) TGUs Reserve contribution upwards

for a specific reserve class
TguSDXXX_YYY TGU Time - binary TGU desynchronization state
TguSUXXX_YYY TGU Time - binary TGU synchronized state
TguUXXX_YYY_ZZZ TGU Time MW (el) MW (th) TGUs modal definition of

PrimEnergyPowerCurve
4.5.2 Constraints
Table 190: List of jROS Constraints used in MILP
Constraint Index 1 Index 2 Index 3 Description
CcpDTMinXXX_YYY CCP Time - Minimum downtime for a combined cycle

plant
CcpRsrvUpX_YYY_ZZZ ReserveClass CCP Time Requested reserve up for a combined

cycle plant
CcpRsrvUpXMaxYYY_ZZZ ReserveClass CCP Time Maximum requested reserve up for a

combined cycle plant
CcpSimRunXXX_YYY CCP Time - Sim Run restriction for CCP modes -

subsequently TGU's
CcpSwXSDYYY_ZZZ HelperIndex CCP Time Shutdown constrain for combined cycle

plant
CcpSwXSUYYY_ZZZ HelperIndex CCP Time Startup constrain for combined cycle

Edition 08.2013
Appendixes
plant
CcpTrAXXX_YYY_ZZZ From To Time CCP state transition A
CcpTrBXXX_YYY_ZZZ From To Time CCP state transition B
CcpTrCXXX_YYY_ZZZ From To Time CCP state transition C
CcpUTMinXXX_YYY CCP Time - Minimum uptime for a combined cycle

plant
CgPowProdXXX_YYY CogenZone Time - power production restriction group

(Min/MaxPowerSched)
CgPrimPowXXX_YYY CogenZone Time - primary power restriction group

(FuelMin/MaxSched)
CgSimStXXX_YYY CogenZone Time - Sim Run restriction for Units
ConPMaxXXX_YYY Contract Time - Maximum power volume in a contract
ConPMinXXX_YYY Contract Time - Minimum power volume in a contract
ContRelXXX_YYY Reservoir Time - Content release from a reservoir
ContRESXXX_YYY Reservoir Time - Content of a reservoir
DefCcpPelXXX_YYY CCP Time - Definition of the electric power

production for the combined cycle plant
DefCcpSDXXX_YYY CCP Time - Definition of the shutdown for the

combined cycle plant
DefCcpSUXXX_YYY CCP Time - Definition of the startup for the combined

cycle plant
DefPumpInSys_XXX Time - - Definition of the pumping state of the

system
DefTguFSX_YYY_ZZZ FuelStock TGU Time Definition of the fuel consumption power

table for a fuel stack
DefTguPelXXX_YYY TGU Time - Definition of the electric power for a TGU
DefTguPHoffXXX TGU - - Definition if the TGU is off for the whole

planning horizon
DefTguPHonXXX TGU - - Definition if the TGU is on for the whole

planning horizon
DefTguPinXXX_YYY TGU Time - Definition of the TGU consumption
DefTguUXXX_YYY TGU Time - Definition of the "modal" PEP for a TGU
DefTurbInSys_XXX Time - - Definition of the turbining state of the

system
FuelConsXXX_YYY TGU Time - Fuel consumption for a specific

FuelStock

Edition 08.2013
Appendixes
HpgPrioXXX_YYY HGU Time - Priority sequence for pump usage
HtgPrioXXX_YYY HGU Time - Priority sequence for turbines
HTGRULX_YYY_ZZZ ReserveClass HGU Time Upper lower coupling of a HGU
LoadSAXXX_YYY Area Time - Area load
Pump2TurbXXX_YYY_ZZZ HGU HGU Time Restriction of pumping and turbinating at

the same time
PumpQMaxXXX_YYY HGU Time - Maximum flow for a pump
PumpQMinXXX_YYY HGU Time - Minimum flow for a pump
R_A_SHXXX_YYY_ZZZ ReserveClass HGU Time Reserve active for a HGU for a reserve
class
R_A_SXXX_YYY_ZZZ ReserveClass TGU Time Reserve active for a TGU for a reserve
class
ResTarLowXXX Reservoir - - Lower target volume of a reservoir
ResTarUppXXX Reservoir - - Upper target volume of a reservoir
RLStHXX_YYY_ZZZ ReserveClass HGU Time Standby reserve downwards for a HGU
RLStTXX_YYY_ZZZ ReserveClass TGU Time Standby reserve downwards for a TGU
RPrSrHL_XXX_YYY ReserveClass HGU Time Primary and secondary reserve

downward for a HGU
RPrSrHU_XXX_YYY ReserveClass HGU Time Primary and secondary reserve upward

for a HGU
RqRDoXXSAYY_ZZZ ReserveClass Area Time Required reserve downward for the area
RqRUpXXSAbinYY_ZZZ ReserveClass Area Time Reserve downward for the area active
RqRUpXXSAYY_ZZZ ReserveClass Area Time Required reserve upward for the area
RsHLoLiNotExX_YYY_ZZZ ReserveClass HGU Time HGU reserve lower limit not exclusive
RsHUpLiNotExX_YYY_ZZZ ReserveClass HGU Time HGU reserve upper limit not exclusive
RsrvHguLoExclX_YYY_ZZZ ReserveClass HGU Time Reserve downward for HGU exclusive
RsrvHguUpExclX_YYY_ZZZ ReserveClass HGU Time Reserve upward for HGU exclusive
RSTEPHXXX_YYY_ZZZ ReserveClass HGU Time Primary and secondary regulation for

HGU
RSTEPXXX_YYY_ZZZ ReserveClass TGU Time Primary and secondary regulation for

TGU
RsTguLoExX_YYY_ZZZ ReserveClass TGU Time Reserve downwards exclusive for TGU
RsTguUpExX_YYY_ZZZ ReserveClass TGU Time Reserve upwards exclusive for TGU
RsTLoLiNExX_YYY_ZZZ ReserveClass TGU Time TGU reserve lower limit not exclusive

Edition 08.2013
Appendixes
RsTUpLiNExX_YYY_ZZZ ReserveClass TGU Time TGU reserve upper limit not exclusive
RUStHXX_YYY_ZZZ ReserveClass HGU Time Standby reserve upwards for a HGU
RUStTXX_YYY_ZZZ ReserveClass TGU Time Standby reserve upwards for a TGU
SimPumpHyShCirc_XXX Time - - Limits pumping operation
SimTurbHyShCirc_XXX Time - - Limits turbining operation
TguBlendXXX_YYY TGU Time - Fuel mixing for a TGU
TguCcpDTbXXX_YYY_ZZZ CCP Time Time Downtime backward for CCP
TguCcpUTbXXX_YYY_ZZZ CCP Time Time Uptime backward for CCP
TguDPelXXX_YYY TGU Time - Ramps for electric power of a TGU
TguDTbXXX_YYY_ZZZ TGU Time Time Downtime backward for TGU
TguDTMinXXX_YYY TGU Time - Minimum downtime for a TGU
TguPinStUpFSXXX_YYY TGU Time - Limiting startup consumption
TguPinStUpXXX_YYY TGU Time - Startup fuel restriction
TguPMaxSUXXX_YYY TGU Time - Startup power production upper limit
TguPMaxXXX_YYY TGU Time - Upper limit of power production of TGU
TguPMinXXX_YYY TGU Time - Lower limit of power production of TGU
TguRaDoXXX_YYY TGU Time - Startup overruling of ramping
TguRaUpXXX_YYY TGU Time - Shutdown overruling of ramping
TguRsMxLoX_YYY_ZZZ ReserveClass TGU Time Maximum reserve downward for TGU
TguRsrvMxX_YYY_ZZZ ReserveClass TGU Time Maximum reserve for TGU
TguSDLimXXX_YYY TGU Time - Shutdown limitation (min uptime + min

downtime)
TguSULimXXX_YYY TGU Time - Startup limitation (min uptime + min

downtime)
TguSURX_YYY_ZZZ ReserveClass TGU Time Reserve start for TGU
TguSUSDXXX_YYY TGU Time - Startup and shutdown exclusive for a

TGU
TguSwXSDYYY_ZZZ HelperIndex TGU Time Definition of shutdown of a TGU
TguSwXSUYYY_ZZZ HelperIndex TGU Time Definition of startup of a TGU
TguUStartXXX_YYY TGU Time - Deactivation of Modal PEP during

Startup of a TGU
TguUTbXXX_YYY_ZZZ TGU Time Time TGU uptime backward
TguUTMinXXX_YYY TGU Time - Minimum uptime for a TGU

Edition 08.2013
Appendixes
TurbQMaxXXX_YYY HGU Time - Maximum flow for a turbine
TurbQMinXXX_YYY HGU Time - Minimum flow for a turbine

Edition 08.2013
Appendixes
4.5.3 Penalties
Table 191: List of jROS Penalties used during the optimization
Penalty Value Description
cHPGVolSlackPen 10 Penalty for HPG slack volume [$/Mm3]
cHTGVolSlackPen 9 Penalty for HTG slack volume [$/Mm3]
cLoadSAPen 50.000 Penalty for load constraint of subareas
cLoadSAPenMilp 50.000 Penalty for load of subareas in MILP
cPowerLinePen 0,1 Penalty for power line interchange
cPowProdPen 4.000.000 Penalty for constraint PowProd violation
cPrimEnPen 100.000 Penalty for constraint PriEn violation
cPrimPowPen 100.000 Penalty for fuel transport limit [$/dim]
cRsrvPen 10.000 Penalty for reserve violation
cRsrvPenMILP 10.000 Penalty for reserve violation in MILP
cSlackPmaxHGU 5.000.000.000 Penalty for violating Pmax of turbines
cSlackPminHGU 10.000.000 Penalty for violating Pmin of turbines

Edition 08.2013
4 Appendixes

Edition 08.2013

jROS UG HTC

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

jROS UG HTC

Uploaded by

Copyright:

Available Formats

History

Spectrum Power Preface

Hydro-Thermal Hydro Thermal Coordination 1

Disclaimer of Liability Copyright

1.0 06.2010 initial version

2.0 07.2010 Update after FAT

2.01 12.2010 Appendices added, minor text changes.

2.1 02.2011 CRs included

3.1 01.2012 Update for Patch 12

4.0 04.2012 Update for Patch 13

5.0 08.2012 Update for Patches 14 & 15

5.1 11.2012 Finalize Patches 14 & 15 etc

5.2 01.2013 Reviewed and finalized

6.0 08.2013 Updated with features for Patch 16

6.1 08.2013 Updated for PLN SAT

2 Hydro Thermal Coordination (HTC), User Guide

Hydro Thermal Coordination (HTC), User Guide 3

Structure of this Manual

4 Hydro Thermal Coordination (HTC), User Guide

Hydro Thermal Coordination (HTC), User Guide 5

1 Hydro Thermal Coordination .............................................................................................................................. 10

3 Power System Model ........................................................................................................................................... 60

6 Hydro Thermal Coordination (HTC), User Guide

3.5.1 Areas and Exchanges Among Areas ................................................................................... 70

Hydro Thermal Coordination (HTC), User Guide 7

4.2.4 CogenStorage .................................................................................................................... 121

8 Hydro Thermal Coordination (HTC), User Guide

4.3.22 EnumHTCCalcMode .......................................................................................................... 160

Hydro Thermal Coordination (HTC), User Guide 9

1 Hydro Thermal Coordination

10 Hydro Thermal Coordination (HTC), User Guide

1.2 Keyboard Shortcuts

Navigating in object tree

Hydro Thermal Coordination (HTC), User Guide 11

Accessing Help Information

12 Hydro Thermal Coordination (HTC), User Guide

1.3 Application User Interface

First look at the user interface

Object Browser Object Panel

Hydro Thermal Coordination (HTC), User Guide 13

Green The unit is available

Grey The unit is set to not-available

Pink The unit is must-on (explicitly or implicitly)

dark-blue The unit is on FixP.

14 Hydro Thermal Coordination (HTC), User Guide

Blue The value is entered manually (or from import)

Red The value is invalid (to be ignored)

Grey The value is not renewed (to be ignored)

In general the colors represent the 'quality-flags' of the values.

User Defined Attributes

- Reverse Message Order

- Sorted Chart Legend

- Additional rows settings

Hydro Thermal Coordination (HTC), User Guide 15

Starting the HTC

16 Hydro Thermal Coordination (HTC), User Guide

Navigate in the selection tree

Hydro Thermal Coordination (HTC), User Guide 17

2.2 Performing a calculation

HTC Program Parameters

You can set the following HTC program parameters

 Begin Time (of planning horizon)

- FullPlanning (a full optimization and subsequent costing)