Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA Pipeline Operations for Liquids

Configure the Inhibits tab of the Plmvoldevice record

Configure the Inhibits tab of the Plmvoldevice record

  • Last UpdatedApr 24, 2025
  • 4 minute read

Each input can be inhibited individually by selecting a checkbox on the plmvoldevice record. This feature is available to both the Controller and Administrator.

Each input can also be configured to inhibit automatically based on the state of a status, multistate, or Advanced Logic Processor (ALP) record.

During the inhibit period, zero volume change is assigned to each recorded minute. The Pipeline Monitor (plm) record continues to exhibit a Fresh state and continues to calculate.

When the inhibit condition is cleared, the volume change that happened to the device during the inhibit interval is ignored, and the minutes during this interval remain set at 0. The first recorded minute after the re-enable shows only the volume change for that minute.

For information on how to set up an ALP, see Advanced Logic Processor (ALP).

To configure the Inhibits tab of the plmvoldevice record

  1. From the Advanced Database Editor (ADE), do one of the following:

    • Navigate to the plmvoldevice record, and double-click the plmvoldevice record you wish to configure.

    • Select Functions > Create New Volume Device to create a plmvoldevice record for a plm record. For more information on creating a new plmvoldevice record, see Create a new Plmvoldevice for the PLM record.

      The plmvoldevice Row Edit appears.

  2. Select the Inhibits tab.

    The Inhibits tab appears.

    Embedded Image (65% Scaling) (LIVE)

  3. To inhibit the device and ensure that it will not contribute to calculations, select the Inhibit checkbox.

  4. To enable the use of the status, multistate, or Advanced Logic Processor (ALP) point configured in the Inhibit Path field, select the Enable auto inhibit checkbox.

    Note: The Enable auto inhibit checkbox must be selected to enable the Inhibit Path, Inhibit states, and Enable states fields.

  5. In the Inhibit Path field, enter (or click [...] to select) a path to either the status, multistate, or alpconfig record to which the application sends the command.

  6. In the Inhibit states field, enter a value belonging to the message set of the record specified in the Input Path. To include multiple values, separate values with commas. When the configured Input Path is in any of these states the plmvoldevice record will become inhibited. If the configured Input Path is a status or multistate, the allowable states can be found in the point’s input base message set. If the configured Input Path is an ALP record then the allowable states are yes or no.

  7. In the Enable states field, enter a state value belonging to the message set of the record specified in the Input Path. To include multiple values, separate values with commas. When the configured Input Path is in any of these states the plmvoldevice will become enabled. If the configured Input Path is a status or multistate, the allowable states can be found in the point’s input base message set. If the configured Input Path is an ALP record then the allowable states are yes or no.

    Note: As soon as you configure either an Inhibit Path, Inhibit states, or Enable states fields, the system automatically (upon saving) validates the states to ensure that all values (Inhibit Path, Inhibit states, and Enable states) are configured. Validation includes checking if proper values appear in the Inhibit states and Enabled states fields. However, prior to configuring the Inhibit Path, Inhibit states, and Enable states fields of the plmvoldevice record, due diligence is required to ensure that the RealTime Database (RTDB) records used for the plmvoldevice record inputs are also properly configured. The plmvoldevice record automatic validation only ensures that the inhibit path exists and that its comparison value is appropriate. For example, it is possible to configure an input path to a status or multistate record that does not have a valid base message set configuration.

    In the ADE, inhibit paths for plmvoldevice records are immediately verified after creation. You will be unable to save if an invalid path is entered (this process also applies to Inhibit states and Enable states). If, at runtime, the inhibit path becomes invalid (for example, is deleted), then the plmvoldevice record will continue using the last known auto inhibit state (for example, if it were inhibited due to auto inhibit it will remain inhibited) until the plmvoldevice record is reconfigured.