Annexes

Annex I: List of Participants

Atmospheric Observation Panel for Climate (AOPC):

Joint Data and Information Panel (JDIMP):

Local Participants:

Secretariat:

Annex II: Agenda

1. OPENING OF THE JOINT SESSION

1.1 Opening

1.2 Welcome and Conduct of the Meeting

1.3 Election of the joint session Chairman

1.4 Approval of the Agenda

2. REPORTS ON CURRENT STATUS AND UPDATE

2.1 Sponsors Reports

2.1.1 Global Climate Observing System (GCOS)

2.1.2 Global Ocean Observing System (GOOS)

2.1.3 Global Terrestrial Observing System (GTOS)

2.1.4 World Climate Research Programme (WCRP)

2.2 Reports of Panels and Other Bodies

2.2.1 Atmospheric Observation Panel for Climate (AOPC)

2.2.2 Joint Data and Information Management Panel (JDIMP)

2.2.3 Terrestrial Observation Panel for Climate (TOPC)

2.2.4 Ocean Observations Panel for Climate (OOPC)

2.2.5 WMO Commission for Climatology (CCl)

2.2.6 WMO Commission on Basic Systems (CBS)

2.2.7 WMO Commission for Marine Meteorology (CMM)

2.2.8 Integrated Global Ocean Services System (IGOSS)

2.3 Other Technical Reports

2.3.1 Integrated Global Observing Strategy (IGOS)

2.3.2 Re-analysis Projects

2.3.3 Extreme Events Workshop

2.3.4 European Climate Support Network (ECSN)

2.3.5 El Niño - Southern Oscillation (ENSO)

2.3.6 El Niño - Southern Oscillation Retrospective

2.3.7 United Nations Framework Convention on Climate Change (UNFCCC)

3. COORDINATION OF JOINT AOPC AND JDIMP ACTIVITIES

3.1 Data and Information Activities for GCOS Networks

3.2 Global Observing Systems Information Center (GOSIC)

3.3 Metadata and Data Set Registration

3.4 WMO Resolution 40 on the Exchange of Meteorological Data

3.5 Formation of a Joint Working Group on AOPC/JDIMP Issues

4. JOINT SESSION OF AOPC AND JDIMP

4.1 Briefing of the Panel Chairman on Outcome of the Individual Sessions

4.2 Future Joint Activities

4.3 Co-ordination of Cross-panel Activities

5. CLOSURE OF THE JOINT SESSION

A 6. ORGANIZATION OF THE INDIVIDUAL SESSION OF AOPC

A 7. DEVELOPMENT OF AN ATMOSPHERIC OBSERVATION PLAN

A 8. CURRENT ACTIVITIES AND DEVELOPMENTS

A 8.1 GCOS Upper-Air Network (GUAN)

A 8.2 GCOS Surface Network (GSN)

A 8.3 Atmospheric Constituents and Radiative Transfer

A 8.4 Air-Sea / Air-Ice Interface

A 8.5 Emerging Technologies

A 8.6 Extreme Events

A 8.7 Monitoring of GCOS Data

A 8.8 GCOS Requirements

A 8.9 Satellite data

A 9. RECOMMENDATIONS AND FINAL REPORT

A 10. CLOSURE OF THE AOPC INDIVIDUAL SESSION

D 6 ORGANIZATION OF THE INDIVIDUAL SESSION OF JDIMP

D 7 CURRENT ACTIVITIES AND DEVELOPMENTS

D 7.1 JDIMP Data Plan

D 7.2 Technical Advisory Group

D 7.3 JDIMP Metadata Project

D 7.4 Activities in the Asia-Pacific Region

D 7.5 ACSYS Data Management and Information Panel (ACSYS DMIP)

D 8 FUTURE ACTIVITIES

D 8.1 Future Atmospheric Data Management Issues

D 8.2 Future GOOS and Related Oceanographic Data management Issues

D 8.3 Future GTOS and Related Terrestrial Data management Issues

D 9 RECOMMENDATIONS AND FINAL REPORT

D 9.1 Establishment of Ad Hoc Working Groups

D 9.2 Reports of Ad Hoc Working Groups

D 9.3 JDIMP Data System Processes

D 9.4 Establishment of Ad Hoc Working Groups for the Data Management Plan

D 9.5 Reports of Ad Hoc Working Groups

D 9.6 Action Items

