3rd June 2004JCOP CCB Meeting1 JCOP Activities and News JCOP FW PVSS Scaling Up DSS GCS Rack Monitoring, Control and Safety (RMCSS) Miscellaneous

3rd June 2004JCOP CCB Meeting2 Framework - I Regular releases (every two weeks) with bug fixes and minor enhancements Discussions with ETM regarding automated testing Main items of progress:  Upgrade of PS/SPS Data Server released  Trending upgrade released  Testing of Oracle archiving continuing Performance measurements and optimization continuing  Configuration DB Tool Feedback given to ETM on best way to insert into DB Awaiting feedback from experiments on it use Fellow is leaving and being replaced, so progress will slow down for a few months  Grouping of PVSS configs and minor mods following code review at ETM

3rd June 2004JCOP CCB Meeting3 Framework - II Outlook for the remainder of 2004  Consolidation, i.e. bug fixes and minor enhancements based on feedback  Documentation; introduction based on course material and on-line help built into FW  Assist the sub-detectors on use of FW  Full integration of mass configuration possibilities  Rack monitoring application (CMS development)  FSM and hierarchy upgrade (LHCb development)  ISEG (ALICE development - assuming working OPC server is provided)  Access control  DIP driver (API manager)  Integration of new CAEN hardware (EASY,..)  Improvement to configuration DB tool based on feedback  Inclusion of Oracle archiving when official release from ETM received (July 2004)

3rd June 2004JCOP CCB Meeting4 Framework - III Collect requirements for:  Alarm system  Data visualisation  Application for data exchange with external systems (LHC machine, C+V, Electricity, DSS, CSAM, Site Access Control, MCS, Primary Gas) To be done during the summer Individual interviews with CC and other interested parties

3rd June 2004JCOP CCB Meeting5 DSS - I Front End  All racks with the exception of ATLAS RSS racks have been delivered on schedule. ALTAS racks are foreseen to be delivered ahead of schedule (June)  First versions of the new Siemens PLC should be available in June  CMS have still to take a decision on RSS - it is our understanding that it is very probable that they will go ahead – number of channels not known  Due to the needs of LHCb a solution for the cables from cavern to surface based on optical-fibres was investigated. ATLAS will also adopt this, but ALICE not. No decision yet from CMS Back End  The BE has been modified based on the comments received from the experiments  Presentation made to DSS Advisory Board  Some points remain to be clarified

3rd June 2004JCOP CCB Meeting6 DSS - II Staff  Board held on 18 th May and candidate selected Overall System  DSS documentation and code has been placed in EDMS  Commissioning of the systems is foreseen for Autumn 2004 (assuming the experiments are ready)  Connections to power distribution and smoke detection need to be followed up further

3rd June 2004JCOP CCB Meeting7 GCS Status ALICE TPC GCS being tested by PH-TA1. Results:  Some modifications to Gas Hardware required  Control of the individual modules is generally OK. A few minor modifications identified which will be incorporated in the GCS FW  Waiting for feedback from PH/TA1 for the synchronization of the modules LHC GCS framework  Global architecture of FW has been defined and the integration of GCS objects types in objects generator will be completed shortly.  Integration of GCS PLC logic and meta-model started

3rd June 2004JCOP CCB Meeting8 GCS Activities and Milestones Collect feedback from ALICE GCS TPC User requirements to be completed  To be done for the non standard modules CO2 removal, CO2 envelop, Recovery.  To be completed for standard ones, i.e. for Gas Analysis module. Critical bug fixing on ALICE TPC GCS. LHC GCS framework  Development in three areas: DB, PLC, PVSS  Generation for Mixer module: 2004 Q3  Generation for Alice TPC: 2004 Q4  Generation for all options: 2005 Q2  Flexible generation: 2005 Q3

3rd June 2004JCOP CCB Meeting9 GCS Issues The DB work will be frozen (One staff leaving for maternity)  The first step will be done without automatic population of the DB from Meta data The PVSS part is slow down (Only one student)  The missing PVSS components will be developed end of 2004 if no extra manpower found Four mixers required ahead of schedule (Dec’04 -> Mar’05)  A priori not with LHC GCS but with LabView-based system from PH/TA1

