Data Access Control Issue Checks

The Supports application performs a Lock and Data Access Control Issue check as part of support creation or modification. A project can then set some control over what can be supported, and what can be supported from.

When selecting a piping, HVAC or cable tray item to be supported, a check is made on that item to confirm if it is available to be supported. With the correct Lock or DAC configuration, the project can control if any workflows on that item, for example, design checks and approvals, prevent it from being selected for additional support.

When selecting a Structural or Civils item to support from, a check is made on that selected item to confirm if it is available to be supported from. With the correct configuration, the project can control if any workflows on that item prevent it from being selected to take the additional load.

A similar check is made on an ancillary when converting a preliminary support to another support type.

In each case the check consists of first a Lock check and then a DACISS (DAC Issue) check. If the item is Locked or DACISS returns a FALSE value, it will not be available for selection either as an item to be supported or an item to support from. This check is distinct from having write access as no write access is required for the item being supported or the item being supported from. Note that the Issue operation is not attempted by the Supports application and is used just for this check.

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

• Element types must be one of:

  • Supported types, for example, piping component, branch, HVAC component, cable tray component

  • Type to support from, for example, GENSEC or Civils type

  • ANCI for a preliminary support

  • ALL if the qualifying conditions will evaluate appropriately for the different scenarios

• Qualifying condition must evaluate TRUE if the item is not available for Supports:

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

  • Other means to evaluate the lifecycle status of the item

• Operations must:

  • Disallow Issue

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

• Attributes must be ALL for the DACISS restriction

• Error message, for example, This item is not available for Supports.

The effect of the DAC configuration can be tested on the item by querying the DACISS pseudo attribute. If DACISS returns a FALSE value, the condition has evaluated TRUE, and selecting that item for a support will return an error.