1. Team now comfortable with > 80k lines of inherited code Controller Ported to run on new 64 bit Proliant machine Re-engineered Orbit Trigger delivery (now uses CTR) New logging (std CO log viewers now usable) Updated/documented/re-factored configurations Bug fixes during readback of COD data, response matrix re- calculation, etc… Continuous build Service unit Ported to: 64-bits + FESA2->FESA3 + RDA2->RDA3 Running on new Proliant server Greatly improved system stability versus run 1 Bugs, buffer over-runs, better control of data-flow to/from controller, reduction of some data sizes, etc. Removal of some redundant functionality Reading BCTs, etc. Moved setting persistency from service unit to LSA snapshots Old OFC/OFSU machines now physically removed OP pleased with performance They are confident leaving OFB on during stable-beams LHC FB service unit LHC FB controller OP Client CO Client Client DB BI Client LHC CODs BPMs BBQs TECHNICAL NETWORK Orbit/Tune data streaming (UDP) Async. commands, settings and diagnostics (TCP) UDP-based RT I/O Up to 25Hz Private eth link LHC Feedbacks

2. LHC Feedbacks… Development of new testbed Joint collaboration with CO and OP Document systems using acceptance tests Reproduce operational problems & validate new features Proved that one of BI’s most complex systems can be tested – Hopefully inspire other future testbeds Preparation of Controller to accept DOROS data Activation postponed due to DOROS not being synchronous with orbit trigger Sister Dashboard project started, allowing us to trace BPM / Tune data quality ‘at the sourse’ User-friendly interface to assist in diagnosing problem sources Previous diagnostics used tcpdump and other cmd line utilities Simplifies problem resolution if data quality is an issue

3. Changes coming soon Concentrator also for BPM calibrations Introduction of settings auto-pilot (aiming for YETS) Setup Qref, Qgain, Quse-case, Qsrc, Oref, Optics as a function of time Generic class will handle all these cases Triggered manually over CMW, or via ARM & START MTG events Hoping to set up another co-operation with CO/OP to help with testbed Commission Controller with DOROS data Few more code changes Delicate configuration changes Regenerate bootstrap files from MAD-X Split of service unit into 2 FESA classes Settings & Proxy Limited impact to OP – Only YASP and Logging will need to change

4. Still on the table… Possible re-write of Controller in FESA May not be possible Long term discussion Removal of TInterlink mechanism between service unit and controller Loading of the optics via CMW rather than executing external Java process from service unit