e-freight mip strategy version 4.1 - iata - home · page 5/105 iata cargo mip strategy disclaimer...

www.iata.org/e-freight IATA CARGO

IATA e-freight

Message Improvement Programme (MIP) Strategy

v4.1

www.iata.org/e-freight /105 IATA CARGO MIP Strategy

Table of Contents

DISCLAIMER 5

CONTACTS 6

REVISION HISTORY 7

1 EXECUTIVE SUMMARY 9

2 OBJECTIVES 10

3 MIP AND CARGO 2000 11

4 SCOPE OF MIP 12

4.1 Message types in scope for IATA e-freight 12 4.2 Message Scope for MIP 13 4.3 Deliverables 14 4.3.1 Improvements in quality and penetration 14 4.3.2 IATA e-freight MIP Handbook 14 4.3.3 Standard set of error messages 14

5 PROGRAMME PARTICIPANTS 15

5.1 Airlines 15 5.2 Forwarders 16

6 MESSAGE IMPROVEMENT METHODOLOGY 17

6.1 Baseline measurement 17 6.2 Root Cause Analysis 17 6.3 Improve quality and increase penetration 17 6.4 Accurate FWB and FHL messaging 17 6.4.1 FWB 17 6.4.2 FHL (where the airline is reporting HAWB for customs purposes) 18

7 GOVERNANCE AND ORGANIZATION 19

7.1 Governance 19 7.2 Organisation structure 19 7.3 e-freight MIP Action Group 20 7.4 Roles and Responsibilities 20 7.4.1 IATA Regional Cargo Director 20 7.4.2 IATA Manager Cargo Business Intelligence 20 7.4.3 IATA Head of Cargo Business Processes and Standards 21 7.4.4 MIP Action Group 21 7.4.5 Airline MIP Representative 21 7.4.6 Forwarder MIP Representative 21 7.4.7 IATA e-freight Representatives 22 7.4.8 IATA StB Programme Centre 22 7.5 IATA Cargo Standards 22

8 COMMUNICATION 23


8.1 Monthly reports 23 8.2 Problem resolution 23 8.3 Airline MIP action plans 23 8.4 Escalation procedure 23

9 RISKS AND ISSUES 24

9.1 Resource requirement 24 9.2 Maintaining consistency across participants 24 9.3 Adding complexity 24

10 APPENDIX A - MIP INPUT - AIRLINE AND CCS MONTHLY DATA FILES 25

10.1 Airline data to submit to IATA 25 10.2 Optional CCS data to submit to Airlines 25 10.3 Recommended data reporting sequence 26 10.4 Monthly data flow 27 10.5 CSV file format 27 10.6 FWB summary file 28 10.6.1 File name 28 10.6.2 Fields description 28 10.6.3 Data records to include 29 10.6.4 Sample data 29 10.6.5 Sample file dump 29 10.7 FHL summary file 30 10.7.1 File name 30 10.7.2 Fields description 30 10.7.3 Data records to include 31 10.7.4 Sample data 31 10.7.5 Sample file dump 31 10.8 FWB detail file 32 10.8.1 File name 32 10.8.2 Fields description 32 10.8.3 Data records to include 34 10.8.4 Sample data 34 10.8.5 Sample file dump 34 10.9 FHL detail file 35 10.9.1 File name 35 10.9.2 Fields description 36 10.9.3 Data records to include 37 10.9.4 Sample data 37 10.9.5 Sample file dump 37

11 APPENDIX B - MIP OUTPUT - MONTHLY REPORTING 39

11.1 Report 1 - Industry Report - Overall Industry FWB Quality and Penetration 39 11.2 Report 2 - Industry Report - Overall Industry FHL Quality and Penetration 41 11.3 Report 3 - Airline Report - FWB Quality and Penetration 43 11.4 Report 4 - Airline Report - FHL Quality and Penetration 45 11.5 Report 5 - Agent Report - IATA FWB Performance report to Agent 47 11.6 Report 6 - Agent Report - IATA FHL Performance report to Agent 49 11.7 Report 7 - Airline Report - Agents performance with airline 51 11.8 Report 8 - Industry Report - Agents overall industry performance 53 11.9 Report 9 - Industry Report - Country Performance Report 55 11.10 Report 10 - Airline and Agent Report - e-freight Location Report 57 11.11 Report 11 – Industry Report – Industry FWB Penetration Report (chart) 59 11.12 Report 12 – Industry Report – Industry FHL Penetration Report (chart) 60 11.13 Report 13 – Airline Report – Airline FWB/FHL Penetration Report (chart) 61 11.14 Report 14 - Validation and Error Reports 62


11.15 Report 15 - Top Errors Report 63

12 APPENDIX C - ERROR CODES 64

12.1 Issues with the current error code set 64 12.2 Improvement – New simplified error code set 64 12.3 The old MIP error code set will continue to be supported but not expanded 65 12.4 MIP Reporting 65 12.5 New Error Code Set 65 12.5.1 Accounting Information Errors 66 12.5.2 Agent Errors 66 12.5.3 Agent Reference Data Errors 67 12.5.4 Air Way Bill Consignment Detail Errors 67 12.5.5 CC Charges in Destination Currency Errors 69 12.5.6 Shipper's Certification Errors 69 12.5.7 Consignee Errors 69 12.5.8 Commission Information Errors 70 12.5.9 Collect Charge Summary Errors 70 12.5.10 Customs Origin Errors 71 12.5.11 Charge Declarations Errors 71 12.5.12 Flight Booking Errors 71 12.5.13 FWB Errors 72 12.5.14 Harmonised Tariff Schedule Information Errors 72 12.5.15 House waybill summary details Errors 72 12.5.16 Carrier's Execution Errors 73 12.5.17 Message Errors 73 12.5.18 Also Notify Errors 73 12.5.19 Nominated Handling Party Errors 74 12.5.20 Other Customs Information Errors 74 12.5.21 Other Participant Information Errors 75 12.5.22 Other Service Information Errors 75 12.5.23 Other Charges Errors 75 12.5.24 Prepaid Charge Summary Errors 76 12.5.25 Sender Reference Errors 76 12.5.26 Rate Description Errors 77 12.5.27 Routing Errors 78 12.5.28 Shipper Errors 80 12.5.29 Sales Incentive Information Errors 80 12.5.30 Special Handling Details Errors 80 12.5.31 Shipment Reference Information Errors 81 12.5.32 Special Service Request Errors 81 12.5.33 Free Text Description of Goods Errors 81 12.6 Old Error Code to New Error code translation 81

13 APPENDIX D - ACTION PLAN 104

13.1 Airline Action Plan – Example. 104 13.2 IATA Action Plan – Example. 105


Disclaimer

The information contained in the publication is subject to constant review in the light of changing business requirements, government requirements and regulations. No subscriber or other reader should act on the basis of any such information without referring to the applicable laws and regulations and/or without taking appropriate professional advice. Although every effort has been made to ensure accuracy, the International Air Transport Association shall not be held responsible for loss or damage caused by errors, omissions, misprints or misinterpretation of the contents hereof. Furthermore, the International Air Transport Association expressly disclaims all and any liability to any person, whether a purchaser of the publication or not, in respect of anything done or omitted, and the consequences of anything done or omitted, by any such person in reliance on the contents of this publication.

No part of this guide may be reproduced, recast, reformatted or transmitted in any form by any means, electronic or mechanical, including photocopying, recording or any information storage and retrieval system, without the permission of:

Director Cargo Supply Chain Management, IDFS

International Air Transport Association

Route de l'Aéroport

33 P.O. Box 416

1215 Geneva 15 Airport

Switzerland


Contacts

MIP

Constantin Syridis, Manager, Cargo Business Intelligence

Email: [email protected]

Website: http://www.iata.org/whatwedo/cargo/efreight/MessageImprovementProgramme-MIP.htm

IATA e-freight

Contact the team at [email protected]

Website: www.iata.org/e-freight


Revision history

Revised by Changes Version Date David Calder Original 1.0 22 Aug 2006

David Calder Section 1: Revision history – added.

Section 4.1 Scope/Message types – Table corrected: (v1.0 stated FZB+FWB in scope; revised to FWB/FHL in scope).

1.01 12 Sep 2006

David Calder Updated with industry feedback – no material changes

1.02 14 Sept 2006

Patrick Murray, e-freight Systems Manager

Updated to move FWB process to appendix, include reporting formats, feedback from C2K and feedback from MIP/StB/Legal Team.

2.0 18 Jan 2007


Updated to include changes to FWB/FHL received definitions. Small changes to IATA roles and Responsibilities.

2.1 2 Feb 2007


Updated to expand definition of the “invalid business data” field.

2.2 9 Feb 2007


Updated to include revised reporting format and details relating to FSU messages in exchange for correct FWBs.

3.0 25 May 2007


Updated to revise IATA AD business process roles and responsibilities and include role of Manager e-freight standards development.

Corrected “typo” (reference to FWB) in FHL reports

Included CCS FHL report details.

Changed Lothar Moehle’s company to C2K.

3.1 27 May 2007


Updated to include notes regarding the measurement of duplicates and airline rejections by the CCS.

Updated to clarify the composition of the “total number of FWB/FHL messages received) that need to be included in the summary report.

3.2 6 Jun 2007

Constantin Syridis, Manager, e-freight EDI Improvement

Cover page, TOC, disclaimer and contacts added, revision updated

Some minor formatting / wording changes / corrections

Added definition for 100% penetration definition and full participants

FFM measurements for June 2008

Removed the Industry Action Group from Governance

Improved MIP Action Group table

Appendix A - removed following conversation with James Shannon who confirms there is no official score sheet defined

Appendix A is now the reports to be provided by Airlines. Improved parts and clarified dates. Added EAP and EAW codes for e-freight Participants.

Appendix B – Reports 1 to 14 samples with explanations.

Appendix D - Error codes typos corrected, added 2

3.3 29 Nov 2007


more error codes for CCS reporting

Constantin Syridis, Manager, e-freight EDI Improvement

Minor wording and formatting adjustments done.

Message scope for e-freight updated.

Message scope for MIP updated.

Organisation structure and governance updated.

Appendix A – MIP Input – File formats section completely updated and simplified following MIP Action Group conference.

Appendix B – MIP Output – Section updated with new report 15, some clarifications added.

Appendix C – New Error codes: entire section updated with simplified / reduced set of error codes + conversion table from old to new error codes.

4 December 2008

Izzy Anderson, Manager Cargo Business Planning and Performance

Revised titles of IATA e-freight Stakeholders

Added EDI specification for e-AWB programme

4.1 March 2010


1 Executive Summary

Today, the air cargo industry almost exclusively relies on paper-based processes to support the movement of freight. The average shipment (MAWB) generates more than 30 documents that are used and / or handled by the various parties involved -shippers, freight forwarders, handling agents, export and import brokers, airlines, and last but not least, Customs and other government authorities. The long-term vision for the industry is to eliminate the need to produce and transport all paper for all stakeholders. This is paperless e-freight and e-Customs. However, before the paper can be removed from the transport process, e-freight stakeholders must have confidence in the quality (completeness and accuracy) of the data in those messages.

To address this, the IATA e-freight Message Improvement Programme (MIP) aims to measure the quality and penetration of electronic documents exchanged between supply chain partners, in order to allow stakeholders to reduce unnecessary duplicate messages and manual corrections. This will also support the philosophy of entering data once at source and share with all partners in the chain. As the e-freight project scope includes new messages to the programme, the MIP may be expanded accordingly.

This Message Improvement Programme Strategy Document describes: The scope of IATA e-freight MIP

The methodology to be used for measuring and increasing both quality and penetration

The governance for MIP

The benefits, risks and issues

The format to be used by airlines and CCS for submission of monthly data

The reports that IATA produces for Airlines, Freight Forwarders and the Industry.

Participation into MIP is mandatory for airlines and freight forwarders involved in e-freight or e-AWB implementations. Other airlines and freight forwarders can also join the programme in preparation for e-freight or e-AWB. Based on the statistical results compiled and provided by IATA, stakeholders will then work together to solve the problems and achieve the objectives of the programme.

By participating in the programme, airlines and freight forwarders are agreeing that aggregated industry or country reports, specified as part of this document, can be shared amongst all participants. Confidential reports for one particular airline or one particular forwarder will not be shared. Should anyone object to any of the information, specified as part of the reports, then this objection should be made in writing to the IATA Director Cargo Supply Chain Management IDFS, prior to the participant joining the programme.

Participation, for an Airline, is defined as providing shipment data as described in the appendices on a monthly basis (15th of the month) to IATA. While it is recognised that an airline may be unable to submit all data files that are complete in every respect, the goal is for all participants to do so as soon as possible.


2 Objectives

The primary objective of IATA e-freight is to eliminate the need to transport paper documents for air cargo. To achieve this goal, numerous business, technical, legal and regulatory requirements must be met. Two such requirements are:

The documents that accompany an e-freight shipment will, wherever possible, be replaced by electronic messages

Data in these electronic messages must be complete and accurate for all shipments. IATA e-freight stakeholders will not replace paper documents with electronic messages unless they have confidence in the quality (completeness and accuracy) of the data in those messages.

To provide a coordinated approach to improving message quality and penetration, the IATA e-freight project has, together with industry stakeholders, established an e-freight message penetration, measurement and improvement programme. This programme has started with a limited number of stakeholders and documents, but continues to expand to become industry wide. The programme enables participants to share lessons learned to resolve common problems and provides standard, simple measures to track progress.

The IATA e-freight Message Improvement Programme (MIP) is an integral part of the e-freight project as well as e-AWB project. All stakeholders involved with local e-freight and e-AWB implementations are required to participate, but the programme is also open to non e-freight stakeholders that will be able to derive direct benefit from improved message performance before they start implementing e-freight or e-AWB.


3 MIP and Cargo 2000

IATA e-freight and Cargo 2000 (C2K) are complementary. C2K and IATA e-freight work together, where appropriate and feasible, to ensure alignment. However, they remain separate programmes.

To achieve the mutual objective, it is envisaged that MIP will become part of the C2K quality measurement and all C2K members will join the IATA e-freight MIP programme. The C2K methodology carries additional quality checks in that certain FWB data elements are measured as part of its existing operating process, checking for receipt, sequence, timeliness and accuracy (the latter defined as the information in the FWB matching that in the route-map). This benefits e-freight by also improving message quality.

As part of this programme, C2K Freight Forwarder and Airline Members will work with IATA to improve the FWB and FHL message penetration and quality.


4 Scope of MIP

The scope of MIP is to cover the messages and documents as defined by the IATA e-freight strategy, by

1. Collecting monthly data from the appropriate stakeholders

2. Producing and distributing monthly reports to the appropriate stakeholders

3. Establishing a formalised root cause analysis process for investigating abnormal measurements

4. Collecting root cause analysis results that are of interest to all industry stakeholders for publication into an EDI Handbook

5. Setting quality and penetration targets with the industry stakeholders

The MIP will continue as long as there is a need to increase data quality and penetration to the point where e-freight stakeholders have sufficient confidence in the quality of data contained in EDI messages to discontinue the use of paper documents as the primary source of shipment information. At this point, subject to other (e.g. legal) constraints, e-freight stakeholders must be in a position to implement paper-free operating processes. Once the paper is removed from the process, quality might still need to be continually monitored.

Note: Once paper documents are no longer in use, stakeholders will have to ensure data quality by comparing data in messages with the physical freight (e.g. weight, pieces). Data quality measurement initiatives in a paper-free environment could potentially be incorporated into a future phase of MIP or Cargo 2000 measurement processes. This will be addressed at the appropriate time.

4.1 Message Types in Scope for IATA e-freight The following table shows the 13 messages / documents in scope for IATA e-freight. Not all documents will be measured by MIP as some of them are not yet widely used enough at this time or others depend on data from messages already extensively measured by MIP (e.g. WCO - World Customs Organisation messages). .

Message definer

Message Message type

From To Format finalised

Version Upcoming versions

Measured by MIP

Measure provider

Comment

Flight / Cargo Manifest

FFM Orig Carrier

Dest Carrier

Yes 6 7 No Airlines decided not to measure this, as it is an internal document. Penetration is 100%

Master Air Waybill

FWB Orig Forwarder

Orig Carrier

Yes 15 none Yes Orig Carrier

House Manifest FHL Orig Forwarder

Orig Carrier

Yes 3 4 Yes Orig Carrier

Detailed version for customs purposes.

IATA Cargo-IMP messages

House Air Waybill

FZB Orig Forwarder

Dest Forwarder

Yes 3 4 No Not widely used today, to be recommended between 2 forwarders

WCO messages

Import Goods Declaration

WCODEC Dest Forwarder

Import Customs

Yes 2 No WCO recommendation based on UNCEFACT CUSDEC. Not widely used, depends on national customs.


Message definer

Message Message type

From To Format finalised

Version Upcoming versions

Measured by MIP

Measure provider

Comment

Import Cargo Declaration

WCOCAR Dest Carrier

Import Customs


Export Goods Declaration

WCODEC Orig Forwarder

Export Customs


Export Cargo Declaration

WCOCAR Orig Carrier

Export Customs


Customs Release Export

WCORES Export Customs

Orig Forwarder /

Carrier

In progress No WCORES is not yet finalised so use CUSRES until the message is finalised.

Customs Release Import

WCORES Import Customs

Dest Forwarder /

Carrier

In progress No WCORES is not yet finalised so use CUSRES until the message is finalised.

Invoice - Shipper Orig Forwarder

Yes TBD TBD Standard defined mainly between shippers and forwarders for customs clearance purposes

Packing List - Shipper Orig Forwarder

Yes TBD TBD Standard defined mainly between shippers and forwarders for customs clearance purposes

UNeDocs messages

Certificate of Origin

- Shipper Orig Forwarder

Yes TBD TBD Standard being defined mainly between shippers and forwarders for customs clearance purposes

4.2 Message Scope for MIP The scope is initially restricted to measurement of the FWB and FHL messages, representing the master air waybill and house manifest respectively. These messages were selected for the following reasons:

1. Both FWB and FHL messages are in relatively common use today and they are routinely used as part of existing operational processes. However, performance (both quality of data and the quantity of messages sent) must be improved.

2. The FWB is the message used to transmit master air waybill information. Since the master air waybill forms the contract of carriage between forwarder and airline and contains details of the shipper, consignee, description of goods, value for customs, etc., it is likely that (subject to legal due diligence and evaluation of alternative solutions) the e-AWB, a variant of the FWB, will be the main source of shipment information, including contract of carriage details, once the paper master air waybill is no longer required. As such, it is particularly important that the information contained in the FWB is correct.


3. The FHL is the electronic message containing data found in the house manifest, but it contains much of the same information that is in the house waybill. Since the house waybill forms the contract of carriage between shipper and forwarder, it is essential that any electronic replacement is accurate. Although the FZB is the Cargo-IMP message used to transmit house waybill information, it is not widely used, so the FHL (which contains much of the same data) is the focus of the MIP. Since an e-freight principle is that data should only be entered once, improving the quality of the FHL will automatically improve the quality of the data in the FZB once that message is implemented industry wide.

4. Customs administrations are increasingly demanding that carriers and forwarders submit advance cargo shipment information in electronic form for security risk assessment purposes. Much of the information required by Customs is contained in the FWB and FHL messages. Since airlines and forwarders are subject to fines if the information provided to Customs is incomplete or inaccurate, they expend considerable effort in ensuring this advance security information is correct, often incurring additional operating costs, for example to re-enter the data from paper documents or to check messages manually prior to submission. By focusing the MIP on messages where there is a requirement for accuracy today, stakeholders should realise immediate benefits from improved quality, even before the paper documents are removed from the overall process.

As the MIP develops and as stakeholders in early adopter countries implement electronic messages to replace other documents, these messages may be incorporated into the MIP.

4.3 Deliverables

4.3.1 Improvements in Quality and Penetration Using the reports described later in this document and the strategy also described herein, the IATA e-freight Message Improvement Programme delivers improvements in both penetration and quality for its participants.

4.3.2 IATA e-freight MIP Handbook The scope of the MIP also includes an IATA e-freight MIP Handbook. The IATA e-freight MIP Handbook consists of three sections:

a. An easy-to-understand guide to EDI (Part 1) b. An introduction to the Message Improvement Programme (Part 2) c. A guide to the most common problems and how to fix them (Part 3)

4.3.3 Standard Set of Error Messages Another section of this document consists of an agreed standard set of error messages, which accompanies corrected or rejected messages. The methodology may result in new IATA resolutions or recommended practices, which will govern the messaging rules.


5 Programme Participants

The programme is open to freight forwarders and carriers, since these parties are generally the originators and recipients of the FWB and FHL messages.

The position regarding other stakeholder groups is as follows:

System providers will be involved in the MIP from the start since system providers transmit the messages and ground handlers often process, send and receive messages on behalf of the airlines. Freight forwarders and airlines should involve their own service providers as appropriate.

Shippers and consignees are not involved initially with these messages and therefore do not need to be involved in the MIP at this stage.

Customs can be the final recipients of the message information, particularly where advance submission of security information is required. However, if the quality checks are performed by the carrier, customs should receive correct information; if incorrect or incomplete information is sent to customs, they will undoubtedly provide feedback which the carriers and forwarders can then investigate and resolve any issues.

The initial participants are a range of:

IATA e-freight working group members (airlines and forwarders)

Cargo 2000 members (airlines and forwarders)

Other airlines which have already expressed an interest in improving message performance

Airlines and Forwarders in e-freight countries as they start implementation

Airlines and Forwarder implementing e-AWB

Programme Participants contact details are published centrally on the IATA MIP extranet site. Each Airline and Forwarder is required to nominate an IATA e-freight MIP representative, who is responsible for driving the IATA e-freight MIP programme within their company, in accordance with the roles and responsibilities laid out later in this document.

The IATA e-freight Message Improvement Programme is an industry wide initiative to improve the quality and penetration of electronic data involved in the transportation of cargo. As with other projects under the umbrella of the Simplifying the Business programme, only an industry wide effort can ensure that the maximum benefits are achieved. In the case of the IATA e-freight and e-AWB MIP, it is imperative that ultimately all stakeholders in the cargo chain recognise the importance of improving data quality and penetration. Therefore, the IATA e-freight Message Improvement Programme is open to freight forwarders and airlines, regardless of their affiliation with IATA (e.g. non-IATA agents and non-IATA airlines).

