ESS Naming Convention

Transcription

1 ESS Naming Convention Karin Rathsman

2 Introduction

3 ESS Naming Convention The ESS Naming Convention apply to all devices and signals in technical systems and conventional facilities. operator screens inventory system drawings design schematics computer software project databases equipment name tags test procedures other sources of technical information at ESS. ESS Naming Convention Naming Convention Revision: 1.2 Status: Accepted Project: ESS Naming Convention Document ID: ESS/AD/0005 File: ESS Naming Convention.doc Owner: Garry Trahern Last modification: Maay 17, 2011 Created: October 26, 2010

4 History ESS Naming Convention is based on a standard developed for the Super Superconducting Collider (SSC) and later adopted to other large research facilities: Spallation Neutron Source (SNS) Facility for Rare Isotope Beams (FRIB) International Thermonuclear Experimental Reactor (ITER) Continuous Electron Beam Accelerator Facility (CEBAF)

5 System and subsystem name Signal type, instance and suffix SSSS-BBBB:DDDD-III:TTTIIIXXX Device identifier and quantifier System name: SSSS Subsystem name: BBBB Device identifier: DDDD Quantifier: III Device name: SSSS-BBBB:DDDD-III Signal name: SSSS-BBBB:DDDD-III:TTTIIIXXX

6 Motivation Millions of signals to control and thousands of devices to operate: Short, meaningful and structured names needed for communication and configuration. Can t rely on high level industrial HMI (barcodes, touch screens, etc.) to operate the facility. Industry standards for naming not applicable - Not human readable. - One of the kind facility. A uniform naming convention for ESS will help enforce system integration activities across all divisions.

7 Act Proactively Establish a naming convention at an early stage of the project. Assign a Naming Czar - Assure consistency - Coordinate Communicate, communicate and communicate! - Accelerator, Target, - Neutron instruments, - Conventional Facilities, - Update the naming convention document on implementation details. - etc. Develop a naming tool - Name support - Enforce syntax - Assure unique names

8 Guidelines Names shall be short, yet meaningful and organized consistently. Name structure does not need follow WBS or other project management structures. - These are for optimizing design and construction. - Device names can however be used to name equipment in these structures. Databases integration is vital.

9 Devices

10 Definition From the ICS point of view, all equipment is modeled as devices. Device is an abstraction that can represent either single pieces of equipment (low level code for interfacing with the hardware)......or higher-level entities of the ICS ( e.g., device models, subsystems, instruments...) Device is the basic unit of granularity of the ICS the smallest that can still be standalone and loosely coupled to other components.

11 This is a device... and this is also a device

12 Devices Inside Devices CMD HB#RF:Cmd#1+ HB#RF:Cav#1a+ HB#RF:Cav#1b+ HB#RF:Cav#1c+ HB#RF:Cav#1d+ Devices are not organized hierarchically through the naming convention. Example: There are four cavities inside a cryomodule. Both cryomodule and cavities are devices. CMD The hierarchical structure are found in other systems where the names are used. QH

13 Parent/Child Structure HB#1# HB%RF:Cmd%1# HB%RF:Cav%1a# HB%RF:Cav%1b# HB%RF:Cav%1c# HB%RF:Cav%1d#

14 Analysis of SNS Signal List

15 SNS Signal List NS_Signallist.xlsx with signals names (SSSS_BBBB:DDDDIII:TTTIIIXXX) 120 System names (SSSS) 97 Subsystem names (BBBB) Device identifiers & qualifiers (DDDDIII) SNS Checklist.pdf 40 System names 135 Subsystem names 634 Device identifiers

16 Analysis of SNS Signal List System (SSSS) approximately shows the part of the facility that the device provide services to. HEBT (High Energy Beam Transport) SCL (Super Conducting Linac) Tgt (Target) SubSystem (BBBB) approximately shows in what context (or discipline) the device is used Diag (Beam Diagnostics) Vac (Vaccum) LLRF (Low Level RF)

17 How to organize devices?

18 Generic and specific device types Generic Device type: Two devices of the same generic type provide the same function Example: RF cavities accelerates the beam Specific Device type: Two devices of the same specific type have the same set of control signals. Example: Elliptical cavity.

19 Device Identifier DDDD Both accelerator and target groups prefer to use generic device identifier DDDD in the names. Until decided it will be allowed to use the the same device identifier for generic and specific device types.

20 Grouping Expect thousand(s) different device types. Devices type and identifier shall be listed and sorted under Discipline - RF - Vacuum - Water cooling Generic Device Type - RF cavities - High power amplifiers - Valves

