PROII93 ReleaseNotes

SimSci
PRO/II 9.3
Release Notes
May 2014
All rights reserved. No part of this documentation shall be reproduced, stored in a retrieval system, or
transmitted by any means, electronic, mechanical, photocopying, recording, or otherwise, without the
prior written permission of Invensys Systems, Inc. No copyright or patent liability is assumed with
respect to the use of the information contained herein. Although every precaution has been taken in the
preparation of this documentation, the publisher and the author assume no responsibility for errors or
omissions. Neither is any liability assumed for damages resulting from the use of the information
contained herein.
The information in this documentation is subject to change without notice and does not represent a
commitment on the part of Invensys Systems, Inc. The software described in this documentation is
furnished under a license or nondisclosure agreement. This software may be used or copied only in
accordance with the terms of these agreements.
2014 by Invensys Systems, Inc. All rights reserved.
Invensys Systems, Inc.
26561 Rancho Parkway South
Lake Forest, CA 92630 U.S.A.
(949) 727-3200
http://www.simsci.com/
For comments or suggestions about the product documentation, send an e-mail message to
ProductDocumentationComments@invensys.com.
All terms mentioned in this documentation that are known to be trademarks or service marks have been
appropriately capitalized. Invensys Systems, Inc. cannot attest to the accuracy of this
information. Use of a term in this documentation should not be regarded as affecting the validity of any
trademark or service mark. Invensys, Invensys logo, PRO/II, and SimSci are trademarks of Invensys
plc, its subsidiaries and affiliates.
9.3 Important: Read First

Release Notes for PRO/II 9.3
Welcome to the release of PRO/II 9.3. These Release Notes
supplement and supersede the corresponding sections in all
PRO/II 9.3 documentation supplied with this release.
Contents
New Features of PRO/II 9.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Important Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
PRO/II 9.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
PRO/II 9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
PRO/II 9.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
PRO/II 9.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
PRO/II 8.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
FAQs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Installation Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Limitations in REFPROP Add-on . . . . . . . . . . . . . . . . . . . . . . . . . 17
Constraints using SIM4ME Reports . . . . . . . . . . . . . . . . . . . . . .
Constraints using SIM4ME Portal. . . . . . . . . . . . . . . . . . . . . . . .
Switching Security Types for PC. . . . . . . . . . . . . . . . . . . . . . . . .
UAS/PDTS Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18
21
23
24
Where to Find PRO/II 9.3 Documentation . . . . . . . . . . . . . . . . . . . . 30

Printed Documentation Included with this Package . . . . . . . . . . 30
Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Summary of Defects Fixed in PRO/II 9.3 . . . . . . . . . . . . . . . . . . . . . 31
Summary of Defects Fixed in PRO/II 9.2 Patches . . . . . . . . . . . . . . 42
Summary of Open Defects in PRO/II 9.3 . . . . . . . . . . . . . . . . . . . . . 50
License and Copyright Information . . . . . . . . . . . . . . . . . . . . . . . . . 51
PRO/II 9.3 Release Notes
New Features of PRO/II 9.3

The following enhancements have been made to PRO/II 9.3:
New Feature
Description
Infrastructure
Update icons in Menus and Toolbars.
All menu items now have icons associated with them that
can be placed on a toolbar. By default all of the icons are
installed on the tool bars. Right-click on any toolbar to
customize the toolbars to your liking. Pre-9.2.1 toolbars can
be selected this way if that is your preference.
Security Upgrade to Flexera 11.11
FlexLM95 is no longer available as it is, not supported by
Flexera. Users will need to upgrade to 11.11.
Microsoft Directory Standards
PRO/II now follows the Microsoft Directory Standards for
naming the directories. Following are some of the changes:
Programs: C:\Program Files (x86)\SIMSCI\PROII93
Data: My Documents\SIMSCI\PROII93
Configuration and TDM files:
C:\Users\USERNAME\AppData\Roaming\SimSci\PROII93
SIM4ME Portal Upgrade
PRO/II has been upgraded to use the latest version of
SIM4ME Portal, 2.3. Following are the notable changes:
MS Excel 2003 is no longer supported.
MS Office 2013 is now supported.
Usability
Improvements
Open File in original version

When opening a file from an earlier version user can migrate
or request to open that file in the original version if installed
in the PC. If the old version is selected then the current
session of PRO/II is exited and the old version is launched
top open the simulation file.
Run Unavailable help
When data is not incomplete and case cannot run, the
unsatisfied stream or equipment is shown on red. But
sometimes the red is hard to find on large simulations. The
Run Unavailable pop-up will show all the problem sections.
Double click on the problem item and the Data Entry Window
(DEW) will open.
New Feature
Description
Exclude Include Block diagrams
PRO/II allows users to control which unit operations are
included or excluded in the calculation sequence. A
convenient way to include or exclude unit operations is to
use the Include Unit and Exclude Unit commands in the right
click menu. PRO/II v9.2 allows you to exclude individual unit
operations by using right click menu option. PRO/II v9.2.1
expands that capability providing right click menu options to:
- Exclude/Include selected block diagram.
- Exclude/Include selected multiple unit operations.
To use this feature, select one or more block diagrams and
unit operations. Right click to reveal the Exclude and/or
Include options. If any units are Excluded in the selected
group, the Include Units (or Block Diagram if it's just that)
will be available. Clicking on that, all units in the selected
group will be enabled. Similarly, if any units are Included in
the select group, the Exclude Units (or Block diagram if it's
just that) will be available. Clicking on that, all units in the
selected group will be disabled. The streams in between the
excluded unit operations will be in excluded state.
Spiral CrudeSuite 5.5.1 integration to PRO/II 9.2.1
v9.2.1 links Spiral's CrudeSuite extensive crude database
and property prediction capability with PRO/II's
comprehensive process simulation capability allowing the
user to seamlessly select CrudeSuite feedstocks in refinery
simulations.
Default Viewer back to Editor
Improvements in User Interface
New colors to identify selected units, copied units, and
failed units.
Quickly Close Multiple Windows
OK to PFD/Cancel to PFD button added to multiple DEWs.
STD and ACT
Volumetric flow rate is now clearly defined as STD
(Standard) or ACT (Actual).
Controller and MVC Behavior
Default has been changed to failed unit and continue
calculations if limits are reached.
If a Controller or MVC fails, the unit is now set to Not Solved
without terminating calculations by default. This allows
subsequent units to be calculated with the possibility that
future passes of the Controller or MVC might solve.
New Feature
Description
Sequence Improvements
The Sequence Data Entry window has been completely
redesigned to provide powerful tools to manage and visualize
sequencing of units and calculation recycles.
The sequence map is now a tree view with nested child
branches representing nested recycle loops.

Calculation loops are coded blue.
Loop crossings are coded red.
Units can be included or excluded with one click.
Parent calculation loops and can be clicked off to exclude
the embedded units.

Unit operations, blocks and recycles can be dragged-and-
dropped anywhere on the tree. Child units are moved with

the parent.
There is a new Find Units feature.
Case Study Improvements

Support for matrix case study.
If cycle fails, it is shown with an * on the cycle number.
Phase Envelope Updates

Add additional EOS to the list of acceptable method sets.
Color code phase envelope lines.
KG Update
New packing correlations received from KochGlistch and
incorporated into PRO/II.
Copy/paste to/from Excel for data in UAS
Click the corner of the grid to select the entire grid, press
Ctrl+C on the keyboard, and then paste it in Excel.
New Feature
Description
Heat Curve Updates
Provide heating/cooling curves for exchangers at three
pressures inlet, outlet, and halfway in between.

Provide option for both sides of the exchangers at once
Allow attributes within a Heat Curve (such as T& P
Ranges) to be set via the "Define" function. Note: Due to

the generic Spec window in PRO/II the choices in the
define may not look reasonable. Always define
Temperatures and Pressures with respect to a stream not
to a unit operation.
The method set for exchangers is forced to match
exchanger method, the field selection is ignored. It is

used only for stream based curves.
Standard heat curve generation from Exchangers at inlet,
outlet and mid pressure isobars.

Improve Depressurization
Re-order product streams
Create pseudo-streams corresponding to instantaneous
vent rates at specific times

Support Density and thickness in Vessel Geometry
Report temperature downstream the relief valve
Add Depressuring Time vs. Pressure Summary to
Depressuring report
Indicate whether flow through valve is critical or sub-
critical
Supply wall and liquid temperature profiles
Require final pressure in depressuring unit to be exactly
the specified PFINAL

Null Out Product streams when the step size is increased
so that fewer streams are produced

Liquid Relief in Depressuring unit
Valve Policy & user control of flow rate and depressuring
time
Provide a Qext UA(Text-Twall) calculation for Blowdown
Dynamic Wetted Area
Put the maximum pressure on the VAT so it can be used
as a control parameter.
Valve policy for User model & Orifice model for area
Document Depressurization unit
New Feature
Description
Convert all Excel spreadsheets and Excel unit operation to
Office 2010 and improve on Column and on Heat Curves
spreadsheet.
Column Spreadsheet
Column summary in mass basis
Column tray plots rates in moles and in mass
Column tray component composition data
Heat Curves Spreadsheet

Transfer all H-Curve properties to spreadsheet tools
All component related properties to be reported when
requested
Heat curves spreadsheet in output units
Tray Properties Available for COM Programs

Find all the details on tray without the need to create
pseudostreams or reflashing internal streams to retrieve
data.
Reports
Tools/Spreadsheet/Heat Curves Update

Easier selection of curves available.
Multiple units available.
Additional properties transferred
Unit Operations
EXCEL Calculator
Same icon as the calculator but choose Excel. Define
parameters, resutls, constants, etc as always.

Select Excel File (template available) and edit it.
No need for FORTRAN language if you do not know how
to code FORTRAN
New Feature
Description
Thermo
PRO/II THERMODYNAMICS
New features pertaining to Thermodynamic entries include:
Choose default system and options when adding
methods.
Select full thermo definitions for new simulations based
on existing simulation.
Thermodynamic Partial Import - When the file is selected
as default but no specific method is set, the file name is

filled on new field. User can use pre-defined file or pick
another file and press Extract.
Correlation 18 for Temperature Dependent Properties.
Correlation 18 can now be chosen for Temperature

Dependent Properties. This is primarily used in solid
enthalpy calculation.
Property = C1 + C2 * T^C3 /(1 + C4/T + C5/ T^2)
Change to default Heat of Formation
The default for prediction of Heat of Formation Data from

petro components has reverted back to the v9.1 method.
When comparing against pure component data, some
classes of hydrocarbons showed improvement in heat of
formation prediction, but unfortunately some
components were worse - for example aromatics. It was
decided to revert to the existing correlation for default
until a clear case can be made for an improvement.
DIPPR 2013
Yearly updates on DIPPR 2013 from now on based on

Lite Database. Sponsor database will be made available to
DIPPR for distribution by DIPPR.
There are values in the SIMSCI databank that are available
only in the SIMSCI databank. If user encounters a
component in DIPPR with such situation, user can select
to cascade data. This will cascade to the next library in
search of missing data.
SIM4ME Thermo 3.8 Updates
NIST REFPROP 9.0 Fluid Files: In the past users needed to obtain a
license of REFPROP to be able to use the REFROP added method
sets in PRO/II. Users can now download and install the files by
requesting them separately from PRO/II via the SimSci-Esscor
Electronic Software Distribution site.
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, 8.0x ,
8.1x, 8.2x, 8.3x, 9.0x, 9.1x, and 9.2x database files will automatically
be converted into PRO/II 9.3 files as they are opened. The original file
will be saved using an alternate file name.
PRO/II 9.3
1.
DIPPR 2013 will expire in 2024.
2.
DIPPR 2013 has a coexisting issue with PRO/II 8.3 and older
libraries. To make the earlier version work the user will need to
unregister DIPPR 2013. There is a utility included with
PRO/II 9.3 to unregister DIPPR 2013.
PRO/II 9.2
1.
Starting with v9.0, USB keys only allow a single instance of PRO/
II to be open at a time. This is intended. If you need multiple
instances of PRO/II open you need to have FlexNet security.
2.
MS Office 64 bit is not supported. Various Excel features (such

as Spreadsheet Tools) will likely not work.
3.
MS Office 2013 is not supported.
PRO/II 9.1
1.
On some Japanese Vista installations, PRO/II cannot install

completely because the required .net 3.5 will not install.
Updating the Vista OS to SP2 will enable complete installation.
2.
Uninstalling certain features of PRO/II (such as OLI, REFPROP

and MSM) will not work from Add-Remove if UAC (User Account
Control) is turned on. You can still uninstall these using Setup,
or, you can turn off UAC temporarily if your work site lets you.
3.
Installing v8.3 or earlier may unregister v9.1 libraries. Use the

new Library Registration Repair tool to fix.
4.
On some windows server machines give an 'OPCUA server failed

to start' error. The error is reproducible in the below
configuration machine. Windows 2008 R2 comes with preinstalled .Net Framework 3.5.1. Users need to enable this feature
from "Server Manager". i.e "You must use the role management
tool to install or configure MICROSOFT .NET FRAMEWORK
Important Notices
3.5".After enabling the .Net Framework 3.5.1 feature from

Service Manger install will go smoothly and OPCUA server also
install without any issue.
PRO/II 9.0
1.
Uninstalling PRO/II 8.2 after installing PRO/II 9.0, the uninstall

removes the Registered libraries in TDM and other products
could launch TDM. Use the new Library Registration Repair tool.
PRO/II 8.3
1.
PRO/II 8.3 to ROMeo 5.1 translator pops up errors and fails.

Changing the EdlibName in Translator.ini file in ROMeo 5.1
install to ROMeo_5.1 works fine.
2.
In Residue Curves, when a new workbook is created, the toolbar

gets deactivated for all open workbooks. This is EXCEL behavior.
For this reason we cannot have a warning message on a
workbook basis.
3.
Previously, distillation columns in recycle loops recalculated in

every recycle iteration. Now, improved logic tests a solved
column to determine if it needs to resolve. When no changes are
detected in the feeds, column operating conditions, or options,
nothing affects the solution. In each iteration where this is
found, the column calculations are skipped so they are not
repeated.
Previously, restarting a solved column began calculations at the
solved state. In many cases, the results drifted due to the
different starting point. Now, restarted columns always restart
using original initial conditions. This eliminates any drift in
results in most cases.
FAQs
Q1) How to operate Portal and data persistence in .prz?
A) Portal opened in standalone mode: Data entered in a PRO/II
simulation from Portal application will not be immediately
reflected in an already open prz. Data entered and saved from
Portal will appear in an already open prz file only upon reopening
it.
B) Portal opened through PRO/II Simulation: Data entered in
Portal reflect in the PRO/II Simulation as well. Even if the user
deletes it from Portal it stays in the simulation. Therefore, if the
user does not want the changes to get saved in the PRO/II
database, he or she must close the simulation without saving it.
Note: As PRO/II GUI and Portal are two independent options
interacting with PRO/II database, it is recommended that user should

