Business Process for Arden Trucking Domestic October 2010
From UG
Contents |
General
Mantis: http://mantis.jaguarfreight.com/mantis/view.php?id=2228
Intro
This is a part of the NATP and is an updated explanation of their Business Process. To be used for testing purposes and discovery of current workflow to ensure most cases are considered and any bugs.
Summary
There are two JFS operators who handle the majority of routings for the EA domestic trucking shipments; Stacy & Erin. Erin handles LTL freight from the Tri-State to the Tri-State area, including LTL shipments that are going to VA and/or ME by using Jewels Transportation as a pooling point. Stacy handles FTL freight to and from the NE, SE, MW & WC, including all of the small package freight, which is up to 150#. Stacy also handles domestic trucking Canada freight.
Use case 1. Shipper created CT from web portal & gets approved by Planner
Normal Flow of Events
1) Traffic planner from EA traffic department or E.M. approves a CT record from the web portal
2) Jaguar operator looks at dashboard to find new shipments approved
NOTE: This is typically done every 15mins to ½ hr
3) Jaguar operator updates CT records via Virtual Group with pickup trucker’s company name, estimated pickup date and sends out batched e-mail confirmations to the pickup trucker for them to collect the goods the following day
NOTE: This is done continuously throughout the day
4) Jaguar operator follows up and tracks the collection & delivery of
5) Jaguar operator fax/e-mail traffic sheet to truck company
See #Figure 1. Create CT from Traffic sheets
Figure 1. Create CT from Traffic sheets
Use case 2a. Direct Pick-up and deliver (NJ, NY, and CT)
Normal Flow of Events
1) Truck company received Traffic sheets
2) Trucker goes to pick up shipment from shipper(s); this can be many truckers to pick up shipment from many other shippers in tri-states area
3) Trucker unloads shipments at the warehouse to consolidate
4) Trucker loads shipments and delivers shipment to consignees
5) Consignees receive shipments and give confirmation POD (proof of delivery) document to Trucker
6) Trucker writes CT# reference on POD (CT# must be matched to the CT# that was created by Jaguar operator)
7) Trucker fax/e-mail POD to Jaguar company
NOTE: This case will be billed from pick-up location to delivery location for truck movement
See #Figure 2a. Direct Pick-up and deliver (NJ, NY, and CT)
Figure 2a. Direct Pick-up and deliver (NJ, NY, and CT)
Use case 2b. Consol Pick-up and deliver (VA)
Normal Flow of Events
1) Truck company received Traffic sheets
2) Trucker goes to pick up shipment from shipper(s); this can be many truckers to pick up shipment from many other shippers in tri-states area
3) Trucker unloads shipments at the warehouse to consolidate
3a) A different truck company will handle shipments from the warehouse to consignee
NOTE: Jaguar handles shipments from shippers to warehouse ONLY
4) Shipments get received and confirmed by warehouse people
5) Warehouse people give POD (proof of delivery) to trucker
6) Trucker writes CT# reference on POD (CT# must be matched to the CT# that was created by Jaguar operator)
7) Trucker fax/e-mail POD to Jaguar company
NOTE: This case will be billed from pick-up location to warehouse location for truck movement
See #Figure 2b. Consol Pick-up and deliver (VA)
Figure 2b. Consol Pick-up and deliver (VA)
Use case 3. Bill to truck planner
Normal Flow of Events
1) Jaguar receives POD from Trucker via fax/e-mail
2) Operator updates CT record with delivery date
3) Operator creates CT groups. One group per traffic planner per day. There are 3 planners.
4) Operator creates a master on top of every group
5) Operator creates Trucking Billing Manifest for each master (this can be up to 3 spreadsheet per day; 3 traffic planners)
6) Operator updates rate information
7) Operator sends it to truck company
8) Truck company updates information and sends it back to Jaguar
9) Jaguar adjust number (adding margin) in order to bill the traffic planner(s);
10) Operator creates one pdf invoice and attaches all Trucking Billing Manifest and sends to the client
See #Figure 3. Bill to truck planner
Figure 3. Bill to truck planner
