Detector controls user requirements
This presentation is the property of its rightful owner.
Sponsored Links
1 / 20

Detector Controls User Requirements PowerPoint PPT Presentation


  • 41 Views
  • Uploaded on
  • Presentation posted in: General

Detector Controls User Requirements. Introduction. Requirements; Why?. Aim of DCS requirements Estimate the size of the project Spot common issues across detectors Investigate common solutions to common problems Avoid duplication of work More efficient maintenance

Download Presentation

Detector Controls User Requirements

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Detector controls user requirements

Detector Controls User Requirements


Introduction

Introduction

Requirements; Why?

  • Aim of DCS requirements

    • Estimate the size of the project

    • Spot common issues across detectors

      • Investigate common solutions to common problems

        • Avoid duplication of work

        • More efficient maintenance

    • Propose solutions for individual detector needs

      • Use of standards (hardware and software)

      • Preserve a coherent DCS

DCS meeting, ALICE week Delhi


Requirements

Requirements

Requirements; What?

  • Requirements should cover

    • All sub systems

      • HV, LV, Cooling, Calibration, Alignment, …

      • Gas, FEE, …

    • Numbers

    • Type of equipment

    • Boundary conditions and limitations

      • How to read sensors

      • Location of equipment (cable lengths)

DCS meeting, ALICE week Delhi


Requirements1

Requirements

Requirements; What?

  • Requirements also should cover

    • Functional Requirements

      • What should the control system do

      • Interaction with other (sub-)systems

      • Safety aspects

      • Typical operation

    • Planning

DCS meeting, ALICE week Delhi


Requirements2

Requirements

Requirements; How?

  • Collecting requirements

    • Existing documents (TDR, …)

    • DCS meetings (Workshops)

    • Questionnaires

    • Private discussions with detectors

      • The most efficient way to get precise detailed information 

      • But, tedious and time consuming 

DCS meeting, ALICE week Delhi


Requirements3

Requirements

Requirements; When?

  • Where are we currently

    • Collected information from TDRs

    • Precious input during May and September DCS workshops at CERN

    • Some information has come from the questionnaire

    • Discussions started with a few detectors

      • To establish contact

      • To gain experience

      • In view of prototyping

DCS meeting, ALICE week Delhi


Requirements4

Requirements

Requirements; When?

  • Where are we currently

    • Concentrating on the more technical aspects

      • As a side effect we collect information on expertise / tests / prototyping in the detectors

DCS meeting, ALICE week Delhi


Requirements5

Requirements

Requirements; Next?

  • What will be next

    • Create a “database”

      • Hold the more “technical requirements”

    • Produce a document that also covers “functional requirements”

      • One URD per detector

    • By no means frozen

      • the requirements should follow the developments of detectors and technology

DCS meeting, ALICE week Delhi


Requirements overview

Requirements, overview

  • Several sub-systems reoccur for almost all detectors:

    • High Voltage

      • 1 to >1000 channels; 50V to 100kV

      • Two main manufacturers, but no real commitment

    • Low Voltage

      • Unclear, several options under investigation (e.g. DC-DC)

    • Cooling

      • Lot of work going on, but the control aspects should be addressed now as well

DCS meeting, ALICE week Delhi


Requirements overview1

Requirements, overview

  • Other areas that are more detector specific:

    (But where common solutions should be envisaged whenever possible).

    • Temperature monitoring

    • Equipment (in widest sense) status monitoring

    • Control of calibration and alignment equipment

    • Interaction with the FEE

    • Specific fluid systems

DCS meeting, ALICE week Delhi


Requirements overview2

Requirements, overview

  • Not mentioned so far:

    • Gas systems

      • Gas Working Group, contacts are established

    • Control of equipment in the racks (and the racks themselves)

      • Common effort ongoing

    • Safety

      • Common effort ongoing

DCS meeting, ALICE week Delhi


Detector controls user requirements

Sub-Systemsper detector

Compiled by

Lennart Jirdén

DCS meeting, ALICE week Delhi


Requirements details

Requirements, details

  • Reaction on questionnaire from:

    • ITS-SPD, ITS-SDD, ITS-SSD, TPC, TRD, TOF and HMPID

  • Overview for HV and LV

    • Need to be digested

DCS meeting, ALICE week Delhi


Requirements details1

Detector

Q

PS

#ch

V

Loc.

SPD

Y

CAEN

120

70

PX/UX

SDD

Y

CAEN

520

40/2400

SSD

Y

CAEN

144

100

UX

TPC

Y

ISEG

160

2000

PX

TRD

Y

ISEG

1080

2500

UX

TOF

Y

100

6000

HMPID

Y

CAEN

50-70

2200

UX

PHOS

30

50/500/3000

FMD

PMD

ZDC

50

Castor

120

1600

Muon

112

Requirements, details

High Voltage

Systems

DCS meeting, ALICE week Delhi


Requirements details2

Detector

Q

PS

#ch

SPD

Y

CAEN or DC-DC

3*120

SDD

Y

Arem

216

SSD

Y

CAEN

450

TPC

Y

Wiener

3*36

TRD

Y

Maybe DC-DC

108

TOF

Y

120

HMPID

Y

CAEN or Wiener

210 or 150

PHOS

55

FMD

PMD

ZDC

Castor

Muon

Requirements, details

Low Voltage

Systems

DCS meeting, ALICE week Delhi


Requirements plans

Requirements, plans

  • Producing a first version of the channel database

    • Based on information mentioned before

    • Exact format still to be decided

  • Collect functional requirements

    • Template of requirements document

    • Discussions with detector controls experts

  • Input to prototyping activities

DCS meeting, ALICE week Delhi


Requirements document

Requirements document

  • A template URD is available

    • A first version

    • Headings and guidelines to fill it

    • Example of a few sub-systems will be available

  • A working document

    • Will evolve to follow the developments of detectors and technology

    • Unknown aspects will be filled later (but are listed)

DCS meeting, ALICE week Delhi


Requirements document1

Requirements document

  • Introduction

  • Detector description

  • Description of Control System

    • Identify sub-systems

    • Requirements for each sub-system

      • Functionality, Detailed description of devices or equipment to be controlled

      • Detailed description of each parameter with its attributes

      • Interlocks and safety

      • Operation and supervision

    • Requirements of the Controls system as a whole

  • Timescales and Planning

DCS meeting, ALICE week Delhi


Requirements document2

Requirements document

  • Positive experience

    • Trigger people to start thinking about controls aspects

    • Reveal issues you hadn’t thought of

  • Many iterations

    • Detectors come with first version

    • Comments/questions/suggestions from the controls team

DCS meeting, ALICE week Delhi


Conclusions

Conclusions

  • Collecting and defining requirements is tedious and time consuming; but it is an investment that is worth it!

    • Part of design; it forces you to think about the (sub-)systems

    • Easier implementation, more support, easier maintenance

  • We are starting, but your collaboration is and will remain essential

  • DCS meeting, ALICE week Delhi


  • Login