1 / 10

IBL Update H. Pernegger, G. Darbo (PO 12/5/09)

IBL Update H. Pernegger, G. Darbo (PO 12/5/09). Organization and WG coordinator Schedule Decision Items Organization Tools & Meetings. Management board. IBL Management Board Membership: IBL PL + IBL TC 2 coordinators from each WG P lus “extra” members. Module WG (2 coordinators) FE-I4

colini
Download Presentation

IBL Update H. Pernegger, G. Darbo (PO 12/5/09)

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. IBL UpdateH. Pernegger, G. Darbo(PO 12/5/09) Organization and WG coordinator Schedule Decision Items Organization Tools & Meetings

  2. Management board • IBL Management Board • Membership: • IBL PL + IBL TC • 2 coordinators from each WG • Plus “extra” members • Module WG • (2 coordinators) • FE-I4 • Sensors • Bump-Bonding • Modules • HDI • Test & QC • Irradiation • Stave WG • (1 Phys + 1 Eng.) • Staves • Loaded Stave • Internal Services • Test & QC • Cooling Design & Stave Thermal management • IBL Integr.-Install. • (2 Eng.) • Stave Integration • Global Sup. • Beam Pipe (BP) • Ext.services inst. • IBL+BP Installation • Cooling Plant • Test & QC • Off-detector • (1 Phys + 1 E.Eng.) • Power • DCS • ROD • Opto-link • Ext.serv.design/proc • Test Beam • System Test

  3. IBL MB Composition • PL and TC propose the following IBL (MB) Composition: • IBL Project Leader: G. Darbo (Genova) • IBL Technical Coordinator: H. Pernegger (Cern) • “Module” WG: Maurice Garcia-Sciveres (LBNL) + Fabian Hugging (Bonn) • “Stave” Working Group: Ole Rohne (Oslo) + Danilo Giugni (Milano) • “IBL Assembly & Installation” WG: Neal Hartman (LBNL) + Raphael Vuillermet (Cern) • “Off-detector” WG: Tobias Flick (Wuppertal) + Stephane Debieux (Geneva, tbc) “Extra” members: • Ex officio: Upgrade Coordinator (N. Hessey), PO Chair (M. Nessi), Pixel PL (B. Di Girolamo), ID PL (P. Wells), Pixel Chair (C. Gößling) • Offline “liaison”: Pixel Off-line coordinator (A. Andreazza) • TDR editor (K. Einsweiler + M. Capeans) • Working Group coordinators have been selected in discussion with IBL PL, IBL TC , the candidates and responsible of their home institutes. • Normally WG coordinators are endorsed by Institute Board • We propose to appoint WG coordinators today ad interim and present this proposal for endorsement at the IB kick-off meeting on July 8. • Appointment is for a two years term

  4. Institute Board July 8 (Atlas week)

  5. Working group mandate • WG coordinators will • In design phase: follow interfaces, define tasks, deliverables, study design options and contribute “their” sections to the TDR • In production phase: lead qualification process on prototypes and follow construction deliverables and tasks through the project • Track actions in their area and report them to the MB • PL and TC have asked workgroup coordinators now to prepare a “mandate” for each working group which includes: • List of activities for each WG • Update of list of deliverables where applicable • First preliminary estimate of resource needs (manpower!) and schedule for R&D, prototyping and construction • Have already a first draft for 3 WG (see last two MB meetings) • This is to be included into the IBL Project Organization Document ATU-ORG-MG-0001 by Giovanni, Heinz, Nigel ready for presentation at the IB kick-off meeting

  6. Towards a Schedule: general consideration • Assume an installation date of Oct 2013 (obviously we will get more info during the time to come) • The schedule is build by working “backwards” from the installation date • A later date (2014?) may give us more time for RD (FEI4) but needs to be balanced with the need for contingency. • We need to forsee time for commissioning after the installation date. • The IBL is small in “number of modules” • Many components are produced with a “single batch” hence our scope to overlap activities and component production is limited • This is a first attempt with many assumptions and over the next week(s) we will develop a detailed schedule for each working area • This can then become a first “baseline” schedule • It does not yet include most of the prototyping (except on chips & sensors) • Based on this first baseline schedule we need to agree on milestones • The schedule will (in some cases) drive the decision making process and timescale for technical decisions (see later)

  7. FEI4 drives the schedule for modules • getting the next FEI4 asap is crucial for module qualification • do we need 2 eng. Runs or 2 eng runs + 1 prod run? Stave 0 plays a crucial to qualify the IBL system (staves and off detector electronics) Service installation happens in shutdowns - need definition & procurement of services (USA15->PP2) early on to use shutdown time efficiently

  8. Decision items • Goal is to establish • Where do we need studies? • When do we have to decide between options? • Need to understand which items need redesign and to develop a complete system layout. This can then be used to update list of deliverables and coordinate the institute’s contributions and provide input to funding requests. • The following list is sorted by working area and nothing more than a personal view • Module • Sensor technology to be used in IBL (mid 2010) • FEI4 functionality & “IBL” version: based on next prototype and its test results: this drives the schedule for IBL , need to investigate if we can build IBL on 2 engineering runs (present schedule) or need 2 eng. Runs + 1 production run (during module assembly) • Module size (end 2009?) : this drives mech. designs • Bump bonding : only 1 vendor or qualify second for FEI4? • Stave • Stave cooling : which type of pipe and coolant? (end 2009?) • Single stave or bi-stave engineering • Fittings/connectors at end of stave or “7m” object? (end 2009) • EoS card: is it passive or does it need active parts (data, power) (end 2009)

  9. Decision items cont. • Integration and installation • Beam pipe removal feasibility study to be concluded (mid 2008) for tooling design • Exact beam pipe specs for IBL and replacement beam pipe (when?) • Support “strategy” for IBL: on BP or on a “mini” PST (when?) • Off-detector • Powering: study for what to do if DC-DC conv. nn FEI4 cannot be used (can start now) • Services inventory and detailed specifications for power,readout,cooling (end 2009?): needed to plan installation and routing • ROD/BOC specs revisited with FEI4 test results (mid 2009?)

  10. Meetings & Work spaces • Regular meetings • Management board weekly Mo 15h30-17h30 • Module & Off-detector WG bi-weekly Thursday • Stave and Integration/Installation WG bi-weekly Tuesday • Still investigation best possible meeting configuration in ID with Pippa • General meetings : 2 days (next June 25-26) • Currently book rooms for those meetings with help from Atlas secretariat • Mailing Lists • Created one per WG + general + Management board • Share point: Collaborative work space for WGs and MB • https://espace.cern.ch/atlas-ibl/default.aspx • Action list on Share point created • “Track Issue” in MB Share Point • EDMS tree created for technical documentation • https://edms.cern.ch/cedar/plsql/navigation.tree?p_top_id=1502214928&p_top_type=P

More Related