e-awb SOP e-awb Standard Operating Procedures at Riyadh - Saudi Arabia

Transcription

1 e-awb SOP e-awb Standard Operating Procedures at Riyadh - Saudi Arabia

2 Revision Tracking Version Date Updated By Changes Made th Jun 2016 IATA created the template 0.2 IATA and SV 0.3 IATA and SV 0.4 IATA and SV nd Jun 2016 IATA and SV eawb SOP Riyadh v0.1 Page 2

3 Introduction This e-awb SOP document contains the operational steps that stakeholders of the air cargo supply chain can follow when shipping air cargo in compliance with the e-awb functional specifications at the e-airports. These procedures are not location specific. In addition to following these generic procedures, stakeholders will also have to comply with any rule that may have been defined for the specific origin and destination locations from and to which they do e-awb. It is important to note that stakeholders may feel that they need to adjust their procedures not only based on specific location rules, but also based on their internal procedures and systems or to comply with any local practice or agreement they may have with their partners, suppliers and customers. eawb SOP Riyadh v0.1 Page 3

4 Table of Contents SECTION 1: EXPORT CARRIER SELF HANDLED... 5 SECTION 1.1 PRE-REQUISITES... 5 SECTION 1.2 OPERATIONS PROCESS STEPS... 6 SECTION 1.3 EXCEPTION MANAGEMENT... 9 SECTION 2: EXPORT CARRIER USING GROUND HANDLING AGENT...11 SECTION 2.1 PRE-REQUISITES...11 SECTION 2.2 OPERATIONS PROCESS STEPS...12 SECTION 2.3 EXCEPTION MANAGEMENT...16 SECTION 3: IMPORT CARRIER SELF HANDLED...18 SECTION 3.1 PRE-REQUISITES...18 SECTION 3.2 OPERATIONS PROCESS STEPS...18 SECTION 3.3 EXCEPTION MANAGEMENT...19 SECTION 4: IMPORT CARRIER USING GROUND HANDLING AGENT...20 SECTION 4.1 PRE-REQUISITES...20 SECTION 4.2 OPERATIONS PROCESS STEPS...20 SECTION 4.3 EXCEPTION MANAGEMENT...21 APPENDIX: GLOSSARY OF TERMS...22 eawb SOP Riyadh v0.1 Page 4

5 SECTION 1: EXPORT CARRIER SELF HANDLED This section describes the e-awb operational procedures for export shipments, when is self-handled at the airport. Section 1.1 Pre-requisites Actor Pre-requisites Task Signed the IATA Multilateral e-awb Agreement, including all branches tendering cargo at the airport. Commits to tender e-awb shipments for all destinations. Recommends to deliver cargo Ready for Carriage (in accordance with IATA Resolution 833, including appropriate labelling and packaging). Agrees to receive electronic Cargo Receipt as delivery receipt (in case of delivery by third party without access to electronic information, a paper Cargo Receipt or Warehouse Receipt can be requested). Capable of transmitting e-awb data to, by means of EDI messages, or via a web portal. When using EDI messages to transmit AWB data to, will use Cargo-IMP FWB version 16 or higher (or Cargo-XML equivalent). Capable of receiving e-awb status updates from, by means of EDI messages, or via a web portal. Capable of sending House manifest data to, by using EDI message or via a web portal. When using EDI messages for receiving Status updates, is able to receive FSU messages, particularly FSU-FOH and FSU-RCS messages (or Cargo-XML equivalent). Capable of archiving the EDI messages for required duration. Joined the IATA Multilateral e-awb Agreement and listed the Airport under the Agreement. Activated the IATA Multilateral e-awb Agreement with (including all its branches that tender cargo at the Airport). Capable of receiving e-awb data from by means of EDI messages or via a web portal, and also capable of processing and storing it electronically. When using EDI messages for receiving e-awb data, is able to receive Cargo-IMP FWB version 16 or higher (or Cargo-XML equivalent). Capable of sending e-awb Status updates, by using EDI message or via a web portal. eawb SOP Riyadh v0.1 Page 5

