Sie sind auf Seite 1von 18

3.2.

1 Quick start tutorial


A simple case can be performed following the steps below:
1) Start the project by creating the new project preferences file: File New project
preferences
2) Select the Water software: EPANET
3) Select the Data storage: Database
4) Configurate the connection parameters
5) Create a new project data scheme: Fill the project name,the project title and select the
SRID.
6) Create the GIS project: Fill in the information for project folder and project name.Also
choose the water software and the data storage (in this case EPANET and data storage), and
finally select the scheme name necessary.
7) Click on Accept on the Project Preferences menu
8) Select US or metric units: Options flow units. Choosing US flow unit; this means that
all other quantities of the project will be expressed in US units, while choosing a metric flow
unit will force all quantities to be expressed in metric units.
8) Complete the material catalogue at least with one record: Material catalog. The default
formula used for computing head loss for flow through a pipe is Hazen-Williams (H-W). It
can be seen that in the EPANET's user manual,it explains how to determine the roughness
value. In addition, this can be changed to the Head loss formula from: Options Head loss.
9) Open GIS project and build the network which should contain the next layers:
GIS PROJECT Sector. You must create at least one sector.
EPANET DATA Hydraulics - Node - Reservoirs. You must create and edit at least one
reservoir. See APPENDIX C EPANET users manual (JUNCTIONS and RESERVOIRS
target) for more information.
EPANET DATA Hydraulics Node - Junctions. You must create and edit the junction
records of your network. See APPENDIX C EPANET users manual (JUNCTIONS target)
for more information.
EPANET DATA Hydraulics - Arc - Pipes. You must create and edit the pipe records of your
network (joining the different nodes). See APPENDIX C EPANET users manual (PIPES
target) for more information.
10) Configure INP file additional parameters. You can define how many sectors will be
simulated: Sector selection, and configure the simulation options, times and report data:
Options / Times / Report.

11a) Generate INP file: export INP checkbox. In this way, Giswater driver will create a text
file (inp extension) stored on the selected folder.
11b) Execute the command line EPANET: Execute EPA software checkbox. Giswater will
execute the command line EPANET file with the inp file, and EPANET will generate two
result files (*.rpt file and *.out file.) stored on the selected folder.
11c) Import Results (optional): Import results check box. Giswater will read the result data
stored on rpt file and will write the values on the schema result tables with the project name
selected.
12) Returns to the GIS project and enjoy the simulation's results on the different shapes and
tables of SIMULATION ANALYSIS.
Key relations between features and tables should be mentioned at this point.
First of all, the key relations from ARC and NODE to other tables are defined as 'on delete
cascade on update cascade.' This means that if you delete one feature from these tables, all
related features from other tables will be deleted. On the other hand if you update values from
these tables, values in all related features will be updated in cascade too.
Further, key relations from SECTOR and MATERIAL are defined 'on delete restrict on
update cascade'. This is quite different from the previous one, because it means that you can
not delete used features from these tables. On the other hand, if you update values from these
tables, values in all related features will be updated in cascade too.
The rest of features do not have relations. Elements as EMITTERS, ENERGY, STATUS,
CONTROLS, RULES, DEMANDS, CURVES, PATTERNS, QUALITY, REACTIONS,
SOURCES, MIXING do not have key relations from theirs to other tables. In this way you
must know that If you update features, the values will not be updated on related tables (if they
exist) and if you delete features, mentioned on related tables will not be deleted (if they exist
too).
his provides a tutorial on how to use Giswater with EPANET on DBF data storage. In order to
activate this data storage mode: Project preferences Data storage: DBF
WARNING: Full capabilities are not allowed on DBF storage mode !!!

Arc
Arc geometries (pipes, valves and pumps)
arc_id: ID label.
node_1: ID of start node.

node_2: ID of end node.


diameter: Pipe diameter in inches (mm).
matcat_id: Material as stated in the catalog of materials.
enet_type: Arc type as EPANET.
sector_id: The code sector where is the space object.

