FIFTEENTH MEETING OF THE SADIS OPERATIONS GROUP (SADISOPSG/15) (Paris, France, 26 to 28 May 2010)

Transcription

1 SADISOPSG/15-REPORT FIFTEENTH MEETING OF THE SADIS OPERATIONS GROUP (SADISOPSG/15) (Paris, France, 26 to 28 May 2010) INTERNATIONAL CIVIL AVIATION ORGANIZATION

2 The designation and the presentation of material in this publication do not imply the expression of any opinion whatsoever on the part of ICAO concerning the legal status of any country, territory, city or area of its authorities, or concerning the delimitation of its frontiers or boundaries.

3 History of the Meeting i-1 TABLE OF CONTENTS Page List of SADISOPSG decisions... i-3 List of SADISOPSG conclusions... i-3 List of conclusions for consideration by the ICAO planning and implementation regional groups... i-3 Agenda Item 1: Opening of the meeting Place and duration Attendance Chairman and officers of the Secretariat Agenda Item 2 Organizational matters Adoption of working arrangements Adoption of the agenda Agenda Item 3 Follow-up of SADISOPSG/14 Conclusions Agenda Item 4: Operation of the SADIS SADIS management report SADIS focal points Operational efficacy of SADIS SADIS inventory SADIS implementation Agenda Item 5: Content of the SADIS broadcast OPMET information: WAFS forecasts Agenda Item 6: Development of the SADIS Report of the SADISOPSG Gateway Development Team Report of the SADISOPSG Strategic Assessment Team Report of the SADISOPSG Technical Developments Team SADIS Internet-based FTP Service Agenda Item 7: Long-term planning of SADIS Agenda Item 8 The SADIS User Guide Agenda Item 9 Future work programme Agenda Item 10 Any other business Appendix A List of participants... A-1 Appendix B SADIS operational focal points... B-1 Appendix C SADIS Inventory... C-1 Appendix D Non-AOP aerodrome to be deleted from FASID Table MET 1A and MET 2A D-1

4 i-2 SADISOPSG/14 Appendix E Summary of the SADIS strategic assessment tables: current and projected data volumes E-1 Appendix F Proposed Secure SADIS FTP Service Registration Form... F-1 Appendix G SADIS long-term plan for the years 2011 to G-1 Appendix H Deliverables, Executive Summaries and task teams of the SADISOPSG... H-1

5 History of the Meeting i-3 LIST OF SADISOPSG DECISIONS Decision 15/1 Follow-up of the SADISOPSG/14 conclusions Decision 15/3 SADIS efficacy questionnaire Decision 15/15 Retention of the X25 Protocol for the Exeter to Whitehill segment of the SADIS 2G Decision 15/16 Retention of existing capacity of fixed lines between Exeter and Whitehill Decision 15/17 Naming of the secure version of SADIS FTP (SADIS FTP enhancement Phase 2 to Secure SADIS FTP Decision 15/20 SADIS long-term plan Decision 15/23 Amendments to Chapters 1 to 7 and Appendices B and H of the SADIS User Guide Decision 15/24 Future work programme of the SADISOPSG LIST OF SADISOPSG CONCLUSIONS Conclusion 15/2 Update of the list of SADIS focal points Conclusion 15/4 Annual statement of operational efficacy of SADIS 2009/ Conclusion 15/5 SADIS Inventory Conclusion 15/6 Revision of Annex 1 concerning OPMET information from non-aop aerodromes Conclusion 15/7 Inclusion of Nuclear Emergency Message in SADIS Conclusion 15/8 Implementation of the correct format of SIGMET Conclusion 15/9 Harmonization of the OPMET content of the SADIS and ISCS broadcasts Conclusion 15/10 SADIS Strategic Assessment Tables Conclusion 15/11 SADIS Strategic Assessment Tables inclusion of expected GRIB1, GRIB2, PNG and BUFR data volumes Conclusion 15/12 SADIS 2G future bandwidth requirements Conclusion 15/13 Further tests over SADIS 2G of GRIB2 data to enable workstation vendors to develop and test their systems Conclusion 15/14 Operational transmission of GRIB2 WAFS forecasts over the SADIS 2G broadcast Conclusion 15/18 Development of Secure SADIS FTP service ( Phase 2 ) Conclusion 15/19 Implementation of Secure SADIS FTP service registration/re-registration process Conclusion 15/21 Consultation of SADIS user States and users concerning the need for continued satellite broadcast beyond Conclusion 15/22 Back-up to the Secure SADIS FTP service Conclusion 15/25 Implementation of corrective actions to eliminate data losses in the SADIS 2G transmission LIST OF CONCLUSIONS FOR CONSIDERATION BY THE ICAO PLANNING AND IMPLEMENTATION REGIONAL GROUPS Nil

6 SADISOPSG/15 Report on Agenda Item Agenda Item 1: Opening of the meeting 1.1 Place and duration The fifteenth meeting of the SADIS Operations Group was held at the European/North Atlantic (EUR/NAT) Regional Office, Paris, France, 26 to 28 May The meeting was opened on 26 May 2010 at 1000 hours by Mr. G. Firican, Deputy Regional Director, ICAO EUR/NAT Regional Office, who reviewed the agenda of the SADISOPSG and welcomed it to the EUR/NAT Regional Office, and by Dr. T. van Stijn, the Chairman of the group, who highlighted the group s main tasks. 1.2 Attendance The list of participants is given in Appendix A. 1.3 Chairman and officers of the Secretariat The Chairman of the group, Dr. T. van Stijn, presided over the meeting throughout its duration Dr. O. M. Turpeinen, from ICAO Headquarters, Montréal, was the secretary of the meeting, assisted by Mr. G. Brock from the EUR/NAT Regional Office, Paris.

7 SADISOPSG/15 Report on Agenda Item Agenda Item 2: Organizational matters 2.1: Adoption of working arrangements The meeting adopted appropriate working arrangements.

8 SADISOPSG/15 Report on Agenda Item Agenda Item 2: Organizational matters 2.2: Adoption of the agenda The following agenda was adopted: Agenda Item 1: Agenda Item 2: Opening of the meeting Organizational matters 2.1: Adoption of working arrangements 2.2: Adoption of the agenda Agenda Item 3: Agenda Item 4: Follow-up of SADISOPSG/14 conclusions Operation of the SADIS 4.1: SADIS management report 4.2: SADIS focal points 4.3: Operational efficacy of the SADIS 4.4: SADIS inventory 4.5: SADIS implementation Agenda item 5: Content of the SADIS broadcast 5.1: OPMET information 5.2: WAFS forecasts Agenda item 6: Development of the SADIS 6.1: Report of the SADISOPSG Gateway Development Team 6.2: Report of the SADISOPSG Strategic Assessment Team 6.3: Report of the SADISOPSG Technical Developments Team 6.4: SADIS Internet-based FTP Service

9 SADISOPSG/ Report on Agenda Item 2.2 Agenda item 7: Agenda item 8: Agenda item 9: Agenda item 10: Long-term planning of SADIS The SADIS User Guide Future work programme Any other business

10 SADISOPSG/15 Report on Agenda Item Agenda Item 3: Follow-up of SADISOPSG/14 Conclusions 3.1 The group recalled that the SADISOPSG/14 Meeting had formulated seventeen conclusions and eight decisions (with no follow-up required). No draft conclusions had been formulated for consideration by ICAO planning and implementation regional groups (PIRGs). 3.2 The group was pleased to note that action on all the conclusions may be considered completed; therefore, the group formulated the following decision: Decision 15/1 Follow-up of the SADISOPSG/14 conclusions That, the follow-up action on the SADISOPSG/14 conclusions be considered completed.

11 SADISOPSG/15 Report on Agenda Item Agenda Item 4: Operation of the SADIS 4.1: SADIS management report The group noted that, in accordance with Conclusion 7/1, the SADIS Provider State had prepared a management report which had been placed on the ICAO SADISOPSG website more than two months prior to this meeting. The group expressed its compliments to the SADIS Provider State for providing a detailed and informative report on the web. The group was pleased to note that the complete management report included statistics on the non-scheduled OPMET messages received at the SADIS uplink station (as called for by Conclusion 8/8) and a list of aerodromes, corresponding to Annex 1 to the SADIS User Guide, whose OPMET data had not been received at the SADIS uplink station (as called for by Conclusion 8/7 b)) A concise summary of the management report highlighting the main issues and developments that had taken place between March 2009 and February 2010 was noted by the group. No issues requiring particular attention by the SADIS Provider State were singled out.

