PROII91 ReleaseNotes PDF

Important: Read First
Release Notes for PRO/II 9.1

Welcome to the release of PRO/II 9.1. These Release Notes supplement and supersede the corresponding sections in all PRO/II 9.1 documentation supplied with this release.
Contents
New Features of PRO/II 9.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Important Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Known issues in PRO/II 9.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Known issues in PRO/II 9.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Known issues in PRO/II 8.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 What is new/changed in PRO/II 9.0 . . . . . . . . . . . . . . . . . . . . . . 7 What is new/changed in PRO/II 8.3 . . . . . . . . . . . . . . . . . . . . . . 11 What is new/changed in PRO/II 8.2 . . . . . . . . . . . . . . . . . . . . . 13 Default changes in PRO/II v8.0: . . . . . . . . . . . . . . . . . . . . . . . . 17 Installation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Known Issues and Limitations in REFPROP Add-on . . . . . . . . 19 Known Defects and Constraints using SIM4ME Reports . . . . . Known Defects and Constraints using SIM4ME Portal . . . . . . Switching Security Types for PC. . . . . . . . . . . . . . . . . . . . . . . . UAS/PDTS Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 22 26 28
Where to Find PRO/II 9.1 Documentation . . . . . . . . . . . . . . . . . . . 34 Printed Documentation Included with this Package . . . . . . . . . 34 Online Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Summary of Defects Fixed in PRO/II 9.1. . . . . . . . . . . . . . . . . . . . 35 Summary of Defects Fixed in PRO/II 9.0 Patches . . . . . . . . . . . . . 41 Summary of Open Defects in PRO/II 9.1 . . . . . . . . . . . . . . . . . . . . 44 License and Copyright Information . . . . . . . . . . . . . . . . . . . . . . . . 45
PRO/II 9.1 Release Notes
New Features of PRO/II 9.1

The following enhancements have been made to PRO/II 9.1:
New Feature ACE-XACE Description - XACE is accessed by toggling it on from within the PRO/ II - ACE program. - XACE can be initialized by another XACE input file, or populated from data entered via the PRO/II ACE DEW - XACE input can be used to populate a PRO/II-ACE model. - Uses COM interface for speed and full functionality - A COM Server interface between PRO/II and HTRI replaces the .DAT files - The maximum number of pressure and temperature points on the property grid has been increased to 12 and 30 respectively, and can be adjusted by the user. Previously it was fixed at 3 and 10. Upgraded from Amsim 7.3 to Amsim 2011.1 (includes new features in Amsim 7.4) - Amsim 7.4: Mixed Physical and Chemical Solvent Process simulation (Sulfolane + MDEA and Sulfolane +DIPA). - Amsim 2011.1: Sterically hindered amine AMP (2-amino2-methyl-1-propanol ) New features for the Koch-Glitsch packing calculations include the following: - New packing types are added: MELLAPAKPLUS 352.Y, MELLAPAKPLUS 602.Y, N252.Y (PLASTIC) - New names for old packings: N125.Y to N125.Y (PLASTIC), N250.X to N250.X (PLASTIC), N250.Y to N250.Y (PLASTIC) New features for the Sulzer packing calculations include the following: - New packing types are added: MELLAPAKPLUS 352.Y, MELLAPAKPLUS 602.Y, N252.Y (PLASTIC) - New names for old packings: N125.Y to N125.Y (PLASTIC), N250.X to N250.X (PLASTIC), N250.Y to N250.Y (PLASTIC) "The following packings have been removed: All MELLADUR types (MD250Y, MD350Y, MD450Y), KERAPAK (KERA), OPTIFLOW C.36 (OFC36) This release provides print warning when Phase Envelope stream contains contains water, alerting the user to possible bad results. SIM4ME Portal 2.0.1 is upgraded to 2.1.1
HXRIG-XIST
AMSIM Update
Koch-Glitsch Packing Updates
Sulzer Packing Updates
Phase Envelope with Water SIM4ME Portal Upgrade
New Feature Integration with FRIfor Column Hydraulic Design
Description You can now select FRI Column Hydraulic rating as an option within the Column Hydraulics data entry window. Features include: - Provides full access to FRI hydraulic calculations during the course of PRO/II convergence - Calls FRI's DLLs directly for bi-directional communication - Uses familiar PRO/II data input windows to ease data entry - Data entry follows the FRI DRP program for data sufficiency - Generates comprehensive hydraulic reports are patterned after DRP output results - Requires an FRI license. FRI members should contact FRI. Your DRP license will work here. - Internals supported: -- Random packing -- Structured packing -- Trays ---- Valve ---- Sieve ---- Dual Flow ---- Baffle
Expanded Tray Previous versions contained tags for <vapor> and <liquid> Loading Data to flow properties. In general these were vapor to and KG-Tower and FRI liquid to values. However, vapor to from tray n might be different than vapor from for tray n+1, and similarly for liquid. It was up to the user to apply the correct flow properties for trays or packing. In v9.1 we now supply four new sets of tags for each stage: <vapor_from> <liquid_to> <vapor_to> <liquid_from> The PRO/II to KG-Tower interface program developed by Koch-Glitsch allows you to designate which flow is to be applied for rating each stage. For example, for tray rating where the load on the deck is limiting, you would choose "vapor to" and "liquid from". However, for random packing you might choose "liquid from" and "vapor from". Whatever you think is appropriate. Completion of Adjusted Vol Rate Project Better Phase Identification (V, L1, L2) The project with staged delivery started in v9.0 and was completed in v9.1. It allows for specification of streams and products based on user-defined standard conditions using the thermo set for that stream. The algorithm for identifying vapor, liquid 1 and liquid 2 phases near the critical have been improved. - It's less likely that streams will switch to a different product port as phase boundaries are crossed. - The ability to find the true upper dew point in the Flash unit operation has been improved.
New Feature Documentation
Description - The Reference Manual .pdf file has been deleted. All Reference Manual information will now reside in a single repository - the on-line Reference Manual. - The SimSci Add-ons Manual has been deleted. The content has been distributed: -- The chapters on electrolytic simulation have been placed in its own manual -- The chapters on polymers simulation have been placed in its own manual. -- Batch Distillation moved to On-line Help and Keyword Manual as a conventional unit operation. -- Batch Reactor moved to On-line Help and Keyword Manual as a conventional unit operation. -- Wiped Film Evaporator moved to On-line Help and Keyword Manual as a conventional unit operation. The OPC-UA Server is the next generation data server for all SimSci-Esscor Simulation Software. - Capable of exposing data and methods to any OPC-UA client. - Installed with latest versions of Dynsim, PRO/IITM, and ROMeo, and future generations of SimSci-Esscor software. - The PRO/II OPC-UA server is automatically visible through discovery services. Once installed, any OPC-UA client can find it. - This allows delivery of simulation services to a wide range of UI's and OPC UA client devices that support OPC-UA standards. Currently existing capabilities - Starting with v9.1, can be used by Sim4Me Portal -- Set by SIM4MEPortal.ini file: OPCUA="true" in C:\Program Files\Common Files\SimSci\SIM4MEPortal211\User - Romeo can access PRO/II data and launch PRO/II simulations via OPC-UA EDI client. - Similarly, any OPC-UA compliant client (including nonSimSci-Esscor) can access PRO/II data and methods - Download UaExpert for Windows (a generic OPC-UA client) from: http://www.unified-automation.com/view-details/opc-uaclients/81-uaexpert-for-windows-v1.2.0.htm Tear streams and references streams can now be easily identified from the GUI without need for generating output reports with these two features. - Color coding of recycle and tear streams on the PFD can be toggled on or off. - The Find Stream feature can be filtered for recycle and/or tear streams.
OPC UA Server
Tear and Reference Streams Identification in the GUI
New Feature Fugacity Activity Basis for Equilibrium Reactors
Description PRO/II allows equilibrium reactors to be defined with fugacities.
Important Notices
Compatibility with Earlier Versions of PRO/II
PRO/II 4.1x, PRO/II 5.0x, PRO/II 5.1x, 5.5x, 5.6x, 6.0x, 7.x, 8.0x , 8.1x, 8.2x, 8.3x and 9.0x database files will automatically be converted into PRO/II 9.1files as they are opened. The original file will be saved using an alternate file name.
Known issues in PRO/II 9.1