use only one interface at a time to update / modify user data or else
human error can cause loss of data.
Q2) Why "Description" and "Value" cells cannot have different
alignment format?
A) As "Description" and "Value" cells for an attribute are clubbed
together they cannot have different alignment format once the
attribute is dropped on the excel worksheet. However, a
workaround is available. The user can pre-format the alignment
of the cells where he wishes to drop the attribute (Scalar or
Vector) to achieve the required alignment and then drop the
attribute.
Q3) What are the Spec/Vary limitations when compared with
PRO/II software?
A) In PRO/II software, a meaningful sentence is displayed for the
spec/vary inputs. This is not reproduced as such in this phase.
Under the current scope, the user would be allowed to just
change the specification values for units like Controller, MVC,
Column, Splitter, and Flash (Product Specification). The user
cannot change specification type, say a Duty specification on a
Flash to Isothermal specification from the Portal. For a
configured Portal file, the user can change the values of the
specification and analyze the results.
Q4) Why is it that the Portal does not issue an error in case of an
incomplete prz?
A) This is a current limitation. It is expected that an expert user
will create the PRO/II simulation file and ensure that it is
complete in all respects before passing it on to a novice user. It
is beyond the scope of the Portal to re-implement all the
validations done by the PROVISION GUI in order to detect such
conditions.
Q5) Do I need to check Excel workbook Security Option for
Running Sim4Me Portal?
A) Yes. The following needs to be checked prior to running
Sim4Me Portal:
10
Important Notices
In Excel workbook > Tools > Macro > Security > Trusted
Publishers > Trust Access to Visual Basic Project, turn this flag
ON.
Q6) Can I search for a stream say "CRUDE" or a Unit Operation

say "PREHEATER" or an attribute say "TEMPERATURE" on the
Flow sheet Explorer?
A) 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.
Q7) What are the drag-drop restrictions in SIM4ME Portal?
A) Multiple drag-drop of various groups and/or various
attributes is not currently supported. Individual items must be
dragged and dropped one by one onto the spreadsheet from FS
explorer.
Q8) What are the limitations present in Excel workbook
functionalities?
A) Normal Excel workbook functionalities like Cut and Paste are
not supported for vectors.
When user tries to copy or delete multiple cells, Excel and/or
Portal give appropriate messages about restriction.
11
Q9) I dragged and dropped a vector attribute onto an empty cell

just below scalar attribute, but it is giving me message "Existing
parameter reference would be overwritten" Why?
A) 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.
Q10) In PRO/II software 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?
A) At this point, by default only the PRO/II software Output slate
is supported in SIM4ME Portal.
Q11) How are the performance specifications shown for the
UnitOPs?
A) For the UnitOPs like Column, Controller, MVC, Splitter, etc.
the performance specifications are shown without their long
descriptions and UOM.
Q12) What should I do when a Portal file is emailed from another
PC to my PC?
A) When a Portal file is emailed from another PC to your 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 stand-alone mode using this portal file and
direct it to the PRO/II software file that it is trying to connect.
Double-clicking the emailed portal file would fail to connect to
simulation.
Q13) What Operating System specifications do I need to have on
my machine before installing Sim4Me Portal?
A) SIM4ME Portal is supported on Microsoft Windows Vista,
Microsoft Windows 7, and Windows 8. Microsoft Excel 2007,
Excel 2010, or Excel 2013 is required.
Q14) Is there a sample Portal file to get the user started? If yes,
how to use the sample file?
12
Important Notices
A) Yes. There are few Sample Portal files placed in

\Documents\Simsci\PROII93\Applib\S4MWorkbooks folder:
Multiple Simulations Link_Chiller Plant - 1 and 2.xlsm
Homotopy.xlsm
Column Interface.xlsm
ColumnProfile.xlsm
Naptha Assay_Case Study.xlsm
If you want to view these files, do any of the following:
Start PRO/II 9.3 application, open the sample file (for example, Homotopy.prz), click Sim4Me Portal icon on the toolbar.
An Open window appears. In the Open window, browse for
the required sample file (Homotopy.xlsm), and click OK.
Start Sim4Me Portal application in stand-alone mode and

open Homotopy.prz.
Double-click the Excel workbook file to view the sample Portal file.
Q15) How to install the patch for Sim4Me Portal?

