Pipephase Release Notes

Important: Read First

Release Notes for PIPEPHASE®9.1Welcome to the release of PIPEPHASE 9.1. These Release Notes supplement and supersede the corresponding sections in all PIPEPHASE 9.1 documentation supplied with this release.

ContentsNew Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Overview of New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Important Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9General Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Security Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10VFP ECLIPSE Import Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . 10Installation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Compaq FORTRAN and UAS Capabilities . . . . . . . . . . . . . . . . . . 11

Where to Find PIPEPHASE 9.1 Documentation . . . . . . . . . . . . . . . . 12

Summary of Defects Fixed in PIPEPHASE 9.1 . . . . . . . . . . . . . . . . . 13

PIPEPHASE 9.x Bug List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

PIPEPHASE-PRO/II Interface 9.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Requirements and Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . 15PIPEPHASE-PRO/II Interface 9.x Bug List . . . . . . . . . . . . . . . . . 16

License and Copyright Information . . . . . . . . . . . . . . . . . . . . . . . . . 17

PIPEPHASE 9.1 Release Notes 1

New Features

The following enhancements have been made to PIPEPHASE 9.1:

Overview of New Features

1. PIPEPHASE & ROMeo Integration for Real-Time Apps➤ Full integration of PIPEPHASE and ROMeo for Real-Time

Applications➤ PIPEPHASE integrated as a “Blackbox” model➤ Multiple PIPEPHASE models can be embedded in a ROMeo

simulation➤ ROMeo solver can manipulate PIPEPHASE parameters, e.g.

Choke Diameters, Insulation thickness, Pipeline roughness, etc.➤ ROMeo perturbs each PIPEPHASE parameter to calculate a

derivative

New Feature Description

Full integration of PIPEPHASE and ROMeo for Real-Time Applications

PIPEPHASE integrated as a “Blackbox” model in ROMeo®

Multiple PIPEPHASE models can be embedded in a ROMeo simulationROMeo solver can manipulate PIPEPHASE parameters, e.g. Choke DiametersTroubleshoot automated applications

Manifold Node Simplify model layout

Network Utilities Callable via PIPEPHASE APITurn on/off well via Excel InterfaceChange Boundary Conditions via ExcelAlternatively use Status.csv file

Log File – Capture all API calls

Log file containing history of all manipulations done via PIPEPHASE APIs.

Automatic Import of Eclipse VFP tables

PIPEPHASE can generate Standard For Eclipse Format VFP tables. VFP tables generated by third party software can be imported into Pipephase provided that the variables defined in the table are compatible with Pipephase VFP tables.

Security FLEXlmTM 9.5 security is added as one of the security options.

2 New Features

PIPEPHASE/ROMeo - The Components

➤ PIPEPHASE models upstream processes➤ Pressure-flow balancing➤ Wells, Pipelines & Gathering networks➤ Multiphase flow

ROMeo models facilities

➤ Exchange any value with real time database: e.g. measurements➤ Automatically tune models with current measurements: Data

Reconciliation➤ Calculate Setpoints that maximize profit: Optimization➤ Notify user of abnormal conditions: e.g. compressor efficiency <

70%

● Automate everything (e.g. at 8:00 daily, or when process becomes steady)

● Download measurements and tune model

● Optimize setpoints

● Upload new setpoints to control system

Example: Chiller Plant

Gas Pipeline

Compressor with head curve

Hydraulically limited column

Air

Natural Gas Liquids TVP < 250 psia

Gathering network:Manipulate chokes

Refrigerant: Cost and availability = F(Ambient)


PIPEPHASE/ROMeo - Benefits to Users

➤ Simultaneously optimize the gathering network and facilities, while respecting the constraints (bounds) of both

➤ Notify user of data problems (ROMeo’s cross checking and scripting systems)

● Warn if a well’s water rate exceeds specified value

● Send E-mail if flow reversal detected or minimum tempera-ture violated

➤ Improve PIPEPHASE model robustness

● Automatically include latest well test data as it becomes available

● Reject any downloaded values that are out of range or too old

● Use facilities measurements to reconcile production model

➤ Save and trend historical results (Captive Historian)

● View a graph of each well’s daily production over the last year