1. On some Japanese Vista installations, PRO/II cannot install completely because the required .net 3.5 will not install. Updating the Vista OS to SP2 will enable complete installation. Uninstalling certain features of PRO/II (such as OLI, REFPROP and MSM) will not work from Add-Remove if UAC (User Account Control) is turned on. You can still uninstall these using Setup, or, you can turn off UAC temporarily if your work site lets you. Installing v8.3 or earlier may unregister v9.1 libraries. Starting with v9.0, USB keys only allow a single instance of PRO/II to be open at a time. This is intended. If you need multiple instances of PRO/II open you need to have FlexNet security. MS Office 64 bit is not supported. Various Excel features (such as Spreadsheet Tools) will likely not work. On some windows server machines give an 'OPCUA server failed to start' error. The error is reproducible in the below configuration machine. Windows 2008 R2 comes with preinstalled .Net Framework 3.5.1. Users need to enable this feature from "Server Manager". i.e "You must use the role management tool to install or configure MICROSOFT .NET FRAMEWORK 3.5".After enabling the .Net Framework 3.5.1 feature from Service Manger install will go smoothly and OPCUA server also install without any issue.
2.
3. 4.
5. 6.

1. Uninstalling PRO/II 8.2 after installing PRO/II 9.0, the uninstall removes the Registered libraries in TDM and other products could launch TDM. Running RegisterP290.cmd from C:\SIMSCI\PROII90\TDM\BIN\RegisterP290.cmd, TDM in PRO/II90 will launch.

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. In Residue Curves, when a new workbook is created, the toolbar gets deactivated for all open workbooks. This is EXCEL behavior. For this reason we cannot have a warning message on a workbook basis. Previously, distillation columns in recycle loops recalculated in every recycle iteration. Now, improved logic tests a solved column to determine if it needs to resolve. When no changes are detected in the feeds, column operating conditions, or options, nothing affects the solution. In each iteration where this is found, the column calculations are skipped so they are not repeated. Previously, restarting a solved column began calculations at the solved state. In many cases, the results drifted due to the different starting point. Now, restarted columns always restart using original initial conditions. This eliminates any drift in results in most cases.
2.
3.
What is new/changed in PRO/II 9.1

For users of KGTower The interface converting tower hydraulic information in PRO/II to a file that can be read by KG-TOWER software, is updated for the release of KG-TOWER version 5.0 which is currently available from Koch-Glitsch. Link to upgrade to KG-TOWER 5.0 http://www.koch-glitsch.com/software/pages/KGTOWER_downloadmain.aspx?ID=lweroiuxycblhjsdfouwerljksdfouwer43587sdji245kj wr897
6 Important Notices

