Interlock Actions and Matrix for DSS Server in SR1 Environment

Slide Note
Embed
Share

Proposal and implementation plan for interlock actions and matrix coordination between DSS server rack and user areas in SR1. Includes agreements, alarms-actions matrix finalization, cable routing, server installation, and commissioning with dummy loads. Discusses CO2 plant signals, temperature monitoring, emergency actions, and interlock strategy for Pixel DCS/DSS and ITk integration.


Uploaded on Jul 19, 2024 | 4 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

E N D

Presentation Transcript


  1. Next 1. Agree the interlock actions and matrix between DSS rack and user areas 1. 2PACL has a signal DSS to stop in: The input matrix is to be defined. 2. Finalize Alarms-Actions-Matrix, started by Ignacio (see agenda) 3. Presentation in Strip and Pixel integration meetings 4. Send for approval 2. Follow-up on hazard list with ATLAS Safety (https://edms.cern.ch/document/2515624) regarding CO2 related risks in SR1. One discussion took place, initiated by Lukasz, with Laure. 3. Cables between DSS server and plant/users: 1. Collect number of cables to be routed in SR1 2. Purchase via 2.3.1.4., orders for DSS-cooling plant by cooling team, DSS-subsystem areas by sub-systems teams 3. Installation to be discussed with Marco et al 4. Installation of DSS server and logic: date to be defined 1. Approval by BE-ICS 2. Areas not connected, due to e.g. later start date, will use inhibit of alarms . 5. Commissioning with dummy loads in all areas 1 5.4.2023 DSS server and interlock matrix for SR1

  2. AAM Proposal Table on indico Question about implementation of AUG button Actions for add/modify? 2 5.4.2023 DSS server and interlock matrix for SR1

  3. SPARE 3 5.4.2023 DSS server and interlock matrix for SR1

  4. Interlock actions 1. CO2 plant sends a hard-wired signal: OK, set point reached . This provides indirectly a temperature information that a test setup can be interlocked if plant running at wrong temperature. Temperature information of the plant is available via DIP. 2. In case cooling plant status ok DSS signal to areas, plant ok 3. In case one area needs to go warm (too high dew point) DSS issue plant to go warm, and all other areas that plant goes to warm Actions in areas to operate warm 4. In case one area needs to go to off DSS issue plant to go off, all other areas that plant not ok. The action plant off is only foreseen in case of a fire. It should be noted that the CO2 is still distributed in pipes in this case. 5. In case plant stops DSS issue all areas plant is not ok 6. In case of smoke alarm in SR1, emergency off of SR1 DSS issue go to warm to plant, emergency off to all areas. Proposal to keep DCS PCs on 7. In case one area is not ok DSS issue to plant that area that it is not. Further action to be defined. 4 29.3.2023 DSS server and interlock matrix for SR1

  5. Pixel DCS/DSS strategy on surface If Interlock matrix/PLC has enough ports and common development started with Strips, Pixel and ITk DCS, the environmental sensors could also be routed via this readout path. Graphics from system test Benedikt Vormwald, CERN 5 5.4.2023 DSS server and interlock matrix for SR1

  6. ITk Interlock Strategy The interlock strategy for pixel integration in cavern is documented on EDMS 2387552 (currently being updated) A hardware-based interlock system built on a fail-safe logic that will protect the ITk detector from damage to the detector and personnel. There are interlock detectors (which sense conditions that require a protective action) and interlock-controlled devices (equipment which must be switched off, i.e. respectively controlled). The interaction between them is defined by the interlock-matrix. To keep the number of devices out of service as low as possible, it is aimed to switch off just the part of the equipment which is directly involved in a risky situation. Interlinks with ATLAS central DSS and DCS are considered There are primarily 3 kind of dangers to be handled by interlocks: Overheating (mainly a risk to the detector and equipment). Typically, smaller units will be affected by overheating; therefore, dedicated actions on fractions of devices are required here. Danger to the entire detector due to a failure in the cooling system, or smoke etc. On surface: to high dewpoint Risks to human beings caused by lasers. Apply strategy also for surface testing during integration and commissioning DCS (monitoring to be adapted too) 6 5.4.2023 DSS server and interlock matrix for SR1

  7. Sensors environmental: in surface testing Number sensors being collected in EDMS 2606284 and EDMS 2044113 Assumption that only those of the sub-detector segment under test are read in each testing step. (Reading all will probably be limited by availability and affordability of type-2 cables.) Sensors during integration testing Sub-system test step # sensors (A- + C-side) #PP1 connectors Environmental IS integration 2x24 2 OB integration 2x21 2 EC integration 2x16 4 PP1 dressing 2x8 2 Cooling IS integration 40 2-wire 2 OB integration 44 2-wire 2 M. Hamer: https://indico.cern.ch/event/1052545/con tributions/4432624/attachments/2273816 /3862207/TsensorGroupingAtPP1.pdf EC integration Shared with env. 44 2-wire, OS integration 11 4-wire 2 7 5.4.2023 DSS server and interlock matrix for SR1

Related


More Related Content