question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
|---|---|
Problem Statement: In the orders table there is a field named delivered. If you look in the data for some one that is currently using the system, you see several different numbers in this field (ex 0,1,2,8). | Solution: Below is the explanation of each number:
0 = Expected
2 = Dispatched
3 = Dispatched late
4 = Loaded
5 = Loaded Late
9 = Late
10 = Delivered
11 = Delivered late
12 = Delivered Partial
Keywords: Retail
Orders
Delivered
References: None |
Problem Statement: What are main alogorithm and heuristics in Aspen Retail? | Solution: The Aspen Retail product has one algorithm and three heuristics that together solve the problem of retail petroleum distribution:
There is a demand forecasting algorithm that creates sales forecasts based on a trailing four week historical database for each product at a gas station. This algorithm is optimized for speed, since it is run extremely often for many data points. It uses a combination of weekly curve fitting and weighted day of week forecasting to come up with its future predictions. It also uses standard deviation analysis to weed out data outliers. We have tools and utilities that allow users to override and adjust these predictions.
There is an order generation heuristic that generates optimal order quantities for each delivered site. This heuristic uses the demand forecast from item #1 above and tries to a) match future delivery quantities to future sales proportionality ratios b) match future delivery quantities to truck compartment constraints c) match future delivery quantities to storage capacity constraints. The balance of these three priorities gives the optimal order.
There is a split trip generation heuristic that creates optimal delivery trip partners based on pre-assigned groupings. This heuristic deals with the problem that many delivery sites cannot take full truckloads of product and need to be partnered with others during a truck trip. We use pre-assigned groupings called clusters to shorten the search time since most good split partner candidates are known and can be set up in advance (we also have a mapping tool that will do this automatically). The heuristic here trades off the constraints of excess travel time created by doing split deliveries (extra unloads, extra in-between trips), carrying costs, and the cost of driving partially empty trucks (as in short loads). It looks to put together trips that will give an overall lowest cost per delivered volume.
Finally, there is a resource scheduling heuristic that aims to automatically build a schedule for a fleet of trucks that has the lowest overall cost per delivered volume. In general, this heuristic uses a multi-pass approach to building a schedule. First, the available orders are grouped by must-go/can-go, by preferred product source, and by preferred truck grouping (which equates to size of the vehicle in a heterogeneous fleet). Next, the orders are prioritized by flexibility, which is defined by the delivery window and the trip time of the order. A first pass at the schedule is created according to the above prioritizations. A second and third pass at the schedule aim to fill gaps, minimize transportation expense, and utilize truck shift time optimally. The heuristic is forward-looking, since it looks at the near future to make sure that it is not sacrificing future schedules to improve the immediate future.
All of these methods are proprietary and are developed from an operations research project that began at Stanford University in 1989 and evolved over the past 11 years with the requirements and real-world constraints found at over 30 oil companies.
Please note that no LP-based technology can solve this problem with the granularity found within Aspen Retail. Aspen Retail is designed to give a scheduler an automated answer which includes delivery quantities, delivery windows, and truck schedules to the granularity of a minute. This schedule can immediately be implemented and allows a scheduler to be more productive by several orders of magnitude. A schedule generated from an LP will give a sourcing plan, but with less granularity and with a much larger need for data massaging and interpretation by a manual scheduler.
Keywords:
References: None |
Problem Statement: Does Aspen Retail store terminal throughput information? | Solution: formation can be obtained from the TPS_COSTHIST table. The table stores this information by carrier and by owned transports. The information just need to be added together to obtain the throughput.
Keywords: Terminal throughput
References: None |
Problem Statement: Is there a limit to the number of splits that are created during automatic split creation? | Solution: MaxRecursiveSplit =6 (Default)
The maximum number of orders into which a load can be split during automatic split creation
Acceptable Values: 1- 10 (6 = Default, recommended)
Use:
This setting can be used to improve system performance because it limits the number of splits, and therefore, the
number of calculations the system must compute, during automatic split creation
Example:
To limit the number of split loads created during automatic split load creation to four split loads, set
MaxRecursiveSplit=4
Key words
Number of splits
Keywords: None
References: None |
Problem Statement: How do I create a global region in global optimizer? | Solution: A Global Region consists of a group of terminals to consider for Global Optimization. Before running a Global Optimization you must create a global region within which the optimization can be performed. Use these steps to create a new global region. From the Aspen Retail main dialog box, select Utilities | Global Region. The Select Global Region ID dialog box appears.
In the Global Region dialog box, click the New Global Region button and enter a Global Region ID in the Add Global Region dialog box. The ID must be numeric and can contain up to 10 digits. Enter a Global Region Name. The name can be alphanumeric and contain up to 30 characters.
Keywords:
References: None |
Problem Statement: What does Variance represent in the Data Quality Manager? | Solution: In Data Quality Manager, the Inventory Variance represents a percentage (%) difference between expected inventory levels and actual reported inventory levels. An inventory variance is displayed when sales & inventory forecasting is used.
Key words
Variance
Keywords: None
References: None |
Problem Statement: What causes the system to not allow shift '3' to be sent? | Solution: In order to be able to export a load in the replenishment planner the shift that you are trying to export the load on must have already been dispatched through the optimizer if it is not the system will not allow the order to be exported. The system stores the status of the shifts inside the TCIF_GROUP status table. In order for a load to be exported thru the replenishment planner the status for that shift must be (E) or exported.
Keywords: Shift 3
emergency orders
References: None |
Problem Statement: What does terminal supply point change when a terminal is changed from one group to another? | Solution: The reason is that you are using best buy for these groups. The original group only has one terminal in it. So there is only one supply choice. But when the terminal is changed to a new group, the new group may have several terminals, which gives the optimizer additional choices as supply points. When the optimizer is re-loaded, one of the functions it does is to run best buy. This is why the shipments are changing. To eliminate this from happening, prior to saving the optimization, the dispatcher can lock the suppliers. This is located under the optimize heading in the optimizer.
Keywords: Best Buy
Supplier
Optimizer
References: None |
Problem Statement: Aspen Retail 2006 and SQL Compatibility | Solution: Are named instances supported by Aspen Retail 2006? YES
Is Aspen Retail 2006 supported under SQL 2005 running in 2000 mode? YES
FYI: make sure to specify servername/instancename when creating ODBC. A common mistake is to specify only servername because the ODBC wizard wording is server:
Keywords:
References: None |
Problem Statement: How do I configue DoTruckChiselInFinalPhase in the INI file? | Solution: DoTruckChiselInFinalPhase =1(Default)
The Truck Chisel algorithm runs after orders have been scheduled on transports. It attempts to optimize shipments by reassigning orders to alternate transports. It ensures that:
The load for an alternate transport is optimally loaded
The original transport for an order is available for orders with a potentially longer trip time orders
The goal of this option is to create additional time on transport in order to deliver overflow orders. This
setting is used to limit the execution of the Truck Chisel algorithm to the final phase, thereby in
increasing the speed of the optimization process
Acceptable Values:
0 = Do not execute the Truck Chisel algorithm in the final phase of the optimization process
1 = (Default) Executes the Truck Chisel algorithm in the final phase of the optimization process
Use: See DoTruckChiselInFirstPhase above
Examples:
To have the Truck Chisel algorithm run in the final phase only, set:
DoTruckChiselInFirstPhase = 0
DoTruckChiselInFinalPhase = 1
To have the Truck Chisel algorithm run in the first phase only, set:
DoTruckChiselInFirstPhase = 1
DoTruckChiselInFinalPhase = 0
To have the Truck Chisel algorithm run in both phases, set:
DoTruckChiselInFirstPhase = 1
DoTruckChiselInFinalPhase = 1
Keywords: INI File
References: None |
Problem Statement: How do I configure the MinSplitDeliveryWindow INI Setting? | Solution: MinSplitDeliveryWindow = 5 (default)
This option allows you to set up the minimum delivery window (in hours) that the system will respect when creating split deliveries. If the delivery window for an order is less than the MinSplitDeliveryWindow value, the system will consider the order as a split load candidate
Acceptable Values: any number of hours you want to set as the minimum delivery window
Use: You can increase or decrease the amount of split loads that the system creates by increasing or decreasing this value. Increasing this value will increase the number of split loads; decreasing this value will decrease the number of split loads
Key words
INI Files
MinSplitDeliveryWindow
Keywords: None
References: None |
Problem Statement: There is the same order number in the TPS_ORDER table multiple times. | Solution: In the tps_orders table there is the same order number multiple times. In Retail each customer gets a default number of orders created based on the ORDERS AHEAD setting in customer setup. We populate the orders with data from other orders. These orders are place holders so that each customer has the correct amount of orders ahead in the orders table. The data inside these orders is junk until the order becomes active. The unique number will only get assigned when the order is an active order at that moment the order is active we go to the ORDNUM table and get the CURNUM and then increment the CURNUM field one.
Keywords: Orders ahead
Orders table
References: None |
Problem Statement: Question on manual options when Done For Day was not run | Solution: If the done for the day does not run at night there are two options.
1. Users may proceed without done for the day running. If the users choose to do this then they will need to print out one of the numerous reports that shows the current inventory time and date and use these reports to make sure that all of the inventories for each account were updated.
2. A second option is to run done for the day and the go to the TCIF_SIIMPORT table and reset the N_INFO_FLG for any inventories for the current day. This will allow the users to use the normal report to see which customers have and have not been forecasted.
Keywords: Done for the day
References: None |
Problem Statement: How do I configure the IgnoreSoftWRInFirstPhase INI Setting? | Solution: IgnoreSoftWRInFirstPhase=1 (default)
This option determines during which phase of the optimization process soft window restrictions are checked. The degree to which the soft restrictions will be adhered to is determined by whether this setting is set to 1 or 0 in the INI file
Acceptable Values:
0 = off; skips soft window restriction checking in the final phase of optimization
1 = on (default); skips soft window restriction checking in first phase of optimization
Use: Aspen Retail can differentiate between hard and soft window restrictions. Hard restrictions are always respected., but the system can be flexible when considering the soft restrictions. The system tries to meet the soft restrictions if possible. When set to 0, the system will not try to break the soft delivery window restrictions, which will result in more orders in overflow, but less orders delivered during their soft window restriction. When set to 1, it allows more orders to be automatically scheduled onto trucks and increase the amount of orders that are delivered in their soft window restriction
Key words
INI Files
IgnoreSoftWRInFirstPhase
Keywords: None
References: None |
Problem Statement: What do we do if the sales and inventory feeds fails? | Solution: Sales or inventory update failures directly affect the validity of demand forecasting and replenishment planning. Fleet Optimizer ASR is able to forecast up to 50 orders into the future given a starting inventory and complete sales trend information. However, the longer the period between the last validated inventory position and the point of a given demand forecast, the greater the risk will be of stock-outs or no-fits due to unforeseen events affecting demand and inventory. There are many alternate methods available to enter inventory or sales updates into Aspen. Should automated feeds be interrupted, manual collection (that is, via phone), and direct input of data (via Manual Information Collection) are possible. Given one validated inventory position per day, Aspen ASR can yield dependable results in most cases.
Keywords: None
References: None |
Problem Statement: Procedure for running the Change Product Utility. | Solution: Please follow the instructions below when using the product code change utility.
Make sure that all NT Services are off, prior to running the Product Code Utility.
NT Services can be turned back on, when the Product Code Change Utility is complete.
Because a customer can have only 5 product codes and all the orders tables read these 5 product codes when you perform a product code change, all the orders will have the new product code. This includes dispatched orders and old orders.
The Exported Orders will only reflect the new product codes if the user re-exports a shift.
Keywords: Utilities
References: None |
Problem Statement: Dispatcher couldn't see Customer Name Column | Solution: In later versions of Retail, it is possible to move Columns and Resize them in the optimizer. This feature was added because different customers have expressed the need to prioritize different data for efficient Dispatching.
Unfortunately this means that occasionally a dispatcher will come in and not be able to find certain columns that he is used to seeing on the screen when he opens up the optimizer. If this is the case, simply scroll all the way to the right and look for any columns that may be hidden or reduced to almost nothing. Sometimes this will require you to click a barely visible line at the far right and hold down the mouse key and drag it further to the right (seemingly out of the box you are working in). This should expand it enough to be able to see the header of the column.
Keywords: Optimizer Columns, Resizing
References: None |
Problem Statement: There is a memory overrun in the Data Quality Manager that can cause the system to lose tank information for a customer. If the tank information is lost then users are not able to exit the customer setup screen and forecasting for the account is inaccurate | Solution: One way to correct this issue is to totally delete the customer and recreate the customer. When this method is used all trend data and history information is lost for the customer, so be sure to take screen shots of existing information.
A second method of correcting this issue is to go directly into the TPS_TIM table and the TPS_GASRECS table and correct the field GASTYPES. The GASTYPES field is simply the product number that is associated with each tank. If this problem is corrected directly in the tables then the history and trend information will be saved.
Keywords: Data Quality Manager
Tank Information
Customers
References: None |
Problem Statement: The NT Service Book Inventory has been retired | Solution: The Forecast NT Service will now calculate the book inventory.
Keywords: Book Inventory
Forecast Service
References: None |
Problem Statement: How do I fix an inventory that was processed as next year? | Solution: TheSolution to this issue is to go into the TPS_YESTINFO table for this customer and fix the processed Inventory Date to reflect the correct date in the INVDATE field and also in the FIRSTINV field. After this the User should be able to proceed with Reforcasting the Customer as necessary.
Keywords: Inventory Date
References: None |
Problem Statement: What is the easiest way to find multiple orders on the same shift for one customer? | Solution: The Multiple Orders screen within Optimizer (RSO) will display all of the shipments for customers who have more than one shipment scheduled for a given shift. The screen displays shows the customer number, ETA, order numbers, and terminal number for each customer. This provides a better way for the user to view the scheduled shipments for the high volume accounts.
Keywords: None
References: None |
Problem Statement: What is a Scheduling Terminal used for? | Solution: The Scheduling Terminal can be used to display a truck that is domiciled at another terminal appear in the list of trucks for a terminal for which it typically hauls deliveries. This saves a dispatcher from having to move deliveries using the Storage Box on the Optimizer Screen.
Keywords: Scheduling Terminal
References: None |
Problem Statement: Why is Done For The Day not running for certain groups? | Solution: The most common case of this occurring is that a user was in the optimizer when done for the day ran. The done for the day service does not override the in process flags in versions 2004.1 to the current version. In version 7.5.2 the system did override the in process flag which could lead to some concurrency issues. It is very important to schedule the Done For The Day service to run when no users will be in the optimizer.
Keywords: None
References: None |
Problem Statement: Is there any way to control how close together the optimizer will schedule multiple orders for the same customer? | Solution: There is an Ini Setting inside the Customize.ini that allows you to specify how close together the Optimizer will schedule 2 (or more) deliveries for any single customer. This setting is:
numMinBetweenTwoDeliveries=60
Expressed in minutes, this is the time between the Start on a delivery (Unloading) on one order to the Start of another delivery (Unloading) for this same customer.
Keywords: Multiple Deliveries, High Volume Customers
References: None |
Problem Statement: What is the basic flow of a shipment inside Aspen Retail? | Solution: When a shipment is generated, it flows through many tables (TPS_ORDER, TCIF_MANORD, TPS_ORDDISP, TCIF_EXPORTORDER, and TPS_OLDORD) in the Aspen Retail database. Below is flow of a shipment from beginning to end.
A forecasted shipment always starts in the TPS_ORDER table.
A manual shipment can begin in the TCIF_MANORD table or the TPS_ORDER table.
A shipment begins in the TCIF_MANORD table under the following circumstances:
Shipment is placed via the IVR
Shipment is placed via the eChain application
Station is in process when a new shipment is being placed via the Replenishment Planner or while in the optimizer
A shipment begins in the TPS_ORDER table under the following circumstance:
Shipment is placed directly in the Replenishment Planner (station is not in process) by a user
A shipment can be moved from the TCIF_MANORD table to the TPS_ORDER table by one of the two processes.
The Manual Order NT Service can process the shipment from the TCIF_MANORD table to the TPS_ORDER table.
Manually imported from the TCIF_MANORD to the TPS_ORDER table by a user while in the optimizer, using the import manual shipments option. This option is controlled by the ini setting manual order.
When a shipment is dispatched, a record is written to the TPS_ORDDISP table (It still is in the TPS_ORDER table). TPS_ORDDISP is like a common interface table similar to the TCIF_EXPORTORDER that was developed for clients on DBASE. The TPS_ORDDISP table provides the ability to export the data or to view what was saved in the optimizer. Since this table was originally designed as an interface table, the N_INFO_FLG was added so that users could tell which shipments had been exported to external systems. In addition, if the ini setting exportorder is on, this shipment will also exist in the TCIF_EXPORTORDER table.
When a shipment is exported, you will see the records in the following tables: TPS_ORDERS, TPS_ORDDISP, and TCIF_EXPORTORDER. In addition, if the shipment is a manual account, the shipment will also be in the TCIF_MANORD table but the flag on the N_INFO will be false.
The TPS_ORDDISP table clears its self whenever the optimizer is saved. However, the TCIF_EXPORTORDER table simply adds to what was already there. So if you saved multiple times, you may see different number of records in each table.
A shipment is moved to the TPS_OLDORD table when the software thinks that shipment has been delivered. The shipments are moved during the forecasting of new inventories.
When the shipment is moved to the TPS_OLDORD table, the record in the TPS_ORDER table is basically moved to the last position in the TPS_ORDER table and then recycled through. However, the move of a shipment to the TPS_OLDORD table will not affect TCIF_MANORD, TPS_ORDDISP, or TCIF_EXPORTORDER. Furthermore, the shipment could still be seen in the TPS_ORDER table but it will now be in an inactive shipment position. Manual shipments will work the same as above except that they are moved to the TPS_OLDORD table from inside the optimizer when the dispatcher pushes Yes to the question Do you want to move all loads to delivered loads log. This is because these accounts are not forecasted and they need another way to move the shipments to that log.
Keywords:
References: None |
Problem Statement: Why does the system only occasionally use Other Additions in the DQM? | Solution: The other additions field is populated when multiple inventories are reported and one of the inventories causes a shipment to be moved to the delivered shipments log.
The following morning the other additions field is populated instead of trying to move the shipment back from the delivered shipments (tps_oldords table) to the orders table.
Basically what might have happened is the initial inventory is reported and then other is reported that is higher than the initial inventory (user error if a shipment was not received between the two inventories). The system then moves a shipment that makes the most sense into the delivered shipments log.
The next morning however a new inventory is entered that corrects the previous days mistake. Since the system does not have the functionality to move the shipment from the delivered shipments log back in to the Replenishment Planner, it populates the other additions field with the shipment quantities.
Keywords: Other additions
Data Quality Manager
References: None |
Problem Statement: Why is my shipment in 'Blue Text?' | Solution: In the Resource Scheduling Optimization, there are 3 possible colors for a delivery once it is placed on a transport. The color scheme has nothing to do with the Red, Yellow/Green, Grey, and White colors associated with the shipment icon. The colors have their own meanings that have been in use since the earliest versions of Aspen Retail and have not changed. For reference the user should consult the Aspen Retail User's Manual, as this is explained in detail.
The colors referred to below are the text of the shipments once they are placed onto a transport. In general, all shipments have a default text color of Black. This indicates a normal shipment with no special delivery conditions to be potentially reviewed and/or specially handled by a dispatcher.
In the cases where the shipment text appears Red, Aspen Retail is indicating to the dispatcher that the shipment has been scheduled on the transport (generally this is done manually for Red shipments) in which the quantities as ordered do not match the compartmentation as configured for the transport. There are many reasons for this case, ranging from a business practice of sending out partial deliveries (i.e. some ordered quantities may be less than a full compartment size, but due to storage restrictions the company allows this delivery to be made) to certain customers; to inaccurate transport setup within the software that the dispatcher does not feel he has the time to fix prior to scheduling this delivery. This delivery text appears Red because the software is alerting the dispatcher that Aspen Retail does not know which products are intended to be loaded into which compartments. The software can not interpret judgment calls that are being made due to execution-related requirements to accommodate the business conditions.
In cases where the shipment text appears Blue, Aspen Retail is indicating to the dispatcher that it cannot determine how to unload this particular shipment into the appropriate tanks. This will only be the case for customers configured with multiple tanks for the same product (i.e. TIM customers). The following example may help to illustrate this situation:
Transport Compartments
Compartment 1 = 10000
Compartment 2 = 20000
Delivery Site Storage for Unleaded
Tank 1 = 8000
Tank 2 = 25000
Whenever Aspen Retail tries to schedule a delivery for this site for Unleaded (for this simplistic case, this is the only product being carried at this site), it will not be able to determine how to load the delivery so that each full compartment can be unloaded into a specific tank. Although the customer may need 30000 liters of product, the software cannot specify that all of the product in Compartment 1 will fit into Tank 1. In this case the software is alerting the dispatcher that there will not be unloading instructions for this shipment.
Some of our clients make a notation in the comments area to indicate that Compartment 1 should be partially unloaded into the Tank 1 before unloading the remaining in the Tank 2, but this only works with transports that have a meter.
In order for the software to be able to automatically handle this condition, and thus not have blue shipments, the dispatcher needs to make sure there are small enough fill lines on the transports to accommodate the smallest tanks sizes at the delivered sites.
Keywords: Blue text
RSO
TSO
TIM
Tank Inventory Management
References: None |
Problem Statement: I keep receiving Winexcpt errors while in the Retail application. And the following error is written into the error log 'WRONG 2 does not exist | Solution: It appears that the PSORA.PACKMIM_SECURITY package got corrupted. The WRONG2 role is a fake role that is returned by set_rights stored procedure in this package if it cannot match the stored username and newly sent user name to continue using the session state.
In fact the application should have stopped working if this error happens as the session state cannot be maintained properly.
The DBA needs to go to the PSORA schema and check if the package is correct and it matches to the one that is used by Retail database schema. If it does not get the package declaration and the implementation and re-build it again on the Oracle server that has this problem.
Keywords: WRONG 2
Winexcpt
PSORA_PACKMIM_SECURITY
schema
References: None |
Problem Statement: Does a user have the ablity to customize Credit Hold Reports or does AspenTech need to do that ? | Solution: Aspentech has to perform this task. All reporting functionality is within the legacy Retail application.The legacy code is invoked from the eChain Credit Manager to provide the report functionality.
Keywords: Reports
References: None |
Problem Statement: How do I change the Forecast Delay for a Station? | Solution: Under the Utilities|Change|Forecast Delay Cutoff?
It can be changed by a variety of filters, Terminal, Zone, or for individual Customers
The time can be entered by Hours and Minutes.
Keywords: Forecast Delay
References: None |
Problem Statement: Is it possible to track which user processed a station in DQM by querying the database? | Solution: At this time this data is not currently stored in the database. Generally most customer use the set schedule of dispatchers to handle customers on a day to day basis so although we have had some audit related requests come in regarding user tracking, this feature has not been added to the software to this point.
If a customer desired to create a trigger to generate this data themselves, it would need to query the login information through the IT hierarchy and track who made the updates per STATNUM in the TPS_YESINFO table in the as this is the end location for post-processing data through the DQM. Caution should be used in creating this as with any triggers as it may slow down the DQM process.
Keywords: DQM Tracking
References: None |
Problem Statement: How does the copy order function work? | Solution: The Copy Order function within the Replenishment Planner Window allows the user to duplicate an order entry shipment. This is useful when multiple entries of the same type are needed. (This is often the case with jet fuel deliveries to airports, where ten copies of the same shipment must be entered). Open the Replenishment Planner and select an Order Entry account. Make sure that an shipment already exists. Highlight that shipment and click on the Copy Order icon. An identical shipment will be created. The only information that should be different is the Order Number.
Keywords: None
References: None |
Problem Statement: How can I set up a terminal as Best Buy in Aspen Fleet Optimizer? | Solution: In order to set up a terminal as Best Buy, look at the Group the terminal is assigned to on the Terminal Setup Screen. Using the Group Setup Screen, open the Group and check the Best Buy box. This will configure the Best Buy settings to work within Fleet Optimizer. These settings allow you to configure Product Outages at the terminal, product prices to trigger calculations about which terminals are best from which to deliver product to customers dependent upon price, etc.
With Best Buy settings turned on, it is also possible to configure multiple suppliers at terminals for pricing decisions to be made as far as which supplier to load from.
Keywords: Best Buy
References: None |
Problem Statement: When a tank is set up as out of service can you manually add product for the tank? | Solution: The tank out of service functionality only works with forecasted accounts. The functionality is not designed nor is it operational with manual accounts. The system will not forecast any product for tanks that are out of service but a user can enter replenishment planner and add product for out of service tanks. The user simply needs to enter the replenishment planner and lock in order quantities for the tank
Keywords: None
References: None |
Problem Statement: How does Test UseFreightInvoiceCache setting work and how to test it? | Solution: Set in the Customize.ini file the following:
If UseFreightInvoiceCache = 0, RSO will not pre-allocate TRIPIDs for the current session and the TRIPIDS will be used based on the number of splits created during optimization.
If UseFreightInvoceCache = 1, RSO will pre-allocate 100 TRIPIDs for the current session and after exiting out of RSO, the PS_CUR value for the FREIGHT_INVOCING will be increased by 100.
You can use the instructions below to test the UseFreightInvoiceCache functionality
[Set in the Internal.ini UseFreightInvoiceCache =0]
1. Do a 'select * from tps_appindex' on the SQL database
2. Take note of the PS_CUR value under FREIGHT_INVOICING
3. Go to Aspen Retail and open RSO
4. Open a terminal and click on Optimize
5. After doing Optimize, do again a select * from tps_appindex on the SQL database
6. Compare the value of FREIGHT_INVOICING now with the previous value, before hitting Optimize.
Expected Result: The number should only increase by number of splits created + 1.
[Set in the Internal.ini UseFreightInvoiceCache =1]
1. Do a 'select * from tps_appindex' on the SQL database
2. Take note of the PS_CUR value under FREIGHT_INVOICING
3. Go to Aspen Retail and open RSO
4. Open a terminal and click on Optimize
5. After doing Optimize, do again a select * from tps_appindex on the SQL database
6. Compare the value of FREIGHT_INVOICING now with the previous value, before hitting Optimize.
Expected Result: The number should only increase by of 100 + 1.
Keywords: INI setting
Testing Procedure
References: None |
Problem Statement: What steps should I take to make a Full recovery after a system interruption? | Solution: See attached document
Keywords: Recovery
References: None |
Problem Statement: How is Time Adjusted Sales work in Data Quality Manager? | Solution: In Data Quality Manager, Time adjusted sales are sales automatically calculated by Aspen Retail when the gap of time between inventory measurements is different than 24 hours. For example, if a Customer consistently measures inventory at 6am daily and one day a measurement is taken at 8am, Aspen Retail will calculate the sales for the two hour period between 6am and 8am today and display it under Time Adjusted Sales for reconciliation purposes
Key words
Time Adjusted Sales
Data Quality Manager
Keywords: None
References: None |
Problem Statement: Where can users select the tubesheet layout display (thermal or mechanical) in the Drawings? | Solution: In Aspen Shell and Tube mechanical, users can select how they want to display tubesheets layout from the Drawings folders. From Input> Program Options> Drawings, users can select thermal or mechanical layout options.
Then, user will be able to see drawings that he/she selected in Results>Drawings>Tubesheet Layout. Below are the pictures of Thermal tubesheet layout and mechanical tubesheet layout.
The thermal and mechanical layout are created by the Aspen/HTFS and Aspen/B-JAC engines respectively. The User can select either one for the final layout. The layout can then be printed or exported to a DXF file.
If the design file has both thermal and mechanical data, when the thermal data is transferred to mechanical, the program assumes that the thermal layout will also be used in mechanical.
Keywords: Tubesheet layout, Thermal Layout, Mechanical Layout
References: None |
Problem Statement: What is the proper setting for DoBackHaulTruckAssignments in the customize.ini file? | Solution: Any client that does not have back haul information set up in the database needs to have this setting turned off (i.e. set to 0). If this setting is accidentally turned on (i.e. set to 1) the system can make sub-optimal sourcing choices. These choices can cause the optimization to be less cost affective.
Keywords: None
References: None |
Problem Statement: Minimum and maximum load size restrictions are now being respected when the system is creating split loads. | Solution: In version 2006.5 Aspen Retail will now respect the customer specific minimum and maximum restrictions that can be set up at the customer level. Prior to Aspen Retail 2006.5 the system was not looking at the restrictions when creating split loads. In version 2006.5 the system does respect these restrictions so when upgrading to version 2006.5 these settings will need to be reviewed to insure split loads can still be automatically created.
Keywords: None
References: None |
Problem Statement: What are size groups used for? | Solution: Size Groups are numerically hard coded categories that transports can be put into to speed up the optimization process. The idea is that the optimizer only looks at one transport for sizing and proportionality in that all transports in the group are the considered to be the same.
Keywords: None
References: None |
Problem Statement: What does the lowercase v stand for in Replenishment Planner next to an order #? | Solution: The lowercase v in Replenishement Planner indicates the order has been forecast without respecting the delivery window restrictions. This case comes up when a user has the DonotRestartForecastWhenRestricitonViolated ini setting turned on.
Keywords: lowercase v, DonotRestartForecastWhenRestricitonViolated, v
References: None |
Problem Statement: 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: Shortload
Split Load
Short vs. Split
References: None |
Problem Statement: How do I enable auditing within Aspen Fleet Optimizer? | Solution: There is a setting in the customized .ini setting call:
OrderAuditLog=1
If this is set to 1 then auditing is on and if it is set to 0 then auditing is off.
This tracks changes made on orders.
Please be aware that this table will grow rapidly so adequate database space will be needed.
This will also only track changes made to orders not the entire data set (i.e. trucks, products, customer setup).
Keywords: Orders
Auditing
Tracking
References: None |
Problem Statement: What does the spike trend percentage do? | Solution: The Sales Trend Spike Percentage is the threshold value in percentage terms at which Fleet Optimizer will consider a short-term fluctuation in sales as an actual trend. The Sales Trend Spike Percentage takes effect only after two days of consistent fluctuations. The forecaster will then apply that fluctuation to the sales forecast.
Keywords: None
References: None |
Problem Statement: This Knowledge Base article answers the following question:
What does the ARCHIVE: store event failed to determine prime by idx error message mean? | Solution: The ARCHIVE: store event failed to determine prime by idx error message indicates that the archiver is unable to find the archive associated with a cache bucket. It needs to open the archive so that it can empty the cache bucket into the archive.
The error message may be generated if the archive fileset is corrupted or perhaps it has been dismounted or was temporarily locked by another process such as an antivirus scan or a 3rd party (non-Aspentech) backup process.
AspenTech recommends that all archive filesets should be mounted unless it is known for sure that the cache does not contain any data destined for the archives.
Keywords:
References: None |
Problem Statement: Does the Day/Night Field on the customer set up screen restrict deliveries for this customer? | Solution: No, this field was created for some customers using our Forecasting Tool but not our Optimization tool. In short, checking the Day Check Box will prevent the Forecasting Algorithm from forecasting a delivery to be delivered during this timeframe, but once these deliveries are moved into the optimizer this field is not being observed. It is required to make delivery restrictions of this nature, to use the Time Restriction fields on the Customer Restriction Screen.
Keywords: Delivery Restrictons, Day/Night
References: None |
Problem Statement: Do customers that are going to be set up to be split partners need to be from the same terminal? | Solution: In all versions of Aspen Retail prior to 2004.1, it is required that Cluster Partners and Cloud Partners be located out of and delivered out of, the same terminal. In 2004.1 this requirement has been removed.
Keywords: Cluster Partners, Split Partners
References: None |
Problem Statement: Sometimes an address is not found in Map Point. This can be because the address is a cross road or the street is new construction, etc. How do you have the software find the address? | Solution: Using Map Point, zero in on the address. Under the Tools menu of Map Point, select Location Sensor. This will provide the user with the latitude and longitude for this address. Next the user needs to put the latitude and longitude into the Aspen Retail application for that location. Remember to input a negative sign in front of the longitude. Map Point does not do this. Save this information back to the database and then reopen the location. Select Station Map from the view menu and the address will be found.
Keywords:
References: None |
Problem Statement: What can I do to try to prevent side products from being delivered in Aspen Fleet Optimizer? | Solution: AFO tries to keep inventories in proportion to sales by default in the forecasting algorithm. However, due to fleet configurations, fill lines, and uneven sales / tankage often encountered in the market, there are some additional settings that allow a dispatcher to manipulate the amount of side products the Fleet Optimizer will attempt to deliver.
On the Customer Set-up Screen, under the View/Carrying Costs... option, you will see two values that can be utilized to help minimize these side product inventories:
Maximum Days Supply and Days Supply Threshold.
Maximum Days Supply?specifies the number of days supply you do not want to exceed following a delivery. Maximum Day Supply is inventory quantity plus the delivery quantity. If the next delivery will exceed this value, the load sizing algorithm will attempt to modify the product mix on the order to get the volumes back under this threshold. If the truck compartment - daily sales do not allow this value to avoid being broken, Aspen Fleet Optimizer will ignore the threshold and delivery the load if it is required to avoid a runout of the faster selling products.
'The Days Supply Threshold allows you to specify the maximum number of days (threshold) supply difference between the controlling product and a non-controlling product and does not allow deliveries that exceed the threshold. That is, the software does not schedule a delivery of product that makes a customer's days supply difference greater than the Days Supply Threshold. This is done to maintain proportionality between your various products.
Aspen Retail calculates the days supply threshold after the delivery by subtracting the largest day supply by product from the smallest day supply by product and compares it to the DaySupplyThreshHold setting.
Example 1:
DaySupplyThreshHold=5
Unleaded
Mid-grade
Premium
Current days supply
3
4
6
Projected days supply after delivery
10
12
14
In this example, the software subtracts the largest day supply (Premium) 14 - from the smallest day supply (Unleaded) 10 to equal 4 (14-10).
The software then compares the 4 days supply to the DaySupplyThreshHold of 5. Since the days supply after the delivery - 4 - is within the DaySupplyThreshHold of 5 days, the delivery is within the tolerance and acceptable.
Example 2:
DaySupplyThreshHold=5
Unleaded
Mid-grade
Premium
Current days supply
3
4
6
Projected days supply after delivery
10
12
17
In this example, the software subtracts the largest day supply - (Premium) 17 - from the smallest day supply (Unleaded) 10 to equal 7 (17-10).
The software then compares the 7 days supply to the DaySupplyThreshHold of 5. Since the days supply after the delivery - 7 - is not within the DaySupplyThreshHold set at 5 days, the delivery is not acceptable and the system tries to either send a different product mix that satisfies the 5 day threshold or tries to create a split load with another customer to adhere to the DaySupplyThreshHold set at 5.
The software also ensures that a delivery is made for a side product; that is, the controlling product on that particular shipment that needs a delivery but would have normally broken the DaySupplyThreshHold.
Example 3:
DaySupplyThreshHold=5
Unleaded
Mid-grade
Premium
Current days supply
3
4
1
Projected days supply after delivery
10
12
17
In this case, the system subtracts the largest day supply (Premium) - 17 - from the smallest day supply (Unleaded) - 10 - to equal 7.
Since the Premium product is the controlling product (the product that runs out first), the software realizes that it is possible to break the DaySupplyThreshHold=5 rule in order to avoid a runout situation even though the days supply after the delivery - 7 - is not within the days supply threshold set at 5 days.
The default for DaySupplyThreshHold is 0.0 or off. This default value is set high so that the proportionality logic is only started in the instances where the client's business case warrants such logic. '
Keywords: Maximum Days Supply, Days Supply Threshold
References: None |
Problem Statement: What are potential issues for migrating the Aspen Rxfinery suite products (Aspen CatRef, Aspen FCC, Aspen Hydrocracker, Aspen Hydrotreater) to newer versions? | Solution: Because of the service project nature of implementing these products inside a refinery, there will always be migration issues.
There are 2 components that may require service projects in each migration:
1. The spreadsheet interface and its objects
2. The Aspen Plus model and its EO-User model components for the reactors.
Often some options or variables will change between versions. For instance, the EO-Analyzer code has been updated for version 7.0 , resulting in compatibility issues with models built in version 2006.5 (or earlier). Specifically, this changes the number of variables inside the Aspen Plus model and its EO-User model. In previous releases of Aspen Plus, various EO options have changed (e.g., by default, automatically dropping missing phases), which require new EO Options to be specified to maintain the desired (previous) behavior. If your models currently run in a very old version of Aspen Plus, these types of changes will significantly increase the number and complexity of migration issues, as this variable structure is changed in every new version of Aspen Plus.
The spreadsheet interface is also updated every version. New objects are introduced for the spreadsheet in each version and need to be re-mapped to the model.
When planning a migration, you should budget resources to upgrade both the spreadsheet and the model. As an example, to upgrade just the model from version 2006 to version 7, would require the following approximate service times:
Aspen Catref 2 hours
Aspen FCC 2 days
Aspen Hydrotreater minor
Aspen Hydrocracker minor
The above migration times are in addition to the time required to migrate the spreadsheet
The spreadsheet interface is also updated every version. New objects are introduced for the spreadsheet in each version and need to be re-mapped to the model.
When planning a migration, you should budget resources to upgrade both the spreadsheet and the model. As an example, to upgrade just the model from version 2006 to version 7, would require the following approximate service times:
Aspen Catref 2 hours
Aspen FCC 2 days
Aspen Hydrotreater minor
Aspen Hydrocracker minor
The above migration times are in addition to the time required to migrate the spreadsheet
Keywords: Catref, FCC, Hydrotreater, Hydrocracker, migration, EO
References: None |
Problem Statement: Why are all shifts treated the same in the optimizer when you open multiple shifts? | Solution: There is fundamental logic in the system does not allow middle shifts to be different from the end shifts.
For example let us say that a dispatcher has dispatched thru NIGHT 5. The dispatcher then goes back into the system to look at NIGHT 3 if the dispatcher changes NIGHT 3 from dispatched to optimizer all shifts that follow that D4, N4, D5, N5 will then also be labeled as optimizer because the core logic in the system does not allow future shifts to be dispatched if a shift prior to that is not dispatched.
This logic also works the other way if DAY 4 is not marked dispatched and a dispatcher goes in an dispatches NIGHT 5 the logic in the system will automatically flag DAY 4 dispatched.
The key point to take away is if a shift is marked DISPATCHED all shifts prior to that will be marked DISPATCHED and if a shift is marked OPTIMIZED all future shifts after that shift will be marked OPTIMIZED. Based on the current core logic the two assumptions above must always hold true and that is why the system seem to apply changes to all shifts.
Keywords: None
References: None |
Problem Statement: How are diesel compartment groups are set up in the Aspen Retail database? | Solution: The COMPARTMENTLENGTH is used to store double wall/diesel group information. It is complicated below are some examples that might be useful.
The value in the COMPARTMENTLENGTH is used for both double walls and diesel compartment groups. It works like this.
If in COMPARTMENTLENGTH for a truck you see all the same value of -1 that means no double walls and no diesel groups.
If you see values that -1,-1,-1,-1,-2, this means a double wall exists but there are no diesel groups
If you see -1.-2.-3.-4.-5, this means all compartments have double walls but no diesel groups are checked
If you see 1, 1, 1, 1,-1, this means one double wall exists and 1 diesel group is checked, the last diesel group is not checked
If you see 1, 1,1,1,2, this means one double wall exists and 2 diesel groups are checked.
So each time the value changes, (for both positive and negative numbers), that means a double wall is checked.
If the number is negative, that means that no diesel group is checked for that compartment.
If the number is positive that means that a diesel group is checked.
Keywords:
References: None |
Problem Statement: Why would a customer want Load Confirmations to import while in the Optimizer? | Solution: The primary reason for this would be to allow the system to update the delivery window's for subsequent deliveries. Additionally there is functionality to display Load Confirmed orders in a different color and to not allow them to be moved off the truck they have been confirmed to after they have been delivery confirmed.
Key words
Load Confirmation
Keywords: None
References: None |
Problem Statement: How do you disable the reset utility in Fleet Optimizer? | Solution: The reset functionality can be turned on or off inside the internal.ini setting.
[menus]
ResetActive=0 (This will turn off the ability to use reset.)
ResetActive=1 (This will turn on the ability to use reset.)
These setting can be turn on or off on individual machines and not global settings.
Keywords: None
References: None |
Problem Statement: How do I edit a future date inAspen Fleet Optimizer? | Solution: If a dispatcher mistakenly enters a future date during Data Quality Manager that can gravely impact the forecast. Currently there is no way to correct this error inside the GUI. If a user incorrectly enters a future date a DBA will need to correct this error directly in the YESTINFO table. The DBA will need to update the INVDATE and the FIRSTINVDATE fields to the current date. Once the DBA has updated these fields to the current date the dispatcher will then be able to correctly enter the inventory time and date. It is highly recommended that the dispatcher reforecast the account after this process.
Keywords: None
References: None |
Problem Statement: In services.ini - what values do I give to StartTime & StopTime if I want the services to run 24 hours per day? | Solution: The Fleet Optimizer services are time based services that can be set to run throughout the day.
They consist of the following setting:
IdCode (This code is normal set to 1 in a few rare case it can be set to another value.)
Period (This value is in minutes and will tell the service how often to run.)
StartTime (This value is in military time and will tell the service what time of day to start processing data.)
StopTime (This value is in military time and will tell the service what time of day to stop processing data.)
Timer (This value is no longer used.)
If you would like to have the services run 24 hours a day please start time to 00:00 and the stop time to 23:59.
Keywords: None
References: None |
Problem Statement: How often should I purge my database tables? | Solution: The attached document provides a suggested schedule for archiving and deleting obsolete records. However, the maintenance schedule you implement at your location should depend upon the needs and business processes in use for your Aspen Retail system. Use maintenance tools provided by your database provider for performing maintenance activities such as backup, archival, and deletion of records. Consider keeping archives of the deleted records.
Keywords: archiving
deleting
maintenance
database
References: None |
Problem Statement: Reset Utility Best Practices | Solution: The Reset Utility, available on the Utilities Menu, allows a User to clear the control of a station from an aborted process. This utility can cause a number of unexpected bad outcomes if it is used haphazardly by an impatient User. It should be limited to only the most advanced users in a dispatch Center.
Before clearing the Control or ownership of a station through the use of the Reset Utility, the user should verify that it was truly being controlled by an aborted or otherwise unnaturally ended process. If another user is making changes to this station, or a back-end service is trying to make changes to a station, the Reset Utility should not be used as data may be lost or otherwise corrupted.
Keywords: Reset
References: None |
Problem Statement: How do I load new Customers into Aspen Retail automatically? | Solution: Aspen Retail has am interface table and an NT service that can be used to automatically upload shell customer information into the core tables. This NT Service is entitles the CPT (for Customer Update) and the table is entitled TCIF_CPT. The table contains fields for basic customer information, such as:
Account number
Location
Products
Tank Sizes
Delivery information from up to 3 terminals
etc.
Once populated, this table of information will be brought into the core tables by the CPT Service on its daily run-through. This table and service are also used to allow companies to modify account information if things such as products and/or tanks have changed.
Once this shellaccount information has been brought into Aspen Retail by the CPT Service, it will be necessary for the dispatcher to to go through and make any customizations necessary, such as delivery restrictions.
Keywords: Customer Update, New Customers
References: None |
Problem Statement: How many products are we limited to with TIM? | Solution: In version 7.7.2 there is still a hard limit of (5) five products per site in Aspen Retail. The TIM functionality will allow users to now create an infinite number of tanks for these five products but the system still have a core limit of (5) five products per site even with TIM.
Keywords: TIM
Limits
Products
References: None |
Problem Statement: What is 'forecast delay cutoff? | Solution: Forecast Delay Cutoff is used by the SalesImport Service to delay forecasting for a customer for a certain period of time if only Sales or Inventory has been received. Rather than forecast immediately upon receiving only the Sales Information for a Customer, if Forecast Delay Cutoff is set to say 30, the Service will delay forecasting for this site (based on the time of the one record that was received , either sales or inventory) until this amount of time (in this example 30 minutes) after the time stamp in the entry date field for this record has been reached.
Keywords: Forecast Delay Cutoff, Delay
References: None |
Problem Statement: What does Opening Inventory mean in Data Quality Manager? | Solution: In Data Quality Manager, this is the inventory the Customer opened up with the last time orders were forecasted for this Customer. Starting inventory is passed in as a fixed variable because it is corrected and verified during the previous forecasting session
Key words
Data Quality Manager
Opening Inventory
Keywords: None
References: None |
Problem Statement: How do I resolve the following error?
S o u r c e : c : \ d o c u m e n t s a n d s e t t i n g s \ k r h o d e s \ a s p e n r e t a i l \ w i n op t . e x e
M s g : P S O D B C : : o d b c E x e c S Q L g e n e r a t e d S Q L S t a t e : H Y 0 0 0 T a b l e : t e rm i n a l
[ D a t a D i r e c t ] [ O D B C O r a c l e d r i v e r ] [ O r a c l e ] O R A - 0 3 1 0 6 : f a t a l t w o- t a s k c o m m u n i c a t i o n p r o t o c o l e r r o r | Solution: The problem is with the NLS strings being out-of-sync between Oracle client and server.
See attached for steps to correct the problem.
Keywords: two-task
access violation
References: None |
Problem Statement: Is Aspen Fuels Marketing 2006.5 compatible with Map Point 2006? | Solution: Aspen Fuels Marketing 2006.5 should have no compatibility issues with Mappoint 2006.
Keywords: Mappoint
References: None |
Problem Statement: Can I remove a manual order from application once it has been dispatched? | Solution: Open group that customer/order belongs to in RSO
Form the Edit Menu, Select Remove Dispatched Orders
EXPECTED RESULTS
Dispatched order should be removed from the Optimizer.
Keywords: Dispatched Orders
References: None |
Problem Statement: What is the Short Vs Split Report? | Solution: The Short vs. Split report prints the financial tradeoff between delivering a short shipment to a customer and assigning a split shipment with another customer. This report can be sorted by Station or Transport.
This report is useful for determining good split partners and evaluating one-by-one individual transportation choices.
Keywords: Short Orders, Split Orders
References: None |
Problem Statement: Microsoft Windows Server has terminal server features (a.k.a., WTS) that can provide the functional equivalent of a thin-client | Solution: . Does Thin Client or Windows Terminal Server environment work well for Aspen Retail? What types of issues can one expect?Solution
Aspen Retail Version 7.x is not designed to run in a WTS environment. Aspen Retail applications works best when implemented in a two-tier client-server (fat-client) model. This is because Aspen Retail application, particularly the Optimizer, requires high bandwidth for data transfer between the client and server. The users may experience problems when the bandwidth is below the equivalent of a 10-MBit LAN connection between the client and server. This is one of the many reasons that our clients usually prefer to assemble and maintain a centralized dispatch operation.
Nonetheless, several of our customers have deployed WTS successfully by using IT techniques to overcome some minor problems that were directly attributed to WTS technology.
However, since Aspen Retail does not officially support WTS implementation, there have been some cases where customers had to use workaround to overcome problems that were isolated and attributed to WTS. Based on the input from our customers, here are some of the issues that are commonly encountered when using WTS with Aspen Retail:
Printing to network printers on the thin-client side.
Initialization file management for multiple-userSolutions.
Sever Memory and CPU under-capacity for multiple-userSolutions.
DLL mismatches/conflicts in the WTS thin-client sessions.
Poor communication bandwidth for WTS sessions.
A performance enhancement tip is to avoid setting up each user's drive that is available during the WTS session on a different network server. Each user drive has a copy of the Retail binary and ini files. If you set up these drives on a different network server, each time Retail needs to read or write to the ini file, or launch one of the binary files, the NOS may take a long time to authenticate the user to access the network server. But if you map the drives to actual WTS server drives, the performance (speed) may improve significantly. This means the time it takes to load the apps, optimize, save, etc. can decrease.
Please note that the above tips are provided by our customers. We ensemble the information here for your convenience and reference. We do not guarantee the accuracy.
AspentTech does not provide hardware specifications for WTS servers. We only provide the fat-client workstation requirements, and the client will have to obtain their own assistance in extrapolating these requirements to a WTSSolution for multiple users. We also advise that our clients find and rely on their IT expertise when deploying thin client environment. AspenTech does not guarantee that we are able to provide support or IT expertise on thin client deployment.
Keywords: Thin client
Fat client
Windows Terminal Server
Citrix
References: None |
Problem Statement: Why are comments appearing from same shipment booked last year in my current shipment? | Solution: The reason is because the same order number (uniquenum) exists in the TPS_ORDER2 table and in the TPS_ORDERS table. The way to avoid this is to make sure your LASTNUM field in the TPS_ORDNUM table is set to a high enough number. For example 100,000. And to also make sure you are regularly (Approximately every 6 months) purging this table along with the TPS_ORDERS table.
Keywords: Private Notes
Comments
Order
Shipment
Uniquenum
Replenishment Planner
References: None |
Problem Statement: What version of Mappoint is supported in Aspen Fleet Optimizer 2004.1? | Solution: AFO version 2004.1 has been tested with Mappoint 2002 and Mappoint 2004. We have not tested earlier version of Mappoint but we do not anticipate issue with it. AFO version 2004.1 was also tested with MS SQL Server 2000 and Oracle 9i.
Keywords: None
References: None |
Problem Statement: What does the short load value do in customer set up? | Solution: The 'Shortload at Value' is a time variable that designates the threshold window length, in hours, which will initiate Load Sizing for a Customer's order. Loadsizing is a function of Fleet Optimizer that willdecrease the payload of an order to attain a desired Delivery Window. The Delivery Window is the period of time between the Retain Point and the Runout Point. For example, a 'Shortload at Value' of 5 instructs Retail to begin Load Sizing only if the largest
available Shipment for the Customer creates a Delivery Window shorter than 5 hours.
Keywords: None
References: None |
Problem Statement: This article explains how to activate debug messaging for TSK_HBAK. | Solution: Use the following steps to activate debugging for TSK_HBAK:
1. Start the Aspen InfoPlus21 Manager.
2. Locate TSK_HBAK in Running Tasks.
3. Hightlight it and click Stop Task
4. Locate TSK_HBAK in Defined Tasks.
5. Double click on it
6. Edit the Command line parameters by adding -d1
7. Click Update to save the changes
8. Click Run Task to restart TSK_HBAK
Debug messages appear in the log file defined in the LOG_FILE field of the HistoryBackup record
Keywords:
References: None |
Problem Statement: How can I handle Credit Hold Accounts through AFO? | Solution: In Fleet Optimizer it is possible to handle accounts that need to be monitored for deliveries due to credit worthiness in a variety of ways depending on business needs.
Accounts can be set in a Credit Hold State so that all orders are automatically on Credit Hold and need to be taken off Credit Hold either directly on the order screen by a dispatcher, or through a Credit Application that can manage Credit Hold customers outside of the traditional Scheduling Center.
Accounts can be set up without Credit Hold status configured and individual orders can be set on Credit Hold status pending updates from the Credit Department or other monitoring group within the company.
Additionally, Credit Status can be set or removed through an NT Service that updates Credit status via Master Record updates.
Keywords: Credit
References: None |
Problem Statement: When I reference a previous holiday's sales for the same holiday, the sales data is not the same. | Solution: The Holiday Storm Utility does not use the same sales as the previous holiday; It uses the sales percentages of the previous holiday.
For example, if the previous days that are referenced had an increase of 10% each day, then a 10% increase will be added to the current sales projection for the current time frame referenced.
Keywords: Holiday Storm Utility
References: None |
Problem Statement: Is there any way to adjust how far into the future the Forecaster will look when reconciling Inventory Updates with deliveries? | Solution: The ini setting InventoryUpdateETACutOffHours= in the Customize.ini file has been added to allow a user to adjust how far in advance the Forecaster will look to try to find a delivery that will help to reconcile a new inventory.
The default for this setting is 24 hours. This means the Forecast engine will look up to 24 hours in advance of the first inventory received for the day to try to reconcile any inventory variations (inventory increases generally).
Keywords: Data Quality Manager, DQM, Inventory Update
References: None |
Problem Statement: What is the Sustainable Shipment Report and what is its purpose? | Solution: The Sustainable Shipment report prints the calculated largest sustainable load for a customer based upon the delivery window requirements. This report can be sorted by Group, Terminal, or Station.
The report shows the size storage and average daily sales by product and goes through an analysis based upon ratio of these figures and the ratio of sales % per product to total tankage.
Taking these figures the report calculates the amount of product that could be delivered over a series of desired delivery windows. 30 hour, 24, hour, 18 hour, 12 hour, 6 hour, 3 hour and point in time delivery.
These figures can be used to help determine appropriate split partners, fill-line options needed, and buffer calculations.
Keywords: Sustainable Shipment, Load Sizing
References: None |
Problem Statement: Can I report sales for 'Out of Service' tanks? | Solution: Yes, we have allowed the reporting of sales for 'Out of Service' tanks because customers have maintained their desire to keep the trends populated for a tank that they may not be delivering to, but that still has some product left in it. This means the system will not forecast for this tank, but will allow sales to be reported and will keep the trends up to date.
Keywords: Out of Service Tanks
References: None |
Problem Statement: Data Quality Manager is moving shipments to delivered loads log out of sequence | Solution: Retail has been designed with a default 24 hour look ahead window in advance of an inventory update that the DQM will look to see if an inventory increase may be due to a future delivery having arrived early. Occasionally this causes the DQM to pull a delivery ahead of a previous one because it matches the inventory change (increase) better than the previous one.
In order to attempt to ameliorate this potential problem, Aspen has created the following INI setting in the Customize.ini file that can change this default 24 hour look ahead window to any desired length the customer feels is better for their business. This INI setting is called:
InventoryUpdateETACutOffHours=6
Keywords: ETA CUTOFF
Inventory Update
References: None |
Problem Statement: This knowledge base article describes how to properly reference a particular occurrence in the repeat area of a tag in InfoPlus.21 when requesting data from InfoPlus.21 through an OPC client application. This applies when the user requests data through InfoPlus.21's OPC server feature. | Solution: Note, this has not been supported since a re-implementation in v7.2 based on a .NET SDK provided by the OPC Foundation. That work had been done so that the OPC DA Server passed the OPC Foundation compliance tests but the ability to read from a particular occurrence number was not part of the tests. With the introduction of v9.0 of Aspen InfoPlus.21 it is again possible to identify a particular occurrence number from a tag's repeat area.
Use the following dot notation to request data from a particular occurrence number in a repeat area of a tag:
definition recordname.tagname.<occurrencenum> fieldname
Replace <occurrencenum> with the number representing the desired occurrence number of the repeat area that contains the field.
Note, the double quote logic handles names containing dot/period (.) character and/or spaces. Consequently, the double quotes are optional.
For example, to see the value of the second occurrence of the IP_TREND_VALUE field for the demo ATCAI tag within MatrikonOPC Explorer, you can use any of the following as the Item ID:
IP_AnalogDef.ATCAI.2 IP_TREND_VALUE
IP_AnalogDef.ATCAI.2 IP_TREND_VALUE
ATCAI.2 IP_TREND_VALUE (this is possible because the definition recordname is optional)
Keywords: Syntax
Aspen.Infoplus21_DA.1 caused COM/OPC error 0x80004005 on IOPCItemMgt.AddItems()
Error string: E_FAIL
Additional: Could not add items to group
ICONICS Genesis
E_UNKNOWN_ITEM_NAME
IP21DeviceRawItem.Constructor
Definition Record for Tag does not contain FieldName
References: None |
Problem Statement: Unable to remove reference to IOGET record for “SUSPENDED_UNTIL_DONE”.
When trying to make an IOGET record unusable, existing reference could not be removed. | Solution: Go to ScheduleActDef Record, under Fields - #_OF_FIELDS_IN_REC, change the value under OP_CHANGE_REF_VALUE from 'none' to 'all'.
Keywords: SUSPENDED_UNTIL_DONE
References: None |
Problem Statement: What are other additions in Data Quality Manager? | Solution: In Data Quality Manager, these values include unexpected or undocumented additional deliveries of Product to the Customer. When a retain occurs and a Customer receives an unexpected load, the quantities of Product dropped must be logged here. Other Additions may also be negative if Product has been removed from a tank through means other than sales.
Key words
Data Quality Manager
Other Additions
Keywords: None
References: None |
Problem Statement: How does Short Shipment At work? | Solution: A time variable that designates the threshold window, in hours, that initiates load sizing for a customer order.
Load sizing is a function that decreases the payload of an order to attain a preferred delivery window. The delivery window is the period of time between the retain and runout points.
For example, a value of 5 in this field instructs Aspen Retail to begin load sizing only if the largest available shipment for the customer creates a delivery window shorter than 5 hours.
If the largest available shipment for a customer is 10,000 gallons (40,000 liters) and this shipment is defined with a 6-hour window, then the system forecasts the customer's shipments on the full size shipment. If the 10,000-gallon shipment is defined with a 4-hour delivery window, then the system initiates load sizing to find a smaller shipment. Load sizing occurs only if Short Shipment Approval is selected.
Keywords: Short Shipments
References: None |
Problem Statement: What do the values in the TPS_INFOUPDATE table represent? | Solution: The field UPDATETYPE has a value of 1, 2, 3 this refers to the type of data that came in for the customer:
1= Sales Only
2= Inventory Only
3= Both (Sales and Inventory)
A second field called UPDATE_SRC the values in this field indicate how the data came in to the system:
P=POS
V=IVR
M=Manual Information Collection
F= Forecast Service
E= DQM (Data Quality Manger)
Keywords:
References: None |
Problem Statement: How do I use INI settings for Truck Matching? I want the software to adjust some of the manual orders, but not all of them, to match the truck fill lines. | Solution: In order to have Aspen Fleet Optimizer adjust manual orders to fit the truck compartments, there are a number of ini settings and changes that will need to take place.
First and foremost, the Fitmatch setting in the Internal.ini needs to be set to 1. If this is not set to 1, the system will not adjust orders to match the trucks at all. Fitmatch=0 means the Fleet Optimizer can force orders onto trucks whether they match the volume of the truck compartments or not. Fitmatch=1 tells the Fleet Optimizer to look at the following parameters to attempt to adjust the orders (or not in some cases) to match the levels of the compartments.
Assuming Fitmatch=1, the following settings are available to customize matching orders to trucks and compartments:
Match Ord (on the Customer Setup screen)
Match Transport (on the Order Detail screen)
If the Match Ord box is checked on the Customer Setup Screen, all the orders placed for this customer will come in with the Match Transport box checked on the Order Detail Screen. If the Match Ord box is unchecked on the Customer Setup Screen, the orders will all have the Match Transport box on the Order Detail Screen unchecked.
In some cases a Dispatcher will want one of a customer's orders to be automatically sized to match the transport, but not have the customer set up with this option as a default. In this case, the Dispatcher would want to leave the Match Ord box unchecked on the Customer Setup Screen, but for this one particular order check the Match Transport check box on the Order Detail Screen.
Once it has been decided which orders and customers will be allowed to be adjusted, the parameters of how much each order can be adjusted need to be configured. The Aspen Fleet Optimizer has the following settings in the Customize.ini file to configure these parameters:
[truckmatch]
xOver=1000
xUnder=1000
yOver=500
yUnder=500
where the X values represent the amount of the total order adjustment allowed, and the Y values represent the amount of the individual product adjustment allowed. The effect is described as follows:
XOver=1000
this means the optimizer can increase the total volume of the order by 1000
XUnder=1000
this means the optimizer can decrease the total volume of the order by 1000
YOver=500
this means the optimizer can increase the volume of each product on the order by 500, provided the amount does not exceed the total order limit set under the XOver value
YUnder=500
this means the optimizer can decrease the volume of each product on the order by 500, provided the amount does not exceed the total order limit set under the XUnder value
Note that these INI settings are global applied to all orders which are flagged with Match Transport check on the Order Detail Screen.
Keywords: INI settings
truck matching
References: None |
Problem Statement: How to Configure Windows 2008 Server for Aspen Fleet Optimizer Order Manager - Web | Solution: See the attached document for details
Keywords: Windows Server
Configuration
References: None |
Problem Statement: What is the Day's Supply Report for? | Solution: The Days Supply report prints the number of days, per product, of inventory that a customer has in the storage tanks.
This report can be used to see how the Forecasting Algorithm is managing the products to level the inventories to a manageable level.
Keywords: Days Supply
References: None |
Problem Statement: How can I view the Expected Sales for a particular day? | Solution: The History Utility allows you to pull up customers and view their Actual Sales, what the Expected Sales had been for that day, and what the Projected Sales are for the next day.
Keywords: History Utility, Projected Sales, Expected Sales
References: None |
Problem Statement: What does the Day/Night Field on the customer setup screen do? | Solution: This field has been around since before there was even an optimizer for Retail. The original purpose of the field was to trigger the forecaster to attempt to observe this soft restriction when creating the delivery. This field is not observed within the optimizer and deliveries that are forecast for day shifts are often taken on night shifts depending on transportation availability.
Since we now have time based restrictions on the restrictions screen in Customer Set-Up, it is better to use these fields to create any time-based restrictions for the optimizer to observe.
Keywords: Restrictions, Day, Night
References: None |
Problem Statement: Database changes from Version 7.5.0.x to Version 7.5.2.0. | Solution: The following illustrates the modifications and updates made to the Aspen Retail database tables in Version 7.5.2 versus Version 7.5.0.x.
New Tables:
The following section lists the new database tables that have been added to the existing Aspen Retail database. The tables are shown with its column names and its associated data types
TPS_TERMINAL2
TERMNUM NUMBER (10) NOT NULL,
MAXHOURS NUMBER (8),
CONSTRAINT PK_TERMINAL2$TERMNUM
PRIMARY KEY ( TERMNUM )
SYNONYM: TERMINAL2
TPS_TERMORDERSHOURS
SHIFTDATE
DATE
NOT NULL,
SHIFT
NUMBER (1)
NOT NULL,
TERMNUM
NUMBER (10)
NOT NULL,
COUNTHOURS
NUMBER (8),
CONSTRAINT PK_TERMORDERSHOURS$PRIMARYKEY
PRIMARY KEY
( SHIFTDATE,
SHIFT, TERMNUM )
SYNONYM: TERMORDERSHOURS
MODIFICATION OF TABLES:
The following section lists the tables that have been modified in the Aspen Retail database to reflect the changes in the Version 7.5.2
**** ALTERED TPS TABLES ****
TPS_TERMPROD
ADD
DENSITY NUMBER(5,3) DEFAULT 0;
**** NEW PROCEDURE ADDED TO RETAIL ****
ADDTERMUSEDUPHRS
MINUSTERMUSEDUPHRS
Keywords:
References: None |
Problem Statement: In Aspen Plus Reformer, the condenser of the stabilizer column has the specification of vapor and liquid, how can I change the model, so I only have a liquid fraction and the reflux? | Solution: This specification isn't currently one of the supported options for the stabilizer tower. However, there is workaround to specify the overhead liquid directly. To do this, follow the steps below:
1. Unhide EBScriptStab worksheet and add the following code in column H before connecting to the engine:
STABTWR.REFL_STDVOL.spec = CALC
VOLRR.BLK.VOLUME_REFLUX_RATIO.spec = CALC
STABTWR.RR_MOLES.spec = CONST
STABTWR.LDRW_31_MOLES.spec = CALC
USERRVP.BLK.USER_RVP.spec = CALC
STABTWR.TR_31_V_TEMP.spec = CALC
STBABV.BLK.IP4_VOLPCT.spec = CALC
STABREC.BLK.IC4_RECOVERY.spec = CALC
STABREC.BLK.NC4_RECOVERY.spec = CALC
STABREC.BLK.IC5_RECOVERY.spec = CALC
STABREC.BLK.NC5_RECOVERY.spec = CALC
STABREC.BLK.NC6_RECOVERY.spec = CALC
STABREC.BLK.BZ_RECOVERY.spec = CALC
STABTWR.LDRW_1_MOLES.spec = CONST
The STABTWR.LDRW_1_MOLES is the liquid mole rate from the overheads and it is made constant. The bottoms rate from the tower (STABTWR.LDRW_31_MOLES) is set to be calculated.
2. In EBScriptStab worksheet add the following line in the bottom of column L:
STABTWR.LDRW_1_MOLES
3. In the same worksheet add the following line to bottom of columns A through G:
STABTWR.LDRW_1_MOLES.spec = CALC
4. Unhide Registry worksheet and change the range in cell B254 by the following:
EBScriptStab!$L$2:$L$15
At this point, the user will be able to connect to the engine and select Stabilizer User 1 Script from the stabilizer options. On the stabilizer page, the reflux ratio and the overhead liquid mole rate will show up as blue and constant. You can reduce the overhead liquid rate to 0.1 kgmole/hr, but it probably isn't good to put it at exactly zero since that could cause problems with the EO.
Keywords: Aspen Plus Reformer, stabilizer column, liquid fraction, reflux.
References: None |
Problem Statement: What does the Holiday-Storm Plan Utility do? | Solution: The Holiday-Storm Plan Utility is a module that forecasts shipments based on the sales trends of a pre-existing reference period. The Utility can be applied to a customer, terminal, or zone. For example, if the user wanted to know how the sales for a particular terminal were going to be affected by a major storm, the user could apply the sales trends from a previous storm to predict the effects of the upcoming storm. This utility is particularly useful in forecasting seasonal aberrations such as holidays, storms, or special events. The user would specify the beginning date of the reference period. AFO will apply the sales trends from the reference period to forecast the sales for the planning period. AFO will create the reference period end date based upon the length of time for the planning period. The user would specify the planning period with the beginning date of the abnormal sales and the ending date of the abnormal sales. The Holiday Storm Planner Utility provided options for AFO to allow the user to set a default % for the fluctuation in sales for a customer with no sales history available for the reference period. For example, a customer has recently opened and has no sales trends from 11-24-2009. AFO will apply the default % for the change in sales when no other trend information is available. AFO gives the user the option of using the estimated sales or the actual sales to update the sales trends. AFO allows the user to enter a specific sales fluctuation for a particular product that has no history. For example, if the diesel sales for the period of 11/24/99 through 11/29/99 are expected to increase by 20percent and not 30 percent, the user can use the default of 20 percent for diesel if the there is no sales history for the reference period.
Keywords: None
References: None |
Problem Statement: How to transfer orders within Replenishment Planner. | Solution: The user has the ability to transfer an exported shipment from the original customer to the actual customer that received the shipment. This is very useful for accounting purposes and also makes it easier to correct delivery mistakes. Click on the Transfer icon. The user can also access the transfer function from the export menu. Select the exported shipment that the user want to transfer. Select the customer the user want to transfer the shipment
to. The entire shipment with the original information will be transferred to the correct customer.
Keywords: None
References: None |
Problem Statement: When a split shipment is exported, but one part of the split is canceled because the delivery was not made there is an issue with the station that did receive their part of the split. Because the entire split shipment is not in the system anymore, the run out date on the next order for that customer is changed to reflect the fact the order was not delivered.
An enhancement needs to be submitted for the ability to delete just one part of the split. | Solution: Until an enhancement is in place. A work around is for the user to make the adjustment to the split shipment in the Replenishment Planner. The user should first make the adjustment to the one part of the split that was not delivered. The next step is to adjustment the shipment that was slated for delivery to the other part of the split.
An enhancement needs to be submitted for the ability to delete just one part of the split. This will serve as a work around until one is implemented.
Keywords: None
References: None |
Problem Statement: What does it mean if the Override Warnings are on for Data Quality Manager? | Solution: The Override Warnings selection available under the Options\Override Warnings selection in the Data Quality Manager will prompt the user to make sure all shipments that have been delivered are marked correctly in the Shipments section of the Data Quality Manager screen. If this is turned on (a check-mark next to this option), the user will be prompted with two dialog boxes to removing them to flag delivered shipments delivered and assign the proper shift to any late shipments.
If this option is not selected, the user will not be prompted with these dialog boxes if they override an exception.
Keywords: Override Warning
References: None |
Problem Statement: How do I use the Security Utility? | Solution: Aspen Retail has four roles: Manager, Coordinator, Support, and Administrator.
These roles can each be assigned the following functions.
Aspen Retail functions for which you define roles include:
Function
If set, allows the ability to use the:
Carrier Setup
Carrier Setup function
Change Customer Number
Change Customer Number utility
Change Forecast Delay Cut
Change Forecast Delay Cutoff utility
Change Holiday Date
Change holiday dates.
Change Loadsize Fill %
Change Loadsizing Fill Percentage
Change Product Code
Change Product Code utility
Change Retain Buffer
Change Retail Buffer utility7
Change Runout Buffer
Change Runout Buffer utility
Change Shortload Cutoff
Change Short Shipment Cutoff utility
Change Terminal Number
Terminal Setup application
Cluster Setup
Cluster Setup application
Configuration Setup
Configuration Setup application
Credit Manager
Custom Credit Manager function; also see the Custom Credit Utility User?s Guide.
Customer Order Link
Customer Order Link utility
Custom Transport Attributes
Defining Custom Truck Attributes utility
Customer Setup
Customer Setup function
Customized Messages
Defining Customized Messages utility
Replenishment Planner
Replenishment Planner
Done For The Day
DoneForDay NT Service
Driver Setup
Driver Setup function
Exception Processing
Exception processing by the Data Quality Manager (DQM) function
GlobalRegion Matrix Generation
Generating a matrix by Global Region
Group Matrix Generation
Generating a matrix generation by Group
Group Setup
Group Setup function
HolidayGOStorm Planner Setup
Holiday-Storm Planner function
Holiday GOStorm Utility
Holiday-Storm Utility
Manual Info Collection
Manual Information collection function
Optimizer
Resource Scheduling Optimization (RSO) function
Product Setup
Product Setup function
Reforecast Utility
Reforecast Utility
Replace Trend Info
Replace Trend Info utility
Replacement Products
Change Replacement Products utility
Table Keys
Table Keys utility
Terminal Setup
Terminal Setup function
Trigger Date
Changing the Trigger Date on individual orders
Truck Setup
Transport Setup function
VRU Utilities
Change Voice Fulfillment Management Switches utilities
Assigning one or more of the 4 roles to the user id's allows the company to permit users whichever privelages should be necessary for their functions.
Keywords: Security, Role
References: None |
Problem Statement: Aspen InfoPlus.21 (IP.21) may not start when using Symantec Endpoint Protection, and the Aspen InfoPlus.21 Task Manager Service executable (tsk_server) may consume excessive CPU time degrading Aspen InfoPlus.21 performance. | Solution: Symantec Endpoint Protection may block Aspen InfoPlus.21 executable images from running with no error logs indicating that the programs were blocked from running.
PerSolution # 139438, place any executable processes related to Aspen InfoPlus.21 into the exclusion list for Symantec Endpoint Protection. You must place the names of the actual executables into the exclusion list; it is not enough to place the Aspen InfoPlus.21 code folder into the exclusion list.
If time is of the essence and you need to start IP.21 quickly, you may also proceed as follows:
· Open Device Manager (see screen captures below)
· Go to View and select “Show hidden devices”
· Then scroll down to Non-Plug and Play Drivers
· Open the BHDrvx64 driver and set the startup type to Disabled.
· Reboot the server
· IP.21 should start now
Keywords: Virus
Symantec
Endpoint
Exclude
Exclusion
References: None |
Problem Statement: What is the use of the Sustainable Shipment Report? | Solution: The Sustainable Shipment report prints the calculated largest sustainable load for a customer based upon the delivery window requirements. This report can be sorted by Group, Terminal, or Station. It allows a Dispatcher to review the size deliveries that can be expected depending upon the delivery windows required.
Keywords: Sustainable
References: None |
Problem Statement: How Do I import Manual Orders in RSO? | Solution: 1. Open the RSO. Select an order entry customer. (Customer Type = 1, 2, 3, or 4)
2. Open that same customer up in the Replenishment Planner and create an order which is must-go on the shift that you have open in the optimizer.
In RSO under the edit menu, select Import manual orders.(NOTE: Import Manual Orders will reject the order if the runout time is before the
current clock time on the server.)
Run the optimizer.
Repeat the process after the optimization has been run.
EXPECTED RESULTS
1. The order should be imported to the Available Shipments window before the optimization has been run.
2. The order should be imported to the Overflow Shipments window after the optimization has been run
Keywords: Manual Orders
Import
References: None |
Problem Statement: How does Loadsizing Filll % Work? | Solution: The goal of load sizing is to adjust the weight or volume of a given load to attain customer-preferred delivery conditions such as large shipment size or a given delivery window. Loadsizing Fill percentage is used to determine the size of transport selected for the delivery of an order.
For example, if Loadsizing Fill Pct is 85% and the total volume of a transport is 40,000 units, the loadsized volume of that transport is 34,000 units (40,000 * .85). As a result, the transport cannot be loaded with less than 34,000 gallons regardless of the transport?s capacity or compartment fill lines.
Keywords: Loadsizing
References: None |
Problem Statement: Why are records not getting passed through the SIIMPORT correctly? | Solution: Sales and Inventory data reported into Aspen Retail are handled depending on what type of information is being provided.
Sales-Only Data:
When a Sales Date is entered into the TCIF_SIIMP table, Aspen Retail will use this information to create a Book Inventory. This assumes that Sales information is being provided for the past 24-hour period and the Inventory is for the current time.
A record containing the unreconciled Sales Only data is written to the TPS_NEWINFO and has a status of '0' in the SIUPD_MODE in the TCIF_SIIMP table. When the data is reconciled, a record will be written in to the TPS_YESTINO table.
For example, a record with the following information provided into the TCIF_SIIMP table:
TCIF_SIIMP
STATNUM
50505
SALES_DATE
INV_DATE
INV_HOUR
INV_MIN
2/10/2002
PRODCODE1
100
SALES1
INVENTORY1
1650
PRODCODE2
200
SALES2
INVENTORY2
5568
ENTRY_DATE
2/11/2002
will signal to Aspen Retail to calculate a Book Inventory during Data Quality Management for 2/11/2002 at 00:00 (midnight).
An important element to consider here is Aspen Retail will use the last reported true Inventory as the time of the day which this 24-hour Sales reconciliation is intended to represent. If there has never been a real inventory time reported, the default in Aspen Retail is midnight (00:00).
Inventory-Only Data:
When an Inventory Date is entered into the TCIF_SIIMP table, Retail will use this information to create a Book Sales for the previous date. This assumes that current Inventory Figures reflect a reconciliation of the past 24-hour Sales cycle. A record containing unreconciled Inventory Only data is written to the TPS_NEWINFO and has a status of '1' in the SIUPD_MODE in the TCIF_SIIMP table. When the data is reconciled, a record will be written in to the TPS_YESTINO table.
For example, a record with the following information provided into the TCIF_SIIMP table:
TCIF_SIIMP
STATNUM
SALES_DATE
50505
INV_DATE
2/10/2002
INV_HOUR
6
INV_MIN
0
PRODCODE1
100
SALES1
INVENTORY1
1650
PRODCODE2
200
SALES2
INVENTORY2
5568
ENTRY_DATE
2/10/2002
Will signal to Aspen Retail to calculate a Book Sales during Data Quality Management for 2/9/2002.
Sales and Inventory:
When both Sales and Inventory information is entered into the TCIF_SIIMP table, Aspen Retail will use this information during the Data Quality Management phase of the dispatchers daily work process. A record containing unreconciled Sales and Inventory data is written to the TPS_CURINFO and has a status of '2' in the SIUPD_MODE in the TCIF_SIIMP table. When the data is reconciled, a record will be written in to the TPS_YESTINO table.
A record submitted into the TCIF_SIIMP table with the following information:
TCIF_SIIMP
STATNUM
50505
SALES_DATE
2/9/2002
INV_DATE
2/10/2002
INV_HOUR
6
INV_MIN
0
PRODCODE1
100
SALES1
1650
INVENTORY1
5000
PRODCODE2
200
SALES2
5568
INVENTORY2
5000
ENTRY_DATE
2/10/2002
will be processed in the Data Quality Management portion of Aspen Retail as an Inventory update for the 2/10/2002 and a 24-hour Sales reconciliation for 2/9/2004.
It is important to note that Aspen Retail is always expecting to see the Inventory for the Current date and the Sales for the previous 24-hour period.
Possible Problems:
If the external system were to submit the following information:
STATNUM
50505
SALES_DATE
2/10/2002
INV_DATE
2/10/2002
INV_HOUR
23
INV_MIN
0
PRODCODE1
100
SALES1
1650
INVENTORY1
5000
PRODCODE2
200
SALES2
5568
INVENTORY2
5000
ENTRY_DATE
2/10/2002
Aspen Retail will treat this as a Sales update for the 11th of February and will calculate a Book Inventory for the 11th of February. Because Aspen will use the time of the last real Inventory Update that occurred, this update could be interpreted (in this case) as a Sales Update and a Book Inventory calculated for 11PM of the 11th of February. This condition could cause significant problems, not the least of which would be potentially late deliveries because Retail thinks the Book Inventory for the 11th at 11PM is accurate.
Generally this case would be caught during the Data Quality Management phase; however, the dispatcher would need to be extra diligent.
In order to avoid this situation, it is recommended that all records submitted follow the format expected by Aspen Retail, i.e. current date inventory, and sales figures for the previous date. Various rules can be put in place either in the operational realm (i.e. the customer's reporting guidelines), or in the data interface to accommodate this requirement.
Keywords:
References: None |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.