Kuala Lumpur FIR Kuala Lumpur and Chennai has successfully - - PowerPoint PPT Presentation

Kuala Lumpur FIR

 Kuala Lumpur and Chennai has successfully

conducted several AIDC trials, collecting useful data

• n systems and connectivity reliability.

 We would be implementing an AIDC version 3

(developed by SELEX).

 We have successfully conducted AIDC training for all

• perational controllers.

 WMKK AIDC Message Address : WMKKAIDC  WMKK ATS Message Address : WMFDYXYF

COP (CO-ORDINATION Point)

NO DATE DESCRIPTION OTHERS

1 24th July 2013 Internal meeting on AIDC between DCA and vendors.

• To discuss readiness of our AIDC system and date to do trial

with Chennai 2 29th July 2013 Another internal meeting to finalize AIDC system and connectivity before set a date for a trial. 3 31st July 2013 (0500 UTC) 1st AIDC trial with Chennai.

• Using INTERIM environment

Successful with minor adjustment 4 1st August 2013 2nd AIDC trial with Chennai.

• Error with connectivity
• Using INTERIM environment
• Check system and connectivity
• CRC error

5 17th Sept 2013 3rd AIDC trial with Chennai.

• CRC error
• Using INTERIM environment

6 21st Oct 2013 Detected that CRC error due database problem 7 30th – 31st Oct 2013 AIDC training

• “Train the trainers”

4 person represent for 4 shift 8 20th Dec 2013 4th AIDC trial with Chennai.

• CRC error resolved
• Using INTERIM environment
• Error on RMK/62/ (generic error)
• Error on RMK/11/8 (invalid flight rule)

9 9th – 10th Jan 2014 5th AIDC trial with Chennai.

• Using INTERIM environment
• Connectivity intermittent
• Agreed with Chennai to enable the AIDC

line to check the connectivity (AFTN). 10 22 Jan 2014 6th AIDC Trial with Chennai.

• Trial using live traffic
• LRM for EST and MAC
• WMKK FDP did alteration on AFTN message

received from Chennai SELEX investigate the error 11 28th Jan 2014 7th AIDC trial with Chennai.

• Trial using live traffic
• No LRM received
• Chennai reported that they received 2 LRM

Chennai email the error and SELEX investigate, than fix it. 12 March 2014 Installed new AIDC software into the system but the connection was in OFLINE mode. 13 19, 20, 21st March 2014 8th AIDC trial using live traffic with Chennai.

• Unsuccessful due connectivity problem

We found out our cable was bend and some of the pin was broken (RS 232 cable). 14 25th March 2014 9th AIDC trial using live traffic

• Successful

15 1st May 2014 Introduction to new KL ATCC system and new WMKK airspace structure due to additional 3rd runway in KLIA (focusing now to SPA – Simultaneous Parallel Approach) Spotlight focusing into SPA, MH370 and MH17. 16 11, 12, 18 & 19 August 2014 AIDC training to all controllers. 17 Early September 2014 Final trial with Chennai ( 1 month or less) We would also like to propose that these trials be extended for another month before a final trial is conducted prior to full implementation(for familiarization and final system check). 18 Early October 2014

• LOA between WMKK and Chennai.
• Implement AIDC.

 An update on some teething problems encountered during

• trials. Our AIDC system does not provide an indication to

the operational controller should there be a time revision. Our vendors (SELEX) are working to rectify this problem, we would therefore, like to propose to Chennai, voice coordinate via direct speech line any time revision in excess of 3 minutes.

 We would also like to propose that these trials be extended

for another month before a final trial is conducted prior to full implementation(for familiarization and final system check).

 During the period of the extended trials, voice coordination

would still be mandatory, but it would be to verify the accuracy and validity of the information received.

Thank You