flarenet_ders_dokümanı

Copyright NoticeThe copyright in this manual and its associated computer program are the property of Hyprotech Ltd. All rights reserved. Both this manual and the computer program have been provided pursuant to a License Agreement containing restrictions on use.

Hyprotech reserves the right to make changes to this manual or its associated computer program without obligation to notify any person or organization. Companies, names and data used in examples herein are fictitious unless otherwise stated.

No part of this manual may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any other language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical manual or otherwise, or disclosed to third parties without the prior written consent of AEA Technology Engineering Software, Hyprotech Ltd., Suite 800, 707 - 8th Avenue SW, Calgary, Alberta, Canada.

© 1999 Hyprotech Ltd. All rights reserved.

Flarenet, HYSYS, HYSYS.Plant, HYSYS.Process and HYSIM are registered trademarks of Hyprotech Ltd.

Windows, Windows 95, Windows NT are registered trademarks of Microsoft Corporation.

Documentation CreditsAuthors of the current release, listed in order of historical start on project:

Adeel Jamil,B.Sc.; Nana Nguyen, B.Sc.; Yannick Sternon, B.Ing.

Since software is always a work in progress, any version, while representing a milestone, is nevertheless but a point in a continuum. Those individuals whose contributions created the foundation upon which this work is built have not been forgotten. The current authors would like to thank the previous contributors.

A special thanks is also extended by the authors to everyone who contributed through countless hours of proof-reading and testing.

Contacting HyprotechHyprotech can be conveniently accessed via the following:

Website: http:\\www.software.aeat.comTechnical Support: [email protected] and Sales: [email protected]

Detailed information on accessing Technical Support can be found in the Technical Support section in the preface to this manual.

Table of Contents

1 Introducing FLARENET.....................................1-11.1 Use of Manuals ................................................................. 1-6

1.2 Technical Support ........................................................... 1-10

Technical Support Centres ....................................................... 1-11

Offices ...................................................................................... 1-12

Agents ...................................................................................... 1-13

2 Installing FLARENET ........................................2-12.1 Basic Requirements .......................................................... 2-3

2.2 Installation ......................................................................... 2-3

2.3 Licensing ........................................................................... 2-5

2.4 Redundant License Servers ............................................ 2-13

2.5 Commuter Licensing ....................................................... 2-16

2.6 License Server Environment Variables ........................... 2-17

2.7 License Server Tools....................................................... 2-25

2.8 User Options ................................................................... 2-38

2.9 Potential Problems Running FLARENET........................ 2-39

2.10 Glossary of Terms........................................................... 2-43

3 Get Started .......................................................3-13.1 Data Requirements ........................................................... 3-3

3.2 Starting Flarenet................................................................ 3-6

3.3 Starting A New Model........................................................ 3-9

3.4 Saving The Model ........................................................... 3-13

3.5 Building The Pipe Network .............................................. 3-14

3.6 Defining The Scenarios ................................................... 3-24

3.7 Defining The Sources...................................................... 3-27

3.8 Rating The Network......................................................... 3-33

3.9 Printing Data And Results ............................................... 3-38

4 Upgrading the Network....................................4-14.1 Data Requirements ........................................................... 4-3

iii

4.2 Starting Flarenet................................................................ 4-7

4.3 Opening the Old Model ..................................................... 4-8

4.4 Updating the Model ........................................................... 4-9

4.5 Defining The Scenarios ................................................... 4-17

4.6 Defining The Sources...................................................... 4-19

4.7 Sizing The Network ......................................................... 4-25

4.8 Rigorous Rating............................................................... 4-30

4.9 Printing Data And Results ............................................... 4-32

5 Interface ...........................................................5-15.1 Terminology....................................................................... 5-3

5.2 Menu Bar........................................................................... 5-5

5.3 Tool Bar............................................................................. 5-6

5.4 Status Bar.......................................................................... 5-8

5.5 Editing Data Views ............................................................ 5-9

5.6 Setting Preferences......................................................... 5-12

5.7 Windows Menu................................................................ 5-16

5.8 Help Menu....................................................................... 5-16

6 Creating and Saving Cases ..............................6-16.1 Creating A New Case........................................................ 6-3

6.2 Opening An Existing Case ................................................ 6-4

6.3 Saving A Case................................................................... 6-5

7 Components......................................................7-17.1 Selecting Components ...................................................... 7-3

7.2 Adding/Editing Components.............................................. 7-5

7.3 Organizing the Component List......................................... 7-9

8 Scenarios..........................................................8-18.1 Adding/Editing Scenarios .................................................. 8-5

8.2 Scenario Tools .................................................................. 8-8

9 Scenarios..........................................................9-19.1 Adding/Editing a Pipe........................................................ 9-3

9.2 Methods Tab ..................................................................... 9-8

9.3 Ignoring/Restoring Pipes................................................. 9-11

9.4 Arranging Display Order.................................................. 9-12

9.5 Pipe Tools ....................................................................... 9-13

10 Nodes..............................................................10-1

iv

10.1 Node Manager................................................................. 10-3

10.2 Node Types..................................................................... 10-4

10.3 Sources ......................................................................... 10-18

10.4 Ignoring/Restoring Nodes.............................................. 10-32

11 Calculations....................................................11-111.1 Calculation Options ......................................................... 11-3

11.2 Starting The Calculations .............................................. 11-11

11.3 Efficient Modelling Techniquies..................................... 11-12

12 Databases.......................................................12-112.1 Database Features.......................................................... 12-3

12.2 Setting The Password ..................................................... 12-5

12.3 Pipe Schedule Database Editor ...................................... 12-6

12.4 Fittings Database Editor .................................................. 12-7

12.5 Component Database Editor ........................................... 12-8

13 Viewing Data and Results ..............................13-113.1 Components Data ........................................................... 13-3

13.2 Scenarios Data................................................................ 13-3

13.3 Pipes Data....................................................................... 13-4

13.4 Sources Data................................................................... 13-4

13.5 Nodes Data ..................................................................... 13-5

13.6 Messages........................................................................ 13-6

13.7 Pressure/Flow Summary ................................................. 13-8

13.8 Compositions................................................................... 13-9

13.9 Physical Properties.......................................................... 13-9

13.10 Profile ............................................................................ 13-11

13.11 Flow Map....................................................................... 13-12

13.12 Scenario Summary........................................................ 13-13

13.13 Graph Control................................................................ 13-14

14 PFD..................................................................14-114.1 Overview ......................................................................... 14-3

14.2 Object Inspection............................................................. 14-5

14.3 Installing Objects ............................................................. 14-8

14.4 Connecting Objects ......................................................... 14-9

14.5 Manipulating the PFD...................................................... 14-9

14.6 Printing and Saving the PFD Image.............................. 14-11

14.7 Changing the PFD View Options................................... 14-12

v

15 Exporting, Importing and Printing..................15-115.1 Printing ............................................................................ 15-4

15.2 Importing Source Data .................................................... 15-8

15.3 Exporting to Microsoft Access ....................................... 15-17

A Theoretical Basis .............................................A-1A.1 Pressure Drop ...................................................................A-3

A.2 Vapour-Liquid Equilibrium ...............................................A-15

A.3 Physical Properties..........................................................A-19

A.4 Noise ...............................................................................A-27

B File Format .......................................................B-1B.1 Access File ........................................................................B-3

B.2 .FMT Files Format ...........................................................B-16

C References .......................................................C-1

D Glossary of Terms ............................................D-1

Index..................................................................I-1

vi

Introducing FLARENET 1-1

1 Introducing FLARENET

1-1

1.1 Use of Manuals ............................................................................................. 6

1.1.1 How This Manual Is Organized ................................................................ 71.1.2 Conventions used in the Manuals ............................................................ 7

1.2 Technical Support ...................................................................................... 10

1-2

1-2


The design of flare and vent system piping is an important part of the overall system design for any chemical process. Traditional methods for the design of these flare and vent systems are often reliant upon the experience of the engineer. He or she must make a number of decisions in order to try to reduce the number of relief scenarios for evaluation based upon tight project deadlines. Failure to evaluate a single scenario due to "a lack of time" in the project design phase can have catastrophic penalties once the process is in operation.

FLARENET has been designed to facilitate the design and rating of flare and vent system piping throughout the entire design process. The program interface uses a flow diagram for direct visualisation of the piping network. This is supported by detailed tables of all pertinent data and calculated results.

FLARENET can model the piping system topologies most commonly found in flare systems.

• Convergent multiphase systems which comprise over 90% oftoday's installations in chemical process plants ranging fromoffshore production facilities to refineries and petrochemicalplants.

Figure 1.1

1-3

1-4

1-4

• Multiphase systems with two flare tips as commonly found onoffshore floating production facilities.

Figure 1.2


• Vapour phase ring mains.

Multiple relief scenarios such as "Plantwide Power Failure", "Plantwide Cooling Water Failure" and "Localised Fire" cases, as well as the individual relief valve loads can be maintained within a single file model of the flare system. The following calculations can be done simply from a consistent data set.

• Design of an entire new flare system for a single reliefscenario.

• Design of an entire new flare system for all relief scenarios.• Debottlenecking design of an entire/partial flare system for a

single relief scenario.• Debottlenecking design of an entire/partial flare system for all

relief scenarios.• Rating of an entire/partial flare system for a single relief

scenario.• Rating of an entire/partial flare system for all relief scenarios.

FLARENET has the option to calculate the pressure profiles using a range of single and two-phase pressure drop calculation methods.

Figure 1.3

1-5

1-6 Use of Manuals

1-6

These methods may be used globally throughout the model or specified at a local level. Robust multiphase thermodynamic models back up the physical property predictions used by the pressure drop models.

FLARENET automatically highlights calculated data that violates user defined design constraints for the flare system:

• Relief valve allowable back pressure• Fluid mach number• Fluid velocity• Fluid temperature• Pipe noise

These violations are automatically colour highlighted on the tabular results display. A graphical display of the pressure profile between any relief source and the flare or vent tip is available to facilitate the rapid determination of sections of the pipe network, which cause pressure-related bottlenecks.

Extensive databases are provided for pipe schedule data, pipe fittings loss coefficients and pure component properties. These databases may be supplemented with user supplied data.

Experienced process design engineers with basic computer knowledge can be expected to quickly acquire the skills necessary to make efficient use of the program. It is recommended, however, that you read this manual in order to fully understand the principles involved in the construction and running of the computer models of the flare and vent systems.

1.1 Use of ManualsYour FLARENET documentation package consists of one main coil-bound User’s Guide. The first three chapters contain the information you need to install FLARENET, plus a Get Started example to get you up and running with the software. The remainder of the manual provides in-depth information on the FLARENET interface environments and architecutre.

All FLARENET documentation is also available electronically on the CD-ROM, which is included with your FLARENET package.

Since FLARENET is totally interactive, it provides virtually unlimited


flexibility in solving any simulation problem. Please keep in mind that the approach used in solving each example problem presented in the FLARENET documentation may only be one of the many possible methods. You should feel free to explore other alternatives.

1.1.1 How This Manual Is OrganizedThis FLARENET User’s Guide is a comprehensive guide that gives details of all the procedures you need to work with the program. To help you learn how to use FLARENET efficiently, this manual describes all areas of the program in a logical sequence.

For the more advanced user, the appendices contain a summary of the database contents as well as details of the mathematical models used within FLARENET.

1.1.2 Conventions used in the Manuals

The following section lists a number of conventions used throughout the documentation.

Keywords for Mouse Actions

As you work through various procedures given in the manuals, you will be given instructions on performing specific functions or commands. Instead of repeating certain phrases for mouse instructions, keywords are used to imply a longer instructional phrase:

A number of text formatting conventions are also used throughout the manuals:

The primary mouse button is the one you use the most. For most users of a standard two-button mouse, the primary mouse button is on the left, and the secondary button on the right.

Keywords Action

Select, choose,press or click

Position the cursor on the object or button of interest,and press the primary mouse button once.

Double-clickPosition the cursor on the object of interest, andpress the primary mouse button twice, quickly insuccession.

Click and drag

Position the cursor on the object of interest, pressand hold the primary mouse button, move the cursorto a new location, and release the primary mousebutton.

Object inspect Position the cursor on the object of interest, andpress the secondary mouse button once.

1-7

1-8 Use of Manuals

1-8

Bullets and Numbering

Bulleted and numbered lists will be used extensively throughout the manuals. Numbered lists are used to break down a procedure into steps, for example:

1. Select the Segment Name cell.

2. Type a name for the pipe segment.

3. Press <Enter> to accept the name.

Bulleted lists are used to identify alternative steps within a procedure, or for simply listing like objects. A sample procedure that utilizes bullets is:

1. Move to the Splits tab by doing one of the following:

• Select the Splits tab• Press <Alt><S>

2. Type a value for the rate.

3. Press <Enter> to accept the value.

Notice the two alternatives for completing Step 1 are indented to indicate their sequence in the overall procedure.

A bulleted list of like objects might describe the various groups on a particular view. For example, the Add Pipe property view (which is opened by pressing the Add button on the Pipe Manager view) has a

Format Example

When you are asked to invoke a FLARENETmenu command, the command is identified bybold lettering.

File indicates the File menuitem.

When you are asked to select a FLARENETbutton, the button is identified by bold, italicizedlettering.

OK identifies the OK buttonon a particular view.

When you are asked to select a key or keys toperform a certain function, keyboardcommands are identified by bold lettering,enclosed by angle brackets.

<F1> identifies the F1 key.

The name of a FLARENET view (or window) isindicated by bold lettering

Component Manager view

The name of a group within a view is identifiedby bold lettering,

Component Types group

The name of radio buttons and check boxes areidentified by bold lettering,

Halogen check box

When you are asked to provide keyboard input,it will be indicated by bold lettering

"Type Pipe 25 for thesegment name."


group which contains four check boxes, namely:

• Resizeable• Separate Liquids• Tailpipe• Allow Autocalc

Callouts

A callout is a label and arrow that describes or identifies an object. An example callout describing a graphic is shown below.

Annotations

Text appearing in the outside margin of the page supplies you with additional or summary information about the adjacent graphic or paragraph. An example is shown to the left.

Shaded Text Boxes

A shaded text box provides you with important information regarding FLARENET’s behaviour, or general messages applying to the manual. Examples include:

The use of many of these conventions will become more apparent as you progress through the manuals.

Figure 1.4

FLARENET Icon

Annotation text appears in the outside page margin.

FLARENET allows you to select single objects as well as multiple objects, but inorder to select an object, you must be in Arrange mode.

Before proceeding, you should have read the introductory section which precedes the example problems in this manual.

1-9

1-10 Technical Support

1-10

1.2 Technical SupportThere are several ways in which you can contact Technical Support. If you cannot find the answer to your question in the manual, we encourage you to visit our Website at www.hyprotech.com, where a variety of information is available to you, including:

• Answers to Frequently Asked Questions• Example Cases and Product Information• Technical Papers• News Bulletins• Hotlink to Support E-mail

You can also access Support directly via E-mail. The following listing of Technical Support Centres includes the Support E-mail address. When contacting us via E-mail, please include in your message:

• Your full name, company, phone and fax numbers.• The version of FLARENET you are using (see Help, About...).• The serial number of your FLARENET security key.• A detailed description of the problem (attach a simulation case

if possible).

We also have toll free lines that you may use. When you call, please have the same information available.


Technical Support CentresCalgary, Canada

AEA Technology - Hyprotech Ltd.

Suite 800, 707 - 8th Avenue SW

Calgary, Alberta

T2P 3V3

[email protected] (e-mail)

(403) 520-6181 (local - technical support)

1-888-757-7836 (toll free - technical support)

(403) 520-6601 (fax - technical support)

1-800-661-8696 (information & sales)

Barcelona, Spain


Hyprotech Europe S.L.

Pg. de Gràcia 56, 4th floor

E-08007 Barcelona, Spain


+34 93 215 68 84 (technical support)

+34 93 215 42 56 (fax - technical support)

+34 93 215 68 84 (information & sales)

Oxford, UK

AEA Technology Engineering Software

Hyprotech

404 Harwell,

Oxford, OX11 0RA

United Kingdom


0800 731 7643 (toll free technical support, UK only)

+44 1235 434284 (fax - technical support)

+44 1235 435555 (technical support, information & sales)

Kuala Lumpur, Malaysia


Hyprotech Ltd., Malaysia

Lot E-3-3a, Dataran Palma

Jalan Selaman ½, Jalan Ampang

68000 Ampang, Selangor

Malaysia


+60 3 470 3880 (technical support)

+60 3 470 3811 (fax - technical support)

+60 3 470 3880 (information & sales)

Yokohama, Japan


AEA Hyprotech KK

Plus Taria Bldg. 6F.

3-1-4, Shin-Yokohama

Kohoku-ku

Yokohama, Japan

222-0033


81 45 476 5051 (technical support)

81 45 476 5051 (information & sales)

81 45 476 3055 (fax)

1-11


1-12

OfficesCalgary, Canada

Tel: (403) 520-6000

Fax: (403) 520-6040/60

Toll Free: 1-800-661-8696

Yokohama, Japan

Tel: 81 45 476 5051

Fax: 81 45 476 3055

Newark, DE, USA

Tel: (302) 369-0773

Fax: (302) 369-0877

Toll Free: 1-800-688-3430

Houston, TX, USA

Tel: (713) 339-9600

Fax: (713) 339-9601

Toll Free: 1-800-475-0011

Oxford, UK

Tel: +44 1235 435555

Fax: +44 1235 434294

Barcelona, Spain

Tel: +34 93 215 68 84

Fax: +34 93 215 42 56

Oudenaarde, Belgium

Tel: +32 55 310 299

Fax: +32 55 302 030

Düsseldorf, Germany

Tel: +49 211 577 933 0

Fax: +49 211 577933 11

Hovik, Norway

Tel: +47 67 10 6464

Fax: +47 67 10 6465

Cairo, Egypt

Tel: +20 2 7020824

Fax: +20 2 7020289

Kuala Lumpur, Malaysia

Tel: +60 3 470 3880

Fax: +60 3 470 3811

Seoul, Korea

Tel: 82 2 3453 3144 or 82 23453 3145

Fax: 82 2 3453 9772


Agents

InternetWebsite: www.hyprotech.com

Email: [email protected]

International Innotech, Inc.Katy, USA

Tel: (281) 492-2774Fax: (281) 492-8144

International Innotech, Inc. Beijing, China

Tel: 86 10 6499 3956 Fax: 86 10 6499 3957

International InnotechTaipei, Taiwan

Tel: 886 2 809 6704Fax: 886 2 809 3095

KBTECH Ltda. Bogota, Colombia

Tel: 57 1 258 44 50 Fax: 57 1 258 44 50

Kinetics Technology India Ltd.New Delhi, India

Tel: 91 11 621 1815 or 91 11 621 1760Fax: 91 11 644 6871 or 91 11 644 1984

Logichem Process Sandton, South Africa

Tel: 27 11 465 3800 Fax: 27 11 465 4548

Process Solutions Pty. Ltd. Peregian, Australia

Tel: 61 7 544 81 355Fax: 61 7 544 81 644

Protech Engineering Bratislava, Slovak Republic

Tel: +421 7 288286Fax: +421 7 288286

PT. Danan Wingus SaktiJakarta, Indonesia

Tel: 62 21 567 4573 75 or 62 21 567 4508 10Fax: 62 21 567 4507 or 62 21 568 3081

Ranchero Services (Thailand) Co. Ltd.Bangkok, Thailand

Tel: 66 2 381 1020Fax: 66 2 381 1209

S.C. Chempetrol Service srl Bucharest, Romania

Tel: +401 335 60 05 or 401 335 60 06Fax: +401 331 3463 or 401 322 30 69

Soteica De Mexico Mexico D.F., Mexico

Tel: 52 5 546 5440Fax: 52 5 535 6610

Soteica Do Brasil Sao Paulo, Brazil

Tel: 55 11 533 2381 Fax: 55 11 556 10746

Soteica S.R.L. Buenos Aires, Argentina

Tel: 54 11 4555 5703 Fax: 54 11 4551 0751

Soteiven C.A. Caracas, Venezuela

Tel: 58 2 264 1873Fax: 58 2 265 9509

Taradis CAD/CAM CenterTehran, Iran

Tel: 98 21 8754496 or 98 21 8758947Fax: 98 21 8753352

ZAO Techneftechim Moscow, Russia

Tel: +7 095 202 4370Fax: +7 095 202 4370

1-13


1-14

Installing FLARENET 2-1

2 Installing FLARENET

2.1 Basic Requirements..................................................................................... 3

2.2 Installation .................................................................................................... 3

2.3 Licensing....................................................................................................... 5

2.3.1 Overview .................................................................................................. 52.3.2 Installing the Hardware key...................................................................... 72.3.3 Standalone Licensing............................................................................... 82.3.4 Network Licensing.................................................................................... 9

2.4 Redundant License Servers ...................................................................... 13

2.4.1 Setting up Redundant License Servers.................................................. 14

2.5 Commuter Licensing.................................................................................. 16

2.6 License Server Environment Variables .................................................... 17

2.6.1 LSHost ................................................................................................... 172.6.2 LSERVOPTS.......................................................................................... 192.6.3 LSDEFAULTDIR..................................................................................... 222.6.4 LSERVRC .............................................................................................. 222.6.5 LSERVRCCNF....................................................................................... 232.6.6 LSPROTOCOL....................................................................................... 232.6.7 LSPORT................................................................................................. 24

2.7 License Server Tools ................................................................................. 25

2.7.1 WLMAdmin ............................................................................................ 252.7.2 lsmon ..................................................................................................... 282.7.3 Wrlftool ................................................................................................... 292.7.4 rlftool ...................................................................................................... 312.7.5 lspool...................................................................................................... 332.7.6 lsusage................................................................................................... 34

2-1

2-2

2-2

2.7.7 Wcommute............................................................................................. 352.7.8 lcommute ............................................................................................... 362.7.9 ipxecho................................................................................................... 372.7.10 lswhere................................................................................................. 372.7.11 lsdecode ............................................................................................... 38

2.8 User Options............................................................................................... 38

2.8.1 Setting Group Reservations................................................................... 38

2.9 Potential Problems Running FLARENET................................................. 39

2.10 Glossary of Terms .................................................................................... 43


2.1 Basic RequirementsThe following system requirements will ensure satisfactory performance by FLARENET on resonably sized simulation.

2.2 InstallationFLARENET may be run as a single user program, in which case a single copy of the program is run from either a stand alone PC or from a workstation on a network. The enforcement of the single user license is by means of the security key attached to the computer or workstation upon which the program is running. Workstation usage requires write access to the program directory.

Optionally, FLARENET may be run as a multi-user program , in which case the program is used in the same way as the single user version, but has the maximum number of concurrent licenses enforced by means of a single security key attached to a server on the network.

2.2.1 FLARENET Program Installation

1. Shut down all other operating Windows programs on the computer before starting the installation process.

2. Insert the FLARENET software CD into the CD-ROM drive of the computer.

3. From the Start Menu, select Run

4. In the Run dialog box, type: d:\Server\setup.exe and click on the OK button (where d: corresponds to the drive letter of the CD-ROM drive).

System Component Requirement

Microprocessor 80486 DX or higher IBM PC type computer. Pentium recommended.

Operating System Microsoft Windows release 3.1 or later.

Physical Memory 8 MB of memory. 16 MB recommended.

Disk Space Approximately 12 MB of free hard disk space is required.

Serial PortA 25 pin parallel port with a female connector for connection of the security key (do not plug in a serial mouse behind the security key).

Keyboard Enhanced (101) keyboard.

Mouse required. Note that a mouse cannot be plugged into the back of the security key.

2-3

2-4 Installation

2-4

5. After several seconds the FLARENET welcome screen will appear. Click Next to continue.

6. Specify your company name for registration and click Next.

7. Select the setup type you would like to install: Network or Standalone. Click Next to continue.

8. Select the components you would like to install as well as select the directory that Flarenet will be installed. Click Next to begin the installation.

As the installation progresses, you will see a view showing the progress of the installation. Note that some files are installed to the appropriate Windows directory (the exact path may vary depending on your system setup).

9. When the installation is complete, you will be prompted with a dialogue box that tells you that you will need to restart you computer to complete the installation.

2.2.2 Starting FLARENETThe FLARENET setup program automatically creates the FLARENET program group which contains the FLARENET application icon.

Double click the FLARENET application icon. The following startup dialog box will be displayed as FLARENET is being loaded; after several seconds, you will be in the FLARENET environment.


2.3 Licensing

2.3.1 Overview

Standard Licenses

Standard mode is based on setting a hard limit of users that are licensed to use the application. In Standard mode, one license is consumed per feature, decreasing the available licenses for that feature by one. For example, a customer with 10 network licenses for Flarenet and 5 network licenses for HYSYS can simultaneously run up to 10 copies of Flarenet and 5 copies of HYSYS. When a user is finished with that feature, the license is released back to the license server allowing other users access to launch it.

Optionally a system administrator can customise this process by setting the license server to release specific licenses only to specific users. See Section 2.6 - License Server Environment Variables for more information.

Licenses can optionally define how many instances can run on a single license. For instance, Flarenet licenses default to allow up to three copies of Flarenet to be running on a single PC while only consuming one Flarenet license from the server. If a fourth copy on that PC is started a second license will be consumed.

Licenses can also be mixed between standalone and network (refer to Section - License Modes). The License Manager will always look for a standalone license first and failing that search for an available network license.

Token Licensing

Token mode allows Hyprotech applications to be licensed in a slightly different way then the Standard mode by setting an upper limit on usage, but not defining specific license numbers. The license specifies a maximum number of tokens and each product is assigned a token value. Every time the application is run, it consumes a number of token licenses until the limit is reached.This upper limit allows any combination of products to be used up to the limit.

This makes token mode very flexible. You can setup any number of application combinations within the framework of your license setting. For example, say Flarenet has a token value of 10 and HYSYS a token

Most licenses are issued in Standard mode.

2-5

2-6 Licensing

2-6

value of 4, with an upper limit of 50 tokens. With this configuration 5 users could run Flarenet. However, it also allows 4 users to run Flarenet and with 2 runing HYSYS, or allow 3 HYSYS users.

Token mode is active in the your Com Security Server (CSS) object if the AEATOKENMODE flag/name is set in the LSHOST Environment variable or "lshost" file.

When the CSS object is in token-mode it will mutate the license request (the Flarenet license is used for this example). The CSS object will request a Descriptor license called AET_Flarenet (note the "T" in the name). This license will be used to define the token value of the Process feature (The token value is a number from 1 to 99).

When the CSS object finds the Descriptor license and extracts a valid token value of "N" units. It will then request "N" units of the AEA__Token license. Effectively this will check-out N AEA__Token licenses at once. If this is successful, then the AEA_Flarenet check-out will return to the application with a success.

If the CSS object cannot find the AET_XXX license for feature XXX then you cannot check-out any tokens for that feature, so the entire check-out fails.

Server error messages are slightly different compared to Standard mode. This is to reflect the underlying fact that we are no longer checking out an AEA_Flarenet license, but we are checking out AET_Flarenet and AEA__Token licenses.

The error messages in token mode has the server names prefixed by either D_ or T_ this means that when the check-out occurs, you may receive an error which states "D_RHART733" with some failure code. This means that the Descriptor license check-out failed. Similarly, an error of "T_RHART733" and an error code indicating that the Descriptor worked, but the AEA__Token check-out failed.


License Modes

There are two methods that can be used to license Hyprotech applications: Standalone licensing and Network licensing.

Standalone licensing is setup so that both the application and the licenses are installed on the a single computer. This kind of configuration is most often used when the application is only used by an individual on a particular computer. Refer to Section 2.3.3 - Standalone Licensing to configure the application to run with Standalone licenses.

Network licensing is setup so that the application is installed on a users computer and the licenses are installed on a network license server. The license server consists of network licenses and the license server application. The license server is used to manage all of the license codes. Refer to Section 2.3.4 - Network Licensing to configure the application to run with Network licenses.

2.3.2 Installing the Hardware keyBoth the standalone and network mode of the application require the use of a hardware key. A unique locking code is read from the hardware key and used to generate license codes needed to run the software. This code locks the hardware key to the licenses. When the application runs, the locking codes must then match the hardware key’s locking code for the licenses to be valid.

Please note that to avoid damage to the computer or key, the computer should be powered down before installation of the key.

Key Types

Computer ID Keys

Computer ID keys (or CID keys) are beige Sentinel SuperPro keys, manufactured by Rainbow Technologies. The Computer ID key is installed on the parallel port (printer port) of your computer. An arrow indicates which end should be plugged into the computer.

CID keys can be used for both standalone and network versions of the software. Note that network licensing requires a Computer ID key be installed on machines that will be used as license servers (refer to Section - Setting up a License Server for additional information). Standalone licensing requires a Computer ID key to be installed on

2-7

every machine that will be running the application.

2-8 Licensing

2-8

Hyprotech Green Keys

Hyprotech green keys are installed into either a 9-pin or 25-pin serial port of your computer. The arrow on the label indicates the proper orientation of the GreenKey (the arrow must point towards the computer).

Hyprotech Green keys can only be used for standalone versions of the software. Standalone licensing requires that a key is installed on every machine that will be running the application.

2.3.3 Standalone LicensingOnce the application and the Hardware key have been installed on your computer you need to install the license file. The license file contains all of the license codes specifying all licensed features of the application.

Locking Codes and License Files

A license code needs to be created that includes the information required to identify a specific computer. The information used to identify a computer is called its fingerprint. The fingerprint required by the application comes from the attached hardware key.

FLARENET Purchases

If you have just purchased FLARENET, you will find included in your package a FLARENET software CD, a Computer ID key and a diskette with the license file associated with that key. Copy the license file in to your FLARENET root directory, where the FLARENET executable is located. Rename the license file to lservrc. You are now set up to run FLARENET with Standalone licenses.

FLARENET Upgrades

If you are currently running a standalone version of FLARENET using a Hyprotech Green Key and are upgrading to the SLM security, you will have to perform the following steps.

1. Open the following directory; C:\Program Files\Common Files\Hyprotech\SLM License Tools.

To install FLARENET refer to Section 2.2.1 - FLARENET Program Installation.

Note the license file does not have an extension.


2. Run the echoid32.exe application. The following window will appear displaying six locking codes.

3. Email the locking code for your key(s) to Hyprotech at [email protected]. In addition to the Lock Code please include the following information in your message to ensure a prompt reply:

• your name and title• company name• address• key serial number

Once Hyprotech has received your Lock Code a license file will be generated and sent back to you.

4. Place the license file in your FLARENET root directory, where the FLARENET executable is located. Rename the license file to lservrc. You are now set up to run FLARENET with Standalone licenses.

2.3.4 Network LicensingNetwork licensing is configured so that each user must install the software on their computer and the licenses are installed on a separate license server computer.

Setting up a License Server

A license server computer is made up of the following components.

• Computer ID key (refer to the Section 2.3.2 - Installing the Hardware key)

• License Server software - follow the steps outlined below to install the License Server on your license server computer.

• License file

Figure 2.1

Because the lock code is unique to each key, you should supply this information for each key that requires an update.

To install FLARENET refer to Section 2.2.1 - FLARENET Program Installation.

2-9

2-10 Licensing

2-10

Because the license server computer must be operational for FLARENET users to run their software, the best choice for the license server computer is one that is left on continually. The most trouble-free installation will result from a license server computer used only for the license server function. This avoids conflicts with other software.

Note that the license server computer does not need to be a powerful or fast computer. The powerful personal computer of a FLARENET user is one of the poorer choices for the license server computer. This computer can be switched off behind locked doors for the weekend, rebooted after lockup in another software program (terminating FLARENET users), or require reconfiguration to suit the needs of a new software program, causing difficulties for existing programs (like the license server software).

Installing the License Server

The following instructions are written assuming installation on Windows NT 4.0 (SP 5) or Windows 95/98.

The License Server installation program creates files only in the directory specified to it during the installation setup procedure.

1. Shut down all other operating Windows programs on the computer before starting the installation process.

2. Insert the FLARENET software CD into the CD-ROM drive of the computer.

3. From the Start Menu, select Run

4. In the Run dialog box, type: d:\Server\Setup\setup.exe and click on the OK button (where d: corresponds to the drive letter of the CD-ROM drive).

5. Follow the on-screen instructions to proceed with installation.

Multiple license server computers can be setup to spread the load over multiple computers.

Note the license server requires certain drivers to talk to the Computer ID key. If you are having problems with the license server ensure that these drivers are installed by running the setup.exe program found in the Delivery Drivers directory on the included disk.


Locking Codes and License Files

A license code needs to be created which includes the information required to identify a specific computer. The information used to identify a computer is called its fingerprint. The fingerprint required by FLARENET comes from the attached Computer ID key.

FLARENET Purchases

If you have just purchased FLARENET, you will find included in your package a FLARENET software CD, a Computer ID key and a diskette with the license file associated with that key. Copy the license file in to your license server directory. The default license server directory is:

C:\Program Files\Rainbow Technologies\sentLM\Server\

Rename the license file to lservrc. Once you have copied the license file to the license server directory you must stop and re-start the license server. See Step 5. below for information on how this done for you operating system.

FLARENET Upgrades

If you wish to upgrade your FLARENET licenses or you did not receive your license file you must perform the following steps.

1. Open the following directory: C:\Program Files\Common Files\Hyprotech\SLM License Tools.

2. Run the echoid32.exe application. The following window will appear displaying six locking codes.

Figure 2.2

Note the license file does not have an extension.

2-11

2-12 Licensing

2-12

3. Email the locking code for your key(s) to Hyprotech at [email protected]. In addition to the Lock Code please include the following information in your message to ensure a prompt reply:

• your name and title• company name• address• key serial number

Once Hyprotech has received your Lock Code a license file will be generated and sent back to you.

4. Place the license file in your license server directory. The default license server directory is:

C:\Program Files\Rainbow Technologies\sentLM\Server\

Rename the license file to lservrc.

5. You must then stop and then re-start the license server when ever you change or make changes to the license file. This is done differently depending on the operating system you are using.

Now that you have the proper license codes in place see the next section on setting the system environment variable to point your FLARENET user computers to your license server.

Because the lock code is unique to each key, you should supply this information for each key that requires an update.

Operating System Description

Windows 2000

The license server controls are accessed by opening the Admin Tools folder, found in the Control Panel, and then opening Services. The license server is seen in the list as SentinelLM. Highlight SentinelLM and click on the restart icon located in the toolbar at the top of the window.

Windows NT (SP 5)

The license server controls are accessed by opening the Services found in the Control Panel. The license server is seen in the list as SentinelLM. To stop the server highlight SentinelLM and click on the Stop button. To re-start the server click on the Start button.

Windows 95/98 The license server has its own window running that allows you to access the license server controls.


2.4 Redundant License Servers

Redundant license servers and license balancing offer several important benefits.

• You can acquire licenses even if a particular license server goes down (license server backup).

• The speed that a you can acquire a license is optimized by distributing license tokens among multiple license servers to reduce the traffic for a particular license server (license balancing).

All of the redundant license servers at your site form a license server pool. Each of the license servers in the pool can take over for any other if one of the l license servers goes down. Each license server runs on a separate computer on the network.

License server computers do not have to be on the same subnet. License servers can be in geographically separate locations on subnets connected to one another via WAN, Internet, or dial-up connections.

You may also configure the license servers so that only one is active and the others are solely backup license servers. In this case, all of the license tokens should be allocated to just a single license server and license balancing turned off. Then the other license servers would only be used if the main license server went down.

The redundant license file (lservrlf) is used to define which license servers make up the redundant license server pool as well as how many token of which licenses are distributed among those license servers. Each computer on which a redundant license server resides requires a copy of this file.

All servers in a redundant license server pool can grant tokens. However, only one of the license servers is designated as the leader. By default, the leader is the first license server in the pool you start up. However, Wrlftool can be used to set the priority order of the license servers. If the leader goes down, the next highest priority server becomes the leader in turn.

The leader synchronizes communication between the license servers in the pool. The leader also makes sure that all the license servers in the pool are using the same version of the redundant license file. If this file is changed on one of the license servers, after one of the license servers

It is recommended that the leader should be in an area of the network with good bandwidth since the leader must communicate with all other redundant license servers.

2-13

2-14 Redundant License Servers

2-14

is stopped and restarted, the leader detects the change in the file and automatically updates the rest of the license servers to the newer version.

If a license server exhausts its token allocation, it will ask the leader to borrow tokens from other license servers. If tokens are available from any other license server, the leader will take away the unused tokens and give them to the requesting license server. The auto-borrowing mechanism helps in load balancing also. Based on requests, the tokens get distributed among the license servers after some interval of time into a pattern that reflects real token use, leading to a balanced system.

2.4.1 Setting up Redundant License Servers

There are three aspects to setting up and using redundant license servers.

• Decide how many redundant license servers to set up and select the computers on which they will reside (you must define at least three, but five is recommended). A Computer ID key must be attached to each of these computers.

• Create the redundant license file, lservrlf, using the Wrlftool utility to define the redundant license server pool.

• Bring up the license servers. To maintain the pool, use the WlmAdmin utilities to dynamically reconfigure the redundant license server pool and set license token allocation.

The following points will go through the steps required to setup a redundant license server.

1. Install the license server on the computers selected to be redundant servers (refer to Setting up a License Server).

2. Set each user to access the preferred license server by setting the LSHOST or LSFORCEHOST environment variables on the users computers (refer to Section 2.6 - License Server Environment Variables).

3. Along with the application you will receive a Computer ID key for each redundant license server. You will also receive a diskette that contains a license file (lservrc) that is locked to each of the Computer ID keys.

4. Install the protected application(s) on the users computers.

Redistribution of tokens only occurs if license borrowing is turned on.

Each computer on which a redundant license server resides must have a fixed IP address.

If you are upgrading your application licenses or you did not receive a license file refer to section Locking Codes and License Files.


5. Use the Wrlftool or rlftool to add the license servers to the redundant license server pool and set the preference number of the license servers to set the order in which the leader will be chosen if the license server goes down.

6. Then, still using the Wrlftool or rlftool utility, install the redundant license codes you received with the application into the redundant license file and set their initial token distribution among the redundant license servers

7. Since this is the first time that the redundant license server pool has been set up, you need to copy the redundant license file to each of redundant license servers. After this, changes to any one of the redundant license files will automatically be transmitted to each redundant license server when one of the license servers is stopped and restarted.

8. Bring up each of the license servers in the pool. Because the redundant license file is in the same directory as each license server, each license server will automatically start up as a redundant license server.

Maintaining the Redundant License Server Pool

