proii83 releasenotes

Important: Read First

Release Notes for PRO/II 8.3 Welcome to the release of PRO/II 8.3. These Release Notes supplement and supersede the corresponding sections in all PRO/II 8.3 documentation supplied with this release.

ContentsNew Features of PRO/II 8.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Important Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Known issues in PRO/II 8.3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3What is new/changed in PRO/II 8.3 . . . . . . . . . . . . . . . . . . . . . . . 3What is new/changed in PRO/II 8.2 . . . . . . . . . . . . . . . . . . . . . . . 6Default changes in PRO/II v8.0: . . . . . . . . . . . . . . . . . . . . . . . . . 10

Installation Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Known Defects and Constraints using SIM4ME Reports . . . . . . . 11Known Defects and Constraints using SIM4ME Portal . . . . . . . . 14Switching Security Types for PC . . . . . . . . . . . . . . . . . . . . . . . . . 18UAS/PDTS Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Where to Find PRO/II 8.3 Documentation . . . . . . . . . . . . . . . . . . . . 25Printed Documentation Included with this Package . . . . . . . . . . 25Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Summary of Defects Fixed in PRO/II 8.3 . . . . . . . . . . . . . . . . . . . . . 26

Summary of Defects Fixed in PRO/II 8.2 Patches . . . . . . . . . . . . . . 40

Summary of Open Defects in PRO/II 8.3 . . . . . . . . . . . . . . . . . . . . . 44

License and Copyright Information . . . . . . . . . . . . . . . . . . . . . . . . . 45

PRO/II 8.3 Release Notes 1

New Features of PRO/II 8.3

The following enhancements have been made to PRO/II 8.3:

New Feature Description

Component and Thermo Upgrades

Update to SIM4ME Thermo 3.3

New Correlations for some property calculations

Component Specific Databank Search Order

Cascading Pure Component Search OrderAllows properties to aggregate from multiple databanks

Choose Component From List UpgradeDynamically populated - can pick components from user libraries

GUI Support for Method Specific Fixed Component Properties

Customizable Language Module

Japanese Language Add-on

Improve Containerization of Simulation Files

Include more working files in .prz “container”.

SIM4ME Portal Phase II Integration

Case Studies, Input Assay Support, Multiple Simulations

More GUI support for KW-only features

Upstream Unit Operation, Dryer Unit Operation, Rotary Drum Filter

RATEFRAC Improvements

Reactive distillation calculations with non-VLE segments

Electrolytes Integration- Brings OLI electrolyte thermo into RATEFRAC- Requires OLI v7- Aqueous or MSE OLI models

HTRI Interface Improvements

Speed Improvements in HTRI via HXRIG- Average of 23% reduction in time required - Primarily achieved by reducing the number of PRO/II-HTRI iterations for pressure balance- Property grid enhancements for phase changes

PRO/II Column HTRI Thermosiphon Reboiler linkage for Recycle Flowrate updating

Air as Utility Stream for ACE

Air as Utility Stream for ACE

CAPE-OPEN Enhancements

Specification/Vary/Define Support for Unit Operations

2 New Features of PRO/II 8.3

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, and 8.2x database files will automatically be converted into PRO/II 8.3 files as they are opened. The original file will be saved using an alternate file name.

Known issues in 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 work-book basis.

3. Previously, distillation columns in recycle loops recalculated in every recycle iteration. Now, improved logic tests a solved col-umn 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 differ-ent starting point. Now, restarted columns always restart using original initial conditions. This eliminates any drift in results in most cases.

What is new/changed in PRO/II 8.3

Default changes

➤ Replace BK10 from the most commonly used thermo list with SRKM

Residue Curve Map Utility

Entirely driven through ExcelFull User ControlCharts and Data are well arranged and ready for further use in MS-Office applications

New Feature Description


➤ New Output Report Defaults:

1. “Include Thermodynamic Input Parameters" will be turned on by default

2. "Include Overall Flowsheet Mass Balance" will be turned on by default

3."Print Calculation Sequence Map in the Output' will be turned on by default

Aromatics extraction NRTL library for use with the Sulfolane® BTX extraction process (Sulfolane is a trademark of Shell International)

A new NRTL parameter databank containing literature sourced inter-action parameters for 11 components have been added to the thermo library. All binary combinations are available. The components include:

Water

Sulfolane (Tetrahydrothiophene-1,1-dioxide)

N-Hexane

N-Heptane

N-Octane

Benzene

Toluene

P-Xylene

M-Xylene

O-Xylene

Ethylbenzene

Improvements to SimSci Heavy Oil Viscosity

PRO/II 8.2.2 contains an update to the SimSci heavy oil liquid viscos-ity method. Bitumens and heavy oils can be orders of magnitude more viscous than conventional sweet light crude. The conventional API method for viscosity prediction significantly underperforms on prediction of heavy oils viscosity. The SimSci heavy oil liquid vis-cosity method originally released in PRO/II 8.2 has been improved the based on data received from SimSci-Esscor's Heavy Oils Con-

4 Important Notices

sortium. This large quantity of unpublished proprietary data on a variety of crude oils, bitumens and distillates obtained from the con-sortium has allowed SimSci Heavy Oil Liquid Viscosity method to be even more accurate than before.

For users of KGTower ®

Koch-Glitsch has announced a new version of KGTower, v4.0. Older versions of KGTower will no longer work as their licenses expire so it will be necessary to upgrade to the new one. You must also update the PRO/II to KGTower interface at the same time. The following link has explicit instructions for downloading and installing both KGTower and the interface.

http://www.koch-glitsch.com/koch/home/News_KGTOWER4.0.asp

KBC Profimatics Upgrade:

The link between PRO/II and Profimatics refinery reactor models from KBC have been validated and are functioning properly.

Upgrade Koch-Glitsch Packing Correlations:

The column packing correlations for Koch-Glitsch column packings have been updated with 24 new packings. The following are the new Koch-Glitsch packings added for 8.2.1:

Random packing:

Metal Cascade Mini Rings 1.5, 2.5, 5 inch

Plastic Flexiring 4 inch

Metal IMTP #60

Plastic Beta Rings 2 inch

Ceramic Flexi Saddle LPD 1, 1.5, 3 inch

Structured packing:

Flexipac 3.5X, 4X, 1Y plastic, 2Y plastic, 3Y plastic

Flexipac HC 500Z metal and 500Z thin plastic

Intalox 1T and 1.5T

Flexigrid 2-33, 2-45, 2-67, 3-33, 3-45 and 3-67

Upgraded Biofuels Application Examples:


PRO/II has upgraded the bioethanol application examples in the Applib folder.

What is new/changed in PRO/II 8.2

Change in IO Column enthalpy balance convergence criteria

The definition of the enthalpy balance tolerance for the IO column has been modified. Previously, the tolerance was only applied to the change in the simple enthalpy model parameters in the outer loop. In certain situations this resulted in an overall heat balance error that was larger than acceptable. To improve the overall heat balance the tolerance now applies to both the change in the simple enthalpy model parameters as well as the scaled enthalpy balance for each tray.

The IO algorithm has also been modified. The new algorithm first converges using the original logic (checking the change in the simple enthalpy model parameters only). At this point, if the absolute value of the maximum scaled enthalpy balance error is greater than the enthalpy tolerance, the column is re-solved using a new enthalpy balance scaling factor for the trays. This new scaling factor gives a greater weighting to the enthalpy balance and drives the error lower. Because of the new enthalpy balance scaling factor, a new Jacobian matrix must be computed.

In most cases the IO algorithm will yield the same results after this improvement. In a few cases the column will require more iterations but will solve to a tighter solution. If this happens it may be necessary to increase the maximum number of iterations. In a very few cases the column may no longer solve regardless of the maximum iterations specification. Loosening the enthalpy tolerance judiciously will result in a converged column that is more tightly converged than v8.1 even though the user input tolerance is less stringent. Alternatively, applying a damping factor may help the column to converge to the new tighter criteria. Also, a model that encounters this behavior might be a good candidate for the Chemdist algorithm.

When the new logic is invoked, the message “Changing Enthalpy Scaling” is written to the history file:

ITER 9 E(K) = 2.538E-06 E(ENTH+SPEC) = 3.309E-06 E(SUM) = 1.186E-05

DAMP = 1.000E+00

INNER 0 : E(ENTH+SPEC) = 6.294E-06

6 Important Notices

Changing Enthalpy Scaling

When the scaling is changed for the enthalpy balance, a new matrix must be calculated:

ITER 10 E(K) = 3.911E-07 E(ENTH+SPEC) = 6.294E-06 E(SUM) = 7.106E-06

