aspenengineeringsuitev7 1 issues

Aspen Engineering Suite

Aspen Engineering

Known Issues in V7.0 and V7.1

Version Number: V7.1 January 2009

Copyright (c) 2009 by Aspen Technology, Inc. All rights reserved.

Aspen Acol+™, Aspen Adsim®, Aspen Adsorption, Aspen Air Cooled Exchanger, Aspen Basic Engineering, Aspen Batch Process Developer, Aspen Batch Distillation, Aspen Batch Plus®, Aspen BatchSep™, Aspen Capital Cost Estimator, Aspen CatRef®, Aspen Chromatography®, Aspen COMThermo®, Aspen Custom Modeler®, Aspen Distillation Synthesis, Aspen Dynamics®, Aspen Energy Analyzer, Aspen FCC®, Aspen Fired Heater, Aspen FiredHeater, Aspen Flare System Analyzer, Aspen FLARENET™, Aspen HTFS Research Network™, Aspen HX-Net®, Aspen Hydrocracker®, Aspen Hydrotreater™, Aspen HYSYS Amines™, Aspen HYSYS Dynamics™, Aspen HYSYS OLGAS 3-Phase™, Aspen HYSYS OLGAS™, Aspen HYSYS PIPESYS™, Aspen HYSYS RTO™ Offline, Aspen HYSYS Upstream Dynamics™, Aspen HYSYS Upstream™, Aspen HYSYS Upstream™, Aspen HYSYS®, Aspen HYSYS® Thermodynamics COM Interface, Aspen HYSYS® Pipeline Hydraulics - OLGAS 2-Phase, Aspen HYSYS® Pipeline Hydraulics - OLGAS 3-Phase, Aspen HYSYS® Pipeline Hydraulics - PIPESYS, Aspen HYSYS® Offline Optimizer, Aspen HYSYS® Hydrocracker, Aspen HYSYS® Reformer, Aspen HYSYS® CatCracker, Aspen HYSYS® Petroleum Refining, Aspen Icarus Process Evaluator®, Aspen Icarus Project Manager®, Aspen In-Plant Cost Estimator, Aspen Kbase®, Aspen MINLP Optimization, Aspen Mixed Integer Optimizer, Aspen Model Runner™, Aspen MPIMS™, Aspen MUSE™, Aspen Online Deployment™, Aspen OnLine®, Aspen OnLine®, Aspen OTS Framework, Aspen PIMS Advanced Optimization™, Aspen PIMS Submodel Calculator™, Aspen PIMS™, Aspen Plate Exchanger, Aspen Plate+™, Aspen Plus Optimizer™, Aspen Plus®, Aspen Plus® CatCracker, Aspen Plus® Dynamics, Aspen Plus® Hydrocracker, Aspen Plus® Hydrotreater, Aspen Plus® Reformer, Aspen Polymers, Aspen Polymers Plus™, Aspen Process Economic Analyzer, Aspen Process Manual™, Aspen Process Tools™, Aspen Properties®, Aspen Rate-Based Distillation, Aspen RateSep™, Aspen Reaction Modeler, Aspen RefSYS Catcracker™, Aspen RefSYS Hydrocracker™, Aspen RefSYS Reformer™, Aspen RefSYS™, Aspen Shell & Tube Exchanger, Aspen Shell & Tube Mechanical, Aspen Simulation Workbook™, Aspen Solubility Modeler, Aspen Split™, Aspen Tasc+™, Aspen Teams®, Aspen Utilities On-Line Optimizer, Aspen Utilities Operations™, Aspen Utilities Planner™, Aspen Zyqad™, SLM™, SLM Commute™, SLM Config Wizard™, the Aspen leaf logo, and Plantelligence are trademarks or registered trademarks of Aspen Technology, Inc., Burlington, MA.

All other brand and product names are trademarks or registered trademarks of their respective companies.

This documentation contains AspenTech proprietary and confidential information and may not be disclosed, used, or copied without the prior consent of AspenTech or as set forth in the applicable license agreement. Users are solely responsible for the proper use of the software and the application of the results obtained.

Although AspenTech has tested the software and reviewed the documentation, the sole warranty for the software may be found in the applicable license agreement between AspenTech and the user. ASPENTECH MAKES NO WARRANTY OR REPRESENTATION, EITHER EXPRESSED OR IMPLIED, WITH RESPECT TO THIS DOCUMENTATION, ITS QUALITY, PERFORMANCE, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.

Aspen Technology, Inc. 200 Wheeler Road Burlington, MA 01803-5501 USA Phone: (1) 781-221-6400 Toll Free: (1) (888) 996-7100 URL: http://www.aspentech.com

http://www.aspentech.com/

Contents 1

Contents

Contents..................................................................................................................1

Introduction for V7.0 and V7.1................................................................................5 Product Name Changes in aspenONE V7.0 ......................................................... 5

Aspen Engineering Workflows.................................................................................9 Process Engineering Console V7.0 .................................................................... 9 Process Engineering Console V7.1 ...................................................................10 Process Development Console V7.0 and V7.1 ....................................................10 Integrated Sizing and Costing V7.0..................................................................11 Integrated Sizing and Costing V7.1..................................................................11

Process Modeling (Aspen Plus) .............................................................................13 Aspen Plus V7.0............................................................................................13 Aspen Plus V7.1............................................................................................14 The OLI Interface V7.0...................................................................................16 The OLI Interface V7.1...................................................................................16 Aspen Properties V7.0....................................................................................17 Aspen Properties V7.1....................................................................................17

Advanced Simulation Options (Aspen Plus)...........................................................19 Aspen Custom Modeler V7.0 ...........................................................................19 Aspen Custom Modeler V7.1 ...........................................................................20 Aspen Model Runner V7.0...............................................................................21 Aspen Model Runner V7.1...............................................................................21 Aspen Plus Dynamics V7.0 (formerly Aspen Dynamics) .......................................22 Aspen Plus Dynamics V7.1 (formerly Aspen Dynamics) .......................................23 Aspen Adsorption V7.0 (formerly Aspen Adsim) .................................................24 Aspen Adsorption V7.1 (formerly Aspen Adsim) .................................................25 Aspen Utilities Planner V7.0 ............................................................................26 Aspen Utilities Planner V7.1 ............................................................................26

Process Modeling (HYSYS) ....................................................................................27 Aspen HYSYS V7.0 ........................................................................................27 Aspen HYSYS V7.1 ........................................................................................29

2 Contents

Aspen HYSYS Dynamics V7.0 ..........................................................................29 Aspen HYSYS Dynamics V7.1 ..........................................................................30 Aspen HYSYS Upstream V7.0 ..........................................................................30 Aspen HYSYS Upstream V7.1 ..........................................................................31 Aspen HYSYS Petroleum Refining V7.0 (formerly Aspen RefSYS) ..........................32 Aspen HYSYS Petroleum Refining V7.1 (formerly Aspen RefSYS) ..........................34

Exchanger Design and Rating................................................................................37 All Exchanger Design and Rating Products V7.0 .................................................37 All Exchanger Design and Rating Products V7.1 .................................................38 Aspen Air Cooled Exchanger V7.0 (formerly Aspen ACOL+) .................................39 Aspen Air Cooled Exchanger V7.1 (formerly Aspen ACOL+) .................................39 Aspen Fired Heater V7.0 and V7.1 (formerly Aspen FiredHeater)..........................40 Aspen Shell & Tube Exchanger V7.0 and V7.1 (formerly Aspen TASC+) ................40 Aspen Shell & Tube Mechanical V7.0 and V7.1 (formerly Aspen TEAMS) ................41 Aspen Plate Exchanger V7.0 and V7.1 (formerly Aspen Plate+)............................41 Aspen HTFS Research Network V7.0 and V7.1 ...................................................41 Aspen MUSE V7.0 and V7.1 ............................................................................42 Plate Fin Exchanger V7.0................................................................................42 Plate Fin Exchanger V7.1................................................................................43

Economic Evaluation .............................................................................................45 Aspen Capital Cost Estimator V7.0 (formerly Aspen KBase) .................................45 Aspen Capital Cost Estimator V7.1 (formerly Aspen KBase) .................................46 Plot Plan Processor feature V7.0......................................................................48 Plot Plan Processor feature V7.1......................................................................50 Spreadsheet Data Entry feature V7.0 ...............................................................50 Spreadsheet Data Entry feature V7.1 ...............................................................51 Aspen In-Plant Cost Estimator V7.0 (formerly Aspen Icarus Project Manager) ........51 Aspen In-Plant Cost Estimator V7.1 (formerly Aspen Icarus Project Manager) ........52 Aspen Process Economic Analyzer V7.0 (formerly Aspen Icarus Process Evaluation)53 Aspen Process Economic Analyzer V7.1 (formerly Aspen Icarus Process Evaluation)55 Integrated Sizing and Costing feature V7.0 (available in Aspen Plus and Aspen HYSYS)........................................................................................................58 Integrated Sizing and Costing feature V7.1 (available in Aspen Plus and Aspen HYSYS)........................................................................................................59

Energy and Flare Analysis .....................................................................................61 Aspen Energy Analyzer V7.0 (formerly Aspen HX-Net)........................................61 Aspen Energy Analyzer V7.1 (formerly Aspen HX-Net)........................................61 Aspen Flare System Analyzer V7.0 (formerly Aspen FLARENET) ...........................62 Aspen Flare System Analyzer V7.1 (formerly Aspen FLARENET) ...........................62 Aspen HYSYS Thermodynamics COM Interface V7.0 and V7.1 (formerly Aspen COMThermo)................................................................................................63

Aspen Simulation Workbook .................................................................................65 Aspen Simulation Workbook V7.0 ....................................................................65 Aspen Simulation Workbook V7.1 ....................................................................66 Aspen OOMF V7.0 and V7.1............................................................................67

Contents 3

Process Development............................................................................................69 Aspen Batch Process Developer V7.0 (formerly Aspen Batch Plus) ........................69 Aspen Batch Process Developer V7.1 (formerly Aspen Batch Plus) ........................70 Solubility Modeling V7.0 and V7.1....................................................................71

Advanced Modeling Options (Process Development).............................................73 Aspen Batch Distillation V7.0 (formerly Aspen BatchSep) ....................................73 Aspen Batch Distillation V7.1 (formerly Aspen BatchSep) ....................................74 Aspen Reaction Modeler V7.0..........................................................................75 Aspen Reaction Modeler V7.1..........................................................................75 Aspen Chromatography V7.0 ..........................................................................76 Aspen Chromatography V7.1 ..........................................................................76 Aspen Process Tools V7.0 and V7.1 .................................................................77

Aspen Process Manual V7.0 and V7.1....................................................................79 Aspen Process Manual V7.0 ............................................................................79 Aspen Process Manual V7.1 ............................................................................79

Basic Engineering V7.0 and V7.1...........................................................................81 Aspen Basic Engineering V7.0 (formerly Aspen Zyqad) .......................................81 Aspen Basic Engineering V7.1 (formerly Aspen Zyqad) .......................................81

Operations Support ...............................................................................................85 Aspen Online Deployment V7.0 .......................................................................85 Aspen Online Deployment V7.1 .......................................................................87 Aspen OTS Framework V7.0 ...........................................................................90 Aspen OTS Framework V7.1 ...........................................................................91

Aspen OnLine V7.0 and V7.1 .................................................................................93

