1. Communications IBL Management Board #25 CERN/Phone, March, 15th 2010 G. Darbo - INFN / Genova Share Point Collaborative WS: https://espace.cern.ch/atlas-ibl/MB/default.aspx

2. Extended Pixel IB • First “Pixel Extended IB” held on March 1st. • Discussed the MoU annexes – Share of Cost and Work Responsibilities • 42 Institutes are presently part of the MoU - >20 on sensor prototyping • Some institutes expressed interest: • Victoria: support for diamond sensors (MoU item 1) and diamond loaded glue (MoU item 4) • Washington: capability on mechanics, tight relationship with SLAC/LBNL, no items or work assigned up to now. • Bern: interested to collaborate with Geneva, no items or work assigned up to now. • Discussion outcome: • IBL project with delivery for installation for end 2014 – accepted (not put into discussion) • No substantial divergence from the circulated MoU – very smooth discussion, some changes requested (recognize ACTA work in the MoU), some clarification on MoU item 8 (Integration & System Test) requested and other minor issues. • Next steps: • Update / correct annexes – NCP meeting discussion in Desy – collect signatures.

3. AUW in Desy • Scheduled 3 hrs for reporting IBL project in Desy • AUW IBL session is for reporting to ATLAS Upgrade community of advancement of the project and is not intended to replace the IBL GM. • Consider 6 – 8 talks: • IBL Project – Update on Organization and MoU • IBL Project Technical Overview and TDR • FE-I4 • Sensors prototype program for IBL • Stave Prototype program • New ROD/BOC • Installation Issues (?) • Loaded stave

4. IBL Topics @ Conferences • IBL becoming an ATLAS project • Presentations to conferences must be coordinated through speakers committees. • How to deal with IBL topics for Conferences • IBL General Talks (*): Author has to contact ID Speaker Committee before sending abstract for a General IBL talk. ID Speaker Committee will verify possible incompatibilities and communicate to the Author. • IBL Subsystems: Author(s) has to agree the abstract content in the related WG and inform ID Speaker Committee. • Sensor Prototyping Activities for IBL (connected to FE-I4): IBL PL, ID Speaker Committee and Upgrade Speaker Committee (since sensor activities are aslo for sLHC) have to be informed. • Sensor development not directly linked to FE-I4: Upgrade Speaker committee has to be informed (this is R&D for sLHC where IBL is not involved). • Additional issues • (*) Conference Organizers usually contact ATLAS Speaker committees for general talks. IBL PL is collecting a list of speakers from each institute leader with the aim to propose speakers. General IBL talks will be dealt in future through this channel and not by individual submissions of abstracts. • If sensors are presented to a conference, in addition to IBL, the chair of the related R&D project has to be informed/involved from the moment of the abstract presentation to the approbation of slides/proceedings. This is not strictly IBL issues, but in the sensor prototype phase we strongly rely on tight collaboration with the ATLAS R&D sensor collaborations and we must recognize their role to validate the results presented. • Short document will be circulated to IBL Collaboration with rules to follow: • Draft in preparation following the former list of rules.