InfoWater conversion notes

This topic discusses how InfoWorks WS Pro converts existing InfoWater network components into an InfoWorks network and InfoWorks network objects. Some data is not imported at all, or is only partially imported. Some InfoWater objects are imported as more complex InfoWorks objects, and additional data will be required to completely define these InfoWorks objects.

InfoWater component Conversion notes
  Nodes InfoWater node IDs are imported into InfoWorks in the Node ID and Asset ID fields of the network and the control data.
Junctions, emitters and demands

Junctions are imported into InfoWorks as nodes.

If the junction is an emitter, it will become a hydrant node. Flow coefficients for emitters are not used.

If the junction has a negative demand, it will become a transfer node.

Demands are imported into a demand diagram. Each pattern becomes a new demand category.

Reservoirs Reservoirs are imported into InfoWorks as fixed head nodes.
Tanks

Tanks are imported into InfoWorks as reservoirs.

Simple cylindrical tanks have their dimension specified as diameter, bottom level, and maximum level. InfoWorks generates a depth volume table based on these dimensions. More complex tanks are defined using a depth volume curve, and this is imported directly.

InfoWater tank minimum level is imported as an InfoWorks minimum operating level.

An InfoWater tank can define a minimum volume:  

  • If the first depth volume curve point has a level of zero and a volume > zero; this is treated as specifying reserve storage below the tank elevation. To account for this additional volume, the importer offsets the reservoir bottom level and curve levels downwards by a distance of 1 unit length. The InfoWater bottom level is imported as the InfoWorks minimum operating level. Top and initial water levels are imported as measured from the InfoWater bottom level (that is, relative to the InfoWorks minimum operating level.)  
  • If there is no depth volume curve, the InfoWater minimum level is zero and the minimum volume is > zero; a bottom offset is calculated from the minimum volume and the tank diameter. The importer offsets the reservoir bottom and the depth volume curve. The minimum operating level is set at the InfoWater bottom level. Top and initial water levels are imported as measured from the InfoWater bottom level (that is, relative to the InfoWorks minimum operating level.)

Any storage in the vertical pipe from above ground reservoirs is ignored.

Links

Link IDs are imported into InfoWorks as Asset ID in both the network and the control data.

Diameters for pumps will be set to 10mm (or equivalent).

Roughness coefficients for valves and pumps will be set to be of type Hazen-Williams with a value of 100.

Lengths for valves and pumps will be set to 1m (or equivalent).

Pipes Pipes with a status of CV (Check Valve) are imported into InfoWorks as non return valves.
Valves

Throttle control valves (TCV) are imported as InfoWorks time control valves (TCV) with gate valve curves. Throttle values are converted to valve openings.

InfoWater TCV valves with valve curves are imported directly.

Float Valves are either imported as InfoWorks float valves (FLV) or InfoWorks open/closed valves (OCV) depending on whether the downstream node is the control tank.

The following InfoWater valve types have no direct import equivalent:

PBV (pressure breaker)

UDV/GPV (general purpose)

Vacuum Breaker Valve

Pressure and vacuum breaker valves are imported as InfoWorks throttle valves (THV).  General purpose valves are imported as InfoWorks butterfly valves.

CONTROLS and RULES data for InfoWater valves that are compatible with InfoWorks WS valve types are imported into the local UPC script of the InfoWorks WS valve object (subject to conditions and actions being convertible).

Pumps

Pumps are imported into InfoWorks as pumping stations containing one pump.

Imported pumps need various parameters set in InfoWorks before the model will validate (see pump curves and pumping stations).

CONTROLS and RULES data for pumps are imported into the local UPC script of the InfoWorks WS pump object (subject to conditions and actions being convertible).

Pump initial speed settings and speed patterns are also imported from the InfoWater XINP file.

Energy settings for pumps do not get imported.

Water Quality

InfoWater water quality sections are imported as follows:

QUALITY component

The QUALITY component of the InfoWater model is used to set either the initial concentration, or the initial age of water at nodes, according to the setting of the QUALITY record in the OPTIONS section of the InfoWater XINP file.

REACTIONS component

Bulk coefficient and wall coefficient information is imported.

Order, limiting potential and roughness correlation information is not imported.

MIXING component

The MIXING component of the InfoWater model is imported to the WQ Mixing Model field of the InfoWorks reservoir object as follows:

InfoWater Mixing Model InfoWorks WQ Mixing Model
MIXED Fully Mixed
2COMP Two Compartment
FIFO First-In First-Out
LIFO First-In Last-Out
SOURCES component

The SOURCES component of the InfoWater model is imported to the Source Type field of the InfoWorks node object as follows:

InfoWater Source Type InfoWorks Source Type
CONCEN Fixed Concentration
MASS Additional Mass Flow
FLOWPACED Additional Concentration
SETPOINT Concentration Booster

Patterns associated with the InfoWater source type will also be imported.

Tags InfoWater tags are imported into the User Text 1 field of the InfoWorks object.
User field data

User field data can be imported into the InfoWorks User Text fields and User Number fields. A maximum of 15 of each field type can be populated, the selection and mapping being made when exporting from InfoWater.

Boolean data must be imported into User Number fields, where True is imported as 1 and False as 0.

Miscellaneous

The following sections do not get imported:

  • Labels
  • Report
  • Sustainability Data

Chezy-Manning roughness values are converted to Darcy-Weisbach.

Object Zones are imported to InfoWorks Object Areas.


Importing InfoWater data

InfoWater import wizard