An airline can be considered as participating when it is providing complete and accurate summary and detailed FHL/FWB shipment data on a monthly basis (15th of the month) to IATA. Airline participants in the IATA e-freight Message Improvement Programme, will send FSU messages with RCS/RCF/DEP status, or the agreed equivalents, to freight forwarders in exchange for correct and accurate FWB messages.

A forwarder can be considered as participating when it has nominated a central point of contact and agreed to put in place an action plan to fix issues identified by analysis of the reports provided by the MIP.

5.1 Airlines Improved message quality is a pre-requisite for e-freight and or e-AWB implementation. Without complete and accurate messages, e-freight or e-AWB is not viable. However, there are also direct and immediate benefits to be achieved by improving message quality. Once airlines determine their baseline performance they


should develop business cases to evaluate the financial benefit associated with improved message performance. Direct benefits for the airline can come from:

Reduced cost of Air Waybill/House Air Waybill data entry for which no FWB/FHL has been supplied.

Reduced cost of amending incorrect FWB/FHL data

Reduced message costs for rejected FWB/FHL messages and duplicate FWB/FHL messages

Advantages of receiving correct FWB/FHL data in advance of the physical document:

Reduction in Customs fines caused by incorrect FWB/FHL data

Aspects of Customer Service, which are impacted by receipt of incorrect FWB/FHL data

Costs for an airline participating in the IATA e-freight programme will come from:

Development of the monthly shipment data generation required by IATA.

Increased message costs through increased penetration and FSU messaging

Resource costs analysing and addressing problems

5.2 Forwarders As above, improved message quality is a pre-requisite for e-freight or e-AWB implementation. Without complete and accurate messages, e-freight or e-AWB is not viable for the forwarder.

Airline participants in the IATA e-freight Message Improvement Programme, will send FSU messages with RCS/RCF/DEP status, or the agreed equivalents, to freight forwarders in exchange for correct and accurate FWB messages.

This has advantages for both the forwarder and the airline in that:

The Forwarder does not need to phone the airline constantly for status updates

Airline does not need to spend time answering queries

Many forwarders have expressed the desire to remove the need to deliver the AWB/HAWB to the airline. This can only be done if the FWB/FHL messages are complete and accurate.


6 Message Improvement Methodology

6.1 Baseline Measurement The first stage is to identify the starting point and baseline where the industry is in terms of the quality and message penetration for FWBs and FHLs. To do this, message recipients taking part in the programme submit to IATA the following baseline measurement:

1. Total number of messages required (to achieve 100% coverage).

2. Total number of messages received

3. Total number of messages rejected because of syntax failures

4. Total number of messages containing invalid business data

5. Total number of duplicates.

This information is collated by IATA and set as the baseline for each airline. As well, this information is used to set the global and regional baselines.

6.2 Root Cause Analysis IATA consolidates data on a monthly basis and sends the details to the message originator and recipient for root cause analysis.

When carrying out the root cause analysis, the message originators and recipients review the evidence and establish why the problem has occurred, taking into account all dependencies.

The activities for Root Cause Analysis are:

Determine the problem

Determine the actions required to solve the problem

Determine the owner of the actions

Determine the target date for completion of the actions

6.3 Improve Quality and Increase Penetration The responsibility to improve messaging performance lies with the participating Airlines and Forwarders. IATA consolidates the information collected, best practices and lessons learned in order to publish an EDI Handbook and facilitate workshops or meetings.

For workshops or meetings,

IATA will review evidence with the message originators and recipients in advance of the meeting so that everyone is aligned. A follow up meeting / conference call can take place if required.

IATA will set up meetings with message originators and recipients, including key representatives from Business and IT departments.

IATA will invite the message originators and recipients, to meet, join the MIP (be a part of the solution) and understand why the problems are occurring, referring to the evidence.

6.4 Accurate FWB and FHL Messaging

6.4.1 FWB As far as possible, only one FWB is sent, by the forwarder, for

each and every MAWB *

The AWB data complies with the rules laid out in IATA resolution 600a.


The AWB data converted into FWB format complies with the CARGO-IMP definition of the version of the message being sent.

The FWB is not rejected by the airline or CCS due to format/syntax errors *

No changes are required to the FWB data to keep the freight moving *

6.4.2 FHL (where the airline is reporting HAWB for customs purposes) Where the Customs authority demands HAWB details be

reported by the carrier (at destination or transit point), each and every HAWB must have only one accompanying FHL message *

The HAWB data is complete and accurate and complies with the customs regulations in the country that it is to be sent to

The HAWB data converted into FHL format complies with the CARGO-IMP definition of the version of the message being sent

The FHL is not rejected by the airline or CCS due to format/syntax errors *

No changes are required to the FHL data to keep the freight moving *

* Details measured by the Message Improvement Programme


7 Governance and Organization

7.1 Governance The MIP is an integrated part of the e-freight project and is therefore covered by the e-freight project governance.

Please refer to the e-freight strategy published on http://www.iata.org/efreight for further project governance details.

7.2 Organisation Structure The IATA Manager, Cargo Business Intelligence is appointed to manage the MIP, reporting to the Director Cargo Supply Chain Management and the MIP Action Group.

The MIP Action Group is responsible for setting direction and driving the implementation of the MIP Programme amongst Airlines and Freight Forwarders. Membership of the MIP Action Group is open to e-freight stakeholders and early adopters, who have implemented the MIP measurement programme.

In the short to medium term, the MIP may identify change requirements for existing EDI messages and identify requirements for new messages. To ensure any such recommendations are addressed and incorporated into new or revised standards, the Cargo Business Intelligence has close links with the Head of IATA Cargo Business Process and Standards, who owns and manages these changes through the Cargo Services Conference mechanism.

In line with other StB projects, performance reporting will be co-ordinated centrally through the StB Programme Office.

The following organisation chart describes the governance structure:

e-freight

Advisory Group(*)

e-freight Central Action Group(*)

IATA e-freight

Product

IATA e-freight

Delivery

IATA e-freight Governance Structure

Cargo Executive

Summit(*)

Cargo Committee

Supply Chain

Advice

IATA Board of Governors and IATA

Annual General Meeting

Airline Simplifying the Business

Steering Group

e-freight

Product

e-freight Project Director

IATA e-freight

Advice

IATA

Governance

Cargo Services Conference

AdviceIATA StB

(*) Customers, Forwarders, Carriers

IATA Project Sponsors –Programme Director StB

and Global Head of Cargo

e-freight specific

e-freight MIP Action Group (*)

e-freight Vendor Action Group


7.3 e-freight MIP Action Group Person Title Company Airlines

Mr. Jan Vreeburg Director Innovations KLM

Mr. Dick Dougherty Project Manager - EDI American Airlines

Mr. Phil Jones Project Manager - Cargo Information Management British Airways

Ms. Karen Jones Manager Regulation and Cargo Quality Standards Air Canada

Mr. Albert Lo Manager Cargo Services Cathay Pacific

Ms. Silke Lehnhardt VP Process and Information Management Lufthansa Cargo

Forwarders

Mr. Michael Weber Manager Processes and Systems Kuehne and Nagel

Industry

Mr. Lothar Moehle Programme Director C2K Cargo 2000

Mr. Constantin Syridis Manager, Cargo Business Intelligence IATA

7.4 Roles and Responsibilities

7.4.1 IATA Regional Cargo Director Drive regional MIP participation and quality/penetration

improvement to meet agreed targets.

Monitor quality and penetration targets. Work with the EDI implementation manager and local cargo manager/implementation manager to drive and implement strategies for increasing penetration and quality.

Collate feedback from the field and recommend changes/updates to the MIP strategy.

7.4.2 IATA Manager Cargo Business Intelligence Manages all aspects of the Message Improvement Programme.

Drive implementation of EDI message improvement and penetration on a global basis, through the IATA StB programme management structure, StB Regional Program Managers, and IATA Cargo field resources.

Agree IATA e-freight MIP participant targets with the Regional Cargo Directors.

Develop and improve metrics measurement. Implement solutions to report improvements in penetration and quality measurement. Publish monthly metrics through StB channels.

Provides overall plan for MIP delivery, including milestones. Monitor progress against plan, identify and report exceptions and recommend remedial action.

Directly interact with key stakeholders to secure participation and support.

Drive mandatory implementation of EDI message improvement and penetration in e-freight countries as a role model for global EDI message improvement.

Escalate issues to the e-freight Central Action Group.


Identifies penetration and quality trends and wherever necessary, implements programmes or seminars to address both.

Produces the IATA e-freight MIP Handbook.

7.4.3 IATA Head of Cargo Business Processes and Standards Owns the master operating set of processes and standards.

Ensures that messaging standards are used adequately.

Internal approval changes to existing message standards or implementation of new message standards.

Lead the delivery of changes to existing standards and of new messages.

Coordinates the validation by the industry of changes to existing standards and of new messages.

Promote the standards and ensure common adoption of industry standards.

7.4.4 MIP Action Group Advise IATA e-freight MIP, review and recommend

improvements or changes to the IATA e-freight MIP Strategy.

Lead MIP in own region, attracting new airlines and forwarders.

Organising, with IATA, workshops to share best practice.

Produce updated versions of the MIP Strategy/Methodology.

Sign off the content of the IATA e-freight MIP Handbook.

7.4.5 Airline MIP Representative Responsible for ensuring the monthly shipment data is

submitted on the 15th of each month, collating any evidence, with IATA, organising meetings with local MIP Working Group.

Work with IATA e-freight representative/Local implementation manager to agree airline action plan for improving FWB/FHL penetration and quality. Sign off the plan.

Chairs local MIP Working Group Meetings.

Carry out the problem analysis for own airline and work with IATA to gather issues and evidence from other airlines. Circulate agenda, in advance of meeting.

With message originator, identify why the problems are occurring, and agree action plan for fixing problems.

Monitor and follow up on action plan.

Reports progress, issues to IATA e-freight representative.

7.4.6 Forwarder MIP Representative Carry out the problem analysis for own company, work with

message recipient, identify why the problems are occurring, and agree action plan for fixing problems. Share details of problem resolution with IATA e-freight representative for inclusion in IATA e-freight MIP progress.

Monitor and follow up on action plan.

Reports progress, issues to IATA e-freight representative.


7.4.7 IATA e-freight Representatives Drive country MIP participation and quality/penetration

improvement to meet agreed targets.

Support MIP champions, as required, in MIP stakeholder resolution meetings (Meetings where freight forwarders and airlines meet to discuss message penetration and quality issues).

Ensures an action plan is developed with each airline. Monitor quality and penetration targets for airline and country.

Work with the EDI Manager and MIP membership to drive strategies for increasing penetration and quality.

Reports issues to EDI MIP manager and Regional Cargo Director. Monitor action plan; follow up with airlines on progress of actions.

Identifies problem solutions. Reports information back to the EDI MIP Manager for inclusion in the FAQs and IATA e-freight MIP Handbook.

7.4.8 IATA StB Programme Centre Provide reporting methodology, tools and infrastructure.

Co-ordinate external and internal communication.

Provide tools and approach for global mobilisation and engagement of local IATA e-freight representatives.

7.5 IATA Cargo Standards The MIP may identify requirements to change existing Cargo-IMP messages or industry business processes. These changes may be to add or remove data elements from existing messages or to change the current mandatory / conditional / optional status of specific data elements. Changes will be processed via IATA Cargo Standards, through the Cargo Services Conference.


8 Communication

8.1 Monthly Reports On the 15th of each month, the airline MIP champion will send their monthly shipment data, relating to the previous months activity, to IATA for consolidation.

On the 20th of each month, using the airline monthly shipment data, IATA will produce a number of reports as described later in this document. These reports will be shared between participants on the MIP Extranet. IATA will also publish individual airline and forwarder statistics on a monthly basis on the airlines and forwarders private extranet page.

The industry penetration statistics will be published on the IATA Internet MIP homepage.

Further details and a description of the MIP reports can be found in Appendix B.

Additional reports might be developed over the coming months and included in the next release of this document.

8.2 Problem Resolution At the country level, as and when a problem is solved it will be communicated by the IATA e-freight representative to the EDI MIP Manager. This information will be added to the next edition of the EDI MIP handbook, which will be published on the MIP homepage.

8.3 Airline MIP Action Plans Airline MIP Action Plans will be published on the Airlines private extranet page. See Appendix D for an example of an airline action plan.

8.4 Escalation Procedure Should there be any form of dispute between the message originator and the message recipient, the issue, and the recommended resolution, will be raised, as an agenda item, by the IATA e-freight MIP Manager at the next IATA e-freight MIP Action Group Meeting.


9 Risks and Issues

9.1 Resource Requirement There is likely to be significant resource requirement associated with working to improve EDI message quality. MIP participants must be prepared to commit sufficient resource to investigate root causes of issues and to develop solutions. However, by working together as an air cargo community, economies of scale will be realised and benefits will also be maximised.

9.2 Maintaining Consistency Across Participants The variation in FWB/FHL data elements that are required for different shipments makes it difficult to develop a “one size fits all” measurement programme. Similarly, when reporting results, it is difficult to ensure consistency and to “prove” that all participants are reporting in exactly the same way. MIP participants will report their own performance to IATA for consolidation. There is a risk that different interpretations of how and what to report will arise, resulting in some stakeholders appearing to achieve better performance than others. During the initial phase of the MIP, participants will work together to eliminate such discrepancies.

However, it must also be acknowledged that the MIP is simply a mechanism to help industry to improve its own EDI message performance. There is nothing to be gained by participants overstating performance; since the true test of success is that a stakeholder has sufficient confidence in the data to remove the paper documents from its operating processes

9.3 Adding Complexity There is a risk that the measurement criteria of “whatever data elements the recipient requires” will add complexity to the freight forwarders’ business, with different airlines requiring different data elements for different shipments, resulting in forwarders having to bespoke their systems to meet these varying demands. The MIP must strive to deliver simplicity and standardisation of requirements, as this will contribute greatly to the ability of forwarders to achieve consistency of performance.


10 Appendix A - MIP Input - Airline and CCS Monthly Data Files

10.1 Airline Data to Submit to IATA Each participating airline must submit to IATA no later than the 15th of the month four CSV (Comma Separated Values) data files providing shipment data for the previous month.

1. FWB Summary Data: CSV file showing the total number of consignments, messages received, messages rejected and messages corrected.

2. FHL Summary Data: CSV file showing the total number of shipments, messages received, messages rejected and messages corrected.

3. FWB Detailed Data: CSV file showing one record for each consignment, including the AWB number, the number of messages received, the forwarder and up to 3 errors.

4. FHL Detailed Data: CSV file showing one record for each shipment, including the AWB and HAWB numbers, the number of messages received, the forwarder and up to 3 errors.

The file formats specifications for the above are described later in this document.

10.2 Optional CCS Data to Submit to Airlines Optionally, CCSs (Cargo Community Systems) can be required by the participating airlines to provide them the following four CSV data files:

1. FWB Summary Data: CSV file showing the number of messages received and messages rejected by the CCS the previous month.

2. FHL Summary Data: CSV file showing the number of messages received and messages rejected by the CCS for the previous month.

3. FWB Detailed Data: CSV file showing one record for each consignment for which all messages have been rejected by the CCS.

4. FHL Detailed Data: CSV file showing one record for each shipment for which all messages have been rejected by the CCS.

To simplify data consolidation, the data files from the CCS to airlines have exactly the same format as the ones from the airlines to IATA. They have to be consolidated by the airline so that IATA receives only one set of 4 files from the airline (that contains both the airline’s and the CCS data). While the file format is the same for CCS or airline data, there are differences in what data has to be provided which is described later in this document.

For airlines, getting this data from the CCS is optional as the rejection rate from CCS is usually low. However, in the case a high number of messages are suspected to be rejected by CCSs (and therefore never reaching the airline), it is recommended the airline gets the above data from the CCS so that the causes of rejections can be better understood through MIP reporting and acted upon.


10.3 Recommended Data Reporting Sequence If an airline can’t provide the full data set as required for MIP upon joining, it is recommended the airline starts providing data in the following sequence:

1. Provide summary FWB data from own system.

2. Provide summary FHL data from own system.

3. Provide detailed FWB data from own system.

a. Start providing all consignment data with the count of messages received, including consignments for which no messages have been received, e-freight consignments (EAP/EAW) and e-AWB consignments (EDI), no error codes to report. This allows addressing message and e-freight penetration issues.

b. Implement the reporting of syntax and rejection error codes that are mandatory for e-freight (described later in this document). From this point, it allows addressing message quality issues.

c. Implement the reporting of other data error codes that are mandatory for e-freight (described later in this document).

d. Implement the reporting of all other remaining error codes that are optional for e-freight (described later in this document).

4. Provide detailed FHL data from own system.

a. Start providing all shipment data with the count of messages received, including shipments for which no messages have been received and e-freight shipments (EAP/EAW), no error codes to report. This allows addressing message and e-freight penetration issues.

b. Implement the reporting of syntax and rejection error codes that are mandatory for e-freight (described later in this document). From this point, it allows addressing message quality issues.

c. Implement the reporting of other data error codes that are mandatory for e-freight (described later in this document).

d. Implement the reporting of all other remaining error codes that are optional for e-freight (described later in this document).

5. Get the summary FWB and FHL data from the CCS system and integrate it into your own summary files.

6. Get the detailed FWB and FHL data from the CCS system and integrate it into your own detailed files.


10.4 Monthly Data Flow This illustrates the monthly data flow between CCS (optional), airlines and IATA.

CCS Airline IATA

FWB Summary DataCSV file

FHL Summary DataCSV file

FWB Detailed DataCSV file

FHL Detailed DataCSV file

FWB Summary DataCSV file

FHL Summary DataCSV file

FWB Detailed DataCSV file

FHL Detailed DataCSV file

IndustryReports

AirlineReports

ForwarderReports

Including CCS data

Including CCS data

Including CCS data

Including CCS data

Optional To be received by IATA bythe 15th of the month

Reports to be distributedby the 20th of the month

10.5 CSV File Format The CSV file format (Comma Separated Values) is an IT industry standard file format for data exchange that is easy to work with and directly supported by many applications such as MS Excel, MS Access and most database systems.

The syntax that is required for the MIP data files submitted by airlines is as follows:

Name the files exactly as specified. The file naming is important to be strictly followed as it allows MIP to correctly identify each file received from every participant and correctly import the data into the database.

One record header line to be shown within each CSV file (as the first record) with all field names to be enclosed by double quotes (“field name”), not single quotes (‘field name’).

Use double quotes (“data”) to enclose every data field (text, numbers, dates) so as to allow commas to be part of the data without the risk of corrupting or shifting other fields.

Use commas (,) as the field separator, not semicolon (;).

The count and order of the fields in each of the 4 files should exactly match the specifications laid out in this document, i.e.

Seven fields for the summary files (both FWB and FHL)

Thirteen fields for the FWB detailed files

Fourteen fields for the FHL detailed files

Use only standard ANSI coding / single-byte (no Unicode / double-byte) in order to keep the size of files as small as possible.


10.6 FWB Summary File This file contains the totals for consignments and FWB activity over the previous month.

10.6.1 File Name The file name format for the airline to IATA file is as follows: XXYYYYMMFWBSUM.CSV

Where:

XX = replace by your airline 2-letter code

YYYY = replace by the reporting year in 4 digits

MM = replace by the reporting month in 2 digits with a leading zero if needed

FWB = the message type

SUM = summary file

Examples:

KL200709FWBSUM.CSV

BA200711FWBSUM.CSV

The file name format for the CCS to airline file should be the same as above with the name of the CCS followed by an underscore (_) as a prefix.

Examples:

Traxon_KL200709FWBSUM.CSV

GLSHK_BA200711FWBSUM.CSV

10.6.2 Fields Description Field

# Field name Description Mandatory Format Length Comments

1 Report Airline to IATA file: AWB/FWB

CCS to airline file: Name of CCS followed by FWB

Yes Text 50

2 Messages Expected

Airline to IATA file: the total number of consignments for which an FWB is expected to be received in the reported month. Note for e-freight only one message is expected to be received for each consignment.

CCS to airline file: leave blank (only the airline can provide what is expected including the consignments for which no messages were received)

Yes for dataprovided by the airline

Number 9 No decimals or thousands separators or any other non-numeric character

3 Messages Received

The total number of FWB messages received (including the messages rejected, the messages with invalid data or syntax and duplicate messages).

Yes Number 9 No decimals or thousands separators or any other non-numeric character


Field #

Field name Description Mandatory Format Length Comments

4 Messages rejected by CCS

CCS to airline file: the total number of FWB messages that rejected by the CCS because of syntax or other errors, therefore never reaching the airline. The assumption is that the CCS returns an FNA to the sender.

Airline to IATA file: the number of messages rejected by the CCS (as provided by the CCS)

Yes for dataprovided by

the CCS


5 Messages rejected by Airline

Airline to IATA file: the total number of FWB messages rejected by the Airline because of syntax or data errors.

CCS to airline file: leave blank



6 Messages with Invalid Business Data

Airline to IATA file: the total number of FWB messages that contain invalid data but are accepted and / or corrected by the airline. CCS to airline file: leave blank (airline is providing the count)



7 Duplicate Message Count

The total number of duplicate messages received. An FWB message is considered to be a duplicate if it has the same Air Waybill numberas a previously received FWB. E.g. same FWB received twice, duplicate count is 1, same FWB received again, duplicate count is 2. CCS to airline file: leave blank (airline is providing the duplicate count)



10.6.3 Data Records to Include This file should only show one record of data with total figures as described above.

For the airline to IATA file, all consignments should be taken into consideration, including those for which no messages were received.

For the CCS to airline file, all messages received should be taken into the count.

10.6.4 Sample Data When the CSV file is opened using a spreadsheet (e.g. MS Excel) or imported into a database (e.g. MS Access), the data should look like this:

Report Messages Expected

Messages Received

Messages rejected by CCS

Messages rejected by Airline

Messages with Invalid Business Data

Duplicate Message Count

AWB/FWB 123456 111111 999 2222 33333 44444

10.6.5 Sample File Dump When opened using a text editor (e.g. Notepad), the CSV file should look like this:

"Report","Messages Expected","Messages Received","Messages rejected by CCS","Messages rejected by Airline","Messages with Invalid Business Data","Duplicate Message Count"

"AWB/FWB","123456","111111","999","2222","33333","44444"


10.7 FHL summary file This file contains the totals for shipments and FHL activity over the previous month.

