GEOSS

Architecture Implementation Pilot, Phase 3

- Call for Participation -

George Percivall, Open Geospatial Consortium GEO Task AR-09-01b Task POC December 2009

AIP-3 Call for Participation (CFP)

• CFP – Main Document – Purpose, Overview, Master Schedule – Instructions on how to respond to CFP • AIP Development Process (CFP – Annex A) – Evolutionary Development Process – Roles in AIP – Communications Plan – Principles of Conduct • AIP Architecture (CFP – Annex B) – Organized using RM-ODP Viewpoints

AIP-3 Summary in CFP Main Document

• Build on service architecture of GCI and AIP-2 – Build on both content and process – Increase emphasis on data provider point of view – Promote mash-ups in a "link-rich" environment • Engage Communities of Practice (CoP)/SBA – Continue AIP-2 CoPs – Identify new CoPs working with UIC and SBA Tasks • Focus on data; Promote content – Coordination with ADC Data Tasks – Vocabulary registries and ontologies as resources for scenarios – Data Sharing Guidelines implementation • Schedule to support Ministerial Summit, November 2010

GEO Task AR-09-01b Architecture Implementation Pilot

• Develop and pilot new process and infrastructure components for the GCI and the broader GEOSS architecture

Slide 4

Context of AIP SBA Tasks, UIC User Needs, Scenarios requirements support Design, Develop, Deploy Architecture Implementation Pilot (AIP) Task AR-09-01b Operational Capability GEOSS Common Infrastructure (GCI) Task AR-09-01a persistent implementation

AIP-3 Master Schedule – Draft

Post AIP-3 CFP Responses to AIP-3 CFP Kickoff Workshop (Europe) Demo Capture Workshop (US) (ExCom/GEOSec prior to Summit) Ministerial Summit & GEO VII (China) Finalize AIP-3 deliverables AIP-3 results transition to operations January 2010 Early March 2010 Mid March 2010 2 nd Half of 2010 (July 2010?) Nov 2010 2 nd Half of 2010 2 nd Half of 2010

AIP Development Process (CFP – Annex A)

• Evolutionary Development Process – Revise AIP-2 Annex A using AIP-2 Summary – Include modeling approach • Roles in AIP – GEO Secretariat role description needed • Communications Plan – Google Sites plan – Asian-Pacific work hours monthly Telecon • Principles of Conduct – No change

© 2009 Open Geospatial Consortium, Inc.

7

AIP Development Approach Participation Concept Development AR-09-01b Architecture Implementation Pilot Evolutionary Development Process Participation Call for Participation Participation Continuous interaction with external activities Updates for each step Kick-off Workshop Participation Architecture Documentation Development Activities Participation Baseline Persistent Operations (AR-09-01a) Operational Baseline and Lessons Learned for next evolutionary spiral

SBA-to-SoA Process 1. SBA Scenarios 2.

Enterprise Models

Optimize

3. Engineering Design

Specify

Use Cases Information Objects Component Types 4.

Deployment Plan

SBA-to-SoA Process Artifacts - Use Cases

AIP Architecture (CFP Annex B)

• ENTERPRISE VIEWPOINT – VALUE OF EARTH OBSERVATIONS • INFORMATION VIEWPOINT – EARTH OBSERVATIONS • COMPUTATIONAL VIEWPOINT – SYSTEMS OF SYSTEMS • ENGINEERING VIEWPOINT – COMPONENTS TYPES • TECHNOLOGY VIEWPOINT – COMPONENT INSTANCES

RM-ODP viewpoints from ISO/IEC 19793

Enterprise Viewpoint – Objective SoA Allows Users to Concentrate on

Decisions

The SoA Way: The Old Way:

Pre-Science

Find data Retrieve high volume data Learn formats and develop readers Extract parameters Perform spatial and other subsetting Identify quality and other flags and constraints Perform filtering/masking Develop analysis and visualization Accept/discard/get more data (sat, model, ground-based) DO Exploration SCIENCE Initial Analysis Use the best data for the final analysis Derive conclusions Write the paper Submit the paper Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Web-based Services:

Find Data Read Data Extract Parameter Subset Spatially Filter Quality Reformat Reproject Visualize Explore Analyze Minutes Days for exploration Use the best data for the final analysis Derive conclusions Write the paper DO SCIENCE Submit the paper

SoA Link-Rich Environment Provides:

discovery, access, manipulation, visualization, and analysis

.

Scientists have

more time to do science.

Decision makers rapid access to information

Courtesy: Gregory Leptoukh, NASA GSFC

Data Provider Perspective

• AIP to increase data access services and to ensure services are correctly registered in the GEOSS CSR • Assumptions of Data Provider services 1.

2.

3.

