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

AVEVA™ Unified Engineering

Status

  • Last UpdatedMay 26, 2023
  • 2 minute read

Use the functionality to display a listing of the standard status and enables user-defined status to be entered within the list. It also enables a restriction to be placed on who can update a clash from or to particular status.

Also use to specify the default status to be allocated to new clashes that do not satisfy auto-acceptance rules.

The standard status cannot be removed, and sequence in which they are displayed signifies their order of priority, when 'worst case' clash details are evaluated by the system. The sequence cannot be changed, but user-defined status can be inserted into the list.

The pane at the top of the tab displays the various status details under Description, State and Access. A Popup Menu is available (mouse right-click) with options of Add, Edit, Delete and Set Default.

For standard status, the Description and State entries are identical, namely, Unknown, Unapproved, Pending, Conditional and Approved, and are read-only. The standard status values are explained below:

Unknown

An initial or default status applied to new clashes if none of the automatic acceptance rules are triggered. The default status for a clash can be configured.

Unapproved

The clash has not been reviewed and remains as a valid or outstanding clash for the project

Pending

This status is used to indicate that the clash is currently under review by the design teams

Conditional

This status is used to indicate that the clash has been reviewed and resolved in the 3D model. This also implies that following the next clash run this clash will no longer appear in the clash report. For reporting purposed this status implies a resolved clash.

Approved

This status is used to indicate that the clash has been reviewed and is considered acceptable by the design team. The clash will continue to be reported in subsequent clash runs but its approved status will remain with the clashing items throughout the remainder of the project lifecycle. If an element has only ‘Approved’ clash status in the database then it is considered ‘Clash Free’.

For user-defined status, the Description can be any text; the State must represent a standard status.

The Access defines who can apply the particular status to a clash or change a clash from the particular status to another. This access restriction is in addition to any set at the Security tab. Access can be set to a discipline, in which case, only a user who has supervisor rights to that discipline can change the status. The alternative access settings are blank or 'Any', both of which signify that there is no access restriction, other than that set at the Security tab.

The Default Status (for New Clashes) drop-down list is for specifying the status to be applied to new clashes that are not automatically accepted.

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