Important: Read First

Release Notes for PRO/II 7.0

Welcome to the release of PRO/II 7.0. These Release Notes supple-
ment and supersede the corresponding sections in all PRO/II 7.0
documentation supplied with this release. If upgrading from PRO/II
4.x, please read the Release Notes for PRO/II 5.0 first.

Contents
New Features of PRO/II 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Compatibility with Earlier Versions of PRO/II . . . . . . . . . . . . . . . . 4
Important Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Installation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Switching Security Types for PC . . . . . . . . . . . . . . . . . . . . . . . . . . 5
UAS/PDTS Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Where to Find PRO/II 7.0 Documentation . . . . . . . . . . . . . . . . . . . . 10
Printed Documentation Included with this Package . . . . . . . . . . 10
Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Summary of Defects Fixed in PRO/II 7.0 . . . . . . . . . . . . . . . . . . . . . 11
Summary of Open Defects in PRO/II 7.0 . . . . . . . . . . . . . . . . . . . . . 18
PRO/II 7.x Bug Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
License and Copyright Information . . . . . . . . . . . . . . . . . . . . . . . . . 19

PRO/II 7.0 Release Notes 1

New Features of PRO/II 7.0
The following enhancements have been made to PRO/II 7.0:

New Feature Description

Batch Distillation -Vapor-liquid-liquid equilibrium is now supported at the
Upgrade condenser. The reflux ratio can be set for each liquid phase
independently.
-Condenser and reboiler conditions can be used as
specifications.
-Specifications can be made on a volumetric or mass flow
rate.
-Pressure profiles can be set for each operation policy, so
change in pressure profile during operation can be taken into
account. Pressures can be either stepped up/down at the
beginning of a policy, or allowed to adjust linearly during a
time interval to the specified policy pressure.
-User can generate trend graphs.
-User can retrieve transport properties at theoretical stages
for detailed design of distillation tower.
Unit Operation All unit operations are supported, including merged
Copy/Paste columns. New feed and product streams are created for the
new unit. Specifications of the new units are cloned to the
new units. Product specifications are cloned to the newly
created product streams. Note: Copy and paste of groups of
units or block diagrams is not supported for v7.0
Global CAPE-Open PRO/II now supports integration with third-party CAPE-Open
Thermodynamics thermodynamic property packages
Interface -Native PRO/II unit operations and streams can use CAPE-
Open property packages
-CAPE-Open unit operations can use either CAPE-Open
property packages or PRO/II thermodynamic systems
HTRI-XIST link PRO/II can access the HTRI XIST program directly for shell
and tube heat exchanger design and rating providing you
have a properly licensed and secured HTRI-IST installed.
PRO/II can invoke the HTRI GUI from PROVISION as a native
unit operation for data entry and results review. PRO/II can
transfer HXRIG input data to and from HTRI. During
flowsheet solution, the required property data are
automatically generated and transferred to HTRI calculations.
Component The component databank search order (PROCESS, SIMSCI)
Databank used for GUI and keyword execution can be specified and
stored in the proii.ini file under user directory.

2 New Features of PRO/II 7.0

 New Feature Description
Transport Property New calculation methods have been added for the following
properties:
Liquid Density
API92 Procedure 6A3.6
API92 Procedure 6A3.7 (High Pressure)
Liquid Thermal Conductivity
Latini Correlation
API96 Procedure 12A3.2
API96 Procedure 12A4.1 (High Pressure)
Liquid Viscosity
Twu Viscosity with Twu-Bulls mixing rule
API Viscosity with Twu-Bulls mixing rule
Vapor Viscosity
Bromley-Wilkey Correlation
Surface Tension
API82 Procedure 10A3.2

PRO/II 7.0 Release Notes 3

 Compatibility with Earlier Versions of PRO/II
Standalone
PRO/II 4.1x, PRO/II 5.0x, PRO/II 5.1x, 5.5x, 5.6x, 6.0x database files
will automatically be converted into PRO/II 7.0 files as they are
opened. The original file will be saved using an alternate file name.

