UG:Air Status USER GUIDE

From UG

(Difference between revisions)

Current revision as of 19:49, 28 December 2011

[edit] Intro

Descartes (Jaguar partner) is offering Automated Air Status Update Service

This service allows 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 Airfreight shipments.

It is our understanding that in order to send updates Descartes needs to receive only MAWB number.

[edit] Logic & Conditions for Status Updates to be sent & received

Airline must participate in air status messaging. The list of current, participating airlines can be found under the Admin Menu > Air Status/EUAN Admin See #FSR Airlines Tab.

All status messages being sent to the airlines and received from airlines are to be recorded on the Systems Log.

NOTE: If any of the following airports - departure, transshipment or destination - that's set in the CT record and/or it's master record does not exist to airline, the message we send will be ignored by airline and no updates will be received. As well, if the departure, transshipment or destination airports that's set in the CT record and/or it's master record does not match the airlines message we receive, the message will be ignored and the record will not be automatically updated.

[edit] Mandatory Fields

The following needs to be filled in order to send & receive automatic updates:

Airline Name
MAWB Number(all 11 digits)
Airport of Departure Name
Estimated Departure Date

NOTE: Once the above mandatory fields are set in the CT record and/or the Master record, a message will automatically be created (in the background) and sent to the airline requesting the status information according to the MAWB #. It does not require any manual transmission on operators part. Once the airline confirms the departure, a message will be received (in the background) and then the CT record and/or the Master record will update accordingly.

[edit] Optional Fields

The following fields are optional but if/when they are filled messages will be sent out and automatic updates will be received:

Airport of Transshipment name
Airport of Transshipment Estimated Departure Date

[edit] Air Status Admin

[edit] Air Status and EU Advance Notice are currently shared in the Admin section of CT

Both the EU Advance notice and the Air Status Updates are shared inside the admin menu because it is Descartes who provides these 2 services to JFS and both are related to airfreight. Note the second & third tabs are related directly to Air Status.

[edit] Parameter Tab

This is where we manage the messages that's being sent and received. It includes the time parameters that we use, for how often the system is to send the messages to the airline and how often the system is to check for new messages being received. As well it includes the server information that is used for passing these electronic messages.

[edit] FSR Airlines Tab

Here is where the current list of participating airlines can be found. The left panel contains the current list of airlines that participate and/or are in testing phase for automatic updates and the right panel contains the current list of airlines that are setup in CyberTrax for Air Status messaging.

[edit] FWB FHL Airlines Tab

This tab is not applicable and is not currently being used. Originally it was created for the airlines that do not participate in the air status and/or EUAN messaging, but would participate in other types of messaging. It was found that such a case does not exist and this tab will most likely be removed from this menu at a later date.

[edit] Logging of sent & received Air Status Messages

Currently all requests sent to the airline are being recorded under our CT Systems Log.

[edit] Systems Log

Once there, expand menu item 'Anywhere and select Air Status/EUAN. You also have search options which can be set by date and/or by the CT # inside of the text box "Component description contains:" Then select Show Log

[edit] Logging of FSR Message

FSR stands for Flight Status Request. Our system send a request for this information to the airline starting 24 hours prior to the set estimated departure and will continue to send a request every hour until the actual departure is received.

[edit] Logging of FSA Message

FSA stands for Flight Status Answer. Once the FSR is sent for an MAWB #, our system awaits the airline's replies/confirmation of the departure date and/or arrival date and upon receipt, these date fields will be recorded here and automatically update the CT & its Master record accordingly.

[edit] History

[edit] Ver 1

See above

[edit] See Also

Link to CT2 User Guide: Category:Support
Link to spec: Air Status EDI

@@ Line 9: / Line 9: @@
 It is our understanding that in order to send updates Descartes needs to receive only MAWB number.
