From UG

Revision as of 14:26, 8 December 2010 (edit) Denise (Talk | contribs) (→Business Requirements) ← Older edit		Revision as of 14:30, 8 December 2010 (edit) (undo) Denise (Talk | contribs) (→PP conditions) Newer edit →
Line 53:		Line 53:
	=== PP conditions ===		=== PP conditions ===
		+
		+	Operator will look at ''ALL'' shipments coming from Shipper X that are going Destination Y are small - IE 1, 2, 8, 10 pallets and weights under
	=== Regular conditions ===		=== Regular conditions ===

---

Revision as of 14:30, 8 December 2010

Contents 1 Info 1.1 Business Requirements 1.1.1 Pool Point Criteria 1.1.2 Exceptions 1.1.3 PP conditions 1.1.4 Regular conditions 1.2 Design Ideas 1.3 SA Notes 1.3.1 Summary 1.3.2 Implementation 1.3.2.1 Admin 1.3.2.2 Shipments 1.3.2.3 TDS dashboard 1.4 LA Notes 1.4.1 3 cases 1.4.1.1 Regular algorithm 1.4.1.2 PP algorithm 1.4.2 Pool time 1.4.3 Exception algorithm 1.4.4 pick ups 1.4.5 Figure: PP 1.5 RFP

Info

Mantis: 2597

Business Requirements

This about adding the concept and functionality into CT2 for pool point shipments according to the Arden domestic business process.

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 picks up all of them to deliver. Since the Arden team creates multiple pool point loads throughout the day from different origins, the TM will always create 2 loads - one from the pickup location to the pool point and the other from the pool point to the delivery location. But in reality the delivery will only be 1 or maybe 2 trailer loads, as the pool point has consolidated them and this is causing inaccurate trailer counts for reporting purposes.

Pool Point Criteria

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).

There are 2 levels on how to decipherer if a shipment should go through a pool point.

1st are the origin & destinations:

• 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%)

2nd are the total number of pallets & total gross weight:

• Total gross weight is less than 44000 LB

• Total pallet count (non-stack) is less than 28

• Total pallet count (stackable) is less than 60

It is possible that CT records can meet the above criteria and the business side would not want to send it through the pool point for a few different reasons. One reason could be that the shipment is very urgent. Another reason could be that it's not cost effective, as the size of the shipment (number of pallets and gross weight) are high, but less than the criteria - (IE 35,000) and this is what you'd call an exception.

Exceptions

What defines an exception is again the pairing of the same origins and destinations, but the total number of pallets and total gross weight will be lower.

• Example:
  • Total gross weight is more than 25000 LB but is less than 44000 LB
  • Total pallet count (non-stack) is more than 20 but less than 28
  • Total pallet count (stackable) is more than 35 but less than 60

In this case, the system should:

• Not send to the TM
• Give some sort of an alert on the TDS
• Give option to users to send through pool point or not
  • Upon users confirmation, send to TM accordingly

PP conditions

Operator will look at ALL shipments coming from Shipper X that are going Destination Y are small - IE 1, 2, 8, 10 pallets and weights under

Regular conditions

Design Ideas

To have the system check every approved CT record to see if meets the #Pool Point Criteria before sending them to the TM.

• If record meets the criteria: have 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.
  • IE CT 121245 has 8 pallets at 1500 lbs, coming from Edison, NJ - going to Roanoke, VA. The system creates 1 CT # 121245a at 8 pallets at 1500 lbs, coming from Edison, NJ - going to the Jewels Transportation in Newark, NJ (they are the pool point). Then the system creates the second CT # 121245b at 8 pallets at 1500 lbs, coming from the pool point - Jewels Transportation in Newark, NJ, going to the deliver to location in Roanoke, VA. Then send these 2 records 121245a & 121245b to the TM, for the Jag ops to work with. Upon carriers tender acceptance in the TM & their updating of the pickup/delivery dates, the system would update the original CT # 121245 only, as received on the status update from the TM, because both a & b records are in the background.

SA Notes

Summary

1) Add admin panel Pool Point with Pool Point adresses and states criteria, the total number of pallets & total gross weight criteria.

• (do we need to add Exceptions criteria to admin panel or its must be hardcoded ?)
  • Answer 1: Yes, pls add to admin panel, do not hard code so we may change if necessary according to business rules

2) what should we to do if CT was edited (total GW and other) ?

• Answer 2: Recheck the changes to see if it makes any difference according to the pool point criteria.
  • If yes, do not send the changes to TMS and give some sort of message to the internal user, so they can update according to the business process.
  • If no, send the changes to TMS, the same way we handle it now.
    • To advise, it would be only the internal users who would make changes to this information.

3) Can TMS work with CT# that contains characters? by example, '111111a'.

• Answer 3: Yes they can work with alphanumeric shipment #'s

Implementation

What we need to do in:

Admin

Add admin tab with tables:

1) Pool Points:

• Name
• Adress

2) States criteria:

• original state,
• destination state,
• Pool Point.

3) Parameters (min(for request operator) , max (for reject Pool Point)):

• Total gross weight,
• Total pallet count (non-stack),
• Total pallet count (stackable)

Shipments

• New CT fields (GenTab ?):
  • Pool Point
  • Actual Pool Point Delivery Date
  • Actual Pool Point PickUp Date

TDS dashboard

• add collumn "Pool Point" with number of approved CTs whose need operator's attention to create Pool Point.

LA Notes

PP - Pool Point.

3 cases

Looks like we have 3 cases:

• CTs that must be routed automatically through PP (#PP algorithm), see #PP conditions
• CTs that must be routed as "regular CT" (#Regular algorithm), see #Regular conditions
• human intervention required (#Exception algorithm), see #Exception conditions

Regular algorithm

• forward CT as it gets approved directly to TMS

PP algorithm

• for one CTX create 2 "child records": one CTXa from Pick Up to PP, another CTXb from PP to Delivery
• forward CTXa to TMS for immediate processing (need to order pick up ASAP)
• forward CTXb to TMS for later processing (operator will order pick up from PP to delivery at "Pool time" in TMS)

Pool time

In general it would be some kind of schedule regulating when to move CTs accumulated at PP and route various destinations.

In case of "current Arden project Jewels pool point" it happens once a day at 4pm.

This should not be captured in the system.

Exception algorithm

Post every such CT on special dashboard

Several times a day before Pool Time operators will examine CTs posted to dashboard and direct system to use #Regular algorithm or #PP algorithm

pick ups

As system d

Figure: PP

RFP

Proposal required before coding.