Reviewer Status Tool (Model Review)

Back to top

Purpose and description

The purpose of this extension is to aid in the application of Review Status UDAs to model objects: either parts or assemblies. The extension works with the Reviewer Role (also available on the Tekla Warehouse) or can be customized to work with your own custom workflow. 

Back to top

System requirements

Tekla Structures 2017i through 2019i

Back to top

Installing Reviewer Status Tool

If you’re intending to use this with the Reviewer Role, you also need to obtain the installers for the role in the Warehouse and follow the installation instructions for that extension.

To install the extension:

1. Download the .tsep file from the Tekla Warehouse
2. Extract and install the .tsep

Back to top

Using Reviewer Status Tool

To use the extension:

1. Open the Applications & Components Catalog
2. If in a US environment - expand the “US Extensions” section, otherwise search for “review”
3. Double click on the icon:

4. Select objects to review in the model
5. Fill out applicable fields within Review Status Tool (example below)

6. Click on a stamp action to apply status to members.

Back to top

Reviewer Status Tool settings

The model can be colorized by the current Role’s review status by clicking the Colorization button. To turn off colorization and go back to your standard representation, click the Colorization button again.

The Reviewer Status Tool settings can be accessed by clicking the Settings button in the top right of the dialog.

From the drop-down menu at the top of the settings dialog, all current roles can be accessed and new roles can be created. One role is required for each user that may need to review a Tekla Structures model and apply statuses, eg. Engineer, Architect, GC, etc. Within each role, the user can define which UDAs the status information will be written to. If the tool is being used in conjunction with the Reviewer Role, the UDAs installed with the Reviewer Role will be pre-populated (as shown for the Architect 1 role in the image below).

Property	Description
Name	Submittal Name UDA syntax
Number	Submittal Number UDA syntax
Date	Review Date UDA syntax
Initials	Reviewer Initials UDA syntax
Comment	Review Comment UDA syntax
Status	Review Status UDA syntax
Filter	This option defines whether this role will be used to apply status information to the Assembly level or the Part level. No matter what hierarchy of object is selected in the model, the status will be applied based on this setting. For example, if a user has this setting set to ‘part’ but has the ‘Select Assemblies’ selection switch on while applying the status, the UDA will still be written to the main part of the Assembly selected.

Back to top

Customizing Reviewer Status Tool

Any UDAs can be used alongside this tool. In order to customize, simply choose the Settings button from the dialog, specify the UDA syntaxes to be used and save the values with a new review role name.

Back to top

Additional information

There are different ways this tool can be used, with the Reviewer Role and without.

Used in conjunction with Reviewer Role

In the “Review Status” UDA tab page the key field that changes and where all of the status data is stored/read from is the “Submittal Number” drop down list. This corresponds to the “Number” field within the Reviewer Status Tool. Instead of having three status sets of data (Architect, Engineer, and Contractor) these are shown as a single set in this tool, you switch between reviewing as an Architect, Engineer, or Contractors using the “Role” drop down list. To match the functionality of the Reviewer Role UI, you need to match the Role selection and the Number selection when stamping the model objects.

Used without the Reviewer Role

If no ‘option type’ UDA is set for the field that you’re using to convey Submittal Number, then this field is left open as an integer value.

If you do not want to keep a running history of status data in the model, then you do not need to have the multiple predefined/fixed roles (Architect, Engineer, and Contractor). You could create one setting file called “standard” for the current status that defines where to store the values. Then you would only change the Number field from 1, 2, 3, etc… as you had subsequent status updates.

Back to top

Limitations

• Works on either Assembly level or Part level only; does not handle other object types at this time.
• Value storage types are hardcoded at this time, but names to where the UDAs are stored can be customized in the Role files.
  • Name: string
  • Number: int
  • Date: int
  • Initials: string
  • Comment: string
  • Status Value: int (0=Approved, 1=Approved as Noted, 2=Revise & Resubmit). If there is no stored value (blank) then it will be considered as no status has been applied.

Back to top