Marine Pace on behalf of the ACCOR team IEFC 8 th Feb 2013 Acknowledgements:

1. Statuson LHC Injectorsrenovationorganisation to face the challenge of LS1 dry runs and commissioning Marine Pace on behalf of the ACCOR team IEFC 8th Feb 2013 Acknowledgements: C.Dehavay, E.Hatziangeli, M.VandenEynden, Machine Controls Coordinators

2. Outline • Context reminder • Organization • After LS1 commissioning • Current status and next step • Main actors

3. Context of Controls Renovation • LS1 = unique opportunity for major renovations • BE/CO is the driving force • Significant number of renovations -large scale - critical impact - • LynxOS, CAMAC, SLEQUIP : targets for eradication • 1900 devices (TIMING – no TG8 left) 1500 (PCs) 400 (function generators) • Critical domains: TIMING, POWER, RF , KICKER,… • Renovations to be synchronized between CO and EQP groups • Operational constraints • LHC planning • Lin3+4, CTF, REX running in LS1 • Special care to commissioning time • Lessons learnt from 2012 experience

4. Context of Controls Renovation -2 • Transfer of Front-End (FE) responsibility from CO to EQP Groups • Unify responsibility model (LHC model) • FEC go under EQP GP responsibility • Except those 100% BE/CO made (timing, OASIS,…) • Imply FE re-organization, knowledge transfer • Deploy the new exploitation operational support model at 2014 startup • First line support will be EQP GP for all renovated FE except pure BE/CO FE • Responsibility discussed and agreed by EQP Groups • Special case of FE not renovated

5. BE/CO organization • A formal approach is required • Large scale renovation: ± 200 FE • Synchronization with other LS1 activities • RENOVATION planning is one [big] component of the global BE/CO planning -> next slides • Close collaboration with OP and EQP groups along the whole renovation from design to commissioning

6. BE/CO LS1 planning Main components • ACCOR : RENOVATION requests for all accelerators • BE/CO other activities : maintenance, upgrade of services • BE/CO contributions required by others • Lin3, CTF3 operation=> exploitation • EN-STI: RADMONs in PS, FIP qualification => Installation C.Dehavay courtesy

7. ACCOR in BE/CO planning https://edms.cern.ch/document/1223926/1 ACCOR C.Dehavay courtesy

8. Renovation process Formal Specification --------------------- Technical specif Responsibilities Workpackage breakdown CO DEFINE RENOVATION Agree on technical solution DEFINE COMMISSIONING TIME Approve specification Schedule Dry runs FINAL Tests planning 2014 SCHEDULE ------------------------ BE/CO Dry Runs PRODUCE RENOVATION PLANNING HW Procurement & Installation SW development & integration LS1 PLANNING Deployment - HW Tests OP Commissioning Accelerator Schedule 2013 Transfer operational support to EQP groups

9. After-LS1 Commissioning : special care • Lessons learnt from LEIR/Linac3 2012 experience • Not thorough enough BE/CO validation before deployment -> During LS1, TESTBED put in place for core components, special focus on testing • Too short CO commissioning time requested • Over-confidence: we believed that systems validated on other machines would work right away on LEIR/LN3 • Commissioning done by CO on its own, with expert tools • Lack of efficiency in the deployment process • Enhancements & automation scheduled in LS1

10. After-LS1 Commissioning: proposed organization • A 3-phase commissioning (LHC model) • HW TESTs: integrity check of CO component • DRY RUNs (no beam): eqp switched ON, timing ON • BEAM TESTs: nominal conditions available • Time requests to be agreed at Commissioning Planning meetings • Commissioning slots will appear in the official 2014 schedule • Dry runs and Beam tests • Global supervision by OP • OP-CO-EQP joint effort required • High availability of all CO experts • Role of MCC Leader fromCO: • Ensurethateach validation getsapproved by OP • Organize the hand over to operations Time for final tuning Time for fix / repair

