Goals of the ILC-Asia Meeting at Pohang

1. Goals of the ILC-Asia Meeting at Pohang Fumihiko Takasaki PAL, Feb. 17, 2006

2. We thank our colleagues of PAL for making this meeting possible.

3. Goals of the Meeting • To have an understanding of the GDE activities and also to have a good prospect for the RDR and beyond. • 2. To exchange idea for the R&D programs in Asian laboratories.

4. Global Design Effort - B. Barish Dec. 9,05 - • The Mission of the GDE • Produce a design for the ILC. • Coordinate worldwide prioritized proposal driven R&D efforts.

5. The GDE Plan and Schedule - B. Barish Dec. 9,05 - 2005 2006 2007 2008 2009 2010 Global Design Effort Project Baseline configuration Reference Design Funding Technical Design globally coordinated regionial coord ILC R&D Program expression of interest Siting Hosting sample siｔes FALC International Mgmt ICFA / ILCSC

6. Baseline Parameters were • chosen by the BCD. • The GDE is now moving • from the BCD into the RDR. • By the RDR, we will have • an ILC Design with costs • so that we can show it to • the funding Agencies.

7. Some Information on the GDE For refreshing our memory

8. Function of the Central Team and the Regional teams ILCSC – Daigu Sept 05 : B. Barish • The Central Team is the focal point for the ILC design effort, holding the schedule, major milestones, and parameter list, and providing intellectual leadership under ICFA guidance. • Regional Teams perform the R&Dand design work of ILC systems in close coordination with the Central Team.

9. GDE Organization for Snowmass - B. Barish Dec. 9,05 - • WG1 LET bdyn. • WG2 Main Linac • WG3a Sources • WG3b DR • WG4 BDS • WG5 Cavity Technical sub-system Working Groups Provide input Global Group • GG1 Parameters • GG2 Instrumentation • GG3 Operations & Reliability • GG4 Cost & Engineering • GG5 Conventional Facilities • GG6 Physics Options Studies issues common across the WGs.

10. GDE Structure and Organization - B. Barish Dec. 9,05 - • Executive Committee for Baseline Configuration • GDE Director • Barish • Regional Directors • Dugan – Americas • Foster – Europe • Takasaki – Asia • Accelerator Leaders • Yokoya - Asia • Raubenheimer - Americas • Walker - Europe • Responsible for decisions and documentation for the Baseline Configuration Document (BCD) • Discuss issues by a Tele-conference once a week. GDE Executive Committee

11. GDE Organization Central team members : 49 → 60 • Americas 21 • Europe 23 • Asia 16 They are core people to Design the ILC.

12. 16 GDE members from Asia Norihito Ouchi Nobuhito Terunuma

13. GDE RDR / R&D Organization - B. Barish Dec. 9,05 - FALC ICFA FALC Resource Board ILCSC GDE Directorate GDE Executive Committee GDE R & D Board GDE Design Cost Board GDE Change Control Board

14. GDE Organizational Evolution for RDR - B. Barish Dec. 9,05 - • Change Control Board (CCB) • The baseline design will be put under configuration control of the CCB. • Design / Cost Board (DCB) • The DCB will coordinate the reference design effort, including costing, etc: Check the consistency of the overall design. • R&D Board (RDB) • The RDB will evaluate, prioritize and coordinate the R&D program with a single chair

15. GDE RDR / R&D Organization FALC ICFA FALC Resource Board ILCSC - B. Barish Dec. 9,05 - GDE Directorate GDE Executive Committee GDE R & D Board GDE Change Control Board GDE Design Cost Board Global R&D Program RDR Design Matrix ILC Design Effort ILC R&D Program

16. R&D Budget (FY 05/06) Region Americas Asia Europe Total (M$) 32.9 (M$) 9.9 (O-Y) 31.1(MEu) FTE 131.2 30.5 281.0 M&S 9.2 (M$) 9.9 (O-Y) 14.2(MEu)

17. Area Systems Damping Main Technical Systemse- sourcee+ source Rings RTML Linac BDS Vacuum systems Magnet systems Cryomodule Cavity Package RF Power Instrumentation Dumps and Collimators Accelerator Physics  Global Systems Commissioning, Operations & Reliability Control System Cryogenics CF&S Installation

18. - B. Barish Dec. 9,05 - Updated list: K. Yokoya

19. - B. Barish Dec. 9,05 - Updated list: K. Yokoya

20. Charges of Area System, Tech. System and Global System and Also Schedule toward RDR - GDE-EC Jan 13, 2006 - Described in a file, RDR_Charges_01-12-06.doc.

21. Steps toward RDR GDE Meetings Bangalore Vancouver Barcelona Bangalore : To coordinate the work for the RDR and cost estimate. A place for communications between the various groups and the boards.

22. Request for Sample Site Information To be used to study siting issues, in advance of a call for “expressions of interest” to host the ILC - B. Barish Dec. 9,05 -

23. Goals of the Meeting • To have an understanding of the GDE activities and also to have a good prospect for the RDR and beyond. • To exchange idea for the R&D programs in Asian laboratories. • Thank you for your attention.

24. Back-up slides

28. GDE Structure and Organization • GDE New Groups • Design / Cost Engineers • Shidara – Asia • Bialowons – Europe • Garbincius – Americas • Siting, Civil Construction and Infrastructure • Baldy - Europe • Enomoto – Asia • Kuchler – Amercas • Physics / Detectors (WWS chairs) • Brau - Americas • Richard - Europe • Yamamoto - Asia • Accelerator Experts (44 GDE members)

29. ILCSC – Daigu Sept 05 : B. Barish • Responsibilities of the Central Team • Manage the execution of the ILC design and associated R&D; • Establish technical and administrative controls to ensure thatthe agreed-upon work toward the RDR and TDR is executed within their approved cost, schedule and technical scope under the MOU; and • Maintain and control the machine parameters database and configuration documents, and direct overall design effort.

30. Approach to ILC R&D Program - B. Barish Dec. 9,05 - • Proposal-driven R&D in support of the baseline design. • Technical developments, demonstration experiments, industrialization, etc. • Proposal-driven R&D in support of alternatives to the baseline • Proposals for potential improvements to the baseline, resources required, time scale, etc. • Develop a prioritized DETECTOR R&D program aimed at technical developments needed to reach combined design performance goals.

31. The Area system reports should include progress since Frascati, unresolved issues, schedule for completing the design with milestones, what communications have taken place with the TS and GS, what will be needed on what timescale, what problems they foresee, concerns, etc.. The Technical systems should present what has been done so far, cost and engineering methodologies, level of detail of the estimates, when they need what information from the AS and GS, schedule for completing the cost estimate with milestones, what problems they foresee, concerns, etc.. The Global system reports should include some combination of the above – progress, schedule, milestones, communications, needs, problems, etc.