PROII81 ReleaseNotes PDF

Important: Read First
Release Notes for PRO/II 8.1

Welcome to the release of PRO/II 8.1. These Release Notes
supplement and supersede the corresponding sections in all PRO/II
8.1 documentation supplied with this release.
Contents
New Features of PRO/II 8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
New Features of PRO/II 8.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Important Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Installation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Known Defects and Constraints using SIM4ME Reports . . . . . . 10
Known Defects and Constraints using SIM4ME Portal . . . . . . . . 13
Switching Security Types for PC . . . . . . . . . . . . . . . . . . . . . . . . . 16
UAS/PDTS Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Where to Find PRO/II 8.1 Documentation . . . . . . . . . . . . . . . . . . . . 22
Printed Documentation Included with this Package . . . . . . . . . . 22
Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Summary of Defects Fixed in PRO/II 8.1 . . . . . . . . . . . . . . . . . . . . . 23
Summary of Defects Fixed in PRO/II 8.0 Patches . . . . . . . . . . . . . . 29
Summary of Open Defects in PRO/II 8.1 . . . . . . . . . . . . . . . . . . 37
License and Copyright Information . . . . . . . . . . . . . . . . . . . . . . . . . 38
PRO/II 8.1 Release Notes 1

New Features of PRO/II 8.1
The following enhancements have been made to PRO/II 8.1:
New Feature Description

SIM4ME Portal The SIM4ME Portal is an easily configured, intuitive
Graphical User Interface from within Microsoft® Excel
TDM Integrated Thermo Data Manager Application

Allow Users to Regress, Manage and Organize Component
and Binary Data
Overview of New Features

1. SIM4ME Portal
The SIM4ME Portal is an easily configured, intuitive Graphical
User Interface from within Microsoft® Excel.
2 New Features of PRO/II 8.1

Create Custom Interfaces
Perform Special Calculations

SIM4ME Portal: Product Details:
➤ Modes to launch SIM4ME® Portal
● From PRO/II toolbar/menu option

● From Start menu
➤ Creations options for a SIM4ME® Portal
● Create a new one

● Use an existing workbook, and enable Portal within it.
➤ Modes of operation
● Connected: PRO/II with ProVision concurrently open with

SIM4ME® Portal
● Stand-alone: Only SIM4ME® Portal open

● Disconnected: Reverts back to be a simple workbook
➤ Two-way Communication between PRO/II and Excel
● Read variables: PRO/II to Excel
● Write variables: Excel to PRO/II
● PRO/II Messages & Solution History: PRO/II to Excel
● Refresh command: PRO/II to Excel
● Run command: Excel to PRO/II

➤ Two GUIs from which to run a PRZ simulation
● Provision
● Microsoft Excel
➤ The SIM4ME® Portal, based on Microsoft® Excel, is intuitive
and inviting for the simulation novice to use
➤ Focus on “Simplicity”; “Ease of Use”; “Stability”
➤ Portal will allow companies to maximize their return on the
expertise invested in their process models
4 New Features of PRO/II 8.1

2. Thermodynamic Data Manager (TDM )
➤ Pure Component Data Regression
● Temperature-dependent thermo-physical property data can

be fitted to any appropriate equation form
● Recognized properties (generally at saturation conditions)
are : Vapor Pressure, Ideal Gas Enthalpy, Liquid and Solid
Enthalpy, Latent Heat of Vaporization, Liquid and Solid
Density, Liquid and Vapor Viscosity, Liquid and Vapor
Thermal Conductivity, Surface Tension
● Equation Of State “alpha” terms can be fitted to pure
component vapor pressure data
➤ Mixture Data Regression
● Binary and multi-component data can be regressed

● Recognized properties are: Equilibrium (VLE and LLE),
Excess Enthalpy, Excess Volume and Activity Coefficients
● Multiple types of equilibrium data – binary and higher order,

VLE and LLE can be regressed to a single, consistent ther-
modynamic model (e.g. NRTL or SRK)
➤ Basic Concepts
Regression is activated from the main TDM screen
● A regression run consists of a number of “Cases”
● Each Case contains a set of:
Components
Multiple Data Sets
Multiple Calc Options
Multiple Scenarios

Important Notices
Compatibility with Earlier Versions of PRO/II
PRO/II 4.1x, PRO/II 5.0x, PRO/II 5.1x, 5.5x, 5.6x, 6.0x, 7.x and 8.0x
database files will automatically be converted into PRO/II 8.1 files as
they are opened. The original file will be saved using an alternate file
name.
Default changes in PRO/II v8.0:

1. The databank search hierarchy has been changed from (Process,
SimSci) to (SimSci, Process). In general the SimSci databank
has more advanced data and should be used for all new
simulations. If it is necessary to revert back to the Process
databank, that can be done either on a simulation-by-simulation
basis, or the default can be changed globally for all simulations
on that PRO/II installation. To change the installation default,
select the menu item Options/Simulation Defaults…/Component
Databank… This change is saved in the \user\proii.ini file.
2. The Assay curve fitting option default has been changed from
“Version 6” to “Version 7”. This affects how a stream TBP curve
6 Important Notices
that is constructed from volume percent of component cuts is
interpolated and extrapolated. The Version 7 method corrects
some problems that were present in the existing simulation.
Most simulations will change very slightly or not at all because
of this change. The most obvious change will occur for assay
results that use the IP (usually 1 vol %) or EP (usually 98 vol %)
as specifications. This was first offered in PRO/II v7.0 as the
“Alternate” option, and made the default in v8.0. If it is
necessary to revert back to the Version 6 method, that can either
be done on a simulation by simulation basis, or the default can
be changed globally for all simulations on that PRO/II
installation. To change the installation default, select the menu
item Options/Simulation Defaults…/Assay Characterization…
This change is saved in the \user\proii.ini file.
3. PRO/II tube side pressure drop, clean, service transfer rates and
roughness correlation have been updated to match HEXTRAN®.
4. There are two new heat exchanger defaults:
➤ Two Phase Heat Transfer Coefficient Method
You may select the method to calculate the two-phase heat
transfer coefficient. Following are the available options to be
selected from drop-down list.
● Chen - Modified Chen Vaporization method (NEW DEFAULT)

● HEX5 - Algorithm used in versions 7.1x and earlier
➤ Tubeside Pressure Drop Method
You may select the method to be used to calculate the tube side
pressure drop. The options are:
● "BBM" for the Beggs-Brill-Moody method (NEW DEFAULT)

● "HEX5" for the method used in versions 7.1x and earlier
PRO/II 8.0 Patch 1 addressed the concerns of some customers that
users may run the risk of inadvertently running simulations defined
by keywords using the new defaults on files that have been validated
using the old defaults. The following changes have been made:
1. When a file is run from keywords, either via the menu item File/
Run Batch..., or from the DOS command line RUNP2 filename,
the keyword file must explicitly state the component search hier-
archy. Failure to do so will result in an input error message that
details the required correction:

*** ERROR *** Starting with version 8.0.1, PRO/II keyword
files must specify the databank search hierarchy on the LIBID
statement. To match the current GUI default specify the order as
BANK = SIMSCI, PROCESS. To match simulations before version
8.0 using the default order specify BANK=PROCESS, SIMSCI.
2. When a file from keywords, either via the menu item File/Run
Batch..., or from the DOS command line RUNP2 filename, and
assays are being used in the simulation, the keyword file must
explicitly state the TBP curve fitting method. Failure to do so will
result in an input error message *** ERROR *** Starting with
version 8.0.1, PRO/II keyword files must specify the curve fitting
option on the ASSAY statement for calculated distillation points.
To match the current GUI default specify the fit as ASSAY CUR-
VEFIT=IMPR. To match simulations before version 8.0 using the
default fit specify ASSAY CURVEFIT=VER6.
3. When importing a file that lacks one or both of these selections,
PRO/II will display a message box requiring the user to make an
explicit selection.
4. On file export, PRO/II will write the selections explicitly into the
keyword file even if the defaults were selected.
5. When opening files created in earlier versions of PRO/II, PRO/II
will display a message box allowing the user a choice to accept
whatever selections were previously made for consistency with
that version, or to change to the newer, improved methods.
6. With v8.0.3, the AMSIM add-on for simulation of amine sweet-
ening has been upgraded to AMSIM v7.3 with the following new
features:
a. Activated Amine - Piperazine + MDEA (~5 wt% + ~40 wt%)
Activated MDEA can be used wherever acid gases, such as
carbon dioxide, hydrogen sulfide, carbonyl sulfide, or mercap-
tans, need to be removed to allow product gases to be pro-
cessed properly, or to meet purchasers' specifications. Typical
applications for the technology are ammonia synthesis gas
plants and hydrogen/oxo synthesis gas plants as well as natu-
ral gas plants for sales gas, or LNG. Other applications include
use in iron ore reduction units, ethane sweetening, and pro-
pane dehydration. Today, more than 200 aMDEA plants are
either in operation, or under construction, worldwide.
8 Important Notices
b. The calculations of the Approach to Equilibrium.
The approach to equilibrium method is normally used by