DAMP = 1.000E+00


Calculating New Matrix

INNER 1 : E(ENTH+SPEC) = 1.258E-07 ALPHA = 1.0000

When the column fails to converge because the enthalpy balance is too tight, a message is added to the history file indicating that the enthalpy balance cannot be met:

ITER 29 E(K) = 0.000E+00 E(ENTH+SPEC) = 6.127E-06 E(SUM) = 6.127E-06

DAMP = 1.000E+00


** MESSAGE ** Scaled enthalpy balance error -2.153E-5 on tray 5 is above the tolerance of 1E-6.

ITER 30 E(K) = 0.000E+00 E(ENTH+SPEC) = 6.127E-06 E(SUM) = 6.127E-06

DAMP = 1.000E+00

Library and Databank Handling During File convertion and Import

Starting with PRO/II v8.0, PRO/II pointed to pure component and interaction databanks located in library files registered by TDM in the Windows registry. In some file conversion and file import cases there could be an ambiguity in which databanks should be used. This may result in a file that points to the wrong databank, or simply doesn't produce a usable file for v8.1.x. The update strengthens the logic and gives the user more opportunity to make the correct unambiguous databank selection.

On import, if a databank is not found among the registered list, PRO/II will now issue the appropriate error message as before, and the import continues to open. Previously all record of the unregistered name disappears from the resulting .prz file. Now the file name appears on the Databank Hierarchy list with an indication that the library is unregistered. If nothing else is wrong with the file, the resulting PFD will open and display a red component data button to indicate the missing data, giving the user an opportunity to correct the problem by registering the file via TDM.

Similarly, if a .prz file is opened and no registered library matches the library found in that file, the file still opens and the component data button will display red.


Heavy Oil Characterization

There is a new petroleum characterization procedure "Heavy Oil" available for criticals properties, ideal-gas enthalpy and molecular weight. This method is an extension of the of the current SimSci (Twu) method. The original Twu correlation is applicable up to a Normal Boiling Point (NBP) of 1000 K (1340 ºF). The Heavy Oil option is intended for the extrapolation of critical properties and molecular weight to NBP's well beyond 1000 K.

The keyword implementation of this method is given on the ASSAY statement.

ASSAY ..., CHARACTERIZE= SIMSCI or CAVETT or CAV80 or LK or EXTAPI or HEAVYOIL, &

MOLW= SIMSCI or API64 or API87 or LK or EXTAPI or HEAVYOIL, ...

The HEAVYOIL keyword selects the new feature. The default remains SIMSCI. To select this via the GUI, access is provided on by pressing the assay button on the toolbar, then navigate to Assay Cutpoints ==> Characterization Options ==> Criticals, Ideal-gas Enthalpy and Molecular Weight drop-down lists.

In addition to the new Heavy Oil method, some additional access to characterization methods previously available only through keywords was added to the GUI. They are:

Characterization - Cavett 1980 and Extended API 1980

Molecular weight - Cavett 1980 and Lee Kessler

References:

The method is described in a paper presented by Cal Spencer at the AIChE Spring Meeting in New Orleans in 2005.

New Kinematic Viscosity Methods

There are three new methods for calcuating kinematic viscosity. They are the Maxwell method, the Refutas method and the Chevron Bending Function Two. The Maxwell and Chevron are volumetric blending methods. The Refutas is a weight blending method. These methods are in addition to the SimSci, Index, User formula and User-index methods available in prior versions of PRO/II.

The keyword implementation is given on the METHOD statement. SIMSCI is the default.METHOD .., KVIS=SIMSCI or REFUTAS or CHEVRON or MAXWELL

or INDEX or USFO or USIN, ...

GUI access is given via the Thermodyanmic Data DEW ==> Modify ==> Refinery Inspection Properties. Select the Kinematic Viscosity

8 Important Notices

Property. The seven methods are selected from the Method drop-down list box.

Reference: Guide to Petroleum Product Blending by HIPE Consultants, Inc., 1989.

Chemdist Convergence Alternatives

There are two new choices for composition iteration variables. By default Chemdist will continue to use the Log of the composition. The user can now select a Linear iteration variable, or select an Adaptive method which changes the iteration variable of trace components as required.

The keyword implementation of these methods is given on the PARAMETER statement. LOG is the default.PARAMETER CHEMDIST,...,CVARIABLE=LOG or LINEAR or ADAPTIVE

To make an alternative selection via the GUI, access is provided on the Column DEW ==> Convergence Data ==> Composition Variable Option. This drop down has three options: Log, Linear and Adaptive.

The default choice is Log.When Log is chosen, Chemdist solves the distillation problem using ln(mole fraction) as the composition iteration variable. This allows the vapor liquid equilibrium equation (VLE) to be written in the ln formln(y) = ln(K) + ln(x)

For most non-ideal thermodynamic methods, ln(K) is more linear than K. Writing the VLE equation in this log form linearizes the equation and helps many chemicals problems to converge robustly. However, writing this form gives a high weighting to trace components. For certain problems with many trace components (i.e. composition below 1e-16) it was found that the Jacobian matrix became almost singular leading to poor convergence characteristics.

When Linear is selected, Chemdist will solve on x rather than ln(x). The VLE is written in the familiar linear formy = Kx

This reduces the impact of the trace components in the overall MESH (Mass, Energy, Summation, enthalpy) equation set.

For the Adaptive solution option, at the start of each column solution all components on all trays are set to Log. As the solution proceeds, Chemdist will switch each component iteration variable on each tray to Linear whenever it determines that that component is a trace component. Once a component on a given tray is determined to be a trace component it will not be switched back again to Log.


Adaptive is recommended if Chemdist fails to solve or is solving more slowly than expected, and trace components are present. Should that also fail, Linear can be tried. If the column comes to a converged solution the results will be the same within the domain created by the specified tolerances regardless of iteration variable chosen.

The Linear and Adaptive choices are valid with Chemdist simulations that have VLE. Chemdist columns with reactions (including those with reaction procedures) are handled. Chemdist with VLLE, liquid-liquid extractors (LLEX) and electrolytic distillation columns (ELDSIT) do not support Linear or Adaptive composition iteration variables.

Default changes in PRO/II v8.0:

1. Replace BK10 from the most commonly used thermo list with SRKM

2. New Output Report Defaults:

● Include Thermodynamic Input Parameters” will be turned on by default

● Include Overall Flowsheet Mass Balance” will be turned on by default

● Print Calculation Sequence Map in the Output’ will be turned on by default

Installation Notes

1. At the end of PRO/II 8.3 installation a dialog pops up asking for Restart, with YES/NO buttons. If user clicks No button PRO/II 8.3 libraries are not registered with TDM. User needs to restart before launching TDM from PRO/II 8.3.

2. PRO/II fails to launch with the default DEP setting on Windows Server 2003. To correct this problem, right-click on My Com-puter ==> 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

Note: Before executing any of the installation programs, disable all antivirus software running on your computer.

Note: Windows Server 2003 Operating System

10 Important Notices

DEP for essential Windows programs and services only. A reboot will be required before this setting takes effect.

3. Hysis™ Translator is not supported on Network Install.

4. In order for PRU to work properly in the Network/ Newuser install, the Newuser must be installed from a mapped network drive.

5. For a Network Install on a Windows XP® SP2 or Windows 2003 Server, read/write permission should be set for all groups of users. Failure to do that may result in the PRU not working properly.

Important information for uninstalling previous versions of PRO/II

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

7. Uninstalling PRO/II 7.1 will disable Visual flow 5.x. During the PRO/II 7.1 uninstall process, the "Simulation Sciences\PROII key is completely removed. The workaround is to export the "HKEY_LOCAL_MACHINES\Softwares\Simulation Sciences" keys to a .reg file, and then re-import the file after completing the uninstall. This issue has been addressed as starting with PROII 8.0 so uninstalling PROII 8.0 or PROII 8.1 will not affect installed versions of Visual flow.

Known Defects and Constraints using SIM4ME Reports

The following is a List of Known Defects and Constraints in using SIM4ME Reports.

1. Sometimes it seems that the last item selected (during multiple selects) is missing after a drag and drop operation. The observed behavior is a limitation in the current implementation. The "CONTROL" or "SHIFT" button needs to be held down until the drag-drop operation is completed. Also, "two consecutive


clicks" un-checks the last item. After performing a multiple drag and drop operations, the user should check that all the desired objects are highlighted in the Flowsheet Explorer. If anything is not highlighted, it will be copied with the rest of the selected objects. This happens most often when the user selects the last object once and then again clicks it to drag and drop. The second click un-checks the last item. What the user should do is select the last item and directly drag them all without another click.