D 10 CLOSURE OF THE JDIMP INDIVIDUAL SESSION

Annex III: Acronyms and Abbreviations

Annex A-I: Outline of the GSN Quality Control (QC) Expert Meeting

An expert meeting on the GSN monitoring activity was proposed to discuss the initial implementation of the two GSN monitoring centres at DWD and at JMA, and their future development. The expert meeting should be attended by a small number (10 to 12 at most) of experts from the GSN Monitoring centres, WDC, and some other leading climate data centres. The expert meeting agenda should outline the following:

(1) Monitoring/QC proposals for initial implementation

JMA and DWD present their plans for the initial implementation

(2) Collaboration between DWD and JMA on the basic monitoring

The discussion should produce agreed technical details on the data sharing/comparison, on common procedures for format check and on other basic QC. Scope, format, and frequency of the monitoring products should be discussed also.

(3) Collaboration between GSN Monitoring Centres and WDC.

The GSN Monitoring Centres and the WDC should agree on the format, frequency and the means to provide quality checked (flagged) data sets.

(4) Existing monitoring methods

Experts from leading climate data centres should be invited to make presentations on quality control activities at these centres.

(5) Medium term development plan

JMA and DWD should present their plans for the medium term (3-5 years).

(6) Areas not covered by DWD/JMA

The areas which DWD and JMA do not cover, at least for the foreseeable future, should be identified. The expert meeting might develop a recommendation to JDIMP with regard to such areas.

(7) Formalities for QC information delivery

The expert meeting should recommend to JDIMP/CCl/CBS the ways the GSN Monitoring Centres deliver the QC information to the nations concerned. Two different ways have already been identified. One is an informal communication between the Monitoring Centre and the countries, and the other is a formal link through the WMO. These need approval from Member states and others involved in this process.

Annex A-II: Format of AOPC Meetings

· Review of current climatic events

Science

GCOS performance

GCOS implications

· Review of GCOS Systems

Status / problems

Changes

Feedback to operators

· New activities

· Revision of AOPC Plan

· Other issues from JSTC, JSC, OOPC, TOPC, JDIMP

· Task Groups

· Summaries

· Next meeting

· Closure

Annex A-III: Outline of the GCOS Plan for Atmospheric Climate Observations

1. Background - Manton

2. Linkages with Other Activities - Manton

3. Requirements for Atmospheric Observations - Manton

3.1 General principles

3.2 Role of data assimilation- Arkin

3.3 Role of satellite data- Manton

*.*Monitoring of climate events; e.g., ENSO, volcanoes, solar variability, extreme local events - Harrison/Karl

4. Components of the Observing Systems

4.1 Introduction

4.2 Issues

5. Atmospheric Dynamics and Thermodynamics- Parker

5.1 Introduction

5.2 GCOS Upper-Air Network (GUAN)

5.3 Satellite observations

6. Atmospheric Constituents and Radiative Transfer- Whelpdale

7. Surface Climate- Arkin

7.1 Introduction

7.2 GCOS Surface Network (GSN)

7.3 Products of assimilation systems

7.4 Specialised data sets

7.4.1 Introduction

7.4.2 Normalised Difference Vegetation Index (NDVI)

7.4.3 Snow cover

7.4.4 Soil wetness

7.4.5 Precipitation

7.4.6 Sea ice

7.4.7 Sea surface temperature

8. Air-Sea Interface- Harrison

9. Air-Land Interface

10 Air-Ice Interface, Including Impact on SST Analysis - Harrison

11. Emerging Needs and Technologies- Fleming

12. General Conclusions - Manton

Appendix 1 Goals and Terms of reference of AOPC

Appendix 2 Acronyms

Each component of the Plan (Chapters 5-10) should discuss:

• Purpose of data

• Data users and products

• Design principles

• Current status

• Initial increments to the system

• Network monitoring and quality control

• Data archive and access

• Product generation

• Long-term increments.

Annex A-IV: Recommended Best Practices for GUAN Stations

Members should attempt to comply with the following best practices:

(a) Long-term continuity should be provided for each GUAN station. This requires the provision of the necessary resources, including well-trained staff, and keeping changes of location to a minimum. Changes of bias caused by changes in instrumentation should be evaluated by a sufficient overlapping period of observation (perhaps, as much as a year) or by making use of the results of instrument intercomparisons made at designated test sites.