10.7.1 File Name The file name format for the airline to IATA file is as follows: XXYYYYMMFHLSUM.CSV

Where:




FHL = the message type

SUM = summary file

Examples:

KL200709FHLSUM.CSV

BA200711FHLSUM.CSV


Examples:

Traxon_KL200709FHLSUM.CSV

GLSHK_BA200711FHLSUM.CSV

10.7.2 Fields Description Field

# Field name Description Mandatory Format Length Comments

1 Report Airline to IATA file: HAWB/FHL

CCS to airline file: Name of CCS followed by FHL

Yes Text 50

2 Messages Expected

Airline to IATA file: the total number of shipments for which an FHL is expected to be received in the reported month. Note for e-freight only one message is expected to be received for each shipment.

FHLs are not expected to be received for every shipment but at least for cross-border shipments where customs need to receive advance information, like for the US, Canada, India and other countries. As the number of countries is growing, you must check what is expected with your cargo operations services.

CCS to airline file: leave blank (only the airline can provide what is expected including the shipments for which no messages were received)



3 Messages Received

The total number of FHL messages received (including the messages rejected, the messages with invalid data or syntax and duplicate messages).

Yes Number 9 No decimals or thousands separators or any other non-numeric character


Field #

Field name Description Mandatory Format Length Comments

4 Messages rejected by CCS

CCS to airline file: the total number of FHL messages rejected by the CCS because of syntax or other errors, therefore never reaching the airline. The assumption is that the CCS returns an FNA to the sender.

Airline to IATA file: the number of messages rejected by the CCS (as provided by the CCS)

Yes for dataprovided by

the CCS


5 Messages rejected by Airline

Airline to IATA file: the total number of FHL messages rejected by the Airline because of syntax or data errors.

CCS to airline file: leave blank



6 Messages with Invalid Business Data

Airline to IATA file: the total number of FHL messages that contained invalid data but were accepted and / or corrected by the airline. CCS to airline file: leave blank (airline is providing the count)



7 Duplicate Message Count

The total number of duplicate messages that were received. An FHL message is considered to be a duplicate if it has the same Air Waybill number and House Waybill number as a previously received FHL. E.g. same FHL received twice, duplicate count is 1, same FHL received again, duplicate count is 2.

CCS to airline file: leave blank (airline is providing the duplicate count)



10.7.3 Data Records to Include This file should only show one record of data with total figures as described above.

For the airline to IATA file, all shipments should be taken into consideration, including those for which no messages were received.

For the CCS to airline file, all messages received should be taken into the count.


Report Messages Expected

Messages Received

Messages rejected by CCS

Messages rejected by Airline

Messages with Invalid Business Data

Duplicate Message Count

House AWB/FHL 12345 1234 123 456 789 1011


"Report","Messages Expected","Messages Received","Messages rejected by CCS","Messages rejected by Airline","Messages with Invalid Business Data","Duplicate Message Count"

"House AWB/FHL","12345","1234","123","456","789","1011"


10.8 FWB detail file This file contains the detail for all consignments and FWBs received over the previous month.

10.8.1 File Name The file name format for the airline to IATA file is as follows: XXYYYYMMFWBDET.CSV

Where:





DET = detail file

Examples:

KL200709FWBDET.CSV

BA200711FWBDET.CSV


Examples:

Traxon_KL200709FWBDET.CSV

GLSHK_BA200711FWBDET.CSV

10.8.2 Fields Description Field Field name Description Mandatory Format Length Comments

1 Awb Date Date of execution of shipment Yes DD/MM/YY with leading zeroes where necessary

8 Year with 2 digits only

2 Awb Num AWB number Yes 11 numbers only, no spaces, punctuations or special signs. Leading zeroes if necessary.

11

3 Awb Orig Sta Cde Airport code to be taken from the FWB. If no FWB received, to be taken from AWB.

Yes XXX - 3 letters uppercase 3

4 Awb Dest Sta Cde Airport code to be taken from the FWB. If no FWB received, to be taken from AWB.


5 Error Code 1 No XXX99C 6


7 Error Code 3

Error code as defined for MIP reporting.

The airline is at liberty to prioritise and report the top 3 error codes in accordance with those it feels are most important.

No XXX99C 6

Note the old format XXX9999 is still supported

8 Remarks To be used for indicating EAP or EAW for e-freight shipments, EDI for e-AWB shipments and any

No Free text format 65 “EAP”, “EAW” or “EDI” to be separated at least by spaces from any other


Field Field name Description Mandatory Format Length Comments

other text to be communicated to forwarders who receive MIP reports. As of 1st April 2008, e-freight participant airlines are required to provide the following values in this field: “EAW” code to indicate “e-freight Consignment with No Accompanying Paper Documents”

“EAP” code to indicate “e-freight Consignment with Accompanying Paper Documents”

This data will be used to measure the penetration of full and partial e-freight shipments. As of June 2010 e-AWB participants airlines are required to provide the following values in the remarks field:

“EDI” code to indicate “e-AWB shipments”

This data will be used to measure the penetration of e-AWB shipments.

text.

9 No of FWBs received

Count of FWBs received for this consignment. 0 if no FWB received for this consignment.

Yes 4 digit number, no decimal point or thousands separator

4

10 Agent IATA Number

To be obtained from FWB if available, else from AWB. If Agent does not have an IATA code, then provide the airline's unique id for this agent, prefixed with the 2-letter airline code.

Yes Agent with IATA code: IATA code with 7 numbers and leading zeroes as necessary.

Agent without IATA code: XX999999

where XX is your airline code and 999999 (up to 18 characters) is your unique internal number / code for the agent.

20 Agents with IATA code:

7 characters for IATA Agent numbers e.g. 0123456

Agent without IATA code:20 characters for non-IATA Agent, prefixed withairline's 2-letter code, e.g. BA123456789

11 Agent IATA CASS address

To be obtained from FWB if available, else from AWB. If Agent does not have an IATA code, then leave blank.

No 4 numbers with leading zeroes if necessary.

4

12 Agent Name To be obtained from FWB if available, else from the AWB in the Airline's system.

No Text 100



13 CCS Record Provider

Name of CCS who provided the record.

Yes if record is provided by CCS

Text 20

10.8.3 Data Records to Include This file should show one record of data for each consignment done the previous month. If the file combines the airline’s and the CCS data, then there might be some consignments appearing more than once (e.g. shown as consignments with no messages received by the airline and shown as FWBs rejected by the CCS).

For the airline to IATA file, all consignments should be taken into consideration, including those for which no messages were received.

For the CCS to airline file, only the messages that have been rejected by the CCS should be shown.


Awb Date Awb Num

Awb Orig Sta Cde

Awb Dest Sta Cde

Error Code 1

Error code 2

Error code 3 Remarks

No of FWBs received

Agent IATA Number

Agent IATA CASS address Agent Name

CCS Record Provider

31/12/07 01234567890 GVA HKG FWB00 CNE01 1 0123456 0123

INTERGALACTIC TRANSPORT CO., LTD.

30/12/07 01234567890 HKG AMS 0 1234567 0001 PAN-COSMIC SHIPPING ULTD.

29/12/07 01234567890 YVR YYZ MSG00 2 4567890 0002 INTRA SOLAR CARGO CORP. CCS1

28/12/07 01234567890 AMS ATH MSG01 EAW 99 0123456 9999 ASTRO LOGISTICS INC. CCS2

01/09/07 01234567890 AMS ATH MSG02 EAP 1 0123456 BLACK HOLE SHIPPERS & CO. CCS3

01/09/07 01234567890 MSP CDG EDI BLACK HOLE SHIPPERS & CO CCS3

01/09/07 01234567890 MSP CDG EAW EDI BLACK HOLE SHIPPERS & CO CCS3


"Awb Date","Awb Num","Awb Orig Sta Cde","Awb Dest Sta Cde","Error Code 1","Error code 2","Error code 3","Remarks","No of FWBs received","Agent IATA Number","Agent IATA CASS address","Agent Name","CCS Record Provider"

"31/12/07","01234567890","GVA","HKG","FWB0010","","","","1","0123456","0123","INTERGALACTIC TRANSPORT CO., LTD.",""

"30/12/07","01234567890","HKG","AMS","","","","","0","1234567","0001","PAN-COSMIC SHIPPING ULTD.",""


"29/12/07","01234567890","YVR","YYZ","FLT0010","FWB0015","","","2","4567890","0002","INTRA SOLAR CARGO CORP.","CCS1"

Sample Message for e-freight Consignment with No Accompanying Paper Documents

"28/12/07","01234567890","AMS","ATH","FWB0010","","","EAW","99","0123456","9999","ASTRO LOGISTICS INC.","CCS2"

Sample Message for e-freight Consignment with Accompanying Paper Documents

"07/07/07","01234567890","AMS","ATH","","","","EAP","1","0123456","","BLACK HOLE SHIPPERS & CO.","CCS3"

Sample Message for e-AWB Consignments

"07/07/07","01234567890","MSP","CDG","","","","EDI","1","0123456","","BLACK HOLE SHIPPERS & CO.","CCS3"

Sample Message for e-AWB Consignments "07/07/07","01234567890","MSP","CDG","","","","EAW EDI","1","0123456","","BLACK HOLE SHIPPERS & CO.","CCS3"

10.9 FHL detail file This file contains the detail for all consignments and FWBs received over the previous month.

10.9.1 File Name The file name format for the airline to IATA file is as follows: XXYYYYMMFHLDET.CSV

Where:





DET = detail file

Examples:

KL200709FHLDET.CSV

BA200711FHLDET.CSV


Examples:

Traxon_KL200709FHLDET.CSV

GLSHK_BA200711FHLDET.CSV


10.9.2 Fields Description Field Field name Description Mandatory Format Length Comments

1 Awb Date Date of execution of shipment. Yes DD/MM/YY with leading zeroes where necessary.

8 Year with 2 digits only

2 Awb Num AWB number Yes 11 numbers only, no spaces, punctuations or special signs. Leading zeroes if necessary.

11

3 Hawb Num HAWB number Yes As it appears on FHL or as captured in Airline's system.

20

4 Awb Orig Sta Cde Airport code to be taken from FHL MAWB consignment (MBI) details. If no FHL received, to be taken from HAWB details from the airline system.


5 Awb Dest Sta Cde Airport code to be taken from FHL MAWB consignment (MBI) details. If no FHL received, to be taken from HAWB details from the airline system.


6 Error Code 1 No XXX99C 7 Note the old format XXX9999 is still supported


8 Error Code 3

Error code as defined for MIP reporting.

The airline is at liberty to prioritise and report the top 3 error codes in accordance with those it feels are most important.

No XXX99C 7

9 Remarks To be used for indicating EAP or EAW e-freight shipments or any other text to be communicated to forwarders who receive MIP reports.

No Free text format 65

10 No of FHLs received

Count of FHLs received. 0 if no FHL received.

Yes 4 digit number, no decimal point or thousands separator

4

11 Agent IATA Number

To be obtained from FWB if available, else from AWB. If Agent does not have an IATA code, then provide the airline's unique id for this agent, prefixed with the 2-letter airline code.

Yes Agent with IATA code: IATA code with 7 numbers and leading zeroes as necessary.

Agent without IATA code: XX999999

where XX is your airline code and 999999 (up to 18 characters) is your unique internal number /

20 Agents with IATA code: 7 characters for IATA Agent numbers e.g. 0123456

Agent without IATA code:20 characters for non-IATA Agent, prefixed withairline's 2-letter code, e.g. BA123456789



code for the agent.

12 Agent IATA CASS address

To be obtained from FWB if available, else from AWB. If Agent does not have an IATA code, then leave blank.

No 4 numbers with leading zeroes if necessary.

4

13 Agent Name To be obtained from FWB if available, else from the AWB in the Airline's system.

No Text 100

14 CCS Record Provider

Name of CCS who provided the record.

Yes if record is provided by CCS

Text 20

10.9.3 Data Records to Include This file should show one record of data for each shipment done the previous month. If the file combines the airline’s and the CCS data, then there might be some shipments appearing more than once (e.g. shown as shipment with no messages received by the airline and shown as FHLs rejected by the CCS).

For the airline to IATA file, all shipments should be taken into consideration, including those for which no messages were received.

For the CCS to airline file, only the messages that have been rejected by the CCS should be shown.


Awb Date Awb Num Hawb Num

Awb Orig Sta Cde

Awb Dest Sta Cde

Error Code 1

Error code 2

Error code 3 Remarks

No of FHLs received

Agent IATA Number

Agent IATA CASS address Agent Name

CCS Record Provider

31/12/07 01234567890 ABC1234567 GVA HKG AWB01 CNE01 1 0123456 0123

INTERGALACTIC TRANSPORT CO., LTD.

30/12/07 01234567890 01234567 HKG AMS 0 1234567 0001 PAN-COSMIC SHIPPING ULTD.

29/12/07 01234567890 ABC1234567 YVR YYZ MSG00 2 4567890 0002 INTRA SOLAR CARGO CORP. CCS1

28/12/07 01234567890 01234567 AMS ATH MSG01 99 0123456 9999 ASTRO LOGISTICS INC. CCS2

07/07/07 01234567890 01234567 AMS ATH MSG02 1 0123456 BLACK HOLE SHIPPERS & CO. CCS3


"Awb Date","Awb Num","Hawb Num","Awb Orig Sta Cde","Awb Dest Sta Cde","Error Code 1","Error code 2","Error code 3","Remarks","No of FHLs received","Agent IATA Number","Agent IATA CASS address","Agent Name","CCS Record Provider"


"31/12/07","1234567890","ABC1234567","GVA","HKG","FHL00","CNE00","","","1","123456","0123","INTERGALACTIC TRANSPORT CO., LTD.",""

"30/12/07","1234567890","1234567","HKG","AMS","","","","","0","1234567","1","PAN-COSMIC SHIPPING ULTD.",""

"29/12/07","1234567890","ABC1234567","YVR","YYZ","MSG01","","","","2","4567890","0002","INTRA SOLAR CARGO CORP.","CCS1"

"28/12/07","1234567890","1234567","AMS","ATH","MSG01","","","","99","123456","9999","ASTRO LOGISTICS INC.","CCS2"

"07/07/07","1234567890","1234567","AMS","ATH","MSG01","","","","1","123456","","BLACK HOLE SHIPPERS & CO.","CCS3"

MIP Strategy version 4 © Copyright IATA 2007-2009

11 Appendix B - MIP Output - Monthly Reporting

11.1 Report 1 - Industry Report - Overall Industry FWB Quality and Penetration Based on the data submitted by the airlines, IATA will produce the following report. It is important to note, that if the report data is not submitted by the airline on the 15th of the month, then their specific data will not be included in the overall statistics, which could have an adverse affect on the industry statistics.

A: M

ON

TH

b: T

otal

# o

f Shi

pmen

ts

c: P

enet

ratio

n

d: %

Pen

etra

tion

e:%

Tar

get

f:% V

aria

nce

g:D

uplic

ates

h:%

Dup

licat

es

i: %

Tar

get

j:% V

aria

nce

k: M

essa

ges

reje

cted

by

CC

S

l% M

essa

ges

reje

cted

by

CC

S

m: %

Tar

get

n:%

Var

ianc

e

o: M

essa

ges

reje

cted

by

Airl

ine

p:%

Mes

sage

s re

ject

ed

by A

irlin

e R

ejec

tions

q: %

Tar

get

r:%

Var

ianc

e

s:Bu

sine

ss D

ata

Inva

lid

t:%B

usin

ess

Dat

a In

valid

u: %

Tar

get

v:%

Var

ianc

e

MAR06 5,000,000 2,500,000 50% 50% 0% 500,000 20% 10% 10% 500,000 10% 10% 0% 500,000 10% 10% 0% 500,000 10% 23% -13%

APR06 5,500,000 2,875,000 52% 51% 1% 499,990 17% 9% 8% 499,990 9% 9% 0% 499,990 9% 9% 0% 499,990 9% 15% -6%

MAY06 6,050,000 3,306,250 55% 52% 3% 499,980 15% 8% 7% 499,980 8% 8% 0% 499,980 8% 8% 0% 499,980 8% 14% -6%

JUN06 6,655,000 3,802,188 57% 53% 5% 499,970 13% 8% 5% 499,970 8% 8% 0% 499,970 8% 8% 0% 499,970 8% 11% -3%

JUL06 7,320,500 4,372,516 60% 53% 6% 499,960 11% 7% 4% 499,960 7% 7% 0% 499,960 7% 7% 0% 499,960 7% 10% -3%

AUG06 8,052,550 5,028,393 62% 54% 8% 499,950 10% 6% 4% 499,950 6% 6% 0% 499,950 6% 6% 0% 499,950 6% 9% -3%

SEP06 8,857,805 5,782,652 65% 55% 10% 499,940 9% 6% 3% 499,940 6% 6% 0% 499,940 6% 6% 0% 499,940 6% 8% -2%

OCT06 9,743,586 6,650,050 68% 56% 12% 499,930 8% 6% 2% 499,930 5% 5% 0% 499,930 5% 5% 0% 499,930 5% 7% -2%

NOV06 10,717,944 7,647,557 71% 57% 15% 499,920 7% 5% 2% 499,920 5% 5% 0% 499,920 5% 5% 0% 499,920 5% 6% -1%

DEC06 11,789,738 8,794,691 75% 60% 15% 499,910 6% 4% 2% 499,910 4% 4% 0% 499,910 4% 4% 0% 499,910 4% 5% -1%

JAN07 12,968,712 10,113,894 78% 62% 16% 499,900 5% 4% 1% 499,900 4% 4% 0% 499,900 4% 4% 0% 499,900 4% 4% 0%

FEB07 14,265,584 11,630,978 82% 63% 19% 499,890 4% 4% 0% 499,890 4% 4% 0% 499,890 4% 4% 0% 499,890 4% 3% 1%

MAR07 15,692,142 13,375,625 85% 64% 21% 499,880 4% 3% 1% 499,880 3% 3% 0% 499,880 3% 3% 0% 499,880 3% 2% 1%


This report is an analysis of the overall FWB Quality and performance and is constructed by using the aggregated data contained in the FWB summary reports submitted each month by airlines participating in the IATA e-freight MIP programme.

Each row of the report details, for the month, the total of the actual industry figures submitted by all airlines relating to that specific measure. The figures relating to Penetration, Duplicates, Messages rejected by CCS, Messages rejected by Airline and Business Data Invalid are calculated as a percentage of the aggregated total messages received by the airlines. Variance against the targets, which will eventually be set at the industry level are calculated and also included in the report.

The above report will be produced on a monthly basis, will be available on the extranet, and contains the following elements:

a) Month

b) The total number of shipments

c) Penetration (= messages received – duplicates – messages rejected)

d) % Penetration (vs. messages expected)

e) % Target

f) %Variance

g) Duplicates

h) % Duplicates (vs. messages received)

i) % Target

j) %Variance

k) Syntax errors

l) % Syntax errors (vs. messages received)

m) % Target

n) %Variance

o) Airline rejections

p) % Airline rejections (vs. messages received)

q) % Target

r) %Variance

s) Business data invalid

t) % Business Data Invalid (vs. messages received)

u) % Target

v) %Variance


11.2 Report 2 - Industry Report - Overall Industry FHL Quality and Penetration Based on the data submitted by the airlines, IATA will produce the following report. It is important to note, that if the report data is not submitted by the airline on the 15th of the month, then this report will not be available to the airline and the error data, from that specific airline, will not be available to the forwarder.

A: M

ON

TH

b: T

otal

# o

f Shi

pmen

ts

c: P

enet

ratio

n

d: %

Pen

etra

tion

e:%

Tar

get

f:% V

aria

nce

g:D

uplic

ates

h:%

Dup

licat

es

i: %

Tar

get

j:% V

aria

nce

k: M

essa

ges

reje

cted

by

CC

S

l% M

essa

ges

reje

cted

by

CC

S m

: % T

arge

t

n:%

Var

ianc

e

o: M

essa

ges

reje

cted

by

Airl

ine

p:%

Mes

sage

s re

ject

ed b

y A

irlin

e R

ejec

tions

q:

% T

arge

t

r:%

Var

ianc

e

s:Bu

sine

ss D

ata

Inva

lid

t:%B

usin

ess

Dat

a In

valid

u: %

Tar

get

v:%

Var

ianc

e

MAR06 5,000,000 2,500,000 50% 50% 0% 500,000 20% 10% 10% 500,000 10% 10% 0% 500,000 10% 10% 0% 500,000 10% 23% -13%

APR06 5,500,000 2,875,000 52% 51% 1% 499,990 17% 9% 8% 499,990 9% 9% 0% 499,990 9% 9% 0% 499,990 9% 15% -6%

MAY06 6,050,000 3,306,250 55% 52% 3% 499,980 15% 8% 7% 499,980 8% 8% 0% 499,980 8% 8% 0% 499,980 8% 14% -6%

JUN06 6,655,000 3,802,188 57% 53% 5% 499,970 13% 8% 5% 499,970 8% 8% 0% 499,970 8% 8% 0% 499,970 8% 11% -3%

JUL06 7,320,500 4,372,516 60% 53% 6% 499,960 11% 7% 4% 499,960 7% 7% 0% 499,960 7% 7% 0% 499,960 7% 10% -3%

AUG06 8,052,550 5,028,393 62% 54% 8% 499,950 10% 6% 4% 499,950 6% 6% 0% 499,950 6% 6% 0% 499,950 6% 9% -3%

SEP06 8,857,805 5,782,652 65% 55% 10% 499,940 9% 6% 3% 499,940 6% 6% 0% 499,940 6% 6% 0% 499,940 6% 8% -2%

OCT06 9,743,586 6,650,050 68% 56% 12% 499,930 8% 6% 2% 499,930 5% 5% 0% 499,930 5% 5% 0% 499,930 5% 7% -2%

NOV06 10,717,944 7,647,557 71% 57% 15% 499,920 7% 5% 2% 499,920 5% 5% 0% 499,920 5% 5% 0% 499,920 5% 6% -1%

DEC06 11,789,738 8,794,691 75% 60% 15% 499,910 6% 4% 2% 499,910 4% 4% 0% 499,910 4% 4% 0% 499,910 4% 5% -1%

JAN07 12,968,712 10,113,894 78% 62% 16% 499,900 5% 4% 1% 499,900 4% 4% 0% 499,900 4% 4% 0% 499,900 4% 4% 0%