2. Can I search for a stream "CRUDE" or a Unit Operation "PREHEATER" on the Flowsheet Explorer? Yes. In this case, go to "streams" and expand it. Now select "Streams" and type in the first few letters of the string you want to search "CRU". You will be navigated to the first match. Note that you need to expand "Streams" or "Unitops" to use the search functionality.

3. Why is it that I get "MISSING" values even when I uncheck "Show Missing Values" in the Report Manager settings? The option "Excel Comparison Report" may be "ON". In this option, the software just looks at the entire list of attributes and ignores the "Show Missing Values" check box.

4. I have selected "Excel Comparison Report" but Columns are not being compared. Why? Only unit operations that lend themselves to comparison are allowed in the "compare mode". For example, Streams/Flashes/HXs/Pumps/Expanders/Compressors have unchanging formats and can be compared side by side. Columns, Reactors, Controllers, etc. cannot be compared because of variations in report formats for individual units.

5. Energy UOMs in the PRO/II output report are reported as "MM BTU/hr" but the prefix "MM" is not used in SIM4ME reports. Why? The prefixes such as "MM" for millions when English units are selected, are not available. These prefixes may be included at a later date.

6. I dragged and dropped an attribute onto a particular row but it is added to the bottom. Why? Location specific attribute addition is not supported in this version of SIM4ME reports. It gets appended to the bottom of the Report pane only.

7. When I add/delete any attribute to a summary report, why does the name of the report change automatically? "Summary" and "Detailed" reports are standard, pre-configured reports. Once you start to customize these reports, the saved name is changed to avoid overwriting these reports. For example; If the user starts


with a "Summary Report" and then adds a unit operation, it gets renamed to "Summary ReportAdd1" to indicate that the report is based on the "Summary Report" with added objects.

8. Sometimes I do not see "Transport Properties" or "Refinery Inspection Properties" in my Excel reports. Why? "Transport Properties" and "Refinery Properties" must be selected in the PRO/II thermodynamics set for these values to be available in SIM4ME reports.

9. Sometimes I do not see Tray Hydraulics data when I drag and drop them onto the reports. Why? There are three options under "Perform Tray Sizing Calculations" in PRO/II Column. The first option "At output time" is the default. In this case, PRO/II updates these data only when the text output report is generated. If you generate SIM4ME reports before generating the text report, these data will not be available. If you generate the text report first, these data will become available and will be included in SIM4ME reports. You could also select either the second or third options under "Perform Tray Sizing Calculations" which will cause tray hydraulics calculations to be executed during the Run operation, in which case the data will be available to SIM4ME reports before creating the report.

10. In PRO/II output options; I have selected the option "Two reports, one in Input UOM, one in Output UOM". But, I do not see both UOM Slates in SIM4ME reports. Why? At this point, only the PRO/II Output slate is supported in SIM4ME Reports. You can manually select the desired SIM4ME UOM Slate under Reports Settings, Current UOM Slate.

11. Why don't my reports save the UOM information? I opened "Summary" report and changed the UOM Slate to "SI". I closed and re-opened the flowsheet to see that the UOM Slate has changed to PRO/II Output Slate. Why? The UOM Slate settings provide an option to temporarily override the UOM slate for the current reports only. These are temporary UOM overrides - they are not stored at this point. Once the report is closed and re-opened, the PRO/II Output UOM Slate is assumed. However, if you need some attributes always in a particular UOM slate irrespective of what slate is selected currently in PRO/II , you should define a new “view” by dragging and dropping the individual attributes. The name of the view will by default appear as Unitop_1 etc. These custom views also save the UOM. You might want to rename the view to “Unitop_SI” etc.


12. I tried to drag and drop individual elements of vectors. I see that the entire vector is dragged and dropped. Why? Drag and drop of individual elements is not yet supported in SIM4ME reports. Also, any operations like "Move Up, Move Down, Delete, and Format Cell" etc. do not work on individual elements of vectors. These will be addressed in future versions.

13. How do I generate formatted reports, e.g., TEMA reports, using SIM4ME reports? Formatted reports are not supported yet. They will be implemented in future versions of SIM4ME reports.

14. The Excel report generated using SIM4ME reports looks different from Tools->Spreadsheet. Why? Which one should I use? The SIM4ME reports is a new reporting tool that gives the user the flexibility of configuring the units and parameters that show up in the report whereas the spreadsheet option generates pre-defined reports. User can use either one based on their needs.

15. What happens when I import a report in a different simulation? You could import a report exported from "a1.prz" to "a2.prz". In this case, the units with same name and class in both files will be displayed. All the views in the imported file will be available for the simulation as local views.

16. If I have a custom view with the same name as global view which one takes precedence? The custom (local) view will take precedence.

17. Why is it that I see numbers displayed too many places after the decimal point? Is there a way to control the number of digits? In the current version, this is a limitation. You need to use the Excel features to control the display in the cells.

Known Defects and Constraints using SIM4ME Portal

The following is a List of Known Defects and Constraints in using SIM4ME Portal. Prior to v8.1.2 the PRO/II Portal would not work with Excel 2007. You can now use Excel 2007 in compatibility mode. The following is a more detailed list of limitations. T

1. Compatibility Mode

A new portal file gets created only in .xls format (Excel 97- 2003 Workbook: Compatibility Mode). While using a portal file in .xls format, there is constraint of having data within 65536th row and 256th (IV) column only.


2. Opening 2007 Excel Portal File

When the user saves the portal file with .xls format (using Save-As option) to any other 2007 format like .xlsx, .xlsm etc., the new formatted file can be connected to the simulation only by Doubleclick. The same file cannot be connected to the simulation through PRO/II GUI or through standalone mode.

3. Re-using 2007 Excel Portal File

If the user wants to re-use the same 2007 portal file (.xlsx, .xlsm) through PRO/II GUI or standalone mode as well, then it needs to be saved back in .xls format. (EXCEL 97-2003 Work-book: Compatibility Mode). But if the original 2007 Portal file has has data on and beyond 65536th row and/or 256th column, an "Office document customization is not available" error pops up.

4. Clicking on cancel in Compatibility Checker dialog is not recommened

Launch PORTAL in standalone mode, create a new file, connect to any prz, and drag drop any writeable variables change the value and click on run button.

Double click the existing portal file. The compatibility checker dialog pops up. If user Clicks on Cancel button, existing links in the portal file get broken. The portal file is temporarily not usable.

User has to close the portal file and reopen. When Compatibility checker dialog pops up select "continue" button.

5. In office 2007 Excel Portal file (.xlsx format), selecting complete excel sheet (Ctrl+A) throws an exception

If the user drag-drops any parameter with UOM on 2007 Excel Portal file (.xlsx format) and then selects the whole worksheet by clicking Ctrl+A, an exception error message pops up.

6. Windows XP Operating System other than English

If the operating system is Windows XP in any language other than English, then user is required to delete this registry key in order to view the flow sheet explorer/action pane.


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InternetEx-plorer\ ActiveXCompatibility\{5f61f809-422a-4152-91f5-9ec1b935efd7}

7. Pro/ll 8.1 has a built in logic to check portal 1.0 registry key. So when 8.3 is installed PRO/II 8.1 doesn't install portal 1.0 again. There will be a warning message instead.

If portal 1.00.0000 is installed over on later version [1.00.0012], it will cause downgrade a original portal 1.0 install does not han-dle upgrade.

8. There is no Horizontal Scroll bar implemented in flowsheet explorer. Very large captioned UnitOPs and Streams and their attributes may not be visible properly.

9. 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.

10. 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.

11. 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.

12. 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.

13. 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.

14. 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.

15. For the UnitOPs like Column, Controller, MVC, Splitter, etc. the performance specifications are shown without their long descriptions and UOM.

16. 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.

17. 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. Microsoft Excel 2003 Professional with SP2 or Microsoft Excel Professional 2007 is required.

18. 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 SIM-SCI\PROII83\Applib 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 and-browse 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:\SIMSCI\PROII83\User\Applib\S4MWorkbooks folder, namely:

- Multiple Dimulations Link_Chiller Plant - 1 and 2.xls


- Homotopy.xls

- ColumnProfile.xls

- Naphtha Assay_case Study.xls

19. Is there any security setting that we need to set in Excel in order to run Portal? Yes.

(a) It does not work with security setting “Very High”. It can be changed from Excel>Tools>Macro>security>Security Level 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 8.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.

