(2019-01-09) Point d'avancement operations RPW #12 (RPW+CNES+MOC)

• Concerned TM checks must be only those via OMM and not via SSMM
• The TM checks will be done manually, an operator will have a PDF with the instructions.
• The instructions will be written in the FOP.
• A specific procedure is needed for the TM checks to be applied after block 1. The PDORs corresponding to each block will be put under conf control. They will be called in the specific system procedure for deployments.

  Note: it would be good if the PDOR name contained the block ID!

  The flight rules (an other part of the FOP) for the deployments need to contain unambiguous rules about what to do with RPW in case of unexpected TM check, OOL or received non nominal event.

• The check for TM packets (on top of TM parameters) can be done easily
• Regroup all the TM checks after the switch on and not during deployment activities or switch on.
• FDIR settings (enabled!)  must be checked at switch on of RPW to make sure RPW is well protected.
• If non-nominal event occurs (but in FDIR boundaries), RPW has to tell MOC what to do. For example, MAG decided to stay ON until the end of deployment, whatever
• Those TM checks can be tested during SVT1A
• To switch on SCM, the temperature has to be increased, which takes ~15 min → RPW will change the temperature at the beginning of switch on, and during the increasing, will switch on all others sub-systems in ordre to switch on SCM 15 min later.

• Blocks presented in slide 2 are ok until SL details the deployments activities.
• 1 Block corresponds to 1 PDOR with delta times (release times). SL is able to transform those delta times in absolute times once the deployment planning is known.
• RPW insists on the importance to run the blocks right before or after the deployment without gap hours. If such gap are foreseen, RPW might cut the blocks to be more flexible.
• In case of stop during deployment activities, RPW can stay switched on one day or more.
  
  

• As blocks have been validated for now as in slide 2, the timeline for SVT1 test remains.
• To test the deployment timeline, TM checks can be sent by email or excel file.
• DB has 4 more sequences to send to SL
• Timeline 1.3 (see attached file) is validated
• We might be able to test the whole data retrieval process

DB : Send missing sequences to SL

MDOR sent by Xavier are ok.

The SW upload may take place post SVT1b and be executed via MOC.
For that we'll need the relevant MDORs as well as the high level patch procedure.
As soon as the MDORs are ready, please pass them on so that we can validate that part already (ie process the MDORs and send back to you for approval).

As software updates are ready for RPW, we must discuss with Airbus and insist on the necessity to perform the update before flight (updates are needed for deployment activities).