A) The Sim4Me Portal patch gets installed when the patch for
PRO/II software is installed. The user just needs to install the
PRO/II software patch.
Q16) I have installed the PRO/II software patch but Sim4Me
Portal has not been installed on my machine. Why?
A) This can happen when Sim4Me Portal has not been installed
with the earlier version of PRO/II. The user might have either
manually uninstalled Sim4Me Portal after installing PRO/II 8.1 or
the user might have not installed Sim4Me Portal at all during the
custom installation of PRO/II software by unchecking the box for
Sim4Me Reports and Portal. In such a situation, the user is
required to install Sim4Me Portal by modifying the current
installation from Add/Remove programs in control panel.
Q17) Is there any security setting that we need to set in Excel
workbook in order to run Portal?
A) Yes.
13
It does not work with security setting "Very High". It can be

changed from Excel > Tools > Macro > security > Security
Level setting in Excel.
Also, in Excel > Tools > Macro > security > Trusted Publishers, check the option "Trust access to Visual basic Project".
Q18) How to use PRO/II software with USB security and Portal
with FNPTM 1111 security?
A) The user should do the following:
From Add-Remove panel, modify PRO/II 9.3 install and

select security as FNP1111. This will create the required
entry for the IPASSI_LICENSE_FILE environment variable. A
reboot is must if prompted to do so.
After reboot, modify PROII.INI to change the security to

USB.
Then PRO/II software will use USB security. Portal will use
FNP1111security. If test 2 is not done, both PRO/II software and
Portal will use FNP1111security.
Q19) When I double-click on a XLSM file, it throws 'Office
Document Customization is not available' error, why?
A) This is because it is a portal file. Therefore, the user can view

this XLSM file only when SIM4ME Portal is installed. This file will
also not behave like a normal XLSM file.
14
Important Notices
Q20) Sometimes Portal is launched in User mode for

Developer's license key. Why?
A) When developer licenses on the FNP server are used up,
Portal will launch in user mode. FNP can have both user and
developer licenses and several people may be using them at the
same time. Therefore, sometimes, it appears to a user that the
Portal launches in user mode. The actual reason is that the
developer licenses were used up on the server. Please check the
availability of developer's licenses if this happens.
Q21) An error message "Error while adding/locating PRO/II
software related menu items. Object reference not set to
instance of the object" is displayed when I double-click on
PORTAL 2.3 version file with Portal 2.3 version file already open
and vice versa. Why?
A) This is a VSTO and Excel Workbook Limitation (design
constraint). If the user wishes to launch the two versions of
Portal at the same time, the user should first launch an instance
of excel workbook and drag and drop the portal file in to that
instance of excel workbook.
Q22) When you Zoom in/Zoom out on the Portal Worksheet, text
on UOM widget is invisible. What should I do?
A) This is a limitation on Portal that when you Zoom in/Zoom out
on the Portal Worksheet; text on UOM widget is invisible. To
view the text on UOM widget properly, you should set 100%
zoom on the Portal worksheet.
Q23) What happens if you drag-drop scalars underneath vectors
for which the length may change?
A) If you drag-drop scalars underneath vectors for which the
length may change then their arrangement/format will be
disturbed. It is advisable to drop scalars above such vector.
Q24) What will happen when Microsoft Office is installed after
installing SIMSCI application using Portal module?
A) While installing SIMSCI application using Portal module,
portal requires some pre-requisites like proper version of
MICROSOFT Office to be installed before installing Portal
module. If required MICROSOFT Office version is not available at
the time of installation, SIMSCI application will display the
15
message "the required MICROSOFT office version is not

available" and hence it will not work.
To make it work, user will have to install required MICROSOFT
Office version in the machine. Then user is required to go to
Add/Remove programs and modify the SIMSCI application
install to update the Portal module.
Q25) How can I connect Portal 2.3 to work with OPC UA
Server1.1 using certificate security?
A) Set OPCUA to "true" in SIM4MEPortal.ini file. Launch the
PRO/II software or SIM4ME Portal in "Run As Administrator"
mode.
Q26). What are the restrictions on double-clicking the preconfigured Portal file?
A) If the Portal file is preconfigured with an old version of
simulation, the user must open that Portal file either through
simulation or through the standalone mode of the current
version of SIM4ME Portal. User should complete this procedure
while opening the portal file in a machine different from the
working machine.
Q27) How to migrate the Portal files from the old version to the
new version of PRO/II?
A) In the old version of PRO/II, disconnect the simulation and
save the Portal file, and then open the same Portal file with the
same simulation in the new version of PRO/II GUI.
Q28) what should I have to do when reports and Portal are not
launching when multiple products are installed?
A) Run "PortalRecovery.bat" file using administrator credentials
located at Portal bin directory.
Q29) In the Portal file, can I copy data from a single row or
column?
A) Due to Microsoft Excel limitations, when user tries to select a
particular row or column that has Portal links in it, the adjoining
cells also get selected. This prevents copying data from single
rows or columns.
16
Important Notices
Installation Notes
1.
At the end of PRO/II 9.3 installation a dialog pops up asking for

Restart, with YES/NO buttons. If user clicks No button PRO/II
9.3 libraries are not registered with TDM. The user needs to
restart before launching TDM from PRO/II 9.3.
2.
PRO/II fails to launch with the default DEP setting on Windows

Server 2003. To correct this problem, right-click on My
Computer ==> Advanced Tab ==> Performance Settings ==>
Data Execution Prevention Tab.By default, the bottom radio
button "Turn on DEP for all programs and services except those I
select". To enable PRO/II to run, select the top button "Turn on
DEP for essential Windows programs and services only. A
reboot will be required before this setting takes effect.
Important information for uninstalling previous versions of

PRO/II
1.
Uninstalling PRO/II 7.1 will disable the HYSYS Translator in

PRO/II 8.0, 8.1, 8.2, 8.3, 9.0 and 9.2 if they are installed on the
same machine. During the PRO/II 7.1 uninstall process, the
"Simulation Sciences\PRO/II key is completely removed. The
workaround is to export the "HKEY_LOCAL_MACHINES\Softwares\Simulation Sciences" keys to a .reg file, and then reimport the file after completing the uninstall. This issue has
been addressed tarting with PRO/II 8.0 so uninstalling PRO/II
8.0 or PRO/II 8.1 will not affect other versions of PRO/II.
2.
Uninstalling PRO/II 7.1 will disable Visual Flow 5.x. During the
PRO/II 7.1 uninstall process, the "Simulation Sciences\PRO/II
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 starting with PRO/II
8.0 so uninstalling PRO/II 8.0 or PRO/II 8.1 will not affect
installed versions of Visual Flow.
Limitations in REFPROP Add-on

Users must be aware of the following limitations the REFPROP Addon has with respect to the standalone REFPROP program from NIST:
1.
Only the REFPROP fluids are supported. The list of supported

fluids also varies with each method. The list of supported fluids
is shown in Appendix B of SIM4ME Thermo REFPROP Thermo
Add-on Release Notes found under \\Manual\User.
17
2.
The fluid files must all be located in the same folder. The location
is saved in the RefProp.ini file as part of the Add-on install step.
3.
Only three thermo methods are supported at this time: NIST23

(the default in REFPROP), GERG-2004 and AGA-8. Other method
variations or combinations available through the standalone
REFPROP application are not supported.
4.
The AGA8 method is only valid for the vapor phase (this is a
limitation of AGA8, not the Add-on).
5.
Air cannot be mixed with other pure components to form a

mixture. Air must be used as the only "component" in the
component slate.
6.
Air is the only "pseudo pure fluid" supported at this time.
7.
The predefined mixtures in REFPROP are not supported at this

time.
8.
Starting with PRO/II 9.0, PRO/II is able to call the REPFPROP

flash directly.
9.
In the past users needed to obtain a license of REFPROP to be

able to use the REFROP added method sets in PRO/II. Users can
now download and install the files by requesting them separately
from PRO/II via the SimSci-Esscor Electronic Software
Distribution site.
SCHNEIDER ELECTRIC and NIST make NO EXPRESS OR IMPLIED

WARRANTY AS TO ANY MATTER, INCLUDING NO WARRANTY OR
MERCHANTABILITY AND NO WARRANTY OF FITNESS FOR A
PARTICULAR PURPOSE. THE MASS SPECTRAL LIBRARY IS
EXPRESSLY MADE AVAILABLE ON "AS IS" BASIS.
Constraints using SIM4ME Reports

The following is a List of Constraints in using SIM4ME Reports.
1.
18
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
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.
19
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 reopened, 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.
20
Important Notices
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.
Constraints using SIM4ME Portal

The following is a List of Known Defects and Constraints in using
SIM4ME Portal.
1.
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.
2.
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.
21
3.
Normal Excel operation like Cut-Paste is supported. These will

be linked parameters after Cut-Paste operation. For Copy-Paste
Operation, only the values are copied and pasted at the selected
location in the spreadsheet. However, these will not be linked
parameters.
4.
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.
5.
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.
6.
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.
7.
For the UnitOPs like Column, Controller, MVC, Splitter, etc. the
performance specifications are shown without their long
descriptions and UOM.
8.
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.
9.
What Operating System specifications do I need to have on my

machine before installing Sim4Me Portal?
Sim4Me Portal is supported on Windows 2000, 2003, XP, VISTA
and Windoows 7. Microsoft Excel 2003 Professional with SP2,
Microsoft Excel Professional 2007 or 2010is required.
10. 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
C:\Users\USERNAME\Documents\SimSci\PROII93\Applib\S4MW
22
Important Notices
orkbooks folder namely G5_Expander_Plant.xls and

