P. 1
AspenEngineeringSuiteV7 1 Issues

AspenEngineeringSuiteV7 1 Issues

|Views: 1.988|Likes:
Publicado porSJSZCGRDHS

More info:

Published by: SJSZCGRDHS on Oct 28, 2010
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

05/11/2013

pdf

text

original

Sections

  • Contents
  • Introduction for V7.0 and V7.1
  • Product Name Changes in aspenONE V7.0
  • Aspen Engineering Workflows
  • Process Engineering Console V7.0
  • Process Engineering Console V7.1
  • Process Development Console V7.0 and V7.1
  • Integrated Sizing and Costing V7.0
  • Integrated Sizing and Costing V7.1
  • Process Modeling (Aspen Plus)
  • Aspen Plus V7.0
  • Aspen Plus V7.1
  • The OLI Interface V7.0
  • The OLI Interface V7.1
  • Aspen Properties V7.0
  • Aspen Properties V7.1
  • Advanced Simulation Options (Aspen Plus)
  • Aspen Custom Modeler V7.0
  • Aspen Custom Modeler V7.1
  • Aspen Model Runner V7.0
  • Aspen Model Runner V7.1
  • Aspen Plus Dynamics V7.0 (formerly Aspen Dynamics)
  • Aspen Plus Dynamics V7.1 (formerly Aspen Dynamics)
  • Aspen Adsorption V7.0 (formerly Aspen Adsim)
  • Aspen Adsorption V7.1 (formerly Aspen Adsim)
  • Aspen Utilities Planner V7.0
  • Aspen Utilities Planner V7.1
  • Process Modeling (HYSYS)
  • Aspen HYSYS V7.0
  • Aspen HYSYS V7.1
  • Aspen HYSYS Dynamics V7.0
  • Aspen HYSYS Dynamics V7.1
  • Aspen HYSYS Upstream V7.0
  • Aspen HYSYS Upstream V7.1
  • Aspen HYSYS Petroleum Refining V7.0 (formerly Aspen RefSYS)
  • Aspen HYSYS Petroleum Refining V7.1 (formerly Aspen RefSYS)
  • Exchanger Design and Rating
  • All Exchanger Design and Rating Products V7.0
  • All Exchanger Design and Rating Products V7.1
  • Aspen Air Cooled Exchanger V7.0 (formerly Aspen ACOL+)
  • 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
  • Economic Evaluation
  • Aspen Capital Cost Estimator V7.0 (formerly Aspen KBase)
  • Aspen Capital Cost Estimator V7.1 (formerly Aspen KBase)
  • Plot Plan Processor feature V7.0
  • Plot Plan Processor feature V7.1
  • Spreadsheet Data Entry feature V7.0
  • Spreadsheet Data Entry feature V7.1
  • Aspen In-Plant Cost Estimator V7.0 (formerly Aspen Icarus Project Manager)
  • Aspen In-Plant Cost Estimator V7.1 (formerly Aspen Icarus Project Manager)
  • Aspen Process Economic Analyzer V7.0 (formerly Aspen Icarus Process Evaluation)
  • Aspen Process Economic Analyzer V7.1 (formerly Aspen Icarus Process Evaluation)
  • Energy and Flare Analysis
  • Aspen Energy Analyzer V7.0 (formerly Aspen HX-Net)
  • Aspen Energy Analyzer V7.1 (formerly Aspen HX-Net)
  • Aspen Flare System Analyzer V7.0 (formerly Aspen FLARENET)
  • Aspen Flare System Analyzer V7.1 (formerly Aspen FLARENET)
  • Aspen Simulation Workbook
  • Aspen Simulation Workbook V7.0
  • Aspen Simulation Workbook V7.1
  • Aspen OOMF V7.0 and V7.1
  • Process Development
  • Aspen Batch Process Developer V7.0 (formerly Aspen Batch Plus)
  • Aspen Batch Process Developer V7.1 (formerly Aspen Batch Plus)
  • Solubility Modeling V7.0 and V7.1
  • Advanced Modeling Options (Process Development)
  • Aspen Batch Distillation V7.0 (formerly Aspen BatchSep)
  • Aspen Batch Distillation V7.1 (formerly Aspen BatchSep)
  • Aspen Reaction Modeler V7.0
  • Aspen Reaction Modeler V7.1
  • Aspen Chromatography V7.0
  • Aspen Chromatography V7.1
  • Aspen Process Tools V7.0 and V7.1
  • Aspen Process Manual V7.0 and V7.1
  • Aspen Process Manual V7.0
  • Aspen Process Manual V7.1
  • Basic Engineering V7.0 and V7.1
  • Aspen Basic Engineering V7.0 (formerly Aspen Zyqad)
  • Aspen Basic Engineering V7.1 (formerly Aspen Zyqad)
  • Operations Support
  • Aspen Online Deployment V7.0
  • Aspen Online Deployment V7.1
  • Aspen OTS Framework V7.0
  • Aspen OTS Framework V7.1
  • Aspen OnLine V7.0 and V7.1
  • 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)
  • 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

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

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 Aspen Aspen Aspen Aspen Aspen Aspen Aspen Aspen Aspen Custom Modeler V7.0 ...........................................................................19 Custom Modeler V7.1 ...........................................................................20 Model Runner V7.0...............................................................................21 Model Runner V7.1...............................................................................21 Plus Dynamics V7.0 (formerly Aspen Dynamics) .......................................22 Plus Dynamics V7.1 (formerly Aspen Dynamics) .......................................23 Adsorption V7.0 (formerly Aspen Adsim) .................................................24 Adsorption V7.1 (formerly Aspen Adsim) .................................................25 Utilities Planner V7.0 ............................................................................26 Utilities Planner V7.1 ............................................................................26

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

Contents

1

........61 Aspen Flare System Analyzer V7............................................................................................1 ................................1 (formerly Aspen Icarus Project Manager) ...........0 and V7...32 Petroleum Refining V7..42 Plate Fin Exchanger V7..30 Upstream V7........42 Plate Fin Exchanger V7...............................................................................37 All Exchanger Design and Rating Products V7.........41 Aspen MUSE V7......................................1 ....0 (formerly Aspen FLARENET) ............50 Spreadsheet Data Entry feature V7.................0 ..1.........61 Aspen Energy Analyzer V7...............................................................................1 (formerly Aspen HX-Net) ...............0 ..............................1 ..........................63 Aspen Simulation Workbook ..........46 Plot Plan Processor feature V7....................................0 (formerly Aspen Icarus Process Evaluation) 53 Aspen Process Economic Analyzer V7................................0 (formerly Aspen RefSYS) ...................1 ..............................1 (formerly Aspen COMThermo) .........................................................................................................................................1 (formerly Aspen Icarus Process Evaluation) 55 Integrated Sizing and Costing feature V7.........0 and V7....................................................................41 Aspen Plate Exchanger V7..........................38 Aspen Air Cooled Exchanger V7.....30 Upstream V7.......................1 (formerly Aspen FiredHeater).......................59 Energy and Flare Analysis ......48 Plot Plan Processor feature V7.........................0 ............................................29 Dynamics V7...............................................................0 (formerly Aspen Icarus Project Manager) ............................0 and V7.............................1 (formerly Aspen KBase) ..................0 and V7.......0 and V7...0 .51 Aspen In-Plant Cost Estimator V7...1 (available in Aspen Plus and Aspen HYSYS).....45 Aspen Capital Cost Estimator V7...........................................1 (formerly Aspen ACOL+) ................37 All Exchanger Design and Rating Products V7...........39 Aspen Air Cooled Exchanger V7.62 Aspen Flare System Analyzer V7................................50 Spreadsheet Data Entry feature V7............34 Exchanger Design and Rating.............................................................................................................................1 ....................65 Aspen Simulation Workbook V7...................................0 (formerly Aspen KBase) ............................0 ....................40 Aspen Shell & Tube Mechanical V7........................................................67 2 Contents ............................................0 ..........1 ..............51 Aspen In-Plant Cost Estimator V7..........0 (available in Aspen Plus and Aspen HYSYS)..............31 Petroleum Refining V7.......................................................45 Aspen Capital Cost Estimator V7.........0 and V7........0 (formerly Aspen HX-Net) ...................................1 (formerly Aspen FLARENET) .................62 Aspen HYSYS Thermodynamics COM Interface V7.....0........52 Aspen Process Economic Analyzer V7................1 (formerly Aspen TASC+) ...........1 (formerly Aspen Plate+)........................................0 and V7................................0 and V7...........................1 ........................1 (formerly Aspen RefSYS) ........0 (formerly Aspen ACOL+) ......1 ...........................................................................1 (formerly Aspen TEAMS) .....................1 ..............................................39 Aspen Fired Heater V7..58 Integrated Sizing and Costing feature V7..........................................Aspen Aspen Aspen Aspen Aspen Aspen HYSYS HYSYS HYSYS HYSYS HYSYS HYSYS Dynamics V7.............65 Aspen Simulation Workbook V7................61 Aspen Energy Analyzer V7............66 Aspen OOMF V7..........41 Aspen HTFS Research Network V7...............................40 Aspen Shell & Tube Exchanger V7.............................43 Economic Evaluation ....................................................

1 (formerly Aspen Hydrocracker).......................................................................................................................................................0 .........................................0 and V7......................................................................1 (formerly Aspen BatchSep) .....................75 Reaction Modeler V7....................................................1 (formerly Aspen Hydrotreater) ..............................................1 .......................76 Process Tools V7...0 ...................................0 .......................81 Aspen Basic Engineering V7..................................76 Chromatography V7.....0 and V7......................1 ....79 Basic Engineering V7....................71 Advanced Modeling Options (Process Development).............................................0 and V7...1 ....................................................1 ....0 and V7..95 Aspen Aspen Aspen Aspen Plus Plus Plus Plus Catcracker V7...........0 ....87 OTS Framework V7...................................95 Hydrotreater V7...1 ........0 (formerly Aspen Zyqad) .....91 Aspen OnLine V7......................................................96 Aspen Open Object Model Framework V7..1 ........................1 .1 (formerly Aspen FCC) .......................................1 ............................................................70 Solubility Modeling V7.0 and V7.................85 Online Deployment V7.........................0 (formerly Aspen Batch Plus) ....0 (formerly Aspen BatchSep) ......................69 Aspen Batch Process Developer V7..........................................................................................................0 and V7......96 Reformer V7.........................81 Operations Support .......1.....................95 Hydrocracker V7..69 Aspen Batch Process Developer V7.....................85 Aspen Aspen Aspen Aspen Online Deployment V7.......74 Reaction Modeler V7.90 OTS Framework V7....1 (formerly Aspen Zyqad) .77 Aspen Process Manual V7......................................................................1 (formerly Aspen CatRef) ....................79 Aspen Process Manual V7..........81 Aspen Basic Engineering V7............................1 (formerly Aspen Batch Plus) .75 Chromatography V7...............................................................0 and V7..........0 ................................93 Aspen Plus Refinery Based Reactors .................................................................1 ..................................0 and V7...............................79 Aspen Process Manual V7.....0 and V7......73 Batch Distillation V7.....................97 Contents 3 ..Process Development ...........................0 and V7.........................................................................................................................................1 ....................................73 Aspen Aspen Aspen Aspen Aspen Aspen Aspen Batch Distillation V7..

4 Contents .

