GSC Sentinel-2 PDGS OCD - Emits - ESA

GSC Sentinel-2 PDGS OCD
Issue 1 Revision 2 (draft) - 25.07.2010
GMES-GSEG-EOPG-TN-09-0008
page 230 of 350
PDGS performances. Nevertheless, it shall be sized sufficiently to allow for real-case
representative load tests on the PDGS integrated systems;
○ It aims for maximised flexibility targeting swift reconfiguration capabilities, mapping a
given physical layout from available generic workstations to match the system test
necessity, and supporting interactive handling of the platform itself as relevant for
investigation purposes such as for the implementation of workaround solutions, the
installation of operating system patches, etc.
○ It aims for deployment in an adapted environment guaranteeing sufficient space for all
the staff working in the IV&V and maintenance processes, and housekeeping all
reference documentation with appropriate human browsing mechanisms (in paper form
or otherwise);
○ It shall be composed by hardware identical or compatible to a large extent with the one
of the deployed PDGS including middleware configurations;
○ It shall be assumed network connectivity to the PDGS deployed sites will be
ascertained supporting secure remote access for software deployments and
troubleshooting on the operational sub-systems.
○ As a standalone PDGS, it aims for transportability in any European location clearly
qualifying and quantifying associated site installation requirements (e.g. required
power resources, cooling, workplace, connectivity requirements, etc).
○ It aims for maximum reuse of widely used market solutions for all system management
support functions dedicated to system inventory, revision control system (e.g. GIT,
SVN, CVS, etc), documentation management (e.g. InfoTrove, KnowledgeTree, etc)
and system anomaly management (e.g. Jira, Mantis, Bugzilla, etc).
5.2.4.5.3 Function Interfaces
The following interfaces are identified:
○ Secure network access interfaces to the PDGS centres (e.g. ssh, sftp) for
troubleshooting and software deployment activities;
○ An interface to the operational MCC function via a local DC function for the provision of
the mission configuration required as reference for testing and validation activities.
5.2.4.6 Collaboration Support Service (CSS) Function
5.2.4.6.1 Function Objectives and High-Level Description
The CSS function is primarily aimed at providing technical support vis-à-vis the collaborative
PDGS peers according to the needs of each type of collaboration expressed in sections
4.10.2.1 and 4.10.2.2, based on collaboration agreement between the peer entities and the
POM.
In addition, it is responsible for liaising with the POM for the definition of the collaborations
and to provide associated progress reports during implementation as defined in section
4.10.3.2.4.
ESA UNCLASSIFIED – For Official Use
© ESA
The copyright of this document is the property of ESA. It is supplied in confidence and shall not be reproduced, copied or
communicated to any third party without written permission from ESA.