1. E. Calvo (BE/BI-QP) 12/10/2015 LHC BI fibre infrastructure

2. E. Calvo (BE/BI) 2 / 11 Aim and Outline BI fibre infrastructure overview Context Proposal Needs, Wants, Likes and concerns… The objective is to evaluate if the exchange of information and the way BE/BI and EN/EL collaborate can be optimized.

3. E. Calvo (BE/BI) 3 / 11 CCR SR3 SR1 SR2 SX4 SR5 SR6 SR7 SR8 BI fibre infrastructure overview : LHC Initially, proposed for the BPM system for transmitting the position signals from the front-end cards (in the tunnel) to the acquisition cards (in surface) ~2176 operational links @LHC ~1088 spares Very early, extended to the BLM system, with a very similar distribution. ~1600 operational links And to the BST system: Broadcast distribution of timing signals from the CCR towards many surface and underground LHC and SPS locations. 1:16 splitters in surface buildings >200 operational links more

4. E. Calvo (BE/BI) 4 / 11 BI fibre infrastructure overview : LTI & SPS Very old infrastructure for distributing timing signals (BST): ~24 operational links The new fibre distribution for the BPM system (MOPOS) ~432 operational links And future BLM? BA1 BA2 BA3 BA4 BA5 BA6 BA7 BPM as in the LHC: ~200 operational links BA7 BA4 Distribution of timing and signals between the CCR and BI laboratories in the CERN Prevessin area. CCR 866 865 867

5. E. Calvo (BE/BI) 5 / 11 Context and a bit of legacy During LHC installation, the termination patch cords (tunnel and surface) were handled by BI (labelling, installation, etc.) → Mapping (documentation of which signal is on which panel/connector, available spares, etc.) was generated and maintained by BI. Mini-tubes came with a standard number of fibres → BI had many spares. Every small request from new BI users was tried to be fulfilled within the BI available infrastructure → Faster, cheaper, more efficient. The number of BI users increased with time: Ex: -DIDT and MIM (in UA47), Prepulses (in Pt.2 & 8), TTC signals for BGV (UA43), Diamond detectors in (Pt. 2, 4, 5, 8), 400MHz for Schottky (Pt. 4), White rabbit for MIM, BRAN signals (Pt. 1), Ethernet links for DOROs (Pt 1 & 7), etc.

6. E. Calvo (BE/BI) 6 / 11 Current situation Frequently, new requests can not be fully route with existing BI infrastructure → Part of the routing is requested to EN/EL → Documentation is split between both teams and routing requires several iterations. The documentation, initially organised for BPM and BLM systems, is not appropriate for other users (multiple racks). Information is distributed through several files: surface rack, tunnel racks, patch cords labels, etc. Should EL-CF and BI continue having a BI link person ? Is this splitting of information the most efficient way of managing the BI fibres?

7. E. Calvo (BE/BI) 7 / 11 Proposal Integrate BI fibre infrastructure in the EN/EL fibre database (or documentation system). So that… 1) BI users contact directly EN/EL-CF 2) EN/EL-CF can completely route the new requests (using BI infrastructure when possible) 3) EN/EL-CF keep the information updated, complete and in a standard way. Not important differences in the way of working for EN/EL … but an important effort in -understanding the current BI documentation -and (eventually) adapting it to EN/EL standards

8. E. Calvo (BE/BI) 8 / 11 Needs, Wants & Likes (I) Be able to connect/unconnect cards at the link ends for maintenance/upgrade/test purposes. Usually <10 links per TS Flip patch cords for disentangle tx/rx issues. BPM can verify correct routing. (BST also can). This is not the case for other systems. Access to the database/documentation system. Know about links routing and links availability. EN/EL “Piquet service” for patching or repairing links. EN/EL particular patch cord store. (BI wishes to keep its small local stock of patch cords as till now). Access to additionall information about the link : length, full attenuation, number of connectors, OTR data Update information in the database: Ex. routing information, power @rx. Does this sound acceptable

9. E. Calvo (BE/BI) 9 / 11 Needs, Wants & Likes (II)  Clear and complete documentation: BI has different levels of documentation quality: - Recent links follow EN/EL standards (visio templates, with panel names, connector types, patch cords lengths, etc) + photos (notes) - BPM, BLM and BST links @ LHC are mainly rack layouts and patch cord excel tables. - BLM has also all the links in the layout database. - Old BST links @ SPS have an excel table with building and rack numbers (there is not information about repeaters, optical attenuators or available spares). If the proposal is retained/considered, first steps will be study the documentation and probably make a series of visits to the facilities. https://edms.cern.ch/project/CERN-0000115916

10. E. Calvo (BE/BI) 10 / 11 Needs, Wants & Likes (III)  Teams should negotiate and stablish a rigorous procedure to keep the documentation up to date. Methods are diverse: direct access to the data base, email, some kind of “DIF” form (“DMF”: Demande de Modification de Fibres? ), etc Something else?

11. 11 / 11

12. 12 / 11

13. E. Calvo (BE/BI) 13 / 11 Example of SX4

14. E. Calvo (BE/BI) 14 / 11 Ex. of SR1 star point rack

15. E. Calvo (BE/BI) 15 / 11 Ex. Diagrams for new BI users

16. E. Calvo (BE/BI) 16 / 11 Kind of connectors used BPM, BLM and BST panels @ LHC ST: BST rx @ LHC LC: Rx @SPS new MOPOS and growing community of new systems FC/PC: Some old patch panels @ SPS

17. E. Calvo (BE/BI) 17 / 11 BLM fibres in the Layout DB

18. E. Calvo (BE/BI) 18 / 11 CO rack configuration tools