Supports Application Data Access Control Checks

Supports Administrator Guide

There are two types of Data Access Control (DAC) checks available with the Supports application.

•

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.

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.

Data Access Control Modify Checks

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.