TMS

From UG

Revision as of 18:30, 19 July 2010 (edit) Alex (Talk | contribs) (Created page with 'Category:Glossary '''TMS''' - Transportation Management System') ← Older edit		Revision as of 00:43, 17 May 2013 (edit) (undo) Alex (Talk | contribs) Newer edit →
Line 1:		Line 1:
-	[[Category:Glossary]]	+	[[Category: EDI to TMS]]
-	'''TMS''' - Transportation Management System	+	== Def ==
		+
		+	'''TMS''' - in general it is Transportation Management System.
		+
		+	In our case it is the Descartes TMS that we integrated with our CT2 system.
		+
		+	== TMS Admin ==
		+
		+	=== Admin Requirements ===
		+
		+	Not to hard code specific CT2/TMS functionality, so as to allow management users the ability to set specifics. Full spec is under category: EDI to TMS
		+
		+	What can be managed here are the following:
		+
		+	*Automatic and manually forwarding the approved portal CT records to the TMS
		+	**Setup the CT2 & TMS server addresses for exchange
		+	**Users can un-check auto option and select dates from calendar
		+
		+	* Automatically accept updates sent to CT2 from the TMS
		+	**This can be managed in number of seconds
		+	**Option for FTP server to hold/store xml files received that have a future date is set and re-ck at a specif time - IE currently set to 12am
		+
		+	* Allowing management users to change/set the number of days, on the Shipment Import XML file, between the earliest pickup date and latest pickup date - IE currently set to 7days from the Approved On Date which = Earliest Pickup Date
		+
		+	== Admin mock up ==
		+
		+	[[File:Client App Admin.JPG]]
		+
		+
		+	== See also ==
		+	These are the original Analysis / Requirements wiki for EDI to TMS proj Mantis: [http://ct.jaguarfreight.com/mantis/view.php?id=2183 2183] & the phase 2 are found here: [http://ct.jaguarfreight.com/mantis/view.php?id=2539 2539]

---

Revision as of 00:43, 17 May 2013

Contents 1 Def 2 TMS Admin 2.1 Admin Requirements 3 Admin mock up 4 See also

Def

TMS - in general it is Transportation Management System.

In our case it is the Descartes TMS that we integrated with our CT2 system.

TMS Admin

Admin Requirements

Not to hard code specific CT2/TMS functionality, so as to allow management users the ability to set specifics. Full spec is under category: EDI to TMS

What can be managed here are the following:

• Automatic and manually forwarding the approved portal CT records to the TMS
  • Setup the CT2 & TMS server addresses for exchange
  • Users can un-check auto option and select dates from calendar

• Automatically accept updates sent to CT2 from the TMS
  • This can be managed in number of seconds
  • Option for FTP server to hold/store xml files received that have a future date is set and re-ck at a specif time - IE currently set to 12am

• Allowing management users to change/set the number of days, on the Shipment Import XML file, between the earliest pickup date and latest pickup date - IE currently set to 7days from the Approved On Date which = Earliest Pickup Date

Admin mock up

See also

These are the original Analysis / Requirements wiki for EDI to TMS proj Mantis: 2183 & the phase 2 are found here: 2539