Parameter, field, and function security

Lock examples

Removing a parameter or field from the security dialog lists in DeltaV Explorer may have unintended consequences. The following examples illustrate the effect of removing parameters and fields from the security dialog lists.

Example 1: Attempt to write FIC101/MYPARAM.CV

  • Field name is CV. CV is not listed in the Field Security Properties dialog.

  • Parameter name is MYPARAM. MYPARAM is not listed in the Parameter Security Properties dialog.

  • System Default security is configured as Control.

Result: The lock in effect is Control. Users with the Control key in FIC101's plant area can write it.

Example 2: Attempt to write FIC101/MYPARAM.CV

  • Field name is CV. CV is not listed in the Field Security Properties dialog.

  • Parameter name is MYPARAM. MYPARAM is configured as Tuning in the Parameter Security Properties dialog.

  • System Default security is configured as Control.

Result: The lock in effect is Tuning. Users with the Tuning key in FIC101's plant area can write it. Users with the Control key in FIC101's plant area cannot write it.

Example 3: Attempt to write FIC101/MYALARM.PRI

  • Field name is PRI. PRI is configured as System Records in the Field Security Properties dialog.

  • Parameter name is MYALARM. MYALARM is configured as Tuning in Parameter Security Properties dialog.

  • System Default security is configured as Control.

Result: The lock in effect is System Records. Users with the System Records key in FIC101's area can write it. Users with the Tuning key in FIC101's plant area cannot write it. Users with the Control key in FIC101's plant area cannot write it.