Software Developer for Vacuum Control System
J. Luis González Arias
TE-VSC-ICM
Abstract
Madrid, 07/03/2017
Example: Defining a connection between LHC valve interlock mux crate and a
TPG300 relay.
HCVRIVC001
The Vacuum Control System is composed of WinCC-OA SCADA (Supervisory
Control And Data Acquisition) applications on the supervision layer and of Siemens
PLCs (Programmable Logic Controller), which are directly connected to vacuum
devices. A custom made application automatically generates the configuration for
both SCADA and PLCs, the VacDB-Editor, which will be extended to automatically
generate documentation using equipment connections defined in the database
(VacDB). For this reason a redefinition of VacDB was performed, and data
concerning equipment connections was compiled.
To help with asset management activities, a new application has been developed,
VacDM, which ensures the consistency of several databases at CERN and also
provides an intuitive UI (User Interface) for managing label requests.
This poster shows the solutions developed, the architecture of the respective
systems and the main motivations for their development.
Introduction
HCVRGPT300
Steps:
1. Define the connector types (MasterDB-Editor).
2. Define the connectors available for each equipment type
(MasterDB-Editor).
3. Set the rules to allow the connection (MasterDB-Editor).
4. Create the connection (MachineDB-Editor).
 User Interface for managing the connections.
 Preventing data errors.
 Tracking changes (what, who, when).
VacDM
What is it?
VacDM is a web application which uses information from different databases. It
ensures that the equipment that users see in the Vacuum SCADA is available in
Infor EAM (Enterprise Asset Management), and that this equipment is declared with
the official descriptions defined in the Naming Portal. This synchronization is
automatic and ensures that all controlled equipment is taken into account for asset
management activities (creation of work orders, preventive maintenance, etc.)
VacDB
Infor EAM DB
The ICM (Interlocks, Control and Monitoring) section is responsible for the Vacuum
Control System of the different experiments at CERN.
SCADA
128 km of vacuum chambers across all accelerators
Pressure range from 10-4 to 10-11 mbar achieved by:
~3000 vacuum pumps
~3000 vacuum gauges
~500 sector valves
Naming Portal
As a software engineer I have contributed to two projects: developing the logic to
support connections for generating documentation automatically within the VacDBEditor, and extending the functionalities of VacDM.
VacDB-Editor
What is it?
VacDB-Editor is a desktop application which provides a UI (User Interface)
whereby users can set the different properties for each component in the vacuum
control system and later generate the configuration files for SCADA (Supervisory
Control And Data Acquisition) and PLCs (Programmable Logic Controller).
VacDB
MASTER
SCADA
SPS
Naming DB
Furthermore, VacDM handles the management of label printing jobs. When a user
requests labels, a printing job ticket is automatically created in JIRA (issue-tracking
tool) and the corresponding assets are automatically created in INFOR EAM with
the official description as defined in Naming DB.
My Contribution
The functionalities implemented in VacDM are:
 Managing label requests.
 Managing users and their roles.
 Managing label printing work.
 Managing the synchronization between VacDB and Infor EAM.
 Displaying user requests (my requests).
 Notification of users upon completion of their requests.
VacDB-Editor
LHC
Conclusion
CPS
LAYOUT DB
This application was implemented in two different editors:
• MasterDB-Editor: Tool to manage the generic information (equipment types,
control types, connector types, alarms, etc.)
• MachineDB-Editor: Tool to manage the specific information (equipment,
connections, racks, export utilities, etc.) defined for a specific machine (SPS,
LHC, CPS).
My contribution
 Extending the VacDB-Editor to work with connections.
 Modifying the database to hold connections data.
 Implementing the logic to support allowed connections.
 Keeping history of changes in equipment connections.
The VacDB-Editor has been finished and released. It provides an intuitive UI and
the logic to work with connections while guaranteeing the integrity of the data, in
addition to other improvements.
VacDM is in production and constantly evolving because other groups have shown
an obvious interest in using it.
The future plan is to implement the VacDB-Editor within VacDM to update the
technology.
Acknowledgments
I would like to thank: FTEC Program, CIEMAT, CDTI, TE-VSC-ICM (Technology Vacuum, Surfaces & Coatings - Interlocks Control and Monitoring) staff and
specially to my supervisor André Rocha for his support.
FTEC PROGRAM 2015