AspenEngineeringSuiteV7 3 Issues

Known Issues in V7.3

Aspen Engineering

Version Number: V7.3March 2011

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

Aspen Acol+™, Aspen Adsim®, Aspen Adsorption , Aspen Air Cooled Exchanger, Aspen Basic Engineering, AspenBatch Process Developer, Aspen Batch Distillation, Aspen Batch Plus®, Aspen BatchSep™, Aspen Capital CostEstimator, Aspen CatRef®, Aspen Chromatography®, Aspen COMThermo®, Aspen Custom Modeler®, AspenDistillation Synthesis, Aspen Dynamics®, Aspen Energy Analyzer, Aspen FCC®, Aspen Fired Heater, AspenFiredHeater, Aspen Flare System Analyzer, Aspen FLARENET™, Aspen HTFS Research Network™, Aspen HX-Net®,Aspen Hydrocracker®, Aspen Hydrotreater™, Aspen HYSYS Amines™, Aspen HYSYS Dynamics™, Aspen HYSYSOLGAS 3-Phase™, Aspen HYSYS OLGAS™, Aspen HYSYS PIPESYS™, Aspen HYSYS RTO™ Offline, Aspen HYSYSUpstream Dynamics™, Aspen HYSYS Upstream Dynamics™, Aspen HYSYS Upstream™, Aspen HYSYS Upstream™,Aspen HYSYS®, Aspen HYSYS® Thermodynamics COM Interface, Aspen HYSYS®, Aspen HYSYS® PipelineHydraulics - OLGAS 2-Phase, Aspen HYSYS® Pipeline Hydraulics - OLGAS 3-Phase, Aspen HYSYS® PipelineHydraulics - PIPESYS, Aspen HYSYS® Offline Optimizer, Aspen HYSYS® Hydrocracker, Aspen HYSYS® Reformer,Aspen HYSYS® CatCracker, Aspen HYSYS® Petroleum Refining, Aspen Icarus Process Evaluator®, Aspen IcarusProject Manager®, Aspen In-Plant Cost Estimator, Aspen Kbase®, Aspen MINLP Optimization, Aspen Mixed IntegerOptimizer, 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 Properties Mobile, Aspen Rate-Based Distillation, AspenRateSep™, Aspen Reaction Modeler, Aspen RefSYS Catcracker™, Aspen RefSYS Hydrocracker™, Aspen RefSYSReformer™, Aspen RefSYS™, Aspen Shell & Tube Exchanger, Aspen Shell & Tube Mechanical, Aspen SimulationWorkbook™, Aspen Solubility Modeler, Aspen Split™, Aspen Tasc+™, Aspen Teams®, Aspen Utilities On-LineOptimizer, Aspen Utilities Operations™, Aspen Utilities Planner™, Aspen Zyqad™, SLM™, SLM Commute™, SLMConfig Wizard™, the Aspen leaf logo, and Plantelligence are trademarks or registered trademarks of AspenTechnology, 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 aresolely 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 softwaremay be found in the applicable license agreement between AspenTech and the user. ASPENTECH MAKES NOWARRANTY 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 RoadBurlington, MA 01803-5501USAPhone: (1) 781-221-6400Toll Free: (1) (888) 996-7100URL: http://www.aspentech.com

http://www.aspentech.com/

Contents iii

Contents

Contents.................................................................................................................iii

Introduction............................................................................................................5

Aspen Engineering Workflows.................................................................................7

Process Engineering Console V7.3 ......................................................................7

Process Modeling (Aspen Plus) ...............................................................................9

Aspen Plus V7.3 ...............................................................................................9OLI Interface V7.3.......................................................................................... 11Aspen Properties V7.3..................................................................................... 11Aspen Properties Mobile .................................................................................. 12Aspen Custom Modeler V7.3 ............................................................................ 12Aspen Model Runner V7.3 ............................................................................... 13Aspen Plus Dynamics V7.3 (formerly Aspen Dynamics) ....................................... 13Aspen Adsorption V7.3 (formerly Aspen Adsim) ................................................. 14Aspen Utilities Planner V7.3............................................................................. 14Aspen Reaction Modeler V7.3........................................................................... 15

Process Modeling (HYSYS) ....................................................................................17

Aspen HYSYS V7.3 ......................................................................................... 17Aspen HYSYS Dynamics V7.3........................................................................... 18Aspen HYSYS Upstream V7.3........................................................................... 19Aspen HYSYS Petroleum Refining V7.3 (formerly Aspen RefSYS) .......................... 19

Exchanger Design and Rating................................................................................21

All Exchanger Design and Rating Products V7.3.................................................. 21All Exchanger Design and Rating Products V7.3.1............................................... 21Aspen Air Cooled Exchanger V7.3.1 (formerly Aspen ACOL+) .............................. 22Aspen Fired Heater V7.3.1 (formerly Aspen FiredHeater)..................................... 23Aspen Shell & Tube Exchanger V7.3.1 (formerly Aspen TASC+) ........................... 23Aspen Shell & Tube Mechanical V7.3.1 (formerly Aspen TEAMS)........................... 24Aspen Plate Exchanger V7.3.1 (formerly Aspen Plate+)....................................... 25Aspen HTFS Research Network V7.3.1 .............................................................. 25Aspen MUSE V7.3........................................................................................... 26Aspen Plate Fin Exchanger V7.3.1 .................................................................... 26

iv Contents

Economic Evaluation .............................................................................................27