12 SADISOPSG/15 Report on Agenda Item Agenda Item 4: Operation of the SADIS 4.2: SADIS focal points The group recalled that the PIRGs had endorsed the SADISOPSG/4 draft conclusion concerning the nomination by SADIS user States of SADIS operational focal points; such a list was considered to provide useful contacts for the SADIS Provider State and the ICAO regional offices to resolve issues regarding, inter alia, missing or incorrectly formatted messages and headers. The current list of focal points, updated by the Secretary based on a consultation with all SADIS user States in response to Conclusion 14/2, is given in Appendix B to this report In view of the importance of the list of SADIS focal points, it was agreed that ICAO should consult all the SADIS user States to ensure that the information was current. The group reviewed the list of SADIS operational focal points and formulated the following conclusion: Conclusion 15/2 Update of the list of SADIS focal points That, the Secretariat consult with all the SADIS user States in order to update the list of the SADIS focal points in time for the dispatch of the SADIS efficacy questionnaire (20 December 2010).

13 SADISOPSG/15 Report on Agenda Item Agenda Item 4: Operation of the SADIS 4.3: Operational efficacy of the SADIS Results of the consultation It was recalled that, in accordance with SADISOPSG Conclusions 1/4 and 2/3, the group had agreed to provide an annual statement of SADIS operational efficacy to the SADIS Cost Recovery Administrative Group (SCRAG), based on the views of States/users on the subject, solicited by ICAO prior to each meeting. The Secretariat had circulated the questionnaire to all States under the SADIS footprint and to the Agence pour la Sécurité de la Navigation Aérienne en Afrique et à Madagascar (ASECNA). To improve the response rate of the annual SADIS questionnaire, the questionnaire had been placed on the SADISOPSG website in an interactive format and sent, in addition to users and States, to the SADIS focal points, in response to Conclusion 6/2. The group was pleased to note that the number of replies had substantially increased from the last few years, i.e. 57 compared to 44 and 48, in 2009 and 2008, respectively A tabulated summary, including specific comments, had been compiled by the Secretariat based on the completed questionnaires returned by States. In accordance with Decision 9/3, the summary had been subsequently forwarded to the SADIS Provider State which had prepared, on behalf of the SADISOPSG Operational Efficacy Assessment Team, a report on the operational efficacy, as called for by Decision 4/4. The group was pleased to note that all the issues raised by SADIS users had been addressed by the SADIS Provider State in this report An analysis of the completed questionnaires indicated the following (the statistics for year in brackets, in accordance with Conclusion 6/3; indicated in percentage, out of a total of 57 and 44 replies received from States, respectively, rounded to the nearest 5 per cent): a) Concerning the SADIS 2G satellite broadcast: 1) 10 (10) per cent experienced signal quality problems; 2) 90 (85) per cent reported good availability of WAFS bulletins in the GRIB code; 3) 90 (85) per cent reported good availability of WAFS bulletins in the BUFR code; and 4) 95 (85) per cent reported good availability of OPMET messages; and b) concerning the reliability of VSAT receiving equipment: 1) 95 (not available) per cent considered it to be good ; and 2) 10 (10) per cent of receivers had to be returned for repairs; and c) concerning the SADIS FTP service (statistics not available for 2008/2009): 1) 10 per cent experienced problems in the service quality;