Components are deployed as a network accessible services, i.e., have internet address reachable by users Metadata in catalogue includes internet address in “on-line linkage” Interoperability Arrangement for “on-line linkages” is supported by Services and Community Clients

Enterprise Viewpoint Scenarios Scenario GEO Task/ CoP Status/comment AIP-3 Lead Editor

Emergency Management Air Quality DI-06-09: HE-09-02b AIP-2, GIGAS Biodiversity and Ecosystems Energy Drought management Malaria Env. Monitoring Water Quality (BI-07-01a) EN-07-03 WA-06-07c Water CoP HE-09-03b ?

AIP-2, ESIP Cluster AIP-2, EuroGEOSS, GIGAS AIP-2 EuroGEOSS, SDSC, FCU, ESIP EEA, EC/FP7

Actors

AIP-3 CFP Information Viewpoint - Draft

• Spatial Referencing • Observations, Sensor Information • Geophysical Parameters • Maps, features, coverages, and observations • Product Types: Global and framework datasets • Product Encoding Formats • Predictive Models • Registry Information Models and Metadata • Alerts and Feeds • Policy, Rights Management, Licenses

Global and Framework datasets for AIP-3

• GEOSS 10 Year Plan envisions “access to data and information through service interfaces” – Move from “Order and delivery of files” to “Access Services” • GEO Global Datasets Task DA-09-03: – Land Cover; Meteorological and Environmental; Geological; and DEM • Promote known global datasets with service access, e.g., – JPL Landsat dataset – OnEarth (300K Maps/day) – CEOS WCS DEM Data Server (ICEDS) – CIESIN socio economic data – (Send link to other global datasets with access services) • Link to GEO 2010 Baseline Initiative (Plenary doc 10)

Implementation of Data Sharing Principles

• Handling of Data restrictions – Use small set of controlled terms for data restrictions (drawn from typical licenses) – Define approach for listing data restrictions in metadata (ISO 19115) – Scenario: handling of data restrictions from multiple WMS in Portal.

– Scenario (low priority): Rights on web maps created from EO data; WPS – Identify relevant Interoperability arrangements • User registration in a system of systems – Several GEO members provide data freely and openly after user registration – Will all GEO users be required to register individually with each GEO member offering data?

– Evaluation of alternatives for single-sign in GEOSS context

• Increase dataset definition using interoperability arrangements – Registries and ontologies as resources for scenarios • Registries and ontologies for observables – User Requirements Registry – DIAS Definitions – WMO definitions – QA4EO for EO sensor characterizations (Task DA-09-01a) – ISO 19100 standards for • Engineering Use Case for several Enterprise Scenarios/UCs – Client to visualize and relate terms accessed from on-line registries – Enterprise scenario maps terms for discovery (Semantic Mediation)

Computational Viewpoint

AIP-2 OUTLINE 4.1 SERVICE ORIENTED ARCHITECTURE (SOA) 4.2 GEOSS FUNCTIONS VIA SOA 4.3 GEOSS FUNCTIONS VIA BROADCAST 4.4 GEOSS FUNCTIONS VIA MEDIA CHANGE FOR AIP-3 CHANGE SERVICE TAXONOMY TO MATCH GCI

Services Viewpoint

Service Taxonomy Comparison

Engineering Viewpoints

5.1

5.2

5.3

5.4

5.5

5.6

5.7

ENGINEERING COMPONENTS AND TIERS GEOSS COMMON INFRASTRUCTURE USER INTERFACE COMPONENTS BUSINESS PROCESS COMPONENTS ACCESS COMPONENTS TEST FACILITY FOR SERVICE REGISTRATION ENGINEERING USE CASES Changes for AIP-3 Update component types and interoperability arrangements Update Engineering Use Cases using AIP-2 results

GEOSS Common Infrastructure AIP-2 Augmenting GCI Main GEO Web Site Registered Community Resources GEO Web Portals Community Portals

Client Tier

Client Applications Registries Components & Services Standards and Interoperability Best Practices Wiki User Requirements GEOSS Clearinghouses Community Catalogues Workflow Management

Business Process Tier

Mediation Servers Alert Servers Processing Servers Test Facility GEONETCast Product Access Servers Sensor Web Servers

Access Tier

Model Access Servers

Engineering Components and Interoperability Arrangements

AIP-2 Transverse Use Cases

Technology Viewpoint

• 6.1 COMPONENT REGISTRY • 6.2 OPERATIONAL PERSISTENCE

Persistent Exemplar Services

• Criteria to be a persistent exemplar 1. Registered in Component and Service Registry (CSR) as “Continuously Operational” 2. Accessible through a GEOSS Interoperability Arrangement that is an international standard. 3. Level of Service: Available >99% of the time (~7 hours downtime/month); Adequate network bandwidth and hardware for performance • 192 services met criteria 1 & 2 as of 13 July 2009, – Methods to assess criterion #3 to be developed