Experimental Areas Controls Review  AB/CO Viewpoint

1. Experimental Areas Controls Review  AB/CO Viewpoint Vito Baggiolini (on behalf of the CESAR team and several people in CO)

2. Color Code + Conventions • Green: already done or no problems anticipated • Orange: not yet 100% clear (potential non-critical problem) • Red: critical problem, to be addressed urgently Vito Baggiolini AB/CO

3. Standard Controls (“StdCtrls”) • CESAR uses Standard CO controls where possible • JAPC: Communication services to the equipment on top of CMW • Middle tier services (data concentrators & elaborators, APIs,..) • On-line monitoring system for Logging, Fixed Displays, Statistics, SDDS • LHC Logging • Laser Alarm system • GUI building components (Java Dataviewer, Frame, beans, knobs, working sets, ...) • Console manager • FESA, CMW, CMW-to-SL_Equip gateway • Responsibilities: • CO: tools / services / components + support • Users (CESAR, BDI, OP): usage, configuration Vito Baggiolini AB/CO

4. CESAR Project (Applications EA + CNGS) State at the end of Run 2004 Successfully tested in PCR, operationally used in West Area Some functionality missing Performance bottleneck Need to adapt some parts to new “standard controls” Ongoing Work 2005/06 Address the above points Adapt to external changes (migration to FESA, new timing, new access system, new standard controls services, …) Resources FTEs in 2004: 1.7 (CO/AP), 0.5 (ATB/EA), 3 2nd Jobs (OP/SPS) FTEs in 2005: 1.1 (CO/AP), 0.3 (ATB/EA) FTEs in 2006 (until startup): 2 (CO/AP), 0.3 (ATB/EA), ??(OP/SPS) CESAR Team is currently working on LEIR… Vito Baggiolini AB/CO

5. Equipment control affecting CO: For reference Lau’s Slide Vito Baggiolini AB/CO *) Decision in October 2005

6. Equipment control affecting CO: For reference CO implication well-defined and agreed on: • Equipment converted to FESA (or not yet supported by CESAR) • Add functionality or adapt CESAR system  CESAR team • FESA development  Equipment groups • Exception: PLCs: First FESA implementation  CO/FC, (maintenance  BDI/SW) • CO + CESAR do not implement specialist applications • To be done with standard controls solutions  Equipment Groups • Tools + Support  CO/AP • BUT: Minor changes in CESAR GUIs where useful  CESAR Vito Baggiolini AB/CO *) Decision in October 2005

7. BDI expert and diagnostics software Lau’s Slide • Has been discussed extensively in two meetings between CO, BDI, EA, PO and OP, • organised by H.Schmickler (01/03 and 17/05). • This software will be based on 5 approaches, 3 of which involve CO: • FESA navigator (simple get/set/sub)  BDI • FESA expert programs (incl. sequences of commands)  BDI/SW No expert GUIs requested for PLC’s! • Minor additions to CESAR GUIs  Cesar team • Working sets & knobs (for PLC)  COconfiguration of WS & knobs by BDI/EA • Integration of Jython scripts into Cesar GUI  CO The VME equipment bus (and MAGEA?) will still use SL-equip and nodal in 2006, but will be moved to FESA navigator and expert GUIS a.s.a.p. (for 2007?)  Nodal is still required at least in 2006, CMW gateway to be stabilised !! The FESA PLC software will be provided by CO/FC by October Integration in common platform coordinated by BDI/EA with help from CO/AP Vito Baggiolini AB/CO

8. BDI expert and diagnostics software • Has been discussed extensively in two meetings between CO, BDI, EA, PO and OP, • organised by H.Schmickler (01/03 and 17/05). • This software will be based on 5 approaches, 3 of which involve CO: • FESA navigator (simple get/set/sub)  BDI • FESA expert programs (incl. sequences of commands)  BDI/SW No expert GUIs requested for PLC’s! • Minor additions to CESAR GUIs  Cesar team • Working sets & knobs (for PLC)  COconfiguration of WS & knobs by BDI/EA • Integration of Jython scripts into Cesar GUI  CO Agreed on. The VME equipment bus (and MAGEA?) will still use SL-equip and nodal in 2006, but will be moved to FESA navigator and expert GUIS a.s.a.p. (for 2007?)  Nodal is still required at least in 2006, CMW gateway to be stabilised !! The FESA PLC software will be provided by CO/FC by October Integration in common platform coordinated by BDI/EA with help from CO/AP Vito Baggiolini AB/CO