All Economic Evaluation V7.3 Products .............................................................. 27Aspen Process Economic Analyzer V7.3 (formerly Aspen Icarus Process Evaluation)32Aspen In-Plant Cost Estimator V7.3 (formerly Aspen Icarus Project Manager) ........ 32Aspen Capital Cost Estimator V7.3 (formerly Aspen KBase) ................................. 34Icarus Evaluation Engine V7.3 ......................................................................... 36

Energy and Flare Analysis .....................................................................................37

Aspen Energy Analyzer V7.3 (formerly Aspen HX-Net) ........................................ 37Aspen Flare System Analyzer V7.3 (formerly Aspen FLARENET) ........................... 38Aspen HYSYS Thermodynamics COM Interface V7.3 (formerly Aspen COMThermo). 39

Aspen Simulation Workbook .................................................................................41

Aspen Simulation Workbook V7.3..................................................................... 41

Process Development............................................................................................43

Aspen Batch Process Developer V7.3 (formerly Aspen Batch Plus) ........................ 43Aspen Solubility Modeler V7.3.......................................................................... 44

Advanced Modeling Options (Process Development).............................................45

Aspen Batch Distillation V7.3 (formerly Aspen BatchSep) .................................... 45Aspen Chromatography V7.3 ........................................................................... 46Aspen Process Tools V7.3 ............................................................................... 46Aspen Process Manual V7.3 ............................................................................. 47

Aspen Basic Engineering .......................................................................................49

Aspen Basic Engineering V7.3 (formerly Aspen Zyqad) ....................................... 49

Operations Support ...............................................................................................51

Aspen Online Deployment V7.3 ........................................................................ 51Aspen OTS Framework V7.3 ............................................................................ 52Aspen Online V7.3.......................................................................................... 52

Aspen Plus Based Refinery Reactors .....................................................................53

Aspen Plus Catcracker V7.3 (formerly Aspen FCC).............................................. 53Aspen Plus Hydrocracker V7.3 (formerly Aspen Hydrocracker) ............................. 54Aspen Plus Hydrotreater V7.3 (formerly Aspen Hydrotreater)............................... 54Aspen Plus Reformer V7.3 (formerly Aspen CatRef) ............................................ 55

Aspen Open Object Model Framework...................................................................57

Aspen Open Object Model Framework ............................................................... 57

PE/PD Console ......................................................................................................59

PE/PD Console ............................................................................................... 59

Introduction 5

Introduction

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

Known issues are listed as those relating to:

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

Installation issues (potential problems arising during the install or uninstallprocedure).

Usability issues.

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

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

http://support.aspentech.com/

6 Introduction

Aspen Engineering Workflows 7

Aspen EngineeringWorkflows

Process Engineering ConsoleV7.3

Coexistence Issues Workaround/Comment

No known issues Not applicable

Installation Issues Workaround/Comment


General Usability Issues Workaround/Comment


8 Aspen Engineering Workflows

Process Modeling (Aspen Plus) 9

Process Modeling (AspenPlus)

Aspen Plus V7.3


Aspen Plus will freeze when it istrying to display the start pagewhen it is running on a Citrix clientconnected to a server runningWindows Server 2003, and theuser account does not haveadministrator privileges.

Install the patch provided by Microsoft in theirknowledge base article KB955692, which canfound at:

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

If multiple versions of EconomicEvaluation are installed and thenone is uninstalled, the toolbarbutton and menu command toActivate Costing may fail with anerror "Failed initializing costing. Besure that Economic Evaluation isinstalled."

Reinstalling Economic Evaluation should fix theproblem. The Repair option from the installermay also work.




Sometimes, property tables, whichreference streams, are not regeneratedafter making changes to a run.

This happens when the changes youmake are handled via an Edit Run. Toforce the tables to update, reinitialize thesimulation and re-run it. You can turn offInteractively Load Results on theTools | Options | Run tab to ensurethis is always updated.


10 Process Modeling (Aspen Plus)


Copying and pasting the table on anObject Manager screen (which normallydisplays the names of objects, theirtypes, and their solution status) doesnot work correctly.

The list of names of the objects copiescorrectly.

Attempting to view a Custom StreamSummary with more than 40,000 cellsmight cause Aspen Plus to freeze.

Avoid doing this. Instead, use theResults Summary | Streams form, oruse the Custom Stream Summary formswithin individual blocks, or specifyInclude Streams under Setup |Report Options | Streams to limitwhich streams are reported, or movesome streams and blocks into Hierarchyblocks so that there are not too manystreams present at any one level ofhierarchy.

