Académique Documents
Professionnel Documents
Culture Documents
PAGE 1 OF 50
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
1.
Introduction
The Spray/Sprinkler Module of PIPENET VISION was specifically developed for the type of
fire protection systems that are used in process plants and similar plants, such as refineries,
petrochemical plants, offshore plants, and terminals. Such systems are characterised by
complex firewater ringmains, deluge systems, sprinkler systems, foam injection systems, etc.
For these systems, it is usually necessary to perform calculations under several scenarios,
such as different fire scenarios and different pump scenarios. With PIPENET VISION, it is
simple and fast to perform these calculations. The objective is to ensure that pipes, pumps,
hydrants, nozzles and other items perform satisfactorily. Where necessary, PIPENET
VISION can be used to size orifice plates in order to balance or reduce the flow rates.
The Spray/Sprinkler Module is a steady-state modelling program for designing systems, with
the objective being to ensure that the sizes of pumps, pipes, nozzles, etc. are adequate.
The Spray/Sprinkler Module complies with the NFPA rules, which are the universal rules
governing the design of fire protection systems in the process plant industry, as far as
hydraulic calculations are concerned.
One of the differences between the Spray/Sprinkler Module and the other modules of
PIPENET VISION is that, with the Spray/Sprinkler Module, it is not possible to enter a network
until either (a) a Sunrise Data File (*.SDF) has been entered and saved or (b) an existing
Sunrise Data File is opened.
In the suite of training manuals for the PIPENET VISION Spray/Sprinkler Module, Chapters 2
and 3 are the core of the training course, whereas Chapters 1 and 4 provide useful reading
material.
Most of the concepts and capabilities introduced in Chapter 1 User Interface of PIPENET
VISION are relevant to this module and should be read prior to reading the training manuals
for this module. In this document, the main concepts and features that are specific to the
Spray/Sprinkler Module are described.
2.
Concepts
2.1
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
Pfric
2 f ( L Le ) u 2
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 depends on the relative roughness of the pipe (i.e., pipe roughness
divided by pipe diameter) and the Reynolds Number, Re, which is defined as
Re
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
uD
where is the fluid viscosity. The standard values for f can be obtained from a graphical
representation known as the Moody Diagram. The friction factor is represented in PIPENET
VISION by the following empirical formulae (in which r is the surface roughness of the pipe).
Laminar flow (Re < 2000):
16
Re
0.27r 1.252
1
1.768 ln
D
f
Re f
Pfric
where
C1.85D 4.87
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
Pfric
4.52 ( L Le )Q1.85
C1.85D 4.87
where
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 UK gallons per minute,
D is the pipe diameter in inches,
C is the Hazen-Williams constant (or C-factor) for the pipe.
Pelev g Z
in which
g is the acceleration due to gravity,
Z is the change in elevation.
2.2
Pumps
In the simple pump model, the pump performance curve is used. The user inputs the flow
rate against head data at 100% rpm. PIPENET VISION can then calculate the performance
curve at other speeds, using the homologous relationships for pumps. This curve is normally
intended only for use only in the positive quadrant; in other words, when the flow and the
head are positive.
Three options are available for defining pump curves:
Quadratic function,
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
Cubic function,
Cubic spline functions.
These functions are applicable to values of Q that lie between the specified minimum and
maximum values (namely, Qmin and Qmax respectively).
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 not be a flow rate that gives no
pressure change (that is, all flow rates must correspond to a non-zero pressure
change, and so the performance curve must not cross the horizontal axis).
If a flow rate lies outside the range Qmin to Qmax, PIPENET VISION issues an appropriate
warning message, and then extrapolates the performance curve using the tangent to the
curve at either the minimum or maximum flow rate (whichever is appropriate).
PIPENET VISION calculates the power required by a pump based on an efficiency value. If
this efficiency value is not supplied, the pump is assumed to be 100% efficient for the purpose
of this calculation.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
Typically, the units for the pump curves are not the same as the units in which pressure-drop
calculations are to be made. For example, it is usual to specify the pump curve in head of
fluid, rather than psi. For this reason, the pump/fan module accepts data in its own units.
The dialog box for inputting a pump curve can be obtained by choosing Pumps Coeffs.
unknown from the Libraries Menu (which is denoted by Libraries | Pumps Coeffs
unknown in the PIPENET VISION training manuals). The resulting dialog box is shown
below.
PIPENET VISION takes into account the fact that the head generated by a pump is
independent of the density of the fluid, and so PIPENET VISION makes an appropriate
density correction in converting the head into a pressure. Similarly, the pressure generated
by a pump depends on the fluid, and when the pump curve is defined in terms of pressure, an
appropriate density correction is applied. This is the reason why, when the pumpperformance curve is defined in terms of pressure, the performance curve is interpreted to be
that of water.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
Type of
curve fitted
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
2.3
Non-Return Valves
Non-return valves allow unrestricted flow of fluid in a positive direction, and prevent all flow in
the reverse direction. Positive flow is taken to be in the direction from the valve's input node to
its output node, in which case there is no pressure drop across the component. Caution
should be exercised to avoid positioning a non-return valve such that it would isolate a portion
of the network. If this were to happen, the calculator could report the error message network
cannot be solved".
Note that, even if the solution to the problem involves the valve being open, PIPENET VISION
can still generate this error message. Occasionally, a non-zero "leakage flow" may be
reported through a closed valve. This flow, which arises from rounding errors that are smaller
than the requested convergence accuracy, is usually negligible.
Modelling Equations
Open valve:
P1 P2
Fully closed valve:
Q1 0
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
Continuity Equation:
Q1 Q2
The following variables are used in the above equations.
P1 is the inlet pressure,
P2 is the outlet pressure,
Q1 is the inlet flow rate,
Q2 is the outlet flow rate.
2.4
Filters
Strainers are usually modelled as equipment items. However, if the user wishes to model
them more accurately and the required data is available, the filter model can be used.
Filters are used in most of the networks to collect residue and dirt particles from the flow
medium. The filters can also be generated in PIPENET VISION by supplying the values of the
coefficients, A and B, in the modelling equations.
Modelling Equation
The modelling equation is
P AQ Q BQ
where
P is the pressure increase from the inlet to the outlet,
Q is the (volumetric) flow rate through the filter,
A is a coefficient (which is less than or equal to zero),
B is a coefficient (which is less than zero).
This equation is valid for values of Q whose modulus is less than a given maximum flow,
Qmax. Note that filters are reversible (i.e., Q may be negative), in which case, since
A 0 and B 0
the pressure drops in the direction of the flow.
2.5
Nozzles
Nozzle models in PIPENET VISION represent both the spray and sprinkler nozzles. The
modelling equation for the nozzle is
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
QK 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 specified minimum and maximum values (P min
and Pmax respectively). The range from Pmin to Pmax 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. When the K value of a nozzle
is referred to, the standard units for P and Q are bar and litres per minute respectively.
Data Required
In the library, the following data is required.
1. A nozzle descriptor to identify the type of nozzle (usually the manufacturers nozzle
name is used).
2. The nozzle K-factor.
3. The values of Pmin and Pmax.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
Notes
1. Nozzles do not have to be stored in a library. Instead, they can be defined by
specifying the values of K, Pmin and Pmax. However, when there are several nozzles of
the same type in the same network, it is easier to define the type in a library, as
described above.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
2. The flow rate required through a nozzle is used in the Design Facility of PIPENET
VISION.
2.6
Deluge Valves
Typically, users prefer to model a deluge valve as an equipment item, since an equipment
item requires only an equivalent length.
This length value can be either calculated or
obtained from the vendor of the deluge valve.
For the sake of completeness, this section contains an introduction to the deluge valve model.
Before a deluge valve can be added to a network, the valve must first be defined in the
private data file (via Libraries | Deluge valves). The dialog box for this option contains a list
of defined valve types.
A descriptor, manufacturer supplied K-factor and X-factor, and bore must be supplied.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
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 (with typical values being 1 and 2).
Typical Performance Curves
2.7
Overboard dump valves (or pressure safety valves) operate with a trigger pressure, P S. When
the pressure upstream of the valve is below the trigger pressure, P S, the valve remains shut;
on the other hand, when the pressure rises above P S, the valve opens. Once the valve is
open, the upstream pressure stabilises at the trigger pressure, P S.
In PIPENET VISION, an overboard dump valve is modelled as a special kind of outlet, and
there is no need to model the network downstream of the point at which the trigger pressure
is measured.
3.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
The rules that govern specifications in the Spray/Sprinkler Module are important. The
following notes will help the user to understand them. These rules are mainly concerned with
applying specifications to firewater ringmains.
Before a simulation can be performed, the user must provide PIPENET VISION with
information about pressures and/or flow rates at a number of nodes in the network. These
specifications must obey the rules described in this section. PIPENET VISION runs the
simulation in two phases; namely, the Design Phase and the Calculation Phase.
The aim of the Design Phase is to find suitable diameters for one or more pipes in the
network, so that the fluid velocity in each pipe and the pressure drop per unit length of pipe
remain within the design criteria. Even if all of the diameters are known, PIPENET VISION
still performs this phase.
In the Calculation Phase, PIPENET VISION performs the final analysis calculations.
For both phases, the user must specify the pressure and/or flow rate in various parts of the
network. The user must also specify the input and output nodes in the network. There are two
sets of specifications for each simulation: the design-phase specifications and the
calculation-phase specifications. So that the problem is mathematically solvable, these two
sets of specifications must obey certain rules. It should be noted that, in some simulations,
the user may not be interested in the results of one of the phases; however, both phases are
still run in PIPENET VISION, and so two sets of specifications need to be supplied.
The specifications have to adhere to the following rules.
1. There must always be at least one pressure specification. (If there is at least one
nozzle in the system, PIPENET VISION will automatically set its outlet pressure to 0
bar G, in which case a pressure need not be set by the user.)
2. The actual number of specifications must obey the rules in the following table.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
Phase
Np
Nf
Design
Nio 1
Analysis
Np
Nio - Np
3.1
When a network is being designed, it is a general requirement that the velocity of the fluid in
each pipe does not exceed a given value (known as the design velocity of the pipe). The
velocity of the fluid in a pipe depends on:
It is, therefore, important that all of the pipes are correctly sized, so that the fluid velocity does
not exceed the design velocity. This problem is addressed in the design phase of the
simulation.
Given the required flow rates in and out of the network, PIPENET VISION will find optimal
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 (a) all nozzles and (b) all but
one of the input and output nodes in the network. PIPENET VISION can then determine the
flow rates required throughout the network, and thus calculate optimal sizes for the pipes.
The total number of Design Phase flow-rate specifications must be one less than the number
of input/output nodes. This point is especially important for firewater ringmains, as they
typically have more than one input/output node.
The following points must be noted. By virtue of mass balance, the flow rates through all of
the input/output nodes can be calculated if the flow rate at one input/output node is left
unspecified. Moreover, the pipe diameters must be sized adequately to handle the required
flow rates, which is the reason why all the specifications during the design phase are flow
rates.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
If desired, the user can set the diameter of some (or all) pipes in the network.
PIPENET VISION 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 a pipe (or group of pipes) is being sized, PIPENET VISION will choose the
smallest pipe size that ensures that the design velocity is not exceeded by the fluid.
In the design phase, it is assumed 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. Consequently, the velocity of the fluid may 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. The user can resolve this problem by setting the
diameters of these pipes to be slightly larger than the design diameters.
In order to size all the pipes in a network, it may be necessary to perform more than one
simulation.
3.2
In the calculation phase, all the diameters of the pipes are known, as they are either (a) set by
the user or (b) determined by PIPENET VISION during the design phase. PIPENET VISION
simulates the behaviour of the network under the pressure and flow-rate conditions set by the
user. All nozzles in the network are assumed to discharge to atmospheric pressure. The user
must supply flow rates and/or pressures at various parts of the network by making Calculation
Phase Specifications (which are described in the next section). PIPENET VISION will then
calculate the pressures and flow rates throughout the network.
The total number of Calculation Phase flow-rate and pressure specifications must be equal to
the number of input/output nodes. This point is especially important for firewater ringmains,
as they typically have more than one input/output node. Usually, the pressures at pump inlets
are known and the flow rates at outlets are known. However, this is not a strict rule. For
example, if a pump-selection case is to be run, the pressure and flow rate will typically be
specified at the most remote output, and the input node would be left simply as an input (but
with no pressure or flow rate specified).
Typically, the calculation phase is used for one or more of the following purposes:
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 is issued for
any nozzle supplying at less than its required rate.)
4.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
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 for which the fluid velocity exceeds the
design velocity.)
When a calculation is run, a pipe-sizing operation is performed if (a) there are unset pipe
sizes and (b) the user has requested that the Design Phase be run. However, the user will
generally perform a pipe sizing-operation, possibly make some changes to the network, and
then perform another pipe-sizing operation, repeating these steps as required. Only when the
user is satisfied will he/she perform a calculation.
The controls relating to the Design and Calculation Phases are located on the Calculation
Toolbar:
4.1
Assumptions
1. The input and output nodes of a network are those points where fluid enters or leaves
the network.
2. Internal nodes are those nodes that are neither input nodes nor output nodes.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
4.2
Design Phase
1. There must be one (and only one) pressure specification, which may be applied at an
input node, an output node, or an internal node. This specification is automatically set
in PIPENET VISION, and so the user does not need to input it.
2. In a network, all but one of the input and output nodes must have a flow specification.
4.3
Calculation Phase
4.4
Simple Example
For a system with two inlets (pumps) and one outlet (deluge system), the specifications would
be as follows.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
5.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
Fire protection piping systems convey a fire-extinguishing substance from the source of
supply to devices and equipment for applying it in fire fighting and fire protection.
Water (owing to its effectiveness, availability, and low cost) is used most extensively as a fireextinguishing material. Other substances that are piped for fire fighting special types of fire
are foam, carbon dioxide (or other inert gases), vaporizing liquid, or dry chemicals in an inert
gas carrier.
The detailed procedures followed by fire-protection specialists in determining anticipated
water flows, in establishing pipe sizes, and in planning pipe locations and arrangement for
particular private installations are too highly specialised and too limited in application to be
allocated space for more than a brief mention here. Detailed information is available in the
publications included in the references that appear later in this section.
5.1
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
5.2
The Tariff Advisory Committee has compiled rules to provide minimum requirements for fixed
water spray systems, based on good engineering practices. While formulating the rules, due
consideration has been shown to the International Standards.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
According to the TAC Manual, full details on the Common Requirements to High Velocity
Water Spray and Medium Velocity Water Spray Systems are explained in the TAC manual,
and they are:
1. Water supplies.
2. Pumps - general requirements for electric driven, compression ignition engine driven
pumps, pump room, etc.
3. Detection system.
4. General requirements.
5. Piping.
6. Fittings.
7. Deluge valves.
8. Drainage.
Similarly, high-velocity water-spray systems and medium-velocity water-spray systems
are also explained in TAC Manual.
5.3
For Fire Protection Facilities for Petroleum Refineries & Oil/Gas processing plants,
the Oil Industry Safety Directorate staffed from within the industry for formulating and
implementing a series of self regulatory measures aimed at removing obsolescence,
standardizing and upgrading the existing standards to ensure safer operations. OISD
constituted a number of committees comprising of experts nominated from the industry to
draw up standards and guidelines on various areas of concern.
This standard covers the design criteria and the details of the various fire protection facilities
to be provided in petroleum refineries and oil/gas processing plants.
5.4
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
5.5
Classification Of Fires
Class 'A' Fires: Fires involving combustible materials of organic nature, such as wood,
paper, rubber and any plastics, etc., where the cooling effect of water is essential for
extinction of such fires.
Class 'B' Fires: Fires involving flammable liquids, petroleum products, or the like, where a
blanketing effect is essential.
Class 'C' Fires: Fires involving flammable gases under pressure, including liquefied gases,
where it is necessary to inhibit the burning gas at a fast rate with an inert gas, powder or
vaporizing liquid for extinguishment.
Class 'D' Fires: Fires involving combustible materials such as magnesium, aluminium, zinc,
sodium, potassium, when the burning metals are reactive to water and water-containing
agents, and in certain cases carbon dioxide, halogenated hydrocarbons and ordinary dry
powders. Special media and techniques are required to extinguish these fires.
5.6
The Fire Protection Philosophy is based on Loss Prevention and Control. The importance of
adequate fire protection facilities for hydrocarbon processing plants need not be emphasised,
as none of the plant is absolutely safe (because of the inherent hazard it carries). A fire in one
part/section of the plant can endanger other sections of the plant as well. If a fire breaks out, it
must be controlled/extinguished as quickly as possible, to minimize the loss to life and
property and to prevent further spread of fire.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
6.
6.1
Spray Options
The dialog box obtained from Options | Module options allows the user to control a number
of modelling and calculation options for the Spray/Sprinkler Module.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
6.2
Pipe Types
In the Spray Module, all pipes in a network must be of a specified type. A pipe type is
associated with a pipe schedule, and this schedule must already exist before the pipe type
can be created. There is an optional lining definition, which may be provided by specifying the
material and the lining thickness.
Please note that, if no pipe type is defined, the Pipe Drawing Tool on the toolbar is disabled,
and the message No Pipe Type appears in the status bar at the bottom of the screen. This
message will disappear when a pipe type is defined, in which case, the Pipe Button will be
enabled.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
5. Linings can also be provided using the drop-down menu (in which case, the thickness
of the lining must be given).
6. Click on the Apply Button to complete the creation of the pipe type.
6.3
Libraries
Libraries are used for storing items that are to be used either (a) several times in the same
network or (b) in different networks.
The library is associated with the data file, and is opened when the data file is open. For the
Spray/Sprinkler Module, a library can contain the following items.
1.
2.
3.
4.
5.
Pipe schedules,
Nozzles,
Pumps (Coefficients Known and Coefficients Unknown),
Linings,
Deluge valves.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
There is only one local user library, which has the file extension .SLF, and replaces all of the
separate library files from previous modules. While a data file is open, entries can be added,
deleted or edited using the Library Editor Dialog. PIPENET VISION automatically saves the
library file when the Sunrise Data File or .SDF file is stored. The name of the library file is
derived from the name of the Sunrise Data File.
6.4
Pipe Schedules
Pipe schedules can be viewed using Libraries | Schedules. There are about eight built-in
pipe schedules in PIPENET VISION. The user is also able to define other pipe schedules.
On the left-hand side of the window is a list of available schedules, both built-in and userdefined. If you select any item in this list, the properties of the schedule are displayed on the
right-hand side of the window.
At the top right-hand corner, there are three fields common to all library editors:
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
1. The name of the schedule as it appears in pop-up menus (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 using the External System Library
Editor.
Below these three fields is a field that contains the roughness; and, below that field, is a grid
showing the standard nominal sizes and the corresponding internal diameters. If the 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; however, if you scroll
down to the end of the grid, you can see 10 user-defined sizes (for which both the nominal
and internal bores can be edited).
The roughness value and the diameters are displayed in the user-specified units.
6.5
Nozzles
The nozzles in PIPENET VISION correspond to the spray or sprinkler nozzles, which are
open to the atmosphere. To set the nozzle attributes, the user can either enter the values
directly in the schematic or obtain them from the library.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
The nozzle library dialog box can be accessed through Libraries | Nozzles.
To view a library nozzle, select the required nozzle from the left-hand side of the window, and
see its properties on the right-hand side. To delete a nozzle, select the nozzle (in the left-hand
side of the window) and then click on the Delete Button.
To add a new nozzle:
1. Click on the New Button.
2. Provide a unique name for the nozzle and an optional description.
3. Enter the values for the K-factor, minimum pressure, and maximum pressure.
4. Click on the Apply Button to add the nozzle to the library.
6.6
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
Linings
Linings for the pipes are provided to protect the inner surface of the pipe from corrosion,
which is caused by the fluid medium. In most fire systems, fluid remains stagnant, resulting in
a higher rate of corrosion. The linings can be concrete, epoxy, thermo setting plastic,
asbestos, etc.
To view a library lining, select the required lining from the left-hand side of the window (and its
properties are displayed on the right-hand side). To delete a lining, select the lining, and then
click on the Delete Button.
To add a new lining:
1. Click on the New Button.
2. Provide a unique name for the lining and an optional description.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
6.7
Deluge Valves
Typically, deluge valves are modelled as equipment items. As mentioned earlier in this
chapter, deluge valves still available in PIPENET VISION for historical reasons. Without this
model, it might not be possible to open some older data files. For the sake of completeness,
the method of inputting deluge valves is described below.
To view a library deluge valve, select the required deluge valve from the left-hand side of the
window, and see its properties on the right-hand side. To delete a deluge valve, select the
deluge valve, and then click on the Delete Button.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
7.
Any description of PIPENET VISION would be incomplete without the following features being
covered.
7.1
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
A local edit can be performed in a similar manner. In this case, the user must select the pipes
to which the copied value is to be pasted.
7.2
This invaluable feature can be used, for example, to determine the pipe with the maximum
velocity or the maximum pressure. This sorting can be performed in the data window.
Select the
Results Tab
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
7.3
Copy/Paste to a Spreadsheet
Click here to
select the results
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
7.4
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
Some fire engineers prefer to use the style of presentation shown in the NFPA rules. This
style is available in PIPENET VISION, and is obtained (after a calculation) by using
Calculation | Browse, and then selecting the NFPA Submittal Option.
Location
Drawing Number
Date
13-Mar-2014 at 10:30
Design
Remote Area Number
Occupancy Classification
Density
Area of Application
6 of which 6 are on
In Rack Demand
634.355 l/min
at Pressure
Type of System
Location
Source
Contractor Information
Name of Contractor
Address
Phone Number
Name of Designer
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
Page 42
Notes
SUPPLY ANALYSIS
Node at Source
Notes
Please enter Supply Information Manually, to get these values from PIPENET, please select a reference node and appropriate Hydraulic curve values from PIPENET
NODE ANALYSIS
Node tag
Elevation (m)
Node Type
Pressure (Bar G)
Discharge (l/min)
0.00
INPUT
4.955
2.00
2.00
SPRINKLER
4.295
107.768
2.00
SPRINKLER
4.067
104.871
2.00
SPRINKLER
4.295
107.768
2.00
SPRINKLER
4.067
104.871
2.00
2.00
SPRINKLER
4.042
104.539
2.00
SPRINKLER
4.042
104.539
Notes
4.324
4.268
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
PIPE INFORMATION
Flow added
(q)(l/min)
Node 1
Elev 1
(m)
K factor
Total flow
(Q)(l/min)
Node 2
Elev 2
(m)
Actual ID(mm)
Pipe label
Nozzle label
Pipe Flow
(l/min)
212.639
212.639
209.077
0.00
Pt (1) (Bar
G)
L (m)
Nominal
ID(mm)
Fittings quantity,
type, and
equivalent
length (m)
C factor
F (m)
Q (m)
Notes
Pe (Bar)
Pf per m
(Bar)
Pf (Bar)
Pipe Type
T (m)
Pt (2) (Bar
G)
10.000
4.955
50
140.0
0.000
0.196
52.000
2*
2.00
634.355
634.355
0.044
SEA Schedule
: No lining
10.000
4.324
5.000
2
2.00
52.00
104.871
107.768
0.435
4.324
50
140.0
0.000
0.000
52.000
212.639
3*
2.00
2
3
0.000
212.639
0.006
0.029
SEA Schedule
: No lining
5.000
4.295
5.000
4.295
25
3
2.00
52.00
140.0
0.000
104.871
4*
2.00
2.00
3
4
52.00
104.871
104.871
107.768
0.000
26.000
0.046
0.228
SEA Schedule
: No lining
5.000
4.067
5.000
4.324
50
140.0
0.000
0.000
52.000
212.639
5*
2.00
4
2
0.000
212.639
0.006
0.029
SEA Schedule
: No lining
5.000
4.295
5.000
4.295
25
5
2.00
52.00
140.0
0.000
104.871
6*
2.00
5
1
104.871
0.000
26.000
0.046
SEA Schedule
: No lining
5.000
4.067
10.000
2
104.539
104.539
2.00
0.228
4.324
50
140.0
0.000
0.000
52.000
209.077
7*
2.00
0.000
209.077
0.006
0.056
SEA Schedule
: No lining
10.000
4.268
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
Page 44
PIPE INFORMATION
Flow added
(q)(l/min)
Node 1
Elev 1
(m)
K factor
Elev 2
(m)
Pipe label
Nozzle label
Total flow
(Q)(l/min)
Node 2
Pipe Flow
(l/min)
Pt (1) (Bar
G)
L (m)
Nominal
ID(mm)
Actual ID(mm)
Fittings quantity,
type, and
equivalent
length (m)
C factor
F (m)
Notes
Pe (Bar)
Q (m)
Pf per m
(Bar)
Pf (Bar)
Pipe Type
T (m)
Pt (2) (Bar
G)
5.000
4.268
25
7
2.00
52.00
140.0
0.000
104.539
8*
2.00
7
6
0.000
26.000
104.539
0.045
0.227
SEA Schedule
: No lining
5.000
4.042
5.000
4.268
25
7
2.00
52.00
140.0
0.000
104.539
9*
2.00
8
5
0.000
26.000
104.539
0.045
0.227
SEA Schedule
: No lining
5.000
4.042
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 and are always the flow outlets
To calculate Pt (2) from Pt (1) subtract elevation pressure and friction loss
K-Factor is considered for the nozzles only
Notes use actual labels for their pressure values
L - Pipe Length, F - Fittings Equivalent Length, Q - Special Equipment Item Equivalent Length, T - Total Equivalent Length
Standard 45 Elbow
Standard 90 Elbow
LE
Gate Valve
NR
Non-return Valve
BV
Ball Valve
Butterfly Valve
7.5
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
Elevation mismatch errors in firewater ringmains are some of the most difficult problems to
resolve. However, PIPENET VISION has tools to assist the user in resolving such problems.
Let us consider the highlighted pipe in the following simple network.
The attributes of this pipe are as shown in the Properties Window below.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
Let us suppose that the user has made an error, and has input an elevation of 1 metre
(instead of 0 metres). We now change the elevation value to 1 metre, and then illustrate the
tools in PIPENET VISION that can be used to resolve this elevation error.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
If we click on the Check Network Button, a diagnostic appears. However, in some cases,
there is little information on the exact location of the error.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
We now double click on an error message (shown in red), which indicates an elevation error.
All of the components in the loop in which the elevation error occurs now appear in red. Note
that the user must ensure that suitable colouration-display rules are selected; for example, if
None is selected, it is possible to see the red loop; otherwise, the loop may not be coloured
red.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
We now click on the Graphs Tab in a Data Window. The elevation profile along the loop is
then shown in the Data Window, starting and ending at Node 1. Note that the node numbers
can be displayed on the profile.
SPRAY: CHAPTER 1
REVISION 2.1, SEP 2010
Alternatively, we can click on the Common Height Errors Button on the Diagnostic Window.
In this case, only the pipes common to more than one problem loop are shown.
Common Height
Errors Button
In some cases, this approach leads to fewer pipes for which the elevations need to be
checked.