Business Process for Arden Trucking Domestic October 2010

From UG

Revision as of 22:52, 28 October 2010

General

Mantis: http://mantis.jaguarfreight.com/mantis/view.php?id=2489

Intro

This is an updated explanation to the NATP Business Process. This is to be used for testing purposes and discovery of their current workflow to ensure most cases are considered.

There is a related workflow already recorded in Wiki, see Business Process for Arden Trucking Domestic.

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.

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.
• She mainly deals with 2 truckers, Express Air & Jewels Transportation, and does have some contact with FTL trucker Albert Farms.
• Etan works directly with Erin and he assists her in updates, but he is here on a part time basis.

Stacy

• Stacy handles FTL freight to and from the NE, SE, MW & WC, including all of the small package freight & Canada freight.
  • Small package freight are shipments that are up to 150 lbs.
• She mainly deals with the remaining trucking 9 companies - Lawrence Transportation, Harris Trucking, Daybreak Express, Land Star, Albert Farms, LEI, YRC, Fed-Ex & UPS and she does have some involvement with pool point carrier, Jewels Transportation.

Use case 1. FTL shipper created CT record gets approved by Planner & JFS routes

Normal Flow of Events

1) EA Traffic planner or E.M. traffic planner approves a FTL CT record that a shipper created in 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.

4) Jag operator sends out batched e-mail confirmations to the pickup trucker for them to collect todays approved goods the following day

NOTE: The above 2 steps are done continuously throughout the day

4) Jaguar operator follows up, tracks the collection & delivery of the shipment. They update the CT records via virtual group the actual pickup, the delivery trucker & the actual delivery dates.

NOTE: With this new process, Jaguar Freight will not receive PODs from 99% of the truckers used to deliver the goods as only 1 trucker bills Jaguar Freight directly, while all of the remaining truckers bill EA directly.

Use case 2a. Direct Pick-ups and delivery (NJ, NY, and CT)

Normal Flow of Events

1) EA Traffic planner(s) and/or E.M. traffic planner(s) approve LTL CT record(s) that shippers created in 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.

4) Jag operator sends out batched e-mail confirmations to the pickup trucker for them to collect todays approved goods the following day

NOTE: The above 2 steps are done continuously throughout the day

5) Trucker goes to pick up shipment from shipper(s); this can be many trucker drivers of same trucking company to pick up shipment from many other shippers in tri-states area

6) Trucker unloads shipments at the warehouse to consolidate

7) Trucker loads shipments and delivers shipment to consignees

NOTE: With this new process, Jaguar Freight will not receive PODs from 99% of the truckers used to deliver the goods as only 1 trucker bills Jaguar Freight directly, while all of the remaining truckers bill EA directly.

Use case 2b. Consolidate with Pool Point, Tri-State Pick-up(s) and VA or ME deliveries

Normal Flow of Events

1) EA Traffic planner(s) and/or E.M. traffic planner(s) approve LTL CT record(s) that shippers created in 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.

4) Jag operator sends out batched e-mail confirmations to the pickup trucker for them to collect todays approved goods the following day

NOTE: The above 2 steps are done continuously throughout the day

5) Trucker goes to pick up shipment from shipper(s); this can be many trucker drivers of same trucking company to pick up shipment from many other shippers in tri-states area

6) Trucker unloads shipments at their warehouse onto another carriers empty trailer for them to come and pickup that same night

7) Delivery trucker collect the now full trailer and delivers shipment to consignee(s)

NOTE: With this new process, Jaguar Freight will not receive PODs from 99% of the truckers used to deliver the goods as only 1 trucker bills Jaguar Freight directly, while all of the remaining truckers bill EA directly.

Once TM is live, the next day after, Jag operator will receive an update from the pool point and delivery trucker advising them of which CT records were loaded onto what trailer. Then Jag operator will go into the TM, move and tweak shipments to match the delivered load.

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