Pipenet Vision Spray/Sprinkler Module User and Reference Manual
Pipenet Vision Spray/Sprinkler Module User and Reference Manual
Spray/Sprinkler Module
User and Reference Manual
Version 1.7
PIPENET and PIPENET VISION are registered trademarks of Sunrise Systems Limited. All other names and
services mentioned in this manual that are trademarks, registered trademarks, or service marks, are the
property of their respective ow ners.
Contents I
Table of Contents
Foreword 0
Part 2 Installation 6
1 Installation
................................................................................................................................... 6
2 Prerequisites
................................................................................................................................... 6
3 Updating
...................................................................................................................................
a key license 6
4 Security
...................................................................................................................................
Key Problems 7
5 Windows
...................................................................................................................................
8 10
6 Nozzle
...................................................................................................................................
characteristics 70
7 The
...................................................................................................................................
design and calculation phases 71
8 Specifications
................................................................................................................................... 71
9 Network
...................................................................................................................................
data entry 72
10 Calculation
...................................................................................................................................
and results 74
3 Copying
...................................................................................................................................
Cells 105
7 Linings
................................................................................................................................... 165
8 Deluge
...................................................................................................................................
Valves 166
9 Editing
...................................................................................................................................
system libraries 166
Index 266
Part
1
Sunrise Systems 2
1 Sunrise Systems
1.1 Welcome
Here is a summary of the new features - see the Help and Training manuals for further
information. We are sure you will enjoy using PIPENET!
Angle Valve - This is common in the oil/gas, power and shipbuilding industries, consisting of
a controlled valve door around a 90 degree bend.
Ball Valve - Consisting of a near-spherical rotary valve door, this valve is also commonly
used in oil/gas, power and shipbuilding.
Butterfly Valve - Consisting of a rotating door, either flat or lenticular in nature, used in
applications which require bi-direction shut-off
Diaphragm Valve - These consist of a rubber or plastic membrane which is pushed down to
shut off flow in many process systems.
Gate Valve - These have a planar sealing surface, between the valve gate and valve seats,
used when a straight line flow is required with minimum restriction.
Globe Valve - Typically used in pipelines, these consist of two halves of a valve body,
separated by an internal baffle, where a plug closes a gap in the baffle.
Y-Type Valve - Similar to globe valves, but instead of using an internal baffle, the gate
mechanism is located at an angle to the flow, allowing frequent operation with less restriction
on the flow.
Standard Module For the analysis of the single phase flow of liquids and gases.
Spray Module For the analysis of fixed fire-protection systems employing water.
Transient Module For the analysis of transient flow in all types of network employing a
liquid.
keys, the number is located in the bottom right-hand corner of the key label (not the Sunrise
address label). Before sending any queries relating to the installation of the software, please
make sure that you have read the trouble-shooting section in this document, and provide details
of any error messages encountered during installation.
Items such as File | New shown in bold indicate the selection of an option from a
menu. The item before the vertical bar is the main menu item, and the item after the
vertical bar is the specific menu option. For example, File | New indicates that the
menu option New is to be selected from the File menu.
Capitalised items shown in bold (for example Apply), generally indicate the selection of
a button or item in a dialog.
Part
2
Installation 6
2 Installation
2.1 Installation
Installation of a PIPENET module will have been described in the installation guide, which
accompanies the CD-ROM. This chapter deals with problems that may occur once the software
has been installed from CD-ROM.
2.2 Prerequisites
To run any of the PIPENET modules, you need the following:
Keys can be re-programmed without needing to be returned to Sunrise Systems Limited for re-
programming, using an encrypted file (which can be sent by email to the customer).
Expiry dates
If a module has been licensed with an expiry date, then any attempt to use the module beyond
the expiry date will result in the key no longer being recognized as a valid key. If a key expires
then Sunrise Systems should be contacted, requesting an update. If approved, a small encrypted
text file will be sent to the customer by email.
1. Make sure that you have started PIPENET, and there is no network open.
2. Select the menu option Help | Update key, and the following message will be
displayed:
3. Selecting OK will display a dialog for navigating to the encrypted licence file.
4. As soon as you have selected the licence file, a second dialog will be displayed,
hopefully indicating the success of the operation:
5. If the operation fails then Sunrise Systems should be contacted for further assistance,
which may necessitate the return of the key. This may occur with security keys that
are several years old.
Note that the encrypted licence file is only valid for a specific key, as identified by the number in
the bottom right-hand corner of the key's label. For parallel port keys, this will be a four digit
number; for USB keys, a 5 digit number greater than 10000. Note, also, that a licence file can
only be used once to update a key; if an attempt is made to update a security key more than
once, the second and subsequent attempts will fail with an error.
PIPENET will never replace an existing file in this directory if it is more recent than the
one shipped with PIPENET.)
Access to the Windows System registry.
If you did not have these rights when you installed the software then the key drivers will not have
been correctly installed, and thus the software cannot be run. Re-install the software, having
obtained the necessary rights and privileges. Contact your IT support group if you unsure as to
how to proceed.
If the key is not programmed for the module you are attempting to run, or the number of runs has
expired, or the key has passed its expiry date then any error messages displayed will inform you
of the specific error.
If the key is correctly fitted, and the drivers have been correctly installed, then the status of the
key and the licences available can be checked via the Help | Key Status menu option. If the
security key is correctly fitted then this will display the key details, including the key number and
customer name, in addition to licensing details.
Trouble shooting
The most common reasons for failure are not having the correct key fitted or the key drivers
were not installed correctly. If the key drivers were not installed then the most likely reason for
the failure is that you did not have the necessary access rights during installation. The following
summarises the checks you should perform to locate the source of the problem:
1. Check that you are using a security key appropriate to the module you are trying to
run.
2. Check that the key is correctly fitted to a USB or parallel port on the computer
where you are attempting to run the PIPENET software.
3. You must have Windows Administrator privileges to install the key drivers, since
changes are made to the System Registry. If you do not have these rights, you will
have to contact your IT department to set up your account details. It is recommended
that you contact your IT department anyway, to confirm any other rights and
restrictions that there may be.
4. Check that you have read and write access to the drive where the software will be
installed (by default, drive C:) and where the temporary files will reside (also, by
default, drive C:). This is necessary, since some organisations prohibit their users from
accessing the local disk, and selected network drives, other than for read access.
Again, if you do not have these rights then you will have to contact your IT
department.
5. Please check (re-install if necessary) that the software and key drivers are correctly
installed.
6. The installation of the key drivers can be checked by running the program
KEYSETUP.EXE, which can be found in the keydriver sub-directory of the
PIPENET installation directory. Running this program produces the display:
Select the Check key drivers button to confirm the installation. Entering this
command will display the status of the key drivers, which, if correctly installed, will
display the date of installation and other information on the printer port, version
number of driver, etc.
7. If step 5 reports that the key driver is not installed then terminate any running
PIPENET module and select the three buttons in the sequence Remove key
drivers, Install key drivers and Check key drivers.
8. The last of the four buttons in the dialog, Check key, will attempt to read the key,
displaying the internally stored key number and the customer name. The customer
name may not be present on very old keys, but the key number should always be
readable if the key drivers are correctly installed.
The key-check utility is stored on your hard drive during installation, in the sub-directory
keydriver, and the key check utility program is named KeySetup.exe.
2.5 Windows 8
Sunrise Systems fully support the use of PIPENET on Windows 8, however there are a couple
of known issues which will be addressed here.
Some users have had issues when upgrading from Windows 8.0 to Windows 8.1 due to
problems with the license key drivers. This simple procedure will enable users to upgrade to
Windows 8.1 from Windows 8.0.
Procedure
When installing Windows 8.1, the old HASP Drivers need to be removed. This has to be done
by downloading
from
http://sentinelcustomer.safenet-inc.com/sentineldownloads
extracting the downloaded zip files. Then, in a command window (cmd.exe), navigating to the
directory where the extracted files are kept by typing
cd [directory]
cd C:\Users\***Username***\Downloads\Sentinel_LDK_Run-time_cmd_line\
haspdinst.exe purge
This completely removes all forms of HASP drivers from the machine. It is important to
note that the GUI Installer does not function correctly as it does not have the capacity to
purge the machine of all traces of the HASP drivers.
Following this, install the update to Windows 8.1 and from the aforementioned web
directory, download
Ensuring it is version 6.60 or above that is installed. Extract and double click on
HASPUserSetup.exe, following the on screen instructions.
This should correctly reinstall the HASP Drivers, compatible with Windows 8.1. You will
now be able to use PIPENET.
Part
3
13 Spray/Sprinkler Module
Upper-left: a Properties Window used for displaying the attributes of the currently
selected component. This window replaces the dialogs of earlier versions of the
software, since data can be entered and edited in this window.
Lower-left: Schematic Overview Window showing an overall view of the schematic,
with a rectangle showing the region covered by the main schematic. The rectangle may
be dragged, with the main schematic window being automatically scrolled to reflect the
changes. Conversely, scrolling the main window or changing the zoom factor will
change the position and/or size of the rectangle in the Overview window.
Upper-right: the Schematic Window, essentially as in the previous versions of
PIPENET, but allowing colour coding, multiple selections, an improved Area Tool with
copy, paste, delete, flip and invert operations, and an unlimited undo/redo facility.
The Tabbed Properties and Schematic Overview windows can be closed by clicking the button
at the top-right of each window. To re-display the windows, select either the View | Properties
or View | Schematic Overview option.
The Properties Window and the Schematic Overview can be moved to the right-hand side of the
screen or "floated", by clicking and dragging the top of each window.
At the top of the screen is the usual assortment of menus and toolbars, and at the bottom is the
status bar.
Menu styles
The menus are arranged differently to the previous PIPENET programs, although users of other
Windows programs may find them more familiar. To revert to the old style of menu, select the
menu option Window | Use Pipenet menu style. To revert to the new window style, select
Window | Use Windows menu style. See also the Window Menu.
When the window is first displayed, it is presented with a light-grey background suitable for
general viewing. The background colour may be changed to white or black. However, for
coloured links and text, it will generally be found that a white background is unsuitable for
viewing.
New elements are added by selecting the appropriate element tool from the tool palette, and
then placing and drawing the component using the mouse.
All labeled elements created via the schematic are automatically assigned a unique label. Labeled
elements include nodes, link elements and attribute elements. Numeric labels are used (no tags)
with each component type having its own set of unique labels.
The background colour and the font sizes used for labeling components can be changed using
the Display Options dialog.
Schematic Underlay
A facility has been included whereby a graphic may be imported and displayed as a background
to the main schematic. Display of this underlay is enabled and disabled via the View menu. The
underlay may be zoomed independently of the main network to achieve relative scaling and
registration. Zooming the network results in the underlay being zoomed by the same selected
zoom factor. In normal use, the procedure to use an underlay commences with a new network:
More than one Tabular View window may be open at a time, each showing the same or a
different component type.
The Tabbed properties window is normally displayed but, if it is closed, it can be re-opened via
the View menu.
W hen a component has been drawn on the schematic it will be assigned default parameters.
These defaults may be edited in the Properties tab. Data entry fields in the properties window
are either straightforward, numeric, text entry, or the selection style (when there is a limited
number of options available). Fields which cannot be edited will be "greyed" out.
The properties for all components are displayed in the same general manner: In the top left-hand
corner of the grid is the symbol for the component, below this a number of rows, one for each
attribute or result. Each row comprises of three columns:
The above example shows the attributes for a pipe. All attributes can be edited: The length and
elevation of the pipe are shown in feet and the diameter in inches. The status of the pipe is
selectable from a drop-down list, and will be one of Normal, Blocked or Broken.
To edit a field, click in the appropriate row in the second column and enter the new value, or
select from the available options. To accept the value, enter Tab to move down to the next field
or Enter on the keyboard. Values with a light-grey background cannot be edited. Changes made
in the window can be undone and redone using the undo and/redo keys:
Scroll buttons
In the bottom right-hand corner of the window are two scroll buttons, which are used to move
from the currently displayed component to the next or previous component of the same type.
For example, if a pipe is currently displayed, selecting the left button will move to the previous
pipe (if there is one). Pressing the right button will move to the next component. Components are
ordered in the sequence in which they were created.
3.6 Fittings
If the currently selected component is a pipe then this window will display the fittings on the
pipe.
The top window displays a list of available fittings; the bottom, a list of the fittings currently
selected on the pipe. The lower window displays for each fitting type; the fitting name, the K-
factor and the number of fittings selected on the pipe; below the window is shown the sum of the
K-factors for all fittings.
Adding a fitting
To add a fitting to a pipe, select the desired fitting from the top window, and then click on the
Add button. Each selection of the Add button adds one fitting of the selected type to the pipe.
Removing a fitting
To remove a fitting, select the desired fitting type in the bottom window, and then click on the
Remove button. Each selection of the Remove button removes one fitting of the selected type.
Display of the Overview window, which is not shown on starting the program, is done via the
View | Schematic Overview menu option.
3.8 Menus
3.8.1 File Menu
The available options are as follows. The displayed options will vary, depending on whether or
not a network is open.
New
Creates a new network. If licenses are available for more than one module type, a
prompt will be displayed requesting the PIPENET module be selected; namely,
Standard, Spray/Sprinkler or Transient.
Open
Opens an existing data file - files may be the old format data files, with a .DAT file
extension, or the new style files, with a .SDF file extension.
Close
Closes the network - if changes have been made to the network, you will be prompted
to save the file first before closing.
Save
Saves the current network and continue working.
Save As
Saves the current file under a different file name.
Export...
This will export the current network as an old style .DAT file, together with any
associated old-style library files; that is, .PDF files, .UFL files, etc. When selecting this
option, you should be aware that some graphical information will not be saved; for
example, colour schemes. When prompted for a file name, enter the name of the .DAT
file, and any associated library files will be saved with the same name, but with a
different file extension.
Autosave...
AutoSave is a feature that can be used to automatically save your edits and
modifications periodically. Select this option to set the interval, in minutes, at which the
network is to be automatically saved. The default is zero, indicating that the autosave
feature is disabled.
Open Library
Opens an external system library.
Import Library
Imports a library file - opens a system library or old format library file (e.g., .pmp pump
library file) and imports its definitions into the local user library.
Print
Print the schematic or the grid - the one that is printed will depend on which of the two
windows is selected. If in doubt, click in the desired window before selecting Print. If
the grid is selected, the current grid page will be printed. If the schematic is selected
then a dialog box is displayed, through which the user can select the scaling and hence
the number of pages. required to print the schematic.
Print Preview
Previews the appearance of printed output.
Print Setup
This option displays a standard Windows dialog, from which the user can select a
particular printer, landscape or portrait mode, etc.
Exit
Exits PIPENET.
Undo
Undoes the last operation - this command will undo the last change made in the
Schematic, Properties or Tabular View window. Following the word Undo is a brief
description of the last operation performed.
Redo
Redoes the last undone operation - as with the Undo command, following the word
Redo is a brief description of the last undo operation.
Cut
Combination of a copy operation followed by a delete.
Copy
If the select tool is in operation, this will copy the attributes of the selected component.
If the Area tool is in use, it will copy all components within the selection rectangle.
Paste
If the select tool is in operation, this will paste the last copied attributes to the selected
component, as long as the components are of the same type (i.e., both are pipes, both
are pumps, etc.). If the Area tool is used, it will paste all components copied by the
last copy operation.
Paste in column
This option is only available in the Tabular View. When a single cell in a column is
selected, it will reproduce the contents of the cell in all cells in the same column.
Mirror
Used with the Area Tool to mirror the contents of the selected area left-right.
Invert
Used with the Area Tool to invert the contents of the selected area.
The left-hand button is the Undo button and the right-hand button is the Redo button.
Toolbar
Displays or hides the main toolbar containing the file and edit related buttons - this is
best left displayed at all times.
Status Bar
Displays or hides the Windows status bar - this is best left displayed at all times.
Palette
Displays or hides the palette bar, which is used to select the tool for drawing within the
schematic window - this is best left displayed at all times.
Schematic Window
Opens the schematic window if, for some reason, it has been closed - only one
schematic window can be open.
Data Window
Opens a tabular view window - more than one tabular view window can be open at
any one time.
Properties
Displays or hides the Properties Window, which contains the tabbed set of windows,
Schematic Overview
Displays or hides the Schematic Overview Window.
Zoom
Used to zoom the network and/or the graphical underlay.
The imported graphic is displayed near the centre of the window, and is scaled to fit the
current size of the window. The size of the imported graphic can be controlled by
zooming (see above). Its position is currently not controllable. However, using the Area
tool to move the network, the relationship between the underlay and the PIPENET
network can be adjusted. The intensity of the displayed image, specified as a
percentage, can be controlled via the underlay tool (i.e., the U button) on the Options
toolbar.
The Libraries menu contains a number of module-specific entries. Those for the Spray/Sprinkler
module include:
Schedules
Define or edit pipe schedules in the local user library.
Nozzles
Define or edit pipe spray nozzles in the local user library.
Deluge Valves
Define or edit deluge valves.
Selecting any of these options displays a tabbed dialog for the appropriate library. It is important
to note that any changes are applied to the definitions in the Local User Library.
To edit the System libraries, select the last option (i.e., Edit system Libraries).
To edit System libraries select the last option Edit system Libraries.
The final option in the Libraries menu opens a very similar window, except that, in this case, edits
are performed on a named System Library. It is important to re-emphasis the distinction
between Local User Libraries, where changes made affect only the current user, and System
Libraries, where changes may affect other users.
Title - Title for the network, for which up to four lines of text may be specified.
Module Options - Various modelling options.
Units - Units to be used.
Pipe Types - Pipe types.
Display options - Schematic display options.
Calculation- Calculation options, including tolerances.
Output tables - Selection of which output results are to appear in the browser output.
Defaults - Default information for pipes and nozzles (module dependent).
Simple rules
This option is used to define the colouring of links and/or nodes, based on the value of
a single attribute or result. For example, node elevation, pipe length, velocity of fluid
through pipes, and so on.
Complex nodes
This option is used to define more complex colouring rules for nodes, based on the
values of more than one attribute or result.
Complex links
This option is used to define more complex colouring rules for pipes, based on the
values of more than one attribute or result.
Check
Check conditions for calculation - checks that specifications are complete and
consistent, and, if pipe elevations are in use, that node heights are consistent. This
option opens a status window (if it is not already open) as described in Status
Checking.
Input data
Runs a validation in the calculator, producing an output browser file. For those users
with metered licenses, a validation does not consume a calculation.
Pipe Sizing
Runs the pipe sizing phase of the calculation only, his phase will calculate the bore of
any pipes with an undefined bore. For those users with metered licenses, a validation
does not consume a calculation.
Calculate
Runs a calculation, consuming one calculation for those users with metered keys.
Browse
Browse the output of the last calculation or the last request for input.
Remove tags
Marks all tagged components as untagged.
Make Path
Used in the construction of an elevation profile to construct a path though two or more
selected nodes..
Export clipboard
Copies the schematic to the clipboard, from where it can be pasted into other
applications.
Export HP-GL/2
Exports the schematic as an HP-GL/2 file containing instructions for off-line plotting.
HP-GL/2 is Hewlett-Packard's standardized Graphics Language supported by many
CAD and graphics programs and peripherals. On selecting this option, you will
prompted to supply an output file name.
Autolayout
The autolayout tool, which is available in the PIPENET spray/sprinkler module, can be
used to automate the task of designing spray/sprinkler systems for vessels or for area
protection.
Key Status
Status and information relating to the Hasp security key and associated licences.
Selecting this option will display the current licences available on the fitted key, the
following being an example of the display:
Selecting OK closes the window, whilst selecting Save will save the displayed details
to a text file (the save feature is not implemented).
Update Key
This option is only available in the Help menu when no PIPENET file is open.
Activating this option will initiate an update to a local HASP security key using a licence
file supplied by Sunrise Systems.
3.9 Toolbars
3.9.1 Spray Toolbar
Then there are eight tools for creating the different types of link components (i.e.
components with an input and output node) available with the Spray module:
Pipe - Note that this button will be greyed out (not selectable) until at least one
pipe type has been defined. In the Spray/Sprinkler module, it is mandatory that all
pipes belong to a pipe type.
Pump
Filter
Nozzle
Non-return valve
Deluge valve
Elastomeric valve
Overboard dump valve (see the note below)
Note that if the Remote nozzle specifications or Mass balance specifications option has
been selected in the Calculation options dialog then the overboard dump valve icon on the
toolbar will be greyed out (non-selectable). This is because overboard dump valves can only be
used with the the User-defined specifications option.
The toolbar consists of four button groups, from left to right the button options are:
Display grid.
Select Orthogonal grid.
Select Isometric grid.
Snap to Grid.
A single button is provided. Selecting the button will display a dialog from which
the intensity of the underlay can be specified as a percentage.
When an option is selected, the button is shown as depressed, as illustrated for the Select
Orthogonal grid option (i.e., the second button in the above diagram).
Check
Checks the conditions for a calculation. More specifically, it checks that specifications
are complete and consistent, and, if pipe elevations are in use, that node heights are
consistent. This option opens a status window (if it is not already open) as described
in Status Checking.
Input data
Runs a validation in the calculator, producing an output browser file. Validation does
not consume a run for users with metered keys.
Pipe sizing
Runs the pipe sizing, or design phase, of the calculation only. Pipe bores will be
calculated for those pipes with undefined sizes, and returned to the user interface for
display with the rest of the pipe attributes. Pipe sizing does not consume a run for users
with metered keys. Pipe sizing is only possible if there is at least one pipe type, and if
there are no ducts present in the network.
Calculate
Runs a calculation, producing a browser output file that can be viewed in the supplied
browser, Word or Write.
Browse
Browses the output of the last calculation or the last request for input.
Design phase
Places the front-end in the design phase, in which pipe sizing operations can be
performed repeatedly.
Calculation phase
Selection of this button places the calculator in calculation mode, and any pipe sizes
calculated in the design phase are fixed for all future calculations.
Selecting the arrow to the right of the text field will drop down a list of currently used tags, and
selecting a tag from this list sets that tag as the default.
If you have a tag selected in one of the drop-downs then, whenever you create a new
component, its automatically assigned numerical id will be prefixed with the specified tag and a
'/'.
Unused tags cannot be explicitly deleted, but, each time a file is re-opened, the tags in use are
re-evaluated, and only those in use will be displayed.
A Find button.
A drop-down list of component types, including the special type <Any>, which can be
used to find a component of any type with the specified label.
An edit box for entering the label of the component to find.
A Next button, which is only enabled if the component type is <Any> and a find has
been performed. Having found one component with a matching label, selecting this
button will find the next component with the same label (assuming there is one).
If a component is not found then an information message will be displayed on the status bar at
the bottom of the main window.
Part
4
35 Spray/Sprinkler Module
4.3 Labels
Each component and each node in the network must be given a label that uniquely identifies it.
Labels may either be tagged or untagged. Untagged labels are simply a number in the range 0-
32767. Tagged labels consist of a 'tag' (i.e., a string of up to 8 characters) followed by a slash (/)
and a number in the range 0-999. Tags can be used to make labels more meaningful, and to
allow sections of large networks to be more easily identified. Up to 100 different tags can be
used in one system. Tags must begin with a letter, and may contain only letters and numbers. For
example, the following are all legal labels:
Untagged:
1
1273
9999
Tagged:
JETTY6/1
JETTY6/876
P/12
Notes:
1. Untagged labels greater than 999 and tagged labels may not be used in the same
network.
2. Tags not followed by a slash and a number are not valid labels. For example, XYZ is a
valid tag, but is not a valid label when used alone.
3. Tags are case insensitive; that is, RING is taken to be the same as Ring and ring.
Some components have only an input node, and although the component may appear to be
drawn between two nodes, the output node is not visible and so it can have no other component
connected to it. For example, a spray nozzle does not have an output node, as the output from a
nozzle cannot be attached to any other component - all nozzles are assumed to discharge to
atmosphere.
as having:
Water is flowing into pipe 1 at node 1, and out of pipes 2 and 3 at nodes 3 and 4. The two
outlets will be required to have a flow rate of 150 litres per minute, and a pressure of 1 bar G. In
practice, only one outlet has its pressure specified, but the symmetry of the network ensures that
the other node is similar. PIPENET will calculate the pressures and flow rates throughout the
network.
Note that node and link labels will be assigned automatically as the network is entered. Your
network will only agree with the above diagram if the pipe labeled 1 in the diagram above is
drawn first, then the pipe labeled 2 and finally the pipe labeled 3.
Note, also, that pipes have a notional direction from input to output, which does not necessarily
correspond to the direction of flow. The elevations shown here are changes in elevation of the
pipes, as measured from the input to the output. Thus, a positive value means that the elevation
increases as we go from the input to the output, and a negative value indicates that the elevation
is decreasing. A value of zero indicates that there is no elevation change. Note that elevation can
be specified as elevation changes on pipes, or as absolute elevations on nodes (see Spray model
options for further details).
The three pipes will come from the built-in schedule Copper/Nickel (90/10) 14 Bar G, with a
design velocity of 5 m/s.
In this first example, the details of entering a network, performing a calculation and viewing the
results will be described in some detail, with few references to other parts of the help.
Subsequent examples will contain references to topics already covered in the example, only
going into detail when discussing new features.
Therefore, it is important that all of the pipes are correctly sized, so that the fluid velocity does
not exceed the design velocity. This problem is addressed by the design phase of the simulation.
Given the required flow rates in and out of the network, PIPENET will find optimum diameters
for each pipe in the network, so that the velocity of the fluid does not exceed the design velocity.
The user must supply the required flow rate for all nozzles, and for all but one of the I/O nodes in
the network. PIPENET can then find the flow rates required throughout the network, and thus
calculate optimal sizes for the pipes.
If desired, the diameter of some (or all) pipes in the network can be set by the user.
PIPENET will then size only those pipes whose diameter has not been set.
If the user wants certain pipes in the network to be given the same diameter then the
Pipe Groupings facility should be used.
When sizing a pipe (or group of pipes), PIPENET will choose the smallest pipe size
that ensures that the design velocity is not exceeded by the fluid.
The design phase assumes that all nozzles discharge at the minimum required rate. In
most systems, there will be some nozzles that actually discharge at a rate greater than
the minimum requirement, and so flow rates and velocities in the system will rise. This
may cause the velocity of the fluid to rise above the design velocity in some pipes in the
system. These pipes will be identified during the calculation phase, and a warning will
be issued. To solve this problem, the user should set the diameters of these pipes to be
slightly larger than the designed diameters.
Calculated diameters are displayed in the Properties window and the Tabular View,
with a yellow background to the text.
More than one simulation may need to be performed in order to size all the pipes in a network.
Determine what pressures are needed to produce the required flow rates.
Select suitable pumps for the network.
Check that all demands made on the network can be satisfied. A warning will be issued
for any nozzle supplying at less than its required rate.
Check that the fluid velocity in each pipe does not exceed the design velocity of the
pipe. A warning will be issued for any pipe in which the fluid velocity exceeds the
design velocity.
The controls relating to the two phases are on the Calculation toolbar:
1. The two buttons D and C correspond to the Design and Calculation phases. If a design
phase is required then the D button is selected by default and the pipe sizing button (the
third button) is enabled.
2. The user enters the network and if he/she requires that PIPENET performs a Design
phase then pipes may be entered with undefined bores.
3. When the user has entered the network they will select the pipe sizing button to size the
undefined pipes. The calculated pipe sizes are returned to the user, where they are
displayed along with other pipe attributes; however, if another pipe sizing operation is
performed, the sizes may change if changes are made to the network.
4. Steps 2 and 3 are repeated as required.
5. When the user is happy with the network, they select the C button (the pipe sizing
button is disabled) to fix the designed pipe sizes, and then perform a calculation (fourth
button).
6. The user can revert to the design phase by selecting the D button. However, the bores
of pipes fixed in step 5 do not become unset.
Pipe grouping
The Grouping facility allows the user to specify sets of pipes in the network that are required to
have the same diameter. For example, when designing a ring main, it might be desirable for the
pipes in the primary main to share a common diameter. The facility is used by setting up groups
of pipes, labeled 1, 2, 3, etc. When the facility is used, PIPENET will ensure that all the pipes in
the same group are given the same diameter.
A pipe is added to a group by specifying the design group number in the attributes for the pipe:
In this example, pipe 1 belongs to Design group 1. Note the default design group is unset,
indicating that the pipe does not belong to a design group.
Select the menu option Options | Units and then, from the dialog that appears, select the unit
system as Metric from the system options in the upper part of the left-hand window.
Information on the other features available in this dialog are discussed in Specifying options -
Unit options:
We are going to use a built-in pipe schedule, so all we need to do is to define the pipe type.
We now need to set the maximum velocities. These are entered in the grid in the bottom right-
hand corner. We could do this by typing the value in every cell in the third column. However,
there is a much quicker way to do this. Enter the value 5.00 in the first cell of the third column
followed by Return. Now, select the cell with the mouse and, whilst holding the button down,
drag the mouse down the column so that all cells in the column are highlighted. On releasing the
mouse button, all cells will be set to the same value of 5.00. The dialog now appears as:
Other parts of this dialog box allow the user to line the pipes with some material, or to restrict
the calculation to a subset of the full schedule.
Note that if a pipe is defined as using a pipe type then, instead of explicitly entering the pipe
diameter, the diameter is selected from a combo box listing the available sizes, together with the
unset value.
Now we can add the properties to the pipe; for example, the bore and length of each pipe. Click
on the first pipe and its current properties appear in the Properties Window. Observe that, since
we are using a pipe type, some of the information is already filled in:
Click in the value field for the pipe diameter and select the value 32 from the drop-down list of
available pipe sizes, followed by Tab to move to the next field, the length. Enter a value of 1.0
for the length of the pipe, followed by either Tab or Return to accept the value. You can now
click on the second and third pipes, entering the appropriate diameters and lengths. Alternatively,
having entered the values for the first pipe, use the red right arrow button in the bottom left-hand
corner of the Properties Window to move to the next pipe (for long time users of PIPENET this
is equivalent to the Next button). Clicking the left arrow button moves to the previous pipe, if
there is one. Note that pipes are assumed to be in order of creation.
To view all three pipes, we can use the Tabular View. Select the menu option View | Data
window to display the window:
Data can be edited in this window simply by clicking in the appropriate cell. Enter a new value or
select from a list of valid options, and press either (a) Tab to move to the next field or (b)
Return.
Both the Schematic Window and the Tabular View can be displayed simultaneously by selecting
the menu option Windows | Tile horizontally or Windows | Tile vertically.
It is a good idea to save the network at this point, by selecting the menu option File | Save.
The colour of a component may revert to blue in either of the following situations:
1. If a check is performed using the check button on the calculation toolbar and the
component is found to be invalid.
2. If the file is saved and re-opened, and on re-loading the component it is found to be
invalid.
4.12 Specifications
Before sending the network to the calculator, we need to specify conditions of pressure and flow
rate at various nodes. Without these, the problem is not mathematically tractable. Also, we must
designate certain nodes as input and output nodes. We achieve this simply by adding some
attributes to some of the nodes.
Click on the first node (that is, the node with label 1 on the extreme left of the schematic), and
we observe in the Properties Window that it has no specifications and is not designated as an
input or output node. The same applies for nodes 3 and 4.
Since all the pipes have had their diameter set, the design phase of the calculation will not have
much to do. However, it must still run and we must still provide appropriate specifications for it.
The rules for design phase specifications say we must supply the flow rates at all but one of the I/
O nodes. We will set nodes 3 and 4 to have design phase flow rates of 50 lit/min.
The rules for calculation phase specifications say that there must be as many specifications as
there are I/O nodes, and at least one of them must be a pressure specification. In this case, we
need three specifications, and at least one of them must be a pressure. We will specify a flow
rate of 50 lit/min on each on the two outlets, and a pressure of 1 bar G on node 4.
Select the first node and, in the Properties window, click on the drop-down menu in the Input/
Output node, change the selection from No to Input, and then hit the Return key. The properties
window should appear as:
Now select node 3, then, in the properties window, change the input/output node status to
Output, and the Design and Analysis fields both from NO to YES. The dialog should appear as:
Now enter the values for node 4, and the Properties Window should appear as:
If you have the Tabular View window open, you can select Design or Analysis specifications
from the drop-down list of components and inspect all specifications:
4.13 Calculating
Having created and specified the network, we are now in a position to calculate its pressures
and flow rates.
Select the menu option Calculation | Calculate, or click on the Calculate toolbar button .
If you want to check that the data is correct without performing a calculation then (useful for
those users with limited run licenses) you can use the Calculation | Check menu option instead,
or click on the Check toolbar button .This option will check that the input data is valid without
performing a calculation.
For all but very large networks (200 pipes or more), the calculation will complete almost
immediately. Whilst the calculator is active, the following dialog appears:
On completion of the calculation, the dialog will display the completion status. Select the OK
button to close the dialog or the Browse button to close the dialog and display the output data.
Selecting OK simply closes the dialog. The browser can subsequently be started from the
calculation toolbar.
The results can be inspected using either the PIPENET supplied browser, Write or Word; we
shall use the PIPENET browser.
The calculation results are held in a temporary file, but may be saved to a more permanent file by
selecting the menu option File | Save As.
With most printers, the report file is suitable for printing with the page orientation set to
landscape. The scroll bars can be used to move around the report. At the top and bottom of the
vertical scroll bars, page icons can be found. These page icons will allow users to move from
one page to the next. On the left side of the horizontal scroll bar, an annotation appears,
Using the browser, text may be searched for, using the Search menu option provided in the
browser window.
When you have finished viewing the output, exit the Output Browser by selecting File | Exit.
The network can be loaded again very simply. When loading a data file, PIPENET will load any
related library files automatically.
Part
5
Example 2 - A Small Sprinkler System 52
In the left-hand window is a list of all currently defined schedules. Selecting an item in this list
displays the properties of the schedule on the right-hand side of the dialog. Data for eight pipe
schedules are built into the PIPENET Spray/Sprinkler module. A non-built-in schedule in the list
can be edited by simply selecting it in the left-hand window and editing the various attributes that
appear in the right-hand side. Note that built-in schedules cannot be edited.
The schedule name, Schedule 80 (this is the name that will appear in the left-hand
window when the data entry is complete).
An optional description (if not specified, the name will be the same as the schedule
name).
A roughness value of 0.4572 mm.
The tab key can be used to move from one field to the next. Note that, in selecting New, the
data grid in the bottom right-hand side lists all internal bores as unset. This simply means that no
value has been supplied for the corresponding nominal bore.
Now place the cursor in the internal bore field corresponding to a nominal bore of 25.00 mm,
and enter the value 24.003 (from table above). Selecting tab moves to the next field, which we
can skip (leaving the value as unset). Selecting tab again moves to the next field, where we enter
the value 37.973. Continue in this way until the last diameter has been entered. Select the Apply
button, and changes are accepted and the new schedule appears in the list in the left-hand
window.
If you are happy with the displayed results, you can either select OK to quit the dialogs or, since
we going to define other library items, simply select another tab, specifically the Nozzles tab
(since we are going to define a library nozzle in the next section).
Nozzles are entered in a similar way to schedules. A dialog is displayed in the left-hand side with
a list of available nozzles, and the data is entered in the right-hand side. This is the same for all
library components except pumps, as we shall see in the next section. Select New to add a new
nozzle, provide the data above, and select Apply to accept the changes. The dialog should then
appear as:
Pumps in PIPENET are modelled with a quadratic performance curve, and the required data are
the three coefficients A, B and C (refer to Modelling - Pumps for details). If these coefficients
are known for the pump then they may be specified directly using the Pumps - coefficients
known tab instead. However, these coefficients are not usually known, and the manufacturer
generally supplies,with each pump, a graph of the pressure increase against throughput. In this
case, coordinates from the graph can be entered, and the Pump/Fan Pre-Processor will find the
coefficients by regression analysis.
1100 1.5
1450 0.6
1. Select New.
2. Select the corresponding schedule from the schedule drop-down. This is the first
editable box on the right-hand side of the dialog. The pipe type name becomes the
schedule name.
3. Enter a C-factor value of 120.
4. Click in the first cell of the column labeled Max. Velocity in the data entry grid, and
enter the value 3.9, followed by a tab or Return. Select this cell and, with the mouse
button held down, drag the mouse down to select all cells in the maximum velocity
column. On releasing the mouse button, all cells will have the value 3.9. Alternatively,
you could enter each value independently.
5. Select the Apply button to accept the pipe type.
All pipe bores should be left unset, since the pipes are to be sized by PIPENET during the
Design phase. Note that, if the pipes are drawn in the order specified above, you should have
input and output designations as shown above. If you draw them in a different order then the
designations may not agree, but as long as the network (when completed) is topologically the
same as the following one, the results will be the same.
1. Select pipe 2.
2. Select the Fittings tab in the properties window.
3. Select the elbow in the upper window.
4. Select the + button to add the fitting.
Select the pump type from the drop down list as Example pump, followed by Return. The
properties window changes to display the pump data from the library, and the pump curve is
reproduced in the bottom of the Properties window:
1. Select the nozzle so that its properties appear in the Properties window.
2. Select the nozzle type as Example Nozzle, followed by Enter - attributes from the
library item appear in the Properties window.
3. Set the required flow rate to 150 litres/minute - a characteristic curve appears in the
lower part of the Properties window.
Associated with each bore in the pipe type is a maximum velocity, and associated with each
nozzle is a required flow rate. The design phase will, for each pipe, select the smallest bore from
the schedule that can deliver the required flow rate without exceeding the maximum velocity.
As there is one I/O node, the user must supply one calculation phase specification. When the
system is operating, it is required that each nozzle is discharging at its required flow rate or
higher. To ensure this condition is satisfied, we use the Remote Nozzle Specification option. The
calculator will find the hydraulically most remote nozzle, and specify that its flow rate is exactly
the required flow rate. In general, this will mean increasing the total flow through the system, and
that may, in turn, cause the fluid velocity to rise above the design velocity. In such circumstances,
it will be necessary for the user to set the bores for some pipes.
The Remote Nozzle Specification option provides the system with one specification, and so this
is all that is required. Select Options | Calculation and select the Remote Nozzle specifications:
It is easy to perform several simulations on a network under different conditions, once the basic
network data has been input. Specifications can easily be edited, and the different data files
saved under different names. The same library private data file and pump library can be used for
all simulations. It is recommended that the user experiments with this network. Try setting
different sets of specifications, altering the flow rate required through the nozzles, editing the
lengths of pipes, etc.
Part
6
65 Spray/Sprinkler Module
The files relating to this example are supplied with PIPENET, and are _farm.sdf, together with its
associated library file in the examples sub-directory.
The Network
Each deluge system will consist of three horizontal semicircles, spaced at 3.28 m intervals
vertically. Each semicircle will have 12 nozzles, 6 each side of the vertical feed pipe. Each tank
has two such semicircular deluge systems. The total number of nozzles protecting a tank is
therefore (3 x 2 x 12) = 72 nozzles. An elevation of a single tank, a plan of a single deluge ring
and a labeled schematic are shown in the following figures.
The semicircles are held at a distance of 0.4 m from the side of the tank.
Lengths of pipes
Nozzle spacing = x D / 24
= (15 + 0.8) /24 m
= 2.068 m
The flow rate required through each nozzle forms part of the nozzle data in the input file.
6.3 Initialisation
Title
The Options | Title option is used to enter a title for the run, as Example 1 - Condensate Tank
Deluge System.
Parameter options
In this example, we will use the Hazen-Williams equation with NFPA rules for fittings. The
default values for the density and viscosity of water will be used.
Specifications data
In this system, the specifications are particularly simple. Note that there is just one I/O node - the
input node V/1. We will look separately at the specifications required for the design and
calculation phases. Parameters are defined via the menu option Options | Module options:
Specifying units
Units will be specified as metric, as in the previous two examples.
P = (Q/K)2
where Q is the flow rate through the nozzle and K is a constant. The nozzles in this system have
a K-value of 45.0 (with P measured in bar and Q measured in lit/min). The minimum and
maximum operating pressures are 1.5 and 3.5 bar G respectively. This nozzle performance data
is contained in the library, along with the pipe schedule data.
As in the previous example, nozzles are entered into the library via the Libraries | Nozzles
menu - a dialog is displayed in the left-hand side with a list of available nozzles, and the data is
entered in the right-hand side. Select New to add a new nozzle, provide the data above and
select Apply to accept the changes. The dialog should then appear as:
In the design phase, PIPENET will find appropriate sizes for pipes in the network, based on the
assumption that each nozzle is discharging at a rate of 65.4498 lit/min, as calculated above. The
design velocity will be 4m/s for all pipes.
In the calculation phase, PIPENET will find the pressures and flow rates throughout the system
when every nozzle is discharging with a flow rate of at least 65.4498 lit/min. This is accomplished
using the Remote Nozzle Specification option, which ensures that every nozzle discharges fluid at
or above its required rate. From the results of this phase, we will be able to determine:
The pressure required at the inlet (node V/1) to ensure that all nozzles discharge fluid
at or above the required rate.
Whether, under these conditions, the fluid velocity in every pipe in the designed
network remains below the pipe's design velocity.
6.8 Specifications
Design phase specifications
During the design phase, PIPENET will assume that all the nozzles discharge at exactly their
required rate (in this case, 65.4498 lit/min). The user must supply the flow rates at all I/O nodes
except one. Since there is only one I/O node, the user needs to provide no design specifications
in this case.
Even though we are making no user-defined specifications, we must still remember to declare
node V/1 as an input node.
Using tags
We could lay out the network as in the previous examples and then, using either the properties
window or the tabular view, change all of the labels manually. However, there is a way to avoid
this using the Tag tool bar:
Tags can be assigned separately for nodes and components and, by default, both have a setting
of <NO TAG>. You can either:
Click in the data entry field and enter a new tag, followed by a Return.
Select an existing tag by selecting the drop-down button to the right of the data entry
field, and selecting from the list of available tags.
If you have a tag selected in one of the drop-downs then whenever you create a new
component, its automatically assigned numerical id will be prefixed with the specified tag and a
'/'.
Pipe data
The following table shows the data for the A branches, the other two branches will have a similar
pattern of connection.
Note that no bores are provided, since we will use the design phase to do the sizing for us.
An easier way
There is another way to generate the 3 pairs of branches; namely, using the automatic nozzle
generation tool on the Tools toolbar. We can use this tool to speed up data entry because all of
the nozzles are of the same type, and all of the pipes between the nozzles are of the same length.
There are several ways we could do this. One way is to select the nozzle generation tool, when
the dialog is displayed:
Note that the tag fields will be used independently of any setting on the tag tool bar.
This is done for each branch; i.e., 6 times. Yet another way is to create one branch pair, say the
A branch, and then use the Area tool to reproduce the other two branch pairs. It only remains to
position the branches and add in the main line.
Useful information may be obtained using colour coding; for example, the following diagram
Part
7
77 Spray/Sprinkler Module
The files relating to the first stage of this example are: _ring1.dat and _ring.pdf.
The Network
The network is a ring main in a typical process plant, feeding a number of potential fire-hazard
areas. The system is to be designed to protect five zones, one of which is the condensate tank
farm investigated in the previous example. Only one of the zones may be discharging at any given
time, but the system must be designed to cater for any of them. The pipes in the network are cast
iron. The pipes in the primary main are below the ground, and are lined with cement.
In example 3, we found that, in order to supply the deluge systems for the Condensate Tank
Farm, a pressure of 3.52 bar G is required at the deluge system inlet. In this example, we
investigate how this supply requirement can be met by a pump at PUMPS2/1. This is done in
two stages:
Stage 1
In stage 1 of this example, we find the pressure required at the pump outlet
(PUMPS2/1) in order to produce a pressure of 3.52 bar G at the node FARM/2.
Stage 2
In stage 2 of this example, we add a pump to the network at PUMPS2/1 (with an input
node IN/1, and an output node PUMPS2/1). We will investigate the pressure it
produces when supplying FARM/2. An orifice plate is used to ensure the correct
pressure of 3.52 bar G is attained. The orifice plate will be sized for us by PIPENET.
Given the pressures required at the other outlets, similar calculations could be carried
out for them.
7.2 Initialisation
Title
The Title option is used to enter a title for the run ('Example 2 - Pressures In the Ring Main').
Units
The Units option can be used to select the units to be used. In this case, we use Metric units.
Module parameters
We will use the Hazen-Williams equation with NFPA rules for fittings. The default values for the
density and viscosity of water will be used.
The dialogs for the two pipe types should appear as:
Fittings* TEE - Tee or Cross; BFLY - Butterfly valve; LRE - Long radius elbow.
The pipes in this example are taken from a built-in schedule. However, some of the pipes are
lined with cement (pipe labels with an * after the name), which is not a built-in lining. The private
data file must thus include data for cement. This data is entered by choosing the Pipe Lining
option from the Libraries | Linings menu. The data required is the lining name and roughness
value. As we are using the Hazen-Williams equation, the roughness will not actually be used, but
a value must be specified (and we use 10-5 mm).
4. Provide a minimum flow rate of 2000 litres/minute and a maximum flow rate of 13000
litres/minute.
5. Now place the cursor in the first cell in the data entry grid in the upper right-hand side
of the dialog, and enter the first flow-rate value of 2000.0.
6. Tab to the next field, and enter the corresponding pressure of 12.5.
7. Continue in this way to enter the remaining data pairs, using tab to move from one cell
to the next.
8. When all the data pairs have been entered, select the Apply button to calculate and
display the pump curve.
7.6 Specifications
Design phase specifications
As all of the pipe diameters are already set, we are not interested in the results of the Design
phase of the simulation. However, we must still supply a set of design phase specifications (in this
case, we choose to set all flow rates to the same values as in the calculation phase, as given
below).
Stage 1
FARM/2: Pressure 3.52 bar g.
Flow rate 5364 lit/min.
Stage 2
(The network having had a pump added, with input node IN/1 and output node
PUMPS2/1)
FARM/2: Flow rate 5364 lit/min.
Other outlets: Flow rate 0 lit/min.
PUMPS1/1: Flow rate 0 lit/min.
IN/1: Pressure 0 bar g.
Flow at inlets
Inlet Node Pressure Flow rate
(bar G ) (lit/min )
PUMPS1/1 5.543 .0000 *
PUMPS2/1 5.752 5364.
Note that an asterisk (*) after a value indicates that this is a specification.
Stage 2 Results
When the pump is added, a pressure of 8.543 bar G is produced at the node FARM/2. In order
to reduce this pressure to the required pressure of 3.52 bar G, an orifice plate can be added to
the pipe FARM/2. This is done using the Orifice Plate tool. The pressure drop required across
the orifice plate is (8.543-3.52) = 5.023 bar G. This forms part of the data for the orifice plate.
Given this required pressure drop, PIPENET can size the orifice plate for us if we carry out
another calculation run - the required diameter is 69.3567mm.
The files relating to the solution to Stage 2 of this problem are also stored in the Examples
directory, as:
pipenet\examples\_ring2.dat
_ring.pdf
_ring2.out
_ring2.pmp
Part
8
85 Spray/Sprinkler Module
The files relating to this problem are supplied with PIPENET, and are: _maint.dat and _maint.
pdf.
In this example, we will assume that the basic system is installed, and that a new fire hazard over
an area measuring 20 feet by 70 feet is to be covered with a larger application rate than was
originally assumed. To achieve the greater cover, we first have to show that the installed system
will not be able to cope, and then add some new pipes and nozzles to cover the new hazard.
In this example, we are not concerned with the pump(s) used to feed the system, although it
would usually be necessary to consider whether the installed ones were inadequate for the new
hazard.
The system is illustrated below. Note that not all the nozzles are marked, and some pipe and
node labels have not been shown.
8.2 Initialisation
Entering the network details
Each node with the tag NEW1 has a nozzle with the same label (e.g., node NEW1/6 has a
nozzle NEW1/6). The two risers NEW2 and NEW3, which spring from slightly different points
on MAIN3, are otherwise identical to NEW1.
Fittings* EL90 - standard 90 Elbow; TEE - Tee or cross; EL45 - standard 45 elbow.
In a SPRAY system, all the nozzles are usually open, and will discharge when water is supplied
to them; whereas, in a SPRINKLER system, each nozzle is individually controlled, either with a
fusible plug or electronically. When modelling SPRINKLER systems, it is necessary to specify
some nozzles as being turned on. To change from the default of a SPRAY system, select the
menu option Options | Spray options and then the Sprinkler option:
Nozzle Data
The existing nozzles are all of the same type, with a K-factor of 95. The operational range is
1.39.5 bar G. Note that these data are in metric units, while the rest of the data is in Imperial.
Preliminary Calculations
First, we must convert the nozzle data to the same units as the rest of the problem. In UK gal/
min and psi G, the K-factor is 5.4871, and the operational range 18.856137.79 psi G.
The required application rate over the new hazard is 0.6 UK gal/ft2 min.
This is above the maximum operating pressure for this nozzle type, so we can conclude that the
present system cannot cope. With 18 additional nozzles, the required flow rate per nozzle
becomes:
= 840/(12+18)
= 840/30
= 28 UK gal/min
This is within the operating range for the nozzles, as 18.856 < 26.04 < 137.79 psi G.
Parameter options
In this example, we will use the Hazen-Williams equation with NFPA rules for fittings. The
default values for the density and viscosity of water at 20C will be used.
8.3 Specifications
Design Rules require that the area to be protected receive a certain total flow rate. In this case,
this is 0.6 UK gal/ft2min over 1400 ft2. As calculated above, if the 30 nozzles in the area each
discharge 28 UK gal/min, this requirement will be met. PIPENET can deal with this situation in
two ways:
Ensure that the total flow rate into the system (and, as the nozzles are the only output,
the total flow rate into the area) is equal to the sum of the flow rates required at each
nozzle (mass balance option).
Ensure that each nozzle individually meets its required flow rate, so that the area is
covered uniformly (remote nozzle specification option).
In this example, we will investigate both, to see whether there is a significant difference in the
results.
If we use the Remote Nozzle Specification option, we must give one more calculation phase
specification. In this case, we simply specify that node MAIN2/7 have a flow rate of 0; we are
simply copying the design phase specification (see the Technical Manual for a full description of
the Remote Nozzle Specification option and making specifications). Even if we are making no
user-defined specifications on it, we must still remember to declare node MAIN1/1 as an input
node.
Results
Both simulations should run smoothly, and in neither one does the flow exceed the designed
speeds or pressures of the network. If you run the simulation and look at the "Flow Through
Nozzles" section of the output browser file, you should observe that the specifications are indeed
met by the simulation. Using the Mass Balance Option, we ensure that the system delivers
exactly 840 UK gal/min. However, the Remote Nozzle Specification only uses 6% more water
and ensures that a more uniform protection is provided. The pumps would have to deliver 47.4
psi G in this case, rather than 43.3 psi G if the Mass Balance is used.
PIPENET has provided an assessment of the feasibility of installing the new risers, and other
configurations could just as easily be tested. If they require the enlargement of some of the
existing pipes, because these exceed their designed velocities, PIPENET issues a warning in the
report file.
Part
9
91 Spray/Sprinkler Module
9 The Schematic
9.1 Schematic Window
The Schematic window is the primary means of entering and viewing networks. It closely
resembles the schematic window of earlier products, but has a number of improvements.
When the window is first displayed, it is presented with a light-grey background suitable for
general viewing. The background colour may be changed to white or black. However, for
coloured links and text, it will generally be found that a white background is unsuitable for
viewing.
New elements are added by selecting the appropriate element tool from the tool palette, and
then placing and drawing the component using the mouse.
All labeled elements created via the schematic are automatically assigned a unique label. Labeled
elements include nodes, link elements and attribute elements. Numeric labels are used (no tags)
with each component type having its own set of unique labels.
The background colour and the font sizes used for labeling components can be changed using
the Display Options dialog.
Schematic Underlay
A facility has been included whereby a graphic may be imported and displayed as a background
to the main schematic. Display of this underlay is enabled and disabled via the View menu. The
underlay may be zoomed independently of the main network to achieve relative scaling and
registration. Zooming the network results in the underlay being zoomed by the same selected
zoom factor. In normal use, the procedure to use an underlay commences with a new network:
Currently, the image is loaded on the first request to display the underlay (see the View menu).
Once loaded, the underlay may be zoomed to establish the relative scale between the underlay
and the network. Generally, the procedure will be as follows:
The display of the underlay can be turned on or off via the View menu. When turned off, the
underlay will track any changes to the scale of the network, retaining the correct relation.
The zooming of the underlay is independent of the network, whereas zooming the network also
zooms the underlay to maintain relative scales.
Currently, the underlay cannot be translated left-right or up-down, although the network can be
moved using the Area Tool.
Delete a component.
Add waypoints.
Delete waypoints.
Insert a node in a pipe.
Reverse the direction of a component (which will negate the elevation change).
Copy and paste the attributes of a component.
The selection tool can also be used for dragging nodes to new positions, and for dragging pipe
components, such as orifice plates, along the length of a pipe. To drag a node or a component,
click the left mouse button and, whilst holding the button down, move the mouse to the desired
position and release the mouse button. Note that, if a node is dragged, all of the components to
which it is connected also move with it.
Adding a waypoint
If you left-click on a pipe, and with the mouse button held down, move the mouse then a
waypoint will be inserted at the selected point in the component link.
Copy/Paste
To copy the attributes from one source component onto another target component of the same
type:
1. Right-click on the source component and select the Copy option (alternatively, use
Ctrl-c).
2. Right-click on the target component and select the Paste option (alternatively, use
Ctrl-v). All attributes are copied from the source component to the target
component.
If the source and target components are pipes then, prior to the copy, all fittings are removed
from the target pipe and replaced with the fittings from the source pipe.
If Paste (Incl. layout) is selected instead of Paste, the process is very similar, except that any
waypoints and components (for example, orifice plates) are also copied from the source to the
target.
Explode Node
This facility can be used to break all of the links meeting at a designated node. To explode a
node, simply right-click on the node and select the Explode node option.
To zoom the network, hold down the left mouse button and drag the cursor until the network
is at the required size. Dragging to the right will enlarge the network, dragging to the left will
minimize it.
To pan across the network, click the left mouse button whilst in the schematic window, and
move the mouse in the direction you wish to pan. Click the left mouse button again to cease
panning. Whilst panning, if the cursor is moved to the edge of the window, the network will
scroll along until the end of the scroll bar is reached.
Pan and zoom can also be achieved using the mouse wheel, if one is present.
To use the tool, click the left mouse button at the point that is to be the top-left corner of a
rectangular area. Whilst holding the mouse button down, move to the point that is to be the
bottom-right-hand corner of the rectangle, and release the mouse button. A dashed outline of the
defined rectangle is drawn, and all nodes and components that lie completely within the rectangle
are selected.
Via the Edit menu, or by right-clicking, the selected items can now be moved, deleted, mirrored,
inverted, copied and nozzles turned on/off. Full undo/redo is available for all operations with this
tool.
Selected items
The items marked as selected are:
Note that if
you are using
copy/paste to
copy from
instance of a
module to
another
instance of the
same module,
ensure that
both instances
are using the
same unit
systems.
Note that, for the purposes of the mirror and inversion operations, the centre of the polygon is
the centre of the enclosing rectangle.
1. Define the first point by holding the shift key down and clicking the left mouse button.
2. Define the second point by moving the mouse to the location of the second point and,
whilst holding the shift key down, click the left mouse button.
3. Repeat step 2 for as many points as you require to define the polygonal area.
4. When you have defined all the points, right click the mouse anywhere in the schematic
(without the shift key being down) to close the defined polygon - the last defined point
is then connected to the first.
Via the Edit menu, or by right-clicking, the selected items can now be deleted, mirrored,
inverted, copied and nozzles turned on/off. Full undo/redo is available for all operations with this
tool.
Selected items
The items marked as selected are:
Enter the text that is to appear in the text field and then select either OK to accept the text or
Cancel to abort. Text options can be specified in the Properties Window, and include typeface,
size, style (normal, bold, italic or bold and italic) and colour.
To change the colour of the text, click on the arrow button in the cell. Selecting the drop-down
arrow in the Colour field will display a small selection of colours:
1. Click on a text element and its properties can be edited in the Properties window.
2. Click and drag to move the text.
3. Right-click on a text element and select Delete from the pop-up menu to delete the
text.
When the component is drawn it will be displayed in blue to indicate that this is a new
component for which the component defaults have been used. If any changes are made to the
component's attributes then it will change to black.
Waypoints
For some components, specifically those for which both an input node and an output node is
displayed (excluding components such as spray nozzles and Transient caissons), additional
intermediate points may be specified between the input and output nodes. These intermediate
nodes, or waypoints, do not form part of the hydraulic network and merely exist to aid in the
layout of the schematic. To add waypoints at the time a new component is added, proceed as
follows:
1. Place the cursor at the point where you want the input node to appear, and left click.
2. If the selected point coincides with an existing node then that node becomes the input
node; otherwise, a new node is created and displayed at the selected point.
3. A line representing the link element is drawn and tracks mouse movements.
4. To add an intermediate point, hold the shift key down and left-click the mouse at the
desired position. This may be repeated as many times as you like to create multiple-
segment pipes and ducts.
5. If you left click without holding down the shift key then the output node is created.
6. If, after creating the pipe or duct, you want to add additional waypoints or to move
waypoints, use the selection tool.
7. The creation of a pipe or duct can be aborted any time between the creation of the
input node and the output node by pressing Escape.
If you have selected the display of direction and/or the presence of fittings on pipes then the
The colour of a component may revert to blue in either of the following situations:
1. If a check is performed using the check button on the calculation toolbar and the
component is found to be invalid.
2. If the file is saved and re-opened, and on re-loading the component it is found to be
invalid.
With any of the attribute element tools selected, it is possible to move any attribute element along
the length of a pipe using click and drag; see, also, the section on the Selection Tool.
To print a schematic, select the File | Print option, which will display a dialog box showing a
range of print scales and the number of pages required to print at each scale, and offering the
option to print all pages or a selected range of pages.
However many pages are required to display the schematic, the network will be displayed
centred across all pages. Each printed page will show the network title, the date, and the page
number in the form Page m of n. Page fit can be selected to print the complete schematic on one
page. If the option Visible window only is selected, only that part of the network visible in the
schematic window will be printed on a single page.
Printing will be to the currently selected printer with the currently selected page orientation. To
change either or both of these, select the File | Print Setup menu option to display the standard
Windows print setup dialog.
The appearance of the printed schematic can be previewed using the File | Print Preview
option.
There is another way to move around the network, highlighting components in turn, using the four
cursor keys on the keyboard. This is best illustrated by the following example. With pipe 2 the
currently selected component, and all component directions being from left to right, selecting the
right cursor key moves to pipe 3, and selecting the left cursor key moves backwards to pipe 1.
Selecting the right cursor key will move to the uppermost component on the right; i.e., pipe 4:
To move to pipe 5 from pipe 4, simply select the down cursor key:
Selecting the down cursor key again will move to pipe 6, whilst selecting the up cursor key will
move back to pipe 4.
If the component is reversed (i.e., the input node is to the right of the output node) then selecting
the right cursor key will move to the link on the left. Similarly, selecting the left cursor key will
move to the link on the right of the current link. So, selecting the right cursor key is interpreted as
a move in the component direction; and the left cursor key, as a move in the reverse direction.
If a mouse wheel is present then this can also be used for panning and zooming, the operations
Zoom
Press the Ctrl key and move the mouse wheel up and down to zoom in and out of the
schematic. The point of the graph directly under the mouse cursor will stay the same.
Panning
Click the mouse wheel and, whist holding down the mouse wheel, move the mouse to
pan the network.
Part
10
The Tabular View 104
Each tabular view displays the information for one component type selected from the drop-down
list at the top of the window:
Sorting
Components are initially displayed in data entry order; however, rows may re-ordered by
clicking in a column heading. For example, to sort pipes in ascending order of diameter, click on
the heading for the pipe diameter column. To sort in descending order of diameter, click on the
column heading a second time. Clicking on a heading toggles between ascending and
descending order.
Cell shading
Cells are normally displayed with a white background; however, the following cell shadings may
also be observed:
Cells coloured yellow (currently, only for pipe sizes) indicates that the displayed size has
been calculated during the design phase (in the Standard Module and the Spray/
Sprinkler Module).
Selecting a row
Left-click on the leftmost cell of the row to select a row.
Editing a cell
The contents of editable cells (non-editable cells will be grayed out) are either of the direct data
entry type or of the drop-down selection type. For example, in the pipe tab, pipe bore and pipe
length are both of the direct data entry type - simply click on the cell to edit or re-enter the value.
The pipe status is selected from a drop down list, and is one of Normal, Broken or Blocked.
Printing
The current grid can be printed by selecting the Print button.
10.2 Validation
All attributes are validated as they are entered:
Fields are validated to check that they are of the correct type; that is, if a field must
contain only numeric data then only entry of numeric digits and optional sign and
decimal point are permitted.
Simple range checking is carried out to ensure that numeric values are within range; for
example, pipe bores must always be positive, filter coefficients must always be
negative, temperatures must be at or above absolute zero, and so on.
If an invalid entry is made then a simple dialog is displayed indicating the fault; for example:
Clicking OK leaves the error highlighted, and the value must be corrected before moving on to
further editing.
Paste-in-Column
Since the operation of reproducing a single value in a column is common, a shortcut is provided
via the Paste-in-Column option in the popup menu. Simply point to the value to be repeated in
the column and select Paste-in-Column.
Select the target cells in the same manner, only now select the Paste option in the popup menu.
Note that the source and target selections must start and end in the same column and be of the
same shape.
Copying a rectangular group of cells from one area of the grid to another
Select the source area as follows:
1. Left-click in a cell at one corner (top-left, for example) of the rectangular group.
2. Whilst holding down the shift key, left-click on the diagonally opposite corner cell to
select the group.
3. Right click on any cell within the group to display the popup menu.
4. Select the Copy option.
Select the target area in the same manner, only now selecting the Paste option in the popup
menu. Note the following:
The source and target areas must have the same shape; i.e., they must be the same
number of columns wide and the same number of rows high. Note, however, the one
exception to this in the next paragraph.
The source and target areas must start and end on the same column.
1. Select the cells from the source row as described in "Copying a contiguous group of
cells from one row to the corresponding cells in another row".
2. Select Copy from the popup menu.
3. Select the target cells as described in "Copying a rectangular group of cells from one
area of the grid to another".
4. Select Paste from the popup menu.
5. Repeating a value.
Part
11
109 Spray/Sprinkler Module
11 Specifications
11.1 Introduction to Specifications
In order to solve a network, boundary conditions must be provided in the form of either (a) flow
or pressure specifications on input and output nodes or (b) pressure specifications on internal
nodes. Note that an internal node is any node that is neither an input nor output node. These
specifications must obey the rules described more formally in the following Specification Rules
section.
Many of the aspects of specifications can, however, be described by reference to a simple single
pipe network.
With this simple example, an initial approach might be to provide equal flow specifications on
both the input and output nodes. However, since the output flow must equal the input flow, one
of these specifications is not required. If we provide two identical flow specifications then there is
redundancy and there is no unique solution to the network. If instead, we provide two different
flow specifications then the specifications would be inconsistent, and again there would be no
solution.
With one flow specification provided at one node, we know the flow at the other node.
However, we do not know the pressure. In fact pressures cannot be determined without the
specification of a reference pressure. So, for our simple network, it turns out that we must
provide two specification, one of which must be a pressure specification. Thus, there are three
possibilities:
1. We provide a flow specification on the input and a pressure specification on the output.
2. We provide a pressure specification on the input and a flow specification on the output.
3. We provide a pressure specification at both the input and output.
This can be generalized to larger networks with any number of input and output nodes to the
simple statement that:
The number of specifications must be equal to the total number of input and output nodes, and
at least one of the specifications must be a pressure specification. See Specification Rules for
further details and the special considerations that apply to the Design Phase, nozzles and remote
specifications.
Disjoint Network
A network is considered disjoint if it is in two or more unconnected parts, or sub-networks. The
following is an example of a simple disjoint network, with two sub-networks A and B:
Since each sub-network is solved separately, the specifications in each sub-network must be
valid. Thus, in the above example there must be a total of four specifications, with sub-networks
A and B each having at least one pressure specification.
It is obvious from this example that the network is disjoint. However, disjoint networks can also
arise in a less obvious way from the use of breaks and blocks in pipes. Consider the following
simple three-pipe network, with the central pipe blocked
The network was initially set up with the pipe in the normal, unblocked state, and the calculation
ran satisfactorily with a flow specification provided at the input and a pressure specification
provide at the output. When the blocked pipe was added, the network refused to calculate -
why? Simply, that the blocked pipe has split the network into two disjoint networks, one
consisting of the single pipe A/1 and the other of the single pipe C/1. Whilst the network
containing the pipe C/1 includes the original pressure specification, the A/1 network does not
have a pressure specification. It should be noted that, with a blocked pipe, a zero flow
specification is added to the node at each end of the block, hence there are correct number of
specifications.
Design phase
1. There must be one (and only one) pressure specification, which may be on an input
node, an output node or an internal node.
2. In a network with a total on n input and output nodes, all but one of these nodes must
have a flow specification.
Calculation Phase
1. There must be at least one pressure specification.
Block
Each of the input and output nodes of the break is assumed to have an associated zero
flow specification.
Break
Each of the input and output nodes of the break is assumed to have an associated
pressure specification.
Each break or block may separate a single network into two sub-networks, and since
specifications must be valid in each sub-network, problems can occur. The most likely problem
to arise is that the presence of a blocked pipe breaks a valid network into two sub-networks,
with one of the sub-networks having no associated pressure specification.
1. By clicking on a node, the details of the specification appear in the Properties window,
where they may be edited. If no specifications have been attached to the node then the
properties window appears as:
2. By displaying the tabular view window and selecting the component type as Node to
display all nodes with details of any specifications attached or Design phase
specification or Calculation phase specification as required.
Adding specifications
Specifications are added by selecting the appropriate node and then setting the status of the
node as an I/O node as appropriate, changing the Design specification drop-down to YES if you
want to add a design specification, and the Calculation Specification drop-down to YES if you
want to add a calculation specification. Changing either of these will result in the display of
additional attributes. For example, adding a calculation phase specification will change the
display to:
Removing specifications
Specifications are removed simply by clicking on the node and changing the Design specification
and/or Calculation specification options to NO.
Checking specifications
Specifications are checked during the performance of a check operation, along with height
checking and general consistency checking. This can be initiated by a user selecting the
Calculation | Check menu option or, more readily, by selecting the Status tab in the Properties
Window.
A number of messages, relating to specifications can appear in the status window. Most will be
errors preventing a calculation from being performed. Specifications are checked separately for
the Design and Analysis phases.
By definition, one can only assign the flow rate at one nozzle, and the flow rate must be given by
the user. This is achieved using the Options | Calculation dialog, but only when the User
defined specifications option is selected:
In this example there is a specification on nozzle 9 with a flow rate of 150 l/min.
Note that if there are any overboard dump valves present in the network then the Remote
nozzle specifications and Mass balance specifications options will be greyed out. This is
because overboard dump valves can only be used with the User-defined specifications
option.
Part
12
Status Checking 116
12 Status Checking
12.1 Status checking
A facility is provided for checking the correctness of the currently defined network prior to
attempting to perform a calculation. This will check for component errors, specification errors
and height-elevation inconsistencies. This facility is activated whenever a calculation is attempted
or, explicitly, by selection of the Calculation | Check option, when the following window is
displayed:
If there are no errors or warnings, the window contains a single status line, as depicted above. If
there are errors and/or warnings, these are shown on separate lines, with the first column
showing a component label (where appropriate) and the second column showing a description of
the error. All components found to be in error (for example, a zero length pipe) will be coloured
blue.
Warnings are shown in black text, and indicate possible problems with the network. Errors are
shown in red text, and indicate problems that may prevent a successful calculation.
If a component number is displayed in a cell then double-clicking anywhere in the row will
highlight the component in the schematic window, scrolling the schematic window to display the
component if it is not already visible.
For reference purposes, a copy of the check results can be printed via the Print button.
Double-clicking in the first column of a row containing an error will select a node in the sub-
network containing the error.
If two or more height errors are found then selecting the Common Height Errors button will
highlight all of the pipes that appear in two or more loops. This is not guaranteed to pinpoint the
Part
13
Colour Schemes 120
13 Colour Schemes
13.1 Colour Schemes
A colour scheme is a simple set of rules used for the colouring of components on the schematic.
At any time, two colour schemes may be in use, one for colouring nodes and one for colouring
pipes/nozzles. The two colour schemes can be selected from an application-specific set of colour
schemes. There is a default colour scheme for both nodes and pipes/nozzles, which provides the
default colouring of:
In all other situations, a component is displayed in the default colour: black (for white and grey
backgrounds) or white (on a black background).
Each colour scheme can assign one of six colours to a component: RED, ORANGE, GREEN,
CYAN, BLUE and MAGENTA. If a component falls outside of the rules for a colour scheme, it
will assign a default colour of black (on a white or grey background) or white (on a black
background).
1. Simple schemes where components are coloured according to the value of a single
attribute or result.
2. Complex schemes where components are coloured according to some logical
combination of one, two or more attributes and results.
< v1 RED
v1 & < v2 GREEN
v2 & < v3 BLUE
v3 & < v4 CYAN
v4 & < v5 MAGENTA
v5 ORANGE
If intervals are not defined, they will be provided automatically, based on a suitable scaling of the
known values for the attributes or results. Note that, for results, the intervals are calculated on
the completion of a calculation.
Colour schemes are displayed and edited via the Classes dialog.
This consists of two columns, one for nodes and the other for pipes/ducts. At the head of each
column is a combo box for selecting the colour scheme. Note that these two combo boxes have
a dual purpose in also selecting which attribute is displayed above a component in the schematic.
Below the combo box are five edit boxes used for defining the six intervals. The coloured boxes
alongside the edit boxes define the colours for the six intervals. The edit boxes will be grayed out
if the selected colouring scheme does not use intervals.
Immediately below each column of five edit boxes are two check boxes:
Colours On - used to enable/display colours. If this box is unchecked then the default
colouring scheme will be used. However, the selected attribute will still be displayed
when the Display Attributes buttons are selected.
Auto classify - used to select automatic calculation of ranges following completion of
a calculation. If this box is checked then the five values defining the six intervals will be
re-calculated each time a calculation is performed.
Use modulus - if this is selected then classification will not take the sign of the attribute
into consideration.
The final three buttons are used to select the way in which the intervals are coloured, the default
being the six colours ordered as RED, GREEN, BLUE, CYAN, MAGENTA and ORANGE.
The ordering of the colours may be reversed by selecting the Reverse colours button. As an
alternative to the six colours, a single colour may be selected to be represented in six shades.
Selecting the Graduated button displays a pop-up window via which the colour can be selected.
Finally, it is possible to change the default colours by left-clicking on one of the coloured boxes,
when a colour selection pop-up appears. For example, in the following image the user has left-
clicked on the orange box.
Selecting a colour from the pop-up will result in the selected colour replacing the colour in the
box.
The two combo boxes for selecting the colour scheme (and, hence, the attribute to be displayed
on the schematic) are reproduced on the Options Toolbar. The Options toolbar can also be
used to display legends (one for nodes and one for pipes) on the schematic. For example:
The legends can be moved around by clicking and dragging with the mouse.
Values are displayed with the correct sign for directional components; i.e., negative if the flow is
in the opposite direction to the component direction, or positive if it is in the same direction.
Note that, for pipes, results are shown on the Schematic or in the Properties Window with the
correct sign. For colour coding, the absolute value is used; for example, +10 m/s will be coded
using the same colour as -10 m/s. This means that the interval values specified in the dialog
should be zero or positive.
Complex rules
Complex rules allow the user to define a colouring rule in a more flexible manner. This is best
This shows the dialog for entering a complex rule for a pipe; the corresponding dialog for a node
has the same layout. It comprises:
The above example states that each pipe with a bore greater than 100 mm, where the calculated
velocity in the pipe exceeds 10 m/sec, is to be coloured red.
The legend window can be selected for display as with simple rules, an example of which is as
follows:
13.2 Tagging
In addition to
the default colour scheme, one additional tagging colour scheme is provided, and it
is common to all application modules. This scheme can be used to colour components based
purely on user selection. This operates as follows:
Now if the tagged colour scheme is selected, tagged items will be displayed in CYAN (this
colour may be changed via the Options | Display Options menu item).
Tagged items can be made untagged by selecting the menu option Tools | Remove Tags.
Regardless of the chosen background colour, the schematic is always printed on a white
background.
Part
14
Elevation Profile and Hydraulic Grade Line 126
Before a profile can be plotted, a path must be defined using the Tools | Make Path menu
option. To use this tool, simply select two or more nodes and then select the Tools | Make
Path menu option to select all components joining the selected nodes. To select more than one
node at a time, simply hold down the Ctrl key whist selecting the nodes.
The path found is the shortest path, where shortest is in terms of the smallest number of nodes.
Having created a path, the elevation profile will be displayed with the nodes plotted from the
leftmost of the two nodes selected to the second, rightmost node. The vertical axis displays an
elevation scale in the user-selected units, and the horizontal axis corresponds to the distance (as
measured from the starting node).
Right-clicking with the mouse displays a popup menu with the following options:
Show values - selecting this option will display the value at a point in a bubble tool-tip.
Label Point - if the mouse is positioned on or close to a node, this will label the node.
Add Text - add text annotation to the plot.
Add Arrow - add an arrow to the plot.
Add arrowed text - add arrowed text to the plot.
Copy - copies the plot to the clipboard, from where it can be inserted into, for
example, a Word document.
Edit properties - selecting this option will display a tabbed dialog, via which it is
possible to edit the title, labels, styles and the axes. These properties can be saved as a
template.
The following figure shows the same plot, but with some nodes labeled and an arrowed text
item:.
The Elevation profile has a number of uses, the major two being:
For the first of these, the following figure shows the elevation profile, after a calculation has been
performed, with the hydraulic grade shown.
In the second of these, clicking on the line in the Status Window will display a height error and
highlight the loop in the network, as well as making a closed path. The following depicts the
profile of a height check error (with labeled nodes), which clearly indicates the error. Note that
the first and last nodes shown on the plot are the same physical node and so their differing
heights on the plot illustrates the scale of the error.
If the static pressure is known then we can also use the relation:
where P is the static pressure, Z is the elevation, is the density, and g is the acceleration due to
gravity.
Following a calculation, the Hydraulic grade line can be displayed in the elevation profile window
by creating a path between two nodes in the network, using the Tools | Make path facility.
Note that, for a hydraulic grade line to be produced, the fluid must be either (a) a liquid, with no
temperature items in the network, or (b) a gas for which the temperature unit is not Kelvin.
Part
15
131 Spray/Sprinkler Module
Selecting the tool via the Tools | Add Multiple Pipes option produces the dialog:
The left-hand window contains the attributes that are to be set for each pipe when the OK
button is selected; the right-hand window contains the set of distance-elevation pairs. Above this
right-hand window is the number of pipes to be created, which can be changed using the up-
down buttons to the right of the displayed value. The distance is incremented automatically by
the length of the pipe specified in the left-hand window. Values in the right-hand window can be
edited.
The check box at the bottom of the dialog indicates that the pipe run will be displayed in a
profile, with pipes being drawn to scale according to their lengths. If this box is unchecked then
the window appears thus:
Here, the pipe run is displayed in plan at a specified angle of inclination, with angles being
measured anti-clockwise from the horizontal. Selecting the option Use proportional lengths
draws the pipes to scale, according to their lengths.
Data can be copied from a spreadsheet and pasted into the right-hand window, the number of
rows being set automatically from the number of data pairs copied. This facility must be used
with caution, since the data from the spreadsheet must be arranged in the same column order as
that used in the right-hand window, also the units must agree with those in the column headings.
Undo/redo is available with this facility.
Part
16
Autolayout and Spray Diagrams 134
Object type
This defines the type of object that requires protection. The options are:
Tanks Area
Protection
Vertical Rectangle
Cylinder
Horizontal
Cylinder
Sphere
Vessel dimensions
Specifies the dimensions of the object.
Pipes
This section defines the type and diameter of pipe you wish to use in the Autolayout network.
The pipe diameter may be set to "Unset" if you wish to use the automatic pipe sizing feature.
Labelling
If you want Autolayout to automatically label the generated components you can define the tags
to be used in this section. If the Label components by range check-box is checked, the labels
of the generated components will be numbered according to the ranges with which they are
associated, based on the specified tags: for example, if the nozzle tag is NOZZ and this option
is enabled, the third nozzle on the second range will be labeled NOZZ2/3.
Options
See the relevant help entry below for explanations of the different options in each case.
o Vertical Cylinder
o Horizontal Cylinder
o Sphere
o Rectangular Area
Tab display
This area displays the content of the currently selected tab.
Preview Tab
This tab shows a 3D view of the generated model. The model can be viewed from different
angles of rotation and elevation by moving the horizontal and vertical sliders respectively (note
that the vertical slider is inverted, so that moving the slider to the bottom displays the
model as viewed from above). In addition, rotation in the preview tab defines the rotation of
the model when placed in the schematic. The notification to the right of the horizontal slider
indicates when the model would appear orthographic in the schematic. If there is an error in
generating a model, or the model is not completely specified then no model is displayed.
Nozzle Tab
This tab shows a table of all nozzles in the nozzle library, along with information about the model
that would be produced if each nozzle were chosen. This is where nozzles are selected to be
used in the model.
In order to generate a model, enter valid data as described in the options pages for the chosen
object type. In the nozzles tab select the nozzle you wish to use. If a valid nozzle has been
chosen then a model will now display in the preview tab. Changing any of the options will
automatically update the model/nozzle table depending on the currently selected tab. To manually
force an update, click the Generate model button.
Spray Diagrams
The Generate Spray Diagram button launches the Spray Diagrams tool, which can be used to
review the effectiveness of the model in protecting the target.
When placed into the schematic, the size of the model is determined by the (Schematic:
Preview) size ratio, which is the ratio of the size of the model in the schematic at 100% zoom to
the size of the model as displayed in the preview tab.
The rotation (controlled by the horizontal slider) of the model in the preview tab controls the
rotation of the model in the schematic.
The schematic is placed in the centre of the current view in the schematic. If this would cause it
to overlap with any part of the network in the schematic then the model is placed either to the left
or right side of the network, whichever is nearer to the current view. To move the model, use
Ranges
This section specifies the ranges in the network (a range is a series of pipes at constant elevation
upon which nozzles are fitted). The Separation distance measures the vertical distance between
ranges.
Start
from
top:
A
range is
placed
at the
top of
the
cylinde
r. An
additio
nal
range is
placed
below
the
previou
s one
until no
more
ranges
will fit.
Start
from
botto
m:
A
range is
placed
at the
bottom
of the
cylinde
r. An
additio
nal
range is
placed
above
the
previou
s one
until no
more
ranges
will fit.
Rang
es at
top
and
botto
m:
For this
the
Separa
tion
distanc
e
becom
es the
Max
separat
ion.
Ranges
are
placed
at the
top and
the
bottom
of the
cylinde
r.
Additio
nal
ranges
are
then
placed
evenly
betwee
n them
so that
the
distanc
e
betwee
n
ranges
is not
greater
than
the
Max
separat
ion. As
few
ranges
as
possibl
e are
used to
achieve
this.
The Use curved pipes check-box tells Autolayout to model the network using curved pipes.
Only the pipes that make up the ranges will be modelled as curved pipes for this object type,
and this has the affect of increasing their length.
The Display curved pipes check-box tells Autolayout to draw the relevant pipes as curves.
Curved pipes are approximated in the schematic by using multiple way-points (increases
Nozzles
These options define the nozzles of the layout. Nozzles are directed so that the centre line of their
spray cone is orthogonal to the vessel surface.
There are two ways for Autolayout to decide how many nozzles to put on each range. The first
is to explicitly tell it, using the Nozzles per range option. The second is to use the Min spray
overlap option. With this selected the number of nozzles on each range will be increased until the
spray patterns of neighbouring nozzles overlap by at least this amount.
The Nozzle to vessel distance defines how far away nozzles are from the surface of the cylinder.
There are also two ways for Autolayout to decide how much flow is required at each nozzle.
Again, the first way is for you to tell it, using the Flow per nozzle option. The second is to define
the Average flow density on the surface of the cylinder. Using this Autolayout can calculate the
flow required at each nozzle based on their efficiency (the fraction of their spray that hits the
vessel).
Ranges
This section specifies the ranges in the network (a range is a series of pipes at constant elevation
upon which nozzles are fitted). The Upper/Lower Separation distances measure the vertical
distances (as measured along the surface of the cylinder) between ranges in the upper/lower
halves of the cylinder respectively. This allows a finer degree of control over the network
(NFPA 15 rule 7.4.2.4 states that surfaces below the equator of a horizontal cylindrical vessel
are not considered wettable from rundown, and hence a denser arrangement of ranges is usually
required in the lower half).
Start
from
poles
:
A
range is
placed
at the
north
pole,
with
additio
nal
ranges
placed
in the
upper
half of
the
cylinde
r so
that the
distanc
e
betwee
n them
is equal
to the
the
upper
separat
ion
(when
measur
ed
along
the
surface
of the
cylinde
r). The
placem
ent of
ranges
in the
lower
half is
analago
us.
Start
from
equat
or:
A
range is
placed
at the
equator
of the
cylinde
r.
Ranges
in the
upper
half of
the
cylinde
r are
placed
so that
the
distanc
es
betwee
n them
is equal
to the
upper
separat
ion
(when
measur
ed
along
the
surface
of the
cylinde
r). The
placem
ent of
ranges
in the
lower
half is
analago
us.
Rang
es at
poles
and
range
at
equat
or:
For this
option
the
Upper/
Lower
Separa
tion
distanc
es
becom
e
Upper/
Lower
Max
separa
tion
distanc
es.
Ranges
are
placed
at the
poles
and at
the
equator
of the
cylinde
r. In
the
upper
half of
the
cylinde
r
additio
nal
ranges
are
then
added
so that
the
distanc
e
(along
the
cylinde
r)
betwee
n
ranges
is not
greater
than
the
upper
max
separat
ion. As
few
ranges
as
possibl
e are
used to
achieve
this.
The
placem
ent of
ranges
in the
lower
half is
analago
us.
The Use curved pipes check-box tells Autolayout to model the network using curved pipes.
Only certain pipes that make up the risers will be modelled as curved pipes for this object type,
and this has the affect of increasing their length.
The Display curved pipes check-box tells Autolayout to draw the relevant pipes as curves.
Curved pipes are approximated in the schematic by using multiple way-points (increases
complexity of network in the schematic).
Nozzles
These options define the nozzles of the layout. Nozzles are directed so that the centre line of their
spray cone is orthogonal to the vessel surface.
There are two ways for Autolayout to decide how many nozzles to put on each range. The first
is to explicitly tell it, using the Nozzles per range option. The second is to use the Min spray
overlap option. With this selected the number of nozzles on each range will be increased until
the spray patterns of neighbouring nozzles overlap by at least this amount.
The Nozzle to vessel distance defines how far away nozzles are from the surface of the
cylinder.
There are also two ways for Autolayout to decide how much flow is required at each nozzle.
Again, the first way is for you to tell it, using the Flow per nozzle option. The second is to define
the Average flow density on the surface of the cylinder. Using this Autolayout can calculate the
flow required at each nozzle based on their efficiency (the fraction of their spray that hits the
vessel).
Ranges
This section specifies the ranges in the network (a range is a series of pipes at constant elevation
upon which nozzles are fitted). The Upper/Lower Separation distances measure the vertical
distances (as measured along the surface of the sphere) between ranges in the upper/lower
hemispheres respectively. This allows a finer degree of control over the network (NFPA 15 rule
7.4.2.4 states that surfaces below the equator of a spherical vessel are not considered wettable
from rundown, and hence a denser arrangement of ranges is usually required in the lower
hemisphere).
Start
from
poles
:
A
range is
placed
at the
north
pole,
with
additio
nal
ranges
placed
in the
upper
hemisp
here so
that the
distanc
e
betwee
n them
is equal
to the
the
upper
separat
ion
(when
measur
ed
along
the
surface
of the
sphere)
. The
placem
ent of
ranges
in the
lower
hemisp
here is
analago
us.
Start
from
equat
or:
A
range is
placed
at the
equator
of the
sphere.
Ranges
in the
upper
hemisp
here
are
placed
so that
the
distanc
e
betwee
n them
is equal
to the
upper
separat
ion
(when
measur
ed
along
the
surface
of the
sphere)
. The
placem
ent of
ranges
in the
lower
hemisp
here is
analago
us.
Rang
es at
poles
and
range
at
equat
or:
For this
option
the
Upper/
lower
Separa
tion
distanc
es
becom
e
Upper/
Lower
Max
separa
tion
distanc
es.
Ranges
are
placed
at the
poles
and at
the
equator
of the
sphere.
Additio
nal
ranges
are
then
added
in the
upper
hemisp
here so
that the
distanc
e
(along
the
sphere)
betwee
n
ranges
is not
greater
than
the
upper
max
separat
ion. As
few
ranges
as
possibl
e are
used to
achieve
this.
The
placem
ent of
ranges
in the
lower
hemisp
here is
analago
us.
The Use curved pipes check-box tells Autolayout to model the network using curved pipes. All
range pipes and certain pipes that make up the risers will be modelled as curved pipes for this
object type, and this has the affect of increasing their length.
The Display curved pipes check-box tells Autolayout to draw the relevant pipes as curves.
Curved pipes are approximated in the schematic by using multiple way-points (increases
complexity of network in the schematic).
Nozzles
These options define the nozzles of the layout. Nozzles are directed so that the centre line of their
spray cone is orthogonal to the vessel surface.
There are two ways for Autolayout to decide how many nozzles to put on each range. The first
is to explicitly tell it, using the Nozzles per range option. The second is to use the Min spray
overlap option. With this selected the number of nozzles on each range will be increased until
the spray patterns of neighbouring nozzles overlap by at least this amount.
The Nozzle to vessel distance defines how far away nozzles are from the surface of the sphere.
There are also two ways for Autolayout to decide how much flow is required at each nozzle.
Again, the first way is for you to tell it, using the Flow per nozzle option. The second is to define
the "Average flow density" on the surface of the sphere. Using this Autolayout can calculate the
flow required at each nozzle based on their efficiency (the fraction of their spray that hits the
vessel).
Nozzles
These options define the nozzles of the layout. Nozzles are directed vertically downwards
Nozzles are placed in a lattice configuration above the target area, and the space between
nozzles can be defined on one of two ways. The first is to give the maximum distance you would
like between nozzles, directly setting the lattice size. The second is to use the Min spray overlap
option. With this selected the lattice structure is refined until the spray patterns of diagonally
adjacent nozzles overlap by at least this amount. Setting this value to a positive number therefore
ensures that the entire target area is covered.
There are also two ways for Autolayout to decide how much flow is required at each nozzle.
The first way is for you to explicitly tell it, using the Flow per nozzle option. The second is to
define the Average flow density on the target area. Using this Autolayout can calculate the flow
required at each nozzle.
Layout
The Spray Diagrams interface is split into 3 panes. The left hand pane(the settings pane) contains
the settings and controls that generate the underlying spray diagram. The top and bottom panes
show different representations of the spray diagram. The top pane (the model pane) shows
vessel as defined in the Autolayout tool, showing the flow density of the spray on the surface.
The bottom pane (the diagram pane) shows the same information but as a flattened out, 2
dimensional image that can be saved/copied/printed.
The model and diagram panes can be resized by dragging the dividing bar up and down.
The menus at the side of the model and diagram panes contain settings pertaining to each of
those panes. These menus are activated by hovering the mouse over them.
Settings Pane
The Regenerate Image button at the bottom of the left hand pane recalculated the spray
diagram based on the current settings.
Settings:
Image resolution: This controls how large the spray diagram will be. It can be increased or
decreased by moving the slide bar, under which the image size is shown. The higher the
resolution (and hence the larger the image) the more detail the generated image will contain,
and the sharper it will look.
Critical flow density: Areas of the spray diagram are coloured with varying intensity based on
the amount of flow that area of the vessel is receiving. Areas receiving high rates of flow are
coloured in darker shades than areas receiving low rates of flow, with white indicating that
zero flow density is measured. The colour used for this shading is set using the Flow density
colour button. The Critical flow density is a threshold that triggers a change in the colour
used when flow density drops below the value selected. This value can either be set at the
NFPA 15 threshold or a user defined threshold.
Colour options: The Flow density colour and Warning colour buttons control the colour of
the flow density in the spray diagram. The legend is a key showing colours that represent the
range of flow densities in the spray diagram, with the max/min flow density at the top/bottom.
Model Pane
Once the model has been generated it will be displayed in the model pane. To move the model,
click and drag anywhere in the model pane with the left mouse button. To zoom, scroll with the
mouse wheel or click and drag anywhere in the model pane with the left and right mouse buttons.
Settings:
Cones: Gives you the option of displaying the spray cones of the nozzles in your model, as well
as choosing their size: at full size the cones strike the surface of the vessel.
3D quality: Allows you to improve the quality of the 3D model or reduce it to improve
performance. Clicking Update tells the model to use the new quality setting.
Orientation: Helps you to navigate by showing an arrow to indicate which direction is up, and
allowing you to reset the view of the model.
Diagram Pane
Once the diagram has been generated it will be displayed in the diagram pane. By hovering the
mouse over the diagram a mouse tooltip shows the calculated flow density at that point on the
diagram.
Settings:
Operations: Gives you the options of saving, copying or printing the spray diagram. Click on
the respective button to perform the desired operation. Clicking Save As will open a Save File
dialog and requires you to enter a valid filename under which to save the diagram. Clicking
Print will prompt you to select a printer from which to print.
Display: Allows you to change what is displayed on the spray diagram. By default the flow
density is shown. The Edge Detect option detects areas of sharp change in the flow density,
useful for showing the outline of each spray cone (in cases where they can be detected). The
Edge Detect Overlay displays the flow density and detects edges.
Edge Detection Sensitivity: This option is available when edge detection is being used. Altering
the sensitivity of the edge detection process grants a finer control over what is detected: a
higher sensitivity will be less discerning when deciding what is an edge and what is not. The
example below shows the effect of increasing the edge detection sensitivity: the sensitivity
becomes high enough that it detects smooth (but large) gradients as edges. In general the
sensitivity will need fine tuning in order to detect edges in a satisfactory way.
Selecting the tool from the tools menu displays a dialog of the form:
The left-hand window contains the attributes of each pipe; the right-hand window, the attributes
of each nozzle. With the check box in the last row of the left-hand window unchecked, clicking
OK will generate n nozzles (in the example above, 10 nozzles are to be created), separated by
pipes of the specified pipe length. If the check box is ticked then the dialog changes to:
Here, the length field is now grayed out in the left-hand window, since the separation of the
nozzles is determined by the number of nozzles and the total run length, as specified in the last
row of the left-hand window.
The pipe run can be drawn at an angle by providing an angle of inclination (in the bottom left-
hand corner of dialog), measured in degrees from the horizontal in a counter-clockwise direction.
Part
17
157 Spray/Sprinkler Module
17 Libraries
17.1 Libraries
Two types of library are used in PIPENET modules:
fittings,
pumps,
valves,
nozzles,
linings,
pipe schedules.
There is only one local user library. It has the file extension .SLF, and replaces all of the separate
library files from previous modules. Whilst a data file is open, entries can be added, deleted or
edited using the Library Editor dialog.
A local user library can be shared by one or more data files; however, if the library is changed in
one network, it is changed for all users of the library.
Local and system libraries have the same format, the only difference being in their relationship to
the data file.
System Library
Whereas the local user library is considered to be under the control of the user opening the data
file, and is, for all intents and purposes, part of the data file, system libraries are external libraries,
generally considered to be under the control of some central administrator.
System libraries can be referenced by a data file, but are not normally edited whilst a data file is
open; instead, the user must edit system libraries in an External System Library Editor.
The concept of separate System Libraries introduces extra flexibility in that now a user can have
more than one source for schedules, fluids, etc. There is also the possibility of imposing central
control over some (System) libraries, whilst allowing users to have their own private library
definitions.
A network data file referencing a single Local User Library essentially corresponds to the way in
which previous products have worked; i.e., in previous products, a network data file could only
refer to a single PDF file, a single UFL library and so on. However, System libraries provide the
facility for a network to gather library definitions from multiple files.
Opening Libraries
Libraries opened from the File menu are always considered external system libraries. Only the
new format libraries (that is, those with a .SLF extension) can be opened.
Importing libraries
New and old style libraries (i.e,. .PDF, .PMP, etc.) can be imported via the Import Library
option in the file menu. Imported libraries are merged into the single local user library.
Exporting Libraries
Libraries cannot be exported individually, but only as a result of exporting the network as an old
style .DAT file. This is achieved by selecting the File | Export... menu option and then providing
the name to be given to the .DAT file. Any associated library files will be saved with the same file
name, but with the appropriate file extension.
Libraries - example 2 - new data file using old style library files
In this example, we assume that a new data file is being created, but it is required to import
library files created under a previous version of PIPENET.
Libraries - example 3 - old data file using old style library files
Opening an old style .Dat file automatically imports any old style library files referenced by the .
Dat file.
Selecting any of these options displays a tabbed dialog with the appropriate library edit selected:
To the left is a list of available schedules, both built-in and user-defined, and selecting any item in
this list displays the properties of the schedule on the right.
At the top right are three fields common to all library editors:
1. The name of the schedule as it appears in pop-up menus, with the length of this name
being limited to 20 characters.
2. An optional longer description.
3. The source of the schedule, which may be one of the following:
Built-in schedule provided with the Spray/Sprinkler module. Built-in schedules
cannot be edited.
Local user library - these items may be edited whilst a network is open.
System library - these items can only be edited when a network is not currently
open.
Below these three fields is a field containing the roughness, and below that is a grid showing the
standard nominal sizes and the corresponding internal diameters. If a nominal diameter is "unset"
then the corresponding nominal diameter is not included in the schedule.
Nominal diameters are greyed-out indicating that their value is fixed. Right-click within the grid
area to display an option to copy the grid contents to the clipboard.
Roughness and diameters are displayed in the user specified units (see Options | Units).
17.4 Nozzles
To view a library nozzle, select the required nozzle from the left-hand window and its properties
are displayed on the right-hand side. To delete a nozzle, select the nozzle in the left-hand
window and then select the Delete button. To add a new nozzle:
Note that the definition of the pump curve will only be accepted if:
For a quadratic curve - at least three points are provided and the slope of
the calculated curve is negative everywhere between the minimum and
maximum values.
For a cubic or smooth curve - at least four points are provided.
For flow rates between the specified minimum and maximum flows - there must be no
flow rate that gives no pressure change; that is, the performance curve must not cross
the horizontal axis.
Right-click within the grid area to display an option to copy the grid contents to the clipboard;
right-click within the graph area to copy the graph to the clipboard.
The reference density for the curve is water at normal conditions, with an assumed density of
998.2343 kgm-3 . For units of head, such as m, the fourth column is the same as the third
column. For units of pressure, such as psi, the fourth column is based on the known density of
the fluid (if the density is not known, the density of water will be assumed). Note that, currently,
the reference density cannot be changed.
Deleting a pump
1. Select the name of the pump from the drop-down list.
2. Select the Delete button.
Note that the definition of the pump curve will be accepted only if the slope of the calculated
curve is negative everywhere between the minimum and maximum values.
Right-click within the grid area to display an option to copy the grid contents to the clipboard;
right-click within the graph area to copy the graph to the clipboard.
The reference density for the curve is water at normal conditions, with an assumed density of
998.2343 kgm-3 . For units of head, such as m, the fourth column is the same as the third
column. For units of pressure, such as psi, the fourth column is based on the known density of
the fluid (if the density is not known the density of water will be assumed). Note that, currently,
Deleting a pump
1. Select the name of the pump from the drop-down list.
2. Select the Delete button.
17.7 Linings
To view a library lining, select the required lining from the left-hand window and its properties
are displayed on the right-hand side. To delete a lining, select the lining in the left-hand window
and then select the Delete button. To add a new lining:
System Libraries can be edited whilst a network referencing the file is open, but this is
not generally recommended.
System Libraries are designed to be shared by a number of users, and any edits may
affect other users.
System Libraries will typically be administered by a central controller, who would
control access to the libraries via read/write permissions.
Whilst there is only one User Library referenced by a network, there can be many
referenced System Libraries.
Open a library file directly if one, and only one, system file is referenced by the
network, or
Display a list of referenced library files, any one of which may be selected for editing.
Part
18
169 Spray/Sprinkler Module
18 Specifying Options
18.1 Title
Use this dialog to enter a title for the PIPENET problem. A title may consist of up to four lines of
text, with each line containing no more than 65 characters. The first line of the title will be
displayed on each page of a printed schematic.
Design Rules
Select one of the available options:
Pressure Model
Select from the available options, referring to the Modelling section - Pressure
Models for further details.
Elevations
Specify the means by which node heights are derived.
Warnings Control
The default is to treat warnings as errors. Occasionally, it may be appropriate to
allow a calculation to continue even if there are warnings.
BS1042.
Heriot-Watt.
Crane.
Chinese Standard (GB) - Note that this option is automatically selected when
the Chinese Standard option is selected for the Design Rules. It cannot be de-
selected, other than by changing the Design Rules.
Fluid
Select water at 20 C or select user-defined, and provide the values for density and
viscosity.
Velocity Pressure model - use the NFPA model, the Standard model, or ignore
velocity pressure considerations. The NFPA model is that given in [NFPA15] and
the Standard model is that given in most textbooks.
Include pressure loss at entrance - indicates whether or not the pressure loss
should be included for the pipes located at the system entrance.
Include pressure loss at exit - indicates whether or not the pressure loss should be
included for the pipes located at the system exit.
The selection of the velocity pressure options only affects the appearance of the NFPA
submittal report.
18.3 Units
A wide selection of unit systems are provided, including:
SI,
Metric,
US,
Imperial,
User Defined.
Each of the first four provides a fixed, consistent set of options. For example, the unit of
diameter (of pipes) and length in the SI system is fixed at metres, and the unit of temperature is
fixed at Kelvin. The User Defined option allows the user to specify the unit to be used for each
measure independently. We could, for example, have length measured in metres but diameter
measured in inches.
In general, it is recommended that the very first operation in the process of creating a new
network should be the selection of the appropriate units. Whilst units can be changed later, it can
lead to complications and confusion. In particular, switching between mass and volumetric flow
can create problems when the fluid density is unknown (depending on the fluid model being
used), and a warning may be issued in these situations.
The left-hand side is a scrollable window via which for each quantity (length, diameter, velocity,
etc) a unit (metres, feet, etc.) may be selected. For users of previous versions of PIPENET, this
window is functionally identical to the Units dialog in those versions; the same set of options is
available. The units options window can be scrolled vertically to display more options.
The example above illustrates that SI units are in use, and units cannot be changed individually.
Selecting the User-defined option will result in the following display and all unit options are now
enabled:
When you switch to User-defined units you will be offered the chance to copy your current
settings to your User-defined settings. This can be very useful, to reset your user-defined settings
and then tweak one or two of them to preferred values.
Display Precisions
At the upper right of the dialog is an area where the display precisions can be set individually for
general display (in the Property windows, dialogs and the Data window) and in the Schematic
window. To use this facility, select the name of the quantity (Length, Diameter, etc.) in the left-
hand window, and the display changes to:
Here, Length has been selected. The values displayed for the precision [0.123] indicate that
three decimal places will be used for the display of length in the selected unit of length (metres, in
this example).
Selecting the arrow to the right of each field produces a drop-down list, showing that the number
of decimal places can be selected to be between zero and eight.:
When a network is saved, the preferred precisions are saved, and they are reloaded when the
file is re-opened. Selecting the Save As Defaults button will save the current settings in the
registry, and these will be the defaults used when new networks are created.
To use the tool, simply enter a value in the left-hand field, select the unit that the value represents
from the left-hand column (from unit) and the unit to which to convert to from the right-hand
column (to unit), and the result is displayed in the right-hand field. This example illustrates that 1
metre is converted to 3.2808399 ft. The example below illustrates the use of the tool to convert
a pressure; specifically, 1.0 psi Abs converts to 6894.75 Pa Abs.
18.4 PipeTypes
In the spray module, all pipes in a network must be of a specified type. A pipe type will be
associated with a pipe schedule, and this schedule must already exist before the pipe type can be
created. An optional lining definition may be provided by specifying the material and the lining
thickness.
If no pipe type is defined then the pipe drawing tool on the toolbar is disabled, and the status
message No Pipe Type appears in the status bar at the bottom of the screen. This status will
disappear when a pipe type is defined and the pipe button will be enabled:
Note that if a pipe is defined as using a pipe type then, instead of explicitly entering the pipe
diameter, the diameter is selected from a combo box listing the available sizes, together with the
unset value.
Label Options
The label options allow nodes to be labeled, links to be labeled, component direction to be
For pipes, an additional option is available indicating whether or not all segments of a multi-
segment pipe (that is, one containing way points) are to be labeled, or only the central segment.
Labeling only the central segment may improve the appearance of printed schematics.
An arrowhead pointing from the input towards the output indicates the component direction. As
with the standard PIPENET definition, the component direction does not necessarily correspond
to the direction of flow.
The presence of one or more fittings on a pipe is indicated by a blue diamond symbol, centred
along the length of the pipe.
Annotation
If your schematic display becomes cluttered, this provides a quick and easy way to reduce the
number of decimal places displayed.
Results Options
Results options - selecting the option "Arrows indicate flow direction" will display an arrow on
each pipe, indicating the direction of flow, instead of the component direction. The results that
are displayed (i.e., pressure, flow rate, velocity, etc.) are selected via the classes tab of the
Properties Window or the Options toolbar.
Line Thickness
Specify the thickness of the lines used for drawing as being between one (the default) and eight
pixels.
Grid Options
Via the Grid options, you can select the display of a grid, its style and whether all nodes and
waypoints are confined to lay on grid intersections. The grid can be orthogonal (vertical and
horizontal grid lines) or isometric (one vertical axis, one axis at 30 degrees to the horizontal and a
third at 150 degrees to the horizontal).
Tool Tips
Selecting this option will cause tool tips to be displayed when the mouse cursor is on or near a
component. The tool tip will display the component type, its label and the current parameter
selected from the Options toolbar. The information is displayed for a few seconds, and then
disappears. For example, moving the mouse to a pipe will display:
message "Failed to Converge" then increasing this value may produce results.
Convergence Accuracy
This parameter defines the convergence accuracy used to determine when two iterations are
sufficiently close to assume that a solution has been reached.
Temporary Path
Enter the path to be used for the storage of all intermediate temporary files required by the
calculator.
Calculation Type
User Defined
This allows the user to specify inlet and outlet conditions, much like in the Standard
Module.
Area Coverage
This takes the total demand flowrate from all nozzles and uses it as an inlet
specification.
Demand/Reference Data
This specifies at which node the total demand is made. It also specifies the reference
node for elevation data.
Supply Data
NFPA Plot
This specifies the data for the drawing of a supply curve on the NFPA Report.
Pump Curve
This allows the drawing of a pump curve at a fixed point on the demand graph.
operation is performed, the node heights will becalculated from the pipe elevations. Here, a
reference node (from which all other node heights are calculated) and a reference height can be
provided. Note that the calculated node heights are only for display in the schematic window,
and they have no effect on the hydraulic calculations. If a reference node is not provided then an
arbitrary node will be used, and assigned a zero elevation. If node elevations are being used then
the two edit fields are greyed out.
The specification of a reference height and the calculation of node heights from pipe
elevations simply provides additional useful feedback to the user, and the information
has no affect on the calculated results.
If the include validation box (in the lower left-hand corner) is selected, a listing of the original
input file will be included at the beginning of the output file. This will display any errors or
warnings arising from the input file.
18.8 Defaults
Through this dialog, the user can specify the defaults to be applied when creating new nozzles:
Part
19
Modelling 184
19 Modelling
19.1 Most Remote Nozzle
This very useful feature allows the user to specify that all nozzles must be discharging at or above
their required minimum rate. PIPENET achieves this goal by identifying the most remote (see
below) nozzle in the network and making a flow-rate specification on it of its minimum required
discharge rate. This counts as one calculation-phase flow-rate specification. Thus, when using
this option, the user must supply another (Nio-1) calculation-phase specifications, so that total
number of specifications is equal to the number of I/O nodes (i.e., Nf + Np =Nio).
The 'Most Remote' nozzle is the nozzle in the network that is hardest to supply at its minimum
rate. Thus, if the most remote nozzle is being supplied at this minimum rate, all other nozzles will
be supplying above their minimum rate. Some of the factors that influence the remoteness of a
nozzle are:
As a simple example of this type of calculation, consider once again the example network:
Suppose that the nozzle is required to supply water at a rate of 600 lit/min, but that, for safety
reasons, the velocity of fluid in the pipe must not exceed 4 m/s (i.e., the design velocity is 4 m/s).
Then we have:
and
or
d2 0.01/ = 0.003183
d 0.056411 m = 56.4 mm..
Thus, in this case, the diameter of the pipe should be larger than 56.4 mm. The actual diameter
of the pipe used will depend on the sizes of pipe that are available. This is determined by the
pipe schedule being used.
Given the flow rates required in and out of the network, PIPENET will calculate the flow rates
through every pipe in the network. PIPENET will then perform a calculation similar to the one
given above, and select a suitable diameter for each pipe.
19.4 Linings
Any of the available pipe schedules (built-in or user-defined) may also be lined in accordance
with the user's requirements. This is done by specifying the lining to be used for the Pipe Type,
together with the thickness of the lining. Of course, if no lining is to be used then no such data is
supplied.
Three types of lining are built into the program, and a further 3 types may be defined by the user
in the Private Data File. The 3 built-in linings are:
Concrete,
Asbestos,
Epoxy.
In order to define a lining it is simply necessary to specify the name and roughness of the lining
material via the Library option.
where:
Pfric = Pressure loss due to friction and fittings.
Pelev = Pressure loss due to elevation change.
Pplat = Pressure loss due to any orifice plate fitted.
Data Required
From the library:
1. Definition of the pipe type (Schedule, lining, C-factor and design velocities).
2. Pipe label.
3. Input and output nodes.
4. Nominal diameter.
5. Pipe length.
6. Increase in elevation from inlet to outlet.
7. A list of fittings on the pipe.
Notes
1. The pipe diameter may or may not be supplied by the user. If the diameter is not set by
the user then a suitable size will be found by PIPENET's Design Facility.
2. The increase in elevation may be given directly, or by supplying the elevations of the
input and output nodes.
With Chinese Standard (GB) options, the pipe pressure loss due to friction and fittings is
calculated as follows:
where:
Pfric is the pipe pressure loss due to friction and fittings, unit is M Pa.
u is the fluid velocity, unit is m/s.
D is the internal diameter of the pipe, unit is m.
L is the pipe length, unit is m.
Le is the equivalent length of any pipe fittings, unit is m.
SI units
The frictional losses are given by:
where:
Pfric is the friction loss in bar,
L is the pipe length in metres,
Le is the equivalent length of any pipe fittings in metres,
Q is the (volumetric) fluid flow rate in l/min,
D is the pipe diameter in mm,
C is the Hazen-Williams constant (or C-factor ) for the pipe.
Imperial units
The frictional losses are given by:
where:
Pfric is the friction loss in psi,
L is the pipe length in feet,
Le is the equivalent length of any pipe fittings in feet,
Q is the (volumetric) fluid flow rate in gallons per minute,
D is the pipe diameter in inches,
C is the Hazen-Williams constant (or C-factor ) for the pipe.
where:
D is the internal diameter of the pipe.
L is the pipe length.
Le is the equivalent length of any pipe fittings.
f is the Fanning friction factor.
u is the fluid velocity.
is the fluid density.
The Fanning friction factor f depends on Reynolds number (Re = uD /, where is the fluid
dynamic viscosity) and the relative roughness of the pipe (i.e., the pipe roughness divided by the
pipe diameter). The standard values for f can be obtained from a graphical representation known
as the Moody diagram. This is represented in PIPENET by the following empirical formulae
(where r is the surface roughness of the pipe):
The Coulson-Richardson method uses the pipe roughness in its calculations, which is taken from
the pipe schedule used for the Pipe Type. In this case, there is no need to specify a C-factor for
the pipe.
With the Hazen-Williams method, the pipe C-factor is used in the calculations, and so the C-
factor must be specified.
It should be noted that, for maximum flexibility, the roughness or C-factor value of the Pipe Type
can be overridden by the user when entering the individual pipe data. However, by default, the
roughness or C-factor of each pipe will be determined by the pipe's pipe type.
where:
is the fluid density.
Z is the change in elevation in the pipe.
g is the acceleration due to gravity.
When the velocity pressure is included, at any nozzle along a pipe (except the end nozzle), the
pressure acting to cause flow from the nozzle is equal to the total pressure minus the velocity
pressure on the upstream side; at the end nozzles, the pressure acting to cause flow from the
nozzle is equal to the total pressure.
Options are also available to include pressure loss at the entrance and pressure loss at the exit.
The pressure loss in the pipe caused by the entrance/exit effect is calculated according to the
formulae in [CRANE]. The entrance pressure drop formula is the most common Flush type,
with r/d=0.
Modelling
where
Pn is the normal pressure in Pa,
Pt is the total pressure in Pa,
Pv is the velocity pressure in Pa.
where
Pv is the velocity pressure in psi,
Q is the (volumetric) fluid flow rate in gpm,
D is the pipe diameter in inches.
where
Pv is the velocity pressure in Pa,
is the fluid density in kg/m3 ,
v is the velocity in m/s.
where
where
PEx is the frictional loss, in Pa, due to the exit effect,
is the fluid density in kg/m3 ,
v is the velocity in m/s.
19.12 Filters
Modelling Equation
P = AQ|Q| + BQ
where:
P is the pressure increase from inlet to outlet.
Q is the (volumetric) flow rate through the filter.
A is a coefficient less than or equal to zero.
B is a coefficient less than zero.
This is operative for values of Q whose modulus is less than a given maximum flow, Qmax . Note
that filters are reversible (Q may be negative), and that as:
A 0 and B < 0
A descriptor, manufacturer supplied K factor and X factor, and bore must be supplied.
Modelling Equation
P = Qx/K
where:
P is the pressure drop across the valve.
Q is the (volumetric) flow rate through the valve.
K is a constant for the valve.
X is a constant for the valve (typical values are 1 or 2, see the curves below).
Data Required
In the library:
1. A valve descriptor to identify the type of valve (usually the manufacturer's valve name is
used).
2. The valve K factor.
3. The valve X factor.
The equation for the deluge valve model in PIPENET goes back to the early 1980s. Angus Fire
Armour (Thame and now part of Kidde) used to publish data for the values of K and x for their
deluge valves those days. So, some users asked for this equation to be built into PIPENET. This
was done. A few years later Angus stopped publishing this data. However, we could not remove
this model because there were users with data files which had this model. Nowadays it is there
largely for historical reasons.
where:
If you have a conventional valve Cv or Kv value from your valve manufacturer which has the
following formula
or
or
or
where:
or
Comparing this equation and the equation for the deluge valve, we can get
X=2
and
or
Please note: when we use the above formula to input K for the deluge valve in PIPENET Spray/
Sprinkler Module, we should set the flowrate and pressure units in PIPENET same as the units
given with the valve Cv value in your valve data. Of course, you can always change to other units
after you input K, PIPENET will calculate the new K value according to your new units.
Furthermore, you can use the following two methods to model a deluge valve as well:
Some engineers who do not wish to use the above model, use the equipment item model instead.
The equipment item model uses the equivalent length for the deluge valve.
For items such as fittings which are not found in the NFPA rules but for which you have some
data, we can use equipment item to model them. It is very common to model items such as
deluge valves, strainers and so on in this way. To use the equipment item, please follow the
procedure below. I have attached some screen shots to show the steps. Suppose a strainer has
an equivalent length of 30 m, you have to go through 3 steps.
PIPENET has the capability of modelling elastomeric valves such as Inbal valves. With this
model it is not even necessary to specify the Cv value of the valve. The user can specify the
required flowrate and PIPENET will calculate the pressure drop across the elastomeric valve
which is necessary to achieve the specified flowrate.
Note that, even if the solution to the problem has the valve open, PIPENET can still generate this
message. Occasionally, a non-zero "leakage flow" may be reported through a closed valve. This
message arises from rounding errors in the calculation, and, since the errors are smaller than the
requested convergence accuracy, they are, therefore, usually negligible.
None.
Modelling Equations
Open valve:
P1 = P2 .
Q1 = 0.
Continuity Equation:
Q1 = Q2.
where:
P1 is the inlet pressure.
P2 is the outlet pressure.
Q1 is the inlet flow rate.
Q2 is the outlet flow rate.
Note that if there are any overboard dump valves present in the network then the Remote
nozzle specifications and Mass balance specifications options will be greyed out in the
Calculations options dialog. This is because overboard dump valves can only be used with the
User-defined specifications option. Note, also, that if the Remote nozzle specifications or
Mass balance specifications option has been selected, the overboard dump valve icon on the
toolbar will be greyed out (as it is non-selectable).
19.17 ElastomericValve
The Elastomeric valve enables the user to achieve the required input pressure, output pressure,
pressure drop or flow rate without the need to input the valve characteristic data. The
elastomeric valve is representative of a valve type that fulfils the above roles; however, the model
described below can be used to model any valve, including elastomeric valves, with the specified
characteristics.
Note:
1. The use of unreasonable target values might make the network unsolvable.
2. A warning message will be given in the calculation report when either (a) the output
pressure is higher than the input pressure or (b) the flow rate is negative.
Modelling equations
Design phase
P1 = P2
Analysis phase
Input pressure type - aim to control the input pressure of the valve to be the given
target value:
P1 = P1*
Output pressure type - aim to control the output pressure of the valve to be the
given target value:
P2 = P2*
Pressure drop type - aim to control the pressure drop of the valve to be the given
target value:
P1 - P2 = P*
Flow rate type - aim to control the flow rate of the valve to be the given target
value:
Q = Q*
where:-
P1 - input pressure,
P2 - output pressure,
P1* - target input pressure,
P2* - target output pressure,
Q - flow rate,
Q* - target flow rate.
Plates with flange tappings in accordance with BS1042, taking into account pressure
recovery downstream. The restrictions of BS1042 are applied, so plates may only be
used in pipes with diameters in the range 2 14 inches (50.8 355.6 mm).
Furthermore, the ratio of the orifice diameter to the pipe diameter must be in the range
0.1 0.748 for pipes over 4 inches in diameter.
The "Heriot-Watt Orange Book" orifice plate model [CRANE]. This model derives
from curves for laminar flow given by Miller in "Internal Flow Systems" and for
turbulent flow given by the ESDU in "Flow of liquids - Pressure losses across orifice
plates, perforated plates and thick orifice plates." The ratio of the orifice diameter to the
pipe diameter should be less than 0.8.
Sharp-edged orifice plates, as described in Crane T.P. 410M. The ratio of the orifice
diameter to the pipe diameter should be in the range 0.2 0.75. In addition, the
Reynolds number of flow in the pipe should be greater than 100, as the accuracy of the
model decreases at lower values.
The pressure drop due to an Orifice Plate, Pplat , may be found in one of two ways: either it may
be specified directly by the user (in which case PIPENET will calculate the orifice diameter
necessary to produce this pressure drop), or it can be calculated by PIPENET from the orifice
diameter given by the user. Users should exercise caution when using this facility, as the
calculation of pressure drop from plate diameter is unstable in that a small change in orifice
diameter may result in a very large change in the pressure drop.
Where:
Pplat is the pressure loss due to the orifice plate, unit is 10-2 M Pa.
u is the fluid velocity, unit is m/s.
g is the acceleration due to gravity.
is the friction factor of the orifice plate, which can be calculated using the
following equation:
Where:
19.19 Pumps
A pump provides a pressure increase, which depends on the pump speed and performance
curve. The pump performance curve is entered in a library.
where:
s is the pump setting.
Q is the flow rate through the pump.
A, B, C are pump performance coefficients.
The pump performance coefficients A, B and C are entered directly, or calculated by PIPENET
for a specified pump curve, in pump libraries. The user also specifies an operating range for flow
rates through the pump. It is recommended that the zero flow rate point is given when defining a
pump curve.
The pump setting, s, must be between 0.0 and 1.0. A setting of s = 0.0 represents a shut-down
pump, while s = 1.0 represents a pump at full speed.
The quadratic curve will, in general, only apply to the specified working range of the pump;
however, degeneration factors can be used to specify the behaviour of the curve below the
specified working range and/or above the specified working range.
PIPENET calculates a binomial correlation to fit the input data (see the solid line in the
above figure):
We introduce a degeneration factor n, which is an integer in the range 0 to 10. The larger
the value of n, the flatter of the pump curve is. When the degeneration exponent n is zero
(i.e., no degeneration), the equation becomes the normal quadratic.
where:
where:
Notes
If the user knows the performance coefficients for a pump, but does not want to use a pump
library, then the pump can be defined as a non-library pump by giving the values of A, B, C, Q
min, and Q max.
In order for the calculator to function correctly, it is necessary to ensure that there is only one
flow rate corresponding to each pressure gain, and so the following restrictions are applied:
For flow rates between Qmin and Qmax, the slope of the performance curve must be
negative or zero.
For flow rates between Qmin and Qmax, there must be no flow rate that gives no
pressure change (that is, the performance curve must not cross the horizontal axis).
For flow rates outside the range Qmin to Qmax, PIPENET extrapolates the performance curve
using the tangent to the curve at the minimum or maximum flow rate, and issues an appropriate
warning message.
PIPENET will calculate the power required by a pump based on a specified efficiency. The
power calculation will assume that the pump is 100% efficient if the efficiency is not specified.
A simple quadratic curve can deviate considerably from the supplied pump data, especially when
the flow rate exceeds the pump capacity, or is less than the allowed minimum flow rate. The
cubic curve can provide better results.
There is a potential problem with the cubic curve in that it may lead to multiple solutions.
Therefore, the above function must satisfy the following condition:
The smooth curve uses cubic spline functions to fit a known pump curve. The obtained curve is
not only a smooth curve but also can closely match all input data.
Within the specified working range QLL to QUL in the region of [Qi , Q i+1]
Below the lower limit, with Q < QLL and along the tangent direction at the point [QLL, PLL]
where:
Above the upper limit, with Q > QUL and along the tangent direction at the point [QUL, PUL]
where:
Pump On/Off
The pump setting, which is a percentage of the maximum pump speed, i.e. in the range 0-1
(100%), can either be specified directly by the User, or be determined by PIPENET such that a
particular sensor set point is satisfied. Three sensor types are available:
Pressure at a node
Flowrate through a particular pipe.
Pressure difference between two nodes
Note:
The use of unreasonable set point values might make the network unsolvable.
NPSH
Net Positive Suction Head (NPSH) is an analysis of the energy conditions on the suction side of
the pump to determine whether the liquid will vaporize at the lowest pressure point in the pump.
NPSH is measured in units of length.
NPSHA is defined as Net Positive Suction Head Available, which can be calculated as
follows:
Where,
HS is the suction head, which includes not only the suction lift but also the sum of the
losses in the inlet pipe and the velocity head.
The cavitation parameter is a dimensionless ratio used to relate the conditions that inhibit
cavitation to the conditions that cause cavitation. There are several common forms of the
cavitation parameter. In PIPENET, the cavitation parameter is defined as:
The calculation of NPSHA and the cavitation parameter is based on the vapour pressure of
water at 60 F (15.6 C) at 1767.745 Pa A, which was calculated using the Water-steam
property facility of the PIPENET Transient module. This information will be given as a note
below the table in the report. This vapour pressure value is only used to calculate NPSHA and
cavitation. It is not used for other purposes, such as a warning of cavitation.
Modelling
Q=K P
where:
Q is the (volumetric) flow rate through the nozzle.
P is the drop in pressure across the nozzle.
K is a constant for the nozzle.
This equation holds for values of P between given minimum and maximum values, Pmin and Pmax .
This is known as the working pressure range of the nozzle.
Note that the value of K depends on the units used for P and Q. Generally, the units used for P
and Q when quoting the K value of a nozzle are bar and litres/min respectively.
Data Required
In the library:
1. A nozzle descriptor to identify the type of nozzle (usually the manufacturer's nozzle
name is used).
2. The nozzle K-factor.
3. Pmin and Pmax .
In the input:
1. Nozzle status (ON or OFF) - note that if a nozzle is off, this is indicated in the
schematic by the presence of a small solid circle inside the nozzle symbol:
2. Nozzle label.
2. Input node.
4. Nozzle name in the library.
5. The flow rate required through the nozzle.
Notes
1. Nozzles can be defined without including them in a library by specifying the values of
K, Pmin and Pmax . When there are several nozzles of the same type, it is easier to
define the type in a library, as described above.
2. The flow rate required through the nozzle is used by PIPENET's Design Facility.
This component can be used to model any type of device which achieves a pressure drop. This
pressure drop is calculated as a function of the flowrate through the component, using the
modelling equations shown below.
Modelling Equations
Resistance equation
where:
P1 is the inlet pressure
P2 is the outlet pressure
Q is the flowrate
K is the resistance factor
m is the exponent
where:
Pref is the reference pressure drop
Qref is the reference flow rate
User-defined type
The resistance factor at the known flow rate and pressure drop can be
calculated based on the following equation. The resistance factor at any flow
rate can be interpolated based on the above deduced factors.
A: Qmin<Q<Qmax
We assume the unknown resistance factor is linear to the flow rate.
or
B: Q<Qmin
The Q-K curve will extrapolate to the lower flow rate along the constant K line
with the same K factor at the lower limit point.
C: Q>Qmax
The Q-K curve will extrapolate to the higher flow rate along the constant K line
with the same K factor at the higher limit point.
A: Qmin<Q<Qmax
The resistance factor and flow rate are quadratic relationship.
B: Q<Qmin
The Q-K curve will extrapolate to the lower flow rate along the constant K line
with the same K factor at the lower limit point.
C: Q>Qmax
The Q-K curve will extrapolate to the higher flow rate along the constant K line
with the same K factor at the higher limit point.
C: Q>Qmax
The Q-K curve will extrapolate to the higher flow rate along the constant K line
with the same K factor at the higher limit point.
19.22 Fittings
All fittings are modelled as equivalent lengths according to either the FOC or NFPA rules, which
are summarized in the Reference data section.
The range of fittings provided is that defined by [NFPA]. If you wish to add some device or
fitting not included in the range of available fittings then you may be able to consider the use of
an Equipment item.
23.4.4.7 (3) Calculate the loss for a tee or a cross where flow direction change occurs
based on the equivalent pipe length of the piping segment in which the fitting is
included.
23.4.4.7 (4) The tee at the top of a riser nipper shall be included in the branch line, the
tee at the base of a riser nipple shall be included in the riser nipple, and the tee or cross
at a cross main-feed main junction shall be included in the cross main.
23.4.4.7 (5) Do not include fitting loss for straight-through flow in a tee or cross.
It is possible, however, that sometimes a user may wish to define the fittings in a different way,
Part
20
213 Spray/Sprinkler Module
The output file contains three tables. The first table, entitled Summary values, contains various
items that can be copied onto the submittal summary sheet; the second and third tables Node
analysis and Pipe information are designed to comply with the format specified in the 2013
Edition of NFPA-13, and are suitable for inclusion in the submittal report. Values are shown in
the user's currently selected units. Node heights are shown relative to an arbitrary datum node
unless both (i) pipe/duct elevations are in use (see Elevations on the Options | Module
options dialogue) and (ii) a reference node and height have been specified (see Calculation of
node heights from pipe elevations on the Options | Calculation dialog).
Velocity pressure information can be optionally displayed for each pipe in the Notes column.
Selection of this option is via the Spray options dialog.
In addition to this, supply and demand may also be calculated, from the Calculation Options
Dialog and presented in the form of a graph, plotted on an N185 grid.
The following report is generated (note that some blank spaces must be filled in):
Page
Page
Project Name
Location
Drawing Number
Design
Occupancy Classification
Density
Area of Application
In Rack Demand
Type of System
Date
Location
Source
Contractor Information
Name of Contractor
Address
Phone Number
Name of Designer
Page
Project Name
Notes
Page
Page
SUPPLY ANALYSIS
Notes
These values have been calculated assuming Residual values were entered for the first point of the Supply Curve
Page
NODE ANALYSIS
Node tag Elevation (m) Node Type Pressure (Bar G) Discharge (l/min) Notes
Page
PIPE INFORMATION
Pt (1) (Bar
G)
Flow added
Nominal ID
(q)(l/min)
Node 1 (milli.m.) L (m)
Elev 1 K factor C factor Notes
Fittings -
(m) Pe (Bar)
quantity,
type, and Pt': Total pressure just
Total flow (Q)
Actual ID equivalent F (m) inside pipe ends
(l/min)
(mm) length (m) Pn': Normal pressure
Node 2 Elev 2 Pf (Bar) just inside pipe ends
Pipe label Pf per m
(m)
Nozzle label (Bar)
T (m)
Pipe Flow (l/
Pipe Type
min)
Pt (2) Bar
G
1.237
435.870 Vel = 0.861 m/sec
200.000 200 Pv = 0.004 Bar
1 0.00 10.000 150.0
955.015 Pn (1) = 1.237 Bar G
2xE=14.78 0.000 Pn (2) = 1.193 Bar G
5xT=71.83 Pt' (1) = 1.235 Bar G
198.000 1xNR=20.60
112.100
1590.885 1xB=4.93 Pn' (1) = 1.231 Bar G
2* 0.00 1 0.000 0.040
test :
122.100
1590.885 Concrete
1.197
98.000
435.870 0.000
1.197
1.197
1.100
1.289
Notes
For full NFPA compliance, a detailed schematic drawing from PIPENET is required, showing pipe labels and directions as well as node and nozzle labels
Reference Node at which flowrates calculated denoted by bold and with an asterisk
To calculate Pt (2) from Pt (1) add elevation pressure, subtract friction loss
Page
T Tee or Cross (Flow turned 90) G Gate Valve C Swing Check Valve
Page
Hydraulic Graph
3.75
Supply
Demand
3
Pressure / Bar G
2.25
1.5
(1590.89,1.23679)
0.75
0
06
02
08
04
00
06
02
08
04
00
1
3
11
21
41
61
Flow Rate (Q1.85) / l/min
Page
aaa
12.5
Pressure / Bar fluid (reference)
7.5
2.5
0
0 25000 50000 75000 100000 125000
Part
21
Exporting the Schematic 226
Part
22
Errors 228
22 Errors
22.1 Errors
Errors can be detected at various points in the opening of an existing network file, or in the
creation of a new network:
Basic errors in the operating environment, the most common error being the absence
of a valid licence to run a PIPENET module, or the absence or incorrect operation of
the security key drivers.
Input errors detected either in reading the main data file or an associated library file.
Specific component errors detected in the GUI when a check operation is
performed; for example, pipe has zero length these errors should be self-
explanatory.
Global errors detected in the graphical user interface (GUI) when a check operation
is performed.
Numerical errors that can only be checked after the calculation starts, and are
therefore reported in the calculator output.
Attempts to run the software on earlier versions of Windows operating system may fail
the software is only validated for Windows 2000, XP, Vista, and Windows 7.
A working PIPENET system may suddenly stop working if a new operating system is
installed, or if a new Windows service pack is installed. Generally, Sunrise Systems
will discover these errors in advance, and will be able to provide suitable fixes, new
security key drivers, etc.
No valid licence separate licences are available for the three PIPENET modules:
Transient, Spray/Sprinkler and Standard. Attempting to run a module for which you
have no licence will produce an error. To determine which licences you have, see the
Help | Key status menu option . If in doubt, contact Sunrise Systems for details of
your current licences.
Licence has expired with the issue of PIPENET VISION 1.10, expiry-date
checking was added to HASP security keys. If an old key is being used, or if the
licence for the module you are attempting to run has expired, then a message will be
displayed informing you of the situation. To see the expiry dates, see the Help | Key
status menu option; if no expiry dates are shown then you have an old key that needs
to be updated. Keys can be updated remotely by Sunrise Systems providing (usually
via email) a small encrypted key-update file see the Updating a key licence section
for further details.
Drivers for security keys not installed correctly see the installation instructions
supplied with the software for information on how to check the status of the drivers
and, if necessary, re-install them. Periodically, the supplier of the security key drivers
will have to issue new versions of the drivers when a new operating system or service
patch is released. When this occurs, Sunrise Systems will make the drivers available
on our website or via email.
One error that may occur with both the old and new types of file is that one of the library files
referenced by the main data file may be missing. In earlier versions of PIPENET, this could
occur if the .DAT file and the associated library files were moved to a new location, since the .
DAT file would contains references to the library files in their original location. With PIPENET
VISION, if a library file cannot be found in its original location, a search will be made in the
directory where the main data file (.SDF file) is located.
that is, the sum of all elevations in the loop does not sum to zero. Double-clicking on this
item will highlight the loop in error in the schematic. For further information see the
height checking section.
I/O node must be on a single pipe when using variable fluid properties and
volumetric flow rate - error
An input or output node must only be connected to one pipe when using variable fluid
properties and volumetric flow rate.
components (for example pumps and valves) must have the same elevation.
One I/O node with no flow spec is required for Design - warning
If a design phase is being used then there must be at least one input/output node with no
flow specification see specifications requirements.
Note that many of these errors are of the general form <attribute name> must be given, as in
the last three examples above, indicating that a value for the attribute has not been provided.
Double-clicking on the error in the Check status dialog will highlight the component in the
schematic.
Calculation fails to converge this may because the calculation cannot be solved as
defined, or it may just require a few more iterations than are specified in the calculation
options. A calculation can also fail to converge if the network is incorrectly specified
in some way.
Also, note that, when you request a calculation, a check is performed first, and any errors or
warnings are displayed in the check status dialog.
Part
23
Reference Data 234
23 Reference Data
23.1 Bibliography
[CRANE] Technical paper No. 410M, "Flow of Fluids Through Valves, Fittings and pipe",
Crane Co., 1988.
[NFPA13] NFPA 13, "Standard for the Installation of Sprinkler Systems", NFPA 2013.
[NFPA15] NFPA 15, "Standard for Water Spray Fixed Systems for Fire Protection",
NFPA 2012.
[NFPA16] NFPA 16, "Standard for the Installation of Foam-Water Sprinkler and Foam-
Water Spray Systems", NFPA 2011
[NFPA20] NFPA 20, "Standard for the Installation of Stationary Pumps for Fire
Protection", NFPA 2013
[NFPA750] NFPA 750, "Standard on Water Mist Fire Protection Systems", NFPA 2010
[HPGL2] "The HP-GL/2 and HPRTL Reference Guide", Third edition, Addison Wesley,
1997.
Material Roughness
(mm) (inch)
Glass Reinforced Plastic (GRP) 0.03 0.06 1.18 10-3 to 2.36 10-3
PVC and plastic pipe 0.0015 0.007 5.91 10-5 to 1.18 10-4
Cast iron
Material Roughness
(mm) (inch)
Steel
When a range of values is provided, the lower value is for new pipes and the upper value is for
old pipes. When a single value is quoted, this is for new pipes. Unfortunately, there is no single
source for the above data, and the data has been compiled from a number of sources, including:
Material C-factor
Material C-factor
Cast iron
20 years old 95 55
30 years old 85 45
50 years old 75 - 40
Bitumen-lined 140
Polyethylene 150
When a range of values is provided the lower value is for new pipes and the upper value is for
old pipes. When a single value is quoted, this is for new pipes. Unfortunately, there is no single
source for the above data, and the data has been compiled from a number of sources, including:
Notes
1. Data is taken from 29th Edition FOC Rules, Table 6124.
2. The above values are used only for a Hazen-Williams C-Factor of 120. For other
values of the C factor, the values are scaled in accordance with Table 6124 of the
FOC Rules.
3. Equivalent lengths of 15mm fittings are assumed to be the same as the corresponding
20mm fitting.
4. Equivalent lengths of valves below 50mm are assumed to be the same as the
corresponding 50mm valve.
Notes
1. Data is taken from 29th Edition FOC Rules, Table 6124.
2. The above values are used only for a Hazen-Williams C-Factor of 120. For other
values of the C-factor, the values are scaled in accordance with Table 6124 of the
FOC Rules.
3. Equivalent lengths of 90mm fittings are the arithmetic means of the corresponding
80mm and 100mm fittings.
Notes
1. Data is taken from 29th Edition FOC Rules, Table 6124.
2. The above values are used only for a Hazen-Williams C-Factor of 120. For other
values of the C-factor, the values are scaled in accordance with Table 6124 of the
FOC Rules.
3. All fittings above 250mm (10in) are assumed to have the same equivalent length as the
corresponding 250mm fitting.
Notes
1. Equivalent lengths are taken from NFPA 15 (2012) Table 8.5.2.1, except for fitting
types 7 and 8, which are manufacturers' data.
2. The above values are used only with a Hazen-Williams C-factor of 120. For other
values of the C-factor, the equivalent lengths are scaled in accordance with NFPA 15
Table 8.5.2.3 (g).
3. Equivalent lengths of 15mm fittings are assumed the same as the corresponding 20mm
fittings.
4. Equivalent lengths of gate and butterfly valves below 50mm are assumed the same as
the 50mm values.
Notes
1. Equivalent lengths are taken from NFPA 15 (2012) Table 8.5.2.1, except for fitting types 7
and 8 which are manufacturers' data.
2. The above values are used only with a Hazen-Williams C-factor of 120. For other values
ofthe C-factor, the equivalent lengths are scaled in accordance with NFPA 5 Table 8.5.2.3
(g).
3. The equivalent length of a 90mm butterfly valve is assumed the same as the 100 mm valve.
Notes
1. Equivalent lengths are taken from NFPA 15 (2012) Table 8.5.2.1, except for fitting types 7
and 8 which are manufacturers' data.
2. The above values are used only with a Hazen-Williams C-factor of 120. For other values of
the C-factor, the equivalent lengths are scaled in accordance with NFPA 15 Table 8.5.2.3.
Notes
1. The above values are used only with a Hazen-Williams C-factor of 120. For other values of
the C-factor, the equivalent lengths are scaled in accordance with NFPA 15 Table 8.5.2.3.
2. Equivalent lengths for these sizes are taken from Factory Mutual data sheet 2.89, except for
fittings types 7 and 8, which are manufacturer's data for 300 mm valves.
Notes
1. The above values are used only with a Hazen-Williams C-factor of 120. For other values of
the C-factor, the equivalent lengths are scaled in accordance with NFPA 15 Table 8.5.2.3.
2. Equivalent lengths for pipe sizes above 600mm have been obtained by extrapolation from
equivalent lengths for the smaller pipe sizes.
Notes
1. The above values are used only with a Hazen-Williams C-factor of 120. For other values of
the C-factor, the equivalent lengths are scaled in accordance with NFPA 15 Table 8.5.2.3.
2. Equivalent lengths for pipe sizes above 600mm have been obtained by extrapolation from
equivalent lengths for the smaller pipe sizes.
With the Chinese Standard (GB) options, the equivalent lengths (metres) of fittings are same as
the table for NFPA rules, but without the C-factor limitations.
Notes
1. Internal and Outside diameters are arithmetic means of values given in BS.3505
(1968).
2. BS.3505 does not include metric nominal sizes; these have been retained for users'
convenience.
Notes
1. Internal and outside diameters are arithmetic means of values given in BS.1387 (1967).
2. Nominal sizes have been used for internal and outside diameters for pipes in the range
200300mm (812 inch) for users' convenience.
3. This data is not part of BS.1387.
Notes
1. Internal and outside diameters are arithmetic means of values given in BS.1387 (1967).
2. Nominal sizes have been used for internal and outside diameters for pipes in the range
200300mm. (812 inch) for users' convenience.
3. This data is not part of BS.1387.
Notes
1. Internal and outside diameters are taken from ANSI B36.10 (1979).
2. ANSI B36.10 does not include metric nominal sizes; however, these have been
retained for users' convenience.
Notes
1. Internal and outside diameters are taken from ANSI B36.10 (1979).
2. ANSI B36.10 does not include metric nominal sizes; however, these have been
retained for users' convenience.
Notes
1. Imperial sizes taken from BS.1211 (1958).
2. This standard does not include metric sizes; these have been obtained by direct
conversion of the internal and outside diameters given in inches.
Notes
1. Outside diameters to BS.2871, Part 2, Table 3; BSMA 18, Table 2; BSMA 60. Wall
thicknesses conform to Lloyds offshore requirements.
2. Imperial sizes are direct conversions of the metric data.
3. Nominal sizes are included for users' convenience.
Notes
1. Outside diameters to BS.2871, Part 2, Table 3; BSMA 18, Table 2; BSMA 60. Wall
thicknesses conform to Lloyds offshore requirements.
2. Imperial sizes are direct conversions of the metric data.
3. Nominal sizes are included for users' convenience.
SCHEMATIC - the main part of the schematic including all nodes and components.
NLABELS - node labels.
CLABELS - component labels.
INDICATORS - fittings symbol (blue lozenge) and directional arrows.
TEXT - text items other than node and component labels.
Part
24
259 Spray/Sprinkler Module
24 Report Generator
24.1 Introduction
The PIPENET report generator is a Microsoft Word template add-in. Using it:
Word can open up a report file generated by PIPENET, and offer up the sub-sections of
the report in the form of a menu to pick from.
Once the user picks a sub-section, the corresponding content is copied into your Word
document at the insertion point. In practical terms, this might generate a section
heading, a title for a picture, or insert a table of data.
If the PIPENET report is regenerated after changes to the model, the Word report can
itself be regenerated to use the new results.
Other Word features such as formatting, or inserting images or other content, remain
available as usual.
24.2 Prerequisities
Microsoft Office 2007 or later
From the same directory locate ReportGeneratorTemplate.dotx file and copy it to your
computers local disk (for example your documents directory).
Depending on your company and project practices, you might choose to create one report
template for your whole business, or one for each piece of your project (or both). For the
purposes of this document we will assume just one template is sufficient.
From the Microsoft Word developer menu select a plain text content control and add controls
to the title page the header and footer and as illustrated in figures 1 to 3, label the content
controls Title-1, Title-2, Title-4 and Title-4. When you load the PIPENET results file, the report
generator will bind these controls to results file elements with the same name replacing the
text with the text defined in the results file.
Save the document as a Word template document ensuring that the file name has been
changed.
You should notice that the text in the content controls you added to the title page and to the
headers and footers have been set to values read from the elements in results file. That is,
the text in the Title-1 content control will now have the same value as Title-1 node in the
results file (Figure 5 Updated Title Page).
Right click the Maximum/Minimum node. This will bring up a menu of actions.
Execute the insert content command. The Maximum/Minimum table is added to the
document.
You can then format the table and maybe add a total row using standard Microsoft Word
commands, as seen below.
Rerun the calculation, saving the results to a different file than before.
Return to Word. Right click the root node of the tree control in the document actions pane and
select update report (Figure 9 Updating a report)
Browse to and select the newly created results file. The document will now update to reflect
the changed title - any other modifications you made to the model will also be reflected in
the document. Also if you added a totals row to the Maximum/Minimum table, the results
will also be updated.
Custom XML parts were introduced in the 2007 Microsoft Word system, along with the Open
XML Formats. These formats introduced a new XML-based file format for Word (i.e. .docx).
Documents in this format consist of XML files (also named XML parts) that are organized in
folders in a ZIP archive. Most of the XML parts are built-in parts that help to define the
structure and the state of the document. However, documents can also contain custom XML
parts, which you can use to store arbitrary XML data in the documents. The report generator
exploits custom XML parts.
Content controls are bounded and potentially labeled regions in a document that serve as
containers for specific types of content. Individual content controls can contain content such
as dates, lists, or paragraphs of formatted text. They enable you to create rich, structured
blocks of content. Content controls enable you to create templates that insert well-defined
blocks into your documents. Content controls also build on the custom XML Parts by allowing
applications to map the Content Controls to elements contained in a Custom XML Part and it is
this feature of content controls which the report generator uses.
Drawing Components 97
Properties 16
-A- Specific Errors
Undefined
231
46, 97
Appearance 13 Condensate tank deluge system 65
Area tool 93 Contacting Sunrise Systems 4
Autolayout 134, 151 Control valves
Flow Density 151 Library 24
Spray Diagrams 151 Convergence accuracy 179
Autosave 20 Copy/Paste 22, 92, 93, 94, 105
Coulson-Richardson 186, 188, 189
-B- Crane 199
Crosses 210
Background colours 124, 177 Cursor keys 100
Basic Errors 228
Bernoulli 188 -D-
Bibliography 234
Blocks 111 Data Window 104
Breaks 111 Deluge Valves
Browse 26 Advance Modelling Techniques 193
Library 166
BS1042 199
Modelling 192
-C- Design facility
Design Phase
184
38, 184
Calculate 26 Display options 177
Calculation Display Precisions 172
Checking 26 Drawing Components 97
Menu 26
Options 26 -E-
Calculation options 179
Calculation phase 38 Edit Menu 22
Calculation toolbar 31 Editing system libraries 166
C-factor 189, 236 Elastomeric valve
Chinese Standard (GB) 169, 186, 199, 248 Modelling 197
Closing a file 20 Elevation profile 126
Colour schemes 120 Equipment items 191
Colouration menu 26 Errors 228
Complex colouring rules 120 Examples
Complex links 26 Example 1 37
Complex nodes 26 Example 2 52
Example 3 65
Components
Adding Components to Pipes 98 Example 4 77
Component Tools 97, 98 Example 5 85
Examples directory 2
Library Nozzles
Nozzle library 161 Add Multiple Nozzles 27
Open 20, 157 Generation 154
Pipe Schedules 24 Library 161
Pumps 24 Modelling 206
Pumps - Coefficients Known 164 Most Remote Nozzle 110, 184
Pumps - Coefficients Unknown 162 Operating Point 15
System Libraries 166 Specification 114
System Library 157 NPSH 200
License 6 NPSHA 200
Line thickness 177 NPSHR 200
Lines per page 179 Numerical errors 232
Linings
Library
Modelling
165
186
-O-
Local user library 157 Opening a file 20
Options Menu
-M- Calculation options 25
Defaults Options 25, 182
Maintenance Area Sprinkler System 85 Display options 25
Mass balance 184 Module options 25
Mass Flow 172 Output tables options 25
Menu Style Pipe type option 25
PIPENET Menu Style 28 Title option 25
Windows Menu Style 28 Units option 25
Mirror 22 Options toolbar 30
Module options 169 Orifice plates
BS 1042 199
Moody diagram 188
Chinese Standard (GB) 199
Most Remote Nozzle 110, 184
Crane 199
Moving around the network 100
Heriot-Watt 199
Multiple Components
Modelling 199
Add Nozzles 27
Add pipes 27, 131 Outlets 36
Overboard dump valves
-N- Modelling 197
Specifications 197
Overview Window 19
Network
Navigating 100
Network representation 35 -P-
Network topology 37
NFPA Pan 93, 101
NFPA 2013 169 Paste in column 22
NFPA pre - 1996 169 Path
NFPA Submittal Report 26, 213 Make a path 27
Rules 242 Path Construction 126
Non-return valves Physical constants 238
Modelling 196 Pipe types
-Z-
Zoom 93, 101