The aqueous flowrates of the iconic species were previously available only in the output report. The other forms of output reports (SIM4ME Reports, spread sheet tools, SIM4ME Portal) were added to PRO/II 8.3 Patch 1 but were overlooked in the patch 1 readme file. New Adjusted Standard Conditions, Volumes, and Volume Rates PRO/II uses different standard conditions for different systems of dimensional units. These differences cause a simulation to reach different solutions when re-run using a different system of units of measure. Also, support for user-defined standard conditions, volumes, and volume rates was limited. These have caused chronic problems for users. PRO.II version 8.3.2 introduces extensive enhancements to address them. Enhanced user-defined standard conditions separate from and in addition to default standard conditions. User-supplied values now constitute new "adjusted standard conditions" that apply to liquid as well as vapor. Adjusted standard vapor volumes are computed using vapor density methods in thermodynamic METHOD sets. Standard vapor volume still is computed using the ideal gas law. Adjusted standard liquid volumes are computed using liquid density methods in thermodynamic METHOD sets. Standard liquid volumes still are computed at default standard conditions, not from user-supplied values. Stream total rates may be specified using the new adjusted standard volume rates. Composition, assay, and referencing streams support these new options. Unit operations that allow product rate specifications using the new adjusted standard volumes include: flash drum, splitter, column, controller, MVC, optimizer, and calculator. Calculators also provide new functions to retrieve adjusted standard volume rates from streams. Utility subroutine SRXSTR supports new argument options that change total stream rate using the new adjusted standard volume rates. DEFINE statements that define calculator
PRO/II 9.1 Release Notes 7
parameters can retrieve the stream rates using the new adjusted standard volume rates. Upstream unit operations now report Gas/Oil Ratio (GOR) using the new adjusted standard rates. Interface subroutines UDENS and DUDENS allow user-added subroutines and PDTS applications to calculate density at vapor or liquid adjusted standard conditions. New options in stream reports and the Stream Report Writer support the new adjusted standard vapor and liquid volume rates. New footnotes automatically appear on pages that display these properties. For a comprehensive introduction to these enhancements, refer to the new technical bulletin "Adjusted Standard Conditions & Adjusted Standard Volume Rates". It is available in the "Manual" directory where PRO/II installs all the other documents. RATEFRAC now supports electrolyte thermodynamics for equilibrium and non equilibrium systems. To use RATEFRAC with electrolytes, v7 OLI chemistry models must be used. RATEFRAC/Electrolytes support both the OLI aqueous model and also the newer MSE model. Within PRO/II, supplied models created for OLI v7.0 end with the characters 70. Built in model SW0170 is created using OLI v7.0 and SW0166 is created using OLI v6.6. Only models created in 7.0 can be used in RATEFRAC. Users creating their own models should use Chem Wizard 2, 3 or 3.1to create compatible v7.0 models. The OLI aqueous model requires that the water mole fraction be greater than 0.6 on every stage or packed column segment. The newer MSE model allows the water mole fraction to vary from 0 to 1. However, OLI is still regressing data for the newer MSE model, and some components are not yet available. In particular, amines are not yet available using the MSE model. Note that RATEFRAC supports both equilibrium and nonequilibrium stages. Therefore RATEFRAC provides an alternative algorithm to Eldist for solving electrolytic distillation models. RATEFRAC/Electrolytes for non equilibrium systems requires transport properties. At the current time, OLI provides rigorous liquid viscosity for electrolyte systems, but not surface tension or
Important Notices
liquid thermal conductivity. OLI does provide diffusion coefficients for electrolyte systems. RATEFRAC/Electrolytes does not support solid precipitates forming within the column. Chemistry models including solids may be used, but the solid reactions and components will be ignored by RATEFRAC. Following are the rules for transport property usage within PRO/II: a) Diffusion Coefficients The OLI supplied diffusion coefficients are always used. No other option is available. b) Liquid Viscosity By default, the OLI viscosity is used. Alternatively, the user can select a PRO/II method such as library. In this case, the apparent mole fractions will be used with the apparent mole fractions to calculate the viscosity. Note that the OLI method takes into account the true species composition (ions and neutral aqueous species) and is the preferred method. c) Vapor Viscosity By default, water properties are used for the vapor viscosity. The user can select a PRO/II method. However, OLI adds additional components to the model beyond what the user specifies in the OLI Chemistry Wizard, and these additional components also require viscosity correlations. d) Surface Tension Currently OLI does not provide a rigorous surface tension method for electrolyte systems. OLI estimates availability the end of first quarter 2010. Currently, RATEFRAC will use water properties for surface tension. The user can also supply the surface tension via library correlations based on apparent compositions. Surface tension can also be supplied on a tray by tray basis for the tower being simulated. e) Liquid Thermal Conductivity Same rules as surface tension. f) Vapor Thermal Conductivity Same rules as vapor viscosity OLI's Chemistry Wizard version 3.1
OLI's Chemistry Wizard version 3.1 is included in the PRO/II 9.1release. This Chemistry Wizard allows users to generate custom electrolyte models with three new types of components: Assay, Pseudo and Inert Solids. By default the Assay and Pseudo components invoke the "Second Liquid" phase calculations. This option works well for modeling desalters with flash drums, but for column modeling we suggest turning off the "Second Liquid" phase calculations. The Assay curve input requires a minimum of 5 percent / boiling point temperature data pairs that must be in ascending temperature order. The Assay curve calculations generate a list of assay cut components named by boiling point temperature and a component with the assay name. The component with the assay name can be given a flow rate using the normal PRO/II Stream Data Entry Window and the OLI calculation engine will distribute that flow rate over the list of assay cuts. The Inert Solids are in the Chemistry Wizard "Available Components" Data Entry Window. The four new components are "Ash", "Carbon", "Coal" and "Coke". OLI provides default density and heat capacity for these components and allows user overrides. Thermo Upgrdaes Some v3.4 and v3.5 features have already been retrofitted in Thermo v3.3 and included in updates to v8.3 including: Heavy Oil viscosity and thermal conductivity methods Sulfolane NRTL binary parameters Biofuel and bioethanol components databank Chlorosilicone components Solubility of Hg in hydrocarbons Default Changes Assay Data Fitting to the Alternate Cubic Spline The Alternate was introduced in v8.1 to improve the shape of the resulting curve for some spline fits. Its proven to be a better method so we decided to make it the new default. IF97 Steam Tables in place of Saturation Water option for VLWE calculations.
10
Important Notices
Saturation option is faster, but only generates good results when water is at saturated conditions. IF97 or Keenan and Keyes gives accurate results for superheated steam. The old default was set at a time when CPU time was more critical. Stream Property Table & Stream Report Write Linkage In v8.3, the Stream Property Table is a GUI-only feature that displays both canned and customizable tables on the PFD. The results cannot be made part of the standard output report. The Stream Report Writer serves a similar function, but writes the special stream report into the standard output report. It cannot be displayed on the PFD or edited via the GUI. In v9.0, all SPTs can, at the user discretion, become part of the standard output report using SRW functionality. The SPT information is exported and persisted in the keyword file. Importing a keyword file with a SRW will cause an equivalent SPT to be placed on the PFD. The output file will be identical for keyword files that are executed with Run Batch, RunP2, or imported first into PRO/II.

Default changes Replace BK10 from the most commonly used thermo list with SRKM 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 interaction 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 viscosity 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 viscosity method originally released in PRO/II 8.2 has been improved the based on data received from SimSci-Esscor's Heavy Oils Consortium. This large quantity of unpublished proprietary data on a variety of crude oils, bitumens and distillates obtained from the consortium has allowed SimSci Heavy Oil Liquid Viscosity method to be even more accurate than before. 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:
12
Important Notices
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.

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
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 INNER 0 : E(ENTH+SPEC) = 7.252E-05
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 INNER 0 : E(ENTH+SPEC) = 6.127E-06
** 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

