1. INDIA AIDC IMPLEMENTATION STATUS AND ISSUES
Presented by
Airports Authority of India
SIP AIDC Seminar October 2014

2. AIDC in India
India initiated AIDC operational trials after commissioning of automation systems at major ATS units in India.
Successful testing has been carried out between major ATC centres in India and plans are now underway to operationalize AIDC in a phased manner.
Extensive trials have been carried out between dissimilar automations systems available at various ATS units
India has also drawn up plans to establish AIDC with adjacent ATS Units of neighboring states in the sub- region. In some cases, successful trials underway.
Currently using APAC AIDC ICD version 3.0

3. ATM Automation systems in India
Raytheon (AT3) Delhi, Mumbai
Raytheon (AT3+) Chennai
Indra (Aircon2100) at Kolkata and upcoming in Delhi as replacement
Indra (Aircon2100) at 38 mid/small sized airports
Selex ATM System at Bengaluru and Hyderabad

4. AIDC Status (International)
Delhi (AT3) AIDC with
Lahore
Karachi Under testing. Working one sided in favour of Delhi
Varanasi
Kathmandu Readiness at Kathmandu end awaited
Mumbai (AT3) AIDC with
Muscat Muscat using OLDI.
Karachi Initial testing carried out.
Seychelles
Sanaa Planned
Mauritius
Mogadishu
Chennai (AT3+) AIDC with
Kuala Lumpur Successful trials carried out.
Male(Maldives) Ready for testing.
Colombo Initial Testing in March13. To start again after adaptation changes
Jakarta, Yangon Not ready for AIDC testing

5. AIDC Status (International)
Kolkata
Kathmandu
Dhaka No Automation system at other end.
Yangon
Ahmedabad
Karachi Successful trials carried out.

6. Chennai – Kuala Lumpur
During initial testing, it was observed that ABI messages sent from Chennai were rejected by Kuala Lumpur system citing CRC errors.
After detailed analysis at Chennai, it was determined that the rejection was due to incorrect calculation of checksum by the Kuala Lumpur system.
Kuala Lumpur Automation system was replacing the alignment characters with space characters prior to CRC calculation leading to discrepancy in the CRC checksum.
After sorting out the CRC errors by Kuala Lumpur, the AIDC message exchange was successful.
Both the States are working together to operationalize AIDC at the earliest after addressing a few minor issues.
LOA expected in December 2014.

7. Ahmedabad - Karachi Trial operations commenced on 05.06.2014.
During the initial phase of testing, it was observed that messages were rejected due to route errors and mismatch in the coordination timing.
Coordination protocol dialogue time out was observed. After synchronizing Karachi AMSS/AFTN system time with India’s AMSS/ AFTN system time, the AIDC messages could be successfully exchanged between the two systems.
Further trial of AIDC for limited hours is in progress between Karachi and Ahmedabad.
Lessons learnt for implementation of AIDC with other ATSUs.

8. AIDC Status (National)
Delhi (AT3) AIDC with
Ahmedabad (Aircon2100)
Nagpur (Aircon2100) Implemented
Varanasi (Aircon2100)
Mumbai (AT3) AIDC with
Chennai (AT3+) Under trial operation
Suspended due to adaptation changes
Chennai (AT3+) AIDC with
Mumbai (AT3+) Under trial operation
Bengaluru (Selex)
Hyderabad (Selex) Planned and configured
Trivandrum (Aircon2100)
Kolkata (Aircon Icon) AIDC with
Varanasi (Aircon2100) Planned

9. AIDC Status (National)
Bangaluru (BIAL) (Selex)
Hyderabad (HIAL) (Selex) Connectivity configured & Satisfactory testing done.
Mangalore (Aircon2100)
Chennai (AT3+)

10. AIDC Implementation Issues
Diverse ATM systems at ATSUs
Some issues in Aircon2100 (under resolution)
Non display of NO, CO in radar data block.
Generation of MAC msg on termination of FPL.
Route terminator "T" to be configured which affects AMAN profile/trajectories of the pairing stations
When the actual boundary ETO in an ABI varies from the system calculated ETO (based on the EOBT) of the overflying aircraft, the system rejects the ABI message with an LRM.
SSR codes of pairing unit sometimes do not match due to limited available codes.

11. Challenges in AIDC Implementation
Interoperability between diverse ATM Systems.
Implementation and system design issues attributed to revision of AIDC ICD versions.
Need for close bilateral cooperation between the concerned States for expeditious and successful implementation of AIDC
Bi-lateral agreements must be in place through MOUs or LOAs between the member states and may be reviewed to meet the intended objectives.
Compatibility with existing Automation system using OLDI, replacement of OLDI with PAN Regional ICD or co-existence of OLDI and AIDC applications are key issues that may have to be addressed by some of the states for harmonized AIDC implementation.
PAN regional ICD shall require synchronization of technology refresh cycles and maintaining backward compatibility of the automation systems for smooth exchange of AIDC messages.

12. Suggestions
HMI for AIDC functionalities may be considered to be included in AIDC Guidance Material.
To avoid prohibitive cost of frequent ATM Automation systems upgrade, backward compatibility of ICD versions should be assured.

13. Thanks for Kind Attention