Abstract
| To complete its mission, the Run3 Installation Coordination team needs a tool to centralize and collect, at a macroscopic scale, all activities to be performed in the programmed stops for Run3 and LS3, including those postponed from LS2. The LS2 experience and the similarity of needs made the PLAN tool the obvious choice to fulfil this function. It was created with a precise LS1 scope,used during LS2 and even if the goals/needs are similar, the PLAN tool was not developed to easily include a new PLAN or be adapted ; significant changes therefore had to be defined, planned, and developed within the constraints defined by the Run3 programmed stops and LS2 completion. The transition from LS2 to this new period, and the support given in that transition, help to understand some of the reporting difficulties, some of the user needs, and lead to the introduction of two new PLAN stages and training sessions for users. Ensuring data continuity, simplifying the tool based on the LS2 users feedback, stage development and availability of the tool for users while developing in parallel were and are the key principles applied in the evolution of the tool. Overcoming some of the known issues, the new challenges presented by this new PLAN, and the open communication with the users to understand the usage are key to define the tool evolution in the coming years to make it more flexible for the future, improving data quality and reducing support needs. |