2782 rfsa

Parent mantis

0002422: [Air Status EDI] ............. <proj parent>

Glossary

• FSU-message - Freight Status Update message - Incoming message from Descartes to CT2

• • Set up in XML format

• FSR-message - Freight Status Request message - Outgoing message to Descartes GLN

• • Set up in XML format

• FSA-message - Freight Status Answer message - Incoming message from Descartes to CT2

• • Set up in XML format

• FWB-message - Forwards way bill or MAWB details - Out going message to Descartes GLN

• • Set Up in CargoImp format

Information

Descartes is offering a service to automate air status updates.

In order to receive these updates for shipments that we do not book directly with the airline (which is the majority of shipments), we need to send a FSR message to Descartes and Descartes will pass this information on to the airlines. In response to the FSR message the airline will send back and FSU or FSA to Descartes, which Descartes will push through to our system. These messages should update the Airport Of Departure Actual Date, Trans Shipment Actual Date (if applicable) and Airport Of Destination Actual Date.

Implementing Automatic updates would save the operators a lot of time. Currently the operators call the airlines and manually enter these updates.

Business Requirements

An FSR message should be transmitted under the following conditions.

Only if the full 11 digit airline is set and the airline is set and the estimated departure is set.

The FSR should start sending 1 day prior to departure or when departure date is set to the current date and plus 24 hours. The FSR should continue to transmit every X hours until the actual airport of departure date has been confirmed and updated.

• Status code for Departure in the FSU or FSA is DEP

The FSR should begin to start to transmit again 24 hours prior to the estimated arrival of the trans-shipment airport if applicable and continue to send every X hours until the actual arrival of the trans-shipment airport has been updated. If no trans-shipment airport is entered, this step should be skipped.

• Status code for arrival of a trans-shipment airport RCF (received from flight) or ARR.

The FSR should again begin to start to send 24 hours prior to estimated arrival of the destination airport and continue to send every X hours until the actual arrival of the destination airport has been confirmed and update.

• Status code for arrival of the destination airport is ARR.

Current conditions have been hard coded and we have been advised is no longer required.
*Specified Airlines
*Specified Origin Country - Gen tab, 11. Origin country; 
We will need an admin section which will be defined

We should also provide operators with the ability to transmit the FWB message, when they have booked the shipment directly with the airlines.

• The system will have no way of validating if the shipment was a direct booking or not, so the giving the operators the ability to transmit this on there own is current suggestion.

When an FWB message is transmitted to the airline, this should trigger automatic updates without the use of FSR's. This is not a guaranteed rule by every airline, so the FSR's should continue to be sent as defined above.

We should have a log of all messages sent and received.

We should also have a place to be able to view any rejected messages or messages that do not match records.

Additional Use Cases

Reusing a MAWB number - This is addressed in a separate http://ct.jaguarfreight.com/wiki/2555_rfsa

Split shipments are still being researched and will be defined in the future.

Admin

We will need a specified or separate message details sections (same as we have in admin > client application admin > TMS tab, but it should not interfere with this tab or be combined with this tab)

We also, would like to be able to stop transmission of the FSR's to certain airlines if required, so we should have all the airlines listed and a check box to disable certain airlines.