Beams Department The Newsletter does not necessarily reflect the views of the Beams Department The contributions solely reflect the views of their author(s) Issue 17 NEWSLETTER December 2016 Inside This Issue p. 1 Editorial – Ronny Billen p. 2 My Work Experience at CERN as a Student Trainee – Gerda Powell, Summer Trainee 2015 BE-BI p. 2 Communication and Informatics for Controls – Fernando Varela, BE-ICS p. 4 Controls Configuration Service – a challenge in usability – Lukasz Burdzanowski, BE-CO p. 7 Pushing LEIR limits to new horizons – Giulia Bellodi, Alexander Huschauer BE-ABP p. 9 Colonne Sécurité p. 10 Administration & Human Resources p. 11 Responsibility Changes p. 12 Newsletter contacts Champagne! Traditionally, the start of the year-end technical stop (acronymically referred to as YETS or even EYETS for the extended one) coincides with the even more traditional Christmas festivities. In general, beam operation gradually stops in the accelerator chain early December. Joyful events are organised to celebrate the upcoming holidays and shake off the accumulated stress. This allows us to get slowly “into the mood” towards an imposed but well-deserved relaxing break. This year is not an exception and the festivities started on Saint Nicholas’ Day at 5 pm in the CCC. Our DG Fabiola Gianotti honoured this event with her presence, joining Paul Collier’s praise to all staff for the impressive machine performance, resulting in outstanding physics results. Both recalled that the ambitious goals, set by the Management, are surpassed on all fronts, in all machines. Since this is becoming a yearly habit, expectations will be even higher next year… Of course, the accelerator complex only provides the “raw material” and the conditions to the Experiments, our clients. Judging by the big smiles and especially the bottles of champagne offered by the Experiments, we can all be proud to have very happy clients! In these last working weeks of 2016, there will be other occasions where we might meet and I’ll be delighted to say “Cheers” and toast with some bubbly liquids. In the meantime, I wish you and your family a Merry Christmas and a Happy New Year! Ronny Billen Editor, BE Newsletter Next issue The next issue will be published beginning of April 2017. Contributions for that issue should be received end of March 2017. Suggestions for contributions are always most welcome: simply contact your Correspondent (see last page). Editorial
Transcript
Beams Department
The Newsletter does not necessarily reflect the views of the Beams Department The contributions solely reflect the views of their author(s)
Issue 17 NEWSLETTER December 2016
Inside This Issue
p. 1 Editorial – Ronny Billen
p. 2 My Work Experience at CERN as a Student Trainee – Gerda Powell, Summer Trainee 2015 BE-BI
p. 2 Communication and Informatics for Controls – Fernando Varela, BE-ICS
p. 4 Controls Configuration Service – a challenge in usability – Lukasz Burdzanowski, BE-CO
p. 7 Pushing LEIR limits to new horizons – Giulia Bellodi, Alexander Huschauer BE-ABP
p. 9 Colonne Sécurité
p. 10 Administration & Human Resources
p. 11 Responsibility Changes
p. 12 Newsletter contacts
Champagne! Traditionally, the start of the year-end technical stop (acronymically referred to as YETS or even EYETS for the extended one) coincides with the even more traditional Christmas festivities. In general, beam operation gradually stops in the accelerator chain early December. Joyful events are organised to celebrate the upcoming holidays and shake off the accumulated stress. This allows us to get slowly “into the mood” towards an imposed but well-deserved relaxing break.
This year is not an exception and the festivities started on Saint Nicholas’ Day at 5 pm in the CCC. Our DG Fabiola Gianotti honoured this event with her presence, joining Paul Collier’s praise to all staff for the impressive machine performance, resulting in outstanding physics results. Both recalled that the ambitious goals, set by the Management, are surpassed on all fronts, in all machines. Since this is becoming a yearly habit, expectations will be even higher next year… Of course, the accelerator complex only provides the “raw material” and the conditions to the Experiments, our clients. Judging by the big smiles and especially the bottles of champagne offered by the Experiments, we can all be proud to have very happy clients!
In these last working weeks of 2016, there will be other occasions where we might meet and I’ll be delighted to say “Cheers” and toast with some bubbly liquids. In the meantime, I wish you and your family
a Merry Christmas and a Happy New Year!
Ronny Billen
Editor, BE Newsletter
Next issue
The next issue will be published beginning of April 2017. Contributions for that issue should be received end of March 2017. Suggestions for contributions are always most welcome: simply contact your Correspondent (see last page).
Editorial
2 Beams Department Newsletter Issue 16
My Work Experience at CERN as a Student Trainee When I found out last winter that I was accepted as an intern at CERN I was terribly excited, since I believed it to be quite impossible for a mature student to get a place as ‘stagiaire’, so nervous months of studying and preparing followed. I couldn’t imagine which work clothes to pack: would I need a blue or a white coat? Would I be sent home after a few days because of lack of knowledge? When I arrived in summer 2015 in the middle of a heat wave I was relieved to find a very relaxed but intense atmosphere, as for the dress code: we wore mainly shorts, skirts and shirts, no coats. I was placed in the Beam Instrumentation Group and their friendliness calmed me immediately. As a student with the Open University my studies and knowledge are quite abstract, my first time in a lab was actually at CERN, where we were investigating the properties of irradiated silicon in cryogenic conditions and looked for possible Schottky / Frenkel defects. Once I saw science in action it was much easier for my brain to accept all these ‘fantastical’ notions. I also learned a lot from the wire scanner team. I was incredibly lucky to be with the group in the control room when the calibration of the scanners took place, whilst the LHC was active. And it was fantastic to spend the last week in the Experimental Areas Group of the Engineering Department, where we learned to set up our own beam. What I liked most about this great experience was that my team leaders and other staff at CERN would not answer even one of my many questions with the dreaded remark: “Interesting question…”, which sometimes means the opposite. It is a sign of a great mind if someone much more learned than you looks at your ideas through his eyes and interprets it with his knowledge. It was great to be able to have all these experts around and get answers there and then instead of searching online for possible and often dubious answers, note down the expert’s correct answers and then go home and think about them and study some more, ready with more ideas for the next, usually very hot day. I also attended many Summer Student lectures. The ones on string theory were mind boggling. The lectures on proton therapy were very interesting to me, since I study physics and also cell biology and genetics, in view of working in biomedical / quantum biological research or maybe in the field of proton therapy.
I actually still find it hard to believe that I was at CERN for nearly a month, I need to look at the many photos I took to believe it. In summer many scientists are on holiday, so my favourite picture is of me in my own CERN office, writing an email on my own CERN email address, how cool can it get? It was just great to think and live science for a few weeks and quite hard to go back to normal, mundane life. As a single mum with 2 jobs and studying for 90 credits every year, I found CERN quite inspiring, I might be a scientist one day after all.
Gerda Powell, summer trainee 2015 in BE-BI and EN-EA
Visiting the Lab of the CERN Education, Communications & Outreach group (IR-ECO), testing a Higgs-field-simulation tool.
Communications and Informatics for Controls In this article we continue the series of presentations of the different sections of the Industrial Controls and Safety systems group (ICS). In this issue, the Communications and Informatics for Controls (CIC) section is presented. Together with the SCADA and Distributed Systems (SDS), and the Process Control Systems sections (PCS), CIC focuses on Industrial Controls for the accelerators, experiments and technical infrastructure. The CIC section, shown in Figure1, is composed of 15 members with mixed backgrounds (physicists, mathematicians and engineers) mostly involved in software development.
3 Beams Department Newsletter Issue 16
Figure 1, The CIC members proudly joined the BE Department in January 2016.
Similarly to other sections in ICS, the work of the CIC section is organized around four main axis: a) CERN-wide support of CANbus, the Data Interchange Protocol (DIP) and OPC; b) Development of applications for controls and contribution to the development of the ICS controls frameworks; c) Provision to the group of the computing infrastructure necessary for the development of controls applications; d) Development and research on Big Data and Cloud computing in collaboration with SDS and PCS. The CIC section plays an important role in the coordination of the Joint COntrols Project (JCOP) [1]; a collaboration between BE-ICS, the four major LHC experiments and EP-DT to develop the control systems of the detectors in common. The section also contributes actively to JCOP Framework development and, together with SDS and PCS, provides and is responsible for, the design, deployment and maintenance of a total of 33 Gas Control Systems (See Figure 2).
Figure 2, Main HMI of the Gas Control System for the ALICE TPC.
In the early 2000s, the JCOP collaboration decided to standardize the interface between front-end devices and SCADA software through the use of an industrial standard middleware: OPC. Just to stress the importance of OPC, the four major experiments have spent over 15 MCHF in their powering systems, therefore, a reliable SCADA/hardware interface is vital. The CIC section provides CERN-wide OPC support and handles communications with CAEN, Wiener and iSEG, the three main providers of power supplies for the experiments. The section is now fully immersed in the development of OPC Unified Architecture Servers for the LS2 upgrades. The section also collaborates with ATLAS on the development a generic OPC UA server development framework, QUASAR [2]. Working together with the Knowledge Transfer group, this is a fully open source project available on GitHub. The LHC Experiments adopted CANbus as the main fieldbus for controlling electronics and power supplies. The total number of nodes used by all experiments exceeds 10,000. The section provides CERN-wide support for CAN and handles the evaluation of new components and interfaces. DIP is the communication protocol agreed by the LHC Experiment Accelerator Data Exchange Working Group (LEADE) to exchange data across different domains at CERN. On this front, the section is responsible for the development of the middleware itself and the necessary infrastructure (e.g. redundant name severs, monitoring, etc.) to ensure 24/7 operation of the service. The section also contributes key components to the UNICOS project like the UNICOS Application Builder (UAB). UAB automatically generates UNICOS applications from specs; generating both the SCADA side software and also the PLC side code. This tool generates most applications provided by BE-ICS. The tool can also reverse engineer existing applications to capture end-user modifications to synchronize the project specs with the applications running in production sites. Another important CIC contribution to UNICOS is the interface between the commercial SCADA WinCC Open Architecture (OA) and the accelerator Common MiddleWare (CMW). Figure 3 shows the main graphical interface of MOON, a supervision tool to monitor the operational status of control system based on WinCC OA and the JCOP/UNICOS frameworks. The tool operates 24/7 and is daily used by the Industrial Controls Standby Service to monitor around 200 controls applications
4 Beams Department Newsletter Issue 16
comprising more than 400 PLCs, developed by BE-ICS and other partner groups in EN, EP, HSE and TE.
Figure 3, MOON’s main GUI showing the layout and stauts of the control system for the Warm Interlock Chain (WIC).
The CIC section has also a strong background in the development of web applications. Figure 4 summarises the status of the LHC Cryogenics. The web visualization receives data from a broadcasting mechanism internally developed in the section. Another web-based development is MARS, a new CIC deliverable that federates data from multiple sources like InforEAM, LanDB, ADAMS, IMPACT to assist on-call operators and experts by providing a complete, comprehensible view of relevant device information during interventions. The section also coordinates the asset maintenance activities for ICS by defining procedures and providing tools to ease these tasks in the group. CIC represents ICS at the BE Asset Management Forum and actively participates in the CERN Quality Assurance Committee.
Figure 4, Example of Web Dashboard summarising the status of the LHC Cryogenics.
Among the computing infrastructure (Confluence, VersionDog, Jenkins, etc.), we would like to highlight the ARES project. ARES is an automatic release service, which allows to make a release of a software package from SVN to the final publication on the web with a single mouse-click, thus simplifying drastically the life of developers. Finally, the CIC section is also an important contributor to data analytics in the group. The work carried out over the last few years has centered on the definition of algorithms for online and offline detection of anomalies in control systems, as well as in defining, together with SDS and IT, the cloud infrastructure necessary to carry out the analyses. CIC plays a crucial role in ICS as it provides the glue to link together the sub-components of complex and distributed control systems, and also common tools across the group, to support the homogenous development, stable operation and incident analysis of control systems. We certainly see a lot of potential synergies with other groups in the department and we hope to be able to contribute significantly to the successful exploitation of the accelerators and experiments.
Fernando Varela Rodriguez on behalf of the BE-ICS-CIC section
[1] The Joint COntrols Project [2] QUASAR
Controls Configuration Service – a challenge in usability The proximity of Geneva gives us a unique opportunity to visit its yearly motor show. We can try various models of cars and quickly get an impression of which suits us best. In some of the cars we feel comfortable and familiar from the very first moment. Sometimes the interior of some models makes us feel somewhat confused or leaves an impression of being difficult to use. This sensation of comfort and ease of use is a matter of ergonomics and usability, very relevant not only to cars but to equipment in everyday use. This sensation is especially important for
software products and graphical user interfaces. Generally speaking, the term usability expresses facility of use and ease of learning of a given man-made object, let it be a tool or a device. In a world of software engineering the term usability represents the degree to which a piece of software can be used by its end-users in a satisfactory, effective and efficient manner. Commonly we can simply say that a given user-interface is intuitive: it does not require intensive training, follows a natural workflow and is designed with its users in mind. The subject of usability is widely acknowledged in the software industry world and is formalised by dedicated ISO standards: - ISO/TR 16982:2002 Ergonomics of human-
system interaction - Usability methods supporting human-centred design
- ISO 9241-210:2010 Ergonomics of human-system interaction - Part 210: Human-centred design for interactive systems
Practically speaking, software applications, specifically graphical user interfaces (GUI), are by no means just mere tools facilitating our daily work. Their sole purpose is to establish an interface between human user and “machine”, specifically the internal implementation of the system. This point is especially important as one of the common failures of some GUIs is their inherent lack of abstraction between system internals, (e.g. a database structure) and its representation to the end-user. While occasionally such a case may be justified, in general as end-users, we don’t want to see the structures of tables, rows, columns nor any other implementation details. What we need and expect is that a software application and its GUIs capture real, practical use-cases and every-day workflows. After all the application is a tool which is expected to facilitate our work and should not generate unnecessary or artificial steps to accomplish common tasks. It is here that we can recognise the real challenge of usable and ergonomic applications - the attempt to capture users’ expectations, their real-life needs and facilitate their daily work. This is especially challenging in the case of engineering-oriented systems, for which the primary concerns are efficiency, robustness and minimalism while look-and-feel is a secondary need. It is precisely the challenge we face in the Controls Configuration Service (CCS). The CCS is undergoing a system-wide consolidation which started in mid-2014. Aside from the efforts to reduce the widely spread technical-debt, one of the main goals of the consolidation is a complete overhaul of all our graphical user interfaces - the
widely known “Data Browser” and APEX/ADF data edition tools. By analysing closer the needs and workflows of our users we identified several aspects of poor ergonomics and a need for essential usability improvements. Our system is currently represented as a set of separate applications, which fail to capture typical daily workflows, frequently leak internal details like database table structures, and have confusing controls and inadequate error messages. These are all just examples of areas which require renovation and advancements. In order to address these flaws and to improve the usability and ergonomics of our tools - the future CCS GUI - the Controls Configuration Data Editor (CCDE) will represent a single and user-oriented view of all the configuration data. The underlying system and GUI will capture the role of the user and act accordingly. One of the challenges of the CCS is its diversified and vast group of users and functions with a multitude of domains and system-specific extensions. Although such a situation brings a considerable level of complexity the benefits are clear and counter potential problems - by having a single and unified source of the configuration in the Controls system we are able to assure its consistency, correctness and remove unnecessary and potentially dangerous redundancies. Thanks to the unification the users of CCS can access and rely on the same configuration data despite their role: hardware installation experts, equipment experts, FESA developers or middleware specialists. Furthermore high-level components of the Controls system depend on the consistent and correct picture of the configuration, i.e.: InCA/LSA (settings management for LHC and injectors) or CALS (the CERN Accelerator Logging Service). As a practical example, today CALS users need to contact support in order to enable logging of new data. In the near future thanks to the new generation Logging Service (NXCALS) and our new approach to providing CCS GUIs - the CCDE will let you enable logging directly when browsing devices, properties and fields. The CCS will capture not only the definition of a device class and its properties but also let you easily turn on logging. It is a simple example of how usability and ergonomics of the system can be increased for the end-users and at the same time hide all the implementation details like integration between separate Controls sub-systems. A more advanced example is the configuration of Front-End Computers (FEC). Today, in order to prepare a FEC for operational use, several distinct actions are required: HW experts need to import or declare the FEC in CCS, then configure its crates and
6 Beams Department Newsletter Issue 16
modules. Low-level software experts may need to setup drivers for HW modules. Finally, equipment experts or FESA developers need to setup FEC start-up sequences in order to launch their FESA processes on the FEC. All of the above requires users to switch back-and-forth between different views, tabs and screens of the CCDB Hardware Editor, often not in a very intuitive manner. After closer analysis and discussions with some of our users for this scenario, we identified two distinct roles in the system: HW installation (physical configuration) and FEC startup configuration (logical configuration).
Fig. 1 Mock-up of a FEC Logical Configuration view in the upcoming CCDE.
The future CCDE will capture these two roles in the way the GUI is designed and works in the context of a currently selected FEC. Thanks to users feedback and their openness to share (often critical) opinions we now understand better how in practice our tools are used. Since hardware installation normally involves the setup of a crate (VME, KISS-2U-CRATE, etc.) and modules (e.g. a set of CTRVs), the ergonomics of the GUI will be improved by showing all the relevant information in a single view and in a logical order - thus limiting unnecessary context-switching and tedious moving between various tabs and panels (as is the case today). FEC runtime configuration is a different perspective of the configuration data and here, once more, the editor will capture a “role” in the system by focusing on DSC Programs, their definition and order of execution.
Fig. 2 Mockup of a FEC Physical Configuration view in the upcoming CCDE.
When addressing usability and user-experience, simple mock-ups are indispensable to get first-hand feedback. Just a few simple wire-frames can help to express the needs of the end-users and let application developers present their understanding. If you are one of our users feel free to visit our library of CCS mock-ups at: https://wikis.cern.ch/display/config/Mockups+library and share your feedback on how you would like to work with our applications. The points mentioned so far are just some examples of how usability and ergonomics of applications can be improved. When reflecting on this matter we can see that above all - the application should capture a natural workflow of its users and help them in their daily work. The challenge to provide usable and easy to use applications or tools is not only limited to a complex domain - in most cases the challenge itself is to better understand requirements and real-life scenarios in which our users are working. It is a failure of a software engineer when a tool or application does not fit its purpose but gets in the way. The specificity of the vast and complex domain of the CERN accelerators makes it difficult to guess and envision how all our users would like to work. Fortunately, software products are generally easier to change and improve than physical tools. It is hard to modify the interior of a car after it has been launched into production but an open-minded software engineer will listen and understand user’s needs. After all, the purpose of our tools is to help our users in their daily work, but only our users can help us to understand their real needs.
Pushing LEIR limits to new horizons The Low Energy Ion Ring (LEIR) is an ion accumulation ring which is at the heart of CERN’s heavy ion beam production. It was conceived to reach the luminosity requirements for lead-lead collisions in the LHC and, to this end, has been equipped with a multi-turn injection scheme and an electron cooler. The latter is required to reduce the phase space volume of the beam injected from Linac3 and the interplay of the complex injection scheme and electron cooling is the key ingredient to producing lead ion beams of high density. Further information about these concepts can be found in the BE newsletter issue 13. LEIR features two different modes of operation, the so-called EARLY and NOMINAL schemes. In the first, a low-intensity, single-bunch ion beam is produced, which serves either as a pilot bunch for the LHC or as the physics beam for experiments in the SPS North Area. During operation with these low-intensity beams, LEIR’s potential is not fully exploited and EARLY beams are rather straightforward to produce. For NOMINAL beams, however, things are more involved. In order to achieve high intensity in LEIR, seven consecutive injections from Linac3 are accumulated, with continuous electron cooling on the injection flat bottom. Just before the rise of the magnetic field, the radio-frequency (RF) voltage is slowly increased, a process referred to as iso-adiabatic RF capture, and two bunches are created. Once completed, the density of these bunches is significantly higher compared to the previously continuous beam and this has important implications for the operation of the machine as explained in the following paragraph. Subsequently, the lead ions are accelerated from the low-energy plateau at 4.2 MeV/n kinetic energy to 72 MeV/n at extraction, where they are sent off towards the PS. The whole process of beam production is shown in Fig. 1. Over the past years, the performance of LEIR has mainly been limited by beam loss occurring at the end of RF capture and during the first part of acceleration. The purple intensity curve in Fig. 1 shows a typical loss pattern measured in 2015, which reveals that more than one-third of all ions were lost before reaching the extraction flat top. In this state, the performance of LEIR was
Fig. 1 Example of a NOMINAL cycle in LEIR. The purple and blue lines correspond to the beam intensity measured in 2015 and 2016, respectively, and the black line shows the magnetic field. The different processes required for beam production are indicated by the colored regimes. insufficient for the future high-luminosity operation of the LHC after Long Shutdown 2 (LS2). Consequently, in the framework of the LHC Injectors Upgrade (LIU) project, additional manpower joined the LEIR team in October 2015 to increase the understanding of the accelerator’s limitations and to find a means to mitigate beam loss. After an intense study period, which continued throughout 2016, the interplay of two effects was pinned down as the explanation of the loss phenomenon. First, the density increase during the bunching process enlarges the repulsion of the equally charged ions inside the bunches and these so-called space charge forces modify the horizontal and vertical oscillation frequencies of the particles. Secondly, magnetic errors, which may arise from unavoidable alignment or manufacturing tolerances or from fringe fields of the main magnets of the accelerator lattice, excite resonances that can lead to the growth of the particles’ oscillation amplitudes and subsequently to beam loss. In LEIR, multiple resonances were observed to be excited and the space charge forces push the particles onto these resonances. One experimental hint of this phenomenon is the fact that the beam size increases drastically during the RF capture, which then results in beam loss once particles touch the vacuum chamber. Based on this understanding different measures to mitigate beam loss in LEIR were pursued. On the one hand, this concerned the optimization of the RF settings at capture. The use of a double harmonic RF system allowed to create longitudinally hollow bunches, with densities that are significantly reduced
8 Beams Department Newsletter Issue 16
compared to Gaussian or parabolic distributions. In order to visualize the longitudinal distribution, a tomographic algorithm can be applied to measured longitudinal profiles. The resultant tomogram of a hollow bunch is pictured in Fig. 2. Another key ingredient to achieving optimum performance is a well-controlled orbit correction. This may seem an obvious requirement, but becomes even more important in LEIR due to the extensive growth of the beam size during the capture process. Furthermore, the excited resonances were observed to be mainly of sextupolar order. Therefore, sextupole magnets, already installed in LEIR, were used to reduce the strengths of the resonances and, hence, reduce beam loss. In parallel, a similar effort to improve the machine performance has been going on at Linac3. Most of the work focused on an upgrade of the GTS-LHC ion source extraction region, where the primary heavy ion beams are produced. Extensive simulations of the beam extraction and transport in the low-energy part of the machine showed that strong beam divergence at the source output was causing significant collimation already onto the beam pipe at the end of the extraction chamber. To improve beam transmission in this region the beam pipe aperture was increased from 65 mm to 100 mm. This change, in combination with careful re-optimization and matching of the beam to the new transport conditions, has delivered an increase of Pb29+ production from the source of 25% and of the Linac3 208Pb54+ output current for LEIR of 40%.
Other directions have also been explored to further improve the Linac3 performance. Firstly, a new
bipolar einzel lens was installed inside the source extraction chamber in order to add more focusing and matching capability of the extracted beam. Initial results have not been conclusive and, therefore, more investigations are needed to assess the benefits of the new installation. Secondly, a measurement campaign was launched to study the effects of double frequency heating on the pulsed performance of the ion source, using a Travelling Wave Tube Amplifier (TWTA) with variable frequency as second microwave source. An effect was observed on high charge state ion currents; improvement on Pb29+ production was however more modest and studies should be continued to assess any possible future advantage for Linac3 operation. Lastly, a dedicated test stand was assembled to better characterize lead ion beam production and oven performance. A numerical thermal model was developed in parallel with ANSYS, and simulation results were successfully benchmarked against measurements of the temperature distribution inside the oven. The exercise yielded initial clues to possible causes of oven failure and blockage mechanisms sometimes observed in operation. Future studies on this will help to clarify the factors impacting source behavior and lead to improved beam stability conditions. With the remarkable performance of Linac3 and the implementation of the above mentioned mitigation measures in LEIR, it was possible to reduce beam loss in LEIR to about 10% and extract more than 8.5 x 1010 charges during the 2016 LHC p-Pb run (see blue curve in Fig. 1). In fact, the performance of LEIR reached in 2016 satisfies the LIU intensity goal of 8 x 1010 charges at extraction. Furthermore, also because of performance improvements in the PS and SPS, it has been possible to split each bunch out of LEIR into two in the PS while keeping the intensity per bunch at LHC injection the same as in 2015. Following a one-year break in 2017, when LEIR will provide xenon ions, we will continue to push the performance of lead ion beams in 2018, with the aim of getting the best out of LEIR after LS2.
Giulia Bellodi, BE-ABP-HSL, and Alexander Huschauer,
BE-ABP-HSI, on behalf of the LIU-Ions PS
Injectors team
Fig. 2 Reconstruction of longitudinal phase space at the end of RF capture. In order to reduce the peak bunch density, the inner lobes are significantly depleted. A projection of the image on the time axis would reveal an almost rectangular longitudinal profile, i.e. constant density along the bunch.
9 Beams Department Newsletter Issue 16
Colonne Sécurité
Sécurité des biens ? Sécurité des personnes !
Nous constatons de plus en plus souvent que des groupes/unités font installer des Système de contrôle d’accès SUSI (Surveillance Site) aux entrées de leurs bâtiments ou locaux.
Quel est le but recherché par l’installation d’un tel contrôle d’accès ? Le système de contrôle d’accès permet d’une part de restreindre le droit d’accès à une certaine catégorie de personnes, et il permet aussi de vérifier a posteriori, en cas de malveillance, qui est entré quand dans le bâtiment ou local.
Concernant le premier point, il s’agit de choisir judicieusement la permission associée à la zone à contrôler. La gestion de cette permission, permet de restreindre le droit d’accès aux personnes qui auront légitimement le besoin et le droit d’accéder au bâtiment/local concerné.
Concernant le second point, les portes associées à ces systèmes de contrôle d’accès ne permettent en général pas de garantir l’unicité de passage (1 badge – 1 personne), et leur temps d’ouverture n’est en général pas limité. Combien de portes ainsi équipées voyons-nous souvent bloquée par un petit caillou ou une poubelle ? Vous avez dit contrôle d’accès ?
Et la Sécurité des personnes dans tout cela ?
La question à se poser est : Les bâtiments ou locaux équipés d’un contrôle d’accès contiennent-ils des équipements présentant un danger pour les personnes non-spécialistes ? Les dangers principaux auxquels il faut penser sont l’électricité, les champs magnétiques, les ondes RF, mais aussi les radiations, les accès en hauteur et le bruit.
Bien sûr, la première règle face au danger, est de minimiser les risques au moyen de protections collectives. Les dangers doivent aussi être signalés. Et en dernier ressort, il faut former les personnes pour y faire face et pour pouvoir réagir en cas de risque avéré ou de dysfonctionnement.
Comment vous assurer que les personnes accédant à vos locaux ont reçu la formation minimum pour faire face aux dangers présents ? En imposant les formations de sécurité appropriées, et ce via le système de contrôle d’accès.
Notre recommandation est donc d’imposer les cours de sécurité nécessaire à la sécurité des personnes. A minima, nous souhaitons que le cours de base « La Sécurité au CERN » soit obligatoire pour accéder aux bâtiments à risques industriels, aux ateliers et aux labos. La sensibilisation aux risques électriques sera aussi souvent un plus.
Avant de faire installer un nouveau système de contrôle d’accès sur l’un de vos bâtiments ou locaux, nous vous prions de contacter l’équipe DSO pour en discuter les modalités. Merci de votre collaboration.
ASSOCIATES AND FELLOWS COMMITEE (AFC) 16th May 2017 Deadline for application – Fellows 28th February 2017 Deadline for application – Associates 9th March 2017
21st November 2017 Deadline for application – Fellows 4th September 2017 Deadline for application – Associates 16th September 2017 TECHNICAL STUDENTS COMMITTEE (TSC) 1st June 2017 Deadline for application 12th April 2017
5th December 2017 Deadline for application 16th October 2017 SUMMER STUDENTS
March 2017 Deadline for application 27th January 2017 TECHNICIAN TRAINING EXPERIENCE (TTE)
14th June 2017 Deadline for application 19th May 2017
6th December 2017 Deadline for application 31st October 2017 Please note deadlines in bold and Selection dates underlined.
MERIT Start of performance appraisal interviews: 1st December 2016
Deadline for completing the interviews: 30th March 2017
Deadline for signing the MERIT form: 14th April 2017
MERIT notification letters to Staff members: mid to 30th May 2017
11 Beams Department Newsletter Issue 16
RESPONSIBILITY CHANGES
End of appointment as ASR-AS Section Leader and DAO
on 31.10.2016 Resignation on 31.01.2017
Laurence Van Cauter-Tanner
New ASR-AS and ASR-RL Section Leader
as from 1.11.2016 Isabelle Laugier
New DAO
as from 1.11.2016 Jeanette Kotzian
End of appointment as OP Group Leader
on 31.12.2016 Mike Lamont
Will take up full time responsibilities as Deputy Department Head
New OP Group Leader as from 1.1.2017
Rende Steerenberg
New OP Deputy Group Leader
as from 1.1.2017 Jörg Wenninger
End of appointment as OP-PSB Section Leader
on 31.12.2016 Klaus Hanke
New OP-PSB Section Leader as from 1.1.2017 Bettina Mikulec
New OP-PS Section Leader as
from 1.1.2017 Klaus Hanke
End of appointment as ICS-SDS Section Leader
on 31.12.2016 Manuel Gonzalez Berges
New ICS-SDS Section Leader as from 1.1.2017 Peter Sollander