14 SADISOPSG/ Report on Agenda Item 4.3 2) 90 per cent reported good availability of WAFS bulletins in the GRIB code; 3) 95 per cent reported good availability of WAFS bulletins in the BUFR code; 4) 85 per cent reported good availability of OPMET messages; and 5) 95 per cent considered it to be good ; and d) concerning the visualization of WAFS SIGWX forecasts: 1) 80 (70) per cent produced compliant WAFS charts from BUFR bulletins; and 2) 60 (60) per cent used WAFS forecasts in the PNG format; and e) concerning the service desk and administrative messages: 1) 75 (70) per cent did not use the 24-hour service desk; and 2) 5 (5) per cent considered that the administrative messages were not adequate It was agreed that the figures were comparable to, or better than, those received last year. The group was particularly pleased to single out two positive developments over the last year: a) increased capacity of producing compliant SIGWX charts from the BUFR-coded WAFS forecasts; and a) improved availability of OPMET messages via the SADIS 2G Based on the responses received, the group reiterated its satisfaction with the quality of SADIS service considered good by a clear majority of users and with the fact that the number of States with serious difficulties with their SADIS VSAT had remained small. Format of the questionnaire The group recalled that the questionnaire on SADIS efficacy had been developed by the Secretariat, in consultation with the Chairman of the SADISOPSG and the SADIS Provider State, and thoroughly revised at the SADISOPSG/14 Meeting (Decision 14/3 refers) to improve its clarity and to add a section related to the SADIS FTP service which was being increasingly used. The group agreed that, at this stage, there was no need to undertake any further revisions. However, in view of the full implementation of SADIS 2G (except for two States which intended to continue to use the SADIS FTP as their primary source of information), the group agreed that the question related to its implementation should be eliminated. The group formulated the following decision:

15 SADISOPSG/15 Report on Agenda Item Decision 15/3 SADIS efficacy questionnaire That, the questionnaire used in future consultations with States/users on the operational efficacy of the SADIS broadcast and SADIS FTP service be unchanged, except for the elimination of the question related to the implementation of the SADIS 2G VSAT. Annual statement The group, including IATA, agreed that, in the light of comments received, the SADIS broadcast and SADIS FTP service continued to meet the operational requirements during the period under review and to formulated the following conclusion: Conclusion 15/4 Annual statement of operational efficacy of SADIS 2009/2010 That, the Chairman of the SADISOPSG be invited to inform the Chairman of the SCRAG that, during the period 2009/2010, the SADIS continued to meet the operational requirements.

16 SADISOPSG/15 Report on Agenda Item Agenda Item 4: Operation of the SADIS 4.4: SADIS inventory The latest inventory which formed the basis for SADIS cost recovery purposes had been developed by the SADISOPSG/14 Meeting and used by SCRAG at its tenth meeting (SCRAG/10) held in Paris in November The inventory has since been updated by the SADIS Provider State in two respects: a) staff costs were expressed in terms of staff-days, instead of percentages of staff, in accordance with instructions given by the SCRAG; and b) the hardware refresh undertaken (in response to Conclusion 14/23) had been included The group reviewed the inventory including the draft amendments and formulated the following conclusion: Conclusion 15/5 SADIS Inventory That, the Chairman of the SADISOPSG be invited to forward the updated SADIS inventory given in Appendix C to this report to the Chairman of SCRAG.

17 SADISOPSG/15 Report on Agenda Item Agenda Item 4: Operation of the SADIS 4.5: SADIS implementation The group was pleased to note that the number of States and users had increased during 2009/2010 with 102 (95 in 2008/2009) Contracting States relying on a total of 121 (104 in 2008/2009) SADIS 2G VSAT receivers and 131 (46 in 2008/2009) FTP servers. A further 8 (12 in 2008/2009) Contracting States had received authorized access, some of which were in the process of installing SADIS VSAT receivers or FTP servers. The group highlighted the fact that, during the past year, the number of SADIS FTP users had almost tripled, similar to the previous year.

