What's New in Bentley Raceway and Cable Management CONNECT Edition Update 4


Product(s):Bentley Raceway and Cable Management
Version(s):10.04.00.31
Environment:N/A
Area:N/A
Subarea:N/A

What's New Highlights

Components Center (Technical Preview)

Components Center is a cloud-based digital component library and catalog management service. It allows users to efficiently manage their digital component libraries while providing their designers with approved, proprietary components as well as manufacturer's content via subscriptions.  

Cell-based equipment can now be stored as components in Components Center.  The Equipment Manager allows you to place cells from Components Center in addition to local or shared cell libraries in a WorkSpace. 

Components Center integration is enabled in the Options > Components Center dialog by selecting the Enable Components Center checkbox. 

iTwin Services Integration 

You can now publish a BRCM i-model and take advantage of the MicroStation bridge to push the data into iTwin Services where you can perform design reviews and identify issues that need resolution.  

Automated Conduit Placement 

A new AutoPlace Conduit tool has been added that allows you to select a raceway segment or trench support and one or more equipment.  The software will automatically generate one more conduits between the selected raceway / trench support and the equipment.  It also adds a virtual connection from the raceway to the conduit to create a complete path that would be recognized when auto routing cables.   

If you need multiple conduits for the same equipment for different voltage levels then a new equipment UDA named, "Conduit_Connections" can be assigned to the equipment where you can specify the type of conduit you want the system to use.  The value of this attribute follows this syntax:  

<Catalog name1>,<Variant1>,<voltage level1>#<Catalog name2>,<variant2>,<voltage level2> 

Where the comma delimits parameters and the hash delimits separate conduit selections based on a voltage level. 

Cable Drums 

Two enhancements have been made to the cable drum features.   

  1. The cable drum number is now included in the cable pull cards. 
  2. The Cable Manager now allows you to export the Cable Drum report to Excel. 

Cable Routing Visualization 

When visualizing a cable route in the Cable Manager we now provide the option of additionally highlighting the optimal route in red if it's different than the actual route that was taken in magenta. 

Enhanced Reporting When Cable Routing Fails  

When cable routing fails we now provide the raceway segment ID that caused failure in the info property making it easier to remedy the issue.   

Utilizing Equipment UDAs in BOQ Product Codes and Descriptions 

You can now include equipment UDA values in the product codes and descriptions that appear in your Bill of Quantities reports. 

New Report Template  

A new report template named, "Detail_Equipment" has been provided that lists the ID of each equipment and it's position (coordinates) in the 3D Model. 

New Raceway Label and Section Table Alignment Options 

The Raceway Label tool has been enhanced so that you can align the labels with either the Raceway Info Line or to the active view.  

The Section Tables now have a Table Direction property that allows you to align the table with the Front, Top, or Active View. 

Excel Equipment Import Now Includes UDAs 

The Excel equipment import is now able to import user defined attribute (UDA) values listed in the Excel file provided that the dataset you are using has those user defined attributes defined.    

Dataset Updates 

Dataset Changes made for Update 4 can be found in the CFG_Properties.xml under each WorkSpace.  

i.e. C:\ProgramData\Bentley\BRCM CONNECT Edition\Configuration\Workspaces\BRCM Imperial Example\Standards\BRCM\std_dataset\metadata\CFG_Properties.xml 

The specific changes in this version can be found under version 3.4 as shown below: 

 <?xml version="1.O" encoding="UTF-8"?> 
<Dataset STANDARD 
+ <Update version 
+ <Update version 
+ <Update version 
+ <Update version 
+ <Update version 
+ <Update version 
+ date version 
<Update version 
Dataset> 
—"imperial" version