LEIR Controls : Gain of Experience for the Running-in of LHC

1. LEIR Controls :Gain of Experience for the Running-in of LHC Marine Pace on behalf of AB/CO and LSA Marine Pace - AB/CO

2. Outline LEIR Controls • Background • Challenges • Gain of experience in view of LHC • Conclusions Marine Pace - AB/CO

3. Background • Major constraints • Use controls designed for the LHC • Apply unified controls from the merge PS and SL Controls Groups • Integrate legacy controls from existing PS accelerators • A test-bed for new standard solutions in view of LHC • Used for the first time under operational conditions • To be deployed in LHC & its pre-injectors at later stage • An anticipated challenge for the CO Group Marine Pace - AB/CO

4. Challenges • Technical • Customize/enhance/generalize LHC controls • Were implemented for transfer lines • But LEIR is a circular + cooling + multi-cycling accelerator • Practically validate LHC controls • Deeper validation than TT40 & Ti8 • Deploy new unified controls from PS and SL • While respecting operational milestones • Tight schedule • Objective: provide a minimum set of functionalities & tools to operate the machine • Cultural • Define a unique strategy from historically different solutions and habits on both sides • Set-up productive developer teams • Convince Operations to understand new concepts and use new tools / methods Marine Pace - AB/CO

5. SettingGene- App Legacy XMotif App Generic App WorkingSetsKnobs BeamSteerApp Consoles TRIM App Config DB LSA DB LSACore ApplicationServers Controls Middleware GM device FESA device Front End Snapshot of a hybrid controls system (not complete) Marine Pace - AB/CO

6. Outline LEIR Controls • Background • Challenges • Gain of experience if view of LHC • Technical perspective • Cultural perspective • Conclusions Marine Pace - AB/CO

7. where LEIR brought a significant experience Gain of experience in view of LHCTechnical Perspective • Controls for LHC deployed at LEIR • Front end Hardware • Front end Software • Application Software • Analogue Signal Observation System • Sequencing and Timing - CBCM • Alarms – LASER • Common Console Manager - CCM • Device Access interface – JAPC • Controls Middleware – CMW • …. Marine Pace - AB/CO

8. Front End Hardware • Front end VME machines • LHC standard technology • Wiener Crates hosting CES PowerPC RIO2/3 processor • Experience • Minor problem solved • Worked well during operation from the start • Timing Receiver Module - CTR • Designed for the LHC, deployed at LEIR • Experience • In-depth validation of main functionalities • Worked well during operation from the start  Very smooth integration of LHC HW components Marine Pace - AB/CO

9. Front End Software • Front-End Software Architecture - FESA • New framework for real-time device software development • Widely used at LEIR: BT, BDI, RF, TIMING devices • Experience • LEIR too early for FESA - Missing commissioning time • Lack of stability and maturity (for a significant part of the commissioning) • Late delivery of some important features • Releasing process not fully mastered • Main functionalities now in place and validated • Major progress compared to old FE software framework • Proven to be efficient + adequate • Stringent software release policy decided  Essential for CO that it was tested in LEIR Marine Pace - AB/CO

10. LHC Software Application – LSA • Settings Management • Challenging cycle definition • Cycle to USER mapping: many USERs, multi-USER cycle • Varying optics in cycles • Cycle in terms of Brho-dot • Complex parameter space • Eddy Current Compensation • Electron Cooler Compensation • Trim • Challenging requirements • Brho-dot, Brho trims • Plus incorporation with cycle. • Plus propagation across USERs • Orbit • Full integration of LSA core components • Drive, Trim, Optics,… Marine Pace - AB/CO

11. LHC Software Application – LSA (cont’d) • Experience • Design proven powerful • Data model, 3 tier architecture, core functionality • Adaptation to LEIR relatively easy • Extremely valuable validation • Lot of debugging and concept straightening performed • Adaptation made LSA more complete and versatile  An important milestone towards LHC controls Marine Pace - AB/CO

12. Generic Application Software – Working Sets / Knobs • Widely used at LEIR • Java re-write of legacy generic applications • Lower-level controls of individual parameters • Experience • Main functionalities are now in place • Helped improvement of Middleware and FESA • No specification for LHC yet but … • Might be an interesting candidate for machine development Fast setting-up of controls environment for a new device • Will be used for CNGS, CESAR, SPS RF timing,… Marine Pace - AB/CO

13. Analogue Signal Observation System OASIS • Designed for all CERN machines, deployed at LEIR • Experience • Significant validation • Scalability (partially) proven ~ 200 signals • Software architecture (3 tier) well suited • Good performance of FESA server and Application server • New Acqiris oscilloscope modules validated • Lots of issues solved during commissioning • Main functionalities in place now • Solution underway for slowness of GLOBAL SIGNAL connections  In-depth validation performed in view of LHC Marine Pace - AB/CO

14. What we learnt Cultural Perspective • Cultural difference PS-SPS was a real challenge • Controls providers: extra effort & time to overcome cultural differences • LEIR Operators from a unique culture – PS • LEIR OP would have preferred traditional PS-style controls to be deployed • NO LEIR operator participatedin the applications development • Experience • Context was not favorable to a mass deployment of new / LHC controls • Closer collaboration CO  LEIR OP in the SW development projects would have helped • But also a great opportunity • Cross pollination between PS and SPS approaches • Fruitful experience for all people who actively participated in the specification, design and development Marine Pace - AB/CO

15. What we did NOT learn • LEIR is a small machine • Scalability of SW architecture and core components NOT validated • Might be an issue. Need of a full scale validation. • LEIR is a harmless machine • Critical systems for LHC NOT validated • Power and Beam interlocks • Real Time feedbacks • Quench protection • Cryogenics • Collimation … • And related services: post mortem, logging….. • NO experience in Unified Industrial Controls UNICOS Marine Pace - AB/CO

16. Conclusion • The starting point • LEIR OP and CO had different goals for LEIR • OP wanted to commission LEIR with 100% functional and reliable controls • CO and LSA team used LEIR as a test bed for LHC software • The outcome • Controls made work more difficult for LEIR-OP • But it did not prevent them from operating the machine • A “Not perfect but operational” controls system is available • From CO viewpoint we achieved an important milestone towards LHC Marine Pace - AB/CO