ESA EO Ground Segment Department

1
ESA EO Ground Segment Department
2
ESA / ESRIN

• Vega Department
• small launchers

Informatics Department ESA Corporate SW and
Networks

• Earth Observation
• Science and Applications Department
• Ground Segment Department

Communication Web portal
3
Earth Observation in ESA
Mission and 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 New
Payload Data Systems
4
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

5
EO Missions handled by EOP
1977
1991
2008
Europ.Users
MeteosatM-1, 2, 3
Transition M-7
Operational M-4, 5, 6
in cooperation with Eumetsat
Meteo
Cryosat,SMOS
GOCE,ADM
Science
Earth Explorers
Core2 Spectra, Wales, Earthcare
Opp2 SWARM (ACE,EGPM),
ERS 1, 2
Applications Services
GMES SE
Earth Watch
TerraSAR
Fuego
GMES Sentinels
6
THE EARTH OBSERVATION EXPLOITATION DATA
INFRASTRUCTURE

• FARNBOROUGH (UK)
• BREST (F)
• MATERA (I)
• OBERPFAFFENHOFEN (D)

• CORE SERVICES AND USER SERVICES
• Mission Planning
• PRODUCT CONTROL SERVICE
• DATA UTILIZATION SERVICES
• MULTIMISSION FACILITIES SERVICES
• MARKETING TECHNOLOGY TRANSFER
• USER SUPPORT
• G/S PRODUCT DEVELOPMENT
• NATIONAL FACILITIES COORDINATION
• G/S STANDARDIZATION

Expert Support Laboratories
EO Payload Data Management Operations
Exploitation
ECMWF Met Network
Nat. GROUND STATIONS NETWORK

• FUCINO (I)
• KIRUNA (S)
• MASPALOMAS (E)
• NEUSTRELITZ (D)
• TROMSOE (N)
• Svalbard (N)
• GATINEAU (CND)
• PRINCE ALBERT (CND)
• SCANZANO (I)
• TIROS COORDINATED NETWORK

User Support Mission Management Market and
Exploitation Development
Commercial DATA DISTRIBUTION NETWORK
Science Users
VAC and Service Companies

• EURIMAGE
• ERSC

• ERSENVISAT Des
• SARCOM
• EMMA
• CCRS

28 FOREIGN STATIONS worldwide
7
Users and EO Missions
7300 ESA EO Users in 131 Countries
8
EC ESA Cooperation

• Framework agreement
• Joint GMES Steering Committee
• EEA
• GSE projects
• DG IST Cooperation
• Long Standing cooperation on several projects
• D-EOP, D-IST Agreement on
• Coordination in contracts
• Regular meetings
• JRC
• Many projects

9
OxygenOpen and Operational Ground SegmentJune
2004
10
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
• 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
11
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 (existing operations to become more
  efficient)
• Benefit from now available off-the shelf
  technology (less development)
• Networking technologically and programmatically
  incl SMEs,
• contingency agreements among operators
• International EO standards
• Internationally agreed EO policy

12
Oxygen Objectives

• Oxygen is a concept aimed at
• Facilitating access to EO data from ESA and
  other missions
• Increasing sustainability of EO data
  provisionwidening the range of offered data
  sources
• Making the operations of EO missions more
  efficient
• Oxygen has started more than 1 year ago and is
  ongoing
• to enlarge the benefits of EO (even in absence
  of GMES)
• Oxygen is probably a pre-requisite for a
  successful EO GMES component

13
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

14
ESA GS layout today
15
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 is
  ongoing at different levels with many of the
  facilities

16
Principles
17
EO Ground Segment Modularity Interoperability
Quality Control
User Services
Help Desk Web Portal
Mission Planning
Catalogue
Data Ordering
CO-ORDINATION CENTRE
SERVICES INFRASTRUCTURE
Network
Monitoring Control
Dissemination
Archive
Acquisition
Production
FACILITY
18
Ground Segment elements

• 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
Archives
D
User Services I/F
Data Management
Products Packaging
Networks
Examples of multimission common elements
19
PB-EO GS Task Force

• GS funding scheme
• GS multi-mission,
• Evolution from current, maintain historic data
• Building block approach with defined interfaces
• Competition
• Coordination
• Oxygen short-term projects in line with PB-EO GS
  task force recommendations

20
PBEO GS Task force vision on EO GS
Infrastructure
GMES Services
Comm.
Public
Science
Public
Public
Science
Public
Comm.
Service Infrastructure and Support
GEOSS Access
EO Data Access Integration Layer
Access
Access
In-situ Non-space systems
Tasking/Dissem
other European Mission ground segment
Non-European agencies ground segments
Production
M C
EUMETSAT
Archive
Acquisition
Satellite/ Missions
ESA
Na t
21
Oxygen Work Plan
22
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

23
Implementation Plan (2003 2005)

• EO Web Portal for awareness of missions, user
  services, products, information and service
  providers
• Online Data Access provision of online products
  and improve online exchange of data
• Service Support Environment for easing provision
  of Services by Service Providers
• Archive rationalization Ensure data Archives
  integrity and access for ESA and national
  missions support
• Harmonization of ground segments for current and
  future ESA missions
• Archive and NRT Facilities Architecture
• User Services and Order Handling

24
Implementation Plan (2003 2005)

• Policy and Programmatic
• Enlargement of data sources through 3rd parties
  cooperation