When you specify a News Feed URL forthe Start Page, if you fail to include theprefix (such as http://), Aspen Plus willcrash.

Be sure to include this prefix whenentering the News Feed URL.

When using the Heat Exchanger Designbutton in the Analysis toolbar to sendheat exchanger data to EDR, if you havea Heater block in the simulation with thewrong type of utility specified on oneside (such as Steam for cooling or Waterfor heating) then EDR may crash.

When this crash occurs, you will see themessage "Import from Aspen Plus:Error generating PSF file. Make sure theblock is already solved," followed by anadditional error from HTFSPSF.

If this occurs, verify the type of utilityand direction of temperature change foreach Heater block in the simulation.

A ConSep block appears in theColumns tab of the Model Library, but ifyou add this ConSep block to theflowsheet, it does not work.

Ignore this ConSep block and use theone on the Conceptual Design tab ofthe Model Library after following theinstructions in the help topicConfiguring Aspen Plus for ConSep.

When using Excel Calculator blocks, ifyou define variables using the Definetool provided in the Excel Add-in, Excelmay crash.

Define variables on the Define sheet inAspen Plus before opening Excel.


OLI Interface V7.3







Aspen Properties V7.3








Aspen Properties Mobile




Upgrading a V7.2.1 Aspen PropertiesMobile server to the V7.3 versionoverwrites any customizations to theweb.config file.

Save a copy of the web.config file beforeupgrading. If Aspen Properties V7.3 hasbeen installed, the new web.config willbe configured to use this version and thelatest databanks, along with the LDAPconfiguration entered during theinstallation. Any other changes to theweb.config will need to be manuallycopied into the file provided by the newversion.



Aspen Custom Modeler V7.3






You can export Structures from AspenCustom Modeler for use in Aspen Plus.However if you attempt to use these inAspen Plus it does not work reliably, andmay cause a crash. Exporting of Modelsfor use in Aspen Plus works fine.

Do not export Structures for use inAspen Plus. You can still instanceStructures within models that you exportto Aspen Plus.



The PolyPlus example contains AspenPlus input files that can no longer beloaded by Aspen Plus V7.3. Thefollowing files: hpde.inp, nylon6.inp,pp.inp and ps.inp contain references tothe PURE10 databank which is no longersupported by Aspen Plus.

Open the files in Notepad and change allinstances of the string PURE10 toPURE25. The edited files should nowload in Aspen Plus.

On some systems, the Regen examplemight fail when you click on the LaunchACM button in the Regen Control Panel.

Open the file RegenDemo.sln in VisualStudio and rebuild the project. The newversion of the program RegenDemo.exeshould now launch ACM.

Aspen Model Runner V7.3







Aspen Plus Dynamics V7.3(formerly Aspen Dynamics)








Aspen Adsorption V7.3(formerly Aspen Adsim)







Aspen Utilities Planner V7.3








Aspen Reaction Modeler V7.3








Process Modeling (HYSYS) 17

Process Modeling (HYSYS)

Aspen HYSYS V7.3






Importing a MUI file into HYSYS PlateFin link only partially completes and LNGunit op fails to solve.

You should import the MUI file beforemapping LNG passes to EDR streamnumbers.

Using the Beggs and Brill correlation(1973 or 1979) for inclined segments inthe HYSYS Pipe operation can giveincorrect pressure drops if the samecorrelation is not selected for horizontalpipes.

To use a Beggs and Brill correlation forthe inclined segments within a HYSYSpipe operation, the same correlationmust also be selected for the horizontalsegments. This is necessary because thewrong flow regime correlation is used,which causes an incorrect pressure dropcalculation. However, if the othercorrelations (HTFS, OLGAS,Gregory/Aziz/Mandhane) are used for theinclined segments, then any correlationcan be selected for the horizontalsegments.

Valve in Steady State Rating ModeCannot Determine Choking Conditions

This happens because the current steadystate solver cannot solve the pressuredrop and choking conditionssimultaneously.

Component Splitter Is Slow in Solving ALarge Sparse Split Specification Matrix

Try to avoid such a large and sparsesetup.

18 Process Modeling (HYSYS)


Use of Aspen Properties from HYSYS(Retired Databanks)

When a fluid package is created byimporting an Aspen plus/AspenProperties backup file which contains theretired databanks (PURE10, PURE93,PURE856, AQU92), the fluid packagemay not have the necessary purecomponent databanks required for ameaningful simulation. This is becausethe retired databanks (which no longerexist in the default APV73 database) arenot automatically upgraded to the latestpure-component databanks (i.e., PURE25and AQUEOUS). As a result, some or allof the components specified in thebackup file may not have access to thenecessary property parameters. This cancause the simulation to fail or to giveinaccurate results. The workaround is toselect the latest pure componentdatabanks (PURE25 and AQUEOUS) onthe Enterprise Databases tab of theComponent List View.

Export Heat Exchanger Heat Curves toABE:

a) Tube-side vapor-phase thermalconductivity values are incorrect.Shell-side values are transferredinstead of tube-side values.

b) Vapor-phase mass-density valuesare incorrect: molar density is

transferred instead of massdensity.

None

Aspen HYSYS Dynamics V7.3






No known issues No known issues

Process Modeling (HYSYS) 19

Aspen HYSYS Upstream V7.3






Conceptual Design Builder: Profiles plotsdo not to show correctly in the excelprofile report.

Profile data is correctly exported to Excelso it can be used to generate the plotsmanually.

Conceptual DesignBuilder/Stabilizer Column: Whenusing crudes from the Assay Librarytogether with an RPV specification, thestabilizer column has difficultiesconverging.

It is recommended in this case to selectthe TVP specification.

Aspen HYSYS PetroleumRefining V7.3 (formerly AspenRefSYS)






If you are using a reformer,hydrocracker, or an FCC, or a flowsheetwith one of these models, HYSYS maycrash due to the extra memoryrequirements for the new start page.

You should disable the start page if youare using one of the reactor models. WhenHYSYS opens, the start page will show. Inthe lower-left-hand corner of the startpage, uncheck Show Start Page NextTime. Exit and restart HYSYS.

20 Process Modeling (HYSYS)


The Petroleum column does notcalibrate when calibration is triggered byFCC flowsheet.

You should calibrate the FCC reactor firstand then the petroleum column. This willrequire you to enter the calibration datadirectly into the petroleum columncalibration environment since data mayhave been improperly transferred fromthe FCC.

When you try to save big PetroleumRefining cases as XML, the applicationwill crash, giving a message that it islow on memory