G2_Deethanizer.xls.
While opening these two files for the first time, there are three
options to view these two files,:(a) Start PRO/II 8.3 application, Open the sample file, say
G5_Expander_plant.prz, Click on Sim4Me Portal Launch
andbrowse for the sample file G5_Expander_Plant.xls.
(b) Start Sim4Me Portal application in standalone mode, open
the G5_Expander_Plant.xls.
(c) Double click the sample portal files .
Apart from these, there are additional sample SIM4ME Poratl
files under
C:\Users\USERNAME\Documents\SimSci\PROII93\Applib\S4MW
orkbooks folder, namely:
- Multiple Dimulations Link_Chiller Plant - 1 and 2.xls
- Homotopy.xls
- ColumnProfile.xls
- Naphtha Assay_case Study.xls
11. (a) It does not work with security setting Very High. It can be
changed from Excel>Tools>Macro>security>Security Level
setting 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 9.3 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.
FLEXNet 11 Security for PRO/II with PROVISION with security

for add-ons.
23
TOKENnet Security for PRO/II with PROVISION with security for

add-ons.
Starting from PRO/II 9.2, a new tool called SIMSCI Security Selection
Tool is provided to change the security options without manually
editing the PROII.ini file.
You can access SIMSCI Security Selection Tool by clicking
Start > All Programs > SIMSCI License Management tool.
The security type can be changed for all the SIMSCI products at once
by selecting "All Products" from the Products Installed list box,
entering the License Servers name in the Flexlm/TOKEN License
Servers field, and clicking Apply.
UAS/PDTS Capabilities
Incompatibility of Previous UAS Versions With PRO/II 9.3
Users using the User-Added Subroutine (UAS) or PRO/II Data
Transfer System (PDTS) capabilities should compile and link their
code using the following compiler:
Intel Visual FORTRAN version 10.1 for Windows (Standard or

Professional Edition). Version 10.1 is the first version of the
compiler to be certified Vista compliant.
Other FORTRAN compilers based upon the NET 2008

architecture probably could be used as alternatives, but none
have been tested are certified for use with PRO/II.
Note: The Compaq Visual FORTRAN compiler (all versions) is not

compatible with PRO/II version 9.3.
If you previously used Compaq Visual FORTRAN:

All projects created using this tool no longer are compatible with
PRO/II. Replacement solutions and projects constructed under NET
2008 architecture for the Intel 10.1 compiler now are shipped with
PRO/II. (Compiler version 10.0 is compatible, but not compliant, with
Windows Vista.)
Static Modular UAS Projects no longer are supported.
Existing static projects must be rebuilt as dynamic projects. When
Compaq Visual FORTRAN was removed from the market users were
forced to use Intel Visual FORTRAN which became incompatible with
24
PRO/II. The older static projects existed only to allow projects

developed using the Intel compiler to function in a limited way with
PRO/II. With version 8.3 the need for static modular projects
disappeared and the static projects have been withdrawn.
New Project Files for Version 9.3 User-Added Subroutines

Older project files have been replaced by newer ones often in
different directories from 9.1 and earlier. Project files were located in
different directories, depending upon whether the were classic UAS,
newer modular UAS, or PDTS projects. The replacement locations
shown below assume (a) the Install PDTS/UAS option was active and
(b) no changes were made to the default path during installation of
9.3.
New Files for PDTS Examples
New Visual Studio Net 2008 PDTS project files are installed in the
default location:
C:\Program Files (x86)\SIMSCI\PROII93\User\Pdts\Examples\IF8
A solution file and a FORTRAN project file are furnished for each
example. For instance, example Exam1 is composed of solution file
Exam1.sln and FORTRAN project file Exam.vfproj.
New Files for Classic UAS Examples
New Visual Studio Net 2008 project files for the classic UAS interface
are installed in the default location:
C:\Program Files (x86)\SIMSCI\PROII93\User\UAS\Examples\IF8
Since classic UAS implements all additions in a single dynamic link
library, there are only two project files:
UasLb.sln Open this solution file using Visual Studio NET 2008.
UasLb.vfproj The only project in the delivered solution.
The flies listed above replace older project files previously located in
C:\Program Files (x86)\SIMSCI\PROII93\User\UAS\Examples\VF6.
New Files for Modular UAS Examples

New Visual Studio Net 2008 project files for the modular UAS
interface are installed in the default location:
C:\Program Files (x86)\SIMSCI\PROII93\User\UAS\UASF90\IVF
Modular UAS allows using a separate project for each
implementation. As delivered, version 9.3 includes two projects: one
25
for modular utilities and another for modular unit operations. The
project files include:
ExUasF90.sln Open this solution file using Visual Studio NET
2008 to build modular utilities.
ExUasF90.vfproj This is the only project in the ExUasF90
solution. It includes utilities for computing interfacial area, mass
transfer, and heat transfer in RATEFRAC.
ExUop.sln Open this solution file using Visual Studio NET 2008
to build modular unit operations.
ExUop1.vfproj The only project in the ExUop solution, this
project builds one dynamic unit operation.
All the projects listed above are dynamic. Static projects no longer
are supported.The flies listed above replace older project files
previously located in the same directory.
Source code changes required for Intel Visual FORTRAN

10.1:
PRO/II 8.3, PRO/II 9.0 and PRO/II 9.1 are built with Intel Visual
FORTRAN 10.1. Version 10.0 is compatible and may be used until
version 10.1 or a newer version can be obtained.
When upgrading older projects, please keep the following
considerations in mind.
NET 2008 uses a different run-time data structure that is
incompatible with older architecture used by older compilers.
For example, Logical File Unit numbers (LFUs) cannot be shared by
the older and newer compilers. Assume PRO/II 9.0 under NET 2008
passes 10 as a file unit to a PDTS or UAS subroutine compiled using
an older compiler. READ or WRITE statements in the UAS routine will
fail, or possibly write to the wrong file, because LFU 10 under NET
2008 is a different file unit than LFU 10 using an older compiler.
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 the PDTS application or
UAS. To avoid problems, the utility subroutine PAWRITE has been
26
provided to allow your application to write output to an external file.

The following code fragments illustrate the required changes:
Original PDTS example:
CHARACTER(LEN=8) :: NAME
...
1001 FORMAT(Enter File Name )
1002 FORMAT(A)
1003 FORMAT(Data Reported for File = , A10)
WRITE(*, 1001)
READ(*, 1002) NAME
.
CALL PAOPEN (NAME, , NFOUT, IRCODE)
WRITE (NFOUT, 1003) NAME
Modified PDTS example using PAWRITE:

CHARACTER(LEN=8) :: NAME
CHARACTER(LEN=133) CHARDATA
...
1001 FORMAT(Enter File Name )
1002 FORMAT(A)
1003 FORMAT(Data Reported for File = ,A10)
WRITE(*, 1001)
READ(*, 1002) NAME
.
CALL PAOPEN (NAME, , NFOUT, IRCODE)
WRITE (CHARDATA, 103) NAME
PAWRITE (NFOUT, CHARDATA)
Note the modified code does not directly write the output to the file
unit number NFOUT. Instead, it writes the output to a character
variable; then calls the utility subroutine PAWRITE() that tells PRO/II
to write the contents of the character variable CHARDATA to file unit
number NFOUT.
Original UAS example:
SUBROUTINE USER42(IPARM,RPARM,SUPPLE,HEAT,IDATA, &
ISOLVE, ISTOP )
...
CHARACTER*12 CID
27
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 to use PAWRITE:

SUBROUTINE &
USER42(IPARM,RPARM,SUPPLE,HEAT,IDATA,ISOLVE,ISTOP)
..
CHARACTER(LEN=12) ::CID
CHARACTER(LEN=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
28
Running PDTS Applications

Note: If you call subroutine FIGETU to get a file 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 file input/output is accomplished within code compiled
by the same compiler.
PDTS applications are designed to execute in a virtual DOS
environment from a Command prompt. When 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
To run PDTS applications, it sometimes is necessary to add
additional directories to the system 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, located in
the user directory. That command file modifies the PATH of the
current Command Prompt session to enable running PDTS
applications in that Command Prompt session.
If you start a second Command Prompt session, then you will need It
may be necessary to execute the setPDTS.bat batch file in each
Command session that you open.
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.
29
Where to Find PRO/II 9.3 Documentation

Printed Documentation Included with this Package
Release Notes for PRO/II 9.3 (this document)
Online Documentation
PRO/II User Guide
PRO/II 9.3 Reference Manual
SIM4ME Portal User Guide
SIM4ME Reports User Guide
TDM User Guide
PRO/II Keyword Manual
PRO/II Getting Started Guide
PRO/II Casebooks
PRO/II Application Briefs Manual
PRO/II LIBMGR and COMPS Users Guide
Data Transfer System Users Guide
User-Added Subroutines Users Guide
PRO/II Interface Modules Users Guide
SIMSCI Component and Thermodynamic Data Input Manual
AMSIM USER MANUAL
PRO/II Ternary Mixture Plots
PRO/II Electrolyte User Guide
OLI Chemistry Wizard 9.1.3
PRO/II Polymer User Guide
SIM4ME Thermo REFPROP Thermo Addon Release Notes
PRO/II COM Server Reference Guide
OPC Unified Architecture Server
PRO/II COM Server Programmers Guide and Tutorial
Note: The PRO/II Welcome screen for the online documentation can
be found on the hard drive under the simsci\proii93\Manuals directory.
30
Where to Find PRO/II 9.3 Documentation
Summary of Defects Fixed in PRO/II 9.3

Feature
Bug Number Description
ACE
LFPE#29335
The PRO/II Air cooler specifying fixed weight air as

a utility stream gives incorrect results. Each time
you click run you get a different answers.
HIPE#22573
In the ACE unit, the Fan Power option should always

be disabled if air is a process stream, and always
enabled if air is a utility stream. That's not
happening.
ACE/HTRI
LFPE#29337
HTRI v7.0 ACE doesn't work through PRO/II.
AMSIM
LFPE#28748
On some PC's, creating an Amsim file from scratch

using AMP results in error message from PRO/II
that AMP is not found.
Assay
LFPE#29174
A TBP curve with sparse number of points (typically

less than 5) may result in a bad petro component
breakdown.
HIPE#22481
Changing the Heat of Formation method in the

Global Defaults is not immediately reflected in local
Heat of Formation options.
LFPE#29767
Adding a component to the component list higher

than the highest boiling assay petro component will
cause the EP of the stream to change. Adding a zero
rate component should have no impact on the assay
curve.
Batch Distillaton
HIPE#22634
In Batch Distillation, open Report Times window

and check off "Output at Additional Times", then
close all DEW by OK button. Returning to the
Report Times Window, the default frequency may
be populated with junk values. If so, the Batch
Distillation will no longer converge.
Calculator
LFPE#29698
The Calculator does not assign a rate=0 for a

reference stream using SRXSTR. A rate of 0.001
works OK. Assigning rate=0 for a conventional
stream works OK.
HIPE#14517
Calculator fails to execute complex assignment

statement
V(M) = MAX(V(M), ABS(V(I)))
but
V(1) = MAX(V(1), ABS(V(2)))
does execute.
31
Feature
Cape Open
Colunm
32

LFPE#29854
In a file using the OPEN command in the Calculator,

similar to
OPEN(FILE=TEST,OVERWRITE)
works OK. File TEST.CAL gets created in the user
working folder.
However,
OPEN(OVERWRITE)
does not create the filename.CAL file as expected.
HIPE#22584
When a Cape Open unit op creates a stream on a

mass basis, it is not being converted properly to
mole basis for the PRO/II Stream Property Table.
LFPE#29761
Renaming or File Converting a .prz file may cause

an unit operation with a CO HTRI file to fail. When
the internal names are changed, the .dat file is not
renamed.
HIPE#22844
The CapeOpen persistance file (.dat) may be

deleted after accessing the .prz from p2oledbs.
LFCR#3530
Sure column has decant water mixed into the tray

property data, but EIO does not. The EIO is
expected to have the same behavior as Sure.
LFPE#29016
Adjusting the tolerance on the Ratefrac column

does not appear to have any effect on solution.
HIPE#22240
After reopening a file that has a column with two

liquid phases, closing and reopening the file causes
the two liquid report to disappear.
LFCR#4960
Sim4Me Reports places the column feed tray at the

initial input position, not the final position after the
optimizer changed it.
HIPE#22487
Retrieval of component flows in a column using

COM, in the presence of both standard and
electrolyte components sometimes gets the
component rates assigined to the wrong
components.
LFPE#29685
Using a water decant thermo in the main

fractionator (such as SRK) and a non-decant
thermo (such as SRKM) in the side-stripper causes
a switch on component labeling. For example, a
component rate of water can be labeled as C2H6S2
in the product stream.
HIPE#22557
Sure column using an API gravity in the reference

part of a spec didn't work right - wouldn't converge
when it should have.
LFPE#29728
Trace components can disappear going through the

IO column.
Feature

HIPE#22597
Spreadsheet tools weight rate report for electrolyte

distillation is incorrect.
LFPE#29794
After File Converting to v9.2.2, a file with inactive

spec on column generates an abort on output
generation.
HIPE#22556
A Column Specifications using sulfur refinery

inspection property sometimes does not persist
after entering the data through the GUI.
HIPE#21167
Calculated heat of formation data for sulfur is

wrong.
HIPE#20633
For component C12ALD (1-DODECANAL), enthalpy

values from PROCESS library bank method is far
away from SIMSCI library method and extrapolation
beyond applicability limit gives flat enthalpy curve
with temperature change.
LFCR#5088
The heat of formation OLEIC and LINOLEIC in the

SIMSCI library is incorrect.
LFPE#29772
Sucrose is designated as a VL component in the

SimSci databank. There are solid properties
available. It should be VLS.
HIPE#22649
The MW of OCBUTRAT is wrong in the SIMSCI

databank.
HIPE#22789
Dowtherm G component has a maximum

temperature for temp-dependent property
calculation which is higher than it's critical
temperature in Simsci databank.
LFPE#29037
Pressures retrieved from a Compressor and into a

Calculator are not cleared to "Missing" after ctl-R.
HIPE#22640
Entropy values are missing in compressor output

for some files opened from prior versions in v9.2.2.
LFPE#29959
When a single MW curve is given on the multiple

MW curve grid, the feed stream is passed on
through to the product stream without any
compressor calculation made.
Containerize
PRZ
HIPE#22663
The Pipephase unitop link to PPZIP file generates a

containerization error when the file name is
changed for the PRO/II.prz file. This occurs if the
file name is changed from Windows Explorer, or
from the PRO/II File/Save As command.
Copy/Paste
LFCR#5055
Copy/paste of petroleum components to Excel

causes the MWs to be pasted twice, and the names
not at all.
HIPE#22601
The Normalize Composition is always checked after

a copy/paste of stream, regardless of whether the
source stream has that option checked.
Component
Component
Databank
Compressor
33
Feature
Depressuring
HIPE#22576
The Depressuring initial vent volume rate is

reported as n/a in the Unit Op Property Table when
it should have a calculated value.
HIPE#22662
Depressuring calculations doesn't consider the

wetted area input by user when liquid height is also
supplied. The inputted wetted area should get
priority over calculated wetted area.
HIPE#22730
Depressuring with decant thermo and all liquid in

the vessel fails to converge. Same thermo without
water decant works fine.
LFPE#29856
In a depressuring unit using the Orifice Flow model,

a discontinuity occurs with the change in type of
flow (from sonic to subsonic)in the
depressurizations profiles.
HIPE#22359
Opening a .prz that points to an OLI .dbs file in the

wrong location, then Browsing to point to the right
location, may result in a component slate that has
an incorrect last component, and that the databank
hierarchy may be wrong. Export, edit the file pointer
so that it looks for the .dbs file in the local directory,
clears the problem.
HIPE#22498
A Visual Basic error is thrown when we try to

generate a component rates spreadsheet for an
electrolyte file.
LFPE#28976
Starting with v9.1.1, pure component hydrocarbons

defined by OLI MSE thermo are assigned vapor
phases when they should be liquid.
LFPE#28021
The Ionic strength for Aqueous OLI thermo is on a

weight basis, and thus higher than expected. MSE
OLI thermo is on a mole basis as expected. These
numbers are reported directly from the OLI engine.
LFPE#29916
An Excel unit operation when run during a

simulation will close other Excel sessions open in
the flowsheet without saving them.
Electrolytes
ExcelUaUOP
34
Feature
Export
LFPE#29749
Having a UAUOP product named FEEDxxx results in

an exported keyword file with bad syntax:
UAUOP(EXCELUOP,20000) UID=700-L
SIDE(1) FEED=550,
PROD=SWEETSYN,CO2,ACIDGAS,PURGEWA,LPVP
CO2, &
FEEDKO
where FEEDKO is interpreted as another FEED

keyword instead of a product stream. FEEDKO
should be allowed as a product stream ID.
LFPE#29140
Export drawing to clipboard and paste to Excel does

not always reveal the entire drawing.
File
LFPE#29852
PRO/II leaves working folders behind in the TEMP

folder if you select opening an old file with the old
version. This eventually results in a large
accumulation of P2_xxxxxxx folders.
Fired Heater
HIPE#22702
Once the Fired Heater Wall Temperature

specificationm checkbox is checked, it is always
comes back on even after it is checked off.
Flash
LFPE#29730
Glycol-HC flash does not consistently predict two

liquid phases.
LFPE#29741
A stream using EOS water solubility near critical

conditions misidentifies the water stream as vapor
phase.
HIPE#22625
In one case, using NIST thermo and PRO/II default

flash results in a liquid phase designation for a
stream that should be vapor. Switching to NIST
flash generates the correct phase.
LFPE#29853
Some streams generated bad Stream Property

tables when run with the Run & Output calculations
button. Not thta thte Run Only button and the Run
plus Generate Report work fine.
LFPE#29950
VLLE flash using SRKM with GAO fill at high

pressure may result in wrong phase designation of
the products.
LFPE#29368
Heating Cooling curves with pure water vapor

streams don't display the thermodynamic
properties paragraph.
LFPE#29838
On some machines, the spreadsheet tools for

Heating-Cooling curves had column headers placed
in the wrong columns.
HCurve
35
Feature
HTFS Interface
LFCR#5045
The HTFS interface is getting an order of magnitude

error in thermal conductivity in the .psf file, using
W/m*K, instead of kW/m*K. Also, values that are
missing are written out as 0.000 rather than *.
HTRI/HTFS
HIPE#22555
Cp in the HTRI/HTFS Spreadsheet tools is incorrect

for VLLE thermo.
LFPE#29836
Spreadsheet tools for HTRI/HTFS is reporting the

wrong weight flow from a heating-cooling curve
attached to an LNGHX unit operation.
HIPE#22372
The Chen HTC calculation can generate incorrect

results.
LFPE#28796
In one case HXRig convergence of kettle steam

boiler is unreliable - comes up with a different duty
each run pass.
HIPE#22337
Access to HTRI 7 from PRO/II hangs on XP

machines.
LFPE#29696
After browsing for the .htri file and using it in a

simulation, it fails to be archived into the .prz file
and isn't available on reopen.
Hydrate
LFPE#29605
Hydrate curve plot is sometimes missing a data

point available in the tabular result. The result is a
discontinuous appearance in the plot which doesn't
actually exist in the calculations performed.
Hysis Translator
LFPE#29433
Import a particular Hysys .xml file and it crashes at

70% completed.
HIPE#22473
PRO/II may shut down when importing a Hysys file

on Japanese OS.
LFPE#29598
Hysys flashes with no pressure designation get

translated into P=0 in PRO/II. This causes errors.
Should be DP=0.
LFPE#29694
Various Hysys translator issues.
LFPE#29875
On some machines, File/Import on files with 5

characters or less in name causes OxC014000f
crash.
LFPE#29453
Keyword import of file with Pour Point data may

crash.
Language
Customization
LFPE#29542
Repair from Programs and Features may cause the

security type selection to change.
OLE
LFPE#29847
COM calls to GetObjNames is slow.
Output
HIPE#22251
The Refinery Inpsection Properties Heating Value is

confused with the conventional gas GHV and NHV.
The RIP method is valid for refinery liquids such as
naphtha. The property should be renamed to Heat
of Combustion.
HXRig
HXRig/HTRI
Import
36
Feature

HIPE#22720
Run the A2 applib file and generate the Excel

Output. You will get an "Abort. No slots available
message" in the messages window, however the
Excel report comes up fine and you can continue to
run PRO/II with no problems.
PFD
LFPE#29422
Opening up a file with a corrupt graphics file could

result in the 100% sizing button to push all the
visible flowsheet off the view port leaving the screen
apparently empty. In this case the stream property
table has a draw frame that is vastly larger than the
actual stream property table. (Note that for v9.2.1,
the likely source of this corruption was fixed, but
opening up old files will still result in this problem).
Pipe
HIPE#22133
A pipe unit with a large number of segments

crashes. For example, 50 segments might work
while 100 segments might crash.
LFPE#29753
In a flowsheet with inactive column specs, adding a

pipe to the working flowsheet causes the flowsheet
to crash on run.
HIPE#22794
Single phase stream in Pipe unit operation with

more than 20 segments may report "annular" flow
regime when it should report "single phase"
LFPE#29583
The Pipe unit operation gets inconsistent results for

streams with high H2 content and a trace of liquid.
LFPE#29316
Output/Launch PES Products currentversion

doesn't work.
LFPE#29588
A single Pipephase RPARM parameter is not visible

to the Spec/Vary/Define system, but becomes
visible if you have two RPARM's.
LFPE#29593
When a controller is used to vary/spec an attribute

in a Pipephase Unit Operation, opening the
Pipephase Unit and closing it again results in a
message that the links are disconnected.
HIPE#22648
Pipephase unit operations with a "." in the UID name

(which should be allowed), will result in a ".zip not
found error."
Pump
LFPE#29974
The combination of 100% efficiency and solids in

the pump feed results in 65% efficiency being used.
Reactor
LFPE#29765
An equilibrium reactor with multiple stoichiometric

equations can give a non-sensical "converged"
result.
LFPE#29812
Reactor reference state enthalpy is wrong for very

low vp streams.
LFPE#29864
Label for Procedure Data variables in PFR do not

persist.
PPIntegration
37
Feature

HIPE#22651
CSTR reactors using power law and fugacity

activity, and using non-SI units, may encounter a
UOM conversion problem and calculate the wrong
reaction rates.
LFPE#29948
In some files with a large number of reactions and/

or reacting components, it's possible for inerts to
react in the equilibrium reactor.
Recycle
HIPE#22603
A file with more than 100 recycle loops gets an

abort on Run.
Regress
HIPE#22574
PRO/II regression analysis is not being printed out

in the .out file.
Security
LFPE#29509
The License Manager tool as delivered in v9.2

doesn't work on some European OS due to comma
decimalization. OS's where the period is the decimal
works OK.
Sequence
LFPE#29568
In one case, importing a file gets an incorrect

recycle message:
*** ERROR *** RECYCLE STREAM S41 FROM
UNIT 141 M19 TO UNIT 155 HC2 IS NOT
INCLUDED IN ANY RECYCLE LOOP
When PRO/II generates its own sequence there
should be no such recycle stream.
SIM4ME Portal
38
LFPE#29554
In one case the sequencer misplaced the outer MVC

so that there were unnecessarily nested calculation
loops.
LFPE#29323
A very long path name (> 200 characters) causes

the Portal to crash when creating the file.
HIPE#22325
Sim4Me Portal: LNG & Gibbs models do not show

User Input data as blue items in the flowsheet
explorer.
HICF#3460
A portal file with a very large number of messages

takds an excessive amount of time to open.
LFPE#29577
Spiral components regeneration through the Portal

do not clean the old components correctly and
Sulfur Content (RIP) results are wrong.
HIPE#22369
A particular portal file loses links when migrated

from earlier version to P2 9.2.2. It will appear to
open fine, but after a number of rows the attribute
links are lost.
LFCR#3924
Sim4Me Portal doesn't link correctly with PI data

historian after initial opening from PRO/II.
Feature

HIPE#22716
In Chinese W7 with Chinese MS office, Sim4Me

Reports fails to display the header text in the
Summary and Detailed Report tabs. It appears that
the grid is empty.
Solids
HIPE#22516
The solid removal unit operation doesn't work when

there are a large number of (> 50) components.
Spec Vary
Define
HIPE#22395
The depressuring vessel weight is available as a

spec in Defines of Depressuring unit and the
Calculator. The default UOM is a weight basis (KG).
OK to PFD and revisit changes to mole bases
(KGMOL).
HIPE#22552
Specify an Adjusted Standard Flowrate in the Spec

Vary Define, and revisit that same DEW and it will
be restored to standard flowrate.
LFPE#29717
Precision isn't fully retained for data entered in

Spec/Vary/Define system. A spec entered as
10,000,001 gets truncated to 10,000,000.
LFPE#29779
Spec/Vary/Define retrieves Pipe Outlet Velocity

when Pipe Average Velocity was requested.
HIPE#22646
Stream link doesn't transfer non-library solids

flowrate data in a flowsheet.
LFPE#29868
Update Initial Estimates and Paste Special of

streams with solids leaves the input stream objects
with bad or unusable data.
HIPE#22836
Tool tip for streams with zero flow may show some
unexpected, non-zero results.
HIPE#22528
The stream calculator might not correctly predict

phases of the stream as displayed in the Stream
Property Table when LS components are present.
Also, compositions of solid components might be
displayed wrong with fractions > 1.0.
LFPE#29923
When adding a component to the component list

and a Stream Calculator uses a spec range that
brackets this new component, the run button turns
red but there is no indication that the Stream
Calculator has a problem in it.
LFPE#29379
Large Stream Property List collections may get

corrupted and lead to a crash. You can usually spot
the bad list by seeing attributes listed in nonsequential order in the sprop.ini file. Deleting that
particular list fixes the problem.
HIPE#22385
After selecting a large Stream Property Table and

some unit operations, Copy/Paste to duplicate the
selection causes PRO/II to hang.
Stream
Stream
Calculator
Stream Property
Table
39
Feature
40

LFCR#5028
PRO/II allows the user to include comma "," into the

name of Stream Property Table lists. On export with
SRW active this gets written verbatim into a
FORMAT statement, and "," is interpreted as a
delimiter instead of part of the name on import. ","
should be disallowed as a SPT List name.
LFPE#29718
Creation of Stream Property Table Lists with name

"[" causes error on use. "[" and "]" should be
disallowed as Stream Property Table List names.
LFPE#29821
v9.1 and earlier files with Stream Report Writer

Names with "&" in them do not File Convert to v9.2.
LFPE#29900
There is an inadequate labeling of "standard" or

"actual" in volume and densities in the Stream
Property Tables.
HIPE#22779
In some cases, the liquid viscosity derived from

kinematic viscosity is not displayed in the Stream
Property Table even though kinematic viscosity and
density are calculated.
LFPE#29951
Some values reported in a Stream Property Table

retain values from the previous run even though the
stream rate has dried up to 0.0.
Stream Report
Writer
LFPE#29310
A group of petro components displayed in SWR rate

does not include all the required components. The
rate of the first component is not included.
Thermo
LFPE#29525
PRO/II can Fill NRTL parameters and get different

results if one of the components is VLS compared
to VL. They should generate the same results.
LFPE#29448
Peneloux-SRK density with NIST k-values results in

"unsupport feature" error. Should be accepted.
HIPE#22458
PRO/II fails to calculate transport properties using

Heavy Oil methods in the presence of solids.
HIPE#22609
Isentropic flash calculations sometimes don't work

with NIST thermo when they should.
HIPE#22707
Import a file using solid components and BWRS

thermo may throw an exception.
LFPE#29977
Lohrenz-Bray-Clark (LBC) liquid viscosity is

disabled above Tr = 1. It should be valid at any Tr.
HIPE#22551
In some cases for temperature dependent

properties, typing 0 for a correlation parameter
does not persist upon reentry.
HIPE#22784
Using NRTL and PHSC fugacity, pure component

thermo-specific data entered does not persist.
Feature

LFPE#29952
Water solubility using Wichert does not extrapolate

beyond the Wichert chart temperatures. This
unnecessarily causes bad water vapor pressure
above the temperature.
UaUOP
LFPE#29585
There is an internal vs. external component

ordering problem in the UAUOP. You can correct it
by designating all the components as VL.
UOM
LFPE#29690
File import with pressure units of MPAG changes

the value of the pressure. For example, pressure
changed from 0.0099913 MPAG in the .inp file, to
0.0099883 MPAG in the .prz file. MPAG is the only
pressure units with this problem.
LFPE#29896
When importing a file and pressure is set to BARG,

values entered for standard state pressure get
shifted. Repeated export/import causes a standard
pressure state "drift".
HIPE#22738
General improvements on phase designation three

phase flashes with high pressure streams when
user-added subroutines are used for thermo.
User Added
Subroutines
41
Summary of Defects Fixed in PRO/II 9.2 Patches

Feature
Bug Number
Description
ACE/HTRI
LFPE#29330
ACE isn't working in v9.3 with HTRI v7.0.
Assay
LFPE#29350
A keyword file with a large number of assay

streams gets a "No slots available" abort on
import.
LFPE#28025
Petro components stored in .lb12 files via TDM

cannot be used in PRO/II when pure component
average transport is used. You get messages
similar to "Liquid thermal conductivity correlation
data is required but missing for component 4."
HIPE#22481
Changing the Heat of Formation method in the

Global Defaults is not immediately reflected in
local Heat of Formation options.
LFPE#29567
The rules changed for persisting calculated petro

component attributes depending on which values
the user overwrote. There is a difference in
behavior incurred when using defaults compared
with visiting the DEW and OKing without changing
anything. That's wrong. For example, enter the
petro data of 70 API and 300 F. On export you
correctly get: Now enter the Component/Fixed
Properties DEW and OK out of the DEW without
changing anything. Now you get: PETRO
1,,,70,300.PETRO 1,,129.454,70,300 In other
words, the MW is now hardwired. This is wrong.
LFPE#29592
Assay display on View Curve of assay DEW does

not show lightends even when lightends is
specifically requested.
BVLE
LFPE#29362
BVLE calculations for H2O/NH3 using Refprop

results in strange results for 0.0 < X(H2O) < 0.15.
Standalone flashes give the right answers. TDM
BVLE charts give the right answers. Using SRK
gives the right answers.
Cape Open
HIPE#22420
The Cape Open .dat files are not being archived

into the .prz file. Depending on the Cape Open unit
operation calculated data may not persist between
PRO/II sessions.
HIPE#13962
The default CapeOpen GUI doesnt support option

parameters. Gives misleading warnings.
HIPE#21246
HTRI via PRO/II/Cape Open doesn't work when

the HTRI install is done under a different user
name from the execution.
HIPE#21198
Case Study doesn't run the first time after View

Results of any stream. Subsequent runs work
fine.
Case Study
42
Feature
Column
Component
Controller
Copy/Paste
Bug Number
Description
HIPE#22480
Adding a parameter related to a side-column in

Case Study and run the file may result in an
exception.
HIPE#22195
VLLE check doesn't work on sub-cooled

condensers.
HIPE#22202
Chemdist Reactive Distillation will converge with

conversion set to an infinitesimal amount, but
fails to converge when set to zero. The results
should be essentially the same.
HIPE#21779
The specific tray efficiencies that are not specified

by user are not calculated correctly when DEFINE
is used.
LFPE#29250
SURE column with reflux ratio spec solves to the

right value but reports a reflux ratio of 1 in the
spec summary.
LFCR#4960
Sim4Me Reports places the column feed tray at

the initial input position, not the final position after
the optimizer changed it.
LFPE#29628
When you have a combination of conventional

thermo and electrolyte thermo, it's possible for
attributes listed in Component Properties DEW to
be offset by one or more rows so that the wrong
attribute is printed to each component below that
point.
LFPE#29421
Export with cascaded pure component properties

fails to write the "CASCADE" keyword for the first
group of LIBIDs. When reimported the
components in that first group may not pick up all
the properties it needs, and the import may fail
due to missing properties.
LFPE#29331
Copy and Paste buttons don't do anything on the

Petroleum Components DEW.
HIPE#22087
Particle Size Distribution information for stream is

not reported correctly in the P2Viewer.
LFPE#29514
Adding components off the DIPPR list may cause

a Databank component creation error.
HIPE#22106
In one case, with the controller set to meet an

impossible specification, rather than detecting
that the spec wasn't moving, PRO/II bracketed the
solution and declared it solved.
HIPE#22478
The specification on reflux ratio loses its WT basis

on export. Thus, on import the specifcation now
has a mole basis.
LFPE#29392
A water stream from a Shortcut Distillation unit

fails to be accounted for in testing for duplicate
streams.
43
Feature
Data Review
Window
Bug Number
Description
LFPE#29307
Copy / Paste Special does not copy Non-MW

components (Char, Ash, Coal).
LFPE#29159
Precision in the Data Review Window (DRW) is

only the display precision. After UOM conversion
where more figures are displayed the values are
imprecise.
LFPE#29414
The Data Review Window (DEW) doesn't support

cm3 as the denominator for density (as in g/cm3).
A stream that has gravity of 0.999 g/cm3 is
displayed as 999 g/cm3 which is incorrect.
HIPE#20966
Values for Molar & Mass concentration don't

change in the Data Review Window (DRW) when
switching from one to the other.
HIPE#22273
The Data Review Window displays distillation

curves incorrectly.
IBP -38.39943804
5% 36.82176512
10% 94.5658547
in the Stream Property Table becomes:
-38.399 F
36.822 F
94.566 F
in the DRW.
Depressuring
Electrolytes
Export
44
HIPE#22310
With a freshly built depressuring simulation

(from File/New), after running, the Generate Plot
function crashes PRO/II. This works fine after File/
Import.
LFPE#29625
Wall temperature plot in depressuring unit is flat

vs. time for fired heat models.
LFPE#29516
In one case PRO/II executed a simulation despite

missing a required OLI .dbs file.
HIPE#22359
Opening a .prz that points to an OLI .dbs file in the

wrong location, then Browsing to point to the
right location, may result in a component slate
that has an incorrect last comonent, and that the
databank hierarchy may be wrong. Export, edit the
file pointer so that it looks for the .dbs file in the
local directory, clears the problem.
HIPE#22498
A Visual Basic error is thrown when we try to

generate a component rate spreadsheet for an
electrolyte file.
LFPE#29333
Compact/Repair after a Pause causes a crash.
Feature
Bug Number
Description
File
LFPE#29405
File/Open from the menu and/or the File/Open icon

fails to open the File Open dialogue. ctl-O always
works. Seems to happen most often (but not
always) on Vista and W7 machines. On machines
with the problem, when you successfully open the
file-open dialogue it pre-populate the file field with
junk characters instead of the normal *.prz, *.pr1.
LFPE#29334
A sequence of events using Compact/Repair

followed by an Export/Import causes the working
directory to be deleted.
LFPE#29555
Using BWRS in cryogenic valves and flashes may

require multiple Runs to solve. SRK works OK.
LFPE#29611
In some cases, PRO/II fails to identify the stream

label on a feed stream flash error message.
LFPE#29615
The phase designation for a particular high

pressure flash was incorrect using the Alternate
Flash algorithm. the LFPE#28916 fix made to
Default Flash algorithm needs to be ported to
Alternate Flash.
LFPE#29465
The phase designation of a hydrocarbon product

near critical in a VLWE calculation can be
influenced by the amount of excess water
present.
LFPE#29349
A flash calculation with user Henry's constants

sometimes fails.
HIPE#22467
After a Restore Input action, the Generate Plot still

creates plots with old data in it from before the
Restore. Once Input is Restored, that data used
for the plots are no longer valid and should be
cleared.
LFPE#29581
The liquid Cp is not displayed in Sim4Me Reports

for single phase liquid streams using the HCURVE
unit operation.
LFPE#29368
Heating Cooling curves with pure water vapor

streams don't display the thermodynamic
properties paragraph.
HX
LFPE#29614
An HX unit in a file with electrolyte and standard

thermo is reporting a bad hot side product
temperature.
HXRig/HTRI
HIPE#22337
Access to HTRI 7 from PRO/II hangs on XP

machines.
Hydrate
LFPE#28862
The hydrate curve for 20 wt% MeOH shows

adiscontinuity at (in the sample case) 43 bars
jumping from -15 C to -5 C.
OLE
LFPE#29675
The OpenDataBase method fails when the same

method worked earlier on.
Flash
HCurve
45
Feature
Bug Number
Description
PFD
LFPE#29629
Importing a file that creates a Stream Property

Table with more than 12 streams may cause the
main flowsheet to appear to be blank. It's a sizing
and centering issue - if you scroll around you can
find the flowsheet.
Reaction Data
HIPE#22224
CSTR Reports incorrect conversion when order of

reaction is different from it's stoichiometric value.
Reactor
LFPE#29508
The Reaction Approach Fraction first parameter is

not allowed to have a value greater than 1.0, but
there is no reason why an approach to equilibrium
can't be greater than 1.0 (in other words, the
reaction can be specified as going past its
equilibrium point).
LFPE#29466
Streams with LS components come out of the