21 In Device Naming Tool <Select> Controls Ctrl Conventional Facilities CF Select or type DDDD Device Identifier Cryogenics Cryo Proton Beam Instrumentation PBI Proton Beam Optics PBO Radio Frequency RF Cavity Cav Vacuum Vac Buncher Cavity Cav Water Cooling WtrC DTL tank 1 Cav Discipline Device Type Generic Device Type DTL tank 2 DTL tank 3 DTL tank 4 Elliptical Cavity Radio Frequency Quadrupole Spoke Resonator Cryomodule Elliptical Cryomodule Spokes Cryomodule Cav Cav Cav Cav Cav Cav CMd CMd CMd

22 Systems System (SSSS) in the ESS naming convention indicates which part of the facility that the device provide services to. Name and label ESS zones/sections after the systems: - High Beta (HB) sections in both tunnel and gallery Avoid using the term System in the naming tool. Ask explicitly: Which part of the facility does the device provide services to? The answer shall be selected from a list.

23 Target

24 Target Target has few devices compared to accelerator, however many things are unique. Target already has a PBS organized in two levels. - Referred to as System-Subsystem by the target group. Devices like pumps, valves etc., appear in many subsystems. There is no desire to use discipline in the name.

25 In the Device Naming Tool Which part of the facility does the device provide service to? <Select> Select or type convention name Gallery Accelerator Target Station Active cells ActC Instruments Active fluids ActF Utilities Active handling ActH Instruments Active workshops ActWS Convention name Super System Handling mock-up HMU Intermediate cooling systems Inm Mobile active vacuum ActVM Moderators-Reflector MR Subsystem Monolith Mnlt Shielding cooling system ShCol Proton beam window PBW Monolith atmosphere system Atm RGEC RGEC Bulk shielding BlkSh Shielding TSh Irradiation plugs IrPlg Target Tgt Liner Lin Target safety system TSS Removable shielding RvSh TS storage TSg Shutter systems Shut Tune-up dump TDmp Neutron beam ports (NBP) NBP Proton beam diagnostics plug PBDPlg System Convention name Proton beam diagnostics skeleton PBDS Internal supporting structure SpStr Target diagnostics plug TDPlg Target diagnostics skeleton TDS

26 Accelerator

27 Accelerator There are many devices of the same kind in the accelerator in a repetitive pattern. The accelerator is divided into sections - Example High beta (HB) Sections are in turn is divided into numbered subsections (referred to as cells) - Example HB 1, HB 2, HB 32. Each subsection contains many devices of different disciplines. - RF, vacuum, Beam optics, etc..

28 FDSL_2012_New ESS Accelerator Sections ID Name SSSS 1 Ion Source ISrc 2 Low Energy Beam Transport LEBT 3 Radio Frequency Quadrupole RFQ 4 Medium Energy Beam Transport MEBT 5 Drift Tube Linac DTL 6 First Beam Extraction FBX 7 Spoke Linac SPK 8 Medium Beta MB 9 Second Beam Extraction SBX 10 High Beta HB 11 Upgrade (or Upper) High Beta UHB 12 High Energy Beam to Target HEBT 13 High Energy Beam to Dump HEBD 2.4 m 4.0 m 3.6 m 32.4 m? m 58.5 m m? m m? m m ISRC LEBT RFQ MEBT DTL FBX SPK MB SBX HB UHB HEBT 75 kev 3 MeV 78 MeV 200 MeV 628 MeV 2500 MeV HEBD

29 High Beta Subsections BBX CMD HB 1! CMD HB 2! BBX CMD HB 3! CMD HB 4! QV BPM BCMHalo BPM QH BBX QV CMD HB 5! CMD HB 6! BPMHalo WS NPM BPM BBX QH CMD HB 7! CMD HB 8! QV BPMHalo WS NPM BPM BBX QH CMD HB 9! CMD HB 10! QV BPM WS NPM BPM BBX QH CMD HB 11! CMDHB 12! QV BPM WS NPM BPM BBX QH CMD HB 13! CMD HB 14! QV BPM BSM BBX BPM QH CMD HB 15! CMDHB 16! QV BPM BSM BBX BPM QH CMD HB 17! CMD HB 18! QV BPM BSM BBX BPM QH CMD HB 19! CMDHB 20! QV BPM Halo BBX BPM QH CMD HB 21! CMD HB 22! QV BPM BBX BPM QH CMD HB 23! CMDHB 24! QV BPM BBX BPM QH CMD HB 25! CMD HB 26! QV BPM BBX BPM QH CMD HB 27! CMDHB 28! QV BPM BBX BPM QH CMD HB 29! CMD HB 30! QV BPM BPM QH QV BPM BPM QH

