Work Plan for DCS project L.Jirden 10.9.01

1. Work Plan for DCS projectL.Jirden 10.9.01 • Initial steps • Strategy • Project phases and system components • Example of a design phase • Planning • Conclusion DCS Workshop - L.Jirdén

2. DCS Work Plan • What is a Work Plan? • It defines the ultimate goal and all the intermediate steps to be performed, when and by whom to achieve the goal. • Ultimate goal: A working DCS ready for exploitation end 2005 ! DCS Workshop - L.Jirdén

3. Initial Steps • Agree on project definition • Establish resources, create ACC team • Establish ACB • Define organization of work • Identify applications for prototyping • Define milestones and detailed planning • Start regular progress meetings DCS Workshop - L.Jirdén

4. Initial Steps • Agree on project definition • Accepted by TB end may • Establish resources, create ACC team • Lennart Jirden • Andre Augustinus • Tarek Ben Ahmed 50% • Sorina Popescu (PJAS) • Physicist/engineer vacancy • Establish ALICE controls board • DCS detector contact people nominated DCS Workshop - L.Jirdén

5. Initial steps Cont. • Define organization of work • We need to set up a “Work Plan” • Start at this meeting • Identify applications for prototyping • Start at this meeting (Andres presentation) • Define milestones and detailed planning • Start at this meeting • Start regular progress meetings • Start later DCS Workshop - L.Jirdén

6. Global Layout PrimaryServices Associated Projects Supervisory Function magnet LHC ECS gas Offline electricity Trigger cooling DCS safety DAQ access ITS TPC MUON pixel strip drift T T p hv hv hv hv hv lv lv lv lv lv Detectors DCS Workshop - L.Jirdén

7. Strategy • A. Process control for the detectors • Identify common requirements • Design “ALICE common solutions” • Pilot applications - test cases • Collaboration ACC – detector groups • Aim to cover all main functions – minimize number of special cases • B. Services • Determine required functions and responsibilities • Pilot applications – test cases • Collaboration ACC – detector groups – CERN services DCS Workshop - L.Jirdén

8. Strategy • C. Operations and supervisory functions • Link detector process control to supervisory layer • Implement vertical slice & use PVSS framework tools • Pilot applications – test cases • Collaboration ACC – detector group – JCOP • D. Links to ALICE DAQ, TRG, offline • Initiate common projects • Pilot applications – test cases • Collaboration ACC – DAQ, TRG, offline – detector group DCS Workshop - L.Jirdén

9. Strategy • E. Links to LHC • Experiment common project (JCOP) • F. Controls Infrastructure • Define requirements • Collaboration ACC – DAQ – Infrastructure group DCS Workshop - L.Jirdén

10. Organization Of Work • Typical project phases • Design • Production/purchasing • Installation • Commissioning • Operation DCS Workshop - L.Jirdén

11. Organization of work Cont. • Controls System main components • Detector sub systems. • HV, LV, cooling, gas, FE electronics, alignment, misc. • Links to Primary Services. • Magnet, primary gas, primary electricity, primary cooling, safety, access. • Links to associated systems. • DAQ, TRG, offline, LHC. • Operations and supervisory functions. • Configuration, logging, archiving, alarms, etc. • Controls infrastructure • XCR, networks, servers, rack space, etc. DCS Workshop - L.Jirdén

12. Organization Of Work • Typical project phases • Design • Production/purchasing • Installation • Commissioning • Operation • DCS Components • Detector sub systems • Links to Primary Services. • Links to associated systems. • Operations and supervisory functions. • Controls infrastructure DCS Workshop - L.Jirdén

13. Design Sub System controls • First • Fix the device to be controlled • Then • Design the controls part DCS Workshop - L.Jirdén

14. Design Sub System controls • Fix the device to be controlled • Question: Common Specification and purchase? • For which devices? • Functional specification and tender or single source purchasing? • Purchase of test units • Evaluation and test • Device fixed or device control fixed DCS Workshop - L.Jirdén

15. Design Sub System controls • Design of controls part • User requirements document • How detailed? TPC field cage example – template. • Boundary conditions • CERN standards – YES! • Which ALICE standards? • PLC’s, field bus, sensors, gas w.g. standards, etc. • common purchasing? • To be defined first! • Process Control layout projected • Prototype and test • Link to supervisory layer – integrate with framework • Prototype and test DCS Workshop - L.Jirdén

16. When and by Whom? • When? DCS planning! • DCS planning file created • Linked to ALICE wide planning • Input from each detector group required • Steps • Dates • By whom? Responsibilities! • Pilot projects shared ACC – detector group • Otherwise detector groups DCS Workshop - L.Jirdén

17. DCS Planning 2001 02 03 04 05 06 DESIGN PROD. PURCH. INST. COMM. BEAM OPERAT. DCS Workshop - L.Jirdén

18. DCS Planning 2001 02 03 04 05 06 DESIGN PROD. PURCH. INST. COMM. BEAM OPERAT. SOLUTION PROJECTED SUPERVISORY LAYER PROTOTYPE & TEST USER REQ. DOC. DCS Workshop - L.Jirdén

19. Conclusion • DCS project launched – some initial steps now effective • Work plan to be set up – aim for end 2001 • Basic strategy defined • Basic Components and project phases outlined – more details needed! • DCS Planning file created – more details needed! • Input from Detector Groups required! DCS Workshop - L.Jirdén