In general XML is not supported forPetroleum Refining cases.

The Healy method for RON/MONblending gives unrealistic numbers andthe problem is apparent either in streamproperties or in the product blender.

Select the Volume Blending method inPetroleum Assay Manager view > PropertyBlending Methods for RON / MON option.

If you attach a product stream to thereformer or hydrocracker and thendelete the stream, it will also delete theinternal stream. At that point, you willno longer be able to connect a productstream to the model and HYSYS mayhang or crash when solving the model.

You should always disconnect the productstream from the reformer or hydrocrackerbefore deleting the stream.

Exchanger Design and Rating 21

Exchanger Design and Rating

All Exchanger Design andRating Products V7.3This section contains a summary of known issues or limitations relating to thisrelease. Workarounds are suggested where possible.

All Exchanger Design andRating Products V7.3.1This section contains a summary of known issues or limitations relating to thisrelease. Workarounds are suggested where possible.






CQ00392063 – Labels are missing inHeadings / Remarks

In Input | Problem Definition |Headings/Remarks, the labels such asCompany:, Location:, Service of Unit:,etc., are missing for new cases.

Affects all EDR applications.

Select Tools | Program Settings,Headings/Drawing tab and click OK.This only need be done one time;thereafter, the labels are present.

CQ00294553 – There is a HYSYS close-down error after EDR-Shell&Tube orEDR-AirCooled results have beenviewed.

Affects HYSYS used with EDR

There is no corruption of data.

22 Exchanger Design and Rating


CQ00413119 – Aspen properties fails towork after transfer from AirCooled toPlate.


After doing a Run-Transfer from AspenAir Cooled Exchanger to Aspen PlateExchanger, EDR appears to hang whileAspen Properties starts. The workaroundis to save and close EDR and then reopenonly the Aspen Plate Exchanger case.

CQ00397130 – File-Open crashes if EDRhas exported to Excel.


If an EDR file has been exported to Exceland then File-Open is selected, EDR willcrash. The workaround is to export toExcel and then close and reopen EDR.

CQ00378264 – EDR fails to identify theproperty method specified in the AspenProperties aprbkp file.


EDR does not display the AspenProperties property method in imported.aprbkp or referenced .aprpdf files;EDR always displays AMINES. This is adisplay issue only; the Aspen Propertiesmethod specified in the Aspen Propertiesfile is used.

Aspen Air Cooled ExchangerV7.3.1 (formerly Aspen ACOL+)Coexistence Issues Workaround/Comment







Aspen Fired Heater V7.3.1(formerly Aspen FiredHeater)







Aspen Shell & Tube ExchangerV7.3.1 (formerly Aspen TASC+)






CQ00430263 – Import from an AspenPlus block, such as HEATER, shows anegative pressure drop in EDR Processdata.

Affects Shell&Tube.

If the inlet stream pressure is less thanthe block pressure, a negative pressuredrop will be imported. The workaround iseither to specify a pressure drop for theblock or change the inlet and/or blockpressures to ensure a positive pressuredrop.

For a block with multiple feed streams,the lowest stream pressure is used in theEDR Process data. One workaround is toadd a mixer block upstream of the blockand make sure a positive pressure dropresults.


The Advanced method is not yetavailable for kettles or double pipeexchangers.

Affects Shell&Tube.

None. The Standard Method gives well-proven results.

The warning messages to show theestimate of the required number ofintermediate supports (for no-tube-in-window exchangers) and U-bendsupports do not appear.

Affects Shell&Tube

The messages should appear when therequired number of supports to preventserious vibration warnings exceeds theinput values.

The vibration output will still indicate thatthere is a vibration problem when theinput number of supports is insufficient.

The number of supports required toeliminate the problem can easily befound by trial and error.

The tube pitch on the tube patternschematic on the Tube Layout diagramis incorrect.

Affects Shell&Tube and Shell&TubeMechanical.

The error is in the schematic only, thetube layout and related calculations usethe correct value and are not affected.

The similar schematic in Shell&TubeMechanical – TEAMS_Tube_Layout – iscorrect.

Aspen Shell & Tube MechanicalV7.3.1 (formerly Aspen TEAMS)






The tube pitch on the tube patternschematic on the Tube Layout diagramis incorrect.

Affects Shell&Tube and Shell&TubeMechanical.

The error is in the schematic only, thetube layout and related calculations usethe correct value and are not affected.

The similar schematic in Shell&TubeMechanical – TEAMS_Tube_Layout – iscorrect.


Aspen Plate Exchanger V7.3.1(formerly Aspen Plate+)







Aspen HTFS Research NetworkV7.3.1








Aspen MUSE V7.3







Aspen Plate Fin ExchangerV7.3.1







Economic Evaluation 27

Economic Evaluation

All Economic Evaluation V7.3ProductsThe following section describes known issues that can apply to all EvaluationV7.3 Products.


Users running Microsoft Windows withWindows Installer 3.1 may experiencecoexistence issues with Economic EvaluationV7.2 and previous versions as describedbelow:

1. The following aspenONE applications areinstalled on a machine:

o EEV7.2.1 (or EEV7.2), EEV7.3

o HYSYS and/or Aspen Plus V7.2+EPs

2. Invoking the Export to EE feature ineither HYSYS or Aspen Plus invokesEEV7.2.1 (or EEV7.2) instead of EEV7.3.This may occur if none of the EE installedsoftware versions are run afterinstallation. This is due to the windowsinstaller resiliency behavior. Once theproblem occurs in one user environment,it is observed with all other users on thatmachine.

