Cargo Messaging Working Group

Face to Face Meeting, Montreal

IATA office, Tuesday 9th to 10th July 2019

Tahir Syed, Manager, Cargo Technology

Messaging Working Group

Messaging Working Group Participants

Sr.# Name Company

1 Amy Ozawa United Airlines

2 Axel Klein (Chair) Lufthansa Cargo AG

3 Deepak Jeswani Lufthansa Cargo AG

4 Dante Favero Swiss World Cargo

5 Chris Lopez Cargolux

6 Christopher Creado Qatar Airways

7 Klaas Kurz DB Schenker

8 Alessandro Rivolta ALHA Airport Services

9 Marc Pilmann Swiss World Cargo

10 Michael Weber K+N

11 Allan Holmstadt Delta Airlines

12 Karel Duran AF/KLM

13 Matthias Hurst Agility

Sr.# Name Company

14 Martin Skopp Riege

15 Andreas Rhodes Riege

16 Eugene Ng GLS HK

17 Laura Kvistad Unisys

18 Bernhard Erren CHAMP Cargosystems

19 Filippo Passeggieri CCS Italy

20 Jos Nuijten Descartes

21 Nicolas Carlone IATA

22 Teresa Divito IATA

23 Francois Massey IATA

24 Tahir Syed IATA

Summary of Discussions (1/11)1. Agenda Reviewed and Approved

2. Round Table Participants Introduction

3. Reviewed Cargo-XML Developments(Membership, Messages, Manual & Toolkit)a. DL and CV will reapply for membership

b. 20 Messages developed and published

c. Toolkit 7th Edition published (1st web update released)

d. PLACI Manual 1st Edition published

4. Reviewed and approved last meeting minutes

5. IT Service Providers attending the meeting are offering Cargo-XML based solutions

6. Implementation

status - Members

LX XFWB and XFZB end of Aug 19 DL Live: XFWB, XFZB, XFHL, XGRQ, XFSU

GLS HK Live: XFWB, XFZB, XFSU, XFHL, XFNM. XFFR in process

Agility Live: XFFR, XFSU, XFNM

DB Schenker Live: XFZB, XFWB UA Not Implemented yet

AF/KLM Live: XFWB, XFZB, XFSU, XFUM, XFFM, XCSN, XFNM, XFRQ. surprise increase in XML customers

QR Live: XFWB, XFZB, XFFM, XFSU, XGRQ, XFNM. XRAF. XRCP in progress

K+N Live: XFWB, XFZB, XFNM. XFSU in process LH Live, XFWB, XFZB, XFSU, XSDG. XCSN in process

CV Via Conversion: XFWB, XFZB and XFFM ALHA Live: XFWB, XFZB

Summary of Discussions (2/11)7. IATA Publication demonstrated Cargo-XML scorecard proposal and group

provided following feedback:a. Should be extended to all stakeholders including IT companies.

b. One IT company should be able handle/manage multiple airlines (update data for)

c. Toolkit can include a link to the scorecard

d. Each record must have a date when it was updated

e. Upon update, a preview must be shown before data is published

f. Vetting/Registration process need to be in place

g. Customer type must be included

h. View should be instantly available for public while update is private (password protected)

i. Notification service will be included as well as there will be a link to view the recent updates

j. GDPR issue must be addressed

k. Data Export must be possible from the tool

l. Pricing discussion is out of scope

m. Latest version will be displayed on top however option will be there to drill down

n. EPIC and scorecard can be merged

Summary of Discussions (3/11)8. IATA Cargo Product Manager noted the issue of limited accessibility of

toolkit within the existing customers.

9. IATA announced Cargo-XML Manual and Toolkit accessibility to wider audience:a. 70-80% discount will be offered on 7th Edition from mid-July to end-August.

b. A promo code will be provided by IATA to avail discount and will be applicable on all IATA products related to Cargo-XML

c. Group can further share the promo code to its stakeholders

d. IATA will run Email/HTML campaign industry-wide

10. AF/KLM provided positive feedback on floating license and encouraged the group to use floating license.

11. Request for long term license (rather than annually) was turned down as IATA infrastructure doesn’t support that.

Summary of Discussions (4/11)12. XML Transport Movement Message

a. Reviewed functionality of MVT, FDM and STM messages

b. Endorsed approach for having single message covering functionality of multiple messages.

c. Group reviewed the specification and schema for XML Transport Movement Message.

d. Group decided to include the Flight diversion functionality in the XML Transport Movement Message.

e. Group noted the need for new code list to support XML Transport Movement Message.

f. Group agreed on specification and schema of the XML Transport Movement Message.

g. Group approved the new code list for XML Transport message

h. Group agreed on:

i. Acronym : XTMV,

ii. Document Code: 265,

iii. Message function values: Create, Respond

i. PoC/Pilot participants: Descartes, LH. Other members will check internally and advise

j. Customs to be inquired if interested in PoC

Summary of Discussions (5/11)13. Flight Plan/Load Advise Message was discussed.

a. Group noted a big difference between load advise for PAX flight and a Freighter.

b. Freighter is more complicated due to special load, live animals, pharma etc.

c. It was noted that airline send FBL and then loading instructions are provided in free text email

d. Current examples are straight forward and simple. These doesn’t contain information exchanged through email such as available capacity etc.

