You are currently reviewing an older revision of this page.
The 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 uncomment the first line to make active:
BB_NAMING_STANDARDS_ENABLE = 1
We also have the facility to pre-set the project code. To do this uncomment 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 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.
The configuration 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.