FEB07 14,265,584 11,630,978 82% 63% 19% 499,890 4% 4% 0% 499,890 4% 4% 0% 499,890 4% 4% 0% 499,890 4% 3% 1%

MAR07 15,692,142 13,375,625 85% 64% 21% 499,880 4% 3% 1% 499,880 3% 3% 0% 499,880 3% 3% 0% 499,880 3% 2% 1%


This report is an analysis of the overall FHL Quality and performance and is constructed by using the aggregated data contained in the FHL summary reports submitted each month by airlines participating in the IATA e-freight MIP programme.

Each row of the report details, for the month, the total of the actual industry figures submitted by all airlines relating to that specific measure. The figures relating to Penetration, Duplicates, Messages rejected by CCS, Messages rejected by Airline and Business Data Invalid are calculated as a percentage of the aggregated total messages received by the airlines. Variance against the targets for each month, which will eventually be set at the industry level are calculated and also included in the report.


a) Month




e) % Target

f) %Variance

g) Duplicates


i) % Target

j) %Variance

k) Syntax errors


m) % Target

n) %Variance



q) % Target

r) %Variance



u) % Target

v) %Variance


11.3 Report 3 - Airline Report - FWB Quality and Penetration Based on the data submitted by the airlines, IATA will produce the following report. It is important to note, that if the report data is not submitted by the airline on the 15th of each month, then the line for the month that the data has not been submitted will be left blank.

A: M

ON

TH

b: T

otal

# o

f Shi

pmen

ts

c: P

enet

ratio

n

d: %

Pen

etra

tion

e:%

Tar

get

f:% V

aria

nce

g:D

uplic

ates

h:%

Dup

licat

es

i: %

Tar

get

j:% V

aria

nce

k: M

essa

ges

reje

cted

by

CC

S

l% M

essa

ges

reje

cted

by

CC

S m

: % T

arge

t

n:%

Var

ianc

e

o: M

essa

ges

reje

cted

by

Airl

ine

p:%

Mes

sage

s re

ject

ed

by A

irlin

e R

ejec

tions

q:

% T

arge

t

r:%

Var

ianc

e

s:Bu

sine

ss D

ata

Inva

lid

t:%B

usin

ess

Dat

a In

valid

u:

% T

arge

t

v:%

Var

ianc

e

MAR06 5,000,000 2,500,000 50% 50% 0% 500,000 20% 10% 10% 500,000 10% 10% 0% 500,000 10% 10% 0% 500,000 10% 23% -13%

APR06 5,500,000 2,875,000 52% 51% 1% 499,990 17% 9% 8% 499,990 9% 9% 0% 499,990 9% 9% 0% 499,990 9% 15% -6%

MAY06 6,050,000 3,306,250 55% 52% 3% 499,980 15% 8% 7% 499,980 8% 8% 0% 499,980 8% 8% 0% 499,980 8% 14% -6%

JUN06 6,655,000 3,802,188 57% 53% 5% 499,970 13% 8% 5% 499,970 8% 8% 0% 499,970 8% 8% 0% 499,970 8% 11% -3%

JUL06 7,320,500 4,372,516 60% 53% 6% 499,960 11% 7% 4% 499,960 7% 7% 0% 499,960 7% 7% 0% 499,960 7% 10% -3%

AUG06 8,052,550 5,028,393 62% 54% 8% 499,950 10% 6% 4% 499,950 6% 6% 0% 499,950 6% 6% 0% 499,950 6% 9% -3%

SEP06 8,857,805 5,782,652 65% 55% 10% 499,940 9% 6% 3% 499,940 6% 6% 0% 499,940 6% 6% 0% 499,940 6% 8% -2%

OCT06 9,743,586 6,650,050 68% 56% 12% 499,930 8% 6% 2% 499,930 5% 5% 0% 499,930 5% 5% 0% 499,930 5% 7% -2%

NOV06 10,717,944 7,647,557 71% 57% 15% 499,920 7% 5% 2% 499,920 5% 5% 0% 499,920 5% 5% 0% 499,920 5% 6% -1%

DEC06 11,789,738 8,794,691 75% 60% 15% 499,910 6% 4% 2% 499,910 4% 4% 0% 499,910 4% 4% 0% 499,910 4% 5% -1%

JAN07 12,968,712 10,113,894 78% 62% 16% 499,900 5% 4% 1% 499,900 4% 4% 0% 499,900 4% 4% 0% 499,900 4% 4% 0%

FEB07 14,265,584 11,630,978 82% 63% 19% 499,890 4% 4% 0% 499,890 4% 4% 0% 499,890 4% 4% 0% 499,890 4% 3% 1%

MAR07 15,692,142 13,375,625 85% 64% 21% 499,880 4% 3% 1% 499,880 3% 3% 0% 499,880 3% 3% 0% 499,880 3% 2% 1%


This report is an analysis of the airline FWB Quality and performance and is constructed by using the data contained in the FWB summary report submitted each month by a specific airline participating in the IATA e-freight MIP programme.

Each row of the report shows, for the month, the actual figures submitted by the airline relating to that specific measure. The figures relating to Penetration, Duplicates, Messages rejected by CCS, Messages rejected by Airline and Business Data Invalid are calculated as a percentage of the total messages received by the airline. Variance against the targets, which will initially be set at the airline level are calculated and also included in the report.


a) Month




e) % Target

f) %Variance

g) Duplicates


i) % Target

j) %Variance

k) Syntax errors


m) % Target

n) %Variance



q) % Target

r) %Variance



u) % Target

v) %Variance


11.4 Report 4 - Airline Report - FHL Quality and Penetration Based on the data submitted by the airlines, IATA will produce the following report. It is important to note, that if the report data is not submitted by the airline on the 15th of the month, then the line of the report that relates to the month for which the data has not been submitted will be left blank.

A: M

ON

TH

b: T

otal

# o

f Shi

pmen

ts

c: P

enet

ratio

n

d: %

Pen

etra

tion

e:%

Tar

get

f:% V

aria

nce

g:D

uplic

ates

h:%

Dup

licat

es

i: %

Tar

get

j:% V

aria

nce

k: M

essa

ges

reje

cted

by

CC

S

l% M

essa

ges

reje

cted

by

CC

S m

: % T

arge

t

n:%

Var

ianc

e

o: M

essa

ges

reje

cted

by

Airl

ine

p:%

Mes

sage

s re

ject

ed

by A

irlin

e R

ejec

tions

q:

% T

arge

t

r:%

Var

ianc

e

s:Bu

sine

ss D

ata

Inva

lid

t:%B

usin

ess

Dat

a In

valid

u:

% T

arge

t

v:%

Var

ianc

e

MAR06 5,000,000 2,500,000 50% 50% 0% 500,000 20% 10% 10% 500,000 10% 10% 0% 500,000 10% 10% 0% 500,000 10% 23% -13%

APR06 5,500,000 2,875,000 52% 51% 1% 499,990 17% 9% 8% 499,990 9% 9% 0% 499,990 9% 9% 0% 499,990 9% 15% -6%

MAY06 6,050,000 3,306,250 55% 52% 3% 499,980 15% 8% 7% 499,980 8% 8% 0% 499,980 8% 8% 0% 499,980 8% 14% -6%

JUN06 6,655,000 3,802,188 57% 53% 5% 499,970 13% 8% 5% 499,970 8% 8% 0% 499,970 8% 8% 0% 499,970 8% 11% -3%

JUL06 7,320,500 4,372,516 60% 53% 6% 499,960 11% 7% 4% 499,960 7% 7% 0% 499,960 7% 7% 0% 499,960 7% 10% -3%

AUG06 8,052,550 5,028,393 62% 54% 8% 499,950 10% 6% 4% 499,950 6% 6% 0% 499,950 6% 6% 0% 499,950 6% 9% -3%

SEP06 8,857,805 5,782,652 65% 55% 10% 499,940 9% 6% 3% 499,940 6% 6% 0% 499,940 6% 6% 0% 499,940 6% 8% -2%

OCT06 9,743,586 6,650,050 68% 56% 12% 499,930 8% 6% 2% 499,930 5% 5% 0% 499,930 5% 5% 0% 499,930 5% 7% -2%

NOV06 10,717,944 7,647,557 71% 57% 15% 499,920 7% 5% 2% 499,920 5% 5% 0% 499,920 5% 5% 0% 499,920 5% 6% -1%

DEC06 11,789,738 8,794,691 75% 60% 15% 499,910 6% 4% 2% 499,910 4% 4% 0% 499,910 4% 4% 0% 499,910 4% 5% -1%

JAN07 12,968,712 10,113,894 78% 62% 16% 499,900 5% 4% 1% 499,900 4% 4% 0% 499,900 4% 4% 0% 499,900 4% 4% 0%

FEB07 14,265,584 11,630,978 82% 63% 19% 499,890 4% 4% 0% 499,890 4% 4% 0% 499,890 4% 4% 0% 499,890 4% 3% 1%

MAR07 15,692,142 13,375,625 85% 64% 21% 499,880 4% 3% 1% 499,880 3% 3% 0% 499,880 3% 3% 0% 499,880 3% 2% 1%


This report is an analysis of the airline FHL Quality and performance and is constructed by using the data contained in the FHL summary report submitted each month by a specific airline participating in the IATA e-freight MIP programme.

Each row of the report shows, for the month, the actual figures submitted by the airline relating to that specific measure. The figures relating to Penetration, Duplicates, Messages rejected by CCS, Messages rejected by Airline and Business Data Invalid are calculated as a percentage of the total messages received by the airline. Variance against the targets, which will initially be set at the airline level are calculated and also included in the report.


a) Month




e) % Target

f) %Variance

g) Duplicates


i) % Target

j) %Variance

k) Syntax errors


m) % Target

n) %Variance



q) % Target

r) %Variance



u) % Target

v) %Variance


11.5 Report 5 - Agent Report - IATA FWB Performance report to Agent Based on the data submitted by the airlines, IATA will produce the following report. It is important to note, that if the report data is not submitted by the airline on the 15th of each month, then this report will not be available to the forwarder.

A:AW

B Da

te

B: A

IRLI

NE

C: C

CS

D: F

ORW

ARDE

R

E: IA

TA A

gent

Num

ber

F: IA

TA C

argo

agen

t Cas

s ad

dres

s

G: M

AWB

Orig

in

H: M

AWB

Dest

inat

ion

I: AW

B No

. J:

No

of F

WBs

rece

ived

by

Airli

ne

K: E

rror 1

L: E

rror 2

M: E

rror 3

N: E

rror 4

O: E

rror 5

P: E

rror 6

Q: R

emar

ks

01-03-2007 BA Traxon DHL 91470038001 LHR B RU 99912345678 0

AWB0015 - Invalid or missing AWB consignment details - airline prefix

CVD0015 - Invalid or missing charge declarations details - ISO currency code

CVD0020 - Invalid or missing charge declarations details - charge code

CVD0025 - Invalid or missing charge declarations details - p/c indicator (Weight/Valuation)

03-03-2007 BA DHL 91470038001 LHR PTY 99923456789 2



04-03-2007 BA DHL 91470038001 LHR SJO 99934567890 2


06-03-2007 BA DHL 91470038001 LHR CLE 99945678901 1



This report details the errors to be reported back to the agents forwarders participating in the MIP programme and results from a consolidation of the details submitted by all airlines relating to that specific or multi-national forwarder. (a multi-national may have several branches, but only one report must be produced, that. This will be identified as part of the agent master file.).

The report shows details of each error for a specific forwarder and is constructed from the FWB detail report submitted by all airlines.

The only items to be excluded from this report are those for which no error exists (error code 1 to 3) AND the FWB count is 1.


a) AWB Date

b) AIRLINE

c) CCS

d) FORWARDER

e) IATA Agent Number

f) IATA Cargo agent Cass address

g) MAWB Origin

h) MAWB Destination

i) AWB No

j) No of FWBs received by Airline

k) Error 1

l) Error 2

m) Error 3

n) Error 4

o) Error 5

p) Error 6

q) Remarks


11.6 Report 6 - Agent Report - IATA FHL Performance report to Agent Based on the data submitted by the airlines, IATA will produce the following report. It is important to note, that if the report data is not submitted by the airline on the 15th of each month, then this report will not be available to the forwarder.

A:AW

B Da

te

B: A

IRLI

NE

C: C

CS

D: F

ORW

ARDE

R

E: IA

TA A

gent

Num

ber

F: IA

TA C

argo

agen

t Cas

s ad

dres

s

G: M

AWB

Orig

in

H: M

AWB

Dest

inat

ion

I: AW

B No

.

J: H

AWB

No

K: N

o of

FW

Bs re

ceive

d by

Ai

rline

L: E

rror 1

M: E

rror 2

N: E

rror 3

O: E

rror 4

P: E

rror 5

Q: E

rror 6

R: R

emar

ks

01-03-2007 BA Traxon; DHL 9147003 8001 LHR B RU 99912345678 12345678 0 AWB0015 - Invalid or missing AWB consignment details - airline prefix



CVD0025 - Invalid or missing charge declarations details - p/cindicator (Weight/Valuation)

03-03-2007 BA DHL 9147003 8001 LHR PTY 99912345678 23456789 2 CVD0015 - Invalid or missing charge declarations details - ISO currency code


04-03-2007 BA DHL 9147003 8001 LHR SJO 99912345678 34567890 2 CVD0020 - Invalid or missing charge declarations details - charge code

06-03-2007 BA DHL 9147003 8001 LHR CLE 99912345678 45678901 1 AWB0015 - Invalid or missing AWB consignment details - airline prefix


This report details the errors to be reported back to the agents participating in the MIP programme and results from a consolidation of the details submitted by all airlines relating to that specific or multi-national forwarder. (a multi-national may have several branches, but only one report must be produced, that will be identified as part of the agent master file.).

The report shows details of each error for a specific forwarder and is constructed from the FHL detail report submitted by all airlines.

The only items to be excluded from this report are those for which no error exists (error code 1 to 3) AND the FHL count is 1.


a) AWB Date

b) AIRLINE

c) CCS

d) FORWARDER



g) MAWB Origin

h) MAWB Destination

i) AWB No.

j) HAWB No.

k) No of FWBs received by Airline

l) Error 1

m) Error 2

n) Error 3

o) Error 4

p) Error 5

q) Error 6

r) Remarks

American Airlines

FWB FHL

a) F

OR

WA

RD

ER

b) %

Pen

etra

tion

c) F

OR

WA

RD

ER

d) %

Mes

sage

s W

ith s

ynta

x pr

oble

ms

e) F

OR

WA

RD

ER

f) %

Mes

sage

s R

ejec

ted

by

Airl

ine

g) F

OR

WA

RD

ER

h) %

Bus

ines

s D

ata

Inva

lid

I) FO

RW

AR

DER

j) %

Dup

licat

es

k) F

OR

WA

RD

ER

l) %

Pen

etra

tion

m) F

OR

WA

RD

ER

n) %

Mes

sage

s w

ith s

ynta

x pr

oble

ms

o) F

OR

WA

RD

ER

p) %

Mes

sage

s R

ejec

ted

by

Airl

ine

q) F

OR

WA

RD

ER

r) %

Bus

ines

s D

ata

Inva

lid

s) F

OR

WA

RD

ER

t) %

Dup

licat

es

KAN 94% YUS 7% YUS 2% YUS 4% YUS 4% KAN 94% YUS 7% YUS 3% YUS 4% YUS 4%

DHL 92% AGY 8% AGY 3% AGY 4% AGY 4% DHL 92% AGY 8% AGY 5% AGY 4% AGY 4%

AGY 90% DHL 8% DHL 5% DHL 4% DHL 5% AGY 90% DHL 8% DHL 5% DHL 4% DHL 5%

YUS 90% KAN 8% KAN 6% SCH 5% SCH 6% YUS 90% KAN 8% KAN 6% SCH 6% SCH 6%

SDV 88% SDV 8% SCH 6% KAN 5% KAN 6% SDV 88% SDV 8% SCH 6% KAN 6% KAN 6%

TNT 88% SCH 9% SDV 6% SDV 6% SDV 6% TNT 88% SCH 9% SDV 6% SDV 6% SDV 6%

SCH 85% TNT 9% TNT 6% TNT 6% TNT 6% SCH 85% TNT 9% TNT 6% TNT 6% TNT 6%

Average 91% 9% 6% 5% 6% Average 91% 9% 6% 6% 6%


This report details a specific or multinational forwarder’s performance with the airline. Each forwarder, or multinational will have their percentage performance for each of the following categories, calculated in accordance with the data element details listed below:

% Penetration

% Messages With syntax problems

% Messages rejected by Airline

% Business Data Invalid

% Duplicates

for both FWB and FHL messages

The forwarder with the best % performance under each category will be listed at the top while the forwarder with the most opportunity for improvement will be listed at the bottom. The forwarder names in the example are for illustrative purposes only and will be further developed.

This report is constructed from the FWB and FHL detailed reports submitted by a specific airlines.


FWB

a) FORWARDER

b) % Penetration

c) FORWARDER

d) % Messages with syntax Problems

e) FORWARDER

f) % Messages Rejected by Airline

g) FORWARDER

h) % Business Data Invalid

i) FORWARDER

j) % Duplicates

FHL

a) FORWARDER

b) % Penetration

c) FORWARDER


e) FORWARDER


g) FORWARDER


i) FORWARDER

j) % Duplicates

which could have an adverse affect on the overall performance.

Overall Performance

FWB FHL

a) F

OR

WA

RD

ER

b) %

Pen

etra

tion

c) F

OR

WA

RD

ER

d) M

essa

ges

With

sy

ntax

pro

blem

s

e) F

OR

WA

RD

ER

f) M

essa

ges

Rej

ecte

d by

A

irlin

e g)

FO

RW

AR

DER

h) B

usin

ess

Dat

a In

valid

I) FO

RW

AR

DER

j) D

uplic

ates

k) F

OR

WA

RD

ER

l) %

Pen

etra

tion

m) F

OR

WA

RD

ER

n) M

essa

ges

with

sy

ntax

pro

blem

s

o) F

OR

WA

RD

ER

p) M

essa

ges

Rej

ecte

d by

A

irlin

e q)

FO

RW

AR

DER

r) B

usin

ess

Dat

a In

valid

s) F

OR

WA

RD

ER

t) D

uplic

ates

KAN 94% YUS 7% YUS 2% YUS 4% YUS 4% KAN 94% YUS 7% YUS 3% YUS 4% YUS 4%

DHL 92% AGY 8% AGY 3% AGY 4% AGY 4% DHL 92% AGY 8% AGY 5% AGY 4% AGY 4%

AGY 90% DHL 8% DHL 5% DHL 4% DHL 5% AGY 90% DHL 8% DHL 5% DHL 4% DHL 5%

YUS 90% KAN 8% KAN 6% SCH 5% SCH 6% YUS 90% KAN 8% KAN 6% SCH 6% SCH 6%

SDV 88% SDV 8% SCH 6% KAN 5% KAN 6% SDV 88% SDV 8% SCH 6% KAN 6% KAN 6%

TNT 88% SCH 9% SDV 6% SDV 6% SDV 6% TNT 88% SCH 9% SDV 6% SDV 6% SDV 6%

SCH 85% TNT 9% TNT 6% TNT 6% TNT 6% SCH 85% TNT 9% TNT 6% TNT 6% TNT 6%

Average 91% 9% 6% 5% 6% Average 91% 9% 6% 6% 6%


This report details a specific or multinational forwarder’s aggregated performance with all airlines. Each forwarder, or multinational will have their percentage performance for each of the following categories, calculated in accordance with the data element details listed below:

% Penetration

% Messages With syntax problems

% Messages rejected by Airline

% Business Data Invalid

% Duplicates

for both FWB and FHL messages.

The agent with the best % performance under each category will be listed at the top while the agent with the most opportunity for improvement will be listed at the bottom. The forwarder names in the example are for illustrative purposes only and will be further developed.

This report is constructed from an aggregation of the FWB and FHL detailed reports submitted by all airlines.


FWB

a) FORWARDER

b) % Penetration

c) FORWARDER


e) FORWARDER


g) FORWARDER


i) FORWARDER

j) % Duplicates

FHL

a) FORWARDER

b) % Penetration

c) FORWARDER


e) FORWARDER


g) FORWARDER


i) FORWARDER

j) % Duplicates

which could have an adverse affect on the country performance.

Country Performance

FWB FHL

a) C

ount

ry

b) %

Pen

etra

tion

c) C

ount

ry

d) M

essa

ges

With

sy

ntax

pro

blem

s

e) C

ount

ry

f) M

essa

ges

Rej

ecte

d by

A

irlin

e g)

Cou

ntry

h) B

usin

ess

Dat

a In

valid

I) C

ount

ry

j) D

uplic

ates

k) C

ount

ry

l) %

Pen

etra

tion

m) C

ount

ry

n) M

essa

ges

with

sy

ntax

pro

blem

s

o) C

ount

ry

p) M

essa

ges

Rej

ecte

d by

A

irlin

e q)

Cou

ntry

r) B

usin

ess

Dat

a In

valid

s) C

ount

ry

t) D

uplic

ates

SG 94% AE 7% SV 3% SV 4% SV 4% SV 94% AE 7% SV 3% SV 4% SV 4%

GB 92% SV 7% HK 5% HK 4% HK 4% HK 92% CH 8% HK 5% HK 4% HK 4%

AE 90% HK 8% NL 5% NL 4% NL 4% NL 90% PT 8% NL 5% NL 4% NL 4%

SV 90% NL 8% AE 8% AE 6% AE 5% AE 90% ES 8% AE 6% AE 5% AE 5%

HK 88% CA 8% CH 8% CH 6% CH 5% CH 88% SV 8% CH 6% CH 5% CH 5%

NL 88% SG 9% PT 8% PT 6% PT 5% PT 88% HK 9% PT 6% PT 5% PT 5%

CA 85% GB 9% ES 9% ES 6% ES 5% ES 85% NL 9% ES 6% ES 5% ES 5%

Average 91% 9% 9% 6% 5% Average 91% 9% 6% 5% 5%


The above report requires a far more complex calculation regarding the countries performance. The same % calculation rules apply, but each AWB/HAWB line item will be allocated to a specific country and the quality and penetration reports will be against the data associated with each specific country. To calculate the figures below, country totals must be calculated for both FWB and FHL messages for:

Penetration

Messages with Syntax Problems

Messages Rejected by Airline

Business Data Invalid

Duplicates

