Pool Point
From UG
(→Pool Point Criteria) |
(→Intro) |
||
| Line 1: | Line 1: | ||
[[Category: EDI to TMS]] | [[Category: EDI to TMS]] | ||
| - | = | + | = Info = |
| - | This article is about adding the concept and functionality into CT2 for pool point shipments according to the Arden domestic business process. | + | This article is about adding the concept and functionality into CT2 for pool point shipments according to the Arden domestic business process. |
| - | == | + | == Business Requirements == |
| - | Currently | + | '''Core Business Need:''' Currently the Arden domestic team is using the TMS to create and tender loads from the same origin company/city going to VA and/or ME by using a pool point. One trucker who collects all of the pickups through out the day and another trucker who pickups to deliver. As the Arden team creates multiple pool point loads throughout the day from different origins, the TM creates 2 loads - one from the pickup location to the pool point and the other from the pool point to the delivery location. But the TMS cannot accommodate their business process and this is causing inaccurate trailer counts for the delivery loads. |
| - | + | Currently there is 1 pool point - Jewels Transportation, who are in Newark, NJ. They collect all of the Tri-State area (NY, NJ, CT) pickups and once the shipments are back in their warehouse, they load empty trailers for the delivery carriers (Lawrence Transportation &/or Albert Farms). | |
The system to look at every approved CT record upon approval to see if meets the pool point criteria before sending the records to the TM. If record meets the criteria, the system would then create 2 copies of that 1 record in the background - 1 from the pickup location to the pool point and 1 from the pool point to the deliver to location. | The system to look at every approved CT record upon approval to see if meets the pool point criteria before sending the records to the TM. If record meets the criteria, the system would then create 2 copies of that 1 record in the background - 1 from the pickup location to the pool point and 1 from the pool point to the deliver to location. | ||
Revision as of 21:04, 1 December 2010
Contents |
Info
This article is about adding the concept and functionality into CT2 for pool point shipments according to the Arden domestic business process.
Business Requirements
Core Business Need: Currently the Arden domestic team is using the TMS to create and tender loads from the same origin company/city going to VA and/or ME by using a pool point. One trucker who collects all of the pickups through out the day and another trucker who pickups to deliver. As the Arden team creates multiple pool point loads throughout the day from different origins, the TM creates 2 loads - one from the pickup location to the pool point and the other from the pool point to the delivery location. But the TMS cannot accommodate their business process and this is causing inaccurate trailer counts for the delivery loads.
Currently there is 1 pool point - Jewels Transportation, who are in Newark, NJ. They collect all of the Tri-State area (NY, NJ, CT) pickups and once the shipments are back in their warehouse, they load empty trailers for the delivery carriers (Lawrence Transportation &/or Albert Farms).
The system to look at every approved CT record upon approval to see if meets the pool point criteria before sending the records to the TM. If record meets the criteria, the system would then create 2 copies of that 1 record in the background - 1 from the pickup location to the pool point and 1 from the pool point to the deliver to location.
Pool Point Criteria
There are 2 levels on how to decipherer if a shipment should go through a pool point. 1st is the origin & destinations and 2nd is the number of pallets & total gross weight.
- NY, NJ, CT, going to destination states VA, ME
- TN, GA, NC, SC & VA, going to destination city/state NY, NY (Manhattan, aka NYC)
- ME, going to VA (this is a rarer business case, about 20%)
