Use Cases for EDI to TMS
From UG
Contents |
Business story
This needs to reflect typical and some exceptional workflows
- 3 CTs get approved
- CT2 sends data to TMS
- Jag oper discovers new approved CTs (how?)
- a) Jag oper manually processes CT
- updates
- docs
- etc
- b) Jag oper uses optimization to handle CT
- updates
- docs
- etc
Use Cases
Use case 1. Shipper Creates CT via Web Portal
Normal Flow of Events
1) Shipper logs into the web portal to enter all new products that are ready to ship and Upon clicking save, they create 1 CT per line item.
2) Planner logs into the web portal to view all new records created by shipper and sets the approval status to "Approved".
NOTE: This is done continuously throughout the day.
3) Jaguar operator logs into CT2 internal application to find these "Approved" CT records on their TDS dashboard.
4) Jaguar operator logs into the TMS system to find same "Approved" CT records from internal app and reviews the information so they can begin to assign truckers.
5) Through TMS, Jag operator assigns the pickup trucker and sets the estimated pickup date.
6) TMS then transits this information to the pickup trucker and sends back a response to Jag operator.
Use case 2a. Direct Pickup and delivery (NJ, NY, and CT)
Normal Flow of Events
1) Trucking company receives all relevant shipping information from TMS and accepts the shipment.
2) Trucker goes and pickups the shipments from each of the shippers (this can be many truckers picking up many shipments from many different shipper's who are all within the tri-state area).
3) Trucker unloads the shipments at the warehouse to consolidate.
4) Trucker loads the shipments and delivers the shipments to the consignee.
5) Consignee receives their shipments and gives a confirmation POD (proof of delivery) document to the trucker.
6) Trucker writes the CT# reference on the POD (CT# must be matched to the CT# that was created by shipper user).
7) Trucker faxes/e-mails the POD to Jaguar.
8) Jaguar operator uploads the POD document into the CT record.
