Use Cases for EDI to TMS

From UG

(Difference between revisions)
Jump to: navigation, search
(→Figure 3)
(→About)
 
(95 intermediate revisions not shown)
Line 1: Line 1:
[[Category:EDI to TMS]]
[[Category:EDI to TMS]]
-
== Business story ==
+
== About ==
 +
<font color="red" size="6"> This article was used as an idea on how the Arden domestic team would use the TM.  It is not relevant to the current business process as it was newly defined. </font>
-
''' July 22'''
+
== Examples ==
-
''Shipper Mary with Jackel creates 1 new CT record (# 11111) shipping from her NJ warehouse, Gannet Warehouse at 58 Executive Drive in Edison, NJ.  She only has 1 pallet ready and would like to get this off of her warehouse dock so her warehouse can continue with their monthly inventory stock report.  Now at the same shipper Harry with Princeton Label creates 1 new CT record (# 11145) shipping from his NJ warehouse, Princeton Labels & Packaging Inc at 1226 Route 130 in Robbinsville, NJ.  He has about 15 pallets that are ready to ship today and hopes that CEI Roanoke will approve this PO/SKU to ship.''
+
=== One CT from A to B ===
-
'''...later that day...'''
+
* import/create 1 CT
 +
* move CT from A to B on one truck  (manually) (One Load?)
 +
* Assign trucker (manually)
 +
* Assign pickup/delivery dates (manually?)
-
''Shipper Ed with Rexam creates 1 new CT record (# 11200) shipping from his CT warehouse, Rexam at 60 Electric Avenue in Thomston, CT and he also has only 1 pallet that is ready to ship'''
+
=== Two CTs from A to B ===
-
'''...even later that day...'''
+
* import/create 2 CT
 +
* move both CTs from A to B on one truck  (manually) (One Load?)
 +
* Assign trucker (manually)
 +
* Assign pickup/delivery dates (manually?)
-
''2 separate Arden planners approve these 3 CT records at the same time (# 11111, 11145 & 11200) and now Jag operator Susan checks her TDS dashboard to find these 3 approved shipments''
+
=== Combining 2 shipments Miami to Boston and Atlanta to NY into one load ===
-
This needs to reflect typical and some exceptional workflows
+
* CT1:
 +
** from: Miami, FL
 +
** to: Boston, MA
-
* 3 CTs get approved
+
* CT2:
-
* CT2 sends data to TMS
+
** from: Atlanta, GA
-
* Jag oper discovers new approved CTs (how?)
+
** to: New York, NY
-
* a) Jag oper manually processes CT
+
-
* updates
+
-
* docs
+
-
* etc
+
-
* b) Jag oper uses optimization to handle CT
+
-
* updates
+
-
* docs
+
-
* etc
+
-
=== Use Cases ===
+
==== Shipment Import XML ====
 +
TBD
-
==== Use case 1. Jaguar Discovers Approved CTs ====
+
==== Optimal route ====
-
===== Figure 1 =====
+
* Track A:
 +
** Start: Pick up CT1 in Miami
 +
** Stop#1: Pick up CT2 in Atlanta
 +
** Stop#2: Drop off CT2 in New York
 +
** Finish: Drop off CT1 in Boston
-
Jaguar operator logs into CT2 internal application to find 3 new "Approved" CT records on their TDS dashboard.
+
===== Load Plan XML for Optimal=====
 +
TBD
-
[[File:Susan's TDS.JPG]]
+
==== Non Optimal route ====
-
===== Figure 2 =====
+
* Track A:
 +
** Start: Pick up CT1 in Miami
 +
** Finish: Drop off CT1 in Boston
-
Jaguar operator logs onto the TMS system, goes into the Main Menu, > Activity Summaries > Activity Details to find their are new shipments listed.  (These are the same "Approved" CT records that are on their TDS dashboard on the internal app).
+
* Track B:
 +
** Start: Pick up CT2 in Atlanta
 +
** Finish: Drop off CT2 in New York
-
[[File:Activity Details Page n1.JPG]]
+
===== Load Plan XML for Non Optimal =====
 +
TBD
-
===== Figure 3 =====
+
==== TMS use options ====
-
Jag operator clicks on the 3 new to review for them to decide who they would like to arrange for the pickup.
+
* operator creates [[#Optimal route]] manually
 +
** discovering shipments to combine
 +
** discovering optimal route
 +
** discovering optimal cost carrier
-
[[File:TMS Shipment list.JPG]]
+
* operator creates [[#Non Optimal route]] manually
-
===== Figure 4 =====
+
* operator runs optimization and system suggests [[#Optimal route]]
-
Jag operator looks at the first CT record.
+
=== Link to User Guide ===
-
[[File:TMS Shipment 1.JPG]]
+
Similar example - see Pic on page 153 in Descartes TMS User guide.
 +
== Business story ==
 +
''' July 22'''
 +
''Shipper Mary with Jackel creates 1 new CT record (# 11111) shipping from her NJ warehouse, Gannet Warehouse at 58 Executive Drive in Edison, NJ.  She only has 1 pallet ready and would like to get this off of her warehouse dock so her warehouse can continue with their monthly inventory stock report.  Now at the same shipper Harry with Princeton Label creates 1 new CT record (# 11145) shipping from his NJ warehouse, Princeton Labels & Packaging Inc at 1226 Route 130 in Robbinsville, NJ.  He has about 15 pallets that are ready to ship today and hopes that CEI Roanoke will approve this PO/SKU to ship.''
-
===== Figure 6 =====
+
'''...later that day...'''
-
Jag operator looks at the second CT record.
+
''Shipper Orlando with Pochet creates 1 new CT record (# 11200) shipping from his NJ warehouse, Vecco Holdings at 6801 West Side Avenue in North Bergen and he also has only 1 pallet that is ready to ship'''
-
[[File:TMS Shipment 2.JPG]]
+
'''...even later that day...'''
 +
''At once, 2 separate Arden planners approve these 3 CT records (# 11111, 11145 & 11200) and now Jag operator Susan notices that her TDS dashboard has 3 approved shipments.  So she logs into TMS and finds those same 3 records on her new shipment list.  Its now 3:45 in the afternoon and as Susan reviews each of the shipments, she notices they are all shipping from NJ and arranges in TMS to build a load with the optimization process.  After her load is built, she tenders the load to Jewels Transportation and awaits their replies.''
 +
'''...shortly before quitting time...'''
-
===== Figure 7 =====
+
''Jewels accepts the tender, confirms they'll arrange to collect all 3 shipments at 17 pallets total the next day.  Now all 3 CT2 records are updated with the pickup truckers name, as well as the estimated pickup date.  As well, all 3 shippers, including EA Dom receive an e-mail notification from cybertrax@jaguarfreight.com that their records were approved and Jewels Transportation will pickup.''
-
Jag operator looks at the third CT record.
+
'''Late afternoon July 23'''
-
[[File:TMS Shipment 3.JPG]]
+
''Jewels collects all 3 shipments and updates their system.  Trucker unloads these shipments at his warehouse and places the 1 shipment to the side for a different carrier to arrange the delivery and updates their system that all were collected and on hand.  Once they update their system, that information is sent to TMS, then TMS sends the information to Jaguar and automatically updates the CT records with the actual pickup date.''
 +
'''...early evening'''
 +
''Delivery trucker, Lawrence Trucking goes in to pick up the 1 shipment for CEI Roanoke.  He signs a confirmation receipt (which is like a POD) of what he is picking up and gives a copy to Jewels.  They update their system that this 1 shipment was transferred to the delivery trucker accordingly and their system sends that information to TMS, then TMS sends the information back to Jaguar and automatically updates the CT record with the delivery truckers name, including the estimated & actual delivery dates.  Now Jewels takes the signed confirmation receipt, writes the CT# reference on it (as the CT# must match the CT# that was created by shipper user) and faxes/e-mails the POD to Jaguar Freight.''
-
3) Now through TMS, Jag operator assigns the pickup trucker.
+
'''...shortly after Lawrence leaves Jewels dock'''
-
4) Then TMS transits this information to the pickup truckers system and waits for their acceptance or rejection.
+
''Jewels warehouse manager is arranging for his truckers morning deliveries.  He loads his driver with several different shipments delivering to the local NJ area which includes these 2 shipments that are delivering to CEI Holmdel.  He updates his system that these 2 shipments will be delivering tomorrow Jul 24 and that information sends to TMS.  Then TMS sends the information back to Jaguar and automatically updates the CT record with the delivery truckers name, including the estimated date.''
-
=== Use case 1a. Direct Pickup and delivery (NJ)  ===
+
'''the next morning July 24...'''
-
1) Trucking company receives all relevant shipping information (pickup & delivery address, the packaging information - including weight and volume) from TMS.  
+
''Jag operator Susan receives the Lawrence POD from Jewels and up loads the POD into the CT record.  She also checks to see that Jewels has arranged for the 2 shipments to CEI Holmdel for delivery today.''
-
1a) Trucker confirms to TMS that they accept the shipment.
+
'''...right before lunch'''
-
1b) TMS receives this acceptance, sends the information back to Jaguar and automatically updates the CT records with the pickup trucking companies name.
+
''Jewels dispatcher hears from his local NJ driver who advises he just got a flat tire...He advises him that it's going to take some time before he can get it fixed and is unsure if he can arrange his last drop...His last drop or delivery is for CEI Holmdel.  Now Jewels Dispatcher calls Jaguar to notify them of the same and Jaguar advises Debbie at CEI Holmdel that her delivery will be late''
-
2) Trucker updates his system with an estimated pickup date.
+
'''4:35 pm...'''
-
2a) Truckers system sends that information to TMS, then TMS sends the information back to Jaguar and automatically updates the CT records with the estimated pickup date.
+
''After some long hours of phone calls and e-mails, the Jewels driver was successful in fixing his flat, as well as delivering these 2 shipments to CEI Holmdel. He calls his dispatcher to advise this and he updates his system that these 2 shipments were delivered today Jul 24.  That information is sent to TMS, then TMS sends that same information back to Jaguar and automatically updates the CT record with the actual delivery date.''
-
3) Trucker pickups the 1 shipment from the shipper's warehouse.
+
'''..whenever the driver returned'''
-
4) Trucker unloads the shipments at his warehouse to arrange for delivery the following day and updates his system.
+
''Jewels takes the POD (or signed confirmation receipt), makes sure that the CT# is listed on the paperwork and faxes/e-mails the POD to Jaguar Freight.''''
-
4b) Truckers system sends that information to TMS, then TMS sends the information to Jaguar and automatically updates the CT record with the actual pickup date.
+
'''the following morning July 25'''
-
5) Trucker now updates his system that the shipment is loaded onto a truck and is out for delivery.
+
''Jaguar operator received the POD document and uploads it into the CT record.'''
 +
 
 +
=== Use Cases ===
 +
 
 +
==== Use Case 1. ====
 +
 
 +
===== Jaguar Discovers Approved CTs =====
 +
 
 +
====== Figure 1 ======
 +
 
 +
Jaguar operator logs into CT2 internal application to find 3 new "Approved" CT records on their TDS dashboard.
 +
 
 +
[[File:Susan's TDS.JPG]]
 +
 
 +
===== Jaguar Operator uses TMS =====
 +
 
 +
====== Figure 2 ======
 +
 
 +
Jaguar operator logs onto the TMS system, goes into the Main Menu, > Activity Summaries > Activity Details to find their are new shipments listed.  (These are the same "Approved" CT records that are on their TDS dashboard on the internal app).
 +
 
 +
[[File:Activity Details Page n1.JPG]]
 +
 
 +
====== Figure 3 ======
 +
 
 +
Jag operator clicks on the number of new shipments (3) to review for them to decide who they would like to arrange for the pickup.
 +
 
 +
[[File:TMS Shipment list 1.JPG]]
 +
 
 +
====== Figure 4 ======
 +
 
 +
Jag operator looks at the first CT record # 11111.
 +
 
 +
[[File:TMS Shipment 1.JPG]]
-
5a) Jaguar operator goes into TMS to update the estimated delivery date.
+
====== Figure 5 ======
-
5b) Truckers system sends that information to TMS, then TMS sends the information back to Jaguar and automatically updates the CT records with the estimated delivery date.
+
Jaguar operator Susan begins the optimization Process from the new shipment list. She highlights all 3 new shipments, then she right clicks and chooses option '''''Consolidate All'''''.  Now the build load page displays.  
-
6) Consignee receives their shipment and gives a confirmation POD (proof of delivery) document to the trucker.
+
[[File:TMS Build Loads 1.JPG]]
-
7) Trucker updates his system with the confirmation POD information (Name of who signed for it, date and time) received from the consignee.
+
====== Figure 6  ======
-
7b) Truckers system sends that information to TMS, then TMS sends the information back to Jaguar and automatically updates the CT records with the actual delivery date.
+
Jaguar operator routes via TMS and uses the '''''Interactive Load Editor''''' to arrange the order of pickups and once done, chooses '''''Validate''''' so she can send a tender to the trucker.
-
8) Trucker writes the CT# reference on the POD (CT# must match the CT# that was created by shipper user).
+
[[File:Consolidation Build Load2.JPG]]
-
9) Trucker faxes/e-mails the POD to Jaguar.
+
====== Figure 7 ======
-
10) Jaguar operator uploads the POD document into the CT record.
+
Jaguar operator tenders the load load to Jewels Trucking by right clicking on the load number. TMS transits this information to the pickup truckers system and Jag operator waits for their acceptance or rejection.
-
=== Use case 1b. Consol Pick-up and deliver (VA)  ===
+
[[File:TMS Tender Available Loads.JPG]]
-
1) Trucking company receives all relevant shipping information (pickup & delivery address, the packaging information - including weight and volume) from TMS.
 
-
1a) Trucker confirms to TMS that they accept the shipment.
+
== Various Use Cases  ==
-
1b) TMS receives this and sends the information back to Jaguar and automatically updates the CT records with the pickup trucking companies name.
+
=== UC 101 Editing Shipment data on CT side after Shipment Import ===
-
2) Trucker updates his system with an estimated pickup date.
+
see [[Shipment_Import#UC_101_Editing_Shipment_data_on_CT_side_after_Shipment_Import]]
-
2a) Truckers system sends that information to TMS, then TMS sends the information back to Jaguar and automatically updates the CT records with the estimated pickup date.
+
=== UC 102 Editing Shipment data on TMS side after Shipment Import ===
-
3) Trucker pickups the shipments from each of the shippers (trucking company can use many different drivers to pickup within the tri-state area).
+
Only some fields will be updated in CT DB through Load Plan.
-
4) Trucker unloads the shipments at his warehouse and places them to the side for another carrier to arrange the delivery and updates his system that they are ready (or on hand) for pickup.
+
Descartes can not make Shipment fields read only.
-
NOTE: Jaguar handles these shipments from the shipper's to the warehouse ONLY.
+
=== UC 103 One Commodity line with both loose and plts will translate into 2 line items on Descartes side ===
-
4a) Truckers system sends that information to TMS, then TMS sends the information to Jaguar and automatically updates the CT record with the actual pickup date.
+
Line with loose will have Qty=0 and Weight = 0.01
-
5) Delivery trucker now goes in to pick up the shipments, signs a confirmation receipt (which is like a POD) of what he is picking up and gives a copy to the pickup trucker.  Pickup trucker updates their system that the shipments were transferred to the delivery trucker accordingly.
+
=== UC 104a Re tendering before Trucker accepts ===
-
5a) Truckers system sends that information to TMS, then TMS sends the information back to Jaguar and automatically updates the CT records with the estimated & actual delivery dates.
+
1. CT#xxx was made part of load LD#yyy
 +
2. LD#yyy was tendered to Trucker ZZZ and pending acceptance
 +
3. Jaguar want to change the Trucker
-
6) Pickup trucker takes the signed confirmation receipt, writes the CT# reference on it (CT# must match the CT# that was created by shipper user).
+
=== UC 104b Re tendering because Trucker rejects ===
-
7) Trucker faxes/e-mails the POD to Jaguar.
+
=== UC 104c Re tendering after Trucker accepts ===
 +
This case can't happen.
-
8) Jaguar operator uploads the POD document into the CT record.
+
=== UC 200 Shipment Import for Approved with date ===
 +
Does it work.
-
== Use case ==
+
== Questions ==
-
== Figures ==
+
* Will routed / pick up counter update correctly?
 +
* Will they generate any reports?
 +
* If CT is too large (>26?plts?) it will not be processed by TMS

Current revision as of 20:32, 20 December 2010


Contents

[edit] About

This article was used as an idea on how the Arden domestic team would use the TM. It is not relevant to the current business process as it was newly defined.

[edit] Examples

[edit] One CT from A to B

  • import/create 1 CT
  • move CT from A to B on one truck (manually) (One Load?)
  • Assign trucker (manually)
  • Assign pickup/delivery dates (manually?)

[edit] Two CTs from A to B

  • import/create 2 CT
  • move both CTs from A to B on one truck (manually) (One Load?)
  • Assign trucker (manually)
  • Assign pickup/delivery dates (manually?)

[edit] Combining 2 shipments Miami to Boston and Atlanta to NY into one load

  • CT1:
    • from: Miami, FL
    • to: Boston, MA
  • CT2:
    • from: Atlanta, GA
    • to: New York, NY

[edit] Shipment Import XML

TBD

[edit] Optimal route

  • Track A:
    • Start: Pick up CT1 in Miami
    • Stop#1: Pick up CT2 in Atlanta
    • Stop#2: Drop off CT2 in New York
    • Finish: Drop off CT1 in Boston
[edit] Load Plan XML for Optimal

TBD

[edit] Non Optimal route

  • Track A:
    • Start: Pick up CT1 in Miami
    • Finish: Drop off CT1 in Boston
  • Track B:
    • Start: Pick up CT2 in Atlanta
    • Finish: Drop off CT2 in New York
[edit] Load Plan XML for Non Optimal

TBD

[edit] TMS use options

  • operator creates #Optimal route manually
    • discovering shipments to combine
    • discovering optimal route
    • discovering optimal cost carrier

[edit] Link to User Guide

Similar example - see Pic on page 153 in Descartes TMS User guide.

[edit] Business story

July 22

Shipper Mary with Jackel creates 1 new CT record (# 11111) shipping from her NJ warehouse, Gannet Warehouse at 58 Executive Drive in Edison, NJ. She only has 1 pallet ready and would like to get this off of her warehouse dock so her warehouse can continue with their monthly inventory stock report. Now at the same shipper Harry with Princeton Label creates 1 new CT record (# 11145) shipping from his NJ warehouse, Princeton Labels & Packaging Inc at 1226 Route 130 in Robbinsville, NJ. He has about 15 pallets that are ready to ship today and hopes that CEI Roanoke will approve this PO/SKU to ship.

...later that day...

Shipper Orlando with Pochet creates 1 new CT record (# 11200) shipping from his NJ warehouse, Vecco Holdings at 6801 West Side Avenue in North Bergen and he also has only 1 pallet that is ready to ship'

...even later that day...

At once, 2 separate Arden planners approve these 3 CT records (# 11111, 11145 & 11200) and now Jag operator Susan notices that her TDS dashboard has 3 approved shipments. So she logs into TMS and finds those same 3 records on her new shipment list. Its now 3:45 in the afternoon and as Susan reviews each of the shipments, she notices they are all shipping from NJ and arranges in TMS to build a load with the optimization process. After her load is built, she tenders the load to Jewels Transportation and awaits their replies.

...shortly before quitting time...

Jewels accepts the tender, confirms they'll arrange to collect all 3 shipments at 17 pallets total the next day. Now all 3 CT2 records are updated with the pickup truckers name, as well as the estimated pickup date. As well, all 3 shippers, including EA Dom receive an e-mail notification from cybertrax@jaguarfreight.com that their records were approved and Jewels Transportation will pickup.

Late afternoon July 23

Jewels collects all 3 shipments and updates their system. Trucker unloads these shipments at his warehouse and places the 1 shipment to the side for a different carrier to arrange the delivery and updates their system that all were collected and on hand. Once they update their system, that information is sent to TMS, then TMS sends the information to Jaguar and automatically updates the CT records with the actual pickup date.

...early evening

Delivery trucker, Lawrence Trucking goes in to pick up the 1 shipment for CEI Roanoke. He signs a confirmation receipt (which is like a POD) of what he is picking up and gives a copy to Jewels. They update their system that this 1 shipment was transferred to the delivery trucker accordingly and their system sends that information to TMS, then TMS sends the information back to Jaguar and automatically updates the CT record with the delivery truckers name, including the estimated & actual delivery dates. Now Jewels takes the signed confirmation receipt, writes the CT# reference on it (as the CT# must match the CT# that was created by shipper user) and faxes/e-mails the POD to Jaguar Freight.

...shortly after Lawrence leaves Jewels dock

Jewels warehouse manager is arranging for his truckers morning deliveries. He loads his driver with several different shipments delivering to the local NJ area which includes these 2 shipments that are delivering to CEI Holmdel. He updates his system that these 2 shipments will be delivering tomorrow Jul 24 and that information sends to TMS. Then TMS sends the information back to Jaguar and automatically updates the CT record with the delivery truckers name, including the estimated date.

the next morning July 24...

Jag operator Susan receives the Lawrence POD from Jewels and up loads the POD into the CT record. She also checks to see that Jewels has arranged for the 2 shipments to CEI Holmdel for delivery today.

...right before lunch

Jewels dispatcher hears from his local NJ driver who advises he just got a flat tire...He advises him that it's going to take some time before he can get it fixed and is unsure if he can arrange his last drop...His last drop or delivery is for CEI Holmdel. Now Jewels Dispatcher calls Jaguar to notify them of the same and Jaguar advises Debbie at CEI Holmdel that her delivery will be late

4:35 pm...

After some long hours of phone calls and e-mails, the Jewels driver was successful in fixing his flat, as well as delivering these 2 shipments to CEI Holmdel. He calls his dispatcher to advise this and he updates his system that these 2 shipments were delivered today Jul 24. That information is sent to TMS, then TMS sends that same information back to Jaguar and automatically updates the CT record with the actual delivery date.

..whenever the driver returned

Jewels takes the POD (or signed confirmation receipt), makes sure that the CT# is listed on the paperwork and faxes/e-mails the POD to Jaguar Freight.''

the following morning July 25

Jaguar operator received the POD document and uploads it into the CT record.'

[edit] Use Cases

[edit] Use Case 1.

[edit] Jaguar Discovers Approved CTs
[edit] Figure 1

Jaguar operator logs into CT2 internal application to find 3 new "Approved" CT records on their TDS dashboard.

File:Susan's TDS.JPG

[edit] Jaguar Operator uses TMS
[edit] Figure 2

Jaguar operator logs onto the TMS system, goes into the Main Menu, > Activity Summaries > Activity Details to find their are new shipments listed. (These are the same "Approved" CT records that are on their TDS dashboard on the internal app).

File:Activity Details Page n1.JPG

[edit] Figure 3

Jag operator clicks on the number of new shipments (3) to review for them to decide who they would like to arrange for the pickup.

File:TMS Shipment list 1.JPG

[edit] Figure 4

Jag operator looks at the first CT record # 11111.

File:TMS Shipment 1.JPG

[edit] Figure 5

Jaguar operator Susan begins the optimization Process from the new shipment list. She highlights all 3 new shipments, then she right clicks and chooses option Consolidate All. Now the build load page displays.

File:TMS Build Loads 1.JPG

[edit] Figure 6

Jaguar operator routes via TMS and uses the Interactive Load Editor to arrange the order of pickups and once done, chooses Validate so she can send a tender to the trucker.

File:Consolidation Build Load2.JPG

[edit] Figure 7

Jaguar operator tenders the load load to Jewels Trucking by right clicking on the load number. TMS transits this information to the pickup truckers system and Jag operator waits for their acceptance or rejection.

File:TMS Tender Available Loads.JPG


[edit] Various Use Cases

[edit] UC 101 Editing Shipment data on CT side after Shipment Import

see Shipment_Import#UC_101_Editing_Shipment_data_on_CT_side_after_Shipment_Import

[edit] UC 102 Editing Shipment data on TMS side after Shipment Import

Only some fields will be updated in CT DB through Load Plan.

Descartes can not make Shipment fields read only.

[edit] UC 103 One Commodity line with both loose and plts will translate into 2 line items on Descartes side

Line with loose will have Qty=0 and Weight = 0.01

[edit] UC 104a Re tendering before Trucker accepts

1. CT#xxx was made part of load LD#yyy 2. LD#yyy was tendered to Trucker ZZZ and pending acceptance 3. Jaguar want to change the Trucker

[edit] UC 104b Re tendering because Trucker rejects

[edit] UC 104c Re tendering after Trucker accepts

This case can't happen.

[edit] UC 200 Shipment Import for Approved with date

Does it work.

[edit] Questions

  • Will routed / pick up counter update correctly?
  • Will they generate any reports?
  • If CT is too large (>26?plts?) it will not be processed by TMS
Retrieved from "https://wiki.jaguarfreight.com/Use_Cases_for_EDI_to_TMS"
Personal tools