➤ Schedule PIPEPHASE runs

2. Manifold Node

4 Overview of New Features

In the input integer matrix, a ‘2’ indicates that the link connecting the I/O-slot-pairs are active or ‘on’. A ‘1’ means the corresponding connecting link is inactive or ‘off’. A ‘0’ means that this connection is currently unavailable for manipulation.

3. Network Utilities

A field engineer may have to change the ‘On’ and ‘Off’ status of sources and manifold links (switching valves). To correctly effect these changes (in earlier versions of PIPEPHASE), the user had to identify and turn of all associated dead links and nodes that are affected by this change. This can be a tedious exercise.

Network Utilities automate this process.


➤ Excel Interface allows the user to turn on/off Sources & Sinks

➤ Users can also modify boundary conditions

➤ Use Filename_status.csv

➤ The Status file should also be used if Manifold nodes are present

➤ The Status file can be opened and edited in Excel

➤ Simple Format – specifies which nodes are on/off

➤ Automatically created

6 Overview of New Features

4. Log File

➤ Simulation Name.log contains a history of all manipulations done via API.

➤ Used for troubleshooting automated applications.

➤ Also have the option of running PIPEPHASE model from Log File.

➤ Hit “Calculation Methods” icon and select “Run from Log File”.

➤ Use to reproduce observed behavior from automated application.


5. Automatic Import of VFP Files

➤ Vertical Flow Performance Curves are used to represent the characteristics of a well

➤ PIPEPHASE can generate VFP tables

● Standard Format

● Eclipse Format

➤ VFP tables generated by third party software can be imported into Pipephase provided that the variables defined in the table are compatible with Pipephase VFP tables.

Compatibility with Earlier Versions of PIPEPHASEStandalone

■ PIPEPHASE 7.02, 7.1x, 7.2, and 7.3 database files are not compatible with PIPEPHASE 7.4 and above. The user needs to import the associated keyword input file.

■ Beginning with PIPEPHASE 7.4 database files will automatically be updated from the older versions. No keyword import will be required.

■ PIPEPHASE now uses the same API for both IN-PROC and OUT-OF-PROC applications. The previous IN-PROC interface IPIPEPHASE (PP_API.DLL) and OUT-OF-PROC interface PPSERVER (PP_API_EXE.EXE) have been merged into IPIPEPHASE (FF_APIServerDLL.DLL and FF_APIServerEXE.EXE).

● Previous PIPEPHASE versions used the IN-PROC mode. The OUT-OF-PROC mode is preferred by clients integrating PIPEPHASE into their in-house software because this eliminates conflicts between the programs. The OUT-OF-PROC mode also allows the user to launch multiple instances of PIPEPHASE simultaneously. The OUT-OF-PROC mode is not currently able to execute TACITE® transient simulations or generate VFP tables for Excel.

● When running PIPEPHASE from the GUI or the command line, the user may specify the run mode in the PIPEPHASE.INI file. The preference RunOutOfProc is set to 0 for IN-PROC mode and to 1 for OUT-OF-PROC mode. The

8 Compatibility with Earlier Versions of PIPEPHASE

preference ShowOutOfProc may be set to 1 show the OUT-OF-PROC calculation results during the run.

● When referencing the PIPEPHASE API from C++ applications, the user may also use the RunOutOfProc preference to select the run mode as shown in the C++ code example in the PIPEPHASE API Interface Manual.

● When referencing the PIPEPHASE API from Visual Basic applications, the standard PIPEPHASE server will be run IN-PROC. An additional PIPEPHASE server (PP_API_EXE) is provided to allow OUT-OF-PROC simulations. Refer to the VB example in the PIPEPHASE API Interface Manual for details.

Important Notices

General Notes

➤ For all existing PRO/II® users with PPUOP unit operation need to install PRO/II 7.1.3 in order to use PIPEPHASE 9.1.

➤ Do not Use OUT-OF-PROC configuration on Windows 98 and Windows ME.

➤ Users of OLGAS-2 Phase and OLGA-3 Phase models need to run PIPEPHASE in OUT-OF-PROC configuration.

➤ Maximum length of a path counting .ppzip or .inp, cannot exceed 256 characters.