(b) Soundings should be capable of reaching 5 hPa^[15]. Because climate data are needed in the stratosphere to monitor changes in the atmospheric circulation and to study the interaction between stratospheric circulation, composition and chemistry, every effort should be made to maintain soundings regularly up to a level of at least 5 hPa. This threshold height will ensure consistent climate data coverage.

(c) Rigorous quality control should be exercised at each GUAN site. Periodic calibration, validation and maintenance of the equipment should be carried out to maintain the quality of the observations.

(d) Basic checks should be made before each sounding to ensure accurate data. The accuracy of a radiosonde's sensors should be checked in a controlled environment immediately before the flight. Checks should also be made during and/or at the end of each sounding to assure incomplete soundings, or soundings containing errors are corrected before transmission.

(e) Back-up radiosondes should be released in cases of failure. In the event of failure of a sounding instrument, incomplete sounding or resulting from difficult weather conditions, a second release should be made to maintain the record from the GUAN station.

(f) Detailed metadata for each GUAN station should be provided. Up to date records of metadata in a standard format should be provided to the GUAN Data Centre so that shifts in the data will not be mistaken for climate change. The metadata should include detailed information about the station such as location, elevation, operating instruments and their changes over time. Changes to operating and correction procedures should also be recorded. Both the corrected and uncorrected upper air observation should be archived. Climate change studies require extremely high stability in the systematic errors of the radiosonde measurements.

(g) CLIMAT TEMP data should be provided in an accurate and timely manner.

Recommended Best Practices for GSN Stations

Members should attempt to comply with the following best practices:

(a) Long-term continuity should be provided for each GSN station. This requires the provision of the necessary resources, including well-trained staff, and keeping changes of location to a minimum. In the case of significant changes in sensor-devices or station location, Members should provide for a sufficiently long period of overlap with dual operation of old and new systems to enable comparisons to be made and the identification of inhomogeneties and other measurement characteristics.

(b) CLIMAT data should be provided in an accurate and timely manner. CLIMAT reports should be transmitted by the fifth day of the month but not later than the eighth day of the month.

(c) Rigorous quality control should be exercised on the measurements. CLIMAT reports require quality control of the measurements themselves and the coding of the messages to ensure their accurate transmission to national, regional and world centres for their use. Quality-control checks should be made on site and at a central location designed to detect equipment faults at the earliest stage possible.

(d) The site layout should follow the recommended form. The layout of the site should follow the recommendations in the Guide on the Global Observing System (WMO- No 488).

(e) The site should be inspected regularly and maintained according to accepted practices. Regular inspection should be made at intervals of not less than two years. The inspections should check the siting and exposure of the instruments. Instruments should be checked regularly against a standard instrument which itself should be checked against a national or regional standard. Maintenance should include regular housekeeping at the site, cleaning of instruments and the recommended checks on automatic instruments.

(f) A national plan should be developed to archive daily data from GSN stations for climate and climate research purposes. The archive should include both observational data and metadata pertaining to each climate station. Metadata should include data concerning a station's establishment, subsequent maintenance, and changes in exposure, instrumentation and staff. The data and metadata should be in its original form as well as digital format.

(g) Detailed meta data and historical climate data for each GSN station should be provided. A GSN data centre should have an up-to-date digital copy of the historical climate data and all types of metadata for GSN stations. A current copy of the long-term series of data and metadata from GSN stations should be made available.

Annex D-I: Key Changes and Talking Points/Issues on the Draft Revised Data Management Plan

Key Changes

Chapter 1 (Introduction and Objectives)

• Stress linkages to science programs

• Text added to provide picture of breadth and complexity of G3OS issues

• Provide for feedback from users

• Addition as specific requirements for IOS

  - to collectors on success of their efforts

  - from users on how well needs are met

  - to science panels so that needed adjustments can be made

Chapter 2 (Data and Information System - Vision and Strategy)

• GCOS data and information management principles

• Updated to reflect G3OS

• Add cross-cutting aspect to scenarios

• Updated first scenario and alternative to reflect cross-cutting programmes

• Added new scenario designed to reflect cross cutting requirement

• Dropped climate specific scenario

• Give example of feed back in scenarios

• Discussed in detail under recommendations, but could be made clearer in the actual scenarios

Chapter 3 (System Design)

• Add section on system performance controls

• Done - includes mention of monitoring and feedback, linkage between components, need to identify and correct problems

