1. SCADA Application Service updates in TS1
Rafal Kulaga BE-ICS-SDS

2. What is SCADA Application Service?
WinCC OA applications, mostly based on UNICOS and JCOP frameworks
Various domains: CRYO, Vacuum, CV, GCS, Electricity, QPS...
230 applications on 120 servers and constantly growing
Server side: CentOS 7 only (CS-CCR-* machines)
Client side: CentOS 7 consoles (CCC and other control rooms) and Windows Server 2008 R2 terminal servers

3. Domains, servers and contact persons
Application domain
Number of servers
BE-ICS-SDS contact
AWAKE 1
Rafal Kulaga
CIET 12
Lukasz Goralczyk
CIRCUIT
Brad Schofield
COLLIMATORS
Cryogenics 18
Cooling & Ventilation 9
DSS
Giulio Morpurgo
Electricity (PSEN) 2
Jean-Charles Tournier
ELEVATORS
Jonas Arroyo Garcia
Experiments Cooling 4
Experiments CRYO 15
GCS 5
Application domain
Number of servers
BE-ICS-SDS contact
IT Temp. Monitoring 1
Riku-Pekka Silvola
MCS 9
NA62 3
Piotr Golonka
PIC
Jonas Arroyo Garcia
QPS 16
REMUS 2
SM18
Lukasz Goralczyk
SURVEY
Rafal Kulaga
TE-EPC
Jean-Charles Tournier
TIP
Vacuum 7
WIC
Brad Schofield

4. Plans for TS1 Update WinCC OA 3.15 to the newest patch on:
CS-CCR-* Linux servers
Windows operator consoles
Linux operator consoles in the CCC and other control rooms
Review and optimize medium-term Oracle archives for WinCC OA systems

5. Updating server-side WinCC OA 3.15 – motivation
Vast majority of servers are running WinCC OA 3.15, deployed during EYETS
A few problems with currently used version of WinCC OA 3.15 have been discovered
We were able to find workarounds for most of them...
... but installing the newest stable patch version of WinCC OA 3.15 ( ) is the long-term solution
Apart from that, the new patch adds some long-awaited features

6. Updating server-side WinCC OA 3.15
Patching during TS1 will be organized in an opt-in, fine-grained fashion
Interventions are expected to take at most 1 hour per server, including making application backups and validating applications after the update
Exact date and time for update of each server is determined with people responsible for applications
Feedback expected before 26th of June, after that upgrades will be reported to SUWG and TIOC
Simple rollback in case of problems – reinstallation of previously used version and restoration of application backups

7. Updating WinCC OA 3.15 on user consoles
User consoles doesn’t have to be updated together with the server side (compatibility between different patches)
Windows terminal servers
Updates coordinated and performed by Uwe Epting (BE-ICS-CIC) and Luigi Gallerani (BE-CO-IN)
Linux consoles in CCC and other control rooms
Updates coordinated and performed by BE-CO-IN
Very simple rollback in case of problems – reinstallation of the previously used version
Console updates are announced to users separately from the server-side updates

8. Optimization of medium-term Oracle archiving
WinCC OA applications archive to medium-term Oracle archive
From there, selected signals are transferred to LHC Logging
Review of medium-term archiving requirements performed before EYETS
Configure for how long data is available, e.g. for trending and alarm history
Optimizing data retrieval performance by adjusting data storage settings
The interventions are transparent for users and will be performed for all applications
WinCC OA application
Selected signals
Medium-term archive
Selected signals
LHC Logging

9. Summary
Update to the newest stable version of WinCC OA – optional action that involves downtime
Input from people responsible for applications expected by 26/06
Review and optimization of medium-term Oracle archiving – fully transparent to users
Full schedule of the work to be performed during TS1 will be ready in the middle of next week

10. Thank you for your attention!
Any questions?