Pipe2008: KYPipe Devices

Examples Manual
KYPIPE LLC, USA
Contents
Chapter 1. Introduction………………………………………………….………………………………5
1.1 List of examples …………………………………………………………………………….6
1.2 Modeling assumptions and limitations ...........................................................................8
1.3 TranSurge features ........................................................................................................9
1.4 TranSurge shortcuts......................................................................................................10
Chapter 2. Examples………………...……………………………………………….… …………….11
2.1 T1.P2K: Full pump trip with NO protection………………………………………………11
Protection from Surges…………………………………………………………………………22
2.2 T2.P2K: Full pump trip with protection……………………………………………………25
2.3 T3.P2K Single Pump Trip Under Multiple Pump Operation……………………………46
2.4 T4.P2K Single Pump Operation and Trip………………………………………………..48
2.5 T5.P2K Emergency Shutdown…………………………………………………………….50
2.6 T6.P2K Normal Pump Shutdown…………………………………………………………54
2.7 T7.P2K Pump Switchover Operation……………………………………………………..56
2.8 T8.P2K Full Pump Trip Followed by Pump Startup……………………………………..58
2.9 T9.P2K Normal Pump Startup……………………………………………………………..60
2.10 T10.P2K Pump Startup with Pump Control Valve and NO Check Valve…………….62
2.11 T11.P2K Surge Protection with Closed Surge Tank…………………………………...66
2.12 T12.P2k Surge Protection with Hydraulically Actuated Surge Anticipation Valve…..68
2.13 T13.P2k Surge Protection with Electrically Actuated Surge Anticipation Valve……..70
2.14 T14.P2K Surge Protection Using Quick Opening Pressure Relief Valve (PRV)……..72
2.15 T15.P2K Non-Linear Valve Closure (Valve Stroking)………………………………….74
2.16 T16.P2K Valve Opening……………………………………………………………………77
2.17 T17.P2K Demand Changes, Hydrant Flow Simulation……………………….………..78
2.18 T18.P2k Grade Changes…………………………………………………………..……..79
2.19 T19.P2K Periodic Input (Grade Change Example)………………………..…………...80
2.20 T20.P2K Turbine Load Rejection…………………………………………………………81
2.21 T21.P2K Turbine Partial Load Rejection…………………………………………………82
2.22 T22.P2K Turbine Full Load Rejection with Wicket Gate Operation……………………83
2.23 T23.P2K Surge Protection with Open Surge Tank………………………………….…..84
2.24 T24.P2K Surge Protection with One-Way Open Surge Tank……………………….…85
Chapter 3. Applications of TranSurge…………………………………………………………………..86
3.1 Cooling Water System……………………………………………………………..………..87
3.2 Crude Oil Pipeline…………………………………………………………………………….89
3.3 Long Pipelines with Inline Booster……………………………………………………..…..91
3.4 Pumping Water to Multiple Elevated Storage Tanks…………………………………..…94
3.5 Groundwater and Surface Water Collection System………………………………….…..96
Appendix A. Limitations of TranSurge demo version ……………….……………………………..…98
LICENSE AGREEMENT
This is a legal agreement between the user and KYPipe LLC. By accepting, using or installing any portion of this software the user agrees to be bound by the
terms of this agreement.
SOFTWARE LICENSE
GRANT OF LICENSE: For each license purchased from KYPipe, LLC, or one of its authorized distributors, KYPipe LLC grants to the user the right to use one copy
of the software program(s) on a single terminal connected to a single computer (i.e., with a single CPU). The user may not network non-network versions of
the software or otherwise use single user versions on more than one computer terminal at the same time. Network versions are only to be used with one
physical site (buildings at the same mailing address) and are not to be used in a WAN environment. The number of network licenses purchased for a network
version is the maximum number of users permitted to run the software concurrently. If granted for an evaluation period by KYPipe LLC, user agrees not to use
the software beyond the evaluation period specified by KYPipe LLC. The user agrees not to utilize features, options, or number of pipes beyond the license the
user has purchased.
COPYRIGHT: The software and the documentation are owned by KYPipe LLC and are protected by United States copyright law and international treaty
provisions. The user must treat the software like any other copyrighted material except that the user may make one copy of the software solely for backup or
archival purposes or may transfer the software to a single hard disk and keep the original disk(s) sole for backup or archival purposes. The user may not copy
the written materials accompanying the software without explicit written permission from KYPipe, LLC.
TRANSFER BY USER: The user may not rent, lease, assign or permit others to use the software but may transfer the software and accompanying materials on
a permanent basis provided the user retains no copies and the recipient agrees to the terms of this agreement. As a condition to permit the recipient use the
software under this License Agreement, when such a transfer is made, KYPipe LLC must be notified, in writing, of the transfer, including the identity and
address of the recipient, and the agreement of the recipient to the terms of this License Agreement.
OTHER RESTRICTIONS: The user may not modify the software. The user may not reverse engineer, decompile, disassemble, or otherwise attempt to
determine the source code of the software. The user shall protect the software from unauthorized use, and shall protect the software and the intellectual
property from infringement by others. The user shall notify KYPipe, LLC, in writing, immediately upon receiving any information that would indicate that the
software is being used in an unauthorized manner or the intellectual property is being infringed.
DISCLAIMER
Although every reasonable effort has been made to ensure that the results obtained are correct, neither the author(s) nor KYPipe LLC assumes any
responsibility for any results or any use made of the results obtained with these programs. THE SOFTWARE IS SOLD AS IS WITH NO IMPLIED WARRANTIES,
INCLUDING WARRANTIES OF MERCHANTABILITY AND FITNESS FOR ANY PARTICULAR PURPOSE. NO EXPRESS WARRANTY EXISTS EXCEPT AS SPECIFICALLY SET
FORTH IN WRITING BY KYPIPE, LLC. IN NO EVENT, REGARDLESS OF THE NATURE OF ANY CLAIM, WILL KYPIPE, LLC, ITS MEMBERS OR AFFILIATES, BE LIABLE
FOR ANY LOSS FOR PERSONAL INJURY, BUSINESS INTERRUPTION, LOST PROFITS, OR INCIDENTAL OR CONSEQUENTIAL DAMAGES, AND ITS LIABILITY, IF ANY,
SHALL BE LIMITED TO THE PURCHASE PRICE OF THE SOFTWARE.
USE OF THE DOCUMENTATION AND PROGRAM
The documentation is provided for the use of individuals or companies which purchase it from KYPipe LLC. Except for back-up copies, the program disks or
documentation may not be copied, marketed, or distributed without explicit written permission from KYPipe, LLC. For users who wish to use the programs on
networks or multiple computers or different locations, network copies and multiple copy discounts may be obtained. Please contact KYPipe LLC for details.
GOVERNING LAW AND VENUE FOR ENFORCEMENT AND DISPUTES
This Agreement will be governed by and construed in accordance with the substantive laws of the Commonwealth of Kentucky, and, to the extent federal law
applies, to the laws of the United States. The state and federal courts of Fayette County, Kentucky, shall have exclusive jurisdiction over any claim brought
against KYPipe, LLC, and the user agrees to submit to the jurisdiction of the state and federal courts of Fayette County, Kentucky, in the event any claim is
brought against the user, and user waives all defenses to jurisdiction and inconvenience of forum.
Contact us
Software Development and Support Team
The following individuals are involved in the software development of Pipe2016 and models KYPipe, Surge, TranSurge, Gas, Steam, GoFlow,
and SWMM and directly support the software.
Don J. Wood
Ph.D, Civil Engineering
(859) 492-6097
[email protected]
Srinivasa Lingireddy
Ph.D, Civil Engineering
(859) 258-0469
[email protected]
Jana Faith
BS, Civil Engineering
(812) 843-4145
[email protected]
Doug Wood
MS, Computer Engineering
(859) 263-0401
[email protected]
Eric Liebenauer
MS, Mechanical Engineering
(859) 263-2234
[email protected]
Ferran Guillen
Mechanical Engineering by ETSEIB
(+034)938 712 483
[email protected]
KYPIPE LLC
710 Tom's Creek Rd. Cary, NC 27519, USA
Phone: (469) 250-1362 or (812) 843-4145
Chapter 1. Introduction
TranSurge is a very powerful modeling tool for analyzing transients in pipeline systems and design of effective surge protection systems. This
comprehensive examples manual is an attempt at streamlining the overwhelming number of features that this tool offers so the users can
quickly locate examples similar to their applications and complete their projects in a timely manner. Beginning users can strengthen their
modeling skills by exploring the already set up example models and the associated step by step instructions. Most examples make use of the
same baseline steady state model so users can focus their attention on setting up transient conditions, understand the effect of various
transient initiating conditions on pipeline systems, and design suitable and effective surge protection systems. Most of these models were set
up to run with the demo version of the software so future users can explore the software (see Appendix A for limitations for the demo version
of the software). Several examples are also included to demonstrate the real capabilities of the software in handling large complex pipeline
systems and the users exploring the software with a demo version should look at those examples to understand the full capabilities of the
software.
The example models cover a variety of applications including water supply, sanitary, oil and other chemical transport, cooling water systems,
slurry transport, etc., a comprehensive list of transient initiating events, and all surge protection devices. Table 1 lists the transient initiating
events covered in this manual along with the associated name of the example model for quick reference. Table 2 lists the surge protection
devices and the models that include those devices.
TranSurge comes with a powerful spreadsheet interface for building most transmission main models almost effortlessly. Users are strongly
encouraged to use that interface for building initial models (analysis without protection) as well as models with surge protection for rapid
estimates for protection measures. More comprehensive modeling and surge protection scenarios can be performed within TranSurge
graphical user interface.
The users are strongly encouraged to thoroughly review the entire TranSurge Users Manual before attempting several of the examples
presented in this manual. Material presented in Chapters 7 and 8 of TranSurge Users Manual should be reviewed at the minimum.
New examples will be added periodically and users are encouraged to download newer versions of this manual from www.kypipe.com.
5
1.1 List of examples
Table 1. Transient event and the associated example model
Transient Event
Example Models
Full pump trip
T1, T11, T12, T13, T14
Single pump trip while other pumps
run
Single pump trip during single
pump operation in a pump station
with multiple pumps
T3
Full pump trip followed by pump
startup
Pump startup
T8
Pump shutdown
T6
Pump switchover operation
T7
Emergency shutdown – valve at
delivery end of pipeline closed
rapidly followed by pump shutdown
T5
Nonlinear valve closure
T15
Valve opening
T16
Demand changes – hydrant flow
simulation
Grade changes
T17
Periodic input
T19
Turbine full load rejection
T20
Turbine partial load rejection
T21
Turbine full load rejection with
wicket gate operation
T22
T4
T9, T10
T18
6
Table 2. Surge protection device and the associated example model
Surge protection device
Example models
Closed surge tank (compressor
vessel)
Bladder surge tank
T11
Open surge tank (stand pipe)
T23
One-way open tank (one-way surge
tank)
Surge anticipation valve (SAV, HSAV,
ESAV)
Pressure relief valve
T24
Air valves
T2, T3, T4, T5, T6, T7, T8, T9, T10, T11
T2, T3, T4, T5, T6, T7, T8, T9, T10
T12, T13
T14
7
1.2 Modeling assumptions and limitations
• Like all other similar software programs, TranSurge assumes closed conduit flow conditions in the entire pipeline system for steady state as
well as throughout the transient simulation period. Portions of pipelines that might be flowing under open channel conditions should be
removed from the model for accurate prediction of transient pressure and flow conditions.
• Precise pressure and flow boundary conditions at the beginning of transient simulations are essential for accurate prediction of transient
pressure and flow conditions throughout the simulation period. When a portion of a pipeline system is isolated from a reservoir node (or
any other fixed grade node), there is no way to set pressure and flow boundary conditions in those isolated areas. For example, if there is a
branch line on a pipeline system with an active valve at the beginning of the branch line and all other nodes along the branch lines are
demand nodes (and no other connections to fixed grade), setting the active valve to OFF status for steady state isolates all demand nodes
from fixed grade nodes. A warning will be generated during a steady state analysis and the users should address this issue before
proceeding with surge analysis. Isolated areas are routinely encountered while simulating pump startup conditions (a closed pump and a
closed active valve in series, for example) and it is a good idea to run a steady state simulation before proceeding with transient simulation
to trap and provide a fix to isolated areas.
• A surge analysis is always preceded internally by a steady state analysis to establish the boundary conditions at the beginning of transient
simulation. This eliminates the need for steady state analysis before performing a surge analysis. However, It is a good practice to run
steady state analysis every time a change is made to the pipeline configuration or data to ensure good steady state results before
proceeding with surge analysis. Bad initial conditions, such as cavitation pressures at even one location along the pipeline, may lead to
erroneous results throughout the pipeline system .
8
1.3 TranSurge features
In addition to providing ultra-simple model development and results processing environment, TranSurge can model every possible
component and surge protection device common to transmission mains. The following shows a partial list of components and surge
protection devices that come with TranSurge software. It may be noted that the most commonly used devices from this list are also
available in spreadsheet format in the profile import tool which will be of a great help to beginning users.
• One-way surge tanks
• Open surge tanks or stand pipes (spilling and non-spilling types)
• Compressor surge vessels
• Bladder surge vessels
• Hybrid surge vessels with dipping tubes and compressors
• Kinetic air valves
• Dual orifice two-stage air valves
• Surge suppressing three-stage non-slam air valves
• Dynamic air valves
• Pressure relief valves
• Hydraulically actuated surge anticipation valves
• Electrically actuated surge anticipation valves
• Rupture disks
• Zero velocity valves
• Vacuum breakers
• Siphon breakers
• Check valves
• Dynamic check valves
• Hydraulic actuators (HOPD)
• Threshold opening pressures
• Non-reopening check valves
• Non-linear closure characteristics
• Initiate closure ahead of flow reversal
• Inline booster pumps
• Offline booster pumps
• Multiple pumps in parallel and series in each station
• PID controllers
• Standard and non-standard isolation and control valves
• Pressure reducing, pressure sustaining and flow control valves, and modulating regulating valves
9
• Turbines and wicket gates
1.4 TranSurge Shortcuts
10
Chapter 2. Examples
2.1 T1.P2K: Full pump trip with NO protection
Diameter of rising main is 900mm, with a pump station at lower end of the pipeline and discharging into atmosphere at the delivery end. There
are three operating pumps at pump station with a rated flow of 1200m 3/h each. Pipe material is cement mortar lined mild steel with a HazenWilliam roughness coefficient of 130. This example is the same as the “Demo 1 – Rising Main.P2K” model presented in the TranSurge User’s
manual. The schematic of the pipeline is shown below. Step by step instructions for building the transmission main model, simulation of a power
failure event (full pump trip) and sample processing of results are illustrated in the following.
620
610
600
590
580
570
560
550
540
0
1000
2000
3000
4000
5000
6000
7000
8000
Naming convention: All data associated with the model is stored to a master file with an extension .p2k., for example , “demo 1 – rising
main.p2k”. When a transient analysis is performed on a p2k model, the TranSurge graphical interface will generate several intermediate
data files and several other results files. Both intermediate and results files are generated to a separate folder that has the same name as
the master p2k model but with an extension kyp. For example, if the name of the model is T1.p2k, then all intermediate and results files
will be generated to a folder called T1.KYP in the same folder where T1.p2k is located. It is necessary to retain only the p2k file for future
use and all other intermediate and results files can be generated by analyzing the model.
11
Creating rising main model
Launch TranSurge using one of the following methods
.
2
3
4
Step
1
Or by clicking one of these icons
on desktop, if the icons are already
created
12
You should see this
blank opening screen of
TranSurge interface.
13
Access profile import tool
1 Click on this button to launch profile import tool
You should see the following main window of profile import tool
14
Browse demo files folder and load the excel file – “Demo 1 - Rising Main.xls ”
1
2
3
15
Provide additional data and generate transmission main model (p2k file)
3
4
1
5
2
6
Generates Pipe2000 file that
includes profile data, pipe
diameter, roughness, wave
speed, pump data and
transient event (pump trip).
7
8
9
10
Note: Data entered by the user (other than modifying spread sheet data) will be saved to a *.def file in the same folder
after step 10. It will be loaded along with the excel file data when the excel file is loaded next time.
16
You should see this
after the last step
Delivery
End
Save this model as T1.P2K for future use
Pumps
2
1
17
Analyze transmission main model
1
Steady State Analysis
2
Transient Analysis
Screen plot showing how pressure varies at
pump discharge after a pump trip event
18
Process results
1
Plot envelope of maximum and minimum pressure heads
2
Use Simple
Profile Style
19
Other available Styles are “Normal” animated profile (shown below) and the “Static” option. To view the “Static” profile,
select “Static” then exit the profilewindow. When you click on the show profile button once again the Static profile will load
(next image).
1
2
3
20
Static Profile
21
Protection From Surges
Surge Control Devices
Prevent Low Pressures
Admit air or water to pipe system
Prevent High Pressures
Expel water from pipe system
Active Surge Control
Add of remove energy to prevent surge conditions
Surge tanks
Passive Surge Control
Respond to surge situation
Air/vacuum valves, pressure relief valves
22
Surge Protection Options
(check)
23
Surge Protection Devices
Closed Bladder Surge TankFor both down- and up-surges,
especially at pump stations
Pump Bypass Line
For down-surges at pumps
with high inlet-side head
Open Surge Tank
At locations with low
hydraulic grade (high points)
Closed Compressor Surge Tank
Same as Bladder Tanks
Feed (one-way) Surge Tank
Down-surge only.
Can be in locations with higher
hydraulic grade than typical
Open Surge Tank
Surge Anticipation Valve
Initial down-surge is detected
activating the device
Air Release/Vacuum Valve
At high points in a pipeline
admits and releases air to
prevent vapor pressure
Pressure Relief Valve
Mainly for up-surge such
as upstream from a valve which
closes rapidly
2.2 T2.P2K: Full pump trip WITH protection
This example illustrates the use of a bladder vessel and an air valve to reduce the magnitudes of positive and negative surge pressures. Instead
of adding the surge control devices to the already generated T1.P2K model in the previous example, this example demonstrates the use of Excel
interface to quickly create a model with surge protection.
Note: Demo 2 – Rising Main.xls along with its
*.def file were setup to demonstrate this
example. Users may continue using the Demo 1
– Rising Main.xls file, provide additional data or
load Demo 2 – Rising Main.xls file which will
have all data entered as shown in subsequent
images.
1
2
3
25
1
3
Surge protection:
•
Bladder vessel at pump discharge
•
3m diameter
•
45m3
•
Precharge head of 30m
•
Connection resistance = 20
•
Air valve at highest elevation point
•
100mm 3-stage air valve
•
25mm smaller outflow orifice
•
2kPa switch pressure
7
8
2
5
6
4
5
9
26
Provide surge protection data
Surge protection:
•
Bladder vessel at pump discharge
•
3m diameter
•
45m3
•
Precharge head of 30m
•
Connection resistance = 20
•
Air valve at highest elevation point
•
100mm 3-stage air valve
•
25mm smaller outflow orifice
•
2kPa switch pressure
1
2
3
Additional settings
4
5
7
6
27
Perform Transient Analysis
1
You should see this
after the last step in the
previous slide
Screen plot showing how pressure
varies at pump discharge after a
pump trip event (with protection)
Note the surge tank at pump station
28
1
Plot envelope of maximum and minimum pressure heads
29
View node results graph
2
1
Save this model as T2.P2K for future use
Left click on this node
2
1
30
Pressure variation graph at node 6
31
Results Presentation
TranSurge offers a number of ways to process results from transient analysis.:
• Node and pipe graphs of several different parameters (pressure, hydraulic grade, pressure head, flow rate, pump speed, air
volume, etc.)
• Display data and results as labels on network map
• Tabulated text and spreadsheet formats
• Static and animated profile plots
This chapter demonstrates some of these features on Demo 2 – Rising Main example described in Chapter 3. Follow the instructions
presented in Section 3.4 to create and analyze the model before proceeding with the following sections.
Demo 2 – Rising Main.P2K
32
Node and pipe graphs
At the bottom of node information window
2
Click on any node
1
3
Pressure variation at node 19
Next page
33
From previous page
1
Pressure Head variation at node 19
2
3
34
3
2
1
Zoom window to pump station
and first surge protection element
35
1
2
36
1
3
4
2
Pressure head variation at nodes 6, 14, and 19
37
Labels on network map
1
Display heads and flows at time 0s
Head
Flowrate
2
Control the parameters to be displayed and simulation times
38
1
Right click on this to access detailed labels menu
39
Tabulated text and spreadsheets
1
40
41
Swap steady state and surge analysis results
42
2
1
Click on this button, draw a box around the entire pipeline
Export profile plot as CAD file
Right click on Show Profile button to access DXF profile tool
2
Enter data as shown and click on “Generate DXF File” button
44
Profile plot as DXF file
DXF file is located in .kyp subfolder
45
2.3 T3.P2K: Single Pump Trip under Multiple Pump Operation
One of three pumps get tripped while the other two continue to run. We will modify T2.p2k to simulate this scenario.
•
•
•
Open T2.p2k and save it as T3.p2k
Zoom to pump station area.
Update change data for the pumps that continue to run.
1
2
4
3
Click on OK button after step 3
5
Click on OK button after step 5
46
7
6
In T2.p2k, change data was setup for all three pumps
to simulate the trip condition for each pump.
9
Repeat this for the second pump
8
These changes will be ignored for transient analysis
when “Ignore Changes” box is checked (step 9), there
by allowing these pumps to maintain their initial
steady state condition throughout the transient
simulation. Alternatively, change data may be deleted
for the pumps that continue to run.
Now only one of the three pumps will trip in the
analysis.
Sample Results
47
2.4 T4.P2K: Single Pump Operation and Trip
Single pump operation for steady state (only one of the three pumps operates) and it gets tripped. T3.p2k will be modified to simulate this
scenario.
•
Open T3.p2k and save it as T4.p2k (step by step instructions for this are provided with T3.p2k)
•
Zoom to pump station area.
•
Change initial status of two of the three pumps to OFF status
•
Make sure the change data for these pumps is appropriate for the intended scenario.
1
Repeat steps 2 and 3 for second pump
Sample Results
3
2
48
Report: View summary of maximum and minimum pressures over the entire pipeline
4
5
49
2.5 T5.P2K Emergency Shutdown
Valve at delivery end of pipeline closes rapidly followed by shut down of pump to prevent over pressure at pump station. Use T2.p2k and make
necessary changes to simulate this scenario.
•
Open T2.p2k and save it as T5.p2k (step by step instructions for this are provided with T3.p2k)
•
Create an active valve at the delivery end of pipeline and provide appropriate valve type, resistance and initial ratio data
•
Setup change data for active valve to simulate rapid closing scenario
•
Update pump changes data to drop pump speed ratio from steady state condition to 0
3
1
2
6
4
5
7
50
Set up node change data for active valve as shown below.
Initial ratio of the valve of 1.0 is maintained for the first two
seconds. Valve closes rapidly in 10 seconds (ratio = 1.0 at
time 2 seconds to ratio = 0.0 at time 12 seconds).
8
Update change data for ALL pumps. Left click on
each pump and then access the change data by
clicking on the icon
under Node Info window.
Lets assume that pump shutdown is initiated 5
seconds after the start of valve closure event and
pump speed is ramped down linearly in 3 seconds.
Shutdown of each pump is staggered by 5 seconds.
10
9
Click on All Changes button and review
the complete set of changes for accuracy.
11
Sample Results
51
Plot pressure head variation at all junction nodes on the pipeline
Click and hold Ctrl button (this activates group mode)
and click on junction nodes, one at a time, to
12
highlight all junction nodes
13
52
To compare results with rapid valve closing event without the shutdown of pumps, check “Ignore Changes” box for all three pumps and reanalyze the model.
14
15
16
Repeat steps 12 and 13 for the other two pumps
and re-analyze the model. Left click on node 1
(common header node between pumps and surge
tank), then click on node results graph icon to
display results at this node. Select head and click
on display previous set of results icon to compare
new set of results (without pump shutdown) with
previous set of results (with pump shutdown).
17
18
Sample Results
53
2.6 T6.P2K: Normal Pump Shutdown
This example demonstrates setting of change data for a normal pump shut down event where pump speeds are ramped down linearly in
succession and in a set number of seconds. Use T2.p2k and make necessary changes to simulate this scenario.
Update change data for ALL pumps. Left on click
on each pump and then access the change data
by clicking on the icon
under Node Info
window. Lets assume that pump speed is
ramped down in 5 seconds and that shutdown of
each pump is staggered by 30 seconds.
1
2
Node 1
Results at Node 1
54
Review variable input data in report file
3
4
5
55
2.7 T7.P2K: Pump Switchover Operation
Pump-3 was assumed to be OFF initially and needs to be started after shutting down Pump-2. Pump-1 continues to operate during the entire
simulation. Use T2.p2k and make necessary changes to simulate this scenario.
•
Set Pump-3 to OFF status
•
Pump-1 continues to operate so the change data associated with this pump should either be deleted or set to ignore status
•
Setup necessary change data for Pump-2 and Pump-3 . Speed of Pump-2 ramps down in 5 seconds. Speed of Pump-3starts ramping up
5 seconds after shutdown of Pump-2 and ramps up in 5 seconds.
4
1
2
3
56
6
Press and hold Ctrl key and click on pump discharge
pipes – selects multiple pipelines for group processing
5
7
Pipe 12 is discharge line of Pump-2, and
pipe 13 is discharge line of Pump-3
57
2.8 T8.P2K: Full pump trip followed by pump startup
A power failure event followed by a sequential start up of all pumps was simulated in this example. Use T2.p2k and make necessary changes to
simulate this scenario.
•
Model T2.p2k simulates a full pump trip event.
•
Change data for each pump should be modified to simulate the subsequent startup conditions.
•
Pumps were assumed to restart after 100s from the beginning of simulation.
•
Pump speed was assumed to ramp up non-linearly in 5 seconds (reaches 75% of rated speed in first 3 seconds and full speed in next 2
seconds) with a 30 second delay for each pump.
1
Pump needs to be restarted at 100s. For this, the pump speed should be
brought to rest first as the pump could be spinning either in positive or
negative direction at 100s following the pump trip event. A speed ratio data
is specified a few seconds ahead of the intended restart time (100s in this
case) which will gradually bring the speed to 0 from whatever the speed is
at that time.
2
3 Provide appropriate change data for Pump-3
Generate pump speed plots
6
Click on this button
and a draw a box
around all three pumps
5
7
4
Speed brought to zero from 90s to 100s
59
2.9 T9.P2K: Normal pump startup
All pumps are OFF initially and pipeline is filled with water. Check valves at pump discharge remain closed and keep the pipelines from draining.
Pumps are started in sequence. Use T2.p2k and make necessary changes to simulate this scenario.
•
Pump startup condition requires the pumps to be in OFF (and initial pump speed ratio set to 0) mode during steady state conditions.
•
Change data for each pump should be modified to simulate the startup conditions.
•
Pump speed was assumed to ramp up linearly in 5 seconds with a 30 second delay for each pump.
2
Change pump status to OFF
1
Note: There must be a check valve on each pump
to simulate a pump startup condition. If not, there
must be a pump control valve or equivalent to keep
the pipeline filled with water (closed conduit flow)
and prevent flow reversal until sufficient energy is
generated by the pump during the startup condition.
3
Modify change data for all pumps
Sample Results
Sample Results
61
2.10 T10.P2K: Pump startup with pump control valve and NO check valve
The scenario is that all pumps are off, begin to activate, then control valves open. Pipeline is initially filled with water and the closed control
valves prevent draining. In model, simulation begins when pumps are running at low speed initially (but not yet flowing). Control valves open so
that pumps are operated in sequence. Use T2.p2k and make necessary changes to simulate this scenario.
•
Add pump control valves (active valves) on pump discharge lines and provide suitable resistance data. Set all pump control valves to
OFF status with an initial ratio of 0. Remove check valves on all pumps.
•
Assume that pump control valves remain closed until the pump speed is ramped up to certain initial speed. Set the initial speed ratio
for all pumps to ratio at which the pump control valves start opening. For this case, lets assume that the pump control valves start
opening when the pump speed reaches 90% of rated speed. Also, the pump speed gets ramped from 90% to 100% in 3 seconds.
•
Pump control valves open in 10 seconds. 30s lag time for each valve.
1
Insert an active valve at pump discharge.
Refer to pages 88 and 89 of TranSurge
users manual for help
2
3
Left click on pipe at
this location
7
Repeat steps 2 through 7 for all three
pump discharge lines
4
5
6
Set initial Speed Ratio for ALL pumps to 0.90 (speed at
which pump control valves start opening). Remove
check valves on ALL pumps.
Setup change data for active valves and pumps
Click on any pump and
access node change
data menu and clear all
change data
9
10
11
8
63
Do NOT attempt to simulate pump startup with both
pumps and active valves closed for steady state as this
leads to disconnected regions between pumps and
active valves – no way to compute pressures in those
portions of pipeline.
If the pumps ramp up to full speed before opening of
pump control valves, set initial speed ratio for pumps to
1.0 and delete (or set to ignore) change data for all
pumps.
If there is a check valve at pump discharge followed by
a pump control valve, then the check valve should be
included with the pump element or it can be placed on
the active valve element and no other changes would
be necessary to the pump or active valve change data.
Sample Results
64
64
Screen plot during transient analysis
Pay attention to computational time, smaller
computational time  more accurate results.
However, results accuracy will not change for
computational times below certain threshold
value for a give pipeline system.
65
2.11 T11.P2K: Surge Protection with Closed Surge Tank
Use T2.P2K which was setup to protect the pipeline using one bladder vessel and an air valve and switch the bladder vessel with a compressor
based closed surge tank.
T2.P2K
T11.P2K
Surge protection:
•
Bladder vessel at pump discharge
•
3m diameter
•
45m3
•
Precharge head of 30m
•
Connection resistance = 20
•
Air valve at highest elevation point
•
100mm 3-stage air valve
•
25mm smaller outflow orifice
•
2kPa switch pressure
Surge protection:
•
Compressor vessel at pump discharge
•
3m diameter
•
45m3
•
Initial gas volume of 20m3
•
Connection resistance = 20
•
Air valve at highest elevation point
•
100mm 3-stage air valve
•
25mm smaller outflow orifice
•
2kPa switch pressure
1
Zoom to pump station and
first surge protection device
3
Click on closed surge tank button to change
selected node to closed surge tank element.
Provide surge tank data – step 4
Left click on bladder tank
2
4
5
6
Sample Results
67
2.12 T12.P2K: Surge Protection with Hydraulically Actuated Surge Anticipation Valve
Use T1.P2K and make necessary changes to the model in TranSurge . Full pump trip condition for this model drops the pressures at pump
discharge to significantly below atmospheric levels. Use of surge anticipation valves can make the negative pressure conditions worse and the
reliable operation of surge anticipation valves become questionable. T1.P2K is modified for single pump operation (instead of three pump
operation) by deleting two of the three pumps and the new model is saved as T12.P2K.
Delete pump and connecting pipe
Surge protection:
3
•
Hyd Act Surge anticipation valve
•
150mm SAV (Kv=390, R=870)
1
•
Low pressure pilot = 6bar
•
High pressure pilot = 10bar
2
•
Valve opens in 3s and closes in 15s
Select one of the three pumps
•
Air valve at highest elevation point
•
100mm 3-stage air valve
Repeat steps 2 and 3 to delete Pump-2 and save file as T12.P2K
•
25mm smaller outflow orifice
•
2kPa switch pressure
5
4
Use resistance tool to
convert Kv value into
resistance
Sample results
SAV continues to flow even after
200s, protection may NOT be
acceptable
69
2.13 T13.P2K: Surge Protection with Electrically Actuated Surge Anticipation Valve
Use T12.P2K and make necessary changes.
Surge protection:
•
Ele Act Surge anticipation valve
•
150mm SAV (Kv=390, R=870)
•
High pressure pilot = 95m
•
Valve opens in 3s and closes in 15s
•
Full cycle time = 20s
•
Air valve at highest elevation point
•
100mm 3-stage air valve
•
25mm smaller outflow orifice
•
2kPa switch pressure
Make sure to select Use Head
option for this model. If the
node type is EleSAV (Prs) after
step 2, check Use Head box to
toggle to EleSAV (Hd) node
type.
2
3
1
Alternative method for changing device to EleSAV.
2
1
70
Sample results
Flow through SAV stops after about 40s.
71
2.14 T14.P2K: Surge protection using quick opening pressure relief valve (PRV)
Use T12.P2K and make necessary changes.
Surge protection:
•
Pressure relief valve
•
200mm PRV (Kv=810, R=200)
•
Opening head = 105m
•
Closing head = 90
•
Valve opens in 0.1s and closes in 15s
•
PRV discharges into a tank with a liquid depth of 5m
•
Air valve at highest elevation point
•
100mm 3-stage air valve
•
25mm smaller outflow orifice
•
2kPa switch pressure
Sample Results
PRV
Compare results with and without PRV
Turn PRV to Off status and re-analyze the model
2
1
4
3
73
2.15 T15.P2K: Non-linear valve closure (Valve stroking)
All pumps are running initially and valve at delivery end is fully open. Use T5.p2k and ignore or delete all changes so the pumps are running
continuously. Save as T15.p2k.
• Add Active Valve at delivery point and provide suitable resistance data (Resistance Tool). Initially valve is fully open (Initial Ratio=1), then
closes over 30 seconds (Changes). This is a linear closure. The Active Valve discharges to the atmosphere (Grade = Elevation = 610 m).
• Assume pumps are running continuously throughout. Remove or ignore pumps changes from T-5.p2k.
• Run a Surge analysis and view the pressure results with linear closure (no stroking) for the inlet side of the Active Valve.
• Use Valve Stroking Tool to find valve closure operation which is more controlled (non-linear closure).
2
1
3
Ignore Changes for all three pumps.
5
4
7
6
3
1
Run Surge Analysis. Results of 30 second linear closure
Right click Resistance
tool icon to bring up all
Tools
Use Steady State results in Valve Stroking Tool:
Velocity and Valve Head (inlet side of valve)
2
View Steady State Results
4
Use these values in Change table,
next page.
75
12.93 s + 2 s = 14.93 s
Run Surge Analysis again with Non-Linear Valve Closure
Pressure Results with Non-Linear Valve Closure
Comparing Linear and Non-Linear Valve Closure
76
2.16 T16.P2K: Valve opening
All pumps are running initially and valve at delivery location is fully open. Use T15.p2k and save as T16.p2k.
• Active Valve needs to be initially closed AND Initial Ratio = 0.
• Create Change data for valve opening over 10 seconds.
3
Changes for valve opening.
1
Flowrate for valve opening.
2
Pressure at junction node for valve opening.
2.17 T17.P2K: Demand Changes, Hydrant Flow Simulation
All pumps are running. Fixed flowrate (Demand) is applied at delivery end. This fixed flow can represent a hydrant, fueling station or any other
discharge at a fixed flowrate. The demand/flowrate can rapidly go up (e.g. hydrant opening) or go down (e.g. hydrant closing). In this simulation
a hydrant is closing over 10 seconds. Use T16.p2k and save as T17.p2k.
• Change Active Valve to a junction.
• Junction Demand is 3000 cmh, this is a fixed flow out of the pipeline at the delivery end.
• Create Change data for change in demand over 10 seconds.
3
1
2
Change in demand – hydrant closing.
Pressure at junction node for hydrant
closing (demand change).
2.18 T18.P2K: Grade Changes
All pumps are running, valve is open, but the liquid level in the vessel at the delivery point rapidly changes, such as a tank failure or rapid filling.
Use T2.p2k and save as T18.p2k.
• Zoom into pump station.
• Add three 600 mm pipes on the inlet side of the pump going to a single junction node.
• Connect the junction node to an Active Valve using a 900 mm pipe.
• Add Elevation data for both new nodes.
• Input additional data for Active Valve as shown. Note the Grade value. This is for the inlet side of the Active Valve.
• Create Change data for Active Valve “Reservoir Setting” (Grade) dropping 10 m in 4 seconds , then raising 20 m in 4 more seconds.
• Ignore Change data for all pumps.
Elevations and Pipe Data
With grade changes, the Active Valve connected to changing
grade must have almost no resistance. Tip: if a valve is to be
used for flow control, use two valves in series, one at the end
for the grade changes and one for flow control
Results at a downstream
junction node
Final grade level
Changes for grade of the supply connected to
inlet side of Active Valve.
Initial grade level
2.19 T19.P2K: Periodic Input (Grade Change Example)
All pumps are running continuously. It is assumed that the water level in a vessel to which the delivery valve (AV-1) is discharging will rise and
fall a total of 8 m each second, the middle level for this fluctuation is 5m above the baseline Grade value. Use T15.p2k. Save as T19.p2k.
•
•
•
•
Delete all changes for the Active Valve. Save and Exit the Change table.
Switch to Surge view.
Click Periodic Input icon.
Input as shown
• Node = AV-1
• Type = 1 this means the
grade, not the valve ratio
is being periodically
varied
• Period = 1 second
• Phase shift – does not
apply
• Amplitude = 4 m height of
the change above average
• Average = 5 m average
grade value.
• Switch back to TranSurge and
run analysis.
1
2
3
4
4 m (amplitude)
5 m above grade
(average)
Grade (HGL) Results
for Active Valve
4m
2.20 T20.P2K: Turbine Load Rejection
Turbine is tripped 2 seconds into the simulation. This example is T20.p2k
• Click on Turbine element and view the Input Data.
• Click on Turbine changes and note that the turbine is
tripped at 2 seconds.
• Run analysis.
Speed Ratio = -1 is a required
parameter for all turbines
File# (1-20) = 9 is required file type
for all turbines.
Input Rated Head, Flow, Speed, and
Inertia (manufacturer data)
Pressure Results for Turbine
2.21 T21.P2K: Turbine Partial Load Rejection
Turbine is closed by 80% in 2 seconds. Use example T20.p2k and save as T21.p2k
• Click on Turbine element.
• In the Changes table, replace the Trip with a ratio change
of 0.2 at time = 4 seconds.
• Run analysis.
Pressure Results for Turbine
2.22 T22.P2K: Turbine Full Load Rejection with Wicket Gate Operation.
Turbine load is fully rejected starting at 2 seconds. Wicket gate throttles down over 70 seconds, starting 5 seconds after Turbine trips.
Use example T20.p2k and save as T22.p2k
• Click on Wicket Gate element and view the input data.
• In the Changes table, input a ratio = 1 change starting at
time = 7 seconds (5 seconds after Turbine trips) and ratio
= 0.03 change at time = 77 seconds (70 seconds later).
• Run analysis.
Resistance , R, is headloss/(flow)^2
when wicket gate is fully open
Initial ratio = 1 means wicket gate is
fully open.
Pressure Results for Wicket Gate
2.23 T23.P2K Surge Protection with Open Surge Tank.
Replace Air Valve with an Open Surge Tank. Close the Bladder Tank by the Pump Station. Use example T5.p2k and save as T23.p2k
•
Run Analysis and view Profile
•
Open Surge Tank are good in many applications but for this model alone it
does not provide protection from cavitation.
Input Data for large Open Surge Tank
2.24 T24.P2K: Surge Protection with One-Way Open Surge Tank.
Use T23.p2k. Save as T24.p2k. Add a One-Way Open Surge Tank in the line as shown.
• Run analysis and view the profile.
Data for One-Way Open Surge Tank
Note the Outfow Resistance value
Added area of surge protection
from one-way open tank.
Chapter 3. Applications of TranSurge
This section describes the use of TranSurge for some specific applications such as cooling water systems, oil pipelines, groundwater collection
network, pumping to multiple tanks.
86
3.1 Cooling water system:
Cooling water systems involve pumping of water through turbine areas and discharge water to cooling water towers. These systems generally
involve low head and high flow pumps and pump stations without check valves. In most cases, cooling water systems are protected by just nonslam air valves.
CW-1.p2k was created based on a real-life cooling water system. Condensers in turbine areas were modeled as loss elements. Water is
discharged to 2 clusters of cooling towers. Pump trip condition was simulated and extreme low pressures were controlled by non-slam air valves.
Pump control valves were set to close non-linearly in 15s, closely matching flow reversal through pumps. Though the over length of pipeline is
relatively short, surge simulations were performed for 500s to air slam conditions , if any, associated with air outflow cycle.
87
Sample results
Pressure head and air volume
at air valve near pump station
88
3.2 Crude oil pipeline:
Surge analysis and design of surge protection systems for pipelines carrying other liquids is not significantly different from modeling those
carrying water. The primary constraint is on the steady state modeling itself – Hazen William equation for modeling friction is not valid for liquids
other than water! The other constraints might be on the type of surge protection devices. For example, air valves may not be suitable for
protecting long cross country oil pipelines. This example (Oil-1.p2k) illustrates a surge model for a 30+ mile 20 inch diameter steel pipeline lifting
3000 barrels per hour of crude oil by nearly 350 feet. A 1500ft 3 bladder vessel was used for protection that limits the surge pressures slightly
over the steady state values.
89
Sample results
90
3.3 Long pipelines with inline boosters:
This example illustrates surge analysis for a long pipeline with two inline boosters . The model was created based on a real-life raw water
irrigation pipeline system with a few minor modifications to protect its identity. Though there are four pump stations, one at intake and three
along the pipeline, the entire pipeline system was modeled in a single p2k file (boosters-1.p2k). Total length of pipeline is roughly 12.5km
comprising mostly 2400mm and 2800mm mild steel pipe with a total static lift of roughly 250m. Compressor surge vessels and non-slam air
valves are used for protecting the pipeline. Sample results from full pump trip simulation are presented in the following.
91
Sample results
92
Sample results
93
3.4 Pumping water to multiple elevated storage tanks:
It is a common practice in certain countries to pump potable water to several elevated storage tanks through a trunk main network for further
distribution by gravity from the outlet side of the elevated storage tanks. This example illustrates surge analysis for one such system. The model
was created based on a real-life potable water supply system serving approximately 60,000 people. Schematic of the network model (mt-1.p2k)
is shown in the following. Flow control valves are used to limit the flows to designated values to various elevated storage tanks. The model
simulates a pump shutdown event and no attempts were made to provide surge protection as surge pressures were not significant.
94
Sample results
95
3.5 Groundwater and surface water collection system:
The purpose of this example is to illustrate the modeling of a groundwater well (deep wells or bore wells) collection system and the associated
transient events. The system comprises three deep wells sources and one surface water source pumping into one common trunk main. The
pipeline system (ms-1.p2k) was protected using 2 stage air valves with large inflow orifice and smaller outflow orifice. Sample results from full
pump trip event (power outage at all stations) are shown in the following.
96
Sample results
97
Appendix A. Limitations of TranSurge demo version
The demo version of TranSurge allows for exploring all features of TranSurge except that it limits the size of Transmission mains. The following is
the list of general restrictions for TranSurge working in demo mode.
•
•
•
•
•
Number of pipe elements should be less than 10
o Pipe element is defined as the entire pipeline between two junction or other hydraulic elements such as reservoirs, pumps, active
valves, surge protection devices, etc.
Total length of pipeline (in the entire network) should be less than 10000m.
Allowable diameters are 50mm, 600mm, and 900mm.
Number of pumps is limited to 1
Number of surge elements is limited to 1
Surge protection device
Demo-1.p2k
Total number of pipe elements = 10
Pipe elements
Pump
Demo-2.p2k
Total number of pipe elements = 9
98
Pipe diameters displayed on the map
Demo-3.p2k
Total number of pipe elements = 10
Pipe diameters displayed on the map
Demo-4.p2k
Total number of pipe elements = 10
99
710 Tom's Creek Rd, Cary, NC 27519, USA
Phone: (859) 263-2234 FAX: (469) 250-1362