11. Commissioning planning preparation • Commissioning planning meetings are called by BECO • ACCOR project leader (chairman) • MCC & LS1 CO Planning officer • EQP GROUP linkpersons for ACCOR • OP GROUP linkpersonsfor ACCOR • Objectives • Reviewrenovationspecification document (final or preliminary EDMS) and build a formal GO or NO-GO amongst all parties • Present dates for hardware installations • Define dry-runs (who, when, conditions, duration) • Propose a new operationalscheduleincluding dry runs • Current status -> in 2 slides

12. Currentstatus • Technical meetings to discuss renovation solutions almost completed • Process started months ago • Significant workload ± 200 FE • Difficulties met: • FEC responsibility transfer • Uncertainty from EQP groups on renovation planning • Intermediate renovation by CO to secure FE waiting for final renovation by EQP group • Detailed specification of renovation plan per FE • Status AD: EDMS final specification close to approval deadline • Status Lin2, PSB, CPS: formal specif. ongoing

13. Currentstatus-2 • Operational validation of critical new controls occurring now: • BE/CO objectives set end 2012 • Anticipate the full validation with beam of critical renovations to 2013 (rather than 2014) • Aim: acquire confidence before large scale deployment, reduce risk at startup 2014. • Full scale validation of new controls • RF Linked timings • RF 10 MHZ low level • Multi-purpose Function Generator (CVORB + CGAFG + Function Editor) • Validated on critical FE (CPS MPS) - One last check scheduled end Feb. • Successful validation • My thanks to CO, RF, OP for the joint effort

14. Currentstatus - 3 • FE Installation planning 2013-2014 established • Breakdown of renovation work packages with time and HR allocated for each FE • Sequenced installations: AD > Lin2 > PSB >CPS/CTF,… • FE installation ongoing for AD -started Dec 2012 • 50% FE renovated (9 out of 18 FE) • Hardware tests + FE SW and AP integration to be performed • LINAC2 right after AD -will start ± 15 Feb • Monitoring of installation process through weekly meetings

15. FE Installation planning for ALL accelerators FE Planning for AD C.Dehavay courtesy

16. AD Installation planning for each FE We are here C.Dehavay courtesy

17. Installation follow-up tools C.Dehavay courtesy

18. In the immediate pipeline • Current effort streamlined on commissioning planning meetings preparation • Provisional agenda ready • 5-6 meetings expected per accelerator (1 per system Bi, RF, ABT,…) • Organization • Input : compact technical specification distributed before the meeting -expected to be carefully read • Output: EDMS document with commissioning time published -to be approved by all parties • High involvement from OP and EQP Groups: ±2 meetings / week

19. Highlights • Excellent collaboration EQP + OP • ACCOR OP link persons proven essential in the validation of new systems in 2012+ Jan-Feb 2013 • ACCOR OP link persons assigned during LS1 for pre-commissioning of new systems for CPS • This initiative should be generalized to all accelerators • We are missing one ACCOR OP link person for REX/ISO • EQP Groups pro-active in the renovation effort and confident in CO solutions

20. ACCOR LS1 Key Players ACCOR Project Leader: Marc LS1 Planning Officer: Claude MCC Leader: Marine Machine Controls Coordinator (MCC)

21. Questions

22. ADDITIONAL SLIDES IF NEEDED

23. ACCOR LS1 Key Players • Focal point for all requests from EQP / OP • Organizetechnicalmeetings • Present an agreedrenovationplan • Define workpackages • Ensure planning is met • Participate actively to commissioning phase ACCOR Project Leader: Marc LS1 Planning Officer: Claude MCC Leader: Marine Machine Controls Coordinator(MCC)

24. ACCOR LS1 Key Players ACCOR Project Leader: Marc LS1 Planning Officer: Claude MCC Leader: Marine Machine Controls Coordinator(MCC) • Gather all renovation objectives. Includethem in the high-level LS1 planning • Ensure that controls required during LS1 are available with nominal service level (ex. Linac4 &3 , CTF, REX) • Reserve ‘free’ time windows dedicated to CO developments • Detect BE/CO HR bottlenecks in deployment & commissioning phases

