Professional Documents
Culture Documents
AspenFlareSysAnalV7 3-Start PDF
AspenFlareSysAnalV7 3-Start PDF
Although AspenTech has tested the software and reviewed the documentation, the sole
warranty for the software may be found in the applicable license agreement between
AspenTech and the user. ASPENTECH MAKES NO WARRANTY OR REPRESENTATION, EITHER
EXPRESSED OR IMPLIED, WITH RESPECT TO THIS DOCUMENTATION, ITS QUALITY,
PERFORMANCE, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
Contents i
1 Introduction
Audience
This guide is intended for process and process systems engineers.
Related Documentation
Title Content
Aspen Flare System Analyzer Reference Manual for Using Aspen
Reference Manual Flare System Analyzer
Technical Support
AspenTech customers with a valid license and software maintenance
agreement can register to access the online AspenTech Support Center at:
http://support.aspentech.com
This Web support site allows you to:
Access current product documentation
1 Introduction 1
Search for tech tips, solutions and frequently asked questions (FAQs)
Search for and download application examples
Search for and download service packs and product updates
Submit and track technical issues
Send suggestions
Report product defects
Review lists of known deficiencies and defects
Registered users can also subscribe to our Technical Support e-Bulletins.
These e-Bulletins are used to alert users to important technical support
information such as:
Technical advisories
Product updates and releases
Customer support is also available by phone, fax, and email. The most up-to-
date contact information is available at the AspenTech Support Center at
http://support.aspentech.com.
2 1 Introduction
2 Building and Running a
Model
Overview
This Getting Started tutorial shows the fundamental principles involved in
using Aspen Flare System Analyzer to design and rate a new flare system.
This guided tour will expose you to most of the major features of Aspen Flare
System Analyzer.
This tutorial assumes that you are familiar with the use of Microsoft Windows
and have some prior experience in the design of flare systems.
This example consists of the following main parts:
1 Building The Pipe Network - Pipes and nodes will be added using either
the Process Flowsheet or Pipe Manager.
2 Defining the Scenarios - Different scenarios will be set up to simulate
various process conditions.
3 Defining The Sources - Relieving sources will be added to each scenario.
4 Sizing the Network - Finally, the pipe network will be simulated and
results will be viewed both in textual and graphical form.
The following diagram shows the connectivity of the system that you will be
designing in this example.
Fig 2.1
The flare tip is not a pipe segment, but rather a node that represents a zero
length piece of pipe with defined fittings loss coefficients. Since the internal
diameter is not specified, it will assume the same diameter as the upstream
pipe segment. Fittings loss coefficients for the flare tip exclude pipe
enlargement and junction losses for the connection to the upstream pipe
which will automatically be calculated.
In this example, you will consider three scenarios that represent one fire case
and two single blocked discharge cases. The following tables define the source
data for each scenario.
2 The current unit set is shown in the Units box.. The default unit set is
Metric,, which will be used for this exam
example.
3 Confirm that the Edit Objects on Add check box is selected.
selected This option
will open the object editor view each time a new object is added.
4 Click OK to close the Preferences Editor.
Starting
arting a New Model
To start a new case, do one of the following:
1 Click New on the Quick Access Toolbar beside the aspenONE Button; or,
click the aspenONE Button, then click New from the Application Menu.
The Documentation Editor is displayed.
2 Enter the appropriate data into the User Name, Job Code,
Code Project, and
Description fields, and then click OK.
The Component Manager is displayed.
Note: Initially, all the check boxes in the Component types group are
selected.. You can clear them by clicking Invert.
Note: Notice that now all the required components are shown in the
Selected components
omponents list, indicating that they
ey have been installed in the
case.
The Component Manager will now appear as follows:
Fig 2.5
10 2 Building
uilding and Running a Model
Note: You can use the horizontal scroll bar at the bottom of the sheet to view
all of the component properties.
Note: You do not need to include the .fnwx extension; Aspen Flare System
Analyzer will add it automatically.
Click Save to close the dialog box and save the file.
Note: Before proceeding any further, make sure that the Edit Objects on
Add check box on the General tab of the Preferences Editor is selected.
At this point the flowsheet should be blank, since we have not added a single
object yet.
The desired objects can be added by using either of the following methods:
Clicking the Palette on the Process Flowsheet tab will open the
Palette,, which displays all the objects available in Aspen Flare System
Analyzer.. You can add an object by dragging it onto the Process
Flowsheet.
Fig 2.7
Fig 2.8
By default the Flare Tip has been named as FlareTip1,, which can be changed
to a more appropriate name as follows:
4 Click in the Name field on the Connections tab of the Flare Tip Editor.
Editor
5 Delete the default name an
and type Flare Tip as the new name.
Since this example is of smaller size, the Location field will be left blank.
This field is only useful for larger cases with multiple sections (areas)
within a same plant. Now you need to specify the pipe, which will be
simulated
imulated as a flare stack
stack, and it is attached to the Flare Tip.
Tip
6 Select Stack from the list in the Upstream node field.
7 In the At field
field, select Downstream as the pipe end connected to the
Flare Tip.
Note: The Fitting Loss Coefficient Basis should be set to Total Pressure
to indicate that the loss coeff
coefficient
icient we are defining will calculate the pressure
loss in the Flare T
Tip including the velocity pressure loss.
8 On the Calculations tab, enter 876.3 as the diameter and 3 as the fitting
loss in the appropriate fields.
Fig 2.9
Now you have provided all the necessary information about the Flare Tip.
9 Click OK to close the view.
Notice that now two new objects have been added to the Process
P
Flowsheet.. These may be drawn one on top of the other so you should
manually arrange them by clicking and dragging the object icons.
10 Open the Stack Object Editor by double-clicking
clicking the pipe icon on the
flowsheet and move to the Dimensions tab.
11 Specify the Length as 100 m and the Elevation Change as 100 m.
This will result in a vertical pipe measuring 100 m tall.
12 Select the Nominal Diameter as 36 inch and the Pipe Schedule as 40.
13 On the Methods tab, confirm that Vertical Pipe and VLE Method are set
as Model Default
Default.
In this example, every pipe segment uses the default models which are
specified on the Methods tab of the Calculation Options Editor.
Editor
14 Click OK to close the Stack Object Editor.
Now you need to add another pipe segment which will be added using the
Pipe Manager
Manager.
2 Click Add.
A new pipe will be added to the list. Click Edit.
The Pipe Editor will be displayed.
3 Change the na
name to Header 3.
4 Move to the Dimensions tab and enter the following data in the
appropriate fields:
Field Value
Length (m) 50
Nominal Diameter (inch) 36
Pipe Schedule 40
5 Click OK to clo
close the Pipe Editor.
6 Close the Pipe Manager by clicking Close.
You need to attach Header 3 with Stack using a node. Aspen Flare
System Analyzer allows you to choose between a variety of nodes, since
you need a simple connec
connection between the two pipes, a Connector node
will be used.
7 On the Palette
Palette, click the Connector icon and drag it to the Process
Flowsheet.
This will open the Connector Editor.
18 2 Building
uilding and Running a Model
Fig 2.14
Notice that by default the Angle has a value of 90 deg and the Fitting
loss method
ethod is set as Calculated.. These and the other entries may be
left at their default values for this example.
12 Click OK to close the Connector Editor.
Now, a tee will be added, using the Node Manager,, to combine the flow
from the two sources.
13 Click Nodes in the Build group on the Home tab of the Ribbon.
Ribbon The
Node Manager will be displayed.
14 Click Add and Select Tee from the list. A new Tee will be added.
Click Edit.
The Tee Editor will be displayed.
21 Click Add to add a new pipe segment. Click Edit to open the Pipe Editor.
22 Change the default pipe name to Tail Pipe 1.
23 Specify Tee 1 as the Downstream node connection and select Branch
in the At field
field.
Note: Setting the tailpipe option to Yes will cause the pressure drop to be
calculated using the rated flows rather than the actual flow. For this pipe
which is a tail pipe tto
o a control valve source, the rated flow and actual flow
will be the same so the setting of this option will have no effect.
Fig 2.20
Fig 2.21
26 2 Building
uilding and Running a Model
Fig 2.23
Now we should add the data for the Source 1 Only scenario.
4 Make sure that Default Scenario is highlighted in the Scenarios list on
the Scenario Manager
Manager. Click Clone. A new scenario will be added to the
list as shown below.
5 Click Edit to open the Scenario Editor for the new scenario.
scenario
6 Change the default name to Source 1 Only and verify the data for the
Source 1 Only scenario is the same as shown below.
7 Click OK to close the Scenario Editor for Source 1 Only.. Repeat Step 4
to
o add a new scenario.
8 Change the name for the new scenario to Source 2 Only.
9 Verify the data for the new scenario on the Constraints tab is the same
as shown below
below.
34 2 Building
uilding and Running a Model
Fig 2.31
5 Click Add and select Control Valve from the list that is displayed.
displayed
6 Change the name to Source 1. Select Tail Pipe 1 in the Outlet field and
set connection to be at Upstream (of Tail Pipe 1).
7 Move to the Conditions tab and set the Mass Flow as 100000 kg/hr. In
this example, the inlet pressure and temperature are the same as the
default values
values, but this will not normally be the case.
8 On the Composition tab, specify the Mol. Wt. to be 20.. Once you have
entered the M
Mol. Wt. and tabbed to the next field, you will notice the
composition will be calculated to give the required Mol. Wt.
Note: The Mole Fractions are automatically estimated from the Molecular
Weight. Because HC is selected from the list, only hydrocarbon
rocarbon components
will be used to match the Molecular Weight.
9 Click OK to close the Control Valve Editor for Source 1.. Click Add in
the Node Manager to add a new source. The node selection list will again
be displayed.
10 Select Relief Valve from the list, and then click Edit to open the Relief
Valve Editor
Editor.
11 Name the new source as Source 2 on the Connections tab.
12 Select Tail Pipe 2 in the Outlet field and set connection to be at
Upstream (of Tail Pipe 2).
13 On the Conditions tab, check that the relief valve set pressure or MAWP
is set to the default value of 10 bar which is correct
ect for this source. Select
the Auto check box next to the Relieving Pressure field. This tells Aspen
Flare System Analyzer to calculate the relieving pressure from the MAWP
and the selected Contingency, which should be left as Operating in this
case. Check k that the relieving pressure is calculated as 10.89 bar.
14 Still on the Conditions tab, check that the Allowable Backpressure is
set to 5.0 bar. Enter the required Mass Flow rate for this source of
100000 kg/ hr. Select tthe Auto check box next to the Rated flow field.
This tells Aspen Flare System Analyzer to calculate the rated flow for the
valve from the specified fluid conditions and properties, valve type and
orifice area.
Fig 2.38
42 2 Building
uilding and Running a Model
Fig 2.39
Fig 2.40
You must now add the source data for the other two scenarios.
20 Select the Source 1 Only scenario from the Scenario Selector list in the
Run group on the Home tab of the Ribbon. Any
ny open data views will now
display data for this scenario.
21 Make the following changes to the flowrates from the Sources data sheet
in the Source 1 Only scenario
cenario (all other information remains the same):
Source 1 - Mass F
Flow 100000 kg/hr, Mol. Wt. 20
Fig 2.42
Once the calculations are complete you can review the results.
4 Select Results | Messages from the Views tab on the Navigation Pane.
Pane
The Messages data vi
view will be displayed.
Fig 2.43
With the Pressure/Flow Summary sheet open, select each scenario in turn
using the Scenario Selector in the Run group.
Note: In the scenario Source 1 Only,, the mach number problem on Tail
Pipe 1 is automatically highlighted.
7 At this point, save the model using either the Save icon on the Quick
Access Toolbar
Toolbar, or click the aspenONE Button
on at the upper left corner of
the application window then select Save from the Application Menu.
M
Overview
In this chapter of the Getting Started tutorial you will change the network
designed in Chapter 2 to model the tie-in of two new control valves into our
current system. The modified system will be simulated for two new scenarios,
one each for the new sources.
This tutorial assumes that you are familiar with the use of Microsoft Windows
and have some prior experience in the design of flare systems.
Note: This tutorial is a continuation of the one in the previous chapter and
requires that you complete that chapter before continuing with this one.
This example consists of the following main parts:
1 Building The Pipe Network - Pipes and nodes will be added using either
the Process Flowsheet or the Manager views.
2 Defining the Scenarios - Different scenarios will be set up to simulate
various process conditions.
3 Defining The Sources - Relieving sources will be added to each scenario.
4 Sizing the Network - Finally, the pipe network will be simulated and
results will be viewed both in textual and graphical form.
Note: When you are sizing a flare system, the initial pipe diameters may
affect the solution when there is a liquid phase and the liquid knockout drum
is modelled. You should initially size a network using vapo
vapour
ur phase methods.
The following diagram shows the connectivity of the system which includes
the new sources you will be adding in this example.
Fig 3.1
The pipe segments in the network diagram are detailed in the following table.
Segment Length Nominal Schedule Fittings Elevation
Name (m) Diameter (inch) Loss Change (m)
Stack 100 36 40 0 100
Header 1 50 28 30 0 0
50 3 Developing
Developin the Model
Segment Length Nominal Schedule Fittings Elevation
Name (m) Diameter (inch) Loss Change (m)
Header 2 50 28 30 0 0
Header 3 50 36 40 0 0
Tail Pipe 1 25 18 40 0 0
Tail Pipe 2 25 18 40 0 0
Tail Pipe 3 25 12 40 0 0
Tail Pipe 4 25 18 40 0 0
The new pipe segments Header 1, Header 2, Tail Pipe 3 and Tail Pipe 4 will be
added.
In this example, you will consider five scenarios that represent one fire case
and four single blocked discharge cases. The following tables define the
source data for each scenario.
The discharge flange size values are left undefined. In this case, they are
assumed to have the same diameter as the attached pipes
Fig 3.2
4 Click the Look in field to select the appropriate disk drive and directory.
Fig 3.3
4 Click Add and select Tee from the list that is displayed. Click Edit.
The Tee Editor will be displayed:
Note: Since this example is of smaller size, therefore the Location field will
be left blank. This field is only useful for larger case with multiple sections
(areas) within a same plant.
6 Move to the Calculations tab and verify that the Fitting Loss Method
setting is Miller
Miller.
7 Close the Tee Editor by clicking OK.
8 Click Close to close the Node Manager.
Now, you cann add two pipe segments to the upstream and branch section
of Tee 3 using the Pipe Manager.
9 Open the Pipe Manager by clicking Pipes in the Build group.
group
Fig 3.12
2 Click Default Scenario in the Scenarios list to highlight it. Click Clone.
A new scenario is added to the list.
7 Verify that the values of the Mach Number on the Constraints tab in
both Headers and Tailpipes groups are 0.5.
8 Click OK to close the Scenario Editor and return to the Scenario
Manager. Now select Default Scenario and click Current to make this
the working scenario. Click Close to close the Scenario Manager.
Manager
2 Click Add and select Control Valve from the list displayed.
displayed
3 Change the default name to Source 3. Select Tail Pipe 3 in the Outlet
field and set connection to be at Upstream (of Tail
il Pipe 3).
3
4 Move to the Conditions tab and set the Mass Flow as 100000 kg/hr.
Note: The composition will be calculated as soon as you tab away from the
Mol. Wt. field.
Note: The Mole Fractions are automatically estimated from the Molecular
Weight. Because HC is selected, only hydrocarbon components will be used to
match the Molecular Weight.
6 Click OK to close the Control Valve Editor for Source 3.
7 Repeat Step 2 to add a new source. Again select Control Valve and the
Control Valve Editor will be displayed.
8 Name the new
ew source as Source 4.
9 Select Tail Pipe 4 in the Outlet field and set connection to be at
Upstream (of Tail Pipe 4).
Fig 3.25
14 You must now add the source data for the four scenarios.
15 Select the scenarios from the Scenario Selector in the Run group on the
Home tab.. Any open data views will display data for the selected
scenario.
Make the following changes to the flowrates iin all scenarios:
Scenarios Source 1 Source 2 Source 3 Source 4
(kg/hr) (kg/hr) (kg/hr) (kg/hr)
Source 1 Only 100000 0 0 0
For each scenario, ensure that the sources which have a flowrate of 0 are
ignored (i.e. select the Ignore check box for the source).
Note: You can also add the single source scenarios by selecting the Add
Single Source Scenarios tool from Source Tools in Tools group on the
Home tab.
2 For the first calculation of this example ensure that the following options
are set:
On the General tab, Calculation Mode should be set to Rating,
Rating Enable
Heat Transfer check box should be cleared, Include Kinetic Energy
check box should be cleared, Ignore Source to Pipe Pressure Loss in
Design Mode should be selected.
Fig 3.27
Once the calculations are complete you can review the results.
results
5 Select Results | Messages from the Views pane on the Navigation
Pane. The Messages sheet will be displayed.
Fig 3.28
Fig 3.29
3 Select Results | Messages from the Views pane, and then select the
Sizing tab to see a list of changes that Aspen Flare System Analyzer has
made to the network
network.
4 Select Results | Pressure/Flow Summary
Summary.
The Pressure/Flow Summary data sheet will be displayed.
displayed
Fig 3.30
Fig 3.31
The reason for this is that the lower back pressure in the system when
only a single source is relieving means that the gas density is reduced
resulting in higher velocities.
7 To fix this problem with our design we will re
re-run the Debottleneck
calculations for all the scenarios. Use the Calculation Mode selector on
the Ribbon to change the calculation mode to Debottleneck and then
click the Run icon.
8 When complete
completed, review the Problems tab of the Messages view to
confirm that the flare system now meets all our design limits in all
scenarios. The Sizing tab will
ill show which pipe sizes have been increased.
Note: We could have run the Debottleneck calculations for all scenarios
immediately after our first rating calculation and obtained the same results.
While this might have been faster, we have obtai
obtained
ned a better understanding
of which scenarios have caused changes to pipe sizes by doing our
calculations in stages.
9 Select Results | Pressure/Flow Summary from the Views
View pane on the
Navigation Pane
Pane.
The Pressure/Flow Summ
Summary will be displayed.
Fig 3.33