Node
Node geometries (junction, reservoir or tank)
node_id: ID label.
elevation: The spot elevation node. Ft (m)
enet_type: Node type as EPANET.
sector_id: Sector where there is the node.
Sector
Defines the network sectors. You must need minimun at once.
sector_id: Code sector.
descript: Description of the sector.
Backdrop
Identifies a backdrop image and dimensions for the network EPANET map.
id: Defines the order of the line text. You must to use this code in order to sort as you need
the lines of text. As you sort the text lines Giswater reads by this order the information. See
definition and remark's section for more information.
text: Text options Backdrop.
Definitions:
DIMENSIONS provides the X and Y coordinates of the lower-left and upper-right corners of
the maps bounding rectangle. Defaults are the extents of the nodal coordinates supplied in
your Gis project selection.
UNITS specifies the units that the maps dimensions are given in
(FEET/METERS/DEGREES/NONE). Default is NONE.
FILE is the name of the file that contains the backdrop image.

OFFSET lists the X and Y distance that the upper-left corner of the backdrop image is offset
from the upper-left corner of the maps bounding rectangle. Default is zero offset.
Remarks:
a. The [BACKDROP] table is optional and is not used at all when EPANET is run as a
console application.
b. Only Windows Enhanced Metafiles and bitmap files can be used as backdrops.
Junction
Defines junction nodes contained in the network.
node_id: ID label.
elevation: The spot elevation junction. (ft or m).
demand: Base demand (flow units). This field is optional.
pattern_id: Demand pattern ID. This field is optional.
sector_id: Sector where there is the junction.
Remarks
a. At least one juction is required
b. If no demand pattern is supplied then the junction demand follows the Default Demand
Pattern specified in the [OPTIONS] parameteres or Pattern 1. If the default pattern (or Pattern
1) does not exist, then the demand remains constant.
c. Demands can also be entered in the [DEMANDS] table and include multiple demand
categories per junction.
Reservoir
Defines all reservoir nodes contained in the network.
node_id: ID label.
elevation: The spot elevation reservoir. Ft (m).
head: Head, ft (m).
pattern_id: Head pattern ID. This field is optional
sector_id: The sector where there is the reservoir.
Remarks:
a. Head is the hydraulic head (elevation + pressure head) of water in the reservoir.
b. A head pattern can be used to make the reservoir head vary with time.
c. At least one reservoir or tank must be contained in the network.

Source
Defines locations of water quality sources.
node_id: ID label.
sourc_type: Source type (CONCEN, MASS, FLOWPACED, or SETPOINT).
quality: Baseline source strength.
pattern_id: Time pattern ID.
Remarks:
a. For MASS type sources, strength is measured in mass flow per minute. All other types
measure source strength in concentration units.
b. Source strength can be made to vary over time by specifying a time pattern.
c. A CONCEN source:
represents the concentration of any external source inflow to the node
applies only when the node has a net negative demand (water enters the network at the node)
if the node is a junction, reported concentration is the result of mixing the source flow and
inflow from the rest of the network
if the node is a reservoir, the reported concentration is the source concentration
if the node is a tank, the reported concentration is the internal concentration of the tank
is best used for nodes that represent source water supplies or treatment works (e.g., reservoirs
or nodes assigned a negative demand)
should not be used at storage tanks with simultaneous inflow/outflow.
d. A MASS, FLOWPACED, or SETPOINT source:
represents a booster source, where the substance is injected directly into the network
irregardless of what the demand at the node is
affects water leaving the node to the rest of the network in the following way:
- a MASS booster adds a fixed mass flow to that resulting from inflow to the node
- a FLOWPACED booster adds a fixed concentration to the resultant inflow concentration at
the node
- a SETPOINT booster fixes the concentration of any flow leaving the node (as long as the
concentration resulting from the inflows is below the setpoint)
the reported concentration at a junction or reservoir booster source is the concentration that
results after the boosting is applied; the reported concentration for a tank with a booster
source is the internal concentration of the tank
is best used to model direct injection of a tracer or disinfectant into the network or to model a
contaminant intrusion.
e. A [SOURCES] table is not needed for simulating water age or source tracing.

Tank
Defines all tank nodes contained in the network.
node_id: Node ID label.
elevation: Bottom elevation. (ft or m).

initlevel: Initial water level. (ft or m).


minlevel: Minimum water level. (ft or m).
maxlevel: Maximum water level. (ft or m).
diameter: Nominal diameter. (ft or m).
minvol: Minimum volume. (cubic ft or cubic meters).
curve_id: Volume curve ID.
sector_id: Sector where there is the tank.
Remarks:
a. Water surface elevation equals bottom elevation plus water level.
b. Non-cylindrical tanks can be modeled by specifying a curve of volume versus water depth
in the [CURVES] table.
c. If a volume curve is supplied the diameter value can be any non-zero number
d. Minimum volume (tank volume at minimum water level) can be zero for a cylindrical tank
or if a volume curve is supplied.
e. A network must contain at least one tank or reservoir.

