GSC Sentinel-2 PDGS OCD - Emits - ESA

GSC Sentinel-2 PDGS OCD
Issue 1 Revision 2 (draft) - 25.07.2010
GMES-GSEG-EOPG-TN-09-0008
page 299 of 350
Test new planning configuration not previously used for the mission plan generation.
During the commissioning phase, it is likely to increase MSI load progressively by
addition of new observation and calibration rules or by the modification (relaxing) of
some constraints modelled in the SSCF;
Re-planning generation. In case it is needed to re-plan due new specific calibration
operations to be added, change of downlink priorities, etc;
New manual planning generation after “failed” automatic planning (mission plan
rejected by the FOS).
6.15.3.3 Automatic Mission Plan Generation
According to the PDGS/MPL function configuration, the mission plan will be generated
automatically on a predefined schedule basis. This scenario accounts for the automatic
mission planning generation according to the operational duty cycle established with the FOS.
The following steps are identified for this operation scenario:
1) The MPL function autonomously triggers the mission plan generation according to
schedule configuration (i.e. typically every 2 weeks);
2) The MPL function autonomously takes current applicable inputs (e.g. observation plan,
calibration plan template, SSCF, etc.);
3) The MPL function autonomously identifies the next planning period (i.e. planning start
and stop, typically 15 days) according to configuration and the previous planned
period;
4) The MPL function generates the mission plan autonomously according to the SSCF
and compatible with the FOS operation constraints defined in section 4.3.7.1;
5) The MPL function autonomously optionally notifies to the ground-stations based on a
configurable time the downlink passes required in advance (i.e. pass-list) to support
the generated Mission-Plan;
6) In case any error happened during the planning generation, the operator is alerted
(e.g. via SMS or email). If planning is successful the operator is reported accordingly
(e.g. report delivery via email).
This scenario can be used once the configuration planning has been consolidated and
already proven in real operations.
6.15.3.4 Planning Loop Closure
This operation scenario is part of the nominal working-flow with the FOS as part of the
mission planning activities. Every time a new mission plan is generated and delivered to the
FOS, the latter performs the satellite safety checks and generates a PIF in response to such
mission plan. The PDGS/MPL verifies that all planned activities have been scheduled by the
FOS.
This operation scenario hence accounts for the automatic planning loop closure although it
may be as well triggered manually by the operator.
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.