6 All parties All parties When using EDI messages for providing Status updates, is able to send FSU messages, particularly FSU-FOH and FSU-RCS messages (or Cargo-XML equivalent). Capable of receiving House manifest data from, by using EDI message or via a web portal. Capable of archiving the EDI messages for required duration. Commits to implementing the Single Process 1, enabling to tender all shipments without paper AWB. Commits to providing proper instructions/training to all concerned staff. Updated internal processes to no longer require paper AWB copies for Accounting activities with regards to e-awb shipments. Ensure that for secured cargo the transmission is compliant with the IATA e- Consignment Security Declaration specifications. In case of changes to the AWB data after the transmission of the initial FWB (or XFWB), the same can be updated by the freight forwarder with a subsequent FWB (or XFWB) until the shipment reaches RCS status. Updates required after the RCS has been sent will have to be addressed using a Charges Correction Advice (CCA). All receiving parties should be able to receive and process subsequent FWB (or XFWB) as per IATA Recommendation. Section 1.2 Operations process steps Day-to-day Operations Step Actor Task 1. Books the e-awb shipment with. 2. Sends the FWB (or XFWB) to the, at least (30 ) minutes before delivery of the goods. Alternatively, the e-awb data can be submitted to via web portal. Notes: 1. For shipments without accompanying document pouch and tendered as e- freight, shall insert Special Handling code EAW in the FWB (or XFWB) message sent to, or in the e-awb data submitted via web portal. 2. For secured cargo the transmission must be compliant with the IATA e- Consignment Security Declaration specifications Processes the e-awb data message received from the, and: 1 Guidelines for Single Process: eawb SOP Riyadh v0.1 Page 6

7 a) If no errors are found, sends FMA (or XFMA) to acknowledging receipt of the e-awb data message. Alternatively, can send the acknowledgement via web portal. or b) If errors are found, sends FNA (or XFNM) to notifying about the errors. Alternatively, can send the error notification via web portal. Note: Upon receiving error notification, shall re-send the corrected e-awb data to. 4. Inserts Special Handling code ECC (if e-awb route) or ECP (if paper AWB needs to be printed from the data), taking into account applicable International Convention, regulatory requirements and network constraints. Note: Printing of AWB (multipage colour coded) to cover ECP shipment is to be done by the in case of single process carriers. 5. Tenders the goods to s cargo acceptance facilities, ready for carriage (in accordance with IATA Resolution 833, including appropriate labelling and packaging) with the following: a) In case there is an accompanying document pouch, ensure it is properly labelled according to IATA Recommended Practice 1600u. b) Any applicable supporting documents (Example: Shippers Declaration for Dangerous Goods). 6. Receives the goods and matches the physical goods with the electronic shipment data in the system (Paper AWB copy is not requested and not used). Note: If any discrepancy is found between physical goods and the electronic shipment data, it shall be communicated to the delivery person immediately, and the shipment shall be put on hold until such time the correct FWB/XFWB has been resent by the freight forwarder. 7. After all the conditions to take delivery of the goods are positive: a) assigns it to a location in the system b) Provides a Cargo Receipt/ Warehouse Receipt to the person delivering the cargo. Note: The Cargo Receipt/Warehouse Receipt can also be provided using electronic means (for example, via ) c) Sends FSU-FOH (or XFSU-FOH) message to, or alternately sends on Hand confirmation to via web portal. Note: The FSU-FOH (or XFSU-FOH) message or freight on hand confirmation should be sent even if the shipment could be declared ready for carriage right away. 8. Performs checks necessary to confirm shipment as ready for carriage. eawb SOP Riyadh v0.1 Page 7

8 Notes: a) In case of secured cargo, checks the validity of the Security Declaration in the electronic data and certifies this action digitally. b) In case of unsecured cargo, performs the Security Check according to current country regulations and, certifies this action digitally. c) All security related activities to be compliant with the IATA e-consignment Security Declaration specifications. 9. After all the required checks are completed with positive results: a) Confirms the shipment as Ready for Carriage in the system. b) Sends FSU-RCS (or XFSU-RCS) message to, or alternatively sends the ready for carriage confirmation to via web portal. c) Provides the Cargo Receipt (in accordance with IATA Resolution 600g) to by electronic means (example: downloadable PDF posted on website or web portal). 10. Manifests the shipment according to verified electronic shipment data in their system. 11. Prepares the physical shipment for transportation: a) Loads the shipment onto a ULD (pallet, container, etc). b) When present, includes the shipment document pouch into the flight pouch c) Ensures paper AWB copy is flown with the cargo (for ECP shipments) Messaging Flow The following illustrates the messaging flow between the parties. eawb SOP Riyadh v0.1 Page 8

