ESS Integrated Control System Software Core Components S.Gysin

ICS Work Packages and Software WBSWork package leaderWBS Name INTCSSGarry TrahernIntegrated Control Systems INTCSS.1Requirements, Architecture and Design INTCSS.2Leandro FernandezPhysics Core Components INTCSS.2.1Machine Model INTCSS.2.2High Level Applications INTCSS.3Suzanne GysinSoftware Core Components INTCSS.3.1Configuration Data Management INTCSS.3.2Control System Services INTCSS.3.3Naming Convention INTCSS.4Daniel FernandezHardware Core Components INTCSS.5Annika NordtProtection Core Components INTCSS.6Miha RescicIntegration Support INTCSS.7Control System Infrastructure INTCSS.8Management INTCSS.9Project Milestones

WU3.1 Configuration Data Management (ICS Databases) Scope: The collection, storage, and distribution of configuration data. What type of data: – static data needed to install, commission, and starting up the machine – Accelerator, Target, Neutron Instruments, and Conventional Facilities The Work Unit consist of: 1.data repositories to store the data 2.software tools to read/write/modify and export the configuration data

Organization of data Device Configuration Database (DCDB): The configurations files for the EPICS IOC’s. Cable Database : Static information relevant to cables and connections Lattice Database (BLED): This is an import of the simulation using Tracewin and additional elements from Beam Diagnostics. Controls Configuration Database (CCDB): Static, physical attributes of the devices in the scope of the ICS

Device Configuration Database DCDB Stores the configuration files for the EPICS IOC’s Software tools: – Ability to create template for devices with multiple instances (BPM) – Ability to store a device’s configuration file from an IOC – Ability to down load a configuration file to an IOC Candidates: – ITER’s SDD – ESS/Cosylab custom Excel based tool Timeframe: – January 2014: decision and high level design – 3Q 2014: first release Plans for Uppsala test stand: – Not needed – 2015 – Part of the vertical integration test

Controls Configuration Database Contains the physical attributes of a specific device. (barcode, location, status calibration test results. What is included: – Control Boxes, MPS devices, PPS devices. Devices controlling vacuum, RF, Cryogenics, target, neutron instruments, and conventional facilities. Typical question the configuration database can answer are: – Has BLM number XYZ been installed and calibrated? – What is the serial number of the power supply that failed and needs to be replaced? Timeframe: – Requirements are written and approved, design is starting Plans for Uppsala test stand: – Not needed – 2015 – Candidate for vertical integration test? It will be used for the series testing.

Lattice Database (BLED) Contains the ESS Accelerator configuration as it is simulated prior to being built. It includes the location and physics data for: – All accelerating structures – Beam diagnostics – Vacuum – Stubs for RF wave guides Typical questions the Lattice Database can answer: – How many BPM’s are in the spoke section? – What is the location of the 3 rd spoke cryomodule? Timeframe: – Version 1 is deployed and operational – October Lattice will be imported and available – Requirements are in progress – Lattice Browser is in progress Plans for Uppsala test stand: – Not applicable, except to extract information.

Cable Database Contains the attributes of cables and their connectors. What is included: – Cables for Control Boxes, MPS devices, PPS devices. Devices controlling vacuum, RF, Cryogenics, target, neutron instruments, and conventional facilities. – Equipment destined for the ESS site including the local test stands. Typical question the configuration database can answer are: – Which devices are connected to port A of device SSSS- BBBB:DDDD-III ? – How long is the cable connecting HBL-PBI:BPM-01a to its power supply. Timeframe: – Requirements are written and approved – Design is starting Plans for Uppsala test stand: – Not applicable, since it is site specific

Configuration Data Management All databases are: – Integrated, such that a user does not have to switch applications to browse one or the other database – use the ESS naming convention – provide version control – protected by the ICS Authentication and Authorization service – accessed is via the provided API (restful) and the Web based GUI – developed using standard technology – Physically located at DMSC We are actively working with DISCS, a collaboration to standardize databases for control systems. Other members are BNL and FRIB.

WU 3.2 Control System Services Scope: provides the common software services to the users of the control system – Applications that benefit from being centralized and/or benefit from being standard and implemented only once. – Includes the applications and repositories that provide the service – Includes Accelerator, Target, Instruments and Conventional Facilities – Construction project only (no operations)

Operator Screens, Archive, and Alarms ESS-CODAC – CSS (EPICS control system studio) – Operator Screen GUI builder (BOY) – Short term archive/logging (BEAUTY) – Alarms (BEAST) – Logbook (Olog) Timeframe: – 1Q 2014 : package available for test stands Plans for Uppsala test stand: – 2014 Test: available, and can be used for remote access. -Candidate for the 2015 vertical integration test

CSS: Operator Screen

BEAUTY: Data Browser

BEAST: Alarm Service

Authentication and Authorization Role Based Access Control for any PV and possibly other resources – Propose to use CERN’s RBAC and extend it to EPICS product – Concise API for any Channel Access client (i.e. application) – Centralized authentication of users via Kerberos – Centralized management of user assignment to roles, and permission to read/write PV – Authorization by roles/location/beam mode in the IOC server. – Timeline: started, requirements and architecture by 1Q Candidate for the 2015 vertical integration test

Long Term Archive PV storage for a longer time ( 1 year – 5 years?) Smaller set of process variables, less frequently Write once, read often, optimized for fast read (data warehouse technology) Candidates: – SLAC’s archive service – CSS with Cassandra back end Timeframe: not started Candidate for the 2015 vertical integration test

Save, Compare and Restore -Save machine settings, -Compare live values with saved values -Restore saved values. -Features include -a golden snapshot, -grouping PV’s into snapshots, -grouping snapshots into machine configurations, -highlighting changed values and database storage of the information. -Essential during commissioning -Candidates: MASAR -Timeline: requirements are complete, development has not started. -Candidate for the 2015 vertical integration test

Other Control System Services Timing System support (DOD) – Archiving on a trigger from the timing system Post Mortem support – High volume archiving on trigger before failure from the timing system – Safety related Maintenance Log – log of preventative maintenance Diagnostic Logging Service – Central index of diagnostic logs.

Control System Services Directory Service Finds PV’s based on search criteria Candidate – Chanel Finder Operations Logistics Beam statistics, run hours, shift summaries, down time, experiment schedules. Search Service Google like search on all ICS Naming Service EPICS PV to IP address/TCP port mapping Video Service Live image stream from instrumentations How large are the images?

WU 3.3 ESS Naming Convention Scope: provides the tools, repositories and processes to generate meaningful and consistent names for devices to be installed at ESS – Scope includes all of ESS – Name database includes 1000 items now – Definition of the naming syntax – Tools: WEB GUI to generate a name for a device and let the user browse the names Database to keep track of the names – Timeline: Naming Syntax has been defined Use to assign 1000 names according to the convention Next: develop the tools and database – 2014 Names are available – 2015 Candidate for Vertical slice test

Summary: candidates for vertical integration test – WU 3.1 Configuration Data Management: Device Configuration Database and Integrator’s tools Controls Configuration Database and tools – WU 3.2 Control System Services ESS CODAC : Operator Screens, archiver, alarms Authentication and Authorization Long term archive Save, compare and restore – WU 3.3 Naming Convention Naming tools Naming database Questions – Remote access for people at Lund and Saclay is essential. We can use ssh and vpn along with virtual machines? – Data repositories and applications reside at DMSC (Denmark), how is the network configured?