Trucking Optimization

From UG

(Difference between revisions)
Jump to: navigation, search
(→Trucking Optimization Report Version 2)
(→Phase B)
 
(18 intermediate revisions not shown)
Line 18: Line 18:
Each trucking company has its own tariff so we are dealing with {tct1, ..., tctK} - set of tariffs.
Each trucking company has its own tariff so we are dealing with {tct1, ..., tctK} - set of tariffs.
 +
 +
...
== Suggested solutions ==
== Suggested solutions ==
Line 45: Line 47:
==== Trucking Optimization Report Version 2 ====
==== Trucking Optimization Report Version 2 ====
-
In this phase it was suggested to add version 2 of [[Trucking_Optimization_Report]].
+
''Wiki home:'' [[Trucking_Optimization_Report#Version_2_that_is_based_on_Zones]]
 +
 
 +
In this phase it was suggested to add version 2 of [[Trucking_Optimization_Report]]. It is based on the concept of [[#Zones]].
Main difference is to improve precision in defining "pick up zone" for milk run by defining zone not as a state but as an any number of pick up locations that are "not too far from each other" on the map.
Main difference is to improve precision in defining "pick up zone" for milk run by defining zone not as a state but as an any number of pick up locations that are "not too far from each other" on the map.
-
See example here [[April_21_NATP_Changes#Figure_2.a]] and [[April_21_NATP_Changes#Figure_2.b]]
+
See [[Trucking_Optimization_Report#Version_2_that_is_based_on_Zones]]
 +
 
 +
===== Zones =====
 +
''Wiki home:'' [[Zoning]]
See attempt at designing Zone object here: [[Zoning]].
See attempt at designing Zone object here: [[Zoning]].
==== Alerts ====
==== Alerts ====
 +
''Wiki home:'' [[Alerts]]
-
This would complement (or replace) user's task to run [[Trucking_Optimization_Report]] periodically.
+
This would complement (or replace) user's task to run [[Trucking_Optimization_Report]] periodically or receive/review from Scheduler.
-
As defined by Tira - see below.
+
The idea is that every time CT is added - the system would "generate trucking optimization reports on a background". For every delivery location it would calculate total weight, pallets accumulated and available in each zone. If for any pick up zone "Ready to move conditions" is satisfied then system would alert operator by e-mail.
-
''It is an alert notification that system tells users that shipments in a particular zone location are ready to pick up. System will send an alert via email as well as show on the dashboard when there is enough shipments to fit on at least one truck. System will consider delivery location zone and pick up location zone; it is a pairing of Delivery Location zone and Pick up Location zone.
+
Operator then would and prepare goods to move: start calling Carriers to find out about rates, truck availability, etc.
-
* Each time shipment is created with the weight, cbm, and/or pallets information, these info will be added to a table and calculated.
+
===== Ready to move conditions =====
-
** Each table is a combination of delivery location and pick up location zone
+
There could be different options here but main idea is to define when we have enough goods to fill FULLY the truck or trucks.
-
* The calculation result meets the minimum space to fit in one truck
+
-
* System should be able to calculate and provide information about:
+
-
** what size of truck to send
+
-
** how many trucks to send
+
-
** require Haz driver or not
+
-
NOTE: It should be automatically alert real time when there is enough shipments (pallets) that need to be pick up.
+
Simplest example: total number of pallets is equal or more that the max number pallets that fit into smallest truck.
-
''
+
 
 +
===== Ready to move conditions Admin =====
 +
 
 +
We need Admin for this conditions
==== Dashboard ====
==== Dashboard ====
 +
''Wiki home:'' [[Dashboard]]
 +
 +
Dashboard is simply a page where we summarize important current info, post alerts, etc.
 +
 +
This should be located on homepage: CT2 > Home (below top menu bar) - now this page is blank.
 +
 +
For this phase all we need is to post all alerts - see [[#Alerts]]. In this case instead (or in addition) to alerts being e-mailed operator would periodically look at CT2 home page.
 +
 +
Only operators that deal with Truck domestic should see it. Also operator should see only alerts for the Client Company he is handling.
 +
 +
=== Phase C ===
 +
 +
==== Trips ====
-
Some ideas from Tira - see below.
+
We probably need this new business object in the system to support new features. It would describe one trucking trip from door to door with any number of pick ups and drop offs on the way.
-
''
+
To support this we need to add new fields to CT to be able to record any number of stops (with date/time, stop address, what commodities were picked/dropped, etc)
-
* Create a dashboard that indicates a pair of delivery and pick-up zones, showing weight, cbm, pallets with a traffic light
+
-
* Traffic light indicates whether shipments are ready to pick up
+
-
* Dashboard will indicate the zone that needs to be pick up and delivery regarding due date
+
-
* Zones should be sorted by the earliest due date to latest due date
+
-
* Dashboard should be able to view information
+
-
:* Table of zones, pallets information with traffic light, how many trucks will it need and what size of the truck and Haz driver is required or not
+
-
:* bar and or pie charts
+
-
:* custom maps indicates locations, zones, number of pallets that need to be pick up and number of pallets that need to be deliver at particular location. This can be indicated by color and symbol to differentiate the locations and zone, etc
+
-
''
+
==== Visualization ====
==== Visualization ====
Line 92: Line 102:
* Maybe Charts - TBD
* Maybe Charts - TBD
-
== Preliminary Design ==
+
==== Etc ====
 +
Add "delivery zones" to support milk run at delivery.
-
=== Preliminary Design Phase B ===
+
Support all options from here: [[Business_Process_and_Use_Cases_for_NATP#Transportation_options]]
-
....
+
-
=== Preliminary Design Phase C ===
+
Use "rates module" (currently in development) to calculate rates for each carrier automatically, suggest cheapest to operator and display all if required.
-
....
+
 +
=== Phase D ===
 +
More automation.
-
== Old links and material ==
+
New strategies.
-
=== Trucking Optimization Report Version 1 ===
+
Extensive use of math algorithms.
-
see [[Trucking_Optimization_Report]]
+
Find and apply best solutions found in industry and academia.
-
=== Zoning ===
+
== Preliminary Design ==
-
* Client Zones based on historical data
+
=== Preliminary Design Phase A ===
-
* Client Zones based on incoming data
+
This phase is in production.
-
* Client Pick Up zones
+
 
-
* Client Delivery To zones
+
=== Preliminary Design Phase B ===
-
* Trucker Pick Up zones
+
....
-
* Trucker Delivery To zones
+
 
-
* required Business Objects (BO)
+
=== Preliminary Design Phase C ===
-
* required [[CRUD]] for BO and required logic
+
....
-
* Trucking Optimization Report Version 2
+

Current revision as of 23:37, 12 May 2010


Contents

[edit] Core Business Requirement

It is required to optimize total cost of domestic trucking business within one country (focus on USA now) for one company's supply chain for given time frame (let's say one year).

It is assumed that there is a constant flow of orders: O1, O2, ... , Oj, ...

Each order is about moving specific amount commodities (cargo) characterized by set of parameters: {Weight, Pieces (Num of palets + loose), Volume, Available Date, Due Date}

Commodities are to be moved together from Pick Up location to Delivery location.

For given Client Company there is a limited set of Up locations (origin doors) {od1, od2, ... , odN}

For given Client Company there is a limited set of Delivery locations (destination doors) {dd1, dd2, ... , ddM }

There are limited number of carriers (trucking companies) {tc1, ..., tcK} that can service country.

Each trucking company has its own tariff so we are dealing with {tct1, ..., tctK} - set of tariffs.

...

[edit] Suggested solutions

Number of things can be done to reduce total cost. For example:

[edit] Phased approach

We follow phased approach which means that in every Sprint we add new optimization methods or improve existing ones.

[edit] Phase A

This phase was released to production on May 1.

In this first phase we added version 1 of Trucking_Optimization_Report. It is designed for Business_Process_and_Use_Cases_for_NATP#One_destination_and_milk_run_at_origin method.

Read Trucking_Optimization_Report article for more details.

[edit] Phase B

Number of features were suggested and partially designed - see below.

[edit] Trucking Optimization Report Version 2

Wiki home: Trucking_Optimization_Report#Version_2_that_is_based_on_Zones

In this phase it was suggested to add version 2 of Trucking_Optimization_Report. It is based on the concept of #Zones.

Main difference is to improve precision in defining "pick up zone" for milk run by defining zone not as a state but as an any number of pick up locations that are "not too far from each other" on the map.

See Trucking_Optimization_Report#Version_2_that_is_based_on_Zones

[edit] Zones

Wiki home: Zoning

See attempt at designing Zone object here: Zoning.

[edit] Alerts

Wiki home: Alerts

This would complement (or replace) user's task to run Trucking_Optimization_Report periodically or receive/review from Scheduler.

The idea is that every time CT is added - the system would "generate trucking optimization reports on a background". For every delivery location it would calculate total weight, pallets accumulated and available in each zone. If for any pick up zone "Ready to move conditions" is satisfied then system would alert operator by e-mail.

Operator then would and prepare goods to move: start calling Carriers to find out about rates, truck availability, etc.

[edit] Ready to move conditions

There could be different options here but main idea is to define when we have enough goods to fill FULLY the truck or trucks.

Simplest example: total number of pallets is equal or more that the max number pallets that fit into smallest truck.

[edit] Ready to move conditions Admin

We need Admin for this conditions

[edit] Dashboard

Wiki home: Dashboard

Dashboard is simply a page where we summarize important current info, post alerts, etc.

This should be located on homepage: CT2 > Home (below top menu bar) - now this page is blank.

For this phase all we need is to post all alerts - see #Alerts. In this case instead (or in addition) to alerts being e-mailed operator would periodically look at CT2 home page.

Only operators that deal with Truck domestic should see it. Also operator should see only alerts for the Client Company he is handling.

[edit] Phase C

[edit] Trips

We probably need this new business object in the system to support new features. It would describe one trucking trip from door to door with any number of pick ups and drop offs on the way.

To support this we need to add new fields to CT to be able to record any number of stops (with date/time, stop address, what commodities were picked/dropped, etc)

[edit] Visualization

  • Google Maps - display moves, location on the map.
  • Maybe Charts - TBD

[edit] Etc

Add "delivery zones" to support milk run at delivery.

Support all options from here: Business_Process_and_Use_Cases_for_NATP#Transportation_options

Use "rates module" (currently in development) to calculate rates for each carrier automatically, suggest cheapest to operator and display all if required.

[edit] Phase D

More automation.

New strategies.

Extensive use of math algorithms.

Find and apply best solutions found in industry and academia.

[edit] Preliminary Design

[edit] Preliminary Design Phase A

This phase is in production.

[edit] Preliminary Design Phase B

....

[edit] Preliminary Design Phase C

....

Retrieved from "https://wiki.jaguarfreight.com/Trucking_Optimization"
Personal tools