ADC Meeting # 2, Seattle, July 2006 Slide # 1 Overview of ADC activities (Committee) Ivan Petiteville, CEOS Meeting # 2, Seattle, July 20-21, 2006

ADC Meeting # 2, Seattle, July 2006 Slide # 2 Role of ADC ADC Structure ADC Communication Documents from the ADC Relationship between ADC and GEO Secretariat Issues & Way Forward

ADC Meeting # 2, Seattle, July 2006 Slide # 3 Role of the ADC - Purpose Defined as per Terms of Reference approved at GEO-II ( see doc. ref. GEO , dated 15 Dec ) Purpose: The ADC supports GEO in all architecture and data management aspects of the design, coordination, and implementation of the Global Earth Observation System of Systems (GEOSS) for comprehensive, coordinated, and sustained Earth observations.

ADC Meeting # 2, Seattle, July 2006 Slide # 4 Role of the ADC - Objectives Enable GEO … –to define the components of GEOSS, –to converge or harmonize observation methods, –to promote the use of standards and references, intercalibration, and data assimilation. based upon user requirements and building on existing systems and initiatives –to define and update interoperability arrangements e.g. for collecting, processing, storing, and disseminating shared data, metadata and products. –to facilitate data management, information management, and common services, –to help to promote data sharing principles for the full and open sharing and exchange of data and information, recognizing relevant international instruments and national policies and legislation.

ADC Meeting # 2, Seattle, July 2006 Slide # 5 Role of the ADC – Approach & Functions Providing advice and recommendation to GEO e.g.: –forum for dialogue and resolution of issues at varying levels; –advocacy within and across existing systems; –coordination with participating international organizations or national agencies; –establishment of subordinate teams to accomplish specific tasks Close liaison and work with existing operating authorities of GEOSS components Monitor and report to Plenary on the achievement of milestones and deliverables in the implementation of the GEO annual work plans. –Liaison between GEO Secretariat and Individual POCs - SHERPA

ADC Meeting # 2, Seattle, July 2006 Slide # 6 ADC Structure 5 Co-chairs representing CEOS, IEEE, Japan, USA and WMO 33 tasks (GEO 2006 WP) to be supervised by ADC –29 POCs ( 24 persons from the 96 Members, Participating Organizations and GEO Secretariat ) –More than 300 “moral” and “physical” persons ( GEO 2006 Roster ) involved

ADC Meeting # 2, Seattle, July 2006 Slide # 7 ADC Communication Meetings –Paris March 2-3, 2006 and Seattle July 20-21, 2006 Teleconferences –7 teleconferences since January s –More than 430 s exchanged in last 6 months between GEO Secretariat and ADC members ( Co-chairs, POCs, Lead and Contributing Agencies )

ADC Meeting # 2, Seattle, July 2006 Slide # 8 Documents from the ADC Minutes –For all meetings ( ftp://ftp.wmo.int/Projects/GEO/ADC ) and teleconferences Presentations –From meeting # 1: ftp://ftp.wmo.int/Projects/GEO/ADC/meeting01-presentations Documents –“Guidance for ADC POC's (Points of Contact) on GEOSS Implementation Tasks”

ADC Meeting # 2, Seattle, July 2006 Slide # 9 Relationship between ADC and GEO Secretariat The GEO Secretariat Expert Staff supporting the ADC are: –Osamu Ochiai –Michael Rast Frequent contacts with Co-chairs Participation to all ADC telecons and meeting

ADC Meeting # 2, Seattle, July 2006 Slide # 10 Issues & Way Forward

ADC Meeting # 2, Seattle, July 2006 Slide # 11 Task Management Issues Task reporting exercise (June 2006) –Sometimes no report from POC –Sometimes ADC sherpa bypassed – direct report from POC to GEO SEC Lack of coordination noticed for some tasks –Little coordination between POC and Sherpa –Insufficient task internal coordination between Lead and Contributing organizations under POC responsibility No progress on some tasks for which no POCs is nominated Observations