25. ACCOR LS1 Key Players ACCOR Project Leader: Marc LS1 Planning Officer: Claude MCC Leader: Marine Machine Controls Coordinators • Rationalize MCC work Ensure generic solutions to common systems thru all machines Promote standardized tools … • During commissioning phase Ensure commissioning progress is compliant with operational planning Declare system ready and hand over to Exploitation manager Report to FOM

26. ACCOR LS1 Key Players ACCOR Project Leader: Marc LS1 Planning Officer: Claude MCC Leader: Marine Machine Controls Coordinator(MCC) • Represent the group’s management and strategy • Lead commissioning meetings • Supervise work for all MCCs

27. Lin2 FE Planning LS1 Plans and Organization – TC October 18th, 2012

28. MS project ACCOR/PSB

29. AD FE Planning LS1 Plans and Organization – TC October 18th, 2012

30. PSB FE Planning LS1 Plans and Organization – TC October 18th, 2012

31. Outstanding:FE responsibility in tricky cases ? •   CO renovates to MenA20/CTR/Linux, keeping some GM classes Which group is responsible for FE and GM ? Ex: a new FE hosting only CBMIA-based POW-Vs • CO renovates TG8->CTR but stays with LynxOS, GM and possibly old modules Which group is responsible for this FE ? Ex: B-train system on DPSBBGEN • EQP GP wants to keep the current system as fall-back solution Which group is responsible for hot spare in case of roll back ? Example: PSB RF • EQP GP fails delivering the promised renovation Should BE/CO keep a fall-back solution and be responsible for it ? Example: brand new PLC controls (BE/ABP) for Linac2 source remote controls

32. SPS highlights (not exhaustive) • RF: all systems(BA2+BA3) • Renovation of 1553 underway. Full eradication by end LS1 confirmed • EPC • Replacement of MUGEF/ROCS by FGCin 2 phases • LS1: ‘FGCD’ class driving current HW. LS2: new HW + ‘FGC’ • Removal of MUGEF/ROCS SW in LS1 • ABT • New Kickers controls. • Rely on FMC-FINEDELAY new module by CO. On time. • CO/BI (BTV) • New digital video distribution approved • CMW-SLEQUIP GW will be removed

33. CPS : focus on new validations • Ambitious BECO objectives end 2012 • Anticipate the full validation with beam of critical renovations to 2013 (rather than 2014) • Aim: acquire confidence before large scale deployment, reduce risk at startup 2014. • Full scale validation of new controls • RF Linked timings • RF 10 MHZ low level • Multi-purpose Function Generator (CVORB + CGAFG + Function Editor) • Validated on critical FE (CPS MPS) - One last check scheduled end Feb. • All objectives met • My thanks for the great investment these last weeks to Greg +INCA/LSA, Anastasiya, Matthieuand those I may have forgotten

34. Lin3 LEIR • Lin2 + Lin3 RF ‘RFLNP’ renovation (2 FE) in stand-by • No progress on RF solution due to internal HR issues • Migration to Linux by CO with immediate taking over by RF not yet accepted by RF. • Meeting with OP/RF management in March 2013.

35. Generic systems • VOS (Video Observation System) • 4 FE (CTF, AD, PSB, CPS) , GM classes + Java AP • Linux + FESA migration (a priori simple) put on hold • Ongoing analysis with OP to integrate the whole VOS functionality into the existing digital video observation system (Fabio AP + Ana BTVI class) • If full integration is confirmed, VOS will be suppressed in 2014. • ‘COMPAR’ • Multi-purpose GM class by BE/OP • Full eradication effective across all machines, incl CTF during LS1 (1FE, 48 devices) • Outstanding: responsibility issue for SIS configuration (replacing COMPAR for PS Stray field compensator). Meeting soon with OP/CO management. • New FESA class replacing POW-V • Finally available by TE/EPC • To reduce risk at 2014 start-up, worthwhile to deploy it on a running accelerator during LS1 ? – to be decided