ESS Naming Conven.on. Karin Rathsman

Transcription

1 ESS Naming Conven.on Karin Rathsman

2 Introduction

3 ESS Naming Convention The ESS Naming Conven<on apply to all devices and signals in technical systems and conven<onal facili<es. operator screens inventory system drawings design schema<cs computer sofware project databases equipment name tags test procedures other sources of technical informa<on at ESS.

4 Guidelines Names shall be short, yet meaningful and organized consistently. Primary scope is for opera<ons. Names are not necessarily structured according to WBS or PBS. - - These are mainly for op<mizing design and construc<on. Device names should however be used to name equipment in these structures. Database integra<on is vital.

5 From the ICS point of view, all equipment is modeled as devices Devices

6 Definition Device is the basic unit of granularity of the ICS the smallest that can s<ll be standalone and loosely coupled to other components. Device is an abstrac<on that can represent either single pieces of equipment (low level code for interfacing with the hardware)......or higher- level en<<es of the ICS ( e.g., device models, subsystems, instruments...)

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

8 Having parallel conven<ons for mnemonic names will inevitably cause confusion. Concurrent Conventions

9 Identification codes Devices at ESS will be assigned several iden<fica<on codes in for example Work break down structure (WBS), Project break down structure (PBS) Inventory BSAB 96 codes (conven<onal facili<es).

10 Restrictions! To avoid confusion equipment iden<fica<on codes other than device and signal names must not be mnemonic, i.e. it shall not contain abbrevia<ons or acronyms. simulate the naming conven<on syntax. Device names shall be used in other systems as azributes.

11 Expect thousands different kind of devices. Devices are categorised on three levels in the naming conven<on. Device Category Structure

12 Level 1 Discipline Branch of knowledge that indicates the context in which a device is used, Example: Vacuum (Vac) Water Cooling (WtrC) Cryogenics (Cryo) Proton Beam Instrumenta<on (PBI) Proton Beam Op<cs (PBO) Controls (Ctrl)

13 Level 3 Generic Device Type Two devices of the same generic type provide the same func<on Example: Pump (Pmp) Controlled Valve (CV) Temperature Sensor (TSn) These are interdisciplinary devices of e.g. Vacuum, Cryogenics as well as Water Cooling.

14 Level 4 Specific Device Type Two devices of the same specific type are iden<cal from a controls perspec<ve and among others have the same set of control signals. Configura<on of a device in the top- down approach is ini<ated by selec<ng the specific device type.

15 Device Identifiers Naming conven<on users prefer to use generic device type (level 3) as device iden<fier DDDD in the names. Therefore: Device names will be constructed using the generic device iden<fier (Level 3). Naming Conven<on users are s<ll responsible for selec<ng the correct specific device type (Level 4).

16 Device Type Reference List 9/25/2013 Karin Rathsman ID Device Type Name Comment Date Beam Magnets and Deflectors (BMD) Choppers 16 Chopper Chop Dipoles 31 Horizontal Dipole DH Misc 30 Vertical Dipole DV 34 Proton Beam Window PBW As indicator... 5/31/2013 Octupoles 43 Octupole, folding in horizontal plane OctH 32 Octupole, folding in vertical plane OctV Quadrupoles 18 Chopper quadrupole QChp 13 Horizontal Focusing Quadrupole QH 14 Vertical Focusing Quadrupole QV 53 Horizontal Permanent Magnet Quadrupole PMQH As indicator 5/31/ Vertical Permanent Magnet Quadrupole PMQV As indicator... 5/31/2013 Solenoids 2 Solenoid Sol Steerers 50 Steerer Str Cryogenics (Cryo) Indicators 94 Flow Indicator FIn follow up? 3/14/ Level Indicator LIn follow up 3/14/ Pressure Indicator PIn follow up 3/14/2013 Misc 80 Temperature Indicator TIn follow up? 3/14/2013

17 Zones, buildings and sec<ons shall be named and labelled afer the technical systems so that device and signal names can be linked to physical loca<on. Logical Area Structure

