Air Status EDI
From UG
(Difference between revisions)
(→Requirements) |
(→Requirements) |
||
| Line 4: | Line 4: | ||
0002422: [Air Status EDI] ............. <proj parent> | 0002422: [Air Status EDI] ............. <proj parent> | ||
| - | == Requirements == | + | == Business Requirements == |
=== Intro === | === Intro === | ||
| + | |||
| + | Project: Automated air status update service (EDI with Descartes) | ||
| + | |||
| + | This will allow airfreight shipments booked directly by Jaguar with the airlines, to be fed automatic status updates (departure and arrival dates), removing our need to manually check and then update the status of Airfreigt shipments. | ||
| + | |||
| + | ==== Technical part ==== | ||
| + | |||
| + | CT2 and Descartes system (GLN) will exchange XML messages. | ||
| + | |||
| + | In a nutshell: | ||
| + | * CT2 sends MAWB (same as FWB) to Descartes(GLN) network/server | ||
| + | * GLN forwards to Airline nework | ||
| + | * when update becomes available info is passed back to CT2 through Descartes | ||
| + | |||
=== One CT one direct flight Use Case === | === One CT one direct flight Use Case === | ||
| Line 13: | Line 27: | ||
=== Split Use Case === | === Split Use Case === | ||
| + | |||
| + | == Technical Requirements and Design == | ||
== History == | == History == | ||
Revision as of 18:13, 27 October 2010
Contents |
Parent mantis
0002422: [Air Status EDI] ............. <proj parent>
Business Requirements
Intro
Project: Automated air status update service (EDI with Descartes)
This will allow airfreight shipments booked directly by Jaguar with the airlines, to be fed automatic status updates (departure and arrival dates), removing our need to manually check and then update the status of Airfreigt shipments.
Technical part
CT2 and Descartes system (GLN) will exchange XML messages.
In a nutshell:
- CT2 sends MAWB (same as FWB) to Descartes(GLN) network/server
- GLN forwards to Airline nework
- when update becomes available info is passed back to CT2 through Descartes
