1. Project X RD&D Plan Controls Jim Patrick AAC Meeting February 3, 2009

2. Page 2 AAC, February 3, 2009 – J. Patrick Outline Description of the scope of the system Performance specification of the system Primary technical issues and the strategy to address them Goals of the plan by year Role of outside collaborators.

3. Page 3 AAC, February 3, 2009 – J. Patrick Control System Console Applications Java Applications Web Applications Database Central Services Web Servlets Open Access Front-Ends IRM Front-Ends MOOC Front-Ends Labview Front-Ends Field Hardware CAMAC, VME, PMC, PLCs, IP, CIA, GPIB, … Application ~200 Central Front-End ~500 ~100

4. Page 4 AAC, February 3, 2009 – J. Patrick Control System Scope Control System Infrastructure –Software frameworks – front-ends, services, applications –Core services – alarms, data acquisition, archiving, database, etc. –Network infrastructure – central and remote switches and cabling Timing System –Central timing generator –Signal distribution –Receiver modules for front-end hardware Machine Protection System –Input modules –Network –Central concentration –Not including detectors

5. Page 5 AAC, February 3, 2009 – J. Patrick System Scope Technical subsystems –Vacuum –LCW –Motion Control –Tunnel cryogenics –High level power supply control Application software –Technical subsystems –Utility applications –Machine applications Not included here: –Instrumentation controls –RF controls

6. Page 6 AAC, February 3, 2009 – J. Patrick System Requirements Pulsed machine – 5 Hz upgradeable to 15 Hz Potentially different characteristics and disposition of each pulse Pulse to pulse feedback for required stability Scale roughly comparable to the current complex: –~350K device properties –~500 front-ends –~100 central services –~200 consoles –Archive ~50K devices; ~10 GB/day

7. Page 7 AAC, February 3, 2009 – J. Patrick Technical Issues Large scale –Scale and complexity comparable to current facility High Availability Requirement Machine Protection Pre-existing MI/Recycler hardware including timing system Integration of externally provided subsystems

8. Page 8 AAC, February 3, 2009 – J. Patrick Technical Strategy Evolve current core system through the NO A era to Project X –Refurbish obsolete systems in MI/Recycler with Project X appropriate hardware (and software)  Large amount of CAMAC, fate t.b.d. –Modernize software frameworks –Support EPICS front-ends and display screens Develop new timing system for Project X linac –New protocol, merge events/data, interface to old system if needed Develop new machine protection system for linac Develop Project X specific software applications Test new technology at the HINS and NML facilities

9. Page 9 AAC, February 3, 2009 – J. Patrick Goals and Timeline 2009 –Global requirements –EPICS integration –Timing system specification –Develop plan for hardware platform R&D –Front-end framework upgrade design 2010 –Hardware platform R&D –Timing system design –Machine protection design –Application framework upgrade –Hardware platform R&D –Core infrastructure modernization

10. Page 10 AAC, February 3, 2009 – J. Patrick Goals and Timeline 2011 –Timing system prototypes –Machine protection prototypes –Standards for externally developed subsystems –Technical subsystem specification –Core infrastructure modernization 2012 –Final timing/machine protection prototypes –Specify machine applications –Technical subsystem prototyping –Core infrastructure modernization

11. Page 11 AAC, February 3, 2009 – J. Patrick Collaborators Collaboration on controls infrastructure –Initial contact with SLAC and Argonne –SLAC interest in evaluation of new hardware platforms (xTCA etc.)  Possibly develop RF interlocks for SLAC test-stand in xTCA –No definite plan at this time Externally provided subsystems –We expect to provide standards for interfacing to the control system  Software and hardware platforms –We expect to support inclusion of EPICS based subsystems  With standards for supported tools, conventions etc. –We will provide timing or other general purpose hardware if needed for remote subsystem development

12. Page 12 AAC, February 3, 2009 – J. Patrick Summary General strategy is to evolve the current control system through the NO A era prior to Project X linac operation –Refurbish hardware in MI/Recycler –Modernize software frameworks –Integrate EPICS Major Project X specific R&D goals: –Hardware platform –New timing system design –New machine protection system design –Technical subsystem design Role of collaborators not yet defined –Preliminary discussions with Argonne and SLAC