18 Level 1 Super Section High level zones and buildings such as Accelerator Target Sta<on Neutron Science Central Services

19 Level 2 Section 13 Accelerator Sec<ons: Ion Source (ISrc) Low Energy Beam Transport (LEBT). Dump Line (DmpL) 16 Target Systems: Monolith (Mnlt) Ac<ve Handling (ActH) Neutron Science Instruments Central Services. Water Cooling Plant (WCP) Cryo Plant (CP)

20 Level 3 Subsection Accelerator has numbered subsec<ons e.g., First HBL subsec<on (HBL-01) Thir<es HBL subsec<on (HBL-30) Target Sta<on has 80 subsec<ons in total, for example Water purifica<on system (ActF-WtrP) Ac<ve gas storage (ActF-Gsg) Central Services High Beta Water Substa<on (WCP-HBWS) is a subsec<on under the Water Cooling Plant.

21 Labeling Conven<onal facili<es have agreed to label the structures according to the sec<on- subsec<ons. The numbering system used by CF as iden<fica<ons for buildings, rooms and sec<ons, is independent on the ESS Naming Conven<on.

22 Section Reference List Karin Rathsman 6/14/2013 Accelerator ID Section Name Comment Date 1 Ion Source ISrc Low energy beam transport included 6/4/ Low Energy Beam Transport LEBT Not in use (part of ISrc.) 6/4/ Radio Frequency Quadrupole RFQ 4 Medium Energy Beam Transport MEBT 5 Drift Tube Linac DTL 7 Spoke Linac Spk 8 Medium Beta Linac MBL Changed from MB to MBL 6/4/ High Beta HBL Changed from HB to HBL 6/4/ Upper High Beta UHB 23 Dogleg DgLg HEBT split into DgLg and A2T 5/15/ Accelerator to Target A2T HEBT split up into DgLg and A2T 5/15/ Monolith beam Line MnBL Belongs to target? 2/22/ DumpLine DmpL Added 5/15/ Bent Dump Line HEBD Not in use (to be deleted) 5/15/2013 Target Station Active Cells ActC Active Fluids ActF Active Handling ActH Active Workshops ActWS Handling mock-up HMU Intermediate cooling Systems Inm Mobile Active Vacuum ActVM Moderator-Reflector MR Monolith Mnlt Proton Beam Window PBW 33 Radioactive Gaseous Effluent Confinement RGEC Section? Accelerator Subsection Reference List Karin Rathsman 6/14/2013 ID Subsection Name Composed Name Ion Source (ISrc) ISrc ISrc ISrc-03 Radio Frequency Quadrupole (RFQ) RFQ-01 Medium Energy Beam Transport (MEBT) MEBT MEBT MEBT MEBT-04 Drift Tube Linac (DTL) DTL DTL DTL DTL-04 Spoke Linac (Spk) Level 1 Super Level 2 Section Level 3 Subsection Spk Spk Spk Spk Shielding TSh Section? 37 Target Tgt The actual target (the wheel) 38 Target Safety System TSS Section? Utilities TS Storage TSg Tune-up dump TDmp 30 Water cooling plant WCP Added 4/4/ Cryo Plant CP Maybe CrP 2/15/ Spk Spk Spk Spk Spk Spk Spk Spk Spk

23 All informa<on needed to construct device names (except for the quan<fier III)is contained in the device category and area breakdown structures. Name Construction

24 Naming Process Logical Area Structure Level 1 Level 2 Level 3 Device Category Level 1 Level 3 Level 4 Tools Rules SSSS-BBBB:DDDD-III

25 Name Components System SSSS Sec<on conven<on name Subsystem BBBB T- type: Subsec<on conven<on name A- type: Discipline conven<on Name Device Iden<fier DDDD Generic device iden<fier Device Quan<fier III T- type: Instance number and/or Alphanumeric qualifier A- type: Subsec<on number immediately followed by alphabe<c numbering (a, b, c or d etc.)

26 Alice is an engineer who, for whatever reason, would like to connect a espresso machine to the control system. In this context Alice is our device editor. Workflow