18 SADISOPSG/15 Report on Agenda Item Agenda Item 5: Content of the SADIS broadcast 5.1: OPMET information METAR, SPECI and TAF General considerations concerning the requirements and actual content of the SADIS broadcast The group recalled that the requirements by States and users for METAR, SPECI and TAF to be broadcast on the SADIS were given in Annex 1 to the SADIS User Guide (SUG) which was extracted from a global OPMET database maintained by the ICAO Secretariat. Annex 1 included OPMET information from both AOP (i.e. aerodromes included in the aerodrome operational planning (AOP) tables of the regional air navigation plans) and non-aop aerodromes In response to Conclusion 8/6, OPMET information from all the AOP aerodromes was included in Annex 1. All AOP aerodromes issued METAR and SPECI, as a minimum (with few exceptions in the EUR Region), while the requirements for TAF were subject to formal regional air navigation (RAN) agreement which was reflected in the Tables MET 1A of all the facilities and services implementation documents (FASID). The group recalled that, since February 2008, similar to Annex 1, all FASID Tables MET 1A were extracted from the global OPMET database thus ensuring the consistency of information between the FASID Tables MET 1A and Annex 1. This arrangement also implied that Annex 1 now reflected, at all times, the formal requirements displayed in FASID Tables MET 1A. Furthermore, the group had agreed that any proposals for amendments related to OPMET data from AOP aerodromes should be addressed directly to the ICAO Regional Office concerned (Decision 13/8 refers). This approach eliminated the need for a lengthy procedure (i.e. formulation by the SADISOPSG of draft conclusions for endorsement by the PIRGs concerned) and substantially expedited the implementation of new requirements With regard to non-aop aerodromes, the group was aware of the fact that OPMET information from these aerodromes could be included in Annex 1 only if the State concerned had no objection to its distribution on the SADIS and with the understanding that States did not have any obligation of providing such data for non-international aerodromes. OPMET requirements from these aerodromes may be amended by the group annually, subject to an agreement by the State concerned It was further recalled that the actual OPMET information that was currently broadcast on SADIS was indicated in Annex 2 (listing the aerodromes included in the bulletins) and Annex 3 (listing the bulletin headers). These annexes were updated bi-annually, with the assistance of the EUR Bulletin Management Group (BMG). Non-implementation of requirements for OPMET data by States The variability of reception of OPMET data from some aerodromes had been cause for adverse comments in the past. However, where such comments concerned aerodromes not listed as a requirement in Annex 1, the SADIS Provider State was unable to pursue missing data from these aerodromes. Non-availability of OPMET data from aerodromes listed in Annex 1 was a different matter and, when notified by users, had been systematically brought to the attention of the States concerned by the appropriate ICAO regional office which had kept on monitoring such deficiencies until their

19 SADISOPSG/ Report on Agenda Item 5.1 resolution. The group concurred that such a real-time approach had turned out to be efficient and had led, in most cases, to the timely resolution of the deficiencies identified. Draft amendments to Annex 1 to the SUG The group reviewed the OPMET data required from non-aop aerodromes based on a proposal made by the International Air Transport Association (IATA). It was noted that the proposal attempted to render the requirements in line with OPMET data that was actually made available by States. In this regard, the group concurred that any proposed deletions could be undertaken by the Secretariat without need for consulting the States concerned while any proposed additions would have to be endorsed by them. It was noted that only those aerodromes with location indicators included in the Location Indicators (Doc 7910) could be included in Annex 1 to the SUG. The group reviewed the proposal, endorsed the proposed changes with the understanding that there would be no substantial cost impacts due to the limited number of aerodromes that were expected to be included and formulated the following conclusion: Conclusion 15/6 Revision of Annex 1 concerning OPMET information from non-aop aerodromes That, ICAO a) seek agreement from the States concerned to provide OPMET information from non-aop aerodromes as depicted in Appendix D to this Report; b) amend Annex 1 to the SADIS User Guide accordingly by 31 December 2010; and c) report back to the SADISOPSG/16 Meeting the number of aerodromes actually added in Annex 1, as a result of the consultation with the States concerned. Note 1. - Only non-aop aerodromes for which location indicators are listed in Doc 7910, Location Indicators will be considered in this context; and Note 2. - States have the prerogative of not providing any OPMET data from non-aop aerodromes, if not considered appropriate or desirable by them. Harmonization of the OPMET content in SADIS and ISCS Since Annex 1 reflected the global requirements by users (e.g. airlines) and States for OPMET data, the group considered that they should be applicable for both the SADIS and ISCS broadcast. Their validity for the ISCS broadcast was confirmed by the fact that Annex 1 to the SUG had been included, without any changes, in the ISCS User Guide. The group was pleased to learn as part of the report by the SADISOPSG Gateway Development Team under Agenda Item 6.1 that the overall

20 SADISOPSG/15 Report on Agenda Item harmonization between the SADIS and ISCS broadcasts had been progressed near to completion. It may be noted that outstanding issues would be addressed under Agenda Item 6.1. Non-scheduled OPMET information In view of the importance of non-scheduled OPMET information for aviation (e.g. SIGMET, AIRMET, tropical cyclone and volcanic ash advisories), the group recalled that it had agreed that the reception of these messages should be monitored by the SADIS Provider State, which should compile annual statistics showing the number of all types of non-scheduled OPMET information received at the SADIS uplink station and present these results to the SADISOPSG as part of the annual management report (Conclusion 8/8 refers). The group was pleased to note that this information which may be considered to be highly relevant had been included in the management report The group noted that the fourth meeting of the International Airways Volcano Watch Operations Group (IAVWOPSG/4) had formulated Conclusion 4/28 b) requesting volcanic ash advisory centre (VAAC) London to transmit the Nuclear Emergency Message received from the International Atomic Energy Agency (IAEA) through the ICAO aeronautical fixed service (AFS). Since SADIS formed part of the AFS, the group agreed that the inclusion of the Nuclear Emergency Message therein would foster its availability to aviation users and formulated the following conclusion: Conclusion 15/7 Inclusion of Nuclear Emergency Message in SADIS That, the SADIS Provider State include the Nuclear Emergency Message received from the International Atomic Energy Agency (IAEA) in the SADIS broadcast and SADIS FTP Service, in time for the applicability of Amendment 75 to Annex 3. Note. - In view of harmonization between SADIS and ISCS, it may be expected that the Nuclear Emergency Message be also included, in due course, in ISCS.