• Data policy evolution adjust ERS and Envisat
  data policy to GMES service needs and to internal
  cooperation requirements
• Ground Segment Task Force to define goals for
  European EO Infrastructure
• Integrating upcoming EO National projects in
  Europe
• Feasibility assessment at political, technical
  and programmatic level (Terrasar-X, Radarsat-2,
  Cosmo, Pleijades)
• Pilot activities for interoperability between
  catalogues, order and online distribution systems
  (standards in SOAP/XML)

25
Oxygen Phase 2

• Objectives
• cost-efficient Ground Segment infrastructure for
  future European and member states missions
• Prepare the EO Data Acess Component in a GMES
  proposal along with the mission and service
  proposals to assure coherent, planable,
  sustainable EO input to GMES
• Establish the (mission independent) single ground
  segment infrastructure and operations concepts
  for the new Earth Explorer missions (Adm, SMOS,
  2nd series of Core missions etc)
• Respond to user needs for access to maximum
  number of mission data
• Implementation
• See GMES preparatory phase proposal, the GSE
  infrastructure and Task Force recommendations
• Design and Architecture
• Interface Definition
• Development Contracts
• (Dedicated Programme Line rather than just using
  mission dependant funding)

26
Oxygen Technical Projects
27
Oxygen eoPortal

• http//www.eoportal.org
• The new eoPortal was created and opened in
  November 2003 to provide access to and promote
  European EO activities.
• provides access to web resources from ESA and
  other institutes
• 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

directory
maps
catalogues

28
eoPortal catalogues

• http//catalogues.eoportal.org
• Access to distributed catalogues,
• new client for catalogue interoperability based
  on the EOLI look and feel
• Provides two levels of search, collection search
  and product search
• Allows access to collections from distributed
  catalogues
• As INFEO follow-up currently ESA (gateway to
  MUIS), DLR (gateway to DIMS), NASA (gateway to
  EOSDIS)
• new standards (SOAP/XML with ISO compatible data
  model) shared with MASS Vito, Envisat, CNES-SPOT
  for inter-access towards DALI catalogue

29
Simple interoperable catalogues

• Principles
• Based in XML/SOAP
• Content of information minimized according to
  user needs
• On-going specifications
• Catalogue access (available, pilot activities
  on-going)
• Order Handling (definition being finalized with
  CNES, DLR)
• Systems supporting the above protocols
• MUIS / EOLI ESA users services front-end
• MASS / SSE non-ESA providers integration platform

30
ADAR Logical model (OASI-based)
31
MMFI Schedule

• Implementation of the Facilities Open
  Multi-mission Infrastructure and evolution of
  existing missions
• ITT to issued within May 2004 (completed within
  fall 2005)
• Migration plan toward ADAR architecture
• Envisat evolution
• ftp function (June 2004),
• Archives evolution (November 2004-2005),
• Completion of ERS and TPM integration by mid 2005
• Completion of Archive management and
  rationalization (HARM) activities within 2004,
  including European archive format implementation

32
Online Data Access Principles

• On-line Archive (MMFI - ADAR) Mass Storage Tape
  Libraries or on disk
• User data request via Internet bypassing manual
  validation (order or subscription)
• Product retrieval via Internet
• High speed Internet backbone (GEANT/NREN) for
  academic users
• Commercial ISP augmented with load-balancing and
  re-routing COTS
• Product distribution via Internet over Satellite
• Distribution Servers providing on-request and
  subscription data
• Electronic data distribution between GS Centers
  using High Speed Intranet (based on GEANT/NREN)
• Security Principles
• Detect and avoid unauthorized use of EO data
• Protection from malicious intrusion

33
Phase 1 Architecture
INTERNET
ADAR
ADAR / PDS FTP Server
Acq Stations
GEANT
ESRIN
ADAR
HiSEEN
GEANT
End Users
TX
DDS
Acq. Stations
ADAR
ADAR / PDS FTP Server
34
Network

• HiSEEN High Speed ESA EO Network
• 34 Mbps Network Based on the GEANT/NREN
  (Academic) Backbone
• De-facto high end-to-end throughput availability
• Cost effective solution
• Deployed at Frascati, Kiruna Salmijarvi and
  Oberpfaffenhofen
• Completion planned for August 2004
• On-line Data access available for end 2004

Envisat, ERS-2, Cryosat Landsat, MODIS, SeaWiFS,
NOAA, ALOS Future national missions (DLR, CNES)
35
Programmatic
36
Data Policy Constraints

• Technical limitations in
• Satellite operations time
• Ground segment throughput and performance
• Coherence/competitiveness of the access policy
  with other data providers
• Coherency of data policy with mission funding
  sources
• Industrial readiness to invest
• Public organisations readiness to purchase
  data/services from industry/from another public
  entity

37
GMES SE infrastructure needs
Policies
Users
Information Needs
Service Needs
Models In-Situ Satellites Ground Segments (Close
to Users) Service Segment
Observation Needs
Infrastructure Needs
38

GMES EO 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 SE Projects
Oxygen Idea Demo
39
Conclusion

• GMES is a user programme not a technology
  demonstration
• The users exist they already have tools and
  systems
• The EO ground segment exists with many players,
  contributors, systems.
• EO is just one element contributing to GMES
• Risk management is just one element of GMES
• The GMES success will be measured on whether it
  delivers not on the technology, the architecture
  or the mechanism used
• The challenge is to make this work together

40

• Thank you