1. AB-CO Exploitation 2006 & Beyond Presented at AB/CO Review 20Sept05 C.H.Sicard (based on the work of Exploitation WG)

2. Status in March 2006  New Control Center  Restart PS (Early for LEIR) & SPS after 1 full year stop  Major SPS Timing change  New control HW (Timing modules, VME controllers,…), but also ageing components (Camac)  Mix of new (FESA, Java apps) and previous controls technologies  Growing obsolescence of Exploitation tools  Too many gray responsibility areas (CO,OP,Eq-Groups)  Multiple console managers & OS  All with LHC HW Commissioning in parallel

3. Scenario for 2006  Must start 2006 with previous organisation: CO piquet for PS complex (when possible) experts on-call for SPS =>Limited Objectives But Reinforce CO Exploitation with: a dedicated Exploitation Manager, covering all machines, with mandate to: a dedicated Exploitation Manager, covering all machines, with mandate to:  Identify and agree with partners on responsibility limits (reduce ‘gray’ areas)  Drive towards Homogenization through the different domains: FE OS, HW, Applic.layers…  Add support structure for Industrial Controls (at first, for LHC Hardware commissioning)  Push for diagnostic tools usable by Operators

4. Later Scenarios: Piquet or On-Call? OP must share a common view!! Piquet + guaranteed availability + single entry point + solves directly all common CO pbs + Enforce homogeneous diagnostic tools - may need to call expert if complex pb - (?) need proper central info - probably no single piquet for all accelerators On-Call - may need to call several numbers to get answer - OP must first diagnose the right domain + more in-depth knowledge => faster repair + (?)No need for Eq.Grp to provide central info or diagnostics + One Call list may cover all machines & domains

5. Converging PS/SL methods Following actions will unify tool & information interface:  FE Startup sequence ‘a la SL’, (from DB as in PS) – (effective now)  Console Manager & generic controls (knobs,..)  Alarms (LASER) – but lacks PS facilities…  FESA progressively replacing GM(PS) or SL-Equip (but need info on device/physical address relation)  Other possible actions (to be discussed): source code directory for operational sw in front-ends Reduce file system dependencies (in view of CNIC..)

6. Centralising Exploitation Information Based on naming standards & DBs:  Layout DB Two layers of description System (PLC, VME, GATEWAY, FIP segment, Server,..) Functional Component (slot) of system (board, Supply, CPU,…) Connection to functional slots (timing, Power, Ethernet..)  ABCAM Asset management tool describing all physical control equipment associated to a functional slot - but just starting to contain relevant data… - mostly LHC -

7. Other Actions  Clarify responsibilities with equipments in all grey areas.  Enforce procedures for reception & change tracking  Identify & execute urgent legacy software upgrade Old LynxOS versions, OS9… HP / Windows servers Important Orphan applications  Integrate all existing diagnostic tools LASER (AP), GTPM (OP), XCLUC (IN), Spectrum (IT -CS), TIM (OP), PVSS UNICOS integrated diagnostics (IS/IN), Application integrated diagnostics (AP),DiagCMW (FC), TIMING Tools (HT), PLC consoles Tools (IS), FIP diagnostic Tool (IS), Logging monitoring (DM)…

8. CO Operation Responsibilities AP Java Applications framework High level applications for : -LEIR -LHC HC LASER HT Timing /Sequencing Remote reset FE FC CMW FE IN Servers FE (via xcluc) PIC/WIC IS PVSS IEPLC CRYO FIP Test bench DM Logging Configuration DB ABCAM LAYOUT DB All CO sections will have activities related to Exploitation in 2006

9. Present piquet Know How AP Java Applications framework Legacy Application High level application : -LEIR -LHC HC LASER HT Timing /Sequencing Remote reset FE FC CMW FE IN Servers FE (via xcluc) PIC/WIC IS PVSS IEPLC CRYO FIP Test bench DM Logging Configuration DB ABCAM LAYOUT DB

10. Sharing Responsibilities inside CO  The Exploitation Responsible in charge of: Interface toward OP (ABOP,…) and Eq.Groups (responsibility limits) Coordination of control system integration Requesting procedure/documentation to system teams Coordinating the diagnostic tools development Requesting from the different teams the functionalities necessary to operation.  CO sections organize (alone, in synergy with other,…) the operation support of the systems they deploy. Not systematic organization (PIQUET OR LIST) Intervention teams can be grouped i.e. : hardware for VME, gateway, FIP, PLC PVSS/PLC & PVSS/FEC applications support  Create a Real Operation Oriented policy within the entire CO group =>All this implies sufficient resources devoted to this task….