Important Notices
Installation Notes
If you have installed multiple SIMSCI products or versions of a
particular SIMSCI product on a single computer and have
subsequently uninstalled one or more of these, you may have
encountered some of the problems described below:
1. When trying to run a SIMSCI product, the error message “Secu-
rity button missing or improperly installed” appears. To fix this
problem, locate the utils directory on the installation media. This
directory is located directly off the root of the CD-ROM. On
WinNT and Windows 2000, copy the ds1410d.sys file to the
winnt\system32\drivers directory, run regnetsec located in the
utils directory on the CD, to register the file, and then reboot. On
Windows XP, copy the file to windows\system32\drivers. On
Win98 and WinME, copy the vsauthd.vxd file (if present) to the
Windows system directory. Try running your product again. If
you still encounter difficulties, please contact your SIMSCI tech-
nical support for further assistance.
2. Some of the utility programs such as Dataprep, EUP or Libmgr
may be missing from your installation area even though you
have not tried to uninstall this particular version of the product.
To fix this problem, rerun the setup program and choose these
items on the custom install.
Note: Before executing any of the installation programs, disable
all antivirus software running on your computer.

Hardware Requirements for PC

The minimum hardware requirements for PRO/II 7.0 is an Intel Pen-

tium 166 MHz with 64 MB of RAM (32 MB for Client-only installa-
tion). Performance is optimized with at least 256 MB RAM.

4 Important Notices
 Switching Security Types for PC
PRO/II 7.0 provides the following security options:

■ PC Dallas Semiconductor Single User Security for PRO/II with

PROVISION, PRO/II Keyword, and add-ons.

■ USB Single User Security for PRO/II with PROVISION, PRO/II

Keyword, and add-ons.

■ FLEXlm Security for Windows 98/Me/NT/W2000/XP for PRO/II

with PROVISION with security for add-ons.

■ Elan Security 5.11 for Windows 98/Me/NT/W2000/XP for PRO/II

with PROVISION with security for add-ons. Elan is no longer
supported by Rainbow. We recommend changing to FLEXlm
option.

The security option used is normally chosen during the install proce-
dure. If you want to switch to a different security method after instal-
lation, use the following procedures.

To switch to Elan security:

■ Open the proii.ini file found in the user directory.

■ Find the section entitled [wss_Security] and set Type=ELAN.

■ Save the file and exit.

■ If you are running Windows 98/Me, open autoexec.bat located

on the root of the C drive. Add the following line to your
autoexec.bat file: set SIMSCI_ELMHOST=@{ELAN server
machine name}.

■ If you are running under Windows NT/2000/XP, add the

SIMSCI_ELMHOST=@{ELAN server machine name} environ-
ment variable to your control panel/system/environment set-
tings.

■ Reboot your computer so the changes to your security environ-

ment will be correctly configured.

To switch to Dallas security:

■ Open the proii.ini file found in the user directory.

■ Find the section entitled [wss_Security] and set Type=DSC.

PRO/II 7.0 Release Notes 5

 ■ If the lines mode=SINGLE and/or Keydir=… are present, com-
ment them out by adding a semi-colon to the front of them.

■ Save the file and exit.

To switch to USB security:

■ Open the proii.ini file found in the user directory.
■ Find the section entitled [wss_Security] and set Type=USB.

■ Save the file and exit.

To switch to FLEXlm security:

■ Open the proii.ini file found in the user directory.

■ Find the section entitled [wss_Security] and set the "Type=" key-
word to one of the following values

■ Type=FLXLM For Flex/LM version 7.2

■ Type=FLXLM92 For Flex/LM version 9.2

■ The version selected must match the version of the Flex/LM

server that is used on your network. Please confirm with your
system administrator the specific version of Flex/LM in use.
■ Save the file and exit.
■ If you are running Windows 98/Me, open autoexec.bat located
on the root of the C drive. Add the following line to your
autoexec.bat file: set IPASSI_LICENSE_FILE={FLXLM server host
name}.
■ If you are running under Windows NT/2000/XP, add the
IPASSI_LICENSE_FILE={FLXLM server host name} environment
variable to your control panel/system/environment settings.
■ Reboot your computer so the changes to your security environ-
ment will be correctly configured.