➤ To generate EXCEL reports you must have your macro security set to medium or low.

➤ Do not re-name *.ppzip files in Windows Explorer. Use “Save As” option in the “File” menu to rename PIPEPHASE simulation files.

➤ The default segmentation in GUI for new simulations is manual segmentation, AUTO=OFF.

➤ Pipephase can not open files with the name *_900.ppzip. User is given option to rename such files to *.ppzip and open.

➤ To generate EXCEL reports you must have a default printer installed on your system otherwise you will get runtime error '1004' during MS-Excel output process.


➤ If you are using Microsoft Office 97, please update to Microsoft Office 97 SR2 otherwise you will have a runtime error during EXCEL report generation.

Security Notes

➤ To switch the security types in Windows 98 OS, users need to use ‘Modify’ install option. Editing the pipephase.ini file causes PIPEPHASE to crash.

➤ OLGAS 3-Phase requires a single FLEXlm license file generated by SimSci-Esscor.

➤ Prompt=1 under [wss_security] in pipephase.ini file causes Elan licencing fail. Deleting this Prompt key or using the value of “0” for it will allow users to user Elan licencing without a problem.

VFP ECLIPSE Import Updates

➤ Import From Existing VFP File

● You can import existing VFP tabular data from a file into the GUI. Only one table should be given in a file as only the first table is imported. The default is to import VFP tables generated by PIPEPHASE in Excel format. The extension for this type of file is "vfp.csv". For the black oil and condensate production wells, you may import VFP tables in Eclipse format. The default extension for these files is "vfp", but you may select any file by typing in the name or entering a search such as *.ecl. Select the file by pressing the Import From Existing VFP File button. The data will be imported into the current VFP Table file when you close the file selection window.

➤ For the Print Options window:

● VFP Tables can be generated during a Nodal Analysis run or from the automated VFP Table generation defined in the Link Device Data Window. Tables can be generated in Excel, Eclipse or User format. For nodal analysis simulations, VFP tables are produced only if a format selection is made. For the automated VFP Table generation, the default is to pro-duce Excel formatted tables. The Excel formatted files are readily imported into Excel and are easy to read. User for-matted files require the PIPEPHASE User-Added Subroutine feature to be installed. By linking in your own code, you can generate VFP Tables in any format you wish.

10 Important Notices

Installation Notes

➤ Do not install PIPEPHASE 9.1 in the same directory with an earlier version of the product. If your computer contains an earlier version, you must specify a different directory for the current installation

➤ Users with existing applications referencing the PIPEPHASE API will need to update their references to use PIPEPHASE 9.1

➤ During installation of PIPEPHASE 9.1 on Windows 98 or Windows ME, installation of SENTINEL driver (required by USB security) fails. Complete the installation by clicking OK to the error message. If your security selection is USB, after rebooting the machine, go to install source media to manually install the SENTINEL driver by following these steps:

● Go to the usbdriver70 subfolder inside the install folder.

● Double click on the file “Sentinel Protection Installer 7.0.0.msi” to start the USB driver install process.

● Complete the install.

Hardware Requirements

Compaq FORTRAN and UAS Capabilities

PIPEPHASE 9.1 users using the UAS capabilities must use Compaq Visual FORTRAN version 6.6b (CVF).

Note: Before executing any of the installation programs, disable all antivirus software running on your computer.

Computer Intel Pentium IV. PIPEPHASE will run on slower computers, but the performance may be unacceptable.

Memory 512 MB (1 GB recommended).

Microsoft Windows

Windows 98, Windows ME, Windows NT 4.0 SP6, Windows 2000 SP2, Windows XP and Windows 2003.

To install under Windows NT/2000/XP, you must have administrator rights. Otherwise, the program will not be installed properly.


Where to Find PIPEPHASE 9.1 Documentation

Printed Documentation Included with this Package

The following documentation is provided for new users only:

■ Release Notes for PIPEPHASE 9.1 (this document)

■ PIPEPHASE 9.1 Installation Guide

■ PIPEPHASE 9.1 User’s Guide

■ PIPEPHASE-PRO/II Interface 9.1 User’s Guide

Printed Documentation Included with PIPEPHASE Add-On Modules

