1. EMCal DCS and related Issues with Shutdown/Installation B. S. Nilsen M. Cherney J. Fujita

2. Interruptions Dec.7-> Feb. 4: No access to Controls System from Outside, Except for approved personnel. – E-mail me with names who need access. I can always add people later. Jan. 12->21 Point 2 shutdown for major cooling intervention. No power to racks, ACR’s,… DAQ upgrade to SL5 not scheduled yet (no testing). – Need to test all Shuttle programs (calibration…) – New DAQ hardware will be 64 bit machines. – DCS remaining on SL4, XP, 2003. Only new machines will be 64 bit. Central DCS plan Hardware/Software upgrades. – All XP system must upgrade to SP3. – PVSS and JCOP patched introduced as needed. – Direct RDB queries to be implemented, 5 min/system 11/11/102 EMCal Weekly meeting Thursday November 11, 17:30 cern

3. Hardware Items Request to send in all ISEG create for modifications – Add externally controllable slow ramp-down of HV. – Can be used in case of loss of communications with control system. – Can be wired into EMCAL’s “Emergency Stop” button. Sets EMCAL into “Supper-Safe” mode. A new round of cable installation is planned. Do we have any new cable to be installed? Ethernet outlets are in low supply do we need more? Now is the time to request any Rack modifications.. 11/11/103 EMCal Weekly meeting Thursday November 11, 17:30 cern

4. Points to Consider Implementation of a new ALICE State, “Run Pause” – If a detector has a problem, in stead of Stopping and starting a run, that detector can request a “Run Pause”. All other detectors stay in usual state ready to pick up the run. – Might the EMCAL want to do so? – What might the EMCAL want to do if some one else request a “Run pause”? – This might/will have an effect on Shuttle programs which will need to exclude this paused time period during its calibrations (especially if they were the cause of the pause). – Any Other issues/requests??? Large power perturbations have been seen by ALICE. – What do we know about EMCAL’s behavior during these times? – Do we have system working to handle such problems? – Especially during installation phase, can we handle unexpected interruptions “any were”? – We may want to set up tests of some or all of our interlocks and monitoring system. 11/11/104 EMCal Weekly meeting Thursday November 11, 17:30 cern

5. DCS plans/changes Implement new EMCAL hardware Remove some Data-Points queried from other systems, others to get “centralized”. Fully Backup our system. Write Restore instruction and provide information about any private/special code needed. Implement RDB monitoring (add one data point). Implement Alert/Alarm help for Central DCS and EMCAL DCS system. Administrator Access to DCS machines. – Recently, Federico had to reboot the DCS machines. – Clearly all On-call’s need this privilege. – It can easily be granted on request, or do find some other solution? 11/11/105 EMCal Weekly meeting Thursday November 11, 17:30 cern

6. Background Changes We will no longer use PVSS. Now it is called “Simatic WinCC”. New DCS data base to be installed. DB table size to be significantly reduced in size. A review of the ALICE Safety Matrix. – EMCAL always “SAFE” and “Supper Safe”. 11/11/106 EMCal Weekly meeting Thursday November 11, 17:30 cern

7. The End 11/11/107 EMCal Weekly meeting Thursday November 11, 17:30 cern