9 Section 1.3 Exception management This section lists the standard exceptions management procedures. Exception management 1: detects missing electronic shipment data in own system upon delivery of the goods Responsibility Task 1. Initiates tracing of electronic shipment data through its systems 2. If data cannot be retrieved within the systems, informs the delivery person and/or the office that a new transmission is required before cargo acceptance can be performed. 3. If the shipment data transmission cannot be completed successfully due to any reason, issue a paper AWB with sufficient copies for transit and destination stations ( will request to provide required information by telephone or ). Promptly responds to the request from to avoid delay to cargo and delivery driver schedule. eawb SOP Riyadh v0.1 Page 9

10 Exception management 2: Detects a discrepancy in number of pieces and/or weight between electronic shipment data and physical goods delivered Responsibility Task 1. Informs the delivery person and contacts immediately the by telephone, informing of required correction to data. 2. Requests confirmation from to proceed with the correction or alternately, asks to re-send the corrected FWB (or XFWB) message or the corrected e-awb data via web portal. 3. Upon receiving confirmation (or corrected data) from, confirms the shipment as Ready for Carriage in the system with the correct number of pieces and weight matching the physical goods received. 4. Confirms Ready for Carriage status to : a) Sends FSU-RCS (or XFSU-RCS) message to, or alternatively sends the ready for carriage confirmation to via web portal. This should contain the correct number of pieces and weight matching the physical goods received. b) Provides the Cargo Receipt (in accordance with IATA Resolution 600g) to by electronic means (example: downloadable PDF posted on website). Promptly responds to the request from to avoid delay to cargo and delivery driver schedule. eawb SOP Riyadh v0.1 Page 10

11 SECTION 2: EXPORT CARRIER USING GROUND HANDLING AGENT This section describes the operational procedures at the airport for export shipments, when uses a Ground Handling Agent (GHA) to accept, process, and manage its cargo shipments at the Airport. Section 2.1 Pre-requisites Actor Pre-requisites Task Signed the IATA Multilateral e-awb Agreement, including all branches tendering cargo at the airport. Commits to tender e-awb shipments for all destinations. Commits to delivering cargo ready for carriage (in accordance with IATA Resolution 833, including appropriate labelling and packaging). Accepts to receive electronic Cargo Receipt as delivery receipt (in case of delivery by third party without access to electronic information, a paper Cargo Receipt or Warehouse Receipt can be requested). Capable of transmitting e-awb data to, by means of EDI messages, or via a web portal. When using EDI messages to transmit AWB data to, will use Cargo-IMP FWB version 16 or higher (or Cargo-XML equivalent). Capable of sending House manifest data to, by using EDI message or via a web portal. Capable of receiving AWB status updates from, by means of EDI messages, or via a web portal. When using EDI messages, is able to receive FSU messages, particularly FSU- FOH and FSU-RCS messages (or Cargo-XML equivalent). Capable of archiving the EDI messages for required duration. Joined the IATA Multilateral e-awb Agreement and listed the Airport under the Agreement. Activated the IATA Multilateral e-awb Agreement with (including all its branches that tender cargo at the Airport). Capable of receiving e-awb data from, by means of EDI messages or via a web portal, and also capable of processing and storing it electronically. When using EDI messages, is able to receive Cargo-IMP FWB version 16 or higher (or Cargo-XML equivalent). Capable of sending Status updates, by using EDI message or via a web portal. When using EDI messages to send Status updates, is able to send FSU messages, particularly FSU-FOH and FSU-RCS messages (or Cargo-XML eawb SOP Riyadh v0.1 Page 11

12 equivalents). GHA GHA GHA GHA All parties Capable of receiving House manifest data from, by using EDI message or via a web portal. Capable of archiving the EDI messages for required duration. Commits to implementing the Single Process 2, enabling to tender all shipments without paper AWB. Commits to providing proper instructions/training to all concerned staff. Updated internal processes to no longer require paper AWB copies for Accounting activities with regards to e-awb shipments. Commits to engage in e-awb, providing proper instruction/training to concerned staff members. Capable of receiving e-awb data from by means of EDI messages, in particular Cargo-IMP FWB version 16 or higher (or Cargo-XML equivalent). Capable of sending Status update (FSU) messages, particularly FSU-FOH and FSU-RCS messages (or Cargo-XML equivalents). Capable of archiving the EDI messages for required duration. Ensure that for secured cargo the transmission is compliant with the IATA e- Consignment Security Declaration specifications. All parties In case of changes to the AWB data after the transmission of the initial FWB (or XFWB), the same can be updated by the freight forwarder with a subsequent FWB (or XFWB) until the shipment reaches RCS status. Updates after this need to be studied by the relevant parties. All receiving parties should be able to receive and process subsequent FWB (or XFWB) as per IATA Recommendation. Note: the MeA (resolution 672, article 4, para 4.5: If (GHA) determine there is a discrepancy between the air waybill data established through Electronic Communication and the weight of, number of pieces, volume of, measurements of, or rate applicable to a cargo shipment then shall so notify ; may receive such cargo shipment by using a Warehouse Receipt (as an interim cargo receipt) and acknowledging through Electronic Communication that the cargo is freight on hand. Discrepancies shall be governed by the s exception procedures. Section 2.2 Operations process steps Day-to-day Operations Step Actor Task 1. Books the e-awb shipment with. 2 Guidelines for Single Process: eawb SOP Riyadh v0.1 Page 12

13 2. Provides to GHA information about the booked cargo at regular intervals through FBL messages. 3. Sends the FWB (or XFWB) message to the, at least 30 minutes before delivery of the goods. Alternatively, the e-awb data can be submitted to via web portal. Notes: 1. For shipments without accompanying paper pouch and tendered as e-freight, shall insert Special Handling code EAW in the FWB (or XFWB) message sent to, or in the e-awb data submitted via web portal. 2. For secured cargo the transmission must be compliant with the IATA e- Consignment Security Declaration specifications. 4. Processes the e-awb data message received from the, and: b) If no errors are found, sends FMA (or XFMA) to acknowledging receipt of the e-awb data message. Alternatively, can send the acknowledgement via web portal. or b) If errors are found, sends FNA (or XFNM) to notifying about the errors. Alternatively, can send the error notification via web portal. Note: Upon receiving error notification, shall re-send the corrected e-awb data to. 5. Inserts Special Handling code ECC (if e-awb route) or ECP (if paper AWB needs to be printed from the data), taking into account applicable International Convention, regulatory requirements and network constraints. Note: For shipment under ECP, it is the responsibility to provide the multipage/multicolour AWB to the GHA at the time of freight acceptance 6. Transmits the e-awb data to GHA, including the Special Handling codes. Also, transmits the House Manifest data, if it is a consolidation shipment. 7. Tenders the goods to GHA acceptance facility, ready for carriage (in accordance with IATA Resolution 833, including appropriate labelling and packaging) with the following: a) In case there is an accompanying document pouch, ensure it is properly labelled according to IATA Recommended Practice 1600u. b) Any applicable supporting documents (Example: Shippers Declaration for Dangerous Goods, etc.) 8. GHA Receives the goods and matches the physical goods with the electronic shipment data in the GHA system (Paper AWB copy is not requested and not used). Note: If any discrepancy is found between physical goods and the electronic shipment data, it shall be communicated to the delivery person immediately, and the shipment shall be handled according to s exception eawb SOP Riyadh v0.1 Page 13