9. BDI expert and diagnostics software • Has been discussed extensively in two meetings between CO, BDI, EA, PO and OP, • organised by H.Schmickler (01/03 and 17/05). • This software will be based on 5 approaches, 3 of which involve CO: • FESA navigator (simple get/set/sub)  BDI • FESA expert programs (incl. sequences of commands)  BDI/SW No expert GUIs requested for PLC’s! • Minor additions to CESAR GUIs  Cesar team • Working sets & knobs (for PLC)  COconfiguration of WS & knobs by BDI/EA • Integration of Jython scripts into Cesar GUI  CO • Nodal Support • CO/IN will support Nodal language on HP-UX 10.20 through 2006 (But no piquet-style supportcan be provided) • Compatibility with new timing needs to be confirmed • CMW-to-SL_Equip Gateway • CMW gateway now deployed on each VME FE, “reliability should be OK”. • If MAGEA is not ported to VME/FESA, CO/FC needs to invest work on GW. (CMW gateway cannot be deployed on old PC-486 front-ends) The VME equipment bus (and MAGEA?) will still use SL-equip and nodal in 2006, but will be moved to FESA navigator and expert GUIS a.s.a.p. (for 2007?)  Nodal is still required at least in 2006, CMW gateway to be stabilised !! The FESA PLC software will be provided by CO/FC by October Integration in common platform coordinated by BDI/EA with help from CO/AP Vito Baggiolini AB/CO

10. BDI expert and diagnostics software • Has been discussed extensively in two meetings between CO, BDI, EA, PO and OP, • organised by H.Schmickler (01/03 and 17/05). • This software will be based on 5 approaches, 3 of which involve CO: • FESA navigator (simple get/set/sub)  BDI • FESA expert programs (incl. sequences of commands)  BDI/SW No expert GUIs requested for PLC’s! • Minor additions to CESAR GUIs  Cesar team • Working sets & knobs (for PLC)  COconfiguration of WS & knobs by BDI/EA • Integration of Jython scripts into Cesar GUI  CO The VME equipment bus (and MAGEA?) will still use SL-equip and nodal in 2006, but will be moved to FESA navigator and expert GUIS a.s.a.p. (for 2007?)  Nodal is still required at least in 2006, CMW gateway to be stabilised !! The FESA PLC software will be provided by CO/FC by October Integration in common platform coordinated by BDI/EA with help from CO/AP Vito Baggiolini AB/CO Agreed on.(StdCtrls)

11. Applications for beam line operators,users: • Jython integration • Access control application program • Reading of Radiation monitors • Settings management • Surveillance, alarms, fixed displays, teletext • Logging (surveillance, measurements, set-actions) • Printing of GUIs • User documentation & Training for operators and EA+BDI experts • Long term maintenance and adaptation to new requirements (apart from configuration – done by ATB-EA) Lau’s Slide Vito Baggiolini AB/CO Very active participation of CO experts in commissioning, tests and dry runs is essential

12. Applications for beam line operators,users: • Jython integration  new StdCtrls(CESAR, CO/AP, CO/IN) • Access control application program  adaptations (CESAR) • Reading of Radiation monitors  CESAR (StdCtrls, CO/AP) • Settings management  CESAR (functionality as in old Nodal System), (additional requirements under discussion)  CESAR • Surveillance  CESAR (StdCtrls, CO/AP),alarms  LASER,fixed displays  CESAR, (StdCtrls, CO/AP), teletext old system(CO/IN) • Logging (surveillance, measurements  LHC logging (StdCtrls, CO/DM), set-actions CESAR) • Printing of GUIs StdCtrls(CO/IN)(OK for experimental physicists?) • User documentation & Training for operators and EA+BDI experts  CESAR • Long term maintenance and adaptation to new requirements (apart from configuration – done by ATB-EA) Vito Baggiolini AB/CO Very active participation of CO experts in commissioning, tests and dry runs is essential

