ࡱ>  tbjbjvv -tm8rr N""""$###Pn#D%L#λ&DB):|)L-L-/b6N8!######,pO9"F9/"/F9F9OB?""L-L-BB?B?B?F9t"L-"L-!B?F9!B?B?( r5k>%p 0λ4B?4B?4"PF9F9F9OOB?F9F9F9λ4F9F9F9F9F9F9F9F9F9r :   Limited Distribution IOC/IODE-XXIV/6.1  Oostende, 28 December 2016 Original: English INTERGOVERNMENTAL OCEANOGRAPHIC COMMISSION (of UNESCO) Twenty-fourth Session of the IOC Committee on International Oceanographic Data and Information Exchange (IODE-XXIV) Kuala Lumpur, Malaysia, 28-31 March 2017 Report of the Inter-sessional working Group to Propose a Re-structuring of IODE (Decision IODE-XXIII.1) Writing team: Hernan E. Garcia (USA), Yutaka Michida (Japan), Robert Keely (Canada), Greg Reed (IODE Project Office), Linda Pikula (USA), Peter Pissierssens (IODE Project office) With contributions from Carolina Calvete, Fatma Uki, Hawa Bint, Kakha Bilashvili, Laure Devine, Lesley Rickards, Murat Elge, Myrian Renee Tamayo Infantes, Pauline Simpson, Regina Folorunsho, Saida Messaoudi, Serge Scory, Sissy Iona, Tetsuichiro Yabuki, Ward Appeltans, Yu Ting, Abdul Haleem Al Muhyi, Arthur, Paterson, Carlos Roddolfo Torres Navarrete, Fatma Uki, Jarisoa Tsarahevitra, Kakha Bilashvili, Maged M.A. Hussein, N'guessan Kouadio, Regina Folorunsho, Saida Messaoudi, Tetsuichiro Yabuki Executive Summary The International Oceanographic Data and Information Exchange (IODE) programme has been exploring options for improving its data and information services to the ocean community. It is mission critical that IODE builds on its international role, engagement strategy, and leadership particularly in those areas where IODE has strong capacity to lead and to support effectively including capacity building and facilitating timely and open access to the best available scientific oceanographic data and information and minimizing competing with other international organizations and that IODE is operating within its budget. This document provides proposals accompanied by success metrics, implementation plan, and risk-benefit considerations responsive to the evolving needs of the IODE ocean data and information community. We recommend (a) instituting a peer-reviewed and merit-based funding cycle process for IODE projects and activities and (b) establishing a new IODE Management Group representing the broad IODE data and information objectives to recommend, to execute, and to track approved IODE committee work plans. We focus on relevant and doable strategies that lend themselves to achieving incremental and tangible progress over the next intersessional periods. We also recommend that IOC/IODE provides recognition to the IODE individuals that provide their time voluntarily to help manage IODE work plans with the consent of their host institutions. The path-forward recommendations discussed herein are offered for consideration to the IODE XXIV Committee for approval. We also provide strategic plan suggestions for the attention of the IODE Inter-sessional working group to revise the IOC Strategic Plan for Oceanographic Data and Information Exchange (Decision IODE-XXIII.2). Table of Contents  TOC \o "1-3" 1. INTRODUCTION  PAGEREF _Toc345671113 \h 1 2. REVIEW THE RECOMMENDATIONS LISTED IN DOCUMENT IOC/IODE-XXIII/5B (THE FUTURE OF IODE RECOMMENDATIONS)  PAGEREF _Toc345671114 \h 2 3. REVIEW THE TERMS OF REFERENCE FOR THE IODE STRUCTURE, PROJECTS, AND ACTIVITIES TO ENSURE CONTINUED RELEVANCE TO IODE AND IOC GOALS  PAGEREF _Toc345671115 \h 3 3.1 Structural elements of IODE  PAGEREF _Toc345671116 \h 3 3.2 Current governance structure of IODE  PAGEREF _Toc345671117 \h 5 3.2.1 The IODE Committee  PAGEREF _Toc345671118 \h 6 3.2.2 The IODE Groups of Experts  PAGEREF _Toc345671119 \h 7 3.2.3 IODE Steering Groups  PAGEREF _Toc345671120 \h 8 3.2.4 IODE Inter-sessional working groups  PAGEREF _Toc345671121 \h 8 3.2.5 IODE Task Teams  PAGEREF _Toc345671122 \h 8 3.2.6 IODE national coordinators for data management  PAGEREF _Toc345671123 \h 8 3.2.7 IODE national coordinators for marine information management  PAGEREF _Toc345671124 \h 9 3.2.8 ADU focal points  PAGEREF _Toc345671125 \h 9 4. IDENTIFY AND EVALUATE THE BENEFITS IODE DERIVES FROM THE CURRENT STRUCTURE, PROJECTS AND ACTIVITIES  PAGEREF _Toc345671126 \h 9 4.1 Benefits that IODE derives from the current structure  PAGEREF _Toc345671127 \h 9 5. EVALUATE ANY WEAKNESSES OF THE CURRENT IODE STRUCTURE, PROJECTS AND ACTIVITIES AND FORMULATE WAYS TO REMEDY THESE WEAKNESSES  PAGEREF _Toc345671128 \h 10 6. PROPOSE OPTIONS FOR REVISING THE CURRENT STRUCTURE, PROJECTS AND ACTIVITIES  PAGEREF _Toc345671129 \h 11 6.1 The IODE Committee  PAGEREF _Toc345671130 \h 11 6.2 IODE management structure  PAGEREF _Toc345671131 \h 13 6.2.1 Background and problem statement  PAGEREF _Toc345671132 \h 13 6.2.2 Recommendations on IODE Management Structure  PAGEREF _Toc345671133 \h 13 6.3 IODE projects: Develop a process-oriented and peer-reviewed funding cycle for IODE projects and activities  PAGEREF _Toc345671134 \h 16 6.3.1 Background and problem statement  PAGEREF _Toc345671135 \h 16 6.3.2 Recommendations  PAGEREF _Toc345671136 \h 17 6.3.3 Process for proposing projects and activities  PAGEREF _Toc345671137 \h 17 6.3.4 Process for evaluating on-going and ending IODE projects or activities  PAGEREF _Toc345671138 \h 21 7. ADDITIONAL RECOMMENDATIONS FOR THE ATTENTION OF THE IODE INTER-SESSIONAL WORKING GROUP TO REVISE THE IOC STRATETGIC PLAN FOR OCEANOGRAPHIC DATA AND INFORMATION EXCHANGE (DECISION IODE-XXIII.2)  PAGEREF _Toc345671139 \h 23 7.1 Evolving IODE  PAGEREF _Toc345671140 \h 23 7.2 Associated Information Units (AIU)  PAGEREF _Toc345671141 \h 29 7.3 Role of IODE in facilitating the development of JCOMM Global Data Assembly Centres (GDACS)  PAGEREF _Toc345671142 \h 30  INTRODUCTION The International Oceanographic Data and Information Exchange (IODE) programme of the Intergovernmental Oceanographic Commission (IOC) of the United Nations Educational, Scientific and Cultural Organization (UNESCO) was established in 1961. Its mission is to enhance marine research, exploitation and development, by facilitating the exchange of oceanographic data and information between participating Member States, and by meeting the needs of users for data and information products. Since its inception, IODE has played an important role by helping facilitate the open exchange of oceanographic data and information between participating Member States with the goal of meeting the needs of users for data and information products. During this time, Member States, through national data and information managers, have committed time and effort to helping coordinate oceanographic data and information management at national, regional, and global scales. The IODE network of data and information centres provides or endorses several value-added products and services, including the internationally recognized World Ocean Database (WOD) and Global Oceanographic Data Archaeology and Rescue (GODAR). WOD and GODAR have stimulated much international exchange of historical and modern oceanographic data, and led the development of quality control procedures and integration of research-quality data at local, regional, and global scales. Other IODE global database projects are GOSUD (Underway Sea Surface Salinity Data Archiving Pilot Project), GTSPP (Global Temperature and Salinity Profile Program) and OBIS (Ocean Biogeographic Information System). With substantial support from the Government of Flanders (Belgium) and the City of Ostend, the IOC Project Office for IODE was established in 2005 in Oostende, Belgium to help support the IODE programme. The 23rd Session of the IODE Committee established an Inter-sessional Working Group (IWG) (Decision IODE-XXIII.1) to examine options for enhancing and possibly restructuring IODE to achieve an efficient and optimal use of human and financial resources and better communications of IODE activities to our partners and stakeholders, with the following objectives: This working group will explore options of the IODE structure for the next 10 years. It will: Review the recommendations listed in Document IOC/IODE-XXIII/5b (The Future of IODE Recommendations); Review the terms of reference for the IODE structure, projects, and activities to ensure continued relevance to IODE and IOC goals; Identify and evaluate the benefits IODE derives from the current structure, projects and activities; Evaluate any weaknesses of the current IODE structure, projects and activities and formulate ways to remedy these weaknesses; Propose options for revising the current structure, projects and activities. The timeline was to complete a draft by December 2016 in preparation for the IODE-XXIV Committee meeting in March 2017. REVIEW THE RECOMMENDATIONS LISTED IN DOCUMENT IOC/IODE-XXIII/5B (THE FUTURE OF IODE RECOMMENDATIONS) Discussions on the Future of IODE have been held during IODE-XXII an IODE-XXIII. During IODE-XXII (2013) Mr Ariel Troisi, then IODE Co-Chair, drew the attention of the Committee to the current crisis situation in which IOC and all its programmes found themselves, including IODE. He also noted that the world had changed drastically since IODE was established in 1961. Old structures and methods may no longer serve todays user needs and IODE needs to adapt and to evolve. IODE-XXII had noted the need for projects to include performance indicators to monitor progress and to adjust operations as necessary. It had not been possible to define such metrics at the time. IODE-XXII had also highlighted the need to prioritize on activities in which it had specific strengths (e.g., in coordination, standards and best practices, data archival and capacity building). The Session had also called for a more active outreach programme to increase the visibility of IODE. It was noted that some of the IODE key products such as the World Ocean Database (WOD) had been neglected in terms of promotion in recent years. WOD is being used throughout the research community and should be highlighted as a core product/outcome of IODE. OBIS, although new to IODE, should also be actively marketed. It was suggested that a compilation of tangible benefits of participation in IODE as noted by NODCs should be assembled. IODE-XXIII (2015) continued discussions on the Future of IODE. Extensive discussions during the Session had resulted in a number of Recommendations to improve the efficiency of IODE (see Table 1). No.Text1Change the nature of the IODE survey of NODCs, DNAs, ADUs to have a common section on the resourcing of the IM and DM operations and inquire about activities that use IODE activities to enhance national operations, and activities that contribute to IODE objectives.2IODE Officers must ensure the IODE session agenda focuses on what discussions, actions, and decisions are needed from the full committee.3In preparation for the committee meeting, IODE Officers should compile the topics of broader issues that need IODE attention, ensure proper documentation is distributed before the meeting, and ensure sufficient time on the agenda for the appropriate treatment of these topics.4IODE sessions should be used by projects (SG members) to recruit IODE members to assist them in implementing their goals. IODE Officers and Project chairs should encourage broader participation in projects.5IODE meetings should make greater use of video conferencing using protocols developed by the Project Office that provide the opportunity for equal participation by individuals both in person and in remote locations.6aThe Officers should solicit a volunteer to poll member web pages to verify IODE presence and recommend changes as appropriate.6bOfficers to identify members willing to be on call to develop posters for events of importance to IODE and recruit IODE members to man such posters as appropriate.6cIODE members need to pursue IM and DM involvement in national or international projects as they are forming. They must demonstrate value by their inclusion.6dOfficers to identify the means to sponsor IM and DM conferences, such as IMDIS, as a forum for IODE members to demonstrate their IM and DM expertise.Table 1: Recommendations formulated by IODE-XXIII to improve the efficiency of IODE IODE-XXIII also noted that the IODE Committee needed to consider whether the large number of projects (approximately 30) could continue to be coordinated by IODE national experts and the IODE Secretariat. In this regard the Committee could consider closing down some of its activities (based on measurable performance indicators) or to the grouping of projects. This should lead to more effective and efficient use of human and financial resources. While some re-grouping of projects was discussed at IODE-XXIII (see Document IOC/IODE-XIII/3 paras 213-216) no decision was taken by the Committee. Instead the Committee decided to establish the inter-sessional working group to propose restructuring of IODE and adopted Decision IODE-XXIII.1 of which the objectives were listed above. Regarding the recommendations in Table 1 it is noted that none relate directly to the current structure of IODE though many had some merit in improving the performance of IODE. Several of the recommendations were implemented already. The working group decided to bear these streamlining recommendations in mind when considering the tasks of the working group. Instead, our group placed emphasis on developing substantive recommendations on the IODE structure accompanied by success metrics, implementation plan, and risk-benefit considerations building on current IODE strengths. REVIEW THE TERMS OF REFERENCE FOR THE IODE STRUCTURE, PROJECTS, AND ACTIVITIES TO ENSURE CONTINUED RELEVANCE TO IODE AND IOC GOALS Structural elements of IODE In accordance with Recommendation IODE-XXII.17 (Structural Elements of IODE), adopted by the 27th Session of the IOC Assembly (2013), IODE has the following structural elements: National Oceanographic Data Centre (NODC) IODE Associate Data Unit (ADU) IODE Global Data Assembly Centre (IODE GDAC) During the same IODE Session the terms of reference of the ADU (Recommendation IODE-XXII.16) and GDAC (Recommendation IODE-XXII.13) were defined: IODE Associate Data Units (ADUs) shall: Be national projects, programmes, institutions or organizations (other than NODCs), or regional or international projects, programmes, institutions or organizations that carry out data management functions, Receive information on, and contribute to, IODE standards and best practices related to ocean data management, Be welcomed to participate in ocean data and information management training, organized within the framework of the IODE OceanTeacher programme, Be invited, as observers, in Sessions of the IODE Committee, Participate in IODE workshops and projects, Share expertise with other ADUs and NODCs, Be invited to share their data and information on their data collection (metadata catalogue), and this should be through their NODC (in the case of national projects, programmes, institutions or organizations), or through another IODE data facility (in the case of regional or international projects, programmes, institutions or organizations) or, in the case of biogeographic data, through iOBIS, Receive assistance, upon request, from IODE, on matters related to ocean data management, Closely link with their IODE National Oceanographic Data Centre (NODC), if existing (in the case of national projects, organizations and institutions), Agree to make available data management documentation (standards, practices, guides) used by the ADU, ADUs will not replace NODCs (centralized or distributed) but should contribute to the objectives of NODCs by (i) improving the completeness of data coverage of NODCs; (ii) ensuring the long-term archival and preservation of ADU data by NODCs; and (iii) increasing awareness amongst the ocean research and observation community of the importance of professional data management through IODE NODCs. IODE GDACs will be included as structural elements of IODE with the following Terms of Reference with respect to particular data types: receive and assemble marine meteorological and/or oceanographic data (real or delayed-mode) and metadata from the appropriate data streams and check that these are consistent; identify duplicates and if possible resolve by keeping the best copy of a dataset; make sure that the data are quality controlled according to the international standards and methods established by IODE, WMO or JCOMM as appropriate; provide feedback to the sources of data regarding quality issues; make data accessible through IODE/ODP; make discovery metadata available to IODE/ODP; forward data and metadata to the appropriate CMOC(s) in agreed format(s) within defined timescales; contribute to WMO and IOC Applications by collecting and processing worldwide marine-meteorological and oceanographic data and metadata documented in appropriate WMO and IOC publications; report to the IODE and JCOMM Committees on its data management status and activities. The tasks and mission of an IODE National Oceanographic Data Centre (NODC) are described in the Guide for Establishing a National Oceanographic Data Centre (IOC Manuals and Guides No. 5, Second revised edition, 2008): The mission of a National Oceanographic Data Centre is to provide access and stewardship for the national resource of oceanographic data. This effort requires the gathering, quality control, processing, summarization, dissemination, and preservation of data generated by national and international agencies The full range of data management tasks to be carried out by a national oceanographic data management system can be summarized as follows: receiving data from national, regional and international programmes collecting oceanographic data; verifying the quality of the data (using agreed upon standards); ensuring the long term preservation of the data and associated information required for correct interpretation of the data; and making data available, nationally and internationally. National Responsibilities include: Receiving data from researchers, performing quality control, and archiving; Receiving data from buoys, ships and satellites on a daily basis, processing the data in a timely way, and providing outputs to various research and engineering users, forecasters, experiment managers, or to other centres participating in the data management plan for the data in question; Reporting the results of quality control directly to data collectors as part of the quality assurance module for the system; Participating in the development of data management plans and establishing systems to support major experiments, monitoring systems, fisheries advisory systems; Disseminating data on the Internet and through other means (and on CD- ROM, DVD, etc); ( Publishing statistical studies and atlases of oceanographic variables, Providing indicators for the different types of data being exchanged in order to track the progress. International Responsibilities include: Participating in the development of international standards and methods for data management through the IODE and JCOMM; Participating in international oceanographic data and information exchange through the IODE and JCOMM, the Joint Commission for Oceanography and Marine Meteorology; Assisting with data management aspects of global or regional programmes or pilot projects through IODE and JCOMM and in the framework of, inter alia, the IOCs Strategic Plan for Oceanographic Data and Information Management; Operating as a data assembly and quality control centre for part of an international science experiment; Operating regional, specialized or World Data Centre (WDC) on behalf of the international science community. Current governance structure of IODE In addition to structural elements, the group reviewed the current governance structure of IODE. These include: The IODE Committee IODE Groups of Experts IODE Steering Groups IODE Inter-sessional working groups IODE Task Teams IODE national coordinators for data management IODE national coordinators for marine information management IODE Officers The IODE Committee As a primary subsidiary body of the IOC, the IODE programme is governed by the IODE Committee which reports directly to the IOC Assembly. As such the IODE Committee formulates Recommendations that are submitted to the IOC Assembly and then become decisions (formerly Resolutions). History: During the Intergovernmental Conference on Oceanographic Research, 1960, at which the setting up of an Intergovernmental Oceanographic Commission was recommended, certain initial tasks for the new Commission were outlined and amongst these was included the requirement for a structure to co-ordinate international oceanographic data exchange. The first formal establishment of a Working Group on Exchange of Oceanographic Data was made by IOC Resolution I9 adopted at the First Session of the Commission in October 1961, which also prescribed that: The mission of this Working Group shall be the facilitating of exchange of oceanographic data, the standardization of forms for reporting and coding data, the encouragement of the preparation of data catalogues, and the assistance of development of national oceanographic data centres. The Commission authorized the continuation of the Working Group at its Second Session (September 1962). In 1986, at its 12th Session, the Working Committee on International Oceanographic Data Exchange, renamed itself to 'the Working Committee on International Oceanographic Data and Information Exchange' As from its 13th Session, the Working Committee on International Oceanographic Data and Information Exchange was known as the 'IOC Committee on International Oceanographic Data and Information Exchange' (IODE) The Fourteenth Session of the IOC Assembly (Paris, 17 March - 1 April 1987) noting the increasing interest in marine scientific information ... recalling also the decision of the Executive Council at its Nineteenth Session, on the Guidelines for the Structure and Responsibilities of the Subsidiary Bodies of the Commission, changed the name of the Technical Committee on International Oceanographic Data Exchange to the IOC Committee on Oceanographic Data and Information Exchange, retaining the acronym IODE. The Eighth Session of the IOC Assembly (1973) decided that the Working Group for International Oceanographic Data Exchange be renamed Working Committee (Resolution VIII31) and it also amended its Terms of Reference (Report of the Eighth Session of the IOC Assembly, Document SC/MD/39, Annex V, page 8, Item II). The Working Committee on International Oceanographic Data Exchange shall: facilitate exchange of oceanographic data, the standardization of forms for reporting and coding data, the encouragement of the preparation of data catalogues and the assistance of development of national oceanographic data centres; facilitate exchange of, and access and referral to, information resulting from, or relating to marine programmes emanating from related activities (ASFIS, MEDI, UNISIST, UNEP, IRS, CODATA, etc.); review and re-appraise the whole international oceanographic data exchange system, recommending changes to the Commission, as appropriate; continue and encourage format standardization for use with automated techniques for data input, storage, retrieval dissemination and exchange; continue the development of means whereby geological-geophysical, biological, special air-sea interaction, marine pollution data and data from continuously recording and remote sensors are incorporated into the international oceanographic data exchange system; take action as necessary to give effect to the Commission's policy decisions, within its prescribed Terms of Reference; make recommendations to the Commission on policy matters within its Terms of Reference and on the need for Consultants and/or temporary Groups of Experts to deal with special scientific and technical matters connected with the Commission's programmes; report regularly and make recommendations to the Commission of the work accomplished and on future action required and prepare with the assistance of the Secretary, a draft two-year programme of the work and financial requirements for submission to each Assembly; maintain close collaboration with World, National, Regional and Responsible Data Centres, with the other Working Committees, with the International Co-ordination Groups for the Co-operative Investigations, and with international organizations, within its Terms of Reference; have the right to form ad hoc task teams to carry out specific parts of the work of the Committee during intersessional periods provided no costs fall on the Commission; make recommendations to the Assembly and the Executive Council regarding the provision of technical guidance and for the formulation and execution of the marine science programmes of UNESCO relating to marine data and information management, and, when appropriate, to facilitate co-ordination with related programmes of other ICSPRO agencies. The terms of reference for the IODE Committee have not been revised since the 8th Session of the IOC Assembly in 1973. Membership of the IODE Committee includes: - the two IODE Co-Chairs - the IODE National Coordinators for Ocean Data Management the IODE National Coordinators for Marine Information Management and the Directors of the WDCs-Oceanography and WDCs-Marine Geology and Geophysics In accordance with the IOC Rules of Procedure the IODE Committee elects its own Chair. In the case of IODE the Committee decided to have two Co-Chairs, with special attention to geographic and gender distribution. Co-Chairs are elected for a term of two years (one inter-sessional period), renewable once. The IODE Groups of Experts The strategy and structure of Groups of Experts has been revised by IODE-XIX following the recommendations made by the IODE Review (2005). IODE-XIX adopted Recommendation IODE-XIX.2 (which was adopted at the 24thSession of the IOC Assembly in June 2007). The Terms of Reference of the IODE Groups of Experts: (i) Objectives: a. IODE Groups of Experts will undertake detailed scientific and technical studies and/or co-ordination tasks, by subject or region, as identified by the IODE Committee; b. IODE Groups of Experts, including the JCOMM/IODE ETDMP, will monitor scientific and technical developments, and identify needs to be addressed by IODE, as pertaining to their IODE subject area and propose a work programme with clear priorities, for consideration by the IODE Committee; c. To facilitate implementation of the Groups of Experts work programme, the Groups of Experts will (i) seek cooperation from IODE national coordinators; (ii) develop and implement projects with clear objectives and deliverables, and take responsibility for the coordination and management of such projects. (ii) Membership: a. the total number of Members of IODE Groups of Experts should not exceed 8; b. the Groups should be composed of not more than 4 long-term members; and not more than 4 short-term members; c. The long-term members will be selected by the Executive Secretary, based upon nominations from Member States and further based upon individual expertise as relevant to the concerned IODE Group of Expert. Long-term members can remain a member of the Group during not more than 4 inter-sessional periods; d. The short-term members shall be selected by the long-term members of the Group, based upon their specific expertise, documented in the OceanExpert system, related to specific tasks or projects and will remain a member during, preferably, not more than two inter-sessional periods; According to the IOC Rules of Procedure Groups of Experts are secondary subsidiary bodies. IODE Steering Groups As IODE has established an increasing number of projects it was then also decided that these projects should be managed by Steering Groups. Each IODE Project is established through a Recommendation. The Recommendation usually has two annexes: (i) Terms of reference of the Project; (ii) Terms of Reference of the Steering Group (including membership). Membership of Steering Groups is not based on nominations by Member States but on national experts coming forward as volunteers to participate in projects. IODE Inter-sessional working groups Working Groups are established during IODE Committee meetings. They are usually inter-sessional working groups which means that they work between two sessions and report back to the Committee or to the Officers when they meeting between two Sessions of the Committee. IODE Task Teams Task teams are usually small groups that are given a short-term well defined task. They are created by the IODE Committee. IODE national coordinators for data management IODE national coordinators for data management are the officially designated representatives of a country's data and information centres in the IODE Committee. They participate in Sessions of the Committee and as such determine the strategy and work plan of the IODE Programme. IODE national coordinators are mostly Directors (or another data centre expert nominated by the Director) of National Oceanographic Data Centres. IODE national coordinators for marine information management Until September 2004 there was only one IODE National Coordinator for each country that participates in the IODE Programme. They represented both their national data management and information management centres. GEMIM-VII, in 2002, recommended that IODE should also have national coordinators for marine information management (Recommendation MIM-VII.1). This recommendation was adopted by IODE-XVII (2003) and by IOC-XXIII (2003). On 21 September 2004 the IOC Secretariat sent out Circular Letter 2125 inviting Member States to identify an "IODE National Coordinator for Marine Information Management". IODE national coordinator for marine information management are usually marine librarians associated with either the same institution that hosts the NODC, or they can be a librarian of another national institution that has a marine library. A problem which often occurs is that IODE national coordinators for data management also designate themselves as IODE national coordinators for marine information management. This, in some cases, is caused by misunderstanding of the term marine information which, due to translation from/into other languages, is interpreted as meaning the same as data. ADU focal points While the terms of reference of the ADUs mentions Be invited, as observers, in Sessions of the IODE Committee this does not make ADU focal points full members of the Committee: they are non-voting observers. This distinction is not present a problem in terms of ownership of IODE if/when the number of ADUs comes close to the number of IODE national coordinators (who do have voting rights in the Committee). The observer status may also have an impact on the ability to submit project proposals and activities and thus utilize IODE financial resources. ADUs will be able to submit project proposals and activities with the knowledge of their respective IODE national coordinator (in the case of national ADUs). IDENTIFY AND EVALUATE THE BENEFITS IODE DERIVES FROM THE CURRENT STRUCTURE, PROJECTS AND ACTIVITIES Benefits that IODE derives from the current structure IODE is a primary subsidiary body of the IOC which is an intergovernmental Organization. As explained previously the Committee prime membership is composed of IODE national coordinators (for data management and for information management) who are officially designated by their Government. This makes the IODE Committee an intergovernmental body. This gives a certain weight to the Committee as the IODE national coordinators, when participating in meetings of the Committee, can speak on behalf of their Government. Similarly, the IODE Groups of Experts membership is based on officially designated experts. The fact that these experts are officially designated also facilities their interaction with their official representatives to the IOC Assembly, thereby ensuring that the requirements and activities of IODE are well known by the country representatives. If the IODE Committee would be composed of experts who are not officially designated by national governments then the link between the IODE experts and the national representatives to the IOC Assembly would be much weaker. Looking at projects, the current structure and methods to establish projects is very simple: experts can submit a proposal as a working document prior to a Session of the IODE Committee. This proposal will be briefly introduced during the IODE Committee Session and, in most cases (provided the requested funding can be accommodated in the work plan and budget) will be approved by the Committee. EVALUATE ANY WEAKNESSES OF THE CURRENT IODE STRUCTURE, PROJECTS AND ACTIVITIES AND FORMULATE WAYS TO REMEDY THESE WEAKNESSES In terms of governance structure a possible weakness of the current structure is that one country can have only one designated national coordinator for data management and one for marine information (library) management. While this was sufficient in the past (basically until the mid-1980s) when IT infrastructure was a heavy investment that needed to be centralized in one national data facility (NODC), the rapid evolution in computer technology as well as the expansion in data types and new areas of ocean research and observation have made that there are now often multiple national facilities that manage, store and disseminate ocean data and information. While ideally the NODC should then assume the additional role of establishing and coordinating a national network of ocean data centres, this is not commonplace and we therefore observe many facilities that manage data but are not associated with IODE. As such we are at risk of missing out on subject matter expertise and a considerable volume of valuable scientific data that may also be at risk of being lost (e.g. in the case project that terminate). Some countries have decided to establish more than one NODC, while others have joined IODE as ADUs (since 2013). Having more than one NODC per country can unbalance the IODE Committee when formal voting is required as IOC votes on the principle of one vote per country. As such, if there are several NODCs for one country then they need to agree on how to vote. The new Associate Data Units have created a different potential problem: in the terms of reference of ADUs it is clearly stated that they can participate in IODE Committee sessions as observers. This means that they do not have the right to vote. However, as the number of ADUs has increased quite rapidly (from 0 in 2013 to 22 in 2016) we may reach a situation where we have as many ADUs and NODCs. Excluding half of the IODE data centres from voting would then be quite undemocratic. To this we add that some of the ADUs are at present national facilities while others are regional or international organizations. Regarding IODE groups of experts we have mentioned that their membership is composed of least 4 officially designated members. A potential problem with this mechanism is that these individuals may not have the necessary expertise to deal with the issues that are assigned to the Group. In addition, the expertise problem is exacerbated by the small size of the Group. The decision to re-organize Groups of Experts to include half officially designated and half selected experts has improved the situation another problem has remained: while the Groups of Experts are supposed to deal with issues identified by the IODE Committee this has seldom happened and Groups of Experts self-defined the issues they would deal with. Nevertheless, two GEs have remained: the IODE Group of Experts on Marine Information management, and the Joint JCOMM/IODE Expert Team on Data Management Practices. Both are special cases: as IODE does not have national information centres the activities of IODE MIM are implemented through the IODE national coordinators for marine information management. However, we observe also that at Sessions of the IODE Committee marine information managers are very under-represented (usually less than 5) which minimizes the opportunities for MIM experts to actively participate in IODE. As such most, if not all, MIM related activities have been started by the GE-MIM. Abolishing the GE-MIM without establishing another community based mechanism to discuss and develop MIM issues would therefore undoubtedly result in the disappearance of MIM within IODE. In terms of the creation and management of projects and activities, we must recognize that IODE has not established a culture of monitoring and reviewing its projects in a systematic way. As mentioned previously the establishment of projects is a quite simple process, projects report on progress during every IODE Committee Session but so far projects and activities are no truly result/output oriented. As most donors (including member states contributing to IOC through UNESCO) are now expecting a results-based management approach IODE must revise its project approval, monitoring and evaluation mechanisms to better justify the use of public funds for its projects and activities. Ways to remedy current weaknesses are proposed in the next chapters. PROPOSE OPTIONS FOR REVISING THE CURRENT STRUCTURE, PROJECTS AND ACTIVITIES The IODE Committee As a primary subsidiary body of the IOC, the IODE Committee is an intergovernmental body. IODE is a "Technical Committee" that is directly answerable to the IOC Governing Bodies (IOC Assembly and IOC Executive Council). Membership of the IODE Committee includes: the two IODE Co-Chairs the IODE National Coordinators for Ocean Data Management the IODE National Coordinators for Marine Information Management the Directors of the WDCs-Oceanography and WDCs-Marine Geology and Geophysics It is noted that the IODE national coordinators are national experts officially designated by their Government. As such they have voting rights in the Committee. The IODE National Coordinators for Ocean Data Management are often, but not always, Directors of NODCs. In some cases countries do not have NODCs but they may still have an IODE national coordinator for data management. IODE national coordinators for Marine Information Management should preferably be qualified Librarians working in a specialized library (Oceanography). We note that IODE does not have a formal network of marine libraries, similar to its network of NODCs. In addition to the above members meetings of the Committee are also attended by invited Organizations (international, NGO, etc.) as well as Observers. In this regard we note that the Associate Data Units (ADUs), established as a structural element of IODE through Recommendation IODE-XXII.16, are invited to participate in meetings of the Committee as Observers (We refer to page  HYPERLINK "http://www.iode.org/adu" http://www.iode.org/adu for further information on ADUs). As such ADUs do not have voting rights in the Committee. This might be an issue that needs to be taken into account if/when the number of ADUs increases substantially (currently 22 ADUs vs 63 NODCs). Note: informal discussions have been held within the GE-MIM to propose the establishment of Associate Information Units (AIUs) as equivalents of ADUs for marine information management. This issue has not been discussed by the IODE Committee. In section 7, we provide additional recommendations including that the IODE IODE Committee considers the possible establishment of Associate Information Units (AIUs) as structural elements of IODE in a similar manner as ADUs. Terms of Reference of the IODE Committee. The Eighth Session of the IOC Assembly decided that the Working Group for International Oceanographic Data Exchange be renamed Working Committee (Resolution VIII31) and it also amended its Terms of Reference (Report of the Eighth Session of the IOC Assembly, Document SC/MD/39, Annex V, page 8, Item II). The Working Committee on International Oceanographic Data Exchange shall: facilitate exchange of oceanographic data, the standardization of forms for reporting and coding data, the encouragement of the preparation of data catalogues and the assistance of development of national oceanographic data centres facilitate exchange of, and access and referral to, information resulting from, or relating to marine programmes emanating from related activities (ASFIS, MEDI, UNISIST, UNEP, IRS, CODATA, etc.) review and re-appraise the whole international oceanographic data exchange system, recommending changes to the Commission, as appropriate continue and encourage format standardization for use with automated techniques for data input, storage, retrieval dissemination and exchange continue the development of means whereby geological-geophysical, biological, special air-sea interaction, marine pollution data and data from continuously recording and remote sensors are incorporated into the international oceanographic data exchange system take action as necessary to give effect to the Commission's policy decisions, within its prescribed Terms of Reference make recommendations to the Commission on policy matters within its Terms of Reference and on the need for Consultants and/or temporary Groups of Experts to deal with special scientific and technical matters connected with the Commission's programmes report regularly and make recommendations to the Commission of the work accomplished and on future action required and prepare with the assistance of the Secretary, a draft two-year programme of the work and financial requirements for submission to each Assembly maintain close collaboration with World, National, Regional and Responsible Data Centres, with the other Working Committees, with the International Co-ordination Groups for the Co-operative Investigations, and with international organizations, within its Terms of Reference have the right to form ad hoc task teams to carry out specific parts of the work of the Committee during intersessional periods provided no costs fall on the Commission make recommendations to the Assembly and the Executive Council regarding the provision of technical guidance and for the formulation and execution of the marine science programmes of UNESCO relating to marine data and information management, and, when appropriate, to facilitate co-ordination with related programmes of other ICSPRO agencies IODE management structure Background and problem statement IODE is a primary subsidiary body of IOC and is subject to the IOC Rules of Procedure as adopted by the IOC Assembly at its 21st Session through Resolution XXI-4 (IOC/INF-1166). According to Rule 25, the Chairperson of each subsidiary body shall be elected by the body concerned. In the case of IODE, two co-chairs are elected at each session of the Committee and co-chairs can serve a maximum of two terms (two intersessional periods). The previous IOC Manual (IOC/INF-785, revised 1989) referred to the chair(s) of subsidiary bodies as Officers, and until IODE-XVIII, the IODE chair and vice-chair were the Officers of IODE. IODE-XVIII revised the composition of the IODE Officers based on the recommendations of the IODE Review (2005) to include the IODE Chair, IODE Vice-Chair, chairs of groups established jointly with other organizations, and chairs of IODE Group of Experts. In addition, the Committee agreed that the WDC Directors and selected regional, scientific or technical experts may be invited to IODE Officers Meetings, if the agenda calls for them. The IODE Officers have the following tasks: (i) to review progress of the work plan and budget, (ii) update the action sheet based on responses from the projects and activities, (iii) identify any issues that need attention, and (iv) prepare for the coming IODE committee session.. Currently, the IODE Officers are composed of two IODE co-chairs, the chairs of Groups of Experts, and previous co-chairs. The current Groups of Experts are Group of Experts on Marine Information Management (GE-MIM) and the Joint JCOMM/IODE ETDMP. Additional representatives from IODE projects and activities have been invited to attend the Officers meeting as appropriate. Note that the former IODE Group of Experts on Biological and Chemical Data Management and Exchange Practices (GE-BICH) and IODE Group of Experts on OBIS were abolished by IODE-XXIII. The IODE Committee meets every two years and the IODE Officers meet once during the inter-sessional period and once just prior to a Session of the IODE Committee. Recommendations on IODE Management Structure The present composition of the IODE Officers does not encompass the broad IODE objectives and strategies and the current structure of IODE. Groups of Experts have been abolished (except GE-MIM and the Joint JCOMM/IODE ETDMP) and a new ICSU World Data System established. Recommendation: It is proposed that the current IODE Officers described above be replaced with the IODE Management Group (IODE-MG) comprising up to six members: The current two IODE Co-Chairs One expert on data management (IODE-DM) One expert on information management (IODE-IM), and One or both past IODE Co-Chairs (to be agreed by past co-chairs) Head of the IODE Project Office (non-voting member) The inclusion of one or both the past IODE co-chairs will provide continuity from the preceding intersessional period. IODE co-chairs will be elected by the full Committee of IODE under the existing election procedures. The IODE-DM and IODE-IM experts will be nominated by the Chairs of the Project Steering Groups or by other members of the IODE community to the current IODE co-chairs for consideration by email. The nomination should include a resume (bio), a statement of why the person believes he/she is qualified to undertake this task, and whether the person has the support of his or her host institution to devote time to this task. The IODE Co-Chairs will then select one IODE-DM and one IODE-IM from the nominees. The IODE-MG will work by email or video conference as appropriate. They should meet once every three months or as appropriate and may meet face-to-face once during the intersessional period. The IODE-MG may invite Subject Matter Experts (SME), the chairs of the Steering Groups of Projects, and observers to meetings to provide advice via video conference or email. Organizing online meetings with a large group could very challenging and may not be realistic, however. The IODE-MG has the authority to appoint, by consensus, an interim IODE-IM or IODE-DM member at any time should the existing one be unable to fulfil his/her duties. Similarly, the IODE-MG has the authority to recommend, by consensus, to the IODE committee to appoint additional voting IODE-MG members as the need arises. The IODE-MG will have the following terms of reference: Be responsible for reviewing progress of the work plan and budget approved by the IODE Committee and adjusting them as required. Oversee the assessment of IODE projects and activities and recommend their endorsements when these meet the agreed evaluation criteria. Evaluate for efficacy the existence of any existing IODE groups formed by the IODE Committee. Twelve months after each IODE session and four months before the next IODE session, IODE Projects and Activities leads will provide written submissions to the IODE-MG describing: Activities implemented since the last IODE session Milestones, results, and outcomes achieved Problems experienced and measures taken Status of their approved work plan and budget Any actions requested from the IODE-MG The IODE Project Office Secretariat will provide technical support to the meetings of the IODE-MG as appropriate and within resources. IODE Management Group (IODE-MG) Individual Roles and Responsibilities IODE co-chairs (shared): Chair IODE sessions and intersessional meetings Manage the progress of IODE implementation Ensure timely and complete production of documentation for Committee Sessions Help communicate IODE-MG decisions in a timely manner to the community Represent IODE at meetings of relevance to IODE It is noted that ONLY the IODE Committee can formulate formal recommendations (to the IOC Assembly) or make decisions. The IODE-MG can therefore only make recommendations to the IODE Committee. However, the IODE-MG can, as could the current Officers, amend the inter-sessional work plan and associated funding, based upon (lack of) progress other factors that require urgent action. IODE past co-chair(s): Advise the IODE co-chairs and the IODE-MG on IODE matters Provide continuity considering past experience Represent IODE at other fora as requested by the IODE-MG Data Management (IODE-DM) member: Advise the IODE-MG concerning overall IODE data management matters Represent IODE in JCOMM data management groups such as: Data Management Program Area (DMPA) Expert Team on Data Management Practices (ETDMP) Chair Data Management Coordination Group (DMCG) Represent IODE in data management groups as requested by the IODE-MG considering resources (e.g. Ocean Observations Panel for Climate [OOPC], Global Ocean Observing System [GOOS]) Represent IODE at other fora as the need arises Inform the IODE community on relevant data management activities Information Management (IODE-IM) member: Advise the IODE-MG concerning overall IODE information management matters Represent IODE on external information management groups (e.g. IAMSLIC, ASFA) Represent IODE at other fora as the need arises Inform the IODE community on relevant information management activities IODE-MG terms Co-chairs, elected by IODE Committee every two years for a two-year term, renewable once. Past co-chairs until new co-chairs are elected. IODE-DM, IODE-IM members, nominated by the IODE Project chairs and other members of the IODE community every two years for a two-year term, renewable once. Interim IODE-IM or IODE-DM members can serve in that capacity up to the next Session of the IODE Committee where new members will be selected. These interim IODE-IM and IODE-DM are chosen by the Co-Chairs. Management group decision making process: The IODE-MG will reach decisions by consensus of its voting members. The IODE-MG may seek the advice of subject matter experts, project chairs, and others as appropriate to help formulate its decisions and recommendations. IOC/IODE recognition of IODE-MG members While the IODE-MG members provide their time voluntarily to these activities with the consent of their host institutions, it is highly recommended that IODE seeks to recognize their individual contributions and those of their host institution. This can be in the form of a thank you letter to the leadership of the IODE-MG member host institutions as well as to the individual member. It is important to recognize the time and effort that these individuals will do on behalf of IODE. Recommendation: it is recommended that such a Letter is signed by the IOC Executive Secretary and sent every two years, a few months prior to the IODE Committee Session. Implementation plan/timeline: submission of proposal for establishment of IODE Management Group as part of relevant IODE Recommendation to IODE-XXIV, March 2017 (and IOC-XXIX Assembly, June 2017); provisional designation of IODE-DM and IODE-IM members of the MG at IODE-XXIV (approval will depend on decision of IOC Assembly) first session of IODE-MG as from July/August 2017 Metrics for success: Responsiveness of the IODE-MG to changing community needs for ocean data and information services (seek user/stakeholder satisfaction with IODE-MG Overall impact and quality of IODE projects and activities managed Identification of priorities and funding needs/requirements. Risks and benefits: Risk: The IODE-MG may have too many tasks to address. A mitigation strategy could be to add additional non-voting members to the IODE-MG to address specific priorities and needs. Benefit: The proposed IODE-MG will help ensure a more balanced and focused implementation of the IODE work plan and strategic vision. IODE projects: Develop a process-oriented and peer-reviewed funding cycle for IODE projects and activities Background and problem statement Existing and new IODE projects- and activities- will benefit from a more effective tracking and oversight process to help ensure that they meet IODE strategic goals and objectives (effective return on investment). At present (2016), IODE manages over thirty projects (global and regional). Some of the existing projects and activities have been continuous for several years. In some cases, the deliverables and performance metrics are not clearly defined. There is an urgent need to develop and implement a harmonized mechanism for deciding and reporting what projects and activities IODE should undertake or discontinue as the case may be. We propose to adopt the following terminology. IODE Pilot Project: A temporary with limited duration (e.g., 1-2 years) requiring complete or partial direct IODE financial funding as well as project office management in-kind support. A pilot project cannot be extended/renewed: if successful then a proposal can be submitted for an IODE project. IODE Project: A temporary effort with limited duration (e.g., 1-2 years) requiring complete or partial direct IODE financial funding as well as project office management in-kind support. Projects can be renewed using a new proposal application process at the discretion of the IODE-MG. IODE Activity: A temporary effort with limited duration (e.g., 1-2 years extended as decided by the IODE-MG) requiring only IODE project office management in-kind support with defined objectives or purpose (no funding). Activities can be in the form of institutional endorsements that draw favourable attention to IODE as an organization, and help IODE to explain how it contributes to IOC objectives. IODE operational programme: a long-term project (requiring complete or partial direct IODE financial funding as well as project office management in-kind support) or activity. Such projects or activities need to be reviewed by the IODE management group at the same frequency as other projects and activities. Current examples of projects or activities include OBIS, WOD, GTSPP, GOSUD, OceanDocs, OceanExpert etc etc For clarity, these above terms should not be confused with how IODE member states define and use these terms within the context of their national or international programs. Recommendations It is essential that all IODE projects and activities carry out tasks that serve the objectives of IODE and its parent IOC. In this regard reference is made also to the IOC Strategic Plan for Oceanographic Data and Information Management. Projects or activities that serve only the needs of a sub-community of IODE and are not linked to the main objectives and strategic goals of IODE are not sustainable. Every project or activity, either a proposal for a new or existing project or activity will therefore need to justify its resourcing from IODE (IOC) by explaining how it fits in the bigger picture. A simple process is outlined below for both new and existing IODE projects and activities: Process for proposing projects and activities Regarding applications for funding from IOC (being the parent organization of the IODE programme) it needs to be taken into account that the IOC budget cycle (covering two years) and inter-sessional periods between Sessions of the IODE Committee meetings (every two years) are not fully overlapping but are out of sync by one year: e.g. if the IOC budget cycle starts on 1 January 2016 to end on 31 December 2017, the IODE Committee meets in March 2017 (and next March 2019) with its recommendations considered by the IOC Assembly in June 2017. When the IODE Committee meets, certainty exists only for the 2016-2017 UNESCO Regular Programme budget, while funding for the 2018-2019 budget is still unconfirmed. Project Proposals will be considered by the IODE Committee as elements of the IODE work plan and budget. The IODE Committee needs to balance the work plan with available financial and human resources. As the demand for resources is likely to be higher than available resources it will be important to score submitted proposals so they can be ranked in accordance to their score. Decisions on funding of projects are the authority ONLY of the IODE Committee, which includes them in the proposed IODE work plan and budget, which is then submitted for approval to the IOC Assembly (June of the same year as the IODE Committee Session). Taking into account the timing of IODE Committee Sessions (usually March) it is essential that all working documents are available to Committee members as from 1st January of the year in which the Committee is held. Below we outline a process and a timeline takes this deadline into account. PROPOSAL PROCESS/TIMELINE The IODE Project Office will provide timely announcement online (IODE Project Office web page) and via email calling for proposing projects and activities from anyone in the IODE community. Guidelines will be provided describing the proposal submission process to the IODE Project Office using a standard template. 1- DEADLINE 1: 1 May (date 0) There shall be a timely announcement online (IODE Project Office web page) and via email calling for proposing projects and activities from the IODE community (communication engagement). Anyone from the IODE community can propose activities and projects following the procedure outlined. Guidelines will be provided describing the proposal submission process to the IODE Project Office. Submission of proposals for new projects (or for renewal of projects) to the Head of the IOC Project Office for IODE. Proposals should use the structure template shown below and not exceed 5 pages (A4 size) Proposals should be submitted in English Template of proposal content elements (projects and activities) Proposed title of project or activity Describe the alignment with IODE strategy and vision What are the benefits to the IOC/IODE community? Proposed starting and end date Project leader, project team members Budget (total budget, available resources, budget requested from IODE) What is the project/activity plan? What are the goals, objectives? Describe the timeline, milestones, and deliverables How will the results be shared with the IOC/IODE community? Optional: Does the project or activity have endorsements or support from the IOC/IODE community or other national, regional, or international programs (this can be added as appendices to the proposal)? All proposals should be signed by the Project Leader and project team members. 2- DEADLINE 2: date 0 + 5 days The IOC Project Office for IODE checks proposals for compliance with the proposal template. Proposals that do not comply are sent back to the submitter with a note explaining what is missing. Submitters have 10 working days to re-submit. Failure to re-submit within that period results in rejection of the proposal 3- DEADLINE 3: date deadline 2 + 10 days The IOC Project Office for IODE checks re-submitted proposals for compliance with the proposal template. Proposals that were re-submitted but still do not comply are rejected. The submitters will be informed of this by email. All proposals received that comply with the proposal template are sent to the members of the IODE Management Group by email, with the request to review and score the proposals not later than date deadline 3 + 30 4- DEADLINE 4: date deadline 3 + 30 days Members of the IODE Management Group have been requested to review and mark all proposals they received. Guidelines for scoring are provided below under Proposal Evaluation Criteria. The IODE-MG may select a pool of independent reviewers or subject matter experts from the IODE community to provide peer-review comments regarding proposed project and activities. The Chair will collect the evaluations for all proposals from all members of the MG, calculate the average score for each proposal, rank the proposals by their average score, and prepare a summary table according to descending scores including title, score and evaluation comments. The Chair will send the summary table with the members of the Management Group asking them to approve the summary table. 5- DEADLINE 5: deadline 4 + 5 days Members of the Management Group will review the summary table and inform the Chair of the MG of their approval. If one or more of the members disagrees (discovers error) then they should inform the Chair immediately so he/she can make the necessary correction(s). The Chair will now prepare a working document for the upcoming IODE Committee Session including the reviewed proposals, the summary table with scores and evaluation comments. 6- DEADLINE 6: deadline 5 + 30 days The Chair will submit the working document to the Head of the IOC Project Office for IODE, who will post the document on the web site for the upcoming IODE Committee Session. The outcome of the proposal review process will be made public in a timely manner Based upon the above deadlines the total process will require 80 working days, i.e. approximately 4 months. Taking into account the deadline for submission of working documents this means that step 1 should start on 1 September of the year preceding the IODE Committee Session. PROPOSAL EVALUATION CRITERIA The IODE-MG will use the following criteria to assess the fitness for purpose of a project proposal or activity within the context of IODE objectives. Each member of the evaluation panel will score the proposal with 4, 2, or 0 points (score) based on their individual evaluation. Scores from all panel members will be added and a project must receive an average score of 60% or more to be considered for recommendation (endorsement) to the IODE committee by the IODE-MG. The following proposal evaluation criteria or guideline are recommended: Does the project or activity target one or more IODE objectives? Are there strong arguments to justify this assertion? Score: 4. Metric: the arguments are strong and the support is clear, Score: 2. Metric: the projector activity appears to target one or more objectives, but arguments are weak, Score: 0. Metric: the project or activity does not seem to support an IODE objective or the arguments are unconvincing. Are there tangible commitments from participating participants and countries? Score: 4. Metric: commitments are clear and documented by letters of support Score: 2. Metric: commitments are clear, but documentation is lacking Score: 0. Metric: commitments are unclear or documentation is lacking Do the project or activity deliverables enhance IODE activities? Score: 4. Metric: deliverables are easily identified with IODE deliverables? Score: 2. Metric: deliverables are clear but not easily connected to IODE deliverables Score: 0. Metric: deliverables are unclear or do not connect to IODE deliverables Is there strong support from IODE stakeholders for the deliverables of the project? Score: 4. Metric: there is documented support from, or participation of stakeholders Score: 2. Metric: there is some weakness in documented support or stakeholders are absent Score: 0. Metric: support is not documented and stakeholders are absent Are there clear performance metrics for the project? Score: 4. Metric: metrics are well explained and relevant to evaluating project against deliverables Score: 2. Metric: some metrics are poorly explained and it is unclear how they can be used in evaluating performance Score: 0. Metric: metrics are poorly defined or cannot be used to evaluate performance Does the project need financial or other support from IODE to meet its objectives? Score: 4. Metric: no support is required Score: 2. Metric: some non-financial support is desirable Score: 0. Metric: full financial support is crucial to the project Does the project or activity fill a gap in IODE activities? Score: 4. Metric: the gap is well described as is how the project addresses it Score: 2. Metric: the argument that there is a gap is not strong, or the project is now clear as to how the gap is addressed Score: 0. Metric: neither the argument of the gap, not the way the project addresses it is well presented Is there a strong governance model for the project (e.g., plan is actionable and realistic)? Score: 4. Metric: the model is well described and appears quite workable given the participants Score: 2. Metric: the model is well described, but there is some doubt of its workability Score: 0. Metric: the model is poor Overall, how strong is the project or activity proposal? Score: 4. Metric: well described, and well received by many IODE members Score: 2. Metric: well described but has more limited member support Score: 0. Metric: the proposal or activity did poorly in gaining IODE member support Process for evaluating on-going and ending IODE projects or activities IODE projects and activities will be evaluated once every year based on annual reports using an evaluation or performance criteria. IODE-MG members may choose to serve on an evaluation panel, or nominate expert(s) to carry out the evaluation on their behalf. However, once the evaluation is done, a concise, written report of results will be available to IODE-MG and IODE members no later than two months after the annual reports are received. Annual project and activity reports with information required to evaluate degree of progress shall be submitted to the IODE-MG. No evaluation panel member may provide an evaluation of a project or activity in which they are involved in any way. It is recommended that the IODE-MG or review panel use the criteria below to evaluate project and activity performance as appropriate. Results of the evaluation will be anonymized and shared with proponents. Project and activity evaluations will be circulated to IODE members. Project or activity performance evaluation criteria: Are there annual reports? Score: 4. Metric: annual reports are produced each year and on time Score: 2. Metric: there is a gap in annual reporting, or they are delivered later than expected, Score: 0. Metric: annual reporting is missing Do the reports explain annual milestones and deliverables, and present measurable results of progress towards them? Score: 4. Metric: objectives are clear and mostly documented as achieved Score: 2. Metric: objectives are clear but documentation of achievements is weak Score: 0. Metric: objectives are poorly stated or achievements are unclear. Are the project objectives still aligned with those of IODE? Score: 4. Metric: objectives are still well aligned Score: 2. Metric: there is some misalignment that can be corrected Score: 0. Metric: objectives are misaligned with IODE objectives Are participants in the proposal actively engaged based on documentation in the reports? Score: 4. Metric: reports document continuing active involvement by participants Score: 2. Metric: reports appear to show some fall off in participant involvement Score: 0. Metric: involvement by members is greatly reduced. Were the expected results obtained? Score: 4. Metric: reports document that the objectives were achieved or likely to be achieved (results driven) Score: 2. Metric: reports show partial success but achievement to date suggest that objectives will likely be met Score: 0. Metric: reports indicate little measure of success or promise that results will be obtained. IODE Management Group Actions: Projects that do not receive a positive evaluation (<60% of maximum score) will be notified of what actions need to be taken to improve performance and given an appropriate time frame for improvement. Projects that receive a negative evaluation will have IODE endorsement withdrawn at the discretion of the IODE-MG. The project may not continue to operate nor funds expended unless an approved performance improvement plan is developed and approved by the IODE-MG. The authors may propose a new project request for funding. Implementation plan IODE-XXIV in 2017: Approval of transition plan for new proposal process. Call for new proposals and activities as soon as practical at the discretion of the proposed IODE-MG but no later than 2019. The IODE-MG will review existing projects and activities based on new proposal description and organize the orderly implementation of approval and start of projects and activities under the new system. Metrics for success Evaluation of projects and activities: All IODE projects and activities, whether ongoing or proposed, need to provide clear evaluation criteria according to IODE-MG defined elements. A progress report outlines what has been accomplished based on the proposed work to date, while a final report outlines what has been accomplished. If projects and activities do not provide a final report or when progress is less than satisfactory with respect to deliverables, then these shall not be considered for another funding cycle unless clear actionable remedies are put in place. For example, if a project or activity did not provide stated deliverables or meet objectives for which funding and/or IODE Project Office support was made available then this could be considered as a metric for not recommending further support or endorsement. Documentation of success: Seek user stakeholder satisfaction with IODE projects, activities, services, document benefits, etc. Impacts: What if we do/dont fund this project/activity, sustainability of operations, oversight, funding needs and priorities. Societal benefits: Facilitation of open access data and information, publications produced as a result of this project, value added services, citation metrics (e.g., Digital Object Identifiers [DOI] or other persistent digital identifiers). Risks and benefits: It will be important to strike an appropriate balance between proposal requirements and oversight of project and activity implementation and accountability by the IODE-MG. This approach will increase the efficiency of IODE projects and activities to address IODE objectives. It offers an open proposal process that is not cumbersome or lengthy. ADDITIONAL RECOMMENDATIONS FOR THE ATTENTION OF THE IODE INTER-SESSIONAL WORKING GROUP TO REVISE THE IOC STRATETGIC PLAN FOR OCEANOGRAPHIC DATA AND INFORMATION EXCHANGE (DECISION IODE-XXIII.2) Evolving IODE While the revision of the IOC Strategic Plan for Oceanographic Data and Information Management was not included in the terms of reference of the inter-sessional working group to propose a Re-structuring of IODE, the group could not make recommendations regarding structure without considering the wider issue of IODEs strategic directions. Accordingly, the Group is providing additional comments and recommendations that can be considered by the IODE Inter-sessional working group to revise the IOC Strategic Plan for Oceanographic Data and Information Exchange. Problem Statement We considered the following question: Is IODE presently meeting the needs and requirements of products and services of the international oceanographic community and its stakeholders? The ocean community needs and requirements have changed substantially in the past decade and will continue to change as the need for improved environmental intelligence evolves. There are two interrelated aspects that should be considered. First, IODE needs to keep with the changing needs and requirements of the oceanographic community that it serves; our primary stakeholders. IODE has tried to do too much with too little funds and without an actionable, strategic, and adaptable guiding roadmap. While IOC has adopted a medium-term strategy that is based on functions, and the contributions of IODE to these functions have been document, this strategy has not yet been translated into a new IODE strategic plan. This must be addressed quite urgently. It is critically important that IODE builds on its international role, engagement strategy, and leadership particularly in those areas where IODE has strong capacity to support effectively including (1) capacity building and (2) facilitating open access to scientific oceanographic data and information. A proposed path forward Moving forward, we propose that IODE places emphasis on developing and coordinating a manageable number of actionable, high-utility strategies responsive to the needs of stakeholders and community engagement. This requires a common vision of success and clear roles, responsibilities, and accountability measurements. This approach is necessary to help ensure that IODE supports the evolving needs of its stakeholders. Specifically, we recommend a focused framework for evolving IODE built around the following objectives: Building on IODE track-proven strengths and budget (e.g., capacity building, training, and information; facilitate or support a more timely and efficient development of authoritative scientific data and information management standards and best practices; and facilitating full and open access of data and information) Increasing IODEs visibility and enhanced communication (e.g., need to dedicate effort to promoting and sharing with others what IODE does well at the international, regional, and national levels); Increasing effective deliverables, accountability, and benchmarks of success to its current projects and activities (e.g., keep what works, terminating what does not work well based on performance metrics); Using a more open process-oriented peer-reviewed proposal framework to take on future funded projects and non-funded activities; Actively fostering strategic alliances and synergies with regional and global organizations with overlapping mission roles with IODE (e.g., capacity building, data management, information management, ocean data standards and best practices related to ocean data management and exchange, etc.). Increase IODE stakeholder community engagement and seek strategic alliance/synergy with international organizations. To achieve these objectives, the Team recommends evolving IODE. IODE should develop a realistic, adaptable, ocean-community relevant, and decision-making strategic plan. This plan needs to align with the high level IOC and IODE strategic plan (SeeDecision IODE-XXIII.2 Inter-sessional working group to revise the IOC Strategic Plan for Oceanographic Data and Information Exchange) and based on a budget plan. IODE is vulnerable to uncertainty in sustainability and level of funding to carry out its work plans. Our IODE Restructuring Group initially considered developing recommendations for enhancing IODE funding options under the rules of IOC/UNESCO. We were unable to carry out this task as we had hoped. We recommend to the IODE XXIV committee to consider establishing an inter-sessional working group to propose a review of IODE budget to help achieve an efficient and optimal use of its financial resources to ensure the continued relevance to IODE goals and mission to the ocean data and information communities. Who are the IODE stakeholders? Historically, the primary goals of IODE have been to serve the needs of the IODE community (stakeholders) in 4 areas: Coordination of ocean data management for international data access Coordination with other international programs with major data and information management components Coordination of national ocean information services, and Capacity building in data and information management The above areas of operations are generally delivered through the IODE Project Office, and through member's national activities and resource contributions. The IODE (Project Office and member activities) pursues several objectives Global activities: Global projects or activities are implemented by many IODE experts through their national oceanographic data center or marine library, or through the IOC Project Office for IODE, or both. Regional activities: IODE's regional program focuses on capacity building related to oceanographic data and information management in a regional context Support to the Joint WMO-IOC Technical Commission for Oceanography and Marine Meteorology (JCOMM): Through this objective the IODE, both at the international level (through IODE projects and other program activities) as well as at the national level (through the IODE National Oceanographic Data Centers and Marine Libraries) provides data and information management services in the areas of ocean science, ocean observations, tsunami warning and mitigation, coastal area management and marine information management. Training and education. To assist Member States to acquire the necessary capacity to manage marine data and information and become partners in the IODE network. Data and information portals (access): Compiling a list of ocean data sources developed and maintained by IODE National Oceanographic Data Centers and Online Repositories of marine information (Clearinghouse) Support of Ocean Biogeographic Information System (OBIS): IODE support to IOC IODE is a primary subsidiary body of IOC and so is expected to support the IOC objectives outlined in their most recent Medium-Term Strategy (2014-2021). They are: Healthy ocean ecosystems and sustained ecosystem services. Effective early warning systems and preparedness for tsunamis and other ocean-related hazards. Increased resiliency to climate change and variability and enhanced safety, efficiency and effectiveness of all ocean-based activities through scientifically-founded services, adaptation and mitigation strategies. Enhanced knowledge of emerging ocean science issues. IODE contributes to all of the above IOC objectives in one form or another. The IOC medium-term strategy divides the tasks of reaching objectives into 6 areas (functions): ocean research observing system / data management early warning and services assessment and information for policy, sustainable management and governance, capacity development IODE figures prominently in many of the IOC capacity development activities IODE support to International Programs International cooperation is needed to undertake measurements at global-scales. These scientific data collected and information products generated form the data represent a significant public investment to supplement global environmental intelligence on our changing planet. There are many international programs and activities to which IODE provides support, such as for example, the IOC, the Joint IOC/WMO Technical Commission for Oceanography and Marine Meteorology (JCOMM), and the Aquatic Sciences and Fisheries (ASFA) network, the International Association of Aquatic and Marine Science Libraries and Information Centers (IAMSLIC); and the International Council for Science World Data System (ICSU-WDS). OBIS also contributes to marine initiatives of the Convention on Biological Diversity (CBD) and global assessments such as the UN World Ocean Assessment, the Group on Earth Observations (GEO). IODE collaborates with JCOMM through the JCOMM Data Management Program Area (DMPA) and its JCOMM/IODE Expert Team on Data Management Practices (ETDMP) to implement and maintain a fully integrated end-to-end data management system across the marine meteorology and oceanographic community. The JCOMM Data Management Coordination Group (DMCG) has a place for representatives from IODE. At present, the IODE Co-Chair also chairs the Data Management Coordination Group (DMCG). IOC and IAMSLIC established a Memorandum of Agreement on General Cooperation in 2011 to strengthen cooperation between both organizations in the field of marine information management through (i) providing training and support to build human capacity related to marine information management; (ii) promoting networking of marine information managers; and (iii) promoting the capacity of libraries and information centers to disseminate and provide access to, marine scientific literature for the benefit of marine scientists and other relevant users. The Joint IODE/IAMSLIC Group of Experts on Marine Information Management aids in the development of the IODE OceanTeacher initiative by identifying a number of resource persons who will contribute content and lecturers, promote the activities of IOC/IODE's marine information management (MIM) activities and collaborates with IODE on the further development of the IAMSLIC Aquatic Commons e-repository. In turn, IODE hosts the Aquatic Commons Repository for IAMSLIC and provides IT assistance to the repository. IODE provides IAMSLIC membership opportunities to the Marine Information Members of IODE to assist in common networking and educational goals and encourages IODE Marine Information Members to participate in IAMSLIC meetings. The ICSU WDS promotes long-term stewardship of, and universal access to, scientific data and data services, products, and information across a range of disciplines. ICSU and IODE have been partners since the early 1960s through the ICSU system of World Data Centers (WDCs) (especially the WDCs Oceanography in Silver Spring, USA; now called World Data Service for Oceanography; Obninsk, Russian Federation; Tianjin, China). In February 2013 ICSU and IOC/IODE signed a Letter of Agreement which defines the conditions under which IODE will contribute to the ICSU WDS as a Network Member. The WDS for Oceanography is one component of a global network of discipline sub-centers that facilitate international exchange of scientific oceanographic data and is hosted by NOAA's National Centers for Environmental Information (NCEI). NCEI consolidates the former U.S. National Oceanic and Atmospheric Administration (NOAA) data centers: The National Climatic Data Center (NCDC), the National Geophysical Data Center (NGDC), and the National Oceanographic Data Center (NODC). Present IODE Objectives The main objectives of the IODE Program are (revision IODE-XXII, March 2013): To facilitate and promote the discovery, exchange of, and access to, marine data and information including metadata, products and information in real-time, near real time and delayed mode, through the use of international standards, and in compliance with the IOC Oceanographic Data Exchange Policy for the ocean research and observation community and other stakeholders; To encourage the long term archival, preservation, documentation, management and services of all marine data, data products, and information; To develop or use existing best practices for the discovery, management, exchange of, and access to marine data and information, including international standards, quality control and appropriate information technology; To assist Member States to acquire the necessary capacity to manage marine research and observation data and information and become partners in the IODE network; To support international scientific and operational marine programs, including the Framework for Ocean Observing for the benefit of a wide range of users. These objectives are set by IODE members and so reflect the range of operations and services that they expect to receive through their participation in IODE. Membership is voluntary. The responsibility of an IODE member is that they contribute to international activities as they are able, in exchange for activities and services conducted by IODE that benefit them. Evolving IODE: Developing a realistic and decision-making strategic plan. [A] Background and Problem statement: Recalling the initial idea of the establishment of IODE as one of the most important programs of IOC at its beginning stage, the essential role of IODE is to promote international oceanographic data and information exchange based on the secure archival and workable dissemination system of oceanographic data and information, by fully taking into account the changing needs of international ocean sciences and services activities. IODE has been evolving since its establishment in 1960s, and trying to meet the scientific and societal needs, which have changed with time. For example, climate change became one of the most crucial problems in the international not only oceanographic but also political community since the 1980s, and IODE initiated several projects in close cooperation with related organizations and programs to meet the requirements of global climate studies, including the Global Temperature and Salinity Profile Program (GTSPP), the Global Oceanographic Data Archaeology and Rescue (GODAR), and many other activities. While the climate issue is still emerging, societal needs have also been raised including disaster prevention, tsunami early warning and mitigation system, conservation of biodiversity, and coastal zone management and marine spatial planning. In 2015 the UN adopted the new Agenda 2030 with Sustainable Development Goals (SDGs), in particular, the SDG-14 calling to conserve and sustainably use the oceans, seas and marine resources for sustainable development. And most recently, the Group of Seven (G7) of industrialized democracies Science and Technology Ministers Meeting agreed and released the Tsukuba Communique, which clearly stated The Future of the Seas and Oceans as one section. This section described actions to take including Promote open science and the improvement of the global data sharing infrastructure to ensure the discoverability, accessibility, and interoperability of a wide range of ocean and marine data. Having considered these recent trends in high level international policy, together with the continuous needs in ocean sciences and services, IODE should effectively meet these requirements by improving its structure and ways of management from a more strategic viewpoint. The number of projects in the IODE framework, for example, exceeds thirty (30) as of 2016, which may have caused less monitoring of their progress, fewer communications between the Secretariat and projects, and in some cases duplicated activities whch should have been avoided. [B] Recommendation: The IODE strategic plan should build on a manageable number of actionable, impact-based, relevant strategies aligned with the purpose of IODE and stakeholders needs. We suggest that IODE focuses primarily on three strategies: 1. Facilitate international open scientific data and information sharing mechanisms with minimum delay (i.e., IOC Oceanographic Data Exchange Policy, 2003, Global Earth Observation System of Systems [GEOSS] data sharing principles). Elevate or enhance the role of IODE engagement in international data and information management activities 2. Facilitate the development of authoritative scientific data and information management standards and best practices. Improve knowledge of stakeholder needs, better understand how they use the data and apply the information via authoritative data standards in close collaboration with related organizations (e.g., IODE/JCOMM Ocean Data Standards process). 3. Enhance membership engagement including capacity building, training, and information. Increase IODE stakeholder community engagement and interaction. Foster strategic alliances with selected regional and global organizations with overlapping mission roles with IODE such as Group of Earth Observations (GEO), Global Ocean Observing System (GOOS), Integrated Ocean Observing System (IOOS), Foundations and Charitable Trusts, etc. Membership in IODE brings with it a responsibility to take an active role in its activities. There are a number of ways IODE members can contribute. Members can: Volunteer to monitor specific international activities which have a bearing on IODE and report on these to the IODE Management Group and IODE Committee. Ensure that data and information management issues of importance to IODE are well presented and discussed at IODE and international meetings. Volunteer to represent IODE at external fora when such gatherings are taking place in their region. Take an active role in IODE discussions and decisions. Support IODE projects especially if they align with their national activities. Promote, share, and partner with others in services that IODE services at the international, regional, and national levels. Measure of success: It is important that IODE focuses primarily on those areas where IODE has a strong capacity to lead. This means adopting metrics to better manage relevant IODE projects and activities to increase efficiency and decrease redundancy in oceanographic data and information management efforts. Below we offer some examples: Obtain user stakeholder level of satisfaction with IODE strategic focus areas Timely publication of relevant standards and best practices based on ocean community needs. IODE stakeholder community engagement and interaction. Fostering strategic alliances with regional and global organizations with overlapping mission roles with IODE such as Group of Earth Observations (GEO), Global Ocean Observing System (GOOS), Foundations and Charitable Trusts, etc. Associated Information Units (AIU) Data and Information Users The IODE system forms a worldwide service oriented network of National Oceanographic Data Centers (NODCs), Marine Science Libraries and Information Centers, Associated Data Units (ADU), and it collaborates closely with the ICSU and WDS resulting in IODE acceptance as a network member of WDS. During the past 50 years, IOC Member States have established 80 oceanographic data centers and 55 National Centers for Marine Information in IOC Member States. The IODE ADU is intended to bring other marine science and information institutions in the wider ocean research and observation communities as key stakeholders of the IODE network. Recommendation: it is recommended that the IODE Committee considers the possible establishment of Associate Information Units (AIUs) as structural elements of IODE similar in concept as the ADUs. Other members of this group include researchers (who also contribute environmental data and information), governmental organizations, and public and private sector agencies. Their interests are usually quite focused, the services they require are often time dependent, and they may or may not be well informed of the scope of national and international ocean data and information activities. If they contact IODE, they expect well informed answers to their questions, and easy access (directly or through pointers) to the international groups that can directly answer their questions. Role of IODE in facilitating the development of JCOMM Global Data Assembly Centres (GDACS) The IODE Global Data Assembly Centres (GDACs) contribute to the Marine Climate Data System (MCDS) as established by JCOMM-4 (2012). The MCDS vision is primarily to coordinate a dedicated WMO-IOC data system. The IODE GDACs were established as structural elements of IODE by the IODE Committee at its 22nd Session, through Recommendation IODE-XXII.13. The current IODE GDAC Terms of Reference are as follows: receive and assemble marine meteorological and/or oceanographic data (real or delayed-mode) and metadata from the appropriate data streams and check the are consistent; identify duplicates and if possible resolve by keeping the best copy of a dataset; make sure that the data are quality controlled according to the international standards and methods established by IODE, WMO or JCOMM as appropriate; provide feedback to the sources of data regarding quality issues; make data accessible through IODE/ODP; make discovery metadata available to IODE/ODP; forward data and metadata to the appropriate CMOC(s) in agreed format(s) within defined timescales; contribute to WMO and IOC Applications by collecting and processing worldwide marine-meteorological and oceanographic data and metadata documented in appropriate WMO and IOC publications; report to the IODE and JCOMM Committees on its data management status and activities At present, IODE GDACs and WMO GDACs have disparate data requirements under the JCOMM and this negatively impact the open exchange of oceanographic and meteorological data under one MCDS. What is needed is to amend the Terms of Reference for JCOMM GDACs to make WMO Information System (WIS) and IODE Ocean Data Portal (ODP) data requirements optional. This does not prevent IODE or WMO GDACs from communicating with WIS and/or ODP formats or from jointly working towards standards and best practices, metadata management and the exchange data, information and services with JCOMM/IODE ETDMP. WMO-IOC Centres for Marine-Meteorological and Oceanographic Climate Data (CMOCs) could have the role of ensuring that all data represented on data discovery and access systems comply with any data standards and best practices. Recommendation: IODE to work closely with JCOMM to review and amend the ToR of the JCOMM GDAC to remove the ODP and the WIS requirements that prevents the development of joint IOC-WMO GDACs and facilitate the role of JCOMM Marine Climate Data System (MCDS) . [end of document]   HYPERLINK "http://www.oceanexpert.net/viewMemberRecord.php?&memberID=707" \h http://www.oceanexpert.net/viewMemberRecord.php?&memberID=707   HYPERLINK "http://www.oceanexpert.net/viewMemberRecord.php?&memberID=8555" \h http://www.oceanexpert.net/viewMemberRecord.php?&memberID=8555   HYPERLINK "http://www.oceanexpert.net/viewMemberRecord.php?&memberID=11859" \h http://www.oceanexpert.net/viewMemberRecord.php?&memberID=11859   HYPERLINK "http://www.oceanexpert.net/viewMemberRecord.php?&memberID=3450" \h http://www.oceanexpert.net/viewMemberRecord.php?&memberID=3450   HYPERLINK "http://www.oceanexpert.net/viewMemberRecord.php?&memberID=7337" \h http://www.oceanexpert.net/viewMemberRecord.php?&memberID=7337   HYPERLINK "http://www.oceanexpert.net/viewMemberRecord.php?&memberID=6552" \h http://www.oceanexpert.net/viewMemberRecord.php?&memberID=6552   HYPERLINK "http://www.iode.org" \h http://www.iode.org   HYPERLINK "http://ioc-unesco.org/" \h http://ioc-unesco.org/   HYPERLINK "http://en.unesco.org/" \h http://en.unesco.org/   HYPERLINK "http://www.iode.org/index.php?option=com_content&view=article&id=465&Itemid=100201" \h http://www.iode.org/index.php?option=com_content&view=article&id=465&Itemid=100201   HYPERLINK "http://www.iode.org/index.php?option=com_content&view=article&id=371&Itemid=100086" \h http://www.iode.org/index.php?option=com_content&view=article&id=371&Itemid=100086   HYPERLINK "http://www.iode.org/index.php?option=com_content&view=article&id=18&Itemid=100087" \h http://www.iode.org/index.php?option=com_content&view=article&id=18&Itemid=100087   HYPERLINK "http://www.iode.org/index.php?option=com_content&view=article&id=46&Itemid=84" \h http://www.iode.org/index.php?option=com_content&view=article&id=46&Itemid=84   HYPERLINK "http://www.iode.org/index.php?option=com_content&view=article&id=289&Itemid=100017" \l "decision23.1" \h http://www.iode.org/index.php?option=com_content&view=article&id=289&Itemid=100017#decision23.1   HYPERLINK "http://www.iode.org/index.php?option=com_oe&task=viewDocumentRecord&docID=14595" http://www.iode.org/index.php?option=com_oe&task=viewDocumentRecord&docID=14595   HYPERLINK "http://www.iode.org/nc-dm" http://www.iode.org/nc-dm   HYPERLINK "http://www.iode.org/nc-mim" http://www.iode.org/nc-mim   HYPERLINK "http://www.iode.org/index.php?option=com_oe&task=viewGroupRecord&groupID=297" http://www.iode.org/index.php?option=com_oe&task=viewGroupRecord&groupID=297  participation of Directors of WDCs-Oceanography has declined in recent years. We also need to take into account the replacement of the ICSU system of WDCs by the new World Data System (WDS).   HYPERLINK "http://www.iode.org/index.php?option=com_oe&task=viewGroupRecord&groupID=64&Itemid=46" \h http://www.iode.org/index.php?option=com_oe&task=viewGroupRecord&groupID=64&Itemid=46   HYPERLINK "http://www.iode.org/index.php?option=com_content&view=article&id=60&Itemid=101" \h http://www.iode.org/index.php?option=com_content&view=article&id=60&Itemid=101   HYPERLINK "http://www.iode.org/index.php?option=com_oe&task=viewDocumentRecord&docID=14791" \h http://www.iode.org/index.php?option=com_oe&task=viewDocumentRecord&docID=14791   HYPERLINK "http://www.oceandatastandards.org/" \h http://www.oceandatastandards.org/   HYPERLINK "http://www.iode.org/index.php?option=com_content&view=article&id=289&Itemid=100017" \l "decision23.2" \h http://www.iode.org/index.php?option=com_content&view=article&id=289&Itemid=100017#decision23.2   HYPERLINK "http://www.iode.org/index.php?option=com_content&view=article&id=15&Itemid=54" http://www.iode.org/index.php?option=com_content&view=article&id=15&Itemid=54   HYPERLINK "http://www.iode.org/index.php?option=com_content&view=article&id=43&Itemid=55" http://www.iode.org/index.php?option=com_content&view=article&id=43&Itemid=55   HYPERLINK http://www.jcomm.info    HYPERLINK "http://www.iode.org/index.php?option=com_content&view=article&id=44&Itemid=82" http://www.iode.org/index.php?option=com_content&view=article&id=44&Itemid=82   HYPERLINK "http://www.iode.org/index.php?option=com_content&view=article&id=178&Itemid=141" http://www.iode.org/index.php?option=com_content&view=article&id=178&Itemid=141   HYPERLINK "http://www.iobis.org/" http://www.iobis.org/   HYPERLINK "http://unesdoc.unesco.org/images/0022/002282/228221m.pdf" http://unesdoc.unesco.org/images/0022/002282/228221m.pdf   HYPERLINK "http://www.iode.org/cdstrategy" http://www.iode.org/cdstrategy   HYPERLINK "http://www.jcomm.info/" http://www.jcomm.info/   HYPERLINK "http://www.iamslic.org/people/committees-taskforces/iamslic-iou-mou" http://www.iamslic.org/people/committees-taskforces/iamslic-iou-mou   HYPERLINK "http://www.icsu-wds.org/" http://www.icsu-wds.org/   HYPERLINK "http://www.jcomm.info/index.php?option=com_content&view=article&id=152&Itemid=100024" http://www.jcomm.info/index.php?option=com_content&view=article&id=152&Itemid=100024   HYPERLINK "http://www.iode.org/index.php?option=com_content&view=article&id=59&Itemid=100052" http://www.iode.org/index.php?option=com_content&view=article&id=59&Itemid=100052   HYPERLINK "http://www.jcomm.info/index.php?option=com_content&view=article&id=25&Itemid=32" http://www.jcomm.info/index.php?option=com_content&view=article&id=25&Itemid=32   HYPERLINK "http://www.jcomm.info/index.php?option=com_oe&task=viewGroupRecord&groupID=117" http://www.jcomm.info/index.php?option=com_oe&task=viewGroupRecord&groupID=117   HYPERLINK "http://classroom.oceanteacher.org/" http://classroom.oceanteacher.org/   HYPERLINK "https://www.nodc.noaa.gov/worlddatacenter/" https://www.nodc.noaa.gov/worlddatacenter/   HYPERLINK "https://www.ncei.noaa.gov/" https://www.ncei.noaa.gov/   HYPERLINK "http://www.iode.org/index.php?option=com_content&view=article&id=385&Itemid=34" http://www.iode.org/index.php?option=com_content&view=article&id=385&Itemid=34   HYPERLINK "http://www.iode.org/index.php?option=com_content&view=article&id=19&Itemid=58" http://www.iode.org/index.php?option=com_content&view=article&id=19&Itemid=58   HYPERLINK "http://www.iode.org/index.php?option=com_content&view=article&id=18&Itemid=100087" http://www.iode.org/index.php?option=com_content&view=article&id=18&Itemid=100087   HYPERLINK "http://www.un.org/sustainabledevelopment/oceans/" http://www.un.org/sustainabledevelopment/oceans/   HYPERLINK "http://www8.cao.go.jp/cstp/english/index.html" http://www8.cao.go.jp/cstp/english/index.html   HYPERLINK "http://www.iode.org/index.php?option=com_content&view=article&id=51&Itemid=95" http://www.iode.org/index.php?option=com_content&view=article&id=51&Itemid=95   HYPERLINK "http://www.oceandatastandards.org/" http://www.oceandatastandards.org/   HYPERLINK "http://www.iode.org/index.php?option=com_content&view=article&id=373&Itemid=100089" http://www.iode.org/index.php?option=com_content&view=article&id=373&Itemid=100089   HYPERLINK "http://www.jcomm.info/index.php?option=com_oe&task=viewEventRecord&eventID=761" http://www.jcomm.info/index.php?option=com_oe&task=viewEventRecord&eventID=761   HYPERLINK "http://www.iode.org/index.php?option=com_content&view=article&id=372&Itemid=100088" http://www.iode.org/index.php?option=com_content&view=article&id=372&Itemid=100088   HYPERLINK "http://www.jcomm.info/index.php?option=com_content&view=article&id=44&Itemid=100024" http://www.jcomm.info/index.php?option=com_content&view=article&id=44&Itemid=100024   HYPERLINK "http://www.iode.org/index.php?option=com_content&view=article&id=26&Itemid=64" http://www.iode.org/index.php?option=com_content&view=article&id=26&Itemid=64   HYPERLINK "http://www.iode.org/index.php?option=com_oe&task=viewDocumentRecord&docID=9991" http://www.iode.org/ind%,789:=?@EISU^cpw󴧝ٓtk_SGSh;}h/R~5CJ aJ h;}hu 5CJ aJ hRp<hu 5CJaJh;}5CJaJhRp<hu CJaJh;}CJ^JaJhvxCJ^JaJh,[/CJ^JaJh CJ^JaJh;}hu CJ^JaJjh%[UmHnHuh: CJ^JaJh;}h/R~CJ^JaJh;}hRx*CJ^JaJh;}hl CJ^JaJh;}hxCJ^JaJ?dc d y gd@gdf<gd;} $a$gdf< $a$gdu ^`gdu $^`a$gd/R~ $^a$gd/R~ $a$gd/R~  . 6 7 8 9 : F H b d ޾xdR:R/jhf<hf<CJH*U\^JaJmH sH #hf<hf<CJ\^JaJmH sH &hf<hf<6CJ\^JaJmH sH h;}5CJ\aJhf<hu CJ$^JaJ$hf<h;}CJ$^JaJ$hf<hf<CJ$^JaJ$hRp<hu 5CJaJh;}hu 5h;}h/R~5h;}h/R~5CJ aJ h;}hRx*5CJ aJ h;}h-5CJ aJ h;}hu 5CJ aJ h;}5CJ aJ  " # D E Y Z d p x y z   > D õzlalVlE h5h}]CJ^JaJmH sH h@CJ\^JaJh5CJ\^JaJh5hCCJ\^JaJ#hf<hf<5CJ^JaJmH sH hf<h@5CJ\^JaJh@hf<CJ\^JaJh|ICJ\^JaJh@h@CJ\^JaJ#h@hf<CJ\^JaJmH sH #hf<hf<CJ\^JaJmH sH /jhf<hf<CJH*U\^JaJmH sH y z iOM"C>, 2# + 2# *  $a$gdSh_gdCgdf<gd;}D T 0;{o5:?GJfᷬxj\N\\@h5h6CJ\^JaJh5h)_CJ\^JaJh5h?CJ\^JaJh5h:3bCJ\^JaJh5hCCJ^JaJh5h5CJ\^JaJh5CJ\^JaJh5hCCJ\^JaJhCJ\^JaJh5h}]CJ\^JaJh7YCJ^JaJmH sH h@CJ^JaJmH sH  h5h}]CJ^JaJmH sH hCJ^JaJmH sH fgptGSfj?ARaǹǫ~q`!jhw5CJU\^JaJh: 5CJ\^JaJhf<5CJ\^JaJ#h5hzmCJ\^JaJmH sH h5hzmCJ\^JaJh5h)_CJ\^JaJh5h:3bCJ\^JaJh5hCCJ\^JaJh5h6CJ\^JaJh5h?CJ\^JaJh5hPSCJ\^JaJ"IJdefghikl    /0JKLMNORٳ٢ٳٳّٳٳـٳٳoٳ jwhwUmHnHu jhwUmHnHu j}hwUmHnHu jhwUmHnHujhwUmHnHu/h%[hwCJOJPJQJ^JmHnHtHuhwmHnHu!jhw5CJU\^JaJhw5CJ\^JaJ+RSxy -.HIJKLMRSwx޿ޠޏ~ jkhwUmHnHu jhwUmHnHu jqhwUmHnHuh( hwmHnHsH u jhwUmHnHujhwUmHnHuhwmHnHu/h%[hwCJOJPJQJ^JmHnHtHu, !"'(efءؐn jhwUmHnHu j_hwUmHnHu jhwUmHnHu jehwUmHnHuh( hwmHnHsH u/h%[hwCJOJPJQJ^JmHnHtHuhwmHnHujhwUmHnHu jhwUmHnHu+#$>?@ABCFG}~89:<=>@Aѯўэ| jMhwUmHnHu jhwUmHnHu jShwUmHnHu jhwUmHnHu jYhwUmHnHuhwmHnHu/h%[hwCJOJPJQJ^JmHnHtHujhwUmHnHu0 !#$%*+KLMghiklmrs/01KLѲѲѲѓѲq jA hwUmHnHu j hwUmHnHuh( hwmHnHsH u jG hwUmHnHuh( hwmHnHsH u jhwUmHnHu/h%[hwCJOJPJQJ^JmHnHtHuhwmHnHujhwUmHnHu,%mQ%xsuE"$%8'''(( & Fdgd&?&@&C&'8'))*ӯäÝ~ *h)hf<B*mH ph"""sH  *h iB*mH ph"""sH  h-hf<hUKhUKmH sH hUKmH sH h)hf<H*mH sH hf<mH sH hSh_mH sH  jh)hf<H*UmH sH h)hf<mH sH hf<5CJ\^JaJhf<-(e))),*-***0000000 $Ifgdf< $$Ifa$gdf<gd!P$a$gd gd;}gdf< & Fdgd>>$????????@!AA & Fgd7qcgdU & Fxgd>[>]>>>?¾Ʒư|xh;}h&h@H*h@hA< h&hA<h3 hlhl hlh h;}5CJ\aJ he45aJ hST$T,T-TUUW W(WJW_W»ɯɡɡɘɏɡɏɏɏɡɏɀ|xlch+\^JaJh&hdF\^JaJh3h+h&hM6\]^JaJhW7S\^JaJhM\^JaJh&hM5\^JaJh&hl\^JaJ hE} hM hLhMh&hM\^JaJh;}CJ\^JaJhUhUCJ\^JaJ!hUhUh|NCJ\^JaJ#KLLMM1NNNN OYO{PPQR@STT.TTKU-VVW & Fgd7qc & Fgd7qcgd& ^gd& & Fgd7qcgdMW(WWWWWW X;XxXXXYY[[[]h]1^__aa=b & Fgd7qcgddFgd& & F!gd7qcgd;}gd&_WcWkWWWWW XxXXXXIYJYYY[[[[[]]___._```aaa+a2abBbbkk»ҡ{oh&hdF\^JaJh&hdF5\^JaJhdFhZ5\^JaJhdFh,\^JaJhdFhdF\^JaJhdFhdF5\^JaJ hhp h!Hh3h3\^JaJh15\^JaJhp\^JaJhZ5\^JaJh+\^JaJhdF\^JaJ(=b>bbqc5ddOeTffghijkk\l]lllll#m & F ^`gd7qc ^gd&gdz*gd;} & Fgd7qcgddFk4l6l7l>l[l\l]lgllllqmrmnnnnoooooooo?v󿳪|xth_V_hHh_hh&hgzw5\^JaJhh\^JaJh2\^JaJh&hgzw\^JaJhph3hpCJ\^JaJh3CJ\^JaJh&hl\^JaJh&h7Y\^JaJhz*\^JaJh&hz*\^JaJh&hz*5\^JaJh&hdF\^JaJh&hZ5\^JaJh&hpH*\^JaJh&hp\^JaJ#mqmrmnnoooo ppqss'sxssu?v@vvv^`gdgzw ^gd+gdgzwgd&gd;} & FW^`Wgd7qc?vvvvzwwwxxxxxyyyzozpzzzzzz'{({z{{{{G|H||Y}Z}~ Ǿ嵬堗~rf]f]hz3\^JaJh,hz3\^JaJh'5h,\^JaJhs\^JaJjh%0J(U\^JaJh%\^JaJh,h,\^JaJh,\^JaJhJ\^JaJh3\^JaJhJhJ\^JaJh1]7\^JaJhgzw\^JaJh3h3CJ\^JaJhgzwCJ\^JaJ$v@wAwxxxxyypzzH||Z}[}~~<Mgd&gd;}gd&gdlgd+gdz3gd,gd&gd& <MW[\~1J˂BQ{|˃̃σݺ|q|cUGcGch@h15\aJmH sH h@h'\aJmH sH h@hh\aJmH sH h'\aJmH sH hh\aJmH sH h+\aJmH sH h15\aJmH sH "jh%0J(U\aJmH sH hH\aJmH sH h.\hH\aJmH sH hh\^JaJh,h6s\^JaJh,hH\^JaJhHh15\^JaJhz3\^JaJ`؄) !ĎȑБܒߒ: u}ab˙֙ĚӚ¾«Ѿ||hBihsZhPSh^hH[h15h& ghhlh;}5CJ\aJh#qh('shH5CJ\aJh;}hH h-hlh h-h h@\aJmH sH h@hh\aJmH sH h@h'\aJmH sH 0eϐ:cWX֝Pgd# & Fgd44gd>Kgdigdigdlgd;}gd&ӚWXuաABآ̸ӴӰӰ|sh`95h1R0JhwjhwUh1Rh$ h+h+ h#5h+h+6h+h#h#5h#h44jh>K0J(Uh>Kh>K5\ h>Kh>Kh>Khi5CJ\aJhi hlh;} hlh h hBihsZ-ģǥB*w {=ϰаDgd gd`pgd`pgd`pgdl2 & F$gdPSgd>Kgd]gd#آ٢:Qpxãģ~ĥťƥǥBC<=ΰϰаNPCD ¾º¾¾xhh h \^JaJmH sH hWmH sH h h H*mH sH h`p^JaJmH sH h mH sH h h mH sH h;} hl2hl2hl2hPSh>K h>Kh>K h1R5\h>Kh>K5\ h1ZDh1ZDh1ZDh]h#h$h1Rjhw0JU& ,\aDEGI۹ҼҪҼҼ򝒇wgZhV}\^JaJmH sH h h\^JaJmH sH h&hW\^JaJmH sH h&himH sH h&h mH sH h \^JaJmH sH "h h 6\^JaJmH sH +jh h H*U\^JaJmH sH h h \^JaJmH sH h hW\^JaJmH sH hW\^JaJmH sH HI+,ϺкK9:\gdPS & F gd7qc ^gd9gdgdWgd ۹*,;<κϺкһ޻78̺zjZJZJZ:h h \^JaJmH sH h@h^~\^JaJmH sH h@h \^JaJmH sH h@h\^JaJmH sH h@hf\^JaJmH sH h@h9\^JaJmH sH h@h\^JaJmH sH h@h)Pl\^JaJmH sH "h@h)Pl5\^JaJmH sH h:\^JaJmH sH hV}\^JaJmH sH hh\^JaJhBi\^JaJmH sH 8:Hڼ19bcdHpu[ñÅxk^kQ^QkQkQkQh:\^JaJmH sH h44\^JaJmH sH h\\^JaJmH sH h\^JaJmH sH hR\^JaJmH sH hV}\^JaJmH sH "h\hR5\^JaJmH sH "h\hV}5\^JaJmH sH h \^JaJmH sH h h \^JaJmH sH "h\h 5\^JaJmH sH h\^JaJmH sH \]tus[\Bmrsgd& $ & F a$gd7qc & F gd7qcgdX & F nn<^n`*^JaJmH sH "h hi56^JaJmH sH h 56^JaJmH sH hz N56^JaJmH sH h)_56^JaJmH sH "h h 56^JaJmH sH h hz N\^JaJmH sH h1R\^JaJmH sH hX\^JaJmH sH h h \^JaJmH sH h_X\^JaJmH sH 0~uv01S & F gd7qc & F^`gd7qc & Fgd7qc ^gdfgdf & Fgd)_ & F^`gd7qc & Fgd7qc & Fgd7qc}~qvvŵ򛎛qdUH8H8h hf\^JaJmH sH hZ\^JaJmH sH h hf^JaJmH sH h4 >*^JaJmH sH hz Nhf>*^JaJmH sH hH[\^JaJmH sH hq\^JaJmH sH hf\^JaJmH sH h)\^JaJmH sH h h \^JaJmH sH h h)_\^JaJmH sH h)_h)_\^JaJmH sH h)_\^JaJmH sH h \^JaJmH sH  /1QScef7xyȸ|obPbCh \^JaJmH sH "h h 6\^JaJmH sH h44\^JaJmH sH hH[\^JaJmH sH h h)\^JaJmH sH h)\^JaJmH sH h h \^JaJmH sH h h ^JaJmH sH hz Nh >*^JaJmH sH hf\^JaJmH sH h hf\^JaJmH sH h)_\^JaJmH sH hZ\^JaJmH sH $T8yz;k & F ^`gd7qcgdf & F^`gd7qc & Fgd7qc 8^8gd& & F^`gd7qc & Fgd7qc & Fgd7qcyz'+j +,GñäÊ}m]M@h%v\^JaJmH sH h hz N\^JaJmH sH h&h >*^JaJmH sH h h \^JaJmH sH hf\^JaJmH sH h \^JaJmH sH h\^JaJmH sH h44\^JaJmH sH "h h 6\^JaJmH sH h h \^JaJmH sH h&h ^JaJmH sH h&h >*^JaJmH sH hz N\^JaJmH sH GNPhij5z{$fpvŸҞҞ~o]⫸Ph\^JaJmH sH "h&h 56^JaJmH sH hd56^JaJmH sH h h 5^JaJmH sH h h \^JaJmH sH h{\^JaJmH sH h4 \^JaJmH sH h\^JaJmH sH h \^JaJmH sH h h \^JaJmH sH h h \^JaJmH sH hi\^JaJmH sH PH & F^`gd7qcgd! & Fgd7qcgd gd& `gd  & F ^`gd7qcqxµ¨¨›|lZHZ;h!\^JaJmH sH "hXIh!56^JaJmH sH "hXIh 56^JaJmH sH h@h \^JaJmH sH "h@h 5\^JaJmH sH h \^JaJmH sH h \^JaJmH sH h\^JaJmH sH h4 \^JaJmH sH h h \^JaJmH sH h\^JaJmH sH h!h >*^JaJmH sH h h\^JaJmH sH GH()=>ruvwxƶƶ}m`SODhl2hl2mH sH hl2haH\^JaJmH sH h \^JaJmH sH hXIh \^JaJmH sH h{\^JaJmH sH h h \^JaJmH sH h!^JaJmH sH h h \^JaJmH sH h!hXI5^JaJmH sH "hXIh 56^JaJmH sH h \^JaJmH sH h!\^JaJmH sH hXI\^JaJmH sH ()=>wxgdAVgdl2gdaH & F ^`gd7qc & F^`gd7qcgd!gd *w"& CGܶ}mm]Pm]h*75\aJmH sH haHhaH6\aJmH sH h*7haH5\aJmH sH haHh 6\aJmH sH haHh \aJmH sH h \aJmH sH h*7h 5\aJmH sH h*7hX85\aJmH sH hX8\aJmH sH hC\aJmH sH haHhaH\aJmH sH hAV\aJmH sH haHhaHmH sH  =^_/0./STgdk$a$gdAVgdgd&gdqP & Fgd7qcgdaHG,612>KMNRZ[iq<=ͽwwwj`haHaJmH sH haHhaHaJmH sH hph \aJmH sH hph\aJmH sH hphHT\aJmH sH hph.\aJmH sH hph*7\aJmH sH hph*75\aJmH sH haH\aJmH sH haHhHT\aJmH sH h \aJmH sH haHhaH\aJmH sH !$3=By]_LfnsտկտտտՋ}o}dYNYNYhk\aJmH sH h->\aJmH sH haHhaHmH sH h haH\aJmH sH haHhaH\aJmH sH hLE\aJmH sH hh\aJmH sH h\aJmH sH hh5\aJmH sH hHT\aJmH sH hp\aJmH sH h\aJmH sH hgo\aJmH sH hgohaHmH sH hqPaJmH sH 6; )*>(-./&(0RSUenopȽȽȭȢȢȗӆxtih \aJmH sH h hG5>*\aJmH sH !h&hl5>*\aJmH sH hG\aJmH sH hp\aJmH sH h&hDH*\aJmH sH hY \aJmH sH hD\aJmH sH hl\aJmH sH h->\aJmH sH hk\aJmH sH hw4v\aJmH sH %TUopOHIJ7\ & Fgd7qcgdkw & Fgd7qc h^hgd& & Fgd7qcgdaHNOYHIJ opq5wlwllhY \aJmH sH hz\aJmH sH hz\aJmH sH hqP\aJmH sH haHhkw\aJmH sH haHhkw56aJmH sH hHT\aJmH sH hp\aJmH sH hphp\aJmH sH hphl\aJmH sH hG\aJmH sH hkw\aJmH sH *W!pqHbgdz & Fgd7qcgdaH & Fgd7qcArGH1`yޮޮ飘ujh\aJmH sH hphp\aJmH sH  *hpB*ph"""hp\aJmH sH h\aJmH sH h2N\aJmH sH h #\aJmH sH  *h B*ph"""h \aJmH sH h&hz5\aJmH sH hz\aJmH sH hz\aJmH sH hY \aJmH sH $78a(u & Fgd7qcgd. & FP^`Pgd.gd&gdgdaH & Fgd7qc!%&&)8(C89: @#XYZĶϦϦϛϛϛϛϛϛϛϛϛxh}#mH sH h\aJmH sH h&h7>*\aJmH sH haH\aJmH sH h&haH>*\aJmH sH haHh7\aJmH sH h7\aJmH sH haHhaH\aJmH sH !h&hu,5>*\aJmH sH !h&h2N5>*\aJmH sH /C9:= @i#rYZ & Fgd7qcgdaHZq]  9 :       ]   & Fgd7qc $a$gd&gd&gd&gdaH & Fgd7qc * 9 Q }     ( 8 9 : T U |         ˽yk`UUykh\\aJmH sH hHT\aJmH sH haHh}#\aJmH sH haH\aJmH sH h.h h \aJmH sH h}#\aJmH sH hD\aJmH sH h&haH>*\aJmH sH haHhaH\aJmH sH h.\aJmH sH h}#aJmH sH h5mH sH hDmH sH h}#mH sH h.mH sH       bGHI=>?wxy,-ʼʼʼʼղʼՋ{pbh.h.\aJmH sH h.\aJmH sH h.haH6\aJmH sH h.haH\aJmH sH h: \aJmH sH h&haH>*aJmH sH h: aJmH sH haHh}#\aJmH sH haH\aJmH sH haHhaH\aJmH sH h&haH>*\aJmH sH haHhaHaJmH sH &   bHI>?;xy gd& & Fgd7qcgdaH,-{|=>LM  ?$gdgd gd gd;} & F `gd.gd&gdaH  @Bz{|%'.<=>Mg   ⸮}u}m}ueu^ hhh.mH sH hfmH sH hmH sH hhmH sH hh h 5CJ\aJh;} hl2h}]h}]h haHhqP\aJh.h: \aJmH sH h.hf\aJmH sH h.h.\aJmH sH h.haH\aJmH sH h.haH6\aJmH sH !       I!F"O"?#=$>$d$n$% % %$%K%^%b%o%%&&;'D''''''''''''(糫竛琫xldh!mH sH hh6mH sH homH sH hDmH sH hKYmH sH h^hmH sH h<mH sH h}]mH sH h.mH sH h^mH sH hfmH sH h!56mH sH h56mH sH hh56mH sH hhmH sH h^h5>*mH sH '?$o%%'()j**,,,'.00#1g112<2$334 & F,8x^8`gdKY & F+8x^8`gdKYgd:gd & F2gdgd^gd((($(.(5(<((((( )))))***j*k*q*w*****r+v+ , , ,,,,,,,,,,,,,,-.. ...&.娠嘍Ղh<h<mH sH h<hmH sH h:mH sH hmH sH h^mH sH  jhhH*UmH sH homH sH hh6mH sH hKYmH sH hDmH sH hhmH sH h!mH sH h|ImH sH 3&.'.0000"1#1536344444446666\7]7A8B8D8X8b8j88888D;P;;<G<Q<R<S<ŽŬŬŽŬŬŬņŽ~p~ņŬjhg0J(UmH sH hgmH sH hdmH sH hKYmH sH h^hmH sH h^h^mH sH  jhhH*UmH sH h^mH sH hhmH sH h^h56>*mH sH h<hmH sH  *hoB*ph"""hohomH sH '4677 8D8X88999p::S;b;;;;;<S<z<@Agdg & F38x^8`gdKY & F18x^8`gdKYgdgd^ & F,8x^8`gdKYS<z<<<<<======>V>W>>>@?A?C?@@V@W@@@'A+A1ATAUAYAZA[AzA{AAAAADDFFbHcHII#J$J幱妞}hzmH sH jh7Y0J(UmH sH h7Yh7YmH sH h7YmH sH hzhzmH sH hmH sH hhmH sH  jhhH*UmH sH h|ImH sH hdmH sH hhmH sH hgh56>*mH sH 1AFK0KKLMaNOOOQZQQ0SVDYl[[b\]_`raxgdgd: & F-^`gdjgd7qcgd$J*mH sH hdmH sH hhmH sH :3Z9ZZZZZM[c[[[[[[[ \$\&\+\1\@\B\C\M\V\`\a\b\e\f\\\\\\\\\\\ϹϮϮĮĮϮϢ~ra jh|Ih:H*UmH sH h|Ih6mH sH h|IhrC5mH sH h|Ih5mH sH h|Ih$5mH sH h|IhT5mH sH h|IhTmH sH h|IhrCmH sH h|Ih$mH sH h|Ih:mH sH h|IhmH sH hmH sH hhmH sH h)PlmH sH &\L]q]|]]]]]]]]]^.^0^1^^^^^____"_v_x______}`````ʾʲ~ֲshhh|Ih)PlmH sH h|IhmH sH  jh|IhH*UmH sH h|Ih6mH sH h|Ih:mH sH h|Ih:5mH sH h|Ih5mH sH h|Ih$5mH sH h|Ihj5mH sH h|IhT5mH sH hhmH sH hmH sH h|IhmH sH $``@aGaLabaoaqarasaaaxbbccccccccddd d dddddddddd9eWeYe`eqezee¹ynyh)Pl\aJmH sH h hj\aJmH sH h h \aJmH sH  h \aJhThT\aJ hT\aJhThT5\aJhj5\aJhmH sH hmH sH h)PlmH sH hTmH sH h7qcmH sH hhmH sH h7qchmH sH *ra bbb7ccddddXeYeef=f$g%gHgIgdgijlgd gd gd;} 4 & Fgd gdTxgd & F(8x^8`gdKYeeeeeeef$g%gHgIgdghhiiijjl&mBmKmLmymzmmmmϼ|tmf]SLSLS h~h\aJh~hh~h\aJh~h5\aJ h h h|Ih h|Ih 5h mH sH  jhh H*UmH sH hh mH sH h7qch 56>*mH sH h 5\aJh hT5\aJh h \aJh hT\aJh h \aJmH sH h hj\aJmH sH h hj\aJlKmLmn nnnoo|pppqxq4rrruuvvvvlwgd~gdgd 4 & F5gd~hgd~hgd;}gd~hmmmmmmmmmn n-n.nAnBnUnVnnnnnnnnrrrrrrrrrrrrrr@sDsFs[s`sssssssss­ЦЭЭЭПЦjh]0J(U\aJh]h]\aJ h\aJ h]\aJ h ^\aJ h \aJjh~h0J(U\aJ h~h\aJ hU\aJ h7)\aJ hx9#\aJhx9#hx9#\aJh~hh~h\aJjh+0J(U\aJ2ssssstttt#t&t/t3t6t7t:tBtJtKtRtStctttt$u%u&u+u,u*B*CJUaJphU h7Yhw>*B*CJaJphUhwjhwUh7YhwCJaJ jh7YhwCJH*UaJhl h;}5CJ\aJh55CJ\aJhTh 5\aJ h7\aJh~hh\aJ h\aJ h \aJ jh|Ih0J(U\aJh|Ih\aJh|Ih \aJwwwwwxxxRxSxxxxxxxxx%y&y'y(y)y*yyyzyyyyyyy z zKzLzMzNzOzPztzuzzɸɸɸɸԩ| hZhw>*B*CJaJphUhZhwCJaJ jhZhwCJH*UaJh~hwCJaJhw jh7YhwCJH*UaJh7YhwCJaJ#jhw>*B*CJUaJphU h7Yhw>*B*CJaJphUjhwU*lwwx'yyMzzz{{|=}}~zu6ӄ1gdH[gdzm&gd6s&gd&gd~zzzzzzzzzzzzzzzz { {{{{{t{u{{{{{{{/|0|||||||||;}<}=}>}?}@}}}}}}}}}f~g~~~~~~~()ɴɴɴɴɴɴɴ!jhZhw0J(CJUaJ hZhw>*B*CJaJphUhwjhwU jhZhwCJH*UaJhZhwCJaJ#jhw>*B*CJUaJphU?)xyz{|}   eftuvwƵ|Ƶ|Ƶ|rgV jhZhwCJH*UaJh>KhwCJaJjhw0J(U"jhw0JCJU\^JaJhZhw0JCJ\^JaJhwjhwUhZhwCJaJ!jhZhw0J(CJUaJhZhwCJaJmH sH *jhw0JCJU\^JaJmH sH 'hZhw0JCJ\^JaJmH sH !wxށ߁456789LMԃՃŴŴšycVhZhwCJ^JaJ+jhw>*B*CJPJU^JaJphU(hZhw>*B*CJPJ^JaJphU%hZhwB*CJPJ^JaJph$jhZhwCJH*U^JaJ jhZhwCJH*UaJhZhwCJaJ#jhw>*B*CJUaJphU hZhw>*B*CJaJphUhwjhwU!qrф҄ӄԄՄք12./01234?@VWXYZ[\   hɼssss#jhw0JCJPJU^JaJ hZhw0JCJPJ^JaJ%hZhwB*CJPJ^JaJph$jhZhwCJH*U^JaJhZhwCJ^JaJ+jhw>*B*CJPJU^JaJphU(hZhw>*B*CJPJ^JaJphUjhwUhw-1YЈeȌ ҍ2^͐|Ցgd gdKYgdKY&gd7Ygd7YgdD&gdDgdDhiCD|}͈ΈψЈш҈ӈ{kjhw0JCJU^JaJhZhw0JCJ^JaJ%jhZhw0J(CJU^JaJhw$jhZhwCJH*U^JaJhZhwCJ^JaJ%hZhwB*CJPJ^JaJph#jhw0JCJPJU^JaJ hZhw0JCJPJ^JaJjhwU*efՉ։VWbcdefghŋƋннннthZhw0JCJaJhZhwCJaJ!jhZhw0J(CJUaJ$jhZhwCJH*U^JaJhZhwCJ^JaJ%hZhwB*CJPJ^JaJph#jhw0JCJPJU^JaJ hZhw0JCJPJ^JaJhwjhwU(vwŌƌnjȌɌʌˌ !"#[\ύЍҍӍԍՍӄueӄjhw0JCJU^JaJhZhw0JCJ^JaJhZhwCJ^JaJ#jhw0JCJPJU^JaJ hZhw0JCJPJ^JaJhwjhwU%hZhwB*CJPJ^JaJph$jhZhwCJH*U^JaJhZhwCJaJjhw0JCJUaJ'Ս12/012345ȵpȵ`ODhZhwCJaJ jhZhwCJH*UaJhwCJOJPJQJ^JaJhZhwCJPJ^JaJ#jhw0JCJPJU^JaJ hZhw0JCJPJ^JaJ%hZhwB*CJPJ^JaJph$jhZhwCJH*U^JaJhZhwCJ^JaJjhw0JCJU^JaJhZhw0JCJ^JaJjhwUhw*+[\^_`aʐː͐ΐϐА+,yz|}~ґӑԑՑ֑בؑ89νννٵr#jhw0JCJPJU^JaJ hZhw0JCJPJ^JaJhZhwCJ^JaJ$jhZhwCJH*U^JaJhwCJaJ jhZhwCJH*UaJhZhwCJaJjhw0JCJUaJhZhw0JCJaJjhwUhw&<=>?@AB[\^_abcdؕtĴxjxjxjxhUjhw0JCJUaJhZhw0JCJaJhZhwCJaJ!jhZhw0J(CJUaJh+hwCJaJhwCJaJjhw0JCJU^JaJhZhw0JCJ^JaJhwjhwUhZhwCJ^JaJ%jhZhw0J(CJU^JaJ(?a:t;t=t>t@tAtCtDtFtGtYtbtctuttttttgd!H$a$gdu gd&gd i&gd&gd]&gd+ex.php?option=com_oe&task=viewDocumentRecord&docID=9991     IOC/IODE-XXIV/6.1 Page (i) IOC/IODE-XXIV/6.1 Page (ii) IOC/IODE-XXIV/6.1 Page  PAGE 30 IOC/IODE-XXIV/6.1 Page  PAGE 29 IOC/IODE-XXIV/6.1 Page  PAGE 1 t7t8t:t;tt?tAtBtDtEtGtYtatbtct{ttttttttttxqj_TEjh&hwU^JaJh&hw^JaJh!Hhw^JaJ h!Hhw h&hwh hwmH sH h hw0JmH sH h hwCJaJmH sH hwhvxhwmH sH $hvxhwOJQJ^JaJmH sH hvxhwaJmH sH jhmUhmhZhwCJaJjhw0JCJUaJhZhw0JCJaJtttttttttttttgd;}$a$gd&$a$gd $a$gdu $a$gd&gd i ttttttttttttttttttttttttttttʻ{mhl h;}5CJ\aJhmh hwmH sH h%[CJaJmHnHsH u%jh%0hwCJUaJmH sH h%0hwCJaJmH sH h hwCJaJmH sH hwh!Hhw^JaJh%[^JaJmHnHujh&hwU^JaJh&hw^JaJ1 0:pu |. A!"#$% > 00P:p&|. A!"#$% Dpn@:ǛQe_%+VOPNG  IHDR!sRGB pHYs!!@IDATx VSǷ)LDL1(̠bhȸˌ`Fĸ_Ҍ1!ƛur˥P E)הsiwe?yyv>+X!sssL*o999Oρp w99&ass ?<<*/L*F߉&~xxT^T/L0}'^999PxaR6NϟoOnsJq Dl`cnVr 79sy̻kqW_=ز8I˺e]N;d~_vaM6e7/#5Z/gffO0 H+;q}73׿g}!Փ^ԓ;)S~ѣGp_I9܌W,KK)+ہor8;#FQGeڴќs;`yq ^ulYtyomz-|'W_5K,q^.]vi̺뮫se&i~3/Sp<}7[lԩYmO-^{JVߏ>lf4H1cmx ϚYfv㎦[nۦuYttXYi  XЇ>4|M5Nj]wlfw2ve\3؞'L] ?i.\щ=l'@3x&ʾYga 3s5#G4ԬƓO>iƌcy5Y 4={4w֨?Qu7}$:Ck׮Dm$j} 7`le`KԼ?N{m/R;v͝-%_wܑ~3+>@{&lbW]uUtMVL_?xfGbZ aZQKkEkFA g~_RoE̡fǧR/hΜ9vv+;-|nN$裏qΝ;2}{؇~4J^-^wu2 l nVHXp}GN_{zٮI&KJžqVvm\sS# ;r\-Q\Lx 裏Ꟙ2W^Ox jICsݻ-i{\z8oر.3۷7կkg1#4sW_mgV1ͪs]Dk'eeĦZp& L_4 -O?~6LD}qNV Yj~2,M1>,ju9l#yrk[+cy5{a^ך2a,ZH+ŠG[ŤDB?k믿_SPpSz)r-E0|3\rAV 坫9|@ _iS3yIK\baa%Wа)\&Dʦ0aIO3@QzM0lG0g pbDAdF|%f7LM˴AeYXMN-掾'yӦM3\}ݧpl[+}Kqm`~7?OfCMUE VJbƛ-ܲW]aB"!2sa"N =[gIMLk;E<3/yT+Xtq˿!5>y4C8mF*Qag -\̞5ۈWH"U=h/LųPG|*״꿓O:~O;_Z⯊-.>Isk+ ,|EUJiymiH 4џ<\ї+Uo/I\$EҚ|ϳ~:O1΋s/QMĨ\KlFP<0rp;R,if]F w^13 IIbNee8b h6xUضDeN?t\Pz`hor ׇklGh/VnEؙR*8*0z9/\%ܖt7&p8itʇ_qyM%ߌ25_g%Z&dٺ VÕEJƍsڢBWX&U Z+30j(+|unv'BDKbcQC؝ mYB8@N۪Ot ㏷[ECF1[+2 7ï$N^-@pv#WQ<`>i &ed"8C,:xUP1k)L7ٳgEp ϳ4/cB"WD hITS +(n:ٳx?}JH|mEhChBD|JmTuV{2CRܞsGyD[Y0a+2F:ĄyXZnyڗf`)x=e, sH( RJj/')& &&<,<:{81͹Ͽ{ TAr0hKB-qķ߄ai`z+$Ah#P LT1㚠En.{.Vbm=%nK87ځLҚ\*o]Ah osVFy}aەۚ9o14{ D끰w/Ez sE;~{1a?Pv|zP#0ivcis݃ j8m)o(H2&8SY-AL@'+) :<((o(@'&aO~řd8"眴#ӗ8Bhל"Rqrt8R=yݸ5f\X48D Bk1>"&N;QLиOIRR&(քX4dCR0aՐИN:@H9&"[nn|G8מWn !j9yώiqzmH<q LB>+;@al8 $e4?I?0^D;2{ (E7ZjChx(]-ǒ\Rtۈ9/M* p)1tSc[󓄪&L<1bvCC6cuBrI$~)e{?7EHцܙb^V##$B8QYĦCtbp&BVlMܣ9|Z5f'(5)m5Xz%5YTdZ]-w_#uaNR/L0s$ 79陧1R9O+?*uhoM*eUa!SfΘYP`+^|H!'#R  qz3ɾ^C FM9gU첋 U{"'nѲyX_5wL;qQٯeB3o¤JpGd; #l1qbɮ " Dmmw4 @Ι&NN4_ ,wQ;VR E|Z4| '9?HzgV[m\XRރoB a|BP/& &='m[|3,&S7@09|pDCH} @;RU?91gi+1H"k,V,ZӦM+tXus&^!Hx ם9~uS4΋,>E.2,@7JC`(q!DpRHLfD*V1߁-Oݻwb՜}M.d` :̒'0!g̜@Ze{Х$"*HK-;Duv/ LJ4,V`"M2En@'ABN4͍P[oeVYyB iѴ&N䤓N餼$d-}(L [s1Maq#ڠp%? 㮫Ak%"M.䒜~gOluU/,+2("t9@mRXxPL9_sol8ܢ tj| A Ivp1U56l0)Vp<,G AJ+5 A!X.A0)6KѴ@G$g%hJPફR-L Șh7b]д{ &>BauVokV5/ %1SZ1JPSafA@=ɽصjyЬjSUhUn`B@=aJ#=oW$ e <'jЂ!~᪕p{WMLR8h NUgjS7qB X -.YA:EhA8 Q @Vbu)ɨ́ZdIc'f9a޶ǶԁS{ 0 q<o'm~; .`]wӍѮ008FMxUJ%*Hǯ!uosK\lMUB五J9XCkbA &𚛃#GԐ+zZ:0al#|):P~{X ]S % 1 1!=N-&c KgG?w#m޳zaI-[M AK.EI03y3e%T_O"1ٳ̥.Ua\1Ivgh],M@3W̭J3Ѧ~ F΅Bl>.N{jw&0ULB迯,0;ZT]?IxXe*PNhA,D:pbJ^6[,RHr(UظlwFp6R1+Mm\ Vw:ɄG@ (#򀨞! T +`D,[9@Hz,0@chʃL@Hf5 Uf<.B|oA_ hBQaW{8E j7hc.-% Z 2⨶KLhB[?0j;xқ"H} X5e(8yD$"ʃط_Fըs0\B5W_SV +4;ZOy3D(Ӈ{fB|L1DŽ_-- `-,k1q^D .}2Ĥ ²C>JK2&L6hCP) !DİOO\p1Y8apl :9Lcj!‚AagFyN;' VM8--x mE_i.э[/^sg$hï=T &3g4_#8Vmj6hXYTUF7<|`2xX0n;mVjfvuCx!T#DZ`]cp"řܻwo褯$ Hd v ҇>, ?p"as <7heCq!a׾'͵ye0rPt` P;TS\m\ŎJlݦ!ߦ> Dy<8Xyxs0o$,mA2?"|+>l+Hߊي R?\h2V/Z [VS^b~1)eϘ.a9s1E*U*ă%^c+S++D.4ईp>Q);AƎWjRX IZ,ɢdZ i;&xH܏$)zIɕzzn W&|11wV!)xβ<@htA$$Y17 o-hVL+gNүk_5JqI}+8D:ǃ lSмzl^o?0%}FR wFQ9uUd$U+ڈlhgY !q6 {1=>^) u&e\lr$K3ScHeR=7?GIh׊1:묳M-ASbנzߣQ7pFMЮc U轄mY@BNNj/xF쾘7jNObQr&:Ŧ/D84IOkCƄLZ'><&oϥ/ܖϴO?7$Ş:z4U_NB2e*`bDU5|( b"h -pK2P*lET.V"{ly1qDpQ/rKI$:J"I9݆4AR{n[n_\78C h*@4oOE "]wZys&Y L&\  W6I ܘeR=.~򓓭8-fATÉ`kI[mJW=o]R J[b?POӐT";jz*Zh%{[پJ:f`HF &P';;ﴘdZAϪ]Ϥ\a(y:uT+D I)w ^qCH Y+ Ky-[ }1V]SKalS^רkcQλX郍G"j+aF9|)h4G zJCʌC-NOa"r@[ 0- 48dY ϒa%L$hSlں뮫]a:pjq}j-wiR3Bb<{ф ,nd"@֑wu@$\LprsޘWZP F!H-"וh! cZ-@nع@ ƽMMR4KOmy[1/T)y$ b9rXi@4LG; eЩY/L7/<:tbg#ę'z6D  'e)Qp>.s0(s-3U2u])iɧ$5Y$m3)ETY;͸q~}G Iz)Cq _n ]o]q)=hVQBj3~DDu„ s@¦Z&#AqW6*@ Fj*Sm$=6$Q IQ v.r%ڈOxh&I xꎄ.7&r0݊8x]O=iW]G ˦ w9^Zڬ--䯄1\,fqp|𛆍 H3Ÿg QYD6C\hȍH]搒ù$7RE$9ɇYŊj/L#H[0aua|vagB *J$#z5;|ޯjD O2-b$*5b2pBa0P=wcb;,D8%߿!yB+{uo(E $DT!#Ɉ/e&)rZ0ÏwNG2aZDž~J6Ҧd s ?kRpm1N HLRDES&uGhNP/,-FJio(^<E-NX-ii:V."Ak<a<52R,*|zV47Gl[̳%DgF,޷is=!㈴ԂF^tE9̓ t'j@=b"X)dćj2Dh$j$^ :ҙkF0&tƝ$p.a?&J-kD o4?S)3'<hI㴭5Eُ·oMv9iI383#Na1Q,!oVuR1)N&8' D>_2t'CAsD+_1_t4zhsAU5w$x9М9 毀 Y~eW|0`<9h߾# lGD)K19BQ#?Ϳ(- Y牒 "/LyTqZ"BޣQ.Cgg) X!ZT2_^|¤Ln.*Óւ@.܈${`"8ѽ{wL* `fsw @8bGGV/.7H,[50`h<:cƛlr^_c9̓%L#U#8TT[x'LUvӅMηj@>,bnop?,TN"N {lssەJ)F#Eڟd&\vYM0)}-qfw_2ԝ|3{l#E (X6o`c86R~@MꙠ!$!ZL }i7Kuy$ lE*@V )?Tr ׂΟ~f;!FRU r;vT6C1^8RO&60I(9ց6L̤5|L?{aŻ9B,GӤpp~H&ٹW~&=~p&ٹW~&=~p&ٹWgh'T ¤ ;uϏVhGjT"W?DAN!IJ!/Ljfsjw_nԅvI11cV<~ R0B8Pc~5-Pl#a<4iVZWH#dݼ*v[aͨ쵬`Ƀ.lPҶlCz[7cѪ V?$&=j$!jPQMpL"R/@%j`: T93lcq sر_؄N:˖K CZI-ρ4sfEi&"Htq쳏7n]Qh/bw='$kɗK"Y!~O'ؿ0VLFK-Xv]SDnyKρf́8a1rȜ`MF?K\bӺ=x"&9?۹3&SV߼0 I΁8a~=ńf7. fAnS! c{q&rl^bh{ٓX7ǎb'TZ%d^98MuQSNcWv $먡!kavtt 'Rg09~myyL)y DviV=nuAG >Xw ,&Yku3ɲ{߽0j~ڏ?XwlTa-6i4V?<י#/L2w7`l~`.5"yaŻV1^P߾Niۯްi8DdGkP\k>̜93{1M Q`k{Cs!a{fs)A ࿊=Z@kV,~mR `➔$@DN҆ V"Gc)-0)av7x}dԒ\@a{[p㏷b3yiӦxs1y >EK!&7jԨ<" if'M괩*>`_BL{ԚI cⁿ"  n66ڵ}'b/ MJK 3;s )pa~a3dȐ\xt)h#F ']v}]5ؿTˁhwX,0&_iw?ѣԱ bhAiQ=h(Z<ݻ|d&~ͳS5/fm׮Vv馛53sXhrɗq_!dC @xJQW+ρr8I9kmTaxs 0G  w0Balloon Text CharCJOJQJaJmH sH tH 8@"8 Rp<Header!Fo1F Rp< Header CharCJ^JaJmH sH tH 8 @B8 Rp<Footer!FoQF Rp< Footer CharCJ^JaJmH sH tH .)@a. Rp< Page NumberfOrf f<Table Contents $*$1$ CJOJPJQJ^JaJmH sH 6U`6 l Hyperlink >*B*phB'`B Comment ReferenceCJaJ`o`  Heading 2 Char,56CJOJPJQJ\]aJmH sH tH ZoZ  Heading 3 Char&5CJOJPJQJ\aJmH sH tH RoR  Heading 4 Char5CJPJ\aJmH sH tH XoX  Heading 5 Char$56CJPJ\]aJmH sH tH RoR  Heading 6 Char5CJPJ\aJmH sH tH LoL  Heading 7 CharCJPJaJmH sH tH RoR  Heading 8 Char6CJPJ]aJmH sH tH ToT Heading 9 Char CJOJPJQJaJmH sH tH 8@"8 # Comment Text"CJNo1N "Comment Text CharCJOJQJ^JaJHj@!"H %Comment Subject$5CJ\aJZoQZ $Comment Subject Char5CJOJQJ\^JaJ:@b: '>K Footnote Text&CJPoqP &>KFootnote Text CharCJOJQJ^JaJ@&`@ >KFootnote ReferenceH*FV`F 1RFollowedHyperlink >*B* ph6`6 Sh_pTOC 1* 2# x.`. ipTOC 2 +^.`. ipTOC 3 ,^. . iTOC 4 -^. . iTOC 5 .p^p. . iTOC 6 /L^L. . iTOC 7 0(^(. . iTOC 8 1^. . iTOC 9 2^P`2PL0Revision3$CJOJQJ^J_HaJmH sH tH @@B@ < List Paragraph 4^m$PK!pO[Content_Types].xmlj0Eжr(΢]yl#!MB;.n̨̽\A1&ҫ QWKvUbOX#&1`RT9<l#$>r `С-;c=1g|/+Q{J Fs1}W`5P{6^忁WܿWAw04+Po۵k($=AV3X=»7n7 ̆rv.,Z^l Hfq(9ˈsBXnF);MGYx}tI5,Q~_so;s?i-A:w[~t$;%08>nf1-iQd/#~BYp{؀G˗I-x|'1:`5 e_Z4w-uS.l}(5C@<9FVg:o%GwsԀJ {>%i3 绒mk#7~F+xK9`ٌ|KgivҼo=߽ o4Yn ~'{wsBD(>jΡ(E ?J \!edL|CD<6uW:x:΂q84foCg.xp$65lѭ UWl#u]7!ufhZH׍2Hx AP#] tN VfFlz  Qծi6L*2p1;euh4MJ z2E,4X6` 4Օem5}2!Z9g"meq1D<D'W9$=WLM(n'K 򩑃I9vEF:ϵV,-=g]fOL1]_xy4g>JB[]Cy;EhOŘ!ZHBxըe9쭺WiȪiW1u؊튼jb(zϥ{[rk'U^RuQ4j j K.ZڱԮS$4onŭVg-4Jiu{_0 CTA`C4Q{\6`Ҁ_2#=u{A*?xMVfȯ׆(,"N~~s2OMtUܟ;d5^Ȓ*Sw$UE\ݡn5fwЪtq:nT=q k:V=*^&V^)3\G@PK! ѐ'theme/theme/_rels/themeManager.xml.relsM 0wooӺ&݈Э5 6?$Q ,.aic21h:qm@RN;d`o7gK(M&$R(.1r'JЊT8V"AȻHu}|$b{P8g/]QAsم(#L[PK-!pO[Content_Types].xmlPK-!֧6 -_rels/.relsPK-!kytheme/theme/themeManager.xmlPK-!u.Ztheme/theme/theme1.xmlPK-! ѐ' theme/theme/_rels/themeManager.xml.relsPK]  "DY \8p>(fquyx6)ݮ"$)*+D--./24556477w8;>@BKLMNSU^gdeEjgjYmf  !"#$%&'()*+,-./01234567$Lr3b- [   V~-6<EWd7:uf|3| (GGGJJp D fRL*H,0;?J_Wk?v Ӛآ ۹8[O}yGG  (&.S<$J3Z\`ems(vwz)whՍttt   !"#$&()*+-./0234567;=y (02m4577AKW=b#mv\TZ ?$4Arallw1tt   %',18< I e g / K M x -IKw e#?A}9< #Lhk0LOx #rWsvRnqs3Yqf %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%Xahk!!!Q"&w JN1pt15T`dM + /  Y ]  q  VSXd{*/!h38{5:> CGVTY OP]af54:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXt ,b$:ǛQe_%+VO@s|@H 0( @ۣ< l ( edl    A? 2 "en-small-bwPicture 2Description: en-small-bw"B S  ??f 6t@= _Toc467256361 _Toc345671113 _Toc345671114 _Toc467849244 _Toc467849245 _Toc467849246 _Toc467849247 _Toc467849248 _Toc467849249 _Toc467849250 _Toc345671115 _Toc345671116 _Toc345671117 _Toc345671118 _Toc345671119 _Toc345671120 _Toc345671121 _Toc345671122 _Toc345671123 _Toc345671124 _Toc345671125 _Toc345671126 _Toc467849263 _Toc345671127 _Toc345671128 _Toc345671129 _Toc345671130 _Toc345671131 _Toc467256379 _Toc345671132 _Toc345671133 _Toc467256380 _Toc467256381 _Toc467256384 _Toc467256382 _Toc467256383 _Toc467256385 _Toc467256386 _Toc467256387 _Toc467256388 _vft20hbz4d1s _Toc467256389 _Toc467256390 _Toc345671134 _Toc467256392 _Toc345671135 _Toc467256393 _Toc345671136 _Toc467256394 _Toc345671137 _2fcrs2bgex5a _Toc467256397 _Toc345671138 _Toc467256398 _Toc467256399 _Toc467256400 _Toc345671139 _Toc345671140 _sorfts9x7r3b _Toc345671141 _Toc345671142zu-"]5]5]5]5]5]5]5]55MO=e5mNo~p qrwz{{#=-GG SʿOa||TTLL`  R]cg  !"#$%&'()*+,-./0124356789:;<"]5]5]5]5]5]5]555M1OWeImqop7qsw{{N{<OFggQk%;\8{  R]cg?@MS  :DFKLU]bp{|  /89@ISUZ[dfqrx"## #99;;==EE/H6HII!L+LLLdOmOSSZZpZzZU^_^_ ___aaXbbbff*h3hhhhhElPlBnCnqqDrMrrrrrssss!ž)3 ʣӣls«ë4:>*D*P,W,\.c.55;9<9::;;>>>?@&@@@A$AAAGAnAtAAAQQW^^^^^v_}___ccd d}kklltmdg?@llKtmdg:::5vlZ>i5bVbjS 077 : 0 Ti# p5 Z,B;W" =N~RuY(;Fn8Z^`X['BF\ֲ]R]@%<G_ԈP.e*%8^`8>*%p^p`>*%@  ^@ ` >*% ^` >*%x^`x>*%H^`H>*%^`>*%P^P`>*%h^`h.8^`8.^`.p ^p` .@  ^@ ` .,^`,.H^`H.^`.^`.h^`h.8^`8.p^p`.@  ^@ ` . ^` .,^`,.H^`H.^`.P^P`.^`OJPJQJ^Jo(-h^`hOJPJQJ^J%8^`8OJPJQJ^Jop^p`OJPJQJ^J%@  ^@ ` OJPJQJ^J% ^` OJPJQJ^Jox^`xOJPJQJ^J%H^`HOJPJQJ^J%^`OJPJQJ^JoP^P`OJPJQJ^J%^`OJPJQJ^Jo(- ^`OJ QJ o(o p^p`OJ QJ o( @ ^@ `OJQJo( ^`OJ QJ o(o ^`OJ QJ o( ^`OJQJo( ^`OJ QJ o(o P^P`OJ QJ o(^`OJPJQJ^Jo(- h^`hOJQJo(8^`8OJPJQJ^Jop^p`OJPJQJ^J%@  ^@ ` OJPJQJ^J% ^` OJPJQJ^Jox^`xOJPJQJ^J%H^`HOJPJQJ^J%^`OJPJQJ^JoP^P`OJPJQJ^J%h^`hOJPJQJ^J%8^`8OJPJQJ^Jop^p`OJPJQJ^J%@  ^@ ` OJPJQJ^J% ^` OJPJQJ^Jox^`xOJPJQJ^J%H^`HOJPJQJ^J%^`OJPJQJ^JoP^P`OJPJQJ^J% ^`OJQJo(h^`h.8^`8.p^p`.@  ^@ ` . ^` .,^`,.H^`H.^`.P^P`.h^`hOJPJQJ^J%8^`8OJPJQJ^Jop^p`OJPJQJ^J%@  ^@ ` OJPJQJ^J% ^` OJPJQJ^Jox^`xOJPJQJ^J%H^`HOJPJQJ^J%^`OJPJQJ^JoP^P`OJPJQJ^J%80^8`0o(()^`.pL^p`L.@ ^@ `.^`.L^`L.^`.^`.PL^P`L.h^`hOJPJQJ^J.8^`8.p^p`.@  ^@ ` . ^` .,^`,.H^`H.^`.P^P`.h^`hOJPJQJ^J%8^`8OJPJQJ^Jo^`OJPJQJ^J%p ^p` OJPJQJ^J%@  ^@ ` OJPJQJ^Jox^`xOJPJQJ^J%H^`HOJPJQJ^J%^`OJPJQJ^Jo^`OJPJQJ^J%h^`hOJPJQJ^J%8^`8OJPJQJ^Jop^p`OJPJQJ^J%@  ^@ ` OJPJQJ^J% ^` OJPJQJ^Jox^`xOJPJQJ^J%H^`HOJPJQJ^J%^`OJPJQJ^JoP^P`OJPJQJ^J%h^`hOJPJQJ^J%8^`8OJPJQJ^Jop^p`OJPJQJ^J%@  ^@ ` OJPJQJ^J% ^` OJPJQJ^Jox^`xOJPJQJ^J%H^`HOJPJQJ^J%^`OJPJQJ^JoP^P`OJPJQJ^J%h^`hOJPJQJ^J%8^`8OJPJQJ^Jop^p`OJPJQJ^J%@  ^@ ` OJPJQJ^J% ^` OJPJQJ^Jox^`xOJPJQJ^J%H^`HOJPJQJ^J%^`OJPJQJ^JoP^P`OJPJQJ^J%h^`h.8^`8.^`.p ^p` .@  ^@ ` .,^`,.H^`H.^`.^`.h^`hOJPJQJ^J%8^`8OJPJQJ^Jop^p`OJPJQJ^J%@  ^@ ` OJPJQJ^J% ^` OJPJQJ^Jox^`xOJPJQJ^J%H^`HOJPJQJ^J%^`OJPJQJ^JoP^P`OJPJQJ^J%^`.p^p`.@ L^@ `L.^`.^`.L^`L.^`.P^P`. L^ `L. h^`hOJQJo(8^`8OJPJQJ^Jop^p`OJPJQJ^J%@  ^@ ` OJPJQJ^J% ^` OJPJQJ^Jox^`xOJPJQJ^J%H^`HOJPJQJ^J%^`OJPJQJ^JoP^P`OJPJQJ^J% ^`OJQJo( ^`OJQJo(p^p`OJ QJ ^J o(o @ ^@ `OJ QJ o( ^`OJQJo(^`OJ QJ ^J o(o ^`OJ QJ o( ^`OJQJo(P^P`OJ QJ ^J o(o  ^ `OJ QJ o(8^8`OJPJQJ^Jo(- ^`OJ QJ o(o  ^ `OJ QJ o(  ^ `OJQJo( x^x`OJ QJ o(o H^H`OJ QJ o( ^`OJQJo( ^`OJ QJ o(o ^`OJ QJ o(^`OJPJQJ^Jo(- ^`OJ QJ o(o p^p`OJ QJ o( @ ^@ `OJQJo( ^`OJ QJ o(o ^`OJ QJ o( ^`OJQJo( ^`OJ QJ o(o P^P`OJ QJ o(h^`h.8^`8.p^p`.@  ^@ ` . ^` .,^`,.H^`H.^`.P^P`.0^`0o(()8^8`.L^`L. ^ `. ^ `.xL^x`L.H^H`.^`.L^`L. ^`OJQJo( ^`OJQJo( p^p`OJ QJ o( @ ^@ `OJQJo(^`OJ QJ ^J o(o ^`OJ QJ o( ^`OJQJo(^`OJ QJ ^J o(o P^P`OJ QJ o( h^`hOJQJo(8^`8OJPJQJ^Jop^p`OJPJQJ^J%@  ^@ ` OJPJQJ^J% ^` OJPJQJ^Jox^`xOJPJQJ^J%H^`HOJPJQJ^J%^`OJPJQJ^JoP^P`OJPJQJ^J% h^`hOJQJo(8^`8OJPJQJ^Jop^p`OJPJQJ^J%@  ^@ ` OJPJQJ^J% ^` OJPJQJ^Jox^`xOJPJQJ^J%H^`HOJPJQJ^J%^`OJPJQJ^JoP^P`OJPJQJ^J%P^`Po(.@^@`o(.0^`0o(sH ..`^``o(... ^`o( .... ^`o( ..... ^`o( ...... `^``o(....... 0^0`o(........h^`hOJPJQJ^J%8^`8OJPJQJ^Jop^p`OJPJQJ^J%@  ^@ ` OJPJQJ^J% ^` OJPJQJ^Jox^`xOJPJQJ^J%H^`HOJPJQJ^J%^`OJPJQJ^JoP^P`OJPJQJ^J%h^`h>*%8^`8>*%p^p`>*%@  ^@ ` >*% ^` >*%x^`x>*%H^`H>*%^`>*%P^P`>*%h^`hOJPJQJ^J%8^`8OJPJQJ^Jop^p`OJPJQJ^J%@  ^@ ` OJPJQJ^J% ^` OJPJQJ^Jox^`xOJPJQJ^J%H^`HOJPJQJ^J%^`OJPJQJ^JoP^P`OJPJQJ^J%h^`h.8^`8.p^p`.@  ^@ ` . ^` .,^`,.H^`H.^`.P^P`.8h^8`hOJ QJ ^J o(o8^`8OJ QJ ^J o(o ^ `OJPJQJ^J%  ^ ` OJPJQJ^J%x ^x` OJPJQJ^JoHx^H`xOJPJQJ^J%H^`HOJPJQJ^J%^`OJPJQJ^Jo^`OJPJQJ^J%^`OJPJQJ^Jo(- ^`OJ QJ o(o p^p`OJ QJ o( @ ^@ `OJQJo( ^`OJ QJ o(o ^`OJ QJ o( ^`OJQJo( ^`OJ QJ o(o P^P`OJ QJ o(^`o(. ^`OJ QJ o(o p^p`OJ QJ o( @ ^@ `OJQJo( ^`OJ QJ o(o ^`OJ QJ o( ^`OJQJo( ^`OJ QJ o(o P^P`OJ QJ o(8^8`OJPJQJ^Jo(- ^`OJ QJ o(o  ^ `OJ QJ o(  ^ `OJQJo( x^x`OJ QJ o(o H^H`OJ QJ o( ^`OJQJo( ^`OJ QJ o(o ^`OJ QJ o( h^`hOJQJo(8^`8OJ QJ ^J o(op^p`OJPJQJ^J%@  ^@ ` OJPJQJ^J% ^` OJPJQJ^Jox^`xOJPJQJ^J%H^`HOJPJQJ^J%^`OJPJQJ^JoP^P`OJPJQJ^J%,^`,o(() ^`OJ QJ o(o p^p`OJ QJ o( @ ^@ `OJQJo( ^`OJ QJ o(o ^`OJ QJ o( ^`OJQJo( ^`OJ QJ o(o P^P`OJ QJ o(h^`hOJPJQJ^J%8^`8OJPJQJ^Jop^p`OJPJQJ^J%@  ^@ ` OJPJQJ^J% ^` OJPJQJ^Jox^`xOJPJQJ^J%H^`HOJPJQJ^J%^`OJPJQJ^JoP^P`OJPJQJ^J%hh^h`h>*OJQJo(88^8`8>*%^`>*%  ^ ` >*%  ^ ` >*%xx^x`x>*%HH^H`H>*%^`>*%^`>*%^`OJPJQJ^Jo(- ^`OJ QJ o(o p^p`OJ QJ o( @ ^@ `OJQJo( ^`OJ QJ o(o ^`OJ QJ o( ^`OJQJo( ^`OJ QJ o(o P^P`OJ QJ o(^`OJPJQJ^Jo(-80^8`0o(()^`.pL^p`L.@ ^@ `.^`.L^`L.^`.^`.PL^P`L. ^`OJQJo(p^p`OJ QJ ^J o(o @ ^@ `OJ QJ o( ^`OJQJo(^`OJ QJ ^J o(o ^`OJ QJ o( ^`OJQJo(P^P`OJ QJ ^J o(o  ^ `OJ QJ o(^`o(.^`o(. p^p`OJ QJ o( @ ^@ `OJQJo( ^`OJ QJ o(o ^`OJ QJ o( ^`OJQJo( ^`OJ QJ o(o P^P`OJ QJ o( ^`OJQJo( ^`OJQJo( p^p`OJ QJ o( @ ^@ `OJQJo(^`OJ QJ ^J o(o ^`OJ QJ o( ^`OJQJo(^`OJ QJ ^J o(o P^P`OJ QJ o(5S@a: S 5GNqg,l*\f1uV)3u.yF\-{y:34+S*/=i5U2+gv .]R]@O}m$4:*"z# 77 _n6P.eG_5 avNFWH{5uY;Wacp< 'jS "@  %: 0 R zJ+X[Fn8Z55e         HbHb        Hb \                           Hb        Hb        \S                 Hb                 Hb                Hb        Hb?                                   NRJ>.P-_ |LM4EpEG`=s2-_ dd$9.P4E(rRbz;pZ$9<?~`rfk|`cCnu;pZbzRJ$Nm-`p$9Jy : E} XHaHR(-,H[ goI{fZ5?~9sT/!Px F Y -"Hr" #x9#% %yd%vw%{%G!("*Rx*z*[+n+.n~.x//,[/}r1l2@,@K@ZoAq_BrC1ZDLEdFILH|qHXIlIyJ64K>KUKM>LLMz NO# P:PpqPqP>QR1RW7SPS~SHT$UyUAV VW_X7YKY5MY|YZ ^)_Sh_yab8b:3b7qcd~zd8f& g~h iBi)Plzm&4oq{rWs('s6seu%v;*vw4v wOwkwgzw,xSyCzZfz\ |V}e}}}~/R~"2j#qr+!)|IJTM7e47l &gNlX8[u,4 zV .!H&T\^Yy^~+sM#bkdz3k!K:hl,lc U1G@lJ{:d!6Q Pw]'*C2NLsZ F}#Wku  Tl{^]i<.a5 sfr(rC: Jp+Azz667Z`gZMn@py,ci;s;}$_pnwFa73#D%[$?.D{}]7mo_dr6U Nl 7ZTZ.eadi"Hp{=}]7)A<ovxz ^[8eX8ixXtmvm@ttj#}tt4IJqf@R@@Unknown G*Ax Times New Roman5Symbol3 *Cx Arial7@ Calibri;Yu Mincho7@Cambria;  jMS GothicO5  jMS MinchoYu GothicC  PLucida Grande? *Cx Courier New;WingdingsA$BCambria Math!1h%SQG%SQGLg66"66"0llB#H?'-"23! xx{w Provisional Agenda IODE-XXI Hernan Garcia;Peter PissierssensPeter Pissierssens5                           ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4  Oh+'0  8 D P \hpx'Provisional Agenda IODE-XXI$Hernan Garcia;Peter Pissierssens Normal.dotmPeter Pissierssens2Microsoft Macintosh Word@F#@a@5k@5k"66 ՜.+,0  hp  ' UNESCO/IOCl Provisional Agenda IODE-XXI Title  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^`abcdefghiklmnopqrstuvwxyz{|}~Root Entry F ª5k@Data _1TablejWordDocument -SummaryInformation(DocumentSummaryInformation8MsoDataStore5k咪5k2BM5TN3CNPA==25k5kItem  PropertiesUCompObj `  F Microsoft Word 97-2004 DocumentNB6WWord.Document.8