ADC Meeting # 2, Seattle, July 2006 Slide # 12 Task Management Issues Is the role of the Sherpa as interface between the POCs and the GEO Secretariat needed ? –Expected Added Value of the ADC Co-Chairs: coordination between tasks liaison and work with operating authorities of GEOSS components Advice & recommendation to GEO SEC –Experience from other GEO Committees? How to improve the task management & coordination by the POC ? Questions

ADC Meeting # 2, Seattle, July 2006 Slide # 13 Tasks Management Issues Questions (cont’) What to do for tasks with no POC ? How to strengthen the Coordination with other GEO Committees? –Direct coordination between Committees Co- Chairs or via GEO Secretariat ?

ADC Meeting # 2, Seattle, July 2006 Slide # 14 Way-Forward Tasks Management - Way Forward Official statement ( e.g. in GEO plan, new document,.. ) to describe: – the duties of the POCs – the relationship between Tasks POCs, Sherpas and the GEO SEC Pressure on the non-responsive POCs ? –Limit the number of tasks coordinated by the same POC –Replace the non-efficient POCs

ADC Meeting # 2, Seattle, July 2006 Slide # 15 Way-Forward Tasks Management - Way Forward Tasks with no POCs –Postpone or remove the task if not critical –Regroup with another related task Coordination with other GEO Committees –Possible GEO Co-Chairs meetings + teleconferences –Other Co-Chairs to attend ADC meetings

ADC Meeting # 2, Seattle, July 2006 Slide # 16 Observations Tasks Execution Issues (1/4) Tasks executed at different paces. Some critical tasks are progressing too slowly (euphemism !) even when considered as high priority tasks –Potential impacts on other tasks if linked ( see next slide ) –No means to force the highest priority tasks to be executed first Difficulty to impose a Priority list for “ADC” Tasks

ADC Meeting # 2, Seattle, July 2006 Slide # 17 Observations Tasks Execution Issues (2/4) Each task is executed independently w.r.t. other tasks –apparent total decorrelation between all tasks while some tasks outputs are required as inputs to other tasks

ADC Meeting # 2, Seattle, July 2006 Slide # 18 Observations Tasks Execution Issues (3/4) Each task is executed independently w.r.t. other tasks (cont’) –Potential mismatch between interfaces (protocol, data type, recommended standards,..) managed within more than one task

ADC Meeting # 2, Seattle, July 2006 Slide # 19 Questions Task Execution Issues Not progressing tasks: –What are the critical and non-critical tasks ? –What to do in each case ? Priority list of tasks –Should we establish a Priority list ? –How to force those tasks to be executed first ? Overall Coordination between tasks –How to improve it taken into account the relationship between them ?

ADC Meeting # 2, Seattle, July 2006 Slide # 20 Tasks Execution - Way Forward Need to establish a GEO overall task coordination process – Identification of tasks interdependencies and tasks criticalities (establishment of a priority list) –Description of the logic for the tasks execution (priority,inputs/outputs, schedule,..) –Generation and maintenance of a Project plan (MS-Project type) –Generation and maintenance of a GEO Overall Interface Control Document (BIBLE !). Identification of: The major GEOSS elements with high-level information The data types exchanged between those elements The protocols used for the data flow management The detailed Interface Control Documents (e.g. one per task) Way-Forward

ADC Meeting # 2, Seattle, July 2006 Slide # 21

ADC Meeting # 2, Seattle, July 2006 Slide # 22 Earth Simulator NASA Archives NASA Archives ESA Archives CERN Grid Reproc. Center CERN Grid Reproc. Center GEOWeb Portal GEOWeb Portal Ecosystem database Ecosystem database Internet SAR L1 & L2 GeoTiff MODIS L1 HDFEOS GEONetCast Any format Fire Location GML

ADC Meeting # 2, Seattle, July 2006 Slide # 23 Tasks Execution - Way Forward Not progressing tasks –if not critical task: Assess whether a change in the task organization (e.g. change of POC) might help Postpone or remove the task Regroup with another related task –if critical task: Assess the reasons for the stagnation and implement mitigations actions Way-Forward

ADC Meeting # 2, Seattle, July 2006 Slide # 24