Once the redundant license servers are set up, you can use lspool or WlmAdmin from any computer on the network to change the license distribution, view information about the redundant license server pool, and turn borrowing on/off (refer to Section 2.7 - License Server Tools for more information).

Make sure that any of the license servers that you will be using as redundant license servers are shut down before using the Wrlftool or rlftool to create the redundant license file.

2-15

2-16 Commuter Licensing

2-16

2.5 Commuter LicensingCommuter licensing allows you to temporarily use a protected application on a portable computer (i.e. laptop) that is not connected to the network. To check out a license the portable computer must first be attached to the network and have access to a license server containing licenses for that application. This application must also be installed on the portable computer.

Since commuter licenses use the same license tokens as other types of licensing you will want restrict the percentage of license tokens on a specific license server that can be used for commuter licensing. you must use the -com option with the LSERVOPTS environment variable. This will ensure that all of your license tokens are not used up by commuter licensing.

Before your users check out a commuter authorization the portable computer must have:

• the protected application installed and ready to use. Remember the application must be able to run off the network.

• network access to the appropriate license server.• is connected to the network.• access to the Wcommute or lcommute utility.

Refer to Section 2.7.7 - Wcommute and Section 2.7.8 - lcommute for information on how to check out a commuter authorization.

You will want to encourage your users to always check authorizations back in as soon as possible.

The commuter licensing user must check an authorization back into the same license server from which the authorization was checked out.


2.6 License Server Environment Variables

If you choose to set any of the environment variables use the following steps to help you if you are unfamiliar with the system tools for Windows NT 4.0 or WIndows 2000.

1. Open the Start menu select Settings and then select Control Panel.

2. Double click on the System icon to open the System Properties window.

3. Select the Environment tab.

4. In the Variable text box enter the name of the environment variable. For example LSHOST.

5. In the Value text box enter the address, hostname of the server(s) or variable options.

6. Click OK.

2.6.1 LSHostWhen the application is started it first tries to identify a standalone license. If this fails it will then (by default) attempt to obtain a license by searching for license servers over the network. This broadcast search is limited to the users local network subnet. If the License Server is located outside the users local subnet then the address/hostname of the server must be specified for the application to make the network connection. There are three ways you can set the environment variable to contact the proper license server. The following lists the steps the application takes to look for a license server:

• If the LSFORCEHOST environment variable is set, the application looks for the specific license server host listed in that variable. If it cannot find that computer, an error message is displayed, and the application will close.

• If no LSFORCEHOST environment variable is set, then the application looks for the LSHOST environment variable. If this variable has been set then the application looks for any of the license server hosts listed.

• If LSHOST is not set, then a check is made for a file with the name “lshost” in the applications root directory. If this file is found, then the application looks for any of the license server hosts listed in the file.

Note the lhost file does not have an extension attached to it and capitalization does not matter. If you choose to use this file you must place it in the applications root directory.

2-17

2-18 License Server Environment Variables

2-18

The LSHOST variable naming conventions are:

• Any valid hostname recognized by your network.• Numeric names (IP address).• NO_NET to disable the default broadcast mechanism from

searching the network.

LSFORCEHOST

The LSFORCEHOST environment variable is used to force the application to look for only one license server computer. If the license server listed in the variable cannot be found, the application stops searching and returns an error. LSFORCEHOST overrides an LSHOST environment variable or “lshost” file, and prevents a network broadcast from being done.

LSHOST

The LSHOST environment variable is used to tell the application to search for one or more license servers. When this variable is set the application will work through the list of license servers beginning at the first license server in the list to the last. If none of the specified license servers is found, the application stops searching and returns an error. LSHOST prevents a network broadcast from being done.

The “lshost” file works the same way as the LSHOST environment variable. The following is an example of an “lshost” file.

