1. Supervision Miniworkshop JCOP Workshop 2015
Organizers: C. Gaspar, P. Golonka, K. Hennessy,
O. Holme, O. Pinazza, M. Gonzalez Berges
5th November 2015

2. Alessandra Lombardi on behalf of the LINAC4 team
Introduction
The experience with supervision systems for the LHC experiments has been very successful. Both WinCC OA (PVSS) and the JCOP Framework are currently used in a large number of installations that will evolve in the next years. The aim of the miniworkshop will be to identify areas of work to help in this evolution and at the same time improve possible shortcomings of the current solutions. Topics related to development and operations will be covered.
Possible follow up:
Workshop (another one;-))
Seminar
Documentation
New development
etc
Alessandra Lombardi
on behalf of the LINAC4 team

3. Alessandra Lombardi on behalf of the LINAC4 team
Poll Results
42 responses (out of ~80 registered at the time of the poll)
Topic
Interested
Partially Interested
Total
FSM 30 7 37
Alarms 28 9
Usability 25 11 36
Development Workflow 13 38
Quality Assurance
Remote Access 21 15
Scripting Language 34
System Overview 20 17
Reporting 19
Archiving
Collaboration Tools 16 35
Alessandra Lombardi
on behalf of the LINAC4 team

4. Alessandra Lombardi on behalf of the LINAC4 team
FSM
Logic and concepts
How did you find the learning process?
Do you feel confident as a developer of the FSM?
What features are missing? Or is it already enough (or too much)?
How much do you use the newer features of SMI++?
e.g. stay_in_state, wait, set
Development tools (panels to design types, FSM tab to create tree)
What is your view of the FSM development process?
Are the tools sufficient for large scale systems?
Have you built other tools to help with development?
Would more checking at design time be helpful (syntax/logic)?
What about tools to export/deploy FSMs? What do you use?
Operational experience
How stable are the FSMs in your systems?
How easy is it to understand a problem that occurred in production?
What kind of improvements might help debugging?
Alessandra Lombardi
on behalf of the LINAC4 team

5. Alessandra Lombardi on behalf of the LINAC4 team
Alarms
Alarm Generation / Configuration
Are existing libraries and tools enough?
Are there features missing in WinCC-OA?
Ex.: time delay, etc.
Are you aware/do you use all features?
hysteresis, discrete alerts, multinstance, external, etc
Do we need better guidelines/policies?
Alarm Handling
Alarm reduction
Are current Alert Summaries enough?
Do we need enhanced Filtering?
Alarm Notification
JCOP Alarm Screen
Do you use it? Or did you develop an experiment specific one?
Is the current functionality satisfactory?
What can be improved?
Alarm help? Historical view? Statistical analysis tools…
, SMS, Voice, etc
Alessandra Lombardi
on behalf of the LINAC4 team

6. Alessandra Lombardi on behalf of the LINAC4 team
Usability
Operation and Development tools
Are the tools easy to use/understand?
Do we feel the JCOP tools are coherent/consistent?
Is there something in particular lacking?
Performance / Responsiveness
what needs improvement?
Issues with scalability?
Problem tracking / Reporting
Do we need better data mining tools - for error logs, debugging?
Are the Plotting/Histogramming tools sufficient?
Suggestions for new components
Do we need more documentation/training?
How hard is it to find solutions? Can I google it?
Is operating system support sufficient? (e.g., tools consistent across OS’s?)
Alessandra Lombardi
on behalf of the LINAC4 team

7. Alessandra Lombardi on behalf of the LINAC4 team
Development Workflow
Actual tools and development methods: are they adequate and functional?
WinCC OA and Framework installation
Do we abide by JCOP guidelines: are these up-to-date, useful? Did groups develop their own?
Configuration management from design to production
Editors: GEDI, script editor and wizards
Debugger
Graphical libraries, widgets, ActiveX
Should we look at other tools?
IDE to Eclipse, feedback?
How to surpass QT graphics?
Do we need different technologies for trends, histograms?
Integration with external tools:
Version control: SVN, GIT
Sharing solutions: do we need a common repository?
Less formalities, no maintenance and no support
Alessandra Lombardi
on behalf of the LINAC4 team

8. Alessandra Lombardi on behalf of the LINAC4 team
Quality Assurance
Source code control and management
Version control, defect tracking, issue tracking infrastructure
Build-management tools, FwPackager? CMake? Better FSM packaging?
Use of Continuous Integration tools (Jenkins?)
Code reviews practices and tools; documentation
Guidelines, coding rules: do we need any update?
Testing
Hardware/software reference setups and test-benches
Improved hardware simulators? (basic CAEN and ISEG exist)
Code tests: setup, unit testing, static analysis, etc
Performance tests
From development to production: release management
Architecture based on components and frameworks
Patches? Live-system hotfixes? Regular backups/snapshots?
Towards more agile approach (also for large upgrade campaigns)
=> meaningful in production control systems? Application Release Automation
Are our tools (fwInstallation, SysConfDB) sufficient?
Distribution repositories (eg. Nexus?)
Alessandra Lombardi
on behalf of the LINAC4 team

9. Alessandra Lombardi on behalf of the LINAC4 team
Other Topics
Poll Suggestions:
Redundancy, Framework review, WinCC OA future (replacement?)
DIP, uTCA, native drivers instead of OPC
Topic
Interested
Partially Interested
Total
FSM 30 7 37
Alarms 28 9
Usability 25 11 36
Development Workflow 13 38
Quality Assurance
Remote Access 21 15
Scripting Language 34
System Overview 20 17
Reporting 19
Archiving
Collaboration Tools 16 35
Alessandra Lombardi
on behalf of the LINAC4 team

10. Alessandra Lombardi on behalf of the LINAC4 team
Thank You!
Alessandra Lombardi
on behalf of the LINAC4 team