1. Update Windows Installer to

version 4.5, which can be

downloaded from the following

site.

http://www.microsoft.com/downloads/details.aspx?FamilyID=5a58b56f-60b6-4412-95b9-54d056d6f9f4&displaylang=en

Note: See the installation guide onhow to check which version ofWindows Installer is present onyour system.

1. Ensure EE V7.2.1 (or EEV7.2)/V7.3is executed as standaloneapplication before invoking EE viaHYSYS V7.2 (or Aspen Plus V7.2).

2. In cases where the problemoccurs, an upgrade/repairinstallation of EE V7.3 can beperformed by running the EE V7.3installation again. The procedureallows the EE V7.3 to be reset asthe default costing feature w/

HYSYS /Aspen Plus V7.2.

Comment: Following the steps belowon the system where EE V7.3 isinstalled alongside previous versions ofEE can avoid the aforementionedissues.





28 Economic Evaluation

1. Update the Windows Installer toversion 4.5

2. Launch EE V7.2.1 (or EEV7.2) andallow the EE V7.2.1 WindowsInstaller resiliency to go through, ifthis the first time EE V7.2.1 isbeing launched under this useraccount.

3. After c;psomg EE V7.2.1, launchEE V7.3 and allow the EE V7.3Windows Installer resiliency to gothrough, if this is the first time EEV7.3 is being launched under thisuser account.




The Manpower Productivity Expert (MPE) isnot supported on 64 bit operating systems(for example, Microsoft Windows 7 or Vista 64bit). Users running these operating systemswill not be able to run this feature. All otherEconomic Evaluation features are functionalwithin these environments.

None.

Retrieval of stream pricing specified in aHYSYS simulation cannot be retrieved byAPEA at this time.

Note: Support for retrieval of HYSYS streampricing is available in the V7.3.1 release ofAPEA. Refer to the What’s New Section of theV7.3.1 APEA Release Notes for furtherinformation.

None.

CQ418712

Aspen Basic Engineering (ABE) V7.2 (+ EPs)will not function with ACCE V7.3.

Note: This EP is not required in order for ABEV7.3 to function with ACCE V7.3 (or ACCEV7.3.1).

Comment:

Note: The new equipment models containedin EE V7.3 do not have corresponding classviews in either ABE V7.2 or V7.3. Thus, datafor these components will not flow betweenthe applications via the Cost Mapper.

An emergency patch has been issuedfor ABE V7.2 to integrate with ACCEV7.3. Please refer to Solution ID#130686 on the Aspen TechnologySupport Site and follow theinstructions on installing this EP. Onceinstalled, ABE V7.2 will function withACCE V7.3.



CQ425673

When using integrated sizing and costing inAspen Plus or HYSYS, if a Mapping process iscompleted without Sizing and the Mappingprocess is again initiated without a simulationchange, the Mapping GUI will not show theLast Mappings made (even if the LastMappings box is checked). Although, thesystem ‘remembers’ the Last Mappings, theGUI will not show them. This means if theuser tries to map the unit ops once again,duplicate components will be created.

In order to see the Last Mappings, aninsignificant change can be made inthe simulator and afterrunning/reloading the data, theMapping process will default to LastMapping and the previous mappingswill now appear.

Note: This defect has been correctedin the V7.3.1 release of APEA.

CQ425575

Projects created in EE V7.2 (not EE V7.2.1)containing air dryers will lose the flowratespecification when the project is opened ineither EE V7.2.1 or V7.3. The field will beblank and if a project evaluation is made, thisitem will not be included in the estimate.

Projects created in EE V7.1 and earlier willsee a ? in the flowrate field when theseprojects are opened in EE V7.2.1 or V7.3. Inthis case when a project evaluation is run, awarning message will be generated indicatinga ? is present in the input.

The flowrate will need to berespecified when projects containingthis component are opened in eitherV7.2.1 or V7.3.

Note: This defect has been correctedin the V7.3.1 release of EE.

CQ - 425863

The current systems V7.2, V7.2.1, and V7.3will allow projects to be merged ontothemselves. When this is run, data in theiccache may be replaced by the data in theproject selected to merge from (due to thefact both projects have the same name).Thus, it is not recommended this action beperformed as there may be more recententries or specifications in the Target projectthat will get overwritten when selecting the“old” project of the same name to mergefrom.

In addition, since multiple EE processes arenow supported in V7.3, users can merge orimport data from a project already open in adifferent instance. This is not recommendedand may lead to data base errors and lose ofdata in the projects that are selected tomerge from

Projects selected to be merged fromshould be closed before the Mergeprocess is initiated.

Note: This issue has been corrected inthe EE V7.3.1 release. Refer to theWhat’s New Section of the V7.3.1 EERelease Notes for further information.



CQ429417

If a ‘target’ project is opened and anotherproject is opened to be used as a ‘source’project via drag/drop methods, opening ofthis ‘source’ project in another instance willnot be supported. In order to open the ‘sourceproject’ in another instance, the originaltarget project should be closed.

This workflow cannot be supported. Ifa mechanism is imposed to lock outthe source project (e.g. to preventopening in another instance), then itwill not be possible for the drag/dropto work. If it is required to open thesource project in another instance, thetarget project (from which the sourceproject was initially opened) will haveto be closed. This will enable thesource project to be opened in thesame or new instance.

CQ404999

Source media may be required whenResiliency is triggered.

