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 319 of 350
○ System Updates
○ Hardware replacement/deployment
○ Mission Configuration validation
○ System configuration reporting
○ Operator Training
6.18.3.1 System Anomaly Management
During operations the PDGS operators will detect problems, (i.e. an anomalous behaviour of
the system) and will use the RP function for the anomaly management. The RP operational
scenario will be triggered by the reception of an anomaly and the following steps are identified
for:
1) Reception and handling of SW problems into the dedicated anomaly database.
Anomalies are entered with all foreseen and defined attributes (e.g. criticality, referred
PDGS subsystem, etc…);
2) Anomaly is investigated on RP environment at sub-system level (see sub-system test
activities). If it can be reproduced, jump to point 6;
3) If anomaly cannot be reproduced a hardware problem may be suspected. Investigation
is performed and if verified jump to scenario hardware replacement/deployment;
4) For system-level anomalies, end-to-end system-test will be performed on RP
environment (see system test activities) with a reference-qualified configuration and
with an operational MCC configuration to investigate anomaly at system level;
5) If anomaly cannot be reproduced a hardware problem may be suspected. Investigation
is performed and if verified jump to scenario hardware upgrade;
6) Once anomaly is identified system or sub-system maintenance actions are triggered
accordingly;
7) On availability of new system or sub-system deliveries correcting the problems, see
system updates scenario.
6.18.3.2 System Updates Management
The availability of new PDGS Release can be considered as a recurrent operational scenario.
It is worth noting that it is necessary to define in advance policies to decrease, as much as
possible, global risks.
Apart to the first delivery of an item that simply marks the start of its availability for the testing
phases, new deliveries are possible as a consequence of two different situations:
○ New releases due to scheduled successive deliveries
○ Unscheduled release due to a previously detected anomaly
The System Updates scenario will be triggered by the reception of a new PDGS Release and
the RP operator will require and receive from the MCC function the last PDGS configuration
version to run the tests.
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.