Trucking Optimization Report
From UG
(Difference between revisions)
(→Use Cases) |
|||
| Line 107: | Line 107: | ||
* Schedule option (need for release) | * Schedule option (need for release) | ||
| - | == | + | == Related Business Process == |
| + | |||
| + | Strategy/constraints: | ||
| + | |||
| + | * you can't pick up freight that is not available | ||
| + | * you must start moving freight that is due soon | ||
| + | * you want to optimize cost of move: | ||
| + | ** minimize the number of trucks | ||
| + | *** truck must be as full as possible | ||
| + | *** send not too frequently | ||
| + | *** send larger trucks | ||
| + | |||
| + | Operator must make decisions about: | ||
| + | |||
| + | * a) what to move | ||
| + | * b) when to move | ||
| + | * c) what truck size to use (or combination) | ||
| + | * d) what trucking company to use | ||
| + | |||
| + | Decisions about a,b,c oper will make based on this report. | ||
| + | |||
| + | New orders come in at any moment of time changing the state of total freight available to move. | ||
| + | |||
| + | Operator will make separate decisions for every delivery location. | ||
| + | |||
| + | For every delivery location operator has to know what is due soon to be delivered (and available for pick up). | ||
| + | |||
| + | Assume | ||
| + | |||
| + | To do that operator will: | ||
| + | * select one delivery location | ||
| + | * | ||
=== All cargo to one Delivery Location for selected Cargo Due time frame === | === All cargo to one Delivery Location for selected Cargo Due time frame === | ||
Revision as of 15:45, 27 April 2010
Contents |
Intro
Testing on Demo server today revealed that we are missing critical Report that needs to be demonstrated to Client on Monday.
This report (#Trucking Optimization Report) is defined below along with required additional fields.
Please postpone all other work to produce this missing Report/components ASAP. See more below.
Due dates
- Ideally: April 23 NY mid day on Demo server
- Worst case: April 26 NY morning on Demo server
Demo Server Data
In order to have meaningful functionality test in NY on Demo server we need more or less latest data from staging (especially Addressbook).
Create additional fields
Cargo available
- widget: datebox
- location: Gen Tab
- default: empty
- meaning: on what date cargo is available for pick up (from Origin Door)
- MOT: Truck
Cargo due
- widget: datebox
- location: Gen Tab
- default: empty
- meaning: by what date cargo should be delivered (to Destination Door)
- MOT: Truck
Trucking Optimization Report
Hard coded conditions
None. (All CTs should be captured)
Filters
For April 23 NY mid day:
- Client Company // single select // match against CT#E0_Client OR CT#E1_Client OR CT#E2_Client OR CT#E3_Client
- CT#MOT // single select // only choice of Truck Domestic for May 1; add 2 more trucking modes after
- #Cargo Due // From datebox To datebox
- #Cargo Available // From datebox To datebox
- CT#Pick Up (Company - city - note) // multi select
- populate list with all unique Address_bo#Company_City_Remark fields existing currently in DB where Address#Category equals to Address#ExportPickUpLocation
- CT#Pick Up (city) // multi select
- populate list with all unique Address#City fields existing currently in DB where Address#Category equals to Address#ExportPickUpLocation
- CT#Pick Up (state) // multi select
- populate list with all unique Address#State fields existing currently in DB where Address#Category equals to Address#ExportPickUpLocation
Developer's Note: ----------------- To simplify you can instead show a list of all US states
- CT#Delivery To (Company - city - note) // multi select
- populate list with all unique Address_bo#Company_City_Remark fields existing currently in DB where Address#Category equals to Address#ExportDeliveryLocation
- CT#Delivery To (city) // multi select
- populate list with all unique Address#City fields existing currently in DB where Address#Category equals to Address#ExportDeliveryLocation
- CT#Delivery To (state) // multi select
- populate list with all unique Address#State fields existing currently in DB where Address#Category equals to Address#ExportDeliveryLocation
Developer's Note: ----------------- To simplify you can instead show a list of all US states
For May 1 release:
- Remaining Virtual Group Filters (not confirmed!)
Output
- media: xls only
- Sort by: Cargo due, earliest on the top
- Tabs: each tab per State (from Pick Up Location)
- Fields (left to right)
- label on xls // mapping explained
- CT# //
- Pick Up Location // Pick Up Location Company
- P City // Pick Up Location City
- P State // Pick Up Location State
- Delivery Location // Delivery Location Company
- D City // Delivery Location City
- D State // Delivery Location State
- HU // Grand ttl for CT
- Weight, lb // Grand ttl for CT
- CBM // Grand ttl for CT
- Cargo Available // CT field
- Cargo Due // CT field
- Totals: provided for numerical columns
Schedule vs Generate
- Generate option (need by April 23 NY mid day on demo)
- Schedule option (need for release)
Related Business Process
Strategy/constraints:
- you can't pick up freight that is not available
- you must start moving freight that is due soon
- you want to optimize cost of move:
- minimize the number of trucks
- truck must be as full as possible
- send not too frequently
- send larger trucks
- minimize the number of trucks
Operator must make decisions about:
- a) what to move
- b) when to move
- c) what truck size to use (or combination)
- d) what trucking company to use
Decisions about a,b,c oper will make based on this report.
New orders come in at any moment of time changing the state of total freight available to move.
Operator will make separate decisions for every delivery location.
For every delivery location operator has to know what is due soon to be delivered (and available for pick up).
Assume
To do that operator will:
- select one delivery location
All cargo to one Delivery Location for selected Cargo Due time frame
See #Figure 1
Figures
Figure 1
