90 likes | 227 Vues
This document outlines the operational planning and control systems for conducting dry runs during the EIS testing phases, specifically with inputs from Marine and Marc. It details a structured 5-day schedule from Monday to Friday, including preparation, testing, and debriefing sessions for BE-CO roles. It emphasizes the importance of collaboration between CO, OP, and EQP teams, along with necessary refinements in the planning phases to ensure smooth execution. The need for defined checks during the Cold Check Out period is also highlighted to streamline the process.
E N D
Operational planning with Control System DRY RUNS Claude Dehavay Thanks to inputs from Marine & Marc
BE-CO Dry run in the Injector schedule 5 working days Period MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY AM PM AM PM AM PM AM PM AM PM Preparation 1 BE-CO Test 1 Debriefing/Debugging/Consolidation Preparation 2 BE-CO Test 2 Debriefing Week 7, 8 + 10: individual EIS tests Week 11 & week 14: global EIS tests -> all EIS available
BE-CO roles during the Dry Run 5 working days Period MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY AM PM AM PM AM PM AM PM AM PM Preparation 1 BE-CO Test 1 Debriefing/Debugging/Consolidation Preparation 2 BE-CO Test 2 Debriefing + ACCOR Project Leader
Final remarks • CO, OP &EQP close collaboration required • Dry Run (DR) planning to be now consolidated and refined with EQP groups + OP • Need to anticipate DR in HWTESTS as Cold Check Out (CCO) period too short • List of checks during CCO to be defined by OP • Organizationof DR: Same as for pilot DR: wiki + Jira issues for each pre-requisite + each check