The security option used is normally chosen during the install procedure. If you want to switch to a different security method after installation, use the following procedures.

To switch to USB security:

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

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

■ Save the file and exit.

To switch to FLEXlm security:


■ Find the section entitled [wss_Security] and set the “Type=” keyword to one of the following values

Type=FLXLM72 For FLEXlm version 7.2

Type=FLXLM95 For FLEXlm version 9.5


■ The version selected must match the version of the FLEXlm server that is used on your network. Please confirm with your system administrator the specific version of FLEXlm in use.


■ If you are running under Windows 2000/XP/2003/VISTA, add the IPASSI_LICENSE_FILE={FLXLM server host name} environment variable to your control panel/system/environment settings.

■ Reboot your computer so the changes to your security environment will be correctly configured.

To switch to TOKEN security:


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


■ If you are running under Windows 2000/XP/2003/VISTA, add the IPASSI_LICENSE_FILE={FLXLM server host name} environment variable to your control panel/system/environment settings.

■ Reboot your computer so the changes to your security environment will be correctly configured.

UAS/PDTS Capabilities

Incompatibility of Previous UAS Versions With PRO/II 8.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 2003 architecture probably could be used as alternatives, but none have been tested are certified for use with PRO/II.

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 2003 architecture for the Intel 10.1 compiler now are shipped with

Note: The Compaq Visual Fortran compiler (all versions) is not compatible with PRO/II version 8.3.


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 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 8.3 User-Added Subroutines

Older project files have been replaced by newer ones, often in different directories. 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 8.3.

New Files for PDTS Examples

New Visual Studio Net 2003 PDTS project files are installed in the default location:

C:\SIMSCI\PROII83\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.

These files replace older projects formerly located in directory C:\SIMSCI\PROII83\User\Pdts\Examples\VF6\. Project files in the VF6 subdirectory are incompatible with version 8.3.

New Files for Classic UAS Examples

New Visual Studio Net 2003 project files for the classic UAS interface are installed in the default location:

C:\SIMSCI\PROII83\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 2003.

UasLb.vfproj The only project in the delivered solution.

20 UAS/PDTS Capabilities

The flies listed above replace older project files previously located in C:\SIMSCI\PROII83\User\Uas\Examples\VF6\.

New Files for Modular UAS Examples

New Visual Studio Net 2003 project files for the modular UAS interface are installed in the default location:

C:\SIMSCI\PROII83\User\Uas\UasF90\IVF\

Modular UAS allows using a separate project for each implementation. As delivered, version 8.3 includes two projects: one for modular utilities and another for modular unit operations. The project files include:

ExUasF90.sln Open this solution file using Visual Studio NET 2003 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 2003 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 previ-ously located in the same directory.

Source code changes required for Intel Visual Fortran 10.1:

PRO/II 8.3 is 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 2003 uses a different run-time data structure that is incompatible with older architecture used by older compilers.

For example, Logical File Unit numbers (LFU’s) cannot be shared by the older and newer compilers. Assume PRO/II 8.3 under Net 2003 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 2003 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() 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 the PDTS application or UAS. To avoid problems, the utility subroutine PAWRITE has been 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

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

Running PDTS Applications

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”.

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.


Where to Find PRO/II 8.3 Documentation

Printed Documentation Included with this Package

■ Release Notes for PRO/II 8.3 (this document)

■ PES Installation Guide

■ PES Tutorial Guide

Online Documentation

■ PRO/II User Guide

■ SIM4ME Portal User Guide

■ SIM4ME Reports User Guide

■ TDM User Guide

■ PRO/II Keyword Manual

■ PRO/II Reference Manual

■ PRO/II Getting Started Guide

■ PRO/II Quick Reference Card

■ PRO/II Casebooks

■ PRO/II Application Briefs Manual

■ PRO/II LIBMGR and COMPS User’s Guide

■ Data Transfer System User’s Guide

■ User-Added Subroutines User’s Guide

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

■ PRO/II Interface Modules User’s Guide

■ SIMSCI Component and Thermodynamic Data Input Manual

■ PRO/II COM Server Reference Guide

■ PRO/II COM Server Programmer’s Guide and Tutorial

Note: The PRO/II Welcome screen for the online documentation can be found on the hard drive under the simsci\proii83\Manuals directory.


Summary of Defects Fixed in PRO/II 8.3Feature Bug Number Description

ACE HIPE#18178 The Air Cooled Exchanger can "converge" even if the tube side temperature specification is not met.

AMSIM HIPE#17295 Files containing Amsim unit operations files do not work on Network installs.

AMSIM LFPE#25595 When the AMSIM unit operation fails, the message popup is hidden and the PRO/II simulation seems to be stuck on the AMSIM unit.

Assay HIPE#18199 MABP, MeABP, CABP are not displayed in the stream property table.

Assay LFPE#26067 When lightends are present, the calculated TBP initial boiling point of streams will take on the value of the lowest boiling point component. It should take on the extrapolated value based on the curve fit.

Assay LFPE#26192 If there is a sharp inflection point at the very beginning of a user supplied assay curve, the boiling point of the first pseudocut might be in error. This might be true even if the inflection occurs in a place that is overwritten by lightend components. In one example, the TBP at 0.05% was at 0 F, and at 0.08% at 50 F. This is a sharp vertical that then levels off to a normal TBP curve. The first cut had an NBP of 20 when it should have been 100.

Assay HIPE#18199 MABP, MeABP, CABP are not displayed in the stream property table.

Assay LFPE#25153 The assay fit method FIT=PDF(EP) does not actually pass through end point.

Assay LFPE#25759 The View Curve feature in the Stream Assay input may have some artifacts at the low volume percentage range. In one case, the first component that boils at 9.5 C does not have it's step displayed from about 0 to 17 %

Assay LFPE#26065 File using GS thermo undergoes file bloating whenever you recalculate assay components. In the case of large flowsheets with large number of components, this can add up to a significant value. In one case, each recalc caused about 50kb of bloat on each recalc and save.

Batch Distillation

HIPE#17911 In a Batch Distillation column, some thermo sets that should be available for different trays in the thermo selection DEW are not.

26 Summary of Defects Fixed in PRO/II 8.3

Batch Distillation

LFPE#25390 In the Depressuring unit, the default "Maximum Step Size" for the Semi-Implicit Trapezoidal method is shown as 0.1 hr. However, if left at that default the calculation is actually based on 0.5 hr.

Breakpoint LFPE#25703 The breakpoint feature will work the first time, and will fail to stop on subsequent passes throught the object.

Cape Open HIPE#18391 The composition derivatives of fugacity communicated to Cape Open are set to "missing" (-1.5 e35).

Cape Open HIPE#18414 If the number of feed stream ports in a Cape Open unit exceeds the number of streams actually connected the feeds may not be mapped to the correct Cape Open feed slot once you open the Cape Open unit op.

Cape Open LFPE#25879 CAPE-OPEN Property Package error messages are not always communicated by PRO/II to the Message Window.

Cape Open HIPE#18700 When accessing HTRI via Cape Open, the answers may be incorrect if the PRO/II internal component order is inconsistent with the user supplied order. Normally this isn't a problem since most SIMSCI databank components are VLS (vapor, liquid and solid formers), and most PROCESS databank components are designated as VL. However, H2 is designated as a VL componenent in the SIMSCI databank. If it does not appear as the first component then HTRI will receive the components in scrambled order. The easiest way to test for this is to check the MW in the HTRI report and compare that to the PRO/II stream report. The workaround is to move H2 to the top of the component list.

Case Study LFPE#25155 The Case Study DEW displays a Calculator Result description incorrectly.

Column HIPE#17096 In one case, rerun a Ratefrac column from the converged state results in a column that doesn't converge.

Column LFCR#3148 Although it runs the first few times, a particular IO column begins to fail after repeated runs from the GUI.

Column LFPE#25274 Tray specific thermo information may be lost when the column algorithm is changed from EIO to SURE.

Column LFCR#3148 Although it runs the first few times, a particular IO column begins to fail after repeated runs from the GUI.

Feature Bug Number Description


Column LFCR#3529 For the SURE method the tray loading report, the liquid flow for one tray may be incorrect when water draws are present. The EIO method generates the correct tray loading report.

Column LFCR#3747 Changing and Enhanced IO column using VLW to VL only, then exporting, results in a VLW column in the keyword file. Importing brings you back to the VLW column and the user edit is lost.

Column HIPE#14110 Keygen with Results; The compositional estimates of L1 and L2 phases and the flowrates of L1 and L2 are not exported for the column.