reactor with altered flowrate even though those
components ware not part of the reaction.
LFPE#28212
The equilibrium reactor may come to an incorrect

solution with a large number of reactions and
components. Reduce the number of reactions and
the answers are good.
LFPE#29338
Duty set to zero in a conversion reactor is

interpreted as 'missing' during recycle.
HIPE#22145
Add a user-defined component may result in the

Gibbs reactor not being updated correctly.
HIPE#22199
The conversions calculated by CST and PF

reactors are incorrect when the base component
stoichiometric coefficient is not the same as the
order of component.
HIPE#22593
Adding a petro component to a Gibbs Reactor

causes a crash.
LFPE#29409
Blending of components with "missing" for RIP

are unconditionally blended in as "0". If the
blending option is "missing", the result for the bulk
stream should be "missing".
LFPE#29230
Real Data and Integer Data for Refinery Inspection

Properties are not written to keywords. Reimport
and the data is gone.
Security
LFPE#29459
A .dbs file created using SimSci limited electrolyte

databank requires the full OLI access electrolyte
license to run. It should require only the limited
license.
Sequence
LFPE#29565
In one case, importing a valid file generated the

error message: *
Refinery
Inspection
Properties
** ERROR *** RECYCLE STREAM 1175B FROM

UNIT 121 E301B TO UNIT 121 E301A IS NOT
INCLUDED IN ANY RECYCLE LOOP
46
Feature
Bug Number
Description
LFPE#29500
A file containing a user supplied sequence

