Architecture and Data Management Strategy (Action Plan) Ivan 1 DeLoatch, USGS, ADC Co-chair Alessandro Annoni, EC, ADC Co-chair Jay Pearlman, IEEE, ADC Co-chair 13 th ADC Meeting Pretoria, South Africa May 2010

Presentation Overview Short Background Reflections on current state Considerations for a to-be state Discussion

5.3 Architecture and Interoperability The success of GEOSS will depend on data and information providers accepting and implementing a set of interoperability arrangements, including technical specifications for collecting, processing, storing, and disseminating shared data, metadata, and products. Interoperability will be focused on interfaces, defining only how system components interface with each other and thereby minimizing any impact on affected systems…….

GEOSS Common Infrastructure (GCI) The Cape Town Declaration stated: “We commit to explore ways and means for the sustained operations of the shared architectural GEOSS components and related information infrastructure”.

GEOSS Common Infrastructure Operational View Represents a COLOSSAL investment by GEO Members & PO in EO systems Delivers major societal benefits to USERS, such as policy makers & citizens Enables GEOSS resources to be readily discovered and accessed Provides improved interoperability Delivers trusted data & information Is "Open”, in accordance with DSP

Considerations Sustainable operations for the GCI to realize the vision for GEOSS What additional steps are needed? How do we incentivize participation in GEOSS? How do we mature from a collection of systems to a System of Systems?

Considerations cont. Architecture and Data Management Strategic Targets Supporting Data Sharing Principles and Action Plan Defining a data architecture GEOSSTasksTargets

Considerations cont. Integrating cross committee activities into routine operations including the requirements from other committees for architecture and data aspects Gap analysis and gap filling across Societal Benefit Areas Connecting the dots from an architectural perspective

ADM Strategy Challenges Moving beyond the GCI Defining a data architecture within a broader architectural context Facilitating transitions to operations of GEOSS (and facilitate providers) Integrating/transitioning cross-committee activities into the sustained operations Identifying areas of emphasis and prioritization of effort for architecture development Facilitating progress in societal benefit areas Measuring progress

Architecture Attributes Robust Expandable Adaptable Multicultural “Re” Usable Multiple access capability Supports decisions Sustainable

Key Architecture Functionality Requirements –Inventory/Assessment of SBA and Community needs –Gap analysis for data and services –Standardization needs –Core capabilities –User Requirements Registry Architectural Analysis –Prototyping –Architectural design Search & Retrieval (S&R) –Data and service registry –Search, evaluation, retrieval –Data policies (?) –User management Interoperability –Standards Registry –Best Practices Wiki –Ontologies –EO Data structure and format –Web protocols Quality Management –Service Quality monitoring including anomaly detection –Data quality –Service level agreements Integration –Support model outputs –Model web (Interactive coupling?) –Data Transformation –Web 2.0/3.0 –Sensor Web –Virtual Constellation User Access –Search and Retrieval Access –Dissemination –Usability –Fitness for use Capacity Building –Documentation –Manuals –Reporting

Understand Requirements Data Use Capacity Building & Feed back State of Play Discovery Gap Analyses Data Policy Interoperability Harmonization Data Quality Prototyping Data Access Harmonize Data Filling Data Gaps User RequirementsInventory and Gaps R&D Development Operations Services &Registries USER

Data and Service Registry Search / Evaluate / Access Data policies User management Service Integration Quality Management Search and Retrieval Current System Understand Requirements Gap Analyses Architecture Concepts R&D/AIP Interoperability Capacity Building User Access Contributed Resources Operations Technical Development User Interface Content Management User User Requirements

Service Integration Quality Management Search and Retrieval Current System Understand Requirements Gap Analyses Architecture Concepts R&D/AIP Interoperability Capacity Building User Access Contributed Resources Operations User Interface Content Mgt User User Requirements Understand Requirements Data Use Capacity Building & Feed back State of Play Discovery Gap Analyses Data Policy Interoperability Harmonization Data Quality Prototyping Data Access Harmonize Data Filling Data Gaps User RequirementsGaps Development Operations Services USER A F C B A B C D D E E F

Discussion Version 04 page 15