Column LFPE#23432 The Overview button in Ratefrac Packing Options screen generates a missing Help file message.

Column LFPE#25275 If the overhead to a liquid-liquid is obve the bubble point temperature, the column is still "solved". Instead, it should have generated a not-solved solution with an error message that the liquids on tray 1 are above the bubble point temperature, and suggest increasing the pressure to resolve the problem. All product streams should be checked for the presence of vapor.

Column LFPE#25445 The View results for the reactive distillation shows wrong value for "TOTAL HEAT OF REACTION AT STANDARD CONDITIONS"

Column LFPE#25699 Change in Separate/Not Separate is not reflected across all IO merged columns in the GUI. The flag is the same for all columns within the merged unit but the DEW display will continue to show whatever was previously shown for that subcolumn even if it's been changed for others.

Column LFPE#25699 Column using Regular Solution Theory Thermo and water decant stream imports and runs in both v8.1.3 and v8.2, but gives an error in File Convert to v8.2. Note that this feature did not exist prior to v8.1.3.

Column LFPE#26140 In the column seight flow report, the weight rate for the feed to the column is calculated with a dry (water decanted away) stream MW. Should be calculated on a wet basis.

Column LFPE#25342 While the user is required to supply an activation energy for the kinetic reactions used in CSTR and plugflow reactors, however, this is not true for kinetic reactions in the column. The activation energy is defaulted to 0.0 which is most probably a bad assumption.

Column LFPE#25343 After importing a file, the time units in the reaction rate expression assumes global diminsions even if it is explicitly defined differently. OK via GUI.



Column LFPE#25991 The weight units View Report for eldist columns are wrong. Other columns are OK, and mole units are OK.

Component HIPE#18066 The component Isodecanol is not present in the SIMSCI although it is present in the PROCESS databank. SIMSCI should be a superset of PROCESS.

Component HIPE#18231 Changing the reference phase in the Heat of Formation DEW causes data in the Fixed Properties DEW to appear as "missing".

Component LFPE#26449 Adding components is slow in some cases - related to the number of libraries registered. This becomes much more obvious when computers are migrated to Microsoft's Active Directory configuration.

Component LFPE#26670 With Component reprint turned on, the databank listed for each component may be paired with the wrong component. This happens when Petro and Libid components are interspersed rather than being grouped together.

Component LFPE#26051 Importing a file with a bad component number on the UNIFAC STRUCTURE statement causes an abort.

Component LFPE#25158 The ideal gas enthalpy that is defined with temperature UOM of F or C results in failure to calculate entropy. Changing UOM to R or K does not immediately fix the problem.

Copy Paste LFPE#23740 Copy/Paste special does not copy non-MW solids.

Crystallizer LFPE#25499 A crystallizer unit operation that fails on the first run, solves to an incorrect solution on the second run. The final duty of the first run was assumed as the duty spec on the second run even though the user specified duty was 0.0

Data Review Window

LFCR#3691 When using the European convention of commas instead of periods for decimal notation, the UOM conversion in the Data Review Window is not precise. Switching back and forth between F and C results in a numerical creep of -158,750F to -105,556C to 158,000F. This problem doesn't occur with periods.

Data Review Window

LFPE#25754 Liquid volume units set to 1000*API BBL causes Data Review Window to display flow in lbmoles/day instead of 1000BBL/day/hr.

Depressuring LFCR#3663 Adding an additional stream to the vent port of the depressuring unit causes that stream to be red. Open and OK the unit op DEW to clear. It should have connected as black because it doesn't require additional data in the unit op to be complete.



Depressuring LFPE#25357 The Depressuring unit VOLFACTOR input is restricted to .1 < VOLF < 2.0 via keywords. It should be VOLF > 0.0. The GUI is correct.

Depressuring LFPE#25359 When the Depressuring step time is given, the step calculation method is disabled. However, File/Export still writes out the CSTEP keyword and PROIN flags it as an error upon import. The CSTEP keyword should not be written out.

Depressuring LFPE#25323 When the Depressuring unit valve constant is changed by the Casestudy, the case study thinks the valve constant was changed by the unit and therefore can't be changed by Casestudy. It returns an error message and stops.

Depressuring LFPE#26148 After generating the legitimate warning"** MESSAGE ** UNIT 3, 'DP2' - Depressuring calculations terminated - Valve back pressure (PBACK) exceeds the pressure in the vessel. and PRO/II reports an incorrect vessel volume. Previous time steps are OK.

Dissolver LFPE#25352 A dissolver that failed because the solubility limit was reached, should have solved at that solution.

Documentation LFPE#25199 The installation package for the v8.2 copies the v8.1 Release Notes into the Manual folder, not the v8.2 Release Notes. If you launch the release notes from welcome.pdf you will get v8.1 information only.

Electrolytes LFCR#3741 The column component estimates embedded in the .p2i file are wrong when OLI MSE thermo is used. This results in imported columns not solving even though the original .p2i file was written out from a converged case.

Electrolytes HIPE#10087 Remove help for EUP which is an obsolete program.

Electrolytes LFPE#26386 OLI returns different apparent compositions and pH's depending on whether a stream has been recommited. In one case the pH changed from 8.0 to 8.2 after a restore/input operation.

ExcelUaUOP HIPE#18175 When we click on Overview or Help button in Excel Unit Operation, the program generates the following error message: Cannot find the D:\SIMSCI82\PROII82\Hlp\p2help.hlp Help file. The Help system fails to launch.

ExcelUaUOP LFPE#25371 OLI returns different apparent compositions and pH's depending on whether a stream has been recommited. In one case the pH changed from 8.0 to 8.2 after a restore/input operation.



Exculeded Unit Op

HIPE#18008 Excluding any unit operation which is already connected to an excluded unit op does not turn the connecting stream RED.

File HIPE#17633 Opening and closing a .prz file through COM may result in the calc engine files (.pr1,2,3) being left outside the .prz archive.

Flash LFPE#25179 A pressure-temperature flash with GPSA thermo and a large number of pseudo-components fails.

Furnace LFPE#25105 In the Furnace, for some UOM systems the Gas to Tube U * A value exported to keywords is wrong. In this case, the UOM for ENERGY is is KJ and that for the HTCOEFF is KJ/Hr.

Furnace LFPE#25509 The Firing Duty for the Furnace is not available as a Calculator Define via the GUI. It's available through keywords.

Furnace LFPE#25583 In the Furnace unit operation with fuel gas containing inerts, the unit may fail with the message *** ERROR *** UNIT 7, '101-BU' - Insufficient Calorific value of Fuel, Unit even though there is plenty of fuel to fire the furnace.

Furnace LFPE#26295 In one case a fired heater failed to converge for a particuilar fuel flowrate, when convergence was obtained for a flowrate just a little more or a little less. It should have converged at the specified rate too.

HCurve HIPE#17757 SIM4ME Report can not access the Heating-Cooling curve latenet heat unless the General print option is turned on.

HCurve LFPE#26186 Heating-cooling curve vapor fraction values are incorrect in Sim4Me reports. Water is not being taken into account.

Help LFPE#26059 Clicking on Sim4Me Reports Help points you to p2help.hlp instead of p2help.chm. p2help.hlp is the old format and no longer exists after v8.1.0. After an appropriate warning, Sim4Me Reports shuts down.

Help LFCR#3674 Right-click on the right-hand panel of the Reference Manual Help crashes PRO/II.

Hot Key LFPE#25416 The hydrate curve with 40% methanol inhibitor is irregular.

HTRI/HTFS LFPE#25956 Pure water stream properties are not communicated to the Cape Open HTRI unit. HTRI then generates error messages concerning missing viscosity, etc.

HX LFPE#25381 A failed feed flash to the simple heat exchanger unit did not result in the HX failing.



HX LFPE#25685 In one case, a simple heat exchanger unit with a hot-side utility and a UA spec failed when the equivalent exchanger using a duty spec solved.

HX LFPE#25894 Simple HX unit using air-cooled exchanger icon fails with the message *** ERROR *** Stream 'S4' CANNOT BE used BOTH as A FEED AND A PRODUCT of unit operation 1.The standard HX icon works OK.

HXRIG LFPE#25654 The Area required per shell may be different in Tools/Spreadsheet/Rigorous Exchangers is wrong due to a bad UOM conversion. The value given in the .out file is correct

Hydrate LFPE#25304 Increasing the number of evaluation points in hydrate calculations rom default 30 to 100 brings about a large discrepancy in the pressure.

Hydrate LFPE#25377 Hydrate curve with 20% MeOH inhibitor has discontinuity at 42 bar pressure.

