Toward UNICOS Major Tasks to be Done Leonid Kopylov TE-VSC-ICM

UNCOS convergense p.2 UNICOS convergence: Main goal for coming years, after completion of LS1 Large amount of work to be done The work to be done by team, not by one person The whole work process must be manageable, with estimations, planning, milestones… As a first step: define list of tasks to be solved on the way to final implementation Development for PLC is (almost) not mentioned because of lack of knowledge

Task grouping p.3 Grouping of tasks to be done The full chain of object type support, starting from specification, through specs file, UAB and PLC/PVSS code Single data source (database), from which both UNICOS specs files and other configurations are produced (ref. Andre’s presentation) Mutually agreed modifications/additions to existing UNICOS CPC code Dedicated vacuum control package, built on top of UNICOS framework and applicable to any vacuum control system Functionality specific to particular machines New Object Types Data source + specs generation Main PVSS functions (UNICOS - integrated) Extended PVSS functions (vacuum package) Very special PVSS functions (machine specific)

New Object Types p.4 New Object Types The task seems to be very heavy Lack of experience Advanced UNICOS courses May be not so difficult, after gaining some experience? Compare to development of new type of existing framework (master DB, export, C++ and PVSS code…) Main steps of development: Specification + Detailed Design Document Device Type Design + Specs Integration UAB integration Implementation in PLC I just don’t know what is behind Implementation in PVSS DP type Check/Import/Export/Delete Front end device functions Etc.

New Object Types p.5 Performance questions? Will UI performance degrade when using UNICOS objects/widgets? If yes – deviations from UNICOS baseline should be acceptable In particular – widgets vs. Qt icons may be reconsidered again First tests of UI performance can be done even on existing objects

Data Source + Specs generation p.6 Data Source + Specs Generation See presentation by A. Rocha

Main PVSS Functions (UNICOS-integrated) p.7 The order of tasks is arbitrary Package building tool Everything shall be organized in packages which can be installed/updated the same way UNICOS is installed into PVSS project Learn by vacuum team Import into PVSS + UAB UNICOS’s style of work: one specs file/import operation per PLC Will make problems for vacuum systems with many PLCs See presentation by A. Rocha Devices ‘not connected’, ‘not controlled’, ‘hidden’ Special functionality for PVSS only Not Connected = device is malfunctioning, can not be repaired immediately (probably, forced mode of UNICOS object?) Not Controlled = there is no connection to periphery (by design), still we want to show it to operators in UI (probably, local devices) Hidden = device working properly (or not), but we don’t want to show it to operators in UI UNICOS core has no support for such scenarios (?)

Main PVSS Functions (UNICOS-integrated) p.8 Devices ‘Blocked OFF’ Something wrong about device, the state is set by expert Only experts are allowed to switch ON device in such state Only experts are allowed to remove ‘Blocked OFF’ state It is clearly visible from device shape that device is in this state There was preliminary discussions with EN-ICE, using DPE lock mechanism UNICOS Device Tree UNICOS implementation = 2 level of hierarchy Vacuum control needs more:  Main Part  Sector  Device Nature  Device There was preliminary discussion with EN-ICE, creating domain hierarchy in UNICOS

Main PVSS Functions (UNICOS-integrated) p.9 Device List Building/Presentation Selecting devices to be shown in the table By status By analog value (check if value is above given limit) By analog value grow (check if value has grown by factor of X in last N hours), not to be a part of UNICOS core? (new) By non-empty comment for device, either now or in given dates range in the past. (new) By device ‘control status’ in PVSS (Not Connected etc.) The way resulting table is displayed Snapshot (UNICOS behavior) Live view (table is updated with fresh data from periphery) Snapshot for selected moment in the past (too heavy for UNICOS) Table in vacuum application has more columns, auxiliary – like sector of device, DCUM…

Main PVSS Functions (UNICOS-integrated) p.10 Group Actions Under development for UNICOS (?) Special processing of ‘Blocked OFF’ devices (silently skip) Comments on Devices Under development for UNICOS (?) Possibility to Mask Alarms for LASER For individual device For all devices in selected sector(s) Access Control Extend number of privileges available (can be achieved with domains) ‘admin’ is a privilege for system administrator, not for users State History (vacuum) vs. Event History (UNICOS) Does the way values are archived in UNICOS allow to build state history? May be event history will be better for vacuum users? Both!

Main PVSS Functions (UNICOS-integrated) p.11 Replay of Archived Data Requires support by widgets, faceplates, profile view Requires inter-panel communication Mobile Equipment Everybody know what is this No ideas on how to implement this in UNICOS framework It looks like this can be combination of ‘hidden’ devices plus some more code around this Retrieving archived values for the case when device migrates from one DP to another will not be a problem with ORACLE archiving where data can be identified by alias SMS Notifications Configurable by end users (Relatively) free criteria specification Different users specify different criteria to the same device (for example, pressure limits) UNICOS uses PVSS alarms for notification – can this be used to fulfil vacuum control requirements?

Extended PVSS functions (vacuum package) p.12 Clean up usage of custom DLLs EWO and CTRL DLLs are allowed Other custom DLLs shall not be used Requirement comes from ‘standard server’ configuration Implementation is not clear yet Machine Layout for Main View Built automatically based on geometry data Represents ‘the very main’ state of vacuum First prototype to be used with UNICOS exists Automatically Built Synoptic Back to old solution: place in panel other panels (UNICOS widgets) Move device type specific logic from C++ to PVSS code Problems foreseen: Smooth scrolling (no good ideas for the moment) Resizable view (will come with next PVSS version) Performance Some ideas by Piotr: Consider using embedded module Web EWO + “widgets” implemented in javascript. This is, probably, in line with general PVSS development towards web UI, UI on mobile phones etc. Not 100% sure…

Extended PVSS functions (vacuum package) p.13 Automatically Built Sector View Very similar to synoptic view ‘Summary of VPIs in sector’ can be considered as PCO Can this ‘PCO-like’ behavior be implemented in PVSS only? Device List for VMR Very similar to ‘normal’ device list More columns Specific way to build/save to file/display Possibility to save resulting list as a reference Fast Archiving Sessions New solution to be developed anyway – after switching to ORACLE archiving Miscellaneous Device-Specific Functions Statistics of PP and TMP operations Statistics of valves operation Access zones, valve control etc.

Very special PVSS functions (machine specific) p.14 Beam Parameters Used in LHC control May be required for other machines Based on external data sources (CMW, DIP) Calculation of sector pressures for CRYO Produce one value per sector based on values of several gauges Looks more simple compared to previous tasks… …provided previous tasks are solved!

Resources p.15 Permanently growing list of tasks in VTL

Leonid Kopylov