1 / 17

Zornitsa Zaharieva , BE-CO-DA on behalf of the CCS team CO3 Meeting 5 December 2013

Zornitsa Zaharieva , BE-CO-DA on behalf of the CCS team CO3 Meeting 5 December 2013. Controls Configuration Service (CCS) - Renovation Aspects I mportant for the ACCOR Project & the Equipment Groups. Contents. Introduction to CCS

mahon
Download Presentation

Zornitsa Zaharieva , BE-CO-DA on behalf of the CCS team CO3 Meeting 5 December 2013

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Zornitsa Zaharieva, BE-CO-DAon behalf of the CCS team CO3 Meeting5 December 2013 Controls Configuration Service (CCS) -Renovation Aspects Important for the ACCOR Project & the Equipment Groups

  2. Contents Z.Zaharieva 22.04.2013 Controls Configuration Service - LS1 Plans EDMS doc: 1281984 Introduction to CCS Migration of the configuration data for the renovated Controls Devices CCS support for the ACCOR baseline CCS support for renovation changes in LSA in 2014 Conclusion 2

  3. Controls Configuration Service • Provides the configuration management facilities for the Controls System components for all accelerators • A collection of processes, tools (editors), APIs and a common repository (DB) for configuration data • Presents an integrated, trusted, coherent and a centralized viewof the Controls System, which is used as a configuration source by all of its components (e.g. CMW, Front-Ends, Timing, Diamon, Laser, etc.) • Integrated, cross-domain configuration data for various controls devices frameworks – FESA, Hardware, Virtual, GM, SL

  4. Controls Devices Configurations Migration • ACCOR Controls Devices Renovation • GM  FESA • FESA2  FESA3 • GM  Hardware (FGCs, Vacuum, etc.) • GM  Virtual • In order to speed up the migrations of the configuration data and not to lose existing configurations a dedicated process has been put in place • Input (migration maps) required in order to perform the migrations • Without the migration maps it is not possible to perform the migration • Only the equipment expert (class responsible) can provide the map (the key)

  5. Controls Devices Configuration Migration Process Controls Configuration LSA Device Properties migration map Devices migration map Class Properties migration map Reference settings instance level properties / fields equip relations, cable signals, module interrupts, sub-addresses, etc. working sets, knobs, metaproperties FECs Generations • Challenges: • There are a lot of manual interventions and coding that the CCS team needs to perform for each class migration • It is not possible to handle all requests simultaneously due to limited resources • Solution:to plan the migrations and to space them in time • The first time a given class & devices from it need to be migrated – 4 weeks notice period • Subsequent migrations of devices – 2 weeks notice period

  6. Support for the Configuration Migration Process • A dedicated editor to collect the input – Migration Maps Editor • User-friendly features - notifications, bulk loading capabilities, etc. • Objective:Automate as much as possible the migration process

  7. Gathered Experience in 2013 • 3 Successful Pilot Dry-Runs – Linac2, AD, Booster • The CCS team collected a lot of input for the required work and for the optimization of the process • Essential to work in close collaboration with the class responsible in order to perform the migrations • The speed of the migration process varies depending on the complexity of the class being migrated • The most difficult migration case so far – GM POW-V class • Special ‘Thank you!’ to Daniel Calcoen • It is not possible to completely automate the migration process

  8. Controls Devices Migration 2013 Results • Reports with the migrated devices status and statistics are available in the Controls Configuration Data Browser (https://cern.ch/service-co-config ) • Total number of migrated devices – 2742 • PTIM-V to LTIM (GM -> FESA2/3) - 1303 • POW-V to PowM1553 (GM -> FESA3) – 1078 devices • POW to FGC_61 (GM -> HARDWARE) – 104 devices • VGAUG to PVPUMP (GM -> HARDWARE) – 96 devices • …..

  9. Controls Devices Configuration Migrations Plans for 2014 Example: CO Generic Classes schedule from Steen • Migration of Timing Classes from Jean-Claude Bau, Xavier Piroux • Continue with the migration of PTIM-V and LTIM from Ioan Kozsar • Migration of the CO Generic Classes from Steen Jensen • Migration of Pow classes from Daniel Calcoen (PowRs422, etc.) • Migration of QPS classes from Herve Milcent (wipe out everything and insert) • ………… • If you are planning to migrate configuration data from classes and devices – contact the Controls-Configuration.Support@cern.ch as soon as possible in order to look into the details

  10. CCS - ACCOR Baseline end of 2013 • Continue with the support for the ACCOR FEC renovations • Refactoring of the Controls Configuration Hardware area • Upgrades and improvements of the db model • New Hardware Configuration Editor (migrating from obsolete technology) • Support for new driver’s configurations functionalities and other new features • User announcements and tutorials will be sent • Release – Dec. 2013

  11. CCS - ACCOR baseline end of 2013 • Integration of the FESA3 Configuration model into the Controls Configuration Service • Providing integration (coherency) with the rest of the systems using the Controls Configuration (e.g. Timing, FEC Configurations, RBAC, etc.) • Support for the FESA releases v.3.1 – 01.07.2013, v.3.1.2 – Dec. 2013 • Reengineering of the Controls Devices -Virtual Devices framework • Extensions for Diamon configurations • Release – Dec. 2013

  12. CCS Data Propagation to LSA in 2013 FECs Generations • The CCS provides a level of abstraction/isolation between LSA and the class-properties device model • Example: LSA uses the FGC aliases and not the device names, etc. • A subset of the class-properties and devices data from CCS is propagated to LSA • Controls Configuration uses ~ 5 100 000 parameters • LSA uses ~192 000 parameters • Usually the properties and devices for LSA are propagated manually • Working Sets and Metaproperties are entered in the Controls Configuration and propagated to LSA

  13. CCS Renovation Changes Affecting LSA in 2014 • Increase the level of abstraction and restrict further the data set that LSA will be able to see • Improve the robustness of the model and avoid problems in LSA due to configuration changes that should not affect it • Transfer the working sets and metaproperties to LSA as they are seen as extension of the settings model (for non-GM devices) • Introduce a flag for all devices and properties in the Controls Configuration (FESA, Hardware, Virtual, GM, SL) to designate which ones should be published to LSA • Based on the flag the propagation of data will happen instantaneously (smooth process) • There will be no need to use the manual data propagation tool • When the flag is introduced all devices and properties currently in LSA will be set with it • Equipment Experts/Operators will need to take care only of subsequent changes

  14. Conclusion • Together with the ACCOR team we have established processes in order to perform and to optimize the device migrations • Proven to be working successfully with the Pilot Dry Runs • Working together with the equipment expert is essential for the successful and on-time migration • Plan the migrations and take into account the notice periods • The Controls Devices configuration data migration requires quite a lot of resources and planning from the CCS team • Contact the Controls-Configuration.Support@cern.ch - tailored support • The CCS is supporting the agreed milestones in the ACCOR baseline • Improvements to the Configuration model and tools in 2013 and 2014 introduced gradually

  15. Questions Thank you for your attention!

  16. Controls Configuration Service Overview Set of 16 Data Editors >250 editing forms - Strict authorization 250 users Browsing Tools220 reports covering all areas of the CCS > 300 users from 4 departments Java APIs Beam IntelocksConfig SMP Config Directory Service Logbooks publishing Controls Configuration DB PL/SQL APIs Drivers Gen, Timing, FESA, etc.Pro*C scripts FECs configs, GM, etc. LASER DB (Alarms) LSA DB Layout DB XML configfiles, Binaries, etc. RBAC CMW Diamon Fixed Displays...

  17. Controls Configuration Logical Domains Role-Based AccessConfiguration AlarmsConfiguration Accelerators Timing System Config Diagnostics & Monitoring Configuration Working Sets & MetapropertiesConfig Power ConvertersConfig PICConfig WICConfig CMW Config OasisConfig Computers Configurations ,Hardware modules ( FECs, PLCs,PVSS servers, etc.) Controls Device Classes & Properties Models (FESA, GM, Hardware, Virtual, SL frameworks) Video Observation System Config Beam Interlock System Config Drivers Config Common ConsoleManager Configuration Fixed Displays Configuration QPSConfig Safe Machine Parameters Config Z.Zaharieva 22.04.2013 Controls Configuration Service - LS1 Plans EDMS doc: 1281984

More Related