Requirements for EDI to TMS
From UG
(Difference between revisions)
(→About) |
(→Introduction) |
||
| Line 26: | Line 26: | ||
* [[#Vendor evaluation]] | * [[#Vendor evaluation]] | ||
* [[#CT2 and TMS integration]] | * [[#CT2 and TMS integration]] | ||
| + | * [[#TMS User interaction and workflow]] | ||
=== Vendor evaluation === | === Vendor evaluation === | ||
| Line 33: | Line 34: | ||
* from Lean Logistics | * from Lean Logistics | ||
| - | === | + | === CT2 and TMS integration === |
In a nutshell: | In a nutshell: | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | + | * (shipment record will be created in CT2 and approved) | |
| + | * '''IP1:''' New CT2 forwarded to TMS through EDI | ||
| + | * (in TMS Jag oper will run optimizations and select carrier) | ||
| + | * (TMS sens bids to carriers) | ||
| + | * '''IP2:''' TMS sends updates to CT2 (Carrier suggested, estim. pick up date, etc) | ||
| + | * (carrier accepts the bid) | ||
| + | * '''IP3:''' TMS sends updates to CT2 (Carrier confirmed, etc) | ||
| + | * (start processing shipments) | ||
| + | * '''IP4:''' carrier '''periodically''' submits updates into TMS (example: actual pickup date, etc) | ||
See Figure below: | See Figure below: | ||
| Line 50: | Line 53: | ||
[[File:Ip lean 1.JPG]] | [[File:Ip lean 1.JPG]] | ||
[[File:Ip lean 2.JPG]] | [[File:Ip lean 2.JPG]] | ||
| + | |||
| + | === User to TMS interaction and workflow === | ||
| + | |||
| + | This is out of scope of this project. But it is still good to have some idea about what is happening at this level. At the moment knowledge is limited, but we know that: | ||
== Workflow == | == Workflow == | ||
Revision as of 18:30, 19 July 2010
Contents |
About
This is a Analysis / Requirements wiki for EDI to TMS proj
Glossary
IP - Integration Point
Introduction
Core Business Need: Jaguar needs ability to optimize truck domestic shipments:
- create optimal loads, cost, routs, etc
- automate tariffs, communication with carriers
Above features are normally present in TMS software.
To achieve that it was decided:
- buy and use existing TMS solution (phase 1) - this project
- gradually add these features to CT2 (phase 2) - another project
To complete phase 1 we need to implement:
Vendor evaluation
Currently there are 2 systems we are considering:
- from Descartes
- from Lean Logistics
CT2 and TMS integration
In a nutshell:
- (shipment record will be created in CT2 and approved)
- IP1: New CT2 forwarded to TMS through EDI
- (in TMS Jag oper will run optimizations and select carrier)
- (TMS sens bids to carriers)
- IP2: TMS sends updates to CT2 (Carrier suggested, estim. pick up date, etc)
- (carrier accepts the bid)
- IP3: TMS sends updates to CT2 (Carrier confirmed, etc)
- (start processing shipments)
- IP4: carrier periodically submits updates into TMS (example: actual pickup date, etc)
See Figure below:
Figure Integration Points
User to TMS interaction and workflow
This is out of scope of this project. But it is still good to have some idea about what is happening at this level. At the moment knowledge is limited, but we know that:
Workflow
High level view of Workflow
- Numbers of CTs gets approved by CT2 Planner user
- CT2 sends info about these CTs to TMS (IP1)
- discover them in TMS
- browse them in TMS
- "route" them in TMS
- option 1: use optimization module
- option 2: manually optimize