Aspen Plus Refinery Based Reactors .....................................................................95 Aspen Plus Catcracker V7.0 and V7.1 (formerly Aspen FCC) ................................95 Aspen Plus Hydrocracker V7.0 and V7.1 (formerly Aspen Hydrocracker)................95 Aspen Plus Hydrotreater V7.0 and V7.1 (formerly Aspen Hydrotreater) .................96 Aspen Plus Reformer V7.0 and V7.1 (formerly Aspen CatRef) ..............................96

Aspen Open Object Model Framework V7.0 and V7.1 ............................................97

4 Contents

Introduction for V7.0 and V7.1 5

Introduction for V7.0 and V7.1

This document contains a summary of known issues or limitations relating to this release. Workarounds are suggested where possible.

Known issues are listed as those relating to:

• Coexistence issues (different versions of products on the same computer).

• Installation issues (potential problems arising during the install or uninstall procedure).

• Usability issues (interface issues that will be addressed in future releases/hot fixes).

Please refer to the tables in each product section for issues relating to the products you are using.

Note: For additional information about Known Issues, see the AspenTech Support web site (http://support.aspentech.com). For additional information about issues relevant to the complete product line, see the aspenONE Known Issues on the Documentation DVD.

Product Name Changes in aspenONE V7.0 With the release of aspenONE V7.0, AspenTech has made the decision to provide more functional names to several of its Process Engineering products. The new names will reflect the function/role that each product performs as part of the overall Aspen Engineering. The installation has also been re-organized to reflect functional groups. To the release of aspenONE V7.1, AspenTech still use these new names. Use the chart below to see the new product names and their corresponding installation selections.

http://support.aspentech.com/

6 Introduction for V7.0 and V7.1

Product Name Release 2006.5

Product Name V7.0

Install Mapping (What to Install)

Required Install Option Selection

Aspen Acol+™ Aspen Air Cooled Exchanger

Exchanger Design And Rating

---

Aspen Adsim® Aspen Adsorption Process Modeling (Aspen Plus)

Advanced Simulation Options

Aspen Batch Plus® Aspen Batch Process Developer

Process Development ---

Aspen BatchSep™ Aspen Batch Distillation

Process Development Advanced Modeling Options

Process Modeling (Aspen Plus)


Aspen CatRef® Aspen Plus® Reformer

Aspen Plus Based Refinery Reactors

---

Aspen Chromatography®

Aspen Chromatography®


Aspen COMThermo®

Aspen HYSYS® Thermodynamics COM Interface

Process Modeling (HYSYS)

Energy and Flare Analysis

Aspen Custom Modeler®

Aspen Custom Modeler®





Aspen Dynamics® Aspen Plus® Dynamics



Aspen FCC® Aspen Plus® CatCracker


---

Aspen FiredHeater Aspen Fired Heater Exchanger Design And Rating

---

Aspen FLARENET™ Aspen Flare System Analyzer





Aspen HTFS Research Network™

Aspen HTFS Research Network™


---

Aspen HX-Net® Aspen Energy Analyzer





Aspen Hydrocracker®

Aspen Plus® Hydrocracker


---

Aspen Hydrotreater™

Aspen Plus® Hydrotreater


---

Aspen HYSYS® Aspen HYSYS® Process Modeling (HYSYS)

---

Aspen HYSYS Amines™

Aspen HYSYS Amines™


---

Aspen HYSYS Dynamics™

Aspen HYSYS Dynamics™


---

Introduction for V7.0 and V7.1 7


Product Name V7.0



Aspen HYSYS OLGAS™

Aspen HYSYS® Pipeline Hydraulics - OLGAS 2-Phase


---

Aspen HYSYS OLGAS 3-Phase™

Aspen HYSYS® Pipeline Hydraulics - OLGAS 3-Phase


---

Aspen HYSYS PIPESYS™

Aspen HYSYS® Pipeline Hydraulics

- PIPESYS


---

Aspen HYSYS RTO™ Offline

Aspen HYSYS® Offline Optimizer


---

Aspen HYSYS Upstream™

Aspen HYSYS Upstream™


---

Aspen HYSYS Upstream Dynamics™

Aspen HYSYS Upstream Dynamics™


---

Aspen Icarus Process Evaluator®

Aspen Process Economic Analyzer

Economic Evaluation ---

Aspen Icarus Project Manager®

Aspen In-Plant Cost Estimator


Aspen Kbase® Aspen Capital Cost Estimator


Aspen MPIMS™ Aspen MPIMS™ Aspen PIMS ---

Aspen Model Runner™

Aspen Model Runner™



Aspen MUSE™ Aspen MUSE™ --- ---

Aspen OnLine® Aspen OnLine® --- ---

Aspen Online Deployment™

Aspen Online Deployment™

Operations Support Aspen Online Deployment

Aspen PIMS™ Aspen PIMS™ Aspen PIMS ---

Aspen PIMS Advanced Optimization™

Aspen PIMS Advanced Optimization™

Aspen PIMS ---

Aspen PIMS Submodel Calculator™

Aspen PIMS Submodel Calculator™

Aspen PIMS ---

Aspen Plate+™ Aspen Plate Exchanger

Exchanger Design and Rating

---

Aspen Plus® Aspen Plus® Process Modeling (Aspen Plus)

---

Aspen Plus EO Model Library (Equation-Oriented HYSYS)

Aspen Plus EO Model Library (Equation-Oriented HYSYS)



Aspen Plus Optimizer™

Aspen Plus Optimizer™


---

Process Modeling Advanced Simulation

8 Introduction for V7.0 and V7.1


Product Name V7.0



(HYSYS) Options

Aspen Polymers Plus™

Aspen Polymers Process Modeling (Aspen Plus)

---

Aspen Process Manual™

Aspen Process Manual™

Process Development (Server Installation only)

---

Aspen Process Tools™

Aspen Process Tools™


Aspen Properties® Aspen Properties® Process Modeling (Aspen Plus)

---

Aspen solubility modeler functionality

Process Development ---

Aspen RateSep™ Aspen Rate-Based Distillation


---

Aspen RefSYS™ Aspen HYSYS® Petroleum Refining


Aspen RefSYS Catcracker™

Aspen HYSYS® CatCracker



Aspen RefSYS Hydrocracker™

Aspen HYSYS® Hydrocracker



Aspen RefSYS Reformer™

Aspen HYSYS® Reformer



Aspen Simulation Workbook™

Aspen Simulation Workbook™

Operations Support Aspen Simulation Workbook


Aspen Simulation Workbook



Aspen Split™ Aspen Distillation Synthesis


---

Aspen Tasc+™ Aspen Shell & Tube Exchanger


---

Aspen Teams® Aspen Shell & Tube Mechanical


---

Aspen Utilities Operations™

Aspen Utilities On-Line Optimizer



Aspen Utilities Planner™

Aspen Utilities Planner™



Aspen Zyqad™ Aspen Basic Engineering

Aspen Basic Engineering

---

NEW Aspen OTS Framework

Operations Support Aspen OTS Framework

Aspen Engineering Workflows 9

Aspen Engineering Workflows

Process Engineering Console V7.0

Coexistence Issues Workaround/Comment

No known issues Not applicable

Installation Issues Workaround/Comment


General Usability Issues Workaround/Comment

PE Console cannot start Aspen Simulation Workbook unless Aspen Simulation Workbook is installed on d: drive

Install ASW on d: drive

PE Console does not properly keep track of Heat Exchanger Design (.edr) files.

Open Heat Exchanger Design program from PE Console, then open .edr file of interest from within Heat Exchanger Design.

10 Aspen Engineering Workflows

Process Engineering Console V7.1






In order for Aspen Process Engineering Console to start Aspen Simulation Workbook, the Microsoft Office Primary Interop Assemblies must be installed. These are normally installed with Microsoft Office, but may be omitted in some express or custom installations.

These can be downloaded and installed from the sites below:

http://www.microsoft.com/downloads/details.aspx?familyid=59DAEBAA-BED4-4282-A28C-B864D8BFA513&displaylang=en (Office 2007)

http://www.microsoft.com/downloads/details.aspx?familyid=3C9A983A-AC14-4125-8BA0-D36D67E0F4AD&displaylang=en (Office 2003)

Process Development Console V7.0 and V7.1







http://www.microsoft.com/downloads/details.aspx?familyid=59DAEBAA-BED4-4282-A28C-B864D8BFA513&displaylang=en




http://www.microsoft.com/downloads/details.aspx?familyid=3C9A983A-AC14-4125-8BA0-D36D67E0F4AD&displaylang=en




Aspen Engineering Workflows 11

Integrated Sizing and Costing V7.0






Costing can only be activated for one simulation at a time.

If you have two simulations open, only activate costing for one of them.

Integrated Sizing and Costing V7.1







12 Aspen Engineering Workflows

Process Modeling (Aspen Plus) 13


Aspen Plus V7.0






The Reboiler Wizard in the RadFrac block is not able to prevent you from deleting one of the linked blocks when the Maintain link feature is used.

You should clear the Maintain link checkbox before deleting one of these blocks; otherwise you may experience unpredictable effects. When you delete a block, any Calculator blocks referencing it may be marked incomplete. You should delete those blocks as well.

When loading a file from version 2006 which contains temperature-dependent parameters from the NIST databank, input is incomplete.

This happens because version 2006 did not contain the units for these parameters in the database. Versions 2006.5 and V7.0 include these units and expect them to be specified. To fix this problem, select Tools | Clean Property Parameters. Select Clean property parameters placed on input forms and then click OK twice. Then on the Components | Specifications | Selection sheet, click Review to retrieve the parameters from the database again.

14 Process Modeling (Aspen Plus)

If any COM Add-ins (such as the one from Aspen Simulation Workbook, or any third-party COM Add-in) are installed in Microsoft Excel, then Excel remains running after you use it with an Excel Calculator block.

You can end this Excel process from the Task Manager or leave it running. It should not cause any problems except for increased memory usage.

Blocks and Streams named TOP and DATA do not work correctly in some situations. For instance, if you double-click a stream named TOP on the flowsheet, the Data Browser opens to the Streams folder, but does not open the form for the stream named TOP.

Starting in version V7.0, these names are reserved and Aspen Plus will not allow you to assign them to streams and blocks. In existing files which use these names, you should rename the blocks and/or streams with these names on the flowsheet.

For some users, the Excel Calculator toolbar fails to appear the second and subsequent times you open an Excel Calculator block in Excel. This prevents changing any of the connections of cells to Aspen Plus variables.

If you save your Aspen Plus simulation, close it, and reopen it, then the Excel Calculator will work correctly once each Aspen Plus session. We are developing a new version of the Excel Calculator add-in for the next release which will resolve this issue.

Certain links within the help files link to other products' help, or to viewlets. These links will not work unless the other product is installed, or in the case of the viewlets, the product whose help you are using is installed.

To view this help from the Doc DVD, click the links in the Doc DVD Browser to open this help directly.

Aspen Plus V7.1


If any version of Aspen Simulation Workbook (ASW) is installed, when you close Aspen Plus after using an Excel Calculator block, both Aspen Plus and Excel remain running in the background.

You can end these processes from the Task Manager.

To prevent this from happening, you can disable the ASW add-in before running Aspen Plus when you are going to use Excel Calculators. Click Start | Programs | Process Modeling V7.1 | Aspen Simulation Workbook | Aspen Simulation Workbook Add-In Manager, clear the boxes by all versions of Aspen Simulation Workbook, and then click OK. You will need to enable it again by checking the box for the desired version when you want to use ASW.


During the installation of Microsoft SQL Server Express 2005 SP2 on non-English versions of Windows XP SP3, a message appears, saying that the installation

If no additional errors appear and the SQL Server installation completes successfully, ignore the message. A localized version of msxml6r.dll is


cannot update the file msxml6r.dll because it is protected by Windows.

installed with Windows XP SP3, and SQL Server fails when trying to overwrite it with the English version, but the localized version works.

This conflict exists within Microsoft SQL Server (2005 and 2008) and Windows XP SP3, and is described at:

http://support.microsoft.com/kb/958897

If you have enabled Windows Sharepoint Services 3.0 or Windows Server Update Services 3.0, and the Microsoft SQL Server 2005 Embedded Edition included in these products is running, it is possible to install Aspen Properties Enterprise Database (APED) on this server. This server is not suitable for APED and connections may fail without additional configuration.

When offered the choice of different SQL Server instances to install on, do not select MICROSOFT##SSEE.

You can also disable this server during the installation to avoid installing APED on it. Click Start | Settings | Control Panel, then double-click Administrative Tools, then double-click Services. Locate Windows Internal Database(MICROSOFT##SSEE) and Stop the service.


The Reboiler Wizard in the RadFrac block is not able to prevent you from deleting one of the linked blocks when the Maintain link feature is used.

You should clear the Maintain link checkbox before deleting one of these blocks; otherwise you may experience unpredictable effects. When you delete a block, any Calculator blocks referencing it may be marked incomplete. You should delete those blocks as well.

When loading an Aspen Plus document (*.apw file) for a synced Equation-Oriented simulation, you may end up with a non-square problem because of errors restoring the state of the EO model when there are connections made to user-defined Ports within a Hierarchy block, or when there are Measurements.

Save the run before syncing to EO to avoid this problem. Given the already-synced run, switch to Sequential Modular, then reinitialize and save at this point. Then you can switch to EO and the sync will re-establish the correct set of variables and equations.

In any simulation with user subroutines, the Tools | Conceptual Design | Azeotrope Search and Ternary Maps features do not work.

Use Tools | Analysis | Property | Ternary to generate ternary and azeotrope data, and use the Plot Wizard on the ternary results to generate the ternary map.

In some cases, if you use the Insert Block command in the context (right-click) menu of a stream within a Hierarchy subflowsheet, Aspen Plus crashes.

To avoid this problem, do not use Insert Block within Hierarchy subflowsheets. Instead, add the block from the Model Library and use the Disconnect and Reconnect commands on the context menu and the stream from the Model Library to connect it.

When using the Block Summary grid to change specifications, if you change the units for a variable and then change the value of the variable, the value is changed to the new value on the block's forms, but in the original units, and thus

Specify the value in the old units and then change units to verify the value, if desired, or change the units and value in the Data Browser. You can select the block in the Block Summary grid and



is the wrong value. click to open the Data Browser to its forms.

The options in the Tools | Options | Flowsheet tab which enable the display of connections will not show connections from Design Spec, Transfer, and Calculator blocks to associated streams, or from Measurement blocks that are not placed inline in material streams to associated streams.

This deficiency will be addressed in a future version.

The OLI Interface V7.0







The OLI Interface V7.1






The OLI models FraChem and Eflash4 may run into numerical problems and will not solve.

We plan to provide a patch to resolve these issues. The patch will be downloadable from the AspenTech Support web site when it is available.


Aspen Properties V7.0






When loading a file from version 2006 which contains temperature-dependent parameters from the NIST databank, input is incomplete.

This happens because version 2006 did not contain the units for these parameters in the database. Versions 2006.5 and V7.0 include these units and expect them to be specified. To fix this problem, select Tools | Clean Property Parameters. Select Clean property parameters placed on input forms and then click OK twice. Then on the Components | Specifications | Selection sheet, click Review to retrieve the parameters from the database again.

Aspen Properties V7.1




During the installation of Microsoft SQL Server Express 2005 SP2 on non-English versions of Windows XP SP3, a message appears, saying that the installation cannot update the file msxml6r.dll because it is protected by Windows.

If no additional errors appear and the SQL Server installation completes successfully, ignore the message. A localized version of msxml6r.dll is installed with Windows XP SP3, and SQL Server fails when trying to overwrite it with the English version, but the localized version works.

This conflict exists within Microsoft SQL Server (2005 and 2008) and Windows XP SP3, and is described at:




If you have enabled Windows Sharepoint Services 3.0 or Windows Server Update Services 3.0, and the Microsoft SQL Server 2005 Embedded Edition included in these products is running, it is possible to install Aspen Properties Enterprise Database (APED) on this server. This server is not suitable for APED and connections may fail without additional configuration.

When offered the choice of different SQL Server instances to install on, do not select MICROSOFT##SSEE.

You can also disable this server during the installation to avoid installing APED on it. Click Start | Settings | Control Panel, then double-click Administrative Tools, then double-click Services. Locate Windows Internal Database(MICROSOFT##SSEE) and Stop the service.



Advanced Simulation Options (Aspen Plus) 19

Advanced Simulation Options (Aspen Plus)

Aspen Custom Modeler V7.0


If you have Aspen Custom Modeler V7.0 and a previous version of Aspen Custom Modeler installed and then uninstall one of these versions, the Aspen Reactions Toolkit might stop working.

Locate the file ARTProc.dll in the AMSystem\bin folder of the version that is still installed. Open a command prompt window and use the regsvr32 command to re-register this file.

For example, if you uninstalled 2006.5 after installing V7.0, you need to re-register ARTProc.dll using the following command:

regsvr32 “C:\Program Files\AspenTech\AMSystem V7.0\bin\ARTProc.dll”




The Aspen Custom Modeler Tools menu includes the item Custom Reactions Model Wizard. This wizard does not work correctly and should not be used.

Please check on the Aspen Custom Modeler section of the AspenTech support web site for a fix to this issue. You can access this by starting Aspen Custom Modeler, going to the Help menu and selecting “Product support on the web”.

20 Advanced Simulation Options (Aspen Plus)

Aspen Custom Modeler V7.1


If you have Aspen Custom Modeler V7.1 and a previous version of Aspen Custom Modeler installed, and then uninstall one of these versions, the Aspen Reactions Toolkit may stop working.

Locate the file ARTProc.dll in the AMSystem\bin folder of the version that is still installed. Open a command prompt window, and use the regsvr32 command to re-register this file.

For example:


If you have Aspen Custom Modeler V7.1 and a previous version of Aspen Custom Modeler installed, and then uninstall one of these versions, the Optimization, Estimation or Online Links may stop working or cause the message: “An unsupported operation was attempted”.

Locate the file: “VSFlex7L.ocx” in the C:\Windows\System32 folder and use the regsvr32 command to re-register this file.

For example:

regsvr32 “C:\Windows\System32\VSFlex7L.ocx”

If you have Aspen Custom Modeler V7.1 and a previous version of Aspen Custom Modeler installed, and then uninstall one of these versions, the Properties dialog for the Plot form may stop working.

Locate the file “pfsplotv230.ocx” in the “C:\Program Files\Common Files\AspenTech Shared” folder and use the regsvr32 command to re-register this file.

For example:

regsvr32 “C:\Program Files\Common Files\AspenTech Shared\ pfsplotv230.ocx”




Model Export will not work if you are outputting to a file name or folder that contains multi-byte characters. This is usually only a problem if you are using a version of Windows configured for Asian languages such as Chinese or Japanese.

Export only to filenames and folder names consisting of ASCII characters.

On Vista systems, if you Configure Physical Properties and choose “Edit using Aspen Properties” the Aspen Properties GUI may launch behind your current ACM window.

Click on the Aspen Properties program in the Windows Taskbar to make Aspen Properties GUI the top window.


Aspen Model Runner V7.0







Aspen Model Runner V7.1


If you have Aspen Model Runner V7.1 and a previous version of Aspen Model Runner installed, and then uninstall one of these versions, the Optimization, Estimation or Online Links may stop working or cause the message: “An unsupported operation was attempted”.


For example:


If you have Aspen Model Runner V7.1 and a previous version of Aspen Model Runner installed, and then uninstall one of these versions, the Properties dialog for the Plot form may stop working.


For example:







Aspen Plus Dynamics V7.0 (formerly Aspen Dynamics)






In V7.0, the following Aspen Plus objects can be displayed graphically: design-specs, calculator blocks, and transfer blocks. When you export to dynamics, these objects are shown on the graphical flowsheet but they are not used by the dynamic simulation.

Please ignore these graphical objects.

USERACM reactions in Aspen Plus are not exported to Aspen Plus Dynamics.

All other ACM exported models can be exported. The support for USERACM reactions will be restored as soon as possible.

This issue occurs if in Aspen Plus you have a MCompr model with the following conditions: • Coolers valid phases = Vapor-Liquid-

Liquid • One (or more) of the inter-stage

Knock Out product stream flow rates = 0

In this case if you export the simulation to Aspen Plus Dynamics, the export will fail with a fatal error.

In Aspen Plus, on the Setup form Convergence tab, set Coolers valid phases = Vapor-Liquid.

If, in Aspen Plus, you have a feed stream with the following conditions: • A Mixed substream present • Flow rate = 0 • Pressure and Vapor Fraction specified

And you export the simulation to Aspen Plus Dynamics, the simulation will be over specified by 1.

In Aspen Plus, set the feed stream flow to a small value, for example 1e-5.


If, in Aspen Plus, you have a RadFrac or PetroFrac model with the following conditions: • Pack Rating is defined • Vendor type of Packing is either

NORTON or GENERIC

And you export the simulation to Aspen Plus Dynamics, the export will fail with a fatal error.

Change vendor type to one of the following: • MTL • GLITSCH • RASCHIG

The documentation for the Aspen Plus Dynamics Example Simulations is in the wrong location in the help contents.

To find this help, look in the contents under “Using DMCplus Controllers”

-> “Example of Using a DMCplus Controller”

Aspen Plus Dynamics V7.1 (formerly Aspen Dynamics)


If you have Aspen Plus Dynamics V7.1 and a previous version of Aspen Plus Dynamics installed, and then uninstall one of these versions, the Aspen Reactions Toolkit may stop working.


For example:


If you have Aspen Plus Dynamics V7.1 and a previous version of Aspen Plus Dynamics installed, and then uninstall one of these versions, the Optimization, Estimation or Online Links may stop working or cause the message: “An unsupported operation was attempted”.


For example:


If you have Aspen Plus Dynamics V7.1 and a previous version of Aspen Plus Dynamics installed, and then uninstall one of these versions, the Properties dialog for the Plot form may stop working.


For example:






Model Export will not work if you are outputting to a file name or folder that contains multi-byte characters. This is usually only a problem if you are using a version of Windows configured for Asian languages such as Chinese or Japanese.

Export only to filenames and folder names consisting of ASCII characters.

On Vista systems, if you Configure Physical Properties and choose “Edit using Aspen Properties” the Aspen Properties GUI may launch behind your current ACM window.


Aspen Adsorption V7.0 (formerly Aspen Adsim)








Aspen Adsorption V7.1 (formerly Aspen Adsim)


If you have Aspen Adsorption V7.1 and a previous version of Aspen Adsorption installed, and then uninstall one of these versions, the Optimization, Estimation or Online Links may stop working or cause the message: “An unsupported operation was attempted”.


For example:


If you have Aspen Adsorption V7.1 and a previous version of Aspen Adsorption installed, and then uninstall one of these versions, the Properties dialog for the Plot form may stop working.


For example:





On Vista systems, if you Configure Physical Properties and choose “Edit using Aspen Properties” the Aspen Properties GUI may launch behind your current Aspen Adsorption window.



Aspen Utilities Planner V7.0







Aspen Utilities Planner V7.1




Uninstalling Aspen Utilities Planner V7.0 causes Aspen Utilities Planner V7.1 to give a “STS_F_Failure” error after optimization.

The cause is not known. A “repair” installation fixes the problem.



Process Modeling (HYSYS) 27


Aspen HYSYS V7.0


Restore File Association fails to set the latest version of HYSYS as the default automation server when multiple versions of HYSYS are installed in the same machine. Remember that when installing HYSYS, the latest version is NOT the active automation server by default.

If Restore File Association is run on the latest HYSYS version and fails, try the following workaround: • Using a command, go to the directory

where the current active HYSYS automation server is installed, e.g. HYSYS 2006.5. Run the following command: hysys.exe /unregserver.

• Using a command window, go to the directory where the last version of HYSYS is installed, e.g. HYSYS V7.0. Run the following command: hysys.exe /unregserver and then hysys.exe /regserver.

When called from VB clients, older versions of HYSYS fail to run as automation servers in the presence of newer HYSYS versions installed in the same machine.

This problem can affect the integration of HYSYS with Aspen Process Economic Analyzer and Aspen Exchanger Design and Rating.

The reason for this problem is that VB loads the latest version of the HYSYS type library, regardless of the version that has been associated through the VB references. Therefore, the VB automation client must call the latest installed version of HYSYS.

To solve this problem, you must make sure that the latest version of HYSYS is the active Automation Server. To do so you should run Restore File Association from Program Files | Aspentech | Process Modeling V7.0 | Aspen HYSYS | Restore File Associations. If this does not solve the problem, follow the registration/unregistration procedure described in the known issue above.

Contact Aspentech Customer Support for more details.

28 Process Modeling (HYSYS)


Not applicable Not applicable


Cost and Sizing: Whenever a change is made on the equipment grid in HYSYS (e.g., change equipment size or add a quoted cost) and then the component is re-estimated, the Direct Cost does not update with the new pricing.

To see the updated results, close down the grid and re-open it to get the new cost. This issue will be fixed in the next release.

Thermosiphon heat exchanger inside a column: If the thermosiphon circulation calculation method is Find flow and the user clicks the Transfer UA to End Point button, the reboiler feed flow spec is locked and the user cannot change the spec value or deactivate it.

Change Find flow to Fixed flow before clicking the Transfer UA to End Point button.

HYSYS will ignore the chemistry definitions in imported Aspen Properties bkp files.

Create the fluid package in HYSYS with Chemistry.

HYSYS with Aspen Properties: Electrolyte models involving light gases could give incorrect answers because Henry Constants are retrieved from incorrect databases.

Not Applicable.

Importing an internal optioned template created with an Aspen Properties based fluid package will crash HYSYS if it tries to reuse an existing Fluid Package in the importing case.

When a window pops up and asks if to reuse an existing fluid package, decline to re-use it. This will be fixed in the next release.

Worksheet of blocks with feed stream inlets will show only the SM values and can be inconsistent with the EO state.

The same applies to the user specified variables in SM forms.

Use the EO Variable grid to see the correct values associated with the feed stream.

Analyzer and HXFlux will fail to see streams not connected to any EO blocks including the ones connected only to ACM blocks.

Create a fake EO block (mixer) and connect the stream to it.

HYSYS allows editing the Fluid Package for a case already synced to EO mode without switching to SM mode.

Manually switch to SM mode and then edit the Fluid Package.


Reaction set with conversion reactions can not be attached to a Fluid package with Aspen Properties.

Not Available.

Heater in EO with both pressure drop correlation parameter spec and temperature change spec will not be recalled correctly.

Use pressure drop spec instead of pressure drop correlation parameter spec if possible. This will be fixed in the next release.

Aspen HYSYS V7.1






A consistency error can be observed when loading and simulating a HYSYS XML case. A possible reason is an over specification where a HYSYS variable initialized with a default value at the same time the solver is trying to calculate it.

Open the view of the unit operation that owns the variable mentioned in the consistency error dialog. If the variable is shown in red simply delete it and allow the solver to calculate it.

Aspen HYSYS Dynamics V7.0






ACM models with no port definitions can be placed in Aspen HYSYS and solved in steady state, but they will fail in dynamic mode.

Create an inlet and outlet port for the ACM model and equate all the outlet port variables to the inlet port variables.

Quick approximation used to compute A correction is available but it needs


the tray residence time in dynamics might lead to mistakes when important imbalances exist between the vapor from below a given tray and the vapor to above.

further testing before it is released.

Aspen HYSYS Dynamics V7.1






No known issues No known issues

Aspen HYSYS Upstream V7.0


Aspen Hydraulics 2006.5 might not be fully functional in the presence of Aspen Hydraulics V7.0.

A .NET configuration file called hysys.exe.config should be installed in the Aspen HYSYS 2006.5 installation folder. This can be obtained from AspenTech Customer Support after the V7.0 release.

Aspen Hydraulics V7.0 might not work after uninstalling Aspen Hydraulics 2006.5.

In this case, Aspen Hydraulics V7.0 needs to be registered again. Contact AspenTech customer support for more information. This coexistence problem will be fixed in the coming release.




DBR PVT PRO does not work under Windows Vista. This component tries to write to a file in the Program Files folder which is not allowed in Vista.

In order to run DBR PVT PRO in Vista, you need to run HYSYS as an administrator. From the Start menu | Program Files | Aspentech | Process Modeling | Aspen HYSYS, select


HYSYS, right-click, and select Run as an administrator. You can also browse to HYSYS using Windows Explorer and select Run as an administrator. Notice that it is NOT enough to log in as an administrator.

Aspen HYSYS Upstream V7.1


Previous versions of Aspen Hydraulics, i.e. 2006.5 and V7.0 may not be fully functional in the presence of Aspen Hydraulics V7.1

The .NET configuration file hysys.exe.config should be installed in the installation folder of HYSYS 2006.5 or HYSYS V7.0. There is a specific file for each of the previous HYSYS versions. The file can be obtained from Aspentech Customer Support.




DBR PVT PRO does not work under Windows Vista. It was found that this component tries to write to a file under Program Files folder which is not allowed in Vista.

In order to run DBR PVT PRO in Vista you need to run HYSYS as an administrator. From the Start menu | Program Files | Aspentech | Process Modeling | Aspen HYSYS select HYSYS and right click and select run as an administrator. You can also browse to HYSYS using windows explorer and select run as an administrator. Notice that it is NOT enough to log in as an administrator.


Aspen HYSYS Petroleum Refining V7.0 (formerly Aspen RefSYS)


No Known issues Not applicable




Any hydrocracker or reformer template or case with a hydrocracker or reformer created before v2006 will not open in V7.0.

Open the case in v2006 and save it. The saved case should open in V7.0.

Any FCC or case with an FCC created before v2006 will not recall properly in V7.0. The case may run, but the results are not reliable.

Open the case in v2006 and save it. The saved case should open fine in V7.0.

If you run a calibration in the reformer or hydrocracker, all other EO unit ops will not solve until the objective function has been unset.

You can unset the objective function by running a simulation for the hydrocracker or reformer. Alternatively, from any command window for the EO environment, you can type the command “set objective = none”.

Temperature, Pressure, and Composition specified for an external hydrogen makeup stream do not get passed to the hydrocracker environment.

Manually enter the same temperature, pressure, and composition in the hydrocracker environment or connect the variables with a HYSYS spreadsheet.

If you run a calibration in FCC and return to the simulation environment without pushing the calibration data, some values are reset incorrectly. For most FCCs, this affects only the sulfur curve. For 2-stage regenerator units, though, the regenerator performance will be affected.

Make sure to save your calibration factor set and push your calibration data to the simulation before returning to the simulation environment.


In the FCC calibration environment, the predictions will not run if the regenerator specs don’t match the regenerator specs from your simulation environment.

Specify the regenerator specs for prediction runs that match your simulation regenerator specs.

Petroleum Shift Reactor (PSR) cannot run PIMS submodels in Vista Operating System.

Not available.

In PSR, even though an assay is referenced by the PSR, the Assay Manager wizard allows deleting the assay.

Before you delete an assay, make sure it is not referenced by a PSR.

Using supplementary feeds in PSR creates some display issues on the Product Spec Page.

You may ignore the rows that correspond to the supplementary feeds on the product spec table. It is solely a display issue.

After the PSR is created, if the user changes the name of a product stream (by entering a different name after opening the stream’s properties page), the change isn’t reflected in the PSR’s internal structures.

Avoid changing product stream’s name.

Macro-cut information can not be exported to ASW.

First export Macro-cut information to a HYSYS spreadsheet and then export the HYSYS spreadsheet value to ASW.

In many cases, liquid density can not be shifted with manipulator.

Not available.

Stream cutter with reformer transition generates incorrect output composition.

Not available.

PIMS assay can not be imported with Aspen Properties fluid package.

Not available.

Conversion reactors with reaction sets using components from reformer or hydrocracker component list cannot be solved.

The problem will be fixed in V7.1.

Reaction set having conversion reactions can not be attached to a Fluid package with Aspen Properties

Not available.

If a HYSYS spreadsheet cell has an attachment as a composition of a stream having a reformer or hydrocracker component list, the cell shows empty values.

User needs to re-establish the link between stream composition and HYSYS spreadsheet.

Transfer of calibration data to short cut column does not work if petroleum assay utility is already attached to Rigorous Column Internal Streams.

Delete all the petroleum assay utilities connected with rigorous column internal stream before transferring calibration data.

Manipulator can not take in yield values in composition view.

First enter distillation temperature and then it will create a space for yield. User can then enter yield values.


Aspen HYSYS Petroleum Refining V7.1 (formerly Aspen RefSYS)






Petroleum Shift Reactor: Some of the screen shots of the User Manual are not up to date.

On the property view page, the Product Specs and Product Properties tabs are merged.

A new button is added to export smc/cme files from Petroleum Shift Reactor.

HYSYS might close sometimes if in a Petroleum Shift Reactor or EOSubmodel, a CME file with an incorrect format is loaded.

Ensure that the CME file is of the correct format by opening it in the CME Visual Executive before loading in HYSYS.

Common Model Utility: On the Variables page, the HYSYS Description is different from CME variable description.

The HYSYS Description is an internal description of the variable and is not to be confused with the CME variable description.

EOSubmodel: A case saved as XML file cannot be reloaded

Not available.

In rare scenarios, a unit op or a stream in a recalled case might issue a message that a particular correlation property is missing.

Just save the case in V7.1 and reload the case.

Any hydrocracker or reformer template or case with a hydrocracker or reformer created before v2006 will not open in V7.1.

Open the case in v2006 and save it. The saved case should open fine in v2006.5 or later.

Any FCC or case with an FCC created before v2006 will not recall properly in V7.1. The case may run, but the results are not reliable.

Open the case in v2006 and save it. The saved case should open fine in v2006.5 or later.

If you run a calibration in the reformer or hydrocracker, all other EO unit ops will not solve until the objective function has been unset.

You can unset the objective function by running a simulation for the hydrocracker or reformer. Or from any command window for the EO environment, you can type the command “set objective =


none”.

Temperature, Pressure and Composition specified for an external hydrogen makeup stream do not get passed to the hydrocracker environment.

Manually enter the same temperature, pressure, and composition in the hydrocracker environment, or connect the variables with a HYSYS spreadsheet.

If you run a calibration in FCC and return to the simulation environment without pushing the calibration data, some value get incorrectly reset. For most FCCs, this affects only the sulfur curve. For 2-stage regenerator units, though, the regenerator performance will be affected.

Make sure to save your calibration factor set and push your calibration data to simulation before returning to the simulation environment.

In the FCC calibration environment, the predictions will not run if the regenerator specs don’t match the regenerator specs from your simulation environment.

Specify the regenerator specs for prediction runs that match your simulation regenerator specs.

If a HYSYS spreadsheet cell has an

attachment as a composition of a

stream having a reformer or

hydrocracker component list, the cell

shows empty values.

User needs to re-establish the link

between stream composition and HYSYS

spreadsheet.

Exchanger Design and Rating 37

Exchanger Design and Rating

All Exchanger Design and Rating Products V7.0






Aspen Simulation Workbook Interface Copy/Paste functionality will not work with Materials of Construction input variables.

Not available

Aspen Simulation Workbook Interface Copy/Paste functionality for List type input variables will only work if an item in the list is selected with a click and then Copy/Paste function is exercised.

Always reselect the desired item in the list prior attempting a Copy/Paste to Aspen Simulation Workbook.

Another option is to access the variables from the Aspen Simulation Data browser.

Drag/Drop to Excel spreadsheet will not work for those List variables that are enclosed in Frames.

Not available

38 Exchanger Design and Rating

All Exchanger Design and Rating Products V7.1


Input/result files created with newer program versions may lose input/result data if they are opened and saved using an older version of the program.

Input/Result files are not totally backward compatible. All files should be forward compatible. If you attempt to open a new file with an older program version, we recommend renaming the file so that there are multiple versions

Switching back and forth between different versions of the EDR programs can cause program crashes unless the version being used is properly registered.

If users maintain multiple versions of the EDR programs on their machines and routinely switch between versions, it is recommended that the version to be used be registered using the Version Control utility provided in the Startup menu. Upon installation, the installed version is registered. There is no need to use the version control utility unless you attempt to run an earlier program version.

Switching back and forth between different versions of the EDR programs and attempting to use Aspen Properties for physical properties can sometimes cause problems with inconsistent results.

If users wish to use a different version of the EDR programs, we recommend that the same version of Aspen Properties be used. This will require that you re-register the correct version of Aspen Properties using the registry fix utility found in the Startup menu.




Aspen Simulation Workbook will only allow a single EDR file to be accessed. If more than 1 is added and then one is deleted, the program will crash.

Fix will be available in cumulative patch.


Aspen Air Cooled Exchanger V7.0 (formerly Aspen ACOL+)






Tube OD, tube ID, and tube wall thickness inputs will not be recognized by the program until the data has been specified and the cursor has been moved to another input field. For example, if the user has 0.75 inch specified for the tube OD and changes this value to 1 inch but leaves the cursor on the input field and immediately runs the program, the calculation engine will not recognize the tube OD has been changed to 1 inch and will continue to use 0.75 inch.

After setting a new tube OD, ID, or wall thickness, always place the cursor on another input field or move to another input form prior to running the program.

Aspen Air Cooled Exchanger V7.1 (formerly Aspen ACOL+)








Aspen Fired Heater V7.0 and V7.1 (formerly Aspen FiredHeater)







Aspen Shell & Tube Exchanger V7.0 and V7.1 (formerly Aspen TASC+)








Aspen Shell & Tube Mechanical V7.0 and V7.1 (formerly Aspen TEAMS)







Aspen Plate Exchanger V7.0 and V7.1 (formerly Aspen Plate+)







Aspen HTFS Research Network V7.0 and V7.1








Aspen MUSE V7.0 and V7.1







Plate Fin Exchanger V7.0








Plate Fin Exchanger V7.1






Importing MUSE files (.MUI) is mostly straightforward, but sometimes manual editing of the imported case geometry is necessary.

You should always check an imported geometry, by looking at the diagrams of the exchanger and all its layer types and supplying missing data. Make sure the MUI file has layer types defined before import.

Some input items are not accessible in V7.1 PlateFin.

This has been done deliberately for features from MUSE not reproduced in PlateFin for the first release. Examples are longitudinal conduction, and X-flow parameters. These will be made available at the earliest opportunity.

The facility to export to Excel transfers only a limited number of parameters, and export to Word is not yet available.

You can modify the Excel template to link to other output parameters that you select. To export to Word, use Export to Excel, then copy into Word.

Economic Evaluation 45

Economic Evaluation

Aspen Capital Cost Estimator V7.0 (formerly Aspen KBase)




When running any Economic Evaluation product for the first time as a restricted user on Terminal Server, the Economic Evaluation Resiliency used to configure folders for the specific user account might not run. A symptom of the resiliency not running is not having the ability to open an Economic Evaluation project.

There is a tool located in the X:\Program Files\AspenTech\Economic Evaluation V7.0\Program\Sys folder that will simulate resiliency. Run HKCURegistry.exe once per restricted user to resolve the issue.


The maximum Number of COAs is limited to 999 in a project.

Projects should have less than 1000 COAs. This issue will be addressed in V7.0 CP1.

Opening or attaching a Volumetric Model Library item with specifications for Pipe Item Detail line sizing fields does not show the values in the GUI.

The values are saved to the file when initially specified but are being lost when re-opened or attached. No workaround exists.

46 Economic Evaluation

Importing a vertical flat bottom storage tank from one project to another where the base units of measure differ between the two projects produces an error when evaluating an item in the destination project when the original value is greater than the maximum allowed value in the target project.

Manually make the appropriate conversion and specify the corresponding units in the specification form.

Clicking the red arrow button in COA fields while editing an external index file’s location indexing does not bring up a selection dialog for picking a COA number.

Workaround is to manually type in the desired value.

Values greater than 1000 or negative values can be specified in the main category fields in an external index file for material or man hour specifications.

Validation is currently not present at the main category level of these specification forms. When entering values here, do not enter invalid data since that would cause errors to be reported during cost evaluation when the external index file is in use.

Using lower case characters in a customized input unit of measure can cause minimum, max, and default values to not appear in the properties window or as blue text.

Workaround is to not use lower case letters in customized input units of measure. The issue seems to mainly affect fields that have values that need to be calculated based on other project settings, for example RPM.

Aspen Capital Cost Estimator V7.1 (formerly Aspen KBase)




When running any Economic Evaluation product for the first time as a restricted user on Terminal Server, the Economic Evaluation Resiliency used to configure folders for the specific user account may not run. A symptom of resiliency not running is not having the ability to open an Economic Evaluation project.


When some data files installed by the Economic Evaluation installation are edited by an Administrative user, and then a different non-Administrator user uses the same installation, errors during the first-run configuration or when using

Modifying the folder/file permissions so that the non-Administrator user has full access to these data files, will resolve the issue.


the edited data files can occur.


Opening or attaching a Volumetric Model Library item with specifications for Pipe Item Detail line sizing fields does not show the values in the GUI.

The values are saved to the file when initially specified but are being lost when re-opened or attached. No workaround exists.

Importing a vertical flat bottom storage tank from one project to another where the base units of measure differ between the two projects produces an error when evaluating item in destination project when the original value is greater than the maximum allowed value in the target project.

Manually make the appropriate conversion and specify the corresponding units in the specification form.…

Values greater than 1000 or negative are allowed to be specified in the main category fields in an external index file for material or man hour specifications.

Validation is currently not present at the main category level of these specification forms. Users should take care when entering values here to not enter invalid data since that would cause errors to be reported during cost evaluation when the external index file is in use.


Workaround is to not use lower case letters in customized input units of measure. The issue seems to mainly affect fields that have values that need calculated based on other project settings, for example RPM.

On Vista, users cannot edit the datafile for User Customized Form Attributes (UserAttributesCust.xls).

Escalating to full administrator permissions allows you to modify this file.

Pressing the Help button on Spreadsheet Equipment forms generates an error that it cannot find the help file.

No workaround, help topics do not exist at this time, refer to the User Guide documentation for help.

When using the Aspen Shell and Tube Mech program for heat exchanger design with the OS German standard numeric formatting in use, the link will fail.

Use English standard numeric formatting when using this link.

The Filter drop-down on the main application GUI toolbar does not show the whole filter text.

There is no work around, however the filter can still work properly in all other respects.

In some instances, when an equipment symbol is placed in an area which it does not belong, the equipment symbol disappears but a gray shadow remains in its place.

There is no refresh option available in the Basic Engineering drawing editor. In order to refresh the drawing and remove the shadows, the drawing must be closed and re-opened.

In Vista/Windows Server 2008, transferring large sets (Usually more than 30 items) of equipment from Aspen Capital Cost Estimator to Aspen Basic Engineering will fail.

Transfer items in batches. We have not had any instances of this when the client software is run on XP.


Area sizes do not display correctly if the drawing scale is not adjusted but simply placed or not placed at all.

The first task (this is required) when creating any Plot plan drawing is to place the drawing scale. The user must currently modify the scale, even if it’s to the default value to have the scale properly initialize the drawing.

The Label (text) showing the Area size on a plot plan drawing reports the X dimension as the Width and Y dimension as the Length.

The user can exit the Symbol to resolve the issue.

Clicking on a field in the spreadsheet view that contains a default value may cause the number of significant digits to change.

No workaround needed.

Duplicate Area names can be created if renamed within the Area Spreadsheet View.

No workaround exists for this item. Doing this will cause issues with evaluation and reporting due to areas having the same name. Users should take care as to not use duplicate area names, especially within the same report group.

Pasting a selection into a spreadsheet view will populate fields that are read-only if accessed individually.

No workaround exists. This behavior gives the user the false impression that the fields will affect costing results. The original data will be preserved when the spreadsheet view is saved via an Apply or OK button click.

Can not select multiple rows/columns in spreadsheet view while holding the CTRL key.

No workaround exists.

Cutting components in a spreadsheet view does not work. Components re-appear in spreadsheet when pasted.

No workaround exists. Either delete the extraneous components after the paste or use copy and delete rather than cut.

Plot Plan Processor feature V7.0


Transfer of plot plan results back to Aspen Capital Cost Estimator (aka Kbase) might be slow.

No workaround exists; issue will be addressed in Cumulative Patch 1 of Aspen Basic Engineering (formerly Zyqad) 7.0.


Cost Known, UCL, EML equipment items, and Piperacks cannot be transferred to plot plan processor.

No workaround exists. However, for piperacks, a piperack symbol from the left pane can be placed on the plot plan drawing. The piperack will exist on the drawing only for representative purposes and no piperack data will be transferred back to the Capital Cost Estimator (CCE) project. Future releases will transfer piperack layout information back to the CCE project. Cost Known, UCL, and EML items will be included in future releases of the 2 (BE and CCE) products.

Equipment items listed in the drawing editor stockpile are not filtered by area. All areas and equipment items are located in the plotplan tab.

No workaround exists. This to be addressed in Basic Engineering V7.0 CP1. In order to expedite equipment placement, a user can close the cost mapper and return to CCE (or look at the Basic Engineering explorer) to relate equipment to its parent area. In addition, equipment ID tags specific to area designations can be used to expedite item/area associations.

In some instances, when an equipment symbol is placed in an area where it does not belong, the equipment symbol disappears but a gray shadow remains in its place.

There is no refresh option available in the Basic Engineering Drawing Editor. In order to refresh the drawing and remove the shadows, the drawing must be closed and re-opened.

User can change the interconnected piping length (calculated from plot plan) but cannot change near-equipment length.

No workaround. It functions as designed.

There is no ability to place equipment at different structure levels graphically; no elevation view of open steel structures and pipe racks is available.

No workaround; the vertical location of equipment is indicated in Capital Cost Estimator (equipment forms) or Basic Engineering (explorer) only.

All equipment in a project is placed in a single sheet. There is no ability to generate area drawings or to copy drawings or parts of a drawing to another sheet.

No workaround.

Additional missing components that have not been added to plot plan functionality include substations, plant bulk piping, headers, and firewater systems.

No workaround. To be addressed in future releases.

Exclusion zones around equipment, equipment plan size, and symbols for equipment and symbols for areas may not be changed in the plot plan.

Exclusion zone dimensions and equipment footprint dimensions can be changed in Capital Cost Estimator (equipment forms) or Basic Engineering (explorer) only.






Plot Plan Processor feature V7.1







Spreadsheet Data Entry feature V7.0


Clicking a field in the spreadsheet view that contains a default value can cause the number of significant digits to change.


Duplicate Area names can be created if they are renamed within the Area Spreadsheet View.

No workaround exists for this item. Duplicate Area names will cause issues with evaluation and reporting. Users should not use duplicate area names, especially within the same report group.


No workaround exists. This behavior gives the user the false impression that the fields will affect costing results. The original data will be preserved when the spreadsheet view is saved by clicking the Apply or OK buttons.

Cannot select multiple rows/columns in spreadsheet view while holding the CTRL key.









Spreadsheet Data Entry feature V7.1







Aspen In-Plant Cost Estimator V7.0 (formerly Aspen Icarus Project Manager)




When running any Economic Evaluation product for the first time as a restricted user on Terminal Server, the Economic Evaluation Resiliency used to configure folders for the specific user account might not run. A symptom of resiliency not running is not having the ability to open an Economic Evaluation project.




The maximum Number of COAs is limited to 999 in a project.

Projects should have less than 1000 COAs. This issue will be addressed in V7.0 CP1.

Importing a vertical flat bottom storage tank from one project to another where the base units of measure differ between the two projects produces an error when evaluating an item in the destination project when the original value is greater than the maximum allowed value in the target project.


Values greater than 1000 or negative can be specified in the main category fields in an external index file for material or man hour specifications.

Validation is currently not present at the main category level of these specification forms. When entering values here, do not enter invalid data since that causes errors to be reported during cost evaluation when the external index file is in use.


Workaround is to not use lower case letters in customized input units of measure. The issue seems to mainly affect fields that have values that need to be calculated based on other project settings, for example, RPM.

Aspen In-Plant Cost Estimator V7.1 (formerly Aspen Icarus Project Manager)






When some data files installed by the Economic Evaluation installation are edited by an Administrative user, and

Modifying the folder/file permissions so that the non-Administrator user has full access to these data files, will resolve the


then a different non-Administrator user uses the same installation, errors during the first-run configuration or when using the edited data files can occur.

issue.


Importing a vertical flat bottom storage tank from one project to another where the base units of measure differ between the two projects produces an error when evaluating item in destination project when the original value is greater than the maximum allowed value in the target project.


Aspen Process Economic Analyzer V7.0 (formerly Aspen Icarus Process Evaluation)


When called from VB clients, older versions of HYSYS fail to run as automation servers in the presence of newer HYSYS versions installed on the same machine.


The reason for this problem is that VB loads the latest version of the HYSYS type library regardless of the version that has been associated through the VB references. Therefore, the VB automation client must call the latest installed version of HYSYS.

To solve this problem, you must make sure that the latest version of HYSYS is the active Automation Server. To do so you should run Restore File Association from Program Files | AspenTech | Process Modeling V7.0 | Aspen HYSYS | Restore File Associations. If this does not solve the problem follow the registration/unregistration procedure described in the following known issue.

Contact AspenTech Customer Support for more details.


Restore File Association fails to set the latest version of HYSYS as the default automation server when multiple versions of HYSYS are installed in the same machine. Recall that when installing HYSYS the latest version is NOT the active automation server by default.

If Restore File Association run on the latest HYSYS version fails try the following workaround (note: the user must have Administrator privileges in order to run this): • Using a command, go to the directory

where the current active HYSYS automation server is installed, e.g. HYSYS 2006.5. Run the following command: hysys.exe /unregserver

• Using a command window, go to the directory where the last version of HYSYS is installed, e.g. HYSYS V7.0. Run the following command: hysys.exe /unregserver and then hysys.exe /regserver.

In V7.0, an error will occur when trying to run the Aspen Process Economic Analyzer link with MUSE.

Use the 2006.5 versions of IPE and MUSE. This will be resolved in the CP1 of Aspen Process Economic Analyzer.


In Restricted User Accounts (i.e. non Administrator Accounts that did not install the software), when Economic Evaluation (EconE) products are executed for the first time after installation via the Process Engineering Console (PE Console) rather than the start menu, the EconE software will not configure properly. This can result in requests for source media or crashes the first time an evaluation is done for each project.

It is highly recommended the EconE products are run at least once from the Start Menu before they are accessed through the PE Console. This allows the EconE products to configure properly. This does not apply to users who did the installation.

When running any Economic Evaluation product for the first time as a restricted user on Terminal Server, the Economic Evaluation Resiliency used to configure folders for the specific user account might not run. A symptom of resiliency not running is not having the ability to open an Economic Evaluation project.



Loading an Aspen Plus simulation into Process Economic Analyzer (aka IPE) using the .rep file will not work in the V7.0 release.

Use the Aspen Plus .xml file (as opposed to the .rep file) when manually loading the data into Process Economic Analyzer. Loading from the .xml file is the preferred method as it is up to date with the latest Aspen Plus features and enhancements. The .rep does not contain the latest information.

Importing a vertical flat bottom storage tank from one project to another where

Manually make the appropriate conversion and specify the corresponding


the base units of measure differ between the two projects produces an error when evaluating an item in the destination project when the original value is greater than the maximum allowed value in the target project.

units in the specification form.

Values greater than 1000 or negative can be specified in the main category fields in an external index file for material or man hour specifications.

Validation is currently not present at the main category level of these specification forms. Users should take care when entering values here to not enter invalid data since that would cause errors to be reported during cost evaluation when the external index file is in use.


Workaround is to not use lower case letters in customized input units of measure. The issue seems to mainly affect fields that have values that need to be calculated based on other project settings, for example RPM.

Aspen Process Economic Analyzer V7.1 (formerly Aspen Icarus Process Evaluation)






When some data files installed by the Economic Evaluation installation are edited by an Administrative user, and then a different non-Administrator user uses the same installation, errors during the first-run configuration or when using the edited data files can occur.

Modifying the folder/file permissions so that the non-Administrator user has full access to these data files, will resolve the issue.



When called from VB clients older versions of HYSYS fail to run as automation servers in the presence of newer HYSYS versions installed on the same machine.


The reason for this problem is that VB loads the latest version of the HYSYS type library irrespective of the version that has been associated through the VB references. Therefore the VB automation client must call the latest installed version of HYSYS.

To solve this problem you must make sure that the latest version of HYSYS is the active Automation Server. To do so you should run Restore File Association from Program Files | Aspentech | Process Modeling V7.1 | Aspen HYSYS | Restore File Associations. If this does not solve the problem follow the registration/unregistration procedure described in the known issue below.

Contact Aspentech Customer Support for more details.

Restore File Association fails to set the latest version of HYSYS as the default automation server when multiple versions of HYSYS are installed in the same machine. Recall that when installing HYSYS the latest version is NOT the active automation server by default.

If Restore File Association run on the latest HYSYS version fails try the following workaround (note: the user must have Administrator privileges in order to run this):

Using a command go to the directory where the current active HYSYS automation server is installed, e.g. HYSYS 2006.5. Run the following command: hysys.exe /unregserver

Using a command window go to the directory where the last version of HYSYS is installed, e.g. HYSYS V7.0. Run the following command: hysys.exe /unregserver and then hysys.exe /regserver.

Loading an Aspen Plus simulation into Process Economic Analyzer (aka IPE) using the .rep file will not work in version V7.0 and later releases.

This is not a defect. Use the Aspen Plus .xml file (as opposed to the .rep file) when manually loading the data into Process Economic Analyzer. Loading from the .xml file is the preferred method as it is up to date with the latest Aspen Plus features and enhancements. The .rep does not contain the latest information.

The tray type specified on the equipment form is not used, and a warning is generated that “Tray type could not be determined” when a tower is sized.

No work-around.


Negative values for stream data (IE Flows or properties) cause errors when using the Map Stream to Lines features.

This is most often seen with PROII.

Do not use the Map Streams to Lines features on these cases.

Pressing the Help button on Spreadsheet Equipment forms generates an error that it cannot find the help file.

No workaround, help topics do not exist at this time, refer to the User Guide documentation for help.

When using the Aspen Shell and Tube Mech program for heat exchanger design with the OS German standard numeric formatting in use, the link will fail.

Use English standard numeric formatting when using this link.

The Filter drop-down on the main application GUI toolbar does not show the whole filter text.

There is no work-around, however the filter can still work properly in all other respects.

Clicking on a field in the spreadsheet view that contains a default value may cause the number of significant digits to change.


Duplicate Area names can be created if renamed within the Area Spreadsheet View

No workaround exists for this item. Doing this will cause issues with evaluation and reporting due to areas having the same name. Users should take care as to not use duplicate area names, especially within the same report group.


No workaround exists. This behavior gives the user the false impression that the fields will affect costing results. The original data will be preserved when the spreadsheet view is saved via an Apply or OK button click.

Can not select multiple rows/columns in spreadsheet view while holding the CTRL key.




No change of status is indicated when evaluating single equipment items. Example of this is when an equipment item is evaluated that has an error in the evaluation. The status bar will indicate the evaluation failed which is expected. However, if other equipment items are evaluated with no errors, the status bar will still indicate the failed state.

The equipment grid can be used to review specific evaluation errors. If no error is reported the evaluation is ok.

The project cache still exists after closing the simulation.

This is not a problem unless there are disk space limitations on the PC. The workaround is to delete the folder after closing the simulation.


The Economic Evaluation project is not stored with the Aspen Plus project in some instances.

Capture the Economic Evaluation project when the Aspen Plus project is open and store it with your Aspen Plus project manually.

HYSYS sample projects fail when using the Economic Evaluation features on Vista.

Copy the samples to My Documents.

Running the Integrated Sizing and Costing inside of a simulator causes the option for using the Excel spreadsheet process economics to be set for the standard Process Economic Analyzer GUI.

Mainly change the option back to use the internal spreadsheet reports if desired.

Integrated Sizing and Costing feature V7.0 (available in Aspen Plus and Aspen HYSYS)






No change of status is indicated when evaluating single equipment items. For example, when an equipment item is evaluated that has an error in the evaluation, the status bar indicates the evaluation failed, which is expected. However, if other equipment items are evaluated with no errors, the status bar will still indicate the failed state.

The equipment grid can be used to review specific evaluation errors. If no error is reported, the evaluation is ok.

The project cache still exists after closing the simulation.

This is not a problem unless there are disk space limitations on the PC. The workaround is to delete the folder after closing the simulation.


Integrated Sizing and Costing feature V7.1 (available in Aspen Plus and Aspen HYSYS)







Energy and Flare Analysis 61


Aspen Energy Analyzer V7.0 (formerly Aspen HX-Net)






In the new feature that allows the transfer of a Heat Exchanger Network from an Excel table fix format to Aspen HX-Net, networks that contain complex process stream splitters are not correctly transferred.

Improvements to this feature will be addressed in successive Aspen Energy Analyzer releases.

Aspen Energy Analyzer V7.1 (formerly Aspen HX-Net)




62 Energy and Flare Analysis



Data Extraction from Aspen Plus stops in Windows Vista or Windows Server 2008. The process hangs waiting for Connect to Engine DB to appear.

Go to Task Manager and click on the "Connect to Engine" application. When the new Connect to Engine DB window appears, tick off the “Save as Default Connection” and then click OK to continue.

Aspen Flare System Analyzer V7.0 (formerly Aspen FLARENET)






Automation Interface: Import/Export of a Flare System Analyzer case might not work if called from a VBA application through an automation call.

The user has to allow an appropriate amount of “sleep” before opening the Flare System Analyzer case in the automation code. This allows for Flare System Analyzer to initialize properly. An example VBA code to do this will be posted on the customer support website.

Aspen Flare System Analyzer V7.1 (formerly Aspen FLARENET)



Energy and Flare Analysis 63




When user tries to export/import a file through automation Flare system analyzer may throw an “Invalid OLEVERB structure” error when “OpenModel” method of the Application interface is called. This is because the VBA code may call the “OpenModel” method of the Application interface before Flare System Analyzer is completely initialized.

The workaround for this problem is to wait for a few seconds before calling the “Openmodel’ of the Application. This can be accomplished by calling the “Sleep” Function of the Windows API which stops the execution of the VBA code for a specified time. A VBA example code will be posted in Customer support website after the V7.1 release.

Aspen HYSYS Thermodynamics COM Interface V7.0 and V7.1 (formerly Aspen COMThermo)







64 Energy and Flare Analysis

Aspen Simulation Workbook 65


Aspen Simulation Workbook V7.0






Unexpected simulation failures due to exhaustion of Windows desktop heap. See Microsoft Knowledge Base articles 126962 and 184802.

This behavior can be observed when an Aspen Simulation Workbook is configured to use the Aspen Remote Simulation Service.

The Aspen Remote Simulation Service allocates a single desktop heap which is shared among all the cases it opens.

To ensure the largest number of simulations can be run before encountering the desktop heap limitation, use the Services control panel applet to set the Aspen Remote Simulation Service properties to: • Logon as: Local System account

selected • Allow service to interact with

desktop checked

This configuration ensures that the service uses a 3072KB heap instead of the default 512KB heap.

The number of cases that the Remote

http://support.microsoft.com/?kbid=126962


66 Aspen Simulation Workbook

Simulation Service can open before encountering desktop heap exhaustion is highly dependent on the simulator technology used and the complexity of the simulation case. The heap consumption can only be determined by experiment (download the Desktop Heap Monitor Version 8.1 tool from Microsoft to help you inspect the desktop heap usage).

A conservative guideline would be to restrict use of a single Remote Simulation Service to 3 or 4 HYSYS and Aspen Plus cases, or just one Aspen Custom Modeler case.

Note: You can increase the number of Aspen Simulation Workbook applications loaded by installing Aspen Remote Simulation Service on many server computers and configuring each Aspen Simulation Workbook’s remote solver host to evenly distribute the load across those servers.

Aspen Simulation Workbook V7.1




If you have both V7.0 and V7.1 installed, and then uninstall either of them, then a shared component (cxsinteropcomv22.dll) can inadvertently become unregistered on your system. This will cause a “Failed to connect to simulation” error to occur when you try to connect to simulations.

To fix the problem, you need to re-register the file on your PC. You can do this by: • On your PC go to ‘Start Button’ -> ‘All

Programs’ -> ‘Accessories’ -> ‘Command Prompt’. This will open a command prompt window.

• In the command prompt window, type regsvr32 “[pathToFile]” where you replace “[pathToFile]” with the path to the “CxsInteropComV22.dll” file on your computer. The default location is “C:\Program Files\Common Files\AspenTech

Aspen Simulation Workbook 67

Shared\CxsInteropComV22.dll”. Note – You need to include the quotation marks around the [pathToFile] if there are any spaces in the path. After that, click the ‘Enter’ key.

• After a few seconds you should see a dialog confirming that the file was registered successfully. You can then close the command window, and ASW should work fine after that.



Aspen OOMF V7.0 and V7.1







68 Aspen Simulation Workbook

Process Development 69

Process Development

Aspen Batch Process Developer V7.0 (formerly Aspen Batch Plus)


If Batch Plus 2006.5 is uninstalled, it will unregister a file used by Aspen Batch Process Developer V7.0, causing an error when a new Unit procedure is added.

Run a “repair” of the Aspen Batch Process Developer installation.




When a React operation uses an Aspen Plus Dynamics Kinetic reactor model, the Aspen Plus Dynamics window is displayed during the Aspen Batch Process Developer simulation.

Close the Aspen Plus Dynamics window after the Aspen Batch Process Developer simulation is complete.

70 Process Development

Aspen Batch Process Developer V7.1 (formerly Aspen Batch Plus)




Aspen Properties will not open after uninstalling Aspen Batch Process Developer.

Run the “Aspen Properties Registry Fix Utility”.

By default, the example projects are installed to C:\Documents and Settings\All Users. Depending on your Windows operating system and security settings these files might not be visible.

Change your folder view options to make system files visible.

You can also search for the example projects in Windows Explorer and then open the containing folder.

If desired, copy these files to a different folder.


The BatchFrac model does not have complete data validation in the Operations UI.

The BatchFrac model will be removed altogether in V8.0.

The BatchFrac model data loading and saving works properly in V7.1 but care must be taken in entering data.

Aspen Properties might need to be initialized before it is used the first time from Aspen Batch Process Developer.

If you have a failure launching Aspen Properties or accessing the Aspen Properties Enterprise Database (APED), you should start the Aspen Properties User Interface. This will perform any necessary initialization and show any errors.

Process Development 71

Solubility Modeling V7.0 and V7.1







72 Process Development

Advanced Modeling Options (Process Development) 73

Advanced Modeling Options (Process Development)

Aspen Batch Distillation V7.0 (formerly Aspen BatchSep)






This issue affects simulations that use the BatchSep unit operation model and that were created in Aspen Plus 2006.5 CP2 or earlier. When these simulations are opened in Aspen Plus V7.0, values specified in operating steps for the following parameters will revert to their default: • Reflux Ratio • Condenser vapor • Controller set point • Controller output

Open the simulation in Aspen Plus 2006.5 and make a note of the values for the affected parameters that are specified in each operating step.

Load the simulation in to Aspen Plus V7.0. Review the specifications for the operating steps and re-enter values for parameters that are incorrect. Save the simulation.

74 Advanced Modeling Options (Process Development)

Aspen Batch Distillation V7.1 (formerly Aspen BatchSep)


If you have Aspen Batch Distillation V7.1 and a previous version of Aspen Batch Distillation installed, and then uninstall one of these versions, the forms for configuring reactions stop working.


For example:


If you have Aspen Batch Distillation V7.1 and a previous version of Aspen Batch Distillation installed, and then uninstall one of these versions, the Optimization item under the Tools menu item may stop working or cause the message: “An unsupported operation was attempted”.


For example:


If you have Aspen Batch Distillation V7.1 and a previous version of Aspen Batch Distillation installed, and then uninstall one of these versions, you may not be able to modify the properties of a displayed plot.


For example:







Aspen Reaction Modeler V7.0






This issue affects cases where the Property calculation option is set to Simple, and one or more experiments have valid-phases set to Vapor-Liquid. For these cases the fit will fail. If you display the simulation messages you will see the message: • Failed to find dynamic link library

AMPropMod (or a DLL used by it) This issue affects the example TetraChloride_NotEquil_Simple that is delivered with Aspen Reaction Modeler.

Add the folder Program Files\AspenTech\APrSystem V7.0\Engine\Xeq to your system path. To do this, go to Control Panel and select System. Select the Advanced tab. Click Environment Variables. Select PATH under either User variables or System variables. To the end of the value for PATH, add the full path to this folder.

For example: • C:\Program

Files\AspenTech\APrSystem V7.0\Engine\Xeq

Aspen Reaction Modeler V7.1


If you have Aspen Reaction Modeler V7.1 and a previous version of Aspen Reaction Modeler installed, and then uninstall one of these versions, Aspen Reaction Modeler will not work.

Reinstall Aspen Reaction Modeler using the “Repair” option.






Aspen Chromatography V7.0







Aspen Chromatography V7.1


If you have Aspen Chromatography V7.1 and a previous version of Aspen Chromatography installed, and then uninstall one of these versions, the Optimization, Estimation or Online Links may stop working or cause the message: “An unsupported operation was attempted”.


For example:


If you have Aspen Chromatography V7.1 and a previous version of Aspen Chromatography installed, and then uninstall one of these versions, the Properties dialog for the Plot form may stop working.


For example:





On Vista systems, if you Configure Physical Properties and choose “Edit using Aspen Properties” the Aspen Properties GUI may launch behind your current Aspen Chromatography window.



Aspen Process Tools V7.0 and V7.1







Aspen Process Manual V7.0 and V7.1 79

Aspen Process Manual V7.0 and V7.1

Aspen Process Manual V7.0







Aspen Process Manual V7.1


If you have previously installed an earlier version of Aspen Process Manual, then the search path for document files may point to the previous document files installation (for example, C:\Program Files\AspenTech\Aspen Process Manual V7.0 \Manual)

On the Administration page, change the Search path for document files setting (the default would be C:\Program Files\AspenTech\Aspen Process Manual V7.1 \Manual). Click on Update document server settings, and Re-index documents to index the files at the correct location.

80 Aspen Process Manual V7.0 and V7.1





Basic Engineering V7.0 and V7.1 81

Basic Engineering V7.0 and V7.1

Aspen Basic Engineering V7.0 (formerly Aspen Zyqad)






Aspen Basic Engineering V7.0 requires Cumulative Patch 1 for use.

Download and install Cumulative Patch 1 from the AspenTech Support Website.

Aspen Basic Engineering V7.1 (formerly Aspen Zyqad)





82 Basic Engineering V7.0 and V7.1


Admin tool: Crash happened when user modified privileges several times.

Only occurs after reloading the workspace multiple times (CQ00334425)

Bridge: When click the enabled box in link list the enabled state can not be changed

The workaround is to open the link and change enabled on the dialog (CQ00320926)

Drawing Editor: White-Out of the Tool Bar in Drawing Editor

That toolbar has only two buttons, thus the white space isn't hiding anything. It is supposed to be painted in grey background (CQ00321677)

Excel Datasheet Editor: Excel datasheets won’t open.

You should check “Trust access to Visual Basic Project” on the Trusted Publishers tab of the Security dialogue. Open this from Tools/Macro/Security…

Excel Datasheet Editor: Annotation & Mark up disappear when click the same field adding annotation or mark up

Only occurs if you edit annotation by clicking the same field without first clicking away (CQ00351965)

Excel Datasheet Editor: If an infinite equipment list is saved from the datasheet editor, and then opened for printing in regular Excel, the page numbers and total pages fields (if they exist) are not correctly filled in during pagination

We are investigating if this is possible in Excel (CQ00331681)

Excel Datasheet Editor: The Excel Datasheet displays zero decimal places (by default).

Values entered directly on the datasheet are not affected. Only imported values by default do not show any decimal places. The format can be changed in the usual way (CQ00350851)

Excel Datasheet Editor: If there are insufficient object to fill the last page, the footer does not appear in the correct row.

We are investigating how to fill the final page of an infinite equipment list with empty rows for printing. (CQ00331615)

Excel Datasheet Editor: - There is no indication when the field can not display the value completely

Workbench displayed >> to show the value has been truncated. Excel does not. (CQ00334658)

Excel Datasheet Editor: Filter datasheet and add a new object on continuous list will add some empty rows

Use Datasheet/pack to remove empty rows (CQ00352023)

Excel Datasheet Editor: AZ Equipment list vessel - error pops up when entering data on ID\TT column: “Cycles in the demons or application triggers exceeded the threshold.”

Use an equipment datasheet to change the value (CQ00338202)

Explorer : Batch save of multiple datasheets

Opens the datasheets but doesn't save them (CQ00333462)

Explorer: Double-clicking on submitted PPID opens the current version.

Use the Open/Submitted menu option instead (CQ00353139)

Explorer: <F-XXX IssueRecord> lock error message shows up when user

Lock errors can occur when submitting the same document twice (CQ00353136)

Basic Engineering V7.0 and V7.1 83

resubmits a datasheet within some specific situation.

IDWF: folder name for issued diagrams does not include issue reason (CQ00348026) Estimation Interface: Some data are not copied for following objects:

• CentrifugalCompressor • ShellTubeHeatExchanger • Fan • Fire Heater • Reciprocating Compressor

PackedColumn

Most data are transferred.

Simulation Interface : Expanders and valves are missing in the equipment tab in the simulation importer

Not possible to copy data from these simulation objects (CQ00353356)

Simulation Interface : errors when importing results for Aspen Plus Radfrac

Stage results are still imported (CQ00351199)

Migration: A workspace created in version 2006.5 or earlier cannot be opened if a datasheet has a name exceeding 255 characters.

Contact AspenTech support for an emergency patch which can be applied to V7.0 CP1, or version 7.1. The fix will also be included in CP2 (for V7.0) and CP1 (for V7.1) (CQ00354195)

Out of the box Datasheets: Some formatting errors (mostly overlapping sections) and for a few fields unable to change units of measurement. Occurs for the following datasheets:

• AT Elevated Flare • AT Enclosed Flare • API Combustion Gas Turbine • AT Centrifugal Fan • AT Centrifugal Pump BB • AT Centrifugal Pump OH (line 49

other field does not work) • AT Centrifugal Pump VS • AT Combustion Gas Turbine • NORSOK Waste Heat Recovery

Unit (page displays 'Sheet') • NORSOK Waste Heat Recovery

Unit • NORSOK Reciprocating

Compressor • NORSOK Pressure Vessel • NORSOK Plate Heat Exchanger • NORSOK Oil System • NORSOK Centrifugal Pump

NORSOK Centrifugal Compressor These will be corrected and included in a cumulative patch.

Plot Plan : Area Drawing Length and Width are reversed on Drawing Plot Plan : Users must set the Scale in order for Areas to work

TEF: Cannot Publish Datasheets

TEF only problem. Creates a view file during publish. Workaround: Create a file:C:\NoViewFile. This problem will become irrelevant in the next release when the Excel Datasheet functionality is

84 Basic Engineering V7.0 and V7.1

complete. Vista Only : the title of Open Workspace cannot be seen clearly

This may depend on your Vista desktop preferences, e.g. color and transparency.

Operations Support 85

Operations Support

Aspen Online Deployment V7.0


When multiple versions of HYSYS, Aspen Plus, Aspen Custom Modeler, or Aspen Exchanger Design and Rating (HTFS+) are installed, Aspen Online Deployment will use the default version.

To explicitly control which version of a process simulator is used, only install one version on the target system.





The impact of desktop heap exhaustion depends on whether the online applications are configured to use a remote solver.

Applications not using remote solver

Aspen Online Deployment is able to allocate a private desktop heap for each online application that does not use the remote solver (i.e., Aspen Remote Simulation Service). That significantly reduces the possibility of encountering the desktop heap exhaustion problem. However, it also limits the number of such applications that can be loaded.

On a Windows 2003 Server with Terminal Services installed, up to 12 online applications can be loaded if they are not configured to use a remote solver. On a Windows XP system or a Windows 2003 Server without Terminal Services



86 Operations Support

installed, just 2 or 3 online applications that do not use a remote solver can be loaded.

Applications using remote solver


To ensure the largest number of simulations can be run before encountering the desktop heap limitation, use the Services control panel applet to set the Aspen Remote Simulation Service properties to: • Logon as: Local System account

selected • Allow service to interact with

desktop checked

This configuration will ensure that the service uses a 3072KB heap instead of the default 512KB heap.

The number of cases that the Remote Simulation Service can open before encountering desktop heap exhaustion is highly dependent on the simulator technology used and the complexity of the simulation case. The heap consumption can only be determined by experiment (download the Desktop Heap Monitor Version 8.1 tool from Microsoft to help you inspect the desktop heap usage).


Note: You can increase the number of online applications loaded by installing Aspen Remote Simulation Service on many server computers and configuring each online application’s remote solver host to evenly distribute the load across those servers.


CQ00321920 - Validity Limits must be entered in a particular sequence.

In past versions of Aspen Online Deployment, you could enter values for lower and upper validity limits in any sequence desired (i.e., change the low limit first then the high limit, or vice versa). In V7.0, you must enter them in a way that does not invert the limits. For example, if the current limits are Low=0 and High=0, and you want them to be Low=100 and High=200, you must first change the high limit to 200 and then the low limit to 100. If you try to change the low limit first you will not be able to enter the value.

Error message is displayed when using the Tab key to navigate user entries.

The problem occurs when using the Tab key to navigate user entry information in the Calculations tab of the Configure Application dialog. The problem is resolved by updating the Microsoft .NET Framework. If you cannot update the Microsoft component, then you can avoid the problem by using the mouse to navigate the user entry information.

On Windows 2003 Server and Windows XP systems, this problem is eliminated by installing SP1 for .NET Framework 2.0.

On Vista systems, this problem is eliminated by installing .NET Framework 3.5.

Aspen Online Deployment V7.1


Simulator support Aspen Online Deployment V7.1 supports version 2006.5, V7.0, and V7.1 of Aspen Plus, Aspen HYSYS, Aspen Custom Modeler, and Exchanger Design and Rating. Earlier versions are not supported.

Simulator version specification A specific simulator version cannot be specified for HTFS+ (Exchanger Design and Rating) cases; the default version of HTFS+ will be used.

A specific version can be specified for Aspen Plus, Aspen HYSYS, and Aspen Custom Modeler.





Configuring Process Engineering software to be used by AOD

The AOD online server runs the process simulators under the local SYSTEM account. This can cause unforeseen problems if there are configuration settings that need to be set so that the simulators function as expected.

A good example is the selection of the Properties database. You will need to configure the SYSTEM account to use the correct properties database; to do that you'll need to run the 'Aspen Properties Database Selector' under the SYSTEM account.

Unfortunately, you cannot logon as SYSTEM. But, you can create a Command window that is running as the SYSTEM account, and then launch the configuration tools from that command window.

See the online help topic “Configuring Process Engineering software to be used by AOD”, found under “System Administration, Online Server administration” in the AOD Desktop online help.


The impact of desktop heap exhaustion depends on whether the online applications are configured to use a remote solver.

Applications not using remote solver

Aspen Online Deployment is able to allocate a private desktop heap for each online application that does not use the remote solver (i.e., Aspen Remote Simulation Service). That significantly reduces the possibility of encountering the desktop heap exhaustion problem. However, it also limits the number of such applications that can be loaded.

On a Windows 2003 Server with Terminal Services installed, up to 12 online applications can be loaded if they are not configured to use a remote solver. On a Windows XP system, or a Windows 2003 Server without Terminal Services installed, just 2 or 3 online applications that do not use a remote solver can be loaded.

Applications using remote solver





To ensure the largest number of simulations can be run before encountering the desktop heap limitation, use the Services control panel applet to set the Aspen Remote Simulation Service properties to:

a) “Logon as: Local System account” selected

b) “Allow service to interact with desktop” checked

That configuration will ensure that the service uses a 3072KB heap instead of the default 512KB heap.

The number of cases that the Remote Simulation Service can open before encountering desktop heap exhaustion is highly dependent on the simulator technology used and the complexity of the simulation case. The heap consumption can only be determined by experiment (download the “Desktop Heap Monitor Version 8.1” tool from Microsoft to help you inspect the desktop heap usage).


Note: You can increase the number of online applications loaded by installing Aspen Remote Simulation Service on many server computers and configuring each online application’s remote solver host so as to evenly distribute the load across those servers.

CQ00321920 - Validity Limits must be entered in a particular sequence

In past versions of Aspen Online Deployment you could enter values for lower and upper validity limits in any sequence desired (i.e., change the low limit first then the high limit, or vice versa). In this version (V7.1) you must enter them in a way that does not invert the limits. For example, if the current limits are Low=0 and High=0, and you want them to be Low=100 and High=200, you must first change the high limit to 200 and then the low limit to 100 -- if you try to change the low limit first you will not be able to enter


the value.

CQ00353214 – special characters in application variable name breaks web plots

Using a ‘%’ (percent) or ‘"’ (double quote) character in the Aspen Online Deployment variable name will prevent the web viewer plots from being displayed for that variable.

For example, the AOD variable name "NapthaD 95%"."Cut Pt-5.00%" should be changed to remove the quotation and percent characters, for example: NapthaD 95pct.Cut Pt-5.00pct.

Note: this restriction is on the AOD variable name (which can be modified in the Variables tab of the Configure Application dialog in the AOD Desktop); there is no such restriction on variable names in the simulation case.

CQ00354695 - Configure Online Server help button error

The help button in the Configure Online Server may not work; you may see a dialog indicating an error and giving you the option to abort or continue (you should select continue).

To see the help information for Configure Online Server, you can display the Desktop Help from the AOD Desktop Help menu and locate the topic “Configure Online Server – Dialog Box”, found under “Dialog Boxes and Screen Displays, Supporting Dialog Boxes and Windows”.

Aspen OTS Framework V7.0






If you have earlier versions of HYSYS installed, Aspen OTS Framework might attempt to use these, resulting in an error when you attempt to activate the models. If you only have HYSYS V7.0, installed you will not see this issue.

• Open a command prompt window. • Change your current folder to the one

containing the earlier version of Aspen HYSYS, for example: cd “c:\Program Files\AspenTech\Aspen HYSYS 2006.5”

• Enter the following command:


hysys.exe /unregserver • Repeat this for any other earlier

versions of HYSYS that you have installed.

• Change your current folder to the one containing Aspen HYSYS V7.0, for example: cd “c:\Program Files\AspenTech\Aspen HYSYS V7.0”

• Enter the following command: hysys.exe /regserver

When using the Browse options from the Tools menu to select variables for Control Signal Connections, you might see an unhandled exception error.

Make the HYSYS case visible and copy and paste variables from the HYSYS case to the Control Signal Connections list instead of using the Browser.

You can take a snapshot from an OPC client by setting the value of the tag Simulation.Snapshot to True. However, after you have done this, the value should be automatically reset to False so that you can take another snapshot. This is not happening.

Use the Aspen OTS Framework GUI to take snapshots.

Aspen OTS Framework V7.1







Aspen OnLine V7.0 and V7.1 93

Aspen OnLine V7.0 and V7.1







94 Aspen OnLine V7.0 and V7.1

Aspen Plus Refinery Based Reactors 95

Aspen Plus Refinery Based Reactors

Aspen Plus Catcracker V7.0 and V7.1 (formerly Aspen FCC)







Aspen Plus Hydrocracker V7.0 and V7.1 (formerly Aspen Hydrocracker)




96 Aspen Plus Refinery Based Reactors




Aspen Plus Hydrotreater V7.0 and V7.1 (formerly Aspen Hydrotreater)







Aspen Plus Reformer V7.0 and V7.1 (formerly Aspen CatRef)







Aspen Open Object Model Framework V7.0 and V7.1 97

Aspen Open Object Model Framework V7.0 and V7.1







98 Aspen Open Object Model Framework V7.0 and V7.1