14 procedures, or as agreed between and. 9. GHA After all the conditions to take delivery of the physical goods are positive: a) GHA assigns it to a location in the system b) Provides a Cargo Receipt/ Warehouse Receipt to the person delivering the cargo. Note: The Cargo Receipt/Warehouse Receipt can also be provided using electronic means (for example, via ) c) Confirms on Hand status to, including weight, volume, and number of pieces received along with the acceptance date and time. 10. Sends FSU-FOH (or XFSU-FOH) message to, or alternately sends freight on hand confirmation to via web portal. Note: The FSU-FOH (or XFSU-FOH) message or freight on hand confirmation should be sent even if the shipment could be declared ready for carriage right away. 11. GHA Performs checks necessary to confirm shipment as ready for carriage. Notes: a) In case of secured cargo, checks the validity of the Security Declaration in the electronic data and certifies this action digitally. b) In case of unsecured cargo, performs the Security Check according to current country regulations and, certifies this action digitally. c) All security related activities to be compliant with the IATA e-consignment Security Declaration specifications. 12. GHA After all required checks are completed with positive results, confirms the shipment as Ready for Carriage in the GHA system. 13. Confirms Ready for Carriage status to : a) Sends FSU-RCS (or XFSU-RCS) message to, or alternatively sends the ready for carriage confirmation to via web portal. b) Provides the Cargo Receipt (in accordance with IATA Resolution 600g) to by electronic means (example: downloadable PDF posted on website). 14. GHA Manifests the shipment according to verified electronic shipment data in their system. 15. GHA Prepares the physical shipment for transportation. a) Loads the shipment onto a ULD (pallet, container, etc). b) When present, includes the shipment document pouch into the flight pouch. c) Ensures paper AWB copy is flown with the cargo when required. eawb SOP Riyadh v0.1 Page 14

