LLRF Collaboration Meeting

Friday 29 Feb 2008, 09:00 → 18:00 Europe/Berlin

3/304 (Helgoland Seminar Room)

Czuba, Napieralski, Romaniuk, Stefan Simrock (DESY), Wrochna

Goals: 1. Discuss how a working collaboration can be achieved and organized. 2. Identify the required prerequisites for a collaboration contract and plan the work to achieve the necessary conditions. Take into account the recommendations of the LLRF review committee. 3. Develop a project plan for the ATCA evaluation project according to the recommendations of the LLRF review committee.

1 Welcome and Status of the XFEL project

Speaker: Reinhard Brinkmann

2 Prerequisites and boundary conditions for a successful collaboration

Speaker: Reinhard Brinkmann

3 Discussion with Prof. Romaniuk about his concerns

Speaker: Ryszard Romaniuk

Answers to Prof. Romaniuk's Questions

Answer to 1: Supervisor needs to be much closer involved in the students' work, so that he can solve any potential problems. Obviously there is some lack of supervision in Warsaw group. LLRF team wide facilitator is needed to help to resolve collaboration issues. Institutes need their own money to provide supervision.

Answer to 2: Original plan was to the development in three steps: 1. SIMCON 3.1 2. SIMCON-DSP 3. SIMCON Gbe With the ATCA standard the step 3 was changed to ATCA. Smaller steps are not possible due to time schedule constraints

Answer to 3: Decission will be based on demostration of controllers from both Institutes as follow: 1. 1st of July 2008 with cavity simulator in lab with ATCA 2. 1st of September 2008 with cryomodule test stand with ATCA 3. January 2009 at FLASH with ATCA 4. Shift on March, 19th - Test of SIMCON controller (8h) - Verity that beam energy stability is better than 0.008% measured in the BC2 whil operating on crest - Demonstrate phase stability during off-crest (10 degrees) operation derivde from beam stability 5. May 20th - Test of SIMCON controller - Demonstration of controller with DOOCS user interface and all functionalities of the present DSP system at FLASH - usage of LLRF hardware configuration as it is installed now in FLASH for user operation

4 Identify prerequisites for a collaboration contract

Speaker: ALL

PREREQUISITES FOR A COLLABORATION CONTRACT: 1. Deliverables, deadlines and cost 1a. Distribution of SWP to Institutes (Responsibilities) 2. Acceptance tests

10:45 coffee break

5 Discuss and agree on LLRF specific collaboration rules

Speaker: ALL

COLLABORATION RULES

1. All information is easily accessible by all collaboration partners 2. It must be easy for everyone (with approval) to make changes of any piece of code (software) - any software changes must go through engineering change request - any changes must be documented 3. Nothing will be build (at least get credit for the work) without written (and agreed upon) requirements, acceptance tests and documented concepts (Hardware and Software). Core team tasks: - will do the weekly planning, - will consists of members of each participating institutes, - will have members with wide range of competence, - will invite experts to their weekly meeting. 4. All workpackage leader must learn how to operate the rf system and participate in the machine operation in some shifts 5. All personnel working on operationally relevant features must learn to operate the rf systems at FLASH. 6. We exclusively use following tools for planning and documentation: (Requisite Pro), Enterprise Architect, EDMS, MS Project and LLRF WIKI page. What is not documented here is considered not to exist at all. 7. Commitment of workpackage leaders from requirement to commissioning phase (2008-2014) 8. Acceptance tests take place at DESY 9. Individual workpackages leaders must work out concepts for Hardware, software, infrastructure and integration workpackage leaders 10. Problems with performance, resources, and schedule must be reported immediately when known. 11. Status and progress reports are due every 3 months (in writing) 12. The LLRF project management will decide on standards to be used by all collaboration partners based on suggestion by the leaders of relevant workpackages. 13. In case of disagreements in technical and organizational matters the project management will decide. Final authority for decisions is the project management. 14. Changes in the scope of requirements and deliverables must be formally approved by the change request board. 15. Necessary pre-requisite for a collaboration contract are that requirements, deliverables, acceptance tests and cost (incl. manpower) for each workpackage are approved by the project management. Only the top level requirements will appear in the collaboration contract. 16. No credit will be given for contributions that did not pass the acceptance test after contract is signed

13:00 Lunch break

6 Plan the work on developing the prerequisites (requirements, deliverables, acceptance tests, cost, etc. for individual workpackages) within the next 3-6 months

Speaker: ALL

Contribution View - LLRF Collaboration Meeting

Plan: 1. Form small teams (below) for each workpackage to define deliverables, schedule and cost 1.1 Derive requirements from high level requirements 1.2 Document in EA 1.3 Have requirements approved by Core Team 2. Verification of completness of workpackages and requirements 3. Tracking progress of requirements preparation 3.1 Monthly meetings on progress 3.2 Requirements review preparation meeting in Wilga, May 25th - June 1st (May 31st of meeting) 3.3 Organize final requirements review at MIXDES 19-21 of June 4. Finalize requirements document 5. Assign responsibility and teams to workpackages (by end of August 2008) Workpackage participants: 1.1 - K. Czuba, H. Weddig, students 1.2 - T. Jezynski, D. Makowski, W. Jalmuzna, students 1.3 - F. Ludwig, M. Felber, G. Moeller, (M. Hoffmann) 1.4

14:45 Coffee break

7 Define milestones etc. for the ATCA evaluation project (according to the recommendation of the LLRF review committee)

Speaker: ALL

Define milestones etc. for the ATCA evaluation project (according to the recommendation of the LLRF review committee)

ATCA Milestones

Hardware milestones

1. ATCA HUB - April 2008 2. ATCA CPU - in house 3. ATCA evaluation blade - in house 4. TAM900 - May 1st 2008 5. Carrier board - May 1st 2008 6. AMC Timing - May 1st 2008 7. AMC VM - May 1st 2008 8. AMC Main module - May 1st 2008 9. RTM DWC - May 1st 2008 10. RMT Signal Adapter - May 1st 2008 11. Installation of hardware in digital lab in June 2008 12. Installation of hardware in ACC 4/5/6 at FLASH in September 2008

Software milestones

1. AMC-MM and TAM900 plug to ATCA Blade * establish PCIe communication * read and send data to boards * DOOCS server on PowerQUICC 2. DOOCS server on ATCA-CPU 3. Communication links * PCIe - AMC<->Carrier * LLL - AMC<->Carrier 4. Aquire signals from RTM to TAM900 on the Carrier (signal integrity check) 5. Program AMC timing (trigger, clocks) + DOOCS server 6. Development of control applications on SIMCON boards

Demonstration milestones

1. Driving cavity simulator with LLRF-ATCA system in June 2008 2. FLASH functionality in LLRF-ATCA system in September 2008 3. Demostration of control of ACC 4/5/6 at FLASH in January 2009

8 Other business

Speaker: ALL

9 Summary of collaboration meeting and near future plans

Speaker: ALL

Verification of ISE Controller with beam 1. Shift on March, 19th (8h) - Verity that beam energy stability is better than 0.008% measured in the BC2 whil operating on crest - Demonstrate phase stability during off-crest (10 degrees) operation derivde from beam stability 2. May 20th - Demonstration of controller with DOOCS user interface and all functionalities of the present DSP system at FLASH - usage of LLRF hardware configuration as it is installed now in FLASH for user operation