Use the chart below to see the new product names and their corresponding installation selections. Introduction for V7.com).0. Please refer to the tables in each product section for issues relating to the products you are using.1 5 .0 and V7. Installation issues (potential problems arising during the install or uninstall procedure).1 This document contains a summary of known issues or limitations relating to this release.0 With the release of aspenONE V7. Known issues are listed as those relating to: • • • Coexistence issues (different versions of products on the same computer).Introduction for V7. Usability issues (interface issues that will be addressed in future releases/hot fixes). Note: For additional information about Known Issues. AspenTech still use these new names.0 and V7. To the release of aspenONE V7. see the AspenTech Support web site (http://support.1. AspenTech has made the decision to provide more functional names to several of its Process Engineering products. Product Name Changes in aspenONE V7.aspentech. The new names will reflect the function/role that each product performs as part of the overall Aspen Engineering. see the aspenONE Known Issues on the Documentation DVD. The installation has also been reorganized to reflect functional groups. Workarounds are suggested where possible. For additional information about issues relevant to the complete product line.

1 .0 and V7.0 Aspen Air Cooled Exchanger Aspen Adsorption Aspen Batch Process Developer Aspen Batch Distillation Install Mapping (What to Install) Exchanger Design And Rating Process Modeling (Aspen Plus) Process Development Process Development Process Modeling (Aspen Plus) Required Install Option Selection --Advanced Simulation Options --Advanced Modeling Options Advanced Simulation Options --Advanced Modeling Options Energy and Flare Analysis Advanced Simulation Options Advanced Simulation Options Advanced Simulation Options ----Energy and Flare Analysis Energy and Flare Analysis --Energy and Flare Analysis Energy and Flare Analysis ----------- Aspen CatRef® Aspen Chromatography® Aspen COMThermo® Aspen Custom Modeler® Aspen Plus® Reformer Aspen Chromatography® Aspen HYSYS® Thermodynamics COM Interface Aspen Custom Modeler® Aspen Plus Based Refinery Reactors Process Development Process Modeling (HYSYS) Process Modeling (Aspen Plus) Process Modeling (HYSYS) Aspen Dynamics® Aspen FCC® Aspen FiredHeater Aspen FLARENET™ Aspen Plus® Dynamics Aspen Plus® CatCracker Aspen Fired Heater Aspen Flare System Analyzer Process Modeling (Aspen Plus) Aspen Plus Based Refinery Reactors Exchanger Design And Rating Process Modeling (Aspen Plus) Process Modeling (HYSYS) Aspen HTFS Research Network™ Aspen HX-Net® Aspen HTFS Research Network™ Aspen Energy Analyzer Exchanger Design And Rating Process Modeling (Aspen Plus) Process Modeling (HYSYS) Aspen Hydrocracker® Aspen Hydrotreater™ Aspen HYSYS® Aspen HYSYS Amines™ Aspen HYSYS Dynamics™ Aspen Plus® Hydrocracker Aspen Plus® Hydrotreater Aspen HYSYS® Aspen HYSYS Amines™ Aspen HYSYS Dynamics™ Aspen Plus Based Refinery Reactors Aspen Plus Based Refinery Reactors Process Modeling (HYSYS) Process Modeling (HYSYS) Process Modeling (HYSYS) 6 Introduction for V7.5 Aspen Acol+™ Aspen Adsim® Aspen Batch Plus® Aspen BatchSep™ Product Name V7.Product Name Release 2006.

Product Name Release 2006.0 Aspen HYSYS® Pipeline Hydraulics .OLGAS 3-Phase Aspen HYSYS® Pipeline Hydraulics .OLGAS 2-Phase Aspen HYSYS® Pipeline Hydraulics .1 7 .5 Aspen HYSYS OLGAS™ Aspen HYSYS OLGAS 3-Phase™ Aspen HYSYS PIPESYS™ Aspen HYSYS RTO™ Offline Aspen HYSYS Upstream™ Aspen HYSYS Upstream Dynamics™ Aspen Icarus Process Evaluator® Aspen Icarus Project Manager® Aspen Kbase® Aspen MPIMS™ Aspen Model Runner™ Aspen MUSE™ Aspen OnLine® Aspen Online Deployment™ Aspen PIMS™ Aspen PIMS Advanced Optimization™ Aspen PIMS Submodel Calculator™ Aspen Plate+™ Aspen Plus® Aspen Plus EO Model Library (Equation-Oriented HYSYS) Aspen Plus Optimizer™ Product Name V7.0 and V7.PIPESYS Aspen HYSYS® Offline Optimizer Aspen HYSYS Upstream™ Aspen HYSYS Upstream Dynamics™ Aspen Process Economic Analyzer Aspen In-Plant Cost Estimator Aspen Capital Cost Estimator Aspen MPIMS™ Aspen Model Runner™ Aspen MUSE™ Aspen OnLine® Aspen Online Deployment™ Aspen PIMS™ Aspen PIMS Advanced Optimization™ Aspen PIMS Submodel Calculator™ Aspen Plate Exchanger Aspen Plus® Aspen Plus EO Model Library (Equation-Oriented HYSYS) Aspen Plus Optimizer™ Install Mapping (What to Install) Process Modeling (HYSYS) Process Modeling (HYSYS) Process Modeling (HYSYS) Process Modeling (HYSYS) Process Modeling (HYSYS) Process Modeling (HYSYS) Economic Evaluation Economic Evaluation Economic Evaluation Aspen PIMS Process Modeling (Aspen Plus) ----Operations Support Aspen PIMS Aspen PIMS Required Install Option Selection --- --- --- ------- --------Advanced Simulation Options ----Aspen Online Deployment ----- Aspen PIMS --- Exchanger Design and Rating Process Modeling (Aspen Plus) Process Modeling (HYSYS) ----Advanced Simulation Options Process Modeling (Aspen Plus) Process Modeling --Advanced Simulation Introduction for V7.

Product Name Release 2006.5 Aspen Polymers Plus™ Aspen Process Manual™ Aspen Process Tools™ Aspen Properties® Product Name V7.0 Aspen Polymers Aspen Process Manual™ Aspen Process Tools™ Aspen Properties® Aspen solubility modeler functionality Install Mapping (What to Install) (HYSYS) Process Modeling (Aspen Plus) Process Development (Server Installation only) Process Development Process Modeling (Aspen Plus) Process Development Required Install Option Selection Options ----- Advanced Modeling Options ----- Aspen RateSep™ Aspen RefSYS™ Aspen RefSYS Catcracker™ Aspen RefSYS Hydrocracker™ Aspen RefSYS Reformer™ Aspen Simulation Workbook™ Aspen Rate-Based Distillation Aspen HYSYS® Petroleum Refining Aspen HYSYS® CatCracker Aspen HYSYS® Hydrocracker Aspen HYSYS® Reformer Aspen Simulation Workbook™ Process Modeling (Aspen Plus) Process Modeling (HYSYS) Process Modeling (HYSYS) Process Modeling (HYSYS) Process Modeling (HYSYS) Operations Support Process Modeling (Aspen Plus) Process Modeling (HYSYS) --- Advanced Simulation Options Advanced Simulation Options Advanced Simulation Options Aspen Simulation Workbook Aspen Simulation Workbook Aspen Simulation Workbook ------Advanced Simulation Options Advanced Simulation Options --Aspen OTS Framework Aspen Split™ Aspen Tasc+™ Aspen Teams® Aspen Utilities Operations™ Aspen Utilities Planner™ Aspen Zyqad™ NEW Aspen Distillation Synthesis Aspen Shell & Tube Exchanger Aspen Shell & Tube Mechanical Aspen Utilities OnLine Optimizer Aspen Utilities Planner™ Aspen Basic Engineering Aspen OTS Framework Process Modeling (Aspen Plus) Exchanger Design And Rating Exchanger Design And Rating Process Modeling (Aspen Plus) Process Modeling (Aspen Plus) Aspen Basic Engineering Operations Support 8 Introduction for V7.1 .0 and V7.

Aspen Engineering Workflows 9 . then open .Aspen Engineering Workflows Process Engineering Console V7.edr) files.0 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues PE Console cannot start Aspen Simulation Workbook unless Aspen Simulation Workbook is installed on d: drive PE Console does not properly keep track of Heat Exchanger Design (. Workaround/Comment Install ASW on d: drive Open Heat Exchanger Design program from PE Console.edr file of interest from within Heat Exchanger Design.

Process Engineering Console V7.1
Coexistence Issues No known issues Workaround/Comment Not applicable

Installation Issues No known issues

Workaround/Comment Not applicable

General Usability Issues 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.

Workaround/Comment These can be downloaded and installed from the sites below: http://www.microsoft.com/downloads/de tails.aspx?familyid=59DAEBAA-BED44282-A28CB864D8BFA513&displaylang=en (Office 2007) http://www.microsoft.com/downloads/de tails.aspx?familyid=3C9A983A-AC144125-8BA0D36D67E0F4AD&displaylang=en (Office 2003)

Process Development Console V7.0 and V7.1
Coexistence Issues No known issues Workaround/Comment Not applicable

Installation Issues No known issues

Workaround/Comment Not applicable

General Usability Issues No known issues

Workaround/Comment Not applicable

10

Aspen Engineering Workflows

Integrated Sizing and Costing V7.0
Coexistence Issues No known issues Workaround/Comment Not applicable

Installation Issues No known issues

Workaround/Comment Not applicable

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

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

Integrated Sizing and Costing V7.1
Coexistence Issues No known issues Workaround/Comment Not applicable

Installation Issues No known issues

Workaround/Comment Not applicable

General Usability Issues No known issues

Workaround/Comment Not applicable

Aspen Engineering Workflows

11

12

Aspen Engineering Workflows

Workaround/Comment You should clear the Maintain link checkbox before deleting one of these blocks. Then on the Components | Specifications | Selection sheet.0 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues 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.Process Modeling (Aspen Plus) Aspen Plus V7. This happens because version 2006 did not contain the units for these parameters in the database. any Calculator blocks referencing it may be marked incomplete. select Tools | Clean Property Parameters. When loading a file from version 2006 which contains temperature-dependent parameters from the NIST databank. otherwise you may experience unpredictable effects. input is incomplete.5 and V7. Versions 2006.0 include these units and expect them to be specified. You should delete those blocks as well. To fix this problem. Process Modeling (Aspen Plus) 13 . click Review to retrieve the parameters from the database again. Select Clean property parameters placed on input forms and then click OK twice. When you delete a block.

Certain links within the help files link to other products' help. You will need to enable it again by checking the box for the desired version when you want to use ASW. or to viewlets. or any third-party COM Add-in) are installed in Microsoft Excel. ignore the message.1 | Aspen Simulation Workbook | Aspen Simulation Workbook Add-In Manager. For some users. Blocks and Streams named TOP and DATA do not work correctly in some situations.dll is 14 Process Modeling (Aspen Plus) . Click Start | Programs | Process Modeling V7. If you save your Aspen Plus simulation. these names are reserved and Aspen Plus will not allow you to assign them to streams and blocks. clear the boxes by all versions of Aspen Simulation Workbook. but does not open the form for the stream named TOP. when you close Aspen Plus after using an Excel Calculator block. It should not cause any problems except for increased memory usage. Workaround/Comment You can end these processes from the Task Manager. A localized version of msxml6r. you can disable the ASW add-in before running Aspen Plus when you are going to use Excel Calculators. and reopen it. and then click OK. or in the case of the viewlets. Installation Issues During the installation of Microsoft SQL Server Express 2005 SP2 on non-English versions of Windows XP SP3. click the links in the Doc DVD Browser to open this help directly. if you doubleclick a stream named TOP on the flowsheet. the Data Browser opens to the Streams folder. close it. you should rename the blocks and/or streams with these names on the flowsheet. For instance. a message appears. Aspen Plus V7.1 Coexistence Issues If any version of Aspen Simulation Workbook (ASW) is installed. the product whose help you are using is installed. In existing files which use these names.0. saying that the installation Workaround/Comment If no additional errors appear and the SQL Server installation completes successfully. then the Excel Calculator will work correctly once each Aspen Plus session. then Excel remains running after you use it with an Excel Calculator block. To prevent this from happening. You can end this Excel process from the Task Manager or leave it running.If any COM Add-ins (such as the one from Aspen Simulation Workbook. These links will not work unless the other product is installed. We are developing a new version of the Excel Calculator addin for the next release which will resolve this issue. Starting in version V7. both Aspen Plus and Excel remain running in the background. the Excel Calculator toolbar fails to appear the second and subsequent times you open an Excel Calculator block in Excel. To view this help from the Doc DVD. This prevents changing any of the connections of cells to Aspen Plus variables.

You can select the block in the Block Summary grid and When loading an Aspen Plus document (*. then double-click Services. This conflict exists within Microsoft SQL Server (2005 and 2008) and Windows XP SP3. if you use the Insert Block command in the context (rightclick) menu of a stream within a Hierarchy subflowsheet. and is described at: http://support. Locate Windows Internal Database(MICROSOFT##SSEE) and Stop the service. it is possible to install Aspen Properties Enterprise Database (APED) on this server. In some cases. installed with Windows XP SP3. the Tools | Conceptual Design | Azeotrope Search and Ternary Maps features do not work. if desired. or when there are Measurements.com/kb/958897 If you have enabled Windows Sharepoint Services 3.cannot update the file msxml6r. but in the original units. Instead. Aspen Plus crashes. do not use Insert Block within Hierarchy subflowsheets. Specify the value in the old units and then change units to verify the value.microsoft. Click Start | Settings | Control Panel.dll because it is protected by Windows. and use the Plot Wizard on the ternary results to generate the ternary map.0. and the Microsoft SQL Server 2005 Embedded Edition included in these products is running. Given the alreadysynced run. otherwise you may experience unpredictable effects. or change the units and value in the Data Browser. Save the run before syncing to EO to avoid this problem. You should delete those blocks as well. Use Tools | Analysis | Property | Ternary to generate ternary and azeotrope data. You can also disable this server during the installation to avoid installing APED on it. To avoid this problem. and SQL Server fails when trying to overwrite it with the English version. and thus Process Modeling (Aspen Plus) 15 . Then you can switch to EO and the sync will re-establish the correct set of variables and equations. General Usability Issues 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.0 or Windows Server Update Services 3. do not select MICROSOFT##SSEE. 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. but the localized version works. 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. This server is not suitable for APED and connections may fail without additional configuration.apw file) for a synced EquationOriented simulation. any Calculator blocks referencing it may be marked incomplete. 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. In any simulation with user subroutines. When offered the choice of different SQL Server instances to install on. When using the Block Summary grid to change specifications. Workaround/Comment You should clear the Maintain link checkbox before deleting one of these blocks. then double-click Administrative Tools. switch to Sequential Modular. When you delete a block. then reinitialize and save at this point.

0 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable The OLI Interface V7.is the wrong value. Workaround/Comment We plan to provide a patch to resolve these issues. Transfer. 16 Process Modeling (Aspen Plus) . The OLI Interface V7. or from Measurement blocks that are not placed inline in material streams to associated streams. click forms.1 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues The OLI models FraChem and Eflash4 may run into numerical problems and will not solve. The patch will be downloadable from the AspenTech Support web site when it is available. and Calculator blocks to associated streams. The options in the Tools | Options | Flowsheet tab which enable the display of connections will not show connections from Design Spec. to open the Data Browser to its This deficiency will be addressed in a future version.

Select Clean property parameters placed on input forms and then click OK twice. Workaround/Comment This happens because version 2006 did not contain the units for these parameters in the database. select Tools | Clean Property Parameters. but the localized version works.com/kb/958897 Process Modeling (Aspen Plus) 17 . ignore the message.dll because it is protected by Windows. Then on the Components | Specifications | Selection sheet.0 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues When loading a file from version 2006 which contains temperature-dependent parameters from the NIST databank. A localized version of msxml6r.microsoft.Aspen Properties V7. and is described at: http://support.dll is installed with Windows XP SP3. Workaround/Comment If no additional errors appear and the SQL Server installation completes successfully. This conflict exists within Microsoft SQL Server (2005 and 2008) and Windows XP SP3.0 include these units and expect them to be specified. Aspen Properties V7. click Review to retrieve the parameters from the database again.5 and V7. saying that the installation cannot update the file msxml6r. a message appears. To fix this problem.1 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues During the installation of Microsoft SQL Server Express 2005 SP2 on non-English versions of Windows XP SP3. input is incomplete. Versions 2006. and SQL Server fails when trying to overwrite it with the English version.

then double-click Administrative Tools. This server is not suitable for APED and connections may fail without additional configuration.If you have enabled Windows Sharepoint Services 3. When offered the choice of different SQL Server instances to install on. then double-click Services. General Usability Issues No known issues Workaround/Comment Not applicable 18 Process Modeling (Aspen Plus) . Click Start | Settings | Control Panel. do not select MICROSOFT##SSEE. You can also disable this server during the installation to avoid installing APED on it. Locate Windows Internal Database(MICROSOFT##SSEE) and Stop the service. it is possible to install Aspen Properties Enterprise Database (APED) on this server.0 or Windows Server Update Services 3.0. and the Microsoft SQL Server 2005 Embedded Edition included in these products is running.

dll using the following command: regsvr32 “C:\Program Files\AspenTech\AMSystem V7. Workaround/Comment Please check on the Aspen Custom Modeler section of the AspenTech support web site for a fix to this issue. Open a command prompt window and use the regsvr32 command to re-register this file. For example. Advanced Simulation Options (Aspen Plus) 19 . if you uninstalled 2006. the Aspen Reactions Toolkit might stop working.5 after installing V7. Workaround/Comment Locate the file ARTProc. going to the Help menu and selecting “Product support on the web”. you need to reregister ARTProc.Advanced Simulation Options (Aspen Plus) Aspen Custom Modeler V7. You can access this by starting Aspen Custom Modeler.0 Coexistence Issues If you have Aspen Custom Modeler V7.0 and a previous version of Aspen Custom Modeler installed and then uninstall one of these versions.dll in the AMSystem\bin folder of the version that is still installed.0\bin\ARTProc. This wizard does not work correctly and should not be used.0.dll” Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues The Aspen Custom Modeler Tools menu includes the item Custom Reactions Model Wizard.

the Properties dialog for the Plot form may stop working. For example: regsvr32 “C:\Program Files\AspenTech\AMSystem V7. For example: regsvr32 “C:\Windows\System32\VSFlex7L. and then uninstall one of these versions.1 and a previous version of Aspen Custom Modeler installed.1 Coexistence Issues If you have Aspen Custom Modeler V7.dll in the AMSystem\bin folder of the version that is still installed. and then uninstall one of these versions. For example: regsvr32 “C:\Program Files\Common Files\AspenTech Shared\ pfsplotv230. Estimation or Online Links may stop working or cause the message: “An unsupported operation was attempted”.1 and a previous version of Aspen Custom Modeler installed. Click on the Aspen Properties program in the Windows Taskbar to make Aspen Properties GUI the top window.ocx” Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues Model Export will not work if you are outputting to a file name or folder that contains multi-byte characters. and then uninstall one of these versions.ocx” in the “C:\Program Files\Common Files\AspenTech Shared” folder and use the regsvr32 command to re-register this file. Workaround/Comment Locate the file ARTProc.1 and a previous version of Aspen Custom Modeler installed.Aspen Custom Modeler V7. the Aspen Reactions Toolkit may stop working. 20 Advanced Simulation Options (Aspen Plus) .ocx” Locate the file “pfsplotv230. Workaround/Comment Export only to filenames and folder names consisting of ASCII characters.dll” If you have Aspen Custom Modeler V7. Open a command prompt window. Locate the file: “VSFlex7L. On Vista systems. If you have Aspen Custom Modeler V7. the Optimization. and use the regsvr32 command to re-register this file.ocx” in the C:\Windows\System32 folder and use the regsvr32 command to re-register this file.1\bin\ARTProc. This is usually only a problem if you are using a version of Windows configured for Asian languages such as Chinese or Japanese. if you Configure Physical Properties and choose “Edit using Aspen Properties” the Aspen Properties GUI may launch behind your current ACM window.

the Properties dialog for the Plot form may stop working. and then uninstall one of these versions.ocx” in the C:\Windows\System32 folder and use the regsvr32 command to re-register this file.1 and a previous version of Aspen Model Runner installed.0 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Aspen Model Runner V7.ocx” in the “C:\Program Files\Common Files\AspenTech Shared” folder and use the regsvr32 command to re-register this file. Estimation or Online Links may stop working or cause the message: “An unsupported operation was attempted”. For example: regsvr32 “C:\Program Files\Common Files\AspenTech Shared\ pfsplotv230.1 and a previous version of Aspen Model Runner installed. Workaround/Comment Locate the file: “VSFlex7L. and then uninstall one of these versions. If you have Aspen Model Runner V7.ocx” Locate the file “pfsplotv230.1 Coexistence Issues If you have Aspen Model Runner V7. the Optimization.ocx” Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Advanced Simulation Options (Aspen Plus) 21 . For example: regsvr32 “C:\Windows\System32\VSFlex7L.Aspen Model Runner V7.

When you export to dynamics. Workaround/Comment Please ignore these graphical objects. these objects are shown on the graphical flowsheet but they are not used by the dynamic simulation. set Coolers valid phases = Vapor-Liquid. the export will fail with a fatal error. USERACM reactions in Aspen Plus are not exported to Aspen Plus Dynamics. in Aspen Plus. for example 1e-5. the following Aspen Plus objects can be displayed graphically: design-specs.Aspen Plus Dynamics V7. 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. In Aspen Plus. 22 Advanced Simulation Options (Aspen Plus) . In Aspen Plus. and transfer blocks. the simulation will be over specified by 1. set the feed stream flow to a small value. on the Setup form Convergence tab. All other ACM exported models can be exported. The support for USERACM reactions will be restored as soon as possible.0. calculator blocks. This issue occurs if in Aspen Plus you have a MCompr model with the following conditions: • Coolers valid phases = Vapor-LiquidLiquid • 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.0 (formerly Aspen Dynamics) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues In V7. If.

The documentation for the Aspen Plus Dynamics Example Simulations is in the wrong location in the help contents.ocx” Advanced Simulation Options (Aspen Plus) 23 . the export will fail with a fatal error. If you have Aspen Plus Dynamics V7. and then uninstall one of these versions.ocx” in the “C:\Program Files\Common Files\AspenTech Shared” folder and use the regsvr32 command to re-register this file.1 and a previous version of Aspen Plus Dynamics installed. and use the regsvr32 command to re-register this file. the Properties dialog for the Plot form may stop working. For example: regsvr32 “C:\Program Files\AspenTech\AMSystem V7. 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.ocx” Locate the file “pfsplotv230. and then uninstall one of these versions.dll” If you have Aspen Plus Dynamics V7.ocx” in the C:\Windows\System32 folder and use the regsvr32 command to re-register this file. and then uninstall one of these versions. Workaround/Comment Locate the file ARTProc. Estimation or Online Links may stop working or cause the message: “An unsupported operation was attempted”.1 and a previous version of Aspen Plus Dynamics installed.dll in the AMSystem\bin folder of the version that is still installed. Change vendor type to one of the following: • MTL • GLITSCH • RASCHIG To find this help.1 and a previous version of Aspen Plus Dynamics installed.1 (formerly Aspen Dynamics) Coexistence Issues If you have Aspen Plus Dynamics V7. Open a command prompt window. Locate the file: “VSFlex7L.If. For example: regsvr32 “C:\Program Files\Common Files\AspenTech Shared\ pfsplotv230. look in the contents under “Using DMCplus Controllers” -> “Example of Using a DMCplus Controller” Aspen Plus Dynamics V7. For example: regsvr32 “C:\Windows\System32\VSFlex7L. the Aspen Reactions Toolkit may stop working. in Aspen Plus.1\bin\ARTProc. the Optimization.

Click on the Aspen Properties program in the Windows Taskbar to make Aspen Properties GUI the top window.Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues Model Export will not work if you are outputting to a file name or folder that contains multi-byte characters. Aspen Adsorption V7. This is usually only a problem if you are using a version of Windows configured for Asian languages such as Chinese or Japanese. if you Configure Physical Properties and choose “Edit using Aspen Properties” the Aspen Properties GUI may launch behind your current ACM window. On Vista systems.0 (formerly Aspen Adsim) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable 24 Advanced Simulation Options (Aspen Plus) . Workaround/Comment Export only to filenames and folder names consisting of ASCII characters.

Aspen Adsorption V7.ocx” in the C:\Windows\System32 folder and use the regsvr32 command to re-register this file.1 and a previous version of Aspen Adsorption installed.1 (formerly Aspen Adsim) Coexistence Issues If you have Aspen Adsorption V7. the Properties dialog for the Plot form may stop working.ocx” Locate the file “pfsplotv230.1 and a previous version of Aspen Adsorption installed. and then uninstall one of these versions. Workaround/Comment Click on the Aspen Properties program in the Windows Taskbar to make Aspen Properties GUI the top window. Advanced Simulation Options (Aspen Plus) 25 . Workaround/Comment Locate the file: “VSFlex7L. if you Configure Physical Properties and choose “Edit using Aspen Properties” the Aspen Properties GUI may launch behind your current Aspen Adsorption window. the Optimization. and then uninstall one of these versions. If you have Aspen Adsorption V7. For example: regsvr32 “C:\Program Files\Common Files\AspenTech Shared\ 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:\Windows\System32\VSFlex7L. Estimation or Online Links may stop working or cause the message: “An unsupported operation was attempted”.ocx” Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues On Vista systems.

Aspen Utilities Planner V7.0
Coexistence Issues No known issues Workaround/Comment Not applicable

Installation Issues No known issues

Workaround/Comment Not applicable

General Usability Issues No known issues

Workaround/Comment Not applicable

Aspen Utilities Planner V7.1
Coexistence Issues No known issues Workaround/Comment Not applicable

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

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

General Usability Issues No known issues

Workaround/Comment Not applicable

26

Advanced Simulation Options (Aspen Plus)

Process Modeling (HYSYS)

Aspen HYSYS V7.0
Coexistence Issues 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. Workaround/Comment 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. 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.

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.

Process Modeling (HYSYS)

27

Installation Issues Not applicable

Workaround/Comment Not applicable

General Usability Issues 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. 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. HYSYS will ignore the chemistry definitions in imported Aspen Properties bkp files. HYSYS with Aspen Properties: Electrolyte models involving light gases could give incorrect answers because Henry Constants are retrieved from incorrect databases. 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. 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. Analyzer and HXFlux will fail to see streams not connected to any EO blocks including the ones connected only to ACM blocks. HYSYS allows editing the Fluid Package for a case already synced to EO mode without switching to SM mode.

Workaround/Comment 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.

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

Create the fluid package in HYSYS with Chemistry.

Not Applicable.

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. Use the EO Variable grid to see the correct values associated with the feed stream.

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

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

28

Process Modeling (HYSYS)

Quick approximation used to compute Workaround/Comment Create an inlet and outlet port for the ACM model and equate all the outlet port variables to the inlet port variables.0 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues ACM models with no port definitions can be placed in Aspen HYSYS and solved in steady state. Aspen HYSYS V7. This will be fixed in the next release. If the variable is shown in red simply delete it and allow the solver to calculate it. Not Available.Reaction set with conversion reactions can not be attached to a Fluid package with Aspen Properties. Aspen HYSYS Dynamics V7. but they will fail in dynamic mode. A correction is available but it needs Process Modeling (HYSYS) 29 . 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. Workaround/Comment Open the view of the unit operation that owns the variable mentioned in the consistency error dialog. Use pressure drop spec instead of pressure drop correlation parameter spec if possible. Heater in EO with both pressure drop correlation parameter spec and temperature change spec will not be recalled correctly.1 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues A consistency error can be observed when loading and simulating a HYSYS XML case.

From the Start menu | Program Files | Aspentech | Process Modeling | Aspen HYSYS.0 Coexistence Issues Aspen Hydraulics 2006.5 installation folder.0.5 might not be fully functional in the presence of Aspen Hydraulics V7. Workaround/Comment A . Aspen HYSYS Dynamics V7.5. Workaround/Comment In order to run DBR PVT PRO in Vista. Contact AspenTech customer support for more information.NET configuration file called hysys. Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues DBR PVT PRO does not work under Windows Vista. This can be obtained from AspenTech Customer Support after the V7. Aspen Hydraulics V7. Aspen Hydraulics V7. In this case.0 release. further testing before it is released.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.0 might not work after uninstalling Aspen Hydraulics 2006. select 30 Process Modeling (HYSYS) .config should be installed in the Aspen HYSYS 2006. This component tries to write to a file in the Program Files folder which is not allowed in Vista. you need to run HYSYS as an administrator.1 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment No known issues Aspen HYSYS Upstream V7.0 needs to be registered again.exe. This coexistence problem will be fixed in the coming release.

and select Run as an administrator.config should be installed in the installation folder of HYSYS 2006.1 Workaround/Comment The . It was found that this component tries to write to a file under Program Files folder which is not allowed in Vista. You can also browse to HYSYS using windows explorer and select run as an administrator.e. Aspen HYSYS Upstream V7. Notice that it is NOT enough to log in as an administrator. Notice that it is NOT enough to log in as an administrator. There is a specific file for each of the previous HYSYS versions. Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues DBR PVT PRO does not work under Windows Vista. right-click. Process Modeling (HYSYS) 31 . i. The file can be obtained from Aspentech Customer Support.5 and V7.1 Coexistence Issues Previous versions of Aspen Hydraulics. You can also browse to HYSYS using Windows Explorer and select Run as an administrator. 2006.NET configuration file hysys. Workaround/Comment In order to run DBR PVT PRO in Vista you need to run HYSYS as an administrator.0 may not be fully functional in the presence of Aspen Hydraulics V7.0. From the Start menu | Program Files | Aspentech | Process Modeling | Aspen HYSYS select HYSYS and right click and select run as an administrator.5 or HYSYS V7.HYSYS.exe.

If you run a calibration in FCC and return to the simulation environment without pushing the calibration data. For most FCCs. You can unset the objective function by running a simulation for the hydrocracker or reformer. Temperature. the regenerator performance will be affected. and Composition specified for an external hydrogen makeup stream do not get passed to the hydrocracker environment. pressure. from any command window for the EO environment. 32 Process Modeling (HYSYS) . this affects only the sulfur curve. all other EO unit ops will not solve until the objective function has been unset. Workaround/Comment Open the case in v2006 and save it.0. Any FCC or case with an FCC created before v2006 will not recall properly in V7. you can type the command “set objective = none”. but the results are not reliable.0.0. For 2-stage regenerator units. Pressure.0. Make sure to save your calibration factor set and push your calibration data to the simulation before returning to the simulation environment. Alternatively.Aspen HYSYS Petroleum Refining V7. Open the case in v2006 and save it. The saved case should open fine in V7. and composition in the hydrocracker environment or connect the variables with a HYSYS spreadsheet. The saved case should open in V7. some values are reset incorrectly. though.0 (formerly Aspen RefSYS) Coexistence Issues No Known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues Any hydrocracker or reformer template or case with a hydrocracker or reformer created before v2006 will not open in V7. Manually enter the same temperature. The case may run. If you run a calibration in the reformer or hydrocracker.

User can then enter yield values. the change isn’t reflected in the PSR’s internal structures. the Assay Manager wizard allows deleting the assay. Macro-cut information can not be exported to ASW. make sure it is not referenced by a PSR. Stream cutter with reformer transition generates incorrect output composition. The problem will be fixed in V7.In the FCC calibration environment. Petroleum Shift Reactor (PSR) cannot run PIMS submodels in Vista Operating System. After the PSR is created. Using supplementary feeds in PSR creates some display issues on the Product Spec Page.1. the predictions will not run if the regenerator specs don’t match the regenerator specs from your simulation environment. Reaction set having conversion reactions can not be attached to a Fluid package with Aspen Properties If a HYSYS spreadsheet cell has an attachment as a composition of a stream having a reformer or hydrocracker component list. User needs to re-establish the link between stream composition and HYSYS spreadsheet. Not available. Not available. Not available. In many cases. Process Modeling (HYSYS) 33 . Specify the regenerator specs for prediction runs that match your simulation regenerator specs. PIMS assay can not be imported with Aspen Properties fluid package. First export Macro-cut information to a HYSYS spreadsheet and then export the HYSYS spreadsheet value to ASW. Not available. even though an assay is referenced by the PSR. It is solely a display issue. You may ignore the rows that correspond to the supplementary feeds on the product spec table. 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. liquid density can not be shifted with manipulator. Not available. Conversion reactors with reaction sets using components from reformer or hydrocracker component list cannot be solved. if the user changes the name of a product stream (by entering a different name after opening the stream’s properties page). Before you delete an assay. First enter distillation temperature and then it will create a space for yield. Manipulator can not take in yield values in composition view. In PSR. Avoid changing product stream’s name. the cell shows empty values.

Common Model Utility: On the Variables page.1.Aspen HYSYS Petroleum Refining V7. you can type the command “set objective = 34 Process Modeling (HYSYS) . Or from any command window for the EO environment. all other EO unit ops will not solve until the objective function has been unset. but the results are not reliable. the Product Specs and Product Properties tabs are merged. Ensure that the CME file is of the correct format by opening it in the CME Visual Executive before loading in HYSYS.1 and reload the case. HYSYS might close sometimes if in a Petroleum Shift Reactor or EOSubmodel. Open the case in v2006 and save it. You can unset the objective function by running a simulation for the hydrocracker or reformer.5 or later. If you run a calibration in the reformer or hydrocracker. Not available. Workaround/Comment On the property view page. a CME file with an incorrect format is loaded.1. Just save the case in V7.1 (formerly Aspen RefSYS) Coexistence Issues No Known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues Petroleum Shift Reactor: Some of the screen shots of the User Manual are not up to date. The HYSYS Description is an internal description of the variable and is not to be confused with the CME variable description. The saved case should open fine in v2006. The saved case should open fine in v2006. a unit op or a stream in a recalled case might issue a message that a particular correlation property is missing. The case may run. EOSubmodel: A case saved as XML file cannot be reloaded In rare scenarios. the HYSYS Description is different from CME variable description.5 or later. A new button is added to export smc/cme files from Petroleum Shift Reactor. Open the case in v2006 and save it. Any FCC or case with an FCC created before v2006 will not recall properly in V7. Any hydrocracker or reformer template or case with a hydrocracker or reformer created before v2006 will not open in V7.

For 2-stage regenerator units. For most FCCs. Process Modeling (HYSYS) 35 . Manually enter the same temperature. User needs to re-establish the link between stream composition and HYSYS spreadsheet. If you run a calibration in FCC and return to the simulation environment without pushing the calibration data. Temperature. though. and composition in the hydrocracker environment. the cell shows empty values. the regenerator performance will be affected.none”. some value get incorrectly reset. If a HYSYS spreadsheet cell has an attachment as a composition of a stream having a reformer or hydrocracker component list. this affects only the sulfur curve. In the FCC calibration environment. Specify the regenerator specs for prediction runs that match your simulation regenerator specs. Pressure and Composition specified for an external hydrogen makeup stream do not get passed to the hydrocracker environment. or connect the variables with a HYSYS spreadsheet. Make sure to save your calibration factor set and push your calibration data to simulation before returning to the simulation environment. the predictions will not run if the regenerator specs don’t match the regenerator specs from your simulation environment. pressure.

36 Process Modeling (HYSYS) .

Another option is to access the variables from the Aspen Simulation Data browser.0 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues Aspen Simulation Workbook Interface Copy/Paste functionality will not work with Materials of Construction input variables. Not available Exchanger Design and Rating 37 . Workaround/Comment Not available Always reselect the desired item in the list prior attempting a Copy/Paste to Aspen Simulation Workbook. Drag/Drop to Excel spreadsheet will not work for those List variables that are enclosed in Frames. 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.Exchanger Design and Rating All Exchanger Design and Rating Products V7.

Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues Aspen Simulation Workbook will only allow a single EDR file to be accessed. it is recommended that the version to be used be registered using the Version Control utility provided in the Startup menu. we recommend renaming the file so that there are multiple versions If users maintain multiple versions of the EDR programs on their machines and routinely switch between versions.All Exchanger Design and Rating Products V7. If users wish to use a different version of the EDR programs. 38 Exchanger Design and Rating . 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. There is no need to use the version control utility unless you attempt to run an earlier program version. This will require that you reregister the correct version of Aspen Properties using the registry fix utility found in the Startup menu. Workaround/Comment Input/Result files are not totally backward compatible. the installed version is registered. Switching back and forth between different versions of the EDR programs can cause program crashes unless the version being used is properly registered. All files should be forward compatible. the program will crash.1 Coexistence Issues 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. If you attempt to open a new file with an older program version. we recommend that the same version of Aspen Properties be used. Upon installation. If more than 1 is added and then one is deleted. Workaround/Comment Fix will be available in cumulative patch.

Aspen Air Cooled Exchanger V7. always place the cursor on another input field or move to another input form prior to running the program. or wall thickness.0 (formerly Aspen ACOL+) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues Tube OD.Aspen Air Cooled Exchanger V7.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. ID. For example. tube ID. if the user has 0. 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.75 inch. the calculation engine will not recognize the tube OD has been changed to 1 inch and will continue to use 0. Workaround/Comment After setting a new tube OD.1 (formerly Aspen ACOL+) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Exchanger Design and Rating 39 .

1 (formerly Aspen TASC+) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable 40 Exchanger Design and Rating .0 and V7.1 (formerly Aspen FiredHeater) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Aspen Shell & Tube Exchanger V7.0 and V7.Aspen Fired Heater V7.

1 (formerly Aspen TEAMS) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Aspen Plate Exchanger V7.1 (formerly Aspen Plate+) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Aspen HTFS Research Network V7.0 and V7.0 and V7.0 and V7.1 Coexistence Issues No known issues Workaround/Comment Not applicable Exchanger Design and Rating 41 .Aspen Shell & Tube Mechanical V7.

0 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable 42 Exchanger Design and Rating .0 and V7.1 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Plate Fin Exchanger V7.Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Aspen MUSE V7.

by looking at the diagrams of the exchanger and all its layer types and supplying missing data.1 PlateFin. and X-flow parameters.1 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues Importing MUSE files (. To export to Word. Some input items are not accessible in V7. Workaround/Comment You should always check an imported geometry. You can modify the Excel template to link to other output parameters that you select. The facility to export to Excel transfers only a limited number of parameters. This has been done deliberately for features from MUSE not reproduced in PlateFin for the first release. but sometimes manual editing of the imported case geometry is necessary. Make sure the MUI file has layer types defined before import. then copy into Word.Plate Fin Exchanger V7.MUI) is mostly straightforward. Examples are longitudinal conduction. These will be made available at the earliest opportunity. and export to Word is not yet available. use Export to Excel. Exchanger Design and Rating 43 .

44 Exchanger Design and Rating .

the Economic Evaluation Resiliency used to configure folders for the specific user account might not run.0 (formerly Aspen KBase) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues When running any Economic Evaluation product for the first time as a restricted user on Terminal Server. The values are saved to the file when initially specified but are being lost when re-opened or attached. A symptom of the resiliency not running is not having the ability to open an Economic Evaluation project. Workaround/Comment Projects should have less than 1000 COAs.exe once per restricted user to resolve the issue. 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. This issue will be addressed in V7. Run HKCURegistry. No workaround exists. Workaround/Comment There is a tool located in the X:\Program Files\AspenTech\Economic Evaluation V7.0 CP1.0\Program\Sys folder that will simulate resiliency. General Usability Issues The maximum Number of COAs is limited to 999 in a project. Economic Evaluation 45 .Economic Evaluation Aspen Capital Cost Estimator V7.

max. Aspen Capital Cost Estimator V7. errors during the first-run configuration or when using Workaround/Comment There is a tool located in the X:\Program Files\AspenTech\Economic Evaluation V7. A symptom of resiliency not running is not having the ability to open an Economic Evaluation project.1 (formerly Aspen KBase) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues When running any Economic Evaluation product for the first time as a restricted user on Terminal Server. for example RPM. Modifying the folder/file permissions so that the non-Administrator user has full access to these data files.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. Run HKCURegistry. 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. will resolve the issue. The issue seems to mainly affect fields that have values that need to be calculated based on other project settings. Validation is currently not present at the main category level of these specification forms. When some data files installed by the Economic Evaluation installation are edited by an Administrative user. When entering values here. 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. do not enter invalid data since that would cause errors to be reported during cost evaluation when the external index file is in use. the Economic Evaluation Resiliency used to configure folders for the specific user account may not run. and then a different non-Administrator user uses the same installation. Workaround is to manually type in the desired value.1\Program\Sys folder that will simulate resiliency. 46 Economic Evaluation . Workaround is to not use lower case letters in customized input units of measure.exe once per restricted user to resolve the issue. and default values to not appear in the properties window or as blue text. Manually make the appropriate conversion and specify the corresponding units in the specification form. Using lower case characters in a customized input unit of measure can cause minimum.

the drawing must be closed and re-opened. help topics do not exist at this time. General Usability Issues 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. No workaround. In some instances. Workaround is to not use lower case letters in customized input units of measure. The Filter drop-down on the main application GUI toolbar does not show the whole filter text. transferring large sets (Usually more than 30 items) of equipment from Aspen Capital Cost Estimator to Aspen Basic Engineering will fail. Workaround/Comment The values are saved to the file when initially specified but are being lost when re-opened or attached. refer to the User Guide documentation for help. the equipment symbol disappears but a gray shadow remains in its place. No workaround exists. Pressing the Help button on Spreadsheet Equipment forms generates an error that it cannot find the help file. In order to refresh the drawing and remove the shadows. 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. 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. We have not had any instances of this when the client software is run on XP. Escalating to full administrator permissions allows you to modify this file. Using lower case characters in a customized input unit of measure can cause minimum. max. Use English standard numeric formatting when using this link. when an equipment symbol is placed in an area which it does not belong. Manually make the appropriate conversion and specify the corresponding units in the specification form. There is no refresh option available in the Basic Engineering drawing editor. In Vista/Windows Server 2008. The issue seems to mainly affect fields that have values that need calculated based on other project settings. and default values to not appear in the properties window or as blue text. On Vista. 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. There is no work around.xls). Economic Evaluation 47 . 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. users cannot edit the datafile for User Customized Form Attributes (UserAttributesCust.… Validation is currently not present at the main category level of these specification forms. for example RPM.the edited data files can occur. Transfer items in batches. however the filter can still work properly in all other respects.

Either delete the extraneous components after the paste or use copy and delete rather than cut. 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. No workaround exists. The user can exit the Symbol to resolve the issue. No workaround exists. No workaround needed. The first task (this is required) when creating any Plot plan drawing is to place the drawing scale. 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 original data will be preserved when the spreadsheet view is saved via an Apply or OK button click. Workaround/Comment No workaround exists. Components reappear in spreadsheet when pasted. especially within the same report group. even if it’s to the default value to have the scale properly initialize the drawing. Pasting a selection into a spreadsheet view will populate fields that are readonly if accessed individually.0 General Usability Issues Transfer of plot plan results back to Aspen Capital Cost Estimator (aka Kbase) might be slow. The user must currently modify the scale.0. 48 Economic Evaluation . This behavior gives the user the false impression that the fields will affect costing results. No workaround exists for this item. Can not select multiple rows/columns in spreadsheet view while holding the CTRL key. issue will be addressed in Cumulative Patch 1 of Aspen Basic Engineering (formerly Zyqad) 7. Clicking on a field in the spreadsheet view that contains a default value may cause the number of significant digits to change. Plot Plan Processor feature V7. No workaround exists. Duplicate Area names can be created if renamed within the Area Spreadsheet View. Cutting components in a spreadsheet view does not work.Area sizes do not display correctly if the drawing scale is not adjusted but simply placed or not placed at all.

No workaround. Exclusion zone dimensions and equipment footprint dimensions can be changed in Capital Cost Estimator (equipment forms) or Basic Engineering (explorer) only. EML equipment items. UCL. Additional missing components that have not been added to plot plan functionality include substations. UCL. In addition. and Piperacks cannot be transferred to plot plan processor. No workaround exists.0 CP1. equipment plan size. Cost Known. headers. Equipment items listed in the drawing editor stockpile are not filtered by area. no elevation view of open steel structures and pipe racks is available. and EML items will be included in future releases of the 2 (BE and CCE) products. It functions as designed. There is no ability to place equipment at different structure levels graphically. All areas and equipment items are located in the plotplan tab. the vertical location of equipment is indicated in Capital Cost Estimator (equipment forms) or Basic Engineering (explorer) only. No workaround. There is no ability to generate area drawings or to copy drawings or parts of a drawing to another sheet. No workaround exists. and firewater systems. 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. a piperack symbol from the left pane can be placed on the plot plan drawing. Future releases will transfer piperack layout information back to the CCE project. In order to refresh the drawing and remove the shadows. the drawing must be closed and re-opened. However. No workaround.Cost Known. All equipment in a project is placed in a single sheet. In some instances. No workaround. User can change the interconnected piping length (calculated from plot plan) but cannot change near-equipment length. To be addressed in future releases. 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. This to be addressed in Basic Engineering V7. In order to expedite equipment placement. the equipment symbol disappears but a gray shadow remains in its place. and symbols for equipment and symbols for areas may not be changed in the plot plan. plant bulk piping. when an equipment symbol is placed in an area where it does not belong. equipment ID tags specific to area designations can be used to expedite item/area associations. There is no refresh option available in the Basic Engineering Drawing Editor. Installation Issues No known issues Workaround/Comment Not applicable Economic Evaluation 49 . for piperacks. Exclusion zones around equipment.

especially within the same report group.General Usability Issues No known issues Workaround/Comment Not applicable Plot Plan Processor feature V7. No workaround exists.1 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Spreadsheet Data Entry feature V7. No workaround exists for this item. No workaround exists. Duplicate Area names can be created if they are renamed within the Area Spreadsheet View. The original data will be preserved when the spreadsheet view is saved by clicking the Apply or OK buttons. Components reappear in spreadsheet when pasted.0 General Usability Issues Clicking a field in the spreadsheet view that contains a default value can cause the number of significant digits to change. Users should not use duplicate area names. Cutting components in a spreadsheet view does not work. This behavior gives the user the false impression that the fields will affect costing results. Workaround/Comment No workaround needed. No workaround exists. Duplicate Area names will cause issues with evaluation and reporting. 50 Economic Evaluation . Cannot select multiple rows/columns in spreadsheet view while holding the CTRL key. Pasting a selection into a spreadsheet view will populate fields that are readonly if accessed individually. Either delete the extraneous components after the paste or use copy and delete rather than cut.

0\Program\Sys folder that will simulate resiliency.0 (formerly Aspen Icarus Project Manager) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues When running any Economic Evaluation product for the first time as a restricted user on Terminal Server. A symptom of resiliency not running is not having the ability to open an Economic Evaluation project. Run HKCURegistry.1 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Aspen In-Plant Cost Estimator V7.exe once per restricted user to resolve the issue. the Economic Evaluation Resiliency used to configure folders for the specific user account might not run.Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Spreadsheet Data Entry feature V7. Economic Evaluation 51 . Workaround/Comment There is a tool located in the X:\Program Files\AspenTech\Economic Evaluation V7.

General Usability Issues The maximum Number of COAs is limited to 999 in a project. will resolve the 52 Economic Evaluation .0 CP1. Run HKCURegistry. 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. Workaround is to not use lower case letters in customized input units of measure. for example.1 (formerly Aspen Icarus Project Manager) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues When running any Economic Evaluation product for the first time as a restricted user on Terminal Server. 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.exe once per restricted user to resolve the issue. 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. Aspen In-Plant Cost Estimator V7. Using lower case characters in a customized input unit of measure can cause minimum. Manually make the appropriate conversion and specify the corresponding units in the specification form. the Economic Evaluation Resiliency used to configure folders for the specific user account may not run. RPM. and default values to not appear in the properties window or as blue text. Validation is currently not present at the main category level of these specification forms. Workaround/Comment Projects should have less than 1000 COAs. max. and Workaround/Comment There is a tool located in the X:\Program Files\AspenTech\Economic Evaluation V7. Modifying the folder/file permissions so that the non-Administrator user has full access to these data files. When entering values here. This issue will be addressed in V7. The issue seems to mainly affect fields that have values that need to be calculated based on other project settings. do not enter invalid data since that causes errors to be reported during cost evaluation when the external index file is in use.1\Program\Sys folder that will simulate resiliency.

Workaround/Comment 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. To solve this problem.then a different non-Administrator user uses the same installation. the VB automation client must call the latest installed version of HYSYS. Therefore. Workaround/Comment Manually make the appropriate conversion and specify the corresponding units in the specification form.0 | Aspen HYSYS | Restore File Associations. Aspen Process Economic Analyzer V7. If this does not solve the problem follow the registration/unregistration procedure described in the following known issue. you must make sure that the latest version of HYSYS is the active Automation Server.0 (formerly Aspen Icarus Process Evaluation) Coexistence Issues When called from VB clients. issue. To do so you should run Restore File Association from Program Files | AspenTech | Process Modeling V7. Economic Evaluation 53 . This problem can affect the integration of HYSYS with Aspen Process Economic Analyzer and Aspen Exchanger Design and Rating. General Usability Issues 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. Contact AspenTech Customer Support for more details. older versions of HYSYS fail to run as automation servers in the presence of newer HYSYS versions installed on the same machine. errors during the first-run configuration or when using the edited data files can occur.

Manually make the appropriate conversion and specify the corresponding Importing a vertical flat bottom storage tank from one project to another where 54 Economic Evaluation . Workaround/Comment Use the Aspen Plus . This allows the EconE products to configure properly. This can result in requests for source media or crashes the first time an evaluation is done for each project. 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.xml file (as opposed to the .exe /unregserver and then hysys. an error will occur when trying to run the Aspen Process Economic Analyzer link with MUSE. the EconE software will not configure properly. A symptom of resiliency not running is not having the ability to open an Economic Evaluation project.0. the Economic Evaluation Resiliency used to configure folders for the specific user account might not run. Workaround/Comment It is highly recommended the EconE products are run at least once from the Start Menu before they are accessed through the PE Console. In V7. HYSYS 2006.5 versions of IPE and MUSE.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. e. The .e. There is a tool located in the X:\Program Files\AspenTech\Economic Evaluation V7. Loading from the . This does not apply to users who did the installation. non Administrator Accounts that did not install the software).0. Installation Issues In Restricted User Accounts (i.rep file) when manually loading the data into Process Economic Analyzer. This will be resolved in the CP1 of Aspen Process Economic Analyzer. go to the directory where the current active HYSYS automation server is installed.g. Run the following command: hysys. HYSYS V7.5.exe /unregserver • Using a command window. go to the directory where the last version of HYSYS is installed.rep does not contain the latest information.0\Program\Sys folder that will simulate resiliency. Run the following command: hysys.rep file will not work in the V7. When running any Economic Evaluation product for the first time as a restricted user on Terminal Server. e. General Usability Issues Loading an Aspen Plus simulation into Process Economic Analyzer (aka IPE) using the . 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. Use the 2006.exe /regserver.g. Run HKCURegistry.exe once per restricted user to resolve the issue.xml file is the preferred method as it is up to date with the latest Aspen Plus features and enhancements.0 release.

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.1 (formerly Aspen Icarus Process Evaluation) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues When running any Economic Evaluation product for the first time as a restricted user on Terminal Server.1\Program\Sys folder that will simulate resiliency. Modifying the folder/file permissions so that the non-Administrator user has full access to these data files.exe once per restricted user to resolve the issue. When some data files installed by the Economic Evaluation installation are edited by an Administrative user. Economic Evaluation 55 . Workaround/Comment There is a tool located in the X:\Program Files\AspenTech\Economic Evaluation V7. The issue seems to mainly affect fields that have values that need to be calculated based on other project settings. for example RPM. max. Workaround is to not use lower case letters in customized input units of measure. the Economic Evaluation Resiliency used to configure folders for the specific user account may not run. Run HKCURegistry. will resolve the issue. errors during the first-run configuration or when using the edited data files can occur. and then a different non-Administrator user uses the same installation. Aspen Process Economic Analyzer V7. and default values to not appear in the properties window or as blue text. Using lower case characters in a customized input unit of measure can cause minimum. A symptom of resiliency not running is not having the ability to open an Economic Evaluation project.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. 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. units in the specification form.

Run the following command: hysys. Run the following command: hysys. No work-around.exe /regserver.0 and later releases. 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. This is not a defect. Contact Aspentech Customer Support for more details. e. The . HYSYS 2006.rep file) when manually loading the data into Process Economic Analyzer.rep does not contain the latest information. Loading an Aspen Plus simulation into Process Economic Analyzer (aka IPE) using the .g. To do so you should run Restore File Association from Program Files | Aspentech | Process Modeling V7.xml file is the preferred method as it is up to date with the latest Aspen Plus features and enhancements.exe /unregserver and then hysys. Use the Aspen Plus . and a warning is generated that “Tray type could not be determined” when a tower is sized.1 | Aspen HYSYS | Restore File Associations. The tray type specified on the equipment form is not used. Recall that when installing HYSYS the latest version is NOT the active automation server by default.5. If this does not solve the problem follow the registration/unregistration procedure described in the known issue below.exe /unregserver Using a command window go to the directory where the last version of HYSYS is installed. HYSYS V7.rep file will not work in version V7. To solve this problem you must make sure that the latest version of HYSYS is the active Automation Server. Workaround/Comment 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.g. Therefore the VB automation client must call the latest installed version of HYSYS.xml file (as opposed to the .General Usability Issues 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. e. Loading from the . This problem can affect the integration of HYSYS with Aspen Process Economic Analyzer and Aspen Exchanger Design and Rating. 56 Economic Evaluation .0. 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.

If no error is reported the evaluation is ok. the link will fail. Example of this is when an equipment item is evaluated that has an error in the evaluation. refer to the User Guide documentation for help. Clicking on a field in the spreadsheet view that contains a default value may cause the number of significant digits to change.Negative values for stream data (IE Flows or properties) cause errors when using the Map Stream to Lines features. Use English standard numeric formatting when using this link. When using the Aspen Shell and Tube Mech program for heat exchanger design with the OS German standard numeric formatting in use. No workaround exists. if other equipment items are evaluated with no errors. The Filter drop-down on the main application GUI toolbar does not show the whole filter text. No workaround exists for this item. This behavior gives the user the false impression that the fields will affect costing results. Either delete the extraneous components after the paste or use copy and delete rather than cut. Components reappear in spreadsheet when pasted. especially within the same report group. Doing this will cause issues with evaluation and reporting due to areas having the same name. Pressing the Help button on Spreadsheet Equipment forms generates an error that it cannot find the help file. Users should take care as to not use duplicate area names. Pasting a selection into a spreadsheet view will populate fields that are readonly if accessed individually. the status bar will still indicate the failed state. Duplicate Area names can be created if renamed within the Area Spreadsheet View Do not use the Map Streams to Lines features on these cases. No workaround exists. help topics do not exist at this time. Cutting components in a spreadsheet view does not work. The project cache still exists after closing the simulation. The original data will be preserved when the spreadsheet view is saved via an Apply or OK button click. There is no work-around. The status bar will indicate the evaluation failed which is expected. however the filter can still work properly in all other respects. The workaround is to delete the folder after closing the simulation. Economic Evaluation 57 . However. No workaround needed. Can not select multiple rows/columns in spreadsheet view while holding the CTRL key. No workaround. No change of status is indicated when evaluating single equipment items. The equipment grid can be used to review specific evaluation errors. No workaround exists. This is not a problem unless there are disk space limitations on the PC. This is most often seen with PROII.

For example. 58 Economic Evaluation . The workaround is to delete the folder after closing the simulation. 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. However. This is not a problem unless there are disk space limitations on the PC. which is expected. If no error is reported. the status bar indicates the evaluation failed. the evaluation is ok. if other equipment items are evaluated with no errors.0 (available in Aspen Plus and Aspen HYSYS) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No change of status is indicated when evaluating single equipment items.The Economic Evaluation project is not stored with the Aspen Plus project in some instances. Mainly change the option back to use the internal spreadsheet reports if desired. when an equipment item is evaluated that has an error in the evaluation. Integrated Sizing and Costing feature V7. HYSYS sample projects fail when using the Economic Evaluation features on Vista. Capture the Economic Evaluation project when the Aspen Plus project is open and store it with your Aspen Plus project manually. the status bar will still indicate the failed state. Copy the samples to My Documents. The project cache still exists after closing the simulation. Workaround/Comment The equipment grid can be used to review specific evaluation errors.

Integrated Sizing and Costing feature V7.1 (available in Aspen Plus and Aspen HYSYS) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Economic Evaluation 59 .

60 Economic Evaluation .

Workaround/Comment Improvements to this feature will be addressed in successive Aspen Energy Analyzer releases. networks that contain complex process stream splitters are not correctly transferred.Energy and Flare Analysis Aspen Energy Analyzer V7.1 (formerly Aspen HX-Net) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues Workaround/Comment Energy and Flare Analysis 61 . Aspen Energy Analyzer V7.0 (formerly Aspen HX-Net) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues In the new feature that allows the transfer of a Heat Exchanger Network from an Excel table fix format to Aspen HX-Net.

The process hangs waiting for Connect to Engine DB to appear.0 (formerly Aspen FLARENET) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues Automation Interface: Import/Export of a Flare System Analyzer case might not work if called from a VBA application through an automation call.1 (formerly Aspen FLARENET) Coexistence Issues No known issues Workaround/Comment Not applicable 62 Energy and Flare Analysis . tick off the “Save as Default Connection” and then click OK to continue. Aspen Flare System Analyzer V7.No known issues Not applicable General Usability Issues Data Extraction from Aspen Plus stops in Windows Vista or Windows Server 2008. Workaround/Comment The user has to allow an appropriate amount of “sleep” before opening the Flare System Analyzer case in the automation code. When the new Connect to Engine DB window appears. An example VBA code to do this will be posted on the customer support website. Aspen Flare System Analyzer V7. Workaround/Comment Go to Task Manager and click on the "Connect to Engine" application. This allows for Flare System Analyzer to initialize properly.

1 (formerly Aspen COMThermo) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Energy and Flare Analysis 63 .0 and V7. A VBA example code will be posted in Customer support website after the V7. Aspen HYSYS Thermodynamics COM Interface V7. 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.Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues 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. Workaround/Comment The workaround for this problem is to wait for a few seconds before calling the “Openmodel’ of the Application. This is because the VBA code may call the “OpenModel” method of the Application interface before Flare System Analyzer is completely initialized.1 release.

64 Energy and Flare Analysis .

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 Aspen Remote Simulation Service allocates a single desktop heap which is shared among all the cases it opens. See Microsoft Knowledge Base articles 126962 and 184802.0 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues Unexpected simulation failures due to exhaustion of Windows desktop heap. To ensure the largest number of simulations can be run before encountering the desktop heap limitation. Workaround/Comment This behavior can be observed when an Aspen Simulation Workbook is configured to use the Aspen Remote Simulation Service. The number of cases that the Remote Aspen Simulation Workbook 65 .Aspen Simulation Workbook Aspen Simulation Workbook V7.

dll) can inadvertently become unregistered on your system. The heap consumption can only be determined by experiment (download the Desktop Heap Monitor Version 8. Aspen Simulation Workbook V7. and then uninstall either of them. then a shared component (cxsinteropcomv22. Workaround/Comment To fix the problem. This will open a command prompt window. type regsvr32 “[pathToFile]” where you replace “[pathToFile]” with the path to the “CxsInteropComV22. This will cause a “Failed to connect to simulation” error to occur when you try to connect to simulations.0 and V7. 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. or just one Aspen Custom Modeler case. • In the command prompt window. You can do this by: • On your PC go to ‘Start Button’ -> ‘All Programs’ -> ‘Accessories’ -> ‘Command Prompt’.1 installed. The default location is “C:\Program Files\Common Files\AspenTech 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.dll” file on your computer. you need to reregister the file on your PC. A conservative guideline would be to restrict use of a single Remote Simulation Service to 3 or 4 HYSYS and Aspen Plus cases.1 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues If you have both V7.1 tool from Microsoft to help you inspect the desktop heap usage).

click the ‘Enter’ key. After that.Shared\CxsInteropComV22.dll”.1 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Aspen Simulation Workbook 67 . General Usability Issues No known issues Workaround/Comment Not applicable Aspen OOMF V7. • 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.0 and V7. Note – You need to include the quotation marks around the [pathToFile] if there are any spaces in the path.

68 Aspen Simulation Workbook .

Process Development Aspen Batch Process Developer V7. Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues When a React operation uses an Aspen Plus Dynamics Kinetic reactor model. causing an error when a new Unit procedure is added.0. Workaround/Comment Run a “repair” of the Aspen Batch Process Developer installation. it will unregister a file used by Aspen Batch Process Developer V7. Process Development 69 . Workaround/Comment Close the Aspen Plus Dynamics window after the Aspen Batch Process Developer simulation is complete.5 is uninstalled.0 (formerly Aspen Batch Plus) Coexistence Issues If Batch Plus 2006. the Aspen Plus Dynamics window is displayed during the Aspen Batch Process Developer simulation.

1 (formerly Aspen Batch Plus) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues Aspen Properties will not open after uninstalling Aspen Batch Process Developer. This will perform any necessary initialization and show any errors. The BatchFrac model will be removed altogether in V8. By default. you should start the Aspen Properties User Interface. General Usability Issues The BatchFrac model does not have complete data validation in the Operations UI. You can also search for the example projects in Windows Explorer and then open the containing folder. Workaround/Comment Run the “Aspen Properties Registry Fix Utility”. 70 Process Development . 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). If desired.Aspen Batch Process Developer V7. the example projects are installed to C:\Documents and Settings\All Users. copy these files to a different folder.1 but care must be taken in entering data. Workaround/Comment The BatchFrac model data loading and saving works properly in V7.0. Change your folder view options to make system files visible. Depending on your Windows operating system and security settings these files might not be visible.

0 and V7.1 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Process Development 71 .Solubility Modeling V7.

72 Process Development .

0 (formerly Aspen BatchSep) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues This issue affects simulations that use the BatchSep unit operation model and that were created in Aspen Plus 2006. Save the simulation.0. Advanced Modeling Options (Process Development) 73 . Load the simulation in to Aspen Plus V7. values specified in operating steps for the following parameters will revert to their default: • Reflux Ratio • Condenser vapor • Controller set point • Controller output Workaround/Comment Open the simulation in Aspen Plus 2006. Review the specifications for the operating steps and re-enter values for parameters that are incorrect.5 CP2 or earlier.5 and make a note of the values for the affected parameters that are specified in each operating step.0. When these simulations are opened in Aspen Plus V7.Advanced Modeling Options (Process Development) Aspen Batch Distillation V7.

Aspen Batch Distillation V7.1 (formerly Aspen BatchSep) Coexistence Issues If you have Aspen Batch Distillation V7.ocx” Locate the file “pfsplotv230.1 and a previous version of Aspen Batch Distillation installed. For example: regsvr32 “C:\Windows\System32\VSFlex7L. and use the regsvr32 command to re-register this file.1 and a previous version of Aspen Batch Distillation installed. Open a command prompt window. and then uninstall one of these versions. and then uninstall one of these versions.1 and a previous version of Aspen Batch Distillation installed. you may not be able to modify the properties of a displayed plot. Locate the file: “VSFlex7L. Workaround/Comment Locate the file ARTProc. and then uninstall one of these versions. the forms for configuring reactions stop working.ocx” Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable 74 Advanced Modeling Options (Process Development) . For example: regsvr32 “C:\Program Files\Common Files\AspenTech Shared\ pfsplotv230.ocx” in the “C:\Program Files\Common Files\AspenTech Shared” folder and use the regsvr32 command to re-register this file. the Optimization item under the Tools menu item may stop working or cause the message: “An unsupported operation was attempted”. For example: regsvr32 “C:\Program Files\AspenTech\AMSystem V7.dll in the AMSystem\bin folder of the version that is still installed.1\bin\ARTProc.ocx” in the C:\Windows\System32 folder and use the regsvr32 command to re-register this file. If you have Aspen Batch Distillation V7.dll” If you have Aspen Batch Distillation V7.

Workaround/Comment Reinstall Aspen Reaction Modeler using the “Repair” option. Select PATH under either User variables or System variables. and then uninstall one of these versions. For these cases the fit will fail. To the end of the value for PATH. and one or more experiments have valid-phases set to Vapor-Liquid. Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Advanced Modeling Options (Process Development) 75 . add the full path to this folder.Aspen Reaction Modeler V7. go to Control Panel and select System. 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. Aspen Reaction Modeler will not work. Workaround/Comment Add the folder Program Files\AspenTech\APrSystem V7. Click Environment Variables.1 Coexistence Issues If you have Aspen Reaction Modeler V7.0 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues This issue affects cases where the Property calculation option is set to Simple.1 and a previous version of Aspen Reaction Modeler installed.0\Engine\Xeq Aspen Reaction Modeler V7.0\Engine\Xeq to your system path. For example: • C:\Program Files\AspenTech\APrSystem V7. Select the Advanced tab. To do this.

Workaround/Comment Locate the file: “VSFlex7L.ocx” in the “C:\Program Files\Common Files\AspenTech Shared” folder and use the regsvr32 command to re-register this file. Estimation or Online Links may stop working or cause the message: “An unsupported operation was attempted”. the Properties dialog for the Plot form may stop working.Aspen Chromatography V7. if you Configure Physical Properties and choose “Edit using Aspen Properties” the Aspen Properties GUI may launch behind your current Aspen Chromatography window. 76 Advanced Modeling Options (Process Development) .1 Coexistence Issues If you have Aspen Chromatography V7. Workaround/Comment Click on the Aspen Properties program in the Windows Taskbar to make Aspen Properties GUI the top window.ocx” in the C:\Windows\System32 folder and use the regsvr32 command to re-register this file. For example: regsvr32 “C:\Program Files\Common Files\AspenTech Shared\ pfsplotv230. For example: regsvr32 “C:\Windows\System32\VSFlex7L.1 and a previous version of Aspen Chromatography installed.1 and a previous version of Aspen Chromatography installed.ocx” Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues On Vista systems. and then uninstall one of these versions. If you have Aspen Chromatography V7.0 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Aspen Chromatography V7.ocx” Locate the file “pfsplotv230. the Optimization. and then uninstall one of these versions.

Aspen Process Tools V7.0 and V7.1 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Advanced Modeling Options (Process Development) 77 .

78 Advanced Modeling Options (Process Development) .

1 \Manual).1 Aspen Process Manual V7. C:\Program Files\AspenTech\Aspen Process Manual V7.0 \Manual) Workaround/Comment On the Administration page.1 Coexistence Issues If you have previously installed an earlier version of Aspen Process Manual. Aspen Process Manual V7. Click on Update document server settings. change the Search path for document files setting (the default would be C:\Program Files\AspenTech\Aspen Process Manual V7. then the search path for document files may point to the previous document files installation (for example.Aspen Process Manual V7.0 and V7. and Reindex documents to index the files at the correct location.1 79 .0 and V7.0 Coexistence Issues No Known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Aspen Process Manual V7.

0 and V7.1 .Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable 80 Aspen Process Manual V7.

1 Aspen Basic Engineering V7. Workaround/Comment Download and install Cumulative Patch 1 from the AspenTech Support Website.Basic Engineering V7.0 (formerly Aspen Zyqad) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues Aspen Basic Engineering V7.1 81 .1 (formerly Aspen Zyqad) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable Basic Engineering V7.0 requires Cumulative Patch 1 for use. Aspen Basic Engineering V7.0 and V7.0 and V7.

Excel Datasheet Editor: Annotation & Mark up disappear when click the same field adding annotation or mark up Excel Datasheet Editor: If an infinite equipment list is saved from the datasheet editor.error pops up when entering data on ID\TT column: “Cycles in the demons or application triggers exceeded the threshold. Explorer: <F-XXX IssueRecord> lock error message shows up when user Use Datasheet/pack to remove empty rows (CQ00352023) Use an equipment datasheet to change the value (CQ00338202) Opens the datasheets but doesn't save them (CQ00333462) Use the Open/Submitted menu option instead (CQ00353139) Lock errors can occur when submitting the same document twice (CQ00353136) 82 Basic Engineering V7.0 and V7. the footer does not appear in the correct row. Open this from Tools/Macro/Security… Only occurs if you edit annotation by clicking the same field without first clicking away (CQ00351965) Excel Datasheet Editor: Excel datasheets won’t open. 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) Values entered directly on the datasheet are not affected. Excel Datasheet Editor: If there are insufficient object to fill the last page. It is supposed to be painted in grey background (CQ00321677) You should check “Trust access to Visual Basic Project” on the Trusted Publishers tab of the Security dialogue. Bridge: When click the enabled box in link list the enabled state can not be changed Drawing Editor: White-Out of the Tool Bar in Drawing Editor Workaround/Comment Only occurs after reloading the workspace multiple times (CQ00334425) The workaround is to open the link and change enabled on the dialog (CQ00320926) That toolbar has only two buttons.There is no indication when the field can not display the value completely Excel Datasheet Editor: Filter datasheet and add a new object on continuous list will add some empty rows Excel Datasheet Editor: AZ Equipment list vessel .1 . The format can be changed in the usual way (CQ00350851) We are investigating how to fill the final page of an infinite equipment list with empty rows for printing. Excel does not.” Explorer : Batch save of multiple datasheets Explorer: Double-clicking on submitted PPID opens the current version. Excel Datasheet Editor: . (CQ00334658) Excel Datasheet Editor: The Excel Datasheet displays zero decimal places (by default). Only imported values by default do not show any decimal places. and then opened for printing in regular Excel.General Usability Issues Admin tool: Crash happened when user modified privileges several times. thus the white space isn't hiding anything. (CQ00331615) Workbench displayed >> to show the value has been truncated.

Creates a view file during publish. IDWF: folder name for issued diagrams does not include issue reason Estimation Interface: Some data are not copied for following objects: • CentrifugalCompressor • ShellTubeHeatExchanger • Fan • Fire Heater • Reciprocating Compressor PackedColumn Simulation Interface : Expanders and valves are missing in the equipment tab in the simulation importer Simulation Interface : errors when importing results for Aspen Plus Radfrac Migration: A workspace created in version 2006. This problem will become irrelevant in the next release when the Excel Datasheet functionality is Basic Engineering V7. TEF: Cannot Publish Datasheets TEF only problem. 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 Plot Plan : Area Drawing Length and Width are reversed on Drawing Plot Plan : Users must set the Scale in order for Areas to work (CQ00348026) Most data are transferred. Out of the box Datasheets: Some formatting errors (mostly overlapping sections) and for a few fields unable to change units of measurement.5 or earlier cannot be opened if a datasheet has a name exceeding 255 characters.1.1) (CQ00354195) These will be corrected and included in a cumulative patch.resubmits a datasheet within some specific situation.0 CP1. The fix will also be included in CP2 (for V7. Not possible to copy data from these simulation objects (CQ00353356) Stage results are still imported (CQ00351199) Contact AspenTech support for an emergency patch which can be applied to V7.1 83 . or version 7.0 and V7.0) and CP1 (for V7. Workaround: Create a file:C:\NoViewFile.

e.Vista Only : the title of Open Workspace cannot be seen clearly complete. 84 Basic Engineering V7.0 and V7.g. color and transparency. This may depend on your Vista desktop preferences.1 .

or Aspen Exchanger Design and Rating (HTFS+) are installed. it also limits the number of such applications that can be loaded. Aspen Custom Modeler. Aspen Online Deployment will use the default version. Workaround/Comment The impact of desktop heap exhaustion depends on whether the online applications are configured to use a remote solver.Operations Support Aspen Online Deployment V7. Aspen Remote Simulation Service).. Workaround/Comment To explicitly control which version of a process simulator is used.0 Coexistence Issues When multiple versions of HYSYS. However. only install one version on the target system. That significantly reduces the possibility of encountering the desktop heap exhaustion problem. 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. Aspen Plus. See Microsoft Knowledge Base articles 126962 and 184802. On a Windows XP system or a Windows 2003 Server without Terminal Services Operations Support 85 . up to 12 online applications can be loaded if they are not configured to use a remote solver.e. On a Windows 2003 Server with Terminal Services installed. Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues Unexpected simulation failures due to exhaustion of Windows desktop heap.

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. just 2 or 3 online applications that do not use a remote solver can be loaded. 86 Operations Support . The heap consumption can only be determined by experiment (download the Desktop Heap Monitor Version 8. Applications using remote solver The Aspen Remote Simulation Service allocates a single desktop heap which is shared among all the cases it opens. or just one Aspen Custom Modeler case.1 tool from Microsoft to help you inspect the desktop heap usage).installed. A conservative guideline would be to restrict use of a single Remote Simulation Service to 3 or 4 HYSYS and Aspen Plus cases. 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. 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.

Error message is displayed when using the Tab key to navigate user entries. change the low limit first then the high limit. Aspen Custom Modeler.NET Framework 2. If you cannot update the Microsoft component. and you want them to be Low=100 and High=200.0. Simulator version specification Operations Support 87 . In past versions of Aspen Online Deployment. The problem is resolved by updating the Microsoft . Aspen Online Deployment V7.Validity Limits must be entered in a particular sequence. In V7. Aspen HYSYS. and Exchanger Design and Rating. The problem occurs when using the Tab key to navigate user entry information in the Calculations tab of the Configure Application dialog. On Vista systems. then you can avoid the problem by using the mouse to navigate the user entry information. If you try to change the low limit first you will not be able to enter the value.0.5. A specific simulator version cannot be specified for HTFS+ (Exchanger Design and Rating) cases. Aspen HYSYS. and Aspen Custom Modeler. the default version of HTFS+ will be used.NET Framework 3. you could enter values for lower and upper validity limits in any sequence desired (i. this problem is eliminated by installing SP1 for .1 of Aspen Plus. V7.NET Framework. if the current limits are Low=0 and High=0. or vice versa).0. On Windows 2003 Server and Windows XP systems.CQ00321920 .1 Coexistence Issues Simulator support Workaround/Comment Aspen Online Deployment V7. you must first change the high limit to 200 and then the low limit to 100.e. this problem is eliminated by installing .1 supports version 2006. and V7.5. you must enter them in a way that does not invert the limits. Earlier versions are not supported.. A specific version can be specified for Aspen Plus. For example.

That significantly reduces the possibility of encountering the desktop heap exhaustion problem.Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues Configuring Process Engineering software to be used by AOD Workaround/Comment The AOD online server runs the process simulators under the local SYSTEM account. and then launch the configuration tools from that command window. Aspen Remote Simulation Service). This can cause unforeseen problems if there are configuration settings that need to be set so that the simulators function as expected.e. or a Windows 2003 Server without Terminal Services installed. up to 12 online applications can be loaded if they are not configured to use a remote solver. it also limits the number of such applications that can be loaded. to do that you'll need to run the 'Aspen Properties Database Selector' under the SYSTEM account. you can create a Command window that is running as the SYSTEM account. But. Unexpected simulation failures due to exhaustion of Windows desktop heap. just 2 or 3 online applications that do not use a remote solver can be loaded. Online Server administration” in the AOD Desktop online help. A good example is the selection of the Properties database. You will need to configure the SYSTEM account to use the correct properties database. See Microsoft Knowledge Base articles 126962 and 184802. 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. On a Windows XP system. you cannot logon as SYSTEM.. Applications using remote solver 88 Operations Support . See the online help topic “Configuring Process Engineering software to be used by AOD”. The impact of desktop heap exhaustion depends on whether the online applications are configured to use a remote solver. Unfortunately. found under “System Administration. On a Windows 2003 Server with Terminal Services installed. However.

