1 / 32

Controls Global Group Tasks

Controls Global Group Tasks. John Carwardine Feb 8, 2006. Focus on three areas…. Develop a reference design and costing for RDR The high priority activity of GDE in 2006. Continue to develop the baseline design Pursue key R&D activities

gloria-mendoza
Download Presentation

Controls Global Group Tasks

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. Controls Global Group Tasks John Carwardine Feb 8, 2006

  2. Focus on three areas… • Develop a reference design and costing for RDR • The high priority activity of GDE in 2006. • Continue to develop the baseline design • Pursue key R&D activities • LLRF development at various test stands (TTF, ILCTA, etc) • RF phase / timing distribution • High Availability

  3. Continue to develop the baseline design and BCD

  4. Instrumentation & Control outline in BCD • 11.1 Controls Standard Architecture • 11.2 Timing System • 11.3 Diagnostic Interlock Layer • 11.4 Global Network • 11.5 Machine Protection • 11.6 Low level RF • 11.7 Feedback • 11.8 Integration with Instrumentation • 11.9 Machine Detector Interface • 11.10 Instrumentation – Beam position monitors • 11.11 Instrumentation – Beam profile monitors (transverse) • 11.12 Instrumentation – Longitudinal • 11.13 Instrumentation – other (intensity, loss, ring)

  5. Control system architecture in BCD…

  6. Issues arisen from BCD Comments • Comments received from Toge, Lockyer, Himel • Communicate to technical system and accelerator area leaders the implications of ATCA and Control System High Availability. • Change baseline design from VME/VXI to ATCA. • Address failure modes for the rf phase reference distribution system (phase jumps). • We need more diagrams to communicate what the control system will look like (being done…)

  7. Main tasks still to do (BCD) • To be addressed by BCD section authors… • Update other BCD sections in response to comments. • Expand LLRF and feedback sections. • Respond to comments from Himel, Toge, Lockyer (written) • New summary has been written. • Submit case for ATCA instead of VME/VXI. • Submit updated BCD to CCB before Bangalore. • To be addressed by the Controls Topic Groups… • Understand requirements from accelerator areas. • Continue to develop control system design details. • Apportion the RF performance requirements across the subsystems.

  8. Controls Topic Groups • CONTROLS INTEGRATION (overall integration) • Carwardine (ANL), Simrock (DESY), Michizono (KEK), Mcbride (FNAL) • CONTROL SYSTEM ARCHITECTURE • Saunders (ANL), Clausen (DESY), Rehlich (DESY), Votava (FNAL) Rechenmacher, Pavlicek (FNAL), Furukawa (KEK) • DATA ACQUISITION / CONTROL • Wendt (FNAL), Votava (FNAL) • HIGH AVAILABILITY • Larsen (SLAC), Downing (SLAC), Lenkszus (ANL), Saunders (ANL). • CONTROLS / INSTRUMENTATION INTEGRATION • Wendt (FNAL)

  9. Controls Topic Groups (2) • LLRF • Nageitsev (FNAL), Cancelo (FNAL), Carcagno(FNAL), Chase (FNAL), Simrock (DESY), Michizono (KEK), Lockyer (U.Penn) • TIMING AND RF PHASE REFERENCE DISTRIBUTION • Lenkszus (ANL), Frisch (SLAC), Pavlicek (FNAL), Matsumoto (KEK) • MACHINE PROTECTION SYSTEM • Ross (SLAC), Lenkszus (ANL) • BEAM-BASED FEEDBACK • Burrows (U. Oxford), Carwardine (ANL), Lebrun (FNAL), White (U. Oxford)

  10. Instrumentation Topic Groups • BEAM POSITION MONITORS: • Smith (SLAC), Wendt (FNAL), Baboi (DESY) • BEAM PROFILE MONITORS - LASERWIRE: • Blair (RHUL), Urakawa (KEK) • BEAM INTENSITY MONITORS, BEAM LOSS MONITORS: • TBA • BUNCH LENGTH MONITORS: • Ross (SLAC) • SPECIAL INSTRUMENTATION: • Ross (SLAC), KEK physicist

  11. Pursue key R&D activities

  12. LLRF development • FNAL, DESY, KEK already actively pursuing this with regard to test stands (ILCTA, TTF, ATF-2, etc) • [Feb 9-10th workshop] • Should determine how we can best integrate the test stands into other controls related development activities.

  13. Timing / RF phase reference distribution Various issues discussed at Jan 19-20 meeting, including… • Evaluate and demonstrate various options • Trench test of fiber system (vs coil in oven) • Sector test – the copper part (local distribution). • Two-channel receiver comparator scheme • Low-cost way of building a vcxo with sufficient performance? • “To chop or not to chop” • Different schemes to meet the bunch compressor requirements. • Failure modes and effects analysis. • Pursue HOM phase detector scheme.

  14. Feedback development issues Various issues discussed at Jan 19-20 meeting, including… • How do the beam-based feedback systems deal with exceptions? • Startup, beam loss, MPS trip, etc • Detecting and handing bad sensors or actuators. • Integrated simulation of LLRF and beam-based feedback. • Interplay between the various feedbacks and feed-forwards? • How does beam-based feedback help the rf specs? • How many intra-train feedbacks do we have, and how many pulses do they collectively take to converge? • Should beam trajectory feedback be several individual loops or a single global system?

  15. High Availability control system demo • R&D Roadmap (starting point) • Claude’s proposal • ATCA + EPICS iocCore + shelf manager + ICE middleware • Claude to set up discussion with interested parties. • Develop an AMC module to plug in / integrate with Claude’s ATCA crate. • How do we utilize the test stands (ILCTA, ATF, TTF)? Feb 9/10 Fermilab mtg

  16. Develop a reference design and costing for RDR

  17. RDR Design Matrix

  18. “Charges for RDR Leaders” memo of 1/12/06 [see Ray Larsen’s table]

  19. Guidance for costing exercise • High level guidance • Expected margin of error for control system costing is +/-30%. • Focus first on overall ILC cost drivers first. • DCB looking for resolution of a few x 0.1% (~$50M). • Priority should be on a top-down rather than bottom-up costing. • Use what has already been done for NLC, TTR, USLCTOS, etc • The RDR is not a detailed design document. • Need to include ‘everything’ • We need to know what to cost and how many…

  20. Baseline is a High Availability control system… • Front-end hardware • Switch from VME to ATCA in baseline for RDR. • Need to know what needs hardware redundancy at front-end. • Servers etc • Need to budget for HA relational databases, software, central computing, data archivers, etc • Central computing + archiving + data backups, etc is part of controls domain. MIS computing is not. • Control system • We will provide infrastructure for implementing HA functionality. • We have to make the middleware reliable (especially). • Cost will be in implementing the recovery policies. • To what level do we go with HA software in the various layers?

  21. Main tasks to do (RDR and costing) • Develop WBS structure for Controls and LLRF. • Collect baseline info from accelerator areas. • Develop Control System and LLRF block diagrams. • Generate Excel spreadsheet of line items for costing exercise. • Meet RDR deliverables, as listed in the “Charge to RDR Leaders” memo. • Prepare for LLRF and Controls reviews in April/May. • Issue: an apparent lack of availability of people to work on RDR.

  22. Immediate tasks • Continue to develop the integrated control system diagram. • Develop an RF/LLRF block diagram of each accelerator area (linac is the most important to do first) • How many I/O + DAQ channels. • How many relay racks. • Cable plant. • Develop a controls block diagram for each accelerator area • How many I/O + DAQ channels. • How many relay racks. • Show interfaces to LLRF, Instrumentation, Timing, MPS, etc • Cable plant.

  23. Control System WBS outline • Global Control System • <List of global systems> • <Control system line items> • <Accelerator Areas> • <Technical Systems> • <Control System line items> • RF System • <LLRF line items> • <Control System line items> • We need information from the area and technical leaders to complete the Controls WBS for the accelerator areas.

  24. Control System WBS (Global level) • Global level (starting point) • Central computing • Networking infrastructure • Timing system / RF phase reference. • Central MPS • Personnel Protection System • Control Room(s) • Data archiving • Control System Software development • Installation / commissioning • Aim to develop a structure with nodes that can be costed and that can be cloned as needed.

  25. Requirements gathering exercise • Plan: • Appoint two points of contact (POC) for each of the six accelerator areas: one for LLRF; one for the Control System. • Appoint one POC for each of the five global groups. • Goals: • Get a broad-brush understanding of the scope of the control system requirements to be able to cost the control system. • Create building-blocks for the RDR costing exercise. • Help establish treaty points. • Initial deliverables from each Point of Contact • Block diagram showing functions and basic geographic layout. • Estimate of number of I/O channels and data rates.

  26. Proposal for accelerator area POCs

  27. Integrated control system block diagrams • We should develop a hierarchy of block diagrams for the integrated control system • Integrated control system functional diagram (Ned’s diagram) • Block diagram of each global subsystem • Timing, MPS, archiving, central control system, etc, etc • Block diagram of each accelerator area control system • E-, E+, DR, RTML, Linac, BDS • Block diagram of each accelerator area LLRF system • E-, E+, DR, RTML, Linac, BDS • Beam-based feedback. • Hardware/geographic and software centric views. • Each block becomes a node on the WBS.

  28. “Ned’s Diagram” (2/1/06 revision) ICS Functional Diagram

  29. ICS Functional Diagram (detail)

  30. Cryo section block diagram

  31. Summary: RDR action items • Identify Points of Contact for accelerators and global groups • POCs develop LLRF and controls block diagrams for each accelerator area. • Develop the controls story for Bangalore. • Develop a costable WBS for Controls and LLRF. • Define costing procedures. • Prepare for first review in April/May timeframe.

  32. We need a pitch for Bangalore… • Strategy for completing the RDR task • Management, technical, etc • How we see things coming together. • What we need from the area, technical, and global groups. • R&D issues for controls and LLRF.

More Related