Template Data Upgrade

Supports Administrator Guide

MDS/TEMPLATES based template data from AVEVA E3D™ version 1.1 is no longer compatible for use with the Supports application. A conversion tool is provided to transfer existing template data into a recognised format.

Two main changes have been implemented to the format of template data for use with the Supports application.

•

Template data is now stored in an application data world hierarchy rather than a site based hierarchy.

•

All SCTN members and their sub-members have been converted into GENSEC based hierarchies.

The application data world hierarchy separates the template data from the 3D model in the sense that it no longer belongs to a SITE. By default, application data world elements are not visible to the user in the Model Explorer as they are considered to be administrative elements.

The hierarchy for the Supports application template displays as:

Template data is categorised by type.

Template data is contained within a STRU / FRMW hierarchy. All SCTN elements and associated sub-members are converted to the GENSEC format.

Existing template joints, for example, SNOD/SJOI, FITT and CMFI are all converted to the single format of:

Existing PNOD/PJOI joints are converted to the format of:

GENSEC

--ENDATU

--FIXING

Note:

The conversion of these items requires the proper connection reference on the PJOI and the appropriate Joint Start (JOIS) or Joint End (JOIE) on the connected section)

Joint conversion attempts to re-establish connectivity with the original template members which includes the appropriate joint references on the new GENSEC members as well as all rules currently associated with the support.

All SUBS and TMPL elements are copied directly into the new hierarchy.

Convert Existing MDS Template Sites

The Supports application attempts to detect old format template data that exists within the current MDB when opened. For example MDS/ TEMPLATES or MDS/Hangers. If one or more template sites are found, an Error window displays indicating that the template sites must be converted before the application can be entered.

Click OK to close the Error window.

The Convert Template Site window converts multiple instances of template site data in one MDB into multiple APPLDW.


	Candidate template sites to convert	Displays the template sites that are available for conversion.
	Add selected template site(s) to conversion list	Click to move the currently selected template site from the Candidate template sites to convert list to the Selected template sites to convert list.
	Remove selected template site(s) from conversion list	Click to move the currently selected template site from the Selected template sites to convert list to the Candidate template sites to convert list.
	Selected template sites to convert	Displays the template sites that are selected for conversion.
	Conversion status	Displays the template sites that have been converted and the conversion status of each converted template site.
	Details	Click to display the conversion error details for the currently selected template site in the Conversion status list. Refer to Conversion Errors for further information.

Click Apply to convert the template sites in the Selected template sites to convert list.

The naming of the APPLDW is taken from the DB name. For example, /MDS/TEMPLATES in the DB MDS/DESITMPL-BS is converted to APPLDW/SUPPORT/FRAMES/BS. If no suffix is found, the APPLDW uses a number as the suffix. For example SUPPORT/FRAMES/1).

During conversion, a progress bar displays in the bottom right corner of the application window, allowing you to track conversion progress.

When the template site conversion is complete, the new application data world is available for use. The database session must be saved to make sure that the converted data world is stored.

Note:

Additional Template Site Conversion

Additional template sites can be converted using the same methodology as existing MDS/TEMPLATES sites:

•

/MDS/SPECIALS are converted to APPLDW/SUPPORT/FRAMES/SPECIALS/<suffix>

•

/MDS/HANGERS are converted to APPLDW/SUPPORT/HANGERS/<suffix>

•

/MDS/TEMPLATES/ORI are converted to APPLDW/SUPPORT/FRAMES/ORI/<suffix>

Template Sets

Different sets of templates, individually contained in APPLDW elements, can exist in the same MDB. For example, APPLDW may contain BS, DIN and AISC framework template sets.

Each framework template APPLDW must have the PURPOSE set to MDST. By default, the correct PURPOSE is assigned during the conversion process. The description of the APPLDW is taken from the description of the converted SITE. For example:

•

/SUPPORT/FRAMES/BS

•

/SUPPORT/FRAMES/DIN

•

/SUPPORT/FRAMES/AISC

Each template type is based on the PURPOSE of the APPLDW:

•

Framework templates must have the PURPOSE set to MDST

•

Special templates must have the PURPOSE set to MDSS

•

Hanger templates must have the PURPOSE set to MDSH

•

ORI framework templates must have the PURPOSE set to MDSO

The Supports Application Defaults window allows you to select the set of framework templates, special templates and hanger templates for the project. The templates can also be set when entering the Supports application. Refer to Default Creation Zone and Templates for further information.

ORI framework templates are based on the selected framework template.

Once set, the selection is stored in the AVEVA_DESIGN_DFLTS and is restored for each session.

Conversion Errors

During the conversion process a number of checks are performed against the old template sites to identify any conversion errors that have occurred and require review. Errors occur when rules are re-executed or when the geometry of the support template does not match that of the previous template.

The Template Conversion Details window displays the detected errors for a converted site together with error details.


Possible errors detected	Displays conversion errors listed by item. The currently selected item displays in the 3D view, the error is indicated with a red highlight.
Error details	Displays detailed error information for the currently selected error in the Possible errors detected list.

User Defined Attributes

Writes a macro file for missing UDA definitions detected during template conversion.

If missing UDA definitions are detected during template site conversion, a Message window displays.

Click OK to close the Message window. By default, the SCTN- > GENSEC UDA checking tool window displays which allows you to view the missing UDA definitions and write a UDA update macro to be imported into AVEVA Administration™.

The SCTN- > GENSEC UDA checking tool window displays a list of missing UDA definitions together with error messages.

Click write uda update macro to create a macro to be imported into AVEVA Administration™. Upon completion of the macro file creation, a message window displays that indicates the name and location of the macro file.

Click OK to close the Message window.

By default, User Defined Attributes (UDA) are no longer visible. To query a UDA, a direct line command must be used. For example, q :MDSSuppRef