1. Data Access Operational Interfaces for GMES Contributing Missions
CDS team
E.Monjoux, B. Greco, B. Rosich , A. Tassa
G.M.Pinna, O. Barois
P.Mougnaud, P. Goryl, G. Ottavianelli
G. Landgraf, V. Amans, A. Baldi , R. Biasutti, J. Martin, M. Longo, M. Trovatello, S. Vazzana
G. Buscemi
D. Moretti

2. Outline of the presentation
GCM SOW Technical Package Introduction
Coordinated Data Access System Introduction
Overview of the system
Basic concepts about DataSets
System Architecture concept
Operational Scenarios
GCMs Operational Interface Requirements
GCMs Interface Implementation life-cycle
< GCMs InfoDay – April 10th, 2008 – ESRIN >

3. GSCDA System Overview GSC Data Access DAP Management GMES Service GMES
Long-term EO Data Requirements
DAP
Management
Agreements
Registrations
Data Requests
Subscription Registrations
GMES
Service
Projects
Data Requests
Subscriptions Updates
GMES
Service
Projects
GSC
Contributing Missions
GMES Service Projects
GSC
Contributing Missions
Coordinated Data access
System
GSC Contributing Missions
GSC Data Sets
GSC Products
GSC Products
Reports
GSC Products
GSC Data Access
< GCMs InfoDay – April 10th, 2008 – ESRIN >

4. Basic GSCDA DataSet concepts
DataSets can be classified…
…with respect to the production mechanism…
Stream
Regularly disseminated with pre-defined frequency within given time window and a given area. Example: Systematic NRT data provision covering the globe
Cumulative
Disseminated only at package completion after products accumulation. Example: Coverage of a given area within a given time window
Standalone
One-off dissemination after single request. Examples: Retrieval of a given batch of data from archive, or single shot acquisition
…with respect to the triggering…
Pre-defined DataSets
correspond to well identified user needs and are defined in advance. E.g. coverage of Europe
On-Request DataSets
cope with specifications that cannot be identified in advance (typically: for emergency or for gap-filling)
< GCMs InfoDay – April 10th, 2008 – ESRIN >

5. < GCMs InfoDay – April 10th, 2008 – ESRIN >
GSCDA Architecture
Mission
Planning
Acquisition/
Processing
Dissemination
CM GSC Products
User Services
Archive
GMES Service Projects
GMES Service Projects
GCMs
Order follow up
Advertisement
Data Requests
Subscription list update
Operational Reporting
CM GSC
Products
Reporting
and Performances
Data request
Core Infrastructure
User Registration
Service Projects Coordinated Interface
GSC
Data Sets
Advertisement
Post-processing Element
CDS
< GCMs InfoDay – April 10th, 2008 – ESRIN >

6. GSCDA Operational Scenarios
Example scenario: Geographic Area Coverage
Mission
Planning
Acquisition/
Processing
Dissemination
User Services
Archive
GMES Service Projects
GCM
Order follow up
Operational Reporting
Order for Pre-defined DataSet
CM GSC
Products
Reporting
and Performances
Core Infrastructure
Service Projects Coordinated Interface
GSC
Data Sets
Post-processing Element
CDS
< GCMs InfoDay – April 10th, 2008 – ESRIN >

7. SOW Technical Package GCM SOW Technical Package Introduction 3)1) 2) 3)
GCM SOW Technical Package Introduction
1) Coordinated Data Access System Introduction
2) GCMs Operational Interface Requirements
3) GCMs Interface Implementation life-cycle
GCM SOW TOC ..
4) GCM Interfaces Implementation …
GSC Data Requirements
(DAP-S)
GSCDA Operational Interface Requirements for GCMs
GSCDA Operational Scenarios for GCMs
< GCMs InfoDay – April 10th, 2008 – ESRIN >

8. SOW Technical Package GCM SOW TOC .. 4) GCM Interface development …
DAP-S
GSCDA Operational Interface Requirements for GCMs
HMA programming ICD
HMA Cataloguing ICD
Table of Contents
Overview
Operational I/F Requirements
Generic
Customer Support Service
Ordering and Planning
Catalogue
Processing & Archiving
Data Dissemination
Data Circulation
Performances and Reporting
Security
Mapping Requirements to Operational Scenarios
HMA Ordering ICD
GSCDA Operational Scenarios for GCMs
GSCDA Reporting ICD
GSCDA Data Quality ICD …
< GCMs InfoDay – April 10th, 2008 – ESRIN >

