Requirements for EDI to TMS
From UG
(Difference between revisions)
m (moved EDI to TMS REQ to Requirements for EDI to TMS) |
(→CT2 and TMS integration) |
||
| Line 38: | Line 38: | ||
* carrier submits updates into TMS (example: actual pickup date) | * carrier submits updates into TMS (example: actual pickup date) | ||
* update above will be forwarded into CT2 through EDI | * update above will be forwarded into CT2 through EDI | ||
| + | |||
| + | See also ''Integration Points.pdf'' attached to 2183. | ||
Revision as of 23:12, 16 July 2010
Contents |
About
This is a Analysis / Requirements wiki for EDI to TMS proj
Intro
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)
- gradually add these features to CT2 (phase 2)
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 forwarded to TMS through EDI
- in TMS Jag oper will run optimizations
- TMS sens bids to carriers
- one carrier accepts the bid and start moving shipments
- carrier submits updates into TMS (example: actual pickup date)
- update above will be forwarded into CT2 through EDI
See also Integration Points.pdf attached to 2183.