The following documentation is provided if you have purchased any of the add-on modules:

■ NETOPT User’s Guide

■ TACITE 4.1 User’s Guide

On-line Documentation

■ PIPEPHASE 9.1 Keyword Manual

■ PIPEPHASE 9.1 Application Briefs

■ SIMSCI Component and Thermodynamic Data Input Manual

Note: PIPEPHASE Online Help is installed on your computer during the PIPEPHASE installation procedure. Open the PIPEPHASE Online Help using the Windows Start menu. The complete path is Start/Programs/SIMSCI/PIPEPHASE 9.1, at which point you should see PIPEPHASE Online Help. When the Online Help opens, you will see a "Roadmap to Online Help". Two sections are shown 1) .HLP help documents and 2) .PDF help documents.

12 Where to Find PIPEPHASE 9.1 Documentation

Summary of Defects Fixed in PIPEPHASE 9.1

Feature Description

Database Duplicate database entries are created when the user changes the link name. This causes database corruption if the user later renames the connecting nodes.

GUI database cannot be opened due to corrupt graficon.dbf data. Fix allows database to be opened to generate keyword file.

DEW Resistance Coefficient K should allow 4 decimal places in the device DEW.

Excel Report Surface temperature plot is not produced if no ambient temperature data is available in the link. Pressure data is repeated when the temperature data cannot be identified.

Node Summary in Excel report fails for steam systems with no flow. Report titles are also incorrect.

GUI GUI Line sizing DEW and accompanying HELP confusing & ambigious. There are 3 line sizing options in PIPEPHASE (1)Sizing based on DP, (2)Sizing based on EROSION VEL ,(3)Sizing based on Velocity curve. The DEW allows you to explicitly select only the last two options. The first selection (erosion velocity constraint) behaves differently depending on BC's. It behaves as option (1) when inlet and outlet pressure is fixed and the flow rate is fixed. Otherwise it behaves as option (2) as indicated by the DEW. The manual Description is also missing the detail description of the options.

PIPEPHASE GUI does not write thermo sets after Woelflin user defined mixing curve is given.

Pipe schedule database does not work when user creates NEW database. Schedule is not displayed in global default and pipe windows. Working user database can be created by editing / renaming the default DIAMDATA database.

The restart file is lost if the Stop button in the GUI run menu is pressed after iterations had started and before the problem run is completed. When you rerun the problem you Get AVCOT: AMW=0 error or an exception error.

GUI DEW says standard GV, calcs interprets as in-situ GV. In the GUI separatore DEW, the Rate is indicated to be standard flow rate. The compositional separator RATE specification is interpreted as 'in-situ' rates at calculation time. This discrepency needs to be fixed.

Import The ESP curve cannot be seen in GUI Curve window after import. If you simply run the problem from the GUI, the pump curve is generated in the keyword file however. It appears like the data is imported and stored but not accessible from the GUI.

Pump curves are not imported correctly into GUI.

PVT PVT table generation does not work for Assay data.


PIPEPHASE 9.x Bug ListTo access the current version of the PIPEPHASE bug list as well as FAQ and Updates, visit our website's Knowledge base at www.simsci-esscor.com. Select the Support Menu and then the ‘Updates, Tips and More’ Option. Finally select PIPEPHASE and enter your personalized SIM4ME® Username & Password.

If you do not have a SIM4ME Username & Password, please take a few minutes to Register. Registration will allow you to access our complete knowledge base as well as allow us to display custom information of interest to you.

Report In the device summary, the pump inlet MWD and TVD is being printed instead of pump length and elevation change. In the P&T detail the MWD and TVD for the pump outlet is wrong. Similarly the resulting P&T well plots were wrong.

Security When we stop a PIPEPHASE run by pressing stop button in the GUI, the run is terminated as expected, but the calc engine does not release the security seat. If you request the stop during preprocessing, some of the intermediate files are not closed/cleaned up and you get errors (cannot open file etc) upon subsequent runs in the same sessions. Security seats also need to be released when you request an invalid license. An error should be given, but the GUI should continue to run to allow the user to select another feature.

Feature Description

14 PIPEPHASE 9.x Bug List

