4.0 Getting Started Guide: Inplant

INPLANT 4.
0 Getting Started Guide
INPLANT 4.0 Getting Started Guide
Use of the INPLANT program, and its component parts and subsystems, is governed by the terms and conditions of a separate written agreement between your employer and Invensys Systems, Inc., its subsidiaries or affiliates. 2006 Invensys Systems, Inc. All rights reserved. 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.
Copyright Notice
Trademarks
INPLANT, NETOPT, Invensys, SimSci-Esscor, and The Power of Simulation3 are trademarks of Invensys plc, its subsidiaries, and affiliates. TACITE is a trademark of Institut Francais du Petrole (IFP). Windows 2000, Windows XP, Windows 2003, and MS-DOS are trademarks of Microsoft Corporation. Compaq Visual Fortran is a trademark of Compaq Computer Corporation. Adobe, Acrobat, Exchange, and Reader are registered marks and/or trademarks of Adobe Systems, Inc. All other products noted herein are trademarks of their respective companies.
U.S. GOVERNMENT RESTRICTED RIGHTS LEGEND The 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.2277013 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, November 2006.
Contents Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 About This Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 About INPLANT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 About SimSci-Esscor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Where to Find INPLANT Documentation . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Where to Find Additional Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Technical Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Chapter 2 Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Verifying the Package Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Installation Media. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Hardware/Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Disk Space Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Virtual Memory Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 USB Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 FLEXlm Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 TOKEN Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 Switching Security Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 Chapter 3 Installing INPLANT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Installing a Standalone Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 For Typical installation: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 INPLANT Installation Directory (Typical) . . . . . . . . . . . . . . . . . . . . 3-4
INPLANT 4.0 Getting Started Guide i
For Custom installation: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 Installing a Network Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 Install all Files onto a Network File Server (NFS) . . . . . . . . . . . . . . . 3-6 Install Executable Files on an NFS and User Directories Locally . . . 3-6 Install Executable Files on an NFS: . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 Typical Directory Structure on a Network Drive . . . . . . . . . . . . . . . . 3-8 Install User Directories Locally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 Uninstalling INPLANT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10 Accessing User-Added Subroutines (UAS) . . . . . . . . . . . . . . . . . . . . . . . 3-11 Workspace for INPLANT User-Added Routines . . . . . . . . . . . . . . . . 3-12 Build Sample One: Customize a Pressure Drop Model . . . . . . . . . . . 3-13 Build Sample Two: Customize an INPLANT Thermo Routine. . . . . 3-15 Chapter 4 Installation Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Diagnosis of Problems with TOKEN and FLEXlm 7.2/9.5 Security . . . . 4-1 Diagnosis of USB Security Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12 General License Security Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17 Chapter 5 Sample Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Step 1 Getting Started, Setting Up the Problem . . . . . . . . . . . . . . . 5-2 Step 2 Selecting Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6 Step 3 Selecting Thermodynamic Methods . . . . . . . . . . . . . . . . . . . 5-7 Step 4 Describing and Defining the Simulation . . . . . . . . . . . . . . . 5-9 Step 5 Selecting Printer Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11 Step 6 Entering Calculation Options . . . . . . . . . . . . . . . . . . . . . . . . 5-12 Step 7 Entering Global Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13 Step 8 Drawing the Flowsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15 Step 9 Running the Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21 Step 10 Viewing the Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22 Index
ii
Contents
Chapter 1 Introduction
About This Manual
Welcome to the INPLANT 4.0 Getting Started Guide. This guide includes details on how to install INPLANT and provides tutorial chapters on using INPLANT This manual contains the chapters shown in Table 1-1 and an index.
Table 1-1: Quick Reference for INPLANT Users See Which Chapter 1, Introduction Chapter 2, Installation Requirements Chapter 3, Installing INPLANT Chapter 4, Installation Troubleshooting Chapter 5, Sample Session Introduces the manual, the program, and SimSciEsscor. Details the hardware and software requirement for running INPLANT. Describes how to install the application. Answers a number of FAQs about problems which may arise during installation. Guides the user through the setup, execution, and output review of a typical compositional network simulation.
About INPLANT
The INPLANT program is a steady-state, fluid flow simulator for designing, rating, and analyzing plant piping systems. Engineers can quickly rate and analyze the safety of plant piping systems via the INPLANT Graphic User Interface for Microsoft Windows Operating Systems. INPLANT also enables the design of new piping systems or the revamp of a wide variety of existing systems. Applications range from simple, single pipe sizing and rating calculations to large, multiphase fluid piping networks with
INPLANT 4.0 Getting Started Guide 1-1
complex, nested-loop topology. Easily solve relief system problems involving networks with single or multiphase fluids at high velocities or in critical flow.
About SimSci-Esscor
For nearly 40 years, SimSci-Esscor has been a leader in the development and deployment of process simulation software, services, and complete solutions for oil and gas production, hydrocarbon and specialty chemical processing and refining, and fossil and nuclear power. Benefit from products that minimize capital requirements, optimize facility performance, maximize ROI, and produce assets for: Plant engineering design and simulation Integrated process engineering (FEED) Pipeline production analysis Asset model management Operational analysis Optimization Process control Dynamic simulation Operator training
Design/Operate/Optimize a safe and profitable plant subject to ever more stringent market and regulatory constraints. SimSci-Esscor software solutions are indispensable tools in solving these three increasingly complex challenges simultaneously. SimSci-Esscor is a business unit of Invensys Process Systems, owned by Invensys, plc.
Where to Find INPLANT Documentation

Online Documentation
Online documentation is provided in the form of .PDF files and .HLP files. The .PDF files are most conveniently viewed using Adobe Acrobat Reader or Acrobat Exchange. The .HLP files are viewed using the standard Windows Help system or WinHelp. You can install Adobe Acrobat Reader from the INPLANT CD-ROM. The
1-2 Introduction
online documentation is installed to the INPLANT40\MANUALS directory during the INPLANT installation process and no longer requires the installation CD to be present in order to be viewed.
Online Help
INPLANT comes with online Help, a comprehensive online reference tool that accesses information quickly. In Help, commands, features, and data fields are explained in easy steps. Answers are available instantly, online, while you work. All dialog boxes in INPLANT GUI have help buttons and clicking on the Help button will take you to the help content relevant for that feature. You can also access the electronic Contents for Help by selecting Help/Contents from the menu bar. A Road Map to Online Help will be displayed where you can select the help document you wish to view. From the desired online help document you can do a search for the desired topic. If you choose a .HLP file, you can search by selecting Help/Search for from the menu bar. If you choose a .PDF formatted document, you can use all the available Acrobat Reader search features to find the topic of interest. Please refer to Acrobat Reader online help for information concerning Acrobat Reader features.
Where to Find Additional Help

If you want to... Learn how to install and simulate a simple flowsheet using INPLANT Obtain detailed information on the capabilities and use of INPLANT Obtain basic information on INPLANT keywords Obtain basic information on INPLANT calculation methods Obtain more detailed information on INPLANT calculation methods Obtain detailed information of component and thermodynamic properties See simulation examples See... This document INPLANT Users Guide INPLANT Keyword Manual Online Help INPLANT Keyword Manual SIMSCI Component and Thermodynamic Data Input Manual INPLANT Application Briefs Manual
1-3
Technical Support
SimSci-Esscor and its agents around the world provide technical support and service for PES products. If you have any questions regarding the use of the program or the interpretation of output produced by the program, contact your local SimSci-Esscor representative for advice or consultation. When calling one of the Technical Support Centers, be prepared to describe your problem or the type of assistance required. Also, to expedite your call, complete the following steps before calling Technical Support: Have the installation CD and all the provided documentation available. Determine the type of computer you are using. Determine the amount of free disk space available on the disk on which the product is installed. Note the exact actions you were taking when the problem occurred, as well as the steps you took leading up to that point. Note the exact error messages that appear on your screen, as well as any other symptoms.
Both new and experienced users will benefit significantly from attending one of SimSci-Esscors regularly scheduled training courses on PES products. If you would like to obtain a list of courses available, or if you have any questions relating to the use of a PES product, its methods, data, or technology, please call your nearest SimSci-Esscor Technical Support office (see Table 1-2) or visit our website at www.simsci-esscor.com.
1-4
Introduction
Table 1-2: Authorized SimSci-Esscor Technical Support Centers