1) you must enter them in a way that does not invert the limits. A conservative guideline would be to restrict use of a single Remote Simulation Service to 3 or 4 HYSYS and Aspen Plus cases. if the current limits are Low=0 and High=0. For example. CQ00321920 .if you try to change the low limit first you will not be able to enter Operations Support 89 . or just one Aspen Custom Modeler case.e. you must first change the high limit to 200 and then the low limit to 100 -.. and you want them to be Low=100 and High=200. 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. or vice versa).The Aspen Remote Simulation Service allocates a single desktop heap which is shared among all the cases it opens. The heap consumption can only be determined by experiment (download the “Desktop Heap Monitor Version 8. change the low limit first then the high limit.1” tool from Microsoft to help you inspect the desktop heap usage).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. In this version (V7. 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. 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. To ensure the largest number of simulations can be run before encountering the desktop heap limitation.

Supporting Dialog Boxes and Windows”. To see the help information for Configure Online Server. for example: cd “c:\Program Files\AspenTech\Aspen HYSYS 2006. resulting in an error when you attempt to activate the models. For example.0 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues General Usability Issues If you have earlier versions of HYSYS installed. Workaround/Comment Not applicable Workaround/Comment • Open a command prompt window. you can display the Desktop Help from the AOD Desktop Help menu and locate the topic “Configure Online Server – Dialog Box”. If you only have HYSYS V7. found under “Dialog Boxes and Screen Displays. Aspen OTS Framework might attempt to use these. CQ00354695 . • Change your current folder to the one containing the earlier version of Aspen HYSYS.Configure Online Server help button error The help button in the Configure Online Server may not work. installed you will not see this issue. you may see a dialog indicating an error and giving you the option to abort or continue (you should select continue). 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). the AOD variable name "NapthaD 95%". for example: NapthaD 95pct."Cut Pt-5.00%" should be changed to remove the quotation and percent characters.Cut Pt-5.5” • Enter the following command: 90 Operations Support .0. 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.00pct. Aspen OTS Framework V7.the value. there is no such restriction on variable names in the simulation case.

