Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

English (US)
Spanish
  • Contact Us
  • Sign up

Other articles

  • Pipes
  • Junctions
  • Hydrants
  • Customer points
  • Supply sources
  • Tanks
  • Pumps
  • Valves
  • Zones
Back to Properties by element
  • Home
  • Editing network elements
  • Properties by element

Pumps

Here you have all the specifications for the pump’s properties and how to modify them both in GIS files and EPANET. Check this table to see all accepted aliases for each property.

Qatium will process your data by running some validation checks and we’ll try to fill any gaps. 

Status

Data you add to your files

GIS editor

Field IniStatus, Status, d_presents, d_normalst, normalstat
Attribute

Open

Closed

 
 

EPANET

Property Initial Status
Value

Open

Closed

 
 

How Qatium processes that data

If not specified, Qatium will apply a default value: Open.

The pump’s status in Qatium reads On (for open) and Off (for closed).

 
 

Relative speed

Data you add to your files

GIS editor

Field Speed
Attribute [number]
 
 

EPANET

Property Speed
Value [number]
 
 

How Qatium processes that data

If not specified, Qatium will ignore it.

 
 

Power

Data you add to your files

GIS editor

Field Power, Potency, Output, Force
Attribute [number]
 
 

EPANET

Property Power
Value [number]
 
 

How Qatium processes that data

If neither the Power nor the Operating curve is specified, Qatium will apply a default value for Power: 0.01 kW.

 
 

Operating curve (head curve)

Data you add to your files

GIS editor

Field pump_curve, HeadCurve
Attribute x1 y1;x2 y2;x3 y3, etc.
 
 

EPANET

Property Pump Curve
Value x1 y1;x2 y2;x3 y3, etc.
 
 

The format of the curve must be: x1 y1;x2 y2;x3 y3... Where x is related to flows and y is related to heads. The ; (semi-colon) separates different point curves and a space separates the x and y values.

x flow
y head
; separates different point curves
[space] separates x and y values

For example: x1 y1;x2 y2;x3 y3

As it is something mandatory in Epanet, we define an ID for the pump curve. In this case, we use the asset ID + _HC.

For example: if the pump ID is P_Mandalorian we create a curve with the ID P_Mandalorian_HC.

How Qatium processes that data

If the curve is not specified and the Power property is not defined by the user, Qatium assigns a default value for the Power (0.01 kW). Curves don’t have default values.

 
 

Terrain elevation

GIS editor

For GIS datasets, Qatium processes elevation data when it's included as an attribute in point assets, like junctions, tanks, supply sources, valves, and pumps.

Field Elevation, Elev, TotalHead, Head
Attribute [number]
 
 

EPANET

In EPANET, to update elevation data for line assets — such as valves and pumps —, you need to edit the elevation of the upstream and downstream junctions connected to them. 

Property Elevation (of the upstream and downstream connected junctions)
Value [number]
 
 

How Qatium processes that data

If you have defined both height and elevation for your pumps in the corresponding file, the result will be the sum of both. Otherwise, Qatium will define the elevation using the Mapbox elevation data.

 
 

Controls

In Qatium, you can set up controls for your network elements — such as pipes, valves, and pumps —. These controls can help you automate operations like opening or closing a valve at a specific time or adjusting a pump’s settings.

Types of controls

Simple controls
Simple controls are straightforward commands, like "Open this valve at 3:00 PM" or "Close this pipe when the tank is full." 

Rule-based controls
Rule-based controls let you create a set of conditions—like "If the pressure drops below a certain level, turn on the pump." These are helpful for automating complex scenarios and responding to real-time changes in the network.

 
 

How to set up controls in Qatium

  1. From a .inp file or a text file (.txt)

You can import EPANET controls — both simple and rule-based — directly uploading a .inp file or a text file (.txt) to your network in Qatium.

Heads up: 
Qatium can detect Simple Controls and Rule Based Controls even if you don’t specify the [CONTROLS] and [RULES] headers in the .txt file format.

 
  1. From GIS files 

Qatium supports simple controls as defined in EPANET. You can also add your controls in a field labeled control or controls.

You can use a simplified format to define controls. Just specify the element type, its ID, and its settings. For example: Pump 1: OPEN AT TIME 3

This means Pump 1 will be open at 3.

If you apply controls to multiple elements within one asset, those controls will affect all of them. For example, for Pump 1 properties: Pump 1 OPEN AT TIME 3, Valve 2 CLOSED AT TIME 2, Valve 2 OPEN AT TIME 3

Here, the instructions for Valve 2 will still apply even though they’re listed under Pump 1 properties.

You can separate control instructions using tabs, commas, semicolons, or line breaks — whatever works best for your data organization.

 
 

How Qatium processes your data

When combining controls from different sources, Qatium applies them in this order:

  1. Controls from the .inp file
  2. Controls from the .txt file
  3. Controls defined in asset properties (GIS)

If any control isn’t valid, it won’t break your model. Instead, Qatium will skip it and include it as a comment in the output file.

Heads up: 
Qatium performs basic checks (like syntax and valid IDs) but doesn’t flag duplicate or conflicting controls. If controls overlap, the last one listed will take effect in the simulation.

 
 
 
 
 

Orientation

Data you add to your files

GIS editor

Field UpstreamConnections, UP, upstream
Attribute [upstream pipe ID]
 
 

EPANET

Property Start node / End node
Value [upstream and downstream nodes ID]
 
 

How Qatium processes that data

If not specified, Qatium will calculate orientation. Learn more in this article.

 
 
pumps properties pump status pump relative speed pump power pump operating curve pump elevation pump controls pump orientation
Status Relative speed Power Operating curve (head curve) Terrain elevation Controls Types of controls How to set up controls in Qatium How Qatium processes your data Orientation
Logo of Qatium © 2025 Qatium
  • Qatium.com
  • Book a Demo
  • Pricing
  • Community
  • Marketplace
  • Status
  • Privacy Policy
  • Terms & Conditions
  • Cookie Policy
Expand