1 / 15

The CMS Pixel upgrade Integration project PROPOSED AGENDA

Detailed agenda for the CMS Pixel upgrade project integration meeting including system upgrade status, engineering questions, integration role definition, and data management. Discussion on interface considerations and future milestones.

spieker
Download Presentation

The CMS Pixel upgrade Integration project PROPOSED AGENDA

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Introduction / adoption of the agenda. G.F. Overview of the Pixel system upgrade project, status and plan. R.H. ETH-Z involvement in the Pixel project. R.W. General Engineering and Integration questions & point of view. G.F. Discussion. All General communication and design data exchange agreement. All A.O.B. and closeout. The CMS Pixel upgrade Integration projectPROPOSEDAGENDA G.W. Faber. 02-03-2011

  2. The CMS Pixel upgrade Integration projectG.W. Faber _ ETH-ZurichConsultant CMS Engineering & Integration Centre G.W. Faber. 02-03-2011

  3. Barrel ? - Pixel upgrade Integration meeting building 904 E&I team. E&I team questions: Born out of ignorance and missing knowledge on Pixel status, progress and plans. Goal of the meeting: Get better communication and understanding. Avoid any show stopper later in the integration process. Which are the interfaces: Personnel, Neighbouring systems, Services and infrastructure, Environmental and Internal. Definition of the E&I role and mandate towards the Pixel projects within CMS by Austin. Points of consideration linked to Beam pipe choices: Inner / outer diameter 45 mm final choice? (Physics impact on other CMS detectors) New design Beam pipe support. Scenario Beam pipe replacement and installation. Points of consideration linked to Tracker. Considerations for the Pixel detector upgrade from the E&I team: Optimize design to use all available volume during insertion. Pixel tooling, use most of the “old”, if still existing, system. Pixel positioning and clearances Which problems of the past have been considered and of course new problems are expected. Pixel Integration G.W. Faber. 02-03-2011

  4. Integration office management G.W. Faber ETH-Zurich for CMS 16-06-2010 Verification Configuration Management 3D Modeling Distribution Mock-up Archiving Versioning Configuration Management Production Parameter collection Envelope Link person Reviews CDR EDR… . Lifecycle New Parameters if required CMS self learning E&I process Parameter drawings No-Go zones Electr. Engineering CDD procedures Update agreed Parameter dwg. Test Parameter book Interface Services and Infrastructure “As-build” model Change state of models in DFS Validation Baseline design Prod. lifecycle management E&I office “As-positioned” Survey data Simplified “Self learning” and “Iterative process” approach started in early 1994. Parameter agreement within the CMS MB. Detector envelope definition by the TC. No-Go zone owned by the E&I coordinator. Design support “On Site” Prod. Inst. Follow-up ALARA and RP procedures Digital Mock-up Maint. Upgr. & Inst. Config. Minor nonconformity (CMS E&I NC procedure) Major nonconformity (CMS NC procedure in EDMS) Traceability Engineering change request (CMS ECR procedure in EDMS) Document & (Production/construction/… data) management centralized in EDMS / EMDb Drawing management in CDD or equivalent HPGL type format (Electronic paper archive) CMS friendly 3D model file system DFS. Access to 3D data from outside CERN Integration office support: data conversion, administrative, …. . G.W. Faber. 02-03-2011

  5. Detector _ E&I 3D data file exchange G.W. Faber. 02-03-2011

  6. Barrel Pixel upgrade Integration meeting building 904 E&I team. Which are the interfaces: Safety and RP: activation maps, materials composition and ALARA requirement. Other systems: Beam pipe, Tracker, Bulkhead, PP1, BRM/PLT, Alignment, CMS. Services: Cooling, Gas, Electrical, Optical, RadMon. (passive/active?) Internal: Mechanics, services (support) tube, Forward Pixel, Thermal neutral. Interfaces to: TK rail system, YB0, routing services, balconies and inside USC. Verification/conformity of: Installation- Removal-tooling and personnel access. Are all thermal, dimensional and position tolerances understood? Provide tolerance and position datasheets, resulting in definition of envelope. Agreement “NO GO” zones, determined by E&I and endorsed by the CMS MB. Maintenance, repair, decommissioning and waste management. Clean room, tooling, RP zone, shielding and personnel training requirements. Assign: people, tasks, 3D data exchange, communication, integration responsibilities. Provide a list of projects and actions, which might have an impact on Pixel installation. Set realistic review milestones including a more detailed look at RP/ALARA questions. Are Pixel Barrel/Forward detectors to be considered by E&I as “independent” projects. Revive cabling and equipment database activities S. Bally. Decommissioning of “old” Pixel detector, showcase waste management. Pixel Integration E&I Questions G.W. Faber. 02-03-2011

  7. Barrel Pixel upgrade Integration meeting building 904 E&I team. Definition of the E&I role and mandate towards the Pixel projects within CMS by Austin. Link persons and regular reporting to TC/E&I as in the past? Understand: Cooling, cooling plant and Gas system. (inert Pixel volume) Cabling, routing, racks in USC and Optical fibres. Interface 3D models Pixel Barrel/Forward/Bulkhead/… . Neighbouring systems interface verification. Activation in these areas in 2013/’14 and 2017/ ..beyond. Shielding, personnel protection and access systems. Scenarios and procedures in all phases of the Pixel lifetime are mandatory. Pixel Integration G.W. Faber. 02-03-2011

  8. Barrel Pixel upgrade Integration meeting building 904 E&I team. Points of consideration linked to Beam pipe choices: Outer diameter 45 mm final choice? FEA stability, is there the need for a middle or asymmetric support? (Preferably not! @ dia. 50mm > 2.5mm sag.) If needed, consider using Pixel barrel as a central load bearing Beam pipe support. Support position, changed from cylinder to conical part. (Z position not changed) Maintain compatibility with old Beam pipe? Used as spare, maybe pixel detector not completely closed or minimal clearance. Reduce/rationalise Beam pipe support material budget. Which risks might this imply, as we know the system better now. Less clearance accepted to “realigned” new or spare Beam pipe. The Beam pipe support is driving the inside of the Pixel envelope dimension. Don’t push the inner diameter of the Pixel detector the to the limit. The (MB) agreed “NO GO” zone has to be respected. Installation of new beam pipe, what if not ready or an accident happens. Study fallback solutions and worst-case scenario. Beam pipe bake-out and conditioning just before first Pixel installation? Keep the same Beam pipe tooling as far as possible. Study and confirm, if modifications are mandatory, keep compatibility. Keep the same Beam pipe bake-out equipment. Pixel Integration G.W. Faber. 02-03-2011

  9. Barrel Pixel upgrade Integration meeting building 904 E&I team. Points of consideration linked to Beam pipe choices: New design Beam pipe support. Do we keep the Beam pipe pointing at I.P. Full integration with Beam pipe cone better space economics. Maintain sufficient clearance Pixel to Beam pipe at critical passage. Check integration with Pixel luminosity telescope. (PLT) Check integration with Beam radiation monitoring system. (BRM) Scenario Beam pipe replacement and installation. Consider spare Beam pipe 3.2 to 10.6 meter. New “optimized” design for this new part or just copy the old design. (Done) Include a better survey, alignment and position sensor policy. Consider ALARA for the closing requirements. Pixel Integration G.W. Faber. 02-03-2011

  10. Barrel Pixel upgrade Integration meeting building 904 E&I team. Points of consideration linked to Beam pipe choices: New design Beam pipe support. BP supported on the Cone – Material choicefor conical part and transition Sst. or Be. Scenario Beam pipe replacement and installation. Study clearance with optimized BP support and existing rail system. Pixel Integration BP ID = 50 mm. BP OD = 45 mm. G.W. Faber. 02-03-2011

  11. Barrel Pixel upgrade Integration meeting building 904 E&I team. Points of consideration linked to Tracker: Activation in bulkhead region. Activation inside TK cylinder and rail system. Optimize environmental shield design tracker. Pixel reservations and modifications inside Bulkhead. Which services / electronics are moved from services tube to- or past- the Bulkhead. Choice of connectors, including cooling and gas, evaluate risk to neighbouring systems. Agree on a program of test and validation processes under LHC HL conditions. Pixel Integration G.W. Faber. 02-03-2011

  12. Barrel Pixel upgrade Integration meeting building 904 E&I team. Considerations for the Pixel detector upgrade from the E&I team: Optimize design to use all available volume during insertion. Device a system of sensors targets and references to position and align optimal. Avoid “active” position adjustment of Pixel, next removal after several years. Risk of blocking the Pixel detector in position, ALARA requirement. Keep sufficient clearance on the outside diameter of the Pixel detector. Compensate the Tracker misalignment on the outer diameter. What is the detector powering policy, using new/different techniques reliability. Can there be a gain in cable- or services- cross section inside the 53° gap? Pixel tooling, use most of the “old”, if still existing, system. Access platform + Table + insertion tool. Check compatibility with Personnel and Radiation shielding. (Modular) TK rail system, validate use for Pixel upgrade. (No modifications needed?) Understand radiation levels in different phases of the detector lifetime. Understand radiation level at removal, if required early in a shutdown. Update calculations done by Mika with better understanding of LHC. Consider automated/robotic inspections and interventions. (ALARA) Get data on RP activation in view of cool down time requirements. Include PLT/BRM/Bulkhead activation/cool down time in procedures. Pixel Integration G.W. Faber. 02-03-2011

  13. Barrel Pixel upgrade Integration meeting building 904 E&I team. Pixel positioning and clearances: Survey is difficult, Radiation hard sensors problematic and adding materials. Make remote measurements only at installation and maybe at removal. Remove remote measuring system after Pixel installation, before closing. Design such system in common with the Beam pipe positioning system. Should there be an “Integrated” CMS Alignment/Positioning project. This area of CMS could be part of it. Pixel Integration G.W. Faber. 02-03-2011

  14. Barrel Pixel upgrade Integration meeting building 904 E&I team. Which problems of the past have been considered and of course new problems are expected: Cooling changes. New problems will showup. Changes in services expected, to be confirmed. Use of the PP1 volume to be understood, what is the “filling factor”? Do we need to investigate possible volumes on the outside of the Magnet barrel? Interface space to be created between Barrel and Forward Pixel. Materials budget in the services cylinder to be understood and maybe reconsidered. Are there possibilities to reduce the materials budget in the service cylinders? Some of the electronics is removed from the services cylinder. The new position of electronics to be understood. Powering / cooling and impact on the neighbours. Less cooling in the 53° gap. Maybe impact on the TK Bulkhead too. Is there a risk of coolant activation in the new system. (Understand risk of pollution) List of foreseeable interventions in view of ALARA. Is there data available on energy loss in the NEW Beam pipe inside the TK / Pixel volume. Can we estimate the B.P. temperature rise as risk for Pixels at HL LHC running? Do we need to install a complementary temperature measurement system? Pixel Integration G.W. Faber. 02-03-2011

  15. WOGEI meeting (chair CMS technical coordinator) exchange of ideas and choices of technical solutions. Link meeting (chair CMS general integration coordinator) short status reports and initiate problem solving processes. Envelope dimensions (proposed by the CMS technical coordinator to the management) defined for every element; simple, everything has to fit inside and to be neutral to the neighboring systems. Interface designs (proposed by the link persons, coordinated within the integration team) the only element spanning the volume between envelopes. “No_Go Zone” (owned by the Integration coordinator) free volume between envelopes determined after a risk analysis. Procedures/configurations (for planning, maintenance, interventions and upgrades.) Data bases Parameter Book“Started on paper!!! And still is …” STD3DEuclid models conversion to Catia CDD2D drawing information repository EDMSEngineering documents repository Cabling / EMDb“As build / Installed / positioned” Survey data Application to access “As positioned” data. ToolsUsed in the past - to be adapted G.W. Faber. 02-03-2011

More Related