question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
|---|---|
Problem Statement: How do I select the location of the center tube on a center line? | Solution: There are certain ways to do so in Shell and Tube Exchanger (S&T Exch) and Shell and Tube Mechanical (S&T Mech). Please use the steps below to select the location of center tube.
For Aspen Shell & Tube Exchanger: When in Rating or Simulation Mode, you can select the center tube location (Off center line or On Center line) by first opting for ‘New,match pass details’ for the Tube layout option at the Input-Exchanger Geometry-Bundle Layout- Layout Parameters tab.
After you select that option, move to the Pass Details Tab and there for Tube in reference location select ‘Yes’ for first tube is on center line and ‘No’ for first tube is off center line.
For Aspen Shell & Tube Mechanical:
You can go to Input-Exchanger Geometry-Tubesheet Layout- Details/pass partitions tab and select the options for center tube location.
The lane clearance will control the offset to the center-line when you select the off center line option.
Keywords: Tube Layout, Pass Details, Bundle layouts
References: None |
Problem Statement: When running an EDR file, user gets a Visual Fortran run-time error. How can user solve this problem? | Solution: This problem is caused because users changed some data files in the location of customized database folder, which is specified in File> Options. By default, the directory is C:\ProgramData\AspenTech\Aspen Exchanger Design and Rating V X.X
Users have two potential solutions if that error comes:
1. Rename the files ( G_COMPNA.PDA and G_PROFIL.PDA) in this directory C:\ProgramData\AspenTech\Aspen Exchanger Design and Rating VX.X. When user run a S & T mechanical example, program will recreate them. Since they are only files related with Headings, it won't take a very long time to recover users' information manually.
2. If the first method didn't work, users can rename the whole folder in this directory C:\ProgramData\AspenTech\Aspen Exchanger Design and Rating VX.X. This action will cause the program recreating new customized database folder. Users may lose all the customized data if they have any before.
Keywords: Visual Fortran run-time error, forrtl: severe (64), customized database folder
References: None |
Problem Statement: How do I upgrade the customized material database from lower version to higher version? | Solution: In this solution, we will use upgrading EDR V8.4 to V8.8 as an example.
Method 1: Create Separate Database
1. Find the customized database directory by going to EDR V8.4. Tools / Program Settings / Files. You should see the default location. In this example, it's C:\ProgramData\AspenTech\Aspen Exchanger Design and Rating V8.4
2. Go to that location and find three files. Copy those files
3. Open EDR V8.8 and go to File / Options / Files
4. Go to the directory and paste the three files.
5. You can check if you have the exact same database from Customize / Material Database
Method 2: Share the same database
1. Open the EDR V8.4 and check the default database directory by moving to EDR V8.4. Tools / Program Settings / Files. Copy the directory
2. Open EDR V8.8. You can go to File / Options / Files and change the directory as the same as the EDR V8.4 customized database directory.
3. You should be able to see the old customized database from Customize / Material Database
Keywords: Customized Material Database, Upgrade Database, Version
References: None |
Problem Statement: How to prevent users from adding User Data Sources in ADSA Client configuration tool. | Solution: Locate dsaconfig.exe present in the C:\Program Files (x86)\Common Files\AspenTech Shared\Adsa
Rename the dsaconfig.exe to something else, say dsaconfig1.exe.
After you rename, once you click on "User Data Source" in ADSA, nothing should happen.
Fixed in Version
CQ00598131: Defect closed with workaround.
KeyWords
ADSA, User Data Sources, Citrix Server
Keywords: None
References: None |
Problem Statement: What is the difference between total tube length and effective tube length in Aspen Air Cooled Exchanger? How do they impact the calculation of finned surface area? | Solution: The total tube length includes the ends fitted into the tubesheets and where the tube comes into contact with tube supports. This input item is only used for tube side pressure drop and exchanger weight calculations.
The "Effective Tube Length" is is the length of tube that is exposed to heat transfer, it is calculated from the "Total Tube Length" minus "Support Plate Thickness" times "Number of Supports", minus "Tubesheet Thickness" times "Number of Tubesheets". The program calculates the finned surface area based on the effective tube length.
To see how the effective tube length is calculated in Aspen Air Cooled Exchanger, from the total tube length, please refer to the solution ID 127955.
Keywords: effective tube length, finned surface area
References: None |
Problem Statement: Why is there no condensation calculation when using gas on the outside of the Aspen Air Cooled Exchanger? | Solution: Dry gas is appropriate for waste heat recovery units where gases such as flue gases are being cooled. Also for any exchanger where gases other than or including air are handled. It should be noted that Air Cooled Exchanger cannot handle condensation of any of the components of the gas stream. However, if condensable components are defined then the following warnings will be issued if there is any likelihood of condensation occurring on the surface or in the bulk stream.
When a gas is specified, the user has to supply properties through the normal Physical Properties input.
The dehumidification calculations will only work when the user selects humid air with the Air Cooled Exchanger program.
Keywords: Warning 4026, Dry Gas, Condensation
References: None |
Problem Statement: How does the Aspen Shell & Tube Exchanger package estimate the cost of the exchangers? | Solution: The Costing Calculation can be thought of as a costing simulation as it considers all aspects of the fabrication process. The costing calculation is performed as part of the mechanical calculation run. Within a program run, once all the geometry of each component part of the heat exchanger has been calculated the costing calculation can be performed.
As well as the geometry, the program requires material costs and labor rates. Both of these data items will vary from fabricator to fabricator so an important part of the material database is the ability for users to update material costs and labor rates to suit their own particular requirements. EDR supplies a standard database with each version of the program. When you make any changes to the database, your changes will always override any values in the standard database.
The three elements of the exchanger cost are the material cost, the labor cost and the mark-ups on material and labor. The material costs are determined component by component using the material prices from the material database and the rough dimensions calculated as part of the mechanical design. The material prices can be changed to suit the local market conditions. The labor costs are determined from the labor rate (hourly rate) and the labor hours required to fabricate each component and assembly within the shell and tube heat exchanger. The labor hours come from correlations that have been developed from several hundred labor estimates for a wide variety of exchanger types and design conditions. These correlations are a function of design pressure, shell diameter, weight, tube length, and material. The hours required for every shop activity and for the fabrication of every component can be changed by modifying the Labor Efficiency Factors. The mark-ups are a quick way of customizing the answers as these can be used to increase or decrease the calculated exchanger cost.
The input data for the costing calculation consists of the following:
? Shell and Tube Heat Exchanger geometry
? Materials of Construction
? Material Prices
? Fabrication Efficiency Factors
The mechanical design performed by the program which includes the geometry data on the input screens, provides the shell and tube heat exchanger geometry. The Input screens provide the materials of construction. The Costing Database will provide the Material Prices and the Fabrication Efficiency Factors.
The best method to adjust the Costing Databases for changes in manufacturing process requirements that are dependent upon exchanger size and/or pressure is to set up multiple sets of costing database files. These different sets can be stored in different folders. When you design a specific exchanger you would point the program to the applicable folder for the type of exchanger being designed. All of the data contained within the costing database is stored in a series of database files (*.pda files). Initially there is a single set of these files that would be used each time the program is run. It is possible to create multiple copies of these files to reflect different circumstances. The program will use which ever set it is told to use.
By default these are located within C:\Program Files\AspenTech\Aspen Exchanger Design and Rating VXX.XX\Dat\PDA. If you want to have multiple sets of these files then you can create a new directory structure then change the location of the costing files by selecting => Tools | Program Settings | Files, then selecting a different location for the ?Folder for customized database files?.
The Costing Database is a database maintenance program, designed to modify and/or print the contents of the labor and material cost files associated with the Aspen EDR programs which address cost estimation. To access the Costing Database go to => Tools | Data Maintenance | Costing Database. The Exchanger Costing Database gives you access to these databases:
Material prices are listed for each individual material specification within separate material standard spreadsheets.
The first column lists the B-JAC material number that is the program?s internal code used to identify each individual material. The value listed under the B-JAC column is the programs material cost that would used unless a value has been entered in the User column.
For each individual operation performed as part of the fabrication process a labor efficiency factor is included as a denominator in the formula used to calculate the time taken. By default this is set to 0.5. Therefore, by changing this efficiency factor the total time and so cost for that operation can be either increased or decreased.
Keywords: EDR
Cost
Aspen Shell & Tube Exchanger
Costing Calculation
Costing Databases
References: None |
Problem Statement: The customer needs to reuse a large bundle for a smaller service by plugging some of the tubes in the bundle. What is the best way to ensure the simulation results are accurate on both the shell and tubeside after the tubes are plugged? | Solution: 1) Run Hetran & optimize your design.
2) Click on Run - Update Hetran to put design in the rating mode.
3) Go to Input - Exchanger Geometry - Rating/Simulation - and Use existing layout(of course you can start at this point if you started as a rating instead of a design).
4) Go to Input - Exchanger Geometry - Rating/Simulation - Tube Layout tab.
5) Mark the tubes you want to plug. To remove a tube, click on the tube (tube is highlighted in red) and select the red X on the menu. If you want to designate a tube as a plugged tube or as a dummy tube, click on the tube (tube is highlighted in red) and click the plugged tube icon or dummy tube icon on the menu.
6) Re-run Hetran.
Keywords: simulate, plugged, tube, tubes, shell, bundle
References: None |
Problem Statement: What does "connected in parallel/series" means in the top of the TEMA sheet? | Solution: The below pictures explain the designations for series/parallel. The process fluid is shown, but the utility fluid has been omitted for clarity's sake:
Keywords: Heatx, Hetran, Tasc, Tasc+, HTFS, HTFS+, Bjac, B-Jac
References: None |
Problem Statement: When opening the aspenONE Process Explorer site in a supported web browser the default behavior of the home page is to display action links to Process Explorer, Community and Show Everything:
This is not happening.
1. Instead an empty area under the Universal Bar (uBar) is seen. The uBar does not even have the title "Home" written in the area between the search box and Help button:
2. Alternatively, you do actually see the home page action links but when you click on the Process Explorer action link it then takes you to an incomplete page: | Solution: The likely cause of this problem is that the Process Data Rest service is not running. In Internet Information Services (IIS) the Process Data Rest service is controlled by the application pool that is associated with the Process Data virtual applications.
Therefore, run IIS Manager (inetmgr.exe) on the web server and check the status of the relevant application pool, the name of which depends on whether you installed 32-bit of 64-bit Aspen Web Server product:
· 64-bit: AspenProcessDataAppPoolx64
· 32-bit: AspenProcessDataAppPoolx86
Note, assuming that the web server is a member of a Windows domain, this application pool should run under a Windows domain account that has privileges to read the Active Directory.
Note, the symptoms of a stopped or misconfigured Process Data Rest service is slightly different depending on which version of aspenONE Process Explorer is installed. In fact, as well as the symptoms described above, it should be mentioned that up until v8.8 the home page would still display the action links but any further attempt to interact with the web site would result in empty trends, empty tag lists, the menu tree not displaying and any number of other odd things.
Keywords: Clear
Blank
Empty
Space
Error reading file
CheckXML(): Failed to parse
Space required after the Public Identifier
References: None |
Problem Statement: Why does user see different Shell Side Velocity values reporting in TEMA Sheet and Overall Summary? | Solution: Both result sheets actually report different velocity values for shell side condition.
TEMA Sheet ---> Mean Velocity & Maximum Velocity throughout the shell side
Overall Summary ---> Inlet Velocity & Outlet Velocity of Bundle Crossflow of the shell side.
Keywords: Shell & Tube, Shell, Velocity, TEMA, Summary, EDR
References: None |
Problem Statement: How to view material properties (such as thermal conductivity and yield strength) at different temperatures in Aspen Exchanger Design & Rating. | Solution: In order to view the properties of materials at different temperature, follow the below steps;
1. Go to Customize tab in Ribbon Bar and select Material Database and Select a Material Databank like Old ASME.
      Â