15 Messaging Flow The following illustrates the messaging flow between the parties. eawb SOP Riyadh v0.1 Page 15

16 Section 2.3 Exception management This section lists the standard exceptions management procedures. Exception management 1: GHA detects missing electronic shipment data in system upon delivery of the goods Responsibility Task GHA Scenario 1 : 1. Initiates tracing of electronic shipment data through its own system and system 2. If data cannot be retrieved within the systems, informs the delivery person and/or the office that a new transmission is required before cargo acceptance can be performed. 3. If the shipment data transmission cannot be completed successfully due to any reason, issue a paper AWB with sufficient copies for transit and destination stations (GHA will request to provide required information by telephone or ). Scenario 2 ( Security Information ) : If missing or wrong => Perform acceptance and screen cargo. Scenario 3 ( House manifest data ) : If missing electronic House Manifest Data for Consolidated shipment => Accept shipment under paper House Manifest and continue with RCS according to carrier requirements. Scenario 4 ( Missing AWB data ) : Stop acceptance, inform all parties Promptly reacts to the request from GHA to avoid delay to cargo and delivery driver schedule. Promptly responds to the request from GHA/ to avoid delay to cargo and delivery driver schedule. eawb SOP Riyadh v0.1 Page 16

17 Exception management 2: GHA detects a discrepancy in number of pieces, weight, dimensions or volume between electronic shipment data and physical goods delivered Responsibility Task Scenario 1 Scenario 2 1. Informs the delivery person and contacts immediately the (by telephone or ), informing of required correction to data. Accept shipment under FOH, continue with RCS according to requirements. GHA 2. Requests confirmation from to proceed with the correction or alternately, GHA asks to re-send the corrected FWB (or XFWB) message or the corrected e-awb data via web portal. 3. Upon receiving confirmation (or corrected data) from, confirms the shipment as Ready for Carriage in the GHA system with the correct number of pieces and weight matching the physical goods received. Confirms Ready for Carriage status to : a) Sends FSU-RCS (or XFSU-RCS) message to, or alternatively sends the ready for carriage confirmation to via web portal. This should contain the correct number of pieces and weight matching the physical goods received by the GHA. b) Provides the Cargo Receipt (in accordance with IATA Resolution 600g) to by electronic means (example: downloadable PDF posted on website). Supports any request from above parties, in order to minimize delay to the shipment flow. eawb SOP Riyadh v0.1 Page 17

18 SECTION 3: IMPORT CARRIER SELF HANDLED This chapter describes the operational procedures at the airport for import shipments, when is self-handled at the Airport. Section 3.1 Pre-requisites Actor and Pre-requisites Task Ready to operate paperless or to accept a locally produce print-out of the AWB from electronic shipment data Capable of receiving and processing EDI messages: FWB version 16 or higher (or Cargo-XML equivalent) and FHL version 4 (or Cargo-XML equivalent). Capable of archiving the EDI messages for required duration. Capable of providing the shipment data in electronic or AWB print-out form upon request by local authorities, consignee, consignee s agent or any other relevant stakeholder in the import process. Informed/trained all operational staff on handling e-awb shipments. Section 3.2 Operations process steps Day-to-day Operations Step Actor Task 1. Receives FFM (or XFFM) message from Origin station along with all corresponding FWB (or XFWB) message. 2. Processes the shipments based on the FWB (or XFWB) message received. 3. Notifies the and/or its Customs Broker of the arrival of the shipment (Example: by using FSU-NFD message). Note: In case of accompanying document pouch, notifies or its Customs Broker (Example: by using FSU-AWD message) and makes the documents available for collection. 4. Takes necessary steps to process the import e-awb shipments without paper copies and informs the of any problem encountered with the shipments. 5. Handover shipment to, and records completion of delivery (Example: by using FSU-DLV message). 6. Provides and Authorities full support for e-awb related questions upon request. eawb SOP Riyadh v0.1 Page 18

19 Exception management 1: Upon arrival of the flight, the electronic shipment data is not found in system Responsibility Task Sends a request for AWB data to the Origin station and informs the of the irregularity. Note: In the event of cargo arriving without any document, any electronic data, any mention on Flight Manifest, it will be reported as FDCA (Found Cargo). Paperless nature of the shipment will be determined only when information is transmitted. If the accompanying document pouch is missing, then the status missing docs is sent to Origin station. Supports any request from above parties, in order to minimize delay to the shipment flow. Section 3.3 Exception management Exception management 2: Paper copy of the AWB for an e-awb shipment is requested by any party Responsibility Task Produces and hands over a print out of the electronic shipment data. Reports to IATA any case of un-necessary request for paper documentation by Authorities. eawb SOP Riyadh v0.1 Page 19

