1. Controls & Monitoring Schedule J. Leaver 02/11/2009

2. 13/07/2015Imperial College 2 Schedule

3. 13/07/2015Imperial College 3 Not officially allocated (rough estimate) Schedule

4. 13/07/2015Imperial College 4 Key Issues Run period ‘conflicts’ –Control system is in regular use – have to schedule significant updates around run periods –Necessary to delay several maintenance tasks until next year Network specification –Cannot complete “Enable remote access” infrastructure task until MICE network configuration is complete – no clear indication of when this will occur Target Controller / DAQ –Very much dependent on Target group’s work – difficult to schedule as a standalone Controls & Monitoring task

5. 13/07/2015Imperial College 5 Key Issues Manpower –‘Controls & Monitoring’ is a very broad subject –Controls effort is ‘significantly understaffed’ (DAQ & Controls Review, June ‘09) –Many unexpected additional requirements & few resources to buffer the load of any additional work At least 30% of total controls effort during past 6 months spent on unscheduled jobs (often piecemeal user requests, or unpredicted/unpredictable infrastructure tasks) A delay on one project can affect many other (potentially unrelated) projects –We are working as fast as we can…