Review of the LEIR Controls situation

1. Review of the LEIR Controls situation Marine Pace - Vito Baggiolini M.Pace –TC -20 October 2005

2. Where Do We Stand ? Behind us • 1st beam injected on 7 July …. on schedule w.r.t. planning • 1st beam circulating on 11 October ….on schedule w.r.t. planning Facing us • Capture + Acceleration : end October 2005 onwards • Cooling : end October 2005 onwards • Extraction towards PS : February 2006 onwards At first sight LEIR controls look fine … but • CO problems often hidden behind installation delays • OP experience with new controls is not satisfactory M.Pace –TC -20 October 2005

3. Motivations for Review • Significant reduction in support + follow-up over the last months • Steen: departure from CERN • Marine: temporary re-affectation to LHC HWC SCT => Short term strategy discussed yesterday • Technical pending issues • Emerged with the restart of the ring commissioning in Sep • Slow down the progress of beam commissioning => Will be presented now M.Pace –TC -20 October 2005

4. Remarkable Features LEIR at the cross roads between new and legacy controls Front end HW • Mix of legacy PSlike modules & new modules Timing & Sequencing • CBCM with extensions for stand alone mode Front end SW • New modules are FESA; legacy modules are GM Application SW • New Java Generic AP (replicate of X/Motif AP) • LSA AP customized for LEIR • A couple of X/Motif AP • New Java Console Manager Analogue Signals • New OASIS Alarms • New LASER M.Pace –TC -20 October 2005

5. Technical Issues Data persistency for FESA devices - Priority 1 • Loss of last value for control settings at DSC reboot • All control settings set back to 0 • Problem occurs when the DSC is rebooting while the task is saving HW settings to file • CO Unit responsible for solution = FESA team M.Pace –TC -20 October 2005

6. Technical Issues Immediate update for Control values - Priority 1 • After Set() to a control property, a device should immediately send an update with a special tag to clients • Technical solution discussed on Sep 15, not yet deployed in FEs • CO Unit responsible for solution = FESA team “Bad Cycle Stamp” – Priority 1 • Control properties in FESA can be subscribed only on-change • Applications need update for all properties once-per-cycle • GM provides once-per-cycle, FESA provides on-change • This mismatch causes “Bad Cycle Stamp” in GUI • CO Unit responsible for solution = FESA team M.Pace –TC -20 October 2005

7. Technical Issues References - Priority 2 • Available last week • Some missing functionalities (No automatic refresh in GUI, No reference available on inactive USERs) • CO Unit responsible for solution = LEIR AP team Archives – Priority 4 • Archives are standard LSA functionality • Archives are available for Functions only, not for Scalars • LSA Settings Management is being adapted to handle Scalars • CO Unit responsible for solution = LSA team • OP Request: access LSA archives from Working Sets/Knobs • CO Unit responsible for solution = LEIR AP team M.Pace –TC -20 October 2005

8. Technical Issues PPM Copy – Priority 2 • Copy of control settings from USER PlsLine1 => USER Plsline2 • Combined with references, PPMCopy provides an archive facility • Multiple sets of reference settings • OP request: • Replicate of existing facility in X/Motif Working Sets • Facility available for any device from Working Sets • Facility today available for GM, not available for FESA • CO Unit responsible for solution = FESA or AP team M.Pace –TC -20 October 2005

9. Technical Issues OASIS – Priority 3 • Slowness of GLOBAL connections • GLOBAL are barely usable • Loss of synchronization • No data updated any more • Gives the impression that the whole application is stuck and stopped responding • CO Unit responsible for solution = OASIS team M.Pace –TC -20 October 2005

10. Technical Issues On line device monitoring – Priority 4 • OP request: • Replacement of previous EqpSurvey not anymore maintained by OP • Display of the evolution versus time of a device property • Expected functionality falls in between 3 products • Fixed Displays (but static configuration is not suitable) • Logging in SDDS files (but data correlation is missing) • Logging in Measurement DB (but plot’s refresh is not suitable) • SDDS Logging submitted to OP for test => does not fulfill URs • Most suitable solution is Logging data to Measurement DB • Provided additional features are implemented for data extraction • CO Unit responsible for solution = Logging + Measurement Service team M.Pace –TC -20 October 2005

11. Technical Issues LASER – Priority 5 • Some expected functionalities are missing • With respect to the existing PS Alarms application • Surveillance of and remote commands on front end machines (1) • Remote commands on specific devices (2) • Ex. Re-initialization sequence of power converters • Alternative solution acceptable by OP • Functionality (1) : use xcluc • Functionality (2) : extend xcluc or implement global actions in Working Set • Replicate existing X/Motif facility + extend to FESA devices • Actions are device class specific + perform in one go on all selected devices • Ex. Set ENABLED on all selected POWDF7000 converters • CO Unit responsible for solution = XCLUC team + ? M.Pace –TC -20 October 2005

12. Improvements beyond LEIR • Incoherent behavior across all device types • FESA and GM devices behave differently • From application viewpoint, all devices should behave the same • We (JAPC, CMW, FESA, GM) have to • Specify the exact device access protocol above CMW • Agree who implements what to achieve a coherent behavior • Requirements formulated in March 2005 following TC (Dec 2004) M.Pace –TC -20 October 2005