The above report will be used by both the Country manager and RCD to ascertain a specific country’s MIP performance, enabling them to identify areas of focus.

FWB

a) Country

b) % Penetration

c) Country


e) Country


g) Country


i) Country

j) % Duplicates

FHL a) Country

b) % Penetration

c) Country

d) Messages with syntax Problems

e) FORWARDER

f) Messages Rejected by Airline

g) FORWARDER

h) Business Data Invalid

i) FORWARDER

j) Duplicates


11.10 Report 10 - Airline and Agent Report - e-freight Location Report Based on the data submitted by the airlines, IATA will produce the following report. It is important to note, that if the airline data is not submitted by the 15th of the month, then their specific data will not be included in this report.

A) A

WB

Date

A) A

IRLI

NE

B:)A

WB

No.

C: H

AWB

no.

D:FO

RWAR

DER

E:MA

WB

ORIG

IN

F:MA

WB

Des

tinat

ion

G: N

o of

FW

Bs/F

HLs

Sent

by a

gent

H: E

rror 1

I: Er

ror 2

J: E

rror 3

K: E

rror 4

L: E

rror 5

M: E

rror 6

01-03-2007 BA 99912345678 DHL LHR HKG 1




CVD0025 - Invalid or missing charge declarations details - p/c indicator (Weight/Valuation)

01-03-2007 BA 99923456789 12345678 DHL LHR HKG 2

01-03-2007 BA 99923456789 23456789 DHL LHR HKG 1

01-03-2007 BA 99923456789 34567890 DHL LHR HKG 6

01-03-2007 CX 77712345678 KAN LHR HKG 6



01-03-2007 CX 77734567890 KAN LHR HKG 8

01-03-2007 CX 77723456789 KAN LHR HKG 1


01-03-2007 CX 77723456789 12345678 KAN LHR HKG 4

01-03-2007 CX 77723456789 23456789 KAN LHR HKG 13

01-03-2007 CX 77723456789 34567890 KAN LHR HKG 6

01-03-2007 CX 77723456789 45678901 KAN LHR HKG 6


The above report will be produced on a monthly basis, and will report against the forwarder and airlines’ performance on e-freight trade lanes.

a) AWB Date

b) AIRLINE

c) CCS

d) FORWARDER



g) MAWB Origin

h) MAWB Destination

i) AWB No

j) HAWB No

k) No of FWBs/FHLs sent by Agent

l) Error 1

m) Error 2

n) Error 3

o) Error 4

p) Error 5

q) Error 6

r) Remarks


11.11 Report 11 – Industry Report – Industry FWB Penetration Report (chart) Based on the data submitted by the airlines, IATA will produce the following report. It is important to note, that if the report data is not submitted by the airline on the 15th of the month, then their specific data will not be included in the overall statistics, which could have an adverse affect on the industry statistics.

%

10%

20%

30%

40%

50%

60%

70%

80%

NO

V07

DEC

07

JAN

08

FEB0

8

MAR

08

APR08

MAY

08

JUN

08

JUL0

8

AUG

08

SEP0

8

OCT

08

FWB Penetration Report Africa

FWB Penetration Report AsiaPacificFWB Penetration Report CIS

FWB Penetration Report Europe

FWB Penetration Report Global

FWB Penetration Report MENA

FWB Penetration Report NorthAsiaFWB Penetration Report TheAmericas

The above report is generated based on the statistics from each airline.

To create this report, each origin city code, is allocated to a specific country and the country associated to a region. The penetration figure is calculated for that specific region using the same method described earlier.

Graphical reports are also produced by region, for

duplicates

business data invalid

syntax errors

rejections

using the same methodology as above and using the same calculation methods as described earlier.


11.12 Report 12 – Industry Report – Industry FHL Penetration Report (chart) Based on the data submitted by the airlines, IATA will produce the following report. It is important to note, that if the report data is not submitted by the airline on the 15th of the month, then their specific data will not be included in the overall statistics, which could have an adverse affect on the industry statistics.

%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%N

OV0

7

DEC

07

JAN

08

FEB0

8

MAR

08

APR08

MAY

08

JUN

08

JUL0

8

AUG

08

SEP0

8

OCT

08

FHL Penetration Report Africa

FHL Penetration Report AsiaPacificFHL Penetration Report CIS

FHL Penetration Report Europe

FHL Penetration Report Global

FHL Penetration Report MENA

FHL Penetration Report NorthAsiaFHL Penetration Report TheAmericas

The above report will be generated based on the statistics from each airline.

To create this report, each origin city code, is allocated to a specific country and the country associated to a region. The penetration figure is calculated for that specific region using the same method described earlier.

Graphical reports are also produced by region, for

duplicates


syntax errors

rejections

using the same methodology as above and using the same calculation methods as described earlier.


11.13 Report 13 – Airline Report – Airline FWB/FHL Penetration Report (chart) Based on historical information, a graph is produced to show overall penetration progress by airline against the actual industry performance and the industry targets when set.

%10%20%30%40%50%60%70%80%90%

NO

V07

DEC

07

JAN

08

FEB0

8

MAR

08

APR08

MAY

08

JUN

08

JUL0

8

AUG

08

SEP0

8

OCT

08

FHL PenetrationFWB PenetrationIndustry FHL PenetrationIndustry FWB Penetration

Graphical reports are also produced for

duplicates


syntax errors

rejections

using the same methodology as above.


11.14 Report 14 - Validation and Error Reports After processing data submissions from participating airlines, a report on which airlines have provided which .CSV files is provided in tabular format for checking purposes.

Airline FWB Summary Report FWB Detail Report FHL Summary

Report FHL Detail Report

AA-American Airlines Y Y Y Y

AC-Air Canada Y Y N Y

AF-Air France Y Y Y Y

AY-Finnair Y Y Y Y

AZ-Alitalia Y N Y N

BA-British Airways Y Y Y Y

CI-China Airlines Y Y Y Y

CV-Cargolux Y Y Y Y

CX-Cathay Pacific Airways Y Y Y Y

EK-Emirates Y Y Y Y

ET-Ethiopian Airlines Y Y Y Y

FI-Icelandair Y Y Y Y

IB-IBERIA Y Y Y Y

JL-Japan Airlines International Y Y Y Y

KA-Hong Kong Dragon Airlines Y Y Y Y

KE-Korean Air Y Y Y Y

KL-KLM Y Y Y Y

KZ-Nippon Cargo Airlines Y N Y N

LA-LAN Airlines Y Y Y Y

LH-Lufthansa Y Y Y Y

LO-LOT Y Y Y Y

LT-LTU Y Y Y N

MP-Martinair Y Y Y Y

MS-Egyptair Y Y Y N

NH-ANA Y Y Y Y

OK-CSA Czech Airlines Y Y Y Y

OZ-Asiana Airlines Y Y Y Y

SA-SAA Y Y N Y

SQ-Singapore Airlines Y Y Y Y

SV-Saudi Airlines Y Y Y Y

TK-Turkish Airlines Y Y Y Y

UA-United Airlines Y Y Y Y


11.15 Report 15 - Top Errors Report Based on airline’s data submission this report shows the top 5 errors in 6 different categories for all MIP participants (airlines and forwarders).

The purpose of this report is to help in prioritising root cause analysis and clearly identify the airlines, forwarders and locations where action is needed to increase penetration, reduce errors or reduce duplicate messages.

The 6 categories are:

1. Top locations with uncorrected errors on mandatory fields for e-freight

2. Top locations with corrected errors on mandatory fields for e-freight

3. Top locations with errors on fields that are optional for e-freight

4. Top locations with duplicate messages

5. Top locations from which no message received from EDI capable forwarders

6. Top locations from which no message received from non-EDI capable forwarders


12 Appendix C - Error Codes

Following the MIP Action Group conference call of 22nd September 2009, it has been agreed to review and simplify the error code set as described below.

12.1 Issues with the current error code set Prior to MIP Strategy v4:

There are 470 different error codes defined in format XXX9999, where XXX usually stands for the 3 letters codes of the C-IMP line identifiers and 9999 stands for a number between 0000 and 9999.

Some codes are redundant with other codes. There can be up to 4 different error codes defined for the same error, depending on if it occurred in an FWB or FHL and if it was corrected or not.

Some recently added fields in FWBs are not yet covered by any MIP error code.

Some codes are not consistently defined.

The definitions for syntax errors and business data invalid errors are misleading. Both types of errors refer to the same condition with the difference that a syntax error has not been corrected by the airline (resulting in the rejection of the message), while a business data invalid error is an error that’s been corrected by the airline (message accepted after correction).

12.2 Improvement – New simplified error code set Starting with MIP Strategy v4 and to be effective from January 1st 2009:

Reduction of the number of different error codes from 470 to 205.

The new error codes have a shorter format: XXX99, where

XXX stands for the same 3 letters as for the old error code (that usually follows the C-IMP line identifiers)

99 stands for a sequential number between 00 and 99

The shorter new error codes will result in smaller data files.

To remain compatible with the old error codes, each new error code can come in 2 different types:

Error not corrected and message rejected (XXX99)

Error corrected by the airline and message accepted (XXX99C), where the error code is followed with the letter “C” that stands for corrected.

Duplicate error codes have been eliminated.

Some new codes that were missing (for recently added fields in FWBs) have been added (see the “Comments” field in the attached spreadsheet).

Each new error code comes with an indication whether it is a priority for e-freight implementation (shown in the “EF Mandatory” column in the attached spreadsheet).

The error types have been reviewed and redefined as follows:

D = Data error, e.g. invalid or missing data in a specific field.

R = Rejected, e.g. message rejected for the reason described in the error definition.


S = Syntax error, e.g. the format of the message is invalid, resulting in the inability to use the message and therefore its rejection.

Some error codes can apply to both FWBs and FHLs (see columns D and E in the attached spreadsheet).

Each new error code indicates exactly which Cargo-IMP field it refers to in order to make sure the error trapping is aligned for every participant (see columns H to L in the attached spreadsheet).

12.3 The old MIP error code set will continue to be supported but not expanded MIP will continue to accept and support the old error codes without any limit

of time. There is no obligation to switch to new codes for existing participants. They can therefore remain indefinitely with the old codes or transition to the new codes if they prefer.

For existing participants who wish to transition to the new codes, the error trapping logic should in principle remain exactly the same in their applications, the only difference being in the error code that is returned for the condition. For each old error code corresponds a new error code. A cross-reference is provided in the included Excel spreadsheet (look at the “Old MIP Error Codes” sheet, column B).

Only new MIP participants (from January 1st 2009) will be required to follow the new error codes, unless the CSS or service provider they rely on is already capable to report using the old codes.

From time to time, C-IMP is upgrading the FWB and FHL message definitions by adding new fields as needed by the industry. Only the new error code set will reflect this and be expanded accordingly. Users of the old error code set will be able to continue reporting using the old error codes and mix in some error codes from the new set as needed.

12.4 MIP Reporting The simultaneous use of old or new error codes will have no impact on MIP

reporting as the new codes do not step over the old ones.

Most MIP Reports will show the error codes as reported by the airlines (old or new), together with the correct definition of the error.

Report 15 (Top Errors Report) will be based on the new error codes only and will automatically translate the old error codes to the new ones in Q1 2009. This will present a more accurate picture as to which errors are most frequent, regardless of if it they were corrected or not by the airlines.

12.5 New Error Code Set Starting with MIP Strategy v4 and to be effective from January 1st 2009.

The table below explains the meaning of the column headings used hereafter.

Column Heading Description

Error Code New MIP Error Code to be effective for all new participants from 1st January 2009

EF Mandatory Shows 1 if this field is mandatory for E-Freight

New Error Type D = invalid Data error (data missing or error in specific field)

R = message Rejected (message of no use)

S = Syntax error (syntax error in message format)

Note the old error types (prior to MIP Strategy v4) were:


Column Heading Description

B = Business Data Invalid (error corrected by the airline)

S = Syntax error (syntax or uncorrected data error resulting in the rejection of the message)

R = message Rejected (message of no use)

Applies To FWB Shows 1 if this error applies to FWBs

Applies To FHL Shows 1 if this error applies to FHLs

Error Description Description of the error

Comments

CIMP Ver Version of the Cargo Interchange Message Procedure Manual (Cargo-IMP)

CIMP FWB Ver Version of the FWB message the error refers to

CIMP FWB Fld Field number in the Cargo-IMP manual this error refers to

CIMP FHL Ver Version of the FHL message the error refers to

CIMP FHL Fld Field number in the Cargo-IMP manual this error refers to

12.5.1 Accounting Information Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL

Error Description Comments CIMP Ver

CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

ACC00 D 1 Invalid or missing accounting information 27 15 10

ACC01 D 1 Invalid or missing accounting information details - accounting information identifier 27 15 10.2.2

ACC02 D 1 Invalid or missing accounting information details - accounting information 27 15 10.2.4

12.5.2 Agent Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

AGT00 1 D 1 Invalid or missing agent details 27 15 7

AGT01 1 D 1 Invalid or missing agent details - account number 27 15 7.2.2

AGT02 1 D 1 Invalid or missing agent details - IATA cargo agent numeric code 27 15 7.2.4

AGT03 1 D 1 Invalid or missing agent details - IATA cargo agent CASS address 27 15 7.2.6

AGT04 1 D 1 Invalid or missing agent details - participant identifier 27 15 7.2.8


Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

AGT05 1 D 1 Invalid or missing agent details - name 27 15 7.4.2

AGT06 1 D 1 Invalid or missing agent details - place 27 15 7.5.2

12.5.3 Agent Reference Data Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

ARD00 D 1 Invalid or missing agent reference data 27 15 24

ARD01 D 1 Invalid or missing agent reference data - file reference 27 15 24.3.1

12.5.4 Air Way Bill Consignment Detail Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

AWB00 1 D 1 1 Invalid or missing AWB consignment details 27 15 2 3 2

AWB01 1 D 1 1 Invalid or missing AWB consignment details - airline prefix 27 15 2.1.1 3 2.3.1

AWB02 1 D 1 1 Invalid or missing AWB consignment details - AWB serial number 27 15 2.1.3 3 2.3.3

AWB03 1 D 1 1 Invalid or missing AWB consignment details - airport/city code of origin 27 15 2.2.1 3 2.4.1

AWB04 1 D 1 1 Invalid or missing AWB consignment details - airport/city code of destination 27 15 2.2.2 3 2.4.2

AWB05 1 D 1 1 Invalid or missing AWB consignment details - shipment description code 27 15 2.3.2 3 2.5.2

AWB06 1 D 1 1 Invalid or missing AWB consignment details - number of pieces 27 15 2.3.3 3 2.5.3

AWB07 1 D 1 1 Invalid or missing AWB consignment details - weight code 27 15 2.3.4 3 2.5.4

AWB08 1 D 1 1 Invalid or missing AWB consignment details - weight 27 15 2.3.5 3 2.5.5

AWB09 1 D 1 Invalid or missing AWB consignment details - volume code Add new 27 15 2.4.1

AWB10 1 D 1 Invalid or missing AWB consignment details - volume amount Add new 27 15 2.4.2

AWB11 1 D 1 Invalid or missing AWB consignment details - density indicator (DG) Add new 27 15 2.5.1

AWB12 1 D 1 Invalid or missing AWB consignment details - density group Add new 27 15 2.5.2

AWB13 1 R 1 1 Message rejected - AWB serial number blacklisted 27 15 -

AWB14 1 R 1 1 Message rejected - AWB serial number not 27 15 -


Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

allocated to this forwarder


12.5.5 CC Charges in Destination Currency Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

CDC00 D 1 Invalid or missing CC charges in destinationcurrency details 27 15 19

CDC01 D 1

Invalid or missing CC charges in destinationcurrency - destination currency details - ISOcurrency code 27 15 19.3.1

CDC02 D 1

Invalid or missing CC charges in destinationcurrency details - currency conversion rate -rate of exchange 27 15 19.4.1

CDC03 D 1

Invalid or missing CC charges in destinationcurrency details - CC charges in destination currency - charge amount 27 15 19.6.1

CDC04 D 1

Invalid or missing CC charges in destinationcurrency details - charges at destination - charge amount 27 15 19.8.1

CDC05 D 1

Invalid or missing CC charges in destinationcurrency details - total collect charges - charge amount 27 15 19.10.1

12.5.6 Shipper's Certification Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

CER00 D 1 Invalid or missing shippers certification details 27 15 16

CER01 D 1 Invalid or missing shippers certification details - signature 27 15 16.3

12.5.7 Consignee Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

CNE00 1 D 1 1 Invalid or missing consignee details 27 15 6 3 7

CNE01 1 D 1 Invalid or missing consignee details - account number 27 15 6.2.2

CNE02 1 D 1 1 Invalid or missing consignee details - name 27 15 6.4.2 3 7.3

CNE03 1 D 1 1 Invalid or missing consignee details - street address 27 15 6.5.2 3 7.5.2

CNE04 1 D 1 1 Invalid or missing consignee details - place 27 15 6.6.2 3 7.6.2

CNE05 1 D 1 1 Invalid or missing consignee details - state/province 27 15 6.6.4 3 7.6.4

CNE06 1 D 1 1 Invalid or missing consignee details - ISO country code 27 15 6.7.2 3 7.7.2

CNE07 1 D 1 1 Invalid or missing consignee details - post code 27 15 6.7.4 3 7.7.4


Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

CNE08 1 D 1 1 Invalid or missing consignee details - contact identifier 27 15 6.8.2 3 7.8.2

CNE09 1 D 1 1 Invalid or missing consignee details - contact number 27 15 6.8.4 3 7.8.4

CNE10 1 S 1 1

Syntax error - consignee details - total characters of country code, post code, contact id and contact number cannot exceed 69 Add new 27 15

6.7-8 FWB41 3

7.7-8 FHL26

12.5.8 Commission Information Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

COI00 D 1 Invalid or missing commission information details 27 15 22

COI01 D 1

Invalid or missing commission information details - no commission indication - CASS indicator 27 15 22.3.1

COI02 D 1

Invalid or missing commission information details - commission amount - CASS settlement factor 27 15 22.5.1

COI03 D 1

Invalid or missing commission information details - commission percentage - CASS settlement factor 27 15 22.7.1

12.5.9 Collect Charge Summary Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

COL00 D 1 Invalid or missing collect charge summary details 27 15 15

COL01 D 1

Invalid or missing collect charge summary details - total weight charge - charge identifier 27 15

15.2 a

COL02 D 1 Invalid or missing collect charge summary details - total weight charge - charge amount 27 15

15.2 b

COL03 D 1 Invalid or missing collect charge summary details - valuation charge - charge amount 27 15 15.2 c

COL04 D 1 Invalid or missing collect charge summary details - taxes - charge amount 27 15

15.2 d

COL05 D 1

Invalid or missing collect charge summary details - total other charges due agent - charge amount 27 15

15.2 e

COL06 D 1

Invalid or missing totals collect charge summary details - total other charges due carrier - charge amount 27 15 15.2 f


Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

COL07 D 1

Invalid or missing collect charge summary details - charges summary total - charge amount 27 15

15.2 g

COL08 D 1 Invalid collect charge summary details - charges collect not allowed to this destination 27 15 15

12.5.10 Customs Origin Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

COR01 D 1 Invalid or missing customs origin code details 27 15 21.3

12.5.11 Charge Declarations Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

CVD00 1 D 1 1 Invalid or missing charge declarations details 27 15 11 3 8

CVD01 1 D 1 1 Invalid or missing charge declarations details - ISO currency code 27 15 11.3 3 8.3

CVD02 1 D 1 Invalid or missing charge declarations details - charge code 27 15 11.5

CVD03 1 D 1 1 Invalid or missing charge declarations details - p/c indicator (Weight/Valuation) 27 15 11.7.1 3 8.5.1

CVD04 1 D 1 1 Invalid or missing charge declarations details - p/c indicator (Other charges) 27 15 11.7.2 3 8.5.2

CVD05 1 D 1 1 Invalid or missing charge declarations details - declared value for carriage 27 15 11.8.2 3 8.6.2

CVD06 1 D 1 1 Invalid or missing charge declarations details - value for customs declaration 27 15 11.10.1 3 8.7.2

CVD07 1 D 1 1 Invalid or missing charge declarations details - value for insurance declaration 27 15 11.11.2 3 8.8.2

12.5.12 Flight Booking Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

FLT00 D 1 Invalid or missing flight booking details 27 15 3

FLT01 D 1 Invalid or missing flight booking details -carrier code 27 15 3.2.2

FLT02 D 1 Invalid or missing flight booking details -flight number 27 15 3.2.3

FLT03 D 1 Invalid or missing flight booking details -day 27 15 3.2.5


12.5.13 FWB Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

FWB01 1 R 1

Message rejected - FWB data differs significantly from that contained in the booking 27 15 -

FWB02 1 R 1 Message rejected - FWB routing differs from that contained in shipment booking 27 15 -

FWB03 S 1

Syntax error - SSR+NFY+OSI+COR total characters length too long - the total characters cannot exceeds 216 27 15 -

12.5.14 Harmonised Tariff Schedule Information Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

HTS01 D 1 Invalid of missing harmonised commodity code details 27 3 5.3

12.5.15 House waybill summary details Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

HBS00 1 D 1 Invalid or missing house waybill summary details 27 3 3

HBS01 1 D 1 Invalid or missing house waybill summary details - HWB Serial Number 27 3 3.3

HBS02 1 D 1 Invalid or missing house waybill summary details - HWB airport/city code of origin 27 3 3.5.1

HBS03 1 D 1 Invalid or missing house waybill summary details - HWB airport/city code of destination 27 3 3.5.2

HBS04 1 D 1 Invalid or missing house waybill summary details - HWB number of pieces 27 3 3.7.1

HBS05 1 D 1 Invalid or missing house waybill summary details - HWB weight code 27 3 3.7.3

HBS06 1 D 1 Invalid or missing house waybill summary details - HWB weight 27 3 3.7.4

HBS07 1 D 1 Invalid or missing house waybill summary details - HWB SLAC 27 3 3.7.6

HBS08 1 D 1 Invalid or missing house waybill summary details - HWB manifest description of goods 27 3 3.8.2

HBS09 1 D 1 Invalid or missing house waybill summary details - HWB special handling code 27 3

3.9.2-3


12.5.16 Carrier's Execution Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

ISU00 1 D 1 Invalid or missing carriers execution details 27 15 17

ISU01 1 D 1 Invalid or missing carriers execution details - AWB issue details - day 27 15 17.2.2

