From UG

Revision as of 17:42, 29 June 2011

Intro

This article is the basic use of CT2 and the TMS for the Arden domestic business process.

Summary

There are two JFS operators who handle the majority of routings for the EA domestic trucking shipments; Stacy & Erin and between the two of them there are 11 trucking companies involved. There is some over lap of trucking companies between the two of them. As well, they both have assistants who also work on the TM. Shannon assists Stacy & Etan assists Erin.

CT2 to TMS Process

Upon portal record being approved

All APPROVED portal records are immediately pushed into the TM at the time of approval. The record(s) can be found on the TM shipment page, as well as on the CT2 TDS dashboard with a TMS Status as Import 1, along with the CT record(s). See #Figure_1

• If record displays TMS Status: yet, suggest refreshing the browser in case of a time delay. If the status does not change, suggest double checking the TM for this shipment # and if not there, then manually upload the record(s) into the TM by way of the virtual group filters.

• All hold with a date CT record(s) will be pushed into the TM shipment page the same day they are listed on the CT2 TDS dashboard, which currently is 48 hours prior to the approved to ship date.
  • Note, this will change to 72 hours at a later date.

Begin working in the TM

• Once in the TM shipment page, each shipment number, (which is the CT #) will have a status set: new, rated or exception
  • If the status is exception, you will need to correct before you can proceed with that record. Suggest to update the record(s) in CyberTrax and upon save, any update(s) will be made in the TM.

• Upon the browser refreshing, the record(s) status will change to rated and a carrier will be automatically assigned.

• The system will check all of the carrier tariffs and assign the cheapest carrier, irrespective of the business process. If no carrier is selected, it is very possible that there aren’t any carrier tariffs in the TM, covering that lane.

• Once the shipment(s) status is rated, a load can be created.

See #Figure_2

Building Loads

There are two types of loads that can be created in the TM; the first type is direct loads & the second type is pool point loads.

Direct loads

• When you right click to create a load, the TM creates 1 load from the pickup location to the delivery location. The TM will NOT take into consideration the cargo available date(s) as per previous business rule requirements and once the shipment record(s) are selected, it will move from the shipment page, to the load page. The record(s) will be inside of the load # the TM sets automatically and the load(s) will also have a status: new or rated.

• Upon the browser refreshing, the load(s) status will change to rated and a carrier will be selected. If the carrier the TM chose is not the carrier to use for the move, suggest right clicking and selecting a different carrier.

See #Figure_3

• The system will check all of the carrier’s tariffs and assign the carrier, as well as take into consideration the carrier routing rules that were already setup. If no carrier is listed, it is very possible that there aren’t any carrier’s tariffs covering that lane or if only 1 carrier is listing, again it is very possible that there aren’t any carrier tariffs in the TM, covering that lane.

• Should a specific carrier need to be assigned according to the business process and does not come up, suggest right clicking and select add a manual rate. Add a rate of $ 1.00, assign the carrier accordingly and follow up with Arden as usual for those rates.

• Once selected carrier is set, tender the load and it will move from the summary list to either the tendered loads list or the accepted tendered loads list.

• Most carriers are set to auto tender accept, expect for Express Air. They are the only carrier setup in the TM, not to auto accept all tender requests and they must be tendered manually by right clicking and selecting, tender.

Pool Point Loads

The current pool point concept that Descartes offer was not useful according to the EA domestic business and it was advised to Descartes we will not use this feature until they change their use of the pool point concept. You can see below #History Therefore the following business process has been created for ALL "pool point" shipments:

Jewels

• I had to update the Jewels tariff in the TM to include all moves ex Tri-State to zip code 24012 at the same rates.
• After that was done, CT records that would usually be “consolidate with pooling” inside the TM, will now need to be handled under the “create load” option.
• Once Jewels accepts the tender (which is automatic) the following happens:
  • TM will send a status message back to CT2 that Jewels is the pickup & the delivery trucker – No way around this currently
  • Have the est p/u date (which is the date the load was created)
• After the records are updated as “picked up” by Jewels on the e-forms, the TM sends the status message 1 with an actual pickup date confirmed.
• After Jewels updates the records on their e-form as “delivered”, meaning they were transferred to Lawrence, ALL of the CT records that were a part of that load, will NOW be marked as delivered.
• When Jag operator creates the 1 CT record containing 1 commodity line with the ttl # of plts, cartons & weight, they will have to do the following:
  • Make shipper Jewels Transportation & cnee whomever the shipments are going to (IE EA Roanoke, CEI Roanoke, Albert Farms) then manually upload that CT record to the TM
  • From the TM shipments page, create a load for it and tender to Lawrence or Albert Farms (wherever its going VA or ME)
  • TM will send a status message back to CT2 that Lawrence or Albert Farms is the pickup & the delivery trucker for this
  • Have the est p/u date (which is the date the load was created)
• After the record is updated as “picked up” by Lawrence/Albert Farms, the TM sends the status message 1 with an actual pickup date confirmed for only this 1 new created CT record.
• After Lawrence/Albert Farms updates the as “delivered”, only that 1 CT record will be updated and Jag operators will have to manually update all of the other CT records that went to Jewels for that load and change the delivery trucker and actual delivery dates.
  • It’s up to how the business side wants to handle this…but my suggestion was to do so at the time of the above - After Jewels updates - to be consistent for reporting purposes.

Lawrence

• Stacy updated the flat rate Lawrence tariff in the TM to include all moves ex various cities in VA to various cities in VA, as well as to NY, NJ & CT with the same flat rate.
• In order to make these loads “rate” correctly and tender to Lawrence according to this “flat rate tariff”, Stacy manually edits the ship to addresses from whatever the shipper entered at time of record creation to Lawrence Transportation’s Whse in VA.
• After that is done, she can create the load
• Once Lawrence accepts the tender (which is automatic) the following happens:
  • TM will send a status message back to CT2 that Lawrence is the pickup & the delivery trucker – No way around this currently
  • Set the est p/u date (which is the date the load was created)
• After the records are updated as “picked up” by Lawrence, the TM sends the status message 1 with an actual pickup date confirmed.
• After Lawrence updates the records as “delivered”, meaning they were transferred to Jewels, ALL of the CT records that were a part of that load, will NOW be marked as delivered.
• Then every Tues/Thurs Lawrence sends a manifest with load #’s that Etan uses to get all of the CT #’s to then create 1 CT record containing 1 commodity line with the ttl # of plts, cartons & weight, from the ASN as follows:
  • Shipper Jewels Transportation & cnee whomever the shipments are going to (IE CEI Holmdel, Rexam, Albert Farms) then manually uploads that CT record into the TM
  • From the TM shipments page, create a load for it and tender to Jewels, Ex Air or Albert Farms (wherever it’s going NJ, CT or ME)
  • TM will send a status message back to CT2 that Jewels, Express Air or Albert Farms is the pickup & delivery trucker
  • Have the est p/u date (which is the date the load was created)
• After the record is updated as “picked up” by Jewels, Ex Air, Albert Farms, the TM sends the status message 1 with an actual pickup date confirmed for only this 1 new created CT record.

* After Lawrence/Albert Farms updates the as “delivered”, only that 1 CT record will be updated and Jag operators would have to manually update all of the other CT records that went to Lawrence for that load and change the delivery truckers and actual delivery dates. ** It’s up to how the business side wants to handle this…but my suggestion was to do so at the time of the above - After Jewels updates - to be consistent for reporting purposes.

Tender of Direct Load

• After the load is tendered to the carrier and it is accepted, within 3 to 4 minutes the CT record(s) change their TMS status to: Load 1.

See #Figure_4

• At the same time, the estimated pickup date (which is the load create date), pickup trucker & delivery trucker will set. This at the same time, the shipper who created the record(s) will receive the portal dispatch and confirmation e-mail.

Tender of Pool Point Load

• Once selected carrier is set and the load is tendered, that load will move from the summary list to either the tendered loads or the accepted tendered loads list.
  • Jewels Transportation is the only pool point location set in the TM to handle all of the local tri-state area pickups that are destined to ME or VA, NC, TN &/or GA.

• Once the carrier is selected and the load is rated, it can be tendered, which will go to both of the carriers. Currently this is something that Descartes is looking into to avoid the multiple tendered delivery loads as this is causing inaccurate trailer counts for Lawrence Transportation & Albert Farms.

• Again, after the load(s) is tendered to both carriers and accepted, within 3 to 4 minutes the CT record(s) change their TMS status to: Load 1. Which at the same time, the estimated pickup date (which is the load create date), pickup trucker & delivery trucker will set. This at the same time, the shipper who created the record(s) will receive the portal dispatch and confirmation e-mail.

After carrier accepts the load tender

• After the carrier(s) accept the load(s) and updates the progress, within 3 to 4 minutes of their update(s), the TM will update the CT record(s) and they will have a TMS status set of: Status 1.

See #Figure_6

• As the carrier(s) continue to update any of the pickup &/or delivery information, the TM will update the same and again the CT record(s) will update within 3 to 4 minutes with a new TMS status of: Status 2, 3, etc, until delivered.

How to handle updates for CT records that have a TMS Status of Load 1, 2, 3, etc

• The record(s) should not be updated via CyberTrax as any changes made, will not update the TM.

• If changes are needed, the following steps should be taken:

1. From the TM, cancel the tendered load.

2. Delete the load. Once the load is deleted, the shipment record(s) will move back to the shipments page.

3. Once records are back on the shipments page, make any/or all changes to the records accordingly inside of CyberTrax.

4. Upon save, the same updates made in the CT record(s) and will be made in the TM.

5. Continue with the shipment record(s) to re-create the load(s).

Loads Marked as Delivered

Once the load is delivered, it is closed inside the TM and cannot be opened or updated unless a request is sent to Descartes.

• If an e-form carrier (IE – Jewels, Albert Farms, Lawrence, Express Air) are unable to update a load and receive some sort of an error message from Descartes, it is quite possible that they checked the “I have completed reporting all the required Shipment Status messages”….

See #Figure_7

• If that is the case, an e-mail message should be sent to Descartes for them to cancel the load. Once that is done by Descartes, the tender must be resent to the carrier and they will have to update the shipment(s) status accordingly.

Figures

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

History

Pool Point Loads

The business process has changed for Pool Point Loads in Dec 2010 as the TM does not allow for the second leg of the shipment to be tendered at a separate time and/or allow for multiple loads to be combined under 1 master load #. Therefore our PP concept was created - see Pool_Point

• When you right click to consolidate with pool point, the TM creates 2 separate loads: 1st load is from the pickup location to the pool point and the 2nd load is from the pool point to the final delivery location. Again the TM will NOT take into consideration the cargo available date(s) as per previous business rule requirements and once the shipment record(s) are selected, it will move from the shipment page, onto the load page. The record(s) will be inside of the load # the TM sets automatically and the load(s) will also have a status: new or rated.

See #Figure_5

• Upon the browser refreshing, the load(s) status will change to rated and a carrier will be selected. If the carrier the TM chose is not the carrier to use for the move, suggest right clicking and selecting a different carrier.

• The system will check all of the carrier’s tariffs and assign the carrier, as well as take into consideration the carrier routing rules that were already setup. If no carrier is listed, it is very possible that there aren’t any carrier’s tariffs covering that lane or if only 1 carrier is listing, again it is very possible that there aren’t any carrier tariffs in the TM, covering that lane.

• Should a specific carrier need to be assigned according to the business process and does not come up, suggest right clicking and select add a manual rate. Add a rate of $ 1.00, assign the carrier accordingly and follow up with Arden as usual for those rates.

test