-== Business Processes ==
+== Logic & Conditions for Status Updates to be sent & received ==
-=== For 1 CT record booked on a direct flight ===
+* Airline must participate in air status messaging.  The list of current, participating airlines can be found under the Admin Menu > Air Status/EUAN Admin  See [[#FSR Airlines Tab]].
-For shipments that are booked on a direct flight the incoming messages should update the following fields in CT.
+* All status messages being sent to the airlines and received from airlines are to be recorded on the Systems Log.
-* Airport Of Departure Actual Date -
+'''NOTE:''' If any of the following airports - departure, transshipment or destination - that's set in the CT record and/or it's master record does not exist to airline, the message we send will be ignored by airline and no updates will be received. As well, if the departure, transshipment or destination airports that's set in the CT record and/or it's master record does not match the airlines message we receive, the message will be ignored and the record will not be automatically updated.
-          o shipment should confirm the airport of departure is correct, by comparing the destination
-            airport listed on the incoming message to the CT#Airport Of Departure
-* Airport Of Destination Actual Date-
+=== Mandatory Fields ===
-          o shipment should confirm the airport of departure is correct, by comparing the destination
-            airport listed on the incoming message to the CT#Airport Of Destination
-=== Transshipment airports ===
+The following needs to be filled in order to send & receive automatic updates:
-It is possible to have more than one transhipment airport.
+* Airline Name
+* MAWB Number(all 11 digits)
+* Airport of Departure Name
+* Estimated Departure Date
-We assume that Descartes can send meaningful updates to accommodate that case.
+'''NOTE:''' Once the above mandatory fields are set in the CT record and/or the Master record, a message will automatically be created (in the background) and sent to the airline requesting the status information according to the MAWB #.  It does not require any manual transmission on operators part.  Once the airline confirms the departure, a message will be received (in the background) and then the CT record and/or the Master record will update accordingly.
-In the event of more than one trans shipment airport, the system should only update the CT#Trans Shipment port listed in the CT record. Once the incoming message received showing the indicated or matching trans ship port arrival, the the CT#Trans Shipment Actual Date should be updated.
+=== Optional Fields ===
-Any departure or destination airports indicated in incoming messages that do not exist or match the CT record should be ignored. This will be addressed in Phase 2.
+The following fields are optional but if/when they are filled messages will be sent out and automatic updates will be received:
-=== Split case ===
+* Airport of Transshipment name
+* Airport of Transshipment Estimated Departure Date
-In this case airline might call and say that X plts/pcs/etc will be placed on Flight F1.
+== Air Status Admin ==
-Later airline might call and say that Y plts/pcs/etc will be placed on Flight F2.
+=== Air Status and EU Advance Notice are currently shared in the Admin section of CT ===
-Later airline might call and say that remaining plts/pcs/etc will be placed on Flight F3.
+[[File:Admin Air Status EUAN Admin.JPG]]
-It could be split 2,3,4, ... times. - Keeping a record of this updates will be TBD for Phase 2
+Both the EU Advance notice and the Air Status Updates are shared inside the admin menu because it is Descartes who provides these 2 services to JFS and both are related to airfreight.  '''Note''' the second & third tabs are related directly to Air Status.
+=== Parameter Tab ===
-We assume that Descartes can send meaningful updates to accommodate that case. CT2 should be re-designed to support that.
+This is where we manage the messages that's being sent and received.  It includes the time parameters that we use, for how often the system is to send the messages to the airline and how often the system is to check for new messages being received.  As well it includes the server information that is used for passing these electronic messages.
-The CT should update the CT#Airport Of Departure Actual Date when the first piece has departed and update when the last piece departs and the CT#Airport Of Destination Actual Date when the first piece arrives and updated when the last piece updates.
+[[File:Parameters Tab.JPG]]
-A comment should be posted showing the following updates as a notification on the above.
+=== FSR Airlines Tab ===
-*
+Here is where the current list of participating airlines can be found.  The left panel contains the current list of airlines that participate and/or are in testing phase for automatic updates and the right panel contains the current list of airlines that are setup in CyberTrax for Air Status messaging.
-          o SPLIT SHIPMENT - First part has departed
-          o SPLIT SHIPMENT - Last part has departed
-          o SPLIT SHIPMENT - First part has arrived
-          o SPLIT SHIPMENT - Last part has arrived
-The system will need to keep a count after the first departure, until the CT#Grand Total: Loose Pkgs or CT#Grand Total: Pkgs On Plts total matches, to accurately update the first and last parts. All other departures or arrivals should be ignored. This will be addressed in Phase 2
+[[File:FSR Airlines Tab.JPG]]
-=== Delays ===
+=== FWB FHL Airlines Tab ===
-In the event that a shipment is removed from the original flight or the original flight is delayed.
+<font color="red" size="3"> This tab is not applicable and is not currently being used. Originally it was created for the airlines that do not participate in the air status and/or EUAN messaging, but would participate in other types of messaging.  It was found that such a case does not exist and this tab will most likely be removed from this menu at a later date. </font>
-Airport Of Departure Estimated Date field should be updated to reflect the corrected information.
+[[File:Air Status FWB FHL Airlines.JPG]]
-Airport Of Destination Estimated Date field should be updated to reflect the corrected information.
+== Logging of sent & received Air Status Messages ==
-=== Phase Two Business Requirements For UC2 & 3 ===
+Currently all requests sent to the airline are being recorded under our CT Systems Log.
-Additional requirements TBD
+=== Systems Log ===
-=== Transshipment airports ===
+Once there, expand menu item '''Anywhere'' and select Air Status/EUAN.  You also have search options which can be set by date and/or by the CT # inside of the text box "Component description contains:"  Then select Show Log
-It is possible to have more than one transhipment airport.
+[[File:Log with comments how to.JPG]]
-We assume that Descartes can send meaningful updates to accommodate that case.
+=== Logging of FSR Message ===
-CT2 should be re-designed to support that.
+FSR stands for '''F'''light '''S'''tatus '''R'''equest.  Our system send a request for this information to the airline starting 24 hours prior to the set estimated departure and will continue to send a request every hour until the actual departure is received.
-=== Split case ===
+[[File:FSR.JPG]]
-In this case airline might call and say that X plts/pcs/etc will be placed on Flight F1.
+=== Logging of FSA Message ===
-Later airline might call and say that Y plts/pcs/etc will be placed on Flight F2.
+FSA stands for '''F'''light '''S'''tatus '''A'''nswer.  Once the FSR is sent for an MAWB #, our system awaits the airline's replies/confirmation of the departure date and/or arrival date and upon receipt, these date fields will be recorded here and automatically update the CT & its Master record accordingly.
-Later airline might call and say that remaining plts/pcs/etc will be placed on Flight F3.
+[[File:FSA.JPG]]
-It could be split 2,3,4, ... times.
+== History ==
-We assume that Descartes can send meaningful updates to accommodate that case. CT2 should be re-designed to support that.
+=== Ver 1 ===
+See above
-== Hard coded or Hidden conditions ==
+== See Also ==
+* '''Link to CT2 User Guide:''' [[:Category:Support]]
+* Link to spec: [[Air Status EDI]]
-== Filters ==