1 May 10, 2007 Detector group organization For the CDR writing we had identified subsystem editors/conveners  This structure has concluded its function  Many thanks for the effort and commitment We should move forward to the next phase Goals:  Advance the R&D activity as coherently as possible  Start creating the infrastructure and doing the work needed for a Technical Design Report  Prepare the ground for the formation of a collaboration We need to keep a delicate but essential balance:  Move forward coherently  Leave room for other groups to join

2 May 10, 2007 R&D Perspectives R&D will be funded at the local or regional level until there is a SuperB collaboration. Groups approach(ed) their funding agencies to get support for what they’re interested in. Nonetheless now that we have a CDR detector, coordination of activities is important:  Identify the most important R&D issues  Avoid duplication of effort  Act together to ask for money  Provide a structure for new activities or new groups

3 May 10, 2007 R&D Coordination I think it would be useful to setup a structure of R&D conveners for the subsystems with the job of:  Keep track/coordinate activities  Help groups focus on what is needed  Provide a point of reference for groups or individuals wishing to participate  Help prepare funding proposals or reports Each subsystem should have one or two conveners  Let’s use the rest of this workshop to discuss about names  Not all the vacancies need to be filled now  Not a life sentence: which should allow dynamic adaptation as things evolve

4 May 10, 2007 Subsystems MDI (including beam pipe) SVT (including Layer0) DCH EMC (including endcaps) PID (including endcaps) IFR Electronics Trigger/DAQ Computing Software

5 May 10, 2007 R&D Review and choices At some point we will need a more formal R&D review process  Committee to review and monitor activity and provide advice to the management  IMHO this should be setup when the collaboration is formed or forming For some regions it may be advantageous to create this committee earlier We need to explore the ramifications of this proposal Eventually we will have to make choices about technology  Usual difficult balance between good that works and better that might not  We should use the time in front of us to develop the new technologies as much as possible  Act together as a group working towards an experiment Minimize pain and disappointment when choices will actually be made by the SuperB collaboration

6 May 10, 2007 Software Simulation  We need to ramp up our simulation ability More and more detailed  Connection with physics group and accelerator design Physics studies Background simulation Detector studies Infrastructure  We need to start setting up a software infrastructure (and group)  From repository to framework  We’ve been using SLAC/Babar so far. How much longer ?

7 May 10, 2007 Last but not least Infrastructure in Tor Vergata  We need to proceed with a feasability study for the Tor Vergata site  It is essential to define building volumes and functions Experimental hall(s), support buildings and caverns, shafts, assembly halls, …  We have regular meetings with the Tor Vergata engineers and architects Need input and answers from the Accelerator and Detector group