3rd June 2004JCOP CCB Meeting10 Rack Monitoring, Control and Safety System - I Monitor board & associated circuits  Functionality agreed following PRR and now “signed-off” by LHC Technical Coordinators Procurement underway  ELMBs available  Coherent batches of components (for rad-tol) mostly available – tests on these will be performed in the GIF during June  10 prototype monitoring boards with PH/ESS  First batch of monitoring boards should be available in September Test equipment in development in PH/ESS  For production & in-situ tests Rack demonstrator (tbc)

3rd June 2004JCOP CCB Meeting11 Rack Monitoring, Control and Safety System - II First monitoring boards mounted in turbine units in November 2004 (~150) CAN branch/ELMB power supply  Status (tbc)

3rd June 2004JCOP CCB Meeting12 Rack Monitoring, Control and Safety System - III Rack monitoring application (being developed by CMS)  Basic functionality existing and demonstrated to FW WG  Awaiting completion of the rack demonstrator to test this component  Functionality/panels will be enhanced based on the experience with the demonstrator  Based on use of common Equipment Management Database (EMDB) Appears to be decided that ALICE will not use this (ALICE has its own Construction Database (CDB)) Discussion required to understand how the EMDB/CDB will be used and whether a common interface (abstract) can be implemented  Interface between TS/EL PLC and rack monitoring application being designed Rack monitoring application will be common for both TS/EL power distribution options

3rd June 2004JCOP CCB Meeting13 Scaling Up PVSS - I Reports containing the results can be found: Tests 31+32: Performance tests with a realistic distributed system, tree structure of machines.  No bad surprises.  Learned about and demonstrated PVSS’ inbuilt overload protection mechanisms.  Not unsurprisingly Linux performs better than Windows.  Any dual CPU capability is exploited well during alert processing.

3rd June 2004JCOP CCB Meeting14 Scaling Up PVSS - II Test 34: Simulation of Control Room machine displaying trends from all other systems. Works well. 48 different trends displayed on Control room machine. Test 35: Control Room machine viewing alerts from many leaf node machines.  It’s easy to overload the Control Room machine if all the leaves are generating alerts as fast as they can!  The basic PVSS protection mechanisms were seen to kick-in: Screen update pauses (with an explanatory message) until the avalanche settles down. Connection is severed to machines whose traffic is so high it threatens to compromise the whole system.

3rd June 2004JCOP CCB Meeting15 Scaling Up PVSS - III Remaining work for ‘showstopper’ tests:  Essentially to complete the current tests and to test the behaviour when breaking and re-establishing connections between managers and systems Indications from previous test are already positive  Barring any problems that appear, all “showstopper” tests should be completed by end June.  Regular feedback suggests further interesting tests during the summer. Optimisation tests  Tests to be performed to understand how best to distribute PVSS managers and to configure the systems to obtain optimised performance Added benefits of this work:  Performing the tests with alpha, pre-beta, beta and candidate releases of PVSS version 3.0 allowed numerous bugs to be identified early and hence fixed in the official release. However, this did slow down the tests.

3rd June 2004JCOP CCB Meeting16 Scaling Up Other scaling issues (Calin Alexa)  FSM/PVSS combination First example looked at is to model CAEN crates, boards and channels as FSM Can the PVSS/FSM integration support such an approach, i.e. in terms of performance, memory, etc.?  Hardware readout Look at the readout of CAEN via OPC to answer questions such as: –Where are the bottlenecks? –How many crates can one reasonably support with one OPC server? Will use multiple CEAN crates

3rd June 2004JCOP CCB Meeting17 Miscellaneous Cooling and ventilation (discussion held with TS/CV)  CMS and LHCb systems to be outsourced  ALICE and ATLAS systems to be built in-house  Meeting will be held to verify agreements of 11/2002  Presentation of status at next CCB (16/9/2004) LDIWG  PVSS driver (API manager) in development Scheduled to be finished end of June  TS/CSE and AB/CO have begun testing  New requests from experiments, e.g. for archiving of DIP data (primarily LHC data), being discussed  Experiments have requested to join the testing as soon as possible Siemens S7 driver being developed by ETM Meeting with ETM planned for September