UAS/PDTS Capabilities
PRO/II 7.0 users using the User-Added Subroutine (UAS) or PRO/II
Data Transfer System (PDTS) capabilities can compile and link their
code using one of the following two compilers:
■ Compaq Visual FORTRAN (version 6.1 through 6.6b)
■ Intel Visual FORTRAN version 8.0 for Windows (Standard or
Professional Edition)

6 Important Notices
 If you are using Compaq Visual FORTRAN 6.x:
The Visual Studio Workspaces for the example PDTS applications are
located at:
C:\SIMSCI\Proii70\User\Pdts\Examples\VF6

The Visual Studio Workspace for the example UAS is located at:
C:\SIMSCI\Proii70\User\Uas\Examples\VF6

This assumes that you have installed to "C:\SIMSCI\Proii70".

We strongly recommend that you take advantage of the free

upgrades available from HP/Compaq to bring your complier up to
6.6b. Compaq Visual FORTRAN patches are available at http://
h18009.www1.hp.com/fortran/visual/updates.html.

Depending on the options selected when you installed Compaq

Visual FORTRAN 6.6b, you may not have oldnames.lib installed on
your computer. This library is required to build PDTS applications
and is located on the Compaq Visual FORTRAN CD in the \X86\SUP-
PORT\LIB directory. If you do not have this library, copy it into your
Compaq Visual FORTRAN library directory before building PDTS
applications.

If you are using Intel FORTRAN 8.0:

The Visual Studio Solution files for the example PDTS applications
are located at:
C:\SIMSCI\Proii70\User\Pdts\Examples\IF8
The Visual Studio Solution file for the example UAS is located at:
C:\SIMSCI\Proii70\User\Uas\Examples\IF8

This assumes that you have installed to "C:\SIMSCI\Proii70".

Source code changes required for Intel FORTRAN 8.0:

PRO/II 7.0 is built with Compaq FORTRAN 6.6b. If you build UAS or
PDTS applications using Intel FORTRAN 8.0, please note that FOR-
TRAN unit numbers cannot be shared by two different compilers. For
example, if a file is opened by Compaq FORTRAN 6.x using FOR-
TRAN unit number 10 and that number is passed to a PDTS or UAS
subroutine compiled using Intel FORTRAN 8.0, then a READ or
WRITE statement using FORTRAN unit 10 will not work because
Compaq FORTRAN 6.x and Intel FORTRAN 8.0 use different internal
runtime data structures.

PRO/II 7.0 Release Notes 7

 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() sub-
routine

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

In both of these cases, PRO/II calls the FORTRAN OPEN statement to
open a file and passes the unit number to your PDTS application or
UAS. For applications built using Intel FORTRAN 8.0, you cannot
directly use this FORTRAN unit number in a WRITE statement.
Instead, the utility subroutine PAWRITE has been provided to allow
your application to write output to the file. The following code frag-
ments illustrate the required changes:
Original PDTS example:
CHARACTER*8 NAME
.
.
1001 FORMAT(‘Enter File Name ’)
1002 FORMAT(A)
1003 FORMAT(‘Data Retrieved Reported for File = ’,A10)
WRITE(*, 1001)
READ(*, 1002) NAME
.
CALL PAOPEN (NAME, ‘ ’, NFOUT, IRCODE)
WRITE (NFOUT, 1003) NAME

PDTS example modified for Intel FORTRAN interoperation with Com-

paq FORTRAN:
CHARACTER*8 NAME
CHARACTER*133 CHARDATA
.
.
1001 FORMAT(‘Enter File Name ’)
1002 FORMAT(A)
1003 FORMAT(‘Data Retrieved Reported for File = ’,A10)
WRITE(*, 1001)
READ(*, 1002) NAME
.
CALL PAOPEN (NAME, ‘ ’, NFOUT, IRCODE)
WRITE (CHARDATA, 103) NAME
PAWRITE (NFOUT, CHARDATA)

