GSC Sentinel-2 PDGS OCD - Emits - ESA

More documents

Recommendations

Info

1) New PDGS Release is received and put under configuration control; GSC Sentinel-2 PDGS OCD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-TN-09-0008 page 320 of 350 2) The effective availability date of a given Test Item will include the preliminary activities of installation and configuration on the RP; 3) A development configuration will be set-up on the RP to simulate the relevant PDGS context required to perform meaningful tests with the upgraded element(s); 4) System test activities will be performed on RP environment (see system test activities). Anomaly(ies), planned to be closed, will be verified and in case of unsuccessful scenario the anomaly management scenario will be executed; 5) Otherwise the validated development configuration becomes qualified and candidate for deployment; 6) Decision will be made to deploy upgraded system, and TTO (Transfer to Operation) action will be performed deploying the new reference-qualified configuration as preliminary configuration; 7) Preliminary-configured system is monitored in operations at PDGS facilities, anomalies planned for closure are tested for and reports will be used by RP operator for the final assessment on the anomaly management database (see anomaly management activities); 8) Possibly if new critical problems arise, the RP operator will decide to roll-back to previous RP configuration for reproducing problems and execute the anomaly management scenario. Otherwise the deployed preliminary configuration becomes the new operative configuration. 6.18.3.3 Hardware Replacement/Deployment The PDGS System will take into account scheduled or not evolution that could affect the HW configuration due at least to following factors: ○ HW updates due to S2B deployment ○ HW configuration due to EDRS integration ○ Network replacement ○ HW migration and/or upgrades PDGS HW design should be driven by an evolution approach and the RP function can help in monitoring and controlling the PDGS HW system inventory. The RP scenario will be triggered by the reception of a new PDGS CIDL (Configuration Item Data List) documentation, which provides the HW and SW environment and full set of application SW that constitutes the new PDGS Release. 1) RP operator receives a new PDGS CIDL; 2) The New PDGS Release is put under Configuration Control; 3) Verification of new HW platform, detailing all new HW items that are foreseen to be deployed on the PDGS target platforms; 4) RP operator will execute the RP HW Inventory activities; 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.
GSC Sentinel-2 PDGS OCD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-TN-09-0008 page 321 of 350 5) The upgraded system is inventoried in the RP environment for nominal inventory and configuration-control; 6) RP operators will provide a summary report of HW items that constitute the new PDGS Release. 6.18.3.4 Mission Configuration Validation Current scenario will be used by the MCC operators before deploying new critical mission configurations. It is reasonable to foresee possible improvements and implementations of the PDGS System (due to e.g. S2B system upgrades, EDRS integration, Network updates, failures managements, etc…). The MCC operator can request to the RP operator to exercise, simulate and test a new mission configuration by opportunely setting-up and using the RP. It corresponds to running an appropriate scenario on the RP environment using the specific MCC configuration dataset (e.g. files and parameters) to be validated with the referencequalified configuration (see system-test activities): 1) The MCC operator requests to the RP one to validate a specific and pre-defined mission configuration; 2) The RP operator receives the new mission configuration files and parameters and performs a RP set-up; 3) Depending on mission configuration items the RP operator will execute the system or sub-system test activities; 4) In case of raised anomalies the RP operator will run the system anomaly management scenario; 5) Once the testing activities will be completed a mission configuration validation report will be sent to MCC operators; 6) The MCC operators can request to RP operator to run the System Updates scenario. 6.18.3.5 System Configuration Reporting The scenario is activated on-request by the RP operator for historical reporting on the system baselines changes, providing traceability with reported/corrected anomalies (and possibly to the affected system requirements) as well as traceability along time of the configuration changes throughout system baseline evolutions. This scenario is based on the following same steps: 1) The RP operator generates a report including the exhaustive description of the current PDGS HW and SW baseline; 2) The RP operator generates a change-log report on a specific sub-system, providing its current and past versions with the list of problems raised and resolved after each version. 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:
Page 265 and 266: 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 315: 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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?