Report on database work for INB in ALICE Latchezar Betev (ALICE) Information Session INB – June 8, 2006

Information session on INB database activities in LHC experiments 2 Aim Presented is the ALICE Detector Construction Database (DCDB) in view of what (we believe) is related to the INB Presented is the ALICE Detector Construction Database (DCDB) in view of what (we believe) is related to the INBDCDB

Information session on INB database activities in LHC experiments 3 Detector Construction DB in ALICE Developed and operated since 2002 Developed and operated since 2002 Main developer – Warsaw University of Technology Main developer – Warsaw University of Technology Repository for detector components and component parameters Repository for detector components and component parameters Distributed database Distributed database 15 instances at the universities and institutes building the ALICE sub-detectors 15 instances at the universities and institutes building the ALICE sub-detectors One central repository at CERN (Oracle) serving as a backup and hosting the information relevant to the sub-detectors installation activities One central repository at CERN (Oracle) serving as a backup and hosting the information relevant to the sub-detectors installation activities

Information session on INB database activities in LHC experiments 4 Detector Construction DB in ALICE (2) Content of the database Content of the database Sub-detector components (readout cards, modules) Sub-detector components (readout cards, modules) Components test results – interfaced to VME, LabView, Excel, arbitrary format file uploads Components test results – interfaced to VME, LabView, Excel, arbitrary format file uploads Cables and pipes Cables and pipes Patch panels and junction points included Patch panels and junction points included Racks and components within racks Racks and components within racks Level of details (dictionary) Level of details (dictionary) Sub-detector components – user defined Sub-detector components – user defined Can be as low as a readout chip on a front-end card or as high as an entire TPC module Can be as low as a readout chip on a front-end card or as high as an entire TPC module Cables and pipes – origin and destination points (passing through patch panels) Cables and pipes – origin and destination points (passing through patch panels) Racks – down to modules in the crates Racks – down to modules in the crates

Information session on INB database activities in LHC experiments 5 Components localization Two distinct classes Two distinct classes Virtual (not installed or a part of a bigger assembly) Virtual (not installed or a part of a bigger assembly) Existing (installed) Existing (installed) Installed components localization Installed components localization Detector group defined location within the detector assembly, following general ALICE localization schema Detector group defined location within the detector assembly, following general ALICE localization schema Taking into account the specific detector layout Taking into account the specific detector layout For cables, pipes and racks – following ALICE integration team localization schema For cables, pipes and racks – following ALICE integration team localization schema Designed wrt the ALICE cavern and infrastructure layout Designed wrt the ALICE cavern and infrastructure layout

Information session on INB database activities in LHC experiments 6 Use of the database Detector components Detector components Strongly encouraged, but not enforced Strongly encouraged, but not enforced All construction information (archival) is stored only in DCDB All construction information (archival) is stored only in DCDB For Integration activities For Integration activities All cables installed by the integration team or contractors are in DCDB All cables installed by the integration team or contractors are in DCDB All racks and rack components are in DCDB All racks and rack components are in DCDB In general, the ALICE policy it to use DCDB as a component repository to facilitate the work of the detector groups and the integration team In general, the ALICE policy it to use DCDB as a component repository to facilitate the work of the detector groups and the integration team

Information session on INB database activities in LHC experiments 7 Traceability of equipment Every component carries its own unique identifier (automatically generated in DCDB) Every component carries its own unique identifier (automatically generated in DCDB) Designed following the LEMIC decision of 18/11/2003, outlined in EDMS doc “CERN equipment identification” Designed following the LEMIC decision of 18/11/2003, outlined in EDMS doc “CERN equipment identification” ALICE implementation: EDMS doc “Naming and numbering convention for the ALICE detector part identification ALICE implementation: EDMS doc “Naming and numbering convention for the ALICE detector part identification The component state is logged in DCDB The component state is logged in DCDB Assembled, partitioned, destroyed, … Assembled, partitioned, destroyed, … DCDB interfaced with printing facility DCDB interfaced with printing facility Production of labels with the unique ID and a bar code Production of labels with the unique ID and a bar code

Information session on INB database activities in LHC experiments 8 Access and operation Authentication Authentication Username/password based Username/password based Authorization Authorization Only selected experts within detector groups and integration team have write access to DCDB Only selected experts within detector groups and integration team have write access to DCDB All modifications to the DB content are logged and for certain operations (especially for cables and rack content) have to be approved by a ‘top level’ expert All modifications to the DB content are logged and for certain operations (especially for cables and rack content) have to be approved by a ‘top level’ expert Read only access is granted more widely, still username/password is required Read only access is granted more widely, still username/password is required The satellite instances are operated by the sub- detector groups (typically 1-2 people have write access) The satellite instances are operated by the sub- detector groups (typically 1-2 people have write access) The access for integration is 1 expert + 1 ‘top level’ expert The access for integration is 1 expert + 1 ‘top level’ expert

Information session on INB database activities in LHC experiments 9 Examples Detector components Detector components

Information session on INB database activities in LHC experiments 10 Examples Cables Cables

Information session on INB database activities in LHC experiments 11 Some statistics 200K detector components of various complexity 200K detector components of various complexity 15K cables, 6700 connection nodes 15K cables, 6700 connection nodes 200 racks, 5000 rack elements 200 racks, 5000 rack elements New components/cables/rack elements are added daily New components/cables/rack elements are added daily

Information session on INB database activities in LHC experiments 12 DCDB support and manpower User support and DB operation – 1 PJAS (CERN) User support and DB operation – 1 PJAS (CERN) Data integrity and updates FTE (CERN) – PJAS above + ‘top level’ expert Data integrity and updates FTE (CERN) – PJAS above + ‘top level’ expert Software development – Warsaw University of Technology (2 FTEs) Software development – Warsaw University of Technology (2 FTEs) 0.1 FTE in the detector groups 0.1 FTE in the detector groups

Information session on INB database activities in LHC experiments 13 Summary ALICE is operating a database as a detector equipment repository ALICE is operating a database as a detector equipment repository Its use is quite extensive, with relatively high level of details and unique components traceability Its use is quite extensive, with relatively high level of details and unique components traceability We need to study how to adapt DCDB to the INB requirements We need to study how to adapt DCDB to the INB requirements