Note that the modified code does not directly write the output to the
FORTRAN unit number NFOUT. Instead, it writes the output to a char-
acter variable then calls the utility subroutine PAWRITE() which tells
PRO/II to write the contents of the character variable CHARDATA to
FORTRAN unit number NFOUT.

8 Important Notices
 Original UAS example:
SUBROUTINE USER42(IPARM,RPARM,SUP-
PLE,HEAT,IDATA,ISOLVE,ISTOP)
.
.
CHARACTER*12 CID
1001 FORMAT(' ERROR !! FEED STREAM ',A12,' IS MISS-
ING').
.
.
IOUT = IDATA(6)
C
C RETRIEVE FEED STREAM
C
CALL URXINF('FEED',1,CID,CNAME,IERR)
IF (IERR. NE. 0) THEN
IPARM(2) = 1
WRITE(IOUT,1001) CID
ISOLVE = 1
ISTOP = 1
GO TO 9999
ENDIF

UAS example modified for Intel FORTRAN interoperation with Com-

paq FORTRAN:
SUBROUTINE USER42(IPARM,RPARM,SUP-
PLE,HEAT,IDATA,ISOLVE,ISTOP)
.
.
CHARACTER*12 CID
CHARACTER*133 CHARDATA
1001 FORMAT(' ERROR !! FEED STREAM ',A12,' IS MISS-
ING').
.
.
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

Note: if you call the subroutine FIGETU to get a FORTRAN unit num-
ber and then call OPEN() in your own PDTS or UAS code, then you
do not need to make any code changes to the READ or WRITE state-

PRO/II 7.0 Release Notes 9

 ments because both the OPEN and the WRITE (or READ) is being
done within code compiled by the same compiler.

Where to Find PRO/II 7.0 Documentation

Printed Documentation Included with this Package
■ Release Notes for PRO/II 7.0 (this document)
■ PRO/II Installation Guide

Online Documentation
■ PRO/II User’s Guide

■ PRO/II Keyword Manual Addendum

■ PRO/II Keyword Manual

■ PRO/II Reference Manual

■ PRO/II Installation Guide v 7.0

■ PRO/II Tutorial Guide

■ PRO/II Quick Reference Card

■ PRO/II Casebooks

■ PRO/II Application Briefs Manual

■ PRO/II LIBMGR and COMPS User’s Guide

■ PRO/II Data Transfer System and User-Added Subroutines

User’s Guide

■ PRO/II Add-On Modules User’s Guide

■ PRO/II Interface Modules User’s Guide

■ SIMSCI Component and Thermodynamic Data Input Manual

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

can be found on the hard drive under the \PROII\PROII70\MANUALS
directory.

10 Where to Find PRO/II 7.0 Documentation

Summary of Defects Fixed in PRO/II 7.0
Feature Description
ACE ACE may issue multiple bogus error messages - such as " **
Fatal Error ** Insufficient data to determine LIQUID SPGR " -
when tube feed is two phase.
ACE Fins set to .1 fin/mm properly gives yellow warning. Status
button, though, says value is above upper limit. If you check the
range, you will see that value is below the upper limit.
ACE Under some circumstances, the Air Cooled Exchanger unit
causes a data file size bloat with repeated runs.
ACE ACE in design mode gives error message that tube length and
bundle length are not allowed - but they're grayed out so they
haven't been entered.
ACE Flowsheet with several ACE units runs fine but gets an error in
report generation that it runs out of slots. Change out one of the
ACE units for an HX and it works fine.
AMSIM PFD with only AMSIM unit op and controller. Enter spec on
controller gives you exception error.
AMSIM Reference stream to an Amsim product stream is not updated
after Amsim solves.
Assay Changing the assay EP from 98 to 99.99 has no effect on the
reported value.
Assay D2887 using API94 gives good answers for 90, 95, 99%, but
gives bad values for rest. This is an output reporting problem
only, internally is good.
Assay Product assay data not available via OLE unless assays are
calculated in Stream Property Table.
Assay Regeneration of pseudocomponents in some cases causes the
Component Properties button to turn red when it shouldn’t. This
means you can't run when it should be allowed.
Autoexec Installing v6.01 on ME: Path on autoexec.bat is deleted and
replaced with \proii601\bin path.
Batch Batch still sets the temperature of the product stream from the
Distillation accumulator at the last temperature of the condenser during the
accumulation period. It should have integrated enthalpy over the
entire period.
Batch Stop condition in stillpot is ignored.
Distillation
Block Diagram A file with stream property tables in a block diagram may get an
exception error on crash.
Calculator Calculator SRVSTR function does not understand "C(I)" for the
array label.
Calculator "Output R(1:5)" .cal does not write the result name out correctly.
It wasn't dimensioned properly for 36 character strings.

PRO/II 7.0 Release Notes 11

 Feature Description
Calculator Add a parameter to a Calculator that uses tray/hydraulics column
diameter in units "M". Commit to PFD. Return, "M" is
disappeared. Only meters is affected, other units of measure
seem OK.
Calculator The calculator allows "$" as a valid character in the Results Name
field. This creates problems on export/import since "$"
terminates the statement.
Casestudy 5.x files using the Case Study feature will lose the Case Study
upon opening into v6.0.
Casestudy Switch to Base Case only option causes Run button to become
disabled
Casestudy Case study feature in v5.11 is dropped on conversion to v5.5.
Casestudy Changing flowrate based on kg/hr during casestudy results in a
zero rate being used.
Casestudy Case study cannot access Profimatics Reactors.
Column After executing a column simulation with sizing, change the
flowsheet and rerun. Column fails to resize, but rates the new
column flows at the old size.
Column Adding a second packing section to a column causes the first
one to disappear.
Column Output report for Column tray loading report has an error when
Feed Separate option is used. Vapor feed to tray 1 should include
the vapor part of the feed to tray two, but doesn't.
Column Automatic spec from estimates problem: flowrate estimate given
in weight units transfers as weight units spec into Specification
DEW. But, column solves to moles spec instead of weight spec.
Column The conversion to BBL/HR is incorrect for water streams on the
Column Summary report.
Column Switching active/inactive specs resets initial column profile
estimates. It shouldn't.
Column Export column with product estimates in liquid volume units
causes exception.
Column After reducing trays, attempting to enter tray hydraulics causes
freeze.
Column Select fins present in ACE and type in .1. OK. Come back,
changed to .1181. Type in some number and it always comes
back changed.
Column Column that works in v5.61 electrolytes give different answers in
v6.0.
Column IO Column with user entered temperature profiles solves with a
water imbalance.
Column Column with more than 3 named pumparounds gets a spurious
FZONE statement on export.

12 Summary of Defects Fixed in PRO/II 7.0

 Feature Description
Column This problem results because the bottom product from the main
tower is fed to a sidestripper. The IO algorithm does not allow
this, you must take a sidedraw from the main tower, feed it to the
sidestripper, vary the sidedraw and set the bottoms rate of the
main tower to 0.
Component Reordering components in the Component Window does not
cascade to a change in order in the Component Properties
Window.
Component Add Therminol 66 to flowsheet and run causes exception error.
Component Enter of fixed properties via GUI does not persist after entry.
Component After importing a file with missing property data for user
components, the problem runs and reports results. Click on
Component Properties and OK. Then Run. Now you get the
warning message you should have gotten in the first place.
Component There is a flaw in displaying properties of petros in the GUI. See
the memo: If PRO/II placed the calculated MW in the fixed prop
DEW you are effectively changing the problem description.
Controller Controller acting on Compressor RPM has moles instead of RPM
as UOM on the Steps and Limits DEW.
CP2File SrBulkProp object does not seem to be working via the class
library.
Crystallizer Crystallizer comes to a solution where the heat balance can't be
met, gives warning, then says solution reached. Should have
been "Unit not solved".
Data Review With weight UOM set to tonnes, Stream Property Table is shows
Window flowrate that should be tonne-mole/day as ton/day instead
(English mass instead of metric mole units)
Data Review In data review window, Change Units should not be a visible
Window option. Only Convert Values or Cancel should be visible. If the
user invokes Change Units then he/she will be looking at
numbers different from the converged results.
Depressuring In the Depres unit, the valve constant is not dimensionless. In
Keywords it doesn't matter because the constant is entered
according to the units in effect. But in the GUI, if the user globally
changes units, the constant value needs to change.
Depressuring Wetted HT area for sphere in blowdown calculation is wrong.
Electrolytes Use CMG to create .dbs file for water/methylamine. Select this
for thermo method. When attempting to create components,
gets message that it could not create, possibly trying to write
over existing components.
Electrolytes Large electrolytes .dbs file results crash when you try to add to
thermo in GUI
Electrolytes Electrolyte flowsheets using built-in models in v5.61 are not
being mapped to the correct electrolyte model in v6.01 on
convert. Component orders are scrambled.

PRO/II 7.0 Release Notes 13

 Feature Description
Electrolytes Electrolytes won't work if P2 installed on \Program Files\
directory. OLI has trouble with spaces.
File Converter - File with attached heat exchanger cannot be converted to a newer
HX version of PRO/II.
Flash Flash with hot vol prod / hot vol feed spec fails. Exactly same
spec using controller solves easily.
Flash Feed flash to mixer fails. Yet, the mixer solves and the flowsheet
solve. Warning message is inadequate - flowsheet should have
failed.
Flash If you use IDEAL thermo and then override some pairs with
KDATA in the input file, all the flashes, including the feed flash,
will use the IDEAL data for the KVALUES in the first iteration of
the flash and then switch to KDATA data for all other iteration.
Flash A flash whose streams are reference feeds may not solve.
Fuel Cell Reported current density is off by several orders of magnitude.
Furnace The makeup air in for the combustion side is composed of an
incorrect O2/N2 mixture.
Furnace First pass through calculator retrieves the right duty from the
Furnace. Second time through, duty is smaller by *.001.
HCURVE The curves for LNGHX can have the wrong cell labels if the
LNGHX cells don't come first on the Hcurve unit op.
Historian/PI You cannot disconnect from the server unless you shutdown
PRO/II and start again.
Hot Keys/Assay Using the assay hot key occasionally fails with the odd error
messages.
Hot Key/ On a particular problem with a Stream Property Table, it's not
Distillation possible to generate a Distillation Curve with the Hot Key unless
the SPT is deleted first.
Hot Key/Phase The hot key phase envelope does not work for certain
Envelope combinations of UOM. The cricondenbar and cricondetherm are
misplaced.
HX The presence of a calculator retrieving LMTD results can change
whether LMTD is calculated based on output or calc time. The
only thing that should influence that calculation is the
ZONES(CALC) or ZONES(OUTP) argument.
HX Import file with DEFINE on HX that refers to the reboiler duty in a
sidestripper. Enter DEW all the way to the DEFINED duty and see
that it's not there. Color reconciliation doesn't occur until you
actually visit that field.
HXRIG When attaching an HXRIG to a column, re-selecting the
attachment checkbox does not enable the groupbox for the
attachment details.

14 Summary of Defects Fixed in PRO/II 7.0

 Feature Description
Menus Alt-F-I doesn't work because it has an ambiguous choice - both
Import and Import Tag
Mixer According to KW documentation, a mixer can only have one
product. You can't have both a V and L product. Not flagged as
an error on import. One of the product streams will be regarded
as an unsatisfied external feed after import to GUI.
NOTES Increase size of Notes field. This is still the same size as v5.61.
Optimizer View Results for Optimizer reports the Specified value as RMISS
(-1.5 e-39) and Constraints Min & Max as n/a. These values are
available to the standard output report.
Output The calculation history report is not included in the output report
under some conditions.
Pipe DP is not available as a reference spec on a Pipe unit operation in
the GUI.
Polymer If you fail to enter moment data for polymers, PRO/II gives
Reactor appropriate error message on Run. However, after entering
moment data, error message doesn't clear.
Polymers You are limited to 3 polymer segments per polymer component.
However, the user has the ability to define unlimited polymer
segments, and thus should be able add an unlimited number of
different segments per component.
Reaction Data Non-reactant with 0 stoichiometric coefficient but with reaction
order (such as a catalyst). Reaction order is lost on import
starting with v6.0.
Reactor/Gibbs Gibbs reactor gives a different answer depending on whether
CHON is present in the component list or not. Should be the
same answer. Don't know which one is right.
Recycle Large flowsheet gets error message "unable to locate command
code 50100000” in early part of flowsheet.
Refinery Import file with Refinery Inspection Property given in FRAC
Inspection results in error message that value is not between 0 and 100.
Properties Percent works OK.

Refinery v5.61 file with Nelson Flash Point RIP in thermo section is not
Inspection converted properly to v6.0x.
Properties
Refinery Streams containing sulfur actually report a real value sulfur
Inspection content providing they are created using the default thermo. If
Properties you switch to an alternate thermo the sulfur content is reported
as n/a.
Refinery Refinery inspection properties are not being properly written out
Inspection on the METHODS statement in the Thermo section.
Properties
Regress Regress results on the output file sometimes have the wrong
component listed.
Regress Generated van Laar coefficients are not copied into the PRO/II
simulation after executing Store Results.

PRO/II 7.0 Release Notes 15

 Feature Description
Regress Flowsheet file with an imbedded regression analysis gets a bad
pointer abort in the flowhseet. Removing the regression and the
flowsheet works OK.
Regress Export of regress data to keywords fails to identify the SRKM
C12 and C21 parameters as being fixed at 1. Instead, they're
given as 0.
Regress View Results from Regress are generating different x-y diagrams
than you get after you transfer the parameters into PRO/II and
run within the PRO/II environment.
Regress File that explicitly reverse the input order of components in Pxy
data results in Wilson parameters being generated in the reverse
order.
Regress Updating HMIX parameters in the Regress GUI leads to selection
of the default units which are Kelvin, when the unit should be KJ.
Changing the unit to KJ without adjusting the parameters yields a
good match with experimental data.
Regress After running successful ternary regression in PRO/II, "transfer
data" results in NRTL i-j parameters being also transferred to i-k
and j-k components. The good results for i-k and j-k are lost.
Regress Running a non-electrolytes problem on an electrolytes version
consumes an electrolyte license (503). Companies with limited
electrolyte licenses often run out of seats for legitimate
electrolyte users.
Sequence After selecting Sequencer button, it turns blue even when all the
settings are default.
Shortcut Deleting side stream causes wrong Fenske spec to be invalidated
in some cases.
Shortcut Export of file with Shortcut and Product estimate in LV basis
causes extraneous value to be printed after the real product
estimate value.
Spec Vary Change of UOM in Optimizer Variable causes Optimizer to fail
Define because it things the variable is in the old UOM.

Spec Vary HX temperature approaches (HOCI, etc.) are not accessible via
Define the SPEC VARY DEFINE system on import.

Spec Vary Spec on heating value needs to have phase field enabled.
Define
Spreadsheet Spreadsheet tools is working fine from within PRO/II, but cannot
Tools be launched externally. Says file is not found, even thought the
path is correct.
Spreadsheet On Windows XP, at random times, p2oledbs.exe does not shut
Tools down even though you have set the object to "nothing" in code.
Multiple copies of p2oledbs processes cause PRO/II and
subsequent OLE operations to fail.
Spreadsheet Adding spreadsheet tools beyond 13 sometimes fails
Tools

16 Summary of Defects Fixed in PRO/II 7.0

 Feature Description
Stream Solids entered in an assay stream do not persist.

Stream When a stream rate is updated by a Calculator, streams

referenced to it may not have the correct flowrate.
Stream Polymers file with stream calculator: After run, attempt to
Calculator change stream calculator spec results in exception error.
Stream Stream Property Table text is misleading. Users may think that
Property Table the critical point is the true critical instead of pseudocritical.
Stream Ionic strength is not available to the Stream Property Table.
Property Table
Stream The Comp. Mole Rate Property list got scrambled in order
Property Table between v6.0 and v6.01 exposing a bug that the attribute list did
not change order too. Results in mismatch between attributes
and UOM.
Tag Change of tag data does not result in re-calc of assay
components.
Tag Stream Liquid Fraction input data using Tags results in incorrect
answers or an error message that the problem is incomplete due
to stream data. Export to keywords results in missing LFRACT
keyword on PROP statement.
Thermo File with three databanks in search order. Attempt to change
search order under K-value(VLE)/Databank Search order results
in error message (no more than two banks), and then Exception
error.
Thermo Combination of multiple thermos and reaction data procedure
causes Bad Pointer error message on import.
Thermo Transport=tacite results in only liquid viscosity calculated using
LBC (wrong). In v5.61 both vapor and liquid were calculated with
LBC (correct).
Thermo Polymer liquid activity methods do not work with Henry's Law.
Thermo Using SRKM, changing selection of alpha method from SimSci
databank to Acentric does not persist.
Thermo In some cases, file open after file conversion leaves enthalpies as
large negative numbers.
TVP TVP calculation for stream with dissolved water is slightly
different from bp calc at 100F. They should be identical.
Unit Property Adding a custom unit operation property table may cause data
Table corruption in a column
Unit Property Units of measure for Depressure RateCalc are displayed as lb-
Table moles/hr, but should be lb/hr.
Unit Ops Right click any unit operation to rename then return to that unit.
Data are lost.

PRO/II 7.0 Release Notes 17

Summary of Open Defects in PRO/II 7.0
PRO/II 7.x Bug Lists
To access the current version of PRO/II 7.0 bug list as well as FAQ
and Updates, visit our website's Knowledge base at www.simsci-ess-
cor.com. Select Support Menu and then the Updates, Tips and More
Option. Finally select PRO/II and enter in your personalized SIM4ME
Username & Password.

If you do not have a SIM4ME username & password, please take a

few minutes to Register. Registration will allow you to access our
complete knowledge base as well as allow us to display custom
information of interest to you.

18 Summary of Open Defects in PRO/II 7.0

License and Copyright Information
Release Notes for The software described in this guide is furnished under a
PRO/II 7.0 written agreement and may be used only in accordance with
the terms and conditions of the license agreement under which
you obtained it. The technical documentation is being
delivered to you AS IS and Invensys Systems, Inc. makes no
warranty as to its accuracy or use. Any use of the technical
documentation or the information contained therein is at the
risk of the user. Documentation may include technical or other
inaccuracies or typographical errors. Invensys Systems, Inc.
reserves the right to make changes without prior notice.
Copyright Notice Copyright © 2004 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, broadcast-
ing, or by any information storage and retrieval system, with-
out permission in writing from Invensys Systems, Inc.

Trademarks PRO/II and Invensys SIMSCI-ESSCOR are trademarks of

Invensys plc, its subsidiaries and affiliates.
AMSIM is a trademark of DBR Schlumberger Canada Limited.
Visual Fortran is a trademark of Intel Corporation.
Windows 98, Windows ME, Windows NT, Windows 2000,
Windows XP, Windows 2003, and MS-DOS are trademarks of
Microsoft Corporation.
Adobe, Acrobat, Exchange, and Reader are trademarks of
Adobe Systems, Inc.
All other products may be trademarks of their respective
companies.
U.S. GOVERNMENT RESTRICTED RIGHTS LEGEND
The Software and accompanying written materials are provided
with restricted rights. Use, duplication, or disclosure by the
Government is subject to restrictions as set forth in
subparagraph (c) (1) (ii) of the Rights in Technical Data And
Computer Software clause at DFARS 252.227-7013 or in
subparagraphs (c) (1) and (2) of the Commercial Computer
Software-Restricted Rights clause at 48 C.F.R. 52.227-19, as
applicable. The Contractor/Manufacturer is: Invensys
Systems, Inc. (Invensys SIMSCI-ESSCOR) 26561 Rancho
Parkway South, Suite 100, Lake Forest, CA 92630, USA.

Printed in the United States of America, July 2004.

PRO/II 7.0 Release Notes 19

20 License and Copyright Information