e. Group reviewed some complex examples shared by ALHA Airport.

f. Next step to check with ICHC if:

i. an updated XFBL messages with additional information or

ii. dig down to details and try to capture complete requirements.

14. NOTOCa. Airlines are using customized NOTOC messages

b. Standardizing the NOTOC is challenging but achievable.

c. Not only DG but special cargo, live animal, crew container, val cargo etc.

d. A detailed analysis of existing customized NOTOCs will be required.

Summary of Discussions (6/11)15. PLACI

a. Reviewed Timelines for EU-ICS2 Postal and Express filing 2021, Airlines 2023, Rail/Road 2025

b. Group noted that Industry is fragmented and Customs initiatives are fragmented hence IATA role is key to standardize the requirements.

c. Group noted that countries other than US,CA,EU and UKPLACI are considering PLACI.

d. Mail PLACI initiative was discussed.

e. CARDIT to XFWB and XFHL conversion solution was reviewed.

f. Pilots – Descartes, DL interested

g. Group Position on Mail PLACI: Assessment complete is needed on CARDIT Level, The paper by UPU was reviewed and approach recommended by UPU is not acceptable.

h. Mail General Principles were reviewed and agreed by the Group.

i. Group concerns were noted as follows:

i. Manifesting Mail/Postal AWB on cargo manifest while the mail is handled by mail handler

ii. Mail Referral Processes: Screening/Do Not Load must be handled by airlines

iii. AXEL will discuss these concerns with the EU during the next meeting.

Summary of Discussions (7/11)16. Sample Messages Review

a. XFNM containing FWB 16 must not be published

b. XGRQ for XFBL approved

c. XGRQ for XFSU approved

d. XFNM for Master Air Waybill approved with Document Name to be updated and Namespace recommendation to be followed

e. XFNM for Direct Air Waybill approved with Document Name to be updated and Namespace recommendation to be followed

f. AF/KLM to provide update samples with brief description.

g. AF/KLM to provide some XFNM samples with reason code included.

h. Descartes provided some samples for review as well.

Summary of Discussions (8/11)17. XCSN Clarification

a. LH proposal accepted for data type and data length change,

b. Three new conversion rules to be applied:

i. Customs ID to be used 999 if not available

ii. Piece must set to 0 if not available

iii. Nominated Party will be identified by two letter role code i.e. FB

c. XCSN will be updated within the same version and the definition of role code will be included in the toolkit.

18. Gaps between GHA and Airline System:

a. Group noted paper presented by Swissport to ICHC to identify the gaps between GHA and airline systems

b. Other than political and commercial reasons, Non availability of airline customized messages with GHA such as

FDM, NOTOC, Customs filing ACAS could be an issue sometimes.

c. ALHA Airport Services Proposed to include Milan (MXP) for gap analysis.

d. United Airlines proposed to include Houston (IAD) for gap analysis.

Summary of Discussions (9/11)19. Street Address for XFWB and XFZB

a. New Business Rules introduced i.e. While converting XFWB/XFZB, if street address is not available then PO Box number will be used

in street address.

b. KL and IATA Secretariat will work to investigate if conditional fields (in the specs) can be restricted in the schema.

c. While conversion from IMP to XML, Street Address concatenation is recommended when there are two lines of Street address

20. Currency Code Update

a. There is need for a robust mechanism for updating the country and currency code as soon as there is an update from ISO.

b. KL and IATA will discuss and come back with a strategy

21. Non-CASS Agent and XFWB

a. IATA, Descartes and AF/KLM will have a conference call with the e-AWB link team to discuss and resolve the issue.

22. Group reviewed the CSC Notices

17. The Group urged IATA to improve the processing of change requests for CSC adoption avoiding unnecessary delays

23. The Group noted the OCI and OSI status codes for Cargo-XML messages are already available in the

code list

24. The Group put on hold the request for JSON samples of existing Cargo-XML messages

Summary of Discussions (10/11)25. XFBL – A new optional field will be included for split pieces and a new version of XFBL will be

produced.

26. ALHA Airport Services will draft a change request for a special handling code for Vehicles

27. The request for exchanging Other Local Charges (other than XFWB message) was not approved by

the Group.

28. The request for removing AssociatedReferenceDocument tag from multiple places(House level and

rating level) in XFZB was not approved by the Group.

29. XFZB new version will be published as per agreed changes

30. Implementation Strategies White Paper -> Cargo-XML Scorecard need to be updated

31. OCI table must be updated with Cargo-XML examples

32. Change Request approved for Cargo Non Stackable special handling code with code NST.

Summary of Discussions (11/11)33. Cargo-XML Accreditation Program being developed

a. Improve Data Quality

b. Standard implementations

c. Audit checklist

d. Linked with scorecard

34. EPIC Discussion

a. IATA Secretariat provided a status update on EPIC development

b. EPIC will be available in Sept

c. There were questions about Access control, Permanent ID format, Distribution Process

d. Group discussed the need for permanent code for Non IATA Agents (Similar to IATA Agent code)

35. One Record Initiative Update

a. Engagement through Pilots

b. API and Security Layer Developments

c. Data Modelling Improvements

36. Unisys interested in getting more details about the One Record Initiative.

37. Next f2f meeting end January/beginning February in Geneva/Madrid.

Thank You

For further information please contact syedt@iata.org