2782 rfd

From UG

Contents 1 Glossary 2 Information 3 Business Requirement 3.1 Additional Use Cases 4 Admin 5 Solution 5.1 FSR functionality 5.2 FWB functionality 5.3 Admin functionality 5.4 System logs

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

• See detail on CIMP-29thEdition2009_FWB.PDF from 2648
• 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 Requirement

An FSR message should be transmitted under the following conditions:

• 11 digit of MAWB field is set AND Airline field is set AND the Estimated departure is set.

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.

Solution

FSR functionality

• System should start/stop sending FSR messages automatically once certain condition are met

• parameters are defined in Admin
• For every date on this list: Departure, Trans-shipment, and Arrival.
  • Start sending FSR X day(s) prior to Estimated date value. NOTE: in some cases system would have to start sending immediately after this date is set, for example: today is march 10 and oper set est date today and set it to march 11 and X is 2 days
  • Stop sending FSR when actual date(s) is set.

• Descartes would forward back messages from the airline with certain updates. This specific info should update CT record.
• Type of update: DEP (Actual departure), ARR (Actual arrival), RCF or ARR (Actual arrival to trans-shipment airport.

FWB functionality

• Provide a transmit FWB button

• CT level on Exp Tab next to the "Master Bill of Lading#:" field.
  • Condition: All required fields MUST be there, otherwise it is failed and pop-up error showing for missing information.
• Master level on Master detail Tab next to the "Master Bill of Lading#:" field.
  • Condition: All required fields MUST be there, otherwise it is failed and pop-up error showing for missing information.
• Operator can have a choice whether they can transmit FWB from CT or Master level

Admin functionality

• Turn on/off FSR per airline

• FSR messsage frequency in X hour(s)
• Parameters for sending FSR
  • Number of hours prior to Estimated dates to start sending FSR in advance

• Provide facility to manage ftp connection

• FTP server address
• Turning on/off
  • FSR
  • FWB

System logs

• Ideally log all events:

• Time date stamp for operator actions, FWB button, etc
• ALl system actions, message sent and received and etc
• All ftp error/fail messages
• All update such as Actual arrival received.
• All xmls received and sent ??? System can keep this log for x days define in admin.
• FNA for operator of last change