Mixing
Identifies the model that governs mixing within storage tanks.
node_id: ID label.
mix_type: Mixing model (MIXED, 2COMP, FIFO or LIFO).
value: Options value parameters of EPANET project.
Remarks:
a. Mixing models include:
Completely Mixed (MIXED)
Two-Compartment Mixing (2COMP)
Plug Flow (FIFO)
Stacked Plug Flow (LIFO)
b. The compartment volume parameter only applies to the two-compartment model and
represents the fraction of the total tank volume devoted to the inlet/outlet compartment.
c. The [MIXING] table is optional. Tanks not described in this table are assumed to be
completely mixed.

Emitter
Defines junctions modeled as emitters (sprinklers or orifices).
node_id: ID label.
coef: Flow coefficient, flow units at 1 psi (1 meter) pressure drop.
Remarks:
a. Emitters are used to model flow through sprinkler heads or pipe leaks.
b. Flow out of the emitter equals the product of the flow coefficient and the junction pressure
raised to a power.
c. The power can be specified using the EMITTER EXPONENT option in the option
parameters. The default power is 0.5, which normally applies to sprinklers and nozzles.
d. Actual demand reported in the program's results includes both the normal demand at the
junction plus flow through the emitter.
e. An [EMITTERS] table is optional.

Demand
Replace to [JUNCTION] feature for defining multiple water demands at junction nodes.
WARNING: If this junction values are used the value of [JUNCTION] is ignored.
id: Row id. Unique value needed.
node_id: Junction ID label.
demand: Base demand (flow units).
pattern_id: Demand pattern ID.
deman_type: Name of demand category preceded by a semicolon.
Remarks:
a. Only use for junctions whose demands need to be changed or supplemented from entries in
[JUNCTION] feature.
b. Data in this section replaces any demand entered in [JUNCTION] feature for the same
junction.
c. Unlimited number of demand categories can be entered per junction.
d. If no demand pattern is supplied then the junction demand follows the Default Demand
Pattern specified in the [OPTIONS] option parameters or Pattern 1 if no default pattern is
specified. If the default pattern (or Pattern 1) does not exist, then the demand remains
constant.
Pipe
Defines all pipe links contained in the network.
arc_id: ID label.

diameter: Diameter. (inches or mm).


matcat_id: Material as stated in the catalog of materials.
minorloss: Minor loss coefficient.
status: Status (OPEN, CLOSED or CV)
sector_id: Sector where there is the pipe.
Remarks:
a. Roughness coefficient is unitless for the Hazen-Williams and Chezy-Manning head loss
formulas and has units of millifeet (mm) for the Darcy-Weisbach formula. Choice of head
loss formula is supplied in the [OPTIONS] option parameters.
b. Setting status to CV means that the pipe contains a check valve restricting flow to one
direction.
c. If minor loss coefficient is 0 and pipe is OPEN then these two items can be dropped form
the input line.
Pump
Defines all pump links contained in the network.
arc_id: ID label of pump.
diameter: Diameter in inches or mm.
matcat_id: Material as stated in the catalog of materials.
power: Write it POWER, leave a space and write the value of power. (Power value for
constant energy pump, hp (kW))
curve_id: ID label.
speed: Write it SPEED, leave a space and write the value of speed. (Relative speed setting
(normal speed is 1.0, 0 means pump is off))
pattern: Write it PATTERN, leave a space and write the value of pattern. (ID of time pattern
that describes how speed setting varies with me)
sector_id: Sector where there is the pump.
Remarks:
a. Keywords consists of:
POWER power value for constant energy pump, hp (kW)
HEAD - ID of curve that describes head versus flow for the pump
SPEED - relative speed setting (normal speed is 1.0, 0 means pump is off)
PATTERN - ID of time pattern that describes how speed setting varies with time
b. Either POWER or HEAD must be supplied for each pump. The other keywords are
optional.

