question
stringlengths
19
6.88k
answer
stringlengths
38
33.3k
Problem Statement: Migrating Microsoft Excel documents that use the Process Data Add-In from Office 2003 Excel to Office 2007.
Solution: There are now two Process Data Add-ins distributed with Aspen Process Explorer: AtData.xla - Aspen Process Data Add-In (for use with earlier versions of Excel.) AtData.xlam - Aspen Process Data Add-In (for Excel 2007.) Both Add-Ins are installed to Program Files\AspenTech\APEx\Pe\Addin. This is the recommended location from which to load the Aspen Process Data Add-In. If Office is already installed when the Aspen installation process runs, then: For Microsoft Office 2003, the Aspen Process Data Add-In is also installed to Program Files\Microsoft Office\OFFICE11\Library\AtData.xla. For Microsoft Office 2007, the Aspen Process Data Add-In is also installed to Program Files\Microsoft Office\Office12\Library\AtData.xlam. In Microsoft Office 2007, for compatibility with Aspen Process Data Add-In spreadsheets created in Microsoft Office 2003, you need to have the older AtData.xla loaded (Office Button, Excel Options... Add-Ins, Manage/Excel Add-Ins, Go... Browse... to the AtData.xla file and load/enable it.) For the correct path in Microsoft Office 2007 when loading Microsoft Excel files saved under Microsoft Office 2003: ? If you use the AtData.xla from Program Files\AspenTech\APEx\Pe\Addin on both machines, the addin will already be in the location expected by the spreadsheet. AtData.xla needs to be loaded/enabled in Microsoft Excel 2007. ? If you used the AtData.xla from Program Files\Microsoft Office\OFFICE11\Library\AtData.xla on the Microsoft Office 2003 machine, AtData.xla also needs to be in the Program Files\Microsoft Office\Office12\Library directory on the Microsoft Office 2007 machine (along with AtData.xlam) and loaded/enabled in Microsoft Excel 2007. Keywords: Process Data Add-In Excel 2003 Excel 2007 locations References: None
Problem Statement: How do I insert a KPI or Q trend control into an Aspen Process Explorer VB form?
Solution: To add additional controls like KPI or Q trend control into an Aspen Process Explorer VB form follow the steps below. ? Open Aspen Process Explorer and select File, New, VBForm. Left-Click the form to display the ToolBox. In the Controls box Right-Click in the empty space and select Additional Controls. From the list of additional controls add Aspen KPI Plot, Aspen Q Histogram Chart, or any other controls needed. The added controls now appear on the ToolBox so they can be dragged over to the form as needed. Then open the VB Editor, select the VB Form and add additional declarations as needed. Keywords: KPI trend Q trend VBForm References: None
Problem Statement: Aspen Process Data / Aspen Process Explorer 'KPI Wizard' V2006.5 Client Engineering Release PD090820A (September 2009) cannot be installed on Windows Vista. You are unable to drag and drop 'AspenTech.KPI.Wizard.dll' into 'C:\Windows\assembly' directory on Windows Vista.
Solution: 1. Unzip the attached file into a temporary directory. gacutil.exe install_kpi_wizard.bat 2. Copy AspenTech.KPI.Wizard.dll attached toSolution 127200 to the temporary directory. 3. Modify install_kpi_wizard.bat to specify correct source directory. 4. Execute install_kpi_wizard.bat, when you are logged in as an administrator account. Keywords: Vista C:\Windows\Assembly References: None
Problem Statement: When using the VB Browser.GetTags command to retrieve tags only 1000 tags are returned. The VB behavior isn''t consistent with that of the Process Explorer Tag Browser. The 1000 tag limitation is imposed by this VB function. It is important to note that the Browser.GetTags search returns all records--not just the standard tag set returned in the Process Explorer Tag Browser. This expanded list includes definintion records, etc. The following code can be used to demonstrate the problem. To use the example, add the Tag Browser PE reference to the project. Private Sub Command1_Click() Dim Browser As New TagBrowser Dim Tags As Recordset Browser.Connect NODENAME If Not Browser.IsConnected Then Exit Sub Set Tags = Browser.GetTags(*) While Not Tags.EOF Map = LCase(Tags.Fields(4)) If Map = ip_analogmap Then Debug.Print Tags.Fields(0) If Map = ip_discretemap Then Debug.Print Tags.Fields(0) If Map = ip_textmap Then Debug.Print Tags.Fields(0) Tags.MoveNext Wend End Sub
Solution: The 1000 tag limitation can be circumvented by using the SQLplus Tag Browser reference in VBA. Using the following code, it is possible to access all records on the system. The following code returns record names in a list box. The total number of records is displayed on the form as well. To use the SQLplus Tag Browser the Aspen Tag Browser SQLplus reference must be added. Private Sub CommandButton1_Click() Dim Browser As New TagBrowser Dim Tags As Recordset Set sqlcon= Browser.Connect(CONNECTION, NODENAME, <Port Number>) Set Tags = Browser.Query(select name from all_records) ListBox1.Clear While Not Tags.EOF ListBox1.AddItem Tags.Fields(0) Tags.MoveNext Wend Label1.Caption = ListBox1.ListCount End Sub Private Sub ListBox1_Click() End Sub Keywords: Visual Basis VB VBA References: None
Problem Statement: What could cause the AO Execution Report menu to be greyed out?
Solution: First, make sure you have a valid license for Aspen PIMS-AO. If you do, this could be caused by a corruption of the registry entries. You should try to cleanup your registry. Please do the following: 1. Uninstall all AspenTech software 2. Reboot 3. Delete these registry keys from Start | Run, then type in Regedit, HKEY_CURRENT_USER | Software | AspenTech and HKLM | Software | AspenTech 4. Reinstall AspenTech software Keywords: registry, grey out, grey, menu, AO Execution Report, report, execution References: None
Problem Statement: Internal error 2711 from Aspen Process Explorer after upgrade.
Solution: This error code indicates that there was a problem with the installation. Check for the existence of Aspen Process Explorer in Start | Settings | Control Panel | Add/Remove programs or under the list of programs when you select to do a repair installation. If Aspen Process Explorer is not in either locations then a re-install of Aspen Process Explorer is required. Keywords: Process Explorer Internal Error References: None
Problem Statement: Data imported into Excel through the Process Data Add-in can be trended in an Excel graph; the graphs can then be saved as a separate chart in the Excel workbook. (From the toolbar, open Insert | Chart). However, when the workbook is reopened and the chart is the active sheet, the user will receive an Out of Memory error message. In addition, the plot area in the chart will be empty and no data is displayed.
Solution: When reopening an Excel workbook, the active sheet will be the sheet which was last open when the workbook was saved and closed. Since the error message will only occur when the chart is the active sheet, the error can be avoided by saving the workbook on a worksheet other than the chart. You can switch between worksheets by selecting a different tab (i.e. Sheet 1, Sheet 2, Chart 1, etc. ) at the bottom of the Excel window. The problem is a result of a Microsoft issue in Excel. It is caused by the chart sheet referencing data cells that contain volatile, user-defined formulas. Many of the formulas used by the add-ins will fall into this category. Additional information can be found in the following article on the Microsoft Website, http://support.microsoft.com/support/kb/articles/Q172/9/48.asp. Keywords: Out of Memory Excel Chart References: None
Problem Statement: On nodes with Lotus Notes debugger installed and active, Process Explorer may display an illegal operation error every time it is opened. The problem occurs if Quincey debugger associated with Lotus notes is on and Dr. Watson is turned off. This error does not affect the functionality of process Explorer Add-in''s.
Solution: TheSolution for now is to turn off Lotus Notes debugger as follows: Go to the install directory (usually c:\notes) Type RUN QNC -U. Keywords: illegal operation tag browser process explorer References: None
Problem Statement: Asterisks (***) appear in a plot, even though the tag being trended is updating in Aspen InfoPlus.21 with current data. Asterisks show up on the side axis and in the scooter values.
Solution: The very first thing to try is to restart the API server task. For Process Explorer, that would be TSK_APEX_SERVER and for Web.21 it would be TSK_DEFAULT_SERVER. If that doesn't help then please read on. Asterisks (***) appear in a plot when a given tag has not updated within the time span you have selected. As long as one data point exists within your timespan, Aspen Process Explorer will then interpolate to the next value. Example: If the tag has not updated in 2 hrs, and your plot window is set for an hour within that period, Aspen Process Explorer would not be able to interpolate the data and would show ***. One way to get around this is to increase the scan frequency for that tag. Or, if the tag does not change often and compression is preventing it from being written into history regularly, you can set your IP_DC_MAX_TIME_INT to force values to history more frequently (every 10, 20 or 30 minutes, for example.) If values are forced to history more frequently than the timespan you trend in Aspen Process Explorer, you will no longer experience the problem. Another possible cause of this problem is that the system time is set incorrectly and current data is actually being saved in Aspen InfoPlus.21 with a past timestamp. If this is the case and the trend is displayed to show current time, the current data would then be populating the trend at an earlier time, which could be off-trend to the left. On rare occasions the problem may be caused by a corrupted ADSA cache. Please seeSolution 115104 for more details. You can also try deleting and re-adding the user to a role in the AFW Security Manager and restarting the IIS Service to refresh the local security cache. Keywords: asterisk asterisks stars star *** References: None
Problem Statement: Is the Process Data Add-in (v2.5.1 and v3.x) supported with Office 2000? Are there known and fixable problems with the Process Data Add-in (v2.5.1 and v3.x) and Office 2000?
Solution: Is Process Data Add-in v2.5.1 supported with Office 2000? It is not officialy supported, but there shouldn''t be any reason why it would have problems. It has been tested in some configurations and no problems were experienced. Is Process Data Add-in v3.x supported with Office 2000? Yes, it is supported. Are there known and fixable problems with Process Data Add-in v2.5.1 and Office 2000? There are no known problems. Are there known and fixable problems with Process Data Add-in v3.x and Office 2000? There are no known problems. Keywords: Excel compatible requirement References: None
Problem Statement: After writing procedure in Aspen SQLPlus and storing in InfoPlus.21 database (ProcedureDef) and then you find that you are unable to pass parameter(s) in the MS Excel Add-In
Solution: A bad query stored within InfoPlus.21 database can prevent MS Excel from displaying the parameters textbox(es) required to execute the procedure. To solve this problem, use the steps below to group the procedures in the InfoPlus.21 Administrator ProcedureDef record and also filter out the procedure(s) causing the problem. Steps: (a) Use the save records command in the InfoPlus.21 Administrator to save procedures in groups: Right click on the database and then select Save Records in the context menu. On the Save Records screen, use the Find button to fetch the procedures in ProcedureDef or highlight and drag some of the records from ProcedureDef into the Save Records box provided. Click the File button to specify where to save the record. Click on OK button to save. Repeat this procedure until all records are saved safely. (b) Remove all the ProcedureDef records from within the InfoPlus.21 database. (c) Use the load records command in InfoPlus.21 Administrator to load procedures one group at a time. (d) Open the MS Excel, on the Process Data tab, click the SQLPlus. If the parameters textbox(es) for the first procedure appears, that group of procedures is good. Save away a copy of the snapshot and move to the next group of procedures. If the parameters textbox(es) is not visible, then one of the procedures in the group you loaded is bad. At this point, remove procedures one at a time until the parameters textbox(es) is visible in Excel. Repeat steps c and d procedure for all the grouped records. Keywords: ProcedureDef MS Excel SQLPlus Bad Query Parameters References: None
Problem Statement: How is the re
Solution: for a trend in a graphic determined? How can I get my reSolution to be more detailed? Solution The sampling for trend graphic is set to 200 points best fit for sampling. This means, no matter what your time frame, the trend will fill it with the best picture it can make from 200 of the historical data points. There is no way to change this default. You may notice that the trend in a graphic and a regular Process Explorer trend may not have the same reSolution or detail. The only way to increase this reSolution in the graphic is to decrease the time frame which you are requesting data. If you need something more than a general trend line for a tag value, the Process Graphic Trend is probably not the best tool to use. It was meant for general trends, not fine detail work. Use Process Explorer for those times. Keywords: points References: None
Problem Statement: Why do Microsoft Excel Spreadsheets using AspenTech's ribbon-based COM Add-ins take a long time to open the first time after system reboots?
Solution: AspenTech ribbon-based COM Add-ins use Microsoft VSTO (Visual Studio Tools for Office) and .NET Framework.A Opening a spreadsheet using VSTO and .NET Framework based add-ins for the first time loads and initializes the .NET Framework and VTSO runtime libraries.A This problem is common to all add-ins (not just those written by AspenTech) using these technologies. Afterwards, spreadsheets will open quickly. Keywords: slow References: None
Problem Statement: You receive an error in the application log in Process Explorer that reads a??atConnections.GetServerList: Can't create ADODB.Recordset!a?? or You open the 'Tag Browser' and no servers are shown in Process Explorer or Ip.21 Administrator. or You get the error message Retrieving the COM class factory for component with CLSID {00000514-0000-0010-8000-00AA006D2EA4} failed due to the following error: 80040154 in Process Explorer. or You add a Process Explorer Graphic into a Basic Phase design in the Aspen Production Execution Manager and receive the errors above when compiling the BP. This occurs when the Msado15.dll file becomes unregistered.
Solution: To fix this issue you will need to register the Msado15.dll file. This file is typically located in the C:\Program Files\Common Files\System\ado folder. A? Open a Command Prompt using Right-Click Run As Administrator and enter: A? regsvr32 C:\Program Files\Common Files\System\ado\Msado15.dl or A? regsvr32 C:\Program Files(x86)\Common Files\System\ado\Msado15.dll You will receive a message that the DLL file has been successfully registered. Keywords: Msado15.dll, Tag Browser, Aspen Process Explorer, Aspen Process Browser, IP.21, Aspen Production Execution Manager, Process Explorer Control References: None
Problem Statement: How do I compare a text tag to a text string in an ad-hoc calculation using the IF statement?
Solution: Use double quotes for the string value as in: =IF ATCAI = HELLO_WORLD THEN FEED123 where ATCAI and FEED123 are tags and the HELLO_WORLD is the string value. Keywords: string, format References: None
Problem Statement: Trend data for a batch in that archive can no longer be displayed in any of the Batch plots if a file set has been removed from the Aspen InfoPlus.21 database. Many customers then wonder why they can still view data in the Batch Detail Display for the same batch. If there is no longer data for the batch in the Aspen InfoPlus.21 database, each batch plot will return a different type of error message: Single Batch Plot -- For each alias listed in the legend, the value field will display *** -- If you right click on the plot and select Show Data Table from the context menu, the value for the start and end time of the batch will read #QUAN Overlay Batch Plot -- For each batch in the legend and in the data table, the value field will read #QUAN Multiple Batch Plot -- Any statistic calculated for an alias will read 0 for each batch
Solution: Aspen Production Record Manager characteristic data is kept in a separate database than the Aspen InfoPlus.21 data. If for some reason, you remove or write over the Aspen InfoPlus.21 archive that contains data for a particular batch, it will not delete the information for the same time period stored in the Aspen Production Record Manager database. This is why it is possible to view the Detail Display data for a batch that cannot be plotted in Process Explorer. This means that on a Multiple Batch Plot you could potentially view characteristic values for a batch but not alias statistics. For example, if you select an alias, the alias resolves into an Aspen InfoPlus.21 record and the data for the plot is pulled from the Aspen InfoPlus.21 database. Conversely, if you select a characteristic for a Multiple Batch Plot, that characteristic value is stored in the Aspen Production Record Manager database. If you select a batch for which there is no longer Aspen InfoPlus.21 data, but there is Aspen Production Record Manager data, you will be able to plot characteristics, but not alias statistics, in Multiple Batch plots. Keywords: References: None
Problem Statement: Using the Excel Add-In, when data is requested for a valid Aspen InfoPlus.21 tag, the following error might be displayed: #ERROR 50102: Bad tag 'tag_name' Where tag_name is the name of the Aspen InfoPlus.21 tag being requested.
Solution: Stop and restart the external tasks TSK_DEFAULT_SERVER, TSK_ORIG_SERVER, and TSK_EXCEL_SERVER using the Aspen InfoPlus.21 Manager. When these tasks aren't running correctly, the error described above can be displayed in all the cells referenced by the Excel Add-In. Keywords: 50102 #ERROR References: None
Problem Statement: When attempting to use a data entry field on a Process Graphic to write to a record in an InfoPlus.21 or Setcim database, an error message as follows may be received: You are not authorized to enter data on this Server or You are not authorized to enter data on <server name>
Solution: Locate the following two registration files in the Aspentech\desktop directory Double-click on the following files: CSDSHISTORYDA.REG CSDSHISTORYV3.REG This will cause changes in the registry that will now enable this PC to have write access to the database. Close and Restart Process Explorer Note: Write priveleges should only be given to users after careful consideration, and sufficient training. Writing data to the database causes immediate and permanent changes. Keywords: process explorer graphics editor authorized References: None
Problem Statement: With the release of v8.0, Aspen MES products are no longer checked during installation. Instead, run-time license enforcement is now required in order to inhibit unlicensed usage of applications. Depending on the value of the License State, it is possible that applications could have reduced or even zero functionality. Please refer to pages 5 and 6 of the Aspen InfoPlus.21 Product Family v8.0 Release Notes for full explanation of the new run-time license enforcement. How does this affect running or trying to run Aspen Process Explorer?
Solution: As you will see from the above referenced document there are 4 License States. Our knowledgebase article 136124 explains how to determine your current License State. If you try to start Aspen Process Explorer in a License Granted State then your application should run with full functionality If you try to start Aspen Process Explorer in a License Denied State then your application will fail to start with an error Unable to acquire RN_PME_PRCEXPL_TK license If you try to start Aspen Process Explorer in an Extended Grace Period State, or, a License Timeout Period State, then your application should run with full functionality. However, in these two States, Aspen Process Explorer displays a warning icon in the lower left corner indicating that there is a problem. Hover over the warning icon for a brief description such as ?License in timeout period (0 01:00:00).? However, Aspen Process Explorer will receive a callback from the licensing component when the license grace period elapses, and then will show a dialog and exit. NOTE: For more details of the different states and functionality you can browse the online help from Aspen Process Explorer itself. Keywords: None References: None
Problem Statement: Process Explorer (and other components) on a server or client machine: 1. Process Explorer invokes but will not display data; Unknown Error appears in the VALUE field of a trend plot. 2. IP.21 Administrator recognizes server but does not display records. 3. Basic tag browser does not display tags for a wilcard (*) query.
Solution: This occurs because the IP.21 DA task is unable to obtain proper network credentials and user information. Ping the server and ensure proper network access. Use NSLookup to verify that the client is able to obtain information about the server. Check both name based and IP addressed base lookup to ensure these are working properly. Use NSLookup on the Server to verify that the client can be properly referenced as a valid network machine. If the above mentioned functions do not work then the DNS services may not be functioning properly if the network is designed for a DNS host, or WINS services may not be working or configured if the network is utilizing WINS. A Microsoft Knowledgebase article on configuring NSLookup access for WINS networks is available. Attached is a simple diagnostic program that can help track down the problem. Note: When the program asks for the IP.21 Server, the actual Machine Name where the IP.21 Server resides needs to be entered, not the ADSA name. If that Machine Name for the IP.21 Server is not known, go to that machine and type hostname at a DOS prompt. Keywords: DA Value Unknown Error Display tag browser wildcard References: None
Problem Statement: Adjusting the font size and other attributes in legend of a trend for example tag name, descriptor etc. in Aspen Process Explorer.
Solution: In Aspen Process Explorer, 1. Select the tag legend you want to change and right click to display the menu 2. Select Legend Settings and then click on the Appearance tab to see its content 3. Click the Legend Font button to display the font screen Then make changes on the font screen and click OK Â Keywords: Legend, Font Size, Process Explorer References: None
Problem Statement: A customer wants to configure Shared On-Demand calculations in InfoPlus.21 using the IP_CalcDef family. Once those are defined, what components are needed on the client side to use them?
Solution: Shared On-Demand calculations exist on the server, and only Process Explorer is needed on the client side to use them. Keep in mind this is different than Stored On-Demand calculations, which exist and are executed on the client. The requirements for Stored On-Demand calculations are discussed in KB 115662. New Shared On-Demand calculations can be configured directly in the Administrator. But for easier management and for more complex calculations, SQLplus can be helpful, as explained in KB 126768. Keywords: installation shared ondemand References: None
Problem Statement: The following error message appears when using the Aspen Process Explorer Excel Add-Ins introduced in version 7.3: Failed: could not connect to net.tcp://xxxx..:52007/PME/ProcessData/IDataService (where xxxx.. is the where you are trying to connect).
Solution: Follow the instructions in knowledge base article 132497 to properly configure your ADSA settings. Keywords: None References: None
Problem Statement: This technical
Solution: describes the best fit algorithm used by Aspen Process Explorer.Solution The best fit algorithm divides an Aspen Process Explorer plot into 199 evenly spaced time slices or buckets. For example, each bucket in a two hour trend chart spans 36.18 seconds ((2 hours*3600 secs/hour)/199 buckets=36.18 secs/bucket). Each bucket contains up to five recordings for a point, and it is possible for a bucket to be empty. For each time slice, the best fit algorithm places into the time slice's bucket the first and last recordings along with the maximum and minimum values of a point if the maximum and minimum values are different from the first and last recordings. Under certain circumstances, the algorithm may also insert the second highest or second lowest historical recording into a bucket if a maximum or minimum value is either the bucket's first or last reading. If a time slice contains a mixture of valid and invalid historical recordings, then the best fit algorithm inserts the first invalid value into the bucket with valid values. If a time slice contains only invalid historical recordings, then the best fit algorithm places the first three readings into the bucket. As the time window gets smaller, buckets only contain actual data points. Keywords: best fit References: None
Problem Statement: A customer with Aspen Engineering and Aspen Manufacturing products installed on the same system developed a problem with the Aspen Manufacturing products after removing the Aspen Engineering suite. To correct the problem, he tried removing the Aspen Manufacturing products to install them again. The customer received the following error during the installation: The customer still saw entries for Aspen Batch.21, Aspen Process Data, and Aspen Process Explorer in the Microsoft Add or Remove Programs screen. .
Solution: The customer used Microsoft's Clean Up Utility to correct this problem. Microsoft's knowledge base article KB290301 (http://support.microsoft.com/kb/290301) describes the utility. The utility shows which products are installed and gives you an opportunity to remove them. After using Microsoft's Cleanup Utility, the customer was able to remove remaining AspenTech products and then install Aspen Process Data and Aspen Process Explorer again. Note: Please direct questions about the use of the Cleanup Utility to Microsoft and not Aspen Technology. Keywords: 1625 References: None
Problem Statement: Why is the average value returned from the Excel Add-in different from the average value returned from SQLplus, when both start/end times and dates are the same in both tools? For example, when retrieving an average value using the Trend/Aggregate method within the Excel Add-in, the average value returned from the Excel Add-in doesn't match the average value returned from SQLplus. In Excel Add-in: Use ATCL101, choose Average, set the time period to 1 Span, Start time of 09/15/06 12:21:05 PM and End time of 09/15/06 13:25:40 PM. The result is ==>18691.88 In SQLplus: Use select avg (ip_trend_value) from ATCL101 where ip_trend_time between '15-SEP-2006 12:21:05' and '15-SEP-2006 1:25:40'; the result is ==> AVG(ip_trend_value) 18916.7 THE DIFFERENCE IS ===> 224.82
Solution: The reason why the average values returned are different is because the Excel Add-in is doing a Time-Weighted Average (non-aggregate); whereas, SQLPlus is doing a straight/simple (aggregate) average. To get the Excel Add-in to calculate the average based on Aggregation instead of non-aggregation, the Value Method must be chosen from the Aggregation tab within the Excel Add-in. Here are the configuration steps to use within Excel Add-in to get average values based on Aggregate. 1. Open Excel Add-in 2. select ASPEN from the Menu bar ==> Process Data ==> Get Data ==> Trend/Aggregate Data 3. in the TAGS field, enter a tag (i.e. ATCAI or ATCL101) 4. in the OUTPUT LOCATION field, enter a cell or range of cell where you would like to display the output 5. in the TYPE field, select Average 6. in the PERIOD field, select 1 7. in the UNITS field, select Span 8. in the Start and End Time fields, enter the start and end time you want (i.e. an hour or two hours apart) 9. click on the Settings... button 10. select AGGREGATION tab, and select VALUE as the method from the drop down menu of the Method field 11. click OK to the Setting screen and the Trend/Aggregate Data screen 12. average value returned should now be aggregate instead of non-aggregate, and the value should match with the average value (aggregate) within SQLplus. For example: In Excel Add-in: Use ATCL101, average, 1 Span, Start time of 09/15/2006 12:21:05 PM and End time of 09/15/2006 1:25:40 PM, Value method is selected for Aggregation. The result is ==> 18916.67 In SQLplus: Select avg (ip_trend_value) from atcl101 where ip_trend_time between '15-SEP-06 12:21:05' and '15-SEP-06 13:25:40'; the result is ==> AVG(ip_trend_value) 18916.7 Keywords: Aggregate Aggregation SQLplus Excel Add-in References: None
Problem Statement: The Aspen Process Data legacy Excel Addin with filtering checked [AtGetFltData] may return a 0 value and 1/0/1900a?? timestamp.A With filtering unchecked [ATGetTrend] returns the correct data.
Solution: The addin function [ATGetTrend] uses Aspen Process Data to return data to Excel whereas [AtGetFltData] uses Aspen SQLplus.A To resolve this issue verify the TCP port used by Aspen SQLplus is open across the firewall.A The port number can be identified in the Windows services file and is typically defined as sqlplus 10014/tcp. Keywords: References: None
Problem Statement: How do I cause historical data to appear more quickly when using the Aspen com-based add-ins to Microsoft Excel?
Solution: Formatting individual date and time cells takes a lot of time. To speed the presentation of data, press the Advanced... field on the Get Historical Values screen and uncheck the box Format cells that contain date-time values with the Windows date and time settings as shown below. Next, in the spreadsheet itself, highlight the column with the historical date/time information, right click, and select Format Cells as shown below. Next, select Custom in the Category box and choose the appropriate data/time format. Keywords: Excel COM addin performance date time date time formatting slow References: None
Problem Statement: Aspen Process Explorer hangs on the splash screen when opening the application. The application must be ended through the Task Manager to close the program.
Solution: Sometimes removing the entry for DefaultFilePath located in the following Registry directory will resolve the problem. HKEY_CURRENT_USER\Software\AspenTech\Aspen Process Explorer\Settings Keywords: hang crash DefaultFilePath References: None
Problem Statement: When you start Process Explorer, the Aspen splash screen for Process Explorer appears. If for some reason Process Explorer hangs, or you kill ProcessExplorer.exe in NT Task Manager, the splash screen refuses to die with the application. Other applications may be hidden by the splash screen.
Solution: To make the splash screen disappear, end the ASPEN~1.EXE process using the Task Manager. Keywords: splash screen References: None
Problem Statement: How do I set up default Data Source in Aspen Process Explorer?
Solution: Please use the following steps to modify your default source in Process Explorer: 1) Choose Options 2) Click on Source Tab 3) Click on Data Source Drop Down and choose the new default data source for Process Explorer 4) Click OK Keywords: References: None
Problem Statement: How do you suppress the Splash Screen on start-up to speed up the application?
Solution: This cannot be done (by the user) and would not speed up the application even if it could. While this may be perceived as causing a longer start-up time (especially for a remote client), the actual delay is related to Security and the other hardware/networking issues. Note that without the splash screen, the user would be looking at nothing (the cursor looks normal and it appears like nothing is working for a few moments). Keywords: aspensplash.exe References: None
Problem Statement: The Aspen menu disappears from the Excel 2003 menu after closing and restarting Excel.
Solution: Upon investigation found a Atdata add-in listed in the Add-ins section of Excel, This is incorrect, as the Aspen's add-ins have specific names to them that begin with Aspen. Opened the Add-Ins section of Excel and when selecting the Atdata add-in received an error: Cannot find add-in 'C:\Program Files\Microsoft Office\Office\Library\AtData.xla', Delete from list? Removed the Atdata add-in this from the list, selected the Aspen Process Data Add-In (2003), exited Excel and when starting up Excel the Aspen menu shows correctly. Keywords: Excel add-in atdata References: None
Problem Statement: VBA timeline controls give error Element not found, when adding them to a VBA form in design mode. They seem to work if coded for run time, and they work in VB. The two timeline controls are Delta Time Control object (Delta Time Entry Box) and AspenTech Timeline Control (Time Line).
Solution: Locate the file AtTime.exd under your profile directory (e.g. c:\winnt\profiles\). and delete it. Re-start Process Explorer and re-add Additional Controls to the VBA toolbox. Keywords: Delta Time Control Delta Time Entry Timeline Control VBA References: None
Problem Statement: When you perform an installation of Process Explorer or the Production Record Manager Client Tools, one of the dialogues will be: For what is the specified account used and is it possible to leave the dialogue blank?
Solution: The account that you specify in this dialogue is used to start the AFW Security Client service. This service is used to verify Aspen application security. The account will need to be able to verify role membership of the user. If you don't use Aspen application security you may decide to leave the dialogue blank and tick the Skip user name/password validation box. The service will be started with the Local System account. Keywords: User Password References: None
Problem Statement: Error 50003 - no connection to server error in Excel when retrieving data from IP.21. Rocket Review software also installed.
Solution: Install Rocket Review software before installing AspenTech software. The installation package for Rocket Review does two things: Removes AspenTech references in the PATH environment variable Alters the registry. The software packages work fine together but the installation sequence is the problem. If the Aspen software is installed last, no problem. If you encounter this problem, re-run the install of Aspen Process Explorer to resolve the problem. Keywords: installation excel add-in References: None
Problem Statement: A tag being plotted in Aspen Process Explorer can have multiple Map Records, usually because that tag has multiple History Repeat Areas (e.g a custom definition record that allows history storage of compressed 'and' uncompressed data). The Map record you use for each tag is listed and can be changed in the Map column of the Legend. Keeping that in mind, Aspen Process Explorer also allows you to create and execute on the fly calculations in a feature called On-Demand Calculations This feature consists of the Ad-Hoc Calculations and Stored Calculations components of Aspen Calc. See the online help for more details. A simple example of such a calculation might be =TagA + TagB If both tags are defined by a definition record with a single History Repeat Area, such as Ip_AnaologDef, then the Trend Plot will be the sum of the History Values for those two tags However, with Ad-Hoc calculations, there is no way to define the Map record associated with the tags. Meaning that if TagA and/or TagB are tags with multiple History Repeat Areas, there is no way in the Legend to change the Map record being used in the Ad-Hoc calculation. What it will do is use the Default Map record. This is the one that if you just plot TagA or TagB independently, Aspen process Explorer will first choose to use when added to the plot legend.
Solution: Although undocumented, a user can pass a History Repeat Area Field Name along with the tagname. The format would be:- tagname followed by History Repeat Area FieldName (Including numeric One), enclosed in Curly Brackets For example, assuming that the field in the Repeat Area is IP_Compressed_Value :- ={TagA 1 Ip_Compressed_Value} + {TagB 1 IP_Compressed_Value} - Note Curly Brackets.. Keywords: Map Ad-Hoc CustomDef References: None
Problem Statement: The Aspen Process Data COM Addin for Excel may have the following error when attempting to read data. This error may occur after installing Aspen Process Data V7.3 Cumulative Patch V7.3.0.2, or Aspen Process Data V7.3 Cumulative Patch V7.3.0.2a (134751) Error:Method not found: 'Void AspenTech.Globalization.IAtMscLicenseAssistant.GetCookie(Int32 ByRef)'.
Solution: If the error occurs replace with the AspenTech.Globalization.dll in the Windows assembly with the attached file. 1. Stop Excel. 2. Download and unzip the attached AspenTech.Globalization.zip file to a temporary folder. 3. Verify the downloaded files are not blocked by the operating system. [see Note] 4. Execute the CopyGACdll.bat with Run as Administrator. Note: Depending on your Windows operating system version and service pack revision, files downloaded from another computer may have their block property set as a preventive measure. The zip file as well as files contained by it may all be blocked. All the files must be unblocked for the patch's proper operation. Unblocking of all the files may be achieved when the zip file itself is unblocked before its contents are extracted. To unblock the zip file, right-click the zip file and select the Properties option from the context menu and then click Unblock, if shown. Keywords: References: None
Problem Statement: After saving a trend in Aspen Process Explorer and closing the application, upon reopening the saved trend the Time Span setting reverts to default time span of 2 hours.
Solution: Go to the View tab in Aspen Process Explorer. Change the checkboxes to deselect Global Timeline and select Private Timeline. Save the trend and close the application. When reopening the save trend, the user specified Time Span will be retained. Keywords: Time Span Time range Plot Global Timeline Private Timeline References: None
Problem Statement: The ribbon-based Microsoft Excel Add-In introduced in V7.3 returns Invalid Datasource when fetching data from Aspen InfoPlus.21.
Solution: Our knowledge-base article 132497 describes the need for a new Control Panel Windows Service called AspenProcessDataService. By default, with V7.3, this service starts with the LocalSystem account. To resolve this error, close Microsoft Excel, restart the service AspenProcessDataService using the account used to start the Aspen InfoPlus.21 Task Service, and then restart Excel. Keywords: None References: None
Problem Statement: Aspen Process Explorer's trend plot display is updated every 5 seconds by default. This knowledge base article provides instructions to change the trend plot update frequency rate. The fastest trend plot update is 1 second.
Solution: Right click on the timeline bar to access the Properties menu: Here you can change the update frequency to your desired value, up to 1 per second. Keep in mind this is a global change and will be applied to all trends you are working with. The setting will persist after Aspen Process Explorer is restarted. Keywords: Update frequency timeline plot refresh rate References: None
Problem Statement: In Aspen Process Explorer you get ?Invalid value in field IP_ARCHIVING? message instead of a value in the Value field. What does it mean?
Solution: Open Aspen InfoPlus.21 Administrator and make sure that the IP_ARCHIVING value is ?ON? for all the tags that are showing this message. Keywords: Invalid value IP_ARCHIVING References: None
Problem Statement: How can I list all active constraints in a PIMS
Solution: ? How can I list non-zero right-hand sides in a PIMSSolution? Solution >How to obtain a list of all constraints that are active in a PIMSSolution PIMS does not provide this directly. The best way to do this is to use Primal.xls. In the ROWs section of this spreadsheet, those rows with non-negative PI values are active in theSolution. You can use the Excel ABS (absolute value) function to compute the absolute value of the PI values, then use the sort descending function to group together all the rows with non-negative PI values. >How to obtain a list of all nonzero RHS in a PIMSSolution The answer is similar to the above. PIMS does not provide this directly. The best way to do this is to look at the ROWs in Primal.xls. Make a new column using the Excel MAX function to compute the maximum of LO RHS and HI RHS. Then use the sort descending function to group together all rows with defined RHS. Keywords: PIMS constraints active RHS References: None
Problem Statement: Table SCALE is used mainly for three purposes: 1. Define property specific recursion tolerances (ATOL and RTOL), either tighter or less constraining. It is recommended to minimize the use of property specific tolerances (columns ATOL, RTOL), in most cases the default values (10^-3) are OK. 2. Define the range of recursed properties (MIN and MAX). Aspen PIMS can calculate this range by examining all input tables that contain property values: BLNPROP, ASSAYS, PGUESS, submodels, etc. however, the best place to define this property range is under columns MIN and MAX in Table SCALE. 3. Define penalties for blending specification properties. If you enter a value under column PENALTY, it means that the blending specification becomes a limit that can be violated by paying a penalty. It is a good practice to have all properties in the model already included in table SCALE in case they need to be used for these purposes later on, for example, for debugging purposes. What is the easiest way to get the complete list of properties used in the model to include in table SCALE?
Solution: All properties used in the model are listed in the outputSolution table PRMAP.xls (Property Map), so this is the best source for the complete list of properties in the model. To generate this report, go to Model Settings | Reporting | Selection | XLS and select PRMAP. Once you run the model, the PRMAP.xls file can be found in the model tree underSolution Files | Report Maps. From the PRMAP.xls file copy the list of properties, and in Table SCALE, to paste it select 'Paste Special | Transpose' as shown below, so that the list of properties in a row format is pasted as a column. You can now proceed to fill in the necessary data in table SCALE under columns ATOL, RTOL, MIN and MAX. Keywords: Table SCALE Properties References: None
Problem Statement: Can a Report Writer template be run automatically at the end of a Aspen PIMS run?
Solution: Aspen PIMS and Report Writer are not specifically designed to do this, however it can be setup by adding the excel.exe file to the Aspen PIMS User Tools menu and running a macro. Download the attached excel file and save it to C:\Documents and Settings\All Users\Documents\AspenTech\Aspen Report Writer. A different location can be selected if desired. 1. In PIMS, select TOOLS | Edit User Tools Menu 2. In the Tools dialog box, click on the Add... button 3. Browse to the excel.exe file on your machine and click Open. (The typical location for this file is C:\Program Files\Microsoft Office\OFFICE11.) PIMS will generate the command line and menu text. You can modify the menu text as desired. Note in the example, this text is Click OK to select and run an RW template or CANCEL to stop. This text will be displayed when the macro runs at the end of the PIMS run. 4. Select Run After Model Execution and Ask for Arguments in the lower left corner. If you select the Ask for Arguments option, PIMS will prompt the user to continue at the end of each PIMS run. This provides a means for the user to decline the RW run. If you would like the RW template to run after every PIMS run, then do not select this option. In this case, you will also need to modify the VBA code in the AutorunRW.xls file so it specifies the desired RW template. 5. In the Arguments box, add C:\Documents and Settings\All Users\Documents\AspenTech\Aspen Report Writer\AutoRunRW.xls. This can be changed as desired, but should match the location chosen for the excel file from step 1. When completed, the dialog box will look like this: When the Aspen PIMS model is run, the user will see this prompt after Aspen PIMS has completed: If the user wishes to stop here and not run a Report Writer, they click on CANCEL and Aspen PIMS will return to the end of the execution log. If they wish to proceed with the RW run, they click on OK and Aspen PIMS will initiate the autorunrw.xls macro. The user will now see Excel open. The macro will execute and allow the user to browse to the desired RW template via this dialog box: Once the desired template is chosen, it will run per it's configuration. This may or may not include being prompted for the desired database. This needs to be defined within the RW template itself and the promtping turned off if you do not wish the user to see a dialog box like this one: Once the user makes the desired selections above, the Report Writer template will execute. Items to note: 1. There is a known issue in PIMS versions prior to V7.1 (18.x) that prevents this method from working in MPIMS/XPIMS models. This issue is fixed in version V7.1. 2. Depending on your security settings in Excel, you may be asked if you wish to enable/disable macros when Excel first opens to run the autorunRW.xls file. You must select ENABLE for the run to continue. 3. If the RW template database function has a hardcoded value for the location of the database and does not prompt the user for interaction as above, then it is possible the RW report will be based on a different model than the one that was just run with PIMS. Likewise, if the user is prompted for the database, they have the ability to select a database that was not made by the PIMS run just executed. Therefore care should be taken in configuring and running the templates. 4. If you wish to turn off the automatic running template, go to TOOLS | Edit User Tools Menu and select the User Tool defined for this function. Now de-select the Run after Execution option. Keywords: RW Report Writer References: None
Problem Statement: Is there a registry setting that controls the the update frequency used by Process Explorer? Can one modify this value to control the frequency for individual user's machines?
Solution: In the registry, the value is held on a per-user basis in: HKEY_CURRENT_USER\Software\AspenTech\AtTime\Settings\UpdateRate One can modify this value within Process Explorer, if desired, by right-clicking on the Process Explorer timeline and selecting Properties. The value is in seconds. Keywords: None References: None
Problem Statement: What are the .xlam files that are placed on disk during a 2006.5 or later Aspen Process Explorer installation?
Solution: The files atdata.xlam and atbatch.xlam are newer versions of the traditional atdata.xla and atbatch.xla files (which are the Process Data Add-ins for Microsoft Excel). They are present in 2006.5 and later versions of a Process Explorer installation and are for use with Excel 2007. If one does not have Excel 2007 then one may safely use the .xla files and ignore the .xlam ones. Keywords: None References: None
Problem Statement: There are situations when Process Explorer 4.1.1 and higher will issue the error: Unknown Security Error: Initialize (2) Process Explorer must initialize the security cache to determine if security has been enabled for that application. This error is issued if it fails in doing this.
Solution: Users must have Change NTFS access to the security cache in order for the application to successfully use the security client components. The fix is for users to have an Administrator give you (your login) permission to write to the security cache. The name of this folder can be found by running AFW Tools, (Start | Programs | AspenTech | AFW Tools), going to the Client Registry Entries tab, and looking at the entry for Cache Path. The default location of the security cache is located at the following location: <drive>:\Program Files\AspenTech\Working Folders\AFW Verify that the URL parameter that defines the location of the security server has been set. This can be done using the AFW Tools, Client Registry Entries tab, and looking at the URL parameter. If both of these things check out okay, then run the SSTest utility for further troubleshooting. The utility and its instructions can be found in Knowlege Base Document ID 106497. Keywords: References: None
Problem Statement: New Plant Area fails to be added for IP_PVDef definition record in Aspen InfoPlus.21 Configuration Excel Add-in. The root of the problem is that some fields in the IP_PVDef definition record have dependencies on other fields. For example, the IP_PLANT_AREA and IP_ENG_UNIT_TYPE fields must be created before IP_PROCESS_UNIT and IP_ENG_UNIT fields.
Solution: To resolve the issue proceed as follows: Open the Aspen InfoPlus.21 Administrator and go to the ProcedureDef definition record Delete these stored procedures, if they exist: ?AtXl_UpdateTags?, ?AtXl_DbSchema? and ?AtXl_GetDefRecs? Install the latest cumulative patch for Aspen InfoPlus.21 Start MS Excel and try using the Aspen InfoPlus.21 Configuration Excel Add-in to create and configure data records defined by the IP_PVDef definition record NOTE: If you still experience problems using the Aspen InfoPlus.21 Configuration Excel Add-in to create and configure data records defined by the IP_PVDef definition record you may have to configure two templates - one to create the record, and one to modify the record. The first execution (using the Create template) configures IP_PLANT_AREA and IP_ENG_UNIT_TYPE, and the second execution (using the Modify template) configures IP_PROCESS_UNIT and IP_ENG_UNIT. Keywords: Addin Add-in References: None
Problem Statement: When database security has not been implemented on the Aspen InfoPlus.21 database, the end user can execute INSERT and UPDATE query from the SQLplus Query functionality in the new Aspen Process Data Excel add-in.
Solution: In order to prevent the end user from writing and changing the database, 1. Launch the Aspen InfoPlus.21 Manager. 2. Stop TSK_SQL_SERVER. 3. Double-click on TSK_SQL_SERVER under the Defined Tasks section. 4. Change the Command line parameters text field to 10014 rc. (Remember to click on the UPDATE button to save any changes) 5. Re-Start TSK_SQL_SERVER. When the user tries to execute INSERT or UPDATE statement which changes the database, they will see an error as shown in below screenshot. HOWVER: This will mean 'all' end users including the Administrator will not have permission to change the database through SQL query. In order to allow some users to continue using the SQLplus Query in the new Aspen Process Data Excel add-in to change the database, 1. Launch Aspen InfoPlus.21 Manager. 2. Double-click on TSK_SQL_SERVER under the Defined Tasks section. 3. Change the Command line parameters text field to n where n is a port number assigned by network administrator and not blocked by firewall. 4. Change the Task name to a new task new, e.g . TSK_SQL_SERVER_W 5. Click the ADD button to Create the new task 6. Start the new task. In order to use the new task, a new AspenDataSouceArchitecture (ADSA) Data Source will need to be configured. 1. Click on Start | Programs | AspenTech | Common Utilities | ADSA Client Config Tool. 2. Click on User Data Sources or Public Data Sources - whic=hever is preferred. 3. Click on Add button. 4. Enter a new name in the Data Source Name text field. 5. Click on Add button. 6. Select Aspen SQLplus service component. 7. Click on OK button. 8. Enter the Host Name and Port Number in which the port number will be the new port number that was defined in the new task. 9. Click on OK button to confirm the configuration. 10. Click on OK to create the new user data source. Relaunch Microsoft Excel in order to test. Below is a sample screen-shot of using the new user data source. Keywords: References: None
Problem Statement: The v7.3 Excel Process Data Addin is returning the error: Error: Server Unavailable (NotResponding) Error ) Error Number -1002) when used.
Solution: The error code -1002 denotes inability to connect to the Data server. This can be resolved by ensuring that the account which is used to run the Process Data Service on the v7.3 ADSA Server is changed from Local System to a named account. This should be the same account that is used to run the IP.21 Task Service. Keywords: Error: Server Unavailable (NotResponding) Error ) Error Number -1002) Process Data Excel Addin References: None
Problem Statement: This knowledge base article describes how to resolve the following error returned from the Aspen Tag Browser. Automation Error
Solution: Resolving this error requires performing a clean installation on the affected computer. The following procedure will resolve this problem. 1. Uninstall all AspenTech software 2. Stop all AspenTech services 3. Stop the Noblenet Portmapper service 4. Reboot the client PC 5. Remove the AspenTech registry hive under HKLM | Software if this was not done by the un-installation 6. Delete the AspenTech folder under Program files if this folder has not been deleted by the un-installation 7. Verify the services noted above are not running 8. Re-install the AspenTech software Keywords: Crash References: None
Problem Statement: The Aspen Process Data Add-in allows you to construct data functions that retrieve and compute data using Aspen-provided formulas and provide the results in an Excel worksheet. The Aspen Process Data Add-in can fetch data from the InfoPlus.21 database. There are times when users may need to modify the formulas in the Aspen Process Add-In directly instead of going through the wizard to modify them. This poses the following question: Is there a list of codes used in formulas in Excel Add-in and their meaning?
Solution: The different functions used to build the formulas in the Aspen Process Add-in are: ATGetCurrVal ATGetTimeVal ATGetAttrVal ATGetFitData ATUserEntry For further details on these functions consult the Aspen Process Add-In Options -> Help menu. These functions use the nDSetting argument, the nDSetting argument is the sum of values that specify the data to be displayed. nDSetting - (long) Numeric expression that controls the elements to be returned in the array. Sum of the constant values (see below): atTagName - (1) Specify the tag name. atServerName - (2) Specify/display the server name for the tag. atMap - (4) Specify/display the map for the tag. atTime - (8) Specify the time/read the time. atValue - (16) Read/write the value. atQLevel - (32) Display the quality level (as a number). atQLevelText - (64) Display the quality level as text (requires atQLevel to be selected). atQStatus - (128) Read/Write the quality status (as a number). atQStatusText - (256) Read/Write the quality status as text (requires at Qstatus to be selected). atSingleTime - (1024) Display a single time for multiple tags. AtSingleTime Does not apply to Actual data. atFillEmpty - (2048) Display asterisks if data is not found for a given cell. AtReverseTime - (4096) Display data from most current to oldest. AtBackRetrieve - (16384) Retrieve data from the most recent date to oldest date. AtHeadings - (32768) Display headings in the formula. AtValueAsString - (65536) Display all the values as strings. For example, to display the Tag, Server, and Status as text: Assign nDSetting = atTagName + atServerName + atQStatus + atQStatusText nDSetting = 1 + 2 + 128 + 256 nDSetting = 387 Keywords: add-in Excel formula References: None
Problem Statement: When starting Microsoft Excel, the below error message appears.
Solution: The error message is due to the fact that Cimview Explorer 97 add-in has been enabled in Microsoft Excel. For Microsoft Excel 2003, 1. Click on Tools in the menu bar of Microsoft Excel. 2. Select Add-Ins menu item. 3. Deselect Cimview Explorer 97 by un-ticking it in the Add-Ins dialog. 4. Click on OK button to close it. 5. Exit from Microsoft Excel. 6. Relaunch Microsoft Excel to verify whether above error message still occurs. For Microsoft Excel 2007, 1. Click on round Office button located at the top left-hand corner. 2. Click on Excel Options button. 3. Select Add-Ins on the left-hand menu of Excel Options dialog. 4. Select Excel Add-ins in the Manage drop-down list if it is not already selected. 5. Click on the Go... button to launch the Add-Ins dialog. 6. Deselect Cimview Explorer 97 by un-ticking it in the Add-Ins dialog. 7. Click on OK button to close it. 8. Exit from Microsoft Excel. 9. Relaunch Microsoft Excel to verify whether above error message still occurs. Note: The following error message may appear when exiting from Microsoft Excel. Runtime error '53': File not found CIMEXP50.dll Keywords: Cimview Explorer CIMEXP50.dll Process Data not installed properly. Reinstall Aspen Process Explorer References: None
Problem Statement: This knowledge base article explains why the following error may be returned when attempting to use a Microsoft ActiveX control such as MSFlexGrid.ocx in a Visual Basic Form within Aspen Process Explorer. Could not paste the control. The control could not be created because it is not properly licensed
Solution: This error is returned because the computer on which the Aspen Process Explorer Visual Basic Form is created does not have a design-time license for the ActiveX control which generated the error. The standard Visual Basic 6.0 Microsoft ActiveX controls are not distributed with Aspen Process Explorer. Important: The design-time licenses are only required on the computer on which the Aspen Process Explorer Visual Basic Form is created. Client computers which only view the forms do not need a design-time license. Design-time licenses for the standard Microsoft ActiveX controls, such as MSFlexGrid.ocx, are installed with Microsoft Visual Basic 6.0. However, Visual Studio .NET does not install these licenses by default. If you use Visual Studio .NET on this computer instead of Visual Basic 6.0 you can follow the instructions in the following Microsoft knowledge base article to get the Visual Basic 6.0 controls properly licensed. http://support.microsoft.com/default.aspx?scid=kb;en-us;318597 If you do not have any Visual Studio products installed on this computer then you can install Visual Basic 6.0 in order for the design-time controls to be properly licensed. Keywords: None References: None
Problem Statement: When launching Aspen Tag Browser, you may see the following error: Error: Failed to load control 'sstab' from tabctl32.ocx. A version of tabctl32.ocx may be outdated.
Solution: There are a couple of suggested reSolutions for this error: The most frequent fix is to re-register the file tabctl32.ocx (using regsvr32.) After the file is registered, reboot the machine and try running the Tag Browser. Occasionally the problem has simply disappeared the next time the system is rebooted. SAP client tools have caused this problem to appear (resolved by updating to a later patch on those tools.) Reinstall Process Explorer, making sure to choose the Force Installation of Core Components option. Keywords: References: None
Problem Statement: I would like to be able to de-activate the IP.21 Configuration Add-in on workstations post install of Process Explorer. The issue is that the IP.21 Configuration Add-in allows users to write to the database and make changes, and without applying database/record level security it is not currently possible to restrict this.
Solution: Other than manually unselecting the Add-in within Excel, it is possible to de-activate the Add-in by downloading the attached file Disable IP21 Configuration Add-in, rename it to .bat and run this file on the machine with Administrator privileges. N.B. This batch file makes changes to registry keys associated with the Add-in. If you are unsure of your actions, and/or if you should be making changes to your registry please contact your I.T. department. Keywords: IP.21 Configuration Addin Excel Addin References: None
Problem Statement: Installing the Microsoft Excel ribbon-based Aspen APRM Data COM Add-in produces the error message AspenTech.PME.ExcelAddin.APRM.dll is not a valid Office Add-in.
Solution: To work around this problem: 1. Make sure you have read/write access to the registry. The COM-based add-ins modify registry settings. 2. Check for the file Microsoft.office.interop.excel in C:\Windows\Assembly. If this file is not there, go to Microsoft's web site and download the file depending on the version of Excel. 3. For 32-bit systems, download the file excelaprmaddin_regasm.txt to excelaprmaddin_regasm.bat and execute the batch file from a Windows command window. 4. For 64-bit systems, download the file excelaprmaddin_regasm_x64.txt to excelaprmaddin_regasm_x64.bat and execute the batch file from a Windows command window. 5. Finally download addin_aprm.txt to addin_aprm.reg and execute the command reg import addin_aprm.reg from a Windows command window. Keywords: References: None
Problem Statement: In Aspen PIMS-AO, variables include properties and column activities. How does Aspen PIMS-AO initialize those variables when using XNLP?
Solution: There are three methods in PIMS-AO, Here we discuss each method and how the execution log will be different from one another, Method 1: Start from previousSolution From the Model Execution window, select inputSolution. The number indicates the file full name is 'XNLP_Solution.001'. You can change the extension .DAT of default outputSolution, XNLP_Solution.DAT to any three digits. This number will be shown in this InputSolution field, Partial Execution Log as below, COMMENCE PROCESSING CASE 1 ReadSolution file XNLP_Solution.001 Start Optimization --> Tuesday, February 01, 2011 2:58:03 PM Start solve --> Tuesday, February 01, 2011 2:58:03 PM Method 2: Use Linear Initialization - ON This setting is located in MODEL SETTINGS | XNLP settings | General tab. PIMS runs one pass of Distributive Recursion using PGUESS as initial values to initialize. Partial Execution Log shown below, COMMENCE PROCESSING CASE 1 PIMS version 18.9.30 incorporates XPRESS version 20.00.21 Selected objective sense: MAXIMIZE Problem Statistics: 399 Rows 415 Structural Columns 0 Integer Variables 0 Special Ordered Sets 1 RHS Columns 3593 Non-Zero Matrix Elements Density = 2.16 Percent Start optimization --> Tuesday, February 01, 2011 3:17:13 PM Using primal simplex method Presolved problem has: 211 rows 224 cols 1923 non-zeros Crash basis containing 0 structural columns created Its Obj Value S Ninf Nneg Sum Inf Time 0 972.720000 p 2 0 10.000000 0 100 972.717905 p 42 10 10.000072 1 200 972.711781 P 16 47 6.218722 1 278 1317.751742 P 0 0 .000000 1 Uncrunching matrix 278 1317.751742 P 0 0 .000000 1 OptimalSolution found End optimization --> Tuesday, February 01, 2011 3:17:14 PM Start Optimization --> Tuesday, February 01, 2011 3:17:14 PM Start solve --> Tuesday, February 01, 2011 3:17:14 PM Method 3: Use Linear Initialization - OFF Set 'Default Initial Value' to 1000. Then all the variables are initialized to this default value. This is the only method to use when using External Models and no initialSolution file is provided. Partial Execution Log shown below, COMMENCE PROCESSING CASE 1 Start Optimization --> Tuesday, February 01, 2011 3:23:33 PM Start solve --> Tuesday, February 01, 2011 3:23:33 PM Keywords: XNLP initialization PIMS-AO References: None
Problem Statement: When you upgrade to MS Excel 2007 and have Aspen PIMS input files in older version, you may get this message from Excel when trying to save the changes: filename.xls cannot be saved in current format.To save your changes, click OK, then save it as the latest format, as shown in the screenshot. Therefore, to save your changes you need to update the MS Excel format. The problem is that with the latest format (2007) the extension of the MS Excel files is .xlsx, not .xls. Therefore, when you save in this format, the connections to the Aspen PIMS model tree are lost, and you need to reconnect the files to the model tree. What is the workaround?
Solution: In MS Excel 2007, select the option Save As and choose the Excel 97-2003 or the 5/95 format; these formats are still .xls, so you avoid having to reattach all the files to the model tree. To save in Excel 97-2003 format Select Save As from the Office button (left top) and then select Excel 97-2003 format. To save in Excel 5/95 format Select Save As from the Office button (left top) and then select Other Formats. From the Save As drop down menu, select Microsoft Excel 5/95 workbook. Keywords: Compatibility MS Excel 2007 MS Office 2007 References: None
Problem Statement: Installing the Microsoft Excel ribbon-based Aspen APRM Configuration Data COM Add-in produces the error message AspenTech.PME.ExcelAddin.APRM.Configuration.dll is not a valid Office Add-in.
Solution: To work around this problem: 1. Make sure you have read/write access to the registry. The COM-based add-ins modify registry settings. 2. Check for the file Microsoft.office.interop.excel in C:\Windows\Assembly. If this file is not there, go to Microsoft's web site and download the file depending on the version of Excel. 3. For 32-bit systems, download the file excelaprmconfigurationaddin_regasm.txt to excelaprmconfigurationaddin_regasm.bat and execute the batch file from a Windows command window. 4. For 64-bit systems, download the file excelaprmconfigurationaddin_x64_regasm.txt to excelaprmconfigurationaddin_x64_regasm.bat and execute the batch file from a Windows command window. 5. Finally download addin_aprmconfiguration.txt to addin_aprmconfiguration.reg and execute the command reg import addin_aprmconfiguration.reg from a Windows command window. Keywords: error, add-in, Exel References: None
Problem Statement: Why does the Configuration Wizard in the Aspen Configuration Add-In set the field IO_#TAGS to 350 in transfer records even though I am adding only a few occurrences?
Solution: This works as designed. When you populate tags within a get record even though you are adding few tags (for example, 10) the Configuration will still create 350 occurrences in a get record, leaving the rest of the occurrences empty to allow for expansion. Keywords: References: None
Problem Statement: When plotting more than one tag in Aspen Process Explorer using the autoscaling feature, one of the tags may disappear from the plot. Turning the autoscaling feature off brings the tag back into the plot.
Solution: When two tags have very similar sampling, trending, and scaling behaviors, autoscaling will cause the trends to overlay each other causing one of them to disappear. ASolution for this is to turn autoscaling on for both tags. Then, enter a new value for the Plot Min or Plot Max for one of the tags that is a couple of points above or below the autoscale value. This will offset the trends enough so that you can see both of them. Keywords: Auto scale Trend References: None
Problem Statement: Using the Aspen Process Data Com Add-In for Microsoft Excel returns:- Error: Unable to acquire license: SLM_RN_PME_PRCEXPL_TK, SLM_Process_Explorer
Solution: Starting with the 7.3.0.3 patch released in April, 2012, the Aspen Process Data Com Add-In for Microsoft Excel requires the license key SLM_RN_PME_PRCEXPL_TK, SLM_Process_Explorer. The error noted above is returned if this license key is not found in your license file. If you do not have this license key then please submit a license key request from the website http://support.aspentech.com to request an updated license file. Keywords: Add-Ins License 7.3.0.3 SLM_RN_PME_PRCEXPL_TK, SLM_Process_Explorer References: None
Problem Statement: SET is running fine. However when I try to modify SET, there is an error message that pops up, saying could not load file or assemble 'WinFormWidgets'
Solution: Copy the file 'WinFormWidgets.dll' into the PIMS installation directory. The default installation directory is C:\Program Files\Aspentech\Aspen PIMS. Keywords: SET References: None
Problem Statement: How can you report properties for a formula blend? Aspen PIMS only reports properties on a Specification Blend.
Solution: There are two different ways to report properties of a Formula Blend. Both ways work using Specification Blends. 1) Create a specification blend with the original Formula Blend as only BlendStock Create your Formula Blend as usual, then create a Specification Blend where the only blendstock is the Formula Blend. In the example shown below, the Formula Blend is called GLP; this is the only blendstock to the Specification Blend LPG. For the properties that you want to report, in table BLNSPEC enter a Pprp row (prp is the property tag) for each property that you want to report. Wherever the formula blend is used in the model (typically in T. SELL), it should be replaced with the new Specification Blend. To report the content of each original Blendstock, you have to enter a Pprp row for each original component. In this example, PSPG, PNC3, PIC4 and PNC4 are used. The changes needed in Tables BLENDS, BLNMIX, BLNSPEC are as follow: The results are shown below: 2) Create a Specification Blend with entries in Table BLNTARG to define the recipe With this method, you do not need to define a Formula Blend, because you will define the recipe through table BLNTARG. Do not enter specifications for the blend in T. BLNSPEC, but enter the Pprp as described above to report properties.. To make PIMS respect the recipe, you may have to use higher penalty values in table BLNTARG to meet the recipe. In the example below, you enter these blend-specific penalties values in columns ULPG and DLPG. The changes needed in Tables BLENDS, BLNMIX, BLNSPEC and BLNTARG are as follows: Note: You must check that there are no active penalties in table BLNTARG for this blend, because if there are penalties, the recipe is not made exactly as intended. The results are shown below: Keywords: blend recipe formula property References: None
Problem Statement: How can we use the Nonlinear Equations facility of Aspen PIMS Advanced Optimization to compute pool properties? We are specifically interested in implementing a PCALC-like calculation, to model the sulfur reduction across a hydrotreater.
Solution: Nonlinear Equations allow us to implement property calculations for recursed pools beyond the standard pooling techniques of Aspen PIMS. ThisSolution will demonstrate the technique for a hydrotreater submodel. The key aspects to this technique are (1) implementation of recursion rows in a submodel, (2) a new submodel column to hold the results of the nonlinear Quantity*Quality (or QQ) calculation, (3) a nonlinear formula. Distillate Hydrotreater Example This example is derived from a PIMS class model. In the original version of the model, PCALC is used to model a constant sulfur removal factor of 90%. In this example, we will use a nonlinear formula to implement the 90% sulfur removal. This type of calculation cannot be implemented in standard pooling structure because the -999 placeholders that represent property values cannot accommodate a multiplier. Feeds to this submodel, SDHT, are heavy straight-run distillate, HD1 and coker distillate, DCD. The main product is hydrotreated distillate, TRD. Submodel Structure In the original modeling scheme for this unit, a dummy feed pool is used to compute the average feed properties, which are then transferred to the hydrotreated distillate via PCALC. In the present example, the product properties are calculated directly by recursion of pool TRD. We call the reader's attention to row RSULTRD. Please note that there are no -999 coefficients in this row. Instead, there is a contribution from column DSU. This column is created to hold the result of the nonlinear calculation of QQ (Quantity*Quality) for the sulfur of the pool. Table PGUESS As with standard pooling in Distributive Recusion, the modeler must include in Table PGUESS initial guesses for all pool properties, including those computed with nonlinear formulas (SUL, in this example). An excerpt from Table PGUESS is shown below. Nonlinear Equation A nonlinear equation is used to compute the activity of SDHTDSU, which represents QQ for the pool sulfur. This equation implements the calculation QQ of pool = (1 - removal fraction)*S(Feed quantity * Feed quality) In XNLP, qualities are represented by explicit variables named Qprpxxx, where prp represents a pool tag and xxx represents a material tag. So QSULHD1 represents the SUL property of pool HD1. Such property variables are created if the property is calculated via recursion structure or via PCALC. Property values defined in Table BLNPROP cannot be accessed this way. Once defined, the nonlinear formula will be visible on the PIMS model tree. Conclusion ThisSolution has demonstrated how nonlinear formulas can be used to implement a property calculation for a unit with a constant contaminant removal factor. More sophisticated calculations are possible with this facility. For example, one property might be a function of several other properties. The submodel structure would be similar to that shown here. Keywords: None References: None
Problem Statement: When the LP
Solution: is not optimal, the messages following will list certain rows and columns. How do we interpret those rows and columns individually, and how should we go about troubleshooting the messages? Solution Those messages happen when the problem is not only not optimal, but also is infeasible. The messages are due to some constraints that cannot be met. We will use the following messages as example. *** PROBLEMSolution IS NOT OPTIMAL *** *** ROW XAROR93 1208.0536 *** ROW XBNZR93 120.8061 *** COLUMN BRFTS90 67.6576 *** COLUMN BRFTI90 0.0005 *** COLUMN BRFTI91 18.0448 *** COLUMN BRFTI92 11.1873 *** COLUMN SRFTR92 32.7481 *** COLUMN SRFTRFT 11.4412 When N or X rows are listed, the problem is most likely to be in blending area. For example in this particular case, the properties of ARO and BNZ in blending need to be investigated. The rows and columns reported here indicate the degree to which they are infeasible. The two rows reported here are maximum blend spec rows, which are of type greater than or equal to. So the left hand sides of these rows are probably less than zero by the reported amounts. The columns are outside of their bounds by the reported amount. Looking at the example set of rows, it appears that the max aromatics and benzene specs for gasoline R93 cannot be met. There are several possibilities may cause the problem, the ARO and BNZ of the R93 components are too high, the specs are too low, the blend cannot get enough of one or more blend components that are low in ARO and BNZ, Therefore it is necessary to investigate the properties and availabilities of blend components to R93. Look at the set of columns, there are multiple BRFTxxx vectors listed. This indicates that there may be an issue for the properties in the blendstock BRFT. Keywords: LP References: None
Problem Statement: How do I limit max number of blend products? For example, there are four blend products, LPG, LRG, URG and UPR. Only three out of four can be produced at the same time, among those, only URG or UPR can be produced at a time.
Solution: Mixed Integer Programming is going to be used in this case. We will build MIP table with four binary variables. In table ROWS, we build 2 equality rows and 4 L-rows. * Table MIP Table of Contents * TEXT BV IPRDLPG LPG 1 IPRDLRG LPG 1 IPRDURG URG 1 IPRDUPR UPR 1 * Table ROWS Table of Contents * TEXT FBLNLPG BVBLLRG BVBLURG BVBLUPR IPRDLPG IPRDLRG IPRDURG IPRDUPR RHS EPRDNUM 1 1 1 1 3 EPRDNu2 1 1 1 LPRDLPG 1 -100 LPRDLRG 1 -100 LPRDURG 1 -100 LPRDUPR 1 -100 In Matrix, those 6 equations are as following, IPRDLPG + IPRDLRG + IPRDURG +IPRDUPR = 3.0 IPRDURG+ IPRDUPR = 1.000000 FBLNLPG -100.0 * IPRDLPG <= 0.0 BVBLLRG -100.0 * IPRDLRG <= 0.0 BVBLUPR -100.0 * IPRDUPR <= 0.0 BVBLURG -100.0 * IPRDURG <= 0.0 In theSolution report, only LPG, URG are produced. Economically, PIMS chooses not to produce LRG. Keywords: MIP blends max number References: None
Problem Statement: I ran Aspen PIMS and this dialog pops up. What is this and what do I need to enter?
Solution: This is related to the components used during parallel processing. Parallel processing is only available with the Aspen PIMS Advanced Optimization license when the XLP matrix generator is being used. To register your credentials, enter your Windows username and password. Once you have entered this, the dialog will no longer pop up in the future. Keywords: MPIEXEC parallel processing References: None
Problem Statement: What happens when there is an 8th character in the Capacity, Control or Parameter row name in Table ASSAYS?
Solution: The eighth character in a Capacity, Control or Parameter row name in Table ASSAYS designates the logical crude unit(s) to which the row applies. Control and parameter rows behave the same is described below for capacity rows. When an eighth character is present, the capacity will only apply to crude unit(s) whose 3 character tag ends with the designated 8th character. For example, crudes ARL and ANS can both processed in crude units SCD1, SCD2, SCD3, and SCR1 and the following structure is in the ASSAY table for each of those crude units: * TABLE ASSAYS Table of Contents * Crude Assay Data TEXT ANS AHV ARL CCAPARL 1 CCAPANS1 1 The corresponding matrix structure for CCAPARL is shown below. Notice that it includes contributors from each of the available crude units. The matrix structure for CCAPANS omits the 1 from the matrix row name and only includes contributions from crude units whose name ends with 1. The reported values would be as follows: In the Capacity Summary section of the fullSolution report: CCAPARL => the total ARL processed in all 4 crude units combined. CCAPANS => the amount of ANS crude processed in SCD1 and SCR1 combined. In the Submodel Summary section of the fullSolution report: Under each submodel, the amount that particular submodel contributed to the capacity will be reported. In this example, that would be: In SCD1 CCAPARL = 0 CCAPANS = 1,000 In SCD2 CCAPARL = 24,369 In SCD3 CCAPARL = 2,551 In SCR1 CCAPARL = 13,080 CCAPANS = 0 Keywords: ASSAY E-row L-row G-row CCAP capacity parameter P-row References: None
Problem Statement: MAX = 0 in DEMAND or DEMALLOC for products with recursed streams blended into them will not suppress error distribution coefficients for those products in the local models. This situation arises when, for example, a reformulated gasoline grade is set to zero in DEMAND or DEMALLOC but that same product is not set to zero in the local model SELL table where that product is produced. If the MAX specified in the local SELL table is not zero then PIMS will not automatically suppress the error distributions to that pool even though the MAX in DEMAND or DEMALLOC is set to zero.. This may cause initial infeasibilities and local optima.
Solution: Users must check their global DEMAND and DEMALLOC tables and make sure if a recursed stream has a MAX = 0, to go to appropriate local models and make SELL = 0 as well. NOTE: It is not recommended that you set all SELL MAX values to zero, only the ones which have a DEMAND/DEMALLOC MAX value of zero. Keywords: M-PIMS PIMS DEMAND DEMALLOC SELL References: None
Problem Statement: How does localization of Aspen Process Explorer work? What do I have to do to see a localized GUI of Aspen Process Explorer in languages different from English? (e.g. French, German or Spanish)
Solution: - In order to display the localized resources for Process Explorer and Process Data, the OS language must match the desired language setting. A French Operating System will display French resources, etc. It has always been this way with Process Explorer. This is due to the way that Process Explorer is constructed and compiled. It's built with all the supported languages available in the actual binary components (EXEs, OCXs, DLLs). The Windows APIs for loading string, menu, and dialog resources at runtime function so that only the OS language determines what displays, not the Regional Settings for the user. - There is a workaround to modify this behavior: it is the use of satellite DLLs. The localization kit for Process Explorer will provide this functionality. If it is desired that other languages are to be displayed on a particular OS, then the localization kit must be used to create satellite resources DLLs for each desired language. This is the only way in which the Regional Settings will affect Process Explorer's localization. Keywords: LOCALIZATION KIT FRENCH GERMAN SPANISH References: None
Problem Statement: 如何用Aspen Process Explorer Graphics Editor添加值到Aspen InfoPlus.21数据库?
Solution: A. 运行Process Graphics Editor: 1. 点击数据区图标,并在右侧按住鼠标左键画出数据区 2. 双击或者右击选择属性,打开数据区属性窗口 3. 在常规标签样式部分,选择允许输入数据。此项会允许用户手动把值输入到数据库中。点击采用后确定 4. 在数据源标签中: a. 在位号名输入目标位号名称(例如:ATCAI) b. 在属性中,选择要输入值的名称 (例如: IP_INPUT_VALUE) c. 在映射和数据源部分,如果在第一步中输入了正确的位号名后会自动显示出来。(例如:映射为IP_ANALOGMAP,数据源为SAMCHVM). d. 点击确定 5. 点击 文件 | 另存为 保存文件 (例如:文件名为 write1.atgraphic ). B. 运行Aspen Process Explorer: 1. 打开步骤A中创建的文件(例如:write1.atgraphic) 2. 双击数据区域,弹出输入新值窗口 3. 在值(V)部分输入想要输入到数据库中的值后点击确定 C. 在IP.21 Administrator 查看刚才输入的数值是否在指定位号的IP_INPUT_VALUE显示 Keywords: 写数据 CN- References: None
Problem Statement: How to read trend comment fields in and IP_PVDef record with the excel addins.
Solution: Create a custom Map record and set the value of the Map fields to the attribute fields you would like to read. Then define the tag and map in the Excel spread sheet cells as described in the Aspen Process Data Addin Help file. EXAMPLE: To read the trend comments in an IP_PVDef record, first make a copy of one of the IPX_PV_*_Map records Then edit the following fields in the new Map record. Map_IsDefault False Map_HistoryArea IP_#_of_Trend_Cmmnts Map_HistoryValue IP_Trend_Cmmnt Map_TimeStamp IP_Trend_Cmmnt_Time Finally point to this Map record in the Excel Add-in Keywords: None References: None
Problem Statement: Process Explorer uses the extension, .apw, for workspaces. Aspen Plus uses the same file extension for its document files. When both products are installed on one machine, there is a conflict. Users are able to open the files, but, they can not associate the files to the appropriate program in Windows. Whichever product is installed last gets to use the extension. In other words, when a user double clicks on the .apw to launch the product, the product that was installed last opens. This may not be the correct product!
Solution: Process Explorer version 6.0.1 changes the extension on .apw files to .apws. If you are running an earlier version of Process explorer, it is recommended that users launch the Aspen Plus or Process Explorer application and then open the .apw files from within the program rather than double clicking on the .apw to launch the program. Keywords: association extension References: None
Problem Statement: Upgraded from version 2.51 to version 4.1 cannot see old history. Scenario: I upgraded from version 2.51 to version 4.1. The upgrade was successful and everything is working. However, when I go into Process Explorer, I only can see today''s data. Whereas, I supposed to see data back several months/years. I followed all the instructions in the installation/upgrade manual and I know for sure that the map.dat file is in the correct place. What should I do to be able to see old history data?
Solution: If you believed that you have followed the instruction carefully and still have the problem, then here are two ways to resolve this issue. Plan A: Shutdown IP.21 Restore the map.dat file from 2.5.1 Restart IP.21. Note: This plan might not work for you if you are collecting new data on the default map.dat that was installed with 4.1. Plan B: Throw out the 4.1 snapshot. Get rid of the fileset(s) that has/have been written to since the 4.1 upgrade along with the cache.dat. (Be sure to delete the cache.dat and if for any reason there is an event.dat, get rid of that too!!) In other words, make sure history is back to where it was at the time of the first upgrade. Create a new virgin snapshot making sure that no CIM-IO or SQLplus is in the picture. (We are not yet using the group configuration file that was backed up from 2.5.1.) Move the 2.5.1 map.dat into place. Run upgrade again on the snapshot Test if old history is viewable shutdown IP.21 restore group configuration (the .ipg file from 2.5.1) Start up IP.21 database Note: It is very important that you make sure nothing new 4.1 gets written to history before you confirm that old history is accessible. Once you can see the old, then you can add new history. Keywords: upgrade history References: None
Problem Statement: Requesting data simultaneously for multiple tags gives the result: #ERROR 50102: Bad tag
Solution: The most common reason for this result is the direction which the tags are listed on the spreadsheet. If the tag names are listed directly below one another (as in a column), then the information for each tag must be read across (in rows). This is because when referencing a tag with the Excel Add-In, the tag can be defined using Tagname, Server, and Map. In this case, if a Tagname was listed in cell A1, then cell B1 could contain the Server name (ADSA data source name), and cell C1 could contain the Map record. With this setup, on the Data Source Tab in the Settings area of the Excel Add-In, you'd want to check the radio button for option: Read the information for each tag in rows, across If, on the other hand, you have the Tagnames listed horizontally (so a tagname would occupy cells A1, B1, and C1), then you'd want to check the radio button for option: Read the information for each tag in columns, down The additional tag information (Server and Map) is not required, however, the Excel Add-In still needs to know the correct direction when reading the tag information. Keywords: bad tag 50102 References: None
Problem Statement: What does an asterisk beside the case number in the run execution dialog indicate?
Solution: The asterisk in the run execution dialog indicates that this case requires generating a new matrix. The asterisk only applies to the XLP matrix generator, therefore the XLP matrix generator must be on to see the asterisk. Once you turn XLP on, the asterisk will remain even if you turn XLP off (at least while that model is still open). Matrix generation is only required for changes in model structure or for things which MIGHT change model structure. Here is a list of items that require generation in the XLP matrix generator: ? Use of the keyword REPLACE or REPLACEALL in table CASE Adding an entire table Adding a row or column to a table Some modifications to a submodel - changing from non-EMPTY to EMPTY, changing from EMPTY to non-EMPTY, changing to or from 999 or -999 Modification of any RFG parameter (SEASON, TYPE, etc.) in table BLNSPEC Modification to table TRANSFER column MAX entry to or from 0 Entry in a column that is not modifiable for the table Keywords: NMG matrix generation matrix generate Asterisk Model Execution dialog run dialog References: None
Problem Statement: Aspen Process Data Add-in cannot be loaded successfully in the sequence when creating the App-V package and then it cannot be used in the client machine. Cause: VSTO 3.0 and VSTO 3.0 SP1 failed to be installed during streaming Process Explorer on App-v Sequencer.
Solution: During Monitor Installation: 1. Install MS Excel 2. Install Vstor30.exe from the core folder in DVD2 aspenONE V7.3 (dvd2\ams\aspenONEv7.3dvd2\core\VSTO2008\) 3. Install Aspen Process Explorer, InfoPlus.21, SQLPlus, Process Data, etc. During Launch Application: 1. Copy vstor30sp1-KB949258-x86.exe from the core folder in DVD2 aspenONE V7.3 (dvd2\ams\aspenONEv7.3dvd2\core\VSTO2008\) to somewhere in Q drive 2. Launch Visual Studio Command Prompt (2008) from the Wizard 3. Launch a Visual Studio 2008 command prompt from the Sequencer and run the SP1 installation from the command prompt. 4. After SP1 is installed, launch MS Excel.exe from Sequencer Keywords: None References: None
Problem Statement: When using Distributed Recursion, the IterationLog.lst report is created, which allows to track changes to the recursed properties from one recursion pass to the next. Is there an equivalent report to track properties changes during the
Solution: when XNLP is used? Solution There is a report called XLSP_report.log. To generate it, go to Model Settings | XNLP | Advanced, and set Trace Level to medium. In this report, you have to look for the Q-variables (e.g. QAFCCF1 for the quality AFC for pool CF1) and then do a Find Next to check the different values through theSolution cycle. All variables will start with XLP., e.g. XLP.QAFCCF1, so you can ignore the XLP. string. The lower and upper bound for the variable are on each side of the value. It can not go beyond those values. In version 7.1 of Aspen PIMS, which will be released around January 2009, a new report will be introduced that has a more convenient format. Keywords: Iteration Log IterationLog Properties Property References: None
Problem Statement: In the Process Limit section of the Full
Solution: report (reporting results of restrictions placed intable PROCLIM), you will see marginal values for properties or process parameters that are at a limit. How do you interpret the marginal values for properties or process parameters restrictions placed in table PROCLIM? Solution The matrix structure created for limits imposed to properties or process parameters using table PROCLIM is the same as the structure created for specification blends. There is one E-row(equal to zero) to accumulate the total amount of the components, there is one L-row (less or equal to zero) for the MIN specification and one G-row (greater or equal to zero) for the MAX specification. Below is an example of the PROCLIM structure generated to limit the severity (SEV) in a reformer with 4 modes of operation (90, 94, 98, 102 severity). The PROCLIM limits are the coefficients under column ZLIMSEV. As the structure is the same, the discussion that applies to the marginal values for specification blends inSolution 122072 applies to the marginal values related to the use of table PROCLIM. Note on the signs of the marginal values: The marginal value of a PROCLIM specification at the limit (either MIN or MAX) indicates the incentive to relax the specification. MIN and MAX marginal values will come out with opposite sign: this is due to the fact that these marginal values are the PI values of the L or G rows that represent the specification. For the L-row, the row is at the upper limit (which is 0), while for the G-row, it is a the lower limit (which is also zero). However, in both cases, the marginal value that is reported indicates the incentive to relax that limit, i.e. make the MIN lower or the MAX higher. You can switch the sign convention by using the setting SIGNREV under MODEL SETTINGS | REPORTING | MISCELLANEOUS as indicated inSolution 118167. Keywords: PROCLIM Process Limits Marginal Value DJ PI References: None
Problem Statement: Sometimes Global Economic Summary in Full
Solution: in XPIMS does not match the sum of local Economic SummarySolution In the global XPIMS model transfers between local models do not have a product price/cost however when local economics are calculated in the reports (e.g. FullSolution) sells price from local SELL table is taken to calculate revenue in a source plant and buy cost from local table BUY is taken to calculate costs in a destination plant. If the same price is used in table BUY (destination model) and SELL (source model) sum of this artificial profit and cost will be zero hence sum of local economics will be equal to global economics. If for a particular transfer user will set up different cost in a destination model and price in a source model PIMS will calculate economics accordingly hence there will be additional revenue/cost which will reflect this difference and sum of local economics will not be equal to global one as on global level this stream is just transferred to another model. Keywords: XPIMS, Economic Summary References: None
Problem Statement: Model Settings / General ?E? ?eGas Volume to Weight Factor (GVTW) ???I?????H
Solution: Aspen PIMS???I??Z?60?x?A1?C?????W???I?K?eGVTW?W???????A???e?BVTW?W???????a?EGVTW?W???E?A???A?aVOL, GAS ?????? WGT?????Y?e???e?e?P?E?n???????GASES???S?X?g???e???X?g?S?[???ESO???ASPG?I????? ???E?????A?A???|?[?g?I???x?????????-?A?d?E?A?e?E?A?K?X?I?IS??vZZ???????-?E?e?B ???Z?E?IBFOE (Barrels of Fuel Oil Equivilant)???K?X?e?E???c?t?e?E?I?IS??E?e?[?u??UNITS???p???c?e?e??????? ?A???B?e?[?u??GASES???p???e?e???I???I?????E?u?I?f?[?^?I?e?[?u??UNITS???c?i?????e?E???e?I?E?c?E???B?K?X?ISPG?I?vZZ?EZg?p???e?o?C?I???x??General Model Settings ?_?C?A???O?IGeneral?^?u?IGVTW???E?Y?e???e?e?K?v??? ?e?B ?o?C???x?I???x?A???I?AZ??x?A`g???E???A?A?I?>???e?B?>?Y?ISi?????e?A?E?e?U?A?A???E???????e?[?u??GASES?E?u?I???e???X?g?S?[???ISPG??GVTW????????e?E???A?A?d?E???e?E?I?IS????????-???i?e?e?????E?E?e?B ??: ???L?I?\?IS#?o?C?E?????eGVTW?W???I?a Gas Unit of Measure Weight Unit of Measure GVTW Factor KSCF at 60 deg F, 1 atm. K# 0.07636 KSCF at 60 deg F, 1 atm. Metric Ton (2204.6 #) 0.03464 PIMS default KSCF at 60 deg F, 1 atm. Short Ton (2000 #) 0.03818 KSCF at 32 deg F, 1 atm. K# 0.08066 M3 at 0 deg C, 1 atm. Metric Ton 0.001292 Example equation for GVTW in kg / cubic meter: Kg / M3 = 1000 * (0.001293 / ( 1 + 0.00367 * T)) * ( P / 760) T = temperature in degrees C, P = pressure in mm Hg Source: Handbook of Chemistry and Physics (47th Edition), The Chemical Rubber Company (CRC) Keywords: GVTW conversion model setting JP- References: None
Problem Statement: During model execution two error windows pop up and the run stops. First you see: When you click OK, you get: The PIMS ExecutionLog.lst shows one of the following messages depending on which optimizer was used: XPRESS Run: PIMSLP version 17.1.10 incorporates XPRESS-MP version 18.00 ?153 Error: Illegal card at line 1026 CPLEX Run: PIMSLP version 17.1.10 PIMSLP incorporates CPLEX version 10.1.1 Selected objective sense: MINIMIZE Selected objective name: OBJFN CPLEX Error 1434: Line 1026: Couldn't convert '-Infinity' to a number.
Solution: This can be caused by extremely large values in T. PGUESS when they are saved from !PGUESS of unsuccessful runs. 1. Examine and correct the values in T.PGUESS, or 2. Find and use a previous copy of T.PGUESS. Keywords: PGUESS aborted infinity illegal 153 1434 References: None
Problem Statement: V7.1 of Aspen PIMS Advanced Optimization now allows Aspen PIMS to utilize multiple processors on computers so equipped. This allows for significant reductions in
Solution: time.Solution Use of this feature requires the following: Multi-core machine PIMS Advanced Optimization license Model using XNLP and the new V7.1 XLP matrix generator This feature is available either while running case stacking or while running multi-start global optimization. PIMS will by default use all available processors, however you can select the number of processors for it to use if desired. When using parallel processing, PIMS will generate all the cases before any of them are run. This allows for early detection of any matrix generation errors and less rick of such an error interrupting the case stack. To turn on this feature for case stacking, go to MODEL SETTINGS | Non-Linear Model (XNLP) | General tab and select the desired number of processors. The screenshot below was from a machine with 2 processors. To turn this feature on for Global Optimization, go to MODEL SETTINGS | Non-Linear Model (XNLP) | Global Optimization tab. Again, select the desired number of processors from the drop down list. During a case stack run using parallel processing, the execution log will display how the cases were allocated. As a processor completes a case, it will be assigned a new one until all cases have been processed. Below is an example of the execution log from a machine with 8 processors. Keywords: XNLP parallel processing multi-core dual-core References: None
Problem Statement: One of the Aspen PIMS Family products (PIMS, ORION, MBO, or DPO) cannot find a license and will not start. All the typical items like license file configuration and SLM Configuration Wizard setup are correct. There is other software on the machine that also uses SLM licensing (for example, some KBC software). For details about checking basic license setup please refer to
Solution: 122853.Solution Some products that use SLM licensing setup an environment variable called LSHOST. If this is defined, then it will override the SLM Configuration Wizard settings for determining where the license should be. We have seen that some KBC software uses SLM licensing and defines the LSHOST variable. The SLM used by PIMS/ORION will also recognize this evironment variable and obey its settings. To check this: 1. On your main desktop, right click on the My Computer icon, and select Properties. 2. Select the ADVANCED tab. 3. Click on the Environment Variables button. 4. Under the section called User variables for.... check to see if you have a variable called LSHOST. 5. If it exists, make sure you append the value with the path (or server name) for the license file that you are using. Do not delete any values that are already there, simply append the PIMS license file location. Keywords: SLM LSHOST Environment variable license References: None
Problem Statement: An important part of the distributive recursion process is the error distribution, i.e. when using recursed properties in a downstream destination the error associated with the recursed value is distributed too. The impact on convergence and on local optima of the guesses of the error distribution coefficients is similar if not more important than the initial property guesses from table PGUESS. When there are cascaded pools, the error distribution problem is amplified. What are cascaded pools and what is their impact on the convergence of an Aspen PIMS run?
Solution: Note:Solution 125804 provides a Report Writer Template to identify cascaded pools in an Aspen PIMS model. Cascaded pools are those where one or more of their components are pools themselves. In this case, there is an error distribution coefficient from the component (source) pool to the destination pool. If the source pool can go to multiple destination pools, and there are several layers of cascaded pools, the convergence can potentially suffer, because Aspen PIMS has to guess and recalculate the error distributions coefficients at every recursion step. If the source pool has only one destination, then there is no problem with the error distribution (the value is 1), but this situation is not very usual. If there are multiple layers of cascaded pools, the problem is magnified, because an incorrect amount of error distributed into a destination pool (i.e. an error distribution that is not proportional to the flow) will affect the selection of the components of that pool. Every new cascaded pool layer amplifies this problem. An example of three layers of cascaded pools is shown below: First Pool HN1 is a swing cut made from the contributions of the crudes (ARL, ANS, NSF). It can go to destination pool LD1 and an additional destination. Second Layer Pool LD1 is a pool made of pools HN1 and HD1. There is error distribution from HN1 and HD1 into LD1. These error distributions coefficients must be proportional to their flow contribution to LD1. Third Layer Pool KTF is a third layer cascaded pool, i.e. the error from HN1 goes to LD1 which distributes to KTF. It also receives error distribution from pool LD2. Modelling recommendations Three layers of cascaded pools are rather common in modelling: for example a swing cut in the crude unit is a pool, which goes into an adjacent cut which is also a pool (second layer), and this cut forms a feed pool to a process unit (third layer), as shown in the figure above. More than 3 layers should be avoided or minimized if possible to reduce the impact this kind of structure has on convergence and local optima. It is also important to avoid too many destinations for a given pool, as it may lead to a weak decision tree and the error distribution calculation may become more prone to oscillations. For example, sending a blending component to too many final blends is not recommended. Keywords: Recursion Convergence Local Optima Recursed Error distribution References: None
Problem Statement: When executing a PIMS-MIP model, optimization stops with the comment problem is cutoff as shown below in a excerpt from an execution log: Its Obj Value S Ninf Nneg Sum Inf Time 0 52.224469 D 98 0 478.664537 0 100 1601.008710 D 166 0 123.441184 0 200 1115.860672 D 111 0 12643.26409 0 253 -568.128097 D 76 0 1774.640576 0 Uncrunching matrix 253 -1281.502224 D 92 0 19415.10877 0 Problem is cut off End optimization --> Friday, May 24, 2002 10:58:31 AM Run End : Friday, May 24, 2002 10:58:35 AM Run Time: 00:00:24
Solution: Go to MODEL SETTINGS, then L.P., and on the MIP LIMITS tab, check to see if there is a value designated for parameter CUTOFF. This parameter sets the minimum Objective Function a node is allowed to have. If a node's objective function is below this value, that node will be cutoff. The default is to leave this parameter blank. However if a zero is entered and the first pass objective function is negative, as it was above, then PIMS will cutoff that node and not continue to the next optimization pass. Note: The CUTOFF parameter is applicable for models using the XPRESS optimizer. For models using the CPLEX optimizer, the parameter is called LOWCUT. Keywords: PIMS MIP XPRESS CUTOFF LOWCUT References: None
Problem Statement: If you are having problems or getting error messages when installing Aspen PIMS Family products, follow the steps below, provided that you use a domain account with Administrator privileges on that computer.
Solution: 1. Uninstall 2. Turn off any antivirus 3. Enable verbose logging. To do this, you will need to set a registry setting: New STRING, HKLM\Software\AspenTech\Setup\EnableLogging with value =1. Also, when you are done with logging the error, you will need to delete the entry and not just change the value. The log will be at least a few MB in size and could be much bigger. The log will be in the %temp% folder and with the name of the product. 4. Install again. This time, make sure that on the feature selection view, you select This feature, and all subfeatures, will be installed on local hard drive., not This feature will be installed on local hard drive.. Because of the logging, installation may take a long time so please be patient. The log file created could give us more information about the error message that you are receiving. If you would like a consultant to review it, please send it to [email protected]. Keywords: References: None
Problem Statement: V7.2 では Create MpsBcd (結果を含むマトリックスファイル) の設定はどこのあるか? 以前のバージョンでは実行ウインドウの下部に位置していた。
Solution: Create MpsBcd の設定は現在 Model Settings | Reporting | Output 以下に位置している。 またRun ウインドウの右側のReportingオプションをクリックすることで設定を開くことができる。 Keywords: JP- References: None
Problem Statement: What can cause this Visual Fortran error in Windows 7 and how can I fix it? Visual Fortran run-time error: forrtl: severe (9): permission to access file denied, unit 7, file d:\economics\post px4\generalized case\standard model\MODIFY.DAT
Solution: This issue can be resolved by turning off file indexing. Follow the steps below: Step 1: Turning off indexing in the working folder. 1) Right click on the folder where you have your Aspen PIMS model and select Properties. In this example it is assumed that the Aspen PIMS model resides in a folder named Users: 2) Click on Advanced: 3) Uncheck the option Allow files in this folder to have contents indexed in addition to file properties. Step 2: Turn off indexing in Control Panel. 1) From the control panel click on Indexing Options: 2) Select the folder (Users, in this case) where you put the Aspen PIMS model and click on Modify. 3) Make sure the Users folder is unchecked. Step 3: Modify Windows Search properties. 1) Type in services from the Windows Start Menu and select services 2) Click on services 3) Double click on Windows search. 4) Select Manual in the Startup type and click on Stop and Apply. Reboot the machine and run the Aspen PIMS model. This should resolve the problem. Keywords: Visual Fortran in time error, PIMS crash, PIMS Windows 7 crash, Fortl: severe (9), modify.dat References: None
Problem Statement: What rounding may occur when your feed exceeds 1,000,000 in a unit?
Solution: PIMS will round the last digit to the 6th digit when the number exceeds 1,000,000 (ton or BBL) The reason is that the old matrix generator in PIMS produces the matrix contained in the MPSPROB.MPS file using Fortran. The Fortran complier has a limit of single precision, meaning that the numbers written into the MPSPROB.MPS file (in scientific notation) can only have 6 significant digits. Let's take an example of a fixed feed ANS, set to be 1,000,714. This number will be represented as 0.100071E+004 (In PIMS, the feed is entered as thousands in unit). This is the most precision one can get for this number in the matrix with the Fortran compiler. PIMS v7.1 and higher include a new matrix generator by XNLP that provides higher precision because it uses C++ instead of Fortran. Therefore, the rounding issue is resolved but theSolution requires the users to have XNLP because the new matrix generator comes with XNLP. If you continue to use DR in PIMS without XNLP, the problem can not be resolved, even in v7.1. To select new matrix generator in PIMS v7.1, go to General Model Setting | General tab, after choose XNLP, check option box of new matrix generator below the option box of XNLP. If you do not want to use this new matrix generator and still want to use a version prior to v7.1, a work around option exists that still requires the user to have XNLP. In table XBOUNDS (which is read and processed in C++ instead of Fortran), you can add a row PURCANS and columns MIN and MAX or FIX with values of 1000.714. The resulting problem will then solve to the correct value. Keywords: Rounding Exceed Fortran compiler C++ New Matrix Generator XNLP References: None
Problem Statement: How are BLNTARG penalties calculated?
Solution: BLNTARG table defines target recipes for specification blends. However, the target recipe may not be feasible as it might not meet the specifications of the blend. In such a scenario, it may incur penalties. The columns UALL, DALL, UBBB, DBBB represents the penalties. BBB is the specific blend name. In the example below, it is for the product UPR. *TABLE BLNTARG Table of Contents * Target Blending Requirements TEXT LRG URG UPR UALL DALL UUPR DUPR *** * IC4 Isobutane 0.10000 0.10000 NC4 Normal Butane 0.10000 0.10000 LN1 Light Virgin Naphtha 0.21000 0.14000 0.10000 0.10000 HCL Hydrocracked Naphtha 0.10000 0.10000 LCN Light Cat Naphtha 0.29000 0.36000 0.10000 0.10000 HCN Heavy Cat Naphtha 0.10000 0.10000 RFT Reformate 0.74000 0.28000 0.27000 0.10000 0.10000 0.30000 0.30000 ALK Alkylate 0.23000 0.28000 0.10000 0.10000 *** UALL, DALL: The numbers under the column represent the penalties. UALL represents penalty if the volume% of the stream is higher than that mentioned as the target in the table BLNTARG. For example, the reformate (RFT) in the UPR is targeted to be 28%. However, in the actual the percentage if 35.28. Since this is higher than the target the penalty of 0.1 mentioned under the UALL column is used. DALL represents penalty if the volume% of the stream is lesser than that mentioned in the target. Note that UALL and DALL is for all the blended products. UUPR, DUPR: These are similar to the UALL and DALL but these are specific to the blended product UPR. Numeric entries under this column are the penalties that override the default penalties specified in the UALL or DALL columns. Product: UPR Premium Gasoline Component to Blend Target Recipe Actual Recipe Penalties Vol% BBLS/DAY Vol% $/DAY NC4 Normal Butane 976 6.50 LCN LCN (C5-350F) 36.00 4,199 28.00 120.070 ALK Alkylate 28.00 4,606 30.71 40.588 RFT Reformate 27.00 5,219 34.79 350.746 Total 91.00 15,000 100.00 511.404 How are Penalties Calculated? Consider LCN in the following example. The target recipe is 36 volume %, the actual volume % is 28. The Penalty = (0.36 - 0.28)*0.1*15000 = 120. The 0.1 is the penalty defined under DALL for the stream LCN. For RFT, the penalty defined under UUPR, 0.3 is considered. The penalty is calculated as follows: (0.3479 - 0.27)*0.3*15000 = 350.55. Keywords: None References: None
Problem Statement: What is the difference between all the matrix files that are on the model tree?
Solution: MPSBCD - For models running with Distributive Recursion (DR), this file contains the data for the solved case. MPSPROB - For models running with DR, this file contains the initial matrix - noSolution values. Xmps001.xlp -- For models running with XNLP or XNLP with XLP, this file is the solved point and contains data that matches theSolution for the designated case. Xlp_new001.xlp and xmps_new001.xmps - For models running with XNLP with XLP, these are two different formats of the same file. These are the generated initial point, therefore they are not expected to match the convergedSolution. The generation of these files can be suppressed by de-selecting the Save Case Specific XMPS Files option under XNLP Model Settings. Keywords: xlp MPSBCD MPSPROB References: None
Problem Statement: In the Validation.lst report, section Miscellaneous will report the model input tables designated in table PRNTABS. The purpose of this report is to see the data as Aspen PIMS sees it, which helps to track errors in the input tables (e.g. hidden columns that designate the end of the table, broken links to other sheets, etc.) In this table you indicate the Aspen PIMS name of the table as rows: tables BOUNDS, PGUESS, PDIST and PCALC will be reported because of this. In the case of the static property tables (BLNPROP), you have to call them as described below. For information on how to use table PRNTABS to report crude assay data from table ASSAY, please refer to
Solution: 126032. Solution To report the static property data from table BLNPROP, you have to indicate table BLNALL (which is the internal name for the combined BLNPROP tables). This is a screenshot for table BLNALL in the Validation report: the combined information from all tables attached to BLNPROP is shown. Keywords: Table PRNTABS Validation report Model Validation References: None
Problem Statement: Virtual Pools can be used to replace physical pools created for composition tracking. This is normally used to depool or split the pool downstream in the proportion of it components. Virtual Pools are created through table VPOOL. The structure created to track the composition and depool downstream when applying Virtual Pools can lead to infeasibilities as it is adding constraints to the model. To overcome these problems, the VPENALTY setting (Virtual Pooling Penalty) can be used to penalize the virtual pooling structure for compositional violations.
Solution: VPENALTY can be enabled under Model Settings | Recursion | Penalties. By default, the setting is activate with a value of 10. The effect of the setting is that infeasibility breakers are incorporated into the depooling structure. These transform the hard constraint of having a unique composition for the virtual pool in all destinations to soft constraints, i.e. it allows for deviations of the original composition in the different destinations. It pays a penalty for not keeping the same composition everywhere, the amount of this penalty is the VPENALTY value. If this penalty is active, it will be highlighted in the first page of the FullSolution report, and the details will be listed in the Penalties section. In this case, review all constraints on the member of the virtual pool in the sources (Purchases, Submodels) and the destination (Sales, Blending, Submodels) and relax them to appropriate values. Note: For additional information about infeasibility breakers and penalty structures reviewSolution documents 127440 and 126938. Keywords: VPOOL Virtual Pool Penalty Infeasibility Breakers References: None
Problem Statement: How can you report properties of a group of blends, e.g. the pool of all gasolines, with Report Writer?
Solution: The attached Report Writer template and database highlight two ways of reporting properties for a group of blends. 1. Easy Way: properties calculated by Aspen PIMS from group blending specifications You need to set up group blending specifications for the streams and properties you are interested in. SeeSolution 128155 for a description on how to apply Group Blending Specifications. The resulting qualities for these groups can be accessed through the RW function ATDSPGroupedStreamsQualities(). There are properties blended in volume (ARO, BNZ) and in weight (SUL). The necessary reporting structure is shown in sheet GroupProperties_FromGroupSpec in the template. The example is for the pool of gasolines. If you want to get results from other groups, copy the block of rows 19-30 and paste it below, then change the Group Number in cell D20 to the appropiate value and change the descriptions of the group. 2. Hard Way: properties calculated in the report from the properties from the individual blends For this approach, you still need to have groups of sales defined in tables GROUPS and SELL. You do not need Group Specification, nor do you need to explicitly define the group members in table GROUPS. The necessary reporting structure is shown in sheet GroupProperties_CalcFromComp in the template. In this case you need to first write the properties of all the members of a group and then calculate the overall quality of the pool by doing the linear blending calculation. In this case, for each group of blends, you will have one block per property: there are examples of blending in volume (ARO, BNZ) and in weight (SUL). It is clear that the best approach is to modify the Aspen PIMS model to incorporate the Group Structure (1st approach) rather than doing the calculations externally. Keywords: Group Specs Group Properties Group Qualities Quality Property References: None
Problem Statement: There is an error that pops up when I test the Integration connection to transfer assay data from Aspen PIMS to Aspen Petroleum Scheduler (APS). The service is running, so I stopped and restarted it, but I still received the same message: Message 1 (indicates there is an issue) Cannot open OrionSvcHost.exe service on computer Message 2 (indicates it was successful) Connection successful!
Solution: There are two things to verify when this error occurs during the connection test: 1. If the DSN is created as trusted connection the username/password fields must be left blank in the configuration wizard when selecting the dsn. 2. When the configuration wizard says unable to start or connect to OrionSvcHost.exe,then it means any changes we made in the configuration were probably not read by the service. Then, restart the service manually. Keywords: integration References: None
Problem Statement: Running Case Comparison, I get the message below in Excel. How can I resolve this?
Solution: In the Aspen PIMS model settings under Reporting | Miscellaneous, select the option Use Excel to createSolution spreadsheets in current Excel format Keywords: None References: None