ࡱ> #` 0gbjbj5G5G W-W-B[c     4J CCChZDD|J >E(E^ F F FqSqSqS$h(~Æ WS^qSWWÆ F F ؆*\\\Wp F F\W\\nف  e FzE PVCY <>dZ@e e|qST\[UUqSqSqSÆÆZ\dqSqSqS>WWWWJ J J %N/J J J N/J J J  Restricted distribution IOC-WMO-UNEP-ICSU/GSSC-X/5.5.1 Agenda Item: 5.5 Paris, February 2007 English only INTERGOVERNMENTAL OCEANOGRAPHIC COMMISSION (of UNESCO)WORLD METEOROLOGICAL ORGANIZATIONUNITED NATIONS ENVIRONMENT PROGRAMMEINTERNATIONAL COUNCIL FOR SCIENCE Tenth Session of the Global Ocean Observing System Scientific Steering Committee (GSSC-X) Seoul, Korea, 13 16 March 2007 COOPERATION WITH IODE (submitted by the Secretariat) Summary and Purpose of Document This contains a discussion document submitted to the nineteenth Session of the IOC Committee on International Oceanographic Data and Information Exchange (IODE-XIX, 12-16 March 2007), reviewing the current status of IODE organization and its cooperation with GOOS. The document then proposes ways to improve the efficiency in organizing sessions, and enhance cooperation among GOOS, IODE and JCOMM. Actions Proposed The Committee is invited to review the document with a view to how the GSSC and overall GOOS Community would improve organization of their sessions, accordingly, seek ways to strengthen collaboration with IODE, as the data management component of GOOS The Committee is also invited to provide feedback to IODE, and further to advise I-GOOS VIII on plan and actions to enhance GOOS-IODE cooperation, including joint GSSC/IODE technical working groups proposed model for the organization of a joint IODE/I-GOOS Session in 2009 The Committee is finally invited to consider a proposal on joint GSSC/IODE/JCOMM officers meetings in 2008, as described in the document. ______________ Annex: 1 Limited distribution IOC/IODE-XIX/49 20 February 2007 Original: English INTERGOVERNMENTAL OCEANOGRAPHIC COMMISSION (of UNESCO) Nineteenth Session of the IOC Committee on International Oceanographic Data and Information Exchange (IODE-XIX) Trieste, Italy, 12-16 March 2007 Options for the organization of future Sessions of the IODE Committee (by Peter Pissierssens) 1. CURRENT ORGANIZATION OF SESSIONS OF THE IODE COMMITTEE Sessions of the IODE Committee are organized every two years. Since the 17th Session (Paris, France, 2003), Sessions have been organized during the months March or April to make it possible to submit the Executive Summary of the Report to the IOC Assembly or Executive Council. The IOC Assembly or Executive Council need to adopt the Summary Report and Recommendations included therein and note the Resolutions adopted by the IODE Committee. DURATION OF THE SESSIONS The duration of the Sessions has remained approx. 4-5 days between the first and 9th Session (1979) but then drastically increased to about 2 weeks between 1981 and 1986, reducing to about 8 days between the 13th and 16th Session. As from the 17th Session in 2003 (due to budget reductions) the duration has been maintained at 5 working days (see Figure 1).  Figure 1: Duration of IODE Sessions The reduction in duration of IODE Sessions is in line with a similar reduction in the duration of the IOC Governing Bodies. The reduction of the duration of the Session has enabled us to reduce cost (for the local host, IOC/IODE and Member States) but has also put additional pressure on the Secretariat and Participants. As the adoption of the Summary Report has to take place on the last day it is not possible to include agenda items on that day and thus all substance has to be scheduled in 4 days. In addition the duration of a Session day is limited to 6 working hours, due to regulations for interpretation. Thus the total number of hours available to discussion agenda items is limited to 24. Whereas the duration of the Session has been limited to 5 working days, the agenda has become heavier in recent years. This is due, on one hand, to the increased collaboration with other Organizations (e.g. GOOS, JCOMM, ), but more importantly, it is due to the increased number of projects implemented by IODE, especially in terms of capacity building (e.g. the many ODINs that have been created). This expanding agenda is increasingly difficult to fit into the timeframe of 4 days (+1 day for the adoption of the summary report, recommendations and resolutions). 1.2 NUMBER OF WORKING DOCUMENTS The expanding agenda has also resulted in an increase in the number of working documents (this number excludes the national reports which are collated into one document). This is shown in Figure 2.  Figure 2: number of working documents per IODE Session 2. A NEW WAY TO PREPARE FOR AND IMPLEMENT SESSIONS OF THE IODE COMMITTEE Taking into consideration the observations made in 1.1 and 1.2 we believe that the time has come to rethink the way we prepare for and implement the IODE Committee Sessions. The following requirements are noted: 2.1 REPORTING ON ACTIVITIES Each activity of the IODE should be able to report to and receive guidance from the IODE Committee. As such each activity should prepare a report for each Session of the Committee (every two years) and, as required, a short progress report for submission to the IODE Officers (for their meeting during the inter-sessional period). Reports should include qualitative as well as quantitative elements (self assessment). In terms of quantitative reporting the RBM framework (Logframe), that was created for the establishment of the activity, should be used. In this regard we refer to Document 46. So for each expected result of the activity, reporting should be provided on meeting the performance indicators, reaching of the programmed benchmarks, etc. This Logframe, together with the qualitative reporting will facilitate the objective assessment of progress (or lack thereof) and guide the Committee with identifying corrective measures if necessary. The report should also include a financial report for the past inter-sessional period and, as required, a detailed work plan and budget for the next inter-sessional period. If the work plan includes actions that differ from the original Logframe (expected results), then a revised Logframe should be provided. The reports should therefore also include a clear set of requested actions. These can include a request for the continuation of the activities, a request for additional resources, etc. Finally the report may include (a) draft resolution(s) or recommendation(s) (we recall that a Resolution is a decision without financial implications to the IOC; a recommendation is a draft decision that has financial implications for IOC and thus requires formal approval by an IOC Governing Body i.e. Assembly or Executive Council). Reports on activities should be submitted to the IODE Secretariat not less than 3 months prior to a Session. The IODE Secretariat will then check the report (compliance with mentioned structure), assign a number and post the document on the Session web site. Member States should then download the document from the web site and analyze the document. Member States are encouraged to share comments on reports with the view of reaching a consensus on the requested actions. It may be appropriate to set up email discussion fora for certain documents that require extensive discussions. This service will be provided by the IODE Secretariat. A volunteer should be identified who will Chair the email discussion forum and prepare a report on the discussions, with clear recommendations for action by the Committee. Such reports should be submitted to the IODE Secretariat, not less than 2 months prior to the Session. The IODE Secretariat will then post this discussion document as an addendum to the original report. 2.2. SUBMISSION OF PROPOSALS FOR NEW ACTIVITIES Each proposal for a new activity should have a work plan and budget attached that uses Results-based-management (RBM) methodology, so expected results and associated performance indicators, means of verification, benchmarks are clearly identified. A proposal should originate either from a Group of Experts, a Steering Group of an existing Project or from a group of Member States. It should be avoided for an individual or one member state to submit a proposal for an activity. Proposals should fit within the medium-term strategy of IODE (as defined) and contribute to the expected results defined in that strategy. Only proposals with a realistic expectation of funding from extra-budgetary sources or that have a substantial in-kind support should be submitted. Finally the proposal may include (a) draft resolution(s) or recommendation(s) (we recall that a Resolution is a decision without financial implications to the IOC; a recommendation is a draft decision that has financial implications for IOC and thus requires formal approval by an IOC Governing Body ie Assembly or Executive Council). Each proposal should be submitted to the IODE Secretariat not less than 3 months prior to the Session. The IODE Secretariat will then check the proposal (compliance with mentioned structure), assign a number and post the document on the Session web site. Member States should then download the document from the web site and analyze the document. Member States are encouraged to share comments on proposals with the view of reaching a consensus on the requested actions. It may be appropriate to set up email discussion fora for certain proposals that require extensive discussions. This service will be provided by the IODE Secretariat. A volunteer should be identified who will Chair the email discussion forum and prepare a report on the discussions, with clear recommendations for action by the Committee. Such reports should be submitted to the IODE Secretariat, not less than 2 months prior to the Session. The IODE Secretariat will then post this discussion document as an addendum to the original proposal document. 2.3. NATIONAL REPORTS For each Session of the Committee Member States are requested to prepare National Reports. These reports traditionally included highlights of the past inter-sessional period. Since IODE-XIX the reporting structure has been changed and is available as Document IOC/IODE-XIX/Inf2. National Reports should be submitted to the IODE Secretariat not less than 2 months prior to the Session. The IODE Secretariat will collate the reports and also analyze the responses of questions 5 to 14. This analysis will be included in the collated report. 2.3 ACTION PAPER In order to facilitate the work of the Committee during a Session, a so-called Action Paper has been prepared at past Sessions (except IODE-XVIII). This document should now include the following elements for each agenda item: Introductory paragraphs that summarize the intervention of the introducer of the agenda item. It is noted that introductions of agenda items should not be longer than 5 minutes of plenary time. Paragraphs proposed as actions by the Committee It is noted that discussions in Plenary will be summarized by the Secretariat during the Session and added to the introductory paragraphs if necessary and/or if they differ from the proposed action paragraphs Logframe: for each activity a logframe (expected results, performance indicators, means of verification, programmed benchmark) for the next inter-sessional period will be added. Financial implications: for each agenda item the financial (resource) implications of the proposed actions will be included in the action paper. These will be used during the Session to compose the proposed work plan and budget CONDUCT OF THE SESSION The Session is traditionally chaired by the IODE Chair. At IODE-XIX it will be proposed to henceforth elect two Co-Chairs. The two co-chairs will agree on the agenda items that each will chair during the Session. The Co-Chair will open an agenda item by inviting the person who will introduce the item. The introducer will refer to the relevant working document and give a brief (not more than 5 minutes) introduction to the Document, referring especially to the actions required from the Committee. The introducer will also refer to the discussion document (see 2.1 and 2.2). Following the introduction, the Co-Chair will invite Member States to comment, especially regarding the recommendations or resolutions formulated in the original document or in the discussion document. For each agenda item there should be actions taken by the Committee. These can be included in the body of the summary report or they can be Resolutions or Recommendations. SESSIONAL WORKING GROUPS Traditionally a number of sessional working groups, composed of participants of the Session, are established during the Session. Preferably all sessional working groups are established under Agenda Item 2.4. As a minimum it is recommended to establish a sessional working group on Programme and Budget, and a sessional working group on capacity building. It is advisable not to establish too many sessional working groups, bearing in mind that most national delegations to the Session have only one member. The sessional working groups will meet after the plenary sessions. For practical reasons the number of sessional working groups that can meet on-site at the same time is two. Sessional working groups can meet as from the first day (possible time slots are lunch-time and evening). Sessional working groups should meet prior to the opening of the relevant agenda item during the plenary. Exceptionally an agenda item can be re-opened or re-scheduled to allow a sessional working group to meet and report back to the Plenary. ADOPTION OF THE REPORT The adoption of the report is composed of adoption of the Resolutions and Recommendations, and adoption of the Summary Report of the Session. Traditionally a full day (the 5th day) is reserved for the adoption of the report. In practice the adoption usually takes day. Bearing in mind the revisions described in 2.1 to 2.4 it may be considered to only adopt the Resolutions and Recommendations and leave the finalization of the Report to the IODE Secretariat, provided that the number of changes to the paragraphs proposed as actions (see 2.3) is not substantial. This may make it possible to reduce the duration of the Session by day (ie a total of 4 days). 3. RECOMMENDATION FOR THE ORGANIZATION OF A JOINT IODE/IGOOS SESSION IN 2009 AS A MECHANISM TO IMPROVE GOOS-IODE COOPERATION The twentieth Session of the IODE Committee will be held in 2009. An invitation has been extended by the Peoples Republic of China of hold the Session in China. This offer will be discussed by IODE-XIX under Agenda Item 11. The Peoples Republic of China has also invited GOOS to hold its I-GOOS (Intergovernmental Committee for GOOS) in China. The revised terms of reference of IODE (revised at IODE-XVIII, 2005) now state (v) to support international scientific and operational marine programmes of IOC and WMO and their sponsor organisations with advice and data management services. This clearly indicates that IODE should play a more cross-cutting/horizontal role as a data and information management service provider for all IOC programmes. The restructuring of the IOC whereby the IODE programme has been housed together with GOOS under the Ocean Observations and Services section should facilitate collaborative activities between GOOS and IODE. Bearing in mind that IODE deals with delayed mode data as well as (an increasingly) with operational data, a closer collaboration with GOOS should be mutually beneficial: for the GOOS community the collaboration with the IODE network of data centres will provide the ocean observation community with access to the know-how of the global network and resources of NODCs (as well as WDCs) and also make use of the IODEs regional as well as global capacity building expertise. IODE will benefit from this collaboration by gaining a new and extensive user community as well as from increased visibility (and hopefully appreciation). One way to establish this closer collaboration could be through the organization of partially joint Sessions of the IODE Committee and I-GOOS (Intergovernmental Committee for GOOS). The Intergovernmental Committee for GOOS (I-GOOS), functioning under the IOC of UNESCO with co-sponsorship from WMO and UNEP, has the overall responsibility for formulation of policy, principles and strategy, and for planning and coordination of GOOS. 23 IOC Member States have identified a GOOS national representatives to I-GOOS. The I-GOOS Board consists of a chair and four vice chairs elected every two years by participating member states at I-GOOS plenary meetings. The chair of the GOOS scientific Steering committee is an appointed ex-officio member and the GPO director serves as secretary GOOS also has a GOOS Scientific Steering Committee (GSSC) that advises the Intergovernmental-GOOS governing board on scientific and technical matters including strategy, implementation and pilot projects. The committee meets annually and is comprised of members appointed by the GOOS sponsoring organizations, representatives of these sponsors, representatives of partner organizations and invited scientific experts. In 2005 the GSSC was expanded in order to include oversight of Coastal GOOS implementation. The GSSC as 12 members. Looking at the terms of reference of the two GOOS bodies we could say that the IODE committee combines the two: the IODE Committee deals with scientific and technical matters including strategy, implementation and pilot projects, but it also has the overall responsibility for formulation of policy, principles and strategy and for planning and coordination of [IODE]. There is also a difference in membership. Whereas the IODE Committee is composed of professionals specialized in data or information management (75 IODE National Coordinator for oceanographic data management and 33 IODE national coordinators for marine information management), I-GOOS is composed of a wider spectrum of expertise (heads of research institutions, policy managers (in various sectors of government), researchers,) representing the wide range of GOOS stakeholders, but as mentioned above the group is smaller (I-GOOS has 23 members). The IODE Committee currently has a Chair and Vice-Chair. IODE also has IODE Officers, composed of the Chair and Vice-Chair of the Committee, and Chairs of the Groups of Experts (including JOCOMM/IODE ETDMP) Ideally the IODE Committee should be able to interact with the GSSC for technical/scientific matters and with the I-GOOS for policy and strategy matters. In the past, coordination was attempted through participation of the IODE Chair in the GSSC and I-GOOS. However in practice the impact of this arrangement was limited and GOOS requirements have not really been taken on board. Inversely IODE has not featured very high on the GSSC and I-GOOS agenda. Establishing mutual paths of input or feedback between IODE on one side, and GSSC/I-GOOS on the other has not been easy. We can mention IODE-XIX and GSSC-X as an example: IODE-XIX takes place between 12 and 16 March 2007 in Trieste, Italy whereas GSSC-X takes place between 13 and 16 March in Korea. This makes interaction between the bodies impossible. I-GOOS VIII provides an opportunity as it will take place between 13 and 16 June 2007 at UNESCO Headquarters in Paris. However this Session is organized very close to the IOC Assembly which will make submission of recommendations from I-GOOS (that might be outcomes by IODE-XIX reviewed by I-GOOS) to the Assembly rather difficult. It should also be noted that a joint IODE/I-GOOS meeting will not result in cost savings: a quick scan of the membership of the IODE Committee and I-GOOS reveals only one common member. For the GSSC and the IODE Committee there are no common members at all. The interest of joint meetings will therefore be of substance benefit rather than financial. Efficient and effective cooperation between the IODE Committee, GSSC and I-GOOS will therefore need a different approach, a different model. If we consider an end-to-end model that includes observation, data management, product/service provision to end users then we can consider that GOOS covers two of these systems - observations and product/service provision to end users. IODE will play a role in the data management system. IODE centres should therefore respond to the needs of the observing system as well as to those of the actors that develop products and services (in some cases the IODE data centres may in fact be these actors). It is likely that the GSSC will be the partner who can identify the needs of the two aforementioned GOOS systems. These needs should then be submitted to IODE which will then, together with relevant GOOS experts, develop strategies and work plans that will enable the development of relevant data management systems (and, to some extent, product/service provision to end users systems). These could then be submitted to I-GOOS for inclusion in, and approval of the relevant policy and strategic decisions. To this we also need to add JCOMM which is considered as the implementing mechanism of GOOS. IODE already has close working relations with JCOMM through the JCOMM/IODE Expert Team on Data Management Practices (ETDMP) and is also a member of the JCOMM Management Committee. Accordingly there should also be linkages between these JCOMM bodies and the GSSC as well as the proposed GSSC/IODE technical working group. If it is preferred not to establish a new body then the ETDMP could possibly play the role of the GSSC/IODE technical working group, provided the TORs are adapted. This model is shown in Figure 3.  SHAPE \* MERGEFORMAT  Figure 3: GOOS/IODE coordinated cooperation model In order for the above model to function a suitable scheduling of GSSC, IODE and I-GOOS Session will be required. We recommend that the model is tested as from 2008 with a GSSC Session in 2008 (any time), IODE Session and I-GOOS Session in 2009 (possibly around March/April) and IOC Assembly in 2009. In order to enable joint discussions of the outcome of the work of the Joint GSSC/IODE technical working groups we recommend that the 2009 Sessions of IODE and I-GOOS are organized with a two joint events: one during the first day which will feature presentations on the issues that should be addressed by IODE (these presentations could be made by members of the joint GSSC/IODE technical working groups and/or members of the GSSC). The second joint event would take place the final day and would feature presentation and adoption of the work plan proposed by the IODE Committee, based upon the requirements defined by the joint GSSC/IODE technical working groups possibly adjusted by the joint event of the first day. This is outlined in Figure 4. It is noted that the joint events on the Day 1 and Day 5 may only require working day.  Figure 4: Organization of joint Sessions of IODE and I-GOOS We note that compressing the IODE Session into 3 days may not be realistic and we may need to plan for 4 days, as a minimum. This will require further discussion with I-GOOS and the IODE Committee. 4. ACTION REQUESTED FROM THE COMMITTEE  SHAPE \* MERGEFORMAT  ______________  Subject to approval by IODE-XIX, the IODE Committee will henceforth be chaired by two Co-chairs     IOC/IODE-XIX/49 Page  PAGE 4 IOC/IODE-XIX/49 Page  PAGE 3 IOC-WMO-UNEP-ICSU/GSSC-X/5.5.1 page  PAGE 8 IOC-WMO-UNEP-ICSU/GSSC-X/5.5.1 page  PAGE 7 IOC-WMO-UNEP-ICSU/GSSC-X/5.5.1 Annex page  PAGE 1 The Committee is requested to: endorse the proposed new way to prepare for, and implement Sessions of the IODE Committee endorse the proposed model for the organization of a joint IODE/I-GOOS Session in 2009 as a mechanism to improve GOOS-IODE cooperation JCOMM MAN JCOMM ETDMP Joint GSSC/IODE technical working groups ( IOC Assembly/Executive Council: review and adopt work plan and implementation strategy ( I-GOOS: review and adopt work plan as part of implementation strategy ( Day 1 Day 2 Day 3 Day 4 Day 5 Adoption Session of joint work plan I-GOOS Session IODE Session Joint Session of the IODE Committee and I-GOOS IODE: study needs and prepare work plan to respond to needs ( GSSC: define D&IM needs ( 127DFGO]kl  i j x лtetZNG h*cshKRh*cshKR5@\h*cshKRnHtHhKR5\mH nHsH tH%hVhKR5\mH nHo(sH tHhKRmH nHsH tHh>/hKRCJaJnHo(tHhKRCJaJnHo(tHhKR h>/hKRh>/hKR5\hKR5CJ\aJhKRCJaJhKRhKRCJPJaJhKRhKRCJPJaJo(h#hKRCJPJaJ7]kl   jskd$$Ifx\ q)   U(4 xaytFZ $$Ifa$gdFZgdKR  L7$8$]LgdKR Bccdg C j u v w $-DM a$gdKR$d-DM a$gdKR$ -DM ^a$gdKRgdKRgdKR$a$gdKR$a$gdKR  u v w + 1 "#$3;=?CY]^lmuwݽݽݰ|ws|lhdwhThn hhhH h5h3hchh21 h21@ hp@hpCJaJnHo(tHh*cshpnHtH h*cshp hKR@hKRhKR@h*cshKR5@\hKRhKRnHtHhKRhKR@ hKR@h*cshKR@h*cshKRnHtH' , L "#$3<=>?m$a$gd21gd21$-DM ^a$gdKR $]a$gdp$a$gdp$-DM a$gdp$d-DM a$gdKR$ & F 5-DM ^5`a$gdpQ+CD:;TU$a$gd21$a$gdh $ & Fa$gdh$a$gd- 0^`0gd3gdT $7$8$H$a$gd3gdT$a$gdT$a$gdTgdT$a$gd21Q*+BCH~9:xhx\xMxMxh-h-CJaJmH sH h$sCJaJmH sH h-h3CJH*aJmH sH h-h3CJaJmH sH h3mH sH h3h5mH sH h3h35mH sH hc5mH sH h35mH sH h3hTh5mHsH hTh5B*CJNHphhThT5B*CJphhTh5B*CJphhh~&r:;TU')02JL`yLPʺʮʺʺʺʋumaUaUaUah(eCJaJmH sH he\PCJaJmH sH h3mH sH h-h-mH sH jh-h-Uh-mH sH h1.CJaJmH sH h-h$sCJaJmH sH h$sCJaJmH sH h-h-CJH*aJmH sH h-h-CJaJmH sH h-hhCJaJmH sH hhCJaJmH sH h-CJaJmH sH !`aIJ !>$a$gdl 0^`0gdl$a$gd21$a$gd(egdT$a$gd-Popqr   4[d)I !?ĹĞđuuuihVMiCJaJmH sH hJ4^CJaJmH sH hlhl5CJaJmH sH he\P5CJaJmH sH h-CJaJmH sH hhhhCJaJmH sH j? hhhhUhhCJaJmH sH hlCJaJmH sH he\PCJaJmH sH hCJaJmH sH h(eCJaJmH sH %>?3 4 =">"B#C#7&8&i&j&c'd'L(M(((m)n)$a$gdg$a$gdv$a$gdVMigdT?@rtu".  3 Q V j l m ~ !!!$!6!9!""""="""ֺֺ֢ʢviviʖʖYhghJ^>*CJaJmH sH hK>*CJaJmH sH hKhK>*CJaJmH sH hKhg>*CJaJmH sH hKCJaJmH sH hgCJaJmH sH hvCJaJmH sH hKhJ^>*CJaJmH sH he\PCJaJmH sH hJ^CJaJmH sH hVMihlCJaJmH sH hVMihJ4^CJaJmH sH """"#A#B#9$?$$%%%&7&j&&&&&&I'e''L(((-)X)k)l)m))))))***+#+$+ܼ谤谘|l|hghVMi>*CJaJmH sH hVMihVMiCJaJmH sH hK>*CJaJmH sH hKCJaJmH sH hCJaJmH sH hVMiCJaJmH sH hKhK>*CJaJmH sH hvhv>*CJaJmH sH hvCJaJmH sH hgCJaJmH sH hJ^CJaJmH sH )n)**%+&+=->--....//]0^000 1 111223e4 $ & Fa$gdv$a$gdv$a$gdg$a$gdK$+%+&+,,=->-{..../-//////00G0^0001112222 3l3x3Ф|p`S````hv5CJaJmH sH hvhv5CJaJmH sH hKCJaJmH sH hM7=hM7=>*CJaJmH sH h6CJaJmH sH hM7=CJaJmH sH hHWCJaJmH sH hKhv>*CJaJmH sH hKhK>*CJaJmH sH he\PCJaJmH sH hgCJaJmH sH hvCJaJmH sH hJ4^CJaJmH sH  x333e4{4I5=6@677 > >V?a?i?~????D@t@u@v@AAAؼذذذؠwhYJhe\Phe\PB* CJaJph&"he\Ph3B* CJaJph&"he\Ph3CJaJmH sH h-CJaJmH sH hKhJ4^5CJaJmH sH h;5CJaJmH sH hKhK5CJaJmH sH hE2+CJaJmH sH hKhKCJH*aJmH sH h;5_CJaJmH sH hKCJaJmH sH hvhv5CJaJmH sH hvCJaJmH sH e4I5J5a5b5869677s8t8!9"9;9<9C=D=[=\=l>???? & FgdK$a$gdKgdK & FgdK^gdJ4^ $ & Fa$gdv?u@v@XAYAAFfHIIKKPMQMGPHPPPRRTTV VgdM7=$a$gdE2+$a$gd $a$gde\P$a$gde\PgdT 0^`0gdKAAAAA B"BBBBBDD7E"jhe\PCJUaJmHnHu jhe\PB* CJUaJph&"he\PB* CJaJph&"h;B* CJaJph&"h21h*K5CJaJh21h;5CJaJh21h)5CJaJh21h1{G5CJaJ6jh215B* CJUaJmHnHph&"sH tHuh215B* CJaJph&"h*K5CJaJh*K5B* CJaJph&"h;5CJaJh;h;5CJaJaaaaaaaaaabbbbbccc.c/c0c1c2c$a$gd21$-DM a$gd21$a$gde\P$a$gd1{Ggd*K$a$gd*K+c,c-c/c0c1c2cAcBcCcDcccccccccccccccccüÚwwwwgZgSFjhchM7=0JU hchM7=hM7=5CJOJQJ^JhchM7=5CJOJQJ^JjhFZUhFZh-|h-|mH sH h-|mH sH h-|jh-|0JUh21CJaJnHo(tHh*csh21nHtH h*csh21h21B* CJaJph&"he\PB* CJaJph&" jhe\PB* CJUaJph&"&j he\Ph;B* CJUaJph&"2cAcBccccccccccccccccccd#d y$Bgd21$a$gdc$a$gdcgdcgdc$a$gde\P $]a$gd21ccccccccccccccccccd ddddddķԨwgXE$jh\.h210JCJUaJhh\.h21CJaJmH sH h\.h21CJaJnHo(tHh21B*CJaJnHphtH"h21B*CJaJnHo(phtHh\.h21B*CJaJphhKC]h21B*CJaJphh;5CJOJQJ^JhchM7=5CJOJQJ^JhM7= hchM7=h210JmHnHujhchM7=0JUhchM7=0Jdd d!d"d#d$d%d7d>d@dCdDdIdJdPdQdRdSdTdUdVdhdodqdzd{dddddddddd޾vf޾_vf޾ h21h21h\.h21CJaJnHo(tHh21B*CJaJnHphtH"h21B*CJaJnHo(phtHh\.h21B*CJaJphhKC]h21B*CJaJphhFZh21h\.h21CJaJmH sH  h210JCJaJhmHnHu$jh\.h210JCJUaJhh\.h210JCJaJh##d$d%dDdTdUdVd{dddddddeI & F Eƀ1&.gd;$a$gde\P$ y$B^a$gd21 $ y$Ba$gd21gd21dddeebeyeeeeeeeeeeeeeee-f϶ϫmeO<8mhLk$hvh*KCJ(OJQJaJ(mH sH * jwhvh*KCJ(OJQJaJ(mH sH h*KmH sH $hGh*KCJOJQJaJmH sH h-|$h6h*KCJOJQJaJmH sH h*KCJOJQJaJmH sH he\Phe\Phe\PmH sH h;5CJaJmH sH h;h;5mH sH h;h;5CJaJmH sH h;he\P5mH sH he\PmH sH he\PB* CJaJph&"eeeeeeeeeeeeee0f1fzf{fgdvgdLk$a$gd*Kgd*Kh^hgd;I & F Eƀ1&.gd;-f.f/f0f1fvfxfyfzf{ffffffffffff-g.g/gjgkgϼϬpplplplplpalL(hLkh*KCJOJQJ^JaJmH sH h1{Gh*KmH sH h1{G$h1{Gh*KCJOJQJaJmH sH $hvh*KCJ(OJQJaJ(mH sH * jxhvh*KCJ(OJQJaJ(mH sH h*KCJOJQJaJmH sH $hLkh*KCJOJQJaJmH sH hLkhvh*KCJ(aJ(mH sH * jyhvh*KCJ(OJQJaJ(mH sH h*KmH sH {fffffffff-g.g/gkgmgngggggg$a$gde\P$a$gd*Kgd*Kkglgmgngggggggȶۣh21B* CJaJph&"hUhvh*KCJ(aJ(mH sH " juhvh*KCJ(aJ(mH sH $hLkh*KCJOJQJaJmH sH h6h1.h*KCJ(aJ(mH sH " jvh1.h*KCJ(aJ(mH sH  9 0&P 1h:pKR. A!"#$6% < 0 0&P 1h:pKR. A!"#$6% @ 00&P 1hP:p21. A!"#$6% $$If!vh5 5 55 #v #v #v#v :V xU(5 5 55 / 44 xaytFZ Dd t0  # A" Vx }2}a":T  @= Vx }2}a":T3ML@0 x[}lT=mc8\AC\r4@cIXT j%KH! X 6j|6H i5Pޭ`c7۝wk)% xJ] xek+ !4_|.\#D~ȱK~#@<t<b_/*/DW$o֝Oq[ a犔>a1 I @K .>3gsH _wn9Bô.>:Wla1/,jϺURfB Ëo;tsl!F5n )YP B=7ֽb?;7K xObqxW4ꘆRvء R8[>_opo2^8SS>ks|i\xo @g@zB::푗G_͗b?mjd[auql&.sUJbnS A]cif5bce{0ZtVq2mucUbL`aywW\:iܼVfVs/NZ[c;VXLmM&"ϻ98wcNYzUe͔Li˰v{)Og$Y.e<  ~B$]C%P\]e{mlj{^buyѺ1~>ryL ?nw3 obx# 0w̹"[ϴbֱgvqp y]1 s'=OL<5ֲxHdYGesZ~ͭU4glAuMJ\]ekZo0k!A lcG!etWڿ-rH l] aHP*[w)}J\]ek?`%.讲 ͱ_tW W eX l/eb ʔQ\]ek>djQ\]ek 5m`2F!ß`x%+ax odx3Û6w2q~g>!NϷ^v  .mݪe2qLߧ>|Ec<tڲNQ'^r|O̰Fmz5Ky xRT}iThc(Jϥ+Hr?8 ÞΞ3} swS,9q,W+G,y"9{|y8,j!Yxk<.![xx]Jn30H!ܿ Qa丩|?pys.sGΥs;`瑓C︅#cGN>}Dn#+Uwy#J6;V7[sjVʻ[wIo<唷[wioh̛fD(N o3ciQ7wyo 3im76ϼ+x(.ϼ+nD3ؽ8cÛ3ǃPzт fšp*`7B炪,񷋇뿊n{p.~Xq(8ȵ@4_\-Bњ _~ ߷N8M|68(v~S|}Ӝax0(b'J3$:p}יCi1IB{58-0x5ts0d9?u7թT\ܛ3~~Ƴ|l?#@8B De^ecogޛ7;{SU(,]Xh,c.#ąع DX+Rh<0J |$=v .DǶ#AfhMZ+b ڰ`ЮcrY2utGnVcї1a>|@=x'(HFacx,ƈߴ :+61?vQ)מU<ذG}q:O`M ʜ+Fk"\y<78d,;/[Gcv,Cڈ3"|R{9˅-q(3 =,؇ͥ:Q@nXIsiG3ږGB9t݃ K&~M}6_u+=%x|?ԩIAW&="|,Tgݽ=O^#RXIOie59WqL{}69VTgƊg{-V{XXQbij NX'3R'u坩<ޙʰ{6 EFoJ_/7< +4x?381 Q8C<rpPI܆8(F NQxo\O5gXckfO\lL<\ k'd:پhoݗٴw5Fu] _ hm=~(yf#6S;QPN;#6SQj?5픵}J)U}2픵} mg}ڌeu)k8-}\-2o{Ҝ3[1;/OowxB?#3ox^'(JW e_5_x\Au#Ne#9&m?-).P݈_!7aJhWSo6ߛ8?SonyoMFy NZ߱r\tuu?z7x>~Vx_ /7y5r,?-U8[!3Y쓌v_:o&نn >Tߠ}/iࣴnWL2Oĺhgy1BW:,!=!]̻υwkm޵>x'x1J2=xg2.3}N2xR.9Y{Lx%"'5qLHn{ȅoމI׹mJwR hWcNNmwwJoŅ7>?ugA|lTHGc+*P&j,'E j2U^eqlL+S9|_o0/[k^ s,{$1j_ v}v6or8V:KDd t",D  3 @"?Dd ~D  3 @@"?D@D NormalCJ_HaJmH nHsH tHt@t T Heading 1,$$dd@&[$\$^`a$5OJPJQJmH sH tH R@R  Heading 2$@&5CJOJPJQJ\^JtH DA@D Default Paragraph FontRi@R  Table Normal4 l4a (k@(No ListLB@L  Body TextB*CJPJmH phsH tH PQ@P  Body Text 3$a$5CJ$PJmH sH tH 4@4 THeader  !4 @"4 TFooter  !.)@1. T Page Number6U@A6 M7= Hyperlink >*B*phHOQH M7= textmedium1CJOJQJaJo(phB^@bB e\P Normal (Web)dd[$\$>@r> -| Footnote TextCJaJ@&@@ -|Footnote ReferenceH*H@H $s Balloon TextCJOJQJ^JaJB'B ;5_Comment ReferenceCJaJ<@< ;5_ Comment TextCJaJ@j@@ ;5_Comment Subject5\G_beI-Rbp_feb_^qponm]\I-Rbp   =_;y7]kl Cjuvw,L"#$3<=>?mQ+CD: ; T U ` a IJ !>?34=>BC78ijcdL M m!n!""%#&#=%>%%&&&&''](^((( ) )))**+e,I-J-a-b-8.9.//s0t0!1"1;1<1C5D5[5\5l67777u8v8X9Y99>f@AACCPEQEGHHHHHJJLLN NNNRRTTUU$U%UWUXUUUVVYYYYYYYYYYYYYYYYYYZZZZZ[[[.[/[0[1[2[A[B[[[[[[[[[[[[[[[[[[\#\$\%\D\T\U\V\{\\\\\\\]]]]]]]]]]]]]]0^1^z^{^^^^^^^^^-_._/_k_m_n_____000000 0 0 0 0 000000000000000000 0 00 0 00000000000?0?00000000000 00000000000000000000000000000000000000000000000000000000000000000000000000 0 0 0 0 00 0000000000 0000 0000000000000000000000000000000000000000000000000000000000000000000000000000@0@00@000b@000@000@000@000@0@0@0@0 @0@0@0.@0@0@0@0@0@0@0@0@0@0@0@0.00`00 0 000000000000000000000000000000000007]kl CjwL"#$3mQ+CD: ; T U ` a I?4=>BC7M m!n!""%#&#=%%&&&&''](^((( ) )))*I-J-a-b-8.9.//s0v8X9Y99>f@AACCPEQELN NNNRRTUU$U%UUUVVY0[1[2[A[[[[[[\#\$\D\T\{\\\\\]]]]]]]]1^{^-_/_m_n__@0@0@0@0@0@0 @0 @0 @0 @0 @0@0@0@0j00@0@0@0@0@0@000r@ 0@00 0 @0 @0000 00000000000 0j0 00j00j00j00j0000j00j00j00V000j00j00j00j00j00gj00nj00j00j00 j00 j00 j0 0!xoj0 0~j00 j0!0}j0!0|j00j00 j00 j00 0j00j00j0(0lj00j00j00j0,0lj0,0lj0,0lj0,0lj00j00j00j00j00j00j00K0>0y?ݱK0>0xK0>0v0j020`j020`j020`j020`j020`3zo0 0j0>0aj00 j00 j00 j00 j0A0bj0A0bB_j0A0aj0@0bj0E0aF,`j0E0`j0E0^j00 j00 j0\0ij0\0gj0\0gj0\0g]H^j0\0fj0\0ej00 j0K0`j0K0^j00 j00 j00 0,0 0@0@00{00{00j00\{00j00 @0j00j00 @0j00 @0 00Oj00j00 @0@0@0@0@0j00C@0@0j00@ACDGHIKLNPQSUW >n)e4? Va2c#de{fg579:=?BEFJMORTVg6UU"U[)[,[___!(*CJLsz|!!!!!Dor@̙ qP (    )8 ZC F. TTTTc"$t [ s *X99? "` )8f \ S  \  y   f ] S  ] *>R   f ^ S ^  )m f _ S _ (o( fB ` s *DԔ y * fB aB s *DԔ #m#f b S b X \ fB cB s *DԔ Ca D fB d s *DԔ ]BPf e S e̙  l f f S f̙   lB gB 0DԔ { lB hB 0DԔ  B AlB iB 0DԔ yq {lB jB 0DԔ L : / Z%/ #  s"*?`  c $X99?: / Z%/N   : # n : J"J) k# 3"n l c $X99?"`: J"J)` m C  m j"(  ` n C  nj"%  ` o C  o%(  ` p C pj"v ( ` q C q v ! B S  ? UY*[_Zt",tkt" TX @ teL e e4 e e et e4 et e e e4 et e e e4 et e e e4 et HHjjq 899r999JJ5K5KKK_     MMovv 899w999JJ:K:KKK_ = *urn:schemas-microsoft-com:office:smarttags PlaceType=*urn:schemas-microsoft-com:office:smarttags PlaceName8*urn:schemas-microsoft-com:office:smarttagsCity9*urn:schemas-microsoft-com:office:smarttagsplaceB*urn:schemas-microsoft-com:office:smarttagscountry-region Ț w!6>AJJN""$$w''++++E,N,V1_111:2C2q2z222;3D33333P4Y45 577a:k:::Z;d;;;/=6=======TTB[[[[[[[[[[[[[\\_,.![@@AACCYYB[[[[[[[[[[[[[\\D\H\{\\\\_3333333333337^w$u; U J-b-"1<1D5\5Z[2[A[B[[[[[[[[[[[[[[[[\\"\#\D\I\S\T\{\\\\\\]]]]{^^^^^^_B[[[[[[[[[[[[[\\__   y|JL_1JFV3~fc"`!*‚b6,nSCPV&\/]>NB`Dh&\,v&\z ^`OJPJQJ^Jo(-^`OJQJ^Jo(hHopp^p`OJ QJ o(hH@ @ ^@ `OJQJo(hH^`OJQJ^Jo(hHo^`OJ QJ o(hH^`OJQJo(hH^`OJQJ^Jo(hHoPP^P`OJ QJ o(hHh**^*`OJQJo(hHh^`OJQJ^Jo(hHoh  ^ `OJ QJ o(hHh  ^ `OJQJo(hHhjj^j`OJQJ^Jo(hHoh::^:`OJ QJ o(hHh  ^ `OJQJo(hHh^`OJQJ^Jo(hHoh^`OJ QJ o(hH0^`0o(0^`0o(.0^`0o(..0^`0o(... 88^8`o( .... 88^8`o( ..... `^``o( ...... `^``o(....... `^``o(........88^8`OJPJQJ^Jo(-^`OJQJ^Jo(hHo  ^ `OJ QJ o(hH  ^ `OJQJo(hHxx^x`OJQJ^Jo(hHoHH^H`OJ QJ o(hH^`OJQJo(hH^`OJQJ^Jo(hHo^`OJ QJ o(hHh^`OJPJQJ^Jo(hH-hpp^p`OJQJ^Jo(hHoh@ @ ^@ `OJ QJ o(hHh^`OJQJo(hHh^`OJQJ^Jo(hHoh^`OJ QJ o(hHh^`OJQJo(hHhPP^P`OJQJ^Jo(hHoh  ^ `OJ QJ o(hH==^=`OJPJQJ^Jo(hH-^`OJQJ^Jo(hHouu^u`OJ QJ o(hHE E ^E `OJQJo(hH^`OJQJ^Jo(hHo^`OJ QJ o(hH^`OJQJo(hH^`OJQJ^Jo(hHoUU^U`OJ QJ o(hHh ^`o(hH.^`OJQJ^Jo(hHopp^p`OJ QJ o(hH@ @ ^@ `OJQJo(hH^`OJQJ^Jo(hHo^`OJ QJ o(hH^`OJQJo(hH^`OJQJ^Jo(hHoPP^P`OJ QJ o(hH^`OJPJQJ^Jo(-^`OJQJ^Jo(hHopp^p`OJ QJ o(hH@ @ ^@ `OJQJo(hH^`OJQJ^Jo(hHo^`OJ QJ o(hH^`OJQJo(hH^`OJQJ^Jo(hHoPP^P`OJ QJ o(hH0^`0o(.0^`0o(..0^`0o(...0^`0o(.... 88^8`o( ..... 88^8`o( ...... `^``o(....... `^``o(........ ^`o(.........^`OJPJQJ^Jo(-^`OJQJ^Jo(hHopp^p`OJ QJ o(hH@ @ ^@ `OJQJo(hH^`OJQJ^Jo(hHo^`OJ QJ o(hH^`OJQJo(hH^`OJQJ^Jo(hHoPP^P`OJ QJ o(hH0^`0o(.0^`0o(..0^`0o(...0^`0o(.... 88^8`o( ..... 88^8`o( ...... `^``o(....... `^``o(........ ^`o(.........0^`0o(.0^`0o(..0^`0o(...0^`0o(.... 88^8`o( ..... 88^8`o( ...... `^``o(....... `^``o(........ ^`o(.........^`OJPJQJ^Jo(-^`OJQJ^Jo(hHopp^p`OJ QJ o(hH@ @ ^@ `OJQJo(hH^`OJQJ^Jo(hHo^`OJ QJ o(hH^`OJQJo(hH^`OJQJ^Jo(hHoPP^P`OJ QJ o(hH Dh CPVzb6,v1J/]!*|Jc"3~ RȤ                         RȤ        eh                 )        RȤ        RȤ        YX6\ c 3pw&!E2+1.A5M7=5?>@CCV`D1{GHHbtJ*Ke\Py\P*R<_U5V8ZFZ[[l#]^J4^;5_c(eVMiUjLkEp"q~&r$sv-|vHW }!J^)6T|B~ KR;3Kl!xKnSsg# - 21nhI]OGMUmYk- rGZl $2[[[[[[[V\\\\/_m_n__]4]4VVV@A[A[A[A[_@@Unknown Greg Reed Gz Times New Roman5Symbol3& z Arial7&  Verdana?Wingdings 2;SimSun[SOeTimes New (W1)Times New Roman5& zaTahoma?5 z Courier New;Wingdings#1h)& M. M.!4d[[ 2qHX ?2Limited distribution Administrator Boram Lee@         Oh+'0 $0 P \ h tLimited distributionAdministrator Normal.dot Boram Lee4Microsoft Office Word@2~@ΒLS@H=V@4V M՜.+,0 hp  UNESCO.[ Limited distribution Title  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXZ[\]^_`abcefghijklmnopqrstuvwxyz{|}~Root Entry F0ͤVData Y1TabledWordDocumentSummaryInformation(DocumentSummaryInformation8CompObjq  FMicrosoft Office Word Document MSWordDocWord.Document.89q