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 190 of 350<br />

4.10.2.2.3 Service Dependencies and Constraints<br />

Service dependencies are described here such as eligibility constraints and the management<br />

of Intellectual Property Rights (IPR) inherent to the collaborations.<br />

4.10.2.2.3.1 Eligibility<br />

Eligibility to the service will be managed by the POM through the detailed definition of<br />

collaboration agreements applicable to this type of collaboration.<br />

The following general constraints will drive eligibility to the hosted-processing service:<br />

○ The <strong>Sentinel</strong>-2 product set available as basis for higher-level processing through the<br />

hosted-processing service includes solely the S2MSI1C product-type;<br />

○ Additional auxiliary data required by the hosted-processor will have to be agreed upon<br />

as part of the collaboration set-up and be at minimum supported by an operational<br />

third-party electronic data provision service;<br />

○ The product classes supported as candidate value-added products to be generated<br />

through the hosted-processing service are <strong>Sentinel</strong>-2 only Level-2 and Level-3 classes<br />

of products. Level-3 products include mono-mission or multi-mission compound<br />

products aggregating the data of a single or several <strong>Sentinel</strong>-2 spacecrafts;<br />

○ The user-processors will have to be pre-existing, tested and portable to the supported<br />

<strong>PDGS</strong> computing platforms;<br />

○ For eligibility to the systematic hosted-processing service, the value-added product<br />

model will have to comply with a well-defined model inherited from the core product<br />

model defined in [RD-07] allowing a swift integration via the generic product handling<br />

mechanisms implemented by the <strong>PDGS</strong>.<br />

4.10.2.2.3.2 Intellectual Property Rights Management and Licensing<br />

The Intellectual Property Rights (IPR) over software and algorithms held by the collaboration<br />

peer entity will not be altered in any way by the collaborative opportunity.<br />

As far as the use of third-party software and algorithms is concerned, the peer entity will be<br />

fully responsible for requesting the necessary authorizations and/or licenses when<br />

appropriate.<br />

To sustain the operations of the systematic hosted-processing service as described under<br />

service evolutions, the peer collaboration entity will have to grant to the POM an adequate<br />

usage license allowing for a long-term exploitation of the hosted-processor within the <strong>PDGS</strong>.<br />

The licensing of the resulting collaborative products will in principle be managed by the<br />

collaborative entity and will be documented in the collaboration agreements.<br />

4.10.2.2.4 Triggering Mechanism and Interface<br />

For the preliminary processor integration step, the service will be managed through a<br />

dedicated Collaboration support <strong>PDGS</strong> function. Please refer to section 5.2.4.6 for an outline<br />

description of this function.<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!