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-01bArchitecture Implementation Pilot• Develop and pilot new process and infrastructure

components for the GCI and the broader GEOSS architecture

Slide 4

OperationalCapability

OperationalCapability

UserNeeds,

Scenarios

UserNeeds,

Scenarios

Design, Develop,Deploy

Design, Develop,Deploy

ArchitectureImplementation

Pilot (AIP)Task AR-09-01b

GEOSS CommonInfrastructure (GCI)Task AR-09-01a

support

persistentimplementation

requirements

SBA Tasks,UIC

Context of AIP

AIP-3 Master Schedule – Draft

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

DevelopmentDevelopmentActivitiesActivities

Kick-offKick-offWorkshopWorkshop

Call for Call for ParticipationParticipation

ConceptConceptDevelopmentDevelopment

PersistentPersistentOperationsOperations(AR-09-01a)(AR-09-01a)

Participation

Participation

Participation

Participation

ParticipationArchitectureArchitectureDocumentationDocumentation

Updates for each step

Baseline

AR-09-01b Architecture Implementation Pilot

Evolutionary Development Process

Operational Baseline and Lessons Learned for next evolutionary spiral

Continuous interaction with external activities

AIP Development Approach

4.Deployment

Plan

4.Deployment

Plan

1. SBA

Scenarios

1. SBA

Scenarios

2.Enterprise

Models

2.Enterprise

Models

3. Engineering

Design

3. Engineering

Design

Use Cases

Component Types

Information Objects

Optimize

Specify

SBA-to-SoA Process

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 – ObjectiveSoA Allows Users to Concentrate on Decisions

SoA Link-Rich Environment Provides:

discovery, access, manipulation, visualization, and

analysis.

DO SCIENCE

Submit the paper

Minutes

Web-based Services:

Perform filtering/masking

Find data Retrieve high volume data

Extract parameters

Perform spatial and other subsetting

Identify quality and other flags and constraints

Develop analysis and visualization

Accept/discard/get more data (sat, model, ground-based)

Learn formats and develop readers

Jan

Feb

Mar

May

Jun

Apr

Pre-Science

Days for exploration

Use the best data for the final analysis

Write the paper

Derive conclusions

Exploration

Use the best data for the final analysis

Write the paper

Initial Analysis

Derive conclusions

Submit the paper

Jul

Aug

Sep

Oct

The Old Way: The SoA Way:

Read Data

Subset Spatially

Filter Quality

Reformat

Analyze

Explore

Reproject

Visualize

Extract Parameter

Scientists have more time to do science.Decision makers rapid access to information

Scientists have more time to do science.Decision makers rapid access to information

DO SCIENCE

Find Data

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. Components are deployed as a network accessible services, i.e., have internet address reachable by users

2. Metadata in catalogue includes internet address in “on-line linkage”

3. Interoperability Arrangement for “on-line linkages” is supported by Services and Community Clients

Enterprise Viewpoint ScenariosScenario GEO Task/ CoP Status/comment AIP-3 Lead

Editor

Emergency Management

DI-06-09: AIP-2, GIGAS

Air Quality HE-09-02b AIP-2, ESIP Cluster

Biodiversity and Ecosystems

(BI-07-01a) AIP-2, EuroGEOSS, GIGAS

Energy EN-07-03 AIP-2

Drought management

WA-06-07c

Water CoP

EuroGEOSS, SDSC, FCU, ESIP

Malaria HE-09-03b

Env. Monitoring Water Quality

? 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

Data definition interoperability arrangements

• 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

Service Taxonomy Comparison

Services Viewpoint

Engineering Viewpoints

5.1 ENGINEERING COMPONENTS AND TIERS

5.2 GEOSS COMMON INFRASTRUCTURE

5.3 USER INTERFACE COMPONENTS

5.4 BUSINESS PROCESS COMPONENTS

5.5 ACCESS COMPONENTS

5.6 TEST FACILITY FOR SERVICE REGISTRATION

5.7 ENGINEERING USE CASES

Changes for AIP-3

Update component types and interoperability arrangements

Update Engineering Use Cases using AIP-2 results

AIP-2 Augmenting GCI

GEOSSClearinghouses

GEO Web Portals

GEOSS Common Infrastructure

Components & ServicesStandards

andInteroperabil

ityBest Practices

WikiUser

Requirements

Registries

Main GEOWeb Site

Registered Community Resources

Community

Portals

Client Applicatio

ns

Client Tier

Business Process TierCommunity

Catalogues

AlertServers

WorkflowManagem

ent

Processing

Servers

Access Tier

GEONETCast

Product AccessServers

Sensor Web

Servers

Model AccessServers

Test Facility

MediationServers

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