Support Center USA and Canada Address Invensys Process Systems (SimSci-Esscor) 10900 Equity Drive Houston, TX 77041 Invensys Process Systems (SimSci-Esscor) Gateway Corporate Center, Suite 304, 223 Wilmington-West Chester Pike, Chaddsford, PA 19317 Invensys Process Systems (SimSci-Esscor) 26561 Rancho Parkway South Suite 100 Lake Forest, CA 92630 Invensys Systems Mexico S.A Ejercito Nacional 1005, Col. Irrigacion Deleg. Miguel Hidalgo, Mexico city 11500 Invensys Systems Argentina Inc. Nunez 4334 Buenos Aires (Argentina) C1430AND Invensys Systems Italia S.p.A Via Carducci, 125 Sesto San Giovanni (MI) 20099, Italia Invensys Systems Venezuela Torre Delta Piso 12, Av.Francisco de Miranda Altamira, Caracas 1060 Invensys Systems Brasil Ltda. Av. Chibaras, 75 - Moema Sao Paulo, SP O 4076 - 000 Invensys Systems GmbH Willy- Brandt- Platz, 6 Mannheim, 68161 Invensys Performance Solutions Level 2-4, 810 Elizabeth Street Sydney 2017, Australia Invensys Systems Japan Harbor One Building 2F, 2-5-5 Higashi-Shinagawa, Shinagawa-ku, Tokyo 140-0002, Japan Invensys ME Dubai PO Box 61495 Jebel Ali Free Zone, Dubai Invensys Software Systems (s) Pte. Ltd. 15, Changi Business Park, Central 1 Singapore 486057 Invensys Systems (UK) Limited High Bank House, Exchange Street, Stockport, Cheshire United Kingdom SK3 OET Invensys Process Systems (China) Co., Ltd. 809, Tower B, Eaglerun Plaza, No.26 Xiaoyun Road Chaoyang District, Beijing 100016 Invensys Systems LA Colombia Calle 100 # 36-39 Int. 4-203, Bucaramanga, SDER Invensys Systems Korea 551-3 Hyosung-dong, Gyeyang-gu Incheon, 407-040 Tel/Fax/Internet Tel: + 1 800 SIMSCI 1 + 1 713 329 1600 Fax: + 1 713 329 1905 E-mail: support.simsci@ips.invensys.com Tel: + 1 610 364 1900 Fax: + 1 610 364 9600 E-mail: support.simsci@ips.invensys.com Tel: + 1 949 525 4684 Fax: + 1909 593 7130 E-mail: suprt.simsci@ips.invensys.com Tel: + 52 55 52 63 01 77 Fax: + 52 55 55 57 26 20 E-mail: support.mx@simsci.com Tel: + 54 11 6345 2100 Fax: + 54 11 6345 2111 E-mail: supportar@simsci.com Tel: + 39 02 262 97326 Fax: + 39 02 262 97200 E-mail: support.it@simsci.com Tel: + 58 212 267 5868 Fax: + 58 212 6270964 E-mail: simscilat@simsci.com Tel: + 55 11 6844 0200 Fax: + 55 11 6844 0341 E-mail: suporte.simsciesscorbrasil@ips.invensys.com Tel: + (0800) 550 - 5510 E-mail: support.de@simsci.com Tel: + 61 2 8396 3626 Fax: + 61 2 8396 3604 E-mail: support.an@simsci.com Tel: + 81 3 6914 2655 Fax: + 81 3 5715 2686 E-mail: support@simsci.jp Tel: + 971 4 88 11440 Fax: + 971 4 88 11426 E-mail: support.me@simsci.com Tel: + 65 6829 8657 Fax: + 65 6261 9492 E-mail: asiapactech@simsci.com Tel: + 44 161 429 6744 Fax: + 44 161 480 9063 E-mail: simsci.uk@ips.invensys.com Tel: + 86 10 8458 5757 Fax: + 86 10 8458 4521 E-mail: china.solution@ips.invensys.com Tel: + 57 1 3136360 E-mail: support.co@simsci.com Tel: + 82-32-540-0665 Fax: + 82-32-542-3778 E-mail: jekwon.lee@ips.invensys.com
USA East Coast
USA West Coast
Mexico
Argentina
Italy
Venezuela
Brazil
Germany
Australia and New Zealand Japan
Middle East
Asia - Pacific
United Kingdom
China
Colombia
Korea
1-5
This Page Intentionally Left Blank
Chapter 2 Installation Requirements

This chapter provides a list of the INPLANT package contents, the installation requirements, and an outline of the hardware and software requirements for running INPLANT.
Verifying the Package Contents

Installation Media
INPLANT is distributed on a CD-ROM.
Documentation
A list of available INPLANT online documents is provided below: This document: INPLANT Getting Started Guide INPLANT Users Guide INPLANT Keyword Manual SIMSCI Component Data Input Manual SIMSCI Thermodynamic Data Input Manual INPLANT Application Briefs Release Notes
2-1
Hardware/Software Requirements
The minimum recommended hardware and software requirements are listed below: Computer RAM Monitor Pointing Device Intel Pentium 4 processor 512 MB. Super VGA or greater. Microsoft or compatible mouse.
Operating System Windows NT, Windows 2000, Windows 2003, or Windows XP. Proper installation of INPLANT requires administrator rights. Compiler To build User-Added Subroutines you need Compaq Visual FORTRAN (CVF) 6.6b.
Note: User-added subroutines built under Windows 2000 will run under
Windows 2000, Windows XP, and Windows 2003.
Disk Space Requirements

A full installation of INPLANT requires approximately 25 MB of free disk space. The INPLANT installation program automatically checks your system resources and notifies you if insufficient resources are available. Typical Installation Custom Installation Adobe Acrobat Reader 19 MB available disk space. Includes PFE text editor. 23 MB available disk space. Includes userspecified options. 7 MB available disk space. (.PDF files)
2-2
Installation Requirements
Virtual Memory Requirement

INPLANT requires at least 55 MB of virtual memory to provide sufficient paging area. To set virtual memory in Windows 2000: From the Windows Start menu, select Settings/Control Panel. Open the System item and access the Advanced tab. Click on the Performance Options... Click on the Change... button in the Virtual Memory section. Change the size in the paging file size for selected drive section, and click on the Set button.
To set virtual memory in Windows XP: From the Windows Start menu, select Settings/Control Panel. Click on the Performance and Maintenance Options. Open the System item and access the Advance tab. Click on Settings icon under Performance. Select the Advance tab. Click on the Change... button in the Virtual Memory section. Change the size in the paging file size for selected drive section, and click on the Set button.
To set virtual memory in Windows 2003 Server: From the Windows Start menu, select Settings/Control Panel. Open the System item and access the Advance tab. Click on Settings icon under Performance. Select the Advance tab. Click on the Change... button in the Virtual Memory section. Change the size in the paging file size for selected drive section, and click on the Set button.
2-3
Security
USB Security
SimSci-Esscor provides USB hardware security, in which you insert the key specially coded to allow use of INPLANT. Simply plug the hardware directly into the computers USB port to start running INPLANT. USB ports are not supported in Windows NT, therefore USB security is not available for this operating system.
FLEXlm Security
SimSci-Esscor provides a FLEXlm security option on the FLEXlm Server Application installation CD. The FLEXlm License Manager is a third-party concurrent-user software licensing tool from Macrovision Corporation. It is a client/server-based tool that has been customized by SimSci-Esscor. FLEXlm Server can run under Windows 2000/XP. The server must have at least 5 MB of available disk space. To install, learn, and troubleshoot FLEXlm security, follow the instructions provided in the FLEXlm Security Guide included in the standard release package.
TOKEN Security
SimSci-Esscor provides a TOKEN security option on the FLEXlm Server 9.5 Application installation CD. The FLEXlm License Manager is a third-party concurrent-user software licensing tool from Macrovision Corporation. It is a client/server-based tool that has been customized by SimSci-Esscor. FLEXlm Server can run under Windows 2000/XP. The server must have at least 5 MB of available disk space. To install, learn, and troubleshoot FLEXlm security, follow the instructions provided in the FLEXlm Security Guide included in the standard release package.
Switching Security Types

To switch to USB security:
2-4
Open the inplant.ini file found in the user directory. Find the section entitled [wss_Security] and set Type=USB. Save the file and exit.
Installation Requirements
To switch to FLEXlm9.5 security: Open the inplant.ini file found in the user directory. Find the section entitled [wss_Security] and set Type=FLXLM95. Save the file and exit. If you are running under Windows 2000/XP/2003, add the IPASSI_LICENSE_FILE=@{FLEXlm server machine name} system environment variable to your control panel/system/ advanced/environment variables. Reboot your computer if prompted, so the changes to your security environment will be correctly configured.
To switch to TOKEN security: Open the inplant.ini file found in the user directory. Find the section entitled [wss_Security] and set Type=TOKEN. Save the file and exit. If you are running under Windows 2000/XP/2003, add the IPASSI_LICENSE_FILE=@{FLEXlm server machine name} system environment variable to your control panel/system/ advanced/environment variables. Reboot your computer if prompted, so the changes to your security environment will be correctly configured.
To switch between security types from the control panel: From the Windows Start menu, select Settings/Control Panel. Click Add or Remove Programs. Select INPLANT. Click Change/Remove. Select Modify and click Next. Switch to desired Security option. Reboot your computer if prompted, so the changes to your security environment will be correctly configured.
2-5
This Page Intentionally Left Blank
Chapter 3 Installing INPLANT

This chapter explains how to install INPLANT as a standalone version or from a network/newuser version. There are three installation options for the INPLANT software: Typical This option installs both the GUI and the calculation portions of INPLANT directly to your PC. This option allows you to customize your installation by selecting the User-Added files with INPLANT. This option allows you to customize your installation by selecting the components you wish to install to the network. Individual users can run a simple setup program Graphic Only installation from their PC to access the INPLANT program installed on the network.
Custom
Network
Note: PC user-added subroutines require a custom installation.
INPLANT can be installed as a standalone version on a local machine or as a multiple-user version to a network machine.
Installing a Standalone Version

These instructions assume that you are installing from a CD-ROM in drive E into the structure C:\SIMSCI.

Start your Windows session. Insert the INPLANT installation CD into drive E.
3-1
Browse to the root of the installation CD and read the Release Notes. Open the INPLANT40 folder and double-click on SETUP.EXE to start the INPLANT Installation program. The first screen you will see in the installation process is the InstallShield Wizard for INPLANT. Once the Windows configuration is completed, an Application Type screen appears, which allows you to select to install either INPLANT or Acrobat Reader. Select INPLANT. Click Next >. At this point you install a Standalone version of INPLANT The Welcome to InstallShield Wizard dialog box appears. Click Next > to continue. The License Agreement dialog box appears. Click Yes > to continue. The Setup Type dialog box appears.
Note: Users installing a Local version of INPLANT on Windows 2000,
Windows XP, and Windows 2003 must have system administrator privileges for install to proceed properly.
Choose Typical or Custom. Enter the location where you wish to install the INPLANT program, if different from the default directory (C:\SIMSCI). To install to this folder, click Next >. To install to a different folder, click Browse... and select another folder.
For Typical installation:

