GSC Sentinel-2 PDGS OCD - Emits - ESA

More documents

Recommendations

Info

ESA UNCLASSIFIED – For Official Use GSC Sentinel-2 PDGS OCD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-TN-09-0008 page 318 of 350 2) As needed by the tests selected, a reference-qualified system-level configuration is assembled on the RP environment to simulate the relevant PDGS system-level context required to perform the tests. For instance, the RP environment will be configured as a CGS to validate a new version of the front-end-processor in integration; 3) The required mission configuration will be retrieved from the MCC as relevant and installed on the RP environment if not already available; 4) Whenever the tests are intended to validate new or upgrade systems, a new RP development configuration will be created with the new /upgraded systems replacing their old versions. At this point, the RP will be ready to support subsystem tests, either in reference-qualified or in the so-created development-configuration. 5) System tests are performed and are reported upon as relevant As regarding the validation in integration of newly upgraded sub-systems (e.g. following corrective maintenance or evolution activities), one or several adequate system-tests will selected according to the specific role assumed at functional and/or physical level of the upgraded element(s) within the PDGS. 6.18.1.5 Sub-System Level Testing In case a new PDGS Release which affects just a specific PDGS subsystem will be provided, the Sub-System Level Testing activity will be executed, by using the requested RP scalability. The overall operations sequence for this activity can be summarised as follows: 1) Analyse new PDGS Release documentation in order to identify PDGS subsystems affected by the new PDGS version 2) Select one or several documented IV&V subsystem test procedures according to the testing coverage required. 3) Subsystem tests are performed and are reported upon as relevant 6.18.2 OPERATION CONSTRAINTS The Reference Platform plays a primary role during the PDGS IVV (Integration, Verification and Validation) activities, but the scope of the current section is to identify and describe the RP operational scenarios in the PDGS operation phases, when PDGS system has been already deployed on-site (on PDGS Facilities target platforms) and has been validated for pre-operations. All other specific testing guidelines regarding the Reference Platform will be described under the PDGS IVV Plan. 6.18.3 OPERATION SCENARIOS The following operational scenarios descriptions provide a step-wise decomposition of the various RP activities, referring to the previously defined RP activities as relevant. The proposed RP operational scenarios are: ○ System Anomaly Management © 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.
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.
Page 1 and 2:
document title/ titre du document P
Page 3 and 4:
GSC Sentinel-2 PDGS OCD issue 1 rev
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
[RD-33] Sentinel-2 MSI - Level 2A A
Page 35 and 36:
Page 37 and 38:
LES LGS Land Equipped Sites Local G
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
3.5.2 MULTI-SPECTRAL INSTRUMENT CHA
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
ESA UNCLASSIFIED - For Official Use
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Table 4-5 Radiometric image quality
Page 99 and 100:
Product- Type On-Line retention Off
Page 101 and 102:
Page 103 and 104:
4.5.1.5 Scalability and Flexibility
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
4.6.3 OPERATIONAL TRANSFER BASELINE
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Product- Type Identifier S2MSI0 S2M
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
5 PDGS DESIGN GSC Sentinel-2 PDGS O
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
○ Effective processing resources
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
o preserving integrity of exchanged
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
6 DETAILED OPERATIONS CONCEPTS GSC
Page 245 and 246:
o Report generation frequency and c
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
○ MSI L1A, L1B, L1C and TCI produ
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 277 and 278: ESA UNCLASSIFIED - For Official Use
Page 289 and 290: Some relevant use cases are present
Page 313: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 325 and 326: Two main mapping services have been
Page 327 and 328: The requirement on the cloud covera
show all

GSC Sentinel-2 PDGS OCD - Emits - ESA

Create successful ePaper yourself

Delete template?

Save as template?