Valve
Defines all control valve links contained in the network.
arc_id: ID label of valve.
diameter: Diameter in inches or mm.
matcat_id: Material as stated in the catalog of materials.
valv_type: Valve type (see remarks)
pressure: Pressure in psi or m.
flow: Flow (flow units)
coef_loss: Loss coefficient.
curve_id: ID of head loss curve
minor_loss: Minor loss coefficient
status: Valve status (see remarks).
sector_id: Sector where there is the valve.
Remarks:
a. Valve types and settings include:
Valve type

Setting

PRV (pressure reducing valve) Pressure, psi (m)


PSV (pressure sustaining
valve)

Pressure, psi (m)

PBV (pressure breaker valve) Pressure, psi (m)


FCV (flow control valve)

Flow (flow units)

TCV (throttle control valve)

Loss Coefficient

GPV (general purpose valve)

ID of head loss curve

b. Shutoff valves and check valves are considered to be part of a pipe, not a separate control
valve component (see [PIPE])
c. The status value can be OPEN or CLOSED. For control valves (e.g., PRVs, FCVs, etc.)
this means that the valve is either fully opened or closed, not active at its control setting.

d. The setting value can be a speed setting for pumps or valve setting for valves.
e. Check valves cannot have their status be preset.
f. If a CLOSED or OPEN control valve is to become ACTIVE again, then its pressure or flow
setting must be specified in the control or rule that re-activates it.
Controls
Defines simple controls that modify links based on a single condition.
id: Defines the order of the line text. You must to use this code in order to sort as you need
the lines of text. As you sort the text lines Giswater reads by this order the information.
text: Controls text (See the example below).
Example:
;Close Link 12 if the level in Tank 23 exceeds 20 ft.
LINK 12 CLOSED IF NODE 23 ABOVE 20
;Open Link 12 if pressure at Node 130 is under 30 psi
LINK 12 OPEN IF NODE 130 BELOW 30
Remarks:
a. Simple controls are used to change link status or settings based on tank water level,
junction pressure, time into the simulation or time of day.
b. See the notes for the [STATUS] parameter in value domain for conventions used in
specifying link status and setting, particularly for control valves.
Rules
Defines rule-based controls that modify links based on a combination of conditions.
id: Defines the order of the line text. You must to use this code in order to sort as you need
the lines of text. As you sort the text lines Giswater reads by this order the information.
text: Defines rule-based controls that modify links based on a combination of conditions.
Example:
RULE 1
IF TANK 1 LEVEL ABOVE 19.1
THEN PUMP 335 STATUS IS CLOSED AND PIPE 330 STATUS IS OPEN
Remarks:
a. Only the RULE, IF and THEN portions of a rule are required; the other portions are
optional.
b. When mixing AND and OR clauses, the OR operator has higher precedence than AND,
i.e.,
IF A or B and C
is equivalent to
IF (A or B) and C.
If the interpretation was meant to be

IF A or (B and C)
then this can be expressed using two rules as in
IF A THEN ...
IF B and C THEN ...
c. The PRIORITY value is used to determine which rule applies when two or more rules
require that conflicting actions be taken on a link. A rule without a priority value always has a
lower priority than one with a value. For two rules with the same priority value, the rule that
appears first is given the higher priority.
Curve
Defines data curves and their X,Y points.
id: Defines the order of the line text. You must to use this code in order to sort as you need
the lines of text. As you sort the text lines Giswater reads by this order the information.
curve_id: Name assigned to table.
x_value: An x (independent variable) value.
y_value: An y (independent variable) value.
Remarks:
a. Curves can be used to represent the following relations:
Head v. Flow for pumps
Efficiency v. Flow for pumps
Volume v. Depth for tanks
Headloss v. Flow for General Purpose Valves
b. The points of a curve must be entered in order of increasing X-values (lower to higher).
c. If the input file will be used with the Windows version of EPANET, then adding a
comment which contains the curve type and description, separated by a colon, directly above
the first entry for a curve will ensure that these items appear correctly in EPANETs Curve
Editor. Curve types include PUMP, EFFICIENCY, VOLUME, and HEADLOSS.
Pattern
Defines time patterns.
pattern_id: Pattern ID label.
factor_1: Pattern value (one or more multipliers).
factor_2: Pattern value (one or more multipliers)
factor_3: Pattern value (one or more multipliers)
...
factor_24: Pattern value (one or more multipliers)

