question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
|---|---|
Problem Statement: Is it possible to enter in only partial information for DQM? | Solution: In the more recent versions of Aspen Fleet Optimizer, we have added the option on entering in only certain information via Manual Information Collection to account for the fact that not all information may be known when the customer is reporting their data. The Yes / No Flag allows the customer to specify if they have updated the sales and/or inventory information for a given product / tank.
Keywords: Partial Information
References: None |
Problem Statement: Customer tried to use the Aspen PI Data Source to read character data, but instead of displaying the text value, the graphic is displaying ??? | Solution: The Aspen Data Source Architecture for PI supports only data types of Digital, Integer or Real. Not character strings.
Documentation will be updated to reflect this.
Keywords: PI data source character
References: None |
Problem Statement: Can you provide more technical background on tubesheet design using UHX? | Solution: The attached paper was produced by the Sub Group of Heat Transfer Equipment of the ASME. Gabriel Aurioles (AspenTech) is the Secretary.
This White Paper is intended to describe the basis of requirements contained in Mandatory Section UHX of Section VIII Division 1 of the Boiler and Pressure Vessel Code. The discussion provides the highlights for the derivation of the analytical methodology and a discussion of the differences of between the ASME requirements and those of TEMA and other international Codes. Likewise, a general discussion is provided regarding the significance of the calculated stresses and how the rules are intended to be applied.
Keywords: None
References: None |
Problem Statement: Which Aspen Data Source Architecture service components are needed by which Production Management and Execution products? | Solution: Product
ADSA Service Component
Aspen InfoPlus.21
-Aspen DA for IP.21
-Aspen Process Data (IP.21)
Aspen Audit & Compliance Manager
-Aspen Audit and Compliance Database
Aspen Calc
-Aspen Process Data (Calc) is OPTIONAL and only required for stored on-demand calculations.
Please Note: Because there can be only one 'Aspen Process Data' service per ADSA data, create a separate ADSA data source specifically for the 'Aspen Process Data (Calc)' service.
Aspen Event.21
Optional, depending on the database being used with the client product:
-Aspen Event.21 Data (.Net Events) ? Does not require an IP.21 data source.
-Aspen Event Data (Simulator)
-Aspen Event Data (IP.21) ? Does require an IP.21 data source.
Aspen IP.21 Process Browser
For an InfoPlus.21 data source:
-Aspen Process Subscription (Generic) ?
recommended for IP.21 connectivity
-Aspen SQLplus service component
-Aspen Process Subscription (GCS) ?
recommended ONLY if specific GCS functionality is not available in the Generic service.
-Aspen DA for IP.21
For an Oracle, MS SQL Server, or MS Access
database:
-Aspen Process Data (RDBMS) for an Oracle, MS SQL Server database, and MS Access (limited to Trend Plot functionality only)
For an OPC data source:
-Aspen Process Data (OPC)
For a PI data source:
-Aspen Process Data (PI) for PI (limited to Trend Plot functionality only)
For a PHD data source:
-Aspen Process Data (PHD) for PHD (limited to Trend Plot functionality only)
Aspen Process Explorer
Required:
-Aspen SQLplus service component
(needed by Tag Browser)
Any one of the Aspen Process Data services
specific to the source of the data.
For an IP.21 data source:
-Aspen Process Data (IP.21)
-Aspen DA for IP.21
For an OPC data source:
-Aspen OPC-DA
For an RDBMS (Oracle, MS SQL Server, or MS Access):
-Aspen Process Data for RDBMS
Note: See the ?Aspen Process Data for RDBMS? section of the Aspen Process Explorer Installation Guide for instructions on setting up the tags table in RDBMS.
For a PI data source:
-Aspen Process Data (PI) for PI (limited to Trend Plot functionality only)
For a PHD data source:
-Aspen Process Data (PHD) for PHD (limited to Trend Plot functionality only)
Optional, depending on the database being used with the client product:
-Aspen Timezone Information Service (Only applicable when connecting to an InfoPlus.21 database that is in a different timezone from the clients.)
Aspen Production Record Manager
Required:
-Aspen Production Record Manager Service
Optional, depending on the database being used with the client product:
-Aspen Process Data (IP.21) for InfoPlus.21
-Aspen Process Data (RDBMS) for an Oracle or MS SQL Server database.
-Aspen Process Data (PI) for PI
-Aspen Process Data (PHD) for PHD
Aspen SQLplus
-Aspen SQLplus service component
Aspen Tag Browser (component of multiple products)
-Aspen SQLplus service component
Keywords: None
References: None |
Problem Statement: The cylindrical barrel welded to a floating tubesheet of type P needs to be thicker to alleviate stresses at the junction with the tubeseheet when using UHX. The designer does not want to thicken this barrel. How can this be simulated? | Solution: Run the tubesheet design as simply supported.
The barrel thickness on the floating head of a P type exchanger (as in an AEP) will probably remain the same if the tubesheet is designed as simply supported. This means that the tubesheet is de-coupled from the welded cylinder in the design model. Sometimes the tubesheet ends up a little bit thicker.
In version 2006.5, the simply supported model input is shown below:
Keywords: TEAMS
simply supported
AEP
UHX
References: None |
Problem Statement: This knowledge base article describes how to troubleshoot the error
Access is denied. (The specified Windows NT host is not a member of a trusted domain, and the security settings of the current process do not permit such connections.)
which is generated during an Aspen Data Source Architecture (ADSA) connection attempt. | Solution: This error is caused by Microsoft Distributed COM (DCOM) connectivity problems. DCOM connections are used by client applications to connect to the ADSA server when public data sources are used. When this error is generated the server has rejected the attempt to connect to ADSA through DCOM.
To troubleshoot this error please follow these steps.
? Make sure that DCOM is not disabled on the ADSA server. This is a global setting for the entire server. When this option is checked, the machine allows the creation of DCOM objects. If it is not checked, objects cannot be created via DCOM. The server must be rebooted for a change to this setting to take effect.
If using Windows 2003 make sure that the Security Options under Security Settings does not have DCOM disabled. If using Windows 2000 make sure the 'Enable Distributed COM on this computer' option is checked in the Default Properties tab in Dcomcnfg.
With Windows Server 2003 the users either need to be in the Administrators group or the Distributed COM Users group. The latter group is new to Windows Server 2003 and any users that need to connect to the server through DCOM need to be in it or the Administrators group.
Please see the following link for Dcomcnfg usage:
http://support.microsoft.com/kb/q268550/
On the ADSA server machine verify that the user running the Test Connection has Access and Launch permissions in Dcomcnfg for the Aspen Data Source Directory. If any changes are made, restart the ADSA service and test again.
As a further test, set the DCOM default authentication level to 'none' using Dcomcnfg. This will prevent DCOM authentication checks.
Another workaround is to create the same client user account with the identical password on the ADSA server.
Yet another workaround is to give the client accounts administrative privileges. DCOM usually lets administrative accounts connect to the server.
The remote logon may also succeed if the normally-disabled, built-in Windows Guest account has been enabled, without a password, on the remote computer and on the ADSA server. In this case, the Windows operating system cannot actually identify the user. The user is granted whatever limited access that has been granted to the Guest user account by the system administrator.
Upgrading AspenTech software to version 2004 will allow the use of the new web service for ADSA, instead of DCOM. The ADSA web service will not encounter this DCOM error.
Use 'user' data sources instead of public data sources. The ADSA server can be bypassed altogether if 'user' data sources are used instead of public data sources. Since the user data sources do not use the ADSA server they are not prone to DCOM problems.
Keywords: Connect
Connection
Fail
Disconnect
Workgroup
References: None |
Problem Statement: What Is Tank Out Of Service Used For? | Solution: The tank out of service feature can be set in the ?CUSTOMER SETUP? screen under the tank information. This function should be used when you do not want to forecast product for a particular tank for an extended period of time. If you turn on the tank out of service button for a product then the system will automatically set the safe fill and pump stop to zero and no product will be forecast. In addition, the system will not allow you to lock in product for that tank.
Keywords: None
References: None |
Problem Statement: Why isn't the highest selling product the controling product? | Solution: Within a given order, there can be more than one product to be delivered. A controlling product is a product that will run out first in a given order. With this new feature, the user can pay close attention to the controlling product and manage deliveries more efficiently.
In the 'order' dialog window, the row that shows the controlling product of the order will be highlighted in red. This feature works only with a forecasted station.
Keywords: Controling Products
References: None |
Problem Statement: How does Aspen Shell and Tube Mechanical calculate the pressure drop of pass plate for code calculation? | Solution: If users transfer a Shell & Tube thermal case into Shell & Tube mechanical, the pass plate pressure drop should be automatically updated on Code Calculation.
If users only use a Shell & Tube mechanical but not have a pressure drop data, the pressure drop on Code Calculation will be a back-calculated results based on the pass partition thickness input. The program is stating that these partition plates will take up to this amount of pressure drops
For example, for the pass partition thickness as 3/8'', maximum pressure drop is 35.6 Psia. Please refer to the snapshot from Code Calculation below.
Keywords: Pass Plate Pressure drop, Code Calculation
References: None |
Problem Statement: We have a forecasted account that normally sells about 14,000 gallons of unleaded each day. The tank size is 20,000 and Retail usually delivers/forecasts an order of 8600 gallons for delivery. Instead of creating the usual order of 8600 or 9000 gals, Retail created two orders of 6200 gals each; one for today and one for tomorrow.
What can I review to determine why that happened? | Solution: Retail uses Compartment Configurations to determine the amount it forecasts for orders. If there is a compartment configuration that is smaller than a full load and short load is turned on then it can use this configuration to meet the delivery window established in Customer Setup. To check what truck is being used to forecast go to the Delivery Manager and pull up the station in question, highlight the order in question, then go to the reforecast GUI (looks like the backend of a trailer with an arrow pointing at it) this will tell you what truck is being used for forecasting.
Keywords: Demand Planner
Configurations
References: None |
Problem Statement: When testing the Aspen Data Source (ADSA) Directory server, the following error is received: The server threw an exception. | Solution: Three options are available to solve or work-around this problem.
Upgrade to version 4.x or
Stop and restart the ADSA service when the problem occurs or
Move the ADSA to a single processor machine.
Keywords:
References: None |
Problem Statement: What is the Aspen Simple Mail Transfer Protocol (SMTP) Configuration used for? There isn't any information in the ADSA manual. | Solution: Basically, this service is used to let Batch.21 know where the email server is on the network for emailing automated reports.
You can find documentation about the SMTP service in the Batch.21 v5.0.1 Help under the topic Configuring ADSA Data Sources. You can find the topic in the Contents pane of the Help topic by following this path of books: System Administration Tools/Batch.21 Administrator Help/Using the Batch.21 Administrator/Using Automated Reports. There are also several Index references to that same topic (you can find one of them by searching for the keyword Configuration and the subkeyword e-mail notification when reports run). There is also a description of the SMTP service in the Batch.21 v5.0.1 release notes (see CQ00101226 under Software Fixes for v5.0 Service Pack 1).
Keywords: adsa
smtp
services
References: None |
Problem Statement: If the actual load is different from the scheduled load will it change the ETA? | Solution: As stated above the ETA time will change based on the time passed into DELIVDATE, DELIVHOUR, DELIVMIN. In addition, if the order quantities are different than the originally dispatched quantities these quantities will be updated. The system will also compare the DISPDATE and DISPSHIFT in the load confirmation with the DISPDATE and DISPSHIFT that is currently on the load if these two differ then the system will update the date and shift to match the one inside the load confirmation record.
Keywords: Load Confirmation
References: None |
Problem Statement: What is the Status field in the STATIONS table used for and should a user modify it? | Solution: The status table is used internally by several Aspen Retail subroutines to track several types of status changes. This field should not be modified by users. It can be helpful to monitor this field when debugging problems with a particular station.
Keywords:
References: None |
Problem Statement: How can I change the customer ID number and retain the site history? | Solution: Under change customer number utility there is a check box for Holiday Storm Planner and History
Keywords: Customers
Changing numbers
History
Hiliday Stomr Planner
References: None |
Problem Statement: Are there any Crystal report template files that I can use to start? | Solution: See attached for template files
Keywords: Crystal Report
Templates
References: None |
Problem Statement: This knowledge base article provides example Visual Basic .NET code which retrieves a list of data sources from the Aspen Data Source Architecture (ADSA) server. | Solution: The example code is as follows:
'---
Dim myadsa As New AspenTech.Adsa.Locator.DsaLocatorClass
Dim available_adsa As AspenTech.Adsa.Locator.IAtDsaResults
Dim i As Integer
Dim number_of_adsa As Integer
available_adsa = myadsa.FindSources({79f29695-5113-11d3-9ba4-00e02905d02b})
number_of_adsa = available_adsa.GetNumResults() For i = 0 To number_of_adsa - 1
cbIP21Servers.Items.Add(available_adsa.GetDataSourceName(i))
Next i
available_adsa = Nothing
'---
Note: It is necessary to add a reference to AtDsaLocator.dll in order for this code to work.
Keywords: Datasource
References: None |
Problem Statement: When testing ADSA Web Service I am getting ?Request Failed: 500? error despite IIS settings and DCOM settings are correctly configured. See | Solution: ID: 129413 ?How to properly configure IIS in Windows 2008? andSolution ID: 124849 ?Aspen Data Source Architecture Test for Web Service failing with error message: Request Failed: 500?.Solution
This problem seems to be caused by IIS. If the above mentionedSolutions don?t solve this issue another way to solve it is to Repair the AspenTech installation.
Stop IIS and stop all AspenTech Services
Remove C:\wwwroot\aspentech\ folder
Restart IIS
Run Repair install of the AspenTech software suite
Reboot the machine
Keywords: Request Failed: 500
ADSA Web Service
References: None |
Problem Statement: What's the new cost and old cost on the GUI? | Solution: The old cost and new cost in the product GUI is for the best buy practice. So if you have multiple suppliers out of one terminal then you would update the New/Old fields with the price of what the products are. Some companies use a 3rd party to import the price into the TCIF_Prod_price table and then the Pricing service would import the updated cost into the terminals. This would also help if you were buying the product from a 3rd party.
Keywords: cost
best buy
References: None |
Problem Statement: What Should I Do If Done For The Day Does Not Run? | Solution: Done For The Day resets the Retail system so it knows that a new days information is coming into the system. If Done For The Day does not run then the data is treated as a inventory update rather than as new information.
If it is noticed that Done For The Day has not run prior to any of the new day's information being processed then simply run Done For The Day manually inside the Retail system.
If data has already been processed by the system then it is normally best to simply proceed that day without running Done For The Day.
If you choose to run Done For The Day after data is processed then it is best to go into the TCIF_SIIMPORT table and reset the new information flag on any data for that day that has been processed. This will allow this data to be re-imported not lost.
Keywords: None
References: None |
Problem Statement: Error received when performing a Test connection from an ADSA client to the ADSA Server:
Remote calls are not allowed for this process | Solution: Make sure that DCOM is enabled on the ADSA client machine. To do this, go to Start | Run | dcomcnfg. From there right click on My Computer, choose Properties, and the Default Properties tab. Make sure that the Enable Distributed COM on this computer is checked and then click on OK. Reboot the machine. Perform the ADSA connection TEST again.
.
Keywords:
References: None |
Problem Statement: How can we import Manual Orders from within the Optimizer? | Solution: Inside the Customize.ini file there is a setting called ManualOrder=
Setting this equal to 1 will allow a user to import any new Manual Orders from within the Optimizer.
To do this go under the Edit Menu | Import | Manual Orders
If this setting is set to 0, however, the Option will be greyed out under the Edit Menu.
Keywords: Import, Manual Orders
References: None |
Problem Statement: Use the Aspen Process Data (RDBMS) service to access time series data from any database (AspenTech only supports Oracle and MS SQL Server). The RDBMS service requires a Tags table be created in your database. For details on creating the Tags table, see the Aspen Process Explorer Installation Manual.
SQLA tags and RDBMS are similar in that both allow clients to access data from a relational database. There are some important distinctions to note, however.
When using SQLA tags, the relational database connection is centralized in InfoPlus.21. In InfoPlus.21 version 2004 and above, The connection to the relational database is defined in the Default SQLA Connection record (defined by SQLConnectionDef). For more information, see knowledge base item 115051.
The SQLA tags, themselves, are defined by the IP_SQLADef record. Process Explorer will simply point to the data via the ADSA data source for InfoPlus.21. Because the connection is focused through InfoPlus.21, it counts as only a single SQL Server connection for licensing.
When using RDBMS, on the other hand, Process Explorer points to the RDBMS data source in ADSA. The connection to the relational database is defined in ADSA. Because of the different architecture, each Process Explorer RDBMS client consumes a license when connecting to a Microsoft SQL Server database.
NOTE: Although the Aspen Process Data (RDBMS) service is designed to work with all relational databases, AspenTech only supports this service with Oracle and MS SQL Server databases. The following procedures are specific to Oracle and MS SQL Server database only. | Solution: To add services for Oracle or MS SQL Server:
1 On the Add Service dialog box, select the Aspen Process Data (RDBMS) service and click OK. The Aspen Process Data (RDBMS) Properties dialog box displays.
2 Click Setup to configure an ADO Connection String to access your data.
3 On the Provider tab, select either Oracle Provider for OLE DB or Microsoft OLE DB Provider for SQL Server from the Data Link Properties dialog box.
4 In the Select or enter a server name: box, select or type an existing server name with which to connect to the MS SQL Server database.
5 Select Use Windows NT Integrated Security if you want to use operating system authentication to access the the database.
OR
Select Use a specific user name and password to use database authentiction to access the database. Enter a User name and Password of an internal database owner account with permissions to access the database.
6 Check Allow Saving Password. Then click Test Connection.
It is important to check Allow Saving Password. Once your password is entered, it is encrypted, and only asterisks are displayed.
7 Select Select the database on the server option and select the database name from the list.
Note: You do not need to use the Advanced or All tabs on the Data Link Properties dialog box to complete your setup.
Keywords: RDBMS
relational
database
Oracle
SQL Server
References: None |
Problem Statement: The Aspen Data Source Directory service fails to start and it gives the following message:
Error 1058: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Also the following error is logged in the Event Viewer:
DCOM got error The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. attempting to start the service AtDsaDirectory with arguments in order to run the server: {0075A079-4B64-11D3-9BA3-00E02905D02B} | Solution: From Microsoft Knowledge base Article 241584 (http://support.microsoft.com/default.aspx?scid=kb;en-us;241584).
Click Start | Settings | Control Panel | Administrative Tools, and then open the Services applet.
Double-click the service that did not start.
Click the Log On tab.
Verify that the service has not been disabled for the hardware profile that you are using. If it has, click Enable.
Click the General tab. Verify that the service has not been disabled in the Startup Type box. If it has, click Automatic to have it start when you start the computer.
Keywords:
References: None |
Problem Statement: How should I create Size Groups? | Solution: What is the purpose of Size Groups?
Size Grouping is a way of speeding up the performance of an optimization. By grouping trucks together into Size Groups, you in effect create smaller subsets of trucks to consider when trying to find a home for an order. However, this can in many cases create a suboptimalSolution. This is because not every truck is being considered for every order. For some customers, in certain specific cases, this is acceptable because the tradeoff in speed performance vs optimal cost is not significant. Generally this is only to be determined after the client has run the system and is simply trying to step up the performance (speed) of the optimization.
How orders get assigned to Size Groups?
For forecasted customers, the Size Group that will be assigned to an order is the Size Group that is associated with the truck on which the order was forecasted.
For manual customers, the Size Group is determined by finding the truck that most closely matches the ordered quantities.
What is the end effect?
Once the Size Group is determined for all deliveries, the optimizer considers all available transports inside those Size Groups. Orders are never considered for trucks outside of the Size Group they have been assigned.
Example of a proper use of Size Groups:
30 Trucks at 10K Liters [Assigned to Size Group 1]
30 Trucks at 40K Liters [Assigned to Size Group 2]
etc...
Orders that are forecasted for the smaller trucks [Size Group 1]. The optimizer does not need to worry about attempting to find a good home on the larger trucks for these orders because they cannot go there anyway (usually). Thus the time that would have been wasted considering these invalid options is saved and the dispatcher can go about his duties more quickly.
Obviously the same is true for the orders that are forecasted for the larger trucks.
Example of an improper use of Size Groups:
2 Trucks at 10K Liters [Assigned to Size Group 1]
10 Trucks at 12K Liters [Assigned to Size Group 2]
5 Trucks of varying sizes from 8K to 20K [Assigned to Size Group 3]
In this case, both forecasted and manual orders will be confined to the Size Group that it has been assigned as per above.
If an order comes in for 10K Liters, for example, it has only 2 trucks that the optimizer will attempt to use. Even if they have set their X and Y values (under the truckmatch section of the Customize.ini) to allow the order to potentially be increased to 12K or descreased to 8K, the optimizer does not have the ability to make this choice because they are confined to Size Group 1. Thus the dispatcher will have to manually find a home for any orders that cannot be placed on the available trucks in their Size Group. This not only causes the dispatcher to have to spend potentially significant time manually adjusting the optimization, but seriously reduces the possibility that you have created the lowest CPV dispatch available.
Keywords:
References: None |
Problem Statement: How does TEAMS handle corrosion thickness for the tubesheet? | Solution: The corrosion allowance used in the tubesheet thickness is a function of the tubesheet material, TEMA class if any and User corrosion allowance entry, if any. For carbon steel and low allow steel, the default corrosion allowance is 0.0625 for TEMA classes B and C and 0.125 for TEMA class R. The program will use any corrosion allowance specified by the User. Teams will not use corrosion allowance as a default for alloy materials.
The TEMA tubesheet thickness calculations are based upon an effective thickness. This effective thickness does not include corrosion allowance. The corrosion allowance is added, after the calculations, to the effective thickness to determine the total required thickness.
In the ASME UHX method, all calculations are performed with corroded thickness. The corrosion allowance, if any, is added after the calculation is finished.
The Tubesheet Summary in the Vessel Dimension section of the result will display values for:
Effective calculated thickness
Code requried thickness
Shell side corrosion allowance
Tube side corrosion allowance
Pass partition recess, if any
Actual required thickness
In the Summary output section Teams will show all relevant thicknesses used in the determination of the 'actual' thickness. The actual thickness contains all relevant corrosion allowances. In the detail output section, the thickness shown, whether UHX or TEMA does not include the corrosion allowance or any other thickness allowance (pass partition groove, clad thickness, etc.).
Hetran, since it only convers the thermal design of a heat exchanger, does not use the corrosion allowance in the estimation of the tubesheet thickness. Teams, as a rigorous mechanical design system, takes into account the corrosion allowance when calculating any vessel thickness.
Keywords: heat exchanger
corrosion
tubesheet
References: None |
Problem Statement: What are the default limits inside Aspen Retail | Solution: Aspen Retail Database Limits
This document lists all the known maximum values of variables that globally affect the Aspen Retail application. The list of maximum values is based upon searching for max in the source code. The accuracy may be 99%.
General
Maximum Product Name (12 Characters)
Maximum Possible Quantity (08 Numbers)
Maximum Amount of Terminals (100)
Maximum Amount of Stations in a Cluster (06)
Maximum Number of Fuel Categories (10)
Maximum Number of Products at the Terminal (200)
Maximum Number of Clusters (10,000)
Maximum Number of Groups (30)
Stations
Maximum Number of Restrictions per Type (05)
Maximum Number of Zones (512)
Maximum Number of Products at a Station
(05)
Transports
Maximum Number of Compartments on a Transport (12)
Maximum Number of Transport Attributes (05)
Maximum Number of Transport Fill Lines (10)
Maximum Number of Transports (200)
Maximum Number of Cost per Volume Charts (500)
Transportation Scheduling Optimization
Maximum Number of Dispatching Shifts (62)
Maximum Number of Overflow Orders (1,000)
Maximum Number of Orders per Non- List Transport (20)
Maximum Number of Deliveries (1,000)
Maximum Number of Partners for a Split Load (120)
Keywords:
References: None |
Problem Statement: Aspen Local Security allows security to be set at both the Application level and the Database level all the way down to Record and Field level. If Record level security has been implemented, how can you tell which records do not have READ access? How can you add READ access to these records?
Versions of InfoPlus.21 earlier than version 4.0 did not have any global methods for accessing or setting security. In 4.0, some SQLplus and API level routines have been added to allow for mass security changes. Some example queries are provided below to demonstrate this feature. | Solution: A query that selects all records that have no record level security is:
select name from all_records
except
select distinct table_name from information_schema.role_table_grants;
A query to assign READ level security to these records is:
grant read on
(select name from all_records
except
select distinct table_name from information_schema.role_table_grants) to everyone;
where everyone is a Plantelligence role.
Keywords:
References: None |
Problem Statement: How does Safety Stock work? | Solution: Safety Stock works in the same fashion as Run out Buffers but is configured by setting a volume rather than an hourly buffer.
When scheduling deliveries, the Optimizer considers the delivery windows on the current shift horizon. If a particular order was originally forecast for X shift, but has a Retain Buffer or Run Out Buffer (or Safety Stock) which when added to the retain/run out time in the delivery window of the order would push either the retain time or run out time to a different shift, this order will not be scheduled for this shift.
For example, if a Customer's delivery window is
Retain 6/1 3pm
Runout 6/2 11am
This customer has a 20 hour delivery window.
If the customer has the following buffers:
Retain Buffer 3 hours for both day and night shift
Run out Buffer 9 hours
This same order has a 11 hour buffered delivery window. As long as the buffered window is at least 5 hours, the system will leave the buffers as is. If the buffered delivery window is not at least 5 hours, the system will cut the buffers in half up to 3 times until it can either achieve the 5 hour buffered delivery window required, or it is forced to remove the buffers altogether.
Safety Stock is calculated in much the same way as the Run out Buffer except it allows the user to enter this value in volume rather than time. This volume will then be calculated into a time value (by using the customer's expected hourly sales during the projected horizon) inside Aspen and applied in the same fashion as the Run out Buffer. If both Safety Stock and Run out Buffers are configured, Aspen will apply whichever one is larger while still maintaining the 5 hour buffered delivery window.
Key words
Safety Stock
Keywords: None
References: None |
Problem Statement: How to mark loads delivered in DQM. | Solution: The Load Lock flag (check box) at the top right of the screen allows the user to manually identify expected deliveries as already delivered shipments. With this box checked, the user can click on an expected delivery using the right side mouse button and mark it delivered. Aspen Retail will automatically add the delivery to the inventory. If this flag is not selected, Aspen Retail will automatically calculate what shipments should have been marked delivered. When forecasting by inventory only, Aspen Retail may require the user to use Load Lock to identify delivered shipments if Aspen Retail is unable to judge what was delivered.
Keywords:
References: None |
Problem Statement: There are rigidity factors shown in Aspen Shell & Tube Mechanical section 8 paragraphs 2-14. Is there a way to override the default values? | Solution: We can input values of KI and KL rigidity factors in version 2006.5 and any version after that. The input fields are in the Input | Exchanger Geometry | Body Flanges | Options tab.
Keywords: ASME, KI, KL, rigidity factor
References: None |
Problem Statement: This Knowledgebase Article discusses the Windows Event ID 10021 as it relates to Aspen Data Source Directory (ADSA) , which can be seen in System log section of the Event Viewer: | Solution: This re-occurring error is related to DCOM permissions affecting ADSA. The CLSID {0075a07a-4b64-11d3-9ba3-00e02905d02b} in the Event description corresponds to the ADSA DCOM Config entry:
This Event normally occurs when ADSA tries to start the DCOM server by using the DCOM infrastructure. However, the permission associated with the DCOM Server may not be correctly configured. In order to fix this problem, a simple, knownSolution is to set the ASDA Security Launch and Activation Permissions the machine default by following these steps:
1. Go to Start | Run and type dcomcnfg
2. Locate and expand DCOM Config
3. Locate Aspen Data Source Directory, right-click and select Properties
4. Select the Security tab and select Default under Launch and Activation Permissions. Click O.K
5. Go to the Windows Services Panel and restart the Aspen Data Source Directory Service
6. Verify that the System errors in the Event Viewer log are no longer occur
In the event that this message continues to appear, please contact AspenTech Support at your earliest convenience.
Keywords: ADSA
DCOM
CLSID {0075a07a-4b64-11d3-9ba3-00e02905d02b}
References: None |
Problem Statement: Your end users are trying to upgrade your database servers. However, when you attempt to launch the Admin Console, it comes back with the ?The page cannot be displayed? error. Also the Informatica Services 8.1.1 SP4 service will not remain running after I start it. | Solution: If your integration service's database is not up and running, you cannot bring up the admin console (domain). There is no simple method of pointing your integration service to the new database. It is recommended to have a backup integration service pointing to your backup database server.
Keywords: Informatica
Integration Service
Powercenter
References: None |
Problem Statement: Why the background turns red when I specify design pressure more than 3000 psi in Shell & Tube Mechanical? | Solution: The red background in input is a signal that the design pressure is over 3000 psi and for the user to be careful. However, the program will run with higher pressures and program reliability is the same under or above 3000 psi.
The red background comes from U-1(d) (ASME Pressure Boiler and Pressure Vessel Code Section VIII, Division 1) code paragraph as a 'reminder':
U-1(d)
(d) The rules of this Division have been formulated on
the basis of design principles and construction practices
applicable to vessels designed for pressures not exceeding
3,000 psi (20 MPa). For pressures above 3,000 psi
(20 MPa), deviations from and additions to these rules
usually are necessary to meet the requirements of design
principles and construction practices for these higher
pressures. Only in the event that after having applied
these additional design principles and construction practices
the vessel still complies with all of the requirements
of this Division may it be stamped with the applicable Certification
Mark with the Designator.
Keywords: Design pressure, program reliability
References: None |
Problem Statement: Why the Tube Layout is different in Aspen TEAMS as compared to Aspen Tasc+ ? | Solution: Aspen Teams and Aspen Tasc+ came from different program families (B-JAC and HTFS), so the layout programs are different.
Aspen HTFS+ will eventually have only one layout program. In the later versions (V8.0 and later), the layout in Teams will be the same as in Tasc+.
For now (V7,1 and earlier,) user will get the Teams layout in Teams and the Tasc+ layout in Tasc+. As far as thermal performance, make sure that the major geometry parameters are the same (tube OD, pitch, layout type). Also the entrance/exit areas are close for accurate pressure drop calculation.
Refer to the attached word document that details steps to create Teams tube layout within Tasc+.
Keywords: tube layout, teams, tasc+, shell and tube
References: None |
Problem Statement: In the most European countries the comma is used as decimal seperator and the point is used to indicate 1000 units. If you open Retail with these settings and you go into a station screen, the unload time will change automatically without the user seeing it. When closing that station screen you get an error. For example : Unload time is 0.6 h originally. When the station is opened, Retails converts is into 600 h. In the optimizer, this would result In station going into the overflow because no truck can deliver a station where it takes that many hours to unload. | Solution: The workaround is that every time someone access a station, they have to put it back to the original value.ck the value and put it back to the original value.
Keywords: decimal point
unload time
References: None |
Problem Statement: How do I know if the target Access database is compatible with the source database? | Solution: Sometimes you can tell by the name of the empty target database. But, in the middle of the DBCOPY procedure, the program will allow you to test the differences between the source and the target database. If you see many differences, assume you have the wrong target database.
Also, you don't have to use an empty Access database as your target. The DBCOPY utility will overwrite any database of the correct format. So, if you have a test database in Access format for your current Aspen Retail version, you can make a copy of it and use the copy as your target database.
Keywords:
References: None |
Problem Statement: Both Aspen Framework and Local Security Server provide a graphical user interface called Afw Security Manager for specifying security data. Administrators should secure the Afw Security Manager by defining who can open and use this tool before making any security specifications. Only people belonging to a role having Open privilege on the AfwSnap-in secured object can open and use the Afw Security Manager. The process of securing a database is documented as a post installation procedure in both the Aspen Local Secuity Server Installation and the AFW Server Installation manuals. For Local Security Server, see the section titled Configuring Aspen Local Security for more information. This document summarizes the procedure documented there.
The following warning will be issued by the Afw Security Manager if these post installation steps were not completed: AFW Security Manager is not secured, please assign Open permission to the role(s).
If the Afw Security Manager is not secured, any user from any client PC connected to the security server may use the Afw Security Manager to edit the security database. | Solution: Steps for securing the Afw Security Manager:
1. In the AFW Security Manager tree view, right click Application, and choose All Tasks | Import Application.
2. Select the AFWSnapin.xml located in the AspenTech\Bpe installation folder, i.e., C:\Program Files\AspenTech\BPE
3. In the tree view of AFW Security Manager, expand AFW Security Manager | Applications | Aspentech Frame Work and select Security Manager.
4. Right click the AfwSnap-in securable object, and choose Properties.
5. In the AfwSnap-in Properties dialog box, select the Administrator role (or other role that should have access to the AFW Security Manager) from the drop down list. Check the Open check box.
6. Click OK.
7. Restart the IISAdmin service (and dependent services) in the Services Snap-in for the change to take effect.
Only members of a role holding Open privilege on the AfwSnap-in secured object will be able to start the Afw Security Manager. The following message will be displayed for all others: You don't have the permission to open the AFW Security Manager or the AFW Security Manager initialization failed.
Keywords: None
References: None |
Problem Statement: When it's time to upgrade your IP.21 server you had spent considerable amount of time configuring, you'd want to preserve and transfer as many of your original settings and customizations to the new server as possible.
Here is a step-by-step procedure for how to properly migrate AFW Local Security server from one node to another. | Solution: IP.21 server component:
1. Shut down IP.21 and all client applications on the old machine.
2. Backup and save the AFWDB.mdb Access Database file, located in the [drive]:\Program Files\AspenTech\Local Security\Access97 directory.
3. Take your OLD machine off line and prepare your NEW machine for IP.21 installation by first renaming it (recommended but not required) to match the old machine's name and then checking to make sure that it meets all hardware and software requirements as described on p. 2-6 and onwards in the InfoPlus.21 Installation Manual.
4. Install IP.21, ADSA, and AFW Local Security on the new machine.
5. Copy the previously backed up AFWDB.mdb Access Database file to the above-mentioned directory on the new node where the AFW Local Security has been installed (this step will overwrite the empty AFWDB.mdb file created during the installation).
6. Start IP.21. Your old local security settings should now be restored.
IP.21 client component:
NOTE: If you have renamed the new IP.21 server to the same name as your old IP.21, you can skip the steps below. Otherwise, read on.
1. On all your client machines, run the AFWTools.exe utility located in the BPE folder ( [drive]:\Program Files\AspenTech\BPE ).
2. On the Client Registry Entries tab double-click on the URL entry.
3. Change the old node's name, which appears in the Data field to the name of the new node where the AFW Local Security is now located.
4. If the location of your ADSA server has also changed, point all your client nodes to the new ADSA.
NOTE: Only one AFW Local Security server can be assigned per client node at a time so all client applications installed on that node must use the same AFW Local Security server.
Keywords:
References: None |
Problem Statement: What are the purpose and function of Security Utility? | Solution: Group security is currently used by one custsomer with their WTS (windows terminal server) to limit users' access to terminals and groups. For example, the New York dispatcher is not able to access California terminals and vice versa. Currently, this is only in place at one customer site and it may need WTS to function correctly.
What prevents a user whose security profile restricts access to certain items in retail from modifying their profile in the security window to gain access?
Inside oracle a grant statment must be run on a users id before he can access that table. If this role is not granted the user has read only access to this table.
Keywords:
References: None |
Problem Statement: What does the error The specified DSN contains an architecture mismatch between the Driver and Application mean? | Solution: This may appear in a 64-bit Windows Server 2008 environment when working with an IIS ASP.NET application.
In the advanced settings for an IIS application pool that's being used with the application you need to set Enable 32-bit application (part of the Advanced Settings) to eliminate the condition which presents the error message.
Keywords: Windows 2008 64-bit, error, .NET
References: None |
Problem Statement: Do you have a excel list indicating the B-JAC no. for each material in Aspen Shell & Tube Mechanical? | Solution: Yes there is a Microsoft access database file inside each of the ASME material years under the installation directory where you can find the Material list.
You can look inside the ASME material year that you are interested in under folder \PDA\ASME???? as shown here:
For example, the ASME2007.MDB files contains 3500 materials.
Keywords: material list, database, B-JAC no, ASME
References: None |
Problem Statement: How to reduce the number of empty kilometers on trips? | Solution: There are two things you can do:
Assume that you have one full load. If best buy is NOT activated, Aspen Retail will look at trip time (not distance) to find the closest terminal. Assume there is a truck available to deliver the load (fill levels, start time, restrictions, product availability, etc.). Once the truck delivered the load to the station, it can either go back to the original terminal and incur the empty kilometers from that, or it can be loaded at another terminal based on the location of the next load(s). If you prefer the second option, then do not turn on the source lock or build in loading restrictions. This would enable a station to be delivered to out of all terminals in the group. This approach could reduce the number of empty kilometers but it requires a lot more flexibility at the terminal level.
Another way to reduce the empty kilometers would be the use of remote truck stops. Truck stops can be considered as parking places where trucks are parked but no product can be loaded. At the end of the day, trucks return to the truck stop. If the distance from the last drop to the truck stop is less than the distance to the terminal, you can reduce the number of empty kilometers.
Keywords:
References: None |
Problem Statement: What do the different statuses mean in the Customer Status Report? | Solution: Whenever sales/inventory data are reported either through the services, or through manual information collection the STATUS field inside the TPS_STATIONS table is updated. Also during the DQM process, when HOLDFORECAST option is checked and the user selects the shipment to be marked as delivered through the Inventory update dialog box, or user Accpets the new information, SPECSTAT2 field in the TPS_STATIONS table is also updated.
The STATUS field can have the following values:
0 = No new sales or inv data has been input for the station. 1 = New data exists for station.
3 = No Exceptions were found during processing.
4 = Station has been forecasted successfully.
11 = New data exists for station.
15 = New Data for station is sales only.
16 = New Data for station is inventory only.
21 = Sales Threshold reported is violated.
22 = Inventory Date is bad.
23 = Balance between expected deliveries and expected inventory bad. 24 = Sales and Balance Bad.
30 = Skip station because no verification yet for inv only data.
40 = Skip station because already forecasted.
The SPECSTATUS field can have the following values:
1 = During secondary inventory updates, when there is an exception, station's specstatus is marked with this value, so that during DQM process, the user can selected the orders to be marked as delivered to be included in the update. (To move orders from order table to old order table)
2 = During secondary updates, when there is an exception (if the net increase in volume is not over 75%), station's specstatus is marked with this value to move orders from old orders table to orders table.
The SPECSTAT2 field can have the following values:
0 = By default
1 = During secondary (multiple) updates, when there is no exception, and orders are moved automatically from dispatched to delivered log, this field is updated with value of 1.
Keywords: TPS_STATIONS
SPECSTAT2
SPECSTATUS
STATUS
References: None |
Problem Statement: When clicking twice on the Trial button on the What-If screen, the Retain time changes from the original value. | Solution: Fixed in 7.04.00.04 or higher (Service Packs)
Keywords: What if
Trial Button
Retain time
References: None |
Problem Statement: How do I specify absolute vacuum design pressure? | Solution: Absolute vacuum design pressure is specified by entering 15 (or -15) psia in the vacuum design pressure input cell. Any value entered in this cell is taken as external pressure.
Keywords: Absolute vacuum design pressure
References: None |
Problem Statement: Why is the ADSA Configuration Applet missing the Public Data Sources button after a full server installation? | Solution: Aspen Data Source Architecture (ADSA) is a component that needs to be selected separately during the installation if the server needs to be set up as ADSA server.A If this component is not selected as a part of the install opening the ADSA client configuration tool on the server will not show the public data sources button as an option.A If ADSA was not selected during the initial install a modify' installation must be completed and the ADSA Server component added.
Keywords: ADSA Server
Public Data Sources
References: None |
Problem Statement: Do you have any literature on Expanded Tube to Tube sheet joint contact pressure calculation that Exchanger Design and Rating (EDR) uses in the Aspen Shell & Tube Mechanical software. | Solution: Attached is the basis of the interfacial pressure calculation used in Aspen Shell & Tube Mechanical program.
Keywords: interfacial, pressure, calculation
References: None |
Problem Statement: Where Can I Find the odbcerrorlog.txt and the dberrorlog.txt? | Solution: The odbcerrorlog.txt and the dberrorlog.txt can be located in the following directory
C:\Program Files\Common Files\AspenTech Shared\Settings
Keywords: -------- odbcerrorlog dberrorlog error logs
References: None |
Problem Statement: Why does it seem like the fitMatch setting is no longer working? | Solution: The fitMatch setting, formerly in the psoft.ini (7.4 and earlier), is now located in the Internal.ini. This setting was wrongly moved to the Customize.ini file in some version of the convert.exe program (designed to migrate ini settings from the former psoft.ini and psoftg.ini to the newer customize.ini, internal.ini, and services.ini). Since this setting is actually being read from the internal.ini, whenever the optimizer is run, this setting is automatically created in the Internal.ini if it does not exist and it may be given the default value (=1).
Therefore the fitmatch setting in customize.ini has no effect whatsoever and should be deleted to avoid confusion.
Keywords: fitMatch, Customize.ini
References: None |
Problem Statement: What are Yesterday's Sales in Data Quality Manager? | Solution: In Data Quality Manager and Manual Information Collection, Yesterday's sales are the Customer's sales for the previous 24 hour period ending at today's reported inventory time. These sales figures are collected daily in sales only and sales & inventory forecasting. With inventory only forecasting, yesterday's sales are calculated by Aspen Retail.
Key words
Yesterday's Sales
Data Quality Manager
Keywords: None
References: None |
Problem Statement: How should I set up Clusters? | Solution: Clusters are used in Aspen Retail, in addition to Clouds (super-clusters) to try to satisfy replenishment needs when for whatever reason one or more customers cannot receive a full delivery.
A Cluster is a group of 6 or less customers that are put together to be potential partners for split deliveries. A Cloud is a group of Clusters (because the Cluster limitation is 6 members).
When creating Clusters, the following factors should be considered:
? Delivery Constraints
o Time Restrictions at the customer sites
If one customer needs split partners but that customer can only receive night deliveries, putting him in a cluster of stations that can only receive day deliveries will not meet his split partner needs.
o Transportation Restrictions
The members of a Cluster should have significant overlap of available Transport options when possible.
o Product Loading Restrictions
If one customer has a product that cannot be hauled with other products, but the orders for this product do not fill a truck completely, the customer should have split partners that also need this product
o Terminal Restrictions
If certain customers can only be loaded out of specific terminals, they need to be paired with customers that can be loaded out of the same terminals.
o Geography
Cluster members should, when possible be in close proximity to each other, but as a rule should never require the truck to drive past the terminal to reach one another unless that distance is very short.
Manual Customer Cluster Needs
In addition to the above constraints, Clusters should also be created with the view that more options is always better. If Manual Order customers need a split partner, the order is for a fixed quantity and will need a partner that is either:
1. Forecasted so it can be adjusted to fit the remaining compartments on the truck
2. Another Manual Customer that is ordering for the remaining quantity to fill out the remaining compartments on the truck
In the case of ?1? above, it is useful to have as many forecasted customers as possible paired up with this Manual Customer to try to guarantee one of them will need a delivery on the same shift that the Manual Customer is ordering for. In the case of ?2? above, it is even more important that there are a number of options because the order size is fixed and it may be a lot harder to find a partner to match up with this order.
Forecaster Customer Cluster Needs
All of the above considerations are important for Forecasted Customers who need small deliveries as well. In addition to the above considerations, whenever creating clusters of Forecasted Customers, it is good to have a mix of Customers with both small tankage (high need for split deliveries) and large tankage (hopefully able to take the balance of truckloads that cannot be delivered to these small tankage sites). This will help provide the most flexibility possible for the problem customers.
Clouds
All of the above considerations should be taken into account when creating clouds as well. Clouds should be considered simply an extension of Clusters. Clusters are limited to 6 members, but there is no limit to the number of Clusters that can be assigned to the same Cloud. Certain performance considerations should be taken into account when putting Clusters into clouds (simply test this out with samples of optimization time as you increase the size of your Clouds), but in general all delivery constraints for Clusters should be observed as much as possible for Clouds.
u Keep this in Mind
Customers are more likely to be automatically Split with others when they are Clustered together with good partners. A lazy approach of simply adding a wide variety of Customers together into haphazard Clusters and adding all those together into Clouds will not be as effective as diligently aligning Customers with the same delivery requirements (when possible) into the same Clusters and extending those to Clouds where necessary.
Keywords: Clusters
References: None |
Problem Statement: What is the purpose of Last Contained restrictions under Product Setup? | Solution: The Last Contained section under Product Setup is a method of configuring the Optimizer to avoid loading specific products immediately after one another.
The matrix provided allows you to specify which Previous Product is not allowed to be followed by a Restricted (if selected in this matrix) Next Product.
Keywords: Last Contained
References: None |
Problem Statement: What is the Restricted field used for on the Truck Set-Up Screen? | Solution: The Restricted field is used to indicate if a Transport should be limited to carrying only deliveries for Customer's who are flagged with this Transport as the Default Transport on Customer Set-Up Screen.
Transports with this flag unchecked can haul deliveries for all Customers in addition to the ALL the deliveries for the Customers with this transport as their Default Transport.
Keywords: Restricted, Default Transport
References: None |
Problem Statement: How do I change a date in DQM if a user accidently enters and accepts a future date? | Solution: If a user accidently enters and accepts a future date in the DQM process the only way to change this is to go directly into the ORACLE/SQL tables and edit the date. The table that needs to be edited is the TPS_YESTINFO table. The INVDATE and FIRSTINV date fields need to be reset to the current date.
Keywords: None
References: None |
Problem Statement: How do I configure the MinSplitPercentage INI Setting? | Solution: MinSplitPercentage=50 (default)
The minimum percentage to which a transport must be loaded in order to deliver a split shipment to a customer
Acceptable Values: 0 to 100
Use: Use this option to reduce the instances when a split load is created that only utilizes a small portion of a truck. This option allows the enforcement of the minimum percentage a split load needs to meet in order to be a valid split load
Example:
MinSplitPercentage = 50
Total Truck Size = 10,000
If the split percentage is set at 50%, only shipments that fulfill 5000 (50%)
of the full transport are included. The application will not create a split
shipment for less than 5000
Key words
MinSplitPercentage
INI Settings
Keywords: None
References: None |
Problem Statement: The following error message is received when opening the ADSA Client Config Tool:
Unrecognized flag: /i
Usage: regsvr32 [/u][/s] dllname
/u - Unregister server
/s - Silent display no message boxes
/c - Console output | Solution: Update the %SystemRoot%\System32\regsvr32.exe file to v5 or later (by whatever means possible)
Keywords:
References: None |
Problem Statement: How do I setup a multi-sourcing truck depot | Solution: Create new groups inside of Group Setup
Create a terminal for every supply point (places with product and no trucks) and a terminal for every truck depot (places with no product but where trucks are housed). In some cases a terminal may need to be in more than one group for these cases create a second terminal under a new terminal number. For the terminals that are setup as 'truck depot's', click the truckstop' check box inside the main screen of Terminal Setup.
For example create terminal number (1) Bangor and terminal number (2) Bangor 2. Make the name slightly different so it is easier to tell which terminal should be in which group. Inside the terminal setup the two Bangor terminals will be exactly the same except for the terminal number and the terminal name. Lastly, it will be important to setup terminal-to-terminal trip times and distances from all the terminals.
Next create the different trucks for the terminals. Trucks should be primarily assigned to the terminal they physically start and end at. For example if a truck starts and ends in Bangor but there is no product or customers assigned there, the truck should still be housed primarily in Bangor. (FYI: The system will always route the truck to return to its primary terminal at the end of a shift.).
Next assign the customers or stations to their primary terminal. The station's primary terminal should be the terminal that the customer most often gets product out of. It will, however, be very important to not only fill in the trip time and distance for the primary terminal but also for any alternate terminals a customer could receive product from.
Keywords: group,
terminal,
trip time
References: None |
Problem Statement: There is a new Data Source Component available within ADSA. The new OPC-DA Server Data Source component allows users to configure an OPC-DA Server directly as a data source. This data source can then be connected to by the AMS client applications. There is some confusion regarding which AMS client applications can make use of the new Data Source component. | Solution: The only AMS client applications that can access the new component are AspenCalc and Web.21 Graphics (the Web.21 Graphics editor also has an OPC Tag Browser that can connect to the data component. The OPC Tag Browser will only find tags if the OPC Server being connected to supports the browsing function).
So, Aspen Process Explorer cannot connect with Data Sources configured with the OPC-DA Server Data Source component. This also applies to the Excel Add-In, the standard Tag Browser, and SQLplus.
Keywords:
References: None |
Problem Statement: Is it possible to configure an RDBMS data source for Microsoft Access? | Solution: Microsoft Access is supported for use with the RDBMS data source functionality in version 6.0 of the Aspen Manufacturing Suite. Microsoft Access was not supported in prior versions the Aspen Manufacturing Suite.
Additional information can be found on page 8 of the Aspen Process Explorer 6.0 Release Notes. That document can be accessed using the link below.
http://support.aspentech.com/Documents/Manufacturing/AspenProcessExplorer/V6.0/AspenProcessExplorerReleaseNotes60.pdf
Keywords: database
MS Access
References: None |
Problem Statement: What's New in Aspen Shell & Tube Mechanical V7.3 - ASME 2010 Elastic-plastic design procedure for floating tubesheet exchangers | Solution: The ASME VIII-1 2010 code included the elastic-plastic design procedure for floating tubesheet exchangers. With this program addition, previous design cases that were overstressed at the tubesheet-to-cylinder junction can now be designed considering the effect of plasticity at the cylinder-tubesheet joint. The program will use this procedure automatically when applicable to further optimize these types of exchangers.
Designs that may have provided this warning:
are now designed without having to increase the cylinder thickness to alleviate a potentially overstress condition.
Keywords: ASME 2010, Code, Elastic-plastic design procedure, floating tubesheet exchangers
References: None |
Problem Statement: How does often does Aspen Tech update Aspen Teams to include the latest ASME code? | Solution: The ASME releases a code update every year. Every 3 years the entire code is reprinted. Between the 3 years, an addendum is issued. Typically, the new ASME code is required to be used by January 1st, in the year following the new ASME code release.
Each calendar year, the Aspen Teams developers release a new software update by December or earlier. Here is how a release cycles were or will be handled:
TEAMS version ASME Code Version
2006 2004 with ASME addendum of 2006 (or A06)
2006.5 2007 (full code)
7.0 2007 with addendum A08
7.1 2007 with addendum A08
(released to coincide with other Aspen software releases)
7.2 2007 with addendum A09
Keywords: ASME Code, TEAMS, development cycle
References: None |
Problem Statement: What Does A Red Order On A Truck Mean? | Solution: Orders that are red do not match the truck compartments/fill levels for the truck they have been placed on. If an order is manually placed onto a truck and it does not match the compartments on that truck then the order will turn red. If an order is red on a truck then the system will not be able to export loading or unloading information for that order into the common interface tables.
Keywords: None
References: None |
Problem Statement: When configuring ADSA, what services need to be configured to access CIM/21 data? | Solution: The only ADSA service that needs to be configured is Aspen Process Data (Cim21). For the host name, enter the official Net/21 nodename of the CIM/21 server. This name can be found by going to the $n21/bin directory and issuing the nodename command.
If client applications (e.g. Process Explorer) are still not able to access CIM/21 data, confirm that the socket_m process is running on both the CIM/21 server and client machines. The socket_m process is started using the Net21 Manager on the client machine.
See Knowledge Base item #102896 for additional information related to this topic.
Keywords: data source
socket
References: None |
Problem Statement: What is the usage of the main Aspen Retail reports? | Solution: The purpose of thisSolution is to describe the usage of the main Aspen Retail reports during daily operations.
The Aspen Retail Suite User's Guide contains the full list of reports with a description for each one of them.
 Customer Status report
Indicates the status of forecast customers (New information needed, Sales only, Inventory only, Manual, Forecasted). The Done for the day service is resetting all customers to New information needed. From there on the TimImport and SalesImport service can bring in new sales and inventory for forecast customers. The user only has this report in Retail to check if the sales and/or inventory has been imported.
Usage:
Only forecast customers.
To be used daily before DQM. The report will give a good indication on whether enough records have been received to start DQM.
To be used again after DQM to see if all important stations have been forecasted. Stations that are not marked as Forecasted after DQM, will not be re-forecasted even though new information is available.
Use the filter on the report to show the relevant stations.
Customer Setup report
Indicates the product setup for all forecast stations and also gives a clear overview of their trend information. This trend information will determine the quality of the forecast. On one page the report gives a clear overview of 4 weeks of historical sales data, as well as an estimate for the next week.
Usage:
On a weekly basis, the dispatch manager or supervisor has to open this report over a terminal or group and go through the trend information. If, during DQM, strange values were accepted or overwritten, this report will indicate the errors. Possible errors can be communicated to the dispatcher who can then update the trend information. This action is very important if only sales are imported.
If stations are moved from order-entry to forecast, it is useful to check this report on a daily basis during the first few weeks to make sure that the trend is updated and written in the correct week. Also make sure that after one full week of data Retail is moving to the next week itself.
If a specific problem occurred with a customer (retain, runout), the dispatcher can consult this report to check the estimated values.
Info Update Log
This report logs every entry related to the DQM process and data entry via interfaces. All data (sales/inventory) that is entered (manually or automatically) is logged in this report as well as the entries that are accepted or overwritten in the DQM.
Usage:
Only forecast customers.
To be used in case of anomalies (retain, runout). This report will allow the dispatcher to verify what data went into the DQM process and what info was accepted or overwritten.
Downside: only details per product and not per tank.
Sustainable Shipment report
This report gives an indication of loadsize for every forecast customer assuming that all products are in proportion. Based on this report, a trade-off can be made between loadsize and delivery window. More time to deliver (runout - retain) implies less loadsize.
Usage:
Only forecast customers.
This report helps detect which stations need splits on a regular basis. You will have to assume a delivery time (for example 18 hours). For this delivery time, the report will indicate the loadsize in volume. Stations that do not accommodate a full truck need either to be set up in a cluster or accept less delivery time. Full-load stations that are never split can also be identified via this report.
Buffer length can be determined by this report.
Downside: only details per product and not per tank.
Tank Inventory Management report
This is the only report in Retail where the user has a quick overview of the tanks % that has been set up for all stations. If sales are reported by tank, these % are updated on a daily basis.
Usage:
Only forecast stations. Order-entry stations cannot have multiple tanks.
To be used on a weekly basis during first weeks of go-live. After that, a monthly review will do.
Look for tanks where the proportion is very disproportionate (one tank that sells 99% and another tank that sells 1%). These values are possibly wrong and will cause runouts and retains on tank level.
RSO Audit report
Summary of every shift saved by an user. Basically a printout of the scorecard.
Usage:
Useful for KPI's
While the scorecard can only be opened for the current shifts, this report allows a view on the KPI's of past shifts.
Sales quadrants by trend
Allows a quick overview of sales quadrants.
Usage:
When setting up forecast stations, this report gives a quick overview of the sales % per quadrant.
Terminal orders report
This report can be sorted by customer, retain, runout and shift. The report shows all orders in the Retail database, forecast and order-entry, sorted by the criteria chosen by the user. Normally the user would sort by runout. A cut-off date can limit the orders up till a certain point in time.
Usage:
Both forecast and order-entry customers.
To be consulted after the dispatching activities.
Check the flag to see that all orders with a certain runout date are marked as dispachted. If not, this means an order was forgotten and station will run out. At this point in time, you still have a possibility to correct the error.
This report can also be checked before starting the dispatch activities, to have an indication of the number of orders for a certain shift (use cut-off date in the filter).
Keywords: REPORTS
References: None |
Problem Statement: Can I model multi-tube hairpin exchanger using the Aspen Teams program? | Solution: Unfortunately multi-tube hairpin exchangers are outside the scope of Teams. Teams only encompasses the mechanical design of shell-and-tube heat exchangers.
Keywords: multi-tube, exchanger
References: None |
Problem Statement: What's New in Aspen Shell & Tube Mechanical V7.3 - ASME 2010 Nozzle reinforcement design for all applicable nozzles under appendix 1-10 | Solution: The ASME VIII-1 2010 code included a change to appendix 1-10 that eliminated the `large? nozzle label from this alternative method for nozzle reinforcement design. This program change for applicable nozzle results in less required reinforcement than the traditional UG-37 and 1-7 code sections.
Typical example using the traditional reinforcement method:
Same example using the new appendix 1-10 design procedure:
Keywords: ASME 2010, Code, Nozzle reinforcement, appendix 1-10
References: None |
Problem Statement: How to Use Short vs Split INI Setting? | Solution: The short -vs- split .ini setting is used to weed out/speed up the decision making on split loads. The system uses this setting to decided if it should even spend time going through the clusters and clouds to look for a partner. In general, if your average station to station trip time is less than the shortvssplit setting (which is displayed in minutes with a default of 60 minutes) then some possible split load candidates may not be considered.
Here is an example of how it works:
Customer A Short Load = 30,000 liters
Customer A Trip Time= 2.0 hours
ShortvsSplit= 60 minutes
Truck Capacity = 40,000 liters
Truck Cost = $100 per hour
The optimizer will begin by looking at Customer A and realize it is a short load and do the following math:
Trip Time and cost of short load= 2.0 hours * 100 = $200
Trip Time and cost to shortest possible split = 3 hours (This time is generated by taking the round trip time plus the shortvssplit time) = 3 hours * 100= $300
Next the system compares the CPV
Short = $200/30,000 liters = .0067 CPV
Split = $300/ 40,000 liters = .0075 CPV
The system at this point will not look at any of the cluster or cloud partners because the system believes that it is cheaper to bring the short load as opposed to the shortest split load. Now of course if there are trip times in the clusters or clouds which are shorter than 60 minutes then the system has made the wrong discussion in this weeding out process and a cheaper split load could have been found. This is a setting that ways optimizer performance verses optimizer results. Generally, speaking you are going to want to have the shortvssplit setup at the average time between split partners. The time can be set as low as 1 minute and as high as 60 minutes. By lowering the number you will in some cases increase the chances that a split load is created but you will also increase the number of calculations the optimizer has to make which could in turn increase the time need to optimize.
Keywords:
References: None |
Problem Statement: How to prepare for Christmas Holidays | Solution: Using the Holiday Storm Ultility you can refernce the previous Christmas Holiday and use the sales history for the current Christmas season. If you have stations in your database that were not on the Aspen Retail system last Christmas season or if there are stations in your database that did not report sales information during the Christmas season, insert a default percentage in the specified default percentage field and check the 'Use default when needed' check box. The default percentage will be used to forecast the stations that did not exist or did not report sales information.
Keywords: Use default when needed
Holiday storm
References: None |
Problem Statement: How does Optimization Heuristic Logic work? | Solution: Aspen Retail Optimizer - Optimization Heuristic Logic
The Aspen optimization Heuristic is a completely custom Heuristic designed specifically to solve the fuel truck dispatch problem. It combines non-linear heuristic and recursive techniques to minimize the average cost per gallon delivered over its planning horizon.
Because of its non-linear and recursive nature, it is impossible to annotate the logic in such a way that a human could follow it through. However, it is possible give an overview of the rules it uses and the decisions it may make along the way to itsSolution.
Must Go Work vs. Can Go Work
Each load has a delivery window composed of the earliest and latest times the load may be delivered to the site. For inventory management accounts, these times are calculated; for order entry accounts, the window is given or based on the requested shift. The shift running times for each truck are setup. Delivery time restrictions for the customer, driving times, loading times, and unloading times are also setup. Given these parameters, the system determines for each load which delivery shifts can be utilized to perform the work. The system prioritizes doing work on a shift if the shift being optimized is the last shift (Must Go) on which the load can go satisfying all timing requirements.
If there is not enough Must Go work to fill out the shift, the system will look for Can Go work (work that can be done on the shift but can also be done on a future shift) to fill in the gaps.
Dedicated vs. Non-dedicated Resources
There are three main classifications of trucking resources that differentiate how variable trucking costs are expensed. First, there are trucks whose drivers are paid for the whole shift, whether or not the driver does a full shift's work. Second, there are trucks that are only paid by the load, but there is a minimum amount of work guaranteed to the truck once it is brought on-duty for the shift. Third, there are trucks that are paid by the load with no minimum. When utilizing these resources, the system will prioritize utilizing the trucks in the first case, then the second, and only use the third type if it makes economic sense or if there is too much Must Go work to be satisfied by the resources in the first two types.
Split Deliveries vs. Short Loads
It is possible to set up groups of customers known as Split Clusters. These are customers in close proximity that share deliveries as Split Deliveries if necessary. The system is able to determine the most cost effective method of delivering product to accounts that are unable to take the full truck load. In some cases, it is more economical to simply Short Load the truck rather than do a Split Delivery; likewise, in other cases, Split Deliveries pay. This calculation is based on the amount of the truck that could be accommodated as a Short Load and the additional cost of doing the Split Delivery due to increased driving and dropping time. When a customer is configured to be part of a Cluster, the system is able to make theses determinations for the customer automatically. For lone accounts, the system will list loads that should be paired into Split Deliveries to aide the user in a manual setup of Split Deliveries if desired. The overall goal of this determination is to minimize the cost per volume delivered.
Multi-Terminal Routing
It is often the case that a particular customer may be serviced by more than one terminal's fleet, or may receive product from more than one choice of sources. The system has the capability to automatically route all the work for a group of terminals simultaneously in order to take advantage of multiple supply points and a distributed fleet. The system endeavors to minimize the total cost of meeting all delivery requirements with available trucking assets. This may involve sending one terminal's truck over to another terminal to help out with an overflow of work, or simply taking advantage of alternate loading points to minimize driving distances and therefore the costs associated with driving time and distance.
Back Hauls
In some cases it is important to recognize the opportunity to manage a delivery en route to a destination, or on the way back in order to minimize empty driving miles which will help to lower overall delivery costs. The system will identify these opportunities and endeavor to make use of them in cases where they help lower the overall cost of theSolution.
Restrictions
Customers may not be able to receive deliveries during certain times of certain days. Customers may not be able to receive deliveries from certain types of trucks. Trucks may not be able to carry certain products or load at certain terminals. Customers may not be able to receive product from certain terminals or terminal's trucks. All of these constitute delivery restrictions that are automatically taken into account by the optimization Heuristic. The system will never automatically break a restriction rule, though the user may manually do so.
Overall Cost Minimization
Taking all factors into consideration including delivery windows, delivery restrictions, truck availability, cost information, routing times and distances, product availability, fixed costs, third party carriage rates, and customer volume requests, the system's goal is to find theSolution that will satisfy all factors at the lowest possible total cost. This involves maximizing the utilization of the trucking fleet, minimizing driving distances and times, putting the right load on the right mode of transportation, and maximizing the gallons delivered on each trip when it pays to do so. All of these secondary goals contribute toward overall cost minimization. The key is to balance the tradeoffs between them to achieve the optimal low-costSolution.
Keywords:
References: None |
Problem Statement: How do I edit the the user material database in Aspen Teams and add material properties? | Solution: Following are the instructions on how to add material properties to a new user-specified material record:
- Create a record in the private material file. You can use that private material number in BJT (or EDR) Teams files just like using a 'public' (not changeable) material number. The private material numbers are > 9000 (program default as well).
Aspen Teams accesses material properties through ASME material files, one for each year since 1998. The latest for version 2006 is ASME2006. The *.PDA files are located in \\...\DAT\PDA\ASMEYEAR. These files cannot be changed by the User.
If you want to use a material with different properties than the ones found in ASME YEAR (you can also enter a few material properties in the input file for a few components), the recommended way is to create a private material. The easiest way to do so is to copy from existing, but obsolete, material files. These properties are from the old ASME B-JAC database, the one the program used before using the ASME properties directly from ASME. These properties are from ~1999-2000).
- Use Tools > Data Maintenance > Material Database.
- Select Databank - ASME. Remember, this ASME databank is obsolete. It is only here to help the User enter private materials so you do not have to enter all properties from scratch.
- Find a similar material to the one you want to enter. For example, if you want to enter carbon steel 'plate' material, use SA-516 Gr 70 plate (number 1109) as the base.
- Scroll down on the left bottom window and double-click on material 1109.
- Click menu item Property > Copy then click Databank > User.
- Click Property > Paste then accept the next available 9000+ number.
- Change information on the left (material names in all 3 places, etc.).
- Select material property top right and change the data as required (allowable stress, etc.) on the lower right pane.
- Enter additional data as required and save record. The program will ask save yes or no when exiting or click the save button.
- Then use the 9000+ material as any other Teams materials in an input file.
There are 3 files affected by this action. These files need to be moved to the next version after the installation of a new program version.
1- MaterialDBIndex.mdb in the \DAT\MDB folder. This file shows the material name (changed by the User) in the input file in the material section.
2- N_PRIVI.PDA in the \DAT\PDA folder.
3- N_PRIVP.PDA in the \DAT\PDA folder.
These files contain the private material properties used by the calculation engine.
You will have to fill out additional details as you go through this procedure.
Keywords: Data base
References: None |
Problem Statement: MAWP (Maximum Allowable Working Pressure) is not calculated for the tubesheet, how can I fix it? | Solution: For exchangers in which the tubesheet is increased by the program for a non-code related reason, for example during the design of a TEMA type W rear head exchanger, the program does not go back to re-calculate the MAWP after changing the tubesheet thickness. For these cases enter the final tubesheet thickness in the input and then re-run the case to have the MAWP calculated based on the actual tubesheet thickness.
Keywords: MAWP, Tubesheet
References: None |
Problem Statement: When processing data exceptions I encountered a record where one the products exceeded the test range threshold percentage but it was not highlighted in red as an exception in the Data Quality Manager. Why? | Solution: Aspen Retail versions 7.2 and greater now include a volume test range on both sales and inventory records. In order for a record in the Data Quality Manger to be highlighted in red indicating an exception both the percentage and volume test range values have to be exceeded.
Keywords: Data Quality Manager
Exceptions
Product Setup
Volume Test Range
References: None |
Problem Statement: When performing the Aspen Data Source Architecture (ADSA) test using Web Service protocol, the following error message is received: Request Failed 401. | Solution: To resolve the above error message, change the ADSAWebService virtual directory to use Anonymous access.
Keywords: Access denied
References: None |
Problem Statement: Will load confirmation give a timestamp of when loaded and, if so, where will you find that? | Solution: Load confirmation has the ability to pass through one of three records. These records are
LOADED (place a V in the DELIVER STAT field)
DELIVER/CONFIRMED (place a C in the DELIVER STAT field)
DISPATCHED (place a D in the DELIVER STAT field)
Inside each record there are three fields called DELIVDATE, DELIVHOUR, DELIVMIN. These are the fields that will update the ETA time for the loads. If a load confirmation record is passed through to the system when the delivery is actually loaded, then the ETA time will reflect the loaded time. This ETA is always displayed inside the DELIVERY DETAIL screen, which is most commonly viewed through the replenishment planner but can also be viewed inside the optimizer.
Keywords: Load Confirmation
References: None |
Problem Statement: Is there a document that describes all of the ini file settings? | Solution: Yes, the attached document has a description of all the ini file settings for the PSOFT.ini and PSOFTG.ini files. For help with the IVR's INI files, please visit the support website's documentation area. The IVR documentation contains detailed descriptions of the Order.ini files.
Keywords:
References: None |
Problem Statement: From time to time we need to run all of our standards through ASME Code software in order to check them. Can TEAMS take input from an Excel spreadsheet and print output to a spreadsheet? | Solution: Yes, Teams is fully MS COM compliant meaning that all variables are exposed to the outside. Excel can call Teams in the background, pass variables into the input side and receive variables from the result side. Simple example files on the basics to do this are shown in default folder C:\Program Files\AspenTech\Aspen HTFS+ 2006\Xmp\VB. Please note that standards design may need some of the code cases that have been developed lately to deal with special situations, like simply supported tubesheets. Teams also includes these code cases.
Keywords: Excel, spreadsheet, ASME, input, output, example
References: None |
Problem Statement: How do orders get moved from the replenishment planner to the delivered loads log? | Solution: Forecasted accounts orders normally get moved from the replenishment planner to the delivered loads log during exception processing or data quality management. This is when the account gets forecasted and the system moves loads based on which loads it believes have been delivered because of an inventory oncrease. The system will base this on the following information:
if the customer reports both sales and inventory the system is looking for 70% of the load being delivered to flag it as delivered
if the customer only reports sales, then the system is looking at the ETA time to decide if a load is delivered or not.
Therefore it is definitely possible to have loads which have not been delivered move into the delivered loads. The following .ini setting printUnDelDispWarn=1 will print a warning to warnings manager if this situation occurs.
Keywords:
References: None |
Problem Statement: What are the possible data entries for the STATUS field in the TCIF_GROUP_STATUS | Solution: The status field in the Group Status table is a Char(1) field. It has the following possible data entries:
'U' Unscheduled/Untouched - The shift has not been touched.
'O' Optimized
'E' Exported
'D' Dispatched
Keywords:
References: None |
Problem Statement: How do you transfer data from Aspen Tasc+ to Aspen Teams? | Solution: To transfer data from Aspen Tasc+ to Aspen Teams, you need to have the geometry data in your Aspen Tasc+ file (simulation or rating mode). Then you need to execute the following steps:
1. Open the file in Aspen HTFS+ interface.
2. Go to Run menu and select Transfer.
3. In the window that will appear select Aspen Teams.
4. Check the Clean Up option if you have existing mechanical data already in the file and you changed the geometry in Aspen Tasc+. Otherwise, there is no need to check the clean up option (Clean up erases any previous geometry data in the mechanical section).
5. Click on the Aspen Teams icon in the tools bar.
6. Run your file in Aspen Teams (mechanical mode).
Keywords: TASC+; TEAMS; DATA Transfer
References: None |
Problem Statement: Where does the Forecaster reside and how do I change its settings? | Solution: The forecaster usually resides in the same directory as the other Aspen Retail applications and is called Forecast.exe.
The settings for the forecaster are contained in the psoftg.ini file:
[Forecast]
StartTime=600
StopTime=2300
Period=2
idcode=1
timer=0
In the above example, Start and StopTime represent the times the forecaster will operate, in military (24 hour clock) time. Period represents how often the forecaster will run in minutes - in this case the forecaster will run every 2 minutes. The idcode is currently a static value, so leave it set equal to one. The timer is the frequency, in minutes, that the forecaster will write to the AppStatus table - in this case the feature is disabled by setting timer equal to 0. This feature is useful in debugging forecaster problems at implementation time. In the production mode, most users leave it set equal to zero.
There are no default values, so the forecast parameters should always be set in the psoftg.ini file
Keywords:
References: None |
Problem Statement: If there is no ADSA license in your license file, should you be concerned? | Solution: There is no license specific to ADSA since AspenTech does not sell ADSA as a separate standalone product. It is a service that is used by other products in the Manufacturing Suite that are licensed.
When installing the Aspen Manufacturing products, the ADSA server option will be available when using the Server Install option. It will not be available when using the Standard Install option.
Keywords: ADSA
license
References: None |
Problem Statement: What are the different types of Costs inside Aspen Retail? How do they work? | Solution: Also see the attached document with screen shots
TERMINAL SETUPCOSTS
MONTHLY FIXED COSTS- the monthly fixed costs inside the terminal setup screen is a combination of all fixed costs that are associated with a terminal. Here is a short list of examples of common fixed costs, monthly rent, depreciation expense, overhead, and electricity. The above list is only a few of the costs that can be aggregated into a monthly fixed cost number any cost that is fixed or standard over a period of a month and should be included in the total delivery costs can be included. The fixed cost is then divided by the number of shifts in the month and a proportion of the cost is allocated to each shift.
EXAMPLE:
MONTHLY FIXED COST NUMBER = $45,000.00
DAYS IN THE MONTH= 31
SHIFTS IN A DAY= 62
TOTAL ALLOCATED TO EACH SHIFT= $45,000.00/62 = $725.81 per shift.
Since these costs are fixed costs, changing the fixed costs at terminals will not affect the optimization results.
PRODUCT COST- Aspen Retail allows users to enter the product costs for each individual product inside the terminal setup. The product costs are only factored into the optimization if a best buy model is setup inside the database. If the best buy model is not setup correctly (i.e. suppliers, replacement products, best buy on at the customer level, etc.), these costs will not be factored into the optimization. If the best model is correctly setup, the optimization will consider both transportation costs and product costs when optimizing. In the best buy model, the product costs is a variable cost. Therefore changing the product cost at different suppliers can affect the optimization results.
Note that only New Price is used when optimizing. Old Price is a reference field only.
CUSTOMER SETUP COSTS
CARRIER FIXED & CARRIER COST TYPE- The carrier fixed cost and carrier cost types are used by the system to cost out loads inside overflow and loads that are not assigned to a truck. These costs type should represent the costs of a load on a point-to-point hauler or a will call hauler scenario that would need to be used if there is not enough truck capacity available. For example, if you have (6) loads that have to go out on a truck but only (5) loads will fit on that truck, the software will use the carrier cost or the carrier fixed cost to decide which load to place into overflow. Which load to be put in overflow is a function of the over flow expense - the load with the cheapest overflow cost is put into overflow. Changes to these cost types will directly affect the optimization result if all of the loads cannot be placed on trucks. Note that carrier fixed cost and carrier cost type are mutually exclusive.
Additionally, the carrier cost type and carrier fixed cost are also used in the scorecard to calculate the BOTTOMLINE OPERATING PROFIT number. In order to calculate this number, the system costs every load out using the carrier cost type or carrier fixed cost numbers and then compares that to the actual costs of the loads as dispatched.
FOR EXAMPLE: If we have a 2 hour load to be placed on a truck that costs $10 per hour, the actually cost is $20 dollars (2 hrs x $10) for delivery. If the customer has a carrier fixed cost setup of $25 at the station level, then the OPERATING PROFIT is $5, which is what is saved by not using a market carrier (i.e. will call carrier or point-to-point carrier).
TRUCK SETUP COSTS- Truck costs can be made up of 1,2 or 3 cost types and they are labor cost, overtime cost, and operating costs. Each of these costs types have the same basic data and format. The discussion below is based on labor costs but the information applies to all three.
Cost per Hours- equals hourly cost that is associated with a truck.
EXAMPLE- COST PER HOUR IS $10 TRUCK WORKS 8 HOURS TRUCK COST = $10.00 X 8= $80.00
Minimum Hours- is a per load minimum hours. The system will automatically use this minimum amount if the round trip time for an order is less than it.
EXAMPLE- MINIMUM HOURS IS 3 DISPATCHER PLACES A 1-HOUR LOAD ON THIS TRUCK.
TRUCK COST WILL EQUAL 3 X $10.00 = $30.00
TRUCK WILL NOT EQUAL 1 X $ 10.00 = $10.00 BECAUSE OF THE 3 HOUR MINIMUM
Cost Per Distance - equals per distance charge for truck (i.e. KM or MILES).
EXAMPLE- COST PER DISTANCE IS .10 CENTS TRUCK DRIVES 100 KM
TRUCK COST= .10 X 100 = $10.00
Minimum Distance- is a per load minimum distance. The system will automatically use this distance if the actual distance is less than it.
EXAMPLE- MINIMUM DISTANCE IS 50 KM ACTUAL DISTANCE IS 30KM
TRUCK COST WILL EQUAL 50 X .10 = $5.00
TRUCK WILL NOT EQUAL 30 X .10 = $3.00 BECAUSE OF THE 50 KM MINIMUM DISTANCE
Cost Volume Chart- is the cost per unit of a product to be delivered over a certain distance.
EXAMPLE
1-10 KM = .05 per liter
11-20KM= .10 per liter
TRIP = 15 KM and 40,000 liters
COST= 40,000 liters X .10 = $4,000.00
TRIP = 5 KM and 35,000 liters
COST= 35,000 liters X .05 = $1750.00
Point to Point Costs- cost volume charts that can be setup for particular customers.
All of the above costs are types that can be setup inside Labor costs, Overtime Costs and Operating Costs. The sum total of these costs should represent the total costs to deliver loads on the truck. These costs are variable costs and can have significant impact on the optimization results.
Keywords:
References: None |
Problem Statement: Using the AFW Security Manager, you may assign Windows Active Directories as members of roles; however, Aspen Local Security is not able to access the members of the active directories. | Solution: Run AFW Tools on the Aspen Local Security Server and verify the key NTGroupSupport is set to 1.
If NTGroupSupport equals 0, the AFW Security Client Service will not attempt to enumerate the members of Windows Active Directories.
To change the value of the key, double-click on the key, change the value to 1, and press OK.
Finally, restart the AFW Security Client Service on the Aspen Local Security server.
Keywords:
References: None |
Problem Statement: 1. How does the cache for ADSA get updated?
2. Is it possible for the cache not to match the data sources on the server?
3. What is the best way to force a refresh of the cache? | Solution: Answer to #1:
The ADSA cache works like this:
1. An application makes a call on the ADSA locator.
2. The ADSA locator reads the cache (if there is one) including the timestamp associated with the cache.
3. The ADSA locator calls the ADSA server passing the timestamp of the cache.
4. The ADSA server compares the timestamp passed in the call with the last modification timestamp of the ADSA data sources.
5. If the timestamps match, it returns a status code indicating that there are no changes. The ADSA locator returns data sources from the cache to the application.
6. If the timestamps don't match, the ADSA server returns the new list of data sources including the last modification timestamp. The ADSA locator stores the new data sources and timestamp in the cache and returns the data source to the application.
7. If the call to the server fails for any reason (such as security or network failure), the ADSA locator returns the data sources from the cache.
Answer to #2:
The only two ways for the cache not to match the data sources on the server are:
1. If the data sources are modified in the registry of the ADSA server without updating the last modification timestamp. The ADSA Config tool always sets this timestamp, so this would have to be a direct modification of the registry either by the users or a program. To verify that the ADSA is pointing to the proper directory server host name, open the Windows Registry editor and search for all occurrences of the DirectoryHost key to make sure that all occurrences of this key are set to the proper directory server host name.
2. If the application hasn't successfully called the ADSA Server since the data sources have been updated. Either the application hasn't called the ADSA Server or the call failed for some reason such as security or network failure.
Answer to #3:
The best way to force a refresh of the cache is to delete the <server> (and children) components of the following registry keys:
<HKEY_CURRENT_USER>\Software\AspenTech\ADSA\Caches\<server>\<user>\<datasource>
and
<HKEY_USERS\.DEFAULT\Software\AspenTech\ADSA\Caches>
and restart the ADSA service and any other service affected by the ADSA cache update. The ADSA cache will now refresh with all the configured datasources.
Key Words
Web Server Establishing DB Links...
No Servers Available
Keywords: None
References: None |
Problem Statement: How Many server connections does Aspen Retail Require? | Solution: The number of connections at any one time depends on the features installed and how many users are accessing them. Here are some guidelines
IVR (voice Recognition):
One connection for the system, and one connection for each outside line
Service Connections:
Two database connections for each service
User Connections:
Two connections for each screen each end-user opens (Customer setup, Data Quality, etc)
For example, in an installation with:
10 IVR lines 11 connections
3 Services 8 connections
5 End Users with 4 open screens 40 connections
For a total of 59 connections.
Note: End Users can occupy as many as 12 connections
Keywords:
References: None |
Problem Statement: I have a supply issue with diesel. Would like to view pending RSO and ASR orders to evaluate demand. | Solution: If you have access to AR's tables, go to the TPS_orders table and query by the date, shift, and product, whatever parameter will give you your desired results. If not use the predefined reports available in Aspen retail. From the main AR GUI click on File, print reports and select one of the following.
Terminal orders by Customer/Day
Terminal orders by Retain/Date
Terminal orders by Runout/Date
Terminal orders by Shift
Use in conjunction with the Days Supply report for ASR customers to aid in determining prioritization.
Keywords: Reports
References: None |
Problem Statement: Can the manual sales and/or inventory import (under the Utilities pull-down menu) be done while customers are in process? | Solution: Unlike the automated sales and inventory procedure (SIIMPORT), the manual imports of sales and inventory do not use Aspen Retail's in-process flagging capabilities. When the in-process checking is disabled, duplicate orders can be produced.
If you plan to use the manual importing feature for sales and/or inventory, you should make all users log off the system until the import is completed.
The SIIMPORT service does respect in-process customers and will wait to update their inventory until the customer is no longer in use by another user.
Keywords:
References: None |
Problem Statement: Can the IOPACKAGE.sql procedure be used to improve the performance of the Aspen Retail graphical user interface? | Solution: No, the IOPACKAGE was intended to speed the SQL searches in the Link and Exchange services only. To activate the IOPACKAGE for the Link and Exchange services, first install the IOPACKAGE and then add UseSP=1 to the setup section of the PSOFT.ini.
Note: You can also have this qualifier in the PSOFTG.ini and the GUI will attempt to use it. If you enable the IOPACKAGE similarly in the PSOFTG.ini file, you will receive several nasty ODBC errors. Should this happen, edit your PSOFTG.ini file and either remove the line that says UseSP=1 or modify the line to UseSP=0 (the default).
Keywords:
References: None |
Problem Statement: ADSA clients cannot connect to the ADSA server. The Test button in the ADSA Client tool returns the error:
The specified Windows NT host is not a member of a trusted domain, and the security settings of the current process do not permit such connections. | Solution: This is a common error when the ADSA server is installed on a Windows 2003 operating system. ADSA uses DCOM to communicate to the ADSA server. However, in Windows 2003, the DCOM settings are restricted by default.
? The following steps detail how to edit the default settings on the ADSA server so clients can make DCOM connections:
1. Start Control Panel
2. Select Administrative Tools
3. Select Component Services
4. Expand Component Services
5. Expand Computers
6. Right-click My Computer and select Properties
7. Select the Default COM Security tab
8. Click the Edit Limits button for Access Permissions. Client accounts must be granted Remote Access through a user account or domain group, such as the EVERYONE group.
9. Click the Edit Limits button for Launch and Activation Permissions. Client accounts must be granted Remote Access through a user account or domain group, such as the EVERYONE group.
An alternative is to put the desired users in the Distributed COM Users group.
This is a new local group on Windows 2003 Server systems. Using the group rather than the DCOM permissions directly allows for easier maintenance (i.e. updating users in a group versus changing application permissions).
Here is link to a Microsoft Technet article that describes the new group for Windows 2003 SP1: DCOM Security Enhancements
Keywords: None
References: None |
Problem Statement: Explain result of not defining all three cost types in transport setup. Explain how maximum transport/truck utilisation can be achieved. Explain how to improve proportion of empty versus loaded trips. Explain simultaneous use of volume cost and cost per distance options. | Solution: Q1) There are 3 different Truck Cost Types (Labour, Overtime & Operating). Is it necessary to use all of them? What Retail will do if, for example, only Labor cost type is defined but Overtime and Operating costs are not set up (e.g. left blank)?
The three different cost types are linked with the status of the truck (Guaranteed or Bill by shipment). Based on this status, Retail will take other costs into considerations.
Example 1: You pay your drivers for the full shift. So even if they work only 6 hours, you will still have to pay them for the full shift (assume 12 hours in this example). Besides this, your trucks have a variable cost per distance (fuel, tyres, oil). For this example you would set up a Labour cost type where you define only a Cost per hour. Next to that you also have to set up an operating cost type where you define only a cost per distance. At the same time you set up your truck as Guaranteed so that Retail will recognize that you have to pay your drivers for the full shift. So for this example you have to set up 2 Cost types and change the status into Guaranteed.
Example 2 : Occasionally, you have to use spot trucks in peak periods. The carrier is charging you a fixed cost plus a Cost per volume chart. For this example, you can set up only one cost type where you define a CPV chart and the fixed cost under the Operating Cost type. Then you make the truck Bill by shipment.
In addition, the system does not require that all cost types are filled in and can function properly with (1) out of the (3) cost types setup. There are a couple of precautions that need to be taken. First Overtime cost is only used when a truck is working overtime so if a truck is only set up with an overtime cost type the truck will not function properly if the truck is not labelled as overtime. It is recommended that all trucks are setup with either an operating cost or a labour cost type. Secondly, it is important to place some costs in overtime cost if you are using a labour costs. If there is no cost inside the overtime field and you place more work on the truck than it is schedule for the system will think the extra work is free.
Q2) How can Retail be encouraged to maximize utilization of the trucks, e.g.:
Use as much working hours from the available as possible, or
Use as much of loading capacity of the trucks as possible, or
Combination of above two options?
A2) Concerning truck utilization, the best option would be to employ the Guaranteed status on a truck. If a truck is marked guaranteed the system realizes that the truck must be used each shift and that the cost incurred with the truck are incurred if the truck is used or not used. If not enough must-go work can be found, Retail will go and look for can-go work up till the point where all the available hours are used. It is even possible that Retail would create can-go splits to better utilize the available truck time. If a truck is bill by shipment there is no penalty in only using 50 % of the available truck time.
Concerning loading capacity, you would normally use the fill lines. If the minimum quantity a truck can load would be 30.000 litres, you make sure that your smallest fill line equals this quantity. The weight opt 3 option can cause Retail to go below this 30.000 litres. Furthermore, that can be controlled by setting the X and Y values correctly in the ini file.
On every forecasted customer you can also set up a minimum and/or maximum shipment size. These fields can be found in the Restriction screen of the customer setup option. The Load Size Restrictions establish minimum and maximum payload quantities for delivery to a specific customer. The minimum Load Size Restrictions value is a lower limit for sizing down a shipment. For example, an entry of 5000 litres will not allow a forecasted shipment for a specific customer to be less than 5000 litres. An entry of zero means no restriction exists.
Q3) Is it possible to force the system to improve proportion of loaded distance versus an empty run? If yes, what's the best/easiest way we can achieve that?
A3)
Let's assume that we have one full load. If best buy is NOT activated, Retail will look at trip time (not distance) to find the closest terminal. Let's assume once again that there is a truck available to deliver the load (fill levels, start time, restrictions, product availability, etc?). Once the truck delivered the load to the station, it has a couple of choices. One would be to go back to his original terminal and incur the empty kilometres that are linked with this.
AnotherSolution would be to load at another terminal based on the location of the next load(s). If this result is desired, it is best not to switch on the source lock or build in loading restrictions. This would imply that a station can be delivered out of all terminals in the group. This approach could reduce the number of empty kilometres but it requires a lot more flexibility on the terminal level.
Another way to reduce the empty kilometres would be the use of remote truck stops. Truck stops can be considered as parking where trucks are parked but no product can be loaded. At the end of the day, trucks return to the truck stop. If the distance from the last drop to the truck stop is less than the distance to the terminal, you can reduce the number of empty kilometres.
Q4) Can both the Cost per Distance AND Volume Cost Chart be used at the same time? What are the expected results of using both ?
A4) Please refer to the table in Q1. In this table you see that you can use Cost per distance and Volume Cost Chart at the same time in a couple of combinations. First possibility is Operating cost for a Guaranteed truck, second one is Labor Cost for a Bill by shipment truck and finally operating cost for Bill by shipment truck. Cost per volume charts and point-to-point costs cannot be used at the same time.
A big difference between both cost structures is that fact that the Cost per volume chart is based on Volume where the cost per distance is of course based on distance. This makes them very difficult to compare. Perhaps an example can help here.
Assume that I have one truck that only has a cost per distance of 1 dollar. The other truck has got a Cost per volume chart that looks like this.
Distance
0-50 0,002
51-100 0,003
101-200 0,004
CPV
Assume that we
have a load for 35.000 liters and the distance to the terminal is 54 km one way.
If we would send truck 1 (only cost per distance) this load would cost us : 108 km x 1= 108 dollar. If we would send truck 2 with the CPV chart, the same load would cost us : 35.000 liters x 0,004 = 140 dollar.
In this case, Retail should take truck 1 to bring the load to the station (assumption is that trucks have the same fill levels).
Now assume that the next time we are going to this station, the load is only 20.000 liters. If we would send truck 1 (only cost per distance) this load would cost us : 108 km x 1= 108 dollar. If we would send truck 2 with the CPV chart, the same load would cost us : 20.000 liters x 0,004 = 80 dollar.
So now, truck 2 is cheaper and will be selected.
Keywords: transport cost types
overtime cost
labor cost
operating cost
guaranteed
bill by shipment
truck utilization
transport utilization
empty truck
cost per distance
volume cost
References: None |
Problem Statement: I am confused between the input of both the nozzle and coupling under Exchanger Geometry/Nozzles-General. The coupling I am trying to define is a size (in NPT) for the nozzle by itself and also specify that it is attached to a larger nozzle diameter. Is there any error with the input of this data inside Aspen TEAMS? | Solution: Unfortunately, the Aspen TEAMS program does not have the capability to handle couplings on nozzles. The program assumes that the couplings entered will be located on the vessel itself, not the nozzle.
Keywords: TEAMS, nozzle, coupling
References: None |
Problem Statement: Is the RETBUFHR field still used in the STATIONS table? | Solution: The RETBUFHRs field is not used any longer - it was replaced by the DAYBUFFER and NITBUFFERS. Our upgrade scripts now map that translation.
Keywords: Retain Buffer
RETBUFHR
DAYBUFFER
NITBUFFER
References: None |
Problem Statement: How to add a new user for IVR login? | Solution: See the attached document
Keywords: IVR
New User
Add
References: None |
Problem Statement: </u></b>
How can one push the Retail system to maximize utilization of the trucks, e.g.:
Use as much working hours from the available as possible, or
Use as much of loading capacity of the trucks as possible, or
Combination of above two options?
<b><u> | Solution: </u></b>
Concerning truck utilization, the best option would be the guaranteed status on a truck (First make sure that all of the trucks that are required to be used each shift are marked guaranteed.) Once you set this up, Retail will try to use all the available hours on the shift. If not enough must go work can be found, Retail will go and look for can go work up till the point where all the available hours are used. It is even possible that Retail creates can-go splits to better utilize the available truck time. If a truck is bill by shipment there is no penalty in only using 50 % of the available truck time.
If a truck is marked guaranteed, Retail knows that the truck must be used each shift and that the cost incurred with the truck are incurred regardless if the truck is used or not used. For guaranteed trucks it is recommended that a labor cost type by hour be set up. If these two parameters are setup the system is going to try and use these trucks. Sometimes, a lot of the work is going to overflow. When loads get to overflow while there are still guaranteed trucks that are not used to capacity, then one needs to find out why the load is not going on the truck and why it is going to overflow. Sometimes, it is a case where the ordered quantities do not fit on any of the fill levels set up on the truck. Therefore this under utilization of trucks is not tied to any cost types. Concerning loading capacity, you would normally use the fill lines. If the minimum quantity a truck can load would be 30.000 liters, you make sure that your smallest fill line equals this quantity. In the case of MOL, the weight opt 3 can cause Retail to go below this 30.000 liters. Even that can be controlled by setting the X and Y values correctly in the ini file.
On every forecasted customer you can also set up a minimum and/or maximum shipment size. In our case, you would be interested in a minimum shipment size. You can find these fields in the Restriction screen of the customers.
Extract from User guide :
The load size restrictions establish minimum and maximum payload quantities for delivery to a specific customer. The minimum Load Size Restrictions value is a lower limit for sizing down a shipment. For example, an entry of 5000 liters will not allow a forecasted shipment for a specific customer to be less than 5000 liters. An entry of zero means no restriction exists.
<b><u>KeyWords</u></b>
Keywords: None
References: None |
Problem Statement: Can One use both Cost per Distance AND Volume Cost Chart at the Same Time? What Is the Effect of Using Both? | Solution: Both cost volume chart and cost per distance can be used. The net affect of this is simply a double charging per kilometer The system would simply charge the COST PER VOLUME rate to the load and then add in any additional per kilometer fee.
You can use Cost per distance and Volume Cost Chart at the same time in a couple of combinations. First possibility is Operating cost for a Guaranteed truck, second one is Labor Cost for a Bill by shipment truck and finally operating cost for Bill by shipment truck. Cost per volume charts and point-to-point costs cannot be used at the same time.
A big difference between both cost structures is the fact that the Cost per volume chart is based on Volume where the cost per distance is of course based on distance. This makes them very difficult to compare. Perhaps an example can help here.
Assume you have one truck that only has a cost per distance of 1 dollar. The other truck has got a Cost per volume chart that looks like this.
Distance CPV
0-50 0,002
51-100 0,003
101-200 0,004
Assume that we have a load for 35.000 liters and the distance to the terminal is 54 km one way. If we would send truck 1 (only cost per distance) this load would cost us : 108 km x 1= 108 dollar. If we would send truck 2 with the CPV chart, the same load would cost us : 35.000 liters x 0,004 = 140 dollar.
In this case, Retail should take truck 1 to bring the load to the station (assumption is that trucks have the same fill levels).
Now assume that the next time we are going to this station, the load is only 20.000 liters. If we would send truck 1 (only cost per distance) this load would cost us : 108 km x 1= 108 dollar. If we would send truck 2 with the CPV chart, the same load would cost us : 20.000 liters x 0,004 = 80 dollar.
So now, truck 2 is cheaper and will be selected.
Keywords:
References: None |
Problem Statement: What are some of causes that prevent the Retail application from getting the license to run? | Solution: Cause:
COMLicenseMgr.exe has not been registered into the PC Registry.Solutions:
Register COMLicenseMgr.exe by double clicking on the filename: COMLicenseMgr.exe
Cause:
It has been found that on a Windows 2000 station, if any of the Retail NT Services is running in the background and then the user tries to run the interactive Retail application, the Retail application will fail to get the license.Solutions:
Stop all the running NT Services, if any.
At the DOS prompt, invoke DCOMCNFG.EXE. The following Distributed COM Configuration Properties dialog box appears. If it prompts you to register any unregistered components, click Yes.
Reconfigure COMLicenseMgrObj Class as follow:
Go to Distibuted COM Configuration Properties
Under applications select COMLicenseMgrObj Class, click Properties button. The COMLicenseMgrObj Class Properties dialog box appears. Click Identity tab | The interactive user radio button | OK. Close down the Distributed COM Configuration Properties dialog box.
Cause:
The date and time of the PC were set backward. The license server will detect it and causes the license checkout to fail.Solutions:
Set the date and time to the current date and time.
Cause:
The Aspen_License_File key in the registery is outdated. AspenSelector.exe does not work properly because the key value:
ASPEN_LICENSE_FILE:REG_SZ:??
(the right side window of the Registry) is still in the Registry: HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License ManagerSolutions:
At the DOS prompt, invoke Regedt32.exe to delete ASPEN_LICENSE_FILE:REG_SZ:?? key value.
Cause:
The AspenSelector.exe cannot start when being double clicked on. The user will get an error message Component 'comdlg32.ocx' or one of its dependencies not correctly registered a file is missing or invalid. This means that the PC that AspenSelector.exe is running on does not have or have an outdated version.Solution
Copy comdlg32.ocx from another machine that has the same operating systems (NT or Windows 2000). Put this file in:
WINNT\System32 (for both NT and Windows 2000)
Cause:
The AspenSelector.exe is pointing to the wrong license server or license file.Solution
Make sure that:
The license server is up and running.
The license server node name is typed in correctly.
The license file and its path are typed in correct.
Cause:
Sample license file content:
SERVER host_name Any
VENDOR aspen
USE_SERVER
FEATURE manschd aspen 11 10-sep-2001 9000 ck=188 SIGN=B9F94BA85424
FEATURE manorder aspen 11 10-sep-2001 9000 ck=221 SIGN=84E3C264DC52
FEATURE linkexch aspen 11 10-sep-2001 9000 ck=195 SIGN=F2B222E42512
FEATURE aspenretail aspen 11 10-sep-2001 9000 \
VENDOR_STRING=MAX_TRUCKS=0,MAX_QUANTITY=27440,MAX_STATIONS=0 \ck=182 SIGN=7659E2006766
#NOTE: You can edit the hostname on the server line (1st arg).
# The (optional) daemon-path on the VENDOR line (2nd arg).
# Most other changes will invalidate this license.
Solution
Make sure the host_name in the first line is replaced with the actual license server node name.
Keywords: License Manager
References: None |
Problem Statement: When manually creating a split load, the retain date and time don't change when altering the order quantities after the add function. In the former release when adding volume to the truck, one immediately saw the effect of changing quantities to the retain date and time. | Solution: Problem fixed in ver 7.03.01.02
Keywords: Retain date
split load
References: None |
Problem Statement: What does the expected sales value represent inside Aspen Fleet Optimizer? | Solution: These figures represent Fleet Optimizer's calculated estimate of sales for the previous 24-hour period. Expected sales are compared with actual reported sales (Yesterday's Sales) to identify erroneous sales reported by the Customer. As a backup, Fleet Optimizer utilizes average sales as expected sales if historical sales information is not available to generate expected sales values.
Keywords: None
References: None |
Problem Statement: The system creates splits with two manual customers, or with a manual customer and a forecasted customer to one truck. This is normal system behavior.
But what if the system puts in the same split a manual customer order for the current day together with a shipment for a forecasted customer which is running out 4 or 8 days later?
Is it normal behavior to create such splits? | Solution: You may expect that the system creates a split only with forecasted and manual customers having very close run out dates.
In versions 7.7.1 a new feature was introduced, the Split Creation INI Setting, which allows the user to manage the creation of split deliveries within RSO: the maxSplitRunoutDatesDiff setting, located in the [winopt] section of the Internal.ini file, will act as a restriction during the split delivery creation.
Its default value is 8, which means that the difference of runouts of split partners shouldn't be more than 8 shifts. By lowering this number, the stations will run out closer together.
You can for example reduce this value to 2 or 3 (shifts).
Keywords: SPLIT DELIVERIES
INI SETTINGS
TRANSPORTATION SCHEDULING OPTIMIZER
RESOURCE SCHEDULING OPTIMIZER
PARAMETERS
References: None |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.