002842635 001__ 2842635
002842635 005__ 20221130203614.0
002842635 0248_ $$aoai:cds.cern.ch:2842635$$pcerncds:FULLTEXT
002842635 037__ $$aCERN-ACC-NOTE-2022-0040
002842635 041__ $$aeng
002842635 100__ $$0AUTHOR|(CDS)2067903$$0AUTHOR|(SzGeCERN)652506$$aBaltasar Dos Santos Pedrosa, [email protected]$$uCERN
002842635 245__ $$aPLAN Tool
002842635 260__ $$c2022
002842635 269__ $$aGeneva$$bCERN$$c11 Oct 2022
002842635 300__ $$a3 p
002842635 520__ $$aTo 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.
002842635 595__ $$aCERN EDS
002842635 595__ $$zUNCL
002842635 65017 $$2SzGeCERN$$aEngineering
002842635 65017 $$2SzGeCERN$$aAccelerators and Storage Rings
002842635 6531_ $$9CERN$$aCoordination
002842635 690C_ $$aCERN
002842635 690C_ $$aINTNOTE
002842635 690C_ $$aPUBLATS
002842635 700__ $$0AUTHOR|(CDS)2722067$$0AUTHOR|(SzGeCERN)848125$$aMasterson, [email protected]$$uMinistere des affaires etrangeres et europeennes (FR)
002842635 700__ $$0AUTHOR|(CDS)2051132$$0AUTHOR|(SzGeCERN)511509$$aTock, [email protected]$$uCERN
002842635 700__ $$0AUTHOR|(SzGeCERN)484626$$0AUTHOR|(CDS)2051125$$aDaudin, [email protected]$$uCERN
002842635 700__ $$0AUTHOR|(CDS)2067680$$0AUTHOR|(SzGeCERN)397795$$aKlem, [email protected]$$uCERN
002842635 700__ $$0AUTHOR|(CDS)2320539$$0AUTHOR|(SzGeCERN)831049$$aLanza, [email protected]
002842635 710__ $$5ATS
002842635 710__ $$aCERN. Geneva. ATS Department
002842635 859__ [email protected]
002842635 8564_ $$82410875$$s128369$$uhttps://cds.cern.ch/record/2842635/files/CERN-ACC-NOTE-2022-0040.pdf
002842635 916__ $$sn$$w202248
002842635 960__ $$a12
002842635 963__ $$aPUBLIC
002842635 980__ $$aINTNOTEATSPUBL
002842635 980__ $$aNOTE