Remarks:
a. Multipliers define how some base quantity (e.g., demand) is adjusted for each time period.
b. All patterns share the same time period interval as defined in the [TIMES] table.
c. Each pattern can have a different number of time periods.
d. When the simulation time exceeds the pattern length the pattern wraps around to its first
period.
e. Use as many lines as it takes to include all multipliers for each pattern.
Curve catalog
Curve catalog.
id: Defines the order of the line text. You must to use this code in order to sort as you need
the lines of text. As you sort the text lines Giswater reads by this order the information. See
definition and remark's section for more information.
curve_type: Curve types include PUMP, EFFICIENCY, VOLUME, and HEADLOSS.
Quality
Describes the contents of the output report produced from a simulation.
node_id: ID label.
initqual: Initial quality.
Remarks:
Selects the type of water quality analysis to perform. The choices are NONE, CHEMICAL,
AGE, and TRACE. In place of CHEMICAL the actual name of the chemical can be used
followed by its concentration units (e.g., CHLORINE mg/L). If TRACE is selected it must be
followed by the ID label of the node being traced. The default selection is NONE (no water
quality analysis).
Global energy
Defines global parameters -for all pumps- used to compute pumping energy and cost.
energ_type: Energy type. Must be GLOBAL or DEMAND CHARGE
parameter: Options parameters. See below
value: Values for the selected parameter.
Remarks:
Parameters are defined as follows:
If you select GLOBAL, Parameters are defined as follows:
PRICE: average cost per kW-hour
PATTERN: ID label of time pattern describing how energy price varies with time.
EFFIC: either a single percent efficiency for global setting or the ID label of an efficiency
curve for a specific pump.

If you select DEMAND CHARGE, parameter remain on blank and directly you can fill data
on value field.
The default global pump efficiency is 75% and the default global energy price is 0.
Single energy
Defines parameters used to compute pumping energy and cost (by specified pump)
pump_id: ID label.
parameter: Options parameters. Must be PRICE, PATTERN or EFFIC
value: Value of the parameter selected
Remarks
Parameters are defined as follows:
PRICE: average cost per kW-hour
PATTERN: ID label of time pattern describing how energy price varies with time.
EFFIC: either a single percent efficiency for global setting or the ID label of an efficiency
curve for a specific pump.
The default global pump efficiency is 75% and the default global energy price is 0.

Global reactions
Defines global parameters -for all elements- related to chemical reactions occurring in the
network.
react_type: Reaction type. Must be ORDER or GLOBAL (see below)
parameter: Options parameters. Must be BULB, WALL, TANK, LIMITING POTENCIAL or
ROUGHNESS CORRELATION
value: Value of the specified parameter
Remarks:
ORDER is used to set the order of reactions occurring in the bulk fluid, at the pipe wall, or in
tanks, respectively. Values for wall reactions must be either 0 or 1. If not supplied the default
reaction order is 1.0.
GLOBAL is used to set a global value for all bulk reaction coefficients (pipes and tanks) or
for all pipe wall coefficients. The default value is zero.
BULK, WALL and TANK are used to override the global reaction coefficients for specific
pipes and tanks.

For LIMITING POTENCIAL or ROUGHNESS CORRELATION fill blank the field


react_type
LIMITING POTENCIAL specifies that reaction rates are proportional to the difference
between the current concentration and some limiting potential value.
ROUGHNESS CORRELATION will make all default pipe wall reaction coefficients be
related to pipe roughness in the following manner:
Head Loss Equation

Roughness Correlation

Hazen-Williams

F/C

Darcy-Weisbach

F / log(e/D)

Chezy-Manning

F*n

a. Remember to use positive numbers for growth reaction coefficients and negative numbers
for decay coefficients.
b. The time units for all reaction coefficients are 1/days.
c. All entries in this section are optional. Items offset by slashes (/) indicate allowable
choices.
Single reactions
Defines individual parameters -specific for each element- related to chemical reactions
occurring in the network.
parameter: BULK, WALL or TANK. Used to override the global reaction coefficients for
specific pipes and tanks
arc_id: Element ID with specific chemical reaction.
value: Reaction coefficient vaules
Remarks:
a. Remember to use positive numbers for growth reaction coefficients and negative numbers
for decay coefficients.
b. The time units for all reaction coefficients are 1/days.
c. All entries in this section are optional. Items offset by slashes (/) indicate allowable
choices.
Value domain
Folder with tables used on other tables as value domain data. Gis projects uses this tables but
data is not updatable. You do not have to do anything, but you can not delete it.
Tags
Associates category labels (tags) with specific nodes and links on EPANET user inferface.

