question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
|---|---|
Problem Statement: Infoplus.21 Tag Configuration - Excel add-in:
Is it a part of Aspen Infoplus.21 Administrator or Aspen Process Explorer setup? | Solution: It is part of the Aspen Process Explorer setup package.
atip21config.xlam and atip21config.xla are listed in the Aspen Process Explorer package.
Keywords: Infoplus.21
IP21
Tag Configuration
Excel Add-In
References: None |
Problem Statement: How can I stop having warnings in the “Inlet piping non recoverable pressure drop”? | Solution: This kind of warning is generated during the calculations if the pressure drop in the inlet piping to a relief valve exceeds this percentage of the relief valve (set pressure). If the Gauge check box is selected, the percentage will be calculated using gauge pressure.
If you want to see the impact reflected in relief valve you need to go to the Relief Valve Editor> summary and refer to the inlet piping as you can see below:
To check which the percentage is, you need to go to the options button in the “Run Ribbon” and go to the General tab.
For example, if you have an inlet piping of 10 ft length, the results will be like the following:
And if it has also an elevation change of 5ft, it will have an effect on the piping pressure drop (recoverable) and the piping non recoverable pressure drop will be the same:
Keywords: Inlet piping, gauge
References: None |
Problem Statement: The VBA code that worked with an .fnw case no longer works with Flare System Analyzer files created with V7.3 (fnwx format). | Solution: Any VB sample code that involves opening a Flare System Analyzer case will not work for .fnwx files. This is a known behavior caused by the OpenModel procedure such as:
FlarenetApp.OpenModel ThisWorkbook.Path & "\" & filename
This procedure only works with .fnw and .fnwxml files. So, the workaround in this case is to save the case in V7.3 (or later) as .fnwxml and then the code will work ok.
Keywords: Visual Basic for applications modules load file
References: None |
Problem Statement: New Automation Methods, logs and routine for Aspen Refinery Multi-Blend Optimizer(MBO) v7.3. | Solution: Some Automation methods, logs and routine have been added in MBO in v7.3:
1. Automation errors are now logged in a file located in the AutomationErrorLogs folder found under your working directory. The name of this file corresponds to the date/time the errors occurred. In addition, the following automation methods have been added:
LaunchDlgAuditInventoriesModeless:
A new automation method has been added to OrionMBO.MBOAuto.Application that allows you to launch the Audit Inventories dialog box as modeless.
LaunchDigSupplyDemandModeless:
A new automation method has been added to OrionMBO.MBOAuto.Application that allows you to launch the Supply and Demand dialog box as modeless.
2. A routine called "Determine Application" has been added to help determine the running application.
3. "AddCase" and "DeleteCase" have been added to OrionMBO.MBOAuto. These methods allow you to add a new case based on an existing case and also to remove an existing case.
Review the MBO Help file for further details about each method.
Keywords: Automation methods
References: None |
Problem Statement: Changing the atmospheric pressure under the External Conditions section of the General tab on the Calculation Options Editor does not reflect on the gauge units. | Solution: The definition of atmospheric pressure is fixed for gauge pressure calculation. There is no option to change it in Flarenet. What you input under Options is the outlet pressure. If you simulate a pipe network, which has a different outlet pressure than 1 atm, you will specify that specific outlet pressure in this field.
As Flarenet is mainly for flare system, the name of the field is given “Atmospheric pressure” instead of “Downstream pressure” or “Outlet Pressure”.
So, when the actual atmospheric pressure is less than the hard coded atmospheric pressure, then the gauge pressure will be negative at the flare tip.
If you have your input psia data based on a different atmospheric pressure definition, you need to convert them by using standard atmospheric pressure definition.
Keywords: Artmospheric pressure, gauge, negative presssure
References: None |
Problem Statement: What is the usage of the DRU Stream option inside a material stream? | Solution: This option is applicable only for data reconciliation problems. The DRU stream is used for data reconciliation to hold different states of streams. During data reconciliation, measured data of DCS tags can be obtained under different stream states (for example, temperature or pressure). The DRU stream can also perform flash calculations as other Aspen HYSYS streams do.
The users are able to work with this through the Data Reconciliation Utility. This utility will address some issues generated in plant models which can only be configured to a specific operational instance, whereas the performance of actual equipment varies as conditions change and equipment degrades. Thus, the model behavior may start to diverge from actual plant behavior.
The DRU brings real benefits by ensuring good representation of plant equipment, and providing indications of poor plant data as an aid to decision making in the following areas:
· Identification of process unit performance, in particular condition monitoring.
· Identification and quantification of instrument errors.
This leads to improvements due to:
· Better process operation in general.
· More effective and efficient equipment maintenance and/or replacement.
· More effective and efficient instrument maintenance.
· Improved plant model representation.
Current applications of the DRU include:
· Compressor model updating/condition monitoring
· Catalyst performance monitoring/updating
· Thermal cracker model updating
· Steam system data reconciliation
· Gas turbine model parameter updating
· Heat exchanger fouling effect updating
· Reactor model parameter updating
· Boiler model updating and condition monitoring
· General network reconciliation (e.g., oil & gas fields, steam systems, etc.)
For detailed information about how to set up the utility, please refer to the PDF attached to this solution.
Keywords: DRU stream, data reconciliation utility
References: None |
Problem Statement: How does Aspen Refinery Multi-Blend Optimizer (MBO) calculate the Available Volume for a Component tank in Single Blend Optimization (SBO) dialog box? | Solution: Single Blend Optimization in Aspen Refinery Multi-Blend Optimization uses the trend limit Min and Max to calculate available volume for Component tanks. See the example below for more details:
In this case there is no variable trend limit and it is using the tank default which is 80 (TBUT tank). The available volume about 40 as seen from the trend plot:
Change the trend limits to min 20. (note that it is the absolute min and not the working min that is used to calculate the available volume:
The available volume is now 20 which is correct:
Keywords: None
References: None |
Problem Statement: We have 2 event screens in our MBO demo model: ‘Gasoline Blending’ and ‘Dist and FO Blending’. Whenever ‘Gasoline Blending’ events are published, all the information from _TANK_MBO gets replaced by ‘Gasoline Blending’ data. If 'Dist and FO Blending' events are then published, the _TANK_MBO data from 'Gasoline Blending' is replaced by the 'Dist and FO Blending' data. This is due to the design of our current version of MBO. According to the design, MBO automatically cleans up any future data before publishing. How can we retain the data that was published first? | Solution: There are two workarounds which allow the user to publish without worrying about the sequence:
1. Add all the tanks in both event screens to the control variable lists. In the first event screen, hide the tanks from the second events. Do the same for the second event screen by hiding the tanks from the first event screen. This way, whenever you publish from one event screen, you always get both sets of tank data published.
2. Create a new event screen to include all the tanks. This screen is only used to do publishing. Anyone who wants to publish always go to this screen to publish.
Keywords: None
References: None |
Problem Statement: An objective function option has been added that minimizes the deviation of blends with the same product tag. This function's purpose is to minimize operational variation of one blend to the next for the same product. The acceptable deviation penalty is user defined. | Solution: The Recipe Stabilization is new to Aspen Refinery Multi-Blend Optimizer V7.3. This feature minimizes the recipe differences among blends that belong to the same grade (product code).
The Recipe Deviation Penalty and Include Fixed Blends options have been added to the Settings dialog box Blending tab.
The Recipe deviation Penalty option allows the user to introduce penalties to minimize or stabilize blend deviations.
This insures a consistent component recipe for all blend events for that product. The fixed blend option allows you to include fixed recipe blends in your calculations.
This is accomplished through a unique optimization algorithm that allows you to control the extent of this reconciliation via a penalty factor. The default value (100) should be sufficient for most cases, although depending on the actual economics of the site a lower or higher value might be more appropriate
You should experiment with different values and also weigh the benefits of this approach. For example, you can optimize with a value of 0 (no penalty), 10 and 100 and compare the corresponding operational margins and the achieved recipe convergence. This will provide a guide on what the actual value used should be based on the importance of common recipes versus lower margins.
Below is an example to illustrate how a deviation penalty is applied:
1.-Assume product U87 has blends B1, B2, and B3, each of which uses component ALK. The blend percentages of ALK are 0.29 for B1, 0.2 for B2 and 0.3 for B3.
2.-centage average for U87 is therefore (.29 + .2 + .3)/3 or 0.27.
3.-The component percentage deviation or the total deviation from the average for this example would be:
abs(0.29-.027) + abs(0.2-0.27)+abs(0.3-0.27)
Enter a value between 0 and 1e+14. A value of 0 indicates there will be no deviation penalty. Any other value causes the component percentage deviation for all components in a blend to be multiplied by the entered deviation penalty. The entered value will be used in the optimization objective function as a penalty.
If a Recipe deviation penalty parameter is defined in the Deviation Penalty field found on the Settings dialog box "Blending" tab, the component percentage deviation would be multiplied by the deviation penalty and would be reported as the "Recipe Deviation Penalty" value in the Blend Details section of the optimization report. Recipes would then be generated where deviations are less and that are therefore closer to each other.
In addition, the Average Product Recipes section is generated.
Keywords: - Optimization Report
- Blending tab
-MBO optimization
References: None |
Problem Statement: Is it possible to launch the execution of the sheet INIT in Aspen Refinery Multi-Blend Optimizer (MBO)? | Solution: If you want to use INIT worksheet (Units.xls) to do some initial calculation, you can add a record in CONFIG table called USE_MBO_INIT value =Y, as shown:
Keywords: -CONFIG
- Units.xls
References: None |
Problem Statement: Aspen Refinery Multi-Blend Optimizer includes a new feature minimizes the recipe differences among blends that belong to the same grade (product code) called "Recipe Deviation Penalty". | Solution: Recipe Deviation Penalty is a new Aspen MBO feature that simultaneously minimizes the recipe differences among blends that belong to the same grade (product code). This is accomplished through a novel optimization algorithm that allows the user to control the extent of this reconciliation via a penalty factor. The default value (100) should be sufficient for most users, although depending on the actual economics of the site a lower or higher value might be more appropriate.
The user should experiment with different values and also weight the benefits of this approach. For example, the user can optimize with a value of 0 (no penalty), 10 and 100 and compare the corresponding operational margins and the achieved recipe convergence. This will provide a guide on what the actual value used should be based on the importance of common recipes versus lower margins.
This easily applied penalty is set in the Model Settings. The user can select to include fixed recipes in the average calculations.
The new HTML output report in MBO will report the recipe deviation impact to the recipe and the calculated average recipe for each grade.
Keywords:
References: None |
Problem Statement: Please recommend property package for Ammonia (NH3) / Water (H2O) system. | Solution: Peng-Robinson can handle simulations with ammonia. The final choice of property package, however, will depend on your specific process (i.e. other components in the simulation and conditions). The limitations on conditions for each PR are explained well in the Simulation Basis Manual - Appendix A.
In a system with small amounts of ammonia and small amounts of water (e.g. a Natural Gas Process), PR or SRK are two packages that would work well. However, one recommendation for modeling Ammonia-Water systems is to use either the Sour-PR or Sour-SRK package. These packages use the Wilson model for the liquid phase, which takes into account the ionization of NH3, and they use the Equation of State (PR or SRK) for the vapour phase. Ideally, we recommend an Activity Model when you can provide the necessary information.
When the composition of ammonia is relatively high, we recommend using Peng-Robinson with Lee-Kesler enthalpies. This model performs well for moderate non-ideal behavior below ambient conditions.
Keywords: NH3, H2O, system, Sour PR, Sour SRK
References: None |
Problem Statement: How do I resolve "Error Code: 0x42C" when installing Aspen Manufacturing Master Data Manager? | Solution: After reviewing the event viewer:
The MS DTC log file cannot be found. After ensuring that all Resource Managers coordinated by MS DTC have no in-doubt transactions, please run msdtc -resetlog to create the log file.
Run "msdtc -resetlog" in command prompt, and this will resolve the problem.
Keywords: None
References: None |
Problem Statement: When trying to import or generate an XML file with the Bulk Load Excel file (.xls) you may get the following error message:
Import XML Error: 429 -- ActiveX component can't create object
The OS is MS Windows 7 and the MS Office version is 2010.
This Knowledge Base article provides steps to resolve the above-mentioned error. | Solution: Most likely the problem is that Window 7 might be missing the MSXML4 components. Please try installing these from this link:
http://www.microsoft.com/en-us/download/details.aspx?id=15697
Keywords: installation, requirements, prerequisites
References: None |
Problem Statement: What's New in Aspen Fired Heater V7.3 - Additional correlations for gas-side heat transfer | Solution: An option to select the ESCOA or HTFS3A correlations in addition to the preexisting PFR correlation for gas-side heat transfer to high finned tubes has been added to FiredHeater for V7.3.
Keywords: ESCOA, HTFS3A, correlations, PFR correlation, gas-side heat transfer
References: None |
Problem Statement: What's New in Aspen Fired Heater V7.3 - Specification of fouling factors for tube-groups and convection banks | Solution: Tube-side and gas-side fouling factors can now be specified separately for each tube-group and convection bank. This allows the user far greater flexibility than earlier versions which were restricted to one tube-side value for each process stream and a single gas-side value for the heater. If desired, by defining appropriate tube-groups, the user can specify different fouling factors for each tube in a firebox path.
Keywords: Fouling factors, tube-groups, convection banks
References: None |
Problem Statement: Heating value in Volume Basis unit is incorrect in Aspen HYSYS V7.3. How do I correct this?
When you enter the properties page in the stream this gives the heating value in volume basis as highlighted below.
The Unit is incorrect in V7.3. The reported value is in Molar Basis (kJ/kgmole) instead of MJ/m3). | Solution: To fix the unit inconsistency for this heating value the user can remove this correlation by clicking on X as highlighted below and add this from the Gas properties by clicking on the Plus (+) symbol.
The added correlation for heating value will be correct.
Note that this inconsistency is only in V7.3. This has been fixed in V8.0 and higher versions.
Keywords: Heating Value, Unit
References: None |
Problem Statement: What's New in Aspen Air Cooled Exchanger V7.3 - Active Input Checking | Solution: Aspen Air Cooled Exchanger V7.3 now has the same input functionality as Shell and Tube and other heat exchanger programs. With each new input, all defaults are recalculated, and all inputs are rechecked. Mandatory inputs display with a blue-green background until a value is supplied. If any input value would generate a fatal error, then the background to the input shows red. Any inputs which are not used for a particular calculation type are grayed out, making the input process much simpler for new users.
Some of this functionality was available previously, but the graying out is completely new, and the calculation of defaults has been extended and improved. Warning messages have been introduced when input values which are unusual, but not sufficiently incorrect to cause a fatal error. The input checking process has in places been made more rigorous, preventing inconsistencies not checked for in previous versions. Some cases which previously ran may thus now fail, but it should be clear which missing or incorrect inputs are causing the problem.
Keywords: Input, checking, grayed out
References: None |
Problem Statement: This Knowledge Base article provides steps to add a comment to a Batch Profile Monitoring plot. | Solution: In order to add a comment to a Batch Profile Monitoring plot please follow the steps below:
1. Right click in the plot area and click Profiles... in the Context menu
2. Right click on the profile you want to add a comment to and click Profile Details...
3. Click the Comments tab
4. Right click in the Comments area and select Insert from the Context menu
5. The Comment dialog box appears. Enter a date and a comment and click OK to save it
NOTE: The Fixed Comments are stored in a selector record named GBP_FIXED_CMNTS.
6. The comment appears in the GBP_#_OF_COMMENTS history repeat area of the KPI record
Keywords: None
References: None |
Problem Statement: In SQLplus menu 'View| | Solution: Depending on the operating system you can find the MSWINSCK.OCX under the
Windows XP and 32bit machines
C:\windows\system32\
Windows 2008 , 7 and 64bit machines
c:\Windows\SysWOW64
You can register the winsock by starting a Command Prompt.
To do this
1. Go to Start and Run and enter the cmd
2. Enter the command 'regsvr32 c:\Windows\System32\mswinsck.ocx' or 'regsvr32 c:\Windows\SysWOW6\mswinsck.ocx'
If you need more information on this file or downloading you can visit the Microsoft website.
Keywords: MSWINSCK
WINSOCK
SQLPLUS
REFERENCES
References: s' you are not able to find the Microsoft Windsock control but this does not appear in the list. |
Problem Statement: What's New in Aspen Shell & Tube Exchanger V7.3 - Updated database for lowfin range internal enhancement data for Wolverine tubes | Solution: The input form for Wolverine tubes has been extended so that tubeside heat transfer and pressure drop data for any Wolverine enhanced tube type can be entered. Previously only a limited range of Wolverine tube data could be accessed from an internal databank.
Keywords: Database, lowfin, Internal enhancement data, Wolverine tubes
References: None |
Problem Statement: The subgroups for Q_XBarS21Def records are not being created when the Q_STD_SubGroup_Size is set to 1. | Solution: Set the Q_STD_SubGroup_Size to a value greater than 10 will allow the subgroups to be created. The minimum Q_STD_SubGroup_Size for Q_XBarS21Def records is 10. This requirement is due to the Standard Deviation calculation which is considered unreliable for less that 10 values.
Additional Information:
There are 4 types of Aspen Real-Time Statistical Process Control Analyzer definition records.
? Q_XBarCDef
Used for XBar, Range, CUSUM and EWMA charts that use a fairly small subgroup size.
? Q_XBarCSDef
Used for XBar, CUSUM, EWMA and Standard Deviation charts that use a larger subgroup size.
? Q_XBar21Def
Similar to Q_XbarCDef but they support EWMA Fixed Limits and support the use of MSSD for standard deviation calculations.
? Q_XBarS21Def
Similar to Q_XBarCSDef but they support EWMA Fixed Limits and support the use of MSSD for standard deviation calculations
? Q_XbarCDef and Q_Xbar21Def have a minimum Subgroup Size is 1.
? Q_XbarCSDef and Q_XbarS21Def have a minimum Subgroup Size is 10.
? The maximum subgroup size for all types of records is 31
Keywords: None
References: None |
Problem Statement: An existing falling film evaporator exchanger has a tube layout like that shown on the right below.
Specifying the shell inside diameter the tube diameter and the tube pitch running Aspen Shell & Tube Exchanger yields a pass arrangement as shown on the left.
How do I make a tube arrangement match an as-built exchanger? | Solution: Starting with Aspen Shell & Tube Exchanger V7.2, users have immense flexibility in specifying the tube layout for rating or simulation cases. The following steps illustrate how you can match the layout shown on the right with a few simple changes.
1. Go to Baffles/Supports | Baffles: Set the baffle cut to 17.6%. Set align baffle cuts with tubes to = no
2. Go to Bundle Layout | Layout Parameters and set the number of sealing strips to = 0
3. Go To Bundle Layout | Tierods/Spacers and set the number of tierods to = 8
4. Go to Bundle Layout | Layout Parameters and set Tube Layout Option = Specify Pass Details
5. Go to the Pass Details tab and set the Tube in reference location selection to = No
6. Run and review the resulting tube layout
Note: You may want to use the interactive tube layout input specifications to re-locate 4 of the tie rods to make sure they are inside the baffle edges.
Keywords: Tube Layout, Bundle Layout, Pass Details, Layout Parameters, Matching tube layouts.
References: None |
Problem Statement: What's New in Aspen Shell & Tube Exchanger V7.3 - Improved method for handling the viscosity of two liquid phases | Solution: An improved method has been incorporated for calculating the effective viscosity of two immiscible liquid phases, usually oil and water. There is a new prediction of the inversion point at which the continuous phase changes from water to oil, with the result that the oil dominant region will extend to lower oil volume fractions. This means that the effective viscosity will tend to be higher than predicted by the previous method when the oil volume fraction is between the old and new inversion point. The new HTFS method will give slightly lower effective viscosities than the old method in the water dominant region, and somewhat larger reductions in the oil dominant region. Thus the new effective viscosity can be greater or smaller than from the previous method depending on the oil volume fraction.
In addition, the HYSYS method for oil-water viscosities is now available as an option. The major difference in the HYSYS method is that the oil is assumed to be dominant for oil volume fractions above 0.5, and the water is dominant below 0.33. A weighted mean is used in the transition region.
Differences between the predictions of the three methods will generally be larger for heavy oils than for light oils.
It is also now possible to specify that the program uses the higher of the oil and water viscosities, and this is the default for condensation and falling film evaporation.
A final option is that it is possible to apply the former HTFS method (the only option in V7.2.1 and earlier).
Keywords: Improved, method, viscosity, two liquid phases
References: None |
Problem Statement: The "Load Snapshot..." menu choice in the Aspen InfoPlus.21 Administrator, which is normally available as a right-click menu choice from the icon that represents a particular InfoPlus.21 database, is not available (it is grayed out). Why is this choice not available? Note that this happens on a running InfoPlus.21 version 2006.5.x system... | Solution: Beginning with version 2006.5 of InfoPlus.21 improvements have been made to make the startup of InfoPlus.21 faster. As a result users are not allowed to load a snapshot into a running InfoPlus.21 system. Users may specify which snapshot should be loaded on the startup of the system by modifying the command line parameters for TSK_DBCLOCK in the InfoPlus.21 Manager. Two examples of that specific entry are:
SNAPSHOT="%SETCIM%\%SETCIM_GROUP_NAME%\InfoPlus.21.snp"
SNAPSHOT="%SETCIM%\ETC\InfoPlus21demo.snp"
The improved startup time and the inability to load snapshots into a running system are discussed in the version 2006.5 Aspen InfoPlus.21 Release Notes in the 'New Features for 2006.5' section:
Faster Startup After Graceful Shutdown
On startup, earlier versions of IP.21 always synchronized database-resident history repeat areas with archived data.
The amount of time required to synchronize all history repeat areas is roughly proportional to the number of history repeat areas to be synchronized. However, there can be considerable variation in the time required, especially if the history events corresponding to a history repeat area are in some older archive instead of the active archive.
Consequently, IP21 startup was reportedly very slow (i.e., 45 min) on some systems.
In order to avoid such prolonged startup times, IP21 will now skip the history synchronization if it can confirm that the earlier shutdown was graceful.
Note that with this enhancement, it is no longer possible to load a database snapshot into a running system that has history enabled. Previously, this was possible, although strongly discouraged, provided the system was not running in compliance mode.
Keywords: "Load Snapshot..."
grey
gray
References: None |
Problem Statement: What's New in Aspen Plate Fin Exchanger V7.3 - Stream Names | Solution: New input added to Input | Problem Definition | Process Data tab.
You can enter a Stream name to help you relate stream number to process fluids. The name is repeated on various other pages of input or output. When data are imported from Process Simulators, names from the simulator should be picked up automatically.
Keywords: stream, name
References: None |
Problem Statement: In Aspen Scheduling Insight Planning Board (SIPB), clicking on Problem Report icon leads to an unknown URL.
1. Click on the Problems Report icon.
2. IE pops up a new window and re-directs to an unknown URL.
The URL reported is http://np-scp/ReportServer/Pages/ReportViewer.aspx?%2fPlant+Scheduling%2fProblems&Model=PSCAP&Scenario=ACTIVE_SCHEDULE. | Solution: Problems Report need SCA (Supply Chain Analytics) support. SCA must be installed and configured.
Keywords:
References: None |
Problem Statement: Are internal state relationships perserved when MIMO is converter to FIR? | Solution: No, the internal relationship is not preserved when MIMO applications are converter to FIR. In the conversion to FIR, all state information is lost. Only the dynamic relationship between the inputs and outputs is retained.
Keywords: None
References: None |
Problem Statement: What's New in Aspen Plate Fin Exchanger V7.3 - UA Types | Solution: New input was added to Input | Program Options | Thermal Analysis |Heat Transfer/Pressure Drop tab.
The simple UA value for an exchanger is the heat load divided by the mean temperature difference between hot and cold streams. Since stream temperatures depend not only on enthalpy (heat load) but also pressure, some assumption must be made about how pressure varies between the inlet and outlet. This assumption often has little effect on the result, but can be important for two phase streams, particularly single component streams, when hot to cold temperature differences are small.
Three options are offered for pressure variation:
? with Temperature
? with Enthalpy
? Program (pressure varies with temperature when a stream is not the only one of a given type (hot or cold), but with enthalpy if it is the only hot or cold stream)
Note that the the Simple UA must be distinguished from the real (calculated) UA value for an exchanger, which is based on individual stream heat curves, not composites, and on the actual pressure variation of that stream in the exchanger, not some artificial assumption.
The first two options for Simple UA pressure variation are new in PlateFin V7.3. The third option is what was used in previous versions and in MUSE. Variation of pressure with enthalpy is the assumption behind UA values in HYSYS.
The simple UA value is important in Design calculations, which are based on the composite hot and cold stream curves used in simple UA calculations.
For Simulation and Checking calculations, the UA method is used for the composite curves which initialize the main calculation but should not affect the final result. For reference purposes, however, in addition to the real (calculated) UA value, two simple UA values are output (in the Solution Overview), one corresponding to the initial duty, and one to the final duty.
Keywords: UA types
References: None |
Problem Statement: The user is able to log on to SIPB and open a schedule, but when the user clicks on an activity an ?Error on page?message is displayed which has the following details: | Solution: To resolve this, you need to modify the SIPB application pool from "default" to "AspenAppPool" using the following steps:
1. Open IIS manager
2. Navigate to ?wpbgui_1? Note: wpbqui_1 is an example representing the Planning Board GUI.
3. Right click, select Manage Application, select Advanced Settings?
4. Select Application Pool, modify Application pool from"Default" to ?AspenAppPool?
Keywords: None
References: None |
Problem Statement: What's New in Aspen Plate Fin Exchanger V7.3 - Layer Schematic | Solution: New schematic was added to Input | Exchanger Geometry | Layer Types tab
The layer type schematic diagram is a simple representation of all layer types, showing the location of all layer elements in each type as a series of colored rectangles. It gives an accurate representation of the specified length of all layer elements, but the width of the layer types is purely schematic. The coloration is defined by stream number, as shown in the key. Distributor elements are shown by rectangles with a cross, as in the example below.
Keywords: Layer Schematic
References: None |
Problem Statement: How can I change the font size for the activity label in Aspen Scheduling Insight? | Solution: /Work-Around
The yellow pop-up label font sizes are not configurable.
The only way to have it increase, is to use the ZOOM keys within IE8 i.e. CTRL+PLUS and CTRL+MINUS. See IE short-cuts from http://support.microsoft.com/kb/306832.
Keywords: None
References: None |
Problem Statement: What's New in Aspen Plate Fin Exchanger V7.3 - Stream Numbers | Solution: New input was added to Input | Exchanger Geometry | Distributors tab.
Redistributors and intermediate distributors are identified by a distributor number, unlike main inlet and outlet distributors, which are identified by a stream number. This means that a stream can in principle have multiple redistributions.
The stream number must therefore be identified for each distributor. In simple cases with a single redistributor, the distributor number defaults to the stream number, so the distributor number and the stream number in it are the same.
Keywords: stream, number
References: None |
Problem Statement: What's New in Aspen Plate Fin Exchanger V7.3 - Results Plots | Solution: Additional tabs were added to the Results sections to allow plotting of results:
? Results | Calculation Details | Stream Details | Stream Plots
? Results | Calculation Details | Stream Details | Layer Plots
? Results | Calculation Details | Temperature and Qualities | Temperature and Qualities Plots
? Results | Calculation Details | Temperature and Qualities | Plots across Pattern
? Results | Calculation Details | Wall Temperatures | Wall Temperature Range Plots
Keywords: Results, plots
References: None |
Problem Statement: Cannot print from Aspen Scheduling Insight Planning Board (SIPB). SIPB does not create the expected .PDF files in PDFFiles folder and the SIPB interface does not return any error messages. The correct PDF driver is installed. | Solution: 1) Ensure you have downloaded the correct eDocPrintPro software and installed it.
a) Click Print Preferences and open the Destination tab.
b) Set the Destination Type to PDF.
c) Set the Saving mode to Use - no Dialog - with preset Folder and Name.
d) Ensure that the Destination folder points to SIPB and contains the following string: \wpb\PDFFiles.
e) Ensure that the If the destination file exists: field is set to Replace existing file
2) Check your registry settings.
a) Copy the contents of the folders listed below:
? HKEY_CURRENT_USER\Software\MAYComputer\eDocPrintPro\eDocPrintPro\Destination
? HKEY_CURRENT_USER\Software\MAYComputer\eDocPrintPro\eDocPrintPro\Standard
b) Paste them into the following folders:
? HKEY_LOCAL_MACHINE\SOFTWARE\MayComputer\eDocPrintPro\Def\eDocPrintPro\Destination
? HKEY_LOCAL_MACHINE\SOFTWARE\MayComputer\eDocPrintPro\Def\eDocPrintPro\Standard
3) In the PDFFile folder ensure the permission is set to "Everyone".
Keywords: None
References: None |
Problem Statement: What's New in Aspen Plate Fin Exchanger V7.3 - Export of Process and Physical Properties in a PSF format file | Solution: New input was added to Input | Program Options | Calculation Options | Calculation tab.
The PSF file contains the process and properties information in the current PlateFin case. It is created in the same directory and with the same name as the current case, but with the extension PSF instead of EDR. PSF files can be imported into any other HTFS (EDR) program, using File |Import.
Keywords: Export, Process, Physical Properties, PSF file
References: None |
Problem Statement: What is "OPB_PERF_COUNT" table and can its content be deleted safely? | Solution: The table OPB_PERF_COUNT consists of the session performance details. In PowerCenter versions prior to 8.5.1, this information is captured only if the session is enabled to collect performance data option. In PowerCenter 8.5.1 onwards, by default, the performance statistics are stored in this table.
OPB_PERF_COUNT works in conjunction with Persist run time session statistics property under Integration Service > Advanced property. By default, this is set to Normal. This means only session statistics are stored in OPB_PERF_COUNT.
If you do not need the session performance statistics data, then delete the records in the table OPB_PERF_COUNT. You can safely truncate the OPB_PERF_COUNT table.
Truncate log does not truncate the table OPB_PERF_COUNT. The historical performance measurements data would be lost. Deleting that data entirely will not corrupt anything from a workflow/session running perspective.
Keywords: Informatica
References: None |
Problem Statement: What's New in Aspen Plate Fin Exchanger V7.3 - Export of Process and Physical Properties in a MUI format file | Solution: New input was added to Input | Program Options | Calculation Options |Calculation tab.
An MUI file is the input file for the heritage MUSE program for plate-fin heat exchangers. Since PlateFin can open (import) an MUI file, generating an MUI file to input to MUSE makes it easier to cross-check the two programs and transfer data between organizations when one only has MUSE, and the other only PlateFin.
MUI files are created in the same directory and with the same name as your current case, but with the extension MUI instead of EDR.
Since PlateFin can handle more geometrically complex exchangers than MUSE, there might be inconsistencies between the PlateFin and MUSE cases. It is worthwhile checking that areas and number of layers for each stream are as expected.
MUI files can only be generated for axial flow exchanger, not crossflow exchangers.
Keywords: Export, Process, Physical Properties, MUI file
References: None |
Problem Statement: What versions of Informatica are supported with Aspen Supply Chain Connect (ASCC) V7.1? | Solution: Refer to the table below for ASCC and Informatica supported versions:
Aspen Supply Chain Connect
Informatica Note
V7.1
Informatica 8.1.1
V7.2
Informatica 8.6.1
V7.3
Informatica 8.6.1
Note: Informatica software is comprised of:
? Informatica 8.1.1
? Informatica SAP-Connect 8.1.1
? Informatica ODBC-Connect 8.1.1
? Informatica PowerCenter 8.1.1
? Informatica Workflow Manager 8.1.1
Keywords: None
References: None |
Problem Statement: Recently the ASCC V7.3 createASCCGrants_ORA script was modified because it didn?t work correctly for Oracle 10g. The change fixed the issue with Oracle 10g and above but has instead created an issue when Oracle is less than 10g.
FOR all_procedures_row IN (SELECT DISTINCT object_name FROM all_procedures WHERE owner = 'ASCCOWNER73' and object_type <> 'TRIGGER')
*
ERROR at line 6:
ORA-06550: line 6, column 110:
PL/SQL: ORA-00904: "OBJECT_TYPE": invalid identifier
ORA-06550: line 6, column 30:
PL/SQL: SQL Statement ignored
ORA-06550: line 8, column 44:
PLS-00364: loop index variable 'ALL_PROCEDURES_ROW' use is invalid
ORA-06550: line 8, column 6:
PL/SQL: Statement ignored
ORA-06550: line 9, column 47:
PLS-00364: loop index variable 'ALL_PROCEDURES_ROW' use is invalid
ORA-06550: line 9, column 6:
PL/SQL: Statement ignored | Solution: Oracle 9i or previous versions of Oracle are not supported. That?s because that OBJECT_TYPE is only available in the ALL_PROCEDURES as of Oracle 10g.
Keywords: None
References: None |
Problem Statement: What ports does IQview on a client machine use in order to communicate with IQ onlines? | Solution: IQview uses Corba/Dais Trader in order to communicate between the client and server machine. Please note that port 11002 is used by the Dais Traders services on the Client and Server machines to communicate with each other. However, the response back from IQlinksrv (Server) to IQview (Client) does not happen through a designated port. The only way to get around it is to open all ports (to/from client) in the Server firewall settings or to completely turn OFF the firewall. IQlinksrv.exe is the only corba server that AspenTech does not set a default port for. Also, there is no way to constrain iqlinksrv to a specific port.
A better workaround would be to switch to using the WCF communication protocol on all Aspen servers. This feature is available starting V7.2 of the aspenONE APC Suite.
Keywords: Corba
Dais Trader
IQview
References: None |
Problem Statement: The RTView bar or pie chart fails to display integer values queried from Aspen InfoPlus.21 through the SQL+ ODBC driver.
The same data (e.g. data obtained with the exact same query) displays successfully in other RTView dashboards (gauge,..). | Solution: The screenshot hereunder shows the default options of the SQLplus ODBC driver.
Note that the integer values are sent as characters by default. This is what the Pie chart and Bar chart controls do not support.
You can remedy the problem by UNCHECKING the ?Integers sent as Character? box and clicking OK.
As soon as the pie and bar charts receive actual integers they will start displaying the values.
Note : it may be necessary to ?re-attach? to the database in the dashboard editor to make the configuration changes effective.
Keywords: Pie chart, Bar chart, dashboard, controls, query, ODBC driver, cast
References: None |
Problem Statement: What's New in Aspen Exchanger Design and Rating Product Family V7.3 - Support for MS Windows 7 64 bit Operating System and MS Office 2010 | Solution: Aspen Exchanger Design and Rating Product Family V7.3, including Aspen Air Cooled Exchanger, Aspen Fired Heater, Aspen Plate Exchanger, Aspen Plate Fin Exchanger, Aspen Shell & Tube Exchanger and Aspen Shell & Tube Mechanical can be run on the MS Windows 7 64-bit operating system and is compatible with MS Office 2010 (32-bit version only).
Keywords: MS Windows 7, MS office 2010
References: None |
Problem Statement: It might be desirable to work with a state space model built using APC Builder in Matlab. For such situations, APC Builder allows the users to export the A, B, C, D matrices in the form of a .LSS file. However, the .LSS format is not supported in Matlab. | Solution: APC Builder does not inherently allow exporting the A, B, C, D matrices in a tab delimited format. Applying the plug-in attached to this solution adds the desired functionality to APC Builder. Please note that the plug-in will only work on a V7.3 CP4 system. Follow the instructions below to apply the plug-in-
1. Download attached zip file and extract the plug-in.
2. Copy the plug-in to the C:\Program Files (x86)\AspenTech\RTE\V7.3\APC directory on the machine where APC Builder is being used.
Once the plug-in is installed, open an APC Project, right-click an SSC model/controller application and export the A, B, C, D matrices as a CSV file.
Please note that this plug-in will not be available for APC versions other than V7.3 CP4. For other APC versions, please contact Aspen Support for a plugin 1.
Keywords: Matlab
SSC model
LSS format
References: None |
Problem Statement: I created a new crude code CON, loaded the assay, and the data looked okay. But when I load the Aspen Petroleum Scheduler (APS) simulator, it creates a crude file CON$.crd with an extra "$". Is that okay, or is CON a reserved name in APS that should be avoided for crude codes? | Solution: In Aspen Petroleum Scheduler the "CON", "PRN", and "AUX" names are all reserved and therefore a "$" will be appended. We append a "$" because the operating system (OS) may get confused if we open a file name CON.crd, since "CON" is a pretty low level reserved word for the Console. If the "$" is not added to the file name the "OS" may try to write to the Console (or printer e.g. PRN).
It's not a problem to use these reserved codes, just be aware that the "$" will be added.
Keywords: -Crude table
References: None |
Problem Statement: This Knowledge Base article shows how to create an Operations Navigator website. | Solution: You May Follow these steps to create an Operations Navigator Website
1) Go to top site (click on the first tab)
2) Select Site Actions/Create
3) Click on ?Sites and Workspaces?:
4) Then create an Ops Nav site as follows:
Keywords: None
References: None |
Problem Statement: The RTView bar or pie chart fails to display integer values queried from Aspen InfoPlus.21 through the SQL+ ODBC driver.
The same data (e.g. data obtained with the exact same query) displays successfully in other RTView dashboards (gauge,..). | Solution: The screenshot hereunder shows the default options of the SQLplus ODBC driver.
Note that the integer values are sent as characters by default. This is what the Pie chart and Bar chart controls do not support.
You can remedy the problem by UNCHECKING the ?Integers sent as Character? box and clicking OK.
As soon as the pie and bar charts receive actual integers they will start displaying the values.
Note : it may be necessary to ?re-attach? to the database in the dashboard editor to make the configuration changes effective.
Keywords: Pie chart, Bar chart, dashboard, controls, query, ODBC driver, cast
References: None |
Problem Statement: On rare occasions the "RBV Sync Tools" can encounter difficulties synchronizing Windows groups with Sharepoint groups and fails with errors like "Failed to import Domain Group into the SharePoint Group" or "The user does not exist or is not unique."
Possible causes for such problems are:
? special characters in the group names
? multiple groups with long, similar names
and it is not always an option to change the group names. | Solution: The RBV Sync Tools is provided by AspenTech to facilitate synchronizing Windows groups with Sharepoint groups. However, this operation can still be done manually in Sharepoint to help avoid the above-mentioned problems.
The enclosed document describes with screen captures the manual procedure in Microsoft Office Sharepoint Server 2007 to synchronize Windows groups and Sharepoint groups.
Keywords: Synchronize, Active Directory, Domain, MOSS, Sharepoint, 2007, groups
References: None |
Problem Statement: Could you provide scripts to convert an Aspen Petroleum Scheduler(APS) model database from MS Access to Oracle Server? | Solution: Scrips need to create Petroleum Scheduler tables in the Petroleum Scheduler database on the Oracle server (contained in the OrionOracleScripts.zip file):
1. Oracle_Create_Tables.sql: Run this script to create the necessary Aspen Petroleum Scheduler data tables in the appropriate format on the Oracle server.
2. Oracle_Drop_Tables.sql: Use this script to remove existing Aspen Petroleum Scheduler tables from the Oracle server. The column order is critical for APS; therefore, it is best to remove existing table and creating new tables when you upgrade to a new version.
3. Oracle documentation.doc
Keywords: Oracle
References: None |
Problem Statement: Is there a limit on where they start the #INPUT section of the calculation (which row can they start it at). If you go above 250 rows, it is not recognize when you run simulator. | Solution: This is right .If the first # Key word (example #INPUT) is not found by the 250th row we ignore that sheet. Also we stop processing after the 2000 row.
In summary:
The first Key Word must be within the first 250 rows and all sections must be within the first 2000 rows of the spreadsheet.
Keywords: -Excel file
-Limitations
References: None |
Problem Statement: What is the meaning of filters selections that appear on Audit Inventories dialog box? | Solution: Audit inventories dialog box has some kind of Filters as shown:
Tank-Type Filter
? All Tanks: Select this option to display all tanks.
? Process Tanks Only: Select this option to display only process tanks.
? Crude Tanks Only: Select this option to display only crude tanks.
? Empty Tanks Only: Select this option to display only tanks that are empty.
Value-Range Filter
? All Ranges : Select this option to display all values.
? In-Range Only : Select this option to display only rows that contain values that fall within the maximum and minimum limits defined in data table ORION_MGR_TNKINV_RANGE.
? Out-Range Only: Select this option to display only rows that contain values that fall outside the maximum and minimum limits defined in data table ORION_MGR_TNKINV_RANGE
? Have Plant Values :Select this option to display only rows that contain a value in the Plant Value field.
? Min/Max Out-Range:Select this option to only display rows where the values in the Min or Max fields contain values out of range.
? Delta Out-Range: Select this option to only display rows where the simulated and plant values are different.
Property Filter Drop-down list
Displays the properties that can be used to filter the information to be displayed in the value grid. Global options associated with the display of these properties are set from the Audit Inventory Options area found on the "Model Settings" tab of the Settings dialog box.
Hide Crude Composition
Only applies to crude tanks. Hides the crude tank composition values, only displays totals.
-Un-select option:
-Select option
Keywords: -Integration
-Audit Inventories
References: None |
Problem Statement: End of the 4 character limitation in the name of the streams, tanks, crudes, units, properties, etc ,in Aspen Petroleum Scheduler (APS) and Refinery Multi-Blend Optimizer (MBO) | Solution: About the feature
Prior to V7.3, tag names were limited to 4-characters. In V7.3, tag length was increased to 32-characters.
Known Exclusions
-Names of Aspen Calc functions limited to 20 characters.
-MATERIAL codes limited to 50-characters
-UNIT names limited to 31-characters
-Dialogs will allow the insertion of blanks and special characters. The addition of these characters may cause issues with APS/MBO performance.
- Tags cannot contain the following characters:
: ; <blank>" ' / \ {} [] () <> or any other special characters
Requirements
DBUpdate must be completed prior to the use of long-tags.
How to Use the Feature:
-Creating a new tag:
1. All dialogs in APS/MBO support the 32-character length. When adding a new tag, simply insert a name up to the 32-character length.
- Changing a current tag to 32-characters:
1. Launch the ATRenameTags.exe utility from the Aspen Petroleum Scheduler folder
2. Select the model type from the drop down list.
3. Locate the database and the corresponding Excel Units spreadsheet using the Browse feature.
4. Provide the user name and password (typically and ADMIN for permission to change the tables).
5. Hit ?OK?
6. Select the Tag type from the dropdown list
7. Type new Tag Name
8. Select ?OK?
9. If the TAG affects the Excel Units worksheet, the user will be able to see the changes being made to the sheet prior to performing the changes.
10. If the TAG Name is contained in the VB code, the user must manually change the VB code for the model to work.
Tip: If a long tag name appears in a grid and the tag is not entirely visible, try right clicking in the grid heading and selecting ?Hide description?. The display change for this dialog box is saved until you select ?Show Description?.
Keywords: -ATRenameTag utility
References: None |
Problem Statement: Some newly created events also appeared in the "Unmatched Events" tab under the "Existing Events" block. My understanding is that the only events that should appear in this block are those that exist in the Aspen Petroleum Scheduler (Orion) database but not in the staging table (ORION_MGR_EVENT_IMPORT). Is this a bug? | Solution: It is not a bug. Look at the check boxes at the top of the ?Unmatched Events? page.
These check boxes specify the criteria for flagging an event as unmatched.
Unmatched events are imported (staged) events and/or events for which the system could not find a match. The system automatically matches events from application database to staged events in data table ORION_MGR_EVENT_IMPORT when the following IDs match:
? Application ID (App ID)
? Movement ID
? Event Type ID
The fact that the program found a staging event matching an Aspen Petroleum Scheduler (APS) event is sufficient for placing both events to the matched grid. However, it does not prevent the same APS event from being treated as unmatched if for example the ?Invalid App ID? option is checked. When it is checked, the program considers the event unmatched if it cannot find its "App ID" in combo box ?Event Data Source?. This combo box is populated from table ORION_MGR_APPLICATION. There is a reason for such a design feature - some events may have obsolete App IDs (remnants from previous matches).
You can work around this problem by one of the following two ways:
? Add "App ID" of the event (in our case, App ID = 1) to table ORION_MGR_APPLICATION. This will inform Orion that its" App ID" is valid. This "App ID" will be added to the combo box.
or
? Clear checkbox ?Invalid App ID?. This will inform the program that you don't care if the App ID is not listed in ORION_MGR_APPLICATION.
In both cases, events with App ID = 1 will not be treated as unmatched.
Other options available under "Existing Events" window are:
? Current App ID:
Select this option to display events that have an APS application ID assigned but are not currently matched to an external system event.
? Missing App ID:
Select this option to display events that do not have application IDs assigned.
? Other Valid App ID
Select this option to display events that have application IDs other than APS that have not yet been matched to APS events.
Keywords: -Integration
- Import Events
-Staging Tables
References: None |
Problem Statement: Aspen Petroleum Scheduler (APS) and Refinery Multi-Blend Optimizer (MBO) now equipped with a new feature called "Excel Integration Utilities" that allow for quick updating of inventories, events, rundowns and assays\y data from Excel into the APS/MBO Database. | Solution: In October 2010, AspenTech implemented the Excel Integration Tools for importing inventory, event, component rundown and crude assay information directly from Excel into APS and MBO. The end users were provided a template for importing the data and the tools provided a method for validation of data before importing the data to staging or database tables. In the V7.3 release, the tools were transitioned to an Excel Add-in that was packaged with the standard installation.
Crude and Product Inventories
For importing crude beginning inventories, the user can input total tank volume along with crude compositions. For process and component inventories, total tank volume along with properties can be imported.
The user can then choose to "Audit/Load" the data which populates the staging tables allowing the use of the Audit Inventory dialog. Selecting Load Data moves the data into the database tables bypassing the auditing step.
Crude and Product Events
For Crude and Product events, the user can import any data that is contained in the events dialog including Batch Numbers, Descriptions, Start and Stop Times and Quantities.
The user will import event information into the staging tables where the Event Import dialog will be used to match imported events to existing events in the model or create new events.
Component Rundowns
Each component being imported will be handled in its own spreadsheet. Daily rundown information is imported directly from Excel into the database table COMP_RD. Component rundowns are specific to MBO.
Crude Assays
Assay tables used in PIMS can be imported directly from Excel. Mapping tables exists that allow the APS user to map PIMS crude names to APS crude names, PIMS properties to APS properties, and PIMS streams to APS streams (including splitting of streams). Whole crude properties such as API and Sulfur can be input through the interface. A new dialog was added in APS to allow the user to compare what is being imported from the spreadsheet to what currently exists in APS.
Keywords:
References: None |
Problem Statement: Is it possible to read period start and period end on a Calc Unit? | Solution: There are some Special keywords that can be using to build a logic in Calc unit (this kind of unit allow the user to define calculations internally rather than externally in the Units.xls excel file), such as:
Model Start : AtModelStart (inside Calc Unit)
Number of model days: AtModelDays
Period Length: AtPeriodLength
Period Start: AtPeriodStart
Weight Factor: AtWeightFactor
Keywords: -Calc Unit
References: None |
Problem Statement: Unable to start External Device Task on IP21 Manager with "Error advancing to the end of output file, error code=131, dwCurrentPos=$d. Please check task output log and event log"
<If you cannot view above image, please download attached PDF> | Solution: As per the error message it’s clearing indicating that OUT files are unable to write. Due to certain security policies permission would be lost on Working Folder of InfoPlus.21.
Following below steps to resolve permission issue.
1. Provide Full permission to “Everyone” on C:\ProgramData\AspenTech and to C:\ProgramData\AspenTech\InfoPlus.21\DB21\Group200 Folders.
2. Provide full permission to account which is used for IP21 Task Service on C:\ProgramData\AspenTech and to C:\ProgramData\AspenTech\InfoPlus.21\DB21\Group200 Folders.
3. Go to C:\ProgramData\AspenTech\InfoPlus.21\DB21\Group200 and delete all OUT and ERR files.
4. Open IP21 Manager and Select appropriate External Task (Ex: TSK_A_XXXX) and click on Run.
5. Once External Task are started successfully. Stop and Start Database to make sure all the required task are running successfully.
Keywords: External Task
TSK_A_
OUT
ERR
Code = 131
output
References: None |
Problem Statement: Effective Date and Expiration Date are some of the most important fields required for Aspen Plant Scheduler. Similarly, the other configured applications of Aspen SCM have different date requirements which are typically imported into the software from flat files or from other software interfaces. One of the most popular date formats for Aspen SCM is YYYYMMDD. This article explains the range of dates accepted by Aspen SCM for this date format. | Solution: When dates are imported into Aspen SCM, Format Data structures are used for storing the values in internal tables. DATETIME function is used to convert the dates into the required format. This function is configured to accept values only between the years 1980 and 2078. Any values beyond this range will be rejected by SCM.
Keywords: None
References: None |
Problem Statement: When using the FONT statement in dialogs, there are a number of parameters supplied (eg. FONT -11,0,0,0,400,0,0,0,0,1,2,1,34,MS Sans Serif). This solution explains what these parameters are. | Solution: FONT -11,0,0,0,400,0,0,0,0,1,2,1,34,MS Sans Serif
This is a common statement used in dialogs (the programming language used to configure the GUI in V7.3) to specify the font and other text attributes used in a window.
These numbers are corresponding to the attributes described in this link:
https://msdn.microsoft.com/en-us/library/windows/desktop/dd145037(v=vs.85).aspx
Keywords: FONT
Dialog
References: None |
Problem Statement: I have added some new blending Operations to this model:
ABCxyzT111
ABCxyzT222
The idea is to blend ABC to BlendT333 at Node xyzT111....At a later node (xyzT222) I would like to do the reverse operation (BlendT333 back into ABC).
I am having issues with infeasibilities and could use some insight on how to fix. | Solution: The user can use the following steps to get the "phase 1" solution:
1. Go to Model Settings
2. Go to the LP tab, select "Primal" for Optimization Algorithm, select "Yes" for Pre-solve Enabled
3. Run the model
After the model is solved, Aspen Petroleum Supply Planner (PSCP) should report infeasible solution status, that's fine, open the Optimization Log, you should see the number of infeasbilities is 3. The infeasibility is not detected during "Pre-solve". Open the solution in Solution Browser, find the infeasible rows:
Row Name St Activity Slack
BAL:BlendT333:xyzT111:Day31 ** -1 1
BAL:BlendT333:xyzT111:Day30 ** -1 1
BAL:BlendT333:xyzT111:Day29 ** -1 1
The infeasibility can be determined. There was too much CrudeOwenT713 produced but not sold or consumed.
According to XPRESS 20 reference manual "The phase 1 solution is useful because the sum of infeasibilities is minimized in the solution and the resulting set violated constraints and bound violated variables provides a clear picture of what aspect of the model is causing the infeasibility."
Keywords: -Infeasibilities
References: None |
Problem Statement: When should I lock a shift in Aspen Fleet Optimizer? | Solution: After all the modifications have been made to the Optimization and the user is satisfied with the results, the Optimization can be locked in to prevent any changes from taking place. This feature is useful when several shifts are being optimized at the same time. It would be beneficial for the user to lock in the Optimization for tonight's night shift before beginning tomorrow's day shift in order to prevent any changes to tonight's dispatch. The Resource Scheduling Optimization allows the user to prepare the delivery schedule for multiple shifts without leaving the Resource Scheduling Optimizer window.
Keywords: None
References: None |
Problem Statement: When do I use the load lock feature in Aspen Fleet Optimizer? | Solution: The Load Lock flag (check box) at the top right of the screen allows the user to manually identify expected deliveries as already delivered shipments. With this box checked, the user can click on an expected delivery using the right side mouse button and mark it delivered. Aspen Fleet Optimizer will automatically add the delivery to the inventory. If this flag is not selected, Aspen Fleet Optimizer will automatically calculate what shipments should have been marked delivered. When forecasting by inventory only, Aspen Fleet Optimizer may require the user to use Load Lock to identify delivered shipments if Aspen Fleet Optimizer is unable to judge what was delivered. The sales test flag enables and disables Aspen Fleet Optimizer's testing of sales information for out of range fluctuations.
Keywords: None
References: None |
Problem Statement: What are clusters used for in Aspen Fleet Optimizer? | Solution: A cluster is used for split shipment cases where certain customers have abnormally small tanks. A cluster is designed so that customers with small storage can be paired with customers with adequate storage and Aspen Fleet Optimizer can manage the inventory of all customers in the cluster as one. With clusters, Aspen Fleet Optimizer will first attempt to ship a full shipment to each customer. In cases when a full shipment cannot be accommodated, Aspen Fleet Optimizer will develop a full shipment and split the shipment quantities between cluster members to meet the inventory needs of each customer within the cluster.
Keywords: None
References: None |
Problem Statement: How do I delete an order in Aspen Fleet Optimizer? | Solution: In the Resource Scheduling Optimization, the user has the ability to delete a shipment from the available shipments list. The Resource Scheduling Optimization allows the user to remove a shipment from the available shipments list to keep it from being dispatched. To delete a shipment, highlight the shipment in the available shipments list then click on the green trashcan on the Resource Scheduling Optimization toolbar. A dialog box will appear confirming the deletion process.
Keywords: None
References: None |
Problem Statement: How can safety stock be used in Aspen Fleet Optimizer? | Solution: The Safety Stock refers to the functionality that allows the user to enter the amount of product by tank that the user would like to consider as “safety stock” or the absolute minimum of product that should always be kept on hand for that particular tank. Aspen Fleet Optimizer uses the greater amount (pump stop or safety stock) when deciding how much product should be left in the tank.
Keywords: None
References: None |
Problem Statement: Where can I find the values that Aspen Fleet Optimizer is forecasting for an account? | Solution: The Customer Summary Report prints the current set of information Aspen Fleet Optimizer is using to forecast product shipments for a particular customer. The Customer Summary Report is useful when processing exceptions because it also displays average sales and fluctuations from average sales. Terminal and zone specifications are required for this report.
Keywords: None
References: None |
Problem Statement: How do I disable the Dais (CORBA) related programs after migrating to WCF? | Solution: Disabling Dais (CORBA) related programs after migrating to WCF
Applies to: Aspen APC Online (v7.2 and later)
If you have upgraded APC Online to v7.2 (or later) and now use the WCF communication option with v7.2 (or later) PCWS, then you no longer need the Dais (CORBA) based communication programs to run on the Online server. Aspen recommends that you disable all Dais-related programs from starting when WCF is being used. Also, if you do not routinely use IQView or ACO Message Viewer (PCWS and APC Mange now fully replace these tools) you should disable these programs also. To disable the Dais programs from starting up, do the following:
1. Stop the "ACO Utility Server" service on the APC Online machine. This forces all Dais-related programs to stop.
2. Edit the autostartlist.txt file located in <ProgramData>\AspenTech\APC\Online\sys\etc.
3. Delete the following sections of this file and save it:
PROCNAME=DMCP_VIEWSRV
SEQNUM=20
APPPATH=$ACODROOT\bin\dmcp_viewsrv.exe
APPTYPE=1
PROCNAME=APOLLO_VIEWSRV
SEQNUM=21
APPPATH=$ACODROOT\bin\apollo_viewsrv.exe
APPTYPE=1
PROCNAME=IQ_VIEWSRV
SEQNUM=21
APPPATH=$ACODROOT\bin\iq_viewsrv.exe
APPTYPE=1
PROCNAME=IQLINKSRV
SEQNUM=80
STDOUT=nul
STDERR=nul
APPPATH=$ACODROOT\bin\iqlinksrv.exe
APPTYPE=1
PROCNAME=ACOMSGSRV
SEQNUM=90
STDOUT=nul
STDERR=nul
APPPATH=$ACODROOT\bin\acomsgsrv.exe
APPTYPE=1
4. Start the "ACO Utility Server" service. Now, you should no longer see the following processes:
Apollo_viewsrv.exe, dmcp_viewsrv.exe, iq_viewsrv.exe, iqlinksrv.exe, acomsgsrv.exe
Important Note: The autostartlist.txt file can be updated any time without stopping the "ACO Utility Server" service. The changes to the autostartlist.txt file would however only take effect when the "ACO Utility Server" is restarted. In case you did not restart the "ACO Utility Server" service after the autostartlist.txt file is updated, the revisions to the autostartlist.txt file will take effect when you reboot the machine (which indirectly restarts the "ACO Utility Server" service).
Keywords: None
References: None |
Problem Statement: What are other additions used for in the Data Quality Manager Aspen Fleet Optimizer? | Solution: Other Additions is a way to add or subtract product to help in the reconciliation of an exception. These values include unexpected or undocumented additional shipments of product to the customer. When a retain occurs or a customer receives an unexpected shipment, the quantities of product dropped must be logged here. This value may also be negative if product has been removed from a tank through means other than sales.
Keywords: None
References: None |
Problem Statement: Where can I find what values were called in two days ago in Aspen Fleet Optimizer? | Solution: The Inventory Forecasted Sales Report by Runout prints a customer's inventory and forecasted sales for a particular day sorted by runout. The Inventory Forecasted Sales Report can be printed by customer, group, or terminal number.
Keywords: None
References: None |
Problem Statement: What are expected sales in Aspen Fleet Optimizer? | Solution: Expected Sales represent Aspen Fleet Optimizer’s’ calculated estimate of sales for the previous 24 hour period. Expected Sales are compared with actual reported sales to identify erroneous sales reported by the customer. As a backup, Aspen Fleet Optimizer will utilize average sales as expected sales if the historical sales information is not available.
Keywords: None
References: None |
Problem Statement: PIMS??????SO?A?>?i?Q?I?C???X?g?[??Ze???????E?I?R?s?[??Zg?p???A?a?????U???B
?g?[?N?????C?Z???X??Zg?p???A???e?e???I???ESLM Server?I?C???X?g?[?????Y?e?????A???-?K?v??? ?e?U???B | Solution: ?Y?t?IPDF?t?@?C?????_?E?????[?h???A?-???????B
Keywords: JP-
References: None |
Problem Statement: ?l?b?g???[?N???C?Z???X???eZz?I?E???[?J??PC?E?U?????AZg?p???e?u?@
?l?b?g???[?N???C?Z???X???I?iZz?l?b?g???[?N?E?U`????A???C?Z???X?T?[?o?[???c???C?Z???X??Z??????U???B???????ASO?o?????l?b?g???[?N?E?U`????SLM Commute?c?[????Zg?p???e?????E???e?A?eZz?I?E???C?Z???X???m?[?gPC???E?U?????e?I?I?t???C????Zg?p??? | Solution: Aspen PIMS V7.3 ???ISLM Commute?c?[???IZg?p?u?@?????O?_???U?????U???B
PDF?h?L???????g???_?E?????[?h???A?-???????B
Keywords: SLM Commute
JP-
References: None |
Problem Statement: Why does the message "DBCLOCK Failing - IP21SLMCheckoutLicenseMulti failed - serverLicenseType = *SLM_InfoPlus21_Points* - ret = -5009" appear in the TSK_DBClock Error log? | Solution: TSK_DBclock in the InfoPlus.21 Manager will monitor the connection to the license server or Dongle and will return a license state to the task. This will check every 5 minutes however time can vary depending on conditions below.
There are a few conditions that may cause this message.
1. No connection to license server or Dongle removed.
2. Poor connection to license server such as high ping and lag.
3. License Expiration
4. License Server or License Service restarted while Tsk_Dbclock checking status.
This issue does not occur in V8 or newer versions as the licensing model is different.
Keywords: SLM_InfoPlus21_Points
TSK_DBClock
-5009
IP21SLMCheckoutLicenseMulti failed
References: None |
Problem Statement: Where is the "Create MpsBcd Database Tables" setting in V7.3? | Solution: This and some other database related settings have been moved. In V7.3 this is now located under MODEL SETTINGS | General | Output Database tab, and then click on OPTIONS.
Keywords: mpsbcd
database
output
References: None |
Problem Statement: ?g?[?N?????C?Z???X?E?K?v?E???C?Z???X?T?[?o?[?I?C???X?g?[??Ze?????Y?e?u?@?????E?I?R?s?[??Zg?p???A?a?????U???B | Solution: ?Y?t?IPDF?t?@?C?????_?E?????[?h???A?-???????B
Keywords: JP-
References: None |
Problem Statement: When requesting Historical Values, Calculated Value, Calculated Values in the Excel COM add-in, receive the "Invalid History Request". | Solution: This error only displays when using a client V7.3 system with the COM add-in loaded, and the IP.21 server machine is at a version level less than V7.3.
Customers using client V7.3 and server V7.3 machines will not experience this problem.
For the customers experiencing this problem, they will need to add a map record when requesting Historical Values, Calculated Value, and Calculated Values. The reason for this issue is that Current value and History Value use attribute request to get values, while Historical Values, Calculated Value, and Calculated Values use history request to get values. History requests in versions prior to V7.3 require a map record.
Keywords: Invalid History Request
COM
add-in
Excel
References: None |
Problem Statement: DA (Setcim's Distributed Applications software), as described in the DA | Solution: The following must be present and/or running and/or licensed on the SERVER side:
VAX/VMS Platform:
1. DA and UCX (or TCPWARE) software must be installed
2. A valid DA license must be present on the system; run UPDATELICENSE to verify
3. DA version must be the same as Setcim version, e.g. DA v4.8 when Setcim v4.8 is installed; check INSTALL.LOG file to make sure correct version of DA server is installed for the version of Setcim you are running
4. TSK_RPC_XXX (where XXX = group#) must be running; check the list of running tasks to verify; if the task is not running, check the error and output files for clues
5. DA server process (SETCIMRPC_SERVER.EXE in the SETCIMCODE directory) must be running; check if DA server process is listed in the setcim.run file
6. The portmapper must be running on the Setcim server; check if the portmapper process is listed in the setcim.run file
7. Make sure your database is running (run a simple SELECT SQLplus query to see if you can retrieve current data values)
UNIX Platform:
1. DA server process (SETCIMRPC_SERVER.EXE in the SETCIMCODE directory) must be running; if it's not, then you must log in as a superuser and execute the command # $SETCIMCODE/setcimrpc_server NOTE: This setcimrpc_server program detaches itself from the terminal and becomes a daemon process. It listens for any request from DA client programs. The setcimrpc_server daemon handles any request for all Setcim groups. There is no similar function for the VMS versions of DA.
2. Make sure your database is running (run a simple SELECT SQLplus query to see if you can retrieve current data values)
The following must be present and/or running and/or licensed on the CLIENT side:
NOTE: Process Explorer can be installed on PC's running any of the following operating systems: Win95 SR2, Win98, WinNT 4.0 Workstation.
1. Process Explorer must be properly installed, licensed, and configured; see Aspen Process Explorer Installation Manual for details
2. A data source must be configured on each client PC, to connect to the correct server; check the Configure Servers dialog box to verify the spelling of the node name; also, input the full path for the node name (for instance prince.hou.aspentech.com instead of prince)
3. Both Noblenet portmapper and Remote Procedure Call (RPC) services must be running on the client (click Start | Settings | Control Panel | Services to verify); restart both services if not running
NOTE to Process Explorer v3.x Users.
Aspen License Manager (ALM) with current license information, Aspen Data Source Architecture (ADSA), and AFW Local Security server must be installed, configured and running for Aspen Process Explorer v3.x to be able to connect to Setcim. Please see Aspen Process Explorer 3.x Installation Manual for step by step installation instructions.
If all of the above are in place and appear to be correct, ensure that your network is up:
1. Check physical network connections to make sure they are secure and firmly in place
2. Make sure that you can ping the server from the client and vice versa
3. Make sure you can successfully run NSLOOKUP on the network
4. Add server IP address to the client's Hosts file
5. Check with your IS department if there have been any intermittent network problems and/or disruptions, which might lead to the "Data server not responding" error
Troubleshooting questions and scenarios:
1. Has it worked before? If so, what happened between the time it worked and the time it stopped working? Has anything changed on the network? Has any new software been installed on the client or the server?
2. Is the problem confined to one client only or are all of them affected?
3. Is the network up? Is the Setcim database running? Make sure you can ping the server from the client and vice versa as described above
4. Do you have a Map record configured in the database for the definition record of the tag you are trying to see in Process Explorer?
5. On the client PC, click on Start | Settings | ControlPanel | System | Environment and add an environment variable called SETCIMRPC_LOG and point it to a file called SETCIMRPC.LOG in a directory structure something like: [drive]:\Aspentech\Desktop\Setcim (depending on your PC setup).
Reboot the PC so that it reads the environment variable. Attempt to make a connection and then capture and examine the LOG file.
6. If running TGV Multinet, make sure the name of the portmapper's .init file is RPC_PORTMAP.INIT; Check the configuration of the portmapper service
7. If connecting PE v3.x to Setcim; verify that the AFW Local Security and ADSA server is running on the network and it can be seen by the node Process Explorer is running on
KeyWords:
Data server not responding
Dataserver not responding
Keywords: None
References: Manual for Setcim version 4.8, provides the ability to create client/server Setcim applications using the current Setcim API, known as Setcim Access Routines. DA allows user-written applications to access multiple Setcim databases from any node on the network. It also enables client applications to access Setcim databases on any platform (i.e., HP/UX, AIX, VMS). Currently, DA supports clients on VMS, HP/UX, AIX and Windows NT/95 platforms.
There may be a multitude of reasons why a client PC won't connect to the Setcim database. The most common error message returned by the client in this situation is: Data server not responding.
This solution is a compilation of possible reasons for the above error message. |
Problem Statement: Which Aspen Manufacturing Suite cumulative patches must be applied to allow the Aspen Process Explorer V7.3 Client using the Excel Add-Ins to be compatible with Aspen InfoPlus.21 Server V7.2 (or earlier)? | Solution: 1. AspenTech always advises you check our support website and check the patches section for the latest relevant patches.
At the time of this solution release the relevant patches are:
? Apply First: Solution ID 134755: Aspen Process Explorer V7.3 Cumulative Patch V7.3.0.3a
? Apply Second: Solution ID 134751: Aspen Process Data V7.3 Cumulative Patch V7.3.0.2a
? Apply Third: Solution ID 134359: Aspen Process Data V7.3 ER DT050812D.WIN (July 2012)
2. Then proceed to complete your required ADSA Data Source configuration using one of the options below:
? Once the three patches listed above are applied, try connecting to the IP.21 Servers and using the Excel Add-Ins by utilizing the existing Public ADSA Data Sources already configured on your V7.2 or prior ADSA Server.
NOTE: If the above option does not work, then you will need to use one of the remaining 2 options below.
? Either install a ADSA V7.3 Server and create a V7.3 Public Data Source the V7.3 Client(s) can use.
? Or simply Build a V7.3 User Data Source on the client's machine and uncheck the "Use Public Data Sources" check box so that the machine uses that User Data Source locally and does not reference the Data Sources configured on the V7.2 or prior ADSA Directory Server.
NOTE: If there will only be a few V7.3 clients needing to connect to the older IP.21 Servers, then Support recommends using the third option listed above if using the existing V7.2 or prior ADSA Data Sources does not work. If there will be many V7.3 clients then it will be faster and much more efficient to install and configure a V7.3 ADSA Server for the V7.3 Clients as needed.
** For added Troubleshooting, please refer to the Solution IDs listed below: **
134263: What are the post Installation changes required for V7.3 Excel Process Data Add-In functionality?
132305: How do I add ribbon-based Excel Add-Ins to spreadsheets?
134714: APEX V7.3 Excel add-in does not load after upgrading from MS Office 2003 to MS Office 2007/2010
134243: Installing AspenTech.PME.ExcelAddin.ProcessData produces "not a valid Office Add-in" error message
Keywords: Backwards Compatibility, COM Add-In, Excel Add-In, Patch, Process Data
References: None |
Problem Statement: How do I perform blending on a different basis than volume or weight?
In this case, it is desired to blend a property on an energy basis rather than by weight or volume - specifically the bio energy content (BEC, %). Aspen PIMS does not have an automatic means of doing this, so how can it be modeled? | Solution: Property Calculation Formula in conjunction with ABML can be used to accomplish this goal.
Heating Value (MJ/kg) can be blended linearly by mass:
Bio energy content (%) blends linearly by energy
• Subscripts
1: Bio blending component
2: Mineral blending component
b: Blended bio diesel product
Table BLNPROP
Define a new property called bio heating value:
Bio heating value (MJ/kg) also blends linearly by mass:
• Table WSPECS
Properties HTV and BHV
Define Property Formula Calculation as follows:
• Table ABML
• Table PGUESS
· BHV and HTV in blended bio diesel products
• Table BLNSPEC
· As appropriate
This article was contributed by Jørgen Fogh of Statoil.
Keywords: None
References: None |
Problem Statement: How do I disable Results.MDB | Solution: You can not, but you can reduce the content
Keywords:
References: None |
Problem Statement: How do I configure the SubModelCalculator (SMC) in Aspen PIMS for Aspen Petroleum Scheduler (APS)? | Solution: Let us look at the APS side first to see what the requirement is. We will use a configured SMC in APS as example.
Color Blue: APS Inputs
Feed in Volume/Weight
Feed properties from Erows (typically from base-delta models control rows)
Needed to be mapped to APS inputs
Color Green: APS Outputs
Propducts in Volume/Weight
Recursed properties for products from Rprp rows (prp as property)
Map them to APS outputs
Color Red: unknown variables
Those variables will use SMC model equations to solve. In this submodel SNHT, there are total 6 variables in red, therefore the model needs 6 equations to solve. Under column ‘USE’, the value ‘1’ indicates that equation is to be used in the matrix for inversion calculation.
In PIMS, you will configure SMC model into square case based on your APS model configuration.
Color Magenta (or Pink)
Those are the placeholder (999 or -999) which are not resolved due to no references are defined in the system
Now, take a look the same SMC from PIMS submodel calculator. We need to make sure the model is square by checking,
number of Cols = number of Rows
The first step is to identify the non-feed columns, then decide how many equations are needed to solve them. In this model there are 6 non-feed columns: 4 of them are related to base-delta model, 2 of them are pool columns.
- Column BAS needs ECHG row (1 row)
- Each base-delta shift column needs a corresponding E property row (3 rows)
- Recursed pool column needs RBAL row (2 rows)
Keywords: submodel
SMC
References: None |
Problem Statement: How do I prevent a Visual Fortran error during model execution? | Solution: This has been seen on some machines that have installed anti-virus software - for example, Symantec Endpoint Protection. Sometimes, the anti-virus software blocks access to a temporary file that is used for a Visual Fortran module by PIMS. The solution is de-activate the anti-virus software. It is usually possible to except some specific folders from the scan list or stop "on-access" scanning of PIMS models files. Instead you can set the scanning of model files for a specific time each day that is outside working hours and won't interfere with PIMS runs. Work with your system administrator to see which options are available for you.
Keywords: Runtime Error, Visual fortran, antivirus, incompatibility
References: None |
Problem Statement: Microsoft SQL Server installation fails when installed after aspenONE products.
Some Microsoft SQL Server components are installed along with several AspenTech products. Including: Aspen PIMS, Aspen InfoPlus.21, Aspen Operations Reconciliation and Accounting, Aspen Tank and Operations Manager, Aspen Reporting Framework, Aspen Petroleum Scheduler. One of the components "Microsoft SQL Server Native Client" causes the Microsoft SQL Server installation to fail with the following error.
Microsoft SQL Server xxxx setup: The following error has occurred:
A network error occurred while attempting to read from the file:
[install-device-name?and-root-of-path-here]\x64\setup\x64\sqlncli[1].msi | Solution: 1. Go to Program and Features.
2. Uninstall Microsoft SQL Server Native Client.
3. Install Microsoft SQL Server.
Note: Microsoft SQL Server Native Client will be reinstalled along with SQL Server.
Keywords: Express, SQL, installation, order
References: None |
Problem Statement: How do I turn off the Aspen HYSYS "Start Page"? | Solution: If you have low memory or memory management issues to load Aspen HYSYS or Refsys case, The Start Page must be turned off. Navigate to Tools on the menu bar and select Preferences.
Navigate to the ?Start Page? tab in Preferences views. It is the last tab. Uncheck the ?Show Start Page? box.
Exit and restart HYSYS.
Keywords: Start page, preference, HYSYS, Refsys
References: None |
Problem Statement: This knowledge base article describes how to resolve the following error on computers which previously ran legacy Hyprotech products.
Unable to acquire Aspen <license key name> | Solution: When this error is returned on computers that previously ran legacy/heritage Hyprotech products the root cause is that the LSHOST environment variable is set. This environment variable was widely used for heritage Hyprotech products. This environment variable overrides any values set in the SLM Configuration Wizard for the SLM license server.
To remove or edit the data associated with LSHOSTS variable, follow these steps:
1.Click Start | Control Panel, and select System. \
2. In the System Properties window, select the Advanced tab or Advanced System Settings.
3. Click on the Environment Variables button. Or click Start and right click Computer. Select Properties and select the Advanced tab or Advanced System Settings.
4. Locate LSHOST in either the User or System variables list. Then do only one of the two following options.
a.) If you are certain that you will not need the variable, highlight LSHOST, then click on the Delete button.
b.) If you are not certain whether you will need LSHOST for some other application, highlight LSHOST, then click edit. Change the name of the variable to #LSHOST.
Important: If this causes any other SLM based application to stop working, you will need to go back and change the name back to LSHOST, and then edit the value. Add the name of your license server, followed by a semi colon. In other words, if the value was:
licserver
and your current license server is newlicserver, then the new value for LSHOST will be:
newlicserver;licserver
Keywords: heritage Hyprotech
LSHOST
SLM
license manager
license error
Environment variable
References: None |
Problem Statement: Is it possible to commute licenses from an SLM server on a virtual machine? | Solution: Licenses can be commuted from a network license installed on a virtual license server. Be advised that virtual servers require dongle-free license files. A request for a dongle-free license file can be made on the Aspen Tech support website (http://support.aspentech.com/) by selecting ?Upgrades, Media & Licenses". A special lock code, specific to the server where the license file will be installed will need to be generated. Instructions for this procedure can be found on the support website and also in the cross-referenced knowledge base articles.
KeyWords
SLM
commuting
commute
VMWare
virtual machine
Keywords: None
References: None |
Problem Statement: How can I manually restart the Sentinel RMS License Manager from a DOS prompt? | Solution: To start the Sentinel RMS License Manager service from a command prompt, type this command:
net start 'Sentinel RMS License Manager'
To stop the Sentinel RMS License Manager service from a command prompt, type this command:
net stop 'Sentinel RMS License Manager'
Keywords: Sentinel RMS License Manager, service, command
References: None |
Problem Statement: In the Installation Guide for Aspen InfoPlus.21 V7.3, Internet Explorer 7 or Internet Explorer 8 are listed as a requirement for web-based applications, but it doesn't specifically say that any other web browser is not supported. | Solution: Aspen IP.21 Process Browser (formerly Web.21) V7.3 and earlier versions are neither tested on nor supported on browsers other than the Internet Explorer versions listed in the Aspen version specific documentation.
Keywords: Mozilla Firefox
Google Chrome
IE7
IE8
Safari
Opera
References: None |
Problem Statement: How do I delete workspaces in HYSYS V7.3? | Solution: In HYSYS V7.3, user can save the current window layout as a workspace (Window | Save Workspace), however, there is no delete button to remove it. The workspace is automatically saved in this HYSYS file rather than saved in a separate file in the installation folder.
The current workaround is to save the file as "*.XML" and reload it again. The workspace is not saved in XML, hence the Workspace area is refreshed.
Keywords: Workspace, Delete
References: None |
Problem Statement: This knowledge base article describes how to troubleshoot the error message:
This error may be accompanied by the error "Not licensed for Upstream Option" when attempting to add an upstream operation. | Solution: This error can occur if there are no available licenses or tokens on the Aspen SLM License Server, especially if only certain users experience the license error message while other users are able to use the product without errors.
The Aspen SLM Profiler can help you determine if all tokens are in use.
To check if the token limit has been reached do the following:
1. Open the Aspen SLM Profiler located at C:\Program Files\AspenTech\Common Files
2. Click on the drop down arrow to select the license server or keep the default to find the license file locally.
3. Click on the browse button to find the license file locally
4. Next, click on the ?Load Information? button
5. Then, click on the ?View Licenses? button
6. Highlight the SLM_Pool and compare the columns. Add Licenses Issued and Licenses Commuted columns and then compare it to the # of Licenses column. If the total is equal to the # of Licenses column then all the tokens are getting consumed.
Keywords: License error, SLM Tool, SLM Profiler, RN_PML_HYSUPSTRM_R3, WLMADMIN, and Aspen HYSYS
Unable to acquire RN_PML_HYSUPSTRM_R3 license
References: None |
Problem Statement: User receives an error message while commuting a license feature. Even though user has configured your SLM Configuration wizard with correct License Server IP address but yet user receive an error stating that "You are about to commute a license from Server = "System-name" to Machine = "IP Address".
As illustrated in below error message: | Solution: This issue would occur if client machine fails to resolve the Hostname to IP address of License Server. There could be some issue on DNS server. This issue will occur if you have configured your SLM Configuration wizard with IP address and DNS server is unable to resolve it to correct Hostname of License server.
To resolve this issue, you may configure your SLM configuration Wizard with License Server "Hostname".
1. Go to Start > All Programs > AspenTech > Common Utilities > SLM Configuration Wizard. Run this Configuration Wizard.
            Â
2. On the Welcome page: Will you be connecting to an SLM server over the network? Select “Yes� and Next
3. Type Server PC Full Computer Name or IP address of the server into the server row and click “Add�. Tick on “Search Configured Servers for all available buckets at run time� and then Next.
              Click “Next� and “Yes� for advanced settings.
Â
            Â
4. Scroll through the set up with “Next� till “Network Broadcasting� which should be unchecked.
             Â
5. Check on the “Register and optimize� license type usage in registry settings and then “next’ to finish the configuration.
6. Click “Finish� to exit the Configuration Wizard.
Keywords: Same Machine
SLM
Commute
References: None |
Problem Statement: Is there a quick way to see whether SLM Tools version 7.3 or 8.4 is installed? | Solution: Check the version of the SLM client DLL STRGXI2.dll located in folder "C:\Program Files\Common Files\Hyprotech\Shared" or in folder "C:\Program Files (x86)\Common Files\Hyprotech\Shared". The 0 before the build number (2010.0.0.291) indicates 7.3, while 1 (2010.0.1.291) indicates 8.4.
Keywords:
References: None |
Problem Statement: SLMcommute utility takes up huge memory resources in the background processes. | Solution: The SLM Commute should not be run under Remote Desktop or Terminal Server method, such as Citrix environment.
Keywords: SLM, Commute, Memory Resources, Remote Desktop, Citrix, Terminal Server
References: None |
Problem Statement: What is the purpose of "no-net" on the list of configured SLM Servers in the SLM Configuration Wizard? | Solution: The "no-net" entry is required for commuting to work properly when a license is checked out from non-default bucket using the SLM Commute tool. For example, bucket 2 in the screenshot below:
Notice that the "no-net" entry is automatically added to the list of Configured Servers in the SLM Configuration Wizard tool after the license is commuted from a non-default license bucket.
Keywords: Commuting
Bucket
no-net
References: None |
Problem Statement: Prelude:
This tutorial provides an example to educate users as of how to configure the Data Viewer to display a custom table and how to include it in the Navigation Pane in Aspen Plant Scheduler. There are no particular pre-requisites required for reading this document; though, prior working experience in Aspen SCM will aid in easier understanding. The version used in this tutorial is Aspen SCM v7.3.
Reasons for using the Data Viewer:
i. All tables can be viewed by entering the appropriate table name in the command window or through the catalog. But the user is not expected to know all the name of the table names; hence the tables that need to be presented to the user should be presented through the Data Viewer and through entries in the Navigation Pane.
ii. The Data Viewer infrastructure can be used to provide a user interface to any tabular data (model inputs or outputs). It can be configured to allow viewing of the same tabular data using different display types e.g. Data list, Bar Graph etc. Each of these views can also be filtered using the Advanced Filters. These features are extremely useful for the users to quickly view and interpret data.
iii. Data Viewer can be configured to allow the user to make (Add/Edit/Replace/Delete) updates to the tabular data. Alternately data views can also be setup as view only.
iv. Data viewer configuration settings also allow specification of custom routines to handle various user generated events on the Data Viewer interface. | Solution: Steps to include a custom table in the Navigation Pane and view it in the Data Viewer:
i. The following table contains the total projected demand data of a certain product. This document details the configuration steps required to configure the Data Viewer user interface for this data. The first column indicates the Month, the second column the Year and the third column the Demand information. The objective is to include this custom table in the Navigation Pane and view it using the Data Viewer.
_MONTH
_YEAR
$ENTRY
JAN
2013
1800
FEB
2013
1500
MAR
2013
1100
APR
2013
900
MAY
2013
1100
JUN
2013
1600
JUL
2013
1800
AUG
2013
1600
SEP
2013
1500
OCT
2013
1100
NOV
2013
900
DEC
2013
1100
JAN
2014
1500
FEB
2014
1100
MAR
2014
900
APR
2014
1100
MAY
2014
1600
JUN
2014
1800
JUL
2014
1500
AUG
2014
1800
SEP
2014
1100
OCT
2014
900
NOV
2014
1100
DEC
2014
1600
ii. Go to Start | All Programs | AspenTech | Aspen Supply Chain Suite | Aspen SCM. This will open the Aspen SCM application. Go to File | Open | C:\Users\Public\Documents\AspenTech\Aspen CAPS\Plant Scheduler\PS_V7-3-1.cas; Go to File | Save As and browse to the desired location for the file to Save in and enter a desired File name.
iii. If you get a CASE DEPENDENT error: In Command Window (press F3 for the Command Bar or go to View | Command Line Toolbar for the Command Window to appear): $TCASES; Change path before all the .casx (64-bit Aspen SCM stores files with .casx extension) / .cas extensions to C:\Program Files (x86)\AspenTech\Aspen CAPs\Shared Libraries for 64-bit machines and to C:\Program Files\AspenTech\Aspen CAPs\Shared Libraries for 32-bit machines.
iv. Go to Catalog in the Main toolbar. Type in _IMPODER in the Name text box and click on New. Make sure that it is selected as a Set and click on OK. In the Set Attributes window, there are no changes required; as a good implementation practice, the title of this set can be named as `Row Set - _IMPODE?, since this set is later going to be referenced to _IMPODE table as its Row Set. In Command Bar: _IMPODER; enter 1 through 24 in the code column. The description can be anything.
v. Go to Catalog in the Main toolbar. Type in _IMPODEC in the Name text box and click on New. Make sure that it is selected as a Set and click on OK. In the Set Attributes window, there are no changes required; as a good implementation practice, the title of this set can be named as `Column Set - _IMPODE?, since this set is later going to be referenced to _IMPODE table as its Column Set. In Command Bar: _IMPODEC; enter _MONTH, _YEAR and $ENTRY in the code column. The description can be anything.
vi. Again go to Catalog in the Main toolbar, enter _IMPODE and click New. This time, make sure that you click on Table and click OK. This is the table the data from the text file is going to be imported into. In the Table Attributes windows: Give an appropriate title in the `Title? text box; In the Rowset, enter _IMPODER; In the Colset, enter _IMPODEC. By this way you are making the previously created sets as the row and column headers of this table. The format of the table should be C8 (this indicates that characters up to 8 digits can be imported into this table), since the text file contains characters. In Command Bar: _IMPODE; copy the contents from the above table or try importing it from a text file as described in the Solution: 135230 ? `Steps to Import Data into Aspen SCM?.
vii. In the Command Bar type: DVTABLES; in a new row enter _IMPODE in the Code section and DEMAND EXAMPLE in the Description section. This introduces the new table to the list of the Data Viewer items.
viii. In the Command Bar type: DVCTL; go to the _IMPODE row: type MD in the TABTYPE column, since _IMPODE is multi-dimensional; type _IMPODE in TABLE column; type NUM in TABFMT column, since the $ENTRY values are going to be numerical; type VTALL in the VTSET column, so that _IMPODE can be looked in different formats including Table, Data List, Line Graph, Bar Graph, Stacked Bar Graph, Are Graph, Table & Line Graph, Table & Bar Graph, Table & Stacked Bar Graph and Table & Area Graph; type Y in the UPDDUP column, to allow duplicates for _IMPODE; type Y in the OVERSAVE column, to save overrides; type LB in the BASEUOM column, since the assumption is that the units of $ENTRY is pounds; enter UOMCONV in the UOMTAB column, to have a conversion table for the unit of weight ($ENTRY).
ix. Go to Catalog in the Main toolbar. Type in _MONTHS in the Name text box and click on New. Make sure that it is selected as a Set and click on OK. In the Set Attributes window, there are no changes required. In Command Bar: _MONTHS; enter JAN through DEC in the code column. The description can be anything.
x. Go to Catalog in the Main toolbar. Type in _YEARS in the Name text box and click on New. Make sure that it is selected as a Set and click on OK. In the Set Attributes window, there are no changes required. In Command Bar: _YEARS; enter 2013 and 2014 in subsequent rows of the code column. The description can be anything.
xi. In the Command Bar type: DVATT; go to last two rows and enter _MONTHS and _YEARS and type anything in the description, preferably MONTHS and YEARS respectively.
xii. In the Command Bar type: DVATTUSG; go to the _MONTHS row and _IMPODE column and type ATTUBASE. Do the same for _YEARS row and _IMPODE column. This step will include the values of _MONTH and _YEAR in the Domain Filters.
xiii. In the Command Bar type: RBTMASTR; go to the last and type DATA_EXAMPLE and DATA_EXAMPLE_DEMEX in the Code column; following the nomenclature, type ..EXAMPLE and ?.DEMAND EXAMPLE in the corresponding rows. This is done to introduce a new section called EXAMPLE under the Data Management and have DEMAND EXAMPLE node to launch the _IMPODE in Data Viewer.
xiv. In the Command Bar type: RMTMAST; go to the ..EXAMPLE row and type: DATA in DEPTH1 column; EXAMPLE in DEPTH2 column; EXAMPLE in LABEL column; REGUI HIGHLEV in ACTION column. Similarly, go to the ?.DEMAND EXAMPLE row and type: DATA in DEPTH1 column; EXAMPLE in DEPTH2 column; DEMEX in DEPTH3 column; DEMAND EXAMPLE in LABEL column; >RDV100 _IMPODE in ACTION column. The DEPTH columns indicate the navigation steps for the new nodes; the LABEL column indicates the name for the new nodes; the ACTION column indicates the action to be performed when those nodes are pressed; REGUI HIGHLEV is the command to bring up the start screen of the application; >RDV100 _IMPODE is the command to bring up the _IMPODE table in Data Viewer.
xv. Once these changes are applied, save, close and reopen the application. Now the new nodes will appear in the Navigation Pane.
The Display type can be changed to other options by clicking on the Options tab and clicking on Update View after the desired Display Type is chosen; For example: if the Type is changed to Bar Graph:
The Domain Filters can be used to filter out the data; to use this option go to the Domain Filter tab and choose the required MONTHS and YEARS. For example: choosing JAN, FEB and MAR would yield:
Keywords: None
References: None |
Problem Statement: Aspen Base Load 서비스가 base load token 확인작업 실패
현상:
1. 프로그램 (예: PIMS, DPO 등) 실행할때 base load tokens 때문에 실행 불가능.
2. Base Load report 혹은 SLM log를 체크하면 서비스는 시작되였고 base load tokens를 확인하였는데 대략 2분후에 tokens를 돌려줬다는 메시지 혹은 token확인이 실패되였다는 메시지 나타납니다.
3. WlmAdmin에서 확인된 base load tokens 없음.
예: | Solution: 본문은 Network token licenses 에만 적용됩니다.
본 이슈는 hyprotech\shared 폴더에 라이센스 파일이 저장되여 있기 때문입니다.
문제를 해결하려면 C:\Program Files\Common Files\Hyprotech\Shared 폴더 안에 *.LIC 혹은 *.SLF 라이센스 파일들을 삭제하셔야 합니다.
Keywords: KR-
References: None |
Problem Statement: How do I suppress the License Expiration Reminder message V7.3 and lower? | Solution: NOTE: This solution only applies to aspenONE V7.3 and lower. In aspenONE v8.0 and higher, the license expiration notifications can be configured by using the SLM Configuration Wizard (see KB 117053 for details)
To suppress the license expiration message, please follow these steps:
1) Open the Windows Registry by clicking the Start Button > Run and type regedit.exe. Click OK.
2) Navigate to: HKEY_CURRENT_USER\Software\Hyprotech\SLM\Configuration
3) Right-click the Configuration folder and select New > String Value.
4) Name the new String Value NextRemindTime.
5) Double-click NextRemindTime and in the Value data: box type Never
6) Click OK. Close the Windows Registry.
After doing the above steps, the user will no longer receive the License Expiration message.
Keywords: License Expiration Reminder
References: None |
Problem Statement: This is Knowledge Base Article addresses the issue seen in the example below, when the SLM Server Log File only shows when SLM starts and stops, but no license usage activity:
# Standalone SentinelLM v7.2.0.1 Tue Jun 22 12:04:03 2004 1087898643 EUD1955900 3708 # Shutdown SentinelLM v7.2.0.1 Tue Jun 22 12:04:36 2004 1087898676 EUD1955900 3708 MA== 321241 # Standalone SentinelLM v7.2.0.1 Mon Jun 28 08:21:33 2004 1088403693 EUD1955900 3204 # Shutdown SentinelLM v7.2.0.1 Mon Jun 28 08:22:09 2004 1088403729 EUD1955900 3204 MA== 139712 | Solution: This behavior can be seen when the LServOpts Windows Environment Variable is set as User type. In order for SLM logging to work properly, make sure that LServOpts is set as a System Environment Variable.
After this change has been made, restart the Sentinel RMS License Manager Service in the Windows Services Panel. License transactions should start logging and will look like the following entry:
2 2 MjY3Mg== Tue Aug 16 10:09:09 2011 1313507349 SLM_HYSYS_Process v 0 1 0 whitakec whitakec01 8.4.0.900 1 00:0:0:0:10.32.63.35:6:2010.0.0.287:hysys.exe_25.0.0.7336 - - - - - 0 - - - NA== 527999 MTg2ODY3MQ==
KeyWords
SLM
log file
LServOpts
report
reporting
software license manager
Keywords: None
References: None |
Problem Statement: How do I install the Aspen Base Load Service? | Solution: The Aspen Base Load Service allows products to consume Base Load Tokens (for a list of Product that consume Base Load Tokens, see KB 128288).
Prerequisites:
? The license key(s) must be configured beforehand to consume the correct number of tokens. For any questions regarding license files, please contact AspenTech Support.
? The SLM Server must be installed and running with the correct license file
? The Aspen Base Load Service must be installed on the same computer as the SLM Server.
Once the prerequisites are met, the service can be installed by running the setup from the aspenONE Manufacturing and Supply Chain (MSC) 2T DVD, under 'Administration':
Insert the MSC 2T DVD and select setup.exe.
Select SLM Server then install.
On the Program Maintenance screen select 'Modify'
On the Feature Selection for SLM select Aspen Base Load Service
Once installed, the service can be seen under the Windows Services Panel:
Keywords: Aspen Base Load Service
References: None |
Problem Statement: An error occurred when Launching Aspen Exchanger Design and Rating (EDR) v7.3.1.
"Run-time Error 430. Class does not support automation or expected interface" | Solution: This error is typically caused by corrupted Windows registry entries. A utility(BjacRegClean.exe) is provided with the the standard installation to remove these corrupted registry entries. Administrative privileges is needed to properly make changes to the registry.
This utility is located at C:\Program Files (x86)\AspenTech\AspenExchanger Design and Rating v7.3\XEQ
1. Launch the BjacRegClean.exe by double clicking on it.
When you run BjacRegClean.exe, you will get a warning message:
"Use of this utility will remove registry entries. Files to revert the registry entries are in the BJACTemp folder"
2. Click OK button to continue.
3. Click "Show unregistration message dialog box"4. Then, click on the "Search Registry" button
5. Then, click "Clean up" button
6. Close the utility and run EDR to check if Run-Time error code 430 is now fixed.
Keywords: BjacRegClean.exe, Run-Time Error Code 430. Exchanger Design and Rating, and Corrupted Registry Entries
References: None |
Problem Statement: The SLM manuals contain the complete instructions to install a "Standalone" (local) license on a machine that runs AspenTech software. Sometimes you may want to have some brief troubleshooting instructions to double check the installation of your license. | Solution: Some troubleshooting instructions can be found in the attached Word document.
Important note: Standalone licenses cannot be used with tokens.
Keywords: Standalone SLM licenses
dongle, dongles
dongleless
dongle-less
dongle-locked
lock mechanism
domain
References: None |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.