In the CONNECT Edition, the software utilizes the native Power Platform configuration system to locate the dataset, connect to the project database, and specify various default settings.
Note: Power Platform is the MicroStation core application that underlies the CONNECT Edition product.
New configuration variables have been introduced that can be set in any configuration file to configure the software. The purpose of this article is to provide a comprehensive list of the application specific variables that are used to configure the software and explain their purpose.
Application variables are prefixed with “BRCM_” to set them apart from the standard Power Platform variables.
The following table provides a complete list of the application specific variables and explains their purpose:
Name
Operator
Value Type
Value (typical)
Description
BRCM_APPLICATION
=
String
BRCM
Short name of the application
BRCM_DB_CONNECTSTRING
DSN=BRCMUSER;UID=BRCMUser;PWD=BRCM
Connection String for SQL Server Database.
BRCM_DB_ID
MYWORKSET
Prefix given to the SQL table names which typically matches the WorkSet name.
BRCM_DB_STATIONID
$(computername)
Unique work station ID.
BRCM_DIR
C:\Program Files\Bentley\Bentley Raceway and Cable Management CONNECT Edition\BRCM\
BRCM_FILE_UPDATE_OPTION
1
Controls how data is saved to the database when the design file is closed (0: no update, 1: Prompt to update, 2: silent update)
BRCM_IMODEL_PUBLISH_MODE
0
Not used in CONNECT Edition
BRCM_WS_EQUIPMENT
C:\ProgramData\Bentley\BRCM CONNECT Edition\Configuration\Workspaces\BRCM Metric Example\Standards\BRCM\std_dataset\equipment
Location of equipment data files
BRCM_WS_LANGUAGE
EN
Language Code for localized metadata files
BRCM_WS_METADATA
C:\ProgramData\Bentley\BRCM CONNECT Edition\Configuration\Workspaces\BRCM Metric Example\Standards\BRCM\std_dataset\metadata
Location of metadata files.
BRCM_WS_RACEWAY
C:\ProgramData\Bentley\BRCM CONNECT Edition\Configuration\Workspaces\BRCM Metric Example\Standards\BRCM\std_dataset\raceway
Location of raceway data files.
BRCM_WS_RACEWAY_TEMPLATES
C:\ProgramData\Bentley\BRCM CONNECT Edition\Configuration\Workspaces\BRCM Metric Example\Standards\BRCM\std_dataset\raceway\Templates
Location of raceway templates.
BRCM_WS_SCHEMAS
C:\ProgramData\Bentley\BRCM CONNECT Edition\Configuration\Workspaces\BRCM Metric Example\Standards\BRCM\std_dataset\schemas
Location of EC schema files.
BRCM_PW_SUBFOLDER_CPC
\Cable Pull Cards
Project subfolder for cable pull cards
BRCM_PW_SUBFOLDER_REPORTS
\Reports
Project subfolder for reports
BRCM_IMAGE_PATH
C:\ProgramData\Bentley\BRCM CONNECT Edition\Configuration\Workspaces\BRCM Metric Example\Worksets\BRCM_EU_EN\Standards\BRCM\Reports\Images
Location of the cable routing path images.
BRCM_OPM_CABLE_CONNECTION
ELECTRICAL_DEVICE_OFFSET
X,Y,Z Offset from the insertion point of the OPM equipment for electrical device.
BRCM_USER_DEFINED_CONFIGS
$(APPDATA)/Bentley/$(BRCM_APPLICATION)/userconfigs/
As a BRCM administrator, you can now define custom ID, Raceway, and Duct Bank spacer configurations and adjust a configuration variable to control where these configurations are saved making it more convenient for you to control who has rights to modify them. The variable, BRCM_USER_DEFINED_CONFIGS by default is set to the local user's app data folder, but can be changed as you desire.
BRCM_ENABLE_EC_PROVIDER
Disables the EC Provider that populates the list of cables in the Explorer by querying the SQL database. By omitting cables from the Explorer tree performance will be greatly improved when designing with the Explorer dialog open. If you require cable data in the Explorer tree you can enable the provider by entering a value of "1" .
BRCM_DB_TYPE
iTwin
PlantSight Integration (Technical Preview).Persist project data inside iModel in PlantSight without the need of SQL Server database.
BRCM_ITWIN_IMODLE_NAME
'iModelName
PlantSight Integration (Technical Preview).Specifies the name of the iModel in PlantSight portal.
BRCM_ITWIN_CACHE_PATH
D:/BRCMiModelCache
PlantSight Integration (Technical Preview). Specifies the location of cache folder.
These configuration variables can be set in any configuration file. To understand how these variables are used in the configuration files that are delivered with a default installation of the software, please refer to the Configuration Files article.