Enabling and configuring the Standardized File Naming Utility for WorkSets

The Standardized File Naming Utility initially delivered with Update 4 has been enhanced in Update 5 with a settings file for the recently published BS EN ISO 19650, in addition to those for BS 1192.

BS EN ISO 19650 is now set to be the default in the BuildingTemplate_UK example WorkSet once the utility is enabled.

The configuration provided in the BuildingTemplate_UK.cfg now includes the following:

#======================================================================

# Enabling File Naming Utility:

# These configurations enable the File Naming Utility for UK Standards.

# BS 1192 has been superseded by BS EN ISO 19650, settings for both are included

# for compatibility with existing projects

#======================================================================

            #BB_NAMING_STANDARDS_ENABLE = 1

            BB_NAMING_STANDARDS_FILE = $(TFDIR_SETTING)BS_EN_ISO-19650_FilenameSetting.xml

            #BB_NAMING_STANDARDS_FILE = $(TFDIR_SETTING)BS1192_FilenameSetting.xml

            # Uncomment and enter a valid alphanumeric project ID of 2-6 characters in length

            # to automatically enter the ID into new file names

            #BB_NAMING_STANDARDS_PROJECT_ID =

The previous settings for BS 1192 can be enabled by commenting out the BS_EN_ISO-19650 line and uncommenting the BS 1192 line.

Note that this utility is turned off by default to avoid unwanted steps in file creation.

To enable the utility:

To enable the utility uncomment the first line to make active:

BB_NAMING_STANDARDS_ENABLE = 1

To pre-set some fields:

We also have the facility to pre-set the project code fro each WorkSet. To do this uncomment (or add to the WorkSet.cfg) the line containing BB_NAMING_STANDARDS_PROJECT_ID and enter the appropriate 4-6 character project code, e.g.:

BB_NAMING_STANDARDS_PROJECT_ID = ABC123

The configuration variable method has been provided as the project code varies for (usually!) every WorkSet, a single setting in the XML can then be used for every project.

The Originator field shown above is also likely to be fixed for the majority of users and will in most cases to common to all projects in a WorkSpace (or for may firms, their whole organization). Adding a single pre-populated pop-down option will fix this as shown here:

        <Control Label="Originator" Order="2" Format="AlphaNumeric" Prefix="-" MinChars="3" MaxChars="6" Required="" CacheValue="true">
            <Desc>A unique identifier for each organization. The code for each originating organization should be from 3-6 characters. (Required)</Desc>
            <Attr>BSUK</Attr>  <!-- Preset Organization code -->
        </Control>

Note that CacheValue is set to True so the selection will be remembered by the utility. The pop-down list is fixed and contains only one option thus enforcing the standard.

Using other standards:

These XML settings files can be used as a basis for other standards, the entire layout of the File Naming Utility and the behavior and content of each field is controlled by the XML so any national or organization standard can be accommodated. A sample File Naming utility XML file is provided by default (C:\Program Files\Bentley\OpenBuildings CONNECT Edition\OpenBuildingsDesigner\Default\Data\StandardsFilenameSetting.xml) You can use this sample file as a template to create your own file naming standards XML files. 

Sub-sections of the file can be populated to create variations applicable to differing model types. For example, for 2D sheet models it might be appropriate to pre-set the Type field.

The configuration statements shown above can be used as a template for enabling the utility with other regional datasets by adding a similar set of configuration statements to the WorkSet.cfg files involved.