the value should be automatically reset to False so that you can take another snapshot. you might see an unhandled exception error.0.Snapshot to True. for example: cd “c:\Program Files\AspenTech\Aspen HYSYS V7.exe /unregserver • Repeat this for any other earlier versions of HYSYS that you have installed. Use the Aspen OTS Framework GUI to take snapshots. Aspen OTS Framework V7. You can take a snapshot from an OPC client by setting the value of the tag Simulation. after you have done this.exe /regserver When using the Browse options from the Tools menu to select variables for Control Signal Connections.hysys. 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.1 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Operations Support 91 . However. This is not happening. • Change your current folder to the one containing Aspen HYSYS V7.0” • Enter the following command: hysys.

92 Operations Support .

Aspen OnLine V7.0 and V7.0 and V7.1 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Aspen OnLine V7.1 93 .

0 and V7.1 .94 Aspen OnLine V7.

0 and V7.1 (formerly Aspen Hydrocracker) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues Workaround/Comment Aspen Plus Refinery Based Reactors 95 .0 and V7.Aspen Plus Refinery Based Reactors Aspen Plus Catcracker V7.1 (formerly Aspen FCC) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Aspen Plus Hydrocracker V7.

No known issues Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Aspen Plus Hydrotreater V7.1 (formerly Aspen CatRef) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable 96 Aspen Plus Refinery Based Reactors .0 and V7.1 (formerly Aspen Hydrotreater) Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Aspen Plus Reformer V7.0 and V7.

1 Coexistence Issues No known issues Workaround/Comment Not applicable Installation Issues No known issues Workaround/Comment Not applicable General Usability Issues No known issues Workaround/Comment Not applicable Aspen Open Object Model Framework V7.Aspen Open Object Model Framework V7.0 and V7.1 97 .0 and V7.

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

You're Reading a Free Preview

Descarga
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->