EPANET conversion notes

EPANET node IDs are imported into InfoWorks in the Node ID and Asset ID fields of the network and the control data.

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 are imported into InfoWorks as fixed head nodes.

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.

EPANET reservoir minimum level is imported as an InfoWorks minimum operating level.

An EPANET tank sometimes defines 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 EPANET bottom level is imported as the InfoWorks minimum operating level. Top and initial water levels are imported as measured from the EPANET bottom level (that is, relative to the InfoWorks minimum operating level.)
• If there is no depth volume curve, the EPANET 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 EPANET bottom level. Top and initial water levels are imported as measured from the EPANET bottom level (that is, relative to the InfoWorks minimum operating level.)

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

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 with a status of CV (Check Valve) are imported into InfoWorks as non return valves.

The following EPANET valve types have no direct import equivalent:

• PBV (pressure breaker)
• TCV (throttle control)
• GPV (general purpose)

Pressure breaker and throttle control valves are imported as InfoWorks throttled valves (THV). General purpose valves are imported as InfoWorks butterfly valves. See Valve.

CONTROLS and RULES data for EPANET 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 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 EPANET file.

Energy settings for pumps do not get imported.

EPANET water quality sections are imported as follows:

QUALITY component

The QUALITY component of the EPANET 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 EPANET 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 EPANET model is imported to the WQ Mixing Model field of the InfoWorks reservoir object as follows::

SOURCES component

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

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

EPANET tags are imported into the User Text 1 field of the InfoWorks object.

The following sections do not get imported:

• Title
• Backdrop
• Labels
• Report

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