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 Roleuser group profile in a certain Tekla Structures environment that limits the available files and settings
In Tekla Structures, different roles may be available in each Tekla Structures environment. Typically the following roles are available: all, concrete contractor, general constructor, engineer, precast concrete detailer, rebar detailer, and steel detailer.
(also available on the Tekla Warehouseservice for collaboration and for storing and sharing Tekla Structures content
In Tekla Warehouse the content items are stored in collections. Tekla Warehouse includes the Tekla Warehouse Service and the Tekla Warehouse web site.
Tekla Warehouse is one of the Tekla online services.
) or can be customized to work with your own custom workflow.
Tekla Structures 2017i
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:
- Download the .tsep file from the Tekla Warehouse
- Extract and install the .tsep
To use the extension:
- Open the Applications & Components Cataloguser interface for displaying or modifying information in categorized lists
For example, profile catalog and shape catalog are catalogs.
- If in a US environment - expand the “US Extensions” section, otherwise search for “review”
- Double click on the icon:
- Select objects to review in the model
- Fill out applicable fields within Review Status Tool (example below)
- Click on a stamp action to apply status to members.
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 representationthe way that the information included in a model is represented visually
, 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 modelbuilding information model that is built with Tekla Structures and that represents a structure to be constructed, containing information needed to manufacture and construct the structure, and other information related to the project
A model is the single source of information for drawings and other model outputs, such as reports and NC files. This ensures that the information in drawings and reports is always up to date, since they react to modifications in the model and are updated accordingly.
Tekla Structures supports multiple users working concurrently on the same model, even in different locations.
A model can be utilized in other software.
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).
|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.|
Any UDAs can be used alongside this tool. In order to customize, simply choose the Settings button from the dialog, specify the UDAobject property created by the user in order to widen the range of predefined object properties
User-defined attributes are used when the predefined object properties are not sufficient but more properties are needed. For example, comment, locked, and erection status are user-defined attributes.
syntaxes to be used and save the values with a new review role name.
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.
, please add the following text to contentattributes.lst, under the "Custom attributes included outside the installation" section (see example below text). The contentattributes.lst file is located here: TeklaStructures\<version>\Environments\usimp\template\settings.
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.
- Works on either Assembly levelassembly’s place in the assembly hierarchy
The assembly level is expressed as a number.
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.