14 Important Notices
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
15
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 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 form
ln(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 form
y = 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. 2. Replace BK10 from the most commonly used thermo list with SRKM 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
Note: Before executing any of the installation programs, disable
all antivirus software running on your computer. 1. At the end of PRO/II 9.1 installation a dialog pops up asking for Restart, with YES/NO buttons. If user clicks No button PRO/II 9.1 libraries are not registered with TDM. tThe user needs to restart before launching TDM from PRO/II 9.1. PRO/II fails to launch with the default DEP setting on Windows Server 2003. To correct this problem, right-click on My Computer ==> Advanced Tab ==> Performance Settings ==> Data Execution Prevention Tab.By default, the bottom radio button "Turn on DEP for all programs and services except those I select". To enable PRO/II to run, select the top button "Turn on DEP for essential Windows programs and services only. A reboot will be required before this setting takes effect.
2.
Important information for uninstalling previous versions of PRO/II

1. Uninstalling PRO/II 7.1 will disable the HYSYS Translator in PRO/II 8.0, 8.1, 8.2, 8.3, 9.0 and 9.1 if they are installed on the same machine. During the PRO/II 7.1 uninstall process, the "Simulation Sciences\PRO/II key is completely removed. The workaround is to export the "HKEY_LOCAL_MACHINES\Softwares\Simulation Sciences" keys to a .reg file, and then re-import the file after completing the uninstall. This issue has been addressed tarting with PRO/II 8.0 so uninstalling PRO/II 8.0 or PRO/II 8.1 will not affect other versions of PRO/II. Uninstalling PRO/II 7.1 will disable Visual Flow 5.x. During the PRO/II 7.1 uninstall process, the "Simulation Sciences\PRO/II key is completely removed. The workaround is to export the "HKEY_LOCAL_MACHINES\Softwares\Simulation Sciences" keys to a .reg file, and then re-import the file after completing the uninstall. This issue has been addressed starting with PRO/II 8.0 so uninstalling PRO/II 8.0 or PRO/II 8.1 will not affect installed versions of Visual Flow.
2.
18
Important Notices
Known Issues and Limitations in REFPROP Add-on

Users must be aware of the following limitations the REFPROP Add-on has with respect to the standalone REFPROP program from NIST: 1. Only the REFPROP fluids are supported. The list of supported fluids also varies with each method. The list of supported fluids is shown in Appendix B of SIM4ME Thermo REFPROP Thermo Add-on Release Notes found under \\Manual\User. The fluid files must all be located in the same folder. The location is saved in the RefProp.ini file as part of the Add-on install step. Only three thermo methods are supported at this time: NIST23 (the default in REFPROP), GERG-2004 and AGA-8. Other method variations or combinations available through the standalone REFPROP application are not supported. The AGA8 method is only valid for the vapor phase (this is a limitation of AGA8, not the Add-on). Air cannot be mixed with other pure components to form a mixture. Air must be used as the only "component" in the component slate. Air is the only "pseudo pure fluid" supported at this time. The predefined mixtures in REFPROP are not supported at this time. Starting with PRO/II 9.0, PRO/II is able to call the REPFPROP flash directly.
2.
3.
4. 5.
6. 7. 8.
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
19
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. 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. 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. 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. 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. 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.
3.
4.
5.
6.
7.
20
Important Notices
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. 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.
9.
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. 1. Compatibility Mode A new portal file gets created only in .xls format (Excel 972003 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.
22
Opening 2007 Excel Portal File

Important Notices
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 Workbook: 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\Internet Explorer\ ActiveXCompatibility\{5f61f809-422a-4152-91f59ec1b935efd7}
23
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 handle upgrade.
8.
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. 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.
9.
10. 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. 11. 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. 12. 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. 13. 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.
24
Important Notices
14. For the UnitOPs like Column, Controller, MVC, Splitter, etc. the performance specifications are shown without their long descriptions and UOM. 15. 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. 16. What Operating System specifications do I need to have on my machine before installing Sim4Me Portal? Sim4Me Portal is supported on Windows 2000, 2003, XP, VISTA and Windoows 7. Microsoft Excel 2003 Professional with SP2, Microsoft Excel Professional 2007 or 2010is required. 17. Is there any sample Portal file to get user started? If yes, how to use the sample file? Yes. There are two Sample Portal files placed in SIMSCI\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 andbrowse for the sample file G5_Expander_Plant.xls. (b) Start Sim4Me Portal application in standalone mode, open the G5_Expander_Plant.xls. (c) Double click the sample portal files . Apart from these, there are additional sample SIM4ME Poratl files under C:\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
25
18. Is there any security setting that we need to set in Excel in order to run Portal? Yes, assistance for Portal security settings can be accessed at C:\Program Files\Common Files\Simsci\SIM4MEPortal201\Bin\Sim4MePortal_Checklist. doc (a) It does not work with security setting Very High. It can be changed from Excel>Tools>Macro>security>Security Level setting in Excel. (b) Also, in Excel>Tools>Macro>security>Trusted Publishers, check the option Trust access to Visual basic Project.
Switching Security Types for PC

PRO/II 9.1provides the following security options: USB Single User Security for PRO/II with PROVISION, PRO/ II Keyword, and add-ons. FLEXlm Security for PRO/II with PROVISION with security for add-ons. TOKEN Security for PRO/II with PROVISION with security for add-ons. FLEXNet 11 Security for PRO/II with PROVISION with security for add-ons. TOKENnet 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: Open the proii.ini file found in the user directory. Find the section entitled [wss_Security] and set the Type= keyword to one of the following values 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. Save the file and exit. If you are running under Windows XP/2003/VISTA, and Windows 7 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: Open the proii.ini file found in the user directory. Find the section entitled [wss_Security] and set Type=TOKEN. Save the file and exit. If you are running under Windows XP/2003/VISTA and Windows 7, 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 FLEXnet 11 security: Open the proii.ini file found in the user directory. Find the section entitled [wss_Security] and set Type=FLXnet11. Save the file and exit. If you are running under Windows XP/2003/VISTA and Windows 7, 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 TOKENnet security: Open the proii.ini file found in the user directory. Find the section entitled [wss_Security] and set Type=TOKENnet. Save the file and exit.
If you are running under Windows XP/2003/VISTA and Windows 7, 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 9.1
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.
Note: The Compaq Visual FORTRAN compiler (all versions) is
not compatible with PRO/II version 9.0. 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 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.
28
New Project Files for Version 9.1 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 9.1. New Files for PDTS Examples New Visual Studio Net 2003 PDTS project files are installed in the default location: C:\SIMSCI\PROII91\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\PROII91\User\Pdts\Examples\VF6\. Project files in the VF6 subdirectory are incompatible with version 9.0. 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\PROII91\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. The flies listed above replace older project files previously located in C:\SIMSCI\PROII91\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\PROII91\User\Uas\UasF91\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:
ExUasF91.sln Open this solution file using Visual Studio NET 2003 to build modular utilities. ExUasF91.vfproj This is the only project in the ExUasF91 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 previously located in the same directory.
Source code changes required for Intel Visual FORTRAN 10.1:

PRO/II 8.3, PRO/II 9.0 and PRO/II 9.1 are built with Intel Visual FORTRAN 10.1. Version 10.0 is compatible and may be used until version 10.1 or a newer version can be obtained. When upgrading older projects, please keep the following considerations in mind. NET 2003 uses a different run-time data structure that is incompatible with older architecture used by older compilers. For example, Logical File Unit numbers (LFUs) cannot be shared by the older and newer compilers. Assume PRO/II 9.0 under Net 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() subroutine User-Added Subroutine: IDATA(6) of the USERnn subroutine In both of these cases, PRO/II calls the FORTRAN OPEN statement to open a file and passes the unit number to the PDTS application or UAS. To avoid problems, the utility subroutine PAWRITE has been provided to allow your application to write
30 UAS/PDTS Capabilities
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
31
1001 FORMAT(' ERROR !! FEED STREAM ',A12,' IS MISSING'). ... IOUT = IDATA(6) C C 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 RETRIEVE FEED STREAM
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 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 RETRIEVE FEED STREAM
32
Running PDTS Applications

Note: If you call subroutine FIGETU to get a file unit number and
then call OPEN() in your own PDTS or UAS code, you do not need to make any code changes to the READ or WRITE statements because both the OPEN and the file input/output is accomplished within code compiled by the same compiler. PDTS applications are designed to execute in a virtual DOS environment from a Command prompt. When you execute a PDTS application, you may get the following message: The dynamic link library PESCalcMain.dll could not be found in the specified path To run PDTS applications, it sometimes is necessary to add additional directories to the system PATH so that the PDTS application can locate PESCalcMain.dll and the other required DLLs. This can be done by executing the batch file SetPDTS.bat, located in the user directory. That command file modifies the PATH of the current Command Prompt session to enable running PDTS applications in that Command Prompt session. If you start a second Command Prompt session, then you will need It may be necessary to execute the setPDTS.bat batch file in each Command session that you open. It is *not* recommended to change the system PATH in the Control Panel, because such a change may impact other installed applications. It is not necessary to execute SETPDTS.bat to run the PRO/II GUI or any of the installed batch files such as runp2.bat.
33
Where to Find PRO/II 9.1 Documentation

Printed Documentation Included with this Package
Release Notes for PRO/II 9.1 (this document)
Online Documentation
PRO/II User Guide SIM4ME Portal User Guide SIM4ME Reports User Guide TDM User Guide PRO/II Keyword Manual PRO/II Getting Started Guide PRO/II Casebooks PRO/II Application Briefs Manual PRO/II LIBMGR and COMPS Users Guide Data Transfer System Users Guide User-Added Subroutines Users Guide PRO/II Interface Modules Users Guide SIMSCI Component and Thermodynamic Data Input Manual PRO/II COM Server Reference Guide PRO/II COM Server Programmers Guide and Tutorial
Note: The PRO/II Welcome screen for the online documentation can be found on the hard drive under the simsci\proii91\Manuals
directory.
34
Where to Find PRO/II 9.1 Documentation
Summary of Defects Fixed in PRO/II 9.1

Feature Assay Bug Number Description HIPE#16707 There is the potential for a discontinuity in viscosity vs. temperature when the Petro method is used. HIPE#20225 In one case, for an assay stream doing "assay view curve" says "Assay analysis could not be completed. Calculated curves cannot be displayed". In one case, component cuts were not plotted correctly for assay plots, not passing through fitted TBP plot.
Assay
Assay
HIPE#20241
Assay
LFPE#27481 In an assay stream where more than 200 components are generated, clicking Vew Curve in the stream assay DEW may cause PRO/II to freeze. LFCR#4230 For one case, the Batch Distillation was out of material balance for two light components.
Batch Distillation Batch Distillation BatchFrac
LFPE#28129 The "gram" units of measure is not used for liquid holdup in batch distillation. kilograms works OK. HIPE#20296 Exporting the vfrac in a condenser adds a value of 1.0 to the exported value, thus resulting in a fraction value > 1.0. This fails import. HIPE#19983 In TDM Generated BVLE with Temperature as specification for the first time, property data is not generated. the workaround is to select Pressure, and then return to Temperature. LFCR#4275 The calculator can not set Temperature or Pressure of a pure non-molecular weight solids stream.
BVLE
Calculator Case Study Case Study
HIPE#20462 With both v9.0 and v8.3 installed, the Portal for v8.3 might not execute a run command. LFPE#28164 In Case Study, a Reference Stream target enthalpy inherits the enthalpy of the source. That's wrong when there is a change in thermo method. HIPE#20246 If a feed stream to a column has a user-supplied initial estimate, closing the column with OK causes the feed calculated values to be replaced with the initial estimate. The calculated values should be retained unless a Restore Input action is taken. HIPE#20270 For column hydraulic calculations, the section names can change when opening a v8.3 file in v9.0. For example, if the names "1" and "2" are used for column sections, they will open in v9.0 as "9" and "9". The hydraulic calculations will still work despite the duplicate name.
Column
Column
35
Feature Column
Bug Number Description HIPE#20520 Reactive distillation\(CHEMDIST & RATEFRAC) doesn't export pre-exponential factors which are present within column. Instead, it exports the value as 0. LFPE#28130 Converting column with side-stripper from IO to SURE does leaves the Convergence DEW in the side-stripper in an unusable state. The workaround is to copy all of the Convergence DEW data from the main column to the side-stripper. HIPE#20453 In one case, the column doesn't allow VLLE Check on VLE Tray though VLLE Thermo is available HIPE#20503 The Ratefrac Electrolyte column crash may crash when hydraulics data are present, using the built-in SCRU70 thermo package. Other built in packages, like SOUR and MEA are fine. LFPE#28171 Intermediate files created by user added subroutines in the default folder are deleted after a File/Exit operation. This is because they are created in the "TEMP" folder which is deleted after PRO/II is done with it. HIPE#20578 File convert from v8.3 to v9.0 with an embedded HTRI or Amsim unit will create a good v9.0 file. However, the backup v8.3 file will lose it's embedded HTRI or Amsim unit and will not open properly. HIPE#20459 PRO/II may not run after pasting an image onto the flowsheet. HIPE#20342 In the depressurize unit, keeping the final depressurize condition blank makes the depressurize to stop in the first time step itself. This criteria should be ignored. LFPE#28020 A stream-only electrolyte flowsheet is not calculated when import from scratch. Add a dummy flash and all is well. HIPE#20491 Modifying exceluop.ini and then using it to transfer more than 30 parameters through exceluop to Excel may result in a crash. LFPE#28109 A stream referenced to a product of a Filtering Centrifuge is not updated with the product stream properties. LFCR#4235 In one case, the phase designation of a cryogenic liquid product was L2 when it should have been L1.
Column
Column
Column
Component
Containerize PRZ
Copy Paste Depressuring
Electrolytes
ExcelUaUOP
Filtering centrifuge Flash
36
Feature Flash Flash Flash
Bug Number Description LFCR#4306 The Upper Dew point calculation may incorrectly find the Water Dew pressure.
LFPE#28018 GPSA VLLE calcs on rare occasion predicts one liquid phase when two liquid phases are present. LFPE#28204 Pure component refrigerants (R1234a, AMMMONIA, R22, PROPANE, R12, IBUTANE, NBUTANE, R21 and R114) using the standard flash algorithm may predict liquid properties when vapor properties are expected. Switching to the Alternate Flash algorithm clears this problem. LFCR#4415 VLLE calculation for low temperature N2/C3 mixture fails to solve on first run. Run a second time and it works predicting an LLE mixture. You cannot open a read-only .prz file, even just to look at it. You must change the attribute to readwrite access.
Flash
File
LFCR#3211
Furnace
LFPE#27949 The Furnace heat balance can be violated if the wall is unable to conduct enough heat to the surroundings. For one particular case, the furnace should have failed instead of solving for a bad balance. LFCR#4237 Attempting to place the HCURVE wet/dry liquid viscosity and/or thermal conductivity on a Portal worksheet results in an error message: "Index was outside the bounds of the array".
HCurve
Help
LFPE#28010 When the HELP document is opened via the F1 key while the cursor is active in any data entry window, the user cannot get back to the main PRO/ II program. LFPE#28181 The data transfer file to HTFS has its thermal conductivity (row 315) in W/m3-K units. HTFS is expecting kW/m3-K so the values are off by x1000. HIPE#20284 Values in Zonal analysis plot for HXRIG may be incorrect when plotted using the Output > Generate plot option. HIPE#18088 An HXRIG-HTRI unit failed because some transport properties were not transferred over from PRO/II to HTRI for a pure component stream. HIPE#20461 Setting the tube-side to the hot side before clicking the Initialize from HTRI file button, results in the setup button remaining in the unsatisfied state. Since this is irrelevant (HTRI already knows which side is hot), this should have no effect. LFPE#28189 Repeat use of Lumping unit fails to generate lumping report or .lmp file. The first time works fine.
HTRI/HTFS
HXRig
HXRig/HTRI
HXRig/HTRI
Lumping Unit
37
Feature Lumping Unit OLI Chemistry
Bug Number Description LFPE#28210 The lumping unit only works the first time. You have to export and reimport to work it again. HIPE#20298 View Results and DRW do not get updated after a run if the file is an untitled PRO/II file. OLI files only. HIPE#20295 Activation energy in the spec-vary-define system given in "kcal/kg-mole" reappears as "kcal" when the DEW is reentered. HIPE#20306 Stream attached to excluded unit operation does not appear in the output report even when input data has been supplied. It should not appear if the stream is not populated by the flowsheet, but it should appear in this case. HIPE#19763 The Tools/Distillation plot tool may leave off the first pseudo-component. HIPE#20629 A conversion reactor with more than 108 reactions fails to import. LFPE#28017 In one example, a Plugflow reactor undergoes an unexpected temperature drop after a short distance down the tube. There is no change in composition that can account for this. LFPE#28035 A plugflow with inadequate Runga-Kutta steps may say that it has solved when it hasn't. Slightly more steps results in a good solution, slightly less steps results in a legitimate "not-solved" condition. LFPE#28213 User-input Gibbs reactor approach temperature is available for laydown on the Portal, but you can't update it via the Portal. HIPE#20599 The Ternary Plot feature doesn't work with Excel 2003. HIPE#19838 In Sim4Me reports, with a user-created report, drag and drop attributes, save it and re-open the report, the new attributes do not persist.
Optimizer
PFD
Plot Reaction Data Reactor
Reactor
Reactor
Residue Curves S4MReports
S4MWorkbooks HIPE#20289 Launching Portal in Pro/II 9.0,after Uninstall and Reinstall of Portal gives an error. S4MWorkbooks HIPE#20407 After creating a Portal from PRO/II, but without saving from within the Portal, a subsequent opening of the Portal as a standalone gives error messages similar to "Attempted to read or write protected memory. This is often an indication that other memory is corrupt." S4MWorkbooks HIPE#20549 View Excel results are not available for the Filtering Centrifuge and Melter-Freezer unit operations.
38
Feature Solids Solids Solids
Bug Number Description HIPE#20641 Solids Removal unit may get bad product flash results if the feeds contain solids. LFCR#4286 The Stream Data Link feature will not transfer data from a non-molecular weight solids only stream.
LFPE#28230 Solid Removal adiabatic mode may not arrive at the same temperature as the feed streams that are already in equilibrium. LFPE#28015 In the spec/vary/define system, changing duty units to kJ from 10^6 kJ does not persist. On DEW reentry it's back to 10^6. HIPE#20408 Drag and drop of Streams Dry vapor specific enthalpy onto a Portal spreadsheet throws an index is out of array bounds error. LFPE#28000 Copy/Paste Special of a single-component twophase stream results in an all vapor or all liquid stream. The thermo state that is copied into the input slot of the new stream needs to be P-Vfrac rather than P-T for that particular scenario. LFPE#28028 For a stand-alone Amsim regenerator unit, entering hydrocarbon data in the rich amine feed to an AMSIM unit via the AMSIM GUI does not persist. Reenter the DEW and it's gone. LFPE#28135 Compressors with reference stream feeds, and with excluded unit in the flowsheet, may give the wrong answers for work. HIPE#20575 Liquid fractions - mole or weight - in Stream Property Table list does not get exported correctly. Reimporting the file fails. LFPE#28106 When a Stream Property Table is present and rate in liters/day is requested, the file is exported to keywords as LIT/DAT for the Stream Report Writer. LIT/DAY is not accepted in import. The workaround is to change the keyword to L/D. HIPE#20155 When Wilson parameters are used, they are not available on the Databank Hierarchy list. HIPE#20476 After changing LLE Interaction parameters, the first run of the flowsheet does not reflect the new parameters. After refresh (ctl-R), the flowsheet solves to the correct solution. VLE is OK. HIPE#20485 In one case, solving a flash using PPR78 resulted in a false root solution > 200 bar. LFPE#28209 The vapor pressure curve for the Keenan and Keyes water calculation method is a the saturated method, not from Keenan and Keyes. The calculated saturated pressure is different from true Keenan and Keyes by a few tenths psi at ordinary steam pressures, to 5 psi near the critical
Spec Vary Define Stream
Stream
Stream
Stream
Stream Property Table Stream Property Table
Thermo Thermo
Thermo Thermo
39
Feature Thermo
Bug Number Description LFPE#28218 When Keenan and Keyes steam method is used, there is some possibility near the critical that the contribution of dissolved liquid density finds a vapor density rather than a liquid density. This results in a discontinuous liquid density as a function of temperature. LFPE#28275 Peneloux vapor densities with only one component in component list can evaluate to a negative number. Adding a second component to the list clears the problem. LFCR#4414 Depending on whether SRK or SRKM is used, a bubble pt LLE split between N2 and Propane either puts the N2 as the L1 phase or N2 as the L2 phase. They should both predict the same phase.
Thermo
Thermo
Unit Op Property Table
HIPE#20553 The Options/Unit Op Property Tables list is initially alpha-sorted (good), but after restricting to one of the unit op types, and then return to all unit op types, it is no longer alpha-sorted (bad). LFPE#27993 A bottom tray negative duty is identified as a reboiler in the column output. LFPE#28128 The Saturated Pressure option in the Upstream unit is supposed to find the high saturation pressure, but occasionally finds the low one. HIPE#20313 Depending on exact mouse cursor placement, right-click to View Results on a stream may create an abort message: *** ABORT *** INDEX CONTROL AREA DOES NOT EXIST SUBSYSTEM FB FAILED IN FBINAM ************* RUN TERMINATED ************* To avoid the bug, move the cursor away from the stream so that it doesn't attempt to do View Results and get stream Tooltips at the same time.
Unit Op Property Table Upstream
View Results
View Results
LFCR#4287 View Results set to Viewer or Browser is incorrectly formatted when non-MW solids are present in a stream. LFPE#28102 View Results when more than one unit is selected results in an access violation.
View Results
40
Summary of Defects Fixed in PRO/II 9.0 Patches

Feature Amsim Bug Number Description HIPE#20314 Converting a file with an Amsim unit operation from 8.3 to 9.0, the new .prz works fine but the _v83.prz does not contain the required .apj file. The file won't run in v8.3 because it lacks the Amsim model. With Cubic Spline and IF97, recalculating the assay breakdown may result in a Bad Pointer Starting Address error. There is a small error that can be introduced in the calculated TBP result when there are multiple components that cover exactly or nearly the same range. For exmaple, if there are two blends with the following: CUTPOINTS TBPCUTS=100,800,28/1200,8/ 1600,4, DEFAULT CUTPOINTS TBPCUTS=100,800,28/1200,8/ 1600,4, BLEND=A you may end up with a TBP value (any percent), that is not exactly on the line plotted by lv% vs T of any of the resulting streams. Most of the points will be correct. If the problem shows up, it may have one point that is off by 2 degrees or so. On one occasion we saw a result that was off by more. Cape Open HIPE#20352 Cape Open COCO_COUS mixer convert from PRO/IIPRO/II 8.3 to PRO/II 9.0 gives a crash when there are more than 6 feeds. A CAPE-OPEN Property package name having embedded space is not supported through keywords. Properties retrieved via Cape Open thermo have non-sensical values. These were OK in v8.3. Properties affected include density, surface tension, thermal conductivity and viscosity. File convert via .com (Say, from Excel) of a file containing Cape Open COCO units fail because the relevant .dat file is not containerized in the .prz.
Assay
LFPE#28095
Assay
LFPE#28165
Cape Open
HIPE#20372
Cape Open
HIPE#20382
Cape Open
HIPE#20385
41
Feature Case Study
Bug Number Description LFPE#27981 Choose to run Base Case only in Case Study problem may result in an error message that the PARAMETER 'PARAM1', changed during calculations in cycle 1. Since cycle 1 is not run, there should have been no error message. The <Liquid> tag information on the xml file for data transfer to FRI's DRP program or KochGlitsch KGTower reports the Liquid To rather than the Liquid From. The Ratefrac Electrolyte column crash may crash when hydraulics data are present using the builtin SCRU70 thermo package. Other built in packages, like SOUR and MEA are fine. User supplied VP data using correlation 20 will be incorrect if the parameters are supplied using deg R. deg K is OK. The critical Pressure for mercury is incorrect Databankin the PROCESS databank. The the user-supplied Polytropic Efficiency for a compressor does not persist after OKing back to the PFD level. Compressors with primarily vapor, but some liquid feed, and VLLE thermo, results in a bad outlet condition calculation, even though there is only one liquid phase. VLE thermo works correctly. In one case, the dew point calculation for an all water stream using IF97 results in incorrect enthalpy near the critical. The stream icon on the build palette turns red (unsatisfied) after a Save As operation. Click around the PFD restores it to the correct black color. Define is being ignored in column reaction data for the Pre-Exponential Factor and resets it to a value of 1.0 Starting PRO/II 9.0 with TokenNet security may result in a security error message about the license expiration date, even though the license is good. he Solid removal unit does not material balance when the feed is a solids-only stream.
Column
LFPE#28076
Column
HIPE#20503
Component
HIPE#20319
Component Databank Compressor
LFPE#28143 LFPE#28096
Compressor
LFPE#28136
Flash
LFPE#28152
PFD
HIPE#20285
Reaction Data
LFCR#4298
Security
LFPE#28115
Solids
HIPE#20370
42
Summary of Defects Fixed in PRO/II 9.0 Patches
Feature Solids Solids
Bug Number Description HIPE#20378 HIPE#20473 The energy balance is not attained for solid removal unit operation. The Plant Material Balance Table could be in error if decant water is present.. Solids Removal adiabatic option does not result in the correct temperature in at least one case. After running a file, click on Tools/Spreadsheet /Stream Properties. At the conclusion of laying out the spreadsheet it may crash with a p2oledbs.exe application error. The Find Stream and Find Unit are not alpha sorted in v9.0. When a Stream Property Table is present and rate in liters/day is requested, the file is exported to keywords as LIT/DAY for the Stream Report Writer. LIT/DAY is not accepted in import. The workaround is to change the keyword to L/D. Some components in the databank appear to have incorrect Unifact structural groups assigned to them. The following components have a mismatch in MW when built via Unifac Fill: CITRONIC, DC9PHEN, DEAA, HYOXCAPR, MALIC, MALONIC, MERPRO, METOXYAC, HNEOC5, PYRUVIC. The parachor surface tension calculation is incorrect for single component flowsheets The Unifac group breakdown for some components is wrong. Affected are: 1M2PRBZ, 1M3PRBZ, 1M4PRBZ, MMSTYR, OMSTRY, 4HSTYREN, IPCH, 2MNON, 4MNON, 5MNON. Using GPSA water saturation, if the stream is nearly pure in a vapor-liquid mix, adding more liquid water decreases the vapor water flowrate. This is because there is a cutoff concentration for pure-component handling (in this one scenario) that is not close enough to 1.0. Updating controller the current variable values to a stream estimate updates the field to the moles/hr value even when the UOM for that field is mass/hr. A User Added Subroutines linked with Intel VF 8 may not work subroutines because of extraneous routines listed in the .sln file.
Solids Spreadsheet Tools
LFPE#28105 LFPE#27921
Stream Stream Property Table
LFPE#28112 LFPE#28106
Thermo
HIPE#18602
Thermo Thermo
HIPE#20447 LFCR#4208
Thermo
LFPE#27975
Update Initial Estimates
HIPE#20403
User Added Subroutines
HIPE#20488
43
Summary of Open Defects in PRO/II 9.1

PRO/II 9.1 Bug Lists
To access the current version of PRO/II 9.1bug list as well as FAQ and Updates, visit our website's Knowledge Base at http:// iom.invensys.com/EN/Pages/SimSci-Esscor.aspx. Select Support Menu and then the SIM4ME Software Updates & Knowledge Base under SimSci-Esscor. 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 9.1
License and Copyright Information

Release Notes for PRO/II 9.1 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. 2011 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. Invensys, Invensys logo, HEXTRAN, INPLANT, PIPEPHASE, PRO/II, Provision, SIM4ME, and SimSciEsscor are trademarks of Invensys plc, its subsidiaries, and affiliates. All other brand names may be trademarks of their respective owners. U.S. GOVERNMENT RESTRICTED RIGHTS LEGEND The Software and accompanying written materials are provided with restricted rights. Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data And Computer Software clause at DFARS 252.227-7013 or in subparagraphs (c) (1) and (2) of the Commercial Computer Software-Restricted Rights clause at 48 C.F.R. 52.227-19, as applicable. The Contractor/Manufacturer is: Invensys Systems, Inc. (a division of Invensys plc. and owner of the SimSci-Esscor brand) 26561 Rancho Parkway S., Lake Forest, CA 92630, USA. Printed in the United States of America, August 2011.
Copyright Notice
Trademarks
45
46
License and Copyright Information

PROII91 ReleaseNotes PDF

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

PROII91 ReleaseNotes PDF

Diunggah oleh

Hak Cipta:

Format Tersedia

Important: Read First

Release Notes for PRO/II 9.1

PRO/II 9.1 Release Notes

New Features of PRO/II 9.1

Koch-Glitsch Packing Updates

Sulzer Packing Updates

Phase Envelope with Water SIM4ME Portal Upgrade

New Features of PRO/II 9.1

New Feature Integration with FRIfor Column Hydraulic Design

PRO/II 9.1 Release Notes

New Feature Documentation

Tear and Reference Streams Identification in the GUI

New Features of PRO/II 9.1

New Feature Fugacity Activity Basis for Equilibrium Reactors

Description PRO/II allows equilibrium reactors to be defined with fugacities.

Known issues in PRO/II 9.1

PRO/II 9.1 Release Notes

Known issues in PRO/II 9.0

Known issues in PRO/II 8.3

What is new/changed in PRO/II 9.1

What is new/changed in PRO/II 9.0

What is new/changed in PRO/II 8.3

What is new/changed in PRO/II 8.2

Calculating New Matrix

Library and Databank Handling During File convertion and Import

PRO/II 9.1 Release Notes

ln(y) = ln(K) + ln(x)

Default changes in PRO/II v8.0:

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

Important information for uninstalling previous versions of PRO/II

Known Issues and Limitations in REFPROP Add-on

Known Defects and Constraints using SIM4ME Reports

PRO/II 9.1 Release Notes

Known Defects and Constraints using SIM4ME Portal

Opening 2007 Excel Portal File

PRO/II 9.1 Release Notes

PRO/II 9.1 Release Notes

Switching Security Types for PC

New Project Files for Version 9.1 User-Added Subroutines

New Files for Modular UAS Examples

Source code changes required for Intel Visual FORTRAN 10.1:

PRO/II 9.1 Release Notes

UAS example modified to use PAWRITE:

Running PDTS Applications

PRO/II 9.1 Release Notes

Where to Find PRO/II 9.1 Documentation

Where to Find PRO/II 9.1 Documentation

Summary of Defects Fixed in PRO/II 9.1

Batch Distillation Batch Distillation BatchFrac

Calculator Case Study Case Study

PRO/II 9.1 Release Notes

Copy Paste Depressuring

Filtering centrifuge Flash

Summary of Defects Fixed in PRO/II 9.1

Feature Flash Flash Flash

PRO/II 9.1 Release Notes

Feature Lumping Unit OLI Chemistry

Plot Reaction Data Reactor

Residue Curves S4MReports

Summary of Defects Fixed in PRO/II 9.1

Feature Solids Solids Solids

Spec Vary Define Stream