13. Applications for beam line operators,users: • Jython integration • Access control application program • Reading of Radiation monitors • Settings management • Surveillance, alarms, fixed displays, teletext • Logging (surveillance, measurements, actions) • Printing of GUIs • User documentation & Training for operators and EA+BDI experts • Long term maintenance and adaptation to new requirements (apart from configuration – done by ATB-EA) Long term maintenance responsibility • CESAR Control System Core  maintained and extended by CO/AP • Technology upgrades  mostly CO (some details to be discussed) • GUIs  maintained and extended by OP/SPS, ATB/EA • Configuration data (XML, Databases)  ATB/EA Vito Baggiolini AB/CO Very active participation of CO experts in commissioning, tests and dry runs is essential Very active participation of CO experts in commissioning, tests and dry runs is essential

14. Lau’s Slide • Other CO responsibilities: • Long term maintenance & support for all software under CO responsibility • Timing with 5 events, that should ‘always’ be present (also for dry runs), including VME hardware, software and support • Tools to populate & maintain configuration database (AB/CO/DM) • Transmission of beam line status to the users (“STDBLK, NSTDBLK”) • Provides and supports PC’s for CCC and areas • Console manager Vito Baggiolini AB/CO

15. Other CO responsibilities: • Long term maintenance & support for all software under CO responsibility • Timing with 5 events, that should ‘always’ be present (also for dry runs), including VME hardware, software and support discussed & agreed (CO/HT) • Tools to populate & maintain configuration database (AB/CO/DM) Now implemented with MS Access, to be ported to standard technology • Transmission of beam line status to the users (“STDBLK, NSTDBLK”) online monitoring + SDDS (StdCtrls, CO/AP), small additions to CESAR • Provides and supports PC’s for CCC and areas  StdCtrls, CO/IN • Console manager  StdCtrls, CO/AP Vito Baggiolini AB/CO

16. At the EA day a controls upgrade project will be presented for 2007 EAST Area: Needs for 2006 and beyond: • All the needs we have for the North Area, apart from the • upgrade related items. • This includes: • Maintenance of existing software • Timing • PC configuration and maintenance in EBCR • Control consoles in CCC Lau’s Slide To be evaluated when the request comes.  CO priorities? However, the CCC is far from the East Area, the lack of remote control becomes serious handicap. Instrumentation is very limited Vito Baggiolini AB/CO

17. For reference Lau’s Slide CNGS Equipment Control: Vito Baggiolini AB/CO

18. For reference CNGS Equipment Control: [Detailed analysis of requirements still ongoing] Standard Controls Requirements • Read/Control  WorkingSets/Knobs (StdCtrls, CO/AP) • Display  Fixed Displays (StdCtrls, CO/AP) • Logging  Monitoring Service (StdCtrls, CO/AP), LHC Logging (StdCtrls, CO/DM) • Profile display  Emittance/Profiles project (OP/SPS)? • Scan  CESAR • Alarms  LASER, Interlocks  SPS/LHC interlocks, Access  SPS/LHC access • Horn/Reflector expert control with UNICOS Special Requirements • Data exchange between CERN and Gran Sasso  LHC Logging? (To be analyzed) Vito Baggiolini AB/CO

19. Conclusions • Requirements for SPS-EA clear and well managed • Good and solid collaboration • No worries for Control System Core • We need “our” CESAR GUI developers (from OP/SPS) in 1st half 2006 for new equipment and missing functionality + CNGS work • Long-term maintenance clear, details to be defined • East Area for 2007 not yet taken into account • CNGS (secondary beamline) • Good and promising collaboration • Overall requirements understood(detailed analysis ongoing) • No problems anticipated, mostly standard controls • If we get “our” GUI developers and if LEIR work stops end of 2005,we can handle Dry Runs, CNGS and SPS Operations in 2006. Vito Baggiolini AB/CO

20. Vito Baggiolini AB/CO