GSC Sentinel-2 PDGS OCD - Emits - ESA

More documents

Recommendations

Info

GSC Sentinel-2 PDGS OCD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-TN-09-0008 page 312 of 350 Every PDGS centre will be in charge of performing its Monitoring & Control activities over its own deployed elements. All the elements required for the every centre local operations will be accordingly under surveillance. In case of any failure or malfunction, each the local support teams will be the problem/solving investigation front-line. Therefore the M&C function will be deployed into every federated centre customised for the role and the associated functions locally present. 6.17.1.2 Horizontal Support to other PDGS functions The PDGS Monitoring & Control function will support other PDGS functions in the already described activities on execution environment monitoring. In addition, M&C function will be the hub of all PDGS functions logging activities. The M&C function will be flexible enough to cope with the different environment executions the different PDGS functions may require. Nowadays the M&C solutions are pretty standard and independent from the business domain (e.g. used in ground systems, in banking activities, and so on). The chosen M&C solution will be able to adapt to any other PDGS function execution environment. Many currently available M&C solutions allow such adaptation by configuration tailoring and/or specific modules. 6.17.1.3 Client-Server Paradigm The M&C function will interact with other PDGS functions using a client/server paradigm. Different M&C artefacts (i.e. monitoring agents) will be deployed on every PDGS function platform to gather the relevant monitoring information and serve it to the M&C function serve side (i.e. the M&C console) for comprehensive presentation to the operator. The M&C agents gathers the relevant information according to configuration and send it to the M&C control panel, as such providing a global status to the operator and alert when required. Analogously, logs are managed by the M&C function as received from others; The PDGS functions will usually make use of a log client library for log messages delivery towards the M&C log server for comprehensive and centralised visualisation. 6.17.2 OPERATION CONSTRAINTS The following operation constraints are identified: ○ Minimum operator intervention: The PDGS M&C function will only require operator intervention on critical errors and will be alerted accordingly; ○ Maximum synergy with the Data Communications Operations on digital networks to allow an overall Monitoring & Control of the PDGS network end-to-end. 6.17.3 OPERATION SCENARIOS 6.17.3.1 M&C Artefacts Configuration This scenario describes the M&C artefacts deployment and configuration on each centre. Every time a new PDGS function is deployed on a given centre, new HW platforms are 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 313 of 350 installed, new network interfaces are used; the appropriated M&C artefacts are configured by the operations team. The following steps are identified for this operation scenario: 1) The configuration of the M&C agents: they are usually installed on the same platform to the new monitored elements. The M&C agents configuration typically includes the monitoring of the system processes status, the CPU usage, memory usage, network connectivity, bandwidth usage, disk usage, etc; 2) The configuration of the alarms notifications in response to the M&C raised events; 3) The logs configuration including the information sent (i.e. filtered by log severity), formatting issues, etc; 4) The configuration of the M&C console (server side) to adapt to the specific centre work-flows; 5) The configuration of the M&C central log tool (server side). This scenario is used when new PDGS functions are deployed in a given centre – The M&C artefacts will be accordingly configured with respect to the new PDGS functions and their HW platforms deployed in. 6.17.3.2 Coordination with Data Communication Operations The M&C function will define the necessary interface, both at technical and procedural levels, to coordinate with the Data communications Operations Centre (cf. section 6.20) for troubleshooting purposes. In particular the Monitor & control function will be able to access reports and monitoring statistics of the Data communications Operations function. 6.17.3.3 Monitoring & Reporting on the Execution Environment This scenario stands for the autonomous monitoring activities performed on every PDGS centre. The operator intervention is reduced to acknowledge the monitoring information when required (e.g. alarms). The M&C function will autonomously monitor the execution environment of the centre locally deployed PDGS functions. In case of function failure, HW / network failures, disks errors, network downtime, bad memory / CPU resources allocation, the M&C function will allow a prompt detection and the tracking of the relevant information needed to identify the source of problems. The following steps are identified for this operation scenario: 1) Monitoring data gathering via agents. The M&C agents perform systematic data monitoring gathering activities according to the configuration; 2) Raising of alarms according to the agents gathered data. In case of execution deviation with respect to the configuration (e.g. log message received with severity as ‘Fatal’); 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: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 261 and 262: ESA UNCLASSIFIED - For Official Use
Page 289 and 290: Some relevant use cases are present
Page 307: ESA UNCLASSIFIED - For Official Use
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?