27 Workflow 1.Browse the device category list generic device type: 1.Alice browses the device category structure to search for a generic device type she can add her espresso machine under. She looks under the discipline controls (Ctrl), but cannot find an generic device type for the espresso machine. 2.Search for a name component 1.Maybe the espresso machine is categorized under a different discipline? Alice enters «espresso» into the search field, but she can s<ll not find the generic device type. She decides to add an espresso machine to the list of generic device types.

28 Workflow 1.Add a new generic device type: 1.Alice selects Controls (Ctrl) => Miscellaneous (Misc) from the menu list of device categories. 2.Alice clicks the the + buzon to add a generic device type under the category Miscellaneous (Misc). 3.In the field labeled Full Name she enters «Espresso Machine». 4.She enters «EspMch» in the mnemonic name field. Alice receives a warning since the mnemonic name is longer than the recommended 2-4 character length. Alice ignores the warning. She knows that six characters is allowed. 5.Alice adds a comment «Device to prepare espresso.» in the comment field. 6.Alice clicks the submit buzon. As a device editor Alice can only add new generic device types as draf. To make the generic device type ac<ve it has to be approved by a super user. A no<fica<on is sent to Bob, the super user specialized on controls, about the request for a new generic device type.

29 Workflow 1.Add a signal name 1.Alice selects the specific device type «Alices» from the device category menu list. 2.Alice clicks the + buzon to add a signal name. 3.Alice enters the full name «Pressure in bar» in the field labeled full name. 4.Alice enters the «Pres» in the mnemonic name field. 5.Alice enters a comment «Nominal» 6.Alice presses the submit buzon.

30 Workflow 1.Add an instance of device to the naming database 1.Alice selects her specific device type from the device category list Discipline=>Category=>Generic Device Type=>Specific Device Type, guided by the ques<on «What kind of device is it?». Alice selects Controls (Ctrl) => Miscellaneous (Misc) => Espresso Machine (EspMch) => Espresso Machine Special (Alice). 2.AFer having read the leading ques<on «Which part of the facility does the device provide service to?» Alice selects Head Quarter (HQ)=>Integrated Control Center (ICC)=> Main Control Room (MCR) from the Area breakdown menu list. 3.Alice presses the Add buzon (or delete buzon or edit). A draf naming conven<on name is generated, with correct quan<fier and everything. It will be ac<ve only afer Bob has approved the generic device qualifier.

31 Workflow 1.Approve or reject a requested device name 1.Bob receives an that a new generic device name has been added. 2.Bob clicks the link in the which directs him to the review page for the generic device type Espresso Machine (EspMch) 3.Bob selects the reject radio buzon. 4.Into the message field, which is mandatory if device type is rejected, Bob enters «Use the generic device type Coffee Machine (CoMa) under the Office (Offs) => Miscellaneous (Misc) instead.»

32 Web- based tools are under development to support the process of naming devices. Use- cases are being studied to collect requirements, e.g., filtering and sor<ng capabili<es, as well as automated name genera<on. Tools

33 Proteus (Discs Collaboration) Figure 2 Naming System Home Page

34

35 Naming Part Descrip<on Requirements Assigned by Dis Discipline Naming CommiZee Cat Category Naming CommiZee gdev Generic Device Type Naming CommiZee sdev Specific Device type Device Editor Sup Super Sec<on Naming CommiZee Sec Sec<on Naming CommiZee Sub Subsec<on Naming CommiZee TTT Type Device Editor III Instance Device Editor XXX Suffix Device Editor

36 Selection tool Users should not have to be informed in detail on defini<ons of sec<on, subsec<on, discipline or the dis<nc<on between generic and specific device types. Ask explicitly: - - What kind of device is it? Which part of the facility does the device provide services to?(do NOT ask: Where is the device located? ) The answer shall be selected from a menu type list.

37 Name Integrity 1.To assure integrity of names the naming conven<on users will be asked to select 1.device type from the device category structure 2.subsec<on from the three level logical area structure 2.Device names are generated automa<cally.

38 Those are my principles. If you don t like them I have others. Groucho Marx The End