03-Apr-2014

DISH22 - CHANGE ADVICE

This document is intended to offer guidance to all stakeholders using the IATA DISH standard, regarding the upgrade
to the new DISH Revision 22:
RET Reporting Systems (using RET & TI formats)
Airlines (using HOT, CSI, TI, CSP, and/or MSA formats)
Agents (using HOT format)
Card acquirers (using CSI and/or CSP formats).
(A separate Change Advice has also been provided to IATA DPCs and other IATA systems using DISH).
Note that the objective this year is for all stakeholders to complete evaluation, development and internal testing for
DISH22 **by 31-Dec-2014**.
End-to-end testing and implementation will then take place starting in Jan-2015 (see plan on following pages).

Please do not hesitate to ask! if any questions/clarifications, or if you notice any typos/inconsistencies in DISH22.
Many thanks in advance for your help and cooperation with DISH22 implementation!
Best regards,
Ron COLE
Manager DPC Systems Development
IATA Geneva
dish22@iata.org

DISH22 - CHANGE ADVICE

1. To align with industry standards, and for all stakeholders to benefit from the highest quality and most
complete data available, all Systems using IATA DISH formats must upgrade to DISH 22.
After implementation of DISH22 (see plan on next page), previous versions of DISH will no longer be supported.

2. Included in the ZIP file with this document, please find attached the DISH22 publication effective 01-Jan-2014 (also
available at www.iata.org/dish).

3. Also included in the ZIP file with this document, please find attached various typos/clarifications that have been
noted since the publication (despite exhaustive review/proofreading); to be included in a formal DISH Bulletin at an
appropriate time during 2014.

4. DISH22 is a major revision. Please refer to the Preface for the high-level enhancements since the last DISH20.3,
as well as to the Summary of Changes for more details.
Especially note:

with the exception of the # symbol, all other change symbols have exceptionally not been feasible/included, due to
the immense volume of amendments.

records have been restructured for improved flexibility (eg. blank space has been consolidated at the end of the
record for RET & HOT).
the Summary of Changes should be reviewed VERY carefully; eg. for attribute/length changes for some fields etc.
due to so many changes, it is required to do a very careful/meticulous page-by-page review and comparison with
DISH20.3 for the entire DISH22 document (at least those parts relevant to your System).
for RET Reporting Systems, all RET validations should also be reviewed very carefully; for additions/changes (eg.
th
CUTP decimals), as well as removal of obsolete validations (eg. TDNR ADM/ACM 4 position = 6/8).

5. The model of DISH20.3 will be followed; ie. test and implement in all BSPs as per a set plan. IATA Geneva will
again coordinate the plan and implementation with all stakeholders (see next page).

DISH22 - Change Advice - 03apr14.docx

Page 2 of 3

DISH22 - HIGH-LEVEL TESTING & IMPLEMENTATION PLAN (overview for ALL stakeholders):
6. By 01-May-2014:
All stakeholders to evaluate DISH22, and advise IATA if any questions/problems with DISH22, or with this High-Level
Testing & Implementation Plan.

7. By 01-Sep-2014:
IATA to advise all stakeholders of Detailed Testing & Implementation Plan for each BSP country (eg. with more
precise dates, test file naming conventions and delivery methods, etc).

8. **By 31-Dec-2014**:
All stakeholders to complete development and internal testing for DISH22.

9. From 01-Jan-2015 to 01-Jul-2015:

a) similar to DISH20.3 implementation, all RET Reporting Systems (global+local) to provide a test DISH22 RET/TI
(full parallel of DISH20.3 Production), for one full day's transactions, based on a to-be-agreed/same reporting period
(coordinated by IATA), for each one of 14 "beta" BSP countries, covering all Regions/DPCs/softwares:
AME(Africa & Middle East): SA,ZA (Maestro)
Americas: BR,MX (Maestro); CA (ISIS)
AsiaPac: AU,IN,JP (ISIS); KR (KEB)
Europe: RU,SE (ISIS); UK (Maestro); DE (TSystems)
NorthAsia: CN (ISIS).
b) all local RET Reporting Systems (ie. not ABAC, AGTD, EARS(BSPlink), FLGX, GDSL, SABR, WEBL, WSPN) will
also be identified in all other BSP countries, and similar full parallel DISH22 RET/TI testing will be done with these, for
one full day's transactions, based on a to-be-agreed reporting period (coordinated by IATA).
c) For all RET/TI testing, IATA will check proper functioning of the DISH22 RET/TI loading and validations, with the
DPCs and the RET Reporting Systems.
d) After successful RET/TI testing, IATA will coordinate test DISH22 outputs with the DPCs. This will include the
following test partners:
- 2-3 airlines HOTs in each of the above BSP countries
- ALL Agent recipients of Agent HOTs in ALL countries (based on DISH20.3 RET input if required)
- ALL Airline & Card acquirer recipients of CSIs in ALL countries (based on DISH20.3 RET input if required)
- any other stakeholder requesting a test output in ANY country (based on DISH20.3 RET input if required).
e) After acceptance of the test outputs with the test partners, IATA will coordinate DISH22 implementation in each of
the 14 beta BSP countries above.

10. From 01-Jul-2015 to 01-Dec-2015:

After all the above testing is successful in all the applicable BSP countries, and after successful implementation in the
14 beta BSP countries, IATA will coordinate DISH22 implementation in all other BSP countries in a "big bang"
approach; in regional groups over a to-be-agreed timeframe (coordinated by IATA).

11. New DISH22 functionalities such as Coupon-level taxes and Netting reporting could obviously not be part of full
parallel testing with DISH20.3. Testing criteria for these are still being defined, and will be advised separately.

DISH22 - Change Advice - 03apr14.docx

Page 3 of 3