design engineers in determining the lean amine circulation
rate. It is based on the premise that the theoretical maximum
rich solution loading is represented by equilibrium with the
feed gas at absorber bottom conditions. Since this theoretical
maximum cannot be attained in practical equipment, it is cus-
tomary to assume that an approach of 75-80% will be
attained. This approach can be considered in terms of either a
rich solution with an acid gas vapor pressure 75-80% of the
acid gas partial pressure in the feed gas, or a rich solution
with an acid gas loading 75-80% of the loading in equilibrium
with the feed gas. A. Kohl and R. Nielsen, Gas Purification,
5th Edition, Gulf Publishing Company, 1997.
The results are represented by partial pressure.
7. This update also includes an updated utility to send .xml files

created by the PRO/II column modules to KG-TOWER(R) 3.1.
Licenses for previous versions of KG-TOWER will expire on Jan
31, 2007 and will no longer be available so this update will be
required when using KG-TOWER. The Koch-Glitsch methods
within the PRO/II column modules will still be the earlier meth-
ods with this update. However, an update will be available on
shortly on our download site that will bring those calculations in
sync with KG-TOWER 3.1.
Installation Notes
Note: Before executing any of the installation programs, disable all
antivirus software running on your computer.
1. If OLI Chemistry Wizard is already installed with PRO/II v7.1,
then the same can not be reinstalled along with PRO/II v.8.1. It
can be found in Programs/OLI Systems/Alliance Suites/ProII 7.x
in the startup menu. If Chemistry Wizard is not installed along
with v7.1, then the same gets installed along with v8.1. It can be
found in Programs/Simsci/ProII81/OLI in the startup menu. To
use the OLI Chemistry Wizard installed along Pro/II v7.1, user
has to change the working directory path of Chemistry Wizard to
v8.0 User directory to automatically copy the related files to v8.0
User directory.
2. Hysis™ Translator is not supported on Network Install.

3. In order for PRU to work properly in the Network/ Newuser
install, the Newuser must be installeed from a mapped network
drive.
4. For a Network Install on a Windwos® XP® SP2 or Windows
2K3 Server, read/write permission should be set for all groups of
users. Failure to do that may result in the PRU not working
properly..
Important information for uninstalling previous versions of

PRO/II
5. Uninstalling PRO/II 7.1 will disable the HYSYS® Translator in
PRO/II 8.0 and 8.1 if they are installed on the same machine.
During the PRO/II 7.1 uninstall process, the "Simulation Sci-
ences\PROII key is completely removed. The workaround is to
export the "HKEY_LOCAL_MACHINES\Softwares\Simulation Sci-
ences" keys to a .reg file, and then re-import the file after com-
pleting the uninstall. This issue has been addressed as starting
with PROII 8.0 so uninstalling PROII 8.0 or PROII 8.1 will not
affect other versions of PRO/II.
6. Uninstalling PRO/II 7.1 will disable Visual flow 5.x. During the
PRO/II 7.1 uninstall process, the "Simulation Sciences\PROII key
is completely removed. The workaround is to export the
"HKEY_LOCAL_MACHINES\Softwares\Simulation Sciences" keys
to a .reg file, and then re-import the file after completing the
uninstall. This issue has been addressed as starting with PROII
8.0 so uninstalling PROII 8.0 or PROII 8.1 will not affect installed
versions of Visual flow.
Known Defects and Constraints using SIM4ME Reports

The following is a List of Known Defects and Constraints in using
SIM4ME Reports.
1. Sometimes it seems that the last item selected (during multiple
selects) is missing after a drag and drop operation. The
observed behavior is a limitation in the current implementation.
The "CONTROL" or "SHIFT" button needs to be held down until
the drag-drop operation is completed. Also, "two consecutive
clicks" un-checks the last item. After performing a multiple drag
and drop operations, the user should check that all the desired
objects are highlighted in the Flowsheet Explorer. If anything is
not highlighted, it will be copied with the rest of the selected
objects. This happens most often when the user selects the last
10 Important Notices
object once and then again clicks it to drag and drop. The second
click un-checks the last item. What the user should do is select
the last item and directly drag them all without another click.
2. Can I search for a stream "CRUDE" or a Unit Operation
"PREHEATER" on the Flowsheet Explorer? Yes. In this case, go to
"streams" and expand it. Now select "Streams" and type in the
first few letters of the string you want to search "CRU". You will
be navigated to the first match. Note that you need to expand
"Streams" or "Unitops" to use the search functionality.
3. Why is it that I get "MISSING" values even when I uncheck "Show
Missing Values" in the Report Manager settings? The option
"Excel Comparison Report" may be "ON". In this option, the
software just looks at the entire list of attributes and ignores the
"Show Missing Values" check box.
4. I have selected "Excel Comparison Report" but Columns are not
being compared. Why? Only unit operations that lend
themselves to comparison are allowed in the "compare mode".
For example, Streams/Flashes/HXs/Pumps/Expanders/
Compressors have unchanging formats and can be compared
side by side. Columns, Reactors, Controllers, etc. cannot be
compared because of variations in report formats for individual
units.
5. Energy UOMs in the PRO/II output report are reported as "MM
BTU/hr" but the prefix "MM" is not used in SIM4ME reports.
Why? The prefixes such as "MM" for millions when English units
are selected, are not available. These prefixes may be included
at a later date.
6. I dragged and dropped an attribute onto a particular row but it is
added to the bottom. Why? Location specific attribute addition is
not supported in this version of SIM4ME reports. It gets
appended to the bottom of the Report pane only.
7. When I add/delete any attribute to a summary report, why does
the name of the report change automatically? "Summary" and
"Detailed" reports are standard, pre-configured reports. Once
you start to customize these reports, the saved name is changed
to avoid overwriting these reports. For example; If the user starts
with a "Summary Report" and then adds a unit operation, it gets
renamed to "Summary ReportAdd1" to indicate that the report is
based on the "Summary Report" with added objects.

