question
stringlengths
19
6.88k
answer
stringlengths
38
33.3k
Problem Statement: How to enter a fixed amount for Basic Engineering in my project?
Solution: There are situations where you might want to override a calculated indirect cost in Aspen Capital Cost Estimator (ACCE) and enter a fixed cost. The “Indirects – Proratables” Customer External File is one way to do this. Let’s say your company does the Basic Engineering and you would like to enter that cost as a fixed cost in ACCE. For our example we will say the Basic Engineering Cost is $125000. First go to: Project Basis View| Customer External Files And do a right mouse button and choose “Select” From the menu choose “DEFAULT” and hit OK Do another right mouse button and choose “Edit” From the “External Indirects” menu choose “Specifications” and hit “Modify” Enter the following information (fields in black). This is entering the total Basic Engineering (COA 71) in as $125000 labor cost. Then hit OK, and then “Close”. Now go to Project Basis View | Engineering Workforce (By Discipline) and double click. Any information from the ‘Indirects – Proratables” form is in addition to the cost the system calculates for Basic Engineering. So we need to tell the system to use “0” (zero) hours for Basic Engineering which would result in a system calculated cost of $0 (i.e. zero dollars). Then the only Basic Engineering cost that will be seen and used will come from the “indirects – Proratables” file. To enter the “0” hours for our system, enter the following information (fields in black): Hit OK to save and close the window. Now we can do a Project Level Evaluation and then go to the Interactive Reports (Excel) Account Basis: And choose Run Report. You will then see the $125000 for Basic Engineering (COA 71). Keywords: Basic Engineering, indirects, indirects proratables, proratables (Indirects – Proratables) References: None
Problem Statement: What is the default value of ambient / atmospheric / barometric pressure in Aspen Plus? How can I change it?
Solution: The default ambient pressure is 14.6959 psi or 1.01325 bar. Go to the Simulation Environment and click on Setup | Global. You can view and change this value in this page. The picture below shows the interface. Note: Ambient pressure is used in gauge pressure specifications and calculations for both sequential modular (SM) and equation-oriented (EO) mode. Example: In the attached example, ambient pressure is set 3 psi. Inlet stream conditions are set 0 psig and 77 F. Bubble point temperature (TBUB) is reported as 141 F at a pressure of 3 psia. At default ambient pressure (14.69 psi), TBUB is about 212 F. Keywords: Ambient, bar, psi, gauge, pressure, default value, change References: None
Problem Statement: aspenONE Process Explorer (A1PE) presenta el error: Server is unable to acquire SLM_RN_PME_IP64_PRDSRV license, y no muestra valores.
Solution: Asegurarse de que el servidor de InfoPlus.21 (IP.21) esté corriendo bajo una licencia con estatus de “granted1. Abrir IP.21 Administrator Dar click derecho sobre el nombre de la base de datos | propiedades | revisar el estatus de la licencia Si IP.21 está corriendo con una licencia en “denied” (denegada) o en “grace period” (periodo de gracia), esto causará el problema en A1PE Si el estatus de la licencia es Granted realizar lo siguiente: En el servidor donde se encuentra A1PE instalado, abrir una Ventana de Comandos como Administrador y correr el comando IISReset. Puede suceder que AspenProcessDataAppPool no esté corriendo, este IIS Pool contiene la aplicación que es utilizada para que A1PE lea valores del servidor de IP.21. Si después de realizar IISReset el problema persiste, Abrir Internet Information Services Manager (IIS Manager) (del menu de inicio de Windows), seleccionar “Application Pools” y verificar que AspenProcessDataAppPool esté corriendo con una cuenta de Administrador correcta Artículo Original: Server is unable to acquire SLM_RN_PME_IP64_PRDSRV license when opening Aspen One Process Explorer Palabras Clave ESP Server is unable to acquire SLM_RN_PME_IP64_PRDSRV license A1PE Estatus de Licencia AspenProcessDataAppPoolx86 IISReset Keywords: None References: None
Problem Statement: Why I’m unable to take total mass/mole flow from results streams to custom table in Aspen Plus V9?
Solution: In Aspen Plus V9 we have changed stream summary report. In Aspen Plus V9 we can able to view stream summary or stream reports in terms of components molar/mass flows, molar/mass fractions, and phase wise. In Aspen Plus V9 when you create custom tables, then you cannot copy & paste or drag & drop the total mass/mole flow of result streams. For that user need to add property sets by using “Add Properties” option placed at bottom in stream results and search for MASSFLMX & MOLEFLMX. After adding property sets you can directly copy & paste or drag or drop to custom tables. Keywords: Custom Tables, Total Mass Flow, Add Properties, MASSFLMX, MOLEFLMX References: None
Problem Statement: How do I convert true electrolyte approach to the apparent approach?
Solution: An example showing how to convert true approach to the apparent approach using RStoic is attached. Apparent to true conversion goes automatically in Aspen Plus since the true component approach recognizes apparent components. Local property switching to true species can be specified for blocks or flowsheet sections. When converting from true species to apparent species, complications may arise due to the fact that a given ionic species could be generated by several molecular species. Starting in Aspen Plus V8.4, Aspen Plus will attempt to convert true components to apparent (see knowledgebase document 56815). To guarantee the proper recombination of ionic species for use in the apparent approach, an RStoic block should be used to fully define the system This is necessary because there may be multipleSolutions to determining the list of apparent components from a given stream in true components. In this example, a Decanter serving as a neutralizer separates out the aqueous from the organic layer. The Decanter block must use the apparent component approach. For more information about modeling electrolytes and liquid-liquid-equilibrium (LLE) seeSolution 4402. The aqueous layer is then going through an evaporator (Flash2) to precipitate out the salt by removing some water. This block must use the true component approach. Upon removal of the salt by a Sep block, the concentrated liquor is sent back for recycle. However, since the Decanter must use the apparent approach, a dummy RStoic block must be used to convert the stream back to apparent form before this stream enters the decanter. Keywords: None References: None
Problem Statement: Frequently Asked Questions for Plant View in aspenONE Engineering V8.2
Solution: 1. What does Plant View do? Plant View is a feature within Aspen Plus and Aspen HYSYS process simulators that allows the process engineer to view plant data side-by-side with model results. From within the Plant View flow sheet, you can point to a plant data server (running a data historian like IP.21) and map specific plant data tags against selected model stream variables and see how the plant is trending. You can view real-time, time-averaged or historical averaged data as well as data trends which help to facilitate operations support applications. Target customers for this product are those who regularly use models to troubleshoot plant operations. 2. What variables can be mapped to Plant Data Tags? Stream variables: Pressure, Temperature, Volume Flow, Molar Flow, Mass Flow, and Vapor Fraction (Flow relates to overall flow of stream not component by component. Other variables cannot be mapped at this time. The composition pie chart also only displays predicted data from the model; it does not display real-time stream composition. 3. Do stream results have to be present before entering Plant view? Yes. In Aspen Plus you need to run the model and have stream results present before you can enter the Plant View Environment. In HYSYS, if auto solve is on, you should be able to enter the Plant View environment because simulation results will already be present. 4. Can stream or unit operation data be manipulated in the Plant View environment? No. 5. How do I set up an IP 21 Process Browser and Data historian? You must first install IP.21 Process Browser. You can then point to a plant data server and start viewing data. IP.21 Installation Guide (with hardware and software Requirements) IP.21 Configuration Guide Compliance Guidelines IP.21 Process Browser and Plant View Quick Start Deployment Guide-Available upon request For more information about IP.21 Process Browser and IP.21 Process Data Historian, please visit the IP.21 support site at: http:// support.aspentech.com 6. For Plantview in V8.2, do you need an Aspen search server? Or is just IP.21 enough? You don't need a Search server. You need IP.21 Process Browser and a data source. The data source can be IP.21 or competitive data historians. 7. What is the form of the Plant View Data Source URL? You will need to enter the URL for the IP.21 Process Browser web server in the Source form of Plant View. The form of the URL is as follows: http://<servername>/web21/processdata/atprocessdatarest.dll 8. What are the security restrictions for setting up an IP 21 server and then linking it to Plant View? PI: Our Process Data for PI interface allows you to specify a PI user to use for the connection. It will have whatever privilege the user defined for the connection. No additional security other than using a specified PI user for the connection is provided. PHD: Depends on PHD user privileges. IP.21: IP.21 Security Settings are detailed in the installation and configuration guides for the IP.21 Product Family. 9. Is there a Quick Start Guide for Deployment of IP.21 Process Browser and Plant View? Yes. Please check the support knowledge base or contact us if you are interested. 10. Do I need to have Aspen Plus or HYSYS open to use Plant View? Plant View compares model results to plant data. It can only be accessed within the Aspen Plus or HYSYS simulators. This feature also uses MSC tokens. For it to work you need to have Token based licenses for the aspenONE MSC suite as well. 11. Can I push data back into the simulation from Plant View? At the moment there is no automated way to do this. However, you can take the current plant data and export it to Excel for further data conditioning if you need to. 12. Is there built-in steady state detection in Plant View? With High Performance Trends, you can export a summary of the tag information for your selected range of data. This includes the average value, the minimum, maximum, and the standard deviation. With this information a preliminary steady state analysis can be made for the purposes of data conditioning and reconciliation. 13. Can I access historical trends from Plant View? Within Plant View, when you map plant data tags and then hover over the mapped stream variables, you can see a preview of the historical trends plot depending on the type of data you are viewing (i.e. you will see a plot preview of real-time data if you have chosen the real-time data filter, same with time-averaged and historical averaged respectively). With V8.2 you can also access the full High Performance Trends Browser within the Plant View environment through the “Plant Trendsâ€� Button in the Plant View Ribbon. With this feature you can see detailed Plant Histories as well as plot multiple tags concurrently on the same High Performance Trends Graph. 14. Can Plant View be used with my OSI PI or Honeywell PhD data historian? Yes.  As long as you have an IP.21 Process Browser Web Server configured and linked to your historian, Plant view will work. For Further Questions, Concerns or Feedback: AspenTech Customer Support: http:// support.aspentech.com AspenTech YouTube Channel:  http://www.youtube.com/user/AspenTechnologyInc Product Management Resources: Product Manager for Plant View: Vidya Mantrala, [email protected] Product Manager for Aspen Plus: David Tremblay [email protected] Product Manager for HYSYS: Dinu Ajikutira [email protected] Product Manager for aspenONE: Simon Lingard MES Product Management: Lynn McMahon [email protected] Michael Harmse [email protected] Keywords: Plant View, Aspen HYSYS, Aspen Plus References: None
Problem Statement: Is it possible to pass an array to a procedure in Aspen SQLplus?
Solution: Yes, here is an example: procedure redimtest(param, nmentries int) local ndx int; for ndx = 1 to nmentries do write 'param['||ndx||'] = '||param[ndx]; end end local param1; redim (param1, 5); local ndx int; for ndx = 1 to 5 do param1[ndx] = 2*ndx; end redimtest(param1, 5); The query returns the following results: param[1] = 2 param[2] = 4 param[3] = 6 param[4] = 8 param[5] = 10 Keywords: datatype References: None
Problem Statement: How do I create a health investigation report? Health investigations allow you to generate reports based on one or more machine learning agents for a given asset, site or location, based on alerts associated with it. This can be used for live asset reports (for example, for performing an investigation after one or more alerts are triggered) or for historical events (to perform root cause analysis on historical failures).
Solution: 1. Open Aspen Mtell System Manager 2. Navigate to the Equipment tab in the ribbon 3. Select the asset you wish to create the report about 4. On the right in the Alert management sub section select Active alerts or Alert history If you select Alert History you may need to edit the Start Time and/or End Time and click Refresh to pull up older alerts. 5. Click on an alert from a machine learning agent and then click on Create Investigation to open the Health Investigation Report Wizard 7. Click Next in the Alert Selection screen of the of the Health Investigation Report Wizard 8. In the Properties section you can select the range of time to investigate 9. Click next and the Report configuration options will appear. 10. In this tab you can choose the title, sensor ranking, work items, probability, excursions, findings and corrective actions, you can also attach files. In any of these tabs you can click to generate the pdf report. To view or edit the report follow these steps: 1. Click the Equipment tab in the ribbon 2. Select the Asset you are interested in 3. In the Alert management section select Investigations. 4. Two tabs will appear, Active and Archived investigations. You can select any investigation and then select Edit Investigation to edit details and generate the report. From here you can also choose to archive or delete the investigation. Keywords: Agent alerts Agent report generated report edit details References: None
Problem Statement: How do I access session preferences in V8?
Solution: There are two ways that you can do this: 1. Open the File tab, click on Options and the preferences file will appear. Here you can select general options, property package warnings and save this preference file. 2. Inside a HYSYS simulation you can click on the Unit Sets Icon and you will access to the session preferences. Keywords: Preferences, unit set, V8, interface A References: None
Problem Statement: How do I change the Mach Number constraint in Aspen Flare System Analyzer (AFSA)?
Solution: To change the Mach Number constraint, select Scenarios from the Build section of the Home ribbon. Choose the scenario(s) for which you want to change the limit and click on Edit. In the Scenario Editor pop-up select the Constraints tab where you can edit the Mach Number limits for both Headers and Tailpipes. The changes will be reflected in the Scenario Input table Keywords: Mach, number, limit, constraint, multiple scenario edit References: None
Problem Statement: My Aspen Mtell application server and my plant are in different locations, can I change the timezone on my Aspen Mtell server to match the timezone the plant is in?
Solution: The Aspen Mtell server's timezone mirrors the timezone set on the computer it is installed on, so to change the timezone for your Aspen Mtell server follow the steps below. 1. Log into the Aspen Mtell server and right-click on the clock on the bottom right on the screen. 2. Select Adjust Date/Time (or similar for different Windows operating systems) 3. Select the desired timezone and close the Date & Time window. Note: It is important to ensure you change only the timezone on the server, and not the time. 4. Delete and re-add the Aspen Mtell Agent Service using the steps below i. Open Aspen Mtell System Manager and click on the Configurations tab > Agent Services ii. Click on the Stop Processing button iii. Click the Delete Service button iv. Follow the steps in KB: 96226 to re-add and restart the Aspen Mtell Agent Service. Keywords: Different time Different times Time mismatch References: None
Problem Statement: When I specify the driver power why is the compressor giving different cost than when I don't specify driver power ? ( Note- both cases compressor using 200HP )
Solution: Depending on the input data provided, the reciprocating air compressor model internally uses different compressor models to do the design/cost evaluation. If the driver power is specified, it is using the “Reciprocating Compressor [DGC RECIP MOTOR]” model. The reciprocating gas compressor includes other sub-systems like gear reducer, lube oil system etc. While when the power is not specified, it is using the “Single recip air compressor – 1 stage [EAC SINGLE 1S]”. The single 1-stage model is for a non-lubricated, packaged reciprocating compressor for oil-free air; includes motor and drive, coupling, base plate, cooler. The two models are different in many ways. That's why there are different costs/weights estimated. If you want a packaged unit you might consider using either the single 1-stage or single 2-stage compressor model or use the reciprocating gas compressor model. Keywords: Compressor, Reciprocating Compressor, Single Reciprocating Air Compressor, Reciprocating Gas Compressor References: None
Problem Statement: Tube material cost under “cost estimate” Shell & Tube Mechanical does not match with the cost updated in “Costing data base” for relevant tube material.
Solution: The tube costs in the program vary by tube OD and thickness. Since there is a large combination of tube ODs and thickness, the base cost entered is always for 19.05 mm OD x 16 BWG (1.651 mm thick). The program has its own algorithm to revise the tubing cost based on the actual tube OD and thickness entered. For example: 16 BWG & 19.05 mm OD (1.651 mm thk) is standard tube available. But user require 10 mm OD & 1 mm thickness. (The above snap is just to show the option of cost of the Tube/meter in Cost Estimate & inCosting Database Maintenance) Based on the user specified cost under costing data base, user needs to take care that the cost provided is not for the user required input but for the standard tube of 19.05 mm OD & 1.651 mm thk. Then Area ratio of that shall be applied in such a way that required cost would be reflected in Cost Estimate. If the user only has costing available for their tube, they can work out the cost / kg and then figure out how much a 19.05 mm OD and 1.651 mm thickness tube would cost per meter. Tip: Calculate the cross-sectional area of the tube: A = (Ao -Ai) Outside Area & inside Area, for the tubes, you can just cross multiply & will get the required cost. Keywords: None References: None
Problem Statement: . How does the 'Performance Slope' affect the stripper efficiency in the FCC?
Solution: . The 'Performance Slope' is a parameter that determines the change in the stripper efficiency with the steam/cat ratio for the FCC. The default number is 1. Along with the stripper efficiency factor, this parameter can also be used to fine tune the stripper response. A smaller number like 0.5 will reduce the effects while a number higher than 1 will accelerate the stripper response. This is an arbitrary factor that changes the slope of the stripper response. Key words. Catalyst Stripper Performance, FCC Keywords: None References: None
Problem Statement: How to activate debug logging for Aspen SQLplus Reporting
Solution: You will need to manually create two new levels of keys in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\AspenTech\InfoPlus.21\SQLplus and then control the logging using new string values. Specifically, create Logging and SqlPlusReporting registry keys and set the new string value (Errors, Interface, Steps) to ON, as seen below: [HKEY_LOCAL_MACHINE\SOFTWARE\AspenTech\InfoPlus.21\SQLplus\Logging\SqlPlusReporting] Errors=ON Interface=ON Steps=ON You must restart the TSK_SQLR external task (listed in Aspen InfoPlus.21 Manager) in order for the new logging controls to take effect. The log file is generated in the group200 folder (default location = C:\ProgramData\AspenTech\InfoPlus.21\db21\group200) with a file name SQLplusReportScheduler_username.log. Keywords: 128983-2 AtEmailDaemon RunReport Failed to run the automated report Failed to convert to Excel format The device is not ready Incorrect function Failed to run the report, check additional log file for more info References: None
Problem Statement: Why isn't the system burying my instrument signal wire? I chose Buried for Control cable placement in my Electrical Specs for my Project Basis, but when I choose the component Instrument electronic transmission wire under my Instrumentation Plant Bulks, I get no trenches? Why?
Solution: The control cable option does not apply to the instrument signal wire. We consider them two different things: Control cable: Low voltage electrical cable from MCC to a motor that controls the motor. Instrument signal wire: Carries electronic signal from a field instrument to a junction box in the field and from the junction box to the control center. For the instrument signal wire we do not have a buried option at the project level or for the plant bulk itself. But you could use the Electrical control cable runs (LV) under Plant Bulks | Electrical - General and choose the Underground cable duct component. Keywords: instrument signal wire, buried References: None
Problem Statement: How do you model a Gas-Solid Preheater with Reaction in a Cement-Clinker?
Solution: Attached is an example of a Single Stage Gas-Solid Preheater with Reaction for Cement-Clinker Production. This example will run in V8.8 and higher. A cyclone preheater is used in connection with a short rotary kiln to produce cement-clinker. Hot gas and dust from the kiln reacts with raw meal and false air in the preheater. A sensitivity analysis is performed on the reactor. Components The following components are defined in the simulation: Component ID Type Component name Alias CACO3 Solid CALCIUM-CARBONATE-CALCITE CACO3 MGCO3 Solid MAGNESIUM-CARBONATE MGCO3 CAO Solid CALCIUM-OXIDE CAO MGO Solid MAGNESIUM-OXIDE MGO N2 Conventional NITROGEN N2 O2 Conventional OXYGEN O2 H2O Conventional WATER H2O CO2 Conventional CARBON-DIOXIDE CO2 COAL Solid CARBON-GRAPHITE C SOLID1 Solid SILICON-DIOXIDE SIO2 SOLID2 Solid SILICON-DIOXIDE SIO2 CLINKER Solid SILICON-DIOXIDE SIO2 Physical Properties Properties for the material stream are computed using Ideal properties using the SOLIDS property method. Molecular weights and tabular enthalpies are entered for coal, solids, and clinker using TABPOLY. Entropy and density are not calculated because of insufficient data. Unit Operation Models The preheater is modeled by a MIXER block and an RSTOIC reactor. Raw meal, kiln gas, and false air are mixed together and fed to the reactor. A FORTRAN block sets the flow rate of false air to 2.5% the flow rate of kiln gas. Stoichiometry and extent of reaction are entered for the reactor. Another FORTRAN block sets the reaction conversions as functions of preheater temperature. The cyclone is simulated by ASPEN PLUS's SSPLIT model. The products of the preheater reaction are separated into a gas stream and 2 solid streams (meal and dust). Each of these streams is sent to a separate HEATER block. A FORTRAN block sets the temperature of the gas stream to the preheater temperature. The solid streams are cooled to 28 C. Finally, the gas and dust are mixed into one stream. Process Specifications The following conditions are specified for this model: Feed stream temperatures, pressures, flow rates, and compositions Mixer pressures Heater temperatures and pressures Stream splitter fractions The model predicts the following: Product stream flow rates and compositions Temperature and pressure profiles Heat duties Potential Applications A sensitivity analysis was performed to study the effect of preheater temperature on reaction conversion. With this information it is possible to optimize the production of cement-clinker. Keywords: None References: None
Problem Statement: This knowledge base article describes how to enable debug logging for an Aspen Process Data connection.
Solution: 1. Debug logging for an Aspen Process Data connection can be enabled using the ProcessDataAdministrator.exe. The ProcessDataAdministrator is located in one of these directories: 32-bit Aspen software installations: C:\Program Files (x86)\AspenTech\ProcessData 64-bit Aspen software installations: C:\Program Files\AspenTech\MES\ProcessData If both executables are present the correct one to use depends on the bitness of the application being tested. One way to determine if the application is 32-bit or 64-bit is to go into the Windows Task Manager and in the Details tab add a column (if it is not present) called Platform. That will display the bitness for each running process. 2. Note - the first tab that appears when the ProcessDataAdministrator.exe starts is the Data Sources tab. Although it may appear that a data source needs to be selected this is NOT true. Logging will take place even if no data source is designated. 3. In the Logging tab select all of the flags for each of the components to log for 'Data Servers' and for any other components suggested by AspenTech Software Support. Do not select 'Process Data' unless it is specifically requested. Click 'Apply' after you have selected the flags for each component to log. 4. Start the client application which uses this Process Data Connection (e.g., Aspen Process Explorer) then make the client application request data from the server or perform any other action that will generate a call to the server. 5. Once data has been collected the debug log files will be created in different directories according to the type of logging selected: C:\ProgramData\AspenTech\DiagnosticLogs\ProcessData Data Servers REST Service .Net Service Windows Service mMDM ProcessData TagBrowser ProcessData .Net ProcessSubscriptions Subscription Servers IP21 Records (SPC, KPI, Profile) AddIn - ProcessData AddIn - APRM AddIn - IP21Configuration Infobus Service Web - ActiveX C:\ProgramData\AspenTech\DiagnosticLogs\SharedComponents ADSA Locator License Component Email Component C:\ProgramData\AspenTech\DiagnosticLogs\Aspen Calc Calc - Scheduler Calc - Component Calc - History C:\ProgramData\AspenTech\DiagnosticLogs\ProductionExecutionManager APEM - ODBC 6. When finished, the debug logging should be turned off. On newer versions of the product the 'Turn OFF all logging flags' button may be used to disable logging. If that button is not present then uncheck all of the flags for each component which has been logged. Click 'Apply' each time this is done for each component. Keywords: pdadmin 121903-2 References: None
Problem Statement: Why are separate development and production environments recommended in Aspen Mtell??
Solution: By following best practices for maintaining separate Development and Production servers, you can potentially Avoid the risk of the production server going down. Leave the production system and data clean and safe. Test and experiment with upgrades without risking the production environment. Test Windows patches before applying them on the production environment. Create and test agents in the Test environment during project execution and transfer only good agents to Production. Promote efficient use of Mtell. Backup an Mtell SQL database from each environment. The recommended best practice is to host two environments: production and development/test. Test critical actions on the dev/test environment before moving the actions to the production environment. Sync the production database with development every quarter or before a version upgrade. Refer to the following diagram: There are two options for agent deployment during project execution: 1. Deploy in bulk: Complete all agent development on the development/test server. Backup the Mtell SQL database and restore it on the production server to go live. (One export at the end of the project.) 2. Deploy as you go: Create agents on the development/test server. As agents are ready to deploy, review, approve, and export to production. (Export as you go.) Likewise, there are two options for agent deployment post project: 1. Incremental development on production system: Create and deploy new agents directly on the production server. 2. Incremental development on test system and migrate: Create agents on the development/test server. As agents are ready to deploy, review, approve, and export to production. Keywords: Agent Builder System Manager Test environment Production environment Database Architecture Dataflow Data-flow Data flow References: KB 000062400: How to transfer a Failure Agent from one Mtell database to another Mtell Database
Problem Statement: How do I get heat tracing on my pipe?
Solution: Heat tracing for a pipe is turned on by choosing the type tracing you would like done from the Special Pipe Description field: Keywords: heat tracing, heat, tracing, special pipe description References: None
Problem Statement: Why am I getting the Warning message, “Percent of Active Brick to be Specified”?
Solution: Typically, this is because someone has changed the setting “Fieldbus short circuit Protec” from the default value of “No” to “Y” (Yes). This causes each of your area values for Percent Active Bricks to be changed from 0 to 100. The message is letting you know that if you want it to be something other than the new 100 percent value, you will need to specify it. You can see this if you check the instrumentation in your areas. The 2nd field from the bottom is Percent active bricks. If you click on it you will see an explanation in your properties window. Keywords: Active Brick, Active, Brick, Instrumentation, Fieldbus, short circuit, short, circuit References: None
Problem Statement: How to delete or scan a specific tag from A1PE search through aspenONE Process Explorer Admin
Solution: Open AspenONE Process Explorer Admin Click on the “Tags” tab On option 1. Select a Data Source choose the database that contain the tag or tags that you want to delete or scan. On option 2. Specify how to scan your tags: you have 4 options; All tags means that it will scan or delete all the tags created on the Data source selected above Tag Name means that you can scan or delete one or several tags by using the name of each tag. IP.21 Folder means that your can scan or delete all the tags that are inside an specific folder by typing the name of that folder. Wildcard (*) means that you can scan or delete all the tags that contain the parameter that you are giving, for example if you write atc* and you have tags named: atcai, atcl101, atcl102 it will scan or delete all these tags. On option 3. Type the name of the tag or folder (depends on option 2) that you want to scan or delete and click on Add or hit the enter tab. Then click on Scan Tags or Delete Tags button. Keywords: Delete Tags Scan Tags A1PE search A1PE admin References: None
Problem Statement: How to browse customized (non-standard) tags in the Aspen InfoPlus21 OPC-DA Server?
Solution: Aspen InfoPlus.21 OPC-DA server based in a .NET Software Development Kit (SDK) provided by the OPC Foundation. The InfoPlus.21 OPC-DA server has passed the OPC Foundation compliance tests. Also, the makes use of the Aspen InfoPlus21 branch record features that make it possible to reduce browsing time by OPC-DA clients. Aspen InfoPlus21 OPC-DA Server exposes the same records that are exposed by the IP.21 Administrator in the upper-level Tags branch of the tree control. The items in this branch are defined in a branch record named IP_TagsBranch. As distributed, IP_TagsBranch lists three definition records in its repeat area: IP_AnalogDef, IP_DiscreteDef, and IP_TextDef. Users can add additional definition records to the IP_TagsBranch record to make them available. The Aspen InfoPlus21 OPC-DA server exposes standard OPC properties (e.g., value, time, quality, engineering units, description) that are owned by the tag record. The OPC-DA will obtain the mapping from an AtMapDef record. The MAP_DefinitionRecord field is used to associate each AtMapDef record with the definition name for the IP.21 tag. For example, the map record IP_AnalogMap has IP_AnalogDef specified in its MAP_DefinitionRecord. Keywords: OPC References: None
Problem Statement: How do I turn on Data Lookback in Aspen Mtell?
Solution: Data Lookback is used when you have a tag or tags that enter(s) the historian after a delay; it enables the Agent Service to look back within the time period set for tags that may have entered after its last run. When Data Lookback is turned on for one tag it is turned on for the entire equipment set. To turn on Data Lookback follow the steps below. 1. Open Aspen Mtell Agent Builder and click on the Machine Learning tab. 2. Select the equipment set you are working on and then click the Sensor Mappings tab. 3. Right-click on the tag you would like to turn on Data Lookback for and select Edit. 4. On the Select Sensor Mapping for Sensor Role screen, enter the length of lookback you require in the Data Lookback field and choose a unit of time. Note: The data lookback must be a multiple of the TDS's granularity. For example, if you have an hourly TDS, your data lookback should be 1 hour, 2 hours, 3 hours, or another multiple of 1 hour. 5. Click Re-import and Retrain. Note: If the only thing changed on the Select Sensor Mapping for Sensor Role screen was Data Lookback then the Re-import and Retrain button will only save the Data Lookback value, the agents will not be retrained. Keywords: Data lookback Date look back Lookback Look back Delayed tags Late tags References: None
Problem Statement: This Knowledge Base article provides steps to resolve the error unknown error = -1 which may be encountered in the Aspen InfoPlus.21 (IP.21) Administrator. The symptoms leading to the above error message are as follows: the IP.21 Administrator becomes slow in responding or stops responding completely, and may time out with an unknown error = -1 or do retry.
Solution: This behavior has been observed on a few occasions and what was found was that another Aspen product, such as Hawk Agent, or a third party product was using a large number of Operating System handles (1,000 +), thus preventing a response from the Aspen InfoPlus.21 Administrator. One can check for this in the Windows Task Manager, under the column Handles. This column is not displayed by default, so one should use the menu choices View -> Select Columns and click on the Handle Count option to see if there's a particular program that may be using a lot of handles. Once one finds a program that's using a large number of handles, the program can be stopped. This should make the Aspen InfoPlus.21 Administrator operational. At this point one can conduct troubleshooting procedures to resolve the problem in the offending program. On several other occasions when the unknown error = -1 or do retry was encountered, a restart the Aspen InfoPlus.21 Task Service and then restart of the InfoPlus.21 Administrator resolved the problem too. Keywords: Unknown error do retry 122573-2 References: None
Problem Statement: How do I disable the activated analysis dashboard in Aspen HYSYS V8.8?
Solution: The Activated Analysis Dashboard is designed to allow users to analyze plant economics, plant energy savings and detailed heat exchanger designs. Due to the engineering benefits of the dashboard we do not recommend removing the activated analysis dashboard. However, to provide more flow sheeting space to the user we do offer the option to remove the Activated Analysis Dashboard. The activated analysis dashboard can be deactivated through the ‘disable activation dashboard’ function found within the Start| Options| Simulation section of Aspen HYSYS. A screenshot of this shown below: Keywords: Activated Analysis, HYSYS References: None
Problem Statement: How do I properly initialize my recycle unit operations on Aspen HYSYS V8 to show the petroleum properties of my streams using an already defined assay from other stream?
Solution: Verify that the petroleum properties on your current recycle outlet streams show an <empty> value, on this example we will use the Asphaltene Content (Petrol) [%] property as one of our Petroleum properties variables we want to display on our streams: Go to the Home tab and put the simulation On Hold and ignore the recycle operations: Go to the Parameters tab and select Convergence, check the box of Initialize Empty Petroleum Props, after that you can click in the ignored box to enable the recycle calculation again: Go to the outlet stream of each recycle operation you have on your case and press the Define from other stream button and select a stream with Petroleum properties, then disable the checkboxes for stream conditions, composition and flow. Click OK and repeat as necessary for remaining recycle operations: Set the solver to Active and we will have the petroleum information for each stream inside your case: Keywords: Recycle, Petroleum, Properties, <empty> References: None
Problem Statement: What is the best way to view complete PFD in Aspen Hysys V8 version?
Solution: Please close Analysis Window as well as Messages Window as per below screenshot In Simulation Environment on Ribbon Toolbar please click on View then click on Zoom to Fit Keywords: PFD View, Zoom to Fit, PFD window etc; References: None
Problem Statement: User subroutine compiled with Compaq complier does not work in V 2006.0 or later
Solution: Aspen Plus 2006 or later versions are based on the Intel Fortran 9.1 compiler. This is a change from the version 2004.1 and earlier versions of Aspen Plus, which used Compaq Visual Fortran instead. Aspen Plus has moved away from Compaq Visual Fortran because this compiler is no longer supported by its manufacturer and may be difficult for some customers to obtain. If you used the Compaq Visual Fortran compiler previously, please be aware of the following issues in upgrading Aspen Plus and/or the Intel Fortran compiler: ? Object files (.OBJ) and static libraries are not compatible between Compaq and Intel compilers. Use DLLs (dynamic or export libraries) for maximum compatibility between code compiled with different compilers. READs and WRITEs to Fortran I/O units opened by code compiled by a different compiler will not work. Aspen Plus opens its pre-defined units (such as the history file and the control panel) using the Intel compiler, so any code compiled by the Compaq compiler will no longer be able to write to these units. Ideally you should move to the Intel compiler and recompile any object files from their source code using the new compiler. If this is not possible consider following different scenarios: Scenario 1: When using a different Fortran compiler than Aspen Plus was compiled with ( For example Aspen Plus compiled with Compaq Visual Fortran) WRITE statements attempting to write to files opened by Aspen Plus fail to write to the files because the I/O libraries between the two compilers are not compatible. Both Compaq and Intel Fortran compilers write to fort.## files in the current working directory in these situations. The crash occurs when the compiler tries to reopen a fort.## file which is still open from a previous run.Solution The writes can be accomplished by calling functions in Aspen Plus to perform the writes. To do so: Include the following (beginning in column 1): #include ppexec_user.cmn Define a character string as a buffer to write the message to (for this example, a two-line message): CHARACTER*256 BUFFER(2) Use a Fortran internal write to write the message to the buffer: 2000 FORMAT (LINE 1,/,LINE 2) WRITE (BUFFER, 2000) Call DMS_WRTALN to write one line at a time to the History File. CALL DMS_WRTALN(USER_NHSTRY,BUFFER(1)) CALL DMS_WRTALN(USER_NHSTRY,BUFFER(2)) Note: Use USER_NRPT rather than USER_NHSTRY to write to the Report File. Scenario 2: You don't have source code, you have only .dll and DLOPT file available compiled and lnked using COMPAQ/INTEL FORTRAN versions. Moreover, you have aspen plus versions such as 2004, 2006, V7.1 installed in your machine. You might be interested to run user subroutine compiled with COMPAQ for 2004 or earlier and with INTEL for 2006 or later. Solution 1) Sort out all of your .dll and DLOPT files created using INTEL or COMPAQ compilers. Place in different folders. 2) Create an user environmental variables by going to Settings ll Control Panel ll System ll Advanced ll Environmental Variables. Click New and edit the name (e.g.;MY_ENV) and value based on where you want to locate. Modifiy the DLOPT FILE path name as %MY_ENV%\ *.dll. Set in linker settings as %MY_ENV%\*.dll Whenever you are trying to run .DLOPT file created in different versions, you need to edit user value of environmental settings: such as modify MY_ENV as: C:\Documents and Settings\islamm\Desktop\CASE\2004 Or C:\Documents and Settings\islamm\Desktop\CASE\2006 Or C:\Documents and Settings\islamm\Desktop\CASE\V7.1 Keywords: *.Dll, DLOPT, %MY-ENV% References: None
Problem Statement: When a value of greater than 1 is entered as a stream component composition, Aspen HYSYS returns a warning saying 'Number is outside allowable range'.
Solution: When provided with compositional data that is in percentage, sometimes there might be a need to enter values which are greater than 1, knowing that eventually Aspen HYSYS will normalize the values and ensure the sum total equals 1. In Aspen HYSYS V8.0, it is not possible to input a single value greater than 1, without getting the error message shown below: This is functionality that is now available in V8.2. In V8.2, even if your input is greater than 1, Aspen HYSYS will accept the value and change it to 1, without showing the warning. The sum of your composition will still be normalized, this is still an Aspen HYSYS capability in all versions. Keywords: Number is outside allowable range, input composition References: None
Problem Statement: In Aspen Calc, in View | Options, get an error when trying to add a new node: Failed to connect to server < servername > : Permission denied.
Solution: 1. Using dcomcnfg, verify in Default Properties that Enable Distributed COM on this computer is checked. If not, check it and restart the Aspen Calculator Engine service. To use dcomcnfg, go to Start | Run and type dcomcnfg. When the Component Services window opens, expand the Component Services option, then expand the Computers option, right click on My Computer object and select the Default Properties tab. Verify that Enable Distributed COM on this computer is checked. 2. You can also log-in to the remote client using the user id that is used to run the Aspen InfoPlus.21 Server services. 3. Alternatively you can also include your user name in the Administrator account of the AspenInfoPlus.21 Server System to access from the remote AspenCalc Client. Keywords: permission denied Aspen Calc References: None
Problem Statement: When attempting to restore a database in SQL Server Management Studio (SSMS), a user might get the following error message: System.Data.SqlClient.SqlError: The sp_configure value 'contained database authentication' must be set to 1 in order to restore a contained database. You may need to use RECONFIGURE to set the value_in_use
Solution: This error message will pop up if the database being restored is contained, while the instance of SQL server has Contained Database Authentication turned off. When Contained Database Authentication is off (set to 0) for an instance, contained databases cannot be created, restored or attached to that Database Engine. If you would like to restore a contained database, follow the steps below to turn on Contained Database Authentication. 1. Click on New Query (1) in SQL Server Management Studio 2. In the new query window (2), type in the following script: sp_configure 'contained database authentication', 1; GO RECONFIGURE; GO 3. Click Execute (3) to run the Script and you should see a similar output as the image below. 4. Proceed to restore the database. Keywords: DB Restore Database restore Restore failure SQL SSMS script Contained DB Contained database CDBA CDA References: None
Problem Statement: When installation prerequisites indicate that MSMQ (Microsoft Message Queuing) is needed for a particular product, how many components of MSMQ are needed? MSMQ components are: 1. Message Queuing Server 2. Directory Service Integration 3. Message Queuing Triggers 4. HTTP Support 5. Multicasting Support 6. Routing Service
Solution: Unless additional, more specific, requirements are listed the default option (Message Queuing Server) is sufficient, as illustrated in the following screenshot: Windows Server Windows 10 Open Control Panel > all control panel items Click Programs and Features, on the left hand pane, click Turn Windows Features on and off. Expand Microsoft Message Queue (MSMQ) Server, navigate to Microsoft Message Queue (MSMQ) Server Core and expand it , select the check boxes for the following Message Queuing features to install: Click OK. Keywords: None References: None
Problem Statement: Aspen Solr Core Scheduler is unable to save passwords containing non-supported characters. User gets the following error message when trying to save a Job: Exception: Could not parse Received Configuration. This knowledge base article contains a list of supported and unsupported characters.
Solution: The following characters are not valid password characters: &< The following characters are valid password characters: !@#$%^*()_+-={}[]~`:;',./>? abcdefghijklmnopqrstuvwxyz ABCDEFGHIJKLMNOPQRSTUVWXYZ Keywords: VSTS 548670 References: None
Problem Statement: How do I sort (re-order) the components in a component list in Aspen HYSYS V8?
Solution: If you wish to re-order or sort the component list, simply click on the component you wish to re-order and drag it to its desired in the list. If you used V8.4, please make sure that you have installed HYSYS V8.4 CP1 or above. Keywords: sort component, re-order component, component sequence, component order etc References: None
Problem Statement: When I try to run the DMCplus example supplied with Aspen Plus Dynamics, I get the following error message: Procedure precall failed for pDMCplus DMCplus 2006.5 is correctly installed, and working correctly.
Solution: The problem is caused by two missing dynamic libraries which are not installed automatically in the correct folder. The workaround is to copy manually the files xmlparse.dll and xmltok.dll from C:\Program Files\AspenTech\APC\Online\bin to C\Program Files\Common Files\AspenTech Shared. This problem is fixed in more recent versions of DMCplus. Keywords: References: None
Problem Statement: In Aspen HYSYS V8.8 and V9 the valve manufacturer and ANSI-ISA valve type can not be selected, while in V8.6 and prior versions, this selection was available. Why?
Solution: In pre V8.8 versions, the valve sizing/method options were mis-categorized. There are basically two sizing methods: - Fisher Universal - ANSI/ISA In the pre-V8.8 versions, with each of the above selections you also had another menu for selecting valve manufacturers as a sub-selection. This was wrong. These selections should not be a subcategory of the above two options. They are separate models with separate equations. Also, ANSI/ISA uses its own unique equation, making the valve manufacturer menu essentially obsolete. Keywords: ANSI-ISA, valve manufacturer methods References: None
Problem Statement: Users may receive the following message when trying to edit Aspen Calc formulae: Failed to edit calculation. Not authorized to create, modify, delete, copy or rename of any type of calculation on this node. How can this be alleviated?
Solution: Check the following things: 1. On the InfoPlus.21 machine open up the Services applet and look for a service called AFW Security Client Service. Get the properties for it. Is it being started by a local account, or the local system account? If so, change it to be a domain account that is a member of the local administrators group on the machine where the service resides. Once the change is made stop any Calc instances that are running and then stop and restart the AFW Security Client Service. Finally, restart Calc and see if the message goes away and if modifications can be made. 2. Beneath '\Program Files\AspenTech\Aspen Calc\Calc' there needs to be an Edit folder. Without it edits are not possible. 3. Does the %ASPEN_CALC_BASE% environment variable exist? If so, does it point to the proper location? 4. Check the settings in DCOMCNFG (Start => Run => dcomcnfg). If they are are not already set as follows then make these adjustments: --Locate the 'My Computer' icon. Right-click on it and choose 'Properties'. Find the 'Default Properties' tab --Set Default Authentication Level => 'Connect' --Set Default Impersonation Level => 'Identify' Keywords: References: None
Problem Statement: How to register an extension for Aspen HYSYS V8.0 and later?
Solution: Both the EDF file and the VB DLL have to have same name, they have to be in the same directory when user try to register the extension. To register an extension, Step 1. To register an extension, you will have to create a folder and put both your dll and edf file into the following directory. C:\Program Files (x86)\AspenTech\Aspen HYSYS VX.X (software current version)\Extensions Step 2. Open Aspen HYSYS (If you have Windows 7 machine, you will have to run Aspen HYSYS as an Administrator.) Step 3. Go to Customize->Register Extensions Step 4. Press “Register an Extension..” to locate the dll or edf file, and then press “Open”. A window will pop up and tell us if the extension is registered successfully or not. If the extension is registered successfully, you will be able to see it from the extension list on the above dialog box. Keywords: Extension, register, registration, association References: None
Problem Statement: Why is the valve resistance equation different in V9 and V10?
Solution: In Aspen HYSYS V9, there was a typo in the resistance equation shown on the valve. This was corrected in V10. The correct equation is shown below. where: Q: flowrate (kg/h) k: constant (kg/hr/sqrt(kPakg/m3)) Vopen: valve opening fraction dP: pressure drop in the system (kPa) Density: upstream density (kg/m3) Eventhough the equation was erroneous in V9, the coded equation was correctly implemented. Hence, the results are not affected. Keywords: simple resistance, equation, valve References: None
Problem Statement: What is the difference between the PSV sizing functionality in Aspen HYSYS V8.3 (or higher) and Aspen Flare System Analyzer?
Solution: There is a great difference between these functionalities. The PSV sizing feature in Aspen HYSYS allows users to size a relief valve by defining design temperature, set pressure, valve type, constant superimposed back pressure and relief scenario. Aspen HYSYS will then calculate orifice area based on the reliving flow defined by the user or based on the capacity of the valve. The PSV sizing feature in Aspen Flare System Analyzer (AFSA) allows users to determine Rated Flow and Critical/Subcritical condition of the relieve valve. AFSA does not calculate orifice area. Users can either define orifice area or select the orifice type from the built-in API orifice library which will report the corresponding orifice area. Other difference is that in HYSYS, users have to create a single valve for every stream. In Aspen Flare System Analyzer users can select the number of valves included in a single valve. The sizing methods options available in Flare System Analyzer are: 1. API_1976: American Petroleum Institute methods in the 1976 edition of RP 520 pt1. No account is made of liquid flashing as it passes through the relief valve, thus this method is not recommended for either two phase or flashing fluids. 2. API_1993: American Petroleum Institute method in the 1993 edition of RP 520 pt1. Liquid flashing is handled by a simplified approach in which the fluid is flashed to the outlet pressure. The relative quantities of each phase at the outlet condition are then used at the inlet of the valve to determine the two phase capacity. 3. API_2000: American Petroleum Institute method in the 2000 edition of RP 520 pt1. This method is often referred to as the Diers or Leung method. This is the recommended method for all two phases fluids. 4. HEM: Homogeneous Equilibrium Method. The sizing method options available in HYSYS PSV sizing are: 1. Latest edition of API RP 520 8e and API RP 521. HEM (direct integration through isentropic nozzle flow) is also supported. API 526 flanged orifices are provided. 2. ASME VIII 3. PD 5500 4. EN 13445 Furthermore, Aspen HYSYS PSV sizing is focused on determining orifice area while Aspen Flare System Analyzer is focused on modeling flare network. Keywords: PSV Sizing, Aspen Flare System Analyzer, Orifice Area References: None
Problem Statement: In the Fire Semi-Dynamic Flash calculation method in safety analysis how is the required relieving mass flow rate calculated?
Solution: The methodology for the semi-dynamic flash is documented clearly with in the Aspen HYSYS On-Line Help under the Fire Relief Load Calculations. In version 8.6 and below HYSYS calculates the relief load by maximizing the Vapor Mass Flow Rate. The calculated parameters are shown in the flash table through the edit flash table feature. Figure 1. Edit Flash Table in v8.6 In Aspen HYSYS version 8.8, the flash table has an extra column showing the calculation of the orifice area. HYSYS determines the required orifice area for relief load using the following equation: In version 8.8 HYSYS now maximizes the Orifice Area and uses the corresponding vapor mass flow to calculate the orifice area. Figure 2. Edit Flash Table in v8.8 Keywords: Flash Table, Safety Analysis References: None
Problem Statement: I imported a variable in to a spreadsheet but I cannot add this to my case study using the drag and drop method.
Solution: The drag and drop method is the quick and easy method to organize key inputs and results in a spreadsheet from the HYSYS simulation. The data, however, cannot be imported to a case study following the similar drag and drop method. This is a known issue in the new GUI for HYSYS V8.0 and V8.2. This has been fixed in Aspen HYSYS V8.3 and newer versions (Ref: CQ00512675). The workaround is to select the Add button in the case study to import variables from the spreadsheet. The HYSYS users are recommended to upgrade the HYSYS to V8.3 or newer version where is GUI has been improved and this issue has been fixed. Keywords: Spreadsheet, Case Study References: None
Problem Statement: If you have recently received a copy of Aspen HYSYS V8.3 and would like to upgrade from V7.3 to V8.3 then follow the simple steps below.
Solution: Before upgrading if you are connecting to SLM Server V7.3 then you will need to upgrade to SLM Server V8.3 so that HYSYS V8.3 can obtain a license otherwise it will not be able to obtain a license. Please make sure you back up your usage logs on the license server if you are carrying out an SLM Server upgrade. If you are using a Standalone license then you can install install HYSYS V8.3 without any problems. Step 1: Insert the SupplementalDVD in your computer drive. Here is what folders you will see. Please note if the DVD does not Auto Play then it means your Operating System does not have this feature enabled. Refer to thisSolution to enable Auto Play - 137117 Step 2. Run the setup.exe which will only install the SLM Patch. Step 3. Double click on the Engineering folder and then click Double click on Full Product Installs folder Step 4 - Once you open up the folder you will then need to Right Click on Setup.exe and Click Run as Administrator. Here is an example. Step 5 - Now you should see Aspen Installer loads up and you will have few options to choose from. Please Note you must keep the radio button selected as a 32bit OS even if you are using a 64bit OS. Aspen HYSYS is a 32bit application but it is compatible with 64bit OS. In this step all you need to do is select Install aspenONE Products Step 6 - Read and accept the software agreement. Step 7 - Install Type - In this step we have two options Typical Install or Custom Install. A typical install will go ahead and install the following programs: · Aspen Plus V8.2 · Aspen HYSYS V8.3 · Simulation Service V8.2 · Aspen Version Comparison assistant · Aspen PIMS (includes Aspen PIMS Platinum) Here is what you get with a Typical install. Custom Install It's recommended to choose a custom install if you only want to choose a specific program to install. For example if you have only HYSYS V7.3 installed and you only want to install HYSYS V8.3 then a custom install is recommended. Here is what you get with a Custom install. Step 8 - Software Licensing - In this step you can choose if you are using a network license or a standalone license. This step is very simple. If you are using a network license then just type in the license server name and then click add and then proceed to the next step. If you are using a Standalone license then click the browse button and select the license you are using. Step 9 - Summary - In this screen you will see a summary of the applications that will be installed. For the purpose of this knowledge baseSolution I have only selected HYSYS. All you need to do now is click the Install Now button and then wait for the application to install. Keywords: upgrade, migration, installation, supplemental References: None
Problem Statement: How to customize PFD Flyby (Tool Tips) in Aspen Hysys V8.4?
Solution: PFD Flyby/Tool Tips can be customized by going to File | Options | simulation page | tool tip section there is a check box show flowsheet flyby, next to it there is a button called specify fly by, when you click that button you have the dialog to customize the flowsheet flyby per object type. Keywords: tool tips, customize, pfd References: None
Problem Statement: When trying to import the
Solution: status of a unit of operation into a spreadsheet, the following common procedures fail in Aspen HYSYS V8 versions, such as V8.4 and V8.6: 1. TheSolution status of a block is not accessible from the Variable navigator. 2. Dragging and dropping the Ignored check box in the unit of operation into a spreadsheet. This is now available in V8.8. 3. The status of Recycle and Adjust blocks can be filtered in the Flowsheet Summary option, but this cannot be imported. 4. The status of Adjust blocks can be seen in the Adjust manager, imported into a Spreadsheet, but this will only solve the units if multiple blocks are used with SimultaneousSolution method.Solution The user can access the block status in the Workbook, ‘Unit Ops’ tab. Click in the icon in the Home ribbon: Check the Ignored column in the Unit Ops tab, as well as the Calc. Level. You can drag the Ignored check boxes into cells in the spreadsheet by dragging and dropping. Remember to click on the Spreadsheet window, before dragging variables from another form displayed in the screen. The code is 0 for Not ignored and 1 for Ignored. You can also check the calculation levels, and import these variables. Keywords: Unit Operations, Spreadsheet, Ignored, Status, Workbook, Calculation level References: None
Problem Statement: How to modify the Calculation Levels in V8?
Solution: According toSolution #109122 you can modify the order in which the objects in your flowsheet are calculated. To modify the Calculation Levels in V8.0 use the Calculation Order box in the Home tab of the HYSYS ribbon. It is in the bottom-right corner of the Solver section. Keywords: calculation, level, order, operation References: None
Problem Statement: Why are the color fields empty in the strip chart legend for Aspen HYSYS V8.0 through V8.3?
Solution: The colour moniker for the strip charts legends was not implemented in the new GUI for Aspen HYSYS V8.0 through V8.3. This gives the legend empty colour fields in the strip chart. The legends are correctly implemented in Aspen HYSYS V8.4 (Ref CQ00508610). Aspen HYSYS users are recommended to upgrade to this version. Aspen HYSYS V8.4 shows the legends correctly as shown below. Keywords: Strip Chart, Colour Legend, color References: None
Problem Statement: How can I feed the same stream to two different unit operations in Aspen HYSYS V8.0 and higher?
Solution: By default Aspen HYSYS doesn't allow you to do this but the preference can be changed to allow multiple stream connections. Go to File|Options|Simulation|General Options page and check the box for ‘Allow multiple stream connections.’ You can then feed your material stream to more than one unit operation. Keywords: Stream, Unit Operations, Allow Multiple Stream Connections References: None
Problem Statement: Are there any tools available to help me decide which property package to use in my simulation? For the new user interface.
Solution: In the properties environment, the Property Wizard is available from the Home ribbon bar tab as shown in the figure below: The Property Wizard can be used to generate a list of potential thermodynamic models based on some general process information provided by the user. Note that detailed information for each of the different property models can be found in the Aspen HYSYS Simulation Basis manual. A link to all product documentation can be found on the left pane of the Aspen support website. Keywords: property, package, wizard, tools, model, thermodynamic, assistant References: None
Problem Statement: How do I resize a table in Aspen HYSYS V8.6?
Solution: You can generally adjust table size by changing size under Format tab on the top. After picking a larger number, you can find that the word size and table size will increase. Keywords: Size the table References: None
Problem Statement: How does Aspen HYSYS 2006 OLE registration changes impact the current usage of Aspen HYSYS via OLE?
Solution: The impact of changes in Aspen HYSYS 2006 OLE registration are summarized in the table below: User?s application (that uses Aspen HYSYS via OLE) Written in VB Written in C++ If you make no change to the application You will get HYSYS 2006 if that is the last registered. If you run version 2004.2 or older after that, then that is the one that will get returned You will get Aspen HYSYS 2006 if that is the last registered. If you run version 2004.2 or older after that, then that is the one that will get returned If you recompile your application with the latest HYSYS Type Library (from Aspen HYSYS 2006) You will get Aspen HYSYS 2006 if that is the last registered. If you run version 2004.2 or older after that, then that is the one that will get returned You will get Aspen HYSYS 2006 as long as it is registered. If you modify your application You can make use of the new ProgIDs (please refer toSolution #119950) to modify your application so that it best suites your work-flow e.g. you can hard-code your application to only work with HYSYS.Application.2006, or you can create a user interface which allows the user of your application to choose which version of Aspen HYSYS would they like to work with. You can make use of the new ProgIDs (please refer toSolution #119950) to modify your application so that it best suites your work-flow e.g. you can hard-code your application to only work with HYSYS.Application.2006, or you can create a user interface which allows the user of your application to choose which version of Aspen HYSYS would they like to work with. In C++, you can use the CLSIDFromProdID function available in Windows API to achieve this. Keywords: VB, Visual Basic, C++, OLE, version, HYSYS Type Library, HYSYS.Application References: None
Problem Statement: How to Export Workbook results to Excel in Aspen Hysys V8 version?
Solution: Please go to Simulation Environment then select Workbook as per below screenshot then click on Excel In next window please click on Select All tab then click on Export To Excel tab Keywords: workbook, Workbook to Excel, workbook export etc; References: None
Problem Statement: How to access Aspen Engineering Suite (AES) V8 documentation
Solution: The documentation for V8 is available online. Go to http://support.aspentch.com and click on the Documentation link in the left hand pane. In addition, you can access the documentation by clicking on the Documentation link in the product. For example, in Aspen Plus V8: Note: The product documentations are posted online to make sure the users are current on the product features. Keywords: None References: None
Problem Statement: How do I prevent my LNG heat exchanger from crashing when I select EDR-PlateFin as the Rating Method in Aspen HYSYS V8.0?
Solution: This problem is been reported and is fixed in V8.2 under CQ00492754. There are two ways of getting the Exchanger install under V8.0 as follow: Option 1: Create a normal Heat Exchanger first and change the Heat Exchanger Model to EDR – Shell&Tube. This will call EDR routine first. Create a LNG and change the Rating Method to EDR – PlateFin Option 2: Open an existing file from an older version that has a LNG EDR – PlateFin model and use this file to start from scratch. Both options will allow you to install the LNG without crashing the program Keywords: LNG, EDR, PlateFin, Crash References: None
Problem Statement: How do I switch between workspaces that I have open? In V7.3, I went to the Windows menu, selected Load Workspace and selected the one I wanted. In V8, the help file says to go to View | Layout | Save/Switch Layout, but when I go there only Save Layout is active (Switch Layout is greyed out). How do I do this?
Solution: You have to first create your layout and then save the layout before you can use the “switch layout� function. This function is to allow user to re-organize the layout of their simulation file in different ways. They can switch from one to another without re-organizing from time to time. This is especially useful when you have a dynamic case where you will need to arrange the PFD, strip charts, control face plate, so that you can monitor the parameters that are important to you all in one window. The layout feature mentioned above is referring to the second feature described inSolution 127010. The first method mentioned in theSolution is using the workload space to switch between different cases open in the same instance of Aspen HYSYS. In V8.0 and above, to load other cases file from the same instance of Aspen HYSYS, you can click on File, select Recent and select the file you wanted to re-open. You will see a window asking whether you want to active, reload or load as new. Active is used to switch to the selected file, reload is used to re-open the case file (any changes made previously will not be saved unless it was saved before switching case). Load as new will load a new copy from your hard disk. Keywords: Load workspace, switch layout, layout References: None
Problem Statement: Gas Properties Correlations (HHV, LHV and Wobbe Index) is different at 0 C in V2006.5 with CP3 as compared to V2006.5 CP4 and later
Solution: Gas Properties Correlations in HYSYS There was a problem with the Gas Properties Correlations in HYSYS V2006.5 CP 3 (and earlier). The problem resulted in the HHV, LHV, and Wobbe Index calculations being in error by about 1% when calculated for the reference temperature 0 deg C. The calculation has been corrected for the reference temperature 0 deg C, and the fix is available in HYSYS V2006.5 CP4 and later versions. Note that the Gas Properties Correlations were calculated properly for the reference temperature 15 deg C, and no correction was required for the 15 deg C reference calculation. Keywords: HHV, LHV, Higher Heating Value, Wobbe, ISO:6976 References: None
Problem Statement: How do I convert a simulation case to XML in Aspen HYSYS V8?
Solution: Please select Home tab on Toolbar then select Input on Ribbon In Input Summary Window click on Export Case as XML tab Keywords: XML file, Hysys to XML References: None
Problem Statement: How do I change the fluid package in a sub-flowsheet or a column in Aspen HYSYS V8.0?
Solution: The option for changing fluid package for sub-flowsheets and columns in Aspen HYSYS V8.0 and newer releases is made available under Home tab and Simulation group. Select Fluid Package Association in the Simulation group. This will bring a form where the fluid packages can be specified for sub-flowsheets and columns. Keywords: Fluid Package, Sub-flowsheet, Column References: None
Problem Statement: How to create Aspen Properties' fluid package in HYSYS V8.0?
Solution: After you add the Aspen Properties' component list by following knowledge baseSolution136762, you can either click Fluid Packages in Home Ribbons or in Navigation Pane. You can add Aspen Properties by clicking the dropdown list to Add button. You will get the familiar Aspen Properties set up interface to choose the property package or check the Phase Handling. Keywords: HYSYS V8, Fluid Package, Aspen Properties. References: None
Problem Statement: What is the easiest way to import variables from flowsheet to Spreadsheet in Aspen HYSYS V8?
Solution: Open any Hysys file Select One of the Material Stream for example Feed stream Open Feed Stream window Select spreadsheet and place it on PFD Open it then go to spreadsheet Please keep above two object windows side by side Please select for example one of the variable in Material Stream window for example Temperature Value cell Select by left click on mouse then hold it then you will see black circle then drag it to spreadsheet Above procedure applicable from Hysys V8 onwards Keywords: Spreadsheet variables, importing variables to spreadsheet etc; References: None
Problem Statement: Installation of Aspen HYSYS 2006.5 encounters File C:\Windows\Temp\/qb error, REBOOT=ReallySuppress.exe cannot be found!
Solution: When facing this error, it indicates the absence of dot net framework 2.0 in the system or the dot net framework has not been properly installed using DVD1 Aspen Installation Browser. Please check under Control Panel | Add/Remove Programs | Microsoft.NET Framework 2.0 (i.e. whether it had been installed). If not, manually run the installer executable from DVD1 under x:\aspenONE20065DVD1\core\dotNET20\dotnetfx.exe where x:\ is the DVD drive. Keywords: HYSYS Install, AspenOne 2006.5, Microsoft Dotnet framework 2.0, .NET Framework References: None
Problem Statement: How do I use the “Stream Properties” option in the Stream Analysis in simulation environment in Aspen Plus V8.4?
Solution: Open “cumene.bkp” from Resources/Examples folder & Run the simulation In Simulation Environment please select “Feed” stream then go to Home/Stream Analysis/Stream Properties In next window user can select which properties to be reported in stream property analysis In above file “Transport Properties TXPORT” was selected Manipulated Variable “Temperature” was selected with lower and upper limits Parametric variable “Pressure” is constant variable & Click on “Run” button in Home tab Results can be viewed under “Analysis/SPROP-1/Results” from Navigation Pane Keywords: Stream properties, property analysis etc; References: None
Problem Statement: SulSim extension interface is not available (HYSYS V8.0 and higher).
Solution: When opening the SulSim extension editor, there is no interface available in Design tab. The problem with the SulSim extension view is that the Design ply picker on the first tab is not located in the upper left corner of the tab. When the new user interface reads .edf views, it attempts to detect the ply picker for a given tab based on this location. Users can manually modify the .edf SulSim view in the View Editor (C:\Program Files\AspenTech\Aspen HYSYS V8.0\viewed.exe). More information can be found inSolution 122322. Open the SulsimLinkExtn.edf file (C:\Program Files\AspenTech\Aspen HYSYS V8.0\Extensions\Sulsim) and double click on the DefaultView. The Name label, name text entry, Solving Behavior group box and Ignore check box need to be shifted to the right. With this modified .edf file in place of the original, when SulSim extension is loaded in Aspen HYSYS, the views work and function as they should. Keywords: SulSim, Extensions, Extension References: None
Problem Statement: Where can I find “Correlation Manager” in Aspen HYSYS V8.4?
Solution: Correlation Manager is available under Home Ribbon in Simulation Environment in Aspen HYSYS V8.4. The screenshot below highlights where this can be found. Keywords: Correlation Manager, ribbon, user interface, simulation utilities References: None
Problem Statement: How to install oil in Aspen HYSYS V8.0?
Solution: To install oil in Aspen HYSYS V8.0, you will have to go to your Blend and click Install Oil button. Keywords: Assay, Blend, install oil References: None
Problem Statement: How to locate an item in the Aspen HYSYS flowsheet for V8.0 and higher?
Solution: If you have very large PFD then you will be to view particular object ( like Unit Operation or Stream or Logical Operation etc;) using Find Object (Object Navigator) in Ribbon. Click on Find Object then select either Unit Operation or Stream in Filter and Select any one of the required Object available in the PFD. Finally Click on Locate to view the selected item in the PFD. Keywords: Object Navigator, Find object, Locate Object. References: None
Problem Statement: Hand Tool/Drag Mode button is not available in Aspen HYSYS V8.0
Solution: In Aspen HYSYS V8.0 Hand Tool/Drag Mode button was not implemented. However we have added it back in future release of Aspen HYSYS. Keywords: hand, drag, tool References: None
Problem Statement: How do I sort a component list in Aspen HYSYS V8?
Solution: You just need to select the component you want to move and then drag it to the place you want it to be, then just drop it there. Keywords: Sort of components, component list, V8.0 References: None
Problem Statement: The minimum and final temperature in the depressuring utility are different between Aspen HYSYS 2006.5 and Aspen HYSYS 7.0.
Solution: Final temperature difference of the case comes from the automatic checking of the option of Close Component material and energy balances at Simulation\Integrator\Options in Aspen HYSYS 7.0. This means that this option is always checked when Depressuring utility is running in 7.0, while in Aspen HYSYS 2006.5 this option could be unchecked depending on the setting of integrator. The reason for this modification is to make sure that the mass and energy balances of the vessel are always satisfied in Depressuring simulation process. If you may simply make this option checked in Aspen HYSYS 2006.5, then you will be able to get the same results between two versions. Or you can uncheck it in V7.0. Keywords: depressuring utility References: None
Problem Statement: How to find preferences in HYSYS V8.0?
Solution: In the old user interface global preferences were set from the ?Tools? menu. To set preferences in the new user interface, open the File menu and click on ?Options? in the bottom right corner. Keywords: Preference, Options, HYSYS V8 References: None
Problem Statement: How do I minimize the ribbon in Aspen HYSYS V8.0?
Solution: To minimize the ribbon in Aspen HYSYS V8.0 select Customize Quick Access Toolbar from the drop down arrow and select Minimize the Ribbon. Keywords: new in V8.0, ribbon, minimize References: None
Problem Statement: What is the difference between Aspen HYSYS 2006 and the older versions, regarding OLE registration?
Solution: Aspen HYSYS 2006 is enhanced to support multiple versions of HYSYS via OLE. This would imply that you can simultaneously start two different versions of Aspen HYSYS from Excel. For the versions prior to v2006, users could only start the last run version of HYSYS. A fallout of this enhancement, Aspen HYSYS 2006 will be registered at install time, but not at run time. Users can manually register and un-register Aspen HYSYS 2006 using the following commands: Hysys /regserver Hysys /unregserver HYSYS 2006 can also be registered by clicking the Restore File Associations option in the Aspen HYSYS group from Windows' Start menu (refer toSolution #119947). Please refer toSolutions #119950 and #119951 for the ProgIDs available for OLE applications and the impact of HYSYS 2006 OLE registration changes on the current usage of Aspen HYSYS via OLE. Keywords: Register, Restore File Associations, OLE, registration, run References: None
Problem Statement: Where can I check Aspen Hysys Version and corresponding Build number in V8?
Solution: Open Aspen Hysys application On The Toolbar File then click on below icon About Then you will get below window where user can see Hysys Version and Build number In this page, you will see numbers like V8.0 [27.0.0.38], where 27 is the version number, 0.0 is the Cumulative patch number and 38 is the build number. Keywords: Hysys Version, Hysys Patch, Hysys Build Number etc; References: None
Problem Statement: How do I change the Fly by variables in Aspen HYSYS V8?
Solution: You need to go to File / Options In the Option window / Simulation / Tool Tips /Specify Fly by You can select the variable that you want to show in the PFD. Keywords: Fly by, properties, PFD References: None
Problem Statement: Aspen HYSYS adds a Stream Cutter operation whenever a transition between different fluid packages is required. However, in some cases, the user may wish to add it by herself. However, the operation is not accessible from the Model Palette.
Solution: To add the Stream Cutter into the flowsheet, follow these steps: 1. Click in Workbook in the Home ribbon. 2. When the Workbook opens, click on the ‘Unit Ops’ tab. 3. Click on the button ‘Add Unit Op’. 4. Select the radio button ‘Logicals’ in Categories. 5. Choose Stream Cutter from the list of Available Unit Operations. 6. Click Add to create new unit, and the configuration panel will open automatically. 7. Another way to access this menu is by pressing the F12 key. Keywords: Stream Cutter, Workbook, Unit Operation References: None
Problem Statement: How to convert the Oil Manager input assay to Petroleum Assays in V8?
Solution: 1. Go to Properties environment. In the Navigation Pane select the Petroleum Assays or use the button in the ribbon Home tab | Oil section. 2. Click on Convert to Refining Assay button located in the Home tab under Oil section. 3. The Export Oil Manager Information property view appears. Select the checkbox of desired assay in the Install column of the Map HYSYS Oil to Petroleum Assay field. 4. In the Fluid Package section, select the component list type that will be used: Use Exixting or Use RefSYS Default. 5. In the Blend Options field, select the blend that will be installed. 6. If you need to map user properties, click User Property To Petroleum Property Map. The Map User Property To Petroleum Properties view appears. 7. Click on Convert button. Keywords: Oil Manager, Petroleum Assay, Convert References: None
Problem Statement: The units of measure in my property set for CPMX are on a mass basis in BTU/LB-F, but in the V9.0 Stream Summary, they are on a mole basis in BTU/LBMOL-R. Can I get the values reported on a mass basis?
Solution: This method of using units to indicate whether heat-capacity property (CPMX) is mole or mass based is not supported in the V9 Stream Summary or in the Custom Stream Summary in earlier versions since these forms cannot do the inter-basis unit conversion. All property-set properties now have only one physical type. In past versions, some properties allowed two or more of mole-based, mass-based, and flow units, such as enthalpy in kJ/kmol, kJ/kg, and kJ/s. Starting in V9, these properties have all been separated into different properties with different names. This will make it clearer what a given property represents and also make it clearer which unit conversions can be performed within results. For example, we have added a mass-based heat capacity (CPMX-M) in addition to the mole-based one(CPMX). This is also an issue for density RHOMX, molar volume VMX and other property sets.where the basis was determined by the units of measure selected. For each affected property, the old property name is used for the mole-based property and new property names apply to the other versions. Most of the new basis specific properties were added for V9, but some underwent this separation of units in past versions. See the help for details. For compatibility, the mole-based property sets still support other kinds of units, but we recommend you choose the correct property for the desired unit type. There are limitations in using molar property sets with non-molar units with the new Stream Summary. In addition, new properties for liquid 1 phase fraction and liquid 2 phase fraction are available, L1FRAC and L2FRAC as mole fractions and MASSL1FR and MASSL2FR as mass fractions. Keywords: None References: None
Problem Statement: Where is the favorites button in V8?
Solution: From the File Open menu inside Aspen Plus, the Favorites shortcut appears on the left side following new Windows standards. There is a link to Aspen Plus V8.x Favorites which opens the C:\program files (x86)\AspenTech\Aspen Plus V8.4\Favorites folder. Following Windows standards, Program Files directories are protected – you need administrator rights to add content to them. Folders can be added to Favorites by browsing to a location and then right mouse clicking on Favorites and selecting Add current location to Favorites. This design is more flexible than the V7.3 design, and more secure. Companies can choose to install files or templates in the protected space (under Program Files) by scripting the installation. These files are protected under normal user accounts. Users can add their own favorite directories and subdirectories at will through the Favorites folder. They can change these files at will too since no special administrator rights are required. Keywords: None References: None
Problem Statement: Convergence blocks cannot be deactivated in V7.2 and higher. The deactivate feature did not work in most cases when applied to Convergence blocks, so Convergence blocks can no longer be deactivated, and files loaded from previous versions containing deactivated Convergence blocks will have those blocks re-activated.
Solution: When loading simulations from previous versions into Aspen Plus V7.2, check the status of the convergence blocks. Keywords: None References: : CQ00405007
Problem Statement: How do I get to the Simulation Engine Window in V8.4? It is not available in the Start menu. Without it, how are compiles and links (aspcomp and asplink) supposed to be done?
Solution: The Simulation Engine is no longer available in V8.4 as it used to be in previous versions. It has been combined with other DOS windows and is now called Customize Aspen Plus V8.4. This was part of an effort to reduce the number of items in the start menu and to standardize on nomenclature between product lines. All the various DOS based windows for Aspen Plus (engine window, customize UI window, etc) were consolidated to one. From p.22 of the What's New guide: Simulation Engine and Customization Windows The Aspen Plus Simulation Engine window and Aspen Plus User Interface Customization window have been combined into a single command under Aspen Plus, called Customize Aspen Plus (Start > AspenTech > Process Modeling V8.4 > Customize Aspen Plus). From here you can do tasks formerly performed in the Aspen Plus Simulation Engine window. To perform user interface customization tasks, change to the customization folder in this window before running commands like mmcustom or custinst.” Keywords: None References: None
Problem Statement: Does Aspen Dynamics support True electrolytes approach?
Solution: Aspen Dynamics now supports true component electrolyte simulations for liquid only and vapor-liquid systems. This lets you view the concentration of salts and ions in each stream, and can also improve the performance of the simulation compared to the apparent component approach for electrolytes. For Feeds, you can enter the composition in terms of apparent or true components (salts and ions). Since the feed stream uses the input values in a true component electrolyte simulation, any change made by a calculator or a design spec to the feed will not be used. If you want to use the feed stream results as the input then the feed stream will have to be reconciled before exporting. Note below the list of available components as well as the edit physical properties button which will have the true approach selected. Note: Aspen Dynamics does not permit a Chemistry object named GLOBAL. Rename the object in Aspen Plus before exporting to Aspen Dynamics.In earlier versions, the error message wouldn't allow an simulation set up with a true approach. Any change to the chemistry must be done in Aspen Plus. You can then use the Update Dynamics button on the dynamics toolbar to incorporate the modified chemistry into the existing Aspen Dynamics flowsheet. On the import dialog box, select the chemistry to be updated and check both the Variable update and Definition file only options: Variable update updates all variables for the dynamic simulation from the new Aspen Plus results Definition file only uses the new .appdf properties file which contains the chemistry reaction constants Aspen Dynamics does not support true component electrolyte simulations for vapor-liquid-liquid systems Keywords: True approach, electrolytes, dynamics References: None
Problem Statement: What are the new Break, Splice and Insert features in Aspen Plus 2006.5?
Solution: These new features are a new way to quickly add break apart streams while either creating new outlet and inlet stream or inserting a block between to existing unit operations. Break stream- By right mouse clicking an existing stream that connects two existing blocks and selecting the break stream option the stream will be split into an inlet and outlet stream from the two previous blocks it was connected to. The outlet stream will now be calculated and the inlet stream will need input provided or a stream reconcile will need to be completed to ensure that stream has input now that it becomes a feed stream to the previous block it was connected to. Splice streams-Splicing two stream is the opposite of a break. Two streams can be combined by right clicking the 2 streams of interest(a outlet and inlet stream) and clicking the splice streams. This option will now join the two streams and remove any input stream specifications making this now a calculated stream. Insert Block- This new feature allows any A+ block to be inserted between existing blocks on the flowsheet. This is activated by right clicking the stream between the two blocks and selecting the Insert block option from the drop down menu. This will open a new window where a block name and block type must be picked. From that point the interface will then open up the browser on that new block and require that minimal block input be completed. Then the block can be arranged to fit the flowsheet better like any other regular block Keywords: Break, Splice, Insert, stream, block References: None
Problem Statement: Are legacy databanks supported in V9?
Solution: Legacy databanks did not use a database server. They existed as files which had to be installed individually into each version of Aspen Plus on each computer. This was the system used prior to the introduction of the Aspen Properties Enterprise Database in version 2006. Custom legacy databanks were created using a system called DFMS and installed in the user interface using a system called TBS. These legacy databanks are no longer supported as of version V9, but the source files for them can be imported into the Aspen Properties Enterprise Database using the procedure inSolution 130991. From the What's New Help for V9: The legacy databank system is no longer available; the Aspen Properties Enterprise Databank is now required for all calculations. The source files for custom legacy databanks can be used to build custom databanks in the Aspen Properties Enterprise Database (APED). If you run an input file from earlier versions which contains legacy databank specifications, a warning will be issued and those databanks will be searched for in the latest database. Keywords: aped References: None
Problem Statement: After installing Aspen HYSYS 2006, it appears to take a long time to load an existing model. The same model loads without any delay using earlier versions of Aspen HYSYS.
Solution: The system is likely slowed due to multiple versions of installed licensing tools. A system cleanup is required to improve performance. To do this, follow the steps outline below: 1. Open the C:\Program Files\Common Files\Hyprotech\Shared folder and check to make sure that you do not have any files with LIC or SLM extensions. If so, make a backup of all files with such extensions. 2. Log off the system and log in using an administrative account. 3. Exit all applications and un-install all versions of SLM client tools. 4. Remove C:\Program Files\Common Files\Hyprotech folder from the system manually. 5. If you have a dongle attached to the system, remove the it from the system 6. Re-install a new copy of the SLM client tools from the aspenONE 2006 Administration DVD 7. Attach the dongle to the system 8. Copy the license files you saved in step one to C:\Program Files\Common Files\Hyprotech\Shared 9. Reboot your system 10. Log in and start Aspen HYSYS 2006 Keywords: SLM, HYSYS, slow References: None
Problem Statement: HYSYS case files still open in Aspen HYSYS 2004.x version even though Aspen HYSYS version 2006 is installed.
Solution: To ensure that Aspen HYSYS 2006 is used when double clicking on a simulation file, follow one of the two procedures outlined below: 1. Go to START | Programs | AspenTech | Aspen Engineering Suite | Aspen HYSYS 2006 | Restore File Associations, then open and close HYSYS 2006. If this step was successful, you should see the message displayed below: Please note that you may need administrative rights to complete this task. 2. Open the Windows Explorer and select Tools | Folder Options from the main menu. Select the File Types tab, and scroll until you find the *.hsc extension. Click the Advanced button and then the Edit button. Check to ensure that the application used to perform this action lists the path for the Aspen HYSYS 2006 executable, as in the screen shots below: Keywords: HYSYS, 2006, open, case, 2004.x References: None
Problem Statement: I cannot link Aspen HYSYS 2006 to MS Excel using automation; it always points to Aspen HYSYS 2004.2. In addition, invoking the Restore File Associations utility does not resolve the problem.
Solution: Unregister Aspen HYSYS 2004.2: 1.) Go to the Windows START menu, select Run then type 'cmd' 2.) From the command line, enter hysys.exe /unregserver in the folder where you have Aspen HYSYS 2004.2 installed Register Aspen HYSYS 2006: 1.) Re-try the Restore File Associations utility 2.) If step (1) above is not successful in restoring the automation link, open a command prompt as described above, and enter hysys.exe /regserver in the folder where Aspen HYSYS 2006 is installed Keywords: restore, file, association, OLE, VB, automation, excel, link References: None
Problem Statement: What's new in Aspen HYSYS 2006 for LNG Heat Exchanger?
Solution: The attached Word document provides a summary of enhancements to LNG Heat Exchanger Unit Operation in Aspen HYSYS 2006. Keywords: LNG, Heat Exchanger, Unit Operation References: None
Problem Statement: Enhancements to Packing Sizing & Rating
Solution: There are some changes and enhancements to the column packing sizing and rating. 1. Many new types of packing are in the database. 2. There are new and additional parameters for existing packings which will give more accurate pressure drop and hydraulic calculations. Users must click on the Update parameters button to load the new parameters. 3. Sizing methods were improved. For example, the Stichlmair method for sizing and approach to flooding calculations was improved. As a result, if you use the Stichlmair method to calculate pressure drop, you will see a different diameter calculated for sizing, or approach to flooding calculated for rating. 4. Other pressure drop methods are allowed. Instead of only allowing the pressure drop method selection for GENERIC, we also allow that selection for other vendors except Sulzer or Raschig. 5. New pressure drop correlations were added. - Generalized Pressure Drop Correlation (GPDC) based on the 1985 paper - Sherwood/Leva/Eckert GPDC - Robbins GPDC Note: In Aspen Plus 2006 and earlier, the packing parameters were saved with the simulation, and it is impossible to distinguish that from user entered values. Keywords: tpsar References: None
Problem Statement: Where can I check Aspen Hysys Version and corresponding Build number in V8?
Solution: Open Aspen Hysys application On The Toolbar File then click on below icon About Then you will get below window where user can see Hysys Version and Build number In this page, you will see numbers like V8.0 [27.0.0.38], where 27 is the version number, 0.0 is the Cumulative patch number and 38 is the build number. Keywords: Hysys Version, Hysys Patch, Hysys Build Number etc; References: None
Problem Statement: After Installing AspenOne 2006, I need to install OLI Alliance Suite for Aspen OLI 2006. Reading Aspen OLI 2006 Readme.pdf File, it refers to a nonexisting AES CD (CD1\Aspen OLI 2006\ OLI Alliance Suite for Aspen OLI 2006 media. Where can I find this media?
Solution: OLI Alliance Suite for Aspen OLI 2006.1.02 is copied to the client system during Aspen Plus 2006 installation. It is located under: C:\Program Files\AspenTech\Aspen OLI interface 2006\ OLI Alliance Suite for Aspen OLI 2006.1.02. When executing this program, it asks for a password which has to be obtained from OLI support by the customer. Keywords: OLI OLI 2006 OLI Alliance Suite for Aspen OLI 2006 Aspen OLI 2006 OLI interface 2006 OLI interface Aspen OLI interface 2006 OLI Alliance Suite OLI Alliance Alliance References: None
Problem Statement: How to plot a ternary diagram in Aspen Plus 2006.5 and higher
Solution: In Aspen Plus 2006.5, it is possible to create ternary diagrams from the Tools | Analysis | Property |Ternary menu without an Aspen Split license. The numerical results are also available. Residue curves are still available. Residue curves show the composition path a mixture takes as it evaporates. This helps users understand liquid-liquid equilibrium (LLE) and develop conceptual distillation designs. Keywords: None References: None
Problem Statement: Are there any issues Using Microsoft SQL Express with 2006.5?
Solution: The Aspen Properties Database Manager (APED) database will change from using MSDE to SQL Express for version 2006.5. Users may encounter the following issues or changes using Microsoft SQL Express with AES 2006.5 products: 1. Installation Issues Cannot Install SQL Express on Windows 2000 Problem Microsoft SQL Express installation fails on Windows 2000. Cause Microsoft SQL Express requires MDAC 2.8 SP1 or later. This version is not installed by default on Windows 2000.Solution Before installing Aspen Plus on Windows 2000, verify that the required version of MDAC is installed. Use Windows Update to update MDAC, or download from: http://www.microsoft.com/downloads/details.aspx?FamilyID=78cac895-efc2-4f8e-a9e0-3a1afbd5922e&DisplayLang=en Databases Not Installed Problem You can connect to the database server, but it has no databases. The built-in databases were not created when APED was installed. You may get the following message if you try to restore the databases manually: The file C:\Documents and Settings\All Users\Application Data\AspenTech\APED 2006.5\AP065.MDF is compressed but does not reside in a read-only database or filegroup. The file must be decompressed. Cause The drive is compressed. SQL server does not support databases on compressed drives except in very limited cases involving read-only databases. SQL Server 2005 and SQL Express will not allow you to create the databases on compressed drives.Solution If possible (enough disk space exists), uncompress the drive by navigating to the drive in Windows Explorer. Right-click it and select Properties, and clear the checkbox Compress drive to save disk space. 2. Run-Time Issues Cannot Connect to the Database Server Problem Connecting to a database server fails. Cause 1 If Microsoft SQL Server or SQL Server Express was installed on the server other than by AspenTech's installer, it may not be configured correctly. It must be configured to use SQL Server and Windows authentication mode. Microsoft's security routines prevent AspenTech's installer from changing this configuration.Solution 1 Using an account with Administrator privileges on the local computer, change the authentication mode for the server to SQL Server and Windows authentication mode. On Microsoft SQL Server: 1 Run Start | Programs | Microsoft SQL Server | Enterprise Manager. 2 In the tree on the left, right-click the name of the server and select Properties. The SQL Server Properties (Configure) dialog box appears. 3 Click the Security tab. 4 Under Authentication, select SQL Server and Windows, and click OK. On SQL Server Express, the user interface for configuring the server is not installed by default. If you do not have it, download it from Microsoft: http://www.microsoft.com/downloads/details.aspx?FamilyId=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en Install it before performing these steps: 1 Run Start | Programs | Microsoft SQL Server 2005 | SQL Server Management. The Connect to Server window appears. 2 Select the server name and Windows Authentication. Click Connect. The Microsoft SQL Server Management Studio Express window appears. 3 In the tree on the left, right-click the name of the server and select Properties. The Server Properties dialog box appears. 4 At the left, click Security. 5 Under Server authentication, select SQL Server and Windows authentication mode, and click OK. Cause 2 If SQL Server Express was installed on a computer (such as by installing Aspen Plus 2006.5 on a computer with no SQL server) before installing Aspen Plus 2006, APED will not work for Aspen Plus 2006. This happens because new security mechanisms in SQL Server Express cause the creation of the user/password aped/aped to fail.Solution 2 Open the SQL Server Management Studio Express as above, and create user aped and give it proper permissions, then re-register the AP06 and NIST06 databases in the Aspen Properties Enterprise Database Manager for Aspen Plus 2006. Cause 3 Microsoft SQL Express uses a modified server name.Solution 3 When specifying a server name in the Aspen Properties Database Manager on a SQL Express server, you must add \SQLEXPRESS after the computer name or use .\SQLEXPRESS for your computer, instead of using localhost or just the computer name as the server name. Cause 4 When using APED on Microsoft SQL Server 2005 or Microsoft SQL Server Express on a remote server, if only Microsoft SQL Server 2000 and/or MSDE is installed locally, you may be unable to connect to the server, with this error: Linking to the server failed. Check your input for Login Name, Password, and Server. This is due to incompatibility between the SQL client and server components.Solution 4 A patch from Microsoft will allow you to connect to the server. Visit: http://www.microsoft.com/downloads/details.aspx?FamilyId=D09C1D60-A13C-4479-9B91-9E8B9D835CDC&displaylang=en Download the Microsoft SQL Server 2005 Backward Compatibility Components, and install the component SQLDMO from this package. Generating Backup Databases Problem When attempting to back up a database on SQL Express, the following error occurs: [Microsoft][ODBC SQL Server Driver]Cannot open backup device '<path>'. Operating system error 5(Access is denied.). [Microsoft][ODBC SQL Server Driver]BACKUP DATABASE is terminating abnormally. Cause SQL Express does not support saving backups outside its working folder.Solution In the Backup Database Wizard, after specifying the server, username, password, and database to be backed up, click Browse and select a name in the default folder, typically C:\Documents and Settings\All Users\Application Data\ASPENTECH\APED 2006.5 3. General Troubleshooting Use the Database Configuration Tester to verify the configuration of the Aspen Properties Enterprise Database and the SQL server it runs on, or to help diagnose problems. To access this utility: From the Start menu, select Programs | AspenTech | Aspen Engineering Suite | Aspen Plus or Aspen Properties <version> | Database Configuration Tester. To use the tester, click the Start button at the bottom of the window. Then it will run several tests: License availability: The tester verifies a license for Aspen Plus or Aspen Properties is available. Configuration file permissions: The tester verifies that the configuration file was installed with the correct permissions. SQL engine authentication settings: The tester reports all servers that have at least one Aspen Properties database that is registered on this computer. On the localhost line, it reports the authentication mode of the local server and whether there is any problem with it. For other servers it cannot check this status, so it only reports what is required. Database access settings: The tester attempts to access each registered database and performs three tests. First, it verifies that it can connect to the database at all, with either a Connection Successful message or a message indicating the error that occurred. Next, it attempts to read the database as Aspen Plus or Aspen Properties would do. This should report Granted/Successful if the database is configured for access from these programs (see Security options under Backup Database Wizard), or Denied/Failed otherwise. Finally, it attempts to read the database as the Database Manager would do. This should also report Granted/Successful or Denied/Failed based on the security options. Keywords: aped References: None
Problem Statement: After running a simulation, there was no way to tell which blocks had errors or warnings when looking at the Process Flow Diagram (PFD).
Solution: Now, in 2006.5, it is possible to graphically indicate errors and warnings on the Process Flow Diagram. This featured is turned on and off on the Tools \ Options \ Global Data dialog. Keywords: None References: None
Problem Statement: In the past, changing the number of stages is inconvenient because the change must be made in several places ? Configuration, streams, pressure, efficiency, reactions, etc?
Solution: The column stage wizard makes all these changes for you automatically to save time and avoid errors The stage wizard will change all of the input appropriately. Keywords: RadFrac distillation column References: None
Problem Statement: A Flash3 block that previously produced significant amounts of both liquid phases in version 2004.1 no longer produces a second liquid phase after the model is migrated to version 2006
Solution: Version 2006 has a new liquid-liquid phase split algorithm and this new algorithm is the default: To keep the model consistent with earlier versions of Aspen Plus, uncheck the USE NEW ALGORITHM TO CHOOSE COMPONENT PAIR FOR L-L PHASE SPLIT box on the Setup | Specifications | Flash Convergence sheet. With the old algorithm (NEW-SPLIT=NO), Aspen Plus chooses a pair of components to split liquid composition X into X1 and X2 by heuristics. With the new algorithm (NEW-SPLIT=YES), Aspen Plus partially evaluate pairs of components for splitting liquid composition X into X1 and X2 by heuristics and select the pair that leads to lowest Gibbs energy. In general, the new splitting algorithm is more reliable. However, for some systems (we have an example of one using the apparent component approach), it is possible to observed the opposite behavior. See below for details about how the algorithms work. Liquid-Liquid Phase Splitting Algorithm Details Original method: 1. Identify a component K that is most likely to form a pure liquid phase. 2. Identify a component KL that is most likely to form a opposite phase from K. 3. Split overall liquid (X) into trial K phase (X2) and KL phase (X1). 4. Refine X1/X2Solution using Broyden's method. Check Gibbs free energy reduction along the way. New method: 1. Identify a few components KC that are most likely to form pure liquid phases. 2. For each component K in KC, identify a few components KLC that are most likely to form a opposite phase from K. 3. For each component K in KC and each component KL in KLC. a. Split overall liquid (X) into trial K phase (X2) and KL phase (X1). b. Perform fixed number of X1/X2 refinements using direct substitution method. c. After the refinement, keep the K/KL that gives the lowest Gibbs energy. 4. Perform additional refinement of X1/X2Solution using Broyden's method for the best K/KL pair. Check Gibbs free energy reduction along the way. Keywords: LLE, VLLE, FLASH3, simulation options, flash convergence, 3-phase. NEW-SPLIT References: None
Problem Statement: I have an old HYSIM case. Is it possible to use it in HYSYS V8.*?
Solution: The option to open HYSIM cases was removed as of V7.3. If you want to use these models in V8.* you must open the HYSIM case in V7.2 or older version of Aspen HYSYS and save it as .hsc (HYSYS file) that can be used in V8.* The procedure to open HYSIM cases in older versions of Aspen HYSYS is described inSolution ID 109095 Keywords: HYSIM cases, backward compatibility References: None
Problem Statement: What is REFPROP? When should it be used?
Solution: REFPROP is an acronym for REFerence fluid PROPerties. This model, developed by the National Institute of Standards and Technology (NIST), provides thermodynamic and transport properties of industrially important fluids and their mixtures with an emphasis on refrigerants and hydrocarbons, especially natural gas systems. REFPROP is based on the most accurate pure fluid and mixture models currently available. It implements three models for the thermodynamic properties of pure fluids: equations of state explicit in Helmholtz energy, the modified Benedict-Webb-Rubin equation of state, and an extended corresponding states (ECS) model. Mixture calculations employ a model that applies mixing rules to the Helmholtz energy of the mixture components; it uses a departure function to account for the departure from ideal mixing. Viscosity and thermal conductivity are modeled with either fluid-specific correlations, an ECS method, or in some cases the friction theory method. There are no adjustable parameters in this model. All pure and binary parameters were developed by NIST and cannot be changed. If a non-RefProp component is in the list, aspen engine will exclude it and re-normalize the available component. The applicable temperature and pressure ranges for pure is documented on help, as shown in the help under Aspen Plus Keywords: None References: -> Physical Property Methods and Models -> Physical Property Methods -> Property Method Descriptions -> Reference Correlations for Specific Components -> REFPROP (NIST reference Fluid Thermodynamic and Transport Database). There are also a number of references on this help page if more detailed information is needed. There is a REFPROP flash option on the Setup | Calculation Options | Flash Convergence sheet in V11 to avoid convergence and wrong result issues. Reference: VSTS 551961
Problem Statement: aspenONE Diagnostics Utility to Automatically Diagnose Problems with your Installed AspenTech Software
Solution: Aspen Diagnostics is a utility which you can download and run on your PC to check for problems with installed AspenTech products. It also can profile your PC’s hardware and software and then export the information to help AspenTech Support further diagnose any problems that you are having. Download the ‘aspenONE Diagnostics.exe’ utility, save it onto your PC, and then double click it to run it. Step through the Wizard interface to select the Aspen products that you want to test as well as which tests you want to run on each product (default is just to test the install of each product). The results are then displayed to you. After viewing the results, you can export or email the results to AspenTech support. The results include a profile of your PC’s hardware and software. Keywords: Diagnostics, test, error, aspenONE References: None
Problem Statement: What is the difference between the Aspen90 and Aspen96 curve fitting methods for tray sizing?
Solution: Aspen90 and Aspen96 methods refer to the tray sizing methods in the following references: · Ballast Tray Design Manual, Glitsch, Inc. Bulletin No. 4900, 3rd ed. Dallas, 1980. · Koch Flexitray Design Manual, Koch Engineering Co., Inc. Bulletins No. 960, 960-1, Wichita. · Nutter Float Valve Design Manual, Tulsa: Nutter Engineering Co., 1976. The Ft data for the Aspen90 and Aspen96 methods is obtained from a plot (shown below) from the Nutter Float Valve Design manual. The Ft value is then used as a parameter to calculate the bubbling area for the tray. Two sets of Ft data – one for Aspen90 and one for Aspen96 – are obtained from the above plot for different tray spacing. The data is then again plotted to compare the differences between the Aspen90 and Aspen96 methods (see plots below) Note: For 24” tray spacing, the Aspen90 and Aspen96 methods are the same (Ft = 1 for both) This option can be changed on the RadFrac Convergence | Convergence | Advanced sheet: Keywords: Aspen90, Aspen90, Nutter Valve Float tray, bubbling area References: None