20 SECTION 4: IMPORT CARRIER USING GROUND HANDLING AGENT This section describes the operational procedures at the airport for export shipments, when uses a Ground Handling Agent (GHA) to accept, process, and manage its cargo shipments at the Airport. Actor Section 4.1 Pre-requisites Pre-conditions Task Ready to operate paperless, or to accept a locally produced print-out of the AWB from electronic shipment data. and GHA GHA GHA /GHA Capable of receiving and transmitting EDI messages: FWB version 16 or higher (or Cargo-XML equivalent) Capable of archiving the EDI messages for required duration. Capable of receiving and processing EDI messages: FWB version 17 (or Cargo-XML equivalent) Capable of providing the shipment data in electronic or AWB print-out form upon request by local authorities, consignee, consignee s agent or any other relevant stakeholder in the import process. Capable of archiving the EDI messages for required duration. Has informed/trained all operational staff on handling e-awb shipments. Section 4.2 Operations process steps Day-to-day Operations Step Actor Task 1. Receives FFM (or XFFM) message from Origin station along with all corresponding FWB (or XFWB) message. 2. Sends to GHA the FFM (or XFFM) message received from Origin station along with all corresponding FWB (or XFWB)) message 3. GHA Receives from the FFM (or XFFM) message, along with all corresponding FWB (or XFWB) message. 4. GHA Processes the shipments based on the FWB (or XFWB) message received from. 5. GHA Notifies the and/or its Customs Broker of the arrival of the shipment (Example: by using FSU-NFD message). Note: In case of accompanying document pouch, notifies or its Customs Broker (Example: by using FSU-AWD message) and makes the documents available for collection. eawb SOP Riyadh v0.1 Page 20

21 6. Makes the necessary efforts to process the import shipments without paper AWB copies and, informs the GHA of any problem encountered. 7 GHA Handover shipment to, and records completion of delivery (Example: by using FSU-DLV message). 8. Provides GHA, and Authorities full support for e-awb related questions upon request. Section 4.3 Exception management This section lists the standard exceptions management procedures. Exception management 1: Upon arrival of the flight, the Electronic Shipment Data is not found in GHA s system Responsibility Task 1. Initiates tracing of electronic shipment data through agreed procedure with. 2. Sends a request for AWB Data to the origin station. GHA 3. Informs the Consignee oandf the irregularity. Note: In the event of cargo arriving without any document, any electronic data, any mention on Flight Manifest, it will be reported as FDCA (Found Cargo). Paperless nature of the shipment will be determined only when information is transmitted. If the accompanying document pouch is missing, then the status missing docs is sent to. Supports any request from above parties, in order to minimize delay to the shipment flow. Informs the and/or GHA of any problem encountered. Exception management 2: Paper copy of the AWB for an e-awb shipment is requested by any party Responsibility GHA Task Produces and hands over a print out of the electronic shipment data. Reports to IATA any case of un-necessary request for paper documentation by Authorities. Informs the and/or GHA of any problem encountered. eawb SOP Riyadh v0.1 Page 21

22 APPENDIX: GLOSSARY OF TERMS Acronym AWB Cargo-IMP Cargo-XML e-awb ECC Meaning Air Waybill IATA Cargo Interchange Message Procedures IATA Cargo-XML Messages Electronic Air Waybill Consignment established with an electronically concluded cargo contract with no accompanying paper air waybill ECP Consignment established with a paper air waybill contract being printed under an e- AWB agreement EDI EAW Electronic Data Interchange e-freight consignment with no Accompanying Documents. EAP Partial e-freight consignment with Accompanying Document. Not considered as e- freight shipment anymore. FFM FMA FNA FOH FSU FWB GHA IATA RCS XFFM XFHL XFNM XFSU XFWB Cargo-IMP Airline Flight Manifest Message Cargo-IMP Acknowledgment Message Cargo-IMP Rejection (Error) Message on Hand Cargo-IMP Status Update Message Cargo-IMP Air Waybill Data Message Ground Handling Agent International Air Transport Association Cargo and Documents are Received Ready for Carriage Cargo-XML Airline Flight Manifest Message Cargo-XML House Manifest Data Message Cargo-XML Notification Message Cargo-XML Status Update Message Cargo-XML Air Waybill Data Message eawb SOP Riyadh v0.1 Page 22