Kuala Lumpur FIR
Kuala Lumpur and Chennai has successfully conducted several AIDC trials, collecting useful data on systems and connectivity reliability. We would be implementing an AIDC version 3 (developed by SELEX). We have successfully conducted AIDC training for all operational controllers.
WMKK AIDC Message Address : WMKKAIDC WMKK ATS Message Address : WMFDYXYF
COP ( CO-ORDINATION Point )
NO DATE DESCRIPTION OTHERS 24 th July 2013 1 Internal meeting on AIDC between DCA and vendors. • To discuss readiness of our AIDC system and date to do trial with Chennai 29 th July 2013 2 Another internal meeting to finalize AIDC system and connectivity before set a date for a trial. 31 st July 2013 1 st AIDC trial with Chennai. 3 Successful with minor adjustment • (0500 UTC) Using INTERIM environment • 1 st August 2013 2 nd AIDC trial with Chennai. 4 Check system and connectivity • • Error with connectivity CRC error • Using INTERIM environment 5 17 th Sept 2013 3 rd AIDC trial with Chennai. • CRC error • Using INTERIM environment 21 st Oct 2013 6 Detected that CRC error due database problem 30 th – 31 st Oct 2013 7 AIDC training 4 person represent for 4 shift • “Train the trainers” 20 th Dec 2013 4 th AIDC trial with Chennai. 8 • CRC error resolved • Using INTERIM environment • Error on RMK/62/ (generic error) • Error on RMK/11/8 (invalid flight rule)
9 th – 10 th Jan 2014 5 th AIDC trial with Chennai. 9 • Using INTERIM environment • Connectivity intermittent • Agreed with Chennai to enable the AIDC line to check the connectivity (AFTN). 6 th AIDC Trial with Chennai. 10 22 Jan 2014 SELEX investigate the error • Trial using live traffic • LRM for EST and MAC • WMKK FDP did alteration on AFTN message received from Chennai 28 th Jan 2014 7 th AIDC trial with Chennai. 11 Chennai email the error and SELEX investigate, than • Trial using live traffic fix it. • No LRM received • Chennai reported that they received 2 LRM 12 March 2014 Installed new AIDC software into the system but the connection was in OFLINE mode. 19, 20, 21 st March 2014 8 th AIDC trial using live traffic with Chennai. 13 We found out our cable was bend and some of the • Unsuccessful due connectivity problem pin was broken (RS 232 cable). 25 th March 2014 9 th AIDC trial using live traffic 14 • Successful 15 1 st May 2014 Introduction to new KL ATCC system and new Spotlight focusing into SPA, MH370 and MH17. WMKK airspace structure due to additional 3 rd runway in KLIA (focusing now to SPA – Simultaneous Parallel Approach) 16 11, 12, 18 & 19 August AIDC training to all controllers. 2014 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
Recommend
More recommend
