1. 19-06-2006Peter Rosinsky, ALICE week, Bologna 1 PVSS/Fw OPC/DIM Network ALICE DCS Naming Conventions Peter Rosinsky & Peter Chochula, ACC team

2. 19-06-2006Peter Rosinsky, ALICE week, Bologna 2 General principles ALICE-wide DCS names standardization –Assure smooth dvelopment&operation –Avoid conflicts Required/recommended by PVSS –DP names, system names in distrib. system, … JCOP framework –Access control, DP, FSM, … Other SW Good practices –Meaning of privileges, user groups, … –Avoid exceptions

3. 19-06-2006Peter Rosinsky, ALICE week, Bologna 3 Applicability Mandatory –system names –project names –OPC server names –DIM server names –DIM services –datapoint names and type names –network attached devices Strongly recommended –panel names –detector-specific script names

4. 19-06-2006Peter Rosinsky, ALICE week, Bologna 4 Composition of names Basic rule: prefix_objName –prefix: unique code for subdetector or subsystem small letters, treated as a single word –objName: standard interCap notation – first letter always small should be meaningful (functionality, location) –objName: exceptions datapoint types: begin with capital letter (JCOP convention) FSM (objects, commands, states): all capital letters, underscore-separated FED DIM services and commands: all capital letters DIM commands: prefix omitted (DNS per subdetector)

5. 19-06-2006Peter Rosinsky, ALICE week, Bologna 5 Prefixes CodeSub-detector or system CodeSub-detector or system spdITS SPDmtrMuon trigger sddITS SDDzdcZDC ssdITS SSDEmcEMCAL tpcTPCTriTrigger trdTRDhltHLT tofTOFdaqCentral DAQ phsPHOSdcsDCS cpvCPVfraFront absorber hmpHMPIDsaaSmall angle abs. fmdFMDsfrSpace frame pmdPMDl3mL3 magnet v00V0dimDipole magnet t00T0bmpBeam pipe mchMuon trackerexhExperimental hall intIntegrationotrOther(not classif.)

6. 19-06-2006Peter Rosinsky, ALICE week, Bologna 6 Subsystems Sub-System nameAbbreviation Low Voltagelv High Voltagehv Very High Voltagevhv Crate Controlcra Environmentenv Coolingcoo Gasgas Front-end and ReadOut Electronicsfero Calibrationcal Laserlas Rackrck Alignmentaln

7. 19-06-2006Peter Rosinsky, ALICE week, Bologna 7 Controlled/monitored quantities Physical quantityAbbreviation Voltagev Currenti Temperaturet Pressurep Flowf Humidityrh

8. 19-06-2006Peter Rosinsky, ALICE week, Bologna 8 Parameters Parameter typeAbbreviation Monitored valuemon Setpoint valueset Trip valuetrip Error limit (high limit, low limit, boolean)errHi, errLo, err

9. 19-06-2006Peter Rosinsky, ALICE week, Bologna 9 FSM SMI++ compatiblity  UPPERCASE –interCap notation can’t be used  underscore as a separator FSM naming rule: DET_OBJECT_NAME –DET: three letter detector/subsystem code –OBJECT_NAME: meaningful description following the detector conventions

10. 19-06-2006Peter Rosinsky, ALICE week, Bologna 10 DIM FED DIM server –one DIM DNS server per detector (on Operator Node) – to be compatible with FED API (common commands) –any external client should use this detector-specific DNS FSM DIM –one central DIM DNS server for all (FSM tree) DIM services –Follow the rules for DPs (prefix_objName) DIM commands –can skip the prefix part

11. 19-06-2006Peter Rosinsky, ALICE week, Bologna 11 Examples DP type and Datapoint name  Agd_seuRegisterSettings (DPT)  agd_seuRegisterSettings (DP)  AGD_seuRegisterSettings (DPT)  agd_SeuRegisterSettings (DP) OPC server: agd_opcWiener1 FSM: AGD_SIDEA_SECTOR3_MODULE1_LV

12. 19-06-2006Peter Rosinsky, ALICE week, Bologna 12 Other elements System names, projects, panels, scripts, … follow the rule: prefix_objName –defined prefix, meaningful names PVSS Projects –use the same name as systems –note: system number is assigned by ACC (use web form) DCS numbering convention –fully compatible with ALICE rules –as stated in “Guidelines”

13. 19-06-2006Peter Rosinsky, ALICE week, Bologna 13 Networked devices Must be unique across CERN! –alidcs prefix “reserved” for P2 production installation  do NOT register name beginning with this for the labs! –convention only, no automatic restrictions by NETOPS –regular checks foreseen Basic rule: alidcsXXXNNN –XXX: three-letter device type code current list on the next slide –NNN: sequential number Examples alidcscom123, alidcscae013, alidcsdig002

14. 19-06-2006Peter Rosinsky, ALICE week, Bologna 14 Device codes devicecode computercom CAENcae Wienerwie PLCplc DIGI boxesdig BCAMbca Switchswi other (auxilliary) deviceaux

15. 19-06-2006Peter Rosinsky, ALICE week, Bologna 15 Production computers Names: alidcscom001-999 –not descriptive, but rather “inventory” name Computer aliases (also unique across CERN!) –encode detector and role Basic rule: aliDETXXNNN –DET: three-letter detector code –XX: WN (worker node) or ON (operator node) –NNN: sequential number Verbose description –use the LANDB description field for more (short & meaningful) –will be printed as a label and placed near your computer

16. 19-06-2006Peter Rosinsky, ALICE week, Bologna 16 Title Text –text Text –text