9. First level de-composition of the Coordinated Data Access System
Manages coordinated mission orders and mission planning requests to the GCMs
Integrated CDS Reporting
Includes:
Service Registration/User management
Coordinated Support Desk
Ordering Interface for GSPs
Implements and manages orders and subscriptions vis-à-vis the GCMs
Manages emergency requests …
Advertise available services, datasets and subscriptions
Support:
products dissemination to GCA and/or to the GSPs
Support Long-term archiving of L0 data
Provides operational reports
Mission planning requests
Emergency requests
Supports electronic and media delivery from dedicated GSC archive/s
Supports On-line data retrieval of DAP-DSs
< GCMs InfoDay – April 10th, 2008 – ESRIN >

10. Overview of HMA/DAIL functionalities with respect to CDS (v2/v3)
DAIL programming could be used for emergency request
DAIL automatic reporting as an input to the M&C reporting about DAIL-based requests satisfaction
HM Services: Programming
DAIL M&C
DAIL Portal: report generation
GSPs Registration supported by DAIL User Management
DAIL supporting on-line ordering
DAIL catalogue used as a support to issue multi-mission orders (both for normal requests and for emergency)
DAIL support of subscriptions
DAIL portal can support advertisement of available collections and products
DAIL Portal
DAIL Collection Discovery
HM Services: Catalogue
HM Services: Ordering and Cataloguing
Receive mission planning requests via HMA I/F
Receive orders/sunscriptions via HMA I/F
Offer catalogue view via HMA I/F
Provide visibility on available collections
VFS could in principle support harmonized data dissemination from different repositories
HM/GS Services: Ordering, programming and Cataloguing
GS Discovery
DAIL VFS
DAIL to interface to the GSC Core Infrastructure Catalogue
HM Services: Cataloguing
< GCMs InfoDay – April 10th, 2008 – ESRIN >

11. CDS Implementation status
Initial DAP with critical datasets fairly consolidated
Initial feedback on approach / architecture from Service Projects favourable
ITT to GCMs issued 30/05/08, deadline 14/07/08
CDS going through a formal review procedure, SRR in June before initiation of ESA contractual actions for development (incl. upgrades to multi-mission gs) and operations
In parallel HMA implementation contracts being discussed in direct negotiation
< GCMs InfoDay – April 10th, 2008 – ESRIN >

12. HMA-I ICDs baseline evolution
Changes may be proposed by:
DAIL contract
HMA follow-on
HMA-T
GCMs Contracts
HMA-E Contract
Start of configuration control: DAIL PDR closeout
HMA-I
ICDs Baseline
Issue 1.0
HMA-I
ICDs Baseline
Issue 1.1
HMA-I
ICDs Baseline
Issue 2.0
HMA-I
ICDs Baseline
Issue 2.0
HMA-I
ICDs Baseline
Issue 3.0
DAIL Contract
CCN
CCN
PDR
CCN
CCN
GCM # 1 Contract
CCN KO
CCN
SRR
GCM # 2 Contract KO
CCN
SRR
< GCMs InfoDay – April 10th, 2008 – ESRIN >

13. HMA-I ICD change control - proposed approach
Until DAIL PDR: ICDs adjustments on-going. HMA-I ICDs baseline being fine-tuned during DAIL design; configuration control under DAIL PM
At DAIL PDR: HMA-I ICDs baseline frozen by DAIL PM (i.e. issue 1.0)
After DAIL PDR:
any change in the HMA-I ICDs baseline shall be assessed by the HMA-I Group
any change in the HMA-I ICDs baseline may result in CCNs in the DAIL contract
At any GCMs contract RFQ: applicable baseline is the latest available
At any GCMs contract KO: applicable baseline is the latest available
At any GCMs contract SRR: HMA-I ICDs baseline is frozen for the GCM (in principal agreement of ICDs without further change)
After GCM SRR:
any change in the HMA-I ICDs baseline may result in CCNs in the DAIL contract and in the GCMs contracts
< GCMs InfoDay – April 10th, 2008 – ESRIN >