Documente Academic
Documente Profesional
Documente Cultură
TRAINING MANUAL
SPRAY/SPRINKLER MODULE
CHAPTER 1
1. INTRODUCTION..............................................................................................................................................2
2. CONCEPTS .....................................................................................................................................................3
2.1 PRESSURE DROP MODEL ...............................................................................................................................3
2.2 PUMPS ..........................................................................................................................................................6
2.3 NON-RETURN VALVES................................................................................................................................. 10
2.4 FILTERS...................................................................................................................................................... 11
2.5 NOZZLES .................................................................................................................................................... 11
2.6 DELUGE VALVES ......................................................................................................................................... 14
2.7 OVERBOARD DUMP VALVES ........................................................................................................................ 15
3. RULES GOVERNING SPECIFICATIONS ................................................................................................... 16
3.1 THE DESIGN PHASE .................................................................................................................................... 16
3.2 THE ANALYSIS PHASE ................................................................................................................................. 18
4. THE USER INTERFACE AND THE DESIGN AND ANALYSIS PHASES .................................................. 19
4.1 ASSUMPTIONS ............................................................................................................................................ 19
4.2 DESIGN PHASE ........................................................................................................................................... 20
4.3 ANALYSIS PHASE ........................................................................................................................................ 20
4.4 SIMPLE EXAMPLE ........................................................................................................................................ 20
5. GENERAL CONCEPTS OF FIRE PROTECTION SYSTEM ....................................................................... 22
5.1 STANDARDS, RULES AND REGULATIONS....................................................................................................... 22
5.2 TARIFF ADVISORY COMMITTEE .................................................................................................................... 23
5.3 OIL INDUSTRY SAFETY DIRECTORATE (OISD) .............................................................................................. 23
5.4 CLASSIFICATION OF PETROLEUM PRODUCTS ............................................................................................... 24
5.5 CLASSIFICATION OF FIRES .......................................................................................................................... 24
5.6 FIRE PROTECTION PHILOSOPHY .................................................................................................................. 25
6. ADDITIONAL INFORMATION ON THE USER INTERFACE ...................................................................... 26
6.1 SPRAY OPTIONS ......................................................................................................................................... 26
6.2 PIPE TYPES ................................................................................................................................................ 27
6.3 LIBRARIES .................................................................................................................................................. 29
6.4 PIPE SCHEDULES ........................................................................................................................................ 30
6.5 NOZZLES .................................................................................................................................................... 32
6.6 LININGS ...................................................................................................................................................... 34
6.7 DELUGE VALVES ......................................................................................................................................... 35
6.8 GENERAL PRESSURE LOSS COMPONENTS ................................................................................................... 36
7. OTHER USEFUL FEATURES OF PIPENET VISION .................................................................................. 37
7.1 GLOBAL AND LOCAL EDIT ............................................................................................................................ 37
7.2 SORTING IN COLUMNS IN THE DATA W INDOW ............................................................................................... 39
7.3 COPY/PASTE TO A SPREADSHEET ................................................................................................................ 41
7.4 NFPA STYLE OF OUTPUT ............................................................................................................................ 43
7.5 ELEVATION ERROR CORRECTION................................................................................................................. 47
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 2 OF 53 REVISION 3.0, NOV 2015
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.
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 3 OF 53 REVISION 3.0, NOV 2015
2. Concepts
Full details of the equations that are used to calculate these pressure losses are described
below.
𝑃fric is determined using the Bernoulli Equation, which is a theoretical equation that gives the
pressure in pipes, ignoring frictional effects. The pressure drop due to friction effects can be
found by comparing the theoretical results from the Bernoulli Equation with results obtained in
experiments. Based on the work of the French engineer Henri Darcy (1803–58) the following
equation is obtained.
2𝑓(𝐿 + 𝐿𝑒 )𝜌𝑢2
𝑃fric =
𝐷
where
𝜌𝑢𝐷
𝑅𝑒 =
𝜇
where 𝜇 is the fluid viscosity. The standard values for 𝑓 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 𝑟 is the surface roughness of the pipe).
16
𝑓=
𝑅𝑒
Transitional flow (2000 < 𝑅𝑒 < 3000):
The value of 𝑓 is obtained by interpolating between the laminar value for 𝑅𝑒 = 2000 and the
turbulent value at 𝑅𝑒 = 3000.
1 0.27𝑟 1.252
= −1.768 ln ( + )
√𝑓 𝐷 𝑅𝑒 √𝑓
It should be noted that, for maximum flexibility, the user is allowed to override the roughness
or C-factor value of the pipe type when entering the individual pipe data. However, by default,
the roughness or C-factor of each pipe will be determined by the pipe type of a particular pipe.
The Hazen-Williams Equation is an empirical formula that gives an explicit expression for the
frictional pressure loss.
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 5 OF 53 REVISION 3.0, NOV 2015
SI Units
4.52(𝐿 + 𝐿𝑒 )𝑄1.85
𝑃fric =
𝐶 1.85 𝐷 4.87
where
𝑃elev = 𝜌𝑔𝑍
in which
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.
Quadratic function,
Cubic function,
Cubic spline functions.
These functions are applicable to values of 𝑄 that lie between the specified minimum and
maximum values (namely, 𝑄min and 𝑄max respectively).
An alternative method, which is seldom used, is for the user to enter the coefficients 𝐴, 𝐵 ,
and 𝐶 that define the pump-performance curve. In this case, the minimum and maximum
values for the flow rate must also be given.
In order for the calculator to function correctly, it is necessary to ensure that there is only one
flow rate that corresponds to each pressure gain, and so the following restrictions apply:
For flow rates between 𝑄min and 𝑄max , the slope of the performance curve must be
negative or zero.
For flow rates between 𝑄min and 𝑄max , 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).
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 7 OF 53 REVISION 3.0, NOV 2015
If a flow rate lies outside the range 𝑄min to 𝑄max , 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.
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 TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 8 OF 53 REVISION 3.0, NOV 2015
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 pump-
performance curve is defined in terms of pressure, the performance curve is interpreted to be
that of water.
Note that the definition of the pump curve is accepted only if at least three points are supplied,
and that the slope of the calculated curve is negative everywhere between the minimum and
maximum values.
Type of
curve fitted
Deleting a Pump
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 10 OF 53 REVISION 3.0, NOV 2015
In this case, the pump coefficients that define the performance curve can be obtained from
the manufacturer. These coefficients are then entered into PIPENET VISION using Libraries
| Pumps – Coeffs. known, and a pump-performance curve is produced.
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:
𝑃1 = 𝑃2
Fully closed valve:
𝑄1 = 0
Continuity Equation:
𝑄1 = 𝑄2
The following variables are used in the above equations.
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, 𝐴 and 𝐵 , in the modelling equations.
Modelling Equation
𝑃 = 𝐴𝑄 |𝑄 | + 𝐵𝑄
where
This equation is valid for values of 𝑄 whose modulus is less than a given maximum flow,
𝑄max . Note that filters are reversible (i.e., 𝑄 may be negative), in which case, since
𝐴 ≤ 0 and 𝐵 < 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
𝑄 = 𝐾√𝑃
where
This equation holds for values of 𝑃 between specified minimum and maximum values (𝑃min
and 𝑃max respectively). The range from 𝑃min to 𝑃max is known as the working pressure range
of the nozzle.
Note that the value of 𝐾 depends on the units used for 𝑃 and 𝑄. When the 𝐾 value of a
nozzle is referred to, the standard units for 𝑃 and 𝑄 are Bar and litres per minute respectively.
Data Required
1. A nozzle descriptor to identify the type of nozzle (usually the manufacturer’s nozzle
name is used).
2. The nozzle K-factor.
3. The values of 𝑃min and 𝑃max .
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 13 OF 53 REVISION 3.0, NOV 2015
1. The nozzle status (i.e., “on” or “off”). Note that, if a nozzle is off, there is a small solid
circle inside the nozzle symbol (in the schematic diagram), as indicated below.
Notes
2. The flow rate required through a nozzle is used in the Design Facility of PIPENET
VISION.
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.
Modelling Equation
𝑄𝑋
𝑃=
𝐾
where
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 15 OF 53 REVISION 3.0, NOV 2015
Overboard dump valves (or pressure safety valves) operate with a trigger pressure, 𝑃𝑆 . When
the pressure upstream of the valve is below the trigger pressure, 𝑃𝑆 , the valve remains shut;
on the other hand, when the pressure rises above 𝑃𝑆 , the valve opens. Once the valve is
open, the upstream pressure stabilises at the trigger pressure, 𝑃𝑆 .
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.
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 16 OF 53 REVISION 3.0, NOV 2015
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 Analysis 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 Analysis 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
analysis-phase specifications. So that the problem is mathematically solvable, these two
sets of specifications must obey certain 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.
Phase 𝑵𝒑 𝑵𝒇
Design 1 (set by PIPENET VISION) 𝑁𝑖𝑜 – 1
Analysis 𝑁𝑝 ≥ 1 𝑁𝑖𝑜 − 𝑁𝑝
𝑁𝑖𝑜 is the sum of the number of inputs and the number of outputs (ignoring nozzles),
𝑁𝑝 is the number of pressure specifications,
𝑁𝑓 is the number of flow specifications.
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.
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.
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 18 OF 53 REVISION 3.0, NOV 2015
In order to size all the pipes in a network, it may be necessary to perform more than one
simulation.
In the analysis 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 Analysis
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 Analysis 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 analysis 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.)
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.)
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 19 OF 53 REVISION 3.0, NOV 2015
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:
1. The two buttons A and D correspond to the Analysis and Design Phases respectively
and the B button corresponds to both. The Analysis Phase only button is selected by
default.
2. The user enters the network and, if he/she requires PIPENET VISION to perform a
Design Phase, then pipes may be entered with undefined bores.
3. When the user has entered the network he/she will select the D and calculate to size
the undefined pipes. The calculated pipe sizes are returned to the user, where they are
displayed along with other pipe attributes. Note that, if another pipe-sizing operation is
performed, the sizes may change if changes are made to the network.
5. When the user is satisfied with the network, he/she should select the A Button to fix the
designed pipe sizes, and then perform a calculation (by pressing the third button on the
Calculation Toolbar).
6. The user can revert to the Design Phase by selecting the D Button; however, the bores
of pipes that were fixed in Step 5 do not become unset.
7. To perform the Design phase and Analysis Phase consecutively select the B button
and perform a calculation.
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.
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 20 OF 53 REVISION 3.0, NOV 2015
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.
For a system with two inlets (pumps) and one outlet (deluge system), the specifications would
be as follows.
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 fire-
extinguishing 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 generally recognized standards that cover fire-protection piping are those developed by
the National Fire Protection Association and by insurance organizations such as the
American Insurance Association, the Factory Mutual Engineering Corporation and the
Factory Insurance Association.
The general recognised standards that relate to fire protection piping are listed below. Note
that the fire protection hand books in References 1 and 2 contain much of the information in
the individual standards, and may provide all the information that is required.
The following standards are all available in the National Fire Protection Association.
The following general references relate to certain aspects of the problems that are
involved in the design and specification of the fire protection system.
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.
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.
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
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 24 OF 53 REVISION 3.0, NOV 2015
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.
Class 'A' Petroleum: Liquids that have a flash point below 23 degrees C.
Class 'B' Petroleum: Liquids that have a flash point of 23 degrees C or above, but below 65
degrees C.
Class 'C' Petroleum: Liquids that have flash point of 65 degrees C or above, but below 93
degrees C.
Excluded Petroleum: Liquids that have a flash point of 93 degrees C or above. Liquefied
gases, including LPG, do not fall under this classification but form a separate category.
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
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 25 OF 53 REVISION 3.0, NOV 2015
agents, and in certain cases carbon dioxide, halogenated hydrocarbons and ordinary dry
powders. Special media and techniques are required to extinguish these fires.
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.
1. Facilities should be designed on the basis that city firewater supply is not available
close to the installation.
2. Fire protection facilities shall be designed to fight two major fires simultaneously,
anywhere in the installation. Fire-water requirements will be decided as per guidelines
given in the Annexure of OISD.
The fire water system in an installation shall be designed to meet the fire water flow
requirement for fighting two fires simultaneously, requiring largest water demand.
Consider different cases (for example, the fire water rate of five different cases), and calculate
the flow rate for each case. Then, the total design fire water rate is the sum of water rates for
the two major fires.
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 26 OF 53 REVISION 3.0, NOV 2015
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.
The Hazen-Williams Equation must be used for water and foam solution systems, and the
Darcy Equation must be used for foam concentrate systems.
NFPA pre-1996
NFPA 2013
FOC
OLDFOC
These norms are in-built into the Spray/Sprinkler Module.
There are two modes provided in this module. In the spray mode, all the nozzles input is open
by default; and in the sprinkler mode, all the nozzles input are closed by default.
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.
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 28 OF 53 REVISION 3.0, NOV 2015
2. Select the associated schedule from the drop-down list provided. Note that a name
and a description are supplied automatically.
3. Provide a C-factor for the pipe schedule. The C-factor value will be taken into
consideration when the Hazen-Williams Formula is selected for performing the
calculation.
4. Supply velocities for all bores that are to be provided by the schedule. Bores can be
marked as available or unavailable by selecting the bore in the bottom right-hand
corner of the window and clicking on the “Use in design” Button or “Avoid in design”
Button as appropriate (and the default is for all valid bores to be marked as available).
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 29 OF 53 REVISION 3.0, NOV 2015
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. Pipe schedules,
2. Nozzles,
3. Pumps (Coefficients Known and Coefficients Unknown),
4. Linings,
5. Deluge valves.
6. General pressure loss components
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 30 OF 53 REVISION 3.0, NOV 2015
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”.
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.
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 31 OF 53 REVISION 3.0, NOV 2015
On the left-hand side of the window is a list of available schedules, both built-in and user-
defined. 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:
1. The name of the schedule as it appears in pop-up menus (the length of this name
being limited to 20 characters).
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.
The roughness value and the diameters are displayed in the user-specified units.
To add a new schedule, select the New Button in the bottom left-hand corner of the dialog
box, enter the desired values (if the Description Field is left empty, the description will become
the same as the schedule name). Next, enter the roughness and the diameters, and then
select either (a) the Apply Button, to accept the new schedule, or (b) the Cancel button, to
abort.
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.
The nozzle library dialog box can be accessed through Libraries | Nozzles.
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 33 OF 53 REVISION 3.0, NOV 2015
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.
3. Enter the values for the K-factor, minimum pressure, and maximum pressure.
6.6 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.
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.
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 36 OF 53 REVISION 3.0, NOV 2015
2. Provide a unique name for the deluge valve and an optional description.
4. Click on the Apply Button to add the deluge valve to the library.
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.
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 37 OF 53 REVISION 3.0, NOV 2015
Any description of PIPENET VISION would be incomplete without the following features being
covered.
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.
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.
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 40 OF 53 REVISION 3.0, NOV 2015
Select the
Results Tab
This section shows how to use Excel for editing PIPENET when a user finds it more
convenient. This is a two-way process where data is copied from PIPENET into Excel, edited
in Excel and pasted back into PIPENET.
From the PIPENET data window, the full table including headers can be selected by clicking
the icon at the top left. Alternatively, a subset of complete rows can also be edited in this
manner as long as the structure is preserved.
Select All
Once the data is edited in Excel it can be copied and pasted straight back to the PIPENET
data window. To do this, select everything minus the headings in Excel and copy it.
Then in the PIPENET data window click and drag to select the necessary cells and then
paste.
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 42 OF 53 REVISION 3.0, NOV 2015
Caution:
If the rows are reordered in Excel, the following warning message will be produced when this
is pasted back into PIPENET in this format.
The result of this is the original order of the rows in the PIPENET data window is preserved
but the other information is reversed.
It is also important to note that if a pipe diameter not included in the schedule is pasted into
the data window, it will appear as unset.
The same rules apply for other parameters selectable via combo box rather than typed.
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 43 OF 53 REVISION 3.0, NOV 2015
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
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
SUPPLY ANALYSIS
Notes
Please enter Supply Information Manually, to get these values from PIPENET, please select a reference node and appropriate Hydraulic curve values from PIPENET
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 45 OF 53 REVISION 3.0, NOV 2015
NODE ANALYSIS
Node tag Elevation (m) Node Type Pressure (Bar G) Discharge (l/min) Notes
2 2.00 3.958
7 2.00 3.907
The node order in the table may not reflect the order of nodes in the network.
Discharge values are only shown for flow exiting the network.
PIPE INFORMATION
Pt (1) (Bar
L (m) G)
Nominal
Node 1 Elev 1 K factor Flow added (q) ID(mm) Fittings - C factor Notes
(m) (l/min) quantity, F (m) Pe (Bar)
type, and
Actual ID(mm) equivalent
Node 2 Elev 2 Pipe label Pipe flow length (m) Q (m) Pf per m Pf (Bar)
(m) Nozzle label (l/min) (Bar)
Pipe type
T (m) Pt (2) (Bar
G)
10.000 3.958
50
2* 2.00 203.424 140.0
203.424 0.000 0.196
199.994 52.000 Vel = 4.762 m/sec
5.000 3.932
50
3* 2.00 52.00 140.0
100.317
0.000 0.000
103.107
52.000 Vel = 1.596 m/sec
5.000 3.932
5.000 3.932
50
5* 2.00 52.00 140.0
100.317
0.000 0.000
103.107
52.000 Vel = 1.596 m/sec
5.000 3.722
25
6* 2.00 52.00 140.0
0.000 0.000
26.000 Vel = 3.149 m/sec
100.317
5 2.00 5 0.000 0.042 0.210
1 SEA Schedule
: No lining
5.000 3.932
10.000 3.907
50
7* 2.00 140.0
99.997
0.000 0.000
99.997
52.000 Vel = 1.570 m/sec
PIPE INFORMATION
Pt (1) (Bar
L (m) G)
Nominal
Node 1 Elev 1 K factor Flow added (q) ID(mm) Fittings - C factor Notes
(m) (l/min) quantity, F (m) Pe (Bar)
type, and
Actual ID(mm) equivalent
Node 2 Elev 2 Pipe label Pipe flow length (m) Q (m) Pf per m Pf (Bar)
(m) Nozzle label (l/min) (Bar)
Pipe type
T (m) Pt (2) (Bar
G)
5.000 3.698
25
8* 2.00 52.00 140.0
0.000 0.000
26.000 Vel = 3.139 m/sec
99.997
7 2.00 7 0.000 0.042 0.209
6 SEA Schedule
: No lining
5.000 3.907
5.000 3.698
25
9* 2.00 52.00 140.0
0.000 0.000
26.000 Vel = 3.139 m/sec
99.997
7 2.00 8 0.000 0.042 0.209
5 SEA Schedule
: No lining
5.000 3.907
Notes
For full NFPA compliance, a detailed schematic drawing from PIPENET is required, showing pipe labels 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) add elevation pressure and friction loss
K-Factor is considered for the nozzles only
Notes use actual labels for their pressure values
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 47 OF 53 REVISION 3.0, NOV 2015
L - Pipe Length, F - Fittings Equivalent Length, Q - Special Equipment Item Equivalent Length, T - Total Equivalent Length
HE Standard 45° Elbow E Standard 90° Elbow LE Long radius 90° Elbow
T Tee or Cross (Flow turned 90°) G Gate Valve C Swing Check Valve
Network Schematic
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.
The attributes of this pipe are as shown in the Properties Window below.
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 48 OF 53 REVISION 3.0, NOV 2015
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 49 OF 53 REVISION 3.0, NOV 2015
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.
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.
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 50 OF 53 REVISION 3.0, NOV 2015
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 51 OF 53 REVISION 3.0, NOV 2015
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.
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.
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 52 OF 53 REVISION 3.0, NOV 2015
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.
PIPENET VISION TRAINING MANUAL SPRAY: CHAPTER 1
PAGE 53 OF 53 REVISION 3.0, NOV 2015
Common Height
Errors Button
In some cases, this approach leads to fewer pipes for which the elevations need to be
checked.