question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
|---|---|
Problem Statement: How can I choose my own color scheme for the Procedure, Operation and Phase levels in the Order Tracking module? | Solution: AeBRS allows you detailed control over the display colors used in the Order Tracking module.
Typically, the default colors should meet most needs. However changing colors might be useful to conform to a corporate standard, or perhaps to accommodate a user who is not able to differentiate between certain colors.
UNDERSTANDING HOW DEFAULT COLORS WORK
The set of default colors are specified in the language resources files. On a system using English, the default language resources file, resources_en.properties is located along this path:
C:\Program Files\AspenTech\AEBRS\resource\resources_en.properties
In that file, search for 255 to quickly move to the relevant section. Scroll another page or so to the specific section:
# Order Tracking Background Colors
This section has two lists - one used to specify the default colors at the top two levels in order tracking (Unit Procedure and Operation.) The second to control the default colors for the Phase level. A Phase has more potential states than a Unit Procedure or Operation unit, so there are more colors that can be controlled. Let's look at typical default colors from the top level of an order down to a Phase.
First, notice that an In Progress Order has a default color of Dark Blue for the state Initiated | Ready for both the Unit Procedure and Operation:
UNIT PROCEDURE AND OPERATION DEFAULT COLOR
FOR INITIATED | READY STATE
Look at the highlighted line from the Unit Procedure and Operation list:
# Unit Procedure & Operation StepColor = 128, 128, 128
StepColor_ENABLED = 128, 128, 128
StepColor_ENABLED_NOT_READY = 128, 128, 128
StepColor_ENABLED_BLOCKED = 128, 128, 128
StepColor_ENABLED_READY = 004, 174, 004
StepColor_ENABLED_SKIPPED = 128, 128, 128
StepColor_EXECUTING = 255, 000, 000
StepColor_EXECUTING_READY = 255, 000, 000
StepColor_INITIATED = 000, 000, 132
StepColor_INITIATED_READY = 000, 000, 132
StepColor_FINISHED = 095, 095, 095
StepColor_FINISHED_COMPLETED = 095, 095, 095
StepColor_FINISHED_SKIPPED = 095, 095, 095
StepColor_CANCELLED = 140, 140, 140
StepColor_CANCELLED_READY = 140, 140, 140
Looking at the text file it is not easy to understand what number combinations make a particular color. Microsoft's Paint utility can provide an easySolution. Open up Paint, and choose Edit Colors under the Paint Colors menu. Now click on the Define Custom Colors button. The dialog that opens up lets you click and drag across a color palette, or type in the Red, Green and Blue (RGB) values. When we enter 0, 0, 132, for example, we see the StepColor_INITIATED_READY color in the Color|Solid preview pane.
Finally, let's drill down to our Phase:
Notice that our three states:
Finished | Completed
Enabled | Ready
Enabled | Not Ready
correspond to three of the many state colors specified in the Phase section:
# Order Tracking Background Colors
# Phase
PhaseColor_ENABLED_NOT_READY = 128, 128, 128
PhaseColor_ENABLED_READY = 004, 174, 004
PhaseColor_FINISHED_COMPLETED = 095, 095, 095
CHANGING THE DEFAULT COLORS
For our example, let's change the colors so that the Unit Procedure and Operation are both green for an active order, and a Phase that has Enabled | Ready status is orange.
OLD VALUES:
# Unit Procedure & Operation
StepColor_INITIATED_READY = 000, 000, 132
# Order Tracking Background Colors
# Phase
PhaseColor_ENABLED_READY = 004, 174, 004
NEW VALUES:
# Unit Procedure & Operation
StepColor_INITIATED_READY = 004, 174, 004
# Order Tracking Background Colors
# Phase
PhaseColor_ENABLED_READY = 255, 128, 000
Once the file is edited and saved, make sure MOC is closed, then run the codify_all.cmd to compile the changes:
C:\Program Files\AspenTech\AEBRS\cfg_source\codify_all.cmd
When MOC is restarted, the new color scheme will be in effect:
New default color of Green for the Initiated | Ready status for both Unit Procedure and Operation:
UNIT PROCEDURE AND OPERATION SET TO GREEN
FOR INITIATED | READY STATE
New color orange used for Phase in Enabled | Ready state:
Keywords:
References: None |
Problem Statement: In an AeBRS environment, often all the client config files are set to use a shared location. So how can a setting for the local workstation be effective if the config information is all shared? | Solution: The mechanism for sharing configuration information in an AeBRS information is as follows:
On each client, in the file config.m2r_cfg, the CONFIG_PATH key is set to something like:
CONFIG_PATH = \\<myAeBRSServer>\\Program Files\\AspenTech\\AEBRS\\
where <myAeBRSServer> is a shared folder on the server.
A few lines down, the INCLUDE_FILES line defines which configuration file information will be read from that shared location, using the pipe symbol as a delimiter. However, if in the INCLUDE_FILES key a full path is provided, then the share location will be ignored. So if the INCLUDE_FILES KEY looked like this:
INCLUDE_FILES = path.cfg|C:\\Program Files\\AspenTech\\AEBRS\\local.cfg
then they are read like this:
\\MyEBRSServer\\Program Files\\Aspentech\\AEBRS\\path.cfg
C:\\Program Files\\AspenTech\\AEBRS\\local.cfg
EXAMPLE:
The flags.m2r_cfg file contains a Default font family name at the end of the file:
DEFAULT_FONT_NAME = Dialog
Since the CONFIG_PATH is shared, that value will be read from the server. However, if the same key exists in multiple places, it will be read from the share path first, and then the absolute path (i.e. server, then client.) So the final time the key is read will be the value it keeps. So by editing local.m2r_cfg, to add the key, but with a different value:
DEFAULT_FONT_NAME = Arial
A local DEFAULT_FONT_NAME is successfully set.
Keywords:
References: None |
Problem Statement: It might take up to one minute for the EBRS MOC client to open. | Solution: If MOC takes a long time to open, the issue may be a slow connection to the JDK components that are resident on the server. If improving network performance is not an option, then a work-around to the problem is to install the JDK components on each client, and then modify the eBRS configuration files so that the local JDK is the one used by the clients.
Steps to install JDK on an EBRS client and change the configuration files so that the local JDK is used:
Insert the AMS installation CD-ROM for your version of eBRS.
Navigate to the JDK setup directory:
<MyDrive>:\Media\Core\JDK1_4
Run Setup.exe in the JDK1_4 directory and accept all default prompts.
Edit the AeBRS.cmd file, located at:
<install drive>:\Program Files\AspenTech\AEBRS\AeBRS.cmd
on each client for which a local JDK installation is performed. You will change the JAVAW.EXE line to reflect the local JDK install. If you installed JDK to the C drive, then the edited line would be as follows:
SET J=C:\j2sdk1.4.0_01\BIN\JAVAW.EXE
As a last step, if all clients are redirected to a local JDK install, then you can eliminate the reference to the shared JDK on the server (though this is not required.) To do so:
Edit the codify.bat file, located on the server at:
C:\Program Files\AspenTech\AEBRS\cfg_source\codify.bat
as follows:
C:\j2sdk1.4.0_01\bin\java -cp <rest of the line remains unchanged>
Keywords: slow
freeze
unresponsive
initial
initiate
start
References: None |
Problem Statement: When trying to create a Master Recipe (MR) via the API, customer gets an error. What is the minimum XML definition needed to use that function? | Solution: At a minimum, both the ID and the Version of the Master Recipe need to be specified in the XML:
MR name specified in the function call; and
MR version controlled by AeBRS.
The Master Recipe name is required because the BatchML schema dictates it (it is a standard from WBF.)
The version should not be required. This is a known issue (CQ167250) that may be addressed in a future version.
Keywords: 14:06:11: soap called OpenUserConnection with arguments:
14:06:11: Result = 261ADAC6D899CB873650E2032A917633
14:06:11: Diagnose = OK
14:06:11: m2rDatabaseConnection - HttpProcessor[8080][6] TRANSACTION Start:0 14:06:11: m2r.DataModel.m2rSQLDataModel.SQL_GETTIME47.Query:select sysdate from dual 14:06:11: m2rDateField.now()=2004-04-29 14:06:11.0
14:06:11: m2rDatabaseConnection - HttpProcessor[8080][6] TRANSACTION Start:1 14:06:11: DataModel.chkDMAPIActionAudit.EBR_API_ACTION_AUDIT.insertExternalRow:INSERT INTO EBR_API_ACTION_AUDIT (ID_ACTION,API_CALL,RETURN_VALUE,DIAGNOSTIC,PAR_COUNT,AUDIT_USER_ID, AUDIT_DATE,SIGNATURE) VALUES (2239,'OpenUserConnection','261ADAC6D899CB873650E2032A917633', 'OK',0,-1583013783,TO_DATE(SUBSTR('2004-04-29 14:06:11.0',1,19),'YYYY-MM-DD HH24:MI:SS'), 4099577260)
14:06:11: m2rDatabaseConnection - HttpProcessor[8080][6] TRANSACTION Commit:1 - rollBackFlag = 0
14:06:11: m2rDatabaseConnection - HttpProcessor[8080][6] TRANSACTION Commit:0 - rollBackFlag = 0
14:06:11: soap called createMasterRecipe with arguments:
14:06:11: Arg[0] =<MasterRecipe><Formula><Parameter><ID>fCuve</ID><Value> ;<ValueString>SP05</ValueString></Value></Parameter><Parameter ><ID>fLique</ID><Value><ValueString>LB5</ValueString>< ;/Value></Parameter><Parameter><ID>fQuantite</ID><Value>&l t;ValueString>600</ValueString></Value></Parameter></Formula>< ;/MasterRecipe> 14:06:11: Arg[1]=TEST_MR
14:06:11: Arg[2]=GLUCOSE
14:06:11: Arg[3]=10
14:06:11: Result = 0
14:06:11: Diagnose = OK
14:06:11: soap called GetLastError with arguments:
14:06:11: Result =
14:06:11: Diagnose = OK
14:06:11: null called CloseUserConnection with arguments:
14:06:11: Result = 1
14:06:11: Diagnose = OK
References: None |
Problem Statement: What does Parent Product and Product's Subsystem in Aspen Operations Reconciliation and Accounting (AORA, formerly called Aspen Advisor) mean? | Solution: What is Parent Product?
In AORA, Parent Product defines a hierarchical relationship between different products. For example, three products can be defined as Gasoline, Unleaded Regular, and Unleaded Super. The Parent Product for Unleaded Regular and Unleaded Super can be set to Gasoline. This association is stored in the database and can be used for reporting aggregations of data.
Another example is Crude. There are different types of crude used in the refinery: Arabian, Mayan, and Alaska crude. In this case it's desirable to create a Parent Product called CRUDE that combines all types of crudes. This allows for aggregate data in the reports (for example, a refinery production report) to see the total crude being received.
In the same way, you have grand_parent and great grand_parent, all used by the reports. Aspen Reporter have an option called Number of Parent Levels (File => Preferences =>Display tab) that determines the number of levels shown in a report (Please note that by default this parameter is set to 2).
What is Product's Subsystem?
Product's Subsystem defines whether the inventory of a product is contained in a subsystem object.
Subsystem is grouping of tanks according to product. Subsystems are objects that contain inventories for several tanks. They are mainly used to group tanks where the internal movements between them are unknown, so it's desirable to consider them as one.
A good example is, Company A has several Spherical tanks or bullets that gravitate and have movements between them that are unaccounted or not important. In this case, the several tanks are considered to be one, having the total inventory of the subsystem.
Keywords: Parent Product
Products subsystem
AORA
References: None |
Problem Statement: What algorithm does Advisor use to determine Daylight Savings Time (DST) changes? | Solution: DST switches come from the operating system, and more specifically, the C-runtime libraries associated with the compiler or operating system.
Keywords:
References: None |
Problem Statement: Gauge instruments in Aspen Advisor have a checkbox which says Outage Gauge. See below for an example.
This knowledge base article defines the term outage gauge. | Solution: A typical gauge used for most tanks measures the height of liquid in the tank by measuring the distance from the bottom of the tank to the top of the liquid in the tank. This type of gauge is referred to as an innage gauge. An outage gauge works in somewhat the opposite way from an innage gauge. Namely, for an outage gauge, the height of liquid in the tank is determined by measuring the distance from the top of the liquid in the tank to either the top of the tank or to a reference point near the top of the tank.
Keywords: plant terms
definition
process
References: None |
Problem Statement: This knowledge base article describes the Oracle server and client version combinations that are supported for Aspen Operations Reconciliation and Accounting (AORA, formerly called Aspen Advisor). | Solution: The following versions of AORA support the referenced versions of Oracle database server and client combinations.
V7.3
Oracle 9i Database Release 2
Oracle 10g Database Release 2
Oracle Client 10.2.0.4
Oracle Client 10.2.0.5
V7.2
Oracle 9i Database Release 2
Oracle 10g Database Release 2
Oracle Client 9.2.0.10
Oracle Client 10.2.0.4
V7.1 and 2006.5
Oracle 9i Database Release 2, Oracle ODBC driver 9.02.0.6.5,
Oracle Database 10g Release 2, Standard Edition
Oracle Client 9.2.0.10
Note: Oracle Client must be 10.2.0.4 for Windows Server 2008 to function properly.
Aspen Operations Accounting is a 32-bit application that uses only 32-bit database drivers. When using a 32-bit driver on a 64-bit edition of Windows, use odbcad32.exe to create a 32-bit system DSN.
Please refer to the AORA documentation in the Aspentech Support website
http://support.aspentech.com/
for the Oracle databases we support for versions prior to 2006.5.
Keywords: DB
Relational
Oracle
AORA
References: None |
Problem Statement: This knowledge base article describes how to put Aspen Advisor into debug mode for troubleshooting purposes.
Setting Aspen Advisor into debug mode may impact system performance. This should be done at the recommendation of AspenTech support. | Solution: Aspen Advisor can be placed into debug mode by adding the following entries to the iisys.ini file then restarting Aspen Advisor.
[Debug]
enabled=1
path=C:\AdvisorModels
where path references the folder where you want the debug files to be created.
Note: To disable debug mode, set the enabled flag to 0 then restart Aspen Advisor.
The following debug log files will be generated to the output path specified.
IIDBConnect-DD-MMM-YYYY_vc
TBDB_BASE-DD-MMM-YYYY_vc
TDPlant-DD-MMM-YYYY_vc
where DD-MMM-YYYY is the date that the log file was generated.
An explanation of the information contained in each log file is provided below.
IIDBConnect-DD-MMM-YYYY_vc
Logs Advisor.exe startup information such as values of registry keys that are read on startup
Logs whether or not the database user and password were read from the iisys.ini file
Logs data base connection information
Logs the build date of IIDBConnect.dll (the dll which controls the connection to the database)
TBDB_BASE-DD-MMM-YYYY_vc
Logs the language dll that is loaded by Aspen Advisor (for example, iidblg_EN.dll)
TDPlant-DD-MMM-YYYY_vc
Logs details of the calculations Aspen Advisor executes in the plant dll (iipl.dll) and in the equation dll (iiequa32.dll)
Logs intermediate calculation values when multi-step calculations are executed.
The information in this log file is logged to assist support/development with troubleshooting. Therefore, customers may not be able to interpret all of the intermediate values generated by this log file.
Note: In order to have calculation details logged to the TDPlant log file, you must make Aspen Advisor execute the calculation while debugging is enabled. For example, if you wish to view details of the vapor space calculations for the LPG equation of state you will need to open an instrument reading (for a product which uses the LPG equation of state) so that Aspen Advisor will calculate the corrected volume and mass for the instrument. The results of these calculations will subsequently be logged to the log file.
Keywords: debug
log
record
calc
EOS
type
References: None |
Problem Statement: This knowledge base article explains which timestamps should be given to continuous flow readings and to inventory readings. | Solution: Inventory readings are typically given the timestamp which corresponds to the last minute of the day. If the accounting day begins at midnight then inventory readings are typically timestamped for 11:59 PM. However, this is not absolutely necessary. In fact, when Aspen Advisor Connect retrieves the inventory readings from the historian the most recent value in history for the accounting day is retrieved. Similarly, if more than a single inventory reading is entered for a given day the most recent value will be used as the vessel's end of day inventory measurement.
Continuous flows must be given the timestamp which corresponds to the first minute of the accounting day. This is necessary because continuous flows must span the full accounting day. When Aspen Advisor Connect retrieves the average flow value from the historian the flow reading is automatically timestamped for the beginning of the accounting day. However, when using tools such as the Aspen Advisor Excel Add-in, users must be careful to specify the timestamp of the continuous flow as the beginning of the day. Otherwise, the expert system will not recognize a continuous flow if the reading does not have a timestamp which corresponds to the beginning of the accounting day.
Note: Although continuous flows must be given a timestamp of the first minute of the accounting day, flows created as user-defined events may have any beginning or ending timestamp. This is the case because events are flows which are designed to occur for less than an entire accounting period.
Keywords: time
stamp
time-stamp
References: None |
Problem Statement: This knowledge base article describes how Aspen Advisor processes events when span more than a single accounting period. | Solution: Aspen Advisor will separate the amount of material moved through a pipe during an event based how long the event flow occurred during each accounting period while assuming a constant flow rate. The following example demonstrates this behavior.
In the example below an event flow of 10,000 barrels (Bbls) starts at at 12:00 on April 10th. The event flow ends at 12:00 the following day, April 11th. The beginning of the accounting day is at midnight (00:00) so the event will span 2 accounting periods. This event will exist for 12 hours in each of the 2 accounting periods.
The first dialog box shows the details of the manually created event.
The next two images highlight the fact that the event flow starts on April 10 at 12:00 and ends on April 11 at 12:00.
The next image shows that the corrected volumetric flow which occurred for the entire event is 10,000 Bbls.
Note: When the event or the instrument reading is viewed on either April 10th or April 11th, the entire event flow amount of 10,000 Bbls will be shown. It is Aspen Advisor's expert system which separates the single event into multiple events. The time-weighted flow values will only be shown by the expert system displays.
When the event is reconciled by the expert system the event flow will be divided into proper amounts for each accounting day. The true time-weighted flow value will be displayed by the expert system dialog boxes and reports for both accounting days. This is illustrated below by the expert system values dialog box for the pipe which was used by the event. Since the flow occurred for 12 hours of each accounting day, 5,000 Bbls is allotted for the event flow for each accounting day.
Keywords: separate
apportion
portion
divide
References: None |
Problem Statement: How do I create a Demo Database to use with Aspen Operations Reconciliation and Accounting (AORA)? | Solution: AORA installation comes with an executable Demo Database.exe that can be used to create a demo model for learning/ demonstration / troubleshooting purposes.
This executable is located in the following folders when using
32 bit Operating System:
C:\Program Files\AspenTech\Advisor\Documents
64 bit Operating System:
C:\Program Files (x86)\AspenTech\Advisor\Documents
Extracting the Demo model:
To extract the Demo model, you need to double click on the executable Demo Database.exe. After this, it creates a demo model in the same folder with name Demo.mdb
Setting up a Demo model for use:
In order to start using this model with AORA, create an ODBC Connection pointing to this MS Access Database and then open the Model from AORA. Please referSolution 102730 for more information on how to set up an ODBC connection.
Keywords: Demo model
Installation
setup
References: None |
Problem Statement: This | Solution: outlines the best way to get the raw data back into Aspen Advisor even after you did Reconciliation (Initialize, Reconcile and Save) for the data come in on that particular day?Solution
Please note that the following steps requires a user with superuser privileges to be logged into Aspen Advisor Model.
Once logged into Aspen Advisor Model, go to File --> Preferences -->Expert tab
In the Expert tab uncheck Load user and system adjustments and check Delete saved results from all zones
Restart the Expert System and do an Initialize and then Save but don't do Reconcile
Stop the Expert System back again by unchecking the Expert system from Tools Menu
Reset the File -->Preferences by unchecking on Delete saved results from all zones and then check Load user and system adjustments
If you restart the Expert System again after following the above steps, only the raw data will be there and you can start any adjustments from the scratch again.
Keywords: Raw data
Expert
IRS
Reconcile
Initialize
Save
References: None |
Problem Statement: An automated install (also known as a silent or unattended install) can be desirable when many clients need to be deployed. Does AeBRS support this method? | Solution: Version 7.0 is the first version to support a silent install method.
Keywords: installation
enterprise
deploy
References: None |
Problem Statement: Customers have inquired to find out if there are problems with certain versions of Adobe Acrobat. | Solution: Even though the AeBRS Installation Guide for version 6.0 specifies version 4.0 or 5.0 of Adobe Acrobat, there have been no reported problems with later versions of Acrobat.
Keywords:
References: None |
Problem Statement: Exception messages written to the APIServer debug file may sometimes indicate a problem with the product or the operating environment. However some exception reports may occur that do not indicate a problem or cause the product to operate outside its design specification. This | Solution: collects various types of exception reports that are acceptable, and provides explanations for each.
Solution
13:41:58: AeBRSNotifier: Client Listener Exception activation listener:java.net.SocketException: socket closed
This exception happens when the listening sockets is closed from the other side of the connection. For example, ExecuteOper() creates a listener to get the result of a phase start and then discards it (thus closing the socket.)
17:59:38: Exception java.lang.NullPointerException at recipe.basicNotificationManager.notify(basicNotificationManager.java:158) at Notifier.socketConnection.run(socketConnection.java:64)
This null pointer exception occurs because of a synchronization issue. A redesign in Version 6.0 has eliminated these type of exception reports.
Keywords:
References: None |
Problem Statement: The message The Expert System option was not installed can be returned for several reasons. This article describes the various circumstances under which this message can be displayed to the user. | Solution: 1. As of Advisor 8.0, the Expert System is licensed separately from the model configuration tool. If a user attempts to load the Expert System on an Advisor installation where the Expert System was not installed, this message will be generated. This is the intended purpose of this message.
2. If the user goes to File | Trace and enables ODBC tracing, clicks on the ... button to change the filename/location, then tries to load the Expert System, this message will be generated.
Note: If the user follows all of these steps except does not press the ... button, everything works fine. The workaround is to always use the default location for the ODBC trace file.
3. If the user launches Advisor from the Advisor task in BPE, then attempts to load the Expert System, this message will be generated. If the user wishes to launch Advisor through BPE, the workaround is to configure a BPE 'Generic' task which points to adv32.exe instead of using the 'Advisor' task.
4. If the user runs a batch script (which launches the expert system) from a directory other than the main Advisor directory, this error message can also be returned. Executing a batch file (Tools/Batch Run) can change the directory to that of the batch file, thereby preventing the system from finding and loading the Expert System.
The expert system assumes the current directory is the Advisor directory when it loads. Scenarios #2, #3 & #4 change the current directory from the Advisor directory to another directory.
Fixed in Version
Scenarios #2 and #3 are being tracked in defect CQ00190232. An ER is tentatively scheduled for release in January 2005.
Keywords:
References: None |
Problem Statement: When running an Advisor model, it should always open on the most recent operating date which should be the current accounting date. Sometimes, due to operator error or system failure, the model opens with a different date than expected. The question arising in this situation is:
How to change the Operating Time of a model? | Solution: In order to change the Operating Time of a model, you can click on File | Time | Change Operating Time... from the Advisor GUI to set the operating date to the correct date. When the automated batch scripts in Advisor Connect run to import data from the historian, they advance the operating time by one day. So, for example, if the operating time is 10 Jun 05, when the scripts run on 12 Jun 05, it will change the model date to 11 Jun 05 and get the data for 11 Jun 05.
It is important to leave the operating date set to the current accounting date when you are finished working with the data. Otherwise the data that gets imported will be for the wrong date.
The operating date of a model can be changed from the Advisor GUI by clicking on the calendar icon. You might receive two messages: You have crossed time intervals. Do you want to continue? If you answer Yes to this question, then the second question is: Do you want to change the operating day? Under normal circumstances, the answer to this question should be No. The only time you would answer the question in the affirmative is if you really intended to change the operating date of a model.
Note of caution: before you change the operating date of a model, just make sure you know where you leave the model when you finish.
Keywords:
References: None |
Problem Statement: Sometimes, when trying to save the reconciled results, a random error message may appear in Advisor. The error reads,
Cannot connect to target model: AdvUtilP; Unknown Exception Critical Failure! System Shutting down
and then the Advisor GUI disappears. | Solution: The problem is usually caused by insufficient amount of Random Access Memory (RAM) on the PC running Advisor. TheSolution is to add more RAM on the PC.
Another possibility is an intermittent network problem, which can results in temporary inability to access Advisor database.
On rare occasions the above error has also been linked to the missing time portion of the timestamp (a timestamp with a date but no time) in some import tables (such as IVRPROP - properties import table). This could be troubleshooted by turning the ODBC trace on to see the different queries.
Keywords:
References: None |
Problem Statement: The Expert system documentation incorrectly described the behavior of 'Use Estimated Events' in versions prior to v.8.2. The description below correctly describes how estimated events are treated when the 'Use Estimated Events' expert option is checked. | Solution: When the Use Estimated Events option is checked in the Expert | Preferences | Expert dialog box, all estimated events are treated by the expert system exactly as though they are firm events. When the Use Estimated Events option is NOT checked, the expert system treats all estimated events as true estimated events. Namely, it gives the estimated events a much higher probability of adjustment by the expert system.
Keywords: None
References: None |
Problem Statement: This knowledge base article describes the steps to follow when creating a new strap table in Aspen Operations Reconciliation and Accounting (AORA). AspenTech recommends creating new strapping tables when updated tables are available for a tank unless specific site plans to modify one or two points in an existing strapping table. | Solution: Step
Directions
1.
Log into AORA and go to Configure --> Global --> Straptables.
2.
A list of all the strapping tables currently configured for the AORA model will show up in the Straptables Listing dialog box .
3.
Click the ADD button to add a new strapping table. You will be prompted for a name and description for the table. Please ensure that this name is unique.
4.
Once you press return (Enter key), you will be asked for the configuration information specific to this strapping table in the Details tab (e.g. interpolate between points, adjusted for the weight of the roof, etc). Fill in the information that is appropriate for this new table.
5.
Click on the ADVANCED tab and note the DBINDEX for the newly created strapping table.
6.
Go to the specific tank and assign the new strapping table to the proper decimal gauge.
To do that, go into the AORA model and go to the actual tank. Click on the fractional gauge instrument --> click on the Details tab --> in the Straptable field, link it to the new strapping table from the list.
Repeat the above step for the gauge instrument.
7.
Enter the strapping table coordinates on the Strapping Table worksheet in this spreadsheet (decimal heights and liquid volumes).
8.
Ensure that each row for the strapping table has the DBINDEX for the newly created strapping table in the IND2STRAP column.
9.
Also make sure that an INSERT statement is generated for each point in the strapping table.
10.
Open DBTOOLS and log into the appropriate model. You must log into DBTOOLS with the superuser password.
11.
Cut the required INSERT statements from the Strapping Table sheet of this spreadsheet and paste them into the QUERY tab of DBTOOLS.
12.
Important: IF THE DBINDEX IS WRONG, YOU MAY OVERWRITE THE DATA CURRENTLY IN THE TABLE. PLEASE MAKE SURE THAT THE DBINDEX VALUE IS CORRECT BEFORE EXECUTING THE INSERT STATEMENTS.
13.
Press the execute button ' !' To run the query and check the messages for errors.
14.
Once the query is executed, the new strapping table values will be available within AORA.
Keywords: None
References: None |
Problem Statement: This knowledge base article describes what can cause the error message
Unable to initialize math solver
when the Aspen Least Square Reconciliation (ALSR) engine is executed on a model. | Solution: This error has been seen to have the following two causes:
1. The ALSR engine encountered an object name which contained a character that it could not process. This has been observed to occur when pipe, instrument or vessel names contain various non-English characters.
2. The ALSR engine encountered a modeling situation for which it was not designed. This can occur, for example, if a pipe contains multiple integrator instruments of the same type, one of which has a beginning and ending integrator value of zero.
Additional information about the error can be obtained by examining the three ALSR output logs. These log files are found in the following folder:
Program Files\AspenTech\Advisor\Expert
The ALSR output log files have the naming convention ASRC_XXX. To use these files for debugging purposes, scroll to the bottom of each file to determine the last object that was processed by the ALSR engine. If no message is present to indicate the source of the problem then examine the last object in the file which was processed by the ALSR engine for configuration abnormalities.
Keywords: None
References: None |
Problem Statement: Why does my Aspen Advisor Database still include some or many of the Aspen Advisor (Report) Temporary Tables after running the Standard Aspen Advisor Database Reports, or in some cases when I have run Custom Reports or even after I have tried running DROP TABLE queries to delete these Tables? | Solution: NOTES:
The Temporary Tables in question here are the tables where the table name starts with R.
You first need to confirm which Standard Reports and Custom Reports (if any) your site uses and runs on a regular basis. Once confirmed, those reports should then be the source of most if not all of the R Temporary Tables in the Advisor Database. If you have any other interfaces developed by third parties that interface with Advisor or Crystal Reports to generate Custom Reports, then AspenTech cannot know what they might create in regards to Temporary Tables or how they should get cleaned up if such tables are created as R Tables by the Custom Reports.
The Temporary Tables get created when users run reports, and Advisor should be deleting them automatically each time a report is executed successfully as long as NONE of the EXCEPTIONS Listed below are TRUE.
This automatic deletion of the Temporary Tables should apply to Custom Reports as well, as long as they were created with Crystal Reports version 8.5 or earlier (preferably version 8.5) or created by modifying one of the Standard Reports using Crystal Reports version 8.5 or earlier.
If the Aspen Advisor Reporter is run in Design Mode, i.e., if the Set the reporter into design mode option is checked, then the Temporary Tables generated are NOT DELETED and instead remain in the database following report execution and thus, you may want to make sure that no one is running the Aspen Advisor Reporter in Design Mode in addition to the other items shared in the Exceptions List provided below. The Design Mode should technically only be used if you are designing Custom Reports, as this mode allows you to view the Temporary Tables and Fields generated and used by the Reports, which is useful if you are designing reports because you can then view the tables and fields to determine which elements you want to put in your customized report.
Likewise, if the Generate All Temporary Tables. option is checked then the Temporary Tables generated are NOT DELETED following report executions. This option is only available if you have selected the Design Mode option. When this option is set, when you print one report Aspen Reporter generates all of the temporary tables with data.
EXCEPTIONS LIST for cases where the Temporary Tables may or will NOT be DELETED:
As mentioned above, the Temporary Tables get created when users run reports, and Advisor should be deleting them automatically each time a report is executed successfully UNLESS one of the following situations is TRUE.
1. If some of these tables are Custom Temporary Tables that your site has created for any custom reporting that your site may use, and they were NOT created using Crystal Reports 8.5 or earlier, preferably version 8.5).
2. If anyone is accessing the Aspen Advisor Database and running reports at the same time as you are attempting to execute the Query to Delete the Temporary Tables.
3. If a user tried to run a report and the report generation failed for some reason.
4. If the Design Mode option Set the reporter into design mode. or the Generate All Temporary Tables. option is set / checked when running reports then this will cause the Temporary Tables to remain in the Aspen Advisor Database until the tables are deleted regardless of whether the same reports are executed again without those options being set / checked. If either of these options were checked when you executed the reports, then there will be Temporary Tables remaining in the Aspen Advisor Database and they remain in place until you run and complete the required delete query and procedures to DELETE them from the database.
With that said, as long as users are not actively running reports while you attempt to execute the delete query if needed, i.e., the combined query including individual DROP TABLE query commands for each R Table, then if NONE of the other EXCEPTIONS listed above are TRUE you should be able to delete any Temporary Tables created by running the Standard Advisor Reports as often as you wish without causing any problems to the Aspen Advisor Database or the Aspen Advisor Reports.
The screen capture below shows the two Aspen Advisor (File | Preference...) options mentioned above that, if checked, will result in the Temporary Tables generated by the Aspen Advisor Reporter NOT being DELETED when reports are executed.
Keywords: Aspen Advisor
Delete
Reporter
Temporary Tables
References: None |
Problem Statement: Occasionally within the Manufacturing Industry companies are bought and sold. The sales contract between companies often do not include execution rights to third party software. Therefore it becomes necessary to determine which workstations need to have the software removed. This knowledge base article describes how to determine whether or not Aspen Advisor is installed on a workstation. | Solution: There are several ways to determine if the Aspen Advisor product has been installed on a workstation.
1. Use Windows Explorer to search for any of the executables listed below:
Advisor.exe
SSInterface.exe
Report32.exe
DBTools.ex
If any of these executables are located then the workstation is capable of executing Aspen Advisor functions. To remove the executables from the workstation please do an Un-install of the Aspen Advisor software.
2. Aspen Advisor will appear in Control Panel | Add/Remove Programs.
3. Check to see if Aspen Advisor is listed in the registry under:
HKL|Software|AspenTech|Setup|Products
However, if a customer has repackaged the Aspen Advisor installation using a custom install script (as some companies do) then there's no guarantee that Aspen Advisor will be listed in Add/Remove Programs or in the registry.
A clean un-installation of AspenTech software can be done according to knowledge base article 111129.
Keywords: un-install
SSInterface
DBTools
Report32
registry
References: None |
Problem Statement: If a site is running both Aspen Advisor using Advisor Connect to retrieve tank inventory readings from a real-time plant database, and Pumper Log, there is a possibility that Advisor may end up with two inventory readings for the same tank gauge with apparently identical timestamps but slightly different inventory values. | Solution: The cause of the duplicate time-stamped readings with different values is in the seconds for the reading. In the first case, Advisor Connect uses a time of 23:59:00 to retrieve its readings, while Pumper Log uses a time of 23:59:59. When viewing the readings in Advisor, the two readings will be displayed with an apparent duplicate reading time-stamped as 23:59, but in fact the values will be slightly different due to the slight delay between the two readings.
In most cases, this slight difference in values will not be significant and will not affect the reconciliation or yield accounting balance, given the tolerances usually set for tank inventory instruments.
The correct method of retrieving tank inventory readings would be to use either Advisor Connect or Pumper Log to retrieve the values, not both.
Keywords: Advisor
Pumper Log
tank gauge instrument
instrument readings
timestamp
References: None |
Problem Statement: How does one change the temperature range for an existing product in Advisor? | Solution: To change a temperature range for a product do the following.
Go to Configure | Global | Products...
Click on the P in the product listbox. This will display the properties of the product when the user double clicks on the product.
Double click on the product for which one would like to change the temperature range.
Double click on the Temperature listing. This will bring up a dialog box which allows the minimum value, default value, and maximum value of the temperature to be set for each product.
Save the changes by clicking OK.
Keywords: Change
Modify
Temperature
Celcius
Centigrade
Fahrenheit
Degrees
References: None |
Problem Statement: How can I tell if service pack 1 has been applied to Advisor 7.0? | Solution: To find out whether or not service pack 1 has been installed on top of Advisor 7.0 do the following:
Navigate to the Advisor root directory. Usually this will be Program Files | AspenTech | Advisor.
Right click on the executable Adv32.exe then select Properties. This is the main Advisor executable.
The version tab should display version 7.0.1.121 if service pack 1 has been applied. If version 7.0.0 is displayed service pack 1 has not been applied.
Keywords: AMS 4.0
SP1
Patch
ER
References: None |
Problem Statement: From version 5.5 onwards, Advisor allows configuration of time frames of less than 24 hours for reconciliation. Most standard yield accounting uses 24-hour periods and this is how Advisor was originally designed to be used. As the usage of Advisor has expanded beyond yield accounting, additional flexibility on reconciliation periods was added, allowing reconciliation on periods of 24, 12, 8, 6, 4, 3, 2 and 1 hours. This functionality allows process engineers to perform 8-hour shift-based reconciliation.
How can Advisor be configured to do shift-based reconciliation? | Solution: The reconciliation period time frame is configured in the details tab of a Reconciliation Base. Go to Configure | Global | Reconciliation Bases and either select an existing reconciliation base or create a new one. In the Details tab, select the desired time frame from the drop-down list box of the Time Frame attribute.
To use the desired reconciliation base, change the time on the calendar control to the beginning of the shift. Note, you must select both the desired starting time of the reconciliation period as well as the date. In Expert | Preferences, the Reconciliation Type should be set to the name of the newly created shift-based reconciliation base. T he Reconciliation Time Frame should now show the start and finish of the desired shift period in Time Frame Begin and Time Frame End.
Note that in order for shift-based reconciliation to be valid, the appropriate reading data must be available such as totalized flows or movement data for the shift, starting and ending tank measurements for the shift, any required lab values, etc.
Keywords: reconciliation period
shift-based reconciliation
Advisor model configuration
References: None |
Problem Statement: This | Solution: outlines the procedure on how to lock and unlock a model in Aspen Advisor.Solution
Locking A Model
Aspen Advisor models can be locked on a specific date and after the model has been locked one can only view the data prior to the lock date and data cannot be changed.
To lock a model:
Note: Any user logged into the Advisor Model should be able to lock the model i.e no specific privileges or permissions are required for a user to lock the model.
1. Click 'File | Lock Model' to open the Lock Model dialog box. If the model is unlocked, 'Locked Date' field displays the message Model is not locked.
2. Click to open the calendar and select the date and time to lock the model.
3. Click OK and the confirmation dialog box appears and upon clicking Yes the model gets locked.
In order to add or delete data in a locked model, change the 'Change to:' field to a date and time prior to the period for which you want to enter data.
Unlock a model:
Note: Users either with superuser or Administrator access rights have the privilege to unlock the model.
1. Click 'File | Lock' Model to open the Lock Model dialog box. Locked Date displays the date and time before which data can be viewed but not changed.
2. In the 'Change to:' box, enter a date and time that is prior to the period for which you want to enter data. Click to open the calendar and select the date and time to lock the model. Click OK
You can enter data for any time after the Locked Date.
Note: Please note that you cannot type in a time in the 'Change to:' field of Lock Model window.
Keywords: Model
Lock
Unlock
Reports
References: None |
Problem Statement: Once a User Table has been created in Aspen Production Execution Manager (APEM), it cannot be edited or changed. Other tables exist in APEM that track the table attributes, and if the table structure is modified directly using DB tools, warnings will be raised. This Read Only status for created tables is a way to help customers rely on the non-changeability of a | Solution: . Code that writes data to a User table can always rely on that table having the structure the original developer created.
But what happens if the data being written to the table changes? For example if a column that holds string data was originally defined with string length of 20 characters, but now longer strings are going to be written, errors like
Error: String or binary data would be truncated
will be displayed when those attempted write operations take place. How can this be resolved, when the end goal is not only changing the structure, but preserving all the data that has accumulated in the table?
Solution
Here is a step-by-step guide on how to re-create the table while not losing all the data in the table. In this example the CONTAINERS table will be recreated, changing the String length for two columns from 20 to 30 characters:
1. Using the Template module, export the User table which needs to be edited. When the table is exported, make sure to NOT select the Struct. Only column -- the key point with this step is to export the data:
2. Open the XML file (contained in the zip file made during export) and make sure the data is present:
3. In the Config module, Delete the Table, using the Delete Table button.
4. Click the Attributes tab and modify the string lengths. In this case the original length for CONTAINER_ID and TYPE have been changed from 20 to 30:
5. Click Create Table. The table once more exists in a state where it can be referenced, but no longer has any data.
6. Open the Template module, and re-import the CONTAINERS template. Because the changes to the structure do not conflict with the contents of the template file the only warning raised is as follows:
7. Checking back in CONFIG, CONTAINERS now has data again:
Keywords: user table, edit user table, create user table, change table, change user table
References: None |
Problem Statement: How do I use the CompileProc? | Solution: The CompileProc command can be used to Compile the Aspen Production Execution Manager Database. This will help with performance and integrity of database.
To run the CompileProc command follow these steps
1. Open a Command Prompt with Administrator privileges.
2. Navigate to the folder c:\Program Files(x86)\AspenTech\AeBRS
3. Run the Command AeBRS CompileProc
This will Compile all orders , BPL, RPL etc and can take several days to run.
In the event you want to run this tool in shorter time periods you will need to add switches to the command.
Syntax of Command is
AeBRS CompileProc SKIP_BPL or if using multiple switches
AeBRS CompileProc SKIP_BPL SKIP_RPL
The switches are as follows
SKIP_BPL
SKIP_SUBDOC
SKIP_RPL
SKIP_DOC
SKIP_ADOC
SKIP_ORDER
SKIP_EDITABLE
SKIP_ARCHIVED
SKIP_ARCHIVED_ORDER
Keywords: AeBRS
CompileProc
MOC
Aspen Production Execution Manager
References: None |
Problem Statement: When user wants to generate a Standard report available from Aspen Reporter using batch script, what are the commands that set the start and end time of the report? | Solution: The beginning date of the report is set using the ChangeTimeBegin command and the command to set the ending date is ChangeTime. The following example of batch script allows the user to generate a Monthly charge and yield report that includes data from March 1st through March 10th
OpenModel modelname, username, password
; Set the report filename to include the Julian date and the Adobe Acrobat .PDF filename extension.
SetExportToFileDateExt .pdf;
;sets the beginning report period/day (first day of MTD report period)
ChangeTimeBegin <modelname>, 2013-03-01 00:00:00
;sets the accounting period/day (last day of MTD report period)
ChangeTime <modelname>, CT, 2013-03-10 00:00:00
; Generate the MTD-Charge and Yield report to PDF and
; write it to the designated location with the designated file name.
ExportToFile MTD-Charge and Yield, PDF, C:\Advisor_Reports;
CloseModel
Exit
Keywords: Change time
Begin
Batch script
Reporter
References: None |
Problem Statement: If the log options are enabled, Monitors will stop working after few days (may be a week or 10 days or 15 days depending upon debug level) even though they are running in the services. | Solution: By enabling the log file option, Aspen AtOMS Monitor continuously writes lot of information in to log files for every 5 minutes. At the end of the day, the size of the log file could become 50 MB or more. When the file is getting bigger, accessing the log file itself takes more time causing the Monitor to hang.
The log file option in monitor should always be disabled and enabled only for troubleshooting purposes. Therefore, to prevent the monitors from hanging disable log options and restart the monitors.
Keywords: Log files
monitors
enable
References: None |
Problem Statement: Does Aspen Operations Reconciliation and Accounting (formerly known as Aspen Advisor) support any standard methods that can be used for Exporting or Printing the Entire GUI Model View to Microsoft Excel or any other Media? | Solution: NO, other than Printing to a selected Printer or Plotter using the Standard File | Print Form available in the Advisor GUI, AspenTech DOES NOT officially support or offer any other standard methods for exporting or printing the Entire GUI Model View to Microsoft Excel or any other Media.
<<See AspenTech KBSolution 122046 for Added
Keywords: Export
Model View
Plot
Print
References: >>
How to send Advisor Model to a Plotter: http://support.aspentech.com/webteamasp/KB.asp?ID=122046
There are no plans on the development road map as of August 2009 to make any future enhancements for adding any extended or revised Model GUI Diagram Printing Capabilities.
Thus, as noted above, currently the only standard supported method available for printing out the Entire Advisor GUI Model Diagram (to show either the Entire Plant View or a User Group View) is to have a Plotter Big Enough to Print it on, and even still you have to get all the Diagram and Text Sizing and Zoom Settings just perfect for it to print out reasonably. AspenTech Support reconfirmed this with two of our NALA Services Team Members here in Houston.
There are no documented procedures for recommended Diagram and Text Sizing and Zoom Settings in regards to being able to make the entire GUI print reasonably on a plotter, and there are no plans to make any printing enhancements for Aspen Advisor right now.
Printing out Individual Units is a much easier task when zoomed in of course, and AspenTech Services engineers often will do just that during model validations with engineering staff. |
Problem Statement: While logging into Aspen Operations Accounting and Reconciliation (AORA, formerly called Aspen Advisor) model, is it possible to use the Windows logon account rather than using a separate account for AORA. This knowledge base article describes how to force AORA to use the Windows logon account. | Solution: By default AORA uses Mixed authentication mode i.e. a user can either use Windows authentication (that forces AORA to use the Windows logon account) or Legacy mode (specifying user name and password in the AORA logon screen).
In order to force AORA to use the Windows logon account, select an AORA model to open leaving the username and password fields blank. This forces AORA to use the Windows logon account to open the model. In order for this windows authentication to work, a user account with the same name as the Windows logon must be added using DBTools. For more information how to add the users to DBTools please refer the DBTools help file.
Keywords: Windows login
Authentication
References: None |
Problem Statement: Errors like this are displayed when running a particular Aspen Production Execution Manager (APEM) Basic Phase after upgrading from a Version 2006.5 or earlier version:
APEM V7.1 (fully patched) introduced a new feature called Structured Variables. Much like Visual Basic exposes properties and methods of objects with the dot separator, like MyObject.property, Structured Variables bring a similar feature to APEM, allowing the programmer to build up data structures with dot separators. However a conflict can arise on a migrated | Solution: where two variables that were unique in the earlier version are now equated as being part of the same structured variable because of the naming convention used, along with the use of the dot separator.
Solution
For example a Basic Phase has three text fields named like:
vE_ABCD_UOM1
vE_ABCD_UOM2
vE_ABCD_UOM3
But those last two are also defined as strings, using the dot separator needed by the structured variables feature:
vE_ABCD_UOM2.exp
vE_ABCD_UOM3.exp
So the result is a naming conflict since from a structured data perspective, the .exp is a subproperty of the top level variable name, not an entirely distinct name, and those top level names conflict with your text field names.
There are two paths to reSolution
1. Edit the BP code, to differentiate the string names, so the root indicator is something different like ve_ABCD_UOM2exp.exp and ve_ABCD_UOM3exp.exp (for example) - the key point is you would then have unique string names that do not conflict with your text field names. This would be considered the bestSolution, since it leaves the structured variable feature enabled, and future application development can take advantage of the new feature.
2. It is possible to disable the structured variable feature, by setting
STRUCT_VAR_ENABLED=0
in a config file (for organizational purposes, the flags.m2r_cfg file is suggested.) This gives an immediateSolution with no code change necessary. In the future, should more application development work be done, any name conflicts would need to be resolved when the structured data feature is re-enabled.
Keywords: 09:06:48: GUI(IQS):Error: VM_ERROR_MESSAGE{VM_ERROR_WITH_INFO{E340,E340,vs_QCen_MatCode->C_QCen_MatCode},VM_ERROR_IN_METHOD{Phase main block IQS_ABCD$QC_CHECK},}
E340
E347
References: None |
Problem Statement: In the Aspen Production Execution Manager scripts are taking several minutes or more to run and need to restart Apache service. | Solution: This problem occurs if the scripts are taking the memory up from the Apache tomcat Java pool.
You may access the Apache Configuration tool by accessing the Icon in the windows toolbar or by navigating to Start | All Programs | Apache Tomcat 5.5 | Configure Tomcat
You can set the Memory Pool to at least 512 MB at a minimum or if you have more memory available on your server you can increase these settings.
Keywords: Aspen Production Execution Manager
MOC
Scripts
References: None |
Problem Statement: When trying to open the MOC thick client, the following error is displayed: | Solution: This error indicates that an incorrect path is in the local.cfg file. This .cfg file should not be edited directly, because it will be overwritten automatically the next time you make a configuration change in the AeBRS\cfg_source directory and run codify_all.cmd
Looking in codify_all.cmd (located in cfg_source) we find the line:
call C:\Program Files\AspenTech\AeBRS\cfg_source\codify C:\Program Files\AspenTech\AeBRS\cfg_source\local.m2r_cfg C:\Program Files\AspenTech\AeBRS\local.cfg
So the wrong path is contained in the user-editable local.m2r_cfg file. Open this file and look for and correct any invalid paths. Once you close this file, saving changes, run codify_all.cmd and try opening MOC again.
Keywords: C:\Program Files\AspenTech\AeBRS\local.cfg
Error: The system cannot find the path specified
References: None |
Problem Statement: When the user updates strapping tables in Advisor with new calibrations, older data is being overwritten by the new data in the strapping tables, and calculations based on the old strapping tables can no longer be repeated. | Solution: Users should not delete old strapping tables or overwrite them with newer data, as calculations using the older data and tables may need to be re-run.
Instead of overwriting the existing strapping tables with new calibrations, the user should simply add the new strapping tables into Advisor (with different names), leaving the older ones intact. Then, in the detail page of the tank gauge instrument, simply point to the new strapping tables on the date they are to be used. With Advisor''s date management of model changes, the tank gauge instrument will know to use the old strapping table prior to the change date and the new strapping table from then onwards.
Keywords: strapping tables
strapping table recalibration
References: None |
Problem Statement: This | Solution: illustrates which database table in the Aspen Operations Reconciliation and Accounting database contains the product states, types and classes.Solution
GCOFEDST is the table in Aspen Operations Reconciliation and Accounting database that contains the configuration information for all products (feedstock) in the Aspen Operations Reconciliation and Accounting model. Among the information are the STATE, TYPE and CLASS of the product and the database fields for this information in the GCOFEDST table are FLAG_STATE, FLAG_TYPE and FLAG_CLASS respectively. The data type of these three fields is IIFLAG, which is an integer value. The translation of the picklist items to the integer equivalents is in the program code but not available in a database table.
Below is the translation of each integer value to the equivalent item in the drop-down selection lists on the Details tab of the Product Configuration dialog box in Aspen Operations Reconciliation and Accounting GUI.
FLAG_STATE
0 = Liquid
1 = Gas
2 = Solid
FLAG_TYPE
0 = Crude
1 = Refined
2 = Chemical
3 = Other
4 = Lube
5 = Chemical II
6 = ELV
7 = Table 6C
FLAG_CLASS
0 = Charge
1 = Finished
2 = Intermediate
3 = Other
1000 = Comp Charge
1001 = Comp Finished
1002 = Comp Intermediate
1003 = Comp Other
Keywords: GCOFEDST
Product States
References: None |
Problem Statement: What relational databases does V7.2 of Aspen Operations Reconciliation and Accounting (AORA, formerly called Aspen Advisor) support? | Solution: AORA is an ODBC-compliant database application, which means it will support any relational database that is compliant to the Open Database Connectivity (ODBC) standard.
The newest release which is V7.2 has been specifically tested and supported when using any of the following database versions with the appropriate ODBC drivers installed:
Microsoft Access: 2007 SP2 and 2003 SP3
Note: Due to limitations in Microsoft Access itself, this database is of limited use with AORA. It is mainly used in initial prototyping of AORA models and exporting of models for support purposes. Microsoft Access does not support the structured query language (SQL) outer join function, so most standard AORA reports will not run properly when running from Aspen Reporter (seeSolution 102714).
Microsoft SQL Server: 2005 SP3 ( Both standard and Enterprise Edition), 2008 SP1 (only Enterprise Edition)
Microsoft SQL Express: 2005 SP3 and 2008 SP1
Oracle: 9i database and 10 g database (both release 2)
For more information on the Supported platforms and the Operating Systems for V7.2 please refer the
V7.2 Installation guide
Note: ThisSolution is only applicable to the our latest release V7.2. Usually the Relational Database support varies a little for every version. To get validated information regarding the databases supported for AORA either for versions prior to V7.2 or future releases please refer the System requirements section under the Overview chap in AORA installation Guide.
AORA Installation Guide for V7.1
AORA Installation Guide for 2006.5
Keywords: Advisor database
relational database
ODBC
database versions
References: None |
Problem Statement: Can Advisor perform flow compensation on raw flowmeter readings? Where is the best place to perform flowmeter compensation? | Solution: Flow compensation usually can be performed at many levels in the plant information system. Compensation for actual flowing conditions (temperature, pressure, density) can be done at the meter level, in the distributed control system (DCS), in the plant historian, and in Advisor itself. Flow compensation must be performed in order to be able to accurately reconcile the plant balances.
Advisor model developers should have the flow compensation performed at the lowest level possible, as data accuracy and granularity decrease as the levels increase, with the lowest levels being at the meter and DCS.
At low levels (meter/DCS), compensation can be done instantaneously if the actual flowing conditions of temperature, pressure and density are available along with the raw flow reading. The compensated flow calculated from instantaneous values should be quite accurate.
At higher levels, such as in Advisor itself, only the daily or hourly averages of temperature, pressure, density and flowrate are usually available. Thus, calculations based on these average values will be inherently less accurate.
Keywords: Advisor model
flowmeters
flow compensation
References: None |
Problem Statement: Is there a batch command that selects a particular zone for processing? | Solution: The SETMODELZONE command will select a previously defined Group Zone within Advisor. The selected zone will then be used for any successive batch commands.
Syntax: SETMODELZONE zonename;
where zonename is the name (tag) of the zone to be used in processing.
NOTES: The SETMODELZONE command must precede the OPENMODEL command.
The zonename must exactly match the zone name (tag) defined in Advisor.
This parameter is case-sensitive.
Keywords: zone
batch command
References: None |
Problem Statement: Following are the Reconciliations statuses that are available under Expert System Preferences
'Not Saved', 'Preliminary', 'Intermediate', 'Complete', 'Finalized' and 'Locked'
This | Solution: explains the purpose of above mentioned Reconciliation status.Solution
'Not Saved' appears by default before the save command is run during the process of Initialize, Reconcile, and Save (IRS) sequence.
'Preliminary' status is shown after expert results are saved.
'Intermediate', 'Complete' and 'Finalized' are not set by the system but can be set by a custom program for user-specific purposes.
'Locked' can be set to prevent other users from modifying data in the Aspen Advisor model. Please note that only users with either Superuser or Administrator access rights have the privilege to unlock the model
Keywords: Advisor
Reconciliation
Status
References: None |
Problem Statement: When should a default product be assigned to a configured pipe in an Advisor model and when is it used? | Solution: The default product for a pipe should be assigned in the Details tab of the pipe object. The default pipe product is used when creating new readings for the pipe. This is the default for that reading when it is created. It is also used to determine the product default properties of a pipe, if it gets to that level. Once the reading is created there is no link back to the pipe product. If you change the pipe product the reading product does not change. If you change the reading product the pipe product does not change.
Keywords: Advisor model configuration
pipe object
default product
References: None |
Problem Statement: An installation of Aspen Operations Reconciliation and Accounting results in a file called IIEQUA32.dll being placed in
A A C:\ProgramFiles\CommonFiles\AspenTechShared
Another three files called IIEQUA32_US,A A IIEQUA32_M15A andA IIEQUA32_M20A are also installed in
A A A A A A ...\AspenTech\Advisor\Measurements
The three dlls in the Measurements directory are for different measurement systems.
iiequa32_us
This is for the US measurement system and 60F is the base temp.
iiequa32_m15
This is for the metric measurement system and 15C is the base temp.
iiequa32_m20
This is for the metric measurement system and 20C is the base temp.
By default, the IIEQUA32.dll in the AspenTechShared directory is identical to the US dll ( IIEQUA32_US.dll ) in the Measurements directory.
What does a user need to do if they want to use one of the other measurements dlls mentioned above? | Solution: Via Windows Explorer rename the file IIEQUA32.dll in the C:\ProgramFiles\CommonFiles\AspenTechShared to such as iiequa32_orig.dll
Copy the required 'measurements' dll from
A ...\AspenTech\Advisor\MeasurementsA A A A toA A A C:\ProgramFiles\CommonFiles\AspenTechShared
Rename the copied file to IIEQUA32.dll
Keywords:
References: None |
Problem Statement: How to set up an ODBC connection to the Aspen Operations Reconciliation and Accounting Model (AORA)? | Solution: Following are the Steps on how to set up an ODBC connection
1. Download the models to your Local Computer. Go to Data Sources ( ODBC) through Start -->Programs -->Control Panel --> Administration Tools. Using the ODBC data source create a new DSN ( System DSN or User DSN based on your profile in the Computer.
Note: When using a machine that has 64 bit OS Computers, use 32 bit ODBC driver executable 'odbcad32.exe' located in the folder C:\Windows\SysWOW64 to create the ODBC data source.
2. You can also choose Microsoft SQL or Oracle Drivers based on the type of Relational Database being used at your site. Screen shot below shows example of creating ODBC data source for Microsoft Access Database.
3. Configure the DSN pointing to the MS Access Database, copied on to the computer and complete the configuration.
4. Next, Launch AORA and go to File and Click on Open Model
5. Open the Model by Selecting the name of the DSN defined in step 2. The default username is 'superuser' with a corresponding password of 'superuser' for the demo model created using the method described in theSolution 136637. When using a different model login with the correct username and password.
Now you can see the Demo model in AORA.
Keywords: Data Source
ODBC
Demo Model
odbcad32.exe
References: None |
Problem Statement: How to determine which Temporary Tables are generated and used when executing selected Aspen Operation Reconciliation and Accounting (AORA) Reports, or when creating Custom Reports from the Standard Crystal Reports?
REASONS FOR ASKING:
We are modifying some of AORA's Standard Report Files to build our own Custom Reports but are having some problems trying to verify some of the report field and value linkages between the final report data that is generated into the Temporary Tables vs the corresponding source data that resides in the Actual Database Tables.
We have also noticed on occasion that some of the Temporary Tables remain behind in the AORA database after running Reports in the Reporter instead of being automatically deleted upon closing the reports and exiting Reporter. This we have noticed leads to report execution errors during subsequent report runs if the Temporary Tables left behind from the previous runs are not first deleted. As such we would like to know which Temporary Tables are generated for each Standard or Custom Report so that we can better troubleshoot which reports are resulting in the Temporary Tables remaining in the database. | Solution: IMPORTANT:
Please read entirely all instructions and notes provided below before proceeding with the documented Temporary Table determinationSolution procedures.
The procedure required to View and/or See and Test specifically which Temporary Table or Tables get created for each Standard Report or Custom Report is to proceed as follows:
1. First DELETE all remaining Temporary Tables from the AORA database if any still exist.Solution ID 125252: How do I delete the Aspen Advisor Database
Temporary Tables left behind after running Advisor Reports?
http://support.aspentech.com/webteamasp/KB.asp?ID=125252
2. Next put the Reporter in Design Mode. This will result in the Temporary Tables remaining in the database after successfully running and closing out a report.
With the model open in Reporter Click File | Preference... from the File Menu.
Select / Click the Advanced Tab located at the top of the Preferences dialog form.
Check the Set the reporter into design mode check box.
IMPORTANT: Remember to take the Reporter OUT of Design Mode when you have completed testing.
3. Then run each of the selected Standard or Custom Reports (RPT Files) one at a time and use either your RDB (SQL Server or Oracle) Management Tools or the Aspen DBTools to review which Temporary Tables are created in the AORA database when each selected report is executed.
Example:
Open the Advisor Model (Database) in the Aspen Advisor DBTools Application.
Run the following SELECT Query using the Aspen Advisor DBTools Application, or by using the query tools available per SQL Server or Oracle corresponding to the installed relational database type you are using.
SELECT * FROM sysobjects WHERE NAME LIKE 'R%';
Executing the above Query will provide you with a List of all the Temporary Tables (R Tables) that exist in the database after executing a selected Standard or Custom Report (RPT File).
OTHER IMPORTANT NOTES:
You will need to make sure that in between each report run you are deleting the Temporary Tables generated by the previous report execution, so that there is absolutely no confusion about the associated tables created for and used by each report just in case there are reports that utilize the same Temporary Tables.
Now assuming you already have a good understanding of the AORA Database Tables (purpose of each table and type of data stored in each table) then the Linkages between the generated Temporary Table data used in the Reports and the corresponding Source data that exists in the AORA Database Global, Physical, Configuration, Reconciliation, Simulation, and other Data Tables can then be determined as follows:
1. By first noting the field names used in the Temp Tables.
2. And then using the AORA Database Help File (aspeniidb.chm) and verification queries as needed to then determine for the report data in the Temp Table the corresponding link back Source tables and data based on the match up of the noted Temp Table field names and values with the respective database table field names and values (for pipes, vessels, instruments, etc.).
For an Example of resolving the actual data source linkages as per the last two steps noted above based of testing applied to the DSRPD.RPT (Standard Daily Sales and Receipts) report execution, then please review the following supporting knowledge baseSolution http://support.aspentech.com/webteamasp/KB.asp?ID=131488
Keywords: Custom Reports
Database Help
Design Mode
Reporter
Temporary Tables
References: None |
Problem Statement: What can one adjust if the Reporter shows other components but not the parent component? | Solution: ThisSolution is quite simple. Go to File | Preferences | Display and set the ''Number of Parent Levels'' field to zero. This tells the reporter to report ALL components (the parent level is the lowest level). A common mistake is to set this field to 1 which shows all levels EXCEPT the parent level.
Keywords: Component
Missing
Parent
Child
References: None |
Problem Statement: When a new Aspen Advisor model is created, what is the default username and password? | Solution: When a new Aspen Advisor model is created, the default username is 'superuser' and the password is 'superuser'. This default password should be changed after the first time the model is opened.
Aspen DBTools can be used to modify the password by opening up Aspen DBTools => File => Change password. You can also use Aspen DBTools to add additional users and grant the desired permission for the new user.
Keywords: None
References: None |
Problem Statement: After installation of Aspen Advisor, the following errors are noticed when one attempts to run the expert system.
AionDS/PC: Setup table not found - NLS.AES
Error Starting the expert system - Error #19217
Error starting session for document | Solution: These errors indicate that the path to the expert system has not been defined correctly. Make sure that one has the correct path to the expert system. Do this as follows:
Log in to Advisor as superuser or an equivalent.
Go to File | Preferences and select the Expert tab.
The Expert Path should point to the Expert directory in the Advisor directory structure. The installation default is:
C:\Program Files\AspenTech\Advisor\Expert
NOTE: If the Advisor software is installed on another computer such as an application server, the Expert directory should reside on the local workstation. This is because the Expert directory is the holding directory for files created and used in the expert system reconciliation process. If the Expert directory is a shared directory, there could be file conflicts if more than one user runs the expert system at the same time.
Select OK, close the model and log back in as a different user that does not have superuser privileges.
Once this is accomplished try reloading the expert system.
If the above does not work, try the following:
Make sure the Expert directory also contains a file called OPTIONS.REC.
Make sure that the AION variable in the AION.INI file in the Windows directory points to the INIT directory under the ADVISOR base directory. See below for an example:
AION=C:\Program Files\AspenTech\Advisor\Init
FOR ADVISOR V7.0.0:
NOTE: If you are running Advisor v7.0.0 and having problem starting the Expert System even after you have applied thisSolution, then you need to download and apply Service Pack 1 for AMS v4.0 in order for the expert system to work. Due to a defect in Advisor 7.0.0, the expert system will not work unless either SP1 is applied or the least squares mathematical reconciliation engine is licensed and installed. SP1 for Advisor 7.0 can be downloaded from knowledge base article 106046.
FOR ADVISOR V7.1.0:
NOTE: If you are running Advisor v7.1.0 and having problem starting the Expert System even after you have applied thisSolution, then you need to download and apply Service Pack 2 for AMS v4.1 in order for the expert system to work. Due to a defect in Advisor 7.1.0, the expert system will not work unless either SP2 is applied or the least squares mathematical reconciliation engine is licensed and installed. SP2 for Advisor 7.1 can be downloaded from knowledge base article 108238.
FOR ADVISOR V8.0 & LATER:
Starting with Advisor v.8.0, the Advisor model configuration tool is licensed separately from the expert system. If one installs the model configuration tool without installing the expert system -- yet attempts to start the expert system, the message Error starting expert system will be returned. The most obvious clue to a non-installed expert system is the absence of the expert subfolder under the Advisor folder.
Keywords: Expert
AION.INI
References: None |
Problem Statement: Aspen Advisor can be used to track product composition in tanks. If product tracking was not initially set up when the model was created, it can be added to the model later. A start date must be select to begin track the products in the tank, it is best to select the start of a month to do this. | Solution: As an example, tracking is going to begin April 1st and the model is using Fractional Gauges for the tanks.
The first step is to manually initialize the product compositions in the tanks on March 31st. Open the model in the Advisor GUI and change the time to March 31. Initialize the composition readings in the fractional gauges. This can be done by the following steps:
From the Advisor menu go Data | Instrument Readings | Inventories | Fraction Gauges... and the Instrument Reading Gauge Fraction dialog window pops up.
In the Instrument Reading Gauge Fraction dialog box, select the Product Comps view.
Select the instrument gauge to be initialize with the product compostions. Double click on the instrument or select the instrument and click the OPEN button to bring up the Product Composition Listing dialog window.
Click on the =0 icon button on the Product Composition Listing dialog and this will enable you to manually enter the compostion values.
To enter the composition value for the Product just double click on the product or select the product and click the OPEN button to bring up the dialog box to modify the composition.
Once the product compositions have been initialized for the tank gauges, the Simulator can now be run to foward the Product Compostions to the next day. The first time you run the Simulator, use the following options: For Simulate Values, select Product Comps
For Simulate Equipment, select Vessels and Pipes
For Simulation Strategies, select Update from reading and the rest can be left as default.
On April 1st and every day thereafter, run the Simulator with the following options: For Simulate Values, select Properties, Components, and Product Comps For Simulate Equipment, select Vessels and Pipes
For Simulation Strategies, select Linear blend and the rest can be left as default.
After the model has been closed you can run the appropriate reports in the Advisor Reporter such as the Daily Tank Prod Comp report by volume and Daily Tank Prod Comp report by mass.
Keywords: None
References: None |
Problem Statement: Where is the density of air stored in Advisor? Can the default value for the density of air be modified? | Solution: The air density is stored in the OLOCONFG table. There is no way to modify the air density through the Advisor GUI, however, the air density value in OLOCONFG can be modified through a SQL script or by manually changing the value in the OLOCONFG table.
Keywords:
References: None |
Problem Statement: The Advisor simulator has two strategies for simulating properties to the next accounting day. This article describes how to configure individual properties to be simulated by the linear blend algorithm or be updated from readings. | Solution: You can simulate physical properties, components, and product components for all tanks and streams defined in an Advisor database model by using the Simulator tool.
The Update from readings strategy simply propagates today's physical property, components, and/or product component values forward to the next accounting time interval. Today?s property, component, and/or product component values may represent actual readings entered by the user for the current accounting interval or values which were previously simulated during the previous accounting time period. The system will take the simulated values for yesterday and then update them with the latest readings on the tanks and pipes for today. Only values that are entered as readings for today are used. No GC calculated, product default, or global default values are used in the determination of the simulated results.
The Linear blend strategy calculates physical property, component, and product component values by linearly blending the values through tanks, blend headers and manifolds. No blending will occur through process units (columns & reactors) since compositional and property data across columns and reactors changes significantly (the linear blending algorithm doesn't apply for this case.) The linear blended values on the pipes exiting the process units (yields) are not calculated and will be updated from the current readings that have been entered for them.
It is possible to apply the linear blend strategy selectively, based on an individual property. This is useful for cases in which a linear average of the property values doesn't make physical sense. For example, it isn't accurate to linear blend temperatures and pressures. More realistic temperature and pressure values will be generated by updating these properties from the previous day's readings. Here is how to specify that a particular property not be linear blended.
1. In Configure | Global | Properties select the property then double click on it. Click on the Details tab.
2. Change the Linearity attribute to 'Non-Linear'.
When the Linearity is set to non-linear, the linear blending algorithm will not be applied to this property. Instead, the properties which are set to be non-linear will automatically be updated from the previous day's readings when the simulator is run with the linear blend strategy.
Note: If there are many user-defined properties defined in the model, setting the properties which should not be linear blended to Non-Linear will significantly reduce the amount of processing time required for the daily simulation process to complete.
Keywords:
References: None |
Problem Statement: When upgrading an Advisor database from earlier versions (5.0 and earlier) to more current versions (7.0 and later), the automated database upgrade scripts will fail. An ODBC error message will appear when the scripts attempt to upgrade the database from version 5.5 to 7.0. Following this error, the OLOCONFG table of Advisor will incorrectly indicate that the database has been properly converted to 7.0. | Solution: When upgrading from pre-5.0 Advisor databases, an error occurs in the 5.0 to 5.5 step because the upgrade script does not correctly drop the TEMP_TBL temporary table. This table is created during the 5.0 to 5.5 step, and the problem occurs when the 5.5 to 7.0 step tries to create this table and generates errors because the table already exists. This causes the upgrade to fail, leaving the tables in the 5.5 state but labeled as 7.0 in the OLOCONFG table.
The workaround is to perform the upgrade until the error occurs, manually drop the TEMP_TBL table, update the LDESC data for the TABLE VERSION key value in the OLOCONFG table to read 5.5000, and then run the upgrade again.
Keywords: Advisor database
upgrade scripts
ODBC error
References: None |
Problem Statement: This | Solution: will document the cause of the error message
Invalid UOM Type for reading
Solution
The message Invalid UOM Type for reading indicates that an instrument has a UOM defined for it which is not compatible with the product associated with the vessel or pipe.
For example, this error message will occur if one attempts to import flow volume data with a gas UOM (such as MSCFD) while the default product is defined to be a liquid for the pipe associated with this instrument.
Keywords: None
References: None |
Problem Statement: What heirarchal logic does Advisor use to obtain property values? | Solution: Actual readings are taken to be the most accurate information and are, therefore, given the highest precedence by Advisor.
Simulated values are used with second highest priority. Simulated properties are propagated to pipes and/or vessels with the understanding that most of the simulated values will be overwritten by actual readings.
Finally, if neither a reading or a simulated value is available, Advisor will use the properties defined for the default product associated with the pipe or vessel.
Keywords: None
References: None |
Problem Statement: How are liquid meter readings calculated in Advisor? | Solution: Advisor calculates a compensated flow value as follows:
Compensated Flow = Meter Reading Meter Factor Correction Factor
The correction factor that Advisor uses for Liquid Meters is as follows:
Correction Factor = SQRT ((New SGflowing/Old SGflowing)*(Old SGbase/New SGbase))
where
New SGflowing = Actual specific gravity at actual temperature
Old SGflowing = Design specific gravity at design temperature
Old SGbase = Design specific gravity adjusted to standard temperature (base conditions)
New SGbase = Actual specific gravity adjusted to standard temperature (base conditions)
SG = Specific gravity of the liquid
There are several things which need to be known before a user can actually do the comparative calculation for themselves. First of all, the user needs to know the base system of measure being used in Advisor, as this defines the standard conditions used in the calculations. Advisor has three choices for base Units of Measure (UOM):
US system with base temperature of 60deg F (which uses iiequa32_us.dll for iiequa32.dll)
Metric system with base temperature of 15deg C (which uses iiequa32_m15.dll for iiequa32.dll)
Metric system with base temperature of 20deg C (which uses iiequa32_m20.dll for iiequa32.dll)
(US, 60deg F) is the default base UOM when Advisor is installed. To change base UOM''s, the user has to copy the desired dll from the \Advisor\Documents directory into the main \Advisor directory and rename it as iiequa32.dll.
Secondly, the user needs to know how the product (and the product''s default gravity), actual temperature, actual pressure and actual gravity are assigned to the meter in the system. This is needed to determine if Advisor is using the expected property values in the calculation.
Is the actual product being assigned with the meter reading, or is the meter using a default product?
Is the actual density (gravity) being assigned by a lab pipe reading, or is it using the default density (gravity) of the product?
Same questions with temperature and pressure.
Assuming the product and the actual readings for temperature, pressure and gravity are assigned properly, and the values are as expected, then the corrected flow would be attributed to the correction factor defined above.
As seen above, the meter correction factor depends on the following gravities/densities:
Actual density at standard temperature (e.g., 60 degrees F in the U.S.) - this is assumed to be given/known from the lab analysis
Actual density at actual/flowing temperature - this is not known but can be calculated from a) above and a Volume Correction Factor (VCF); the VCF calculation assumes that the density squared term in the denominator of the VCF equation is at standard temperature. Since this is the a) value above, no iterative/recursive calculation is required.
The meter design density at design flowing temperature - this is assumed to be given/known from the meter design parameters
The meter design density at standard temperature - this is not known and has to be calculated from c) above and a Volume Correction Factor (VCF); Since the VCF calculation assumes that the density squared term in the denominator of the VCF equation is at standard temperature, the value of d) is a function of itself. Hence, a recursive calculation is required to solve for the value of d).
Keywords: liquid flow compensation
volume correction factor
liquid meter
References: None |
Problem Statement: How upgrading from an older version (i.e. v4.2) to the latest version (i.e. v7.1) works in the background. | Solution: Suppose you want to upgrade from a v.4.2 model to v.7.1. When you attempt to open your 4.2 model with 7.1, a call is made to the Advisor database dll for a table version check. The Advisor database dll will notice that we are asking it to open an older model so it will ask us if we want to upgrade. Once we select to upgrade, a series of ''functions'' will be called from this database dll for the upgrade process. Each function will only do a single version upgrade. For example, the first function will upgrade from 4.2 to 4.9. The second function will then take over and upgrade from 4.9 to 5.0. This process occurs until the database version is up to, in this example, 7.1.
The point here is that the upgrade process is sequential in nature.... so, if you test the upgrade process from 6.0 to 7.1, then the upgrade should also work from 4.2 to 7.1 because they''re reusing the old upgrade code to get from an earlier version to 6.0.
Keywords:
References: None |
Problem Statement: As Aspen Operations Reconciliation and Accounting (AORA, formerly called Aspen Advisor) is enhanced from version to version, it is usually necessary to modify the database to accommodate these enhancements. This | Solution: discusses how to upgrade an existing AORA (database) to a new version of the software.Solution
Nothing special has to be done by the user or the database administrator to upgrade the AORA model/database to the newer version. The upgrade will be done automatically by AORA for the first time the model is opened in AORA GUI with a new version of the software that requires a new database structure.
NOTE: It is recommended to backup your old database before allowing AORA to upgrade the database to newer version. This should be done using your standard method of data backup.
Keywords: upgrade
convert
database
version
References: None |
Problem Statement: It is the policy of many IT departments to periodically require a user to change their network login password for security reasons. If the login account is used for a machine running Microsoft SQL Server which contains an Advisor model, SQL Server may not start up properly and the user will not be able to access the model. | Solution: One of the reasons Microsoft SQL Server may fail to start could be the way the services are configured in Windows NT.
In Control Panel | Services, the following services should be checked:
MSSQLServer
MSSQLServerOLAPService
SQLServerAgent
If Log On As: is This Account: Domain\Username, then you may have to change the password to the new password and manually start the service.
If Log On As: is System Account, then you will not need to change the password of the service.
Changing the login account-based services to use the new password on start-up will ensure that SQL Server starts-up properly and access to the Advisor model is enabled.
Keywords: Microsoft SQL Server
Windows NT services
Advisor models
passwords
References: None |
Problem Statement: Aspen Technology is pleased to announce the availability of the Aspen Manufacturing Suite - Production Management family of products version 2.0 | Solution: Aspen Technology is pleased to announce the availability of the Aspen Manufacturing Suite - Production Management family of products version 2.0. This suite of products is currently distributed with the Information Management System release 3.0.
This release, in particular, focuses on integration with Aspen Framework to demonstrate that AspenTech is indeed the one company that can provide integrated enterprise wideSolutions. In addition, there are significant enhancements to the products themselves including ease of use and additional configuration flexibility. You can expect to see further integration in future releases that will bring more a consistent look and feel to all the AspenTech products you use.
The first shipments of this release were mailed on June 26th, 2000.
The key products released in this suite are:
*Aspen Process Recipe 3.0
*Aspen Process Order 2.0 (Refining version)
*Aspen Advisor 5.5
*ERP Connect 3.0
The Production Management release 2.0 will be quickly followed by a 2.1 release in September as part of the IMS release 3.1. The 2.1 Production Management release will include:
*The first release of Aspen Transition Manager. This product in combination with Aspen Process Recipe allows support, design and execution of product transitions. *Aspen Process Recipe 3.1. This version will provide the data structures and definitions required to support the Aspen Transition Manager release.
Please refer to the product release notes for more details about the new features. The Installation guides describe the upgrade procedure for existing customers. You can access the release notes and installation manuals from the Documentation area of the online Technical Support Center, http://support.aspentech.com/webteam/DocsProdMgmt/DocsProdMgmt.htm .
Keywords:
References: None |
Problem Statement: When the Table adjusted for roof displacement option is checked in the straptable Details tab, the Roof displacement attributes become available. This knowledge base article describes how the roof displacement attributes are used when calculating the volume of material in a tank from a straptable. | Solution: If the straptable has been created with the floating roof correction already built-in, a second calculation must be done to account for the difference between the reference density (used when the straptable was built) and the observed density of the measured temperature of the material in the tank. This calculation is carried out using the roof displacement attribute data.
Design Gravity - The design gravity is the reference density that was used in the height to volume pairs when the straptable was built.
Volume - This is the volume which will be added or subtracted from the uncorrected volume (Gross Observed Volume) of the tank to account for the difference between the reference density and the observed density.
Gravity - For each unit entered in the Gravity field, the amount entered into the Volume field will be added or subtracted to/from the uncorrected volume calculated from the straptable.
For example, if The Design Gravity is 35, the Observed Gravity (the gravity that is measured in the tank for a given day) is 42, the Volume field is 24.59 bbls and the Gravity field is 1 then:
The difference between observed gravity and design gravity is
42 - 35 = 7
For each 1 Gravity unit above 35 API, 24.59 bbls will be subtracted from the volume calculated directly from the straptable. Therefore, a total of
7 * 24.59 bbls = 172 bbls
Will be subtracted from the volume calculated from the straptable.
Note: The reason that the volume of 24.59 bbls will be subtracted for each gravity unit is because the design gravity is less than the observed gravity. If the design gravity is greater than the observed gravity the calculated volume will be added to the volume obtained from the straptable.
The uncorrected volume displayed in Aspen Advisor's instrument reading (highlighted in red) will include the volume calculated from the straptable with the 172 bbls correction shown above already factored in.
This calculation is outlined in the American Petroleum Institute's Manual of Petroleum Measurement Standards, Chapter 12 section 9.1.4a.
Keywords: Strap
Strapping
Correction
Deviation
American
Petroleum
Institute
ASTM
References: None |
Problem Statement: Aspen Advisor may crash with the error:
Abnormal Termination: Unknown Exception Critical failure! System shutting down
when running the Expert system. | Solution: 1.) First, check that the PC where Aspen Advisor is installed has enough RAM. This problem can sometimes be caused by an insufficient amount of Random Access Memory (RAM) on the PC running Aspen Advisor. TheSolution is to add more RAM on the PC (http://support.aspentech.com/webteamasp/KB.asp?ID=116532). If the PC does have plenty of RAM, then move on to the other procedures provided below.
2.) Check for and delete if necessary the old copy of the iiequa32.dll file from the Aspen Advisor Folder location (<drive>:\Program Files\AspenTech\Advisor), which is used to store this file for previous Aspen Advisor versions. For Advisor versions 2004.2.1 and above this file should be located in the <drive>:\Program Files\Common Files\AspenTech Shared folder exclusively, where <drive> is the root drive (C:, D:, etc.) where the Aspen Advisor Application is installed.
3.) Incidents have also been reported where the client was using a Custom Install Script that did not completely uninstall the old version of Aspen Advisor. In such cases like this you will need to reinstall and make sure that all the latest patches have been applied.
Note: If you must reinstall, then it is recommended that you perform a ?Clean Uninstall? of all Aspen Products by following steps similar to or as mentioned in KBSolution 111129.
How to do a clean uninstall of Aspen InfoPlus.21 products:
http://support.aspentech.com/webteamasp/KB.asp?ID=111129
(Same basic procedures apply to other Aspen Apps as well).
Keywords: iiequa32.dll
expert system
References: None |
Problem Statement: This knowledge base article addresses the issue of how to send an Aspen Operations Reconciliation and Accounting Model (AORA, formerly called Aspen Advisor) to a Print Plotter. | Solution: One can use the Print button from the AORA Graphical User Interface (GUI) directly with a plotter. The model needs to be defined somehow to see the pipes, instruments and other objects on the appropriate scale. When using a plotter you may need to make some changes under the Diagram | Preferences menu to make the objects on the printout more visible. Select the plotter from the drop down list and the desired paper size so as to get the model to print legibly.
We can also use Microsoft Visio (10.0) to reverse engineer portions of a model.
Keywords: Print Plotter
GUI
Advisor
References: None |
Problem Statement: How to build a batch file to reconcile and save over more that one day? | Solution: Please see attached example to loop through several days.
Keywords:
References: None |
Problem Statement: This knowledge base article provides an Excel spreadsheet which calculates volume correction factors (VCFs) using the American Petroleum Institute (API) standard 2540. API standard 2540 is the standard by which Aspen Advisor calculates VCFs. | Solution: The calculations in this spreadsheet can be used to determine the VCF for the Metric or English unit systems. However, the temperature and density data needs to be entered in units of degrees C and Kg/m3 regardless of which units are used in your Aspen Advisor model.
This spreadsheet calculates VCFs for each product type which is specified by the API 2540 standard. The actual VCF which is used in Aspen Advisor's calculations is determined by the density of the product. A description of the logic Aspen Advisor uses to determine which VCF is used can be found in KB article 116772.
Note that the VCF for gasolines will be used in this example since:
1. The product Type is defined as Refined
2. The density of the material specified in the example above (724.89754 kg/m3) is less than 770.0 kg/m3.
The screen capture below shows the VCF calculated by Aspen Advisor using the example data above. The VCF calculated by Aspen Advisor agrees with the VCF calculated by the API standard 2540 for gasolines.
Keywords: ASTM
corrected
standardized
References: None |
Problem Statement: If a MOC client or Web Client is left open, but with no activity for a long period of time (This can be few minutes to hours depending on machine performance, and network) it may hang and be unresponsive. Examining the debug output, messages like Database error and The connection is closed are found (see | Solution: MOC requires a constantly open port to the relational database (by default, port 1433 in SQL Server.) However network/firewall configurations in some environments monitor open ports and, if no activity is detected for a set period of time, then the ports are closed. This can also occur if the Client is Minimized in Windows which can means that windows may close the ports. This hangs MOC, and it must be restarted (by going to Task Manager and killing the javaw.exe process first.)
V7.2 adds a new Keep Alive feature that automatically creates activity on the DB port at a default interval of 10 minutes (CQ00386053, listed in the Release Notes.) The flag is found in flags.m2r_cfg, in units of minutes:
NOTE: Before this feature can be used in V7.2 or V7.3 please update to latest Patch for Aspen Production Execution Manager. If you do not have the latest patches you may receive unwanted error messages in the MOC Debug
# Database connection keep alive thread period (in minutes - default=10min) - <=0 means keep alive disabled
# KEEP_DB_ALIVE_PERIOD = 10
Keep in mind that even though this flag is commented out, it is in fact active by default at the 10 minute interval. The purpose of uncommenting it would be to either (1) disable it by setting it to 0 or a negative number (not recommended), or (2) changing the frequency.
Another key point of this new feature is that if a disconnect happens -- for example the system administrator may stop the Relational Database to take a backup -- MOC will attempt to reconnect at the defined frequency. The disconnect/reconnect happens in the background and when the user comes back to their workstation they would not be aware anything has happened unless they examine the MOC debug file. If a Basic Phase is open on the screen the system will still attempt to reconnect, however there may be errors displayed and, depending on the Basic Phase, a reconnect may not be successful, and a MOC restart may be required.
Keywords: for more debut entries.)
What can be done to avoid this hang?
References: None |
Problem Statement: Customers have occasionally reported that when checking the Aspen Production Execution Manager (APEM) screenshot report for a Basic Phase, some of the screens are missing. What can cause this problem? | Solution: This problem has been reported on V7.1, but because the underlying issue is a Java error, it could happen on any version which is supported on a JDK 6 1.6 variant:
APEM Version
Officially Supported Java JDK Version
V7.1
Sun J2SE 1.4.8, 1.5.12 (JDK 5), 1.6.2 (JDK 6)
V7.2
Sun J2SE 1.4.8, 1.5.12 (JDK 5), 1.6.2 (JDK 6)
V7.3
Sun J2SE 1.6.18 (JDK 6)
To resolve the blank screenshot problem, it has been reported to Aspentech that variant JDK 1.6 Update 26 runs APEM correctly, and also correctly adds screenshots to the batch record.
Keep in mind that the versions documented above are the officially supported JDK versions, meaning the JDK variants that were used for official testing at the time of the release. When installing any later version, it is the customer responsibility to verify that in their particular environment that later patch works correctly. In the case of Java patches, what we have seen is that updates to a specific major Java release (meaning 1.4.x, 1.5.x, 1.6.x) tend to work without issue. But for example running a supported APEM version from the table above on JDK 1.7 would only partially work, and may introduce other problems or issues.
Keywords: empty
missing
References: None |
Problem Statement: When trying to open MOC Thick Client, the message Error loading workstation is displayed | Solution: Every node (workstation) that is part of an AeBRS system must be defined in the Workstation table. Typically this is either the short or long-form of the nodename of the workstation (like MyComputer, or MyComputer.Company.corp) When defining a thin-client workstation (i.e. one that will only access AeBRS via the web, it is required that the workstation name be based on the nodename as described. However for the thick client, the workstation name can be any unique string.
When the message Error loading workstation is displayed, it means that the server detected a mismatch between the workstation name as defined on the client, and the workstation table entries in the Config module on the server. On each client, the workstation name is defined in the config.m2r_cfg file, near the top, like this:
# Workstation Identification (has to match a name in the CHK_WORKSTATION table) WORKSTATION_NAME = WORKSTATION
TheSolution is to either (1) change the client entry to match the workstation, or the reverse. If you change the config.m2r_cfg file, then run codify_all.cmd, and then try to open MOC again to confirm whether the problem is resolved.
Keywords:
References: None |
Problem Statement: In the Aspen Production Execution Manager (APEM) Administrator tool, attempts to start the Audit & Compliance Extractor Service, or edit the Connection string, or change the debug level result in errors like this:
Or the above dialog, where the first line says:
Error at testing database connection
or
Error at saving logging properties
These errors happen even if the user is opening the APEM Administrator using an account that has APEM Administrator privilege granted in Aspen Local or Framework security. Also, other operations in the Administrator tool, like creating or restoring archives work correctly, for the account with that privilege. | Solution: The above errors occur because the Administrator account must be specifically granted rights to do Audit & Compliance Extractor operations. These rights are currently separate from the general Administrative rights that give a user in the Administrator role rights to all other APEM activities.
To grant the Administrator role the additional privilege of administrating Aspen Audit & Compliance Extractor tasks, right-click on the APEM application in Local Security:
and grant the privilege to the Administrator role:
To test these changes without waiting for a refresh of the Security server (which has a 5 minute update interval), use the Security Client Tool to immediately refresh the cache on the PC where the APEM Administrator is running.
IMPORTANT NOTE: CQ00426842, included in the V7.3 release, fixes typos in the error messages, makes the error messages themselves more clear (relating them to a missing Local Security permission), and correctly places the permission in the right-hand pane of the Security interface, and not as an application-level permission as it is in V7.2 and V7.1.
Keywords: Error at saving database connection string
Permission denied.Permission denied.
Error Code: 0x00000000
Error at saving logging properties
Error at testing database connection
References: None |
Problem Statement: Copy and paste functionality could help expedite work with RPLs -- i.e. copying and pasting Unit Procedures, Operations and Basic Phases from one RPL to another, or to a Control Recipe. | Solution: This functionality exists in the product:
In the source RPL, with the focus on the correct object, choose Copy. This copies the contents to the Windows clipboard.
Go to the correct target location (another RPL or a Control Recipe) and paste on the appropriate link (i.e. with a focus on a Unit Procedure link if pasting a UP, on a link in the Operation level, if pasting an Operation, or the same on the Basic Phase (BP) level.
Keywords: cut
duplicate
References: None |
Problem Statement: You get errors when using Extended desktop or multiple monitors when using MOC.
You may get errors such as Exception java.lang.IllegalArgumentException or MOC will close without warning. | Solution: Extended desktop or using multiple monitors while using Moc is not supported. Open MOC only on the main screen.
Keywords: Aspen Production Execution Manager
MOC
Extended Desktop
Multiple Monitors
References: None |
Problem Statement: This error message 'Error message address already in use JVM_Bind' will occur when attempting to use multiple MOC sessions. By Default MOC client uses port 8888. When multiple sessions of MOC are loaded it will use port 8888 and fail as the port is already in use. | Solution: There are two possibleSolutions to this issue.
1) Install multiple copies of MOC in different location then the default install or the location of your MOC install.
Once installed in a different location you need to edit the Config.M2r.cfg located in the AeBRS\cfg_source folder. Edit or Add the key NOTIFICATION_IP_PORT=xxxx (where x = port). Close and Save
Config.M2r.cfg
Note: Ensure that you run 'Codify_all' in same folder to ensure changes have been made.
2) If the Config files are stored on the Server then the you Open the server copy of the Config.M2r.cfg and Edit or
Add the key NOTIFICATION_IP_PORT=0. This will force MOC to use a ephemeral port between 0 and
65535 for each MOC session.
Note: Ensure that you run 'Codify_all' in same folder to ensure changes have been made.
Keywords: NOTIFICATION_IP_PORT
Aspen Production Execution Manager
AeBRS
PORT
References: None |
Problem Statement: How do I resolve the error message Error: E603:Positive number expected in method window validation action when using variables in graphical components? | Solution: This behavior can be prevented by disabling the flag:
COMBO_CLEAR_INVALID_VARIABLE=0
The flag can be added or edited in the file flags.M2R_CFG in the ..\Aspentech\AeBRS\cfg_source folder.
Once you have made the changes make sure you run the 'Codify_All' batch file in same folder.
Keywords: E603, MOC, Graphical Components, Variables
References: None |
Problem Statement: After patches are applied to an Aspen Production Execution Manager (APEM) server the MOC clients start displaying a message like this:
The problem persists even after the server is restarted. | Solution: This problem is typically caused because Java updates have been applied, and Apache Tomcat has automatically been redirected to use the latest JDK. For V7.3 and earlier, there are compatibility issues with JRE6. So if an automatic update starts running Apache under JRE6, Apache will no longer start up, and MOC clients cannot connect.
To check what Java Virtual Machine Apache is using, use the Monitor Tomcat application:
Opening the Monitor does not in fact display a GUI immediately, but instead adds the Monitor to your Windows Start Bar:
So open it from there, and go to the Java tab, and check the Java Virtual Machine that you are pointing to:
As also shown in the above screencap, browsing out the Program Files\Java level will show you all the JDK and JRE packages installed and available on the machine. Consult the Documentation for your version (the APEM Installation manual) for the supported Java Virtual Machine. V7.3, for example, supports JDK 1.5 and JDK 1.6. So to redirect a V7.3 Apache to use a supported JVM, the following choice could be made, selecting the jvm.dll:
Another way to verify what JVM the clients are using, which will also be a good choice for Apache, is to open AeBRS.cmd with Notepad, and check the Java path:
However note that the path here is to JAVAW.EXE, so the useful information here is the Java package being used, but it is still necessary to link to jvm.dll, as shown in the preceding screen cap.
Once the jvm.dll has been selected, Apache should start, and then MOC clients will connect again once they are restarted.
Keywords: Error Message: Notification server (where client is registered) not available - continue checking?
Apache not starting
Apache dead
Apache will not start
Apache disabled
eBRS server down
clients not connecting
RPL refresh
References: None |
Problem Statement: Every time a User Table is created in Aspen Production Execution Manager (APEM), two indexes are created by default. The primary index is PK_table, and a second index on the signature field to help speed up the record signature process, table_SIGN_KEY.
Internal SQL applies these defaults during the creation process of the User table. However for very large user tables, it may be desirable to store the table itself in one tablespace for example, and the indexes in another, or make some other customization to the table creation process. How can this be accomplished? | Solution: CQ00428111 adds the ability in V7.1 or later to customize the SQL that is executed during specific Config module activities:
SQL_CREATE_TABLE = create table {0} ( {1},constraint {2} primary key ( {3} ))
SQL_CREATE_INDEX = create index {1} on {0} ( {2} )
SQL_DELETE_TABLE = delete from {0}
SQL_DROP_TABLE = drop table {0}
If the above keys are defined in an APEM config file, then the SQL statements for each key will be used instead of the default internal SQL of the product. In other words, it allows the opportunity specify exactly HOW a table will be created when the user clicks Create Table in Config. The custom SQL will be executed, with the parameter values supplied from the Config module automatically. The SQL shown above is just example code. The expectation is a customer who defines these keys will work with a DBA to make any desired customizations.
For example a user creates this User table:
When the user clicks Create Table, the following two SQL statements will be executed:
SQL_CREATE_TABLE = create table {0} ( {1},constraint {2} primary key ( {3} ))
SQL_CREATE_INDEX = create index {1} on {0} ( {2} )
For SQL_CREATE_TABLE, using the generic SQL shown above, the bracketed items are replaced with the following values:
0 = table name
1 = field definition
2 = primary key index name (build by APEM based on table name)
3 = comma-separated list of ID fields
So for this example, the SQL executed is:
create table U_TABLE ( KEY_COL varchar(20) NOT NULL,VAL_COL varchar(80) NULL,EBR_SIGNATURE DECIMAL(38,0) NOT NULL, constraint PK_U_TABLE primary key ( KEY_COL ))
For SQL_CREATE_INDEX, using the generic SQL shown above, the bracketed items are replaced with the following values:
0 = table name
1 = index name (build by APEM based on table name)
2 = comma-separated list of index fields: only one used EBR_SIGNATURE
create index U_TABLE_SIGN_KEY on U_TABLE ( EBR_SIGNATURE )
For the last two config keys, the bracketed item is the table name.
ADDITIONAL NOTE: As of September 2011 this CQ is available for V7.1, by applying the latest patches. For V7.2 and V7.3 the same CQ is targeted to be included in upcoming Cumulative Patches. For V8, the enhanced functionality is targeted to be included at the time of release.
Keywords:
References: None |
Problem Statement: After upgrade of Aspen Production Execution Manager you start MOC and get the Error E4147 and In the MOC debug you get the error message EBR_CONFIGURATION_0.Invalid record
signature:ITEM=DB_VERSION,VALUE=11.3.0,SIGNATURE=1234567890 after an upgrade | Solution: This error may occur after you upgrade and start MOC without runing the AeBRS installer.
On the Aspen Production Execution Manager server run the AeBRSInstaller.
To do this open command prompt and navigate to to the AeBRS folder and then Run the command AeBRS AeBRSInstaller.
The command is case sensitive.
Keywords: E4147
MOC
EBR_CONFIGURATION
References: None |
Problem Statement: After the initial DVD install of the product, then running the Aspentech Database Wizard, the AeBRSInstaller must be run as the final configuration step of a new Aspen Production Execution Manager installation. However the following error may occur when launching the AeBRSInstaller: | Solution: This error can occur if manual edits are done to the configuration files in the aebrs\cfg_source directory, after the initial install, but before running the AeBRSInstaller program. It happens because once the Installer detects that changes have been made to the files, it expects there to already be data in the APEM database, when in fact it is still empty (i.e. the installer follows the upgrade path, not the new install path.)
To resolve the error return all config files to their original state, and run the AeBRSInstaller again.
Keywords: Database error: The INSERT statement conflicted with the FOREIGN KEY constraint EBR_INSTALL_AUDIT_REF1. The conflict occurred in database AeBRS, table dbo.EBR_USER,column ID_USER.
References: None |
Problem Statement: What are the possible approaches for having Basic Phases repeat? | Solution: To repeat a Basic Phase, or a series of Phases, there are two possible approaches:
1. Use the RPL Transition component of type Step transition to control whether the previous RPL element is executed again, once the flow of execution reaches the transition. If the transition evaluates to No, the flow of execution returns to the element above it. Once it evaluates to Yes, the previous element reaches a Finished state and the flow of execution passes the transition element.
2. It is possible to use repetition-related properties of the Basic Phase itself to configure repetition behavior. This separate design approach exists as a legacy of older APEM versions that did not include the Recipe environment. And the key properties (like Complete repetition and End when repetition reached can only be set at Design time, they are not configurable as parameters, severely limiting their functionality.
Here is more detail about each approach:
1. Using RPL Transition of type Step transition
This flexible approach governs the number of repetitions strictly through code provided by the Designer. (Finish writing this section.)
2. Using repetition-related properties of the Basic Phase.
It is possible to control whether or not a Basic Phase repeats using Properties of the Basic Phase itself in the RPL Designer. There are four related properties:
1. Complete repetition
2. End when repetition reached
3. Use Phase Return
4. End when convergent reached
Standard behavior of a Basic Phase is governed by the fact that Use Phase Return is checked by Default. This means that no repetitions will happen and when the Basic Phase finishes with Return Yes it will attain a Finished/Completed status. So the first step to modifying repetition properties is to uncheck Use Phase Return.
Once unchecked, the number of repetitions is governed by the two fields Complete repetition and End when repetition reached. The reason two fields exist is because it may be desirable in some circumstances to keep repeating a Basic Phase while, after a specified number of repetitions, releasing the flow to continue. Using the Pizza restaurant example, let's say a pizza can have six possible toppings. In that case, give Complete repetition a value of 6. After executing the first time, the Phase will get a status of Completed/Enabled and repeat. After the 6th repetition flow will continue to the next element, but the Basic Phase will still have a Completed/Enabled status -- attaining a Finished/Completed status will happen one of two ways:
A. If End when repetition reached also has a value of six, then after the sixth repetition, the Basic Phase will get Finished/Completed status.
B. When all of the Basic Phases that are part of that Operation finish, then any Phase in a Completed/Enabled status will automatically be changed to Finished/Completed.
Lastly, the End when convergent reached checkbox is useful when putting Basic Phases with a Complete repetition count into a Parallel construct. To exit a Parallel construct, all the Basic Phases it contains need a Complete status. So to keep the flow of execution from continuing, at least one Basic Phase (call it the Driver) should NOT have the property checked. All the other (let's call them Worker) Basic Phases should have End when convergent reached box checked. After the first repetition of each Worker phase they will all attain a Completed/Enabled status, but the Parallel will remain active as long as the Driver (which has no repetition count) has not completed. Once the Driver finishes, then based on the End when convergent reached property, all worker Basic Phases with at least one execution will also attain a Finished/Completed status.
Keywords: Aspen Production Execution Manager
Basic Phase
BPL
Repeat
References: None |
Problem Statement: How do I set Time Zone or/and Clock in Aspen Production Execution Manager MOC application?
The MOC application will use the Regional time settings on the Client machine by default. | Solution: You may want to change the time zone settings to show a different time zone.
To change this navigate to the location of your MOC configuration files.
By default this will be c:\Program Files (x86)\AspenTech\AeBRS\cfg_source.
1. Open the flags.m2r_cfg file with 'Notepad' in windows.
2. Search for the Key OVERRIDE_TZ =
3. Open the file Attached to this incident to look for the list of Country Codes and time zones allowed by Java.
4. Change flag ie. OVERRIDE_TZ = Europe/Paris
5. Save this file and close notepad
6. In the same folder you will see the file 'Codify_all.cmd'. Double click on this file and it will update the configuration.
Keywords: AeBRS
APEM
Timezone
Override
Override_tz
References: None |
Problem Statement: This | Solution: illustrates the reason why Atoms2Advisor is not sending the Temperature Reading on Temporary Integrators when importing movements from AtOMS to Aspen AdvisorSolution
By design AtOMS will NEVER send the actual temperature of an integrator to Advisor. For all the integrators AtOMS will send NET volumes to Advisor, set the water content to 0% and Temperature from the AtOMS2Advisor.ini file, which is the compensation temperature.To see how to set the temperature parameters to match the default units in Advisor please refer theSolution 125846.
If we send NET volume to Advisor and a temperature other than the compensation temperature, Advisor will compensate the volume again thereby net volume and mass calculated will be WRONG. As we are sending a net volume, then we have to set the parameters (temp and %H2O) to the compensation basis so Advisor does not compensate the volume again. That is just the way it is, by design. It is not possible to have the temperature and the water content from AtOMS sent to Advisor.
Even though AtOMS is not sending any values of properties to Advisor, it still shows READING for the properties because AtOMS2Advisor is sending the values, the compensation temperature and zero for water content respectively from the AtOMS2Advisor.ini file.
Keywords: Temporary Integrator
Temperature
References: None |
Problem Statement: Sometimes a User account no longer works. Why? | Solution: A User account in eBRS may go to Inactive status for two reasons: (1) the user account has had three successive log-in failures; (2) the current password has expired. If no password expiration date is set by the Administrator, an account will automatically go to Inactive status after 365 days.
Because of the extensive auditing features built into eBRS, it is possible to track all actions related to User accounts. Within the Audit Module, choose the User Login Failure table to see a list of all unsuccessful logins recorded by AeBRS.
An Administrator can change the User Account back from an Inactive to Active status to allow further log-ins.
In Version 7.0 and later, the User model has changed. Access to AeBRS applications is based on the Windows logon account. This gives the customer even more control over characteristics of user accounts, and is administratively simpler, since there is no longer a need to maintain a separate set of user identities, account characteristics and passwords. Regarding auditing, actions relating to log-in failures are no longer stored within eBRS though, since the entire User scheme is external to eBRS.
Keywords: lockout
expire
References: None |
Problem Statement: This knowledge base article describes how to change a data historian tag for a tank level in Aspen AtOMS. | Solution: o Modify the Instrument in Aspen Operations Reconciliation and Accounting (either TAG or TAG ALIAS).
o Go to the ATOMS ADMIN tool.
o In the Node Instruments tree, locate the LEVEL instrument to be modified. (sorting by NODE will help)
o Edit the instrument
o Modify NAME with the new TAG (not necessary but avoids confusion)
o Be sure that INSTRUMENT NAME IS THE same AORA instrument (selected from the list box). This level should be linked to the equivalent level instrument in AORA so that AtOMS can use the strapping table.
o Double check in the tab DETAILED that the INSTRUMENT ID is the DBINDEX in AORA.
Keywords: Aspen InfoPlus.21
IP.21
PI
PHD
References: None |
Problem Statement: Aspen Tank and Operations Manager (AtOMS) monitors cannot connect to database on Windows 2008 R2 x64 platform. | Solution: The Connection Error was a Result of the ODBC connection in Windows 2008 Server 64 bit. The connection string used in AtOMS Config is not the same as the one used by the AtOMS Monitors.
The AtOMS Config points to the DSNs configured in Windows 64 bit OS which is normally accessible in the Control Panel; while the AtOMS Monitors are STILL accessing Data Sources configured by the ODBC 32 bit version which is found under C:\Windows\SysWOW64\odbcad32.exe
Thus in Windows 2008 Server R2 64 bit, 2 ODBC connections have to be added in 2 different locations.
Keywords:
References: None |
Problem Statement: When trying to log in to MOC authentication can fail with different messages. This knowledge base article explains why these error messages occur. | Solution: 1. Problem: Correct account, but not sufficient privileges.
means that MOC is successfully contacting the Aspen Local Security or Framework server, but that the Windows user account does not have sufficient privileges to log in. Make sure that the Role the user belongs to has at least MOC user permission.
If there is a problem with the translation files, then instead of the above message you will see a dialog box that says chkusernotuser.
2. Problem: Incorrect Windows credentials.
This message displays when the Windows domain controller does not authenticate the account. It is not an Aspen eBRS error. Resolve this problem by checking with your I.S. Administrator. Possible reSolutions are (1) the account is locked and refusing authentication, (2) the password is incorrect (make sure Caps Lock is not on.)
If there is a problem with the translation files, then instead of the above message you will see a dialog box that says chkinvaliduser.
For some Aspen eBRS customers it is critical to do an account authentication when MOC is opened (especially in environments concerned with 21 CFR 11 compliance.) If that is not the case and you would like MOC to attempt opening directly based on the account of the current Windows user (the interactive user) read KB Article #121425 for more information.
Keywords: chkusernotuser
chkinvaliduser
login failure
log-in failure
References: None |
Problem Statement: Aspen Production Execution Manager (APEM) Basic Phase Designer includes an image component.
However it does not allow a .BMP image to be referenced successfully for display on a BP screen: | Solution: BMP is not a supported format. All images added must be either GIF or JPG format.The restriction is not directly imposed by APEM in fact, but is inherited from the Java environment, which does not support BMP images.
Depending on the image source, a BMP file can be very large, several megabytes, but the same image saved as GIF or JPG will typically be a few hundred kilobytes, or even smaller. Also, since all BP designs are saved to the Relational Database, this is a good way to avoid quickly increasing the size of the DB because of saved image, and of course also means that screens will load and display faster, since they are not carrying large image files with them:
Keywords: jpeg
tiff
png
flashpix
pdf
References: None |
Problem Statement: Even after following advice in Knowledgebase Article 114292 to increase memory available to the MOC execution environment, you may get Out of Memory problems when working within modules like Config, Templates and Audit. Why? | Solution: This happens because Templates, Audit and Config are really separate programs being launched from the MOC environment, so they have their own default memory parameters (Workstation and other MOC functionality all execute within the memory space defined according to Knowledgebase Article 114292.)
A global allocation is available for Templates, Audit and Config by editing the path.m2r_cfg file in the cfg_source directory. By default, the relevant entry looks like this:
# Execute Java command format
# {0} = contains module name
# {1} = classpath
# {2} = Java runtime directory (i.e.: <java.home> - {2}\bin\java.exe should be used to call Java)
# If not defined defaults to 'javaw -cp {1} {0}' (quotes not belonging to definition)
# (no need to use {2}, as Java launches application using current Java Runtime Environment)
# JAVA_EXEC_COMMAND = {2}\\bin\\javaw -cp {1} {0}
To control how much memory is available for these three eBRS modules, the edits would look as follows (refer to your own AeBRS.cmd file for the settings particular to your eBRS system:
# Execute Java command format
# {0} = contains module name
# {1} = classpath
# {2} = Java runtime directory (i.e.: <java.home> - {2}\bin\java.exe should be used to call Java)
# If not defined defaults to 'javaw -cp {1} {0}' (quotes not belonging to definition)
# (no need to use {2}, as Java launches application using current Java Runtime Environment)
JAVA_EXEC_COMMAND = {2}\\bin\\javaw -Xmx128M -cp {1} {0}
Notice the only changes are (1) uncomment the JAVA_EXEC_COMMAND line and add the new memory allocation (default is 64 megabytes, and in this example we have doubled it to 128 megabytes.)
After making the edit, save path.m2r_cfg and run codify_all.cmd in the cfg_source directory to commit the change. When MOC is reopened, the change takes effect.
Further Explanation
There is no need to supply a value for {0} -- when you choose to launch a specific module, this argument is passed by MOC.
There is no need to supply a value for {1} -- when you choose to launch a specific module, this argument is passed as the classpath from the AeBRS.cmd file automatically.
There is no need to supply a value for {2} -- as the configuration module itself explains, the current JVM runtime environment is assumed, since these modules are launched from within MOC.
Keywords: None
References: None |
Problem Statement: When trying to run the Version 2006 AeBRS Installer program like this, for example:
This error results: | Solution: Java is a case-sensitive programming language. Because the call is a request to a Windows CMD file (AeBRS) which is not case-sensitive, but carrying a parameter to a Java program which is (AeBRSInstaller) it is important to type the argument to AeBRS precisely as shown below (and as documented in Appendix D of the Version 2006 installation manual):
Keywords: Could not find the main class. Program will exit.
AeBRS AeBRSInstaller
References: None |
Problem Statement: If a connection to an Aspen InfoPlus.21 database is configured in the Aspen eBRS external_db.m2r_cfg file using a DSN based on the SQLPlus driver, the connection inherits the credentials of the interactive window session, not the username and password specified in the connection properties. If no Aspen InfoPlus.21 security is used, this situation may not be noticed, but when database security is applied, write requests from Aspen eBRS will start to fail. The preferred situation is that the Windows user, and the Windows account used to access MOC both have limited rights to InfoPlus.21 (for example read-only), but the actions taken within a MOC session (for example, executing a Basic Phase which needs to read and write InfoPlus.21 data) have elevated privileges based on the credentials in the external_db.m2r_cfg file.
How can an Aspen eBRS system be configured to enable this? | Solution: SeeSolution 121868 for general information on how to configure the external_db.m2r_cfg file. ThatSolution explains each element of a connection definition. As discussed in detail in that article, connections to external relational databases are defined, and any necessary username/password information can be successfully passed to get the correct security context.
However in the case of InfoPlus.21, to pass credentials successfully, the configuration is slightly different. The DB_URL_1 line defines the connection, using the local SQLPlus Driver and providing the node information, so the driver knows where to connect. Using this approach, the username and password are passed successfully:
# Information for IP.21 connection
# AspenTech SQLplus Driver.
DB_NAME_1 = MyIP21
DB_DESC_1 = connection to InfoPlus.21
# Type. InfoPlus.21 Type not defined (inherits DB defaults.)
DB_TYPE_1 = INFOPLUS.21
DB_URL_1 = jdbc:odbc:DRIVER={AspenTech SQLplus};HOST=MyIP21Server
DB_DRIVER_1 = sun.jdbc.odbc.JdbcOdbcDriver
DB_USER_1 = MyIP21Server\\MyAccount
DB_PASSWORD_1 = MyPassword
The internal eBRS code will call this connection by referring to MyIP21, the DB_NAME_1 parameter. For example this line:
DB_SELECT_ONE(MyIP21,SELECT IP_INPUT_VALUE FROM OvenTemp,MyTemp)
will return the current value of the IP_INPUT_VALUE field from the tag OvenTemp into eBRS variable MyTemp.
As a final note, this configuration can be used in any Aspen eBRS version from 5.0 forward. However the ability to accept a username and password was added to SQLplus ODBC driver in Version 2004.1, so the IP.21 being connected to should be at least at that version.
A future version of eBRS (later than 7.1) will include example configuration like the above in the external_db.m2r_cfg file for connecting to an InfoPlus.21 system in a way that allows security credentials to be passed successfully.
Keywords: Access Denied
References: None |
Problem Statement: How do Effective and Expiration dates work within Aspen eBRS? | Solution: Effective and Expiration dates physically block objects from being used. However the blocking action is based on hierarchical relationships. Therefore a Recipe (RPL) operating within its own Effective and Expiration dates can use an expired Basic Phase Library (BPL.) And in turn a Master Recipe (MR) operating within its valid date range can use an RPL that is expired. Objects higher in the hierarchy override effective date ranges of objects lower in the hierarchy.
Even though higher objects override lower objects another important point is that attempting to certify a MR that includes a lower object out of its certified date range will fail.
So in practice an Aspen eBRS application can be brought into production only when all objects up and down the hierarchy are certified, but any object except the top one (typically a Master Recipe) expiring does not disable the application.
Keywords: None
References: None |
Problem Statement: When calling OpenUserConnection(), user is unable to obtain a session identifier and gets 0 instead. | Solution: This is due to permissions issue.
1. Check that the domain logon name is specified in the following format: domain_name\username.
2. Check that the domain logon name is assigned to a role with permission to make API calls.
Keywords: OpenUserConnection
API
session identifier
References: None |
Problem Statement: The Software Requirements section of the Aspen Production Execution Manager Installation Guide does not mention IIS. Does that mean it is not required on a Production Execution Manager server? | Solution: IIS is not listed as a requirement because the Production Execution Manager web server is an optional subcomponent of the installation. If thin clients are part of theSolution being deployed, then the web server is required. The web server itself can be installed on the server or another node. Wherever it is installed, IIS is required.
CQ00381471 has been entered, requesting a clarification to the Software Requirements section of the Installation Guide to document the dependency between IIS and the Production Execution Manager web server subcomponent.
Keywords: sub-component
References: None |
Problem Statement: How do I test for Null or Empty Array Element values in Aspen Production Execution Manager? | Solution: This problem lays in the fact that what it is stored in EBR_MASTER_RECIPE_PARAM.VALUE is an expression, not actually a value. So, there are strings containing (two double quotes), not simply an empty string (which, by the way, cannot be recorded into the Aspen Production Execution Manager database and end up as NULLs).
vb_testcy1:=(as_ArgumentValue[vi_XCtr] = ) will do
Double quotes are represented doubling them inside string which Aspen Production Execution Manager wraps with double quotes automatically resulting in a sequence of 6 double-quotes shown above.
Keywords: Null
Array value
References: None |
Problem Statement: It is possible to use Aspen Production Execution Manager (APEM) run-time variables to dynamically change various background and foreground object and text colors. But where is the Documentation? | Solution: Documentation will be added in a future version.However to see the properties and their syntax, load the attached .CHK file into an empty Basic Phase in a BPL, and then execute it from the BPL library to see the effect of run-time background and foreground color settings, and examine the code to see all the syntax.Exposed controls in the example CHK file allow you to make changes and see the results during run-time:
Keywords: Design
References: Guide
AeBRS
eBRS |
Problem Statement: A customer administrating an Aspen Production Execution Manager (APEM) system where the server and all workstations have French Regional Settings asks the following:
How come in codify_all.cmd, the codified language source file is written to a language file with the extention lng_en.lng?
example :
...codify D:\Mes\AEBRS\cfg_source\AeBRS_FR_v01.txt D:\Mes\AEBRS\resource\AeBRS_FR_v01.lng_en.lng
why not:
AeBRS_FR_v01.lng_fr.lng
or
AeBRS_FR_v01.lng
Note that in path.m2r_cfg file, the language file referenced is:
LANGUAGE = AeBRS_FR_v01.lng | Solution: If there is no need for custom vocabulary (i.e. the system default for a new install) then you will see in path.m2r_cfg
LANGUAGE =
In this case nothing extra is specified. Of course most customers have custom terminology they want to define and, if they have the same application in use in different locations, they may even want to define those custom terms in several different languages. In this case we suggest a root name (though even this is user-definable) like AeBRS_v01. So in this case, the LANGUAGE key value in path.m2r_cfg would be updated to read:
LANGUAGE=AeBRS_v01
Then in the resources folder it is necessary to define individual language files for every desired language, using an extension that is in the form _en.lng, or _fr.lng etc., like:
AeBRS_V01_en.lng
AeBRS_V01_fr.lng
AeBRS_V01_de.lng
At startup, an APEM client asks the operating system for its Regional settings. If the answer comes back French, to use an example, then the _fr.lng file will be used. If an answer comes back for a language for which no resources file exists, then the system will default to English. Using these examples above, the same application would pick up German language keys (_de.lng) for a workstation with German Regional Settings, and French language with French Regional settings, and any other setting will end up defaulting to English.
So in fact, it is OK to define a key such as LANGUAGE=AeBRS_FR_v01 and it will work fine, but if you define the key like that, you then need to name your resource file for French like:
AeBRS_FR_v01_fr.lng
to be properly integrated at startup. For that reason we suggest staying with the simpler root of AeBRS_v01
A method to know what valid two letter combinations work for various regions is to go into the BP language tab in the BPL window, click Plus to add a language, and the displayed list shows all valid codes.
Of course once you decide on a particular naming convention, you may need to edit your codify_all.cmd file so any edits to your language resource files can be compiled for use.
Keywords: local
locale
localization
localisation
References: None |
Problem Statement: The variable explorer in Aspen Plus will help you determine the correct path-to-node name and find-node names for most Aspen Plus objects (see | Solution: document 106094). The trouble is that that the syntax for the methods and properties of those objects is not always obvious. Tabular data is also challenging to format the correct syntax.
Are there any VB or VBA tools to aid in creating the proper syntax for retreiving and manipulating these Aspen Plus objects?
Solution
Inside the Visual Basic Editor are 2 useful tools:
1. The Immediate Window (Click on the VIEW pull-down menu and then Immediate window). It allows you to test code real-time without disturbing your current subroutines. It saves a lot of time over writing tracer statements.
2. The VB Editor's Object Browser (also located on the VIEW Pull down menu).Change the ALL LIBRARIES filter at the top to HAPP to show just the Aspen Plus objects. To get a partial syntax on the control panel's Move-To capability, in the line below the HAPP or ALL LIBRARIES entry, type move and then click on the binocular button to find all properties and methods that contain the word move in their name or description. See the below screen snapshot.
The best way to test syntax is a combination of both the object browser and the immediate window. Using the above Move-to example, the object browser does not give us enough code instruction. If for example, you wanted to move the calculation sequence to block B2 in the PFDTUT.bkp file (found in the Aspen Plus example folder c:\Program Files\AspenTech\Aspen Plus xxxx.x\Gui\Xmp, where xxxx.x is the Aspen Plus version number), here is a sample session in the immediate window:
first determine if the Aspen Plus simulation is connected to the VB editor
go_simulation.Name
type this line & hit enter
Aspen Plus 12.1 OLE Services
ask the name of block b2 to verify the syntax of the block's path-to-node name
go_simulation.Tree.Data.Blocks.B2.name 'type this line & hit enter B2
The prompt at the bottom of Figure 1 alerts us that the MoveTo method expects two arguments; IAP_MOVE_TO_TYPE and the name of the block. Look in the SEARCH RESULTS frame of Figure 1. The top two rows have a CLASS type of IAP_MOVE_TO_TYPE. The member displayed in the second row will allow you to move the calculation sequence to the utility report calculations with if you use it's IAP_MOVETO_UTILITY member. If you want to move to a BLOCK, you would have to scroll the object browser up a few rows until you see IAP_MOVETO_BLOCK, which has an integer value of 0 assigned to it (according to the prompt at the bottom of the object browser). We could write the value of 0 for the first argument to the MoveTo command, but using the IAP_MOVETO_BLOCK constant makes the code more readable.
Now try the move to command. From the object browser, we know move-to is a subroutine and will need a CALL statement. Type the below line in the immediate window:
call go_simulation.engine.MoveTo(IAP_MOVETO_BLOCK,B2)
type this line & hit
If the above command does not cause an error, then the syntax was correct.
Keywords: VBA, immediate window, object browser, syntax
References: None |
Problem Statement: The display value for density in Specific Gravity is rounded to 2 decimal places even though it accepts 4 decimal places (as it should be). This applies to movements and tank events. The value in the database tables is correct, but since the display is rounded, it confuses the operators. | Solution: Following are the steps to overcome this problem:
1. Go to Atoms Administrator
2. Expand Instrument_type
3. Double-click on DENSITY
4. Set the value DECIMALS to 4.
5. Press on ACCEPT
Keywords: None
References: None |
Problem Statement: Aspen AtOMS application can access a database such as Aspen Infoplus.21, to create cut-off for a tank and movements. There are some situations, where Monitor can read Current value from the database, but it is not creating cut-off. | Solution: If ADSA Connection protocol is 'DCOM' and the system has DCOM configuration issue (default DCOM is changed for some reason), then AtOMS Monitor can read current value from the database, but can not create Cut-off instruments.
In this case, please change the ADSA Connection protocol to 'Web Services'; it should create a cut-off for both tank and movements.
Keywords: Cut-off
AtOMS
RTDB
References: None |
Problem Statement: Can Aspen Tank and Operations Manager handle LPG Vapor space for Mass calculation ? | Solution: Yes. Starting from V7.1 and above Aspen Tank and Operations Manager starting (AtOMS) handles LPG Vapor Space for mass calculations, similar to the way Aspen Operation Reconciliation and Accounting(AORA) handles.
In AORA, we need to choose product type as LPG, to enable this Vapor Mass Calculation.
Total Mass of a LPG in a Sphere= Mass of a Liquid + Mass of Vapor contained in the LPG Sphere.
AtOMS V7.1 and higher uses the same formula as mentioned above.
Note: Both AtOMS and AORA shares common equation library ( iiequa32.dll) from starting from Aspen One V7.1.
Keywords: LPG
Vapor mass
References: None |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.