Choose Typical option from the Setup Type dialog box. The Make Security Options dialog box appears. The Server Option requires FLEXlm or Token security. Utilizes a USB hardware key attached to the USB port on the back of the current machine for licensing purposes. Using this type, INPLANT will only search this hardware key for license(s).
USB
3-2
Installing INPLANT
FLEXlm7.2
Allows INPLANT to go beyond the current machine to obtain licenses from another machine (FLEXlm7.2 security server machine) on the network. Allows INPLANT to go beyond the current machine to obtain licenses from another machine (FLEXlm9.5 security server machine) on the network. Allows INPLANT to go beyond the current machine to obtain licenses from a Token server on the network.
FLEXlm9.5
Token
If you chose Token or FLEXlm, specify the prospective IPASSI FLEXlm server(s) (e.g., @server1; @server2) to guide INPLANT to find the FLEXlm server. Click Next > to continue. The Select Program Folder dialog box appears. By default, the setup program adds INPLANT icons in the SIMSCI program folder. You may type a new folder name, or select one from folder name, or select one from the existing folders list. Click Next > to continue. The Start Copying Files dialog box appears, which summarizes your install settings. If you want to review or change any settings, click < Back. If you are satisfied with the settings, click Next > to begin copying files. When your installation is complete, the InstallShield Wizard Complete Installation dialog box appears. Click Finish to complete the Local installation. When installation is done, you should see a SIMSCI group with a INPLANT GUI icon and a desktop INPLANT icon.
Note: If the Setup prompts for a reboot, you must restart your computer for the
software to be correctly configured.
You should now test your INPLANT installation. Proceed to the Testing INPLANT section for more information.
3-3
INPLANT Installation Directory (Typical)

C:\SIMSCI\INPLANT40\BIN C:\SIMSCI\INPLANT40\LIB C:\SIMSCI\INPLANT40\SYSTEM C:\SIMSCI\INPLANT40\USER C:\SIMSCI\INPLANT40\MANUALS C:\SIMSCI\INPLANT40\RESOURCE [Program executable files] [Component library directory] [INPLANT system files] [INPLANT user directory] [INPLANT Manuals] GUI bitmaps and icon files]
A typical installation creates the following three icons under Start\All Programs\SIMSCI\INPLANT40:

INPLANT 4.0 INPLANT 4.0 Online Help Programmers File Editor
For Custom installation:

The Select Features dialog box appears. Click Next > to continue. Choose the components you wish to install. If you plan to link your own user-added subroutines into INPLANT, select the User-Added Files option. Refer to the User-Added Subroutine section for re-link procedures. The Make Security Options dialog box appears. The Server Option requires FLEXlm or Token security. Utilizes a USB hardware key attached to the USB port on the back of the current machine for licensing purposes. Using this type, INPLANT will only search this hardware key for license(s). Allows INPLANT to go beyond the current machine to obtain licenses from another machine (FLEXlm7.2 security server machine) on the network. Allows INPLANT to go beyond the current machine to obtain licenses from another machine (FLEXlm9.5 security server machine) on the network.
USB
FLEXlm7.2
FLEXlm9.5
3-4
Installing INPLANT
Token
Allows INPLANT to go beyond the current machine to obtain licenses from a Token server on the network.
Click Next > to continue. The Select Program Folder dialog box appears. By default, the setup program adds INPLANT icons in the SIMSCI program folder. You may type a new folder name, or select one from folder name, or select one from the existing folders list. Click Next > to continue. The Start Copying Files dialog box appears, which summarizes your install settings. If you want to review or change any settings, click < Back. If you are satisfied with the settings, click Next > to begin copying files. You will see a box logging the progress of your installation. You can use the Cancel button at any time during disk installation to pause or exit the installation program. When your installation is complete, the InstallShield Wizard Complete Installation dialog box appears. Click Finish to complete the Custom installation. When installation is done, you should see a SIMSCI group with a INPLANT GUI icon and a desktop INPLANT icon.
Note: If the Setup prompts for a reboot, you must restart your computer for the
software to be correctly configured.
Continue the installation procedure by testing your INPLANT installation.
The following section guides you through network installation.
Installing a Network Version

A system administrator usually installs the network version. As system administrator, you have two options:

Install all files from the INPLANT CD onto a network file server; or Install executable files on network and user directories locally.
3-5
Install all Files onto a Network File Server (NFS)

This option is typically done in preparation for local installations. You simply copy all of the files and folders from the INPLANT CD to the network server. This makes the install program accessible to users on the network who can then perform a local installation to their local hard drives.
Install Executable Files on an NFS and User Directories Locally

This option is a two-part installation: 1. An installation of executables and their related files on the network. 2. Installations of user directories on each users local disk drive using the INPLANT New User install procedure. The following sections guide you through network installation.
Install Executable Files on an NFS:

Begin the install process as previously stated in Installing a Standalone Version, p. 3-1. Select the INPLANT Network installation procedure. The Welcome to InstallShield Wizard dialog box appears. Click Next > to proceed. The Choose Destination Location dialog box appears. This box shows the default destination directory (C:\SIMSCI) of the INPLANT files. To install to this folder, click Next >. To install to a different folder, click Browse... and select another folder. The Select Features dialog box appears. The Select Features dialog box allows you to select the additional components you want to install. The list box shows all possible components. Check the components you want to install, uncheck the components you do not want to install, and note the change in required disk space. Remember what you choose to install will become defaults during the New User install. Click Next > to proceed. The Make Security Options Install dialog box appears. Here you will select which security option will appear as the default
3-6
Installing INPLANT
in the INPLANT New User install. Select one of the four security options: USB Utilizes a USB hardware key attached to the USB port on the back of the current machine for licensing purposes. Using this type, INPLANT will only search this hardware key for license(s). Allows INPLANT to go beyond the current machine to obtain licenses from another machine (FLEXlm7.2 security server machine) on the network. Allows INPLANT to go beyond the current machine to obtain licenses from another machine (FLEXlm9.5 security server machine) on the network for licenses. Allows INPLANT to go beyond the current machine to obtain licenses from a Token server on the network.
FLEXlm7.2
FLEXlm9.5
Token
If you chose FLEXlm9.5, or Token, specify one or more FLEXlm license servers from which INPLANT will obtain the license. Click Next > to continue. The Start Copying Files dialog box appears which summarizes your settings. If you want to review or change any settings, click < Back. If you are satisfied with the settings, click Next > to begin copying files. When your installation is complete, the Complete INPLANT Installation dialog box appears. Click Finish to complete the installation.
3-7
Typical Directory Structure on a Network Drive

