Configuring hydrant testing using GMR

00:04

The mapped CSV import function can be used to populate

00:07

a GMR configuration and simulate a hydrant testing exercise.

00:12

In this exercise, you will configure the GMR to test hydrant flows of 5, 10,

00:22

When the model predicts the minimum residual pressure,

00:25

this is a more efficient way to perform firef flow simulations.

00:29

Since GMR allows for a large number of hydrants to be tested simultaneously

00:34

from the model group. Right, click the run group and select new run

00:40

in the schedule hydraulic run dialog box.

00:43

Set up an experimental normal hydraulic run with

00:46

the GMR network control and demand diagram provided

00:50

and call it baseline,

00:53

run this simulation

00:55

in the GEO plan open the baseline simulation results

00:59

then from the model group double click the hydrant summary SQL.

01:04

This SQL

01:05

provides a list of each hydrant as well as

01:07

the time when each one experiences the lowest pressure,

01:11

you will use the time of lowest pressure as the test time for the hydrant to

01:15

ensure that it can provide the required fire

01:17

flow when it is experiencing the lowest pressure

01:21

in the SQL

01:22

hydrant summary window select run.

01:25

The SQL

01:25

results can be open as a grid which is used to provide

01:29

a list of test nodes and test times in the GMR.

01:32

Make sure this grid is kept open.

01:35

Create a new GMR configuration object

01:39

from the model group, right,

01:41

click generalized multi run group and

01:43

select new generalized multi run configuration

01:47

in the pop up, name it hydrant testing and click. OK.

01:51

In the generalized multi run configuration,

01:53

dialog box dragon drop the hydrant selection list into

01:56

the selection list pane from the model group.

01:59

Then

01:60

click mapped CSV import to upload the details from the SQL

02:04

results grid.

02:06

Once the GMR mapped CSV import window is open

02:09

enable import from SQL

02:11

results view

02:13

in the first row of the table in the test case column,

02:16

expand the dropdown and select CSV node id.

02:21

Then in the table column, select run

02:25

in the field column, select existing node id

02:28

and in the value column, select CSV node id

02:33

in the second row of the table in the test case column, select CSV node id

02:40

in the table column, select run

02:43

in the field column, select hydrant testing time

02:47

and in the value column, select CSV time.

02:51

Click OK.

02:53

Back in the generalized multi run configuration dialogue, click the results tab

02:58

these options allow for different levels of

03:00

detail to be retained for future review.

03:04

For this example, select keep summary report only

03:09

click the analysis tab and select the following options

03:12

available firef flow

03:14

fully open hydrant flow

03:17

hydran testing result

03:19

minimum and maximum firef flow

03:22

pretest demand and pressure,

03:24

residual pressure at available firef flow

03:28

fully open hydrant flow,

03:30

minimum and maximum fire flow.

03:33

Save the GMR configuration object.

Video transcript

00:04

The mapped CSV import function can be used to populate

00:07

a GMR configuration and simulate a hydrant testing exercise.

00:12

In this exercise, you will configure the GMR to test hydrant flows of 5, 10,

00:22

When the model predicts the minimum residual pressure,

00:25

this is a more efficient way to perform firef flow simulations.

00:29

Since GMR allows for a large number of hydrants to be tested simultaneously

00:34

from the model group. Right, click the run group and select new run

00:40

in the schedule hydraulic run dialog box.

00:43

Set up an experimental normal hydraulic run with

00:46

the GMR network control and demand diagram provided

00:50

and call it baseline,

00:53

run this simulation

00:55

in the GEO plan open the baseline simulation results

00:59

then from the model group double click the hydrant summary SQL.

01:04

This SQL

01:05

provides a list of each hydrant as well as

01:07

the time when each one experiences the lowest pressure,

01:11

you will use the time of lowest pressure as the test time for the hydrant to

01:15

ensure that it can provide the required fire

01:17

flow when it is experiencing the lowest pressure

01:21

in the SQL

01:22

hydrant summary window select run.

01:25

The SQL

01:25

results can be open as a grid which is used to provide

01:29

a list of test nodes and test times in the GMR.

01:32

Make sure this grid is kept open.

01:35

Create a new GMR configuration object

01:39

from the model group, right,

01:41

click generalized multi run group and

01:43

select new generalized multi run configuration

01:47

in the pop up, name it hydrant testing and click. OK.

01:51

In the generalized multi run configuration,

01:53

dialog box dragon drop the hydrant selection list into

01:56

the selection list pane from the model group.

01:59

Then

01:60

click mapped CSV import to upload the details from the SQL

02:04

results grid.

02:06

Once the GMR mapped CSV import window is open

02:09

enable import from SQL