generated a bogus sequence error message:
*** ERROR *** RECYCLE STREAM S406 FROM
UNIT 169
E2284-V TO UNIT 157 F1_CLV IS
NOT INCLUDED IN ANY RECYCLE LOOP"
SIM4ME Portal
LFPE#29451
Changing sequencer from user-defined to

Minimum Tear Stream, and then later back to user
defined can cause one of the units to be
duplicated on the list.
LFPE#29577
Spiral components regeneration through the

Portal do not clean the old components correctly
and Sulfur Content (RIP) results are wrong.
SIM4ME Report LFPE#29309
Sim4me reports doesn't work in Japanese OS

when logged in as a normal user.
HIPE#22485
Custom Sim4Me Reports are not avaliable in

"select active report" drop down list until the
flowsheet has been saved at least 2 times.
Spec Vary
Define
LFPE#29576
When duty is given as a variable, the limits are

multiplied by E6 every time you OK the DEW.
Spreadsheet
Tools
HIPE#22303
Spreadsheet tools fails when launched from

SRIRPT.xls.
HIPE#22249
Some of the Spreadsheet Tools fail to launch after

launching the Portal.
HIPE#21674
In the Ternary Plot feature, changing the axis

doesnt affect the singular point.
LFPE#28830
On rare occasion, double clicking on a stream fails