The software will trigger Resiliency toconfigure the application for a new orRestricted user on a machine. This will occurthe first time any EE application is launched(by the user) and will not occur again once ithas successfully completed. Thus, in order forthe system to behave as designed, it isimportant to let the Resiliency processcomplete. Under normal situations, Resiliencycan be completed without requiring theSource Media from which the application wasinstalled from. However, there have beencomplications where a request is made duringthe Resiliency Process for the source media.

During testing, we have determined potentialcause for the source media requirement. Ifanother user on the same machine ran MSExcel from within the EE system, even if theExcel spreadsheet is merely opened andclosed without saving, some file attributeschange in Excel that cause the installer tothink the installation has changed (theattributes that are changed are invisible tothe user). Once this happens, the sourcemedia requirement is made by the installer.

The root cause of this issue is a MicrosoftExcel 2003 design issue (it does not happenwith Word 2003 or Excel 2007) and cannot befully address within the application orinstaller. As a reference, the following MS KBlink describes the Excel behavior.


If the source media is available, theuser should make it available duringthis process. This media can be thedownload location, network drive, orDVD (when available).

If the source media is not available,the original user that ran MS Excelfrom the EE application will need torun the same test (under the originalaccount).

If the Reporter was run, the usershould open the correspondingtemplate xls file in Excel and save thefile (w/o any changes). This willchange the time stamp on the file andthe installer will ignore it when theResiliency process is run. The Exceltemplate files are located in:

\Documents and Settings\AllUsers\Documents\AspenTech\SharedEconomic EvaluationV7.3\Reporter\Templates



CQ426039

Users having metric projects with custom pipespecs files attached will see a crash when theapplication (either ACCE or AICE) is closed. Itis a nuisance crash that does not affectproject or application performance as theproject/application can be used in thecustomary manner (that is, evaluated/savedin the normal way). The crash does nothappen when IP projects containing custompipe specs are used. The issue does notpertain to APEA as this product does notpermit custom pipe specs from being used.

An emergency patch has been issuedfor EE V7.3 to correct this issue.Please refer to Solution ID# 130686on the Aspen Technology Support Siteand follow the instructions oninstalling this EP. Once installed,metric projects used or created ineither ACCE or AICE V7.3 will not seea crash when the application is closed.

Note: This issue has been corrected inthe V7.3.1 EE release.

CQ00420283

When scheduling data is transferred toPrimavera, a new calendar is created alongwith the project. The name of the Calendarstarts with the project name. If while loadingthe calendars a corrupted calendar object isencountered, the Primavera Integration APIwill generate an error. This generallyhappens when the Primavera database has acorrupted calendar. When this error isgenerated, AICE stops transferring schedulingdata to P6. In EEV7.3.1 this behavior hasbeen changed and it will now skip loading thecalendars from the Primavera database if itencounters any problem during loading thecalendars. The application will make use ofthe default Primavera calendar in such errorconditions and data transfer to P6 will not bestopped. However, it will ignore “Number ofDays/Week” and “First Day of the Week” fieldspecified under Schedule settings Specs andfollowing message will be displayed:

The Primavera project will use “Number ofDays/Week” and “First Day of the Week”defined in the default Primavera calendar.

To correct this issue:

1. User needs to adjust defaultPrimavera Calendar to makethe schedule consistent withthe IPM Schedule SettingsSpecs.

2. Install a new database topermanently fix the issue.

In order to support HYSYS Stream Pricingwithin APEA V7.3.1 (see What’s Newdocumentation), APEA V7.3.1 will no longersupport earlier versions of HYSYS (V7.2 andearlier).

HYSYS users will be required to useHYSYS V7.3 to integrate with APEAV7.3.1.


Aspen Process EconomicAnalyzer V7.3 (formerly AspenIcarus Process Evaluation)







Aspen In-Plant Cost EstimatorV7.3 (formerly Aspen IcarusProject Manager)







CQ00420283

Headline: Scheduling data transfer fromAICE to P6 fails if it encounters acorrupted calendar object in Primaveradatabase while loading the Primaveracalendars.

When scheduling data is transferred toPrimavera, a new calendar is createdalong with the project. The name of theCalendar starts with the project name. Ifwhile loading the calendars a corruptedcalendar object is encountered, thePrimavera Integration API will generatean error. This generally happens whenthe Primavera database has a corruptedcalendar. When this error is generated,AICE stops transferring scheduling datato P6. In EEV7.3.1 this behavior hasbeen changed and it will now skiploading the calendars from the Primaveradatabase if it encounters any problemduring loading the calendars. Theapplication will make use of the defaultPrimavera calendar in such errorconditions and data transfer to P6 willnot be stopped. However, it will ignore“Number of Days/Week” and “First Dayof the Week” field specified underSchedule settings Specs and followingmessage will be displayed:

The Primavera project will use “Numberof Days/Week” and “First Day of theWeek” defined in the default Primaveracalendar.

To correct this issue:

1. User needs to adjust defaultPrimavera Calendar to make theschedule consistent with the IPMSchedule Settings Specs.

2. Install a new database topermanently fix the issue.


Aspen Capital Cost EstimatorV7.3 (formerly Aspen KBase)


Users running Microsoft Windows withWindows Installer 3.1 may experiencecoexistence issues with EconomicEvaluation V7.2 and previous versions asdescribed below:

1. The following aspenONEapplications are installed on amachine:

EEV7.2.1 (or EEV7.2),EEV7.3

HYSYS and/or Aspen PlusV7.2+EPs

