PROII Data Transfer System User Guide
PROII Data Transfer System User Guide
PROII Data Transfer System User Guide
8.0
PRO/II 8.0
Data Transfer System Users’ Guide
PRO/II 8.0 Data Transfer System Use of the PRO/II program, and its component parts and
Users’ Guide subsystems, is governed by the terms and conditions of a
separate written agreement between your employer and Invensys
Systems, Inc., its subsidiaries or affiliates..
Copyright Notice Copyright © 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.
Trademarks PRO/II and Invensys SIMSCI-ESSCOR are trademarks of
Invensys plc its subsidiaries and affiliates.
AMSIM is a trademark of DBR Schlumberger Canada Limited.
® is a trademark registered to KOCH-GLITSCH.
RATEFRAC
®
BATCHFRAC is a trademark registered to KOCH-GLITSCH.
Visual Fortran is a trademark of Intel Corporation.
Windows NT, Windows 2000, Windows XP, Windows 2003, and
MS-DOS are trademarks of Microsoft Corporation.
Adobe, Acrobat, Exchange and Reader are trademarks of Adobe
Systems, Inc.
All other products may be trademarks of their respective owners.
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.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.
Introduction
About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
About PRO/II. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii
About SIMSCI-ESSCOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii
8 Contents
CSTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-23
Plug Flow Reactor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-24
Gibbs Reactor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-25
User-Added Unit Operations. . . . . . . . . . . . . . . . . . . . . . . . . .5-25
Index ...............................................................I-1
About SIMSCI-ESSCOR
SIMSCI-ESSCOR, an operating unit of Invensys plc., is a leader in
the development and deployment of industrial process simulation
software and systems for a variety of industries, including oil and
gas exploration, petroleum refining, petrochemical and chemical
manufacturing, electrical power generation, mining, pulp and paper,
and engineering and construction. SIMSCI-ESSCOR products
enable clients to minimize capital requirements, optimize facility
performance, and maximize returns on investments in producing
assets. SIMSCI-ESSCOR supports more than 750 client companies
in more than 70 countries. For more information, visit the SIM-
SCIESSCOR Website at www.simsciesscor.com.
Technical Support
SIMSCI and its agents around the world provide technical support
and service for PRO/II. If you have any questions regarding pro-
ii Introduction
gram use or the interpretation of program output, contact your local
SIMSCI representative for advice or consultation.
When calling a Technical Support Center, be prepared to describe
your problem or the type of assistance you feel you require. Also, to
expedite your request, please observe the following before calling:
■ Have the installation CD and printed documentation available.
■ Determine the type of computer you are using.
■ Determine the amount of free disk space available on the disk
where PRO/II 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.
This chapter introduces the PDTS utility for PRO/II. In this chapter
you will:
■ Determine what PRO/II files you need when using PDTS.
■ Learn the Class, Attribute, and Item concept underlying the
PDTS utility.
■ Find out how to handle units of measure (UOM).
■ Learn how to handle simulations with multiple case studies.
What is PDTS?
The PRO/II Data Transfer System (PDTS) is a post-processing util-
ity that provides electronic access to a wide range of flowsheet data
from any completed PRO/II simulation. The data retrieved may then
be used in any other application. This manual describes how to use
this tool effectively.
Program Limits
Although a PRO/II simulation has no explicit limits on the size of
its parameters, PDTS is constrained due to the nature of the retrieval
process which uses the FORTRAN language. The standard limits
for this release are listed in Table 1-1. If the PRO/II simulation
exceeds any of these limits, a warning will be sent to the standard
output and execution will terminate. If your requirements exceed
these limits, contact your SIMSCI representative to request an
enlarged version of PDTS.
To specify the PRO/II data, the user will refer to the data as an
Attribute belonging to a particular Class and for a specified Item.
The data will then be returned to a data buffer. Class and Attribute
lists can be found in Chapter 5. The Item is the ID of the stream or
Note: In the above subroutine call, the Class, Attribute and Item
are supplied as character strings (i.e., enclosed in single quotes).
Class and Attribute strings are case sensitive. It is essential that
these strings be entered exactly as given in Chapter 5.
The fourth argument in the call above is the return Variable for the
Attribute. In the example above, data are returned in WCALC. Since
Attributes are either scalar or vectors, it is the user’s responsibility
to provide a return Variable sufficiently sized to hold the returned
value.
Note: For the subroutines PADATR, PADATI, and PADATC, the first
four arguments are identical: Class, Attribute, Item and the return
Variable.
The last four arguments in the subroutine above are integer argu-
ments KC, KU, IU, and IERR. In the order shown above, these argu-
ments are used to:
■ Determine the number of items returned.
■ Specify the Unit of Measure Group.
■ Return the Unit of Measure Class.
■ Test whether an error occurred.
All subroutine and function calls are described in detail in
Chapter 3, PDTS Subroutines and Functions.
Example:
KU = 0
CALL PADATR(‘Compressor’,‘WorkActualCalc’,‘C-1’,WCALC,KC,*
KU,IU,IERR)
Note: These routines are not required if the BASECASE is the only
case of interest.
Purpose:
To open PRO/II database files for access and to create a user-acces-
sible output file.
Note: This routine must be called before any other PDTS routine
in this system.
Arguments:
NAME Character string corresponding to the primary file
name (name) on the TITLE statement specified by
the keyword NEWFILE=name. The PRO/II database
files name.PR1, etc. must be in the current directory
when the application is executed.
SPATH Character string consisting of path to error and
support files. If these files were installed in default
location on the (same disk drive as the PDTS
application was run from), then user may enter a
blank string - ' ' ('<space>') for this argument
NFOUT The Fortran output file unit number for the default
PDTS output file. The default file name will be
name.PDS.
IRCODE Return code (non-zero indicates error
condition).
Example:
CHARACTER*8 NAME
.
.
1001 FORMAT(‘Enter File Name ’)
1002 FORMAT(A)
1003 FORMAT(‘Data Retrieved Reported for File = ’,A10)
WRITE(*, 1001)
READ(*, 1002) NAME
.
CALL PAOPEN (NAME, ‘ ’, NFOUT, IRCODE)
WRITE (NFOUT, 1003) NAME
In the above example, you are prompted to supply, through the stan-
dard input, the file name for database retrieval. Subsequent output is
written to Fortran unit NFOUT. System support and error files are
assumed in their default location. On the PC the default is the direc-
tory: \SIMSCI\PROII_W\SYSTEM\. On UNIX systems the default is
the directory: /usr/local/lib/simsci/ssilib/.
Purpose:
To return an array of CHARACTER*12 strings with the case IDs
which are available in the current PRO/II database files opened by a
previous call to PAOPEN.
Arguments:
Example:
PARAMETER (MXN = 25)
.
CHARACTER*12 NAME, CASEN (MXN)
.
.
1001 FORMAT (‘Enter File Name ’)
1002 FORMAT (A)
1003 FORMAT (‘Number Case IDs Found = ’,I5, /)
1004 FORMAT (I5, 1X,A14)
WRITE (*, 1001)
READ (*, 1002) NAME
Purpose:
To set up an individual simulation case.
Arguments:
Example:
PARAMETER (MXN = 25)
.
CHARACTER*12 NAME, CASEN (MXN), CASEX
.
.
1001 FORMAT (‘Enter File Name: ’)
1002 FORMAT (A)
1003 FORMAT (‘ Number Case IDs Found = ’,I5, /)
1004 FORMAT (I5, 1X,A14)
1005 FORMAT (‘ Enter Case ID : ’)
WRITE (*, 1001)
READ (*, 1002) NAME
.
CALL PAOPEN (NAME, ‘ ’, NFOUT, IRCODE)
CALL PACASL (MXN, KXN, CASEN, IRCODE)
WRITE (*, 1003) KXN
NXN = MIN (MXN, KXN)
DO 2001 IX = 1, NXN
WRITE (*, 1004) IX, CASEN (IX)
2001 CONTINUE
C
Purpose:
To retrieve basic flowsheet parameters and initialize the system.
This subroutine must be called before any call to retrieve other
flowsheet data items. If a case other than BASECASE is to be set up,
then this routine should be called after a call to PACASE. If the flow-
sheet case is not a converged solution, IRCODE will be equal to 1,
and an error message will be displayed to the standard output.
Arguments:
Example:
1001 FORMAT (‘Number of Components = ’, I5, /,
+ ‘Number of Streams = ’, I5, / ,
+ ‘Number of Unit Ops = ’, I5)
1002 FORMAT(‘ Solution Not Reached !! ’)
.
CALL PAOPEN ( NAME, ‘ ’, NFOUT, IRCODE)
.
CALL PACASE ( CASEX, IRCODE)
C
C Get Miscellaneous Flowsheet Data
Purpose:
To retrieve single precision floating point data from the PRO/II
flowsheet described by Class, Attribute and Item to store the
retrieved data in variable RBUF. The retrieved data item may be
either a single number or an array of values.
Arguments:
Example:
DIMENSION XNBP (MAXNOC)
CHARACTER*20 CTEMP, PAUOMS
.
.
1001 FORMAT (‘Normal Boiling Point - DEG’, A5)
1002 FORMAT (5E15.6)
.
.
KU = 7
CALL PADATR (‘COMP’, ‘NormBoilPt’, ‘ALL’, XNBP, KC, KU,
IU, IER)
CTEMP = PAUOMS ( IU, KU, IRCODE)
WRITE (NFOUT, 1001) CTEMP(1:5)
WRITE (NFOUT, 1002) (XNBP(I), I = 1, KC)
Integer Data
SUBROUTINE PADATI (CLASS, ATTRIB, ITEM, IBUF, KC, IRCODE)
Purpose:
To retrieve integer data from the PRO/II flowsheet described by
Class, Attribute and Item and to store the retrieved data in variable
IBUF. The retrieved data item may be either a single number or an
array of values.
Arguments:
Example:
1001 FORMAT (‘Number of Trays in Column T-1 = ’, I5)
CALL PADATI (‘Colu’,‘NumberOfTrays’,‘T-1’,NTRAY,KC,IER)
WRITE (NFOUT, 1001) NTRAY
Character Data
SUBROUTINE PADATC (CLASS, ATTRIB, ITEM, CBUF, KS, KC,
IRCODE)
Purpose:
To retrieve character type data from the PRO/II flowsheet described
by Class, Attribute and Item and store the retrieved data in variable
CBUF. The retrieved data item may be either a single character
string or an array of strings.
Arguments:
Example:
CHARACTER*12 UNID (MAXUOP)
.
.
CALL PADATC (‘UNIT’, ‘IDS’, ‘ALL’, UNID, KS, KC, IERR)
In this example, the unit IDs for all unit operations in the flowsheet
are retrieved into the array of character strings UNID. By reference
to Chapter 5, the user has determined that the Class for generic unit
data is ‘UNIT’ and that the Attribute to get the unit IDs is ‘IDS’. This is
an array of character strings with one member of the array for each
unit operation. Therefore, the Item requested was ‘ALL’. Variable KC
Purpose:
To retrieve a character string description for the units of measure
defined by the flags IU and KU. If the value of IU passed to the func-
tion is zero indicating a dimensionless quantity, PAUOMS will return
a blank string and the IRCODE will be equal to 1. The size of the
string retrieved by PAUOMS will not exceed 30 characters.
Arguments:
Example:
CHARACTER*30 PAUOMS, CVEL
1001 FORMAT (‘Maximum Velocity in Pipe = ’, F10.4, A30)
.
KU = 0
.
CALL PADATR (‘Pipe’, ‘CalcMaxVelocity’, ‘P-1’, VMAX, KC,
KU, IU, IERR)
CVEL = PAUOMS (IU, KU, IERR)
WRITE (NFOUT, 1001) VMAX, CVEL
In this example, the user retrieves the maximum velocity in pipe
unit P-1 by a call to PADATR. Upon return from PADATR, the value of
IU will be an integer flag corresponding to velocity units. Because
the user has set KU = 0 before the call to PADATR, the value of VMAX
is in Input units. Thus, function PAUOMS will retrieve a character
string constant with the value of VMAX.
If the velocity units on the DIME statement in the original PRO/II
keyword input file is FT/S and the velocity is 5.0, then the output to
the default output file will read:
MAXIMUM VELOCITY IN PIPE = 5.0000 FT/SEC
Purpose:
To write a line of character data to the standard output file provided
by PRO/II PDTS.
This subroutine is required only when the PDTS application is com-
piled with Intel Visual Fortran 8.0. For PDTS applications built with
Compaq Fortran 6.x, the WRITE statement can be used directly as
in previous versions.
Arguments:
Example:
CHARACTER*8 NAME
CHARACTER*133 CHARDATA
.
.
1001 FORMAT(‘Enter File Name ’)
1002 FORMAT(A)
1003 FORMAT(‘Data Retrieved Reported for File = ’,A10)
WRITE(*, 1001)
READ(*, 1002) NAME
.
CALL PAOPEN (NAME, ‘ ’, NFOUT, IRCODE)
WRITE (CHARDATA, 103) NAME
PAWRITE (NFOUT, CHARDATA)
Purpose:
This subroutine closes all database files and the default output file
opened by PAOPEN. It is recommended that this routine be called at
the end of your PDTS application.
There are no arguments.
5. Next, obtain arrays of unit type and unit description for each
individual unit. In these retrievals, the individual unit ID string
is the Item passed to PADATC. As each unit type and description
string is retrieved, it is echoed to the output file.
C GET UNIT TYPE & NAME
C
DO 1004 IX = 1, NUNIT
CALL PADATC(‘UNIT’,‘TYPE’,UID(IX),UTYPE(IX,KS,KC,IER)
C
CALL PADATC(‘UNIT’,‘NAME’,UID(IX),UNAME(IX,KS,KC,IER)
C
WRITE (NFOUT,111) IX,UID(IX),UTYPE(IX),UNAME(IX)\
1004 CONTINUE
6. The next subroutine call is to PADATC which will return the col-
umn unit name. By referring to Chapter 5, you can see that the
Class and Attribute for this retrieval are ‘UNIT’ and ‘NAME’
respectively. Because these data are required for one unit only,
the Item is UID.
C GET UNIT NAME
C
C CALL PADATC(‘UNIT’,‘NAME’,UID,UNAME,KS,KC,IER)
7. The next step is to obtain the total molar flowrate of the feed
stream 1. In these retrievals, the individual stream ID string
(defined above as stream “1”) is the Item passed to PADATC.
C GET FEED STREAM RATE
8. Then, two separate calls are made to PADATR to retrieve the col-
umn condenser and reboiler duties. To check the unit type, keep
in mind that the first four characters of the type string will
match those of the unit operation keyword for that unit type. In
each case, the Class is ‘Colu’ and the calls to subroutine PADATR
are made with the appropriate Attribute strings as given in
Chapter 5 for Column data.
C GET COLUMN CONDENSER & REBOILER DUTIES
C
CALL PADATR(‘Colu’,‘CondenserDuty’,UID,QCON(KX),KC,
+ KUOM,IDUTY,IER)
C
CALL PADATR(‘Colu’,‘ReboilerDuty’,UID,QREB(KX),KC,
+ KUOM,IUOM,IER)
C
3001 CONTINUE
4. The next two subroutine calls are to PADATC, which returns the
component IDs and column unit name. By referring to Chapter
5, you can see that the Class and Attribute for the first call are
‘COMPS’ and ‘IDS’. Because these data are required for all com-
ponents, the Item is ‘ALL’. For the second call, the Class and
Attribute are ‘UNIT’ and ‘NAME’ respectively. Because these data
are required for one unit only, the Item is UID.
C GET COMPONENT IDS
C
CALL PADATC(‘COMPS’,‘IDS’,‘ALL’,COMPID,KS,KC,IER)
C
C GET UNIT NAME
C
CALL PADATC(‘UNIT’,‘NAME’,UID,UNAME,KS,KC,IER)
6. Then, two separate calls are made to PADATR to retrieve the col-
umn tray temperature and pressure. To check the unit type,
keep in mind that the first four characters of the type string will
match those of the unit operations keyword for that unit type. In
each case the Class is ‘Colu’ and the calls to subroutine PADATR
are made with the appropriate Attribute strings as given in
Chapter 5 for Column data.
Use Item: ‘ALL’ for all component attributes (count = number of components)
Use Item: ‘ALL’ for attribute ‘IDS’ only (count = number of streams)
Item Description Variable Array/ Units Notes
Type Scalar
‘BulkMolecularWeight’ Molecular weight of bulk stream Real Scalar
‘BulkUopK’ Watson K (UOP) of bulk stream Real Scalar
‘CetanIndex’ Cetane index Real Scalar
‘CloudPt’ Cloud point Real Scalar Temperature
‘D1160Curve’ D1160 curve Real Array Temperature 1
‘D86Curve’ D86 curve Real Array Temperature 1
‘FlashPt’ Flash point Real Scalar Temperature
‘GrosHeatValue’ Gross heating value Real Scalar Energy/Vap.Vol.
‘IDS’ IDs of streams Character Array 12 Characters
‘L1Fraction’ Fraction of L1 liquid phase Real Scalar
‘L2Fraction’ Fraction of L2 liquid phase Real Scalar
‘MotOctaneNumb’ Motor octane number Real Scalar
‘NAME’ Stream name Character Scalar 40 Characters
‘NetHeatValue’ Lower or net heating value Real Scalar Energy/Vap.Vol.
‘PourPt’ Pour point Real Scalar Temperature
‘Pressure’ Stream pressure Real Scalar Pressure
‘ReidVapPres’ Reid vapor pressure Real Scalar PSI (always)
‘ResOctaneNumb’ Research octane number Real Scalar
‘SolidFraction’ Stream solid fraction Real Scalar
‘SulfurWtPerc’ Sulfur weight percent Real Scalar
‘TBPCurve’ TBP curve Real Array Temperature 1
‘Temperature’ Stream temperature Real Scalar Temperature
‘TotalComposition’ Total composition of bulk stream Real Array 2
‘TotalMolarEnthalpy’ Total molar enthalpy Real Scalar Energy/Mole
‘TotalMolarEntropy’ Total molar entropy Real Scalar Entropy/Mole
‘TotalMolarRate’ Total molar flowrate Real Scalar Mole Rate
‘TrueVapPres’ True vapor pressure Real Scalar Pressure
‘WaterFraction’ Fraction of aqueous phase Real Scalar
Liquid Phase
‘LiqApiGravity’ API gravity of liquid phase Real Scalar
‘LiqCP’ CP of liquid phase Real Scalar Molar Heat Capacity
‘LiqDensityAct’ Actual density of liquid phase Real Scalar Density
‘LiqKineVisc’ Kinematic viscosity of liquid phase Real Scalar Kinematic Viscosity
‘LiqMolarEnthalpy’ Molar enthalpy of liquid phase Real Scalar Energy/Mole
‘LiqMolarEntropy’ Molar entropy of liquid phase Real Scalar
‘LiqMolarRate’ Molar rate of liquid phase Real Scalar Mole Rate
‘LiqMolecularWeight’ Molecular weight of liquid phase Real Scalar
‘LiqSpecGravity’ Specific gravity of liquid phase Real Scalar
Notes:
1) Distillation curves of 13 points at percent distilled points: 0, 5, 10, 20, 30, 40, 50, 60,70, 80, 90, 95, 100
2) Compositions in mole fraction; Count = number of components
Unit Data
Class: ‘UNIT’
Use Item: ‘ALL’ for attribute ‘IDS’ only (count = number of unit operations)
Item Description Variable Array/ Units Notes
Type Scalar
‘FeedData’ Stream IDs for unit feeds Character Array 2
‘IDS’ IDs of units Character Array 12 Characters
‘NAME’ Name of unit Character Scalar 40 Characters
‘NumberFeeds’ Number of feed streams to unit Integer Scalar
‘NumberProducts’ Number of product streams from unit Integer Scalar
‘NumberSides’ Number of sides in unit Integer Scalar 1
‘ProdData’ Stream IDs for unit products Character Array 2
‘TYPE’ Type of unit Character Scalar 16 Characters
Notes:
1) Most unit operations are single-sided. Exchanger unit operations may be multi-sided.
2) The feed and product data variables are arrays of 12 character stream IDs.
For exchanger units of more than one side, the stream IDs will be in this order:
HX Hot Side/Cold Side
HXRIG Shell Side/Tube Side
LNGHX Hot Cells/Cold Cells
The number of feeds and products for each respective side can be obtained using the appropriate exchanger class.
Valve
Class: ‘Valve’
Expander
Class: ‘Expander’
Pipe
Class: ‘Pipe’
Phase Envelope
Class: ‘Phase’
Equilibrium Reactor
Class: ‘EquReactor’
CHARACTER*8 FNAME
CHARACTER*12 UID(MAXUOP), UTYPE(MAXUOP), CUTYPE, XID(3)
CHARACTER*40 UNAME(MAXUOP), XNAME(3)
CHARACTER*10 DNTEMP, DNPRES, DNWORK, DNDUTY, PAUOMS
DIMENSION PIN(3), TIN(3), POUT(3), TOUT(3), PRAT(3),
+ WORK(3), EFF(3), DUTY(3)
*********************************************************
100 FORMAT(/)
101 FORMAT(‘ *** PDTS EXAMPLE PROBLEM # 1 ***’,/,
+ ‘ ENTER FILE NAME: ‘)
102 FORMAT(A)
103 FORMAT(/,’ DATA RETRIEVAL FROM FILE: ‘,A15,/)
107 FORMAT(‘ NUMBER OF COMPONENTS = ‘,I5,/
+ ‘ NUMBER OF STREAMS = ‘,I5,/
+ ‘ NUMBER OF UNITS = ‘,I5,/)
110 FORMAT(/,’UNITS’,/)
111 FORMAT(I3,’ :’,A12,1X,A20,1X,A40)
112 FORMAT(/,’ COMPRESSOR TRAIN SUMMARY TABLE ‘,//,
+ ‘ UNIT ID ‘,15X,3A12,/,
+ 40X,3A12,/)
114 FORMAT(‘ INLET PRESSURE ‘,A10,3F12.4)
Subroutine FIGETU
The calling sequence is:
CALL FIGETU ( 1, LOUT)
This is a PRO/II utility that guarantees that the Fortran unit number
passed to your Fortran OPEN statement will not conflict with files
opened by the PDTS system. The FIGETU subroutine call returns the
next available Fortran unit number for input or output as integer
variable LOUT. An example code extract is shown below:
CHARACTER*8 FNAME
CHARACTER*12 FEXTRA
1001 FORMAT(‘ ENTER FILE NAME: ‘)
1002 FORMAT(A)
.
C
C GET NAME OF PRO/II DATA BASE
WRITE (*, 1001)
READ (*, 1002) FNAME
C
C USE PAOPEN TO OPEN DATABASE FILES AND FILE ‘FNAME.PDS’
CALL PAOPEN(FNAME ‘ ‘, NFOUT, IERR)
C
C GET ANOTHER FILE UNIT FOR OUTPUT
CALL FIGETU(1, LOUT)
C
C OPEN FILE ‘FNAME.PXX’ AS NEW FORMATTED SEQUENTIAL FILE
FEXTRA = FNAME // ‘PXX’
OPEN (UNIT=LOUT, FILE=FEXTRA, STATUS=’NEW’,
+ FORM=’FORMATTED’, ACCESS=’SEQUENTIAL’)
PDTS Applications
Applications which have been developed in the past using older ver-
sions of the PDTS functions will continue to work with this version
of PRO/II with minor modifications.
Users must recompile the Fortran source code and relink their
PDTS application with this version of the PRO/II libraries in order
to make them compatible with PRO/II databases generated with
PRO/II v5.5.
UAS Applications
PRO/II UAS v5.5 allows up to 25 feed and 25 product streams. The
URXINF subroutine is used to identify these streams.
Prior versions were limited to 10 feed and 10 product streams, and
the IDATA array was used for stream identification:
➤ IDATA(11)-(20) Stream IDs for feeds in same order as FEED
statement
➤ IDATA(21)-(30) Stream IDs for products in same order as
PRODUCT statement
Although this method is still valid in version 5.5 for the first 10 feed
and product streams, it is no longer recommended.
To ensure compatibility with future versions, users are encouraged
to revise their UAS code to account for this change.
A C
Attribute Case ID , 1-3
See Data retrieval Case sensitivity
Attribute lists of strings , 1-4
complete listing of , 5-1 Case study ID list subroutine
Calculator , 5-21 PACAS() , 3-3
Column/Side , 5-16
Case study option
Component data , 5-2
multiple cases , 1-6
Compressor , 5-6
Case study setup subroutine
Conversion Reactor , 5-22
PACASE() , 3-4
CSTR , 5-23
Class
Equilibrium Reactor , 5-21
See Data retrieval
Expander , 5-6
Flash , 5-5
Gibbs Reactor , 5-25
HCURVE (heating curve) , 5-19
D
HX (simple) , 5-9
HXRIG (rigorous) , 5-10 Data retrieval
LLEX (liq.-liq. extraction) , 5-18 class, attribute, item scheme , 1-3
LNGHX (liq. nat. gas HX) , 5-14 Data retrieval subroutine
Phase Envelope , 5-20 PADATC() - character , 1-3, 3-8
Pipe , 5-7 PADATI() - integer , 1-3, 3-7
Plug Flow Reactor , 5-24 PADATR() - floating point , 1-3, 1-4, 3-6
Pump , 5-7 Database close subroutine
Shortcut (column) , 5-15 PACLOS() , 3-10
Stream Data , 5-3 Database open subroutine
Unit Data , 5-4 PAOPEN , 2-3, 3-2
Valve , 5-5
F
B
FIGETU()
Building executables Example of implementation , 7-1
for PDTS , 2-2, 2-4 Flowsheet parameter retrieval subroutine
PMISC() , 3-5
Fortran compilers
Compaq Visual Fortran , 2-1
Intel Visual Fortran , 2-4
O T
OUTDIME statement , 1-5 Technical support centers , xiv
P U
PACAS() UOM Class flag - IU , 1-5
See Case study ID
UOM group specifier - KU , 1-5
PACASE()
See Case study setup UOM groups (KU) , 1-5
PACLOS UOM string retrieval subroutine
See Database close PAUOMS() , 3-9
I-2 Index