THE LAYOUT SERVICE Eve FORTESCUEBECK on behalf of
THE LAYOUT SERVICE Eve FORTESCUE-BECK on behalf of the Layout Team 2 nd BE Asset Management Forum Meeting, 14 th May 2018 https: //indico. cern. ch/event/724603/
Outline • Purpose of the Layout Service • What are Functional Positions? • When to use Layout • Layout Service Consolidation • Layout Application: Main Functionalities • Data Responsibilities & Contact Information The Layout Service - E. Fortescue-Beck (BE-CO-DS) 2
Purpose of the Layout Service Initially developed in 2003, the Layout Database centralises the management of integrated, controlled Functional Positions (FP) and all associated layout data which potentially have an impact on accelerator operation, in any CERN beam line. In Layout, CERN infrastructures are documented by modelling topologies as layouts of related FPs. More details: https: //wikis. cern. ch/display/Layout The Layout Service - E. Fortescue-Beck (BE-CO-DS) 3
Purpose of the Layout Service Layout data is often fundamental for the operation of the accelerator complex. It is used by 100’s of people all over CERN and supports a diverse set of, sometimes mission critical, activities, such as: • Being the primary reference for the configuration of CERN Beam-line Layouts - maintained by EN-ACE-CL. • Feeding DMU (Digital Mock-Up) and Smar. Team - used by the Integration team to produce 3 D scenes of the machine and 2 D Engineering Drawings. • Providing automatic generation of MAD sequence files for Optic simulations - for BE-ABP. • Feeding the GIS (accelerator locations, racks, Rad. Mon, control and power boxes). • Managing Electronics Hierarchies (racks, crates, modules…) to serve for diagnostics and a basis for hardware configuration • Providing the main documentation of the EIS (Elements Importants de Sécurité). • Describing Powering circuits (sets of connections between power converters and magnets) in detail. • Describing Controls circuits (e. g. World. FIP, Pulse Repeaters, White Rabbit fieldbuses), up to the client • Configuration of the LHC Quench Protection Systems (Electronics + logical dependencies). • Providing the UNICOS specifications for the configuration of the LHC Cryogenic Controls System (~ 32 K instruments , electronics & cabling). The Layout Service - E. Fortescue-Beck (BE-CO-DS) 4
What is a Functional Position? Every component in the Layout database is defined as a Functional Position which specifies the size and the position of the space that the component occupies in the accelerator. Functional Positions have the following characteristics: • A Type Code: defined by the CERN naming conventions • A Location: Machine Half Cell, Period, Alcove, Building Number etc • A Position: within the location, or within the accelerator • Dimensions: can be very large (several meters) or very small (a few mm) • Unique Name(s) according to the QA plan of each machine + expert names The Layout Service - E. Fortescue-Beck (BE-CO-DS) 5
What is a Functional Position? In Layout, Functional Positions are defined as part of a hierarchy: Example: An instrument FP is defined as the child of a magnet FP. • The position of the instrument is defined as an offset with respect to the start of the magnet • The instrument inherits the location of the magnet • The exact position of the instrument in the accelerator is then calculated. • If the position of the magnet changes, the position of the instrument updates automatically The Layout Service - E. Fortescue-Beck (BE-CO-DS) 6
When to use Layout? In order to have complete and coherent descriptions of the machines: Functional Positions that are directly related to the accelerators must be declared in Layout The concept of an FP also exists in Infor EAM – this is a common point between these two distinct systems. • Work is ongoing between EN-ACE and BE-CO to clearly document the FP-related functionality of the two systems. • We have an agreement improve the integration between the two systems, concerning the exchange of FP-related data. The Layout Service - E. Fortescue-Beck (BE-CO-DS) 7
Layout Service Consolidation To cope with an ever-increasing demand on the service, the team is currently implementing: • A completely new Oracle Layout Database • A new web application to browse, visualise and edit layout data • The new application covers and extends the functionality of the current read-only website The first production version of the new application was deployed in September 2017 and provides core functionalities and some domain specifics. https: //layout. cern. ch Additional domains will be deployed according to the roadmap defined in Portfolio The Layout Service - E. Fortescue-Beck (BE-CO-DS) 8
Layout Application: Main Functionalities The Layout Service - E. Fortescue-Beck (BE-CO-DS) 9
Functional Positions Following Naming conventions Time-Oriented The Layout Service - E. Fortescue-Beck (BE-CO-DS) 10
Assembly Breakdown Structures Containers Content The Layout Service - E. Fortescue-Beck (BE-CO-DS) Validity period of the relationships 11
Electronics Assemblies Drag & Drop to move content The Layout Service - E. Fortescue-Beck (BE-CO-DS) 12
Circuits and Connections Interactive circuit network diagram Fieldbus tree navigator: World. FIP, Pulse repeater, White Rabbit circuits Upload & download csv file of the circuit The Layout Service - E. Fortescue-Beck (BE-CO-DS) 13
Links with other CERN systems Links towards MTF, EAM Light, Infor. EAM Embedded interactive GIS viewer centred on selected rack The Layout Service - E. Fortescue-Beck (BE-CO-DS) 14
Data Responsibilities & Contact Information Management of Beam-line components data remains the responsibility of EN-ACE. Equipment groups now have the possibility to manage domain-specific data, relationships and non-beamline components, for themselves. If you wish to start using the Layout Database, please contact: Layout. Service@cern. ch The team will: • Provide advice on how to define and structure Functional Positions in an integrated way • Discuss specific requirements (domain properties, views etc) • Provide training on how to use the available tools • Provide the necessary access rights Controls Hardware Data Management - E. Fortescue-Beck (BE-CO-DS) 15
- Slides: 15