G' Kohlhammer - PowerPoint PPT Presentation

1 / 19
About This Presentation
Title:

G' Kohlhammer

Description:

Collection of scientific and user input in general, Definition of mission requirements ... Detailed definition of open architecture ... – PowerPoint PPT presentation

Number of Views:23
Avg rating:3.0/5.0
Slides: 20
Provided by: elt16
Category:

less

Transcript and Presenter's Notes

Title: G' Kohlhammer


1
ESRIN 22 April 2004
  • Who are we
  • Oxygen
  • GMES
  • G. Kohlhammer
  • EO Ground Segment Department

2
ESRIN
168 ESA Staff 394 Industry Staff
ESRIN
3
  • Vega Department
  • small launchers

Informatics Department ESA Corporate SW and
Networks
  • Earth Observation
  • Science and Applications Department
  • Ground Segment Department

Communication Web portal
4
Earth Observation in ESA
5
Earth Observation in ESRIN
EOP-S is responsible for Collection of
scientific and user input in general,
Definition of mission requirements Scientific
user support (Pis) Service and Application
development DUE, mainly public users GMES
application programmes Market Development
EOP-G is responsible for Mission Management,
Ground Segment Strategy Management User
Services and Mission Planning Facilities
Development and Operations Data and instrument
Monitoring Quality, Algorithms,
Processors Research and Technology,
Infrastructure for Services Support
6
EO Missions handled by EOP
1977
1991
2015
Europ.Users
MeteosatM-1, 2, 3
Transition M-7
Operational M-4, 5, 6
in cooperation with Eumetsat
Meteo
Cryosat,SMOS
GOCE,ADM
Earth Explorers
Science
Core2 Spectra, Wales, Earthcare
Opp2 ACE,EGPM, SWARM
ERS 1, 2
Applications Services
GMES
7
Oxygen Objectives
  • Oxygen is a concept
  • aimed at
  • Facilitating access to EO data from
    ESA and other missions
  • Increasing sustainability of EO data provision
    widening the range of offered data sources
  • Making the operations of EO missions more
    efficient

8
The need from the user view point
  • Today
  • gt75 of the EO data users, access data from more
    than 1 instrument/satellite
  • close to 90 require other auxiliary data (e.g.
    met. or ground truth data) to process/correct
    the satellite data
  • Today a lot of
  • missions, instruments, data, tools, information,
    (nearly)
  • off-the shelf technology
  • exist
  • However
  • no coherent access technically
  • no common international policy for data access
    and use
  • Everybody only knows parts Users know even
    smaller parts
  • Services providers spend up to 40 of their time
    getting access to data rather than providing the
    services

Demand
Resources
Access
Service
9
The need to respond to the technological evolution
Phase 1 (1980-1990) ESA to develop Europ.
Technology for EO Data access Earthnet Programme
Phase 2 (1990-2002) Large nationally funded
infrastructure developments ESA to enable
support such national developments in the context
of its and other individual missions
  • Phase 3 (2003-2010)
  • Develop global EO based service (independent of
    the space mission)
  • Convert and tune overcapacity to service needs
  • Reach sustainability of services, benefits
    budgets (exisiting operations to become more
    efficient)
  • Benefit from now available off-the shelf
    technology (less development)
  • Networking technologically and programmatically
    incl SMEs, incl contingency agreements among
    operators
  • International EO standards
  • Internationally agreed EO policy

10
ESA EO Programme Lines
Vertical and Horizontal Programmes in EO The
Envelop Programme and a future GMES Programme
will cover elements in both directions
User Needs for Continuity -------gt Evolution of
GS technology ------? Oxygen Concept
-------gt .
11
Oxygen Short-term Implementation
  • Analysis of Existing
  • Technically
  • Make existing more easily accessible (web
    portal, on-line archiving, networking, shared
    tools and services)
  • Tune new developments towardsa generic ground
    segment approach
  • Policy and price wise
  • Harmonize data access conditions

Service Support Infrastructure
12
Main Conclusion on existing Systems
  • User Services
  • Multiple EO Portals (11), Orders desk(11),
    Catalogues (12), Interoperatability Protocols
    (19)
  • Many servers for online data access .. in
    different locations .. with different type of
    services .. providing partial data sub-sets.
  • Difficult for a user to find the right path to
    the required data
  • Mission Planning
  • Many single Mission Planning tool. No tools
    supporting cross-missions acquisition planning.
  • ? Users and Mission Planners do not have
    visibility of acquisition possibility
    across-missions
  • Mission/Sensors Performance Monitoring Quality
    Control
  • Q/C tools are mainly instrument specific
  • No standard indicator of sensor or product
    quality
  • ? Complex environment limited to experts

13
Functions / Facilities Overview
  • There are many facilities
  • All with different functions, interfaces and
    agreements or contracts with ESA
  • The number of facilities is increasing (more and
    more public user entities assume a role as
    ground segment facility)
  • Discussion in cooperation and evolution has
    started at different levels with many of the
    facilities

14
Oxygen eoPortal
directory
  • http//www.eoportal.org
  • The new eoPortal was opened in November 2003 to
    provide access to European EO Non-ESA and ESA
    activities.
  • re-uses all components of the INFEO initiative
    (JRC/CEO) and adds new features
  • comprised of sub-sites to provide access to
    various data types
  • directory of resources
  • calendar
  • maps
  • catalogues
  • services

maps
catalogues

15
Principles
  • Facilities harmonization
  • Detailed definition of open architecture
  • identification of generic-common elements,
    specific mission elements and define standard
    interfaces
  • Evolution of existing system rather than new
    developments
  • Evolution of the common elements to integrate new
    missions

Specific to missions elements (Processors,Acquisit
ion,Q/C,etc.)
Mission A
B
C
Monitoring Control
D
Archives
User Services I/F
Data Management
Products Packaging
Networks
Examples of multimission common elements
16
Networking
  • HiSEEN High Speed ESA EO Network
  • 34 Mbps Network
  • Based on the GEANT/NREN (Academic) Backbone
  • Deployed at Frascati, Kiruna Salmijarvi and
    Oberpfaffenhofen
  • Completion planned for August 2004
  • Study for a cost-sharing model between different
    network partners end 2004

Envisat, ERS-2, Cryosat Landsat, MODIS, SeaWiFS,
NOAA, ALOS Future national missions (DLR, CNES)
17

GMES Schedule and Dependencies
2004
2005
2006
2007
2003
EOEP-2 ERS, EE,DUE, MD
EOEP-3 ?
ENVISAT
  • GMES Programme
  • (EO as service to public benefit)
  • Series of missions (nat., ESA, purchase)
  • Infrastructure ensuring EO service
  • Application Programmes

EW-Preparation
White paper/Green Paper
EO-Summit
ESA Ministerial
GMES Projects
Oxygen Idea Demo
18
Basic Principles of GMES
Policies
Users
Information Needs
Service Needs
Models In-Situ Satellites Ground Segments (Close
to Users) Service Segment
Observation Needs
Infrastructure Needs
19
Second GMES Service Element (GSE) Information
DayMay 06 2004, ESA-ESRIN
  • Presentation of GMES Services after 14 months
    (12 teams)
  • Introduce the new GSE consolidation actions
    (Atmospheric Monitoring and Humanitarian Aid)
  • Coordination between different GMES projects
  • Key issues and challenges GMES Service
    implementation
  • Participants
  • ESA delegations, GMES stakeholders,
  • end-users, EC-funded GMES projects


Identification of more requirements for Data,
Ground segments and service infrastructure !
Write a Comment
User Comments (0)
About PowerShow.com