Software Scope Susanne Regnell Group Leader Control System Software 2016-04.

Slides:



Advertisements
Similar presentations
Control System Studio (CSS)
Advertisements

SNS Integrated Control System SNS RDB Requirements, wish list, status A little history l Oracle RDB used exclusively by accelerator physics group l JERI.
1 1999/Ph 514: Channel Access Concepts EPICS Channel Access Concepts Bob Dalesio LANL.
Status of the European Spallation Source Timo Korhonen Chief Engineer, Integrated Control System Division October 21, 2014.
ITIL: Service Transition
Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 MICE Control and Monitoring: General Architecture Subsystem Integration User Interface.
Agenda Adaptation of existing open-source control systems from compact accelerators to large scale facilities.
Drag and Drop Display and Builder. Timofei B. Bolshakov, Andrey D. Petrov FermiLab.
Configuration Database MICE Collaboration Meeting 28, Sofia David Forrest University of Glasgow Antony Wilson Science and Technology Facilities Council.
MASAR Service Guobao Shen Photon Sciences Department Brookhaven National Laboratory EPICS Collaboration Workshop Oct 05, 2013.
Elder Matias, Diony Medrano, Dong Liu (At Michigan State University - Nov 2011) IRMIS at CLS.
Final Review of ITER PBS 45 CODAC – PART 1 – 14 th, 15 th and 16 th of January CadarachePage 1 FINAL DESIGN REVIEW OF ITER PBS 45 CODAC – PART 1.
CIDB The PSI Controls Inventory DataBase Timo Korhonen, PSI (for the CIDB Team)
SONIC-3: Creating Large Scale Installations & Deployments Andrew S. Neumann Principal Engineer, Progress Sonic.
SONIC-3: Creating Large Scale Installations & Deployments Andrew S. Neumann Principal Engineer Progress Sonic.
F Drag and Drop Controls Display and Builder (Synoptic Display) Timofei Bolshakov, Andrey Petrov Fermilab Accelerator Controls Department March 26, 2007.
Creating SmartArt 1.Create a slide and select Insert > SmartArt. 2.Choose a SmartArt design and type your text. (Choose any format to start. You can change.
Status & development of the software for CALICE-DAQ Tao Wu On behalf of UK Collaboration.
CS223: Software Engineering Lecture 13: Software Architecture.
1 Channel Access Concepts – IHEP EPICS Training – K.F – Aug EPICS Channel Access Concepts Kazuro Furukawa, KEK (Bob Dalesio, LANL)
R. Krempaska, October, 2013 Wir schaffen Wissen – heute für morgen Controls Security at PSI Current Status R. Krempaska, A. Bertrand, C. Higgs, R. Kapeller,
Control System Considerations for ADS EuCARD-2/MAX Accelerators for Accelerator Driven Systems Workshop, CERN, March 20-21, 2014 Klemen Žagar Robert Modic.
Database Issues Peter Chochula 7 th DCS Workshop, June 16, 2003.
Responses to recommendations of TAC 11 Integrated Control Systems Henrik Carling ESS/ICS Date:
ICS WP3 – Software Core Components Suzanne Gysin Work Package Lead November 25, 2014.
Industrial Control Engineering Session 1 Introduction  What is RADE  Technology  Palette  Tools  Template  Combined Example  How to get RADE 
ESS Integrated Control System Software Core Components S.Gysin
Software Core Components (ICS WP3) Suzanne Gysin Work Package Lead February 22, 2014.
 TE-MPE-PE Clean code workshop – R.Heil, M.Koza, K.Krol Introduction to the MPE software process Raphaela Heil TE-MPE-PE Clean code workshop - 9 th July.
SNS Integrated Control System ORACLE –JERI DB Generation April 27, 2004 Coles Sibley Jeff Patton.
1 DEPLOYMENT AND OPERATIONS MODULE 23 ECM SPECIALIST COURSE 1 Copyright AIIM.
Control System Tools for Beam Commissioning Timo Korhonen Controls Division Chief Engineer April 8, 2014.
Integrated Control Systems Status and Plans Garry Trahern Head of ICS Division TAC 9, 3 rd April, 2014, ESS, Lund.
Software Reuse. Objectives l To explain the benefits of software reuse and some reuse problems l To discuss several different ways to implement software.
Advanced Higher Computing Science
Combining safety and conventional interfaces for interlock PLCs
LCLS Commissioning & Operations High Level Software
Architecture Review 10/11/2004
ITIL: Service Transition
BaBar Transition: Computing/Monitoring
Chapter 1 The Systems Development Environment
Installation The Intercompany Integration Solution for SAP Business One Version 2.0 for SAP Business One 9.1 Welcome to the course on the installation.
Chapter 1 The Systems Development Environment
Presented by Li Gang Accelerator Control Group
Self Healing and Dynamic Construction Framework:
Chapter 1 The Systems Development Environment
Relational Database Collaboration
EIN 6133 Enterprise Engineering
Chapter 1 The Systems Development Environment
FESA evolution and the vision for Front-End Software
Installation The Intercompany Integration Solution for SAP Business One Version 2.0 for SAP Business One 9.1 Welcome to the course on the installation.
LCLS Commissioning & Operations High Level Software
EPICS Version 4 Abstract:
Object Oriented Analysis and Design
Control System Studio (CSS)
SISAI STATISTICAL INFORMATION SYSTEMS ARCHITECTURE AND INTEGRATION
EDDI12 – Bergen, Norway Toni Sissala
A Virtual Implementation of VELA (CLARA)
ICS update 7th Experiment Control Workshop
PLCs integration into the ICS
Channel Access Concepts
Automation of Control System Configuration TAC 18
European Spallation Source Archiving Service
Chapter 1 The Systems Development Environment
Banafsheh Hajinasab Based on presentation by K. Strnisa, Cosylab
Operation of Target Safety System (TSS)
ESHAC #8 Safety Readiness Review Thomas Hansson, ESH
Channel Access Concepts
Update on Software Scope Control System Software
Presentation transcript:

Software Scope Susanne Regnell Group Leader Control System Software

Status - Work packages 2 and 3 - Software Work package scope – Controls software development, integration and deployment in the ESS operations environment Work package status – Many development activities have been started and have been ongoing for a long time (years) – ESS-wide requirements analysis and structured approach to identifying scope has been lacking – This means that the development efforts have gone on without central prioritization and review Sometimes in the hands of commercial suppliers without strong enough ICS supervision – With a new line manager since Q4 2015, this is changing Issues – Lack of ESS-wide requirements analysis has led to arbitrary prioritization of ongoing efforts – Lack of ESS-wide requirements analysis has led to arbitrary budget allocation onto activities Next steps – Systematic identification of “minimal scope” and hard prioritizations are ongoing – Packaging of control software products for in-kinding in order to balance budget spend 2 AlarmsMachine Protection System application ArchivingMachine sequencer Channel FinderPost mortem application Control System StudioPreventive Maintenance System Controls Configuration toolsSave Compare Restore Development environmentSoftware interlock system EPICSState and notification service Scripting frameworkSynoptic Web application Diagnostics applicationsFixed display framework Electronic checklist

Software scope: Data Flow Diagram

Software scope 2016 CCDB, Cable DB, IOC Factory, RBAC, Naming Service Calibration DB Alarm Service & Handler Control System Studio/BOY Channel Finder OpenXAL (online model and physics applications support Post Mortem Application Software Interlock System Save, Compare & Restore Archiving Service Machine Sequencer Scripting FwkFixed display FwkSynoptic Web applDiagnostics appl. Electronic checklist EPICS v4 adaptations for ESS MPS Configuration Application

Software scope: Controls Configuration Database (CCDB) Scope – Collects, stores and manages the (static) information of devices such as cameras, PLCs, IOCs, racks, crates etc. that will be in operation at ESS by defining their properties and relationships between these from the control system perspective. Status – Currently the scope of the CCDB covers a “plant model perspective”. Application is delivered in our production environment. Issues – Is the current application covering all use cases for the plant model perspective? – Currently there is no interface defined between CCDB and the Lattice DB (LinacLEGO) which is under the responsibility of the Accelerator division. Next steps – Review current scope, review GUI and evaluate the possible of extension of scope needed to cover the inventory aspect. – Maintenance. – No known dependencies to EPICS v4 (as compared to EPICS v3) 5

Software scope: Cable Database Scope – Cable Database – manages the information about cables that the ESS Machine Directorate’s Divisions are/will be responsible for. Depending on the CCDB for detailed information regarding the devices that a cable is connecting. Status – Application delivered in our production environment. Issues – Is current application covering all use cases? – Which cables are included? Where do we draw the line for which cables to include in our Cables DB? Next steps – Review current scope and GUI. – Maintenance. – No known dependencies to EPICS v4 (as compared to EPICS v3) 6

Software scope: Naming Server (ESS Naming Convention) Scope – A web application for users to generate and register names of devices and cables in the control system environment. Status – Application delivered in our production environment. Issues – Is current application covering all use cases? – Performance may need to be improved. Next steps – Review current scope and GUI. – Integration with LinacLEGO, Calibration DB, PLM system etc. – Maintenance. – No known dependencies to EPICS v4 (as compared to EPICS v3) 7

Software scope: Role Based Access Control (RBAC) Scope – Authentication and authorization service for EPICS Process Variables and Control System applications. Status – Application delivered in our production environment. Issues – Is current application covering all use cases? Next steps – Review current scope and GUI. – Maintenance. – No known dependencies to EPICS v4 (as compared to EPICS v3) 8

Software scope: IOC Factory Scope – IOC Factory – is responsible for managing (configure, generate, browse and audit) IOCs at ESS. Status – Scope is clear. – Application delivered in our production environment. Issues – N/A Next steps – Maintenance. – No known dependencies to EPICS v4 (as compared to EPICS v3) 9

Software scope 2016 CCDB, Cable DB, IOC Factory, RBAC, Naming Service Calibration DB Alarm Service & Handler Control System Studio/BOY Channel Finder OpenXAL (online model and physics applications support Post Mortem Application Software Interlock System Save, Compare & Restore Archiving Service Machine Sequencer Scripting FwkFixed display FwkSynoptic Web applDiagnostics appl. Electronic checklist EPICS v4 adaptations for ESS MPS Configuration Application

Software scope: Calibration Database Scope – Version controlled (?) storage and retrieval of Calibration data for devices. Status – Application not defined. Issues – Extend CCDB scope to cover also the requirements for the storage of Calibration data. Current recommendation from Chief Engineer is to not extend the CCDB-scope, but rather to build a new application to cover this need. Next steps – Define detailed scope as needed for the ESS/ICS project. – Investigate already existing solutions for storage of calibration data to decide if we can re-use something from the community (EPICS IRMIS is not re-usable according to Timo Korhonen). – Investigate if any EPICS v4 dependency. – If new application is needed, identify potential in-kind partner. 11

Software scope 2016 CCDB, Cable DB, IOC Factory, RBAC, Naming Service Calibration DB Alarm Service & Handler Control System Studio/BOY Channel Finder OpenXAL (online model and physics applications support Post Mortem Application Software Interlock System Save, Compare & Restore Archiving Service Machine Sequencer Scripting FwkFixed display FwkSynoptic Web applDiagnostics appl. Electronic checklist EPICS v4 adaptations for ESS MPS Configuration Application

Software scope: Alarm Service & Handler Scope – Strategy and service for Alarms handling for ESS. Status – BEAST is currently chosen as the ESS/ICS Alarm handler. – Work with the alarm service & strategy has been re-started with a re-cap meeting with GoalArt that has written an “ESS Alarm Strategy” document on our behalf. Issues – Requires a non-trivial internal effort to reach a common understanding of the alarms service structure and setup. Next steps – Survey alarm strategies at other facilities (e.g. SNS, CERN, PSI, DLS). – Establish a – Requirements, design, implementation, define a default configuration and test for/of the Alarm Service. – Identify in-kind partner to work with Alarms on our behalf. 13

Software scope 2016 CCDB, Cable DB, IOC Factory, RBAC, Naming Service Calibration DB Alarm Service & Handler Control System Studio/BOY Channel Finder OpenXAL (online model and physics applications support Post Mortem Application Software Interlock System Save, Compare & Restore Archiving Service Machine Sequencer Scripting FwkFixed display FwkSynoptic Web applDiagnostics appl. Electronic checklist EPICS v4 adaptations for ESS MPS Configuration Application

Software scope: Control System Studio (CSS) Scope/description – CSS is an open source component with an Eclipse-based collection of tools to monitor and operate large scale control systems, such as ESS. The CSS BOY framework will be used for the development of engineering screens. Status – No ESS-branch for CSS/BOY is currently available. – Integration team is currently using CSS/BOY off-the-shelf. Issues – No progress made after employee left in Employee has not yet been replaced, but recruitment is ongoing. Next steps – Install, create ESS-branch, define a default configuration and write installation manuals for CSS/BOY, CSS/BEAST and CSS/Archiver Appliance. – Investigate, plan, implement, test and install any possible changes needed for EPICS v4. – Investigate, plan and decide what contributions we can do to the CSS-community. 15

Software scope 2016 CCDB, Cable DB, IOC Factory, RBAC, Naming Service Calibration DB Alarm Service & Handler Control System Studio/BOY Channel Finder OpenXAL (online model and physics applications support Post Mortem Application Software Interlock System Save, Compare & Restore Archiving Service Machine Sequencer Scripting FwkFixed display FwkSynoptic Web applDiagnostics appl. Electronic checklist EPICS v4 adaptations for ESS MPS Configuration Application

Software scope: Channel Finder Scope – Generic directory service for EPICS Channels (with flat name space) to manage thousands of channels and to create lattice structures. Status – Channel Finder project fits ESS Project needs as far as we understand today. Issues – Different open source application servers and data bases are used, this may be a problem. GlassFish, TomCat), JBoss/Java EE, MySQL, PostgreSQL. Next steps – Investigate and determine what work is needed for the current Channel Finder to be fully usable for the ESS project. – EPICS v4 compatibility need to be verified. – Investigate what, if anything, can be done as in-kind. 17

Software scope 2016 CCDB, Cable DB, IOC Factory, RBAC, Naming Service Calibration DB Alarm Service & Handler Control System Studio/BOY Channel Finder OpenXAL (online model and physics applications support Post Mortem Application Software Interlock System Save, Compare & Restore Archiving Service Machine Sequencer Scripting FwkFixed display FwkSynoptic Web applDiagnostics appl. Electronic checklist EPICS v4 adaptations for ESS MPS Configuration Application

Software scope: Archiving Service Scope – Archiving for a EPICS v4 control system, storing millions of PVs in different stages and clusters. – Built in process to move data between stages, with the added capability of reducing the data as it is moved into storage. – Ability to cluster appliances and to scale by adding additional appliances to cluster. – Data retrieval performance focus. Status – Archiver Appliance has been evaluated and chosen as ESS/ICS Archiver Solution. – Integration team is currently using “Archiving off-the-shelf”. Issues – Performance for Data-on-Demand wave forms needs further investigation. Next steps – Install, create ESS-branch, define a default configuration and write installation manual. – Performance requirements need to be further investigated and handled. – EPICS v4 compatibility need to be verified. 19

Software scope 2016 CCDB, Cable DB, IOC Factory, RBAC, Naming Service Calibration DB Alarm Service & Handler Control System Studio/BOY Channel Finder OpenXAL (online model and physics applications support Post Mortem Application Software Interlock System Save, Compare & Restore Archiving Service Machine Sequencer Scripting FwkFixed display FwkSynoptic Web applDiagnostics appl. Electronic checklist EPICS v4 adaptations for ESS MPS Configuration Application

Software scope: Save, Compare & Restore Scope – Storage of a set of PV values, compare live values with saved sets of values and restore saved values. Current ICS design includes a golden snapshot, grouping PV’s into request files, highlighting changed values and database storage of the information. Status – Implementation of ICS Save, Compare and Restore is put on hold for further evaluation. Issues – It is not clear if the ICS Save, Compare & Restore design covers our use cases: e.g. we will have at least ~40 Beam/Machine modes, that each would need to store its “golden snapshot”, possibly with version control. Next steps – Install CASR as first solution. Judged to be a viable solution for LEBT & RFQ commissioning (i.e. until ~March 2018). – Evaluate options and choose long term solution: ICS design for Save, Compare & Restore – implementation put on hold. Investigate MASAR, why did we choose to go with our own implementation? OpenXAL SCORE – Investigate what could be done as in-kind. 21

Software scope 2016 CCDB, Cable DB, IOC Factory, RBAC, Naming Service Calibration DB Alarm Service & Handler Control System Studio/BOY Channel Finder OpenXAL (online model and physics applications support Post Mortem Application Software Interlock System Save, Compare & Restore Archiving Service Machine Sequencer Scripting FwkFixed display FwkSynoptic Web applDiagnostics appl. Electronic checklist EPICS v4 adaptions for ESS MPS Configuration Application

Software scope: Other applications – Fixed Displays Framework Simple screens to display information on consoles, overhead screens, TVs etc. – Synoptic Web Applications Applications running in a web browser where the user has a schematic view of the accelerator accessing static or live data, e.g.: – Configuration data from the CCDB and/or from LinacLEGO (Lattice DB). – Result of a physics simulation based on the outcome of OpenXAL. – Layout of racks and cables based on information from the Cable DB. – Electronic Checklist(s) – should this even be in ICS Scope? Checklists describing e.g. installation procedures, hardware installations. Installations will be reported in real-time and it will be possible to query the status of a given installation, identify problems, report issues, etc. – Expert GUI applications, e.g.: Machine sequencer – short term solution is to use the CSS/BOY-screens for initial commissioning. Diagnostic applications – Integrated system logs, centralized monitoring of SW performance, preventive maintenance, infrastructure management. MPS Configuration Application – Scripting frameworks (promotion of a main scripting language: Python) Python modules to interface and access all ICS services. 23

Software scope 2016 CCDB, Cable DB, IOC Factory, RBAC, Naming Service Calibration DB Alarm Service & Handler Control System Studio/BOY Channel Finder OpenXAL (online model and physics applications support) Post Mortem Application Software Interlock System Save, Compare & Restore Archiving Service Machine Sequencer Scripting FwkFixed display FwkSynoptic Web applDiagnostics appl. Electronic checklist EPICS v.4 adaptations for ESS MPS Configuration Application

Software scope: OpenXAL Scope/Description – Framework for development of Control room applications. OpenXAL is an open source development environment Java library for creating accelerator physics applications, scripts and services. Status – ICS is providing the OpenXAL framework, developing an online model of the accelerator and supporting the Beam Physics group for their development of physics applications. Issues – Beam Physics will need to switch person working with the physics applications again, due to parental leave. Will most likely cause delays, and more work on our part (ICS). – OpenXAL is today EPICS v3 compliant, if we are to make a full conversion to EPICS v4 it is going to cost us both lead time and money. – Before we have the ESS machine up and running with EPICS v4, we have no way of testing an EPICS v4 fully compliant OpenXAL. Next steps – Continued work with the online model. – Continued support to the Beam Physics Group for their development of the physics applications. – OpenXAL integration with the Python Scripting Framework. – Decide how to move forward with EPIC v4 for OpenXAL from an ESS point of view. 25

Software scope: EPICS v4, ESS EPICS v4: – IOC Core: List of ESS/ICS records needed and general configuration of the IOC needs. – Define ESS EPICS base life cycle. – Transition to EPICS v4: EPICS modules has to be added to the EEE (ESS EPICS Environment) Calibration data needs to be modified IOCs and clients (CSS, Archiver, Alarms, …) need to be re-factored. OpenXAL: pvAccess client needs to be changed (minimum) – pvAccess clients can read data for CA-servers. pvGateway is under development – on track. We have testing planned. 26

Software scope 2016 CCDB, Cable DB, IOC Factory, RBAC, Naming Service Calibration DB Alarm Service & Handler Control System Studio/BOY Channel Finder Post Mortem Application Software Interlock System Save, Compare & Restore Archiving Service Machine Sequencer Scripting FwkFixed display FwkSynoptic Web applDiagnostics appl. Electronic checklist OpenXAL (online model and physics applications support) EPICS v.4 adaptations for ESS MPS Configuration Application

Software scope: Post Mortem Application Scope – Handle the collection, storage and retrieval of Post Mortem data, needed to be able to understand what went wrong when the accelerator had to shutdown. Status – Beam Interlock System architecture is not mature enough to start looking at Post Mortem application system requirements just yet. Issues – N/A Next steps – Software, integration and protection teams need to discuss how to move forward on this topic. 28

Software scope: Software Interlock System (SIS) Application Scope – To be defined. Status – Not started. This system need to be developed after the installation of the accelerator and the first beam event. Issues – N/A. Next steps – Timo Korhonen to communicate and discuss topic with Annika Nordt. 29