30 In the Device Naming Tool Which part of the facility does the device provide service to? <Select> Gallery Select or enter convention name Accelerator Ion Source ISrc Target Station Low Energy Beam Transport LEBT Instruments Radio Frequency Quadrupole RFQ Utilities Medium Energy Beam Transport MEBT Subsection Drift Tube Linac DTL First Beam Extraction FBX Spokes Section SPK Section Medium Beta Elliptical Cavities MB High Beta Elliptical Cavities HB 1 Upgrade (or Upper) High Beta UHB 2 High Energy Beam transport to Target HEBT 3 High Energy Beam transport to Dump HEBD 4 5 Convention name 6

31 How to Construct Names?

32 Structure Use the same tool and structure for target and accelerator: Discipline - Generic device type - Specific device System - Subsystem - I.e, the accelerator section is referred to as system and accelerator subsection as subsystem Question: How to construct the names using the Device Name Syntax: SSSS-BBBB:DDDD-III - Where SSSS and BBBB are not necessarily the system and subsystem convention names

33 First Rejected Proposals SSSS is the system convention name BBBB is the subsection convention name. Ok for target Accelerator device names like HB-3:Cav-2 not accepted. - Shall be HB-RF:Cav-3b.

34 Second Rejected Proposals SSSS is the subsection convention name. BBBB is the discipline convention name. Not accepted by target. Accelerator device names like HB3-RF:Cav-2 not accepted. - Shall be HB-RF:Cav-3b.

35 Third Rejected Proposals SSSS is the system convention name. BBBB is the discipline convention name. Not accepted by target Accelerator device names like HB-RF:Cav-3b accepted.

36 Forth Rejected Proposals SSSS is the system convention name. BBBB is the subsystem convention name, however the accelerator subsystems are given by the discipline rather than subsection numbers Accepted by target Accepted by accelerator Not accepted by naming czar because the structure is wrong: - Disciplines applies to all the accelerator sections and subsections and shall not be sorted under these. - Categorization of devices is needed.

37 Present Proposal Construct accelerator and target names differently. Target - SSSS = System - BBBB = Subsystem - III = Whatever... Accelerator - SSSS = System - BBBB = Discipline - First part of qualifier III = Subsystem ( a number) - Second part of qualifier III = a, b, c, d or whatever starts with an alphabetic character.

38 Conclusion The System-Subsystem and Discipline- Device type tables contain sufficient information for naming accelerator and target devices, however the requirement on how to construct the names are different. Not a surprise since accelerator and target are very different. If we manage to consistently name devices for both target and accelerator it should be straightforward to name other devices at ESS.

39 Terminology To avoid confusion, do not display the following terms in the Device Naming Tool Discipline System Subsystem Instead: Instruct or ask: Select Device Type Which part of the facility does the device provide service to?

40 Tools

41 Device Menu Tool User: Naming Czar Shall be possible to add/delete/edit - Discipline (full name and convention name) - Generic device type (full name and identifier) - Specific device identifier (full name and identifier) Version control Name check

42 System Menu Tool User: naming Czar Shall be possible to add/delete/edit: - Super system names ( full name) - System names (full name and convention name) - Subsystem names (full name and convention name) Version control Name check Shall be possible to customize order of names in menus.

43 Signal Tool (Can wait...) User: Configurator. Access: read access to all Disciplines and write access to a limited numbers of Disciplines. Shall be possible to select a generic device type from the Device menu For a selected generic device type it shall be possible to add/remove/edit - specific device types (full name and identifier) For a given specific device identifier it shall be possible to add/remove/edit - Signal (T.B.D) Version control Name check

44 Device Naming Tool User: TBD Access: TBD Shall be possible to select subsystem from the system menu. - The terms Super System, Section and Subsection shall not be displayed in the tool. - If the selected subsystem is a number or blank the name shall be constructed as accelerator device are? Shall be possible to select discipline and device identifier - The terms Discipline, specific, generic shall not be displayed in the tool. Shall be possible to add/edit/remove quantifier. Check quantifier - First character shall be alphabetic for accelerator devices Check that names are unique Shall be possible to customize order of devices (alphanumerical as default)

45 Other Tools Viewer: - Given any name SSSS-BBBB: DDDD-III it shall be possible to find all relevant information about this device.

46 Check convention names When checking the convention names use the following rules. 1. Convention names and device identifiers shall be alphanumerical. 2. First character of convention names and device identifiers shall be alphabetic 3. Convention names and generic device identifiers shall be unique. 4. Identifiers of special device types shall be unique or given by the generic device type. 5. Convention names and device identifiers shall be unique irrespective of letter case 6. Convention names and device identifiers shall be unique irrespective of letters I, l and number 1 7. Convention names and device identifiers shall be unique irrespective of letter O and number 0 8. Convention names and device identifiers shall be unique irrespective of letters V and W 9. Convention names and device identifiers shall be unique irrespective of number 0 immediately following a non-numerical character

47 Remark The required tools do not necessary have to be standalone, what matters is the functionality.

48 Finally Those are my principle. If you don t like them I have others. Groucho Marx