1 / 14

User Requirement Document

User Requirement Document. DCS User requirements. General requirements Sub-detector requirements. General requirements : where we are. 2008 - Primary discussion : Oliver, Jonas, Valeri NA62_URD_Draft (attached)

decker
Download Presentation

User Requirement Document

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. User Requirement Document FV

  2. DCS User requirements General requirements Sub-detector requirements VF

  3. General requirements: where we are • 2008 - Primary discussion : Oliver, Jonas, Valeri NA62_URD_Draft (attached) • 2009 – “Initial Requirement Document”: Roberto, Piotr, Jonas, Oliver, Valeri https://edms.cern.ch/file/1038362/1.5/NA62_URD.pdf • Preliminary version of URD • Requirements of many sub-detectors are obsolete or missing • FSM model description is rudimentary and uncompleted • 2010 – FSM discussion: • “Proposal for implementation of the hierarchical controls”: Piotr, Jonas, Fernando • NA62FSM (attached) • NA62 FSM: Valeri • FSM.v.1.04 (attached) • New version of the URD is planned to be ready at the beginning of 2011 VF

  4. General requirements: some highlights The requirements include many standard items: Hierarchical controls with propagation of commands and state based on use of FSM (still under discussion) VF

  5. General requirements: some highlights - 2 • Readout • Synchronous and asynchronous modes • Possibility of dynamical definition of the acquisition frequency or the dead-band • Configuration database and tools • User interface • Access Control • Navigation • Homogeneity • User friendliness • Alarm handling and display • Trending • Condition database • Archiving and retrieval of data including logging of commands, events, alarms and actions • Interface to external systems VF

  6. General requirements: some highlights - 3 • System robustness : • System should monitor itself and report problems via alarms • System should be on UPS. If the power cut lasts longer than the autonomy of the UPS (at least ½ hour lifetime), the system will shutdown itself • In case of a power cut all important analogous measurements should be acquired and archived during the autonomy of the UPS • It would be desirable to be able to (re-)start the complete system with a single button press • If equipment becomes disconnected, this will be displayed to the user (and a alarm raised) • The PCs that the system runs on should be robust and allow for changing of disks and power supplies while running • The application shall be backed up. In addition to this backup mechanism, it should also be possible to rebuild the application quickly in case of failure • In reasonable circumstances, the control system shall never be down for longer than one hour during the run • It is planned to discuss the general requirements on future meetings VF

  7. General requirements: Detector Operation Modes • Detector operation mode (DOM) is a set of rules used by the DCS for the detector operation in specific conditions. The rules also determine the way how the DCS moves from one DOM to another and communicate with external systems. Typical DOMs are: • SHUTDOWN (FSM) • MAINTENANCE • RUN (FSM) • SAFE_MODE (FSM) VF

  8. Sub-detector requirements 2009 – “Questionnaire on requirements” - primary estimation of sub-detectors needs Today – Presentation of requirements for the SR January 2011 – Detailed specification document from each sub-detector participating in SR - on the EDMS (“a la TD”) June 2011 - Detailed specification document from each sub-detector for final system - on the EDMS The central team will provide some guidelines for the documentation preparation VF

  9. Sub-detector requirements – EDMS structure DCS URD General Requirements SR LAV Straw Tracker MUV IRC&SAC CHOD Final System CEDAR LAV … VF

  10. Spares VF

  11. User requirements -Detector Operation Modes • MAINTENANCE: • This is the main tuning and adjustment mode – “A la NA48”. • The detector is operated by means of expert panels • FSM is not used for central control MAINTENANCE VF

  12. User requirements -Detector Operation Modes Example of MAINTENANCE panel VF

  13. User requirements -Detector Operation Modes • STANDBY: • The detector is ready for data taking in stable conditions, the equipment is in state predefined in a configuration file, no actions are allowed anymore • The detector is operated by means of FSM • The DCS sends a signal to DAQ – “Ready for data taking” STANDBY Go to MAINTENANCE Go to STANDBY MAINTENANCE VF

  14. User requirements -Detector Operation Modes • RUN: • The detector is in stable conditions, no actions are allowed anymore • The detector is operated by means of the FSM • The transition to the RUN and back is triggered by DAQ RUN DAQ signal: Go to STANDBY DAQ signal: Go to RUN STANDBY Go to MAINTENANCE Go to STANDBY MAINTENANCE VF

More Related