1.1. Defining Macros Raceway IDs can now be defined during raceway placement. In the RW Router dialog box, additional tab ID settings are added to define Raceway ID macros, start value and increment. Users can apply different RW ID settings to individual raceways in the same configuration, or the same RW ID settings can be applied to all raceways included in the configuration. Raceway IDs as defined in the macro, are applied to all selected raceways.
1.2. Using the Insert Attribute option, users can select attributes to be included in the raceway label. Additional separators or text can be combined with attributes to create a macro.
1.3. To insert attributes into ID settings, select the desired attribute from the list and select option Insert Attribute
1.4. Start value settings and increment can be changed as needed. Once the raceway is placed, the start value section is automatically adjusted to the first available number.
1.5. Once a macro is defined, it can be saved for future use. File xml is stored in the metadata folder and is used to store all saved macros
Equipment IDs can now contain more details about equipment through the assignment of equipment ID macros.
If UDA attribute (location and subtype shown in the example below) are associated with equipment, the same UDAs can be used in equipment ID macro.
2.1. To add equipment attributes to the label, select those attributes from the list and use Insert Attribute option to add those to EQP Macro section
2.2 In the example below, Location, Symbol Subtype, and ID are added to the EQP Macro
2.3. If the equipment is placed consecutively (without going back to the Equipment Manager), serial numbers will be automatically adjusted (an example is shown below).
Product codes can now be associated with cables and used in cable schedules and reports. Product codes can be added to the existing cable types definitions in two ways:
3.1. By manually typing individual values in Options>Cable Data.
3.2. If the cable list is more substantial, it is recommended that product codes be imported from the Excel spreadsheet. The existing cable types spreadsheet can be updated by adding an additional column that contains product codes and XML file should be amended to include product code (an example is shown below)
3.3. Once cable type list and XML import files are modified to include cable product code, option Load is used to import the updated cable list
3.4. Review Differences dialog will show product code values
3.5. Once cable product codes are imported, the same will be included in cable schedules.
This enhancement eliminates additional steps needed to make UDA attributes available in reports and i-model.
4.1. New UDAs can be added in Options dialog:
4.2. Once new UDA is added to the raceway catalog, the same can be associated with raceways
4.3. Newly added UDA attributes are automatically available in element properties (those attributes will be included in i-model)
BRCM has the functionality to import Equipment from Excel spreadsheet by utilizing X,Y,Z coordinates and equipment IDs. Enhancement delivered in this release is the ability to specify equipment name vs using generic junction boxes for all imported equipment. Equipment name as defined in the EQP_Equipment_name.XML files is used to define which equipment will be automatically placed using X,Y,Z coordinates with Equipment ID defined in the import file.
5.1. To import a specific equipment list, add an additional attribute in the equipment list to define
The equipment names (must match names defined in the EQP_Equipment_name.XML file as shown below
5.2. Adjust Equipment_Import.XML file to include a column with Equipment name and save changes. In the example below Equipment name is defined in column E, so Equipment Name property is mapped to column E.
5.3. Initiate Equipment Import
5.4. Select Equipment import files
5.5. Accept import of all new equipment
5.6. If any of the equipment names are not found in the dataset, a message similar to one below will come up. To resolve the issue, make changes to the Equipment name (use equipment name available in the dataset) and repeat steps 5.3 and forward.
5.7. Equipment is now automatically placed in DGN file according to coordinates, equipment IDs and equipment names in import files.
To ensure that arch, circle and b-splines of all sizes can be converted into optimal raceway segments, users can now set base number of segments to be used in the conversion process.
In previous BRCM versions, the conversion process was trying to minimize the number of sections needed to convert the arch into the raceway. With this enhancement, the user will be able to define the maximum number of sections needed to convert the arch into the raceway.
6.1. For comparison purposes, when the new setting was left out, the 12’ bend radius arch was converted into a raceway by utilizing 12 individual sections.
6.2.. Once option Arch conversion straight fitting maximum is selected and maximum number set to 20, the same arch is converted to raceway using 20 individual raceway sections. As a result, the last conversion results in a smoother arch.
As a general rule, using a larger number of straight fittings will result in a smoother curve and it might take a longer time to complete the conversion.
Enhancement has been made to use a dashed line style for any overlapping raceway parts. In the previous releases, the entire length of the overlapped raceway section would be depicted with dashed line style and not only the raceway area that is overlapped. Below is 2D extraction with this enhancement.
Compared with the original behavior in the V8i release:
If Raceway catalog contains the location information, the location can be used to organize the report according to location.
8.1. To Include Location information into the raceway catalogs, first add the location as UDA attribute
8.2. To include the location in specific raceway catalog, select the catalog and add the Location UDA
8.3. Once the location UDA attribute has been added to the catalog, place the raceway and define the location UDA attribute during placement.
8.4. If UDA class “val” was defined in the options dialog box, users will be able to type in the location info. If class “collection” has been selected users would need to select the location from the predefined list.
8.5. Each raceway catalog XML file contains the list of UDA attributes specific to that catalog, and new definitions for classes defined as “collection” are defined in this file Example of the location UAD definition is shown below:
8.6. Once the raceway has been placed with associated location information, a report can be created using UDA as a filter.
8.7. The report can be exported to Excel
The new Section Cuts templates have been added to the imperial dataset to match templates already available in the metric dataset
Examples of new templates aer shown below:
10.1. In the BRCM metric dataset users will now find a new project COMOS_Sample
10.2. Once the project is selected, users can select COMOS templates for importing the cable list: CableList_COMOS.xlsx and IMPORT_CableList_COMOS.xml located in the C:\ProgramData\Bentley\BRCM CONNECT Edition\Configuration\Workspaces\BRCM Metric Example\Worksets\COMOS_SAMPLE\Standards\BRCM\Documents
10.3. Those templates are matching the default templates for cable list exported from the COMOS.
10.4. Cable list exported from the COMOS will be imported into BRCM and used for cable management. Once cable management process is completed, the same format of cable list with final cable length can be exported from BRCM and imported back to the COMOS.
Dataset Changes between V8i (SELECTseries 2) Refresh and Bentley Raceway Cable Management CONNECT Edition (Update 2)