21 SADISOPSG/15 Report on Agenda Item Agenda Item 5: Content of the SADIS broadcast 5.2: WAFS forecasts The group recalled that the list of the world area forecast system (WAFS) forecasts disseminated on SADIS was included in Annex 4 to the SUG which had been updated last time in 2008 to include the new GRIB 2-coded WAFS forecasts. This update had been subsequently endorsed by the SADISOPSG/14 Meeting. The group noted that since that meeting, no amendments to the list of WAFS forecasts broadcast on SADIS contained in Annex 4 had been made, and therefore concurred that there was no need to formulate any decisions in this regard.

22 SADISOPSG/15 Report on Agenda Item Agenda Item 6: Development of the SADIS 6.1: Report of the SADISOPSG Gateway Development Team The group recalled that the SADIS gateway function had been developed in response to the European Air Navigation Planning Group (EANPG) Conclusion 38/33 and that, at subsequent meetings, it had developed a set of high-level technical requirements, including the real-time monitoring. It had also finalized the SADIS Gateway Operations Handbook which was available on the SADISOPSG website, in accordance with Conclusion 8/15. The system had been fully operational since The group took note of the report by the Rapporteur of the SADISOPSG Gateway Development Team related to the progress made since the SADISOPSG/14 Meeting. In this report, the group s attention was drawn to three specific issues: a) SIGMET validation; b) harmonization of the OPMET content between the SADIS broadcast, SADIS FTP service and ISCS broadcast; and c) removal of the TAF auto-correction function. Validation of SIGMET at the SADIS gateway Concerning the validation of SIGMET, the group recalled that SADISOPSG Conclusion 13/12 had urged States to comply with the provisions of Annex 3 Meteorological Service for International Air Navigation provisions as far as the format of SIGMET bulletins was concerned. The implementation of the correct format had been considered essential by the group since the low level of implementation had rendered the real-time monitoring of SIGMET at the SADIS gateway impracticable. The results in 2009 had been encouraging since compliance had increased significantly to a value of 64.4 per cent from 38.8 per cent the previous year and there was considerable optimism that the 80 per cent threshold considered necessary for the implementation of SIGMET validation would be achieved in The group was disappointed to learn that the results of the 14-day analysis undertaken in early 2010 had shown no improvement on the compliance in 2009; it had remained insufficient to trigger the automatic validation at the SADIS gateway. The results further indicated that particular problems with compliance persisted in Canada, India and the United States. To address this safety issue, the group agreed that the foregoing States should be reminded of the importance of the correct format of SIGMET and formulated the following conclusion: Conclusion 15/8 Implementation of the correct format of SIGMET That, in order to ensure the safety of aircraft operations, the Secretariat urge Canada, India and the United States to implement, as a matter of urgency, the correct format of SIGMET as contained in Annex 3.

23 SADISOPSG/ Report on Agenda Item 6.1 Harmonization of the OPMET content between SADIS and ISCS With regard to the harmonization of the operational meteorological (OPMET content between the SADIS and international satellite communications system (ISCS), the group recalled that substantial progress had been made last year. It was pleased to note that further steps were expected with the introduction of revised bulletins by the ISCS Provider State, which would render the set of bulletins consistent on both systems In spite of the progress made, the group considered that, based on the monitoring of the SADIS broadcast over a period of 9 weeks by IATA, the harmonization efforts should continue to further align the content of the ISCS and SADIS broadcasts. In view of the foregoing, the group formulated the following conclusion: Conclusion 15/9 Harmonization of the OPMET content of the SADIS and ISCS broadcasts That, the SADIS Provider State, in coordination with the ISCS Provider State, continue its efforts to harmonize the required OPMET content of the SADIS and ISCS broadcasts. Note 1. - The aim is to reach a 95 per cent availability of OPMET data on SADIS and ISCS broadcasts as soon as possible, but not later than the SADISOPG/16 meeting; Note 2. Required OPMET content is listed in Annex 1 to the SUG; and Note 3. Bi-annual monitoring comparing the contents of the two broadcasts will be undertaken by the EUR BMG. Removal of the TAF auto-correction function Concerning the TAF auto-correction, the group recalled that it had been removed prior to the SADISOPSG/14 Meeting due to its incompatibility with the new TAF code form introduced by Amendment 74. The group was pleased to note that the corresponding updates to the SADIS Gateway Handbook as called for by Conclusion 14/14 had been published in November 2009 as part of the fourth edition of the document.

24 SADISOPSG/15 Report on Agenda Item Agenda Item 6: Development of the SADIS 6.2: Report of the SADISOPSG Strategic Assessment Team Based on a report provided by the SADISOPSG Strategic Assessment Team, the group reviewed the format and content of the strategic assessment tables. It was noted that the current figures for 2010 had been obtained from an analysis of the OPMET data promulgated to SADIS via the SADIS Gateway and that the draft figures for had been prepared by the SADIS Provider State using the current figures as a base line. This would ensure that projected figures were consistent with the current OPMET data distributed on the SADIS. On completion of the review of the tables, the group requested the Secretariat to forward the tables to the MET sub-groups (SGs) of the planning and implementation regional groups (PIRGs) concerned in 2010, in view of forming the basis for the next regional update of future SADIS requirements, including the figures for the year In this regard, the group formulated the following conclusion: Conclusion 15/10 SADIS Strategic Assessment Tables That, a) the SADIS Provider State take note of the completed SADIS Strategic Assessment Tables, provided in Appendix E to this report, to form the basis for the future development of the SADIS; and b) the Secretariat forward the SADIS Strategic Assessment Tables to the subgroups of the PIRGs concerned for update in respect of future requirements. Note 1. - Any major changes to the SADIS will be subject to draft conclusions, to be formulated by the SADISOPSG, to be endorsed by the relevant PIRGs, and to be noted, as necessary, by the Commission or Council; and Note 2. - Completed SADIS Strategic Assessment Tables are provided by ICAO Regional Offices to the SADISOPSG following consideration at appropriate sub-group meetings of the PIRGs concerned With regard to the format of the strategic assessment tables, the group agreed that the current format fully reflected the data originated outside the world area forecast centres (WAFCs) and promulgated on the SADIS; therefore it was agreed that there was no need to amend the current format The group considered whether separate tables related to data volumes of WAFS forecasts disseminated on the SADIS should be included. It was noted that the strategic assessment tables had been initially introduced to allow the MET SGs of the PIRGs to express the expected future regional requirements for OPMET-message dissemination on the SADIS. The group agreed that the estimated data volumes for WAFS forecasts in the GRIB1, GRIB2, PNG and BUFR code forms were global in nature and that no input from the MET SGs could be expected in this regard. Therefore, it was concurred that there was no need to refer the new tables for formal consideration by the MET SGs; they should simply be provided for information and be dealt with separately from the regional strategic assessment tables. The group formulated the following conclusion:

