question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
|---|---|
Problem Statement: How to perform a Fire scenario with the Pres Relief analysis | Solution: Aspen Plus allows to model dynamically vessels undergoing pressure relief due to a fire or heat input specified by the user. To perform a Fire scenario with the Pres Relief analysis, please follow these steps:
1-Under the Flowsheeting Options, select Pres Relief and click in new.
2- In the Setup ribbon, select "Dynamic Run with Vessel Engulfed by Fire" and set the capacity (Actual or code) and the vent discharge pressure.
3- In the Vessel Contents, select the reference stream, the flash specifications and the vessel Fillage. The MAWP can be input in the Rules tab as a percentage or an user specified.
4- In the Relief Device, select the desire Relief Device and the number of inlet pipes and tail pipes.
5- Complete the specifications for the inlet pipes and tail pipes with their respective length, inner diameter and fittings
6- In the Dynamic Input set the vessel specifications and design parameters
7- In the Fire tab, the user must specify the vessel geometry and initial composition, so Aspen Plus can compute the energy input for this scenario according to the following standards:
Also, the user must enter vessel geometry for the dynamic scenarios and can choose one of the following vessel types:
Vertical Vessel
Horizontal Vessel
API Tank (always a vertical vessel)
Sphere
Heat exchanger shell
Vessel jacket
User-specified
If the user-specified option is selected, the user must specify surface area and volume. Surface area is also required for vessel jacket. Maximum Allowable Working Pressure (MAWP) with corresponding temperature is required for all vessel types. Some vessel types require diameter, length, and volume of internals.
8- In the Operations Ribbon, set the Stop criteria and simulation times
Keywords: Pres Relief, Fire, Scenario, NFPA-30, API-520, API-2000
References: None |
Problem Statement: My license no longer matches my license locking information, what should I do? | Solution: If you notice that your locking information for your network or standalone license does not match then you will need to request for the license to be changed.
This knowledge base article can be used to request a re-host as well.
Please Note: Customer Care will double check that the license is not being used on another machine, so before submitting a license request make sure you don't have the license installed on another machine.
Step 1 - Obtain updated locking information
· Download the locking information tool - Download Page
· Run the application on the machine you have the license installed on or the machine you want the license to be transferred to.
· Extract the file you downloaded and then run the SLMLockInfo.exe.
· Once the application is running you will need to click Copy to Clipboard.
· Now paste the information into a text file and save it to your desktop for later use.
Step 2 - Submitting the license key request
Now that you have the locking information it's time to submit the request.
Open the Support menu in the upper right hand corner
Click "Request License Keys"
Once redirected to the license request form, you will need to fill out the form and then submit it.
Once the form is submitted Customer Care will need to check everything is in order before passing the information to distribution for the new license to be generated.
Keywords: : locking information doesn't match, license rehost, license does not work, how do I request a new license?
References: None |
Problem Statement: It is tedious to delete multiple events from the RAM Data Environment. Is there a quick way to delete multiple events at a time? | Solution: Starting from V10 CP6, a Delete Selected button has been added to the RAM Data environment | Events tab. The Delete Selected button allows you to delete multiple events by selecting multiple events in the RAM Data environment and clicking the Delete Selected button. Remember, events can only be deleted from the RAM Data environment if no instance of the event exists in the Simulation environment. If you attempt to delete an event in the RAM Data environment, which is currently being used in the Simulation environment, a warning message pops up prohibiting you from doing so.
Keywords: delete multiple events
References: None |
Problem Statement: How to create a live link of Cv value of one valve with Cv value of another valve? | Solution: In HYSYS, users can check the "Use sizing methods to calculate Delta P" check box to calculate either the Delta P or Mass Flow. Delta P or Mass Flow rate depends on the Valve Opening, C1, Cv or K, and Valve Operating Characteristics.
When modeling multiple pipe segments that may handle different feed throughput scenarios, it could be useful to link Cv value of one valve to other valves, so when user changes one Cv value to accommodate for new feed flow, Cv value for other valves will also change automatically.
Normally, a SET operation or a Spreadsheet operation can be used to link variables (read an imported variable then write to an exported variable). However, for the case of Cv value, the variable can only be imported. Export variable for Cv does not write into the Cv entry of the valve.
We can overcome this situation by setting two Spreadsheet operations that each reads the input (write) entry of Cv variable in the 2 valves.
Then, an additional SET operation can be used to link the these two Spreadsheet variables.
Attached is a HYSYS example file demonstrating the setup for this linking procedure. If we change the Cv value in Valve V-101, Cv value in Valve V-100 will also be changed correspondingly. Note that the transfer is only in one direction.
Keywords: None
References: None |
Problem Statement: How to display different transport properties per stage in a column? | Solution: Aspen HYSYS allow the user to review profiles, transport properties or composition per stage in a column. To display different transport properties, please follow these steps:
1. In the column Performance Tab, select Plots and choose the desired tray by tray properties option you want to track
2. Click in "View Table..." and the profile for that specific properties will be displayed per stage
3. To modify the default settings of the Profile Table like the basis or phase, please click in the "Properties..."
Keywords: Tray by Tray, Per stage, Property, Additional, Profile, Column
References: None |
Problem Statement: What does the Aspen Fidelis Reliability Submodel file contain? | Solution: The submodel file feature was introduced in V10 CP5. The submodel file is a text file which represents the utilized capacity and the culpability of the sensitivity basis unit. The text file is divided into three fields:
Lists run parameter information, the sensitivity basis unit information, and the name of the model file the submodel file originated.
Lists all events in order by ID.
Lists information regarding the sensitivity basis unit's capacity at a specific time slice for all lifecycles.
The Event Id refers to an event that is inactive at the specified time slice.
The Culpability refers to an inactive event's effect on the sensitivity basis unit's utilized capacity.
Keywords: submodel file
References: None |
Problem Statement: How can we visually identify pipes having different service/product/flow etc.? | Solution: Starting from V10 CP6, you can change the color of pipe elements to increase visibility and enhance understanding of the Aspen Fidelis Reliability model. You can select pipe colors based on different pipe flow/service/ product etc. To change the pipe's color, either use the Pipe Color input field in the Pipe Op form, or right-click a pipe element and select the Set Pipe Color... option. You can change the color using either the Standard view or the Advanced view. The Standard view displays a variety of colors organized in palette view. The Advanced view displays the RGB color model. There are three ways to pick a color in the Advanced view:
Pick a color using the color picker and the color slider
Specify the hex code in the input field
Use the slider bar for each RGB color value
Key word
pipe, color
Keywords: None
References: None |
Problem Statement: How does EDR calculate latent heat when this property is not user input and fluid composition is not specified? | Solution: In situations where fluid properties have been manually input into EDR, but fluid composition and latent heat have not been input, EDR can estimate latent heat as follows:
Keywords: None
References: None |
Problem Statement: The fields in the RAM environment are too small. Is there a way, I can zoom in/ magnify? | Solution: Starting from V10 CP6, you can now use the zoom functionality in the RAM Data environment. The View tab is not available for the RAM Data environment. You have two other options of using the zoom functions.
Use the Zoom slider bar on the bottom-right of the Aspen Fidelis Reliability application.
If you are working with a mouse, hold the Ctrl button and use the mouse spinner to adjust the zoom percentage.
Note: Selecting the Zoom to Fit button located next to the Zoom slider bar on the bottom-right causes the zoom percentage to reset to 100%.
Keywords: Zoom, RAM Data
References: None |
Problem Statement: What is a submodel in AFR and how do I create one? | Solution: A submodel in Aspen Fidelis Reliability represents an envelope model with the ability to assimilate systems with varying interactions to fully model an operation. The ability to break apart large mutli-system models by creating envelope models reduces simulation time and allows you to have a better understanding of the overall model interaction. Submodels can be used to:
Model or connect multiple plants or operations.
Connect various systems to see the bigger picture and model a broader interaction between systems.
Model utilities or external unknowns to increase accuracy of the current working system model.
There are two steps to using submodels:
Create and export a submodel file. All model files can create a submodel file which can be exported for later use.
Import the submodel file to a submodel element in Aspen Fidelis Reliability model. Troubleshoot any errors between the imported submodel file and the model file to run the simulation.
Note: Do not manually change or update submodel files. If a submodel file is out of date, re-run the simulation that produce the submodel file and export the resulting file. Changes to the submodel file may result in an invalid file or an anomalous behavior when attempting to use the altered file.
Creating and Exporting a submodel file:
Submodel file can be created by checking the Create submodel results. checkbox and running the simulation. The Create submodel results. checkbox is unchecked by default and can be found in the Run Parameters window. The Run Parameters window can be accessed by clicking the Set Run Parameters button on the Home ribbon | Simulation group. You can export by using the export functionality in the File menu.
Keywords: create submodel
References: None |
Problem Statement: This article explains the steps to complete the Calibration Wizard when using Distillation-based separation in PIMS Aspen Assay Management. | Solution: This feature allows you to calibrate the fractionation model using distillation curve data obtained for the products of a distillation tower in actual operations (aka test-run data). The resulting SI factors can then be used directly to recut crudes and update PIMS assay tables.
Complete the Fractionation Model tab information. Default value for SI Top and SI Bottom is 10. Once information is complete, click on "Calibrate" button.
Calibration Steps:
1. Configure column. Select the column you want to calibrate from the Configure Column drop-down list. Column information defined on the Fractionation Model tab, including PIMS Cut Code, PIMS Cut Description, Cut Type, SI Top and SI Bottom, will be displayed in this step.
2. Enter light product data. Enter product yield (or flow rate), light hydrocarbon composition basis, and light hydrocarbon compositions (GC data) for light products, which are typically off gas and Naphtha streams.
3. Enter heavy product data. Enter product yield (or flow rate) and distillation curve data for heavy products. The supported curve types are TBP, D86, D1160, and D2887. All products of the column are available on this form. If you are calibrating interconnected columns (such as CDU and VDU) together, the atmospheric residuum stream from the CDU may not have measured distillation data and therefore need not be entered.
4. Perform Calibration.
Specify the calibration algorithm settings. The calibration algorithm includes specifying Calibration Settings, SI Top = SI Bottom and Cut Back Parameters. Specify
Specifying weighing factors. A weight of zero means that data will not be considered.
Provide initial values of SI factors. It is important to provide reasonable initial guess of the SI factors to ensure a successful calibration.
Click on “Generate Initial Value” button to populate ECP values.
Then click on “Calibrate” button to generate updated SI values.
5. Review calibration results.
Table results: The table results display the optimized SI factors and the calculated vs. input property values.
Plot results: review how well the distillation input can be matched. The plot results display the distillation curve for each heavy product and provide valuable visual indication of how well the input distillation curve are matched by the calibrated SCD model.
As a final step for the Fractionation Model Calibration Wizard, click on “Transfer Tuning Parameters” button to populate the SI Top and SI Bottom updated values in the Fractionation Model tab.
Keywords: Distillation based, AAM,cut crudes, separation index
References: None |
Problem Statement: Is it possible to define different source conditions for each scenario? For example, the allowable back pressure for certain relief valves in one scenario. | Solution: In Aspen Flare System Analyzer the geometry and configuration network are fixed for all the scenarios as mentioned in the article (Is it possible to ignore a pipe in one scenario, but allow it in other scenarios?) but source conditions can be adjusted as needed.
As show in the following image, the inputs that are mark in blue are for scenario specific, it means that the user can set different values for each scenario.
If the user wants the same value for all the scenarios, it will be necessary to change it manually if not, the default or calculated value will be used.
Keywords: Scenario, Specific value, Blue, Change
References: None |
Problem Statement: Why the ‘% of Target’ for one of my utilities is reported as ‘INF’ on the Summary Page? | Solution: The Summary page displays the percentage values relative to the target value. In this case, the ‘INF’ stands for ‘infinity’; This just means the utility target is 0, which is possible depending on process stream data.
Keywords: INF, Utility Target, % of Target.
References: None |
Problem Statement: Does the control valve handle critical flow in Aspen HYSYS Dynamics? | Solution: The valve model in Aspen HYSYS handles critical flow in dynamic mode. This information is available in the Flow Limits page under the Dynamics tab as shown below.
Note that for vapour flows, choking is handled automatically. For liquid flow, the option has to be enabled. You can also enable the liquid choking on the Options page in the Integrator property view.
Keywords: Critical Flow, Valve Choking
References: None |
Problem Statement: How can I estimate properties not reported for solid inorganic salts? | Solution: To achieve this, you can use the Mostafa method. The Mostafa method is a group contribution method for estimating solid standard Gibbs free energy of formation (DGSFRM) and solid standard enthalpy of formation (DHSFRM), along with parameters for the solid heat capacity correlation (CPSPO1).
This method is applied to solid inorganic salts which are divided to cations, anions and ligands (for further info, refer to the article What is the Mostafa method for property estimation?).
To estimate missing parameters for solid inorganic salts:
Browse through the Navigation Pane in the Properties Environment to Components | Molecular Structure and select the inorganic ionic component solid inorganic salts you desire to get the properties from.
Go to the Functional Group tab and select the Mostafa method from the dropdown menu.
Specifying the Group Numbers for each species. These Group Number can be found on the Help Guide by looking for PCES Functional Groups Table 3.7A, then look for the Mostafa Method. Note there are some other methods to use, every one of them besides the Mostafa method is developed for Organic species.
Then add the Number of Occurrences of each species. A groups may exist in the component more than once.
Then switch from Analysis to Estimation Run Mode and estimate all missing parameters. The estimated properties will be reported under the form Estimation | Results.
For further information on the Estimation feature, please refer to the article Estimation Techniques for Physical Properties
Keywords: Estimate, Pure, Component, Mostafa, Inorganic salt, DGSFRM, DHSFRM, CPSPO1
References: None |
Problem Statement: What is the difference between heat exchanger model in Aspen HYSYS? | Solution: Below is the difference between heat exchanger models:
Rigorous Shell&Tube:
Incorporates Aspen EDR software for mode detailed calculations.
Simple End Point:
- UA method.
- Temperature difference based on LMTD.
- No phase change applications.
Simple Steady State Rating:
Rating calculations compute heat transfer coefficient and pressure drop given defined heat exchanger geometry.
Simple Weighted:
- UA method.
- Interval calculation for temperature difference.
- Use for change of phase applications.
Keywords: Heat Exchanger, Model, Aspen HYSYS
References: None |
Problem Statement: What are the recommended property packages for solubility of gas in water in a hydrocarbon system? | Solution: Peng Robinson is generally recommended as the property package of choice in Aspen HYSYS for any hydrocarbon system. However, in some cases the PR equation can consider the water solubility of Hydrocarbons to be a little low.
If hydrocarbon solubility in the aqueous phase is important, then the user can use the Kabadi-Danner package. This package is a modification of the SRK EOS enhanced to provide good VLL equilibrium results for dilute HC/H2O systems. The other option is to consider the Glycol package. The Glycol package in Aspen HYSYS has been improved in recent Aspen HYSYS. This has updated with interaction parameters giving better prediction of solubility of hydrocarbon in aqueous phase.
Keywords: Property Package, Hydrocarbon Solubility
References: None |
Problem Statement: What exactly does every file in the Offline folder do? | Solution:
When working with AOL projects the Offline folder is generated inside the AOL Project folder. This Offline folder contains a number of different files. We are going to define each one and explain their usage for the AOL project:
First off, bkp/apw, appdf, inp as well as any supporting files (cfg, dll, etc.) are essential.
Both bkp and apw are model files (YOU MUST HAVE ONE MODEL FILE). The difference being apw creates appdf file. If appdf file has been generated, you can only have one of either (not necessary to have both apw and bkp). If apw is not there, then appdf and inp should be added.
Aspen Problem Definition File (appdf) is a binary file containing arrays and intermediate convergence information used in the simulation calculations.
Aspen Plus Input files (inp) are compact summaries of the specifications for a flowsheet simulation. An input file can:
Be used as the input file for a stand-alone Aspen Plus engine run
Provide a compact summary of the input specifications for a simulation (for example, to be included in a report)
Provide the documentation of record for a simulation study (for example, as part of the archives for a design project)
Help expert users diagnose problems
As their name implies, input files contain only input specifications. No results are saved. If you want to save results, reconcile input first or use a different format.
Another file found on the Offline folder is the ads file. This is a new file type created for a different purpose. It is a data transfer file to ease integration with costing, EDR, etc.
Some other file types include def, for and his files. These used to be required in older versions of Aspen OnLine before v9. In V9 and above, def and for are empty files, while the his file is merely a text file containing detailed calculation history and diagnostic messages, which is not required for AOL applications.
Keywords:
offline, folder, online, files
References: None |
Problem Statement: In EDR simulation, the TEMA sheet result of the outlet stream does not agree with the temperature specification in the process data. I got the following note 1925 in Warning & Messages:
How could I mitigate it? | Solution: The reason why the TMEA sheet results do not match the temperature specified, is because whenever the program detects that there is 2-phase flow, the program solves the energy balance and pressure drop calculations simultaneously. The temperature reported in TEMA is that corresponding to the real outlet pressure found by the program.
In note 1925, it explains that the initial value was for an estimated outlet pressure and was changed due to the calculated pressure. Design and Checking calculations are based on a fix heat load: temperature can change when pressures change. If you want to avoid this change in temperature, set the estimated outlet pressure to the calculated pressure and repeat the calculation.
Keywords: EDR
Note 1925
2-phase flow
References: None |
Problem Statement: When simulating a heat exchanger, I need to input Oil SAE 20, with ISO Viscosity Grade 46cSt@40°C. However, I cannot find it in any of EDR’s physical property package databank. In B-JAC I can only find Oil SAE 10, 30 and 40. | Solution: ISO VG Oils are proprietary machine oils and AspenTech does not have access to their detailed thermodynamics data. Also, the relevant properties provided by different suppliers could be slightly different. You could approach your vendor for those information or search on the internet to see if such data package is available for sale. Then you could manually enter user-defined properties into EDR.
If you could accept a little inaccuracy, you could use a mixture of components that are available in our database to represent Oil SAE 20. For example, you could define a mixture of 80% Oil SAE 10 and 20% Oil SAE 30.
By ISO, Oil SAE 20 should have a kinetic viscosity of 46cSt at 40°C. In the generated stream property table, you could double check by calculating the kinetic viscosity from liquid viscosity and density at 40 degree C:
0.042462 Pa.s / 908.39 kg/m3 = 46.7 cSt (close enough)
Keywords: SAE 20
B-JAC
Viscosity
References: None |
Problem Statement: After you run a script on your simulation, you might be interested in checking the value of a given variable of interest in the message box. This article
shows which command to use in order to accomplish that. | Solution: Let’s say you’d like to print a message for the pressure of a separator block called “FLASH”. Here is an example of the syntax for you to use on your script:
application.msg "Pressure is " & BLOCKS("FLASH").P.value &”bar”
which results in a message on the Simulation Messages window, as shown below:
Keep in mind that Scripts use a different syntax compared to Tasks, so using “Print” will result in an error message.
Keywords: Print Command; Dynamics; Message Box; Task; Syntax; Script;
References: None |
Problem Statement: Plant Data throws connection error when connection to Domain is broken | Solution:
When the IP address of a machine changes while Plant Data in Aspen HYSYS or Aspen Plus is running, Plant Data will throw a connection error such as “No connection could be made because the Target machine actively refused it”. For example, if a laptop that is running Plant Data is remotely connected to your organization’s Domain, and you leave it for a while, this connection might time out. When this occurs, the IP address of the laptop will change.
Aspen OnLine uses .NET remoting technology. When a machine is on a domain and connection is lost between the machine and the domain, .NET remoting cannot resolve the machine’s IP address.
To solve this:
Ensure that the machine is connected to the domain. One way to do this is to ping the DNS server for your organization. Contact your IT personnel for assistance. It is important to resolve this before moving on to step 2 below.
If there is any non-responsive application, end the respective process using the Task Manager.
Using an account with administrative privileges, open the Control Panel. Search for Services and run it
In the Name column, locate and double click Aspen OnLine V10.0
In the dialog that pops up, under the General tab, Click Stop and then Start if the service is running. If the service is not running, click Start.
In the Startup Type field, the word Automatic should appear. If it does not, select Automatic in the Startup type field.
It is also advised to change the Startup type to Automatic (Delayed Start) for the Aspen OnLine Service. This can help avoid problems from bad start up that might be caused by limited machine resources.
Keywords:
plant, data, online, connection, RTO
References: None |
Problem Statement: How to set the Cetane Number as a column spec? | Solution: In Aspen HYSYS is possible to report the Cetane Number and Cetane Number D4737 (What is the difference between Cetane Number and Cetane Number D4737?) and like the TBP, the cetane number or index can be used as a column spec.
To set the Cetane number as a column spec follow these steps:
1. In the Design Tab and the Monitor Ribbon, click "Add Spec" and chose "Column Stream Property Spec"
2. Select the reference stream and click in "Select Property"
3. Under the Petroleum ribbon, the Cetane indexes and Cetane numbers will be located
4. Select the desire and add the Spec Value
Keywords: Add, Petroleum property, Cetane Idx D4737, Cetane Idx D976, Cetane number D4747, Cetane number 4737
References: None |
Problem Statement: Rule RPBCOL returns UNKNOWN for coloring scheme in PBACLRS that is not standard. | Solution: In V10, for custom coloring schemes in PBACLRS you need to create a new rule with appropriate predicate.
Create a rule with the predicate: ASSIGN_IND_BASED_ACTIVITY_COLORS_FOR custom scheme
Note: This rule must populate the COL column of the MAKI table to color activities according to your new color scheme.
Keywords: None
References: None |
Problem Statement: Which pressure is used if you specify both the atmospheric pressure and system back pressure in Aspen Flare System Analyzer? | Solution: In Aspen Flare System Analyzer the user can specify the Atmospheric pressure from the General tab in the Calculation Settings page.
The user can also set the System back pressure in the scenario editor. System back pressure refers to the static pressure at the outlet of the flare tip.
The System back pressure is scenario specific. The Flare System Analyzer uses this as the flare tip pressure for the specific scenario. If this value is left empty then the atmospheric pressure is used for all the scenarios.
Keywords: Atmospheric pressure, System back pressure
References: None |
Problem Statement: How do I access the Safety Analysis results if the Documentation Builder isn't loading properly? | Solution: The safety environment saves almost all of its information in an mdb file (Microsoft Access Database) with the same name as the case file (for instance, if the case file is named Example.hsc, then the database will be named Example.mdb). Therefore, it is extremely important to keep the Access database in sync with the case file by ensuring that the Access file and HYSYS file have the same name and are located in the same folder.
When there are problems with the Documentation Buiilder, we can open the Access file created by the safety environment as the last resource. Please contact AspenTech Support to review this procedure.
Notes:
The Access file must not be edited, is only for revision because this could break the connection between Safety Analysis and the Access file and all the information will be lost.
If for some reason the access file is deleted it will be impossible to restore it and the user must need to recreate again all the safety analysis case.
Keywords: Access, message, mdb. hscz, PRD
References: None |
Problem Statement: Error "Could not get add-in BatchPlus 36.0 EquipmentDiagrams" when trying to generate Equipment Diagram Results.
When attempting to generate equipment drawings from Aspen Batch Process Developer using Microsoft Visio, ABPD fails to find Visio even when it is installed.
Attempting to manually install BatchPlus XX Equipment Diagrams Add-In (EquipmentDiagram2k.vsl) to Visio fails and the messages “not a valid office Add-In” is returned. | Solution: User will encounter this issue when BatchPlus Equipment Diagrams addins is not full registered with Microsoft Visio.
Copy below listed files from “C:\Program Files (x86)\AspenTech\Aspen Batch Process Developer V10.0\bin” directory to “C:\Program Files (x86)\Microsoft Office\Office15”
Try to generate an Equipment Diagram Results.
If there are issues, then repair Microsoft Visio installation.
Reboot the machine.
List of dlls to be copied and pasted:
FacilityData.dll
CalendarDialog.dll
HelpWrapper.dll
Utility.dll
ABPDTypesSimple.dll
ConfiguratorCore.dll
ErrorReporter.dll
ABPDUnmanagedInterface.dll
UnmanagedWrapper.dll
Engine_DLL.dll
ApropInterf.dll
BPSharedClasses.dll
AplusInterf.dll
BPMaterial.dll
ErrMsg.dll
BPDataIO.dll
BPComp.dll
ACMInterf.dll
DBConnection.dll
ABPDTableDescriptors.dll
ABPDInterfaces.dll
Please send an email to [email protected] if your issue is still not resolved.
Keywords: Unable to generate equipment diagrams,
visio not installed,
not a valid office add-in,
abpd and visio,
apbd equipment diagrams
References: None |
Problem Statement: When trying to generate a data file report to create a custom databank, DFMS file does not get created by Aspen Plus | Solution: As part of the workflow for creating a custom database in Aspen Properties Database Manager, the correct data structure can be generated as report from the Aspen Plus Properties Parameters and exported to an Aspen Plus DFMS report file which has a *.dfm file extension.
If there are any Proprietary databanks selected in the Enterprise Databanks list, and these databanks are secure, then Aspen Plus will not generate the dfm file even when you ask it (File|Export|File|*.rep).To ensure the dfm file is created, make sure all proprietary databanks are no longer selected and the DFMS will be generated.
Keywords: DFMS file not getting created, Aspen Properties report, *.dfm, proprietary databanks
References: None |
Problem Statement: This knowledge base article describes the table data formats used in Aspen SCM. | Solution: SCM table data can be one of several formats. Table data formats consist of a letter followed by a number. The letter indicates the type of data. The number indicates the number and format of digits.
Character (C) Format:
Each entry in a Character table consists of 1 to 64 alphanumeric characters
Default: C8
Floating Point (F) Format:
Each entry in a Floating Point table consists of a number with a total of 1 to 7 digits as follows:
1 to 7 digits to the left of the decimal point
0 to 6 digits to the right of the decimal point.
Valid formats are:
F7.0
F6.1
F5.2 (Default)
F4.3
F3.4
F2.5
F1.6
Integer (I) Format:
Each entry in an Integer table consists of a number of 1 to 8 digits, with all digits to the left of the decimal point
Default: I8
String (S) Format:
Each entry in a String table consists of 1 to 256 alphanumeric characters
Default: S256
Panel (P) Format:
A String table that contains some protected fields
Default: P256
Keywords: None
References: None |
Problem Statement: Is there a limit on tube count in the radiant box of a Fired Heater in Aspen HYSYS? | Solution: Yes, there is a limit on tube count in the radiant box of a Fired Heater in Aspen HYSYS. Currently, the limit is set to 50.
However, the limit of tube counts will be increased in next version release.
Keywords: Tube Count, Radiant Section, Fired Heater
References: None |
Problem Statement: Why the ‘% of Target’ for one of my utilities is reported as ‘INF’ on the Summary Page? | Solution: The Summary page displays the percentage values relative to the target value. In this case, the ‘INF’ stands for ‘infinity’; This just means the utility target is 0, which is possible depending on process stream data.
Keywords: INF, Utility Target, % of Target.
References: None |
Problem Statement: This knowledge base article describes the MAKF table columns that is filled by simulator in Aspen Plant Scheduler. | Solution: The MAKF table (IND x HKF) contains Floating Point information about each activity in the schedule.
Descriptions of MAKF Columns
Following is a description of MAKF columns.
LS
(Required) Specifies the Lot Size- the amount of the product produced by the operation.
PT
(Required) Specifies the Process Time- duration of this activity. Process Time is expressed in the data time unit (DTU).
ST
(Required) Specifies the Scheduled Start Time- the time when the algorithms want to start the activity. Scheduled Start Time is expressed in number of days from the start of the schedule.
AS
(Required) Specifies the Actual Start Time- the time when the simulator calculates that the activity can actually start. If there is more than one activity on a facility in a time period, the Actual Start Time will be later than the Scheduled Start Time. Actual Start Time is expressed in number of days from the start of the schedule, and is zero until you run a continuous algorithm.
JITB
(Required) Specifies the Just-in-Time (JIT) Bound- the latest time an activity can start so that its output is not delivered late. Just-in-Time Bound is expressed in days from the start of the schedule.
LT
(Required) Specifies the Lead Time- the time from the start of the operation until the product becomes available in inventory. Lead Time does not include any planned buffer (column PL in TDAT) time. Lead Time is expressed in the data time unit (DTU).
SU
(Required) Specifies the Setup Time-the time it takes to change from the previous activity on the facility to the current activity. Setup Time is expressed in the data time unit (DTU).
YF
(Optional, but must be the eighth column if it exists) Specifies the Yield Factor—a value between zero and one that is used to calculate the number of units of a scheduled activity that must be started in order to get a given, required number of completed units.
AE
(Optional) Specifies the activity's Actual end time.
PS
(Optional) Specifies the activity's Process start time.
SUC
(Optional) Specifies the setup cost.
ERANGE
(Optional) Specifies the earliest scheduled start time of the activity within the valid time range.
LRANGE
(Optional) Specifies the latest scheduled start time of the activity within the valid time range.
SOFFSET
(Optional) Specifies the offset from the activity scheduled start time referenced in ERANGE/LRANGE.
Keywords: None
References: None |
Problem Statement: How to install the Oil Manager blend in a stream located in a Sub-Flowsheet | Solution: To install an oil manager blend into a stream located in a Sub-Flowsheet, follow next steps:
Crete a new Sub-Flowsheet in the Simulation Environment (or use an existing one)
Now the Sub-Flowsheet has to be associated with Oil Manager. Go to Properties environment | Fluid Package and click "Associate Fluid Package" form the Home ribbon. Active the Subf-Flowshee check box.
Finally, install the blend from Oil Manager | Output Blend | "Install Oil" button. Create the stream by entering stream name (or use a stream already created in the existing Sub-Flowsheet), select desired flowsheet from the drop-down menu and click on Install.
Keywords: Sub-Flowsheet, Oil Manager
References: None |
Problem Statement: In some cases, the default working directory for Aspen Plus Dynamics might not be available to you. This KB articles explains how to change the working directory to another location. | Solution: The working folder is used to store temporary files created when you run a simulation. By default, the working folder AM_filename is created in the same location as the simulation files. To change the default working folder, please follow the steps below:
Note: changing the working folder closes any open simulations so it is recommended that you set the working folder before opening a simulation case.
1. On the File menu, click on Set Working Folder.
2. Browse for Folder dialog box.
3. Select the folder you would like to be your new default working folder.
4. Click OK to close the dialog box.
Keywords: Working Folder; Dynamics; Directory; Change
References: None |
Problem Statement: When simulating a heat exchanger, I need to input Oil SAE 20, with ISO Viscosity Grade 46cSt@40°C. However, I cannot find it in any of EDR’s physical property package databank. In B-JAC I can only find Oil SAE 10, 30 and 40. | Solution: ISO VG Oils are proprietary machine oils and AspenTech does not have access to their detailed thermodynamics data. Also, the relevant properties provided by different suppliers could be slightly different. You could approach your vendor for those information or search on the internet to see if such data package is available for sale. Then you could manually enter user-defined properties into EDR.
If you could accept a little inaccuracy, you could use a mixture of components that are available in our database to represent Oil SAE 20. For example, you could define a mixture of 80% Oil SAE 10 and 20% Oil SAE 30.
By ISO, Oil SAE 20 should have a kinetic viscosity of 46cSt at 40°C. In the generated stream property table, you could double check by calculating the kinetic viscosity from liquid viscosity and density at 40 degree C:
0.042462 Pa.s / 908.39 kg/m3 = 46.7 cSt (close enough)
Keywords: SAE 20
B-JAC
Viscosity
References: None |
Problem Statement: Based on the stream inlet temperature (dry bulb temperature) and the relative humidity (RH) of the Stream Saturator, how does Aspen HYSYS calculate the Wet Bulb Temperature? | Solution: Aspen HYSYS first estimates the water composition of outlet fluid at RH% saturation using the user input – feed condition, RH and Dry bulb temperature (DBT).
For WBT calculation: “Dry fluid” composition is estimated by removing the water composition from the feed stream and then it is flashed at reference T and P (the reference T is nothing but DBT). This fluid is then used to estimate parameters which will later be used for Humidity calculation mentioned below.
WBT estimation:
Start with a guess value for WBT and using iterative calculation
Estimate the WBT at which the calculated Humidity matches the user input humidity value.
Here, Aspen HYSYS chooses between two different Humidity calculations depending upon whether the feed is air or not.
Note: Both of these are essentially empirical calculations from literature.
The source for the method used when feed is air is taken from "Rules of Thumb for Chemical Engineers by Carl R. Branan” which cites Pallady, P.H., "Compute Relative Humidity Quickly," Chemical Engineering, November 1989, p.255.
Keywords: Wet Bulb Temperature, dry bulb temperature, Humidity, Stream Saturator, Saturate with water, extension
References: None |
Problem Statement: This knowledge base article describes how to classify inventory to generate a feasible schedule, | Solution: TYI:
TYI set contains all the types used for classifying inventory
This set would have been nulled out during the Data Initialization process
Based on the materials and the lines in the model, TYI needs to be filled up.
Some of the standard inventory types used in all models needs to be appended to TYI are:
ARR – Arrivals
DEM – Demand
DT – Downtime
_UA - Unassigned
SRC – M SEARCH (used in advanced models: PS-EA structure)
TYPE:
TYPE is a mapping table which maps each PRO to TYI which has to be manually filled out. The TYPE table (PRO x HPT) indicates which setup families apply to each product.
The column set of TYPE - HPT should contain the setup families.
TYPE table should also establish the relationship between PRO and the Setup attribute.
FAM:
The FAM set lists setup families. FAM entries consist of the following:
Code - Name of a setup family set
Description - Description of the setup family
Example:
This example shows the PKG (Package) setup family set, which lists the categories within the Package family.
Keywords: None
References: None |
Problem Statement: What are the supported amine solvents in Acid Gas - Liquid Treating property package in V10? | Solution: Supported Amines
MEA
DEA
MDEA
DGA
MDEA + PZ
Keywords: Liquid Treating
References: None |
Problem Statement: When starting Aspen Batch Modeler v8.4 Distillation you get a message saying Unable to load DLL 'attpsr.dll' "The network path was not found. This error is only for Aspen Batch Modeler v8.4 and no other version.
With Aspen Batch Distillation v7.3, you could get a similar message saying Unable to load DLL 'attpsr.dll'; Access is denied.
Error example is shown in the screenshot below. | Solution: The errors are very different but we describe both in the same document as customers searching for the error could find the incorrect one...
Aspen Batch Modeler v8.4 only
For v8.4, the reason is that Aspen Batch Modeler v8.4 may be used with Aspen Properties v8.4 or Aspen Properties v8.6. When you install Aspen Batch Modeler v8.4 it is configured to use Aspen Properties v8.4. The error will occur if Aspen Properties v8.4 is not installed. To select Aspen Properties v8.6, you should search for the program "Aspen Properties Version Selector", and select the v8.6 option as shown below:
Aspen Batch Distillation v7.3 only
For Aspen Batch Distillation v7.3 the error is caused by the fact the program is unable to access the file attpsr.dll which is located in two different directories.
For a 32bit OS it will be located in
"C:\Program Files\AspenTech\APrSystem V7.3\Engine\Xeq"
"C:\Program Files\AspenTech\APrSystem V7.3\GUI\Xeq"
For a 64bit OS it will be located in
"C:\Program Files (x86)\AspenTech\APrSystem V7.3\Engine\Xeq"
"C:\Program Files (x86)\AspenTech\APrSystem V7.3\GUI\Xeq"
The solution is give to the user read/write access to these folders. Note that v7.3 is no longer supported, so this part of the solution is mostly only for historical purposes. The change of access rights is not needed for other versions.
Keywords: None
References: None |
Problem Statement: How do I find the build number of Aspen HYSYS? | Solution: Sometimes because of version compatibility users need to know which build number they're using. To do so please open Aspen HYSYS and go to File | About and check the last four numbers inside the parenthesis.
In this example, for Aspen HYSYS V10 the build number is 36.01.250.
Here some more examples of Aspen HYSYS build numbers per version.
V10 – 36
V9.0 – 35
V8.8 – 34
V8.7 – 33
V8.6 – 32
V8.4 – 30
V8.3 – 29
V8.2 – 28
V8.0 – 27
V7.3 – 25
To verify all Aspen HYSYS versions installed on a computer, click on Start button in your Windows machine, and type regedit in the search box. In Registry Editor window, go to HKEY_LOCAL_MACHINE | SOFTWARE | Wow6432Node | AspenTech | HYSYS folder.
Keywords: build number, versions, HYSYS
References: None |
Problem Statement: This knowledge base article describes the columns in MAKI table that is populated by simulator. | Solution: The MAKI table (IND x HKI) contains Integer (index) information about each activity in the schedule. This table is populated by the Simulator (M SIM).
Descriptions of MAKI Columns:
Following is a description of MAKI columns.
LEV
(Required) Specifies the hierarchy (HIER) level assigned to the activity by the last algorithm that changed the activity. A entry of -1 indicates that this activity is not in the current schedule; that is, it has been deleted.
The entry in the first row is the next free IND value. This is the first IND entry which represents a deleted activity, one that has a -1-hierarchy level. This next free IND is maintained so that as activities are added, they can fill empty slots in the MAKx tables instead of always being added to the end.
FAC
(Required) Index of the FAC set entry for the facility where the operation occurs.
PRO
(Required) Index of the PRO set entry for the product produced by the operation.
TIM
(Required) Index of the TIM set entry that corresponds to the Scheduled Start Time (ST).
ALT
(Required) Index of the PRO set entry for the alternate operation.
DEM
(Optional) Index of the DEM set for the activity.
COL
(Optional) Index of the SCOLOR set that indicates the activity color.
TIMAS
(Optional) Index of the TIM set entry that corresponds to the Actual Start Time (AS).
TIMPS
(Optional) Index of the TIM set entry that corresponds to the Process Start Time (PS).
BOMID
(Optional) Index of the BOMID set for the bill of materials ID. A value of -1 indicates that the bill of materials ID is currently undefined.
ELKIND
(Optional) Specifies the associated activity from the ERANGE constraint in MAKF.
LLKIND
(Optional) Specifies the associated activity from the LRANGE constraint in MAKF.
Keywords: None
References: None |
Problem Statement: How to fix a license commuted error code 75?
Successfully commuted the Aspen Plus license key, opened Aspen Plus, and then SLM Commute error 75 occurred. | Solution: The SLM Client Commuter registry is corrupted and a clean file is required to remove the error code 75. Please follow the 3 steps to receive your clean file from AspenTech Technical Support Team.
1. Please login and submit a case at the https://esupport.aspentech.com/apex/S_Homepage.
2. Provide the Locking Information (KB #22206)
3. Provide the System Name (KB #22471)
Note: Return all commuted license and close all the SLM Client tools before using the clean file.
You will receive a zip file that contains the following two files:
a. SLMClean.exe and a clean file
b. Save and extract at the same folder
c. Right click the SLMClean.exe and select “Run as administrator”
d. Click on the browse button to point it back to the clean file located at the same folder.
e. Finally, click Start Clean button and click close button once it is completed.
f. Commute a license key(s), open Aspen Plus, and then open a case to use the commuted license.
g. From Aspen Plus, click "File" Tab, "About", then "Licensing Information" button to verify the commuted license is check-out from the no-net.
You should see the license key name and no-net (commuted license).
This confirms that the commuted license key is now working and you are no longer seeing an error 75.
Keywords: SLM Commute tool, error code 75, and error while commuting
References: None |
Problem Statement: Why if the Sulfur Content of my assay is set as zero I still see a value reported in the stream properties? | Solution: Aspen HYSYS doesn't distinguish between organic sulfur and inorganic sulfur, it just has a sulfur property and if your stream composition has H2S, you are expected to see the sulfur content in the stream properties. If you want to see the sulfur content without the effects of H2S, you either need to remove the H2S, or reset the H2S sulfur to zero (e.g. using a manipulator).
Keywords: Sulfur Content, Manipulator, H2S, Organic, Inorganic, Assay, Properties.
References: None |
Problem Statement: How does Aspen Plus calculate the Diffusion Coefficient? Is possible to report it? | Solution: The Aspen Physical Property System has seven built-in diffusivity models:
Model Type
Chapman-Enskog-Wilke-Lee (Binary) Low pressure vapor
Chapman-Enskog-Wilke-Lee (Mixture) Low pressure vapor
Dawson-Khoury-Kobayashi (Binary) Vapor
Dawson-Khoury-Kobayashi (Mixture) Vapor
Nernst-Hartley Electrolyte
Wilke-Chang (Binary) Liquid
Wilke-Chang (Mixture) Liquid
The diffusion is related to viscosity, so several of these diffusion coefficient methods, require viscosity, for both liquid and for vapor diffusion coefficients (Chapman-Enskog-Wilke-Lee and Wilke-Chang models).
Vapor diffusion coefficients can be calculated from molecular theories similar to those discussed for low pressure vapor viscosity and thermal conductivity. Similarly, pressure correction methods exist. The Dawson-Khoury-Kobayashi model calculates a pressure correction factor which requires the density as input.
Liquid diffusion coefficients depend on activity and liquid viscosity.
Binary diffusion coefficients are required in processes where mass transfer is limited such as in rate-based distillation. Binary diffusion coefficients describe the diffusion of one component at infinite dilution in another component. In multicomponent systems this corresponds to a matrix of values. These values can be reported on the RadFrac | Transfer Coefficients | Diffusion sheet. The profile is only available if the Include binary diffusion coefficients checkbox on the Rate-Based Report | Property Options sheet is selected. To make this profile available, select that option and re-run the simulation..
The average diffusion coefficient of a component in a mixture does not have any quantitative applications; it is an informative property. However, it can be reported using the property DMX (Diffusion Coefficient for a component on a mixture), defining the components and the phase on the Qualifiers.
Note: Phase=L is not allowed when 2-liquid phases are present.
Keywords: Diffusivity, Diffusion coefficient, DMX, Chapman-Enskog-Wilke-Lee, Dawson-Khoury-Kobayashi, Nernst-Hartley, Wilke-Chang.
References: None |
Problem Statement: The attached guide explains several common recommendations to set up the format of a Dynamics model. | Solution: This here is the most trivial information you will ever read on dynamic simulation, yet it is valuable information intended to make things a bit easier. The idea is to separate the trivial from the modelling problems, so you can better focus on the real work. Most of this should be done while still in steady-state mode to make sure that you only need to do the formatting work once.
Keywords: Dynamics, Strip Charts, Format.
References: None |
Problem Statement: How are equivalent length of fittings calculated in Aspen Flare System Analyzer? | Solution: The fittings loss method in Flare System Analyzer uses two-K method. The equation used is
K = A + B * fT
Where
A
= constant, also known as VH (velocity head) factor
B
= constant, also known as FT factor
fT
= Darcy friction factor for fully turbulent flow (Re = 10^10)
f
= Darcy friction factor at actual pipe flowing conditions (reported in pipe summary)
After K is solved for, equivalent length can be calculated from K = f * ( L/D ).
Please see the attached MS excel file.
Keywords: Equivalent length, fittings, pipe
References: None |
Problem Statement: When user design distillation column in HYSYS, program will input feed stream's vapor and liquid phase together into the designated stage (default).
It can cause high uncertainty for some distillation column which has 2-phase feed stream. | Solution: Some of feed stream are depressurized or heated for next distillation column.
Vacuum distillation unit is a good example for this operation. When the liquid stream from atmospheric distillation is fed into the vacuum distillation, it depressurize from atmospheric pressure to 2-4 psia which is almost 6-7 times lower than previous condition. Then 10~20% of fluid is vaporized.
Generally, feed stream is fed above the column tray so the vapor phase goes to the above stage while the liquid phase is fed to the designated stage. However, when user input the stream as a default configuration, those vapor phase is fed into the same stage with liquid phase. Thus, it can calculate column heat duty incorrectly.
In this case, user can use 'split' option to model this rigorously. This will make vapor phase go to the above stage and liquid phase go to the designated stage.
This configuration can increase the condenser heat duty slightly.
Please consider 'split' option carefully when there's higher pressure drop for feed stream or the feed stream is 2 phase. Also, user need to consider his own column configuration to model the simulation rigorously.
Keywords: Split, distillation, 2 phase
References: None |
Problem Statement: How to fix Aspen Plus V10 "Error_while_checking_out_license_(SLM_RN_PML_PLS_BATCHMOD)?
***************************************************************************** * SORRY, LICENSE VALIDATION/CHECKOUT FAILURE FOR BatchProcess * * Server: "Error_while_checking_out_license_(SLM_RN_PML_PLS_BATCHMOD)" re * * turned error: "SLM Configuration Information" * * Server: "IgnoreLocal" returned error: "SLM Configuration Information" * * Server: "Error_while_checking_out_license_(SLM_RN_PML_PLS_BATCHMOD)" re * * turned error: "SLM Configuration Information" * * Server: "server name(default,SLM)" returned error: "18 * * . The license for this product or feature could not be retrieved. * * * * Please ensure that you are connected to the correct license server and * * check that the feature that you are trying to access is available on th * * at server."* * Server: "SuppressBroadcasts" returned error: "SLM Configuration Informa * * tion"* ***************************************************************************** | Solution: First, verify that your current license does not include the license key by opening the License Profile. Please refer to this KB article #45955 on how to use the License Profiler.
Second, refer to KB article #22319 on how to submit a license upgrade request and priority. This is not a rehost license request; therefore, you do not need to add the locking information
Finally, You will received the new license file as an email attachment from customer care. Please refer to KB article #22241 on how to install a network license file.
Keywords: Batch Process, License validation failure, Error while checking out license, license file upgrade, and Aspen Plus license error.
References: None |
Problem Statement: This knowledge base article describes set up time and cost for materials and the underlying structures that define them. | Solution: Setup time is the time consumed on transitioning from one operation to another.
Setup cost is the cost incurred on transitioning from one operation to another.
SGRP Table
The SGRP table (FAM x HTC) defines parallel and serial setup tasks. SGRP is an Integer table.
SGRP table defines whether the setup attributes are serial or parallel:
Serial setups are indicated by the same number for all tasks.
Parallel setups are indicated by a different number for tasks.
Create entries in SGRP as follows:
Serial setup tasks - Assign the same number to all tasks.
Parallel setup tasks - Assign different numbers to tasks.
Example
STBC Table:
The STBC table (FAM x HTC) specifies setup resource consumption. The rows of STBC are the setup families. STBC's columns include the following:
COST keyword (required).
TIME keyword (required).
Any other setup resource consumed (Optional). These can be consumable or non-consumable. All setup resources (other than COST and TIME) must be defined in the PRO set.
Example:
This STBC table contains the required columns for COST and TIME, plus columns for two other resources that are required for setups: Labor (Workers, a non-consumable resource) and cleaning chemical (a consumable resource).
Keywords: None
References: None |
Problem Statement: What are the supported amine solvents in Acid Gas - Physical Solvents property package in V10? | Solution: Currently, only DEPG is supported amine solvents in Acid Gas - Physical Solvents property package.
Keywords: Physical Solvents, Acid Gas
References: None |
Problem Statement: What is the source of the Conduction terms (heat capacity, density and thermal conductivity) available in the Detailed Heat Flow model in the dynamics pipe segment? | Solution: The heat capacity, density and thermal conductivity values must depend on the pipe material.
The topic Pipe Segment Heat Model Page | Detailed Heat Loss Model | Conduction Option shows a table with some typical values for metals. However, you will notice the default values are based on a material that is not listed in the table. The table lists values for common metals but they are likely averages from various alloy composition variations. These values seem more like an average rough estimate that could be useful if you don’t have access to any other source.
Here is a list of materials with thermal properties that you could use as reference as well.
The material values in HYSYS are from arbitrary material, the table values may deviate from other literature values probably because they are averages or assuming a particular alloy composition.
The default values are there just to signal to the user that they are an input. Aspen HYSYS Dynamics does not intend for the default values to be rigorous approximations; they are simply placeholders.
Keywords: Dynamics, Pipe Segment, Heat Model, Heat Flow, Detailed, Properties, Conduction.
References: None |
Problem Statement: Role permissions defined in RBNAVMAP not respected for Sequence Builder related screens in Aspen Plant Scheduler. | Solution: RBCMG is the campaign manager role permissions configuration table and it repopulates RBNAVMWK in RRBTIER.
So, you need to also uncheck the appropriate rows there in RBCMG for the Role permissions to work.
Keywords: None
References: None |
Problem Statement: I am trying to design a heat exchanger with shells in series. However, the program is preventing me from specifying more than one shell in the design parameters. Why is this? | Solution: The issue relates to the shellside nozzle configuration. If separate nozzles for vapour / liquid outlets have been specified, you will not be able to design with shells in series. Changing the option to the screenshot below will resolve the issue
Keywords: ,
Shell in series, Shell side nozzles
References: None |
Problem Statement: How can I convert a flowsheet into a template? Can I convert a subflowsheet into a template? | Solution: To save a simulation file as a template, instructions change depending on the HYSYS version:
For V7.0 to V7.3
Select Simulation | Main properties from the top level menu and click the Convert to Template button.
For V8.0 to V8.2
Click on the Convert to Template button located in the ribbon under the Home Tab
For V8.3 to V10.0
Click on the Convert to Template button located in the ribbon under the Customize Tab
Choose YES to confirm converting the existing case to a template, then either YES or NO to save any changes made to the current case. Note that when you close the template case you must save the file in a suitable folder.
To insert a saved template into a PFD (or in another subflowsheet), first add a Subflowsheet operation from the Model Palette. Select the Read an Existing Template option and select the template file saved previously.
This workflow only applies to convert a whole flowsheet into a template. If you want to convert a single subflowsheet into a template, you need to first create a separate HYSYS file with the desired subflowsheet, and then convert it into a template.
KB article #29731 describes how several subflowsheets can be merged into a single flowsheet by using templates.
Keywords: Template, Convert, Subflowsheet, HYSYS
References: None |
Problem Statement: What are the supported amine solvents in Acid Gas - Chemical Solvents property package in V10? | Solution: Supported Amines
DEA
DGA
DIPA
MDEA
MEA
PZ
TEA
Supported Amine Blends
DEA+DGA DGA+DIPA DIPA+MDEA MDEA+MEA MEA+PZ PZ+TEA Sulfolane+DIPA
DEA+DIPA DGA+MDEA DIPA+MEA MDEA+PZ MEA+TEA Sulfolane+MDEA
DEA+MDEA DGA+MEA DIPA+PZ MDEA+TEA Sulfolane+MDEA+PZ
DEA+MEA DGA+PZ DIPA+TEA MDEA+MEA+DEA
DEA+PZ DGA+TEA
DEA+TEA
Keywords: Chemical Solvent, Acid Gas, Amine
References: None |
Problem Statement: This knowledge base article describes the complete list of TDAT parameters in Aspen Plant Scheduler. | Solution:
ACCUMULATION FACTOR (AF):
The accumulation factor column controls on how inventories are carried over from one-time period to the next.
0 or Blank: No inventory is carried over from one-time period to the next
1: Inventory is carried over
Number between 0 and 1: Some inventory is lost during storage.
LOT SIZE POLICY:
Lot Size Policy (LP in TDAT) specifies how you want the scheduling algorithms to determine lot sizes for activities. You can use the Lot Size Policy to control flexibility in lot sizes.
Three related parameters are used in determining lot sizes, depending on the Lot Size Policy:
Target Lot Size (LS)
Minimum Lot Size (MN)
Maximum Lot Size (MX)
Possible Values: The following are possible values for Lot Size Policy (LP).
FIXED
Lot size is fixed. Algorithms must use the value from the Target Lot Size (LS) parameter for all activities.
ADJUST
Lot size is adjustable. Algorithms can set the lot size to any value between the Minimum Lot Size (MN) and the Maximum Lot Size (MX) as needed. When using ADJUST Lot Size Policy, set the Minimum Lot Size (MN) parameter to the physical lower limit or the minimum volume that can be run between setups. Set the Maximum Lot Size (MX) to a value that is less than the volume that can be produced in a single time, in order to allow the scheduling algorithms to do capacity balancing. If detailed coordination of intermediate inventories is critical, you can set MX as low as 10% of the amount that can be produced in a single time period.
NOMAKE
Do not make the product.
IGNORE
Do not make the product and ignore problems associated with not making it.
INCRE
Lot size is adjustable. Algorithms can set the lot size to any value between the Minimum Lot Size (MN) and the Maximum Lot Size (MX) in increments of the Target Lot Size (LS). INCRE honors the tolerance you specify for the Tolerance for Zero (TOLZ) parameter in the CMAN table.
The INCL (Honor Incremental Lot size Policy) parameter in CMAN controls which algorithms honor the INCRE policy.
MINIMUM LOT SIZE (MN):
Minimum Lot Size (MN in TDAT) specifies minimum lot size quantities for use when Lot Size Policy (LP) is set to ADJUST or INCRE.
MAXIMUM LOT SIZE (MX):
Maximum Lot Size (MX in TDAT) specifies maximum lot size quantities for use when Lot Size Policy (LP) is set to ADJUST or INCRE.
MAXIMUM STORAGE (MS):
An entry in the maximum storage column defines the maximum allowable inventory of a product. This column is used by the TANK and MOVE algorithms.
DURATION CALCULATION POLICY (DURCALC):
Duration Calculation Policy (DURCALC in TDAT), determines whether SCM interprets the Process Time (PT) column in TDAT as a time or a rate.
Possible Values
FIXED: (Default) The TDAT Process Time (PT) column represents the process time for one batch.
VARIABLE: The TDAT Process Time (PT) column represents the rate of a batch.Duration = TDAT (*, PT) * LT
COMPONENT INVENTORY POLICY:
Component Inventory Profile Policy (CMPINVP in TDAT) controls how the operation consumes its components.
Possible Values:
STEP: (Default) The operation consumes all the components at once, at the operation’s Process Start Time (after any setup time).
RAMP: The operation consumes the components at a steady rate during the operation.
OUTPUT INVENTORY PROFILE POLICY (OUTINVP):
Output Inventory Profile Policy (OUTINVP in TDAT) controls when the operation’s output becomes available.
Possible Values:
STEP: (Default) The operation’s product becomes available all at once, after the calculated Lead time.
RAMP: The operation produces the product at a steady rate starting after the calculated Lead Time.
LEAD TIME CALCULATION POLICY:
Lead Time Calculation Policy (LTCALC in TDAT), controls how SCM calculates the Lead Time.
Possible Values:
INCLPT: Lead Time includes Process Time. Lead Time is a sum of the TDAT Lead Time (LT) LeadTime>main column and the Process Time for the activity.
EXCLPT: (Default) Lead Time does not include Process Time. The TDAT Lead Time (LT) column represents the entire Lead Time.
EDIT CHANGE POLICY:
EDITLS: When modifying Lot Size
CHGDUR: Recalculates Duration
CHGRATE: Recalculates Rate
NA - Rejects lot size Changes
EDITRATE: When modifying Rate
CHGLS: Recalculates Lot Size
CHGDUR: Recalculates Duration
NA - Rejects Rate Changes
EDITDUR: When modifying Duration
CHGRATE: Recalculates Rate
CHGLS: Recalculates Lot Size
NA – Rejects Duration changes
INVENTORY POLICY(IP):
Inventory Policy reflects the units in which consumption of a given product is measured.
UNIT: Consumption is measured in units per unit made. This policy normally applies to raw materials, intermediate products and finished goods.
HOURLY: Consumption is measured in units per hour run. In conjunction with an Accumulation Factor of 0.0, the resource disappears at the end of each time period. This policy is applied to manpower.
NONCON: Consumption is measured in units per hour run. Accumulation Factor must be zero, as the simulator accumulates inventory and receipts automatically over time. This policy is applied to tooling used in setups or operations.
EXPEDITE: Assumes that all receipts are available at the beginning of the schedule. There is an Activity Policy, IGNORE, that ignores inventory considerations for operations.
LEAD TIME (LT):
The Lead Time determines product availability. It is the delay between the start of an operation and the time at which product becomes available. This delay includes the time required to move the product to the next facility and any quality control measures.
PLANNED BUFFER (PL):
The Planned Buffer is an optional timing buffer which is used in the development of the discrete solution and aids in obtaining synchronous flow in continuous time. The Planned Buffer is added to the Lead Time to add an extra time cushion for selected products. While this buffer causes products to be made earlier than might be required, it does not cause additional parts to be made.
PROCESS POLICY (PP):
The Process Policy defines whether the operation runs in batch or continuous mode. The three possible policies are:
BATCH: The operation is considered intermittent. The process time is determined by the Duration Calculation Policy.
CONTIN: The operation is continuous, i.e., the process time will take up the entire period, and there will be only one operation per facility in each time period. The amount produced in each time period is between the MINIMUM and MAXIMUM LOTSIZE. For CONTIN policies, the Duration Calculation Policy must be FIXED, and the Process Time entry should be CAPF.
BLOCK: The operations run continuously. On the facility, there can be a change from one operation to another. This is referred to as blocking the operations. There is no idle time on the facility between operations. The simulators enforce this feature by pulling all activities forward. This is similar to running M PULL on the facility.
SETUP POLICY:
The Setup Policy defines how a setup cost and time is calculated for a changeover. Setup Policy has one option: SKIP. The SKIP option skips the calculation of setup time and cost from an activity with the setup policy SKIP to the other activity. Instead, it will find the preceding or earlier non-SKIP type activity on the same facility and use its PRO Code for the changeover. For example, we have activities A, B and C in sequence and the setup policy of activity B is SKIP. When calculating the setup item and cost from activity B to activity C, M SETUP will actually calculate the setup cost and time from activity A to activity C. This would be useful when activity B is a shutdown and the machine configuration remains the same.
RATE ADJUSTMENT POLICY:
User-defined rates can be maintained. In order to keep the rate of an operation constant, the column set of TDAT must contain Code RA, and the TDAT entry for that operation in the RA column must be FIXED. The rate of an existing activity for that operation is not changed when it is moved in time on the same facility, but if the activity moves to another facility, the activity gets the TDAT rate appropriate for that facility. New activities would still get their rate from TDAT.
ACTIVITY POLICY:
Activity Policy defines how a product is consumed and how the operations consuming this resource are handled in runout situations. This policy is used exclusively by the CRIT and SYNC algorithms. The options for this policy are:
Blank: Advances or delays activity as required to solve the problem.
IGNORE: Ignores resource constraints.
ADVANC: Makes the process batch earlier when the resource is available. CRIT cannot advance a continuous operation.
DELAY: Makes the process batch later when the resource is available.
ALTERN: Looks for an alternate operation in place of the given operation.
LOOKAHEAD POLICY (LA):
The Lookahead Policy is used for looking ahead in computing lot sizes. This Policy is turned on by the presence of the LA (LOOKAHEAD) entry in the HTD column in the TDAT table. It tries to compute a lot size for the next n data time units where n comes from TDAT(@,LA). The LOOKAHEAD value n can be represented by a constant value or a table. Lot size Policy can be ADJUST or INCRE. Even though the LA entry exists in the HTD set, an inventory type (TYI) with n blank or zero will ignore the LOOKAHEAD logic.
LOOKAHEAD POLICY FOR MAKE (LAMAK):
Lookahead Policy for MAKE (LAMAK in the TDAT table) specifies a number of DTUs that you want the MAKE algorithm to "look ahead" in the schedule to determine whether to create or modify jobs in the current time period in response to an inventory shortage. Inventory shortages are caused by negative values in the LEVE table.
If the Lookahead Policy for MAKE column exists in TDAT and the current inventory level is less than the Order Point or less than the ending inventory target when applicable, MAKE moves ahead the specified number of DTUs starting from the end of the current time period, and checks the inventory level in the LEVE table in that time period.
If the inventory shortage does not exist in the later time period (the corresponding value in the LEVE table is greater than the Order Point and ending inventory target when applicable), MAKE does not add new activities or increase the quantities of existing activities, even if there is an inventory shortage in the current time period.
If the inventory shortage exists (the corresponding value in the LEVE table is less than the Order Point or ending inventory target when applicable), it adds new activities or increases the quantities of existing activities in the current time period in order to meet the deficit amount. The deficit is the greater of the inventory shortage number in current time period and that in the future time period determined by the lookahead amount.
Sometimes activities in the current period do not release material until the next time period or even later, depending on the Lead Time Calculation Policy (LTCALC in TDAT), Output Inventory Profile Policy (OUTINVP in TDAT), or Duration Policy (DP in TDAT). This means that the demands which the activities were meant to fulfill are not met in the current period. Lookahead Policy for MAKE enables you to overcome this difficulty.
Possible Values
Desired number of DTUs
Table name
0 or negative number – Do not use Lookahead Policy for MAKE
ORDER POINT:
The Order Point is the inventory amount of a given product which triggers a decision to order or produce additional product. Order Point is sometimes referred to as safety stock level.
Possible Values:
Number
Table dimensioned PRO by TIM. SCM compares the values in the last column of the table to ending inventory targets from the PDAT table, and takes the higher of the two values as the Order Point.
Table dimensioned as follows:
Row set: Any set other than TIM
Column set: 1
Caution: Do not use tables with the following dimensions for Order Point. If you do so, SCM takes the value for the first-time period and applies it to all time periods.
TIM by 1
Any set other than PRO by TIM.
DURATION POLICY:
FIXED Duration Policy:
FIXED, one of the possible settings for Duration Policy, consists of the following options:
Duration (DURCALC): FIXED
Lead Time Calculation (LTCALC): EXCLPT
Component Inventory Profile (CMPINVP): STEP
Output Inventory Profile (OUTINVP): STEP
Edit Change works as follows. A change to the:
Rate is not allowed
Duration or Lot Size recalculates the Rate
FIXLOTS Duration Policy:
FIXLOTS, one of the possible settings for Duration Policy, consists of the following options:
Duration (DURCALC): FIXED
Lead Time Calculation (LTCALC): EXCLPT
Component Inventory Profile (CMPINVP): RAMP
Output Inventory Profile (OUTINVP): RAMP
Edit Change works as follows. A change to the:
Rate recalculates the Duration
Duration or Lot Size recalculates the Rate
FIXDUR Duration Policy:
FIXDUR, one of the possible settings for Duration Policy, consists of the following options:
Duration (DURCALC): FIXED
Lead Time Calculation (LTCALC): EXCLPT
Component Inventory Profile (CMPINVP): RAMP
Output Inventory Profile (OUTINVP): RAMP
Edit Change works as follows. A change to the:
Rate recalculates the Lot Size
Duration or Lot Size recalculates the Rate.
FIXRATE Duration Policy:
FIXRATE, one of the possible settings for Duration Policy, consists of the following options:
Duration (DURCALC): VARIABLE
Lead Time Calculation (LTCALC): EXCLPT
Component Inventory Profile (CMPINVP): RAMP
Output Inventory Profile (OUTINVP): RAMP
Edit Change works as follows. A change to the:
Rate or Lot Size recalculates the Duration
Duration recalculates the Lot Size
VARIAB Duration Policy:
VARIAB, one of the possible settings for Duration Policy, consists of the following options:
Duration (DURCALC): VARIABLE
Lead Time Calculation (LTCALC): EXCLPT
Component Inventory Profile (CMPINVP): RAMP
Output Inventory Profile (OUTINVP): RAMP
Edit Change works as follows. A change to the:
Rate is not allowed
Duration recalculates the Rate
Lot Size recalculates the Duration
VARBLOCK Duration Policy:
VARBLOCK, one of the possible settings for Duration Policy, consists of the following options:
Duration (DURCALC): VARIABLE
Lead Time Calculation (LTCALC): INCLPT
Component Inventory Profile (CMPINVP): STEP
Output Inventory Profile (OUTINVP): STEP
Edit Change works as follows. A change to the:
Rate is not allowed
Duration recalculates the Rate
Lot Size recalculates the Duration.
VARCYCLE Duration Policy:
VARCYCLE, one of the possible settings for Duration Policy, consists of the following options:
Duration (DURCALC): VARIABLE
Lead Time Calculation (LTCALC): EXCLPT
Component Inventory Profile (CMPINVP): STEP
Output Inventory Profile (OUTINVP): STEP
Edit Change works as follows. A change to the:
Rate is not allowed
Duration recalculates the Rate
Lot Size recalculates the Duration
OFFSET DAYS FOR EARLY JIT (EJIT):
The M SEARCH algorithms use this TDAT parameter. Offset Days for Early JIT (EJIT) specifies the number of days before the JIT date when the Very Early Penalty Cost (VHC) takes effect.
OFFSET DAYS TO LATE JIT (LJIT):
The M SEARCH algorithms use this TDAT parameter. Offset Days for Late JIT (LJIT) specifies the number of days after the JIT date when the Very Late Penalty Cost (VRP) takes effect.
YIELD FACTOR:
Certain scheduling problems have yield structures that vary by activity. The yield factor concept supports this class of problem. This factor is typically a value between zero and one and is used to calculate the number of units of a scheduled activity that must be started to get a given, required number of completed units.
OPERATING COST:
The Operating Cost is the cost of the operation in dollars per time unit. If the dollar units are $1000 and the data time unit (from the CMAN table) is Hours, then the operating cost should be specified in $1000/hour.
HOLDING COST:
The Holding Cost, which is sometimes called Inventory Cost, is the cost per year to hold inventories. It is typically computed as a function of the plant's cost of capital. The holding cost is expressed in dollar units per inventory unit per year (regardless of the choice of data time unit). Thus, if the dollar units are $1000 and the inventories are in gallons, then the holding cost is in $1000/gallon/year.
RUNOUT PENALTY:
The Run out Penalty is used to drive the LATE, COST, and MOVE algorithms when there is an infeasibility due to inventory runout in the model. The units of this penalty are the same as for Holding Cost, dollars per unit per year.
VERY EARLY PENALTY COST(VHC):
The M SEARCH algorithms assess this additional penalty cost (dollars per unit per year) on top of the Holding Cost if an activity is scheduled more than a specified time before the Just-in-Time date. The EJIT parameter specifies the additional time before the JIT date when this penalty takes effect.
VERY LATE PENALTY COST (VRP):
The M SEARCH algorithms assess this additional cost (dollars per unit per year) on top of the Runout Penalty, if a production activity is scheduled more than a specified time after the Just-in-Time date. The LJIT parameter in TDAT specifies the additional time beyond the JIT date when this penalty takes effect.
LATE ABSOLUTE PENALTY COST (AHP):
The M SEARCH algorithms assess the Late Absolute Penalty Cost (ARP) when an activity is produced later than a specified absolute time. The absolute late penalty is most commonly used to represent a time after which production of the activity will cause material infeasibility.
ABSOLUTE EARLY COST (AHC):
The M SEARCH algorithms assess the Early Absolute Penalty Cost (AHC) when an activity is produced earlier than a specified absolute time. The most common use of the absolute early time is to represent a time before which an intermediate or untracked raw material will not be available. These times are often calculated using the M JIT EARLY command.
Keywords: None
References: None |
Problem Statement: Are binary interaction parameters (BIPs) estimated when using the Aspen HYSYS property methods HYSPR, HYSSRK, HYSGLYCO? | Solution: These models are primarily intended for supporting the use of Aspen Properties by Aspen HYSYS and usually, the HYSYS component databank contains data for its binary interaction parameters:
GLYABV: Glycol activity binary parameters
GLYKIJ: Glycol EOS binary parameter
HPRKIJ: HYSYS PR binary parameter
HSRKIJ: HYSYS SRK binary parameter
Note: when using property package from Aspen HYSYS, it is recommended to place the HYSYS databank in the search order before other databanks.
However, if these parameters are not available in the HYSYS databank, they can be estimated by Aspen Properties. For example, both HPRKIJ/ HSRKIJ can be estimated from critical volume (Vc) as follows:
Note: Aspen HYSYS uses the same estimate, but may obtain slightly different values because the databank in the Aspen Physical Property System stores values to a greater precision. Also, Aspen HYSYS reports all parameters, while the Aspen Physical Property System does not report estimated parameter values.
Now, Aspen Plus does not display all the property parameters on the parameters form, so if you would like to check these estimates, first we need to go the Home Ribbon and select Tools | Retrieve Parameters. After that, the HYSYS BIP parameters will be available under Methods | Parameters | Results | Binary Interaction. The parameters GLYKIJ, HPRKIJ and HSRKIJ can be found on the Scalar tab, while the GLYABV will be reported on the T-Dependent section.
Keywords: HYSYS, HYSPR, HYSSRK, HYSGLYCO, GLYABV, GLYKIJ, HPRKIJ, HSRKIJ, Binary Interaction, Estimation.
References: None |
Problem Statement: How to use XLR Viewer to analyze and troubleshoot solutions in PIMS AO | Solution: PIMS-Advanced Optimization (PIMS-AO) provides a new tool since V7.3 to give the user the ability to analyze run results in a straightforward but extremely powerful environment. This tool, the XLR Viewer, is amazingly capable as a problem analysis tool. But it can also be used to provide the user with great insights into his model itself, and in understanding the true ramifications of the optimal solution.
With PIMS-AO V7.3 we are introducing the XLR Viewer. This tool provides, in a single modern GUI environment, the capability to analyze all aspects of the model and the solution from beginning to end. An example of the XLR Viewer is shown below:
The XLR Viewer allows the user to investigate just about any aspect of the mathematical model and solution. Some of the study sections it provides are:
Options - a view of all of the variable settings used for the model creation and solution
Variables - analysis of all of the variables in the model, such as purchases, sales, flows, process limits, capacities, properties, etc. This includes initialization and values for each iteration in the solution as well as graphical displays.
Equations - A display of all of the equation in the model. These are categorized by material and utility balances, capacity constraints, control rows, recursion balances, specification equations, etc. Graphical display of each equation is also provided by iteration.
Diagnostics - This includes data and graphical display by iteration of active bounds, largest changes from iteration to iteration, largest residuals, largest feasibility slacks, and largest shadow prices
Infeasibilities - This section only contains information if the final solution is infeasible. It provides a display of the infeasible equations and variables.
Each of these items can be studied at many points along the way from initial model setup through final solution.
As shown in the above screen capture, individual variables or other items can be selected and plotted to see how they behaved during the solution process. The ones in the simple model above are straightforward and well behaved. But here is a much more interesting one from a more complex model that had some difficulty solving:
An additional capability of the XLR Viewer is that it provides a direct link to the Matrix Analyzer. By simply double-clicking on an equation or variable, the Matrix Analyzer is activated and displays all of the information regarding that equation or variable. A sample of the Matrix Analyzer is shown below.
The PIMS Matrix Analyzer has been used for many years as a powerful tool for analyzing the mathematical structure of the PIMS mathematical model. By providing the direct link between the XLR Viewer and the PIMS Matrix Analyzer, the user can go directly from the information in the XLR viewer to the detailed mathematical model analysis. Using these two tools in tandem, the LP can't hide anything from them. Everything is there to be seen.
Keywords: None
References: None |
Problem Statement: At what drive location to place any custom constraint file for Optimization? | Solution: The default location to place any custom optimization constraint file is: C:\ProgramData\AspenTech\Aspen Utilities Planner V10.0
If “Program Data” folder is not visible, please make it visible from Administrative mode.
From this location, both Aspen Utilities Planner Optimization and Excel Add-in Optimizer should be able to access the constraint file during optimization run.
Key Words
Optimization, Custom Constraint, Add-In
Keywords: None
References: None |
Problem Statement: EDR does not open since updating to Solidworks 2018 | Solution: There have been reports where after updating to Solidworks 2018, EDR won’t work anymore and it will show a message saying that “Aspen EDR has encountered an error and will be closed” on every attempt to open the application, and poiting to a log file in a speficic location (usually C:\Users\[users]\AppData\Local\AspenTech\AspenEDR VX.X).
As confirmation, you can look for the log file mentioned in the error message you see when trying to open EDR. The log file should contain information like the following:
[08:35:32]:[ATVDataServer]: Unhandled Exception Could not load file or assembly 'AtvVCDll.dll' or one of its dependencies. The specified module could not be found.
at ATVDataServer.ATVApp.Class_Initialize_Renamed()
at ATVDataServer.ATVApp..ctor()
at ATVDataServer.ATVService.LoadNewApp(String AppName, Int32 Lang, Int32 Units)
at AspenTech.EDR.ShellApp.BJACAppHelper..ctor()
at AspenTech.EDR.ShellApp.BJACAppHelper.GetBJACAppHelper()
at AspenTech.EDR.ShellApp.App.InitHeatExchanger()
at AspenTech.EDR.ShellApp.App.OnStartup(StartupEventArgs e)
[08:36:18]:[ATVDataServer]: Unhandled Exception Could not load file or assembly 'AtvVCDll.dll' or one of its dependencies. The specified module could not be found.
at ATVDataServer.ATVApp.Destroy()
at ATVDataServer.ATVApp.Finalize()
This has an easy fix, you only have to repair the EDR installation, which can be done by using the media (USB or Disc) you used to install the software.
Keywords: Solidworks, EDR, ATVDataServer
References: None |
Problem Statement: When performing a line sizing for a PSV in the Safety Analysis environment in Aspen Plus or Aspen HYSYS, you have the option to change the value for the pipe roughness. In some specific situations the value of roughness does not impact the calculated pressure drop for your line. | Solution: A portion of the pressure drop calculation involves the evaluation of the friction factor, which, in turn, strongly depends upon the type of relieving flow the system surpasses.
According to Moody’s Chart (1944) for friction factor (see picture below) for any given fluid undergoing laminar flow (~Re<10,000), the friction factor follows a linear function of Reynolds number only and becomes independent of pipe roughness.
Therefore, under laminar scenario, any changes made to roughness on the PSV Line Sizing environment will not affect the calculated pressure drop. It might be a good idea to check for high viscosity values, since they contribute significantly to decrease the Reynolds number.
Note: It is important to notice that the Safety Analysis Environment does not explicitly report Reynolds number. Instead, it reports the type of relieving flow for each scenario and fluid properties at the inlet and outlet of the pipeline. If you are interested in calculating this value, you can generate a Line Sizing report containing all fluid properties necessary for you to obtain Reynold’s Number. This information is also displayed at the tab Line Sizing as demonstrated in the picture below.
For more information about friction factor and Moody Chart, please refer to Perry’s Handbook 7th ed. pp. 6-10 and 6-11.
Keywords: PSV; roughness; Line Sizing; Safety Environment; Analysis;
References: None |
Problem Statement: What ports need to be open between Mtell Server, Client and MS SQL Server? | Solution: Only port 1433 is needed to be open between any Mtell server or client and the MS SQL Server machine.
Ports 4501-4510 are also used between the Mtell server and Mtell client machines if you plan to install the rich client applications on any end user machines. They will all need two-way TCP communication, with ports 4504 and 4505 requiring two-way UDP communication as well.
You will also need port 5093 and 5094 TCP/UDP two-way communication for AspenTech licensing and will need to have relevant IIS ports open if Mtell view is being used.
Keywords: None
References: None |
Problem Statement: A closed propane refrigeration solves in Sequential Modular mode but when switching to Equation Oriented mode it fails. | Solution: A closed loop flowsheet can not be modeled in EO the same way as it is modeled in SM. In SM the Aspen Hysys flowsheet does not require a recycle logical operation to converge at the Loop. The same model in EO mode will return several non-linearity errors due to the closed nature of the model. The solution is to break the loop then use EO connection equations to pass variables across the broken stream connections.
The model attached shows how this can be modeled. The loop is broken in a position of the flowsheet that is most efficient with regards to optiomizing the number of variables being passed, thereby the number of connection equations required. The stream out of the Condenser (CHILLER) and inlet to the flash drum (S-DRUM) will be the connection location.
The EO variable connection equation can be defined to connect individual variables, however in this case a port connection is used. A port is a collection of several variables, this ability to group several variables together enables the user treat a set of variables the same way in the flowsheet. A port is created at the block level of the CHILLER and S-DRUMIN. A port type can be generic, i.e different variable types can be defined, or material, whereby only a specific set of variables can be defined for that port. To define a port, the name, port type and variables passing through that port must be specified. A port called OUTLET is created for the CHILLER variables and a port called INLET is created for the S-DRUMIN variables. The variables included in the port are the variables specified as constant in EO mode as these were the variables that were user input in SM.
A simple OOMF query can be used in the control panel command line to verify that the ports have been created correctly in each block.
Next, in the EO Connection form at the flowsheet level, an EO Connection is created to connect the outlet port and inlet ports of CHILLOUT and S-DRUMIN, respectively. To ensure the ports get connected, the Port Connection check box is selected and the enable box ensures the connection is active.
The flowsheet is constrained to calculate flow of refirgerant by making condenser (COND) duty constant, using an EO spec group (FIX FLOW).
Positive heat flow in the Hysys heater block, will ensure positive material flow through the loop and the concept is that the duty demand is calculated by the process side which is not part of this flowsheet, therefore the duty is made constant.
Modelling tips: Use the reset and/or validate EO options when making changes to the flowsheet variables in EO mode. This enables the solver build the changes in the EO matrix and exposes any errors before solving.
Keywords: Closed loop in EO, singularity, non-linearity, EO refrigerant loop
References: None |
Problem Statement: Aspen Batch Modeler by default is not handling solid components in the component list, but sometimes batch processes include solid catalyst. How to include solid component as catalyst in Aspen Batch Modeler? | Solution: In Aspen Batch Modeler, in the Configuration folder| Reaction tab there is an option to select: "Solid catalyst present" and then one can include a mass of the solid catalyst and volume/density of the catalyst.
This option is considered for the scenario when the reaction occurs in the pot only.
There is no detailed explanation in Aspen Batch Modeler help files, how mass of the catalyst is included in the calculations of the reaction rate, but this option works similar as similar setup in Aspen Plus RPlug block: “The specified or computed catalyst mass is used to calculate the species generation rates when the rate basis is specified as Cat (Wt) for a reaction that occurs in this reactor.
By default, if a catalyst is present in the reactor, the computed catalyst volume is subtracted from the reactor volume when computing the residence times and species generation rates. One can turn off this behavior by selecting Ignore catalyst volume in rate/residence time calculations.
The catalyst properties are not otherwise incorporated into RPlug (Pot) calculations. Reaction rate specifications supplied to reactor should account for the effects of catalysts including mass/heat transfer effects that may cause the reaction to occur at conditions different than those of the bulk fluid.”
Please refer to Aspen Plus online- help for more details, depending on version please check the chapters:
V8.0-V8.6
Simulation Environment Forms| Blocks| RPlug| RPlug Setup Form| RPlug Setup Catalyst Sheet
Using Aspen Plus| SM Flowsheeting Tools and Reactions| Specifying Reactions| Specifying Power Law Reactions for Reactors and Pressure Relief Systems| Rate-Controlled Reactions
Using Aspen Plus| SM Flowsheeting Tools and Reactions| Specifying Reactions| Reactions with Solids| Stoichiometry and Reaction Rate
V8.8-V10
Using Simulation Environment| Simulation Environment Forms| Blocks| RPlug| RPlug Setup Form| RPlug Setup Catalyst Sheet
Using Simulation Environment| Specifying Reactions| Specifying Power Law Reactions for Reactors and Pressure Relief Systems| Rate-Controlled Reactions
Using Simulation Environment| Specifying Reactions| Reactions with Solids| Stoichiometry and Reaction Rate
Keywords: Solid Catalyst, Aspen Batch Modeler, Reaction with Catalyst
References: None |
Problem Statement: Sometimes we have parameters that fit a liquid pure component viscosity model only within a certain temperature range. Extrapolating the results provided by an equation to temperature values out of its valid range may incur in significant errors. To account for the deviations caused by this procedure, you may be interested in adding a second set of parameters that can well adjust the model when working in a scenario containing temperature values not covered by the first set.
Aspen Plus allows you to create a second set of parameters to fit your pure component viscosity at different temperature ranges. This article provides an example file and describes a step-by-step solution on how to do it. | Solution: The pure component viscosity model used in Aspen Plus is represented by the pure component parameter MULDIP-1.
To define a second set of parameters (MULDIP-2), follow the steps below:
1. After you have defined your components and property method, add a second method in the Properties Environment | Methods | Selected Methods | New | Name your Method (here called NRTL-2) | OK.
2. Click on the new method created and go to the tab Models. Find the property liquid pure component viscosity (MUL) and change the data set from 1 to 2.
Note: This procedure can be replicated to other properties (e.g. vapor viscosity – MUV)
3. In Parameters | Pure Component | New | T-dependent correlation | Miscellaneous find the second set of parameters for pure liquid viscosity equation MULDIP-2, select it and click OK.
4. Double Click your new form MULDIP-2 and you’ll be able to input new constants for your liquid pure component viscosity equation.
Note: make sure you use the correct property method when working with your simulation, as the parameter set to be used will be chosen respecting the method selected.
An example file has been attached (V10) to this article to illustrate the procedure described with Water as a component.
Keywords: Viscosty; MULDIP-2; MULDIP-1; Pure Component; Parameters; Aspen Properties;
References: None |
Problem Statement: Upgrade of GML_V10.0.CAS library fails with an error message. | Solution: There is an known issue in Aspen SCM related to RLIBMGR ,COLLECT and LINK which can result in error while trying to upgrade GML_V10.0.CAS .
Please follow the below steps to resolve the error:
1. Open the model.
2. Copy RLIBMGR from the GML library by running the below command in the Command Window
COPY RLIBMGR “C:\Program Files\AspenTech\Aspen Caps\Shared Libraries\GML_V10.0.CAS”
3. Run COLLECT
4. Run LINK
5. Save the model and install the library.
Keywords: None
References: None |
Problem Statement: How to model NAOH Heat of Dilution in Aspen Plus? | Solution: When using Aspen Plus to model the NAOH heat of dilution, users will use Electrolyte NRTL method and the old MNAOH insert file. The aim of MNAOH insert file is to add one more chemical equilibrium on top of the regular chemical equilibrium from Electrolyte Wizard.
Equilibrium NAOH + 2.0 H2O <--> NA+ + H5O3-
Please review the attached example Aspen Plus file in this solution. The model successfully captures the NAOH heat of dilution and results in temperature increase to 142 F by dissolving 50 % NAOH to 20 % NAOH solution.
To build the model, users will follow the steps below.
1. Add NAOH and H20 in component list and use electrolyte wizard to generate the regular chemical equilibrium.
2. Import the MNAOH insert file by using "File > Import > File " and navigating to Eleclns directory (C:\Program Files (x86)\AspenTech\Aspen Plus V9.0\GUI\Elecins)
3. Type NAOH for component NAOH and use merge to resolve ID conflicts.
4. Build the Simulation Model by adding 50% NAOH, Water, 20% NAOH streams and Mixer Block.
5. Run the simulation and check the 20 % NAOH stream temperature. It shows 142 F as expected.
Keywords: NAOH, Dilution of Heat, Example
References: None |
Problem Statement: This knowledge base article describes how to control the coloring schemes for activities on Planning Board. | Solution: PBACLRS set contains the list of coloring Schemes for activities on Planning Board. Description mentioned in this set is visible on the Format tab of the Planning Board Ribbon.
PBACCTL is the Control table for the Coloring Schemes.
PROIND - Should be filled with either PRO or IND, based on the coloring scheme .If “IND” is used, user must create a RULE to fill in MAKI(@,COL) with the color for the IND .The predicate of this rule must be: ASSIGN_IND_BASED_ACTIVITY_COLORS_FOR Code of PBACLRS
COLTAB -Holds the table where the color configurations are done. The Rowset is the attribute based on which coloring should be done. The code of SCOLOR set (Codes have been created for different Hex colors) should be filled in this table.
PROGRP -For all PRO based coloring, PRODATA should have a column (if it does not, it should be added and filled) and that should be mentioned here.
LABWIDTH- Color Key Label Width
MAXROWS- Maximum Rows in Color Key.
WPB- Send to Web PB?
DEFCOLOR- Default Color
AUTOCAL- Auto Recalculation
RPEG- Run Demand Pegging Logic? [Y|BLANK]
OVERRIDE- Allows to run an override when the coloring scheme is applied
PBTACLNG - Language table for Coloring Schemes.
Keywords: None
References: None |
Problem Statement: In Aspen Plus, the user can write Fortran Expressions (How do you write Fortran expressions?, Aspen Plus V10 User Models Manual) but in some cases Aspen Plus can shows the following error: "Fortran error declaration begins with invalid keyword or contains invalid variable name". | Solution: To achieve successful compilation of the Fortran statements, please ensure all these rules are acomplish:
The variables beginning with A through H, or O through Z, are double precision real. Variables beginning with I through N are integer. Use double precision functions (for example, DSQRT) and double precision constants (for example, 1D0).
Note: Double Precision (floating point numbers) are used to represent fractional values, or when a wider range is needed than is provided by fixed point (of the same bit width) and may be chosen when the range and/or precision of single precision would be insufficient.
Do not use variable names beginning with IZ or ZZ.
Do not use Fortran keywords or the names USE, INCLUDE, or CALCXL as variable names. As this are functions to inserts a file into the source program.
Because Fortran is column-sensitive, this table shows how to do certain things:
The user can call their owns subroutines or functions and can use labeled or blank (unlabeled) COMMON blocks.
Fortran variables you define on the Specification sheet cannot be placed in a COMMON.
Do not use IMPLICIT, SUBROUTINE, ENTRY, RETURN, END statements, nor arithmetic statement functions.
Note: Each reference to a function, subroutine, or entry must use an actual argument list that agrees in order, number, type, and name with the dummy argument list in the corresponding FUNCTION, SUBROUTINE, or ENTRY statement.
READ and WRITE statements to numbered file units (as in WRITE (NTERM,*)) only work if the same compiler was used to compile the code containing these statements and the code which opened the files. Aspen Plus now uses the Intel Fortran compiler to open its built-in units for the report file, history file, and control panel.
Note: Aspen Plus V10 was compiled with the Intel Fortran compiler 2013 SP1 and Microsoft Visual Studio 2013 Update 3.
Keywords: Fortran, Statements, Rules, In-Line, Calculator, Intel Fortran compiler 2013 SP1, Microsoft Visual Studio 2013 Update 3
References: None |
Problem Statement: When the user select an unit operation that works with PSD, why the message "PSD ATTRIBUTE IS NOT PRESENT IN SUBSTREAM 'MIXED', PSD MESH OF SUBSTREAM 'CIPSD' WILL BE USED WITH SOLIDS EVENLY DISTRIBUTED IN EACH INTERVAL" appears? | Solution: This message appears because the solid is specify in the Mixed Tab instead of the CI Solid Tab of the inlet stream.
For example, a Spray Tower is a block that requires a solid distribution, it's necessary that the user inputs the solid in the CISOLID Tab of the inlet stream and also specify a PSD. (How do I set up a Particle Size Distribution (PSD) for solids modeling in Aspen Plus?).
Note: Ensure that the MIXNCPSD stream class is selected in the Setup/Stream Class folder.
Keywords: CISOLID, MIXNCPSD, MIXED, PSD, Weight fraction
References: None |
Problem Statement: Sometimes you need to add new components to your Aspen Plus Dynamics simulation but you do not want to rebuild an entire Aspen Plus Simulation from scratch, re-export it and end up losing all the work you have already done with your dynamic model.
This article explains how the user can add new components to the dynamic simulation. | Solution: KB article 119082-2 explains how you can update blocks, controllers and components from within the steady state simulation through the use of a built-in update tool within Aspen Plus. Alternatively, if you are willing to add new components only (or even change the property package), it might be useful to just update the Aspen Properties Definition File instead of updating the whole flowsheet. In order to that, follow the steps below:
1) Open your bkp file - the one that generated the Aspen Plus Dynamics file.
2) In the properties environment, add the new component to your component list.
3) Check for the new parameters and run the properties environment simulation to its completion.
4) Go to File > Export > choose file type as *.apprdf file and save at a known location.
5) Open your Aspen Plus Dynamics file (you may close your Aspen Plus Steady State file if you will).
6) In Component List, go to Properties, Configure and select Use Properties Definition file.
7) Browse the Problem Definition File (*.apprdf) you have just saved and you will see that the new component will be available to you in the component list.
Keywords: Update; New Component; Aspen Plus Dynamics;
References: None |
Problem Statement: How to clear Recent Models window in Aspen Plus | Solution: When opening Aspen Plus, there is a default window showing recently opened files.
To clear the files that show up in Recent Models, please follow these steps:
Make sure that all Aspen Plus files are closed.
Open Windows explorer and access the following route: C:\Users\username\AppData\Local\AspenTech
Note: you may have to enable "hidden folders" on your computer to see the AppData folder.
Open the View tab in your explorer window
Click on Options button
Go to View tab and toggle the "Show hidden files, folders, and drives"
Click on ok and close the window
From the available folders select the Aspen Plus version from where the Recent Models should be cleared.
Inside the Aspen Plus folder look for the file application.settings and open it using the Notepad or Wordpad.
Search for the entry <ApplicationSettings.MostRecentlyUsedFiles>. You will see below the <s:String> entries with recent files routes.
Select the route of the file you want to clear and delete the whole line. If you want to have the Recent Models form totally empty, remove all the entries listed between the lines <ApplicationSettings.MostRecentlyUsedFiles> and </ApplicationSettings.MostRecentlyUsedFiles> then save the file and close it.
<ApplicationSettings.MostRecentlyUsedFiles>
<s:String>C:\Program Files (x86)\AspenTech\Aspen Plus V10.0\GUI\Examples\Bulk Chemical\Triple-Effect Evaporator.bkp</s:String>
<s:String>C:\Program Files (x86)\AspenTech\Aspen Plus V10.0\GUI\Examples\Bulk Chemical\cumene.bkp</s:String>
</ApplicationSettings.MostRecentlyUsedFiles>
Open Aspen Plus to see the Recent Models empty.
To clear Recent Models from Aspen HYSYS, please review the article How to clear Recent Models window in Aspen HYSYS
Keywords: Recent models, recent files, clear, Plus
References: None |
Problem Statement: A closed propane refrigeration solves in Sequential Modular mode but when switching to Equation Oriented mode it fails. | Solution: A closed loop flowsheet can not be modeled in EO the same way as it is modeled in SM. In SM the Aspen Hysys flowsheet does not require a recycle logical operation to converge at the Loop. The same model in EO mode will return several non-linearity errors due to the closed nature of the model. The solution is to break the loop then use EO connection equations to pass variables across the broken stream connections.
The model attached shows how this can be modeled. The loop is broken in a position of the flowsheet that is most efficient with regards to optiomizing the number of variables being passed, thereby the number of connection equations required. The stream out of the Condenser (CHILLER) and inlet to the flash drum (S-DRUM) will be the connection location.
The EO variable connection equation can be defined to connect individual variables, however in this case a port connection is used. A port is a collection of several variables, this ability to group several variables together enables the user treat a set of variables the same way in the flowsheet. A port is created at the block level of the CHILLER and S-DRUMIN. A port type can be generic, i.e different variable types can be defined, or material, whereby only a specific set of variables can be defined for that port. To define a port, the name, port type and variables passing through that port must be specified. A port called OUTLET is created for the CHILLER variables and a port called INLET is created for the S-DRUMIN variables. The variables included in the port are the variables specified as constant in EO mode as these were the variables that were user input in SM.
A simple OOMF query can be used in the control panel command line to verify that the ports have been created correctly in each block.
Next, in the EO Connection form at the flowsheet level, an EO Connection is created to connect the outlet port and inlet ports of CHILLOUT and S-DRUMIN, respectively. To ensure the ports get connected, the Port Connection check box is selected and the enable box ensures the connection is active.
The flowsheet is constrained to calculate flow of refirgerant by making condenser (COND) duty constant, using an EO spec group (FIX FLOW).
Positive heat flow in the Hysys heater block, will ensure positive material flow through the loop and the concept is that the duty demand is calculated by the process side which is not part of this flowsheet, therefore the duty is made constant.
Modelling tips: Use the reset and/or validate EO options when making changes to the flowsheet variables in EO mode. This enables the solver build the changes in the EO matrix and exposes any errors before solving.
Keywords: Closed loop in EO, singularity, non-linearity, EO refrigerant loop
References: None |
Problem Statement: How does AFR handle Cold Standby cases? | Solution: Cold Standby events are handled by AFR in the following way:
If an event is selected for cold standby, then when the event is NOT being used (or is not on a solved path) then the software stops the aging process. That is, while the event is not used it will not incur age (or get older). Once the event is being used (or is on a selected path), the event will begin the aging process. When multiple events are connected to a rate multiplier, then the following occurs:
In the case below, if all events are selected for cold standby, then “Event2” and “Events3” will not be incurring age. As opposed to “Event4” and “Event5” will be as they are a part of the selected path (green path).
Key words
Cold Standby
Keywords: None
References: None |
Problem Statement: How to change the default database location for Aspen Utilities Planner Optimization? | Solution: By default, all optimization databases are selected to be placed in C:\ProgramData\AspenTech\Aspen Utilities Planner Vx\Example Databases.
However, this default location can be changed from Aspen Utilities Planner > Optimization > Configure
From Database Configuration, please browse desired location to place the databases. Please make sure to keep all databases in same location.
Key Words
Optimization, Databases, Database Locations
Keywords: None
References: None |
Problem Statement: This knowledge base article describes on how to configure User Guidance in Aspen Plant Scheduler. | Solution: Open CNTLS and Set the (ERNG) Enforce Time Range Constraints for Drag and Drop[Y|N] - YES
Possible Values:
YES (or Y): The Activity Drag and Drop Constraint feature is turned on.
NO (or N): (Default) The Activity drag and drop constraint feature is turned off
RELAX: If you drag and drop an activity to a restricted location, a warning message will appear asking you to confirm the action. If the restricted location is a facility that is not listed in the FACI table an additional warning message will appear.
SILENT: If you drag and drop an activity to a restricted location, a warning message will not appear asking you to confirm the action. Also, if the restricted location is a facility that is not included in the FACI table, no additional warning message will appear.
Set ERANGE AND LRANGE in the MAKF table are optional. If the ERANGE/LRANGE values are specified in MAKF and the CNTLS(ENRG) switch is set to YES, then the below colors display
• Dark green
• Light green
• Yellow
You can also set the order of color preferences for dragging and dropping on these facilities in the FACI table.
If a facility is labeled as Alternative 1, then the dark green color is applied to the facility as the default. If a facility is labeled as Alternative 2, Alternative3, Alternaive4, and so on, the light green color is applied to the facility.
For facilities that are not assigned an alternate number in FACI, if the CNTLS(AFO) switch is set to YES, then the color yellow is applied to the facility and you are allowed to perform a drag and drop override. If the CNTLS(AFO) switch is set to NO, then you will not be permitted to perform a drag and drop onto this facility.
If an activity is dragged beyond a valid time range, the arrow line color changes from green to red. After you release the dragged activity, an error message displays, informing you of the invalid time range.
Keywords: None
References: None |
Problem Statement: Why sometimes the Utilities Planner Optimizer Editor cannot update databases? | Solution: Before starting to open the Aspen Utilities Planner and Excel Add-in file, please make sure to copy the following database files from the folder:
ProfileData.mdb
DemandData.mdb
TariffData.mdb
Interface.mdb
And paste the files into the following path:
C:\ProgramData\AspenTech\Aspen Utilities Planner V10.0\Example Databases
Missing this step may cause these databases not updated from optimization Editor.
Key Words
Optimization, Data Editor, Add-In
Keywords: None
References: None |
Problem Statement: How do I activate/deactivate the Uniform Section option in an Aspen HYSYS Column? | Solution: The Uniform Section option can be found in the Column editor under Rating tab | Towers section.
When checked this option, will do all Column stages to have the same physical setup (diameter, tray type, etc.). You may notice this one is grayed out so you won’t be able to activate/deactivate the option.
To adjust this setting, you must enter to the column environment and enter to the Column Main Tray Section editor. Then move to Rating | Sizing | Section Properties. Here you will find the options Uniform Tray Data and Non Uniform Tray Data to adjust as needed.
If you go back to the main environment, please notice the change is applied depending of your selection.
Keywords: Column, Towers, Uniform Section, Uniform Tray Data, Non Uniform Tray Data.
References: None |
Problem Statement: Pre- requisites/Tasks to complete before starting the V10.0 Aspen Collaborative Forecasting Installation. | Solution: Aspen Collaborative Forecasting (CF) can not be installed before both JAVA and Apache Tomcat are installed and configured.
1. Install Java JRE 1.8 build xxxx.
2. Install and configure Apache Tomcat.
3. Setup Oracle or SQL Databases
Create two (2) Oracle or SQL Databases: (1) Operational and (1) Stage
Supported Oracle Databases: 12.1.0.2 & 11.2.0.4
Supported SQL Databases: Microsoft SQL Server 2016 SP1 Enterprise or Standard Edition, Microsoft SQL Server 2014 SP2 Enterprise or Standard Edition,
Microsoft SQL Server 2012 SP2 Enterprise or Standard Edition
Make sure the SQL Server Native client is installed in Demand Manager machine if CF Database is MS SQL Server.
4. Install Aspen SCM V10.0 .
5.Install Aspen Collaborative Forecasting (CF).
Keywords: None
References: None |
Problem Statement: How do you model heat transfer in a Finned Tube? | Solution: The heat transfer observed in the fin tube are:
1) The heat transfer from hot liquid to the finned tube ( convection)
2) The heat transfer throughout the metal ( conduction).
3) Dissipation of heat to the surroundings ( convection)
For one dimensional fin expose to the surroundings at a ambient temperature, the system can be defined with the following differential equations:
Where T is temperature; h is heat transfer coefficient, P is perimeter, A is heat transfer area and k is thermal conductivity
Boundary conditions
At x=0, T= Tin
Other boundary conditions could be used, depending on the physical situation. For example, if we consider the fin is very long and the temperature at the end of the fin is essentially that of the surrounding fluid.
Model Temp
n as integerparameter (100);
L as realparameter(10);
x as LengthDomain (highestorderderivative:2, length:L, spacingpreference:L/n);
A as area (fixed,50);
Tin as Temperature (description:"inlet temperature");
K as conductivity (fixed, 16);
h as heat_trans_coeff(fixed,5);
peri as length(fixed, 30);
T as Distribution1D(XDomain is X) of Temperature;
in_f as input materialport;
out_p as output materialport;
// feed temperature
Tin = in_f.T;
// product temperature
out_p.T = T(n);
//Boundary conditions:
T(0) = Tin;
T(n).ddx = 0;
//Equations:
for x_ in x.interior do
k*A*T(x_).d2dx2=h*peri*T(x_);
endfor
end
To view the profile of temperature, you can right click the block, Explore and navigate to the block T (distribution) then double click ValueProfile. Alternatively, you can also create a profile plot in the flowsheet or in the model.
Keywords: Ambient Temperature, Dissipation, convection, conduction and thermal conductivity
References: : Holman J.P. ," Heat Transfer" , 8th edition, McGraw-Hill publications |
Problem Statement: Is it possible to assign different stream classes to individual streams? | Solution: Aspen Plus allows the user to define a stream classes with the following options.
CONVEN: Use when the simulation doesn't involve solids or when solids are salts defined using Chemistry.
MIXNC: Use when you have nonconventional solids present but no particle size distribution.
MIXCISLD: Use when you have conventional solids present but no particle size distribution.
MIXNCPSD: Use when you have nonconventional solids present with particle size distribution.
MIXCIPSD: Use when you have conventional solids present with particle size distribution.
MIXCINC: Use when you have both conventional and nonconventional solids but no particle size distribution.
MCINCPSD: Use when you have both conventional and nonconventional solids present with particle size distribution.
In Stream Class Ribbon, the user can:
Define the stream class for flowsheet sections or the entire simulation in the Flowsheet Tab.
Define the stream class for a specific stream in the Streams Tab. The Stream Class is marked in gray because it isn't selected, when the user click in the stream class it will turn blue and mark as incomplete.
Keywords: Stream Class, Section, Specific Stream
References: None |
Problem Statement: In AtOMS, How to filter the issued movements as per the Start date in the TimeFrame option for the Movement Summary page? | Solution: In AtOMS, user can select the start date range from which he/she wants to see the movements.This in turn helps in removing the old dated issued movements compared to the Start date selected from the movement summary screen.
To use this filter option, please try the below solution :
1. Open AtOMS > Go to the 'Issued Movement' summary page.
2. Select Change TimeFrame option from the Tool bar below the Menu bar
3. Select the Start date as per requirement, the End date is fixed by AtOMS itself.
Example : Here we select the start date as 26th April, which means all movements Issued post 26th April must be seen in the screen , the old dated issued movements must get filtered out)
4. Once the start date range is selected, uncheck the option 'Show Issued and Active'
5. After unchecking this option , click okay.
6. In the Movement Summary Page you will see that the Issued Movements have been filtered by the Start Date range selected.
(As per example you will see only those movements which were issued after 26th April are to be seen on the screen )
KeyWords
ATOMS, Issued Movements, Filter, etc.
Keywords: None
References: None |
Problem Statement: Is it possible to know the duty required in the intermediate streams not displayed on the Delayed Coker unit? | Solution: All the calculations internal to the Delayed Coker model are done on the basis of the kinetic lumps. The model is primarily used for predicting yields. However, there are certain heat terms that can be tracked in the EO model.
The Delayed Coker unit is modeled as follows: the furnace as a combination of a mixer/flash blocks and reactors. Each block has its own heat loss term. First there is a feed heater that heats the feed from the inlet temperature to 400C with no reactions. After that the feed goes to a series of three reactors and after each reactor there is a flash. Each of these will have a heat duty term associated with it. You can find these on the Solver | EO Variables page.
The names of the variables are as follows:
FDHTR.BLK.HEAT_LOSS
FURN1.BLK.HEAT_LOAD
FURN2.BLK.HEAT_LOAD
FURN3.BLK.HEAT_LOAD
PFLASH.BLK.HEAT_LOSS
PFLASH.BLK.HEAT_LOSS
PFLASH.BLK.HEAT_LOSS
Note that the HEAT_LOSS variables will have the opposite sign, so if heat is input into the system, the heat loss will be negative. The HEAT_LOAD terms will be positive if heat is input to the system. Also, they are currently different units (the first one has units of MJ/HR and all others are in Watts). Also, it can be a bit time consuming all of these in the EO Variables list.
If you decide you want to use these variables, it would be recommended pasting the values to a Spreadsheet. To find the variables, click the Enter Query button at the top right of the EO Variables page.
Use the following three queries to find the 7 variables:
FDHTR*HEAT*
FURN*HEAT*
PFLASH*HEAT*
Note also, that once you paste the variables to the HYSYS Spreadsheet, it will automatically do a unit conversion back to the base HYSYS units. So, you easily will be able to use it to report the duty in the desired units.
Keywords: Delayed Coker, Furnace, EO variables, Heat Loss, Duty.
References: None |
Problem Statement: This knowledge base article describes the Inventory problems caused by Inventory Run outs and Inventory Over runs and methods to view those problems. | Solution: Inventory problem can arise when there is inventory shortage(Under) or when inventory(Over) is above a specified limit.
Inventory Run Outs - An inventory run out occurs when a product's inventory level falls below the minimum in a particular time slice. The minimum is determined by the MAKE Ignore Order Point (IGOP) parameter in the CMAN table.
If IGOP is set to YES, the minimum is zero.
If IGOP is set to No, the minimum comes from the Order Point (OP) column of the TDAT table.
Inventory Overruns - An inventory overrun occurs when the inventory level exceeds the maximum as defined in the Maximum Storage (MS) column of the TDAT table.
Methods to View Inventory Problems in Aspen Plant Scheduler:
1. Inventory Problems Report
2. Problems Report:
Keywords: None
References: None |
Problem Statement:
This knowledge base article describes the method to view detailed production information for a product on production (demand) and Consumption(Supply) using Supply Demand Balance Report. | Solution:
Supply Demand Balance Report can be used to view detailed production information for the product in each time slice. The report indicates production (positive values) and consumption (negative values) for the product in each time slice.
Accessing the Report
Open the Planning Board.
Click on the Format tab on the Ribbon.
Click on Report icon.
Click on Supply Demand Balance Report.
Using the Supply Demand Balance Report
Period Ending indicates the time slice/time period.
Activity indicates the index of the activity.
Amount indicates the quantity produced or consumed.
Proj Inv indicates the projected inventory for the material.
Operation indicates the method of production.
Consuming Material indicates the downstream consuming material.
Consuming Operation indicates the downstream consuming operation.
Upper section of the report contains
Material name and Starting Inventory.
Users can also view the Supply Demand Balance report for the component materials through Component dropdown.
If users would like to view the report for different report , they need to select the product and click on Update report icon.
Keywords: None
References: None |
Problem Statement: How do I set the default file path when opening a case in Aspen Plus | Solution: In Aspen Plus there are 3 ways to configure the directory when opening a case from File | Open button. Go to File | Options | Files | Locations and expand the "More files starts with" option. Select which directory to use from the following options:
Current directory is the directory last used to open or save a file.
O/S default behavior is the Documents folder for the currently logged in account.
Default working directory is the one specified above.
Click on Apply and close the window.
To change the default file path in Aspen HYSYS, please review the following KB article: How do I change the default file path when clicking on Open Case in Aspen HYSYS
Keywords: Path, Plus
References: None |
Problem Statement: Error while upgrading the PSL_V8.8.CAS | Solution: Before you start the upgrade, set CNTLE(SCMPM,1) to NUMLIM instead of NUMERIC. After the upgrades are complete, you can restore the value if you prefer to. The library manager has to compare current version with the library being installed and it requires this setting in some instances without resulting in error.
Keywords: None
References: None |
Problem Statement: How can I detect streams with negative flows in my simulation? | Solution: Sometimes, due to bad inputs for flow rates, ratios or equations on spreadsheet blocks, a simulation in Aspen HYSYS may calculate negative flow rates in some instances.
Since Aspen HYSYS focuses only on the numeric solution of the mass balance, it can allow and may calculate negative values for flow rates. We know these are physically unfeasible, so the user must be aware of which streams have negative flow rates.
Looking at one stream at a time looking for this negative values may take a long time, so the fastest way to identify which streams have negative flow rates is using Conditional Formatting.
1. Make sure the subflowsheet with the stream is fully converged. Click anywhere on the Flowsheet to be able to access the Flowsheet/Modify ribbon.
2. Click the Editor button (highlighted above) on the Conditional Formatting section of the ribbon, which opens the Conditional Formatting window. Then select the drop-down menu and click <Add New> for a new conditional formatting option.
3. Browse through the Select Query Variable window and look for either Mole Flow or Mass Flow and select it; then click on OK.
4. You will now see a new conditional formatting, Mass Flow (flow rate). Change the Number of Segments to 2, this allows only one value to be written. Write down any value below zero (-0.1 for example) and choose the colors you want those streams to be highlighted with; the top color will be displayed for streams not complying with the format, the bottom color to the ones complying. So for example, you can select the top color as green and the bottom as red, so the streams with negative flow values will be seen in red.
For additional information, go to the following articles:
https://esupport.aspentech.com/S_Article?id=000031357
Keywords: Negative, Flow, Streams, HYSYS, Display
References: None |
Problem Statement: In the Unit Diagram, when should I use Rate Multiplier (Rate Responses) vs. using Link Capacities? | Solution: The attached document provides an overview of when you should be using Rate Multiplier vs using Link Capacity to achieve your desired outcome for Rate Responses. It also provides examples for the same.
Key words
Rate Multiplier, Link Capacity
Keywords: None
References: None |
Problem Statement: This knowledgebase solution documents the increase of UDP network traffic on port 5093 from the SLM client server and how to stop it from happening. | Solution: The SLM broadcasting option is used to broadcast to other Aspentech installations available on the network which can cause a large amount of UDP 5093 traffic generated if the network has multiple installations on the network.
The idea of the broadcasting option is to send the message around the subnet so that all listening Aspentech installations can be detected.
Aspentech recommends using the specific IP address of the the Server Licence Manager Server (SLM) instead of the hostname as this has been shown to increase network performance with the SLM if the user states the specific subnet within the IP address.
To stop the UDP traffic from appearing please uncheck the following option from the SLM client as shown in the image below.
Keywords: SLM
Performance
UDP
5093
References: None |
Problem Statement: Example: Creating a case study in Aspen HYSYS analyzing the amount of inhibitor required to avoid hydrate formation at different temperatures | Solution: This example shows the necessary steps to generate a case study where the user can exploit the tools in Aspen HYSYS to calculate the required flow of inhibitor that is required to avoid hydrate formation.
The first step is to identify the stream(s) of interest and generate a Hydrate formation analysis. This can be done from the Home | Stream Analysis section or from the stream form on the Attachments | Analysis form.
The Hydrate formation analysis shows on the Performance tab the Hydrate formation temperature. The case study should focus on analyzing temperatures below this, since any temperature above will result in 0 flow of inhibitor needed.
Go to the Design tab and activate the Inhibitor Flow Calculation, then select one of the supported inhibitors (present in the component list). If the stream temperature is below the hydrate formation point, HYSYS will calculate the amount of inhibitor required to avoid the presence of hydrates.
Once the analysis has been properly set up to calculate the inhibitor flow, you can begin creating the case study. For this study, two main variables are required, the stream temperature (independent variable) and the inhibitor flow (dependent variable). Feel free to add any other variable of interest for the analysis.
Note: The easiest way to add the inhibitor flow is to right click the flow value and select Send to | Case Study.
With the variables configured in the case study, the user can now enter the temperature range/values of interest. As mentioned before, it is useful to evaluate temperature values below the Hydrate formation point, since any value above this will always result in 0.0 inhibitor flow.
The attached example has been built in Aspen HYSYS V10, an XML version of this file is included for use in older versions.
Keywords: Inhibitor, Vary, Case Study, Temperature, Hydrate, Formation, Stream Analysis.
References: None |
Problem Statement: How can I link the Actual Volumetric flow of two different streams in Aspen HYSYS? | Solution: In the case that the user needs to link the volumetric flow (Act. Volume Flow) of two different streams, an Adjust operation in addition with a spreadsheet block can be used. Using this method, the values for the volume flow of both streams will be linked regardless if they have different conditions and composition.
Note that this KB article has an attached HYSYS file that can be consulted to review the result of the description bellow. The stream names and information in this example file will be referred through the article for further clarification.
1. Identify the two streams whose flow will be linked. Note that one of these streams will transfer the value of its flow to the second, so this second stream should have a user specified flow, either on mass or molar basis. In this example, stream “compressor in” will be used as the base stream, and “unattached stream” will be used to copy this flow.
2. Add a Spreadsheet operation to the simulation, use it to link the value of Act. Volume Flow from stream 1 (compressor in). To do this, you can simply copy the value from stream 1 and paste it in the spreadsheet or simply drag and drop the value from that stream to the spreadsheet.
Note: Act. Volume Flow can be found under the Properties section of the stream form.
3. Add an adjust operation to the flowsheet, select the Mass or Molar flow of the second stream as the Adjusted variable.
Be careful, if stream 2 has a specified (blue) value under molar flow, then molar flow should be selected in this step.
4. Set the target variable as Stream 2 | Calculator | Act. Volume Flow.
5. As Target value, select SpreadSheetCell Object as the source, then select the cell where you linked the volume flow of Stream 1. Leave the default Offset of 0.0.
6. Run the Adjust block and review the results.
The Spreadsheet operation together with the Adjust block fulfills the task of linking the values of the actual volumetric flow, so if the flow on the initial stream changes anytime in the simulation, the second flow will be automatically linked.
Keywords: Act. Volume Flow, Link, Spreadsheet, Adjust, Example
References: None |
Problem Statement: Upgrade of DAL_V9-0.CAS library runs for some time and fails without any warnings. | Solution: The Library manager logic is contained in the GML library, so sometimes when Aspen makes updates to the library manager logic in a GML, you can then have trouble if you upgrade the GML library and then go right into the next upgrade.
To resolve the issue, follow the below steps:
Install the GML (V9.0).
Save the case,
Close and re-open the case,
Install the rest of the V9.0 libraries.
Keywords: None
References: None |
Problem Statement: What can be done if the SLM License file has been encrypted? | Solution: Method 1 – If done by Symantec Endpoint Encryption (SEE)
If you have received a file or folder that was encrypted using SEE it can be decrypted and opened or read by completing the following steps.
You must know the password that was set when it was encrypted. Please note this cannot be done on Macintosh computers; any Windows computer can be used whether or not SEE is installed.
1. Save the SEE file to the desired location on your computer, then double-click it to start decrypting.
2. The Symantec Endpoint Encryption Self-Extractor Password window will appear. Type in the decryption password that was given to you and click OK.
NOTE: If you see a window prompting for the Extract to location please click here for instructions.
NOTE: SEE allows you four attempts to type in the correct password. If it is not entered correctly, you will have to wait for one minute before being able to try again.
3. When the correct password is entered, the Symantec Endpoint Encryption Removable Storage Package Modifier window will appear and display the original file or folder name. Select the Extract To button near the bottom of the window.
4. The Removable Storage Extractor window will appear. You can decrypt the file in the default Extract to location, or select a different location under the Folders/Drives area. Click the Extract button at the bottom of the window when you are ready.
5. When decryption is done a success, message will be displayed. Click OK.
6. The decrypted file will appear in the location specified in step 4 above, with the original name it had before it was encrypted. Double-click on the file to open.
Method 2 – If File Encrypted by operating system
For example – Windows 10
Here you will see license file with a yellow icon
Steps to un-encrypt the file:
1 – Select file – right click file and go to properties
2 – Click on the Advanced tab button
3 – Remove tick against encrypt contents to secure data – then click ok – then apply changes
4 – Click ok to close window
5 – Now the license file is in original format
6 – Now you can install the license file without any problems
KeyWords
Decrypt
Keywords: None
References: None |
Problem Statement: This knowledgebase solution documents why you may see 32766 licenses. | Solution: 32766 total licenses is an indication of having a perpetual based license. Often these are standalone licenses which do not run using an SLM server, but that is not always the case.
To identify whether your license is a token or non-token based (perpetual) license, please do the following-
Open the SLM License Profiler, select the license file you wish to examine, load information and then click on view licenses.
If SLM_Pool = 0 , 1 or 32766 Perpetual (Non-token) license.
If 1 < SLM_Pool << 32766 Token based license.
Token – Under Token agreements, users have access to all the products as specified within the contract. Each product has a specified token value and each license is limited by the Token limit on the SLM server. The token values can be found in the Aspen License Profiler' - In the licenses window, select the products you are interested by scrolling the vertical bar. Then scroll the horizontal bar to the right till you see the column 'Token Value' or 'Commuted Token Value’. The number indicates the total tokens required to run that program if you connect to the license or commute the license respectively. Typically, if the limit is exceeded then the application will not start. Tokens are returned to the token pool when the user closes the application.
Non-Token – A standard Network License where an individual can access the software licensing as long as the number of purchased license units is not exceeded. SLM counts the software in use and limits the number of units that can be accessed simultaneously to the number of units purchased. A standard network license is sold in “seats” or simultaneous users. This often shows as a perpetual license with the pool showing 32766 available licenses.
KeyWords
Tokens
Perpetual
SLM
Keywords: None
References: None |
Problem Statement: When you need to install new software on an old version of Windows operating system, it requires having installed the latest .NET Framework. But in Windows Server 2016, you may want to install the old software which requires older libraries to run. | Solution: Simply installing features on Windows Server is easy to perform through server manager or command line and PowerShell. But in this case the .NET Framework needs a source directory to completely install on Windows Server.
Install .NET Framework 3.5 on Windows Server 2016
Using the latest Windows Server 2016, you install .NET Framework 3.5 easily through server manager with a graphical interface.
1. Open Server Manager and navigate to Manage and add rule and features.
2. Just click next to Features section and select the .NET Framework 3.5 then click Next. On the Confirmation page click the Specify an alternative source path. Then type the path of Windows Server 2016 image exactly like below screenshot.
It will let you Install .NET Framework 3.5 without having internet connection on your Windows Server. You can install this with command line also.
Using DISM command line is easy, but sometimes make trouble to install some feature with. Instead, you can do it with this method.
3. Finally, when the .NET Framework 3.5 has been installed successfully on Windows Server 2016, click Close to finalize the installation.
Keywords: None
References: None |
Problem Statement: How does the Mixed Mode Method work and how do I set it up correctly? | Solution: The Mixed Mode is a Solution Strategy which allows a hybrid solution between the Sequential Modular (SM) and Equation Oriented (EO) techniques to converge a simulation. It is used when you deliberately want to run a model in SM while on EO.
This Method works by using a Perturbation Layer around the block you would like to run in SM mode. The Perturbation Layer is the mechanism to run a closed model in the EO strategy, this layer forms a wrapper around the closed model and generates the EO variables for the model.
In Aspen Plus, the SM strategy uses closed models, meaning each block computes its outlet streams. EO collects all the model equations and solves them simultaneously using specialized solvers, all of which use the open model to solve.
To be able to use the Mixed Mode you require to specify at least one block to solve in SM mode (closed form). To do this, go to the selected Block ID | Block Options | EO Options | Additional Options | Solution Method and select the 4th Option (Closed; use Perturbation layer around closed model).
Keywords: EO, Mixed, Mode, Perturbation, Layer
References: None |
Problem Statement: In the event of having reduced capacity upon failure of an item, the flow should go through the event at normal operation however, the validation shows otherwise. Is there an explanation for this? | Solution: This is a side effect of the algorithm used. If all paths are up (or available) then it selects the path(s) that will provide the greatest capacity. In the above case, it is choosing the path of least resistance. That is, the path with no events. Mathematically, if the “Bypass” event is not in cold standby, then all results will be correct. The “Bypass” event will still age and therefore, fail during the simulation (assuming the distribution is not set to Never). When this occurs, the link with no event (or bypass link) will allow the unit to operate at the desired bypass rate. We are currently working on fixing this by eliminating the need for bypass links. Instead, you will need only set the “0 paths up” value within the RM op form to the desired value. As a note, if the bypass link is set to something less than 1, then both paths will be used (highlighted in green). In this case, it is only allowing 100% capacity, so mathematically it is correct, but looks strange. Note in the example below the bypass link is set to 0.5. Thus, both paths are used. The full 50% of the bypass and 50% of the path with “Event6” on it.
Key words
validation, bypass
Keywords: None
References: None |
Problem Statement: This knowledge base article describes the steps to configure version 2 Activity Editor. | Solution: Open CNTLS
Specify the Activity Editor Version to 2
Specify the Activity Editor Control table to be AECTL1
AECTL1 Activity Editor control table and is dimensioned by TYI.
AEPSMFG table provides control over MODIFIABLE, INVISIBLE, READONLY tabs of the Activity Editor.
AEOMFG table that provides control the contents of the tabs.
AEPSID: Contains the code of the tab
LABEL: Text to be displayed
BEFDISP: Rule / Macro to be executed for calculating the value of the field
SOURCE: Value of the field
AEBMFG table provides control over the contents of the bill of material tab.
AEPSID: Contains the code of the tab
LABEL: Text to be displayed
BEFDISP: Rule / Macro to be executed for calculating the value of the field
SOURCE: Value of the field
Keywords: None
References: None |
Problem Statement: Starting from V10, we need to specify the Capacity Multipliers in the Rate Multiplier form. Is it possible to specify the Rate Responses similar to the legacy Titan version? | Solution: Starting in V10 CP4, the response configuration section of the rate multiplier unit op form has been improved to allow you to select the number of paths required for 100% operation (as shown in attached screenshot). The drop-down selection allows you to specify N/A or any value from 1 to N, where N is equal to the total number of output paths from the rate multiplier. The Rate Response grid | Capacity Multiplier values update based on the selection made in the Response Configuration drop-down menu for all paths except for 0 paths up.
Key words
Rate Responses, Rate Multiplier
Keywords: None
References: None |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.