The LCC is in charge of the supervision of:
- LCC operations (operations schedulling, computer health monitoring, etc.),
- operations with the external interfaces (SONC, RMOC, RSOC, PIs).
This function is in charge of displaying to the public the main results/operations/information of the project.
Once a Lander telecommand has been defined, and before sending it to RSOC for uploading, the LCC will simulate/validate the telecommand in order to make sure that these plans may have the expected results (in terms of resource consumption, operations, etc.). The telecommands are executed in order to be sure that the plan is safe for the Lander regarding the resources (energy, power, memory, etc.) and the system (operations compatible with the system constraints).
The Rosetta Lander platform and payload operations know-how has to be maintained during the entire Rosetta Mission. Appropriate measures will be established to satisfy the following functional requirements:
- upkeeping the existing Lander project document database,
- parallel ground reference laboratory programmes and intermediate scientific programmes.
The Lander is designed to be fully automatic.
During the activated cruise operations, a plan is uplinked to the Lander and executed automatically. The status of the execution of the plan will be known using telemetry.
For the delivery and on-comet operations, a preliminary plan is on-board the Lander from launch, taking into account the current knowledge for the scientific operations (comets, experiment functioning, Lander resources, etc.). This plan will certainly be changed via telecommand uploading, with regards to the status of the Lander (platform and experiments, orbiter, etc.) and the landing site descent trajectory definition. This plan will then be executed automatically by the Lander during descent and on the comet, using its own resources (power, energy, memory, etc.).
Lander resource allocationThe LCC will allocate resources (power, energy, data volume) for the operation change requests (the following week or days depending on the mission phase) taking into account the status of the Lander platform and other constraints such as visibility period, sunshine, etc. The resource allocation will affect both the experiments and the subsystems.
Lander short loop operation plan elaboration
The LCC allocates resources (power, energy, data volume) to the subsystem. It will be in charge of:
- maintaining the database on the subsystems operations (and associated constraints, resources, etc.) for each subsystem,
- inside the resources allocated, defining the subsystem scenarios with the associated constraints (Orbiter parallel operations, duration, etc.) in collaboration with the Rosetta timeline, regarding the results of the parameter monitoring and display,
- translating subsystem scenarios in macro-commands,
- developing the Rosetta Lander plan.
Lander long loop operation plan development
This loop, in addition to the close one, implements the necessary scientific operation plan given (by the SONC) in an overall Lander operation plan.
Lander TC request development
The Lander operations plan has to be sent to the Lander. The LCC is in charge of translating the plan in macro-commands in the format of TC requests.
These Lander Operations requests are then sent, after validation, to RSOC using the transmission function.
Verification of the RSOC and RMOC on the Lander telecommand
After having received the LOR (Lander Operations Request), the RSOC may verify it (TBD), regarding resource allocation (mainly when the Lander is attached and consumed orbiter resources). Then the LOR is sent to the RMOC which will process it for integration into CCSDS TC format.
In some urge cases, the LOR may be directly sent from RSOC to RMOC without verification at RSOC level.
Before uploading, and when there is enough time (off-line process), in order to be sure that no errors have been integrated by this "translation", the TC formatted by RMOC (format TBD) are sent to LCC for verification (using the ground reference model if necessary) before uploading.
Lander subsystems telemetry processing
The LCC will process all the critical parameters for the Rosetta Lander mission (coming from subsystems and also some from experiments).
- It sorts the SFDU by subsystems (one APID per subsystem),
- and it produces the physical parameters to monitor.
Lander data monitoring and display
The LCC will take into account the Rosetta Lander critical data in order to monitor the status of the Lander mission.
- It applies a monitoring plan on the critical data, having a status of each subsystem health (and experiment if needed).
- It displays the data with the results of the monitoring (red/green/orange lights, etc.).
- It writes a Lander subsystems quick-look status report.
Lander data off-line processing
The Lander is activated during different mission slots (commissioning, activated phase during cruise, pre-delivery phase, descent and on the comet). The LCC will take care of the evolution of the Lander platform data (coming from processed and archived data). This may imply modification of some telemetry transfer functions.
This function is in charge of the LCC operational interfaces:
- It acquires the data sent by RMOC (Lander housekeeping telemetry, Rosetta mission plan, Rosetta mission status, auxiliary data) and SONC (Lander experiments operation plan) using the defined interfaces.
- It transmits all necessary data from the LCC to RSOC (Lander Operations Request), to RMOC (Lander status synthesis), and to the SONC (Lander experiment resources, Lander status).
- It manages all the telecommunication means (data links, video, audio, etc.) to support the operational co-ordination with the other centres.
The LCC is the interface with the Rosetta Lander platform suppliers. It will offer the following services:
- access to the Rosetta Lander platform health, the subsystems telemetry (raw and processed),
- parameters processing request,
- subsystem operations request.
All these services will be protected with an access code for each user. All users will not have access to all the services.
For high phases, the subsystem suppliers must be co-located at the LCC.
All the data and information produced and received by the LCC are archived during the whole mission (nearly 11 years). The main ones are:
- raw Lander telemetry,
- Lander subsystems operations plan.
The archiving is done automatically. The access is done based on criteria (time, parameters, etc.). The corresponding catalogue is updated and maintained all along the mission.
This database must be compatible with the SONC one. This means that:
- both databases shall provide a similar interface and the same functionality to an external user,
- both databases shall provide the same set of data.
This doesn't affect the internal type, structure, and design of the database.
After a certain period (6 or 12 months TBD), the Lander's calibrated data must be provided in PDS format (Planetary Data Structure) to RSOC for public access.