Import LFCR#3472 Importing files with Stream Report Writers may result in a spurious unsupported "INCHECK" message, even though no INCHECK keyword is present. Even if it were, INCHECK is irrelevant within the GUI environment and should have been accepted silently.

Import LFCR#3472 Importing files with Stream Report Writers may result in a spurious unsupported "INCHECK" message, even though no INCHECK keyword is present. Even if it were, INCHECK is irrelevant within the GUI environment and should have been accepted silently.

Import LFPE#25641 Importing a file with an existing .sfd (graphics) file leads to an access violation exception if the .sfd contains a block diagram.

Import LFCR#3236 Changing the feed stream to a unit in the keyword file is not detected upon reimport. It should generate a warning message and create a new layout.

Install HIPE#18186 After some install/uninstall sequences, upon running of PRO/II get message saying the PESGUIMain.dll not loaded.

Install LFPE#25494 Sim4Me Portal does not install in the presence of Excel 2002, which is correct behavior. However, it does not issue any kind of diagnostic to tell the user why the Portal didn't install. The first indication of trouble is when the user actually attempts to use the Portal and it won't launch, again without diagnostic.

Install LFPE#25667 The usage icon under Start\SimSci\PROII82 launches the documentation Welcome screen instead of the usage program.



Install LFPE#25889 v8.2 won't install on Home XP or any sub-flavor (Premium, Ultimate). This restriction needs to be removed.

Install HICF#509 In a machine with other than Office 2003 or 2007;Installing PROII patch X simply uninstalls Portal 1.0 (if present). Should issue a diagnostic saying that no supported version of Excel is available.

Install LFPE#25619 Starting with v8.2.1, the Common Diagnostics feature may not purge it's files correctly. This results in a Buffer Overrun Detected! message coming out of PROII.EXE. The workaround in v8.2.1 is to manually delete all the files in C:\Documents and Settings\user_name\My Documents\Simsci\InstallationDiagnostics. Deleting these files does no harm.

Membrane LFPE#26004 Membrane unit with permeation parameter DEFINED to calculator result errors out for lack of permeation parameter.

Output LFCR#3625 In some cases, small numbers such as 1e-120 were being reported as actual value rather than zero in .p2i files and output reports.

Output LFCR#3627 Run batch from keywords, the dry flowrate is missing for an all dry-vapor stream in the stream summary report.

Output LFPE#25354 The is no error message when sufficient disk space is not available for Pro/II to write its ouput files.

PFD LFPE#25280 File conversion of flowsheet with excluded unit operations does not recover the original flowsheet lay out.

PFD LFCR#3457 Changing the default unit display style does not persist from one session of Pro/II to the next.

PFD HIPE#17634 Pro/II crashes when “Turn on DEP for all programs and services except those I select” is selected. This is a common setting with Windows Server 2003. When “Turn on DEP for essential Windows programs and services only”, Pro/II does not crash.

PFD LFCR#3675 After deleting and then recreating a page on a PFD, printing that page causes an exception.

PFD LFPE#24928 Rerunning a file after generating a Sim4Me Report may result in PRO/II hanging.

PFD LFPE#25280 File conversion of flowsheet with excluded unit operations does not recover the original flowsheet lay out.

PFE HIPE#18383 PFE32 may crash in Vista. The fix in v8.3 does not address the problem wrt to Japanese Vista. A workaround is to use a currently maintained text editor such as Notepad++.exe.



Pipe HIPE#18190 The Pipe Unit Duty is a user specified value but in the SIM4Me Portal it is colored green indicating it is a read-only/output parameter.

Pipe LFPE#25344 The nominal dia for pipe unit in SIM4ME portal displays wrong value.

Pipe LFPE#26317 When the Pipe unit fails because of missing length, it does not populate all the output parameters that it could (such as diameter). If a Calculator retrieves one of these missing items it stops.

Polymers LFPE#25689 Running a file with ALM (polymer) thermo with around 110 components results in Access Violation exception.

PPIntegration HIPE#17498 With Pipephase 9.0 installed on a machine, importing a PRO/II file with an embedded Pipephase unit operation infrequently results in the message "Error Detected in Pipehase Preprocessor". Click OK and the model will run normally. This message also comes up when you open the Pipehase unit GUI.

PPIntegration HIPE#16952 If there is an embedded Pipephase unit operation with a simulation using Pipephase v9.0, but Pipephase v9.1 is installed on the machine, may fail even if the Pipephase simulation works on a standalone v9.1 installation.

Reactor LFCR#3443 The Gibbs reactor does not persist user's selection to use component rate estimates. When you return to the DEW it switches back to PRO/II default of supplying no estimates.

Reactor LFCR#3828 PFR accepts IDATA=0 and the value of 'TIN' being defined. However, when imported, get an exception for IDATA=0 and also, definition for TIN is not accepted.

Reactor HIPE#17447 An incorrect error message is generated when the reaction order is changed for a reactant. If the order is a non-integer value, once the dew is comitted and revisited, all the reaction orders are set to zero.

Reactor LFPE#25102 Plug Flow Reactor with single component coolant stream under UNIQUAC thermo failed the coolant inlet flash.

Reactor LFPE#25103 The Plug Flow Reactor results change depending on how many printout points are requested. The actual number of integration steps used is incorrectly influenced by the number of printout points.

Reactor LFPE#25447 The Heat of reaction is calculated from the Heat of formation at 25 C, Vapour State. The user should get a warning message when Hf is given on the basis of liquid phase.



Reactor LFPE#25531 I one case, a conversion reaction with the limiting conversion reaction set to "reduce" (XOPTION=REDU) resulted in all the reactions in reduced to zero even though some of there was room for some reaction to occur.

Reactor LFPE#25992 Confusing error message when Gibbs atomic groups are specified "No reaction is possible because each component is specified as a unique group. Try specifying multiple components for each group." even though all groups do have multiple components.

Reactor HIPE#18586 The GUI allows entry of reaction equilibrium data for shift and methanation reactions, however they are not used if entered. Data entry for these fields should be disabled.

Reactor LFPE#25298 Plugflow reactors with multiple stoichiometries in the reaction set will only accept pre-exponential and activation energy changes from the Portal for the first four expressions.

Reactor LFPE#25330 Change the Reaction Set in the conversion reactor can result in an access violation.

Reactor LFPE#25532 In a conversion reaction, if the no-reaction is invoked (XOPTION=NORX) for some of the stoichiometries when negative compositions are encountered the heat of reaction may be wrong.

Reactor LFPE#25962 The presence of a trace amount of a component in the equilibrium reactor could cause the reactor to fail.

Refinery Inspection Properties

HIPE#17743 The value of the RON for cyclopentane filled by the Simsci method is 0. It should be around 100.


HIPE#18498 N- paraffin is missing from the Thermo/Modify/Refinery Inspection Properities drop-down list. It is available as a spec, however.


HIPE#18220 In some cases the Smoke point is reported off by a factor of 1e-3 - a value of 15 would be reported as 0.015.


LFPE#25347 Deleting a component with KVIS Refinery Inspection Property in a very large file causes exception error and PRO/II shutdown. Smaller files works OK.


LFPE#26177 With POUR NCFILL=API, the pour point for some of the assay components is not being calculated when the specific gravity for that component exceeds the correlation limits. This condition needs a warning message.

Run LFPE#26276 RUNP2 "path\filename" (run from command prompt) doesn't work if there is a space in the path.



Security LFPE#25564 When PRO/II 8.2 is launched using FLEXlm 7.2, users get the blank error message box. The message was supposed to contain the license expiration data.

Sim4Me Reports

BI1#3079 When attempting to launch Sim4Me Reports if the PRO/II file hasn't been saved first, nothing happens. PRO/II needs a message to inform the user that he/she needs to save the file first.

Sim4Me Portal LFPE#25506 The Cp of streams is not reported in Sim4Me Portal.

Solids LFPE#25389 Many of the cyclone unit operation results are shown as N/A in the Sim4Me reports. Values are available in the standard output report.

Solid Unit LFPE#25864 The check solid unit operation sometimes generates a UTP (Unable To Predict) message near the bubble point. Solutions should be possible in this region.

Spec Vary Define

LFPE#26120 The 'Percent of Flood' can not be retrived using the Calculator for all algorithms except Ratefrac. 0.0 is reported instead of the value shown in the column output report.

Spec Vary Define

LFCR#3684 In some cases the Z value of a stream retreived by the Calculator was wrong.

Spec Vary Define

