1. Controls & Tools
Greg, Kajetan

2. Many Open Questions Many ideas, but what fits into Evian?
General hope: Find speakers from different groups/sections but keep topics broader (speakers will have to do some research ;-)
 Good Speakers?

3. Main Topics Retrospective on 2016 + near future
Interfacing/Interaction with the control system
Collaborations on operational tools
Maintenance
Testing/Deployment and related risks/downtime
MD tools vs. Operational tools

4. Retrospective of 2016 & near Future
Either one or two talks:
LHC Controls: Retrospective on 2016 and outlook for 2017 [OP?]
How was the past year?
What controls functionalities were missing that had an impact on operations?
Most urgent things to improve? (if any?)
Causes for operational mistakes/delays and could they be avoided?
Most important changes foreseen for EYETS and their impact
Improvements in systems, procedures and tools [CO/EQP?]
Answers to talk 1) including resources and responsibilities
Is the follow-up good? If not, how can we improve it?

5. Interfacing/Interaction with the control system
Who and how uses the control system?
Humans, Java and non-Java tools and languages, scripting,...
What should/should not be possible?
Coherency
Vertical integration of layers (from FE up to GUI)
GUI development: Desktop apps, Web
Accessibility
Interfaces to the control system: APIs, UIs
Opening to non-Java technologies: Python, REST, …
Integration with Industrial Controls (BE-ICS)
Usability
Tedious procedures
Performance
Data storage and analysis
How to evolve?

6. Collaborations on Operational Tools
Collaboration vs. user-provider model
Advantages? Challenges?
Organization, resources?
How to set priorities?
Examples: LSA, Lumi leveling, Fidel, Parameter tracker/publisher, Injectors, GUI frameworks..

7. Maintenance & Evolution[Shared?: ]
Code is the cost, not an asset!
What is the trend for code and for resources? (numbers!)
How much technical debt do we have at the moment? How to deal with it?
Impact of technical debt on operation?
What effort goes into maintenance for the moment and what into moving forward?
Can a software product be really frozen?
Long term vision - what are options to minimize new debt in the future?

8. Testing and Deployment
How do we test at the moment (different layers e.g. Java GUIs, Servers, frontends?)
Available testing infrastructure? (CO testbed … FB testbed… Acctesting…)
Are we happy with this?
If not, how should it look like?
What are plans to change? (e.g. MPE testbed)
What resources are involved? What collaborations are planned?
How to build up testing knowledge?
How can we reduce risk of deployments?
How can we reduce time of roundtrip of development?
How can we reduce downtime? Can we get numbers?
How can continuous deployment work in our environment? Plans, ideas?

9. The road from MD prototypes to operational tools
Examples: Chroma, Feedback, …
How to get operational tools for Optics measurements? Coupling?
What are the difficulties?
Do we want them operational, or do we want to keep the expertise outside OP?
How to combine RAD tools requirements with operational stability (w/o rewriting everything)?
Resources: Who can/should provide such tools?

10. Plans for Follow up (very short) On what do we agree?
What to follow up and how?