object: The keyword NODE or LINK.


node_id: The node or link ID label.
tag: The text of the tag label (with no spaces).
Remarks:
a. Tags can be useful for assigning nodes to different pressure zones or for classifying pipes
by material or age.
b. If a node or links tag is not identified in this section then it is assumed to be blank.
c. The [TAGS] table is optional and has no effect on the hydraulic or water quality
calculations.
Labels
Assigns coordinates to map labels on EPANET user inferface.
id: Defines the order of the line text. You must to use this code in order to sort as you need
the lines of text. As you sort the text lines Giswater reads by this order the information.
xcoord: Horizontal coordinate of vertex relative to origin in lower left of map.
ycoord: Vertical coordinate of vertex relative to origin in lower left of map.
label: Text of label in double quotes.
node_id: ID label.
Remarks:
a. Include one line for each label on the map.
b. The coordinates refer to the upper left corner of the label and are with respect to an
arbitrary origin at the lower left of the map.
c. The optional anchor node anchors the label to the node when the map is re-scaled during
zoom-in operations.
d. The [LABELS] table is optional and is not used at all when EPANET is run as a console
application.
Node minimum values
Node minimum values simulation analisys data.
node_id: ID label of node.
result_id: ID simulation result.
elevation: Elevation (ft or m).
max_demand: Maximum bse demand (flow units)
min_demand: Minimum base demand (flow units).

max_head: Maximum head (ft or m).


min_head: Minimum head (ft or m)
max_pressure: Maximum pressure (psi or m).
min_pressure: Minimum pressure (psi or m).
Node maximum values
Node simulation maximum values simulation analisys data.
node_id: ID label of node.
result_id: ID simulation result.
elevation: Elevation (ft or m).
max_demand: Maximum bse demand (flow units).
min_demand: Minimum base demand (flow units).
max_head: Maximum head (ft or m).
min_head: Minimum head (ft or m).
max_pressure: Maximum pressure (psi or m).
min_pressure: Minimum pressure (psi or m).
Arc minimum values
Arc minimum values simulation analisys data.
arc_id: ID label of arc.
result_id: ID simulation result.
max_flow: Maximum flow (flow units).
min_flow: Minimum flow (flow units).
max_vel: Maximum velocity (fps).
min_vel: Minimum velocity (fps).
max_headloss: Maximum headloss (/1000ft).
min_headloss: Minimum headloss (/1000ft).

max_setting: Maximum setting. (Roughness for pipes, speed for pumps, pressure/flow setting
for valves).
min_setting: Minimum setting. (Roughness for pipes, speed for pumps, pressure/flow setting
for valves).
max_reaction: Maximum reaction.
min_reaction: Minimum reaction.
max_ffactor: Maximum friction factor.
min_ffactor: Minimum friction factor.
Arc maximum values
Arc maximum values simulation analisys data.
arc_id: ID label of arc.
result_id: ID simulation result.
max_flow: Maximum flow (flow units).
min_flow: Minimum flow (flow units).
max_vel: Maximum velocity (fps).
min_vel: Minimum velocity (fps).
max_headloss: Maximum headloss (/1000ft).
min_headloss: Minimum headloss (/1000ft).
max_setting: Maximum setting. (Roughness for pipes, speed for pumps, pressure/flow setting
for valves).
min_setting: Minimum setting. (Roughness for pipes, speed for pumps, pressure/flow setting
for valves).
max_reaction: Maximum reaction.
min_reaction: Minimum reaction.
max_ffactor: Maximum friction factor.
min_ffactor: Minimum friction factor.
Energy usage values
Energy usage values simulation analisys data.

id: Defines the order of the line text. You must to use this code in order to sort as you need
the lines of text. As you sort the text lines Giswater reads by this order the information.
result_id: ID simulation result.
pump_id: ID label of pump.
usage_fact: Usage factor.
avg_effic: Average efficiency.
kwhr_mgal: Kw hr (/Mgal).
avg_kw: Average (Kw).
peak_kw: Peak (Kw)
cost_day: Cost (/day)
Hydraulic status
Hydraulic status values simulation analisys data.
id: Defines the order of the line text. You must to use this code in order to sort as you need
the lines of text. As you sort the text lines Giswater reads by this order the information.
result_id: ID simulation result.
time: 'Time'.
text: 'Text'.