ISU02 1 D 1 Invalid or missing carriers execution details - AWB issue details - month 27 15 17.2.3

ISU03 1 D 1 Invalid or missing carriers execution details - AWB issue details - year 27 15 17.2.4

ISU04 1 D 1 Invalid or missing carriers execution details - AWB issue details - place or airport/city code 27 15 17.2.6

ISU05 1 D 1 Invalid or missing carriers execution details - authorisation - signature 27 15 17.3.2

12.5.17 Message Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

MSG01 1 S 1 1 Syntax error - message envelope syntax error 27

MSG02 1 S 1 1 Syntax error - invalid or no end of message character 27

MSG03 1 S 1 1

Syntax error - unable to use the data (data contained in the message cannot be used to update the carrier system) 27 15 - 3 -

MSG04 1 R 1 1

Message rejected - data already created in carriers system (too late to be of any use, message received after the carrier has created the data in its system) 27 15 - 3 -

MSG05 1 R 1 1 Message rejected - the originators TTY address is not recognised by the carrier 27 15 - 3 -

MSG06 1 R 1 1

Message rejected - the originator TTY address is recognised but not configured to accept this message type 27 15 - 3 -

MSG07 1 R 1 1 Message rejected - message version number not supported by carrier 27 15 1.3 3 1.3

12.5.18 Also Notify Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

NFY00 D 1 Invalid or missing also notify details 27 15 9

NFY01 D 1 Invalid or missing also notify details - name 27 15 9.2.2

NFY02 D 1 Invalid or missing also notify details - street address 27 15 9.3.2

NFY03 D 1 Invalid or missing also notify details - place 27 15 9.4.2


Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

NFY04 D 1 Invalid or missing also notify details - state/province 27 15 9.4.4

NFY05 D 1 Invalid or missing also notify details - ISO country code 27 15 9.5.2

NFY06 D 1 Invalid or missing also notify details - post code 27 15 9.5.4

NFY07 D 1 Invalid or missing also notify details - contact identifier 27 15 9.6.2

NFY08 D 1 Invalid or missing also notify details - contact number 27 15 9.6.4

NFY09 S 1

Syntax error - also notify details - total characters of country code, post code, contact id and contact number cannot exceed 69 Add new 27 15

9.5-6 FWB42

12.5.19 Nominated Handling Party Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

NOM00 D 1 Invalid or missing nominated handling party details 27 15 26

NOM01 D 1 Invalid or missing nominated handling party details - name 27 15 26.3

NOM02 D 1 Invalid or missing nominated handling party details - place 27 15 26.5

12.5.20 Other Customs Information Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

OCI00 D 1 Invalid or missing other customs information details 27 15 29

OCI01 D 1 Invalid or missing other customs information details - ISO country code 27 15 29.3

OCI02 D 1 Invalid or missing other customs information details - information identifier 27 15 29.5

OCI03 D 1 Invalid or missing other customs information details - customs information identifier 27 15 29.7

OCI04 D 1 Invalid or missing other customs information details - supplementary customs information 27 15 29.9


12.5.21 Other Participant Information Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

OPI00 D 1 Invalid or missing other participant information details 27 15 28

OPI01 D 1 Invalid or missing other participant information details - name 27 15 28.3

OPI02 D 1

Invalid or missing other participant information details - participant office message address - airport/city code 27 15 28.6.1

OPI03 D 1

Invalid or missing other participant information details - participant office message address - office function designator 27 15 28.6.2

OPI04 D 1

Invalid or missing other participant information details - participant office message address - company designator 27 15 28.6.3

OPI05 D 1

Invalid or missing other participant information details - other participant information - file reference 27 15 28.8.1

OPI06 D 1

Invalid or missing other participant information details - other participant identification - participant identifier 27 15 28.9.2

OPI07 D 1

Invalid or missing other participant information details - other participant identification - participant code 27 15 28.9.4

OPI08 D 1

Invalid or missing other participant information details - other participant identification - airport/city code 27 15 28.9.6

12.5.22 Other Service Information Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

OSI01 D 1 Invalid or missing Other Service Information 27 15 18

12.5.23 Other Charges Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

OTH00 D 1 Invalid or missing other charge details 27 15 13

OTH01 D 1 Invalid or missing other charge details - p/c indicator 27 15 13.2.2

OTH02 D 1 Invalid or missing other charge details - other charge code 27 15 13.13.1

OTH03 D 1 Invalid or missing other charge details - entitlement code 27 15 13.3.2

OTH04 D 1 Invalid or missing other charge details - 27 15 13.3.3


Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

charge amount

12.5.24 Prepaid Charge Summary Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

PPD00 D 1 Invalid or missing prepaid charge summary details 27 15 14

PPD01 D 1

Invalid or missing prepaid charge summary details - total weight charge - charge identifier 27 15

14.2-4/6-8.2

PPD02 D 1 Invalid or missing prepaid charge summary details - total weight charge - charge amount 27 15 14.2.3

PPD03 D 1 Invalid or missing prepaid charge summary details - valuation charge - charge amount 27 15 14.3.3

PPD04 D 1 Invalid or missing prepaid charge summary details - taxes - charge amount 27 15 14.4.3

PPD05 D 1

Invalid or missing prepaid charge summary details - total other charges due agent - charge amount 27 15 14.6.3

PPD06 D 1

Invalid or missing prepaid charge summary details - total other charges due carrier - charge amount 27 15 14.7.3

PPD07 D 1

Invalid or missing prepaid charge summary details - charge summary total - charge amount 27 15 14.8.3

12.5.25 Sender Reference Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

REF00 1 D 1 Invalid or missing sender reference details 27 15 20

REF01 1 D 1

Invalid or missing sender reference details - sender office message address - airport/city code 27 15 20.3.1

REF02 1 D 1

Invalid or missing sender reference details - sender office message address - office function designator 27 15 20.3.2

REF03 1 D 1

Invalid or missing sender reference details - sender office message address - company designator 27 15 20.3.3

REF04 1 D 1 Invalid or missing sender reference details - sender office file reference - file reference 27 15 20.5.1

REF05 1 D 1

Invalid or missing sender reference details - sender participant identification - participant identifier 27 15 20.6.2


Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

REF06 1 D 1

Invalid or missing sender reference details - sender participant identification - participant code 27 15 20.6.4

REF07 1 D 1

Invalid or missing sender reference details - sender participant identification - participant airport/city code 27 15 20.6.6

12.5.26 Rate Description Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

RTD00 1 D 1 Invalid or missing rate description details 27 15 12

RTD01 1 D 1 Invalid or missing rate description details - AWB rate line number 27 15 12.2.2

RTD02 1 D 1 Invalid or missing rate description details - AWB column Identifier 27 15

12.3/5-9/11-18.2

RTD03 1 D 1

Invalid or missing rate description details - number of pieces/RCP details - number of pieces/rate combination point 27 15 12.3.3

RTD04 1 D 1 Invalid or missing rate description details - gross weight details - weight code 27 15 12.4.2

RTD05 1 D 1 Invalid or missing rate description details - gross weight details - weight 27 15 12.4.3

RTD06 1 D 1 Invalid or missing rate description details - rate class details - rate class code 27 15 12.5.3

RTD07 1 D 1

Invalid or missing rate description details - commodity item number details - commodity item number/ULD rate class type/rate class code class rate percentage 27 15 12.6.3

RTD08 1 D 1 Invalid or missing rate description details - chargeable weight details - weight 27 15 12.7.3

RTD09 1 D 1

Invalid or missing rate description details - rate charge details - rate or charge or discount 27 15 12.8.3

RTD10 1 D 1

Invalid or missing rate description details - total details - charge amount or discount amount 27 15 12.9.3

RTD11 1 D 1 Invalid or missing rate description details - goods description - goods data identifier 27 15

12.11-18.3

RTD12 1 D 1

Invalid or missing rate description details - goods description - nature and quantity of goods 27 15 12.11.5

RTD13 1 D 1

Invalid or missing rate description details - consolidation - nature and quantity of goods 27 15 12.12.5


Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

RTD14 1 D 1 Invalid or missing rate description details - dimensions - weight code 27 15 12.13.5

RTD15 1 D 1 Invalid or missing rate description details - dimensions - weight 27 15 12.13.6

RTD16 1 D 1

Invalid or missing rate description details - dimensions - measurement unit code or no dimensions available code 27 15 12.13.8

RTD17 1 D 1 Invalid or missing rate description details - dimensions - length dimension 27 15 12.13.9

RTD18 1 D 1 Invalid or missing rate description details - dimensions - width dimension 27 15 12.13.11

RTD19 1 D 1 Invalid or missing rate description details - dimensions - height dimension 27 15 12.13.13

RTD20 1 D 1 Invalid or missing rate description details - dimensions - no of pieces 27 15 12.13.15

RTD21 1 S 1

Syntax error - rate description details - totalnumber of characters of unit code, length, width, height and no of pieces cannot exceed 20 Add new 27 15

12.13.8-15

FWB47

RTD22 1 D 1 Invalid or missing rate description details - volume - volume code 27 15 12.14.5

RTD23 1 D 1 Invalid or missing rate description details - volume - volume amount 27 15 12.14.6

RTD24 1 D 1 Invalid or missing rate description details - ULD number - ULD type 27 15 12.15.5

RTD25 1 D 1 Invalid or missing rate description details - ULD number - ULD serial number 27 15 12.15.6

RTD26 1 D 1 Invalid or missing rate description details - ULD number - ULD owner code 27 15 12.15.7

RTD27 1 D 1 Invalid or missing rate description details - shippers load and count - SLAC 27 15 12.16.5

RTD28 1 D 1 Invalid or missing rate description details - harmonised commodity code 27 15 12.17.5

RTD29 1 D 1

Invalid or missing rate description details - country of origin of goods - ISO country code 27 15 12.18.5

RTD30 1 D 1 Invalid or missing rate description details - service code details - service code 27 15 12.19.2

12.5.27 Routing Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

RTG00 1 D 1 Invalid or missing routing details 27 15 4

RTG01 1 D 1 Invalid or missing routing details - 1st destination/carrier airport city code 27 15 4.2.2


Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

RTG02 1 D 1 Invalid or missing routing details - 1st destination/carrier carrier code 27 15 4.2.3

RTG03 1 D 1 Invalid or missing routing details - onward destination/carrier airport city code 27 15 4.3.2

RTG04 1 D 1 Invalid or missing routing details - onward destination/carrier carrier code 27 15 4.3.3


12.5.28 Shipper Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

SHP00 1 D 1 1 Invalid or missing shipper details 27 15 5 3 6

SHP01 1 D 1 Invalid or missing shipper details - account number 27 15 5.2.2

SHP02 1 D 1 1 Invalid or missing shipper details - name 27 15 5.4.2 3 6.3

SHP03 1 D 1 1 Invalid or missing shipper details - street address 27 15 5.5.2 3 6.5.2

SHP04 1 D 1 1 Invalid or missing shipper details - place 27 15 5.6.2 3 6.6.2

SHP05 1 D 1 1 Invalid or missing shipper details - state/province 27 15 5.6.4 3 6.6.4

SHP06 1 D 1 1 Invalid or missing shipper details - ISO country code 27 15 5.7.2 3 6.7.2

SHP07 1 D 1 1 Invalid or missing shipper details - post code 27 15 5.7.4 3 6.7.4

SHP08 1 D 1 1 Invalid or missing shipper details - contact identifier 27 15 5.8.2 3 6.8.2

SHP09 1 D 1 1 Invalid or missing shipper details - contact number 27 15 5.8.4 3 6.8.4

SHP10 1 S 1 1

Syntax error - shipper details - total characters of country code, post code, contact id and contact number cannot exceed 69 Add new 27 15

5.7-8 FWB40 3

6.7-8 FHL22

12.5.29 Sales Incentive Information Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

SII00 D 1 Invalid or missing sales incentive information details 27 15 23

SII01 D 1 Invalid or missing sales incentive information details - charge amount 27 15 23.3.1

SII02 D 1 Invalid or missing sales incentive information details - CASS indicator 27 15 23.5.1

12.5.30 Special Handling Details Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

SPH01 1 D 1 Invalid or missing special handling code EF 27 15 25.2.2


12.5.31 Shipment Reference Information Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

SRI00 D 1 Invalid or missing shipment reference information details 27 15 27

SRI01 D 1 Invalid or missing shipment reference information details - reference number 27 15 27.3

SRI02 D 1

Invalid or missing shipment reference information details - supplementary shipment information 27 15

27.5-7

12.5.32 Special Service Request Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

SSR01 D 1 Invalid or missing Special Service Request 27 15 8

12.5.33 Free Text Description of Goods Errors Error Code

EF Mandatory

New Error Type

AppliesTo

FWB

AppliesTo FHL


CIMP FWB Ver

CIMP FWB Fld

CIMP FHL Ver

CIMP FHL Fld

TXT01 D 1 Invalid or missing free text description of goods details 27 3 4.3

TXT02 S 1 Syntax error - free text description of goods details - total characters cannot exceed 545 Add new 27 3 4.3

12.6 Old Error Code to New Error code translation The below table shows all old error codes in the second column (prior to MIP Strategy v4) and how they translate to the new error codes in the third column (effective with MIP Strategy v4 from January 1st 2009). Error Code Group Description

Old MIP Error Code

New MIPError Code

EF Mandatory

ErrorType

AppliesTo

FWB

AppliesTo FHL

Error Correctedby Airline

Error Description Comments CIMPVer

CIMPFWB Ver

CIMP FWB Fld

CIMPFHL Ver

CIMP FHL Fld

Accounting Information ACC0010 ACC00 S 1

Invalid or missing accounting information 27 15 10


Invalid or missing accounting details- accounting information identifier 27 15 10.2.2


Invalid or missing accounting details- accounting information 27 15 10.2.4

Accounting Information ACC1010 ACC00C B 1 1 Accounting information corrected 27 15 10

Accounting Information ACC1015 ACC01C B 1 1

Accounting information details - accounting information identifier corrected 27 15 10.2.2

Accounting Information ACC1020 ACC02C B 1 1

Accounting information details - accounting information corrected 27 15 10.2.4

Agent AGT0010 AGT00 1 S 1 Invalid or missing agent details 27 15 7

Agent AGT0015 AGT01 1 S 1 Invalid or missing agent details -

27 15 7.2.2


Error Code Group Description

Old MIP Error Code

New MIPError Code

EF Mandatory

ErrorType

AppliesTo

FWB

AppliesTo FHL



CIMPFWB Ver

CIMP FWB Fld

CIMPFHL Ver

CIMP FHL Fld

account number

Agent AGT0020 AGT02 1 S 1 Invalid or missing agent details - IATA cargo agent numeric code 27 15 7.2.4

Agent AGT0025 AGT03 1 S 1 Invalid or missing agent details - IATA cargo agent CASS address 27 15 7.2.6

Agent AGT0030 AGT04 1 S 1 Invalid or missing agent details - participant identifier 27 15 7.2.8

Agent AGT0035 AGT05 1 S 1 Invalid or missing agent name 27 15 7.4.2

Agent AGT0040 AGT06 1 S 1 Invalid or missing agent place 27 15 7.5.2

Agent AGT1010 AGT00C 1 B 1 1 Agent details corrected 27 15 7

Agent AGT1015 AGT01C 1 B 1 1 Agent details - account number corrected 27 15 7.2.2

Agent AGT1020 AGT02C 1 B 1 1 Agent details - IATA cargo agent numeric code corrected 27 15 7.2.4

Agent AGT1025 AGT03C 1 B 1 1 Agent details - IATA cargo agent CASS address corrected 27 15 7.2.6

Agent AGT1030 AGT04C 1 B 1 1 Agent details - participant identifier corrected 27 15 7.2.8

Agent AGT1035 AGT05C 1 B 1 1 Agent details - name corrected 27 15 7.4.2

Agent AGT1040 AGT06C 1 B 1 1 Agent details - place corrected 27 15 7.5.2

Agent Reference Data ARD0010 ARD00 S 1

Invalid or missing agent reference data 27 15 24

Agent Reference Data ARD0015 ARD01 S 1

Invalid or missing agent reference data file reference 27 15 24.3.1

Agent Reference Data ARD1010 ARD00C B 1 1 Agent reference data corrected 27 15 24

Agent Reference Data ARD1015 ARD01C B 1 1

Agent reference data file reference corrected 27 15 24.3.1

Air Way Bill Consignment Detail AWB0010 AWB00 1 S 1

Invalid or missing AWB consignment details 27 15 2


Invalid or missing AWB consignment details - airline prefix 27 15 2.1.1


Invalid or missing AWB consignment details - AWB serial number 27 15 2.1.3


Invalid or missing AWB consignment details - airport/city code of origin 27 15 2.2.1


Invalid or missing AWB consignment details - airport/city code of destination 27 15 2.2.2


Invalid or missing AWB consignment details - shipment description code 27 15 2.3.2


Invalid or missing AWB consignment details - number of pieces 27 15 2.3.3


Invalid or missing AWB consignment details - weight code 27 15 2.3.4



Old MIP Error Code

New MIPError Code

EF Mandatory

ErrorType

AppliesTo

FWB

AppliesTo FHL



CIMPFWB Ver

CIMP FWB Fld

CIMPFHL Ver

CIMP FHL Fld


Invalid or missing AWB consignment details - weight 27 15 2.3.5

Air Way Bill Consignment Detail AWB1010 AWB00C 1 B 1 1 AWB Consignment details corrected 27 15 2

Air Way Bill Consignment Detail AWB1015 AWB01C 1 B 1 1

AWB consignment details - airline prefix corrected 27 15 2.1.1


AWB consignment details - AWB serial number corrected 27 15 2.1.3


AWB consignment details - airport/city code of origin corrected 27 15 2.2.1


AWB consignment details - airport/city code of destination corrected 27 15 2.2.2


AWB consignment details - shipment description code corrected 27 15 2.3.2


AWB consignment details - number of pieces corrected 27 15 2.3.3


AWB consignment details - weight code corrected 27 15 2.3.4


AWB consignment details - weight corrected 27 15 2.3.5


Invalid or missing Master AWB Consignment Details 27 3 2


Invalid or missing Master AWB Consignment Details - Airline Prefix 27 3 2.3.1


Invalid or missing Master AWB Consignment Details - AWB Serial Number 27 3 2.3.3


Invalid or missing Master AWB Consignment Details - AWB airport/city code of origin 27 3 2.4.1


Invalid or missing Master AWB Consignment Details - AWB airport/city code of destination 27 3 2.4.2


Invalid or missing Master AWB Consignment Details - AWB shipment description code 27 3 2.5.2


Invalid or missing Master AWB Consignment Details - AWB numberof pieces 27 3 2.5.3


Invalid or missing Master AWB Consignment Details - AWB weight code 27 3 2.5.4


Invalid or missing Master AWB Consignment Details - AWB weight 27 3 2.5.5


Master AWB Consignment Details corrected 27 3 2



Old MIP Error Code

New MIPError Code

EF Mandatory

ErrorType

AppliesTo

FWB

AppliesTo FHL



CIMPFWB Ver

CIMP FWB Fld

CIMPFHL Ver

CIMP FHL Fld


Master AWB Consignment Details - Airline Prefix corrected 27 3 2.3.1


Master AWB Consignment Details - AWB Serial Number corrected 27 3 2.3.3


Master AWB Consignment Details - AWB Airport/City Code of Origin corrected 27 3 2.4.1


Master AWB Consignment Details - AWB Airport/City Code of Destination corrected 27 3 2.4.2


Master AWB Consignment Details - AWB Shipment Description Code corrected 27 3 2.5.2


Master AWB Consignment Details - AWB Number of pieces corrected 27 3 2.5.3


Master AWB Consignment Details - AWB Weight code corrected 27 3 2.5.4


Master AWB Consignment Details - AWB Weight corrected 27 3 2.5.5

CCS CCS0015 MSG01 1 S 1 FWB envelope syntax error

New error code added 11/9/2007 for CCS rejections 27

CCS CCS0020 MSG01 1 S 1 FHL envelope syntax error

New error code added 11/9/2007 for CCS rejections 27

CC Charges in Destination Currency CDC0010 CDC00 S 1

Invalid or missing CC charges in destination currency details 27 15 19


Invalid or missing CC charges in destination currency - destination currency details - ISO currency code 27 15 19.3.1


Invalid or missing CC charges in destination currency details - currency conversion rate - rate of exchange 27 15 19.4.1


Invalid or missing CC charges in destination currency details - CC charges in destination currency - charge amount 27 15 19.6.1


Invalid or missing CC charges in destination currency details - charges at destination - charge amount 27 15 19.8.1


Invalid or missing CC charges in destination currency details - total collect charges - charge amount 27 15 19.10.1

CC Charges in Destination Currency CDC1010 CDC00C B 1 1

CC charges in destination currency details corrected 27 15 19

CC Charges in Destination

CDC1015 CDC01C B 1 1 CC charges in destination currency details - destination currency - ISO

27 15 19.3.1



Old MIP Error Code

New MIPError Code

EF Mandatory

ErrorType

AppliesTo

FWB

AppliesTo FHL



CIMPFWB Ver

CIMP FWB Fld

CIMPFHL Ver

CIMP FHL Fld

Currency currency code corrected


CC charges in destination currency - currency conversion rate - rate of exchange corrected 27 15 19.4.1


CC charges in destination currency details - CC charges in destination currency - charge amount corrected 27 15 19.6.1


CC charges in destination currency details - charges at destination - charge amount corrected 27 15 19.8.1


CC charges in destination currency details - total collect charges - charge amount corrected 27 15 19.10.1

Shipper's Certification CER0010 CER00 S 1

Invalid or missing shippers certification details 27 15 16

Shipper's Certification CER0015 CER01 S 1

Invalid or missing shippers certification details - signature 27 15 16.3

Shipper's Certification CER1010 CER00C B 1 1

Shippers certification details corrected 27 15 16

Shipper's Certification CER1015 CER01C B 1 1

Shippers certification details - signature corrected 27 15 16.3

Consignee CNE0010 CNE00 1 S 1 Invalid or missing consignee details 27 15 6

Consignee CNE0015 CNE01 1 S 1 Invalid or missing consignee details - account number 27 15 6.2.2

Consignee CNE0020 CNE02 1 S 1 Invalid or missing consignee details - name 27 15 6.4.2

Consignee CNE0025 CNE03 1 S 1 Invalid or missing consignee details - street address 27 15 6.5.2

Consignee CNE0030 CNE04 1 S 1 Invalid or missing consignee details - place 27 15 6.6.2

