CERN-GSI Collaboration Steering Board Meeting
Description: CERN-GSI Collaboration Steering Board Meeting Controls Topics J.Fitzek (GSI), C.Roderick (CERN), P.Sollander (CERN) Areas of CERN-GSI Controls Collaboration Areas of Technical Exchange Controls Software Architecture UI Technologies,
Related Topics
Download Presentation
"CERN-GSI Collaboration Steering Board Meeting" is the property of its rightful owner. Permission is granted to download and print the materials on this website for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Presentation Transcript
slide1. CERN-GSI Collaboration Steering Board Meeting Controls Topics J.Fitzek (GSI), C.Roderick (CERN), P.Sollander (CERN)<br>
slide2. Areas of CERN-GSI Controls Collaboration Areas of Technical Exchange
Controls Software Architecture
UI Technologies, Application Services
Sequencer
Archiving / Logging System
Interfaces for Python, C++, REST
Software Engineering Tools & Practices
Analogue Signal Acquisition
Accelerator-Testing Framework
Containerization
Safety PLC
Motion control framework
Front-End Linux Platform 2 Areas of Active Collaborations
Settings Management (LSA)
Controls Middleware (CMW, RBAC)
Timing (WR Network / Switches)
Front-End Software (FESA, SILECS)
Industrial Controls Framework (UNICOS)
Formal Verification for PLC applications (PLCVerif)<br>
slide3. Action Items 1/4: Deliverables / MoU ACTION 4: The FAIR project is progressing and specific deliverables are required in many areas. If the Controls collaboration is to continue, the deliverables and timetable/milestones need to be clearly defined (Chris Roderick for GSI deliverable to CERN and Ralph Baer for deliverables to GSI).
No formal deliverables required for the Controls collaboration in general
Instead a MoU is favored, draft started description how GSI and CERN intend to continue to generally share knowledge and software with one another, but without any formal commitment to support, maintain or evolve the software according to the others needs
Specific requirements needed on the field of Industrial Controls leading to individual addenda to the Collaboration Agreement see second part of this presentation by P.Sollander 3<br>
slide4. Action Items 2/4: Python 4 A collaboration on Python has not yet been initiated. It could be of interest to reuse the CERN solution for using Python, in the GSI controls infrastructure. Alternatively, a solution could be developed at GSI that could better match the GSI controls infrastructure.
Goal at GSI is to support MDs with quick python access to the Control System (a priori not intended for productive operation usage)
Prototyping started at GSI on different levels: evaluate, if the CERN solution could be used at GSI<br>
slide5. Python Prototype at GSI Settings Management
pjlsa was set-up by A.Oeftiger with support from R.Müller at GSI, contact at CERN: M.Hostettler
necessary modifications already backported to CERN: current version of pjlsa works for both labs !
full control loop successfully implemented by S.Appel „Schottky measurement readout and analysis” that performes an energy trim in SIS18 using pjlsa
next step: simplify installation process for GSI
Accessing Devices
next step: evaluate CERN python libraries for data subscription
Goal: have a working prototype for the next beamtime at GSI 5<br>
slide6. Action Items 3/4 Machine protection and interlock system could be a topic for future collaboration. Some clarification on possible topics inside GSI is required before.
Interlock
GSI has a working Interlock System, currently no collaboration is foreseen
Machine Protection
One person moved over to GSI Controls from Jülich within the TransFAIR Process will is dedicated to the Machine Protection Topic
Topic is picked up again, possible Collaboration aspects to be discussed in future, but expected to be covered in the MoU 6<br>
slide7. Action Items 4/4: White Rabbit 7 For the timing systems using White Rabbit (WR), CERN is in the early phase of deployment. GSI uses WR as base for its Timing System.
Will be covered by the MoU, main aspect is the technical exchange
GSI participates in a common pool for a WR collaboration with 10 kCHF/year.
Proposal by CERN at the White Rabbit Workshop in Oct/2022: Goal is to establish a general White Rabbit Collaboration with CERN, GSI and other partners that drives further WR development
GSI intends to support this initiative
Example: 2020-22 White Rabbit Switch firmware development (paid by GSI)<br>
slide8. Industrial Controls with WinCC OA and UNICOS GSI uses UNICOS and WinCC OA to develop industrial control systems since several years for Vacuum, Cryogenic Controls and Access Systems
WinCC OA – Commercial SCADA software from Siemens / ETM
GSI buys the software directly from Siemens
No CERN support for incidents, requests or licenses
Dependency: follow the CERN WinCC OA version for UNICOS support
UNICOS Framework
A CERN-developed software framework on top of WinCC OA
Freely distributed to GSI
Soon to be Open-source licensed to ensure availability long term for GSI and others
No official collaboration agreement in place 8<br>
slide9. UNICOS support UNICOS software available to GSI free of charge
GSI has access to UNICOS support lines
CERN offers best-effort support
Fixes to known problems are distributed
Incidents and Requests are accepted, but not necessarily treated with high priority
CERN and GSI agree that the current best-effort support is acceptable to GSI
CERN invites GSI to join the UNICOS Technical Committee
Learn about CERN plans, issues, new developments and strategy
Inform CERN about GSI needs, issues and plans 9<br>
slide10. UNICOS development CERN defines UNICOS Plan of Work yearly
GSI may have special needs not prioritised by CERN
Collaboration model to be defined
Pilot project – GSI hiring external help, helping to port UNICOS to new version of WinCC OA ahead of CERNs plans
Possible solution for future development help
The pilot will be evaluated and conclusions drawn for future collaboration 10<br>
slide11. UNICOS risk mitigation UNICOS software availability
Open-licensing the UNICOS software will ensure availability long term to GSI
Support
Current best effort support seems sufficient for the time being
Operational support needs to be evaluated for FAIR
Development
GSI benefits from any general UNICOS development
Specific developments must be handled by GSI.
Pilot project in place
Software versioning
Changing versions of WinCC OA and the underlying Operating System must be managed.
CERN wants to minimise the number of versions supported
Different Roadmaps
CERN’s software release calendar may not be ideal for GSI and FAIR, being in a development stage allowing and asking for more frequent updates than stable operation at CERN 11<br>
slide12. PLCVerif collaboration successfully completed Verification of Personnel Access System safety PLC programs with PLCverif
Guidelines to formalize the requirements
Formal verification of these requirements against the PLC programs using PLCverif
Analysis of the verification results to find the source of the problem
Guidance and support to allow GSI to use PLCverif autonomously
Deliverables and outcome of the 6-month collaboration in 2022:
Beam Off Group and NE Area PLC programs were formally verified
Many discrepancies between the specification and the PLC programs were found (e.g. 26 discrepancies for the BOG project) and the sources of the problems were identified. A detailed report was produced and given to GSI as main deliverable.
Knowledge Transfer completed allowing GSI continued autonomous use of PLCverif.
New features and improvements were added to PLCverif to fully support the GSI programs. 12 2010 agreement K1727/DG: Addendum 17<br>
slide2. Areas of CERN-GSI Controls Collaboration Areas of Technical Exchange
Controls Software Architecture
UI Technologies, Application Services
Sequencer
Archiving / Logging System
Interfaces for Python, C++, REST
Software Engineering Tools & Practices
Analogue Signal Acquisition
Accelerator-Testing Framework
Containerization
Safety PLC
Motion control framework
Front-End Linux Platform 2 Areas of Active Collaborations
Settings Management (LSA)
Controls Middleware (CMW, RBAC)
Timing (WR Network / Switches)
Front-End Software (FESA, SILECS)
Industrial Controls Framework (UNICOS)
Formal Verification for PLC applications (PLCVerif)<br>
slide3. Action Items 1/4: Deliverables / MoU ACTION 4: The FAIR project is progressing and specific deliverables are required in many areas. If the Controls collaboration is to continue, the deliverables and timetable/milestones need to be clearly defined (Chris Roderick for GSI deliverable to CERN and Ralph Baer for deliverables to GSI).
No formal deliverables required for the Controls collaboration in general
Instead a MoU is favored, draft started description how GSI and CERN intend to continue to generally share knowledge and software with one another, but without any formal commitment to support, maintain or evolve the software according to the others needs
Specific requirements needed on the field of Industrial Controls leading to individual addenda to the Collaboration Agreement see second part of this presentation by P.Sollander 3<br>
slide4. Action Items 2/4: Python 4 A collaboration on Python has not yet been initiated. It could be of interest to reuse the CERN solution for using Python, in the GSI controls infrastructure. Alternatively, a solution could be developed at GSI that could better match the GSI controls infrastructure.
Goal at GSI is to support MDs with quick python access to the Control System (a priori not intended for productive operation usage)
Prototyping started at GSI on different levels: evaluate, if the CERN solution could be used at GSI<br>
slide5. Python Prototype at GSI Settings Management
pjlsa was set-up by A.Oeftiger with support from R.Müller at GSI, contact at CERN: M.Hostettler
necessary modifications already backported to CERN: current version of pjlsa works for both labs !
full control loop successfully implemented by S.Appel „Schottky measurement readout and analysis” that performes an energy trim in SIS18 using pjlsa
next step: simplify installation process for GSI
Accessing Devices
next step: evaluate CERN python libraries for data subscription
Goal: have a working prototype for the next beamtime at GSI 5<br>
slide6. Action Items 3/4 Machine protection and interlock system could be a topic for future collaboration. Some clarification on possible topics inside GSI is required before.
Interlock
GSI has a working Interlock System, currently no collaboration is foreseen
Machine Protection
One person moved over to GSI Controls from Jülich within the TransFAIR Process will is dedicated to the Machine Protection Topic
Topic is picked up again, possible Collaboration aspects to be discussed in future, but expected to be covered in the MoU 6<br>
slide7. Action Items 4/4: White Rabbit 7 For the timing systems using White Rabbit (WR), CERN is in the early phase of deployment. GSI uses WR as base for its Timing System.
Will be covered by the MoU, main aspect is the technical exchange
GSI participates in a common pool for a WR collaboration with 10 kCHF/year.
Proposal by CERN at the White Rabbit Workshop in Oct/2022: Goal is to establish a general White Rabbit Collaboration with CERN, GSI and other partners that drives further WR development
GSI intends to support this initiative
Example: 2020-22 White Rabbit Switch firmware development (paid by GSI)<br>
slide8. Industrial Controls with WinCC OA and UNICOS GSI uses UNICOS and WinCC OA to develop industrial control systems since several years for Vacuum, Cryogenic Controls and Access Systems
WinCC OA – Commercial SCADA software from Siemens / ETM
GSI buys the software directly from Siemens
No CERN support for incidents, requests or licenses
Dependency: follow the CERN WinCC OA version for UNICOS support
UNICOS Framework
A CERN-developed software framework on top of WinCC OA
Freely distributed to GSI
Soon to be Open-source licensed to ensure availability long term for GSI and others
No official collaboration agreement in place 8<br>
slide9. UNICOS support UNICOS software available to GSI free of charge
GSI has access to UNICOS support lines
CERN offers best-effort support
Fixes to known problems are distributed
Incidents and Requests are accepted, but not necessarily treated with high priority
CERN and GSI agree that the current best-effort support is acceptable to GSI
CERN invites GSI to join the UNICOS Technical Committee
Learn about CERN plans, issues, new developments and strategy
Inform CERN about GSI needs, issues and plans 9<br>
slide10. UNICOS development CERN defines UNICOS Plan of Work yearly
GSI may have special needs not prioritised by CERN
Collaboration model to be defined
Pilot project – GSI hiring external help, helping to port UNICOS to new version of WinCC OA ahead of CERNs plans
Possible solution for future development help
The pilot will be evaluated and conclusions drawn for future collaboration 10<br>
slide11. UNICOS risk mitigation UNICOS software availability
Open-licensing the UNICOS software will ensure availability long term to GSI
Support
Current best effort support seems sufficient for the time being
Operational support needs to be evaluated for FAIR
Development
GSI benefits from any general UNICOS development
Specific developments must be handled by GSI.
Pilot project in place
Software versioning
Changing versions of WinCC OA and the underlying Operating System must be managed.
CERN wants to minimise the number of versions supported
Different Roadmaps
CERN’s software release calendar may not be ideal for GSI and FAIR, being in a development stage allowing and asking for more frequent updates than stable operation at CERN 11<br>
slide12. PLCVerif collaboration successfully completed Verification of Personnel Access System safety PLC programs with PLCverif
Guidelines to formalize the requirements
Formal verification of these requirements against the PLC programs using PLCverif
Analysis of the verification results to find the source of the problem
Guidance and support to allow GSI to use PLCverif autonomously
Deliverables and outcome of the 6-month collaboration in 2022:
Beam Off Group and NE Area PLC programs were formally verified
Many discrepancies between the specification and the PLC programs were found (e.g. 26 discrepancies for the BOG project) and the sources of the problems were identified. A detailed report was produced and given to GSI as main deliverable.
Knowledge Transfer completed allowing GSI continued autonomous use of PLCverif.
New features and improvements were added to PLCverif to fully support the GSI programs. 12 2010 agreement K1727/DG: Addendum 17<br>