2782 rfsa

From UG

Revision as of 16:59, 22 February 2011 (edit) Alex (Talk | contribs) (→Business Requirements) ← Older edit

Revision as of 16:24, 24 February 2011 (edit) (undo) Alex (Talk | contribs) m (moved AIR STATUS UPDATE to 2782 rfsa) Newer edit →

---

Revision as of 16:24, 24 February 2011

Contents 1 Parent mantis 2 Glossary 3 Business Requirements 3.1 One CT one direct flight 3.1.1 Fields to be updated: 3.2 Transshipment airports 3.3 Split case 3.4 Delays 3.5 When to send messages 3.6 Use Case Operator changed MAWB 4 UAT Plan 4.1 Use Case 1 User enters MAWB in CT profile

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 TBD

• 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

• • Set Up in CargoImp format

Business Requirements

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

• 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

In this case airline might update saying that X plts/pcs/etc will be placed on Flight F1.

Later airline might update saying that Y plts/pcs/etc will be placed on Flight F2.

Later airline might update saying that remaining plts/pcs/etc will be placed on Flight F3.

It could be split 2,3,4, ... times. - Keeping a record of this updates will be TBD for Phase 2

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.

A comment should be posted showing the following updates as a notification on the above.

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

Delays

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.

When to send messages

CT2 system should send Ct#MAWB through EDI as soon as it gets assigned by operator.

• • 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 also have a place to be able to view any rejected messages or messages that do not match records.

Use Case Operator changed MAWB

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

UAT Plan

Use Case 1 User enters MAWB in CT profile

• 1) User enters MAWB in CT profile (Exp tab)
• 2) click Save, system should produce co pop-up

Note:
-----
This would work only for specific set or airlines/origin (hardcoded for now).