This file will search for TESTSERV_1, TESTSERV_2, TESTSERV_3 and TESTSERV_5, in that order. Notice that TESTSERV_4 has been commented out. Anything that follows a number symbol (#) is treated as a comment.

Figure 2.3

Note if you are using a network system where the DNS is variable, then you cannot use the IP address for this purpose.

Note when using multiple server names you need to separate the names, in both the environment variable string and “lshost “ file, with a colon (:).


2.6.2 LSERVOPTSThe LSERVOPTS environment variable is used to set license server options. The options for this variable are found in the following table.

Some of the options that can be set with LSERVOPTS can be set with a specific environment variable. It is recommended that the specific environment variable be used whenever possible

Option Description

-s license file

Specifies the name and location of the license code file. By default, the license server will use the file, lservrc, in the local directory. This can also be specified by the LSERVRC environment variable.

-e license configuration file

Specifies the name and location of the optional license configuration file. This can also be specified by the LSERVRCCNF environment variable.

-l usage log file

Enables usage logging by specifying the name and location of the usage log file (note you can not include any spaced in the path name). A typical log file name is lserv.log. By default usage logging is disabled.

-z usage log file size

Specifies the maximum size of the usage file. The default value for the maximum size of the log file is 1 megabyte. The size can be specified in bytes, kilobytes, or megabytes. For example, -z 2000 means 2000 bytes, -z 2k means 2 kilobytes and -z 2m means 2 megabytes. Once the maximum size of the file is reached, the license server will create a backup log file unless the -x option has been used.

The maximum number of backup files is 99. However you can move existing backup log file to another directory and the license server will begin again.

-x

By default, on overflow of the usage log file, the file contents will be moved into a backup file. New usage records are then written to the original file until it overflows again. If the -x option is specified, the file will not be backed up on overflow. Instead the license server will simply stop writing further records to the file.

-port port number

The license server port number is used by the TCP/IP protocol when transferring data between the license server and the client. This can also be specified by the LSPORT environment variable.

-com percentage

Commuter licensing uses the same license tokens as other network licenses. To ensure that not all license tokens are used up by commuter, set this option to the percentage of license tokens you want used for commuter licensing. Once that percentage of tokens are used up on more will be made available to commuters until tokens are returned.

2-19


2-20

Setting Usage Logging

If you activate the usage logging option the license server records all license requests and returns in this file. Usage reports can be viewed by using the lsusage tool (refer to Section 2.7.6 - lsusage on how to view the log file). Information is recorded in the file one entry per line in the following format.

-rlf redundant license file

Starts the license server as a redundant license server using the specified redundant license file. You do not need to use this option to start the license server as a redundant license server if a lservrlf redundant license file is in the same directory as the license server.

-lfe encryption level

Specifies the level of encryption that license transactions will be written to the licenses server log file, 1 to 4.

• 1 - No encryption• 2 - No encryption. Transaction data will be

readable, but tampering with or deleting an entry will be detected by lsusage. This is the default encryption level if you do not specify one.

• 3 - Encrypt usage only. Transaction data will be readable except for license usage data. Such entries will not be displayed by lsusage.

• 4 - Encrypt entire record. All transaction data for the license code will be encrypted. Such entries will not be displayed by lsusage.

-f error file

Specifies the name and location of the error file where the license server will log occurrences of unexpected conditions. By default, this is disabled until the option is specified. Then the license server will append the lservlog file in the current directory.

-u group reservations file

Specifies the name and location of the optional group reservations file. BY default, the license server uses the lsreserv file in the current directory.

-b

For Windows 95/98, starts the license server as a background service that will not be terminated when the computer user logs off. The license server runs without displaying a window or message. You must use the lsrvdown command to stop the license server.

Option Description

Element Description

Server-LFE Customer defined log file encryption level as specified by the license server -lfe option.

License-LFE Vendor defined log file encryption level. If this is non-zero, it overrides the Server-LFE.

Date The date the entry was made.


Example

Time-Stamp The time stamp of the entry.

Feature Name of the feature.

Ver Version of the feature.

Trans The transaction type. 0 indicates an issue, 1 a denial, and 2 a release.

NumKeysThe number of licenses in use after the current request/release. (Encrypted if encryption level is set to 3 or 4)

Keylife How long in second, the license was issued. Only applicable after a license release.

User The user name of the application associated with the entry.

Host The host name of the application associated with the entry.

LSver The version of the license server.

CurrencyThe number of licenses handled during the transaction. (Encrypted if encryption level is set to 3 or 4)

Comment The text passed in by the protected application.

Element Description

Figure 2.4

2-21


2-22

2.6.3 LSDEFAULTDIRThe LSDEFAULTDIR environment variable can be used to set the default location of the license server file. It’s recommended that the license server default directory not be changed. By default, the default directory is set to the directory the license server executable is located in.

Example

2.6.4 LSERVRCThe LSERVRC environment variable is used to set the name and location of the license code file. It is recommended that the default name and location are used for this file. By default, this file will be called lservrc and reside in the license server default directory.

Example

Figure 2.5

Figure 2.6


2.6.5 LSERVRCCNFThe LSERVRCCNF environment variable can be used to set the name and location of the license server configuration file. This file is used in setting up user alerts and other options. It is recommended that the default name and location are used for this file. In most installations, this file will be called lservc.cnf and reside in the license server default directory. If LSERVRCCNF is not used to specify the configuration file then the name and location of this file will be based upon the name and location of the license code file. In this case the configuration file will reside in the same directory as the license code file and have the same base name as the license code file but with the extension.cnf.

Example

2.6.6 LSPROTOCOLThe LSPROTOCOL environment variable is used to specify the communications protocol that will be used to communicate with the license server. Specify IPX or UDP (for TCP/IP) to choose the protocol.

Example

Figure 2.7

Figure 2.8

2-23


2-24

2.6.7 LSPORTThe license server port number is used by the TCP/IP protocol when transferring data between the license server and the client. Do not change the port number unless your vendor has instructed you to do so or conflicts are occurring between the license server and another network application that is using the license server’s port number. (The license server default port number is 5093). A symptom of such a conflict would be license server communication errors.

Example

Figure 2.9


2.7 License Server ToolsAll of the license server tools are located in the following directory:

C:\Program Files\Common Files\Hyprotech\SLM License Tools

2.7.1 WLMAdminWLMAdmin is a network administration tool that provides you with information on licensing activities, such as license servers detected, detail on active licenses, and information on licensed users. Running the WLMAdmin application will open the following window.

The View menu provides three ways to query license servers.

• Single Server - allows you to specify the host name, IP address or IPX address of a single license server.

Note that when you first open WLMAdmin you will see a blank screen. From then on WLMAdmin will start up with whatever view mode was last used.

Figure 2.10

2-25

2-26 License Server Tools

2-26

• Server List - allows you to create a list of license servers you would like to view. The list is created by choosing the Server List option from the Edit menu. You will see the following window.

Specify the host name, IP address or IPX address of the license server into the text box and click Add. You can add as many servers as you want. To delete a license server from the list highlight the server and click Delete. Click Close when you are done.

• All in Subnet - lists all of the license servers found on your area of the network. This option may be slow since WLMAdmin searches the entire subnet.

The list located in the left-hand pane displays all of the license servers that could be found on the network. Beneath the license server name is a list of the all the licenses associated with that license server. Beneath the license name is a list of license users (users who are using the license) and queue users (users who are waiting for the license).

As you can see in Figure 2.10 highlighting a license displays information on the characteristics of the license in the right -hand pane. You will see information such as:

• license type,• how many concurrent users can use the license,• when the license expires,• what users currently are using the license, and• whether or not the license can be used for computer licensing.

Clicking on the user name located under the license user or queue user heading will display information about that user in the right-hand pane.

Figure 2.11


Maintaining a Redundant License Server Pool

There are two menu sets that you can use to maintain your redundant license servers: License Server specific and License specific.

To view the License Server specific menu click on a license server name in the main display and then click the right mouse button. This will display the following menu.

To view the License specific menu click on a license name in the left hand pane of the main display and then click the right mouse button. This will display the following menu.

Figure 2.12

Option Description

Add server to pool Adds the selected license server to the license server pool that is a member of.

Delete server from pool

Deletes the selected license server from it redundant license server pool.

Get leader server name

Display the name of the leader of the redundant license server.

Get pool server list Display the list of all license servers in the redundant license pool that this license server is a member.

Disable borrowing for all features

Turn off all token borrowing for this license server.

Enable borrowing for all features

Turn on all token borrowing for this license server.

Figure 2.13

2-27


2-28

2.7.2 lsmonLsmon is a command line utility that retrieves information about all features currently licensed by the license server and the clients using those features. The following option may be supplied:

If Server-host is omitted, lsmon will attempt to talk to the license server on the computer indicated in the LSHOST environment variable or in the LSHOST file. If the variable or file does not exist, then it will attempt to contact a license server using the broadcast mechanism. If lsmon fails to find a license server, you will receive an error message and the utility will exit.

Option Description

Change distribution criteria

For this license, change how its tokens are distributed among the redundant license servers. When you select this command, you see a text box that you may type the new distribution criteria. Use the following format: Server1:tokens1^Server2:token2... where Server is the host name, IP address or IPX address that identifies the redundant license server and tokens is the number of tokens to allocate to that server.

Get distribution criteria

See how the license tokens are currently distributed. This is the dynamic allocation, not the initial allocation set in the redundant license file. You see a list of the license servers. Each server is followed by three numbers, where the first number is the number of tokens allocated, the second number is the tokens in use, and the third number is commuter tokens in use.

Disable borrowing For this particular license, disables tokens borrowing for this license server only.

Enable borrowing For this particular license, enables token borrowing for this license server only.

Option Description

Server-host The name of the computer that the license server is running.


2.7.3 WrlftoolWrlftool is a Windows-interface program that allows you to create and maintain a redundant license file.

Creating and Maintaining the Redundant License Server Pool

To create a new redundant license file, select New from the File menu. To edit an existing redundant license file, select Open from the File menu then select the file.

To add a new license server to the pool, click Add Server. Specify the host name and the IP or IPX address of the computer that runs the license server. You are required to add at least 3 servers. Once you have added more than one server to the pool you can use the Move Up or Move Down buttons to adjust the order of the server in the pool. This sets the preference order. Although the first license server in the pool to be started up becomes the leader by default, the preference order determines in what order the license servers will become the leader if the license servers go down.

At any time you can select a license server and click Delete Server to remove the server from the pool.

Figure 2.14

If you are editing an existing redundant license file we recommend you make your changes to a copy of your file under another name in order to avoid synchronization problems with someone trying to use the file when you are editing it. Remember to change the name back to its original name when you are done.

2-29


2-30

Adding, Editing and Deleting Redundant Licenses

To add a redundant license to the pool, click Add License. You will see a screen that allows you to either add the license code or specify a file containing the license code.

Once you have added the license code the license editing view will appear.

Figure 2.15

Figure 2.16


The license code, feature name, version number, number of license servers that make up the redundant license server pool and number of tokens available make up the License Attribute group box. Along with displaying the license attributes you can specify the following information for the license.

• Borrowing threshold - This is the percentage of license tokens that, when consumed, will trigger borrowing from another license server in the pool. For example, if this license has 100 tokens and the borrowing threshold is set to 90%, the when 10 license tokens are remaining on any license server, that license server will borrow more tokens from another license server in the pool

• License distribution - From a list of servers in the pool you can choose which license servers will service this license by selecting the appropriate Include check boxes. For each license server you include you can select how many tokens will initially be distributed to that license server.

For a license code with more than one license you can set up each license differently by scrolling through each license using the Next License button. If you would like all of the licenses set up to be identical you can use the Accept All button.

After at least one license has been added to the pool, you can select an existing license from the main screen and click Edit License to modify the license or click Delete License to delete the license from the pool.

2.7.4 rlftoolRlftool is a command line utility that allows you to create and maintain a redundant license file.

To use rlftool in menu mode to create a new redundant license file, from DOS type:

rlftool

Or, to modify an existing redundant license file, type:

rlftool -1 redundant-license-file

You then see a menu that lists the rlftool options. Type the number of the option you want to use and press Return. To exit and save the file, type 12 and press Return.

You may find using the Windows-interface Wrlftool utility more convenient than this utility.

2-31


2-32

Two options available when using rlftool in menu mode that are not available as command line options are:

To use the rlftool as a command line utility, type rlftool followed by any of the options below except -l (which will take you to the menu).

Option Description

Preference Order

The first redundant license server in the pool to be started is by default the leader. However, by setting the preference order, you set the order that the license servers will be elected the leader if the leader goes down.

View/Edit License You can select an existing license to view, and may change the token allocations for that license.

Option Description

-h Displays a list of the rlftool options

-l filename Load or create a redundant license file.

-a server-name address

Add the license server specified by the host name and IP or IPX address.

-d server-name Delete the license server specified by the host name.

-A license-code

Add the specified license code to the redundant license file. Enclose the license code in quotation marks. You will be prompted for token distribution and for the threshold percentage. When this percentage of the total number of tokens has been consumed on any license server, token borrowing will occur.

-F license-file-name Add the license codes contained in the specified text file to the redundant license file.

-D feature version Delete a license code with the specified feature/version from the redundant license file.

-p pool-name Change the redundant license server pool name to the one specified. May be 8 characters.

-s sequence-#

Change the sequence number of the redundant license file. (A mismatch in sequence numbers triggers transmission of the redundant license file to the other redundant license servers when the license server that this change is being made is stopped and restarted. Not necessary except in extraordinary circumstances, because this is handled for you automatically.(

-t time-stamp

Change the time-date stamp of the redundant license file. (A mismatch in time-date stamps triggers transmission of the redundant license file to the other redundant license servers when the license server that this change is being made is stopped and restarted. Not necessary except in extraordinary circumstances, because this is handled for you automatically.(


2.7.5 lspoolLspool is a command line utility that performs the same functions the WLMAdmin utility does.

You must set the LSHOST environment variable to point to one of the redundant license servers. Some lspool options dynamically change the redundant license server configuration, but do not write the changes permanently to the redundant license file. When the redundant license servers are restarted the changes are lost.

The lspool options are:

-R report-filename Write the redundant license file contents to the specified file.

-C conflict report Write any conflicts between token allocation and license servers to the specified file.

Option Description

When making changes to the redundant license server pool as a whole we recommend you select the leader license server to make the changes to.

Features and versions are obtained from the license file lservrc.

Option Description

-h Displays a list of lspool options

-a license server

Add the license server to the redundant license server pool. You can specify the host name, IP address, or IPX address to identify the new license server.

Modifies the redundant license file.

-d license server

Deletes a license server from the redundant license server pool. You can specify the host name, IP address, or IPX address to identify the new license server.

Modifies the redundant license file.

-l Displays the host name of the leader redundant license server.

-p Displays a list of license servers in the redundant license server pool.

-c feature name dist-crit.

Changes the distribution criteria for the specified feature/version tokens. The dist-crit format is: server1:tokens1^server2:tokens2... where server is the host name, IP address, or IPX address. If the version is not specified, it must be replaced with empty quotation marks: “ “.

Temporary change only in effect until the license server is stopped and restarted. Does not modify the redundant license file.

-g feature versionDisplays the distribution criteria for the specified feature/version. If the version is not specified, it must be replaced with empty quotation marks: “ “.

2-33


2-34

2.7.6 lsusageLsusage is a command line utility that displays a summary of application usage, providing information on license transactions contained in the license server usage file. At the command line enter the following: lsusage logfile. Where logfile is the name you have given to the log file. The log file will then be displayed with the following information.

-b feature version OFF|ON

DIsable or enable token borrowing for the specified feature version for this license server. If the version is not specified, it must be replaced with empty quotation marks: “ “.


-B OFF|ON

Disable or enable token borrowing for all features/versions for this license server.


-L event OFF|ON

Disable or enable logging for the specified event.

• 0 - log all events• 1 - log license server up. On by default• 2 - log election of leader license server• 3 - log heart beat• 4 - log borrowing related event• 5 - log usage information event• 6 - log distribution change• 7 - log license information synchronization• 8 - log redundant license file transfer• 9 - log license server down• 10 - log license server addition/deletion• 11 - log license addition deletion

Option Description

Element Description

Feature name/Version Identifies the license for which this entry was made.

%age DeniedThe percentage of requests for this license that were denied (usually because the hard limit of the license had already been reached).

%age Issued The percentage of requests for this license that were granted.

Ttl Keys Issued The number of tokens for this license that were issued.


2.7.7 WcommuteWcommute is a Windows-interface utility used for checking commuter authorizations in and out. When you first open Wcommute you will see the following window.

%age Queued granted The percentage of queued license requests that were granted.

%age Qreq.

The percentage of license requests that were placed in the license queue. (License requests are queued only if license queuing is enabled for this license.)

Min. App. Duration The minimum number of minutes the application for this license was in use.

Avg. App. Duration The average number of minutes the application for this license was in use.

Max. App. Duration The maximum number of minutes the application for this license was is use.

LOG REPORT FOR Sessions: x

The session numbers for this license server that were logged in this file.

Element Description

Figure 2.17

Object Description

Check Out Checks out an authorization for a specific license

Check In Checks in an authorization for a specific license

2-35


2-36

Perform the following steps to check out an authorization for a license.

1. Click Search Subnet or Single Server to display the commuter licenses available for authorization.

2. Click once on a commuter license, that you would like to check out, to select it. This activates the Please enter the number of days until the authorization expires text box. Enter a number between 1 to 30 to specify the number of days this license will be checked out.

3. Click Check Out. A read check mark will then appear next to the license indicating that it has been checked out.

4. To check in an authorization, look for the license under the license server that you checked the license out of (There should be a red check mark beside it, indicating it has been checked out). Click once on the license name to select it and then click Check In.

2.7.8 lcommuteLcommute is a command line utility used for checking commuter authorizations in and out. The lcommute options are:

Search Subnet Searches for and displays all of the license servers on your subnet.

Single ServerSearched for and displays a specified license server. Requires you to specify the license server’s computer hostname, IP address or IPX address.

Object Description

Figure 2.18Remember the name of the license server that you obtained the authorization. You will need to check the authorization back into the same license.

Note if you do not supply any command line options lcommute will ask you for the information it needs.

Option Description

-h Displays list of options.

-c:i Check in an authorization for a commuter license.

-c:o Check out an authorization for a commuter license.

-s:license server Host name, IP address or IPX address of the license server servicing the commuter license.


Example

lcommute -s:QATEST -c:o -f:AEA_BDK -d:30

In this case, the license server to be contacted is QATEST, the authorization is being checked out, the feature name identifying the commuter license is AEA_BDK, the license does not have a version number, and the authorization is being checked out for 30 days.

2.7.9 ipxechoDisplays the IPX network address. When using the IPX network protocol, the license server host name must be the IPX address of the computer on which the license server resides. The address is returned in the form of four hexadecimal bytes (network-node address) followed by six hexadecimal bytes (IPX-address).

2.7.10 lswhereLswehere is a command line utility used to display the network names of the computers running the license server. By default the address of the computer that the license server is running as well as its host name is displayed. You can specify the following options:

-f:feature Name of feature. This identifies the license you want to use.

-v:version Version. This also identifies the license you want to use. If the license does not have a version, this can be omitted.

-d:days Number of days the authorization will be checked out, from 1 to 30. Only use when you are using the -c:o option.

Option Description

Option Description

-d Displays details on the license servers found on the network. This is the default setting.

-r Displays just the IP or IPX addresses of the license servers found on the network.

2-37

2-38 User Options

2-38

2.7.11 lsdecodeLsdecode is a command line utility used to decrypt parts of the information in license code strings. This utility can be useful in determining the details of licensing agreements. It also enables you to decipher unknown codes. You can specify the following options:

2.8 User Options

2.8.1 Setting Group ReservationsGroup reservations allows you to associate user groups with each feature and reserving for each group a pool containing a certain number of licenses. Any licenses not specifically reserved fall into the general pool.

A group specification consists of the following:

• The name of the feature for which the reservation applies,• The name of the group,• The number of licenses reserved for that group,• And the login names of users or host IDs of computers that

belong to that group.

The groups must be mutually exclusive. Different groups for the same feature should not have common users or computers. The number of licenses reserved for a feature cannot exceed the number of concurrent copies specified in the license code for that feature.

When the license server receives a request, it checks whether the user making the request belongs to a group. If so, and licenses are available for that group, the license server will issue the license(s) and remove

Option Description

-s license-file

The name of the license file. If this is not specified the default file name, lservrc, is used. You cannot use lsdecode to read a redundant license file (default name lservrlf), but you can use it to read a redundant license code file containing un-installed redundant license code.

-e license-config-file

The name of the configuration file that may be needed in case readable license strings have been customized by re-mapping of fixed strings. By default, lsdecode looks for license-file.cnf (for example, lservrc.cnf).


them from that group’s pool. Otherwise, requests will be serviced with licenses from the general pool until no licenses are available.

Group reservations should be entered according to the following format, with one group per line:

feature_name[ ,ver ]:group_name:num_of_licenses: user_name | computer

One or more user_name and or computer may be specifies, but at least one value must be specified in the last field. The version number is optional. If no version number is specified, only the feature name is used.

2.9 Potential Problems Running FLARENET

The following table provides descriptions of some possible error returns from the system.

The path and file name of the reservation file is defined by the LSERVRC environment variable.

The characters $ and ! have special meaning. $ indicates the computer name, and ! indicates a logical NOT.

Error Description

aLS_BADHANDLE Handle used on call did not describe a valid licensing system context

aLS_INSUFFICIENTUNITS Licensing system could not locate enough available licensing resources

aLS_LICENSESYSNOTAVAILABLE No licensing system could be found with which to perform the function invoked

aLS_LICENSETERMINATEDThe licensing system has determined that the resources used to satisfy a previous request are no longer granted to the calling software.

aLS_NOAUTHORIZATIONAVAILABLE The licensing system has no licensing resources that could satisfy the request.

aLS_NOLICENSESAVAILABLEThe licensing system has licensing resources that could satisfy the request, but they are not available at the time of the request.

aLS_NORESOURCES Insufficient resources (such as memory) are available to complete the request.

aLS_NO_NETWORK The network is unavailable.

aLS_NO_MSG_TEXTA warning occurred while looking up an error message string for the LSGetMessage() function.

aLS_UNKNOWN_STATUS An unrecognized status code was passed into the LSGetMessage() function.

aLS_BAD_INDEX An invalid index was specified in LSEnumProviders() or LSQuery License.

2-39

2-40 Potential Problems Running FLARENET

2-40

aLS_NO_MORE_UNITS No additional units are available.

aLS_LICENSE_EXPIREDThe license associated with the current context has expired. This may be due to a time-restriction on the license.

aLS_BUFFER_TOO_SMALL Input buffer is too small, need a bigger buffer.

aLS_NO_SUCCESS No success in achieving the target.

aVLS_NO_LICENSE_GIVENGeneric error when a license is denied by a server. If reasons are known, more specific errors are given.

aVLS_APP_UNNAMED Application has not been given a name.

aVLS_HOST_UNKNOWNUnknown host (Application is given a server name but that server name doesn’t seem to exist).

aVLS_NO_SERVER_FILENo FILE giving license server name (Application cannot figure out the license server.

aVLS_NO_SERVER_RUNNING On the specified machine, license server is not RUNNING.

aVLS_APP_NODE_LOCKEDThis feature is node locked but the request for a key came from a machine other than the host running the SentinelLM server.

aVLS_NO_KEY_TO_RETURNLSrelease called when this copy of the application had not received a valid key from the SentinelLM server.

aVLS_RETURN_FAILED Failed to return the key issued to this copy of the application.

aVLS_NO_MORE_CLIENTS End of clients on calling VLSgetClientInfo.

aVLS_NO_MORE_FEATURES End of features on calling VLSgetFeatureInfo.

aVLS_CALLING_ERROR General error by vendor in calling function etc.

aVLS_INTERNAL_ERROR Internal error in SentinelLM.

aVLS_SEVERE_INTERNAL_ERROR Irrecoverable Internal error in SentinelLM.

aVLS_NO_SERVER_RESPONSE

On the specified machine, license server is not responding. (Probable cause - network down, wrong port number, some other application on that port etc.).

aVLS_USER_EXCLUDED User// excluded.

aVLS_UNKNOWN_SHARED_ID Unknown shared id.

aVLS_NO_RESPONSE_TO_BROADCAST

No servers responded to client broadcast.

aVLS_NO_SUCH_FEATURE No such feature recognized by server.

aVLS_ADD_LIC_FAILED Failed to add license.

aVLS_DELETE_LIC_FAILED Failed to delete license.

aVLS_LOCAL_UPDATE Last update was done locally.

aVLS_REMOTE_UPDATE Last update was done by the SentinelLM server.

Error Description


aVLS_VENDORIDMISMATCHThe vendor identification of requesting application does not match with that of the application licensed by this system.

aVLS_MULTIPLE_VENDORID_FOUND

The server has licenses for the same feature, version from multiple vendors, and it is not clear from the requested operation which license the requester is interested in.

aVLS_BAD_SERVER_MESSAGE

An error has occured in decrypting (or decoding) a network message. Probably an incompatible or unknown server, or a version mismatch.

aVLS_CLK_TAMP_FOUND

The server has found evidence of tampering of the system clock, and it cannot service the request since the license for this feature has been set to be time tamper proof.

aVLS_NOT_AUTHORIZED The specified operation is not permitted - authorization failed.

aVLS_INVALID_DOMAIN The domain of server is different from that of client.

aVLS_UNKNOWN_TAG_TYPE The server does not know of this tag type.

aVLS_INVALID_TAG_TYPE A tag’s type is invalid for the operation requested.

aVLS_UNKNOWN_TAG The server doesn’t know this tag.

aVLS_UPDATE_TAGGED_KEY_ERROR Attempt to update a tagged key.

aVLS_TAGS_NOT_SUPPORTED Server does not support tags.

aVLS_LOG_FILE_NAME_NOT_FOUND ???????

aVLS_LOG_FILE_NAME_NOT_CHANGED

???????

aVLS_FINGERPRINT_MISMATCH ???????

aVLS_TRIAL_LIC_EXHAUSTED Trial License Usage Exhausted or Trial License Expired.

aVLS_NO_UPDATES_SO_FAR No Updates have been made so far.

aVLS_ALL_UNITS_RELEASEDEven though the client asked VLSreleaseExt API to return a specific number of units, it returned all the issued units.

aVLS_QUEUED_HANDLE The LS_HANDLE = is a queued handle.

aVLS_ACTIVE_HANDLE The LS_HANDLE = is an active handle.

aVLS_AMBIGUOUS_HANDLE The status of LS_HANDLE = is ambiguous.

aVLS_NOMORE_QUEUE_RESOURCES Could not queue the client because the queue is full.

aVLS_NO_SUCH_CLIENT No client as specified, found with the server.

aVLS_CLIENT_NOT_AUTHORIZED Client not authorized to make the specified request.

aVLS_BAD_DISTB_CRIT Distribution Criterion given is not correct.

aVLS_LEADER_NOT_PRESENT Processing not done because current leader is not known.

Error Description

2-41

2-42 Potential Problems Running FLARENET

2-42

aVLS_SERVER_ALREADY_PRESENT Tried to add a server to pool which is already there.

aVLS_SERVER_NOT_PRESENT Tried to delete a server who is not in pool currently.

aVLS_FILE_OPEN_ERROR File can not be open.

aVLS_BAD_HOSTNAME Host name is not valid or can not be resolved.

aVLS_DIFF_LIB_VER Different API version. Client server version mismatch.

aVLS_NON_REDUNDANT_SRVR A non-redundant server contacted for redundant server related information.

aVLS_MSG_TO_LEADER Message forwarded to leader. It is not an error.

aVLS_CONTACT_FAILOVER_SERVER Update fail. may be Contact server died or modified.

aVLS_UNRESOLVED_IP_ADDRESS IP address given can not be resolved.

aVLS_UNRESOLVED_HOSTNAME Host name given is unresolved.

aVLS_INVALID_IP_ADDRESS Invalid IP address Format.

aVLS_SERVER_FILE_SYNC Server is synchronizing dist table. Not an Error.

aVLS_POOL_FULL Pool is already having max. no. of servers it can handle.

aVLS_ONLY_SERVER Pool will not exist if this only server is removed.

aVLS_FEATURE_INACTIVE The feature is inactive on the requested server.

aVLS_MAJORITY_RULE_FAILURE The token cannot be issued because of majority rule failure.

aVLS_CONF_FILE_ERROR Error related to configuration file operation.

aVLS_NON_REDUNDANT_FEATURE A non-redundant feature given for redundant feature related operation.

aVLS_NO_TRIAL_INFO No Trial usage info.

aVLS_TRIAL_INFO_FAILED Trial usage query failed.

aVLS_ELM_LIC_NOT_ENABLE elan License not enabled.

aVLS_NOT_LINKED_TO_INTEGRATED_LIBRARY

Commuter related error code not linked to integrated library.

aVLS_CLIENT_COMMUTER_CODE_DOES_NOT_EXIST

Client commuter code does not exist.

aVLS_CLIENT_ALREADY_EXISTS Client already exist.

aVLS_NO_MORE_COMMUTER_CODE End of features on calling VLSgetCommuterInfo API.

aVLS_GET_COMMUTER_INFO_FAILED Failed to get client commuter info.

aVLS_UNABLE_TO_UNINSTALL_CLIENT_COMMUTER_CODE

VLSuninstallAndReturnCommuterCode() API failed.

aVLS_ISSUE_COMMUTER_CODE_FAILED

VLSgetAndInstallCommuterCode() failed.

aVLS_UNABLE_TO_ISSUE_COMMUTER_CODE

Server is not allowed to issue commuter code for the requested feature and version.

Error Description


2.10 Glossary of Terms

aVLS_NOT_ENOUGH_COMMUTER_KEYS_AVAILABLE

Not enough key available to check out commuter code.

aVLS_INVALID_INFO_FROM_CLIENT Invalid lock Info provided by client.

aVLS_CLIENT_ALREADY_EXIST Server has already check out one commuter code for this client.

aVLS_COMMUTER_CODE_DOES_NOT_EXIST

No commuter code exit with this feature / version.

aVLS_COMMUTER_CODE_ALREADY_EXIST

Client has already had commuter code with this feature version.

aVLS_SERVER_SYNC_IN_PROGRESS Server synchronization in progress. Please wait...

Error Description

Term Description

License Permission granted to program/application/component to use a specific feature.

License Code

Encrypted/Checksummed/TamperProtected Alpha-Numeric text string, used to define a single licensed feature. Each code is licked to a hardware key (Computer ID key or GreenKey).

License File File containing License Codes for the specific features licensed to the user.

Standalone License License granted local to the users machine.

Network License License granted/obtained from a network license server.

Network License Server

Program/Service running on a computer which is attached to the LAN. Grants Licenses to the application which is running on network user machines.

Hardware Key Physical hardware device used to secure Licenses.

2-43

2-44 Glossary of Terms

2-44

Get Started 3-1

3 Get Started

3-1

3.1 Data Requirements....................................................................................... 3

3.2 Starting Flarenet........................................................................................... 6

3.3 Starting A New Model .................................................................................. 9

3.4 Saving The Model....................................................................................... 13

3.5 Building The Pipe Network........................................................................ 14

3.6 Defining The Scenarios ............................................................................. 24

3.7 Defining The Sources ................................................................................ 27

3.8 Rating The Network.................................................................................... 33

3.9 Printing Data And Results ......................................................................... 38

3-2

3-2

Get Started 3-3

This Get Started tutorial shows the fundamental principles involved in using FLARENET to design and rate a new flare system. This "guided tour" will expose you to most of the major features of FLARENET.

This tutorial assumes that you are familiar with the use of 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 PFD 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.

3.1 Data RequirementsBefore you can start to build a computer model of the flare header system, you must first define all the data that will determine your system.

Pipe Segment Data

Data Description

ConnectivityYou would normally have prepared a systemsketch that defines the nodes to which the pipesegments are connected.

Length and fittingsloss coefficients foreach pipe segment

These will be based upon either a preliminary ordetailed isometric drawing of the piping.

Diameter and pipeschedule for each pipesegment

If you are rating an existing network, these willnormally be taken from the flare system P&ID. Ifyou are sizing a new flare system, the pipediameters that you define are relativelyunimportant since they will be overwritten by thesizing algorithms. It is recommended thatreasonable diameters be defined, so that thesizing algorithm initialises to a condition that willgive faster convergence.

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 vapour phase methods.

3-3

3-4 Data Requirements

3-4

The following diagram shows the connectivity of the system that you will be designing in this example.

The pipe segments in the network diagram are detailed in the following table.

The flare tip is assumed to be a simple opened ended piece of 18" pipe. It will not be resized. Fittings loss coefficients exclude pipe enlargement and junction losses which will automatically be calculated, assuming standard tees for the junctions.

Figure 3.1

Segment Name Length (m)InternalDiameter(mm)

WallThickness(mm)

FittingsLoss

ElevationChange (m)

Flare Tip 0 876.3 3.0 0

Stack 100 876.3 19.05 0 100

Header 3 50 876.3 19.05 0 0

Tail Pipe 1 25 428.65 14.275 0 0

Tail Pipe 2 25 428.65 14.275 0 0

Get Started 3-5

Relief Source Data

The following data must be specified for the sources:

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.

Default Source Data

Data Description

Flow and Composition

These may vary for each scenario that youare evaluating. If a relief source is not usedin a particular scenario the flow may be set tozero. The Flow refers to the quantity of fluidthat the source valve must pass as aconsequence of the plant upset condition.The Rated Flow refers to the quantity of fluidthat the source valve will pass due to itsphysical construction. Rated flow mustalways be greater than or equal to flow.

Maximum Allowable BackPressure (MABP)

This is the maximum pressure that can existat the outlet of the device (source) withoutaffecting its capacity.

Downstream temperature

This temperature is used as the pressureindependent temperature at which thesource enters the network. This temperatureis used when ideal gas enthalpies are usedto calculate the heat balance, or as an initialguess when any other enthalpy method isused.

Upstream pressure andtemperature

These are only used if the Ideal Gasenthalpies are not used for the heat balance.These may vary for each scenario that youare evaluating. With relief valves, the flowingpressure should be used.

Discharge flange size This will normally be determined from therelief valve sizing calculations.

SourceName

Flowrate(kg/hr)

FlangeSize(mm)

Mol. Wt.USTemp(C)

DS Temp(C)

US Pres.(bar abs)

MABP(bar abs)

Source 1 100000 300 20 15 15 10 5.0

Source 2 100000 300 25 15 15 10 5.0

3-5

3-6 Starting Flarenet

3-6

Source 1 Only Data

Source 2 Only Data

For each source, it will be assumed that the rated flow is equal to the maximum flow for the source from the two scenarios +20%.

System Design Constraints

In this case, the following data is used for both Scenarios:

• Maximum allowable mach number - 0.50 for both main headersand tailpipes.

3.2 Starting FlarenetThe installation process creates a shortcut to Flarenet in the Start Menu under Programs...AEA Technology. To Start Flarenet,

1. Select the Start Menu.

2. Move from the Programs to AEA Technology to Flarenet 3.0.

SourceName

Flowrate(kg/hr)

FlangeSize(mm)

Mol. Wt.USTemp(C)

DS Temp(C)

US Pres.(bar abs)

MABP(bar abs)

Source 1 100000 300 20 15 15 10 5.0

Source 2 0 300 25 15 15 10 5.0

SourceName

Flowrate(kg/hr)

FlangeSize(mm)

Mol. Wt.USTemp(C)

DS Temp(C)

US Pres.(bar abs)

MABP(bar abs)

Source 1 0 300 20 15 15 10 5.0

Source 2 100000 300 25 15 15 10 5.0

Get Started 3-7

3. Select Flarenet 3.0.

Now you are ready to begin working with Flarenet.

Figure 3.2

3-7

3-8 Starting Flarenet

3-8

When you start Flarenet, the Flarenet Desktop will appear:

Note that this view has been resized; your Desktop view should appear larger than this when initially opened. To re-size the view, click and drag the outside border. To make the view full size, press the Maximize button in the upper right hand corner.

Before setting up the Get Started case, you should choose the Flarenet unit set for displaying information. You can check your current unit set by accessing the Preferences Editor:

1. Select the Preference from the Flarenet File menu, the Preferences

Figure 3.3

Get Started 3-9

Editor view will open.

2. The current unit set is shown in the Units drop down menu. The Flarenet defualt is Metric, which will be used for this example. Also confirm that the Edit Objects on Add checkbox is active(checked). This option will open the object editor view each time a new object is added.

3. Press the OK button to close the Preferences Editor view.

3.3 Starting A New ModelTo start a new case, do one of the following:

• Select New from the File menu on the main program menubar.

Figure 3.4

Figure 3.5

New Case Button

3-9

3-10 Starting A New Model

3-10

• Press the New Case button.

The Description Editor view appears.

Enter the appropriate data (as shown in Figure 3.6) into the User Name, Job Code, Project, and Description fields, and then click the OK button. The Component Manager view then appears.

There are number of ways to select components for your simulaion. One method is to filter the database for a certain component type. In this model, we will be using the following components: Methane, Ethane and Propane. To add methane using the filter option:

1. Ensure that the HC checkbox in the Component Type group is

Figure 3.6

Figure 3.7The Selected list box is empty, indicating that no components have yet been installed in the case.

Initially, all the checkboxes in the Component Types group are active. You can deactivate them by pressing the Invert button.

Get Started 3-11

activated.

2. Start typing methane in the Selection Filter edit box. Notice that as you are typing, the Database list box will be filtered out to show only the matching components.

3. Double click Methane in the Database list box. Methane will now have been selected and will be shown in the Selected list box.

Repeat the previous step with Ethane and Propane. As an alternative method, you may scroll through the Database list box until you see the desired component. Highlight the component by single clicking on it and then click Add to place it in the Selected list.

Figure 3.8

3-11

3-12 Starting A New Model

3-12

This Component Manager view will now appear as follows:

Click OK to close the Component Manager view and accept the list of components.

Open the View menu and then the Data sub-menu. Select Components from the sub-menu. The Components data view will be displayed:

Figure 3.9

Notice that now all the required components are shown in the Selected list box, indicating that they have been installed in the case.

You can use the horizontal scroll bar at the bottom of the view to view all of the component properties.

Figure 3.10

Get Started 3-13

3.4 Saving The ModelIt is good practice to periodically save your case by doing one of the following:

• Press the Save button on the button bar.• Select Save from the File menu.• Press <Ctrl><S>.

As this is the first time you have saved your case, the Save Flarenet Model view will be displayed:

After selecting an appropriate disk drive and directory in the Save in drop-down menu, enter the name of the file to which you wish to save the case in the File name field. Note that you do not need to include the .fnw extension; FLARENET will add it automatically.

Click Save to close the dialog box and save the file.

Figure 3.11

Save button

3-13

3-14 Building The Pipe Network

3-14

3.5 Building The Pipe Network

Since all scenarios have a common pipe network, you should first build the pipe network model via the PFD.

Press the Open PFD View button on the button bar. The PFD view will be displayed with its own button bar.

At this point the view should be blank, since we have not added a single object yet.

The desired objects can be added with any of the following features:

• Pressing the Toggle Palette Display button on the PFDview or the F4 key will open the Toolbox view, whichdislays all the objects available in Flarenet. You can add anobject by clicking on it.

• Objects can also be added via the Pipe Manager and theNode Manager views. These are accessible throughPipes... and Nodes... in the Build menu, respectively.

Open PFD Button

Figure 3.12

Before proceeding any further, make sure that the Edit Objects on Add checkbox on the General tab of the Preferences Editor view is checked.

Get Started 3-15

3-15

For the Flare Tip, press the Flare Tip button on the Toolbox view. Since the Edit Objects on Add checkbox is selected, The Flare Tip Editor view will be displayed:

By default the Flare Tip has been named as 1, which can be changed to a more appropriate name as follows:

1. Click in the Name field on the Flare Tip Editor view.

2. Delete the default name and type Flare Tip as the new name.

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. Now you need to specify the pipe, which will be simulated as a flare stack, and it is attached to the Tip.

3. Enter the name Stack in the Inlet field.

4. In the At drop down box, select Downstream as the pipe end connected to the Tip.

In order to complete the Flare Tip Editor view, you need to specify the Diameter and the Fitting Loss values on the Calculations tab.

Figure 3.13Flare Tip Button


3-16

5. On the Calculations tab, enter 876.3 as the diameter and 3 as the fitting loss in the appropriate fields.

Now you have provided all the necessary information about the Tip.

6. Press OK to close the view.

Notice that two new objects have been added to the PFD view. You can either manually arrange them by clicking and dragging the object icons or let Flarenet auto-arrange the icons by selecting Regenerate from the PFD menu under the View drop down menu.

7. Open the Stack property view and move to the Dimensions tab.

8. Specify the Length as 100 m and the Elevation Change as 100 m.

This will result in a vertical pipe measuring 100 m tall.

Figure 3.14

Get Started 3-17

9. Select the Nominal Diameter as 36 inch and the Pipe Schedule as 40.

10. On the Methods tab, confirm that Vertical Pipe and VLE Method are set as default models.

In this example, every pipe segment uses the default models which are specified on the Methods tab of the Calculation Options Editor view.

11. Press OK to close the Stack property view.

Now you need to add another pipe segment which will be added using the Pipe Manager view.

12. Select Pipes from the Build menu on menu bar. The Pipe Manager view will be displayed.

Figure 3.15

Figure 3.16

The default methods, as defined in the Calculation Options Editor view, are Isothermal Vapour Pressure Drop, and Compressible Gas VLE.

3-17


3-18

13. Click the Add button.

The Pipe Editor property view will be displayed.

14. Change the default name to Header 3.

15. Move to the Dimensions tab and enter the following data in the appropriate fields:

16. Click OK to close the Pipe Editor view.

17. Close the Pipe Manager view by pressing the OK button.

You need to attach Header 3 with Stack using a node. Flarenet allows you to choose between a variety of nodes, since you need a simple connection between the two pipes, a Connector node will be used.

18. On the PFD Toolbox view, click on the Connector button.

Figure 3.17

Field Value

Length (m) 50

Nominal Diameter (inch) 36

Pipe Schedule 40

Connector Button

Get Started 3-19

This will open the Connector Editor view.

19. On the Connections tab, Enter the new name as Con 1.

20. In the Downstream drop down box, select Stack and specify the connection at Upstream (of Stack) in the At drop down box.

21. In the Upstream drop down box, select Header 3 and specify the connection at Downstream (of Header 3) in the At drop down box.

22. Move to the Calculations tab.

Notice that by default the Theta has a value of 90 deg and the Fitting Loss Method is set as Calculated. You can leave the default value for this example.

23. Press the OK button to close the Connector Editor view.

Now, a tee will be added, using the Node Manager, to combine the flow from the two sources.

Figure 3.18

Figure 3.19

3-19


3-20

24. Select Nodes from the Build menu on menu bar. The Node Manager view will be displayed.

25. Click the Add button and Select Tee from the pop up list.

The Tee Editor will be displayed.

26. Change the default name to Tee 1 in the Name field.

27. Specify the Downstream connection to be Header 3 and select Upstream from the At drop down menu.

28. Move to the Calculations tab and change the Fittings Loss Methods setting to Miller in the drop down menu.

29. Close the Tee Editor property view by pressing Ok button.

30. Press Ok to close the Node Manager view.

Figure 3.20

Figure 3.21

Get Started 3-21

Now, you can add two pipe segments to the upstream and branch section of Tee 1 using the Pipe Manager view.

31. Open the Pipe Manager view by selecting Pipes from the Build menu.

32. Press the Add button to add a new pipe segment.

33. Change the default pipe name to Tail Pipe 1.

34. Specify Tee 1 as the Downstream connection and select Branch in the At drop down box.

35. Move to the Dimensions tab and specify the Length as 25 m.

36. Set Nominal Diameter as 18 inch from the drop down box.

37. Press Next to add another pipe segment.

Figure 3.22

Figure 3.23

3-21


3-22

Notice that Tail Pipe 1 has been added to the Pipe Manager list.

38. Change the new pipe segment default name to Tail Pipe 2.

39. Specify Tee 1 as the Downstream connection and select Upstream in the At drop down box.



42. Press the OK button to close the Pipe Editor property view.


Select Data-Pipes from the View drop down menu on the menu bar. The Pipes view displays the data for all of the pipe segments:

Figure 3.24

Figure 3.25

Get Started 3-23

You could also check the PFD to ensure that the proper connections have been made. A portion of the PFD is displayed below:

Figure 3.26

3-23

3-24 Defining The Scenarios

3-24

3.6 Defining The Scenarios

You now need to define the data for all the scenario, the Default Scenario, Source 1 Only and Source 2 Only scenarios. Since each case must contain at least one scenario, a set of default scenario data is created when you start a new case. We need to modify this data.

44. Select Scenarios from the Build menu on the menu bar.

The Scenario Manager dialog box will be displayed.

45. Double click on Default Scenario in the Scenario list box.

Figure 3.27

Get Started 3-25

The Scenario Editor dialog box will be displayed. Alternatively, you could single-click Default Scenario in the Scenario list box then click Edit.

46. Enter the data for the Default Scenario scenario as shown in Figure 3.28, then click OK to close the Edit Scenario dialog box and return to the Scenario Manager.

Now we should add the data for the Source 1 Only scenario.

47. Click Add on the Scenario Manager. The Clone Scenario From dialog box will be displayed.

48. Select the only entry in the dialog box, i.e. Default Scenario scenario.

Figure 3.28

Figure 3.29

3-25


3-26

49. Change the default name to Source 1 Only and enter the data for the Source 1 Only scenario as shown in Figure 3.30.

50. To add a new scenario press Next on the Scenario Editor and select the Source 1 Only scenario from the Clone Scenario From dialog box.

51. Change the default new for the new scenario to Source 2 Only.

52. Enter the data for the new scenario as shown in Figure 3.30.

53. Click OK to close the Scenario Editor view and return to the Scenario Manager, then click OK to close the Scenario Manager.

Figure 3.30

Figure 3.31

Get Started 3-27

3.7 Defining The SourcesYou will now enter the source data for the sources in all scenarios. Since for the first part of the example you will be defining the source compositions in terms of molecular weight, the program preferences must be set to accept the compositions on this basis.

54. Select Preferences from the File drop down menu on the menu bar. The Preferences view will be displayed.

Ensure that Mol. Wt. is selected in the Composition Basis drop down list box.

55. Click OK to close the Preferences Editor view.

Figure 3.32

Figure 3.33

3-27

3-28 Defining The Sources

3-28

Before defining a set of source data, You must select the scenario which corresponds to this data. You will start by defining the data for the Default Scenario.

56. Select the Default Scenario scenario. Any open data views would now display data for this scenario.

You can now add the data corresponding to this scenario for each source.

Figure 3.34

Get Started 3-29

57. Select Nodes from the Build menu on the main menu bar (<Alt>, B, S). The Node Manager dialog box will be displayed:

58. Click Add and select Control Valve from the pop up list.

Figure 3.35

Figure 3.36

The Mole Fractions are automatically estimated from the Molecular Weight. Because HC is selected from the drop down, only hydrocarbon components will be used to match the Molecular Weight.

3-29


3-30

The Control Valve Editor view will be displayed:

59. Change the default name to Source 1. Select Tail Pipe 1 in the Outlet drop down down box and set connection to be at Upstream (of Tail Pipe 1).

60. Move to the Conditions tab and set the Mass Flow as 100000 kg/hr.

61. On the Composition tab, specify the Mol. Wt. to be 25.

62. Click Next to add a new source. The node pop up list will again be displayed.

Figure 3.37

Figure 3.38

Get Started 3-31

63. Again select Control Valve from and the Control Valve Editor view will be displayed.

64. Name the new source as Source 2 on the General tab.

65. Select Tail Pipe 2 in the Outlet drop down down box and set connection to be at Upstream (of Tail Pipe 2).

66. Repeat step# 60-62 to add all the information required by the scenario.

67. Press the Ok button to close the Control Valve Editor view.

The Node Manager dialog box will now appear as follows:

Figure 3.39

Figure 3.40

The source name appears as the source name preceded by the plant identifier.

3-31


3-32

68. Close the Node Manager view by pressing the OK button.

69. Select Data-Sources from the View drop down menu on the menu bar.

The Sources data view for the Default Scenario will be displayed:

You must now add the source data for the other two scenarios.

70. Select the Source 1 Only scenario from the Scencario Selector drop down menu on the tool bar (to the right of the buttons). Any open data views will now display data for this scenario.

71. Make the following changes to the flowrates in the Source 1 Only Scenario (all other information remains the same):

• Source 1 - 100000 kg/hr• Source 2 - 0 kg/hr

72. Next, select the Source 2 Only scenario from the Scencario Selector drop down menu on the tool bar (to the right of the buttons) and make the following changes to the Source 2 Only:

• Source 1 - 0 kg/hr• Source 2 - 100000 kg/hr

Figure 3.41

Get Started 3-33

3.8 Rating The NetworkWe have now entered all the model data and can now make the sizing calculations. We will need to set the calculation options before starting the calculations.

73. Select Options from the Calculation menu on the menu bar. The Options dialog box will be displayed:

74. Enter the data as shown above, then click OK.

The options are explained below:

Figure 3.42

OptionDefault

SettingDescription

Max Iterations25 The maximum number of iterations.

The calculations will stop if this limit isreached.

PressureTolerance

0.01% When the difference in pressurebetween successive iterations is lessthan this tolerance, convergence isassumed.

Mass BalanceTolerance

1% This is the solution tolerance for theiterative mass balance performedduring looped system calculations.

DampingFactor

1 The damping factor used in the iterativesolution procedure.

AtmosphericPressure

1.01325 barabs

Specify the atmospheric pressure.

3-33

3-34 Rating The Network

3-34

AmbientTemperature

15o C The Ambient temperature must be inthe range -100oC to 100oC.

Wind Velocity 10 m/s The average wind velocity.

LengthMultiplier

1 The length of the pipe is multiplied bythis value to determine the equivalentlength used for the pressure dropcalculation.

CalculationMode

Rating Select the Calculating Mode from thedrop down menu. The available optionsare:

• Rating - It is used to check the existingflare system in a plant. This methodcalculates the pressure profile for theexisting pipe network.

• Design - It is used to design new flaresystem for the plant. During calculationit adjust the diameters of all pipes untilall the design constraints of MABP,velocity and etc have been meet. Thesediameters can be smaller than theinitially defined data.

• Debottleneck - It is used to determineareas of the flare system that must beincreased in size due to either theuprating of the existing plant and henceflare loading, or the tie-in of new plant.

Loop Solver

Newton-Raphson

These algorithms provides globallyconvergent methods for nonlinearsystems of equations. The methodsavailable are:

• Broyden - It provides a quicker solutionsince it does not have to calculateJacobian matrix. You need to providebetter guesses for the tear pipe flows.

• Newton-Raphson - It works morereliably if default initial guesses areused but takes a longer time.

Rated Flow forTailpipes

OFF If checked, the rated flow will be usedin the sizing calculations for thetaipipes (as opposed to the actualflowrates). The API guide for Pressure-Relieving and Depressuring Systemsrecommends that tailpipes be sizedbased on the rated capacity

Enable HeatTransfer

OFF If checked, heat transfer can take placebetween the pipe segment and thesurroundings for pipe segments whichhave Heat Transfer with Atmosphereenabled.

OptionDefault

SettingDescription

Get Started 3-35

You can now start the calculations.

75. Select Calculate from the Calculation drop down menu on the menu bar (<Alt><C><C> or <Ctrl><R>). Alternatively, you could select the Calculations button.

All Scenarios

OFF If checked, the calculations will bemade for all the scenarios defined inthe model, otherwise the calculationswill be made only for the scenariowhich is currently displayed.

When sizing calculations are made fora number of scenarios simultaneously,a single network is calculated that willsatisfy the desigh constraints for allscenarios.

Choked FlowCheck

ON If left unchecked, velocities will not belimited to the sonic condition. This isuseful in sizing calculations since themach number limitations will still be metby the time the final solution is reached.Calculation speed is greater at the riskof numerical instability andconvergence failure.

Echo SolverHistory

OFF When checked, it should enableprinting of much more intermediateinformation during calculations. Thisshould be left unchecked unless youhave convergence problems.

ForceConvergentSolver

OFF Check if you are modelling aconvergent flare system, but with 2flare tips as commonly found onoffshore floating production facilities.

OptionDefault

SettingDescription

Figure 3.43Calculations button

3-35

3-36 Rating The Network

3-36

Note that the current calculation is shown on the status bar:

Once the calculations are complete you can review the results.


The Sources view shows the data for all the sources in the current scenario.

77. Select Results-Messages from the View drop down menu on the menu bar.

Figure 3.44

Figure 3.45

Get Started 3-37

The Messages data view will be displayed.

This window contains general information and warning messages regarding the calculations. Note that the Problem tab list two mach number violations for Tail Pipe 1 and Tail Pipe 2. These problems can be fixed by doing detail design for the network. But for this example you can ignore them and concentrate more on the features available in Flarenet.

78. Press Pressure/Flow Summary button on the button bar.

The Pressure/Flow Summary view will be displayed:

Figure 3.46

Pressure/Flow Summary button

Figure 3.47

3-37

3-38 Printing Data And Results

3-38

3.9 Printing Data And Results

To print data and results:

79. Select Print from the File drop down menu on the menu bar. The Print dialog box will be displayed.

80. Click on the appropriate check boxes to select the items that you wish to print. Also check the All Scenarios box to print the results for all of the scenarios instead of just the current scenario. If you want to print to a file, check the Print To Text File box, then select the file type from the Text File Type drop down.

81. Click OK.

This case is available for review in Step1.fnw (model before calculations) and Step1c.fnw (model after calculations) which are stored in the qstart sub-directory under the main program directory.

Upgrading the Network 4-1

4 Upgrading the Network

4-1

4.1 Data Requirements....................................................................................... 3

4.2 Starting Flarenet........................................................................................... 7

4.3 Opening the Old Model ................................................................................ 8

4.4 Updating the Model ...................................................................................... 9

4.5 Defining The Scenarios ............................................................................. 17

4.6 Defining The Sources ................................................................................ 19

4.7 Sizing The Network .................................................................................... 25

4.8 Rigorous Rating ......................................................................................... 30

4.9 Printing Data And Results ......................................................................... 32

4-2

4-2


In this Get Started tutorial you will change the network designed in Chapter 3 - Get Started 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 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 PFD 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.

4.1 Data RequirementsBefore you can start to upgrade a computer model of the existing flare header system, you must first define all the data that will determine your system.

Pipe Segment Data

Note that this tutorial is a continuation of the one in Chapter 3 - Get Started and requires that you complete that tutorial before continuing with this one.

Data Description

ConnectivityYou would normally have prepared a systemsketch that defines the nodes to which the newpipe segments are connected.

Length and fittingsloss coefficients fornew pipe segment

These will be based upon either a preliminary ordetailed isometric drawing of the piping.

Diameter and pipeschedule for each pipesegment

If you are rating an existing network, these willnormally be taken from the flare system P&ID. Ifyou are sizing a new flare system, the pipediameters that you define are relativelyunimportant since they will be overwritten by thesizing algorithms. It is recommended thatreasonable diameters be defined, so that thesizing algorithm initialises to a condition that willgive faster convergence.

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 vapour phase methods.

4-3


4-4

The following diagram shows the connectivity of the system which includes the new sources you will be adding in this example.

The pipe segments in the network diagram are detailed in the following table.

The new pipe segments Header 1, Header 2, Tail Pipe 3 and Tail Pipe 4 will be added.

Figure 4.1

Segment Name Length (m)NominalDiameter(inch)

ScheduleFittingsLoss

ElevationChange (m)

Stack 100 36 40 0 100

Header 1 50 28 30 0 0

Header 2 50 32 40 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


Relief Source Data

The following data must be specified for the sources:

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.

Default Source Data

Data Description

Flow and Composition

These may vary for each scenario that youare evaluating. If a relief source is not usedin a particular scenario the flow may be set tozero. The Flow refers to the quantity of fluidthat the source valve must pass as aconsequence of the plant upset condition.The Rated Flow refers to the quantity of fluidthat the source valve will pass due to itsphysical construction. Rated flow mustalways be greater than or equal to flow.

Maximum Allowable BackPressure (MABP)

This is the maximum pressure that can existat the outlet of the device (source) withoutaffecting its capacity.

Downstream temperature

This temperature is used as the pressureindependent temperature at which thesource enters the network. This temperatureis used when ideal gas enthalpies are usedto calculate the heat balance, or as an initialguess when any other enthalpy method isused.

Upstream pressure andtemperature

These are only used if the Ideal Gasenthalpies are not used for the heat balance.These may vary for each scenario that youare evaluating. With relief valves, the flowingpressure should be used.

Discharge flange size This will normally be determined from therelief valve sizing calculations.

SourceName

Flowrate(kg/hr)

FlangeSize(mm)

Mol. Wt.USTemp(C)

DS Temp(C)

US Pres.(bar abs)

MABP(bar abs)

Source 1 100000 300 20 15 15 10 5.0

Source 2 100000 300 25 15 15 10 5.0

Source 3 100000 300 30 15 15 10 5.0

Source 4 100000 300 35 15 15 10 5.0

4-5


4-6

Source 1 Only Data

Source 2 Only Data

Source 3 Only Data

Source 4 Only Data

For each source, it will be assumed that the rated flow is equal to the maximum flow for the source from the two scenarios +20%.

SourceName

Flowrate(kg/hr)

FlangeSize(mm)

Mol. Wt.USTemp(C)

DS Temp(C)

US Pres.(bar abs)

MABP(bar abs)

Source 1 100000 300 20 15 15 10 5.0

Source 2 0 300 25 15 15 10 5.0

Source 3 0 300 30 15 15 10 5.0

Source 4 0 300 35 15 15 10 5.0

SourceName

Flowrate(kg/hr)

FlangeSize(mm)

Mol. Wt.USTemp(C)

DS Temp(C)

US Pres.(bar abs)

MABP(bar abs)

Source 1 0 300 20 15 15 10 5.0

Source 2 100000 300 25 15 15 10 5.0

Source 3 0 300 30 15 15 10 5.0

Source 4 0 300 35 15 15 10 5.0

SourceName

Flowrate(kg/hr)

FlangeSize(mm)

Mol. Wt.USTemp(C)

DS Temp(C)

US Pres.(bar abs)

MABP(bar abs)

Source 1 0 300 20 15 15 10 5.0

Source 2 0 300 25 15 15 10 5.0

Source 3 100000 300 30 15 15 10 5.0

Source 4 0 300 35 15 15 10 5.0

SourceName

Flowrate(kg/hr)

FlangeSize(mm)

Mol. Wt.USTemp(C)

DS Temp(C)

US Pres.(bar abs)

MABP(bar abs)

Source 1 0 300 20 15 15 10 5.0

Source 2 0 300 25 15 15 10 5.0

Source 3 0 300 30 15 15 10 5.0

Source 4 100000 300 35 15 15 10 5.0


System Design Constraints

In this case, the following data is used for both Scenarios:

• Maximum allowable mach number - 0.50 for both main headersand tailpipes.

4.2 Starting FlarenetTo Start Flarenet,

1. Select the Start Menu.

2. Move from the Programs to AEA Technology to Flarenet 3.0.

3. Select Flarenet 3.0.

Now you are ready to began working with Flarenet.

Figure 4.2

4-7

4-8 Opening the Old Model

4-8

When you start Flarenet, the Flarenet Desktop will appear:

Note that this view has been resized; your Desktop view should appear larger than this when initially opened. To re-size the view, click and drag the outside border. To make the view full size, press the Maximize button in the upper right hand corner.

You do not need to change the setting on the Preference Editor view since the stored case has its own setting.

4.3 Opening the Old ModelTo open the previously stored case:

• Select Open from the File menu on the main program menubar.

• Press the Load An Existing Model From Disk button.• Press <Ctrl><O> .

Figure 4.3

Maximize button


The Open Flarenet Model view will appear.

4. Use the Look in drop-down menu to select the appropriate disk drive and directory.

5. Next select the file named step1c.fnw from the list and press the Open button.

This will open the Step1c.fnw case and any open view will display the case data.

4.4 Updating the ModelBefore proceeding any further, you need to do the following modifications to the pipe network:

A large pipe diameter is selected to adjust the network for flow from the new sources.

Figure 4.4

Segment NameDiameter(mm)

Length (m)NominalDiameter(inch)

ScheduleFittingsLoss

ElevationChange (m)

Header 3 50 36 40 0 0

Stack 100 36 40 0 100

Tip 876.3 3

4-9

4-10 Updating the Model

4-10

Now you need to add the new pipe segments to the existing model. But first delete the connection between Tee 1 and Header 3 as follows:

6. Press the Toggle Connect/Arrange Mode button to switch to connect mode and select the connection between Tee 1 and Header 3.

7. Press the Delete button on the keyboard.

To add a tee section after Header 3:

8. Open the Node Manager view.

9. Press the Add button and select the Tee from the pop up list.

Figure 4.5

Figure 4.6

Toggle Connect/Arrange Mode button (Connect Mode)

Toggle Connect/Arrange Mode button (Arrange Mode)


The Tee Editor view will be displayed:

10. Change the default name to Tee 3 in the Name field.

11. Specify the Downstream connection to be Header 3 and select Upstream from the At drop down menu.

12. Move to the Calculations tab and change the Fittings Loss Methods setting to Miller in the drop down menu.

13. Close the Tee Editor property view by pressing Ok button.

14. Press Ok to close the Node Manager view.

Now, you can add two pipe segments to the upstream and branch section of Tee 3 using the Pipe Manager view.

15. Open the Pipe Manager view by selecting Pipes from the Build menu.

Figure 4.7

Figure 4.8

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.

4-11


4-12

16. Press the Add button to add a new pipe segment.

17. Change the default pipe name to Tail Pipe 4.




21. Press Next to add another pipe segment.

22. Change the new pipe segment default name to Header 2.




Figure 4.9

Figure 4.10

After pressing Next, you will noticed that Tail Pipe 4 has been added to the Pipe Manager list.




Notice that three new objects have been added to the PFD view. You can either manually arrange them by clicking and dragging the object icons or let Flarenet does the auto-arrangement by selecting Regenerate from the PFD menu under the View drop down menu.

Now you will add a tee section using the PFD Toolbox.

28. Open the PFD Toolbox view (if it is not displayed) by pressing the Toolbox button

29. Press the Tee button on the Toolbox view.

Since the Edit Objects on Add checkbox is selected, The Tee Editor view will be displayed:

By default the Tee has been named as 7 (or whichever name you see in the Name field), which can be changed to a more appropriate name as follows:

30. Click in the Name field on the Tee Editor view.

31. Delete the default name and type Tee 2 as the new name.

32. Specify Header 2 as the Downstream connection and select Upstream in the At drop down box.

33. Close the Tee Editor view by pressing the OK button.

Now, you can add two pipe segments to the upstream and branch section of Tee 2 using the PFD Toolbox view.

Figure 4.11

PFD Toolbox button

Tee button

4-13


4-14

34. Press the Pipe button to add a new pipe segment.

35. On the Pipe Editor view, change the default pipe name to Tail Pipe 3.




39. Close the Pipe Editor property view by pressing the OK button.

40. Press the Pipe button again to add another pipe segment.

41. Change the new pipe segment default name to Header 1.


43. Specify Tee 1 as the Upstream connection and select Downstream in the At drop down box.


Figure 4.12

Pipe button




Select Data-Pipes from the View drop down menu on the menu bar. The Pipes view displays the data for all of the pipe segments:

You could also check the PFD to ensure that the proper connections

Figure 4.13

Figure 4.14

4-15


4-16

have been made. A portion of the PFD is displayed below:

Figure 4.15


4.5 Defining The Scenarios

You now need to define the data for the new scenarios, the Source 3 Only and Source 4 Only scenarios. The existing model already contains three scenarios which you still be using in this example. To add the new scenarios:

47. Select Scenario from the Build menu on the menu bar.

The Scenario Manager dialog box will be displayed.

48. Click Add on the Scenario Manager. The Clone Scenario From dialog box will be displayed.

Figure 4.16

Figure 4.17

4-17


4-18

49. Select the Source 2 Only scenario from the list.

50. Change the default name to Source 3 Only and enter the data for the Source 3 Only scenario as shown in Figure 4.18.

51. To add a new scenario press Next on the Scenario Editor and select the Source 3 Only scenario from the Clone Scenario From dialog box.

52. Change the default name for the new scenario to Source 4 Only.

53. Enter the data for the new scenario as shown in Figure 4.18.

54. Click OK to close the Scenario Editor view and return to the Scenario Manager, then click OK to close the Scenario Manager.

Figure 4.18

Figure 4.19


4.6 Defining The SourcesYou will now enter the source data for the sources in all scenarios. Since for the first part of the example you will be defining the source compositions in terms of molecular weight, the program preferences must be set to accept the compositions on this basis.

55. Select Preferences from the File menu on the menu bar. The Preferences view will be displayed.

Ensure that Mol. Wt. is selected in the Composition Basis drop down list box on the Defaults tab.

56. Click OK to close the Preferences Editor view.

Figure 4.20

Figure 4.21

4-19

4-20

Before defining a set of source data, you must select the scenario which corresponds to this data. You will start by defining the data for the Default Scenario.

57. Select the Default Scenario scenario. Any open data views would now display data for this scenario.

You can now add the data corresponding to this scenario for the new sources.

58. Select Nodes from the Build drop down menu on the main menu bar (<Alt>< S>).

Figure 4.22

The Mole Fractions are automatically estimated from the Molecular Weight. Because HC is selected from the drop down, only hydrocarbon components will be used to match the Molecular Weight.


The Node Manager dialog box will be displayed:

59. Click Add and select Control Valve from the pop up list.

Figure 4.23

Figure 4.24

4-21


4-22

The Control Valve Editor view will be displayed:

60. Change the default name to Source 3. Select Tail Pipe 3 in the Outlet drop down box and set connection to be at Upstream (of Tail Pipe 3).

61. Move to the Conditions tab and set the Mass Flow as 100000 kg/hr.

62. On the Composition tab, specify the Mol. Wt. to be 30.

Figure 4.25

Figure 4.26


63. Press the Normalise button to calculate an appropriate binary composition.

64. Click Next to add a new source. The node pop up list will again be displayed.

65. Again select Control Valve from and the Control Valve Editor view will be displayed.

66. Name the new source as Source 4 on the General tab.

67. Select Tail Pipe 4 in the Outlet drop down box and set connection to be at Upstream (of Tail Pipe 4).

Figure 4.27

Figure 4.28

4-23


4-24

68. Repeat Step 61 - 63 to add all the information required by the scenario. Specify Mole Wt. to be 35 on the Composition tab.

69. Press the Ok button to close the Control Valve Editor view.

The Node Manager dialog box will now appear as follows:

70. Close the Node Manager view by pressing the OK button.


The Sources data view for the Default Scenario will be displayed:

Figure 4.29

The source name appears as the source name preceded by the plant identifier.

Figure 4.30


You must now add the source data for the other four scenarios.

72. Select the scenarios from the selector on the tool bar. Any open data views will display data for the selected scenario.

73. Make the following changes to the flowrates in all scenarios:

For each scenario, ensure that the sources which have a flowrate of zero are ignored (i.e. select the Ignore check box for the source).

4.7 Sizing The NetworkYou have now entered all the model data and can now make the sizing calculations. You will need to set the calculation options before starting the calculations.

74. Select Options from the Calculation drop down menu on the menu bar. The Options dialog box will be displayed:

75. Enter the data as shown above, then click OK.

Scenarios Source 1 (kg/hr) Source 2 (kg/hr) Source 3 (kg/hr) Source 4 (kg/hr)

Source 1 Only 100000 0 0 0

Source 2 Only 0 100000 0 0

Source 3 Only 0 0 100000 0

Source 4 Only 0 0 0 100000

Figure 4.31

4-25

4-26 Sizing The Network

4-26

The options are explained below:

OptionDefault

SettingDescription

Max Iterations25 The maximum number of iterations.

The calculations will stop if this limit isreached.

PressureTolerance

0.01% When the difference in pressurebetween successive iterations is lessthan this tolerance, convergence isassumed.


1% This is the solution tolerance for theiterative mass balance performedduring looped system calculations.

DampingFactor

1 The damping factor used in the iterativesolution procedure.

AtmosphericPressure

1.01325 barabs

Specify the atmospheric pressure.

AmbientTemperature

15o C The Ambient temperature must be inthe range -100oC to 100oC.

Wind Velocity 10 m/s The average wind velocity.

LengthMultiplier

1 The length of the pipe is multiplied bythis value to determine the equivalentlength used for the pressure dropcalculation.

CalculationMode

Rating Select the Calculating Mode from thedrop down menu. The available optionsare:

• Rating - It is used to check the existingflare system in a plant. This methodcalculates the pressure profile for theexisting pipe network.

• Design - It is used to design new flaresystem for the plant. During calculationit adjust the diameters of all pipes untilall the design constraints of MABP,velocity and etc. have been meet.These diameters can be smaller thanthe initially defined data.

• Debottleneck - It is used to determineareas of the flare system that must beincreased in size due to either theupgrading of the existing plant andhence flare loading, or the tie-in of newplant.


Loop Solver

Newton-Raphson

These algorithms provides globallyconvergent methods for nonlinearsystems of equations. The methodsavailable are:

• Broyden - It provides a quicker solutionsince it does not have to calculateJacobian matrix. You need to providebetter guesses for the tear pipe flows.

• Newton-Raphson - It works morereliably if default initial guesses areused but takes a longer time.


OFF If checked, the rated flow will be usedin the sizing calculations for thetailpipes (as opposed to the actualflowrates). The API guide for Pressure-Relieving and Depressuring Systemsrecommends that tailpipes be sizedbased on the rated capacity

Enable HeatTransfer

OFF If checked, heat transfer can take placebetween the pipe segment and thesurroundings for pipe segments whichhave Heat Transfer with Atmosphereenabled.

All Scenarios

OFF If checked, the calculations will bemade for all the scenarios defined inthe model, otherwise the calculationswill be made only for the scenariowhich is currently displayed.

When sizing calculations are made fora number of scenarios simultaneously,a single network is calculated that willsatisfy the design constraints for allscenarios.

Choked FlowCheck

ON If left unchecked, velocities will not belimited to the sonic condition. This isuseful in sizing calculations since themach number limitations will still be metby the time the final solution is reached.Calculation speed is greater at the riskof numerical instability andconvergence failure.

Echo SolverHistory

OFF When checked, it should enableprinting of much more intermediateinformation during calculations. Thisshould be left unchecked unless youhave convergence problems.

ForceConvergentSolver

OFF Check if you are modelling aconvergent flare system, but with 2flare tips as commonly found onoffshore floating production facilities.

OptionDefault

SettingDescription

4-27

4-28 Sizing The Network

4-28

You can now start the calculations.

76. Select Calculate from the Calculation drop down menu on the menu bar (<Alt>< C>< C> or <Ctrl><R>). Alternatively, you could select the Calculations button.

Note that the current calculation is shown on the status bar:

Once the calculations are complete you can review the results.

Figure 4.32Calculations button

Figure 4.33

Note that red text is used for non resizable pipe segments, and magenta is used for resized pipe segments.


77. Select Results-Problems from the View drop down menu on the menu bar. The Messages data view will be displayed.

This window contains general information and warning messages regarding the calculations. In this case the mach number exceeds the design value of 0.5, which was defined for each scenario, for Tail Pipe 1 and Tail Pipe 3. It also shows both upstream and downstream pipe segment mach number for each violation. It is due to smaller pipe segments causing very high fluid velocities across the pipe segment.

At this point, it is a good idea to save your case before doing detail design.

78. Select Save As from the File menu and save the file as Get Started 2 Rating.fnw

Figure 4.34

4-29

4-30 Rigorous Rating

4-30

4.8 Rigorous RatingThe system will now be rated taking into account the appropriate pipe sizes.

79. Select Options from the Calculation drop down menu on the menu bar. The Calculation Options Editor dialog box will be displayed:

80. Change the Calculation Mode to Design and press the OK button to close the Calculation Options Editor view.

You can now start a detail design calculation.

81. Select the Start Calculation button on the button bar.

Notice that the status bar will display the current calculation.

Figure 4.35

Figure 4.36

After the calculation have been completed, you can review the new results.

82. Press the Open Pipe Tabular View button on the button bar.

The Pipes view shows the data for all the pipe segment in the current scenario.

Notice that Flarenet has selected the appropriate nominal diameter for the pipe segments in the network.

83. Select Results - Pressure/Flow Summary from the View menu on the menu bar.

The Pressure/Flow Summary view will be displayed:

Notice that the upstream and downstream mach number are now within the design specification for the given scenario. You can use the bottom scroll bar to move across the columns.

84. Press <Ctrl><A> to save the case. as a new file.

85. Enter the new file name as Get Started 2 Design.fnw on the Save Flarenet Model view and press the Save button.

Open Pipe Tabular View button

Figure 4.37

Figure 4.38

4-31

4-32 Printing Data And Results

4-32

4.9 Printing Data And Results

To print data and results:

86. Select Print from the File drop down menu on the menu bar. The Print dialog box will be displayed.

87. Click on the appropriate check boxes to select the items that you wish to print. Also check the All Scenarios box to print the results for all of the scenarios instead of just the current scenario. If you want to print to a file, check the Print To Text File box, then select the file type from the Text File Type drop down.

88. Click OK.

This case is available for review in Get Started 2 Rating.fnw (model before detail design) and Get Started 2 Design.fnw (model after detail design) which are stored in the \Samples sub-directory under the main program directory.

Interface 5-1

5 Interface

5.1 Terminology .................................................................................................. 3

5.2 Menu Bar ....................................................................................................... 5

5.3 Tool Bar ......................................................................................................... 6

5.4 Status Bar ..................................................................................................... 8

5.5 Editing Data Views ....................................................................................... 9

5.5.1 Changing Column Width .......................................................................... 95.5.2 Changing Column Order ........................................................................ 10

5.6 Setting Preferences.................................................................................... 12

5.6.1 General Tab............................................................................................ 125.6.2 Defaults Tab ........................................................................................... 145.6.3 Databases Tab ....................................................................................... 155.6.4 Reports Tab............................................................................................ 155.6.5 Import Tab .............................................................................................. 16

5.7 Windows Menu ........................................................................................... 16

5.8 Help Menu ................................................................................................... 16

5-1

5-2

5-2

Interface 5-3

The FLARENET interface has been designed to give you a great deal of flexibility in the way in which you enter, modify and view the data and results which comprise your model of a flare system. This chapter describes the various components of the FLARENET interface. If you need help with any particular task, the on-line help can give you step-by-step instructions.

5.1 TerminologyThe following view of the FLARENET screen shows most of the interface components that you will encounter. The terminology used to describe these components throughout this manual is given here.

Figure 5.1

Menu Bar

Tool Bar

Scenario Selector

Data View

Check box

Edit Box

Title Bar

Button

FLARENETDesktop Area

Status Box

Drop DownList Box

Scroll Button

Dialog Box Scroll Bar

Tool Tip

Modal/Non-ModalView

5-3

5-4 Terminology

5-4

Term Definition

Button

Most views contain buttons. They perform aspecific action when selected (either by clickingthe left mouse button or via the appropriate hotkey combination).

Check BoxData items or settings that have an On/Off statusare indicated by Check Boxes. Selecting the boxwill turn it on, selecting it again will turn it off.

Data View A window that contains a non-editable view ofthe model data and/or the calculation results.

Dialog Box

A modal window which allows you to enter themodel data. You cannot access any otherelement in the model until this form has beenclosed.

Drop Down List BoxA drop down list is indicated by a down arrownext to a field. If you click on this arrow, a list ofavailable options for that field will be displayed.

Edit Box

Data items that are alphanumeric in nature areentered into an Edit Box. In general, the data thatis entered in an Edit Box is checked for validitybefore you can continue.

Menu Bar

The Menu Bar displays all of the programfunctions, which can be accessed by clicking onthe appropriate menu item. This is described inmore detail later in the chapter.

Modal/Non-Modal View

When a view is modal, you cannot access anyother element in the simulation until you close it.Non-modal views do not restrict you in thismanner. You can leave a non-modal view openand interact with any other view or menu item.

Scenario Selector

This drop down list box shows the currentscenario selected for the case. On clicking thedown arrow, located beside the field, a list of allthe scenarios will be displayed.

Scroll Bar

Whenever the information associated with a viewor list exceeds what can be displayed, you maymove through the view or list by using the scrollbar.

Scroll Button Part of the Scroll Bar, allowing you to slide the listup or down, or left or right.

Status Bar This displays the current model status. For moreinformation, see Section 5.4 - Status Bar .

Title Bar Indicates the Flarenet file currently loaded.

Tool Bar

The Tool Bar contains a number of controls(buttons) which give shortcut access to the mostcommonly used program functions. This isdescribed in more detail later in this chapter.

Tool Tip

Whenever you pass the mouse pointer over oneof the buttons on the Tool Bar, a Tool Tip will bedisplayed. It will contain a summary description ofthe action that will take place if you click on thatbutton.

Note that throughout this manual whenever any reference is made to clicking on a button or menu item, unless otherwise specified it refers to the left mouse button.

A modal view is characterised by a single border and the absence of the minimise/maximise buttons in the upper right-hand corner of the view. A non-modal view has a double border, and has the minimise/maximise buttons.

Interface 5-5

5.2 Menu BarThe menu bar allows access to all the program functions via menus and sub-menus.

The menu bar contains commands for each of the main areas of program functionality:

Figure 5.2

Menu Sub-menu

Menu Description

File

Work with files (New, Open, Save), supply CaseDescription, import/export files, print, adjustprinter setup, and set preferences. Also a list ofpreviously opened cases are displayed at thebottom of the drop down menu.

Build Access the Managers for Components,Scenarios, Pipes and Nodes.

ToolsAccess various FLARENET utilities (see Section8.2 - Scenario Tools , Section 9.5 - Pipe Tools ,and Section 10.3.2 - Source Tools ).

Calculations Set calculation options and start calculations.

DatabaseManage the pipe schedule, pipe fittings, purecomponent databases and allows you to set apassword.

View Look at summaries of the Data, the Results, andthe Process Flow Diagram (PFD).

5-5

5-6 Tool Bar

5-6

As an alternative to using the mouse to click on the menu item, you can hit the <Alt> key, then the underlined letter key. For example, to import source data from the HYSIM process simulator as shown above you would hit the <Alt> key, and then while holding down the <Alt>, hit the <F>, and <H> keys in sequence (abbreviated as <Alt><F><H>).

5.3 Tool BarThe Tool Bar contains a set of controls which give shortcut access to some of the program functions without the need to navigate through a series of menus and/or sub-menus.

Windows Arrange the display of windows (Cascade, Tile,etc.)

Help Access on-line help and program versioninformation.

Menu Description

Button View Description

New CaseStarts a new case.

Load CaseOpens a case that has beenpreviously saved to disk.

Save Case

Saves a case to disk using thecurrent file name. If you wish tosave the case with a different filename, use the Save As commandin the File menu.

Print Data andResults

Opens a Print view, which allowsyou to print the entries from theDatabase, Data and Resultsgroups. You can either print to aprinter or to a file.

Display MetricUnits

Displays data and results in Metricunits.

Display BritishUnits

Displays data and results in Britishunits.

Display PFDDisplays the Process FlowDiagram .

Interface 5-7

Display PipeData View

Displays the Pipe data view.

Display SourceData View

Displays the Source data view.

Display NodeData View

Displays the Node data view.

Open Pressure/Flow SummaryView

Displays the Pressure/FlowSummary view.

Open ProfileGraphical View

Displays the graphical Profile view.

StartCalculations

Starts the FLARENET calculations.

StopCalculations

Stops the FLARENET calculations.

ScenarioSelector

This drop down list box show thecurrent scenario selected for thecase. On clicking the down arrow,located beside the field, a list of allthe scenarios will be displayed.


The Tool Bar can be hidden by unchecking the Show Toolbar check box in the Preferences view.

5-7

5-8 Status Bar

5-8

5.4 Status Bar

The status bar displays the current status of the model. There are two general regions in the status bar:

• The first region displays the program status - If Edit isdisplayed, you can make changes to your model. Duringcalculations, this field will display Calc .

• The second region displays important information duringcalculations, such as the iteration error and the current pipebeing solved.

Figure 5.3

Status Bar(first region)

Status Bar (second region)

The calculation time can be reduced by hiding the status bar, which is particularly useful for large cases.

The Status Bar can be hidden by unchecking the Show Status Bar check box in the Preferences view.

Interface 5-9

5.5 Editing Data ViewsYou can change the position and width of some of the columns in each of the data views such as the Pressure/Flow Summary view.

5.5.1 Changing Column WidthTo change the width of a column, move the mouse pointer until it is over the vertical column separator line to the right of the column that you wish to resize (e.g. - Flowrate). The mouse pointer will change to a double-headed arrow.

Click and hold down the primary mouse button, then drag the separator line to the new position.

The column width set here remains in effect for the duration of the current session and is saved when you exit FLARENET.

Figure 5.4

Figure 5.5

Mouse pointer turneddouble-headed arrow.

5-9

5-10 Editing Data Views

5-10

5.5.2 Changing Column OrderTo reposition columns, first select the columns by positioning the mouse pointer in the column heading(s) (you will see a down arrow), then clicking. The column heading will now be shaded.

Now click anywhere in the shaded region and hold down the primary mouse button. The move column cursor will be shown, and there will be a heavy vertical line to the left of the column which contains the cursor. While holding down the mouse button, drag the column(s) to their new position. The heavy vertical line will move as you drag the column(s) and indicates where the selected column(s) will be transferred. In this case, the Mass Flowrate and the Molar Flowrate columns will be positioned between the Rated Flowrate and the Pressure Drop columns.

Release the mouse button. The selected column(s) will remain in their

Figure 5.6

Figure 5.7

Select column cursor

Column movecursor

Heavy VerticalLine

Interface 5-11

new location within the data view.

The change in column order remains in effect for the duration of the current session and is saved when you exit FLARENET.

Figure 5.8

Note that you can highlight multiple columns by clicking and dragging the mouse over the adjacent columns you wish to select. Alternatively, you could hold the <Shift> key and click on the additional adjacent columns you wish to select.

5-11

5-12 Setting Preferences

5-12

5.6 Setting PreferencesThe Preferences view allows you to specify default information for the simulation case.

To access the Preferences view, select Preferences from the File menu (<Alt>, F, P). The Preferences view will be displayed.

The information on the preference view is divided into different tabs: General, Defaults, Databases, Reports and Import tab.

5.6.1 General Tab

The following options are available on the General tab.

Figure 5.9

Options Description

Show Status Bar Select this check box to display the Status bar.

Show Tool Bar Activate this checkbox to display the Tool bar.

Timed BackupSelect this check box to activate a periodicallybackup of the current case. File is saved back tothe directory as Backup.fnw.

Backup FrequencyThis edit box is only accessed if the TimedBackup check box is selected. The default valueis 10 minutes.

Compress FilesIf checked, the data files will be saved in acompressed format that can reduce the file sizeof the saved cases by a factor of up to 50.

Interface 5-13

Edit Objects On AddOn activating this checkbox, the editor view willbe displayed as the nodes/pipes are added to thePFD.

UnitsSpecify the units set to be used for thesimulation. The available unit sets are Metric andBritish .

Work Directory Specify the directory for temporary files, whichshould be writable.

Auto Flash SourceNodes

Activate the Auto Flash Source Nodes checkbox to automatically flash the source fluid when itis edited. Otherwise sources are flashed duringthe calculation.

Display Total Pressure

Select this check box to display the totalpressure, which is a sum of the static pressureand the velocity pressure, instead of the staticpressure.

Save Phase Properties

Phase properties can be saved by activating thischeckbox. The disk space/memory requirementsare significantly effected by this option, speciallyfor large cases. It is advised to select this optiononly if you have a high specification PC.

Options Description

5-13

5-14 Setting Preferences

5-14

5.6.2 Defaults Tab

The options available on this tab are:

Figure 5.10

The default data values given on the Default tab applies only to new instances of pipe class of pipes and nodes. The value for each instance may be freely edited at any stage.

Options Description

Composition Basis

Select composition basis for each of the reliefsources:

• Molecular Weight - The molecular weight ofthe fluid is given. Mole fractions areestimated by FLARENET, based upon thelist of installed components.

• Mole/Mass Fractions - A full component-by-component composition must be givenfor the fluid.

Tee TypeSelect the tee type to be set as a default for allthe tees in the model. The available tee types are90o, 60o, 45o and 30o tee.

Pipe MaterialThis is the default material to be used in newpipes. The two material available for selection areCarbon Steel and Stainless Steel .

Use Pipe Class Activate this check box to use the pipe class torestrict the available uses for pipes.

CS/SS RoughnessSet the material roughness to be used incalculation. The default CS Roughness is0.04572 mm and SS Roughness is 0.02540 mm.

CS = Carbon Steel

SS = Stainless Steel

Interface 5-15

5.6.3 Databases Tab

You can specify the directories where the Components, Pipe Schedules and Pipe Fittings database are stored.

5.6.4 Reports Tab

You can specify the directories in which to save the report definition for each of the entries in the Report list. This allows you to maintain a range of alternative report definitions for each type of report.

Figure 5.11

Figure 5.12

5-15

5-16 Windows Menu

5-16

5.6.5 Import Tab

Specify the sizing factor to be used by the FLARENET to scale the PFDs created in earlier versions.

5.7 Windows MenuThis is a general Windows application function. The options are:

5.8 Help MenuThe options under the Help menu are:

Figure 5.13

Option Description

Cascade Cascade all currently-open windows.

Tile Horizontally Tile all currently-open windows horizontally.

Tile Vertically Tile all currently-open windows vertically.

Arrange Icons Organise icons at the bottom of the screen.

Open All Open all the windows, which can be accessedthrough the View menu bar

Close All Close all windows.

Option Description

Contents Displays the FLARENET Help contents.

Using Help Displays the general Windows Help on usingHelp.

Technical Support Displays a list of world wide Technical Supportoffices.

About Provides information about FLARENET.

Creating and Saving Cases 6-1

6 Creating and Saving Cases

6-1

6.1 Creating A New Case ................................................................................... 3

6.2 Opening An Existing Case .......................................................................... 4

6.3 Saving A Case .............................................................................................. 5

6-2

6-2

6.1 Creating A New CaseTo start a new case, do one of the following:

• Select New from the File menu in the menu bar.• Use the hot key combination <Alt><F><N> .• Click on the New Case button in the button bar.

The Case Description view will be displayed.

Enter appropriate data into the User Name, Job Code, Project, and Description fields and then click the OK button.

After you enter the case description information, the Component Manager view appears as shown on the next page.

Figure 6.1

Figure 6.2

When you start FLARENET, a new case is automatically created.

New Case Button

The case description can later be modified by selecting Description from the File menu.

6-3

6-4 Opening An Existing Case

6-4

Select the desired components as described in Chapter 7 - Components and click OK. You can now set up the simulation.

6.2 Opening An Existing Case

When you open a case that has previously been stored on disk, all data from the current case is cleared; however, the arrangement of any windows that are already open is maintained.

To open an existing case, do one of the following:

• Select Open from the File menu.• Use the hot key combination <Alt><F><O> .• Press the Load Case button on the button bar.

The File Open view appears.

Select the file to be opened by doing one of the following:

• Type the file name (including exact directory path if necessary)into the Filename field and click the OK button.

• Search the directory using the Look in drop-down menu andupon finding the file, click once on the file name to highlight itand then click the OK button.

• Search the directory using the Look in drop-down menu andupon finding the file, double click on the file name.

Figure 6.3

Load Case Button

6.3 Saving A CaseCases may either be saved using the current case name or under a new name.

To save a case using the current file name, do one of the following:

• Select Save from the File menu.• Use the hot key combination <Alt><F><S> .• Click on the Save Case button on the button bar.

To save a case using a new name, do one of the following:

• Select Save As from the File menu.• Use the hot key combination <Alt><F><A> .

When you’re saving the case for the first time or with a new name, the Save Flarenet Model view will appear as shown on the next page.

Clear the Filename field, type in the file name you want to give to the case in and click on the OK button. Note that you do not have to include the .fnw extension. FLARENET will add it on automatically.

Figure 6.4

Save Case Button

Select the file to be saved by directly entering it, or selecting the appropriate file in the list box in the view which contains all the files and folders. The Save in drop-down menu can be used to change the directory and/or drive.

6-5

6-6 Saving A Case

6-6

Components 7-1

7 Components

7-1

7.1 Selecting Components ................................................................................ 3

7.1.1 Component Types .................................................................................... 37.1.2 Component List ........................................................................................ 47.1.3 Matching the Name String ....................................................................... 47.1.4 Removing Selected Components............................................................. 5

7.2 Adding/Editing Components....................................................................... 5

7.2.1 Add Hypothetical Component/Edit Component View............................... 57.2.2 Estimating Unknown Properties............................................................... 8

7.3 Organizing the Component List.................................................................. 9

7.3.1 Sorting the Component List ..................................................................... 97.3.2 Swapping two components ...................................................................... 97.3.3 Changing the Components ...................................................................... 9

7-2

7-2

Components 7-3

Data for all components that will be used in the simulation must be selected before the sources are defined. These components may be taken from the standard component library, or you may define your own components (hypothetical).

You may select components from the Component Manager, which can be accessed by selecting Components from the Build menu.

The Component Manager view will be displayed:

This view displays all of the Database and Selected components, and provides various tools which you can use to add and edit database and hypothetical components.

7.1 Selecting Components

7.1.1 Component TypesYou may filter the list of available components to include only those belonging to a specific family. The All and None buttons turn all of the filters on and off, respectively, while the Invert button toggles the status of each check box individually. As an example, if only the Hydrocarbons (HC) and Misc options were on, and you pressed the Invert button, then these two options would be turned off, and the remaining options would be turned on.

Figure 7.1

7-3

7-4 Selecting Components

7-4

7.1.2 Component ListComponents can be chosen from the Database list, and added to the Selected group, using one of the following methods:

• Arrow Keys - The <> or < > arrow keys move the highlightup one component, and the < > or < > arrow keys move thehighlight down one component.

• PageUp/PageDown - Use these keyboard keys to advance anentire page forward or backward.

• Home/End - The <Home> key moves to the start of the list andthe <End> key moves to the end of the list.

• Scroll Bar - With the mouse, use the scroll bar to move up anddown through the list.

• Enter a character - When you type a letter or number, you willmove to the next component in the list which starts with thatcharacter. If you repeatedly enter the same character, you willcycle through all of the components which start with thatcharacter.

To add a component, you must first highlight it (by moving through the list until that component is highlighted), then transfer it by double-clicking on it or selecting the Add button.

7.1.3 Matching the Name StringAnother way to add components is through the Selection Filter feature. The Selection Filter cell accepts keyboard input, and is used to locate the component(s) in the current list that best matches your input.

You may use wildcard characters as follows:

• ? - Represents a single character.• * - Represents a group of characters of undefined length.• Any filter string has an implied '*' character at the end.

Some examples are shown here:

Note that you cannot highlight multiple components to add to the Selected list.

The interpretation of your input is limited to the Component Types which are checked.

As you are typing into the Selection Filter cell, the component list is updated, matching what you have presently typed. You may not have to enter the complete name or formula before it appears in the component list.

Filter Result

methan methanol, methane, etc.

*anol methanol, ethanol, propanol, etc.

?-propanol 1-propanol, 2-propanol

*ane methane, ethane, propane, i-butane, etc.

Components 7-5

7.1.4 Removing Selected Components

You can remove any component from the Selected component list:

1. Highlight the component(s) you wish to delete. Note that you may select multiple components by using the <Shift> and <Ctrl> keys.

2. Press either the Delete button on the Component Manager view, or the <Delete> key.

Once the component(s) are removed from the list, any source compositions that used this component will be normalised.

7.2 Adding/Editing Components

To edit a component, highlight it in the Selected Component list, and click the Edit button.

To create a new component (hypothetical), select the Hypothetical button. Hypothetical components are set up in the same manner as database components.

To clone a component, edit it, then change its name. Be careful not to enter a component name that is already in the database.

7.2.1 Add Hypothetical Component/Edit Component View

Upon clicking either the Hypothetical button or the Edit button the Component Editor view opens up. This view is similar between adding a new hypothetical component and editing an existing component.

The Component Editor view for Methane is shown in Figure 7.2:

7-5

7-6 Adding/Editing Components

7-6

Identification Tab

You can enter the following information on this tab:

Figure 7.2

Input Field Description

Name An alphanumeric name for the component (e.g. -Hypo -1 ). Up to 15 characters are accepted.

Type

The type of component (or family) can beselected from the drop-down menu provided.There is a wide selection of families to choosefrom, which allows better estimation methods tobe chosen for that component.

ID The ID number is provided automatically for newcomponents and cannot be edited.

Mol. Wt. The molecular weight of the component. Validvalues are between 2 and 500.

NBP The normal boiling point of the component.

Std. Density The density of the component as liquid at 1 atmand 60 F.

Watson K The Watson characterisation factor.

Component Types:

• Hydrocarbon• Miscellaneous• Amine• Alcohol• Ketone• Aldehyde• Ester• Carboxylic Acid• Halogen• Nitrile• Phenol• Ether

Components 7-7

Critical Tab

The following fields are available on the Critical tab:

Figure 7.3


Critical Pressure

The critical pressure of the component. If thecomponent represents more than a single realcomponent, the pseudo critical pressure shouldbe used. Valid values are between 0.01 bar absand 500 bar abs.

Critical Temp.

The critical temperature of the component. If thecomponent represents more than a single realcomponent, the pseudo critical temperatureshould be used. Valid values are between 5 Kand 1500 K.

Critical Volume

The critical volume of the component. If thecomponent represents more than a single realcomponent, the pseudo critical volume should beused. Valid values are between 0.001 m3/kg and10 m3/kg.

Acentric Factor The acentric factor of the component. Validvalues are between -1 and 10.

Acentric Factor (SRK)The Soave-Redlich-Kwong acentric factor of thecomponent (also called the COSTALDAcentricity).

7-7

7-8 Adding/Editing Components

7-8

Other Tab

You can specify the following information:

7.2.2 Estimating Unknown Properties

If any of the above data is unknown, then click Estimate to fill-in the unknown properties.

Supply as many properties as are known, so that the estimation can be as accurate as possible.

Figure 7.4


Hi A, Hi B, Hi C, Hi D, HiE, and Hi F

The coefficients for the ideal gas specificenthalpy equation:

Hi = A + BT + CT2 + DT3 + ET4 + FT5

Entropy Coef. The coefficient for the entropy equation.

Vicosity A andViscosity B

Viscosity coefficients used in the NBS Method(Ely and Hanley, 1983).

At the very minimum, you need to specify the Molecular Weight. However, it is a good practise to specify at least two of the following properties defined:

• Molecular Weight• Normal Boiling Point• Standard Density

Components 7-9

7.3 Organizing the Component List

The Selected Components list can be organized in different ways. You can either swap any two components or sort the whole list by Name, Molecular Weight, NBP or Group.

7.3.1 Sorting the Component ListComponents can be sorted in the following ways:

7.3.2 Swapping two componentsIn the Component Manager view, select the first component in the Selected Component list by clicking on it. Then select the second component either using the <Shift> key if the two are in sequence or pressing the <Ctrl> key and then clicking on the component. Swap the two components by pressing the Swap button.

7.3.3 Changing the ComponentsYou can switch the components in the Selected Component list with the ones in the Database list while maintaining the source mole fractions.

In the Component Manager view, select the components in both the Selected Components and the Database lists. Press the Change button to switch the two components.

Sorting Option Description

Name Arranged components alphabetically indescending order.

Molecular Weight Components are listed according to increasingmolecular weight.

Normal Boiling Point(NBP)

Select this to arrange components in increasingNBP value.

Group Group the components by type.

7-9

7-10 Organizing the Component List

7-10

Scenarios 8-1

8 Scenarios

8-1

8.1 Adding/Editing Scenarios............................................................................ 5

8.1.1 General Tab.............................................................................................. 58.1.2 Headers and Tailpipes Tabs ..................................................................... 68.1.3 Sources Tab ............................................................................................. 78.1.4 Estimates Tab........................................................................................... 7

8.2 Scenario Tools.............................................................................................. 8

8.2.1 Adding Single Source Scenarios ............................................................. 8

8-2

8-2

Scenarios 8-3

A scenario defines a set of source conditions (flows, compositions, pressures and temperatures) for the entire network. The design of a typical flare header system will be comprised of many scenarios for each of which the header system must have adequate hydraulic capacity. Typical scenarios might correspond to:

• Plantwide power failure.• Plantwide cooling medium or instrument air failure.• Localised control valve failure.• Localised fire or Depressurisation.

The scenario management features within FLARENET allow you to simultaneously design and rate the header system for all of the possible relief scenarios.

As well as having different source conditions, each scenario can have unique design limitations that will be used either to size the pipes or to highlight problem areas if any existing flare system is being rated. For example, a Mach number limit of 0.30 might be applied for normal flaring compared to a Mach number limit of 0.50 or greater at the peak flows encountered during plant blowdown.

Scenarios are managed via the Scenario Manager view. This view has buttons that allow you to add, edit or delete scenarios as well as to select the current scenario for which scenario specific data is displayed. All cases have at least one scenario.

To access the Scenario Manager view, select Scenarios from the Build menu.

Although the major relief scenarios will normally constrain the size of the main headers, care should be taken in the evaluation of velocities in the individual relief valve tailpipes and sub headers. When looking at relief valves which might operate alone, lower back pressures in the main headers may lead to localised high velocities and consequently choked flow in the tail pipes.

Scenarios can also be selected by selecting the scenario in the scenario selector on the tool bar.

8-3

8-4

8-4

The Scenario Manager view will be displayed.

The Scenario Manager view displays all Scenarios in the case, and indicates the Current Scenario. Several buttons are available:

Figure 8.1

Button Description

Add Adds a new scenario (See Adding/EditingScenarios below).

Edit Edits the highlighted scenario (See Adding/Editing Scenarios below).

DeleteRemoves the currently highlighted scenario (notethat there must always be at least one scenario inthe case).

Sort Arrange the scenario list alphabetically indescending order.

Up and Down Arrow Move the highlighted scenario up and down theScenario list.

Swap Swap the two selected scenarios in the list.

CurrentTo make a scenario the current one, highlight theappropriate scenario, and then click on theCurrent button.

OK Closes the Scenario Manager view.

Scenarios 8-5

8.1 Adding/Editing Scenarios

To add a scenario, click the Add button on the Scenario Manager view. If there is already a scenario present in the Scenario list, pressing the Add button will show a Clone Scenario Form dialog box. You can select an existing scenario from the list to be used to initialise the flows, compositions, pressures and temperatures of all the sources in the new scenario.

To edit a scenario, highlight it, then click the Edit button. For adding and editing a scenario, the views are similar except for the Next button on the Scenario Editor view for adding a scenario.

8.1.1 General Tab

You may provide the following information on the General tab:

Figure 8.2

FLARENET has no pre-programmed limits on the number of scenarios which can be defined within a single case.

The Next button allows you to continue adding scenarios without returning to the Scenario Manager.

Data Description

NameAn alphanumeric description of the scenario (e.g.Power Failure ). Up to 40 characters areaccepted.

System Back Pressure

The system back pressure at the flare tip exit.This will normally be atmospheric pressure, butcan be set to represent system design conditionsat the exit point. If left empty, the value on theCalculation Options Editor view will be used.The minimum value is 0.01 bar abs.

8-5

8-6 Adding/Editing Scenarios

8-6

8.1.2 Headers and Tailpipes Tabs

The Headers and Tailpipes tabs required the following information:

Figure 8.3

Data Description

Mach NumberThe maximum allowable Mach number for allpipe segments. Calculated values that exceedthis number will be highlighted in the results.

Vapour VelocityThe maximum allowable vapour velocity.Calculated velocities that exceed this value willbe indicated in the results.

Liquid VelocityThe maximum allowable liquid velocity.Calculated velocities that exceed this value willbe indicated in the results.

Rho V2It is the density times the velocity square. Thisvalue is normally used as a limiting factor toprevent erosion.

Design Noise at 1m

The maximum allowable sound pressure level ata distance of 1 metre for all pipe segments. Thisis an average value over the length of the pipe.Calculated values that exceed this specificationwill be highlighted in the results.

You may provide different design information (Mach Number, Noise at 1 m, Vapour Velocity, Liquid Velocity) for the Main Headers and Tailpipes.

Any field may be left empty, in which case they will be ignored.

You may define an allowable Mach number of 1.00 within a network, in order to highlight only choked flow conditions. It is recommended that you use a more reasonable value such as 0.5 or 0.7. This will obtain a more rapid solution towards maximum allowable back pressure constraints when performing sizing calculations.

Scenarios 8-7

8.1.3 Sources TabWhen you select the Sources tab, you will see a view similar to the one shown in Figure 8.4. All sources are displayed on this tab (note that if you are setting up a new case, this view will not show any sources).

This tab is useful in that you can easily toggle whether or not individual sources are to be included in the current scenario, without having to either unnecesarily delete sources or set the flow of a source to zero.

8.1.4 Estimates TabYou can specify molar flow estimates for any pipes that you wish on the Estimates tab. These are only required if looped models fail to converge. You do not have to specify them all, only the ones that match the tear pipes for which you solve the flow in the looped systems.

Figure 8.4

Figure 8.5

If a source is ignored, the MABP constraint is ignored by sizing calculations.

8-7

8-8 Scenario Tools

8-8

8.2 Scenario ToolsThe complete analysis of a flare system should ideally include analysis of the system for the scenarios in which each source relieves on its own. For a large network with many sources, it can become tedious to define each of these scenarios. These can automatically be added to your model as follows.

8.2.1 Adding Single Source Scenarios

Select Add Single Source Scenarios from the Tools menu or use the hot key combination <Alt><T><N>.

This will analyse your model and add a scenario for each source that has a non-zero flowrate defined in at least one scenario. Source data will be copied from the scenario in which it has the highest flowrate.

Scenarios 9-1

9 Scenarios

9-1

9.1 Adding/Editing a Pipe .................................................................................. 3

9.1.1 Connections Tab ...................................................................................... 39.1.2 Dimensions Tab........................................................................................ 49.1.3 Fittings Tab............................................................................................... 69.1.4 Heat Transfer Tab..................................................................................... 7

9.2 Methods Tab ................................................................................................. 8

9.2.1 Multiple Editing....................................................................................... 10

9.3 Ignoring/Restoring Pipes........................................................................... 11

9.4 Arranging Display Order............................................................................ 12

9.5 Pipe Tools ................................................................................................... 13

9.5.1 Pipe Class Editor ................................................................................... 13

9-2

9-2

Scenarios 9-3

9.1 Adding/Editing a PipeTo add a pipe, click the Add button on the Pipe Manager view. To edit a pipe segment, highlight it, then click the Edit button. You can also edit the pipe segment through the PFD, by double clicking on it’s icon. For both adding and editing pipes the views are identical and it is called Pipe Editor. The tabs available on the Pipe Editor view are Connections, Dimensions, Fittings, Heat Transfer and Methods tabs.

9.1.1 Connections Tab

You may provide the following data in the Connections tab:

To ignore the pipe segment during calculations, select the Ignore check box. Flarenet will completely disregard the pipe until you restore it to an active state by clearing the check box.

Figure 9.1

FLARENET has a limit of approximately 30000 pipe segments that can be defined within a single case.

Input Data Description

Segment Name An alphanumeric description of the pipesegment. Up to 30 characters are accepted.

Location

An alphanumeric description of the locationwithin the plant for the segment. This is a usefulparameter for grouping pipes together via theSort command.

UpStream NodeAn integer number to represent the upstream endof the pipe segment. Valid values are between 1and 30000.

DownStream NodeAn integer number to represent the downstreamend of the pipe segment. Valid values arebetween 0 and 30000.

9-3

9-4 Adding/Editing a Pipe

9-4

You have the option of modelling the current segment as a main header or a tailpipe. If this box is checked, the segment is considered to be a tailpipe. Note that in the Scenario Editor view, you can set the Mach Number, Vapour and Liquid Velocities, Rho V2 and Noise for both the main headers and the tailpipes (See Section 8.1 - Adding/Editing Scenarios).

The ability to classify a pipe as either a tailpipe or a header allows us to perform calculations in which the pressure drop for tailpipes is determined by the rated flow and that for headers is determined by the nominal flow. This is in accordance with API-RP-521.

9.1.2 Dimensions Tab

Enter the following information in the Dimensions tab:

Figure 9.2


Length

The physical length of the pipe segment. Thislength is used in association with the fittings losscoefficients to calculate the equivalent length ofthe pipe. If you have equivalent length data foryour network, enter this data here as the sum ofthe actual length plus the equivalunt length of thefittings and enter zero for the fittings losscoefficients.

Elevation Change A positive elevation indicates that the outlet ishigher than the inlet.

Material The pipe material, either Carbon Steel orStainless Steel.

Scenarios 9-5

If you wish the pipe segment to be resized by sizing calculations, Sizeable check box should be checked. For example, a model of a network containing a representation of the knockout drum as a pipe segment would normally leave this unchecked such that sizing calculations for the pipes would not change the knockout drum size.

Select the Use Pipe Class check box to restrict the pipe sizes to those defined by the Pipe Class tool.

Roughness

The surface roughness of the pipe segment.Whenever a material is selected, the absoluteroughness is initialised to the default value for thematerial as defined on the Preferences dialogbox. Valid values are between 0.00001 inchesand 0.1 inches.

Nominal Diameter

The nominal pipe diameter used to describe thepipe size. For pipes with a nominal diameter of 14inches or more, this will be the same as theoutside diameter of the pipe.

Schedule Number

If a pipe schedule other than "-" is selected, youwill be able to select a nominal pipe diameterfrom the pipe databases. It will not be necessaryto specify the internal diameter or the wallthickness for the pipe.

If you select "-" you will be unable to select anominal pipe diameter from the pipe databasesand you will then have to specify both the internaldiameter and wall thickness for the pipe.

Internal Diameter The pipe diameter used for the pressure dropcalculations.

Wall Thickness The thickness of the pipe wall. Valid values areany positive number or zero.


Schedule Numbers:

Carbon Steel:

10, 20, 30, 40, 60, 80, 100, 120, 140, 160, STD, XS, XXS

Stainless Steel:

5S, 10S, 40S, 80S

You can also define your own schedules (See Section 12.3 - Pipe Schedule Database Editor).

9-5

9-6 Adding/Editing a Pipe

9-6

9.1.3 Fittings Tab

You can supply the following data:

From the Database Fitting box, select the appropriate type of fitting, then press the Add button to move the selection in the Selected Fitting box. You can select as many fittings as required. The final fitting loss equation, which will be a sum of all the selected fittings, will appear in a box underneath the Selected Fitting box. Click Link to transfer the coefficients for this equation into the Fittings Loss field, while maintaining the list of fittings. Click Paste to transfer the coefficients for the fitting equation into the Fittings Loss field on the Pipe Editor view. The selected list of fittings will not be retained. To remove the selected fitting individually, select the fitting and press the Delete button.

Figure 9.3


Length Multiplier

The length of the pipe is multiplied by this valueto determine the equivalent length used for thepressure drop calculation. If left blank then thevalue on the Calculation Options Editor isused.

Fittings Loss

The fittings "K" factor is calculated from thefollowing equation in which Ft is the friction factorfor fully developed turbulent flow:

K = A + BFt

Valid values are any positive number or 0.

The network cannot be sized correctly if you use equivalent length data to model fittings losses, since the equivalent length of any pipe fitting is a function of the pipe diameter and will therefore be incorrect when the diameters change.

Scenarios 9-7

9.1.4 Heat Transfer Tab

The groups available on the Heat Transfer tab are as follows:

• External Conditions• Insulation• Heating

External Conditions Group

The following fields are available in this group:

If the Heat Transfer With Atmosphere check box is activated, the pipe segment can have an heat exchange with the surrounding.

Insulation Group

The Insulation group contains the following:

Figure 9.4


Temperature Enter the outside temperature. It will be used tocalculate the amount of heat transfer.

Wind Velocity Specify the wind velocity.


Description A brief description about the pipe insulation.

Thickness Supply the insulation thickness.

Thermal Conductivity Enter the insulation thermal conductivity.

9-7

9-8 Methods Tab

9-8

Heating Group

You can supply either one of the following in the Heating group:

9.2 Methods Tab

The following data information should be supplied on the Methods tab:


Outlet temperature

You can explicitly set an outlet temperature forthis segment, or leave it blank. A heater in a flareknockout drum is an example of processequipment that may require a fixed outlettemperature. Valid values are between -260°Cand 999°C.

Duty Enter the heating duty and the outlet temperaturewill be calculated based on the inlet temperature.

Figure 9.5


VLE Method

The options for the Vapour-Liquid Equilibrium calculations are as follows (see Appendix A- Theoretical Basis for more details):

• Compressible Gas - Real Gas relationship• Peng Robinson - Peng Robinson Equation of State• Soave Redlich Kwong - Soave Redlich Kwon Equation of State• Vapour Pressure - Vapour Pressure method as described in API Techincal Data Book

Volume 113.• Model Deafault - If this is selected, the Default method for the VLE method (as defined

on the Calculation Options Editor view) will be used.

Scenarios 9-9

Horizontal andInclined Pipes

The Horizontal/Inclined method applies only when you have selected Two-Phase pressuredrop. The options are:

• Isothermal Gas - This is a compressible gas method that assumes isothermal expansionof the gas as it passes along the pipe. Flarenet uses averaged properties of the fluid overthe length of the pipe. The outlet temperature from the pipe is calcualted by adiabaticheat balance either with or without heat transfer. Pressure losses due to change inelevation are ignored.

• Adiabatic Gas - This is a compressible gas method that assumes adiabatic expansion ofthe gas as it passes along the pipe. As with the Isothermal Gas method, pressure lossesdue to change in elevation are ignored.

• Beggs & Brill - The Beggs and Brill method is based on work done with an air-watermicture at many different conditions, and is aplicable for inclined flow. For more details,see Appendix A - Theoretical Basis .

• Dukler - Dukler breaks the pressure drop in two-phase systems into three components -friction, elevation and acceleration. Each component is evaluated independantly andadded algebraically to determine the overall pressure drop. For more details , seeAppendix A - Theoretical Basis .

• Default - If this is selected, the Default method for the Horizontal/Inclined method (asdefined on the Calculation Options Editor view) will be used.

Vertical Pipes

The Vertical method applies only when you have selected Two-Phase pressure drop. Theoptions are:

• Isothermal Gas - This is a compressible gas method that assumes isothermal expansionof the gas as it passes along the pipe. Flarenet uses averaged properties of the fluid overthe length of the pipe. The outlet temperature from the pipe is calcualted by adiabaticheat balance either with or without heat transfer. Pressure losses due to change inelevation are ignored.

• Adiabatic Gas - This is a compressible gas method that assumes adiabatic expansion ofthe gas as it passes along the pipe. As with the Isothermal Gas method, pressure lossesdue to change in elevation are ignored.

• Beggs & Brill - Although the Beggs and Brill method was not originally intedned for usewith vertical pipes, it is nevertheless commonly used for this purpose, and is thereforeincluded as an option for vertical pressure drop methods. For more details, see AppendixA - Theoretical Basis .

• Dukler - Although the Dukler method is not generally applicable to vertical pipes, it isincluded here to allow comparison with the other methods.

• Orkiszewski - This is a pressure drip correlation for vertical, two-phase flow for fourdifferent flow regimes - bubble, slug, annular-slug transition and annular mist. For moredetails, see Appendix A - Theoretical Basis .

• Default - If this is selected, the Default method for the Vertical method (as defined on theCalculation Options Editor view) will be used.

Two PhaseElements

For two-phase calculations, the pipe segment is divided into a specified number of elements.On each element, energy and material balances are solved along with the pressure dropcorrelation. In simulations involving high heat transfer rates, many increments may benecessary, due to the non-linearity of the temperature profile. Obviously, as the number ofincrements increases, so does the calculation time; therefore, you should try to select anumber of increments that reflects the required accuracy.

Friction FactorMethod

The Friction Factor Method applies only when you have entered a value for friction factor. Theoptions are:

• Round - This method has been maintained promarily for historical purposes in order forolder Flarenet calculations to be matched. It tends to over predict the friction factor by upto 10% in the fully turbulent region.

• Chen - It should always be the method of preference since it gives better predictions andfully turbulent flow conditions normally found within flare systems.

• Default - If this is selected, the Default method for the Friction Factor Method (as definedon the Calculation Options Editor view) will be used.

Damping Factor The damping factor used in the iteratice solution procedure. If this is left blank, the value in theCalculation Options Editor view is used.


9-9

9-10 Methods Tab

9-10

Click OK to accept the modifications and return to the Pipe Manager view, or Cancel to discard the modifications.

9.2.1 Multiple EditingYou can edit multiple pipe segments simultaneously by highlighting them with the mouse cursor while keeping the Ctrl key pressed. After you have finished selecting pipe segments, double click any of them to open the common Pipe Editor view.

This particular Pipe Editor view does not show the Name field as well as the Upstream and Downstream Nodes field since those are associated with individual pipe segments. You can specify a universal setting for all the selected pipe segments or allow them to keep their individual settings by entering * in the field or selecting * from the drop down menus.

Figure 9.6

Figure 9.7

The two phase methods are really meant for incompressible fluids. If the pressure drop is greater than 10% of the inlet pressure then the comprissibility effects become significant you can approximate compressible elements in the pipe.

Scenarios 9-11

9.3 Ignoring/Restoring Pipes

You can ignore single or multiple pipe segments within the model. When you ignore a single pipe segment, all upstream pipe segments are automatically ignored. This enables you to do what if type calculations, where part of the network can be excluded from the calculation without the need for deletion and reinstallation of the appropriate pipe segments.

To ignore a pipe:

1. Open the Pipe Editor view of the pipe segment that you wish to ignore.

2. On the Connections tab, see Figure 9.8, activate the Ignore check box.

To restore a pipe segment that has previously been ignored:

1. Open the Pipe Editor view of the pipe segment that you wish to ignore.

2. On the Connections tab, deactivate the Ignore check box.

Figure 9.8

When you ignore a single pipe segment, all upstream pipe segments are automatically ignored.

9-11

9-12 Arranging Display Order

9-12

9.4 Arranging Display Order

The display order for the pipe segments has no impact on the calculations. Consequently, you are free to display the pipe segments in any order that you wish. To arrange the display order of the pipe segments:

1. Display the Pipe Manager view.

This view has buttons to position individual pipe segments within the display and to sort the order by either the group or alphanumerically based on the segment name.

2. Manipulate the display order as follows:

• To sort the pipe segments by location, click the Sort button andthen select Group from the extended menu.

• To sort the pipe segments in alphabetical order based upon thesegment name, click the Sort button and then select Namefrom the menu.

• To swap the display position of two pipe segments, click thename of the first pipe segment in the Pipe box and then eitherpressing the <Shift> key click on the name of the second pipesegment if they are on top of each other or pressing the <Ctrl>key click on the name of the second pipe segment if they arelocated in different places in the list. Press the Swap button todisplay the pipe segment list in the new order.

• To reposition the display position of one pipe segment, click thename of the pipe segment to be moved in the Pipe box andthen click on either the up or down arrow keys.

4. Click OK to accept the new order.

Figure 9.9

Scenarios 9-13

9.5 Pipe Tools

9.5.1 Pipe Class EditorThe Pipe Class Editor allows you to edit the allowable schedules for each nominal diameter, for both Carbon Steel and Stainless Steel, during sizing calculations. It also allows you to restrict specific pipe sizes.

Note that if you have selected Use Pipe Class When Sizing in the Run Options view, these are the schedules which will be used.

Figure 9.10

9-13

9-14 Pipe Tools

9-14

Nodes 10-1

10 Nodes

10-1

10.1 Node Manager............................................................................................. 3

10.2 Node Types ................................................................................................. 4

10.3 Sources ..................................................................................................... 18

10.3.1 Copy Source Data................................................................................ 3010.3.2 Source Tools ........................................................................................ 31

10.4 Ignoring/Restoring Nodes ....................................................................... 32

10-2

10-2

Nodes 10-3

Pipes are connected via nodes, which can be added, edited and deleted from the Node Manager. Sources are also added through the Node Manager view.

10.1 Node ManagerTo access the Node Manager, select Nodes from the Build menu.

The following buttons are available:

Figure 10.1

Button Description

Add

You will be prompted to select the type of node.This new node will be named with a numberdepending upon the number of nodes alreadyadded.

EditAllows you to edit the currently highlighted node.The form varies, depending on the type of node,as discussed below.

Delete Allows you to remove the currently highlightednode.

Sort Sort the nodes list alphabetically (in descendingorder) either by name or location or type of node.

Up and Down Arrow Move the highlighted pipe up and down the list.

Swap Swap the two selected pipes in the Pipes list.

OK Closes the view.

10-3

10-4 Node Types

10-4

10.2 Node TypesThe following types of node available in FLARENET.

• Flare Tip• Connector• Tee• Vertical Separator• Horizontal Separator• Orifice Plate• Flow Bleed• Relief Valve• Control Valve

Flare Tip

The tabs available on the Flare Tip Editor are the Connections and Calculations tabs.

Figure 10.2

Nodes 10-5

Connections Tab

The following fields are available on this tab:

To ignore the flare tip node during calculations, select the Ignore check box. Flarenet will completely disregard the node until you restore it to an active state by clearing the check box.

Calculations Tab

The Calculations tab contains the following:

Select the Use Curve check box to enter a vendor supplied data for the pressure drop through a flare tip, which often take the form of a curve. It gives the pressure drop versus the mass flowrate for a fluid with defined molecular weight and temperature and uses linear interpolation. To add a new data point, press the Add button and to delete an existing data point press the Delete button. You can provide up to 10 data points.

Field Description

Name The alphanumeric description of the node (e.g. -HP Flare Tip).

Location

You may wish to specify the location of the nodein the plant. Note that the location can have analphanumeric name. This feature is useful forlarge flowsheets; you can provide a different“location” name to different sections to make itmore comprehensible.

Inlet Either type in the name of the pipe segment orselect from the drop down menu.

At You can specify the end of the pipe segmentattached with the flare tip.

Field Description

DiameterYou can specify a diameter for the tip. The defaultvalue is 1000 mm. Valid values are between 0and 1000 mm.

Fitting Loss Fitting loss will be used to correct the sizing forthe tip.

10-5

10-6 Node Types

10-6

Connector

This connects two pipe objects. The tabs available on the Connector Editor view are Connections and Calculations tab.

Connections Tab


Figure 10.3

Field Description

Name The alphanumeric description of the node (e.g. -HP Connect 1).

Location


Upstream/Downstream Either type in the name of the pipe segment orselect from the drop down menu.

At You can specify the end of the pipe segmentattached with the connector.

Nodes 10-7

To ignore the connector node during calculations, select the Ignore check box. Flarenet will completely disregard the node until you restore it to an active state by clearing the check box.

Calculations Tab


Field Description

Theta Specify the connector expansion angle. If notdefined, it will be calculated from length.

Length Enter the connector length. If not defined, it willbe calculated from theta.

Fitting Loss Method

The available options are;• Calculated - The fitting loss willl be calculated

based on upstream/downstream pipesizes.

• Ignored - Flarenet will not calculate the fitting lossif this is selected.

10-7

10-8 Node Types

10-8

Tee

This tee connects three pipes. The Tee Editor view is used to enter connection data and it contains the Connections and Calculations tabs.

Figure 10.4

Nodes 10-9

Connections Tab


To ignore the tee node during calculations, select the Ignore check box. Flarenet will completely disregard the node until you restore it to an active state by clearing the check box.

Calculations Tab


Field Description

Name The alphanumeric description of the node (e.g. -HP Tee 1).

Location


Upstream/Downstream/Branch

Either type in the name of the pipe segment orselect from the drop down menu.

At You can specify the end of the pipe segmentattached with the tee.

You only need to provide 2 of 3 connections to be able to solve the tee. This allows for solution(s) to partially built networks.

Field Description

ThetaSpecify the connector expansion. This will bezero if used between pipes with the samediameter.

Fitting Loss Method

The available options are;• Ignored - Flarenet would not calculate the fitting

loss if this option is selected.

• Simple - It uses a constant flow ratio independentK factor for the loss through the branch and run.

• Miller - This method uses a K factor which isinterpolated using Miller Curves, which arefunctions of the flow and area ratios of the branchto the total flow as well as the branch angle.

10-9

10-10 Node Types

10-10

Vertical Separator

Separators are used to divide the vessel contents into its constituent vapour and liquid phases. In Flarenet, the Vertical Separator have only one inlet and one vapour outlet stream.

Connections Tab

The Connections tab contains the following fields:

To ignore the Vertical Separator during calculations, select the Ignore check box. Flarenet will completely disregard the node until you restore it to an active state by clearing the check box.

Figure 10.5

Field Description

Name The alphanumeric description of the Vertical Separator (e.g. - HP KO Drum).

Location

You may wish to specify the location of theVertical Separator in the plant. Note that thelocation can have an alphanumeric name. Thisfeature is useful for large flowsheets; you canprovide a different “location” name to differentsections to make it more comprehensible.

Inlet/Vapour Outlet Either type in the name of the pipe segment orselect from the drop down menu.

At You can specify the end of the pipe segmentattached with the Vertical Separator.

Nodes 10-11

Calculations Tab

The following fields are available:

Figure 10.6

Field Description

Diameter The internal diameter of the vessel.

Fitting Loss Method

The Fitting Loss drop down menu have thefollowing two options available:

• Ignored - If this option is selected, the fittinglosses for the Vertical Separator will not becalculated.

• Calculated - The fitting losses for theseparator will be calculated.

10-11

10-12 Node Types

10-12

Horizontal Separator

Separators are used to divide the vessel contents into its constituent vapour and liquid phases. In Flarenet, the Horizontal Separator have only one primary inlet, one secondary inlet/outlet, and one vapour outlet stream.

Connections Tab


To ignore the Horizontal Separator during calculations, select the Ignore check box. Flarenet will completely disregard the node until you restore it to an active state by clearing the check box.

Figure 10.7

Field Description

Name The alphanumeric description of the Horizontal Separator (e.g. - HP KO Drum).

Location

You may wish to specify the location of theHorizontal Separator in the plant. Note that thelocation can have an alphanumeric name. Thisfeature is useful for large flowsheets; you canprovide a different “location” name to differentsections to make it more comprehensible.

Primary Inlet/Secondary Inlet/VapourOutlet

Either type in the name of the pipe segment orselect from the drop down menu.

At You can specify the end of the pipe segmentattached with the Horizontal Separator.

You only need to provide 2 of 3 connections to be able to solve the separator. This allows for solution(s) to partially built networks.

Nodes 10-13

Calculations Tab

The following fields are available:

Figure 10.8

Field Description

Diameter The internal diameter of the vessel.

Liquid LevelThe liquid level in the vessel. Pressure drop iscalculated based upon the the vapour spaceabove the liquid.

Fitting Loss Method


• Ignored - If this option is selected, the fittinglosses for the Horizontal Separator will notbe calculated.

• Calculated - The fitting losses for thesource will be calculated.

10-13

10-14 Node Types

10-14

Orifice Plate

An Orifice Plate is a thin plate, which has a clean-cut hole with straight walls perpendicular to the flat upstream face of the plate placed crosswire of the channel.

Connections Tab


To ignore the Orifice Plate during calculations, select the Ignore check box. Flarenet will completely disregard the node until you restore it to an active state by clearing the check box.

Figure 10.9

Field Description

Name The alphanumeric description of the Orifice Plate (e.g. - HP OP).

Location

You may wish to specify the location of theOrifice Plate in the plant. Note that the locationcan have an alphanumeric name. This feature isuseful for large flowsheets; you can provide adifferent “location” name to different sections tomake it more comprehensible.


AtYou can specify the end of the pipe segmentattached with the Orifice Plate.

Nodes 10-15

Calculations Tab

The fields available on the Calculations tab are:

Figure 10.10

Field Description

Diameter The diameter of the orifice hole. Valid values arebetween 0 and 1000 mm.

Upstream DiameterRatio

It is the ratio of the throat diameter to theUpstream pipe diameter.

Downstream DiameterRatio

It is the ratio of the throat diameter to theDownstream pipe diameter.

Fittings Loss Method


• Ignored - If this option is selected, the fittinglosses for the Horintal Separator would notbe calculated.

• Thin Orifice - The fitting losses for theorifice plate will be calculated using theequations for the thin orifice plate.

• Contraction/Expansion - For this fittingloss method, orifice plates will be modelledas a sudden contraction from the inlet linesize to the hole diameter followed by asudden expansion from the hole diameter tothe outlet line size.

You only need to provide 1 of 3 sizing parameters. For Example, if you entered the Diameter than FLARENET will calculate the Upstream Diameter Ratio and the Downstream Diameter Ratio.

10-15

10-16 Node Types

10-16

Flow Bleed

The Flow Bleed is a simple calculation block that allows you to;

• Specify a fixed pressure drop• Specify a constrained flow offtake where the flow offtake is

calculated from

The calculated Offtake is constrained to maximum and minimum values.

Connections Tab


To ignore the Flow Bleed during calculations, select the Ignore check box. Flarenet will completely disregard the node until you restore it to

(10.1)Offtake Multiplier Inlet Flow Offset+×=

Figure 10.11

Field Description

Name The alphanumeric description of the Flow Bleed (e.g. - HP Connect XX).

Location

You may wish to specify the location of the Flow Bleed in the plant. Note that the location canhave an alphanumeric name. This feature isuseful for large flowsheets; you can provide adifferent “location” name to different sections tomake it more comprehensible.


AtYou can specify the end of the pipe segmentattached with the Flow Bleed.

Nodes 10-17

an active state by clearing the check box.

Calculations Tab

The Fields available on the Calculations tab are:

Source

This connects a source to a pipe object. All sources are connected as a source node. Section 10.3 - Sources lists in detail the type of sources available in Flarenet.

Figure 10.12

Field Description

Offtake Multiplier Specify the Offtake multiplier. The default value is0.

Offtake Offset Specify the Offset for the Offtake to compensatefor the changes in the inlet flow.

Offtake Minimum Specify the minimum value for the Offtake.

Offtake Maximum Specify the maximum value for the Offtake.

Pressure Drop Enter the pressure drop across the Flow Bleed.

10-17

10-18 Sources

10-18

10.3 SourcesRelief valves, blowdown valves, rupture disks, purge valves, etc. are represented by sources. Each source gives a fixed flow, composition, pressure and temperature description for the fluid entering the flare header network at a defined point.

The fluid data for each source may vary between scenarios, but the connection node and any physical characteristics are always the same for all scenarios.

For example, you might have to consider both a blocked control valve scenario and a fire scenario for a particular relief valve. The following sample Fluid data would be specific to each scenario:

However, the following Source data would be the same for both scenarios:

The source data is managed by the Node Manager view. The sources available in Flarenet are: Relief Valve and Control Valve.

PropertyScenario

Blocked Valve Fire

Molecular Weight 23.0 34.0

Flow [kg/hr] 50,000 10,000

Upstream Pressure [bar abs] 11 12

Upstream Temperature [C] 90 150

FLARENET will display the scenario specific data in blue . The data which is common to all the scenarios is shown in black.

Property Value

Orifice Area Per Valve (mm 2) 70.698

Diameter (mm) 300

Nodes 10-19

Relief Valve

The Relief Valve source can be used to model types of spring loaded relief valves. Relief valves are used frequently in many industries in order to prevent dangerous situations occuring from pressure buildups in a system.

Connections Tab

The Connections tab is where the name of the Relief Valve and its outlet stream is specified. The following fields are available:

To ignore the Relief Valve during calculations, select the Ignore check box. Flarenet will completely disregard the node until you restore it to an active state by clearing the check box.

Figure 10.13

Field Description

Name The alphanumeric description of the Relief Valve (e.g. - PSV 1).

Location

You may wish to specify the location of the ReliefValve in the plant. Note that the location can havean alphanumeric name. This feature is useful forlarge flowsheets; you can provide a different“location” name to different sections to make itmore comprehensible.

Inlet Either type in the name of the pipe segment orselect from the drop down menu.

At You can specify the end of the pipe segmentattached with the Relief Valve.

10-19

10-20 Sources

10-20

Conditions Tab

The fields avalable on this page are:

Figure 10.14

Field Descrption

MAWP

The Maximum Allowable Working Pressure(MAWP) is the maximum gauge pressurepermissible in a vessel at its operatingtemperature. It is normally equal to the reliefvalve set pressure unless you have a lowpressure vessel.

Contingency

In general there are two types of process upsetconditions:

• Fire - The relieving pressure is 121% of MAWP.

• Operating - The relieving pressure is 110% ofMAWP. Some of the operating upset examples arecooling failure, power failure and instrument airfailure.

Relieving Pressure

The Relieving Pessure is equal to the valve setpressure plus the overpressure. You can eitherenter the value or have it calculated using theMAWP and the Contingency by pressing the Setbutton. If you entered a value less than theMAWP, a warning message will be generated.Valid values are between 0.01 and 600 bar.

Nodes 10-21

Inlet Temp Spec.

The temperature specification of the source onthe upstream side of the relief valve. Valid valuesare between -250oC and 1500oC.

You can select the fluid condition from the dropdown box on the ledft side. The available optionare:

• Actual - it uses the given inlet temperatureas the actual fluid temperature.

• Subcool - If this option is selected, enter theamount of subcooling.

• Superheat - If this option is selected, enterthe amount of superheat.

Allowable BackPressure

The Allowed Back Pressure is the pressure thatis allowed to exist at the outlet of a pressure reliefdevice as a result of the pressure in thedischarge system. It is the sum of thesuperimposed and built-up back pressure.Pressing the Set button calculates the AllowableBack Pressure as a function of the valve type asdefined on the Dimension tab. Valid values arebetween 0.01 to 600 bar.

Outlet Temperature

This is the temperature of the source on thedownstream side of the valve.

If the enthalpy method chosen is the Ideal Gasmodel, then this temperature is used todetermine the enthalpy of the source at theentrance to the pipe network, otherwise thisenthalpy is calculated by isenthalpic flash fromthe upstream pressure and temperature. Validvalues are between -250oC and 1500oC.

Mass Flow It is the mass flow of the source. Valid values arebetween 0 and 100,000,000 kg/hr.

Rated FlowIt is the rated mass flow of the source. This is thesized or allowable flowrate. Valid values arebetween 0 and 100,000,000 kg/hr.

Field Descrption

We recommend a value for Outlet Temperature which corresponds to an isenthalpic flash from the upstream conditions down to the Allowable Back Pressure. This will give the highest probable entry temperature into the system which will in turn give the highest velocities.

The rated flowrate is required if you are sizing the tailpipes based on the rated capacity of the source. The API guide for Pressure-Relieving and Depressuring Systems recommends that tailpipes be sized in this manner (Section 5.4.1.3.1, 1990 Edition23).

10-21

10-22 Sources

10-22

Composition Tab

The Composition tab contains the following fields:

Figure 10.15

Field Description

Basis The composition basis, which may be either Mol.Wt., Mole Fraction or Mass Fraction .

Mol. Wt.

The molecular weight of the fluid. You can onlyenter data here if the composition basis selectedis Molecular Weight. Valid values are between 2and 500.

If the composition basis selected is MoleFractions , the molecular weight is updated whenyou enter or change the component fractions.

Fluid Type

If Molecular Weight is selected in the compositionbasis drop down box, you need to select theFluid Type to calculate a binary composition inorder to match the molecular weight. If the twocomponents of the specified fluid type are notfound then the other components are used.

Component Fractions

The fluid composition in either mole or massfractions. You can only enter data here if thecomposition basis selected is Mole Fractions.

When you exit the Source view, you will beprompted about an Invalid Composition if thesum of these fractions is not equal to one. Youcan normalised the composition either by mauallyeditting the component fractions or by pressingthe Normalise button.

If the composition basis selected is MolecularWeight , the component fractions are re-estimated when you change the molecularweight.

Nodes 10-23

Dimensions Tab

The following fields are available on the Dimensions tab:

Figure 10.16

Field Description

Flange Diameter The diameter of the valve discharge flange.

Number of Valves Specify the number of valves for the source. Validvalues are between 1 and 10.

Orifice Area Per Valve

You can either enter it manually or press theLookup button and select from the OrificeSelection view. Valid values are between 0 and100,000,000 mm2.

Valve Type

The choices are:

• Balanced - A spring loaded pressure reliefvalve that incorporates a means forminimizing the effect of back pressure on theperformance characteristics.

• Conventional - A spring loaded pressurerelief valve whose performancecharacteristics are directly affected bychanges in the back pressure on the valve.

10-23

10-24 Sources

10-24

Methods Tab

The available fields are:

Figure 10.17

Fields Description

Fittings Loss Method

The Fittings Loss drop down menu have thefollowing two options available:

• Ignored - If this option is selected, the fittinglosses for the relief valve would not becalculated.


VLE Method

The options for the Vapour-Liquid Equilibriumcalculations are as follows (see Appendix A -Theoretical Basis for more details):

• Compressible Gas - Real Gas relationship.• Peng Robinson - Peng Robinson Equation

of State.• Soave Redlich Kwong - Soave Redlich

Kwong Equation of State.• Vapour Pressure - Vapour Pressure

method as described in API Technical DataBook - Volume 1.

• Model Default - If this is selected, theDefault method for the VLE method (asdefined on the Options view) will be used.

Sizing MethodThe two Sizing Method options available are:

• API - American Petroleum Institute• HEM - Homogeneous Equilibrium Model

Nodes 10-25

Control Valve

The control valve is used to model a constant flow source such as purge valves, bursting disks and blowdown valves. The most significant difference to the relief valve is that the rated flow equals the nominal flow.

Connections Tab

The Connections tab is where the name of the Control Valve and its outlet stream is specified. The following fields are available:

To ignore the Control Valve during calculations, select the Ignore check box. Flarenet will completely disregard the node until you restore it to an active state by clearing the check box.

Figure 10.18

Field Description

Name The alphanumeric description of the ControlValve (e.g. - FCV 1).

Location

You may wish to specify the location of theControl Valve in the plant. Note that the locationcan have an alphanumeric name. This feature isuseful for large flowsheets; you can provide adifferent “location” name to different sections tomake it more comprehensible.

Outlet Either type in the name of the pipe segment orselect from the drop down menu.

At You can specify where the pipe segment is to beattached to the Control Valve.

10-25

10-26 Sources

10-26

Conditions Tab

The fields avalable on this page are:

Figure 10.19

Field Descrption

Inlet PressureThe pressure of the source on the upstream sideof the valve. Valid values are between 0.01 and600 bar.

Inlet Temp Spec.The temperature specification of the source onthe upstream side of the control valve. Validvalues are between -260oC and 1500oC.

Allowable BackPressure

The Allowed Back Pressure is the pressure thatis allowed to exist at the outlet of a pressure reliefdevice as a result of the pressure in thedischarge system. It is the sum of thesuperimposed and built-up back pressure.Pressing the Set button calculates the AllowableBack Pressure as a function of the valve type asdefined on the Dimension tab. Valid values arebetween 0.01 to 600 bar.

Outlet Temperature

This is the temperature of the source on thedownstream side of the valve.

If the enthalpy method chosen is the Ideal Gasmodel, then this temperature is used todetermine the enthalpy of the source at theentrance to the pipe network, otherwise thisenthalpy is calculated from the upstreampressure and temperature. Valid values arebetween -250oC and 1500oC.

Mass Flow This is the mass flow of the source. Valid valuesare between 0 and 100,000,000 kg/hr.

It is recommended that a value for Outlet Temperature which corresponds to an isenthalpic flash from the upstream conditions down to the Allowable Back Pressure. This will give the highest probable entry temperature into the system which will in turn give the highest velocities.

Nodes 10-27

Composition Tab

The Composition tab contains the following fields:

Figure 10.20

Field Description

BasisThis is the composition basis, which may beeither Mol. Wt. , Mole Fraction or MassFraction .

Mol. Wt.

It is the molecular weight of the fluid. You canonly enter data here if the composition basisselected is Molecular Weight. Valid values arebetween 2 and 500.

If the composition basis selected is MoleFractions , the molecular weight is updated whenyou enter or change the component fractions.

Fluid Type

If Molecular Weight is selected in the compositionbasis drop down box, you need to select theFluid Type to calculate a binary composition inorder to match the molecular weight. If the twocomponents of the specified fluid type are notfound then the other components are used.

Component Fractions

This is the fluid composition in either mole ormass fractions. You can only enter data here ifthe composition basis selected is Mole Fractions.

When you exit the Source view, you will beprompted about the Invalid Composition if thesum of these fractions is not equal to one. Youcan normalised the composition by either mauallyeditting the component fractions or by pressingthe Normalise button.

If the composition basis selected is MolecularWeight , the component fractions are estimatedwhen you change the molecular weight.

10-27

10-28 Sources

10-28

Dimensions Tab

The only field available on the Dimension tab is the Flange Diameter. It is the diameter of the valve discharge flange.

Figure 10.21

Nodes 10-29

Methods Tab

The available fields are:

Figure 10.22

Fields Description

Fitting Loss Method


• Ignored - If this option is selected, the fittinglosses for the control valve would not becalculated.


VLE Method






• Model Default - If this is selected, theDefault method for the VLE method (asdefined on the Options view) will be used.

10-29

10-30 Sources

10-30

10.3.1 Copy Source DataOn the Relief Valve Editor and Control Valve Editor views, press the Copy To button to copy source data to other scenarios. You will see a view similar to the following:

The Copy Source Data to Scenarios view contains two columns: Copy and Scenario. You can select the scenarios from the Scenario list by activating the corresponding check box in the Copy colum.

Figure 10.23

Nodes 10-31

10.3.2 Source ToolsThe initial sizing of a flare system is time consuming both in terms of time taken to build the model and the computation time. Using an Ideal Gas method can speed up the calculation during the initial sizing estimation. Speed is an important issue during sizing calculation especially for a complex multiple scenario case. Typically, the back pressure should be used for calculations. Rigourous rating calculations for all scenarios can be done by the Peng Robinson enthalpy method or any other enthalpy methods with pressure depedency and provides the down stream temperature.

Updating Downstream Temperatures

The downstream temperatures are only used to define the system entry temperature when ideal gas enthalpies are used. After several cycles of rating and sizing calculations, the original values for each source may no longer be valid. These values may be updated to reflect the results of the last calculation using an equation of state enthalpy method as follows.

Select Refresh Source Temperatures from the Tools menu.

Adding Single Source Scenarios

The thorough evaluation of a flare network will require the evaluation of many scenarios. In most systems, there will be the possibility of each relief valve lifting on its own. In the case of a petrochemical complex, this could have several hundred relief valves and the task of setting up the scenarios for each relief valve would be time consuming and error prone.

Once all the major scenarios have been defined, select Add Single Source Scenarios from the Tools menu. Press Yes to allow FLARENET to analyse the existing scenarios to determine the greatest flow rate for each relief valve and create a scenario using this data.

10-31

10-32 Ignoring/Restoring Nodes

10-32

10.4 Ignoring/Restoring Nodes

You can ignore single or multiple nodes within the model. When you ignore a single node, all upstream nodes are automatically ignored. This enables you to do what if type calculations, where part of the network can be excluded from the calculation without the need for deletion and reinstallation of the appropriate nodes.

To ignore a node:

1. Open the node editor view of the node that you wish to ignore.

2. On the Connections tab, see Figure 10.24, activate the Ignore check box.

To restore a node that has previously been ignored:

1. Open the node editor view of the node that you wish to ignore.

2. On the Connections tab, deactivate the Ignore check box.

Figure 10.24

When you ignore a single node, all upstream nodes are automatically ignored.

Calculations 11-1

11 Calculations

11-1

11.1 Calculation Options ................................................................................... 3

11.1.1 General Tab............................................................................................ 311.1.2 Methods Tab........................................................................................... 611.1.3 Warnings Tab ......................................................................................... 911.1.4 Initialisation Tab.................................................................................... 10

11.2 Starting The Calculations........................................................................ 11

11.3 Efficient Modelling Techniquies.............................................................. 12

11.3.1 Data Entry ............................................................................................ 1211.3.2 Calculation Speed................................................................................ 1311.3.3 Sizing Calculations............................................................................... 15

11-2

11-2

Calculations 11-3

11.1 Calculation OptionsThe selection of settings and options for the calculations is managed from the Calculation Options Editor view. To access the Calculation Options Editor view, select Options from the Calculations menu.

11.1.1 General Tab

The fields available on this tab are:

Figure 11.1

Field Description

Max iterations

The maximum number of iterations. Thecalculations will stop if this limit is reached.

Valid values are between 1 and 100; the defaultis 25.

Pressure Tolerance

When the difference in pressure betweensuccessive iterations is less than this tolerance,convergence is assumed.

Valid values are between 0.00001% and 10%;the default is 0.01%


This is the solution tolerance for the iterativemass balance performed during looped systemcalculations.

Valid values are between 0.00001% and 10%;the default is 0.01%

Damping Factor The damping factor used in the iterative solutionprocedure. A default-damping factor of 1 is used.

11-3

11-4 Calculation Options

11-4

Atmospheric Pressure Specify the atmospheric pressure. The defaultvalues are 1.01325 bar abs or 14.69618 psia.

Ambient Temperature The Ambient temperature must be in the range-100oC to 100oC.

Wind Velocity The average wind velocity.

Length MultiplierThe length of the pipe is multiplied by this valueto determine the equivalent length used for thepressure drop calculation.

Calculation Mode

Select the Calculating Mode from the drop downmenu. The available options are:

• Rating - It is used to check the existing flaresystem in a plant. This method calculates thepressure profile for the existing pipe network.

• Design - It is used to design anew flare system forthe plant. During calculation it adjust the diametersof all pipes until all the design constraints of MABP,velocity, etc, have been met. These diameters canbe smaller than the initially defined data.

• Debottleneck - It is used to determine areas of theflare system that must be increased in size due toeither the uprating of the existing plant and henceflare loading, or the tie-in of new plant.

Loop Solver

These algorithms provide globally convergentmethods for nonlinear systems of equations. Thefollowing methods are available:

• Broyden - It provides a quicker solution since itdoes not have to calculate Jacobian matrix. Youneed to provide better guesses for the tear pipeflows.

• Newton-Raphson - It works more reliably if defaultinitial guesses are used but takes a longer time.

Field Description

Calculations 11-5

The following check boxes are available on this tab:

Checkbox Description


If checked, the rated flow will be used in thesizing calculations for the tailpipes (as opposedto the actual flowrates). The API guide forPressure-Relieving and Depressuring Systemsrecommends that tailpipes be sized based on therated capacity

Enable Heat Transfer

If checked, heat transfer can take place betweenthe pipe segment and the surroundings for pipesegments which have Heat Transfer withAtmosphere enabled.

All Scenarios

If checked, the calculations will be made for allthe scenarios defined in the model, otherwise thecalculations will be made only for the scenariowhich is currently displayed.

When sizing calculations are made for a numberof scenarios simultaneously, a single network iscalculated that will satisfy the design constraintsfor all scenarios.

Choked Flow Check

If left uncheked, velocities will not be limited tothe sonic condition. This is useful in sizingcalculations since the mach number limitationswill still be met by the time the final solution isreached. Calculation speed is greater at the riskof numerical instability and convergence failure.

Echo Solver History

When checked, it should enable printing of muchmore intermediate information duringcalculations. This should be left uncheckedunless you have convergence problems.

Force ConvergentSolver

Check this option if you are modelling aconvergent flare system, but with 2 flare tips ascommonly found on offshore floating productionfacilities.

11-5


11-6

11.1.2 Methods Tab

The Methods tab contains the following fields:

Figure 11.2


VLE Method






Enthalpy

The following calculation method for thedetermination of fluid enthalpies are available:

• Ideal Gas - This method uses the specifieddownstream temperature of a source tocalculate the heat balance within thenetwork.

• Peng Robinson - The Peng Robinsonenthalpy is determined rigorously.

• Soave Redlich Kwong - The Soave RedlichKwong enthalpy is determined rigorously.

• Lee-Kesler - This method uses the specifiedupstream temperature and pressure of asource to calculate the heat balance withinthe network. The Lee Kesler enthalpies maybe more accurate than the Property Packageenthalpies, but they require solution of aseparate model.

Calculations 11-7

Horizontal and InclinedPipes

The Horizontal/Inclined method applies onlywhen you have selected Two-Phase pressuredrop. The options are:

• Isothermal Gas - This is a compressible gasmethod that assumes isothermal expansionof the gas as it passes along the pipe.Flarenet uses averaged properties of thefluid over the length of the pipe. The outlettemperature from the pipe is calculated byadiabatic heat balance either with or withoutheat transfer. Pressure losses due to changein elevation are ignored.

• Adiabatic Gas - This is a compressible gasmethod that assumes adiabatic expansion ofthe gas as it passes along the pipe. As withthe Isothermal Gas method, pressure lossesdue to change in elevation are ignored.

• Beggs & Brill - The Beggs and Brill methodis based on work done with an air-watermixture at many different conditions, and isapplicable for inclined flow. For more details,see Appendix A - Theoretical Basis .

• Dukler - Dukler breaks the pressure drop intwo-phase systems into three components -friction, elevation and acceleration. Eachcomponent is evaluated independently andadded algebraically to determine the overallpressure drop. For more details, seeAppendix A - Theoretical Basis .


11-7


11-8

Vertical Pipes

The Vertical method applies only when you haveselected Two-Phase pressure drop. The optionsare:

• Isothermal Gas - This is a compressible gasmethod that assumes isothermal expansionof the gas as it passes along the pipe.Flarenet uses averaged properties of thefluid over the length of the pipe. The outlettemperature from the pipe is calculated byadiabatic heat balance either with or withoutheat transfer. Pressure losses due to changein elevation are ignored.

• Adiabatic Gas - This is a compressible gasmethod that assumes adiabatic expansion ofthe gas as it passes along the pipe. As withthe Isothermal Gas method, pressure lossesdue to change in elevation are ignored.

• Beggs & Brill - Although the Beggs and Brillmethod was not originally intended for usewith vertical pipes, it is neverthelesscommonly used for this purpose, and istherefore included as an option for verticalpressure drop methods. For more details,see Appendix A - Theoretical Basis .

• Dukler - although the Dukler method is notgenerally applicable to vertical pipes, it isincluded here to allow comparison with theother methods.

• Orkiszewski - This is a pressure dropcorrelation for vertical, two-phase flow forfour different flow regimes - bubble, slug,annular-slug transition, and annular mist. Formore details, see Appendix A - TheoreticalBasis .

Two Phase Elements

For two-phase calculations, the pipe segment isdivided into a specified number of elements. Oneach element, energy and meterial balances aresolved along with the pressure drop correlation.In simulations involving high heat transfer rates,many increments may be necessary, due to thenon-linearity of the temperature profile.Obviously, as the number of incrementsincreases, so does the calculation time;therefore, you should try to select a number ofincrements which reflects the required accuracy.

Friction Factor Method

The Friction Factor Method applies only whenyou have entered a value for friction factor. Theoptions are:

• Round - This method has been maintainedprimarily for historical purposes in order forolder Flarenet calculations to be matched. Ittends to over predict the friction factor by upto 10% in the fully turbulent region.

• Chen - It should always be the method ofpreference since it gives better predictionsand fully turbulent flow conditions normallyfound within flare systems.


Calculations 11-9

11.1.3 Warnings Tab

There are three groups available on the Warnings tab:

• Design Problems• Calculation Problems• Sizing Status

Design Problems Group

The following options can be selected in this group:

• Mach Number• Velocity• Rho V2• Noise• Back Pressure• Choked Flow• Slug Flow• Temperature• Carbon Steel Min./Max Temp.• Carbon Steel Min./Max Temp.

Figure 11.3

You can set the level of detail of the warnings by checking the appropriate boxes. By default, they are all checked.

11-9


11-10

Calculation Problems Group

The Calculation Problems group contain the following check boxes:

• Physical properties Failure• Heat Balance Failure• Choke Pressure Failure• Pressure Drop Failure• Liquid With Vapour Only Method

Sizing Status Group

The check boxes available in this group are:

• Initialisation• Size Change• Limited Reached

11.1.4 Initialisation Tab

The Initialisation tab allows you to specify the initial value for the pressure for physical property calculations. It should be at least equal to the system exit pressure.

Figure 11.4

Calculations 11-11

11.2 Starting The Calculations

To start the calculations, select Calculate from the Calculations menu. Alternatively, you could select the Start Calculations button on the button bar.

The status of the rating calculations is shown on the status bar. In the following screen shot, the second box on the status bar shows that the node mass and energy balance calculations are performed for tee Tee 1. The third box shows that at the second iteration, the pressure tolerance for the sixth pipe is calculated as 2.45e-1.

To abort calculations, select the Stop Calculations button, which takes the place of the Start Calculations button during calculations.

Figure 11.5

Start Calculations Button

The following words before the object on the status bar shows the type of calculation being performed:

B = Mass and Energy Calculations

P = Pressure Drop Calculations

Stop Calculations ButtonDue to speed considerations, it is recommended that sizing calculations be performed subject to the constraints:

• Compressible Gas VLE• Ideal Gas Enthalpy Method• No Heat Transfer Calculations

11-11

11-12 Efficient Modelling Techniquies

11-12

11.3 Efficient Modelling Techniquies

Efficient modelling of a flare network requires some forethought in order to meet the primary objectives which are in general:

1. Definition of the design constraints for the flare system. These will usually be defined by company standards or by local health and safety regulations. If unavailable, standard texts such as API-RP-521 can be used to select preliminary acceptable values.

2. Efficient acquisition of the data for the piping configuration and layout.

3. Definition of the scenarios or contingencies which should be evaluated. Grass roots design will require analysis of a far wider range of scenarios to those required by the simple expansion of a flare system to incorporate a new relief valve.

4. Rapid construction of the computer model of the flare system.

5. Fast and efficient calculation of the computer model of the flare system.

Objectives 1 to 5 can only be achieved by the use of engineering skill and judgement. Once complete, the efficient use of Flarenet can lead to a satisfactory project conclusion.

11.3.1 Data EntryFlarenet has a wide range of methods for entering the data for each object within the model. In general, you should use the method that you are most comfortable with, but experience has shown that use of the PFD environment for definition of the piping configuration and layout can save many man days of labour with large flare networks.

Although there is no set order in which the model must be built, the recommended sequence of data entry for building the model is:

1. Define the project description, user name, etc. by selecting Description under File in the menu bar.

2. Set preferences for the default piping materials, type of tee, composition basis, etc. from the Preferences view, accessed via the File command in the menu bar. These may be overwritten on an object by object basis at any stage. Ensure that the Edit Objects On Add check box is active if you wish to edit the object data as each new flowsheet object is created.

Calculations 11-13

3. Define a pipe class if appropriate. This will ensure that you only use pipe sizes as allowed by your project. Open the Pipe Class Editor using the Tools command in the menu bar.

4. With the Calculation Options Editor, define default calculation methods for VLE, Pressure drop, etc. To open this view, select Options under the Calculations menu.

5. Define all the source nodes (relief valves and control valves) for the first scenario. The first scenario should be the one that has the greatest level of common data amongst the complete set of scenarios. Drag the nodes from the toolbox to the PFD.

6. Define the design constraints on Mach number, noise, etc for the first scenario using the Scenario Manager. Set source node on ignored status for this scenario. To access this view, select the Build menu, then Scenarios from the drop-down list.

7. Define the pipe network (common to all scenarios). If the network is to be sized, some care must be taken in defining reasonable estimates for the pipe diameters.

8. Add the next scenario by selecting the Add button on the Scenario Manager. The data for the sources should be cloned from the previously defined scenario that has the most similar data. Edit the design constraints of this scenario if necessary.

9. Make the new scenario current. Highlight it on the Scenario Manager and select the Current button.

10. Edit the source data for each source for the new scenario. Double click sources on the PFD

Repeat steps #8 through #10 for all scenarios

11.3.2 Calculation SpeedCalculation time will often be only a small percentage of the time taken to construct the computer model. However, on low specification personal computers, a sizing calculation for a complex multiple scenario model could take several hours, if not days, if care is not taken in the selection of the thermodynamic models or in the definition of the component slate.

When considering the desired accuracy for the calculations, due consideration must be given to the fact that you are modelling a system that will rarely if ever come close to a steady state condition, with a steady state modelling tool.

11-13


11-14

Component Slate

As a rule of thumb you can assume that the calculation time is proportional to the square of the number of components. Especially when the VLE is calculated by an equation of state instead of treating the fluids as a simple compressible gas.

Flare systems generally operate at conditions in which heavy components such as hexane or heavier will stay in the liquid phase throughout the system. You should therefore endeavour to characterise the heavy ends of petroleum fluids by as few components as possible. The properties that you use for the characterisation should be optimised to:

• Ensure the component stays in the liquid phase• Match the liquid phase density

VLE Method

Source compositions may be modelled either by definition of a molecular weight or by a detailed component by component analysis. When a composition is defined solely by molecular weight Flarenet analizes the user defined component slate to select a pair of components whose molecular weights straddle the defined value. A binary composition is then calculated to match this value. This type of fluid characterisation is only suitable for network analyses in which the fluids are assumed to be vapour, since the VLE behaviour cannot be reasonably predicted from this level of detail. Thus the Compressible Gas VLE method is the only one that should ever be used in association with molecular weight modelling.

When modelling using a detailed component by component analysis, if you are confident that the system will be liquid free then the Compressible Gas VLE method should be used since it does not have the overhead of determining the vapour/liquid equilibrium split. The computation time for the fluid properties then becomes several order of magnitudes faster that those involving a liquid phase.

When modelling a system in which two phase effects are important, consideration must be given to the pressures both upstream of the sources and within the flare piping. The Vapour Pressure VLE method, which is the fastest of the multiphase methods, is, strictly speaking, only valid for pressures below 10 bar. The reduced temperature of the fluid should also be greater than 0.3. Experience has shown that it also works to an acceptable degree of accuracy for flare system analysis at

Calculations 11-15

pressures well beyond this. If speed is an issue, then it is recommended that a scenario with as many active sources as possible be rated both using one of the cubic equations of state and this method. If acceptable agreement between the results is achieved then it may be reasonably assumed that the extrapolation is valid.

11.3.3 Sizing CalculationsThe final calculations upon which a flare system is built should of course be made using the most detailed model consistent with the quality of data available, but for initial sizing calculations a number of points should be considered when selecting appropriate calculation methods.

• There is not generally a great deal of difference between thepressure drops calculated for a two phase system, whethercalculated by treating the system as a compressible gas or as atwo phase fluid. This occurs since as the fluid condenses thevelocities will decrease but the two-phase friction factor willincrease.

• Unless choked flow is allowed in the system, the back pressureon each source should not vary greatly with line size. Thespecification of a reasonable fixed downstream temperature foreach source for use with the ideal gas enthalpy model shouldtherefore give reasonable results.

The recommended procedure for performing sizing calculations is as follows:

1. Build the network using reasonable estimates for the pipe diameters. Estimate the diameters from:

where: d = Diameter (m)

W = Mass flow (kg/s)

P = Tip pressure (bar abs)

M = Design mach number

2. Rate the network for all the scenarios with your desired detailed model for the VLE and enthalpies. This will give reasonable temperatures downstream of each source.

(11.1)dW

300PM------------------=

11-15


11-16

3. Copy the calculated temperatures downstream of each source to the source data by the Refresh Source Temperatures option under the Tools menu.

4. Size the network for all scenarios using Compress Gas VLE and Ideal Gas enthalpies.

5. Rate the network for all the scenarios with your desired detailed model for the VLE and enthalpies. If there are any design violations, make a debottlenecking calculation with these methods.

Databases 12-1

12 Databases

12-1

12.1 Database Features ..................................................................................... 3

12.1.1 Selection Filter ....................................................................................... 312.1.2 Manoeuvring Through the Table ............................................................ 412.1.3 Printing................................................................................................... 512.1.4 Adding/Deleting Data ............................................................................. 5

12.2 Setting The Password ................................................................................ 5

12.3 Pipe Schedule Database Editor ................................................................ 6

12.4 Fittings Database Editor ............................................................................ 7

12.5 Component Database Editor ..................................................................... 8

12-2

12-2

Databases 12-3

The data for the various installable components of the model are stored in user-modifiable database files.

The database files are:

• SCHEDULE.MDB - The pipe schedule database. This containsdata for both carbon steel and stainless steel pipe.

• FITTINGS.MDB - The pipe fittings database.• COMPS.MDB - The pure component database.

These files are initially installed to the Database sub-directory in your main FLARENET directory.

The databases may be password protected by a single password common to each. If the password has been disabled, or an incorrect access password has been entered, the databases may be reviewed in read-only mode (note that original data is always read-only). You must have defined an access password before any database can be edited.

12.1 Database Features

12.1.1 Selection FilterThe Selection Filter may be used to restrict the data which is shown. You may use the following wildcard characters:

• ? - Represents a single character.• * - Represents a group of characters of undefined length.• Any filter string has an implied * character at the end.

Some examples are shown below:

You may add and edit your own data to the databases. However, you cannot edit or delete any of the original data.

Filter Application Result

*0 Pipe Schedule 10, 20, 30, 40, 60, 80, 100, 120,140, 160

1?0 Pipe Schedule 100, 120, 140, 160

1* Pipe Schedule 10, 100, 120, 140, 160

*90* Fittings All 90 degree bends and elbows

*Entrance* Fittings All Pipe Entrance fittings

*thane Components Methane, Ethane

M* Components Methane, Mcyclopentane, etc.

As you navigate through the table, you will see that the standard database records are shown in black. User-defined records, which may be edited, are shown in blue.

12-3

12-4 Database Features

12-4

12.1.2 Manoeuvring Through the Table

Click on the table to select a record, then navigate through the table using the navigator and scroll bar controls.

Figure 12.1

Indicates theselected record

Go to first record

Go to previousrecord

Go to lastrecord

Go to next recordUse this scroll bar to manoeuvrethrough the Properties (applicable onlyto the Component Database Editor ).

Use this scrollbar to movethrough thedatabase list.

Databases 12-5

12.1.3 PrintingSelect the Print All button to print the pipe schedule, fittings or component data, depending on which editor you are currently using. FLARENET prints formatted output using the default printer settings.

12.1.4 Adding/Deleting DataWhen the Add button is clicked, the cursor will move to the last record on the table and insert a new record that contains dummy data. You should override this data with your actual data. Note that user-defined data is shown in blue.

When you add items, they will then become immediately available to the simulation.

Select the Delete button to delete the current record. You can only delete your own data.

Click OK to close the Database Editor view.

12.2 Setting The PasswordTo set or modify the password:

1. Select Set Password from the Database menu on the menu bar.

The Password Editor dialog box will now be displayed.

2. Enter your existing password in the Old Password field.

3. Enter your new password in both the New Password and Confirm New Password field and then click OK, or Cancel to abort the procedure.

Figure 12.2

Print All Button

Add Button

Add Button

If you have already set your password, you first need to enter the existing password before supplying the new one.

12-5

12-6 Pipe Schedule Database Editor

12-6

12.3 Pipe Schedule Database Editor

The Pipe Schedule Database Editor allows you to view the pipe schedule data for all pipes in the database, and to add and edit user-defined entries.

To use the Pipe Schedule Database Editor, select Pipe Schedule from the Database menu. After you enter the password, the Pipe Schedule Database Editor view will be displayed, as shown in Figure 12.3.

Select the material you wish to view using the Material drop down. This may be either Carbon Steel or Stainless Steel.

The Nominal Diameter, Schedule, Internal Diameter, Wall Thickness and Group for each entry is tabulated.

For information on the Database view features that are common to the Pipe Schedule, Fittings and Components Databases, see Section 12.1 - Database Features.

Figure 12.3

If you have already set your password, you will need to enter the password before accessing the databases.

Databases 12-7

12.4 Fittings Database Editor

The Fittings Database Editor allows you to view the pipe fittings data for all fittings types in the database, and to add and edit user-defined entries.

To display the Fittings Database Editor, select Pipe Fittings from the Database menu. After you enter the password, the Fittings Database Editor view will be displayed, as shown in Figure 12.4.

The description of each fitting, as well as the A and B term in the pipe fitting equation is tabulated. The Reference defines the literature source for the data.

The pipe fitting equation is:

K = A + BFt

For information on the Database view features that are common to the Pipe Schedule, Fittings and Components Databases, see Section 12.1 - Database Features.

Figure 12.4

12-7

12-8 Component Database Editor

12-8

12.5 Component Database Editor

The Component Database Editor allows you to view the component data for all the pure components in the database, and to add and edit user defined entries.

To display the Component Database Editor, select Component from the Database menu. After you enter the password, the Component Database Editor view will be displayed, as shown in Figure 12.5.

The data for each component in the database is tabulated.

For information on the Database view features that are common to the Pipe Schedule, Fittings and Components Databases, see the next section.

Figure 12.5

Databases 12-9

12.5.1 Importing Component DataAdditional components may be added to the database via an ASCII file whose format is given in Appendix B - File Format.

The component data file can be read into FLARENET by selecting the Import Button on the Component Database Editor view. Note the Import button is unique to the Component Database Editor. This feature allows you to specify the text file, which must be created previously within HYSIM, on the Select Import File view.

A utility to create this file from a HYSIM case is supplied. Two steps are necessary in order to import component data from HYSIM Version 2.60 into the component database.

1. Export the component data from HYSIM. A calculator program must be executed within HYSIM in order to convert the component data to the proper format.

2. Import the component data into FLARENET, via the component database editor.

In order to create the HYSIM transfer file:

1. Load the HYSIM case containing the component data into HYSIM.

2. At the main HYSIM command line prompt, type the command !EXPORT. You must previously have copied the file EXPORT.HCL into the HYSIM working directory from the \HYSIM directory under your main program directory. This need be done only once.

3. When prompted for the name of the export file, enter the file name. This file will be given the extension .TXT. The transfer file will now be created (in your HYSIM directory).

Figure 12.6

Print All Button

12-9

12-10 Component Database Editor

12-10

Viewing Data and Results 13-1

13 Viewing Data and Results

13.1 Components Data....................................................................................... 3

13.2 Scenarios Data ........................................................................................... 3

13.3 Pipes Data ................................................................................................... 4

13.4 Sources Data .............................................................................................. 4

13.5 Nodes Data.................................................................................................. 5

13.6 Messages .................................................................................................... 6

13.6.1 Problems Tab ......................................................................................... 613.6.2 Data Echo Tab........................................................................................ 613.6.3 Solver Tab .............................................................................................. 713.6.4 Sizing Tab............................................................................................... 713.6.5 Loops tab ............................................................................................... 8

13.7 Pressure/Flow Summary ........................................................................... 8

13.8 Compositions ............................................................................................. 9

13.9 Physical Properties .................................................................................... 9

13.10 Profile ...................................................................................................... 11

13.11 Flow Map ................................................................................................. 12

13.12 Scenario Summary................................................................................. 13

13.13 Graph Control ......................................................................................... 14

13.13.1 Control Tab......................................................................................... 1513.13.2 Axes Tab ............................................................................................ 1613.13.3 ChartStyles Tab.................................................................................. 17

13-1

13-2

13-2

13.13.4 Legend Tab ........................................................................................ 1813.13.5 ChartArea Tab.................................................................................... 1913.13.6 Plot Area Tab...................................................................................... 20

Tabulated Data and Results can be viewed from the View menu in the menu bar.

13.1 Components DataProperties for all components in the current case can be viewed by selecting Data and then Components from the View menu. Alternatively, you can use the key combination <Alt><V><D><C>.

Components can be edited, on the Component Editor view, by double clicking on any cell in the appropriate row. For more information on editing the components see Section 7.2 - Adding/Editing Components.

13.2 Scenarios DataScenario data for all the scenarios in the case can be viewed by selecting Data and then Scenarios from the View menu. Alternatively, you can use the key combination <Alt><V><D><S>.

Figure 13.1

Figure 13.2

For all of these views, columns can be resized and moved as described in Section 5.5.1 - Changing Column Width and Section 5.5.2 - Changing Column Order.

13-3

13-4 Pipes Data

13-4

The Scenario Editor can be accessed by double clicking on any cell in the appropriate row. See Section 8.1 - Adding/Editing Scenarios for more information on editing scenarios.

13.3 Pipes DataProperties of the pipe network on a segment-by-segment basis can be viewed by selecting Data and then Pipes from the View menu. Alternatively, you can use the key combination <Alt><V><D>.

You can edit an individual segment by double clicking on any cell in the appropriate row. See Section 9.1 - Adding/Editing a Pipe for more information on editing pipe segments.

13.4 Sources DataSource data can be viewed by selecting Data and then Sources from the View menu. Alternatively, you can use the key combination <Alt><V><D><S>.

Figure 13.3

Figure 13.4

You can edit an individual source by double clicking on any cell in the appropriate row. See Section 10.3 - Sources for more information on editing sources.

To view source data for a different scenario select the appropriate scenario in the scenario selector on the toolbar, and the Sources view will change accordingly.

13.5 Nodes DataProperties for all the nodes in the current case can be viewed by selecting Data and then Nodes from the View menu. Alternatively, you can use the key combination <Alt><V><D><N>.

You can edit an individual node by double-clicking on any cell in the appropriate row. For information on editing nodes see Section 10.1 - Node Manager.

Figure 13.5

To change scenarios, you could select the appropriate scenario tab, or select one from the Scenario Manager.

13-5

13-6 Messages

13-6

13.6 MessagesMessages can be viewed by selecting Results and then Messages from the View menu. Alternatively, you can use the key combination <Alt><V><R><M>.Note that they can be viewed only after you have run the calculations.

13.6.1 Problems TabAny violations of the design constraints are shown on this tab.

13.6.2 Data Echo TabThe Data Echo tab shows the options chosen for the calculation.

Figure 13.6

Figure 13.7

The messages that are displayed depend on the Message options you have selected (see Section 11.1.3 - Warnings Tab).

The following design constraints will be checked for violations :

• Mach Number• Velocity• pv2

• Noise• Back Pressure• Temperature• Slug Flow• Ice Formation


13.6.3 Solver TabThis tab displays any complications encountered by the solver.

13.6.4 Sizing TabThis tab displays the sequence of line size changes during sizing calculations.

Figure 13.8

Figure 13.9

13-7

13-8 Pressure/Flow Summary

13-8

13.6.5 Loops tabThis tab displays the solution history for looped network calculations.

13.7 Pressure/Flow Summary

After running the case, you can view the Pressure/Flow Summary by selecting Results and then Pressure/Flow Summary from the View menu.

Note that if any value violates a design limitation (e.g. - a Mach number is greater than the maximum allowable Mach number), it is displayed in emboldened red.

Figure 13.10

Figure 13.11

The following variables are shown:

• Mass Flowrate• Molar Flowrate• Rated Flowrate• Static Pressure Drop• Noise• Static Source Back Pressure• Upstream (US) Static

Pressure• US Temperature• US Velocity• US Mach No.• US Rho V2• US Energy• Downstream (DS) Static

Pressure• DS Temperature• DS Velocity• DS Mach No.• DS Rho V2• DS Energy• Flow Regime• Static Pipe Acceleration

Loss• Static Pipe Elevation Loss• Static Pipe Fittings Loss• Friction Factor• Reynolds Number• Duty• Overall HTC• External HTC• Internal HTC• Length Used

13.8 CompositionsAfter running the case, you can view the Compositions for each pipe segment by selecting Results and then Compositions from the View menu. You can also use the <Alt><V><R><C> key combination to access the view.

The Composition view may not be available if Save Phase Propertise is not active on the General tab of the Preferences Editor view.

13.9 Physical PropertiesAfter running the case, you can view the Physical Properties for each pipe segment by selecting Results and then Physical Properties from the View menu. Alternatively, you can use the key combination <Alt<V><R><R>.

The Physical Properties view may not be available if Save Phase Propertise is not active on the General tab of the Preferences Editor view.

Figure 13.12

Figure 13.13

The following properties are displayed (Upstream and Downstream):

• Density• Enthalpy• Entropy• Phase Fraction• Heat Capacity• Molecular Weight• Surface Tension• Thermal Conductivity• Viscosity• Z Factor

13-9

13-10 Physical Properties

13-10

You can view properties for different fluid phases by double-clicking anywhere inside the view. Each line expands to display properties for the various phases.

Double clicking again, inside the view, will contract the view to its original state.

Figure 13.14

F = Fluid (Overall)

V = Vapour Phase

L = Liquid Phase

W = Water Phase

M = Mixed (Water & Liquid)

13.10 ProfileAfter running the case, you can view the properties profile by selecting Results and then Profile from the View menu or by pressing the key combination <Alt><V><R>.

You can select the property type from the drop down menu. The Profile displays the profile from the selected Source (which may be chosen from the drop down menu at the top of the view) to the Flare.

Three buttons are available:

Figure 13.15

The following properties profile are available:

• Pressure

• Temperature

• Mass Flow

• Molar Flow

• Mach No.

• Noise

• Rho V2

The property type can be selected from the drop down box.

Select the Source for which you want to display the profile.


Print

Print the graph using the currentprinter settings. The output alsoincludes important information such asthe name of the file, the scenario, andthe model statistics.

SaveSave the graph to a windows metafile.wmf . You will be prompted for the filename and path.

Copy

Copy the graph to the Windowsclipboard. It can then be pasted inother applicable Windows applications(such as your word processor).

13-11

13-12 Flow Map

13-12

The plot can be modified by the 2D Chart Control Properties which is available on object inspecting the plot area. See Section 13.13 - Graph Control for more information on 2D Chart Control Properties view.

13.11 Flow MapThe flow map available in FLARENET displays the flow pattern correlation of Gregory Aziz and Mandhane which is currently the most widely used method. It was based on almost 6,000 flow pattern observations, from a variety of systems, and many independent studies and it is strictly applicable only to horizontal flow. Typically, the superficial gas and liquid velocities in a horizontal pipe are the most important single parameters influencing the flow pattern.

After running the case, you can view the Gregory Aziz and Mandhane flow map by selecting Results and then Flow Map from the View menu or by pressing the key combination <Alt><V><R><W>.

You can display the flow map for each pipe segment by selecting the desired pipe segment from the drop down box on the top of the view. The upstream and downstream condition are marked with a red dot and a label on the flow map. Unless the pipe segment has a single phase flow with a large pressure drop, both upstream and downstream pipe conditions will generally be close to each other.

Figure 13.16


Three buttons are available:

13.12 Scenario SummaryAfter running the case, you can view the Scenario Summary by selecting Results and then Scenario Summary from the View menu.

You can select a source from the drop-down menu at the top of the view.


Print

Print the graph using the currentprinter settings. The output alsoincludes important information such asthe name of the file, the scenario, andthe model statistics.

SaveSave the graph to a windows metafile.wmf . You will be prompted for the filename and path.

Copy

Copy the graph to the Windowsclipboard. It can then be pasted inother applicable Windows applications(such as your word processor).

Figure 13.17

13-13

13-14 Graph Control

13-14

Two buttons are also available:

13.13 Graph ControlYou can customize each individual plot in Flarenet using the Chart Control tool. You can modify many of the plot characteristics, which are categorized into the six tabs of the 2D Chart Control Properties view: Control, Axes, ChartStyles, Legend, ChartArea and PlotArea.

You can open the 2D Chart Control Properties view by object inspecting any spot on an active plot.


Print

Print the results using the currentprinter settings. The output alsoincludes important information suchas the name of the file, scenario, andthe model statistics.

SaveSave the results to an ASCII text file.txt . You will be prompted for the filename and path.

Figure 13.18


13.13.1 Control Tab

The Control tab is used to specify the background border, background and foreground colors and background image. The inner tabs available on the Control tab are:

Figure 13.19

Inner Tab Option Description

Border

Type Select the border type drawn around the area from thedrop down box.

Width Enter the boarder type width in pixels. Valid values arebetween 0 and 20 pixels.

Interior

Background ColorRGB

Enter the RGB value for the specified background color.Valid values are between #000000 and #ffffff.

Background ColorName

Select the color name from the drop down box.

Foreground ColorRGB

Enter the RGB value for the specified foreground color.Valid values are between #000000 and #ffffff.

Foreground ColorName

Select the Color name from the drop down box.

13-15

13-16 Graph Control

13-16

13.13.2 Axes Tab

The Axes tab allows you to customize the plot area, using the following inner tabs:

Figure 13.20


Grid

IsStyleDefault When checked, the GridStyle returns to the default. If thisoption is disabled, it does not apply to the selected axis.

Spacing Specifies the grid increment. If this option is disabled, itdoes not apply to the selected axis.

GridStyle

Pattern List the available line patterns.

Width Specify the width of the line, in pixels.

Color RGB List the RGB value of the line color. Valid values arebetween #000000 and #ffffff.

Color name List the name of the specified line color. To choose a newcolor by its name, click the down arrow or type the nameof the color here.

When displaying Undefined , there is no matching colorname for the specified color.

Font

Description List the current font setting for the text. Click the button onthe right to choose a new font,size, or style.

Sample Shows a sample of how text will appear with the specifiedfont setting.


13.13.3 ChartStyles Tab

The ChartStyles tab allows you to customize how data series look in the chart. The inner tabs available on the ChartStyles tab are:

Figure 13.21

Press the Add button to add a ChartStyle after the selected Style in the list.

Press the Remove button to remove the selected ChartStyle from the list.


FillStyle

Pattern This drop down box lists the available fill patterns.

Color RGB Lists the RGB value of the fill color. Valid values arebetween #000000 and #ffffff.

Color Name Lists the name of the specified fill color. To choose a newcolor by its name, click the down arrow or type the nameof the color here.


LineStyle

Pattern Lists the avaiable line patterns.

Width Specifies the width of the line, in pixels.

Color RGB Lists the RGB value of the fill color. Valid values arebetween #000000 and #ffffff.

Color Name Lists the name of the specified fill color. To choose a newcolor by its name, click the down arrow or type the nameof the color.


SymbolStyle

Shape Lists the available symbol shapes.

Size Specifies the size of the symbol.

Color RGB Lists the RGB value of the symbol color. Valid values arebetween #000000 and #ffffff.

Color Name Lists the name of the specified symbol color. To choose anew color by its name, click the down arrow or type thename of the color here.


13-17

13-18 Graph Control

13-18

13.13.4 Legend Tab

The Legend tab allows you to customize the legend on the following inner tabs:

Figure 13.22


General

Anchor Specifies where the legend is positioned, relative to theChartArea. You can fine-tune the positioning with theLocation inner tab.

Orientation Specifies the layout of items in the Legend.

IsShowing Displays the label, if Series-labels have been defined

Location

Left Specifies the distance from the left edge of the chart tothe area, in pixels. If this option is disabled, you cannotchange the position of this area.

Top Specifies the distance from the top edge of the chart tothe area, in pixels. If this option is disabled, the distancecannot be changed.

Width Specifies the width of the area in pixels. If this option isdisabled, the width cannot be changed.

Height Specifies the height of the area in pixels. If this option isdisabled, the height cannot be changed.

BorderType Specifies the type of border drawn around the area. If this

option is disabled, you cannot change the border type.

Width Specifies the width of the border in pixels.


13.13.5 ChartArea Tab

The ChartArea tab allows you to customize the chart area in detail.

Interior

Background ColorRGB



List the name of the specified background color. Tochoose a new color by its name, click the down arrow ortype the name of the color.

Foreground ColorRGB



List the name of the specified foreground color. To choosea new color by its name, click the down arrow or type thename of the color.

Font

Description List the current font setting for the text. Click the button onthe right to choose a new font, size, or style.

Sample Shows a sample of how text will appear with the specifiedfont setting.


Figure 13.23


Location

Left Specifies the distance from the left edge of the chart tothe area, in pixels. If this option is disabled, you cannotchange the position of this area.

Top Specifies the distance from the top edge of the chart tothe area, in pixels. If this option is disabled, the distancecannot be changed.

Width Specifies the width of the area in pixels. If this option isdisabled, the width cannot be changed.

Height Specifies the height of the area in pixels. If this option isdisabled, the height cannot be changed.

13-19

13-20 Graph Control

13-20

13.13.6 Plot Area Tab

The plot area can be customized on the PlotArea tab using the following inner tabs:

BorderType Specifies the type of border drawn around the area. If this

option is disabled, you cannot change the border type.

Width Specifies the width of the border in pixels.

Interior

Background ColorRGB




Foreground ColorRGB





Figure 13.24


General

IsBoxed Draws a box arount the plot area.

Top Specifies the distance from the top of the chart area to theaxis. Positive values allow space for axis labels; negativevalues let you “zoom in” on a chart.

Bottom Specifies the distance from the bottom of the chart area tothe axis. Positive values allow space for axis labels;negative values let you “zoom in” on a chart.

Left Specifies the distance from the left side of the chart areato the axis. Positive values allow space for axis labels;negative values let you “zoom in” on a chart.

Right Specifies the distance from the right side of the chart areato the axis. Positive values allow space for axis labels;negative values let you “zoom in” on a chart.


Interior

Background ColorRGB




Foreground ColorRGB




Image

File Specifies the file name and path of the image you want toload into the chart element.

Layout Select the way you want the image to be displayed in thebackround.

IsEmbedded When checked, the image is embedded into the chart.When unchecked, the chart looks for the image in thespecified location.

Reset button Click this button to return the chart element background toits default.


13-21

13-22 Graph Control

13-22

PFD 14-1

14 PFD

14-1

14.1 Overview ..................................................................................................... 3

14.2 Object Inspection ....................................................................................... 5

14.2.1 PFD Toolbar Buttons .............................................................................. 514.2.2 Print Options .......................................................................................... 614.2.3 Stream Label Options ............................................................................ 714.2.4 Viewports Option.................................................................................... 7

14.3 Installing Objects ....................................................................................... 8

14.4 Connecting Objects ................................................................................... 9

14.5 Manipulating the PFD................................................................................. 9

14.5.1 Selecting PFD Objects ........................................................................... 914.5.2 Unselecting Objects ............................................................................. 1014.5.3 Moving Objects .................................................................................... 1014.5.5 Regenerate PFD .................................................................................. 11

14.6 Printing and Saving the PFD Image........................................................ 11

14.7 Changing the PFD View Options ............................................................ 12

14-2

14-2

PFD 14-3

14.1 OverviewOne of the key benefits of the Process Flow Diagram (PFD) is that it provides the best representation of the flowsheet as a whole. From this one location, you have an immediate reference to your current progress in building the Flare network.

The PFD has been developed to satisfy a number of functions. In addition to the graphical representation, you can build your flowsheet within the PFD using the mouse to install objects and make connections. You can also reposition objects, resize icons and reroute connections.

The PFD also possesses analytical capabilities in that you can access the Edit views for nodes, pipe segments, and sources which are displayed.

Each object has a specific icon to represent it: The nodes on the objects have been colour coded to show the flow path. The red dot is for upstream flow, the blue dot is for downstream flow whereas magenta is for branch flow in case of a tee or horizontal separator.

Object Icon

Pipe-Segment

Flare Tip

Connector

Tee

Relief Valve

Control Valve

14-3

14-4 Overview

14-4

To open the PFD, select PFD and then Open from the View menu. A separate window with its own tool bar is opened.

Vertical Separator

Horizontal Separator

Orifice Plate

Flow Bleed

Object Icon

Figure 14.1

PFD ToolBar

VerticalScroll Bar

HorizontalScroll Bar

PFD 14-5

14.2 Object InspectionOne of the key features of the FLARENET PFD is the ability to inspect objects in the flowsheet. If you double-click on any pipe-segment, source or node, the appropriate edit view will be opened for that object. PFD Toolbar

There are several tools that helps to simplify your interaction with the PFD. The most basic tools relate to what is displayed in the PFD Window.

14.2.1 PFD Toolbar ButtonsThe PFD toolbar buttons are arranged as follows:

All of these buttons perform an important function as explained below:

Figure 14.2


Print PFDPrint the PFD to the Printer.

Save PFDSave the PFD to file. It is saved ina .wmf format (Windows Metafile).

Copy PFDCopies the PFD to the clipboard,allowing you to paste it into otherapplications.

Toggle GridDisplay

Toggle the grid on and off. Whenthe grid is on, this button will befaded.

Coarser Grid

This button increases gridspacing. All objects you move oradd "snap to" the current gridspacing.

14-5

14-6 Object Inspection

14-6

14.2.2 Print OptionsYou can specify the area of the PFD that you desire to print by selecting the following options available on the PFD button bar.

Finer Grid

This button decreases gridspacing. All objects you move oradd "snap to" the current gridspacing.

Snap To GridOn/Off

Toggles the snap to grid option onand off. When the snap to grid ison all pipe segments and nodeswill be snapped to the closestgrids.

Rotate PipesClockwise

Rotate the selected pipesegments and nodes.

Toggle Direct/Orthogonalconnections

Toggle between bent and straightconnections. All currentconnections (and any connectionsyou subsequently make) willconform to the connection methodyou have selected.

Toggle Arrange/Connect Mode

Toggle between Arrange andConnect modes. Arrange modeallows you to move icons andlabels. Connect mode allows youto graphically connect compatibleobjects. The status bar on thePFD shows which mode isactivated.

ToolboxThis button toggles the Toolboxview.


The Ctrl+Shift+S hot keys snaps the objects to the grid. While in the snap mode, the Status bar displays the word Snap.

Option Description

Print Visible Print part of the PFD visible on the screen.

Print All Print the whole PFD.

Print Selected

Print only the selected part of the PFD. You canhighlight the part of the PFD by clicking once onthe PFD and than dragging the section of PFD.The PFD is printed without the page header andfooter to allow compilation of a multiple tiledimage.

PFD 14-7

14.2.3 Stream Label OptionsBy default, each object on the PFD has a label that displays its name. You can change all object name labels so that the current value of a key variable is shown in the place of each object name.

You can chose between the type of labels for the pipe segments and nodes by selecting the property drop down box on the PFD button bar.

The box on the right side of the property drop down box displays the default units for the chosen property.

If the object label is red in colour it indicates that the object violated the limits setup in the Scenarios Editor or the fluid is in the slug region. Some of the possible causes are ice formation, slug flow, temperature violation and source back pressure. If the object label is grey in colour it indicates that the object is ignored for calculation by activating the Ignore check box on the object property view.

14.2.4 Viewports OptionYou have the option to change the PFD viewports. By default, a single PFD viewport is defined as Overall. You can specify a different setting for each viewport including percent zoom and stream labels.

Add a New Viewport

New viewports can be added to the PFD by right clicking the title bar of the PFD view and selecting the Add Viewport from the displayed menu.

Delete an Existing Viewport

You can delete an existing viewport from the PFD by right clicking the PFD view title bar and selecting the Delete Viewport from the menu.

Figure 14.3

The following properties are available:

• Energy Flow

• Length

• Mach Number

• Mass Flow

• Molecular Weight

• Molar Flow

• Noise

• Nominal Diameter

• Pressure

• Rho V2

• Temperature

• Vapour Fraction

• Velocity

• Velocity (Liq)

• Velocity (Vap)

Scroll downto see morevariables.

14-7

14-8 Installing Objects

14-8

Print Viewport

Visible viewports can be printed to a selected printer by choosing the Print Window from the menu.

14.3 Installing ObjectsThe PFD can be used to install objects into the flowsheet, as well as connect compatible objects. Object specifications are then supplied via the appropriate Property view which can be accessed by double-clicking the object icon.

The PFD Toolbox is used to install operations. The Toolbox can be accessed by doing one of the following:

• Open the View menu and then open the PFD sub-menu. SelectToolbox .

• Press the <F4> key.• Press the Toolbox button on the PFD button bar.

The procedure for installing operations via the Toolbox is as follows:

1. Click the desired object in the PFD Toolbox. You will see the button being depressed.

2. Click in the specific area in the PFD where you want to place the object icon. The object then appears in the PFD.

3. Drag and drop the desired object using the secondary mouse key.

To delete an object, select the object you wish to delete, then press the <Delete> key on the keyboard.

Figure 14.4

Tee

Flare Tip

HorizontalSeparator

Connector

Relief Valve

PipeSegment

VerticalSeparator

ControlValve

FlowBleed

OrificePlate

If the Edit Objects on Add check box is activated, the object editor view will be open for each new object which is added to the PFD.

PFD 14-9

14.4 Connecting ObjectsTo connect objects:

1. Enter connect mode by clicking the Connect button on the tool bar. This toggles between connect and arrange modes.

2. Click on the source object to select it.

3. Move the mouse pointer over the central handle point (blue fill instead of white for this handle point) then press the left mouse button.

4. Drag off the source object and over the destination object.

5. Release the left mouse button.

14.5 Manipulating the PFD

There are a number of features built into the PFD interface to modify its appearance. The manipulations apply to all objects that are installed in the PFD.

14.5.1 Selecting PFD ObjectsTo select a single object, position the mouse pointer on top of the object, then click once with the left mouse button. The selected object will have eight small boxes outlining its border. These small boxes are used to size an object.

Note that text must be selected separately; that is, when you select an object, the corresponding text is not also automatically selected.

There are two methods you can use to select multiple objects:

Method One1. If the objects are all contained within the same area, the quickest

and easiest way is to marquee select that group. Press the left mouse button (outside the group), and drag the mouse so that a

Arrange Mode button

Connect Mode button

FLARENET allows you to select single objects as well as multiple objects, but in order to select an object, you must be in Arrange mode.

A pipe which has been selected.

A pipe and the corresponding text which have been selected.

14-9

14-10 Manipulating the PFD

14-10

box appears.

2. Continue dragging until this box contains all the objects that you want selected.

3. When you release the mouse button, each object will have its own rectangular box surrounding it, indicating it has been selected.

Method Two1. Position the mouse pointer on the first object in the PFD you want

to select.

2. Press the left mouse button to select this object.

3. To select a second object, hold down the <Shift> key or <Ctrl> key, then click on the second object with the left mouse button. Two objects will now be selected.

4. Continue this method for the remainder of the objects you wish to select.

14.5.2 Unselecting ObjectsThe following methods can be used:

• Click on an empty spot in the PFD with the left mouse button.• To unselect only one item, press the <Shift> key and click on

the object with the left mouse button.

14.5.3 Moving ObjectsYou can move objects individually, or as a group.

1. Select the item or items you want to move.

2. Position the mouse pointer on one of the objects and press the left mouse button.

3. Drag the mouse to the new position on the PFD and release the mouse button. All selected items will move to the new location.

14.5.4 Locating Objects on the PFDYou can locate individual object on the PFD by pressing the <Ctrl><Shift><F> hot keys, which displays the Locate Object view. You can select individual objects from the list by clicking on them using the primary mouse key. The object will be highlighted on the PFD.

If the grid is on, all objects which are moved will "snap to" the grid. Their movement will be constrained to the grid spacing.

PFD 14-11

14.5.5 Regenerate PFDUse this function to reposition all objects in a logical manner. Select PFD and then Regenerate from the View menu.

This feature is a great time-saver especially when you have not laid out the PFD as you were building the case. Rather than placing all objects yourself, regenerate the PFD in this manner. You can then make additional changes to further fine-tune your PFD. Regenerate PFD option places all the objects along a vertical path in the best possible manner. It is not recommended to regenerate well laid out PFDs.

14.6 Printing and Saving the PFD Image

The first three toolbar buttons are used to transfer the PFD to the printer, Windows Metafile and to memory.

To print the PFD using the current Print Setup, press the Print PFD button. For more information on the Print Setup, see Section 15.1.3 - Printer Setup.

To save the PFD in a .wmf format (Windows Metafile), press the Save PFD button. You will be prompted to enter a file name:

Enter the file name and path, then click OK. To view the PFD, you can then use a program which is capable of reading .wmf files (such as Corel DrawTM).

Figure 14.5

Print PFD Button

Save PFD Button

14-11

14-12 Changing the PFD View Options

14-12

To copy the PFD to the clipboard, select the Copy PFD button. You can then paste it into other Windows applications as you would with any Windows object.

14.7 Changing the PFD View Options

When in the PFD window, FLARENET allows you to select several view options, namely, Grid, Rotate, and Connection. All of these options are available via toolbar buttons. The following is a brief description of each button:

Copy PFD Button

Button Description

Grid

When the Grid Toolbar button is selected, a gridis superimposed upon the existing PFD. Thereare also 3 buttons beside the Grid Toolbar button.These buttons allow you to either increase ordecrease the grid density as well as snap theelements to grid.

Rotate

You can select to rotate or mirror (flip) theselected object about its centre in one of thefollowing five ways:

• Rotate 90

• Rotate 180

• Rotate 270

• Flip Y

• Flip X

Toggle Direct/Orthogonal

This button allows you to toggle between directand orthogonal connecting lines.

Exporting, Importing and Printing 15-1

15 Exporting, Importing and Printing

15-1

15.1 Printing........................................................................................................ 4

15.1.2 Location-Specific Printing ...................................................................... 715.1.3 Printer Setup .......................................................................................... 7

15.2 Importing Source Data............................................................................... 8

15.2.1 ASCII Text Files...................................................................................... 815.2.2 Importing HYSYS Source Data............................................................ 1315.2.3 Importing from Microsoft Access.......................................................... 16

15.3 Exporting to Microsoft Access ............................................................... 17

15-2

15-2


Data can be either exported to, or imported from a number of external sources. The printing of data and results is included as an export function since the printing functionality incorporated within FLARENET is also used to export data and results in a number of industry standard formats.

The following data may be exported from FLARENET:

• All data and results may be printed on any Windows-compatible printer.

• All data and results may be saved as either ASCII text,Comma-separated text, or Tab-separated text.

• All data and results may be saved in a Microsoft Accessdatabase.

The following data may be imported into FLARENET:

• Source data from the HYSIM and HYSYS process simulators.This data is transferred via an ASCII file. Consequently, itshould be possible to import source data from any externalsource provided it conforms to this file format.

• Component data from the HYSIM process simulator, which isdiscussed in Section 12.5.1 - Importing Component Data .This data is transferred via an ASCII file. Consequently, itshould be possible to import component data from any externalsource provided it conforms to this file format.

• Data from a Microsoft Access database. The format of thisdatabase is given in the appendices.

15-3

15-4 Printing

15-4

15.1 PrintingIn order to print either model data or calculation results that are not specific to a single source, select Print from the File drop down menu. The Print view will be displayed.

Select the items that you wish to print by checking the appropriate boxes in the Database, Data and Results group box.

By default, the printout is only for the current scenario. Check the All Scenarios box if you want printouts for all of the scenarios.

If you want the results to be saved as an ASCII text file, check the Print To File box. You will then be able to select the file format via the Text File Format drop-down menu. The following file formats are supported:

• Text - Saves the data in ASCII format, with all values separatedby spaces.

• CSV, Comma Separated - Saves the data in ASCII format,with all values separated by commas.

• TSV, Tab Separated - Saves the data in ASCII format, with allvalues separated by tabs.

Figure 15.1


If you checked the Print To File check box, the Print To File view will be displayed when you click OK.

Select or directly enter the file, then click OK.

If you did not check the Print To File check box, the results will immediately be printed when you click OK on the Print view.

15.1.1 .FMT FilesThe printouts can be customised to a limited extent using a series of ASCII text files with the extension ".fmt". These files may be edited using any ASCII text editor such as the NOTEPAD application distributed with Microsoft Windows.

The default ".fmt" files for each printed report are:

Figure 15.2

Report .fmt File

Component Database DbComps.fmt

Pipe Fittings Database DbFittings.fmt

Pipe SchedulesDatabase

DbSchedules.fmt

Components Comps.fmt

Scenarios Scenarios.fmt

Pipes Pipes.fmt

Source Sources.fmt

Nodes Nodes.fmt

Messages Messages.fmt

Pressure/Flow Summary Summary.fmt

Compositions MoleFracs.fmt

15-5

15-6 Printing

15-6

By default, these files are located in the Flarenet program directory. You can change the location and ".fmt" file for each report via the Reports tab on the Preferences Editor view.

These files conform to the format shown in Appendix B - File Format.

Physical Properties Properties.fmt

Scenario Summary ScenSum.fmt

Report .fmt File

Figure 15.3

15.1.2 Location-Specific PrintingResults that are specific to a single source must be printed individually. The Profile, Flow Map and Scenario Summary views each have a Print button which can be selected to print the displayed data. The Profile view is shown here:

15.1.3 Printer SetupTo edit the printer setup, select Printer Setup from the File menu or press the <Alt><F><R> key combination. This is used to select the default/specific printer, print orientation, paper size, paper source, and any other settings applicable to your printer. It is similar to the Printer Setup commands in other Windows applications. Note that the Print

Figure 15.4

Information on printing the PFD is given in Section 14.6 - Printing and Saving the PFD Image.

See Section 13.10 - Profile and Section 13.12 - Scenario Summary for more details.

Print

Save

Copy

15-7

15-8 Importing Source Data

15-8

Setup Options vary for different printers.

15.2 Importing Source DataFLARENET allows you to import source data through multiple ways. You could load up data from a specially formated text file or directly from HYSYS, as well as using existing Access database to import data.

15.2.1 ASCII Text FilesTo access the ASCII text files containing the source data, select Import from the File menu and then select Text File Sources from the Import

Figure 15.5


15-9

submenu. The Text Import of Source Data view will be displayed:

The following objects are available on this view:

Figure 15.6

Object Description

File

Specify the file from which the source data will beimported. Pressing the Browse button opens theText File For Source Data view. Select the textfile from this view and press the OK button. Pressthe Open button to load the source data file inFLARENET.

P/T Location

Specify the pressure and temperature location forthe source. If Upstream is selected from the dropdown box, the relieving pressure and the actualInlet temperature specification is copied from thesource data file. If Downstream is selected fromthe drop down box, the allowable back pressureand the outlet temperature is copied from thesource data file.

Component Data

Specify the action to be taken if similiarcomponents exist in the text file and theFLARENET case. The Ignore Existing selectiondoes not copy the same components from thetext file to the FLARENET case, whereas theOverwrite Existing copies all the componentdata from text file to the FLARENET case.

Stream List all the streams available to be imported inFLARENET.

Source Select the source to which the source data will beimported.

ScenariosList all the scenarios available in the FLARENETcase. You can select the scenarios to which thedata will be copied.


15-10

Example: Importing from HYSIM

Two steps are necessary in order to import source data from HYSIM Version 2.6 or later.

1. Export the source data from HYSIM. A calculator program must be executed within HYSIM in order to convert the source data to the proper format.

2. Import the source data into FLARENET, using the File Import feature.

In order to create the HYSIM transfer file:

1. Load the HYSIM case containing the source data into HYSIM.

2. At the main HYSIM command line prompt, type the command !FNW26 as shown below. You must previously have copied the file FNW25.HCL into the HYSIM working directory from the \HYSIM program directory under your main program directory. This need be done only once.

3. When prompted for the name of the export file as shown below, enter the file name. This file will be given the extension .PRN.

4. When prompted for the pressure and temperature location as shown below, define whether the conditions for the streams within the simulation case represent either conditions upstream or downstream of the source valve.

Figure 15.7

Figure 15.8

Figure 15.9


5. When prompted for the streams to export as shown below, select as many streams as you wish (do not select energy streams), by using the standard HYSIM stream selection methods.

The transfer file will now be created (in your HYSIM directory).

In order to import the HYSIM transfer file:

1. Select Import then Text File Sources from the File menu. When prompted for the Text Import File as shown below, enter the file name.

2. On the Text Import Of Source Data view, enter the source number for the selected scenario within the FLARENET model that corresponds to each HYSIM stream. Specify the P/T Location and the Component Data from the drop down box.

Figure 15.10

Figure 15.11

15-11


15-12

Example 2: Importing From HYSYS

Two steps are necessary in order to import source data from HYSYS.1.

1. Export the source data from HYSYS. A program must be executed externally to HYSYS in order to convert the source data to the proper format.

2. Import the source data into FLARENET, using the File Import feature.

In order to create the HYSYS transfer file:

1. Run the FNETEXPT.EXE program. This is initially installed in the \HYSYS directory under your main program directory. The following dialog box will be displayed.

2. Enter the name of the HYSYS file containing the streams of interest, then click Open. The Flowsheet Streams list will then contain a list of all the material streams in the file.

3. Select the streams to export as well as the location that the pressure and temperature represent (P&T Location).

4. Click Export. Select a name for the transfer file then click OK. The transfer file will now be created.

Figure 15.12


In order to import the HYSYS transfer file:

1. Select Import then Text File Sources from the File menu. When prompted for the Text Import File as shown below, enter the file name.

2. On the Text Import Of Source Data view, enter the source number for the selected scenario within the FLARENET model that corresponds to each HYSYS stream. Specify the P/T Location and the Component Data from the drop down box.

15.2.2 Importing HYSYS Source DataThe Source data can also be imported directly from HYSYS. To access the HYSYS files containing the source data, select Import from the File menu and then select HYSYS Sources from the submenu. The Hysys

Figure 15.13

Blank source name fields means that the stream data is not imported

15-13


15-14

Import of Source Data view will be displayed:

The following objects are available on this view:

Figure 15.14

Object Description

File

Specify the HYSYS file from which the sourcedata will be imported. Pressing the Browsebutton opens the Hysys File For Source Dataview. Select the HYSYS file from this view andpress the OK button. Press the Open button toload the source data file in FLARENET.

P/T Location

Specify the pressure and temperature location forthe source. If Upstream is selected from the dropdown box, the relieving pressure and the actualInlet temperature specification is copied from thesource data file. If Downstream is selected fromthe drop down box, the allowable back pressureand the outlet temperature is copied from thesource data file.

Component Data

Specify the action to be taken if similiarcomponents exist in the HYSYS file and theFLARENET case. The Ignore Existing selectiondoes not copy the same components from theHYSYS file to the FLARENET case, whereas theOverwrite Existing copies all the componentdata from HYSYS file to the FLARENET case.

Stream List all the streams available in HYSYS file whichcan be imported in FLARENET.


Source Select the source to which the source data will beimported.

ScenariosList all the scenarios available in the FLARENETcase. You can select the scenarios to which thedata will be copied.

Object Description

15-15


15-16

15.2.3 Importing from Microsoft Access

Source data can be imported from a Microsoft Access database. In order to import source data:

1. Select Access Database from the Import sub-menu under the File menu on the main program menu bar. The Import Data From Access Database view will be displayed.

2. Select the file to be imported by either typing or selecting the appropriate file in the File Name box. The search directory and drive can be changed using the Directories and Drives boxes.

3. Click OK.

FLARENET looks for data in the following tables in the Access data file.

• Components• Connectors• ControlValves• FlowBleeds• HorizontalSeparators• OrificePlates• Pipes• PressureFlowSummary• ReliefValves• Tees• Tips• VerticalSeparators

For a description of fields contained in each of these tables see Appendix B - File Format.

Figure 15.15


15.3 Exporting to Microsoft Access

In order to save the components and nodes in a Microsoft Access database, select Export and then Access Database from the File menu. The Export Data To Access Database view will be displayed:

You can open the Access data file from within Access. This file contain the following tables, which will be created even if they contain no data.


For a description of fields contained in each of these tables look in Appendix B - File Format.

Figure 15.16

15-17

15-18 Exporting to Microsoft Access

15-18

Theoretical Basis A-1

A Theoretical Basis

A-1

A.1 Pressure Drop .............................................................................................. 3

A.1.1 Pipe Pressure Drop Method .................................................................... 3A.1.2 Fittings Pressure Drop Methods ............................................................ 11

A.2 Vapour-Liquid Equilibrium........................................................................ 15

A.2.1 Compressible Gas ................................................................................. 15A.2.2 Vapour Pressure .................................................................................... 16A.2.3 Soave Redlich Kwong............................................................................ 17A.2.4 Peng Robinson ...................................................................................... 18

A.3 Physical Properties ................................................................................... 19

A.3.1 Vapour Density ...................................................................................... 19A.3.2 Liquid Density ........................................................................................ 19A.3.3 Vapour Viscosity .................................................................................... 20A.3.4 Liquid Viscosity ...................................................................................... 20A.3.5 Thermal Conductivity............................................................................. 23A.3.6 Enthalpy................................................................................................. 24

A.4 Noise ........................................................................................................... 27

A-2

A-2


A.1 Pressure Drop

A.1.1 Pipe Pressure Drop Method

Vapour Phase Pressure Drop Methods

Pressure drop can be calculated either from the theoretically derived equation for isothermal flow of a compressible fluid in a horizontal pipe2:

where: G = Mass flow

a = Cross sectional area of pipe

P1 = Upstream pressure

P2 = Downstream pressure

R = Universal gas constant

f = Moody friction factor

φ = Internal diameter

L = Equivalent length

T = Temperature

M = Molecular weight

or from the theoretically derived equation for adiabatic flow of a compressible fluid in a horizontal pipe2:

where: G = Mass flow

a = Cross sectional area of pipe

P1 = Upstream pressure

(A.1)Ga----

2 P1

P2------ ln

M P2

2 P2

1–( )2RT

--------------------------------- 2fLφ--- G

a----

2+ + 0=

(A.2)4fLφ--- γ 1–

2γ-----------

P1

V1------

aG----

2+

1V1

V2------

2–

γ 1+

γ-----------

V2

V1------ ln–=

A-3

A-4 Pressure Drop

A-4

R = Universal gas constant

V1 = Upstream velocity

V2 = Downstream velocity

f = Moody friction factor


L = Equivalent length

γ = Ratio of specific heats

The Moody friction factor is calculated using an equation appropriate for the flow regime. These equations correlate the friction factor to the pipe diameter, Reynolds number and roughness of the pipe4:

Turbulent Flow (Re > 4000)

The friction factor may be calculated from either the Round equation:

where: f = Moody friction factor

Re = Reynolds number


e = Absolute pipe roughness

Or from the Chen21 equation:


Re = reynolds number



(A.3)1

f----- 3.6

Re

0.135 Reeφ--- 6.5+

-------------------------------------------

log=

(A.4)1

f----- 4

e φ⁄3.7065----------------

5.0452Re

----------------e φ⁄( )1.1098

2.8257---------------------------

7.149Re

-------------

0.8981+

log–

log–=

Transition Flow (2100 Re 4000)





Laminar Flow (Re < 2100)



The Darcy friction factor is given by:


fd = Darcy friction factor

2-Phase Pressure Drop

Beggs and Brill

The Beggs and Brill9 method is based on work done with an air-water mixture at many different conditions, and is applicable for inclined flow. In the Beggs and Brill correlation, the flow regime is determined using the Froude number and inlet liquid content. The flow map used is based on horizontal flow and has four regimes: segregated, intermittent, distributed and transition. Once the flow regime has been determined, the liquid hold-up for a horizontal pipe is calculated, using

≤ ≤

(A.5)1

f----- 4.0

e3.7φ---------- log–

5.02Re

----------e

3.7φ---------- 5.02

Re----------

e3.7φ----------

13.0Re

----------– log–

log–=

(A.6)f16.0Re

----------=

(A.7)fd 4 f•=

Although the Beggs and Brill method was not intended for use with vertical pipes, it is nevertheless commonly used for this purpose, and is therefore included as an option for vertical pressure drop methods.

A-5

A-6 Pressure Drop

A-6

the correlation applicable to that regime. A factor is applied to this hold-up to account for pipe inclination. From the hold-up, a two-phase friction factor is calculated and the pressure gradient determined.

The boundaries between regions are defined in terms of two constants and the Froude number 10:

where: x = ln(λ)

λ = input liquid content = qliquid/(qliquid +qgas)

q = in situ volumetric flowrate

Figure A.1

0.0001 0.001 0.01 0.1 10.1

1

10

100

1000

Input Liquid Content

Fro

ud

e N

um

ber

Distributed

Segregated

Intermittent

Transition

Beggs and Brill Flow Regimes

(A.8)

(A.9)

L1 4.62– 3.757x– 0.481x2

– 0.0207x3

–( )exp=

L2 1.061 4.602x– 1.609x2

– 0.0179x3

– 0.000635x5

+( )exp=


According to Beggs and Brill:

1. If the Froude number is less than L1, the flow pattern is segregated.

2. If the Froude number is greater than both L1 and L2, the flow pattern is distributed.

3. If the Froude number is greater than L1 and smaller than L2 the flow pattern is intermittent.

Dukler Method

The Dukler10 method breaks the pressure drop into three components - Friction, Elevation and Acceleration. The total pressure drop is the sum of the pressure drop due to these components:

where: ∆PTotal = Total change in pressure

∆PF = Change in pressure due to friction

∆PE = Change in pressure due to elevation

∆PA = Change in pressure due to acceleration

The pressure drop due to friction is:

where: fTP = Two-phase friction factor (determined empirically)

L = Equivalent length of the pipeline (ft)

Vm = Velocity of the two-phase mixture in pipeline assuming equal velocity (ft/s)

ρm = Density of two-phase mixture (lb/ft3)

gc = Gravitational constant (32.2 lbm-ft/lbf-s2)

D = Inside diameter of pipe (ft)

(A.10)∆PTotal ∆PF ∆PE ∆PA+ +=

(A.11)∆PF

2fTPLVm2ρm

144gcD--------------------------------=

A-7

A-8 Pressure Drop

A-8

The pressure drop due to elevation is as follows:

where: Eh = Liquid head factor (determined empirically)

ρL = Liquid density

ΣH = Sum of elevation changes

The pressure drop due to acceleration is usually very small in oil/gas distribution systems, but becomes significant in flare systems:

where: A = Cross-sectional area

ρg = Gas density

QGPL = Volume of gas flowing at pipeline temperature and pressure (ft3/hr)

QLPL = Volume of liquid flowing at pipeline temperature and pressure (ft3/hr)

RL = Liquid holdup in pipeline as a percentage of pipeline capacity

θ = Angle of the pipe bend

Orkiszewski Method

The Orkiszewski11,12 method assumes there are four different flow regimes existing in vertical two-phase flow - bubble, slug, annular-slug transition and annular-mist.

The bubble flow regime consists mainly of liquid with a small amount of a free-gas phase. The gas phase consists of small, randomly distributed gas bubbles with varying diameters. The gas phase has little effect on the pressure gradient (with the exception of its density).

In the slug flow regime, the gas phase is most pronounced. The gas

(A.12)∆PE

EhρL H144

------------------------=

(A.13)∆PA1

144gcA2

---------------------ρgQGPL

2

1 RL–--------------------

ρLQLPL2

RL--------------------+

DS

ρgQGPL2

1 RL–--------------------

ρLQLPL2

RL--------------------+

US

θcos–=


bubbles coalesce and form stable bubbles of approximately the same size and shape. The gas bubbles are separated by slugs of a continuous liquid phase. There is a film of liquid around the gas bubbles. The gas bubbles move faster than the liquid phase. At high flow velocities, the liquid can become entrained in the gas bubbles. The gas and liquid phases may have significant effects on the pressure gradient.

Transition flow is the regime where the change from a continuous liquid phase to a continuous gas phase occurs. In this regime, the gas phase becomes more dominant, with a significant amount of liquid becoming entrained in the gas phase. The liquid slug between the gas bubbles virtually disappears in the transition regime.

In the annular-mist regime, the gas phase is continuous and is the controlling phase. The bulk of the liquid is entrained and carried in the gas phase.

Orkiszewski defined bubble flow, slug flow, mist flow and gas velocity numbers which are used to determine the appropriate flow regime.

If the ratio of superficial gas velocity to the non-slip velocity is less than the bubble flow number, then bubble flow exists, for which the pressure drop is:

where: ∆P = Pressure drop (lb/ft2 per foot of length)

ftp = Two-phase friction factor

ρL = Liquid density (lb/ft3)

VsL = Superficial liquid velocity (ft/s)

RL = Dimensionless factor dependent on non-slip velocity

gc = Gravitational constant (32.2 lbm-ft/lbf-s2)

D = Hydraulic diameter (ft)

If the ratio of superficial gas velocity to the non-slip velocity is greater than the bubble flow number, and the gas velocity number is smaller than the slug flow number, then slug flow exists. The pressure drop in

(A.14)∆P ftpρL

VsL

RL--------

2

2gcD----------------=

A-9

A-10 Pressure Drop

A-10

this case is:

where: Vns = Non-slip velocity

Vr = Bubble rise velocity

Γ = Constant

The pressure drop calculation for mist flow is as follows:

where: Vsg = Superficial gas velocity (ft/s)

ρg = Gas density (lb/ft3)

The pressure drop for transition flow is:

where: ∆Ps = Pressure drop for slug flow

∆Pm = Pressure drop for mixed flow

χ = Weighting factor, dependent on mist flow, slug flow, and gas velocity numbers.

The pressure drop calculated by the previous equations are for a one-foot length of pipe. These are converted to total pressure drop by:

where: ρ = Density of the flowing regime (lb/ft3)

Qtotal = Mass rate of combined liquid/gas (lb/s)

(A.15)∆PftpρLVns

2

2gcD--------------------- VsL Vr+

Vns Vr+-------------------- Γ+=

(A.16)∆P ftpρg

Vsg( )2

2gcD---------------=

(A.17)∆P ∆Ps 1 χ–( )∆Pm+=

(A.18)∆Ptotal

ρ∆PL

144 1QtotalGf

4637PAp2

----------------------

–

----------------------------------------------------=


Gf = Gas flow rate (ft3/s)

Ap = Cross-sectional area of pipe (ft2)

p = Average pressure in segment (psia)

∆P = Unit pressure drop (as calculated above)

L = Length of line segment (ft)

A.1.2 Fittings Pressure Drop Methods

Fitting pressure losses are calculated from a type specific loss coefficient, K, which is defined by

Where: P = Total pressure loss

= Density

U = Velocity

The static inlet pressure is then calculated from the following equation in which it is assumed that there is no elevation change across the node.

Where: P = Total pressure loss

P = Static pressure

= Density

U = Velocity

Subscripts: 1 = Inlet

2 = Outlet

(A.19)K∆P

ρU2( ) 2⁄

----------------------=

∆

ρ

(A.20)∆P P1

ρ1U12

2-------------+

P2

ρ2U22

2-------------+

–=

∆

ρ

A-11

A-12 Pressure Drop

A-12

Enlargers/Contractions

The loss coefficient is calculated from the ratio of the smaller diameter to the larger diameter, β, which is defined by:

Sudden and gradual contraction

If < 45° :

Otherwise:

(A.21)βd1

d2-----=

Figure A.2

θ

(A.22)K2

0.8θ2--- 1 β2

–( )sin

β4---------------------------------------

K1

β4------= =

(A.23)K2

0.5 1 β2–( ) θ

2---sin

β4-------------------------------------------

K1

β4------= =

Sudden and gradual enlargement

If < 45° :

Otherwise:

Tees

Tees can be modelled either using a flow independent loss coefficient for each flow path or using variable loss coefficients that are a function of the volumetric flow and area for each flow path as well as the branch angle. The following numbering scheme is used to reference the flow paths.

Figure A.3

θ

(A.24)K2

2.6θ2--- 1 β2

–( )2

sin

β4-----------------------------------------

K1

β4------= =

(A.25)K21 β2

–( )2

β4----------------------

K1

β4------= =

Figure A.4

A-13

A-14 Pressure Drop

A-14

Constant Loss Coefficient

If: = 90°

Otherwise :

Variable Loss Coefficients

The loss coefficient is a function of the branch angle, branch area to total flow area ratio and branch volumetric flow to total volumetric flow ratio. These values have been graphically represented by Miller. reference here A typical chart for K23 in combining flow is shown.

θ

(A.26)

(A.27)

K13 K31 0.5= =

K23 K32 0.5= =

(A.28)

(A.29)

K13 K31 1.37= =

K23 K32 0.76= =

Figure A.5

Flow Ratio, Q1/Q3

Are

aR

atio

A1/

A3


Orifice Plates

Orifice plates can either be modelled as a sudden contraction from the inlet line size to the hole diameter followed by a sudden expansion from the hole diameter to the outlet line size. This simplistic treatment if often adequate given the uncertainty in the prediction of two phase loss coefficients.

Alternatively the equation for a thin orifice plate may be used:

where: d1 = Inlet pipe diameter

d2 = Hole diameter

Separators

The pressure loss for a separator is modelled by treating it as a sudden enlargement of the total flow from the inlet line size to the hydraulic diameter of the body followed by a sudden contraction of the vapour flow from the hydraulic diameter of the body to the to the outlet line size. Friction losses within the separator body are ignored.

A.2 Vapour-Liquid Equilibrium

A.2.1 Compressible GasThe PVT relationship is expressed as:

(A.30)

(A.31)

K22.825 1 β2

–( )1.5082β0.08596

β4------------------------------------------------------------=

βd1

d2-----=

(A.32)PV ZRT=

A-15

A-16 Vapour-Liquid Equilibrium

A-16

where: P = pressure

V = Volume

Z = Compressibility factor

R = Gas constant

T = Temperature

The compressibility factor Z is a function of reduced temperature and pressure. The overall critical temperature and pressure are determined using applicable mixing rules.

A.2.2 Vapour PressureThe following equations are used for estimating the vapour pressure, given the component critical properties3:

where: p*r = Reduced vapour pressure (p*/pc)

p* = Vapour pressure (psi abs)

pc = Critical pressure (psi abs)

ω = Acentric factor

Tr = Reduced temperature (T/Tc)

T = Temperature (°R)

Tc = Critical Temperature (°R)

This equation is restricted to reduced temperatures greater than 0.30, and should not be used below the freezing point. Its use was intended for hydrocarbons, but it generally works well with water.

(A.33)

(A.34)

(A.35)

p∗rln p∗rln( ) 0( ) ω p∗rln( ) 1( )+=

p∗rln( ) 0( )5.92714

6.09648Tr

-------------------– 1.28862 Trln– 0.169347Tr6

+=

p∗rln( ) 1( )15.2518

16.6875Tr

-------------------– 13.4721 Trln– 0.43577Tr6

+=


A.2.3 Soave Redlich KwongIt was noted by Wilson (1965, 1966) that the main drawback of the Redlich-Kwong equation of state was its inability of accurately reproducing the vapour pressures of pure component constituents of a given mixture. He proposed a modification to the RK equation of state using the acentricity as a correlating parameter, but this approach was widely ignored until 1972, when Soave (1972) proposed a modification of the SRK equation of this form:

The a term was fitted in such a way as to reproduce the vapour pressure of hydrocarbons using the acentric factor as a correlating parameter. This led to the following development:

The reduced form is:

The SRK equation of state can represent with good accuracy the behaviour of hydrocarbon systems for separation operations, and since it is readily converted into computer code, its usage has been extensive in the last twenty years. Other derived thermodynamic properties, like enthalpies and entropies, are reasonably accurate for engineering work, and the SRK equation enjoys wide acceptance in the engineering

(A.36)PRT

V b–------------

a T Tc ω, ,( )V V b+( )

---------------------------–=

(A.37)

(A.38)

(A.39)

(A.40)

PRT

V b–------------

acαV V b+( )---------------------–=

ac Ωa

R2Tc

2

Pc-------------- (Ωathe same as RK)=

α 1 S 1 Tr0.5

–( )+=

S 0.480 1.574ω 0.176ω2–+=

(A.41)Pr

3Tr

Vr 0.2559–----------------------------

3.8473αVr Vr 0.2599+( )---------------------------------------–=

A-17

A-18 Vapour-Liquid Equilibrium

A-18

community today.

A.2.4 Peng RobinsonPeng and Robinson (1976) noted that although the SRK was an improvement over the RK equation for VLE calculations, the densities for the liquid phase were still in considerable disagreement with experimental values due to a universal critical compressibility factor of 0.3333, which was still too high. They proposed a modification to the RK equation which reduced the critical compressibility to about 0.307, and which would also represent the VLE of natural gas systems accurately. This improved equation is represented by:

They used the same functional dependency for the α term as Soave:

The accuracy of the SRK and PR equations of state are roughly the same (except for density calculations).

(A.42)

(A.43)

(A.44)

PRT

V b–------------

acαV V b+( ) b V b–( )+-------------------------------------------------–=

ac 0.45724R

2Tc

2

Pc--------------=

b 0.07780RTc

Pc---------=

(A.45)

(A.46)

(A.47)

α 1 S 1 Tr0.5

–( )+=

S 0.37464 1.5422ω 0.26992ω2–+=

Pr

3.2573Tr

Vr 0.2534–----------------------------

4.8514α

Vr2

0.5068Vr 0.0642–+-----------------------------------------------------------–=


A.3 Physical Properties

A.3.1 Vapour DensityVapour density is calculated using the compressibility factor calculated from the Berthalot equation5. This equation correlates the compressibility factor to the pseudo reduced pressure and pseudo reduced temperature.

The density is then calculated from the real gas equation.

A.3.2 Liquid DensitySaturated liquid volumes are obtained using a corresponding states equation developed by R. W. Hankinson and G. H. Thompson14 which explicitly relates the liquid volume of a pure component to its reduced temperature and a second parameter termed the characteristic volume. This method has been adopted as an API standard. The pure compound parameters needed in the corresponding states liquid density (COSTALD) calculations are taken from the original tables published by Hankinson and Thompson, and the API data book for components contained in FLARENET's library. The parameters for hypothetical components are based on the API gravity and the generalized Lu equation. Although the COSTALD method was developed for saturated liquid densities, it can be applied to sub-cooled liquid densities, i.e., at pressures greater than the vapour pressure, using the Chueh and Prausnitz correction factor for compressed fluids. The COSTALD model was modified to improve its accuracy to predict the density for all systems whose pseudo-reduced temperature is below 1.0. Above this temperature, the equation of state compressibility factor is used to calculate the liquid density.

(A.48)Z 1.0 0.0703Pr

Tr----- 1.0

6.0

Tr2

-------–

+=

(A.49)ρ PMZRT-----------=

A-19

A-20 Physical Properties

A-20

A.3.3 Vapour ViscosityVapour viscosity is calculated from the Golubev3 method. These equations correlate the vapour viscosity to molecular weight, temperature and the pseudo critical properties.

Tr > 1.0

Tr 1.0

A.3.4 Liquid ViscosityFLARENET will automatically select the model best suited for predicting the phase viscosities of the system under study. The model selected will be from one of the three available in FLARENET: a modification of the NBS method (Ely and Hanley), Twu's model, and a modification of the Letsou-Stiel correlation. FLARENET will select the appropriate model using the following criteria:

All the models are based on corresponding states principles and have been modified for more reliable application. These models were selected since they were found from internal validation to yield the most reliable results for the chemical systems shown. Viscosity predictions for light hydrocarbon liquid phases and vapour phases were found to be handled more reliably by an in-house modification of the original Ely and Hanley model, heavier hydrocarbon liquids were more effectively handled by Twu's model, and chemical systems were more accurately handled by an in-house modification of the original

(A.50)µ3.5M

0.5Pc

0.667Tr

0.71 0.29 Tr⁄+( )

10000.0Tc0.167

------------------------------------------------------------------------=

≤

(A.51)µ3.5M

0.5Pc

0.667Tr

0.965

10000.0Tc0.167

------------------------------------------------=

Chemical System Liquid Phase Methodology

Lt Hydrocarbons (NBP < 155 F) Mod Ely & Hanley

Hvy Hydrocarbons (NBP > 155 F) Twu

Non-Ideal Chemicals Mod Letsou-Stiel


Letsou-Stiel model.

A complete description of the original corresponding states (NBS) model used for viscosity predictions is presented by Ely and Hanley in their NBS publication16. The original model has been modified to eliminate the iterative procedure for calculating the system shape factors. The generalized Leech-Leland shape factor models have been replaced by component specific models. FLARENET constructs a PVT map for each component and regresses the shape factor constants such that the PVT map can be reproduced using the reference fluid. It is important to note that the PVT map is constructed using the COSTALD for the liquid region. The shape factor constants for all the library components have already been regressed and are stored with the pure component properties.

Pseudo component shape factor constants are regressed when the physical properties are supplied. Kinematic or dynamic viscosity versus temperature curves may be supplied to replace FLARENET's internal pure component viscosity correlations. FLARENET uses the viscosity curves, whether supplied or internally calculated, with the physical properties to generate a PVT map and regress the shape factor constants. Pure component data is not required, but if it is available it will increase the accuracy of the calculation.

The general model employs methane as a reference fluid and is applicable to the entire range of non-polar fluid mixtures in the hydrocarbon industry. Accuracy for highly aromatic or naphthenic oil will be increased by supplying viscosity curves when available, since the pure component property generators were developed for average crude oils. The model also handles water and acid gases as well as quantum gases.

Although the modified NBS model handles these systems very well, the Twu method was found to do a better job of predicting the viscosities of heavier hydrocarbon liquids. The Twu model18 is also based on corresponding states principles, but has implemented a viscosity correlation for n-alkanes as its reference fluid instead of methane. A complete description of this model is given in the paper18 titled "Internally Consistent Correlation for Predicting Liquid Viscosities of Petroleum Fractions".

For chemical systems the modified NBS model of Ely and Hanley is used for predicting vapour phase viscosities, whereas a modified form of the Letsou-Stiel model15 is used for predicting the liquid viscosities. This method is also based on corresponding states principles and was found to perform satisfactorily for the components tested.

A-21


A-22

The parameters supplied for all FLARENET pure library components have been fit to match existing viscosity data over a broad operating range. Although this will yield good viscosity predictions as an average over the entire range, improved accuracy over a more narrow operating range can be achieved by supplying viscosity curves for any given component. This may be achieved either by modifying an existing library component through FLARENET's component librarian or by entering the desired component as a hypothetical and supplying its viscosity curve.

Liquid Phase Mixing Rules for Viscosity

The estimates of the apparent liquid phase viscosity of immiscible Hydrocarbon Liquid - Aqueous mixtures are calculated using the following "mixing rules":

i) If the volume fraction of the hydrocarbon phase is greater than or equal to 0.33, the following equation is used19:

where: µeff = apparent viscosity

µoil = viscosity of Hydrocarbon phase

νoil = volume fraction Hydrocarbon phase

ii) If the volume fraction of the hydrocarbon phase is less than 0.33, the following equation is used20:

where: µeff = apparent viscosity

µoil = viscosity of Hydrocarbon phase

µH2O = viscosity of Aqueous phase

νoil = volume fraction Hydrocarbon phase

The remaining properties of the pseudo phase are calculated as

(A.52)µeff µoile3.6 1 υoil–( )

=

(A.53)µeff 1 2.5νoil

µoil 0.4µH2O+

µoil µH2O+------------------------------------

+ µH2O=


follows:

A.3.5 Thermal ConductivityAs in viscosity predictions, a number of different models and component specific correlations are implemented for prediction of liquid and vapour phase thermal conductivities. The text by Reid, Prausnitz and Poling15was used as a general guideline in determining which model was best suited for each class of components. For hydrocarbon systems the corresponding states method proposed by Ely and Hanley16is generally used. The method requires molecular weight, acentric factor and ideal heat capacity for each component. These parameters are tabulated for all library components and may either be input or calculated for hypothetical components. It is recommended that all of these parameters be supplied for non-hydrocarbon hypotheticals to ensure reliable thermal conductivity coefficients and enthalpy departures.

The modifications to the method are identical to those for the viscosity calculations. Shape factors calculated in the viscosity routines are used directly in the thermal conductivity equations. The accuracy of the method will depend on the consistency of the original PVT map.

The Sato-Reidel method15 is used for liquid phase thermal conductivity predictions of glycols and acids, the Latini et al. Method15 is used for esters, alcohols and light hydrocarbons in the range of C3 - C7, and the Missenard and Reidel method15 is used for the remaining components.

For vapour phase thermal conductivity predictions, the Misic and Thodos, and Chung et al.15 methods are used. The effect of higher pressure on thermal conductivities is taken into account by the Chung et al. method.

(A.54)

(A.55)

(A.56)

mweff ximwi= (molecular weight)

ρeff 1 xi pi⁄( )( )⁄= (mixture density)

Cpeff xiCpi= (misture specific heat)

A-23


A-24

As in viscosity, the thermal conductivity for two liquid phases is approximated by using empirical mixing rules for generating a single pseudo liquid phase property.

A.3.6 Enthalpy

Ideal Gas

The ideal gas enthalpy is calculated from the following equation:

where: H = Ideal enthalpy

T = Temperature

A, B, C, D, E = Ideal Gas heat capacity terms

Lee-Kesler

The Lee-Kesler enthalpy method corrects the ideal gas enthalpy for temperature and pressure.

(A.57)Hideal

Ai BiT CiT2

DiT3

EiT4

+ + + +=

(A.58)

(A.59)

(A.60)

H Hideal

Hdep

+=

Hdep

RTc------------ H

dep

RTc------------

sω

ωr------

Hdep

RTc------------

rH

dep

RTc------------

s

–

+=

Hdep

RTc------------

k

Tr Zk

1.0–

b2k 2b3

k

Tr-----------

–3b4

k

Tt2

-----------

+

TrVr------------------------------------------------------–

c2k 3c3

k

Tr2

----------

–

2TrVr2

------------------------------–d2

k

5TrVr5

----------------- 3E+ +

–=


where: Tc = Critical temperature

H = Specific enthalpy

ω = Acentric factor

r = Reference fluid

s = Simple fluid

Hideal = Ideal enthalpy

b, c, d, β, γ = Lee-Kesler terms

Hdep = Ideal Gas departure enthalpy

Equations of State

The Enthalpy and Entropy calculations are performed rigorously using the following exact thermodynamic relations:

For the Peng Robinson Equation of State, we have:

(A.61)Ec4

k

2Tr3γk

---------------- βk1.0 βk

1γk

Vr2

--------+ +

e

γk

Vr2

-------–

–+

=

(A.62)

(A.63)

H HID

–RT

-------------------- Z 1–1

RT------- T

∂P∂T------

VP– Vd

∞

V

+=

S S°ID

–

R------------------- Zln

PP°------ln–

1R---

∂P∂T------

V

1V---– Vd

∞

V

+=

(A.64)H H

ID–RT

-------------------- Z 1–1

21.5

bRT-------------------- a T

dadt------–

V 20.5

1+( )b+

V 20.5

1–( )b+------------------------------------

ln–=

A-25


A-26

where:

For the SRK Equation of State:

A and B term definitions are provided below:

(A.65)S S°

ID–

R------------------- Z B–( )ln

PP°------ln–

A

21.5

B-------------

Ta---

dadT------

Z 2

0.51+( )B+

Z 20.5

1–( )B–-------------------------------------ln+=

(A.66)a xixj aiaj( )0.51 kij–( )

j 1=

N

i 1=

N

=

(A.67)

(A.68)

H HID

–RT

-------------------- Z 1–1

bRT---------- a T

dadT------– 1

bV---+

ln–=

S S°ID

–

R------------------- Z B–( )ln

PP°------ln–

AB---

Ta---

dadT------ 1

BZ---+

ln+=

Term Peng-Robinson Soave-Redlich-Kwong

bi 0.077796RTci

Pci----------- 0.08664

RTci

Pci-----------

aiaciαi aciαi

aci0.457235

RTci( )2

Pci------------------ 0.42748

RTci( )2

Pci------------------

αi 1 mi 1 Tri0.5

–( )+ 1 mi 1 Tri0.5

–( )+

mi 0.37646 1.54226ωi 0.26992ωi2

–+ 0.48 1.574ωi 0.176ωi2

–+


where:

and

ID = Ideal Gas

° = Reference state

R = Ideal gas constant

H = Enthalpy

S = Entropy

A.4 NoiseThe sound pressure level at a given distance from the pipe is calculated from the following equations. In these equations the noise producing mechanism is assumed to be solely due to the pressure drop due to friction.

where: L = Equivalent length

SPL = Sound pressure level

r = Distance from pipe

(A.69)a xixj aiaj( )0.51 kij–( )

j 1=

N

i 1=

N

=

(A.70)b xibi

i 1=

N

=

(A.71)

(A.72)

Wm 1.36∆PL

------- πφ2

4--------- =

SPLr 1010

13ηWmL

4πr2

---------------------------

1–log=

A-27

A-28 Noise

A-28

φ = Internal diameter pressure

η = Acoustic efficiency

∆P = Change in Pressure

The acoustical efficiency is calculated from the following graph.

Figure A.6

(A.73)

0.0 0.2 0.4 0.6 0.8 1.0

Mach Number

10-11

10-10

10-9

10-8

10-7

10-6

10-5

10-4

10-3

Aco

ust

ical

Eff

icie

ncy

pt = 10.0

pt = 1.0

pt = 0.1

ptP1

P2------ T2

T1-----

2=


The transmission loss due to the pipe wall is calculated from:

(A.74)t 17.00.5mv

φ--------------- 36.0–=

A-29

A-30 Noise

A-30

File Format B-1

B File Format

B-1

B.1 Access File ................................................................................................... 3

B.1.1 Components Table................................................................................... 3B.1.2 Connectors Table..................................................................................... 4B.1.3 ControlValves Table ................................................................................. 5B.1.4 FlowBleeds Table..................................................................................... 6B.1.5 HorizontalSeparators Table...................................................................... 7B.1.6 OrificePlates Table................................................................................... 8B.1.7 Pipe Table ................................................................................................ 9B.1.8 PressureFlowSummary Table................................................................ 10B.1.9 ReliefValves Table.................................................................................. 11B.1.10 Tees Table............................................................................................ 13B.1.11 Tips Table ............................................................................................ 14B.1.12 VerticalSeparators Table...................................................................... 15

B.2 .FMT Files Format ...................................................................................... 16

B-2

B-2

File Format B-3

B.1 Access File FLARENET looks for data in the following tables in the Access data file.


A description of fields contained in each of these tables is given below.

B.1.1 Components TableThe following table gives a description of the fields in the Access file called Components.

Field Description Type Units

Name Component Name Text

Type Component Type Text

MolWt Component Molecular Weight Double

StdDensity Standard Liquid Density Double kg/m3

NBP Normal Boiling Point Double K

Watson Watson Characterisation factor Double

Pc Critical Pressure Double bar abs

Tc Critical Temperature Double K

Vc Critical Volume Double m3/kgmole

Vchar Characteristic Volume Double m3/kgmole

Omega Acentric Factor Double

OmegaSRK SRK Acentric Factor Double

Ha Indeal Gas Enthalpy Coefficient A Double kJ/kgmole

Hb Indeal Gas Enthalpy Coefficient B Double kJ/kgmole/K

Hc Indeal Gas Enthalpy Coefficient C Double kJ/kgmole/K2

Hd Indeal Gas Enthalpy Coefficient D Double kJ/kgmole/K3

B-3

B-4 Access File

B-4

B.1.2 Connectors TableThe following table gives a description of the fields in the Access file. These must be in a table called Connectors.

He Indeal Gas Enthalpy Coefficient E Double kJ/kgmole/K4

Hf Indeal Gas Enthalpy Coefficient F Double kJ/kgmole/K5

S Entropy Coefficient Double

ViscA Viscosity Coefficient A For Ely AndHanley Method

Double

ViscB Viscosity Coefficient B For Ely AndHanley Method

Double



Name Segment Name Text

Location Segment Location Text

Connection1 Name of node connected toupstream end

Text

ConnectionPoint1Index of connection on node connectto upstream end (0 = Upstream, 1 =Downstream, -32767 = unknown)

Integer

Connection2 Name of node connected todownstream end

Text

ConnectionPoint2Index of connection on node connectto downstream end (0 = Upstream, 1= Downstream, -32767 = unknown)

Integer

Length Segment Length. Set to -32767 forunknown.

Double

Angle Included Angle. Set to -32767 forunknown

Double

XposX coordinate of upper left corner oficon on PFD. The 0,0 coordinaterefers to the top left corner

Double Twips

YposY coordinate of upper left corner oficon on PFD. The 0,0 coordinaterefers to the top left corner

Double Twips

XposLabelX coordinate of upper left corner oflabel on PFD. The 0,0 coordinaterefers to the top left corner

Double Twips

YposLabelY coordinate of upper left corner oflabel on PFD. The 0,0 coordinaterefers to the top left corner

Double Twips

Rotation

Rotation of icon on PFD (0 = Normal,1 = 90o, 2 = 180o, 3 = 270o, Add 4 tovalue to flip about Y axis beforerotation

Double

File Format B-5

B.1.3 ControlValves TableThe following table gives a description of the fields in the Access file. These must be in a table called ControlValves.





Text


Integer

FlangeInternalDiameter Internal Diameter Of Outlet Flange Double mm

MassFlow Mass Flow Double kg/hr

Pressure Inlet Pressure Double bar abs

TemperatureFlagFlag To Indicate Type OfTemperature Specification; 0 =Absolute, 1 = Superheat, 2 = Subcool

Integer

TemperatureInlet Temperature SpecificationRelative To Type Defined ByTemperature Flag

Double C

AllowableBackPressure Allowable Pressure At Outlet Flange Double bar abs

FluidType

Description Of Fluid Type; HC, Misc,Amine, Alcohol, Ketone, Aldehyde,Ester, Carbacid, Halogen, Nitrile,Phenol, Ether

Text

MoleFractionx

Component mole fraction in detailedcomposition. x gives the index of thecomponent in the component list,starting at 1.

Double


Double Twips


Double Twips


Double Twips


Double Twips

Rotation


Double

B-5

B-6 Access File

B-6

B.1.4 FlowBleeds TableThe following table gives a description of the fields in the Access file. These must be in a table called FlowBleeds.





Text


Integer


Text


Integer

PressureDrop Fixed Pressure Drop. Set To -32767for unknown.

Double bar

FlowOffset Fixed Flow Offtake Contribution Double kg/hr

FlowMultiplier Proportional Flow OfftakeContribution

Double kg/hr

FlowMinimum Minimum Bound To CalculatedOfftake. Set to -32767 for unknown.

Double kg/hr

FlowMaximum Maximum Bound To CalculatedOfftake. Set ot -32767 for unknown

Double kg/hr


Double Twips


Double Twips


Double Twips


Double Twips

Rotation


Double

File Format B-7

B.1.5 HorizontalSeparators TableThe following table gives a description of the fields in the Access file. These must be in a table called HorizontalSeparators.





Text


Integer


Text


Integer

Connection3 Name of node connected tosecondary inlet

Text

ConnectionPoint3Index of connection on node connectto secondary inlet (0 = Upstream, 1 =Downstream, -32767 = unknown)

Integer

Diameter Vessel Diameter Double mm

LiquidLevel Liquid Level Double mm


Double Twips


Double Twips


Double Twips


Double Twips

Rotation


Double

B-7

B-8 Access File

B-8

B.1.6 OrificePlates TableThe following table gives a description of the fields in the Access file. These must be in a table called OrificePlates.





Text


Integer


Text


Integer

OrificeDiameter Diameter of orifice. Set to -32767 forunknown.

Double mm

OrificeInletDiameterRatio Ratio of orifice diameter to inletdiameter. Set to -32767 for unknown.

Double

OrificeOutletDiameterRatio Ratio of orifice diameter to outletdiameter. Set to -32767 for unknown.

Double


Double Twips


Double Twips


Double Twips


Double Twips

Rotation


Double

File Format B-9

B.1.7 Pipe TableThe following table gives a description of the fields in the Access file. These must be in a table called Pipe.





Text

ConnectionPoint1

Index of connection on node connectto upstream end (0 = Upstream, 1 =Downstream, -32767 = unknown, 2 =Branch/Secondary Inlet)

Integer


Text

ConnectionPoint2

Index of connection on node connectto downstream end (0 = Upstream, 1= Downstream, -32767 = unknown, 2= Branch/Secondary Inlet)

Integer

TailPipe Tailpipe flag (1 = True, 0 = False) Integer

Length Segment Length Double m

ElevationChange Elevation Change Double m

MaterialCode Pipe Material (0 = Carbon Steel, 1 =Stainless Steel)

Integer

Roughness Pipe Roughness Double inches

InternalDiameter Pipe Internal Diameter Double inches

WallThickness Pipe Wall Thickness Double inches

NominalDiameter Nominal Pipe Size Text

Schedule Pipe Schedule Text

LengthMultiplier Fitting length multiplier Double

K1 A in fitting loss equation Double

K2 B in fitting loss equation Double

Ambient Ambient temperature Double C

WindSpeed Wind speed Double m/s

OutletTemp Fluid outlet temperature (Set to -32767 if to be calculated)

Double C

Duty Heat transfer to pipe (Set to -32767 ifto be calculated)

Double kJ/hr

InsulationName Description of insulation Text

InsulationThickness Insulation thickness Double mm

InsulationConductivity Insulation thermal conductivity Double W/m/C


Double Twips

B-9

B-10 Access File

B-10

B.1.8 PressureFlowSummary TableThe following table gives a description of the fields in the Access file. These must be in a table called PressureFlowSummary.


Double Twips


Double Twips


Double Twips

Rotation


Double





RatedFlow Rated Flow Double kg/hr

MolarFlow Molar Flow Based Upon Mass Flow Double kgmole/hr

PressureDrop Pressure Drop Double bar

PressureAtSource Pressure At Source Node OutletFlange. -32767 if unknown.

Double bar

PressureDropFriction Friction Component Of PressureDrop. -32767 if unknown.

Double bar

PressureDropElevation Elevation Component Of PressureDrop. -32767 if unknown.

Double bar

PressureDropAcceleration

Acceleration Component Of PessureDrop. -32767 if unknown.

Double bar

PressureDropFittings Pressure Drop Due To Fittings Double bar

Noise Average Sound pressure level At ADistance Of 1 m From The Pipe

Double dB

FrictionFactor Fracition Factor Double

Reynolds Reynolds number Double

FlowRegime Flow Regime Text

EquivalentLength Equivalent Length Of Pipe InludingPhysical Length And Fittings.

Double m

Duty Calculated Duty Double kJ/hr

Htc Overall Heat Transfer Coefficient Double W/m2/C

HtcExternal External Heat Transfer Coefficient Double W/m2/C

File Format B-11

B.1.9 ReliefValves TableThe following table gives a description of the fields in the Access file. These must be in a table called ReliefValves.

HtcInternal Internal Heat Transfer Coefficient Double W/m2/C

Pressure1 Upstream Pressure Double bar abs

Temperature1 Upstream Temperature Double C

Velocity1 Upstream Velocity Double m/s

Mach1 Upstream Mach Number Double

RhoV21 Upstream Rho V2 Double kg/m/s2

Energy1 Upstream energy Flow Double kJ/hr

Pressure2 Downstream Pressure Double bar abs

Temperature2 Downstream Temperature Double C

Velocity2 Downstream Velocity Double m/s

Mach2 Downstream Mach Number Double

RhoV22 Downstream Rho V2 Double kg/m/s2

Energy2 Downstream energy Flow Double kJ/hr






Text


Integer

FlangeInternalDiameter Internal Diameter Of Outlet Flange Double mm


RatedFlow Rated Flow (The Maximum FlowThat The Valve Can Pass)

Double kg/hr

MAWP Maximum Allowable WorkingPressure

Double bar abs

Pressure Inlet Pressure Double bar abs

TemperatureFlagFlag To Indicate Type OfTemperature Specification; 0 =Absolute, 1 = Superheat, 2 = Subcool

Integer

TemperatureInlet Temperature SpecificationRelative To Type Defined ByTemperature Flag

Double C

ContingencyFlag Type oF Contingency (0 = Operating,1 = Fire)

Double

B-11

B-12 Access File

B-12

AllowableBackPressure Allowable Pressure At Outlet Flange Double bar abs

ValveTypeFlag Type Of Valve (0 = BalancedBellows, 1 = Conventopnal)

Double

ValveCount Number Of Valves In The Assmbley Integer

OrificeAreaPerValve Orifice Area Per valve Double mm2

FluidType

Description Of Fluid Type; HC, Misc,Amine, Alcohol, Ketone, Aldehyde,Ester, Carbacid, Halogen, Nitrile,Phenol, Ether

Text

MoleFractionx

Component mole fraction in detailedcomposition. x gives the index of thecomponent in the component list,starting at 1.

Double


Double Twips


Double Twips


Double Twips


Double Twips

Rotation


Double


File Format B-13

B.1.10Tees TableThe following table gives a description of the fields in the Access file. These must be in a table called Tees.





Text


Integer


Text


Integer

Connection3 Name of node connected to branch Text

ConnectionPoint3Index of connection on node connectto branch (0 = Upstream, 1 =Downstream, -32767 = unknown)

Integer

BranchAngleIndex Branch Angle Identifier ( 0 = 30o, 1 =45o, 2 = 60o, 3 = 90o)

Integer

Body

Coonection Ondex Of Pipe ThatDefines The Body Diameter (0 =Upstream, 1 = Downstream, 2 =Branch)

Integer


Double


Double


Double


Double

Rotation


Double

B-13

B-14 Access File

B-14

B.1.11Tips TableThe following table gives a description of the fields in the Access file. These must be in a table called Tips.





Text


Integer

Diameter Exit Diameter Double mm

K Total Head Loss Coefficient Double

CurveFlag Use Curve Flag (0 = No, 1 = Yes) Integer

CurvePoints Number of points in pressure dropcurve.

Integer

CurveMassFlowxMass Flow Point In Pressure DropCurve. x gives the index of the point,starting at 1.

Double kg/hr

CurvePressureDropxPressure Drop Point In PressureDrop Curve. x gives the index of thepoint, starting at 1.

Double bar


Double Twips


Double Twips


Double Twips


Double Twips

Rotation


Double

File Format B-15

B.1.12VerticalSeparators TableThe following table gives a description of the fields in the Access file. These must be in a table called VerticalSeparators.





Text


Integer


Text


Integer

Diameter Vessel Diameter Double mm


Double Twips


Double Twips


Double Twips


Double Twips

Rotation


Double

B-15

B-16 .FMT Files Format

B-16

B.2 .FMT Files FormatThe printouts can be customised to a limited extent using a series of ASCII text files with the extension “.fmt”. These files may be edited using any ASCII text editor such as the NOTEPAD application distributed with Microsoft Windows.

The default “.fmt” files for each printed report are:

By default, these files are located in the Flarenet program directory. You can change the location and “.fmt“ file for each report on the Reports tab on the Preferences Editor view.

Report “.fmt” file

Component Data Comps.fmt

Component Database DbComps.fmt

Compositions MoleFrac.fmt

Fittings Database DbFittings.fmt

Messages Messages.fmt

Node Data Node.fmt

Pipes Data Pipes.fmt

Physical Properties Properties.fmt

Pipe Schedule Database DbSchedules.fmt

Pressure/Flow Summary Summary.fmt

Scenarios Data Scenarios.fmt

Scenarios Summary ScenSum.fmt

Source Data Sources.fmt

Figure B.1

File Format B-17

These files confirm to the following format, here shown for part of the DbSchedules.fmt file.

The following defines which variable may be printed with each report:

Variable Description

5 Number of variables to display

6 Font Size (Point)

Arial Font Name

schedule,20.0,0 Variable Name,width (mm), repeat flag (0 = Allpanes, 1 = Once only)nominal,20.0,1

internal,20.0,1

wall,20.0,1

group,20.0,1

Variable Name Variable Description

Com

ps.fm

t

DbC

omps

.fmt

Mol

eFra

cs.fm

t

DbF

ittin

gs.fm

t

Mes

sage

s.fm

t

Nod

es.fm

t

Pip

es.fm

t

Pro

pert

ies.

fmt

DbS

ched

ules

.fmt

Sum

mar

y.fm

t

Sce

nario

s.fm

t

Sce

nSum

.fmt

Sou

rces

.fmt

ambient Ambient Temperature x

angle Angle To Horizontal

backpres Back Pressure x

basis Composition Basis x

calcloss Autocalculated Fittings LossEquation

calculations Node Run, Branch and TailSegment

x

class Pipe Class x

comps Mole Fractions x x

connections x

count Number Of Items

damp Damping Factor

density Standard Liquid Density x x

densitydown Downstream Density x

densityup Upstream Density x

desc Description x

dsn Downstream Node x

duty Heat Loss x

elevation Elevation Change x

energy Energy x

B-17


B-18

energydown Downstream Energy Flow x

energyup Upstream Energy Flow x

enthalpy Enthalpy x

enthalpydown Downstream Enthalpy x

enthalpyup Upstream Enthalpy x

entropy Entropy x

entropydown Downstream Entropy x

entropyup Upstream Entropy x

equivlength Equivalent Length

factor Rated Flow factor

fitloss Fittings Loss Equation

fittingsa Fitting Loss A x

fittingsb Fitting Loss B x

fittingsuse x

flange Flange Diameter x

flow Mass flow

fractiondown Downstream Phase Fraction x

fractionup Upstream Phase Fraction x

frictionfractor Friction Factor x

group Item Group x

headmach Header Mach No. x

headvelvap Header Vapour Velocity x

headvelliq Header Liquid Velocity x

headrhov2 Header Rho V2 x

headnoise Header Noise x

heatcapdown Downstream Heat Capacity x

heatcapup Upstream Heat Capacity x

hia Enthalpy A Coefficient x x

hib Enthalpy B Coefficient x x

hic Enthalpy C Coefficient x x

hid Enthalpy D Coefficient x x

hie Enthalpy E Coefficient x x

hif Enthalpy F Coefficient x x

htc Heat Transfer Coefficient

htcoverall Overall HTC x


Com

ps.fm

t

DbC

omps

.fmt

Mol

eFra

cs.fm

t

DbF

ittin

gs.fm

t

Mes

sage

s.fm

t

Nod

es.fm

t

Pip

es.fm

t

Pro

pert

ies.

fmt

DbS

ched

ules

.fmt

Sum

mar

y.fm

t

Sce

nario

s.fm

t

Sce

nSum

.fmt

Sou

rces

.fmt

File Format B-19

htcexternal External HTC x

htcinternal Internal HTC x

id Item ID x

ignored Item Ignored x x

insname Insulation Description x

insthick Insulation Thickness x

insconductivity Insulation Conductivity x

internal Internal Diameter x x

length Segment Length x

lmultiply Length Multiplier x

location Segment Location x

machdown Downstream Mach Number x

machup Upstream Mach Number x

massflow Mass Flow x x

material Material Of Construction x

methoddamping Damping Factor x

methoddp Pressure Drop Method

methodelements Twp Phase Elements x

methodfriction Friction Factor x

methodfitlos Fittings Loss Method x

methodhordp Horizontal 2 Phase Pressure DropMethod

x

methodincdp Inclined Pressure Drop x

methodverdp Vertical 2 Phase Pressure DropMethod

x

methodvle VLE method x x

molarflow Molar Flow x

moleflow Source Molar Flow

molwt Molecular Weight x x x x

molwtdown Downstream Molecular Weight x

molwtup Upstream Molecular Weight x

msg Text Message

multiply Fittings Equation Multiplier x

name Item Name x x x x x x x x x x

nbp Normal Boiling Point x x

node Node x x


Com

ps.fm

t

DbC

omps

.fmt

Mol

eFra

cs.fm

t

DbF

ittin

gs.fm

t

Mes

sage

s.fm

t

Nod

es.fm

t

Pip

es.fm

t

Pro

pert

ies.

fmt

DbS

ched

ules

.fmt

Sum

mar

y.fm

t

Sce

nario

s.fm

t

Sce

nSum

.fmt

Sou

rces

.fmt

B-19


B-20

noise Noise x

nominal Nominal Pipe Diameter x x

number Index Number x

offmaximum Maximum Flow Offtake

offminimum Minimum Flow Offtake

offmultiply Offtake Flow Multiplier

offrate Offtake Flow Offset

offset Fittings Equation Offset x

omega Acentric Factor x x

omegasrk SRK Acentric Factor x x

pc Critical Pressure x x

phase Phase Label x

plant Source Plant Location

pressource Static Source Back Pressure x

presallow Allowable Back Pressure x

presdown Downstream Static Pressure x

presdrop Pressure Drop x

presdropfriction Static Pipe Friction Loss x

presdropacceleration

Static Pipe Acceleration Loss x

presdropelevation

Static Pipe Elevation Loss x

presdropfittings Static Pipe Fittings Loss x

presin Inlet Pressure x

presup Upstream Static Pressure x

property Property Description x

ratedflow Rated Mass Flow x

refer Literature Reference x

regime Flow Regime x

resize Resizable Flag x

reynolds Reynolds Number x

rhov2up Upstream Rho V2 x

rhov2down Downstream Rho V2 x

roughness Wall roughness x

scenario Scenario Name x

schedule Pipe Schedule x x


Com

ps.fm

t

DbC

omps

.fmt

Mol

eFra

cs.fm

t

DbF

ittin

gs.fm

t

Mes

sage

s.fm

t

Nod

es.fm

t

Pip

es.fm

t

Pro

pert

ies.

fmt

DbS

ched

ules

.fmt

Sum

mar

y.fm

t

Sce

nario

s.fm

t

Sce

nSum

.fmt

Sou

rces

.fmt

File Format B-21

seg1 Node Run Segment x

seg2 Node Branch Segment x

seg3 Node Tail Segment x

separate Separator Flag

si Entropy Coefficient x

source Source Name

status Ignored Status Flag

surftendn Downstream Surface Tension x

surftenup Upstream Surface Tension x

tailmach Tailpipe Mach No. x

tailnoise Tailpipe Noise x

tailpipe Tailpipe Flag x

tailrhov2 Tailpipe Rho V2 x

tailvelliq Tailpipe Liquid Velocity x

tailvelvap Tailpipe Vapour Velocity x

tc Critical Temperature x x

temp Temperature

tempcalc Inlet Temperature Calculations x

tempdown Downstream Temperature x

tempout Outlet Temperature x x

tempspec Inlet Temperature Specification x

tempup Upstream Temperature x

thermconddn Downstream Thermal Conductivity x

thermcondup Upstream Thermal Conductivity x

type Item Type x x x x

usn Upstream Node x

vapourfrac Source Vapour Fraction x

vc Critical volume x x

vchar Characteristic Volume x x

veldn Downstream Velocity x

velup Upstream Velocity x


Com

ps.fm

t

DbC

omps

.fmt

Mol

eFra

cs.fm

t

DbF

ittin

gs.fm

t

Mes

sage

s.fm

t

Nod

es.fm

t

Pip

es.fm

t

Pro

pert

ies.

fmt

DbS

ched

ules

.fmt

Sum

mar

y.fm

t

Sce

nario

s.fm

t

Sce

nSum

.fmt

Sou

rces

.fmt

B-21


B-22

visca Viscosity A Coefficient x x

viscb Viscosity B Coefficient x x

viscdown Downstream Viscosity x

viscup Upstream Viscosity x

volume Pipe volume

wall Wall Thickness x x

watson Watson CharacterisationParameter

x x

wind Wind Velocity x

zfactordown Downstream CompressibilityFactor

x

zfactorup Upstream Compressibility Factor x


Com

ps.fm

t

DbC

omps

.fmt

Mol

eFra

cs.fm

t

DbF

ittin

gs.fm

t

Mes

sage

s.fm

t

Nod

es.fm

t

Pip

es.fm

t

Pro

pert

ies.

fmt

DbS

ched

ules

.fmt

Sum

mar

y.fm

t

Sce

nario

s.fm

t

Sce

nSum

.fmt

Sou

rces

.fmt

References C-1

C References

C-1

C-2

C-2

References C-3

1 “GPSA Engineering Data Book”.

2 “chemical Engineering Volume 1”, 2nd Edition, J. M Coulson and J. F. Richardson, Pergamon Press.

3 “Viscosity of Gases And Mixtures”, I. F. Golubev, Natinoal Technical Information Services, TT7050022, 1959.

4 "Chemical Process Computations 1, Chemical Engineering-Data Processing", Raman, Raghu, Elsevier Applied Science Publishers Ltd, 1985.

5 "Journal Of Physics", 3 ,263 , D. J. Berthalot.

6 "Technical Data Book-Petroleum Refining", American Petroleum Institute, 1977.

7 Ely, J.F. and Hanley, H.J.M., "A Computer Program for the Prediction of Viscosity and Thermal Conductivity in Hydrocarbon Mixtures", NBS Technical Note 1039 (1983).

8 Hankinson, R.W., and Thompson, G.H., AIChE J., 25, 653 (1979).

9 Beggs, H.D., and Brill, J.P., "A Study of Two-Phase Flow in Inclined Pipes", J. Petrol. Technol., p. 607, May (1973).

10Gas Conditioning and Processing, Volume 3, Robert N. Maddox and Larry L. Lilly, 1982 by Campbell Petroleum Series (second edition, 1990).

11Orkiszewski, J., Journal of Petroleum Technology, B29-B38, June, 1967.

12Gas Conditioning and Processing, Volume 3, Robert N. Maddox and Larry L. Lilly, 1982 by Campbell Petroleum Series (second edition, 1990).

13API Technical Data Book - Volume 1 , 1983, American Petroleum Institute.

14Hankinson, R.W. and Thompson, G.H., A.I.Ch.E. Journal, 25, No. 4, p.653 (1979).

C-3

C-4

C-4

15Reid, R.C., Prausnitz, J.M., Poling, B.E., "The Properties of Gases &Liquids", McGraw-Hill, Inc., 1987.

16Ely, J.F. and Hanly, H.J.M., "A Computer Program for the Prediction of Viscosity and Thermal Conductivity in Hydrocarbon Mixtures", NBS Technical Note 1039.

17Pausnitz, J.M., Lichtenthaler, R.N., Azevedo, E.G., "Molecular Thermodynamics of Fluid Phase Equilibria", 2nd. Ed., McGraw-Hill, Inc. 1986.

18Twu, C.H., IEC. Proc Des & Dev, 24, p. 1287 (1985).

19Woelfin, W., "Viscosity of Crude-Oil Emulsions", presented at the spring meeting, Pacific Coast District, Division of Production, Los Angeles, Calif., Mar. 10, 1942.

20Gambill, W.R., Chem Eng., March 9, 1959.

21Chen, N.H., "An Explicit Equation for Friction Factor in Pipe", Ind. Eng. Chem. Fund., 18, 296, 1979.

22API Recommended Practice 520, “Sizing, Selection, and Installation of Pressure - Relieving Devices in Refineries”, Part I, 6th. Ed., American Petroleum Institute, March, 1993

23API Recommended Practice 521, “Guide for Pressure-Relieving and Depressuring Systems”, 3rd. Ed., American Petroleum Institute, November, 1990

24Leung, J.C., "Easily Size Relief Devices and Piping for Two-Phase Flow", Chem. Eng. Prog., p. 28, December, 1996.

25Miller, D.M., "Internal Flow Systems", 2nd. Ed., BHR Group Limited, 1990.

Glossary of Terms D-1

D Glossary of Terms

D.1.1 Adiabatic Flow ......................................................................................... 3D.1.2 Choked Flow............................................................................................ 3D.1.3 Critical Pressure ...................................................................................... 3D.1.4 Critical Temperature................................................................................. 3D.1.5 Dongle ..................................................................................................... 3D.1.6 Equivalent Length .................................................................................... 3D.1.7 Isothermal Flow ....................................................................................... 3D.1.8 MABP....................................................................................................... 4D.1.9 Mach Number .......................................................................................... 4D.1.10 Node ...................................................................................................... 4D.1.11 Reduced Pressure ................................................................................. 4D.1.12 Reduced Temperature ........................................................................... 4D.1.13 Scenario ................................................................................................ 4D.1.14 Schedule................................................................................................ 5D.1.15 Security Device...................................................................................... 5D.1.16 Source ................................................................................................... 5D.1.17 Static Pressure ...................................................................................... 5D.1.18 Tailpipe................................................................................................... 5D.1.19 Total Pressure........................................................................................ 5D.1.20 Velocity Pressure ................................................................................... 5

D-1

D-2

D-2


D.1.1 Adiabatic FlowAdiabatic flow is the constant enthalpy flow of a fluid in a pipe.

D.1.2 Choked FlowThe velocity of a fluid in a pipe of constant cross sectional area cannot exceed the sonic velocity of the fluid. If the flow of fluid in a pipe is great enough that the sonic velocity is reached, then a pressure discontinuity is seen at the exit end of the pipe.

D.1.3 Critical PressureThe critical pressure is the pressure at which the vapour density and liquid density of a substance may be the same.

D.1.4 Critical TemperatureThe critical temperature is the temperature at which the vapour density and liquid density of a substance may be the same.

D.1.5 DongleSee Security Device.

D.1.6 Equivalent LengthThe equivalent length of a pipe is the straight length of pipe which would create the same pressure drop as the actual pipe length plus losses due to bends and fittings.

D.1.7 Isothermal FlowIsothermal flow is the constant temperature flow of a fluid in a pipe. In general when the pressure of a gas reduces, there is a small change in temperature. This assumption leads to a small error in the calculated pressure profile. In practice for pipes of length at least 1000 diameters, this difference does not exceed 5% and in fact never exceeds 20%.

D-3

D-4

D-4

D.1.8 MABPThe Maximum Allowable Back Pressure on a relief device is the maximum pressure that can exist at the outlet of the device without affecting the capacity of the device.

In general the MABP for a conventional pressure relief valve should not exceed 10% of the set pressure at 10% overpressure.

In general the MABP for a balanced pressure relief valve should not exceed 40% of the set pressure at 10% overpressure.

D.1.9 Mach NumberMach number is the ratio of the fluid velocity to the sonic velocity in the fluid.

D.1.10NodeNodes define the connection points between pipes, and pipes with sources. These are always represented by integer numbers. Node 0 always refers to the exit from the flare system.

D.1.11Reduced PressureReduced pressure is the ratio of the absolute pressure to the critical pressure of the fluid.

D.1.12Reduced TemperatureReduced temperature is the ratio of the absolute temperature to the critical temperature of the fluid.

D.1.13ScenarioA scenario represents a set of flow and compositional data for all sources in the system.


D.1.14ScheduleThe schedule of a pipe defines a standard thickness for a given nominal pipe size. In general, flare and vent systems are constructed from schedule 40 or 80 pipe.

D.1.15Security DeviceThe hardware device that is connected to the parallel port of the computer. FLARENET cannot be run unless this device is connected.

D.1.16SourceA source refers to a fluid entering the piping network regardless of the type of pipe fitting from which it enters. the fluid is defined in terms of its composition, mass flowrate, pressure and temperature.

D.1.17Static PressureThe pressure acting equally in all directions at a point in the fluid.

Physical properties are calculated at the static pressure condition.

D.1.18TailpipeThe section of pipe between the discharge flange of the source valve and the main collection header is generally refered to as a tailpipe.

D.1.19Total PressureThe sum of the static and velocity pressures.

D.1.20Velocity PressureGiven by , also called the kinematic pressure.ρU

2

2----------

D-5

D-6

D-6

Index

A

Acentric Factor A-16, A-17, A-23, A-25Adiabatic Flow

definition D-3Allowable Back Pressure 10-21, 10-26

B

Berthalot Equation A-19Button Bar 5-6

C

Calculation Options 11-3Calculation Options Editor 11-3

General tab 11-3Methods tab 11-6Warnings tab 11-9

Calculation Problems group 11-10Design Problems group 11-9Sizing Status group 11-10

Calculations 11-1starting the 11-11

Casecreating a new 6-3opening an existing 6-4saving a 6-5

Case Description View 6-3Check Box 5-4Chen Equation A-4Choked Flow

definition D-3Column Order

changing 5-10Column Width

changing 5-9Comma Separated Values 15-4Component

adding/editing 7-5changing 7-9

list 7-4removing selected 7-5selecting 7-3

matching name string 7-4selection filter 7-4sorting 7-9swapping 7-9type 7-3

Component Editor View 7-5Critical tab 7-7estimating unknown properties 7-8Identification tab 7-6Other tab 7-8

Component Manager View 7-3Composition Basis 5-14Connector Editor 10-6

Calculations tab 10-7Connections tab 10-6

Control Valve EditorComposition tab 10-27Conditions tab 10-26Connections tab 10-25Dimensions tab 10-28Methods tab 10-29

Copying Source DataSee Sources copy source data

COSTALD Calculations A-19Critical Pressure

definition D-3Critical Temperature

definition D-3CSV

See Comma Separated Values

D

Darcy Friction Factor A-5Data

components 13-3sources 13-4

I-1

I-2

I-2

viewing 13-1Data Export 15-3Data Import 15-3Data View 5-4

editing 5-9Database Editor

component 12-8fittings 12-7pipe schedule 12-6

Database Features 12-3adding/deleting data 12-5manoeuvring through the table 12-4printing 12-5selection filter 12-3

Databases Menu 12-1Dialog Box 5-4Dongle

See Security DeviceDrop Down List Box 5-4

E

Edit Box 5-4Equation

Berthalot A-19Chen A-4Real Gas A-19Round A-4SRK A-17

Equivalent Lengthdefinition D-3

Exportingto Microsoft Access 15-17

Exporting to Microsoft Access 15-17

F

Flare Tip Editor 10-4Calculations tab 10-5Connections tab 10-5

Flowlaminar A-5mist A-10transition A-5, A-9, A-10turbulent A-4

Flow Bleed EditorCalculations tab 10-17Connections tab 10-16

FMT Files 15-5Froude Number A-6

H

Help Menu 5-16Horizontal Separator Editor


Hysim 15-3

I

ImportingASCII text files 15-8from HYSIM 15-8from Microsoft Access 15-16HYSYS source data 15-13

Interface 5-1Isothermal Flow

definition D-3

M

MABPdefinition D-4

Mach Numberdefinition D-4

Maximum Allowable Working Pressure (MAWP) 10-20Menu Bar 5-5Mod Ely & Hanley Method A-20Mod Letsou-Stiel A-20Modal View 5-4Moody Friction Factor A-4

N

Networkrating an existing 11-12

Nodedefinition D-4

Node Manager 10-3Node Types 10-4

connector 10-6flare tip 10-4flow bleed 10-16horizontal separator 10-12orifice plate 10-14sources 10-18tee 10-8vertical separator 10-10

Nodes 10-1Noise A-27

acoustical efficiency A-28

Index I-3

Non-Modal View 5-4

O

Orifice Plate EditorCalculations tab 10-15Connections tab 10-14

P

Passwordsetting the 12-5

PFD 14-1button bar 14-5changing view options 14-12

grid 14-12toggle direct/orthogonal 14-12

connecting objects 14-9icons 14-3installing objects 14-8manipulating the 14-9moving objects 14-10object inspection 14-5overview 14-3printing 14-11regenerate 14-11saving 14-11selecting objects 14-9

method one 14-9method two 14-10

unselecting objects 14-10view 14-4

Physical Properties A-19liquid density A-19liquid viscosity A-20mixing rules A-22thermal conductivity A-23vapour density A-19vapour viscosity A-20

Golubev method A-20Physical Prperties

enthalpy A-24Equations of State A-25ideal gas A-24Lee-Kesler A-24

Pipeadding/editing a 9-3arranging display order 9-12ignoring/restoring 9-11multiple editing 9-10

Pipe Editor 9-3

Fittings tab 9-6Heat Transfer tab 9-7

External Conditions group 9-7Heating group 9-8Insulation group 9-7

Methods tab 9-8Pipe Tools 9-13

pipe class editor 9-13Preferences

setting 5-12Preferences Editor

Databases tab 5-15Defaults tab 5-14General tab 5-12Import tab 5-16Reports tab 5-15

Pressure Drop A-3Printer Setup 15-7Printing 15-4

location-specific 15-7PVT Relationship A-15

R

Real Gas Equation A-19Reduced Pressure

definition D-4Reduced Temperature

definition D-4Refresh Source Temperatures 10-31Relief Valve Editor

Composition tab 10-22Conditions tab 10-20Connections tab 10-19Dimensions tab 10-23Methods tab 10-24

Removing 7-5Results

compositions 13-9messages 13-6physical properties 13-9pressure/flow summary 13-8scenario summary 13-13viewing 13-1

Round Equation A-4

S

Scenariodefinition D-4

Scenario Editor

I-3

I-4

I-4

Estimates tab 8-7General tab 8-5Headers tab 8-6Sources tab 8-7Tailpipes tab 8-6

Scenario Management 8-3Scenario Manager View 8-3Scenario Selector 5-4Scenario Tools 8-8Scenarios

adding single source 8-8adding/editing 8-5

General tab 8-5Sources tab 8-7

Scheduledefinition D-5number 9-5

Security Devicedefinition D-5

Sourcecopy source data to scenarios 10-30definition D-5

Source Tools 10-31adding single source scenarios 10-31updating downstream temperatures 10-31

Source Typescontrol valve 10-25relief valve 10-19

SRK Equation A-17SRK Equation of State A-26Status Bar 5-8

T

Tab Separated Values 15-4Tee Editor 10-8


Terminology 5-3Title Bar 5-4Tool Tip 5-4TSV

See Tab Separated ValuesTwo-Phase Pressure Drop A-5

Beggs and Brill A-5Dukler method A-7Orkiszewski method A-8

Twu Method A-20

V

Vaour Phase Pressure Dropmethods A-3

Vapour-Liquid Equilibrium A-15compressible gas A-15Peng Robinson A-18Soave Redlich Kwong A-17vapour pressure A-16

Vertical Separator EditorCalculations tab 10-11Connections tab 10-10

W

Windows Menu 5-16

flarenet_ders_dokümanı

Documents