PIPEPHASE-PRO/II Interface 9.1Users can now run:

■ A PIPEPHASE simulation and automatically transfer stream data into a PRO/II simulation.

■ The reverse of this is also true.

■ Users can choose to converge the two simulators when a recycle from the production plant back into the PIPEPHASE surface network is desired.

■ In addition, users can transfer stream data from a PIPEPHASE simulation to another PIPEPHASE simulation and from a PRO/II simulation to another PRO/II simulation.

■ Users having Blackoil models in PIPEPHASE simulation can transfer temperature, pressure and flowrate data to PRO/II simulation.

This interfacing program is provided on a separate CD and has its own installation program named “setup” that you can execute once PIPEPHASE 9.1 or above and PRO/II 7.0 or above have been installed.

Requirements and Limitations

1. In order to integrate a PIPEPHASE simulation, the PIPEPHASE Input file must be generated by the PIPEPHASE GUI.

2. Components, component sequence and component naming must be identical among the various simulations that are being integrated.

3. Opening PRO/II or PIPEPHASE simulations while they are being converged using the PIPEPHASE-PRO/II Interface, can cause the PRO/II OLE Server or PIPEPHASE COM Server to behave improperly. Please, make sure each simulator is shut down before running the integrated simulation.

4. Currently the PIPEPHASE-PRO/II Interface allows only one recycle per integration.

5. Do not use files with duplicate names for two simulations, even if file paths are different.

6. Do not use two PIPEPHASE simulations at the same directory path.


PIPEPHASE-PRO/II Interface 9.x Bug ListTo access the current version of the PIPEPHASE-PRO/II bug list as well as FAQ and Updates, visit our website's Knowledge base at www.simsci-esscor.com. Select the Support Menu and then the ‘Updates, Tips and More’ Option. Finally select PIPEPHASE and enter your personalized SIM4ME Username & Password.

If you do not have a SIM4ME Username & Password, please take a few minutes to Register. Registration will allow you to access our complete knowledge base as well as allow us to display custom information of interest to you.

16 PIPEPHASE-PRO/II Interface 9.x Bug List

License and Copyright Information

Release Notes for PIPEPHASE 9.1

The software described in this guide is furnished under a written license agreement and may be used only in accordance with the terms and conditions of the license agreement under which it was obtained. The written technical documentation is being delivered to you without warranty from Invensys Systems, Inc. Any use of the technical documentation or the information contained therein is the sole responsibility of the user. Invensys Systems, Inc. reserves the right to make changes without prior notice.

Copyright Notice © 2006 Invensys Systems, Inc. No part of the material protected by this copyright may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying, recording, broadcasting, or by any information storage and retrieval system, without permission in writing from Invensys Systems, Inc.

Trademarks PIPEPHASE, NETOPT, SimSci-Esscor and SIM4ME are trademarks of Invensys plc., its subsidiaries, and affiliates. TACITE is a trademark of Institut Français du Petrole (IFP). OLGAS 1.1, OLGAS TWO-PHASE, and OLGAS THREE-PHASE are trademarks of SCANDPOWER A/S. Windows 98 ME, Windows NT, Windows 2000, Windows XP and Windows 2003 are trademarks of Microsoft Corporation.Pentium is a trademark of Intel Corporation. FLEXlm is a trademark of Macrovision Corporation. Compaq Visual Fortran is a trademark of Compaq Computer Corporation. Adobe, Acrobat, Exchange and Reader are trademarks of Adobe Systems, Inc. All other products are trademarks of their respective companies.

U.S. GOVERNMENT RESTRICTED RIGHTS LEGENDThe Software and accompanying written materials are provided with restricted rights. Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data And Computer Software clause at DFARS 252.227-7013 or in subparagraphs (c) (1) and (2) of the Commercial Computer Software-Restricted Rights clause at 48 C.F.R. 52.227-19, as applicable. The Contractor/Manufacturer is: Invensys Systems, Inc. (Invensys SIMSCI-ESSCOR) 26561 Rancho Parkway South, Suite 100, Lake Forest, CA 92630, USA.Printed in the United States of America March 2006.


18 License and Copyright Information

Pipephase Release Notes

Documents

Transcript of Pipephase Release Notes