Note: when finalised. this should all be documented in an EDMS document

All major items (e.g. modules, cold boxes, electronics, cables, etc.) shall be identified and labelled using the LHCb and CERN wide convention described in this document. These labels serve also as unambiguous identifiers of equipment which needs to be entered and removed from the point 8 underground area. If, unexpectedly, unlabelled 'minor equipment', like a cable tray, a fibre support plate etc. needs to be removed, it will receive a label in an ad-hoc way.

Rules for assignment of unique identifiers:

Information from Gloria C.:

You can find the rules for the assignment of unique identifiers for the general and the different assignments for each character in the following documents on EDMS:

In the same folder there are also notes for the calo and muon that have their one dedicated additional rules.

Once you settle on your rule we can consider implementing them in addition to the general one in our traceability system as we will need to register all the parts. We will need a general description of the type of equipment (dimensions, weight and material composition) and the location of the equipment for each as well as a budget code and a responsible of the equipment. Once the parts are registered in the LHCb traceability system they are then recognised by the RP TREC system when needed for transport or shipping, as we just recently connected to it.

Note that for cables we have a separate system and database that connects to the LHCb traceability once the cables are installed. For the cables you can look at the presentation at

and the web-based Cables Management System is available at

Registering Parts in the Database

Info from Matthias:

The registering of parts has to be done first in our LHCb database, which is not TREC!

Our interface has the possibility to do bulk operations, e.g. you search for the common first letters of all parts of a certain group, then checkmark the items you want to move on the list that appears as search results, and then move them all in one go, as long as they all go to the same location.

In addition, if during registration you attach some of the smaller parts (“child”) to another part that is holding together a larger assembly (“parent”), then only the parent parts have to be moved in order to change the location for the whole assembly, until they are detached again.

TREC is only going to be involved if one or more of these parts are transported outside of Point 8. In that case, the information that was registered in our LHCb database will be transferred automatically to TREC when you first ask for a transport request, so that you don’t have to register anything twice.

In any case, in response to your initial question: I think it is sufficient if you register those parts as being in the LHCb UX85B cavern from the start, as we only care about parts that actually have been exposed to radiation. However I would suggest waiting with the registration until we have updated our location tree in the traceability interface with location names that are hopefully more accurate and easy to identify.

Gloria: I would argue that the earlier you do it the better. At the latest when you install them but registering takes a little longer and I think you do not want to spend time on this at installation.

SciFi Part Traceability for the LHCb Database & TREC:

The convention integrates seamlessly with the existing labeling conventions used in LHCb and CERN wide. The identifiers shall have the form:

4-TS-XXX-YYY-12345 (The dashes are not part of the identifier) .

The different parts have the following meaning:

4 = fixed CERN-wide code for the LHCb experiment;

TS = fixed Tracker, SciFi [2];

XXX = fixed three characters defining the institute

Y-YY = SciFi specific three characters for the part ID, describing the nature of the item. The first letter is the work package. The second two are the sub-item. For example, the fibre module below would be F-SM.

12345 = variable five numbers, assigned by the institute.

Production Database

The link to the production database


The code names and bar codes are used in production as well as the LHCb database. Additional codes for sub-parts are likely used here, and have not followed the YYY scheme below, but will not be part of the LHCb database. Please follow the work-package convention for INSTALLED ASSEMBLIES ONLY where the first letter of the work-package is reserved. The last two letters are free.

Table of Part Identifiers

Parts/Assemblies that will require entry into the LHCb database should be entered into this table. (Things that could theoretically be exchanged, removed, or installed in the pit) Underlined codes are fixed and cannot be changed anymore.

Work Package (Y) Part Name Part Code (YY) dimensions(mm) weight (kg) material composition (most to least by weight)
Mechanics (M)
C-Frame FR
Fibre Modules ( F ) Full Size Module SM 4850 x 520 x 50 20 Aluminium, Polystyrene, Nomex, Araldite glue, Carbon Fibre Reinforced Polymer
F-Module with coldboxes AM
Cold-Boxes (B)
Top Cover with SiPMs TC
Shell Assembly SA
Electronics (E)
Front End Box FB
Master Board MB 115x256.20x20.2 516gr.
Light Injection System LIS LS
Versatile link dual transmitter TT 3.55gr
Versatile link transceiver TR 3,45gr.
FeastMP FM 4 gr.
Heatsink HS
Cluster Board CB 60*88*11 0.05 FR4
Pacific Board PB 60*65*1.6 0.0235 TU-862HF
Pacific ASIC PA
Cooling plate FBF x x Aluminium
Small cover FBS x x Aluminium
Large cover FBL x x Aluminium
Front End box FB x x Aluminium
Capacitor Board CA x x
Heating PCB HB
Cabling (C)
HV Cables HV
Optical Fibre OP
LV Long Cable LL
LV Short Cable LS
Dry Gas Flow Metre GF
Dry Gas (G)
Bellows BL
Exhaust Pipe EP
Flow Metre FM
Main Manifold MM
Square Manifold SM
-- BlakeLeverington - 2018-03-22
Edit | Attach | Watch | Print version | History: r12 < r11 < r10 < r9 < r8 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r12 - 2020-03-19 - BlakeLeverington
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LHCb All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback