question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
|---|---|
Problem Statement: This Knowledge Base article explains what BCU does when it finds a bad value. | Solution: The BCU accesses trends of data during trigger condition analysis, and accesses individual time-points of data during sub-batch/characteristic/command execution.
Trigger condition analysis
As per the online help you select the Ignore bad data between good samples checkbox (defined for each trigger in the Conditions tab) to specify that bad data points occurring between two otherwise good data points be ignored.
This is how this works: During trigger condition analysis, at each time-point under consideration, the BCU condenses its conditions into a single FALSE or TRUE value. In a transition trigger, the trigger will fire when this aggregate truth changes from FALSE to TRUE.
However, in order to fire the trigger, the BCU must have good data at both of those time-points: if the data went from FALSE to Bad to TRUE, it is impossible to tell exactly when the trigger should have fired in that bad-data region.
The BCU follows the principle that no data is better than incorrect data, so it does not fire the trigger; instead, it writes a log file message and stops processing. However, the user can set the Ignore bad data between good samples option to tell the BCU to ignore the data dropout, fire the trigger and continue processing.
Execution of a sub-batch/characteristic/command
Bad data points are not used to compute characteristics. A characteristic will only be recorded based on good tag values. Otherwise, we would end up with unreliable batch data.
During action execution, there are no workarounds for bad data. If designator tags have bad data for the time-point at which it is desired to fire the trigger, it is impossible to determine which batch the data should be recorded for, and the BCU writes a log file message and the unit fails (stops processing) and the user must fix the bad data point.
Keywords: GOOD DATA
BAD DATA
CHARACTERISTICS
TRIGGERS
SUBBATCH
References: None |
Problem Statement: How to read values from a repeat area of a record using ODBC Access through ADO in VB | Solution: This task can be accomplished by writing a Visual Basic program for a form with a command button and a listbox. The example code below gets the last hour of history from a hard coded record name ( i.e. ATCTIC301) into a recordset object then fills a list box with the results.
This code could be used in either VB or VBA (for Access or Process Explorer or Excel) provided that the Microsoft ActiveX Data Objects library is loaded as a reference to the application. This library comes with VB and also can be downloaded from Microsoft.
*********************************** VISUAL BASIC code *************************
Dim adoCon As New ADODB.Connection
Dim adoRecords As ADODB.Recordset
Dim qrystr as String
Private Sub Command1_Click()
'open a named ODBC DSN
adoCon.Open (SQLplus on localhost)
'build valid sqlplus query
qrystr = Select ip_trend_value, ip_trend_time from ATCTIC301 where ip_trend_time > (current_timestamp - 1:00)
'execute query and put results in recordset variable
Set adoRecords = adoCon.Execute(qrystr)
'cycle through recordset putting data into listbox
List1.Clear
Do While Not adoRecords.EOF
List1.AddItem adoRecords!ip_trend_time & & adoRecords!ip_trend_value adoRecords.MoveNext
Loop
'close the connection
adoCon.Close
End Sub
Keywords: ODBC Access
References: None |
Problem Statement: The Batch Handles column can''t be removed in the right-hand pane of the Batch Query Tool. | Solution: To allow for full functionality of sorting features and drag-and-drop in the Batch Query Tool, the batch handle field must be in an actual column and visible.
Keywords: BQT
handle
References: None |
Problem Statement: Aspen Production Record Manager usually gets the process data from Aspen Infoplus.21 and stores the Batch information in a relational database like SQL Server or Oracle.
But, some customers have their process data stored in PI-OSISoft and want to to view the batch information using the process data directly from the PI-OSISoft instead of getting the data from Aspen Infoplus.21. Is this possible ? | Solution: The answer is yes, you can configure Aspen Process Data for PI instead of Aspen Process Data for IP21, and Aspen Process Record Manager(APRM) and the BCU will work.
1) Open ADSA by going to Start>Programs>Commom Utilities>ADSA Client Config Tool
2) Click in the Public or User Datasource button depending if the datasource will be available for other users or not
3) Create a new DataSource (called PI for example):
4) Click in the edit button and the service Aspen Process Data (PI)
5) Click in the configure button and fill the information related to the PI server
Then you can set the BCU to log batch start/stop events based on data from PI OSI-Soft, instead of Aspen Infoplus.21
Keywords: PI
Osisoft
APRM
BCU
References: None |
Problem Statement: When using the Aspen Add-In in Microsoft Excel and selecting New in Production Record Manager or BCU sections in the Aspen Configuration menu an error occurs.
Aspen Production Record Manger Configuraiton Add-In
BCUConfigurationViewModel::OnOpenBCUTemplate:Exception
from HRESULT: 0x800A03EC | Solution: Excel VBA (Visual Basic for Applications) is the name of the programming language of Excel. With Excel VBA you can automate tasks by writing programs called macros.
The Aspen Add-In Production Record Manager and BCU menus in the Aspen Configuration menu use VBA commands to do their work. You'll receive this message when VBA is not enabled in Microsoft Excel.
The follow ing steps are for Excel 2010; the steps for other versions of Excelmay be slightly different.
To enable VBA in Microsoft Excel, use the File -> Options menu and select Customize the Ribbon . You then have tick the Developer box to allow the Developer icon to appear.
You also have to allow in Microsoft Excel to run programs included with spreadsheets. To do this use the File -> Options menu again but this time select the Trust Center and the Trust Center Settings.
Select Macro settings and finally select enable all macros.
Keywords: Aspen Production Record Manager, Configuration, VBA
References: None |
Problem Statement: Aspen Batch.21 automated calculations - When variables are bound to timestamp characteristics, the timestamp is expressed in UTC. Is this the expected behavior? | Solution: Yes. this is as designed. The server is executing this in the background and all processing is UTC based.
Keywords:
References: None |
Problem Statement: When building Aspen Golden Batch Profiles a user would use one tag for one profile and a different tag for another profile etc.
The question arose as to whether it was possible to create an Aspen Golden Batch Profile using such as ={Tag1+Tag2} | Solution: The answer is NO.
You would need to create a new tag record and, using such as Aspen Calc or Aspen SQLplus, do the math to write to the new tag record and then use that when building the new Profile...
Keywords:
References: None |
Problem Statement: This Knowledge Base article shows how to resolve the following error message:
Error: Unable to create license component.
which may be received when executing a dynamic query in Aspen Production Record Manager (APRM) Excel Add-in in Microsoft SharePoint. The above error may also be received when executing an Aspen Process Data Add-in query. | Solution: On your Windows Server 2008 R2 64-bit system go to the following directory
C:\Program Files\Common Files\Hyprotech\Shared
and register file STRGXI2.dll using the 64-bit version of regsvr32 as shown below:
Keywords:
References: None |
Problem Statement: What are the names of the services which get installed by AspenTech client applications? | Solution: Potentially, there are only two services that get installed on client computers: a service called Noblenet Portmapper for TCP that gets installed whenever Aspen Process Explorer is installed, and AspenTech Calculator Engine service that gets installed whenever the Aspen Calc client is installed.
Below are the names of the applications typically installed on your client computers. No services are installed with these applications:
1.. Aspen Process Data
a.. Process Data for InfoPlus.21 and Setcim -- no service is installed
b.. Process Data File -- no service is installed
2.. Aspen Process Explorer
a.. Event.21 -- no service is installed
b.. Q for Process Explorer -- no service is installed
c.. Aspen MultiVariate -- no service is installed
3.. Batch.21 Client
a.. Application Interface -- no service is installed
b.. User Tools -- no service is installed
c.. Plots -- no service is installed
4.. SQL-plus client -- no service is installed
For users with Administrative privileges the installations would also include:
1.. Batch.21 Client
a.. Administration Tool -- no service is installed
b.. BCU -- no service is installed
2.. Definition Editor -- no service is installed
3.. InfoPlus.21 Administrator -- no service is installed
Keywords:
References: None |
Problem Statement: Can you change the Description field for ad-hoc calculations? | Solution: In versions prior to Version 2006, it is not possible to specify or modify the Description field for Ad-Hoc calculated pens.
However Frank Weishaeupl of Nordzucker AG pointed out a helpful work-around. Even though the Description field itself cannot be modified, by adding a single quote at the end of the formula a text string can follow, providing much the same utility:
But as far as the ability to control the Description field itself via an ad-hoc calculation, various enhancements were considered to enable the modification of the description field for this type of pen. However the bug review committee determined that it would be inadvisable to make the Unit field and the Description field changeable for all legend entries, because these changes would be saved in the plot file, and would override information stored in the actual tag record.
In version 2006, Shared On Demand calculations were introduced. These type of shared calculations allow the user to create ad-hoc calculation records that can be used by all clients, and they allow the Description and Units to be defined as desired.
Keywords: adhoc
ad hoc
Aspen Calc
References: None |
Problem Statement: Why do I get an error class not registered error when starting BCU server?
When Starting the BCU server from the Aspen Production Record Manager Administrator you get a message
Class not registered shown in first screenshot. You cannot select a data source or Start the unit scheduling.
Another error message may show when starting the Unit Scheduling as shown below. | Solution: This error can show when the Aspen Production Record Manager files have become corrupted or not registered.
To resolve this issue follow the steps below.
1. Close the APRM Administrator and BCU administrator
2. Open a Command prompt
3. As shown in the second screenshot navigate to folder
For 32 bit systems c:\Program Files(x86)\AspenTech\Batch.21\Client\
For 64 Bit systems c:\Program Files\AspenTech\Batch.21\Client\
4. Run the command Regsvr32 Batch21services.tlb
5. You should get a message that the file above is registered.
6. Open the APRM administrator and try and start the Unit Scheduling but Right Clicking BCU and select 'Start Unit Scheduling'
If this step does not work you will need to repair the APRM installation using the DVD. This does not effect the Product configuration when running the repair.
Please seeSolution KB119149
Keywords: Class not registered
BCU
APRM
Aspen Production Record Manager
Batch21
Batch.21
References: None |
Problem Statement: This | Solution: outlines new features in the Aspen Production Record Manager V8.5 administrator.Solution
Aspen Production Record Manager V8.5 introduces the following new features:
1. Supporting 64-bit Installation
Aspen Production Record Manager supports 64-bit installation.
2. Working with Microsoft’s Failover Cluster
Aspen Production Record Manager (APRM) is designed to work with Microsoft’s Failover Cluster feature. The cluster here refers to a group of managed computers that appear on a network as a single computer having its own network IP address. The computer that currently owns or hosts the server application is called the owner computer. The computer that is ready to become the owner, when called up, is called the ready computer. Multiple ready computers in one cluster is allowed. When APRM server is added to a cluster, an APRM group will be created, along with a network name, IP address, and a shared disk. Then, a generic service resource is created for each Windows service on which the application depends.
The application data and configuration files are copied to the shared disk. In addition, certain settings in the Windows registry file are configured for synchronization between clustered computers.
When a failure results in a failover, Microsoft’s Cluster Service processes the following stages:
· Services are stopped on the failed computer.
· Ownership of the shared disk is moved to the next ready computer.
· Network traffic is re-routed to the ready computer.
· Registry data is synchronized on the ready computer.
Keywords: APRM
Batch.21
What's New
V8.5
Cluster
64bit
References: None |
Problem Statement: In a clustered | Solution: while configuring the Aspen Production Record Manager using the Aspen Wizard, which server name is created in Database, will the Aspen Wizard use the cluster name or the single cluster nodes?Solution
When configuring the Aspen Production Record Manager using the Aspen Wizard, it normally creates a <server name>\<user> in the database. In a clustered environment, it will use the cluster name as the server name instead of the single cluster nodes since the machines will use this name in the connection string.
Keywords: clustered
APRM
Aspen Production Record Manager
Server name
User
Aspen Wizard
Database
References: None |
Problem Statement: How do I use Ad-hoc calculations to display values for one tag on the basis of criteria applied to one or several other tags? | Solution: It is possible to write a simple join condition with a Process Explorer Ad-hoc calculation. Such a calculation would
allow the user to impose a relational context onto data stored in InfoPlus.21 tags which otherwise are by their
nature completely non-relational. The goal is to permit the user to select values for one tag by applying a filtering
criteria based on one or several other tags. Here's an example using the Aspentech demo tags:
=if ATCPRODN =1 and ATCQUAL > 75 and ATCQUAL < 79 and ATCMADE > 1800 then ATCTIC301
This calculation displays values for ATCTIC301 only when ATCPRODN (product made_ = 1),
ATCQUAL (product quality) is greater than 75 and less than 79 (between 75 and 79) and
ATCMADE (amount of product made) > 1800 for a particular time range. So for the time range selected in the
Process Explorer Timeline control, the user will not see all the values of ATCTIC301, but only those where
all the filter conditions are True. The X's indicate time ranges where these conditions are not True.
The values can also be viewed in the data table and in the Excel Add-In.
Ad-hoc calculations like this can be used to describe simple or complex process interactions between several
or many process variables. This allows the users to codify their knowledge of useful and meaningful relationships
between process variables using a relatively easy to write Ad-hoc calculation syntax. This technique can be used
in hindsight. For example, show me how often the specific interaction described in the Ad-hoc calculation has
occurred in the last 12 months. The user can use this technique to explore the interaction by adjusting the filter
criteria interactively and observing the results.
This sort of Ad-hoc calculation can also be used as a real time monitoring technique. To do this the equation
might be modified to:
=if ATCPRODN =1 and ATCQUAL > 75 and ATCQUAL < 79 and ATCMADE > 1800 then 1
When this Ad-hoc calculation is added to the Legend, the value for the pen will only show up as a current value
when the interaction is actually True right now. If the pen is not visible, the conditions for the interaction are not
happening right now. When used this way, the Ad-hoc calculation could be used like an alarm flag indicating that
the process is headed for trouble. This same type of Ad-hoc calculation could also be used as an indicator for
flagging ideal or best practice conditions. Show me the Ad-hoc value when the reactor temperature is between this
and that and reactor pressure is between this and that and line speed is between this and that, and ph is between
this and that and the product is X. The idea is that plant personnel know that if all these conditions are true, then
you're in the sweet spot and things are going well. The value of 1 for the Ad-hoc pen on the plot would be a constant
confirmation of this. When the process slips out of the good zone zone the 1 indicator would disappear signalling
a potential problem with one or several of the variables. It might take several Ad-hoc calculations to describe all the
relevant interactions that define best practice for the process.
It's important to note that these sorts of multi-variable Ad-hoc equations are not automatically supported by any
statistical inferences like SPC variables would be. However, an Ad-hoc calculation could be used to describe a
multi-variate model that was generated using PLs or PCA methods. They could also be used to describe simple,
first principle models. They could easily be used to describe relatively simple models based on empirical observations
of the process for years. Such a situation might be described by When this particular combination of circumstances
happen it's bad news for the process! We're not exactly sure why but we want to react as quickly as possible to
remedy this situation.
There are a wide range of possible applications for this simple but powerful technique. The user is encouraged to
experiment with the syntax until they get the hang of it. Any valid Ad-hoc syntax as well as On-Demand or Shared
calculations can be included in the calculation. The order of precedence within the calculation can be controlled by
using parentheses.
Keywords: adhoc, Ad-hoc, On Demand, Aspen Calc, calculation, join, criteria
References: None |
Problem Statement: PROBLEM 1:
After running a silent install of the AMS software, MicroSoft Excel gives the following message when loading the Aspen Process Data Add-in:
Compile error in hidden module: Atglobal
This error only occurs if the software was installed with the silent install procedure. If a normal install was used to setup the software, Microsoft Excel launches without the error.
PROBLEM 2:
Error when adding the Aspen Process Data Add-in: Compile error in hidden module: Atglobal. This problem was reported with MicroSoft Office XP 2002 but may be relevant with other versions of Office as well. | Solution: Solution 1:
The error message is a result of the TimeDialogs.exe file not being properly registered during the silent install. To fix the problem, open a command prompt, change directory to the \Program Files\AspenTech\APEx\Pe\Addin location and manually register the TimeDialogs executable. Make sure to register the file using an account with Administrator privileges on the machine. Detailed instructions are listed below:
C:
cd \Program Files\AspenTech\APEx\Pe\Addin
TimeDialogs /regserverSolution 2:
To solve this problem, uncheck the boxes for these Add-Ins:
Analysis ToolPak
Analysis ToolPak - VBA
This will then allow you to add the Aspen Excel Add-Ins.
Keywords: None
References: None |
Problem Statement: Some sites have complicated network configurations. In some cases, a site will use DHCP in conjunction with a WINS Server, and DNS. With this type of configuration, there are cases where Process Explorer is unable to trend data from the InfoPlus.21 Server.
The symptoms will be that the tag browser works, however, when a tag is taken from the Tag Browser and placed onto a trend plot the window hangs. The window will just hang for several minutes and eventually the value field in the legend of the trend plot will say, unspecified error.
If the PE application is killed while the trend plot is hanging, the APEX task in the IP.21 Manager dies. | Solution: The network needs to be configured for WINS host name reSolution and reverse lookup reSolution. The InfoPlus.21 Server must be able to perform a successful nslookup of the Client PC using both the client's nodename and TCP/IP address. See the attached document for information on this configuration.
Keywords: nslookup
References: None |
Problem Statement: The Process Data | Get Data | Attribute Values... function will not work for Excel worksheets that contain spaces in the worksheet name. For example, changing the worksheet name from Sheet1 to Sheet 1 will cause the function to return an error similar to:
#ERROR 50103: Bad Attribute 'Sheet 1!$C$1 | Solution: The only workaround is to change the name of the worksheet so that it does not contain spaces.
Keywords: bad attribute
References: None |
Problem Statement: After a new installation of Aspen Manufacturing Suite (AMS) suite, whenever you open the AMS application, there will be a pop up message (after the product splash screen) to ask you to register for AspenTech product information.
Some user find this is not applicable for them as they are not connected to internet and thus cannot register for the product information. What is the | Solution: to bypass the pop up message during the next start up?Solution
1. Click Cancel when the pop message first appears.
2. Click Do Not Register on the second pop up message box.
This will prevent the pop up message during the next start up of the application.
However, for the AspenTech products users who have the internet access, it will be a tremendous experience to register in order to get the latest news and development of the AspenTech products.
Keywords: Splash
Aspen Process Explorer
Register
References: None |
Problem Statement: Is there a way for the Map TimeStamp field to point to another field other than the key timestamp field such as IP_Trend_Time?
For example in those cases where a custom record for Lab21 data is created, this custom record might have two time stamp fields IP_Trend_Time (data insert time) and L21_Trend_Time (time written by Lab21 operator);
Although the map of this custom record (IP_Lab21Map) points the time fields to L21_Trend_Time (Map_Timestamp), the trend still plot against the IP_Trend_time. | Solution: Unfortunately this is not possible, history retrieval is based on the key timestamp, not some other timestamp that might be in the history repeat area. This has always been the case for Aspen Infoplus21.
Aspen Infoplus21 history is ordered according to the key timestamp of the history events. Consequently, history retrieval looks at the key timetamps.
Based on the above the MAP record doesn't have any influence on the timestamp field being returned, because this is how the database API works.
Keywords: Custom record
Map
Timestamp field
References: None |
Problem Statement: This knowledge base article provides possible reasons why the error message,
The following alias was not resolved
can be displayed in the Aspen Process Explorer 'Description' field when a user attempts to drag and drop a tag alias from the Alias Browser onto an Aspen Process Explorer Batch plot. | Solution: This error message is usually an indication of a configuration problem. The cause is usually one of the following:
? In some cases the Alias cannot be resolved if there is not a tag assigned to the Alias. You should first configure the unit, then the tags for that specific unit and finally the alias to those tags.
? This error can also appear when a bad combination is picked for an Alias, For example, if you pick a characteristic which is not valid for a particular phase. Aspen Batch.21 will allow the user to select 'invalid' combinations like this. The only way to avoid selecting an invalid combination is to understand the process being handled by Aspen Batch.21.
? You may not have any values recorded in the Aspen Batch.21 database for these characteristics. In this case you would also get the above error because there wouldn't be a valid tag value to resolve an alias to.
? Aspen Batch.21 is case sensitive in some areas. If the unit name in the Aspen BCU Administrator is different (including case) than the unit name in the Aspen Batch21 Administrator this error message can be returned.
? The Aspen Batch.21 Administrator will still validate the tag definition name if the user accidentally types a blank space in the name. However, the Alias will subsequently return the wrong tag name, and subsequently generate this error message.
Keywords: config
APEx
single
overlay
References: None |
Problem Statement: This knowledge base article explains why the error message,
Error executing method 'Item': Dispatch error 0x80004005
can be returned from a custom program or Aspen SQLplus script which calls functions from the Aspen Batch.21 application programming interface (API). | Solution: This message is returned when the user's account which runs the custom program or script does not have the necessary permissions to access the Aspen Batch.21 areas. When a custom executable is run, it runs under the user's Windows login account. The user's Windows login account is also used to run an Aspen SQLplus query when it is executed within the Query Writer. However, Aspen SQLplus queries which are run as QueryDef, CompQueryDef or ProcedureDef records are run under the account which starts the Aspen InfoPlus.21 Task service.
? Verify that the Aspen Batch.21 client tools can view all areas when the client tools are run from the same account.
? Ensure the account used to run the custom program or Aspen SQLplus query has been granted enough permissions to use the Aspen Batch.21 API. Such guidelines can be found in knowledge base article 113216.
? Ensure that DCOM is configured according to knowledge base article 117207. Also, when examining the DCOM configuration ensure that the default impersonation level has not been set to anonymous. Using an anonymous default impersonation level will usually result in an account being used for authentication which does not have permission to access the Aspen Batch.21 areas.
The Aspen Batch.21 services and the Aspen InfoPlus.21 services should be started from domain accounts which have administrative privileges on the local server. The account which runs the custom program or Aspen SQLplus script should also be a domain account with sufficient privileges to access the Aspen Batch.21 areas.
Note: After changing the accounts which run the AspenTech services from local accounts to domain accounts, sometimes the servers need to be rebooted in order for the change to be fully recognized.
? If this error is generated from an Aspen SQLplus script when run through the Query Writer from a client machine, a good test is to log into the client machine using the domain account which starts the Aspen InfoPlus.21 service, then run the script from the Query Writer to verify whether or not the problem is related to the specific user's account.
? This error can be returned if security is set on the Aspen Batch.21 data source in the ADSA Client Config Tool. To check this:
- Open the ADSA Client Config Tool
- Click the Public Data Sources button, click the Advanced button.
- Ensure the option to 'Enable Security' is not checked. If this option is checked please uncheck it then restart the Aspen Data Source Directory service.
The following test query retrieves a complete list of Aspen Batch.21 areas and characteristics for each area. Sometimes this error message is coupled with a problem in which incomplete information is returned for the Aspen Batch.21 areas. This query can be used to verify whether or not all batch area information is returned.
Note: A reference to the Aspen Batch.21 Application Interface must be added in the Query Writer in order for this query to run.
-----
local data_sources, area, char_defs,ds_num int, area_num int, char_num int;
data_sources = createobject('AspenTech.Batch21.BatchDataSources');
for ds_num = 1 to data_sources.count do
write 'Data Source: '||data_sources(ds_num).name;
for area_num = 1 to data_sources(ds_num).areas.count do
area = data_sources(ds_num).areas(area_num);
write 'Area: '||area.name;
char_defs = area.batchdefinition.characteristicdefinitions;
for char_num = 1 to char_defs.count do
write ' Characteristic: '||char_defs.item(char_num);
end
end
end
-----
Keywords: privilege
rights
deny
denied
References: None |
Problem Statement: This knowledge base article describes how to programmatically change the time span of the global timeline in Aspen Process Explorer. | Solution: There is a sample VBForm file called TrendForm.apx which illustrates how to use the Aspen Process Explorer automation interface to control the timespan of a timeline. TrendForm.apx gets installed at this location:
Program Files\AspenTech\APEx\Samples\ProcessExplorer\VBForm
Open TrendForm.apx then examine the code behind the Time 6 to 8, Time 8 to 10 and RealTime buttons. The code behind the Time 6 to 8 button is pasted below.
'Set the time span to be from 6 to 8 in the morning
Private Sub Time6to8_Click()
Dim endTime, startTime
startTime = Date
startTime = DateAdd(h, 6, startTime)
endTime = DateAdd(h, 2, startTime)
TimeLine1.SetTimeRange startTime, endTime
End Sub
This code actually controls a private timeline which is named TimeLine1. However, when the private timeline is moved the global timeline will automatically make the same change if both timelines have the same global time server (the TimeServer attribute is set in the timeline's properties - see the screen capture below.) To give the appearance of controlling only the global timeline you would then need to hide the private timeline. To hide the private timeline (TimeLine1) do the following:
? Right click on the private timeline then select Properties (make sure to select the Propertes item at the top of the and not the Properties item at the bottom of the list.)
? When the TimeLine1 Properties box appears set the Visible attribute to False.
Keywords: Change
Modify
Time
Span
VBA
Code
References: None |
Problem Statement: Users may receive a message like the following when working in Excel or Process Explorer:
Microsoft Visual Basic (title of dialog box)
Compile error:
Can't find project or library | Solution: This message is an indicator that some underlying VBA code is referring to AspenTech Add-Ins that are not present and no longer needed. These references need to be removed from the VBA project.
If the message appears when opening a Microsoft Excel spreadsheet choose 'Developer' tab | 'Visual Basic' | 'Tools' | '
Keywords: None
References: s' and uncheck any references that report as 'Missing'.
If the message appears in Aspen Process Explorer choose 'Tools' tab | 'Visual Basic' | 'Tools' | 'References' and uncheck any references that report as 'Missing'.
Click 'OK' after making the changes and restart the application (Microsoft Excel or Aspen Process Explorer) and the error message should no longer appear. |
Problem Statement: This Knowledge Base article shows how to use Themes in Aspen Process Explorer V7.1. | Solution: Themes have been added to Process Explorer and its components in V7.1. A theme can be applied at run time to change the appearance of the application. Three themes are available:
Aspen - based on AspenTech's style guide for a common look and feel
Office - similar to Microsoft Office 2007
Windows - based on system colors
Themes can be applied from the View menu and from the Plot tab of the Tag Properties dialog box.
View Menu
Applying a theme from the View menu applies the theme globally to Process Explorer.
1. Click View | Application Theme.
2. Select the desired theme from the list.
Tag Properties
Applying a theme from the Plot tab of the Tag Properties dialog box applies the theme to Process Explorer globally and also to stand-alone trend plots outside of Process Explorer, such as those used by IP.21 Process Browser (formerly Web.21).
1. Right-click the Plot or Legend display.
2. Click Tag Properties.
3. From the Plot tab of the Tag Properties dialog box, select from the Theme list.
4. Click OK.
Keywords: None
References: None |
Problem Statement: When triggers do not execute the underlying cause is almost always data related. This knowledge base article describes how to enable logging such that the data and conditions processed by each trigger on a unit basis are logged to a file. This log file will assist in the determination of why a specific trigger does not execute as expected. | Solution: - In the Aspen BCU Administrator, go to Server | Scheduling Table
- When the Scheduling Table appears, right click on the unit in question then disable it. The unit logging cannot be changed while the unit is enabled
- Right click on the unit again then click Scheduling Properties
- In the Logging tab, make sure that the Trigger Condition Analysis option is selected
- Re-enable the unit and let the trigger process
The log file will show information about the trigger processing such as in the example below.
---
06/03/2007 10:14:31.231594 : Trigger mix_end_trig : analyze next data point:
Trigger condition analysis at time 06/03/2007 10:14:30.300000 :
term 1, condition 1 :
atcmixer1 == constant
0 == 0 : true
True term encountered -- skipping remaining logical terms.
Truth: true Data status: Good
Trigger analysis: timestamp / state / status
anchor: 05/03/2007 04:46:35.300000 / true / Good
current: 06/03/2007 10:14:30.300000 / true / Good
Trigger mix_start_trig : no more trigger condition data is available.
---
Keywords: fire
run
shoot
References: None |
Problem Statement: The scooter timestamps in Aspen Process Explorer can sometimes be difficult to read, depending on the font color used. This can be fixed by adjusting the font color for the timestamps. | Solution: The color for the scooter timestamp corresponds to the color selected for the first tag in the legend. If you change the color used for this tag, it will change the color of the timestamp font. It is possible to change the tag color by right mouse clicking the tag in the legend and selecting properties. On the Pen tab in the Properties window, you can select the Line color and change it from the default color.
Keywords:
References: None |
Problem Statement: When reading the 'State' and 'StatusSummary' properties of the BCU 'installed unit' object from SQLplus, a number is returned. What is the meaning of these numbers?
Sample SQLplus query (after enabling the SQLplus reference for the Aspen Batch 21 BCU Application Interface through the menu item View > | Solution: The possible codes and associated meanings are as follows:
State:
1 - Enabled
2 - Disabled
3 - Executing
4 - Stopping
5 - NotLoaded
6 - Loading
7 - LoadFailed
8 - Aborted
StatuseSummary:
1 - Reset
2 - InProgress
3 - Interrupted
4 - WaitingForData
5 - WaitingForGate
6 - CommunicationFailed
7 - Failed
8 - OK
9 - Current
10 - Complete
Note: not all these status codes may have been implemented.
Keywords: BCU Application Interface
State
StatusSummary
References: s...):
local objBCU_DS;
objBCU_DS = New(AtBatch21BcuApplicationInterface.BcuDataSources);
write objBCU_DS.Item(1).Areas.item(1).InstalledUnits(1).State;
write objBCU_DS.Item(1).Areas.item(1).InstalledUnits(1).StatusSummary; |
Problem Statement: The values for all tags in Aspen Process Explorer is displayed as the following error.
Aspen DA for IP.21 service is not configured | Solution: Two Aspen Data Source Architecture (ADSA) services are required to view InfoPlus.21 tags in Aspen Process Explorer.
Aspen DA for IP.21
Aspen Process Data (IP.21)
The error indicates that the Aspen DA for IP.21 service has not been configured for the data source in ADSA.
Data sources are configured using the ADSA Client Config Tool (Start | Programs | AspenTech | Common Utilities | ADSA Client Config Tool).
If the Use Public Data Sources option is not selected, the Aspen DA for IP.21 service for the data source can be added locally using the User Data Sources button.
If the Use Public Data Sources option is selected, the Aspen DA for IP.21 service should be added to the public data source on the Directory Server specified.
Keywords: DA
IP.21
data
source
not configured
References: None |
Problem Statement: How to display Phase start and End time on a batch plot in Process Explorer | Solution: The workaround to do this is to configure the Batch List Properties for the plot.
Right click on plot legend area à Click on Properties à Click on “Batch List� à Select the Sub batch Start time and End Time as the Start and End Characteristics respectively.
Click Ok to save the changes.
Keywords: Batch Plot
Phase
Subbatch
References: None |
Problem Statement: How do I change the precision of the seconds value of the timestamp displayed within the Show Data Table feature? Can it be adjusted from whole seconds to show tenths, hundredths, or thousandths of a second? | Solution: The precision of the Aspen Process Explorer timestamp displayed in the timeline and Show Data Table can be adjusted in the legend properties.
1. Right Click on the clock face in the timeline control and Select Properties.
2. On the Time tab increase the precision from 0 to 6 for the desired number of decimal places.
3. OK or apply this setting.
4. Close and open the trend plot.
Keywords: decimal
References: None |
Problem Statement: In a typical installation scenario a single Aspen Production Record Manager Server Service will connect to a single Relational Database, as defined in the ADSA Server it connects to.
Can one Aspen Production Record Manager Server talk to multiple relational databases?
Can multiple Aspen Production Record Manager Servers talk to the same relational database? | Solution: Multiple Aspen Production Record Manager (APRM) Server services can point back to the same Relational Database. By definition one APRM Server is a single machine as any given machine can only run one instance of the Server service.
For example: A customer currently has three separate servers hosting databases (DB) called AspenBatch. They want to consolidate these three separate DB instances onto the same SQL Server or Oracle RDB. Using Import/Export tools move and rename the DB?s from servers 2 and 3, to Server 1, so the final result is three uniquely named DB?s, like
AspenBatch
MyArea1
MyArea2
AspenBatch2
MyArea1
MyArea2
AspenBatch3
MyArea1
MyArea2
Area names are irrelevant, but the renaming of the actual DB instances is necessary since each DB needs a unique identity when all running on the same DB server. Renaming the DBs has no material impact since the only place the name of the DB itself is referenced is in the ADSA connection information. Any code written against those separate DBs will use Datasource and area names, all of which can be maintained during the consolidation.
However it is interesting to then consider whether or not you still need three different APRM Server services. If each DB instance has many areas and is quite busy, then three separate PCs should still be maintained ? they would each just need an edit to their existing connection string information to point back to their specific Batch DB on the new consolidated RDB server (AspenBatch, AspenBatch2, AspenBatch3.)
However it is in fact possible to configure your ADSA so that one APRM Server Service runs several separate DBs (regardless of where they are running, separate boxes or consolidated on one SQL Server):
Here is how it works: Every APRM Server service points to an ADSA Server. Every Defined Data Source in that ADSA points back to a APRM Server node (using Server host name field.) The Server Connection String points to the unique DBs:
ADSA Server (Aspen Public Data Sources)
Defined Data Source: AspenBatch
Configured Services:
Aspen Batch.21 Service
Server host name: MyBatch.21Server
Server Connection String: AspenBatch
Defined Data Source: AspenBatch2
Configured Services:
Aspen Batch.21 Service
Server host name: MyBatch.21Server
Server Connection String: AspenBatch2
Defined Data Source: AspenBatch3
Configured Services:
Aspen Batch.21 Service
Server host name: MyBatch.21Server
Server Connection String: AspenBatch3
Notice in the above example that the Server host name is the same, so this means you are pointing to your one and only APRM Server. That one server instance will run all the DBs, regardless of where they are running (all in one SQL Server, or on several different nodes).
Keywords: architecture
topology
load balance
capacity
design
References: None |
Problem Statement: A right-click, Properties operation on the Server Administration node in the Aspen Production Record Manager (APRM) Administrator Tool reveals a Cache dialog:
What is this Datasource-related caching used for? | Solution: There are three usage scenarios where choosing a default Datasource and hitting Apply can help your users:
Scenario
Description
Usage Scenario 1
I have a large configuration.
No Datasource selected in the Administrator cache dialog.
I restart the batch server.
It starts but does not load up any cache until the first request from a client.
The first user will experience a delay while the APRM Server loads up the cache to return configuration data to the client.
The second and following users will experience better performance (since the configuration data is now loaded in memory.)
Usage Scenario 2
I have a large configuration.
A Datasource is selected in the Administrator cache dialog.
I restart the batch server.
It has a Datasource to load up, so it loads up the cache on Service startup.
The first user will no longer experience a delay.
Usage Scenario 3
I have several datasources my users have access to.
80% of the clients connect to A and only rarely use B.
I choose Datasource A in the Administrator cache dialog.
The Server loads the cache for A on Batch Service startup.
The first user of A no longer experiences a delay.
Keep in mind that if another automated process is waiting on the Service to startup, in order to read or write batch data, then whatever Datasource that program is trying to communicate with will be cached as soon as the Service receives the request. In that case the first user of a datasource after system startup is likely not experiencing a delay, as long as that program was trying to communicate with the same Datasource.
Keywords:
References: None |
Problem Statement: While configuring a BCU unit, the designer wants a trigger that knows when, for example, Step 433 ends, in order to record the End_Time characteristic.
Typically you could use a Transition trigger type with the same conditions as the startStep trigger, and just NOT the Trigger condition. That approach works fine for Transition trigger types, but putting a NOT on a State trigger will end up firing the trigger for every data point the trigger is not true for, so this doesn't work. | Solution: Here is the BCU trigger logic needed to get the transition out of Step 433 (Notepad shows the entire Summary line):
Explanation of trigger:
We want the change of STEP (markdiscrete) when it no longer is 433 but it was a second ago. And of course where the batches no longer are the same.
Keywords: logic
timespan
BCU Administrator
unit
References: None |
Problem Statement: This knowledge base article describes the various options available for viewing alarm states for records in Aspen InfoPlus.21. | Solution: Alarms for IP_AnalogDef records in Aspen InfoPlus.21 are keyed off of the field IP_Alarm_State field. The alarm limits are configured in the individual IP_AnalogDef records through the following fields:
IP_HIGH_HIGH_LIMIT
IP_HIGH_LIMIT
IP_LOW_LIMIT
IP_LOW_LOW_LIMIT
The following options can be used to view the alarm state of an IP_AnalogDef record.
? In the Aspen Process Explorer Graphics Editor, you can add a data field to the graphic then set the data field to show the alarm field of a record (for example, in an IP_AnalogDef record display the attribute IP_Alarm_State) then display the text for this alarm condition at run-time in a graphic. In addition, you can use animation to control the color of the data value depending on the current value of the data. An example of such a graphic is shown below. The first image shows the value in an acceptable range, the second image shows the data value is red to indicate an abnormal alarm state.
? As part of the standard product, Aspen Web.21 has an alarm summary page, an unacknowledged alarm summary page as well as an alarm log page.
These alarm summary pages display the tag name, description, current value and alarm status as shown below.
? The Tag Watch and Point List pages in Aspen Web.21 also show the alarm state field. By default, tags in alarm do not appear in a different color but it may be possible to add conditional scripting to the page to achieve this goal.
The Tag Watch and Point List pages will display the tag name, description, current value, units, alarm status and the data source as shown below.
Keywords: status
ack
unack
operator
References: None |
Problem Statement: After an installation or upgrade of an Aspen Production Record Manager server, when viewing a web page that includes Batch Query Criteria, the tab controls are missing: | Solution: The tab controls are part of a package of web controls from Microsoft. When this problem occurs, it is because the controls were not properly installed during the installation/upgrade. To resolve the issue:
1. Go to Start=> Settings=>ControlPanel and 'remove' Microsoft Internet Explorer WebControls
2. Go to the aspenONE20065DVD2\core\IEWebControls folder, and run the IEWebControls.msi package
3. Do an IISRESET
NOTE: The same path noted in step 2 is valid for any supported version of the Manufacturing Suite.
Keywords: Batch.21
fail
render
corrupt
References: None |
Problem Statement: When you configure the datasource in the BCU administrator or if you try and start the BCU unit scheduler in the Aspen Production Record Manager administrator tool may get the error 'B21BCU-55031: Unable to access the specified BCU data source: XXXX'? | Solution: This error will occur when the User logged in does not have access to the Registry and ADSA but are trying to configure the BCU datasource and APRM administrator BCU unit scheduling.
To resolve this issue the user logged in will need to ensure they have administrator rights and edit the registry keys in both the 32bit and 64bit location.
Key Locations in Regedit.
[HKEY_LOCAL_MACHINE\SOFTWARE\AspenTech\ADSA\Locator]
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\AspenTech\ADSA\Locator]
Look for the key
DirectoryHost=CHANGE_TO_ADSA_SERVER
If you dont have the dwords in the Location key then add the keys below.
You can copy the dword from the 32 bit location if they are not present in the 64b for example.
DirectoryHost=CHANGE_TO_ADSA_SERVER
DisableLookup=dword:00000000
Protocol=dword:00000000
Timeout=dword:00000bb8
Once you add the Datasource then save the registry and open the APRM Administrator and ensure that the datasourse and unit scheduling has been started. Start BCU administrator and configure datasource and area.
Keywords: Adsa
BCU
APRM
Aspen Production Record Manager
B21BCU-55031
Unable to access the specified BCU data source
References: None |
Problem Statement: This knowledge base article provides an example which shows how to execute code when the global time line changes. | Solution: The TimeLine object has an event called TimeChangedEvent which you can use to detect when the time line updates. The following code snippet shows how to use the TimeChangedEvent with the global time line.
'----- ADD TO A VBA FORM IN ASPEN PROCESS EXPLORER -----
Public WithEvents g_globalTimeLine As AtTime.TimeLine
Private Sub g_globalTimeLine_TimeChangedEvent()
' Prove that it works by displaying a message when the time changes
MsgBox Time Changed
' Any user specific code goes here
End Sub
Private Sub UserForm_Initialize()
Set g_globalTimeLine = Application.GlobalTimeLine
End Sub
'
Keywords: None
References: None |
Problem Statement: After an upgrade from V7.1 to V7.2, the Production Record Manager Query Tool still shows V7.1 in the titlebar, even though Help, About shows V7.2, and the application is in fact V7.2. | Solution: If this happens, look for the file BatchQueryTool_en.dll in
C:\Program Files\AspenTech\Batch.21\Locale\
and delete it. After deleting it, the correct V7.2 title should appear.
Keywords: Batch Query Tool
upgrade failure
wrong version
References: None |
Problem Statement: This article demostrates how to add an ad-hoc tag to a Process Explorer plot using the VBA automation interface. | Solution: Note: This example references the example file 'TrendForm.apx' which is installed in the following directory:
Program Files\AspenTech\APEx\Samples\ProcessExplorer\VBForm
Procedure:
Open TrendForm.apx. Click on the 'Design Mode' button in the toolbar to make the project editable.
Add a new button to the VB form. In this example, the button is called CommandButton2
Double click on the new command button, then add the following code:
Private Sub CommandButton2_Click()
'Add an ad-hoc tag
Set g_customTag = MyTrendPlot.TrendTags.Add(, , =atcai*2/atcl101) g_customTagHandle = g_customTag.Handle
End Sub
Notice that the method MyTrendPlot.TrendTags.Add takes 3 arguments. These arguments are (in order):
The name of the IP.21 database as listed in the ADSA data source list
The name of the map record.
The name of the tag.
In this case, the tag is an ad-hoc tag. Therefore, instead of a tag name, a calculation of
=atcai*2/atcl101
is specified instead. In this calculation atcai and atcl101 are names of tags in the Infoplus.21 demo database.
Save the code changes. Click on the 'View Process Explorer' button (leftmost button in toolbar) to get back to the VB plot.
Click the 'Exit Design Mode' button in the toolbar. This will take the VB form out of edit mode.
Click on the new button to add the ad-hoc tag. Notice that the tag name in the Process Explorer pen area shows the calculation specified in the VB code. Process Explorer will plot the calculated result.
Keywords:
References: None |
Problem Statement: Is it possible to execute a calculation for a batch that has already run? | Solution: In batch detail display, right click on a characteristic where the value is determined using a calculation and select Modify. Increase the timestamp value by one second, and the calculation will re-execute for the characteristic.
You can verify that the calculation executed by checking in the Aspen Production Record Manager Administrator. In the left hand pane of the Administrator, expand the Data Source name, Server Administration, Eventing. Right click on Eventing and select Recent Actions. If the calculation executed, it will appear in the queue.
Keywords: characteristic
batch
calculation
APRM
References: None |
Problem Statement: How does the Aspen Production Record Manager (APRM) StatisticValue object derive its average value? For a given Average statistic returned via the StatisticValue object, is the Average determined by equally spaced values over the time period, or simply the sum of AllGoodPointsInMyTimespan / NumberOfGoodPointsInMyTimespan? | Solution: There are two ways to compute statistics: Value or Integral. The Value is where you add up all the values and divide by the number of samples. The Integral computes the area under the curve using every actual data point.
In APRM, the computation uses an integral computation (the area under the curve). It takes every actual data point (not evenly spaced) to compute the area under the curve.
Other notes:
1. Bad points are not used to compute the statistic.
Keywords: Batch.21
Batch21
Query Tool
References: None |
Problem Statement: Sometimes when opening the BCU administrator you will receive an error B21BSC-500002 Relational Database Error -2147467259 [Aspentech][SQLPlus] InfoPlus.21 record batch21_configuration does not exist. How can this error be resolved? | Solution: One might receive this error upon opening BCU Administrator when the Aspen Production Record Manager service component in ADSA is set up to use a ODBC Data Source instead of OLEDB driver. In order to change this component to use OLEDB driver
1. Go to ADSA Client config tool and select the data source where you have added Aspen Production Record Manager service. Click on Edit and select Aspen Production Record Manager service component.
2. After clicking on set up select the Microsoft OLEDB Provider for SQL Server or Oracle depending on the Relational database you are using
3. After selecting the driver click Next and make sure you are pointing to the correct database in the connection tab and the connection is successful.
4. Upon changing to OLEDB the server connection string should look like the following in the APRM Service component in ADSA.
5. Click OK.
6. After this try opening BCU administrator to verify the error does not persists.
Keywords: Batch21
BCU Administrator
SQL Server
References: None |
Problem Statement: When trying to plot a tag in Aspen Process Explorer, the time zone (TZ) field is giving the error:
Invalid Bias Response: <!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Strict//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd>
This error may occur on certain servers and from certain client machines and is caused by the fact that some Web components are no installed on that server. | Solution: To fix this error message, open the ADSA Client Config Tool and select the data source name from either Public Data Sources (if you are running from the server) or User Data Sources (if you are configured from the client). Select the Aspen Timezone Information Service and edit the Protocol to DCOM instead of Web Service. Apply these changes and exit the ADSA Client Config Tool. Once Aspen Process Explorer is re-opened, the error message will no longer appear in the TZ field for the tag.
Keywords: Timezone
Aspen Process Explorer
Invalid Bias Response
References: None |
Problem Statement: How do I link END TIME characteristic to another trigger or action in a journal file? | Solution: There is a file called TRIGACT.DEF, located in the
..\Program Files\AspenTech\Batch.21\Data\BatchConnect\Data
directory, which contains the mappings from triggers and actions to a specific characteristic in the Aspen Production Record Manager database. If you want to point the END TIME characteristic to another trigger or action, you will need to look into TRIGACT.DEF file and change the mapping accordingly.
Keywords: None
References: None |
Problem Statement: While running the Aspen Database Wizard to upgrade a much older db version (for example Version 6) the Upgrade fails with this error message: | Solution: Because of unique data usage patterns in a particular Batch database, it may be necessary to edit and run the DDL files individually to update the database, when a Wizard failure occurs. In V7.2 and after the DDL files for all products the Wizard updates are made available under:
C:\Program Files (x86)\Common Files\AspenTech Shared\DatabaseWizard\Configuration
for just this purpose.
However before going that direction, it may simply be a case of the database properties in SQL Server -- by default Transaction Log growth is limited, and this can provoke a Wizard failure. So as a first attempt at resolving this problem:
1. Reimport the source DB again (not strictly required, but it is recommended to start with the original source DB, rather than a partially upgraded one.)
2. In SQL Server Management Studio, right-click on the DB, choose Properties, and then in the Properties dialog, choose Files.
3. Click the extended choices button for any property (database size or log) that shows restricted growth, and make sure it is set to Unrestricted
Try the upgrade again. If there is still a failure, contact Aspen Support for further assistance, making sure to include a copy of the DatabaseWizard log file (found along the above path in the DatabaseWizard directory.)
Keywords: ALTER TABLE [AspenBatch].dbo.char_batch_data_history ADD CONSTRAINT
Number = -2147217900
Source = Microsoft OLE DB Provider for SQL Server
Description = Could not create constraint. See previous errors.
SQLState = 42000
NativeError = 1750
References: None |
Problem Statement: Ad-hoc calculations are typically used in Process Explorer. But they could also provide a useful way to generate meaningful process data information in a batch context. Is that possible? | Solution: Ad-hoc calculations cannot be used directly in the Query Tool, but they can be specified together with statistics, as this example shows:
Keywords:
References: None |
Problem Statement: It is not possible to copy-and-paste an entire Batch within a Batch area. | Solution: To duplicate a batch in a batch area (i.e. copy-and-paste) first create an XML file of the Batch by exporting it from the Batch Detail Display, then submit it to Batch.21 using the Web Service Test utility. Here are the detailed steps:
1. Find the Batch you want to export using the Batch Detail Display. Choose File, Export and create the XML output file.
2. Copy-and-paste all the information contained within the <Batch> </Batch> tags of your output file into a structure like the following, (making sure to use the correct references for MyBatchServer and MyBatchArea):
<Datasource xmlns='Aspentech.Batch21' name='MyBatchServer'>
<Area name='MyBatchArea' xmlns='Aspentech.Batch21'>
<InsertBatchData xmlns='Aspentech.Batch21'>
<BatchList xmlns='Aspentech.Batch21'>
<Batch>
...
</Batch>
</BatchList>
</InsertBatchData>
</Area>
</Datasource>
3. Pay special attention to the Handle tag in your output file.
- If you leave the Handle untouched, the data will be added (i.e. duplicated) into the existing batch you exported from. Any Handle specified must already exist.
- If you supply a Designator, the batch information will search for a batch matching those values and add the data to it.
- If you do not supply either Handle or Designator values a new batch is created and the data added to that batch.
4. Copy and paste the content of your new XML into the Batch.2WebServiceTestApplication.exe utility, found here:
C:\Inetpub\wwwroot\AspenTech\Batch.21\bin
WARNING: There is no Undo feature in Batch.21, so when submitting XML it is highly recommended to use a test environment first.
Keywords: duplicate
repetitions
Batch Area
APRM
Aspen Production Record Manager
References: None |
Problem Statement: In the Batch Time Range plot, the Planned Start Time and Planned End Time characteristics provide a graphical way to compare planned versus actual run times at the Batch level. As long as characteristics named Planned Start Time and Planned End Time are recorded at the batch level, this comparison is available. This display shows the actual Start and End times of Batch 928, and a gray overlay of the Planned Start and End. (Hovering the mouse over the actual or planned bars will display a Tooltip showing the values of the corresponding Start / End Time characteristics for each.)
Tooltip for Actual:
Tooltip for Planned:
However even if the Planned Start Time and Planned End Time characteristics have been recorded at the Batch level, they do not automatically display when viewing the batch in the Time Range plot:
How can they be added to the display? | Solution: Right-click on the plot area and choose Planned Batch View:
For any batch that has Planned Start Time and Planned End Time characteristic instances recorded, an overlay of the planned time-range for the batch will be displayed.
Note that this Planned Start/End overlay is only available at the top level of the batch.
Keywords:
References: None |
Problem Statement: When using the Excel Process Data Add-In to retrieve values for the Max/Min aggregate, the associated timestamp returned is not the timestamp of the actual Max/Min value. Rather, the timestamp provided is the anchor timestamp of the aggregate period.
For example, if the aggregate period is one hour (11:00 - 12:00 for instance) and the Maximum value for the tag occurred at 11:14, the Max aggregate function would return an associated timestamp of 11:00 if the Aggregation Anchor option is set to Begin. If the Anchor option is set to End, the timestamp returned would be 12:00.
The Max/Min VALUE is correctly returned, but the timestamp associated to the value is derived from the Aggregation Anchor option - so it doesn't return the timestamp of the actual Max/Min value. Many users would also like to know the actual timestamp of the associated Max/Min value. | Solution: In order to determine the timestamp associated to the actual Max/Min value, use SQLplus. For example, this script will return one 24-hour max aggregate value and the value's actual timestamp, for each day included in the script's span.
-- Get_Max_ValueAndTime(Tag Name , StartTime , EndTime , Period)
function Get_Max_ValueAndTime(n1, StartTime timestamp, EndTime timestamp, P1 integer)
local temp1 timestamp;
temp1 = StartTime;
for (select ts_end, max from aggregates where name = n1 and ts between StartTime and EndTime and period = P1 and request = 0) do
select ts, value from History where name=n1 and ROUND(value, 3) >= ROUND(max,3) and ts between temp1 AND ts_end AND request = 4;
temp1 = ts_end;
end;
end;
Get_Max_ValueAndTime ('tagname', '07-jul-06 00:00:00', '15-jul-06 00:00:00', 24:00);
You will need to edit the tagname and timestamps in the last line to suit your needs. Also, if the Min aggregate value is desired, the appropriate changes would be required.
Keywords:
References: None |
Problem Statement: By default, the batch structure is shown in the Administrator and Characteristic Browser tools in the order in which the elements were created. As long as the creation order represents something meaningful that is fine. But if the structure is later edited, all new elements automatically appear at the end of their respective levels. Also, in a structure with many elements, it may be more useful to simply put elements at each level in alphabetic order, or some other order that has meaning in the environment. | Solution: V7.2 introduces the ability to sort batch structure elements within the Administrator tool (CQ00041203, listed in the Aspen Production Record Manager V7.2 Release Notes Fixed Defects section.) That sort order is then reflected in the Characteristic browser. For example, if a new AGITATE phase was added to the AspenChem demo, by default it would appear like this:
However by using the new Subbatch Order property in the Administrator, it could be moved into either alphabetic order (first) or time order (before the MIX phase):
The view from the Characteristic Browser the next time it is opened:
Note that there is no automatic alphabetic sorting. Whatever sort order is preferred must be configured by the system administrator /Solution developer.
Keywords: numeric
time-based
random
shell
priority
alphabet
alphabetical
References: None |
Problem Statement: Starting from V7.2 Batch Configuration Utility (BCU) Administrator has been enhanced to dynamically create sub-batch names and characteristics. | Solution: New features in the V7.2 version of the Aspen Production Record Manager (APRM) BCU Administrator support automatic configuration of characteristics and sub-batches. Prior to V7.2, sub-batches and characteristics had to be pre-defined using the APRM Administrator tool before they could be referenced in the BCU.
The configuration drop-down menus in the BCU now include a selection for 'Auto configure', requiring the user to only specify the data type (i.e. Numeric, Character, Time, Long, or Event). The name can be a configured name or name that does not exist. When verifying or installing the unit, the auto-configured characteristic or sub-batch will not be validated. When triggered, the batch server will create the characteristic or sub-batch if the name does not exist.
Keywords: V7.2 Overview
BCU
Auto Configure
Characteristics
Sub-batches
APRM
References: None |
Problem Statement: Plot Start Time and End Time of Batch Overlay plot do not match start/end time of plot.
Scenario:
A user would like to be able to change the Overlay plot Legend Start Time and End Time columns to show the Run, Start Time and Run, End Time instead of the Batch Start Time and Batch End Time. They have successfully changed the Start and End Time characteristics on the Properties\Batch List page so that the plot only shows data for a part of the batch (subbatch). However, the timestamps that are actually shown in the plot Legend are the overall batch Start and End Times.
Can this be changed? | Solution: Batch Start Time and Batch End Time columns in the batch plot Legend will not change to match the plot Start and End Time.
Batch Start/End Times in the plot Legend reflect the start and end time of the batch (batch level characteristics).
Plot Start/End Times reflect the setting from the Batch List Property page based on characteristic specifications.
Each time a batch is selected it will snap the timeline to the Plot Start/End values.
Otherwise you can change the timeline to whatever you want.
These values will not change.
This is as designed.
Keywords: None
References: None |
Problem Statement: You have two (or more) Aspen InfoPlus.21 (IP.21) servers feeding data into the same Aspen Production Record Manager (APRM) database. And APRM services on both servers are using the same local user account (let's call it amsadmin).
However, in this scenario the stored procedure BATCH21_SP_INSERT_USER will not be able to distinguish between the two local accounts when updating the dbo.USERS table and will throw the following duplicate key error:
Execute stored procedure BATCH21_SP_INSERT_USER: -2147217873
Relational Database Error -2147217873: Violation of PRIMARY KEY constraint 'PK__users__00551192'. Cannot insert duplicate key in object 'dbo.USERS'.: E_FAIL | Solution: To resolve the error, first open the dbo.users table and manually create an entry for each non-unique user account that is running APRM Server service on your IP.21/APRM servers and is configured to write batch data to the APRM database having the issue. To make it unique, the user_domain column should contain the name of the IP.21/APRM server each local user account resides on, as follows:
amsadmin        server1
amsadmin        server2
Now, before exiting the dbo.users table, note the number in the user_id column.
Next, open the id_counters table and look for the user_id row. Update the number in the id column to the same number you noted in the user_id column in the dbo.users table.
Keywords: None
References: None |
Problem Statement: Error:
Relational Database Error -2147217900: ORA-01654: unable to extend index
seen in the Batch21Services log file. | Solution: This is not an Aspentech error -- refer this issue to the Oracle Administrator. The tablespace for the table noted in the log file error must be increased. The error occurs because Aspen Production Record Manager is unable to write to that database table.
Keywords: Aspen Production Record Manager
unable to extend index
Relational Database Error -2147217900
References: None |
Problem Statement: This Knowledge Base article provides a list of special characters that are not supported within subbatch and characteristic names. | Solution: The following characters are not supported within subbatch and characteristic names: open ([) and closed (]) brackets and commas (?,?). Additionally, all non-printable (hidden) characters are not supported.
Testing results indicate that Batch.21 does support the following characters:
_~!@#$%^&*()_+=-`
_./?;':><{}\|
abcdefghijklmnopqrstuvwxyz
ABCDEFGHIJKLMNOPQRSTUVWXYZ_Caps
Keywords: None
References: None |
Problem Statement: Aspen Production Record Manager only works on the server, and all users are getting locked out with no access to read information from the database. The error message shown is Unable to get pointer to Batch Areas for Data Source Access is denied. (0x80070005). Aspen Framework Security or Aspen Local Security may or may not be implemented in this situation. | Solution: This indicates a DCOM security issue with the APRM server. To fix this issue, open DCOMCNFG.EXE and navigate to Console Root | Component Services | Computer | My Computer. Right-click on My Computer and select Properties. Select COM Security from the tab that opens and make sure that Edit Limits and Edit Default under both Access Permissions and Launch and Activation Permissions include full access for all users listed. Add the users Everyone and Authenticated Users and give those groups full access if they are not already listed and given full access. Also be sure the check that DCOM is enabled on your company's network.
Keywords: Access is denied
(0x80070005)
References: None |
Problem Statement: Users often want to compare Batch data from one plant with similar data from another plant. Is it possible to view Batch plots (Single, Batch, Multiple) from more than one ADSA data source in the same Aspen Process Explorer plot window? | Solution: Yes, it is as long as you use tag aliases (it won't work with tag names) and the same tag alias represents the same process variable on both systems.
If you have several ADSA data sources configured on your ADSA server with the Aspen Batch.21 Service component configured, you would open the Batch Query Tool and from Tools/Options point to one of the ADSA data sources selecting the desired Batch Area at the same time. Perform a search and drag the batches of interest into the Process Explorer Batch plot window.
Go back to the Batch Query Tool and change Tools/Options to point to another ADSA data source and Batch Area. Run a query and select the desired batches and drag them into the same Batch plot window as before.
All the batches should show up in the same plot. You can use the Single batch plot, the Batch Overlay plot or the Multiple batch plot. For the Multiple batch plot it might be desirable to keep all the Batches from a particular area grouped together in the Batch Legend. If this is done, then a certain portion of the Multiple batch plot will be batches from one plant while another area of that plot will have batches from another plant. This will make it easier to compare the summary statistics or characteristics being viewed for one plant against another.
If the Batch Designator contains a reference to the Plant Name, then it will be easy to identify which plant which batches are from. If this is not the case, you might want to add the Plant name as a characteristic in the Batch data base. Before you run the query in the Batch Query Tool, add the Plant Name characteristic as an additional fields using the Fields dialog. Then the Plant characteristic will return to the plot along with the default Batch Designator, Start Time and End Time characteristics and will be visible in the Single batch plot and the Multiple batch plot when using a Scooter.
Keywords: Multiple data sources, Batch.21, Batch plots, multiple plants, multiple sites
References: None |
Problem Statement: When attempting to create a new Aspen Production Record Manager (APRM) Basic Report, the characteristics component is not loading properly and you receive the message:
Batch characteristics loading... | Solution: This is an Internet Explorer version issue and can be fixed by updating IE 9 or IE 10 with the latest patches available from Windows Update.
.
To test the issue, try loading the APRM website with another browser such as Firefox or Chrome and the characteristic component will load properly.
Keywords: Characteristics Browser
web based reports
References: None |
Problem Statement: Unable to see or connect to batch areas. | Solution: To see DCOM errors, we had to add key CallFailureLoggingLevel with value of 1. This Microsoft article has information about the flag and general DCOM troubleshooting.
http://technet.microsoft.com/en-us/library/cc738214.aspx
Setting this flag revealed error XXXX in System log of Event Viewer.
1. Click Start, click Run, type regedit, and then click OK.
2. Locate the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole registry subkey.
3. Right-click the Ole value, point to New, and then click DWORD Value.
4.Type CallFailureLoggingLevel, and then press ENTER. Double-click CallFailureLoggingLevel, type 1 in the Value data box, and then click OK.
5. Restart the DCOM program, and then examine the System log and the Application log for DCOM errors.
Keywords: Batch areas
Batch21
Aspen Production Record Manager
DCOM
References: None |
Problem Statement: As Microsoft releases new Office versions, the location of their library directories changes. Will AspenTech follow Microsoft's lead in making sure that AtData.xla is installed into the correct library? The issue here is that end users make extensive use of the Excel Add-in (AtData.xla). In the past, with new releases of Aspen Process Explorer and MS Office, the locations of these libraries change with no warning which causes headaches for users.
Background:
With each release of Microsoft Office, the library location seems to change. AspenTech's standard location of %ProgramFiles%\AspenTech\APEx\Pe\Addin does not exist anymore with the install of version 6 software. Rather, the file is located in %ProgramFiles%\Common Files\AspenTech Shared. In other words, both Microsoft and AspenTech have continued to change the directory structure for the Add-in. | Solution: AspenTech's overall goal is to maintain consistency where the libraries are located in all releases of AspenTech software. Consistency with Microsoft's library location must also be established to provide seamless Excel functionality with the end users. AspenTech now utilizes a Microsoft function call at install time to determine where the office library is located.
For v2004 and later, .xla files are only installed into one directory.
If Excel is installed on the machine, then .xla files are copied to the directory returned by this .vbs snippet:
Set oXl = CreateObject(Excel.Application)
XlLibPath = oXl.LibraryPath
If nothing is returned, the files are copied to:
%ProgramFiles%\Common Files\AspenTech Shared
This results in always installing into the correct location (varies by locale and version of Office) or into one single default location.
Keywords: None
References: None |
Problem Statement: Aspen-Tag (non visible) component (AT_tag.ocx) is not available from v5 onwards | Solution: At_tag.ocx is no longer supported and has been removed from distribution from v5.0 onwards. If using a VBA Form with v5.0 and above then any references to At_tag.ocx must be replaced with references to Aspen Process Data Automation. To add Aspen Process Data Automation to the VBA Project Click Tools
Keywords: At_tag.ocx
non visible component
References: s and select Aspen Process Data Automation from the Available References. If it does not appear in the list browse to it in the following location.
..\Program files\AspenTech\APEx\Pe\Addin\AtProcessDataAuto.dll |
Problem Statement: When making XML requests to the Production Record Manager Server, the Configuration information is automatically returned with the query, even though it may not be needed. Configuration information is not the data for a particular batch, but items like the Batch Definition itself (Designators characteristics, Unit Definitions.) Depending on the particular implementation, the amount of Area configuration information can be significant. And unless you are specifically looking for that configuration data in your XML reply it can be thought of as overhead. Is there a way to eliminate that config information to make XML queries more efficient? | Solution: Whether or not the Area configuration information is sent with the XML reply depends on a comment in the XSL file, called includeAreaConfiguration. Even though in XML terms the format of includeAreaConfiguration makes it look like a comment, it is in fact processed by the server, and it's value of 0 or 1 determines whether or not Area Configuration information is included with the XML reply. To illustrate this, let's look at the BatchDetail.xsl file that is processed when a user requests a Batch Detail Report from a Production Record Manager client tool. The first few lines of the XSL file look like this (note the includeAreaConfiguration tag, with its default value of 0):
So what happens if that includeAreaConfiguration comment is changed to 1? The report results look exactly the same, because the format is structured to only display batch information for the batch in question. However compare the activity captured in the Batch21Services.AtlServer log file.
Server activity with includeAreaConfiguration set to 0:
Server activity with includeAreaConfiguration set to 1:
The important point to note is that if you are sending XML requests to the server without applying any XSL transformation to it that includes <!-- includeAreaConfiguration=0 -->, then all your Area Configuration information is being returned with each reply.
Keywords: XML answer slow
definition
References: None |
Problem Statement: Developers should protect their Process Explorer VBA projects from unauthorized modification by other users. This article describes how the current features of Process Explorer and AFW/ALS security can be combined to protect a Process Explorer VBA project. | Solution: When editing a project in Process Explorer, the Tools | VBAProject Properties | Protection tab allows you to password protect your project's source code and properties from viewing by anyone who doesn't have the correct password. However, if you only lock you project this way, users with the VBA permission in ALS/AFW will be able to put your project into design mode, move the objects around on the form, and save the form with the repositioned objects. These users will not be able to view any source code without the correct VBA project password.
If you don't wish for the other users to be able to put your Process Explorer VBA project into design mode, then you need to deny the 'VBA' privilege to these users in ALS/AFW security. This will cause the design mode buttons to be unaccessible (grayed out) for these users.
Keywords:
References: None |
Problem Statement: This Knowledge Base article provides steps to resolve the following error:
B21BAI-60104: Unknown Exception...
which may be encountered when trying to save an Aspen Batch.21 Report. | Solution: Open the Aspen Batch.21 Administrator
Right click on the Reporting object for the Area in question and select Properties from the context menu (see screen grab below)
Make sure that the paths for the three folders (Template, Query, and Output) are configured correctly (not pointing to the wrong drive such as F:\ instead of E:\). You can validate the paths by copying them and pasting them into the Windows Explorer Address Bar.
Keywords: B21BAI-60104 Unknown Exception
References: None |
Problem Statement: Using Visual Basic for Aapplications (VBA) in Aspen Process Explorer, how do you open a Process Explorer graphic file from a command button? | Solution: Use this method: Application.Documents.Open (C:\samples\Boiler_Room_A103.atgraphic)
Keywords: None
References: None |
Problem Statement: Two numeric characteristics are defined, e.g. NUM and SUM, and SUM should be the sum of all instances of NUM. How does the auto calculation have to look to have SUM calculated whenever a new instance of NUM is added or when one instance of NUM is modified. Can it be done in Calcscript? | Solution: A good approach is to trigger on any instance of NUM being recorded and then sum all of the instances that exist in the formula. An alternative would be to use the ReturnValue below and map it to the output characteristic SUM as well.
Keywords: None
References: None |
Problem Statement: How do I install a missing AspenTech service? | Solution: AspenTech recommends completing a re-install or repair installation if services are not installed as expected. If these options are not available then the service can be installed using the SC command providing the service executable file was installed. This will require the user to have read/write access to the registry.
Example:
If the Aspen Production Record Manager BCU service did not install during the initial installation. It can be installed using the SC command.
sc <server> [command] [service name] <option1> <option2>...
Example sc command to install the Aspen Production Record Manager BCU service:
sc create Batch21BCUService displayname= Aspen Production Record Manager BCU Service binpath= C:\Program Files (x86)\AspenTech\Batch.21\Server\BCUServer.exe
Note: In many cases the service name and display name are different and must be specified using the displayname option.
Keywords:
References: None |
Problem Statement: This Knowledge Base article answers the following question: What does the message BCU started with Allocation Granularity ( ..... ) really mean? | Solution: The above-mentioned error message can sometimes be seen in the BcuServer.log. This message is strictly informational in nature and it may be safely ignored. It is present only when logging is enabled and it has to do with application trying to control the size of the BCU threads. The allocation granularity indicates how big each thread will be when it is created.
Below is an excerpt from a Microsoft site defining this concept:
================================================
AllocationGranularity
Specifies the granularity with which virtual memory is allocated. This value was hard coded as 64K in the past; since the Windows environment expands to different hardware platforms, other values may be necessary.
================================================
Keywords: None
References: None |
Problem Statement: If you install an AspenTech product that installs Microsoft Visual Basic for Applications (VBA) on a computer that has an earlier version of VBA, you may experience one of the following problems:
? When you try to run a macro, you may receive an error message similar to the following:
'Object library invalid or contains references to object definitions that could not be found'
or a pop up message similar to the ones shown below.
Or
When this problem occurs, the macro does not run.
? When you try to add one of the updated controls to an Office Visual Basic for Applications form, you may receive an error message similar to the following:
'Element not found'
or the pop up message shown below.
When this problem occurs, the control is not added to the form.
? After configuring the Aspen Process Data Add-in the following errors appear either when you open Excel or if you try to select an icon:
When this problem occurs, the control is not added to the form. | Solution: To resolve the problem, delete cached versions of the control type libraries. To do this, search your computer's hard disk for all files with the extension '.exd', and then delete all occurrences. The .exd files are re-created automatically by using the new controls the next time you use VBA.
NOTE: When searching for the '.exd' files, make sure the 'Search hidden files and folders' option is checked in the 'More advanced options' of Windows Explorer Search tool.
For more information follow the link below:
http://support.microsoft.com/kb/957924
Keywords: Compile Error in Hidden Module: B21Main
Compile Error in Hidden Module: Main
Add-in
Excel Addin
Cumulative update rollup for VB6 SP6
Could not run the macro
Ribbon_OnLoad
Ribbon_GetLabel
exd
References: None |
Problem Statement: This Knowledge Base article shows how to show the detail display for a specific batch handle from Visual Basic. | Solution: Below is a sample VB code that shows how to activate the detail display from Visual Basic. The batch handle in this example is Batch21 v7.1.1405.
There are three steps:
1. Create the object
2. Set the batch handle: SetBatch
3. Show the detail display: Show
NOTE: NOTHING is a check to make sure we created the batch detail display object.
Public batchDetailDisplay As Object
Private Sub Command1_Click()
If (batchDetailDisplay Is Nothing) Then
Set batchDetailDisplay = CreateObject(BatchDetailDisplay.Application)
End If
If (batchDetailDisplay Is Nothing) Then
Exit Sub
End If
batchDetailDisplay.SetBatch Batch21 v7.1.1405
batchDetailDisplay.Show
End Sub
Keywords: None
References: None |
Problem Statement: What does a locked batch signify in Aspen Production Record Manager? Is there still some way to edit the batch? | Solution: Once a given batch is locked, no changes can be made by anyone. Characteristics cannot be added, deleted or modified no matter what permissions the user has in the system. The only action that can be taken is that someone with the Lock privilege can unlock the batch. Of course in a compliant system (i.e. one where Aspen Audit & Compliance tracks all auditable activity) both locking and unlocking the batch create audit trail entries.
Keywords: read-only
permanent
permission
References: None |
Problem Statement: Why am I getting the Error B21BCN-54037 when opening a Journal file?
This means the specified event journal file is partially completed and is no longer in the journal_directory, or is
inaccessible. | Solution: To resolve this issue determine why the <filename> file is missing and
restore it. A missing file may be due to:
• Manual deletion of the file.
• The file may reside on a remote server that is currently
inaccessible.
• Access to a file is no longer available due to a change in directory permissions.
Keywords: Batch.21
APRM
Aspen Production Record Manager
OpenBatch
EVT
Mem
B21BCN-54037
References: None |
Problem Statement: A Trend plot added to an Aspen Production Record Manager web-based advanced report does not display the trend line when the report is generated. Also the Batch21Services log will include the following message “Failed to add tag data request to data manager: E_IINVALIDARG”.
If the Aspen InfoPlus.21 Task Service and the Aspen Production Record Manager Services are started with different accounts the method call to read tag data from IP21 may fail because the user information is not passed from the Web to Aspen Production Record Manager to Aspen InfoPlus.21. | Solution: Add the following entry into the registry [below] to force the direct connect method to read tag data from Aspen InfoPlus.21.
· Export the registry as a backup.
· Go to [HKEY_CLASSES_ROOT\CLSID\{710B32A1-7277-11D1-932C-00805F0F1C84}
· Add a key “ProcessList” if it does not already exist
· Add a String Value under the key ProcessList called “ProcessName# [where # is “1” if it’s the first Process name or the next consecutive number if 1 or more already exists]
· Populate the value of “ProcessName#” with Batch21Services.exe
NOTE:
Be very careful when modifying the registry. There may already be values in the process list.
The algorithm is to put ProcessName# where # starts at 1 and increases by one. The code looks for ProcessName1, then ProcessName2, etc.
EXAMPLE, adding ProcessName2
Keywords:
References: None |
Problem Statement: Can I test my APRM connection and run test SQL queries? | Solution: Starting from v8.8, Aspentech has implemented a new ODBC test utility that can be found in 32 bit and 64 bit format:
C:\Program Files\AspenTech\Batch.21\Client\APRM_ODBC_TestApp.exe -- 64 bit client
C:\Program Files (x86)\AspenTech\Batch.21\Client\APRM_ODBC_TestApp.exe -- 32 bit client
Once you select the desired connection method (ADSA, ODBC DSN or Connection String) click on Open Connection to start testing.
Here's a screen capture of the results:
Keywords: APRM_ODBC_TestApp.exe
Test APRM Connection
References: None |
Problem Statement: Why does the BCU service go to 100% after restarting machine? After restarting the BCU server the 'Aspen Production Record Manager BCU service' goes to 100% in the Windows Task Manager. This can cause performance issues with the APRM and BCU servers and clients. | Solution: This issue is caused when there are units in the BCU server administrator that are disabled. These units may have pointed to another data source that either does not exist or is not reachable. This causes connection errors and the BCU will try and re connect. The re connection time varies on scheduled time in the Unit. This will create multiple reconnection errors in the BCU server log located in c:\ProgramData\AspenTech\DiagnosticLogs\ProductionRecordManager\
To resolve this issue you will need to remove the reference to the old server in the BCU unit/trigger or completely remove the unit/trigger. If you delete units then ensure that you restart the APRM and BCU services to refresh the cache.
Keywords: BCU
CPU
100%
References: None |
Problem Statement: Currently, the Aspen Production Record Manager (APRM) and BCU default log file location on aspenONE servers is:
C:\ProgramData\AspenTech\DiagnosticLogs\ProductionRecordManager
But this location is not accessible to a majority of APRM (non-privileged) users.
Can this file location be changed? | Solution: The log file location is hardcoded in the application itself and it cannot be changed.
Keywords: None
References: None |
Problem Statement: Is it possible for a process graphic to change color based upon the value of a tag attribute? Is it possible to animate an object representing a text tag? | Solution: It is possible to animate a live data object so that it changes color depending upon the value of a tag attribute. For text labels, the text string can be changed based on a tag value.
For images, an image can be changed on a tag value. Animated objects always have an associated tag and they can change appearance based on the tag data they receive from the database.
The following objects can be animated:
Bar Graphs
Data Fields
Ellipses
Images
Lines
Polygons
Rectangles
Symbol Groups
Text
Animating Objects
1) Determine the tag and the attribute that you would like to use as a data source for the animation.
2) Determine the values in the attribute that indicate different ranges that you would like to identify.
For example, if the values 0 through 10 indicate a low value, the values 11 through 20 indicate a normal value, and 21 through 30 indicate a high value, you need to configure three ranges.
3) Right-click on the object, and then click Properties.
4) Click the Data Source tab.
5) In the Tag Name box, type the name of the tag that you want to use as a source. You can search for tags with the Tag Browser by clicking the Tag Browser button in the Toolbox.
Refer to the Aspen Tag Browser Help file for more information about using the Tag Browser.
6) In the Attribute box, type the name of the tag attribute that you want to use as an animation source. The value attribute is the default.
7) In the Data Source box, select a data source.
Note: You can drag a tag from the Tag Browser onto the Data Source page to apply a tag name and data source.
8) In the Map box, select the map you want to use to obtain the value. Usually there is a single map and it is used as the default. For more information about maps, see the InfoPlus.21 Database User's Manual.
9) Click the Animation tab.
10) Select the Animation On check box.
11) Click Add Range once for each range of values that you want to configure. Click Delete Range to delete a range.
12) Under Range, click on a triangle.
13) In the Min box, type the minimum value for the range.
14) In the Max box, type the maximum value for the range.
When the value for the tag is greater than or equal to the Min and less than or equal to the Max of a range, the color that you specify for that range is the color of the object. The min and max values are inclusive?if ranges overlap, the first range specified will determine the display characteristics.
15) Click the Color button, and then select a color from the drop-down color palette to change the color of the object.
16) If you are animating a text string, you will see an additional Text entry field in the dialog. Type the text that you want to appear in each range in the Text field.
17) If you are animating an image, in the File box, type the relative pathname to the image that you want to appear for the selected range. Click Search to search for the image.
18) Click Apply. Under Range, select the next triangle.
19) Repeat steps 11 through 14 for each range that you want to configure.
20) Click OK.
When viewing the graphic in the Process Graphics Editor or in Process Explorer, the animated object's color will change according to the value of the specified tag.
Animating Text Values
It is not possible to directly animate text values. To animate an object representing a text tag, a work around must be employed. The text must be represented as an integer. Two options are available to represent the animate text values.
1. Set up a parallel IP_DiscreteDef tag and write an SQLplus script to convert the text into an integer using a selector record, which will link each text message received from the DCS to an integer number.
2. If the text values read from the DCS have a corresponding integer value on the DCS then, it is possible to set up a parallel IP_DiscreteDef tag, read the integer values from the DCS and use that tag as the value source in your graphic.
Keywords: color
animate
change
text
numeric
References: None |
Problem Statement: Requesting data from the Aspen Batch (Aspen Production Record Manager) Data Excel Add-In gives an
Error: unable to acquire license : SLM_RN_PME_BTCHDEXCLADD | Solution: The new Aspen Batch Data Excel Add-In introduced with the 7.3.0.2 Supplemental Release patch released in March, 2012 requires the license key:
RN_PME_BTCHDEXCLADD
The error noted above is returned if this license key is not found in your license file. If you have an NCM token license agreement you may submit a license key request from the website http://support.aspentech.com to request an updated license file. Customers who do not have an NCM token license will need to purchase this license key.
Keywords: Add-Ins, License, 7.3.0.2
References: None |
Problem Statement: Client PCs which use v6.0.1 or earlier versions of the Aspen Process Data Add-In are not able to use the ATGetCurrVal() function on sheets which were created with v2004 of the Aspen Process Data Excel Add-In. This is because the number of arguments has changed for the ATGetCurrVal() function in v2004.
Version 6.0.1 and earlier shows the following arguments:
ATGetCurrVal(Sheet1!$B$5, Datasource, , 16, 0, 0)
While v2004 shows the following arguments:
ATGetCurrVal(Sheet1!$B$5, Datasource, , 16, 0, 0, ) | Solution: TheSolution is to double click the cell which contains a reference to ATGetCurrVal(). When the dialog box pops up, click OK to execute the data retrieval once. After the function is executed on a PC which uses an earlier version of the Process Data add-in, the correct number of arguments will automatically be placed in the call to ATGetCurrVal ().
This behavior has been fixed in the v2004.1 release, so no formula modifications are needed.
Keywords: Upgrade
addins
add-ins
References: None |
Problem Statement: How does the license timeout and grace period impact the functionality of the Aspen Batch x64 ODBC Driver? | Solution: The Aspen Batch ODBC Driver allows third party applications to retrieve a batch of records from Aspen products through a ODBC connection.
The Aspen Batch x64 ODBC Driver will check out a license when it prepares a statement. If the ODBC driver is unable to contact the SLM Server while the license is checked out, it will enter a license timeout period for 15 hours.
If the connection to the SLM Server is not re-established within the license timeout period of 15 hours, the ODBC driver will then enter either a 10 day grace period (for client) or a 30 day grace period (for server).
During the license timeout and grace periods, the client will remain fully functional with no limitations. Once the ODBC Driver on the server enters the grace period, the server will continue to function with the limitation that no new configurations can be made.
Keywords: Batch ODBC Driver, Sentinel License Manager, license timeout, grace period
References: None |
Problem Statement: After upgrading a pre-v8.4 Aspen Production Record Manager (APRM) system you cannot find any of the Server Tools because the menu option would appear to have not been installed. | Solution: In v8.4 the management of the APRM services is handled within the Aspen Production Record Manager (Batch) Administrator. You will find them under the Local Services node in the console tree.
The APRM Administrator Help file has a new section Using the Local Services Node introducing the function of this new node.
It has been noted that there may be some references in the documentation to the location of the now obsolete external APRM Server Tools. These references will be corrected in due course.
Keywords: Missing
Not found
Not installed
BcuServerManager.exe
AtXServiceOptions.exe
References: None |
Problem Statement: No AM/PM parameter is shown in the timeline when the time setting is in 12 hour format. There should always be either an AM or PM suffix. | Solution: This problem is not specific to Process Explorer, but is instead a system setting. This setting is under Control Panel -> Regional and Language Options -> Customize... (button on the Regional Options tab) -> Time tab. Normally, most people use one of the four options in the pull down menu for Time format. But this field may also be edited, and deleting the tt for AM/PM will removed this suffix. Therefore, be sure to select either the standard h:mm:ss tt or hh:mm:ss tt (for a leading zero) format.
Keywords: am
pm
timezone
ante meridiem
post meridiem
References: None |
Problem Statement: The following warning message is received when opening a spreadsheet with AspenTech Process Data Add-Ins loaded:
This application is about to initialize ActiveX controls that might be unsafe. If you trust the source of this file, select OK and the controls will be initialized using your current workspace settings. | Solution: The problem is cause by the MSGrid.ocx control. This is a standard Visual Control which is not shipped with Windows 2000 but gets installed with Aspen Process Explorer. With some versions of Excel, the MSGrid.ocx cannot be loaded by the Add-In because it is not marked as Safe for Initializing and Safe for Scripting. A workaround for this problem is to update the registry, creating a .reg file with the following information and run it:
REGEDIT4
[HKEY_CLASSES_ROOT\CLSID\{A8C3B720-0B5A-101B-B22E-00AA0037B2FC}\Implemented Categories]
[HKEY_CLASSES_ROOT\CLSID\{A8C3B720-0B5A-101B-B22E-00AA0037B2FC}\Implemented Categories\{7DD95801-9882-11CF-9FA9-00AA006C42C4}] @=Safe For Scripting
[HKEY_CLASSES_ROOT\CLSID\{A8C3B720-0B5A-101B-B22E-00AA0037B2FC}\Implemented Categories\{7DD95802-9882-11CF-9FA9-00AA006C42C4}] @=Safe For Initializing
Keywords: Process Data Add-in
ActiveX
References: None |
Problem Statement: When I use the Aspen Production Record Manager Administrator and then close the application, I see the following pop-up window:
Why is this happening and how can I solve it? | Solution: The message Save console settings to console name? appears each time you close a console opened in Author mode.
To avoid the pop-up window set the default mode for the console to one of the user modes and then clear the Do not save changes to this console check box:
1. Go to C:\Program Files\AspenTech\Batch.21\Client
2. Right click the Administrator.msc file and select Author
3. Go to File | Options | Console tab
4. From the Console mode drop down list, select User mode - full access.
5. Uncheck the Do not save changes to this console check box.
6. Click Apply, OK, then close it (it will show the message again when you close it).
After this, open the Aspen Productio nRecord Manager Administrator normally, either double-clicking the icon or through the Start menu. If you make any changes and then close the application, the changes will be automatically saved. Any changes to the console will be saved by default.
As you will see, if you go to File | Options at this point, you will not see the Console tab. In order to see it, you have to right click on the icon, then select Author to open it in author mode.
Keywords: PRM Administrator
Microsoft Management Console
References: None |
Problem Statement: Error on BatchData XML Import
The following error message appears in Result file:
Database Error: Relational Database Error -2147217887: Invalid character value for cast | Solution: The problem may be that you are not including timestamps for your values. Timestamps should be specified when importing XML into V7.1.x. Here is an example format:
2010-01-14T14:43:00
In V7.2 timestamps are allowed to be missing (default to NOW.)
Keywords: Batch
Data
XML
Relational
Database
Invalid
Character
References: None |
Problem Statement: My users don't need Aspen Process Explorer, and only want to have the Aspen Process Data Add-In ( Excel Add-In) available. | Solution: text and added screen capture and updated versions
Applicable Version(s)
Multiple
Keywords: Add-in
Excel
References: None |
Problem Statement: How to create a subbatch Duration Calculation. | Solution: Creating a subbatch duration calculation requires the use of arrays. You need to create a phase duration within each individual phase and then create a rollup calculation to add up the array of individual phase durations.
To create a subbatch duration calculation:
1. In Aspen Production Record Manager Administrator, expand the tree view in the navigation pane:
- Under Batch Definition | Characteristic Definition node, create a duration characteristic.
- Under Phase Definition | Phase | Characteristic Definitions node, create a duration characteristic.
The Phase refers to the phase for which you want to create a duration calculation.
2. Create two calculations, one for the Duration and the other for the Total Reaction Duration.
3. Specify the calculation properties in the Calculation Property dialog box.
- For the calculation properties of Duration, specify the Calculation tab as follows:
Trigger Characteristic:
REACT[Any], END TIME[Any]
Calculation script:
Return Value = endTime - startTime
Variables
Name
Mode
Binding Type
Binding
endTime
Input
Characteristic
REACT[Trigger], END TIME[Trigger]
ReturnValue
ReturnValue
Characteristic
REACT[Trigger], Duration[Trigger]
startTime
Input
Characteristic
REACT[Trigger], START TIME[Trigger]
For the calculation properties of Total Reaction Duration, specify the calculation tab as follows:
Trigger Characteristic:
REACT[Any], Duration[Any]
Calculation script:
For index = 1 to durationArray.count
Return Value = returnValue + durationArray[Index]
Next i
Variables
Name
Mode
Binding Type
Binding
ReturnValue
ReturnValue
Characteristic
Total Reaction Duration
durationArray
Input
Characteristic
REACT[All], Duration[All]
index
Output
None
Note: Ensure to use ALL, ANY and TRIGGER instances specifically where needed.
Keywords: Subbatch
Duration
Aspen Production Record Manager
Characteristic
Batch
References: None |
Problem Statement: When looking at a Q (SPC) Chart, such as an XBAR chart, with V6 or later, several new features were added. One of them was the ability to Right-Click in the plot area and select Subgroup Details. From the screen that appears, provided you are plotting a Q-Record rather than an Ad-Hoc record, you can enter either or Free or Fixed Comments relating to the Specific Subgroup being Analyzed. Once you have entered comments, you should see a Magenta coloured Diamond around the plotted subgroup. Whether you scroll in Time, or get out of Process Explorer and Back-in, you should always see that Diamond around that plotted subgroup. You should then be able to point to that subgoup in the Plot area, Right-Click and choose Subgroup Details. You will see the comments you had initially entered or chosen.
AspenTech support has had some reports that the Comments did not persist and the Magenta Diamnond disappeared. | Solution: The problem is caused by not having the latest changes to 'several' records in the IP.21 database. For example, look in the record XBARRCMAP (Defined by AtMapDef). Look in the Repeat Area MAP_#Maps
For this new V6 feature to work:
Occurrence 19 should have 'Map_Attribute' value of 'Fixed Comment' and 'Map_FieldName' value of 'Q_Fixed_Comment'
If you are having the problem described above, AND find that your records do not have these latest changes, you will need to run the InfoPlus.21 Upgrade Wizard in Custom mode. Create a new Database, ensuring NEWCIMQ21.RLD is loaded and then Upgrade your current snapshot into it. If you need help or further explanation about this, please contact the AspenTech Support Helpline for AMS products.
Keywords:
References: None |
Problem Statement: How does Aspen Process Explorer verify Aspen Framework (AFW) security? | Solution: Aspen Process Explorer (PE) is a securable application, using the Aspen Local Security (ALS) or Aspen Framework (AFW) security servers. Roles created on the security server can contain both individual domain accounts, and domain groups. The AFW roles can then be applied to the Process Explorer application and granted the following permissions: File New, File Save and VBA.
When first launching the Process Explorer client, the user will see the splash screen appear. For a brief period the splash screen status bar will display Verifying Security. At this point, several actions occur to validate the users permissions. In the default version 6.x installation those actions are as follows:
1. The Process Explorer executable calls the pfwauth.dll on the local system, which determines the user account currently logged onto the machine. (The pfwauth.dll is the process which contains all of security access checking routines. This method of launching the security routines is refered to as In Process, since the pfwauth.dll is running within the PE process, as opposed to running within a separate service.)
2. The pfwauth.dll will verify if the PE.xml file has been added to the list of secured applications on the Aspen security server. If it hasn't, no further security validation occurs.
3. If the PE.xml file has been included, the pfwauth.dll will execute several security routines to determine the PE permissions assigned to the various AFW roles.
4. In order to compare the user logging into PE with the list of roles available in AFW, the pfwauth process will connect to the nearest domain controller (typically running Active Directory) in order to find any domain groups the user belongs to. This connection to the domain controller will be authenticated as the user logged into the PE machine, who is also the user requesting access to PE. Since a user should always have permission to lookup their own account and group membership in Active Directory, it is unlikely to have a problem performing this step.
(In Active Directory, the ability to validate the user account and verify group membership requires read permission to the User objects, such as Orangizational Units, in Active Directory. For more general information about Active Directory, please seeSolution 113224.)
5. Once the user account has been verified on the domain controller, the pfwauth.dll (running within the Process Explorer process) then grants application access according to the assigned permissions.
NOTE: If the UseServerADSI registry key (accessible through AFW Tools) is set to 1 on this machine, the pfwauth.dll will still contact the Aspen Local Security server for AFW role information, but it will delegate the action of looking up group membership from the domain controller/Active Directory server to the Local Security server. (All clients prior to AMS version 5 delegated the group lookup to the Local Security server.) Therefore, the account running the Aspen Local Security server will be the account requiring permission to read user objects in the Active Directory server. As of AMS version 5, the default value of the UseServerADSI key is set to 0, therefore Process Explorer will directly contact the domain controller/Active Directory server. For more information, please seeSolution 110390.
IMPORTANT NOTE: The above steps define the process from which Process Explorer verifies application specific permissions, such as the ability of a certain user to access the VBA components. Once a user's permissions to the application have been verified, and the user attempts to view data from IP.21, the process of ensuring appropriate access to IP21 data is handled on the IP.21 server. (Process Explorer simply requests data for the user account logged in, and IP.21 runs its own security routines to determine if access can be granted.) For more information on the process IP21 uses to verify AFW security, please seeSolution 113221.
For more information on using AMS products in conjunction with Active Directory, seeSolution 113224. For information on how the various AMS clients verify security, please see the following knowledgebase articles:
113221 - How does IP.21 verify AFW security?
113222 - How does SQLPlus verify AFW security?
113223 - How does Web.21 verify AFW security?
113233 - What account is running the Aspen Local Security Server?
Keywords: connection failure is fatal
access denied
init cache com
invalid tag
References: None |
Problem Statement: How can you execute an SQLplus query from within a graphic running in Aspen Process Explorer? | Solution: 1. In the Aspen Process Graphics Editor, create a data field.
2. In the Properties for this data field, on the General tab, click on the box for Allow Data Entry.
3. On the Data Source tab, in the Tag Name field, enter the name of the query to be executed. For the Attribute field, scroll to and choose the field Execute. The Map field should populate with the correct ATMapDef record. Choose the appropriate Data Source.
4. Click OK to close the dialog box. The current value of the Execute field, NO, should be displayed.
5. Save and close the graphic.
6. Open the graphic in Aspen Process Explorer. By default the current value of the field in the query record, NO, will be displayed. Click on the field and type the integer value of 1 into the Value field of the dialog box. This will execute the query. The integer value of 1 is the YES equivalent.
7. To verify that the query was actually executed, find the query record in the Aspen InfoPlus.21 Administrator. Look at the field, Last_Executed. The timestamp for this field should be the time that you typed YES into the data field.
Keywords: execute
graphic
query
References: None |
Problem Statement: When viewing data in Process Explore on one PC and viewing the same data in the Administrator on the IP.21 server PC, the timestamps are off by 1+ hours. | Solution: First check that the system time on the IP.21 server machine is the same as the client machine with Process Explorer, both are set to the same timezone, and both use the automatic daylight savings switch in the control panel (Start -> Settings -> Control Panel -> Date/Time -> Timezone). If these are all the same, check for a TZ environment variable (Start -> Settings -> Control Panel -> System -> Environment). This environment variable is normally not needed and should be deleted. Also, check for time-synchronization programs that could change system properties that otherwise appear normal in the control panel.
Keywords: TZ, tz
timezone
time zone
timestamp
References: None |
Problem Statement: The Aspen Tag Browser is a key component of Aspen Process Explorer and from v2004 onwards it can also be launched from the Aspen InfoPlus.21 Administrator.
Clicking on Search in the Header area brings a dropdown menu that includes Simple Search and Advanced Search.
The Simple Search allows search for tags based on a text search of the Description and/or Name of the tag.
The Advanced Search allows a user to build a much more complicated set of search criteria.
What does it mean if the Simple Search works but the Advanced Search is grayed out ? | Solution: There are two possible reasons
1) The Aspen Data Source Architecture (ADSA) configuration for a Data Source includes added components. If the Aspen SQLplus service component has not been added to the Data Source, then the Advanced Search won't be available when connecting to that Data Source.
2) Although the TagBrowser uses Aspen SQLplus to do its searches, the Aspen SQLplus product doesn't need to be installed on a client computer if only doing Simple Searches.
However, if doing Advanced Searches, the Aspen SQLplus client must be installed on the client computer.
Keywords:
References: None |
Problem Statement: How to increase the default size of the log file created by Aspen Production Record Manager? | Solution: By default the log file generated by Aspen Production Record Manager Services is 1MB in size.
To increase the default size of the log file created by Aspen Production Record Manager open the Production Record Manager.Profile.xml file located in the
C:\ProgramData\AspenTech\Production Record Manager
folder and search for a section on logging. Change the log size parameter there, save the file and restart the Aspen Production Record Manager Services service and/or the Aspen Production Record Manager BCU Service service.
Example
<Logging><ApplicationInterface Size=1 Interface= SQL= Steps= Audit= Security= SPC= Publish= Profile= KPI= XML= Calc=
To double the size of the log file, change the Size=1 to Size=2 (which means 2MB). If this is not enough, you can increase the size further to triple or quadruple the size of the APRM Server log file.
NOTE: Please make sure you have enough disk space before increasing the size of the log file beyond the above-suggested values.
Keywords: None
References: None |
Problem Statement: The BCU Log file contains errors like:
B21SVR-50159 error Value for characteristic already exists
A typical cause for this error is multiple triggers firing simultaneously trying to create or populate characteristics. | Solution: If only one unit is involved, try synchronizing the triggers so they are forced to execute one after the other. In the case of multiple units, change the area properties (in the BCU Server Manager) so that less units can process simultaneously (the default number of simultaneously processing units is 3.)
Keywords: B21BSC-50159: Value for characteristic already exists
B21SVR-50159: La valeur pour la caracteristique existe deja.
References: None |
Problem Statement: When you open the BCU administrator and go to Scheduling Table you will notice that the Units are in a Failed state.
When you check the Diagnostic logs files for APRM you will see the error B21BSC-50002: Relational Database Error -2147217900: The transaction log for database 'PPAPRMDatabase' is full. | Solution: This issue is caused by the Database being full or the database does not have permission
You can change the size of the database or Contact your Sql Server Administrator.
1.. Open SQL Server Enterprise Manager, and expand to the APRM Database.
2. Choose Properties on the APRM Database.
3. From the Properties dialog, click on Files, on the left.
4. Note the properties for APRM_log1, and its Autogrowth parameters - it is likely restricted.
5. Click the . . . icon. Likely under Maximum File Size you need to choose the radio button Unrestricted File Growth.
Keywords: B21BSC-50002: Relational Database Error -2147217900
B21BSC-50002
BCU
BCU Load Failed
APRM
References: None |
Problem Statement: When a user attempts to add new characteristics to a basic query in the Aspen Batch.21 reporting web page the characteristics never appear when trying to add them to the query. The Aspen Batch.21 reporting page then hangs. This knowledge base article explains why this problem occurs as well as how to resolve it. | Solution: This is caused by using a version of Internet Explorer (IE) that is older than the version required by the Aspen Batch.21 installation manual. For versions 2004 and 2006 Internet Explorer version 6 SP1 is required.
Keywords: IE6
v2004
v2006
freeze
hang
missing
empty
References: None |
Problem Statement: This | Solution: provides an overview of Batch.21 SPC functionalitySolution
Introduction
SPC plots for Batch.21 were introduced with v2004. The SPC plots available include: XBar, Range, CUSUM and EWMA.
There are two types of Batch SPC plots:
Batch.21 Ad-hoc SPC plots that can be created on the fly and can be used to analyze historical as well as current values. Ad-hoc Batch.21 SPC pens in Process Explorer can be converted to Batch Online SPC plots using a wizard. Batch.21 Online SPC variables can also be created and configured from within the Batch.21 Administrator.
Batch.21 Online SPC plots involve the creation of Q_BatchXBARDef data records in InfoPlus.21 and corresponding variables in the Batch.21 Administrator and Batch.21 database.
A Batch.21 SPC plot is basically a multiple batch plot with statistical control limits and SPC alarm rules applied. The user can chart subgroups that are tied to batch characteristics or subgroups that are batch-related summary statistics such as average, sum, minimum, maximum, range, standard deviation and variance. For Batch.21 SPC charts the subgroup size is always set to one, one characteristic per batch plotted over several batches, or one summary statistic per batch plotted over several batches. Statistics can be calculated on any defined sub-batch level. For instance, the user might plot subgroups tied to the average reactor temperature for the Heat Step of the Mix Stage.
Batch.21 Ad-hoc SPC Plots
To create a new Batch.21 Ad-hoc SPC plot go to File/New/Batch/Batch Ad Hoc SPC from the main Process Explorer menu.
Add a Pen to the Legend and several batches to the batch list. You can use the Batch Query Tool or the Find Batch dialog in Process Explorer. The Find Batch dialog has been enhanced in v2004. The default plot that comes up is the XBar chart.
The Upper and Lower SPC control limits are calculated from the values in the plot using the standard SQC formulas. The limit calculations are performed using the same algorithms used for Q SPC charts. In this example, each subgroup value in the plot is the average reactor temperature for the entire batch. There are 8 subgroup values plotted because 8 batches were added to the Batch List. The Process Explorer Timeline Control has no real meaning in this sort of plot. Additional batches can be dragged into the Batch List at any time and they do not need to be sequential in time. The chart displays the XBarBar value (average of all the plotted subgroups) as well as the standard deviation of the population and the range. The standard deviation is used to calculate the upper and lower control limits. Subgroup size is always one for Batch.21 SPC charts.
Sub-batch statistics could be specified from the Batch List tab of the plot Properties window.
Right-clicking in the plot and selecting Change Characteristic allows the user to specify a Batch.21 Characteristic rather than a statistic.
Keywords:
References: None |
Problem Statement: After installing Aspen Process Explorer, the application reports the following error when started:
AttypeInfoCache::GetTypeInfoOfGuid
Invalid Type Library: 8002801d | Solution: The problem is that the ATTime.dll file was not registered properly during the installation.
From a DOS prompt, change to the directory C:\Program Files\Common Files\AspenTech Shared\APEX
From this directory, run the following command:
regsvr32 Attime.dll
.
Keywords: Attime
gettypeInfoOfguid
Invalid type Library
References: None |
Problem Statement: Older versions of Aspen Process Explorer displayed real numbers with full precision, thus showing many decimal places whether the user wanted to see the full precision or not. This knowledge base article describes why Aspen Process Explorer shows data as formatted by each respective Aspen InfoPlus.21 record after an upgrade to Aspen Process Explorer version 6.0.1. | Solution: The ability of Aspen Process Explorer to display values as they are formatted in Aspen InfoPlus.21 is a feature which was put into version 6.0.1. Since Aspen InfoPlus.21 actually stores the full single or double precision real value in history it has always been possible to adjust the IP_VALUE_FORMAT of each individual record so that different numbers of decimal places are displayed for different tags within the Aspen InfoPlus.21 Administrator. As of version 6.0.1 this flexibility was extended to the data displays in Aspen Process Explorer.
An SQLplus query can be used to change the IP_VALUE_FORMAT of many records at once. An example of such a query follows:
Update IP_AnalogDef
Set IP_VALUE_FORMAT = 'F22.11';
This query changes the IP_VALUE_FORMAT for all records defined by IP_AnalogDef.
Keywords: Point
Decimal
Place
Places
Single
References: None |
Problem Statement: This knowledge base article illustrates how to specify the Map record from which to retrieve data using the Process Data Add-In for Excel. | Solution: Open an Excel spreadsheet. Type the Tag name in one cell, Server name in the next, and name of Map record in the following cell. It must be in this order either across or down.
Select Aspen > Process Data > Get Data > Trend/Aggregate Data Select the groups of cells you just specified as your Input area for Tags box
Choose the Settings button. On the Output tab, verify that Tag Name, Server, Map & Value boxes are checked. On the Data Source tab, verify that the Tag information is displayed in the direction you want them to be read & the Server is configured correctly. Click Set as Default, then OK.
Keywords: excel add-in
process explorer
map record
References: None |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.