2. Invoking the Export to EE featurein either HYSYS or Aspen Plusinvokes EEV7.2.1 (or EEV7.2)instead of EEV7.3. This mayoccur if none of the EE installedsoftware versions are run afterinstallation. This is due to thewindows installer resiliencybehavior. Once the problemoccurs in one user environment,it is observed with all other users

on that machine.

1. Update Windows Installer to version4.5, which can be downloaded fromthe following site.

http://www.microsoft.com/downlo

ads/details.aspx?FamilyID=5a58b5

6f-60b6-4412-95b9-

54d056d6f9f4&displaylang=en

Note: See the installation guide onhow to check which version ofWindows Installer is present on yoursystem.

2. Ensure EE V7.2.1 (or EEV7.2)/V7.3 isexecuted as standalone applicationbefore invoking EE via HYSYS V7.2 (orAspen Plus V7.2).

3. In cases where the problem occurs, anupgrade/repair installation of EE V7.3can be performed by running the EEV7.3 installation again. The procedureallows the EE V7.3 to be reset as thedefault costing feature w/ HYSYS/Aspen Plus V7.2.

Comment: Following the steps belowon the system where EE V7.3 isinstalled alongside previous versions ofEE can avoid the aforementionedissues.

1. Update the Windows Installerto version 4.5

2. Launch EE V7.2.1 (or EEV7.2) andallow the EE V7.2.1 WindowsInstaller resiliency to go through, ifthis the first time EE V7.2.1 isbeing launched under this useraccount.

3. After closing EE V7.2.1, Launch EEV7.3 and allow the EE V7.3Windows Installer resiliency to gothrough, if this the first time EEV7.3 is being launched under thisuser account.









CQ00420283

When scheduling data is transferred toPrimavera a new calendar is createdalong with the project. The name of theCalendar starts with the project name.If while loading the calendars acorrupted calendar object isencountered, the Primavera IntegrationAPI will generate an error. This generallyhappens when the Primavera databasehas a corrupted calendar. When thiserror is generated, ACCE stopstransferring scheduling data to P6. InEEV7.3.1 this behavior has beenchanged and it will now skip loading thecalendars from the Primavera database ifit encounters any problem during loadingthe calendars. The application will makeuse of the default Primavera calendar insuch error conditions and data transferto P6 will not be stopped. The followingmessage will be generated if theseconditions exist:

It doesn’t affect ACCE users, the onlydifference is that the scheduling projectwill use the default Primavera calendar.

To correct this issue, Install a newdatabase to avoid above message box andpermanently fix the issue.


Icarus Evaluation Engine V7.3







Energy and Flare Analysis 37

Energy and Flare Analysis

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







38 Energy and Flare Analysis

Aspen Flare System AnalyzerV7.3 (formerly AspenFLARENET)






Automation Support: Only .fnwxml and.fnw cases can be loaded into AspenFlare System Analyzer thru OLEautomation interfaces.

The cases in .fnwx format as well asnew cases need to be saved in .fnwxmlformat first.

Automation Support: Failure to run FlareSystem Analyzer cases in rating/design/ or debottlenecking mode fromthe automation interface directly.

Following dlls : Fnacalc32.dll,MslBasiclib.dll, MathSolver.dll need to becopied to the path of the executable. Forexample, if the you are trying to run acase from a Microsoft excel macro, theabove mentioned dlls need to be copiedto the location where excel is installed,for example: \MicrosoftOffice\Office12\EXCEL.EXE

Information in the estimate page of thescenario editor is not saved to the.fnwxml file and also cannot beexported to .xml/.mdb/.xls files. Thisfield also does not dirty case or scenariowhen modified.

Make sure that these fields are initializedcorrectly after importing a Flarenet casepreviously saved as xml, access or as anexcel file.

All process data is saved in metric unitswhen a Flare System Analyzer case isexported to .xml/.mdb/.xls files

None.

Aspen Flare System Analyzer fails toimport the composition while importingsources from text files.

None.

Energy and Flare Analysis 39

Estimation of Tc and Pc of a hypocomponent can be wrong after savingand reloading a case.

If possible when creating a new case youcan generate the hypo componentsbefore closing the case. If this is notapplicable you can save the case to xmland reload it. After this the estimated Tcand Pc of newly created hypocomponents will be correct again.

PFD Printing: The All Tail option for thePFD is not printing correctly (althoughthe preview is correctly generated).

No workaround.

Aspen HYSYS ThermodynamicsCOM Interface V7.3 (formerlyAspen COMThermo)







40 Energy and Flare Analysis

Aspen Simulation Workbook 41

Aspen Simulation Workbook

Aspen Simulation WorkbookV7.3







42 Aspen Simulation Workbook

Process Development 43

Process Development

Aspen Batch Process DeveloperV7.3 (formerly Aspen BatchPlus)






If you are working on the English XPoperating system, you cannot enterChinese characters into the Renamedialog box when an Operations dialogbox is also open. The Chinese characterpreview box freezes.

Access the Rename dialog box througha different data form, for example Data| Pure Components | Rename.

Note: This workaround does not work forrenaming streams. To rename streams,delete the stream and re-enter it as a

new stream.

If your language is set to a Languageother than English, you might see errorswhen trying to produce the MessageSummary Excel Report or whenexporting data to a custom ExcelReport.

The language of Excel must match thelanguage setting in Windows. For Excel2003, this means that a languagespecific version of Excel needs to beinstalled. For Excel 2007 and Excel 2010,the Excel Language Pack must beinstalled.

Vapor Pressure calculations beyond thetemperature bounds of the Antoineequation have a new calculationprocedure. This might change results forair emissions and mixture bubble pointtemperatures.

