ESA > Join & Share > HMA > HMA-EO DAIL



The main object of the "Earth Observation Data Access & Integration Layer Implementation" (EO DAIL) Project is to develop and validate an operational architecture and set of Heterogeneous Mission services for access to Ground Segment services from the GMES Contributing Missions (GCM) and the ESA missions. This project is a follow-on to the Heterogeneous Missions Accessibility (HMA) study.


In September 2005, ESA initiated the Heterogeneous Missions Accessibility (HMA) study aiming at harmonising and standardising the services provided the ground segments of the GMES contributing missions. The study was also responsible for designing and prototyping the architecture in which those services would be provided, in particular the Earth Observation Data Access & Integration Layer (EO DAIL).


The objective of HMA is to establish harmonised access to heterogeneous EO missions’ data from multiple mission G/S’s, including national missions and ESA Sentinel missions. The EO-DAIL and HMA implementation is being applied first in the context of GMES Space Component Data Access.


The technical solution that has been selected for this project is based on the architecture defined in the HMA project. The key design drivers leading to that solution are:

  • A reliable solution open to future changes: This development addresses the short-term needs of the GMES initiatives and as such the proposed solution relies mainly on currently well-understood and well-tested standards, technologies, designs and concepts to ensure fast, safe and cost effective implementation. For the medium to long-term needs of GMES, the proposed design has been chosen to be capable of evolving with the changing service portfolio, needs and technological advances.
  • Architecture Supporting Interoperability Concepts: The proposed architecture provides a solution that allows the easy and cost effective data and services integration among heterogeneous infrastructures that HMA requires. This architecture focuses on processes rather than on the underlying IT infrastructure.
  • Modular architecture based on COTS: A key driver of the architecture design is the maximization of the reuse of COTS and OpenSource products to reduce the development costs and minimize timescales.

Identity Management

User and Identity Management has been recognised during the HMA study as one of the key elements of the HMA architecture due to the sensitive nature of the data and services provided by the ground segments of the GMES Contributing Missions.
The selected architecture for the Identity Management follows the line of the architecture prototyped and demonstrated during the previous HMA project. This architecture responds to the key requirements that arose from the GCM’s and ESA, namely it:

  • Is applicable to a heterogeneous environment by using COTS tools based on standards minimising integration effort for GCM’s with legacy components
  • Is applicable to a distributed environment where each node can be both a Service Provider (SP) and an Identity Provider (idP)
  • Is applicable to a distributed environment where individual policies can be appliced at the GS level by allowing each GCM to have its own Policy Enforcement Point (PEP)


Delivered with the architecture will be 4 main services:

  • HM Collection Catalogue service – providing a central catalogue of the collection metadata of all the catalogue services accessible through the EO DAIL architecture
  • HM Product Catalogue service – providing a distributed catalogue capability allowing users a single access point for placing requests to any of the catalogue services accessible through the EO DAIL architecture
  • HM Programming service – providing an interface to enable HMA users to place and manage programming requests to any of the programming services accessible through the EO DAIL architecture
  • HM Ordering service – providing an interface enabling HMA users to order products from any of the Ordering services accessible through the EO DAIL architecture

Whilst a client will be specifically developed in this project, all these services will provide interfaces compliant to the OGC specifications created during the HMA study and it will possible for external clients to connect to those services.


The technical tasks to be performed in this contract fall into 3 main activities:

  • Development and testing of the EO DAIL architecture and services
  • Integration of the GCM services with the EO DAIL
  • Support of the pre-operational use of the EO DAIL

The project will last 30 months divided in 2 phases.

Phase 1: EO DAIL Development and First HMA Integration (12 months)

In phase 1, the requirements baseline output from the HMA study will be reviewed and a consolidated version of the main requirement documents, the EO DAIL Requirement Baseline and the User Management specification for the EO DAIL, will be generated. The EO DAIL implementation and testing activities of phase 1 will conclude with a Factory Acceptance Test, after which the integration of a first batch of GCM GS services with the DAIL will take place.

Phase 2: EO DAIL Pre-Operational and Integration Phase (18 months)

In phase 2 the EO DAIL is put in a pre-operational mode, so is available for external interfacing, for the length of the phase whilst in parallel continuing the integration of additional GS services as available in a sequence of 4 batches.
Phase 2 concludes with a final presentation and handover of the system to the operations team.

EO DAIL Schedule

KO 04 December 2007Kick Off
SRR 22 January 2008System Requirements Review
PDR September 2008Preliminary Design Review
CDR January 2009 Critical Design Review
AR June 2009(ongoing) Factory Acceptance Test
PORRAR+4 Pre-Operation Readiness Review
P0 Start TBD Start phase 2
FO TBDFinal Presentation

Project member resources

Contributors to this page: Jolyon Martin
Marco Nota .

Page last modified on Wednesday 17 of June 2009 10:49:59 CEST by Jolyon Martin.

Category: HMA