25 SADISOPSG/ Report on Agenda Item 6.2 Conclusion 15/11 SADIS Strategic Assessment Tables inclusion of expected GRIB1, GRIB2, PNG and BUFR data volumes That, the SADIS Strategic Assessment Team, in consultation with the SADIS Provider State, provide estimates of future data volumes related to WAFS forecasts in the GRIB1, GRIB2, PNG and BUFR code forms, as an attachment to the SADIS Strategic Assessment Tables. Note. - These data volumes are provided to the MET SGs for information purposes only.

26 SADISOPSG/15 Report on Agenda Item Agenda Item 6: Development of the SADIS 6.3: Report of the SADISOPSG Technical Developments Team The group recalled that the SADISOPSG Technical Developments Team was expected to monitor, report on and propose action on technological developments having an impact on SADIS. Over the last 12 months, the major technical developments addressed by this team were related to: a) future utilization of the SADIS satellite bandwidth (Conclusion 14/25 refers); b) transmission of GRIB2 data on the SADIS 2G (Conclusion 14/16 refers); and a) SADIS 2G uplink protocols (Conclusion 14/24 refers). Future utilization of the SADIS satellite bandwidth The group recalled that the SADISOPSG/14 Meeting had formulated Conclusion 14/25 which had called for the SADIS Provider State, in coordination with the SADISOPSG Technical Developments Team, to review SADIS satellite bandwidth allocation taking into account the expected changes in the WAFS forecasts (e.g. dissemination of GRIB2-coded WAFS forecasts) and report back the findings thereof to the SADISOPSG/15 Meeting. It was understood that the need for any end-user hardware changes was to be considered in this context The group recalled that the Second Generation Satellite Distribution System (SADIS 2G) made use of dedicated satellite uplink/downlink capacity. Furthermore, the now retired First Generation SADIS (SADIS 1G), whilst no longer requiring uplink/downlink capacities had, nonetheless, had its operational capacity retained with the view that it may be necessary to make this now spare capacity available to SADIS 2G in light of expected developments with regard to the provision of WAFS GRIB2 forecasts over the SADIS 2G system The group noted the detailed review related to the SADIS satellite bandwidth allocation taking into account the expected changes in the WAFS forecasts prepared by the SADIS Technical Developments Team, in coordination with the SADIS Provider State. The group endorsed the following conclusions drawn from this review: a) with careful management, GRIB1 and GRIB2 data volumes could be managed such that the current SADIS 2G bandwidth allowances were sufficient and did not need to be increased; b) during the periods of GRIB1 and GRIB2 transmissions where sustained rates of transfer of the order 60 kbps were made for some tens of minutes, it had been confirmed that there were no adverse delays to OPMET data; and c) regarding the future XML schemas to be used for all OPMET exchanges, it was considered that it was not possible to make informed decisions in this regard due to the lack of detailed information.

27 SADISOPSG/ Report on Agenda Item Based on the foregoing, the group agreed that the existing SADIS 2G data transfer rate of 64 kbps was sufficient for the foreseen needs of the service, including the introduction of GRIB2 transmissions, subject to the introduction of GRIB2 data being suitably managed and prioritized against GRIB1 data. Accordingly, the group formulated the following conclusion: Conclusion 15/12 SADIS 2G future bandwidth requirements That, the SADIS Provider State Transmission of GRIB2 data over satellite a) relinquish the currently retained SADIS 1G satellite bandwidth at the end of the current contract (31 December 2010) to save some per annum from the SADIS cost base; b) inform the Chairman of the SCRAG on the cessation of that part of the contract; and c) prepare, in time for the SADISOPSG/16 Meeting, an implementation plan, in coordination with the SADIS Technical Developments Team, concerning the GRIB2 and GRIB1 data sets over the SADIS 2G broadcast such that the two datasets are not transmitted at the same time. Note 1. - The existing SADIS 2G satellite bandwidth and transfer speed of 64kbps will be retained until such time as directed otherwise by the SADISOPSG; Note 2. - The implementation plan will include a prioritization of the GRIB1 versus GRIB2 datasets; and Note 3. - The SADIS Provider State, assisted by the Secretariat and the SADIS Technical Developments Team, will closely monitor the progress of the implementation of OPMET data in table-driven codes (e.g. XML) and report back to the group in due course The group recalled that the SADISOPSG/14 Meeting had formulated Conclusion 14/16 calling for the SADIS Provider State, in coordination with the SADISOPSG Technical Developments Team, to complete the trial of compressed GRIB2 coded data by 30 September 2009 and present proposals, for endorsement by the SADISOPSG/15 Meeting, for further steps in view of introducing the transmission of GRIB2 coded data on the SADIS 2G broadcast as an operational procedure. It had been noted that the inclusion of GRIB2 forecasts for CB clouds, icing and turbulence would be subject to endorsement by the World Area Forecast System Operations Group (WAFSOPSG) and that the decoding and decompression software would be made available at no cost to SADIS users. Furthermore, the group had understood that the inclusion of the GRIB2 data in the SADIS 2G broadcast was to be performed in coordination with the ISCS Provider State.

