question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
|---|---|
Problem Statement: How are Sales Percentage updated when using multiple tanks for products? | Solution: Each day sales and/or inventories are reported, the figures are broken down by tank for each product having more than one tank. The sales percentage figure that was stored for the previous reported period is then updated with a smoothing algorithm to avoid dramatic peaks or troughs. This new sales percentage estimate is then written to the tables for use the next day. The algorithm is designed to smoothly increase or decrease individual tanks percentages to avoid dramatically under- or over- forecasting for an individual tank.
Keywords: Sales Percentages
References: None |
Problem Statement: Is Windows Server 2008 R2 and SQL 2008 64 bit supported in Aspen Fleet Optimizer (AFO) V7.3? | Solution: SQL Server 2008 R2 64-bit on Windows 2008 R2 is supported, however Aspen Fleet Optimzer runs as a 32 bit application on the 64 bit platforms.
Keywords: None
References: None |
Problem Statement: If you are going to generate Matrix Entries with Aspen Retail and Mappoint, it is important to make sure you configure the options within the Mappoint Template that determine speeds to be travelled on different roads, basic units (miles or kilometers), and if you choose, the preference for certain roads within Mappoint. | Solution: The following screen shots will show you where these options are within Mappoint:
Keywords: Mappoint, Matrix, Generation
References: None |
Problem Statement: In which order should the 2004.1 to 2006.5 upgrade scripts be run? | Solution: The upgrade scripts for version 2006.5 are on the support website and can be downloaded. The upgrade scripts should be run in the following order:
Aspen.Retail.oracle.2004.01.00-07.07.04.upgrade.sql
Aspen.Retail.oracle.2004.01.00.maintainence.sql
Aspen.Retail.oracle.2004.01.00.cleanup.sql
Aspen.Retail.oracle.2006.05.00-2004.01.00.upgrade.sql
Aspen.Retail.oracle.2006.05.00.synonym.sql
Prior to running the upgrade scripts please contact the Retail support team to see if any additional scripts are needed for specific Retail installations.
Keywords: None
References: None |
Problem Statement: How is how safety stock is calculated? | Solution: First, safety stock is not treated the same way as pump stop the system is still treating the safety stock as extra inventory in the ground and not as an absolute run out point. This basically means that the system will try and use the safety stock number but if the delivery window is too tight or the system cannot allow for it to be used the system will still revert back to the actually run out point or pump stop.
Secondly, safety stock is not going to affect the run out point at all. The displayed run out point in Aspen Retail will always be the actual non-buffered run out point. Safety stock will only affect the must-go shift of the load.
Now here is how the safety stock functionality works. First the system will take the volume that is in the safety stock field and translate that into and hours number based on projected sales and sales segments. Once it has this hour number for safety stock it will compare the number of hours to the run out buffer hours. It will then apply the bigger number as the new run out buffer.
For example:
Run out buffer = 12 hours
Safety Stock= 5000 liters / 5000 liters average sales= 24 hours
The system will apply a 24 hour buffer.
Run out buffer = 12 hours
Safety Stock = 5000/ 15000 liters average sales = 8 hours
The system will apply a 12 hour buffer.
The system will treat this run out buffer as a normal buffer therefore if the 24 hour buffer from our first example can not be applied to the load because of window restraints the system will then cut this buffer in half and try a 12 hour buffer.
Keywords: None
References: None |
Problem Statement: What is Crossed Delivery Window? | Solution: A Crossed Delivery Window exists when the retain point is later than the runout point. The Resource Scheduling Optimization is restricted against delivering this shipment at any time. The user can correct this by decreasing the size of the shipment to create an acceptable delivery window and by making sure the transports have all available compartment configurations setup.
Keywords: None
References: None |
Problem Statement: What is the basic function of Replenishment Planner? | Solution: Replenishment Planner is the Fleet Optimizer module where the user can access, review, modify, and reforecast shipments. Whether a shipment is a split shipment or full shipment, an Order Entry or forecasted. Fleet Optimizer displays all customers' shipments in the Replenishment Planner. From within Replenishment Planner, the user can change a shipment's quantities or delivery shift. The user can flag shipments as 'dispatched' and 'locked' for a delivery shift, suspend shipments for customers on credit hold or even cancel a shipment if necessary. The user can also transfer a dispatched shipment from one customer to another and export a single shipment with the Replenishment Planner. For shipments being generated by Fleet Optimizer, Replenishment Planner provides reforecast functions when shipment quantities change or if a shipment needs to be matched to a different transport. The Replenishment Planner Window was designed to display a customer's pertinent delivery information. It allows the user to efficiently manage shipments by keeping track of order numbers, delivery dates, and shipment quantities.
Keywords: None
References: None |
Problem Statement: What's new in latest 7.4.00.17? | Solution: As part of our ongoing commitment to improve our documentation methodology and develop a more proactive communication strategy with our valued customers, we have implemented this news flash when new service packs are available. The news flash includes information on the newest release, the location from which clients can download it, and a brief description of the changes included as well as who may be affected and the potential impact it could create if not implemented depending on the client business practices.
The thorough documentation is available directly through the support website at http://support.aspentech.com
We hope you find value this new process and if you have any suggestions as to how it can be further improved to provide you benefits, please contact us by sending an email to: [email protected]. We truly value your relationship and will consistently seek for ways to improve our service and your satisfaction in the future.
Aspen Retail News Flash
Who is affected?
§ All current users of Aspen Retail versions 7.04.x or those planning to upgrade to versions 7.04.00.17
What is this pertaining to?
§ A new version of Aspen Retail, Version 7.04.00.17, is available for download via our support website. Instructions: Go to http://support.aspentech.com/, then go to the Service Packs link (if not login, then click Login). Then click on Aspen Retail link, and follow the dowaload instructions.
Summary of changes & potential impact to users running prior versions:
Fixed the Manual Order (ManOrd) service which was not handling shipments with past dates
Potential Impact - All Customers on 7.04.x could be affected. The ManOrd service was checking to see if an order was placed for a previously dispatched shift. In that case, the system would write an error code, and stop the order from coming in. The trouble occurred when emergency loads (for previously dispatched shifts), were placed while the order was in process. Unless your interface applications included functions that handle this ManOrd error code and notify the appropriate user, the dispatcher would not know that the new order did not successfully arrive for scheduling. It would effectively be lost in this case if it was not discovered.
How this issue is resolved in the new version - We have removed the check for dispatched or in process shifts.
A modification was made to the manual order import function contained within Optimizer application. In now also supports the use of the Site ID field. It previously supported only the station ID (STATNUM).
Potential Impact - Virtually all our clients are using station number (idcode setting = 1). The manual order import from within the optimizer was only working if the idcode in the Service.ini file was set to 1 (use STATNUM). In the case where the idcode was set to either Site ID (idcode=3) or reference number (idcode=2), the system was not correctly bringing in the order from within the Optimizer. (However, the Manual Order Service did handle these correctly.)
How this issue is resolved in the new version - The enhancement now allows the idcode in the Service.ini to be set to 1 (STATNUM compared to STATIONS.STATNUM), 2 (STATNUM compared to STATIONS.REFNUM), or 3 (SITEID compared to STATIONS.SITEID). This is the same as the existing handling in the Manual Order Service.
An LBD date and time stamp (LBD - Locked By Dealer) was added to the order-comment field in order dialog box
Potential Impact - When a forecasted customer modifies and locks an order via the Aspen Retail IVR, the IVR was designed to enter a note into this comment field as follows: LBD 11/04 19:52. The issue was that the date and time was not set in the order-comment as designed.
How this issue is resolved in the new version - The system now enters the note with the time & date-stamp as per design.
An eChain enhancement was made to allow users to enter load-confirmation information in any product order.
Potential Impact - If the user entered the confirmed product quantities in a sequence that differed from the sequence that existed in the customer setup screens, this was a problem. The information would be displayed and processed incorrectly.
How this issue is resolved in the new version - In this new version, we now match user entries by product code. Load confirmation information entered via eChain will now always be displayed and processed correctly.
Modifications were made to the manual order import within the Optimizer to correctly handle multiple order-records in ManOrd table that exist for the same unique order.
Potential Impact - Any Retail user that uses a PO number when placing order-entry orders could be affected. The N_INFO_FLG field was not being changed to false F in some cases, and was resulting in the same order to be brought in twice (in effect creating an extra order).
How this issue is resolved- It now processes orders with PO's correctly in all cases, the N_INFO_FLG will change to false (F).
The Terminal Cost History Report was modified so that terminal groups with more than 2 terminals will now correctly display data for all the terminals in the terminal group.
Potential Impact - When using this report, any terminal group with more than two terminals could have been affected. When there were more than 2 terminals the report was only calculating and displaying the results for the 1st two terminals.
How this issue is resolved in the new version - We now correctly calculate and display the data for all terminals in a group.
Fix for Weight Optimization retain date update.
Potential Impact - This impacts any customer using Weight Optimization set to 1. The retain time/date was not being updated after the load had been Optimized and Weight Opt made its adjustment.
How this issue is resolved in the new version - The retain date is now updated properly.
Modified the Order Generation algorithms to ensure controlling product is always shipped.
Potential Impact - This could impact all customers. There were certain cases where the optimal scheduled load did not include any controlling product. This case was generated based on the available transport constraints and when the optimal quantity of controlling product was either very low or disproportionate. Rather than sending less than a compartment of controlling product to maintain proportionality or sending a full compartment that would throw off proportionality, the system would not send any controlling product.
How this issue is resolved in the new version - The Order Generation algorithms now identify these cases and verify that controlling product is delivered on every scheduled load while continuing to ensure proportionality is maintained as closely as possible.
Fix to ManOrd table to display the correct UNIQUENUM
Potential Impact - If an order number was being supplied from a third party system, the third party order number was overwriting Aspen's order number (UNIQUENUM).
How this issue is resolved in the new version - The system now respects the third party order number without overwriting the Aspen Order number (UNIQUENUM)
Removed an unnecessary error code and string for successfully handled Man Ord records
Potential Impact - If a station is in process, when an order is placed, the system will generates an error string the advises that the order is in process and the N_Info flag is set to T. If the order is brought in via the optimizer, the N_Info flag would be set to F, but the error code and string would not be removed, giving a false impression that the order is still in process.
How this issue is resolved in the new version - The system will now clear the error code and string when the record is brought in via the optimizer.
Fix to concurrency issues when using the What If function
Potential Impact - In the Replenishment Planner, if the What if function was opened and closed, the in process flag for that station was being removed which could lead to concurrency problems.
How this issue is resolved in the new version - When the What if function is opened and closed, the in process status is respected.
Fix to concurrency issues when opening Customer Setup
Potential Impact - If a station was opened in Customer setup, and then the pick open station dialog box was opened and then cancelled, the in process flag for that station was being removed which could lead to concurrency problems.
How this issue is resolved in the new version - When a station is opened in Customer setup, and then the pick open station dialog box is opened and then cancelled, the in process status is respected.
Keywords: Retail Flash News
References: None |
Problem Statement: How do I stop getting orders moved between groups in 2006 | Solution: The ini setting AllowTermTransfer in the Internal.ini needs to be set to 0 to prevent this functionality from being available. There are some cases where this setting must be changed due to business processes regarding ghost terminals in alternate groups.
Keywords: AllowTermTransfer , Moving Orders
References: None |
Problem Statement: Can different users log into Aspen Retail with the same ID? | Solution: Aspen Retail will not work correctly if multiple users log into the system with the same user ID. Aspen Retail has added new functionality that will automatically reset accounts if the system detects that the same user ID is processing more than one account through two separate modules in Aspen Retail. This automatic resetting of the in process flags can and will cause concurrency issues. Any Aspen Retail users on version 7.4 and up need to have their own private login ID
Keywords:
References: None |
Problem Statement: How do I add a group in Aspen Fleet Optimizer? | Solution: 1. Click on the Group Setup button in the AFO toolbar. You can also select the Groups option from the File menu.
2. Click on the New button in the Group Setup toolbar. You can also select the option New from the File menu.
3. Type in the new group's id. Click on OK to confirm the creation of a new group.
You may edit existing groups by clicking on the Open button to view the list of existing groups, then highlight that group and click on OK.
Keywords: set up, groups, configuration
References: None |
Problem Statement: Why are all my loads going to overflow? | Solution: When you see all your loads (shipments) go to overflow, it is very likely that an incorrect change of a product code has taken place. If one changes a product code on a station level but never adds the change to the terminal that the station is delivered out of, you will see all loads go to overflow.
It is very important that, when doing product code changes, one makes sure that the changes are done both at the station level and at the terminal level. In other words, the products that are setup in Customer Setup must be available at the Terminal that the customer is delivered from.
Keywords: Product code change
Termiinal
References: None |
Problem Statement: How is the ADS calculated and where does the value come from? | Solution: Here is how ADS is calculated:
For a new customer, average daily sales information from the Customer Setup is used for one week. Once the sales trend is established, information from sales trend data is used for calculation. Now ADS is the average of the last 3 days sales information.
Keywords: ADS
Avearge daily sales
References: None |
Problem Statement: What types of Warnings can I see in the Warning Manager? | Solution: The Warning Manager can be used to help a dispatcher avoid a lot of undesirable circumstances in the scheduling of Fuel Deliveries. Warnings are generated as sales and inventory updates are processed or loads are confirmed as delivered or loaded. These following list of potential warnings is not comprehensive, but demonstrates the variety and usefulness of utilizing this essential tool in the dispatchers arsenal:
Tank Inventory Outage
Product Inventory Outage
Runout
Retain
Lock Reset
With active monitoring of these and other warnings that can be generated inside the Warning Manager a dispatcher can help to prevent the stock-outs and retains that often plague a poorly managed supply chain. The Warning Manager is accessed from the File Menu on the main Fleet Optimizer screen under File/Warnings. Warnings can be brought up for the date range desired and may be filtered/printed/marked resolved, etc.
Keywords: Warnings, Warning Manager
References: None |
Problem Statement: What is the process flow from TCIF_TIM to TCIF_SIIMPORT? | Solution: The TIM service and TCIF_TIM table are new in version 7.5. In previous version of the software the IVR and Echain wrote sales and inventory information directly into the TCIF_SIIMPORT table. Starting with version 7.5 eChain and IVR will now write this information into the TCIF_TIM table and the TIM service will now pass this information into the TCIF_SIIMPORT service. This change was made to accommodate by tank inventory and sales readings. Any custom interfaces can still write directly to the SIIMPORT table.
Keywords:
References: None |
Problem Statement: What version of AFO will support Oracle 11g? | Solution: The first version of AFO that will support Oracle version 11.2 will be V8. The latest released version 7.7.3 was tested on Oracle 10g Release 2.
Keywords: None
References: None |
Problem Statement: How do I turn on/off the ability to import Manual Orders inside the Optimizer? | Solution: There is an ini setting inside the Customize.ini that controls this ability.
The following setting is either 0 or 1:
ManualOrder=1
1 = ON -- meaning that you can import Orders through the Optimizer
0 = OFF -- the Import Manual Orders option in the Optimizer will be greyed out
Keywords: Manual Orders, Ini Settings
References: None |
Problem Statement: Can the Aspen Retail system handle both US customary units and Metric units in the same database? | Solution: The Aspen Retail system can handle both gallons and liters along with miles and kilometers. The Aspen Retail system does not store data in any specific measurement system. One group can be set up as gallons and miles and a second group can be set up as kilometers and liters. As long as the data for each group is consistent then system will function correctly because it looks at each group independently.
Keywords: None
References: None |
Problem Statement: Is it true that in version 7.5.2 the buffers will get cut up to 3 times maximum? Is it true that in version 2006.5 it will keep going until a 5 hour buffered window is achieved or till the buffers become zero and are discarded. | Solution: The buffer reductions are attempted up to 5 times. Once the window (runout-retain) is greater than sum of the total (reduced) buffers and the 5 hour minimum window requirement, the (reduced) buffers are applied to the runout and retain. If the window still isn't met after 5 attempted reductions, the retain and runout are used without buffering.
Release 2006.5 difference: In Release2006.5, if the window (runout-retain) is less than or equal to the minimum window requirement the attempt to apply buffers is abandoned immediately.
Keywords: None
References: None |
Problem Statement: What database tables need to be purged? | Solution: document attached
Keywords: purge
tables
database
References: None |
Problem Statement: What should the warnNumberDaysBeforeExpires setting be set to? | Solution: The default setting for this is 30 days this will allow for adequate time to turn around all of the paper work need to complete a new license file. The absolute lowest setting for this would be 5 days. This would allow for an emergency temporary license file to be issued.
Keywords: None
References: None |
Problem Statement: Unable to modify a transferred order | Solution: In Internal,ini set AllowTermTransfer=1
SPECIAL REQUIREMENTS
Another terminal has all products needed available
1. In RSO load group in which the customer/order belongs
2. Transfer a manual order in available shipments list to another terminal (suppose it's in group2)
a) Right click the highlighted order, select Transfer->Order
b) Click Yes when asked: Do you want to transfer the selected order to another terminal?
c) Select the target terminal in the Select Terminal dialog box and click OK
d) Click Yes if the dialog says: Shift for the terminal to which this order will be transferred is either dispatched or exported. Do you
still want to continue with the transfer process?
e) Click OK to confirm order transferred successfully
3. Keep the group open. Click Edit->Import Manual Orders, import the manual order in the terminal that you targeted, same shift.
4. Click OK on the Import Manual Orders dialog box
5. Open Exchange, use Exchange to generate a change record for the order, change quantities of product.
a) Click Manual Orders tab, click Add New Record
b) Select Changing Existing Record and then click OK on the Select Record Type dialog box
c) Open the customer and select the order, click OK
d) Click Edit and then modify the order quantities
e) Change the retain and runout time if necessary, make sure the runout time is larger the current system time (simply set it be tomorrow)
f) Click Save
6. If accessible, in the database, modify the change record to have source terminal zero in TCIF_MANUALORDERS table. Notice the N_INFO_FLG value is 'T'
7. Go back to the group , click Edit->Import Manual Orders to import the order
8. Click OK on the Import Manual Orders dialog box
9. Click Edit->Search->Order Number, search that order
10. Double-click the order, check the order information
EXPECTED RESULTS
Transferred order has been changed successfully.
Keywords: Transfer Order
Modifying Order
References: None |
Problem Statement: Why can I not add matrices larger than 100? | Solution: There are two ini setting that need to be changed from the default, which is 100. In the Customize ini file, change the setting max allowable trip time to equal 1000 and then do the same for the setting max allowable trip distance. This is probably set to the default 100 and so if the distance is more than a 100 the system will only allow 100 to be the max. Make sure that when you run the matrix generation you are overriding existing matrices, this should fix any 99's that may also exist.
Keywords: Matrix
References: None |
Problem Statement: How to Configure Short vs Split Setting in Customize INI File | Solution: shortVSsplit=60
A split creation parameter, expressed in terms of minutes, which
determines the load size. This setting is used to determine whether to deliver a short order or a split order
Acceptable Values: 1 to 180
Use: Increasing this value decreases the number of split loads; decreasing this value increases the number of split loads
Key words
Short vs Split
INI File
Keywords: None
References: None |
Problem Statement: Using the Customer Credit Restriction | Solution: When customer credit restriction = 0
When the order quantity is changed to a quantity greater than what is setup in customer set up , warning message appears that states tolerance is exceeded, do you wish to continue. when the user selects yes, the change is accepted, which is correct. If the user selects no, change is still accepted, this is incorrect, the system should go back to the order for user to change quantity within tolerance
Key words
customer credit
Keywords: None
References: None |
Problem Statement: What could be the cause of duplicate order numbers and lost shipments? | Solution: One major issue could be that the USESP ini setting is not equal to '1'. The USESP ini setting must be equal to '1' on every machine that is running any part of the Aspen Retail Suite. This is for users that are only using an oracle database. SQL users should have the setting equal to '0'
If the USESP ini setting is not equal to '1', please update the field to equal '1', shut down the machine and restart the application. This is extremely important
Keywords: USESP
Oracle
SQL
Lost orders
duplicate order numbers
References: None |
Problem Statement: How do I turn off the Toll Road option in Map Point? | Solution: Map Point does provide options for geo segment preferences, three options exist Quickest, Shortest and Preferred Roads. When you click on Route->More Options...(this provides the geo segment options only when there are waypoints exists), brings up 'More Route Options' dialog, then select the 'Segments' tab, where one can see the above mentioned options. Click on 'Preferred Roads' button enables other button 'Preferred Road Types...', when clicked on this button, will bring up a dialog named 'Preferred Roads', where one can set Toll Roads ON or OFF. Just for information sake I did give the above details on how to set Toll Roads ON or OFF.
When directly using Map Point for route calculation, one can turn Toll Roads ON or OFF as mentioned above, but certainly Map Point will not switch Toll Roads ON (when it was OFF) by itself.
The problem that the client might be facing is (Map Point automatically turn Toll Roads ON/includes Toll Roads, even though it is turned OFF) while generating matrices through Matrix Generator Utility. The reason for this is, Aspen Retail has an ini setting 'MapPointRoutePreference' under the [mapping] section in internal.ini, by default it will be '0' which means Quickest segment preference, when it is the Quickest, it doesn't matter whether you turned Toll Road ON or OF, it will always use the Toll Roads (if it finds that's the quickest route), it is same for Shortest (1) option also.
To really not to use Toll Roads while calculating matrices through Matrix Generator Utility, the user has to set MapPointRoutePreference to '2' (Preferred Roads) and then turn off the Toll Road option in Map Point and then run Matrix Generator Utility to get the matrices. It will work fine and no Toll Roads will be included.
Keywords: MapPoint
Toll Roads
References: None |
Problem Statement: What is the easiest way to find an order in RSO? | Solution: First click on the Edit menu inside the Resource Scheduling Optimization (Optimizer) toolbar. Next select either the customer number or order number option from the search menu. A dialog box will appear asking the user to enter the customer number or order number. Then enter the value the user wish to search. A search dialog box will appear that lists up to six of the customer's shipments. Each order number will be listed along with its position within the Resource Scheduling Optimization. An 'A' designates the shipment is in the Available Shipments List. An 'O' designates that the shipment is in the Overflow Window. A 'T' designates that the shipment is on a Transport. A 'D' designates that the shipment has been dispatched. To move to a shipment, the user can either highlight the shipment in question or click on the Go To button or double-click on the actual shipment. Aspen Fleet Optimizer will automatically take the user to wherever the shipment is located within the Resource Scheduling Optimization. From the Search dialog box, the user can view customer and tank information. To exit the Search function, click on the Close button.
Keywords: None
References: None |
Problem Statement: What tables store the Matrix data? | Solution: The trip matrix is stored in the TPS_MATRIX table for station to terminal trip times; the trip matrix is stored in the TPS_STATMATRIX for station to station trip times and stored in the TPS_TERMMATRIX for terminal to terminal trip times.
Matrix
trip times
station information
Keywords: None
References: None |
Problem Statement: Why do loads appear Blue in the Replenishment Planner? | Solution: If a Load Confirmation has been sent in from another System into Aspen Fleet Optimizer, the load will appear Blue in the Replenishment Planner.
Keywords: Blue Load, Replenishment Planner
References: None |
Problem Statement: How to configure Aspen Operations Domain Model (ODM) to be used in Aspen Data Source Architecture for ODM? | Solution: As mentioned in the Aspen Data Source Architecture Release Notes v2006, ADSA Version 2006 adds, among other new services, the Process Data (ODM) service.
The Aspen Process Data (ODM) service is used by Process Data applications such as Process Explorer and Web.21 to access data from Operations Domain Model (ODM). It supports static and dynamic data.
The configuration of the ODM Data Source the ADSA configuration tool is very simple:
? Add a DataSource with the Service Aspen Process Data (ODM)
? For the configuration, select the Advanced option and enter the Workspace Alias name. Typically Default_Database is used to connect to the Workspace that is loaded from the Database. ?Default_File? is used to connect to the Workspace that is loaded from local XML files.
Notice that for Advanced configuration no node name is specified. That is because to use Advanced configuration the ODM API must be installed on the client PC.
You can also find some information in the ADSA Client Config Tool help (or download the attached ADSA.chm, double-click to run this help file), Aspen Process Data (ODM) chapter.
When you use the ODM browser from the Web.21 Graphic Studio, you can drag and drop Tag Aliases or other Objects into Process Explorer. This does work also for classes other than TagAlias which are visible in the S95 browser.
Keywords: None
References: None |
Problem Statement: | Solution: DaysSupplyThreshold was added specifically to help Irving. Here is a description.
DaysSupplyTheshold= This value is used to keep stores tanks in proportion. The value is represented in number of days and can be set between 1-100.
Here is an example of how this works
Before Delivery
Tank A 5 days of supply left.
Tank B 3 days of supply left
DaysSupplyTheshold = 6
The first thing the system is going to do is come up with the largest most proportional load that it can. So lets assume that we have a 9000 gallon trucks and the system wants to bring 6600 gallons to Tank A and 2400 gallons to Tank B.
Next the system says how many days supply am I going to have after I delivery this load.
After the Delivery
Tank A 11 days of supply left
Tank B 15 days of supply left
In this case the days supply difference is 15-11= 4. Since 4 is less that 6 the system will deliver this load as is 6600 and 2300.
Lets assume that the days supply were different after the delivery.
Tank A 20 days of supply left
Tank B 9 days of supply left
In this case the days supply difference is 20-9= 11. Since 11 is great than the dayssupplythreshold of 6 the load fails and now the system will go back and look at the first short load fill level and see if that load will pass the dayssupplythreshold. If it does it sends it. If it does not it will cut the load again and see if it passes the dayssupplythreshold and so on until it finds a load that will pass. As a very general rule the closer in proportion you keep the tanks (ie the smaller the dayssupply threshold is) the smaller the loads will be and the great chance there is for a split load.
Keywords:
References: None |
Problem Statement: The Terminal field is missing from the TCIF_EXPORTORDERS Table | Solution: The Terminal field is no longer a required field in the TCIF_EXPORTORDERS Table. This field is now stored in the TCIF_EXPORT_ORDER_PRODUCT_DETAIL Table. It is then mapped to the TCIF_EXPORTORDERS Table by uniquenum.
Keywords: Terminal
TCIF_EXPORTORDERS
TCIF_EXPORT_ORDER_PRODUCT_DETAIL
References: None |
Problem Statement: What are the steps that I should take if my company was to incur a System Interruption? | Solution: See attached document
Keywords: database backup
system recovery
References: None |
Problem Statement: Where Can I Find the odbcerrorlog.txt and the dberrorlog.txt? | Solution: The odbcerrorlog.txt and the dberrorlog.txt can be located in the following directory
C:\Program Files\Common Files\AspenTech Shared\Settings
Keywords: -------- odbcerrorlog dberrorlog error logs
References: None |
Problem Statement: Why does it seem like the fitMatch setting is no longer working? | Solution: The fitMatch setting, formerly in the psoft.ini (7.4 and earlier), is now located in the Internal.ini. This setting was wrongly moved to the Customize.ini file in some version of the convert.exe program (designed to migrate ini settings from the former psoft.ini and psoftg.ini to the newer customize.ini, internal.ini, and services.ini). Since this setting is actually being read from the internal.ini, whenever the optimizer is run, this setting is automatically created in the Internal.ini if it does not exist and it may be given the default value (=1).
Therefore the fitmatch setting in customize.ini has no effect whatsoever and should be deleted to avoid confusion.
Keywords: fitMatch, Customize.ini
References: None |
Problem Statement: What are Yesterday's Sales in Data Quality Manager? | Solution: In Data Quality Manager and Manual Information Collection, Yesterday's sales are the Customer's sales for the previous 24 hour period ending at today's reported inventory time. These sales figures are collected daily in sales only and sales & inventory forecasting. With inventory only forecasting, yesterday's sales are calculated by Aspen Retail.
Key words
Yesterday's Sales
Data Quality Manager
Keywords: None
References: None |
Problem Statement: How should I set up Clusters? | Solution: Clusters are used in Aspen Retail, in addition to Clouds (super-clusters) to try to satisfy replenishment needs when for whatever reason one or more customers cannot receive a full delivery.
A Cluster is a group of 6 or less customers that are put together to be potential partners for split deliveries. A Cloud is a group of Clusters (because the Cluster limitation is 6 members).
When creating Clusters, the following factors should be considered:
? Delivery Constraints
o Time Restrictions at the customer sites
If one customer needs split partners but that customer can only receive night deliveries, putting him in a cluster of stations that can only receive day deliveries will not meet his split partner needs.
o Transportation Restrictions
The members of a Cluster should have significant overlap of available Transport options when possible.
o Product Loading Restrictions
If one customer has a product that cannot be hauled with other products, but the orders for this product do not fill a truck completely, the customer should have split partners that also need this product
o Terminal Restrictions
If certain customers can only be loaded out of specific terminals, they need to be paired with customers that can be loaded out of the same terminals.
o Geography
Cluster members should, when possible be in close proximity to each other, but as a rule should never require the truck to drive past the terminal to reach one another unless that distance is very short.
Manual Customer Cluster Needs
In addition to the above constraints, Clusters should also be created with the view that more options is always better. If Manual Order customers need a split partner, the order is for a fixed quantity and will need a partner that is either:
1. Forecasted so it can be adjusted to fit the remaining compartments on the truck
2. Another Manual Customer that is ordering for the remaining quantity to fill out the remaining compartments on the truck
In the case of ?1? above, it is useful to have as many forecasted customers as possible paired up with this Manual Customer to try to guarantee one of them will need a delivery on the same shift that the Manual Customer is ordering for. In the case of ?2? above, it is even more important that there are a number of options because the order size is fixed and it may be a lot harder to find a partner to match up with this order.
Forecaster Customer Cluster Needs
All of the above considerations are important for Forecasted Customers who need small deliveries as well. In addition to the above considerations, whenever creating clusters of Forecasted Customers, it is good to have a mix of Customers with both small tankage (high need for split deliveries) and large tankage (hopefully able to take the balance of truckloads that cannot be delivered to these small tankage sites). This will help provide the most flexibility possible for the problem customers.
Clouds
All of the above considerations should be taken into account when creating clouds as well. Clouds should be considered simply an extension of Clusters. Clusters are limited to 6 members, but there is no limit to the number of Clusters that can be assigned to the same Cloud. Certain performance considerations should be taken into account when putting Clusters into clouds (simply test this out with samples of optimization time as you increase the size of your Clouds), but in general all delivery constraints for Clusters should be observed as much as possible for Clouds.
u Keep this in Mind
Customers are more likely to be automatically Split with others when they are Clustered together with good partners. A lazy approach of simply adding a wide variety of Customers together into haphazard Clusters and adding all those together into Clouds will not be as effective as diligently aligning Customers with the same delivery requirements (when possible) into the same Clusters and extending those to Clouds where necessary.
Keywords: Clusters
References: None |
Problem Statement: What is the purpose of Last Contained restrictions under Product Setup? | Solution: The Last Contained section under Product Setup is a method of configuring the Optimizer to avoid loading specific products immediately after one another.
The matrix provided allows you to specify which Previous Product is not allowed to be followed by a Restricted (if selected in this matrix) Next Product.
Keywords: Last Contained
References: None |
Problem Statement: What is the Restricted field used for on the Truck Set-Up Screen? | Solution: The Restricted field is used to indicate if a Transport should be limited to carrying only deliveries for Customer's who are flagged with this Transport as the Default Transport on Customer Set-Up Screen.
Transports with this flag unchecked can haul deliveries for all Customers in addition to the ALL the deliveries for the Customers with this transport as their Default Transport.
Keywords: Restricted, Default Transport
References: None |
Problem Statement: How do I change a date in DQM if a user accidently enters and accepts a future date? | Solution: If a user accidently enters and accepts a future date in the DQM process the only way to change this is to go directly into the ORACLE/SQL tables and edit the date. The table that needs to be edited is the TPS_YESTINFO table. The INVDATE and FIRSTINV date fields need to be reset to the current date.
Keywords: None
References: None |
Problem Statement: How do I configure the MinSplitPercentage INI Setting? | Solution: MinSplitPercentage=50 (default)
The minimum percentage to which a transport must be loaded in order to deliver a split shipment to a customer
Acceptable Values: 0 to 100
Use: Use this option to reduce the instances when a split load is created that only utilizes a small portion of a truck. This option allows the enforcement of the minimum percentage a split load needs to meet in order to be a valid split load
Example:
MinSplitPercentage = 50
Total Truck Size = 10,000
If the split percentage is set at 50%, only shipments that fulfill 5000 (50%)
of the full transport are included. The application will not create a split
shipment for less than 5000
Key words
MinSplitPercentage
INI Settings
Keywords: None
References: None |
Problem Statement: What is the best scenario for the Safety Stock functionality? | Solution: The safety stock feature in Aspen Retail is used to increase the amount of product that is stored at the Retail sites. This feature, however, works in conjunction with all of the other aspects of Aspen Retail (i.e. load sizing, proportionality, must go shift, delivery window) therefore it is possible that the amount of stock that is onsite at any given time could lower than the safety stock setting. This setting is best used at stations that have relatively large storage as compared to the size of the delivery trucks. If the station's storage is too small to as compared to the truck size to accommodate the safety stock number then it will not be adhered too.
Keywords: Safety Stock
References: None |
Problem Statement: I have 2 Orders for the same customer, how come I can't make a split delivery out of them? | Solution: The thing to do in this circumstance would be to simply change one of the orders to contain all of the products of both deliveries.
Retail does not allow customer's to be split with themselves, but you could simply change one of the orders to contain all the necessary products and delete the second order and accomplish the same objective.
Keywords: Split Shipments
References: None |
Problem Statement: What error logs would be needed for analysis and detailed instructions on how to get them? | Solution: Within the Aspen Retail application there is an option under the help menu to 'email support'. When selected this automatically launches Outlook and automatically attachés the dberrlog.txt and the odbcerrlog.txt which are the two files that support needs to investigate any defect submitted. The user can also type a quick email describing the defect that they are submitting. This will also track what user submitter the problem so we know who to communicate with.
If this is not an option then Aspen Support will need the dberrlog.txt and the odbcerrlog.txt for defects submitted. These files are located in the C:\Program Files\Common Files\AspenTech Shared\Settings directory.
Keywords: error logs
odbcerrlog
dberrlog
References: None |
Problem Statement: How do I use Crystal Reports 10 with Aspen Retail 7.5.2.9 and higher. | Solution: Please also refernceSolution Document #110653 for information on the installation Crystal Reports.
Using Crystal Reports 10 with Aspen Retail 7.5.2.9 and higher.
Crystal Reports 10 should not be installed on the same machine that Aspen Retail is installed. Use a separate machine to edit the rpt files.
There are four crystal report template files installed with Aspen Retail.
GroupTenderReport.rpt
TerminalTenderReport.rpt
TruckTenderReport.rpt
OrderTenderReport.rpt
They are located in this folder:
C:\Program Files\AspenTech\Aspen Retail Suite\Aspen Retail
Copy the rpt files on to the machine that has Crystal Reports 10 on it. Launch Crystal Reports 10 and browse to the location on the rpt file that you want to edit Edit the rpt file and then save the file overwriting the original rpt file (you will promted for the format in which you wish to save the rpt file, it makes no difference which format is saved. Both are compatible) Copy the edited rpt files back to the Aspen Retail machine replacing the old rpt files. Make sure Crystal Reports settings are '1' in the Customize ini file. Run Aspen Retail as normal
It takes some time for Crystal Reports to open inside of Retail.
Keywords: Crystal Reports
rpt files
reports
tender reports
References: None |
Problem Statement: How Does The Holiday Storm Planner Work? | 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. Aspen Retail will apply the sales trends from the reference period to forecast the sales for the planning period. Aspen Retail 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 utility creates the forecast based on the reference periods actual historical sales compared to the total estimated sales for the same time.
EQUATION
PCTCHANGE = ((TotalActual - TotalEstimated) / TotalEstimated) * 100%.
TotalActual = Actual sales for all products on the reference period date. These values are taken from the TPS_HISTORY table.
TotalEstimated = Estimated sales for the reference period date. The demand planner calculates these values.
The totalestimated sales are a recreation of the forecast for the reference period. The system will actually recreate a forecast by passing historical data into the demand planner. The system then compares the totalestimated by product against the totalactual by product. The percentage increase or decrease is then applied to each individual product over the reference period.
Keywords:
References: None |
Problem Statement: V7.3 debugsymbols build for advanced log files. | Solution: Aspen Fleet Optimizer V7.3 has a special symbols that can be extremely useful in tracking down abnormal ends or crashes. The symbols build can be provided to customers if they run into problems that the normal error logs can not track down and help solve. The symbols build is installed the exact same way as the regular Aspen Fleet Optimizer software is installed. The symbols build will also require some additional Microsoft software to be installed. Please review the attachment to thisSolution for detailed set up information.
Attached should be a copy of the symbols build install and instructions on running the logging. Please let me know if you have any issues installing this build or getting the logging started.
Keywords: None
References: None |
Problem Statement: Why are the input fields inactive in mechanical shell and tube? | Solution: The reason for the input->exchanger geometry -> Shell Tab inputs being disabled within mechanical is the fact that the file most likely involved a transfer from thermal to mechanical
When this occurs, thermal will supply mechanical with a specific tubesheet layout.
Therefore, within mechanical, input -> exchanger geometry -> tubesheet layout -> tubesheet layout tab, the Tube layout option will display the Use existing layout as selected.
When this is selected, many of the input items related to the tubesheet layout, or any that may effect the design of a tubesheet layout, will now be disabled since the program should keep the existing layout.
To enter new specifications a new Layout must be created from :
Shell & Tube Mech -> Input -> Exchanger Geometry -> Tubesheet Layout -> Tubesheet Layout Tab and at the bottom of the window change the radio button to Create a new layout
Keywords: , inactive input fields, mechanical shell and tube exchanger
References: None |
Problem Statement: Is it true that when the cutting of buffers occurs, once either the retain buffer or runout buffer becomes zero that both buffers are discarded? | Solution: No, the buffer reduction continues as long as the sum of the buffer times is greater than zero. If one of the buffers values reaches zero but the other buffer is still great than zero then that buffer will be applied to the forecast.
Keywords: None
References: None |
Problem Statement: Can the Optimizer break apart splits if they don't fit on any trucks? | Solution: The ini setting
breakUpOverflowSplits=1
in the Internal.ini tells the Optimizer whether or not to break apart Split Loads before sending them to the Overflow if they do not Optimize onto trucks Automatically.
=1 tells the Optimizer to break them up
=0 tells the Optimizer to leave them together as a Split Load
Keywords: Split Loads, Overflow
References: None |
Problem Statement: Alternate Weight by Axle Configuration | Solution: Summary
This document outlines the procedure for configuring weight by axle when the actual weight contributions per compartment and maximum weight per axle is not available.
Data Requirements
- Net Weight - The weight of the empty equipment (truck and trailer)
- Max Gross Weight - The maximum weight of the equipment when loaded with product
- Product Density - The density for each product. This density can either be set at Product Level (in Product Setup) or at each individual Terminal (in Terminal Setup)
- Max Volume per Compartment - The maximum amount of product allowed in each compartment
- Minimum Volume per Compartment - The minimum amount of product allowed to be loaded into each compartment
Procedure
Setting Min and Max per Compartment
1. Open Aspen Retail
2. Go the compartment screen in Truck setup
3. Make sure that you are viewing the largest fill line for the truck
4. Take the largest quantity from the fill line for each compartment and enter that value as the maximum for each product.
5. Enter a minimum for each compartment. This minimum should be a volume that is acceptable based on your business regulations and guidelines
6. Click OK and close compartment screen
7. Repeat steps 1 - 6 for every truck in the model.
8. End of flow
Setting Max Weight per Axle
1. Go to the internal.ini and set weightbyaxle = 1. If the user would like the orders assigned to be rounded, set the weightbyaxle = 100.
2. Save and close the internal.ini
3. Open Aspen Retail and Truck Setup
4. Enter the Net Weight for the equipment
5. Enter the Max Gross Weight, note that the Max. Product Weight.
6. Open the compartment screen
7. At the top of the screen, Set the Number of Axles equal to the number of compartments for the truck
8. Sum the maximums for each compartment to get the Total Maximum for the products, note this value.
9. In the weight contribution section of the screen, enter 100 for each compartment for each axle per compartment. The set-up will look like below:
10. Perform the following calculation for each compartment:
Mv = Max Volume per compartment
Tv = Sum of all max volumes per compartment
Mpw = Max product weight
Formula - (Mv/Tv) X Mpw = Max Weight per Axle
11. Enter the Max weight per Axle for each axle using the calculation above
12. Click Ok to close compartment screen
13. Repeat steps 3 - 12 for each compartment
14. End of Flow
Entering Product Density
1. Open Aspen Retail and Product Set-up
2. Enter a product density in the field called Density. This density should be updated on a regular basis.
**Alternatively this product density could be added in Terminal Set up To do this:
1. Open Aspen Retail and open Terminal Setup
2. Double click on the first product in Terminal Products section, this will open the Terminal Product screen
3. Enter the product density in the field called Terminal Density
4. Click OK to close
5. Repeat this for each product in the terminal setup
6. End of flow
Optional Configuration Items
If desired users can force Aspen Retail to use each compartment on a truck when forecasting and scheduling orders by clicking on the Must Use flag in the compartments screen.
Checking this box will also check the weight focus check box.
Verifying Weight By Axle Configuration
1. Once the components of the weight by axle configuration are completed, open RSO and load a group for which you believe all trucks and products to be configured correct.
2. During the loading is there are any trucks in the Group that do not have the correct weight by axle configuration the following dialog will be displayed:
3. If this error appears, click no and re-validate that all trucks are set-up with a weight by axle configuration
4. Once verified that the configuration exists, reload RSO.
5. The user can either optimize or drag a single order onto a truck.
6. Open the order detail and you should see that Total Weight is now displayed
7. End of flow
Keywords: Weight by axle
Product density
References: None |
Problem Statement: This knowledge base article describes the typical problems that may go wrong during an upgrade of Aspen Fleet Optimizer. | Solution: Aspen Fleet Optimizer upgrades are complex and problems may occur in several places if the upgrade is not planned properly. Here are a few of the most common problem areas and best practices to avoid them.
License File Issues:
The best way to avoid license file issues is to send a current copy of your license to the AspenTech support staff. This will allow us to review the new license file to ensure that it contains the correct keys and is configured to work in your environment.
Scripting Issues:
The Fleet Optimizer upgrade scripts are standard scripts which should run against any standard Aspen Fleet Optimizer database. In order to ensure that these scripts will run correctly we recommend that prior to running the scripts at your site a full database dump is provided to the AspenTech support staff. AspenTech will then run the upgrade scripts against your database to ensure they correctly upgrade the database table structure. AspenTech support will e-mail any modified scripts that are need directly to the client.
It is important that the database dump sent to AspenTech contains recent production data as well as database users to ensure that scripts tested against your database in our environment will work when they are executed against the database in your environment.
Software Application Issues
AspenTech thoroughly tests Aspen Fleet Optimizer using simulated user testing for each release test cycle. Our simulated user testing is conducted largely based on actual test cases received from our customers. AspenTech would like to incorporate any test cases that relate to the dispatch processes specific to your site into the testing phase of our planned release cycle. Please send your test cases to AspenTech support.
Ini File Settings
It is important to ensure the ini files used in your testing of Aspen Fleet Optimizer correctly match the ini files that are used in production.
Keywords: None
References: None |
Problem Statement: How does Aspen Fleet Optimizer calculate Must Go vs. Can Go work? | Solution: Each load has a delivery window composed of the earliest and latest times the load may be delivered to the site. For inventory management accounts, these times are calculated; for order entry accounts, the window is given or based on the requested shift. The shift running times for each truck are setup. Delivery time restrictions for the customer, driving times, loading times, and unloading times are also setup. Given these parameters, the system determines for each load which delivery shifts can be utilized to perform the work. The system prioritizes doing work on a shift if the shift being optimized is the last shift (Must Go) on which the load can go satisfying all timing requirements.
If there is not enough Must Go work to fill out the shift, the system will look for Can Go work (work that can be done on the shift but can also be done on a future shift) to fill in the gaps
Key words
Must go
Can go
Keywords: None
References: None |
Problem Statement: Where can I locate the Initialization (INI) Files for Aspen Fleet Optimizer | Solution: The INI files are located on your system in the following directory:
C:\Program Files\Common Files\AspenTech Shared\Settings
Warning: INI files are registered at this location during Aspen Retail installation. Moving them from this location will cause the system to function incorrectly
Key words
INI Files
Installation
Keywords: None
References: None |
Problem Statement: What does the Warning Manager do? | Solution: The Warning Manager allows you to view warnings that have been generated when new Sales and Inventory updates have been processed relating to potential Retains and Runouts. Using this tool a dispatcher can help to make sure upcoming dispatched or undispatched shipments are adequately handled as new information comes in.
Keywords: Warning Manager
References: None |
Problem Statement: What are the issues with Warning for Manual Accounts? | Solution: This warning is intended to help prevent retains at manual order stores. This logic is dependent upon having correct information for average daily sales for manual order customers. Obviously if sales are incorrect or zero this logic will not work correctly and will cause the warning to occur whenever multiple loads are place at one customer site for the same shift or back to back shift. Currently, this logic cannot be controlled by and .ini setting. If you do not have the correct information available for average daily sales, then it is suggested that you substitute the tank size into the average daily sales. This should help avoid needless warnings.
Keywords: Replinshment planner
Warning
References: None |
Problem Statement: Is there a way to determine if a split order was created by the user or by the system? | Solution: Yes - examine the title bar on the order form. If the optimizer generated the split order, the title bar will contain the phrase Forecasted (SPLIT). If the user generated the split order, the title bar will only say SPLIT.
eyWords:
Keywords: None
References: None |
Problem Statement: How to populate Global Optimization matrix tables? | Solution: The process of generating all the matrixes for global optimization may take a long time when using Mappoint. To help alleviate down time on a production database a back up database can be used and the following tables need to be transferred into the production database.
TPS_STATMATR-station-to-station information.
TPS_MATRIX - terminal-to-station information.
TPS_TERMMATR -terminal-to-terminal information.
Please work against a restored database backup to generate the matrix data, and then import the matrix data from the restored database into their production database.
Keywords: None
References: None |
Problem Statement: How do I configure the DoShiftWork INI setting? | Solution: DoShiftWork =1(Default)
The DoShiftWork setting is used to load-balance terminals and transports when fulfilling shipments. Load balancing is achieved by switching orders from terminals with less capacity to terminals with greater capacity. This setting allows you to determine whether RSO will automatically switch orders from one terminal to another to better load-balance terminals and transports
Acceptable Values:
0 = Off; RSO will not automatically shift work from one terminal to another terminal. No load-balancing takes place.
1 = On (default); RSO will automatically shift work from one terminal to another terminal
Use:
In most cases, AspenTech recommends that DoShiftWork is set to 1(On)
Consider setting DoShiftWork to 0 (Off) if RSO sources orders from an alternate
terminal (other than the default terminal) with undesirable consequences, such as
increased trip time or increased cost.
If you are running optimization for groups using Best Buy (BestBuy =1 (On) in the
TPS_GROUPS table), set DoShiftWork to 0 (Off). This ensures that DoShiftWork
will not move work from a terminal for Best Buy cases. If DoShiftWork is set to 1 (On), the RSOSolution may not be optimal
Note: The Best Buy value is defined using Group Setup
Key words
INI
Keywords: None
References: None |
Problem Statement: Creation Date: 29-Jun-2004 06:57PM
Applicable Version(s)
Problem Statement
Can Retail be configured to breakup split shipments if they don't get scheduled onto a truck? | Solution: Yes. To configure Retail for this functionality, you need to change the ini setting breakupoverflowsplits=1 in the internal.ini
Keywords: Split Shipments, Overflow, RSO
References: None |
Problem Statement: What does the sales spike percentage do in product setup? | Solution: When this value is met or exceeded for two straight days AFO will put a much higher emphasis on the most recent trending and much less on the past historically trending. The purpose is to have AFO react more or less quickly to spikes or decreases in sales.
Keywords: None
References: None |
Problem Statement: How can I make sure Split Shipments do not occur? | Solution: The best way to make sure Aspen Fleet Optimizer will not create Split Loads is to make sure all the Cluster's have been removed from the database. The most comprehensive way to perform this is to go through the Cluster Set-up Screen and remove all of the clusters from the database. It is possible to use queries in the back-end of the database to remove them more quickly, but this should only be done with the assistance of Aspentech Personnel.
Keywords: Removing Split Clusters
References: None |
Problem Statement: What is a Short Shipment? | Solution: A Short Shipment is a shipment of fuel that is less than the full carrying capacity of a transport. The Short Shipments check box determines whether or not a customer is authorized to receive less than a full load of product.
A short shipment is only calculated for a customer if the Short Shipment check box is checked and the customer requires a short load to meet a preferred delivery window (Short Shipment At) requirement. During load sizing, if there are several transport sizes at a terminal and the short loads option is off, Aspen Retail does not create short loads on a specific transport. It still sizes shipments from the largest full shipment transport to the smallest full shipment transport available at a terminal.
Keywords: Short Load, Short Shipment
References: None |
Problem Statement: What are the proper conditions for Hard and Soft Time Restrictions? | Solution: In Aspen's Customer Setup Panel it is possible to assign a number of restrictions for a Customer. One of the primary restriction types is the Time restriction. The system allows a wide variety of when and how a station can be prevented from being scheduled to receive a delivery.
Hard Restrictions -
The Fleet Optimizer will never schedule a delivery inside this window automatically. It is possible to manually place deliveries onto trucks to override these restrictions; the DC will be given warnings to alert them when they are doing this.
Conditions for a Hard Restriction would be issues concerning Safety, Legal Regulations, etc.
Soft Restrictions -
The Fleet Optimizer views Soft Restrictions as preferences and attempts to avoid scheduling deliveries inside these restricted windows when possible. If however, there are no other available windows, or all the available windows have been filled with other deliveries, the Fleet Optimizer will automatically schedule loads inside these restricted windows.
Conditions for a Soft Restriction would be preferences often expressed by Station owners as to when they would like to receive deliveries, traffic issues (depending on the severity of the traffic congestion, this could warrant putting it in as a Hard Restriction), etc.
Keywords: Hard Restriction, Soft Restriction
References: None |
Problem Statement: How does one retrieve longitude and latitude data from MapPoint and enter them into Aspen Retail? | Solution: Here are the steps to get Longitude & Latitude from Mappoint
Open up Mappoint
In the Navigation Toolbar, type in the address of the location in the drop-down box with the texst Type place or address highlighted once Mappoint opens.
Click the Find Button
If Mappoint finds the address automatically, goto step 7, if not, goto step 5
Find the location closest to the address in the list of possible addresses Mappoint present you with, then double-click on it. This should take the map on your screen close to your desired location.
Find you location by locating landmarks such as majot highways and other easily recognizeable items on the map - once you are close enough to approximate the location, right-click on it and select the option Route - add as stop (this should mark the location with a number so you can easily find it for the next step.
Go to the Tools Menu and select location sensor - this should bring up a small rectagonal box on the bottom of the screen with the Latitude and Longitude
Move the mouse cursor over the location you marked (or that Mappoint automatically located) and write down what the numbers are for the Latitude and Longitude.
These can be entered into the Aspen Retail Customer Set-up Screen in the field's labeled Lat/Longitude. When entering the longitude, it is important to enter a - sign before number. This is because the longitude is West (which is represented as a negative - for future reference, Latitudes are positive if they are North of the equator and negative if they are South, Longitudes are positive if they are East of the Observatory in Greenwich, England, negative if they are East of it.)
For Canadian addresses, one might find the following tip helpful. http://www.infinitegravity.ca/MapPoint.asp. Note that AspenTech has no relationship with that website. The link is provided simply for our customer's convenience and we have not verified that tip ourselves.
Keywords: MapPoint
Longitude
Latitude
GPS
References: None |
Problem Statement: What deliveries are included in the delivery log? | Solution: In Data Quality Manager, the Delivery Log includes all the loads that were last forecasted for the Customer. Expected deliveries are prompted so the user may verify that the loads that should have been delivered between the previous and current inventory measurements were actually delivered with their expected quantities of fuel. Updating expected deliveries to reflect actual deliveries is important for reconciliation but especially critical for sales only or inventory only forecasting
Key words
delivery log
Keywords: None
References: None |
Problem Statement: The Data Quality Manager appears to be sorting the stations in some unusual new order since our upgrade to 7.7. | Solution: In version 7.7 we added the ability to sort the stations by SiteId. This is particularly useful for customers who have many sites tied together through common SiteIDs. If you are one of our customers who does not use the SiteId field to tie multiple customers together or you would simply prefer to have the Data Quality Manager sort through the list of stations by the Statnum, we have created an ini setting to allow you to swap between methods at your discretion.
[DQM]
SortStations=0
This setting controls how the Data Quality Manager will sort stations when processing. If it is set to 1, it will sort by the statnum field. If it is set to 0, it will sort the stations in DQM by the siteid field (this method is particularly useful if tank station modelling is being used).
Keywords: SiteID, DQM, sorting
References: None |
Problem Statement: Why is my station not showing on the Map? | Solution: If the numeric id for a customer or terminal is greater than nine (9) digits the customer and terminal cannot be displayed on the map. This issue occurs when trying to view the customer or terminal on a map using View | Customer from the Customer Setup window, or View | Terminal from the Terminal Setup window.
To work around this issue, from the main Aspen Retail window click Mapping | Plot and select either Plot Stations or Plot Terminals.
Keywords: Map Point
Customer Setup
References: None |
Problem Statement: Why would fill transport pick the most expensive transport when forecasting? | Solution: The system does not start looking at costs until the shipments are in the optimizer. When the system is forecasting shipments, it will use any of the transports that are in the system and that are not mark as restricted. The system tries to use the largest transports first and as soon as the delivery window is met the system then stops. The shipments are then best fit based on what transports are on duty in the optimizer, cost and then loadsize.
Keywords:
References: None |
Problem Statement: What is the best way to handle overflow loads in the optimizer? | Solution: A Problem Shipment is an overflow shipment that could not be assigned to a shift because of a restriction conflict or delivery window problem. To help determine why a shipment is a problem shipment, the shipment must be manually forced onto a transport then its delivery timeline can be checked in Gantt view. While manually assigning an shipment to a transport, the 'Add Order to Transport' window will appear. This window displays any warnings and/or restrictions when a user tries to force a shipment onto a transport. Once the shipment is manually assigned to a transport, it can be displayed in Gantt view. Within the Gantt view, the delivery timeline for the problem shipment is displayed at the bottom of the window. The user can then view the cause for the problem shipment.
Keywords: None
References: None |
Problem Statement: Which .ini file does the Forecast service look at? | Solution: The services.ini contains these two entries:
[Forecast]
IdCode=1
Period=5
StartTime=501
StopTime=845
Timer=15
[ForecastService]
IdCode=1
Period=1
StartTime=441
StopTime=715
Timer=0
The forecast service is looking at the setting call forecast. The setting call forecastservice is an obsolete setting that is no longer used by the Retail system.
Keywords:
References: None |
Problem Statement: How does the short shipment value function? | Solution: The Short Shipment at Value is a time variable that designates the threshold window length, in hours, which will initiate load sizing for a customer's shipment. Loadsizing is a function of Aspen Retail that will decrease the payload of a shipment 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 Short Shipment at Value of 5 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 Aspen Retail will forecast the customer's shipments on the full size shipment. If the 10,000-gallon shipment is defined with a 4-hour delivery window, then Aspen Retail will initiate load sizing to find a smaller shipment. Load Sizing will only occur if the short loads approval check box is selected.
A Short Load is a shipment of fuel that is less than the full carrying capacity of a transport. The Short Load Approval check box determines whether or not a customer is authorized to receive less than a full load of product. A short load will only be calculated for a customer if the Short Load Approval box is checked and the customer requires a short
load to meet delivery window requirements. During loadsizing, if there are several transport sizes at a terminal and the short loads option is off, Aspen Retail won't create short loads on a specific transport. It will still size shipments from the largest full shipment transport to the smallest full shipment transport available at the terminal.
Keywords:
References: None |
Problem Statement: What is the INI Configuration for Aspen Fleet Optimizer TripTime Matrix? | Solution: The following instructions should be used create the Matrix Data you need:
Use the following setting in the Internal.ini
[Mapping] section
Enablemapping = 1
MapPointProgID = MapPoint.Map.EU (for the European version of MapPoint) or Map.Point.Map.NA for the North American version of MapPoint)
MapPointAppID = MapPoint.Application.EU (for the European version of MapPoint) or Map.Point.Map.NA for the North American version of MapPoint)
Inside Mappoint, Make sure the following is adjusted if necessary:
For information about matrix generation settings, see the INI Settings chapter in the aspenONE for Fuels Marketing Administration Guide.
To avoid a potential problem with erroneous trip times in Microsoft MapPoint, set the Start Driving at and End Driving at fields in MapPoint to span a 24-hour period,
For example 6:00 AM to 6:00 AM. This prevents erroneous trip times caused by the resting period between driving times.
For example, assume the following conditions: the Start Driving at time is set to 8:00 AM and the End Driving at time is set to 6:00 PM and you have a 1 hour trip that starts at 5:30 PM. In this case, MapPoint calculates the total trip time not as 1 hour but as 15 hours (30 minutes (5:30 PM to 6:00 PM) plus 14 hours (the resting period between driving times) plus 30 minutes (8:00 AM to 8:30 AM)).
After this is configured , please follow the directions below this will enable you to generate the Matrices to your business needs:
To Generate a Matrix:
From the Aspen Retail main dialog box
1. Select Mapping | Matrix Generation. The Matrix Generation dialog box appears.
2. Select a Group for which you want to create a matrix. Then select from the following options:
Station - Station
Calculates trip times and distances from all stations to stations in the selected Group.
Station - Terminal
Calculates trip times and distances from all stations to all terminals in the selected Group.
Terminal - Terminal
Calculates trip times and distances from all terminals to terminals in the selected Group.
Group By Zone
Creates matrices between stations grouped in the same zone (or territory). Matrices are not created between stations in different zones.
Do Bi-Directional Lookups
Calculates the driving time and distances separately for trips to and from a destination. Select this option if the one-way drive times and distances are different between two points. Do not select this option if both one-way drive times and distances are the same.
Override area
Options to override the existing matrices
Auto-Overrides existing matrices for stations whose matrix information was created automatically.
Manual-Overrides only existing matrices for stations whose matrix information was entered manually.
Both-Overrides all existing matrices.
None-Does not override any existing matrices. It only generates matrix information for stations that are new.
3. Click Generate to create the matrix.
Keywords: Matrix
Trip Times
References: None |
Problem Statement: How does Fleet Optimizer forecast loads? | Solution: Calculating the Runout Point
The first stage in the forecasting process is determining the point in time when a customer will run out of the first product. The runout point is calculated by subtracting forecasted sales from a reported current inventory level. The forecasted sales are generated through the use of sales trends, average daily sales, and sales constants. With a noted current inventory level, Fleet Optimizer will subtract forecasted sales by product on an hour-by-hour basis until the
runout point of the first product is determined.
Calculating the Optimal Shipment
Once the runout point is calculated, Fleet Optimizer determines how much product is left over in the other tanks. Knowing the amount of left over product at the runout point enables Fleet Optimizer to generate the optimal shipment that will balance inventory levels to reflect sales rates at the runout point. The optimal shipment will be the perfect shipment accurate to the gallon/liter that will restore proportionality in the tanks.
Matching the Optimal Shipment to a Transport
Once the optimal shipment is determined, Fleet Optimizer will match that shipment to a transport assigned to the customer. A four compartment transport can be matched with four products in 256 different ways. Fleet Optimizer determines the best match for the transport that most closely resembles the optimal shipment quantities. Transport matching guarantees that all shipments created by Fleet Optimizer are viable shipments that can be loaded and onto existing transports.
Calculating the Retain Point
Once a shipment is matched to a transport, Fleet Optimizer can then determine when the matched shipment can fit in a customer's tanks. The point in time when a matched shipment can first fit is known as the retain point. The retain point is calculated by forecasting when a customer's tanks will be sufficiently empty to hold each of the products ordered on the shipment. The latest of these times is the time when all products on the shipment can be held in the customer's tanks. This is the retain point.
Keywords: None
References: None |
Problem Statement: What does Missing Sales mean in Data Quality Manager? | Solution: Missing Sales are sales figures a Customer has failed to report for a specific day. In Data Quality Manager, Aspen Retail will prompt the user to update missing sales with actual sales figures for the days for which no sales information exists. In Sales and Inventory Forecasting mode, missing sales do not generate an exception. In Sales Only or Inventory Only Forecasting modes, missing sales will generate an exception. In all modes of forecasting it is important to update missing sales with actual sales because Aspen Retail utilizes actual sales figures to develop trends for forecasting.
Key words
Missing Sales
Data Quality Manager
Keywords: None
References: None |
Problem Statement: How do I configure the numMinBetweenTwoDeliveries INI Setting? | Solution: numMinBetweenTwoDeliveries=30 (Default)
Description: The minimum number of minutes between delivering
multiple shipments to the same customer
Acceptable Values: Any reasonable number of minutes you want
scheduled between deliveries to the same customer on the same day
Use: Use this option in situations when a customer is receiving multiple
loads per shift. This option ensures that the deliveries will be
scheduled a certain time apart so that drivers do not arrive at the
same time at the same site
Key words
INI Files
Keywords: None
References: None |
Problem Statement: How does the TPS_NEWTREND table get populated? | Solution: The TPS_NEWTREND table is populated every day when a station gets forecasted. When the station is forecasted either by the FORECAST NT Service or by the Data Quality Manager, the sales information for that day is written directly to the TPS_NEWTREND (i.e. TRENDS) table. This process is updated daily and the system will store a rolling 4 weeks with of trend data which is then used for forecasting.
Keywords: Trends
TPS tables
Forecasting
References: None |
Problem Statement: What does Forecast Delay do? | Solution: The Forecast Delay Utility in the Utilities menu is to allow the Customer to set the system up to wait until a specified point in time before the Forecast Service would process either the Sales and/or Inventory on its own (thus creating a book figure for the missing piece.
Keywords: Forecast Delay
References: None |
Problem Statement: What is the Inventory Proportionality Report for? | Solution: The Inventory Proportionality report prints the degree to which a customer's inventory is in proportion to its sales. This report can be sorted by Group, Terminal, and Station.
Keywords: Proportionality
References: None |
Problem Statement: There is no option in Aspen Shell & Tube Mechanical for the nozzle profile connections Fig. UW-16.1 (f-1), (f-2), (f-3) or (f-4). How can I specify them? | Solution: You have to assume a standard reinforcing ring that will have the equivalent area as depicted in Fig. UW-16.1, without exceeding the code reinforcement limits.
Connections (f�-1), (f�-2) and (f�-3) can be thought of as depicted below, reinforcing in red containing the same area as the actual profile in figure UW�-16.1:
Connection (f-1) should be very similar to a repad. Connections (f-2) and (f-3) not so much (more manual work). (f-4) is the same as no repad passing the reinforcement rules (thick walls), or can also be without reinforcing pad by selecting No to the reinforcing ring design option.
Then, the nozzle code calculations can be changed manually by adding the sketch number.
Keywords: reinforcement, nozzles, repad
References: None |
Problem Statement: How does Iterative Truck Match work? | Solution: [IterativeTruckMatch] Assigning product(s) to compartments on a truck:
Iterative truck matching logic is used to enhance optimization performance by
limiting the number of possible product/compartment combinations that the RSO
must calculate
Use iterative truck matching when you are scheduling more than 100 transports,
some of the transports contain more than six compartments, and RSO
performance is slow
The iterative truck match logic is used when the system encounters a case
where both the NumCompart and NumProducts values are met or exceeded
Key words
Iterative truck match
INI File
Keywords: None
References: None |
Problem Statement: Aspen Shell & Tube Mechanical (Aspen TEAMS) Main Material Search function Disabled under Input | Materials upon opening the application and prior to any input. | Solution: Main Material Search function will be enabled and loaded with appropriate data once the TEAMS Exchanger or Vessel option under Input | Problem Definition | Description is selected.
Then the program will load Heat exchanger material data and search option once Heat exchanger option is selected and it will do the same if Pressure Vessel option is selected.
Keywords: Material Input, Material Search, Main Materials.
References: None |
Problem Statement: On the Utilities pull-down menu, there is an entry for CHANGE and Forecast Delay Cutoff. Where does Aspen Retail store the value for Forecast Delay Cutoff? | Solution: It is stored in the TPS_STATIONS table in the SOCUTOFF column. The number stored in the SOCUTOFF column is the minutes past midnight. For example, if the desired cutoff time was 10:01 AM, the number stored in the SOCUTOFF column would be 601.
Keywords:
References: None |
Problem Statement: What problems are fixed in Release 7.04.00.16 and prior releases? | Solution: This release contains the following major fixes:
With weight opt =2, loads were being scheduled before the retain, and after the run-out.
RVP\OXYÂShipmentsÂthatÂwereÂdeletedÂandÂnot&A circ;putÂinÂtheÂdeliveredÂshipmentsÂlogÂwere&Aci rc;notÂbeingÂwrittenÂtoÂtheÂcanceledÂorders&Acir c;table
Fix for the Sales Import Service and Man Ord Service not giving an error when a record remains unprocessed with n_info_flg=T because the station is in process.
Fix for the credit status when this field is not included inside the CPT update. If a customer is on credit hold and a credit person releases a load for them (i.e prepay) and then the CPT runs updating a field but the credit field is not populated (i.e. null value) the system will then place this load back on credit hold.
The ManOrder service correctly kept the n_info_flg as 'T' and wrote the inprocess error message when a station was in process, but when the station was no longer in process and the record was processed successfully, the in process errcode was not cleared out.
Fix for a record entered into TCIF_MANUALORDERS with an invalid terminal number. The record is processed correctly (n_info_flg changes to 'F' and error 600 'Invalid terminal' is given), but station remains in process
Inventory Date is not being updated to the correct date when new information is input for a customer
Fix for loads no longer being re-forecasted if you look at tank info
To find out what problems have been fixed in the previous service packs, go to http://support.aspentech.com/webteamcgi/SolutionDisplay_view.cgi?key=108026
Note that the fixes are accumulative. Any fixes delievered in prior versions are contained in the latest version. If you are already using Aspen Retail 7.04.00.xx, you can readily upgrade to this Service Pack. Please email to [email protected] if you are interested in this service pack.
Keywords:
References: None |
Problem Statement: Is there a way to prevent users from overiding the In-Process warning messages? The messages will pop up when a user tries to modify a customer's orders while someone else is optimizing that terminal / customer. | Solution: Yes, in the PSOFTG.ini file's WINOPT section add (or modify to) the following:
[winopt]
showorbutt=0
This feature is strategic as overiding this warning can cause duplicate orders that lead to runouts.
Note: When using the automated SIIMPORT executable (Service), the in-process flags are respected for all station that are in service when the new sales and inventory data arrive to the Aspen Retail database. Once the optimizer is closed, these orders are processed. If the user has the ability to hit the override button (showOrBut =1) then duplicate orders can be generated.
Keywords:
References: None |
Problem Statement: What is the purpose of the What-If Delivery Scenario? | Solution: The What-If Delivery functionality allows the users to make modifications to existing orders to note the effect before saving the changes. The What-If Delivery enhancement works only with forecasted customers. It allows the user to see what happens if the parameters of an existing order are changed. Instantly, the user can see how the delivery schedule will be affected.
The user can access What-If Delivery from either the tank info button within an order or from the tank icon in the main menu of the Replenishment Planner. While the user can access What-If Delivery from other applications in Aspen Retail, changes can only be saved while in the Replenishment Planner.
Keywords: What-If
Replenishment Planner
References: None |
Problem Statement: Do all customers in a cluster need to be in the same terminal? | Solution: In order for the Split Load functionality to work, all customers in the same cluster must be sourced from the same terminal as their home terminal. When adding customers to a cluster, you should be warned if they do not belong to the same terminal.
Keywords: Clusters
References: None |
Problem Statement: How is the Accept button used in the Data Quality Manager? | Solution: In Data Quality Manager, this button is used to accept sales and inventory information for forecasting after the exception has been addressed. When an exception pops up, the Accept Button is grayed out and cannot be used until sales, inventory and delivery information reconciles. When sales, inventory and delivery information reconciles, the accept button will light up.
Key words
accept button
Keywords: None
References: None |
Problem Statement: Why do loads appear Green in the Replenishment Planner? | Solution: If a Delivery Confirmation has been sent in from another System into Aspen Fleet Optimizer, the load will appear Green in the Replenishment Planner.
Keywords: Blue Load, Replenishment Planner
References: None |
Problem Statement: Why would I want to import Load Confirmations into Aspen Fleet 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.
Keywords: Load Confirmation, Optimizer
References: None |
Problem Statement: What does In-process = 2 in the TPS_STATLOCK table mean? | Solution: In the TPS_STATLOCK table, the field INPROCESS is generally set equal to 1 or 0 depending on actions occurring within the Application. If a Customer is open in Customer Setup, or the Optimizer is open to the group this Customer belongs in, the INPROCESS flag will be set to 1.
In some circumstances it has been found that a Customer could be set to 2 in this field. This is not a valid entry and generally means something has caused this Customer to be locked and updated after it was locked. If this case is seen please report it to AspenTech Support.
Keywords: INPROCESS, STATLOCK
References: None |
Problem Statement: How do I specify minimum or maximum delivery quantities that can be delivered to a customer? | Solution: On the Customer Set-up Screen click the tool bar button the resembles a stop sign. This will being up the Customer Restriction screen. On this screen in the top right are two fields for entering minimum and maximum delivery volumes. Once entered here the system will respect these constraints when creating deliveries for this account. Please bear in mind that it is not possible to specify a minimum without specifying a maximum. If your business case does not present maximum restriction but does contain minimum restrictions, simply enter a value in the maximum field larger than your largest transport and you will have accomplished setting a minimum restriction without limiting the maximum size for a delivery.
Keywords: Minimum Delivery, Maximum Delivery
References: None |
Problem Statement: How do I see the latest Sales and Inventory entered and how it was entered? | Solution: The Sales and Inventory Log available under the Utilities menu allows you to see the latest Sales and Inventory Data and how it was entered, either via IVR, POS, Manual Information Collection, or directly into the Data Quality Manager.
Keywords: Sales and Inventory Log
References: None |
Problem Statement: How do I submit incidents into Scopus? | Solution: Log onto http://support.aspentech.com
Along the left pane, there is an option to Register Now'
Enter your email address to begin the registration process
Complete the information regarding business address, products of interest, etc
Press 'I Accept' to agree to the terms of the AspenTech Technical Support Center Agreement
Registration submission will then appear and your request will be processed within 1 business day.
Once you receive confirmation that your username and password have been registered, click on the link below to read instructions on how to enter incidents into Scopus.
http://support.aspentech.com/webteamcgi/SolutionDisplay_view.cgi?key=113454
Keywords:
References: None |
Problem Statement: How does Aspen Fleet Optimizer determine the Must Go shift? | Solution: MustGoForc =1(Default)
Determines the definition of a must-go shift
Acceptable Values:
0 = the must-go shift is the shift in which a runout occurs
1 = the must-go shift is the system recommended forecasted shift for which the order generator created the order (default). The system recommended shift is the last full shift (12 hours) of delivery prior to the buffered run-out point
Use: Setting MustGoForc to 0 puts the system in the more difficult situation to resolve delivery. Though it allows bigger deliveries and decreases both transportation and carrying cost. With MustGoForc=0 much more problem orders may appear in theSolution, which will require manual handling. MustGoForc=1 will rely more on an automaticSolution which may not be as optimal
Example:
Assume the following:
a runout buffer of 9 hours
two scheduling shifts per day
MustGoForc=0
In this example, if a tank is scheduled to runout on January 1, 2004 at 8:00 AM, the must go shift is the first shift on January 1, 2004 (12:00 AM ? 11:59 PM).
MustGoForc=1
In this example, if a tank is scheduled to runout on January 1, 2004 at 8:00 AM, the must go shift is the first shift on December 31, 2003 (12:00 AM ? 11:59 PM).
Key words
Must go shift
Forecasting
Keywords: None
References: None |
Problem Statement: Are the number of compartments and number of products evaluated together? Yes, this | Solution: shows how the calculation is doneSolution
NumCompart =12 (default)
The NumCompart and NumProducts settings are evaluated together to determine if the recursive or iterative method
is used to assign product(s) to compartments on a transport
Acceptable Values: from 1 to 12 (default)
Use: The system uses only the iterative method if:
The number of compartments on the truck is greater than or equal to the NumCompart value, and
The number of products in the order is greater than or equal to the NumProducts
Once the iterative method for assigning products to compartments is chosen, the system takes one of two possible
approaches:
If the order requests more products than the number of compartments on the truck, the approach of the RSO
is to deliver more product type rather than the greatest volume of product
Consequently, the same product should not be assigned to more than one compartment, unless the load is
being split
If the truck has more compartments than the number of products in the order, the RSO loads the truck with the
greatest volume of product. Consequently, the same product can be assigned to multiple compartments
Example:
The recursive method would be used in the following example:
NumCompart=12
NumProducts=5
Actual number of compartments on the truck=6
Actual number of products in the order=3
The iterative method would be used in the following example:
NumCompart=12
NumProducts=5
Actual number of compartments on the truck=12
Actual number of products in the order=6
Key words
Number of compartments
Number of products
Keywords: None
References: None |
Problem Statement: Can Databuild Customer's import Manual Orders? | Solution: Customers in databuild status cannot receive Manual Orders. Databuild Status is for bringing in Sales figures to build up trends prior to becoming an Active customer.
Keywords: Databuild
References: None |
Problem Statement: When should I use the rest utility? | Solution: Reset Utility enables the user to reset the customer in process flag. The in process flag helps avoid concurrency problems. The reset utility can be used to reset the in process flag for a group, zone, terminal, or customer. The rest utility is very powerful and incorrect usage of this can cause many unexpected results inside Fleet Optimizer. The rest utility should only be used when an account is locked by another process and that process has frozen or crashed. The reset utility should never be used as a way to gain control of an account if another user or process has control of the account and has not abnormally ended.
Keywords: None
References: None |
Problem Statement: What does the upper-case P designate on an order inside the Optimizer? | Solution: This P indicated the order has been Pre-Assigned to this truck by the dispatcher. This process tells the Optimizer not to Optimize this load to any other truck because the dispatcher has a specific reason to want this delivery to go onto this specific truck.
Keywords: Pre-Assigned
References: None |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.