2. After selecting database search your material and select the material property which you want to review.
3.A list will come with different temperature points and material property.
Â
Keywords: Material Database, Thermal Conductivity, Yield Strength, Tensile Strength, Material Properties
References: None |
Problem Statement: While trending a tag in aspenONE Process Explorer on a client machine, you may receive an error "IP.21 is inaccessible" in the value column.
The Data Server log files that can be found in "C:\ProgramData\AspenTech\DiagnosticLogs\ProcessData" on the A1PE Web Server report an error "Failed to create IP21DAManager.dll:class does not exist".
This knowledge based solution on how to resolve the error. | Solution: This error usually occurs when both the 32-bit and the 64-bit versions of IP21DAManager.dll exist on the aspenONE Process Explorer web server.
The Aspen Process Data Service uses the 64-bit version of the dll.
To resolve this error try un-registering and re-registering both the DLL’s using the command line.
1. Open a command line window by doing a “Run as Administrator”.
2. The 32 bit DLL is located in C:\Program Files (x86)\AspenTe<h\ProcessData.
To un-register/register, you need to use regsvr32 command in the C:\Windows\SysWOW64
i.e.
> cd C:\Program Files (x86)\AspenTech\ProcessData
> C:\Windows\SysWOW64\regsvr32 /u IP21DAManager.dll
> C:\Windows\SysWOW64\regsvr32 IP21DAManager.dll
3. The 64-bit version of the DLL is located in the C:\Program Files\AspenTech\MES\ProcessData.
To un-register/register, you need to use regsvr32 command in the C:\Windows\System32
i.e.
> cd C:\Program Files\AspenTech\MES\ProcessData
> C:\Windows\System32\regsvr32 /u IP21DAManager.dll
> C:\Windows\System32\regsvr32 IP21DAManager.dll
Keywords: IP21DAManager.dll
A1PE
Trend
References: None |
Problem Statement: You can easily customize your workspace by using the Save to Home icon to add links to files and searches, this is explained in the online help file. Is it possible to further customize the aspenONE home page by, for example, removing the Community action link? | Solution: The default content of the aspenONE home page is controlled by a text file:
\inetpub\wwwroot\AspenTech\ProcessExplorer\WorkspaceDefault.json
Simply modify this file in a text editor to remove or rename core Action Links (such as the Community link) or even add your own action links that can open any other external URL.
You will need to clear the browser cache and then restart the web browser in order to see the changes you made to the home page.
Keywords: a1PE
hide
add
ProcessExplorer
Workspace
aspenONECore
References: None |
Problem Statement: How to setup a heat exchanger model in the new Aspen Exchanger Design and Rating interface. | Solution: The new interface provides an easy way to set up a new EDR model. Home ribbon is set up in such a manner that it reflects the common work flow in building a new EDR model.
1. Provide the Process, Components (Properties) and Geometry
The Model Setup group provides access to key input forms to complete the model setup.
You can follow the Next button to provide the necessary inputs for a particular Run Mode.
You can start with setting process conditions-> then set the stream physical properties-> next define the geometry requirements-> then set any materials of construction and mechanical specifications.
These items are augmented by extensive input specification forms accessible from the navigation pane.
2. Selecting or switching Run Mode
Select/switch task by selecting the appropriate program mode from the Run Mode group from the Home Ribbon. The Run mode is based on the type of heat exchanger under consideration.
3. Selecting Heat Exchanger type to Transfer data to other Heat Exchanger
Select/switch between Heat Exchanger types from the Model Type group from the Home Ribbon. The program allows transfer of key data to the selected heat exchanger.
4. Results
The Results group provides access to program results forms to review key program output.
Keywords: Model Setup, Results, Heat Exchanger Type, Switching Mode
References: None |
Problem Statement: How is the Shell Side MEAN Velocity that is reported in the TEMA sheet is calculated? | Solution: In TEMA Sheet, shell side velocity values are reported in Mean and Maximum values.
The shell side mean velocity value reported in TEMA Sheet is calculated based on the following items:
(1) Shell inlet space velocity,
(2) Shell outlet space velocity
(3) Crossflow velocity of the baffles space near inlet and outlet of the shell.
User can get these values from the Results | Thermal / Hydraulic Summary | Pressure Drop section as shown in the screenshot below. (Circled values)
Shell Side Mean Velocity
= (Inlet Space Xflow + Bundle inlet Xflow + Bundle Outlet Xflow + Outlet Space Xflow)/4
= (11.55 + 14.18 + 23.76 + 19.35)/4
= 17.21 m/s (as shown in TEMA Sheet)
Keywords: Shell and Tube, heat exchanger, EDR, Shell, Velocity, mean, TEMA
References: None |
Problem Statement: aspenONE Process Explorer provides a nice interface to visualize different kind of plots that can actually be used on custom application to fulfill specifics needs. This solution shows a method to used aspenONE Process Explorer main plot view for custom applications using Visual Studio. The example provided on this solution can be easily escalated to more sophisticated customs applications. Basic knowledge on ASP.Net development is needed. | Solution: I. Developing the application
In this example we’re going to build a VB ASP.Net web project using Visual Studio 2015. This simple custom application will display an aspenONE Process Explorer tag trend, plot or graphic based on entries or file name provided at user interface though a dropdown list box, preventing users to interact further with the view to see non-available tags or files.
For this follow next steps:
1. Start a new ASP.Net project on Visual Studio 2015, (optionally name it as MyCustomApp):
2. Select Web Forms as startup project:
3. On the Solution Explorer pane, right click on the main project node and select Add / New Item
4. Add a new web form and name it as (optionally name it as MyCustomPage):
5. Copy the code below and use it to replace the code in the added page source code:
<%@ Page Language="vb" AutoEventWireup="false" CodeBehind="MyCustomPage.aspx.vb" Inherits="MyCustomApp.MyCustomPage" %>
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title></title>
</head>
<body style="background-color:#FFFFFF">
<form id="form1" runat="server">
<table style="border:0px; background-color:#FFFFFF; width:90%">
<tbody>
<tr> <td style="height:10px"></td></tr>
<tr>
<td width="355" align="right" valign="middle" style="font-familyHelvetica, Arial, sans - serif; font-size: 10px; color:#747679; letter-spacing: 1px; font-weight:600; text-transform:uppercase;">My Custom Application</td>
</tr>
<tr> <td style="height:15px"></td></tr>
<tr> <td style="height:3px; background-color:#FFC425"></td></tr>
<tr> <td style="height:15px"></td></tr>
<tr>
<td style="font-familyHelvetica, Arial, sans - serif; color: #0078C9; font-size:16px;">Select a value to show:</td>
</tr>
<tr>
<td><iframe runat="server" id="MyIFrame" style="height: 600px; width: 90%; float: left"></iframe></td>
</tr>
<tr >
<td style="float:left"><asp:DropDownList ID="DropDownList1" runat="server" AutoPostBack="True" onselectedindexchanged="DropDownList1_SelectedIndexChanged"></asp:DropDownList></td>
<td style="float:left"><asp:DropDownList ID="DropDownList2" runat="server" AutoPostBack="True" onselectedindexchanged="DropDownList2_SelectedIndexChanged"></asp:DropDownList></td>
<td style="float:left"><asp:DropDownList ID="DropDownList3" runat="server" AutoPostBack="True" onselectedindexchanged="DropDownList3_SelectedIndexChanged"></asp:DropDownList></td>
</tr>
</tbody>
</table>
</form>
</body>
</html>
6. Copy the code below and use it to replace the code on the code behind of this page (right click and select View Code…)
Public Class MyCustomPage
Inherits System.Web.UI.Page
'Change this for your server name
Private A1PEServerName = "IIP21WebServerV883"
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
'Tags to show on list 1
AddIfNotContained(DropDownList1, "ATCL101")
AddIfNotContained(DropDownList1, "ATCL102")
AddIfNotContained(DropDownList1, "ATCL103")
'Plots to show on list 2
AddIfNotContained(DropDownList2, "Linear1.xml")
AddIfNotContained(DropDownList2, "Frequency.xml")
'Graphics to show on list 3
AddIfNotContained(DropDownList3, "Index.json")
AddIfNotContained(DropDownList3, "Graphic1.json")
AddIfNotContained(DropDownList3, "Graphic2.json")
End Sub
Private Sub AddIfNotContained(aListControl As DropDownList, aValue As String)
If aListControl.Items.FindByText(aValue) Is Nothing Then aListControl.Items.Add(aValue)
End Sub
Public Sub DropDownList1_SelectedIndexChanged(sender As Object, e As EventArgs) Handles DropDownList1.SelectedIndexChanged
Dim MyPath = "http://" & A1PEServerName & "/ProcessExplorer/WebControls/PBPlots.asp?outsidea1=graphic&tag=" & DropDownList1.SelectedValue
MyIFrame.Src = MyPath
End Sub
Public Sub DropDownList2_SelectedIndexChanged(sender As Object, e As EventArgs) Handles DropDownList2.SelectedIndexChanged
Dim MyPath = "http://" & A1PEServerName & "/ProcessExplorer/WebControls/PBPlots.asp?outsidea1=graphic&plotFile=" & DropDownList2.SelectedValue
MyIFrame.Src = MyPath
End Sub
Public Sub DropDownList3_SelectedIndexChanged(sender As Object, e As EventArgs) Handles DropDownList3.SelectedIndexChanged
Dim MyPath = "http://" & A1PEServerName & "/processexplorer/WebControls/PBGraphics.asp?outsidea1=graphic&File=Public/" & DropDownList3.SelectedValue
MyIFrame.Src = MyPath
End Sub
End Class
7. Do the proper changes on the previous code to make it work with your tags, plots and graphics saved on your aspenONE Process Explorer:
a) User your aspenONE Process Explorer server name or ip address for the variable A1PEServerName.
b) Add some of your tags on the list 1, plots saved as .xml on your public folder for the list 2 and graphics saved as .json files also located on your public folder.
8. Click on Play green button to test the application. It should display your tag list, plots list and graphics list as part at the bottom. Changing any element should present this on the Iframe control:
II. Explaining the code
The previous example shows how to use the PBGraphics.asp page as part of a custom application. This page can be used to display most of the content displayed on aspenONE Process Explorer by changing the input parameters used on web GET call using the next base link:
Error! Hyperlink reference not valid.?
The previous application example simple build a path programmatically using UI parameters that the PBGraphics.asp can use to display different content.
Extended interaction with IP.21 database or other application can also be done by using specific APIs.
The parameters explanation is described on the next section.
II.1Tag parameter
Using this parameter it is possible request to the PBGraphic.asp page to show a tag or a list of tags. Use this parameter as follow:
tag=<single tag name>
Example: http://LocalHost/ProcessExplorer/WebControls/PBPlots.asp?tag=atcai
or
tag=<tag1 name>,<tag2 name>, … <tagN name>
Example: http://LocalHost/ProcessExplorer/WebControls/PBPlots.asp?tag=atcl101,atcl102,atcl102
for a list of tags.
II.2 PlotFile parameter
Using this parameter it is possible request to the PBGraphic.asp page to show any plot saved on any reachable location under the C:\inetpub\wwwroot\AspenTech\ProcessExplorer\Files folder. The previous example application shows the Public folder hardcoded but this can be any different location inside the Files folder. Use this parameter as follow:
plotFile=<path to the xml plot including extension>
Example: http://LocalHost/ProcessExplorer/WebControls/PBPlots.asp?plotFile=Public/Linear1.xml
Notice from image on instruction point 7 the location of the Linear1.xml file on this example.
II.3 File parameter
Using this parameter it is possible request to the PBGraphic.asp page to show any graphic that has been already published on aspenONE Process Explorer saved as a .json file. The previous example application shows the Public folder hardcoded but this can be any different location inside the Files folder. Use this parameter as follow:
File=<path to the xml plot including extension>
Example: http://LocalHost/processexplorer/WebControls/PBGraphics.asp? File=Public/Graphic1.json
Notice from image on instruction point 7 the location of the Graphic1.json file on this example.
II.4 Outsidea1 parameter
This parameters define which elements are displayed as part of the PBPlots.asp view, notice from the image on instruction point 8 that the frequency plot displayed does not shows any method to add new tags, comments, save changes, etc. this parameter need be used among with previous parameters by concatenating them using “&” character. Use this parameter as follow:
Outsidea1=<one of the next options: >
Graphic
Dashboard
TabGroup
Example of Graphic option:
http://10.36.48.182/ProcessExplorer/WebControls/PBPlots.asp?tag=atcai&outsidea1=graphic
-No search box.
-No application bar (Forward, Back, Tree View, Add new, Actions, Setting and Save button are not displayed).
-Replay menu is available.
-Tag floating menu is available.
-Timeline control is available.
-Excel export and Columns Hide/Show options are available.
Example of Dashboard option:
http://10.36.48.182/ProcessExplorer/WebControls/PBPlots.asp?tag=atcai&outsidea1=Dashboard
-No search box.
-No application bar (Forward, Back, Tree View, Add new, Actions, Setting and Save button are not displayed).
-No replay menu.
-No Tag floating menu.
-No Timeline control.
-No Excel export and Columns Hide/Show options.
Example of TabGroup option:
http://10.36.48.182/ProcessExplorer/WebControls/PBPlots.asp?tag=atcai&outsidea1=TabGroup
-Search box is available (it is possible to add new tags).
-No application bar (Forward, Back, Tree View, Add new, Actions, Setting and Save button are not displayed).
-Replay menu is available.
- Tag floating menu is available.
-Timeline control is available.
-Excel export and Columns Hide/Show options are available.
-Zoom menu is available.
-Plot settings menu is available.
-Comments menu is available.
To show the complete interface you can simple not use this parameter:
Keywords: aspenONE Process Explorer
ASP.Net
Custom applications
References: None |
Problem Statement: What are the criteria for maldistribution in Aspen Plate Fin Exchanger? | Solution: The distributors at the inlet and outlet of each layer consist of one or two pads of finning. At least one of which is at an angle to the main flow direction in order to direct the flow in the main fin to or from a stream header.
Each distributor pad has a defined fin type and flow direction, so the mass flux (perpendicular to the flow direction) is well defined. This means that pressure gradients and heat transfer coefficients can readily be calculated for each pad. Since the pads are (usually) triangular, they have two extreme flow lengths, one along one side of the triangle, the other (at the vertex) being zero. The mean pressure change in each pad is calculated using a mean flow length, where the pressure changes along the extreme (left and right) paths are used in determining the risk of flow maldistribution.
The pressure changes are given from Results | Thermal / Hydraulic Summary | Pressure Changes | Main Distribution tab.
It provides information on the main fin pressure drop and then gives the total left and right hand pressure drop. Distributor structure means that there is inevitably a difference between left and right hand paths of an individual distributor, but some effort is normally made to have the inlet and outlet distributors compensating each other, so the total left and right hand path frictional losses are as close as possible.
The maldistribution risk is based on the difference between the left/right hand pressure changes and the mean pressure change. If the “Total friction (LH) excluding nozzles” or the “Total friction (RH) excluding nozzles” is larger than 110% of the “Total friction (mean) excluding nozzles” then a maldistribution risk is reported for the stream.
Note: The calculation simply points to a risk of side-to-side maldistribution, but does not evaluate its effect.
Keywords: maldistribution, risk, distributor, pressure change
References: None |
Problem Statement: There are various application types of column and drum as follows:
What will change by the selection?
How does changing the selection affect the Equipment Design/Cost? | Solution: These are different configurations for the component and will change the volumetric model (Piping and Instrumentation) scope. So for the different application options you will see piping and instrumentation cost differences.
A visual depiction of the different application options is available in the P&ID
Keywords: Column, Drum, Application type, P&ID
References: Guide.
Different configurations may result in different nozzle schedules, so equipment pricing may change because of nozzle differences. |
Problem Statement: Does Office 365 work with Aspen Capital Cost Estimator V8.8.2? | Solution: Aspen Capital Cost Estimator (ACCE) V8.8.2 runs with Office 365 desktop deployment only. It does not work when installed with the "Click to Run" deployment.
Keywords: Office 365, "Click to Run"
References: None |
Problem Statement: How to update the targets when we are using production targets function in PIMS? | Solution: Open production targets from the tool bar.
Select your targets and send to Targets pane shown like below, we can see the capacity for VT2 in case 11 is 25 now.
Close the window and go back to case table, change the capacity of VT2 from 25 to 30 then run the model again. Go back to the production target window. We will find in the target selection pane the activity of VT2 is changing to 30, but in the target pane the remains to 25.
This is because the data selected to be pushed to APS is tied to a particular solution/execution/run. If you are pushing data from several solutions/executions/runs, then that will be done in different sessions. Basically, you will not see VT2 get updated automatically in the Targets tab. To achieve the update function, you need to delete old VT2 target from the Targets pane first. Then select the new VT2 and move it into the Targets pane as shown below:
Keywords: Production Targets
Targets update
Integration in PIMS
References: None |
Problem Statement: After clicking on the "Show Everything" action link on the home page or clicking on the magnifying glass button on the Universal Bar (uBar) within aspenONE Process Explorer (a1PE), the Search page does not display as expected. Instead you see the following message:
Access service error !
1. Text Status: undefined
2. Error Thrown: undefined
You note that the type ahead search on the other pages within a1PE are working fine, the problem is only on the Search page. | Solution: 1. This suggestion can also be found in Knowledge Base article 142321-2 but surely represents the number one cause of this problem and is worth repeating: In Internet Information Services (IIS) Manager on the a1PE server you should check the Authentication on the aspenONE application and make sure you have Anonymous Authentication enabled. For example, the symptoms described above will be seen if you only have Windows Authentication enabled. After correcting the Authentication setting you may well see expected results delivered immediately on clicking the magnifying glass button next to "Search for Everything" - no iisreset or log out of a1PE etc is required.
2. The results on the Search page are delivered by the aspenONE Search Service. This service uses the search index scanned using Apache Tomcat Solr application and the error that is displayed is likely to be caused by misconfigured Solr parameters.
You need to open the aspenONE Search configuration file using a text editor. The default location of this file is:
c:\inetpub\wwwroot\AspenTech\aspenONE\App_Data\config.xml
By default, the SolrServerURL parameter is http://localhost:8080. Test this on the a1PE server itself by pasting the URL specified in the SolrServerURL parameter into a web browser with the /solr application name as a suffix,
eg. http://localhost:8080/solr
If this does not produce a username/password dialog (and assuming Tomcat Windows service is running and is correctly configured on a particular port - see Knowledge Base article 144666-2) then the port number in the config.xml is likely to be wrong and you should correct it.
The other parameters in the config.xml file are SolrUserName and SolrPassword. These are encrypted and you should edit the Tomcat Basic Authentication for Search Security in aspenONE Credentials utility to set them - see Knowledge Base article 141989-2.
After making changes to configuration files used by IIS, you should run iisreset.exe on the a1PE server.
Keywords: Spinner
Wait forever
Blank page
Search for Everything
References: None |
Problem Statement: All values to be saved on Aspen InfoPlus.21 database need to use a proper record definition as well as a proper format (in most cases) so that the information provided by them can be properly interpreted. Aspen InfoPlus.21 provides a set of records definitions and format that can cover almost all kind of needs. This solutions provides information on what definition record and format you can use based on the canonical type of the data to be saved. | Solution: There are three main kind of records definitions to saved values that are provided on Aspen InfoPlus.21 out-of-the-box:
IP_AnalogDef
IP_DiscreteDef
IP_TextDef
Usage of these records definitions is explained as follow:
Usage of IP_AnalogDef records
IP_AnalogDef records will work properly for next canonical types of data:
Canonical type
Description
R4
4 bytes real
R8
8 bytes real
The format selection (Fx.d or ExEx) depends on the best way to represent the value:
· Use Fx.d format to represent a value as an extended number with decimal points, for example: 10.1, 10.001, -25.00, etc. In Fx.d, x represent the total number of digits including the point and +/- characters while d represents the number of rounded decimal points. To select a proper format follow this:
1) Define how many decimal points (d) do you want to display.
2) Define how many characters does the value is going to have to the left of decimal points (x’) and add 2 + d. So that x = x’ + (2 + d).
Example: To represent a tag having value between 100 and 2000 having 3 decimal points characters precision.
d = 3
x’ = 4 (maximum number of characters in upper limit 2000)
x = 4 + (2 + 3) = 9
Ideal format: F9.3
· Use ExEx to represent the value as scientific notation, for example: 4.57E+005, 4.010E-99, etc. In Ex1Ex2, x1 represent the number of numeric digits to the left of the E exponent, which are expressed as c.n where c is always a single digit and n is the number of digits to the right of the point minus 1 (n = x1-1); while x1 represent the number of digits if the exponent. To select a proper format follow this:
1) Define how many digits do you want to use on the exponent (x2).
2) Define how many digits do you want to use to the right of the base number (n) and add 1, x1 = n + 1
Example: To represent a value on scientific notating like 1.2455E24
x2 = 2
n = 4
x1 = 4 + 1 = 5
Ideal format: E5E2
Usage of IP_DiscreteDef records
IP_AnalogDef records will work properly for next canonical types of data:
Canonical type
Description
I1
1 byte signed character
I2
2 bytes signed integer
I4
4 bytes signed integer
I8
8 bytes signed integer
UI1
1 byte unsigned character
UI2
2 bytes unsigned integer
UI4
4 bytes unsigned integer
UI8
8 bytes unsigned integer
Bool
Boolean
Enum
Enumerators
Format selection for IP_discreteDef depends of the type to values to display.
· To display numeric integer values you use any Ix format, where x is the lengh of the number to display, for example, a tag having values betwee 100 and 999 you can use I3 format.
· To display the value as string from a enumerator (for example as TRUE/FALSE, ON/OFF, DUE/PENDING/DONE, etc.) you must select the format as the name of a selector record holding the string representation you need. Selector records are defined by different SelectxDef where x is the number of characters that can hold in each option. Solution 143233 shows how you can create this records if they’re not provided as part of Aspen InfoPlus.21 out-of-the-box x records. When using a selector as a format, Aspen InfoPlus.21 does not save the values a string; its saved the value as the number representation of the enumerator, for example, if a Selector defines TRUE as 0 and FALSE as 1, Aspen InfoPlus.21 saves the value as 0 or 1 not as TRUE or FALSE, so that, it is actually possible to change the format (specifying another selector record) without affecting the value saved on history.
Usage of IP_TextDef records
IP_TextDef records will work properly for next canonical types of data:
Canonical type
Description
BSTR
Byte length prefixed Unicode characters
CHAR*, WCHAR*
Null-terminated characters
No format is required to use this definition, these records can hold up to 600 ASCII characters.
Other formats
Aspen InfoPlus.21 also provides additional format needed for data types not mentioned before, the next table summarize them;
Format
Example
Representation
Zx
A10F
Signed Hex values
UZx
- A10F
Unsigned Hex values
DTx
12345:30:00.0
Delta time
DSx
1:30:00
Delta time (seconds)
DMx
1:30
Delta time (minutes)
Tsx
01-APR-16 12:30:00
Timestamp
Keywords: Definition Records
Format
IP_AnalogDef
IP_DiscreteDef
IP_TextDef
References: None |
Problem Statement: aspenONE SLM License Manager V8.8 or V9.0 (Client side application) cannot load server info from Sentinel Server 9.6.0. The error message below shows:
“Could not communicate with the server. Make sure that the server is running and accessible form this machine.”
This is caused by Internet Control Message Protocol (ICMP) network traffic being turned off (This is now a default behavior on Windows Server 2012, Windows Server 2016, Windows Server 2019 and Windows 10)
This can be checked by opening a Command Prompt window on the Client machine and ping the server. (see below). | Solution: This is happening because the SLM License Manager included in V8.8 and V9.0 return an error message if the machine cannot be reached by ping.
There are two workarounds:
Install a later version of SLM License Manager (V10.0 or later)
Unblock the required ports on the license server. (See the Microsoft KB articles below)
For Windows Server 2012 R2 and Windows Server 2012
For Windows 10, Windows Server 2016 and Windows Server 2016
Later versions of SLM License Manager do not fail if the machine cannot be reached by ping.
Fixed in Version
V10.0 and later versions.
Keywords: SLM
Sentinel RMS License Manager
References: None |
Problem Statement: How can I report volumetric HHV and/or LHV in different units? | Solution: Units to report volumetric HHV and LHV are limited, only a few options are available. However, using the Spreadsheet block within HYSYS, it is possible to take a calculated value and convert it to a specific set of units.
In the attached example, HHV is calculated and reported in MMBtu/gal, and by using a Spreadsheet, converted to MMBtu/ft3.
Keywords: Volumetric, HHV, LHV, units, spreadsheet
References: None |
Problem Statement: How to upload Bulk loading of Strap Table data in Advisor? | Solution: Aspen Operations Accounting(AORA/Advisor) does not have any Built-in Function to upload Bulk loading of Strap Table data. The only option is, to use SQL Server Management Studio that is the feature of Import / Export Data option.
The below procedure may be followed for bulk uploading of data in to Strapping tables of Advisor Model.
Brief Over view of steps:
1. Create a New Strap Table in Advisor and make a note on DBINDEX
2. Prepare the Tank calibration chart in excel sheet with required format.
3. Convert Excel sheet in to MS Access format.
4. Check the MS Access file before import.
5. Export MS Access format in to Advisor Model via SQL DTS
6. Validate the Imported values in SQL Server
7. Check the New Strap Table in Advisor Model
1.1 Creating a new strap table in Advisor :
a). Create a New strap Table in Advisor through Configure à Global à Strap Tables
Enter the name of the new strap table
b). Check the DBINDXEX of the table created through Advanced Tab
1.2 Create a Excel sheet with Tank calibration data in required format.
Once the Strap table is created in Advisor GUI, then prepare the calibration data
in excel asper the following format:
Column ‘A’ – IND2STRAP conatins the DBINDEX of the newly created Strap
table in Advisor Model. It is same for all the rows, for a specific tank.
Column ‘B’ STRAP_COOR contains the Calibration chart height
Column ‘C’ STRAP_VOLM conatins the Correponding Volume for the tank
height.
General Instructions for Excel format of Tank calibration chart:
1. Excel sheet must conatins only values, not any formual or cell
reference. If any formual / cell references are there, then replace with
values.
2. Delete any unused Columns and Rows in the excel sheet, than the
actaul data column / row being used.
1.3 Convert the Excel sheet in to MS Access format
a. Create a new MS Access Database and import the Excel data in to Access tables.
b. Open the MS Access file. Go to File> Get External Data > Import
c. Select the Excel file contains Strap table data.
d. MS Access Import Spreadsheet wizard will appear.
e. Check the Column format and then Click ‘Next’ and finish at the
end
f. Select “No Primary Key” option, so that no additional fields are
added.
1.4 Check the MS Access file before import
a. Atfer successful import of the Excel data in to Access file, open
the Access file and check the data.
b. Verify the number of Rows and Columns converted into Access
format.
c. Delete if any unused rows.
2.0 Export the data in to Advisor Model – SQL Server:
a. Open MS SQL Server management Studio and Connect to Advisor
Database ‘AdvisorDEV’.
b. Important: Take a back up of current database, before changes.
c. Right Click in AdvisorDEV Database and Select Tasks Import data.
d. Select Source as MS Access file and Destination as Advisor Model on
the SQL Server.
Destination Selection:
Click Next and Finish then review the results for successful import.
Execute SQL Query to check the data imported.
Open Advisor Model, Refresh and check the new strap table data.
Remarks:
Follow the same procedure if multiple tanks needs update
Keywords: None
References: None |
Problem Statement: How do I read Aspen HYSYS cases created in a later version when I am running Aspen HYSYS of a lower version? It complains that “Files created in a newer version of HYSYS cannot be opened in an older version of HYSYS”. | Solution: You may use XML technology for the backward compatibility, 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.
First save the case in XML format:
Within Aspen HYSYS later version, go to File --> Save as
In the Save as type, choose “HYSYS XML Cases (*.xml)”
Give a name and save the case.
Please note that if you have Petroleum Assays defined in the simulation, you cannot save it in the XML file. You have to detach Petroleum Assays from all of the streams and then delete the Petroleum Assays under Properties.
To open an XML file in Aspen HYSYS:
In any Aspen HYSYS version (including versions earlier than the one you saved the Aspen HYSYS cases), click "Open"
Change the File Filter to "HYSYS XML cases" (*.xml)
Browse to the saved .XML cases to open the case.
The case should re-open, and by default Aspen HYSYS solver is placed on Hold mode. You can go ahead and put the Solver to Active.
Please note that:
The case may or may not be fully solved due to the differences between the HYSYS versions.
You will expect that if your models use any of the new features only added in the later version of HYSYS, these features in the model will not turn up in the lower version of HYSYS when you import the model.
Extensions (e.g. unit operations extensions) in models do not always work when saved in XML format. In these cases, you need to delete those extensions for a successful XML export.
After having exported your case to an XML file, take some time to check for the following:
Ensure the component list is the same. Make sure all the hypotheticals are included in the component list.
Check to make sure the column specs are the same. The bottom up numbering is particularly bad, so are side operations.
Check connections on unit operations that have multiple inputs and outputs, especially with columns and heat exchangers.
Keywords: Forward compatibility
XML
Newer version
References: None |
Problem Statement: Do you have any suggestions for setting up my HYSYS views while running in dynamic mode? | Solution: The attached document entitled "Formatting HYSYS for Easy Operation in Dynamic Mode" gives a number of suggestions on how to set up strip charts, PFDs and your HYSYS screen.
Keywords: Dynamics; Strip Charts
References: None |
Problem Statement: This Knowledge Base article provides steps to resolve the following error:
“You do not have the necessary components installed (Base API) for testing. Contact your system administrator if you believe you should have access to this functionality."
.. which may be encountered when one clicks on the "Test" option in the Test Configuration Properties dialog in Aspen Batch and Event Extractor (the Extractor). | Solution: Note: This solution is only applicable to Aspen Extractor versions 9.x.
The issue occurs on the 64-bit version of the Extractor and is caused by missing dlls.
The Configuration Test tool requires 32-bit dlls, which were not shipped with the 64-bit version of the Extractor.
Attached to this KB article is a zip file containing the missing Extractor 32-bit dlls. Please do the following:
• Download the attached Extractor_V9_32-bit_files.zip file to your computer
• Unblock the zip file before unzipping (Right click | Properties | clear the block flag on the zip file and click OK to save your changes)
• Copy the dlls to the Extractor directory (C:\Program Files (x86)\AspenTech\Batch.21\) and register them. Make sure you are copying the correct files to their corresponding directories. There are two folders in the zip file – copy the files from the Server folder to the Server folder in the C:\Program Files (x86)\AspenTech\Batch.21\ directory and copy the files from the Client folder to the Client folder in the C:\Program Files (x86)\AspenTech\Batch.21\ directory.
Keywords: audit
compliance
record
References: None |
Problem Statement: When I leave the Basis environment after making a change, HYSYS asks if I want to be left in HOLD mode. What should I choose? | Solution: The reason HYSYS will prompt you to be left in holding mode is that it has been detected that you have made changes in Properties Environment (Basis environment). In some instances, this will impact the thermodynamic behaviour of your system, and therefore pieces of information which you have specified in your case may require re-evaluation.
For instance, consider the case where you are simulating a Crude Distillation Unit. Supppose you have converged a column using product flow rates as specifications, and then you return to the Basis Environment and install a different oil in the flowsheet. When you return to the simulation environment, you may wish to update the column specifications to account for the change in system behaviour as a result of the new oil which you are using before you attempt to re-solve the flowsheet.
Keywords: basis environment, return, simulation environment, holding, hold mode
References: None |
Problem Statement: How do I backup and restore a workspace? | Solution: To backup a workspace.
1. Open AZ191Backup.exe (for V10). Default location is: C:\Program Files\AspenTech\Basic Engineering V10.0\DataServices\x64bin
2. Select Backup Workspace option and click Next.
3. Select the workspace to backup from dropdown list and click Next.
4. Select the location where you want to save a backup of this workspace and click Next.
5. Click Backup and exit once it's finished.
To restore a workspace.
1. Create a new blank workspace with appropriate Library Set.
2. Open AZ191Backup.exe (for V10).
3. Select Restore Workspace option and click Next.
4. Select the folder of the new workspace to restore to. Make sure you double click on workspace name folder.
5. Click Next and Select backup file location.
6. Click on Restore option.
Keywords: Backup, workspace backup
References: None |
Problem Statement: What is Aspen Fleet Optimizer Order Manager Web? | Solution: Credit Management allows credit representatives to review and modify customers’ credit status. This also includes the ability to change, cancel, and hold customer orders. Credit Management uses the Web to allow real-time updates. Credit Management and core Aspen Fleet Optimizer applications run from a single production database. This allows direct access to critical supply chain data. This also eliminates time lags and data errors making easier information sharing within the supply chain. There is also the ability to change, delete, view, and print orders along with direct access to review and suspend customer credit.
Keywords: None
References: None |
Problem Statement: How to submit an upgrade request. | Solution: 1.Go to https://esupport.aspentech.com/
2.Login to your Support Center account
3. Select Support menu in the top bar
4.Click on Order Upgrades under the Software Services section
5.Complete the form and Submit
A case will be created and a Customer Care Specialist will review your request
FAQ’s
WHAT INFORMATION DO I NEED TO UPGRADE THE SOFTWARE?
Please include the System Name you would like to upgrade.
How to obtain my System Name
WHAT SHOULD I DO IF I DON’T KNOW MY SYSTEM NAME?
Please enter “need help” in that field and submit your request. We will contact you to help you to locate the necessary information.
WILL I GET AN UPDATED LICENSE FILE?
Depending on the version you currently have, an updated license file may or may not be required. If an updated license file is needed, it will be processed together with the upgrade.
IS THERE ANY OTHER INFORMATION THAT I NEED TO INCLUDE?
If you are requesting to download a version other than the latest released version, please specify the version you would like to download.
Keywords: None
References: None |
Problem Statement: Do you have any tips on troubleshooting column convergence? | Solution: Attached you will find a document which can be useful for practical troubleshooting of column convergence. This document provides tips for troubleshooting the I/O solver and was originally created for use with Hysim, but the content extends to the HYSYS column.
Keywords: Column, Troubleshooting, Convergence
References: None |
Problem Statement: DMC3 builder allows to use Pseudoramp variables as it used to be in DMCplus builder. However, the way these variables can be declarer change from the legacy version. | Solution: 1.- From the Controller tab, select the Cases folder under master model. Then select All Variables.
2.-On the Variables View Select the CV that is going to be set as a Pseudoramp. Then click Edit and the Variable Type window will pop-up. In this Window select stability as Ramp. This will allow us further to select this same variable as a Pseudoramp.
3.- Then go to the Optimization Tab on the DMC3 three. Then select Configure Optimizer from the top ribbon. This will show all the variables optimization configuration and will noticed that on the CV side is now available a column with the Pseudoramp header. It will be noticed that this option is locked in grey except for the varibales that were previously declare as Ramp.
4.- Finally check the box for the variables that will be set as a pseudoramp.
Keywords: DMC3, Pseudoramp, CV
References: None |
Problem Statement: When opening the printed documentation and clicking on the help links for other documents, nothing happens and unable to access the help documentations. For example: Aspen Economic Evaluation V12 Printed Documentation.
This is occurring because the PDF documentation is opening in a Browser PDF Reader. If you are using a Web Browser as the default pdf display application, these links will not work. The links are intended to only work when using the desktop Adobe Reader application. | Solution: Set the default application, for opening PDF files, to the Adobe PDF reader desktop application.
Keywords: Printed Documentation
Aspen Capital Cost Estimator
PDF
Help Documentation
User Guide
References: None |
Problem Statement: What are the key concepts and main troubleshooting tips and best practices when using Aspen HYSYS Dynamics? | Solution: A. Steady State Backup File.
Always save a copy of the steady state simulation file you will use to depart from steady state to dynamic mode, so whether something goes wrong or if any change(s) need(s) to be made in steady state, you can start off again from the same steady state file. Going back from dynamic mode to steady state most of the times will not lead to a solution, but to convergence issues..
B. Dynamic Solver.
1) The dynamic solver in Aspen HYSYS is not the same as the steady state solver.
2) The dynamic solver considers the flowsheet as a boundary value problem.
3) If either pressure or flow specs are made on all the boundary streams (i.e. feed(s) and product(s)), then the Pressure/Flow (P/F) solver will be able to solve all internal pressures and flows simultaneously. Dynamic calculations are not sequential as in steady state.
4) Three key concepts:
4.1) Pressure/Flow specs (only one, either pressure or flow) for boundary streams.
4.2) Resistance / Conductance operations (equations that calculate pressure drop, such as valves).
4.3) Pressure node operations (calculate a pressure, such as vessels).
5) All unit operations must be properly sized prior to moving from steady state to dynamic mode on either the 'Rating' or 'Dynamics' tab of each unit.
C. Fluid Package.
1) Aspen HYSYS Dynamics uses the same physical property calculation routines as Aspen HYSYS. Make sure that the selected Fluid Package is the best option.
2) In case of convergence difficulties or noise, try other combinations:
2.1) Activate the ‘Try IOFlash’ option.
2.2) Change to ‘Multi Phase’ method if there are 2 liquid phases.
3) Remove those components that are not required for the dynamic simulation, it is, those components for which composition is negligible or zero. The calculation of the properties of these components (with compositions equal to zero) can lead to convergence problems. An additional benefit is that the simulation size will decrease, hence it will run faster.
D. Troubleshooting Tips.
1) Always analyze the problem with Process Engineering judgement. It may be useful to study a large flowsheet in smaller sections.
2) Use spreadsheets and strip charts to track the behavior of process variables with respect to time.
3) Check the control system and its tuning parameters.
4) Use the ‘Event Scheduler’ to repeat actions in a consistent way, rather than manually changing the control system performance.
5) Use ‘snapshots’ to store your starting points and/or save a moment during the dynamic run if you need to go back to such moment again.
6) Pay attention to the control system if it is not operating properly.
6.1) Add controllers where required.
6.2) Double check controller settings, especially the controller action mode.
6.3) Suspect of saturated controllers.
6.4) Suspect of controllers with high gain, but short integral time.
7) The following are values that have been proved to work fine as tuning parameters for controllers. However, users are encouraged to make use of accurate information (provided by vendors) to rigorously model the performance of the control system.
8) You can only change the value of fixed variables (pressure/flow specs).
E. Best Practices.
1) Do not run your model in dynamic mode without a control system and proper tuning parameters.
2) A vapor phase will be needed in separators. Consider if you will need to add inert components to pressurize the vessel.
3) Do not connect two pressure nodes directly (e.g. separators). Use a resistance/conductance operation in between (e.g. valves).
4) Think about the suggestions made by the ‘Dynamics Assistant’. You do not have to necessarily make all the listed changes.
5) If static head contributions are considered, you will need to check the nozzles locations in all blocks.
Keywords: Dynamics, Best Practices, Troubleshooting, Tips.
References: None |
Problem Statement: What can I do to avoid inaccuracies in the flare network solution when using rated flow for tailpipes? | Solution: We understand that API has guidance on sizing tailpipes based on rated flow, but this should not be done at all in the flare network if rated flow and mass (design) flow are very different. Only if there is a small difference between mass (design) flow and rated flow, then rated flow for tailpipes can be used to get sensible results.
Now, if the ‘Use rated flow for tailpipes’ option is used in cases in which rated flow is, for example, 50-100 times higher than the required flow (mass (design) flow), then results will be totally non-physical. We do not believe that the flare network solution can be accurate if the rated flow is not close enough to required flow within a couple of % points.
In Aspen Flare System Analyzer (AFSA), when rated flow is used for tailpipes, then rated flow is used for the pressure drop calculation for tailpipes, but mass (design) flow is still used in the energy balance equation.
The ‘Use rated flow for tailpipe’ feature is there in AFSA for historical reasons and because of API’s guidance on sizing tailpipes based on rated flow, so its use is up to the user's Engineering judgement, as well as results analysis and interpretation.
To learn more about Rated Flow and Mach number ins Aspen Flare System Analyzer, please consult the following Articles:
000031922 - 'What does the ''Rated Flow for Tailpipes'' option mean?'.
000045646 - 'Is the calculated Mach number based on mass (design) flow or rated flow?'.
Keywords: Rated Flow, Mass Flow, Design Flow, Tailpipes, Difference, Flare Network, Pressure Drop.
References: None |
Problem Statement: License log files are created in the APC online and AspenWatch servers to detail the licensing procedure of various APC processes. | Solution: For an APC online server, the licensing log can be found at C:\ProgramData\AspenTech\APC\Online\sys\etc/APCOnlinelicensing.log for DMCplus, DMC3 controllers running under ACO-based platform. IQ applications licensing log can also be found in the same file.
For RTE applications, the licensing log is found at C:\ProgramData\AspenTech\RTE\V10\Clouds\Online\sys/APCOnlinelicensing.log
For an AspenWatch server, the licensing log can be found at C:\ProgramData\AspenTech\APC\Performance Monitor\etc\cfg/APCOnlinelicensing.log. For v8.7 and later, AspenWatch data pump is the process that checks out the AspenWatch license key (SLM_APC_AW) unless the controller is a DMC3 controller. In that case, the APC application is checking out a SLM_RN_APC_DMC3 key on the APC online server.
There is no license required to run a Production Control Web Sever (PCWS).
Keywords: SLM_APC_AW
licensing log
References: None |
Problem Statement: What's the difference between HC Dew Point and Water Dew point? | Solution: The dew point is the temperature at a given pressure at which the first drop of liquid starts to form. Hydrocarbon and water dew points indicate the type of liquid formed.
In HYSYS, the dew point is calculated by using a flash to calculate the temperature at which the vapour fraction is equal to one. When the vapour fraction is equal to one, the vapour is said to be saturated or at steam pressure. If the case does not contain water, the temperature at which the vapour fraction equal to one is reported as the hydrocarbon dew point (HC Dew Point). If the case has water as one of the components, the type of liquid phase formed is reported with its corresponding Water dew point temperature. Then the temperature is decreased until a second liquid phase forms, the temperature at which this occurs is reported as the HC dew point
For example in the stream 1
As it has water inside, the dew point in which the vapor fraction is one, is the Water Dew Point, then the temperature at which the second liquid phase forms is the HC Dew Point.
" Water Dew Point
Vf=1, P=14.7 psia, only one liquid present
" HC Dew Point
P=14.7 psia and T=-80.56 F, the second liquid appears
So, if water is not present on your component list (Stream 2 in the example case), please use the HC Dew Point, the Water Dew Point will be showed as <empty>.
Keywords: HC Dew point, Water Dew Point
References: None |
Problem Statement: How to setup reciprocating pump or positive displacement pump in Aspen HYSYS? | Solution: A positive displacement pump can be modeled using a pump [with or without characteristic curve], valve and transfer function. In reality, the flow and pressure of a positive displacement pump trend as a pulse. Please refer to attached case file where a 2nd order sine wave transfer function disturbance is selected to simulate such scenario.
Keywords: positive displacement pump, reciprocating pump, pump
References: None |
Problem Statement: Why does Aspen HYSYS ignore bulk olefin only content in petroleum assay input? | Solution: In V9, Aspen HYSYS cannot estimate olefin distribution curve from bulk olefin only. You need to enter olefin for at least three constituent cuts.
Then after characterization, you can see olefin content is populated:
But there are additional known issues in V9:
- Olefins are not part of PNA balance. that is, PNA is summed up to 100%, not PONA.
A workaround is to specify PONA input such that they add up to 100%.
Keywords: Olefin input, Petroleum Assay, PNA
References: None |
Problem Statement: How do I add and then view/modify Heat Stable Salts in an amine-based Acid Gas Cleaning process? | Solution: After selecting “Acid Gas – Chemical Solvents” as the Property Package, return to the Component List and click the “Add Heat Stable Salts” button
A series of reactions will be generated in the Reactions folder
Return to the Simulation Environment and open the Lean Amine Stream
Go to the Composition form and then click the “Edit” button
Click the “HSS Composition Wizard” button
A form will appear displaying salt compositions. These compositions can be modified and the effect on the outlet sweet gas H2S composition may be observed.
Key Words
Heat Stable Salts, HSS, acid gas cleaning, amine
Keywords: None
References: None |
Problem Statement: This Knowledge Base article provides troubleshooting steps to resolve problems with HPT Search results in V8.0. | Solution: HPT Search General Troubleshooting Tips
HPT Search contains the following modules: Search Engine (SOLR in Tomcat), Tag Publishing (DispatchService in IIS), and Search Query.
To troubleshoot problems with HPT Search, please follow the steps below:
1. Make sure TOMCAT7 service is running. If it can’t be started, please check log files and address the problems properly.
2. Make sure Solr Application is running. To check this go to Tomcat manager on the Web server: http:http://hostname:8080, the default userid: password is admin/admin. At the bottom of the list, the SOLR should be there and running. If it is not running, try restarting Tomcat which should fix this problem.
3. Make sure the DispatchService is running properly and tags can be published.
a. Open the C:\inetpub\wwwroot\AspenTech\DispatchService\Metadata\web.config, look for the following sections and make sure the server names are correct and the search port is the same as the tomcat port.
<add key="LocalMetaDataService" value="W2K8XHV.dev.aspentech.com/Web21/ProcessData/AtProcessDataRest.dll"/>
<add key="LocalSearchServer" value="W2K8XHV.dev.aspentech.com"/>
<add key="LocalSearchPort" value="8080"/>
b. Open C:\inetpub\wwwroot\AspenTech\Web21\ProcessData\ AtProcessDataREST.config, look for the section:
<TriggerURL>http:http://localhost/DispatchService/Metadata/Dispatch.svc/ScanLocalDatasources</TriggerURL>
Run the above-mentioned url in a browser to republish tags and see if the result is correct. A log file can also be found at
c:\inetpub\wwwroot\aspentech\dispatchservice\metadata\log
If error occurs, please address it properly.
4. Check search configuration, the port number used by the Search Engine should be the same as the Tomcat port number.
Open file
C:\inetpub\wwwroot\AspenTech\Web21\WebControls \AtWebPlotsConfig.xml
and check that search solr string is pointing to the correct server and port number, example:
<Solr>
<!-- the SOLR engine server with port -->
<Server>http://localhost:8080</Server>
<!-- the maximum rows to return from SOLR engine, but this can be override in code -->
<RowsRetrieve>10</RowsRetrieve>
</Solr>
Note, the Dispatch Service was removed in v9.0 of Aspen Web Server.
Keywords:
References: None |
Problem Statement: Aspen SQLplus Query Writer 에서 InfoPlus.21 history 내용을 읽을때 아래와 같은 오류 발생 | Solution: 본 오류는 읽는 fileset 의 복구가 필요하기 때문입니다.
1. CMD 프롬프트 실행
2. 아래와 같은 명령어로 경로 변경
V7.1보다 낡은 버전,
cd %h21%/bin
V7.1 과 V7.1 이후 버전
cd <Installation Drive>:\Program Files\AspenTech\InfoPlus.21\c21\h21\bin
3. History check utility 실행, H21ARCCK.
h21arcck -r <repository name> -a <fileset number> -d -o -b
주: Repository name는 대소문자를 구별함으로 "TSK_DHIS" 와 "tsk_dhis"는 다른 내용입니다.
Keywords: Error reading historical repeat area
Disk history read error -1021
KR-
References: None |
Problem Statement: Starting with aspenONE Process Explorer (A1PE) V8.8.1, a variety of plots are available that allow users to add comments and annotations to the plot and store them in the Aspen InfoPlus.21 (IP.21) database. This requires that either the IP.21 server be running on V8.8.1 or If using IP.21 versions prior to V8.8.1, a new definition record should be loaded to the IP.21 database for comments and annotations to function correctly.
Note: A1PE only supports connecting to the IP.21 databases starting from V7.3 and higher. For more information, check the A1PE Release notes. | Solution: A new definition record called "IP_CommentDef" is introduced in V8.8.1 to store comments and events added by users to the event plots in A1PE.. These comments can be added to KPIs, SPC charts, Trend charts and Event plots, but the comments will not function or get saved to IP.21 when connecting to IP.21 database prior to V8.8.1 without adding the "IP_CommentDef" record to the database. This solution documents two methods to get the comments to work when connecting to older versions of IP.21.
Method 1:
The first way is to load "IP_CommentDef" record into the IP.21 database. Use the attached RLD file (Comment.rld) to load this new definition record into older IP.21 databases prior to V8.8.1. For instructions on how to load RLD files into IP.21, please refer to AspenTech KB solution 111481.
Method 2:
The second way is to install a V8.8.1 IP.21 server that is dedicated to storing comments on the same server as aspenONE Process Explorer. This way, A1PE will point to the local IP.21 server to store comments.
Keywords: Comments
IP_CommentDef
References: None |
Problem Statement: When publishing an Aspen IP.21 Browser Graphic Studio project to aspenONE Process Explorer not all of the folders are created in the ProcessExplorer publish path and the process ends abruptly with the curious error dialog:
Cannot create directory <C:\inetpub\wwwroot\AspenTech\ProcessExplorer\Files\Public\MyProject>
Error is: The operation completed successfully.
Alternatively, when publishing the same project to Process Browser a different, but slightly more informative (but still unhelpful), error message appears:
Encountered an improper argument. | Solution: The problem can be caused by project graphic references to files that have been either deleted or renamed. You must go through all the Display Items and attempt to Edit Graphic to see where the problem lies:
You are likely to find that at least one of the Display Items has a reference to a file that does not exist. Such a Display Item would produce the following error dialog when you attempt to edit it:
Cannot find the file : MyGraphic
Having identified this referencing error it is a good idea to synchronize the listed graphics in the Mimic folder since it is likely to be showing obsolete references. There is a right click option to do this in the Project Directories area of the application (bottom left corner of window):
You should then correct the graphic reference. Right click the problem Display Item and click Properties. The Graphic Name on the Graphic Display Properties window will need to be reselected from the Choose a graphic file dialog:
Save the changes made and attempt to republish the project. You may have to do this several times before complete success if multiple files have been deleted or renamed.
Keywords: Upload
Web21
a1PE
warning
References: None |
Problem Statement: How to upgrade an Aspen InfoPlus21 snapshot (.SNP) file. | Solution: Upgrading a Snapshot file is the step taken after Aspen InfoPlus.21 family of products are upgraded. In other words, we should run a utility that creates a new database snapshot from an older, previously saved database snapshot. The new database snapshot will have records with an internal structure that is required by the upgraded version of InfoPlus.21. InfoPlus.21 includes the InfoPlus.21 Database Upgrade Wizard that aids in upgrading the InfoPlus.21 database snapshot.
The procedure to upgrade IP21 snapshot file is mentioned below:
Please find the procedure below to upgrade the snapshot file (.SNP):
1. Open IP21 Manager from Start | Programs | AspenTech | Aspen Manufacturing Suite | Aspen InfoPlus.21 | InfoPlus.21 Manager
2. Confirm that the InfoPlus.21 database is not running.
3. Click Actions | Upgrade Database. The InfoPlus.21 Database Upgrade Wizard is displayed.
Note: You can click Cancel on any of the screens to stop the upgrade.
It is recommended to use the Typical upgrade option.
To use the Typical option to upgrade the database:
1. Click the Typical option to select the default upgrade options.
2. Click Next. The InfoPlus.21 Database Upgrade Wizard Source/Output Screen is displayed.
3. In the Source field, enter the source snapshot filename you want to upgrade, or click Browse… to locate a snapshot file. Click on a file to select it and click Open. The selected file name is displayed in the Source field.
4. In the Output field, enter the name of the database snapshot where you want to save the upgraded database, or browse to locate the snapshot file. Click on the file to select it and click Save. The selected file name is displayed in the Output field.
5. Click Finish. The upgrade process starts. A message is displayed when the upgrade is successful.
To use the Custom option to upgrade the database:
1. Select the Custom option to begin a manual entry upgrade.
2. Click Next. The InfoPlus.21 Database Upgrade Wizard Source Database screen is displayed.
3. In the Snapshot filename field, enter the name of the database snapshot that you want to upgrade, or browse to locate a snapshot file.
Click on a file to select it and click Open. The selected file name is
displayed in the Source field.
Note: This field will only display the filename that InfoPlus.21 loads if that particular snapshot needs to be upgraded. The field remains blank if the snapshot is up-to-date.
4. Optionally, in the Optional list of records that should not be created or modified field, select a file that contains records that should not be created or modified. Enter the name of a text file, or browse to locate the text file. Click on the file to select it and click Open. The selected file is displayed in the field.
Note: You can click View to see the contents of the text file.
5. Click Next. The InfoPlus.21 Database Upgrade Wizard Target Database Screen is displayed.
6. To use the default Build and load a new snapshot option, click Next.
The InfoPlus.21 Database Upgrade Wizard Base Database Snapshot screen is displayed.
Note: To use the Load an existing snapshot option, select the option, enter a snapshot name, click Next, and go to Step 10. For more information, see the InfoPlus.21 Administration Help.
7. In the Base field, select a snapshot file that contains RLD files to be loaded or accept the default file (InfoPlus21DB.snp). Enter the name of a snapshot file, or click Browse… to locate the snapshot file. Click on the file to select it and click Open. The selected file is displayed in the Base field.
8. Optionally, click on an RLD file from the Available list and click the right arrow to move it to the Selected list. Within the Selected list, you can reorder RLD files using the up and down arrows.
9. Click Next. The InfoPlus.21 Database Upgrade Wizard Upgrade Options Screen is displayed.
10. To use the default Modify some records option, and then click Next.
The InfoPlus.21 Database Upgrade Wizard Output Database Screen is displayed.
Note: Aspen Technology strongly recommends using the default option.
11. In the Save database field, enter the name of the database snapshot where you want to save the new database, or browse to locate the snapshot file. Click on the file to select it and click Save. The selected file name is displayed in the Save database field.
12. Optionally, change the name and destination of the output message file.
13. Optionally, click the Copy ACLs for created records option to specify to only copy ACLs for records that will be created in the target database. The default selection is the Modify all record ACLs option.
14. Click Finish. The upgrade process starts. A message is displayed when the upgrade is successful.
15. When the upgrade is completed, select the Start on Reboot check box in the InfoPlus.21 Manager (if it was selected before upgrading to V8.8).
16. Before restarting InfoPlus.21, make sure that the upgraded database is named the same as the previous InfoPlus.21 database. Then restart the InfoPlus.21 database
Keywords: Upgrade snapshot
InfoPlus21 upgrade
.SNP upgrade
References: None |
Problem Statement: When trending in Aspen Process Explorer in the Aspen InfoPlus.21 server, getting the following error message shown in the screenshot below. | Solution: Below detailed the troubleshooting steps to be taken.
1. Browse to C:\Program Files (x86)\AspenTech\ProcessData in Windows Explorer
2. Double-click on ProcessDataAdministrator.exe to launch the Aspen Process Data Administratror
3. Select the data source from the drop-down list in Data Sources tab. The Status and Status String should be shown as below screenshot in which Status is showing as apdConnected and Status String as Connected.
4. Select the Admin tab.
5. Click on the Test For Components button.
The following error message may be displayed.
Proceed to click on the OK button and the following screen will be shown prompting that the IP21DaManager.dll is not registered.
If logging had been enabled for Data Servers in the Logging tab in Aspen Process Data Administrator, browse to C:\ProgramData\AspenTech\DiagnosticLogs\ProcessData and open the log file called ProcessExplorer.DataServer.IP21.<username>.log in Notepad. The following error message will be seen in the log file.
The following steps will need to be performed to resolve the issue.
1. Browse to C:\Windows\SysWOW64 in Windows Explorer.
2. Right-click on cmd.exe.
3. Select Run as administrator from context menu.
4. Browse to the folder in which the DLL is located in using the following command in command prompt.
cd C:\Program Files (x86)\AspenTech\ProcessData
NOTE:
This path can be different depending on version and 32bit or 64bit.
C:\Program Files\AspenTech\MES\ProcessData
C:\Program Files (x86)\AspenTech\ProcessData
5. Re-register the IP21DAManager.dll using the following command in command prompt.
regsvr32 IP21DAManager.dll
6. You may in some cases need to restart the TSK_APEX_SERVER task from the Infoplus.21 manager.
7. Relaunch Aspen Process Explorer.
Keywords: IP.21 is not accessible from '<nodename>' or is not currently running on '<nodename>'
IP21DaManager.dll is not registered. Required for communication with IP.21.
Failed to create IP21 DA Manager component: IP21DAManager.dll: Class not registered
References: None |
Problem Statement: How to close HYSYS case using VBA? | Solution: We will discuss two methods to close HYSYS case using VBA:
METHOD 1.
Normally, user can close HYSYS application by executing the following codes. The code will be triggered when the scripted macro button "CloseSimulation" is clicked:
Private Sub cmd_CloseSimulation_Click()
Dim Response As String
On Error Resume Next
' -- check to see if simulation is loaded --
If IsSimLoaded = True Then
Response = MsgBox(Prompt:="Would you like to save changes in your simulation'.", Buttons:=vbYesNo)
If Response = vbYes Then
hyCase.Visible = False
hyCase.Close (True)
End If
' -- close simulation --
hyCase.Visible = False
hyCase.Close
'hyApp.Quit 'This statement would also close the application. Deactivated by default.
Set hyCase = Nothing
' -- delete displayed name of simulation --
Worksheets("Sheet1").Range("A5").Value = ""
End If
Worksheets("Sheet1").Range("A5").Value = ""
End Sub
METHOD 2.
It is possible to increase the level of automation to automating the closing of HYSYS Application as soon as user exits the Workbook. No macro button is needed in this case.
Assuming that HYSYS Application has been declared (you can refer to this article for different ways of calling HYSYS simulation cases: https://esupport.aspentech.com/S_Article?id=000044410), we can utilize the Workbook trigger in VBA as followed:
On VBA editor window, open "ThisWorkbook" code by right clicking on "ThisWorkbook" > View Code.
On the Script Editor Window, select "BeforeClose" as the procedure. This is a built-in trigger in VBA. The subroutine will be executed based on the selected trigger.
For the script itself, we can write the following codes:
Private Sub Workbook_BeforeClose(Cancel As Boolean)
Set hysysApp = hyCase.Parent
hyCase.Close
hysysApp.Quit
End Sub
This simple script will close HYSYS automatically as soon as user exits the Workbook.
Keywords: None
References: None |
Problem Statement: The TFREEZE property gives an error message ''ERRORS ENCOUNTERED IN CALCULATION OF SOLID PURE COMPONENT PROPS USING'' when using the Vapor-Liquid-Liquid system. | Solution: We recommend to upgrade the software to the latest version.
However, this workaround:
1. Open the Properties Environment and select from the Home ribbon: Retrieve Parameters.
2. Navigate to Methods | Parameters | Pure Components | REVIEW-1
3. Find the parameter DCPLS (difference between liquid and solid heat capacity at the triple point) and input some values for the related solid components.
After doing the above workaround, the customer should be able to run the simulation and view the stream results.
Keywords: TFREEZE, DCPLS, freeze-out temperature
References: None |
Problem Statement: How to create Overspill for a note datasheet. | Solution: First make sure that the note overspill datasheet name and template name is different than “AZ Notes Overspill Sheet.xls ” and “AZ Notes Overspill Sheet” respectively, as this feature will be included in out of the box product.
There are two main parts to create an overspill for Note datasheet:
Modify Class Library
Define Datasheet as overspill
Modifying the Class Library
1. Open class library editor (CLE) application.
2. Define a new class view (i.e. NoteOverspillCV).
3. Create a new composite view (i.e.Note OverspillCmpV) and select base class for this (i.e select comment class in this case) as shown in screenshot below:
4. Define new attribute in these newly created class view (i.e. NoteOspill) and composite view (i.e. NoteOspill) as shown in screenshot below.
5. Open Comment class and create new attribute (i.e. TestNoteOSpill) as shown in screenshot below:
6. Connect NoteOspill attribute of composite view to TestNoteoSpill attribute of comment class by dragging that attribute from Comment class and dropping it on composite view attribute. As soon as you drop that on Composite view new dialogue box will appear as below. Select Synchronize All option from it:
7. Similarly connect class view attribute NoteOspill to composite view attribute NoteOspill.
8. Add this NoteOverspillCV class view to the existing ProcessSpecification class view by creating a new node inside ProcessSpecification class view, which is a datasheet object class view for note datasheet. See screenshot below for more detail.
9. Open ProcessPlantEquipment composite view and add new attribute (i.e. Ospill).
10. Open ProcessPlantEquipment Class and drag and drop Comment node from that class to Ospill attribute in ProcessPlantEquipment composite view.
11. This will open new dialogue box as below. Select Synchronize All option from that option as shown in screenshot below:
12. Drag and drop Ospill attribute from ProcessPlantEquipment composite view to Ospill node(The one which we have defined in step 8 above) in ProcessSpecification class view and select Synchronize All option.
13. Check Library for errors by pressing “Ctrl+F7” or by clicking on “Tools | Check Library” option from toolbar as shown in screenshot below:
14. It should say zero error found as shown in screenshot below:
15. Make a class store by selecting option from toolbar “Tools | Make Class Store” as shown below. You can choose to overwrite or create a new one and follow the option.
16. Once class store is made without any error message, close the class library editor (CLE).
17. Open ABE (Aspen Basic Engineering) administration tool and re-load the particular workspace which is using this class store.
B. Define Datasheet as overspill
1. Open Datasheet Definer application and connect to the workspace which is using the same class store that we have modified in Part – A of this document.
2. Open “AZ Notes sheet.xls” datasheet with datasheet definer.
3. Save this file as different name. i.e. “Notes Overspill Sheet.xls” you can save it as different name as long as it is not “AZ Notes Sheet.xls” or “AZ Notes Overspill Sheet.xls”.
4. From Datasheet Menu click on Properties | Datasheet Properties and it will give you dialogue box as below. Change the name over here also for Title field. Normally you can type the same name as datasheet name. i.e. “Notes Overspill Sheet”.
]
5. Click on Notes field in datasheet and from datasheet menu select properties | field properties.
6. Click on browse button and map to the noteOspill attribute in select Attribute window. Click ok on Select Attribute window.
7. Once you click on Ok button on Select Attribute window, Route in Value Field should show as below. Also change the number of lines to 47 or you can change it according to your requirement.
8. Click on Ok button on Value Field Properties window.
9. Make sure you select that NoteOspill field and from Datasheet menu Select Tools | Set Wildcards.
10. It will open up a new window named “Set Wildcard”, click ok on this widow. This will set a wildcard value in NoteOspill field to 1.
11. Again make sure you have NoteOspill field selected and from Datasheet Menu click on Tools|Set Overspill and type same name for TemplateID as you have specified in step 4 for Title field as shown in screenshot below. (This will overspill the sheet with template ID “Notes Overspill Sheet”) Click on ok button.
12. Click on Generate Template option from Datasheet menu and save this template in appropriate template directory.
13. Save this datasheet, close this datasheet, close workspace and exit out of the datasheet definer application.
14. Reload the workspace from ABE Administration tool.
15. You should see new datasheet with name Notes Overspill Sheet in datasheet editor application.
Keywords: Note Datasheet, Overspill.
References: None |
Problem Statement: How to import stream data from Aspen HYSYS into Aspen Flare System Analyzer | Solution: In this discussion, an Aspen HYSYS model named "Sour Water Stripper.hsc" with two product streams is used. A user can follow the next detailed instructions to import data from Aspen HYSYS.
1) Open Aspen Flare System Analyzer.
2) Create a new case or load an existing case. When creating a new case, it is not necessary to select components before importing the HYSYS data.
3) From the command menu select File | Import Sources ... | HYSYS Stream Sources ... to get to the HYSYS Import of Source Data dialog window shown below:
4) Click on the Browse button to select the intended hsc file (Sour Water Stripper.hsc in this example, located on the folder C:\Program Files (x86)\AspenTech\Aspen HYSYS VX.X\Samples) and click on the Open button on the HYSYS File for Source Data dialog window. Note that this step only defines the file path for this process.
Note: Change VX.X for your current version (i.e. V10.0).
5) Click on the Open button on the HYSYS Import of Source Data dialog window to link to HYSYS model. After the HYSYS simulation information is loaded, all streams in the HYSYS model will now be listed.
6) To import stream data (use stream Off Gas as an example here), enter a new name or select an existing name for Source, and set Source Type (typically Relief Valve).
7) After all the sources are processed, click on the OK button at the lower right corner of the dialog window to import data.
Keywords: Import, Import Data, HYSYS
References: None |
Problem Statement: User creates a new Cim-IO 'Transfer' record (Get or Put), populates it with all the relevant information, and then tries to activate it. They turn IO_Record_Processing to ON, and next they set IO_Activate? to YES. The problem is that IO_Activate? does not reset itself to NO, and the record fails to operate as designed with IO_Last_Status set to 'Initial State'. | Solution: The probable cause is that the Cim-IO 'Transfer' record (Get or Put) is in an UNUSABLE state and first needs to be set to USABLE.
When creating a new Transfer record, unlike a standard Analog or Discrete record, it is created as Unusable. This is because it contains a 'Record Pointer' field that points to the 'Main Task' (IO_Main_Task). Once this field is populated then the record can be set to Usable.
KeyWords
Keywords: None
References: None |
Problem Statement: After adjusting Cim-IO variables via Cim-IO IP21 Connection Manager [CCM], or Cim-IO Interface Manager [CIM] the registry does not update as expected. | Solution: Due to updated permission requirements of Windows Operating Systems may be necessary to run any Cim-IO configuration utilities with "Run as Administrator" privileges.
Keywords: Registry update
Cim-IO variables
References: None |
Problem Statement: To ensure AspenTech IP.21 servers operate as expected alongside anti-virus/endpoint protection products this article should be adhered to.
It has been known that anti-virus/endpoint protection products may falsely block AspenTech IP.21 product files and cause the following on an Aspen IP.21 server:
performance to be impacted
start-up problems
*Note, this article is written regardless of antivirus product or endpoint security protection vendor (Symantec, McAfee, FireEye, etc…)
The following | Solution: states both the folders and specific Aspen executable files that together must be excluded from anti-virus/endpoint protection scanning.
Solution:
1) Folders to be excluded (where existing):
.\Program Files (x86)\AspenTech\
.\Program Files (x86)\Common Files\AspenTech Shared\
.\Program Files\AspenTech\
.\Program Files\Common Files\AspenTech Shared\
.\inetpub\wwwroot\AspenTech\
.\ProgramData\AspenTech\
C:\Users\Public\PublicDocuments\AspenTech\
C:\Users\All Users\AspenTech\
2) Files to be explicitly excluded:
Place any executable processes related to Aspen InfoPlus.21 server into the exclusion list. You must place the names of the actual executables into the exclusion list, it is considered not enough to just place the Aspen InfoPlus.21 code folder into the exclusion list.
The following list of executables are normally started by Aspen InfoPlus.21 server, however this list is not exhaustive. Your Aspen InfoPlus.21 server may also start other programs not in this list. The solution here is to check your Defined Tasks listed in InfoPlus.21 Manager for the executables used.
*Note: depending on your installation bitness (32 or 64), except for h21prime and h21archive, these executables are located in either:
C:\Program Files\AspenTech\InfoPlus.21\db21\code
C:\Program Files (x86)\AspenTech\InfoPlus.21\db21\code
Name of executable: Used to start:
tsk_server.exe InfoPlus.21 Task Service
dbclock.exe TSK_DBCLOCK
h21prime.exe
(C:\Program Files (x86)\AspenTech\InfoPlus.21\c21\h21\bin\
OR C:\Program Files\AspenTech\InfoPlus.21\c21\h21\bin\) Initializes repositories
h21archive.exe
(C:\Program Files (x86)\AspenTech\InfoPlus.21\c21\h21\bin\
OR C:\Program Files\AspenTech\InfoPlus.21\c21\h21\bin\) Archiving program for each repository
plantap.exe TSK_PLAN
savedb.exe TSK_SAVE
h21task.exe TSK_H21T
h21arcbackup.exe TSK_HBAK
kpi_task.exe TSK_KPI
hlth.exe TSK_HLTH
ip21servicehost.exe TSK_ACCESS_SVC
ip21OPCuaserverhost.exe TSK_OPCUA_SVR
cimq.exe TSK_CIMQ
infoplus21_api_server.exe TSK_ORIG_SERVER, TSK_ADMIN_SERVER, TSK_APEX_SERVER, TSK_EXCEL_SERVER, TSK_DEFAULT_SERVER, TSK_BATCH21_SERVER
sqlplus_server.exe TSK_SQL_SERVER
iqtask.exe Query tasks (TSK_IQ1, TSK_IQ2, etc.)
sqlplusreportscheduler.exe TSK_SQLR
tsk_clc1.exe TSK_CLC1
bgcsnet.exe TSK_BGCSNET
iq.exe TSK_CHK_SCRATCH, TSK_ACTG_SYNC
actg.exe TSK_ACTG
actg_snf.exe TSK_SNFA, TSK_SNF2, TSK_SNF3, TSK_SNF4, TSK_SNF5
GoldenBatchProfiling.exe TSK_GBP
cmon.exe TSK_CMON
cmrpt.exe TSK_CMRP
ceve.exe TSK_CEVE
cimio_c_client.exe Cim-IO Main Client Tasks (TSK_M_device)
cimio_c_async.exe Cim-IO Async Client Tasks (TSK_A_device)
cimio_c_unsol.exe Cim-IO Unsolicited Client Tasks (TSK_U_device)
cimio_c_changeover.exe TSK_DETECT
Finally, it would also be recommended to exclude the Aspen executable responsible for network licensing located on servers running Aspen SLM network:
lservnt.exe
(C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT)
Keywords: Virus
Antivirus
Firewall
Exception
Exclusion
Exclude
Security
Scanning
References: None |
Problem Statement: There are two sets of Lower and Higher heating values (LHV & HHV) available for a stream in Aspen HYSYS. What is the difference between them? | Solution: HYSYS streams are able to calculate two different sets of LHV and HHV, and each of these is calculated with a different method. The first set is calculated with the HYSYS default method as a part of the stream properties, as shown below:
In this default, HYSYS calculates the Lower Heating Value as the sum of the heat of combustion (at 25 °C and 1 atm) multiplied by the mole fraction for each component in the stream:
The Higher Heating Value is calculated as the lower heating value plus the heat of vaporization of the water formed during combustion (at standard conditions):
Note: HYSYS will report <empty> if the Heat of Combustion is not specified for one of the components present in the stream (note that hypothetical components by default do not have this value specified).
The following spreadsheet illustrates this calculation for an equal molar gas mixture of C1 to C4 alkanes.
The Heat of Combustion values for individual components in cells B2 through B6 are taken from the HYSYS pure compound database which can be reviewed in any HYSYS simulation.
The second set of heating values are calculated using the same formula as above, but with data from ISO 6976:1995(E). This calculation includes data for the following components (at 15 °C and 1 atm):
Note: If the stream contains components other than these, then data for the hydrocarbon with the nearest molecular weight is used. If the molecular weight is greater than decane, then the data for decane is assumed. When data is being assumed, a message will appear in the trace window.
This set of heating values is calculated in a volume specific energy unit and is not displayed automatically among stream properties in HYSYS. To view them, follow these steps:
1. From the Properties page of a stream view, press the green colored plus sign to bring up the list of Available Stream Correlations.
2. Expand the "Gas" option to view the list of properties in this category.
3. Highlight the Higher and Lower Heating Values, one at a time, and press the "Apply" button to add them to the stream properties.
Keywords: Heating values, Lower Heating value, Higher Heating value, LHV, HHV, Gross Heating Value, Net Heating Value, Gas Properties
References: None |
Problem Statement: How can solid polymers be used in Solid Models? | Solution: Before V8.8, Component Type “Polymer” was not supported in Solid handling models. Polymer pellets could be defined under “Solid” type. If MIXCISLD sub-streams were defined and the polymer was placed in the CISOLID substream, Aspen Plus would ignore phase equilibrium involving the polymer.
Starting in V8.8, Polymer Modelling in Aspen Plus was extended so that polymers and oligomers can be recognized as particulate solids, enabling optimization of many more common processes.
Aspen Polymers, has always calculated properties for polymers below their melting point properly, but now the solid-handling unit operations can also treat them as solids.
Aspen Plus originally treated solid polymers as liquid-phase components in order to address phase equilibrium. Small molecules (solvents and monomers) dissolve inside the solid polymers even when the polymer is below the melt transition temperature. By including the solid polymers in the liquid phase, the Aspen Plus flash algorithms are able to calculate the equilibrium concentration of dissolved monomers in the polymer phase.
For solid-liquid systems, like emulsion polymerization, the system will treat the polymer as a second liquid phase (appropriate binary parameters between segments and monomer/solvent components are required to force the phase split).
From V8.8, to enable polymers in solid handling models, the following must all be true:
The "Treat polymers below the polymer melting point as solids" box on the Components | Polymers | Characterization | Options sheet in the Properties environment must be checked.
The substream containing the polymer (usually the MIXED substream) must be assigned a PSD mesh ID on the Setup | Solids | Substreams sheet in the Simulation environment.
If there is a single liquid phase, and the mole fraction of the polymer component is greater than Solid polymer mole fraction threshold, or if there are two liquid phases (in which case the phase richer in polymer is treated as solid, regardless of whether it meets the threshold).
When all of the above are true, three kinds of components will be treated as solid in solid-handling unit operations:
Components specified as Solid on the Components | Specifications | Selection sheet
Components specified as Polymer or Oligomer on the Components | Specifications | Selection sheet, if they are below their polymer melting point (property-set property TM) in the solid inlet stream to the block.
Components specified as catalysts on the Components | Polymers | Characterization | Site-Based Species sheet, if they are non-volatile (set Pure Component parameter PLXANT to -1e20 for the component to force non-volatility).
The following notes are important when using polymers in solid model:
This decision to treat polymers as solid are made independently by each block, based on the temperature of the solid inlet stream.
Generally when polymers are processed in solid-handling equipment they are well below their melting point, but care must be taken with solid-handling blocks such as dryers, which change the temperature.
When one of the conditions stated above is not satisfied, then only the first of these sets of components will be treated as solid (and possibly not in the MIXED substream, depending on the block's support for solids in the MIXED substream).
When polymers are treated as solids, the entire liquid phase containing the polymer is treated as solid. Non-polymer components in this phase are treated as moisture components.
The solid-handling models support solids in the MIXED substream. This is true for most models. Exceptions:
-CCD (no support for solids in the MIXED sub-stream)
-Dryer (shortcut model does not support solids in the MIXED sub-stream; the other models have support)
-Crystallizer (not designed for crystallizing polymers, but inert solid polymer flow affects results from the McCabe growth law)
Keywords: , Solid Models, Solid Polymers
References: None |
Problem Statement:
How to install Aspen Flare System Analyzer, Aspen Energy Analyzer, Aspen Simulation Workbook (ASW), and Aspen OnLine?
These products can be installed using the custom install during the installation process. The picture below is a standard install and not a custom install. Therefore, clicking the setup.exe within the last "aspenONE_V10_ENG" folder will not show the custom install option. | Solution:
The install must start with the setup.exe located at the root of the install folder. Locate the main setup.exe, then, run the custom install option. Please follow these installation steps:
1. Open the installation media and locate the Setup.exe at the aspenONE_V10 folder and right click the Setup.exe then select “run as Administrator”.
2. click "Yes" button
3. Click "aspenONE Engineering"
4. Click the box for "Use Custom Install" and then click "Begin Install" button.
5. Click on "Install aspenONE products" button
6. Click the box "I accept the terms of this agreement", then click "Next" button.
7. Finally, check the boxes for the four Aspen Products as needed and click "Next" button to continue and complete the rest of the installation steps.
Keywords: aspenONE Engineering V10 installation, Aspen Flare System Analyzer, Aspen Energy Analyzer, Aspen Simulation Workbook, and Aspen OnLine
References: None |
Problem Statement: Does the auto-mapping feature among process streams and equipment ports work in the ABE V10 Legacy Explorer? | Solution: The auto-mapping feature among process streams and equipment ports in ABE V10 is only available from the Web Mapper and Drawing Editor.
When creating new equipment in either the Web or Legacy Explorer, the equipment will not contain mapped ports. The only exceptions are: Pump, Compressor, Air Exchanger and Plate Exchanger since there is an ‘Auto-Port’ rule already defined for this type of equipment. The only way to get to map streams to ports is through the Drawing Editor, Web Mapper or Simulation Importer tool.
Keywords: Auto-mapping, Process Streams, Equipment Ports, Web Mapper, Drawing Editor, Web Explorer, Legacy Explorer, Simulation Importer.
References: None |
Problem Statement: How to access individual phase properties of a stream in HYSYS from VBA? | Solution: Typically users can get overall stream properties by accessing directly the attribute associated with the property. These attributes can be found under the object class view in VBA HYSYS type library. However, the reported values associated with the attributes under the class are of the overall properties of the streams in HYSYS. Some overall properties may be empty if the properties can only be reported for individual phase. For example, in the case of compressibility factor of a single phase stream, it's possible to get the compressibility factor by the following code:
…mystream.Compressibility.GetValue…
(Note that the above code assumes you have already declared mystream object (ProcessStream or MaterialStream object) and its parent objects. If you are not familiar with the declaration steps, please refer to this article:
However, for a two phase stream, compressibility factor is not reported as overall mixture property because it would not have any useful physical meaning. The compressibility factors are only reported for individual phases, and the overall mixture property is left empty.
To access the individual phases properties, users need to go through the Fluid object path rather than directly under the ProcessStream or MaterialStream object. For example, in the above context, accessing the vapor compressibility factor can be done as followed:
…mystream.DupilcateFluid.FluidPhases(ptVapourPhase).Compressibility.Value…
Keywords: None
References: None |
Problem Statement: How do I request a replacement / modification / correction / consolidation for my license file? How can I obtain a new or additional license file? | Solution: There are several reasons why you want or need to request a new license file, such as:
Add a product that is missing.
Moving license file from one machine to another machine.
Change license configuration from standalone to network and vice versa.
Change license configuration from dongle to dongle-free and vice versa.
Upgrade software version.
Consolidate several license files into one.
Split one license file into several files, among others.
Need a temporary or emergency license.
Note: If you are experiencing a critical "plant down" situation and are in immediate need of a license file, please reach out to our Deployment support team using one of our support numbers to get an emergency license file.
1. Go to https://esupport.aspentech.com
2. Log in to your Support Center account
3. Select Support menu in the top bar
4. Click on Request License Keys in the Software Services section
5. Complete the form and Submit
A case will be created and a Customer Care specialist will review your request
FAQ’s
WHAT INFORMATION DO I NEED TO REHOST MY LICENSE?
Please be sure to include your System Name and Locking Information of your new machine.
How to obtain my System Name
How to obtain my Locking Information
IS THERE ANY OTHER INFORMATION THAT I NEED TO INCLUDE?
Please provide as much detail as possible regarding your need for a license key, this will help to prevent any delays and expedite your request.
For version above V8.8, the locking information could be successfully generated from “Locking info” tab of SLM license manager.
When the request is entered, a new Customer Care case will be created with a ticket ID,
This ticket ID can then be used to follow the progress of the request.
Keywords: Request license file, obtain license file, locking info
References: None |
Problem Statement: How to submit a university order | Solution: 1. Go to https://esupport.aspentech.com/
2. Select Support Menu in the top bar.
3. Click on Academic Order within the Software Services section.
4. Select Guest if you are a new user, or Login if you are a University contact with a valid role
5. Complete the form and Submit.
An Opportunity will be created and a Customer Care Specialist will review your request.
FAQ’s
CAN I USE MY PERSONAL EMAIL ADDRESS FOR THIS REQUEST?
No, please be sure to include University email addresses for all contacts in the order.
WHAT INFORMATION DO I NEED IF I AM RENEWING MY LICENSE?
Please be sure to have your system name handy.
How to obtain my System Name
HOW CAN I CHANGE THE CURRENT AUTHORIZED CONTACTS FOR MY UNIVERSITY?
Include the new contacts in the University Order form. For changes after your order is processed, please contact [email protected].
DO I NEED TO PAY IN ADVANCE FOR MY ORDER?
For 1 year only, no. For 2-5 years, payment in full is needed before we can ship your order.
WHAT PRODUCTS ARE INCLUDED IN THE UNIVERSITY PROGRAM LICENSE?
Please visit the following link to review all the products included.
https://www.aspentech.com/en/university-outreach/available-products
Keywords: None
References: None |
Problem Statement: In Aspen Shell & Tube Exchanger version 8.4, there is a tab for opening templates.
Where do you find this option in version 8.8.2? | Solution: In Aspen Shell & Tube Exchanger V8.8.2, there are no New and Template selections because the file extension.EDT is added to the file type in the Open dialog.
You just need to locate the template file on your machine.
The default template files .EDT are located in the following directory C:\Program Files (x86)\AspenTech\Aspen Exchanger Design and Rating V8.8.2\Dat\Template
Keywords: EDT, template, location
References: None |
Problem Statement: I added the property Total stream cost, I input some stream prices, but after the simulation is run the row for Total stream cost was empty. Would you please tell me what to do to get the total stream cost? | Solution: You should change the calculation option for this property. By default the WET option is chosen:
The user needs to select DRY option. Please go to the Simulation environment, Stream Results, click on General Options from the Stream Summary tab to change the settings (1), open Calculation Options tab (2), select "Total stream cost" property from the list on the left side (3), change the Water Basis to DRY (4) and click OK (5). After that you will be able to see the cost in stream results table.
If the DRY water basis option is not available, please go to the properties environment and add WATER to the component list.
Key words
Aspen Plus, stream cost, stream results
Keywords: None
References: None |
Problem Statement: When saving my EDR file, an Aspen B-Jac Drawing Document is also created, which looks exactly the same from the outside as my original file. What is the purpose of this data and why is it created? | Solution: The .BJT file contains the Mechanical drawing information (this is what you see when you click on ‘All Drawings’). If this file wasn’t present when you opened a file, the Mechanical drawings would be blank and you would have to run the case to see the drawings. If you had the .BJT file, you could see the drawings without running the case.
If you do not want the .BJT file to be saved, you can run the Mechanical calculation in a mode that does not generate drawings:
Key words
EDR, Shell and Tube Mechanical, Drawings, BJT
Keywords: None
References: None |
Problem Statement: How to view the data points used by the program for constructing the plots? | Solution: Right-click on the plot and click Show as history. Raw data used for constructing the plot displayed, as shown below.
KeyWords
Plots, Raw data
Keywords: None
References: None |
Problem Statement: Frequently Asked Questions (FAQs) regarding Data Collection in APC Builder | Solution: 1. Is there any limit to the number of tags I can collect?
There is no limit to the number of tags, other than the physical hardware limits i.e. memory and CPU.
2. How can I tell if data is being collected right now?
In APC Builder, navigate to Online | Manage Data Collection and connect to the server. At the bottom of the data collection list, there should be a button that either reads “Start Collection” or “Stop Collection.” If the button reads “Stop Collection” and is active, then it indicates that the collection is running.
To confirm if good data is being captured, the user will need to extract data out using Online | Get Collected data and review the new dataset in APC Builder.
3. Where is the data actually stored?
The live data collection files are stored in “ProgramData | AspenTech | RTE | Vx.x | Clouds | Online | DataCollection.” However, these files are in binary format and are secured. It is not recommended to open or edit or move these files when data collection is running.
4. If I set up a large collection for my test, should I worry about running out of disk space?
All live data collection files are in binary format, which are compressed as far as the file size is concerned. The live data collection files therefore take up less space. However, like any other program, as the data collection keeps getting bigger and the collection period longer, these files will grow in size.
Additionally, the dataset that gets created during the extract process is an in-memory dataset. Which means, it creates the entire dataset in memory. This can easily cause the user to need to create smaller subsets of data points to extract from a long running data collection or to limit the number of points in the data collection. In case the size of the dataset and the duration of data collection requested got too large for the memory footprint, it is recommended to extract smaller batches (time range) of data each time.
5. Does stopping the collection free up any space?
No.
6. Can I move the data collection files to another disk where I have more space (i.e., off the system disk)?
It is not recommended to move the live data collection files. The data collection files cannot be moved without affecting the data collection process.
7. How do I get rid of old data that has been collected? Do I need to, or is it automatically deleted after a while?
The user could extract the data out using APC Builder and save the extracted data on a different drive, then stop data collection, clear the files out and restart data collection to free up space.
8. How can I collect data for several controller tests on one server? How do I keep them separated?
All data collections on a single server are stored as a single entity. To perform data collection for several controller tests, the user just needs to add the new tags for each test to existing collection list. While the collection itself cannot be separated, the user can separate out the tags for a specific test using the extract data option on a dataset that was extracted using Get Collected data.
9. Should I be using Excel to manage my collection lists?
Yes, it is easier to build and manage collection lists on Excel, which can then be imported into APC Builder. The format of this file can be generated by adding a dummy tag to the blank collection list and exporting out an excel file.
10. What happens if I delete all the tags and add a bunch of new ones while the collection is running?
The data for the old tags can no longer be accessed/extracted through the interface.
Keywords: APC Builder
Data Collection
DMC3
References: None |
Problem Statement: What is the best procedure to structure an APC Builder Project file? | Solution: Users of the conventional Aspen DMCplus application have over the years developed and refined best practice techniques of structuring and maintaining the modeling information for each individual DMC implementation. The APC Builder interface, which is comparatively newer interface for DMC application had multiple features that build on the conventional DMCplus Model interface. The differences between the two interfaces warrant developing a new set of best practice procedures to guide users. The list of best practices suggestions provided in this article will help users of the APC Builder interface to-
a. Organize the APC Builder Project file for multiple model cases, controller model updates, controller tuning updates.
b. Maintain a clean Project file to help ease the support and maintenance steps associated with an APC Controller.
Some best practice strategies for organizing an APC Project file include-
1. When a new model built in APC Builder is extended to develop the complete application (inclusive of the tuning), all Model ID cases and trials will be lost. APC Builder warns the user of this consequence before proceeding with the extension. The reason for deleting the cases and trials being that this information is not required when deploying the application online. Keeping the information in the online controller will unnecessarily increase the size of the online application.
The model cases and trial ID runs are however very important from model development and maintenance perspective. This information can be retained by making a copy of the original model application with the cases and using the copy to develop the application. The original application should be kept as a model only application (suggested naming convention- <ControllerName_Master>.
2. Keep the APC Workspace less crowded. Only keep the Master Model and the currently deployed application in this space (See screenshot below). For situations where a single APC Builder project file is used to maintain multiple controllers, keep the Master Model and currently deployed application for each of the controller in the APC Workspace.
3. All offline model updates must be carried out under the Master Model application in the APC Workspace.
4. Save any offline model updates to the Project Tree as separate applications instead of models. This helps preserve case references for model updates. Whenever there is a need to use one of the objects in the Project Tree, copy the object over to the APC Workspace, perform the desired operations, re-save the object back to the Project Tree and clear any unneeded information from the APC Workspace (bullet 2).
5. All other models, datasets and controller applications should be saved and preserved in the Project Tree.
6. Always specify timestamps in the object name when saving to the Project Tree.
Keywords: APC Builder
Project file
Best Practices
Organize
Structure
References: None |
Problem Statement: APC Builder (Aspen Process Controller Builder) is our new product that integrates the legacy Model, Simulate, Build, Smart Tune applications and the Collect and Extract commands.
This solution will address some tips and tricks for APC Builder projects. | Solution: · Purge the recycle bin more frequently. The recycle bin works similarly to the MS Windows recycle bin, if the bin is not purged, the "deleted" items will stay there.
· Save large datasets to the project and only have datasets you are currently working on the workspace.
· Split up the project into multiple projects where possible.
· Merge datasets that overlap with duplicated data.
· Use smaller datasets in the workspace; you can use ‘extract’ to create smaller datasets containing only the vectors needed.
Keywords: APC Builder, tips, project folder, APC Builder project, best practices
References: None |
Problem Statement: I am using the Equation Oriented Sensitivity feature to study the gains of my process for process control purposes. However, I am confused with the results I see. The results for a 1x1 case does not match the results found in a 2x2 case, where one of the independent and one of the dependent variables are the same as in the 1x1 case.
See the attached file for an example. The calculator block creates a linear system with 4 variables and 2 equations:
x = fa*a + fb*b
y = ga*a + gb*b
When a and b are constants, and x and y are calculated, we obtain the sensitivity matrix (fa fb; ga gb) for the 2x2 system, and if we evaluate the sensitivity of x (dependent) with respect to a (independent) we obtain fa. However, if we create a spec group to make both a and b calculated, and x and y constant, the results for the sensitivity calculation of x (dependent) with respect to a (independent) is no longer equal to fa. The constant fa is set to 11, but the gain which is calculated is 11.81.
Why? | Solution: Equation-oriented sensitivity enables you to compute the sensitivity between a set of independent and dependent variables. The sensitivity is the derivative or gain between the variables. This can be very useful for analyzing flowsheet behavior or in control system design.
Note that the problem reported above occurs only when the independent variable is not constant, and the dependent variable is not calculated. When the option "Force variable specification" check box is selected, the sensitivity changes the variable specification for the calculation: the independent variable is changed to be constant, and the dependent variable is changed to be calculated.
We can demonstrate why there is a difference. Suppose we have four variables, a, b, x and y which are related by two equations f and g.
(1)
If a and b are constant, then the sensitivity of x with respect to a is equal to
(2)
It helps to step back and look at the definition of the sensitivity. It tells by how much x will change when a is changed by a small amount. In other words:
(3)
Using the differential rules we have
(4)
If b is constant, we can replace Db by zero and we obtain the same formula as (2).
We can write the same equation as (4) for y:
(5)
If b is calculated and y is constant, we now need to set Dy to zero in equation (5) . That means that if we make Da non-zero, it implies Db is no longer zero. It is equal to:
(6)
We can then use the equation (6) in formula (4) to work out the new sensitivity:
(7)
This gives the sensitivity:
You can now clearly see why this sensitivity is not the same as when y is calculated and b constant. You can also check with the example that the formula gives the correct answer. See the calculator block C-1. The value of fa is 11, fb is -12, ga is 0.212121 and gb is 3.14159. The sensitivity is fa - fb * ga/gb = 11.81.
The key difference between the 1x1 case and the 2x2 case is that in the 1x1 case, the variable b is calculated and the variable y is constant, while in the 2x2 case they are constant and calculated, respectively.
If you're familiar with the control world, it is really the same as doing the process gain calculation with open or closed loops. In the 1x1 case, you still have one closed loop compared to the 2x2 case.
Be careful when using the "Force variable specification" to understand the consequences.
Keywords: EO Sensitivity
References: None |
Problem Statement: How to specify the relative humidity of a process stream in Aspen HYSYS? | Solution: The extension "Saturate with Water" can be used to specify the relative humidity of a process stream. In the newer versions this and some other commonly used extensions are installed with Aspen HYSYS. The extensions are available in the Custom group of Object Palette.
In the Saturate with Water extension, you can specify the relative humidity. The default value is 100%. You only need to specify the component mole fraction of water in the water stream. By default, the extension uses the temperature and pressure as specified in the Process stream. The flow rate for water is calculated based on the specified relative humidity.
There is a separate knowledge base solution (ID 112173) which explains how to configure a simulation to specify the relative humidity without using the extension. The "Saturate with Water" extension makes this easier without involving extra configuration in the simulation.
There is a simple example case attached with this solution which illustrates how to specify the relative humidity with "Saturate with Water" extension.
Keywords: Relative Humidity, Saturate with Water
References: None |
Problem Statement: Example of how to calculate the erosion velocity | Solution: In the Aspen HYSYS file you can find an example of how to calculate the erosion velocity using a spreadsheet or a user variable. This example uses the API -RP -14E equation referenced in solution 109437:
Vm = C/sqrt(rM)
where: C = a constant
rM = mixture density, lb/ft3
VM = maximum allowable mixture velocity
The attached Aspen HYSYS file uses an arbitrary value of 100. This equation is for liquid droplet systems (sand free).
Keywords: erosion velocity; user variable
References: None |
Problem Statement: Is there an example of component yields user subroutine for RYIELD block? | Solution: You can find the template of the subroutine in the folder c:\program files (x86)\AspenTech\Aspen Plus v8.8\Engine\User. The file is usryld.f.
Refer to the "user models reference guide" for detailed information. Note that the input stream vector argument SIN is not confused by the fortran compiler with the SIN() mathematical function, but you can rename the argument if you wish. Also the input and output stream vectors are declared as SIN(1) or SOUT(1). This is one of the fortran convention to indicate that the argument is a vector. The value of 1 is only a placeholder value. You may replace with the alternative syntax SIN(*) and SOUT(*). This will make no difference.
The attached example shows what you need to do in the USER subroutine. This example mimics what is done by the mass yield specification available as a standard option, only to illustrate with a very simple example. Code dealing with NC and CISOLID substreams will require a more detailed specification and details are available in the reference documentation.
The screen capture shows how the data entered in the block are mapped to the arguments of the subroutine.
Note that you need to have an intel fortran compiler installed and configured correctly to run this example.
Keywords: RYIELD, user, usryld
References: None |
Problem Statement: Unable to optimize heat exchanger design, due to disparate tools for process design, thermal heat exchanger design and mechanical designs, and optimization methods followed by other heat exchanger design tools that are not based on costs | Solution: Cost based design optimization philosophy followed by Aspen Exchanger design and rating (EDR)softwares would enable you to find the optimal design for your heat exchanger needs based on cost.
The seamless integration between the thermal and mechanical design tools of Aspen EDR together with its integration with Aspen Tech’s process simulation tools enables analysis of several different alternatives before presenting you with the most optimal design.
This document serves as a simple “getting started” guide, guiding through the most common progression of how an equipment designer would use Aspen Shell & Tube Mechanical to generate optimal heat exchanger design.
This Guide Demonstrates how to
· Specify input data
· Run the program
· View Key results
· Transfer results to other formats
Please download and follow the instruction on the file ‘Design Better HX using Aspen Shell & Tube Mechanical.pdf ’. This is a guide that would take you step by step through the exercise.
Keywords: design shell and tube, Cost based optimization, optimal heat exchanger design, mechanical design of shell and tube, interface to autocad inventor
References: None |
Problem Statement: Example of a DeButanizer column in Aspen HYSYS Dynamics. | Solution: The example is for a DeButanizer column to run in dynamic mode in Aspen HYSYS. There are two feed streams, each of which is a mixture of light hydrocarbons. The overhead product is a butane rich stream, and the bottom product is a mixture of heavier hydrocarbons.
The column has 15 stages. The feeds are connected to stage 4 and stage 8. A partial condenser has been used with vapour product going to vent and liquid product contains butanes. There are four control valves: two valves for two feeds, one for the overhead butane product and one for the bottom product.
There are six controllers in the simulation. The following variables are controlled using PID controllers:
· Feed1 – Mass flow
· Feed2 – Mass flow
· Condenser – Liquid percent level
· Condenser – Vessel pressure
· Reboiler – Liquid percent level
· Column Stage 6 – Temperature
The configured controllers can be found in the Control Manager. The user can open the control and change the setpoint to each controller from the Control Manager.
Â
The simulation has a strip chart with the following variables:
· Feed1 - Mass Flow
· Feed2 - Mass Flow
· Condenser - Vessel Pressure
· Main TS - Stage 6 - Temperature
· Butanes - Component Mass Fraction - i-C5
The HYSYS case is attached with this solution. You can download this example and explore the performance of each controller in the event of changes of setpoints.
Note: The example was created in V8.6 so it can only be opened in Aspen HYSYS V8.6 and higher.
Keywords: DeButanizer Column, Dynamics
References: None |
Problem Statement: How do I determine the Gibbs Free Energy (or other properties) of a stream? | Solution: In order to have the Gibbs Free Energy (or other properties) of streams reported, do the following:
Go to Data/Data Browser/Properties/Prop-Sets, and select New
Create a New ID property set (see Figure 1)
Figure 1. Creating a New Property Set.
In Properties tab, left click on Physical properties, and scroll down the properties list, select GMX
(Free energy of mixture) or other properties that you wish to be reported. See Figure 2.
Figure 2. Selecting Free Energy of mixture (GMX)
Then navigate to Setup/ Report Options/ Stream, and left click Property Sets button.
Move the property set that you created earlier from Available property sets list to Selected property
sets list by using arrow button. See Figure 3.
Figure 3. Selecting Property sets to be reported.
Reinitialize and run your simulation.
You will have the Gibbs Free Energy of streams (or other properties that you included on Property
set created) reported. See Figure 4.
Figure 4. Streams results summary.
Keywords: Gibbs Free Energy of a stream.
References: None |
Problem Statement: How do I design an A-frame vacuum steam condenser using Aspen Air Cooled Exchanger? | Solution: This new design guide is a step by step introduction to finding the optimum design of an A-frame air-cooled exchanger for the main vacuum condenser duty of a power cycle. It shows how to use the design optimization logic of Aspen Air Cooled Exchanger to find the optimum arrangement of your exchanger and the optimum air flow. From a conventional forced draft design you can see how to complete the following: transform your arrangement into an equivalent A-frame arrangement, check-rate the design, and finally, simulate the operation to verify your design accounting for the effects of vapor distribution.
The KBI includes a full design guide document as well as sample case files.
Keywords: design, rating, simulation, air cooler, vacuum, steam, condenser
References: None |
Problem Statement: Is it possible to vary the feed stage location and the total number of stages in RadFrac in order to find the optimum feed tray location? | Solution: There are some graphical techniques ( i.e. McCabe Thiele diagram ) which are very powerful to locate the feed tray. Nevertheless, Aspen Plus is well suited to locate the optimum feed tray.
The basic idea is to minimize some objective function by perturbing the feed location. The Optimization block in Aspen Plus does not handle discrete variables like stage numbers so this is not the best approach. The recommended approach is to use a Sensitivity block. A Calculator block (called a Fortran block before Aspen Plus 10.2) may be required depending on how fancy you want to get.
There are two scenarios:
Case 1: Vary only feed stage location, the total number of stages is fixed. Case 2: Vary both feed stage location and the total number of stages.
Example files are attached to illustrate both of these scenarios.
Vary the feed location
In the first case, the number of stages is fixed, and a Sensitivity block is used to directly vary the feed location. Once the results are obtained, it is possible to plot the composition of light key in the bottom to get the optimum feed location, or any of the other quantities.
Vary both the number of stages and the feed location
The second case is a little bit more complex. Here, a Sensitivity block is used to manipulate both, the number of stages and the feed location. A Calculator block (called a Fortran block before Aspen Plus 10.2) is used to set the feed stage at specific ratios of the total number of stages. It is essential that the feed stage is less than the total number of stages. The results are presented in tabular form. By inspecting the sensitivity results, it is possible to determine the optimum feed location for each tower size.
KeyWords:
column
tower
radfrac
Keywords: None
References: None |
Problem Statement: An example of reactive distillation in Aspen HYSYS | Solution: This example case simulates the synthesis of Methyl Acetate from Methanol and Acetic Acid in a catalytic distillation column. The feed conditions and composition are as follows:
Temperature 75°C (165°F)
Pressure 101.3 kPa (14.7 psia)
Molar Flow 45 kgmole/h (100 lbmole/hr)
Composition - Mole Fractions
Methanol 0.4
Acetic Acid 0.4
M-Acetate 0.1
Water 0.1
The column is configured with the specifications given below:
No. of Stages 15
Feed Feed, Stage 10
Condenser Type Total
Ovhd Liquid Distillate
Bottoms Liquid Bottoms
Condenser Energy Cond Q
Reboiler Energy Reb Q
Pressure
Delta P, Condenser 0 kPa (0 psi)
Condenser 95 kPa (13 psia)
Reboiler 101.3 kPa (14 psia)
Active Specifications
Reflux Ratio 5
Distillate Rate 20 kgmole/h (44 lbmole/hr)
The column is first solved without reaction.
The following kinetic reaction is added in the Properties Environment.
CH3OH + CH3COOH = CH3CH3COO + H2O
The forward has the following parameters:
A = 1.0e5
E = 2.3e4 kJ/kgmole
When the reaction is ready, enter the simulation environment and add the reaction in the column. It is assumed that the user is already familiar with reaction sets in Aspen HYSYS.
The standard solver “HYSIM Inside-Out” is not capable of handling reactions in the column. HYSYS will change the solver to Newton-Raphson Inside-Out. However, for this column we will use the Sparse Continuation Solver.
There are two HYSYS files attached with this solution: one with a distillation column without reaction and the other with reactions. Note that the simulations were created in HYSYS V8.6. These files can only be opened with V8.6 and higher versions.
Keywords: Reactive Distillation
References: None |
Problem Statement: When a compressor compresses gas from one system at P1 and T1 to another system at P2 and T2 and stops during the maximum pressure drop case, a differential pressure is developed. After a compressor’s shutdown, the gas is trapped between the upstream and downstream pipes as a result of the check valves and the pressure is equalized out. This equalized pressure throughout the compressor loops is called the settle-out pressure. The maximum settle-out pressure is calculated from coincident high-trip pressures on both suction and discharge sides of the compressor.
As per the API 521 standard, the minimum design pressure of the separator drum/scrubber should be calculated as 1.05 times the settle-out pressure. This will provide an adequate differential between the operating pressure and set pressure of the pressure relief device for a compressor shutdown contingency. | Solution: In the attached file, the activated compressors surge analysis tool in Aspen HYSYS has been used to determine the settle out pressure.
The steps taken to determine the settle out pressure are as follows:
1. Create a surge analysis for a compressor in the flowsheet.
2. Select the first template "Cooler on discharge side".
3. Select “ Total Power Loss “ for the scenario
4. In the Event Scheduler, add a new event to close the Loading valve as in the attached demo file
5. Run the surge analysis
6. The equalized pressure across the compressor, representing the settle-out pressure can be seen in the Worksheet tab of the compressor in the surge analysis sub-flowsheet
Keywords: Activated Surge Analysis, Settle-out pressure
References: None |
Problem Statement: Potential savings on CAPEX, OPEX and Energy consumed by process plants, lost due to use of simple heat exchanger models in Aspen Plus flowsheets | Solution: Rigorous heat exchanger models incorporated in process flow sheets enhances the fidelity of the flowsheet enabling you to reduce CAPEX, OPEX and Energy consumed.
Aspen Plus enables you to develop rigorous heat exchanger models in just few clicks, from within the flowsheet.
Here we demonstrate how you can develop rigorous heat exchanger models of
· A Shell & Tube heat exchanger and
· An Air Cooled heat exchanger
from an Aspen PLUS Flowsheet.
Please follow the steps below
1. Download the below files (attached with this solution)
a. Size HX from Aspen Plus.pdf
b. Shell&Tube for Interactive Sizing.bkp
2. Follow the instruction on the file ‘Size HX from Aspen Plus.pdf’. This is a guide that would take you step by step through the exercise.
By the end of this exercise you would have learnt how to convert simple heat exchanger models in your Aspen PLUS flowsheet to rigorous models without leaving the flowsheet, so as to capture savings from your process flowsheets.
Keywords: Design fin fan heat exchangers, Improve flowsheet accuracy, improve process accuracy, simple heat exchanger models, design shell and tube, design air coolers, troubleshoot operational problems, preliminary heat exchanger design, initial heat exchanger design
References: None |
Problem Statement: Potential savings on CAPEX, OPEX and Energy consumed by process plants, lost due to use of simple heat exchanger models in Aspen HYSYS flowsheets | Solution: Rigorous heat exchanger models incorporated in process flow sheets enhances the fidelity of the flowsheet enabling you to reduce CAPEX, OPEX and Energy consumed.
Aspen HYSYS enables you to specify rigorous heat exchanger models in just few clicks, from within the flowsheet.
Here we demonstrate how you can develop rigorous heat exchanger models of a Shell & Tube heat exchanger from an Aspen HYSYS Flowsheet.
Please follow the steps below
1. Download the below files (attached with this solution)
a. Specify HX Geometry in Aspen HYSYS .pdf
b. CDU_Model.zip
c. E-103_TEMA.pdf
2. Follow the instruction on the file ‘Specify HX Geometry in Aspen HYSYS .pdf’. This is a guide that would take you step by step through the exercise.
By the end of this exercise you would have learnt how to convert simple heat exchanger models in your Aspen HYSYS flowsheet to rigorous models by specifying heat exchanger geometry,without leaving the flowsheet, so as to capture savings from your process flowsheets.
Keywords: Improve flowsheet accuracy, improve process accuracy, simple heat exchanger models, design shell and tube, troubleshoot operational problems, preliminary heat exchanger design, initial heat exchanger design
References: None |
Problem Statement: Modeling Vertical Tubeside Condensers with Aspen Shell & Tube Exchanger | Solution: OBJECTIVE
The example file will enable you to setup a Vertical Tubeside Condenser rating case in the Shell & Tube Module of the EDR program and help analyze results.
PROCESS DESCRIPTION
Model a cyclohexane condensation on the tube side using cooling water on the shell side. Enable rating / checking mode to evaluate performance in a defined geometry.
GENERAL GUIDELINE
Set process data and pressure drop constraints. Select fluid components for both shell and tube sides from Aspen Properties databank. Select REFPROP property method for cyclohexane (tube side properties).
Set calculation method to rating / checking mode and input all parameters as shown in the example. Run the program.
RESULTS SUMMARY
OPTIMIZATION PATH: Offers a quick design check to confirm surface area ratio and pressure drop ratio. Confirms design status.
TEMA SHEET: Performance, design and construction details can be found in the section.
THERMAL & HYDRAULIC SUMMARY: Confirms complete condensation of cyclohexane and heat load matches between shell and tube sides. Pressure drop conditions are met as well. Distribution of pressure drop across various sections of geometry helps determine what to adjust to minimize pressure drop.
CALCULATION DETAILS: Performance along shell tube and tube side are located in separate sections. Each section details performance along the length of the heat exchanger and values for vapor fraction, film coefficients, heat flux, heat load, etc. can be depicted on a plot for easier understanding.
DESIGN CONSIDERATION: This design illustrates a vertical tubeside condenser with axial nozzles and selection of alloy tubes. TEMA type BEP construction provide versatility to this design – outside packed floating head to withstand axial thermal differential stresses between shell and tube sides either during operation or cleaning cycle, and ease of mechanical cleaning of tubes.
Keywords: EDR, Vertical Tubeside Condenser, Design, Simulation
References: None |
Problem Statement: When using the envelope utility to calculate the curve for a stream that contains hydrogen, there will be a strange shape to the envelope PT curve. The shape returns to normal if hydrogen is removed from the stream. You could see the phenomena in the Example Case file in the attached. | Solution: It is expected that the introduction of hydrogen will cause retrograde behavior at lower temperatures, where the bubble point should rapidly rise. Since the hydrogen content is so small in the case file, we do not expect a shift in the VLE region. Although the pressure rapidly increase at lower temperature, the envelope is nearly identical at higher temperature. For example, for stream G Gas Sample 2012 in the Example Case file, the bubble point curve with on hydrogen is the same as the curve with hydrogen until around -150 C, as below shown:
For more detailed information, please see the attached paper “RETROGRADE-PHENOMENA (including Hydrogen).pdf�
Keywords: Retrograde, hydrogen, envelope
References: None |
Problem Statement: How do I import the Air Cooled exchanger fan power in Spreadsheet? | Solution: Fan power for air coolers is calculated by EDR Air Cooled and available through Aspen HYSYS. To test this:
1. Load the attached case.
2. Add a spreadsheet to the flowsheet.
3. Open the spreadsheet form, select a cell and click Add Import.
4. Select the air cooler AC-100 and wait for variables to populate.
5. Scroll down to variable "xEDRr: Brake power for all fans" and select. Click OK.
6. On spreadsheet tab note the value of this variable which populates the cell.
7. To verify the number, open the form for AC-100. Go to Rigorous AirCooler tab and click model details which launches the EDR browser.
8. In the EDR browser, navigate to Results|Mechanical Summary|Exchanger data and go to Fan Details. Confirm "Total brake power (winter)" is the same as the value in step 6.
Keywords: Fan Power, Air Cooled Exchanger
References: None |
Problem Statement: Potential savings on CAPEX, OPEX and Energy consumed by process plants, lost due to use of simple heat exchanger models in Aspen Plus flowsheets | Solution: Rigorous heat exchanger models incorporated in process flow sheets enhances the fidelity of the flowsheet enabling you to reduce CAPEX, OPEX and Energy consumed.
Aspen Plus enables you to specify rigorous heat exchanger models in just few clicks, from within the flowsheet.
Here we demonstrate how you can develop rigorous heat exchanger models of
· A Shell & Tube heat exchanger and
· An Air Cooled heat exchanger
from an Aspen PlusFlowsheet.
Please follow the steps below
1. Download the below files (attached with this solution)
a. Specify HX Geometry in Aspen Plus .pdf
b. Shell&Tube for Interactive Sizing.zip
c. E-103_TEMA.pdf
d. AC-101_API.pdf
2. Follow the instruction on the file ‘Specify HX Geometry in Aspen Plus .pdf’. This is a guide that would take you step by step through the exercise.
By the end of this exercise you would have learnt how to convert simple heat exchanger models in your Aspen PLUS flowsheet to rigorous models by specifying heat exchanger geometry,without leaving the flowsheet, so as to capture savings from your process flowsheets.
Keywords: Design fin fan heat exchangers, Improve flowsheet accuracy, improve process accuracy, simple heat exchanger models, design shell and tube, design air coolers, troubleshoot operational problems, preliminary heat exchanger design, initial heat exchanger design
References: None |
Problem Statement: Equations and Example Benchmark Calculations for Two Phase Orifice Sizing and vapor noise and reaction forces | Solution: The attached PDF contains a validation with hand calculations for two phase orifice sizing and vapor noise and reaction forces inside the Safety Analysis Environment. This gives two forms of the Leung Omega Methods as implemented in the Safety Analysis Environment.
1. For cases that are saturated or two-phase at relief conditions, upstream of the relief valve.
2. For cases that are subcooled liquid upstream of the relief valve, with flashing occurring across the valve, producing a two-phase stream at the valve outlet.
This document contains:
1. Non-Subcooled Omega Method
a. Equations
b. Example with Critical Flow
c. Example with Supercritical Flow
2. Subcooled Omega Method
a. Equations
b. Example with Low Subcooling, critical flow
c. Example with Low Subcooling, subcritical flow
d. Example with High Subcooling
3. Direct Integration Method
a. Equations
b. Example
4. Noise
a. Equations
b. Example
5. Reaction Forces
a. Equations
b. Example
Keywords: PSV, PRD, Relief Sizing, Orifice Sizing, validation, whitepaper
References: None |
Problem Statement: This solution added two examples for user variables to generate overall frictional and static pressure drops in a pipe segment. | Solution: The pipe segment frictional and static pressure drops are not exposed through ActiveX. Backdoor variables are required to access these parameters in the pipe segment. To find the moniker for the correct variable the values can be copied to to Excel and pasted with the link. The link should gives the moniker for the backdoor variables to be used.
The following are the two useful links giving details of how to create and use an user variable, and information about backdoor variables.
What are user variables and how can I use them?
http://support.aspentech.com/webteamcgi/SolutionDisplay_view.cgi?key=122258
How can I access an un-wrapped variable without using a Backdoor object?
http://support.aspentech.com/webteamcgi/SolutionDisplay_view.cgi?key=108953
Follows the code for an user variable to produce overall frictional pressure drop in a pipe segment.
Sub PostExecute()
Dim hyPipeOp As Object
Dim bdPipe As BackDoor
Dim i As Long
Dim myBDVarFDP As Variant
Dim myBDVarSDP As Variant
Dim TotFDP As Double, TotSDP As Double
On Error Resume Next
Set bdPipe = activeobject
myBDVarFDP = bdPipe.BackDoorVariable(":Pressure.592.[]").Variable.Values
TotFDP = 0
For i = 0 To UBound(myBDVarFDP)
If myBDVarFDP(i) <> -32767 Then
TotFDP = TotFDP + myBDVarFDP(i)
End If
Next
activevariablewrapper.Variable = TotFDP
End Sub
The code used to calculate the static pressure drop in a pipe segment is given below.
Sub PostExecute()
Dim bdPipe As BackDoor
Dim i As Long
Dim myBDVarSDP As Variant
Dim TotSDP As Double
On Error Resume Next
Set bdPipe = activeobject
myBDVarSDP = bdPipe.BackDoorVariable(":Pressure.593.[]").Variable.Values
TotSDP = 0
For i = 0 To UBound(myBDVarSDP)
If myBDVarSDP(i) <> -32767 Then
TotSDP = TotSDP + myBDVarSDP(i)
End If
Next
activevariablewrapper.Variable = TotSDP
End Sub
The attached HYSYS file contains the above two user variables. The user variables from this simulation can be exported and saved in a file and imported from another simulation case.
Keywords: User Variable, Pipe Segment
References: None |
Problem Statement: How can I use Aspen HYSYS to model humidity in air? | Solution: In this model, we show how to compose an air mixture accurately, how to use a spreadsheet to record and dispatch process conditions, and how to calculate ambient humidity.
Air compositions are often given as volume percentage. In this model, dry air contains (by volume) 78.09% nitrogen, 20.95% oxygen, 0.93% argon, 0.039% carbon dioxide, and small amounts of other gases. Since vapor volume factions cannot be entered directly, Adjust unit operations are used to match the volume compositions.
The air pressure, ambient temperature, ambient relative humidity, and a/c outlet temperature setting are entered in spreadsheet on row 2. Ambient pressure and temperature are exported to stream sat air. An Adjust is used to manipulate the amount of water in stream ambient air to match the relative humidity given in cell C2. The a/c temperature setting goes to stream ac air. The stream office air presents the humidity indoors.
The complete model is shown below. The key streams are listed below:
sat air -- air saturated with water
ambient air -- actual outdoor air
office air -- air indoor
The model uses a Balance unit operation to pass compositions of air to dry air stream as the starting point of the model. Energy stream Q-102 is attached to V-100 so that the ambient temperature can be specified for stream sat air. while the temperature on stream dry air and water to saturate air can remain constant. The energy stream Q-100 is attached to unit X-100 so that equal temperature and equal pressure can be specified.
A relative humidity range of 30% to 60% is generally considered a comfortable condition for humans. For this reason, the a/c setting of between 65 F to 70 F gives a desirable humidity range during summer.
Keywords: air, humidity
References: None |
Problem Statement: Modeling Seal Water Heat Exchangers with Aspen Shell & Tube Exchanger | Solution: OBJECTIVE
The example file will enable you to setup a Seal Water cooler simulation case in the Shell & Tube Module of the EDR program and help analyze results.
PROCESS DESCRIPTION
Model a high-fouling seal water cooling application using tower water on the tube side. Enable simulation mode to evaluate actual performance in a defined geometry.
GENERAL GUIDELINE
Set process data and pressure drop constraints. Select water for both shell and tube sides from BJAC properties databank.
Set calculation method to simulation mode and input all parameters as shown in the example. Run the program. This method will determine outlet temperature of hot and cold side fluids for given inlet conditions.
RESULTS SUMMARY
OPTIMIZATION PATH: Offers a quick design check to confirm surface area ratio and pressure drop ratio. Confirms design status.
TEMA SHEET: Performance, design and construction details can be found in the section.
THERMAL & HYDRAULIC SUMMARY: Confirms heat load matches between shell and tube sides. Pressure drop conditions are met as well. Distribution of pressure drop across various sections of geometry helps determine what to adjust to minimize pressure drop.
CALCULATION DETAILS: Performance along shell tube and tube side are located in separate sections. Each section details performance along the length of the heat exchanger and values for vapor fraction, film coefficients, heat flux, heat load, etc. can be depicted on a plot for easier understanding.
DESIGN CONSIDERATION: High-fouling fluid has been located on the shell side. A square tube pitch has been selected in order to facilitate mechanical cleaning on the outside of tubes. An AEW style design provides the following advantages for this application: Externally sealed floating tubesheet to withstand axial thermal differential stresses between shell and tube sides and removable tube bundle which can be chemically and mechanically cleaned. This style of design is more suitable for low pressure, low temperature and non-hazardous applications. An alternate arrangement would be to locate high fouling fluids on the tube side for ease of cleaning.
Keywords: EDR, Seal Water Heat Exchanger, Design, Simulation
References: None |
Problem Statement: Modeling Lowfin Tube Heat Exchangers with Aspen Shell & Tube Exchanger | Solution: OBJECTIVE
The example file will enable you to setup a rating case with Lowfin Tubes in the Shell & Tube Module of the EDR program and help analyze results.
PROCESS DESCRIPTION
Model a compressed air cooling process on the shell side using water on the tube side. Enable rating / checking mode to evaluate performance in a defined geometry.
GENERAL GUIDELINE
Set process data and pressure drop constraints. Select Air and Water using BJAC Property package for shell and tube sides respectively.
Set calculation method to rating / checking mode and input all parameters as shown in the example. Run the program.
RESULTS SUMMARY
OPTIMIZATION PATH: Offers a quick design check to confirm surface area ratio and pressure drop ratio. Confirms design status.
TEMA SHEET: Performance, design and construction details can be found in the section.
THERMAL & HYDRAULIC SUMMARY: Confirms heat load matches between shell and tube sides. Pressure drop conditions are met as well. Distribution of pressure drop across various sections of geometry helps determine what to adjust to minimize pressure drop.
CALCULATION DETAILS: Performance along shell tube and tube side are located in separate sections. Each section details performance along the length of the heat exchanger and values for vapor fraction, film coefficients, heat flux, heat load, etc. can be depicted on a plot for easier understanding.
DESIGN CONSIDERATION: BXM design feature has been illustrated in this example. Baffles are not required for this design. Number of tube supports can be adjusted to mitigate any vibration and resonance issues. Lowfin tube geometry has been specified from the available databank. In order to meet pressure drop constraints, appropriate adjustments have been made to tube pitch.
Keywords: EDR, Lowfin Tube Heat Exchanger, Design, Simulation
References: None |
Problem Statement: Modeling Kettle Reboilers - Gas Coolers with Aspen Shell & Tube Exchanger | Solution: OBJECTIVE
The example file will enable you to setup a Kettle Reboiler rating case in the Shell & Tube Module of the EDR program and help analyze results.
PROCESS DESCRIPTION
Model a propane reboiler in a kettle shell using process gas on the tube side. Enable rating / checking mode to evaluate performance in a defined geometry.
GENERAL GUIDELINE
Set process data and pressure drop constraints. Select propane from Aspen Properties package for shell side. Choose user specified properties for the hot stream (tube side). Enter properties for hot side fluid as shown in the example file.
Set calculation method to rating / checking mode and input all parameters as shown in the example. Run the program.
RESULTS SUMMARY
OPTIMIZATION PATH: Offers a quick design check to confirm surface area ratio and pressure drop ratio. Confirms design status.
TEMA SHEET: Performance, design and construction details can be found in the section.
THERMAL & HYDRAULIC SUMMARY: Based on specified process conditions, the program will predict the amount of vaporization on the shell side and matches heat load between shell and tube sides. Pressure drop conditions are met as well. Distribution of pressure drop across various sections of geometry helps determine what to adjust to minimize pressure drop.
CALCULATION DETAILS: Performance along shell tube and tube side are located in separate sections. Each section details performance along the length of the heat exchanger and values for vapor fraction, film coefficients, heat flux, heat load, etc. can be depicted on a plot for easier understanding.
DESIGN CONSIDERATION: NKN style design incorporates a fixed tubesheet where channel is integral with tubesheet. This design is not feasible for applications with high temperature difference between the two sides. An expansion joint may become necessary in such cases. This example illustrates the use of baffle supports and resonating baffle to mitigate vibration and resonance issues. In general, a square tube pattern and/or increase tube pitch will reduce vapor blanketing around the tubes and minimize pressure drop. Critical design parameters such as Recirculation Ratio, Quality at top of the Bundle and Entrainment Fraction are reported in Results/thermal Hydraulic Summary/Flow Analysis/Thermosiphons and Kettles. More information on these important design considerations can be found in the HTFS research network. ©
Keywords: EDR, Kettle Reboiler Gas Condenser, Design, Simulation
References: None |
Problem Statement: How to import to import pressure relieving devices from the HYSYS Safety Analysis environment into Aspen Flare System Analyzer? | Solution: 1. Select File | Import Sources | Aspen Plus / HYSYS Relief Valve Sources to import pressure relieving devices from the HYSYS Safety Analysis environment. The Import Aspen Plus / HYSYS Pressure Relieving Devices window appears.
2. Click Browse to open the Aspen Plus / HYSYS File For Source Data dialog box. Select the HYSYS file (.hsc or .hscz) from which the source data will be imported and click Open to confirm the path.
Note: If you select a .hsc file, there must be an associated .mdb file with a similar name in the same directory as the HYSYS file. This .mdb file contains information about the relieving devices you wish to import. If Aspen Flare System Analyzer cannot find the associated .mdb file, an error message will appear when you click Upload HYSYS File, and the HYSYS file will not be loaded.
3. From the Component Data drop-down list, specify the action to be taken if similar components exist in the HYSYS file and the Aspen Flare System Analyzer case. Use HYSYS Components copies all the component data from HYSYS file to the current case, whereas Use Native Components does not copy the same components from the HYSYS file.
4. If you want to create a flare scenario, select the <Add New> button and type the name of the new scenario to create a new scenario, or select the Default Scenario button.
5. Click Upload File to load the source data into Aspen Flare System Analyzer. The pressure relieving devices associated with the case are imported and all the relieving devices available in HYSYS file that can be imported in Flare System Analyzer are listed.
6. Select the source to which the source data will be imported. If the source already exists, the source data will be overwritten.
7. AspenPlus/HYSYS Scenario lists the HYSYS scenarios mapped to Flare scenarios.
8. The Mass flow, pressure and Temperature column show the fluid state and these are read only values.
9. If you want to store the information mapped during your session, select the Save Import Set button. The file will be stored in the same directory as the Aspen Flare System Analyzer file. Otherwise hit Done and say No to the pop up box.
10. Check the data should be imported
Keywords:
References: None |
Problem Statement: Potential savings on CAPEX, OPEX and Energy consumed by process plants, lost due to use of simple air cooler models in Aspen HYSYS flowsheets | Solution: Rigorous air cooled heat exchanger models incorporated in process flow sheets enhances the fidelity of the flowsheet enabling you to reduce CAPEX, OPEX and Energy consumed.
Integration between Aspen EDR and Aspen HYSYS enables you to better optimize the design of air coolers, eliminate manual data transfer between the two softwares and seamlessly integrate rigorous air cooler models into Aspen HYSYS flowsheets.
This self-guided demo shows how to design an air cooler using Aspen EDR.
Additionally you would learn how to
· Import necessary data from an Aspen HYSYS model
· Find the optimal air flow for the air cooler
· Export the final air cooler model to Aspen HYSYS
Please follow the steps below
1. Download the below files (attached with this solution)
a. Air Cooler Design with Aspen EDR.pdf
b. EDR_CDU.hsc
2. Follow the instruction on the file 'Air Cooler Design with Aspen EDR.pdf'. This is a guide that would take you step by step through the exercise.
Keywords: Design fin fan heat exchangers, Improve flowsheet accuracy, improve process accuracy, simple heat exchanger models, design air coolers, troubleshoot operational problems, preliminary heat exchanger design, initial heat exchanger design
References: None |
Problem Statement: Modeling MEG Reboilers with Aspen Shell & Tube Exchanger | Solution: OBJECTIVE
The example file will enable you to setup a MEG Reboiler rating case in the Shell & Tube Module of the EDR program and help analyze results.
PROCESS DESCRIPTION
Model a MEG Reboiler (Two units connected in Parallel) using steam as heating media. Enable rating / checking mode to evaluate performance in a defined geometry.
GENERAL GUIDELINE
Set process data and pressure drop constraints. Select steam for shell side from BJAC properties databank. Tube side contains user defined properties which can be manually entered or imported from Process Simulators such as Aspen Plus and HYSYS.
Set calculation method to rating / checking mode and input all parameters as shown in the example. Run the program.
RESULTS SUMMARY
OPTIMIZATION PATH: Offers a quick design check to confirm surface area ratio and pressure drop ratio. Confirms design status.
TEMA SHEET: Performance, design and construction details can be found in the section.
THERMAL & HYDRAULIC SUMMARY: Confirms heat load matches between shell and tube sides. Pressure drop conditions are met as well. Distribution of pressure drop across various sections of geometry helps determine what to adjust to minimize pressure drop.
CALCULATION DETAILS: Performance along shell tube and tube side are located in separate sections. Each section details performance along the length of the heat exchanger and values for vapor fraction, film coefficients, heat flux, heat load, etc. can be depicted on a plot for easier understanding.
DESIGN CONSIDERATION: This design case illustrates two heat exchangers connected in parallel with minimal pressure drop on both shell and tube sides. Double segmental baffles employed in this design helps reduce pressure drop and mitigate vibration and resonance issues. The use of deresonating baffle to overcome resonance issues is captured in this design. TEMA type AES construction provide versatility to this design – floating head with backing device to withstand axial thermal differential stresses between shell and tube sides, removable bundle and ease of mechanical cleaning of tubes. One pass ‘S’ floating head construction requires a mechanism to absorb the axial thermal expansion being transmitted to the tube outlet nozzle.
Keywords: EDR, MEG Reboiler, Design, Simulation
References: None |
Problem Statement: Modeling Kettle Reboilers with Customer Specified Properties & Heat Load with Aspen Shell & Tube Exchanger | Solution: OBJECTIVE
The example file will enable you to setup a Kettle Reboiler rating case in the Shell & Tube Module of the EDR program and help analyze results.
PROCESS DESCRIPTION
Model a process reboiler in a kettle shell using low pressure steam on the tube side. Enable rating / checking mode to evaluate performance in a defined geometry.
GENERAL GUIDELINE
Set process data and pressure drop constraints. Select steam / water from BJAC property package for tube side. Choose user specified properties using heat loads for the cold stream (shell side). Enter properties for cold side fluid as shown in the example file. The program will make an assumption if liquid surface tension is not specified. The program will convert specified heat load and flow rate to specific enthalpies.
Set calculation method to rating / checking mode and input all parameters as shown in the example. Run the program.
RESULTS SUMMARY
OPTIMIZATION PATH: Offers a quick design check to confirm surface area ratio and pressure drop ratio. Confirms design status.
TEMA SHEET: Performance, design and construction details can be found in the section.
THERMAL & HYDRAULIC SUMMARY: Based on specified process conditions, the program will predict the amount of vaporization on the shell side and matches heat load between shell and tube sides. Pressure drop conditions are met as well. Distribution of pressure drop across various sections of geometry helps determine what to adjust to minimize pressure drop.
CALCULATION DETAILS: Performance along shell tube and tube side are located in separate sections. Each section details performance along the length of the heat exchanger and values for vapor fraction, film coefficients, heat flux, heat load, etc. can be depicted on a plot for easier understanding.
DESIGN CONSIDERATION: NKU style design incorporates a non-removable U-tube bundle for very clean service with very high temperature difference between the two sides. For high fouling fluids where periodic cleaning of tube bundle is necessary, a BKU style design is an ideal choice. This example illustrates the use of baffle supports and resonating baffle to mitigate vibration and resonance issues. In general, a square tube pattern and/or increase tube pitch will reduce vapor blanketing around the tubes and minimize pressure drop. Critical design parameters such as Recirculation Ratio, Quality at top of the Bundle and Entrainment Fraction are reported in Results/thermal Hydraulic Summary/Flow Analysis/Thermosiphons and Kettles. More information on these important design considerations can be found in the HTFS research network.
Keywords: EDR, Kettle Reboiler with Customer Specified Properties & Heat Load, Design, Simulation
References: None |
Problem Statement: OTS basic work flow with a Hysys model | Solution: This sample solution describes the basic work flow of creating a OTS project and test it with a OPC client. It starts from scratch, so it does not need project or model files. To carry on the exercise, one would need only a simulator, for this case, Hysys to be installed besides OTS itself. The step by step instructions and screen shots are captured in the Word file attached.
Keywords: Work Flow, Basic, sample, example
References: None |
Problem Statement: Modeling High Pressure Gas Heaters with Aspen Shell & Tube Exchanger | Solution: OBJECTIVE
The example file will enable you to setup a High Pressure Gas Heater design case in the Shell & Tube Module of the EDR program and help analyze results.
PROCESS DESCRIPTION
Model a high pressure gas heater in design mode using high temperature thermal fluid on the shell side. Enable design mode in order for the program to optimize size and cost of the unit.
GENERAL GUIDELINE
Set process data and pressure drop constraints. Note that mass flow of HP Gas is beyond the expected range of the program. This red background enables the user to answer the question “are you sure of this high flow rate?” Program will still optimize and offer designs based on specified process conditions. Select customer supplied properties and enter properties as shown in the example for both shell and tube sides.
Set calculation method to design mode and input all parameters as shown in the example. Run the program.
RESULTS SUMMARY
OPTIMIZATION PATH: The program provides numerous designs that meet process conditions. Design optimization is based on area ratio and total cost. A single large heat exchanger or several heat exchangers connected in parallel can be chosen depending on individual requirements. Any chosen design (including designs that are marked NEAR) can be transferred to rating mode of the program for further optimization.
TEMA SHEET: Performance, design and construction details can be found in the section.
THERMAL & HYDRAULIC SUMMARY: Based on specified process conditions, the program calculates mass flow rate of thermal fluid and matches heat load between shell and tube sides. Pressure drop conditions are met as well. Distribution of pressure drop across various sections of geometry helps determine what to adjust to minimize pressure drop.
CALCULATION DETAILS: Performance along shell tube and tube side are located in separate sections. Each section details performance along the length of the heat exchanger and values for vapor fraction, film coefficients, heat flux, heat load, etc. can be depicted on a plot for easier understanding.
DESIGN CONSIDERATION: TEMA type AES construction provide versatility to this design – floating head with backing device to withstand axial thermal differential stresses between shell and tube sides, removable bundle and ease of mechanical cleaning of tubes. One pass ‘S’ floating head construction requires a mechanism to absorb the axial thermal expansion being transmitted to the tube outlet nozzle. Square tube pitch bundle is easier to clean and large diameter tubes helps reduce pressure drop on the tube side.
Keywords: EDR, High Pressure Gas Heater, Design, Simulation
References: None |
Problem Statement: Modeling Gas Condensers with Aspen Shell & Tube Exchanger | Solution: OBJECTIVE
The example file will enable you to setup a Gas Mixture Partial Condenser rating case in the Shell & Tube Module of the EDR program and help analyze results.
PROCESS DESCRIPTION
Model a partial condensation of gas mixture on the tube side using ethylene glycol-water mixture on the shell side. Enable rating / checking mode to evaluate performance in a defined geometry.
GENERAL GUIDELINE
Set process data and pressure drop constraints. Enter gas stream composition and choose Aspen Properties package. Enter ethylene glycol-water composition for shell side and pick BJAC properties package. Program works coherently with different property packages for shell and tube side fluids.
Set calculation method to rating / checking mode and input all parameters as shown in the example. Run the program.
RESULTS SUMMARY
OPTIMIZATION PATH: Offers a quick design check to confirm surface area ratio and pressure drop ratio. Confirms design status.
TEMA SHEET: Performance, design and construction details can be found in the section.
THERMAL & HYDRAULIC SUMMARY: Confirms partial condensation and heat load matches between shell and tube sides. Pressure drop conditions are met as well. Distribution of pressure drop across various sections of geometry helps determine what to adjust to minimize pressure drop.
CALCULATION DETAILS: Performance along shell tube and tube side are located in separate sections. Each section details performance along the length of the heat exchanger and values for vapor fraction, film coefficients, heat flux, heat load, etc. can be depicted on a plot for easier understanding.
DESIGN CONSIDERATION: Since there are a number of components in the gas mixture, HTFS-Silver-Bell method will be used for condensation heat transfer model. Ensure that actual pressure drop is close to allowable pressure drop in order to achieve a true Vapor-Liquid Equilibrium diagram. High fouling fluids are typically located on the tube side for ease of cleaning.
Keywords: EDR, Gas Condenser, Design, Simulation
References: None |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.