Requirements for EDI to TMS
From UG
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
Requirements/Design tasks breakdown:
- analyze documentation provided by TMS vendor
- identify what CT fields to send to TMS
- provide mapping (name in CT2 vs name in TMS, for example in CT2 what we call "HU" in TMS might be called "Units")
- create "DD (data dictionary) wiki"
- identify and document gaps between type/format of fields in TMS vs EDI
- identify if we have any fields missing in CT2 that is required for optimization
- create examples of XML strings that would be used to send (assume we send over FTP):
- CT info to TMS from CT2
- updates from TMS to CT2
- design complete workflow
- document most typical use cases
Development tasks breakdown:
- review REQ doc
- review TMS guide
- decide on particular technology for EDI (message format, protocol)
- implement
- test
