2782 rfsa

From UG

(Difference between revisions)
Jump to: navigation, search
(→Business Requirements)
 
(12 intermediate revisions not shown)
Line 1: Line 1:
-
[[Category:RFD]]
+
[[Category:RFSA]]
 +
<div style="background-color:lightSteelBlue">
== Parent mantis ==
== Parent mantis ==
Line 16: Line 17:
*'''FSA-message''' - Freight Status Answer message - Incoming message from Descartes to CT2
*'''FSA-message''' - Freight Status Answer message - Incoming message from Descartes to CT2
-
**Set up TBD
+
**Set up in XML format  
-
 
+
-
*'''FHL-message''' - Forwards House bill details - Out going message to Descartes GLN
+
-
 
+
-
**Set up in CargoImp format  
+
*'''FWB-message''' - Forwards way bill or MAWB details -  Out going message to Descartes GLN
*'''FWB-message''' - Forwards way bill or MAWB details -  Out going message to Descartes GLN
Line 26: Line 23:
**Set Up in CargoImp format
**Set Up in CargoImp format
 +
== Information ==
-
== Business Requirements ==
+
Descartes is offering a service to automate air status updates.
-
Descartes is offering ''Automated Air Status Update Service''
+
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.
-
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.
+
Implementing Automatic updates would save the operators a lot of time. Currently the operators call the airlines and manually enter these updates.
-
 
+
-
It is our understanding that in order to send updates Descartes needs to receive only MAWB number.
+
-
 
+
-
*The message should not transmit to the airline until the full MAWB number is entered**
+
-
 
+
-
*Current conditions have been hard coded.  We need an admin section to be able to edit the following conditions for air status updates.
+
-
 
+
-
**Specified Airlines
+
-
**Specified Jaguar Office
+
-
**Specified Origin Country - Gen tab, 11. Origin country;
+
-
**Specified Destination Country
+
-
**Specified / 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)
+
-
 
+
-
 
+
-
=== One CT one direct flight ===
+
-
 
+
-
For shipments that are complete and are booked on one flight or direct flight the incoming messages should update the following fields in CT. 
+
-
 
+
-
====Fields to be updated:====
+
-
 
+
-
*[[CT#Airport Of Departure Actual Date]] -
+
-
**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]]
+
-
*[[CT#Airport Of Destination Actual Date]]-
+
-
**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 ===
+
-
 
+
-
It is possible to have more than one transhipment airport.
+
-
 
+
-
We assume that Descartes can send meaningful updates to accommodate that case.
+
-
 
+
-
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 [[CT#Trans Shipment Actual Date]] should be updated.
+
-
 
+
-
Any departure or destination airports indicated in incoming messages that do not exist or match the CT record should be ignored. 
+
-
 
+
-
 
+
-
=== Split case ===
+
 +
== Business Requirements ==
-
In this case airline might update saying that X plts/pcs/etc will be placed on Flight F1.
+
An FSR message should be transmitted under the following conditions.
-
Later airline might update saying that Y plts/pcs/etc will be placed on Flight F2.
+
Only if the full 11 digit airline is set and the airline is set and the estimated departure is set.
-
Later airline might update saying that remaining plts/pcs/etc will be placed on Flight F3.
+
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. 
-
It could be split 2,3,4, ... times. - Keeping a record of this updates will be TBD for Phase 2
+
*  Status code for Departure in the FSU or FSA is DEP
-
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.
+
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.
-
A comment should be posted showing the following updates as a notification on the above.
+
*  Status code for arrival of a trans-shipment airport RCF (received from flight) or ARR.
-
** '''''SPLIT SHIPMENT''''' - First part has departed
+
-
** '''''SPLIT SHIPMENT''''' - Last part has departed
+
-
** '''''SPLIT SHIPMENT''''' - First part has arrived
+
-
** '''''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 not update the record.
+
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.  
-
=== Delays ===
+
*  Status code for arrival of the destination airport is ARR.
-
In the event that a shipment is removed from the original flight or the original flight is delayed.
 
-
''Airport Of Departure Estimated Date'' field should be updated to reflect the corrected information.
 
-
''Airport Of Destination Estimated Date'' field should be updated to reflect the corrected information.
+
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.
-
=== When to send messages ===
+
*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.
-
CT2 system should send [[Ct#MAWB]] through EDI as soon as it gets assigned by operator.
+
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.
-
**It seems that this is set up to send at the time the operator clicks save.  I think this should be changed because we do not want to send an FSU message until the record is complete.  UAT has shown that the mawb is being transmitted to the airline once the airline is assigned and save is hit.  So the operator does not have to enter even the remaining digits of the mawb.
+
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.
+
We should also have a place to be able to view any rejected messages or messages that do not match records.
-
=== Use Case Operator changed MAWB ===
+
=== Additional Use Cases ===
-
This is addressed in a separate http://ct.jaguarfreight.com/wiki/2555_rfsa
+
Reusing a MAWB number - This is addressed in a separate http://ct.jaguarfreight.com/wiki/2555_rfsa
-
== UAT Plan ==
+
Split shipments are still being researched and will be defined in the future.
-
=== Use Case 1 User enters MAWB in CT profile ===
+
==Admin==
-
* 1) User enters MAWB in CT profile (Exp tab)
+
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)
-
* 2) click Save, system should produce co pop-up
+
-
Note:
+
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.
-
-----
+
</div>
-
This would work only for specific set or airlines/origin (hardcoded for now).
+

Current revision as of 21:41, 24 February 2011

Contents

[edit] Parent mantis

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

[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
    • Set Up in CargoImp format

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

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

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

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