28 SADISOPSG/15 Report on Agenda Item Following on from trials of transmission of uncompressed GRIB2 over the SADIS 2G where it had been determined that a data volume of around 50 MB took approximately 1hr 55min to transmit (compared to around 10 MB and approximately 30 min for GRIB1 over the SADIS), completion of trials to determine the data volumes and time of transmission for compressed versions of the GRIB2 data were undertaken The group noted that the results of the tests undertaken in September 2009 and February 2010 involving compressed bulletins indicated that the transmission over the SADIS 2G of the: a) complete dataset (i.e bulletins including forecasts of cumulonimbus (CB) clouds, icing and turbulence) compressed to about 22 MB, took approximately 45 to 50 minutes; and b) reduced dataset (i.e. 671 bulletins excluding forecasts of CB clouds, icing and turbulence) compressed to about 16 MB took approximately 35 minutes It was noted that the results of these tests had indicated that the datasets were successfully received and decompressed. Furthermore, the comparison of NATS TAF/METAR bulletin transmission logs against the reception logs provided by KNMI and MeteoSwiss in February 2010 had shown that the delays were between 1 to 5 seconds, demonstrating that there was no significant, negative impact on TAF/METAR reception Whilst these tests demonstrated that GRIB2 WAFS data could be successfully transmitted, decompressed and visualized when broadcast via the SADIS 2G, the group concurred that there were additional considerations that needed to be taken into account, i.e. avoiding conflicts with the transmission of OPMET messages and WAFS forecasts in the GRIB1 code form, and considering the operational acceptability of forecasts for CB clouds, icing and turbulence to the aviation users. In this regard, the group concurred that the transmission of the WAFS forecasts in the GRIB2 code form over the SADIS 2G be: a) 1 hour later than that of the WAFS forecasts in the GRIB1 code form to avoid any negative impact on the timeliness of the OPMET messages and WAFS forecasts in the GRIB1 code form; and b) initially limited to be the dataset excluding the new forecasts of CB clouds, icing and turbulence, with the understanding that the new forecasts be included as soon as they were considered operational by the WAFSOPSG. It was noted that these arrangements would also be applicable under back-up. Based on the foregoing, the group formulated the following conclusions:

29 SADISOPSG/ Report on Agenda Item 6.4 Conclusion 15/13 Further tests over SADIS 2G of GRIB2 data to enable workstation vendors to develop and test their systems That, to enable workstation vendors to develop and test their systems, the SADIS Provider State, with assistance of the SADIS Technical Developments Team, carry out further test/development transmissions of GRIB2 WAFS data before the operational implementation of the broadcast. Note 1. - Transmission times should be such that they do not conflict with GRIB1 transmissions; and Note 2. - SADIS users will be provided with a schedule containing the exact dates and times of transmission through SADIS administrative messages; and Note 3. Test transmissions will be via the fourth SADIS 2G channel, available to vendors only. Conclusion 15/14 Operational transmission of GRIB2 WAFS forecasts over the SADIS 2G broadcast That, the SADIS Provider State, in coordination with the ISCS Provider State, implement the transmission of GRIB2 WAFS forecasts with effect from 1200 UTC data (transmitted 1600 to 1655 UTC) on 18 November 2010, subject to the following conditions: a) transmission of GRIB2 WAFS forecasts will be 1 hour after the transmission of GRIB1 WAFS forecasts; and b) forecasts for CB clouds, icing and turbulence in the GRIB 2 code form that are currently considered trial forecasts will not be transmitted until endorsed by the WAFSOPSG. Note 1. - Transmission times for GRIB2 WAFS forecasts will initially be UTC for DT 0000; UTC for DT 0600; UTC for DT 1200; and UTC for DT 1800, and the SADIS users will be informed accordingly through administrative messages; Note 2. The users of GRIB1 data will not be affected by the introduction of the GRIB2 WAFS forecasts; and Note 3. User States are advised to contact their vendors for possible system upgrades.

30 SADISOPSG/15 Report on Agenda Item SADIS 2G Uplink protocols The group recalled that the SADIOPSG/14 Meeting had tasked the SADIS Provider State to determine what transfer protocol (i.e. X25 protocol versus Internet Protocol (IP)) between Exeter and Whitehill was the most efficient to use, and whether or not it was justifiable to increase the bandwidth of the two fixed links between Exeter and Whitehill to 128 kbps each from their current 64 kbps each (Conclusion 14/24 refers) The group recalled that the current arrangement was that data was transmitted from the Met Office FROST Message Switch to the VadEDGE 4200 Routers using IP. The VadEDGE routers at Exeter converted the data to X25 before onward transmission to the MegaPAC-V-IX. The MegaPAC-V-IX converted the data a third time to the VSAT protocol. The group noted that the SADIS Technical Developments Team had assessed the possibility of using the IP instead of the X25 Protocol in the Exeter to Whitehill link, thus saving one conversion and also complying with a general desire to move away from X25 within the SADIS Provider State s infrastructure The group noted that the SADIS Technical Developments Team had considered, in coordination with the SADIS Provider States, the advantages and disadvantages of X25 against IP and the justification to increase bandwidth to 128 kbps. The group endorsed the findings of the detailed analysis which indicated that: a) it would be disadvantageous to replace the existing X25 Protocol with the IP between Exeter and Whitehill due to the lack of error correction and increased communication overheads related to the use of IP. It was considered that a change of protocol from X25 to IP would only be viable with a complete redesign of the system; and b) with regard to the transmission rate of the links between Exeter and Whitehill, the foreseen needs of the SADIS 2G could be met with the current infrastructure (i.e. 64 kbps transmission rates), and there was no need to increase the transmission rate (bandwidth) of the satellite broadcast, nor the capacity of the physical lines In order to formally endorse the above findings, the group formulated the following decisions: Decision 15/15 Retention of the X25 Protocol for the Exeter to Whitehill segment of the SADIS 2G That, the SADIS Provider State continue to use the X25 Protocol for the Exeter to Whitehill segment of the SADIS 2G satellite broadcast. Decision 15/16 Retention of existing capacity of fixed lines between Exeter and Whitehill That, the SADIS Provider State retain the existing capacity of 64 kbps for each of the fixed lines between Exeter and Whitehill.