8. Sometimes I do not see "Transport Properties" or "Refinery
Inspection Properties" in my Excel reports. Why? "Transport
Properties" and "Refinery Properties" must be selected in the
PRO/II thermodynamics set for these values to be available in
SIM4ME reports.
9. Sometimes I do not see Tray Hydraulics data when I drag and
drop them onto the reports. Why? There are three options under
"Perform Tray Sizing Calculations" in PRO/II Column. The first
option "At output time" is the default. In this case, PRO/II
updates these data only when the text output report is generated.
If you generate SIM4ME reports before generating the text
report, these data will not be available. If you generate the text
report first, these data will become available and will be included
in SIM4ME reports. You could also select either the second or
third options under "Perform Tray Sizing Calculations" which will
cause tray hydraulics calculations to be executed during the Run
operation, in which case the data will be available to SIM4ME
reports before creating the report.
10. In PRO/II output options; I have selected the option "Two
reports, one in Input UOM, one in Output UOM". But, I do not see
both UOM Slates in SIM4ME reports. Why? At this point, only
the PRO/II Output slate is supported in SIM4ME Reports. You
can manually select the desired SIM4ME UOM Slate under
Reports Settings, Current UOM Slate.
11. Why don't my reports save the UOM information? I opened
"Summary" report and changed the UOM Slate to "SI". I closed
and re-opened the flowsheet to see that the UOM Slate has
changed to PRO/II Output Slate. Why? The UOM Slate settings
provide an option to temporarily override the UOM slate for the
current reports only. These are temporary UOM overrides - they
are not stored at this point. Once the report is closed and re-
opened, the PRO/II Output UOM Slate is assumed. However, if
you need some attributes always in a particular UOM slate
irrespective of what slate is selected currently in PRO/II , you
should define a new “view” by dragging and dropping the
individual attributes. The name of the view will by default appear
as Unitop_1 etc. These custom views also save the UOM. You
might want to rename the view to “Unitop_SI” etc.
12. I tried to drag and drop individual elements of vectors. I see that
the entire vector is dragged and dropped. Why? Drag and drop
of individual elements is not yet supported in SIM4ME reports.
Also, any operations like "Move Up, Move Down, Delete, and
Format Cell" etc. do not work on individual elements of vectors.
These will be addressed in future versions.
13. How do I generate formatted reports, e.g., TEMA reports, using
SIM4ME reports? Formatted reports are not supported yet. They
will be implemented in future versions of SIM4ME reports.
14. The Excel report generated using SIM4ME reports looks
different from Tools->Spreadsheet. Why? Which one should I
use? The SIM4ME reports is a new reporting tool that gives the
user the flexibility of configuring the units and parameters that
show up in the report whereas the spreadsheet option generates
pre-defined reports. User can use either one based on their
needs.
15. What happens when I import a report in a different simulation?
You could import a report exported from "a1.prz" to "a2.prz". In
this case, the units with same name and class in both files will be
displayed. All the views in the imported file will be available for
the simulation as local views.
16. If I have a custom view with the same name as global view which
one takes precedence? The custom (local) view will take
precedence.
17. Why is it that I see numbers displayed too many places after the
decimal point? Is there a way to control the number of digits? In
the current version, this is a limitation. You need to use the Excel
features to control the display in the cells.
Known Defects and Constraints using SIM4ME Portal

The following is a List of Known Defects and Constraints in using
SIM4ME Portal.
1. There is no Horizontal Scroll bar implemented in flowsheet
explorer. Very large captioned UnitOPs and Streams and their
attributes may not be visible properly.
2. Can I search for a stream "CRUDE" or a Unit Operation
"PREHEATER" or an attribute "TEMPERATURE" on the Flow sheet
Explorer? Yes. In this case, type in the first few letters of the
string in the "Filter" search box placed on the FS explorer. You
will get the filtered results in the FS explorer. Note that you need
to expand all the nodes of the FS explorer to see the filtered
results.

3. Multiple drag-drop of various groups and/or various attributes is
not supported. Currently you need to drag drop individual items
one by one onto the spreadsheet from FS explorer.
4. While dragging and dropping a vector onto the spreadsheet, you
cannot select individual elements of the vector. Current version
of SIM4ME Portal allows only drag drop of complete vector.
5. Normal Excel functionalities like Cut, Copy and Paste are not
supported. If you perform "Cut", "Copy" and "Paste" operation on
any of the cells, you will be given a proper message that "This
operation is not supported." If you perform these operations
using short cut keyboard keys like "Ctrl+x", "Ctrl+c" and "Ctrl+v",
then you won't be given such messages and you may see that
UOM control is left behind at original cell. It is advised not to use
Cut, Copy and Paste functionalities in this version.
6. Energy UOMs in the PRO/II output report are reported as "MM
BTU/hr" but the prefix "MM" is not used in SIM4ME Portal. Why?
The prefixes such as "MM" for millions are available there in
UOM conversion window which pops up when you click on UOM
control and select "Millions" from the dropdown list and click on
Convert Value.
7. I dragged and dropped a vector attribute onto an empty cell just
below scalar attribute but it is giving me the message "Existing
parameter reference would be overwritten…" Why? The vector
attribute requires two cells above the location of dropping to
place the vector heading and vector UOM. Since you have
dropped just one cell below the scalar attribute, this message is
thrown. Please drop the vector two cells below scalar.
8. In PRO/II output options, I have selected the option "Two
reports, one in Input UOM, one in Output UOM". But, I always
see the values shown in Output Slate in SIM4ME Portal. Why? At
this point, by default only the PRO/II Output slate is supported in
SIM4ME Portal.
9. For the UnitOPs like Column, Controller, MVC, Splitter, etc. the
performance specifications are shown without their long
descriptions and UOM.
10. When SIM4ME Portal is launched from standalone mode to any
PRO/II file, you will not be able to launch the same PRO/II file
using PRO/II. You will get Visual FORTRAN Error message. We
are working on this and it should be available in the next version.
11. When a Portal file is emailed from one PC to another PC, you
should not just double click the portal file. You should first save
this Portal file in a particular location on your PC. You should
then start Portal in standalone mode using this portal file and
direct it to the PRO/II file that it is trying to connect. Double
clicking the emailed portal file would fail to connect to
simulation.
12. If any Pop Up window comes over UOM control, then UOM
control formatting gets shadowed by the image. To restore the
UOM control, just hover the mouse over the damaged UOM
control.
13. What Operating System specifications do I need to have on my
machine before installing Sim4Me Portal? Sim4Me Portal is
supported on Win 2000, Win 2003 & Win XP. Microsoft Excel
2003 Professional with SP2 is required.
14. Is there any sample Portal file to get user started? If yes, how to
use the sample file? Yes. There are two Sample Portal files
placed in SIMSCI\PROII81\Applib folder namely
G5_Expander_Plant.xls and G2_Deethanizer.xls. While opening
these two files for the first time, please do not just Double click
them, otherwise it will throw some exception. If you want to view
these two files, there are three options:-
(a) Start PRO/II 8.1 application, Open the sample file, say
G5_Expander_plant.prz, Click on Sim4Me Portal Launch and
browse for the sample file G5_Expander_Plant.xls.
(b) Start Sim4Me Portal application in stand alone mode, open

the G5_Expander_Plant.xls.
(c) Execute the batch file “PortalApplibs.bat” placed in C:\SIM-

SCI\Proii81\User. Before executing the batch file, please ensure
that the Tools>Macro>security setting in Excel is Medium.
After following any of the above three options, you should be

able to use the sample files without any issues. The next time if
you want to open the sample file, you can just double click the
Excel file to view the sample Portal file.
15. Is there any security setting that we need to set in Excel in order
to run Portal? Yes.

(a) It does not work with security setting “Very High”. It can be
changed from Excel>Tools>Macro>security>Security Level set-
ting in Excel.
(b) Also, in Excel>Tools>Macro>security>Trusted Publishers,
check the option “Trust access to Visual basic Project”.
Switching Security Types for PC

PRO/II 8.1 provides the following security options:
■ USB Single User Security for PRO/II with PROVISION, PRO/II
Keyword, and add-ons.
■ FLEXlm Security for PRO/II with PROVISION with security for
add-ons.
■ TOKEN Security for PRO/II with PROVISION with security for
add-ons.
The security option used is normally chosen during the install
procedure. If you want to switch to a different security method after
installation, use the following procedures.
To switch to USB security:

■ Open the proii.ini file found in the user directory.
■ Find the section entitled [wss_Security] and set Type=USB.
■ Save the file and exit.
To switch to FLEXlm security:
■ Find the section entitled [wss_Security] and set the “Type=”
keyword to one of the following values
Type=FLXLM72 For FLEXlm version 7.2
Type=FLXLM95 For FLEXlm version 9.5

■ The version selected must match the version of the FLEXlm
server that is used on your network. Please confirm with your
system administrator the specific version of FLEXlm in use.
■ If you are running under Windows 2000/XP, add the
IPASSI_LICENSE_FILE={FLXLM server host name} environment
variable to your control panel/system/environment settings.
■ Reboot your computer so the changes to your security
environment will be correctly configured.
To switch to TOKEN security:
■ Find the section entitled [wss_Security] and set Type=TOKEN.
■ If you are running under Windows 2000/XP, add the
IPASSI_LICENSE_FILE={FLXLM server host name} environment
variable to your control panel/system/environment settings.
■ Reboot your computer so the changes to your security
environment will be correctly configured.

