1. Application Development for Operations in the Coming Years Mike Lamont

2. The development of operational application software by BE-OP does not systematically follow standard software development processes In order to ensure that operators are equipped with reliable software for the operation of LHC and its injectors, during the lifetime of the LHC, the Head of BE-OP should ensure that the processes used in BE-OP for future operational software development and for reporting problems follow the highest professional quality standards and are coherent across the four islets of the CCC. To this end, the head of BE-OP should reinforce the collaboration and the sharing of best practices in software development between BE-OP and BE-CO. Audit of the operation of LHC and its injectors 2

3. PS: “Pas mal” LHC: bloody impressive SPS: pretty good PSB: Needs INCAfying, but OK AD: eek! ISOLDE: heroes at work LEIR: INCA & LSA and it still works TI: excellent job in a heterogeneous world Present situation 3

4. LSA  Deployed in SPS, LHC, LEIR, transfer lines  Huge core – skeleton support  Many associated applications  Improvements, maintenance continually ongoing INCA  Deployed in PS, LEIR  PSB incoming  LSA inside – support critical Some excellent standard facilities in use across the complex:  eLogbook, fixed displays, SIS, YASP… Stand alone applications  Many, many (beam instrumentation, RF, working point control etc. etc.) plus legacy, orphans etc. Present situation 4

5. A mountain has been climbed and huge mountain of software has been developed over the last few years Excellent and good natured collaboration between OP and CO (and BI, ABT, PO, ABP, MA…) This software is valuable asset and allows proper exploitation of a very valuable resource (the accelerator complex) Important: this software needs TLC and an appropriate level of support Clearly there are issues and a continuing need for improvements Present situation 5

6. The functioning of the PS complex is still relying heavily on a large number of X-Motif applications, which are extremely important operational tools and need good support in case of problems. These applications will gradually be replaced, but this will take time. Progress will depend on system renovation, INCA implementation and available resources AD also uses archives, but problems with the archiving created a substantial loss of time in order to ensure that the data in the archives were correct Typical issues 6

7. Application development more-or-less handed over to OP  “Second job”  Fellows, Ph.D.s, external collaboration  Other groups (BI, ABP…) Note that this is not just “GUIs”  Some serious, very good stuff…  IQC, BQM, YASP, Settings Generation, BLMs, Lumi scan, Fidel Long operational years recently mean less time for development Evitable turnover of personnel Resulting in some orphans and less than ideal support of the big pile Development 7

8. OP resources 2011 8 Tight

9. Incoming LS1 – 2013/2014 9 Exactly what and how long – the subject of intense discussion Simon Baird

10. LS1 software deliverables 10 AD,LSA at least ISOLDE HIE ISOLDE High level controls LINAC4High level controls PSBINCAify booster LINAC4/PSB diagnostics PSINCA consolidation, renovation of various classes Continued LSAfication Xmotif eradication SPS & LEIRConsolidation, GUIs LHCConsolidation Re-work GUIs & improvements Cherries on cakes, fully integrated on-line model, etc… TIOperational Manpower requirements to be established

11. L4: standard software 11 Clear ongoing interest to leverage existing functionality G Bellodi -BE/ABP/HSL

12. L4: beam instrumentation 12

13. L4: beam instrumentation 2/2 13 G Bellodi -BE/ABP/HSL

14. L4: equipment control 14 G Bellodi -BE/ABP/HSL

15. L4: general purpose 15 All standard and existing facilities G Bellodi -BE/ABP/HSL

16. L4: interfaces ++/RTUs 16 G Bellodi -BE/ABP/HSL

17. Every new or renovated system requires writing or adapting the applications. The aim for 2013 is also to get a part of the "intelligence" that is presently in the GUI's. We also need to eradicate the X-motif applications as they have still to go through the XML RPC server slowing down the performances Some applications on the renovation list are: - LKTIM (flexible timing trees for RF) - t = f(t) (management of the timing settings (apart form RF) for all cycles - Make the proto-type extraction bump application in JAVA and extend it to include orbit length compensation by changing RF phase. - Bunch shape measurement - Tomoscope - Some sampler related application - Extra requirement that will come with LIU PS 17 Rende Steerenberg

18. 2013-2014: OP resources

19. When we get back from Barbados… 19 Provide non-LHC software applications [10.4 FTE] Provide LHC (LSA) software applications [3.4 FTE]

20. 14 OP FTEs (to be confirmed)  Well-organized – serious progress possible Other groups  Specialized accelerator physics related applications External collaborations  LAFS… Fellows, VIAs, GETs, Ph.D.s Associates Resources 2013 (& part of 2014) 20 At first sight, enough manpower to mop up foreseen deliverables

21. Relatively healthy situation reflected in excellent performance of the complex Concerns about support levels in CO and a stretched OP group Foresee maintaining a holding pattern until the end of 2012  Maintenance and development at current levels Significant manpower to be made available in LS1  Should be sufficient to cover foreseen requirements:  LINAC4, Xmotif eradication… etc. Conclusions 21