Consignee CNE0035 CNE05 1 S 1 Invalid or missing consignee details - state/province 27 15 6.6.4

Consignee CNE0040 CNE06 1 S 1 Invalid or missing consignee details - ISO country code 27 15 6.7.2

Consignee CNE0045 CNE07 1 S 1 Invalid or missing consignee details - post code. 27 15 6.7.4

Consignee CNE0050 CNE08 1 S 1 Invalid or missing consignee details - contact identifier 27 15 6.8.2

Consignee CNE0055 CNE09 1 S 1 Invalid or missing consignee details - contact number 27 15 6.8.4

Consignee CNE1010 CNE00C 1 B 1 1 Consignee details corrected 27 15 6

Consignee CNE1015 CNE01C 1 B 1 1 Consignee details - account numbercorrected 27 15 6.2.2

Consignee CNE1020 CNE02C 1 B 1 1 Consignee details - name corrected 27 15 6.4.2

Consignee CNE1025 CNE03C 1 B 1 1 Consignee details - street address corrected 27 15 6.5.2

Consignee CNE1030 CNE04C 1 B 1 1 Consignee details - place corrected 27 15 6.6.2

Consignee CNE1035 CNE05C 1 B 1 1 Consignee details - state/province corrected 27 15 6.6.4

Consignee CNE1040 CNE06C 1 B 1 1 Consignee details - ISO country code corrected 27 15 6.7.2

Consignee CNE1045 CNE07C 1 B 1 1 Consignee details - post code corrected 27 15 6.7.4



Old MIP Error Code

New MIPError Code

EF Mandatory

ErrorType

AppliesTo

FWB

AppliesTo FHL



CIMPFWB Ver

CIMP FWB Fld

CIMPFHL Ver

CIMP FHL Fld

Consignee CNE1050 CNE08C 1 B 1 1 Consignee details - contact identifier corrected 27 15 6.8.2

Consignee CNE1055 CNE09C 1 B 1 1 Consignee details - contact number corrected 27 15 6.8.4

Consignee CNE2010 CNE00 S 1 Invalid or missing consignee details 27 3 7

Consignee CNE2015 CNE02 S 1 Invalid or missing consignee details - name 27 3 7.3

Consignee CNE2020 CNE03 S 1 Invalid or missing consignee details - street address 27 3 7.5.2

Consignee CNE2025 CNE04 S 1 Invalid or missing consignee details - place 27 3 7.6.2

Consignee CNE2030 CNE05 S 1 Invalid or missing consignee details - state/province 27 3 7.6.4

Consignee CNE2035 CNE06 S 1 Invalid or missing consignee details - ISO country code 27 3 7.7.2

Consignee CNE2040 CNE07 S 1 Invalid or missing consignee details - post code. 27 3 7.7.4

Consignee CNE2045 CNE08 S 1 Invalid or missing consignee details - contact identifier 27 3 7.8.2

Consignee CNE2050 CNE09 S 1 Invalid or missing consignee details - contact number 27 3 7.8.4

Consignee CNE3010 CNE00C B 1 1 Consignee corrected 27 3 7

Consignee CNE3015 CNE02C B 1 1 Consignee details - name corrected 27 3 7.3

Consignee CNE3020 CNE03C B 1 1 Consignee details - street address corrected 27 3 7.5.2

Consignee CNE3025 CNE04C B 1 1 Consignee details - place corrected 27 3 7.6.2

Consignee CNE3030 CNE05C B 1 1 Consignee details - state/province corrected 27 3 7.6.4

Consignee CNE3035 CNE06C B 1 1 Consignee details - ISO country code corrected 27 3 7.7.2

Consignee CNE3040 CNE07C B 1 1 Consignee details - post code corrected 27 3 7.7.4

Consignee CNE3045 CNE08C B 1 1 Consignee details - contact identifier corrected 27 3 7.8.2

Consignee CNE3050 CNE09C B 1 1 Consignee details - contact number corrected 27 3 7.8.4

Commission Information COI0010 COI00 S 1

Invalid or missing commission information details 27 15 22


Invalid or missing commission information details - no commission indication - CASS indicator 27 15 22.3.1


Invalid or missing commission information details - commission amount - CASS settlement factor 27 15 22.5.1


Invalid or missing commission information details - commission percentage - CASS settlement factor 27 15 22.7.1

Commission Information COI1010 COI00C B 1 1

Commission information details corrected 27 15 22


Commission information details - no commission indication - CASS indicator corrected 27 15 22.3.1



Old MIP Error Code

New MIPError Code

EF Mandatory

ErrorType

AppliesTo

FWB

AppliesTo FHL



CIMPFWB Ver

CIMP FWB Fld

CIMPFHL Ver

CIMP FHL Fld


Commission information details - commission amount - CASS settlement factor corrected 27 15 22.5.1


Commission information details - commission percentage - CASS settlement factor corrected 27 15 22.7.1

Collect Charge Summary COL0010 COL00 S 1

Invalid or missing collect charge summary details 27 15 15


Invalid or missing collect charge summary details - total weight charge - charge identifier 27 15 15.2 a


Invalid or missing collect charge summary details - total weight charge - charge amount 27 15 15.2 b


Invalid or missing collect charge summary details - valuation charge - charge amount 27 15 15.2 c


Invalid or missing collect charge summary details - taxes - charge amount 27 15 15.2 d


Invalid or missing collect charge summary details - total other charges due agent - charge amount 27 15 15.2 e


Invalid or missing totals collect charge summary details - total other charges due carrier - charge amount 27 15 15.2 f


Invalid or missing collect charge summary details - charges summary total - charge amount 27 15 15.2 g

Collect Charge Summary COL1010 COL00C B 1 1 Collect charge summary corrected 27 15 15

Collect Charge Summary COL1015 COL01C B 1 1

Collect charge summary details - total weight charge - charge identifier corrected 27 15 15.2 a


Collect charge summary details - total weight charge - charge amount corrected 27 15 15.2 b


Collect charge summary details - valuation charge - charge amount corrected 27 15 15.2 c


Collect charge summary details - taxes - charge amount corrected 27 15 15.2 d


Collect charge summary details - totals other charges due agent - charge amount corrected 27 15 15.2 e


Collect charge summary details - total other charges due carrier - charge amount corrected

Typo in MIPStrategy Doc where it shows as COL0040 27 15 15.2 f


Collect charge summary details - charges summary total - charge amount corrected 27 15 15.2 g

Customs Origin COR0010 COR01 S 1

Invalid or missing customs origin code details 27 15 21.3

Customs Origin COR1010 COR01C B 1 1

Customs origin code details corrected 27 15 21.3

Charge CVD0010 CVD00 1 S 1

Invalid or missing charge 27 15 11



Old MIP Error Code

New MIPError Code

EF Mandatory

ErrorType

AppliesTo

FWB

AppliesTo FHL



CIMPFWB Ver

CIMP FWB Fld

CIMPFHL Ver

CIMP FHL Fld

Declarations declarations details

Charge Declarations CVD0015 CVD01 1 S 1

Invalid or missing charge declarations details - ISO currency code 27 15 11.3


Invalid or missing charge declarations details - charge code 27 15 11.5


Invalid or missing charge declarations details - p/c indicator (Weight/Valuation) 27 15 11.7.1


Invalid or missing charge declarations details - p/c indicator (Other charges) 27 15 11.7.2


Invalid or missing charge declarations details - declared value for carriage 27 15 11.8.2


Invalid or missing charge declarations declared details - value for customs declaration 27 15 11.10.1


Invalid or missing charge declarations details - value for insurance declaration 27 15 11.11.2

Charge Declarations CVD1010 CVD00C 1 B 1 1

Charge declarations details corrected 27 15 11


Charge declarations details - ISO currency code corrected 27 15 11.3


Charge declarations details - chargecode corrected 27 15 11.5


Charge declarations details - p/c indicator (Weight/Valuation) corrected 27 15 11.7.1


Charge declarations details - p/c indicator (Other charges) corrected 27 15 11.7.2


Charge declarations details - declared value for carriage corrected 27 15 11.8.2


Charge declarations details - value for customs declaration corrected 27 15 11.10.1


Charge declarations details - value for insurance declaration corrected 27 15 11.11.2

Charge Declarations CVD2010 CVD00 S 1

Invalid or missing charge declarations details 27 3 8


Invalid or missing charge declarations details - ISO currency code 27 3 8.3


Invalid or missing charge declarations details - p/c indicator (Weight/Valuation) 27 3 8.5.1


Invalid or missing charge declarations details - p/c indicator (Other charges) 27 3 8.5.2


Invalid or missing charge declarations details - declared value for carriage 27 3 8.6.2


Invalid or missing charge declarations details - declared value for customs 27 3 8.7.2



Old MIP Error Code

New MIPError Code

EF Mandatory

ErrorType

AppliesTo

FWB

AppliesTo FHL



CIMPFWB Ver

CIMP FWB Fld

CIMPFHL Ver

CIMP FHL Fld


Invalid or missing charge declarations details - amount of insurance 27 3 8.8.2

Charge Declarations CVD3010 CVD00C B 1 1

Charge declarations details corrected 27 3 8


Charge declarations details - ISO currency code corrected 27 3 8.3


Charge declarations details - p/c indicator (Weight/Valuation) corrected 27 3 8.5.1


Charge declarations details - p/c indicator (Other charges) corrected 27 3 8.5.2


Charge declarations details - declared Value for Carriage corrected 27 3 8.6.2


Charge declarations details - declared Value for Customs corrected 27 3 8.7.2


Charge declarations details - amount of insurance corrected 27 3 8.8.2

FHL FHL2010 MSG03 1 R 1

Unable to use the FHL data (Data contained with the sent message cannot be used to update the carriers system). 27 3 -


House Air Waybill already created in carriers system (The FWB has been received after the carrier has created the data in his system and is too late to be of any use) 27 3 -

FHL FHL2020 MSG05 1 R 1 The originators TTY address is not recognised by the carrier. 27 3 -


The originator TTY address is recognised but not configured to accept this message type. 27 3 -

FHL FHL2030 AWB03 1 R 1

Carrier does not recognise airport oforigin (The carrier is unable to create the routing in its system using the origin airport supplied) 27 3

2.4.1/3.5.1


Carrier does not recognise airport ofdestination (The carrier is unable to create the routing in its system using the destination airport supplied in the message) 27 3

2.4.2/3.5.2

FHL FHL2040 HBS01 1 R 1

The House air waybill number contained in the FHL does not match with the House air waybill number on the document. 27 3 3.3

FHL FHL2045 MSG07 1 R 1 FHL version number not supported by carrier. 27 3 1.3

FHL FHL2050 AWB02 1 R 1 No corresponding MAWB/FWB exists in carriers system. 27 3 2.3.3


The sum of the number of pieces in the FHL details received so far exceeds the number of pieces in theFWB/AWB 27 3 2.5.3


The sum of the gross weight relating the FHL details received so far exceeds the gross weight in the FWB/AWB 27 3 2.5.5



Old MIP Error Code

New MIPError Code

EF Mandatory

ErrorType

AppliesTo

FWB

AppliesTo FHL



CIMPFWB Ver

CIMP FWB Fld

CIMPFHL Ver

CIMP FHL Fld

Flight Booking FLT0010 FLT00 S 1 Invalid or missing flight booking details 27 15 3

Flight Booking FLT0015 FLT01 S 1 Invalid or missing flight booking details - carrier code 27 15 3.2.2

Flight Booking FLT0020 FLT02 S 1 Invalid or missing flight booking details - flight number 27 15 3.2.3

Flight Booking FLT0025 FLT03 S 1 Invalid or missing flight booking details - day 27 15 3.2.5

Flight Booking FLT1010 FLT00C B 1 1 Flight booking details corrected 27 15 3

Flight Booking FLT1015 FLT01C B 1 1 Flight booking details - carrier code corrected 27 15 3.2.2

Flight Booking FLT1020 FLT02C B 1 1 Flight booking details - flight numbercorrected 27 15 3.2.3

Flight Booking FLT1025 FLT03C B 1 1 Flight booking details - day corrected 27 15 3.2.5

FWB FNA0010 MSG03 1 R 1

Unable to use the FWB data (Data contained with the sent message cannot be used to update the carriers system) *** Obsolete code - Use FWB0010 instead ***

Obsolete code - Use FWB0010 or new code MSG03 instead 27

FWB FNA0015 MSG04 1 R 1

Air Waybill already tendered or created in carriers system (The FWB has been received after the carrier has created the data in his system and is too late to be of any use) *** Obsolete code - Use FWB0015 instead ***

Obsolete code - Use FWB0015 or new code MSG04 instead 27

FWB FWB0010 MSG03 1 R 1

Unable to use the FWB data (Data contained with the sent message cannot be used to update the carriers system). 27 15 -


Air Waybill already tendered or created in carriers system (The FWB has been received after the carrier has created the data in his system and is too late to be of any use) 27 15 -

FWB FWB0020 MSG05 1 R 1 The originators TTY address is not recognised by the carrier. 27 15 -


The originator TTY address is recognised but not configured to accept this message type. 27 15 -

FWB FWB0030 AWB03 1 R 1

Carrier does not recognise airport oforigin (The carrier is unable to create the routing in its system using the origin airport supplied) 27 15 2.2.1


Carrier does not recognise airport ofdestination (The carrier is unable to create the routing in its system using the destination airport supplied in the message) 27 15 2.2.2

FWB FWB0040 MSG07 1 R 1 FWB version number not supported by carrier 27 15 1.3

FWB FWB0045 FWB01 1 R 1 FWB data differs significantly from that contained in the booking. 27 15 -

FWB FWB0050 FWB02 1 R 1 FWB routing differs from that contained in shipment booking 27 15 -



Old MIP Error Code

New MIPError Code

EF Mandatory

ErrorType

AppliesTo

FWB

AppliesTo FHL



CIMPFWB Ver

CIMP FWB Fld

CIMPFHL Ver

CIMP FHL Fld

FWB FWB0055 COL08 R 1 FWB charges collect not allowed to this destination 27 15 15/19

FWB FWB0060 AWB01 1 R 1 FWB invalid airline account number. 27 15 2.1.1

FWB FWB0065 AWB13 1 R 1 FWB rejected - AWB blacklisted 27 15 -

FWB FWB0070 AWB01 1 R 1 FWB rejected - invalid airline account number. 27 15 2.1.1


FWB Number of pieces in rate line is not equal to the total dimension number of pieces. 27 15

2.3.3/12.3.3/12.1

3.15

FWB FWB0080 RTD24 1 R 1

FWB rejected - ULD details are mandatory for this rate line rate class code. 27 15

12.15.5-7

FWB FWB0085 RTD09 1 R 1

FWB rejected - Per kilo rate can exist only if rate line B (Basic rate) exists 27 15

12.13.5-6


FWB rejected - This AWB number has not been allocated, as part of the airline stock control, to this forwarder. 27 15 -

FWB FWB0095 MSG02 1 R 1 FWB rejected - Invalid or no end of message character. 27 15 -

FWB FWB1010 FWB01C 1 B 1 1

FWB data differs from that contained in the shipment booking - booking corrected. 27 15 -

FWB FWB1015 FWB02C 1 B 1 1

FWB routing differs from that contained in shipment booking - booking corrected 27 15 -

FWB FWB1020 COL08C B 1 1

FWB charges collect not allowed to this destination - corrected to prepaid 27 15 15/19

FWB FWB1025 AWB01C B 1 1 FWB invalid airline account number - airline account number changed 27 15 2.1.1

Harmonised Tariff Schedule Information HTS2010 HTS01 S 1

Invalid of missing harmonised commodity code details 27 3 5.3

Harmonised Tariff Schedule Information HTS3010 HTS01C B 1 1

Harmonised commodity code details corrected 27 3 5.3

House Air Waybill Summary Detail HWB2010HBS00 1 S 1

Invalid or missing house waybill summary details 27 3 3


Invalid or missing house waybill summary details - HWB Serial Number 27 3 3.3


Invalid or missing house waybill summary details - HWB airport/city code of origin 27 3 3.5.1


Invalid or missing house waybill summary details - HWB airport/city code of destination 27 3 3.5.2

House Air Waybill

HWB2030HBS04 1 S 1 Invalid or missing house waybill summary details - HWB number of

27 3 3.7.1



Old MIP Error Code

New MIPError Code

EF Mandatory

ErrorType

AppliesTo

FWB

AppliesTo FHL



CIMPFWB Ver

CIMP FWB Fld

CIMPFHL Ver

CIMP FHL Fld

Summary Detail

pieces


Invalid or missing house waybill summary details - HWB weight code 27 3 3.7.3


Invalid or missing house waybill summary details - HWB weight 27 3 3.7.4


Invalid or missing house waybill summary details - HWB SLAC 27 3 3.7.6


Invalid or missing house waybill summary details - HWB manifest description of goods 27 3 3.8.2


Invalid or missing house waybill summary details - HWB special handling code 27 3 3.9.2-3

House Air Waybill Summary Detail HWB3010HBS00C 1 B 1 1

House Waybill summary details corrected 27 3 3


House Waybill summary details corrected - HWB Serial Number corrected 27 3 3.3


House Waybill summary details corrected - HWB Airport/City Code of Origin corrected 27 3 3.5.1


House Waybill summary details corrected - HWB Airport/City Code of Destination corrected 27 3 3.5.2


House Waybill summary details corrected - HWB Number of pieces corrected 27 3 3.7.1


House Waybill summary details corrected - HWB Weight code corrected 27 3 3.7.3


House Waybill summary details corrected - HWB Weight corrected 27 3 3.7.4


House Waybill summary details corrected - HWB SLAC corrected 27 3 3.7.6


House Waybill summary details corrected - HWB Manifest description of goods corrected 27 3 3.8.2


House Waybill summary details corrected - HWB Special handling code corrected 27 3 3.9.2-3



Old MIP Error Code

New MIPError Code

EF Mandatory

ErrorType

AppliesTo

FWB

AppliesTo FHL



CIMPFWB Ver

CIMP FWB Fld

CIMPFHL Ver

CIMP FHL Fld

Carrier's Execution ISU0010 ISU00 1 S 1

Invalid or missing carriers execution details 27 15 17


Invalid or missing carriers execution details - AWB issue details - day 27 15 17.2.2


Invalid or missing carriers execution details - AWB issue details - month 27 15 17.2.3


Invalid or missing carriers execution details - AWB issue details - year 27 15 17.2.4


Invalid or missing carriers execution details - AWB issue details - place or airport/city code 27 15 17.2.6


Invalid or missing carriers execution details - authorisation - signature 27 15 17.3.2

Carrier's Execution ISU1010 ISU00C 1 B 1 1 Carriers execution details corrected 27 15 17

Carrier's Execution ISU1015 ISU01C 1 B 1 1

Carriers Execution details - AWB issue details - day corrected 27 15 17.2.2


Carriers Execution details - AWB issue details - month corrected 27 15 17.2.3


Carriers Execution details - AWB issue details - year corrected 27 15 17.2.4


Carriers Execution details - AWB issue details - place or airport/city code corrected 27 15 17.2.6


Carriers Execution details - Authorisation - signature corrected 27 15 17.3.2

Miscellaneous MSC0010 FWB03 0 S 1

SSR - NFY - OSI - COR - combined length too long. The combined character length for these elements exceeds 216. 27 15 -

Also Notify NFY0010 NFY00 S 1 Invalid or missing also notify details 27 15 9

Also Notify NFY0015 NFY01 S 1 Invalid or missing also notify details - name 27 15 9.2.2

Also Notify NFY0020 NFY02 S 1 Invalid or missing also notify details - street address 27 15 9.3.2

Also Notify NFY0025 NFY03 S 1 Invalid or missing also notify details - place 27 15 9.4.2

Also Notify NFY0030 NFY04 S 1 Invalid or missing also notify details - state/province 27 15 9.4.4

Also Notify NFY0035 NFY05 S 1 Invalid or missing also notify details - ISO country code 27 15 9.5.2

Also Notify NFY0040 NFY06 S 1 Invalid or missing also notify details - post code. 27 15 9.5.4

Also Notify NFY0045 NFY07 S 1 Invalid or missing also notify details - contact identifier 27 15 9.6.2

Also Notify NFY0050 NFY08 S 1 Invalid or missing also notify details - contact number 27 15 9.6.4

Also Notify NFY1010 NFY00C B 1 1 Also notify details corrected 27 15 9

Also Notify NFY1015 NFY01C B 1 1 Also notify details - name corrected 27 15 9.2.2

Also Notify NFY1020 NFY02C B 1 1 Also notify details - street address corrected 27 15 9.3.2

Also Notify NFY1025 NFY03C B 1 1 Also notify details - place corrected 27 15 9.4.2

Also Notify NFY1030 NFY04C B 1 1 Also notify details - state/province corrected 27 15 9.4.4



Old MIP Error Code

New MIPError Code

EF Mandatory

ErrorType

AppliesTo

FWB

AppliesTo FHL



CIMPFWB Ver

CIMP FWB Fld

CIMPFHL Ver

CIMP FHL Fld

Also Notify NFY1035 NFY05C B 1 1 Also notify details - ISO country code corrected 27 15 9.5.2

Also Notify NFY1040 NFY06C B 1 1 Also notify details - post code corrected 27 15 9.5.4

Also Notify NFY1045 NFY07C B 1 1 Also notify details - contact identifier corrected 27 15 9.6.2

Also Notify NFY1050 NFY08C B 1 1 Also notify details - contact number corrected 27 15 9.6.4

Nominated Handling Party NOM0010NOM00 S 1

Invalid or missing nominated handling party details 27 15 26


Invalid or missing nominated handling party details - name 27 15 26.3


Invalid or missing nominated handling party details - place 27 15 26.5

Nominated Handling Party NOM1010NOM00C B 1 1

Nominated handling party details corrected 27 15 26


Nominated handling party details - name corrected 27 15 26.3


Nominated handling party details - place corrected 27 15 26.5

Other Customs Information OCI0010 OCI00 S 1

Invalid or missing other customs information details 27 15 29


Invalid or missing other customs information details - ISO country code 27 15 29.3


Invalid or missing other customs information details - information identifier 27 15 29.5


Invalid or missing other customs information details - customs information identifier 27 15 29.7


Invalid or missing other customs information details - supplementary customs information 27 15 29.9

Other Customs Information OCI1010 OCI00C B 1 1