to open that stream.
HIPE#22434
Stream results are displayed after an export/

import or repair. These functions reinitialize the
flowsheet and therefore the stream results should
also be reinitialized.
LFPE#29181
A file with a large number of Stream Property

Tables eventually hang.
LFPE#29365
After running a file for perhaps 20 seconds, pause

execution, and then click on stream search button,
you can get an exception.
HIPE#22528
The stream calculator might not correctly predict

the phases of the stream as displayed in the
Stream Property Table when LS components are
present. Also, compositions of solid components
might be displayed incorrectly, with
fractions > 1.0.
Stream
Stream
Calculator
47
48
Feature
Bug Number
Description
Stream
Property Table
LFPE#29497
Using a non-electrolyte thermo on a SPT designed

for electrolyte thermo causes values to be printed
out on the wrong rows.
LFPE#29473
A file using a Stream Property List with Latent

Heat crashes while generating the Stream
Property Table.
LFPE#29498
Deleting an electrolyte thermo set will delete the

apparent components from the stream reports,
but does not delete the electrolyte species from
aqueous report.
Tags
LFCR#5046
Compact/Repair does not export/import tag data

and thus the file is incomplete after that operation.
Thermo
HIPE#22373
Entropy is not calculated for a stream which has a

component from a user databank with CORR=24
for ideal gas enthalpy.
HIPE#22419
Thermal conductivity is not being communicated

from IF97 water to PRO/II. Unit operations that
need it (like HTRI) can fail.
HIPE#22459
With Hayden-OConnell method for vapor

enthalpy, density, fugacity and entropy, enter the
component properties DEW results in a crash.
LFPE#29406
The range check for acentric factor for BWRS at

the Thermo-set specific component property level
is incorrect and traps out values that should be
OK.
LFPE#29483
Bromley-Wilkes vapor viscosity for low

temperature C1 is incorrect.
LFPE#29416
Vapor phase properties for some electrolyte

streams are reported as N/A. After you separate
the same stream using a flash drum the vapor
phase has the properties reported. They should
have been reported for the feed stream too.
LFPE#29380
The presence of a non-lib component causes the

Flash Point calculation to be disallowed.
LFPE#29407
Having a second thermo system in the file causes

NIST transport properties not to be calculated.
LFPE#29395
A1 through A11 BWRS properties for binary

interactions are sometimes reported as
"calculated" even though they were read off the
databank.
LFPE#29394
Reprint of critical values for thermo-specific

BWRS pure component properties were wrong.
They had wrong UOM conversions. The values
included Tc,Vc, and acentric factor.
Feature
Bug Number
Description
HIPE#22127
The reported C and H do not exactly match the

reported C/H ratio in some cases.
HIPE#21979
The TBC equation of state never uses the LLE Data

for calculations.
LFPE#28531
In one case, a file with non-library components

crashed on reopen. Occurs on XP only. Windows
7 is OK.
LFPE#29336
Gauge pressure with ambient pressure offset is

wrong on import.
LFPE#29390
The user-entered value for Standard Vapor

Volume does not persist if focus is gained on Std
Temp or Std Pres.
User Added
Subroutines
HIPE#22243
The Check Solid Unit Operation calculations are

bypassed when execution control is set to Output.
View Results
HIPE#22025
L1/L2 Phase separation is not reported correctly

in stream View Results for one case. All of the
contents are reported in L1.
UOM
49
Summary of Open Defects in PRO/II 9.3

PRO/II 9.3 Bug Lists
To access the current version of PRO/II 9.3 bug list as well as FAQ
and Updates, visit our website's Knowledge Base at http://
www2.simsci.com/sim4me/esd/login.asp. Enter your personalized
SIM4ME Username and Password. Select Software Updates &
Knowledge Base and then PRO/II.
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.
50
Summary of Open Defects in PRO/II 9.3
License and Copyright Information

Release Notes for
PRO/II 9.3
The software described in this guide is furnished under a

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
2014 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
Invensys, Invensys logo, HEXTRAN, INPLANT, PIPEPHASE,

PRO/II, Provision, SIM4ME, and SimSci-Esscor are
trademarks of Invensys plc, its subsidiaries, and affiliates.
All other brand names 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. (a division of Invensys plc. and owner of the SimSciEsscor brand) 26561 Rancho Parkway S., Lake Forest, CA
92630, USA.
Printed in the United States of America, February 2014.
51
52
License and Copyright Information
Invensys Systems, Inc.

26561 Rancho Parkway South
Lake Forest, CA 92630
United States of America
http://iom.invensys.com
Global Customer Support

Inside U.S.: 1-866-746-6477
Outside U.S.: 1-508-549-2424 or contact your
local Invensys Representative.
Email: Invensys.iom.support@Schneider-electric.com
Website: http://support.ips.invensys.com

PROII93 ReleaseNotes

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

PROII93 ReleaseNotes

Transféré par

Droits d'auteur :

Formats disponibles

SimSci

9.3 Important: Read First

Where to Find PRO/II 9.3 Documentation . . . . . . . . . . . . . . . . . . . . 30

PRO/II 9.3 Release Notes

New Features of PRO/II 9.3

Open File in original version

New Features of PRO/II 9.3

PRO/II 9.3 Release Notes

branches representing nested recycle loops.

the embedded units.

dropped anywhere on the tree. Child units are moved with

Case Study Improvements

Phase Envelope Updates

New Features of PRO/II 9.3

pressures inlet, outlet, and halfway in between.

Ranges) to be set via the "Define" function. Note: Due to

exchanger method, the field selection is ignored. It is

outlet and mid pressure isobars.

vent rates at specific times

the specified PFINAL

so that fewer streams are produced

PRO/II 9.3 Release Notes

Heat Curves Spreadsheet

Tray Properties Available for COM Programs

Tools/Spreadsheet/Heat Curves Update

parameters, resutls, constants, etc as always.

New Features of PRO/II 9.3

as default but no specific method is set, the file name is

Correlation 18 can now be chosen for Temperature

The default for prediction of Heat of Formation Data from

Yearly updates on DIPPR 2013 from now on based on

PRO/II 9.3 Release Notes

DIPPR 2013 will expire in 2024.

MS Office 64 bit is not supported. Various Excel features (such

MS Office 2013 is not supported.

On some Japanese Vista installations, PRO/II cannot install

Uninstalling certain features of PRO/II (such as OLI, REFPROP

Installing v8.3 or earlier may unregister v9.1 libraries. Use the

On some windows server machines give an 'OPCUA server failed

3.5".After enabling the .Net Framework 3.5.1 feature from

Uninstalling PRO/II 8.2 after installing PRO/II 9.0, the uninstall

PRO/II 8.3 to ROMeo 5.1 translator pops up errors and fails.

In Residue Curves, when a new workbook is created, the toolbar

Previously, distillation columns in recycle loops recalculated in

interacting with PRO/II database, it is recommended that user should

Q6) Can I search for a stream say "CRUDE" or a Unit Operation

Q9) I dragged and dropped a vector attribute onto an empty cell

A) Yes. There are few Sample Portal files placed in

Multiple Simulations Link_Chiller Plant - 1 and 2.xlsm

Naptha Assay_Case Study.xlsm

If you want to view these files, do any of the following:

Start Sim4Me Portal application in stand-alone mode and

Q15) How to install the patch for Sim4Me Portal?

PRO/II 9.3 Release Notes

It does not work with security setting "Very High". It can be

From Add-Remove panel, modify PRO/II 9.3 install and

After reboot, modify PROII.INI to change the security to

A) This is because it is a portal file. Therefore, the user can view

Q20) Sometimes Portal is launched in User mode for

message "the required MICROSOFT office version is not

At the end of PRO/II 9.3 installation a dialog pops up asking for

PRO/II fails to launch with the default DEP setting on Windows

Important information for uninstalling previous versions of