LFCR#3833 DEFINE a parameter to a non-existing Calculator Result results in a cryptic error message:*** ERROR *** An INVALID VAT flag was DETECTED in VATDECODE.and still gives you Solution Reached with a bad answer. This should result in a more meaningful error message and fail the simulation.

Spec Vary Define

LFPE#24942 PRO/II allows a pressure spec on a column, which should be illegal.

Spec Vary Define

LFPE#26066 Tray diameter and Max Percent Flood are not communicated to Case study results. They show up as 0.0 and missing respectively on Case Study reports.

Spreadsheet Tools

HIPE#17870 In one instance with Excel 2007 installed, PRO/II 8.2 can't launch Excel plotter with the following message:Excel Plot Driver: Unable to launch Microsoft Excel using the command line "C:\PROGRA~1\MICROS~2\OFFICE11\EXCEL.EXE /e". Path not found. However, the path information is correct in Options/Plot Setup.

Start SC1#8620 PRO/II can crash if the Windows DEP setting is turned on to enabled.

Stream BI1#2710 Sim4Me Reports displays 0.0 instead of n/a for the some of the properties of a non-existent phase.



Stream HIPE#18868 The actual bulk density (BulkDensityAct) is missing in the SrBulkProp object accessed through the COM layer.

Stream LFPE#26353 Copy/Paste Special does not copy the polymer components.

Stream LFPE#26618 The calculated molecular weight and weight flowrates are not being updated correctly in Sim4Me workbooks after changing the composition of input stream values in the Portal, and running.

Stream LFCR#3450 A stream in SIM4ME Portal may identify the wrong thermo method than what is used in the simulation. The standard output report has the identifies the correct method.

Stream LFCR#3736 A reference stream feed to a Reset unit operation may adopt the thermo of the restet unit rather than the source stream for the reference.

Stream HIPE#18570 An unused thermo where kinematic viscosity is unavailable may cause the kinematic viscoisty to be reported as n/a for thermo sets where it is available.

Stream LFPE#24899 The feed stream to a unit operation is displayed as blue even though the stream flash does not solve.

Stream LFPE#26050 Update Stream Recycle from current calc state does not copy non-libid component rates to input. When you open the recycle stream and view it's initial estimates, non-libs have a blank value for rate/composition.

Stream Property Table

LFCR#3732 When multiple assay streams are present using different blends, the Stream Property Table may use the MW from the wrong blend components in calculating the weight rate.


LFPE#25176 The Stream Property Table does reports output volumetric flowrate in output units as requested, but based on input units standard conditions.


LFPE#26057 With input units in English and output units in SI, a Stream Property Table actual flow rate set to output units does not take into account the shift in standard state from 60 F to 0 C.


LFPE#26659 Electrolyte system with a large number of components (for example, 276) only displays 16 components on the Stream Property Table.

Tags LFPE#26184 If an assay stream has a tag on it that is placed before a compositional stream, some of the stream flowrates might be wrong. OK in v8.2.0, bad in v8.2.1.

Tags LFCR#3753 The TAGFILE entry on the TITLE statement must be the last item on that statement. PRO/II will not recognize statement entries beyond that.



TDM Integration

HIPE#18167 This is a problem that occurs in v8.1 after installing v8.2. Closing TDM gives spurious error message that TDMServer Module has encountered a problem and needs to close. However, the TDM session and the continuing PRO/II session are completely successful.

TDM Integration

HIPE#18330 When TDM is launched from the PRO/II Component Selection-Databank Search Order button. the TOOLS\ADD\NEW COMPONENT button is disabled. It should be enabled. The workaround is to add the component with a right-click on the databank icon.

Thermo HICF#273 There are a number of properties that cannot be modified in TDM yet. They include - Component Name- CASNO- MOLFORMULA- SIMSCIID- Standard Liquid Density (Not Specific Gravity)- Reference Phase for Heats of Formation- Carbon Number- Hydrogen Deficiency Number

Thermo HIPE#17904 Some bad values "1.#QNB " are printed in strem property table when Correlation 54 is used for calculating enthalpy. They are shown as missing in the standard output report.

Thermo LFCR#3666 The Tacite package refers to "Tacite" K-values and enthalpies. There is no such thing - these should be PR.

Thermo HIPE#17904 Some bad values "1.#QNB " are printed in strem property table when Correlation 54 is used for calculating enthalpy. They are shown as missing in the standard output report.

Thermo HIPE#18112 The Online help for the UNIFAC structures dew does not exist.

Thermo HIPE#18617 In one case with user-supplied Peng-Robinson interaction parameters and a dumb-bell mixture of light and heavy components, the phase envelope unit operation reports dew-points on both sides of the critical point, along the phase envelope curve.

Thermo LFPE#24241 In some cases, importing a file with Henry's Law data does not allow all of the data to be correctly displayed in the GUI. The Run results are correct, however.

Thermo LFPE#25276 After importing a liquid-liquid column problem with print options, opening the column DEW generates a message that print options will be deleted, Continue (Yes/No)? Selecting No results in an LL column with VL phases. The print options are supported via keywords and should be supported via GUI.



Thermo LFPE#25518 The PEN statement (for Penetration) is no longer accepted in the THERMO section. It should be.

Thermo LFPE#25540 Refinery Inpsection Properties for petroleum components are not getting filled in for alternate thermo sets for streams passing through the reset unit operation.

Thermo LFPE#25704 The solubility of water in hydrocarbon using the SimSci solubility method, changed when H2S, CO2 or H2 are present. This change occured in patch 1 (v8.2.1), and is not present on other versions.

Toolbar LFPE#25740 Spurious shutdowns in Japanese Vista with messages similar to:1st message PRO/II w/PROVISION stopped working.Collecting information now. This will take several minutes.2nd message (after 1st message disappear)PRO/II w/PROVISION stopped working.In order to problems, program couldn’t work properly. Program will be closed.If there are solutions, WINDOWS will report to you.

Toolbar HIPE#18208 Text entered into the Problem Description entry field through OPTION\Simulation Defaults \ Problem Description is not getting transferred to new flowsheets.

UOM LFPE#26354 Keyword files with PC given in KG/CM2G get understood as KG/CM rather than KG/CMG (the valid keywords for that argument). To accomodate existing (but incorrect) files that use KG/CM2G, need to add that as an alias to KG/CMG.

UOM LFCR#3176 When area units are different from default on a simple heat exchanger UA spec, the exported file fails to contain the area UOM argument. On importing, the UA value is numerically correct but for the wrong units.

UOM LFCR#3176 The associated UOM cells attached to an Excel value cells in the Portal does not drag and drop together with the value.

UOM LFPE#24878 The gauge pressure basis used in View Results gets changed after the output report is generated if the pbasis in Output Diminesions is different from Input Dimensions.

View Results LFPE#24878 View results on the column that fails to converge results in rerunning of the column. It does not show the results.



Summary of Defects Fixed in PRO/II 8.2 PatchesFeature Bug Number Description

Assay LFPE#25115 Files with multiple blends may have streams with incorrect flowrates when those streams are OKed through the GUI.

Batch Distillation

HIPE#18035 Batch Column error messages use PRO/II internalSI units. They should use the user-specified problem UOMs.

Check Solid LFPE#25864 The check solid unit operation sometimes generates a UTP (Unable To Predict) message near the bubble point. Solutions should be possible in this region.

Column LFPE#25598 The overhead of a liquid-liquid column might possibly not be in strict phase equilibrium. In one case, the overhead of a liquid-liquid column was, on reflash, only 99.5% L1 phase, and 0.5% L2 phase. It should be 100% L1 phase.

Column HIPE#18042 A spec containing a reference to a feed stream in a Sure Column results in a misleading error messages. The message refers to a missing or incorrect stream label.

Column LFPE#24895 With the Ratefrac unit operation, you get an error message that IMTP packing #40 doesn't have size info. Other packings are OK.

Column LFPE#25110 One instance of the SURE column tray 1 not being in mass balance.

Column LFPE#25111 The presence of a feed that has zero flowrate to the column results in its failure. It converges w/o that feed.

Column LFCR#3626 Column using Regular Solution Theory Thermo and water decant stream imports and runs in both v8.1.3 and v8.2, but gives an error in File Convert to v8.2. Note that this feature did not exist prior to v8.1.3.

Component LFPE#25126 Visiting a Petro component density correlationcauses PRO/II to lose that correlation on OK. Run, and you get a Ideal Enthalpy correlation missing error. Export/Import to clear.

Component LFPE#25132 Visiting a Petro component density correlationcauses PRO/II to lose that correlation on OK. Run, and you get a Ideal Enthalpy correlationmissing error. Export/Import to clear.