F:\..\SIMSCI\INPLANT40\BIN F:\..\SIMSCI\INPLANT40\LIB F:\..\SIMSCI\INPLANT40\SYSTEM F:\..\SIMSCI\INPLANT40\MANUALS F:\..\SIMSCI\INPLANT40\GUISETUP F:\..\SIMSCI\INPLANT40\USERADD [Program executable files] [Component library directory] [INPLANT system files] [Online Documentation Files] [GUI Setup files] [User-added Subroutine filesoptional [GUI Bitmaps and icon files]
F:\..\SIMSCI\INPLANT40\RESOURCE
where F:\..\ is the subdirectory on your network drive.

Note: The User-added Subroutine files will appear only if the user has selected
them during the network installation.
Install User Directories Locally

The INPLANT New User install program installs INPLANT User directory and icons that are linked to the executable files on the network server. Each user must execute the INPLANT New User install program from their machines. To install user directories locally:

On the client machine map to the drive and directory to which you have installed the INPLANT Network Version. Locate the GUISetup directory and run SETUP.EXE in this directory. The first screen you will see in the installation process is the InstallShield Wizard for INPLANT. Once the Windows configuration is completed, an Application Type screen appears, which allows you to select to install either INPLANT or Acrobat Reader. Select INPLANT. Click Next >.
3-8
Installing INPLANT
The License Agreement dialog box appears. Click Yes > to continue. The Choose Destination Location dialog box appears. This box shows the default destination directory (C:\SIMSCI) of the INPLANT files. To install to this folder, click Next >. To install to a different folder, click Browse... and select another folder. The Select Features dialog box appears. The Make Security Options for Newuser Install dialog box appears. Select one of the four security options: Utilizes a USB hardware key attached to the USB port on the back of the current machine for licensing purposes. Using this type, INPLANT will only search this hardware key for license(s). Allows INPLANT to go beyond the current machine to obtain licenses from another machine (FLEXlm7.2 security server machine) on the network. Allows INPLANT to go beyond the current machine to obtain licenses from another machine (FLEXlm9.5 security server machine) on the network for licenses. Allows INPLANT to go beyond the current machine to obtain licenses from a Token server on the network.
USB
FLEXlm7.2
FLEXlm9.5
Token
If you chose FLEXlm9.5, or Token, specify one or more FLEXlm license servers from which INPLANT will obtain the license. Click Next > to continue. The Select Program Folder dialog box appears. By default, the setup program adds INPLANT icons in the SIMSCI program folder. You may type a new folder name, or select one from folder name, or select one from the existing folders list. Click Next > to continue. The Start Copying Files dialog box appears which summarizes your settings. If you want to review or change any settings,
3-9
click < Back. If you are satisfied with the settings, click Next > to begin copying files.

When your installation is complete, the Complete INPLANT Installation dialog box appears. Click Finish to complete the installation.
After you have installed local directories for a user, setup returns you to the users desktop. Newly installed program icons appear in the group you selected. A typical installation produces the following icons: INPLANT 4.0 INPLANT 4.0 Online Help Programmers File Editor
Note: If the Setup prompts for a reboot, you must restart your computer
for the software to be correctly configured.
Uninstalling INPLANT
You can uninstall INPLANT by accessing Add/Remove Programs in the Control Panel. To uninstall INPLANT:

Click Start. Select Settings and then select Control Panel. Double-click Add/Remove Programs. The Add/Remove Programs Properties dialog box appears. Select INPLANT 4.0 (for Typical & Custom) and INPLANT 4.0 workstation for Graphics only install (Network install). Click Add/Remove. Click Yes to confirm the deletion. A message may ask you whether to delete a shared file. If you know that the file is not used by another application, click Yes. Otherwise, click No. Uninstall deletes the component and displays a screen verifying deletion.
3-10
Installing INPLANT
Click OK again.
Note: The order of uninstalling components and/or creating files under the
INPLANT tree may cause certain single files to remain on the disk. After uninstalling a component, check the corresponding installation directory for remaining files and delete them manually.
Accessing User-Added Subroutines (UAS)

You can choose to install the directories for UAS during the standard installation procedures. See the instructions earlier in this chapter. Building and Using INPLANT UAS UAS written in FORTRAN can be integrated into INPLANT by creating a new D_MAINONE.DLL module. UAS for the INPLANT thermodynamics can be integrated into INPLANT by creating a new FFPESMainDLL.DLL. The UAS must be compiled and linked using Compaq Visual FORTRAN (or CVF) for Windows 2000/XP. Refer to Hardware/ Software Requirements, p. 2-2 for information concerning the version of CVF required for this release of INPLANT. The build procedures outlined in this chapter assumes that you are familiar with the currently supported versions of the Windows OS and CVF. If you already have CVF installed on your computer, you can find information on setting up your computer's environment in the batch file located at c:\program files\devstudio\df\bin\dfvars. This manual does not contain instructions on writing the FORTRAN subroutines or using CVF. For information on using CVF, see the Compaq Visual FORTRAN Programmer's Guide.
Note: These instructions assume that you have installed the INPLANT UAS files in the default directory structure, C:\SIMSCI\INPLANT40\USERADD. Modify the paths indicated in the procedure below if you have installed the routine in a directory structure other than the default structure.
3-11
Workspace for INPLANT User-Added Routines

The workspace C:\SIMSCI\INPLANT40\USERADD\Makewsp\MAKEWSP.DSW contains several projects, listed below in the order most commonly used:
Table 3-1: Work Space for INPLANT User-Added Routines Project D_MAINONE MAINONE_CPP FFPESMAINDLL Description
Project used to update INPLANT user-added routines (i.e. HUSER1.FOR) Main program entry point provided for debugging purposes Project used to update INPLANT thermo user-added routines **(i.e. HUSER1.FOR) Main program for thermo preprocessor provided for debugging purposes
Build Products D_MAINONE.DLL MAINONE.EXE FFPESMainDLL.DLL
MAINTI
MAINTI.EXE
** Refer to the INPLANT documentation for information regarding INPLANT User-Added capabilities.
Note: Build products must be copied into the C:\SIMSCI\INPLANT40\BIN
directory. You should save the original products into another directory in case you want to go back to the standard release version.
3-12
Installing INPLANT
Build Sample One: Customize a Pressure Drop Model

In this sample build procedure, we will integrate the sample UAS routine HUSER1.FOR into D_MAINONE.DLL. First you must open the development project:

Start CVF by selecting it from the Start menu. Select the Open Workspace option from the menu. Select project \SIMSCI\INPLANT40\USERADD\MAKEWSP\MAKESP.DSW Set the active project to D_MAINONE by selecting Set Active Project from the Project menu.
Next you must add the file HUSER1.FOR into project:

Select the folder CLIENT USER FILES and use the right mouse button to select the Add Files to Folder option Add the file \SIMSCI\INPLANT40\USERADD\USERSRC\HUSER1.FOR. (If this file is already in the project, a message will be displayed.) Click OK to close the window and update the project file.
Next you can update the code and build D_MAINONE.DLL:

Modify the user-added routine. For example, increase the frictional pressure drop by 10% (PGF = PGF*1.1). Select the Win 32 Release version. Select the Rebuild All option from the Build menu. This builds D_MAINONE.DLL in directory \SIMSCI\INPLANT40\USERADD\MAKEWSP. Copy this file to the \SIMSCI\INPLANT40\BIN directory.
Now you can verify the UAS in the build
Run the file \SIMSCI\INPLANT40\USERADD\USERINP\HUSER.INP and compare the results to file HUSER.CHK. View the Node Summary and verify that the pressure drop has changed as expected.
You may also use the MAINONE_CPP project for debugging.
Repeat the build procedures for D_MAINONE.DLL, but select the Win 32 Debug option. D_MAINONE.DLL will still be built in the directory \SIMSCI\INPLANT40\USE3-13
RADD\MAKEWSP. Copy this file to the \SIMSCI\INPLANT40\BIN directory.

Now set the active project to MAINONE_CPP by selecting Set Active Project from the Project menu. Select the Win 32 Debug version. Select the Rebuild All option from the Build menu. CVF will build the MAINONE.EXE in the directory \SIMSCI\INPLANT40\USERADD\MAKEWSP. Copy this file to the \SIMSCI\INPLANT40\BIN directory. Set the debug options as follows:
Executable for Working Dir Program Arg. \SIMSCI\INPLANT40\BIN\MAINONE \SIMSCI\INPLANT40\BIN /F=filename / D=\SIMSCI\INPLANT40\USER\ / I=\SIMSCI\INPLANT40\USER\ INPLANT.INI
Set a breakpoint in MAINONE_CPP at command to Run Preprocessor and run to this breakpoint. Now you can set breakpoints in the user-added routines and debug as normal.
3-14
Installing INPLANT
Build Sample Two: Customize an INPLANT Thermo Routine

In this sample build procedure, we will integrate the sample UAS routine UKHS1.FOR into FFPESMainDLL.DLL. First you must open the development project:

Start CVF by selecting it from the Start menu. Select the Open Workspace option from the menu. Select file C:\SIMSCI\INPLANT40\USERADD\MAKEWSP\MAKEWSP.DSW and click OK. Set the active project to FFPESMainDLL by selecting Set Active Project from the Project menu.
Next, you must add the file UKHS1.FOR into the project:

Select the folder CLIENT USER FILES and use the right mouse button to select the Add Files to Folder option Add the file \SIMSCI\INPLANT40\USERADD\USERSRC\UKHS1.FOR. (If this file is already in the project, a message will be displayed.) Click OK to close the window and update the project file.
Next you can update the code and build FFPESMainDLL.DLL:

Select the Win 32 Release version. Modify the user-added routine. For example, increase the liquid density by 10% (DENSE = DENSE*1.1). Select the Rebuild All option from the Build menu. CVF will build the FFPESMainDLL.DLL module in the directory \SIMSCI\INPLANT40\USERADD\MAKEWSP. Copy this file to the \SIMSCI\INPLANT40\BIN directory.
Note: To update the version identification to include the UAS, you must
rebuild D_MAINONE.DLL as described in the previous example.
3-15
Now you can verify the UAS build:
Run the file \SIMSCI\INPLANT40\USERADD\USERINP\ETH_UAS.INP and compare the results to file ETH_UAS.CHK.
Note: You may debug your routines by building this dll in debug mode as
described in the previous example.
3-16
Installing INPLANT
Chapter 4 Installation Troubleshooting

This chapter addresses some of the more common support questions and problems related to TOKEN and FLEXlm 7.2/9.5, USB, and General License security. If you are having problems installing this product, review this section. If you are unable to correct the problem, contact Technical Support located at your local SIMSCI Technical Support Center, as listed in Chapter 1, Introduction.
Diagnosis of Problems with TOKEN and FLEXlm 7.2/9.5 Security

Step 1 - Ensure that the FLEXlm server is working correctly When encountering a licensing problem with TOKEN or FLEXlm 7.2/9.5 security, first ensure that the FLEXlm server is running without any errors. The TOKEN license server is actually a FLEXlm 9.5 server, and the only difference between these two types of license servers lies in the license files, one being tokenbased (each product requires a specified number of tokens when used) and the other product-specific. Incidentally, only a 9.5 FLEXlm server can manage a SimSci-Esscor TOKEN license file. There are two ways to verify that the FLEXlm server is running correctly. The first way is to examine the FLEXlm server debug log file ipassi.log. This log file is by default located in the FLEXlm directory (C:\Program Files\IPASSI\Security\FLEXlm for FLEXlm 7.2 and C:\Program Files\IPASSI\Security\FLEXlm95 for FLEXlm 9.5) The actual location for this log file can be found from the FLEXlm lmtool.exe utility in the Path to the debug log file
4-1
field on the Config Services tab (See figure below). Carefully go through the log file to see if there are any errors recorded in this log file.
Figure 4-1: LMTools Configuration Service
Alternatively, after attempting to start the FLEXlm server, start the lmtools.exe utility, click on the Server Status button on the Server Status tab, and then click the Perform Status Enquiry button (as shown in the Figure below). Again, carefully go through the output text to find any error messages. Note that if you need to perform the server status enquiry multiple times, you can use Edit>Clear Window from the menu bar as this will clear the output text box for easy reading.
4-2
Installation Troubleshooting
Figure 4-2: LMTools Server Status
If there are any error messages in the FLEXlm server log file or in the lmtool.exe Server Status output text window, try and take appropriate action to resolve the problem yourself. Examples: If you try to start the FLEXlm server on a license file not intended for the license server, you will get an authentication error. In this case, you will either need to install the license (and FLEXlm server) on the machine for which the license was generated, or contact your SimSci-Esscor sales representative to issue you a license file for the machine on which the FLEXlm server is installed. Another issue could be that the licenses themselves have expired. The expiration date can either be obtained by looking at the license file, ipassi.lic, or by clicking on the Perform Diagnostics button on the Server Diags tab. If the licenses have expired, then contact your SimSci-Esscor sales representative to renew your licenses. A further common error is that the FLEXlm server machine name, the second item on the SERVER line in the FLEXlm license file, is not stated correctly. An example of the server line, from a permanent license, is as follows: SERVER miawa2ca 000874fe5ea8 Or for a temporary license: SERVER ukfcra-g6fyq0j ANY
4-3
Note, for a temporary license the ANY, the third item on the SERVER line, must be retained. If the machine name is correct in the SERVER line but the FLEXlm server is still not starting correctly, then use the IP address of the server machine instead of the machine name. For errors that you cannot resolve yourself, contact your SimSciEsscor technical support for assistance. When doing so, have the server log file available to send as this will aid in the troubleshooting. Step 2 - Ensure that the application is using FLEXlm/TOKEN security If the FLEXlm server is up and running with the correct license, but there is still a problem launching the application due to a FLEXlm/ TOKEN security error, then the focus should switch to the SimSciEsscor application side. The second step in troubleshooting FLEXlm/TOKEN security is to verify if FLEXlm/TOKEN is indeed the active license security type. This selection of license security type is made in the main initialization file (*.ini) of the application. These files are usually named after the applications they control, such as PROII.ini, PipePhase.ini, Datacon.ini, etc. The easiest way to locate these ini files is to search the application directory for the *.ini file that contains the string [wss_Security]. Once you identify the ini file, you need to open the file (NotePad will work fine for this) to see what the active security type is. Search for the Type statement in the [wss_Security] section. The active security Type statement is the one that does not have a semicolon (;) in front of it. If FLEXlm/TOKEN is not the current active security type, you will need to comment out the current active type by placing a semi-colon at the beginning of that line, and uncomment the ;Type=FLEXlm or the ;Type=TOKEN line. For example: [wss_Security] (if you are using FLEXlm 9.5 for security) Type=FLXLM95 ;Type=USB ;Type=FLXLM72 ;Type=TOKEN Or
4-4
[wss_Security] (if you are using TOKEN for security) Type= TOKEN ;Type=USB ;Type=FLXLM72 ;Type= FLXLM95 If FLEXlm/TOKEN security was previously not the active security type and has now been made the active security type, the user should test the application to verify that the change has corrected the problem. If the FLEXlm/TOKEN security still does not work, proceed to Step 3 for further diagnosis. Step 3 - Ensure that the application is using the correct set of security files This step involves checking the security files at two levels. At the first level, the user needs to make sure that the application is actually using its own set of security files (scintf.dll, token.dll, flxlm72.dll, and flxlm95.dll). Sometimes multiple copies of the security files exist on the machine and the application may be using the file(s) somewhere on the paths specified in the PATH environment variable, not the ones under its own directory. Since this will create significant confusion during security troubleshooting, it is highly recommended that all security files that are not part of any SimSci-Esscor application file systems be deleted, especially the ones on the PATH environment variable. When this is done, the user can be sure exactly which security files the application is using. The second level is only applicable to the FLEXlm security. The SimSci-Esscor FLEXlm security comes in two versions, 7.2 and 9.5. Because these two versions are not completely compatible with each other, it is critical that the FLEXlm client (the flxlm.dll on the application side), the license file, and the FLEXlm server be of the same FLEXlm version. The symptom of this incompatibility is that the application fails and in the server debug file you see the license is checked out and back in almost at the same time. The FLEXlm server version can be found in the server log file (ipassi.log) and the license file version can be found in the license file itself. If the version cannot be found in the license file, then the license file should be FLEXlm version 7.2. The version of the flxlm.dll can be found by right-clicking the file, selecting Properties, and then selecting the Version tab. From 2006, we are moving towards using
INPLANT 4.0 Getting Started Guide 4-5
the FLEXlm version in FLEXlm dll file names. For instance, flxlm72.dll means the file is version 7.2 and flxlm95.dll means version 9.5. Moreover, the value of the Type statement in the application ini file also uses flxlm95 and flxlm72 to reflect the FLEXlm version it is using. Step 4 - Ensure that the FLEXlm communications are functioning properly If the FLEXlm server is running correctly and the application's licensing configuration is appropriate, but there is still a FLEXlm/ TOKEN licensing problem, turn the focus to the communications between the application machine and the FLEXlm server machine. To do this, first ping the FLEXlm server machine from the application machine to see if the communications between them are enabled. If not, the user should contact their IT personnel to resolve this issue first. After the fundamental communications problem is resolved, examine the value of the environment variable IPASSI_LICENSE_FILE on the application machine to see if the value points to the intended FLEXlm server machine. If this value has been set multiple times, examining and editing the value in the registry may be necessary because the old value may be cached in the registry location. Figure 4-3 shows the registry entry for server @cms4m0ca:
Figure 4-3: Registry Entry for Server @cms4m0ca
The user can directly delete or edit the value of the IPASSI_LICENSE_FILE from here or run lmpath.exe to accomplish the same result. Another issue with this environment variable is that sometimes the application machine system has a problem resolving the FLEXlm server machine name into the IP address. In this case, instead of using the FLEXlm server machine name for value of IPASSI_LICENSE_FILE, use the FLEXlm server machine's IP address, such as @123.12.10.100.
4-6
If the environment variable is managed correctly and the problem still persists, the user may resolve the problem based on any error messages rendered on the application side. The user should examine the contents of the FLEXlm server log file ipassi.log to see if there are any records about the license request. If there are no records at all in the server log file about this license request, then the communication between the FLEXlm client and FLEXlm server have not been established. In this case, the user needs to examine the firewall on the FLEXlm server machine to ensure that the port numbers used by the FLEXlm server (lmgrd.exe) are enabled for the communication. The port numbers used by the FLEXlm server can be found in the FLEXlm server log file ipassi.log.
4-7
Example: 10:21:59 (lmgrd) lmgrd tcp-port 27000 10:22:10 (lmgrd) IPASSI using TCP-port 2601 Another possible FLEXlm communication issue may be encountered accessing FLEXlm licenses over the internet, as it may take longer for the application to connect to the FLEXlm server machine. If this takes too long, the application may prematurely timeout the connection attempt and return an error. To overcome this problem, set the environment variable FLEXLM_TIMEOUT on the application machine. The usage of this variable is as follows: Set the timeout value of a FLEXlm-licensed application when attempting to connect to a license server port in the range 2700027009. Values are in microseconds, within the range 0 through 2147483647. The default setting is 100000 microseconds. The other thing the user can do to reduce the connection time is to explicitly set the FLEXlm server ports such that the application knows exactly what ports to talk to. Please refer to Table 4-1 for details on setting up explicit FLEXlm server ports.
Table 4-1: FLEXlm License Security-related Problems and Solutions Problem Fix Can I have multiple FLEXlm servers installed and run on the same machine? Yes, it is allowed to install and simultaneously run multiple FLEXlm servers from different vendors on the same machine. When doing so, it is highly recommended that you install the servers to different locations so that they do not interfere with one another. However, multiple FLEXlm servers from the same vendor cannot run simultaneously. Only one version can be active at a time. For example, the IPASSI FLEXlm 7.2 and 9.5 can be installed in different locations on the same machine, but only one of them can be running at a time. I have multiple IPASSI license files on my FLEXlm server machine. Can I combine them into one? If those license files have an identical SERVER line, then they can be combined. Otherwise, the answer is no. After the merge, there should be only one SERVER line and one VENDOR line in the resultant license file.
Problem Fix
4-8
Problem Fix
How do I instruct my IPASSI FLEXlm server to use multiple license files? Use lmtools.exe to configure the FLEXlm service so that the field Path to the license file points to the directory where the license files are located (as shown below). In addition, all the license files in the directory must have the. lic file extension name.
Problem Fix
How can I make FLEXlm security work with firewall on the FLEXlm server machine? To make FLEXlm security work with firewalls, the following three components must be configured correctly. 1. Use a port number on the SERVER line in the license file as follows: SERVER host hostid [port] Example: SERVER ips-sol07 0002b303df80 27000 2. Use another port number on the VENDOR line in the license file: VENDOR vendor [port=]port Example: VENDOR IPASSI port=27001 3. On the application machine, set the value of the environment variable IPASSI_LICENSE_FILE to be 27000@ips-sol07. The port number here is the port number from the SERVER line. Make sure both the ports are enabled on the FLEXlm server machine. Ensure that the port numbers for the SERVER line and for the VENDOR line are not used by other applications on the FLEXlm server machine, and are different from each other.
4. 5.
Problem Fix
How do I automatically launch my FLEXlm server when I reboot my FLEXlm server machines? For FLEXlm servers on Windows NT/2000/XP/2003 machines, this is possible through the Config Services tab. On this tab, check the Use Services and the Start Server at Power Up checkboxes and save the server configuration.
4-9
Problem Fix
How do I prevent my FLEXlm server from being manipulated by users on other machines? Beginning with FLEXlm 9.5, when you are starting the FLEXlm server, you can specify that users on other machine cannot shut down the FLEXlm server. To do this, go to the Start/Stop/Reread tab, select the service you are about to start, click the Advanced settings, and check lmdown will only work from node where lmgrd is running. Then, click Start Server.
Problem
If I get the message below when launching a SimSci-Esscor application, what could be going wrong?
Fix
A common cause of this error is that the FLEXlm dll on the application is of version 7.2, but the FLEXlm server is 9.5. In this case, run the FLEXlm 9.5 Client Retrofit program to update the application and this should resolve the problem.
4-10
Problem Fix
How do I obtain the system information about the machine, including the host ID? The FLEXlm utility, lmtools.exe System Settings tab, is always the most accurate for checking the host ID. Note that when issuing a FLEXlm/TOKEN license, SimSci-Esscor uses Ethernet Address or Disk Volume Serial Number to bind the license. If your FLEXlm cannot start correctly, you may want to verify that the Ethernet address or disk volume serial number in the license file is consistent with that on the machine. In addition, you may check the Computer/ Hostname to verify that this value is the same as the second item on the SERVER line in your license file. An example of lmtools System Settings tab display:
Problem Fix
How do I configure the usage of my license(s)? Use a FLEXlm options file to specify how the license(s) should be used. For detailed information, please refer to the Options File documentation. How do I include a FLEXlm options file and how would I know if the FLEXlm server is using the options file? If you use ipassi.opt for the name of the options file, then simply put this options file in the FLEXlm server folder (where the lmgrd.exe and IPASSI.EXE are). When the next time the IPASSI FLEXlm server starts, it will automatically read and apply the rules in this file. If the options file does not have the default file name or is not located in the FLEXlm server folder, then you'll need to explicitly specify the options file on the VENDOR line in the license file as follows:
VENDOR IPASSI options=C:\Program Files\IPASSI\ Security\FLEXlm95\ipassi.opt
Problem Fix
Note that if there are any spaces in the path or the file name, put double quotes around the fully qualified path as above. When an options file is in use, you should see an entry similar to that shown below in the FLEXlm server log file, ipassi.log: 16:12:11 (IPASSI) Using options file: "C:\Program Files\IPASSI\ Security\FLEXlm95\ipassi.opt"
4-11
Problem Fix
Can I use a regular FLEXlm license file and a TOKEN license file under the same IPASSI FLEXlm server? Technically, this configuration should work. However, this is not recommended as the logging and reporting functionalities work differently for FLEXlm and for TOKEN security. For clarity, it is highly recommended that FLEXlm and TOKEN be installed on different license server machines. We're using FLEXlm over a wide-area network. What can we do to improve the FLEXlm licensing performance? To shorten the initial connection time between the FLEXlm Client and the FLEXlm Server over a wide-area network, you can specify the FLEXlm server port numbers in the FLEXlm license file. In this case, the Client will know exactly what ports on the Server machine to use when trying to connect to the Server. We're using FLEXlm over a slow wide-area network. What can we do to allow longer FLEXlm Client/Server initial connection time? You can set the environment variable FLEXLM_TIMEOUT to a larger value on the Client machine. This value sets the timeout period of a FLEXlm-licensed application when attempting to connect to a license server port in the range 27000-27009. Values are in microseconds, within the range 0 through 2147483647. The default setting is 100000 microseconds.
Problem Fix
Problem Fix
Diagnosis of USB Security Problems

When encountering licensing problem with the USB security, you can diagnose the problem following the steps described below: Step 1 - Verify the active type of license security This step is to ensure that USB is indeed the active license security type. This selection of security type is made in the main initialization file (*.ini) of the application. These files are usually named after the programs they control (Proii.ini, PipePhase.ini, Datacon.ini, etc.) The easiest way to locate these files is to search the application directory for the *.ini that contains the word [wss_Security]. When the ini file is identified, you need to open the file (NotePad will work fine for this) and find the value of the Type statement in the [wss_Security] section. The active security type will not have a semi-colon (;) in front of the Type statement. If USB is not the current active security type, you will need to comment out the current active type by placing a semi-colon at the beginning of the line, and uncomment the ;Type=USB line as follows: [wss_Security] Type=USB
4-12
;Type=FLXLM72 ;Type=FLXLM95 ;Type=TOKEN If USB was not previously the active security type and has now been made the active security type just now, the user should test the application to verify that the change has corrected the problem. If the USB security still does not work, proceed to Step 2 for further diagnosis. Step 2 - Examine the USB environment on the machine For the USB security to work, the machine itself must be able to correctly detect the USB key. This step is to determine if this is the case. With the USB key plugged in, go to the Device Manager and open the Universal Serial Bus Controllers to see whether the entry for the USB key is listed correctly as illustrated in Figure 4-4:
Figure 4-4: Device Manager
If there is a conflict or problem, the USB SuperPro controller (shown as Rainbow USB SuperPro) will show up with a yellow exclamation mark or a red X (or may not show up at all). Figure 4-5 shows an example of a USB driver issue, i.e. a yellow exclamation mark displayed by the USB SuperPro entry:
Figure 4-5: Device Manager > USB SuperPro
4-13
When the machine is not detecting the USB entry correctly, please unplug the USB key from the machine and uninstall the existing USB driver using the Add/Remove Programs function (Figure 4-6):
Figure 4-6: Add/Remove Programs
After un-installing the existing USB driver, install the USB 7.0 driver. The install program for USB 7.0 driver is available from the SimSci-Esscor application install CD or from the SimSci-Esscor ESD web site. After installing the driver successfully, the Sentinel Protection Installer 7.0.0 entry should appear in the Add/Remove Programs window as follows:
Figure 4-7: Sentinel Protection Installer 7.0.0
Now, plug the USB key back into the machine and go to the Device Manager again to verify that the system is correctly detecting the USB key. If the problem persists, then either the key is damaged or the computer, including the USB port, may be malfunctioning. In this case, the user will either have to try the key on another machine that has working USB environment to determine if the key is good; or alternatively, the user can try another USB key that is known to be working on another machine to try on this problem machine and verify if its USB environment is functioning correctly. If the result indicates that the USB key is not functioning properly, please return the key to SimSci-Esscor technical support for further diagnosis. If the USB environment on the machine is not working correctly, the user will have to resolve the machine problem first.
4-14
Another method for examining the USB environment is to use the SuperproMedic utility program (SproMedic.exe) from Rainbow Technology. The install program (SuperproMedic.exe) for this utility is available in the Utility folder in the USB 5.0 Retrofit program, which can be found in the SimSci-Esscor ESD web site. The default install location for this program is C:\Program Files\ Rainbow Technologies\SuperPro\Medic. This program displays the version of the current Sentinel System Driver on the machine. Note that not all versions of Sentinel System Driver work with the SimSci-Esscor USB key. If the existing USB driver is not a good one, the SuperproMedic utility program will indicate the problem as shown below (Version 5.39.2 - Unknown S):
Figure 4-8: SuperproMedic
In this case, the user will have to unplug the USB key from the machine, un-install the current USB driver, and then re-install the USB 7.0 driver. When the utility program shows no error in the Sentinel System Driver, the user can click on the Find SuperPro button to see if it can detect the USB key. If it finds the key, the output should look similar to Figure 4-9 (1 Hard limit of first key found):
Figure 4-9: USB Key Detected
4-15
If no keys are detected, the output is as follows (0 Hard limit of first key found):
Figure 4-10: USB Key Not Found
Step 3 - Examine the SimSci-Esscor USB key and the USB.DLL If the SproMedic.exe utility can correctly detect the USB key, the next thing to look at is the usb.dll and the USB key. A potential problem with the USB.DLL is that it may not be recent enough to recognize the applications turned on in the USB key. To eliminate this problem, the user simply downloads the USB 5.0 Retrofit program from the Update area in the SimSci-Esscor ESD web site, and then retrofits the application accordingly to update the USB.DLL. After the retrofitting, the user can run the USBKeyCheck.exe utility program first to see if the USB key is good. If the USBKeycheck.exe program indicates that the USB key has already expired or does not contain the license to run the application, please contact the SimSci-Esscor sales representative to resolve this issue. Step 4 - Examine the copies of USB.DLL on the machine Sometimes there are multiple copies of USB.DLL existing on the machine. In this case, the application may or may not be using the newly updated USB.DLL obtained from the previous step. The SimSci-Esscor security files, including USB.DLL, should only exist inside the application folder and the application should only use its own set of security files. Should there be any SimSci-Esscor security files existing outside of all SimSci-Esscor application folders, it is highly recommended that they be deleted to eliminate the confusion, especially those that exist on the paths specified in the PATH environment variable.
4-16
General License Security Questions

Table 4-2: General License Security-related Problems and Solutions Problem Fix Problem Fix Can I use mixed security types in one application session? No. With the current license security implementation, only one licensing type can be used in one application session. Where do I download SimSci-Esscor license security software? As long as you have a valid SimSci-Esscor ESD user account, you are eligible to download the license security programs/utilities from the ESD web site. The steps for the download are: 1 Open the web page http://www.simsci-esscor.com 2 Select Support->Software Updates & Knowledge 3 Click the Enter the SIM4ME Software Updates & Knowledge Base Website link 4 Click the License Security link 5 Enter your user name and password and click the Login button 6 Click the Updates/documentations/Examples/Utilities/ Simulation Tips link 7 Click the item that you'd like to download You have problems reading the disks: General failure reading drive, repeats the request for the next disk (wrong disk). Errors during the installation or unloading of the archived files. 1 2 1 2 Verify that you have inserted the correct disk. Insert the disk again and retry. Verify the disk with CHKDSK. If the disk cannot be read, or if CHKDSK shows errors, contact Technical Support for fast replacement.
Problem
Fix 1 Fix 2
Problem Fix 1 Fix 2
Invalid path of access failures: You receive messages that files could not be copied and that the installation failed. If you are installing to a network, ensure that you have adequate read/ write access privileges. Ensure that you have enough disk space in the specified directory.
4-17
Problem Fix 1 Fix 2
Security chip missing errors. The security device must be the first item in parallel port. Make sure that the security installation has been completed correctly and that you have the security device listed in the installation instructions. Make sure that the security device is firmly inserted into the parallel port. Check the 25 connector pins on the security device for damage. If a printer is attached, make sure it is turned on. Some laptop computers do not put out enough voltage to the parallel port to return an answer to the program. You can test this by attaching a printer, turning it on, and executing the program. If it works with a printer attached, then you can use that as a solution, move the program to another computer, or contact Technical Support for a special battery adapter to increase voltage directly to the security device number. Something to try: Some laptop problems have been resolved by attaching a cable at least two feet long to the printer side of the security device (no printer). Make sure only similar security devices are piggybacked. INPLANT is installed on a system running Windows NT. When you run INPLANT, it produces errors relating to security. Ensure that whoever installed INPLANT had system administration rights/privileges.
Fix 3 Fix 4 Fix 5
Fix 6 Problem Fix
4-18
Chapter 5 Sample Session

Overview
This sample shows a typical session using the INPLANT GUI to enter data for a simulation, execute the calculations, and review the results. The Problem Build a flowsheet for a gathering adiabatic net coming from buried sources and pipes to above surface pipes and sinks with a planned flow reversal in one of the links.
Table 5-1: Problem Design Constraints Feature Parameter Overall Dimensions Temperature Pressure Molar Rate Weight Rate Liquid Volume Rate Gas Volume Rate Length Duty Calculation Type Pressure Drop Correlation Nominal Pipe Diameter Pipe Schedule Pipe Roughness Pipe heat transfer coefficient Conductivity, Air Viscosity SI F PSIA MOLHR KGHR CMHR CFHR FT,IN KCHR Network, Compositional (GAS) PIPE= eaton 8 40 .001800 5.6783 2 .02
5-1
Table 5-1: Problem Design Constraints (cont.) Feature Parameter Density Velocity Soil, Conductivity Pipe Buried Depth Pipe Thickness Pipe thermal conductivity Pipe Segment Length Maximum # of Segments Minimum pressure Maximum pressure Flow allocation Pressure Tolerance Thermal System Transport System 1000 5 2 480 0.500 50 50 30 0 25014.699 Total resistance 10 LKP, density (vapor) = LK HCMIX
Step 1 Getting Started, Setting Up the Problem

Assuming that the installation has been successfully completed and you have launched the application, INPLANT will automatically guide you through the first few dialog boxes of a new problem setup. To create a new problem:

Click on the File menu and select New or click the icon on the tool bar. A New dialog box appears as shown in Figure 5-1. Enter a name for the new simulation.
5-2
Sample Session
Figure 5-1: Create New Problem Dialog
INPLANT will now automatically take you through the Simulation Setup Wizard as shown in Figure 5-2.
Figure 5-2: Simulation Setup Wizard
Click the Next button.
INPLANT will now bring up the Simulation Type dialog box as shown in Figure 5-3.
5-3
Figure 5-3: Select Simulation Type
Select the Network model Simulation Type. Click the Next button.
Figure 5-4: Select Fluid Type
Select Gas as Fluid Type. Click the Next button.
5-4
Sample Session
Figure 5-5: Select Default Units of Measurement
Select SI as Default Units of Measurement. Click the Next button.

Figure 5-6: Confirm the Selections
Confirm your selections. Click Finish.
5-5
Step 2 Selecting Components

Because we are specifying a compositional fluid in this problem, INPLANT will automatically bring up the Component Data dialog box shown in Figure 5-7 to select the components. This dialog box displays the Library and Petroleum components that have been defined. A number of buttons are available to add and edit component data.
Figure 5-7: Component Data Dialog
To select components:
Click on the Add button. The Library Component Data dialog box appears as shown in Figure 5-8.
5-6
Sample Session
Figure 5-8: Library Component Data Dialog
The components we wish to add are all in the component family and Most Commonly Used is the default family. The first component we wish to add is Ethane.
Scroll through the Specific Components Available for Selection list box until ETHANE is found, then highlight it by clicking on it with the mouse. Then click the Add Components button. ETHANE will appear as a component in the lower list box. Do the same to add METHANE and then click OK. The Library Component Data dialog box will now appear with the two selected components. Click OK to complete the component selection.
Step 3 Selecting Thermodynamic Methods

After completing the component selection, INPLANT will automatically open the Fluid Property Data window as shown in Figure 5-9.
5-7
Figure 5-9: Fluid Property Data
Click New on the Fluid Property Data window. A new Property Set is created. Select the Property Set and click Edit on the Fluid Property Data window. The Thermodynamic Data dialog box appears as shown in Figure 5-10. Select the thermodynamic methods shown and click OK.
5-8
Sample Session
Figure 5-10: Thermodynamic Methods
Note: If you want to edit the component data and thermodynamic methods at a
later stage, click the respective buttons available on the toolbar or from the General menu pull-down options.
This will bring up a Note dialog box as shown in Figure 5-11 to inform the user of the significance of colors used in the GUI.
Figure 5-11: Note on Color indicators
Click the OK button to continue.
Step 4 Describing and Defining the Simulation

To enter the simulation details like description, definition, and inputs units of measurement, follow the steps below:
From the toolbar, select General/Simulation Description. This will bring up the Simulation Description window shown in Figure 5-12.
5-9
Figure 5-12: Simulation Description
Enter the Project, Problem, User, Date, Site, and Description data entry fields and click the OK button. From the toolbar, select General/Simulation Definition. This will bring up the Simulation Definition window shown in Figure 5-13.
Figure 5-13: Simulation Definition
Use the drop-down list boxes to select Simulation Type as Network Model and Fluid Type as Compositional and the phase as Gas. Click the OK button to continue.
After leaving the Simulation Definition window, you will want to check Input Dimensions. From the toolbar, select General/Input Units of Measurement. This will bring up the Input Dimensions window shown in Figure 5-14.
5-10
Sample Session
Figure 5-14: Inputs unit of measurement
For this problem, change the defaults for temperature, pressure, and other units as shown in Table 5-1 Click OK to continue.
Step 5 Selecting Printer Options
Select and click Print Options... under the General pull-down menu. The Print Options dialog box will appear as shown in Figure 5-15 In this problem we want the following Plot/Print options: Provide iteration history No connectivity diagram (diagram of flowsheet) Output Reports in both the OLD and the NEW formats. To enter this setup: Enter the settings shown.
5-11
Figure 5-15: Problem Definition Dialog
Step 6 Entering Calculation Options

To enter the calculation options:
Select and click Calculation Options... under the General pulldown menu. The Network Calculation Methods dialog box will appear as shown in Figure 5-16. Check the Adiabatic Sources option since the simulation deals with gathering adiabatic net from buried sources and pipes to the surface pipes and sinks.
Figure 5-16: Network Calculation Methods Dialog
5-12
Sample Session
Click the Segmentation Data button on the Network Calculation Methods window and enter the segmentation data of the pipe as given in Table 5-1. Click the T/P Limits... button on the Network Calculation Methods window and enter the minimum and maximum pressure limits. Click OK and exit the Network Calculation Methods window.
Step 7 Entering Global Defaults

To enter global defaults:
Click the Global Defaults... option under the General pulldown menu. The dialog box will appear as shown in Figure 5-17. Enter the data and click the OK button.
Figure 5-17: Piping Global Defaults Dialog
For this problem, we must enter Air, Soil, and Pipe Heat Transfer data as shown in Table 5-1.
Click the Air Heat Transfer... button on the Pipe Global Defaults window. The Air Heat Transfer Defaults dialog box appears. Enter the data as shown in Figure 5-18 and click the OK button. Do the same for the Soil Heat Transfer Defaults... (Figure 5-19) and the Pipe Heat Transfer Defaults... (Figure 5-20).
5-13
Figure 5-18: Air Heat Transfer Defaults Dialog
Figure 5-19: Soil Heat Transfer Defaults Dialog
Figure 5-20: Pipe Heat Transfer Defaults Dialog
Before leaving the Piping Global Defaults dialog box:

Click the Pressure Drop Methods Defaults... button. The dialog box appears as shown in Figure 5-21. Enter pressure drop data and click OK.
5-14
Sample Session
Figure 5-21: Pressure Drop Defaults Dialog
Step 8 Drawing the Flowsheet

In this section, you will learn how to select and add nodes and links to a flowsheet. We will guide you through a typical sequence which will be of direct benefit in entering the remainder of the problem yourself. The sources, junctions, and sink for this problem are summarized in Table 5-2.
Table 5-2: Source, Junction, and Sink Summary Pressure Temp Rate (esti, GV) Comp (GV)
Sources
S000 S001 S002

Junctions
1000 1000 1000
80 80 80
5 5 5
40/60 50/50 REF(S002)
J000 J001 J002

Sinks
D000
500
10
To add node S000:

Click on the node icon on the tool bar. Move the icon to a location on the flowsheet. Click once on the flowsheet to place the icon at that position. Double-click on the icon to enter data. The dialog box shown in Figure 5-22 will appear.
5-15
Figure 5-22: Compositional Source Dialog
Enter the temperature, pressure, and rate data. Click on the Define Composition button. The Source Composition worksheet shown in Figure 5-23 will appear.
Figure 5-23: Source Composition Worksheet
Enter the composition. Click the OK button on the Compositional Source dialog box.
5-16
Sample Session
The Sink node can be added to the flowsheet in a similar manner. The Junction nodes require no input data.
Note: Make sure that the names of the nodes and junctions are consistent
with those given in the problem. This information is editable in the input data dialog box for each node.
Your flowsheet should look similar to that shown in Figure 5-24 (without the links drawn).
Figure 5-24: Flowsheet without links
Now we are ready to draw the links and add devices on the links. Table 5-3 summarizes the links and devices for the problem. As an example we will use link L002. Click on Node S000 to reveal its attachment square. We are now going to create the link. Grab the attachment square and click on it with the left mouse button. Hold the left mouse button down and drag it to junction J006's attachment square. Release the left mouse button. The link has been created. Add devices to the link by double-clicking on the link to bring up the Device Data dialog box as shown in Figure 5-25.
5-17
Figure 5-25: Device Data Dialog
As you can see from Table 5-3, link L002 contains a pipe device.
Click the Pipe button on the device palette to add this device to the link. This automatically brings up the Pipe data entry window.
Figure 5-26: Pipe Input Data Dialog
Enter the data given in Table 5-3 and click the OK button. To complete the device adding process, click the OK button in the top left hand side of the Device Data dialog box. Create the other links with devices by repeating the steps outlined above.
5-18
Sample Session
The connections between the nodes in this problem are summarized in Table 5-3.
Table 5-3: Problem Links and Devices Link L002 From S000 To J000 Devices Pipe Parameter Name Length Elevation increase Nominal Diameter Schedule Nonisothermal L003 S001 J000 Pipe Name Length Elevation increase Nominal Diameter Schedule Nonisothermal L004 S002 J001 Pipe Name Length Elevation increase Nominal Diameter Schedule Nonisothermal L005 J000 J002 Pipe Name Length Elevation increase Nominal Diameter Schedule Nonisothermal Bend Name Nominal Diameter Schedule Nonstandard Angle Radius KMUL Roughness Pipe Name Length Elevation Increase 90 2 12 0.0018 E007 500 10 E005 1000 10 8 40 Air E006 8 40 E004 1000 40 8 40 E003 100 40 8 40 Value E002 1000 40 8 40
Note: All links should have the Print option turned on in their respective device input data dialog boxes.
5-19
Table 5-3: Problem Links and Devices (cont.) Link From To Devices Parameter Nominal Diameter Schedule Nonisothermal L006 J002 D000 Pipe Name Length Elevation Increase Nominal Diameter Schedule Nonisothermal Valve Name Nominal Diameter Schedule Nominal Diameter KMUL Chisholm C2 Pipe Name Length Nominal Diameter Schedule Nonisothermal L007 J000 J001 Pipe Name Length Nominal Diameter Schedule Nonisothermal L008 J001 J002 Pipe Name Length Nominal Diameter Schedule Nonisothermal 8 40 Air E008 250 -10 8 40 Air E009 Incoming=8 40 Outgoing=8 340 1.500 E010 250 8 40 Air E011 500 8 40 Air E012 500 8 40 Air Value
Note: All links should have the Print option turned on in their respective device input data dialog boxes.
Note: With the GUI, the order of data entry has no bearing on the solution. As an alternative to the approach used above, you may opt to enter all the link connection data first followed by all the device data.
Your flowsheet should look similar to Figure 5-27.
5-20
Sample Session
Figure 5-27: Your Flowsheet
Step 9 Running the Simulation

Run the simulation by:
Clicking on the right arrow icon. A Run Simulation and View Results window appears as shown in Figure 5-28.
Figure 5-28: Run Simulation and View Results
5-21
Select the run and action type from the respective drop down lists. Click the Run button.The status of the simulation run is shown in the Run Status window. If the simulation run is successful, the same is indicated in the Run Status window. If the input data entered is wrong, during the simulation run, errors and warnings are notified in the Run Status window. The error and warning messages can be viewed in the output file.
If you have created an input file entirely using keyword entry, or if you have modified an existing keyword file, you can import the keyword file into the GUI database and run the calculations.
Step 10 Viewing the Results

The results of each node or link may be viewed graphically, or some or all of the output file may be viewed using an editor. For more details, refer to the chapter Viewing INPLANT Output in the User Guide.
5-22
Sample Session
Index
C
Compaq Visual FORTRAN (CVF) Compiler requirements Computer requirements Custom (full) installation option 2-2 2-2 2-2 3-1
N
Network installation option 3-1
O
Online documentation Operating system requirements 1-3 2-2
D
Default installation directory Disk space requirements Documentation online Help system online PDF files 3-4 2-2 1-2 1-2
S
Security FLEXlm 2-4 TOKEN 2-4 USB for Windows NT 2-4 Security FAQs downloading license security software 4-17 drive read failure 4-17 errors running Win NT 4-18 finding host IDs 4-11 FLEXlm options file 4-11 FLEXlm performance on WAN 4-12 invalid license keys 4-10 launching FLEXlm server 4-9 license file compatibility 4-12 license usage configuration 4-11 multiple FLEXlm servers 4-8 multiple license files 4-8 path access failures 4-17 restricting access to FLEXlm server 4-10 security and firewalls 4-8 security chip missing 4-18 using mixed security types 4-17 Security options selecting for INPLANT 3-2, 3-4, 3-6, 3-9 Software requirements 2-2
F
FLEXlm9.5 3-3, 3-4, 3-7, 3-9
H
Hardware requirements 2-2
I
Icons created during installation Installation 3-4, 3-10 3-1, 3-10
M
Memory requirements 2-2
VISUAL FLOW 5.2 Installation Guide
I-1
T
Technical support centers Typical (default) installation option 1-5 3-1
U
Uninstalling INPLANT User-added subroutines installation option installing Virtual Memory Requirements 3-10 3-1 3-4 1-2
I-2
Index

4.0 Getting Started Guide: Inplant

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

4.0 Getting Started Guide: Inplant

Uploaded by

Copyright:

Available Formats

INPLANT 4.

0 Getting Started Guide

INPLANT 4.0 Getting Started Guide

Contents Table of Contents

Where to Find INPLANT Documentation

Where to Find Additional Help

INPLANT 4.0 Getting Started Guide

Table 1-2: Authorized SimSci-Esscor Technical Support Centers

USA East Coast

USA West Coast

Australia and New Zealand Japan

INPLANT 4.0 Getting Started Guide

This Page Intentionally Left Blank

Chapter 2 Installation Requirements

Verifying the Package Contents

INPLANT 4.0 Getting Started Guide

Disk Space Requirements

Virtual Memory Requirement

INPLANT 4.0 Getting Started Guide

Switching Security Types

INPLANT 4.0 Getting Started Guide

This Page Intentionally Left Blank

Chapter 3 Installing INPLANT

Note: PC user-added subroutines require a custom installation.

Installing a Standalone Version

INPLANT 4.0 Getting Started Guide

For Typical installation:

INPLANT 4.0 Getting Started Guide

INPLANT Installation Directory (Typical)

INPLANT 4.0 INPLANT 4.0 Online Help Programmers File Editor

For Custom installation:

Continue the installation procedure by testing your INPLANT installation.

The following section guides you through network installation.

Installing a Network Version

INPLANT 4.0 Getting Started Guide

Install all Files onto a Network File Server (NFS)

Install Executable Files on an NFS and User Directories Locally

Install Executable Files on an NFS:

INPLANT 4.0 Getting Started Guide

Typical Directory Structure on a Network Drive

where F:\..\ is the subdirectory on your network drive.

Install User Directories Locally

INPLANT 4.0 Getting Started Guide

Accessing User-Added Subroutines (UAS)

INPLANT 4.0 Getting Started Guide

Workspace for INPLANT User-Added Routines

Build Products D_MAINONE.DLL MAINONE.EXE FFPESMainDLL.DLL

Build Sample One: Customize a Pressure Drop Model

Next you must add the file HUSER1.FOR into project:

Next you can update the code and build D_MAINONE.DLL:

Now you can verify the UAS in the build

You may also use the MAINONE_CPP project for debugging.

INPLANT 4.0 Getting Started Guide

RADD\MAKEWSP. Copy this file to the \SIMSCI\INPLANT40\BIN directory.

Build Sample Two: Customize an INPLANT Thermo Routine

Next you can update the code and build FFPESMainDLL.DLL:

INPLANT 4.0 Getting Started Guide

Now you can verify the UAS build:

Chapter 4 Installation Troubleshooting

Diagnosis of Problems with TOKEN and FLEXlm 7.2/9.5 Security

INPLANT 4.0 Getting Started Guide

Figure 4-2: LMTools Server Status