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

AVEVA™ Unified Engineering

Data Access Control Modify Checks

  • Last UpdatedJan 24, 2023
  • 2 minute read

The Supports application performs a Lock and Data Access Control Modify check on the POS attribute when making any modification to a support. Some modifications require access to all parts of the Support, and some modifications are more specific in their access requirements.

You can modify a framework support if it contains a locked ancillary. If the ancillary is locked by the Lock attribute, or the Position attribute is locked by DAC, the support can be modified but only certain modifications are allowed. Functionality is available to use Status Control and DAC to lock ancillaries in response to design approval whilst allowing scope for acceptable modification thereafter.

You may not make modifications that affect the whole support, for example, modifying the position, flipping or mirroring. You may not make modifications that affect the locked ancillary directly, for example, modifying the datum ancillary, reselecting the ancillary, adding or modifying packing pieces or compensation plates, or modifying reinforcement pad details.

Configurations FT05 and CT03 do not support further modification when an ancillary is locked as the application requires write access to the whole support.

You can make modifications to the support that do not impact the locked ancillary, for example, adding a pipe, tray or duct, extending sections, adding bracing or reselecting structural members. Modifications cannot be made to a locked ancillary, for example, as a result of a structural change, and if needed this is detected by the support health check.

When configuring DACs for this purpose, the following settings are recommended:

  • Element types must be one of:

    • ANCI if the requirement is to lock individual ancillaries on a support

    • Any other support element type according to project requirements

  • Qualifying condition must evaluate TRUE if the item is not to be modified

    • For example, using a status expression similar to ( ATTRIB STVNUM(ID /SupportStatus ) GE 50 ) or

    • Other means to evaluate the lifecycle status of the item

  • Operations must

    • Disallow Modify

    • Depending on project requirements, typically also disallow Create, Delete, Claim, Issue and Drop

  • Attributes must be POS for the DACMOD restriction

  • Error message, for example, You may not modify an approved support.

The effect of the DAC configuration can be tested on the ANCI by querying the DACMOD(POS) pseudo attribute. If this returns a FALSE value, the condition has evaluated TRUE, and the ANCI will be treated as locked.

TitleResults for “How to create a CRG?”Also Available in