Other customs information details corrected 27 15 29


Other customs information details - ISO country code corrected 27 15 29.3


Other customs information details - information identifier corrected 27 15 29.5


Other customs information details - customs information identifier corrected 27 15 29.7


Other customs information details - supplementary customs information corrected 27 15 29.9

Other Participant Information OPI0010 OPI00 S 1

Invalid or missing other participant information details 27 15 28


Invalid or missing other participant information details - name 27 15 28.3



Old MIP Error Code

New MIPError Code

EF Mandatory

ErrorType

AppliesTo

FWB

AppliesTo FHL



CIMPFWB Ver

CIMP FWB Fld

CIMPFHL Ver

CIMP FHL Fld


Invalid or missing other participant information details - participant office message address - airport/citycode 27 15 28.6.1


Invalid or missing other participant information details - participant office message address - office function designator 27 15 28.6.2


Invalid or missing other participant information details - participant office message address - company designator 27 15 28.6.3


Invalid or missing other participant information details - other participant information - file reference 27 15 28.8.1


Invalid or missing other participant information details - other participant identification - participant identifier 27 15 28.9.2


Invalid or missing other participant information details - other participant identification - participant code 27 15 28.9.4


Invalid or missing other participant information details - other participant identification - airport/city code 27 15 28.9.6

Other Participant Information OPI1010 OPI00C B 1 1

Other participant information details corrected 27 15 28


Other participant information details - name corrected 27 15 28.3


Other participant information details - participant office message address- airport/city code corrected 27 15 28.6.1


Other participant information details - participant office message address- office function designator corrected 27 15 28.6.2


Other participant information details - participant office message address- company designator corrected 27 15 28.6.3


Other participant information details - other participant information - file reference corrected 27 15 28.8.1


Other participant information details - other participant identification - participant identifier corrected 27 15 28.9.2


Other participant information details - other participant identification - participant code corrected 27 15 28.9.4


Other participant information details - other participant identification - airport/city code corrected 27 15 28.9.6

Other Service Information OSI0010 OSI01 S 1

Invalid or missing Other Service Information 27 15 18

Other Service Information OSI1010 OSI01C B 1 1 Other Service Information corrected 27 15 18

Other Charges OTH0010 OTH00 S 1 Invalid or missing other charge

27 15 13



Old MIP Error Code

New MIPError Code

EF Mandatory

ErrorType

AppliesTo

FWB

AppliesTo FHL



CIMPFWB Ver

CIMP FWB Fld

CIMPFHL Ver

CIMP FHL Fld

details

Other Charges OTH0015 OTH01 S 1 Invalid or missing other charge details - p/c indicator 27 15 13.2.2

Other Charges OTH0020 OTH02 S 1 Invalid or missing other charge details - other charge code 27 15 13.13.1

Other Charges OTH0025 OTH03 S 1 Invalid or missing other charge details - entitlement code 27 15 13.3.2

Other Charges OTH0030 OTH04 S 1 Invalid or missing other charge details - charge amount 27 15 13.3.3

Other Charges OTH1010 OTH00C B 1 1 Other charges details corrected 27 15 13

Other Charges OTH1015 OTH01C B 1 1 Other charges details - p/c indicator corrected 27 15 13.2.2

Other Charges OTH1020 OTH02C B 1 1 Other charge details - code corrected 27 15 13.13.1

Other Charges OTH1025 OTH03C B 1 1 Other charges details - entitlement code corrected 27 15 13.3.2

Other Charges OTH1030 OTH04C B 1 1 Other charges details - charge amount corrected 27 15 13.3.3

Prepaid Charge Summary PPD0010 PPD00 S 1

Invalid or missing prepaid charge summary details 27 15 14


Invalid or missing prepaid charge summary details - total weight charge - charge identifier 27 15

14.2-4/6-8.2


Invalid or missing prepaid charge summary details - total weight charge - charge amount 27 15 14.2.3


Invalid or missing prepaid charge summary details - valuation charge - charge amount 27 15 14.3.3


Invalid or missing prepaid charge summary details - taxes - charge amount 27 15 14.4.3


Invalid or missing prepaid charge summary details - total other charges due agent - charge amount 27 15 14.6.3


Invalid or missing prepaid charge summary details - total other charges due carrier - charge amount 27 15 14.7.3


Invalid or missing prepaid charge summary details - charge summary total - charge amount 27 15 14.8.3

Prepaid Charge Summary PPD1010 PPD00C B 1 1

Prepaid charge summary details corrected 27 15 14


Prepaid charge summary details - total weight charge - charge identifier corrected 27 15

14.2-4/6-8.2


Prepaid charge summary details - total weight charge - charge amount corrected 27 15 14.2.3


Prepaid charge summary details - valuation charge - charge amount corrected 27 15 14.3.3



Old MIP Error Code

New MIPError Code

EF Mandatory

ErrorType

AppliesTo

FWB

AppliesTo FHL



CIMPFWB Ver

CIMP FWB Fld

CIMPFHL Ver

CIMP FHL Fld


Prepaid charge summary details - taxes - charge amount corrected 27 15 14.4.3


Prepaid charge summary details - totals other charges due agent - charge amount corrected 27 15 14.6.3


Prepaid charge summary details - total other charges due carrier - charge amount corrected

Typo in MIPStrategy Doc where it shows as PPD0040 27 15 14.7.3


Prepaid charge summary details - charges summary total - charge amount corrected 27 15 14.8.3

Sender Reference REF0010 REF00 1 S 1

Invalid or missing sender reference details 27 15 20


Invalid or missing sender reference details - sender office message address - airport/city code 27 15 20.3.1


Invalid or missing sender reference details - sender office message address - office function designator 27 15 20.3.2


Invalid or missing sender reference details - sender office message address - company designator 27 15 20.3.3


Invalid or missing sender reference details - sender office file reference - file reference 27 15 20.5.1


Invalid or missing sender reference details - sender participant identification - participant identifier 27 15 20.6.2


Invalid or missing sender reference details - sender participant identification - participant code 27 15 20.6.4


Invalid or missing sender reference details - sender participant identification - participant airport/city code 27 15 20.6.6

Sender Reference REF1010 REF00C 1 B 1 1 Sender reference details corrected 27 15 20

Sender Reference REF1015 REF01C 1 B 1 1

Sender reference details - sender office message address - airport/citycode corrected 27 15 20.3.1


Sender reference details - sender office message address - office function designator corrected 27 15 20.3.2


Sender reference details - sender office message address - company designator corrected 27 15 20.3.3


Sender reference details - sender office file reference - file reference corrected 27 15 20.5.1


Sender reference details - sender participant identification - participant identifier corrected 27 15 20.6.2


Sender reference details - sender participant identification - participant code corrected 27 15 20.6.4

Sender Reference REF1045 REF07C 1 B 1 1 Sender reference details - sender

participant identification - participant 27 15 20.6.6



Old MIP Error Code

New MIPError Code

EF Mandatory

ErrorType

AppliesTo

FWB

AppliesTo FHL



CIMPFWB Ver

CIMP FWB Fld

CIMPFHL Ver

CIMP FHL Fld

airport/city code corrected

Rate Description RTD0010 RTD00 1 S 1

Invalid or missing rate description details 27 15 12


Invalid or missing rate description details - AWB rate line number 27 15 12.2.2


Invalid or missing rate description details - AWB column Identifier 27 15

12.3/5-9/11-18.2


Invalid or missing rate description details - number of pieces/RCP details - number of pieces/rate combination point 27 15 12.3.3


Invalid or missing rate description details - gross weight details - weight code 27 15 12.4.2


Invalid or missing rate description details - gross weight details - weight 27 15 12.4.3


Invalid or missing rate description details - rate class details - rate class code 27 15 12.5.3


Invalid or missing rate description details - commodity item number details - commodity item number/ULD rate class type/rate class code class rate percentage 27 15 12.6.3


Invalid or missing rate description details - chargeable weight details - weight 27 15 12.7.3


Invalid or missing rate description details - rate charge details - rate or charge or discount 27 15 12.8.3


Invalid or missing rate description details - total details - charge amount or discount amount 27 15 12.9.3


Invalid or missing rate description details - goods description - goods data identifier 27 15

12.11-18.3


Invalid or missing rate description details - goods description - nature and quantity of goods 27 15 12.11.5


Invalid or missing rate description details - consolidation - nature and quantity of goods 27 15 12.12.5


Invalid or missing rate description details - dimensions - weight code 27 15 12.13.5


Invalid or missing rate description details - dimensions - weight 27 15 12.13.6


Invalid or missing rate description details - dimensions - measurement unit code or no dimensions available code 27 15 12.13.8


Invalid or missing rate description details - dimensions - length dimension 27 15 12.13.9


Invalid or missing rate description details - dimensions - width dimension 27 15 12.13.11



Old MIP Error Code

New MIPError Code

EF Mandatory

ErrorType

AppliesTo

FWB

AppliesTo FHL



CIMPFWB Ver

CIMP FWB Fld

CIMPFHL Ver

CIMP FHL Fld


Invalid or missing rate description details - dimensions - height dimension 27 15 12.13.13


Invalid or missing rate description details - dimensions - no of pieces 27 15 12.13.15


Invalid or missing rate description details - volume - volume code 27 15 12.14.5


Invalid or missing rate description details - volume - volume amount 27 15 12.14.6


Invalid or missing rate description details - ULD number - ULD type 27 15 12.15.5


Invalid or missing rate description details - ULD number - ULD serial number 27 15 12.15.6


Invalid or missing rate description details - ULD number - ULD owner code 27 15 12.15.7


Invalid or missing rate description details - shippers load and count - SLAC 27 15 12.16.5


Invalid or missing rate description details - harmonised commodity code 27 15 12.17.5


Invalid or missing rate description details - Country of origin of goods - ISO country code 27 15 12.18.5


Invalid or missing rate description details - service code details - service code 27 15 12.19.2

Rate Description RTD1010 RTD00C 1 B 1 1 Rate description details corrected 27 15 12

Rate Description RTD1015 RTD01C 1 B 1 1

Rate description details - AWB Rate line number corrected 27 15 12.2.2


Rate description details - AWB column Identifier corrected 27 15

12.3/5-9/11-18.2


Rate description details - number of pieces/RCP details - number of pieces/rate combination point corrected 27 15 12.3.3


Rate description details - gross weight details - weight code corrected 27 15 12.4.2


Rate description details - gross weight details - weight corrected 27 15 12.4.3


Rate description details - rate class details - rate class code corrected 27 15 12.5.3


Rate description details - commodity item number details - commodity item number/ULD rate class type/rate class code class ratepercentage corrected 27 15 12.6.3


Rate description details - chargeable weight details - weight corrected 27 15 12.7.3


Rate description details - rate charge details - rate or charge or discount corrected 27 15 12.8.3



Old MIP Error Code

New MIPError Code

EF Mandatory

ErrorType

AppliesTo

FWB

AppliesTo FHL



CIMPFWB Ver

CIMP FWB Fld

CIMPFHL Ver

CIMP FHL Fld


Rate description details - total details - charge amount or discount amount corrected 27 15 12.9.3


Rate description details - goods description - goods data identifier corrected 27 15

12.11-18.3


Rate description details - goods description - nature and quantity of goods corrected 27 15 12.11.5


Rate description details - consolidation - nature and quantity of goods corrected 27 15 12.12.5


Rate description details - dimensions - weight code corrected 27 15 12.13.5


Rate description details - dimensions - weight corrected 27 15 12.13.6


Rate description details - dimensions - measurement unit code or no dimensions available code corrected 27 15 12.13.8


Rate description details - dimensions - length dimension corrected 27 15 12.13.9


Rate description details - dimensions - width dimension corrected 27 15 12.13.11


Rate description details - dimensions - Height dimension corrected 27 15 12.13.13


Rate description details - dimensions - no of pieces corrected 27 15 12.13.15


Rate description details - volume - volume code corrected 27 15 12.14.5


Rate description details - volume - volume amount corrected 27 15 12.14.6


Rate description details - ULD number - ULD type corrected 27 15 12.15.5


Rate description details - ULD number - ULD serial number corrected 27 15 12.15.6


Rate description details - ULD number - ULD owner code corrected 27 15 12.15.7


Rate description details - shippers load and count - SLAC corrected 27 15 12.16.5


Rate description details - harmonised commodity code corrected 27 15 12.17.5


Rate description details - ISO country code corrected 27 15 12.18.5


Rate description details - service code details corrected 27 15 12.19.2

Routing RTG0010 RTG00 1 S 1 Invalid or missing routing details 27 15 4

Routing RTG0015 RTG01 1 S 1

Invalid or missing routing details - 1st destination/carrier airport city code 27 15 4.2.2



Old MIP Error Code

New MIPError Code

EF Mandatory

ErrorType

AppliesTo

FWB

AppliesTo FHL



CIMPFWB Ver

CIMP FWB Fld

CIMPFHL Ver

CIMP FHL Fld

Routing RTG0020 RTG02 1 S 1 Invalid or missing routing details - 1st destination/carrier carrier code 27 15 4.2.3


Invalid or missing routing details - onward destination/carrier airport city code 27 15 4.3.2


Invalid or missing routing details - onward destination/carrier carrier code 27 15 4.3.3

Routing RTG1010 RTG00C 1 B 1 1 Routing details corrected 27 15 4

Routing RTG1015 RTG01C 1 B 1 1

Routing details - 1st destination/carrier airport city code corrected 27 15 4.2.2


Routing details - 1st destination/carrier carrier code corrected 27 15 4.2.3


Routing details - onward destination/carrier airport city code corrected 27 15 4.3.2


Routing details - onward destination/carrier carrier code corrected 27 15 4.3.3

Shipper SHP0010 SHP00 1 S 1 Invalid or missing shipper details 27 15 5

Shipper SHP0015 SHP01 1 S 1 Invalid or missing shipper details - account number 27 15 5.2.2

Shipper SHP0020 SHP02 1 S 1 Invalid or missing shipper details - name 27 15 5.4.2

Shipper SHP0025 SHP03 1 S 1 Invalid or missing shipper details - street address 27 15 5.5.2

Shipper SHP0030 SHP04 1 S 1 Invalid or missing shipper details - place 27 15 5.6.2

Shipper SHP0035 SHP05 1 S 1 Invalid or missing shipper details - state/province 27 15 5.6.4

Shipper SHP0040 SHP06 1 S 1 Invalid or missing shipper details - ISO country code 27 15 5.7.2

Shipper SHP0045 SHP07 1 S 1 Invalid or missing shipper details - post code. 27 15 5.7.4

Shipper SHP0050 SHP08 1 S 1 Invalid or missing shipper details - contact identifier 27 15 5.8.2

Shipper SHP0055 SHP09 1 S 1 Invalid or missing shipper details - contact number 27 15 5.8.4

Shipper SHP1010 SHP00C 1 B 1 1 Shipper details corrected 27 15 5

Shipper SHP1015 SHP01C 1 B 1 1 Shipper details - account number corrected 27 15 5.2.2

Shipper SHP1020 SHP02C 1 B 1 1 Shipper details - name corrected 27 15 5.4.2

Shipper SHP1025 SHP03C 1 B 1 1 Shipper details - street address corrected 27 15 5.5.2

Shipper SHP1030 SHP04C 1 B 1 1 Shipper details - place corrected 27 15 5.6.2

Shipper SHP1035 SHP05C 1 B 1 1 Shipper details - state/province corrected 27 15 5.6.4

Shipper SHP1040 SHP06C 1 B 1 1 Shipper details - ISO country code corrected 27 15 5.7.2

Shipper SHP1045 SHP07C 1 B 1 1 Shipper details - post code corrected 27 15 5.7.4

Shipper SHP1050 SHP08C 1 B 1 1 Shipper details - contact identifier corrected 27 15 5.8.2



Old MIP Error Code

New MIPError Code

EF Mandatory

ErrorType

AppliesTo

FWB

AppliesTo FHL



CIMPFWB Ver

CIMP FWB Fld

CIMPFHL Ver

CIMP FHL Fld

Shipper SHP1055 SHP09C 1 B 1 1 Shipper details - contact number corrected 27 15 5.8.4

Shipper SHP2010 SHP00 S 1 Invalid or missing shipper details 27 3 6

Shipper SHP2015 SHP02 S 1 Invalid or missing shipper details - name 27 3 6.3

Shipper SHP2020 SHP03 S 1 Invalid or missing shipper details - street address 27 3 6.5.2

Shipper SHP2025 SHP04 S 1 Invalid or missing shipper details - place 27 3 6.6.2

Shipper SHP2030 SHP05 S 1 Invalid or missing shipper details - state/province 27 3 6.6.4

Shipper SHP2035 SHP06 S 1 Invalid or missing shipper details - ISO country code 27 3 6.7.2

Shipper SHP2040 SHP07 S 1 Invalid or missing shipper details - post code. 27 3 6.7.4

Shipper SHP2045 SHP08 S 1 Invalid or missing shipper details - contact identifier 27 3 6.8.2

Shipper SHP2050 SHP09 S 1 Invalid or missing shipper details - contact number 27 3 6.8.4

Shipper SHP3010 SHP00C B 1 1 Shipper details corrected 27 3 6

Shipper SHP3015 SHP02C B 1 1 Shipper details - name corrected 27 3 6.3

Shipper SHP3020 SHP03C B 1 1 Shipper details - street address corrected 27 3 6.5.2

Shipper SHP3025 SHP04C B 1 1 Shipper details - place corrected 27 3 6.6.2

Shipper SHP3030 SHP05C B 1 1 Shipper details - state/province corrected 27 3 6.6.4

Shipper SHP3035 SHP06C B 1 1 Shipper details - ISO country code corrected 27 3 6.7.2

Shipper SHP3040 SHP07C B 1 1 Shipper details - post code corrected 27 3 6.7.4

Shipper SHP3045 SHP08C B 1 1 Shipper details - contact identifier corrected 27 3 6.8.2

Shipper SHP3050 SHP09C B 1 1 Shipper details - contact number corrected 27 3 6.8.4

Sales Incentive Information SII0010 SII00 S 1

Invalid or missing sales incentive information details 27 15 23


Invalid or missing sales incentive details - charge amount 27 15 23.3.1


Invalid or missing sales incentive indication - CASS indicator 27 15 23.5.1

Sales Incentive Information SII1010 SII00C B 1 1

Sales incentive information details corrected 27 15 23


Sales incentive details - charge amount corrected 27 15 23.3.1


Sales incentive indication - CASS indicator corrected 27 15 23.5.1

Special Handling Details SPH0010 SPH01 1 S 1

Invalid or missing special handling code 27 15 25.2.2



Old MIP Error Code

New MIPError Code

EF Mandatory

ErrorType

AppliesTo

FWB

AppliesTo FHL



CIMPFWB Ver

CIMP FWB Fld

CIMPFHL Ver

CIMP FHL Fld

Special Handling Details SPH1010 SPH01C 1 B 1 1 Special handling code corrected 27 15 25.2.2

Shipment Reference Information SRI0010 SRI00 S 1

Invalid or missing shipment reference information details 27 15 27


Invalid or missing shipment reference information details - reference number 27 15 27.3


Invalid or missing shipment reference information details - supplementary shipment information 27 15 27.5-7

Shipment Reference Information SRI1010 SRI00C B 1 1

Shipment reference information details corrected 27 15 27


Shipment reference details - reference number corrected 27 15 27.3


Shipment reference details - Supplementary shipment information corrected 27 15 27.5-7

Special Service Request SSR0010 SSR01 S 1

Invalid or missing Special Service Request 27 15 8

Special Service Request SSR1010 SSR01C B 1 1 Special Service Request corrected 27 15 8

Free Text Description of Goods TXT2010 TXT01 S 1

Invalid or missing Free text description of goods details 27 3 4.3

Free Text Description of Goods TXT3010 TXT01C B 1 1

Free text description of goods details corrected 27 3 4.3


13 Appendix D - Action Plan

13.1 Airline Action Plan – Example. The following details an example of the airline action plan. This report should be put together in conjunction with the IATA e-freight MIP Champion and once approved by the airline MIP champion, loaded to the airline extranet page. The IATA e-freight representative will then be required to monitor progress against the plan.

ZZ Airlines IATA e-freight action plan

Measure Baseline Current status

Target 2007

Number of FWBs required to meet target

Action plan

FWB penetration

47% 48% 50% 50,000 1.Identify top agents who are currently capable of sending FWB messages, but contribute to a shortfall of 50,000 2. Identify trends. Is non-sending relevant to a specific country, airport. 3. IATA will look at same agents performance as reported by other airlines. 3. Collate evidence 4.Arrange meetings/workshop with agents 5.Airline agrees action plan with agents to increase penetration. 6.Monitor progress

Rejected Messages due to syntax errors Messages rejected by airline Business data invalid

6% 5% 2% 10,000 1.Airline/IATA identifies top agents who are currently sending FWB messages, containing syntax related errors and contribute to the total of 10,000 incorrect messages 2. Identify common problems that are contributing to trends. Data entry staff, incorrect charges, description of goods. 3. Collate evidence and send to the agent with solutions. 4.follow up telephone call/meeting to agree action plan with agents to fix problems. 5.Monitor progress

Duplicate messages

9% 8% 0% 60,000 1.Airline/IATA identifies top agents who are currently sending duplicate FWB messages. 2. Collate evidence and send to the agent. 3.follow up telephone call/meeting to agree action plan to fix process. 4.Monitor progress


13.2 IATA Action Plan – Example.

IATA/C2K e-freight action plan (C2K Agents) Measure Baseline Current

status Target 2007

Number of FWBs required to meet target

Action plan

FWB penetration

80% 85% 95% 150,000 1.Identify C2K agents current penetration figures 2. Identify locations/AWBs for which no FWB is being sent 3. Produce league table for distribution to C2K programme management. 4. Report findings to C2K technical working group. Agree action plan for addressing problems. 5.Monitor progress

Rejected Messages due to syntax errors Messages rejected by airline Business data invalid

6% 5% 2% 120,000 1.Identify C2K agents current error rate 2. Identify reasons for message errors 3. Produce league table for distribution to C2K programme management. 4. Report findings to C2K technical working group. Agree action plan for addressing problems. 5.Monitor progress

Duplicate messages

9% 8% 0% 60,000 1.Identify C2K agents current duplicate message % 2. Produce league table for distribution to C2K programme management. 3. Report findings to C2K technical working group. Agree action plan for addressing problems. 4.Monitor progress