Chapter 4 (Management of the Programme)

• Add periodic system reviews

• Add in under implementation strategy

Talking Points and Issues

• Existing systems

  - Adequate inventory

  - Clear picture of contributions

  - Existing agreement with centers of data

• G3OS data sets

  - Need to identify specific types of data as G3OS

  - Will there be core set that will be initial focus?

  - Peer review process

• Commitments to users and policy-makers

  - Need clear statement.

Annex D-II: Report of the Ad Hoc Working Group 2

- Metadata Issues -

• A metadata record is an essential part of every G3OS data set

• Distinguish between directory-level & archive-level metadata

  - Directory-level metadata is a subset

• Science programs are responsible for specification of archive-level metadata

  - Provides additional detail

  - Must be "welded" to the data

• Key words (directory level)

  - Definition by the three programs

  - JDIMP responsible for coordination

  - IODE will support implementation

• Continue the JDIMP Metadata Pilot Project

  - Evaluate, with a view to endorsing, the directory-level metadata structure for use in G3OS data management

Metadata Pilot Project

• Enter G3OS data set descriptions

  - Science programs select data sets

  - Information Center will assist

• Make available standalone data-capture & data management software

• Work with other programs in system implementation

  - e.g., IGBP, WCRP, CEOS members, ...

  - Participate in IGBP-DIS Focus 2 meeting (May, '98)

  - Information Center evaluate metadata structure for cross-center searches

What is a G3OS data set?

• Meets G3OS needs

  - contains necessary metadata

• Identified by relevant scientific panels

  - e.g., AOPC, HOTO, LMR, OOPC, TOPC, ...

• Includes relevant historical data sets

Information Center

• An activity to develop an operational model for an information center

• Should allow a user to locate and obtain G3OS data and information

  - a navigation tool

  - provide means for a user to evaluate the data stream

• Identify and document end-to-end processes and mechanisms for the G3OS data streams

  - focus on one or two data streams in each of the three programs

  - reveal gaps in the data systems

• Work closely with the data systems of the three programs

G3OS Workshop

• Discuss technical issues

  - metadata, co-ordination, data flow

• Involve representative data centres having G3OS data sets

• Make the issues broadly representative of environmental data needs

• Probably not prepared for a meeting in the near future

Annex D-III: JDIMP Data System Processes

Annex D-IV: Outline and Issues on the Revised Data Management Plan

· Group I (Science Issues, Political Issues, Applications, Variables of G3OS Interest, Is the System Working?)

Overview and Principles

• Should have scenarios but not necessarily three.

• Look at plans for GCOS, GOOS and GTOS for overall objectives and goals.

• Motherhood statements

  - Use of existing programs (para. 2.2.1)

  - Use of international standards (para. 2.2.2).

• Principles of environmental monitoring.

• Data policy principles - compare with GOOS (J. Withrow) and GTOS (G. Martin).

• This plan supports the end-to-end data management strategy and this plan will be laid out along the lines of this strategy.

• There needs to be a diagram in the introduction that shows the end-to-end system. It should work to clarify the responsibility of the JDIMP vis-a-vis the science panels in system oversight.

• GTOS already has a list of the terrestrial conventions of interest to JDIMP.

Political Issues

• Need to mention Conventions and other political drivers (e.g. Convention on Biodiversity, Framework Convention on Climate Change, Convention on Desertification). These conventions raise scientific issues and lay the framework for action to resolve these issues.

• The political drivers are the responsibility of the Sponsoring Organizations in co-operation with the Steering Committees.

Science Issues

• Improve understanding of processes influencing global change.

• The international conventions raise scientific issues and lay the framework for scientific action to resolve these issues. The responsibility for responding to these issues lies with the respective G3OS scientific panels and steering committees.

Requirements and Variables

• Respond to G3OS requirements originating from and the responsibility of the science panels. The section should be rewritten to reflect more strongly and clearly that the scientific requirements and associated variables of G3OS interest (both in situ and remotely sensed) are established by the science panels of the respective Global Observing Systems and supported by the JDIMP. (para. 2.2.3)

• Recognize that there are external applications and services of importance

• the G3OS such as CLIPS.

Is the System Working?

• Monitor and evaluate the system constantly. (para. 2.2.5)

  - Oversee the implementation of the system even in areas where JDIMP does not have any direct responsibility for action to ensure data system continuity and effectiveness.

  - In co-operation with the science panels, identify gaps and deficiencies in the end to end data system as opposed to gaps in, for example, the observation systems which are not in our terms of reference.

  - Co-ordinate amongst relevant data and information management activities within the G3OS to ensure maximum effectiveness and exchange of relevant information.

  · Co-ordinate with other international groups concerned with data and information management (e.g. CEOS, IGBP, WMO).

· Group II (Measurements, Collection/Data Assembly, Integration into Database, Data Archaeology, Data Product Generation)

Measurements

• Build on existing systems/expertise.

• Diversity of data and measuring techniques.

• Metadata essential i.e. documentation of observation procedures, types of instrument, initial quality control....

• Carried with data.

• Verify metadata in place (Information Center).

• Interact with programme groups to define necessary metadata requirements.

Collection/Data Assembly, Integration into Database

Clarification

- of "steps" in process

- integration/merging

· Distributed process.

· Data centre functions.

· May not involve (hierarchical) centres.

· Metadata (description of data set) to Information Center.

Data Archaeology

• Historical data should be identified where it is of use to G3OS (science programmes).

• Historical data with no metadata should be flagged but not necessarily rejected.

Data Product Generation

• Defined by panels/programmes.

Other

• Quality control/assessment not JDIMP business.

• Integration of G3OS data is required; what is role of JDIMP? Guidelines/recommendations? e.g., time and location data.

· Group III (Data & Product Distribution to Users)

• Timetable and actions items in Annex 1 should be updated regularly.

• Flow diagram up front based on the Wilson diagram.

Data and Product Distribution

• GOLDIS - still required as is GEDS (Guide to Environmental Data Sources), inventory to order data from a centre on an offline medium. There is a question as to whether this is still going to happen as described.

• There needs to an off-line system and an on-line system. The off-line system should also be available on-line.

• The names may or may not continue.

• Is there enough information available to describe these in detail in a plan or only the framework so as not to commit to something that may not be implemented as described?

• The on-line and off-line systems will cover data, products and metadata.

  - Vision paragraph with technical assumptions still needed. Outlook should be five years and assume capability and capacity will continue to increase. Will have higher communication speeds, cheaper computers, DVD etc.

  - However some will still not have access to the most modern technologies.

  - Principles? Data and information will be provided through state of the art agreed or de facto industry standards.

  - Metadata is considered to be an integral part of the data and products and access to the various levels of metadata will be facilitated in the development of the data management systems.

  - Inventories of products will have to be maintained on-line and be available on off-line media.

Feedback (3/4 to one page on feedback)

• The scenarios should remain in the plan and be updated as already suggested. (Perhaps in an annex.)

Several kinds of feedback

- Timeliness, completeness of data flows, is the system working?

- Data, data products, algorithms, standardised (if possible) feedback on quality, usefulness, application, consequences (published regularly through some centre).

- Feedback on additional user needs.

- User satisfaction.

· Development of feedback systems should be done in co-operation between JDIMP and the elements of the programs.

Information Center

• The Role of the Center in general terms at this point.

• Contact information.

• Will develop into a distributed virtual center.

• The Information Center provides pointers to all aspects of information on G3OS data management.

• Points to prominent users as a promotional element of the program.

· Group IV (Archiving, Metadata Products)

Metadata Issues

• What is metadata?

  • The information about the data contained in data sets which is needed to understand the content and optimise the usefulness of the data set.

  - What is a G3OS data set?

• Meets G3OS needs

  - contains necessary metadata.

• Identified by relevant scientific panels

  - e.g., AOPC, HOTO, LMR, OOPC, TOPC, ...

Includes relevant historical data sets

• A metadata record is an essential part of every G3OS data set.

• Distinguish between directory-level & archive-level metadata

  - Directory-level metadata is a subset.

• Science programs are responsible for specification of archive-level metadata (JDIMP can assist)

  - Provides additional detail

  - Must be "welded" to the data.

• Key words (directory level)

  - Definition by the three programs

  - JDIMP responsible for co-ordination.

• Stand-alone data-capture & data management software is available.

• Work with other programs in system implementation

  - e.g., IGBP, WCRP, CEOS members.

• G3OS programs should actively encourage the use of directory-level metadata as defined in the guidelines.

• The G3OS Information Center will use the directory-level metadata to aid users in locating and obtaining data sets.

Archiving Issues

• All G3OS data should be regularly forwarded to and maintained by at least one designated archive facility.

• Each facility should as a minimum

  - Guarantee indefinitely:

  • data integrity & long-term survival

  • that metadata are preserved with the data

  - Ensure that critical data are duplicated.

- Archive facilities should be able to retrieve data sets and their associated metadata as received at the archive.

Annex D-V: Proposed Terms of Reference for JDIMP

1. Terms of Reference (approved by GCOS JSTC and submitted to GOOS SC)

Recognizing the need for a comprehensive approach to formulate, implement, and oversee data and information management of the global observing systems, the JSTC of GCOS, the GOOS Steering Committee (GSC), and the GTOS Steering Committee (SC) have established a Joint Data and Information Management Panel (JDIMP).

The data and information management system for the global observing systems, G3OS, should be developed, to the degree possible, to accommodate data and products from the various components of the global observing systems. To do so, the JDIMP should consist of a core group of members representing the various global observing communities, as well as representatives from contributing disciplines, programmes, and agencies. The JDIMP should possess a broad range of expertise including research scientists, who use and understand global data sets, and data and information management experts responsible for significant components of existing operational and research global information management systems. The JDIMP should be a highly focused "problem solving" group, concentrating on resolving crucial issues affecting the quality and maintenance of global observing system data sets, and access to them. Particular agenda items may require additional experts be invited.

Terms of Reference:

• In concert with the G3OS science requirements and associated user communities, formulate and develop the G3OS Data and Information Management Plan(s);

• Monitor the overall implementation of the data-related elements of the plans;

• Make reports and present recommendations, as required, to the JSTC, GOOS, and GTOS SC on information management issues.

The JDIMP has the following specific responsibilities:

• Based on requirements from the science panels and user communities, to solicit data sets relevant in meeting the G3OS objectives;

• To identify gaps in available G3OS data sets and co-ordinate efforts to redress data deficiencies;

• To consider and develop a process whereby data sets may be identified and included as "G3OS Data Sets". The process should include an assessment addressing, inter alia:

  - that the data quality meets standards acceptable to peers of the submitting scientists using that type of data, or standards appropriate for specific applications,

  - that the data contain documentation (metadata) of a standard allowing adequate appreciation of the data quality;

• To identify the cross-cutting data and information management themes and establish a practical framework (e.g., metadata guidelines, information centre requirements, etc.) for these activities within the observing systems;

• To review, advise on, and provide oversight of the G3OS information management system(s) to ensure for example:

  - that access to data and products is provided as required,

  - that archiving activities are adequate.

2. Terms of Reference (modified by GOOS SC)

Recognizing the need for a comprehensive approach to formulate, implement, and oversee data and information management of the global observing systems, the JSTC of GCOS, the GOOS Steering Committee (GSC), and the GTOS Steering Committee (SC) have established a Joint Data and Information Management Panel (JDIMP).

The data and information management system for the global observing systems, G3OS, should be developed, to the degree possible, to accommodate data and products from the various components of the global observing systems. To do so, the JDIMP should consist of a core group of members representing the various global observing communities, as well as representatives from contributing disciplines, programmes, and agencies. The JDIMP should possess a broad range of expertise including research scientists, who use and understand global data sets, and data and information management experts responsible for significant components of existing operational and research global information management systems. The JDIMP should be a highly focused "problem solving" group, concentrating on resolving crucial issues affecting the quality and maintenance of global observing system data sets, and access to them. Particular agenda items may require additional experts be invited.

Terms of Reference:

• In concert with the G3OS science requirements and associated user communities, formulate and develop the G3OS Data and Information Management Plan(s);

• Monitor the overall implementation of the data-related elements of the plans;

• Make reports and present recommendations, as required, to the JSTC, GOOS, and GTOS SC on information management issues.

The JDIMP has the following specific responsibilities:

• Periodically review the G3OS data and information management plan(s) and principles of monitoring as required, commission studies needed by specific observing system components,

• Review adherence of G3OS to cross-cutting principles of data and information management,

• Advise on implementation of data and information management as requested by the senior science committees and sub-panels of the G3OS, to ensure that, for example, data and products are provided as required and archiving activities are adequate,

• Act as a G3OS focus in relation to policy issues, e.g., proposals and actions threatening the availability of environmental data;

Consider studies commissioned by specific observing system components and the implications for G3OS data and information management.