<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="de">
	<id>https://www.talsim.de/docs/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Haghani</id>
	<title>TALSIM Docs - Benutzerbeiträge [de]</title>
	<link rel="self" type="application/atom+xml" href="https://www.talsim.de/docs/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Haghani"/>
	<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Spezial:Beitr%C3%A4ge/Haghani"/>
	<updated>2026-04-05T14:15:24Z</updated>
	<subtitle>Benutzerbeiträge</subtitle>
	<generator>MediaWiki 1.38.4</generator>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Unterteilung_in_Systemelemente/en&amp;diff=13000</id>
		<title>Unterteilung in Systemelemente/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Unterteilung_in_Systemelemente/en&amp;diff=13000"/>
		<updated>2021-08-30T10:49:26Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=Systemabgrenzung|hoch=Arbeitsschritte zur Modellerstellung|nachher=Systemlogik}}&lt;br /&gt;
&lt;br /&gt;
In order to divide a water resources system into individual [[Special:MyLanguage/Beschreibung der Systemelemente|system elements]] it is vital to consider the problem which the model is used for and the existing data basis. &lt;br /&gt;
&lt;br /&gt;
Basically there are two possible ways for the division of the system. It can be divided either catchment-based or grid-based. In addition, all hydrological structures relevant to the problem must be identified and represented by a suitable [[Special:MyLanguage/Beschreibung der Systemelemente|system element]], e.g. dams by [[Special:MyLanguage/Speicher|storage]], extractions by [[Special:MyLanguage/Verbraucher|consumer]], etc. Often there are several feasible solutions.&lt;br /&gt;
&lt;br /&gt;
The preliminary work for dividing a river basin is usually done with a GIS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Catchment-based Division==&lt;br /&gt;
&lt;br /&gt;
Criteria for the division can be:&lt;br /&gt;
&lt;br /&gt;
*Catchment properties (topography)&lt;br /&gt;
* Punctual changes of the outflow by&lt;br /&gt;
** Inflows&lt;br /&gt;
** Point sources&lt;br /&gt;
** Extractions&lt;br /&gt;
* Location of hydrological structures&lt;br /&gt;
* Location of gauging stations&lt;br /&gt;
* Flow type and geometry&lt;br /&gt;
&lt;br /&gt;
The results of this division are digital catchment boundaries and river sections. If the available data initially results in a rough division, it can be subdivided even further, especially if, due to the problem at hand, certain processes in the waterbody can no longer be represented with the intitial division. In the following, a high resolution water resources system is compared to a low resolution water resources system:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| [[Datei:System_räumlich_hochaufgelöst.png|400px]] || [[Datei:System_räumlich_geringaufgelöst.png|400px]]&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
*As the accuracy of system mapping increases, the importance of hydraulics in the waterbodies increases.&lt;br /&gt;
*The parameters of the runoff concentration only refer to the surface runoff in the corresponding sub-catchments, resp. interflow and base flow.&lt;br /&gt;
*The illustration of flood-routing within the waterbodies is possible.&lt;br /&gt;
||&lt;br /&gt;
*Simple approaches to the calculation of runoff generation usually manage better with a rough system illustration.&lt;br /&gt;
*Both, the surface runoff in the sub-catchments and the flood-routing that occur in the waterbodies are included in the parameters of the runoff concentration. &lt;br /&gt;
*The illustration of flood-routing within the waterbodies is hardly possible.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[Datei:Teilgebiet_Auswahl_Systemelemente.png|thumb| Sub-catchments can be defined via a [[Einzugsgebiet|Rainfall-Runoff Model]][[Datei:Systemelement001.png|20px]] or can be visualised through a [[Special:MyLanguage/Einleitung|hydrograph]][[Datei:Systemelement002.png|20px]] at the output]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The next step is to decide which system elements are to be used to map the sub-catchments, depending on the problem and the data basis. Alongside the system element [[Special:MyLanguage/Einzugsgebiet|sub-basin]], which brings the load into the system via a precipitation-runoff simulation, the system element [[Special:MyLanguage/Einleitung|point source]] can feed the outflow from the sub-catchment directly into the system via a hydrograph. The latter is of course only possible if a hydrograph is available. Then it is the solution using the fewest computational resources, which in addition (with good quality of the input data) also illustrates the actual outflow behavior in a realistic manner. If, however, for example, a forecast is to be calculated with changed land use conditions or if the hydrograph is not long enough, it is advisable to use the system element [[Special:MyLanguage/Einzugsgebiet|sub-basin]]. In Talsim-NG the selection of the system element for sub-catchments can also vary from sub-catchment to sub-catchment.&lt;br /&gt;
&lt;br /&gt;
Once the system elements are defined, the [[Special:MyLanguage/Systemlogik|flow network]] is created, i.e. the flow relationships between the elements are defined.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Grid-based Division==&lt;br /&gt;
&lt;br /&gt;
In grid-based division, water is generally passed from one cell to the next according to its flow direction. &lt;br /&gt;
&lt;br /&gt;
The transfer from one cell to the next varies depending on the flow component:&lt;br /&gt;
* Surface runoff is incorporated into the runoff generation process of the next cell, i.e. it is treated like additional precipitation.&lt;br /&gt;
* Interflow is fed into the cascade of storages of the next cell&#039;s interflow.&lt;br /&gt;
* Base flow is fed into the cascade of storages of the next cell&#039;s base flow.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Unterteilung_in_Systemelemente/3/en&amp;diff=12999</id>
		<title>Translations:Unterteilung in Systemelemente/3/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Unterteilung_in_Systemelemente/3/en&amp;diff=12999"/>
		<updated>2021-08-30T10:49:26Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Basically there are two possible ways for the division of the system. It can be divided either catchment-based or grid-based. In addition, all hydrological structures relevant to the problem must be identified and represented by a suitable [[Special:MyLanguage/Beschreibung der Systemelemente|system element]], e.g. dams by [[Special:MyLanguage/Speicher|storage]], extractions by [[Special:MyLanguage/Verbraucher|consumer]], etc. Often there are several feasible solutions.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Speicher/en&amp;diff=12998</id>
		<title>Speicher/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Speicher/en&amp;diff=12998"/>
		<updated>2021-08-30T10:48:25Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=Verzweigung|hoch=Beschreibung der Systemelemente|nachher=Speicher mit Wasserkraftanlagen}}&lt;br /&gt;
&lt;br /&gt;
[[Datei:Systemelement006.png|50px|none]]&lt;br /&gt;
&lt;br /&gt;
Storages are used to store an inflow and, depending on the current storage content and operating rules, to release water for different uses to up to three different system elements. With the possibility to [[Special:MyLanguage/Betriebsregelkonzept|regulate and control]] releases, it is an extremely flexible system element with a variety of options. Originally, the storage element was developed to represent reservoirs behind dams, but it can also be used to model other storages such as flood control reservoirs or similar.&lt;br /&gt;
Additionally, it is possible to optionally simulate the addition of water to the storage by precipitation, as well as losses from the storage by evaporation and infiltration.&lt;br /&gt;
&lt;br /&gt;
The storage system element can also be used to simulate [[Special:MyLanguage/Speicher mit Wasserkraftanlagen|hydro power plants]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rating Curve==&lt;br /&gt;
&lt;br /&gt;
The storage rating curve defines the relationship between storage volume, water level and surface area.&lt;br /&gt;
It forms the basis for all calculation options that depend on not only the storage volume but also the water level and/or the surface area e.g., precipitation/losses, flow over a weir, pressurized flow through pipes.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Releases==&lt;br /&gt;
The term release is used to describe any discharge of water according to operating rules from the storage to the downstream area through regulated or unregulated outlets. This includes controlled releases through operating and bottom outlets as well as releases via a spillway. &lt;br /&gt;
&lt;br /&gt;
Releases are often related to operating rules, therefore, it is possible or sometimes also necessary to define several releases for each outlet.&lt;br /&gt;
&lt;br /&gt;
===Calculation Options===&lt;br /&gt;
&lt;br /&gt;
Independent of the selected calculation option, releases can always be scaled with a system state/control cluster, which makes it possible to model complex [[Special:MyLanguage/Betriebsregelkonzept|operating rules]], which are not only dependent on states within the storage, but also on other states within the river basin.&lt;br /&gt;
&lt;br /&gt;
====Release per Timestep / Release Sequence====&lt;br /&gt;
&lt;br /&gt;
With this option, you define the release values by directly entering (up to 365) values. During the simulation, these values are then used as release values for the individual simulation timesteps in the given order.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Function (+ Hydrograph/Time Series)====&lt;br /&gt;
&lt;br /&gt;
With this option, releases are defined as functions of storage volume by entering the nodes of the function. These releases can additionally be scaled with a factor, an annual, weekly and/or daily pattern (and, as with all calculation options, with a system state or a control cluster) or with a factor and a time series.&lt;br /&gt;
&lt;br /&gt;
The following function types are available:&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|&lt;br /&gt;
KNL&lt;br /&gt;
|Rating curve&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
LAM&lt;br /&gt;
|Pool-based operating plan&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
XYZ&lt;br /&gt;
|Time-dependent function &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Rating Curve=====&lt;br /&gt;
&lt;br /&gt;
The rating curve consists of a time-independent functional relationship between releases and storage volume. You can specify whether the function should be interpolated linearly between the entered nodes or whether the function should be interpreted as a step function.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Pool-Based Operating Plan=====&lt;br /&gt;
&lt;br /&gt;
With the option pool-based operating plan, the storage is divided into different pools which vary over the year and these pools are each assigned a fixed release amount. A pool-based operating plan is defined by entering a number of releases with ascending amounts and specifying the corresponding storage volume for each release amount at different times of the year. &lt;br /&gt;
&lt;br /&gt;
The areas between the entered nodes can be interpreted as steps. However, it is also possible to interpolate linearly in time and/or between the release amounts.&amp;lt;br clear=&amp;quot;all&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery mode=&amp;quot;nolines&amp;quot; widths=600px heights=200px&amp;gt;&lt;br /&gt;
Datei:Lamellenplan_EN.png|Comparison of a pool-based operating plan in the two- and three-dimensional representation, &amp;lt;br/&amp;gt;Interpretation: constant block (steps)&lt;br /&gt;
Datei:Lamellenplan_linear_interpoliert_EN.png|Comparison of a pool-based operating plan in the two- and three-dimensional representation, &amp;lt;br/&amp;gt;Interpretation: linearly interpolated (both in time and between pools)&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Time-Dependent Function=====&lt;br /&gt;
&lt;br /&gt;
A time-dependent function is very similar to a pool-based operating plan, but a bit more flexible: the releases defined at different time periods only have to be of equal number but not in value, and they do not necessarily have to be ascending. This makes it possible to define arbitrary functions with individual nodes for release amounts and storage volumes for different time periods.&lt;br /&gt;
&lt;br /&gt;
By default the functions are interpreted as steps with constant values between the entered nodes. However, it is also possible to interpolate linearly in time and/or between the entered storage-release value pairs.&amp;lt;br clear=&amp;quot;all&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Weir Overflow====&lt;br /&gt;
&lt;br /&gt;
The release is calculated using the weir formula according to Poleni as free / submerged overflow.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Pressure Pipeline====&lt;br /&gt;
&lt;br /&gt;
The release is calculated according to the Prandtl-Colebrook and Darcy-Weisbach formulas.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Turbine====&lt;br /&gt;
&lt;br /&gt;
Based on the characteristics of the turbine, the flow through the turbine is determined depending on the storage level and the downstream water level, such that the desired power output is maintained as long as the maximum possible flow rate of the outlet is not exceeded. See also the page on [[Special:MyLanguage/Speicher_mit_Wasserkraftanlagen|hydropower plants]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Limits===&lt;br /&gt;
&lt;br /&gt;
The [[Special:MyLanguage/Betriebsregeltypen|maximum physically possible output]] of individual outlets can be entered as functions of storage volume, causing releases to be limited to these values. It is also possible to specify a minimum permissible release value, below which the release will be set to 0.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Internal Dependencies===&lt;br /&gt;
&lt;br /&gt;
Internal dependencies are used to define the [[Special:MyLanguage/Betriebsregeltypen|priorities in case of multiple competing releases from one storage]]. One or more releases can be reduced if another release exceeds a certain amount or if the storage volume falls below a certain value. &lt;br /&gt;
&lt;br /&gt;
The limits for releases and storage volumes for internal dependencies are entered as constant values, which can however be scaled with daily, weekly and/or annual patterns.&lt;br /&gt;
&lt;br /&gt;
If several releases are to be reduced simultaneously, the order in which they should be reduced must also be specified.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&#039;&#039;If release B &amp;gt; 0 and the storage volume S &amp;lt; X, then reduce release A by the amount of release B, but at most to a minimum value of zero.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This means that there is a linear relatioship between A and B until B is equal to the value of A. If the value of B rises any further, A still remains zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Precipitation/Losses==&lt;br /&gt;
&lt;br /&gt;
An addition of water caused by precipitation onto the storage&#039;s surface or losses caused by evaporation or infiltration can be considered via two options:&lt;br /&gt;
&lt;br /&gt;
* Constant pattern (daily, weekly and/or annual pattern)&lt;br /&gt;
* Time series&lt;br /&gt;
&lt;br /&gt;
These can be additionally scaled by a factor.&lt;br /&gt;
Precipitation, evaporation and infiltration values must be provided as a linear unit such as e.g. mm. During the simulation, the provided values are converted to water volumes by multiplying with the current storage surface area.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Speicher/7/en&amp;diff=12997</id>
		<title>Translations:Speicher/7/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Speicher/7/en&amp;diff=12997"/>
		<updated>2021-08-30T10:48:24Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Releases==&lt;br /&gt;
The term release is used to describe any discharge of water according to operating rules from the storage to the downstream area through regulated or unregulated outlets. This includes controlled releases through operating and bottom outlets as well as releases via a spillway.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12996</id>
		<title>Betriebsregeltypen/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12996"/>
		<updated>2021-08-30T10:47:13Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=|hoch=Betriebsregelkonzept|nachher=Abstraktion der Betriebsregeln}}&lt;br /&gt;
&lt;br /&gt;
The operating plan of a dam or a storage network is part of the official approval of plans and usually is available as a report or presentation. Its complexity can vary: it ranges from simply defining flood protection areas and setting a report and alarm plan to notify the supervisory authorities in exceptional situations to complex sets of rules concerning functional dependencies that derive discharges from varying system states.&lt;br /&gt;
&lt;br /&gt;
As follows, principles to clarify the variety of possible regulations and reduce them to essential dependencies are presented. A concept is derived to represent most operating rules by a few basic calculation rules. The given selection does not claim to be complete, but it is likely to contain the rules applied in practice.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Basic Principle: Verification of Physical Limits==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb1.png|thumb|Figure 1: Dependency on storage capacity]]&lt;br /&gt;
&lt;br /&gt;
When specifying discharges according to an operating rule, it is assumed that the outlet capacity is sufficient to meet these discharges. Thus, dimensioning the outlet element must consider the operating requirements. In principle, the physically possible discharge, given by the outlet&#039;s characteristic curve at full opening, sets the upper limit value.&lt;br /&gt;
&lt;br /&gt;
If the pressure level or the outlet capacity is sufficient to discharge the desired quantity when fully opened, the discharge can be throttled to the intended level by closing a slide. If the pressure level is insufficient, only the hydraulically possible discharge can be discharged.&lt;br /&gt;
&lt;br /&gt;
*Mathematical abstraction:&lt;br /&gt;
:All outlets obeying an operating rule are functions of the storage&#039;s volume and cannot exceed the outlets&#039; maximum capacity when fully opened. As soon as the capacity of the outlets exceeds the required discharge, it can be adjusted by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
All discharge types from storages mentioned below are subject to this restriction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 1: Definition of a Minimum Output or a Safely Dischargeable Maximum Output==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb2.png|thumb|Figure 2: Example for minimum and maximum discharge as a function of storage capacity]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The specification of a minimum or maximum discharge is based on requirements downstream of a storage. The maximal discharge is based on the discharge respective to a critical, downstream cross-section. Consequently, a hydraulic method exists for its determination. In contrast, there is no clear guideline for the minimum discharge. Often, ratios of MNQ or MQ are used. Independent of determining the minimum or maximum discharge, the basic principle to verify outlet elements&#039; physical limits is applied. So, minimum and maximum discharge can only be discharged if the outlet capacity is sufficient at the given pressure level. Since, in reality, it is unlikely that the dimensioning of the outlet elements and the required discharge are conflicting, the reference to the dependence on the storage capacity content is rather theoretical but necessary to derive general laws.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Minimum and maximum discharge are functions of the storage volume and follow the characteristic curve of fully opened outlets at a low filling level. As soon as the outlet elements&#039; capacity is sufficient for the required discharge volume, the discharge can be kept constant by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 2: Maintaining a Flood Protection Area, Possibly Timely Variable Over the Year==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb3.png|thumb|Figure 3: Example of a function to maintain a flood protection area]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The definition of a flood protection area as a minimum requirement only includes the designation of a volume, which has to be kept free for potential floodwater. The dimensioning is based on flood events with certain recurrence intervals. If the water level exceeds the mark of the protection area, an increased discharge to the downstream water of the storage ensures that the area is kept empty. Thus, this rule is reduced to a relation between discharge and storage volume, where the outlet capacity or a defined maximum discharge can serve as an upper limit for keeping the flood protection area empty. If the flood protection area is variable in time over the year, only the discharge of the respective storage volume is increased.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:There is a direct relation between storage capacity and release. If the storage capacity exceeds the mark of the flood protection area, a discharge occurs. If it remains below the mark, the discharge is set to zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 3: Direct Withdrawals from a storage for Drinking or Service Water ==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb4.png|thumb|Figure 4: Example of a function for drinking or raw water withdrawal]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Primarily, the current demand determines the volume of withdrawals from the storage, but it is also subject to temporal variations. The upper limits for withdrawals are generally set by water rights or defined maximum withdrawal volumes, which refer to selected periods such as a day, a month, a quarter, or a year. Initially, one only considers the current demand communicated by water suppliers, which constitutes a claim towards the storage. There is no connection to the actual storage and the respective storage volume.&lt;br /&gt;
:Whether the demand can be pleased by withdrawing water from the storage is determined by the actual storage volumes. To connect the water demand to the actual storage volumes, the structural implementation of withdrawal elements and means of anticipatory management are taken into account. For example, if particularly low storage volumes are reached, it is advisable to throttle withdrawals in advance to avoid the storage running empty and then completely failing at covering the demand during prolonged periods of low water &amp;lt;ref name=&amp;quot;Schultz_1989&amp;quot;&amp;gt;&#039;&#039;&#039;Schultz, G.A.&#039;&#039;&#039; (1989): Entwicklung von Betriebsregeln für die Wupper-Talsperre in Niedrig- und Hochwasserzeiten. Wasserwirtschaft 79 (7/8) S. 340-343&amp;lt;/ref&amp;gt;. Hence, there is usually space reserved in a dam specifically used for drinking water supply. Its use is handled separately in respective operating plans.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:If the demand is exactly known and unchangeable, a direct relation between withdrawal and storage volume can be defined. However, the demand is subject to certain variations. For this reason, it is recommended to normalize the relationship between withdrawals and storage volume, where the current demand serves as a scaling factor. If the storage volume falls below a defined limit value, only a certain percentage of the current demand is satisfied. The limit value, as well as the form of the function, can be variable in time.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 4: Standard Discharge to Downstream Water==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb5.png|thumb|Figure 5: Pool-based operating plan in a two-dimensional representation]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The normal discharge to the downstream water should provide a discharge compensation for seasonal differences in the inflow. If a minimum discharge is required, it will be included in the normal discharge. A pool-based operating plan is used to describe the normal discharge. It divides the storage capacity into different areas and assigns a discharge to each pool-based operation. When determining the pool-based operating plan, the long-term discharge and other withdrawals from the storage for other purposes play a decisive role. A storage should collect water in periods of high inflow but still not overflow to have sufficient reserves in periods of low inflow. The coupling of the releases to the storage pool-based operation is a function of the storage volume. Since the system is supposed to react to variations of inflow during the year, the relationship between storage volume and discharge is usually variable over time.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb6.png|thumb|Figure 6: Comparison of a pool-based operating plan in a two- and three-dimensional representation]] Like for the previous rules, the output depends on the storage volume. Usually, a pool-based operating plan is displayed in two-dimensional diagrams. The X-axis shows the time of one year, while the Y-axis shows the storage capacity. Pool-based operations are depicted as lines of equal outputs.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb7.png|thumb|Figure 7: Pool-based operating plan with linear interpolation between successive time reference points]]This view is practical but not yet complete: A three-dimensional representation of a simple pool-based operating plan makes this clear. On the X-axis is the time, on the Y-axis the storage capacity is plotted, while the Z-axis shows the output directed upwards.&lt;br /&gt;
&lt;br /&gt;
:The 3D image viewed from above gives the two-dimensional shape. Instead of taking constant blocks for the individual time horizons, a linear connection is also used often.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb8.png|thumb|Figure 8: Pool-based operating plan with two types of interpretation (selected month of May)]]For the individual periods - here months - different functional dependencies between storage capacity and outflow are considered. If the storage volume/discharge relation is also considered for a selected point in time, there are two possibilities to connect the discharge nodes. On the one hand, there is the possibility of linear interpolation, and on the other hand, a step function is possible.&lt;br /&gt;
&lt;br /&gt;
:In two-dimensional space, this information is not visible and must be specified separately. However, there is usually the convention to assume that the output between two nodes is constant, i.e. to interpret the pool-based operating plan as shown above in the form of steps.&amp;lt;br clear=&amp;quot;all&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 5: Maintaining Defined Discharges to Downstream Waters (Increase of Low Water / Coverage of Demand)==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb9.png|thumb|Figure 9: Example of a function between shortfalls and scaling factors for a storage&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
* Dependency: &lt;br /&gt;
:In this case, the current discharge is determined by conditions downstream of a storage. At a cross-section of a water resources system, the so-called &#039;&#039;control point&#039;&#039;, where the flow is dependent on the discharge from the upstream storage, a minimum flow is defined. The flow at the control point is composed of the discharge from upstream storages and the lateral inflows between the storages and the control point. If the current flow remains below the set minimum, an additional discharge from upstream storages is necessary. The volume of the additional discharge depends on the difference between the previously defined target flow and the actual flow. Whether the required discharge can be fully provided from the storage depends on the currently available stored volumes in the storage. The lower the level, the less favorable it is to provide additional water. In this context, the increase of low water/coverage of demand behaves completely identical to the drinking or service water withdrawal, with only the triggering factor differing. As mentioned before, a storage-dependent function is scaled by a factor, but this factor is now derived from a comparison between set values and current discharges.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:The determination of the additionally needed discharge is composed of several factors. Firstly, a volumetrically varying shortfall of water results from failing the target discharge. The shortfall of water is then implemented as a scaling factor to the discharge which can be defined by a function. The shortfall of water functions independently, while the scaling factor functions dependently.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb10.png|thumb|Figure 10: Example of a function for increasing low water levels or meeting demand]]&lt;br /&gt;
&lt;br /&gt;
:Secondly, it depends on the actual storage volume, if and how an additional discharge from the storage can be met. A normalized volume-dependent function and the needed discharge lead to a clear determination of the additional discharge volumes. The following [[:Datei:Theorie_Abb10.png||Fig. 10]] shows an example, where the complete provision of an increased target can only be achieved if the filling level of the storage is above a critical limit (25%).&lt;br /&gt;
&lt;br /&gt;
:If more than one storage has an influence on the relevant control point or if, in principle, more than one storage facility is to be used to meet the demand, the required additional discharge is to be divided between the storages in accordance with the corresponding regulations. A distinction must be made between the direct and indirect influences of a storage on the control point. A direct influence is present if a discharge can have a direct effect on the flow conditions at the control point, i.e. the natural flow between the storage &lt;br /&gt;
and the control point can no longer be changed by regulation. If this is not the case, an indirect influence is given.&lt;br /&gt;
&lt;br /&gt;
:All storages with a direct influence on the control point receive a shortfall factor and a volume-dependent, scalable function according to [[:Datei:Theorie_Abb10.png|Figure 10]]. Thus, depending on the shortfall quantities and the storage capacity, the actual discharge can be determined separately for each storage.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 6: Discharge Depending on the storage Inflow==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb11.png|thumb|Figure 11: Direct dependency between storage and control point]]&lt;br /&gt;
:There is a direct dependency between the discharge from the storage and the current inflow to the storage. Similar to the pool-based operating plan, there is also an adaptation to different inflow situations. This is done to prevent depletion or overflowing or to obtain a variable discharge regime downstream. However, long-term inflow fluctuations are difficult to detect with this operating rule, since the observations are only carried out as snapshots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:To determine an inflow-dependent discharge, several components have to be considered. First of all, a relation between the current inflow and discharge must be defined. In addition to the current inflow, the current storage volume is important, because the relation inflow/outflow must not be valid for every filling level. Thus it is likely that the relation is ceded completely or the release quantities are adjusted if the storage level falls below a critical level.&lt;br /&gt;
&lt;br /&gt;
:As this rule can lead to the co-occurrence of relatively small storage volumes and high inflows resulting in high discharge volumes, special attention must be paid to the basic principle of checking the physical limits.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb12.png|thumb|Figure 12: Example of functions for inflow-dependent discharge]]&lt;br /&gt;
:In this case, three functional dependencies play a part. First, there is a direct dependency between the current inflow and the discharge. The form of the function can be arbitrary. It is possible to reproduce only individual sections of the inflow, which corresponds to a partial approximation of the discharge to the duration curve of the inflow.&lt;br /&gt;
&lt;br /&gt;
:Second, the inflow/discharge function can be superposed with the relationship between storage volume and discharge. For reasons of clarity, it is recommended to work with a normalized function. This makes it possible to influence the result of the inflow/discharge function for each storage volume, which is especially convenient for low filling levels.&lt;br /&gt;
&lt;br /&gt;
:Finally, the required discharge has to be checked with regard to the outlet elements&#039; capacity.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb13.png|thumb|left|Figure 13: Results of different inflow-dependent release strategies]]&lt;br /&gt;
&lt;br /&gt;
:The examples below show how the interaction of different functions affects the discharges. The results are compared in the following figures as inflow and discharge duration lines.&lt;br /&gt;
&lt;br /&gt;
:In the case of a linear relation between inflow and discharge and a constant factor for the storage volume, the duration line of the discharge is a curve corresponding to the inflow reduced by a certain percentage. If the storage volume factor remains constant, the duration line can be changed by varying the inflow/discharge relationship. An additional modification of the factor via the storage volume has the advantage of being able to respond to certain filling levels to prevent the storage from emptying or overflowing.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 7: Influence of Discharges Trough System States==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Rule 7, just as rule 6, is a continuation and generalization of the increase of low water as described in rules 5. Just like a discharge deficit at a cross-section or the storage inflow can influence the discharge, any other system state can. In general terms, this means that a discharge from a storage is triggered, increased, or reduced due to a certain system state. Basically, it is irrelevant where the system state occurs. All measurable variables that influence the transport and storage of water can be considered as system states, e.g. the filling of other storages, discharges, flow regime at a cross-section, a snow depth in the catchment area, current precipitation, or current soil moisture.&lt;br /&gt;
&lt;br /&gt;
:As a requirement to apply those dependencies a detection of the system state is necessary. Practically, this means either that a measuring device must be available to determine needed parameters or the required values are calculated using a mathematical model. Parameters are only considered as snap-shots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:If several system states should influence the discharge, a superposition of the parameters according to a corresponding regulation is necessary.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Mathematically, the influence of system states on the discharge can always be undertaken by scaling. Two functions are necessary for this. The first function describes the relationship between storage volume and discharge. The second one controls the dependency between the system state and a scaling factor. The connection is done by multiplying the discharge with the scaling factor.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb13.5.png|thumb|Transition]]&lt;br /&gt;
&lt;br /&gt;
:A simple example is given by a transition from storage A to storage B. &lt;br /&gt;
&lt;br /&gt;
:The decisive discharge is the transition from A to B. The considered system state is the storage volume of B. It seems obvious that a discharge from A to B is only useful if storage A has sufficient provision and storage B has sufficient capacity to hold additional water. This results in the following simple functions:&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb14.png|thumb|left|Figure 14: Example functions for linking a system state to a discharge]]storage B takes 100% of the discharge from A as long as its filling level does not reach 70% of the maximum volume. Furthermore, it is undesirable to receive additional water for flood protection reasons. The scaling factor decreases from 70% filling level to zero. Starting at a filling level above 50% it becomes increasingly easy to transfer water from Storage A to storage B. The actual transfer, however, only results from the interaction of both functions, taking into account the current filling level of storage B and the scaling derived from it.&lt;br /&gt;
&lt;br /&gt;
:For storage A, the definition of the discharge is in m³/s, while the function for storage B receives a unitless scaling factor. In principle, however, it is possible to exchange the meaning of the functions and to use a unitless function for storage A to scale the desired transfer volume for storage B.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 8: Influencing a Discharge with Balances==&lt;br /&gt;
&lt;br /&gt;
 Dependency: [[Datei:Theorie_Abb15.png|thumb|Figure 15 : Example of long-term monthly averages and moving 30 day averages of storage volumes]]&lt;br /&gt;
:This rule is an extension of rule 7. Instead of using a current state parameter, the balance of a system state is linked to discharge. It is important that there are set time boundaries for carrying out the balance. However, it is irrelevant whether the balance is interpreted as a sum or as an average. A function that displays scaling factors depending on the actual balance can then be used to influence discharges.&lt;br /&gt;
&lt;br /&gt;
:In practice, this form of dependency is often found where water rights define maximum withdrawal volumes per time unit. But the application of a balance is also interesting regarding the long-term behaviour of storage filling levels or inflows. For example, a discharge could be reduced to build up provisions if the inflow of the past winter half-year was below a defined expected value. Another application is the comparison between long-term and current moving averages of storage filling levels. If the current values deviate from the long-term values by a certain amount, the discharge can be reduced or increased to compensate.&lt;br /&gt;
&lt;br /&gt;
:If linking a discharge to several balances is desired, it is possible to superpose several balances (see example at the end of this chapter). &lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb16.png|thumb|Figure 16: Example of a rule for standard discharge]]&lt;br /&gt;
:The influence of the balance on the discharge is posed by two functions according to rule 7. In addition to the already necessary storage volume/discharge function, there is a relation between the balance and scaling factor. The scaling factor is taken from the difference between the actual balance and the expected value.&lt;br /&gt;
&lt;br /&gt;
:The method is demonstrated with a simple example of a standard discharge.&lt;br /&gt;
&lt;br /&gt;
:For storage A, long-term monthly mean values of the storage volumes and derived sliding 30-day mean values of the storage filling levels, as well as the rule for the standard discharge, are known.&lt;br /&gt;
&lt;br /&gt;
:If, for example, on May 1st the average value of the storage volume calculated from the last 30 days amounts to 5.6 million m³ and thus, according to [[:Datei:Theorie_Abb15.png|Fig. 15]], it deviates by 30% from the long-term average value of 8 million m³, a scaling factor of 0.5 results (see [[:Datei:Theorie_Abb16.png|Fig. 16]]). With this value, the standard discharge is reduced and delivers only 0.25m³/s at a current storage filling level of 40%, i.e. 50% less than intended.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb17.png|thumb|left|Abbildung 17: Example functions to link a water balance with a discharge]]The relation between the deviation of the balance and the scaling factor indicates that only starting from a difference greater than 20% a change of the standard discharge takes place. In the case of a decrease of more than 20%, the standard discharge is reduced stepwise. If the actual moving 30-day average exceeds the long-term values by more than 20%, the standard discharge is increased continuously.&lt;br /&gt;
&lt;br /&gt;
:In general, there is also the possibility to extend the relation by superposing and combining several water balances.&lt;br /&gt;
&lt;br /&gt;
:The interaction between water balance and discharge function is explained below.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 9: Priorities for Competing Discharges from a Storage==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb18.png|thumb|Figure 18: Example for assigning priorities via the position of functions]]&lt;br /&gt;
:If there are several discharges from a storage, it can occur that it is not possible to carry out all demanded discharges. In such a case, priorities need to be specified, which determine an order in which discharges are to be satisfied. The order of priorities is often a consequence of political decisions and is not subject to physical conditions.&lt;br /&gt;
&lt;br /&gt;
:However, there are some priorities based on physical conditions. An example is turning off a turbine in times of water shortage in favor of securing the water supply. In practice, operating rules often meet this problem by fulfilling demands up to defined storage volumes, but not maintaining discharges below the set storage volume.&lt;br /&gt;
&lt;br /&gt;
:Another way to describe priorities is to reduce a discharge A exactly by an amount, which is resulting from a second discharge B, with the discharge A never being smaller than zero.&lt;br /&gt;
&lt;br /&gt;
* Practical example:&lt;br /&gt;
:The Wiehl dam gives a good example for the practical operating conditions of a dam. The Wiehl dam serves primarily as a drinking water supply and a means for flood protection, and secondarily for energy production. In addition, a minimum flow of 100 l/s has to be guaranteed downstream of the Wiehl dam. The first priority is the drinking water supply. In order to ensure sufficient water quality in the storage, additional discharges used for energy production are stopped when the storage volume falls below 70% of the total volume. As both the minimum discharge and the turbine discharge leave into the Wiehl, it would also be uncalled-for to maintain the minimum discharge if water was simultaneously discharged through the turbine. This results in a reduction of a discharge A (minimum discharge) by the amount of discharge B (turbine) as described above &amp;lt;ref name=&amp;quot;Aggerverband_1999&amp;quot;&amp;gt;&#039;&#039;&#039;Aggerverband&#039;&#039;&#039; (1999): Hydrologische Sicherheit der Genkel- und Aggertalsperre. Gutachten des Fachgebietes Ingenieurhydrologie und Wasserbewirtschaftung, TU Darmstadt&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb19.png|thumb||Figure 19: Example of a relation between two discharges]]&lt;br /&gt;
:Assuming that for each use, following the above rules, a functional dependency between storage content and discharge exists, a ranking of several uses is already given by the position of the function&#039;s nodes.  Then, the respective storage volume from which the target discharge is no longer covered to 100% or even reduced to zero is decisive.&lt;br /&gt;
&lt;br /&gt;
:In the example, the ranking of the uses is clearly visible. First, the turbine is switched off, then the increase of low water refrained from until only the discharge covering the water supply remains.&lt;br /&gt;
&lt;br /&gt;
:In addition, it is possible to directly compare two or more discharges. Such a rule could be:&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;If discharge B &amp;gt; 0 and the storage volume S &amp;lt; X, then reduce discharge A by the amount of discharge B, with discharge  A not being smaller than zero.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:This means that a linear dependency exists between A and B until B is equal to the value of A. If B increases further, A remains constantly zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 11: Water Distribution==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:If there is the need to distribute water within a water resources system, a distribution rule must be defined.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb19.5.png|thumb|Diversion]]&lt;br /&gt;
&lt;br /&gt;
:Two types of diversions can occur:&lt;br /&gt;
:# Diversion that exclusively follows hydraulic laws &lt;br /&gt;
:# Adjustable diversions &lt;br /&gt;
&lt;br /&gt;
:In both cases, relations can always be defined as a function of the inflow. In the second case, these distribution rules represent an operating rule, since they directly influence the transport and storage behavior of water. The number of discharges is basically not limited. The difference to transitions at dams is that in this case no storage volume can be used as a reference value.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb20.png|thumb|Figure 20 :Example of assignment functions for multiple sequences]]&lt;br /&gt;
&lt;br /&gt;
* Practical example: &lt;br /&gt;
:The water supply of Windhoek, the capital of Namibia, is provided by three dams. However, the water withdrawal for the drinking water supply is only possible from one dam - the Von Bach Dam. The remaining two storages are connected to the main dam by pipes. However, the volume transferred between Swakopport Dam and Von Bach Dam is not exclusively available for refilling the Von Bach Dam, but also serves to supply the town of Karibib with drinking water.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb21.png|thumb|left|Fig. 21: Example of a threshold concept for a division into two flows]]For the definition of division rules, functions depending on the current inflow are an appropriate representation. Thus, both a hydraulic description and a description serving the management of the storage are possible. For each discharge leaving the diversion structure, a distribution function has to be specified. If the functions are to be variable, scaling is recommended.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb22.png|thumb|Figure 22: Example of a threshold concept with a distribution to serve several users&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
:If the distribution functions cannot be pre-defined, but the discharge volumes rather result later from demand calculations, then a threshold concept is suitable, which in turn can work with scaling factors. The threshold is scaled by a factor and is therefore variable. As long as the inflow is lower than the threshold, the entire inflow is used to satisfy the demand. Only when the current inflow exceeds the threshold, the remaining amount is discharged.&lt;br /&gt;
&lt;br /&gt;
:If a division into more than two discharges is necessary, the threshold concept can be successively applied several times. The order of the discharges determines the priorities of the water distribution.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Literature==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/57/en&amp;diff=12995</id>
		<title>Translations:Betriebsregeltypen/57/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/57/en&amp;diff=12995"/>
		<updated>2021-08-30T10:47:13Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;:[[Datei:Theorie_Abb14.png|thumb|left|Figure 14: Example functions for linking a system state to a discharge]]storage B takes 100% of the discharge from A as long as its filling level does not reach 70% of the maximum volume. Furthermore, it is undesirable to receive additional water for flood protection reasons. The scaling factor decreases from 70% filling level to zero. Starting at a filling level above 50% it becomes increasingly easy to transfer water from Storage A to storage B. The actual transfer, however, only results from the interaction of both functions, taking into account the current filling level of storage B and the scaling derived from it.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12994</id>
		<title>Betriebsregeltypen/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12994"/>
		<updated>2021-08-30T10:46:21Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=|hoch=Betriebsregelkonzept|nachher=Abstraktion der Betriebsregeln}}&lt;br /&gt;
&lt;br /&gt;
The operating plan of a dam or a storage network is part of the official approval of plans and usually is available as a report or presentation. Its complexity can vary: it ranges from simply defining flood protection areas and setting a report and alarm plan to notify the supervisory authorities in exceptional situations to complex sets of rules concerning functional dependencies that derive discharges from varying system states.&lt;br /&gt;
&lt;br /&gt;
As follows, principles to clarify the variety of possible regulations and reduce them to essential dependencies are presented. A concept is derived to represent most operating rules by a few basic calculation rules. The given selection does not claim to be complete, but it is likely to contain the rules applied in practice.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Basic Principle: Verification of Physical Limits==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb1.png|thumb|Figure 1: Dependency on storage capacity]]&lt;br /&gt;
&lt;br /&gt;
When specifying discharges according to an operating rule, it is assumed that the outlet capacity is sufficient to meet these discharges. Thus, dimensioning the outlet element must consider the operating requirements. In principle, the physically possible discharge, given by the outlet&#039;s characteristic curve at full opening, sets the upper limit value.&lt;br /&gt;
&lt;br /&gt;
If the pressure level or the outlet capacity is sufficient to discharge the desired quantity when fully opened, the discharge can be throttled to the intended level by closing a slide. If the pressure level is insufficient, only the hydraulically possible discharge can be discharged.&lt;br /&gt;
&lt;br /&gt;
*Mathematical abstraction:&lt;br /&gt;
:All outlets obeying an operating rule are functions of the storage&#039;s volume and cannot exceed the outlets&#039; maximum capacity when fully opened. As soon as the capacity of the outlets exceeds the required discharge, it can be adjusted by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
All discharge types from storages mentioned below are subject to this restriction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 1: Definition of a Minimum Output or a Safely Dischargeable Maximum Output==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb2.png|thumb|Figure 2: Example for minimum and maximum discharge as a function of storage capacity]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The specification of a minimum or maximum discharge is based on requirements downstream of a storage. The maximal discharge is based on the discharge respective to a critical, downstream cross-section. Consequently, a hydraulic method exists for its determination. In contrast, there is no clear guideline for the minimum discharge. Often, ratios of MNQ or MQ are used. Independent of determining the minimum or maximum discharge, the basic principle to verify outlet elements&#039; physical limits is applied. So, minimum and maximum discharge can only be discharged if the outlet capacity is sufficient at the given pressure level. Since, in reality, it is unlikely that the dimensioning of the outlet elements and the required discharge are conflicting, the reference to the dependence on the storage capacity content is rather theoretical but necessary to derive general laws.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Minimum and maximum discharge are functions of the storage volume and follow the characteristic curve of fully opened outlets at a low filling level. As soon as the outlet elements&#039; capacity is sufficient for the required discharge volume, the discharge can be kept constant by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 2: Maintaining a Flood Protection Area, Possibly Timely Variable Over the Year==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb3.png|thumb|Figure 3: Example of a function to maintain a flood protection area]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The definition of a flood protection area as a minimum requirement only includes the designation of a volume, which has to be kept free for potential floodwater. The dimensioning is based on flood events with certain recurrence intervals. If the water level exceeds the mark of the protection area, an increased discharge to the downstream water of the storage ensures that the area is kept empty. Thus, this rule is reduced to a relation between discharge and storage volume, where the outlet capacity or a defined maximum discharge can serve as an upper limit for keeping the flood protection area empty. If the flood protection area is variable in time over the year, only the discharge of the respective storage volume is increased.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:There is a direct relation between storage capacity and release. If the storage capacity exceeds the mark of the flood protection area, a discharge occurs. If it remains below the mark, the discharge is set to zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 3: Direct Withdrawals from a storage for Drinking or Service Water ==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb4.png|thumb|Figure 4: Example of a function for drinking or raw water withdrawal]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Primarily, the current demand determines the volume of withdrawals from the storage, but it is also subject to temporal variations. The upper limits for withdrawals are generally set by water rights or defined maximum withdrawal volumes, which refer to selected periods such as a day, a month, a quarter, or a year. Initially, one only considers the current demand communicated by water suppliers, which constitutes a claim towards the storage. There is no connection to the actual storage and the respective storage volume.&lt;br /&gt;
:Whether the demand can be pleased by withdrawing water from the storage is determined by the actual storage volumes. To connect the water demand to the actual storage volumes, the structural implementation of withdrawal elements and means of anticipatory management are taken into account. For example, if particularly low storage volumes are reached, it is advisable to throttle withdrawals in advance to avoid the storage running empty and then completely failing at covering the demand during prolonged periods of low water &amp;lt;ref name=&amp;quot;Schultz_1989&amp;quot;&amp;gt;&#039;&#039;&#039;Schultz, G.A.&#039;&#039;&#039; (1989): Entwicklung von Betriebsregeln für die Wupper-Talsperre in Niedrig- und Hochwasserzeiten. Wasserwirtschaft 79 (7/8) S. 340-343&amp;lt;/ref&amp;gt;. Hence, there is usually space reserved in a dam specifically used for drinking water supply. Its use is handled separately in respective operating plans.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:If the demand is exactly known and unchangeable, a direct relation between withdrawal and storage volume can be defined. However, the demand is subject to certain variations. For this reason, it is recommended to normalize the relationship between withdrawals and storage volume, where the current demand serves as a scaling factor. If the storage volume falls below a defined limit value, only a certain percentage of the current demand is satisfied. The limit value, as well as the form of the function, can be variable in time.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 4: Standard Discharge to Downstream Water==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb5.png|thumb|Figure 5: Pool-based operating plan in a two-dimensional representation]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The normal discharge to the downstream water should provide a discharge compensation for seasonal differences in the inflow. If a minimum discharge is required, it will be included in the normal discharge. A pool-based operating plan is used to describe the normal discharge. It divides the storage capacity into different areas and assigns a discharge to each pool-based operation. When determining the pool-based operating plan, the long-term discharge and other withdrawals from the storage for other purposes play a decisive role. A storage should collect water in periods of high inflow but still not overflow to have sufficient reserves in periods of low inflow. The coupling of the releases to the storage pool-based operation is a function of the storage volume. Since the system is supposed to react to variations of inflow during the year, the relationship between storage volume and discharge is usually variable over time.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb6.png|thumb|Figure 6: Comparison of a pool-based operating plan in a two- and three-dimensional representation]] Like for the previous rules, the output depends on the storage volume. Usually, a pool-based operating plan is displayed in two-dimensional diagrams. The X-axis shows the time of one year, while the Y-axis shows the storage capacity. Pool-based operations are depicted as lines of equal outputs.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb7.png|thumb|Figure 7: Pool-based operating plan with linear interpolation between successive time reference points]]This view is practical but not yet complete: A three-dimensional representation of a simple pool-based operating plan makes this clear. On the X-axis is the time, on the Y-axis the storage capacity is plotted, while the Z-axis shows the output directed upwards.&lt;br /&gt;
&lt;br /&gt;
:The 3D image viewed from above gives the two-dimensional shape. Instead of taking constant blocks for the individual time horizons, a linear connection is also used often.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb8.png|thumb|Figure 8: Pool-based operating plan with two types of interpretation (selected month of May)]]For the individual periods - here months - different functional dependencies between storage capacity and outflow are considered. If the storage volume/discharge relation is also considered for a selected point in time, there are two possibilities to connect the discharge nodes. On the one hand, there is the possibility of linear interpolation, and on the other hand, a step function is possible.&lt;br /&gt;
&lt;br /&gt;
:In two-dimensional space, this information is not visible and must be specified separately. However, there is usually the convention to assume that the output between two nodes is constant, i.e. to interpret the pool-based operating plan as shown above in the form of steps.&amp;lt;br clear=&amp;quot;all&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 5: Maintaining Defined Discharges to Downstream Waters (Increase of Low Water / Coverage of Demand)==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb9.png|thumb|Figure 9: Example of a function between shortfalls and scaling factors for a storage&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
* Dependency: &lt;br /&gt;
:In this case, the current discharge is determined by conditions downstream of a storage. At a cross-section of a water resources system, the so-called &#039;&#039;control point&#039;&#039;, where the flow is dependent on the discharge from the upstream storage, a minimum flow is defined. The flow at the control point is composed of the discharge from upstream storages and the lateral inflows between the storages and the control point. If the current flow remains below the set minimum, an additional discharge from upstream storages is necessary. The volume of the additional discharge depends on the difference between the previously defined target flow and the actual flow. Whether the required discharge can be fully provided from the storage depends on the currently available stored volumes in the storage. The lower the level, the less favorable it is to provide additional water. In this context, the increase of low water/coverage of demand behaves completely identical to the drinking or service water withdrawal, with only the triggering factor differing. As mentioned before, a storage-dependent function is scaled by a factor, but this factor is now derived from a comparison between set values and current discharges.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:The determination of the additionally needed discharge is composed of several factors. Firstly, a volumetrically varying shortfall of water results from failing the target discharge. The shortfall of water is then implemented as a scaling factor to the discharge which can be defined by a function. The shortfall of water functions independently, while the scaling factor functions dependently.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb10.png|thumb|Figure 10: Example of a function for increasing low water levels or meeting demand]]&lt;br /&gt;
&lt;br /&gt;
:Secondly, it depends on the actual storage volume, if and how an additional discharge from the storage can be met. A normalized volume-dependent function and the needed discharge lead to a clear determination of the additional discharge volumes. The following [[:Datei:Theorie_Abb10.png||Fig. 10]] shows an example, where the complete provision of an increased target can only be achieved if the filling level of the storage is above a critical limit (25%).&lt;br /&gt;
&lt;br /&gt;
:If more than one storage has an influence on the relevant control point or if, in principle, more than one storage facility is to be used to meet the demand, the required additional discharge is to be divided between the storages in accordance with the corresponding regulations. A distinction must be made between the direct and indirect influences of a storage on the control point. A direct influence is present if a discharge can have a direct effect on the flow conditions at the control point, i.e. the natural flow between the storage &lt;br /&gt;
and the control point can no longer be changed by regulation. If this is not the case, an indirect influence is given.&lt;br /&gt;
&lt;br /&gt;
:All storages with a direct influence on the control point receive a shortfall factor and a volume-dependent, scalable function according to [[:Datei:Theorie_Abb10.png|Figure 10]]. Thus, depending on the shortfall quantities and the storage capacity, the actual discharge can be determined separately for each storage.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 6: Discharge Depending on the storage Inflow==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb11.png|thumb|Figure 11: Direct dependency between storage and control point]]&lt;br /&gt;
:There is a direct dependency between the discharge from the storage and the current inflow to the storage. Similar to the pool-based operating plan, there is also an adaptation to different inflow situations. This is done to prevent depletion or overflowing or to obtain a variable discharge regime downstream. However, long-term inflow fluctuations are difficult to detect with this operating rule, since the observations are only carried out as snapshots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:To determine an inflow-dependent discharge, several components have to be considered. First of all, a relation between the current inflow and discharge must be defined. In addition to the current inflow, the current storage volume is important, because the relation inflow/outflow must not be valid for every filling level. Thus it is likely that the relation is ceded completely or the release quantities are adjusted if the storage level falls below a critical level.&lt;br /&gt;
&lt;br /&gt;
:As this rule can lead to the co-occurrence of relatively small storage volumes and high inflows resulting in high discharge volumes, special attention must be paid to the basic principle of checking the physical limits.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb12.png|thumb|Figure 12: Example of functions for inflow-dependent discharge]]&lt;br /&gt;
:In this case, three functional dependencies play a part. First, there is a direct dependency between the current inflow and the discharge. The form of the function can be arbitrary. It is possible to reproduce only individual sections of the inflow, which corresponds to a partial approximation of the discharge to the duration curve of the inflow.&lt;br /&gt;
&lt;br /&gt;
:Second, the inflow/discharge function can be superposed with the relationship between storage volume and discharge. For reasons of clarity, it is recommended to work with a normalized function. This makes it possible to influence the result of the inflow/discharge function for each storage volume, which is especially convenient for low filling levels.&lt;br /&gt;
&lt;br /&gt;
:Finally, the required discharge has to be checked with regard to the outlet elements&#039; capacity.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb13.png|thumb|left|Figure 13: Results of different inflow-dependent release strategies]]&lt;br /&gt;
&lt;br /&gt;
:The examples below show how the interaction of different functions affects the discharges. The results are compared in the following figures as inflow and discharge duration lines.&lt;br /&gt;
&lt;br /&gt;
:In the case of a linear relation between inflow and discharge and a constant factor for the storage volume, the duration line of the discharge is a curve corresponding to the inflow reduced by a certain percentage. If the storage volume factor remains constant, the duration line can be changed by varying the inflow/discharge relationship. An additional modification of the factor via the storage volume has the advantage of being able to respond to certain filling levels to prevent the storage from emptying or overflowing.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 7: Influence of Discharges Trough System States==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Rule 7, just as rule 6, is a continuation and generalization of the increase of low water as described in rules 5. Just like a discharge deficit at a cross-section or the storage inflow can influence the discharge, any other system state can. In general terms, this means that a discharge from a storage is triggered, increased, or reduced due to a certain system state. Basically, it is irrelevant where the system state occurs. All measurable variables that influence the transport and storage of water can be considered as system states, e.g. the filling of other storages, discharges, flow regime at a cross-section, a snow depth in the catchment area, current precipitation, or current soil moisture.&lt;br /&gt;
&lt;br /&gt;
:As a requirement to apply those dependencies a detection of the system state is necessary. Practically, this means either that a measuring device must be available to determine needed parameters or the required values are calculated using a mathematical model. Parameters are only considered as snap-shots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:If several system states should influence the discharge, a superposition of the parameters according to a corresponding regulation is necessary.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Mathematically, the influence of system states on the discharge can always be undertaken by scaling. Two functions are necessary for this. The first function describes the relationship between storage volume and discharge. The second one controls the dependency between the system state and a scaling factor. The connection is done by multiplying the discharge with the scaling factor.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb13.5.png|thumb|Transition]]&lt;br /&gt;
&lt;br /&gt;
:A simple example is given by a transition from storage A to storage B. &lt;br /&gt;
&lt;br /&gt;
:The decisive discharge is the transition from A to B. The considered system state is the storage volume of B. It seems obvious that a discharge from A to B is only useful if storage A has sufficient provision and storage B has sufficient capacity to hold additional water. This results in the following simple functions:&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb14.png|thumb|left|Figure 14: Example functions for linking a system state to a discharge]]Reservoir B takes 100% of the discharge from A as long as its filling level does not reach 70% of the maximum volume. Furthermore, it is undesirable to receive additional water for flood protection reasons. The scaling factor decreases from 70% filling level to zero. Starting at a filling level above 50% it becomes increasingly easy to transfer water from Reservoir A to reservoir B. The actual transfer, however, only results from the interaction of both functions, taking into account the current filling level of reservoir B and the scaling derived from it.&lt;br /&gt;
&lt;br /&gt;
:For storage A, the definition of the discharge is in m³/s, while the function for storage B receives a unitless scaling factor. In principle, however, it is possible to exchange the meaning of the functions and to use a unitless function for storage A to scale the desired transfer volume for storage B.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 8: Influencing a Discharge with Balances==&lt;br /&gt;
&lt;br /&gt;
 Dependency: [[Datei:Theorie_Abb15.png|thumb|Figure 15 : Example of long-term monthly averages and moving 30 day averages of storage volumes]]&lt;br /&gt;
:This rule is an extension of rule 7. Instead of using a current state parameter, the balance of a system state is linked to discharge. It is important that there are set time boundaries for carrying out the balance. However, it is irrelevant whether the balance is interpreted as a sum or as an average. A function that displays scaling factors depending on the actual balance can then be used to influence discharges.&lt;br /&gt;
&lt;br /&gt;
:In practice, this form of dependency is often found where water rights define maximum withdrawal volumes per time unit. But the application of a balance is also interesting regarding the long-term behaviour of storage filling levels or inflows. For example, a discharge could be reduced to build up provisions if the inflow of the past winter half-year was below a defined expected value. Another application is the comparison between long-term and current moving averages of storage filling levels. If the current values deviate from the long-term values by a certain amount, the discharge can be reduced or increased to compensate.&lt;br /&gt;
&lt;br /&gt;
:If linking a discharge to several balances is desired, it is possible to superpose several balances (see example at the end of this chapter). &lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb16.png|thumb|Figure 16: Example of a rule for standard discharge]]&lt;br /&gt;
:The influence of the balance on the discharge is posed by two functions according to rule 7. In addition to the already necessary storage volume/discharge function, there is a relation between the balance and scaling factor. The scaling factor is taken from the difference between the actual balance and the expected value.&lt;br /&gt;
&lt;br /&gt;
:The method is demonstrated with a simple example of a standard discharge.&lt;br /&gt;
&lt;br /&gt;
:For storage A, long-term monthly mean values of the storage volumes and derived sliding 30-day mean values of the storage filling levels, as well as the rule for the standard discharge, are known.&lt;br /&gt;
&lt;br /&gt;
:If, for example, on May 1st the average value of the storage volume calculated from the last 30 days amounts to 5.6 million m³ and thus, according to [[:Datei:Theorie_Abb15.png|Fig. 15]], it deviates by 30% from the long-term average value of 8 million m³, a scaling factor of 0.5 results (see [[:Datei:Theorie_Abb16.png|Fig. 16]]). With this value, the standard discharge is reduced and delivers only 0.25m³/s at a current storage filling level of 40%, i.e. 50% less than intended.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb17.png|thumb|left|Abbildung 17: Example functions to link a water balance with a discharge]]The relation between the deviation of the balance and the scaling factor indicates that only starting from a difference greater than 20% a change of the standard discharge takes place. In the case of a decrease of more than 20%, the standard discharge is reduced stepwise. If the actual moving 30-day average exceeds the long-term values by more than 20%, the standard discharge is increased continuously.&lt;br /&gt;
&lt;br /&gt;
:In general, there is also the possibility to extend the relation by superposing and combining several water balances.&lt;br /&gt;
&lt;br /&gt;
:The interaction between water balance and discharge function is explained below.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 9: Priorities for Competing Discharges from a Storage==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb18.png|thumb|Figure 18: Example for assigning priorities via the position of functions]]&lt;br /&gt;
:If there are several discharges from a storage, it can occur that it is not possible to carry out all demanded discharges. In such a case, priorities need to be specified, which determine an order in which discharges are to be satisfied. The order of priorities is often a consequence of political decisions and is not subject to physical conditions.&lt;br /&gt;
&lt;br /&gt;
:However, there are some priorities based on physical conditions. An example is turning off a turbine in times of water shortage in favor of securing the water supply. In practice, operating rules often meet this problem by fulfilling demands up to defined storage volumes, but not maintaining discharges below the set storage volume.&lt;br /&gt;
&lt;br /&gt;
:Another way to describe priorities is to reduce a discharge A exactly by an amount, which is resulting from a second discharge B, with the discharge A never being smaller than zero.&lt;br /&gt;
&lt;br /&gt;
* Practical example:&lt;br /&gt;
:The Wiehl dam gives a good example for the practical operating conditions of a dam. The Wiehl dam serves primarily as a drinking water supply and a means for flood protection, and secondarily for energy production. In addition, a minimum flow of 100 l/s has to be guaranteed downstream of the Wiehl dam. The first priority is the drinking water supply. In order to ensure sufficient water quality in the storage, additional discharges used for energy production are stopped when the storage volume falls below 70% of the total volume. As both the minimum discharge and the turbine discharge leave into the Wiehl, it would also be uncalled-for to maintain the minimum discharge if water was simultaneously discharged through the turbine. This results in a reduction of a discharge A (minimum discharge) by the amount of discharge B (turbine) as described above &amp;lt;ref name=&amp;quot;Aggerverband_1999&amp;quot;&amp;gt;&#039;&#039;&#039;Aggerverband&#039;&#039;&#039; (1999): Hydrologische Sicherheit der Genkel- und Aggertalsperre. Gutachten des Fachgebietes Ingenieurhydrologie und Wasserbewirtschaftung, TU Darmstadt&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb19.png|thumb||Figure 19: Example of a relation between two discharges]]&lt;br /&gt;
:Assuming that for each use, following the above rules, a functional dependency between storage content and discharge exists, a ranking of several uses is already given by the position of the function&#039;s nodes.  Then, the respective storage volume from which the target discharge is no longer covered to 100% or even reduced to zero is decisive.&lt;br /&gt;
&lt;br /&gt;
:In the example, the ranking of the uses is clearly visible. First, the turbine is switched off, then the increase of low water refrained from until only the discharge covering the water supply remains.&lt;br /&gt;
&lt;br /&gt;
:In addition, it is possible to directly compare two or more discharges. Such a rule could be:&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;If discharge B &amp;gt; 0 and the storage volume S &amp;lt; X, then reduce discharge A by the amount of discharge B, with discharge  A not being smaller than zero.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:This means that a linear dependency exists between A and B until B is equal to the value of A. If B increases further, A remains constantly zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 11: Water Distribution==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:If there is the need to distribute water within a water resources system, a distribution rule must be defined.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb19.5.png|thumb|Diversion]]&lt;br /&gt;
&lt;br /&gt;
:Two types of diversions can occur:&lt;br /&gt;
:# Diversion that exclusively follows hydraulic laws &lt;br /&gt;
:# Adjustable diversions &lt;br /&gt;
&lt;br /&gt;
:In both cases, relations can always be defined as a function of the inflow. In the second case, these distribution rules represent an operating rule, since they directly influence the transport and storage behavior of water. The number of discharges is basically not limited. The difference to transitions at dams is that in this case no storage volume can be used as a reference value.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb20.png|thumb|Figure 20 :Example of assignment functions for multiple sequences]]&lt;br /&gt;
&lt;br /&gt;
* Practical example: &lt;br /&gt;
:The water supply of Windhoek, the capital of Namibia, is provided by three dams. However, the water withdrawal for the drinking water supply is only possible from one dam - the Von Bach Dam. The remaining two storages are connected to the main dam by pipes. However, the volume transferred between Swakopport Dam and Von Bach Dam is not exclusively available for refilling the Von Bach Dam, but also serves to supply the town of Karibib with drinking water.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb21.png|thumb|left|Fig. 21: Example of a threshold concept for a division into two flows]]For the definition of division rules, functions depending on the current inflow are an appropriate representation. Thus, both a hydraulic description and a description serving the management of the storage are possible. For each discharge leaving the diversion structure, a distribution function has to be specified. If the functions are to be variable, scaling is recommended.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb22.png|thumb|Figure 22: Example of a threshold concept with a distribution to serve several users&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
:If the distribution functions cannot be pre-defined, but the discharge volumes rather result later from demand calculations, then a threshold concept is suitable, which in turn can work with scaling factors. The threshold is scaled by a factor and is therefore variable. As long as the inflow is lower than the threshold, the entire inflow is used to satisfy the demand. Only when the current inflow exceeds the threshold, the remaining amount is discharged.&lt;br /&gt;
&lt;br /&gt;
:If a division into more than two discharges is necessary, the threshold concept can be successively applied several times. The order of the discharges determines the priorities of the water distribution.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Literature==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/24/en&amp;diff=12993</id>
		<title>Translations:Betriebsregeltypen/24/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/24/en&amp;diff=12993"/>
		<updated>2021-08-30T10:46:20Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* Dependency:&lt;br /&gt;
:The normal discharge to the downstream water should provide a discharge compensation for seasonal differences in the inflow. If a minimum discharge is required, it will be included in the normal discharge. A pool-based operating plan is used to describe the normal discharge. It divides the storage capacity into different areas and assigns a discharge to each pool-based operation. When determining the pool-based operating plan, the long-term discharge and other withdrawals from the storage for other purposes play a decisive role. A storage should collect water in periods of high inflow but still not overflow to have sufficient reserves in periods of low inflow. The coupling of the releases to the storage pool-based operation is a function of the storage volume. Since the system is supposed to react to variations of inflow during the year, the relationship between storage volume and discharge is usually variable over time.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12992</id>
		<title>Betriebsregeltypen/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12992"/>
		<updated>2021-08-30T10:46:03Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=|hoch=Betriebsregelkonzept|nachher=Abstraktion der Betriebsregeln}}&lt;br /&gt;
&lt;br /&gt;
The operating plan of a dam or a storage network is part of the official approval of plans and usually is available as a report or presentation. Its complexity can vary: it ranges from simply defining flood protection areas and setting a report and alarm plan to notify the supervisory authorities in exceptional situations to complex sets of rules concerning functional dependencies that derive discharges from varying system states.&lt;br /&gt;
&lt;br /&gt;
As follows, principles to clarify the variety of possible regulations and reduce them to essential dependencies are presented. A concept is derived to represent most operating rules by a few basic calculation rules. The given selection does not claim to be complete, but it is likely to contain the rules applied in practice.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Basic Principle: Verification of Physical Limits==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb1.png|thumb|Figure 1: Dependency on storage capacity]]&lt;br /&gt;
&lt;br /&gt;
When specifying discharges according to an operating rule, it is assumed that the outlet capacity is sufficient to meet these discharges. Thus, dimensioning the outlet element must consider the operating requirements. In principle, the physically possible discharge, given by the outlet&#039;s characteristic curve at full opening, sets the upper limit value.&lt;br /&gt;
&lt;br /&gt;
If the pressure level or the outlet capacity is sufficient to discharge the desired quantity when fully opened, the discharge can be throttled to the intended level by closing a slide. If the pressure level is insufficient, only the hydraulically possible discharge can be discharged.&lt;br /&gt;
&lt;br /&gt;
*Mathematical abstraction:&lt;br /&gt;
:All outlets obeying an operating rule are functions of the storage&#039;s volume and cannot exceed the outlets&#039; maximum capacity when fully opened. As soon as the capacity of the outlets exceeds the required discharge, it can be adjusted by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
All discharge types from storages mentioned below are subject to this restriction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 1: Definition of a Minimum Output or a Safely Dischargeable Maximum Output==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb2.png|thumb|Figure 2: Example for minimum and maximum discharge as a function of storage capacity]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The specification of a minimum or maximum discharge is based on requirements downstream of a storage. The maximal discharge is based on the discharge respective to a critical, downstream cross-section. Consequently, a hydraulic method exists for its determination. In contrast, there is no clear guideline for the minimum discharge. Often, ratios of MNQ or MQ are used. Independent of determining the minimum or maximum discharge, the basic principle to verify outlet elements&#039; physical limits is applied. So, minimum and maximum discharge can only be discharged if the outlet capacity is sufficient at the given pressure level. Since, in reality, it is unlikely that the dimensioning of the outlet elements and the required discharge are conflicting, the reference to the dependence on the storage capacity content is rather theoretical but necessary to derive general laws.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Minimum and maximum discharge are functions of the storage volume and follow the characteristic curve of fully opened outlets at a low filling level. As soon as the outlet elements&#039; capacity is sufficient for the required discharge volume, the discharge can be kept constant by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 2: Maintaining a Flood Protection Area, Possibly Timely Variable Over the Year==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb3.png|thumb|Figure 3: Example of a function to maintain a flood protection area]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The definition of a flood protection area as a minimum requirement only includes the designation of a volume, which has to be kept free for potential floodwater. The dimensioning is based on flood events with certain recurrence intervals. If the water level exceeds the mark of the protection area, an increased discharge to the downstream water of the storage ensures that the area is kept empty. Thus, this rule is reduced to a relation between discharge and storage volume, where the outlet capacity or a defined maximum discharge can serve as an upper limit for keeping the flood protection area empty. If the flood protection area is variable in time over the year, only the discharge of the respective storage volume is increased.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:There is a direct relation between storage capacity and release. If the storage capacity exceeds the mark of the flood protection area, a discharge occurs. If it remains below the mark, the discharge is set to zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 3: Direct Withdrawals from a storage for Drinking or Service Water ==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb4.png|thumb|Figure 4: Example of a function for drinking or raw water withdrawal]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Primarily, the current demand determines the volume of withdrawals from the storage, but it is also subject to temporal variations. The upper limits for withdrawals are generally set by water rights or defined maximum withdrawal volumes, which refer to selected periods such as a day, a month, a quarter, or a year. Initially, one only considers the current demand communicated by water suppliers, which constitutes a claim towards the storage. There is no connection to the actual storage and the respective storage volume.&lt;br /&gt;
:Whether the demand can be pleased by withdrawing water from the storage is determined by the actual storage volumes. To connect the water demand to the actual storage volumes, the structural implementation of withdrawal elements and means of anticipatory management are taken into account. For example, if particularly low storage volumes are reached, it is advisable to throttle withdrawals in advance to avoid the storage running empty and then completely failing at covering the demand during prolonged periods of low water &amp;lt;ref name=&amp;quot;Schultz_1989&amp;quot;&amp;gt;&#039;&#039;&#039;Schultz, G.A.&#039;&#039;&#039; (1989): Entwicklung von Betriebsregeln für die Wupper-Talsperre in Niedrig- und Hochwasserzeiten. Wasserwirtschaft 79 (7/8) S. 340-343&amp;lt;/ref&amp;gt;. Hence, there is usually space reserved in a dam specifically used for drinking water supply. Its use is handled separately in respective operating plans.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:If the demand is exactly known and unchangeable, a direct relation between withdrawal and storage volume can be defined. However, the demand is subject to certain variations. For this reason, it is recommended to normalize the relationship between withdrawals and storage volume, where the current demand serves as a scaling factor. If the storage volume falls below a defined limit value, only a certain percentage of the current demand is satisfied. The limit value, as well as the form of the function, can be variable in time.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 4: Standard Discharge to Downstream Water==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb5.png|thumb|Figure 5: Pool-based operating plan in a two-dimensional representation]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The normal discharge to the downstream water should provide a discharge compensation for seasonal differences in the inflow. If a minimum discharge is required, it will be included in the normal discharge. A pool-based operating plan is used to describe the normal discharge. It divides the storage capacity into different areas and assigns a discharge to each pool-based operation. When determining the pool-based operating plan, the long-term discharge and other withdrawals from the reservoir for other purposes play a decisive role. A reservoir should collect water in periods of high inflow but still not overflow to have sufficient reserves in periods of low inflow. The coupling of the releases to the storage pool-based operation is a function of the storage volume. Since the system is supposed to react to variations of inflow during the year, the relationship between storage volume and discharge is usually variable over time.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb6.png|thumb|Figure 6: Comparison of a pool-based operating plan in a two- and three-dimensional representation]] Like for the previous rules, the output depends on the storage volume. Usually, a pool-based operating plan is displayed in two-dimensional diagrams. The X-axis shows the time of one year, while the Y-axis shows the storage capacity. Pool-based operations are depicted as lines of equal outputs.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb7.png|thumb|Figure 7: Pool-based operating plan with linear interpolation between successive time reference points]]This view is practical but not yet complete: A three-dimensional representation of a simple pool-based operating plan makes this clear. On the X-axis is the time, on the Y-axis the storage capacity is plotted, while the Z-axis shows the output directed upwards.&lt;br /&gt;
&lt;br /&gt;
:The 3D image viewed from above gives the two-dimensional shape. Instead of taking constant blocks for the individual time horizons, a linear connection is also used often.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb8.png|thumb|Figure 8: Pool-based operating plan with two types of interpretation (selected month of May)]]For the individual periods - here months - different functional dependencies between storage capacity and outflow are considered. If the storage volume/discharge relation is also considered for a selected point in time, there are two possibilities to connect the discharge nodes. On the one hand, there is the possibility of linear interpolation, and on the other hand, a step function is possible.&lt;br /&gt;
&lt;br /&gt;
:In two-dimensional space, this information is not visible and must be specified separately. However, there is usually the convention to assume that the output between two nodes is constant, i.e. to interpret the pool-based operating plan as shown above in the form of steps.&amp;lt;br clear=&amp;quot;all&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 5: Maintaining Defined Discharges to Downstream Waters (Increase of Low Water / Coverage of Demand)==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb9.png|thumb|Figure 9: Example of a function between shortfalls and scaling factors for a storage&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
* Dependency: &lt;br /&gt;
:In this case, the current discharge is determined by conditions downstream of a storage. At a cross-section of a water resources system, the so-called &#039;&#039;control point&#039;&#039;, where the flow is dependent on the discharge from the upstream storage, a minimum flow is defined. The flow at the control point is composed of the discharge from upstream storages and the lateral inflows between the storages and the control point. If the current flow remains below the set minimum, an additional discharge from upstream storages is necessary. The volume of the additional discharge depends on the difference between the previously defined target flow and the actual flow. Whether the required discharge can be fully provided from the storage depends on the currently available stored volumes in the storage. The lower the level, the less favorable it is to provide additional water. In this context, the increase of low water/coverage of demand behaves completely identical to the drinking or service water withdrawal, with only the triggering factor differing. As mentioned before, a storage-dependent function is scaled by a factor, but this factor is now derived from a comparison between set values and current discharges.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:The determination of the additionally needed discharge is composed of several factors. Firstly, a volumetrically varying shortfall of water results from failing the target discharge. The shortfall of water is then implemented as a scaling factor to the discharge which can be defined by a function. The shortfall of water functions independently, while the scaling factor functions dependently.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb10.png|thumb|Figure 10: Example of a function for increasing low water levels or meeting demand]]&lt;br /&gt;
&lt;br /&gt;
:Secondly, it depends on the actual storage volume, if and how an additional discharge from the storage can be met. A normalized volume-dependent function and the needed discharge lead to a clear determination of the additional discharge volumes. The following [[:Datei:Theorie_Abb10.png||Fig. 10]] shows an example, where the complete provision of an increased target can only be achieved if the filling level of the storage is above a critical limit (25%).&lt;br /&gt;
&lt;br /&gt;
:If more than one storage has an influence on the relevant control point or if, in principle, more than one storage facility is to be used to meet the demand, the required additional discharge is to be divided between the storages in accordance with the corresponding regulations. A distinction must be made between the direct and indirect influences of a storage on the control point. A direct influence is present if a discharge can have a direct effect on the flow conditions at the control point, i.e. the natural flow between the storage &lt;br /&gt;
and the control point can no longer be changed by regulation. If this is not the case, an indirect influence is given.&lt;br /&gt;
&lt;br /&gt;
:All storages with a direct influence on the control point receive a shortfall factor and a volume-dependent, scalable function according to [[:Datei:Theorie_Abb10.png|Figure 10]]. Thus, depending on the shortfall quantities and the storage capacity, the actual discharge can be determined separately for each storage.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 6: Discharge Depending on the storage Inflow==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb11.png|thumb|Figure 11: Direct dependency between storage and control point]]&lt;br /&gt;
:There is a direct dependency between the discharge from the storage and the current inflow to the storage. Similar to the pool-based operating plan, there is also an adaptation to different inflow situations. This is done to prevent depletion or overflowing or to obtain a variable discharge regime downstream. However, long-term inflow fluctuations are difficult to detect with this operating rule, since the observations are only carried out as snapshots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:To determine an inflow-dependent discharge, several components have to be considered. First of all, a relation between the current inflow and discharge must be defined. In addition to the current inflow, the current storage volume is important, because the relation inflow/outflow must not be valid for every filling level. Thus it is likely that the relation is ceded completely or the release quantities are adjusted if the storage level falls below a critical level.&lt;br /&gt;
&lt;br /&gt;
:As this rule can lead to the co-occurrence of relatively small storage volumes and high inflows resulting in high discharge volumes, special attention must be paid to the basic principle of checking the physical limits.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb12.png|thumb|Figure 12: Example of functions for inflow-dependent discharge]]&lt;br /&gt;
:In this case, three functional dependencies play a part. First, there is a direct dependency between the current inflow and the discharge. The form of the function can be arbitrary. It is possible to reproduce only individual sections of the inflow, which corresponds to a partial approximation of the discharge to the duration curve of the inflow.&lt;br /&gt;
&lt;br /&gt;
:Second, the inflow/discharge function can be superposed with the relationship between storage volume and discharge. For reasons of clarity, it is recommended to work with a normalized function. This makes it possible to influence the result of the inflow/discharge function for each storage volume, which is especially convenient for low filling levels.&lt;br /&gt;
&lt;br /&gt;
:Finally, the required discharge has to be checked with regard to the outlet elements&#039; capacity.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb13.png|thumb|left|Figure 13: Results of different inflow-dependent release strategies]]&lt;br /&gt;
&lt;br /&gt;
:The examples below show how the interaction of different functions affects the discharges. The results are compared in the following figures as inflow and discharge duration lines.&lt;br /&gt;
&lt;br /&gt;
:In the case of a linear relation between inflow and discharge and a constant factor for the storage volume, the duration line of the discharge is a curve corresponding to the inflow reduced by a certain percentage. If the storage volume factor remains constant, the duration line can be changed by varying the inflow/discharge relationship. An additional modification of the factor via the storage volume has the advantage of being able to respond to certain filling levels to prevent the storage from emptying or overflowing.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 7: Influence of Discharges Trough System States==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Rule 7, just as rule 6, is a continuation and generalization of the increase of low water as described in rules 5. Just like a discharge deficit at a cross-section or the storage inflow can influence the discharge, any other system state can. In general terms, this means that a discharge from a storage is triggered, increased, or reduced due to a certain system state. Basically, it is irrelevant where the system state occurs. All measurable variables that influence the transport and storage of water can be considered as system states, e.g. the filling of other storages, discharges, flow regime at a cross-section, a snow depth in the catchment area, current precipitation, or current soil moisture.&lt;br /&gt;
&lt;br /&gt;
:As a requirement to apply those dependencies a detection of the system state is necessary. Practically, this means either that a measuring device must be available to determine needed parameters or the required values are calculated using a mathematical model. Parameters are only considered as snap-shots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:If several system states should influence the discharge, a superposition of the parameters according to a corresponding regulation is necessary.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Mathematically, the influence of system states on the discharge can always be undertaken by scaling. Two functions are necessary for this. The first function describes the relationship between storage volume and discharge. The second one controls the dependency between the system state and a scaling factor. The connection is done by multiplying the discharge with the scaling factor.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb13.5.png|thumb|Transition]]&lt;br /&gt;
&lt;br /&gt;
:A simple example is given by a transition from storage A to storage B. &lt;br /&gt;
&lt;br /&gt;
:The decisive discharge is the transition from A to B. The considered system state is the storage volume of B. It seems obvious that a discharge from A to B is only useful if storage A has sufficient provision and storage B has sufficient capacity to hold additional water. This results in the following simple functions:&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb14.png|thumb|left|Figure 14: Example functions for linking a system state to a discharge]]Reservoir B takes 100% of the discharge from A as long as its filling level does not reach 70% of the maximum volume. Furthermore, it is undesirable to receive additional water for flood protection reasons. The scaling factor decreases from 70% filling level to zero. Starting at a filling level above 50% it becomes increasingly easy to transfer water from Reservoir A to reservoir B. The actual transfer, however, only results from the interaction of both functions, taking into account the current filling level of reservoir B and the scaling derived from it.&lt;br /&gt;
&lt;br /&gt;
:For storage A, the definition of the discharge is in m³/s, while the function for storage B receives a unitless scaling factor. In principle, however, it is possible to exchange the meaning of the functions and to use a unitless function for storage A to scale the desired transfer volume for storage B.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 8: Influencing a Discharge with Balances==&lt;br /&gt;
&lt;br /&gt;
 Dependency: [[Datei:Theorie_Abb15.png|thumb|Figure 15 : Example of long-term monthly averages and moving 30 day averages of storage volumes]]&lt;br /&gt;
:This rule is an extension of rule 7. Instead of using a current state parameter, the balance of a system state is linked to discharge. It is important that there are set time boundaries for carrying out the balance. However, it is irrelevant whether the balance is interpreted as a sum or as an average. A function that displays scaling factors depending on the actual balance can then be used to influence discharges.&lt;br /&gt;
&lt;br /&gt;
:In practice, this form of dependency is often found where water rights define maximum withdrawal volumes per time unit. But the application of a balance is also interesting regarding the long-term behaviour of storage filling levels or inflows. For example, a discharge could be reduced to build up provisions if the inflow of the past winter half-year was below a defined expected value. Another application is the comparison between long-term and current moving averages of storage filling levels. If the current values deviate from the long-term values by a certain amount, the discharge can be reduced or increased to compensate.&lt;br /&gt;
&lt;br /&gt;
:If linking a discharge to several balances is desired, it is possible to superpose several balances (see example at the end of this chapter). &lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb16.png|thumb|Figure 16: Example of a rule for standard discharge]]&lt;br /&gt;
:The influence of the balance on the discharge is posed by two functions according to rule 7. In addition to the already necessary storage volume/discharge function, there is a relation between the balance and scaling factor. The scaling factor is taken from the difference between the actual balance and the expected value.&lt;br /&gt;
&lt;br /&gt;
:The method is demonstrated with a simple example of a standard discharge.&lt;br /&gt;
&lt;br /&gt;
:For storage A, long-term monthly mean values of the storage volumes and derived sliding 30-day mean values of the storage filling levels, as well as the rule for the standard discharge, are known.&lt;br /&gt;
&lt;br /&gt;
:If, for example, on May 1st the average value of the storage volume calculated from the last 30 days amounts to 5.6 million m³ and thus, according to [[:Datei:Theorie_Abb15.png|Fig. 15]], it deviates by 30% from the long-term average value of 8 million m³, a scaling factor of 0.5 results (see [[:Datei:Theorie_Abb16.png|Fig. 16]]). With this value, the standard discharge is reduced and delivers only 0.25m³/s at a current storage filling level of 40%, i.e. 50% less than intended.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb17.png|thumb|left|Abbildung 17: Example functions to link a water balance with a discharge]]The relation between the deviation of the balance and the scaling factor indicates that only starting from a difference greater than 20% a change of the standard discharge takes place. In the case of a decrease of more than 20%, the standard discharge is reduced stepwise. If the actual moving 30-day average exceeds the long-term values by more than 20%, the standard discharge is increased continuously.&lt;br /&gt;
&lt;br /&gt;
:In general, there is also the possibility to extend the relation by superposing and combining several water balances.&lt;br /&gt;
&lt;br /&gt;
:The interaction between water balance and discharge function is explained below.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 9: Priorities for Competing Discharges from a Storage==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb18.png|thumb|Figure 18: Example for assigning priorities via the position of functions]]&lt;br /&gt;
:If there are several discharges from a storage, it can occur that it is not possible to carry out all demanded discharges. In such a case, priorities need to be specified, which determine an order in which discharges are to be satisfied. The order of priorities is often a consequence of political decisions and is not subject to physical conditions.&lt;br /&gt;
&lt;br /&gt;
:However, there are some priorities based on physical conditions. An example is turning off a turbine in times of water shortage in favor of securing the water supply. In practice, operating rules often meet this problem by fulfilling demands up to defined storage volumes, but not maintaining discharges below the set storage volume.&lt;br /&gt;
&lt;br /&gt;
:Another way to describe priorities is to reduce a discharge A exactly by an amount, which is resulting from a second discharge B, with the discharge A never being smaller than zero.&lt;br /&gt;
&lt;br /&gt;
* Practical example:&lt;br /&gt;
:The Wiehl dam gives a good example for the practical operating conditions of a dam. The Wiehl dam serves primarily as a drinking water supply and a means for flood protection, and secondarily for energy production. In addition, a minimum flow of 100 l/s has to be guaranteed downstream of the Wiehl dam. The first priority is the drinking water supply. In order to ensure sufficient water quality in the storage, additional discharges used for energy production are stopped when the storage volume falls below 70% of the total volume. As both the minimum discharge and the turbine discharge leave into the Wiehl, it would also be uncalled-for to maintain the minimum discharge if water was simultaneously discharged through the turbine. This results in a reduction of a discharge A (minimum discharge) by the amount of discharge B (turbine) as described above &amp;lt;ref name=&amp;quot;Aggerverband_1999&amp;quot;&amp;gt;&#039;&#039;&#039;Aggerverband&#039;&#039;&#039; (1999): Hydrologische Sicherheit der Genkel- und Aggertalsperre. Gutachten des Fachgebietes Ingenieurhydrologie und Wasserbewirtschaftung, TU Darmstadt&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb19.png|thumb||Figure 19: Example of a relation between two discharges]]&lt;br /&gt;
:Assuming that for each use, following the above rules, a functional dependency between storage content and discharge exists, a ranking of several uses is already given by the position of the function&#039;s nodes.  Then, the respective storage volume from which the target discharge is no longer covered to 100% or even reduced to zero is decisive.&lt;br /&gt;
&lt;br /&gt;
:In the example, the ranking of the uses is clearly visible. First, the turbine is switched off, then the increase of low water refrained from until only the discharge covering the water supply remains.&lt;br /&gt;
&lt;br /&gt;
:In addition, it is possible to directly compare two or more discharges. Such a rule could be:&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;If discharge B &amp;gt; 0 and the storage volume S &amp;lt; X, then reduce discharge A by the amount of discharge B, with discharge  A not being smaller than zero.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:This means that a linear dependency exists between A and B until B is equal to the value of A. If B increases further, A remains constantly zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 11: Water Distribution==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:If there is the need to distribute water within a water resources system, a distribution rule must be defined.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb19.5.png|thumb|Diversion]]&lt;br /&gt;
&lt;br /&gt;
:Two types of diversions can occur:&lt;br /&gt;
:# Diversion that exclusively follows hydraulic laws &lt;br /&gt;
:# Adjustable diversions &lt;br /&gt;
&lt;br /&gt;
:In both cases, relations can always be defined as a function of the inflow. In the second case, these distribution rules represent an operating rule, since they directly influence the transport and storage behavior of water. The number of discharges is basically not limited. The difference to transitions at dams is that in this case no storage volume can be used as a reference value.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb20.png|thumb|Figure 20 :Example of assignment functions for multiple sequences]]&lt;br /&gt;
&lt;br /&gt;
* Practical example: &lt;br /&gt;
:The water supply of Windhoek, the capital of Namibia, is provided by three dams. However, the water withdrawal for the drinking water supply is only possible from one dam - the Von Bach Dam. The remaining two storages are connected to the main dam by pipes. However, the volume transferred between Swakopport Dam and Von Bach Dam is not exclusively available for refilling the Von Bach Dam, but also serves to supply the town of Karibib with drinking water.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb21.png|thumb|left|Fig. 21: Example of a threshold concept for a division into two flows]]For the definition of division rules, functions depending on the current inflow are an appropriate representation. Thus, both a hydraulic description and a description serving the management of the storage are possible. For each discharge leaving the diversion structure, a distribution function has to be specified. If the functions are to be variable, scaling is recommended.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb22.png|thumb|Figure 22: Example of a threshold concept with a distribution to serve several users&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
:If the distribution functions cannot be pre-defined, but the discharge volumes rather result later from demand calculations, then a threshold concept is suitable, which in turn can work with scaling factors. The threshold is scaled by a factor and is therefore variable. As long as the inflow is lower than the threshold, the entire inflow is used to satisfy the demand. Only when the current inflow exceeds the threshold, the remaining amount is discharged.&lt;br /&gt;
&lt;br /&gt;
:If a division into more than two discharges is necessary, the threshold concept can be successively applied several times. The order of the discharges determines the priorities of the water distribution.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Literature==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/12/en&amp;diff=12991</id>
		<title>Translations:Betriebsregeltypen/12/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/12/en&amp;diff=12991"/>
		<updated>2021-08-30T10:46:03Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* Dependency:&lt;br /&gt;
:The specification of a minimum or maximum discharge is based on requirements downstream of a storage. The maximal discharge is based on the discharge respective to a critical, downstream cross-section. Consequently, a hydraulic method exists for its determination. In contrast, there is no clear guideline for the minimum discharge. Often, ratios of MNQ or MQ are used. Independent of determining the minimum or maximum discharge, the basic principle to verify outlet elements&#039; physical limits is applied. So, minimum and maximum discharge can only be discharged if the outlet capacity is sufficient at the given pressure level. Since, in reality, it is unlikely that the dimensioning of the outlet elements and the required discharge are conflicting, the reference to the dependence on the storage capacity content is rather theoretical but necessary to derive general laws.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Transportstrecke/en&amp;diff=12990</id>
		<title>Transportstrecke/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Transportstrecke/en&amp;diff=12990"/>
		<updated>2021-08-30T10:45:16Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=Einleitung|hoch=Beschreibung der Systemelemente|nachher=Verbraucher}}&lt;br /&gt;
__TOC__&lt;br /&gt;
[[Datei:Systemelement003.png|50px|none]]&lt;br /&gt;
Transport reaches simulate the translation and retention behavior of natural water courses or pipelines. There are different approaches for the calculation of pipes or natural channels.&lt;br /&gt;
&lt;br /&gt;
The following options are implemented:&lt;br /&gt;
[[Datei:Berechnungsoptionen_Transportstrecke_EN.png|frame|none|Calculation options for transport reaches]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Translation==&lt;br /&gt;
&lt;br /&gt;
The inflow wave is output at the outlet with a time offset that corresponds to the flow time in the transport reach. If the flow time is smaller than the simulation time step, the translation behavior is not visible in the simulation results.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Non-Pressurized Pipeline==&lt;br /&gt;
&lt;br /&gt;
This option encompasses flow routing calculation for pipes according to Kalinin-Miljukov. The parameters required by the Kalinin-Miljukov method are estimated internally according to /Euler, 1983/ for circular pipes, and for non-circular profiles, are determined from the hydraulic diameter and the cross-sectional area when completely filled. &lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Characteristic length: ||&amp;lt;math&amp;gt;L=0.4 \cdot \frac{D}{I_S}~\mbox{[m]} &amp;lt;/math&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|Retention constant: ||&amp;lt;math&amp;gt;0.64 \cdot L \cdot \frac{D^2}{Q_v} ~\mbox{[s]}&amp;lt;/math&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
with:&lt;br /&gt;
{|style=&amp;quot;margin-left: 40px;&amp;quot;&lt;br /&gt;
|&amp;lt;math&amp;gt;D~\mbox{[m]}&amp;lt;/math&amp;gt;: || Circular pipe diameter or hydraulic diameter&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;math&amp;gt;I_S~\mbox{[-]}&amp;lt;/math&amp;gt;: || Slope of the pipe&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;math&amp;gt;Q_v ~\mbox{[m³/s]}&amp;lt;/math&amp;gt;: || Discharge capacity of the pipe when completely filled&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The discharge capacity of the pipe when completely filled is calculated according to the flow law of Prandtl-Colebrook:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;math&amp;gt;Q_v=A_v \left [ -2 \cdot \lg \left [\frac{251 \cdot \nu}{D \sqrt{2 g D I_S}} + \frac{k_b}{3.71 \cdot D} \right ] \cdot \sqrt{2gDI_s} \right ]&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
with:&lt;br /&gt;
{|style=&amp;quot;margin-left: 40px;&amp;quot;&lt;br /&gt;
|&amp;lt;math&amp;gt;A_v~\mbox{[m²]}&amp;lt;/math&amp;gt;: || Cross-sectional area of the profile&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;math&amp;gt;\nu~\mbox{[m²/s]}&amp;lt;/math&amp;gt;: || Kinematic viscosity&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;math&amp;gt;k_b ~\mbox{[m³/s]}&amp;lt;/math&amp;gt;: || Operating roughness&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;math&amp;gt;g ~\mbox{[m/s²]}&amp;lt;/math&amp;gt;: || Gravitational acceleration&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Using the characteristic length &amp;lt;math&amp;gt;L&amp;lt;/math&amp;gt;, the length of the transport reach &amp;lt;math&amp;gt;L_g&amp;lt;/math&amp;gt; is divided into &amp;lt;math&amp;gt;n&amp;lt;/math&amp;gt; calculation sections of equal length with&lt;br /&gt;
&lt;br /&gt;
::&amp;lt;math&amp;gt;n=L_g/L&amp;lt;/math&amp;gt; (where &amp;lt;math&amp;gt;n&amp;lt;/math&amp;gt; is an integer number)&lt;br /&gt;
&lt;br /&gt;
Parameters are adjusted as follows for the individual calculation sections:&lt;br /&gt;
&lt;br /&gt;
::&amp;lt;math&amp;gt;L^*=L_g/n&amp;lt;/math&amp;gt;&lt;br /&gt;
::&amp;lt;math&amp;gt;K^*=K \cdot L^*/L&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Based on these parameters, after calculating the following recursion formula &amp;lt;math&amp;gt;n&amp;lt;/math&amp;gt; times,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;math&amp;gt;Q_{a,i}=Q_{a,i-1}+C_1 \cdot \left(Q_{z,i-1} - Q_{a,i-1} \right ) + C_2 \cdot \left(Q_{z,i}-Q_{z,i-1} \right) &amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
with:&lt;br /&gt;
{|style=&amp;quot;margin-left: 40px;&amp;quot;&lt;br /&gt;
|&amp;lt;math&amp;gt;Q_z&amp;lt;/math&amp;gt;: || Inflow to calculation section&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;math&amp;gt;Q_a&amp;lt;/math&amp;gt;: || Outflow from calculation section&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;math&amp;gt;i&amp;lt;/math&amp;gt;: || Current calculation time step&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;math&amp;gt;i-1&amp;lt;/math&amp;gt;: || Previous calculation time step&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;math&amp;gt;dt&amp;lt;/math&amp;gt;: || Calculation time interval&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;math&amp;gt;C_1=1- e^{-dt/K^*}&amp;lt;/math&amp;gt; || &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;math&amp;gt;C_2=1- \frac{K^*}{dt}/C_1&amp;lt;/math&amp;gt; || &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
produces the outflow at the end of the pipe.&lt;br /&gt;
This approximation method derived from Kalinin-Miljukov is identical to the linear storage cascade used for calculating runoff concentration. This means the flow ina transport reach can be simulated using a linear storage cascade consisting of &amp;lt;math&amp;gt;n&amp;lt;/math&amp;gt; storages with the retention constant &amp;lt;math&amp;gt;K^*&amp;lt;/math&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Cross-Section (Open Channel)==&lt;br /&gt;
&lt;br /&gt;
As with non-pressurized pipelines, the translation and retention behavior is simulated using flow routing according to Kalinin-Miljukov. The characteristic length required as a parameter for the Kalinin-Miljukov method is derived from the steady uniform flow relationship according to Manning-Strickler /Rosemann, 1970/. &lt;br /&gt;
&lt;br /&gt;
[[Datei:Schema_charakteristische_Länge_EN.png|400px]]&lt;br /&gt;
&lt;br /&gt;
The channel is divided into individual segments with the characteristic length. For each segment, the calculation of flow routing is carried out using [[Special:MyLanguage/Berechnungsschema von Speichern|nonlinear storage calculation]] with the help of the steady uniform flow relation.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rating Curve (Open Channel)==&lt;br /&gt;
&lt;br /&gt;
If the flow behavior of the transport reach is known, e.g. from previous hydraulic calculations, a rating curve defining the relationship between water level, cross sectional area and discharge can be used.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Transportstrecke/21/en&amp;diff=12989</id>
		<title>Translations:Transportstrecke/21/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Transportstrecke/21/en&amp;diff=12989"/>
		<updated>2021-08-30T10:45:16Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Datei:Schema_charakteristische_Länge_EN.png|400px]]&lt;br /&gt;
&lt;br /&gt;
The channel is divided into individual segments with the characteristic length. For each segment, the calculation of flow routing is carried out using [[Special:MyLanguage/Berechnungsschema von Speichern|nonlinear storage calculation]] with the help of the steady uniform flow relation.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Unterteilung_in_Systemelemente/en&amp;diff=12988</id>
		<title>Unterteilung in Systemelemente/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Unterteilung_in_Systemelemente/en&amp;diff=12988"/>
		<updated>2021-08-30T10:44:49Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=Systemabgrenzung|hoch=Arbeitsschritte zur Modellerstellung|nachher=Systemlogik}}&lt;br /&gt;
&lt;br /&gt;
In order to divide a water resources system into individual [[Special:MyLanguage/Beschreibung der Systemelemente|system elements]] it is vital to consider the problem which the model is used for and the existing data basis. &lt;br /&gt;
&lt;br /&gt;
Basically there are two possible ways for the division of the system. It can be divided either catchment-based or grid-based. In addition, all hydrological structures relevant to the problem must be identified and represented by a suitable [[Special:MyLanguage/Beschreibung der Systemelemente|system element]], e.g. dams by [[Special:MyLanguage/Speicher|reservoir]], extractions by [[Special:MyLanguage/Verbraucher|consumer]], etc. Often there are several feasible solutions.&lt;br /&gt;
&lt;br /&gt;
The preliminary work for dividing a river basin is usually done with a GIS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Catchment-based Division==&lt;br /&gt;
&lt;br /&gt;
Criteria for the division can be:&lt;br /&gt;
&lt;br /&gt;
*Catchment properties (topography)&lt;br /&gt;
* Punctual changes of the outflow by&lt;br /&gt;
** Inflows&lt;br /&gt;
** Point sources&lt;br /&gt;
** Extractions&lt;br /&gt;
* Location of hydrological structures&lt;br /&gt;
* Location of gauging stations&lt;br /&gt;
* Flow type and geometry&lt;br /&gt;
&lt;br /&gt;
The results of this division are digital catchment boundaries and river sections. If the available data initially results in a rough division, it can be subdivided even further, especially if, due to the problem at hand, certain processes in the waterbody can no longer be represented with the intitial division. In the following, a high resolution water resources system is compared to a low resolution water resources system:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| [[Datei:System_räumlich_hochaufgelöst.png|400px]] || [[Datei:System_räumlich_geringaufgelöst.png|400px]]&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
*As the accuracy of system mapping increases, the importance of hydraulics in the waterbodies increases.&lt;br /&gt;
*The parameters of the runoff concentration only refer to the surface runoff in the corresponding sub-catchments, resp. interflow and base flow.&lt;br /&gt;
*The illustration of flood-routing within the waterbodies is possible.&lt;br /&gt;
||&lt;br /&gt;
*Simple approaches to the calculation of runoff generation usually manage better with a rough system illustration.&lt;br /&gt;
*Both, the surface runoff in the sub-catchments and the flood-routing that occur in the waterbodies are included in the parameters of the runoff concentration. &lt;br /&gt;
*The illustration of flood-routing within the waterbodies is hardly possible.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[Datei:Teilgebiet_Auswahl_Systemelemente.png|thumb| Sub-catchments can be defined via a [[Einzugsgebiet|Rainfall-Runoff Model]][[Datei:Systemelement001.png|20px]] or can be visualised through a [[Special:MyLanguage/Einleitung|hydrograph]][[Datei:Systemelement002.png|20px]] at the output]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The next step is to decide which system elements are to be used to map the sub-catchments, depending on the problem and the data basis. Alongside the system element [[Special:MyLanguage/Einzugsgebiet|sub-basin]], which brings the load into the system via a precipitation-runoff simulation, the system element [[Special:MyLanguage/Einleitung|point source]] can feed the outflow from the sub-catchment directly into the system via a hydrograph. The latter is of course only possible if a hydrograph is available. Then it is the solution using the fewest computational resources, which in addition (with good quality of the input data) also illustrates the actual outflow behavior in a realistic manner. If, however, for example, a forecast is to be calculated with changed land use conditions or if the hydrograph is not long enough, it is advisable to use the system element [[Special:MyLanguage/Einzugsgebiet|sub-basin]]. In Talsim-NG the selection of the system element for sub-catchments can also vary from sub-catchment to sub-catchment.&lt;br /&gt;
&lt;br /&gt;
Once the system elements are defined, the [[Special:MyLanguage/Systemlogik|flow network]] is created, i.e. the flow relationships between the elements are defined.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Grid-based Division==&lt;br /&gt;
&lt;br /&gt;
In grid-based division, water is generally passed from one cell to the next according to its flow direction. &lt;br /&gt;
&lt;br /&gt;
The transfer from one cell to the next varies depending on the flow component:&lt;br /&gt;
* Surface runoff is incorporated into the runoff generation process of the next cell, i.e. it is treated like additional precipitation.&lt;br /&gt;
* Interflow is fed into the cascade of storages of the next cell&#039;s interflow.&lt;br /&gt;
* Base flow is fed into the cascade of storages of the next cell&#039;s base flow.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Unterteilung_in_Systemelemente/15/en&amp;diff=12987</id>
		<title>Translations:Unterteilung in Systemelemente/15/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Unterteilung_in_Systemelemente/15/en&amp;diff=12987"/>
		<updated>2021-08-30T10:44:49Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The transfer from one cell to the next varies depending on the flow component:&lt;br /&gt;
* Surface runoff is incorporated into the runoff generation process of the next cell, i.e. it is treated like additional precipitation.&lt;br /&gt;
* Interflow is fed into the cascade of storages of the next cell&#039;s interflow.&lt;br /&gt;
* Base flow is fed into the cascade of storages of the next cell&#039;s base flow.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=ASCII-Datensatz/en&amp;diff=12986</id>
		<title>ASCII-Datensatz/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=ASCII-Datensatz/en&amp;diff=12986"/>
		<updated>2021-08-30T10:43:45Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=|hoch=Schnittstellen: Import/Export|nachher=Import/Export Zeitreihen}}&lt;br /&gt;
A data set contains all information about a system (e.g. flow network, input parameters, etc.) and is obtained by [[Special:MyLanguage/Bereich_Varianten#Variante_exportieren|exporting a scenario]] for example under &#039;&#039;D:\Talsim-NG\Customers\Auftraggeber_1\projectData\Example\dataSets&#039;&#039;. Depending on the size of the system, the dataset consists of a varying number of files: the more data and system elements are included in the system, the more files are created. &lt;br /&gt;
&lt;br /&gt;
The created data set can be passed on to other editors. They can [[Special:MyLanguage/Bereich_Varianten#Variante_importieren|import]] the data set into their Talsim model. For this, the *.SYS file is necessary.&lt;br /&gt;
&lt;br /&gt;
Below, an overview of all possible files is presented. &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Suffix !! Data&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/ALL-Datei|*.ALL]] || General information about the project&lt;br /&gt;
|- &lt;br /&gt;
| [[Special:MyLanguage/BOA-Datei|*.BOA]] ||Soil texture&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/BOD-Datei|*.BOD]] || Soil type&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/EIN-Datei|*.EIN]] || Point sources&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/EZG-Datei|*.EZG]] || Subcatchments&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/EXT-Datei|*.EXT]] || External time series&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/FKT-Datei|*.FKT]]	|| Functions with function values&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/HYO-Datei|*.HYO]]	|| Hydrology, evaporation, humidity, sunshine, wind&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/JGG-Datei|*.JGG]]	|| [[Special:MyLanguage/Belastungsdefinition / Modellinput#Jahresgang erstellen|Annual Patterns]]&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/KAL-Datei|*.KAL]] || Calibration factors&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/KTR-Datei|*.KTR]]	|| Control functions&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/LNZ-Datei|*.LNZ]]	|| Land use&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/PRO-Datei|*.PRO]]	|| Simulation settings for short-term simulations/design storms, parameters for model rains, flood wave statistics&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/QUA-Datei|*.QUA]]	|| [[Special:MyLanguage/Belastungsdefinition / Modellinput#Stoffparameter|Quality parameters]]&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/RFD-Datei|*.RFD]]	|| Precipitation distribution&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/SCE-Datei|*.SCE]]	|| Settings for scenario simulation&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/SIMINFO-Datei|*.SIMINFO]] || Information about the simulation&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/SYS-Datei|*.SYS]]	|| Flow network&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/TAL-Datei|*.TAL]]	|| Settings for all storage elements&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/TEM-Datei|*.TEM]]	|| Settings for temperature modelling&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/TGG-Datei|*.TGG]]	|| [[Special:MyLanguage/Belastungsdefinition / Modellinput#Tagesgang erstellen|Daily patterns]]&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/TRS-Datei|*.TRS]] || Settings for all transport elements&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/TXT-Datei|*.TXT]]	|| Description of all system elements, control clusters, system states&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/UPD-Datei|*.UPD]]	|| Update configuration&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/VAR-Datei|*.VAR]] || Consumer&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/VER-Datei|*.VER]]	|| Diversions&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/WGG-Datei|*.WGG]]	|| [[Special:MyLanguage/Belastungsdefinition / Modellinput#Wochengang erstellen|Weekly patterns]]&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/ZIE-Datei|*.ZIE]]	|| Objective function&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Besides, two result data sets are automatically saved after a scenario has been simulated.&lt;br /&gt;
&lt;br /&gt;
Firstly, the zipped data set &#039;&#039;&#039;*.WLZIP&#039;&#039;&#039; contains all results for the simulation. It is created under &#039;&#039;D:\Talsim-NG\Customers\Auftraggeber_1\projectData\Beispiel\dataBase\Beispiel_Data&#039;&#039;. When unpacking the zipped file, the files *.WEL and *.WELINFO are the output. Depending on the [[Special:MyLanguage/Belastungsdefinition / Modellinput#Stoffparameter|quality parameters]], there is the possibility of more output files.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Suffix !! Data&lt;br /&gt;
|-&lt;br /&gt;
| *.CHLO.WEL || Chloride loads and concentrations of all system elements&lt;br /&gt;
|-&lt;br /&gt;
| *.CHLO.WELINFO || Respective labeling of the file *.CHLO.WEL&lt;br /&gt;
|-&lt;br /&gt;
| *.KALI.WEL || Potassium loads and concentrations of all system elements&lt;br /&gt;
|-&lt;br /&gt;
| *.KALI.WELINFO || Respective labeling of the file *.KALI.WEL&lt;br /&gt;
|-&lt;br /&gt;
| *.KTR.WEL	|| Simulation results of all control functions&lt;br /&gt;
|-&lt;br /&gt;
| *.KTR.WELINFO	|| Respective labeling of the file *.KTR.WEL&lt;br /&gt;
|-&lt;br /&gt;
| *.WEL	|| Simulation results of all system elements&lt;br /&gt;
|-&lt;br /&gt;
| *.WELINFO || Respective labeling of the file *.WEL&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Secondly, the zipped data set &#039;&#039;&#039;*.ERGZIP&#039;&#039;&#039; is created under &#039;&#039;D:\Talsim-NG\Customers\Auftraggeber_1\projectData\Beispiel\dataBase\Beispiel_Data\result&#039;&#039;. When the zipped file is unpacked, the following files are the output. &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Suffix !! Data&lt;br /&gt;
|-&lt;br /&gt;
| *.[[Special:MyLanguage/BLZ-Datei|BLZ]] || Balance results&lt;br /&gt;
|-&lt;br /&gt;
| *.LOG || &lt;br /&gt;
|-&lt;br /&gt;
| *.MAX || &lt;br /&gt;
|-&lt;br /&gt;
| *.SIMEND || &lt;br /&gt;
|-&lt;br /&gt;
| *.SIMINFO || &lt;br /&gt;
|-&lt;br /&gt;
| *.WELINFO || &lt;br /&gt;
|-&lt;br /&gt;
| *.WMX|| &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:ASCII-Datensatz/4/en&amp;diff=12985</id>
		<title>Translations:ASCII-Datensatz/4/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:ASCII-Datensatz/4/en&amp;diff=12985"/>
		<updated>2021-08-30T10:43:44Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Suffix !! Data&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/ALL-Datei|*.ALL]] || General information about the project&lt;br /&gt;
|- &lt;br /&gt;
| [[Special:MyLanguage/BOA-Datei|*.BOA]] ||Soil texture&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/BOD-Datei|*.BOD]] || Soil type&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/EIN-Datei|*.EIN]] || Point sources&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/EZG-Datei|*.EZG]] || Subcatchments&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/EXT-Datei|*.EXT]] || External time series&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/FKT-Datei|*.FKT]]	|| Functions with function values&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/HYO-Datei|*.HYO]]	|| Hydrology, evaporation, humidity, sunshine, wind&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/JGG-Datei|*.JGG]]	|| [[Special:MyLanguage/Belastungsdefinition / Modellinput#Jahresgang erstellen|Annual Patterns]]&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/KAL-Datei|*.KAL]] || Calibration factors&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/KTR-Datei|*.KTR]]	|| Control functions&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/LNZ-Datei|*.LNZ]]	|| Land use&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/PRO-Datei|*.PRO]]	|| Simulation settings for short-term simulations/design storms, parameters for model rains, flood wave statistics&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/QUA-Datei|*.QUA]]	|| [[Special:MyLanguage/Belastungsdefinition / Modellinput#Stoffparameter|Quality parameters]]&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/RFD-Datei|*.RFD]]	|| Precipitation distribution&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/SCE-Datei|*.SCE]]	|| Settings for scenario simulation&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/SIMINFO-Datei|*.SIMINFO]] || Information about the simulation&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/SYS-Datei|*.SYS]]	|| Flow network&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/TAL-Datei|*.TAL]]	|| Settings for all storage elements&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/TEM-Datei|*.TEM]]	|| Settings for temperature modelling&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/TGG-Datei|*.TGG]]	|| [[Special:MyLanguage/Belastungsdefinition / Modellinput#Tagesgang erstellen|Daily patterns]]&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/TRS-Datei|*.TRS]] || Settings for all transport elements&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/TXT-Datei|*.TXT]]	|| Description of all system elements, control clusters, system states&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/UPD-Datei|*.UPD]]	|| Update configuration&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/VAR-Datei|*.VAR]] || Consumer&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/VER-Datei|*.VER]]	|| Diversions&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/WGG-Datei|*.WGG]]	|| [[Special:MyLanguage/Belastungsdefinition / Modellinput#Wochengang erstellen|Weekly patterns]]&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/ZIE-Datei|*.ZIE]]	|| Objective function&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Zeitreihenverwaltung/en&amp;diff=12984</id>
		<title>Zeitreihenverwaltung/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Zeitreihenverwaltung/en&amp;diff=12984"/>
		<updated>2021-08-30T10:43:21Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=Menüleiste Systemverwaltung|hoch=Hauptseite|nachher=Einzelfenster von Modellkomponenten}}&lt;br /&gt;
&lt;br /&gt;
Time series can be stored in TALSIM-NG&#039;s own time series manager, where they are classified by the type of data and the station they belong to. There they can be viewed graphically and edited tabularly. A basic statistics&#039; tool, which can calculate average values for a defined period of time as well as other statistics, is also integrated in the time series manager.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Opening the Time Series Manager===&lt;br /&gt;
&lt;br /&gt;
The time series manager can be accessed via the &#039;&#039;Menu bar &amp;amp;rarr; Time series &amp;amp;rarr; Time series manager&#039;&#039;. The &#039;&#039;&#039;Talsim-User Selection&#039;&#039;&#039; window, where you are required to choose a user to proceed, appears. If you want to create and edit time series, you should choose your username and confirm with &#039;&#039;&#039;OK&#039;&#039;&#039;. If you log in using another username, you can only see the stations and time series, but you cannot edit or delete them.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe001_EN.png|Datei:Zeitreihe001EN_.png|500px]] &lt;br /&gt;
[[Datei:Zeitreihe002_EN.png]]&lt;br /&gt;
&lt;br /&gt;
If you are logged in with your username and have not created any time series yet, an empty &#039;&#039;&#039;TalsminNG - TS Explorer&#039;&#039;&#039; opens. This explorer can be customized using &#039;&#039;&#039;View&#039;&#039;&#039;, &#039;&#039;&#039;Folder&#039;&#039;&#039;, as well as the &#039;&#039;&#039;folder icon&#039;&#039;&#039;. &lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe003_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Create New Station===&lt;br /&gt;
&lt;br /&gt;
Time series are principally assigned to stations, e.g. measuring stations. For this reason a station should be created first. To do this, right-click on the &#039;&#039;Explorer &amp;amp;rarr; New Station&#039;&#039;. A window, where you can enter the name of the station and confirm with &#039;&#039;&#039;OK&#039;&#039;&#039;, will appear.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe004_EN.png]] [[Datei:Zeitreihe005_EN.png|Datei:Zeitreihe005_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Subsequently, a new station, as well as 15 subfolders are created. These subfolders present the different types of the hydrological, hydrometeorological, or storage-dependent variables that can be saved as time series in the TS Explorer.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe006_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You have a choice of the following options when you right-click on the new station in the explorer.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width:70%&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;New Station&#039;&#039;&#039; 	||A new empty station with 15 subfolders is created. &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Edit Station&#039;&#039;&#039; 	||The dialog window &#039;&#039;Edit of a Talsim time series station&#039;&#039;, in which information about the selected station can be edited, is opened.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Delete Station&#039;&#039;&#039; ||The marked station and all associated time series are deleted. This operation cannot be undone.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Copy to Clipboard&#039;&#039;&#039; || The list of time series associated with the station as well as their metadata is copied to the clipboard.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;New Time Series&#039;&#039;&#039; ||A new time series associated with the selected station is created.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Release Edit-lock&#039;&#039;&#039; ||Releases the edit-lock of the station, so it can be edited by another user.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Create New Time Series===&lt;br /&gt;
&lt;br /&gt;
To create a time series, right-click on the &#039;&#039;Station &amp;amp;rarr; New Time Series&#039;&#039; in the [[Special:MyLanguage/Belastungsdefinition / Modellinput#Zeitreihenverwaltung|time series explorer]]. A window will open, prompting you to enter the name of the new time series. Confirm with &#039;&#039;&#039;OK&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe007_EN.png|Datei:Zeitreihe007_EN.png]]&lt;br /&gt;
&lt;br /&gt;
The following attributes are displayed for each time series in the explorer:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width:70%&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Name&#039;&#039;&#039; 	||Name of the time series.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;ID&#039;&#039;&#039; 	||Identification number of a time series. ID corresponds to the ID of the binary file, stored in the system data. Caution: Not to be confused with the ID of a simulation in the model and on the server.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Type&#039;&#039;&#039; ||Hydrological, hydrometeorological, storage-dependent or geological variable. With this setting the time series is assigned to one of the 15 subfolders of the station. Default value: discharge.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Unit&#039;&#039;&#039; ||Unit of the values. Default value: m³/s.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Interpretation&#039;&#039;&#039; ||Information about the time series values, i.e. how to understand the timestamp and the value stored in it. Caution: wrongly set interpretations inevitably lead to incorrect results. For example, precipitation [mm] is usually a sum per timestep. Default value: Current_value (linear_interpolation)&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Origin&#039;&#039;&#039; ||Origin of the time series. Default value: measured.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;from&#039;&#039;&#039; ||Date and time of the start of the time series. Default value: Day and time of creation.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;to&#039;&#039;&#039; ||Date and time of the end of the time series. Default value: Day and time of creation.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Data points&#039;&#039;&#039; ||Number of data points. Default value: 0&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe008_EN.png]]&lt;br /&gt;
&lt;br /&gt;
The created time series is assigned the chosen name and a consecutive ID number. The other attributes are filled with the default values.&lt;br /&gt;
&lt;br /&gt;
You can use the following buttons if you right-click on the time series in the explorer.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width:70%&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Edit Time Series&#039;&#039;&#039; ||The selected time series can be edited.  &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Chart&#039;&#039;&#039; 	||The time series can be displayed as a graph over time or as a duration curve.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Edit Values&#039;&#039;&#039; ||Values with date are added to the selected time series. Values can also be edited or deleted.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Statistics&#039;&#039;&#039; ||Calculates a statistical overview of the time series.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Import Time Series&#039;&#039;&#039; ||An existing time series can be imported.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Export Time Series&#039;&#039;&#039; ||The selected time series can be exported.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Delete Time Series&#039;&#039;&#039; ||The selected time series is deleted. This operation cannot be undone.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Release Edit-lock&#039;&#039;&#039; ||Releases the edit-lock of the time series, so it can be edited by another user..&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Refresh Attributes&#039;&#039;&#039; ||After adjusting the attributes of a time series, those attributes are updated in the explorer.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Edit Time Series&lt;br /&gt;
&lt;br /&gt;
To adjust the attributes of a time series, right-click on &#039;&#039;Time Series &amp;amp;rarr; Edit Time Series&#039;&#039; in the time series manager. &lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe009_EN.png]]&lt;br /&gt;
&lt;br /&gt;
The following dialog window, where you can edit the attributes, opens. The attributes assigned to identification and settings, which are displayed in black, can be adjusted with a double-click. By clicking OK all time series attributes can be saved. &lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe010_EN.png]]&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width:70%&amp;quot;&lt;br /&gt;
|- &lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot; style=&amp;quot;text-align:center&amp;quot; |&#039;&#039;&#039;Identification&#039;&#039;&#039; &lt;br /&gt;
|&#039;&#039;Description&#039;&#039; &lt;br /&gt;
|Description of the time series &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Name&#039;&#039; &lt;br /&gt;
|Name of the time series&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;8&amp;quot; style=&amp;quot;text-align:center&amp;quot;|&#039;&#039;&#039;Settings&#039;&#039;&#039; &lt;br /&gt;
|&#039;&#039;Altitude masl&#039;&#039; &lt;br /&gt;
|Height of the measuring station in meters above sea level&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Coordinate-X&#039;&#039;&lt;br /&gt;
|X-coordinate of the measuring station &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Coordinate-Y&#039;&#039;&lt;br /&gt;
|Y-coordinate of the measuring station  &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Interpretation&#039;&#039; &lt;br /&gt;
|Information about the time series values, i.e. how to understand the timestamp and the value stored in it. Caution: wrongly defined interpretations inevitably lead to incorrect results. &lt;br /&gt;
Choice of: [[Datei:00036_EN.png|mini]]&lt;br /&gt;
*BlockLeft &lt;br /&gt;
*BlockRight&lt;br /&gt;
*Instantaneous_(Linear_Interpolation)&lt;br /&gt;
*Cumulative &lt;br /&gt;
*CumulativePerTimeStep&lt;br /&gt;
*Undefined&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Memo&#039;&#039;&lt;br /&gt;
|Description of the origin of the time series and other additional information&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Origin&#039;&#039;&lt;br /&gt;
|Origin of the time series&lt;br /&gt;
Choice of:&lt;br /&gt;
*derived&lt;br /&gt;
*measured&lt;br /&gt;
*imported&lt;br /&gt;
*manual&lt;br /&gt;
*simulated&lt;br /&gt;
*miscellaneous&lt;br /&gt;
*synthetic&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Type&#039;&#039;&lt;br /&gt;
|Hydrological, hydrometeorological, storage-dependent or geological variable &lt;br /&gt;
With this setting the time series is assigned to one of the 15 subfolders of the station.&lt;br /&gt;
Choice of:&lt;br /&gt;
*area &lt;br /&gt;
*discharge&lt;br /&gt;
*evaporation&lt;br /&gt;
*humidity&lt;br /&gt;
*mass movement&lt;br /&gt;
*precipitation&lt;br /&gt;
*pressure&lt;br /&gt;
*soil process&lt;br /&gt;
*storage &lt;br /&gt;
*sunshine &lt;br /&gt;
*temperature &lt;br /&gt;
*unknown&lt;br /&gt;
*velocity&lt;br /&gt;
*water level &lt;br /&gt;
*wind&lt;br /&gt;
|-&lt;br /&gt;
|Unit&lt;br /&gt;
|Unit of the variable&lt;br /&gt;
Choice of:&lt;br /&gt;
?,empty, number, class, mm/m, percent, h/d, 0/00, ml/l, mm, m, cm, km, hm, dm, l/ha, l/km², l/m², mNN, m², km², ha, cm², mm², dm², m³/m, m³, Tsd. m³, Mio. m³, l, hl, &lt;br /&gt;
km³, cm³, mm³, m/s, mm/d, mm/h, mm/min, l/s/km², m/h, m/d, l/s/ha, m/s², m³/s, l/s, m³/d, m³/h, l/h, l/d, °C, kg, g, mg, t, s, min, h, d, w, mon, a, Datum, &lt;br /&gt;
A, bar, pa, hpa, Grad, Rad, kg/m³, mg/l, g/l, l/kg, ml/g, Grad_C, kg/s, y/n&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Time Series Values===&lt;br /&gt;
&lt;br /&gt;
After a new time series is created and edited, values can be added to it. To do this, right-click on the &#039;&#039;Time Series &amp;amp;rarr; Edit Value&#039;&#039;. If a time series with values already exists, the values can be edited or deleted. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe0011_EN.png]]&lt;br /&gt;
&lt;br /&gt;
You can use the following buttons:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Edit&#039;&#039;&#039; ||Selected values of the time series can be edited.  &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Add&#039;&#039;&#039; ||Values can be added to the time series.&lt;br /&gt;
|-.&lt;br /&gt;
|&#039;&#039;&#039;Delete&#039;&#039;&#039; ||Selected values of the time series can be deleted. This operation cannot be undone.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Add Values to Time Series====&lt;br /&gt;
&lt;br /&gt;
To add new values to the time series, click on &#039;&#039;&#039;add&#039;&#039;&#039;. The following &#039;&#039;TalsimNGZreProvider&#039;&#039; window opens. This indicates that the time series does not contain any values yet, and is, therefore, not stored on the server on in the database. By clicking &#039;&#039;&#039;OK&#039;&#039;&#039; the window for editing the time series values opens. &lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe012_EN.png|Datei:Zeitreihe012_EN.png]] [[Datei:Zeitreihe013_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here you can use the following buttons:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Insert Row&#039;&#039;&#039; ||A row is inserted above the selected cell. &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Add Row&#039;&#039;&#039; || A row is added to the end of the time series.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Remove Row&#039;&#039;&#039; ||The selected row is removed.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Graph&#039;&#039;&#039; ||The time series is displayed graphically.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Check dates&#039;&#039;&#039; ||The date of the time series is checked. This means that the date must be ascending in time.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Write values&#039;&#039;&#039; ||The time series and its values are stored on the server and in the database. Additionally, a binary file, named after the ID of the time series, is created in the system data.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Delete values&#039;&#039;&#039; ||All values are deleted.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The &#039;Edit time series&#039; window shows the active time series, as well as the date, which by default corresponds to the date of creating the time series, unless it has been manually changed. Here you can manually enter a date and its corresponding value. You can also copy a time series with dates and values e.g. from Excel and click on the first cell of the table and paste it there (key combination: Ctrl+V).&lt;br /&gt;
&lt;br /&gt;
When the values are inserted, the time series can be displayed using &#039;&#039;&#039;Graph&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe014_EN.png|Datei:Zeitreihe014_EN.png]]&lt;br /&gt;
&lt;br /&gt;
In the next step the date is checked. If the dates are ascending, a window with &amp;quot;Check successful!&amp;quot; will appear. Otherwise an error message will be displayed.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe015_EN.png|Datei:Zeitreihe015_EN.png]] [[Datei:Zeitreihe016_EN.png|Datei:Zeitreihe016_EN.png]]&lt;br /&gt;
&lt;br /&gt;
If all values are complete and the date is successfully checked, the values are written. In the appearing window, click &#039;&#039;&#039;Yes&#039;&#039;&#039; to confirm, &#039;&#039;&#039;No&#039;&#039;&#039; or &#039;&#039;&#039;Cancel&#039;&#039;&#039; to cancel. &lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe017_EN.png|Datei:Zeitreihe017_EN.png]]&lt;br /&gt;
&lt;br /&gt;
The implementation of the values into the time series has been successful if the following confirmation window appears. Completing this step, saves the time series in the time series database as well as in the system data as a binary file, and exports the time series to the server. The editing window can now be closed.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe018_EN.png|Datei:Zeitreihe018_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Edit Values of the Time Series====&lt;br /&gt;
&lt;br /&gt;
Time series can be edited by right-clicking on the &#039;&#039;Time Series &amp;amp;rarr; Edit Values &amp;amp;rarr; Edit&#039;&#039;. The active time series and its appropriate date is displayed. Now you can select the time period for which you want to make changes to load it into the edit window. The data will be displayed accordingly. With the other buttons you can edit the time series as described under [[Special:MyLanguage/Belastungsdefinition / Modellinput#Werte zur Zeitreihe hinzufügen|&#039;&#039;Add Values to Time Series&#039;&#039;]].&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe019_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;mw-translate-fuzzy&amp;quot;&amp;gt;&lt;br /&gt;
====[[Special:MyLanguage/Werte in der Zeitreihe löschen|Delete Values of the Time Series]]====&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Display Time Series Graphically===&lt;br /&gt;
&lt;br /&gt;
A time series can be displayed graphically by right-clicking on &#039;&#039;Time Series &amp;amp;rarr; Charts&#039;&#039;. You have the choice between a [[Special:MyLanguage/Ganglinie|hydrograph]] (Time series chart) and a [[Special:MyLanguage/Dauerlinie|duration curve]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe020_EN.png]] [[Datei:Zeitreihe021_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Evaluate Time Series Statistically===&lt;br /&gt;
&lt;br /&gt;
Right-clicking &#039;&#039;Time Series &amp;amp;rarr; Statistics&#039;&#039; opens a statistics tool with which you can calculate severlal statistical measures for a predefined period. Furthermore, you can perform a low water or flood analysis. The results are displayed once you click on &#039;&#039;&#039;Calculate&#039;&#039;&#039; after entering the required data. &lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe022_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;mw-translate-fuzzy&amp;quot;&amp;gt;&lt;br /&gt;
===Import Time Series===&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;mw-translate-fuzzy&amp;quot;&amp;gt;&lt;br /&gt;
=== Export Time Series===&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;mw-translate-fuzzy&amp;quot;&amp;gt;&lt;br /&gt;
===Delete Time Series===&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;mw-translate-fuzzy&amp;quot;&amp;gt;&lt;br /&gt;
===Release Edit-Lock===&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Zeitreihenverwaltung/32/en&amp;diff=12983</id>
		<title>Translations:Zeitreihenverwaltung/32/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Zeitreihenverwaltung/32/en&amp;diff=12983"/>
		<updated>2021-08-30T10:43:21Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;|-&lt;br /&gt;
|&#039;&#039;Memo&#039;&#039;&lt;br /&gt;
|Description of the origin of the time series and other additional information&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Origin&#039;&#039;&lt;br /&gt;
|Origin of the time series&lt;br /&gt;
Choice of:&lt;br /&gt;
*derived&lt;br /&gt;
*measured&lt;br /&gt;
*imported&lt;br /&gt;
*manual&lt;br /&gt;
*simulated&lt;br /&gt;
*miscellaneous&lt;br /&gt;
*synthetic&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Type&#039;&#039;&lt;br /&gt;
|Hydrological, hydrometeorological, storage-dependent or geological variable &lt;br /&gt;
With this setting the time series is assigned to one of the 15 subfolders of the station.&lt;br /&gt;
Choice of:&lt;br /&gt;
*area &lt;br /&gt;
*discharge&lt;br /&gt;
*evaporation&lt;br /&gt;
*humidity&lt;br /&gt;
*mass movement&lt;br /&gt;
*precipitation&lt;br /&gt;
*pressure&lt;br /&gt;
*soil process&lt;br /&gt;
*storage &lt;br /&gt;
*sunshine &lt;br /&gt;
*temperature &lt;br /&gt;
*unknown&lt;br /&gt;
*velocity&lt;br /&gt;
*water level &lt;br /&gt;
*wind&lt;br /&gt;
|-&lt;br /&gt;
|Unit&lt;br /&gt;
|Unit of the variable&lt;br /&gt;
Choice of:&lt;br /&gt;
?,empty, number, class, mm/m, percent, h/d, 0/00, ml/l, mm, m, cm, km, hm, dm, l/ha, l/km², l/m², mNN, m², km², ha, cm², mm², dm², m³/m, m³, Tsd. m³, Mio. m³, l, hl, &lt;br /&gt;
km³, cm³, mm³, m/s, mm/d, mm/h, mm/min, l/s/km², m/h, m/d, l/s/ha, m/s², m³/s, l/s, m³/d, m³/h, l/h, l/d, °C, kg, g, mg, t, s, min, h, d, w, mon, a, Datum, &lt;br /&gt;
A, bar, pa, hpa, Grad, Rad, kg/m³, mg/l, g/l, l/kg, ml/g, Grad_C, kg/s, y/n&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Zeitreihenverwaltung/en&amp;diff=12982</id>
		<title>Zeitreihenverwaltung/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Zeitreihenverwaltung/en&amp;diff=12982"/>
		<updated>2021-08-30T10:43:09Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=Menüleiste Systemverwaltung|hoch=Hauptseite|nachher=Einzelfenster von Modellkomponenten}}&lt;br /&gt;
&lt;br /&gt;
Time series can be stored in TALSIM-NG&#039;s own time series manager, where they are classified by the type of data and the station they belong to. There they can be viewed graphically and edited tabularly. A basic statistics&#039; tool, which can calculate average values for a defined period of time as well as other statistics, is also integrated in the time series manager.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Opening the Time Series Manager===&lt;br /&gt;
&lt;br /&gt;
The time series manager can be accessed via the &#039;&#039;Menu bar &amp;amp;rarr; Time series &amp;amp;rarr; Time series manager&#039;&#039;. The &#039;&#039;&#039;Talsim-User Selection&#039;&#039;&#039; window, where you are required to choose a user to proceed, appears. If you want to create and edit time series, you should choose your username and confirm with &#039;&#039;&#039;OK&#039;&#039;&#039;. If you log in using another username, you can only see the stations and time series, but you cannot edit or delete them.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe001_EN.png|Datei:Zeitreihe001EN_.png|500px]] &lt;br /&gt;
[[Datei:Zeitreihe002_EN.png]]&lt;br /&gt;
&lt;br /&gt;
If you are logged in with your username and have not created any time series yet, an empty &#039;&#039;&#039;TalsminNG - TS Explorer&#039;&#039;&#039; opens. This explorer can be customized using &#039;&#039;&#039;View&#039;&#039;&#039;, &#039;&#039;&#039;Folder&#039;&#039;&#039;, as well as the &#039;&#039;&#039;folder icon&#039;&#039;&#039;. &lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe003_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Create New Station===&lt;br /&gt;
&lt;br /&gt;
Time series are principally assigned to stations, e.g. measuring stations. For this reason a station should be created first. To do this, right-click on the &#039;&#039;Explorer &amp;amp;rarr; New Station&#039;&#039;. A window, where you can enter the name of the station and confirm with &#039;&#039;&#039;OK&#039;&#039;&#039;, will appear.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe004_EN.png]] [[Datei:Zeitreihe005_EN.png|Datei:Zeitreihe005_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Subsequently, a new station, as well as 15 subfolders are created. These subfolders present the different types of the hydrological, hydrometeorological, or storage-dependent variables that can be saved as time series in the TS Explorer.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe006_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You have a choice of the following options when you right-click on the new station in the explorer.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width:70%&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;New Station&#039;&#039;&#039; 	||A new empty station with 15 subfolders is created. &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Edit Station&#039;&#039;&#039; 	||The dialog window &#039;&#039;Edit of a Talsim time series station&#039;&#039;, in which information about the selected station can be edited, is opened.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Delete Station&#039;&#039;&#039; ||The marked station and all associated time series are deleted. This operation cannot be undone.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Copy to Clipboard&#039;&#039;&#039; || The list of time series associated with the station as well as their metadata is copied to the clipboard.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;New Time Series&#039;&#039;&#039; ||A new time series associated with the selected station is created.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Release Edit-lock&#039;&#039;&#039; ||Releases the edit-lock of the station, so it can be edited by another user.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Create New Time Series===&lt;br /&gt;
&lt;br /&gt;
To create a time series, right-click on the &#039;&#039;Station &amp;amp;rarr; New Time Series&#039;&#039; in the [[Special:MyLanguage/Belastungsdefinition / Modellinput#Zeitreihenverwaltung|time series explorer]]. A window will open, prompting you to enter the name of the new time series. Confirm with &#039;&#039;&#039;OK&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe007_EN.png|Datei:Zeitreihe007_EN.png]]&lt;br /&gt;
&lt;br /&gt;
The following attributes are displayed for each time series in the explorer:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width:70%&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Name&#039;&#039;&#039; 	||Name of the time series.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;ID&#039;&#039;&#039; 	||Identification number of a time series. ID corresponds to the ID of the binary file, stored in the system data. Caution: Not to be confused with the ID of a simulation in the model and on the server.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Type&#039;&#039;&#039; ||Hydrological, hydrometeorological, storage-dependent or geological variable. With this setting the time series is assigned to one of the 15 subfolders of the station. Default value: discharge.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Unit&#039;&#039;&#039; ||Unit of the values. Default value: m³/s.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Interpretation&#039;&#039;&#039; ||Information about the time series values, i.e. how to understand the timestamp and the value stored in it. Caution: wrongly set interpretations inevitably lead to incorrect results. For example, precipitation [mm] is usually a sum per timestep. Default value: Current_value (linear_interpolation)&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Origin&#039;&#039;&#039; ||Origin of the time series. Default value: measured.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;from&#039;&#039;&#039; ||Date and time of the start of the time series. Default value: Day and time of creation.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;to&#039;&#039;&#039; ||Date and time of the end of the time series. Default value: Day and time of creation.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Data points&#039;&#039;&#039; ||Number of data points. Default value: 0&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe008_EN.png]]&lt;br /&gt;
&lt;br /&gt;
The created time series is assigned the chosen name and a consecutive ID number. The other attributes are filled with the default values.&lt;br /&gt;
&lt;br /&gt;
You can use the following buttons if you right-click on the time series in the explorer.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width:70%&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Edit Time Series&#039;&#039;&#039; ||The selected time series can be edited.  &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Chart&#039;&#039;&#039; 	||The time series can be displayed as a graph over time or as a duration curve.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Edit Values&#039;&#039;&#039; ||Values with date are added to the selected time series. Values can also be edited or deleted.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Statistics&#039;&#039;&#039; ||Calculates a statistical overview of the time series.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Import Time Series&#039;&#039;&#039; ||An existing time series can be imported.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Export Time Series&#039;&#039;&#039; ||The selected time series can be exported.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Delete Time Series&#039;&#039;&#039; ||The selected time series is deleted. This operation cannot be undone.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Release Edit-lock&#039;&#039;&#039; ||Releases the edit-lock of the time series, so it can be edited by another user..&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Refresh Attributes&#039;&#039;&#039; ||After adjusting the attributes of a time series, those attributes are updated in the explorer.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Edit Time Series&lt;br /&gt;
&lt;br /&gt;
To adjust the attributes of a time series, right-click on &#039;&#039;Time Series &amp;amp;rarr; Edit Time Series&#039;&#039; in the time series manager. &lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe009_EN.png]]&lt;br /&gt;
&lt;br /&gt;
The following dialog window, where you can edit the attributes, opens. The attributes assigned to identification and settings, which are displayed in black, can be adjusted with a double-click. By clicking OK all time series attributes can be saved. &lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe010_EN.png]]&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width:70%&amp;quot;&lt;br /&gt;
|- &lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot; style=&amp;quot;text-align:center&amp;quot; |&#039;&#039;&#039;Identification&#039;&#039;&#039; &lt;br /&gt;
|&#039;&#039;Description&#039;&#039; &lt;br /&gt;
|Description of the time series &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Name&#039;&#039; &lt;br /&gt;
|Name of the time series&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;8&amp;quot; style=&amp;quot;text-align:center&amp;quot;|&#039;&#039;&#039;Settings&#039;&#039;&#039; &lt;br /&gt;
|&#039;&#039;Altitude masl&#039;&#039; &lt;br /&gt;
|Height of the measuring station in meters above sea level&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Coordinate-X&#039;&#039;&lt;br /&gt;
|X-coordinate of the measuring station &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Coordinate-Y&#039;&#039;&lt;br /&gt;
|Y-coordinate of the measuring station  &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Interpretation&#039;&#039; &lt;br /&gt;
|Information about the time series values, i.e. how to understand the timestamp and the value stored in it. Caution: wrongly defined interpretations inevitably lead to incorrect results. &lt;br /&gt;
Choice of: [[Datei:00036_EN.png|mini]]&lt;br /&gt;
*BlockLeft &lt;br /&gt;
*BlockRight&lt;br /&gt;
*Instantaneous_(Linear_Interpolation)&lt;br /&gt;
*Cumulative &lt;br /&gt;
*CumulativePerTimeStep&lt;br /&gt;
*Undefined&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Memo&#039;&#039;&lt;br /&gt;
|Description of the origin of the time series and other additional information&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Origin&#039;&#039;&lt;br /&gt;
|Origin of the time series&lt;br /&gt;
Choice of:&lt;br /&gt;
*derived&lt;br /&gt;
*measured&lt;br /&gt;
*imported&lt;br /&gt;
*manual&lt;br /&gt;
*simulated&lt;br /&gt;
*miscellaneous&lt;br /&gt;
*synthetic&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Type&#039;&#039;&lt;br /&gt;
|Hydrological, hydrometeorological, reservoir-dependent or geological variable &lt;br /&gt;
With this setting the time series is assigned to one of the 15 subfolders of the station.&lt;br /&gt;
Choice of:&lt;br /&gt;
*area &lt;br /&gt;
*discharge&lt;br /&gt;
*evaporation&lt;br /&gt;
*humidity&lt;br /&gt;
*mass movement&lt;br /&gt;
*precipitation&lt;br /&gt;
*pressure&lt;br /&gt;
*soil process&lt;br /&gt;
*storage &lt;br /&gt;
*sunshine &lt;br /&gt;
*temperature &lt;br /&gt;
*unknown&lt;br /&gt;
*velocity&lt;br /&gt;
*water level &lt;br /&gt;
*wind&lt;br /&gt;
|-&lt;br /&gt;
|Unit&lt;br /&gt;
|Unit of the variable&lt;br /&gt;
Choice of:&lt;br /&gt;
?,empty, number, class, mm/m, percent, h/d, 0/00, ml/l, mm, m, cm, km, hm, dm, l/ha, l/km², l/m², mNN, m², km², ha, cm², mm², dm², m³/m, m³, Tsd. m³, Mio. m³, l, hl, &lt;br /&gt;
km³, cm³, mm³, m/s, mm/d, mm/h, mm/min, l/s/km², m/h, m/d, l/s/ha, m/s², m³/s, l/s, m³/d, m³/h, l/h, l/d, °C, kg, g, mg, t, s, min, h, d, w, mon, a, Datum, &lt;br /&gt;
A, bar, pa, hpa, Grad, Rad, kg/m³, mg/l, g/l, l/kg, ml/g, Grad_C, kg/s, y/n&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Time Series Values===&lt;br /&gt;
&lt;br /&gt;
After a new time series is created and edited, values can be added to it. To do this, right-click on the &#039;&#039;Time Series &amp;amp;rarr; Edit Value&#039;&#039;. If a time series with values already exists, the values can be edited or deleted. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe0011_EN.png]]&lt;br /&gt;
&lt;br /&gt;
You can use the following buttons:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Edit&#039;&#039;&#039; ||Selected values of the time series can be edited.  &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Add&#039;&#039;&#039; ||Values can be added to the time series.&lt;br /&gt;
|-.&lt;br /&gt;
|&#039;&#039;&#039;Delete&#039;&#039;&#039; ||Selected values of the time series can be deleted. This operation cannot be undone.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Add Values to Time Series====&lt;br /&gt;
&lt;br /&gt;
To add new values to the time series, click on &#039;&#039;&#039;add&#039;&#039;&#039;. The following &#039;&#039;TalsimNGZreProvider&#039;&#039; window opens. This indicates that the time series does not contain any values yet, and is, therefore, not stored on the server on in the database. By clicking &#039;&#039;&#039;OK&#039;&#039;&#039; the window for editing the time series values opens. &lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe012_EN.png|Datei:Zeitreihe012_EN.png]] [[Datei:Zeitreihe013_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here you can use the following buttons:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Insert Row&#039;&#039;&#039; ||A row is inserted above the selected cell. &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Add Row&#039;&#039;&#039; || A row is added to the end of the time series.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Remove Row&#039;&#039;&#039; ||The selected row is removed.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Graph&#039;&#039;&#039; ||The time series is displayed graphically.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Check dates&#039;&#039;&#039; ||The date of the time series is checked. This means that the date must be ascending in time.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Write values&#039;&#039;&#039; ||The time series and its values are stored on the server and in the database. Additionally, a binary file, named after the ID of the time series, is created in the system data.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Delete values&#039;&#039;&#039; ||All values are deleted.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The &#039;Edit time series&#039; window shows the active time series, as well as the date, which by default corresponds to the date of creating the time series, unless it has been manually changed. Here you can manually enter a date and its corresponding value. You can also copy a time series with dates and values e.g. from Excel and click on the first cell of the table and paste it there (key combination: Ctrl+V).&lt;br /&gt;
&lt;br /&gt;
When the values are inserted, the time series can be displayed using &#039;&#039;&#039;Graph&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe014_EN.png|Datei:Zeitreihe014_EN.png]]&lt;br /&gt;
&lt;br /&gt;
In the next step the date is checked. If the dates are ascending, a window with &amp;quot;Check successful!&amp;quot; will appear. Otherwise an error message will be displayed.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe015_EN.png|Datei:Zeitreihe015_EN.png]] [[Datei:Zeitreihe016_EN.png|Datei:Zeitreihe016_EN.png]]&lt;br /&gt;
&lt;br /&gt;
If all values are complete and the date is successfully checked, the values are written. In the appearing window, click &#039;&#039;&#039;Yes&#039;&#039;&#039; to confirm, &#039;&#039;&#039;No&#039;&#039;&#039; or &#039;&#039;&#039;Cancel&#039;&#039;&#039; to cancel. &lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe017_EN.png|Datei:Zeitreihe017_EN.png]]&lt;br /&gt;
&lt;br /&gt;
The implementation of the values into the time series has been successful if the following confirmation window appears. Completing this step, saves the time series in the time series database as well as in the system data as a binary file, and exports the time series to the server. The editing window can now be closed.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe018_EN.png|Datei:Zeitreihe018_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Edit Values of the Time Series====&lt;br /&gt;
&lt;br /&gt;
Time series can be edited by right-clicking on the &#039;&#039;Time Series &amp;amp;rarr; Edit Values &amp;amp;rarr; Edit&#039;&#039;. The active time series and its appropriate date is displayed. Now you can select the time period for which you want to make changes to load it into the edit window. The data will be displayed accordingly. With the other buttons you can edit the time series as described under [[Special:MyLanguage/Belastungsdefinition / Modellinput#Werte zur Zeitreihe hinzufügen|&#039;&#039;Add Values to Time Series&#039;&#039;]].&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe019_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;mw-translate-fuzzy&amp;quot;&amp;gt;&lt;br /&gt;
====[[Special:MyLanguage/Werte in der Zeitreihe löschen|Delete Values of the Time Series]]====&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Display Time Series Graphically===&lt;br /&gt;
&lt;br /&gt;
A time series can be displayed graphically by right-clicking on &#039;&#039;Time Series &amp;amp;rarr; Charts&#039;&#039;. You have the choice between a [[Special:MyLanguage/Ganglinie|hydrograph]] (Time series chart) and a [[Special:MyLanguage/Dauerlinie|duration curve]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe020_EN.png]] [[Datei:Zeitreihe021_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Evaluate Time Series Statistically===&lt;br /&gt;
&lt;br /&gt;
Right-clicking &#039;&#039;Time Series &amp;amp;rarr; Statistics&#039;&#039; opens a statistics tool with which you can calculate severlal statistical measures for a predefined period. Furthermore, you can perform a low water or flood analysis. The results are displayed once you click on &#039;&#039;&#039;Calculate&#039;&#039;&#039; after entering the required data. &lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe022_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;mw-translate-fuzzy&amp;quot;&amp;gt;&lt;br /&gt;
===Import Time Series===&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;mw-translate-fuzzy&amp;quot;&amp;gt;&lt;br /&gt;
=== Export Time Series===&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;mw-translate-fuzzy&amp;quot;&amp;gt;&lt;br /&gt;
===Delete Time Series===&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;mw-translate-fuzzy&amp;quot;&amp;gt;&lt;br /&gt;
===Release Edit-Lock===&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Zeitreihenverwaltung/19/en&amp;diff=12981</id>
		<title>Translations:Zeitreihenverwaltung/19/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Zeitreihenverwaltung/19/en&amp;diff=12981"/>
		<updated>2021-08-30T10:43:09Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width:70%&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Name&#039;&#039;&#039; 	||Name of the time series.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;ID&#039;&#039;&#039; 	||Identification number of a time series. ID corresponds to the ID of the binary file, stored in the system data. Caution: Not to be confused with the ID of a simulation in the model and on the server.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Type&#039;&#039;&#039; ||Hydrological, hydrometeorological, storage-dependent or geological variable. With this setting the time series is assigned to one of the 15 subfolders of the station. Default value: discharge.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Unit&#039;&#039;&#039; ||Unit of the values. Default value: m³/s.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Interpretation&#039;&#039;&#039; ||Information about the time series values, i.e. how to understand the timestamp and the value stored in it. Caution: wrongly set interpretations inevitably lead to incorrect results. For example, precipitation [mm] is usually a sum per timestep. Default value: Current_value (linear_interpolation)&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Origin&#039;&#039;&#039; ||Origin of the time series. Default value: measured.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;from&#039;&#039;&#039; ||Date and time of the start of the time series. Default value: Day and time of creation.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;to&#039;&#039;&#039; ||Date and time of the end of the time series. Default value: Day and time of creation.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Data points&#039;&#039;&#039; ||Number of data points. Default value: 0&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Zeitreihenverwaltung/en&amp;diff=12980</id>
		<title>Zeitreihenverwaltung/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Zeitreihenverwaltung/en&amp;diff=12980"/>
		<updated>2021-08-30T10:42:51Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=Menüleiste Systemverwaltung|hoch=Hauptseite|nachher=Einzelfenster von Modellkomponenten}}&lt;br /&gt;
&lt;br /&gt;
Time series can be stored in TALSIM-NG&#039;s own time series manager, where they are classified by the type of data and the station they belong to. There they can be viewed graphically and edited tabularly. A basic statistics&#039; tool, which can calculate average values for a defined period of time as well as other statistics, is also integrated in the time series manager.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Opening the Time Series Manager===&lt;br /&gt;
&lt;br /&gt;
The time series manager can be accessed via the &#039;&#039;Menu bar &amp;amp;rarr; Time series &amp;amp;rarr; Time series manager&#039;&#039;. The &#039;&#039;&#039;Talsim-User Selection&#039;&#039;&#039; window, where you are required to choose a user to proceed, appears. If you want to create and edit time series, you should choose your username and confirm with &#039;&#039;&#039;OK&#039;&#039;&#039;. If you log in using another username, you can only see the stations and time series, but you cannot edit or delete them.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe001_EN.png|Datei:Zeitreihe001EN_.png|500px]] &lt;br /&gt;
[[Datei:Zeitreihe002_EN.png]]&lt;br /&gt;
&lt;br /&gt;
If you are logged in with your username and have not created any time series yet, an empty &#039;&#039;&#039;TalsminNG - TS Explorer&#039;&#039;&#039; opens. This explorer can be customized using &#039;&#039;&#039;View&#039;&#039;&#039;, &#039;&#039;&#039;Folder&#039;&#039;&#039;, as well as the &#039;&#039;&#039;folder icon&#039;&#039;&#039;. &lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe003_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Create New Station===&lt;br /&gt;
&lt;br /&gt;
Time series are principally assigned to stations, e.g. measuring stations. For this reason a station should be created first. To do this, right-click on the &#039;&#039;Explorer &amp;amp;rarr; New Station&#039;&#039;. A window, where you can enter the name of the station and confirm with &#039;&#039;&#039;OK&#039;&#039;&#039;, will appear.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe004_EN.png]] [[Datei:Zeitreihe005_EN.png|Datei:Zeitreihe005_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Subsequently, a new station, as well as 15 subfolders are created. These subfolders present the different types of the hydrological, hydrometeorological, or storage-dependent variables that can be saved as time series in the TS Explorer.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe006_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You have a choice of the following options when you right-click on the new station in the explorer.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width:70%&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;New Station&#039;&#039;&#039; 	||A new empty station with 15 subfolders is created. &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Edit Station&#039;&#039;&#039; 	||The dialog window &#039;&#039;Edit of a Talsim time series station&#039;&#039;, in which information about the selected station can be edited, is opened.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Delete Station&#039;&#039;&#039; ||The marked station and all associated time series are deleted. This operation cannot be undone.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Copy to Clipboard&#039;&#039;&#039; || The list of time series associated with the station as well as their metadata is copied to the clipboard.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;New Time Series&#039;&#039;&#039; ||A new time series associated with the selected station is created.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Release Edit-lock&#039;&#039;&#039; ||Releases the edit-lock of the station, so it can be edited by another user.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Create New Time Series===&lt;br /&gt;
&lt;br /&gt;
To create a time series, right-click on the &#039;&#039;Station &amp;amp;rarr; New Time Series&#039;&#039; in the [[Special:MyLanguage/Belastungsdefinition / Modellinput#Zeitreihenverwaltung|time series explorer]]. A window will open, prompting you to enter the name of the new time series. Confirm with &#039;&#039;&#039;OK&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe007_EN.png|Datei:Zeitreihe007_EN.png]]&lt;br /&gt;
&lt;br /&gt;
The following attributes are displayed for each time series in the explorer:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width:70%&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Name&#039;&#039;&#039; 	||Name of the time series.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;ID&#039;&#039;&#039; 	||Identification number of a time series. ID corresponds to the ID of the binary file, stored in the system data. Caution: Not to be confused with the ID of a simulation in the model and on the server.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Type&#039;&#039;&#039; ||Hydrological, hydrometeorological, reservoir-dependent or geological variable. With this setting the time series is assigned to one of the 15 subfolders of the station. Default value: discharge.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Unit&#039;&#039;&#039; ||Unit of the values. Default value: m³/s.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Interpretation&#039;&#039;&#039; ||Information about the time series values, i.e. how to understand the timestamp and the value stored in it. Caution: wrongly set interpretations inevitably lead to incorrect results. For example, precipitation [mm] is usually a sum per timestep. Default value: Current_value (linear_interpolation)&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Origin&#039;&#039;&#039; ||Origin of the time series. Default value: measured.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;from&#039;&#039;&#039; ||Date and time of the start of the time series. Default value: Day and time of creation.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;to&#039;&#039;&#039; ||Date and time of the end of the time series. Default value: Day and time of creation.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Data points&#039;&#039;&#039; ||Number of data points. Default value: 0&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe008_EN.png]]&lt;br /&gt;
&lt;br /&gt;
The created time series is assigned the chosen name and a consecutive ID number. The other attributes are filled with the default values.&lt;br /&gt;
&lt;br /&gt;
You can use the following buttons if you right-click on the time series in the explorer.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width:70%&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Edit Time Series&#039;&#039;&#039; ||The selected time series can be edited.  &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Chart&#039;&#039;&#039; 	||The time series can be displayed as a graph over time or as a duration curve.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Edit Values&#039;&#039;&#039; ||Values with date are added to the selected time series. Values can also be edited or deleted.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Statistics&#039;&#039;&#039; ||Calculates a statistical overview of the time series.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Import Time Series&#039;&#039;&#039; ||An existing time series can be imported.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Export Time Series&#039;&#039;&#039; ||The selected time series can be exported.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Delete Time Series&#039;&#039;&#039; ||The selected time series is deleted. This operation cannot be undone.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Release Edit-lock&#039;&#039;&#039; ||Releases the edit-lock of the time series, so it can be edited by another user..&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Refresh Attributes&#039;&#039;&#039; ||After adjusting the attributes of a time series, those attributes are updated in the explorer.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Edit Time Series&lt;br /&gt;
&lt;br /&gt;
To adjust the attributes of a time series, right-click on &#039;&#039;Time Series &amp;amp;rarr; Edit Time Series&#039;&#039; in the time series manager. &lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe009_EN.png]]&lt;br /&gt;
&lt;br /&gt;
The following dialog window, where you can edit the attributes, opens. The attributes assigned to identification and settings, which are displayed in black, can be adjusted with a double-click. By clicking OK all time series attributes can be saved. &lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe010_EN.png]]&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width:70%&amp;quot;&lt;br /&gt;
|- &lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot; style=&amp;quot;text-align:center&amp;quot; |&#039;&#039;&#039;Identification&#039;&#039;&#039; &lt;br /&gt;
|&#039;&#039;Description&#039;&#039; &lt;br /&gt;
|Description of the time series &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Name&#039;&#039; &lt;br /&gt;
|Name of the time series&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;8&amp;quot; style=&amp;quot;text-align:center&amp;quot;|&#039;&#039;&#039;Settings&#039;&#039;&#039; &lt;br /&gt;
|&#039;&#039;Altitude masl&#039;&#039; &lt;br /&gt;
|Height of the measuring station in meters above sea level&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Coordinate-X&#039;&#039;&lt;br /&gt;
|X-coordinate of the measuring station &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Coordinate-Y&#039;&#039;&lt;br /&gt;
|Y-coordinate of the measuring station  &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Interpretation&#039;&#039; &lt;br /&gt;
|Information about the time series values, i.e. how to understand the timestamp and the value stored in it. Caution: wrongly defined interpretations inevitably lead to incorrect results. &lt;br /&gt;
Choice of: [[Datei:00036_EN.png|mini]]&lt;br /&gt;
*BlockLeft &lt;br /&gt;
*BlockRight&lt;br /&gt;
*Instantaneous_(Linear_Interpolation)&lt;br /&gt;
*Cumulative &lt;br /&gt;
*CumulativePerTimeStep&lt;br /&gt;
*Undefined&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Memo&#039;&#039;&lt;br /&gt;
|Description of the origin of the time series and other additional information&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Origin&#039;&#039;&lt;br /&gt;
|Origin of the time series&lt;br /&gt;
Choice of:&lt;br /&gt;
*derived&lt;br /&gt;
*measured&lt;br /&gt;
*imported&lt;br /&gt;
*manual&lt;br /&gt;
*simulated&lt;br /&gt;
*miscellaneous&lt;br /&gt;
*synthetic&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;Type&#039;&#039;&lt;br /&gt;
|Hydrological, hydrometeorological, reservoir-dependent or geological variable &lt;br /&gt;
With this setting the time series is assigned to one of the 15 subfolders of the station.&lt;br /&gt;
Choice of:&lt;br /&gt;
*area &lt;br /&gt;
*discharge&lt;br /&gt;
*evaporation&lt;br /&gt;
*humidity&lt;br /&gt;
*mass movement&lt;br /&gt;
*precipitation&lt;br /&gt;
*pressure&lt;br /&gt;
*soil process&lt;br /&gt;
*storage &lt;br /&gt;
*sunshine &lt;br /&gt;
*temperature &lt;br /&gt;
*unknown&lt;br /&gt;
*velocity&lt;br /&gt;
*water level &lt;br /&gt;
*wind&lt;br /&gt;
|-&lt;br /&gt;
|Unit&lt;br /&gt;
|Unit of the variable&lt;br /&gt;
Choice of:&lt;br /&gt;
?,empty, number, class, mm/m, percent, h/d, 0/00, ml/l, mm, m, cm, km, hm, dm, l/ha, l/km², l/m², mNN, m², km², ha, cm², mm², dm², m³/m, m³, Tsd. m³, Mio. m³, l, hl, &lt;br /&gt;
km³, cm³, mm³, m/s, mm/d, mm/h, mm/min, l/s/km², m/h, m/d, l/s/ha, m/s², m³/s, l/s, m³/d, m³/h, l/h, l/d, °C, kg, g, mg, t, s, min, h, d, w, mon, a, Datum, &lt;br /&gt;
A, bar, pa, hpa, Grad, Rad, kg/m³, mg/l, g/l, l/kg, ml/g, Grad_C, kg/s, y/n&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Time Series Values===&lt;br /&gt;
&lt;br /&gt;
After a new time series is created and edited, values can be added to it. To do this, right-click on the &#039;&#039;Time Series &amp;amp;rarr; Edit Value&#039;&#039;. If a time series with values already exists, the values can be edited or deleted. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe0011_EN.png]]&lt;br /&gt;
&lt;br /&gt;
You can use the following buttons:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Edit&#039;&#039;&#039; ||Selected values of the time series can be edited.  &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Add&#039;&#039;&#039; ||Values can be added to the time series.&lt;br /&gt;
|-.&lt;br /&gt;
|&#039;&#039;&#039;Delete&#039;&#039;&#039; ||Selected values of the time series can be deleted. This operation cannot be undone.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Add Values to Time Series====&lt;br /&gt;
&lt;br /&gt;
To add new values to the time series, click on &#039;&#039;&#039;add&#039;&#039;&#039;. The following &#039;&#039;TalsimNGZreProvider&#039;&#039; window opens. This indicates that the time series does not contain any values yet, and is, therefore, not stored on the server on in the database. By clicking &#039;&#039;&#039;OK&#039;&#039;&#039; the window for editing the time series values opens. &lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe012_EN.png|Datei:Zeitreihe012_EN.png]] [[Datei:Zeitreihe013_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here you can use the following buttons:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Insert Row&#039;&#039;&#039; ||A row is inserted above the selected cell. &lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Add Row&#039;&#039;&#039; || A row is added to the end of the time series.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Remove Row&#039;&#039;&#039; ||The selected row is removed.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Graph&#039;&#039;&#039; ||The time series is displayed graphically.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Check dates&#039;&#039;&#039; ||The date of the time series is checked. This means that the date must be ascending in time.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Write values&#039;&#039;&#039; ||The time series and its values are stored on the server and in the database. Additionally, a binary file, named after the ID of the time series, is created in the system data.&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Delete values&#039;&#039;&#039; ||All values are deleted.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The &#039;Edit time series&#039; window shows the active time series, as well as the date, which by default corresponds to the date of creating the time series, unless it has been manually changed. Here you can manually enter a date and its corresponding value. You can also copy a time series with dates and values e.g. from Excel and click on the first cell of the table and paste it there (key combination: Ctrl+V).&lt;br /&gt;
&lt;br /&gt;
When the values are inserted, the time series can be displayed using &#039;&#039;&#039;Graph&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe014_EN.png|Datei:Zeitreihe014_EN.png]]&lt;br /&gt;
&lt;br /&gt;
In the next step the date is checked. If the dates are ascending, a window with &amp;quot;Check successful!&amp;quot; will appear. Otherwise an error message will be displayed.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe015_EN.png|Datei:Zeitreihe015_EN.png]] [[Datei:Zeitreihe016_EN.png|Datei:Zeitreihe016_EN.png]]&lt;br /&gt;
&lt;br /&gt;
If all values are complete and the date is successfully checked, the values are written. In the appearing window, click &#039;&#039;&#039;Yes&#039;&#039;&#039; to confirm, &#039;&#039;&#039;No&#039;&#039;&#039; or &#039;&#039;&#039;Cancel&#039;&#039;&#039; to cancel. &lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe017_EN.png|Datei:Zeitreihe017_EN.png]]&lt;br /&gt;
&lt;br /&gt;
The implementation of the values into the time series has been successful if the following confirmation window appears. Completing this step, saves the time series in the time series database as well as in the system data as a binary file, and exports the time series to the server. The editing window can now be closed.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe018_EN.png|Datei:Zeitreihe018_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Edit Values of the Time Series====&lt;br /&gt;
&lt;br /&gt;
Time series can be edited by right-clicking on the &#039;&#039;Time Series &amp;amp;rarr; Edit Values &amp;amp;rarr; Edit&#039;&#039;. The active time series and its appropriate date is displayed. Now you can select the time period for which you want to make changes to load it into the edit window. The data will be displayed accordingly. With the other buttons you can edit the time series as described under [[Special:MyLanguage/Belastungsdefinition / Modellinput#Werte zur Zeitreihe hinzufügen|&#039;&#039;Add Values to Time Series&#039;&#039;]].&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe019_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;mw-translate-fuzzy&amp;quot;&amp;gt;&lt;br /&gt;
====[[Special:MyLanguage/Werte in der Zeitreihe löschen|Delete Values of the Time Series]]====&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Display Time Series Graphically===&lt;br /&gt;
&lt;br /&gt;
A time series can be displayed graphically by right-clicking on &#039;&#039;Time Series &amp;amp;rarr; Charts&#039;&#039;. You have the choice between a [[Special:MyLanguage/Ganglinie|hydrograph]] (Time series chart) and a [[Special:MyLanguage/Dauerlinie|duration curve]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe020_EN.png]] [[Datei:Zeitreihe021_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Evaluate Time Series Statistically===&lt;br /&gt;
&lt;br /&gt;
Right-clicking &#039;&#039;Time Series &amp;amp;rarr; Statistics&#039;&#039; opens a statistics tool with which you can calculate severlal statistical measures for a predefined period. Furthermore, you can perform a low water or flood analysis. The results are displayed once you click on &#039;&#039;&#039;Calculate&#039;&#039;&#039; after entering the required data. &lt;br /&gt;
&lt;br /&gt;
[[Datei:Zeitreihe022_EN.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;mw-translate-fuzzy&amp;quot;&amp;gt;&lt;br /&gt;
===Import Time Series===&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;mw-translate-fuzzy&amp;quot;&amp;gt;&lt;br /&gt;
=== Export Time Series===&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;mw-translate-fuzzy&amp;quot;&amp;gt;&lt;br /&gt;
===Delete Time Series===&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;mw-translate-fuzzy&amp;quot;&amp;gt;&lt;br /&gt;
===Release Edit-Lock===&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Zeitreihenverwaltung/11/en&amp;diff=12979</id>
		<title>Translations:Zeitreihenverwaltung/11/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Zeitreihenverwaltung/11/en&amp;diff=12979"/>
		<updated>2021-08-30T10:42:50Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Subsequently, a new station, as well as 15 subfolders are created. These subfolders present the different types of the hydrological, hydrometeorological, or storage-dependent variables that can be saved as time series in the TS Explorer.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Fenster_der_Systemelemente/en&amp;diff=12978</id>
		<title>Fenster der Systemelemente/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Fenster_der_Systemelemente/en&amp;diff=12978"/>
		<updated>2021-08-30T10:42:17Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=|hoch=Einzelfenster von Modellkomponenten|nachher=Einzugsgebietsfenster}}&lt;br /&gt;
&lt;br /&gt;
The system elements in Talsim-NG are filled by using two types of windows. &lt;br /&gt;
&lt;br /&gt;
==General Window of System Elements==&lt;br /&gt;
&lt;br /&gt;
The settings, which are, to a large extent, similar for all elements, are predefined in a general window. This window opens automatically when creating a new system element. It contains the following tabs:&lt;br /&gt;
&lt;br /&gt;
;Key&lt;br /&gt;
: 4-digit unique key of the element; the first letter is determined by the element type.&lt;br /&gt;
: Short description of the system element.&lt;br /&gt;
;Outflows&lt;br /&gt;
: Keys of the outflow elements. Depending on the type of element there is the possibility to assign one or more outflow elements. To do so, select the corresponding element from the list on the right side of the window and assign it to the desired outflow using the arrow key.&lt;br /&gt;
;Flow direction&lt;br /&gt;
: Display of the flow direction in the flow network map. This setting has no effect on the calculation.&lt;br /&gt;
;Symbol&lt;br /&gt;
: Symbol which shall represent the system element in the system plan. For each element type there are different options with a short description of what the symbols are intended for. The symbols have no influence on the calculation of the system element and a differentiation within an element type only serves to improve the clarity of the flow network map. Therefore, each user can make a distinction according to one&#039;s own criteria or use the default symbol.&lt;br /&gt;
;Description&lt;br /&gt;
: Detailed description of the system element.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery widths=200px mode=&amp;quot;nolines&amp;quot;&amp;gt;&lt;br /&gt;
Datei:Fenster_Systemelemente_Kennung_EN.png|Key&lt;br /&gt;
Datei:Fenster_Systemelemente_Abläufe_EN.png|Outflows&lt;br /&gt;
Datei:Fenster_Systemelemente_Fließrichtung_EN.png|Flow direction&lt;br /&gt;
Datei:Fenster_Systemelemente_Symbol_EN.png|Symbol&lt;br /&gt;
Datei:Fenster_Systemelemente_Beschreibung_EN.png|Description&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Later, this window can be opened by right-clicking on the system element and selecting &#039;&#039;Key&#039;&#039;, &#039;&#039;Outflows&#039;&#039; or &#039;&#039;Flow direction&#039;&#039; from the appearing menu, also allowing changes to the settings.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Properties of System Elements==&lt;br /&gt;
&lt;br /&gt;
The second window shows the properties of a system element which will differ for each element type. The window contains the calculation methods for the system element, as well as the corresponding characteristics and parameters.&lt;br /&gt;
&lt;br /&gt;
*[[Special:MyLanguage/Einzugsgebietsfenster|Sub-basin window]]&lt;br /&gt;
*[[Special:MyLanguage/Einzeleinleiterfenster|Point source window]]&lt;br /&gt;
*[[Special:MyLanguage/Transportstreckenfenster|Transport element window]]&lt;br /&gt;
*[[Special:MyLanguage/Verbraucherfenster|Consumer window]]&lt;br /&gt;
*[[Special:MyLanguage/Verzweigungsfenster|Diversion window]]&lt;br /&gt;
*[[Special:MyLanguage/Speicherfenster|Storage window]]&lt;br /&gt;
&lt;br /&gt;
The properties can be opened by double-clicking on the system element or by right-clicking &amp;amp;rarr; &#039;&#039;Properties&#039;&#039;.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Fenster_der_Systemelemente/10/en&amp;diff=12977</id>
		<title>Translations:Fenster der Systemelemente/10/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Fenster_der_Systemelemente/10/en&amp;diff=12977"/>
		<updated>2021-08-30T10:42:16Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;*[[Special:MyLanguage/Einzugsgebietsfenster|Sub-basin window]]&lt;br /&gt;
*[[Special:MyLanguage/Einzeleinleiterfenster|Point source window]]&lt;br /&gt;
*[[Special:MyLanguage/Transportstreckenfenster|Transport element window]]&lt;br /&gt;
*[[Special:MyLanguage/Verbraucherfenster|Consumer window]]&lt;br /&gt;
*[[Special:MyLanguage/Verzweigungsfenster|Diversion window]]&lt;br /&gt;
*[[Special:MyLanguage/Speicherfenster|Storage window]]&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Anwendungsbeispiel:_Umsetzung_eines_Betriebsplans/en&amp;diff=12976</id>
		<title>Anwendungsbeispiel: Umsetzung eines Betriebsplans/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Anwendungsbeispiel:_Umsetzung_eines_Betriebsplans/en&amp;diff=12976"/>
		<updated>2021-08-30T10:41:27Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=Berechungsschema/ Implementierung der Betriebsregeln|hoch=Betriebsregelkonzept|nachher=Begriffsdefinitionen}}&lt;br /&gt;
&lt;br /&gt;
Taking the [https://de.wikipedia.org/wiki/Wehebachtalsperre  Wehebach-Dam] as an example of use, the implementation of an operating plan in accordance with applying laws is illustrated.&lt;br /&gt;
&lt;br /&gt;
The Wehebach-Dam is a multi-purpose storage used for water supply and flood protection. In addition, a standard discharge of 100 l/s to the downstream watercourse is to be maintained. The operator of the dam is the [http://www.wver.de Water association Eifel-Rur]. The operation responsibilities include the drinking water supply of the greater Aachen area, the northern Eifel region and the supply of service water for several industrial companies. The catchment area of the dam is 43.61 km², the average annual inflow is 21 million m³, and the storage capacity is 119.3%. Built as a rockfill dam, the construction of the storage was completed in 1983.&lt;br /&gt;
&lt;br /&gt;
The following operating plan was drawn up for the Wehebach-Dam:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;Characteristics of the dam:&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:Max. content at crest level: 27.1M m³&lt;br /&gt;
:Capacity to the spillway: 25.06M m³&lt;br /&gt;
:Capacity level (normal water level): see flood control areas&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;Release volume for water supply:&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The storage provides two water supply companies with drinking water. The companies request water via daily demand values. Concerning the water supply, it is set that up to 11 million m³ must be provided annually as drinking water, of which no more than 2.5 million m³ may be discharged each month.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;Standard discharge:&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The standard discharge is intended to provide a minimum flow downstream of the dam and is set depending on the inflow, as follows: &lt;br /&gt;
&lt;br /&gt;
:{| cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot;&lt;br /&gt;
| &amp;amp;nbsp; || Inflow || &amp;amp;ge; 200 l/s || &amp;amp;rarr; || Standard discharge || = || 200 l/s &lt;br /&gt;
|- &lt;br /&gt;
| 100 l/s &amp;amp;le; || Inflow || &amp;amp;lt; 200 l/s || &amp;amp;rarr; || Standard discharge || = || Inflow &lt;br /&gt;
|- &lt;br /&gt;
| &amp;amp;nbsp; || Inflow || &amp;amp;lt; 100 l/s || &amp;amp;rarr; || Standard discharge || = || 100 l/s &lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
Every water resources management year, not later than the end of March, 4 m³/s must be discharged to the downstream watercourse as a flushing wave over a period of 6 hours.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;Flood control areas:&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
To ensure sufficing flood protection, a time-variable pool-based flood level is defined. The lower limit of the flood control areas is defined as the capacity level.&lt;br /&gt;
&lt;br /&gt;
:{| cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot;&lt;br /&gt;
| 1.10. - 31.10. || Flood control area || = 1.00M m³ || Capacity level || = 24.06M m³&lt;br /&gt;
|- &lt;br /&gt;
| 1.11. - 30.11. || Flood control area || = 2.75M m³ || Capacity level || = 22.31M m³&lt;br /&gt;
|- &lt;br /&gt;
| 1.12. - 15.1. || Flood control area || = 4.50M m³ || Capacity level || = 20.56M m³&lt;br /&gt;
|- &lt;br /&gt;
| 16.1. - 31.3. || Flood control area || = 2.50M m³ || Capacity level || = 22.56M m³&lt;br /&gt;
|- &lt;br /&gt;
| 1.4. - 30.4. || Flood control area || = 1.75M m³ || Capacity level || = 23.31M m³&lt;br /&gt;
|- &lt;br /&gt;
| 1.5. - 30.9. || Flood control area || = 1.00M m³ || Capacity level || = 24.06M m³&lt;br /&gt;
|}  &lt;br /&gt;
&lt;br /&gt;
Clearance of flood control areas is done at the maximal permitted discharge.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;Maximal permitted discharge:&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
As long as the normal water level has not yet been reached, no more than 5 m³/s may be discharged to the downstream watercourse.&lt;br /&gt;
&lt;br /&gt;
If the normal water level of the dam is exceeded and the inflow exceeds the maximum discharge of 5 m³/s, no more than 5 m³/s may be discharged from the bottom outlet. Additional inflow is to be discharged via the spillway.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;Capacity curve of the spillway:&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The characteristic curve is given as a X-Y curve with interpolation points.&lt;br /&gt;
&lt;br /&gt;
The realization of the operating plan considering the terminology described above, first requires the identification of all expectations and uses for the dam and a definition of the &#039;&#039;discharge functions&#039;&#039;. The following information is provided only to illustrate the operating plan concept and does not claim to be complete or an accurate representation of actual conditions.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&#039;&#039;Use:&#039;&#039;&#039; Water supply&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:{| cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | &amp;lt;u&amp;gt;Temporal dependency:&amp;lt;/u&amp;gt;  || Constant annualized discharge function, variable demand&lt;br /&gt;
|- &lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | &amp;lt;u&amp;gt;External dependencies:&amp;lt;/u&amp;gt;  || Yes&lt;br /&gt;
|- &lt;br /&gt;
| &amp;amp;nbsp; || 1. Current water demand [m³/s]:  || Factor1 (calculation rule: multiplication) &lt;br /&gt;
|- &lt;br /&gt;
| &amp;amp;nbsp; || 2. Monthly balance of withdrawals: || Factor2 (calculation rule: multiplication) &lt;br /&gt;
|- &lt;br /&gt;
| &amp;amp;nbsp; || 3. Annual balance of withdrawals:  || Factor3 (calculation rule: multiplication) &lt;br /&gt;
|- &lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; valign=&amp;quot;top&amp;quot; | &amp;lt;u&amp;gt;Discharge per time step:&amp;lt;/u&amp;gt;  || Calculation of the use &#039;water supply&#039; with:&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;Discharge = Factor1 &amp;amp;times; Factor2 &amp;amp;times; Factor3 &amp;amp;times; f(Storage volume)&amp;lt;/code&amp;gt;&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
:{| class=&amp;quot;wikitable&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- style=&amp;quot;background-color:#CCCCCC;&amp;quot; &lt;br /&gt;
! width=&amp;quot;300&amp;quot; | Conditions &lt;br /&gt;
! width=&amp;quot;200&amp;quot; | Discharge functions&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;u&amp;gt;Fulfillment of demand [%]:&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Period of validity: Jan. 1 - Dec. 31.&lt;br /&gt;
&lt;br /&gt;
Explanation:  Starting from a storage capacity of &amp;lt; 10 million m³, the fulfillment of demand is reduced to 80%. If the storage volume falls below 2 million m³, no more water is withdrawn.&lt;br /&gt;
&lt;br /&gt;
| align=&amp;quot;center&amp;quot; | [[Bild:Theorie_Bsp01.png|thumb|none]]&lt;br /&gt;
|- style=&amp;quot;background-color:#CCCCCC;&amp;quot; &lt;br /&gt;
! Conditions !! System State Functions&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;u&amp;gt;Actual water demand [m³/s]:&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(Factor 1)&lt;br /&gt;
&lt;br /&gt;
Time reference: current value&lt;br /&gt;
&lt;br /&gt;
Calculation rule: multiplication&lt;br /&gt;
| align=&amp;quot;center&amp;quot; | No function necessary&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;u&amp;gt;Monthly balance of discharge [-]:&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(Factor 2)&lt;br /&gt;
&lt;br /&gt;
Time reference: monthly balance&lt;br /&gt;
&lt;br /&gt;
Period of validity: Jan. 1 - Dec. 31.&lt;br /&gt;
&lt;br /&gt;
Limit value: 2.5M m³&lt;br /&gt;
&lt;br /&gt;
Calculation rule: multiplication&lt;br /&gt;
| align=&amp;quot;center&amp;quot; | [[Bild:Theorie_Bsp02.png|thumb|none]]&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;u&amp;gt;Annual balance of discharge [-]:&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(Factor 3)&lt;br /&gt;
&lt;br /&gt;
Time reference: annual balance&lt;br /&gt;
&lt;br /&gt;
Period of validity: Jan. 1 - Dec. 31.&lt;br /&gt;
&lt;br /&gt;
Limit value: 11.0M m³&lt;br /&gt;
&lt;br /&gt;
Calculation rule: multiplication&lt;br /&gt;
| [[Bild:Theorie_Bsp03.png|thumb|none]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&#039;&#039;Use:&#039;&#039;&#039; Flood Protection&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:{| cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot;&lt;br /&gt;
| &amp;lt;u&amp;gt;Time dependency:&amp;lt;/u&amp;gt; || Yes &lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;u&amp;gt;External dependencies:&amp;lt;/u&amp;gt; || No &lt;br /&gt;
|-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; | &amp;lt;u&amp;gt;Discharge per time step:&amp;lt;/u&amp;gt; || The use &#039;flood protection&#039; is given directly as a function of the date.&lt;br /&gt;
&amp;lt;code&amp;gt;Discharge = f(storage volume)&amp;lt;/code&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
:{| class=&amp;quot;wikitable&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- style=&amp;quot;background-color:#CCCCCC;&amp;quot; &lt;br /&gt;
! width=&amp;quot;300&amp;quot; | Conditions &lt;br /&gt;
! width=&amp;quot;200&amp;quot; | Discharge Functions&lt;br /&gt;
|-&lt;br /&gt;
| Period of validity: Dec. 1 - Jan. 15.&lt;br /&gt;
&lt;br /&gt;
Maximal permitted discharge: 5 m³/s&lt;br /&gt;
&lt;br /&gt;
Capacity level: 20.56M m³&lt;br /&gt;
| [[Bild:Theorie_Bsp04.png|thumb|none]]&lt;br /&gt;
|-&lt;br /&gt;
|Period of validity: 16 Jan - 31 March&lt;br /&gt;
&lt;br /&gt;
Maximal permitted discharge: 5 m³/s&lt;br /&gt;
&lt;br /&gt;
Capacity level: 22.56M m³&lt;br /&gt;
| [[Bild:Theorie_Bsp05.png|thumb|none]]&lt;br /&gt;
|-&lt;br /&gt;
| Period of validity: April 1 - April 30&lt;br /&gt;
&lt;br /&gt;
Maximal permitted discharge: 5 m³/s&lt;br /&gt;
&lt;br /&gt;
Capacity level: 23.31M m³/s&lt;br /&gt;
| [[Bild:Theorie_Bsp06.png|thumb|none]]&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | For the remaining periods, the discharge functions are analogous.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&#039;&#039;Use:&#039;&#039;&#039; Standard discharge&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:{| cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | &amp;lt;u&amp;gt;Time dependency:&amp;lt;/u&amp;gt; || Yes &lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | &amp;lt;u&amp;gt;External dependencies:&amp;lt;/u&amp;gt; || Yes&lt;br /&gt;
|-&lt;br /&gt;
| &amp;amp;nbsp; || 1. Current inflow {m³/s]: || Factor 1 (calculation rule: multiplication)&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; valign=&amp;quot;top&amp;quot; | &amp;lt;u&amp;gt;Discharge per time step:&amp;lt;/u&amp;gt; || Calculation of the use &#039;standard discharge&#039; with:&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;Discharge = Factor &amp;amp;times; f(storage volume)&amp;lt;/code&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
:{| class=&amp;quot;wikitable&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- style=&amp;quot;background-color:#CCCCCC;&amp;quot; &lt;br /&gt;
! width=&amp;quot;300&amp;quot; | Conditions &lt;br /&gt;
! width=&amp;quot;200&amp;quot; | Discharge Functions&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;u&amp;gt;Factor standard discharge [-]:&amp;lt;/u&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Period of validity: Jan. 1 - Dec. 31. &lt;br /&gt;
&lt;br /&gt;
Explanation: If the storage volume declines below 2 million m³, a standard discharge is no longer maintained. &lt;br /&gt;
&lt;br /&gt;
| [[Bild:Theorie_Bsp07.png|thumb|none]]&lt;br /&gt;
|- style=&amp;quot;background-color:#CCCCCC;&amp;quot; &lt;br /&gt;
! Conditions &lt;br /&gt;
! System State Functions&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;u&amp;gt;Current inflow [m³/s]:&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(Factor 1)&lt;br /&gt;
&lt;br /&gt;
Period of validity: Jan. 1 - Dec. 31. &lt;br /&gt;
&lt;br /&gt;
Maximal permitted discharge: 5 m³/s &lt;br /&gt;
&lt;br /&gt;
Explanation: If the inflow exceeds 0.2 m³/s, a discharge of 0.2 m³/s continues. &lt;br /&gt;
&lt;br /&gt;
| [[Bild:Theorie_Bsp08.png|thumb|none]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Bild:Theorie_Abb26.png|thumb|Abbildung 26: Skalierte Abgabenfunktionen]]&lt;br /&gt;
&lt;br /&gt;
For a selected time and an assumed initial storage volume of S&amp;lt;sub&amp;gt;0&amp;lt;/sub&amp;gt; = 23K m³, all relations are plotted in [[:Bild:Theorie_Abb26.png|Abbildung 26]]. For illustration purposes, a different y-axis scale is chosen for the flood control function.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- style=&amp;quot;background-color:#CCCCCC;&amp;quot; &lt;br /&gt;
! Parameters !! Defaults !! Affected Parameters:&lt;br /&gt;
|-&lt;br /&gt;
| Time || January 30 || flood protection, water supply. (Factor1, Factor2)&lt;br /&gt;
|-&lt;br /&gt;
| Initial storage volume || 23M m³ || all discharge functions&lt;br /&gt;
|-&lt;br /&gt;
| Average daily inflow || 0.180 m³/s || standard discharge&lt;br /&gt;
|-&lt;br /&gt;
| Average water demand || 0.300 m³/s || discharge for water supply&lt;br /&gt;
|-&lt;br /&gt;
| Discharge for water supply since 1.Jan. || 0.750M m³ || discharge for water supply&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Anwendungsbeispiel:_Umsetzung_eines_Betriebsplans/8/en&amp;diff=12975</id>
		<title>Translations:Anwendungsbeispiel: Umsetzung eines Betriebsplans/8/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Anwendungsbeispiel:_Umsetzung_eines_Betriebsplans/8/en&amp;diff=12975"/>
		<updated>2021-08-30T10:41:27Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The storage provides two water supply companies with drinking water. The companies request water via daily demand values. Concerning the water supply, it is set that up to 11 million m³ must be provided annually as drinking water, of which no more than 2.5 million m³ may be discharged each month.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Anwendungsbeispiel:_Umsetzung_eines_Betriebsplans/en&amp;diff=12974</id>
		<title>Anwendungsbeispiel: Umsetzung eines Betriebsplans/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Anwendungsbeispiel:_Umsetzung_eines_Betriebsplans/en&amp;diff=12974"/>
		<updated>2021-08-30T10:41:13Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=Berechungsschema/ Implementierung der Betriebsregeln|hoch=Betriebsregelkonzept|nachher=Begriffsdefinitionen}}&lt;br /&gt;
&lt;br /&gt;
Taking the [https://de.wikipedia.org/wiki/Wehebachtalsperre  Wehebach-Dam] as an example of use, the implementation of an operating plan in accordance with applying laws is illustrated.&lt;br /&gt;
&lt;br /&gt;
The Wehebach-Dam is a multi-purpose storage used for water supply and flood protection. In addition, a standard discharge of 100 l/s to the downstream watercourse is to be maintained. The operator of the dam is the [http://www.wver.de Water association Eifel-Rur]. The operation responsibilities include the drinking water supply of the greater Aachen area, the northern Eifel region and the supply of service water for several industrial companies. The catchment area of the dam is 43.61 km², the average annual inflow is 21 million m³, and the storage capacity is 119.3%. Built as a rockfill dam, the construction of the storage was completed in 1983.&lt;br /&gt;
&lt;br /&gt;
The following operating plan was drawn up for the Wehebach-Dam:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;Characteristics of the dam:&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:Max. content at crest level: 27.1M m³&lt;br /&gt;
:Capacity to the spillway: 25.06M m³&lt;br /&gt;
:Capacity level (normal water level): see flood control areas&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;Release volume for water supply:&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The reservoir provides two water supply companies with drinking water. The companies request water via daily demand values. Concerning the water supply, it is set that up to 11 million m³ must be provided annually as drinking water, of which no more than 2.5 million m³ may be discharged each month.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;Standard discharge:&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The standard discharge is intended to provide a minimum flow downstream of the dam and is set depending on the inflow, as follows: &lt;br /&gt;
&lt;br /&gt;
:{| cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot;&lt;br /&gt;
| &amp;amp;nbsp; || Inflow || &amp;amp;ge; 200 l/s || &amp;amp;rarr; || Standard discharge || = || 200 l/s &lt;br /&gt;
|- &lt;br /&gt;
| 100 l/s &amp;amp;le; || Inflow || &amp;amp;lt; 200 l/s || &amp;amp;rarr; || Standard discharge || = || Inflow &lt;br /&gt;
|- &lt;br /&gt;
| &amp;amp;nbsp; || Inflow || &amp;amp;lt; 100 l/s || &amp;amp;rarr; || Standard discharge || = || 100 l/s &lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
Every water resources management year, not later than the end of March, 4 m³/s must be discharged to the downstream watercourse as a flushing wave over a period of 6 hours.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;Flood control areas:&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
To ensure sufficing flood protection, a time-variable pool-based flood level is defined. The lower limit of the flood control areas is defined as the capacity level.&lt;br /&gt;
&lt;br /&gt;
:{| cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot;&lt;br /&gt;
| 1.10. - 31.10. || Flood control area || = 1.00M m³ || Capacity level || = 24.06M m³&lt;br /&gt;
|- &lt;br /&gt;
| 1.11. - 30.11. || Flood control area || = 2.75M m³ || Capacity level || = 22.31M m³&lt;br /&gt;
|- &lt;br /&gt;
| 1.12. - 15.1. || Flood control area || = 4.50M m³ || Capacity level || = 20.56M m³&lt;br /&gt;
|- &lt;br /&gt;
| 16.1. - 31.3. || Flood control area || = 2.50M m³ || Capacity level || = 22.56M m³&lt;br /&gt;
|- &lt;br /&gt;
| 1.4. - 30.4. || Flood control area || = 1.75M m³ || Capacity level || = 23.31M m³&lt;br /&gt;
|- &lt;br /&gt;
| 1.5. - 30.9. || Flood control area || = 1.00M m³ || Capacity level || = 24.06M m³&lt;br /&gt;
|}  &lt;br /&gt;
&lt;br /&gt;
Clearance of flood control areas is done at the maximal permitted discharge.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;Maximal permitted discharge:&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
As long as the normal water level has not yet been reached, no more than 5 m³/s may be discharged to the downstream watercourse.&lt;br /&gt;
&lt;br /&gt;
If the normal water level of the dam is exceeded and the inflow exceeds the maximum discharge of 5 m³/s, no more than 5 m³/s may be discharged from the bottom outlet. Additional inflow is to be discharged via the spillway.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;Capacity curve of the spillway:&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The characteristic curve is given as a X-Y curve with interpolation points.&lt;br /&gt;
&lt;br /&gt;
The realization of the operating plan considering the terminology described above, first requires the identification of all expectations and uses for the dam and a definition of the &#039;&#039;discharge functions&#039;&#039;. The following information is provided only to illustrate the operating plan concept and does not claim to be complete or an accurate representation of actual conditions.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&#039;&#039;Use:&#039;&#039;&#039; Water supply&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:{| cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | &amp;lt;u&amp;gt;Temporal dependency:&amp;lt;/u&amp;gt;  || Constant annualized discharge function, variable demand&lt;br /&gt;
|- &lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | &amp;lt;u&amp;gt;External dependencies:&amp;lt;/u&amp;gt;  || Yes&lt;br /&gt;
|- &lt;br /&gt;
| &amp;amp;nbsp; || 1. Current water demand [m³/s]:  || Factor1 (calculation rule: multiplication) &lt;br /&gt;
|- &lt;br /&gt;
| &amp;amp;nbsp; || 2. Monthly balance of withdrawals: || Factor2 (calculation rule: multiplication) &lt;br /&gt;
|- &lt;br /&gt;
| &amp;amp;nbsp; || 3. Annual balance of withdrawals:  || Factor3 (calculation rule: multiplication) &lt;br /&gt;
|- &lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; valign=&amp;quot;top&amp;quot; | &amp;lt;u&amp;gt;Discharge per time step:&amp;lt;/u&amp;gt;  || Calculation of the use &#039;water supply&#039; with:&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;Discharge = Factor1 &amp;amp;times; Factor2 &amp;amp;times; Factor3 &amp;amp;times; f(Storage volume)&amp;lt;/code&amp;gt;&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
:{| class=&amp;quot;wikitable&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- style=&amp;quot;background-color:#CCCCCC;&amp;quot; &lt;br /&gt;
! width=&amp;quot;300&amp;quot; | Conditions &lt;br /&gt;
! width=&amp;quot;200&amp;quot; | Discharge functions&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;u&amp;gt;Fulfillment of demand [%]:&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Period of validity: Jan. 1 - Dec. 31.&lt;br /&gt;
&lt;br /&gt;
Explanation:  Starting from a storage capacity of &amp;lt; 10 million m³, the fulfillment of demand is reduced to 80%. If the storage volume falls below 2 million m³, no more water is withdrawn.&lt;br /&gt;
&lt;br /&gt;
| align=&amp;quot;center&amp;quot; | [[Bild:Theorie_Bsp01.png|thumb|none]]&lt;br /&gt;
|- style=&amp;quot;background-color:#CCCCCC;&amp;quot; &lt;br /&gt;
! Conditions !! System State Functions&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;u&amp;gt;Actual water demand [m³/s]:&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(Factor 1)&lt;br /&gt;
&lt;br /&gt;
Time reference: current value&lt;br /&gt;
&lt;br /&gt;
Calculation rule: multiplication&lt;br /&gt;
| align=&amp;quot;center&amp;quot; | No function necessary&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;u&amp;gt;Monthly balance of discharge [-]:&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(Factor 2)&lt;br /&gt;
&lt;br /&gt;
Time reference: monthly balance&lt;br /&gt;
&lt;br /&gt;
Period of validity: Jan. 1 - Dec. 31.&lt;br /&gt;
&lt;br /&gt;
Limit value: 2.5M m³&lt;br /&gt;
&lt;br /&gt;
Calculation rule: multiplication&lt;br /&gt;
| align=&amp;quot;center&amp;quot; | [[Bild:Theorie_Bsp02.png|thumb|none]]&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;u&amp;gt;Annual balance of discharge [-]:&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(Factor 3)&lt;br /&gt;
&lt;br /&gt;
Time reference: annual balance&lt;br /&gt;
&lt;br /&gt;
Period of validity: Jan. 1 - Dec. 31.&lt;br /&gt;
&lt;br /&gt;
Limit value: 11.0M m³&lt;br /&gt;
&lt;br /&gt;
Calculation rule: multiplication&lt;br /&gt;
| [[Bild:Theorie_Bsp03.png|thumb|none]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&#039;&#039;Use:&#039;&#039;&#039; Flood Protection&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:{| cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot;&lt;br /&gt;
| &amp;lt;u&amp;gt;Time dependency:&amp;lt;/u&amp;gt; || Yes &lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;u&amp;gt;External dependencies:&amp;lt;/u&amp;gt; || No &lt;br /&gt;
|-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; | &amp;lt;u&amp;gt;Discharge per time step:&amp;lt;/u&amp;gt; || The use &#039;flood protection&#039; is given directly as a function of the date.&lt;br /&gt;
&amp;lt;code&amp;gt;Discharge = f(storage volume)&amp;lt;/code&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
:{| class=&amp;quot;wikitable&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- style=&amp;quot;background-color:#CCCCCC;&amp;quot; &lt;br /&gt;
! width=&amp;quot;300&amp;quot; | Conditions &lt;br /&gt;
! width=&amp;quot;200&amp;quot; | Discharge Functions&lt;br /&gt;
|-&lt;br /&gt;
| Period of validity: Dec. 1 - Jan. 15.&lt;br /&gt;
&lt;br /&gt;
Maximal permitted discharge: 5 m³/s&lt;br /&gt;
&lt;br /&gt;
Capacity level: 20.56M m³&lt;br /&gt;
| [[Bild:Theorie_Bsp04.png|thumb|none]]&lt;br /&gt;
|-&lt;br /&gt;
|Period of validity: 16 Jan - 31 March&lt;br /&gt;
&lt;br /&gt;
Maximal permitted discharge: 5 m³/s&lt;br /&gt;
&lt;br /&gt;
Capacity level: 22.56M m³&lt;br /&gt;
| [[Bild:Theorie_Bsp05.png|thumb|none]]&lt;br /&gt;
|-&lt;br /&gt;
| Period of validity: April 1 - April 30&lt;br /&gt;
&lt;br /&gt;
Maximal permitted discharge: 5 m³/s&lt;br /&gt;
&lt;br /&gt;
Capacity level: 23.31M m³/s&lt;br /&gt;
| [[Bild:Theorie_Bsp06.png|thumb|none]]&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | For the remaining periods, the discharge functions are analogous.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&#039;&#039;Use:&#039;&#039;&#039; Standard discharge&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:{| cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | &amp;lt;u&amp;gt;Time dependency:&amp;lt;/u&amp;gt; || Yes &lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | &amp;lt;u&amp;gt;External dependencies:&amp;lt;/u&amp;gt; || Yes&lt;br /&gt;
|-&lt;br /&gt;
| &amp;amp;nbsp; || 1. Current inflow {m³/s]: || Factor 1 (calculation rule: multiplication)&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; valign=&amp;quot;top&amp;quot; | &amp;lt;u&amp;gt;Discharge per time step:&amp;lt;/u&amp;gt; || Calculation of the use &#039;standard discharge&#039; with:&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;Discharge = Factor &amp;amp;times; f(storage volume)&amp;lt;/code&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
:{| class=&amp;quot;wikitable&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- style=&amp;quot;background-color:#CCCCCC;&amp;quot; &lt;br /&gt;
! width=&amp;quot;300&amp;quot; | Conditions &lt;br /&gt;
! width=&amp;quot;200&amp;quot; | Discharge Functions&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;u&amp;gt;Factor standard discharge [-]:&amp;lt;/u&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Period of validity: Jan. 1 - Dec. 31. &lt;br /&gt;
&lt;br /&gt;
Explanation: If the storage volume declines below 2 million m³, a standard discharge is no longer maintained. &lt;br /&gt;
&lt;br /&gt;
| [[Bild:Theorie_Bsp07.png|thumb|none]]&lt;br /&gt;
|- style=&amp;quot;background-color:#CCCCCC;&amp;quot; &lt;br /&gt;
! Conditions &lt;br /&gt;
! System State Functions&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;u&amp;gt;Current inflow [m³/s]:&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(Factor 1)&lt;br /&gt;
&lt;br /&gt;
Period of validity: Jan. 1 - Dec. 31. &lt;br /&gt;
&lt;br /&gt;
Maximal permitted discharge: 5 m³/s &lt;br /&gt;
&lt;br /&gt;
Explanation: If the inflow exceeds 0.2 m³/s, a discharge of 0.2 m³/s continues. &lt;br /&gt;
&lt;br /&gt;
| [[Bild:Theorie_Bsp08.png|thumb|none]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Bild:Theorie_Abb26.png|thumb|Abbildung 26: Skalierte Abgabenfunktionen]]&lt;br /&gt;
&lt;br /&gt;
For a selected time and an assumed initial storage volume of S&amp;lt;sub&amp;gt;0&amp;lt;/sub&amp;gt; = 23K m³, all relations are plotted in [[:Bild:Theorie_Abb26.png|Abbildung 26]]. For illustration purposes, a different y-axis scale is chosen for the flood control function.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- style=&amp;quot;background-color:#CCCCCC;&amp;quot; &lt;br /&gt;
! Parameters !! Defaults !! Affected Parameters:&lt;br /&gt;
|-&lt;br /&gt;
| Time || January 30 || flood protection, water supply. (Factor1, Factor2)&lt;br /&gt;
|-&lt;br /&gt;
| Initial storage volume || 23M m³ || all discharge functions&lt;br /&gt;
|-&lt;br /&gt;
| Average daily inflow || 0.180 m³/s || standard discharge&lt;br /&gt;
|-&lt;br /&gt;
| Average water demand || 0.300 m³/s || discharge for water supply&lt;br /&gt;
|-&lt;br /&gt;
| Discharge for water supply since 1.Jan. || 0.750M m³ || discharge for water supply&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Anwendungsbeispiel:_Umsetzung_eines_Betriebsplans/3/en&amp;diff=12973</id>
		<title>Translations:Anwendungsbeispiel: Umsetzung eines Betriebsplans/3/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Anwendungsbeispiel:_Umsetzung_eines_Betriebsplans/3/en&amp;diff=12973"/>
		<updated>2021-08-30T10:41:13Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Wehebach-Dam is a multi-purpose storage used for water supply and flood protection. In addition, a standard discharge of 100 l/s to the downstream watercourse is to be maintained. The operator of the dam is the [http://www.wver.de Water association Eifel-Rur]. The operation responsibilities include the drinking water supply of the greater Aachen area, the northern Eifel region and the supply of service water for several industrial companies. The catchment area of the dam is 43.61 km², the average annual inflow is 21 million m³, and the storage capacity is 119.3%. Built as a rockfill dam, the construction of the storage was completed in 1983.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Beschreibung_der_Systemelemente/en&amp;diff=12972</id>
		<title>Beschreibung der Systemelemente/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Beschreibung_der_Systemelemente/en&amp;diff=12972"/>
		<updated>2021-08-30T10:40:34Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=Modellkonzept|hoch=Hauptseite#Theoretische Grundlagen|nachher=Einzugsgebiet}}&lt;br /&gt;
In Talsim-NG, a river basin model is setup according to a modular principle. All relevant objects and processes of the [[Special:MyLanguage/Begriffsdefinitionen|water resources system]] are represented by system elements. These can be linked together as building blocks to represent the entire system including its interactions.&lt;br /&gt;
&lt;br /&gt;
Each system element has specific [[Special:MyLanguage/Begriffsdefinitionen|properties]] and methods, is able to process certain input variables and provides specific output variables (see [[Special:MyLanguage/Modellkonzept|model concept]]). The following table gives an overview of all system elements in Talsim-NG with their most important properties/methods as well as input and output variables:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Element || Important loads || Properties / methods || Element output&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/Einzugsgebiet|Sub-basin]] &amp;lt;br /&amp;gt;[[Datei:Systemelement001.png|40px]] ||&lt;br /&gt;
*Precipitation&lt;br /&gt;
*Temperature&lt;br /&gt;
*Evaporation&lt;br /&gt;
||&lt;br /&gt;
*Soil properties/imperviousness&lt;br /&gt;
*Runoff generation&lt;br /&gt;
*Runoff distribution&lt;br /&gt;
*Runoff concentration&lt;br /&gt;
*...&lt;br /&gt;
|| &lt;br /&gt;
*Surface runoff&lt;br /&gt;
*Baseflow&lt;br /&gt;
*Total discharge&lt;br /&gt;
*...&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/Einleitung|Point source]] &amp;lt;br /&amp;gt;[[Datei:Systemelement002.png|40px]]||  || &lt;br /&gt;
*Water input into the system&lt;br /&gt;
|| &lt;br /&gt;
*Runoff&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/Transportstrecke|Transport reach]] &amp;lt;br /&amp;gt;[[Datei:Systemelement003.png|40px]]|| &lt;br /&gt;
*Inflow&lt;br /&gt;
|| &lt;br /&gt;
*Translation&lt;br /&gt;
*Retention &lt;br /&gt;
|| &lt;br /&gt;
*Runoff&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/Verbraucher|Consumer]] &amp;lt;br /&amp;gt;[[Datei:Systemelement004.png|40px]]|| &lt;br /&gt;
*Inflow&lt;br /&gt;
|| &lt;br /&gt;
*Consumption behavior&lt;br /&gt;
*External contribution&lt;br /&gt;
*Return flow into the system&lt;br /&gt;
|| &lt;br /&gt;
*Return flow&lt;br /&gt;
*External contribution&lt;br /&gt;
*Total discharge&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/Verzweigung|Diversion]] &amp;lt;br /&amp;gt;[[Datei:Systemelement005.png|50px]]||&lt;br /&gt;
*Inflow &lt;br /&gt;
|| &lt;br /&gt;
*Diversion rule &lt;br /&gt;
|| &lt;br /&gt;
*Two outflows&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/Speicher|Storage]] &amp;lt;br /&amp;gt;[[Datei:Systemelement006.png|50px]]|| &lt;br /&gt;
*Inflow&lt;br /&gt;
optional:&lt;br /&gt;
*Precipitation&lt;br /&gt;
*Evaporation &lt;br /&gt;
|| &lt;br /&gt;
*Storage rating curve&lt;br /&gt;
*Storage-surface rating curve&lt;br /&gt;
*Capacity of operational equipment&lt;br /&gt;
*Operating rules&lt;br /&gt;
*(Infiltration properties)&lt;br /&gt;
*... &lt;br /&gt;
|| &lt;br /&gt;
*Releases&lt;br /&gt;
*Storage&lt;br /&gt;
*Water level&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/Zielpegel|System outlet]] &amp;lt;br /&amp;gt;[[Datei:Symbol_Zielpegel.PNG]]|| &lt;br /&gt;
*Inflow&lt;br /&gt;
|| &lt;br /&gt;
|| &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Beschreibung_der_Systemelemente/3/en&amp;diff=12971</id>
		<title>Translations:Beschreibung der Systemelemente/3/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Beschreibung_der_Systemelemente/3/en&amp;diff=12971"/>
		<updated>2021-08-30T10:40:34Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Element || Important loads || Properties / methods || Element output&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/Einzugsgebiet|Sub-basin]] &amp;lt;br /&amp;gt;[[Datei:Systemelement001.png|40px]] ||&lt;br /&gt;
*Precipitation&lt;br /&gt;
*Temperature&lt;br /&gt;
*Evaporation&lt;br /&gt;
||&lt;br /&gt;
*Soil properties/imperviousness&lt;br /&gt;
*Runoff generation&lt;br /&gt;
*Runoff distribution&lt;br /&gt;
*Runoff concentration&lt;br /&gt;
*...&lt;br /&gt;
|| &lt;br /&gt;
*Surface runoff&lt;br /&gt;
*Baseflow&lt;br /&gt;
*Total discharge&lt;br /&gt;
*...&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/Einleitung|Point source]] &amp;lt;br /&amp;gt;[[Datei:Systemelement002.png|40px]]||  || &lt;br /&gt;
*Water input into the system&lt;br /&gt;
|| &lt;br /&gt;
*Runoff&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/Transportstrecke|Transport reach]] &amp;lt;br /&amp;gt;[[Datei:Systemelement003.png|40px]]|| &lt;br /&gt;
*Inflow&lt;br /&gt;
|| &lt;br /&gt;
*Translation&lt;br /&gt;
*Retention &lt;br /&gt;
|| &lt;br /&gt;
*Runoff&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/Verbraucher|Consumer]] &amp;lt;br /&amp;gt;[[Datei:Systemelement004.png|40px]]|| &lt;br /&gt;
*Inflow&lt;br /&gt;
|| &lt;br /&gt;
*Consumption behavior&lt;br /&gt;
*External contribution&lt;br /&gt;
*Return flow into the system&lt;br /&gt;
|| &lt;br /&gt;
*Return flow&lt;br /&gt;
*External contribution&lt;br /&gt;
*Total discharge&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/Verzweigung|Diversion]] &amp;lt;br /&amp;gt;[[Datei:Systemelement005.png|50px]]||&lt;br /&gt;
*Inflow &lt;br /&gt;
|| &lt;br /&gt;
*Diversion rule &lt;br /&gt;
|| &lt;br /&gt;
*Two outflows&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/Speicher|Storage]] &amp;lt;br /&amp;gt;[[Datei:Systemelement006.png|50px]]|| &lt;br /&gt;
*Inflow&lt;br /&gt;
optional:&lt;br /&gt;
*Precipitation&lt;br /&gt;
*Evaporation &lt;br /&gt;
|| &lt;br /&gt;
*Storage rating curve&lt;br /&gt;
*Storage-surface rating curve&lt;br /&gt;
*Capacity of operational equipment&lt;br /&gt;
*Operating rules&lt;br /&gt;
*(Infiltration properties)&lt;br /&gt;
*... &lt;br /&gt;
|| &lt;br /&gt;
*Releases&lt;br /&gt;
*Storage&lt;br /&gt;
*Water level&lt;br /&gt;
|-&lt;br /&gt;
| [[Special:MyLanguage/Zielpegel|System outlet]] &amp;lt;br /&amp;gt;[[Datei:Symbol_Zielpegel.PNG]]|| &lt;br /&gt;
*Inflow&lt;br /&gt;
|| &lt;br /&gt;
|| &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Betriebsregelkonzept/en&amp;diff=12970</id>
		<title>Betriebsregelkonzept/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Betriebsregelkonzept/en&amp;diff=12970"/>
		<updated>2021-08-30T10:39:02Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=Berechnungsschema von Speichern|hoch=Hauptseite|nachher=Betriebsregeltypen}}&lt;br /&gt;
&lt;br /&gt;
In order to achieve the best possible water resource management of storage systems, you need instructions that clearly define how water should be stored, released or distributed under given system loads and conditions. These instructions are summarized in an operating plan. An operating plan can consist of many individual instructions, e.g. the compliance with a certain release amount depending on the storage volume. An individual instruction can be called an operating rule.&lt;br /&gt;
&lt;br /&gt;
Since the formulation of an operating rule is always associated with a corrective intervention in the natural flow behaviour, in order to be able to execute the operating rule you must also be able to change the flow in some way. Only few water resource management elements are suitable for this purpose. Normally these will be storages with adjustable releases. Apart from that, there are also controllable diversion structures or weirs. In Talsim-NG the system elements [[Special:MyLanguage/Speicher|storage]] and [[Special:MyLanguage/Verzweigung|diversion]] offer the possibility to be controlled by operating rules.&lt;br /&gt;
&lt;br /&gt;
The purpose of all operating rules is to adapt system states of a water resources system in order to meet specified objectives. It is irrelevant where the system states and target variables occur, as long as the target variables can be influenced by a change in the system states. &lt;br /&gt;
&lt;br /&gt;
In the following&lt;br /&gt;
*[[Special:MyLanguage/Betriebsregeltypen|typical operating rules]] for the operation of storages are presented,&lt;br /&gt;
*their principles are [[Special:MyLanguage/Abstraktion der Betriebsregeln|abstracted]],&lt;br /&gt;
*the [[Special:MyLanguage/Berechungsschema/ Implementierung der Betriebsregeln|implementation of a calculation scheme]] for the simulation is derived,&lt;br /&gt;
*and an [[Special:MyLanguage/Anwendungsbeispiel:_Umsetzung_eines_Betriebsplans|example]] demonstrates the implementation of an operating plan in Talsim-NG.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Betriebsregelkonzept/3/en&amp;diff=12969</id>
		<title>Translations:Betriebsregelkonzept/3/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Betriebsregelkonzept/3/en&amp;diff=12969"/>
		<updated>2021-08-30T10:39:01Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Since the formulation of an operating rule is always associated with a corrective intervention in the natural flow behaviour, in order to be able to execute the operating rule you must also be able to change the flow in some way. Only few water resource management elements are suitable for this purpose. Normally these will be storages with adjustable releases. Apart from that, there are also controllable diversion structures or weirs. In Talsim-NG the system elements [[Special:MyLanguage/Speicher|storage]] and [[Special:MyLanguage/Verzweigung|diversion]] offer the possibility to be controlled by operating rules.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12968</id>
		<title>Betriebsregeltypen/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12968"/>
		<updated>2021-08-30T10:36:09Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=|hoch=Betriebsregelkonzept|nachher=Abstraktion der Betriebsregeln}}&lt;br /&gt;
&lt;br /&gt;
The operating plan of a dam or a storage network is part of the official approval of plans and usually is available as a report or presentation. Its complexity can vary: it ranges from simply defining flood protection areas and setting a report and alarm plan to notify the supervisory authorities in exceptional situations to complex sets of rules concerning functional dependencies that derive discharges from varying system states.&lt;br /&gt;
&lt;br /&gt;
As follows, principles to clarify the variety of possible regulations and reduce them to essential dependencies are presented. A concept is derived to represent most operating rules by a few basic calculation rules. The given selection does not claim to be complete, but it is likely to contain the rules applied in practice.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Basic Principle: Verification of Physical Limits==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb1.png|thumb|Figure 1: Dependency on storage capacity]]&lt;br /&gt;
&lt;br /&gt;
When specifying discharges according to an operating rule, it is assumed that the outlet capacity is sufficient to meet these discharges. Thus, dimensioning the outlet element must consider the operating requirements. In principle, the physically possible discharge, given by the outlet&#039;s characteristic curve at full opening, sets the upper limit value.&lt;br /&gt;
&lt;br /&gt;
If the pressure level or the outlet capacity is sufficient to discharge the desired quantity when fully opened, the discharge can be throttled to the intended level by closing a slide. If the pressure level is insufficient, only the hydraulically possible discharge can be discharged.&lt;br /&gt;
&lt;br /&gt;
*Mathematical abstraction:&lt;br /&gt;
:All outlets obeying an operating rule are functions of the storage&#039;s volume and cannot exceed the outlets&#039; maximum capacity when fully opened. As soon as the capacity of the outlets exceeds the required discharge, it can be adjusted by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
All discharge types from storages mentioned below are subject to this restriction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 1: Definition of a Minimum Output or a Safely Dischargeable Maximum Output==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb2.png|thumb|Figure 2: Example for minimum and maximum discharge as a function of storage capacity]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The specification of a minimum or maximum discharge is based on requirements downstream of a reservoir. The maximal discharge is based on the discharge respective to a critical, downstream cross-section. Consequently, a hydraulic method exists for its determination. In contrast, there is no clear guideline for the minimum discharge. Often, ratios of MNQ or MQ are used. Independent of determining the minimum or maximum discharge, the basic principle to verify outlet elements&#039; physical limits is applied. So, minimum and maximum discharge can only be discharged if the outlet capacity is sufficient at the given pressure level. Since, in reality, it is unlikely that the dimensioning of the outlet elements and the required discharge are conflicting, the reference to the dependence on the storage capacity content is rather theoretical but necessary to derive general laws.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Minimum and maximum discharge are functions of the storage volume and follow the characteristic curve of fully opened outlets at a low filling level. As soon as the outlet elements&#039; capacity is sufficient for the required discharge volume, the discharge can be kept constant by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 2: Maintaining a Flood Protection Area, Possibly Timely Variable Over the Year==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb3.png|thumb|Figure 3: Example of a function to maintain a flood protection area]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The definition of a flood protection area as a minimum requirement only includes the designation of a volume, which has to be kept free for potential floodwater. The dimensioning is based on flood events with certain recurrence intervals. If the water level exceeds the mark of the protection area, an increased discharge to the downstream water of the storage ensures that the area is kept empty. Thus, this rule is reduced to a relation between discharge and storage volume, where the outlet capacity or a defined maximum discharge can serve as an upper limit for keeping the flood protection area empty. If the flood protection area is variable in time over the year, only the discharge of the respective storage volume is increased.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:There is a direct relation between storage capacity and release. If the storage capacity exceeds the mark of the flood protection area, a discharge occurs. If it remains below the mark, the discharge is set to zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 3: Direct Withdrawals from a storage for Drinking or Service Water ==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb4.png|thumb|Figure 4: Example of a function for drinking or raw water withdrawal]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Primarily, the current demand determines the volume of withdrawals from the storage, but it is also subject to temporal variations. The upper limits for withdrawals are generally set by water rights or defined maximum withdrawal volumes, which refer to selected periods such as a day, a month, a quarter, or a year. Initially, one only considers the current demand communicated by water suppliers, which constitutes a claim towards the storage. There is no connection to the actual storage and the respective storage volume.&lt;br /&gt;
:Whether the demand can be pleased by withdrawing water from the storage is determined by the actual storage volumes. To connect the water demand to the actual storage volumes, the structural implementation of withdrawal elements and means of anticipatory management are taken into account. For example, if particularly low storage volumes are reached, it is advisable to throttle withdrawals in advance to avoid the storage running empty and then completely failing at covering the demand during prolonged periods of low water &amp;lt;ref name=&amp;quot;Schultz_1989&amp;quot;&amp;gt;&#039;&#039;&#039;Schultz, G.A.&#039;&#039;&#039; (1989): Entwicklung von Betriebsregeln für die Wupper-Talsperre in Niedrig- und Hochwasserzeiten. Wasserwirtschaft 79 (7/8) S. 340-343&amp;lt;/ref&amp;gt;. Hence, there is usually space reserved in a dam specifically used for drinking water supply. Its use is handled separately in respective operating plans.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:If the demand is exactly known and unchangeable, a direct relation between withdrawal and storage volume can be defined. However, the demand is subject to certain variations. For this reason, it is recommended to normalize the relationship between withdrawals and storage volume, where the current demand serves as a scaling factor. If the storage volume falls below a defined limit value, only a certain percentage of the current demand is satisfied. The limit value, as well as the form of the function, can be variable in time.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 4: Standard Discharge to Downstream Water==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb5.png|thumb|Figure 5: Pool-based operating plan in a two-dimensional representation]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The normal discharge to the downstream water should provide a discharge compensation for seasonal differences in the inflow. If a minimum discharge is required, it will be included in the normal discharge. A pool-based operating plan is used to describe the normal discharge. It divides the storage capacity into different areas and assigns a discharge to each pool-based operation. When determining the pool-based operating plan, the long-term discharge and other withdrawals from the reservoir for other purposes play a decisive role. A reservoir should collect water in periods of high inflow but still not overflow to have sufficient reserves in periods of low inflow. The coupling of the releases to the storage pool-based operation is a function of the storage volume. Since the system is supposed to react to variations of inflow during the year, the relationship between storage volume and discharge is usually variable over time.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb6.png|thumb|Figure 6: Comparison of a pool-based operating plan in a two- and three-dimensional representation]] Like for the previous rules, the output depends on the storage volume. Usually, a pool-based operating plan is displayed in two-dimensional diagrams. The X-axis shows the time of one year, while the Y-axis shows the storage capacity. Pool-based operations are depicted as lines of equal outputs.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb7.png|thumb|Figure 7: Pool-based operating plan with linear interpolation between successive time reference points]]This view is practical but not yet complete: A three-dimensional representation of a simple pool-based operating plan makes this clear. On the X-axis is the time, on the Y-axis the storage capacity is plotted, while the Z-axis shows the output directed upwards.&lt;br /&gt;
&lt;br /&gt;
:The 3D image viewed from above gives the two-dimensional shape. Instead of taking constant blocks for the individual time horizons, a linear connection is also used often.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb8.png|thumb|Figure 8: Pool-based operating plan with two types of interpretation (selected month of May)]]For the individual periods - here months - different functional dependencies between storage capacity and outflow are considered. If the storage volume/discharge relation is also considered for a selected point in time, there are two possibilities to connect the discharge nodes. On the one hand, there is the possibility of linear interpolation, and on the other hand, a step function is possible.&lt;br /&gt;
&lt;br /&gt;
:In two-dimensional space, this information is not visible and must be specified separately. However, there is usually the convention to assume that the output between two nodes is constant, i.e. to interpret the pool-based operating plan as shown above in the form of steps.&amp;lt;br clear=&amp;quot;all&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 5: Maintaining Defined Discharges to Downstream Waters (Increase of Low Water / Coverage of Demand)==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb9.png|thumb|Figure 9: Example of a function between shortfalls and scaling factors for a storage&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
* Dependency: &lt;br /&gt;
:In this case, the current discharge is determined by conditions downstream of a storage. At a cross-section of a water resources system, the so-called &#039;&#039;control point&#039;&#039;, where the flow is dependent on the discharge from the upstream storage, a minimum flow is defined. The flow at the control point is composed of the discharge from upstream storages and the lateral inflows between the storages and the control point. If the current flow remains below the set minimum, an additional discharge from upstream storages is necessary. The volume of the additional discharge depends on the difference between the previously defined target flow and the actual flow. Whether the required discharge can be fully provided from the storage depends on the currently available stored volumes in the storage. The lower the level, the less favorable it is to provide additional water. In this context, the increase of low water/coverage of demand behaves completely identical to the drinking or service water withdrawal, with only the triggering factor differing. As mentioned before, a storage-dependent function is scaled by a factor, but this factor is now derived from a comparison between set values and current discharges.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:The determination of the additionally needed discharge is composed of several factors. Firstly, a volumetrically varying shortfall of water results from failing the target discharge. The shortfall of water is then implemented as a scaling factor to the discharge which can be defined by a function. The shortfall of water functions independently, while the scaling factor functions dependently.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb10.png|thumb|Figure 10: Example of a function for increasing low water levels or meeting demand]]&lt;br /&gt;
&lt;br /&gt;
:Secondly, it depends on the actual storage volume, if and how an additional discharge from the storage can be met. A normalized volume-dependent function and the needed discharge lead to a clear determination of the additional discharge volumes. The following [[:Datei:Theorie_Abb10.png||Fig. 10]] shows an example, where the complete provision of an increased target can only be achieved if the filling level of the storage is above a critical limit (25%).&lt;br /&gt;
&lt;br /&gt;
:If more than one storage has an influence on the relevant control point or if, in principle, more than one storage facility is to be used to meet the demand, the required additional discharge is to be divided between the storages in accordance with the corresponding regulations. A distinction must be made between the direct and indirect influences of a storage on the control point. A direct influence is present if a discharge can have a direct effect on the flow conditions at the control point, i.e. the natural flow between the storage &lt;br /&gt;
and the control point can no longer be changed by regulation. If this is not the case, an indirect influence is given.&lt;br /&gt;
&lt;br /&gt;
:All storages with a direct influence on the control point receive a shortfall factor and a volume-dependent, scalable function according to [[:Datei:Theorie_Abb10.png|Figure 10]]. Thus, depending on the shortfall quantities and the storage capacity, the actual discharge can be determined separately for each storage.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 6: Discharge Depending on the storage Inflow==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb11.png|thumb|Figure 11: Direct dependency between storage and control point]]&lt;br /&gt;
:There is a direct dependency between the discharge from the storage and the current inflow to the storage. Similar to the pool-based operating plan, there is also an adaptation to different inflow situations. This is done to prevent depletion or overflowing or to obtain a variable discharge regime downstream. However, long-term inflow fluctuations are difficult to detect with this operating rule, since the observations are only carried out as snapshots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:To determine an inflow-dependent discharge, several components have to be considered. First of all, a relation between the current inflow and discharge must be defined. In addition to the current inflow, the current storage volume is important, because the relation inflow/outflow must not be valid for every filling level. Thus it is likely that the relation is ceded completely or the release quantities are adjusted if the storage level falls below a critical level.&lt;br /&gt;
&lt;br /&gt;
:As this rule can lead to the co-occurrence of relatively small storage volumes and high inflows resulting in high discharge volumes, special attention must be paid to the basic principle of checking the physical limits.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb12.png|thumb|Figure 12: Example of functions for inflow-dependent discharge]]&lt;br /&gt;
:In this case, three functional dependencies play a part. First, there is a direct dependency between the current inflow and the discharge. The form of the function can be arbitrary. It is possible to reproduce only individual sections of the inflow, which corresponds to a partial approximation of the discharge to the duration curve of the inflow.&lt;br /&gt;
&lt;br /&gt;
:Second, the inflow/discharge function can be superposed with the relationship between storage volume and discharge. For reasons of clarity, it is recommended to work with a normalized function. This makes it possible to influence the result of the inflow/discharge function for each storage volume, which is especially convenient for low filling levels.&lt;br /&gt;
&lt;br /&gt;
:Finally, the required discharge has to be checked with regard to the outlet elements&#039; capacity.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb13.png|thumb|left|Figure 13: Results of different inflow-dependent release strategies]]&lt;br /&gt;
&lt;br /&gt;
:The examples below show how the interaction of different functions affects the discharges. The results are compared in the following figures as inflow and discharge duration lines.&lt;br /&gt;
&lt;br /&gt;
:In the case of a linear relation between inflow and discharge and a constant factor for the storage volume, the duration line of the discharge is a curve corresponding to the inflow reduced by a certain percentage. If the storage volume factor remains constant, the duration line can be changed by varying the inflow/discharge relationship. An additional modification of the factor via the storage volume has the advantage of being able to respond to certain filling levels to prevent the storage from emptying or overflowing.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 7: Influence of Discharges Trough System States==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Rule 7, just as rule 6, is a continuation and generalization of the increase of low water as described in rules 5. Just like a discharge deficit at a cross-section or the storage inflow can influence the discharge, any other system state can. In general terms, this means that a discharge from a storage is triggered, increased, or reduced due to a certain system state. Basically, it is irrelevant where the system state occurs. All measurable variables that influence the transport and storage of water can be considered as system states, e.g. the filling of other storages, discharges, flow regime at a cross-section, a snow depth in the catchment area, current precipitation, or current soil moisture.&lt;br /&gt;
&lt;br /&gt;
:As a requirement to apply those dependencies a detection of the system state is necessary. Practically, this means either that a measuring device must be available to determine needed parameters or the required values are calculated using a mathematical model. Parameters are only considered as snap-shots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:If several system states should influence the discharge, a superposition of the parameters according to a corresponding regulation is necessary.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Mathematically, the influence of system states on the discharge can always be undertaken by scaling. Two functions are necessary for this. The first function describes the relationship between storage volume and discharge. The second one controls the dependency between the system state and a scaling factor. The connection is done by multiplying the discharge with the scaling factor.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb13.5.png|thumb|Transition]]&lt;br /&gt;
&lt;br /&gt;
:A simple example is given by a transition from storage A to storage B. &lt;br /&gt;
&lt;br /&gt;
:The decisive discharge is the transition from A to B. The considered system state is the storage volume of B. It seems obvious that a discharge from A to B is only useful if storage A has sufficient provision and storage B has sufficient capacity to hold additional water. This results in the following simple functions:&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb14.png|thumb|left|Figure 14: Example functions for linking a system state to a discharge]]Reservoir B takes 100% of the discharge from A as long as its filling level does not reach 70% of the maximum volume. Furthermore, it is undesirable to receive additional water for flood protection reasons. The scaling factor decreases from 70% filling level to zero. Starting at a filling level above 50% it becomes increasingly easy to transfer water from Reservoir A to reservoir B. The actual transfer, however, only results from the interaction of both functions, taking into account the current filling level of reservoir B and the scaling derived from it.&lt;br /&gt;
&lt;br /&gt;
:For storage A, the definition of the discharge is in m³/s, while the function for storage B receives a unitless scaling factor. In principle, however, it is possible to exchange the meaning of the functions and to use a unitless function for storage A to scale the desired transfer volume for storage B.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 8: Influencing a Discharge with Balances==&lt;br /&gt;
&lt;br /&gt;
 Dependency: [[Datei:Theorie_Abb15.png|thumb|Figure 15 : Example of long-term monthly averages and moving 30 day averages of storage volumes]]&lt;br /&gt;
:This rule is an extension of rule 7. Instead of using a current state parameter, the balance of a system state is linked to discharge. It is important that there are set time boundaries for carrying out the balance. However, it is irrelevant whether the balance is interpreted as a sum or as an average. A function that displays scaling factors depending on the actual balance can then be used to influence discharges.&lt;br /&gt;
&lt;br /&gt;
:In practice, this form of dependency is often found where water rights define maximum withdrawal volumes per time unit. But the application of a balance is also interesting regarding the long-term behaviour of storage filling levels or inflows. For example, a discharge could be reduced to build up provisions if the inflow of the past winter half-year was below a defined expected value. Another application is the comparison between long-term and current moving averages of storage filling levels. If the current values deviate from the long-term values by a certain amount, the discharge can be reduced or increased to compensate.&lt;br /&gt;
&lt;br /&gt;
:If linking a discharge to several balances is desired, it is possible to superpose several balances (see example at the end of this chapter). &lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb16.png|thumb|Figure 16: Example of a rule for standard discharge]]&lt;br /&gt;
:The influence of the balance on the discharge is posed by two functions according to rule 7. In addition to the already necessary storage volume/discharge function, there is a relation between the balance and scaling factor. The scaling factor is taken from the difference between the actual balance and the expected value.&lt;br /&gt;
&lt;br /&gt;
:The method is demonstrated with a simple example of a standard discharge.&lt;br /&gt;
&lt;br /&gt;
:For storage A, long-term monthly mean values of the storage volumes and derived sliding 30-day mean values of the storage filling levels, as well as the rule for the standard discharge, are known.&lt;br /&gt;
&lt;br /&gt;
:If, for example, on May 1st the average value of the storage volume calculated from the last 30 days amounts to 5.6 million m³ and thus, according to [[:Datei:Theorie_Abb15.png|Fig. 15]], it deviates by 30% from the long-term average value of 8 million m³, a scaling factor of 0.5 results (see [[:Datei:Theorie_Abb16.png|Fig. 16]]). With this value, the standard discharge is reduced and delivers only 0.25m³/s at a current storage filling level of 40%, i.e. 50% less than intended.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb17.png|thumb|left|Abbildung 17: Example functions to link a water balance with a discharge]]The relation between the deviation of the balance and the scaling factor indicates that only starting from a difference greater than 20% a change of the standard discharge takes place. In the case of a decrease of more than 20%, the standard discharge is reduced stepwise. If the actual moving 30-day average exceeds the long-term values by more than 20%, the standard discharge is increased continuously.&lt;br /&gt;
&lt;br /&gt;
:In general, there is also the possibility to extend the relation by superposing and combining several water balances.&lt;br /&gt;
&lt;br /&gt;
:The interaction between water balance and discharge function is explained below.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 9: Priorities for Competing Discharges from a Storage==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb18.png|thumb|Figure 18: Example for assigning priorities via the position of functions]]&lt;br /&gt;
:If there are several discharges from a storage, it can occur that it is not possible to carry out all demanded discharges. In such a case, priorities need to be specified, which determine an order in which discharges are to be satisfied. The order of priorities is often a consequence of political decisions and is not subject to physical conditions.&lt;br /&gt;
&lt;br /&gt;
:However, there are some priorities based on physical conditions. An example is turning off a turbine in times of water shortage in favor of securing the water supply. In practice, operating rules often meet this problem by fulfilling demands up to defined storage volumes, but not maintaining discharges below the set storage volume.&lt;br /&gt;
&lt;br /&gt;
:Another way to describe priorities is to reduce a discharge A exactly by an amount, which is resulting from a second discharge B, with the discharge A never being smaller than zero.&lt;br /&gt;
&lt;br /&gt;
* Practical example:&lt;br /&gt;
:The Wiehl dam gives a good example for the practical operating conditions of a dam. The Wiehl dam serves primarily as a drinking water supply and a means for flood protection, and secondarily for energy production. In addition, a minimum flow of 100 l/s has to be guaranteed downstream of the Wiehl dam. The first priority is the drinking water supply. In order to ensure sufficient water quality in the storage, additional discharges used for energy production are stopped when the storage volume falls below 70% of the total volume. As both the minimum discharge and the turbine discharge leave into the Wiehl, it would also be uncalled-for to maintain the minimum discharge if water was simultaneously discharged through the turbine. This results in a reduction of a discharge A (minimum discharge) by the amount of discharge B (turbine) as described above &amp;lt;ref name=&amp;quot;Aggerverband_1999&amp;quot;&amp;gt;&#039;&#039;&#039;Aggerverband&#039;&#039;&#039; (1999): Hydrologische Sicherheit der Genkel- und Aggertalsperre. Gutachten des Fachgebietes Ingenieurhydrologie und Wasserbewirtschaftung, TU Darmstadt&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb19.png|thumb||Figure 19: Example of a relation between two discharges]]&lt;br /&gt;
:Assuming that for each use, following the above rules, a functional dependency between storage content and discharge exists, a ranking of several uses is already given by the position of the function&#039;s nodes.  Then, the respective storage volume from which the target discharge is no longer covered to 100% or even reduced to zero is decisive.&lt;br /&gt;
&lt;br /&gt;
:In the example, the ranking of the uses is clearly visible. First, the turbine is switched off, then the increase of low water refrained from until only the discharge covering the water supply remains.&lt;br /&gt;
&lt;br /&gt;
:In addition, it is possible to directly compare two or more discharges. Such a rule could be:&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;If discharge B &amp;gt; 0 and the storage volume S &amp;lt; X, then reduce discharge A by the amount of discharge B, with discharge  A not being smaller than zero.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:This means that a linear dependency exists between A and B until B is equal to the value of A. If B increases further, A remains constantly zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 11: Water Distribution==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:If there is the need to distribute water within a water resources system, a distribution rule must be defined.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb19.5.png|thumb|Diversion]]&lt;br /&gt;
&lt;br /&gt;
:Two types of diversions can occur:&lt;br /&gt;
:# Diversion that exclusively follows hydraulic laws &lt;br /&gt;
:# Adjustable diversions &lt;br /&gt;
&lt;br /&gt;
:In both cases, relations can always be defined as a function of the inflow. In the second case, these distribution rules represent an operating rule, since they directly influence the transport and storage behavior of water. The number of discharges is basically not limited. The difference to transitions at dams is that in this case no storage volume can be used as a reference value.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb20.png|thumb|Figure 20 :Example of assignment functions for multiple sequences]]&lt;br /&gt;
&lt;br /&gt;
* Practical example: &lt;br /&gt;
:The water supply of Windhoek, the capital of Namibia, is provided by three dams. However, the water withdrawal for the drinking water supply is only possible from one dam - the Von Bach Dam. The remaining two storages are connected to the main dam by pipes. However, the volume transferred between Swakopport Dam and Von Bach Dam is not exclusively available for refilling the Von Bach Dam, but also serves to supply the town of Karibib with drinking water.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb21.png|thumb|left|Fig. 21: Example of a threshold concept for a division into two flows]]For the definition of division rules, functions depending on the current inflow are an appropriate representation. Thus, both a hydraulic description and a description serving the management of the storage are possible. For each discharge leaving the diversion structure, a distribution function has to be specified. If the functions are to be variable, scaling is recommended.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb22.png|thumb|Figure 22: Example of a threshold concept with a distribution to serve several users&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
:If the distribution functions cannot be pre-defined, but the discharge volumes rather result later from demand calculations, then a threshold concept is suitable, which in turn can work with scaling factors. The threshold is scaled by a factor and is therefore variable. As long as the inflow is lower than the threshold, the entire inflow is used to satisfy the demand. Only when the current inflow exceeds the threshold, the remaining amount is discharged.&lt;br /&gt;
&lt;br /&gt;
:If a division into more than two discharges is necessary, the threshold concept can be successively applied several times. The order of the discharges determines the priorities of the water distribution.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Literature==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/87/en&amp;diff=12967</id>
		<title>Translations:Betriebsregeltypen/87/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/87/en&amp;diff=12967"/>
		<updated>2021-08-30T10:36:08Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* Practical example: &lt;br /&gt;
:The water supply of Windhoek, the capital of Namibia, is provided by three dams. However, the water withdrawal for the drinking water supply is only possible from one dam - the Von Bach Dam. The remaining two storages are connected to the main dam by pipes. However, the volume transferred between Swakopport Dam and Von Bach Dam is not exclusively available for refilling the Von Bach Dam, but also serves to supply the town of Karibib with drinking water.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12966</id>
		<title>Betriebsregeltypen/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12966"/>
		<updated>2021-08-30T10:35:54Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=|hoch=Betriebsregelkonzept|nachher=Abstraktion der Betriebsregeln}}&lt;br /&gt;
&lt;br /&gt;
The operating plan of a dam or a storage network is part of the official approval of plans and usually is available as a report or presentation. Its complexity can vary: it ranges from simply defining flood protection areas and setting a report and alarm plan to notify the supervisory authorities in exceptional situations to complex sets of rules concerning functional dependencies that derive discharges from varying system states.&lt;br /&gt;
&lt;br /&gt;
As follows, principles to clarify the variety of possible regulations and reduce them to essential dependencies are presented. A concept is derived to represent most operating rules by a few basic calculation rules. The given selection does not claim to be complete, but it is likely to contain the rules applied in practice.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Basic Principle: Verification of Physical Limits==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb1.png|thumb|Figure 1: Dependency on storage capacity]]&lt;br /&gt;
&lt;br /&gt;
When specifying discharges according to an operating rule, it is assumed that the outlet capacity is sufficient to meet these discharges. Thus, dimensioning the outlet element must consider the operating requirements. In principle, the physically possible discharge, given by the outlet&#039;s characteristic curve at full opening, sets the upper limit value.&lt;br /&gt;
&lt;br /&gt;
If the pressure level or the outlet capacity is sufficient to discharge the desired quantity when fully opened, the discharge can be throttled to the intended level by closing a slide. If the pressure level is insufficient, only the hydraulically possible discharge can be discharged.&lt;br /&gt;
&lt;br /&gt;
*Mathematical abstraction:&lt;br /&gt;
:All outlets obeying an operating rule are functions of the storage&#039;s volume and cannot exceed the outlets&#039; maximum capacity when fully opened. As soon as the capacity of the outlets exceeds the required discharge, it can be adjusted by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
All discharge types from storages mentioned below are subject to this restriction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 1: Definition of a Minimum Output or a Safely Dischargeable Maximum Output==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb2.png|thumb|Figure 2: Example for minimum and maximum discharge as a function of storage capacity]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The specification of a minimum or maximum discharge is based on requirements downstream of a reservoir. The maximal discharge is based on the discharge respective to a critical, downstream cross-section. Consequently, a hydraulic method exists for its determination. In contrast, there is no clear guideline for the minimum discharge. Often, ratios of MNQ or MQ are used. Independent of determining the minimum or maximum discharge, the basic principle to verify outlet elements&#039; physical limits is applied. So, minimum and maximum discharge can only be discharged if the outlet capacity is sufficient at the given pressure level. Since, in reality, it is unlikely that the dimensioning of the outlet elements and the required discharge are conflicting, the reference to the dependence on the storage capacity content is rather theoretical but necessary to derive general laws.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Minimum and maximum discharge are functions of the storage volume and follow the characteristic curve of fully opened outlets at a low filling level. As soon as the outlet elements&#039; capacity is sufficient for the required discharge volume, the discharge can be kept constant by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 2: Maintaining a Flood Protection Area, Possibly Timely Variable Over the Year==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb3.png|thumb|Figure 3: Example of a function to maintain a flood protection area]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The definition of a flood protection area as a minimum requirement only includes the designation of a volume, which has to be kept free for potential floodwater. The dimensioning is based on flood events with certain recurrence intervals. If the water level exceeds the mark of the protection area, an increased discharge to the downstream water of the storage ensures that the area is kept empty. Thus, this rule is reduced to a relation between discharge and storage volume, where the outlet capacity or a defined maximum discharge can serve as an upper limit for keeping the flood protection area empty. If the flood protection area is variable in time over the year, only the discharge of the respective storage volume is increased.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:There is a direct relation between storage capacity and release. If the storage capacity exceeds the mark of the flood protection area, a discharge occurs. If it remains below the mark, the discharge is set to zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 3: Direct Withdrawals from a storage for Drinking or Service Water ==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb4.png|thumb|Figure 4: Example of a function for drinking or raw water withdrawal]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Primarily, the current demand determines the volume of withdrawals from the storage, but it is also subject to temporal variations. The upper limits for withdrawals are generally set by water rights or defined maximum withdrawal volumes, which refer to selected periods such as a day, a month, a quarter, or a year. Initially, one only considers the current demand communicated by water suppliers, which constitutes a claim towards the storage. There is no connection to the actual storage and the respective storage volume.&lt;br /&gt;
:Whether the demand can be pleased by withdrawing water from the storage is determined by the actual storage volumes. To connect the water demand to the actual storage volumes, the structural implementation of withdrawal elements and means of anticipatory management are taken into account. For example, if particularly low storage volumes are reached, it is advisable to throttle withdrawals in advance to avoid the storage running empty and then completely failing at covering the demand during prolonged periods of low water &amp;lt;ref name=&amp;quot;Schultz_1989&amp;quot;&amp;gt;&#039;&#039;&#039;Schultz, G.A.&#039;&#039;&#039; (1989): Entwicklung von Betriebsregeln für die Wupper-Talsperre in Niedrig- und Hochwasserzeiten. Wasserwirtschaft 79 (7/8) S. 340-343&amp;lt;/ref&amp;gt;. Hence, there is usually space reserved in a dam specifically used for drinking water supply. Its use is handled separately in respective operating plans.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:If the demand is exactly known and unchangeable, a direct relation between withdrawal and storage volume can be defined. However, the demand is subject to certain variations. For this reason, it is recommended to normalize the relationship between withdrawals and storage volume, where the current demand serves as a scaling factor. If the storage volume falls below a defined limit value, only a certain percentage of the current demand is satisfied. The limit value, as well as the form of the function, can be variable in time.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 4: Standard Discharge to Downstream Water==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb5.png|thumb|Figure 5: Pool-based operating plan in a two-dimensional representation]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The normal discharge to the downstream water should provide a discharge compensation for seasonal differences in the inflow. If a minimum discharge is required, it will be included in the normal discharge. A pool-based operating plan is used to describe the normal discharge. It divides the storage capacity into different areas and assigns a discharge to each pool-based operation. When determining the pool-based operating plan, the long-term discharge and other withdrawals from the reservoir for other purposes play a decisive role. A reservoir should collect water in periods of high inflow but still not overflow to have sufficient reserves in periods of low inflow. The coupling of the releases to the storage pool-based operation is a function of the storage volume. Since the system is supposed to react to variations of inflow during the year, the relationship between storage volume and discharge is usually variable over time.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb6.png|thumb|Figure 6: Comparison of a pool-based operating plan in a two- and three-dimensional representation]] Like for the previous rules, the output depends on the storage volume. Usually, a pool-based operating plan is displayed in two-dimensional diagrams. The X-axis shows the time of one year, while the Y-axis shows the storage capacity. Pool-based operations are depicted as lines of equal outputs.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb7.png|thumb|Figure 7: Pool-based operating plan with linear interpolation between successive time reference points]]This view is practical but not yet complete: A three-dimensional representation of a simple pool-based operating plan makes this clear. On the X-axis is the time, on the Y-axis the storage capacity is plotted, while the Z-axis shows the output directed upwards.&lt;br /&gt;
&lt;br /&gt;
:The 3D image viewed from above gives the two-dimensional shape. Instead of taking constant blocks for the individual time horizons, a linear connection is also used often.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb8.png|thumb|Figure 8: Pool-based operating plan with two types of interpretation (selected month of May)]]For the individual periods - here months - different functional dependencies between storage capacity and outflow are considered. If the storage volume/discharge relation is also considered for a selected point in time, there are two possibilities to connect the discharge nodes. On the one hand, there is the possibility of linear interpolation, and on the other hand, a step function is possible.&lt;br /&gt;
&lt;br /&gt;
:In two-dimensional space, this information is not visible and must be specified separately. However, there is usually the convention to assume that the output between two nodes is constant, i.e. to interpret the pool-based operating plan as shown above in the form of steps.&amp;lt;br clear=&amp;quot;all&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 5: Maintaining Defined Discharges to Downstream Waters (Increase of Low Water / Coverage of Demand)==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb9.png|thumb|Figure 9: Example of a function between shortfalls and scaling factors for a storage&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
* Dependency: &lt;br /&gt;
:In this case, the current discharge is determined by conditions downstream of a storage. At a cross-section of a water resources system, the so-called &#039;&#039;control point&#039;&#039;, where the flow is dependent on the discharge from the upstream storage, a minimum flow is defined. The flow at the control point is composed of the discharge from upstream storages and the lateral inflows between the storages and the control point. If the current flow remains below the set minimum, an additional discharge from upstream storages is necessary. The volume of the additional discharge depends on the difference between the previously defined target flow and the actual flow. Whether the required discharge can be fully provided from the storage depends on the currently available stored volumes in the storage. The lower the level, the less favorable it is to provide additional water. In this context, the increase of low water/coverage of demand behaves completely identical to the drinking or service water withdrawal, with only the triggering factor differing. As mentioned before, a storage-dependent function is scaled by a factor, but this factor is now derived from a comparison between set values and current discharges.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:The determination of the additionally needed discharge is composed of several factors. Firstly, a volumetrically varying shortfall of water results from failing the target discharge. The shortfall of water is then implemented as a scaling factor to the discharge which can be defined by a function. The shortfall of water functions independently, while the scaling factor functions dependently.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb10.png|thumb|Figure 10: Example of a function for increasing low water levels or meeting demand]]&lt;br /&gt;
&lt;br /&gt;
:Secondly, it depends on the actual storage volume, if and how an additional discharge from the storage can be met. A normalized volume-dependent function and the needed discharge lead to a clear determination of the additional discharge volumes. The following [[:Datei:Theorie_Abb10.png||Fig. 10]] shows an example, where the complete provision of an increased target can only be achieved if the filling level of the storage is above a critical limit (25%).&lt;br /&gt;
&lt;br /&gt;
:If more than one storage has an influence on the relevant control point or if, in principle, more than one storage facility is to be used to meet the demand, the required additional discharge is to be divided between the storages in accordance with the corresponding regulations. A distinction must be made between the direct and indirect influences of a storage on the control point. A direct influence is present if a discharge can have a direct effect on the flow conditions at the control point, i.e. the natural flow between the storage &lt;br /&gt;
and the control point can no longer be changed by regulation. If this is not the case, an indirect influence is given.&lt;br /&gt;
&lt;br /&gt;
:All storages with a direct influence on the control point receive a shortfall factor and a volume-dependent, scalable function according to [[:Datei:Theorie_Abb10.png|Figure 10]]. Thus, depending on the shortfall quantities and the storage capacity, the actual discharge can be determined separately for each storage.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 6: Discharge Depending on the storage Inflow==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb11.png|thumb|Figure 11: Direct dependency between storage and control point]]&lt;br /&gt;
:There is a direct dependency between the discharge from the storage and the current inflow to the storage. Similar to the pool-based operating plan, there is also an adaptation to different inflow situations. This is done to prevent depletion or overflowing or to obtain a variable discharge regime downstream. However, long-term inflow fluctuations are difficult to detect with this operating rule, since the observations are only carried out as snapshots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:To determine an inflow-dependent discharge, several components have to be considered. First of all, a relation between the current inflow and discharge must be defined. In addition to the current inflow, the current storage volume is important, because the relation inflow/outflow must not be valid for every filling level. Thus it is likely that the relation is ceded completely or the release quantities are adjusted if the storage level falls below a critical level.&lt;br /&gt;
&lt;br /&gt;
:As this rule can lead to the co-occurrence of relatively small storage volumes and high inflows resulting in high discharge volumes, special attention must be paid to the basic principle of checking the physical limits.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb12.png|thumb|Figure 12: Example of functions for inflow-dependent discharge]]&lt;br /&gt;
:In this case, three functional dependencies play a part. First, there is a direct dependency between the current inflow and the discharge. The form of the function can be arbitrary. It is possible to reproduce only individual sections of the inflow, which corresponds to a partial approximation of the discharge to the duration curve of the inflow.&lt;br /&gt;
&lt;br /&gt;
:Second, the inflow/discharge function can be superposed with the relationship between storage volume and discharge. For reasons of clarity, it is recommended to work with a normalized function. This makes it possible to influence the result of the inflow/discharge function for each storage volume, which is especially convenient for low filling levels.&lt;br /&gt;
&lt;br /&gt;
:Finally, the required discharge has to be checked with regard to the outlet elements&#039; capacity.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb13.png|thumb|left|Figure 13: Results of different inflow-dependent release strategies]]&lt;br /&gt;
&lt;br /&gt;
:The examples below show how the interaction of different functions affects the discharges. The results are compared in the following figures as inflow and discharge duration lines.&lt;br /&gt;
&lt;br /&gt;
:In the case of a linear relation between inflow and discharge and a constant factor for the storage volume, the duration line of the discharge is a curve corresponding to the inflow reduced by a certain percentage. If the storage volume factor remains constant, the duration line can be changed by varying the inflow/discharge relationship. An additional modification of the factor via the storage volume has the advantage of being able to respond to certain filling levels to prevent the storage from emptying or overflowing.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 7: Influence of Discharges Trough System States==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Rule 7, just as rule 6, is a continuation and generalization of the increase of low water as described in rules 5. Just like a discharge deficit at a cross-section or the storage inflow can influence the discharge, any other system state can. In general terms, this means that a discharge from a storage is triggered, increased, or reduced due to a certain system state. Basically, it is irrelevant where the system state occurs. All measurable variables that influence the transport and storage of water can be considered as system states, e.g. the filling of other storages, discharges, flow regime at a cross-section, a snow depth in the catchment area, current precipitation, or current soil moisture.&lt;br /&gt;
&lt;br /&gt;
:As a requirement to apply those dependencies a detection of the system state is necessary. Practically, this means either that a measuring device must be available to determine needed parameters or the required values are calculated using a mathematical model. Parameters are only considered as snap-shots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:If several system states should influence the discharge, a superposition of the parameters according to a corresponding regulation is necessary.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Mathematically, the influence of system states on the discharge can always be undertaken by scaling. Two functions are necessary for this. The first function describes the relationship between storage volume and discharge. The second one controls the dependency between the system state and a scaling factor. The connection is done by multiplying the discharge with the scaling factor.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb13.5.png|thumb|Transition]]&lt;br /&gt;
&lt;br /&gt;
:A simple example is given by a transition from storage A to storage B. &lt;br /&gt;
&lt;br /&gt;
:The decisive discharge is the transition from A to B. The considered system state is the storage volume of B. It seems obvious that a discharge from A to B is only useful if storage A has sufficient provision and storage B has sufficient capacity to hold additional water. This results in the following simple functions:&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb14.png|thumb|left|Figure 14: Example functions for linking a system state to a discharge]]Reservoir B takes 100% of the discharge from A as long as its filling level does not reach 70% of the maximum volume. Furthermore, it is undesirable to receive additional water for flood protection reasons. The scaling factor decreases from 70% filling level to zero. Starting at a filling level above 50% it becomes increasingly easy to transfer water from Reservoir A to reservoir B. The actual transfer, however, only results from the interaction of both functions, taking into account the current filling level of reservoir B and the scaling derived from it.&lt;br /&gt;
&lt;br /&gt;
:For storage A, the definition of the discharge is in m³/s, while the function for storage B receives a unitless scaling factor. In principle, however, it is possible to exchange the meaning of the functions and to use a unitless function for storage A to scale the desired transfer volume for storage B.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 8: Influencing a Discharge with Balances==&lt;br /&gt;
&lt;br /&gt;
 Dependency: [[Datei:Theorie_Abb15.png|thumb|Figure 15 : Example of long-term monthly averages and moving 30 day averages of storage volumes]]&lt;br /&gt;
:This rule is an extension of rule 7. Instead of using a current state parameter, the balance of a system state is linked to discharge. It is important that there are set time boundaries for carrying out the balance. However, it is irrelevant whether the balance is interpreted as a sum or as an average. A function that displays scaling factors depending on the actual balance can then be used to influence discharges.&lt;br /&gt;
&lt;br /&gt;
:In practice, this form of dependency is often found where water rights define maximum withdrawal volumes per time unit. But the application of a balance is also interesting regarding the long-term behaviour of storage filling levels or inflows. For example, a discharge could be reduced to build up provisions if the inflow of the past winter half-year was below a defined expected value. Another application is the comparison between long-term and current moving averages of storage filling levels. If the current values deviate from the long-term values by a certain amount, the discharge can be reduced or increased to compensate.&lt;br /&gt;
&lt;br /&gt;
:If linking a discharge to several balances is desired, it is possible to superpose several balances (see example at the end of this chapter). &lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb16.png|thumb|Figure 16: Example of a rule for standard discharge]]&lt;br /&gt;
:The influence of the balance on the discharge is posed by two functions according to rule 7. In addition to the already necessary storage volume/discharge function, there is a relation between the balance and scaling factor. The scaling factor is taken from the difference between the actual balance and the expected value.&lt;br /&gt;
&lt;br /&gt;
:The method is demonstrated with a simple example of a standard discharge.&lt;br /&gt;
&lt;br /&gt;
:For storage A, long-term monthly mean values of the storage volumes and derived sliding 30-day mean values of the storage filling levels, as well as the rule for the standard discharge, are known.&lt;br /&gt;
&lt;br /&gt;
:If, for example, on May 1st the average value of the storage volume calculated from the last 30 days amounts to 5.6 million m³ and thus, according to [[:Datei:Theorie_Abb15.png|Fig. 15]], it deviates by 30% from the long-term average value of 8 million m³, a scaling factor of 0.5 results (see [[:Datei:Theorie_Abb16.png|Fig. 16]]). With this value, the standard discharge is reduced and delivers only 0.25m³/s at a current storage filling level of 40%, i.e. 50% less than intended.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb17.png|thumb|left|Abbildung 17: Example functions to link a water balance with a discharge]]The relation between the deviation of the balance and the scaling factor indicates that only starting from a difference greater than 20% a change of the standard discharge takes place. In the case of a decrease of more than 20%, the standard discharge is reduced stepwise. If the actual moving 30-day average exceeds the long-term values by more than 20%, the standard discharge is increased continuously.&lt;br /&gt;
&lt;br /&gt;
:In general, there is also the possibility to extend the relation by superposing and combining several water balances.&lt;br /&gt;
&lt;br /&gt;
:The interaction between water balance and discharge function is explained below.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 9: Priorities for Competing Discharges from a Storage==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb18.png|thumb|Figure 18: Example for assigning priorities via the position of functions]]&lt;br /&gt;
:If there are several discharges from a storage, it can occur that it is not possible to carry out all demanded discharges. In such a case, priorities need to be specified, which determine an order in which discharges are to be satisfied. The order of priorities is often a consequence of political decisions and is not subject to physical conditions.&lt;br /&gt;
&lt;br /&gt;
:However, there are some priorities based on physical conditions. An example is turning off a turbine in times of water shortage in favor of securing the water supply. In practice, operating rules often meet this problem by fulfilling demands up to defined storage volumes, but not maintaining discharges below the set storage volume.&lt;br /&gt;
&lt;br /&gt;
:Another way to describe priorities is to reduce a discharge A exactly by an amount, which is resulting from a second discharge B, with the discharge A never being smaller than zero.&lt;br /&gt;
&lt;br /&gt;
* Practical example:&lt;br /&gt;
:The Wiehl dam gives a good example for the practical operating conditions of a dam. The Wiehl dam serves primarily as a drinking water supply and a means for flood protection, and secondarily for energy production. In addition, a minimum flow of 100 l/s has to be guaranteed downstream of the Wiehl dam. The first priority is the drinking water supply. In order to ensure sufficient water quality in the storage, additional discharges used for energy production are stopped when the storage volume falls below 70% of the total volume. As both the minimum discharge and the turbine discharge leave into the Wiehl, it would also be uncalled-for to maintain the minimum discharge if water was simultaneously discharged through the turbine. This results in a reduction of a discharge A (minimum discharge) by the amount of discharge B (turbine) as described above &amp;lt;ref name=&amp;quot;Aggerverband_1999&amp;quot;&amp;gt;&#039;&#039;&#039;Aggerverband&#039;&#039;&#039; (1999): Hydrologische Sicherheit der Genkel- und Aggertalsperre. Gutachten des Fachgebietes Ingenieurhydrologie und Wasserbewirtschaftung, TU Darmstadt&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb19.png|thumb||Figure 19: Example of a relation between two discharges]]&lt;br /&gt;
:Assuming that for each use, following the above rules, a functional dependency between storage content and discharge exists, a ranking of several uses is already given by the position of the function&#039;s nodes.  Then, the respective storage volume from which the target discharge is no longer covered to 100% or even reduced to zero is decisive.&lt;br /&gt;
&lt;br /&gt;
:In the example, the ranking of the uses is clearly visible. First, the turbine is switched off, then the increase of low water refrained from until only the discharge covering the water supply remains.&lt;br /&gt;
&lt;br /&gt;
:In addition, it is possible to directly compare two or more discharges. Such a rule could be:&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;If discharge B &amp;gt; 0 and the storage volume S &amp;lt; X, then reduce discharge A by the amount of discharge B, with discharge  A not being smaller than zero.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:This means that a linear dependency exists between A and B until B is equal to the value of A. If B increases further, A remains constantly zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 11: Water Distribution==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:If there is the need to distribute water within a water resources system, a distribution rule must be defined.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb19.5.png|thumb|Diversion]]&lt;br /&gt;
&lt;br /&gt;
:Two types of diversions can occur:&lt;br /&gt;
:# Diversion that exclusively follows hydraulic laws &lt;br /&gt;
:# Adjustable diversions &lt;br /&gt;
&lt;br /&gt;
:In both cases, relations can always be defined as a function of the inflow. In the second case, these distribution rules represent an operating rule, since they directly influence the transport and storage behavior of water. The number of discharges is basically not limited. The difference to transitions at dams is that in this case no storage volume can be used as a reference value.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb20.png|thumb|Figure 20 :Example of assignment functions for multiple sequences]]&lt;br /&gt;
&lt;br /&gt;
* Practical example: &lt;br /&gt;
:The water supply of Windhoek, the capital of Namibia, is provided by three dams. However, the water withdrawal for the drinking water supply is only possible from one dam - the Von Bach Dam. The remaining two reservoirs are connected to the main dam by pipes. However, the volume transferred between Swakopport Dam and Von Bach Dam is not exclusively available for refilling the Von Bach Dam, but also serves to supply the town of Karibib with drinking water.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb21.png|thumb|left|Fig. 21: Example of a threshold concept for a division into two flows]]For the definition of division rules, functions depending on the current inflow are an appropriate representation. Thus, both a hydraulic description and a description serving the management of the storage are possible. For each discharge leaving the diversion structure, a distribution function has to be specified. If the functions are to be variable, scaling is recommended.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb22.png|thumb|Figure 22: Example of a threshold concept with a distribution to serve several users&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
:If the distribution functions cannot be pre-defined, but the discharge volumes rather result later from demand calculations, then a threshold concept is suitable, which in turn can work with scaling factors. The threshold is scaled by a factor and is therefore variable. As long as the inflow is lower than the threshold, the entire inflow is used to satisfy the demand. Only when the current inflow exceeds the threshold, the remaining amount is discharged.&lt;br /&gt;
&lt;br /&gt;
:If a division into more than two discharges is necessary, the threshold concept can be successively applied several times. The order of the discharges determines the priorities of the water distribution.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Literature==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/85/en&amp;diff=12965</id>
		<title>Translations:Betriebsregeltypen/85/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/85/en&amp;diff=12965"/>
		<updated>2021-08-30T10:35:54Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;:In both cases, relations can always be defined as a function of the inflow. In the second case, these distribution rules represent an operating rule, since they directly influence the transport and storage behavior of water. The number of discharges is basically not limited. The difference to transitions at dams is that in this case no storage volume can be used as a reference value.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12964</id>
		<title>Betriebsregeltypen/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12964"/>
		<updated>2021-08-30T10:35:35Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=|hoch=Betriebsregelkonzept|nachher=Abstraktion der Betriebsregeln}}&lt;br /&gt;
&lt;br /&gt;
The operating plan of a dam or a storage network is part of the official approval of plans and usually is available as a report or presentation. Its complexity can vary: it ranges from simply defining flood protection areas and setting a report and alarm plan to notify the supervisory authorities in exceptional situations to complex sets of rules concerning functional dependencies that derive discharges from varying system states.&lt;br /&gt;
&lt;br /&gt;
As follows, principles to clarify the variety of possible regulations and reduce them to essential dependencies are presented. A concept is derived to represent most operating rules by a few basic calculation rules. The given selection does not claim to be complete, but it is likely to contain the rules applied in practice.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Basic Principle: Verification of Physical Limits==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb1.png|thumb|Figure 1: Dependency on storage capacity]]&lt;br /&gt;
&lt;br /&gt;
When specifying discharges according to an operating rule, it is assumed that the outlet capacity is sufficient to meet these discharges. Thus, dimensioning the outlet element must consider the operating requirements. In principle, the physically possible discharge, given by the outlet&#039;s characteristic curve at full opening, sets the upper limit value.&lt;br /&gt;
&lt;br /&gt;
If the pressure level or the outlet capacity is sufficient to discharge the desired quantity when fully opened, the discharge can be throttled to the intended level by closing a slide. If the pressure level is insufficient, only the hydraulically possible discharge can be discharged.&lt;br /&gt;
&lt;br /&gt;
*Mathematical abstraction:&lt;br /&gt;
:All outlets obeying an operating rule are functions of the storage&#039;s volume and cannot exceed the outlets&#039; maximum capacity when fully opened. As soon as the capacity of the outlets exceeds the required discharge, it can be adjusted by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
All discharge types from storages mentioned below are subject to this restriction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 1: Definition of a Minimum Output or a Safely Dischargeable Maximum Output==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb2.png|thumb|Figure 2: Example for minimum and maximum discharge as a function of storage capacity]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The specification of a minimum or maximum discharge is based on requirements downstream of a reservoir. The maximal discharge is based on the discharge respective to a critical, downstream cross-section. Consequently, a hydraulic method exists for its determination. In contrast, there is no clear guideline for the minimum discharge. Often, ratios of MNQ or MQ are used. Independent of determining the minimum or maximum discharge, the basic principle to verify outlet elements&#039; physical limits is applied. So, minimum and maximum discharge can only be discharged if the outlet capacity is sufficient at the given pressure level. Since, in reality, it is unlikely that the dimensioning of the outlet elements and the required discharge are conflicting, the reference to the dependence on the storage capacity content is rather theoretical but necessary to derive general laws.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Minimum and maximum discharge are functions of the storage volume and follow the characteristic curve of fully opened outlets at a low filling level. As soon as the outlet elements&#039; capacity is sufficient for the required discharge volume, the discharge can be kept constant by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 2: Maintaining a Flood Protection Area, Possibly Timely Variable Over the Year==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb3.png|thumb|Figure 3: Example of a function to maintain a flood protection area]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The definition of a flood protection area as a minimum requirement only includes the designation of a volume, which has to be kept free for potential floodwater. The dimensioning is based on flood events with certain recurrence intervals. If the water level exceeds the mark of the protection area, an increased discharge to the downstream water of the storage ensures that the area is kept empty. Thus, this rule is reduced to a relation between discharge and storage volume, where the outlet capacity or a defined maximum discharge can serve as an upper limit for keeping the flood protection area empty. If the flood protection area is variable in time over the year, only the discharge of the respective storage volume is increased.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:There is a direct relation between storage capacity and release. If the storage capacity exceeds the mark of the flood protection area, a discharge occurs. If it remains below the mark, the discharge is set to zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 3: Direct Withdrawals from a storage for Drinking or Service Water ==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb4.png|thumb|Figure 4: Example of a function for drinking or raw water withdrawal]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Primarily, the current demand determines the volume of withdrawals from the storage, but it is also subject to temporal variations. The upper limits for withdrawals are generally set by water rights or defined maximum withdrawal volumes, which refer to selected periods such as a day, a month, a quarter, or a year. Initially, one only considers the current demand communicated by water suppliers, which constitutes a claim towards the storage. There is no connection to the actual storage and the respective storage volume.&lt;br /&gt;
:Whether the demand can be pleased by withdrawing water from the storage is determined by the actual storage volumes. To connect the water demand to the actual storage volumes, the structural implementation of withdrawal elements and means of anticipatory management are taken into account. For example, if particularly low storage volumes are reached, it is advisable to throttle withdrawals in advance to avoid the storage running empty and then completely failing at covering the demand during prolonged periods of low water &amp;lt;ref name=&amp;quot;Schultz_1989&amp;quot;&amp;gt;&#039;&#039;&#039;Schultz, G.A.&#039;&#039;&#039; (1989): Entwicklung von Betriebsregeln für die Wupper-Talsperre in Niedrig- und Hochwasserzeiten. Wasserwirtschaft 79 (7/8) S. 340-343&amp;lt;/ref&amp;gt;. Hence, there is usually space reserved in a dam specifically used for drinking water supply. Its use is handled separately in respective operating plans.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:If the demand is exactly known and unchangeable, a direct relation between withdrawal and storage volume can be defined. However, the demand is subject to certain variations. For this reason, it is recommended to normalize the relationship between withdrawals and storage volume, where the current demand serves as a scaling factor. If the storage volume falls below a defined limit value, only a certain percentage of the current demand is satisfied. The limit value, as well as the form of the function, can be variable in time.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 4: Standard Discharge to Downstream Water==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb5.png|thumb|Figure 5: Pool-based operating plan in a two-dimensional representation]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The normal discharge to the downstream water should provide a discharge compensation for seasonal differences in the inflow. If a minimum discharge is required, it will be included in the normal discharge. A pool-based operating plan is used to describe the normal discharge. It divides the storage capacity into different areas and assigns a discharge to each pool-based operation. When determining the pool-based operating plan, the long-term discharge and other withdrawals from the reservoir for other purposes play a decisive role. A reservoir should collect water in periods of high inflow but still not overflow to have sufficient reserves in periods of low inflow. The coupling of the releases to the storage pool-based operation is a function of the storage volume. Since the system is supposed to react to variations of inflow during the year, the relationship between storage volume and discharge is usually variable over time.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb6.png|thumb|Figure 6: Comparison of a pool-based operating plan in a two- and three-dimensional representation]] Like for the previous rules, the output depends on the storage volume. Usually, a pool-based operating plan is displayed in two-dimensional diagrams. The X-axis shows the time of one year, while the Y-axis shows the storage capacity. Pool-based operations are depicted as lines of equal outputs.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb7.png|thumb|Figure 7: Pool-based operating plan with linear interpolation between successive time reference points]]This view is practical but not yet complete: A three-dimensional representation of a simple pool-based operating plan makes this clear. On the X-axis is the time, on the Y-axis the storage capacity is plotted, while the Z-axis shows the output directed upwards.&lt;br /&gt;
&lt;br /&gt;
:The 3D image viewed from above gives the two-dimensional shape. Instead of taking constant blocks for the individual time horizons, a linear connection is also used often.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb8.png|thumb|Figure 8: Pool-based operating plan with two types of interpretation (selected month of May)]]For the individual periods - here months - different functional dependencies between storage capacity and outflow are considered. If the storage volume/discharge relation is also considered for a selected point in time, there are two possibilities to connect the discharge nodes. On the one hand, there is the possibility of linear interpolation, and on the other hand, a step function is possible.&lt;br /&gt;
&lt;br /&gt;
:In two-dimensional space, this information is not visible and must be specified separately. However, there is usually the convention to assume that the output between two nodes is constant, i.e. to interpret the pool-based operating plan as shown above in the form of steps.&amp;lt;br clear=&amp;quot;all&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 5: Maintaining Defined Discharges to Downstream Waters (Increase of Low Water / Coverage of Demand)==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb9.png|thumb|Figure 9: Example of a function between shortfalls and scaling factors for a storage&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
* Dependency: &lt;br /&gt;
:In this case, the current discharge is determined by conditions downstream of a storage. At a cross-section of a water resources system, the so-called &#039;&#039;control point&#039;&#039;, where the flow is dependent on the discharge from the upstream storage, a minimum flow is defined. The flow at the control point is composed of the discharge from upstream storages and the lateral inflows between the storages and the control point. If the current flow remains below the set minimum, an additional discharge from upstream storages is necessary. The volume of the additional discharge depends on the difference between the previously defined target flow and the actual flow. Whether the required discharge can be fully provided from the storage depends on the currently available stored volumes in the storage. The lower the level, the less favorable it is to provide additional water. In this context, the increase of low water/coverage of demand behaves completely identical to the drinking or service water withdrawal, with only the triggering factor differing. As mentioned before, a storage-dependent function is scaled by a factor, but this factor is now derived from a comparison between set values and current discharges.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:The determination of the additionally needed discharge is composed of several factors. Firstly, a volumetrically varying shortfall of water results from failing the target discharge. The shortfall of water is then implemented as a scaling factor to the discharge which can be defined by a function. The shortfall of water functions independently, while the scaling factor functions dependently.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb10.png|thumb|Figure 10: Example of a function for increasing low water levels or meeting demand]]&lt;br /&gt;
&lt;br /&gt;
:Secondly, it depends on the actual storage volume, if and how an additional discharge from the storage can be met. A normalized volume-dependent function and the needed discharge lead to a clear determination of the additional discharge volumes. The following [[:Datei:Theorie_Abb10.png||Fig. 10]] shows an example, where the complete provision of an increased target can only be achieved if the filling level of the storage is above a critical limit (25%).&lt;br /&gt;
&lt;br /&gt;
:If more than one storage has an influence on the relevant control point or if, in principle, more than one storage facility is to be used to meet the demand, the required additional discharge is to be divided between the storages in accordance with the corresponding regulations. A distinction must be made between the direct and indirect influences of a storage on the control point. A direct influence is present if a discharge can have a direct effect on the flow conditions at the control point, i.e. the natural flow between the storage &lt;br /&gt;
and the control point can no longer be changed by regulation. If this is not the case, an indirect influence is given.&lt;br /&gt;
&lt;br /&gt;
:All storages with a direct influence on the control point receive a shortfall factor and a volume-dependent, scalable function according to [[:Datei:Theorie_Abb10.png|Figure 10]]. Thus, depending on the shortfall quantities and the storage capacity, the actual discharge can be determined separately for each storage.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 6: Discharge Depending on the storage Inflow==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb11.png|thumb|Figure 11: Direct dependency between storage and control point]]&lt;br /&gt;
:There is a direct dependency between the discharge from the storage and the current inflow to the storage. Similar to the pool-based operating plan, there is also an adaptation to different inflow situations. This is done to prevent depletion or overflowing or to obtain a variable discharge regime downstream. However, long-term inflow fluctuations are difficult to detect with this operating rule, since the observations are only carried out as snapshots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:To determine an inflow-dependent discharge, several components have to be considered. First of all, a relation between the current inflow and discharge must be defined. In addition to the current inflow, the current storage volume is important, because the relation inflow/outflow must not be valid for every filling level. Thus it is likely that the relation is ceded completely or the release quantities are adjusted if the storage level falls below a critical level.&lt;br /&gt;
&lt;br /&gt;
:As this rule can lead to the co-occurrence of relatively small storage volumes and high inflows resulting in high discharge volumes, special attention must be paid to the basic principle of checking the physical limits.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb12.png|thumb|Figure 12: Example of functions for inflow-dependent discharge]]&lt;br /&gt;
:In this case, three functional dependencies play a part. First, there is a direct dependency between the current inflow and the discharge. The form of the function can be arbitrary. It is possible to reproduce only individual sections of the inflow, which corresponds to a partial approximation of the discharge to the duration curve of the inflow.&lt;br /&gt;
&lt;br /&gt;
:Second, the inflow/discharge function can be superposed with the relationship between storage volume and discharge. For reasons of clarity, it is recommended to work with a normalized function. This makes it possible to influence the result of the inflow/discharge function for each storage volume, which is especially convenient for low filling levels.&lt;br /&gt;
&lt;br /&gt;
:Finally, the required discharge has to be checked with regard to the outlet elements&#039; capacity.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb13.png|thumb|left|Figure 13: Results of different inflow-dependent release strategies]]&lt;br /&gt;
&lt;br /&gt;
:The examples below show how the interaction of different functions affects the discharges. The results are compared in the following figures as inflow and discharge duration lines.&lt;br /&gt;
&lt;br /&gt;
:In the case of a linear relation between inflow and discharge and a constant factor for the storage volume, the duration line of the discharge is a curve corresponding to the inflow reduced by a certain percentage. If the storage volume factor remains constant, the duration line can be changed by varying the inflow/discharge relationship. An additional modification of the factor via the storage volume has the advantage of being able to respond to certain filling levels to prevent the storage from emptying or overflowing.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 7: Influence of Discharges Trough System States==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Rule 7, just as rule 6, is a continuation and generalization of the increase of low water as described in rules 5. Just like a discharge deficit at a cross-section or the storage inflow can influence the discharge, any other system state can. In general terms, this means that a discharge from a storage is triggered, increased, or reduced due to a certain system state. Basically, it is irrelevant where the system state occurs. All measurable variables that influence the transport and storage of water can be considered as system states, e.g. the filling of other storages, discharges, flow regime at a cross-section, a snow depth in the catchment area, current precipitation, or current soil moisture.&lt;br /&gt;
&lt;br /&gt;
:As a requirement to apply those dependencies a detection of the system state is necessary. Practically, this means either that a measuring device must be available to determine needed parameters or the required values are calculated using a mathematical model. Parameters are only considered as snap-shots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:If several system states should influence the discharge, a superposition of the parameters according to a corresponding regulation is necessary.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Mathematically, the influence of system states on the discharge can always be undertaken by scaling. Two functions are necessary for this. The first function describes the relationship between storage volume and discharge. The second one controls the dependency between the system state and a scaling factor. The connection is done by multiplying the discharge with the scaling factor.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb13.5.png|thumb|Transition]]&lt;br /&gt;
&lt;br /&gt;
:A simple example is given by a transition from storage A to storage B. &lt;br /&gt;
&lt;br /&gt;
:The decisive discharge is the transition from A to B. The considered system state is the storage volume of B. It seems obvious that a discharge from A to B is only useful if storage A has sufficient provision and storage B has sufficient capacity to hold additional water. This results in the following simple functions:&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb14.png|thumb|left|Figure 14: Example functions for linking a system state to a discharge]]Reservoir B takes 100% of the discharge from A as long as its filling level does not reach 70% of the maximum volume. Furthermore, it is undesirable to receive additional water for flood protection reasons. The scaling factor decreases from 70% filling level to zero. Starting at a filling level above 50% it becomes increasingly easy to transfer water from Reservoir A to reservoir B. The actual transfer, however, only results from the interaction of both functions, taking into account the current filling level of reservoir B and the scaling derived from it.&lt;br /&gt;
&lt;br /&gt;
:For storage A, the definition of the discharge is in m³/s, while the function for storage B receives a unitless scaling factor. In principle, however, it is possible to exchange the meaning of the functions and to use a unitless function for storage A to scale the desired transfer volume for storage B.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 8: Influencing a Discharge with Balances==&lt;br /&gt;
&lt;br /&gt;
 Dependency: [[Datei:Theorie_Abb15.png|thumb|Figure 15 : Example of long-term monthly averages and moving 30 day averages of storage volumes]]&lt;br /&gt;
:This rule is an extension of rule 7. Instead of using a current state parameter, the balance of a system state is linked to discharge. It is important that there are set time boundaries for carrying out the balance. However, it is irrelevant whether the balance is interpreted as a sum or as an average. A function that displays scaling factors depending on the actual balance can then be used to influence discharges.&lt;br /&gt;
&lt;br /&gt;
:In practice, this form of dependency is often found where water rights define maximum withdrawal volumes per time unit. But the application of a balance is also interesting regarding the long-term behaviour of storage filling levels or inflows. For example, a discharge could be reduced to build up provisions if the inflow of the past winter half-year was below a defined expected value. Another application is the comparison between long-term and current moving averages of storage filling levels. If the current values deviate from the long-term values by a certain amount, the discharge can be reduced or increased to compensate.&lt;br /&gt;
&lt;br /&gt;
:If linking a discharge to several balances is desired, it is possible to superpose several balances (see example at the end of this chapter). &lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb16.png|thumb|Figure 16: Example of a rule for standard discharge]]&lt;br /&gt;
:The influence of the balance on the discharge is posed by two functions according to rule 7. In addition to the already necessary storage volume/discharge function, there is a relation between the balance and scaling factor. The scaling factor is taken from the difference between the actual balance and the expected value.&lt;br /&gt;
&lt;br /&gt;
:The method is demonstrated with a simple example of a standard discharge.&lt;br /&gt;
&lt;br /&gt;
:For storage A, long-term monthly mean values of the storage volumes and derived sliding 30-day mean values of the storage filling levels, as well as the rule for the standard discharge, are known.&lt;br /&gt;
&lt;br /&gt;
:If, for example, on May 1st the average value of the storage volume calculated from the last 30 days amounts to 5.6 million m³ and thus, according to [[:Datei:Theorie_Abb15.png|Fig. 15]], it deviates by 30% from the long-term average value of 8 million m³, a scaling factor of 0.5 results (see [[:Datei:Theorie_Abb16.png|Fig. 16]]). With this value, the standard discharge is reduced and delivers only 0.25m³/s at a current storage filling level of 40%, i.e. 50% less than intended.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb17.png|thumb|left|Abbildung 17: Example functions to link a water balance with a discharge]]The relation between the deviation of the balance and the scaling factor indicates that only starting from a difference greater than 20% a change of the standard discharge takes place. In the case of a decrease of more than 20%, the standard discharge is reduced stepwise. If the actual moving 30-day average exceeds the long-term values by more than 20%, the standard discharge is increased continuously.&lt;br /&gt;
&lt;br /&gt;
:In general, there is also the possibility to extend the relation by superposing and combining several water balances.&lt;br /&gt;
&lt;br /&gt;
:The interaction between water balance and discharge function is explained below.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 9: Priorities for Competing Discharges from a Storage==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb18.png|thumb|Figure 18: Example for assigning priorities via the position of functions]]&lt;br /&gt;
:If there are several discharges from a storage, it can occur that it is not possible to carry out all demanded discharges. In such a case, priorities need to be specified, which determine an order in which discharges are to be satisfied. The order of priorities is often a consequence of political decisions and is not subject to physical conditions.&lt;br /&gt;
&lt;br /&gt;
:However, there are some priorities based on physical conditions. An example is turning off a turbine in times of water shortage in favor of securing the water supply. In practice, operating rules often meet this problem by fulfilling demands up to defined storage volumes, but not maintaining discharges below the set storage volume.&lt;br /&gt;
&lt;br /&gt;
:Another way to describe priorities is to reduce a discharge A exactly by an amount, which is resulting from a second discharge B, with the discharge A never being smaller than zero.&lt;br /&gt;
&lt;br /&gt;
* Practical example:&lt;br /&gt;
:The Wiehl dam gives a good example for the practical operating conditions of a dam. The Wiehl dam serves primarily as a drinking water supply and a means for flood protection, and secondarily for energy production. In addition, a minimum flow of 100 l/s has to be guaranteed downstream of the Wiehl dam. The first priority is the drinking water supply. In order to ensure sufficient water quality in the storage, additional discharges used for energy production are stopped when the storage volume falls below 70% of the total volume. As both the minimum discharge and the turbine discharge leave into the Wiehl, it would also be uncalled-for to maintain the minimum discharge if water was simultaneously discharged through the turbine. This results in a reduction of a discharge A (minimum discharge) by the amount of discharge B (turbine) as described above &amp;lt;ref name=&amp;quot;Aggerverband_1999&amp;quot;&amp;gt;&#039;&#039;&#039;Aggerverband&#039;&#039;&#039; (1999): Hydrologische Sicherheit der Genkel- und Aggertalsperre. Gutachten des Fachgebietes Ingenieurhydrologie und Wasserbewirtschaftung, TU Darmstadt&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb19.png|thumb||Figure 19: Example of a relation between two discharges]]&lt;br /&gt;
:Assuming that for each use, following the above rules, a functional dependency between storage content and discharge exists, a ranking of several uses is already given by the position of the function&#039;s nodes.  Then, the respective storage volume from which the target discharge is no longer covered to 100% or even reduced to zero is decisive.&lt;br /&gt;
&lt;br /&gt;
:In the example, the ranking of the uses is clearly visible. First, the turbine is switched off, then the increase of low water refrained from until only the discharge covering the water supply remains.&lt;br /&gt;
&lt;br /&gt;
:In addition, it is possible to directly compare two or more discharges. Such a rule could be:&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;If discharge B &amp;gt; 0 and the storage volume S &amp;lt; X, then reduce discharge A by the amount of discharge B, with discharge  A not being smaller than zero.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:This means that a linear dependency exists between A and B until B is equal to the value of A. If B increases further, A remains constantly zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 11: Water Distribution==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:If there is the need to distribute water within a water resources system, a distribution rule must be defined.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb19.5.png|thumb|Diversion]]&lt;br /&gt;
&lt;br /&gt;
:Two types of diversions can occur:&lt;br /&gt;
:# Diversion that exclusively follows hydraulic laws &lt;br /&gt;
:# Adjustable diversions &lt;br /&gt;
&lt;br /&gt;
:In both cases, relations can always be defined as a function of the inflow. In the second case, these distribution rules represent an operating rule, since they directly influence the transport and storage behavior of water. The number of discharges is basically not limited. The difference to transitions at dams is that in this case no reservoir volume can be used as a reference value.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb20.png|thumb|Figure 20 :Example of assignment functions for multiple sequences]]&lt;br /&gt;
&lt;br /&gt;
* Practical example: &lt;br /&gt;
:The water supply of Windhoek, the capital of Namibia, is provided by three dams. However, the water withdrawal for the drinking water supply is only possible from one dam - the Von Bach Dam. The remaining two reservoirs are connected to the main dam by pipes. However, the volume transferred between Swakopport Dam and Von Bach Dam is not exclusively available for refilling the Von Bach Dam, but also serves to supply the town of Karibib with drinking water.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb21.png|thumb|left|Fig. 21: Example of a threshold concept for a division into two flows]]For the definition of division rules, functions depending on the current inflow are an appropriate representation. Thus, both a hydraulic description and a description serving the management of the storage are possible. For each discharge leaving the diversion structure, a distribution function has to be specified. If the functions are to be variable, scaling is recommended.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb22.png|thumb|Figure 22: Example of a threshold concept with a distribution to serve several users&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
:If the distribution functions cannot be pre-defined, but the discharge volumes rather result later from demand calculations, then a threshold concept is suitable, which in turn can work with scaling factors. The threshold is scaled by a factor and is therefore variable. As long as the inflow is lower than the threshold, the entire inflow is used to satisfy the demand. Only when the current inflow exceeds the threshold, the remaining amount is discharged.&lt;br /&gt;
&lt;br /&gt;
:If a division into more than two discharges is necessary, the threshold concept can be successively applied several times. The order of the discharges determines the priorities of the water distribution.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Literature==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/79/en&amp;diff=12963</id>
		<title>Translations:Betriebsregeltypen/79/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/79/en&amp;diff=12963"/>
		<updated>2021-08-30T10:35:35Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;:&#039;&#039;If discharge B &amp;gt; 0 and the storage volume S &amp;lt; X, then reduce discharge A by the amount of discharge B, with discharge  A not being smaller than zero.&#039;&#039;&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12962</id>
		<title>Betriebsregeltypen/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12962"/>
		<updated>2021-08-30T10:35:21Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=|hoch=Betriebsregelkonzept|nachher=Abstraktion der Betriebsregeln}}&lt;br /&gt;
&lt;br /&gt;
The operating plan of a dam or a storage network is part of the official approval of plans and usually is available as a report or presentation. Its complexity can vary: it ranges from simply defining flood protection areas and setting a report and alarm plan to notify the supervisory authorities in exceptional situations to complex sets of rules concerning functional dependencies that derive discharges from varying system states.&lt;br /&gt;
&lt;br /&gt;
As follows, principles to clarify the variety of possible regulations and reduce them to essential dependencies are presented. A concept is derived to represent most operating rules by a few basic calculation rules. The given selection does not claim to be complete, but it is likely to contain the rules applied in practice.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Basic Principle: Verification of Physical Limits==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb1.png|thumb|Figure 1: Dependency on storage capacity]]&lt;br /&gt;
&lt;br /&gt;
When specifying discharges according to an operating rule, it is assumed that the outlet capacity is sufficient to meet these discharges. Thus, dimensioning the outlet element must consider the operating requirements. In principle, the physically possible discharge, given by the outlet&#039;s characteristic curve at full opening, sets the upper limit value.&lt;br /&gt;
&lt;br /&gt;
If the pressure level or the outlet capacity is sufficient to discharge the desired quantity when fully opened, the discharge can be throttled to the intended level by closing a slide. If the pressure level is insufficient, only the hydraulically possible discharge can be discharged.&lt;br /&gt;
&lt;br /&gt;
*Mathematical abstraction:&lt;br /&gt;
:All outlets obeying an operating rule are functions of the storage&#039;s volume and cannot exceed the outlets&#039; maximum capacity when fully opened. As soon as the capacity of the outlets exceeds the required discharge, it can be adjusted by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
All discharge types from storages mentioned below are subject to this restriction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 1: Definition of a Minimum Output or a Safely Dischargeable Maximum Output==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb2.png|thumb|Figure 2: Example for minimum and maximum discharge as a function of storage capacity]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The specification of a minimum or maximum discharge is based on requirements downstream of a reservoir. The maximal discharge is based on the discharge respective to a critical, downstream cross-section. Consequently, a hydraulic method exists for its determination. In contrast, there is no clear guideline for the minimum discharge. Often, ratios of MNQ or MQ are used. Independent of determining the minimum or maximum discharge, the basic principle to verify outlet elements&#039; physical limits is applied. So, minimum and maximum discharge can only be discharged if the outlet capacity is sufficient at the given pressure level. Since, in reality, it is unlikely that the dimensioning of the outlet elements and the required discharge are conflicting, the reference to the dependence on the storage capacity content is rather theoretical but necessary to derive general laws.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Minimum and maximum discharge are functions of the storage volume and follow the characteristic curve of fully opened outlets at a low filling level. As soon as the outlet elements&#039; capacity is sufficient for the required discharge volume, the discharge can be kept constant by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 2: Maintaining a Flood Protection Area, Possibly Timely Variable Over the Year==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb3.png|thumb|Figure 3: Example of a function to maintain a flood protection area]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The definition of a flood protection area as a minimum requirement only includes the designation of a volume, which has to be kept free for potential floodwater. The dimensioning is based on flood events with certain recurrence intervals. If the water level exceeds the mark of the protection area, an increased discharge to the downstream water of the storage ensures that the area is kept empty. Thus, this rule is reduced to a relation between discharge and storage volume, where the outlet capacity or a defined maximum discharge can serve as an upper limit for keeping the flood protection area empty. If the flood protection area is variable in time over the year, only the discharge of the respective storage volume is increased.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:There is a direct relation between storage capacity and release. If the storage capacity exceeds the mark of the flood protection area, a discharge occurs. If it remains below the mark, the discharge is set to zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 3: Direct Withdrawals from a storage for Drinking or Service Water ==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb4.png|thumb|Figure 4: Example of a function for drinking or raw water withdrawal]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Primarily, the current demand determines the volume of withdrawals from the storage, but it is also subject to temporal variations. The upper limits for withdrawals are generally set by water rights or defined maximum withdrawal volumes, which refer to selected periods such as a day, a month, a quarter, or a year. Initially, one only considers the current demand communicated by water suppliers, which constitutes a claim towards the storage. There is no connection to the actual storage and the respective storage volume.&lt;br /&gt;
:Whether the demand can be pleased by withdrawing water from the storage is determined by the actual storage volumes. To connect the water demand to the actual storage volumes, the structural implementation of withdrawal elements and means of anticipatory management are taken into account. For example, if particularly low storage volumes are reached, it is advisable to throttle withdrawals in advance to avoid the storage running empty and then completely failing at covering the demand during prolonged periods of low water &amp;lt;ref name=&amp;quot;Schultz_1989&amp;quot;&amp;gt;&#039;&#039;&#039;Schultz, G.A.&#039;&#039;&#039; (1989): Entwicklung von Betriebsregeln für die Wupper-Talsperre in Niedrig- und Hochwasserzeiten. Wasserwirtschaft 79 (7/8) S. 340-343&amp;lt;/ref&amp;gt;. Hence, there is usually space reserved in a dam specifically used for drinking water supply. Its use is handled separately in respective operating plans.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:If the demand is exactly known and unchangeable, a direct relation between withdrawal and storage volume can be defined. However, the demand is subject to certain variations. For this reason, it is recommended to normalize the relationship between withdrawals and storage volume, where the current demand serves as a scaling factor. If the storage volume falls below a defined limit value, only a certain percentage of the current demand is satisfied. The limit value, as well as the form of the function, can be variable in time.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 4: Standard Discharge to Downstream Water==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb5.png|thumb|Figure 5: Pool-based operating plan in a two-dimensional representation]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The normal discharge to the downstream water should provide a discharge compensation for seasonal differences in the inflow. If a minimum discharge is required, it will be included in the normal discharge. A pool-based operating plan is used to describe the normal discharge. It divides the storage capacity into different areas and assigns a discharge to each pool-based operation. When determining the pool-based operating plan, the long-term discharge and other withdrawals from the reservoir for other purposes play a decisive role. A reservoir should collect water in periods of high inflow but still not overflow to have sufficient reserves in periods of low inflow. The coupling of the releases to the storage pool-based operation is a function of the storage volume. Since the system is supposed to react to variations of inflow during the year, the relationship between storage volume and discharge is usually variable over time.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb6.png|thumb|Figure 6: Comparison of a pool-based operating plan in a two- and three-dimensional representation]] Like for the previous rules, the output depends on the storage volume. Usually, a pool-based operating plan is displayed in two-dimensional diagrams. The X-axis shows the time of one year, while the Y-axis shows the storage capacity. Pool-based operations are depicted as lines of equal outputs.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb7.png|thumb|Figure 7: Pool-based operating plan with linear interpolation between successive time reference points]]This view is practical but not yet complete: A three-dimensional representation of a simple pool-based operating plan makes this clear. On the X-axis is the time, on the Y-axis the storage capacity is plotted, while the Z-axis shows the output directed upwards.&lt;br /&gt;
&lt;br /&gt;
:The 3D image viewed from above gives the two-dimensional shape. Instead of taking constant blocks for the individual time horizons, a linear connection is also used often.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb8.png|thumb|Figure 8: Pool-based operating plan with two types of interpretation (selected month of May)]]For the individual periods - here months - different functional dependencies between storage capacity and outflow are considered. If the storage volume/discharge relation is also considered for a selected point in time, there are two possibilities to connect the discharge nodes. On the one hand, there is the possibility of linear interpolation, and on the other hand, a step function is possible.&lt;br /&gt;
&lt;br /&gt;
:In two-dimensional space, this information is not visible and must be specified separately. However, there is usually the convention to assume that the output between two nodes is constant, i.e. to interpret the pool-based operating plan as shown above in the form of steps.&amp;lt;br clear=&amp;quot;all&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 5: Maintaining Defined Discharges to Downstream Waters (Increase of Low Water / Coverage of Demand)==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb9.png|thumb|Figure 9: Example of a function between shortfalls and scaling factors for a storage&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
* Dependency: &lt;br /&gt;
:In this case, the current discharge is determined by conditions downstream of a storage. At a cross-section of a water resources system, the so-called &#039;&#039;control point&#039;&#039;, where the flow is dependent on the discharge from the upstream storage, a minimum flow is defined. The flow at the control point is composed of the discharge from upstream storages and the lateral inflows between the storages and the control point. If the current flow remains below the set minimum, an additional discharge from upstream storages is necessary. The volume of the additional discharge depends on the difference between the previously defined target flow and the actual flow. Whether the required discharge can be fully provided from the storage depends on the currently available stored volumes in the storage. The lower the level, the less favorable it is to provide additional water. In this context, the increase of low water/coverage of demand behaves completely identical to the drinking or service water withdrawal, with only the triggering factor differing. As mentioned before, a storage-dependent function is scaled by a factor, but this factor is now derived from a comparison between set values and current discharges.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:The determination of the additionally needed discharge is composed of several factors. Firstly, a volumetrically varying shortfall of water results from failing the target discharge. The shortfall of water is then implemented as a scaling factor to the discharge which can be defined by a function. The shortfall of water functions independently, while the scaling factor functions dependently.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb10.png|thumb|Figure 10: Example of a function for increasing low water levels or meeting demand]]&lt;br /&gt;
&lt;br /&gt;
:Secondly, it depends on the actual storage volume, if and how an additional discharge from the storage can be met. A normalized volume-dependent function and the needed discharge lead to a clear determination of the additional discharge volumes. The following [[:Datei:Theorie_Abb10.png||Fig. 10]] shows an example, where the complete provision of an increased target can only be achieved if the filling level of the storage is above a critical limit (25%).&lt;br /&gt;
&lt;br /&gt;
:If more than one storage has an influence on the relevant control point or if, in principle, more than one storage facility is to be used to meet the demand, the required additional discharge is to be divided between the storages in accordance with the corresponding regulations. A distinction must be made between the direct and indirect influences of a storage on the control point. A direct influence is present if a discharge can have a direct effect on the flow conditions at the control point, i.e. the natural flow between the storage &lt;br /&gt;
and the control point can no longer be changed by regulation. If this is not the case, an indirect influence is given.&lt;br /&gt;
&lt;br /&gt;
:All storages with a direct influence on the control point receive a shortfall factor and a volume-dependent, scalable function according to [[:Datei:Theorie_Abb10.png|Figure 10]]. Thus, depending on the shortfall quantities and the storage capacity, the actual discharge can be determined separately for each storage.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 6: Discharge Depending on the storage Inflow==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb11.png|thumb|Figure 11: Direct dependency between storage and control point]]&lt;br /&gt;
:There is a direct dependency between the discharge from the storage and the current inflow to the storage. Similar to the pool-based operating plan, there is also an adaptation to different inflow situations. This is done to prevent depletion or overflowing or to obtain a variable discharge regime downstream. However, long-term inflow fluctuations are difficult to detect with this operating rule, since the observations are only carried out as snapshots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:To determine an inflow-dependent discharge, several components have to be considered. First of all, a relation between the current inflow and discharge must be defined. In addition to the current inflow, the current storage volume is important, because the relation inflow/outflow must not be valid for every filling level. Thus it is likely that the relation is ceded completely or the release quantities are adjusted if the storage level falls below a critical level.&lt;br /&gt;
&lt;br /&gt;
:As this rule can lead to the co-occurrence of relatively small storage volumes and high inflows resulting in high discharge volumes, special attention must be paid to the basic principle of checking the physical limits.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb12.png|thumb|Figure 12: Example of functions for inflow-dependent discharge]]&lt;br /&gt;
:In this case, three functional dependencies play a part. First, there is a direct dependency between the current inflow and the discharge. The form of the function can be arbitrary. It is possible to reproduce only individual sections of the inflow, which corresponds to a partial approximation of the discharge to the duration curve of the inflow.&lt;br /&gt;
&lt;br /&gt;
:Second, the inflow/discharge function can be superposed with the relationship between storage volume and discharge. For reasons of clarity, it is recommended to work with a normalized function. This makes it possible to influence the result of the inflow/discharge function for each storage volume, which is especially convenient for low filling levels.&lt;br /&gt;
&lt;br /&gt;
:Finally, the required discharge has to be checked with regard to the outlet elements&#039; capacity.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb13.png|thumb|left|Figure 13: Results of different inflow-dependent release strategies]]&lt;br /&gt;
&lt;br /&gt;
:The examples below show how the interaction of different functions affects the discharges. The results are compared in the following figures as inflow and discharge duration lines.&lt;br /&gt;
&lt;br /&gt;
:In the case of a linear relation between inflow and discharge and a constant factor for the storage volume, the duration line of the discharge is a curve corresponding to the inflow reduced by a certain percentage. If the storage volume factor remains constant, the duration line can be changed by varying the inflow/discharge relationship. An additional modification of the factor via the storage volume has the advantage of being able to respond to certain filling levels to prevent the storage from emptying or overflowing.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 7: Influence of Discharges Trough System States==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Rule 7, just as rule 6, is a continuation and generalization of the increase of low water as described in rules 5. Just like a discharge deficit at a cross-section or the storage inflow can influence the discharge, any other system state can. In general terms, this means that a discharge from a storage is triggered, increased, or reduced due to a certain system state. Basically, it is irrelevant where the system state occurs. All measurable variables that influence the transport and storage of water can be considered as system states, e.g. the filling of other storages, discharges, flow regime at a cross-section, a snow depth in the catchment area, current precipitation, or current soil moisture.&lt;br /&gt;
&lt;br /&gt;
:As a requirement to apply those dependencies a detection of the system state is necessary. Practically, this means either that a measuring device must be available to determine needed parameters or the required values are calculated using a mathematical model. Parameters are only considered as snap-shots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:If several system states should influence the discharge, a superposition of the parameters according to a corresponding regulation is necessary.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Mathematically, the influence of system states on the discharge can always be undertaken by scaling. Two functions are necessary for this. The first function describes the relationship between storage volume and discharge. The second one controls the dependency between the system state and a scaling factor. The connection is done by multiplying the discharge with the scaling factor.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb13.5.png|thumb|Transition]]&lt;br /&gt;
&lt;br /&gt;
:A simple example is given by a transition from storage A to storage B. &lt;br /&gt;
&lt;br /&gt;
:The decisive discharge is the transition from A to B. The considered system state is the storage volume of B. It seems obvious that a discharge from A to B is only useful if storage A has sufficient provision and storage B has sufficient capacity to hold additional water. This results in the following simple functions:&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb14.png|thumb|left|Figure 14: Example functions for linking a system state to a discharge]]Reservoir B takes 100% of the discharge from A as long as its filling level does not reach 70% of the maximum volume. Furthermore, it is undesirable to receive additional water for flood protection reasons. The scaling factor decreases from 70% filling level to zero. Starting at a filling level above 50% it becomes increasingly easy to transfer water from Reservoir A to reservoir B. The actual transfer, however, only results from the interaction of both functions, taking into account the current filling level of reservoir B and the scaling derived from it.&lt;br /&gt;
&lt;br /&gt;
:For storage A, the definition of the discharge is in m³/s, while the function for storage B receives a unitless scaling factor. In principle, however, it is possible to exchange the meaning of the functions and to use a unitless function for storage A to scale the desired transfer volume for storage B.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 8: Influencing a Discharge with Balances==&lt;br /&gt;
&lt;br /&gt;
 Dependency: [[Datei:Theorie_Abb15.png|thumb|Figure 15 : Example of long-term monthly averages and moving 30 day averages of storage volumes]]&lt;br /&gt;
:This rule is an extension of rule 7. Instead of using a current state parameter, the balance of a system state is linked to discharge. It is important that there are set time boundaries for carrying out the balance. However, it is irrelevant whether the balance is interpreted as a sum or as an average. A function that displays scaling factors depending on the actual balance can then be used to influence discharges.&lt;br /&gt;
&lt;br /&gt;
:In practice, this form of dependency is often found where water rights define maximum withdrawal volumes per time unit. But the application of a balance is also interesting regarding the long-term behaviour of storage filling levels or inflows. For example, a discharge could be reduced to build up provisions if the inflow of the past winter half-year was below a defined expected value. Another application is the comparison between long-term and current moving averages of storage filling levels. If the current values deviate from the long-term values by a certain amount, the discharge can be reduced or increased to compensate.&lt;br /&gt;
&lt;br /&gt;
:If linking a discharge to several balances is desired, it is possible to superpose several balances (see example at the end of this chapter). &lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb16.png|thumb|Figure 16: Example of a rule for standard discharge]]&lt;br /&gt;
:The influence of the balance on the discharge is posed by two functions according to rule 7. In addition to the already necessary storage volume/discharge function, there is a relation between the balance and scaling factor. The scaling factor is taken from the difference between the actual balance and the expected value.&lt;br /&gt;
&lt;br /&gt;
:The method is demonstrated with a simple example of a standard discharge.&lt;br /&gt;
&lt;br /&gt;
:For storage A, long-term monthly mean values of the storage volumes and derived sliding 30-day mean values of the storage filling levels, as well as the rule for the standard discharge, are known.&lt;br /&gt;
&lt;br /&gt;
:If, for example, on May 1st the average value of the storage volume calculated from the last 30 days amounts to 5.6 million m³ and thus, according to [[:Datei:Theorie_Abb15.png|Fig. 15]], it deviates by 30% from the long-term average value of 8 million m³, a scaling factor of 0.5 results (see [[:Datei:Theorie_Abb16.png|Fig. 16]]). With this value, the standard discharge is reduced and delivers only 0.25m³/s at a current storage filling level of 40%, i.e. 50% less than intended.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb17.png|thumb|left|Abbildung 17: Example functions to link a water balance with a discharge]]The relation between the deviation of the balance and the scaling factor indicates that only starting from a difference greater than 20% a change of the standard discharge takes place. In the case of a decrease of more than 20%, the standard discharge is reduced stepwise. If the actual moving 30-day average exceeds the long-term values by more than 20%, the standard discharge is increased continuously.&lt;br /&gt;
&lt;br /&gt;
:In general, there is also the possibility to extend the relation by superposing and combining several water balances.&lt;br /&gt;
&lt;br /&gt;
:The interaction between water balance and discharge function is explained below.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 9: Priorities for Competing Discharges from a Storage==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb18.png|thumb|Figure 18: Example for assigning priorities via the position of functions]]&lt;br /&gt;
:If there are several discharges from a storage, it can occur that it is not possible to carry out all demanded discharges. In such a case, priorities need to be specified, which determine an order in which discharges are to be satisfied. The order of priorities is often a consequence of political decisions and is not subject to physical conditions.&lt;br /&gt;
&lt;br /&gt;
:However, there are some priorities based on physical conditions. An example is turning off a turbine in times of water shortage in favor of securing the water supply. In practice, operating rules often meet this problem by fulfilling demands up to defined storage volumes, but not maintaining discharges below the set storage volume.&lt;br /&gt;
&lt;br /&gt;
:Another way to describe priorities is to reduce a discharge A exactly by an amount, which is resulting from a second discharge B, with the discharge A never being smaller than zero.&lt;br /&gt;
&lt;br /&gt;
* Practical example:&lt;br /&gt;
:The Wiehl dam gives a good example for the practical operating conditions of a dam. The Wiehl dam serves primarily as a drinking water supply and a means for flood protection, and secondarily for energy production. In addition, a minimum flow of 100 l/s has to be guaranteed downstream of the Wiehl dam. The first priority is the drinking water supply. In order to ensure sufficient water quality in the storage, additional discharges used for energy production are stopped when the storage volume falls below 70% of the total volume. As both the minimum discharge and the turbine discharge leave into the Wiehl, it would also be uncalled-for to maintain the minimum discharge if water was simultaneously discharged through the turbine. This results in a reduction of a discharge A (minimum discharge) by the amount of discharge B (turbine) as described above &amp;lt;ref name=&amp;quot;Aggerverband_1999&amp;quot;&amp;gt;&#039;&#039;&#039;Aggerverband&#039;&#039;&#039; (1999): Hydrologische Sicherheit der Genkel- und Aggertalsperre. Gutachten des Fachgebietes Ingenieurhydrologie und Wasserbewirtschaftung, TU Darmstadt&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb19.png|thumb||Figure 19: Example of a relation between two discharges]]&lt;br /&gt;
:Assuming that for each use, following the above rules, a functional dependency between storage content and discharge exists, a ranking of several uses is already given by the position of the function&#039;s nodes.  Then, the respective storage volume from which the target discharge is no longer covered to 100% or even reduced to zero is decisive.&lt;br /&gt;
&lt;br /&gt;
:In the example, the ranking of the uses is clearly visible. First, the turbine is switched off, then the increase of low water refrained from until only the discharge covering the water supply remains.&lt;br /&gt;
&lt;br /&gt;
:In addition, it is possible to directly compare two or more discharges. Such a rule could be:&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;If discharge B &amp;gt; 0 and the reservoir volume S &amp;lt; X, then reduce discharge A by the amount of discharge B, with discharge  A not being smaller than zero.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:This means that a linear dependency exists between A and B until B is equal to the value of A. If B increases further, A remains constantly zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 11: Water Distribution==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:If there is the need to distribute water within a water resources system, a distribution rule must be defined.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb19.5.png|thumb|Diversion]]&lt;br /&gt;
&lt;br /&gt;
:Two types of diversions can occur:&lt;br /&gt;
:# Diversion that exclusively follows hydraulic laws &lt;br /&gt;
:# Adjustable diversions &lt;br /&gt;
&lt;br /&gt;
:In both cases, relations can always be defined as a function of the inflow. In the second case, these distribution rules represent an operating rule, since they directly influence the transport and storage behavior of water. The number of discharges is basically not limited. The difference to transitions at dams is that in this case no reservoir volume can be used as a reference value.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb20.png|thumb|Figure 20 :Example of assignment functions for multiple sequences]]&lt;br /&gt;
&lt;br /&gt;
* Practical example: &lt;br /&gt;
:The water supply of Windhoek, the capital of Namibia, is provided by three dams. However, the water withdrawal for the drinking water supply is only possible from one dam - the Von Bach Dam. The remaining two reservoirs are connected to the main dam by pipes. However, the volume transferred between Swakopport Dam and Von Bach Dam is not exclusively available for refilling the Von Bach Dam, but also serves to supply the town of Karibib with drinking water.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb21.png|thumb|left|Fig. 21: Example of a threshold concept for a division into two flows]]For the definition of division rules, functions depending on the current inflow are an appropriate representation. Thus, both a hydraulic description and a description serving the management of the storage are possible. For each discharge leaving the diversion structure, a distribution function has to be specified. If the functions are to be variable, scaling is recommended.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb22.png|thumb|Figure 22: Example of a threshold concept with a distribution to serve several users&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
:If the distribution functions cannot be pre-defined, but the discharge volumes rather result later from demand calculations, then a threshold concept is suitable, which in turn can work with scaling factors. The threshold is scaled by a factor and is therefore variable. As long as the inflow is lower than the threshold, the entire inflow is used to satisfy the demand. Only when the current inflow exceeds the threshold, the remaining amount is discharged.&lt;br /&gt;
&lt;br /&gt;
:If a division into more than two discharges is necessary, the threshold concept can be successively applied several times. The order of the discharges determines the priorities of the water distribution.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Literature==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/76/en&amp;diff=12961</id>
		<title>Translations:Betriebsregeltypen/76/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/76/en&amp;diff=12961"/>
		<updated>2021-08-30T10:35:21Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* Mathematical abstraction: [[Datei:Theorie_Abb19.png|thumb||Figure 19: Example of a relation between two discharges]]&lt;br /&gt;
:Assuming that for each use, following the above rules, a functional dependency between storage content and discharge exists, a ranking of several uses is already given by the position of the function&#039;s nodes.  Then, the respective storage volume from which the target discharge is no longer covered to 100% or even reduced to zero is decisive.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12960</id>
		<title>Betriebsregeltypen/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12960"/>
		<updated>2021-08-30T10:35:04Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=|hoch=Betriebsregelkonzept|nachher=Abstraktion der Betriebsregeln}}&lt;br /&gt;
&lt;br /&gt;
The operating plan of a dam or a storage network is part of the official approval of plans and usually is available as a report or presentation. Its complexity can vary: it ranges from simply defining flood protection areas and setting a report and alarm plan to notify the supervisory authorities in exceptional situations to complex sets of rules concerning functional dependencies that derive discharges from varying system states.&lt;br /&gt;
&lt;br /&gt;
As follows, principles to clarify the variety of possible regulations and reduce them to essential dependencies are presented. A concept is derived to represent most operating rules by a few basic calculation rules. The given selection does not claim to be complete, but it is likely to contain the rules applied in practice.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Basic Principle: Verification of Physical Limits==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb1.png|thumb|Figure 1: Dependency on storage capacity]]&lt;br /&gt;
&lt;br /&gt;
When specifying discharges according to an operating rule, it is assumed that the outlet capacity is sufficient to meet these discharges. Thus, dimensioning the outlet element must consider the operating requirements. In principle, the physically possible discharge, given by the outlet&#039;s characteristic curve at full opening, sets the upper limit value.&lt;br /&gt;
&lt;br /&gt;
If the pressure level or the outlet capacity is sufficient to discharge the desired quantity when fully opened, the discharge can be throttled to the intended level by closing a slide. If the pressure level is insufficient, only the hydraulically possible discharge can be discharged.&lt;br /&gt;
&lt;br /&gt;
*Mathematical abstraction:&lt;br /&gt;
:All outlets obeying an operating rule are functions of the storage&#039;s volume and cannot exceed the outlets&#039; maximum capacity when fully opened. As soon as the capacity of the outlets exceeds the required discharge, it can be adjusted by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
All discharge types from storages mentioned below are subject to this restriction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 1: Definition of a Minimum Output or a Safely Dischargeable Maximum Output==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb2.png|thumb|Figure 2: Example for minimum and maximum discharge as a function of storage capacity]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The specification of a minimum or maximum discharge is based on requirements downstream of a reservoir. The maximal discharge is based on the discharge respective to a critical, downstream cross-section. Consequently, a hydraulic method exists for its determination. In contrast, there is no clear guideline for the minimum discharge. Often, ratios of MNQ or MQ are used. Independent of determining the minimum or maximum discharge, the basic principle to verify outlet elements&#039; physical limits is applied. So, minimum and maximum discharge can only be discharged if the outlet capacity is sufficient at the given pressure level. Since, in reality, it is unlikely that the dimensioning of the outlet elements and the required discharge are conflicting, the reference to the dependence on the storage capacity content is rather theoretical but necessary to derive general laws.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Minimum and maximum discharge are functions of the storage volume and follow the characteristic curve of fully opened outlets at a low filling level. As soon as the outlet elements&#039; capacity is sufficient for the required discharge volume, the discharge can be kept constant by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 2: Maintaining a Flood Protection Area, Possibly Timely Variable Over the Year==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb3.png|thumb|Figure 3: Example of a function to maintain a flood protection area]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The definition of a flood protection area as a minimum requirement only includes the designation of a volume, which has to be kept free for potential floodwater. The dimensioning is based on flood events with certain recurrence intervals. If the water level exceeds the mark of the protection area, an increased discharge to the downstream water of the storage ensures that the area is kept empty. Thus, this rule is reduced to a relation between discharge and storage volume, where the outlet capacity or a defined maximum discharge can serve as an upper limit for keeping the flood protection area empty. If the flood protection area is variable in time over the year, only the discharge of the respective storage volume is increased.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:There is a direct relation between storage capacity and release. If the storage capacity exceeds the mark of the flood protection area, a discharge occurs. If it remains below the mark, the discharge is set to zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 3: Direct Withdrawals from a storage for Drinking or Service Water ==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb4.png|thumb|Figure 4: Example of a function for drinking or raw water withdrawal]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Primarily, the current demand determines the volume of withdrawals from the storage, but it is also subject to temporal variations. The upper limits for withdrawals are generally set by water rights or defined maximum withdrawal volumes, which refer to selected periods such as a day, a month, a quarter, or a year. Initially, one only considers the current demand communicated by water suppliers, which constitutes a claim towards the storage. There is no connection to the actual storage and the respective storage volume.&lt;br /&gt;
:Whether the demand can be pleased by withdrawing water from the storage is determined by the actual storage volumes. To connect the water demand to the actual storage volumes, the structural implementation of withdrawal elements and means of anticipatory management are taken into account. For example, if particularly low storage volumes are reached, it is advisable to throttle withdrawals in advance to avoid the storage running empty and then completely failing at covering the demand during prolonged periods of low water &amp;lt;ref name=&amp;quot;Schultz_1989&amp;quot;&amp;gt;&#039;&#039;&#039;Schultz, G.A.&#039;&#039;&#039; (1989): Entwicklung von Betriebsregeln für die Wupper-Talsperre in Niedrig- und Hochwasserzeiten. Wasserwirtschaft 79 (7/8) S. 340-343&amp;lt;/ref&amp;gt;. Hence, there is usually space reserved in a dam specifically used for drinking water supply. Its use is handled separately in respective operating plans.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:If the demand is exactly known and unchangeable, a direct relation between withdrawal and storage volume can be defined. However, the demand is subject to certain variations. For this reason, it is recommended to normalize the relationship between withdrawals and storage volume, where the current demand serves as a scaling factor. If the storage volume falls below a defined limit value, only a certain percentage of the current demand is satisfied. The limit value, as well as the form of the function, can be variable in time.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 4: Standard Discharge to Downstream Water==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb5.png|thumb|Figure 5: Pool-based operating plan in a two-dimensional representation]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The normal discharge to the downstream water should provide a discharge compensation for seasonal differences in the inflow. If a minimum discharge is required, it will be included in the normal discharge. A pool-based operating plan is used to describe the normal discharge. It divides the storage capacity into different areas and assigns a discharge to each pool-based operation. When determining the pool-based operating plan, the long-term discharge and other withdrawals from the reservoir for other purposes play a decisive role. A reservoir should collect water in periods of high inflow but still not overflow to have sufficient reserves in periods of low inflow. The coupling of the releases to the storage pool-based operation is a function of the storage volume. Since the system is supposed to react to variations of inflow during the year, the relationship between storage volume and discharge is usually variable over time.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb6.png|thumb|Figure 6: Comparison of a pool-based operating plan in a two- and three-dimensional representation]] Like for the previous rules, the output depends on the storage volume. Usually, a pool-based operating plan is displayed in two-dimensional diagrams. The X-axis shows the time of one year, while the Y-axis shows the storage capacity. Pool-based operations are depicted as lines of equal outputs.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb7.png|thumb|Figure 7: Pool-based operating plan with linear interpolation between successive time reference points]]This view is practical but not yet complete: A three-dimensional representation of a simple pool-based operating plan makes this clear. On the X-axis is the time, on the Y-axis the storage capacity is plotted, while the Z-axis shows the output directed upwards.&lt;br /&gt;
&lt;br /&gt;
:The 3D image viewed from above gives the two-dimensional shape. Instead of taking constant blocks for the individual time horizons, a linear connection is also used often.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb8.png|thumb|Figure 8: Pool-based operating plan with two types of interpretation (selected month of May)]]For the individual periods - here months - different functional dependencies between storage capacity and outflow are considered. If the storage volume/discharge relation is also considered for a selected point in time, there are two possibilities to connect the discharge nodes. On the one hand, there is the possibility of linear interpolation, and on the other hand, a step function is possible.&lt;br /&gt;
&lt;br /&gt;
:In two-dimensional space, this information is not visible and must be specified separately. However, there is usually the convention to assume that the output between two nodes is constant, i.e. to interpret the pool-based operating plan as shown above in the form of steps.&amp;lt;br clear=&amp;quot;all&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 5: Maintaining Defined Discharges to Downstream Waters (Increase of Low Water / Coverage of Demand)==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb9.png|thumb|Figure 9: Example of a function between shortfalls and scaling factors for a storage&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
* Dependency: &lt;br /&gt;
:In this case, the current discharge is determined by conditions downstream of a storage. At a cross-section of a water resources system, the so-called &#039;&#039;control point&#039;&#039;, where the flow is dependent on the discharge from the upstream storage, a minimum flow is defined. The flow at the control point is composed of the discharge from upstream storages and the lateral inflows between the storages and the control point. If the current flow remains below the set minimum, an additional discharge from upstream storages is necessary. The volume of the additional discharge depends on the difference between the previously defined target flow and the actual flow. Whether the required discharge can be fully provided from the storage depends on the currently available stored volumes in the storage. The lower the level, the less favorable it is to provide additional water. In this context, the increase of low water/coverage of demand behaves completely identical to the drinking or service water withdrawal, with only the triggering factor differing. As mentioned before, a storage-dependent function is scaled by a factor, but this factor is now derived from a comparison between set values and current discharges.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:The determination of the additionally needed discharge is composed of several factors. Firstly, a volumetrically varying shortfall of water results from failing the target discharge. The shortfall of water is then implemented as a scaling factor to the discharge which can be defined by a function. The shortfall of water functions independently, while the scaling factor functions dependently.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb10.png|thumb|Figure 10: Example of a function for increasing low water levels or meeting demand]]&lt;br /&gt;
&lt;br /&gt;
:Secondly, it depends on the actual storage volume, if and how an additional discharge from the storage can be met. A normalized volume-dependent function and the needed discharge lead to a clear determination of the additional discharge volumes. The following [[:Datei:Theorie_Abb10.png||Fig. 10]] shows an example, where the complete provision of an increased target can only be achieved if the filling level of the storage is above a critical limit (25%).&lt;br /&gt;
&lt;br /&gt;
:If more than one storage has an influence on the relevant control point or if, in principle, more than one storage facility is to be used to meet the demand, the required additional discharge is to be divided between the storages in accordance with the corresponding regulations. A distinction must be made between the direct and indirect influences of a storage on the control point. A direct influence is present if a discharge can have a direct effect on the flow conditions at the control point, i.e. the natural flow between the storage &lt;br /&gt;
and the control point can no longer be changed by regulation. If this is not the case, an indirect influence is given.&lt;br /&gt;
&lt;br /&gt;
:All storages with a direct influence on the control point receive a shortfall factor and a volume-dependent, scalable function according to [[:Datei:Theorie_Abb10.png|Figure 10]]. Thus, depending on the shortfall quantities and the storage capacity, the actual discharge can be determined separately for each storage.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 6: Discharge Depending on the storage Inflow==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb11.png|thumb|Figure 11: Direct dependency between storage and control point]]&lt;br /&gt;
:There is a direct dependency between the discharge from the storage and the current inflow to the storage. Similar to the pool-based operating plan, there is also an adaptation to different inflow situations. This is done to prevent depletion or overflowing or to obtain a variable discharge regime downstream. However, long-term inflow fluctuations are difficult to detect with this operating rule, since the observations are only carried out as snapshots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:To determine an inflow-dependent discharge, several components have to be considered. First of all, a relation between the current inflow and discharge must be defined. In addition to the current inflow, the current storage volume is important, because the relation inflow/outflow must not be valid for every filling level. Thus it is likely that the relation is ceded completely or the release quantities are adjusted if the storage level falls below a critical level.&lt;br /&gt;
&lt;br /&gt;
:As this rule can lead to the co-occurrence of relatively small storage volumes and high inflows resulting in high discharge volumes, special attention must be paid to the basic principle of checking the physical limits.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb12.png|thumb|Figure 12: Example of functions for inflow-dependent discharge]]&lt;br /&gt;
:In this case, three functional dependencies play a part. First, there is a direct dependency between the current inflow and the discharge. The form of the function can be arbitrary. It is possible to reproduce only individual sections of the inflow, which corresponds to a partial approximation of the discharge to the duration curve of the inflow.&lt;br /&gt;
&lt;br /&gt;
:Second, the inflow/discharge function can be superposed with the relationship between storage volume and discharge. For reasons of clarity, it is recommended to work with a normalized function. This makes it possible to influence the result of the inflow/discharge function for each storage volume, which is especially convenient for low filling levels.&lt;br /&gt;
&lt;br /&gt;
:Finally, the required discharge has to be checked with regard to the outlet elements&#039; capacity.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb13.png|thumb|left|Figure 13: Results of different inflow-dependent release strategies]]&lt;br /&gt;
&lt;br /&gt;
:The examples below show how the interaction of different functions affects the discharges. The results are compared in the following figures as inflow and discharge duration lines.&lt;br /&gt;
&lt;br /&gt;
:In the case of a linear relation between inflow and discharge and a constant factor for the storage volume, the duration line of the discharge is a curve corresponding to the inflow reduced by a certain percentage. If the storage volume factor remains constant, the duration line can be changed by varying the inflow/discharge relationship. An additional modification of the factor via the storage volume has the advantage of being able to respond to certain filling levels to prevent the storage from emptying or overflowing.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 7: Influence of Discharges Trough System States==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Rule 7, just as rule 6, is a continuation and generalization of the increase of low water as described in rules 5. Just like a discharge deficit at a cross-section or the storage inflow can influence the discharge, any other system state can. In general terms, this means that a discharge from a storage is triggered, increased, or reduced due to a certain system state. Basically, it is irrelevant where the system state occurs. All measurable variables that influence the transport and storage of water can be considered as system states, e.g. the filling of other storages, discharges, flow regime at a cross-section, a snow depth in the catchment area, current precipitation, or current soil moisture.&lt;br /&gt;
&lt;br /&gt;
:As a requirement to apply those dependencies a detection of the system state is necessary. Practically, this means either that a measuring device must be available to determine needed parameters or the required values are calculated using a mathematical model. Parameters are only considered as snap-shots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:If several system states should influence the discharge, a superposition of the parameters according to a corresponding regulation is necessary.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Mathematically, the influence of system states on the discharge can always be undertaken by scaling. Two functions are necessary for this. The first function describes the relationship between storage volume and discharge. The second one controls the dependency between the system state and a scaling factor. The connection is done by multiplying the discharge with the scaling factor.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb13.5.png|thumb|Transition]]&lt;br /&gt;
&lt;br /&gt;
:A simple example is given by a transition from storage A to storage B. &lt;br /&gt;
&lt;br /&gt;
:The decisive discharge is the transition from A to B. The considered system state is the storage volume of B. It seems obvious that a discharge from A to B is only useful if storage A has sufficient provision and storage B has sufficient capacity to hold additional water. This results in the following simple functions:&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb14.png|thumb|left|Figure 14: Example functions for linking a system state to a discharge]]Reservoir B takes 100% of the discharge from A as long as its filling level does not reach 70% of the maximum volume. Furthermore, it is undesirable to receive additional water for flood protection reasons. The scaling factor decreases from 70% filling level to zero. Starting at a filling level above 50% it becomes increasingly easy to transfer water from Reservoir A to reservoir B. The actual transfer, however, only results from the interaction of both functions, taking into account the current filling level of reservoir B and the scaling derived from it.&lt;br /&gt;
&lt;br /&gt;
:For storage A, the definition of the discharge is in m³/s, while the function for storage B receives a unitless scaling factor. In principle, however, it is possible to exchange the meaning of the functions and to use a unitless function for storage A to scale the desired transfer volume for storage B.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 8: Influencing a Discharge with Balances==&lt;br /&gt;
&lt;br /&gt;
 Dependency: [[Datei:Theorie_Abb15.png|thumb|Figure 15 : Example of long-term monthly averages and moving 30 day averages of storage volumes]]&lt;br /&gt;
:This rule is an extension of rule 7. Instead of using a current state parameter, the balance of a system state is linked to discharge. It is important that there are set time boundaries for carrying out the balance. However, it is irrelevant whether the balance is interpreted as a sum or as an average. A function that displays scaling factors depending on the actual balance can then be used to influence discharges.&lt;br /&gt;
&lt;br /&gt;
:In practice, this form of dependency is often found where water rights define maximum withdrawal volumes per time unit. But the application of a balance is also interesting regarding the long-term behaviour of storage filling levels or inflows. For example, a discharge could be reduced to build up provisions if the inflow of the past winter half-year was below a defined expected value. Another application is the comparison between long-term and current moving averages of storage filling levels. If the current values deviate from the long-term values by a certain amount, the discharge can be reduced or increased to compensate.&lt;br /&gt;
&lt;br /&gt;
:If linking a discharge to several balances is desired, it is possible to superpose several balances (see example at the end of this chapter). &lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb16.png|thumb|Figure 16: Example of a rule for standard discharge]]&lt;br /&gt;
:The influence of the balance on the discharge is posed by two functions according to rule 7. In addition to the already necessary storage volume/discharge function, there is a relation between the balance and scaling factor. The scaling factor is taken from the difference between the actual balance and the expected value.&lt;br /&gt;
&lt;br /&gt;
:The method is demonstrated with a simple example of a standard discharge.&lt;br /&gt;
&lt;br /&gt;
:For storage A, long-term monthly mean values of the storage volumes and derived sliding 30-day mean values of the storage filling levels, as well as the rule for the standard discharge, are known.&lt;br /&gt;
&lt;br /&gt;
:If, for example, on May 1st the average value of the storage volume calculated from the last 30 days amounts to 5.6 million m³ and thus, according to [[:Datei:Theorie_Abb15.png|Fig. 15]], it deviates by 30% from the long-term average value of 8 million m³, a scaling factor of 0.5 results (see [[:Datei:Theorie_Abb16.png|Fig. 16]]). With this value, the standard discharge is reduced and delivers only 0.25m³/s at a current storage filling level of 40%, i.e. 50% less than intended.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb17.png|thumb|left|Abbildung 17: Example functions to link a water balance with a discharge]]The relation between the deviation of the balance and the scaling factor indicates that only starting from a difference greater than 20% a change of the standard discharge takes place. In the case of a decrease of more than 20%, the standard discharge is reduced stepwise. If the actual moving 30-day average exceeds the long-term values by more than 20%, the standard discharge is increased continuously.&lt;br /&gt;
&lt;br /&gt;
:In general, there is also the possibility to extend the relation by superposing and combining several water balances.&lt;br /&gt;
&lt;br /&gt;
:The interaction between water balance and discharge function is explained below.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 9: Priorities for Competing Discharges from a Storage==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb18.png|thumb|Figure 18: Example for assigning priorities via the position of functions]]&lt;br /&gt;
:If there are several discharges from a storage, it can occur that it is not possible to carry out all demanded discharges. In such a case, priorities need to be specified, which determine an order in which discharges are to be satisfied. The order of priorities is often a consequence of political decisions and is not subject to physical conditions.&lt;br /&gt;
&lt;br /&gt;
:However, there are some priorities based on physical conditions. An example is turning off a turbine in times of water shortage in favor of securing the water supply. In practice, operating rules often meet this problem by fulfilling demands up to defined storage volumes, but not maintaining discharges below the set storage volume.&lt;br /&gt;
&lt;br /&gt;
:Another way to describe priorities is to reduce a discharge A exactly by an amount, which is resulting from a second discharge B, with the discharge A never being smaller than zero.&lt;br /&gt;
&lt;br /&gt;
* Practical example:&lt;br /&gt;
:The Wiehl dam gives a good example for the practical operating conditions of a dam. The Wiehl dam serves primarily as a drinking water supply and a means for flood protection, and secondarily for energy production. In addition, a minimum flow of 100 l/s has to be guaranteed downstream of the Wiehl dam. The first priority is the drinking water supply. In order to ensure sufficient water quality in the storage, additional discharges used for energy production are stopped when the storage volume falls below 70% of the total volume. As both the minimum discharge and the turbine discharge leave into the Wiehl, it would also be uncalled-for to maintain the minimum discharge if water was simultaneously discharged through the turbine. This results in a reduction of a discharge A (minimum discharge) by the amount of discharge B (turbine) as described above &amp;lt;ref name=&amp;quot;Aggerverband_1999&amp;quot;&amp;gt;&#039;&#039;&#039;Aggerverband&#039;&#039;&#039; (1999): Hydrologische Sicherheit der Genkel- und Aggertalsperre. Gutachten des Fachgebietes Ingenieurhydrologie und Wasserbewirtschaftung, TU Darmstadt&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb19.png|thumb||Figure 19: Example of a relation between two discharges]]&lt;br /&gt;
:Assuming that for each use, following the above rules, a functional dependency between reservoir content and discharge exists, a ranking of several uses is already given by the position of the function&#039;s nodes.  Then, the respective reservoir volume from which the target discharge is no longer covered to 100% or even reduced to zero is decisive.&lt;br /&gt;
&lt;br /&gt;
:In the example, the ranking of the uses is clearly visible. First, the turbine is switched off, then the increase of low water refrained from until only the discharge covering the water supply remains.&lt;br /&gt;
&lt;br /&gt;
:In addition, it is possible to directly compare two or more discharges. Such a rule could be:&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;If discharge B &amp;gt; 0 and the reservoir volume S &amp;lt; X, then reduce discharge A by the amount of discharge B, with discharge  A not being smaller than zero.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:This means that a linear dependency exists between A and B until B is equal to the value of A. If B increases further, A remains constantly zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 11: Water Distribution==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:If there is the need to distribute water within a water resources system, a distribution rule must be defined.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb19.5.png|thumb|Diversion]]&lt;br /&gt;
&lt;br /&gt;
:Two types of diversions can occur:&lt;br /&gt;
:# Diversion that exclusively follows hydraulic laws &lt;br /&gt;
:# Adjustable diversions &lt;br /&gt;
&lt;br /&gt;
:In both cases, relations can always be defined as a function of the inflow. In the second case, these distribution rules represent an operating rule, since they directly influence the transport and storage behavior of water. The number of discharges is basically not limited. The difference to transitions at dams is that in this case no reservoir volume can be used as a reference value.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb20.png|thumb|Figure 20 :Example of assignment functions for multiple sequences]]&lt;br /&gt;
&lt;br /&gt;
* Practical example: &lt;br /&gt;
:The water supply of Windhoek, the capital of Namibia, is provided by three dams. However, the water withdrawal for the drinking water supply is only possible from one dam - the Von Bach Dam. The remaining two reservoirs are connected to the main dam by pipes. However, the volume transferred between Swakopport Dam and Von Bach Dam is not exclusively available for refilling the Von Bach Dam, but also serves to supply the town of Karibib with drinking water.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb21.png|thumb|left|Fig. 21: Example of a threshold concept for a division into two flows]]For the definition of division rules, functions depending on the current inflow are an appropriate representation. Thus, both a hydraulic description and a description serving the management of the storage are possible. For each discharge leaving the diversion structure, a distribution function has to be specified. If the functions are to be variable, scaling is recommended.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb22.png|thumb|Figure 22: Example of a threshold concept with a distribution to serve several users&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
:If the distribution functions cannot be pre-defined, but the discharge volumes rather result later from demand calculations, then a threshold concept is suitable, which in turn can work with scaling factors. The threshold is scaled by a factor and is therefore variable. As long as the inflow is lower than the threshold, the entire inflow is used to satisfy the demand. Only when the current inflow exceeds the threshold, the remaining amount is discharged.&lt;br /&gt;
&lt;br /&gt;
:If a division into more than two discharges is necessary, the threshold concept can be successively applied several times. The order of the discharges determines the priorities of the water distribution.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Literature==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/75/en&amp;diff=12959</id>
		<title>Translations:Betriebsregeltypen/75/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/75/en&amp;diff=12959"/>
		<updated>2021-08-30T10:35:04Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* Practical example:&lt;br /&gt;
:The Wiehl dam gives a good example for the practical operating conditions of a dam. The Wiehl dam serves primarily as a drinking water supply and a means for flood protection, and secondarily for energy production. In addition, a minimum flow of 100 l/s has to be guaranteed downstream of the Wiehl dam. The first priority is the drinking water supply. In order to ensure sufficient water quality in the storage, additional discharges used for energy production are stopped when the storage volume falls below 70% of the total volume. As both the minimum discharge and the turbine discharge leave into the Wiehl, it would also be uncalled-for to maintain the minimum discharge if water was simultaneously discharged through the turbine. This results in a reduction of a discharge A (minimum discharge) by the amount of discharge B (turbine) as described above &amp;lt;ref name=&amp;quot;Aggerverband_1999&amp;quot;&amp;gt;&#039;&#039;&#039;Aggerverband&#039;&#039;&#039; (1999): Hydrologische Sicherheit der Genkel- und Aggertalsperre. Gutachten des Fachgebietes Ingenieurhydrologie und Wasserbewirtschaftung, TU Darmstadt&amp;lt;/ref&amp;gt;.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12958</id>
		<title>Betriebsregeltypen/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12958"/>
		<updated>2021-08-30T10:34:45Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=|hoch=Betriebsregelkonzept|nachher=Abstraktion der Betriebsregeln}}&lt;br /&gt;
&lt;br /&gt;
The operating plan of a dam or a storage network is part of the official approval of plans and usually is available as a report or presentation. Its complexity can vary: it ranges from simply defining flood protection areas and setting a report and alarm plan to notify the supervisory authorities in exceptional situations to complex sets of rules concerning functional dependencies that derive discharges from varying system states.&lt;br /&gt;
&lt;br /&gt;
As follows, principles to clarify the variety of possible regulations and reduce them to essential dependencies are presented. A concept is derived to represent most operating rules by a few basic calculation rules. The given selection does not claim to be complete, but it is likely to contain the rules applied in practice.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Basic Principle: Verification of Physical Limits==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb1.png|thumb|Figure 1: Dependency on storage capacity]]&lt;br /&gt;
&lt;br /&gt;
When specifying discharges according to an operating rule, it is assumed that the outlet capacity is sufficient to meet these discharges. Thus, dimensioning the outlet element must consider the operating requirements. In principle, the physically possible discharge, given by the outlet&#039;s characteristic curve at full opening, sets the upper limit value.&lt;br /&gt;
&lt;br /&gt;
If the pressure level or the outlet capacity is sufficient to discharge the desired quantity when fully opened, the discharge can be throttled to the intended level by closing a slide. If the pressure level is insufficient, only the hydraulically possible discharge can be discharged.&lt;br /&gt;
&lt;br /&gt;
*Mathematical abstraction:&lt;br /&gt;
:All outlets obeying an operating rule are functions of the storage&#039;s volume and cannot exceed the outlets&#039; maximum capacity when fully opened. As soon as the capacity of the outlets exceeds the required discharge, it can be adjusted by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
All discharge types from storages mentioned below are subject to this restriction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 1: Definition of a Minimum Output or a Safely Dischargeable Maximum Output==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb2.png|thumb|Figure 2: Example for minimum and maximum discharge as a function of storage capacity]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The specification of a minimum or maximum discharge is based on requirements downstream of a reservoir. The maximal discharge is based on the discharge respective to a critical, downstream cross-section. Consequently, a hydraulic method exists for its determination. In contrast, there is no clear guideline for the minimum discharge. Often, ratios of MNQ or MQ are used. Independent of determining the minimum or maximum discharge, the basic principle to verify outlet elements&#039; physical limits is applied. So, minimum and maximum discharge can only be discharged if the outlet capacity is sufficient at the given pressure level. Since, in reality, it is unlikely that the dimensioning of the outlet elements and the required discharge are conflicting, the reference to the dependence on the storage capacity content is rather theoretical but necessary to derive general laws.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Minimum and maximum discharge are functions of the storage volume and follow the characteristic curve of fully opened outlets at a low filling level. As soon as the outlet elements&#039; capacity is sufficient for the required discharge volume, the discharge can be kept constant by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 2: Maintaining a Flood Protection Area, Possibly Timely Variable Over the Year==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb3.png|thumb|Figure 3: Example of a function to maintain a flood protection area]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The definition of a flood protection area as a minimum requirement only includes the designation of a volume, which has to be kept free for potential floodwater. The dimensioning is based on flood events with certain recurrence intervals. If the water level exceeds the mark of the protection area, an increased discharge to the downstream water of the storage ensures that the area is kept empty. Thus, this rule is reduced to a relation between discharge and storage volume, where the outlet capacity or a defined maximum discharge can serve as an upper limit for keeping the flood protection area empty. If the flood protection area is variable in time over the year, only the discharge of the respective storage volume is increased.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:There is a direct relation between storage capacity and release. If the storage capacity exceeds the mark of the flood protection area, a discharge occurs. If it remains below the mark, the discharge is set to zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 3: Direct Withdrawals from a storage for Drinking or Service Water ==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb4.png|thumb|Figure 4: Example of a function for drinking or raw water withdrawal]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Primarily, the current demand determines the volume of withdrawals from the storage, but it is also subject to temporal variations. The upper limits for withdrawals are generally set by water rights or defined maximum withdrawal volumes, which refer to selected periods such as a day, a month, a quarter, or a year. Initially, one only considers the current demand communicated by water suppliers, which constitutes a claim towards the storage. There is no connection to the actual storage and the respective storage volume.&lt;br /&gt;
:Whether the demand can be pleased by withdrawing water from the storage is determined by the actual storage volumes. To connect the water demand to the actual storage volumes, the structural implementation of withdrawal elements and means of anticipatory management are taken into account. For example, if particularly low storage volumes are reached, it is advisable to throttle withdrawals in advance to avoid the storage running empty and then completely failing at covering the demand during prolonged periods of low water &amp;lt;ref name=&amp;quot;Schultz_1989&amp;quot;&amp;gt;&#039;&#039;&#039;Schultz, G.A.&#039;&#039;&#039; (1989): Entwicklung von Betriebsregeln für die Wupper-Talsperre in Niedrig- und Hochwasserzeiten. Wasserwirtschaft 79 (7/8) S. 340-343&amp;lt;/ref&amp;gt;. Hence, there is usually space reserved in a dam specifically used for drinking water supply. Its use is handled separately in respective operating plans.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:If the demand is exactly known and unchangeable, a direct relation between withdrawal and storage volume can be defined. However, the demand is subject to certain variations. For this reason, it is recommended to normalize the relationship between withdrawals and storage volume, where the current demand serves as a scaling factor. If the storage volume falls below a defined limit value, only a certain percentage of the current demand is satisfied. The limit value, as well as the form of the function, can be variable in time.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 4: Standard Discharge to Downstream Water==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb5.png|thumb|Figure 5: Pool-based operating plan in a two-dimensional representation]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The normal discharge to the downstream water should provide a discharge compensation for seasonal differences in the inflow. If a minimum discharge is required, it will be included in the normal discharge. A pool-based operating plan is used to describe the normal discharge. It divides the storage capacity into different areas and assigns a discharge to each pool-based operation. When determining the pool-based operating plan, the long-term discharge and other withdrawals from the reservoir for other purposes play a decisive role. A reservoir should collect water in periods of high inflow but still not overflow to have sufficient reserves in periods of low inflow. The coupling of the releases to the storage pool-based operation is a function of the storage volume. Since the system is supposed to react to variations of inflow during the year, the relationship between storage volume and discharge is usually variable over time.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb6.png|thumb|Figure 6: Comparison of a pool-based operating plan in a two- and three-dimensional representation]] Like for the previous rules, the output depends on the storage volume. Usually, a pool-based operating plan is displayed in two-dimensional diagrams. The X-axis shows the time of one year, while the Y-axis shows the storage capacity. Pool-based operations are depicted as lines of equal outputs.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb7.png|thumb|Figure 7: Pool-based operating plan with linear interpolation between successive time reference points]]This view is practical but not yet complete: A three-dimensional representation of a simple pool-based operating plan makes this clear. On the X-axis is the time, on the Y-axis the storage capacity is plotted, while the Z-axis shows the output directed upwards.&lt;br /&gt;
&lt;br /&gt;
:The 3D image viewed from above gives the two-dimensional shape. Instead of taking constant blocks for the individual time horizons, a linear connection is also used often.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb8.png|thumb|Figure 8: Pool-based operating plan with two types of interpretation (selected month of May)]]For the individual periods - here months - different functional dependencies between storage capacity and outflow are considered. If the storage volume/discharge relation is also considered for a selected point in time, there are two possibilities to connect the discharge nodes. On the one hand, there is the possibility of linear interpolation, and on the other hand, a step function is possible.&lt;br /&gt;
&lt;br /&gt;
:In two-dimensional space, this information is not visible and must be specified separately. However, there is usually the convention to assume that the output between two nodes is constant, i.e. to interpret the pool-based operating plan as shown above in the form of steps.&amp;lt;br clear=&amp;quot;all&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 5: Maintaining Defined Discharges to Downstream Waters (Increase of Low Water / Coverage of Demand)==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb9.png|thumb|Figure 9: Example of a function between shortfalls and scaling factors for a storage&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
* Dependency: &lt;br /&gt;
:In this case, the current discharge is determined by conditions downstream of a storage. At a cross-section of a water resources system, the so-called &#039;&#039;control point&#039;&#039;, where the flow is dependent on the discharge from the upstream storage, a minimum flow is defined. The flow at the control point is composed of the discharge from upstream storages and the lateral inflows between the storages and the control point. If the current flow remains below the set minimum, an additional discharge from upstream storages is necessary. The volume of the additional discharge depends on the difference between the previously defined target flow and the actual flow. Whether the required discharge can be fully provided from the storage depends on the currently available stored volumes in the storage. The lower the level, the less favorable it is to provide additional water. In this context, the increase of low water/coverage of demand behaves completely identical to the drinking or service water withdrawal, with only the triggering factor differing. As mentioned before, a storage-dependent function is scaled by a factor, but this factor is now derived from a comparison between set values and current discharges.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:The determination of the additionally needed discharge is composed of several factors. Firstly, a volumetrically varying shortfall of water results from failing the target discharge. The shortfall of water is then implemented as a scaling factor to the discharge which can be defined by a function. The shortfall of water functions independently, while the scaling factor functions dependently.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb10.png|thumb|Figure 10: Example of a function for increasing low water levels or meeting demand]]&lt;br /&gt;
&lt;br /&gt;
:Secondly, it depends on the actual storage volume, if and how an additional discharge from the storage can be met. A normalized volume-dependent function and the needed discharge lead to a clear determination of the additional discharge volumes. The following [[:Datei:Theorie_Abb10.png||Fig. 10]] shows an example, where the complete provision of an increased target can only be achieved if the filling level of the storage is above a critical limit (25%).&lt;br /&gt;
&lt;br /&gt;
:If more than one storage has an influence on the relevant control point or if, in principle, more than one storage facility is to be used to meet the demand, the required additional discharge is to be divided between the storages in accordance with the corresponding regulations. A distinction must be made between the direct and indirect influences of a storage on the control point. A direct influence is present if a discharge can have a direct effect on the flow conditions at the control point, i.e. the natural flow between the storage &lt;br /&gt;
and the control point can no longer be changed by regulation. If this is not the case, an indirect influence is given.&lt;br /&gt;
&lt;br /&gt;
:All storages with a direct influence on the control point receive a shortfall factor and a volume-dependent, scalable function according to [[:Datei:Theorie_Abb10.png|Figure 10]]. Thus, depending on the shortfall quantities and the storage capacity, the actual discharge can be determined separately for each storage.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 6: Discharge Depending on the storage Inflow==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb11.png|thumb|Figure 11: Direct dependency between storage and control point]]&lt;br /&gt;
:There is a direct dependency between the discharge from the storage and the current inflow to the storage. Similar to the pool-based operating plan, there is also an adaptation to different inflow situations. This is done to prevent depletion or overflowing or to obtain a variable discharge regime downstream. However, long-term inflow fluctuations are difficult to detect with this operating rule, since the observations are only carried out as snapshots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:To determine an inflow-dependent discharge, several components have to be considered. First of all, a relation between the current inflow and discharge must be defined. In addition to the current inflow, the current storage volume is important, because the relation inflow/outflow must not be valid for every filling level. Thus it is likely that the relation is ceded completely or the release quantities are adjusted if the storage level falls below a critical level.&lt;br /&gt;
&lt;br /&gt;
:As this rule can lead to the co-occurrence of relatively small storage volumes and high inflows resulting in high discharge volumes, special attention must be paid to the basic principle of checking the physical limits.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb12.png|thumb|Figure 12: Example of functions for inflow-dependent discharge]]&lt;br /&gt;
:In this case, three functional dependencies play a part. First, there is a direct dependency between the current inflow and the discharge. The form of the function can be arbitrary. It is possible to reproduce only individual sections of the inflow, which corresponds to a partial approximation of the discharge to the duration curve of the inflow.&lt;br /&gt;
&lt;br /&gt;
:Second, the inflow/discharge function can be superposed with the relationship between storage volume and discharge. For reasons of clarity, it is recommended to work with a normalized function. This makes it possible to influence the result of the inflow/discharge function for each storage volume, which is especially convenient for low filling levels.&lt;br /&gt;
&lt;br /&gt;
:Finally, the required discharge has to be checked with regard to the outlet elements&#039; capacity.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb13.png|thumb|left|Figure 13: Results of different inflow-dependent release strategies]]&lt;br /&gt;
&lt;br /&gt;
:The examples below show how the interaction of different functions affects the discharges. The results are compared in the following figures as inflow and discharge duration lines.&lt;br /&gt;
&lt;br /&gt;
:In the case of a linear relation between inflow and discharge and a constant factor for the storage volume, the duration line of the discharge is a curve corresponding to the inflow reduced by a certain percentage. If the storage volume factor remains constant, the duration line can be changed by varying the inflow/discharge relationship. An additional modification of the factor via the storage volume has the advantage of being able to respond to certain filling levels to prevent the storage from emptying or overflowing.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 7: Influence of Discharges Trough System States==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Rule 7, just as rule 6, is a continuation and generalization of the increase of low water as described in rules 5. Just like a discharge deficit at a cross-section or the storage inflow can influence the discharge, any other system state can. In general terms, this means that a discharge from a storage is triggered, increased, or reduced due to a certain system state. Basically, it is irrelevant where the system state occurs. All measurable variables that influence the transport and storage of water can be considered as system states, e.g. the filling of other storages, discharges, flow regime at a cross-section, a snow depth in the catchment area, current precipitation, or current soil moisture.&lt;br /&gt;
&lt;br /&gt;
:As a requirement to apply those dependencies a detection of the system state is necessary. Practically, this means either that a measuring device must be available to determine needed parameters or the required values are calculated using a mathematical model. Parameters are only considered as snap-shots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:If several system states should influence the discharge, a superposition of the parameters according to a corresponding regulation is necessary.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Mathematically, the influence of system states on the discharge can always be undertaken by scaling. Two functions are necessary for this. The first function describes the relationship between storage volume and discharge. The second one controls the dependency between the system state and a scaling factor. The connection is done by multiplying the discharge with the scaling factor.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb13.5.png|thumb|Transition]]&lt;br /&gt;
&lt;br /&gt;
:A simple example is given by a transition from storage A to storage B. &lt;br /&gt;
&lt;br /&gt;
:The decisive discharge is the transition from A to B. The considered system state is the storage volume of B. It seems obvious that a discharge from A to B is only useful if storage A has sufficient provision and storage B has sufficient capacity to hold additional water. This results in the following simple functions:&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb14.png|thumb|left|Figure 14: Example functions for linking a system state to a discharge]]Reservoir B takes 100% of the discharge from A as long as its filling level does not reach 70% of the maximum volume. Furthermore, it is undesirable to receive additional water for flood protection reasons. The scaling factor decreases from 70% filling level to zero. Starting at a filling level above 50% it becomes increasingly easy to transfer water from Reservoir A to reservoir B. The actual transfer, however, only results from the interaction of both functions, taking into account the current filling level of reservoir B and the scaling derived from it.&lt;br /&gt;
&lt;br /&gt;
:For storage A, the definition of the discharge is in m³/s, while the function for storage B receives a unitless scaling factor. In principle, however, it is possible to exchange the meaning of the functions and to use a unitless function for storage A to scale the desired transfer volume for storage B.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 8: Influencing a Discharge with Balances==&lt;br /&gt;
&lt;br /&gt;
 Dependency: [[Datei:Theorie_Abb15.png|thumb|Figure 15 : Example of long-term monthly averages and moving 30 day averages of storage volumes]]&lt;br /&gt;
:This rule is an extension of rule 7. Instead of using a current state parameter, the balance of a system state is linked to discharge. It is important that there are set time boundaries for carrying out the balance. However, it is irrelevant whether the balance is interpreted as a sum or as an average. A function that displays scaling factors depending on the actual balance can then be used to influence discharges.&lt;br /&gt;
&lt;br /&gt;
:In practice, this form of dependency is often found where water rights define maximum withdrawal volumes per time unit. But the application of a balance is also interesting regarding the long-term behaviour of storage filling levels or inflows. For example, a discharge could be reduced to build up provisions if the inflow of the past winter half-year was below a defined expected value. Another application is the comparison between long-term and current moving averages of storage filling levels. If the current values deviate from the long-term values by a certain amount, the discharge can be reduced or increased to compensate.&lt;br /&gt;
&lt;br /&gt;
:If linking a discharge to several balances is desired, it is possible to superpose several balances (see example at the end of this chapter). &lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb16.png|thumb|Figure 16: Example of a rule for standard discharge]]&lt;br /&gt;
:The influence of the balance on the discharge is posed by two functions according to rule 7. In addition to the already necessary storage volume/discharge function, there is a relation between the balance and scaling factor. The scaling factor is taken from the difference between the actual balance and the expected value.&lt;br /&gt;
&lt;br /&gt;
:The method is demonstrated with a simple example of a standard discharge.&lt;br /&gt;
&lt;br /&gt;
:For storage A, long-term monthly mean values of the storage volumes and derived sliding 30-day mean values of the storage filling levels, as well as the rule for the standard discharge, are known.&lt;br /&gt;
&lt;br /&gt;
:If, for example, on May 1st the average value of the storage volume calculated from the last 30 days amounts to 5.6 million m³ and thus, according to [[:Datei:Theorie_Abb15.png|Fig. 15]], it deviates by 30% from the long-term average value of 8 million m³, a scaling factor of 0.5 results (see [[:Datei:Theorie_Abb16.png|Fig. 16]]). With this value, the standard discharge is reduced and delivers only 0.25m³/s at a current storage filling level of 40%, i.e. 50% less than intended.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb17.png|thumb|left|Abbildung 17: Example functions to link a water balance with a discharge]]The relation between the deviation of the balance and the scaling factor indicates that only starting from a difference greater than 20% a change of the standard discharge takes place. In the case of a decrease of more than 20%, the standard discharge is reduced stepwise. If the actual moving 30-day average exceeds the long-term values by more than 20%, the standard discharge is increased continuously.&lt;br /&gt;
&lt;br /&gt;
:In general, there is also the possibility to extend the relation by superposing and combining several water balances.&lt;br /&gt;
&lt;br /&gt;
:The interaction between water balance and discharge function is explained below.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 9: Priorities for Competing Discharges from a Storage==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb18.png|thumb|Figure 18: Example for assigning priorities via the position of functions]]&lt;br /&gt;
:If there are several discharges from a storage, it can occur that it is not possible to carry out all demanded discharges. In such a case, priorities need to be specified, which determine an order in which discharges are to be satisfied. The order of priorities is often a consequence of political decisions and is not subject to physical conditions.&lt;br /&gt;
&lt;br /&gt;
:However, there are some priorities based on physical conditions. An example is turning off a turbine in times of water shortage in favor of securing the water supply. In practice, operating rules often meet this problem by fulfilling demands up to defined storage volumes, but not maintaining discharges below the set storage volume.&lt;br /&gt;
&lt;br /&gt;
:Another way to describe priorities is to reduce a discharge A exactly by an amount, which is resulting from a second discharge B, with the discharge A never being smaller than zero.&lt;br /&gt;
&lt;br /&gt;
* Practical example:&lt;br /&gt;
:The Wiehl dam gives a good example for the practical operating conditions of a dam. The Wiehl dam serves primarily as a drinking water supply and a means for flood protection, and secondarily for energy production. In addition, a minimum flow of 100 l/s has to be guaranteed downstream of the Wiehl dam. The first priority is the drinking water supply. In order to ensure sufficient water quality in the reservoir, additional discharges used for energy production are stopped when the reservoir volume falls below 70% of the total volume. As both the minimum discharge and the turbine discharge leave into the Wiehl, it would also be uncalled-for to maintain the minimum discharge if water was simultaneously discharged through the turbine. This results in a reduction of a discharge A (minimum discharge) by the amount of discharge B (turbine) as described above &amp;lt;ref name=&amp;quot;Aggerverband_1999&amp;quot;&amp;gt;&#039;&#039;&#039;Aggerverband&#039;&#039;&#039; (1999): Hydrologische Sicherheit der Genkel- und Aggertalsperre. Gutachten des Fachgebietes Ingenieurhydrologie und Wasserbewirtschaftung, TU Darmstadt&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb19.png|thumb||Figure 19: Example of a relation between two discharges]]&lt;br /&gt;
:Assuming that for each use, following the above rules, a functional dependency between reservoir content and discharge exists, a ranking of several uses is already given by the position of the function&#039;s nodes.  Then, the respective reservoir volume from which the target discharge is no longer covered to 100% or even reduced to zero is decisive.&lt;br /&gt;
&lt;br /&gt;
:In the example, the ranking of the uses is clearly visible. First, the turbine is switched off, then the increase of low water refrained from until only the discharge covering the water supply remains.&lt;br /&gt;
&lt;br /&gt;
:In addition, it is possible to directly compare two or more discharges. Such a rule could be:&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;If discharge B &amp;gt; 0 and the reservoir volume S &amp;lt; X, then reduce discharge A by the amount of discharge B, with discharge  A not being smaller than zero.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:This means that a linear dependency exists between A and B until B is equal to the value of A. If B increases further, A remains constantly zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 11: Water Distribution==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:If there is the need to distribute water within a water resources system, a distribution rule must be defined.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb19.5.png|thumb|Diversion]]&lt;br /&gt;
&lt;br /&gt;
:Two types of diversions can occur:&lt;br /&gt;
:# Diversion that exclusively follows hydraulic laws &lt;br /&gt;
:# Adjustable diversions &lt;br /&gt;
&lt;br /&gt;
:In both cases, relations can always be defined as a function of the inflow. In the second case, these distribution rules represent an operating rule, since they directly influence the transport and storage behavior of water. The number of discharges is basically not limited. The difference to transitions at dams is that in this case no reservoir volume can be used as a reference value.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb20.png|thumb|Figure 20 :Example of assignment functions for multiple sequences]]&lt;br /&gt;
&lt;br /&gt;
* Practical example: &lt;br /&gt;
:The water supply of Windhoek, the capital of Namibia, is provided by three dams. However, the water withdrawal for the drinking water supply is only possible from one dam - the Von Bach Dam. The remaining two reservoirs are connected to the main dam by pipes. However, the volume transferred between Swakopport Dam and Von Bach Dam is not exclusively available for refilling the Von Bach Dam, but also serves to supply the town of Karibib with drinking water.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb21.png|thumb|left|Fig. 21: Example of a threshold concept for a division into two flows]]For the definition of division rules, functions depending on the current inflow are an appropriate representation. Thus, both a hydraulic description and a description serving the management of the storage are possible. For each discharge leaving the diversion structure, a distribution function has to be specified. If the functions are to be variable, scaling is recommended.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb22.png|thumb|Figure 22: Example of a threshold concept with a distribution to serve several users&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
:If the distribution functions cannot be pre-defined, but the discharge volumes rather result later from demand calculations, then a threshold concept is suitable, which in turn can work with scaling factors. The threshold is scaled by a factor and is therefore variable. As long as the inflow is lower than the threshold, the entire inflow is used to satisfy the demand. Only when the current inflow exceeds the threshold, the remaining amount is discharged.&lt;br /&gt;
&lt;br /&gt;
:If a division into more than two discharges is necessary, the threshold concept can be successively applied several times. The order of the discharges determines the priorities of the water distribution.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Literature==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/73/en&amp;diff=12957</id>
		<title>Translations:Betriebsregeltypen/73/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/73/en&amp;diff=12957"/>
		<updated>2021-08-30T10:34:45Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;:However, there are some priorities based on physical conditions. An example is turning off a turbine in times of water shortage in favor of securing the water supply. In practice, operating rules often meet this problem by fulfilling demands up to defined storage volumes, but not maintaining discharges below the set storage volume.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12956</id>
		<title>Betriebsregeltypen/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12956"/>
		<updated>2021-08-30T10:34:33Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=|hoch=Betriebsregelkonzept|nachher=Abstraktion der Betriebsregeln}}&lt;br /&gt;
&lt;br /&gt;
The operating plan of a dam or a storage network is part of the official approval of plans and usually is available as a report or presentation. Its complexity can vary: it ranges from simply defining flood protection areas and setting a report and alarm plan to notify the supervisory authorities in exceptional situations to complex sets of rules concerning functional dependencies that derive discharges from varying system states.&lt;br /&gt;
&lt;br /&gt;
As follows, principles to clarify the variety of possible regulations and reduce them to essential dependencies are presented. A concept is derived to represent most operating rules by a few basic calculation rules. The given selection does not claim to be complete, but it is likely to contain the rules applied in practice.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Basic Principle: Verification of Physical Limits==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb1.png|thumb|Figure 1: Dependency on storage capacity]]&lt;br /&gt;
&lt;br /&gt;
When specifying discharges according to an operating rule, it is assumed that the outlet capacity is sufficient to meet these discharges. Thus, dimensioning the outlet element must consider the operating requirements. In principle, the physically possible discharge, given by the outlet&#039;s characteristic curve at full opening, sets the upper limit value.&lt;br /&gt;
&lt;br /&gt;
If the pressure level or the outlet capacity is sufficient to discharge the desired quantity when fully opened, the discharge can be throttled to the intended level by closing a slide. If the pressure level is insufficient, only the hydraulically possible discharge can be discharged.&lt;br /&gt;
&lt;br /&gt;
*Mathematical abstraction:&lt;br /&gt;
:All outlets obeying an operating rule are functions of the storage&#039;s volume and cannot exceed the outlets&#039; maximum capacity when fully opened. As soon as the capacity of the outlets exceeds the required discharge, it can be adjusted by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
All discharge types from storages mentioned below are subject to this restriction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 1: Definition of a Minimum Output or a Safely Dischargeable Maximum Output==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb2.png|thumb|Figure 2: Example for minimum and maximum discharge as a function of storage capacity]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The specification of a minimum or maximum discharge is based on requirements downstream of a reservoir. The maximal discharge is based on the discharge respective to a critical, downstream cross-section. Consequently, a hydraulic method exists for its determination. In contrast, there is no clear guideline for the minimum discharge. Often, ratios of MNQ or MQ are used. Independent of determining the minimum or maximum discharge, the basic principle to verify outlet elements&#039; physical limits is applied. So, minimum and maximum discharge can only be discharged if the outlet capacity is sufficient at the given pressure level. Since, in reality, it is unlikely that the dimensioning of the outlet elements and the required discharge are conflicting, the reference to the dependence on the storage capacity content is rather theoretical but necessary to derive general laws.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Minimum and maximum discharge are functions of the storage volume and follow the characteristic curve of fully opened outlets at a low filling level. As soon as the outlet elements&#039; capacity is sufficient for the required discharge volume, the discharge can be kept constant by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 2: Maintaining a Flood Protection Area, Possibly Timely Variable Over the Year==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb3.png|thumb|Figure 3: Example of a function to maintain a flood protection area]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The definition of a flood protection area as a minimum requirement only includes the designation of a volume, which has to be kept free for potential floodwater. The dimensioning is based on flood events with certain recurrence intervals. If the water level exceeds the mark of the protection area, an increased discharge to the downstream water of the storage ensures that the area is kept empty. Thus, this rule is reduced to a relation between discharge and storage volume, where the outlet capacity or a defined maximum discharge can serve as an upper limit for keeping the flood protection area empty. If the flood protection area is variable in time over the year, only the discharge of the respective storage volume is increased.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:There is a direct relation between storage capacity and release. If the storage capacity exceeds the mark of the flood protection area, a discharge occurs. If it remains below the mark, the discharge is set to zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 3: Direct Withdrawals from a storage for Drinking or Service Water ==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb4.png|thumb|Figure 4: Example of a function for drinking or raw water withdrawal]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Primarily, the current demand determines the volume of withdrawals from the storage, but it is also subject to temporal variations. The upper limits for withdrawals are generally set by water rights or defined maximum withdrawal volumes, which refer to selected periods such as a day, a month, a quarter, or a year. Initially, one only considers the current demand communicated by water suppliers, which constitutes a claim towards the storage. There is no connection to the actual storage and the respective storage volume.&lt;br /&gt;
:Whether the demand can be pleased by withdrawing water from the storage is determined by the actual storage volumes. To connect the water demand to the actual storage volumes, the structural implementation of withdrawal elements and means of anticipatory management are taken into account. For example, if particularly low storage volumes are reached, it is advisable to throttle withdrawals in advance to avoid the storage running empty and then completely failing at covering the demand during prolonged periods of low water &amp;lt;ref name=&amp;quot;Schultz_1989&amp;quot;&amp;gt;&#039;&#039;&#039;Schultz, G.A.&#039;&#039;&#039; (1989): Entwicklung von Betriebsregeln für die Wupper-Talsperre in Niedrig- und Hochwasserzeiten. Wasserwirtschaft 79 (7/8) S. 340-343&amp;lt;/ref&amp;gt;. Hence, there is usually space reserved in a dam specifically used for drinking water supply. Its use is handled separately in respective operating plans.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:If the demand is exactly known and unchangeable, a direct relation between withdrawal and storage volume can be defined. However, the demand is subject to certain variations. For this reason, it is recommended to normalize the relationship between withdrawals and storage volume, where the current demand serves as a scaling factor. If the storage volume falls below a defined limit value, only a certain percentage of the current demand is satisfied. The limit value, as well as the form of the function, can be variable in time.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 4: Standard Discharge to Downstream Water==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb5.png|thumb|Figure 5: Pool-based operating plan in a two-dimensional representation]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The normal discharge to the downstream water should provide a discharge compensation for seasonal differences in the inflow. If a minimum discharge is required, it will be included in the normal discharge. A pool-based operating plan is used to describe the normal discharge. It divides the storage capacity into different areas and assigns a discharge to each pool-based operation. When determining the pool-based operating plan, the long-term discharge and other withdrawals from the reservoir for other purposes play a decisive role. A reservoir should collect water in periods of high inflow but still not overflow to have sufficient reserves in periods of low inflow. The coupling of the releases to the storage pool-based operation is a function of the storage volume. Since the system is supposed to react to variations of inflow during the year, the relationship between storage volume and discharge is usually variable over time.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb6.png|thumb|Figure 6: Comparison of a pool-based operating plan in a two- and three-dimensional representation]] Like for the previous rules, the output depends on the storage volume. Usually, a pool-based operating plan is displayed in two-dimensional diagrams. The X-axis shows the time of one year, while the Y-axis shows the storage capacity. Pool-based operations are depicted as lines of equal outputs.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb7.png|thumb|Figure 7: Pool-based operating plan with linear interpolation between successive time reference points]]This view is practical but not yet complete: A three-dimensional representation of a simple pool-based operating plan makes this clear. On the X-axis is the time, on the Y-axis the storage capacity is plotted, while the Z-axis shows the output directed upwards.&lt;br /&gt;
&lt;br /&gt;
:The 3D image viewed from above gives the two-dimensional shape. Instead of taking constant blocks for the individual time horizons, a linear connection is also used often.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb8.png|thumb|Figure 8: Pool-based operating plan with two types of interpretation (selected month of May)]]For the individual periods - here months - different functional dependencies between storage capacity and outflow are considered. If the storage volume/discharge relation is also considered for a selected point in time, there are two possibilities to connect the discharge nodes. On the one hand, there is the possibility of linear interpolation, and on the other hand, a step function is possible.&lt;br /&gt;
&lt;br /&gt;
:In two-dimensional space, this information is not visible and must be specified separately. However, there is usually the convention to assume that the output between two nodes is constant, i.e. to interpret the pool-based operating plan as shown above in the form of steps.&amp;lt;br clear=&amp;quot;all&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 5: Maintaining Defined Discharges to Downstream Waters (Increase of Low Water / Coverage of Demand)==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb9.png|thumb|Figure 9: Example of a function between shortfalls and scaling factors for a storage&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
* Dependency: &lt;br /&gt;
:In this case, the current discharge is determined by conditions downstream of a storage. At a cross-section of a water resources system, the so-called &#039;&#039;control point&#039;&#039;, where the flow is dependent on the discharge from the upstream storage, a minimum flow is defined. The flow at the control point is composed of the discharge from upstream storages and the lateral inflows between the storages and the control point. If the current flow remains below the set minimum, an additional discharge from upstream storages is necessary. The volume of the additional discharge depends on the difference between the previously defined target flow and the actual flow. Whether the required discharge can be fully provided from the storage depends on the currently available stored volumes in the storage. The lower the level, the less favorable it is to provide additional water. In this context, the increase of low water/coverage of demand behaves completely identical to the drinking or service water withdrawal, with only the triggering factor differing. As mentioned before, a storage-dependent function is scaled by a factor, but this factor is now derived from a comparison between set values and current discharges.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:The determination of the additionally needed discharge is composed of several factors. Firstly, a volumetrically varying shortfall of water results from failing the target discharge. The shortfall of water is then implemented as a scaling factor to the discharge which can be defined by a function. The shortfall of water functions independently, while the scaling factor functions dependently.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb10.png|thumb|Figure 10: Example of a function for increasing low water levels or meeting demand]]&lt;br /&gt;
&lt;br /&gt;
:Secondly, it depends on the actual storage volume, if and how an additional discharge from the storage can be met. A normalized volume-dependent function and the needed discharge lead to a clear determination of the additional discharge volumes. The following [[:Datei:Theorie_Abb10.png||Fig. 10]] shows an example, where the complete provision of an increased target can only be achieved if the filling level of the storage is above a critical limit (25%).&lt;br /&gt;
&lt;br /&gt;
:If more than one storage has an influence on the relevant control point or if, in principle, more than one storage facility is to be used to meet the demand, the required additional discharge is to be divided between the storages in accordance with the corresponding regulations. A distinction must be made between the direct and indirect influences of a storage on the control point. A direct influence is present if a discharge can have a direct effect on the flow conditions at the control point, i.e. the natural flow between the storage &lt;br /&gt;
and the control point can no longer be changed by regulation. If this is not the case, an indirect influence is given.&lt;br /&gt;
&lt;br /&gt;
:All storages with a direct influence on the control point receive a shortfall factor and a volume-dependent, scalable function according to [[:Datei:Theorie_Abb10.png|Figure 10]]. Thus, depending on the shortfall quantities and the storage capacity, the actual discharge can be determined separately for each storage.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 6: Discharge Depending on the storage Inflow==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb11.png|thumb|Figure 11: Direct dependency between storage and control point]]&lt;br /&gt;
:There is a direct dependency between the discharge from the storage and the current inflow to the storage. Similar to the pool-based operating plan, there is also an adaptation to different inflow situations. This is done to prevent depletion or overflowing or to obtain a variable discharge regime downstream. However, long-term inflow fluctuations are difficult to detect with this operating rule, since the observations are only carried out as snapshots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:To determine an inflow-dependent discharge, several components have to be considered. First of all, a relation between the current inflow and discharge must be defined. In addition to the current inflow, the current storage volume is important, because the relation inflow/outflow must not be valid for every filling level. Thus it is likely that the relation is ceded completely or the release quantities are adjusted if the storage level falls below a critical level.&lt;br /&gt;
&lt;br /&gt;
:As this rule can lead to the co-occurrence of relatively small storage volumes and high inflows resulting in high discharge volumes, special attention must be paid to the basic principle of checking the physical limits.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb12.png|thumb|Figure 12: Example of functions for inflow-dependent discharge]]&lt;br /&gt;
:In this case, three functional dependencies play a part. First, there is a direct dependency between the current inflow and the discharge. The form of the function can be arbitrary. It is possible to reproduce only individual sections of the inflow, which corresponds to a partial approximation of the discharge to the duration curve of the inflow.&lt;br /&gt;
&lt;br /&gt;
:Second, the inflow/discharge function can be superposed with the relationship between storage volume and discharge. For reasons of clarity, it is recommended to work with a normalized function. This makes it possible to influence the result of the inflow/discharge function for each storage volume, which is especially convenient for low filling levels.&lt;br /&gt;
&lt;br /&gt;
:Finally, the required discharge has to be checked with regard to the outlet elements&#039; capacity.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb13.png|thumb|left|Figure 13: Results of different inflow-dependent release strategies]]&lt;br /&gt;
&lt;br /&gt;
:The examples below show how the interaction of different functions affects the discharges. The results are compared in the following figures as inflow and discharge duration lines.&lt;br /&gt;
&lt;br /&gt;
:In the case of a linear relation between inflow and discharge and a constant factor for the storage volume, the duration line of the discharge is a curve corresponding to the inflow reduced by a certain percentage. If the storage volume factor remains constant, the duration line can be changed by varying the inflow/discharge relationship. An additional modification of the factor via the storage volume has the advantage of being able to respond to certain filling levels to prevent the storage from emptying or overflowing.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 7: Influence of Discharges Trough System States==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Rule 7, just as rule 6, is a continuation and generalization of the increase of low water as described in rules 5. Just like a discharge deficit at a cross-section or the storage inflow can influence the discharge, any other system state can. In general terms, this means that a discharge from a storage is triggered, increased, or reduced due to a certain system state. Basically, it is irrelevant where the system state occurs. All measurable variables that influence the transport and storage of water can be considered as system states, e.g. the filling of other storages, discharges, flow regime at a cross-section, a snow depth in the catchment area, current precipitation, or current soil moisture.&lt;br /&gt;
&lt;br /&gt;
:As a requirement to apply those dependencies a detection of the system state is necessary. Practically, this means either that a measuring device must be available to determine needed parameters or the required values are calculated using a mathematical model. Parameters are only considered as snap-shots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:If several system states should influence the discharge, a superposition of the parameters according to a corresponding regulation is necessary.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Mathematically, the influence of system states on the discharge can always be undertaken by scaling. Two functions are necessary for this. The first function describes the relationship between storage volume and discharge. The second one controls the dependency between the system state and a scaling factor. The connection is done by multiplying the discharge with the scaling factor.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb13.5.png|thumb|Transition]]&lt;br /&gt;
&lt;br /&gt;
:A simple example is given by a transition from storage A to storage B. &lt;br /&gt;
&lt;br /&gt;
:The decisive discharge is the transition from A to B. The considered system state is the storage volume of B. It seems obvious that a discharge from A to B is only useful if storage A has sufficient provision and storage B has sufficient capacity to hold additional water. This results in the following simple functions:&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb14.png|thumb|left|Figure 14: Example functions for linking a system state to a discharge]]Reservoir B takes 100% of the discharge from A as long as its filling level does not reach 70% of the maximum volume. Furthermore, it is undesirable to receive additional water for flood protection reasons. The scaling factor decreases from 70% filling level to zero. Starting at a filling level above 50% it becomes increasingly easy to transfer water from Reservoir A to reservoir B. The actual transfer, however, only results from the interaction of both functions, taking into account the current filling level of reservoir B and the scaling derived from it.&lt;br /&gt;
&lt;br /&gt;
:For storage A, the definition of the discharge is in m³/s, while the function for storage B receives a unitless scaling factor. In principle, however, it is possible to exchange the meaning of the functions and to use a unitless function for storage A to scale the desired transfer volume for storage B.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 8: Influencing a Discharge with Balances==&lt;br /&gt;
&lt;br /&gt;
 Dependency: [[Datei:Theorie_Abb15.png|thumb|Figure 15 : Example of long-term monthly averages and moving 30 day averages of storage volumes]]&lt;br /&gt;
:This rule is an extension of rule 7. Instead of using a current state parameter, the balance of a system state is linked to discharge. It is important that there are set time boundaries for carrying out the balance. However, it is irrelevant whether the balance is interpreted as a sum or as an average. A function that displays scaling factors depending on the actual balance can then be used to influence discharges.&lt;br /&gt;
&lt;br /&gt;
:In practice, this form of dependency is often found where water rights define maximum withdrawal volumes per time unit. But the application of a balance is also interesting regarding the long-term behaviour of storage filling levels or inflows. For example, a discharge could be reduced to build up provisions if the inflow of the past winter half-year was below a defined expected value. Another application is the comparison between long-term and current moving averages of storage filling levels. If the current values deviate from the long-term values by a certain amount, the discharge can be reduced or increased to compensate.&lt;br /&gt;
&lt;br /&gt;
:If linking a discharge to several balances is desired, it is possible to superpose several balances (see example at the end of this chapter). &lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb16.png|thumb|Figure 16: Example of a rule for standard discharge]]&lt;br /&gt;
:The influence of the balance on the discharge is posed by two functions according to rule 7. In addition to the already necessary storage volume/discharge function, there is a relation between the balance and scaling factor. The scaling factor is taken from the difference between the actual balance and the expected value.&lt;br /&gt;
&lt;br /&gt;
:The method is demonstrated with a simple example of a standard discharge.&lt;br /&gt;
&lt;br /&gt;
:For storage A, long-term monthly mean values of the storage volumes and derived sliding 30-day mean values of the storage filling levels, as well as the rule for the standard discharge, are known.&lt;br /&gt;
&lt;br /&gt;
:If, for example, on May 1st the average value of the storage volume calculated from the last 30 days amounts to 5.6 million m³ and thus, according to [[:Datei:Theorie_Abb15.png|Fig. 15]], it deviates by 30% from the long-term average value of 8 million m³, a scaling factor of 0.5 results (see [[:Datei:Theorie_Abb16.png|Fig. 16]]). With this value, the standard discharge is reduced and delivers only 0.25m³/s at a current storage filling level of 40%, i.e. 50% less than intended.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb17.png|thumb|left|Abbildung 17: Example functions to link a water balance with a discharge]]The relation between the deviation of the balance and the scaling factor indicates that only starting from a difference greater than 20% a change of the standard discharge takes place. In the case of a decrease of more than 20%, the standard discharge is reduced stepwise. If the actual moving 30-day average exceeds the long-term values by more than 20%, the standard discharge is increased continuously.&lt;br /&gt;
&lt;br /&gt;
:In general, there is also the possibility to extend the relation by superposing and combining several water balances.&lt;br /&gt;
&lt;br /&gt;
:The interaction between water balance and discharge function is explained below.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 9: Priorities for Competing Discharges from a Storage==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb18.png|thumb|Figure 18: Example for assigning priorities via the position of functions]]&lt;br /&gt;
:If there are several discharges from a storage, it can occur that it is not possible to carry out all demanded discharges. In such a case, priorities need to be specified, which determine an order in which discharges are to be satisfied. The order of priorities is often a consequence of political decisions and is not subject to physical conditions.&lt;br /&gt;
&lt;br /&gt;
:However, there are some priorities based on physical conditions. An example is turning off a turbine in times of water shortage in favor of securing the water supply. In practice, operating rules often meet this problem by fulfilling demands up to defined reservoir volumes, but not maintaining discharges below the set reservoir volume.&lt;br /&gt;
&lt;br /&gt;
:Another way to describe priorities is to reduce a discharge A exactly by an amount, which is resulting from a second discharge B, with the discharge A never being smaller than zero.&lt;br /&gt;
&lt;br /&gt;
* Practical example:&lt;br /&gt;
:The Wiehl dam gives a good example for the practical operating conditions of a dam. The Wiehl dam serves primarily as a drinking water supply and a means for flood protection, and secondarily for energy production. In addition, a minimum flow of 100 l/s has to be guaranteed downstream of the Wiehl dam. The first priority is the drinking water supply. In order to ensure sufficient water quality in the reservoir, additional discharges used for energy production are stopped when the reservoir volume falls below 70% of the total volume. As both the minimum discharge and the turbine discharge leave into the Wiehl, it would also be uncalled-for to maintain the minimum discharge if water was simultaneously discharged through the turbine. This results in a reduction of a discharge A (minimum discharge) by the amount of discharge B (turbine) as described above &amp;lt;ref name=&amp;quot;Aggerverband_1999&amp;quot;&amp;gt;&#039;&#039;&#039;Aggerverband&#039;&#039;&#039; (1999): Hydrologische Sicherheit der Genkel- und Aggertalsperre. Gutachten des Fachgebietes Ingenieurhydrologie und Wasserbewirtschaftung, TU Darmstadt&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb19.png|thumb||Figure 19: Example of a relation between two discharges]]&lt;br /&gt;
:Assuming that for each use, following the above rules, a functional dependency between reservoir content and discharge exists, a ranking of several uses is already given by the position of the function&#039;s nodes.  Then, the respective reservoir volume from which the target discharge is no longer covered to 100% or even reduced to zero is decisive.&lt;br /&gt;
&lt;br /&gt;
:In the example, the ranking of the uses is clearly visible. First, the turbine is switched off, then the increase of low water refrained from until only the discharge covering the water supply remains.&lt;br /&gt;
&lt;br /&gt;
:In addition, it is possible to directly compare two or more discharges. Such a rule could be:&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;If discharge B &amp;gt; 0 and the reservoir volume S &amp;lt; X, then reduce discharge A by the amount of discharge B, with discharge  A not being smaller than zero.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:This means that a linear dependency exists between A and B until B is equal to the value of A. If B increases further, A remains constantly zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 11: Water Distribution==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:If there is the need to distribute water within a water resources system, a distribution rule must be defined.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb19.5.png|thumb|Diversion]]&lt;br /&gt;
&lt;br /&gt;
:Two types of diversions can occur:&lt;br /&gt;
:# Diversion that exclusively follows hydraulic laws &lt;br /&gt;
:# Adjustable diversions &lt;br /&gt;
&lt;br /&gt;
:In both cases, relations can always be defined as a function of the inflow. In the second case, these distribution rules represent an operating rule, since they directly influence the transport and storage behavior of water. The number of discharges is basically not limited. The difference to transitions at dams is that in this case no reservoir volume can be used as a reference value.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb20.png|thumb|Figure 20 :Example of assignment functions for multiple sequences]]&lt;br /&gt;
&lt;br /&gt;
* Practical example: &lt;br /&gt;
:The water supply of Windhoek, the capital of Namibia, is provided by three dams. However, the water withdrawal for the drinking water supply is only possible from one dam - the Von Bach Dam. The remaining two reservoirs are connected to the main dam by pipes. However, the volume transferred between Swakopport Dam and Von Bach Dam is not exclusively available for refilling the Von Bach Dam, but also serves to supply the town of Karibib with drinking water.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb21.png|thumb|left|Fig. 21: Example of a threshold concept for a division into two flows]]For the definition of division rules, functions depending on the current inflow are an appropriate representation. Thus, both a hydraulic description and a description serving the management of the storage are possible. For each discharge leaving the diversion structure, a distribution function has to be specified. If the functions are to be variable, scaling is recommended.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb22.png|thumb|Figure 22: Example of a threshold concept with a distribution to serve several users&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
:If the distribution functions cannot be pre-defined, but the discharge volumes rather result later from demand calculations, then a threshold concept is suitable, which in turn can work with scaling factors. The threshold is scaled by a factor and is therefore variable. As long as the inflow is lower than the threshold, the entire inflow is used to satisfy the demand. Only when the current inflow exceeds the threshold, the remaining amount is discharged.&lt;br /&gt;
&lt;br /&gt;
:If a division into more than two discharges is necessary, the threshold concept can be successively applied several times. The order of the discharges determines the priorities of the water distribution.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Literature==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/72/en&amp;diff=12955</id>
		<title>Translations:Betriebsregeltypen/72/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/72/en&amp;diff=12955"/>
		<updated>2021-08-30T10:34:33Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* Dependency: [[Datei:Theorie_Abb18.png|thumb|Figure 18: Example for assigning priorities via the position of functions]]&lt;br /&gt;
:If there are several discharges from a storage, it can occur that it is not possible to carry out all demanded discharges. In such a case, priorities need to be specified, which determine an order in which discharges are to be satisfied. The order of priorities is often a consequence of political decisions and is not subject to physical conditions.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12954</id>
		<title>Betriebsregeltypen/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12954"/>
		<updated>2021-08-30T10:34:10Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=|hoch=Betriebsregelkonzept|nachher=Abstraktion der Betriebsregeln}}&lt;br /&gt;
&lt;br /&gt;
The operating plan of a dam or a storage network is part of the official approval of plans and usually is available as a report or presentation. Its complexity can vary: it ranges from simply defining flood protection areas and setting a report and alarm plan to notify the supervisory authorities in exceptional situations to complex sets of rules concerning functional dependencies that derive discharges from varying system states.&lt;br /&gt;
&lt;br /&gt;
As follows, principles to clarify the variety of possible regulations and reduce them to essential dependencies are presented. A concept is derived to represent most operating rules by a few basic calculation rules. The given selection does not claim to be complete, but it is likely to contain the rules applied in practice.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Basic Principle: Verification of Physical Limits==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb1.png|thumb|Figure 1: Dependency on storage capacity]]&lt;br /&gt;
&lt;br /&gt;
When specifying discharges according to an operating rule, it is assumed that the outlet capacity is sufficient to meet these discharges. Thus, dimensioning the outlet element must consider the operating requirements. In principle, the physically possible discharge, given by the outlet&#039;s characteristic curve at full opening, sets the upper limit value.&lt;br /&gt;
&lt;br /&gt;
If the pressure level or the outlet capacity is sufficient to discharge the desired quantity when fully opened, the discharge can be throttled to the intended level by closing a slide. If the pressure level is insufficient, only the hydraulically possible discharge can be discharged.&lt;br /&gt;
&lt;br /&gt;
*Mathematical abstraction:&lt;br /&gt;
:All outlets obeying an operating rule are functions of the storage&#039;s volume and cannot exceed the outlets&#039; maximum capacity when fully opened. As soon as the capacity of the outlets exceeds the required discharge, it can be adjusted by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
All discharge types from storages mentioned below are subject to this restriction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 1: Definition of a Minimum Output or a Safely Dischargeable Maximum Output==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb2.png|thumb|Figure 2: Example for minimum and maximum discharge as a function of storage capacity]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The specification of a minimum or maximum discharge is based on requirements downstream of a reservoir. The maximal discharge is based on the discharge respective to a critical, downstream cross-section. Consequently, a hydraulic method exists for its determination. In contrast, there is no clear guideline for the minimum discharge. Often, ratios of MNQ or MQ are used. Independent of determining the minimum or maximum discharge, the basic principle to verify outlet elements&#039; physical limits is applied. So, minimum and maximum discharge can only be discharged if the outlet capacity is sufficient at the given pressure level. Since, in reality, it is unlikely that the dimensioning of the outlet elements and the required discharge are conflicting, the reference to the dependence on the storage capacity content is rather theoretical but necessary to derive general laws.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Minimum and maximum discharge are functions of the storage volume and follow the characteristic curve of fully opened outlets at a low filling level. As soon as the outlet elements&#039; capacity is sufficient for the required discharge volume, the discharge can be kept constant by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 2: Maintaining a Flood Protection Area, Possibly Timely Variable Over the Year==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb3.png|thumb|Figure 3: Example of a function to maintain a flood protection area]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The definition of a flood protection area as a minimum requirement only includes the designation of a volume, which has to be kept free for potential floodwater. The dimensioning is based on flood events with certain recurrence intervals. If the water level exceeds the mark of the protection area, an increased discharge to the downstream water of the storage ensures that the area is kept empty. Thus, this rule is reduced to a relation between discharge and storage volume, where the outlet capacity or a defined maximum discharge can serve as an upper limit for keeping the flood protection area empty. If the flood protection area is variable in time over the year, only the discharge of the respective storage volume is increased.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:There is a direct relation between storage capacity and release. If the storage capacity exceeds the mark of the flood protection area, a discharge occurs. If it remains below the mark, the discharge is set to zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 3: Direct Withdrawals from a storage for Drinking or Service Water ==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb4.png|thumb|Figure 4: Example of a function for drinking or raw water withdrawal]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Primarily, the current demand determines the volume of withdrawals from the storage, but it is also subject to temporal variations. The upper limits for withdrawals are generally set by water rights or defined maximum withdrawal volumes, which refer to selected periods such as a day, a month, a quarter, or a year. Initially, one only considers the current demand communicated by water suppliers, which constitutes a claim towards the storage. There is no connection to the actual storage and the respective storage volume.&lt;br /&gt;
:Whether the demand can be pleased by withdrawing water from the storage is determined by the actual storage volumes. To connect the water demand to the actual storage volumes, the structural implementation of withdrawal elements and means of anticipatory management are taken into account. For example, if particularly low storage volumes are reached, it is advisable to throttle withdrawals in advance to avoid the storage running empty and then completely failing at covering the demand during prolonged periods of low water &amp;lt;ref name=&amp;quot;Schultz_1989&amp;quot;&amp;gt;&#039;&#039;&#039;Schultz, G.A.&#039;&#039;&#039; (1989): Entwicklung von Betriebsregeln für die Wupper-Talsperre in Niedrig- und Hochwasserzeiten. Wasserwirtschaft 79 (7/8) S. 340-343&amp;lt;/ref&amp;gt;. Hence, there is usually space reserved in a dam specifically used for drinking water supply. Its use is handled separately in respective operating plans.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:If the demand is exactly known and unchangeable, a direct relation between withdrawal and storage volume can be defined. However, the demand is subject to certain variations. For this reason, it is recommended to normalize the relationship between withdrawals and storage volume, where the current demand serves as a scaling factor. If the storage volume falls below a defined limit value, only a certain percentage of the current demand is satisfied. The limit value, as well as the form of the function, can be variable in time.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 4: Standard Discharge to Downstream Water==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb5.png|thumb|Figure 5: Pool-based operating plan in a two-dimensional representation]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The normal discharge to the downstream water should provide a discharge compensation for seasonal differences in the inflow. If a minimum discharge is required, it will be included in the normal discharge. A pool-based operating plan is used to describe the normal discharge. It divides the storage capacity into different areas and assigns a discharge to each pool-based operation. When determining the pool-based operating plan, the long-term discharge and other withdrawals from the reservoir for other purposes play a decisive role. A reservoir should collect water in periods of high inflow but still not overflow to have sufficient reserves in periods of low inflow. The coupling of the releases to the storage pool-based operation is a function of the storage volume. Since the system is supposed to react to variations of inflow during the year, the relationship between storage volume and discharge is usually variable over time.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb6.png|thumb|Figure 6: Comparison of a pool-based operating plan in a two- and three-dimensional representation]] Like for the previous rules, the output depends on the storage volume. Usually, a pool-based operating plan is displayed in two-dimensional diagrams. The X-axis shows the time of one year, while the Y-axis shows the storage capacity. Pool-based operations are depicted as lines of equal outputs.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb7.png|thumb|Figure 7: Pool-based operating plan with linear interpolation between successive time reference points]]This view is practical but not yet complete: A three-dimensional representation of a simple pool-based operating plan makes this clear. On the X-axis is the time, on the Y-axis the storage capacity is plotted, while the Z-axis shows the output directed upwards.&lt;br /&gt;
&lt;br /&gt;
:The 3D image viewed from above gives the two-dimensional shape. Instead of taking constant blocks for the individual time horizons, a linear connection is also used often.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb8.png|thumb|Figure 8: Pool-based operating plan with two types of interpretation (selected month of May)]]For the individual periods - here months - different functional dependencies between storage capacity and outflow are considered. If the storage volume/discharge relation is also considered for a selected point in time, there are two possibilities to connect the discharge nodes. On the one hand, there is the possibility of linear interpolation, and on the other hand, a step function is possible.&lt;br /&gt;
&lt;br /&gt;
:In two-dimensional space, this information is not visible and must be specified separately. However, there is usually the convention to assume that the output between two nodes is constant, i.e. to interpret the pool-based operating plan as shown above in the form of steps.&amp;lt;br clear=&amp;quot;all&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 5: Maintaining Defined Discharges to Downstream Waters (Increase of Low Water / Coverage of Demand)==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb9.png|thumb|Figure 9: Example of a function between shortfalls and scaling factors for a storage&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
* Dependency: &lt;br /&gt;
:In this case, the current discharge is determined by conditions downstream of a storage. At a cross-section of a water resources system, the so-called &#039;&#039;control point&#039;&#039;, where the flow is dependent on the discharge from the upstream storage, a minimum flow is defined. The flow at the control point is composed of the discharge from upstream storages and the lateral inflows between the storages and the control point. If the current flow remains below the set minimum, an additional discharge from upstream storages is necessary. The volume of the additional discharge depends on the difference between the previously defined target flow and the actual flow. Whether the required discharge can be fully provided from the storage depends on the currently available stored volumes in the storage. The lower the level, the less favorable it is to provide additional water. In this context, the increase of low water/coverage of demand behaves completely identical to the drinking or service water withdrawal, with only the triggering factor differing. As mentioned before, a storage-dependent function is scaled by a factor, but this factor is now derived from a comparison between set values and current discharges.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:The determination of the additionally needed discharge is composed of several factors. Firstly, a volumetrically varying shortfall of water results from failing the target discharge. The shortfall of water is then implemented as a scaling factor to the discharge which can be defined by a function. The shortfall of water functions independently, while the scaling factor functions dependently.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb10.png|thumb|Figure 10: Example of a function for increasing low water levels or meeting demand]]&lt;br /&gt;
&lt;br /&gt;
:Secondly, it depends on the actual storage volume, if and how an additional discharge from the storage can be met. A normalized volume-dependent function and the needed discharge lead to a clear determination of the additional discharge volumes. The following [[:Datei:Theorie_Abb10.png||Fig. 10]] shows an example, where the complete provision of an increased target can only be achieved if the filling level of the storage is above a critical limit (25%).&lt;br /&gt;
&lt;br /&gt;
:If more than one storage has an influence on the relevant control point or if, in principle, more than one storage facility is to be used to meet the demand, the required additional discharge is to be divided between the storages in accordance with the corresponding regulations. A distinction must be made between the direct and indirect influences of a storage on the control point. A direct influence is present if a discharge can have a direct effect on the flow conditions at the control point, i.e. the natural flow between the storage &lt;br /&gt;
and the control point can no longer be changed by regulation. If this is not the case, an indirect influence is given.&lt;br /&gt;
&lt;br /&gt;
:All storages with a direct influence on the control point receive a shortfall factor and a volume-dependent, scalable function according to [[:Datei:Theorie_Abb10.png|Figure 10]]. Thus, depending on the shortfall quantities and the storage capacity, the actual discharge can be determined separately for each storage.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 6: Discharge Depending on the storage Inflow==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb11.png|thumb|Figure 11: Direct dependency between storage and control point]]&lt;br /&gt;
:There is a direct dependency between the discharge from the storage and the current inflow to the storage. Similar to the pool-based operating plan, there is also an adaptation to different inflow situations. This is done to prevent depletion or overflowing or to obtain a variable discharge regime downstream. However, long-term inflow fluctuations are difficult to detect with this operating rule, since the observations are only carried out as snapshots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:To determine an inflow-dependent discharge, several components have to be considered. First of all, a relation between the current inflow and discharge must be defined. In addition to the current inflow, the current storage volume is important, because the relation inflow/outflow must not be valid for every filling level. Thus it is likely that the relation is ceded completely or the release quantities are adjusted if the storage level falls below a critical level.&lt;br /&gt;
&lt;br /&gt;
:As this rule can lead to the co-occurrence of relatively small storage volumes and high inflows resulting in high discharge volumes, special attention must be paid to the basic principle of checking the physical limits.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb12.png|thumb|Figure 12: Example of functions for inflow-dependent discharge]]&lt;br /&gt;
:In this case, three functional dependencies play a part. First, there is a direct dependency between the current inflow and the discharge. The form of the function can be arbitrary. It is possible to reproduce only individual sections of the inflow, which corresponds to a partial approximation of the discharge to the duration curve of the inflow.&lt;br /&gt;
&lt;br /&gt;
:Second, the inflow/discharge function can be superposed with the relationship between storage volume and discharge. For reasons of clarity, it is recommended to work with a normalized function. This makes it possible to influence the result of the inflow/discharge function for each storage volume, which is especially convenient for low filling levels.&lt;br /&gt;
&lt;br /&gt;
:Finally, the required discharge has to be checked with regard to the outlet elements&#039; capacity.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb13.png|thumb|left|Figure 13: Results of different inflow-dependent release strategies]]&lt;br /&gt;
&lt;br /&gt;
:The examples below show how the interaction of different functions affects the discharges. The results are compared in the following figures as inflow and discharge duration lines.&lt;br /&gt;
&lt;br /&gt;
:In the case of a linear relation between inflow and discharge and a constant factor for the storage volume, the duration line of the discharge is a curve corresponding to the inflow reduced by a certain percentage. If the storage volume factor remains constant, the duration line can be changed by varying the inflow/discharge relationship. An additional modification of the factor via the storage volume has the advantage of being able to respond to certain filling levels to prevent the storage from emptying or overflowing.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 7: Influence of Discharges Trough System States==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Rule 7, just as rule 6, is a continuation and generalization of the increase of low water as described in rules 5. Just like a discharge deficit at a cross-section or the storage inflow can influence the discharge, any other system state can. In general terms, this means that a discharge from a storage is triggered, increased, or reduced due to a certain system state. Basically, it is irrelevant where the system state occurs. All measurable variables that influence the transport and storage of water can be considered as system states, e.g. the filling of other storages, discharges, flow regime at a cross-section, a snow depth in the catchment area, current precipitation, or current soil moisture.&lt;br /&gt;
&lt;br /&gt;
:As a requirement to apply those dependencies a detection of the system state is necessary. Practically, this means either that a measuring device must be available to determine needed parameters or the required values are calculated using a mathematical model. Parameters are only considered as snap-shots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:If several system states should influence the discharge, a superposition of the parameters according to a corresponding regulation is necessary.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Mathematically, the influence of system states on the discharge can always be undertaken by scaling. Two functions are necessary for this. The first function describes the relationship between storage volume and discharge. The second one controls the dependency between the system state and a scaling factor. The connection is done by multiplying the discharge with the scaling factor.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb13.5.png|thumb|Transition]]&lt;br /&gt;
&lt;br /&gt;
:A simple example is given by a transition from storage A to storage B. &lt;br /&gt;
&lt;br /&gt;
:The decisive discharge is the transition from A to B. The considered system state is the storage volume of B. It seems obvious that a discharge from A to B is only useful if storage A has sufficient provision and storage B has sufficient capacity to hold additional water. This results in the following simple functions:&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb14.png|thumb|left|Figure 14: Example functions for linking a system state to a discharge]]Reservoir B takes 100% of the discharge from A as long as its filling level does not reach 70% of the maximum volume. Furthermore, it is undesirable to receive additional water for flood protection reasons. The scaling factor decreases from 70% filling level to zero. Starting at a filling level above 50% it becomes increasingly easy to transfer water from Reservoir A to reservoir B. The actual transfer, however, only results from the interaction of both functions, taking into account the current filling level of reservoir B and the scaling derived from it.&lt;br /&gt;
&lt;br /&gt;
:For storage A, the definition of the discharge is in m³/s, while the function for storage B receives a unitless scaling factor. In principle, however, it is possible to exchange the meaning of the functions and to use a unitless function for storage A to scale the desired transfer volume for storage B.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 8: Influencing a Discharge with Balances==&lt;br /&gt;
&lt;br /&gt;
 Dependency: [[Datei:Theorie_Abb15.png|thumb|Figure 15 : Example of long-term monthly averages and moving 30 day averages of storage volumes]]&lt;br /&gt;
:This rule is an extension of rule 7. Instead of using a current state parameter, the balance of a system state is linked to discharge. It is important that there are set time boundaries for carrying out the balance. However, it is irrelevant whether the balance is interpreted as a sum or as an average. A function that displays scaling factors depending on the actual balance can then be used to influence discharges.&lt;br /&gt;
&lt;br /&gt;
:In practice, this form of dependency is often found where water rights define maximum withdrawal volumes per time unit. But the application of a balance is also interesting regarding the long-term behaviour of storage filling levels or inflows. For example, a discharge could be reduced to build up provisions if the inflow of the past winter half-year was below a defined expected value. Another application is the comparison between long-term and current moving averages of storage filling levels. If the current values deviate from the long-term values by a certain amount, the discharge can be reduced or increased to compensate.&lt;br /&gt;
&lt;br /&gt;
:If linking a discharge to several balances is desired, it is possible to superpose several balances (see example at the end of this chapter). &lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb16.png|thumb|Figure 16: Example of a rule for standard discharge]]&lt;br /&gt;
:The influence of the balance on the discharge is posed by two functions according to rule 7. In addition to the already necessary storage volume/discharge function, there is a relation between the balance and scaling factor. The scaling factor is taken from the difference between the actual balance and the expected value.&lt;br /&gt;
&lt;br /&gt;
:The method is demonstrated with a simple example of a standard discharge.&lt;br /&gt;
&lt;br /&gt;
:For storage A, long-term monthly mean values of the storage volumes and derived sliding 30-day mean values of the storage filling levels, as well as the rule for the standard discharge, are known.&lt;br /&gt;
&lt;br /&gt;
:If, for example, on May 1st the average value of the storage volume calculated from the last 30 days amounts to 5.6 million m³ and thus, according to [[:Datei:Theorie_Abb15.png|Fig. 15]], it deviates by 30% from the long-term average value of 8 million m³, a scaling factor of 0.5 results (see [[:Datei:Theorie_Abb16.png|Fig. 16]]). With this value, the standard discharge is reduced and delivers only 0.25m³/s at a current storage filling level of 40%, i.e. 50% less than intended.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb17.png|thumb|left|Abbildung 17: Example functions to link a water balance with a discharge]]The relation between the deviation of the balance and the scaling factor indicates that only starting from a difference greater than 20% a change of the standard discharge takes place. In the case of a decrease of more than 20%, the standard discharge is reduced stepwise. If the actual moving 30-day average exceeds the long-term values by more than 20%, the standard discharge is increased continuously.&lt;br /&gt;
&lt;br /&gt;
:In general, there is also the possibility to extend the relation by superposing and combining several water balances.&lt;br /&gt;
&lt;br /&gt;
:The interaction between water balance and discharge function is explained below.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 9: Priorities for Competing Discharges from a Storage==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb18.png|thumb|Figure 18: Example for assigning priorities via the position of functions]]&lt;br /&gt;
:If there are several discharges from a reservoir, it can occur that it is not possible to carry out all demanded discharges. In such a case, priorities need to be specified, which determine an order in which discharges are to be satisfied. The order of priorities is often a consequence of political decisions and is not subject to physical conditions.&lt;br /&gt;
&lt;br /&gt;
:However, there are some priorities based on physical conditions. An example is turning off a turbine in times of water shortage in favor of securing the water supply. In practice, operating rules often meet this problem by fulfilling demands up to defined reservoir volumes, but not maintaining discharges below the set reservoir volume.&lt;br /&gt;
&lt;br /&gt;
:Another way to describe priorities is to reduce a discharge A exactly by an amount, which is resulting from a second discharge B, with the discharge A never being smaller than zero.&lt;br /&gt;
&lt;br /&gt;
* Practical example:&lt;br /&gt;
:The Wiehl dam gives a good example for the practical operating conditions of a dam. The Wiehl dam serves primarily as a drinking water supply and a means for flood protection, and secondarily for energy production. In addition, a minimum flow of 100 l/s has to be guaranteed downstream of the Wiehl dam. The first priority is the drinking water supply. In order to ensure sufficient water quality in the reservoir, additional discharges used for energy production are stopped when the reservoir volume falls below 70% of the total volume. As both the minimum discharge and the turbine discharge leave into the Wiehl, it would also be uncalled-for to maintain the minimum discharge if water was simultaneously discharged through the turbine. This results in a reduction of a discharge A (minimum discharge) by the amount of discharge B (turbine) as described above &amp;lt;ref name=&amp;quot;Aggerverband_1999&amp;quot;&amp;gt;&#039;&#039;&#039;Aggerverband&#039;&#039;&#039; (1999): Hydrologische Sicherheit der Genkel- und Aggertalsperre. Gutachten des Fachgebietes Ingenieurhydrologie und Wasserbewirtschaftung, TU Darmstadt&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb19.png|thumb||Figure 19: Example of a relation between two discharges]]&lt;br /&gt;
:Assuming that for each use, following the above rules, a functional dependency between reservoir content and discharge exists, a ranking of several uses is already given by the position of the function&#039;s nodes.  Then, the respective reservoir volume from which the target discharge is no longer covered to 100% or even reduced to zero is decisive.&lt;br /&gt;
&lt;br /&gt;
:In the example, the ranking of the uses is clearly visible. First, the turbine is switched off, then the increase of low water refrained from until only the discharge covering the water supply remains.&lt;br /&gt;
&lt;br /&gt;
:In addition, it is possible to directly compare two or more discharges. Such a rule could be:&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;If discharge B &amp;gt; 0 and the reservoir volume S &amp;lt; X, then reduce discharge A by the amount of discharge B, with discharge  A not being smaller than zero.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:This means that a linear dependency exists between A and B until B is equal to the value of A. If B increases further, A remains constantly zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 11: Water Distribution==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:If there is the need to distribute water within a water resources system, a distribution rule must be defined.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb19.5.png|thumb|Diversion]]&lt;br /&gt;
&lt;br /&gt;
:Two types of diversions can occur:&lt;br /&gt;
:# Diversion that exclusively follows hydraulic laws &lt;br /&gt;
:# Adjustable diversions &lt;br /&gt;
&lt;br /&gt;
:In both cases, relations can always be defined as a function of the inflow. In the second case, these distribution rules represent an operating rule, since they directly influence the transport and storage behavior of water. The number of discharges is basically not limited. The difference to transitions at dams is that in this case no reservoir volume can be used as a reference value.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb20.png|thumb|Figure 20 :Example of assignment functions for multiple sequences]]&lt;br /&gt;
&lt;br /&gt;
* Practical example: &lt;br /&gt;
:The water supply of Windhoek, the capital of Namibia, is provided by three dams. However, the water withdrawal for the drinking water supply is only possible from one dam - the Von Bach Dam. The remaining two reservoirs are connected to the main dam by pipes. However, the volume transferred between Swakopport Dam and Von Bach Dam is not exclusively available for refilling the Von Bach Dam, but also serves to supply the town of Karibib with drinking water.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb21.png|thumb|left|Fig. 21: Example of a threshold concept for a division into two flows]]For the definition of division rules, functions depending on the current inflow are an appropriate representation. Thus, both a hydraulic description and a description serving the management of the storage are possible. For each discharge leaving the diversion structure, a distribution function has to be specified. If the functions are to be variable, scaling is recommended.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb22.png|thumb|Figure 22: Example of a threshold concept with a distribution to serve several users&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
:If the distribution functions cannot be pre-defined, but the discharge volumes rather result later from demand calculations, then a threshold concept is suitable, which in turn can work with scaling factors. The threshold is scaled by a factor and is therefore variable. As long as the inflow is lower than the threshold, the entire inflow is used to satisfy the demand. Only when the current inflow exceeds the threshold, the remaining amount is discharged.&lt;br /&gt;
&lt;br /&gt;
:If a division into more than two discharges is necessary, the threshold concept can be successively applied several times. The order of the discharges determines the priorities of the water distribution.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Literature==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/71/en&amp;diff=12953</id>
		<title>Translations:Betriebsregeltypen/71/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/71/en&amp;diff=12953"/>
		<updated>2021-08-30T10:34:10Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Rule Type 9: Priorities for Competing Discharges from a Storage==&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12952</id>
		<title>Betriebsregeltypen/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Betriebsregeltypen/en&amp;diff=12952"/>
		<updated>2021-08-30T10:33:50Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;languages/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Navigation|vorher=|hoch=Betriebsregelkonzept|nachher=Abstraktion der Betriebsregeln}}&lt;br /&gt;
&lt;br /&gt;
The operating plan of a dam or a storage network is part of the official approval of plans and usually is available as a report or presentation. Its complexity can vary: it ranges from simply defining flood protection areas and setting a report and alarm plan to notify the supervisory authorities in exceptional situations to complex sets of rules concerning functional dependencies that derive discharges from varying system states.&lt;br /&gt;
&lt;br /&gt;
As follows, principles to clarify the variety of possible regulations and reduce them to essential dependencies are presented. A concept is derived to represent most operating rules by a few basic calculation rules. The given selection does not claim to be complete, but it is likely to contain the rules applied in practice.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Basic Principle: Verification of Physical Limits==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb1.png|thumb|Figure 1: Dependency on storage capacity]]&lt;br /&gt;
&lt;br /&gt;
When specifying discharges according to an operating rule, it is assumed that the outlet capacity is sufficient to meet these discharges. Thus, dimensioning the outlet element must consider the operating requirements. In principle, the physically possible discharge, given by the outlet&#039;s characteristic curve at full opening, sets the upper limit value.&lt;br /&gt;
&lt;br /&gt;
If the pressure level or the outlet capacity is sufficient to discharge the desired quantity when fully opened, the discharge can be throttled to the intended level by closing a slide. If the pressure level is insufficient, only the hydraulically possible discharge can be discharged.&lt;br /&gt;
&lt;br /&gt;
*Mathematical abstraction:&lt;br /&gt;
:All outlets obeying an operating rule are functions of the storage&#039;s volume and cannot exceed the outlets&#039; maximum capacity when fully opened. As soon as the capacity of the outlets exceeds the required discharge, it can be adjusted by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
All discharge types from storages mentioned below are subject to this restriction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 1: Definition of a Minimum Output or a Safely Dischargeable Maximum Output==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb2.png|thumb|Figure 2: Example for minimum and maximum discharge as a function of storage capacity]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The specification of a minimum or maximum discharge is based on requirements downstream of a reservoir. The maximal discharge is based on the discharge respective to a critical, downstream cross-section. Consequently, a hydraulic method exists for its determination. In contrast, there is no clear guideline for the minimum discharge. Often, ratios of MNQ or MQ are used. Independent of determining the minimum or maximum discharge, the basic principle to verify outlet elements&#039; physical limits is applied. So, minimum and maximum discharge can only be discharged if the outlet capacity is sufficient at the given pressure level. Since, in reality, it is unlikely that the dimensioning of the outlet elements and the required discharge are conflicting, the reference to the dependence on the storage capacity content is rather theoretical but necessary to derive general laws.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Minimum and maximum discharge are functions of the storage volume and follow the characteristic curve of fully opened outlets at a low filling level. As soon as the outlet elements&#039; capacity is sufficient for the required discharge volume, the discharge can be kept constant by partially closing the control elements.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 2: Maintaining a Flood Protection Area, Possibly Timely Variable Over the Year==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb3.png|thumb|Figure 3: Example of a function to maintain a flood protection area]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The definition of a flood protection area as a minimum requirement only includes the designation of a volume, which has to be kept free for potential floodwater. The dimensioning is based on flood events with certain recurrence intervals. If the water level exceeds the mark of the protection area, an increased discharge to the downstream water of the storage ensures that the area is kept empty. Thus, this rule is reduced to a relation between discharge and storage volume, where the outlet capacity or a defined maximum discharge can serve as an upper limit for keeping the flood protection area empty. If the flood protection area is variable in time over the year, only the discharge of the respective storage volume is increased.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:There is a direct relation between storage capacity and release. If the storage capacity exceeds the mark of the flood protection area, a discharge occurs. If it remains below the mark, the discharge is set to zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 3: Direct Withdrawals from a storage for Drinking or Service Water ==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb4.png|thumb|Figure 4: Example of a function for drinking or raw water withdrawal]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Primarily, the current demand determines the volume of withdrawals from the storage, but it is also subject to temporal variations. The upper limits for withdrawals are generally set by water rights or defined maximum withdrawal volumes, which refer to selected periods such as a day, a month, a quarter, or a year. Initially, one only considers the current demand communicated by water suppliers, which constitutes a claim towards the storage. There is no connection to the actual storage and the respective storage volume.&lt;br /&gt;
:Whether the demand can be pleased by withdrawing water from the storage is determined by the actual storage volumes. To connect the water demand to the actual storage volumes, the structural implementation of withdrawal elements and means of anticipatory management are taken into account. For example, if particularly low storage volumes are reached, it is advisable to throttle withdrawals in advance to avoid the storage running empty and then completely failing at covering the demand during prolonged periods of low water &amp;lt;ref name=&amp;quot;Schultz_1989&amp;quot;&amp;gt;&#039;&#039;&#039;Schultz, G.A.&#039;&#039;&#039; (1989): Entwicklung von Betriebsregeln für die Wupper-Talsperre in Niedrig- und Hochwasserzeiten. Wasserwirtschaft 79 (7/8) S. 340-343&amp;lt;/ref&amp;gt;. Hence, there is usually space reserved in a dam specifically used for drinking water supply. Its use is handled separately in respective operating plans.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:If the demand is exactly known and unchangeable, a direct relation between withdrawal and storage volume can be defined. However, the demand is subject to certain variations. For this reason, it is recommended to normalize the relationship between withdrawals and storage volume, where the current demand serves as a scaling factor. If the storage volume falls below a defined limit value, only a certain percentage of the current demand is satisfied. The limit value, as well as the form of the function, can be variable in time.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 4: Standard Discharge to Downstream Water==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb5.png|thumb|Figure 5: Pool-based operating plan in a two-dimensional representation]]&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:The normal discharge to the downstream water should provide a discharge compensation for seasonal differences in the inflow. If a minimum discharge is required, it will be included in the normal discharge. A pool-based operating plan is used to describe the normal discharge. It divides the storage capacity into different areas and assigns a discharge to each pool-based operation. When determining the pool-based operating plan, the long-term discharge and other withdrawals from the reservoir for other purposes play a decisive role. A reservoir should collect water in periods of high inflow but still not overflow to have sufficient reserves in periods of low inflow. The coupling of the releases to the storage pool-based operation is a function of the storage volume. Since the system is supposed to react to variations of inflow during the year, the relationship between storage volume and discharge is usually variable over time.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb6.png|thumb|Figure 6: Comparison of a pool-based operating plan in a two- and three-dimensional representation]] Like for the previous rules, the output depends on the storage volume. Usually, a pool-based operating plan is displayed in two-dimensional diagrams. The X-axis shows the time of one year, while the Y-axis shows the storage capacity. Pool-based operations are depicted as lines of equal outputs.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb7.png|thumb|Figure 7: Pool-based operating plan with linear interpolation between successive time reference points]]This view is practical but not yet complete: A three-dimensional representation of a simple pool-based operating plan makes this clear. On the X-axis is the time, on the Y-axis the storage capacity is plotted, while the Z-axis shows the output directed upwards.&lt;br /&gt;
&lt;br /&gt;
:The 3D image viewed from above gives the two-dimensional shape. Instead of taking constant blocks for the individual time horizons, a linear connection is also used often.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb8.png|thumb|Figure 8: Pool-based operating plan with two types of interpretation (selected month of May)]]For the individual periods - here months - different functional dependencies between storage capacity and outflow are considered. If the storage volume/discharge relation is also considered for a selected point in time, there are two possibilities to connect the discharge nodes. On the one hand, there is the possibility of linear interpolation, and on the other hand, a step function is possible.&lt;br /&gt;
&lt;br /&gt;
:In two-dimensional space, this information is not visible and must be specified separately. However, there is usually the convention to assume that the output between two nodes is constant, i.e. to interpret the pool-based operating plan as shown above in the form of steps.&amp;lt;br clear=&amp;quot;all&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 5: Maintaining Defined Discharges to Downstream Waters (Increase of Low Water / Coverage of Demand)==&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb9.png|thumb|Figure 9: Example of a function between shortfalls and scaling factors for a storage&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
* Dependency: &lt;br /&gt;
:In this case, the current discharge is determined by conditions downstream of a storage. At a cross-section of a water resources system, the so-called &#039;&#039;control point&#039;&#039;, where the flow is dependent on the discharge from the upstream storage, a minimum flow is defined. The flow at the control point is composed of the discharge from upstream storages and the lateral inflows between the storages and the control point. If the current flow remains below the set minimum, an additional discharge from upstream storages is necessary. The volume of the additional discharge depends on the difference between the previously defined target flow and the actual flow. Whether the required discharge can be fully provided from the storage depends on the currently available stored volumes in the storage. The lower the level, the less favorable it is to provide additional water. In this context, the increase of low water/coverage of demand behaves completely identical to the drinking or service water withdrawal, with only the triggering factor differing. As mentioned before, a storage-dependent function is scaled by a factor, but this factor is now derived from a comparison between set values and current discharges.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:The determination of the additionally needed discharge is composed of several factors. Firstly, a volumetrically varying shortfall of water results from failing the target discharge. The shortfall of water is then implemented as a scaling factor to the discharge which can be defined by a function. The shortfall of water functions independently, while the scaling factor functions dependently.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb10.png|thumb|Figure 10: Example of a function for increasing low water levels or meeting demand]]&lt;br /&gt;
&lt;br /&gt;
:Secondly, it depends on the actual storage volume, if and how an additional discharge from the storage can be met. A normalized volume-dependent function and the needed discharge lead to a clear determination of the additional discharge volumes. The following [[:Datei:Theorie_Abb10.png||Fig. 10]] shows an example, where the complete provision of an increased target can only be achieved if the filling level of the storage is above a critical limit (25%).&lt;br /&gt;
&lt;br /&gt;
:If more than one storage has an influence on the relevant control point or if, in principle, more than one storage facility is to be used to meet the demand, the required additional discharge is to be divided between the storages in accordance with the corresponding regulations. A distinction must be made between the direct and indirect influences of a storage on the control point. A direct influence is present if a discharge can have a direct effect on the flow conditions at the control point, i.e. the natural flow between the storage &lt;br /&gt;
and the control point can no longer be changed by regulation. If this is not the case, an indirect influence is given.&lt;br /&gt;
&lt;br /&gt;
:All storages with a direct influence on the control point receive a shortfall factor and a volume-dependent, scalable function according to [[:Datei:Theorie_Abb10.png|Figure 10]]. Thus, depending on the shortfall quantities and the storage capacity, the actual discharge can be determined separately for each storage.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 6: Discharge Depending on the storage Inflow==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb11.png|thumb|Figure 11: Direct dependency between storage and control point]]&lt;br /&gt;
:There is a direct dependency between the discharge from the storage and the current inflow to the storage. Similar to the pool-based operating plan, there is also an adaptation to different inflow situations. This is done to prevent depletion or overflowing or to obtain a variable discharge regime downstream. However, long-term inflow fluctuations are difficult to detect with this operating rule, since the observations are only carried out as snapshots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:To determine an inflow-dependent discharge, several components have to be considered. First of all, a relation between the current inflow and discharge must be defined. In addition to the current inflow, the current storage volume is important, because the relation inflow/outflow must not be valid for every filling level. Thus it is likely that the relation is ceded completely or the release quantities are adjusted if the storage level falls below a critical level.&lt;br /&gt;
&lt;br /&gt;
:As this rule can lead to the co-occurrence of relatively small storage volumes and high inflows resulting in high discharge volumes, special attention must be paid to the basic principle of checking the physical limits.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb12.png|thumb|Figure 12: Example of functions for inflow-dependent discharge]]&lt;br /&gt;
:In this case, three functional dependencies play a part. First, there is a direct dependency between the current inflow and the discharge. The form of the function can be arbitrary. It is possible to reproduce only individual sections of the inflow, which corresponds to a partial approximation of the discharge to the duration curve of the inflow.&lt;br /&gt;
&lt;br /&gt;
:Second, the inflow/discharge function can be superposed with the relationship between storage volume and discharge. For reasons of clarity, it is recommended to work with a normalized function. This makes it possible to influence the result of the inflow/discharge function for each storage volume, which is especially convenient for low filling levels.&lt;br /&gt;
&lt;br /&gt;
:Finally, the required discharge has to be checked with regard to the outlet elements&#039; capacity.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb13.png|thumb|left|Figure 13: Results of different inflow-dependent release strategies]]&lt;br /&gt;
&lt;br /&gt;
:The examples below show how the interaction of different functions affects the discharges. The results are compared in the following figures as inflow and discharge duration lines.&lt;br /&gt;
&lt;br /&gt;
:In the case of a linear relation between inflow and discharge and a constant factor for the storage volume, the duration line of the discharge is a curve corresponding to the inflow reduced by a certain percentage. If the storage volume factor remains constant, the duration line can be changed by varying the inflow/discharge relationship. An additional modification of the factor via the storage volume has the advantage of being able to respond to certain filling levels to prevent the storage from emptying or overflowing.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 7: Influence of Discharges Trough System States==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:Rule 7, just as rule 6, is a continuation and generalization of the increase of low water as described in rules 5. Just like a discharge deficit at a cross-section or the storage inflow can influence the discharge, any other system state can. In general terms, this means that a discharge from a storage is triggered, increased, or reduced due to a certain system state. Basically, it is irrelevant where the system state occurs. All measurable variables that influence the transport and storage of water can be considered as system states, e.g. the filling of other storages, discharges, flow regime at a cross-section, a snow depth in the catchment area, current precipitation, or current soil moisture.&lt;br /&gt;
&lt;br /&gt;
:As a requirement to apply those dependencies a detection of the system state is necessary. Practically, this means either that a measuring device must be available to determine needed parameters or the required values are calculated using a mathematical model. Parameters are only considered as snap-shots and not continuously.&lt;br /&gt;
&lt;br /&gt;
:If several system states should influence the discharge, a superposition of the parameters according to a corresponding regulation is necessary.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction:&lt;br /&gt;
:Mathematically, the influence of system states on the discharge can always be undertaken by scaling. Two functions are necessary for this. The first function describes the relationship between storage volume and discharge. The second one controls the dependency between the system state and a scaling factor. The connection is done by multiplying the discharge with the scaling factor.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb13.5.png|thumb|Transition]]&lt;br /&gt;
&lt;br /&gt;
:A simple example is given by a transition from storage A to storage B. &lt;br /&gt;
&lt;br /&gt;
:The decisive discharge is the transition from A to B. The considered system state is the storage volume of B. It seems obvious that a discharge from A to B is only useful if storage A has sufficient provision and storage B has sufficient capacity to hold additional water. This results in the following simple functions:&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb14.png|thumb|left|Figure 14: Example functions for linking a system state to a discharge]]Reservoir B takes 100% of the discharge from A as long as its filling level does not reach 70% of the maximum volume. Furthermore, it is undesirable to receive additional water for flood protection reasons. The scaling factor decreases from 70% filling level to zero. Starting at a filling level above 50% it becomes increasingly easy to transfer water from Reservoir A to reservoir B. The actual transfer, however, only results from the interaction of both functions, taking into account the current filling level of reservoir B and the scaling derived from it.&lt;br /&gt;
&lt;br /&gt;
:For storage A, the definition of the discharge is in m³/s, while the function for storage B receives a unitless scaling factor. In principle, however, it is possible to exchange the meaning of the functions and to use a unitless function for storage A to scale the desired transfer volume for storage B.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 8: Influencing a Discharge with Balances==&lt;br /&gt;
&lt;br /&gt;
 Dependency: [[Datei:Theorie_Abb15.png|thumb|Figure 15 : Example of long-term monthly averages and moving 30 day averages of storage volumes]]&lt;br /&gt;
:This rule is an extension of rule 7. Instead of using a current state parameter, the balance of a system state is linked to discharge. It is important that there are set time boundaries for carrying out the balance. However, it is irrelevant whether the balance is interpreted as a sum or as an average. A function that displays scaling factors depending on the actual balance can then be used to influence discharges.&lt;br /&gt;
&lt;br /&gt;
:In practice, this form of dependency is often found where water rights define maximum withdrawal volumes per time unit. But the application of a balance is also interesting regarding the long-term behaviour of storage filling levels or inflows. For example, a discharge could be reduced to build up provisions if the inflow of the past winter half-year was below a defined expected value. Another application is the comparison between long-term and current moving averages of storage filling levels. If the current values deviate from the long-term values by a certain amount, the discharge can be reduced or increased to compensate.&lt;br /&gt;
&lt;br /&gt;
:If linking a discharge to several balances is desired, it is possible to superpose several balances (see example at the end of this chapter). &lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb16.png|thumb|Figure 16: Example of a rule for standard discharge]]&lt;br /&gt;
:The influence of the balance on the discharge is posed by two functions according to rule 7. In addition to the already necessary storage volume/discharge function, there is a relation between the balance and scaling factor. The scaling factor is taken from the difference between the actual balance and the expected value.&lt;br /&gt;
&lt;br /&gt;
:The method is demonstrated with a simple example of a standard discharge.&lt;br /&gt;
&lt;br /&gt;
:For storage A, long-term monthly mean values of the storage volumes and derived sliding 30-day mean values of the storage filling levels, as well as the rule for the standard discharge, are known.&lt;br /&gt;
&lt;br /&gt;
:If, for example, on May 1st the average value of the storage volume calculated from the last 30 days amounts to 5.6 million m³ and thus, according to [[:Datei:Theorie_Abb15.png|Fig. 15]], it deviates by 30% from the long-term average value of 8 million m³, a scaling factor of 0.5 results (see [[:Datei:Theorie_Abb16.png|Fig. 16]]). With this value, the standard discharge is reduced and delivers only 0.25m³/s at a current storage filling level of 40%, i.e. 50% less than intended.&lt;br /&gt;
&lt;br /&gt;
:[[Datei:Theorie_Abb17.png|thumb|left|Abbildung 17: Example functions to link a water balance with a discharge]]The relation between the deviation of the balance and the scaling factor indicates that only starting from a difference greater than 20% a change of the standard discharge takes place. In the case of a decrease of more than 20%, the standard discharge is reduced stepwise. If the actual moving 30-day average exceeds the long-term values by more than 20%, the standard discharge is increased continuously.&lt;br /&gt;
&lt;br /&gt;
:In general, there is also the possibility to extend the relation by superposing and combining several water balances.&lt;br /&gt;
&lt;br /&gt;
:The interaction between water balance and discharge function is explained below.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Rule Type 9: Priorities for Competing Discharges from a Reservoir==&lt;br /&gt;
&lt;br /&gt;
* Dependency: [[Datei:Theorie_Abb18.png|thumb|Figure 18: Example for assigning priorities via the position of functions]]&lt;br /&gt;
:If there are several discharges from a reservoir, it can occur that it is not possible to carry out all demanded discharges. In such a case, priorities need to be specified, which determine an order in which discharges are to be satisfied. The order of priorities is often a consequence of political decisions and is not subject to physical conditions.&lt;br /&gt;
&lt;br /&gt;
:However, there are some priorities based on physical conditions. An example is turning off a turbine in times of water shortage in favor of securing the water supply. In practice, operating rules often meet this problem by fulfilling demands up to defined reservoir volumes, but not maintaining discharges below the set reservoir volume.&lt;br /&gt;
&lt;br /&gt;
:Another way to describe priorities is to reduce a discharge A exactly by an amount, which is resulting from a second discharge B, with the discharge A never being smaller than zero.&lt;br /&gt;
&lt;br /&gt;
* Practical example:&lt;br /&gt;
:The Wiehl dam gives a good example for the practical operating conditions of a dam. The Wiehl dam serves primarily as a drinking water supply and a means for flood protection, and secondarily for energy production. In addition, a minimum flow of 100 l/s has to be guaranteed downstream of the Wiehl dam. The first priority is the drinking water supply. In order to ensure sufficient water quality in the reservoir, additional discharges used for energy production are stopped when the reservoir volume falls below 70% of the total volume. As both the minimum discharge and the turbine discharge leave into the Wiehl, it would also be uncalled-for to maintain the minimum discharge if water was simultaneously discharged through the turbine. This results in a reduction of a discharge A (minimum discharge) by the amount of discharge B (turbine) as described above &amp;lt;ref name=&amp;quot;Aggerverband_1999&amp;quot;&amp;gt;&#039;&#039;&#039;Aggerverband&#039;&#039;&#039; (1999): Hydrologische Sicherheit der Genkel- und Aggertalsperre. Gutachten des Fachgebietes Ingenieurhydrologie und Wasserbewirtschaftung, TU Darmstadt&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: [[Datei:Theorie_Abb19.png|thumb||Figure 19: Example of a relation between two discharges]]&lt;br /&gt;
:Assuming that for each use, following the above rules, a functional dependency between reservoir content and discharge exists, a ranking of several uses is already given by the position of the function&#039;s nodes.  Then, the respective reservoir volume from which the target discharge is no longer covered to 100% or even reduced to zero is decisive.&lt;br /&gt;
&lt;br /&gt;
:In the example, the ranking of the uses is clearly visible. First, the turbine is switched off, then the increase of low water refrained from until only the discharge covering the water supply remains.&lt;br /&gt;
&lt;br /&gt;
:In addition, it is possible to directly compare two or more discharges. Such a rule could be:&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;If discharge B &amp;gt; 0 and the reservoir volume S &amp;lt; X, then reduce discharge A by the amount of discharge B, with discharge  A not being smaller than zero.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:This means that a linear dependency exists between A and B until B is equal to the value of A. If B increases further, A remains constantly zero.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Rule Type 11: Water Distribution==&lt;br /&gt;
&lt;br /&gt;
* Dependency:&lt;br /&gt;
:If there is the need to distribute water within a water resources system, a distribution rule must be defined.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb19.5.png|thumb|Diversion]]&lt;br /&gt;
&lt;br /&gt;
:Two types of diversions can occur:&lt;br /&gt;
:# Diversion that exclusively follows hydraulic laws &lt;br /&gt;
:# Adjustable diversions &lt;br /&gt;
&lt;br /&gt;
:In both cases, relations can always be defined as a function of the inflow. In the second case, these distribution rules represent an operating rule, since they directly influence the transport and storage behavior of water. The number of discharges is basically not limited. The difference to transitions at dams is that in this case no reservoir volume can be used as a reference value.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb20.png|thumb|Figure 20 :Example of assignment functions for multiple sequences]]&lt;br /&gt;
&lt;br /&gt;
* Practical example: &lt;br /&gt;
:The water supply of Windhoek, the capital of Namibia, is provided by three dams. However, the water withdrawal for the drinking water supply is only possible from one dam - the Von Bach Dam. The remaining two reservoirs are connected to the main dam by pipes. However, the volume transferred between Swakopport Dam and Von Bach Dam is not exclusively available for refilling the Von Bach Dam, but also serves to supply the town of Karibib with drinking water.&lt;br /&gt;
&lt;br /&gt;
* Mathematical abstraction: &lt;br /&gt;
:[[Datei:Theorie_Abb21.png|thumb|left|Fig. 21: Example of a threshold concept for a division into two flows]]For the definition of division rules, functions depending on the current inflow are an appropriate representation. Thus, both a hydraulic description and a description serving the management of the storage are possible. For each discharge leaving the diversion structure, a distribution function has to be specified. If the functions are to be variable, scaling is recommended.&lt;br /&gt;
&lt;br /&gt;
[[Datei:Theorie_Abb22.png|thumb|Figure 22: Example of a threshold concept with a distribution to serve several users&lt;br /&gt;
]]&lt;br /&gt;
&lt;br /&gt;
:If the distribution functions cannot be pre-defined, but the discharge volumes rather result later from demand calculations, then a threshold concept is suitable, which in turn can work with scaling factors. The threshold is scaled by a factor and is therefore variable. As long as the inflow is lower than the threshold, the entire inflow is used to satisfy the demand. Only when the current inflow exceeds the threshold, the remaining amount is discharged.&lt;br /&gt;
&lt;br /&gt;
:If a division into more than two discharges is necessary, the threshold concept can be successively applied several times. The order of the discharges determines the priorities of the water distribution.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Literature==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
	<entry>
		<id>https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/66/en&amp;diff=12951</id>
		<title>Translations:Betriebsregeltypen/66/en</title>
		<link rel="alternate" type="text/html" href="https://www.talsim.de/docs/index.php?title=Translations:Betriebsregeltypen/66/en&amp;diff=12951"/>
		<updated>2021-08-30T10:33:50Z</updated>

		<summary type="html">&lt;p&gt;Haghani: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;:If, for example, on May 1st the average value of the storage volume calculated from the last 30 days amounts to 5.6 million m³ and thus, according to [[:Datei:Theorie_Abb15.png|Fig. 15]], it deviates by 30% from the long-term average value of 8 million m³, a scaling factor of 0.5 results (see [[:Datei:Theorie_Abb16.png|Fig. 16]]). With this value, the standard discharge is reduced and delivers only 0.25m³/s at a current storage filling level of 40%, i.e. 50% less than intended.&lt;/div&gt;</summary>
		<author><name>Haghani</name></author>
	</entry>
</feed>