2782 rfd

From UG

(Difference between revisions)
Jump to: navigation, search
(Created page with 'Category:RFD')
(→Current List of Participating & Non Participating Airlines)
 
(51 intermediate revisions not shown)
Line 1: Line 1:
[[Category:RFD]]
[[Category:RFD]]
 +
 +
== 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  [http://ct.jaguarfreight.com/mantis/view.php?id=2648 2648]
 +
:*Set up in CargoImp format (Jaguar sends message to Descartes in XML format, Descartes will convert to cargoImp)
 +
:*See CT2 field mapping [http://ct.jaguarfreight.com/mantis/view.php?id=2787 here]
 +
 +
== 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.
 +
 +
* Provide operators with the ability to transmit the FWB message, when they have booked the shipment directly with the airlines.
 +
:* When an FWB message is transmitted to the airline, this should trigger automatically 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.
 +
:* Show pop-up error - unsuccessful transmission such as MAWB is not fully filled in, etc
 +
 +
* System log all messages sent and received.
 +
* The log of transmission should be visible to operators as well, so they can confirm in a quick check or glance if they have already transmitted the information.
 +
 +
== Solution ==
 +
 +
=== FSR functionality ===
 +
==== Sending data to Descartes/Airline ====
 +
* 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.
 +
:** Logic: Est date - X date is passed today date, send FSR message immediately
 +
:** Stop sending FSR when actual date(s) is set.
 +
 +
==== Receiving date from Descartes/Airline ====
 +
* Descartes would forward back messages from the airline with certain updates. This specific info should update CT record.
 +
* Type of update: '''DEP''' (Actual departure), ''' RCF''' or '''ARR''' (Actual arrival to trans-shipment airport and destination airport).
 +
* NOTE: once the expected dates are updated, system stops sending that particular FSR
 +
 +
=== FWB functionality ===
 +
* Provide a transmit FWB button
 +
:* Master level on Master detail Tab next to the "Master Bill of Lading#:" field. See [[#Figure 1. Transmit button on Master level ]]
 +
:** Condition: All required fields MUST be there, otherwise it is failed and pop-up error showing for missing information.
 +
:* Transmit FWB via Master level and action will be taken
 +
 +
=== Admin functionality ===
 +
* Turn on/off FSR per airline
 +
:* FSR message frequency in X hour(s)
 +
:* Parameters for sending FSR
 +
:** Number of hours prior to Estimated dates to start sending FSR in advance
 +
* Turn on/off FWB/FHL per airline
 +
:* FWB/FHL button for air status on the Master level
 +
:* This is needed for the air status for a particular airlines that will response from FWB/FHL message instead of FSR message
 +
* Provide facility to manage ftp connection
 +
:* FTP server address
 +
:* Turning on/off
 +
:** FSR
 +
:*** provide ability to enable/disable for certain airlines if required.
 +
:** FWB
 +
:*** provide ability to enable/disable for certain airlines if required.
 +
:* This should not interfere with TMS functionality (Specifically for this project- Air Status update and EUAN)
 +
 +
=== System logs ===
 +
 +
* Ideally log all events:
 +
:* Time date stamp for operator actions, transmit 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.
 +
:* All the event MUST be recorded under update log as well
 +
* Additional transmission log event:
 +
:* Display transmission log event to operator to quickly check whether they have already transmitted the information.
 +
 +
 +
=== Addition Info ===
 +
* XML schema requires to add a new field in our database to indicate a recipient (it is an airline code). For example HSQFMAA is for American Airline. This is an IATA code for each airline. Descartes sent us a list of the IATA codes to update data on our database.
 +
* This field can be added on the Airline table.
 +
* System must understand message nodes for both uppercase and lowercase for XML schema
 +
 +
== Current List of Participating & Non Participating Airlines ==
 +
 +
* See excel attached in mantis [http://ct.jaguarfreight.com/mantis/view.php?id=3291 3291]
 +
 +
== Figures ==
 +
 +
=== Figure 1. Transmit button on Master level ===
 +
[[File:MasterAWB.JPG]]

Current revision as of 22:03, 6 December 2011


Contents

[edit] 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 (Jaguar sends message to Descartes in XML format, Descartes will convert to cargoImp)
  • See CT2 field mapping here

[edit] 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.


[edit] 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.
  • Provide operators with the ability to transmit the FWB message, when they have booked the shipment directly with the airlines.
  • When an FWB message is transmitted to the airline, this should trigger automatically 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.
  • Show pop-up error - unsuccessful transmission such as MAWB is not fully filled in, etc
  • System log all messages sent and received.
  • The log of transmission should be visible to operators as well, so they can confirm in a quick check or glance if they have already transmitted the information.

[edit] Solution

[edit] FSR functionality

[edit] Sending data to Descartes/Airline

  • 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.
    • Logic: Est date - X date is passed today date, send FSR message immediately
    • Stop sending FSR when actual date(s) is set.

[edit] Receiving date from Descartes/Airline

  • Descartes would forward back messages from the airline with certain updates. This specific info should update CT record.
  • Type of update: DEP (Actual departure), RCF or ARR (Actual arrival to trans-shipment airport and destination airport).
  • NOTE: once the expected dates are updated, system stops sending that particular FSR

[edit] FWB functionality

  • Provide a transmit FWB button
  • Master level on Master detail Tab next to the "Master Bill of Lading#:" field. See #Figure 1. Transmit button on Master level
    • Condition: All required fields MUST be there, otherwise it is failed and pop-up error showing for missing information.
  • Transmit FWB via Master level and action will be taken

[edit] Admin functionality

  • Turn on/off FSR per airline
  • FSR message frequency in X hour(s)
  • Parameters for sending FSR
    • Number of hours prior to Estimated dates to start sending FSR in advance
  • Turn on/off FWB/FHL per airline
  • FWB/FHL button for air status on the Master level
  • This is needed for the air status for a particular airlines that will response from FWB/FHL message instead of FSR message
  • Provide facility to manage ftp connection
  • FTP server address
  • Turning on/off
    • FSR
      • provide ability to enable/disable for certain airlines if required.
    • FWB
      • provide ability to enable/disable for certain airlines if required.
  • This should not interfere with TMS functionality (Specifically for this project- Air Status update and EUAN)

[edit] System logs

  • Ideally log all events:
  • Time date stamp for operator actions, transmit 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.
  • All the event MUST be recorded under update log as well
  • Additional transmission log event:
  • Display transmission log event to operator to quickly check whether they have already transmitted the information.


[edit] Addition Info

  • XML schema requires to add a new field in our database to indicate a recipient (it is an airline code). For example HSQFMAA is for American Airline. This is an IATA code for each airline. Descartes sent us a list of the IATA codes to update data on our database.
  • This field can be added on the Airline table.
  • System must understand message nodes for both uppercase and lowercase for XML schema

[edit] Current List of Participating & Non Participating Airlines

  • See excel attached in mantis 3291

[edit] Figures

[edit] Figure 1. Transmit button on Master level

File:MasterAWB.JPG

Retrieved from "https://wiki.jaguarfreight.com/2782_rfd"
Personal tools