The new procedure matches the AspenProperties procedure to extrapolate ln pversus 1/T when outside the temperaturebounds of the Antoine equation.

44 Process Development

The Recipe Document report may showreaction coefficients before and after themolecular structure image in thereaction.

Delete the extra reaction coefficients thatappear after the image.

Aspen Solubility Modeler V7.3







Advanced Modeling Options (Process Development) 45

Advanced Modeling Options(Process Development)

Aspen Batch Distillation V7.3(formerly Aspen BatchSep)







46 Advanced Modeling Options (Process Development)

Aspen Chromatography V7.3







Aspen Process Tools V7.3






FDFit incorrectly performs a unitconversion operation on the VolumeSteady value.

A possible work around is to use aVolume Steady value of 0 (zero).

FDFit fails to perform a unit conversioncorrection on the user entered filtrationpressure in scale-up calculations usingmultiple test data.

Enter the filtration pressure value withunits of Pa (i.e. 1000x that indicated inUI, which requests the pressure in kPa).

Advanced Modeling Options (Process Development) 47

Aspen Process Manual V7.3







48 Advanced Modeling Options (Process Development)

Aspen Basic Engineering 49

Aspen Basic Engineering

Aspen Basic Engineering V7.3(formerly Aspen Zyqad)


ABE Version V7.3 cannot exchange datawith HYSYS Version V7.2 or lower. Italso cannot exchange data with ACCEVersion V7.2 or lower.

ABE Version V7.3 will exchange data withHYSYS V7.3 and ACCE V7.3.


When upgrading existing V7.1 or V7.2 toV7.3, the upgrade installationunregisters the (VB6) knowledgebaserules (KBs) from versions V7.1 and V7.2replacing them with a new set of (.NET)KBs referenced in the new config files(StandardLibrarySet.cfg andTEFLibrarySet.cfg). If you havecustomized the VB6 KBs and wish to usethem in V7.3 they will have to be re-registered.

The VB6 KBs can be manually registeredfrom the command line, e.g.:

Regsvr32 Filters162.dl

Repeat this command for each of the*162.dll files

Alternatively you could download a bat filefrom the Customer Support websiteknowledge base solution:

http://support.aspentech.com/webteamcgi/SolutionDisplay_view.cgi?key= 131212

This file can be copied to the foldercontaining the VB6 KBs and invoked to re-register all the VB6 KB DLLs.

You are allowed to use a combination ofthe old VB6 and new .NET KBs in aworkspace library, but you cannotimplement the same module more thanonce. The .NET KBs should not beregistered, they need to be placed in thefolder referenced by the config file e.g.ManagedKBsDirectory= "KBS". See theAdministration help (zyadminapp.chm) inthe section:Managing Workspaces | MigratingWorkspaces to V7.1 and Later | Migrating

50 Aspen Basic Engineering

Workspaces to V7.1 and Later. If you arereferencing the managed KBs in yourconfig file, be sure to remove thesemodules from the DataServiceModuleskeyword.


Excel Datasheet Editor:enumerations: The drop-down lists onExcel datasheets, which displayavailable choices for enumeration fieldsincluding units of measurement, have amaximum of 255 characters.

This is a Microsoft Excel limitation.

Excel Datasheet Editor: Not all fieldscan be edited after object claimedfrom Excel: You can edit the valuefields on the current page, but otherfield types and other pages cannot beedited.

Close and reopen the datasheet to makeall fields editable.

Excel Datasheet Editor: Sub objectdata is not editable if the mainobject is not claimed: For example, ina project if the motor is claimed but thepump is not, you cannot edit data forthe motor.

Claim the parent object

Excel Datasheet Editor: FilterContinuous List: There are blank linesadded to the end of the list.

Close and reopen the datasheet – theblank lines will be removed.

Operations Support 51

Operations Support

Aspen Online Deployment V7.3


Simulator support. Aspen Online Deployment V7.3 supportsversions V7.1, V7.2, and V7.3 of AspenPlus, Aspen HYSYS, Aspen CustomModeler, Aspen Model Runner, andExchanger Design and Rating.

Earlier versions are not supported.

Simulator version specification. A specific simulator version cannot bespecified for Exchanger Design andRating (EDR) cases; the default versionof EDR is used.

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





52 Operations Support

Aspen OTS Framework V7.3







Aspen Online V7.3


Aspen Online V7.3 can coexist withearlier version of Aspen Online.

Aspen Online V7.3 requires Aspen PlusV7.3.




SQL error dialog when using ChineseOS.

Acknowledge error and continue. Thiserror message does not stop the normalfunctioning of the user interface.

Aspen Plus Based Refinery Reactors 53

Aspen Plus Based RefineryReactors

Aspen Plus Catcracker V7.3(formerly Aspen FCC)







54 Aspen Plus Based Refinery Reactors

Aspen Plus Hydrocracker V7.3(formerly Aspen Hydrocracker)







Aspen Plus Hydrotreater V7.3(formerly Aspen Hydrotreater)







Aspen Plus Based Refinery Reactors 55

Aspen Plus Reformer V7.3(formerly Aspen CatRef)







56 Aspen Plus Based Refinery Reactors

Aspen Open Object Model Framework 57

Aspen Open Object ModelFramework

Aspen Open Object ModelFramework







58 Aspen Open Object Model Framework

PE/PD Console 59

PE/PD Console

PE/PD ConsoleCoexistence Issues Workaround/Comment






60 PE/PD Console