ComponentHICF#823

Importing file with a duplicate component numbermay cause an exception. It should be errored onon import.

40 Summary of Defects Fixed in PRO/II 8.2 Patches

Depressuring HIPE#15012 Depending on units of measure, exporting a file with depressuring with user supplied Cp may result in a bad value being exported.

Documentation LFPE#25334 Linking to "Getting Started" and "Release Notes" from the Welcome.pdf file results in version 8.2 documents being opened.

HCurve LFPE#25051 The Sim4Me Reports for the heating-cooling curve does not print the right number of data points.

HCurve LFPE#25052 If you select N points for an HCURVE, PRO/II will generate N + i points where i is the number of phase boundaries crossed. S4MPortal always generates N + 1 points. If there are no phase boundaries then Sim4Me Portal one extra point with junk values. If there are two phase boundaries then Sim4Me Reports fails to report the last point.

HCurve LFPE#25053 Sim4Me Reports for HCURVE fails to report phaseboundaries.

Help LFPE#25195 The Zero Fill method is missing for some Refinery Inspection Properties including:1. Paraffin Content (ISO or Total)2. Naphthene content3. Olefin (MONO or Branched or Cyclic)4. Aromatics (Ring or Total)

HXRig HIPE#18159 The Rigorous Heat Exchanger tube length is reporting as **** in the TEMA datasheet and Extended TEMA datasheet if the length is more than 4 digits long.

HXRig LFPE#25711 n one case, the HXRIG unit ignores the calculated delta P, or the user supplied delta P override. The problem is due to a flash failure - the HXRIG should have failed.

Import LFCR#3823 If a reference stream is used twice in a flowsheet, upon importing to GUI it is not replicated correctly, losing the rate if provided. For example if stream S5 is used twice as a unit op feed, PROPERTY STREAM=S5, REFSTREAM=S4, RATE(M)=100 the S5-REF that is supposed to clone S5 on import is missing the 100 mole rate and will simply assume whatever rate value is in S4.

Output HIPE#17956 Launching Sim4Me Reports with Sim4Me Portal not installed causes no action to take place. It needs a warning to inform the user how to proceed.



PFD HIPE#18078 During file conversion, file having MS Excel objects embedded in PFD fails to preserve the flowsheet layout after conversion.

Pipe HIPE#18455 The enthalpy of pipe products where elevation change has occurred is not adjusted for changein static head.

Pipe LFPE#25283 The Pipe unit does not adjust the productenthalpy for static head.

Plot HIPE#18004 Many of the Sim4Me Reports plot options are notfully implemented and they display zero value for the full range.

Reactor HIPE#18029 Adding a new component to the component list might cause the Gibbs Reactor not to populate the product stream with that component unless the Reacting Components window under Reactor Data in the Gibbs Reactor is visited and OKed.

Reactor LFPE#25098 The Gibbs reactor has convergence problems when some of the components are defined as Fill from structure.

Reactor LFPE#25120 For equilibrium reactor with a solid component,the equilibrium expression does not change witha change in units of measure. OK for all equilibrium reactions without solids.

Reaction Data LFPE#25550 File convert reactor files from v7.1 and thekinetic data in some cases may be ported tov8.2 in Min instead of Hr.


LFPE#25427 Some of the RIPs are missing in the Sim4Me portal.

Run LFPE#25284 Double-click Output/Report Manager/Sim4Me Portal menu item will result in file dialogue menu hidden behind PRO/II. PRO/II appears to be frozen.

Security LFPE#25564 When PRO/II 8.2 is launched using FLEXlm 7.2,users get the blank error message box. Themessage was supposed to contain the licenseexpiration data.

Shortcut LFPE#25638 Regeneration of assay components may causean Access Exception if a Shortcut column is present in the flowsheet.

Spreadsheet Tools

LFPE#25152 Stream referenced to solid stream has rate specified in lb/hr, but gets prorated to moles/hr.

Stream LFCR#3496 Non-molecular weight solids component flow rates are not available in S4MReports.


42 Summary of Defects Fixed in PRO/II 8.2 Patches

Stream HIPE#18008 Excluding any unit operation which is alreadyconnected to an excluded unit op does not turn the connecting stream RED.


LFCR#3732 When multiple assay streams are present usingdifferent blends, the Stream Property Tablemay use the MW from the wrong blend components in calculating the weight rate.

Tags LFPE#25645 If an assay stream has a tag on it that isplaced before a compositional stream, someof the stream flowrates might be wrong. OKin v8.2.0, bad in v8.2.1.

TDM Integration

LFCR#3624 The Documentation Welcome.pdf file links to an obsolete TDM 3.0 manual instead of the TDM 3.2 manual.

Thermo LFPE#25639 Starting in v8.2.1, the density of water calculated by the IF97 method is infinity, thus the volumetric flowrate is 0.0.

Thermo LFPE#25864 The solubility of water in hydrocarbon usingthe SimSci solubility method, changed when H2S, CO2 or H2 are present. This change occured inpatch 1 (v8.2.1), and is not present on other versions.

Thermo HIPE#18108 Rackett parameters supplied in the user databank are not being used.

Thermo LFPE#24975 The Keenan & Keyes steam tables have a discontinuity for displayed liquid Cp for a narrow range around 13 372.40 F, 18.000 psia. Other properties are OK.

Thermo LFPE#25128 If BANK=NONE for TBC EOS, the SIMSCI databankis used. However, the output shows that "ALL PAIRS HAVE BEEN DEFAULTED TO IDEAL"

Tool Tip LFPE#24993 Tool tip cache not cleared out after Restore Input. If you hover over a stream the old values are displayed.

Unit Op Property Table

LFPE#25242 The HX Unit Operation Property Table reportsthe utility Cp on a molar basis rather than the expected mass basis.

UOM HIPE#18093 Starting with v8.2 PRO/II can import a filewith the "Kcal/h" UOM in addition to the customary "Kcal/hr". However, after importing the displayed UOM in some cases is KJoule/hr.

Unit HIPE#18088 Excluding any unit operation which is already connected to an excluded unit operation does not turn the connecting stream RED.



Summary of Open Defects in PRO/II 8.3

PRO/II 8.3 Bug Lists

To access the current version of PRO/II 8.3 bug list as well as FAQ and Updates, visit our website's Knowledge Base at http://www.simsci-esscor.com. Select Support Menu and then the Software Updates & Knowledge Base. Select Enter the SIM4ME Software Updates & Knowledge Base Website. Updates. Finally select PRO/II and enter in your personalized SIM4ME Username and Password.

If you do not have a SIM4ME username and password, please take a few minutes to register. Registration will allow you to access our complete Knowledge Base as well as allow us to display custom information of interest to you.

44 Summary of Open Defects in PRO/II 8.3

License and Copyright Information

Release Notes for PRO/II 8.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 © 2009 Invensys Systems, Inc. All rights reserved. No part of the material protected by this copyright may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying, recording, broadcasting, or by any information storage and retrieval system, without permission in writing from Invensys Systems, Inc.

Trademarks PRO/II, SIM4ME, HEXTRAN, INPLANT, PIPEPHASE, Invensys, and SimSci-Esscor are trademarks of Invensys plc, its subsidiaries, and affiliates. AMSIM is a trademark of DBR Schlumberger Canada Limited. RATEFRAC and BATCHFRAC are registered marks of KOCH-GLITSCH. Visual Fortran is a trademark of Intel Corporation. Windows XP, Windows Vista , Windows 2003 Server, Windows 2008, MS DOS and EXCEL are trademarks of Microsoft Corporation. FLEXlm is a trademark of Macrovision. Adobe, Acrobat, and Exchange are trademarks of Adobe Systems Inc. Intel and Pentium are registered marks of Intel Corp. All other products noted herein are trademarks of their respective companies.

U.S. GOVERNMENT RESTRICTED RIGHTS LEGEND

The Software and accompanying written materials are provided with restricted rights. Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data And Computer Software clause at DFARS 252.227-7013 or in subparagraphs (c) (1) and (2) of the Commercial Computer Software-Restricted Rights clause at 48 C.F.R. 52.227-19, as applicable. The Contractor/Manufacturer is: Invensys Systems, Inc. (a division of Invensys plc. and owner of the SimSci-Esscor brand) 26561 Rancho Parkway S., Lake Forest, CA 92630, USA.

Printed in the United States of America, May 2009.


46 License and Copyright Information

proii83 releasenotes

Documents

ipassilicensefileflxlm

hkeylocalmachinessoftwaressimulation

simulation

strem property

compaq visual

provision

excluded unit

stream property