Data Point Type fwAtlasGasProjMonitor

Context: MDT GAS System

Project(s): ATLMDTMON

Data Points: 1

Overview

The data point of type fwAtlasGasProjMonitor contains information on the overall state of the DCS monitoring of the gas system. It contains in particular information on the status of the various PVSS Control scripts, the 'Gas system alive' checking mechanism and the results of a set of integrity tests. ALARMS for this data point's elements should be followed up by the MDT DCS experts, rather than the gas experts.

Elements and Alarms

The following data point elements are set up with an alarm configuration:

#GCSAlive

AliveChecking.GCSAlive -- MDT GAS AliveFlag

The gas system PLC is equipped with a counter which is increased by 1 every few seconds. It is the principal means of checking that data on the gas system displayed in DCS is up-to-date. An ALARM indicates no updates of the alive counter for more than 120 seconds. Reasons for this can include

  • Gas control system PLC stuck
  • Gas control system superisory PC being down/ supervisory project not running/data publication via DIP not running
  • Import of gas data into Atlas DCS (DIP subscription in project ATLGCSIS2) not running
  • No connection between MDT gas DCS project and central system ATLGCSIS2
  • Data copy script not running

Actions in case of alarm: Note alarm and associated alarms in elog. Call MDT DCS expert staright away.

CopyScript.Running -- MDT GAS Data CopyMechanism

This data point indicates whether the PVSS control script responsible for copying gas system data to the MDT project is running (OK) or not (ALARM).

Actions in case of alarm: Call MDT DCS expert.

CopyScript.Error -- MDT GAS Data CopyMechanism Error

A TRUE value indicates that during intialization of the data copying control script a crucial error occured. The details can be checked by the DCS expert from the PVSS log file.

Actions in case of alarm: Call MDT DCS expert.

CopyScript.Warning -- MDT GAS Data CopyMechanism Warning

A TRUE value indicates that during intialization of the data copying control script a non-crucial error occured. The details can be checked by the DCS expert from the PVSS log file.

Actions in case of alarm: Note in elog for follow up by the DCS experts.

SumAlerts.DevicesUnknown -- MDT GAS SUMMARY Devices DataStatus

A TRUE value indicates that there is one or more gas system devices with bad data status. Most often, this is due to the gas system alive flag being FALSE, i.e. data from the gas system not being up-to-date.

Actions in case of alarm: Call DCS expert.

UserDefined.HvInterlock.Status.Running -- MDT GAS HvInterlock Mechanism

A FALSE value (ALARM) indicates that the PVSS control script providing interlock functionality to chambers' HV if the gas status is not ok is not running.

Actions in case of alarm: Call DCS expert.

UserDefined.HvInterlock.Status.NoConnection -- MDT GAS HvInterlock PS Connection

A TRUE value (ALARM) indicates that there is no connection between the gas monitoring PVSS project and (one of) the power system project(s) and thus that the HV Interlock feature is not operational.

Actions in case of alarm: Call DCS expert.

UserDefined.HvInterlock.Status.BadGasAlertConfigs -- MDT GAS HvInterlock Alert Configs

The HV Interlock mechanism relies on standardized PVSS alert configurations of the gas system data point elements. A value different from zero (ALARM) indicates that there are gas device data pouint elements with incorrect alert setup.

Actions in case of alarm: Note in elog and notofy DCS experts for follow up (by means of PVSS log file)

UserDefined.HvInterlock.Actions.ActionTaken -- MDT GAS HvInterlock Action

If TRUE indicates that the HV Interlock mechanism has acted (switched off) on at least one HV channel. Details can be found from the Expert panel accessible from the MDT FSM node. Note: The value of this data point element is reset to FALSE when acknowledging the alarm, which is meant primarily as a notification.

Actions in case of alarm: Determine the cause of the HV Interlock action. Follow up where needed. Document in elog. Afterwards clear the alarm by acknowledging it.

-- StephanieZimmermann - 06 Jan 2009

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2009-01-06 - StephanieZimmermann
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Atlas All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback