Follow these specs to specify your valves’ type, their status, and/or edit their properties.
Check this table to see all accepted aliases for each property.
Qatium will process that information by running some validation checks and we’ll try to fill any gaps.
Type
Shut-off valves
GIS files
| Field | Type |
|---|---|
| Attribute | TCV |
EPANET
| Property | Type |
|---|---|
| Value | TCV |
How Qatium processes that data
If not specified, Qatium will apply a default value: TCV.
Regulating valves
GIS files
| Field | Type |
|---|---|
| Attribute |
PBV FCV PSV PRV GPV |
EPANET
| Property | Type |
|---|---|
| Value |
PBV FCV PSV PRV GPV |
How Qatium processes that data
If not specified, Qatium will apply a default value: TCV.
Setting
GIS files
| Field | Setting |
|---|---|
| Attribute | <number> |
EPANET
| Property | Setting |
|---|---|
| Value | <number> |
How Qatium processes that data
If not specified, it will be ignored and the Status will be Active.
Status
Shut-off valves
GIS files
| Field | Status |
|---|---|
| Attribute |
Active Open Closed |
EPANET
| Property | Fixed Status |
|---|---|
| Value |
None Open Closed |
How Qatium processes that data
If not specified, Qatium will apply a default value: Active/Open.
Regulating valves
GIS files
| Field | Status |
|---|---|
| Attribute |
Active Open Closed |
EPANET
| Property | Fixed Status |
|---|---|
| Value |
None Open Closed |
How Qatium processes that data
If not specified, Qatium will apply a default value: Open (or active–regulating, in case there’s a setting property).
You can also modify the valve’s status directly in Qatium while performing scenarios. But bear in mind that this change won’t persist in your actual network.
Diameter
GIS files
| Field | Diameter |
|---|---|
| Attribute | <number> |
EPANET
| Property | Diameter |
|---|---|
| Value | <number> |
How Qatium processes that data
If not specified, Qatium will apply a default value:
| SI units | US units |
|---|---|
| 200 mm | 8 in |
Terrain elevation
GIS files
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 |
|---|---|
| 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 not specified: Qatium will add it from 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
- 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.
⚠️ Important: 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.
- 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: Valve 1: OPEN AT TIME 3
This means Valve 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: Valve 1 properties: Valve 1 OPEN AT TIME 3, Pipe 2 CLOSED AT TIME 2, Pipe 2 OPEN AT TIME 3
Here, the instructions for Pipe 2 will still apply even though they’re listed under Valve 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:
- Controls from the .inp file
- Controls from the .txt file
- 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.
⚠️ Important: 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
To define the orientation, we recommend defining the upstream pipe in your pump and valve layers as it limits inferences.
GIS files
| Field | 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.