the Control System? Stephane Deghaye (BE-CO) Many thanks to all the - PowerPoint PPT Presentation

How to improve interactions with the Control System? Stephane Deghaye (BE-CO) Many thanks to all the colleagues who gave me feedback on the interaction with Accelerator Control System Evian’16 2 14-12-2016

Evaluation criteria • Accelerator Controls in 2016 : Availability • 10 10 System availability: 99.89% 8 8 • Raw fault time: 9h 81 6 6 • Source: AFT (08-12-2016) 4 4 • Main contributors : 2 2 • WorldFIP 0 0 • Timing • Front-end HW Evian’16 – S. Deghaye (BE-CO) 3 14-12-2016

Accelerator Controls’ Availability in 2016 • The most important criterion for the Control System • Not the only criterion to be optimised. Much more is expected Evian’16 – S. Deghaye (BE-CO) 4 14-12-2016

Evaluation criteria • Maintainability : Availability Availability Availability • Low-level renovation (ACCOR) 10 10 10 8 8 8 • Finishes in LS2 (Post-ACCOR) 6 6 6 • High-level SW consolidation (InCA) 4 4 4 Maintainability Maintainability Maintainability • Cost : 2 2 2 • Factor 2 to 3 reduction with recent 0 0 0 platforms • Still expensive for high-end HW (OASIS) • Exportability : Exportability Cost Cost • Difficult to contribute from outside • GSI uses our solutions Evian’16 – S. Deghaye (BE-CO) 5 14-12-2016

Evaluation criteria UX : person’s emotions and • Availability Availability Availability attitudes using a particular 10 10 10 8 8 8 product, system or service [1]. 6 6 6 Highlight the human-product Flexibility Maintainability 4 4 4 Maintainability User Experience Maintainability interaction 2 2 2 • Usability : How the system eases 0 0 0 or impedes the performance of a supported task Usability Cost • Flexibility : How easy it is to Exportability Exportability Cost Cost extends the system with new Exportability needs/features [1] Wikipedia Evian’16 – S. Deghaye (BE-CO) 6 14-12-2016

Users? R Operator O RF Developers L Etc. 1 st line Diagnostic E S MD User Software Developer (HL & LL) ABP Physicists Hardware Developer LHC Operators Evian’16 – S. Deghaye (BE-CO) 7 14-12-2016

UX issues with current system • Interview with key users  Control System is Complex & Heavy • Complexity impedes Usability • Tools* are inadequate for some common tasks • Technical & Organisational inflexibility Several solutions to a single problem (Acc CS, SCADA, … ) • * Tools: end-users GUIs & programming languages Evian’16 – S. Deghaye (BE-CO) 8 14-12-2016

Usability issues – a few examples • Heterogeneous APIs DIAMON • ≠ sources ⇒ ≠ behaviour Alarms PM SIS CCDB • Configuration marathon: InCA/LSA CALS Many steps that are JAPC/CMW manual w/o self-evident transitions FESA FGC TN SILECS Availability on GPN not consistent GPN Evian’16 – S. Deghaye (BE-CO) 9 14-12-2016

Usability – Development tasks Develop Release Deploy Import Configure Test Operational Timing ONLY • Feature set not consistent • Vertical testing not possible Low-level dev cycle • Long iteration time Evian’16 – S. Deghaye (BE-CO) 10 14-12-2016

Flexibility - Technical Heavy dev process prevents quick test • and fast-iteration developments • Infrastructure geared ? FESA Class toward stable operation ? Driver Hardware under DEV Evian’16 – S. Deghaye (BE-CO) 11 14-12-2016

Flexibility - Organisational Needs are immediate, not solutions • • Priorities (requester vs provider) • Limited resources (provider)  Ad-hoc solutions appear - maintainability issues Who does what? • • Responsibility limits • Long-term maintainability Evian’16 – S. Deghaye (BE-CO) 12 14-12-2016

Usability improvements • Look at Control System use-cases instead of at service use-cases • Role-based & task-oriented Tools New services in existing tools No new specific tools (e.g. CALS) Evian’16 – S. Deghaye (BE-CO) 13 14-12-2016

Usability improvements Software developers Feature set must make sense throughout the CS & Full stack must be available in DEV Evian’16 – S. Deghaye (BE-CO) 14 14-12-2016

Usability improvements OP Convention MD Users & App developers over  Reduce API fragmentation Configuration Device/Property API PM CMW … Less config tools CALS Timing LSA & more homogeneous behaviour Evian’16 – S. Deghaye (BE-CO) 15 14-12-2016

Flexibility improvements • Embrace relevant RAD environments (e.g. Python) • Depart from Provider/Client model & open up to sector- wide collaborations Taurus & Sardana Community dev • Python Focus Group Others: • Web dev • Inspector • FESA, etc. Courtesy C. Pascual-Izarra et al. Evian’16 – S. Deghaye (BE-CO) 17 14-12-2016

Summary Excellent operational availability •  To be kept at that level • Improving maintainability  LS2 should see the maximum being reached Improvement of the interactions • • Role-based, task-oriented analysis & tools • More flexibility thanks to RAD tools & collaborations • Work towards an integrated Accelerator Control System Evian’16 – S. Deghaye (BE-CO) 18 14-12-2016