SMTMS

1. SMTMS SM18 Tests Management System

2. The SM18 Facility

3. SM18 Tests Management System S M T M S • Introduction to SM18 & Magnets Tests Facility • Work to be done • By Operation department together with many more Indians and external contractors • Control Infrastructure • How SMTMS a web based database system helped operation in everyday work • Why we needed this tool • Main tasks of the program • Other helpful benefits • Conclusion

4. The Magnet ZOOor, what we need to test • 1232 DIPOLES 15m long each • Tunnel filling factor ~20 Km out of 27km and the rest…… • 360 Short Straight Sections – SSS • Quadrupoles integrated with Orbit Dipole Correctors, • Octupoles, • Sextupoles, skew elements • All in same cryostat • 114 Dispersion or Insertion Region SSS’s of 14 different types • Big issue (Only manual tests)

6. Test Facility in SM18 • 12 test benches in SM18 • Roughly speaking: • 3 magnets @1.9 ‘k • 3 in warm-up or cool-down phase • 3 in connection Or disconnection phase • 3 spare &/or dedicated to special use • 6 power supplies ( 1 per 2 benches) • Dipoles as well as SSS’s Testing

7. Foreseen Times • Standard time • 12 hrs connection • 12 hours vacuum pumping • 26 hours cooldown • 36 hours cold test • 12 hours warm up • 12 hours disconnection • Total 108 hours per magnet • (4.5 days of 24 hours)

8. Real Times

9. Control Infrastructure • Based on proprietary system • Sun WS • Labview • Incaa Acquisition System • And Home-Made system • Magnetic Measure • Hardware recognition, Test master

10. VME integrators GPIB M X I b u s Sun Workstation Energy Loss Measurement R S - 2 3 2 C t o G P I B RRR Measurement Analogue signals P o w e r DVM Trigger S u p p l y R S - 2 3 2 C c o i l s shafts A n g u l a r A n g u l a r F o r c e & Program. Amps m o t o rs e n c o d e rs T o r s i o n Magnet on bench S H A F T C O N T R O L Application layer of Magnet Test Benches [Adriaan Rijllart AB-CO] Power Tests Magnetic Measurements Data base Ethernet Sun Workstation VME based DAQ system

11. Bench Remote control

12. Tests Work • Today, tests done via 6 dedicated work ‘consoles’ • For 6 clusters = 12 benches (magnets) • Lots of tests done on floor level (resistance, HV); • Power tests • Training of magnets • (Automatic) Quench Analyses • Magnetic measurements • Only for a few magnets • Magnetic measurement list of things to observe & check during tests • Sending of magn. Measurement data to analyses database for others to continue analyses from the sent data

13. Control Room Work • Data check and filling • In paper logbook (mainly for tests at floor level and analysis) • In database most of the filling is automatic, some tests or results have to be entered manually • Logbook PC for Equipment Faults • Decision on Magnet Goodness • Team work collaboration • Priority settings

14. Excel files on server Network problem Takes 2 minutes to save Excel takes 90 % resources of the PC (24 files of 2 MB) Sharing problem Users locked the file Need to type same data in many files Quench table test Sequence Current history Paper Private server Hidden private data Only experts can have access Big files with all built macro Each file was 2 MB (total DB with 718 magnets is 7 MB) No global view For statistics we need to open 3 files per magnet Test definition and name problem Not centralized Starting Situation- Particular Problems

15. Why We Need SMTMS (1) • Task tracking system • We need fixed display with the work ongoing • We need concurrent access • With Read Only protection • Statistics Tools • We need to have real time measurements to see where we should put the pressure

16. Why We Need SMTMS (2) • Avoid duplication of work • Filling paper and many files • A tool accessible from every PC or WS • Easily suitable to our needs • Fast enough • Data – Style Separation unlike Word or Excel

17. Statistic Tools Database items Other DB Fixed display Other DB Site Overview

18. SM 18 Hall SM 18 control Room IT Web Server Offices Display ASP Technology: Programs are run inside the server. Server sends only HTML pages. Security by IP addresses

19. First Purpose • Keep a track of the test • To Do list • contains all the possible tests for a magnet • Test Sequence • Contains the executed test for a particular magnet

20. Bench Status on CERN LHC Dashboard (CERN home page)

21. Statistics

22. MAPS for Magnet

23. XLQuench Table XLTest sequence for magnet For backward compatibility

24. Magnet Quench Table by Type

25. Shift Statistics

26. White board

27. Priority Management

28. Direct Link to MTF DB

29. Update Issue • At the beginning update was done manually by operators • Date Format problems • Wrong phase • File names with mistake • Data depends on other teams • Soon we developed an automatic update system

30. Pull solution • For this solution data were available on the web. • The automatic update program scans the web services in order to download update information Call Answer Server 1 Server 2

31. SM 18 control Room Push solution • For this solution data were available on file servers. • The automatic perl update program scans the new files in order to upload new test in the DB Update DB File server Web Server

32. Time tracking

33. Test tracking

34. Quench behaviour

35. Weekly statistics

37. Other uses of database • Precise name for control system • Web Database is able to generate correct name of magnet in case of retesting • Display of magnet name and tests on LCD panels in top of the benches is also driven by the web database

38. Conclusions • Lot of the concepts, usage & applications which led to the SMTMS were due to the fact that in the industrial environment of SM18 it is very difficult to make understand people what operation is • SMTMS was born out of difficulty to manage the tests in a structured & simplified way, with constant flow of short-stay & rotating Indian staff and other external contractors • This project can be re-used in situation where various teams must work together on a defined project

39. Conclusions • It was made as flexible as possible to cope with monthly modification • Automatic update and flexibility made the tools easy to use and to maintain • It eases the management of the facility by splitting a big problem into smaller one. With this tool you can easily have a view by magnet, by week, by test, … • I would like to thank people in IT division for their help especially E. Roux for much advice he provided to me in ASP programming I would thank also J. Axensalva for the good collaboration we had in this project

40. Prototype facility Repair as they can Operation not actively involved in Software and design of facility Each group has its own idea and implements its way Culture of keeping things secret (Password) Running accelerator Fast repair Operation is central about design and software development Advice of operation before implementation Open environment with trust of operation Differences between SM18 and MCR

41. Short time facility Uses as it is Test coordinators have no common rules Many test to be done on floor level or not automated Prototype control system Many bugs Needs to be improved Long time run Try to improve things Machine supervisors relies on meeting and long tradition Remote operation functional Robust control system Differences between SM18 and MCR

42. Paper Logbook with Test Equipment and Magnet problem mixed Test sequence and quench files in XL format with redundant information E-log book for Equipment Database for magnets One data base for all magnet information with help of a paper logbook to track test on floor level SM18 and MCR philosophy

43. 11 words file per magnet stored on a private server Power tests results on a gigabyte server to be analysed further. MRM project still not working after more than 600 magnets tested One web-based data base for all magnet information with the possibility to generate XL files First Analysis results stored in Database SM18 and MCR philosophy