CV PVSS project architecture

Outline Remote access Access when no network Log in computer Log in PVSS Availability LASER, Supervision: upgrade: components, OS, PVSS. Development of applications and integration

Remote access Req.: access to the UI inside TN, from CERN GPN, outside CERN EN/ICE: same as for other project From TN: console, start CVOP CCM From CERN GPN: log in trusted computer VPC or terminal server, start CVOP CCM Outside CERN: log in cernts and same as from CERN GPN

Access when no network Access via touch panel Pros: Cons: SCADA Data Server OWS in local and central control room TN Ethernet Touch panel PLC Access via touch panel Pros: Direct access to the PLC Can be configured remotely Cons: Synoptics in PVSS and touch panel A change in IO address implies an update of the synoptics

Log in computer In Windows OWS, VPC, terminal server VPC: reserved for developers with NICE user name, no service account Terminal server: reserved for operation with service account NICE user name, no service account Service account used in the DS.

Log in PVSS Req.: log in with NICE user name, list of user may vary regularly A central project linked to all CV projects with AC Server, list of users, group, domains and privilege downloaded to all the linked project Pros: no need to configure users, group, domains, privilege, association user/domain/privilege in each project Cons: all the domain of all the application in all DS. The domain list must be limited, typically few identical domains in all application

Accessibility LASER, Supervision Req.: Access to the Supervision at any time if needed also during technical stop, Christmas, maintenance period, operation Alarm sent to LASER Unavailability of the Supervision or the LASER accepted but not at the same time

Availability LASER, Supervision: downtime based on more than 5 years experience in the LHC reason periodicity Down time consequence remarks Major upgrade of PVSS or DS hardware 5 years 1 day per DS No supervision Maximum 5 DS at a time Major upgrade of PVSS 3 years 4 hours per DS Can be combined with OS upgrade and component upgrade with no extra down time OS upgrade, OS patch installation, firmware upgrade 1 year or less depending on the security issues 30 minutes Can be combined with PVSS upgrade with no extra down time PVSS upgrade 1 year or less depending on the issues Can be combined with OS upgrade with no extra down time Upgrade of components 6 month or less depending on the issues No UI Could let the communication with the PLC active if the upgrade has no impact on the drivers and PVSS00crtl Can be done in many project at the same time with no major extra time.

Availability LASER, Supervision: upgrade component, OS, PVSS Redundant SCADA Data Server with Laser SCADA Data Server no Laser OWS in local and central control room TN Ethernet TSPP polling PLC Pros: No interruption of the LASER interface (except rare cases) Smooth upgrade of LASER and Supervision interface Cons: Polling from the LASER DS: each DS does a polling: time stamp from DS not from PLC LASER interface not ready in redundant mode

Development of application Req.: small application, PLC not always connected to the network, local supervision Proposal: A PVSS generic project (template) for Windows XP (Windows 7) used for commissioning Procedure: Use the template with to commission the application When the device configuration is OK, export and redo spec Import in Linux DS & connect to the PLC Pros: can do commissioning even without network Cons: 2 imports. Copy manually the synoptics from the Windows local PC and Linux server Export the trend/window tree and import it in the Linux DS

Integration into DS Req.: no major perturbation on running project, running application should not be re-commissioned when commissioning new application, no access to device of other project everywhere in UI, no development of customized interface. BE/CO constraints: Little place in CCR 2011: only new 8 DS acceptable More DS means: cabling, new IP, cooling, powering, etc. Virtualization not yet operational in BE/CO environment

Integration into DS Few machines, multi-project, many application per project, different driver, valarch, whenever possible Pros: Maintenance, installation, etc. easier (less DS) OK with BE/CO constraints Cons: No availability during upgrade OS, PVSS Note: with redundant LASER, req. availability OK Limited availability during upgrade of component Note: in minor upgrade one can think of keeping driver and PVSS00ctrl running, stop only the UI. UI no access to devices of other application not ready Note: this can be added in UNICOS, and so this will required very little development to deploy a new application interface.

Who does what? New PVSS project or application means different person involved Creation of the project, archive, etc. Installation, connection MOON Import device: Laser: SystemIntegrity, optimizing the archive, final step, etc.

Any questions ?