question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
|---|---|
Problem Statement: What are the database roles required for SQL Server Management Tool? | Solution: The following roles are needed to perform certain actions in PIMS SQL Server Management Tool:
The sysadmin Server Role is required to create or delete a database. (Security | Logins | *USER* | Server Roles).
Under User Mapping, the db_datareader, db_datawriter and db_ddladmin database role memberships are required to truncate a database. (Security | Logins | *USER* | User Mapping)
Under User Mapping, the db_datareader and db_datawriter database role memberships are required to delete selected cases. (Security | Logins | *USER* | User Mapping)
If you are not familiar with SQL Server management, please consult with your database administrator prior to making any changes.
If the settings above are missing, you will not be able to use all the tool functions and information may not be visible.
For more details on how to create a database please refer to the following KB: https://esupport.aspentech.com/S_Article?id=000050106
Keywords: SQL Server Management Studio, results
References: None |
Problem Statement: What can cause some local model structure to be missing when running a global model in Aspen PIMS V11? | Solution: In PIMS V11 and V10 CP3, fixes were made to ensure the global overrides for tables BLNSPEC, CAPS, PROCLIM are all correct as documented in the HELP. This could cause the objective function to be different compared to previous versions of PIMS.
For BLNSPEC, you should see W353 if the global BLNSPEC is ignored because it's missing from the local model.
For CAPS and PROCLIM, you should see W026 if the changed MIN, MAX, or FIX is not defined in the local model.
For all three tables, you should see W720, W721, W722 if the global model tag is invalid or the tag is missing from the referenced local model.
To solve this you must go to the local model and add the missing structure specified in the warning message.
For example, for warning message “W353 Global BLNSPEC Entry at NE40A and DSL Ignored” you must specify a value for NE40 for DSL in table BLNSPEC of local model A.
Keywords: None
References: None |
Problem Statement: When converting Titan version 2 file to an Aspen Fidelis Reliability, the converter does not allow this action to happen. It shows an error message saying "Operation is not allowed when the object is closed." | Solution: Titan2 version needs to be 2.24.74. In a later version is added a new property to pipes that Titan2 does not have.
To avoid this issue:
Uninstall your current version of Titan2
Install the Titan version 2.24.74
Open any old *.fid files and simply save (not need to do a Save As, just click Save or the Save button)
Then the database should be updated with the new pipe property
The model should be able to be converted.
Keywords: Titan File, Fidelis Converter, Titan File Converter, Object is closed
References: None |
Problem Statement: How to calculate the volume flow at standard conditions from the free expansion volume flow calculated in the tail pipe boundary of BLOWDOWN. | Solution: To calculate the volume flow at standard conditions from the Free Expansion Volumetric Flow calculated in the tail pipe boundary of BLOWDOWN it is necessary to follow the steps described below, as this calculation is not performed directly in the BLOWDOWN Analysis.
In the parent flowsheet place an independent stream, here is were we are going to input all the desired data to allow the software to perform its calculations.
Once BLOWDOWN calculations are successfully completed copy and paste the following results into the Conditions and Composition worksheet of the stream we previously added:
Free Expansion Pressure and the Free Expansion Temperature from the Tail Pipe Boundary over the Free Expansion results at the time of interest.
Mass Flow Rate and Orifice Composition at the selected time of interest from the Result Summary | Orifice Results. For more information about orifice results please refer to solution 000049066.
Once you have fully defined the stream from the step 1, go to the Properties worksheet and look for the Std. Flow, which is calculated at the default standard conditions of 15 C and 101.3 kPa.
Consider that the property package and calculations used to simulate the depressurization system in the BLOWDOWN Analysis tool offer superior predictions for fluid properties around the critical point, it is proprietary and distinct from the main PFD simulation and it is not available in the Properties environment. So, to get an accurate approximation you could use the Peng-Robinson or the Soave-Redlich-Kwong property packages to evaluate the independent stream.
Keywords: BLOWDOWN, Standard, Volume flow
References: None |
Problem Statement: Can I use the Rated capacity of a header to calculate Acoustic Induced Vibration in Aspen Flare System Analyzer? | Solution: Since AIV calculations were introduced into AFSA in V9.0, these calculations have used the actual Flow through an object.
In V11.0, a new option has been introduced that allows the user to switch between this current Required Flow and the Rated capacity in the elements to be analyzed.
The user can control this option by clicking on Home | Calculation Settings | AIV, allowing the user to fully control
Keywords: Rated, Required, flow, SPL, AIV, New Features
References: None |
Problem Statement: How to set a color scheme in a score plot | Solution: Aspen ProMV allows the user to create a full level spectrum based on the score. To do that, please follow these steps:
1. In the Score Plot do right click and select Properties
2. In the Coloring Ribbon of the Plot Properties Window, select the desire method and style to sort the values. Then click in Apply.
Standard
Variable
Score
Density
3. Now the user can identify in an easier way the scores.
Keywords: Color, Score, Sort, Level
References: None |
Problem Statement: In the Safety Analysis, the PSV allows the user to add PRDs (arranged in parallel) to the relief system. | Solution: To add PRDs to the current valve, please follow these steps:
1.- Go to the PRD Data tab for relief device and click on the Add PRD button to add a second PSV.
2.- In the Rating tab, set the desire Allowable Overpressure (%) for the primary PSV and the set Pressure Increase for the secondary PSV
3.- Ensure that the capacities for the arrangement doesn't present any error (undersized valve) or warning (oversized as is lower than the minimum capacity). If yes, try different orifice sizes that satisfy the design constraints for both scenarios.
Keywords: Relief Capacity, PRD, Percentage, Orifice
References: None |
Problem Statement: Differences in shell side velocity between EDR versions | Solution: The shell side model considers that there are different components for the shell side flow:
Crossflow (B stream): Only the crossflow (and part of the window flow) contribute to the heat transfer. The crossflow fraction usually ranges from 30-70 % of the total flow. Lower values will give lower pressure drops, but generally indicate a poor design.
Shell ID to Bundle OTL diametric clearance (C stream): This is called a bypass stream, because it largely bypasses the heat transfer surface. This is also known as the "C" stream. When this shell-bundle OTL clearance is large, as in the case of an inside floating head exchanger (TEMA rear head types S & T), the program automatically adds sealing strips to force the flow back into the bundle.
Pass Lanes (F stream): This is bypass flow in in-line pass partition lanes, also known as the "F" stream.
Window (B+C+F flow): This is the sum of:
- Crossflow (B stream)
- Bypass Flow around the outside of the bundle (C stream)
- Bypass Flow in in-line pass partition lanes (F stream)
Baffle hole to Tube OD diametric clearance (A stream): This is the location of the primary leakage stream and is sometimes referred to as the "A" stream. Leakage through this opening can significantly decrease the pressure drop and will also reduce the film coefficient.
Baffle OD to Shell ID diametric clearance (E stream): This is a secondary leakage stream and is sometimes called the "E" stream.
To calculate the velocity of these regions, EDR needs to know the flow area and the flowrate through each region.
Previous to V10, EDR would use the entire flowrate for the crossflow and window-flow velocity calculations. For V10 (and after), EDR estimates the appropriate flow fraction for each one of these regions, so only this fraction of the total flowrate will be considered for the velocity calculations.
These flow fractions can be consulted under Results | Thermal/Hydraulic Summary | Flow Analysis:
The Cumulative Patch 1 (CP1) for EDR V10 includes a new option (under Input | Program Options | Methods/Correlations | General) to select which convention should be used for the shell side velocity calculations (full flow or calculate flow fractions), where the default option is to use flow fractions:
This option will be included as a default feature starting with EDR V11.1
For more information regarding the meaning of the shell side flow fractions, please refer to the following article:
What do the Shellside Flow Fractions mean?
Keywords: Shell side velocity, velocities, flow fraction
References: None |
Problem Statement: How to use the "Custom Curves" & "Custom Attenuation" for the AIV Calculations | Solution: Aspen Flare System Analyzer allows the users to enter its own "D/t" and "dB" values to perform the AIV Calculations for the pipes in the network.
Note: These values are coming from operating companies standards (or already implemented curves like CSTI) and are given for calculating acceptable dB (based on the D/t vs dB) for a particular pipe D/t.
For example, if a user has D/t vs dB as follows
D/t dB
30.4 137
26.5 124
On the Calculation Settings|AIV tab select the custom curve option and click in Add Row to enter the data.
When the AIV calculations are performed for the pipes in the network, this custom curve data is used to flag if the AIV concern occurs as the SPL is not acceptable. The SPL is still calculated using the API 521 6e SPL equation as below:
For further information of when is applicable please refer to the article What are specific examples that are a good basis for employing custom attenuation for a device or fitting?
Keywords: AIV, Custom, Data, dB, D/t
References: None |
Problem Statement: Procedure to import Aspen HYSYS models to Aspen Economic Analyzer (APEA). | Solution: This solution discusses the step by step procedure to import simulation data obtained from an Aspen HYSYS model into Aspen Process Economic Analyzer.
1. Load the Aspen HYSYS file and make sure all unit operations have converged results and none of them have errors. It's important to make sure all results are ready before the data is transferred to APEA.
2. Save the Aspen HYSYS file using the HSC format.
3. Close the Aspen HYSYS file and launch Aspen Process Economic Analyzer. Make sure you use the same version of APEA used to save the Aspen HYSYS file.
4. Create a new APEA Project and Scenario by clicking File | New.
5. Enter a name for your new Project and Scenario and click OK.
6. Select between IP (English) or Metric Units of Measure, then Click OK.
Note: The units cannot be toggled after the project file has been created, so make sure the selected units match your required data.
7. Accept Input Units of Measure Specifications by closing dialog box
8. On the General Project Data window, make sure you enter the desired Country Base (US, UK, EU, JP, ME) and if required, enter the Currency Symbol and conversion rate. Hit OK when done.
Note: This selection cannot be changed after closing this Window, if a different country basis is required it's required to close the current Project and create a new file.
9. Left click on Project basis View Tab (on the left bottom).
10. Double click on Simulator type, then select Aspen HYSYS and hit OK. A confirmation window will appear upon hitting OK.
11. Double left click on Simulator file name, then browse for your Aspen HYSYS file. Hit OK when done.
Note: use the File type window on the lower corner of the browser to find HSC files.
13. Click on Run | Load Data. You can also use the icon from the tool bar. Click Yes in the confirmation message to proceed.
14. At this point, you can switch to the Process View tab to view the objects found on the simulation file:
15. Click on Run | Map Items. You can also use the icon from the tool bar.
16. In the upcoming window, accept the default options and click OK.
17. The Map Preview window will appear, use this to map each Aspen HYSYS operation present in your simulation to real life equipment. The Aspen HYSYS operations will be listed on the left section of this window.
Since APEA maps every operation by default, you can click on any Aspen HYSYS unit to review the current mapped equipment. Feel free to correct any operation mapping if needed. Mapping can be modified later in your evaluation.
18. Click OK when done. Allow APEA to complete the mapping process, wait for the status at the bottom to read Ready in order to continue.
19. Switch to the Project View tab. This section displays the actual equipment that will be estimated by APEA. The objects imported from the simulator will be displayed under the section "Miscellaneous Flowsheet Area".
Note: Objects located in a HYSYS Subflowsheet may appear in another section, with the same name of the flowsheet.
20. Feel free to browse each APEA component to review the information that was taken from Aspen Plus.
This marks the end of this process, you will have imported your Aspen HYSYS Model/results into APEA at this point.
Keywords: Aspen Process Economic Analyzer, APEA, Aspen HYSYS, Simulator, Import.
References: None |
Problem Statement: By default Aspen Flare System Analyzer only shows the iteration error for the whole network in the trace window, not the error per unit in the iteration. | Solution: If the user wants to track a detail information of the iteration process inside Aspen Flare System Analyzer, please follow these steps:
1. In the Home Tab, click Calculation Settings
2. In the Solver Tab, check the "Echo error history" and click OK
3. In the View Tab click the Trace option and run the model. Now, each iteration will show a detail information at what specific point of the network is solving ad the current internal iteration error
Keywords: Iteration, Error, Track, History.
References: None |
Problem Statement: Is it possible to know Aspen HYSYS file original version? | Solution: It is very common for users to need to know what version was an Aspen HYSYS file originally developed. This is especially important when the file was saved on a newer version and user is working on an older version, which means the user will not be able to open such file. On those cases, Aspen HYSYS displays the following message:
To open a file from an older version on a newer version, you may use XML technology, e.g. it applies if you would like to read a case created in Aspen HYSYS V10 but you are running Aspen HYSYS V8 or V9 (for more info on this, refer to the article How do I read Aspen HYSYS cases created in a newer version when I am running an older version?).
On the flipside, it is possible to open older version files in newer versions. Aspen HYSYS display the message below, however it does not tell the user the file's original version:
To know that, first proceed and save the file as an *.XML file, then open that *.XML file with the NotePad. The NotePad should state the original version the file was developed in:
For example, on this case, HscFileRevision states 7263 as the revised version, which is version 7.0.236. This means the version the file was developed in was V7 without cumulative patches.
Note BuildNumber also shows up; this is the version of where the .xml file comes from. In this case, it is 10.0.249 or V10 without cumulative patches.
For additional information and other examples, refer to the following articles:
What is XML?
Why is XML important? What new features does XML functionality bring to HYSYS?
Keywords: Version, xml, HscFileRevision, BuildNumber.
References: None |
Problem Statement:
In VSTA coding for an AFR module if random.next instruction is declared the sequence of randomness is not "random"; also it does not fix the specific iteration.
Example: When the first iteration is run it will give some values that are not accurate to the ones in the module and when is run it again those values change.
This might be due to the usage of Rand(), function that is a library in .NET. | Solution:
To get repeatable random numbers, is needed to use the same seed value.
Please have a look at the examples on MSDN Random Constructor.
KeyWords:
Random, random.next, VSTA coding, Seed value, Random objects.
Keywords: None
References: None |
Problem Statement: When calculating Entropy Departure using Aspen HYSYS fluid package, I get a different value than that obtained when using the same fluid package in Aspen Properties. | Solution: The formula to calculate entropy departure (S-SIG) in Aspen Properties is different than that in Aspen HYSYS.
In Aspen HYSYS, the entropy departure function is calculated using equation (1):
(1)
Where:
S = Molar Entropy
SIG = Molar Ideal Gas Entropy
R = Gas Constant (8.314 J / (K x mol))
Z = Compressibility Factor
P = Pressure
P0 =
Keywords: Entropy Departure, Peng-Robinson, Aspen Properties.
References: Pressure (101.325 kPa)
V = Molar Volume
In Aspen Properties, the entropy departure function is calculated using equation (2):
(2)
Entropy departure in Aspen HYSYS needs to add R*ln(P0) to be equal to the entropy departure calculated in Aspen Properties.
To validate it, the user can follow the calculations as described below.
1) In Aspen HYSYS, use Aspen Properties package, select Aspen HYSYS Peng Robinson method. Use this method to calculate entropy departure in Aspen Properties.
2) Create another fluid package, select native Peng Robinson method, this time calculate the entropy departure in Aspen HYSYS.
3) Check the relationship: S_departure_HYSYS + R*ln(P0) = S_departure_Aprop.
These steps are reproduced in the file attached, as an example. |
Problem Statement: As mentioned in the article What is the "Choose Label Variable" in Aspen HYSYS V8?, the user can display at the same time 2 different variable labels for the Material Streams on the PFD, but in some of these labels contain an asterisk (*) next to the value, and others don't. | Solution: The variables that are user inputs will have an asterisk (*) on its variable label, while the variables calculated by Aspen HYSYS won't.
Keywords: PFD Label, Asterisk, Display, Material Stream, Input, Calculated.
References: None |
Problem Statement: How to fix the message ERROR> 'LIB- #' CODE OF ACCOUNT IS NOT DEFINED? | Solution: This error message appears on the Economic Evaluation software when the COA for a Unit Cost Library item (LIB model) has not been correctly defined.
To solve it, the user should check the following:
On the Codes of Accounts Definitions, check if the defined COA indeed exist on the list.
If the COA is user defined, check the "Icarus/User COA option” is set to “U: User defined code of account will be assumed”
Keywords: Unit Cost Library, ERROR, LIB, Code of Account, COA Option.
References: None |
Problem Statement: What is the root cause of the following error message?
ERROR> 'CCP- #' PIPELINE SEGMENT IS ALLOWED ONLY IN PIPELINE AREAS? | Solution: This message appears in an ACCE project when a component of the “Above grade or buried pipeline segment” class (PCCP) is added into a regular ACCE area (Grade, Pad, Open, Module, etc.).
These types of components are special and can only be correctly evaluated when these are added into a Pipeline Area. For information on how to add a Pipeline area to an ACCE project please review KB: How can I add a Pipeline Area in Aspen Capital Cost Estimator?
The EE programs usually do not allow the user to link this Pipeline Segment component to a normal Project Area, when the user attempts to add one of these components to an Area, the following warning appears:
There are however some ways to force adding this component to a normal Area, such as copying and pasting the component itself.
In order to get rid of this issue, the user should make sure that all the components of this type are linked exclusively to Pipeline Areas and remove any of these components from regular Project Areas.
Keywords: CCP, Pipeline, Cross Country, Troubleshooting, Not Allowed, Error, Not Created.
References: None |
Problem Statement: After migrating datasheet from previous versions to V10 or V11, the "Select Class" list no longer shows the defined classes when generating a new datasheet (creating a blank datasheet not associated with any equipment objects). | Solution: Starting in V10, a functionality was added to hide sub objects or objects which were determined as not likely to be created as a standalone object. When the HideForDisplay flag is set in the Datamodel, users will not have the ability to create the objects via the "Select Class" list. Users can either change the flag to "False" or delete the flag in order to be able to select the class. Attached file is a list of objects and sub objects whose HideForDisplay flag was modified in V10. Users can refer to this list to change the flag if they're migrating datasheets associated with these objects.
Keywords: None
References: None |
Problem Statement: Why do I get the “Result Warning 1299: Thermal leakage across the longitudinal baffle is estimated to be significant (…)”? | Solution: After completion of the main calculation, thermal leakage across the longitudinal baffle is estimated based on some simplified assumptions (the procedure is explained in the HTFS report SM25: Estimation of Thermal Leakage Effects in TEMA F-shells). This does not affect the results and is only used to issue the Warning 1299 when thermal leakage is significant (leakage penalty factor is greater than 5%).
As mentioned on the Warning 1299, to match the calculated results the user has two options:
Increase the surface area
Add an insulated longitudinal baffle, although this configuration is not currently supported on Aspen Shell&Tube Exchanger
Keywords: Warning 1299, Thermal Leakage, Longitudinal Baffle.
References: None |
Problem Statement: What is the difference between the Classic and the Online Dynamic alignment methods? | Solution: Aspen ProMV have two different methods to align batch data:
The Classic method allows to use the following approaches:
Linear interpolation of the time scale: The user must choose the variable to warp against (Clock_Time is the default).
Offline Dynamic warping: Calculates an optimal match between two given sequences
The Online Dynamic method is an optimization approach that incorporates multiple signals. It also recommended subset of batches to review to in order to choose the reference batch and determine the weight of each variable
Keywords: Batch, Data, Alignment, Methods, Classic, Online Dynamic
References: None |
Problem Statement: How to attach a petroleum assay to a material using VBA? | Solution: To attach a petroleum assay is necessary to use backdoor mechanism by the command Call simcaseBackDoor.SendAttachObject2("FlowSht.1/StreamObject.400(1)/Viewable.397:PetroleumAssay.500", assayMoniker). For further information of how to use a backdoor method please refer to the following article How to use the BackDoorVariable method in Aspen HYSYS
The example includes an Aspen HYSYS model file and a MS Excel file. The Excel file is calling the Aspen HYSYS file, and attach the desire assay to the stream 1.
Notes:
There is no way to access the Aspen Assay Manager (AAM) functionality externally or by coding, neither through Aspen HYSYS automation nor another external automation interface.
The assay that is attach to the stream must match to one of the current characterized assays of the Petroleum Assay tool
To modify an assay created with Oil Manager, please refer to the following article Can I change the flow rate of the assays in a blend via OLE?
Keywords: Petroleum Assay, Attach, VBA, Coding, Automation, Backdoor
References: None |
Problem Statement: Is possible to edit the wetted area exponent for fire calculations? | Solution: Starting in V11, Supercritical, Wetted (API), and Semi-Dynamic Flash Fire scenarios now allow you to edit the wetted area exponent for fire calculations involving partial confinement.
This new feature was added to model fire under an air-cooled exchanger and partially enclosed fire, as the API 521 allows use of exponent of 1.0 for these two different cases.
It’s also useful in other situations (e.g. fully enclosed fire), where the user has corporate standards or other input suggesting a different exponent.
Note: when opening cases created in a previous version, the default exponent, 0.82, is applied.
Additional information on Fire Emergency Scenarios can be consulted on the articles below:
Jump Start Guide: Fire Overpressure Analysis in Aspen HYSYS and Aspen Plus
White Paper: Validation of Fire Scenario Relief Load Calculations with the Semi-Dynamic Flash and Supercritical Methods in Aspen HYSYS
How is the Latent heat estimated with the Wetted method for Fire Scenarios?
Keywords: PSV, Wetted Area Exponent, API 521, Fire Scenarios.
References: None |
Problem Statement: Why does the Tube Wall Thickness reported on the TEMA sheet not match with the Tube Wall Thickness input? | Solution: On Plain tubes, the tube wall thickness input is effectively the value reported on the TEMA sheet (Tks, Average).
However, for Lowfin tubes, the Tube Wall Thickness input refers to the unfinned regions, and the TEMA output reports the Tube wall thickness under fin (thickness on finned region), which can be specified under Exchanger Geometry | Tubes | Lowfins.
For additional information, refer to the articles below:
How are each of the Lowfin tube parameters defined?
Jump Start Guide - Modeling Lowfin Tube Heat Exchangers with Aspen Shell & Tube Exchanger
Keywords: Tube Wall Thickness, TEMA, Lowfin, Tks Average.
References: None |
Problem Statement: How do I prevent the tray warning/error "Total liquid rate is above the maximum weir loading" on Aspen HYSYS? | Solution: On distillation tray columns, at high weir loadings, possible adverse hydraulic results as follows:
Large crests and high froth heights and “jet flooding”
Crests that are so large that those crests do not fit into downcomer mouths, and “choke flooding” occurs
High froth heights sometimes yield excessive pressure drops, and “downcomer backup flooding” occurs
For the maximum weir load limit, Aspen HYSYS uses a default based on the tray spacing (Resetarits & Orgundeji, 2009); if the operating point approaches 10% within these limits, a warning will show in the hydraulic plots. If the value gets exceeded, an error message will be shown instead.
Tray Spacing
(in.) Maximum Weir Loading
(gal/min per inch)
12 3
15 5
18 8
21 10
24 13
One cure for high weir loadings is increased column diameter.
More often, multi-pass trays are recommended. However, there are some disadvantages to multi-pass trays as follows:
Reduced tray efficiencies
Increased tray costs (more complicated drawings and more tray parts)
Increased horizontal ring and vertical bolting bar costs
Longer tray installation times
Alternatively, we can use swept-back weirs to increase the effective length of the side weirs and decrease the weir loading.
On Aspen HYSYS, this type of weir can be specified under Column | Column Internals | Tray Geometry | Geometry | Weir Modifications
Three different shapes for swept-back weirs are available, corresponding with designs offered in vendor programs SulCol, KG-Tower, and FRI. Choose one of these shapes, and then specify the geometry parameters in the diagram (Column | Column Internals | Tray Geometry | Geometry | Picketed/swept-Back Weirs sheet)
SulCol: Specify lengths A, B, and S, which define the size and shape of the swept-back portion of the weir.
In Interactive sizing mode, if the loading of the side weir exceeds the Maximum weir loading specified on the Design Parameters sheet, S is calculated to ensure that the effective weir loading of the swept back weir equals the maximum weir loading. This effective weir loading is calculated as:
The default for A is 2/3 of the width of the side downcomer, and the default for B is 2/3 of A.
KG-Tower: Specify the depth from the main part of the weir at the point where it is most swept back. The other geometry parameters are defined relative to this.
The default for this depth is calculated in the same way as the default for S in the Sulcol weir.
FRI: Specify the lengths of the three different segments of the weir.
The defaults are calculated in the same way as the default for S in the Sulcol weir.
The following results are displayed on the same sheet:
The tray with maximum weir loading
The maximum weir loading for this tray
The maximum allowable weir loading (from the Design Parameters sheet)
Actual side weir length of swept-back weir
Effective (or projected) side weir length of the swept-back weir
The percentage of tray active area lost due to the swept-back weirs
Keywords: Maximum Weir Load, Weir Loading, Multi-Pass trays, Swept-Back Weirs.
References: None |
Problem Statement: What information should I enter in the Equipment/Item Class and Equipment/ItemType fields when adding a User model in the Economic Evaluation (EE) products? | Solution: The Equipment/Item class and type are used to allow the EE applications to calculate the Engineering cost of items not included in the system library, such as Quoted Equipment and Equipment Model Library (EML) objects.
If the entered class and type symbols match with one applicable combinations of system symbols, then the EE products will the corresponding model to calculate the Engineering cost as it would for a library component.
If the specified combination of class and type does not match with existing system symbols, then EE will assign a default percentage (15%-20%) corresponding to the Engineering cost of these components.
You can find the list of Classifications and Types on Chapter 1 of the Icarus
Keywords: Equipment Library Model, EML, Engineering, Class, Categories, Quoted, Item, User Cost Libraries.
References: Guide – Introduction to Process Equipment (Help | Documentation | Icarus Reference).
A list of Classes can be found on Sub Chapter “Process Equipment Categories” and a list of Types is available on the Sub Chapter “List of Process Equipment” |
Problem Statement: As mentioned in the article How can I use MS Excel to retrieve the heating and cooling curve of a heat exchanger in user specified units? the user can retrieved information from the heating and cooling curves using VBA macros but due to the structure underlying the scripts of the above article, it will be necessary to use the curve itself to identify its own offset before getting the Phase Mass Fraction. | Solution: Below is some sample VBA to show how to get this value as a workaround:
Private Function GetCurveOffset(ByRef hcurve As HeatExchangerCurve) As Integer
Dim bdCurve As BackDoor
Dim curvenames As TextFlexVariable
Dim names() As String
Dim i As Integer
GetCurveOffset = HEmpty 'initialize to invalid value
Set bdCurve = hcurve
Set curvenames = bdCurve.BackDoorVariable("ExchPerf.300/ExchPlot.300.0/ExchPlotCurve.301.[]:Name.0").Variable
names = curvenames.Values
For i = LBound(names) To UBound(names)
If names(i) = hcurve.Name Then
GetCurveOffset = i
Exit For
End If
Next i
End Function
Private Function GetPhaseMassFracVariable(ByRef hcurve As HeatExchangerCurve, ByVal pointOffset As Integer) As RealVariable
Dim bdCurve As BackDoor
Dim curveOffset As Integer
Set bdCurve = hcurve
curveOffset = GetCurveOffset(hcurve)
If curveOffset <> HEmpty Then
Dim moniker As String
moniker = "ExchPerf.300/ExchPlot.300.0/ExchPlotCurve.301." & Trim(Str(curveOffset)) & ":PhaseMassFrac.300." & Trim(Str(pointOffset))
Set GetPhaseMassFracVariable = bdCurve.BackDoorVariable(moniker).Variable
End If
End Function
Notes:
Within the "With hyCurvePoint" block in "GetHtExCurves", the following line msut be added: OutputValue GetPhaseMassFracVariable(hyCurve, Counter), xlOutStart.Offset(Counter, 5), ""
That command will call the "GetPhaseMassFracVariable" function above and provide the RealVariable to their OutputValue function.
Keywords: Heating, Cooling, Curve, Phase Mass Fraction, Heat Exchanger, VBA
References: None |
Problem Statement: How to calculate the maximum flow allowed for a valve for which the valve flow coefficient (Cv) is already known? | Solution: To be able to calculate the maximum flow that is going to be allowed through a valve for which we already know the Cv it is necessary to look for the flow at which the valve may be choked, to do this we must iterate the inlet flow value until the error message "The valve rating method fails to find a solution. Valve may be choked: increase valve size" is displayed. The maximum flow found at which the valve does converge will be the maximum flow allowed for that valve.
The main steps to achieve this are described below:
1. Fully define the inlet stream
2. Fully specify the reduced port valve making sure to:
a. Active the Use sizing methods to calculate Delta P in Design|Parameters
b. Set the Valve opening [%] as 100 in Rating|Sizing and define the valve flow coefficient
c. Activate the Model Liquid Choking option in Rating | Flow Limits to model the liquid choking as this is optional by default.
3. Finally, vary the inlet flow rate until you find the boundary at which the system can not converge, the boundary flow at which the system is able to converge will be the maximum flow allowed for the valve.
In the attachments you will find an example made for pure water with ASME Steam as property package selected where the dummy values of 77 F and 100 psig have been chosen for the inlet stream and 5 Cv of the valve. With this input the system is able to converge when dealing with 1330 lbmol/hr but not at 1335 lbmol/hr. Additionally, this could easily be solved by increasing the Cv value to 6.
Keywords: Choking, Valve size, Maximum flow, Valve, Valve flow coefficient
References: None |
Problem Statement: What does the following error message mean and how do I fix it?
FATAL> 'GP - n' DATA SEQUENCE ERROR OR INCOMPLETE DATA SET | Solution: This message appears in an ACCE project which has enabled the Pipeline Areas and it refers to incomplete information present in the current project.
The root cause of this message is that no components have been yet added to the Pipeline Area. Different from regular process areas available in an ACCE project, the Pipeline areas cannot be left empty, if one of these areas has no components, the project evaluation cannot effectively be completed.
By adding a Pipeline segment component, you can solve this message, make sure all Pipeline Areas in the project have at least one component.
Keywords: GP - n, Pipeline, Cross Country, Fatal, Empty, Incomplete, Error
References: None |
Problem Statement: A desalter unit in an oil refinery is a process used to remove salt from crude oil. The salt is dissolved in the water, not in the crude oil itself. Is it possible to model such a unit in Aspen HYSYS? | Solution: Up to V11, there is not a specific unit operation to model a crude desalter unit in Aspen HYSYS. However, the vessel itself can be modeled using a three-phase separator. To model the salt content, you would have to use an Electrolyte Thermo package such as OLI or Electrolyte NRTL from Aspen properties.
Please mind that you will need to include the salts and the actual components, as the usage of hypo components with these fluid packages is not supported, i.e., you will not be able to characterize an oil using the HYSYS Oil Characterization or Petroleum Assay). However, All components from HYSYS Databanks are available such as methane, ethane, propane, etc.
Keywords: Desalter; Desalinization; System; Salt; Removal; Oil; Crude
References: None |
Problem Statement: When a data source is deleted from ADSA before it is purged from aspenONE Search, it will continue to appear in the Add Tags.. search results. This is because purging the data source after it has been deleted from ADSA will not remove it from aspenONE Search, so the question is:
How do I delete a purged data source from aspenONE Search? | Solution: To delete an old data source, paste the following URL into your web browser's address bar (after making necessary changes described below):
http://<web_server_name>:8080/solr/update?stream.body=<delete><query><![CDATA[(ace_nav:tag)AND(tag_datasource:<old_data_source>)]]></query></delete>&commit=true
-where-
· <web_server_name> is the name of your Aspen Web Server (you can replace it with localhost instead if you are running this directly on the Web Server),
· 8080 is the port number that Apache Tomcat is using (see Knowledge Base article: Which files do I check when the Tomcat port number was changed from the default 8080 to something else and the Search stops working?)
· <old_data_source> is the name of the data source that needs to be deleted from aspenONE Search
Note, the command will interact with the search database directly.
KeyWords
clean
140222-2
Keywords: None
References: None |
Problem Statement: I have multiple versions of Aspen Flare System Analyzer installed on my machine but cannot get to import HYSYS stream sources into my Aspen Flare model. What can I do to resolve this problem? | Solution: Sometimes, when multiple Aspen Flare System Analyzer (AFSA) versions are installed on a machine, the ‘Import HYSYS Stream Sources’ feature might not work properly.
Something that usually makes the trick to overcome this issue is to run the Aspen HYSYS ‘Set Version’ tool (as Administrator).
For example, let’s assume that a user has the Aspen Engineering Suite V9, V10 and V11 installed on their machine. The user attempts to import Aspen HYSYS V10 material stream data into an AFSA V10 model using the ‘Import HYSYS Stream Sources’, but AFSA launches the error message shown down below:
If the user runs the Aspen HYSYS ‘Set Version V10’ as Administrator, the problem will most likely get resolved.
Keywords: Import Sources, HYSYS Stream Sources, Set Version, Administrator.
References: None |
Problem Statement: I am unable to import my RAM asset register into my Aspen Fidelis Reliability (AFR) model | Solution: Aspen Fidelis Reliability gives users the option to populate their simulation models’ RAM data using the Import function in the RAM Data environment, Home ribbon.
If you find that you are unable to import Ram data and instead are receiving an error message from AFR, try the following:
Check that all the tabs are present in the Excel file for the data you are trying to import. For instance, if importing Event data ensure the following tabs are present; Events, Spare Pools, Schedule and Profile
Check that there are no empty cells in any prepopulated columns. Empty cells are read as null entries by the software and therefore unacceptable. An example of why there might be an empty cell is if you have no date for repair distribution or no Duration Distribution and Parameter data, for that Event. In this case, instead of leaving these cells blank, use ‘Never’ and ‘0’. See snapshot below::
If the installation of MS Office on that user/system account is new, then launch MS Excel as a standalone first to allow MS Excel to complete the initial configuration and post-install set-up. Then attempt the import work-flow again.
It is usually best practice to export the RAM data register from AFR, populate this and then Import. This ensures that any workbook structural issues, highlighted in item 1, will not occur.
Keywords: RAM asset register, RAM data, vsts 457759,
References: None |
Problem Statement: What does the following message mean and how do I fix it?
“Pipe #: The estimate for the outer heat transfer at segment #, increment # may not be valid because the heat transfer is a mixture of free and forced convection" | Solution: This message is generated when the specification for air velocity, in the HTC pipe calculation is very low.
Increasing the value for the air velocity can get rid of the message.
At low velocities, HYSYS assumes the heat transfer could be caused due to fixed and forced convection, however, HYSYS currently has no correlation to estimate the HTC for free convection, thus generating the message above.
In order to model free convection, the user can do a manual calculation of this value and enter it directly as the Overall HTC for the pipe.
Keywords: Pipe, Convection, HTC, Air, Velocity, Estimate, Rating, Segment
References: None |
Problem Statement: Why Does Changing Dimension Set Not Change Unit In Drawing Editor? | Solution: When using the OOTB Heat and Mass Balance (HMB) Header in Drawing Editor, the user may notice that changing the Dimension Set in Explorer does not convert the value displayed in the HMB in Drawing Editor. The Dimension Set actually is supposed to have effect on the entire workspace. The reason why variables are not converted on the HMB is because of the way the HMB was defined in the Graphics Definer. The Graphics Definer tool is used to create objects to be used in the Drawing Editor, such as the HMB Header. The variables displayed in the HMB are defined during this process. In fact, variable such as flow rate which was defined with Unit of Measure should be converted when Dimension Set is changed. Other variables such as temperature and pressure was defined without Unit of Measure. The data displayed are only raw data, and hence the program does not have the basis to convert accordingly with the Dimension Set.
Keywords: None
References: None |
Problem Statement: When attempting to open any Aspen Fidelis Reliability (AFR) file, the user gets the recurrent error message "Recover Model", even if the model was saved correctly. Choosing “Discard Recovery”/”Save Backup As” does not solve the error. | Solution: This error happens when there are unrecovered files, from a previous crash for example. If something got stuck in the temp files that might cause this error to pop up unexpectedly.
To solve this issue, the users can manually clear their temp folder cache:
Make sure there are no instances of AFR open on the machine
Open the following file path C:\Users\<UserName>\AppData\Local\Temp\Fid Files
Delete all the files and folders found in this location.
Relaunch AFR and no Recover dialog should occur
If another crash occurs, then this dialog will come back (if you are not trying to recover, you can disregard the message).
Keywords: Recover Model, Discard Recovery, Save Backup As.
References: None |
Problem Statement: Is there an alternative to the SUMIF formula in Excel to maintain OXE compatibility? | Solution: Currently in APS, the SUMIF formula is not OXE compatible. To maintain the OXE compatibility, you can use a combination of the IF and SUM formulas as follows:
1. IF(D15=5,E17,0)+IF(D16=5,E18,0)+IF(.....)+IF(......)..., or
2. Put all IF conditions in a column below #END and then have a SUM function at the bottom of it which is referenced in the formula cell.
Keywords: None
References: None |
Problem Statement: How to convert a standalone model into an online continuous model | Solution: Aspen ProMV is a multivariate data analysis (MVA) software package that allows the user to deploy and monitor real time models. To deploy an online model, please follow the following steps:
1. Open the desire standalone model, right click and select “Export Online Model”.
2. Open ProMV Online Continuous and click in the “+” to add a new ProMV Online model.
3. In the first ribbon you can enter an analytic name and description of your model to an easier tracking in case you have multiple models.
4. In the “Model” section, click in “Browse…” and select the exported model of the first step
When the model is attached, all the details can be check (i.e. Model Type, R2, Q2, etc.)
5. Click the next ribbon, in this section the user can map the existing tags with the model input variables by:
Search for tags, then drag and drop from the list to the model variable
Browse for a graphic, then drag and drop from the list to the model variable
Upload a previously created .csv file
6. In the next tab, the user can map the existing tags with the model sensor variables by the same ways of the previous point.
7. Click in the "Control Charts" column; in this section the user can set the desire monitoring range of each variable by percentage or a specific value.
8. In the Deploy column, the user can set the detection and diagnosis parameters of the different dashboards and click in "Deploy" button to finish the Online model set up.
9. In the Summary Page, the user can active the desire models to track by clicking the On/Off button.
10. When the Online Model is active:
In the Run time dashboards, the user can monitor Alerts, the SPE, Hotelling T2, Operating Map, etc.
In the Diagnostics View, the user can monitor the SPEX contribution in a trend or control chart way
Keywords: Standalone, Online, Model, Deploy
References: None |
Problem Statement: How do I prevent the tray warning/error "Total liquid rate is above the maximum weir loading" on Aspen Plus? | Solution: On distillation tray columns, at high weir loadings, possible adverse hydraulic results as follows:
Large crests and high froth heights and “jet flooding”
Crests that are so large that those crests do not fit into downcomer mouths, and “choke flooding” occurs
High froth heights sometimes yield excessive pressure drops, and “downcomer backup flooding” occurs
For the maximum weir load limit, Aspen Plus uses a default based on the tray spacing (Resetarits & Orgundeji, 2009); if the operating point approaches 10% within these limits, a warning will show in the hydraulic plots. If the value gets exceeded, an error message will be shown instead.
Tray Spacing
(in.) Maximum Weir Loading
(gal/min per inch)
12 3
15 5
18 8
21 10
24 13
One cure for high weir loadings is increased column diameter.
More often, multi-pass trays are recommended. However, there are some disadvantages to multi-pass trays as follows:
Reduced tray efficiencies
Increased tray costs (more complicated drawings and more tray parts)
Increased horizontal ring and vertical bolting bar costs
Longer tray installation times
Alternatively, we can use swept-back weirs to increase the effective length of the side weirs and decrease the weir loading.
On Aspen Plus, this type of weir can be specified under RadFrac | Column Internals | INT-n | Sections | CS-n | Geometry | Weir Modifications
Three different shapes for swept-back weirs are available, corresponding with designs offered in vendor programs SulCol, KG-Tower, and FRI. Choose one of these shapes, and then specify the geometry parameters in the diagram (RadFrac | Column Internals | INT-n | Sections | CS-n | Geometry | Picketed/Swept-Back Weirs Sheet)
SulCol: Specify lengths A, B, and S, which define the size and shape of the swept-back portion of the weir.
In Interactive sizing mode, if the loading of the side weir exceeds the Maximum weir loading specified on the Design Parameters sheet, S is calculated to ensure that the effective weir loading of the swept back weir equals the maximum weir loading. This effective weir loading is calculated as:
The default for A is 2/3 of the width of the side downcomer, and the default for B is 2/3 of A.
KG-Tower: Specify the depth from the main part of the weir at the point where it is most swept back. The other geometry parameters are defined relative to this.
The default for this depth is calculated in the same way as the default for S in the Sulcol weir.
FRI: Specify the lengths of the three different segments of the weir.
The defaults are calculated in the same way as the default for S in the Sulcol weir.
The following results are displayed on the same sheet:
The tray with maximum weir loading
The maximum weir loading for this tray
The maximum allowable weir loading (from the Design Parameters sheet)
Actual side weir length of swept-back weir
Effective (or projected) side weir length of the swept-back weir
The percentage of tray active area lost due to the swept-back weirs
Keywords: Maximum Weir Load, Weir Loading, Multi-Pass trays, Swept-Back Weirs.
References: None |
Problem Statement: What’s New in V11: Better User Control of Fire Water Header, Loop, and Lateral Piping Calculations | Solution: Currently in the utility piping plant bulk and area level utility piping, the length of firewater loop and firewater lateral piping lines is based on the utility length parameters. The length of firewater loop and firewater lateral lines is 2 times the utility length parameter. Because it is typically different from the firewater lateral length, a separate field has been added after the length parameter to specify the firewater loop length.
A similar change applies to area level utility piping.
NOTE: By default we set the area level utility length parameter to 0. Users need to set the utility length parameter to a non-zero value to get area level utility piping.
The length will be reported in the design data sheet for the plant bulk item or in the area data sheet in case of area level utility piping.
Keywords: V11, new, fire water header, loop, lateral, piping, fire, header
References: None |
Problem Statement: How to use drag and drop functionality in EDR V11? | Solution: Any input node in the EDR navigation tree can be dragged from the source EDR application and dropped anywhere in the target EDR application. Drag and drop can only be between two EDR applications of the same type
The EDR Navigator is shown below. For example, to copy all exchanger geometry, click and drag the Exchanger Geometry node in the source application and drop it anywhere in the target application. To copy the entire Shell and Tube case, drag the Shell & Tube node and drop it anywhere in the target application.
To complete drag and drop of input, you can click 'Yes' on the following window.
Usage notes:
As stated above, drag and drop can only be between two EDR applications of the same type.
Only drag-and-drop of input is supported. Drag-and-drop of Results is not supported.
The drag-and-drop can be canceled by pressing the Esc key. Alternatively, thedrag-and-drop is canceled if the drop is on the source.
All copied data goes into the target application as user input. Default values in the source application will be user-input values in the target application. This may impact active input checking which can set default values for missing input
Keywords: Shell and Tube Heat Exchanger, Drag-and-drop
References: None |
Problem Statement: Is possible to define the Orifice Designation and the In/Out Flanges sizes for a PSV Custom Size Orifice? | Solution: For Standard API orifice sizes, the Orifice Designation and the In/Out Flanges are selected for you as per API 526.
Starting on V11, is possible to define those values for Custom Orifices sizes as well. This can be done from from the Preferences Manager | Orifice Manger, on the ‘Designation’ column. The reported values will be populated according to the API 526.
Note: the values will be overridden if you specify the Flange Sizes, but the designation letter will remain.
How to change orifice sizes for PSV's in the Safety Analysis Environment
Why a PRD reports ‘zero/empty’ for its flange sizes?
How to calculate equivalent length for enlargements and contractions using the Line Sizing tool in the Safety Analysis Environment
Keywords: PSV, PRD, Designation, Custom Orifice Size, Flange Size.
References: None |
Problem Statement: For the Leung Method in PSV Line Sizing, what is the difference between “In line: K Entrance” and “In line: K in” and what information should I enter/read? | Solution: Overall, “In line K” represents the fitting loss coefficient in the inlet piping line. This coefficient is calculated from the fittings that are installed in the pipe. When using the Leung Method, there is no automatic way of calculating the equivalent length from a fittings list, so the coefficient K is used directly to obtain this data. For more information on how K is calculated please review article 32020
That said, the input field In Line: K Entrance allows the user to directly specify the fittings loss coefficient for the inlet piping, this allows the line sizing tool to calculate the maximum Pipe length that can be used for the inlet pipe without exceeding the maximum pressure drop given the specified K.
In Line: K in, represents then the maximum fitting loss coefficient that could be mounted on the inlet pipeline, if the user were to enter any value higher than this on the “K Entrance” field, then Safety Analysis will no longer be able to calculate the maximum I Line: Pipe Length value.
Keywords: Line Sizing, Equivalent Length, In line K, Leung, Safety, Out Line, Length, Dimension, Entrance, Inlet
References: None |
Problem Statement: Do applications that connect to Aspen InfoPlus21 via the API or ODBC return data when Aspen InfoPlus21 is in license denied status? | Solution: YES; Applications that connect to Aspen InfoPlus21 via the API or ODBC will continue to return data. Only applications that verify the license status like Aspen Process Explorer will fail to return data when Aspen InfoPlus21 is in license denied status.
KeyWords:
license denied
api
odbc
Keywords: None
References: None |
Problem Statement: Why a PRD reports "zero/empty" for its flange sizes? | Solution: In the Aspen Safety Analysis Environment, the flange sizes are populated according to the American Petroleum Institute (API) standard guidance table (API 526). When you select a Standard valve orifice, Aspen HYSYS checks that the Pressure and Temperature Limits are not exceeded for the selected valve. If these limits are exceeded, a warning message appears and no flange sizes are reported.
Alternatively, if you are working with Custom Orifices Sizes, you should input the flange size for the custom size as well, otherwise the software will assume its value is zero (<empty>).
Note: Starting on V11, is possible to define the Orifice Designation for a Custom Size Orifice. The values for the Flange Sizes will be populated according to the API 526, even if the user leave the Flange Sizes as <blank> on the Orifice Manager.
For additional information, refer to the next articles:
How to change orifice sizes for PSV's in the Safety Analysis Environment
Is possible to define the Orifice Designation and the In/Out Flanges sizes for a PSV Custom Size Orifice?
How to calculate equivalent length for enlargements and contractions using the Line Sizing tool in the Safety Analysis Environment
Keywords: PSV, PRD, Flange Size, Custom Orifice Size, Zero, Empty, API 526.
References: None |
Problem Statement: How are substreams defined and how do they work? | Solution:
Substream classes are the building blocks of stream classes. Stream Classes are used to differentiate between the properties of each substream in the simulation.
The Substreams classes are for usage of specific types of components on the streams. Depending on which substream class is selected on the Stream Classes, the required information for the stream to be defined changes.
To use the stream classes, one needs to:
Choose one of the predefined stream classes or
Create a stream class and assign the appropriate substreams to the stream class
Substreams can either be predefined or custom. Predefined Substream Classes:
Substream Class Component type Usage
MIXED Fluids Standard components used in VLE calculations; typically vapor-liquid components, but may also be conventional solids present in mixtures in phase and/or chemical equilibrium, including electrolyte salts
CISOLID Conventional Inert Solids Solids that do not participate in phase equilibrium calculations. Are traditionally assigned the substream type CISOLID to distinguish them from other conventional solids
NC Nonconventional solids Materials characterized in terms of empirical factors called component attributes. Component attributes represent component composition by one or more constituents. These solids never participate in phase or chemical equilibrium calculations and are always assigned to the NC substream
NCPSD Nonconventional solids with PSD Nonconventional solids with a Particle Size Distribution specification
CIPSD Conventional Inert Solids with PSD Conventional Inert Solids with a Particle Size Distribution specification
Custom substream classes:
Create an additional substream to complement the predefined substreams.
Custom substreams are used to:
Allow treatment of different solids in one simulation
Permit the use of different PSD's for one predefined substream type
Custom substream classes are specified under the Solids folder | Substreams tab:
Based on the Predefined substream Classes, there are also pre-defined Stream Classes. This Stream Classes use substream classes as definition for them. Which substream classes are used for which stream classes depends upon the pre-defined selections, although the user can select which substream classes are used for each stream class. This is found under the Setup | Stream Class | Stream Class tab:
The predefined Stream Classes are:
Keywords:
substreams, class, stream, solids, nonconventional
References: None |
Problem Statement: Can Aspen Flare System Analyzer perform heat transfer calculations with the environment? | Solution: Aspen Flare System Analyzer (AFSA), can perform evaluations of the transferred heat between the pipe operations and the external environment.
To activate these calculations, the user should verify the following inputs are correctly activated:
1. Under Home | Calculation settings, make sure the checkbox is active to Enable heat transfer.
2. Enter a relevant value for the Ambient Temperature and the External medium velocity. These values will be used to evaluate heat transfer in all the desired pipes, but can be overwritten on each piping item.
3. Identify the pipe(s) where this calculation should be applied, open each element and switch to the Heat Transfer tab, then switch the Heat transfer enabled option to Yes.
If applicable, the user can overwrite the Ambien Temperature and Medium Velocity on the Heat Transfer Tab for each pipe, if left empty, AFSA will use the value specified on the Calculation Settings
Note: By default, all pipe operations are set not to enable heat transfer with the environment, if the option is set to No, heat transfer with the external environment will not be evaluated.
Note: You can use the global pipe editor (Home | Build | Pipes) to activate the heat transfer option in multiple pipes at the same time
4. Once these settings have been applied, the user can run the model and review the updated results.
Keywords: Heat, Transfer, Enable, External, Environment, Ambient, Convection
References: None |
Problem Statement: How can I control the number of rows or columns in the Spreadsheet operation in Aspen HYSYS? | Solution: The user can adjust the number of rows and columns on the top left hand corner of the Parameters tab.
The effect will take place once the user switches back to the Spreadsheet tab of the unit operation, the number of rows and columns will be adjusted to those values specified on the Parameters tab.
Keywords: Spreadsheet, Rows, Columns, Increase, Modify
References: None |
Problem Statement: When using the Aspen Properties add-in in Excel, is it possible to review a historical record of the calculations the Add-In performs, as in Aspen Properties Standalone? | Solution: When running an Aspen Properties Excel add-in file, a temporary history (*.his) file is created under "C:\Users\username\AppData\Local\Temp"
This temporary file, however, does not store the full historical record as Aspen Properties Standalone does, so it's recommended to run the standalone application to obtain a more accurate record of the calculation history.
The standalone application generates a history file (*.aprhis) along with a (*.rp2) file in the same folder. The *.rp2 file stores the data of all property parameters used in Aspen Properties calculation, so this may be the most useful on obtaining information:
Keywords: History, Excel, Add-In, Record, his, Temporary, aprhis, rp2
References: None |
Problem Statement: What is the name of the OPC.DeltaV.1 COM application? | Solution: The COM application name for the OPC.DeltaV.1 OPC server is “FRSOPCDV”.
KeyWords:
DCOM
dcom
identy
Keywords: None
References: None |
Problem Statement: How to replace the IO_Tagnames in Aspen CimIO transfer records using Aspen SQLPlus. | Solution: Here is a query that updates the IO_Tagnames in transfer records for existing occurrences. A CSV file with the format “IO_TAGNAME, IO_VALUE_RECORD&FLD” that contains the updated tag names and existing record and field names is required. IO_Record_Processing must be OFF for the transfer record(s) that will be modified before running the query.
local IOTagname char(80);
local IOValuename char(42);
--
-- Replace 'C:\work\NewTagnames.csv' with the path\name of your CSV file.
--
for (select line as defline from 'C:\work\NewTagnames.csv') do;
IOTagname = substring(1 of defline between ',');
IOValuename = substring(2 of defline between ',');
--
-- Replace "iolongtaggetdef" with the appropriate definition record.
--
update iolongtaggetdef
set io_tagname = IOTagName
where "io_value_record&&fld" = IOValueName;
end
KeyWords:
replace tag names
new tags
Keywords: None
References: None |
Problem Statement: How are Electrical Testing Man Hours calculated? | Solution: ACCE calculates and reports testing man hours for Electrical items in COA 791(Electrical Circuit Testing). These man hours are reported at the area level and do not include any material costs.
The Man Hours for electrical testing are calculated as a contribution of the items installed at the Area level as components or installation bulks and the Substations part of the Power Distribution network. These two contributions are added up in the end to give the final number in COA 791.
The electrical items that are accounted on this testing are the Low, Medium and High Voltage transformers and switchgears, electrical circuits, transmission lines and grounding.
To calculate this number, based on heuristic data the Icarus engine follows the next equations:
Substation Electrical Testing Hours:
6 * No. Low Voltage Transformers
8 * No. High Voltage and Medium Voltage Transformers
4 * No. Electrical Circuits
15 * No. Transmission Lines
4 * No. Grounding Items
3 * No. Low and Medium Voltage Switchgears
4 * No. High Voltage Switchgears
All the above is added up to obtain the Number of Substation Electrical Testing Hours
Area Electrical Testing Hours:
1.5 * No. Motors
2.5 * No. Electrical Circuits
0.3 * No. MCCs
0.15 * No. Grounding Items
3 * No. Low and Medium Voltage Switchgears
4 * No. High Voltage Switchgears
6 * No. Low Voltage Transformers
8 * No. Medium and High Voltage Transformers
15 * Transmission lines
All the above is added up to obtain the Number of Area Electrical Testing Hours
The total Substation and Area Electrical Testing hours are added up to obtain the final Electrical Testing Man Hours.
Keywords: Testing, Electrical, Power, Include, Formula, test
References: None |
Problem Statement: The Aspen Plus stream report is not showing any results. Although the simulation status shows the Results are Available, no data is displayed on the Stream Summary form. | Solution: If you are using Aspen Plus V10 and seeing this behavior, please review article 47643 and try the solution recommended beforehand.
A certain degree of corruption in the file can cause this type of behavior, where the results are indeed calculated and present, but the stream summary is not able to display them. As a workaround, you can open the Run Settings window on the Home Tab:
Click on the Options tab and change the selection for the “Interactively load results” option, this means that if the option was originally deactivated you should turn it on and vice versa.
Apply your changes and re-run the model, this should allow the Stream Summary to populate correctly
Keywords: Empty, No results, Blank, Results, Load, Settings, Summary
References: None |
Problem Statement: Is possible to specify the BatchSep External Exchanger is used for heating AND cooling? | Solution: From BatchSep | Heat Transfer | Configuration | External exchanger you can click on both Heating and Cooling options to specify the unit is used for heating AND cooling. From there you need to choose which will be the Initial Mode as well:
Then you will need to define the Externa Exchanger Heating and Cooling options from their respective tabs:
Certainly, you cannot have the coil heating and cooling at the same time, so you will need to define its behavior from the Operating Steps; on the Process Variable to be change select the External Exchanger Heat Transfer Mode to switch the unit from heating to cooling mode and vice versa:
Check the attached example file for more details.
Keywords: BatchSep, Batch Distillation, External Exchanger, Heating, Cooling.
References: None |
Problem Statement: How can I include a heat exchanger in an Aspen Flare System Analyzer simulation? | Solution: Aspen Flare System Analyzer does not have a heat exchanger model, since it focuses on analyzing the hydraulic aspect of the flare network.
However, the user can add a dummy pipe, which preferably should have the same diameter as the upstream pipe and 0.0 length to avoid unexpected pressure loss.
After adding this operation, the user can switch to the Heat Transfer tab and specify any required duty or outlet temperature spec:
Note: Only one spec can be entered on the pipe operation
After running the model, you should verify the Summary tab for this dummy pipe to ensure your input has been applied correctly
Keywords: Heat, Exchanger, Duty, Temperature, Heating, Transfer
References: None |
Problem Statement: How is Aspen Online connected to retrieve/send data from/to IP.21 (on V9 and newer versions)? | Solution:
Aspen OnLine (AOL) allows automation of the transfer of validated plant data to rigorous process models, removing the need for engineers to perform the laborious and repetitive task.
Due to this information transfer, it is required for AOL to communicate with both the Data Historian and the Advanced Process Control programs. The communication mechanism used to achieve this is Cim-IO, which is a socket-based communication mechanism used to transfer data between applications or databases (such as InfoPlus.21, DMCplus and other AspenTech products) and external devices as well.
Cim-IO runs in a client-server configuration. Client and server components can run on the same computer or on different computers. Multi-threaded client and server applications are supported on Windows Intel systems. Cim-IO relies on TCP/IP to provide reliable, transparent communication between a Cim-IO client and a Cim-IO server.
Cim-IO Client Component
A Cim-IO client component resides between the application or the database that uses Cim-IO and the Cim-IO Core. The function of a Cim-IO client component is to request data from a Cim-IO server through the Cim-IO Core and store the data into an application or a database, or read data from an application or a database and send this data to a Cim-IO server through the Cim-IO Core. Cim-IO client components are specific to the application or database with which they interface. A Cim-IO client consists of a main client component and optional components if asynchronous and/or unsolicited transfers are being used.
Cim-IO Server Component
The function of a Cim-IO server is to provide communication with a device. A Cim-IO server component resides between the Cim-IO Core and the device it communicates with (note that the device could also be a database). The server component receives requests from the Cim-IO client through the Cim-IO Core, communicates with the device and sends replies back to the Cim-IO client through the Cim-IO Core.
A Cim-IO server normally consists of a Device Logical Gateway Program (DLGP) and one or more Device Input/Output Programs (DIOPs).
AOL and IP.21 connection
AOL and IP.21 connection is made by Cim-IO for IP.21. Cim-IO for IP.21 interface needs to be established before AOL can retrieve data from the IP.21 server. The interface is created in the Cim-IO server by a tool called the Cim-IO Interface Manager, which is usually installed on the IP.21 server or a separate server.
From Cim-IO interface manager, a new Cim-IO for IP21 interface is added
Once the interface is established, new services will be automatically added. A new logical device for this interface must be created. From V9 and newer versions, it is possible to set up said interface from AOL. without the need of adding the device on cimio_logical_devices.def file.
1. Click File | Configure CIM-IO
This AOL tool updates the cimio_logical_devices.def file and the services file. This has been done manually in the past. In addition, this does not change anything on the IP.21 server. The user needs to ensure that the correct entries are entered in the services file on the IP.21 server machine
2. In the dialog that pops up enter correct values for IP.21 Server name and ports
3. Set CIM-IO properties for DCS tags
a. Go to “Project Configuration | Tags” and navigate to the CIM-IO tab
b. You can set CIM-IO device one tag at a time, or you can use “Set all CIM-IO properties”
Connection should be made at that point. A quick way to verify everything is correctly set up in AOL is to use the Validate tools in the Home Ribbon, under Diagnostics:
This will give you a list of tags without CIM-IO information configured as well as other configuration information for tags. If not, there are a couple of helpful tips for items to check.
Tip 1: Use CIM-IO Test API tool to test connectivity to IP.21
Use windows search to open CIM-IO Test API as an administrator
Enter the logical device name i.e. IOSETCIM200
Hit Enter until Tag name entry options. Enter 1 for “Please select tagname entry option”
Enter a DCS tag for “Please enter tagname”
Select appropriate data type (e.g. 1 for real)
Hit Enter to “choose default for Device data type”
If connection successful, you should see a GET successful message as shown on the right.
Tip 2: Troubleshooting IP.21 connection
Make sure the port numbers for the DLGP Service (CIMIOSETCIM_200 in the example) and the Hist DLGP Service (CIMIOSETCIMH_200) match on your client machine and IP.21 machine. Check the port numbers in the windows services file at C:\Windows\System32\drivers\etc\. There is a quick section to review this on the Configure CIM-IO section:
Even though the Services File can be accessed through the stated section, when there are connectivity issues, it is still advised to check the services file itself (again, located on C:\Windows\System32\drivers\etc\). Note we need to make sure the port numbers are not conflicting with already existing port numbers. This can be done by searching the services file and ensuring that a unique port number is being used for the CIMIO services.
Ensure the required processes (shown below for IP.21) are running on the IP.21 machine. Use the Task Manager to see this (i.e. Right-click Task bar and select Task Manager). These processes are started automatically by starting the “Aspen CIM-IO Manager” service.
CIM-IO Log location: C:\Program Files (x86)\AspenTech\CIM-IO\log\
CIM-IO Start scripts: C:\Program Files (x86)\AspenTech\CIM-IO\commands\
Keywords:
online, ip21, connection, cimio, rto
References: None |
Problem Statement: Is possible to include Column Internals on a BatchSep? | Solution: When Pressure Profile and Holdups are calculated from tray and packing hydraulics (A) (Setup | Configuration), tray and/or packing geometry must be specified for each stage on the Column Internals form (B):
You can define multiple sets of column internals, but only the one marked as Active will be used for calculating column results.
Each column internals set may contain multiple sections, which are defined below. You can use the following internals types in your column:
Trayed: Uses a simple sieve tray model. Has the option to calculate flooding factor and downcomer backup.
Packed: Uses a simple packing model. Has the option to calculate flooding factor.
Trayed (Vendor)*: Uses rigorous vendor correlations for pressure drop, vapor and liquid flows. Allows multi-pass trays. Calculates flooding factor and downcomer backup.
Packed (Vendor)*: Uses rigorous vendor correlations for pressure drop, vapor and liquid flows, and liquid and vapor holdup. Calculates flooding factor.
*Note: the vendor trays and packing are supported starting with Aspen Plus V11. This feature has been updated to use the tray and packing types and input method from Column Analysis in RadFrac. However, only rating calculations are supported, and the features below are not supported either:
Hydraulic plots
User subroutines
Active area under downcomer
Swept-back weirs
Downcomer balancing
Export to vendor
Montz packing
MD trays
Generic or custom trays
When specifying vendor packing, setting the section packed height does not update the input for HETP, though the value will be reflected in the results.
Alternatively, to overcome the limitations described above, you can use a RadFrac block in the Batch Flowsheet instead: Is possible to include RadFrac blocks in the Batch Flowsheet?
Keywords: BatchSep, Batch Distillation, Column Internals, Tray, Packed, Vendor.
References: None |
Problem Statement: Why is Aspen Flare System Analyzer not using the Heating spec I enter for a pipe? | Solution: In Aspen Flare System Analyzer (AFSA), the user can enter either a Duty value or an Outlet Temperature value to be applied to any pipe unit operation on the Heat Transfer Tab.
AFSA is also able to calculate the heat transfer across a pipe exchanged with the environment, using the ambient temperature and wind velocity data that has been entered on the General Calculation settings or in a specific Pipe element.
However, these two calculations cannot be evaluated at the same time, if the user enables the heat transfer with the external medium in a pipe, AFSA will give precedence to this evaluation, which will cause the specified Duty or Outlet Temp. value to be ignored:
If you wish to force a specific Duty/Outlet Temp spec in a specific pipe, make sure you disable the Heat Transfer in this operation, this does not stop other pipes from evaluating the heat transfer with the external medium.
For more information on how to use Heating specs in AFSA, please review article How can I include a heat exchanger in an Aspen Flare System Analyzer simulation?
For more information on using heat transfer with an external environment please review article Can Aspen Flare System Analyzer perform heat transfer calculations with the environment?
Keywords: Heat, Duty, Temperature, Heating, Transfer, Ignored, Enable, Disable
References: None |
Problem Statement: Where are AspenONE installation logs located? | Solution: The AspenONE installation logs are located in C:\Users\USERNAME\AppData\Local\Temp
KeyWords:
log
MES
Keywords: None
References: None |
Problem Statement: Can I overwrite the Heat of Reaction calculated by HYSYS to match experimental or literature data? | Solution: The Reaction Heat in HYSYS is a calculated value and can not be directly entered by the user. This value is calculated using the Heat of Formation at 25 C values of the participating reactants and products.
In order for the user to be able to modify this value, it's necessary to overwrite the Heat of formation values for these components.
These values can be found by opening the component list in use and double clicking in the desired component to open the component's Properties table. Once this table is Open, navigate to the Point tab and make sure Thermodynamic and Physical Props is selected.
NOTE: The Heat of Formation can be modified directly for Hypothetical Components, the regular library components must first be cloned to allow the modification of this value. For more information on cloning or converting library components please review Article 31664 and for information on how heat of reaction is calculated check article 29530
eywords
Heat of Reaction, Formation, Overwrite, Enter, Properties, Calculation
Keywords: None
References: None |
Problem Statement: How are Instrument Testing Man Hours calculated? | Solution: ACCE calculates and reports testing man hours for Instruments in COA 691(Instrument Testing). These man hours are reported at the area level and do not include any material costs.
The Man Hours for Instrument testing are calculated as a function of the instrument type and quantity in the project.
To calculate this number, based on heuristic data, the Icarus engine will search for the total count of the following devices and apply the following formula:
Instrument Controllers
Thermocouples
Switch Wire Runs
Indicating and Control loops (DCS, etc.)
Local Panel Indicating and Control Loops
Testing MH = 1.75 * Total Device Count
Keywords: Testing, Instrumentation, Include, Formula, 691, type
References: None |
Problem Statement: How does the Schedule Property Bias work for the Yields and properties to which it applies? How does it work for other properties? | Solution: Use the Scheduling Property Biasing dialog box to add, modify, and delete schedule (time-dependent) property bias . A Schedule Property Bias allows the user to modify the properties of effluent (overflow) streams.
Yield biasing is only valid for the properties: VOL and WGT.
If yield biasing is applied to the volume (VOL), the system automatically generates a companion WGT bias. The weight is recalculated based the biased VOL * SPG * volume-to-weight conversion factor (density of water). Similarly, if yield biasing is applied to the weight (WGT), the volume is recalculated based on the biased WGT/SPG/volume-to-weight conversion factor.
SPG can be biased independently. Biasing of SPG independent of yield biasing only affects the SPG of the stream. Therefore, the volume and weight of the stream are not affected.
For Yield Bias:
You have to select the checkbox in the YLD column as shown:
The equation uses by APS will be :
Biased Yield= Current Yield + %Factor*Current yield (Ignore Constant column; factor is in percent)
for example: (1.5/100) *7.9 + 7.9 = 8.01
For other properties:
You have to left unselected the checkbox in YLD column(above). The equation uses by APS is:
Biased Property= Factor* Current Property + Constant (factor corresponds with the exactly number you put it on, not in percent).
Keywords: None
References: None |
Problem Statement: Can I have multiple Aspen HYSYS cases open at the same time in the same Aspen HYSYS window? | Solution: Yes, you can have multiple Aspen HYSYS cases open at the same time.
Every time you open an Aspen HYSYS case in the same window by going to File | Open or by launching an Example file while another case is currently open, the cases that were already active are NOT closed, they are just hiding in a different workspace.
In order to switch the active case go to the File menu and select Activate. This will display a list of Open cases, and you can select any of them to display.
'
Alternatively, you can also use the Activate Case button from the Quick Access toolbar:
Note that you can only display one workspace at a time in a single instance of HYSYS. If you wish to open two cases side-by-side, you will need to open two instances/windows of HYSYS.
Keywords: Workspace, Load, Multiple Cases, Active, Switch
References: None |
Problem Statement: Do I need to install the ABE V11 Local Server on my machine to access the new PSV Datasheets in either Aspen Plus or Aspen HYSYS? | Solution: No, it is not needed to install the ABE V11 Local Server on the clients if the ABE Server being deployed is the Enterprise Server. The Safety Analysis in either Aspen Plus or Aspen HYSYS will call the PSV Datasheets from the server, where the ABE V11 Enterpise Server should be installed.
Unless no Enterpise Server is neither set up nor deployed, then the Local Server will need to be installed on the clients.
Keywords: Local Server, PSV Datasheets, ABE V11, Enterprise Server.
References: None |
Problem Statement: Is possible to specify the BatchSep Coil is used for heating AND cooling? | Solution: From BatchSep | Heat Transfer | Configuration | Coils you can click on both Heating and Cooling options to specify the coil is used for heating AND cooling. From there you need to choose which will be the Initial Mode as well:
Then you will need to define the Coil Heating and Cooling options from their respective tabs:
Certainly, you cannot have the coil heating and cooling at the same time, so you will need to define its behavior from the Operating Steps; on the Process Variable to be change select the Coils Heat Transfer Mode to switch the coils from heating to cooling mode and vice versa:
Check the attached example file for more details.
Keywords: BatchSep, Batch Distillation, Coil, Heating, Cooling.
References: None |
Problem Statement: How to automatically updating attribute value based on changes made in another attribute in ABE? | Solution: Automation can be achieved in ABE using Demon and Event KB script. This article assumes users have already been familiar with the use of these two KB types. In this article, we will utilize ModifyAttribute() Event to automatically update attribute value when another attribute is modified.
A use-case for the following example is when we need to link two attributes together (any changes made to one attribute will also reflect on the other attribute). To make the link consistent with the case in which the data is modified, the attribute to be updated need to be defined with "Case Fixed" property as "False." Also the two attributes must belong to the same class.
[!Modulename= CopyAttributeValue!]
[?Class=ProcessVessels?]
AZEvent ModifyAttribute()
set attrib = eventdata.Attribute
if attrib.Name = "InternalDiameter" then
self.CustomAttribute = attrib.Value
end if
End AZEvent
Keywords: None
References: None |
Problem Statement: How to Uninstall AspenTech Software | Solution: Open the start menu and search for the AspenTech Configuration folder, and open the Uninstall AspenTech Software option (this requires admin rights):
When the new window opens, select the software you want to uninstall (you can select all by checking the Products option) and click uninstall to proceed:
Once this process finishes, it might ask for a restart, please do so to complete the process.
Keywords: None
References: None |
Problem Statement: HYSYS is calculating different pump powers in Dynamic and Steady-State modes. What might be causing this discrepancy? | Solution: HYSYS Dynamics has an Inertia feature that allows the user to model inertia and friction losses to the fluid:
The friction loss to the fluid can significantly contribute to the total calculated pump power:
To prevent HYSYS Dynamics from calculating the friction loss power component, set the Rotational Inertia and Friction Loss Factor parameters to zero:
Keywords: energy, duty, motor
References: None |
Problem Statement: When using a Column Internals analysis in Aspen HYSYS, where can I find the Weir loading results of each tray? | Solution: Weir Loading is calculated and reported when performing a Column Internals Analysis. To find these results the user needs to make sure that the Column Internals Analysis has run and generated results.
Open the Hydraulic Plot results:
In the following window, select the tray or trays you’re interested on analyzing, you can either use the column diagram and click on the tray you wish to review or simply navigate through the plots on the lower section of the window.
After selecting the tray you’d want to analyze, place your cursor over the Weir Loading Plot bars, this will display the value for the side/center weir loading:
You can review the results of any tray, simply select a different tray to see the respective results.
For more information on Hydraulic Plot results please refer to KB 46881
Keywords: Loading, Plot, Internals, Tray, Weir, Analysis, Results
References: None |
Problem Statement: Column pressure variables are not available as ‘write’ variables in the Hysys object VBA library. Therefore, when implementing an automation solution, how can the value of the variables be set from an MS Excel spreadsheet using VBA? | Solution: The Hysys type library (Hysys.tlb) contains all the objects and paramaters associated with the Hysys application and accessible via VBA in MS Excel. Users can create variables in VBA that reference these objects in the Hysys library. However, there are some objects that are not directly available in the library or may be available but may not have the desired behaviour. For example, the Hysys Column stage pressures are only available as read-only variables, in VBA. To write out to them, you would have to access the object variables as backdoor variables. The backdoor variables monikers are not easily known but can be found through scripting.
The example provided demonstrates how the backdorr variables for a Hysys column using Excel VBA. The section of the subroutine most relevant is as follows:
Dim Bstg As Double
Dim Ptop As Double
Dim Pbtm As Double
Bstg = Cstg - 1 'Bstg is the bottom stage of the column, the top stage is 0 so the bottom stage is the total stages offset by negative 1
'set the top-most pressure
Dim bdFS As BackDoor
Set bdFS = colFS
Dim prssVarTop As RealVariable
Dim prssVarBt As RealVariable
'"ColumnStage.500.[]:Pressure.300", [] represents the stage to be accessed, with 0 being the top
Set prssVarTop = bdFS.BackDoorVariable("ColumnStage.500.0:Pressure.300").Variable 'this accesses the top stage pressure as a backdoor variable
Set prssVarBt = bdFS.BackDoorVariable("ColumnStage.500.Bstg:Pressure.300").Variable 'this accesses the top stage pressure as a backdoor variable
Ptop = ActiveWorkbook.Sheets("Main").Cells(2, 7).Value
Pbtm = ActiveWorkbook.Sheets("Main").Cells(3, 7).Value
The example inlcudes an Aspen Hysys model file, with a distillation column named DEHYDRATOR and an MS Excel file. The Excel file is calling the Aspen Hysys file, and setting the pressures for the Top and Bottom stages of the column.
On the Excel sheet, the pressure profile of the column is shown before the update and then displayed after the update. To update the pressure, run the VBA macro by clicking on the Start button.
Cells G2 and G3 contain the values of the new pressures that will be sent to the column in the Aspen Hysys file. Column F reportes the column original pressure profile from when the Aspen Hysys model is just opened and Column G reports the new column profiles after the top and bottom stages have been updated. To close the Aspen Hysys model, use the Close Hysys button.
Running the Example
Download and save the zip file, extract the contents of the Zip file and ensure both files are in the same location. Open the ColumnPressure.xls file. You may provide different values in cells G2 and G3 to represent Top and bottom stage pressures. Next, click Start and this will erase the values in cells G13:G43, update the values in cells F13:43 and finally report the newly calculated pressure profile in celsl G13:G43.
If you want to use the same MSExcel VBA macro to run a different Aspen Hysys model then carry out the following steps:
Place the Aspen Hysys model file in the same location folder as the MS Excel ColumnPressure.xls file
Go to Developer menu tab, Controls ribbon, View Code menu
The desired subroutine is located in Sheet1(Main) and is Sub Start_Click()
Go to Line 42 of the Start-Click() sub routine to find this line of code: Set hycase = hyapp.SimulationCases.Open(ActiveWorkbook.Path & "\" & "Ethanol Dehydration.hsc")
Replace the string text “Ethanol Dehydration.hsc” with the desired Aspen Hysys model file name
Save VBA and close the Code UI and return back to excel. Run the case as described above.
Tips: To ensure the macro runs correctly, make sure that the correct Hysys type library is referenced in the MSExcel VBA environment.
Go to the Developer menu tab and then select View Code from the Controls ribbon. Once inside the coding environment, go to Tools|
Keywords: Backdoor variables, aspen hysys column, column pressures, set column pressures, vba and hysys
References: s menu:
This will open the References-VBAProject form and you should see Hysys X Type Library, with X being the default Hyys version. In this example, the version of Aspen Hysys used is V10, therefore X is 10
If no Hysys library or the incorrect version is referenced, click on Browse and using Windows Explorer, the navigate to the directory where Aspen Hysys is installed, for V10 and older it would be C:\Program Files(x86)\AspenTech\Aspen HYSYS VX.X and for V11 it would be C:\Program Files\AspenTech\Aspen HYSYS V11.0, then find, select and open hysys.tlb. |
Problem Statement: Is it possible to model nozzle welds using UW-16 rules for Partial Penetration? | Solution:
In Aspen Shell and Tube Mechanical (EDR), every nozzle on the Code Calcs is modeled as per UW-16 section of the ASME Sec. VIII Div. 1 code; where the nozzle welds are specified. Per code, every nozzle weld specification falls into the UW16.1 sketches.
One can select most of the available ASME weld types under Exchanger Geometry | Nozzles-Details-Ext.Loads, where the specified Type is based on the sketch code of UW16.1:
The sketch found under the Nozzle Code Calculations should follow the selected type. For example, (c) would look like this:
Same happens when changed to (b):
If you want to model “alternative rules” for nozzles attached by partial penetration welds (i.e., UW16-(d), Neck Attached by Fillet or Partial Penetration Welds), per ASME code, the nozzles following these rules fall into UW16.1 sketches (v-1), (v-2), (w-1), (x), (y), (z), etc. These weld types are not available on the EDR Shell & Tube Mechanical program.
There is currently an enhancement directed to add more Nozzle Weld Types (VSTS 423861). Said enhancement is due for a future release.
Keywords:
Nozzle, UW16, Weld, Mechanical Design, ASME.
References: None |
Problem Statement: Example of a User kinetics subroutine for RBatch | Solution: Attached is an example of a User kinetic subroutine for RBatch
It illustrates the use of IRRCHK, KFORMC, and VOLL calls, and the use of RATES vector.
This routine is a simple illustration of an Aspen Plus user-defined kinetic routine that can be used with any of the kinetic reactors (RCSTR, RPlug, or RBatch), or the pressure relief flowsheeting option. A simple power law rate expression was chosen so that this example can be easily compared with a companion example stored as BATPLAW.INP. The companion example utilizes a standard power law reaction object in place of the user routine. Comparison of these examples will provide a better illustration of how kinetic expressions are defined in Aspen Plus.
In this example, the ethanol and acetic acid reaction is considered. Ethyl acetate and water are formed. Both forward and backward reactions are considered.
The Aspen Plus diagnostic message facility is also illustrated (IRRCHK). Messages are printed to the history file based on the diagnostic level requested by the simulation (sim-level). Messages are printed for diagnostic levels 5 and 6.
C 6/09 fixed initialization
SUBROUTINE USRKBT (SOUT, NSUBS, IDXSUB, ITYPE, NINT,
2 INT, NREAL, REAL, IDS, NPO,
3 NBOPST, NIWORK, IWORK, NWORK, WORK,
4 NC, NR, STOIC, RATES, FLUXM,
5 FLUXS, XCURR, NTCAT, RATCAT, NTSSAT,
6 RATSSA, KCALL, KFAIL, KFLASH, NCOMP,
7 IDX, Y, X, X1, X2,
8 NRALL, RATALL, NUSERV, USERV, NINTR,
9 INTR, NREALR, REALR, NIWR, IWR,
* NWR, WR)
C
Keywords: None
References: None |
Problem Statement: How can I see all the items stored inside an APWZ file? | Solution: APWZ files are compressed folders that contain the actual Aspen Plus file and any auxiliary file needed to correctly run the simulation.
These auxiliary files include Excel spreadsheets linked to a Calculator block, PSV information from the Safety Environment, etc.
The file contained inside the APWZ folder can be either a BKP file or an APW file, for information on how to control the file stored inside the APWZ, please check article 26557.
Being compressed folders, they can be opened by using applications such as WinZip by right clicking on them and selecting Open With:
For Windows 10 systems, the File Explorer can open compressed files, but it will not recognize nor open files with extension APWZ. You can manually change the file extension from APWZ to ZIP, which will enable the File Explorer to open the folder and check its contents, although the approach using WinZip is preferred.
Keywords: APWZ, compressed, open, contents, extension
References: None |
Problem Statement: Is possible to specify the BatchSep Jacket is used for heating AND cooling? | Solution: From BatchSep | Heat Transfer | Configuration | Jacket you can click on both Heating and Cooling options to specify the jacket is used for heating AND cooling. From there you need to choose which will be the Initial Mode as well:
Then you will need to define the Heating and Cooling options from their respective tabs:
Certainly, you cannot have the jacket heating and cooling at the same time, so you will need to define its behavior from the Operating Steps; on the Process Variable to be change select the Jacket Heat Transfer Mode to switch the jacket from heating to cooling mode and vice versa:
Check the attached example file for more details.
Keywords: BatchSep, Batch Distillation, Jacket, Heating, Cooling.
References: None |
Problem Statement: Code calculations using Rich Text are incomplete on V11 | Solution:
Aspen Shell and Tube Exchanger V11 is 64-bit and requires 64-bit Microsoft Mathematics to be installed. On systems where this is not installed, the rich text Code Calculations report will be missing parts:
This is how the section above should look with 64-bit Microsoft Mathematics installed. The missing parts are highlighted:
Keywords:
edr, mechanical, code, calculations, text, v11
References: None |
Problem Statement: Is possible to exclude Heat Exchanger units from the Activated Energy Analysis? | Solution: The easiest way to exclude units from the Activated Energy Analysis (without deleting them), is move them to a Hierarchy block (Aspen Plus) or into a Subflowsheet (Aspen HYSYS), and then just uncheck such Hierarchy/Subflowsheet sections from the Energy Analysis Scope.
How do I transfer several streams and equipment into a subflowsheet?
How do I include multiple parts and unit models within a Hierarchy User Model block in Aspen Plus?
Keywords: Activated Energy Analysis, Exclude units, Define Scope.
References: None |
Problem Statement: Back to basics: how to interpret matrix row and column nomenclature in PSCP? | Solution: In PSCP matrix file dialog, we can search column and row names to find the corresponding matrix structure.
LP matrix row and column names consist of a system-defined type identifier, concatenated with user-defined tags for materials, nodes, modes, & c. Each of these constituent parts is separated from the others by a colon, ':'. These user-defined tags may be variable in length. Tags may not contain colons nor spaces. Tag name are also limited to 20 characters. Overall, LP names are limited to by the optimizer.
For more details, please refer to LP Row and Column Nomenclature in PSCP help document.
Keywords: None
References: None |
Problem Statement: Why are the heat flow terms in my Pipe Segment not balanced? Is the energy balance satisfied? | Solution: In the Pipe Segment Worksheet tab, the energy flow of inlet stream, outlet stream, and energy stream (heat loss) can be viewed from the "Heat Flow" term. With the Pipe Segment as the control volume, this heat flow term should be balanced. But in some cases, users may find that the total inlet heat flow may not be equal to the total outlet heat flow.
This imbalance is because of the omission to report potential energy in the heat flow term. If the Pipe Segment has a vertical flow, potential energy is calculated and reported separately as "Gravitational Energy Change" under Design tab | Parameters page. Summing all inlet and outlet heat flows with consideration of heat loss and gravitational energy change will show that the energy balance is satisfied.
Keywords: None
References: None |
Problem Statement: The Debugging feature in Microsoft VSTA 2017 will not work with Aspen Fidelis Reliability (AFR) V11 unless certain settings are configured in Visual Studio 2017. Instead, AFR V11 will crash when attempting to debug custom routines in VSTA. | Solution: Visual Studio 2017 requires a debug setting to be checked for the debug feature of user coding to work properly. Below are the steps required to ensure the debug setting is checked:
1. Click “Debug” from the Ribbon
2. Select “Options…”
3. Expand the “Debugging” section and select “General”
4. Locate the “Use Managed Compatibility Mode” and ensure that it is checked
5. Click the “Ok” button
Once the above steps are completed, the debug feature can then be used.
Keywords: VSTA 2017 compatibility, crash when debugging, AFR V11 crash, Visual Studio 2017 settings, VSTA debugging
References: None |
Problem Statement: When trying to generate a report in Aspen Flare System Analyzer through File | Print, the following error comes up and Flare closes after hitting Cancel. | Solution: This message can indicate that the Aspen Flare System Analyzer file in use could be corrupted. The message specifically comes up when the user chooses to print the report for All Scenarios.
To fix the corruption on the file and allow AFSA to correctly generate the Print report, the user can re-generate the AFSA file by Exporting the file to Access, Excel or XML and then Importing the data back into a new AFSA file.
For more details on the steps for the export-import procedure please review KB article 000031870.
After regenerating the file, the error message should no longer come up and the user should be able to generate the Print report successfully.
Keywords: Print, PDF, Text, Report, Error, Unexpected Exception, Object, FlarenetFramework, GetResultDataForAllScenarios
References: None |
Problem Statement: What does double banked mean on a Plate Fin Heat Exchanger? How can I select that configuration? | Solution: Double banking occurs on a Plate Fin Exchanger when two adjacent layers of the same stream appear in a layer pattern, or whenever two hot stream layers or two cold stream layers occur together.
You have two options to define this configuration:
Specify a Fraction Double Banked for each layer (Exchanger Geometry | Layer Types)
This input lets you specify the fraction of layers of a given type which are double banked.
For example:
-In the pattern ABBABBABBA the fraction for B is 1.0
-In the pattern ABABBABA, the fraction for B is 0.5, since two of the four layers are double banked.
-If A is hot, and B and C are cold in the pattern ABCACBABCA, then both B and C have a double banking fraction of 1.0
Specify a Layer Pattern (Exchanger Geometry | General | Layer Pattern):
If you specify a Layer Pattern, the fraction double banked input is not needed since the program can work it out from the pattern, but default values will show you the double banking fractions calculated from the pattern.
Where can we give layer pattern in Aspen Plate Fin Exchanger Program?
How to interpret the Layer Pattern results in Aspen Plate Fin Exchanger
Notes: the double banking fraction is not used in layer by layer calculations, so this input is ignored (it is shown greyed out). It can however improve the accuracy of stream by stream (common wall temperature) calculations.
If you do not specify the layer pattern, the double banking fraction is estimated from the layer count. This should be reasonably accurate when there are the same number of hot and cold layers (nearly all single banked) or there is a hot to cold layer ratio close to 2.0 or 0.5, when nearly all the layers of one type will be double banked. In other cases, with the exception of the trivial two stream case, the estimated defaults may be very approximate.
Keywords: Double Banked, Fraction Double Banking, Layer Pattern, Adjacent Layers.
References: None |
Problem Statement: How to model a Wet Gas Compressor in Aspen HYSYS? | Solution: Aspen HYSYS allows the user to specify GMF (Gas Mass Fraction) or GVF (Gas Vapor Fraction) performance curve data for a single or multiple collections.
Note: The Wet Gas Compressor is only an operating mode, is not another unit operation.
To model a Wet Gas Compressor follow these steps:
1. On the Parameters ribbon of the Design tab, select the Wet Gas Compressor operating mode and specify one of the two input options:
Single GMF/GVF: Aspen HYSYS will use single pair of head vs. flow and efficiency vs. flow curve
Multiple GMF/GVF: Aspen HYSYS will use multiple pair of head vs. flow and efficiency vs. flow curve
Note: For more information of how the Feed GMF or GVF is calculated, refer to the following article What is the basis used for the Vapour / Phase Fraction in the stream conditions in Aspen HYSYS?
2. On the Curves ribbon of the Rating Tab, select the desire Gas Fraction basis
3. To add different speed curves for a single GMF or GVF, click in Add Curve... and enter the volume flow vs head vs % efficiency data.
4. To add more GMF or GVF performance curves, the can click on:
Add Curve Collection to add a blank collection
Clone Curve Collection to copy the existing data of the current collection
5. To enter the Surge and Stonewall Curves (only applicable in Dynamics), select the Flow limits ribbon and click on Enter Surge Curves and/or Enter Stonewall Curves where you can specify the specific GF.
6. To compare the performances of the multiple collections, select the "Plot all collections" option and click on Plot Curves
Note: If the "Plot all collections" option is not check, only the collection that is selected will be plot.
Keywords: Wet Gas, Compressor, GVF, GMF, Multiple
References: None |
Problem Statement: When we use APS and open an excel file we cannot reload simulator because APS looks for the index/excel macros in the wrong excel file rather than in the Units file linked to APS.
If we do not have any other Excel file open we can reload simulator because APS can find the macros of the correlations, if there is one or more excel files opened APS cannot find those correlations anymore and it gets stuck. | Solution: The issue can be resolved by adding EXCEL_IGNORE_REMOTE_REQ keyword in the CONFIG table. Please set the value to "Y".
This way Excel files are open in different instances of Excel and do not interfere with APS Simulation and excel interaction. It prevents APS, MBO from accessing the incorrect workbook in the shared Excel session.
Keywords: Multiple
Excel
CONFIG
Units file
References: None |
Problem Statement: Example of hematite (Fe2O3) production from Iron chloride with HCl scrubbing | Solution: To simulate the process of hematite production, we will part from the reactions which form said component. We are going to obtain hematite from a couple of iron chlorides, which reactions are:
The solid hematite is separated, whilst the remaining HCl is cooled down and separated on an absorber column, with more water being fed from the top which effectively scrubs the HCl down to the liquid product.
Considerations
This example was developed for an Aspen Plus simulation with gas components (N2, O2 and HCl) and solid components FeCl2, FeCl3 and Fe2O3. Selected Property Method was ELECNRTL with specified Henry Comps N2, O2 and HCl.
The flowsheet consists of a simple scrubbing process, starting with a reactor which retrieves the desired hematite and HCl by-product. The hematite is then separated as the main product and the Vapor product is cooled down and fed to the absorber column, in which the HCl is scrubbed down and the Off-Gas is vented.
Keywords:
scrub, hematite, hcl, plus, elecnrtl
References: None |
Problem Statement: Example of a User kinetic subroutine for RPlug | Solution: Attached is an example of a User kinetic subroutine for RPlug
It illustrates the use of IRRCHK, KFORMC, and VOLL calls, and the use of RATES vector.
This routine is a simple illustration of an Aspen Plus user-defined kinetic routine that can be used with any of the kinetic reactors (RCSTR, RPlug, or RBatch), or the pressure relief flowsheeting option. A simple power law rate expression was chosen so that this example can be easily compared with a companion example stored as PLUGPLAW.INP. The companion example utilizes a standard power law reaction object in place of the user routine. Comparison of these examples will provide a better illustration of how kinetic expressions are defined in Aspen Plus.
In this example, the ethanol and acetic acid reaction is considered. Ethyl acetate and water are formed. Both forward and backward reactions are considered.
The Aspen Plus diagnostic message facility is also illustrated (IRRCHK). Messages are printed to the history file based on the diagnostic level requested by the simulation (sim-level). Messages are printed for diagnostic levels 5 and 6.
C 6/09 fixed initialization
SUBROUTINE USRKPG (SOUT, NSUBS, IDXSUB, ITYPE, NINT,
2 INT, NREAL, REAL, IDS, NPO,
3 NBOPST, NIWORK, IWORK, NWORK, WORK,
4 NC, NR, STOIC, RATES, FLUXM,
5 FLUXS, XCURR, NTCAT, RATCAT, NTSSAT,
6 RATSSA, KCALL, KFAIL, KFLASH, NCOMP,
7 IDX, Y, X, X1, X2,
8 NRALL, RATALL, NUSERV, USERV, NINTR,
9 INTR, NREALR, REALR, NIWR, IWR,
* NWR, WR)
C
Keywords: None
References: None |
Problem Statement: This solution outlines what may cause an Instrument alarm to display the error message below even though the analytic is already deployed. It will also discuss how you can prevent this error message from appearing in the future. | Solution: This error message occurs in a deployed model if Aspen Asset Analytics attempts to refresh the model with new rule history data where no rule history data exists. By default, Aspen Asset Analytics attempts to refresh rule history data every 5 minutes, so if the record associated with Instrument alarms does not update with at least one new data point every 5 minutes, this error will occur.
To work around this issue, you will need to increase the rescan rate for checking rule history data. Navigate to the web.config file (By default, this is located in C:\inetpub\wwwroot\AspenTech\AspenAnalyticsService) and edit the file using notepad. Search for the string “RuntimeTimeLength” to find the following entry:
<!--How much recent time used for runtime alert check, seconds-->
<add key="RuntimeTimeLength" value="300" />
Change the value from 300 to a higher value to ensure that there will always be at least one rule history data point in a given scan cycle. Save the file and close notepad. Open IIS Manager and restart the “AspenAnalyticsAppPool” Application Pool. This error message should no longer occur.
Keywords: :
References: None |
Problem Statement:
Known issue: Excel add-in runtime error in V11 and V10 | Solution:
A problem was found with the signing of Excel VSTO (.NET) add-ins. This problem affects add-ins used for Aspen Basic Engineering and Aspen Fidelis Reliability, V10 and V11.
The issue will be fixed with an emergency patch. In the mean time, here are the possibilities of what the user would see (depending on the application and how each uses the VSTO add-ins) and its workaround:
1. A warning asking them to accept a customization of Excel when accessing the VSTO add-in from these applications. If they see this, then if they accept it then the add-in will continue to work.
2. They could also just see the add-in fail to load. This will likely happen with Aspen Basic Engineering add-ins. To workaround this problem, close the current Excel instance, open a new blank Excel instance with Admin privilege (note that you need to open through Microsoft Excel shortcut, do not open Excel through Datasheet Definer or Excel Datasheet Editor shortcuts). Then, navigate to enable the add-ins via COM add-ins. You should see the following window popped up, proceed to click "Install". The issue should be resolved. This procedure should only need to be done once.
Keywords:
EDSE, Datasheet Definer, ABE, missing add-ins
References: None |
Problem Statement: What is a hyFluid and how to use it? | Solution: A hyFluid object is derived from a single Process Material Stream and is an internal copy of a Process Material Stream (share many of the properties) that can be manipulated for property calculation purposes without interfering in the simulation.
To create a hyFluid from a Process Material Stream and use it to perform a flash calculation, the command "DuplicateFluid" must be used to return a Fluid object; a variety of flashes (PV, TP, PH, etc) could have been performed to evaluate different conditions as shown in the following code:
Public Sub FluidExample(pressureval As Double)
Dim hyFluid As Fluid 'Declaring the variable as a Fluid Object
Dim hyStream As ProcessStream
Set hyStream = hyCase.Flowsheet.MaterialStreams.Item(0)
Set hyFluid = hyStream.DuplicateFluid 'Copying the information from the desire Stream
hyFluid.PVFlash pressureval, 0 'Doing a PV with a pressure value of zero
End Sub
Keywords: Fluid, Stream, Duplicate, Properties
References: None |
Problem Statement: When using Oil and Gas Feed option in a stream, in the section of Gas-Oil Flash Calculation, pressure and temperature are specified for each stage as well as GOR and WOR information, and when observing the Stage GOR, it can be seen that the Total GOR is not the cumulative sum of each stage GOR. | Solution: GOR is the volumetric model flow ratio of gas and oil, while WOR is the volumetric flow ratio of water and oil. However, when more than one stage is selected, the calculations changes and are as follows:
The first stage is flashed at set conditions, then only liquid phase goes to next stage where now it is flashed to new stage conditions, then it goes the same for each stage. Hence, for stage i, stage GOR and Total GOR are calculated by the next equations:
Where V and L are the volumetric flow of vapor and Liquid respectively and n is the cumulative number of stages. When n=N, the total number of stages, Total GOR is the same as the one set by the user.
WOR calculation is similar to GOR, the only difference is that instead of Vapor flow it is water flow.
Also, it can be noticed that none of the variables are the accumulate and do not satisfy a volumetric balance since every stage has different conditions.
Keywords: GOR, WOR, Oil and Gas Feed, Total GOR
References: None |
Problem Statement: As mentioned in the article What is a hyFluid and how to use it?, Aspen HYSYS allows the user to generate a copy of a Process Material Stream and evaluate different flash conditions but in some occasions after the user sets a new flash condition and retrieves a thermodynamic property it isn't updated or an empty appears | Solution: Every time the user changes a flash condition (i.e. T, P or H) of a hyFluid object it must be reflash to retrieve the new thermodynamic properties at those new conditions as the Aspen HYSYS Engine doesn't do it automatically.
The following type of flashes can be done in a hyFluid:
For a Pressure-Vapor Fraction: hyFluid.PVFlash DesirePressure, DesireVaporFraction
For a Pressure-Entropy: hyFluid.PEFlash DesirePressure, DesireEntropy
For a Pressure-Enthalpy: hyFluid.PHFlash DesirePressure, DesireEnthalpy
For a Temperature-Vapor Fraction: hyFluid.TVFlash DesireTemperature, DesireVaporFraction
For a Temperature-Pressure: hyFluid.TPFlash DesireTemperature, DesirePressure
Example:
Dim E As Double
Dim Presvalue1 as Double
Set HyFluid = hyStream.DuplicateFluid
'Isentropic flash at the current pressure
Presvalue1=10 'KPa
E = hyStream.MolarEntropy
HyFluid.PEFlash Presvalue1, E
Keywords: hyFluid, Flash, Update, Thermodynamic property
References: None |
Problem Statement: It is common that users compare thermodynamic models within Aspen HYSYS such as NRTL and General NRTL and observe that there are no real differences in VLE behavior of mixtures between both applications. | Solution: Aspen HYSYS has two different NRTL Fluid Packages, one is NRTL and the other is General NRTL, both models are the same NRTL model indeed:
The real differences lies in the parameters form and the options to calculate these parameters, NRTL model offers a limited unique option to calculate parameters, whereas General NRTL has different options with different binary parameters depending on the calculation model selected, which provides an advantage when entering experimental data or when trying to use binary parameters from other databases, such as Aspen Properties database which cannot be used in NRTL, only in General NRTL. Ahead both parameters model calculations are presented.
HYSYS NRTL Parameters:
General NRTL parameters:
Both default models are giving very similar results, with very little differences in VLE results, thus as mentioned, the main differences is the options that can be used.
Keywords: NRTL, General NRTL, Binary Parameters
References: None |
Problem Statement: How to Control Volumetric Amount of a Stream (or the Addition of Several Streams) in a Submodel of PIMS? | Solution: This question was asked frequently recently. A dummy capacity structure should be added to calculate this.
If you are in table ASSAYS and would like to control the total amount of a crude cut, here is what you should consider:
First go to table ASSAYS and add a dummy CCAPXXX structure. This is not a real capacity, but a dummy capacity that controls the addition of the coefficients x variables you’d like to add up. The “XXX” could be any 3-letter tags you want, but make sure it is the same “XXX” 3-letter tag you are going to use in table CAPS. All these options depend on what coefficients you put in the submodel.
The following is how to control a specific amount of cut. Don’t forget you could put a number at the eight character of “CCAPXXX” to indicate what logical crude unit is this capacity row constraining. The example controls the total amount of cut HD1 that is going to be generated from all of the crudes in CD 1 together.
Then in Table CAPS, put the actual min and max unit of stream that you wish to control.
Another scenario is we could control the amount of stream/gas produced or incoming into a submodel. It follows the same structure.
In the actual submodel:
In table CAPS:
Please note this example is for a PPIMS model. If you are using regular PIMS or MPIMS, the column names will change in table CAPS.
Keywords: None
References: None |
Problem Statement: How can I add streams in APEA? | Solution: After opening a project within Aspen Process Economic Analizer new streams can be developed. The user can develop completely new streams or use an existing stream as a base, this can be done either from the Project Basis View window or from the Process Flow Diagram. Both procedures are described below.
From the Project Basis View:
Right-click the Streams form in the Project Basis View and select Edit.
The Develop Streams dialog box will appears. Select the Create tab.
In the Streams tree structure, select User to create a new process stream or Utility to create a utility process stream.
Note: In the Create tab you can add process and utility streams, and use existing streams as a base. The new stream can be either copied from the existing stream (Absolute Basis mode) or copied from and linked dynamically to the existing stream so that when the base stream is changed the new stream inherits these changes (Relative Basis mode).
Click Create. The Develop Stream window will appear.
Specify the stream information, such as: primary fluid component, temperature, pressure and liquid mass flow
Click OK to return to the Develop Streams dialog box
From the Process Flow Diagram:
Go to View | Process Flow Diagram and select the button Add stream and create the new utility stream
Then, the Develop Streams window will appear where you can add process and utility streams and use existing streams as a base.
These new streams can be drawn and connected to the equipments in the PFD using the Draw Disconnected Stream and Edit Connectivity buttons at the top of the PFD.
Keywords: Add, create, modify, delete, connect, utility, streams
References: None |
Problem Statement: Why is MW difference observed across the KO drum? | Solution: Inside Aspen Flare System Analyzer KO Drums are used to allow liquid to separate from the feed stream so that it can be removed from the flare system. This block completely removes the liquid phase flow going into the separator feed from the upstream elements of the network, this is applied to the outlets of this object. When liquid is present at the outlet(s), the most likely cause is the condensation phenomena, which can occur due to the pressure conditions change on the downstream pipes.
Once all liquid phase flow has removed from the feed stream, it’s expected that there will be a change of MW in between the inlet & outlet stream for a KO drum as below.
Keywords: Liquid, Outlet, KO Drum, Vapor
References: None |
Problem Statement: If a user does not have access to SQL server db, how could an APS user differentiate between active and inactive crudes? | Solution: The solution to this question needs us to understand the similarities and differences between CRUDES, CRUPROPS, and CRUDCUTX tables.
The user could still view the data in results tables from “Table View” in APS. For table CRUDES, by design, it shows the records from APS memory. APS does not load inactive crudes in the memory so only active crudes are shown.
If you look in the Table View of CRUDES table and compare it with the table in the SQL DB (admin on the db), you will see the CRUDES table from Table View in APS has more columns than the actual DB. This is because APS loads the table by memory. CRUDES table is the combination of CRUDES, CRDCUTX, and CRDPROPS. CRDCUTX and CRDPROPS have both active and inactive crudes, but because CRUDES only loads the active crudes by memory, the combination of the three is what you see in the end - an in-memory table not a physical one.
The user could separate the active and inactive crudes. A comparison could be done between table CRDPROPS/CRDCUTX and table CRUDES. The reason is CRUDES table has all active ones, and CRDPROPS/CRDCUTX has both active and inactive crudes. So a comparison could be done to filter out the inactive ones. This is a manual process but it is possible. In V12, this functionality has been added for the users.
Keywords: None
References: None |
Problem Statement: In occasions it is necessary sending some properties from all the streams in a Aspen HYSYS simulation to ASW and linking each property of each stream in ASW can take much time. | Solution: In Aspen HYSYS, in Home tab there is an option called Model Summary Grid, which displays some properties of all the streams in the simulation in a template table, it also can display results from unit operations, feed and product streams.
The template can be modified according to the properties that the user needs to send to ASW, the template can be modified following these steps:
1. Click in the dropdown arrow of the Default template and click on <Manage templates>. A window will prompt with all the templates available, if there are no templates just click on New, if there are already created templates just click on Edit in the templates to modify them. Clicking on New or in Edit will allow the user to select the variables displayed in the table for each option of the model grid template. You can give it a name as well, click on ok to apply the changes.
2. Then click again in the dropdown arrow of template and the created template will be available now, select it to be the displayed template.
3. Now copy the properties wanted to be reported and paste them in the table. It is a simple copy and paste using right click or Ctrl+C and Ctrol+V, when a variable from a single stream, viscosity for instance, is copied and pasted into the table, the viscosity from all the streams will be pasted in the model table.
4. The properties have been pasted in the model table, but all of them are named Overall, to change their name go to Manage templates again and click on Edit this template, here you can change the name of the variables you have pasted.
5. Once that the table is ready, just click on Send to Excel/ASW, a window will prompt to ask you what sections of this table send to Excel. Also, you can choose if each table should be sent to one worksheet or all tables in the same worksheet.
6. Finally click on Export table to Excel and it will ask for a location and name of the file. Click on save and the table will be sent to Excel, select Open Excel file to review the properties table in Excel.
This way of sending properties to Excel will allow a fast connection between Aspen HYSYS and ASW, so users can get a stream report faster in Excel.
Keywords: Model, ASW, Excel, Model Summary Grid
References: None |
Problem Statement: What is the Relationship Among Tables CRUDES, CRDCUTX, and CRDPROPS and How do They Work Together in APS? | Solution: The above question needs to be answered when the user would like to activate or deactivate a crude in APS. In the current functionality, if the user is not the admin of the SQL server db of the model, then the user cannot directly activate a crude. The db admin needs to do that part. However, from V12 onwards, we have added a feature that allows the users to do this directly in APS.
When looking into the information of CRUDES, CRDCUTX, and CRDPROPS in APS table view, you might find they are showing different sets of crudes. This is because CRUDES table only loads whatever is in the memory, and APS doesn’t load inactive crudes which are not in the memory. On the other hand, CRDCUTX and CRDPROPS are showing both active and inactive crudes which means if the user compare CRUDES with CRDCUTX or CRDPROPS, the inactive ones will be filtered out.
This is a manual way for the user to find out which crudes are active and which are not, but please keep in mind that db admin is needed to activate a crude in an APS version prior to V12.
Keywords: None
References: None |
Problem Statement: How to manually upgrade Aspen Report Writer to a newer version? | Solution: To manually upgrade Aspen Report Writer to a newer version, users may first get AspenRpt.dll and AspenRpt.xla(m) files of newer versions and follow steps below to properly set up Report Writer.
1. Place new version AspenRpt.dll in C:\Program Files (x86)\Common Files\AspenTech Shared.
Place AspenRpt.xla(m) in excel library path which could be found from ARW>>Excel Library Path menu.
2. Register new version AspenRpt.dll file.
The upgrade command for ARW .NET version uses Regasm.exe command.
For 32 bit office, use 32 bit version on C:\Windows\Microsoft.NET\Framework\v4.0.30319
For 64 bit office, use 64 bit version on C:\Windows\Microsoft.NET\Framework64\v4.0.30319
Workflow to register dll:
Run regasm.exe "C:\Program Files (x86)\Common Files\AspenTech Shared\AspenRpt.dll" /unregister
Replace AspenRpt.dll in C:\Program Files (x86)\Common Files\AspenTech Shared
Replace AspenRpt.xlam in office library folder
Run regasm.exe "C:\Program Files (x86)\Common Files\AspenTech Shared\AspenRpt.dll" /tlb:"C:\Program Files (x86)\Common Files\AspenTech Shared\AspenRpt.tlb" /codebase
3. Update the registry key.
In the following registry keys, enter the correct excel library path of AspenRpt.xla(m).
64 bit office
\HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Excel\Options\OPEN
32 bit office:
\HKEY_CURRENT_USER\Software\Wow6432Node\Microsoft\Office\16.0\Excel\Options\OPEN
Keywords: None
References: None |
Problem Statement: Is CIM-IO communication possible through a firewall?
Installation of firewall: What ports are used for communication between Aspen InfoPlus.21 and Aspen CIM-IO server?
What ports are used for communication between Aspen InfoPlus.21 and Aspen CIM-IO Redundancy (Primary and Secondary) systems communicating with each other? | Solution: Yes, CIM-IO communication is possible through a firewall. The ports assigned to Aspen CIM-IO processes On the Cim-IO Interface server are used to tranfer data between the Cim-IO client and server.
What ports are used for communication between Aspen InfoPlus..21 and Aspen CIM-IO server?
Aspen CIM-IO client tasks on IP.21 (TSK_M_XXX, TSK_A_XXX, etc) communicate with the Aspen CIM-IO server (CIM-IO to XXX) via TCP/IP using port numbers specified in the services file (Windows\system32\drivers\etc).
Aspen CIM-IO Redundancy (Primary and Secondary) systems communicate with each other using the same TCP/IP port numbers specified in this services file on each machine.
Here is an example of an excerpt from a Services file on a Aspen CIM-IO server machine.
CIMIOMANAGER 7777/tcp
CIOPROCESSXOPCS 10017/tcp
PROCESSXOPCS_SC 10018/tcp
PROCESSXOPCS_ST 10019/tcp
PROCESSXOPCS_FW 10020/tcp
You are going to need to open the ports listed in the services file between the Aspen InfoPlus.21 CIM-IO client and Aspen CIM-IO server machine.
Questions that are asked when installing firewall:
Q: What ports does Aspen Cim-IO need open for Aspen InfoPlus.21 to communicate across a firewall?
A: Keep open whatever ports are defined in the Services file for Aspen CIM-IO. i.e. Store and Forward processes, DIOPs and DLGPs, and the CIM-IO Manager service.
KeyWords
redundant CIMIO
redundancy
fire wall
Keywords: None
References: None |
Problem Statement: In our refinery usually we send products to a ship from two or three different tanks. For us it is important to target the qualities in the ship, even if one or more tanks are off spec or in give away.
The function Blend Groups in MBO it seems to target Hdr combine quality, but we have to consider complete tanks quality and the mix of tanks qualities in a ship. | Solution: Attached model (use case WA) demonstrates approach helping customer to set blend group (for U87 from T87A and T87B) considering tank heels also.
The main idea is as follows:
Define a tank representing the ship (SHIP)
Define virtual tanks for each product tank (VT and VT2) that can send product to the ship
Define a virtual component for each tank and add Property Balances for all the specs of the product blended at the ship
Define a new product for the product blended at the ship and add the virtual components to it.
Create a transfer between the real product tank and its corresponding virtual tank; this transfer's finish time has to be linked to the last blend in the real product tank and must be very short (we recommend no more than 1 hour)
Open this transfer with min = 0 and max = some large number
Create a blend of the product blended at the ship starting after the transfers are finished
You can see the transfers and blend created for the workaround in the screenshot below
Note that you need to define initial properties in the dialog Model->Beginning Inventories for all the new tanks introduced in the workaround
Keywords: blend group
shipment
specification
References: None |
Problem Statement: Detailed guide is needed to configure clustering in PIMS V10 | Solution: There are some KB articles available for cluster configuration in PIMS like:
How to configure machines for cluster processing of Aspen PIMS
How to define nodes for Aspen PIMS-AO cluster processing
Here you can find more comprehensive guide, which is applicable for V10 and later versions.
Attached document has two parts. Part 1 is to verify that the PIMS clustering feature works using sample models. This tests the PIMS clustering feature using the node configuration. Part 2 is to configure clustering.
Keywords: cluster
parallel processing
PIMS-AO
nodes
performance
References: None |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.