31 SADISOPSG/ Report on Agenda Item 6.4 Agenda Item 6: Development of the SADIS 6.4: SADIS Internet-based FTP Service The group recalled that the SADIS FTP service had been in operation for a number of years and had consistently seen the number of users accessing the service grow year-upon-year, as well as seen a growth in the number of products being accessed by those users. Furthermore, it was expected that during the next few years it was likely that the downloading of WAFS forecasts in the GRIB2 code form would introduce a sharp rise in downloaded products. Implementation of SADIS FTP The group recalled that it had formulated Conclusion 14/19 calling for the SADIS Provider State to increase the SADIS FTP Internet bandwidth allocation to 4 Mbps bursting to 8 Mbps between server and Internet service provider (with individual client connections guaranteed at 64 kbps, bursting to 512 kbps), in time for the SADISOPSG/15 Meeting. It was noted that the bandwidth allocation had been increased accordingly on 31 January Development of Secure SADIS FTP service It was recalled that the group had formulated Conclusion 14/18 calling for the SADIS Provider State, in coordination with the SADIS Technical Developments Team, to proceed with the development of a SADIS FTP Secure service ( Phase 2 ) and provide a progress report on the status of the implementation of Phase 2 to the SADISOPSG/15 Meeting. It had been further noted that the Phase 2 was expected to be operational by November 2010 and would run in parallel with the existing SADIS FTP Enhanced service ( Phase 1 ) for at least 12 months to afford users sufficient time to migrate to the new service The group agreed that, to avoid any misunderstanding, the new service should be called Secure SADIS FTP service, instead of SADIS FTP Secure service. In this regard, the group formulated the following decision: Decision 15/17 Naming of the secure version of SADIS FTP (SADIS FTP Enhancement Phase 2 to Secure SADIS FTP That, in order to prevent any possible confusion relating to the methodology used to implement security features in the new SADIS FTP service, it be known as Secure SADIS FTP. Note. The phrases Secure FTP and FTP Secure have specific and incompatible meanings with regard to particular security protocols. In order to remove as far as possible the risk of confusion, the word secure and the abbreviation FTP should be separated, - hence Secure SADIS FTP.

32 SADISOPSG/15 Report on Agenda Item The group noted the progress report prepared by the SADIS Provider State. It was noted that the key requirements of a secure SADIS FTP Service were to mitigate against the following risks, i.e. the reception of: a) corrupt data from an invalid source, instead of original data from a legitimate source; b) forged or fake data from an apparently legitimate source, but in reality a fake source; or c) original data from a legitimate source, but data which is incomplete or inaccurate With regard to the details of a secure SADIS FTP Service, the group considered the following five future options together with the corresponding estimates of costs: Digital Signing, HTTPS, SFTP, FTPS and status quo. The group noted the results of the assessment (estimated costs in brackets) which indicated that: a) Digital Signing. This option was the one initially proposed at the SADISOPSG/14 Meeting; it would meet to the highest level the security requirements in terms of data integrity and authenticity. It was the only option that could fully provide proof of integrity of data (either through malicious or accidental modification of data), and ultimately full non-repudiation protection. (Costs: ± 13000, as notified to Chairman of the SCRAG at the SCRAG/10 Meeting); b) HTTPS (Hyper Text Transfer Protocol Secure). It was noted that the HTTPS protocol was used for secure online transactions and provided confidentiality in the sense that the user could be assured that they had connected to the SADIS Provider State s servers. However, it did not provide absolute proof that a document transmitted from the provider had been received intact by the user. Since alerting SADIS users for potential corruption or tampering was considered critical, the HTTPS was not considered appropriate for SADIS. (Costs: ± 4000); c) SFTP (Secure Shell (SSH) File Transfer Protocol). The group noted that the SFTP encrypted both commands and data, providing effective protection against common network security risks and preventing the casual detection of the username, password or any other transmitted data. However, it did not provide the absolute proof of integrity or authenticity of the data, and was not therefore considered appropriate for SADIS. (Costs: ± 4000); d) FTPS (FTP with Transport Security Layer (TSL) and Secure Socket Layer (SSL). It was noted that that with FTPS, the control session would always be encrypted, while the data session might not be. This option was ruled out on the basis that it did not provide absolute proof of integrity or authenticity of the data, considered essential by the group. (Costs: ± 4000); and e) Status quo. The status quo scenario would not provide confidentiality or the proof of data integrity, and was not therefore considered to meet the minimum requirements for SADIS as stipulated in Doc (Costs: no additional expenditure).