02:11

results view

02:13

in the first row of the table in the test case column,

02:16

expand the dropdown and select CSV node id.

02:21

Then in the table column, select run

02:25

in the field column, select existing node id

02:28

and in the value column, select CSV node id

02:33

in the second row of the table in the test case column, select CSV node id

02:40

in the table column, select run

02:43

in the field column, select hydrant testing time

02:47

and in the value column, select CSV time.

02:51

Click OK.

02:53

Back in the generalized multi run configuration dialogue, click the results tab

02:58

these options allow for different levels of

03:00

detail to be retained for future review.

03:04

For this example, select keep summary report only

03:09

click the analysis tab and select the following options

03:12

available firef flow

03:14

fully open hydrant flow

03:17

hydran testing result

03:19

minimum and maximum firef flow

03:22

pretest demand and pressure,

03:24

residual pressure at available firef flow

03:28

fully open hydrant flow,

03:30

minimum and maximum fire flow.

03:33

Save the GMR configuration object.

Video quiz

Which of the following methods for creating fire flow analyses in InfoWorks WS Pro allows for the greatest number of hydrants to be simulated at once?

(Select one)
Select an answer

1/1 questions left unanswered

Step-by-step guide

In InfoWorks WS Pro, the Mapped CSV Import function can be used to populate a GMR configuration and simulate a hydrant testing exercise. In this tutorial, you create and configure a GMR to test hydrant flows of 5, 10, 15, 20, etc. l/s, at the time of day when the model predicts the minimum residual pressure. The goal is to ensure that each hydrant can provide the required fire flow when it is at the lowest pressure.

  1. In the Model Group, right-click the Run Group.
  2. Select New > Run.
  3. In the Schedule Hydraulic Run dialog box, in the Title field, enter the name “Baseline”.
  4. Enable Experimental.
  5. From the Model Group, drag the Network into the Schedule Hydraulic Run dialog box and drop it into the Network group box. The Control and Demand Diagram boxes also populate.
  6. Click Run.

The Schedule Hydraulic Run dialog box displays with the parameters set for an experimental, normal run named “Baseline”.

  1. In the Model Group, expand Baseline.
  2. Drag the Control simulation results and drop them into the GeoPlan.
  3. From the Model Group, double-click the Hydrant summary SQL.
  4. In the SQL: Hydrant summary window, select Run.

The SQL results open in a grid window, with a list of hydrants and the time at which each experiences the lowest pressure. Make sure this grid is kept open.

The SQL results grid, with a list of hydrants and the time at which each experiences the lowest pressure.

To create the new GMR Configuration:

  1. From the Model Group, right-click Generalised Multi Run Group.
  2. Select New > Generalised Multi Run Config.
  3. In the popup, enter the name “Hydrant Testing”.
  4. Click OK.
  5. In the Model Group, select Hydrant Testing to open the Generalised Multi Run Config dialog box, now renamed “Hydrant Testing”.
  6. Drag and drop the Hydrant selection list into the Hydrant Testing dialog box and drop it into the Selection List group box.
  7. Click Mapped CSV Import to upload the details from the SQL Results Grid.
  8. In the GMR Mapped CSV Import dialog box, enable Import from SQL Results View.
  9. In the first row of the table, in the Test Case column, expand the drop-down and select CSV:node_id.
  10. In the Table column, select Run.
  11. In the Field column, select Existing Node ID.
  12. In the Value column, select CSV:node_id.
  13. In the second row of the table, in the Test Case column, select CSV:node_id.
  14. In the Table column, select Run.
  15. In the Field column, select Hydrant Testing Time.
  16. In the Value column, select CSV:Time.
  17. Click OK.

The GMR Mapped CSV Import window with Import from SQL Results View enabled and two rows of data entered in the table.

  1. Back in the Hydrant Testing dialog box, click the Results tab.
  2. For this example, select Keep summary report only.
  3. Click the Analysis tab.
  4. In the Results field list, select Available Fire Flow.
  5. Select Fully-open Hydrant Flow.
  6. Select Hydrant Testing Result.
  7. Select Maximum Fire Flow.
  8. Select Minimum Fire Flow.
  9. Select Pre-Test Demand.
  10. Select Pre-Test Pressure.
  11. Select Residual Pressure at Available Fire Flow.
  12. Select Residual Pressure at Fully-open Hydrant Flow.
  13. Select Residual Pressure at Maximum Fire Flow.
  14. Select Residual Pressure at Minimum Fire Flow.

In the Hydrant Testing dialog box, Results tab, with the Results field list highlighted in red and checkboxes being selected to enable options.

  1. Click Save to save the GMR Configuration.
Was this information helpful?