29.11.2014 Views

GSC Sentinel-2 PDGS OCD - Emits - ESA

GSC Sentinel-2 PDGS OCD - Emits - ESA

GSC Sentinel-2 PDGS OCD - Emits - ESA

SHOW MORE
SHOW LESS

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>GSC</strong> <strong>Sentinel</strong>-2 <strong>PDGS</strong> <strong>OCD</strong><br />

Issue 1 Revision 2 (draft) - 25.07.2010<br />

GMES-GSEG-EOPG-TN-09-0008<br />

page 196 of 350<br />

○ a system-level functionality expected to be translated into an automated behaviour of<br />

the <strong>PDGS</strong> through actual systems but which is intentionally left at system-level to<br />

maximise the opportunity of fulfilling it by reusing aggregate or customisable existing<br />

solutions;<br />

5.2 Functional Model<br />

This section describes the decomposition of the <strong>PDGS</strong> overall functionality into<br />

complementary high-level primary Functions.<br />

5.2.1 DESIGN LOGIC<br />

Based on the overall design rationale presented in the previous paragraph, the functional<br />

decomposition aims at defining a logical split of the <strong>PDGS</strong> overall required functionality into<br />

primary Functions which can optimally be distributed across centres to globally implement the<br />

operation baseline of the <strong>PDGS</strong>. As such, the functional breakdown comprehensively aims at:<br />

○ Providing a first-level layout of primary Functions each one solving part of the problem<br />

in coordination with others in a logical way;<br />

○ Providing a clear basis for the definition of operation concepts at Function-level that<br />

logically aggregate at system-level in responding to the <strong>PDGS</strong> baseline services;<br />

○ Isolating Functions in view of optimising the logical-to-physical mapping into macrofunctional<br />

roles for the definition of <strong>PDGS</strong> Centres;<br />

○ Isolating Functions according to typical existing market solutions that can be reused in<br />

parts or entirely from previous <strong>PDGS</strong> developments, while concentrating the<br />

specificities of the <strong>Sentinel</strong>-2 <strong>PDGS</strong> into other dedicated Functions;<br />

○ Providing a clear view over the envisaged enhancements compared to previous<br />

developments, to meet the particular challenges of the <strong>Sentinel</strong>-2 mission;<br />

○ Ensuring the functional blocks can be clearly associated to their key design-drivers in<br />

view of their implementation;<br />

○ Embedding the required flexibility and scalability in the design in view of the distributed<br />

but yet unknown physical layout of the <strong>PDGS</strong>;<br />

Following a first section defining the breakdown, each identified function is then separately<br />

detailed with its specific objective, design-drivers and logical interfaces to the other functional<br />

blocks. The design rationale pertinent to each function group or function is described recalling<br />

the source operation constraints and drivers of section 4.3. Specific relevance to the <strong>PDGS</strong><br />

operation baseline definitions outlined in chapter 4 is also pointed out.<br />

5.2.2 FUNCTIONAL BREAKDOWN<br />

The first-level of the <strong>PDGS</strong> functional decomposition discriminates between Data<br />

Management functions, System Control functions and Data-Communication functions.<br />

<strong>ESA</strong> UNCLASSIFIED – For Official Use<br />

© <strong>ESA</strong><br />

The copyright of this document is the property of <strong>ESA</strong>. It is supplied in confidence and shall not be reproduced, copied or<br />

communicated to any third party without written permission from <strong>ESA</strong>.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!