UAS/PDTS Capabilities
PRO/II 8.1 users using the User-Added Subroutine (UAS) or PRO/II
Data Transfer System (PDTS) capabilities can compile and link their
code using one of the following two compilers:
■ Compaq Visual FORTRAN (version 6.1 through 6.6b)
■ Intel® Visual FORTRAN version 8.0 for Windows (Standard or
Professional Edition)
If you are using Compaq Visual FORTRAN 6.x:
The Visual Studio Workspace for the example PDTS applications are
located at:
C:\SIMSCI\Proii81\User\Pdts\Examples\VF6
The Visual Studio Workspace for the example UAS is located at:
C:\SIMSCI\Proii81\User\Uas\Examples\VF6
This assumes that you have installed to “C:\SIMSCI\Proii81”.
We strongly recommend that you take advantage of the free

upgrades available from HP/Compaq to bring your complier up to
6.6b. Compaq Visual FORTRAN patches are available at http://
h18009.www1.hp.com/fortran/visual/updates.html.
Depending on the options selected when you installed Compaq

Visual FORTRAN 6.6b, you may not have oldnames.lib installed on
your computer. This library is required to build PDTS applications
and is located on the Compaq Visual FORTRAN CD in the
\X86\SUPPORT\LIB directory. If you do not have this library, copy it
into your Compaq Visual FORTRAN library directory before building
PDTS applications.
If you are using Intel FORTRAN 8.0:
The Visual Studio Solution files for the example PDTS applications
are located at:
C:\SIMSCI\Proii81\User\Pdts\Examples\IF8
The Visual Studio Solution file for the example UAS is located at:
C:\SIMSCI\Proii81\User\Uas\Examples\IF8
This assumes that you have installed to “C:\SIMSCI\Proii81”.
Source code changes required for Intel FORTRAN 8.0:
PRO/II 8.1 is built with Compaq FORTRAN 6.6b. If you build UAS or
PDTS applications using Intel FORTRAN 8.0, please note that
FORTRAN unit numbers cannot be shared by two different compilers.
For example, if a file is opened by Compaq FORTRAN 6.x using
FORTRAN unit number 10 and that number is passed to a PDTS or
UAS subroutine compiled using Intel FORTRAN 8.0, then a READ or
WRITE statement using FORTRAN unit 10 will not work because
Compaq FORTRAN 6.x and Intel FORTRAN 8.0 use different internal
runtime data structures.
There are two cases when PRO/II opens an output file and passes the
associated FORTRAN unit number to your PDTS or UAS code:
PDTS application: the NFOUT argument of the PAOPEN()
subroutine
User-Added Subroutine: IDATA(6) of the USERnn subroutine
In both of these cases, PRO/II calls the FORTRAN OPEN statement to

open a file and passes the unit number to your PDTS application or
UAS. For applications built using Intel FORTRAN 8.0, you cannot
directly use this FORTRAN unit number in a WRITE statement.
Instead, the utility subroutine PAWRITE has been provided to allow
your application to write output to the file. The following code
fragments illustrate the required changes:
Original PDTS 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
PDTS example modified for Intel FORTRAN interoperation with

Compaq FORTRAN:
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)
Note that the modified code does not directly write the output to the
FORTRAN unit number NFOUT. Instead, it writes the output to a
character variable then calls the utility subroutine PAWRITE() which
tells PRO/II to write the contents of the character variable CHARDATA
to FORTRAN unit number NFOUT.
Original UAS example:

SUBROUTINE
USER42(IPARM,RPARM,SUPPLE,HEAT,IDATA,ISOLVE,ISTOP)
.
.
CHARACTER*12 CID
1001 FORMAT(' ERROR !! FEED STREAM ',A12,' IS
MISSING').
.
.
IOUT = IDATA(6)
C
C RETRIEVE FEED STREAM
C
CALL URXINF('FEED',1,CID,CNAME,IERR)
IF (IERR. NE. 0) THEN
IPARM(2) = 1
WRITE(IOUT,1001) CID
ISOLVE = 1
ISTOP = 1
GO TO 9999
ENDIF
UAS example modified for Intel FORTRAN interoperation with

Compaq FORTRAN:
SUBROUTINE
USER42(IPARM,RPARM,SUPPLE,HEAT,IDATA,ISOLVE,ISTOP)
.
.
CHARACTER*12 CID
CHARACTER*133 CHARDATA
1001 FORMAT(' ERROR !! FEED STREAM ',A12,' IS
MISSING').
.
.
IOUT = IDATA(6)
C
C RETRIEVE FEED STREAM
C
CALL URXINF('FEED',1,CID,CNAME,IERR)
IF (IERR. NE. 0) THEN
IPARM(2) = 1
WRITE (CHARDATA, 1001) CID
PAWRITE (IOUT, CHARDATA)
ISOLVE = 1
ISTOP = 1
GO TO 9999
ENDIF
Running PDTS Applications

Note: If you call the subroutine FIGETU to get a FORTRAN unit
number and then call OPEN() in your own PDTS or UAS code,
you do not need to make any code changes to the READ or
WRITE statements because both the OPEN and the WRITE (or
READ) is being done within code compiled by the same compiler.
If you execute a PDTS application, you may get the following

message:
The dynamic link library PESCalcMain.dll could not be found in
the specified path
In order to run PDTS applications, it is necessary to add additional

directories to the sysytem PATH so that the PDTS application can
locate PESCalcMain.dll and the other required DLLs.
This can be done by executing the batch file setPDTS.bat which is

located in the “user” directory. The PATH wil be modified for the
current Command Prompt session and you will be able to run the
PDTS application in that Command Prompt session.
If you start a second Command Prompt session, then you will need
to execute the setPDTS.bat batch file in that second session.
It is *not* recommended to change the system PATH in the Control

Panel, because such a change may impact other installed
applications.
It is not necessary to execute setPDTS.bat to run the PRO/II GUI or
any of the installed batch files such as “runp2.bat”.

Where to Find PRO/II 8.1 Documentation
Printed Documentation Included with this Package
■ Release Notes for PRO/II 8.1 (this document)
■ PES Installation Guide
■ PES Tutorial Guide
Online Documentation
■ PRO/II User Guide
■ PRO/II Keyword Manual
■ PRO/II Reference Manual
■ PRO/II Getting Started Guide
■ PRO/II Quick Reference Card
■ PRO/II Casebooks
■ PRO/II Application Briefs Manual
■ PRO/II LIBMGR and COMPS User’s Guide
■ Data Transfer System User’s Guide
■ User-Added Subroutines User’s Guide
■ PRO/II Add-On Modules User’s Guide
■ PRO/II Interface Modules User’s Guide
■ SIMSCI Component and Thermodynamic Data Input Manual
■ PRO/II COM Server Reference Guide
■ PRO/II COM Server Programmer’s Guide and Tutorial
Note: The PRO/II Welcome screen for the online documentation

can be found on the hard drive under the simsci\proii81\Manuals
directory.
22 Where to Find PRO/II 8.1 Documentation

Summary of Defects Fixed in PRO/II 8.1
Feature Description
ACE The numeric value of pressure drop in the ACE output is in kPa
when the labeled units are kg/cm2.
Assay Curve fitting of D2887 before conversion to TBP is not as
smooth as it should be. Curves with large delta T's in excess of
API recommended limits could have significant deviations from a
smoothly fitting curve. This deviation will not be obvious without
a large number of components to track the vol%/TBP
distribution of components.
Assay Multiple ASSAY statements, legal since they contain different
data, result in an error message that there is an illegal METHOD
statement on import.
Assay Changing the curve fitting method from cubic spline to pdf or
quadratic causes strange error messages to pop up for a merged
IO column with sidestripper. There is nothing wrong with the
column. Once it's in a bad mode it can't recover.
Assay User supplied recycle stream estimates get wiped out when
assays are recalculated. These estimates need to be retained for
flowsheet solution efficiency, and in some cases for simply
achieving a flowsheet solution.
Batch Only instantaneous draws may be taken from the accumulator of
Distillation the batch still. Instantaneous or continuous draws may be taken
from any location except the accumulator.
Batch Some of the Batch Distillation fixed rate side-draw streams may
Distillation be reported to have n/a flow rates when they are actually a
positive value.
Batch Weight feed rate reported in Batch Distillation output report is
Distillation wrong. Mole rate is OK.
BatchFrac Weight feed rate reported in Batch Distillation output report is
wrong. Mole rate is OK.
Blending The blending reports an incorrect warning message that the feed
Report and product stream have a different thermo set. However, this is
a requirement for proper working of the blending unit.
Calculator The Calculator WRITE statement is unable to print out special
variables such as MAXC.
Case Study If you set the rate (or temperature, etc.) of a stream as using the
parameter statement on the Case Study feature, and that stream
is also a product from a unit operation, you get a warning but
PRO/II will still run. The results appear to show that the stream
rate has not been varied. This should be flagged as an error
condition.
Column Column with thermosiphon reboiler w-baffles will converge on
first pass. Hit run again and it fails to converge. Seems to be
related to the algorithm deciding to make reboiler sump
subcooled.

Feature Description
Column In some cases, Ratefrac runs considerably slower in v8.0
compared to v7.1.
Column A VLLE Chemdist column that refers to the feed stream in one of
the specifications fails, but if it refers to a clone of the feed it
solves. Since the feed stream isn't varied the specification
should be valid..
Column When Ratefrac has a pumparound specified in mass or volume
basis, the column may "solve" with a substantial heat imbalance.
Column Sure columns may fail using Simsci/Process databank order
because of a mix of VL/VLS capable components. In one
example, with Process/Simsci order the Sure columns solves.
With Simsci/Process, it fails. Change all the components to VL
components and the Simsci/Process order works.
Column A warning message about the column hydraulic calculation
encountering a mechanical restriction can occur even when the
column minimum diameter set to avoid these mechanical
restrictions.
Column The value of the condenser temperature shown in the column
unit operation property table may be wrong when the condenser
is not heater/cooler #1.
Column Making a column specification with homotopy associated with it
inactive causes an *** ABORT *** ENTRY NUMBER NEGATIVE
OR ZERO error when you run the file.
Column "CONDENSER" is accepted as a pumparound name - this leads to
errors if a real condenser is present since the term
"CONDENSER" is reserved for real condensers. This problem is
compounded because PROVISION would automatically name all
duties "CONDENSER" if they appeared on tray 1, even if it were
just a pumparound.
Column Run/save/change repeated several times may result in a file size
bloat in liquid-liquid distillation columns.
Column Incorrect error messages occur during packing hydraulic
calculations in the column when the flowsheet is changed after
being interrupted during run. Similar to:
*** ERROR *** (MERGED COLUMN) UNIT 29, 'C-301', 'Frctntr'
- PACK statement 2 - IMTP #25 Random Packing. Size is
Required. If you allow the run to come to completion and then
make your changes, the error message does not occur.
Column Tools\Spreadsheet\Distillation doesn't work for side-strippers in
merged columns.
Component A few components in the SimSci databank (for example
triethylphosphate) are missing phase designation (VLS or VL).
This results in an error message requiring the user to supply a
phase designation.
Component Triethylphosphate does not have H(ideal) or H(liquid) in the
SIMSCI databank.
24 Summary of Defects Fixed in PRO/II 8.1

Feature Description
Component The SIMSCI databank doesn't have UNIFAC structure data for
NH3.
Component On file import, the checking component task takes about seven
times longer to accomplish in v8.0 compared with v7.1. This
becomes noticeable for simulations with a large number of
components (>100).
Component A file with a large number of components, several thermo
systems, one of which includes Lee-Kessler densities, bloats by
94kb on each cycle of Restore Input Data/Save.
Component The Gross Heating Value and Lower Heating Value may be
displayed as "missing" in the Component Properties/
Miscellaneous data entry window even though those values are
available.
Component If multiple thermo sets are present and the flowsheet contains
assay streams, when a new component is added the stream
compositions are shifted so that the new component takes on
the flow value of the first pseudocomponent.
Data Review The Data Review Window converts UOMs based on the number
Window on the display number, not on the actual number. Sequential
conversions to different UOM could result in values very much in
error.
Depressuring Selecting the calculation time step for a Depressuring unit
causes the program to go through an infinite loop. The message
window shows that the time step is being decreased to extremely
small values.
Depressuring Changing Depressuring Unit composition printout options via
GUI does not cause the actual printout to change. It works OK via
keywords and following file import.
Depressuring Range checking is incorrect for the liquid height of a
depressuring vertical cylinder.
File File/Save on a newly created file may fail. This works most of the
time, but occasionally when you create a new file, work on it,
then do a save, the resulting .prz file is empty.
Flash The deletion of the stream attached to the flash is sometimes not
reflected in the Flash Product Phases data entry window.
Flash In one case, PRO/II identified the products of a LLE separation as
VLE. This may occur when there is hydrogen in the system.
Flash In one particular file, the SRKS thermo method resulted in very
slow convergence of flashes. Switching to SRKM fixed the
problem.
HX HX with hot temp specification and a UAMax override displays
the outlet temp as the hot temp spec even though the UAMax
override kicked in and the resulting temperature is different from
the hot temperature specification. The View Results and Unit Op
Property Table are both wrong.

Feature Description
HXRIG The number of baffles calculated for H type exchangers is
incorrect. This results in a high pressure drop and does not
match HEXTRAN or HTRI calculations.
HXRIG The Rigorous Heat Exchanger using the new Chen correlations
may calculate an incorrect heat flux calculation when there is
more than one shell in series.
HXRIG The tube side pressure drop with HEX5 method is reporting only
vapor pressure drop. The weighted average of liquid and vapor
pressure drops should be reported.
HXRIG In one case, there is a large shell side delta P difference when
using Hex5 vs Chen HTC for BFU type exchanger even when
outlet temp is specified, or when duty is specified. Once the duty
of the HX is fixed, the pressure drop calculation should be
decoupled from the HTC method so these two cases should be
the same. Other types of exchangers such as AES show no
difference as expected.
HXRIG/HTRI When a file with HXRIG pointing to an .htri file is imported and
then closed, the external .htri file disappears from the directory
and only lives within the .prz file.
HXRIG/HTRI Using an external .htri file not in the working directory doesn't
work. Pointing to a file in the current working directory works
OK.
HXRIG/HTRI Designation of Tubeside=hotside doesn't persist in round trip
from rigorous heat exchangers using HTRI, switching to HXRIG,
and then back to HTRI.
Licensing For FlexLM licensing a user is unable to "borrow" the suite
licenses. Instead, he/she must borrow a specific product license
but will then consume the suite license.
Material The Material Balance output shows an imbalance in the
Balance flowsheet when a Check Solids unit operation is present. The
Check Solids has a feed but no products, but the lack of a
product is not accounted for properly in the overall balance.
Optimizer Constraints Minimum and Maximum for Optimizers are not
reported correctly in View Results.
PFD Printing a flowsheet page prints more than what is inside the
drawn page when the Fill Option is set to gradient.
PFD Unnecessary calculations are being done, and warning
messages being generated as the curser moves over streams
with Tooltips turned on. In flowsheets with a large number of
components and/or thermo sets this results in excess
performance degradation.
Plot TDM allows the user to plot logP vs. 1/T. However, the label on
the x-axis is incorrect.
Polymer A polymer CSTR ZN reactor appears to react reasonably on first
pass, but hit run again and there is no reaction.
Reaction Data Activation energy in kcal/kg-mole gets converted to a bad value
going from v7.1 to v8.0.

Feature Description
Reaction Data A file with reaction that has stoichiometric imbalance imports
into Provision with errors. However, the same file can then be
run without errors which is should not be possible.
Reaction Data Assigning a Case Study parameter to a reaction activation energy
could cause and access violation error.
Reaction Data Flowsheet with reaction data section, multiple blends and a large
number of resulting pseudocomponents, gets an access
violation exception when entering reaction data.
Reactor File with conversion reactor and LS components work OK on
import, but after you modify the file, it aborts. Work with it some
more and you get an exception error.
Reactor When a large number of Runge-Kutta steps (~20,000) is
specified, the PFR profiles does not report values for total length.
Reactor With the reference state set to ideal, the reactor enthalpy path
gives the reference state as 0 psig. The enthalpy is actually
calculated at ideal vapor state.
Recycle In one case, the flowsheet does not converge but PRO/II says its
converged. One of the streams was still red and the splitter
specification was not met.
Refinery TAN (Total Acid Number) is available as a keyword RIP, but isn't
Inspection listed on the GUI as an option.
Properties
Refinery The Refinery Inspection properties specified in the input file are
Inspection not correctly mapped within the Parameter selection data entry
Properties window of the Calculator unit-op.
Report Repeated use of SIM4ME report manager causes an increase in

the memory usage of PROII.EXE as viewed from Task Manager.
Memory is not getting released. Repeated cycles of Run/Report
may cause an exception error.
Reset Unit The reset unit generates a warning that the product streams have
a different thermodynamic set from the feed streams. However,
that's the one unit operation which can ONLY work right if the
product streams have a different thermo from the feed streams.
The warning is incorrect.
Run Batch The INCHECK keyword on the CALCULATION statement is
ignored when the file is run using the Run Batch option, or using
the RUNP2 batch command.
Sequence Flash with two feeds, one defined and one referenced to product
from flash solves without recognizing implicit recycle loop and
gives mass imbalance.
Sequence Pseudo-stream products from columns may not be registered
correctly in the MBAL table resulting in a report that appears to
be out of mass balance. The flowsheet results are OK, however.
SIM4ME SIM4ME Reports do not work with some European and Latin
Reports American regional settings.

Feature Description
Spec Vary Distillation points (D86(5%), etc) for a stream can specified or
Define defined in 1 percent increments via keywords. However, only five
percent increments are available via the GUI.
Spec Vary Define of a flash duty relative to a column duty in a flash zone
Define does not persist after run and re-open of flash data entry
window.
Stream The Kinematic Viscosity data for an assay stream may or may
not include the Average data for a temperature. Kvis can be
supplied at two temperatures, normally 100 F and 210 F. If one of
those temperature curves contains an average Kvis but the other
doesn't, on export to keywords both of the average Kvis values
will be missing.
Stream Pseudo stream from rxdist column does not get it's enthalpy
transferred correctly to a stream that references it.
Stream There is inconsistency in the values reported for the different
RVPs when they appear in the user defined properties list in the
output report compared to that retrieved by defines in a
calculator.
Stream The Stream Properties spreadsheet tool reports water Cp value
as 0.0 BTU/Lb-F. The output report shows it as 0.997 units.
Stream The Component Rates spreadsheet tool reports a mole flowrate
for Non-MW solids. This rate should be reported as "n/a".
Stream The reported heat capacities are wrong for liquid streams w/
water in the Tools/Spreadsheet/Stream Properties Excel report.
Also, the pure water stream reports a Cp of 0.0 which is wrong.
Stream The SPT does not update the components displayed when the
Property Table component is deleted from the flowsheet.
Solid A file with a Check solids unit operation failed to predict solids in
v8.0. The same run in v7.0 did predict solids, which is believed
to be the correct answer.
Tags The PI client is not working. There is no way to make the PI
Historian work. On usage you get the following message from
the PI server the user gets an 0XE06D7363 error followed by a
system crash.
TDM In a few cases, install of PRO/II on a clean (without previous
Integration SimSci products installed) Windows 2000 SP4 machine gets an
error message on about tdm20\bin\registerth.bat. The install
fails.
TDM Attempting to launch TDM from within PRO/II gives an exception
Integration error when logged in as a User. Logging in as a Power-user or as
an Administrator works OK.
Thermo When some of the components are VL components and the rest
are VLS, the NRTL interaction parameters as printed in the
thermo reprint page may not have the values.
Thermo In some cases the binary interaction parameter reprint is not
printed in the output when requested.

Feature Description
Thermo The Wilson parameters for one of the binary pairs may not be
reported in the Thermo reprint. It appears that the user supplied
value is being used, however.
Thermo The combination of use of Stream Property Table in combination
with Lee-Kesler-Plocker thermo may result in a file bloat problem
where the .prz file increases on each cycle of run-change-run.
Thermo Files with large numbers of thermo systems and a large number
of components may take a long time to perform certain steps -
such as File Convert to v8.0, and Run.
UAUOP Compiling the new user-added utilities and UAUOP using the
new INTEL FORTRAN compiler does not work.
Summary of Defects Fixed in PRO/II 8.0 Patches

Feature Description
ACE A warning message "The TUBE ROW WIDTH is INVALID. It is
less than the duct width" comes up even when there is no duct
width entered. This warning should only occur when there is a
user-supplied conflict between tube row width and duct width.
ACE The ACE unit reports the wrong duty for one case due to
inadequate internal solution tolerance. Repeat the run and the
duty comes out OK. The outlet temperature changed very little in
the two runs in this case, but a small temperature change
resulted in a large duty change.
AMSIM An AMSIM column simulation gets a Floating Point Over- flow
error. Increasing diameter (decreasing loading) resolves the
problem.
AMSIM Liquid/liquid AMSIM absorber gets floating point error. The root
cause is that the liquid rate is too low. AMSIM should provide
diagnostic rather than generate a floating point error.
AMSIM In one particular Amsim run with a large column (in terms of
trays), liquid flows rates of column traffic don't match flow rates
of external streams. Also, there are some obviously incorrect
tray compositions reported by the Amsim GUI towards the
bottom of the tower. This can be detected by observing a lot of 0
compositions for trays and components that clearly should not
have a 0 value.
Assay The addition of the petro components with NBP same as that of
assay generated petros results in an access violation exception
error.
Assay Using the API-87 interconversion, the D2887 to TBP conversion
may not be correct at the 70% point. Typical errors are < 3 F.
Assay On the ASSAY statement, the keyword CURVEFIT must be
supplied in full. PRO/II standard is to accept the first four
characters.

Feature Description
Assay An access violation exception error occurs when the flowsheet is
run after the secondary assay cutset (defined as default) is
deleted.
Assay The D86 to D2887(98%) conversion do not exactly reproduce
the method in the API databook when the API '87
interconversion method is selected.
Block Diagram The deleting a component and replacing it with another is not
reflected in stream property tables inside a block diagram.
Case Study When the scope for a Case Study Parameter statement
concludes and PRO/II continues to the next case, the value for
that parameter remains unchanged with respect to the last case .
However, PRO/II incorrectly reports the value as reverting to
base case.
Column The column vapor composition plots are wrong when the
component list has a liquid-solid component.
Column The mole / mass / volume composition fractions printed for a

RATEFRAC column in the column summary are incorrect when
the components are reordered.
Column When Duty Names are integers, PRO/II confuses them and treats
them as actual integers rather than strings. Specifications on
duties (using the Spec system, not the duties directly), will get
scrambled after repeated run/change/runs. The workaround is to
use a text string instead of an integer for the name.
Column The SIM4ME Reports column summary does not report the
feeds and products rates.
Column The File Converter applied to a file with a column and DEFINEd
duties on multiple pumparounds may end up getting the duties
defined to the wrong heater/coolers.
Column There is an undocumented liquid volume of 1 m3 for reaction
volume in RXDist. If the user fails to enter a volume, that default
is used without warning creating the possibility of serious error.
Failure to enter the liquid volume should be errored out.
Column Component composition tray print out is in scrambled order
when a mix of VL and VLS forming components is present.
Normally this doesn't occur because the great majority of
components in the PROCESS bank are all VL components, and in
the SIMSCI bank are all VLS components. However, there are a
couple of exceptions. Also, if a component is not found in the
default bank, PRO/II will search the other bank. The workaround
is to make sure that all the components have the same phase
potential designation.
Component Duplicate component rate values for the same component in a
keyword file aren't flagged as an error during import.
Component In one case, PRO/II hangs while performing component lumping
calculations during output time.
30 Summary of Defects Fixed in PRO/II 8.0 Patches

Feature Description
Containerize A custom Unit Op Property List may be displayed under
PRZ Stream Property Lists instead of Unit Op Property Lists. When
you are opening a file that uses that custom Unit Op Property
List, opening the list on the PFD and then OKing may cause an
exception.
Controller Controller using default tolerance on a pressure difference spec
solves unconditionally even though a reasonable tolerance has
not been met. The workaround is to provide an absolute
tolerance.
Depressuring On the controller history for changing the valve constant of the
Depressuring unit, the UOM are in internal PRO/II units (SI)
rather than user units as are other controller variable reports.
Excel UAUOP The Excel Unit Operation stopped working after one of
Microsoft's security updates. The root cause of this problem is
an update to two of the XML related dll's. Service Pack 5 for
msxml3.dll and msxml3r.dll works, Service Pack 7 fails. The
workaround is to revert to the older dll's.
Excel UAUOP After running Excel unit operations the values of INT, PAR, and
DBLs reported in the output report have not been updated with
the calculated results.
File Some of the benchmark timings for GUI performance have
increased over v7.1. These include file/open, file/new, file/
import, exit and starting PRO/II.
File You cannot open a file created in v8.0.1 in v8.0.0. Customer sites
that are incompletely updated with Patch 1 will not be able to
trade files reliably.
Flash Flash with GPSA thermo, 2500psig and high H2O and H2
content, generates two phases which it reports as L2 and L1.
Should be L2 and V.
Flash In one case, a feed stream flash with high hydrogen content, and
assay streams present elsewhere in the flowsheet, worked the
first time and failed after a Restore Input data operation.
Flash In one case while using the Chao-Seader method, the simple
heat exchanger converges while the flash unit operation with
same specification fails.
Import On the ASSAY statement, FIT=VER7 fails even though that was
the way it was written out in file export in previous version of
PRO/II. VER7 should be an alias for IMPR.
HCURVE The ACE unit data added to a heating-cooling curve does not
persist. If you add an ACE to Hcurve and commit it and then
revisit the Hcurve, it is in the unsatisfied state.
Hot Key Cutpoints and NBP of cutpoints are plotted incorrectly on Tools/
Distillation. The plots should be based on the midpoints of the
components actually used, but appears to be based on the
standard reported 9 - point curves. The histograms of the
pseudocomponents don't match the actual components.

Feature Description
HTRI/HTFS You cannot run the HTRI DOS interface from Windows Start
menu when the user creates the .pr1,2,3 files from Provision.
Saving the simulation as a .prz file works OK.
HX The simple heat exchanger and LNG heat exchanger unit op
property tables do not have an MTD attribute available.
HX Changing the attached simple exchanger to point to a different
pumparound does not persist. It uses the old PA during run time
and reverts to the old value when you reinspect the DEW after
running.
HX In one case, the simple heat exchanger hot side specification of
1e-18 above dew point generated a product stream with liquid in
it.
HX Deletion of a product stream from an HX unit operation, and then
attach a new stream results in red borders. The newly attached
stream may appear as duplicate entries within the HX DEW.
HXRig In one case, the rigorous heat exchange unit (HXRIG) using the
rating mode and the Chen HTC model calculates different U
values for rating vs. design. Running the rating a second time
gets the correct results. This seems to be an internal tolerance
problem.
HXRig The rigorous heat exchanger in flowsheets with potential solid-
containing components gives excessive warnings at the
beginning of the simulation. This comes up frequently now with
the "SimSci, Process" databank order where most components in
the SimSci databank have solid properties. PRO/II correctly flags
an error in the HXRIG unit during calculation time when solids
are detected in the feed streams to the unit, thus the reduntant
warnings at the beginning of the simulation are unnecessary.
HXRig The calculation of weighted average of Prandtl number is
missing for the new HTC method (i.e Modified Chen
Vaporization) added in the v8.0 output report.
HXRig/HTRI PRO/II only supports the HTRI-Xist program. PRO/II crashes if
the HTRI file selected belongs to air-cooled exchanger (Xace) or
plate and frame heat exchanger (Xphe). It should fail with a valid
diagnostic.
HXRig/HTRI TEMA Shell type J12 and J21 designation, while present in the
HTRI input file, are not preserved in the HTRI_OUTPUT.htri file.
This results in the HTRI_OUTPUT.htri file failing during the HTRI
XIST session.
HXRig/HTRI When initializing a PRO/II HTRI unit operation from an external
.htri file, the external file is eventually deleted.
HXRig/HTRI HTRI allows both hot side and cold side outlet temperatures to
be specified. This information is lost when creating the
_OUTPUT.htri file - only the cold side is specified.
Help Help/Update does not work.

Feature Description
Library The number of binary pairs that can be handled by Library
Manager Manager is 6662. This number needs to be increased to 30,000.
LNGHX An LNGHX that fails on the first couple of passes through the
recycle but eventually solves, fails to apply the specified delta p
to one of the cells.
LNGHX A file with VLS components generates warnings for LNGHX even
though solids are not present in the flowsheet. This check should
only be conducted at run time.
PFD Export with layout will get an old version of the layout if there
was no save operation right before the export.
Pipephase PRO/II files with embedded multiple v7.1 Pipephase simulations
Integration will only do a file convert to Pipephase 9.1 on the first Pipephase
Unit OP opening. The second one crashes with a file-open error.
Pipephase PRO/II and Pipephase may not match in component order
Integration resulting in compositions being wrong in Pipephase. This will
happen when the components in PRO/II are not all of the same
phase formation potential (for example, say nC8 is user-selected
to be a VL component while nC9 is a VLS component). Most
components in the PROCESS library are VL components, while
most components in the SIMSCI library are VLS components. All
PROCESS or all SIMSCI components usually works, but there
are exceptions.
Reaction Data When creating reaction kinetics, the default rate (in SI units) is
1e3 kJ/kg-mole for the pre-exponential term. It's dangerous to
have any default in there . it should be empty and in the
unsatisfied (red) state.
Reactor The Plug Flow reactor diameter cannot be input via the Define
syntax using keywords. The input process accepts the syntax,
but the diameter imports to a zero value. If roughness is given,
an error occurs because roughness is > diameter.
Reactor A conversion reactor with solids flowing through may result in
bad solid rates for individual components in the product.
Reacttor An equilibrium reactor in a recycle loop may fail in the third or
later recycle pass. Once it starts failing it's unable to recover in
subsequent iterations.
Report "Problem solution not reached" is sometimes incorrectly
displayed for fully converged files in SIM4ME reports. This may
occur in Run/Change/Run scenarios where the first run failed to
converge and the second one did converge.
Sequence Changing the recycle sequence from MTS to User Defined
results in failure to identify the tear streams.
Sequence In some cases, reopening a file with an excluded unit operation
may display the excluded unit as included (not grayed-out).
Shortcut The condenser and reboiler duties reported for the Shortcut
Column are wrong in some cases.

Feature Description
Spec Vary File export uses the syntax DEFINE DUTY(KC/H) AS
Define COLUMN=T1, DNAME(KC/H)=FURNACE for column duty
defines. However, the equivalent file import routine does not yet
recognize the new DNAME keyword on the DEFINE statement.
Spec Vary Defines pointing to the condenser as Duty(1) are being Define
Define ignored on import.
Spec Vary GUI selection of the RVP calculation may result in the Define
Define wrong method being selected. Selecting API Naphtha, API
Crude, API D323-73 works OK. Selection of D323-82, D323-94,
D4953 and D5191 may result in the wrong method being used
even though PRO/II indicates the method selected by the user.
Spec Vary In one case, an attempt to retrieve "vapor" phase compressibility
Define for a super-critical pure ethane stream from a Calculator Define
resulted in a BAD STARTING ADDRESS POINTER exception.
Stream SIM4ME Reports print values for some properties of zero rate
streams. It should print n/a.
Stream Changing the stream type from assay to any other type causes
an access violation exception error in some cases.
Stream File with VLS components generates warnings for the Stream
Calculator Calculator even though solids are not present in the flowsheet.
This check should only be made at run time.
TDM Importing a file with user defined databank that is not registered
Integration through TDM fails to generate an error. It's too easy to miss the
warning. Continuing to run may result in a bad solution without
further warning.
TDM The file conversion of a file with a user=defined databank fails
Integration even though the databank is registered through TDM.
TDM Run Batch on a keyword file with a missing component databank
Integration specified will run and generate an easy-to-miss warning
message, and continues with calculations even though data
might be missing. This situation needs to generate a fatal error
message to avoid a bad-answer, no-warning situation.
TDM TDM does not work for Power User.
Integration
TDM Un-installation of either Pipephase or PRO/II prevents the launch
Integration of TDM from PRO/II and Dynsim. Workaround for this issue is to
run the RegOCX.bat located in %TDM_ROOT%\..\TDM20\bin.
TDM Unifac databanks should not be modifiable by the user, but a
Integration button is enabled in PRO/II that allows you to open up a TDM
databank. Any attempt to create a TDM library in all of the Unifac
variant thermos causes an error in TDM. This button should be
disabled.

Feature Description
TDM The SAFT and PHSC thermodynamic methods (used for
Integration polymers) are not recognized by TDM, and TDM will not create a
databank for them. The access to the TDM should be turned off
within PRO/II.
TDM An exception error occurs while trying to use the user-define
Integration library on non-NTFS drives.
Thermo An older version (< 7.1 Patch 1) file with transport properties not
calculated converted into 8.0 does not export into a keyword file
with TRANS=NONE designated. Thus, when you reimport, the
TRANS=PURE will be assumed. The file as initially converted,
and the one after imported, will thus be different.
Thermo Physical properties (density, entropy, etc.) for steam calculated
with IF-97 steam table calculations are incorrect for pressures
above 16.5 mPa.
Thermo Old files with multiple thermo systems and a large number of
components takes much longer to convert to v8.0 compared to
v7.1. For five or more thermo systems, the difference can be two
orders of magnitude. Similarly, v8.0 files with multiple thermo
systems can take much longer to initiate a run than in v7.1.
Thermo Keyword file with Electrolyte thermo with transport properties
turned on should generate an error on import. It's not.
Thermo An access violation may occur when importing a keyword file
with TBC thermo.
Thermo In the data files created by Library Manager, there are always
some strange characters at the end of the row "NAME".
Thermo Using BWRS thermo, the phase of a pure helium stream is
reported as liquid while other thermo methods show it as vapor
(as you would expect). This does not affect any flowsheet
calculations.
Toggle Stream An access violation exception arises when the user specified list
that the stream id toggle uses is deleted.
Tooltip Hovering over a stream when stream tooltips are turned on
creates a dead-time while property calculations are being
performed. The lag is far in excess of what it should take to
create this table. This occurs on flowsheets with a large number
of components and/or thermo systems.
Tooltip Tooltip style Stream Property Tables does not honor the user
specified real number formatting. Regular Stream Property
Tables are OK.
Unit Property The Pipe Unit Operation Table has confusing and duplicate labels
Table for available attributes.
UAUOP Increasing the number of DBL parameters in the Excel unit
operation doesn't work. For example, change the number from
10 to 20 will result in 10 parameters still being used.

Feature Description
UOM DUTY=KCAL/HR on the dimension statement is not honored -
the duty imports as Energy units per time units. However, the
numeric value is unchanged so if energy or time doesn't
correspond to KCAL/HR, the values are wrong.
Valve The specified pressure drop across a valve unit operation is not
honored when the product stream is a tear stream in a recycle.
This works OK if the valves are replaced with equivalent flash
unit operations.

Summary of Open Defects in PRO/II 8.1
PRO/II 8.1 Bug Lists
To access the current version of PRO/II 8.1 bug list as well as FAQ
and Updates, visit our website's Knowledge Base at http://
www.simsci-esscor.com. Select Support Menu and then the
Software Updates & Knowledge Base. Select Enter the SIM4ME
Software Updates & Knowledge Base Website. Updates. Finally select
PRO/II and enter in your personalized SIM4ME Username and
Password.
If you do not have a SIM4ME username and password, please take a
few minutes to register. Registration will allow you to access our
complete Knowledge Base as well as allow us to display custom
information of interest to you.

License and Copyright Information
Release Notes for The software described in this guide is furnished under a
PRO/II 8.1 written agreement and may be used only in accordance with
the terms and conditions of the license agreement under which
you obtained it.
Copyright Notice © 2007 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, SIM4ME, HEXTRAN, INPLANT, PIPEPHASE, Invensys,

and SimSci-Esscor are trademarks of Invensys plc, its
subsidiaries, and affiliates. AMSIM is a trademark of DBR
Schlumberger Canada Limited. RATEFRAC and BATCHFRAC
are registered marks of KOCH-GLITSCH. Visual Fortran is a
trademark of Intel Corporation. Windows NT, Windows 2000,
Windows XP, and Windows 2003 are trademarks of Microsoft
Corporation. FLEXlm is a trademark of Macrovision. Adobe,
Acrobat, and Exchange are trademarks of Adobe Systems Inc.
Intel and Pentium are registered marks of Intel Corp. HP is a
registered mark of Hewlett-Packard Co. Epson is a registered
mark of Seiko Epson Corp. Canon is a registered mark of
Canon Inc. NEC is a registered mark of NEC. 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.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. (a division of Invensys plc. and owner of the SimSci-
Esscor brand) 26561 Rancho Parkway S., Lake Forest, CA
92630, USA.
Printed in the United States of America, May 2007.
38 License and Copyright Information

PROII81 ReleaseNotes PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

PROII81 ReleaseNotes PDF

Transféré par

Droits d'auteur :

Formats disponibles

Important: Read First

Release Notes for PRO/II 8.1

PRO/II 8.1 Release Notes 1

New Feature Description

TDM Integrated Thermo Data Manager Application

Overview of New Features

2 New Features of PRO/II 8.1

Perform Special Calculations

PRO/II 8.1 Release Notes 3

● From PRO/II toolbar/menu option

● Create a new one

● Connected: PRO/II with ProVision concurrently open with

● Stand-alone: Only SIM4ME® Portal open

● Run command: Excel to PRO/II

4 New Features of PRO/II 8.1

● Temperature-dependent thermo-physical property data can

● Binary and multi-component data can be regressed

● Multiple types of equilibrium data – binary and higher order,

Multiple Data Sets

Multiple Calc Options

PRO/II 8.1 Release Notes 5

Default changes in PRO/II v8.0:

● Chen - Modified Chen Vaporization method (NEW DEFAULT)

● "BBM" for the Beggs-Brill-Moody method (NEW DEFAULT)

PRO/II 8.1 Release Notes 7

The approach to equilibrium method is normally used by

7. This update also includes an updated utility to send .xml files

PRO/II 8.1 Release Notes 9

Important information for uninstalling previous versions of

Known Defects and Constraints using SIM4ME Reports

PRO/II 8.1 Release Notes 11

Known Defects and Constraints using SIM4ME Portal

PRO/II 8.1 Release Notes 13

(b) Start Sim4Me Portal application in stand alone mode, open

(c) Execute the batch file “PortalApplibs.bat” placed in C:\SIM-

After following any of the above three options, you should be

PRO/II 8.1 Release Notes 15

Switching Security Types for PC

To switch to USB security:

Type=FLXLM95 For FLEXlm version 9.5

PRO/II 8.1 Release Notes 17

This assumes that you have installed to “C:\SIMSCI\Proii81”.

We strongly recommend that you take advantage of the free

Depending on the options selected when you installed Compaq

If you are using Intel FORTRAN 8.0:

This assumes that you have installed to “C:\SIMSCI\Proii81”.

User-Added Subroutine: IDATA(6) of the USERnn subroutine

In both of these cases, PRO/II calls the FORTRAN OPEN statement to

PDTS example modified for Intel FORTRAN interoperation with

PRO/II 8.1 Release Notes 19

Original UAS example:

UAS example modified for Intel FORTRAN interoperation with

Running PDTS Applications

If you execute a PDTS application, you may get the following

In order to run PDTS applications, it is necessary to add additional

This can be done by executing the batch file setPDTS.bat which is

It is *not* recommended to change the system PATH in the Control

PRO/II 8.1 Release Notes 21

Note: The PRO/II Welcome screen for the online documentation

22 Where to Find PRO/II 8.1 Documentation

PRO/II 8.1 Release Notes 23

24 Summary of Defects Fixed in PRO/II 8.1

PRO/II 8.1 Release Notes 25

It is not recommended to change the system PATH in the Control