<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Migrating custom content from AECOsim Building Designer SS6 to a current OpenBuildings Designer version</title><link>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>Migrating custom content from AECOsim Building Designer SS6 to a current OpenBuildings Designer version</title><link>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version</link><pubDate>Tue, 26 Oct 2021 11:45:57 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:74ea833a-2c67-4860-90b8-05cf1fd96ae0</guid><dc:creator>Marc Thomas</dc:creator><comments>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version#comments</comments><description>Current Revision posted to OpenBuildings | AECOsim | Speedikon Wiki by Marc Thomas on 10/26/2021 11:45:57 AM&lt;br /&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;" width="30%"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;OpenBuildings Designer&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;CONNECT Edition&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Datasets and content&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Migration/Upgrade&lt;span&gt; &lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;This article focuses on the migration of project&amp;nbsp;and customized dataset content.&lt;/p&gt;
&lt;p&gt;The principles of migrating a V8i Workspace to a CONNECT Edition Configuration is&amp;nbsp;covered by training course&amp;nbsp;&lt;a href="https://learn.bentley.com/app/Public/ViewLearningPathDetails?lpId=113058&amp;amp;aftkn=5527c519-bbc7-4890-9a2e-063edc9da5c0" rel="noopener noreferrer" target="_blank"&gt;BIM Management 301: Installation and Upgrade Guide&lt;/a&gt;, we recommend viewing this training and downloading the course workbook prior to embarking on a migration process. We have also published a playlist of YouTube videos covering the same material:&amp;nbsp;&lt;a href="https://www.youtube.com/playlist?list=PL7jfe0_WZE1qraPxafKm0hf_Eurbrss2c" rel="noopener noreferrer" target="_blank"&gt;BIM Management 301: Installation and Upgrade Guide - YouTube&lt;/a&gt;, this article includes links to some of these videos.&lt;/p&gt;
&lt;p&gt;A key recommendation is that any &lt;span&gt;CONNECT Edition Configuration should be in a separate folder structure&amp;nbsp;to any existing V8i Workspace; their folder structures&amp;nbsp;and configuration files are significantly different. Using a separate&amp;nbsp;location allows any new Configuration to be tested without affecting&amp;nbsp;an active production Workspace.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The migration of delivered dataset content from SS6 to CONNECT Edition is relatively straightforward as the dataset changes have been minimised for most datasets. Please note the exception to this: due to major changes in British standards the V8i UK/GB dataset is not directly compatible with the CONNECT versions. Please see &lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/35923/connect-edition---british-dataset-migration" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - British Dataset migration&lt;/a&gt;&amp;nbsp;for full details.&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Step 1: Preparation&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Decide where&amp;nbsp;the CONNECT Edition configuration will be located, this must be in a separate location to the active V8i Workspace, even if only in a different root folder on a network share.&lt;/span&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Decide whether structural elements will be upgraded from the legacy building tools to work with the ProStructures functionality available from&amp;nbsp;OpenBuildings Designer Update 7 onwards. This is a one way upgrade that offers additional capability, for an overview of this capability please see this playlist:&amp;nbsp;&lt;a style="font-family:inherit;" href="https://www.youtube.com/playlist?list=PL7jfe0_WZE1rk9JVA-jRTWO4B6E_uje1m"&gt;OpenBuildings Designer: Next Generation of Structural Elements - YouTube&lt;/a&gt;.&lt;br /&gt;Regardless of this decision there are a number of &lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/51023/configuration-changes-to-support-prostructures-interoperability" rel="noopener noreferrer" target="_blank"&gt;ProStructures folders and files&lt;/a&gt; that must be present in the Custom Configuration for the application to run successfully. (A standard installation of&amp;nbsp;OpenBuildings Designer Update 7 or later will include these.)&lt;span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;span style="font-family:inherit;"&gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Identify custom dataset content used in V8i, this could be cell libraries, DGNLIBs, XML files, etc. Ideally this content will be in separate folders and files from Bentley&amp;#39;s example dataset, however it may well be mixed in alongside delivered content. This will depend on how the V8i Workspace was organised.&lt;/span&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decide how the example dataset(s) will be used. There are two main options:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Use as is accepting that some of the example content will not suit your situation. This means that when a new dataset is released it can simply replace the existing version without affecting any customisations.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Take ownership of the example dataset, modifying it as needed. This requires both a different approach when a new dataset is released and an organised approach to the creation and storage of custom content. Custom content should always be contained in clearly identified files to enable any changed files from Bentley to be added/replaced/deleted. Changes introduced by new versions are listed in the &lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/51437/dataset-changes-in-the-latest-version-of-openbuildings-designer" rel="noopener noreferrer" target="_blank"&gt;dataset delta document&lt;/a&gt; and must be implemented manually.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decide where the dataset(s) will be located. There are two options:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;In the Custom Configuration (recommended). This is suitable for either of the options 1 or 2 above.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the local machine. This only applies if the delivered dataset is used unchanged, option 1 above, unless some external process is available to synchronize any customizations to the local copy.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="padding-left:30px;"&gt;These are discussed in more detail in&amp;nbsp;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/51041/dataset-strategies---local-or-network" rel="noopener noreferrer" target="_blank"&gt;Dataset Strategies - Local or Network&lt;/a&gt;.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;em&gt;Please note that the default location for the datasets&amp;nbsp;folder in a custom configuration changed after Update 7, this is discussed in&amp;nbsp;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/50875/configuring-the-datasets-root-folder-location"&gt;&lt;span lang="en-US"&gt;Configuring the Datasets Root Folder Location&lt;/span&gt;&lt;/a&gt;.&amp;nbsp;From Update 8 onwards the default location will be the Datasets folder in the Custom Configuration.&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Plan the implementation of access control via Windows File/Folder permissions to Organization, WorkSpace and WorkSet levels, the purpose of which is to ensure that only the responsible people are able to modify shared content:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Organization: Read-only to non-admin users.&lt;/li&gt;
&lt;li&gt;WorkSpaces: Write access to appropriate administrators, this may include BIM Coordinator type roles depending on organizational structure.&lt;/li&gt;
&lt;li&gt;WorkSets: Write access to all relevant users.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For initial design and testing of a new configuration we recommend using a local folder. Once the following steps including testing and validation are&amp;nbsp;be completed locally the entire Custom Configuration can be copied to a network location for further testing.&lt;/p&gt;
&lt;h1&gt;Step 2: Installing and Directing OpenBuildings Designer to a Network Location&lt;/h1&gt;
&lt;p&gt;To create a complete example configuration install OpenBuildings Designer in the normal manner, specifying the Custom Configuration path on your local machine that will be used initially. Doing this via the installer is described in&amp;nbsp;&lt;a href="https://www.youtube.com/watch?v=67Zi9_TDcNQ&amp;amp;list=PL7jfe0_WZE1qraPxafKm0hf_Eurbrss2c&amp;amp;index=1"&gt;Part 1 - Installing OpenBuildings Designer to a Network Location - YouTube&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The location of a custom configuration is stored in ConfigurationSetup.cfg on each machine. This is the only file that needs to be modified to redirect a machine to a custom configuration.&amp;nbsp;The configured location does not have to be available when OpenBuildings Designer is installed, the path will be ignored unless WorkSpace CFG files are present.&lt;/p&gt;
&lt;p&gt;If OpenBuildings Designer is already installed ConfigurationSetup.cfg can be updated as described in &lt;a href="/products/projectwise/content_management/w/wiki/53045/projectwise-drive" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - Configuration Tips : Should I edit ConfigurationSetup.cfg?&lt;/a&gt;&lt;/p&gt;
&lt;h1&gt;Step 3:&amp;nbsp;Populate the Custom Configuration&lt;/h1&gt;
&lt;p&gt;Creating the required folder structure is outlined in &lt;a href="https://www.youtube.com/watch?v=3KbLtNL-fns&amp;amp;list=PL7jfe0_WZE1qraPxafKm0hf_Eurbrss2c&amp;amp;index=2" rel="noopener noreferrer" target="_blank"&gt;Part 2 - Setting Up the Dataset and Organization Folders - YouTube&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Shown below is a typical example where the Datasets are located in the Custom Configuration under ...\OBD_Resources\Datasets\; one WorkSpace named ActiveProjects_365 is contained in the WorkSpaces folder.&lt;/p&gt;
&lt;table border="1" height="789"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td rowspan="3"&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635168631491v2.png" /&gt;&lt;/td&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;Datasets:&lt;/p&gt;
&lt;p&gt;Unless configured otherwise the Catalog User Interface will treat the active Dataset as the Organization level&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635169877994v3.png" /&gt;&lt;/p&gt;
&lt;p&gt;Organization level custom content may be stored here depending on the decision discussed above about use of delivered datasets.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;Organization:&lt;/p&gt;
&lt;p&gt;Unless configured otherwise the Organization subfolders contain shared platform or ProStructures content directed to by Standards.cfg and some &lt;span&gt;ProStructures&amp;nbsp;&lt;/span&gt;CFG files. Any content here will be available to all users unless configured otherwise.&lt;/p&gt;
&lt;p&gt;There are no other OpenBuildings specific folders.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;WorkSpaces:&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The Catalog&amp;nbsp;Editor will recognize the&amp;nbsp;WorkSpaces folder as the WorkSpaces&amp;nbsp;level.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Any content here will be available only to&amp;nbsp;users of the active WorkSpace.&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Step 4: Create WorkSets&lt;/h1&gt;
&lt;p&gt;The default WorkSet location will be in the WorkSets folder within the Custom Configuration. Live project data should always be separated from back office shared resources so WorkSet folders will need to be in the appropriate project data location. This is covered by &lt;a href="https://www.youtube.com/watch?v=_7FtTz64USg&amp;amp;list=PL7jfe0_WZE1qraPxafKm0hf_Eurbrss2c&amp;amp;index=5" rel="noopener noreferrer" target="_blank"&gt;Part 5 - Moving WorkSets to a Separate Drive - YouTube&lt;/a&gt;, the essential part of which is editing the _USTN_WORKSETROOT path in all WorkSpace CFG files. In this example that file is&amp;nbsp;ActiveProjects_365.cfg and it needs to contain a line defining&amp;nbsp;&lt;span&gt;_USTN_WORKSETROOT as pointing to the project data location, for example P:\ActiveProjects\OBD_AU_Demo\, e.g.:&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;For testing:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;em&gt;_USTN_WORKSETROOT = C:/ActiveProjects/$(_USTN_WORKSETNAME)/&lt;/em&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;For production:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;em&gt;_USTN_WORKSETROOT = P:/ActiveProjects/$(_USTN_WORKSETNAME)/&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Create a new WorkSet by copying the appropriate regional WorkSet example,&amp;nbsp;for example BuildingTemplate_AU:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The&amp;nbsp;BuildingTemplate_AU folder should be copied to the project data location&lt;/li&gt;
&lt;li&gt;BuildingTemplate_AU.cfg should be copied to the WorkSets folder.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Both must be renamed with the new project name, folder and CFG file names must match since this is what links them together.&lt;/p&gt;
&lt;p&gt;For testing we recommend that a completely new project structure is used (during the initial testing this could also be on a local drive).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Once the example WorkSet has been copied, but before adding any V8i content or making site specific changes to folder structures, test the new Custom Configuration. Review any messages displayed in the Message Center or elsewhere in the UI taking appropriate action to rectify them.&lt;/p&gt;
&lt;p&gt;At this stage also run the Dataset Validator&amp;nbsp;to ascertain the current state of the dataset.&amp;nbsp;It will be easier to fix any errors before custom content is added. (File &amp;gt; Dataset Tools &amp;gt; Validate. Help:&amp;nbsp;&lt;a href="https://docs.bentley.com/LiveContent/web/OpenBuildings%20Designer%20Help-v4/en/ARCH_DataGroupValidationDbox.html" rel="noopener noreferrer" target="_blank"&gt;DataGroup System Validator&lt;/a&gt;)&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/resized-image/__size/640x480/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635240790157v1.png" /&gt;&lt;/p&gt;
&lt;p&gt;An error free report at this point will confirm that the DataGroup Catalog is valid prior to the addition of custom content.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;Step 5: Add previous custom content&lt;/h1&gt;
&lt;p&gt;Check against dataset delta documents to see if any of the custom V8i files are now obsolete. For instance, since V8i curtain walls are superseded by a completely new CONNECT Edition tool, earlier content will not work with this new tool.&lt;/p&gt;
&lt;p&gt;Add V8i files in the appropriate locations at&amp;nbsp;&lt;span&gt;Organization, WorkSpace or WorkSet levels.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Run the Dataset Validator&amp;nbsp;again and fix any errors.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Test that the&amp;nbsp;content&amp;nbsp;is available in the UI,&amp;nbsp;i.e. in the&amp;nbsp;Catalog Editor and in the building and building systems element placement&amp;nbsp;tools.&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;Step 6: Modify WorkSet folder names or structure as appropriate to conform with organization standards&lt;/h1&gt;
&lt;p&gt;This step is put at the end of the process so a baseline is established before any site specific changes to&amp;nbsp;folder structures and files names are made. This narrows down the scope of any troubleshooting&amp;nbsp;that may be necessary; when CFG file are being edited even simple typos can cause errors.&lt;/p&gt;
&lt;p&gt;For example, in the example WorkSet CFG the default folder for design files is&amp;nbsp;called &amp;#39;Designs&amp;#39;:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635173318687v1.png" /&gt;&lt;/p&gt;
&lt;p&gt;This is defined by the lines:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635173558944v2.png" /&gt;&lt;/p&gt;
&lt;p&gt;If the folder location is correct, but the name &lt;span&gt;&amp;#39;Designs&amp;#39;&amp;nbsp;&lt;/span&gt;does not comply with project standards it can be renamed. The name &amp;#39;Designs&amp;#39; in the&amp;nbsp;&lt;span&gt;_USTN_WORKSETDGNS statement must then be changed to match the new folder name. (This has to be done by text editing since we do not have a UI for such changes.)&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;Step 7: Add any CONNECT Edition custom content (optional, can be done at a later stage)&lt;/h1&gt;
&lt;p&gt;New features in&amp;nbsp;&lt;span&gt;CONNECT Edition may benefit from customized content so this may be an appropriate point to add such&amp;nbsp;content.&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;&lt;span&gt;Step 8: Copy existing DGN files&lt;/span&gt;&lt;/h1&gt;
&lt;p&gt;&lt;span&gt;Existing DGN files and other WorkSet specific content should&amp;nbsp;be copied&amp;nbsp;into the appropriate folders in the CONNECT Edition WorkSet.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Any model files&amp;nbsp;that contain building elements (these are typically all of the 3D model files in a project) must be synchronised&amp;nbsp;with the new dataset using the&amp;nbsp;Schema Upgrade Utility. This can be done to all files in one go as explained in &lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479/upgrade-existing-elements-and-their-properties-to-the-current-catalog-schema" rel="noopener noreferrer" target="_blank"&gt;Schema Upgrade Utility&lt;/a&gt;:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;img src="/resized-image/__size/640x480/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635247888837v3.png" alt=" " /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The utility should&amp;nbsp;also be run on any existing&amp;nbsp;&amp;nbsp;BB_Floormaster.dgnlib. This may be successful, however as there have been significant changes&amp;nbsp;to the internal structure of&amp;nbsp;&amp;nbsp;BB_Floormaster.dgnlib since V8i we cannot&amp;nbsp;guarantee that&amp;nbsp;&amp;nbsp;BB_Floormaster.dgnlib content will be entirely&amp;nbsp;valid. It may be necessary to recreate the floor and Grid Systems content.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;2D files, generally&amp;nbsp;drawing&amp;nbsp;and sheets, do not contain building elements so do not need to be upgraded.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;To use the Verify Parts utility the WorkSet will need to contain some DGN files (File &amp;gt; Utilities &amp;gt; Part Utilities &amp;gt; Verify Parts. Help:&amp;nbsp;&lt;a href="https://docs.bentley.com/LiveContent/web/OpenBuildings%20Designer%20Help-v4/en/VerifyPartsDbox.html" rel="noopener noreferrer" target="_blank"&gt;Verify Part and Family&lt;/a&gt;)&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635242939413v2.png" /&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;If models contain Catalog Items or Parts that are not present in the new dataset, the DataGroup Transformation Utility can be used to missing custom properties to delivered properties, and the Part utilities can be used to verify and where necessary remap parts to elements (help: &lt;a href="https://docs.bentley.com/LiveContent/web/OpenBuildings%20Designer%20Help-v4/en/DataGroupTransformationServicesDialogBox.html" rel="noopener noreferrer" target="_blank"&gt;DataGroup Transformation Utility&lt;/a&gt;):&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;img alt=" " src="/resized-image/__size/640x480/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635241392109v4.png" /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;If significant differences between V8i and CONNECT are apparent a mapping file can be built&amp;nbsp;to apply to subsequent&amp;nbsp;project&amp;nbsp;to WorkSet migrations. This is a time saver when it comes to migrating multiple projects.&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;Step 9: Copy New Configuration and WorkSets to Network Locations&lt;/h1&gt;
&lt;p&gt;The new &lt;span&gt;Configuration and WorkSets can be copied to network locations&amp;nbsp;for sharing and further testing o&lt;/span&gt;nce local setup and testing&amp;nbsp;reaches a satisfactory status.&lt;/p&gt;
&lt;p&gt;To use these locations two files will need to be edited:&lt;/p&gt;
&lt;h2&gt;ConfigurationSetup.cfg&lt;/h2&gt;
&lt;p&gt;Edit the line:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;em&gt;_USTN_CUSTOM_CONFIGURATION = &amp;lt;path&amp;gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;as described in&amp;nbsp;&lt;/span&gt;&lt;a href="/products/projectwise/content_management/w/wiki/53045/projectwise-drive" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - Configuration Tips : Should I edit ConfigurationSetup.cfg?&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;Any WorkSpace CFG Files&lt;/h2&gt;
&lt;p&gt;Edit the value of&amp;nbsp;_USTN_WORKSETROOT from the local path to match the network path&amp;nbsp;e.g.:&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;em&gt;_USTN_WORKSETROOT = P:/ActiveProjects/$(_USTN_WORKSETNAME)/&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;All other files will be exactly as they were locally, this should be a simple duplication.&lt;/p&gt;
&lt;p&gt;Copying the Custom Configuration is straightforward, it should be in a new entirely separate share/folder to the V8i Workspace.&lt;/p&gt;
&lt;p&gt;WorkSet content can be more complex as real-world project folder structures are generally used by multiple applications and user groups. How migrated WorkSet content is inserted into existing project structures is a matter of judgement in each situation. Some guidelines to follow are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Remove V8i project configuration content to archive. Typically, this would be the &amp;#39;support&amp;#39; folder and its contents.&lt;/li&gt;
&lt;li&gt;Run the Schema Upgrade Utility and other tools as necessary on DGN files.&lt;/li&gt;
&lt;li&gt;Ensure users do not attempt to access migrated projects (WorkSets) with AECOsim V8i applications.&lt;/li&gt;
&lt;li&gt;Ensure statements in the WorkSet CFG containing paths to project folders and folder names are matched with those in use (as Step 6 above) taking any variations that may exist between projects into account.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/03548.NewLogo.png"&gt;&lt;img style="border-width:0px;" alt=" " height="60" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" width="189" /&gt;&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Custom Configuration, CONNECT Edition, v8i, OpenBuildings Designer, Migration, AECOsim Building Designer, Configuration&lt;/div&gt;
</description></item><item><title>Migrating custom content from AECOsim Building Designer SS6 to a current OpenBuildings Designer version</title><link>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version/revision/12</link><pubDate>Tue, 26 Oct 2021 09:55:24 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:74ea833a-2c67-4860-90b8-05cf1fd96ae0</guid><dc:creator>Marc Thomas</dc:creator><comments>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version#comments</comments><description>Revision 12 posted to OpenBuildings | AECOsim | Speedikon Wiki by Marc Thomas on 10/26/2021 9:55:24 AM&lt;br /&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;" width="30%"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;OpenBuildings Designer&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;CONNECT Edition&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Datasets and content&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Migration/Upgrade&lt;span&gt; &lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;This article focuses on the migration of project&amp;nbsp;and customized dataset content.&lt;/p&gt;
&lt;p&gt;The principles of migrating a V8i Workspace to a CONNECT Edition Configuration is&amp;nbsp;covered by training course&amp;nbsp;&lt;a href="https://learn.bentley.com/app/Public/ViewLearningPathDetails?lpId=113058&amp;amp;aftkn=5527c519-bbc7-4890-9a2e-063edc9da5c0" rel="noopener noreferrer" target="_blank"&gt;BIM Management 301: Installation and Upgrade Guide&lt;/a&gt;, we recommend viewing this training and downloading the course workbook prior to embarking on a migration process. We have also published a playlist of YouTube videos covering the same material:&amp;nbsp;&lt;a href="https://www.youtube.com/playlist?list=PL7jfe0_WZE1qraPxafKm0hf_Eurbrss2c" rel="noopener noreferrer" target="_blank"&gt;BIM Management 301: Installation and Upgrade Guide - YouTube&lt;/a&gt;, this article includes links to some of these videos.&lt;/p&gt;
&lt;p&gt;A key recommendation is that any &lt;span&gt;CONNECT Edition Configuration should be in a separate folder structure&amp;nbsp;to any existing V8i Workspace; their folder structures&amp;nbsp;and configuration files are significantly different. Using a separate&amp;nbsp;location allows any new Configuration to be tested without affecting&amp;nbsp;an active production Workspace.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The migration of delivered dataset content from SS6 to CONNECT Edition is relatively straightforward as the dataset changes have been minimised for most datasets. Please note the exception to this: due to major changes in British standards the V8i UK/GB dataset is not directly compatible with the CONNECT versions. Please see &lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/35923/connect-edition---british-dataset-migration" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - British Dataset migration&lt;/a&gt;&amp;nbsp;for full details.&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Step 1: Preparation&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Decide where&amp;nbsp;the CONNECT Edition configuration will be located, this must be in a separate location to the active V8i Workspace, even if only in a different root folder on a network share.&lt;/span&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Decide whether structural elements will be upgraded from the legacy building tools to work with the ProStructures functionality available from&amp;nbsp;OpenBuildings Designer Update 7 onwards. This is a one way upgrade that offers additional capability, for an overview of this capability please see this playlist:&amp;nbsp;&lt;a style="font-family:inherit;" href="https://www.youtube.com/playlist?list=PL7jfe0_WZE1rk9JVA-jRTWO4B6E_uje1m"&gt;OpenBuildings Designer: Next Generation of Structural Elements - YouTube&lt;/a&gt;.&lt;br /&gt;Regardless of this decision there are a number of &lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/51023/configuration-changes-to-support-prostructures-interoperability" rel="noopener noreferrer" target="_blank"&gt;ProStructures folders and files&lt;/a&gt; that must be present in the Custom Configuration for the application to run successfully. (A standard installation of&amp;nbsp;OpenBuildings Designer Update 7 or later will include these.)&lt;span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;span style="font-family:inherit;"&gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Identify custom dataset content used in V8i, this could be cell libraries, DGNLIBs, XML files, etc. Ideally this content will be in separate folders and files from Bentley&amp;#39;s example dataset, however it may well be mixed in alongside delivered content. This will depend on how the V8i Workspace was organised.&lt;/span&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decide how the example dataset(s) will be used. There are two main options:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Use as is accepting that some of the example content will not suit your situation. This means that when a new dataset is released it can simply replace the existing version without affecting any customisations.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Take ownership of the example dataset, modifying it as needed. This requires both a different approach when a new dataset is released and an organised approach to the creation and storage of custom content. Custom content should always be contained in clearly identified files to enable any changed files from Bentley to be added/replaced/deleted. Changes introduced by new versions are listed in the &lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/51437/dataset-changes-in-the-latest-version-of-openbuildings-designer" rel="noopener noreferrer" target="_blank"&gt;dataset delta document&lt;/a&gt; and must be implemented manually.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decide where the dataset(s) will be located. There are two options:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;In the Custom Configuration (recommended). This is suitable for either of the options 1 or 2 above.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the local machine. This only applies if the delivered dataset is used unchanged, option 1 above, unless some external process is available to synchronize any customizations to the local copy.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="padding-left:30px;"&gt;These are discussed in more detail in&amp;nbsp;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/51041/dataset-strategies---local-or-network" rel="noopener noreferrer" target="_blank"&gt;Dataset Strategies - Local or Network&lt;/a&gt;.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;em&gt;Please note that the default location for the datasets&amp;nbsp;folder in a custom configuration changed after Update 7, this is discussed in&amp;nbsp;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/50875/configuring-the-datasets-root-folder-location"&gt;&lt;span lang="en-US"&gt;Configuring the Datasets Root Folder Location&lt;/span&gt;&lt;/a&gt;.&amp;nbsp;From Update 8 onwards the default location will be the Datasets folder in the Custom Configuration.&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Plan the implementation of access control via Windows File/Folder permissions to Organization, WorkSpace and WorkSet levels, the purpose of which is to ensure that only the responsible people are able to modify shared content:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Organization: Read-only to non-admin users.&lt;/li&gt;
&lt;li&gt;WorkSpaces: Write access to appropriate administrators, this may include BIM Coordinator type roles depending on organizational structure.&lt;/li&gt;
&lt;li&gt;WorkSets: Write access to all relevant users.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For initial design and testing of a new configuration we recommend using a local folder. Once the following steps including testing and validation are&amp;nbsp;be completed locally the entire Custom Configuration can be copied to a network location for further testing.&lt;/p&gt;
&lt;h1&gt;Step 2: Installing and Directing OpenBuildings Designer to a Network Location&lt;/h1&gt;
&lt;p&gt;To create a complete example configuration install OpenBuildings Designer in the normal manner, specifying the Custom Configuration path on your local machine that will be used initially. Doing this via the installer is described in&amp;nbsp;&lt;a href="https://www.youtube.com/watch?v=67Zi9_TDcNQ&amp;amp;list=PL7jfe0_WZE1qraPxafKm0hf_Eurbrss2c&amp;amp;index=1"&gt;Part 1 - Installing OpenBuildings Designer to a Network Location - YouTube&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The location of a custom configuration is stored in ConfigurationSetup.cfg on each machine. This is the only file that needs to be modified to redirect a machine to a custom configuration.&amp;nbsp;The configured location does not have to be available when OpenBuildings Designer is installed, the path will be ignored unless WorkSpace CFG files are present.&lt;/p&gt;
&lt;p&gt;If OpenBuildings Designer is already installed ConfigurationSetup.cfg can be updated as described in &lt;a href="/products/projectwise/content_management/w/wiki/53045/projectwise-drive" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - Configuration Tips : Should I edit ConfigurationSetup.cfg?&lt;/a&gt;&lt;/p&gt;
&lt;h1&gt;Step 3:&amp;nbsp;Populate the Custom Configuration&lt;/h1&gt;
&lt;p&gt;Creating the required folder structure is outlined in &lt;a href="https://www.youtube.com/watch?v=3KbLtNL-fns&amp;amp;list=PL7jfe0_WZE1qraPxafKm0hf_Eurbrss2c&amp;amp;index=2" rel="noopener noreferrer" target="_blank"&gt;Part 2 - Setting Up the Dataset and Organization Folders - YouTube&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Shown below is a typical example where the Datasets are located in the Custom Configuration under ...\OBD_Resources\Datasets\; one WorkSpace named ActiveProjects_365 is contained in the WorkSpaces folder.&lt;/p&gt;
&lt;table border="1" height="789"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td rowspan="3"&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635168631491v2.png" /&gt;&lt;/td&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;Datasets:&lt;/p&gt;
&lt;p&gt;Unless configured otherwise the Catalog User Interface will treat the active Dataset as the Organization level&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635169877994v3.png" /&gt;&lt;/p&gt;
&lt;p&gt;Organization level custom content may be stored here depending on the decision discussed above about use of delivered datasets.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;Organization:&lt;/p&gt;
&lt;p&gt;Unless configured otherwise the Organization subfolders contain shared platform or ProStructures content directed to by Standards.cfg and some &lt;span&gt;ProStructures&amp;nbsp;&lt;/span&gt;CFG files. Any content here will be available to all users unless configured otherwise.&lt;/p&gt;
&lt;p&gt;There are no other OpenBuildings specific folders.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;WorkSpaces:&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The Catalog&amp;nbsp;Editor will recognize the&amp;nbsp;WorkSpaces folder as the WorkSpaces&amp;nbsp;level.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Any content here will be available only to&amp;nbsp;users of the active WorkSpace.&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Step 4: Create WorkSets&lt;/h1&gt;
&lt;p&gt;The default WorkSet location will be in the WorkSets folder within the Custom Configuration. Live project data should always be separated from back office shared resources so WorkSet folders will need to be in the appropriate project data location. This is covered by &lt;a href="https://www.youtube.com/watch?v=_7FtTz64USg&amp;amp;list=PL7jfe0_WZE1qraPxafKm0hf_Eurbrss2c&amp;amp;index=5" rel="noopener noreferrer" target="_blank"&gt;Part 5 - Moving WorkSets to a Separate Drive - YouTube&lt;/a&gt;, the essential part of which is editing the _USTN_WORKSETROOT path in all WorkSpace CFG files. In this example that file is&amp;nbsp;ActiveProjects_365.cfg and it needs to contain a line defining&amp;nbsp;&lt;span&gt;_USTN_WORKSETROOT as pointing to the project data location, for example P:\ActiveProjects\OBD_AU_Demo\, e.g.:&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;em&gt;_USTN_WORKSETROOT = P:/ActiveProjects/$(_USTN_WORKSETNAME)/&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Create a new WorkSet by copying the appropriate regional WorkSet example,&amp;nbsp;for example BuildingTemplate_AU:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The&amp;nbsp;BuildingTemplate_AU folder should be copied to the project data location&lt;/li&gt;
&lt;li&gt;BuildingTemplate_AU.cfg should be copied to the WorkSets folder.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Both must be renamed with the new project name, folder and CFG file names must match since this is what links them together.&lt;/p&gt;
&lt;p&gt;Once the example WorkSet has been copied, but before adding any V8i content or making site specific changes to folder structures, test the new Custom Configuration. Review any messages displayed in the Message Center or elsewhere in the UI taking appropriate action to rectify them.&lt;/p&gt;
&lt;p&gt;At this stage also run the Dataset Validator&amp;nbsp;to ascertain the current state of the dataset.&amp;nbsp;It will be easier to fix any errors before custom content is added. (File &amp;gt; Dataset Tools &amp;gt; Validate. Help:&amp;nbsp;&lt;a href="https://docs.bentley.com/LiveContent/web/OpenBuildings%20Designer%20Help-v4/en/ARCH_DataGroupValidationDbox.html" rel="noopener noreferrer" target="_blank"&gt;DataGroup System Validator&lt;/a&gt;)&lt;/p&gt;
&lt;p&gt;&lt;img src="/resized-image/__size/640x480/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635240790157v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;An error free report at this point will confirm that the DataGroup Catalog is valid.&lt;/p&gt;
&lt;p&gt;To use the Verify Parts utility the WorkSet will need to contain some DGN files (File &amp;gt; Utilities &amp;gt; Part Utilities &amp;gt; Verify Parts. Help:&amp;nbsp;&lt;a href="https://docs.bentley.com/LiveContent/web/OpenBuildings%20Designer%20Help-v4/en/VerifyPartsDbox.html" rel="noopener noreferrer" target="_blank"&gt;Verify Part and Family&lt;/a&gt;)&lt;/p&gt;
&lt;p&gt;&lt;img src="/resized-image/__size/640x480/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635240858967v2.png" alt=" " /&gt;&lt;/p&gt;
&lt;h1&gt;Step 5: Add previous custom content&lt;/h1&gt;
&lt;p&gt;Check against dataset delta documents to see if any of the V8i files are now obsolete. For instance, since V8i curtain walls are superseded by a completely new CONNECT Edition tool, earlier content will not work with this new tool.&lt;/p&gt;
&lt;p&gt;Add V8i files in the appropriate locations at&amp;nbsp;&lt;span&gt;Organization, WorkSpace or WorkSet levels.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Run the Dataset Validator&amp;nbsp;again and fix any errors.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Test that the&amp;nbsp;content&amp;nbsp;is available in the UI,&amp;nbsp;i.e. in the&amp;nbsp;Catalog Editor and in the building and building systems element placement&amp;nbsp;tools.&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;Step 6: Modify WorkSet folder names or structure as appropriate to conform with organization standards&lt;/h1&gt;
&lt;p&gt;This step is put at the end of the process so a baseline is established before any site specific changes to&amp;nbsp;folder structures and files names are made. This narrows down the scope of any troubleshooting&amp;nbsp;that may be necessary; when CFG file are being edited even simple typos can cause errors.&lt;/p&gt;
&lt;p&gt;For example, in the example WorkSet CFG the default folder for design files is&amp;nbsp;called &amp;#39;Designs&amp;#39;:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635173318687v1.png" /&gt;&lt;/p&gt;
&lt;p&gt;This is defined by the lines:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635173558944v2.png" /&gt;&lt;/p&gt;
&lt;p&gt;If the folder location is correct, but the name &lt;span&gt;&amp;#39;Designs&amp;#39;&amp;nbsp;&lt;/span&gt;does not comply with project standards it can be renamed. The name &amp;#39;Designs&amp;#39; in the&amp;nbsp;&lt;span&gt;_USTN_WORKSETDGNS statement must then be changed to match the new folder name. (This has to be done by text editing since we do not have a UI for such changes.)&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;Step 7: Add any CONNECT Edition custom content (optional, can be done at a later stage)&lt;/h1&gt;
&lt;p&gt;New features in&amp;nbsp;&lt;span&gt;CONNECT Edition may benefit from customized content so this may be an appropriate point to add such&amp;nbsp;content.&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;&lt;span&gt;Step 8: Copy existing DGN files&lt;/span&gt;&lt;/h1&gt;
&lt;p&gt;&lt;span&gt;Existing DGN files and other WorkSet specific content should&amp;nbsp;be copied&amp;nbsp;into the appropriate folders in the CONNECT Edition WorkSet.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Any model files&amp;nbsp;that contain building elements (these are typically all of the 3D model files in a project) must be synchronised&amp;nbsp;with the new dataset using the&amp;nbsp;Schema Upgrade Utility. This can be done to all files in one go as explained in &lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479/upgrade-existing-elements-and-their-properties-to-the-current-catalog-schema" rel="noopener noreferrer" target="_blank"&gt;Schema Upgrade Utility&lt;/a&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The utility should&amp;nbsp;also be run on any existing&amp;nbsp;&amp;nbsp;BB_Floormaster.dgnlib. This may be successful, however as there have been significant changes&amp;nbsp;to the internal structure of&amp;nbsp;&amp;nbsp;BB_Floormaster.dgnlib since V8i we cannot&amp;nbsp;guarantee that&amp;nbsp;&amp;nbsp;BB_Floormaster.dgnlib content will be entirely&amp;nbsp;valid. It may be necessary to recreate the floor and Grid Systems content.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;2D files, generally&amp;nbsp;drawing&amp;nbsp;and sheets, do not contain building elements so do not need to be upgraded.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;If models contain Catalog Items or Parts that are not present in the new dataset, the DataGroup Transformation Utility can be used to missing custom properties to delivered properties, and the Part utilities can be used to verify and where necessary remap parts to elements (help: &lt;a href="https://docs.bentley.com/LiveContent/web/OpenBuildings%20Designer%20Help-v4/en/DataGroupTransformationServicesDialogBox.html" rel="noopener noreferrer" target="_blank"&gt;DataGroup Transformation Utility&lt;/a&gt;):&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;img src="/resized-image/__size/640x480/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635241392109v4.png" alt=" " /&gt; &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/03548.NewLogo.png"&gt;&lt;img style="border-width:0px;" alt=" " height="60" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" width="189" /&gt;&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Custom Configuration, CONNECT Edition, v8i, OpenBuildings Designer, Migration, AECOsim Building Designer, Configuration&lt;/div&gt;
</description></item><item><title>Migrating custom content from AECOsim Building Designer SS6 to a current OpenBuildings Designer version</title><link>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version/revision/11</link><pubDate>Mon, 25 Oct 2021 18:54:48 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:74ea833a-2c67-4860-90b8-05cf1fd96ae0</guid><dc:creator>Marc Thomas</dc:creator><comments>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version#comments</comments><description>Revision 11 posted to OpenBuildings | AECOsim | Speedikon Wiki by Marc Thomas on 10/25/2021 6:54:48 PM&lt;br /&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;" width="30%"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;OpenBuildings Designer&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;CONNECT Edition&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Datasets and content&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Migration/Upgrade&lt;span&gt; &lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;This article discusses the migration of dataset content.&lt;/p&gt;
&lt;p&gt;Migration of a V8i Workspace to a CONNECT Edition Configuration is&amp;nbsp;covered by training course&amp;nbsp;&lt;a href="https://learn.bentley.com/app/Public/ViewLearningPathDetails?lpId=113058&amp;amp;aftkn=5527c519-bbc7-4890-9a2e-063edc9da5c0" rel="noopener noreferrer" target="_blank"&gt;BIM Management 301: Installation and Upgrade Guide&lt;/a&gt;, we recommend viewing this training and downloading the course workbook prior to embarking on a migration process.&amp;nbsp;This article will refer to some exercises contained in this training course that cover the creation of CONNECT WorkSpaces and WorkSets. We have also published a playlist of YouTube videos covering the same material:&amp;nbsp;&lt;a href="https://www.youtube.com/playlist?list=PL7jfe0_WZE1qraPxafKm0hf_Eurbrss2c" rel="noopener noreferrer" target="_blank"&gt;BIM Management 301: Installation and Upgrade Guide - YouTube&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;A key recommendation is that any &lt;span&gt;CONNECT Edition Configuration should be in a separate folder structure&amp;nbsp;to any existing V8i Workspace; their folder structures&amp;nbsp;and configuration files are significantly different. Using a separate&amp;nbsp;location allows any new Configuration to be tested without affecting&amp;nbsp;an active production Workspace.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The migration of delivered dataset content from SS6 to CONNECT Edition is relatively straightforward as the dataset changes have been minimised for most datasets. Please note the exception to this: due to major changes in British standards the V8i UK/GB dataset is not directly compatible with the CONNECT versions. Please see &lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/35923/connect-edition---british-dataset-migration" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - British Dataset migration&lt;/a&gt;&amp;nbsp;for full details.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Step 1: Preparation&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Identify a separate location for the CONNECT Edition configuration, this must be in a separate location to the active V8i Workspace, even if only in a different root folder on a network share.&lt;/span&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Identify custom dataset content used in V8i, this could be cell libraries, DGNLIBs, XML files, etc. Ideally this content will be in separate folders and files from Bentley&amp;#39;s example dataset, however it may well be&amp;nbsp; mixed in alongside delivered content. This will depend on how the V8i Workspace was organised.&lt;/span&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decide how the example dataset(s) will be used. There are two main options.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Use as is accepting that some of the example content will not suit your situation. This means that when a new dataset is released it can simply replace the existing version without affecting any customisations.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Take ownership of the example dataset, modifying it as needed. This requires both a different approach when a new dataset is released and an organised approach to the creation and storage of custom content. Custom content should always be contained in clearly identified files to enable any changed files from Bentley to be added/replaced/deleted. Changes introduced by new versions are listed in the dataset delta document and must be implemented manually.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decide where the dataset(s) will be located. There are two options.*&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;In the Custom Configuration (recommended). This is suitable for either of the options 1 or 2 above.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the local machine. This only applies if the delivered dataset is used unchanged, option 1 above, unless some external process is available to synchronize any customizations to the local copy.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="padding-left:30px;"&gt;These are discussed in more detail in&amp;nbsp;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/51041/dataset-strategies---local-or-network" rel="noopener noreferrer" target="_blank"&gt;Dataset Strategies - Local or Network&lt;/a&gt;.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;em&gt;Please note that the default location for the datasets&amp;nbsp;folder in a custom configuration changed after Update 7, this is discussed in&amp;nbsp;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/50875/configuring-the-datasets-root-folder-location"&gt;&lt;span lang="en-US"&gt;Configuring the Datasets Root Folder Location&lt;/span&gt;&lt;/a&gt;.&amp;nbsp;From Update 8 onwards the default location will be the Datasets folder in the Custom Configuration.&lt;/em&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:inherit;"&gt;&lt;/span&gt;*Note: &lt;a href="/products/projectwise/content_management/w/wiki/53045/projectwise-drive" rel="noopener noreferrer" target="_blank"&gt;ProjectWise 365 Drive&lt;/a&gt; will become an option for sharing configurations and synchronising their content to local machines&amp;nbsp;when additional features are released late in 2021.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Plan the implementation of access control via Windows File/Folder permissions to Organization, WorkSpace and WorkSet levels, the purpose of which is to ensure that only the responsible people are able to modify shared content:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Organization: Read-only to non-admin users.&lt;/li&gt;
&lt;li&gt;WorkSpaces: Write access to appropriate administrators, this may include BIM Coordinator type roles depending on organizational structure.&lt;/li&gt;
&lt;li&gt;WorkSets: Write access to all relevant users.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h1&gt;Step 2: Directing OpenBuildings Designer to a Network Location&lt;/h1&gt;
&lt;p&gt;This is described in Exercise 1: Installing OpenBuildings Designer Configured to a Network Location.&lt;/p&gt;
&lt;p&gt;The location of a custom configuration is stored in ConfigurationSetup.cfg on each machine. This is the only file that needs to be modified to redirect a machine to a custom configuration.&amp;nbsp;The configured location does not have to be available when OpenBuildings Designer is installed, the path will be ignored unless WorkSpace CFG files are present.&lt;/p&gt;
&lt;p&gt;If OpenBuildings Designer is already installed ConfigurationSetup.cfg can be updated as described in &lt;a href="/products/projectwise/content_management/w/wiki/53045/projectwise-drive" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - Configuration Tips : Should I edit ConfigurationSetup.cfg?&lt;/a&gt;&lt;/p&gt;
&lt;h1&gt;Step 3:&amp;nbsp;Populate the Custom Configuration&lt;/h1&gt;
&lt;p&gt;Creating the required folder structure is outlined in Exercise 2: Setting Up the Organization and WorkSpace Folders.&lt;/p&gt;
&lt;p&gt;This is a typical example where the Datasets are located in the Custom Configuration under ...\OBD_Resources\Datasets\; one WorkSpace named ActiveProjects_365 is contained in the WorkSpaces folder.&lt;/p&gt;
&lt;table border="1" height="789"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td rowspan="3"&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635168631491v2.png" /&gt;&lt;/td&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;Datasets:&lt;/p&gt;
&lt;p&gt;Unless configured otherwise the Catalog User Interface will treat the active Dataset as the Organisation level&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635169877994v3.png" /&gt;&lt;/p&gt;
&lt;p&gt;Organization level Custom content may be stored here depending on the decision discussed above about use of delivered datasets.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;Organization:&lt;/p&gt;
&lt;p&gt;Unless configured otherwise the Organization subfolders contain shared platform or ProStructures content directed to by Standards.cfg and some &lt;span&gt;ProStructures&amp;nbsp;&lt;/span&gt;CFG files. Any content here will be available to all users unless configured otherwise.&lt;/p&gt;
&lt;p&gt;There are no OpenBuildings specific folders.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;WorkSpaces:&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The Catalog User Interface will recognize the&amp;nbsp;WorkSpaces folder as the WorkSpaces&amp;nbsp;level.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Any content here will be available to&amp;nbsp;only to&amp;nbsp;users of the active WorkSpace.&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Step 4: Create WorkSets&lt;/h1&gt;
&lt;p&gt;The default WorkSet location will be in the WorkSets folder within the Custom Configuration. Obviously project data is not a sub-set of an application. WorkSet folders will need to be in the appropriate project data location. This is covered by&amp;nbsp;Exercise 5: Moving the WorkSets to a Separate Drive, the essential part of which is editing the _USTN_WORKSETROOT path in all WorkSpace CFG files. In this example that file is&amp;nbsp;ActiveProjects_365.cfg and it needs to contain a line defining&amp;nbsp;&lt;span&gt;_USTN_WORKSETROOT as pointing to the project data location, for example P:\ActiveProjects\OBD_AU_Demo\, e.g.:&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;em&gt;_USTN_WORKSETROOT = P:/ActiveProjects/$(_USTN_WORKSETNAME)/&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Create a new WorkSet by copying the appropriate regional WorkSet example, e.g.&amp;nbsp;BuildingTemplate_AU.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The&amp;nbsp;BuildingTemplate_AU folder should be copied to the project data location&lt;/li&gt;
&lt;li&gt;BuildingTemplate_AU.cfg should be copied to the WorkSets folder.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Both must be renamed with the new project name, folder and CFG file names must match, this is what links them together.&lt;/p&gt;
&lt;p&gt;Once the example WorkSet has been copied, but before adding any V8i content or making site specific changes to folder structures, test the new Custom Configuration. Review any messages displayed in the Message Center or elsewhere in the UI taking appropriate action to rectify them.&lt;/p&gt;
&lt;p&gt;At this point also run the Dataset Validator (File &amp;gt; Dataset Tools &amp;gt; Validate) and Verify Parts (File &amp;gt; Utilities &amp;gt; Part Utilities &amp;gt; Verify Parts) to ascertain the current state of the dataset.&amp;nbsp;It will be easier to fix errors at this point before custom content is added.&lt;/p&gt;
&lt;h1&gt;Step 5: Add previous custom content.&lt;/h1&gt;
&lt;p&gt;Check against dataset delta documents to see if any of the V8i files are now obsolete. For instance V8i curtain walls are superseded by the CONNECT Edition tools, earlier content will not work with the new tool.&lt;/p&gt;
&lt;p&gt;Add V8i files in the appropriate locations at&amp;nbsp;&lt;span&gt;Organization, WorkSpace or WorkSet levels.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Run the Dataset Validator&amp;nbsp;again and fix any errors.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Test that the&amp;nbsp;content&amp;nbsp;is available in the UI,&amp;nbsp;i.e. in the&amp;nbsp;Catalog Editor and in the building tools.&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;Step 6: Modify WorkSet folder names or structure as appropriate to conform with organization standards&lt;/h1&gt;
&lt;p&gt;This step is put at the end of the process so a baseline is established before any site specific changes to&amp;nbsp;folder structures and files names are made. This narrows down the scope of any troubleshooting&amp;nbsp;that may be necessary; when CFG file are being edited even simple typos can cause errors.&lt;/p&gt;
&lt;p&gt;For example, in the example WorkSet CFG the default folder for design files is&amp;nbsp;called &amp;#39;Designs&amp;#39;:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635173318687v1.png" /&gt;&lt;/p&gt;
&lt;p&gt;This is defined by the lines:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635173558944v2.png" /&gt;&lt;/p&gt;
&lt;p&gt;If the folder location is correct, but the name &lt;span&gt;&amp;#39;Designs&amp;#39;&amp;nbsp;&lt;/span&gt;does not comply with project standards it can be renamed. The name &amp;#39;Designs&amp;#39; in the&amp;nbsp;&lt;span&gt;_USTN_WORKSETDGNS statement must then be changed to match the new folder name. (This has to be done by text editing we do not have a UI for such changes.)&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;Step 7: Add any CONNECT Edition custom content (optional, can be done at a later stage)&lt;/h1&gt;
&lt;p&gt;New features in&amp;nbsp;&lt;span&gt;CONNECT Edition may benefit form customized content this may be an appropriate point to add such&amp;nbsp;content.&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;&lt;span&gt;Step 8: Copy existing DGN files&lt;/span&gt;&lt;/h1&gt;
&lt;p&gt;&lt;span&gt;Existing DGN files and other WorkSet specific content should&amp;nbsp;be copied&amp;nbsp;into the appropriate folders in the CONNECT Edition WorkSet.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Any model files&amp;nbsp;that contain building elements, (these are typically all of the 3D model files in a project) must be synchronised&amp;nbsp;with the new dataset using the&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479/upgrade-existing-elements-and-their-properties-to-the-current-catalog-schema" rel="noopener noreferrer" target="_blank"&gt;&amp;nbsp;Schema Upgrade Utility&lt;/a&gt;. This can be done to all files in one go as explained in the&amp;nbsp;linked article. &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The utility should&amp;nbsp;also be run on any existing&amp;nbsp;&amp;nbsp;BB_Floormaster.dgnlib. This may be successful, however as there have been significant changes&amp;nbsp;to the internal structure of&amp;nbsp;&amp;nbsp;BB_Floormaster.dgnlib since V8i we cannot&amp;nbsp;guarantee that&amp;nbsp;&amp;nbsp;BB_Floormaster.dgnlib content will be entirely&amp;nbsp;valid. It may be necessary to recreate the floor and Grid Systems content.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;2D files, generally&amp;nbsp;drawing&amp;nbsp;and sheets, do not contain building elements so do not need to be upgraded.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;If models contain Catalog Items or Parts that are not present in the new dataset the DataGroup Transformation Utility can be used to remap properties and the Part utilities can be used to verify and where necessary remap parts to elements.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/03548.NewLogo.png"&gt;&lt;img style="border-width:0px;" alt=" " height="60" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" width="189" /&gt;&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Custom Configuration, CONNECT Edition, v8i, OpenBuildings Designer, Migration, AECOsim Building Designer, Configuration&lt;/div&gt;
</description></item><item><title>Migrating custom content from AECOsim Building Designer SS6 to a current OpenBuildings Designer version</title><link>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version/revision/10</link><pubDate>Mon, 25 Oct 2021 15:51:45 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:74ea833a-2c67-4860-90b8-05cf1fd96ae0</guid><dc:creator>Marc Thomas</dc:creator><comments>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version#comments</comments><description>Revision 10 posted to OpenBuildings | AECOsim | Speedikon Wiki by Marc Thomas on 10/25/2021 3:51:45 PM&lt;br /&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;" width="30%"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;OpenBuildings Designer&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;CONNECT Edition&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Datasets and content&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Migration/Upgrade&lt;span&gt; &lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;This article discusses the migration of dataset content.&lt;/p&gt;
&lt;p&gt;Migration of a V8i Workspace to a CONNECT Edition Configuration is&amp;nbsp;covered by training course&amp;nbsp;&lt;a href="https://learn.bentley.com/app/Public/ViewLearningPathDetails?lpId=113058&amp;amp;aftkn=5527c519-bbc7-4890-9a2e-063edc9da5c0" rel="noopener noreferrer" target="_blank"&gt;BIM Management 301: Installation and Upgrade Guide&lt;/a&gt;, we recommend viewing this training and downloading the course workbook prior to embarking on a migration process.&amp;nbsp;This article will refer to some exercises contained in this training course that cover the creation of CONNECT WorkSpaces and WorkSets.&lt;/p&gt;
&lt;p&gt;A key recommendation is that any &lt;span&gt;CONNECT Edition Configuration should be in a separate folder structure&amp;nbsp;to any existing V8i Workspace; their folder structures&amp;nbsp;and configuration files are significantly different. Using a separate&amp;nbsp;location allows any new Configuration to be tested without affecting&amp;nbsp;an active production Workspace.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The migration of delivered dataset content from SS6 to CONNECT Edition is relatively straightforward as the dataset changes have been minimised for most datasets. Please note the exception to this: due to major changes in British standards the V8i UK/GB dataset is not directly compatible with the CONNECT versions. Please see &lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/35923/connect-edition---british-dataset-migration" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - British Dataset migration&lt;/a&gt;&amp;nbsp;for full details.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Step 1: Preparation&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Identify a separate location for the CONNECT Edition configuration, this must be in a separate location to the active V8i Workspace, even if only in a different root folder on a network share.&lt;/span&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Identify custom dataset content used in V8i, this could be cell libraries, DGNLIBs, XML files, etc. Ideally this content will be in separate folders and files from Bentley&amp;#39;s example dataset, however it may well be&amp;nbsp; mixed in alongside delivered content. This will depend on how the V8i Workspace was organised.&lt;/span&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decide how the example dataset(s) will be used. There are two main options.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Use as is accepting that some of the example content will not suit your situation. This means that when a new dataset is released it can simply replace the existing version without affecting any customisations.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Take ownership of the example dataset, modifying it as needed. This requires both a different approach when a new dataset is released and an organised approach to the creation and storage of custom content. Custom content should always be contained in clearly identified files to enable any changed files from Bentley to be added/replaced/deleted. Changes introduced by new versions are listed in the dataset delta document and must be implemented manually.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decide where the dataset(s) will be located. There are two options.*&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;In the Custom Configuration (recommended). This is suitable for either of the options 1 or 2 above.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the local machine. This only applies if the delivered dataset is used unchanged, option 1 above, unless some external process is available to synchronize any customizations to the local copy.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="padding-left:30px;"&gt;These are discussed in more detail in&amp;nbsp;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/51041/dataset-strategies---local-or-network" rel="noopener noreferrer" target="_blank"&gt;Dataset Strategies - Local or Network&lt;/a&gt;.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;em&gt;Please note that the default location for the datasets&amp;nbsp;folder in a custom configuration changed after Update 7, this is discussed in&amp;nbsp;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/50875/configuring-the-datasets-root-folder-location"&gt;&lt;span lang="en-US"&gt;Configuring the Datasets Root Folder Location&lt;/span&gt;&lt;/a&gt;.&amp;nbsp;From Update 8 onwards the default location will be the Datasets folder in the Custom Configuration.&lt;/em&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:inherit;"&gt;&lt;/span&gt;*Note: &lt;a href="/products/projectwise/content_management/w/wiki/53045/projectwise-drive" rel="noopener noreferrer" target="_blank"&gt;ProjectWise 365 Drive&lt;/a&gt; will become an option for sharing configurations and synchronising their content to local machines&amp;nbsp;when additional features are released late in 2021.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Plan the implementation of access control via Windows File/Folder permissions to Organization, WorkSpace and WorkSet levels, the purpose of which is to ensure that only the responsible people are able to modify shared content:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Organization: Read-only to non-admin users.&lt;/li&gt;
&lt;li&gt;WorkSpaces: Write access to appropriate administrators, this may include BIM Coordinator type roles depending on organizational structure.&lt;/li&gt;
&lt;li&gt;WorkSets: Write access to all relevant users.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h1&gt;Step 2: Directing OpenBuildings Designer to a Network Location&lt;/h1&gt;
&lt;p&gt;This is described in Exercise 1: Installing OpenBuildings Designer Configured to a Network Location.&lt;/p&gt;
&lt;p&gt;The location of a custom configuration is stored in ConfigurationSetup.cfg on each machine. This is the only file that needs to be modified to redirect a machine to a custom configuration.&amp;nbsp;The configured location does not have to be available when OpenBuildings Designer is installed, the path will be ignored unless WorkSpace CFG files are present.&lt;/p&gt;
&lt;p&gt;If OpenBuildings Designer is already installed ConfigurationSetup.cfg can be updated as described in &lt;a href="/products/projectwise/content_management/w/wiki/53045/projectwise-drive" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - Configuration Tips : Should I edit ConfigurationSetup.cfg?&lt;/a&gt;&lt;/p&gt;
&lt;h1&gt;Step 3:&amp;nbsp;Populate the Custom Configuration&lt;/h1&gt;
&lt;p&gt;Creating the required folder structure is outlined in Exercise 2: Setting Up the Organization and WorkSpace Folders.&lt;/p&gt;
&lt;p&gt;This is a typical example where the Datasets are located in the Custom Configuration under ...\OBD_Resources\Datasets\; one WorkSpace named ActiveProjects_365 is contained in the WorkSpaces folder.&lt;/p&gt;
&lt;table border="1" height="789"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td rowspan="3"&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635168631491v2.png" /&gt;&lt;/td&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;Datasets:&lt;/p&gt;
&lt;p&gt;Unless configured otherwise the Catalog User Interface will treat the active Dataset as the Organisation level&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635169877994v3.png" /&gt;&lt;/p&gt;
&lt;p&gt;Organization level Custom content may be stored here depending on the decision discussed above about use of delivered datasets.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;Organization:&lt;/p&gt;
&lt;p&gt;Unless configured otherwise the Organization subfolders contain shared platform or ProStructures content directed to by Standards.cfg and some &lt;span&gt;ProStructures&amp;nbsp;&lt;/span&gt;CFG files. Any content here will be available to all users unless configured otherwise.&lt;/p&gt;
&lt;p&gt;There are no OpenBuildings specific folders.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;WorkSpaces:&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The Catalog User Interface will recognize the&amp;nbsp;WorkSpaces folder as the WorkSpaces&amp;nbsp;level.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Any content here will be available to&amp;nbsp;only to&amp;nbsp;users of the active WorkSpace.&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Step 4: Create WorkSets&lt;/h1&gt;
&lt;p&gt;The default WorkSet location will be in the WorkSets folder within the Custom Configuration. Obviously project data is not a sub-set of an application. WorkSet folders will need to be in the appropriate project data location. This is covered by&amp;nbsp;Exercise 5: Moving the WorkSets to a Separate Drive, the essential part of which is editing the _USTN_WORKSETROOT path in all WorkSpace CFG files. In this example that file is&amp;nbsp;ActiveProjects_365.cfg and it needs to contain a line defining&amp;nbsp;&lt;span&gt;_USTN_WORKSETROOT as pointing to the project data location, for example P:\ActiveProjects\OBD_AU_Demo\, e.g.:&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;em&gt;_USTN_WORKSETROOT = P:/ActiveProjects/$(_USTN_WORKSETNAME)/&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Create a new WorkSet by copying the appropriate regional WorkSet example, e.g.&amp;nbsp;BuildingTemplate_AU.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The&amp;nbsp;BuildingTemplate_AU folder should be copied to the project data location&lt;/li&gt;
&lt;li&gt;BuildingTemplate_AU.cfg should be copied to the WorkSets folder.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Both must be renamed with the new project name, folder and CFG file names must match, this is what links them together.&lt;/p&gt;
&lt;p&gt;Once the example WorkSet has been copied, but before adding any V8i content or making site specific changes to folder structures, test the new Custom Configuration. Review any messages displayed in the Message Center or elsewhere in the UI taking appropriate action to rectify them.&lt;/p&gt;
&lt;p&gt;At this point also run the Dataset Validator (File &amp;gt; Dataset Tools &amp;gt; Validate) and Verify Parts (File &amp;gt; Utilities &amp;gt; Part Utilities &amp;gt; Verify Parts) to ascertain the current state of the dataset.&amp;nbsp;It will be easier to fix errors at this point before custom content is added.&lt;/p&gt;
&lt;h1&gt;Step 5: Add previous custom content.&lt;/h1&gt;
&lt;p&gt;Check against dataset delta documents to see if any of the V8i files are now obsolete. For instance V8i curtain walls are superseded by the CONNECT Edition tools, earlier content will not work with the new tool.&lt;/p&gt;
&lt;p&gt;Add V8i files in the appropriate locations at&amp;nbsp;&lt;span&gt;Organization, WorkSpace or WorkSet levels.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Run the Dataset Validator&amp;nbsp;again and fix any errors.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Test that the&amp;nbsp;content&amp;nbsp;is available in the UI,&amp;nbsp;i.e. in the&amp;nbsp;Catalog Editor and in the building tools.&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;Step 6: Modify WorkSet folder names or structure as appropriate to conform with organization standards&lt;/h1&gt;
&lt;p&gt;This step is put at the end of the process so a baseline is established before any site specific changes to&amp;nbsp;folder structures and files names are made. This narrows down the scope of any troubleshooting&amp;nbsp;that may be necessary; when CFG file are being edited even simple typos can cause errors.&lt;/p&gt;
&lt;p&gt;For example, in the example WorkSet CFG the default folder for design files is&amp;nbsp;called &amp;#39;Designs&amp;#39;:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635173318687v1.png" /&gt;&lt;/p&gt;
&lt;p&gt;This is defined by the lines:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635173558944v2.png" /&gt;&lt;/p&gt;
&lt;p&gt;If the folder location is correct, but the name &lt;span&gt;&amp;#39;Designs&amp;#39;&amp;nbsp;&lt;/span&gt;does not comply with project standards it can be renamed. The name &amp;#39;Designs&amp;#39; in the&amp;nbsp;&lt;span&gt;_USTN_WORKSETDGNS statement must then be changed to match the new folder name. (This has to be done by text editing we do not have a UI for such changes.)&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;Step 7: Add any CONNECT Edition custom content (optional, can be done at a later stage)&lt;/h1&gt;
&lt;p&gt;New features in&amp;nbsp;&lt;span&gt;CONNECT Edition may benefit form customized content this may be an appropriate point to add such&amp;nbsp;content.&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;&lt;span&gt;Step 8: Copy existing DGN files&lt;/span&gt;&lt;/h1&gt;
&lt;p&gt;&lt;span&gt;Existing DGN files and other WorkSet specific content should&amp;nbsp;be copied&amp;nbsp;into the appropriate folders in the CONNECT Edition WorkSet.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Any model files&amp;nbsp;that contain building elements, (these are typically all of the 3D model files in a project) must be synchronised&amp;nbsp;with the new dataset using the&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479/upgrade-existing-elements-and-their-properties-to-the-current-catalog-schema" rel="noopener noreferrer" target="_blank"&gt;&amp;nbsp;Schema Upgrade Utility&lt;/a&gt;. This can be done to all files in one go as explained in the&amp;nbsp;linked article. &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The utility should&amp;nbsp;also be run on any existing&amp;nbsp;&amp;nbsp;BB_Floormaster.dgnlib. This may be successful, however as there have been significant changes&amp;nbsp;to the internal structure of&amp;nbsp;&amp;nbsp;BB_Floormaster.dgnlib since V8i we cannot&amp;nbsp;guarantee that&amp;nbsp;&amp;nbsp;BB_Floormaster.dgnlib content will be entirely&amp;nbsp;valid. It may be necessary to recreate the floor and Grid Systems content.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;2D files, generally&amp;nbsp;drawing&amp;nbsp;and sheets, do not contain building elements so do not need to be upgraded.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;If models contain Catalog Items or Parts that are not present in the new dataset the DataGroup Transformation Utility can be used to remap properties and the Part utilities can be used to verify and where necessary remap parts to elements.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/03548.NewLogo.png"&gt;&lt;img style="border-width:0px;" alt=" " height="60" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" width="189" /&gt;&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Draft - Content is WiP&lt;/div&gt;
</description></item><item><title>Migrating custom content from AECOsim Building Designer SS6 to a current OpenBuildings Designer version</title><link>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version/revision/9</link><pubDate>Mon, 25 Oct 2021 15:36:14 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:74ea833a-2c67-4860-90b8-05cf1fd96ae0</guid><dc:creator>Marc Thomas</dc:creator><comments>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version#comments</comments><description>Revision 9 posted to OpenBuildings | AECOsim | Speedikon Wiki by Marc Thomas on 10/25/2021 3:36:14 PM&lt;br /&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;" width="30%"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;OpenBuildings Designer&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;CONNECT Edition&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Datasets and content&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Migration/Upgrade&lt;span&gt; &lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;This article discusses the migration of dataset content.&lt;/p&gt;
&lt;p&gt;Migration of a V8i Workspace to a CONNECT Edition Configuration is&amp;nbsp;covered by training course&amp;nbsp;&lt;a href="https://learn.bentley.com/app/Public/ViewLearningPathDetails?lpId=113058&amp;amp;aftkn=5527c519-bbc7-4890-9a2e-063edc9da5c0" rel="noopener noreferrer" target="_blank"&gt;BIM Management 301: Installation and Upgrade Guide&lt;/a&gt;, we recommend viewing this training and downloading the course workbook prior to embarking on a migration process.&amp;nbsp;This article will refer to some exercises contained in this training course that cover the creation of CONNECT WorkSpaces and WorkSets.&lt;/p&gt;
&lt;p&gt;A key recommendation is that any &lt;span&gt;CONNECT Edition Configuration should be in a separate folder structure&amp;nbsp;to any existing V8i Workspace; their folder structures&amp;nbsp;and configuration files are significantly different. Using a separate&amp;nbsp;location allows any new Configuration to be tested without affecting&amp;nbsp;an active production Workspace.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The migration of delivered dataset content from SS6 to CONNECT Edition is relatively straightforward as the dataset changes have been minimised for most datasets. Please note the exception to this: due to major changes in British standards the V8i UK/GB dataset is not directly compatible with the CONNECT versions. Please see &lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/35923/connect-edition---british-dataset-migration" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - British Dataset migration&lt;/a&gt;&amp;nbsp;for full details.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Step 1: Preparation&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Identify a separate location for the CONNECT Edition configuration, this must be in a separate location to the active V8i Workspace, even if only in a different root folder on a network share.&lt;/span&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Identify custom dataset content used in V8i, this could be cell libraries, DGNLIBs, XML files, etc. Ideally this content will be in separate folders and files from Bentley&amp;#39;s example dataset, however it may well be&amp;nbsp; mixed in alongside delivered content. This will depend on how the V8i Workspace was organised.&lt;/span&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decide how the example dataset(s) will be used. There are two main options.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Use as is accepting that some of the example content will not suit your situation. This means that when a new dataset is released it can simply replace the existing version without affecting any customisations.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Take ownership of the example dataset, modifying it as needed. This requires both a different approach when a new dataset is released and an organised approach to the creation and storage of custom content. Custom content should always be contained in clearly identified files to enable any changed files from Bentley to be added/replaced/deleted. Changes introduced by new versions are listed in the dataset delta document and must be implemented manually.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decide where the dataset(s) will be located. There are two options.*&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;In the Custom Configuration (recommended). This is suitable for either of the options 1 or 2 above.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the local machine. This only applies if the delivered dataset is used unchanged, option 1 above, unless some external process is available to synchronize any customizations to the local copy.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="padding-left:30px;"&gt;These are discussed in more detail in&amp;nbsp;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/51041/dataset-strategies---local-or-network" rel="noopener noreferrer" target="_blank"&gt;Dataset Strategies - Local or Network&lt;/a&gt;.&amp;nbsp; If datasets on a local machine are preferred please refer to&amp;nbsp;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/50875/configuring-the-datasets-root-folder-location"&gt;&lt;span lang="en-US"&gt;Configuring the Datasets Root Folder Location&lt;/span&gt;&lt;/a&gt;.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:inherit;"&gt;&lt;/span&gt;*Note: &lt;a href="/products/projectwise/content_management/w/wiki/53045/projectwise-drive" rel="noopener noreferrer" target="_blank"&gt;ProjectWise 365 Drive&lt;/a&gt; will become an option for sharing configurations and synchronising their content to local machines&amp;nbsp;when additional features are released late in 2021.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Plan the implementation of access control via Windows File/Folder permissions to Organization, WorkSpace and WorkSet levels, the purpose of which is to ensure that only the responsible people are able to modify shared content:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Organization: Read-only to non-admin users.&lt;/li&gt;
&lt;li&gt;WorkSpaces: Write access to appropriate administrators, this may include BIM Coordinator type roles depending on organizational structure.&lt;/li&gt;
&lt;li&gt;WorkSets: Write access to all relevant users.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h1&gt;Step 2: Directing OpenBuildings Designer to a Network Location&lt;/h1&gt;
&lt;p&gt;This is described in Exercise 1: Installing OpenBuildings Designer Configured to a Network Location.&lt;/p&gt;
&lt;p&gt;The location of a custom configuration is stored in ConfigurationSetup.cfg on each machine. This is the only file that needs to be modified to redirect a machine to a custom configuration.&amp;nbsp;The configured location does not have to be available when OpenBuildings Designer is installed, the path will be ignored unless WorkSpace CFG files are present.&lt;/p&gt;
&lt;p&gt;If OpenBuildings Designer is already installed ConfigurationSetup.cfg can be updated as described in &lt;a href="/products/projectwise/content_management/w/wiki/53045/projectwise-drive" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - Configuration Tips : Should I edit ConfigurationSetup.cfg?&lt;/a&gt;&lt;/p&gt;
&lt;h1&gt;Step 3:&amp;nbsp;Populate the Custom Configuration&lt;/h1&gt;
&lt;p&gt;Creating the required folder structure is outlined in Exercise 2: Setting Up the Organization and WorkSpace Folders.&lt;/p&gt;
&lt;p&gt;This is a typical example where the Datasets are located in the Custom Configuration under ...\OBD_Resources\Datasets\; one WorkSpace named ActiveProjects_365 is contained in the WorkSpaces folder.&lt;/p&gt;
&lt;table border="1" height="789"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td rowspan="3"&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635168631491v2.png" /&gt;&lt;/td&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;Datasets:&lt;/p&gt;
&lt;p&gt;Unless configured otherwise the Catalog User Interface will treat the active Dataset as the Organisation level&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635169877994v3.png" /&gt;&lt;/p&gt;
&lt;p&gt;Organization level Custom content may be stored here depending on the decision discussed above about use of delivered datasets.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;Organization:&lt;/p&gt;
&lt;p&gt;Unless configured otherwise the Organization subfolders contain shared platform or ProStructures content directed to by Standards.cfg and some &lt;span&gt;ProStructures&amp;nbsp;&lt;/span&gt;CFG files. Any content here will be available to all users unless configured otherwise.&lt;/p&gt;
&lt;p&gt;There are no OpenBuildings specific folders.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;WorkSpaces:&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The Catalog User Interface will recognize the&amp;nbsp;WorkSpaces folder as the WorkSpaces&amp;nbsp;level.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Any content here will be available to&amp;nbsp;only to&amp;nbsp;users of the active WorkSpace.&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Step 4: Create WorkSets&lt;/h1&gt;
&lt;p&gt;The default WorkSet location will be in the WorkSets folder within the Custom Configuration. Obviously project data is not a sub-set of an application. WorkSet folders will need to be in the appropriate project data location. This is covered by&amp;nbsp;Exercise 5: Moving the WorkSets to a Separate Drive, the essential part of which is editing the _USTN_WORKSETROOT path in all WorkSpace CFG files. In this example that file is&amp;nbsp;ActiveProjects_365.cfg and it needs to contain a line defining&amp;nbsp;&lt;span&gt;_USTN_WORKSETROOT as pointing to the project data location, for example P:\ActiveProjects\OBD_AU_Demo\, e.g.:&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;em&gt;_USTN_WORKSETROOT = P:/ActiveProjects/$(_USTN_WORKSETNAME)/&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Create a new WorkSet by copying the appropriate regional WorkSet example, e.g.&amp;nbsp;BuildingTemplate_AU.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The&amp;nbsp;BuildingTemplate_AU folder should be copied to the project data location&lt;/li&gt;
&lt;li&gt;BuildingTemplate_AU.cfg should be copied to the WorkSets folder.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Both must be renamed with the new project name, folder and CFG file names must match, this is what links them together.&lt;/p&gt;
&lt;p&gt;Once the example WorkSet has been copied, but before adding any V8i content or making site specific changes to folder structures, test the new Custom Configuration. Review any messages displayed in the Message Center or elsewhere in the UI taking appropriate action to rectify them.&lt;/p&gt;
&lt;p&gt;At this point also run the Dataset Validator (File &amp;gt; Dataset Tools &amp;gt; Validate) and Verify Parts (File &amp;gt; Utilities &amp;gt; Part Utilities &amp;gt; Verify Parts) to ascertain the current state of the dataset.&amp;nbsp;It will be easier to fix errors at this point before custom content is added.&lt;/p&gt;
&lt;h1&gt;Step 5: Add previous custom content.&lt;/h1&gt;
&lt;p&gt;Check against dataset delta documents to see if any of the V8i files are now obsolete. For instance V8i curtain walls are superseded by the CONNECT Edition tools, earlier content will not work with the new tool.&lt;/p&gt;
&lt;p&gt;Add V8i files in the appropriate locations at&amp;nbsp;&lt;span&gt;Organization, WorkSpace or WorkSet levels.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Run the Dataset Validator&amp;nbsp;again and fix any errors.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Test that the&amp;nbsp;content&amp;nbsp;is available in the UI,&amp;nbsp;i.e. in the&amp;nbsp;Catalog Editor and in the building tools.&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;Step 6: Modify WorkSet folder names or structure as appropriate to conform with organization standards&lt;/h1&gt;
&lt;p&gt;This step is put at the end of the process so a baseline is established before any site specific changes to&amp;nbsp;folder structures and files names are made. This narrows down the scope of any troubleshooting&amp;nbsp;that may be necessary; when CFG file are being edited even simple typos can cause errors.&lt;/p&gt;
&lt;p&gt;For example, in the example WorkSet CFG the default folder for design files is&amp;nbsp;called &amp;#39;Designs&amp;#39;:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635173318687v1.png" /&gt;&lt;/p&gt;
&lt;p&gt;This is defined by the lines:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635173558944v2.png" /&gt;&lt;/p&gt;
&lt;p&gt;If the folder location is correct, but the name &lt;span&gt;&amp;#39;Designs&amp;#39;&amp;nbsp;&lt;/span&gt;does not comply with project standards it can be renamed. The name &amp;#39;Designs&amp;#39; in the&amp;nbsp;&lt;span&gt;_USTN_WORKSETDGNS statement must then be changed to match the new folder name. (This has to be done by text editing we do not have a UI for such changes.)&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;Step 7: Add any CONNECT Edition custom content (optional, can be done at a later stage)&lt;/h1&gt;
&lt;p&gt;New features in&amp;nbsp;&lt;span&gt;CONNECT Edition may benefit form customized content this may be an appropriate point to add such&amp;nbsp;content.&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;&lt;span&gt;Step 8: Copy existing DGN files&lt;/span&gt;&lt;/h1&gt;
&lt;p&gt;&lt;span&gt;Existing DGN files and other WorkSet specific content should&amp;nbsp;be copied&amp;nbsp;into the appropriate folders in the CONNECT Edition WorkSet.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Any model files&amp;nbsp;that contain building elements, (these are typically all of the 3D model files in a project) must be synchronised&amp;nbsp;with the new dataset using the&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479/upgrade-existing-elements-and-their-properties-to-the-current-catalog-schema" rel="noopener noreferrer" target="_blank"&gt;&amp;nbsp;Schema Upgrade Utility&lt;/a&gt;. This can be done to all files in one go as explained in the&amp;nbsp;linked article. &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The utility should&amp;nbsp;also be run on any existing&amp;nbsp;&amp;nbsp;BB_Floormaster.dgnlib. This may be successful, however as there have been significant changes&amp;nbsp;to the internal structure of&amp;nbsp;&amp;nbsp;BB_Floormaster.dgnlib since V8i we cannot&amp;nbsp;guarantee that&amp;nbsp;&amp;nbsp;BB_Floormaster.dgnlib content will be entirely&amp;nbsp;valid. It may be necessary to recreate the floor and Grid Systems content.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;2D files, generally&amp;nbsp;drawing&amp;nbsp;and sheets, do not contain building elements so do not need to be upgraded.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;If models contain Catalog Items or Parts that are not present in the new dataset the DataGroup Transformation Utility can be used to remap properties and the Part utilities can be used to verify and where necessary remap parts to elements.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/03548.NewLogo.png"&gt;&lt;img style="border-width:0px;" alt=" " height="60" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" width="189" /&gt;&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Draft - Content is WiP&lt;/div&gt;
</description></item><item><title>Migrating custom content from AECOsim Building Designer SS6 to a current OpenBuildings Designer version</title><link>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version/revision/8</link><pubDate>Mon, 25 Oct 2021 15:26:23 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:74ea833a-2c67-4860-90b8-05cf1fd96ae0</guid><dc:creator>Marc Thomas</dc:creator><comments>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version#comments</comments><description>Revision 8 posted to OpenBuildings | AECOsim | Speedikon Wiki by Marc Thomas on 10/25/2021 3:26:23 PM&lt;br /&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;" width="30%"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;OpenBuildings Designer&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;CONNECT Edition&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Datasets and content&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Migration/Upgrade&lt;span&gt; &lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;This article discusses the migration of dataset content.&lt;/p&gt;
&lt;p&gt;Migration of a V8i Workspace to a CONNECT Edition Configuration is&amp;nbsp;covered by training course&amp;nbsp;&lt;a href="https://learn.bentley.com/app/Public/ViewLearningPathDetails?lpId=113058&amp;amp;aftkn=5527c519-bbc7-4890-9a2e-063edc9da5c0" rel="noopener noreferrer" target="_blank"&gt;BIM Management 301: Installation and Upgrade Guide&lt;/a&gt;, we recommend viewing this training and downloading the course workbook prior to embarking on a migration process.&amp;nbsp;This article will refer to some exercises contained in this training course that cover the creation of CONNECT WorkSpaces and WorkSets.&lt;/p&gt;
&lt;p&gt;A key recommendation is that any &lt;span&gt;CONNECT Edition Configuration should be in a separate folder structure&amp;nbsp;to any existing V8i Workspace; their folder structures&amp;nbsp;and configuration files are significantly different. Using a separate&amp;nbsp;location allows any new Configuration to be tested without affecting&amp;nbsp;an active production Workspace.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The migration of delivered dataset content from SS6 to CONNECT Edition is relatively straightforward as the dataset changes have been minimised for most datasets. Please note the exception to this: due to major changes in British standards the V8i UK/GB dataset is not directly compatible with the CONNECT versions. Please see &lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/35923/connect-edition---british-dataset-migration" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - British Dataset migration&lt;/a&gt;&amp;nbsp;for full details.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Step 1: Preparation&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Identify a separate location for the CONNECT Edition configuration, this must be in a separate location to the active V8i Workspace, even if only in a different root folder on a network share.&lt;/span&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Identify custom dataset content used in V8i, this could be cell libraries, DGNLIBs, XML files, etc. Ideally this content will be in separate folders and files from Bentley&amp;#39;s example dataset, however it may well be&amp;nbsp; mixed in alongside delivered content. This will depend on how the V8i Workspace was organised.&lt;/span&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decide how the example dataset(s) will be used. There are two main options.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Use as is accepting that some of the example content will not suit your situation. This means that when a new dataset is released it can simply replace the existing version without affecting any customisations.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Take ownership of the example dataset, modifying it as needed. This requires both a different approach when a new dataset is released and an organised approach to the creation and storage of custom content. Custom content should always be contained in clearly identified files to enable any changed files from Bentley to be added/replaced/deleted. Changes introduced by new versions are listed in the dataset delta document and must be implemented manually.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decide where the dataset(s) will be located. There are two options.*&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;In the Custom Configuration (recommended). This is suitable for either of the options 1 or 2 above.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the local machine. This only applies if the delivered dataset is used unchanged, option 1 above, unless some external process is available to synchronize any customizations to the local copy.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="padding-left:30px;"&gt;These are discussed in more detail in&amp;nbsp;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/51041/dataset-strategies---local-or-network" rel="noopener noreferrer" target="_blank"&gt;Dataset Strategies - Local or Network&lt;/a&gt;.&amp;nbsp; If datasets on a local machine are preferred please refer to&amp;nbsp;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/50875/configuring-the-datasets-root-folder-location"&gt;&lt;span lang="en-US"&gt;Configuring the Datasets Root Folder Location&lt;/span&gt;&lt;/a&gt;.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:inherit;"&gt;&lt;/span&gt;*Note: &lt;a href="/products/projectwise/content_management/w/wiki/53045/projectwise-drive" rel="noopener noreferrer" target="_blank"&gt;ProjectWise 365 Drive&lt;/a&gt; will become an option for sharing configurations and synchronising their content to local machines&amp;nbsp;when additional features are released late in 2021.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Plan the implementation of access control via Windows File/Folder permissions to Organization, WorkSpace and WorkSet levels, the purpose of which is to ensure that only the responsible people are able to modify shared content:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Organization: Read-only to non-admin users.&lt;/li&gt;
&lt;li&gt;WorkSpaces: Write access to appropriate administrators, this may include BIM Coordinator type roles depending on organizational structure.&lt;/li&gt;
&lt;li&gt;WorkSets: Write access to all relevant users.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h1&gt;Step 2: Directing OpenBuildings Designer to a Network Location&lt;/h1&gt;
&lt;p&gt;This is described in Exercise 1: Installing OpenBuildings Designer Configured to a Network Location.&lt;/p&gt;
&lt;p&gt;The location of a custom configuration is stored in ConfigurationSetup.cfg on each machine. This is the only file that needs to be modified to redirect a machine to a custom configuration.&amp;nbsp;The configured location does not have to be available when OpenBuildings Designer is installed, the path will be ignored unless WorkSpace CFG files are present.&lt;/p&gt;
&lt;p&gt;If OpenBuildings Designer is already installed ConfigurationSetup.cfg can be updated as described in &lt;a href="/products/projectwise/content_management/w/wiki/53045/projectwise-drive" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - Configuration Tips : Should I edit ConfigurationSetup.cfg?&lt;/a&gt;&lt;/p&gt;
&lt;h1&gt;Step 3:&amp;nbsp;Populate the Custom Configuration&lt;/h1&gt;
&lt;p&gt;Creating the required folder structure is outlined in Exercise 2: Setting Up the Organization and WorkSpace Folders.&lt;/p&gt;
&lt;p&gt;This is a typical example where the Datasets are located in the Custom Configuration under ...\OBD_Resources\Datasets\; one WorkSpace named ActiveProjects_365 is contained in the WorkSpaces folder.&lt;/p&gt;
&lt;table border="1" height="789"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td rowspan="3"&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635168631491v2.png" /&gt;&lt;/td&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;Datasets:&lt;/p&gt;
&lt;p&gt;Unless configured otherwise the Catalog User Interface will treat the active Dataset as the Organisation level&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635169877994v3.png" /&gt;&lt;/p&gt;
&lt;p&gt;Organization level Custom content may be stored here depending on the decision discussed above about use of delivered datasets.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;Organization:&lt;/p&gt;
&lt;p&gt;Unless configured otherwise the Organization subfolders contain shared platform or ProStructures content directed to by Standards.cfg and some &lt;span&gt;ProStructures&amp;nbsp;&lt;/span&gt;CFG files. Any content here will be available to all users unless configured otherwise.&lt;/p&gt;
&lt;p&gt;There are no OpenBuildings specific folders.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;WorkSpaces:&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The Catalog User Interface will recognize the&amp;nbsp;WorkSpaces folder as the WorkSpaces&amp;nbsp;level.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Any content here will be available to&amp;nbsp;only to&amp;nbsp;users of the active WorkSpace.&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Step 4: Create WorkSets&lt;/h1&gt;
&lt;p&gt;The default WorkSet location will be in the WorkSets folder within the Custom Configuration. Obviously project data is not a sub-set of an application. WorkSet folders will need to be in the appropriate project data location. This is covered by&amp;nbsp;Exercise 5: Moving the WorkSets to a Separate Drive, the essential part of which is editing the _USTN_WORKSETROOT path in all WorkSpace CFG files. In this example that file is&amp;nbsp;ActiveProjects_365.cfg and it needs to contain a line defining&amp;nbsp;&lt;span&gt;_USTN_WORKSETROOT as pointing to the project data location, for example P:\ActiveProjects\OBD_AU_Demo\, e.g.:&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;em&gt;_USTN_WORKSETROOT = P:/ActiveProjects/$(_USTN_WORKSETNAME)/&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Create a new WorkSet by copying the appropriate regional WorkSet example, e.g.&amp;nbsp;BuildingTemplate_AU.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The&amp;nbsp;BuildingTemplate_AU folder should be copied to the project data location&lt;/li&gt;
&lt;li&gt;BuildingTemplate_AU.cfg should be copied to the WorkSets folder.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Both must be renamed with the new project name, folder and CFG file names must match, this is what links them together.&lt;/p&gt;
&lt;p&gt;Once the example WorkSet has been copied, but before adding any V8i content or making site specific changes to folder structures, test the new Custom Configuration. Review any messages displayed in the Message Center or elsewhere in the UI taking appropriate action to rectify them.&lt;/p&gt;
&lt;p&gt;At this point also run the Dataset Validator (File &amp;gt; Dataset Tools &amp;gt; Validate) and Verify Parts (File &amp;gt; Utilities &amp;gt; Part Utilities &amp;gt; Verify Parts) to ascertain the current state of the dataset.&amp;nbsp;It will be easier to fix errors at this point before custom content is added.&lt;/p&gt;
&lt;h1&gt;Step 5: Add previous custom content.&lt;/h1&gt;
&lt;p&gt;Check against dataset delta documents to see if any of the V8i files are now obsolete. For instance V8i curtain walls are superseded by the CONNECT Edition tools, earlier content will not work with the new tool.&lt;/p&gt;
&lt;p&gt;Add V8i files in the appropriate locations at&amp;nbsp;&lt;span&gt;Organization, WorkSpace or WorkSet levels.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Run the Dataset Validator&amp;nbsp;again and fix any errors.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Test that the&amp;nbsp;content&amp;nbsp;is available in the UI,&amp;nbsp;i.e. in the&amp;nbsp;Catalog Editor and in the building tools.&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;Step 6: Modify WorkSet folder names or structure as appropriate to conform with organization standards&lt;/h1&gt;
&lt;p&gt;This step is put at the end of the process so a baseline is established before any site specific changes to&amp;nbsp;folder structures and files names are made. This narrows down the scope of any troubleshooting&amp;nbsp;that may be necessary; when CFG file are being edited even simple typos can cause errors.&lt;/p&gt;
&lt;p&gt;For example, in the example WorkSet CFG the default folder for design files is&amp;nbsp;called &amp;#39;Designs&amp;#39;:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635173318687v1.png" /&gt;&lt;/p&gt;
&lt;p&gt;This is defined by the lines:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635173558944v2.png" /&gt;&lt;/p&gt;
&lt;p&gt;If the folder location is correct, but the name &lt;span&gt;&amp;#39;Designs&amp;#39;&amp;nbsp;&lt;/span&gt;does not comply with project standards it can be renamed. The name &amp;#39;Designs&amp;#39; in the&amp;nbsp;&lt;span&gt;_USTN_WORKSETDGNS statement must then be changed to match the new folder name. (This has to be done by text editing we do not have a UI for such changes.)&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;Step 7: Add any CONNECT Edition custom content (optional, can be done at a later stage)&lt;/h1&gt;
&lt;p&gt;New features in&amp;nbsp;&lt;span&gt;CONNECT Edition may benefit form customized content this may be an appropriate point to add such&amp;nbsp;content.&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;&lt;span&gt;Step 8: Copy existing DGN files&lt;/span&gt;&lt;/h1&gt;
&lt;p&gt;&lt;span&gt;Existing DGN files should&amp;nbsp;be copied&amp;nbsp;into the appropriate folders in the CONNECT Edition WorkSet.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Any model files&amp;nbsp;that contain building elements, (these are typically all of the 3D model files in a project) must be synchronised&amp;nbsp;with the new dataset using the&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479/upgrade-existing-elements-and-their-properties-to-the-current-catalog-schema" rel="noopener noreferrer" target="_blank"&gt;&amp;nbsp;Schema Upgrade Utility&lt;/a&gt;. This can be done to all files in one go as explained in the&amp;nbsp;linked article.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;2D files, generally&amp;nbsp;drawing&amp;nbsp;and sheets, do not contain building elements so do not need to be upgraded.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;If models contain Catalog Items or Parts that are not present in the new dataset the DataGroup Transformation Utility can be used to remap properties and the Part utilities can be used to verify and where necessary remap parts to elements.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/03548.NewLogo.png"&gt;&lt;img style="border-width:0px;" alt=" " height="60" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" width="189" /&gt;&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Draft - Content is WiP&lt;/div&gt;
</description></item><item><title>Migrating custom content from AECOsim Building Designer SS6 to a current OpenBuildings Designer version</title><link>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version/revision/7</link><pubDate>Mon, 25 Oct 2021 15:25:57 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:74ea833a-2c67-4860-90b8-05cf1fd96ae0</guid><dc:creator>Marc Thomas</dc:creator><comments>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version#comments</comments><description>Revision 7 posted to OpenBuildings | AECOsim | Speedikon Wiki by Marc Thomas on 10/25/2021 3:25:57 PM&lt;br /&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;" width="30%"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;OpenBuildings Designer&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;CONNECT Edition&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Datasets and content&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Migration/Upgrade&lt;span&gt; &lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2&gt;&lt;em&gt;Draft Wiki.............................................................&lt;/em&gt;&lt;/h2&gt;
&lt;p&gt;This article discusses the migration of dataset content.&lt;/p&gt;
&lt;p&gt;Migration of a V8i Workspace to a CONNECT Edition Configuration is&amp;nbsp;covered by training course&amp;nbsp;&lt;a href="https://learn.bentley.com/app/Public/ViewLearningPathDetails?lpId=113058&amp;amp;aftkn=5527c519-bbc7-4890-9a2e-063edc9da5c0" rel="noopener noreferrer" target="_blank"&gt;BIM Management 301: Installation and Upgrade Guide&lt;/a&gt;, we recommend viewing this training and downloading the course workbook prior to embarking on a migration process.&amp;nbsp;This article will refer to some exercises contained in this training course that cover the creation of CONNECT WorkSpaces and WorkSets.&lt;/p&gt;
&lt;p&gt;A key recommendation is that any &lt;span&gt;CONNECT Edition Configuration should be in a separate folder structure&amp;nbsp;to any existing V8i Workspace; their folder structures&amp;nbsp;and configuration files are significantly different. Using a separate&amp;nbsp;location allows any new Configuration to be tested without affecting&amp;nbsp;an active production Workspace.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The migration of delivered dataset content from SS6 to CONNECT Edition is relatively straightforward as the dataset changes have been minimised for most datasets. Please note the exception to this: due to major changes in British standards the V8i UK/GB dataset is not directly compatible with the CONNECT versions. Please see &lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/35923/connect-edition---british-dataset-migration" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - British Dataset migration&lt;/a&gt;&amp;nbsp;for full details.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Step 1: Preparation&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Identify a separate location for the CONNECT Edition configuration, this must be in a separate location to the active V8i Workspace, even if only in a different root folder on a network share.&lt;/span&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Identify custom dataset content used in V8i, this could be cell libraries, DGNLIBs, XML files, etc. Ideally this content will be in separate folders and files from Bentley&amp;#39;s example dataset, however it may well be&amp;nbsp; mixed in alongside delivered content. This will depend on how the V8i Workspace was organised.&lt;/span&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decide how the example dataset(s) will be used. There are two main options.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Use as is accepting that some of the example content will not suit your situation. This means that when a new dataset is released it can simply replace the existing version without affecting any customisations.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Take ownership of the example dataset, modifying it as needed. This requires both a different approach when a new dataset is released and an organised approach to the creation and storage of custom content. Custom content should always be contained in clearly identified files to enable any changed files from Bentley to be added/replaced/deleted. Changes introduced by new versions are listed in the dataset delta document and must be implemented manually.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decide where the dataset(s) will be located. There are two options.*&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;In the Custom Configuration (recommended). This is suitable for either of the options 1 or 2 above.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the local machine. This only applies if the delivered dataset is used unchanged, option 1 above, unless some external process is available to synchronize any customizations to the local copy.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="padding-left:30px;"&gt;These are discussed in more detail in&amp;nbsp;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/51041/dataset-strategies---local-or-network" rel="noopener noreferrer" target="_blank"&gt;Dataset Strategies - Local or Network&lt;/a&gt;.&amp;nbsp; If datasets on a local machine are preferred please refer to&amp;nbsp;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/50875/configuring-the-datasets-root-folder-location"&gt;&lt;span lang="en-US"&gt;Configuring the Datasets Root Folder Location&lt;/span&gt;&lt;/a&gt;.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:inherit;"&gt;&lt;/span&gt;*Note: &lt;a href="/products/projectwise/content_management/w/wiki/53045/projectwise-drive" rel="noopener noreferrer" target="_blank"&gt;ProjectWise 365 Drive&lt;/a&gt; will become an option for sharing configurations and synchronising their content to local machines&amp;nbsp;when additional features are released late in 2021.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Plan the implementation of access control via Windows File/Folder permissions to Organization, WorkSpace and WorkSet levels, the purpose of which is to ensure that only the responsible people are able to modify shared content:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Organization: Read-only to non-admin users.&lt;/li&gt;
&lt;li&gt;WorkSpaces: Write access to appropriate administrators, this may include BIM Coordinator type roles depending on organizational structure.&lt;/li&gt;
&lt;li&gt;WorkSets: Write access to all relevant users.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h1&gt;Step 2: Directing OpenBuildings Designer to a Network Location&lt;/h1&gt;
&lt;p&gt;This is described in Exercise 1: Installing OpenBuildings Designer Configured to a Network Location.&lt;/p&gt;
&lt;p&gt;The location of a custom configuration is stored in ConfigurationSetup.cfg on each machine. This is the only file that needs to be modified to redirect a machine to a custom configuration.&amp;nbsp;The configured location does not have to be available when OpenBuildings Designer is installed, the path will be ignored unless WorkSpace CFG files are present.&lt;/p&gt;
&lt;p&gt;If OpenBuildings Designer is already installed ConfigurationSetup.cfg can be updated as described in &lt;a href="/products/projectwise/content_management/w/wiki/53045/projectwise-drive" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - Configuration Tips : Should I edit ConfigurationSetup.cfg?&lt;/a&gt;&lt;/p&gt;
&lt;h1&gt;Step 3:&amp;nbsp;Populate the Custom Configuration&lt;/h1&gt;
&lt;p&gt;Creating the required folder structure is outlined in Exercise 2: Setting Up the Organization and WorkSpace Folders.&lt;/p&gt;
&lt;p&gt;This is a typical example where the Datasets are located in the Custom Configuration under ...\OBD_Resources\Datasets\; one WorkSpace named ActiveProjects_365 is contained in the WorkSpaces folder.&lt;/p&gt;
&lt;table border="1" height="789"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td rowspan="3"&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635168631491v2.png" /&gt;&lt;/td&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;Datasets:&lt;/p&gt;
&lt;p&gt;Unless configured otherwise the Catalog User Interface will treat the active Dataset as the Organisation level&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635169877994v3.png" /&gt;&lt;/p&gt;
&lt;p&gt;Organization level Custom content may be stored here depending on the decision discussed above about use of delivered datasets.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;Organization:&lt;/p&gt;
&lt;p&gt;Unless configured otherwise the Organization subfolders contain shared platform or ProStructures content directed to by Standards.cfg and some &lt;span&gt;ProStructures&amp;nbsp;&lt;/span&gt;CFG files. Any content here will be available to all users unless configured otherwise.&lt;/p&gt;
&lt;p&gt;There are no OpenBuildings specific folders.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;WorkSpaces:&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The Catalog User Interface will recognize the&amp;nbsp;WorkSpaces folder as the WorkSpaces&amp;nbsp;level.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Any content here will be available to&amp;nbsp;only to&amp;nbsp;users of the active WorkSpace.&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Step 4: Create WorkSets&lt;/h1&gt;
&lt;p&gt;The default WorkSet location will be in the WorkSets folder within the Custom Configuration. Obviously project data is not a sub-set of an application. WorkSet folders will need to be in the appropriate project data location. This is covered by&amp;nbsp;Exercise 5: Moving the WorkSets to a Separate Drive, the essential part of which is editing the _USTN_WORKSETROOT path in all WorkSpace CFG files. In this example that file is&amp;nbsp;ActiveProjects_365.cfg and it needs to contain a line defining&amp;nbsp;&lt;span&gt;_USTN_WORKSETROOT as pointing to the project data location, for example P:\ActiveProjects\OBD_AU_Demo\, e.g.:&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;em&gt;_USTN_WORKSETROOT = P:/ActiveProjects/$(_USTN_WORKSETNAME)/&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Create a new WorkSet by copying the appropriate regional WorkSet example, e.g.&amp;nbsp;BuildingTemplate_AU.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The&amp;nbsp;BuildingTemplate_AU folder should be copied to the project data location&lt;/li&gt;
&lt;li&gt;BuildingTemplate_AU.cfg should be copied to the WorkSets folder.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Both must be renamed with the new project name, folder and CFG file names must match, this is what links them together.&lt;/p&gt;
&lt;p&gt;Once the example WorkSet has been copied, but before adding any V8i content or making site specific changes to folder structures, test the new Custom Configuration. Review any messages displayed in the Message Center or elsewhere in the UI taking appropriate action to rectify them.&lt;/p&gt;
&lt;p&gt;At this point also run the Dataset Validator (File &amp;gt; Dataset Tools &amp;gt; Validate) and Verify Parts (File &amp;gt; Utilities &amp;gt; Part Utilities &amp;gt; Verify Parts) to ascertain the current state of the dataset.&amp;nbsp;It will be easier to fix errors at this point before custom content is added.&lt;/p&gt;
&lt;h1&gt;Step 5: Add previous custom content.&lt;/h1&gt;
&lt;p&gt;Check against dataset delta documents to see if any of the V8i files are now obsolete. For instance V8i curtain walls are superseded by the CONNECT Edition tools, earlier content will not work with the new tool.&lt;/p&gt;
&lt;p&gt;Add V8i files in the appropriate locations at&amp;nbsp;&lt;span&gt;Organization, WorkSpace or WorkSet levels.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Run the Dataset Validator&amp;nbsp;again and fix any errors.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Test that the&amp;nbsp;content&amp;nbsp;is available in the UI,&amp;nbsp;i.e. in the&amp;nbsp;Catalog Editor and in the building tools.&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;Step 6: Modify WorkSet folder names or structure as appropriate to conform with organization standards&lt;/h1&gt;
&lt;p&gt;This step is put at the end of the process so a baseline is established before any site specific changes to&amp;nbsp;folder structures and files names are made. This narrows down the scope of any troubleshooting&amp;nbsp;that may be necessary; when CFG file are being edited even simple typos can cause errors.&lt;/p&gt;
&lt;p&gt;For example, in the example WorkSet CFG the default folder for design files is&amp;nbsp;called &amp;#39;Designs&amp;#39;:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635173318687v1.png" /&gt;&lt;/p&gt;
&lt;p&gt;This is defined by the lines:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635173558944v2.png" /&gt;&lt;/p&gt;
&lt;p&gt;If the folder location is correct, but the name &lt;span&gt;&amp;#39;Designs&amp;#39;&amp;nbsp;&lt;/span&gt;does not comply with project standards it can be renamed. The name &amp;#39;Designs&amp;#39; in the&amp;nbsp;&lt;span&gt;_USTN_WORKSETDGNS statement must then be changed to match the new folder name. (This has to be done by text editing we do not have a UI for such changes.)&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;Step 7: Add any CONNECT Edition custom content (optional, can be done at a later stage)&lt;/h1&gt;
&lt;p&gt;New features in&amp;nbsp;&lt;span&gt;CONNECT Edition may benefit form customized content this may be an appropriate point to add such&amp;nbsp;content.&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;&lt;span&gt;Step 8: Copy existing DGN files&lt;/span&gt;&lt;/h1&gt;
&lt;p&gt;&lt;span&gt;Existing DGN files should&amp;nbsp;be copied&amp;nbsp;into the appropriate folders in the CONNECT Edition WorkSet.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Any model files&amp;nbsp;that contain building elements, (these are typically all of the 3D model files in a project) must be synchronised&amp;nbsp;with the new dataset using the&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479/upgrade-existing-elements-and-their-properties-to-the-current-catalog-schema" rel="noopener noreferrer" target="_blank"&gt;&amp;nbsp;Schema Upgrade Utility&lt;/a&gt;. This can be done to all files in one go as explained in the&amp;nbsp;linked article.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;2D files, generally&amp;nbsp;drawing&amp;nbsp;and sheets, do not contain building elements so do not need to be upgraded.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;If models contain Catalog Items or Parts that are not present in the new dataset the DataGroup Transformation Utility can be used to remap properties and the Part utilities can be used to verify and where necessary remap parts to elements.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/03548.NewLogo.png"&gt;&lt;img style="border-width:0px;" alt=" " height="60" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" width="189" /&gt;&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Draft - Content is WiP&lt;/div&gt;
</description></item><item><title>Migrating custom content from AECOsim Building Designer SS6 to a current OpenBuildings Designer version</title><link>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version/revision/6</link><pubDate>Mon, 25 Oct 2021 14:47:53 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:74ea833a-2c67-4860-90b8-05cf1fd96ae0</guid><dc:creator>Marc Thomas</dc:creator><comments>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version#comments</comments><description>Revision 6 posted to OpenBuildings | AECOsim | Speedikon Wiki by Marc Thomas on 10/25/2021 2:47:53 PM&lt;br /&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;" width="30%"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;OpenBuildings Designer&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;CONNECT Edition&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Datasets and content&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Migration/Upgrade&lt;span&gt; &lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2&gt;&lt;em&gt;Draft Wiki.............................................................&lt;/em&gt;&lt;/h2&gt;
&lt;p&gt;This article discusses the migration of dataset content.&lt;/p&gt;
&lt;p&gt;Migration of a V8i Workspace to a CONNECT Edition Configuration is&amp;nbsp;covered by training course&amp;nbsp;&lt;a href="https://learn.bentley.com/app/Public/ViewLearningPathDetails?lpId=113058&amp;amp;aftkn=5527c519-bbc7-4890-9a2e-063edc9da5c0" rel="noopener noreferrer" target="_blank"&gt;BIM Management 301: Installation and Upgrade Guide&lt;/a&gt;, we recommend viewing this training and downloading the course workbook prior to embarking on a migration process.&amp;nbsp;This article will refer to some exercises contained in this training course that cover the creation of CONNECT WorkSpaces and WorkSets.&lt;/p&gt;
&lt;p&gt;A key recommendation is that any &lt;span&gt;CONNECT Edition Configuration should be in a separate folder structure&amp;nbsp;to any existing V8i Workspace; their folder structures&amp;nbsp;and configuration files are significantly different. Using a separate&amp;nbsp;location allows any new Configuration to be tested without affecting&amp;nbsp;an active production Workspace.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The migration of delivered dataset content from SS6 to CONNECT Edition is relatively straightforward as the dataset changes have been minimised for most datasets. Please note the exception to this: due to major changes in British standards the V8i UK/GB dataset is not directly compatible with the CONNECT versions. Please see &lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/35923/connect-edition---british-dataset-migration" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - British Dataset migration&lt;/a&gt;&amp;nbsp;for full details.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Step 1: Preparation&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Identify a separate location for the CONNECT Edition configuration, this must be in a separate location to the active V8i Workspace, even if only in a different root folder on a network share.&lt;/span&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Identify custom dataset content used in V8i, this could be cell libraries, DGNLIBs, XML files, etc. Ideally this content will be in separate folders and files from Bentley&amp;#39;s example dataset, however it may well be&amp;nbsp; mixed in alongside delivered content. This will depend on how the V8i Workspace was organised.&lt;/span&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decide how the example dataset(s) will be used. There are two main options.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Use as is accepting that some of the example content will not suit your situation. This means that when a new dataset is released it can simply replace the existing version without affecting any customisations.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Take ownership of the example dataset, modifying it as needed. This requires both a different approach when a new dataset is released and an organised approach to the creation and storage of custom content. Custom content should always be contained in clearly identified files to enable any changed files from Bentley to be added/replaced/deleted. Changes introduced by new versions are listed in the dataset delta document and must be implemented manually.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decide where the dataset(s) will be located. There are two options.*&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;In the Custom Configuration (recommended). This is suitable for either of the options 1 or 2 above.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the local machine. This only applies if the delivered dataset is used unchanged, option 1 above, unless some external process is available to synchronize any customizations to the local copy.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="padding-left:30px;"&gt;These are discussed in more detail in&amp;nbsp;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/51041/dataset-strategies---local-or-network" rel="noopener noreferrer" target="_blank"&gt;Dataset Strategies - Local or Network&lt;/a&gt;.&amp;nbsp; If datasets on a local machine are preferred please refer to&amp;nbsp;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/50875/configuring-the-datasets-root-folder-location"&gt;&lt;span lang="en-US"&gt;Configuring the Datasets Root Folder Location&lt;/span&gt;&lt;/a&gt;.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:inherit;"&gt;&lt;/span&gt;*Note: &lt;a href="/products/projectwise/content_management/w/wiki/53045/projectwise-drive" rel="noopener noreferrer" target="_blank"&gt;ProjectWise 365 Drive&lt;/a&gt; will become an option for sharing configurations and synchronising their content to local machines&amp;nbsp;when additional features are released late in 2021.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Plan the implementation of access control via Windows File/Folder permissions to Organization, WorkSpace and WorkSet levels, the purpose of which is to ensure that only the responsible people are able to modify shared content:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Organization: Read-only to non-admin users.&lt;/li&gt;
&lt;li&gt;WorkSpaces: Write access to appropriate administrators, this may include BIM Coordinator type roles depending on organizational structure.&lt;/li&gt;
&lt;li&gt;WorkSets: Write access to all relevant users.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h1&gt;Step 2: Directing OpenBuildings Designer to a Network Location&lt;/h1&gt;
&lt;p&gt;This is described in Exercise 1: Installing OpenBuildings Designer Configured to a Network Location.&lt;/p&gt;
&lt;p&gt;The location of a custom configuration is stored in ConfigurationSetup.cfg on each machine. This is the only file that needs to be modified to redirect a machine to a custom configuration.&amp;nbsp;The configured location does not have to be available when OpenBuildings Designer is installed, the path will be ignored unless WorkSpace CFG files are present.&lt;/p&gt;
&lt;p&gt;If OpenBuildings Designer is already installed ConfigurationSetup.cfg can be updated as described in &lt;a href="/products/projectwise/content_management/w/wiki/53045/projectwise-drive" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - Configuration Tips : Should I edit ConfigurationSetup.cfg?&lt;/a&gt;&lt;/p&gt;
&lt;h1&gt;Step 3:&amp;nbsp;Populate the Custom Configuration&lt;/h1&gt;
&lt;p&gt;Creating the required folder structure is outlined in Exercise 2: Setting Up the Organization and WorkSpace Folders.&lt;/p&gt;
&lt;p&gt;This is a typical example where the Datasets are located in the Custom Configuration under ...\OBD_Resources\Datasets\; one WorkSpace named ActiveProjects_365 is contained in the WorkSpaces folder.&lt;/p&gt;
&lt;table border="1" height="789"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td rowspan="3"&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635168631491v2.png" /&gt;&lt;/td&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;Datasets:&lt;/p&gt;
&lt;p&gt;Unless configured otherwise the Catalog User Interface will treat the active Dataset as the Organisation level&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635169877994v3.png" /&gt;&lt;/p&gt;
&lt;p&gt;Organization level Custom content may be stored here depending on the decision discussed above about use of delivered datasets.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;Organization:&lt;/p&gt;
&lt;p&gt;Unless configured otherwise the Organization subfolders contain shared platform or ProStructures content directed to by Standards.cfg and some &lt;span&gt;ProStructures&amp;nbsp;&lt;/span&gt;CFG files. Any content here will be available to all users unless configured otherwise.&lt;/p&gt;
&lt;p&gt;There are no OpenBuildings specific folders.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;WorkSpaces:&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The Catalog User Interface will recognize the&amp;nbsp;WorkSpaces folder as the WorkSpaces&amp;nbsp;level.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Any content here will be available to&amp;nbsp;only to&amp;nbsp;users of the active WorkSpace.&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Step 4: Create WorkSets&lt;/h1&gt;
&lt;p&gt;The default WorkSet location will be in the WorkSets folder within the Custom Configuration. Obviously project data is not a sub-set of an application. WorkSet folders will need to be in the appropriate project data location. This is covered by&amp;nbsp;Exercise 5: Moving the WorkSets to a Separate Drive, the essential part of which is editing the _USTN_WORKSETROOT path in all WorkSpace CFG files. In this example that file is&amp;nbsp;ActiveProjects_365.cfg and it needs to contain a line defining&amp;nbsp;&lt;span&gt;_USTN_WORKSETROOT as pointing to the project data location, for example P:\ActiveProjects\OBD_AU_Demo\, e.g.:&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;em&gt;_USTN_WORKSETROOT = P:/ActiveProjects/$(_USTN_WORKSETNAME)/&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Create a new WorkSet by copying the appropriate regional WorkSet example, e.g.&amp;nbsp;BuildingTemplate_AU.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The&amp;nbsp;BuildingTemplate_AU folder should be copied to the project data location&lt;/li&gt;
&lt;li&gt;BuildingTemplate_AU.cfg should be copied to the WorkSets folder.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Both must be renamed with the new project name, folder and CFG file names must match, this is what links them together.&lt;/p&gt;
&lt;p&gt;Once the example WorkSet has been copied, but before adding any V8i content or making site specific changes to folder structures, test the new Custom Configuration. Review any messages displayed in the Message Center or elsewhere in the UI taking appropriate action to rectify them.&lt;/p&gt;
&lt;h1&gt;Step 5: Add previous custom content.&lt;/h1&gt;
&lt;p&gt;check against dataset delta documents to see if any V8i files are now obsolete. For instance V8i curtain walls are superseded by the CONNECT Edition tools, earlier content will not work with the new tool.&lt;/p&gt;
&lt;p&gt;Add V8i files in the appropriate locations at&amp;nbsp;&lt;span&gt;Organization, WorkSpace or WorkSet levels.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Test that the&amp;nbsp;content&amp;nbsp;is available&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;Step 6: Modify WorkSet folder names or structure as appropriate to conform with organization standards&lt;/h1&gt;
&lt;p&gt;This step is put at the end of the process so a baseline is established before any site specific changes to&amp;nbsp;folder structures and files names are made. This narrows down the scope of any troubleshooting&amp;nbsp;that may be necessary; when CFG file are being edited even simple typos can cause errors.&lt;/p&gt;
&lt;p&gt;For example, in the example WorkSet CFG the default folder for design files is&amp;nbsp;called &amp;#39;Designs&amp;#39;:&lt;/p&gt;
&lt;p&gt;&lt;span class="mceItem mceNonEditable mceInsertMediaItem mceInsertMediaItem mceInsertMediaItemImage" style="color:transparent;height:240px;width:320px;" id="pastedimage1635173251826v1"&gt;...&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;#======================================================================&lt;br /&gt;# Establish WorkSet Directories:&lt;br /&gt;#======================================================================&lt;br /&gt; # Primary WorkSet Directory (Search Path for design files)&lt;br /&gt; MS_DEF = $(_USTN_WORKSETDGNS)&lt;/p&gt;
&lt;p&gt;# DESIGN: WorkSet Directory for Design Models&lt;br /&gt; _USTN_WORKSETDGNS = $(_USTN_WORKSETROOT)Designs/&lt;br /&gt; MS_DESIGNDIR = $(_USTN_WORKSETDGNS)&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Test the Custom Configuration to establish that&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Previously identified custom content can be placed in the appropriate folders at Organization, WorkSpace or WorkSet levels.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The&amp;nbsp;decision about how to use delivered dataset content leads to two main scenarios for an upgrade sequence:&lt;/li&gt;
&lt;/ul&gt;
&lt;ol&gt;
&lt;li&gt;Where the delivered dataset has not been modified and all custom families/parts and DataGroup content have been stored in project datasets.&lt;/li&gt;
&lt;li&gt;Where the delivered dataset has been modified by the addition of Company custom families/parts and DataGroup content in addition to those&amp;nbsp;stored in project datasets.&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li&gt;&lt;/li&gt;
&lt;li&gt;Other variations are possible, but the steps to upgrade these two will provide general guidance for similar cases.&lt;/li&gt;
&lt;li&gt;1. Unmodified Delivered Dataset.&lt;/li&gt;
&lt;li&gt;Summary of steps:&lt;/li&gt;
&lt;/ul&gt;
&lt;ol&gt;
&lt;li&gt;....&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Run the Schema Upgrade utility on your project files as described in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479.upgrade-existing-elements-to-current-datagroup-system-properties.aspx"&gt;Upgrade existing elements to current DataGroup System properties&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Run the&amp;nbsp;&lt;/span&gt;&lt;span&gt;Schema&amp;nbsp;&lt;/span&gt;&lt;span&gt;Upgrade utility on existing BB_Floormaster.dgnlib files &amp;lt;link batch script to delete unused contnet&amp;gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Run other Building utilities as required to upgrade project dataset content.&lt;/li&gt;
&lt;li&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li&gt;&lt;/li&gt;
&lt;li&gt;2. Delivered Dataset has Been Modified&lt;/li&gt;
&lt;li&gt;Summary of steps:&lt;/li&gt;
&lt;/ul&gt;
&lt;ol&gt;
&lt;li&gt;Copy existing workspace folders and contents to the new SS6 folder including&amp;nbsp;the Building Dataset(s).&lt;/li&gt;
&lt;li&gt;Copy your Company Dataset (if you have one) folders from SS5 to SS6.&lt;/li&gt;
&lt;li&gt;Follow the steps described in C:\ProgramData\Bentley\AECOsimBuildingDesigner V8i Ss6\WorkSpace\BuildingDatasets\Dataset_&amp;lt;regionCode&amp;gt;\Dataset_&amp;lt;regionCode&amp;gt;_Ss6_delta.pdf to add, delete or modify files in the SS5 dataset to match SS6.&lt;/li&gt;
&lt;li&gt;Run the DataGroup Upgrade utility on your project files as described in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479.upgrade-existing-elements-to-current-datagroup-system-properties.aspx"&gt;Upgrade existing elements to current DataGroup System properties&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Run the&amp;nbsp;&lt;/span&gt;&lt;span&gt;Schema&amp;nbsp;&lt;/span&gt;&lt;span&gt;Upgrade utility on existing BB_Floormaster.dgnlib files&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Run other Building utilities as required to upgrade project dataset content.&lt;/li&gt;
&lt;li&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li&gt;See Also&lt;/li&gt;
&lt;li&gt;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479.upgrade-existing-elements-to-current-datagroup-system-properties.aspx"&gt;Upgrade existing elements to current DataGroup System properties&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/03548.NewLogo.png"&gt;&lt;img style="border-width:0px;" alt=" " height="60" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" width="189" /&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Draft - Content is WiP&lt;/div&gt;
</description></item><item><title>Migrating custom content from AECOsim Building Designer SS6 to a current OpenBuildings Designer version</title><link>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version/revision/5</link><pubDate>Mon, 25 Oct 2021 14:44:03 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:74ea833a-2c67-4860-90b8-05cf1fd96ae0</guid><dc:creator>Marc Thomas</dc:creator><comments>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version#comments</comments><description>Revision 5 posted to OpenBuildings | AECOsim | Speedikon Wiki by Marc Thomas on 10/25/2021 2:44:03 PM&lt;br /&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;" width="30%"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;OpenBuildings Designer&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;CONNECT Edition&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Datasets and content&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Migration/Upgrade&lt;span&gt; &lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2&gt;&lt;em&gt;Draft Wiki.............................................................&lt;/em&gt;&lt;/h2&gt;
&lt;p&gt;This article discusses the migration of dataset content.&lt;/p&gt;
&lt;p&gt;Migration of a V8i Workspace to a CONNECT Edition Configuration is&amp;nbsp;covered by training course&amp;nbsp;&lt;a href="https://learn.bentley.com/app/Public/ViewLearningPathDetails?lpId=113058&amp;amp;aftkn=5527c519-bbc7-4890-9a2e-063edc9da5c0" rel="noopener noreferrer" target="_blank"&gt;BIM Management 301: Installation and Upgrade Guide&lt;/a&gt;, we recommend viewing this training and downloading the course workbook prior to embarking on a migration process.&amp;nbsp;This article will refer to some exercises contained in this training course that cover the creation of CONNECT WorkSpaces and WorkSets.&lt;/p&gt;
&lt;p&gt;A key recommendation is that any &lt;span&gt;CONNECT Edition Configuration should be in a separate folder structure&amp;nbsp;to any existing V8i Workspace; their folder structures&amp;nbsp;and configuration files are significantly different. Using a separate&amp;nbsp;location allows any new Configuration to be tested without affecting&amp;nbsp;an active production Workspace.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The migration of delivered dataset content from SS6 to CONNECT Edition is relatively straightforward as the dataset changes have been minimised for most datasets. Please note the exception to this: due to major changes in British standards the V8i UK/GB dataset is not directly compatible with the CONNECT versions. Please see &lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/35923/connect-edition---british-dataset-migration" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - British Dataset migration&lt;/a&gt;&amp;nbsp;for full details.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Step 1: Preparation&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Identify a separate location for the CONNECT Edition configuration, this must be in a separate location to the active V8i Workspace, even if only in a different root folder on a network share.&lt;/span&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Identify custom dataset content used in V8i, this could be cell libraries, DGNLIBs, XML files, etc. Ideally this content will be in separate folders and files from Bentley&amp;#39;s example dataset, however it may well be&amp;nbsp; mixed in alongside delivered content. This will depend on how the V8i Workspace was organised.&lt;/span&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decide how the example dataset(s) will be used. There are two main options.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Use as is accepting that some of the example content will not suit your situation. This means that when a new dataset is released it can simply replace the existing version without affecting any customisations.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Take ownership of the example dataset, modifying it as needed. This requires both a different approach when a new dataset is released and an organised approach to the creation and storage of custom content. Custom content should always be contained in clearly identified files to enable any changed files from Bentley to be added/replaced/deleted. Changes introduced by new versions are listed in the dataset delta document and must be implemented manually.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decide where the dataset(s) will be located. There are two options.*&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;In the Custom Configuration (recommended). This is suitable for either of the options 1 or 2 above.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the local machine. This only applies if the delivered dataset is used unchanged, option 1 above, unless some external process is available to synchronize any customizations to the local copy.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="padding-left:30px;"&gt;These are discussed in more detail in&amp;nbsp;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/51041/dataset-strategies---local-or-network" rel="noopener noreferrer" target="_blank"&gt;Dataset Strategies - Local or Network&lt;/a&gt;.&amp;nbsp; If datasets on a local machine are preferred please refer to&amp;nbsp;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/50875/configuring-the-datasets-root-folder-location"&gt;&lt;span lang="en-US"&gt;Configuring the Datasets Root Folder Location&lt;/span&gt;&lt;/a&gt;.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:inherit;"&gt;&lt;/span&gt;*Note: &lt;a href="/products/projectwise/content_management/w/wiki/53045/projectwise-drive" rel="noopener noreferrer" target="_blank"&gt;ProjectWise 365 Drive&lt;/a&gt; will become an option for sharing configurations and synchronising their content to local machines&amp;nbsp;when additional features are released late in 2021.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Plan the implementation of access control via Windows File/Folder permissions to Organization, WorkSpace and WorkSet levels, the purpose of which is to ensure that only the responsible people are able to modify shared content:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Organization: Read-only to non-admin users.&lt;/li&gt;
&lt;li&gt;WorkSpaces: Write access to appropriate administrators, this may include BIM Coordinator type roles depending on organizational structure.&lt;/li&gt;
&lt;li&gt;WorkSets: Write access to all relevant users.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h1&gt;Step 2: Directing OpenBuildings Designer to a Network Location&lt;/h1&gt;
&lt;p&gt;This is described in Exercise 1: Installing OpenBuildings Designer Configured to a Network Location.&lt;/p&gt;
&lt;p&gt;The location of a custom configuration is stored in ConfigurationSetup.cfg on each machine. This is the only file that needs to be modified to redirect a machine to a custom configuration.&amp;nbsp;The configured location does not have to be available when OpenBuildings Designer is installed, the path will be ignored unless WorkSpace CFG files are present.&lt;/p&gt;
&lt;p&gt;If OpenBuildings Designer is already installed ConfigurationSetup.cfg can be updated as described in &lt;a href="/products/projectwise/content_management/w/wiki/53045/projectwise-drive" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - Configuration Tips : Should I edit ConfigurationSetup.cfg?&lt;/a&gt;&lt;/p&gt;
&lt;h1&gt;Step 3:&amp;nbsp;Populate the Custom Configuration&lt;/h1&gt;
&lt;p&gt;Creating the required folder structure is outlined in Exercise 2: Setting Up the Organization and WorkSpace Folders.&lt;/p&gt;
&lt;p&gt;This is a typical example where the Datasets are located in the Custom Configuration under ...\OBD_Resources\Datasets\; one WorkSpace named ActiveProjects_365 is contained in the WorkSpaces folder.&lt;/p&gt;
&lt;table border="1" height="789"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td rowspan="3"&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635168631491v2.png" /&gt;&lt;/td&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;Datasets:&lt;/p&gt;
&lt;p&gt;Unless configured otherwise the Catalog User Interface will treat the active Dataset as the Organisation level&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635169877994v3.png" /&gt;&lt;/p&gt;
&lt;p&gt;Organization level Custom content may be stored here depending on the decision discussed above about use of delivered datasets.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;Organization:&lt;/p&gt;
&lt;p&gt;Unless configured otherwise the Organization subfolders contain shared platform or ProStructures content directed to by Standards.cfg and some &lt;span&gt;ProStructures&amp;nbsp;&lt;/span&gt;CFG files. Any content here will be available to all users unless configured otherwise.&lt;/p&gt;
&lt;p&gt;There are no OpenBuildings specific folders.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;WorkSpaces:&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The Catalog User Interface will recognize the&amp;nbsp;WorkSpaces folder as the WorkSpaces&amp;nbsp;level.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Any content here will be available to&amp;nbsp;only to&amp;nbsp;users of the active WorkSpace.&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Step 4: Create WorkSets&lt;/h1&gt;
&lt;p&gt;The default WorkSet location will be in the WorkSets folder within the Custom Configuration. Obviously project data is not a sub-set of an application. WorkSet folders will need to be in the appropriate project data location. This is covered by&amp;nbsp;Exercise 5: Moving the WorkSets to a Separate Drive, the essential part of which is editing the _USTN_WORKSETROOT path in all WorkSpace CFG files. In this example that file is&amp;nbsp;ActiveProjects_365.cfg and it needs to contain a line defining&amp;nbsp;&lt;span&gt;_USTN_WORKSETROOT as pointing to the project data location, for example P:\ActiveProjects\OBD_AU_Demo\, e.g.:&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;em&gt;_USTN_WORKSETROOT = P:/ActiveProjects/$(_USTN_WORKSETNAME)/&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Create a new WorkSet by copying the appropriate regional WorkSet example, e.g.&amp;nbsp;BuildingTemplate_AU.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The&amp;nbsp;BuildingTemplate_AU folder should be copied to the project data location&lt;/li&gt;
&lt;li&gt;BuildingTemplate_AU.cfg should be copied to the WorkSets folder.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Both must be renamed with the new project name, folder and CFG file names must match, this is what links them together.&lt;/p&gt;
&lt;p&gt;Once the example WorkSet has been copied, but before adding any V8i content or making site specific changes to folder structures, test the new Custom Configuration. Review any messages displayed in the Message Center or elsewhere in the UI taking appropriate action to rectify them.&lt;/p&gt;
&lt;h1&gt;Step 5: Add previous custom content.&lt;/h1&gt;
&lt;p&gt;check against dataset delta documents to see if any V8i files are now obsolete. For instance V8i curtain walls are superseded by the CONNECT Edition tools, earlier content will not work with the new tool.&lt;/p&gt;
&lt;p&gt;Add V8i files in the appropriate locations at&amp;nbsp;&lt;span&gt;Organization, WorkSpace or WorkSet levels.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Test that the&amp;nbsp;content&amp;nbsp;is available&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;Step 6: Modify WorkSet folder names or structure as appropriate to conform with organization standards&lt;/h1&gt;
&lt;p&gt;This step is put at the end of the process so a baseline is established before any site specific changes to&amp;nbsp;folder structures and files names are made. This narrows down the scope of any troubleshooting&amp;nbsp;that may be necessary; when CFG file are being edited even simple typos can cause errors.&lt;/p&gt;
&lt;p&gt;For example,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Test the Custom Configuration to establish that&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Previously identified custom content can be placed in the appropriate folders at Organization, WorkSpace or WorkSet levels.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The&amp;nbsp;decision about how to use delivered dataset content leads to two main scenarios for an upgrade sequence:&lt;/li&gt;
&lt;/ul&gt;
&lt;ol&gt;
&lt;li&gt;Where the delivered dataset has not been modified and all custom families/parts and DataGroup content have been stored in project datasets.&lt;/li&gt;
&lt;li&gt;Where the delivered dataset has been modified by the addition of Company custom families/parts and DataGroup content in addition to those&amp;nbsp;stored in project datasets.&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li&gt;&lt;/li&gt;
&lt;li&gt;Other variations are possible, but the steps to upgrade these two will provide general guidance for similar cases.&lt;/li&gt;
&lt;li&gt;1. Unmodified Delivered Dataset.&lt;/li&gt;
&lt;li&gt;Summary of steps:&lt;/li&gt;
&lt;/ul&gt;
&lt;ol&gt;
&lt;li&gt;....&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Run the Schema Upgrade utility on your project files as described in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479.upgrade-existing-elements-to-current-datagroup-system-properties.aspx"&gt;Upgrade existing elements to current DataGroup System properties&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Run the&amp;nbsp;&lt;/span&gt;&lt;span&gt;Schema&amp;nbsp;&lt;/span&gt;&lt;span&gt;Upgrade utility on existing BB_Floormaster.dgnlib files &amp;lt;link batch script to delete unused contnet&amp;gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Run other Building utilities as required to upgrade project dataset content.&lt;/li&gt;
&lt;li&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li&gt;&lt;/li&gt;
&lt;li&gt;2. Delivered Dataset has Been Modified&lt;/li&gt;
&lt;li&gt;Summary of steps:&lt;/li&gt;
&lt;/ul&gt;
&lt;ol&gt;
&lt;li&gt;Copy existing workspace folders and contents to the new SS6 folder including&amp;nbsp;the Building Dataset(s).&lt;/li&gt;
&lt;li&gt;Copy your Company Dataset (if you have one) folders from SS5 to SS6.&lt;/li&gt;
&lt;li&gt;Follow the steps described in C:\ProgramData\Bentley\AECOsimBuildingDesigner V8i Ss6\WorkSpace\BuildingDatasets\Dataset_&amp;lt;regionCode&amp;gt;\Dataset_&amp;lt;regionCode&amp;gt;_Ss6_delta.pdf to add, delete or modify files in the SS5 dataset to match SS6.&lt;/li&gt;
&lt;li&gt;Run the DataGroup Upgrade utility on your project files as described in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479.upgrade-existing-elements-to-current-datagroup-system-properties.aspx"&gt;Upgrade existing elements to current DataGroup System properties&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Run the&amp;nbsp;&lt;/span&gt;&lt;span&gt;Schema&amp;nbsp;&lt;/span&gt;&lt;span&gt;Upgrade utility on existing BB_Floormaster.dgnlib files&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Run other Building utilities as required to upgrade project dataset content.&lt;/li&gt;
&lt;li&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li&gt;See Also&lt;/li&gt;
&lt;li&gt;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479.upgrade-existing-elements-to-current-datagroup-system-properties.aspx"&gt;Upgrade existing elements to current DataGroup System properties&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/03548.NewLogo.png"&gt;&lt;img style="border-width:0px;" alt=" " height="60" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" width="189" /&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Draft - Content is WiP&lt;/div&gt;
</description></item><item><title>Migrating custom content from AECOsim Building Designer SS6 to a current OpenBuildings Designer version</title><link>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version/revision/4</link><pubDate>Mon, 25 Oct 2021 14:43:21 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:74ea833a-2c67-4860-90b8-05cf1fd96ae0</guid><dc:creator>Marc Thomas</dc:creator><comments>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version#comments</comments><description>Revision 4 posted to OpenBuildings | AECOsim | Speedikon Wiki by Marc Thomas on 10/25/2021 2:43:21 PM&lt;br /&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;" width="30%"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;OpenBuildings Designer&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;CONNECT Edition&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Datasets and content&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Migration/Upgrade&lt;span&gt; &lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2&gt;&lt;em&gt;Draft Wiki.............................................................&lt;/em&gt;&lt;/h2&gt;
&lt;p&gt;This article discusses the migration of dataset content.&lt;/p&gt;
&lt;p&gt;Migration of a V8i Workspace to a CONNECT Edition Configuration is&amp;nbsp;covered by training course&amp;nbsp;&lt;a href="https://learn.bentley.com/app/Public/ViewLearningPathDetails?lpId=113058&amp;amp;aftkn=5527c519-bbc7-4890-9a2e-063edc9da5c0" rel="noopener noreferrer" target="_blank"&gt;BIM Management 301: Installation and Upgrade Guide&lt;/a&gt;, we recommend viewing this training and downloading the course workbook prior to embarking on a migration process.&amp;nbsp;This article will refer to some exercises contained in this training course that cover the creation of CONNECT WorkSpaces and WorkSets.&lt;/p&gt;
&lt;p&gt;A key recommendation is that any &lt;span&gt;CONNECT Edition Configuration should be in a separate folder structure&amp;nbsp;to any existing V8i Workspace; their folder structures&amp;nbsp;and configuration files are significantly different. Using a separate&amp;nbsp;location allows any new Configuration to be tested without affecting&amp;nbsp;an active production Workspace.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The migration of delivered dataset content from SS6 to CONNECT Edition is relatively straightforward as the dataset changes have been minimised for most datasets. Please note the exception to this: due to major changes in British standards the V8i UK/GB dataset is not directly compatible with the CONNECT versions. Please see &lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/35923/connect-edition---british-dataset-migration" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - British Dataset migration&lt;/a&gt;&amp;nbsp;for full details.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Step 1: Preparation&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Identify a separate location for the CONNECT Edition configuration, this must be in a separate location to the active V8i Workspace, even if only in a different root folder on a network share.&lt;/span&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Identify custom dataset content used in V8i, this could be cell libraries, DGNLIBs, XML files, etc. Ideally this content will be in separate folders and files from Bentley&amp;#39;s example dataset, however it may well be&amp;nbsp; mixed in alongside delivered content. This will depend on how the V8i Workspace was organised.&lt;/span&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decide how the example dataset(s) will be used. There are two main options.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Use as is accepting that some of the example content will not suit your situation. This means that when a new dataset is released it can simply replace the existing version without affecting any customisations.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Take ownership of the example dataset, modifying it as needed. This requires both a different approach when a new dataset is released and an organised approach to the creation and storage of custom content. Custom content should always be contained in clearly identified files to enable any changed files from Bentley to be added/replaced/deleted. Changes introduced by new versions are listed in the dataset delta document and must be implemented manually.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decide where the dataset(s) will be located. There are two options.*&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;In the Custom Configuration (recommended). This is suitable for either of the options 1 or 2 above.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the local machine. This only applies if the delivered dataset is used unchanged, option 1 above, unless some external process is available to synchronize any customizations to the local copy.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p style="padding-left:30px;"&gt;These are discussed in more detail in&amp;nbsp;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/51041/dataset-strategies---local-or-network" rel="noopener noreferrer" target="_blank"&gt;Dataset Strategies - Local or Network&lt;/a&gt;.&amp;nbsp; If datasets on a local machine are preferred please refer to&amp;nbsp;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/50875/configuring-the-datasets-root-folder-location"&gt;&lt;span lang="en-US"&gt;Configuring the Datasets Root Folder Location&lt;/span&gt;&lt;/a&gt;.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:inherit;"&gt;&lt;/span&gt;*Note: &lt;a href="/products/projectwise/content_management/w/wiki/53045/projectwise-drive" rel="noopener noreferrer" target="_blank"&gt;ProjectWise 365 Drive&lt;/a&gt; will become an option for sharing configurations and synchronising their content to local machines&amp;nbsp;when additional features are released late in 2021.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Plan the implementation of access control via Windows File/Folder permissions to Organization, WorkSpace and WorkSet levels, the purpose of which is to ensure that only the responsible people are able to modify shared content:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Organization: Read-only to non-admin users.&lt;/li&gt;
&lt;li&gt;WorkSpaces: Write access to appropriate administrators, this may include BIM Coordinator type roles depending on organizational structure.&lt;/li&gt;
&lt;li&gt;WorkSets: Write access to all relevant users.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h1&gt;Step 2: Directing OpenBuildings Designer to a Network Location&lt;/h1&gt;
&lt;p&gt;This is described in Exercise 1: Installing OpenBuildings Designer Configured to a Network Location.&lt;/p&gt;
&lt;p&gt;The location of a custom configuration is stored in ConfigurationSetup.cfg on each machine. This is the only file that needs to be modified to redirect a machine to a custom configuration.&amp;nbsp;The configured location does not have to be available when OpenBuildings Designer is installed, the path will be ignored unless WorkSpace CFG files are present.&lt;/p&gt;
&lt;p&gt;If OpenBuildings Designer is already installed ConfigurationSetup.cfg can be updated as described in &lt;a href="/products/projectwise/content_management/w/wiki/53045/projectwise-drive" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - Configuration Tips : Should I edit ConfigurationSetup.cfg?&lt;/a&gt;&lt;/p&gt;
&lt;h1&gt;Step 3:&amp;nbsp;Populate the Custom Configuration&lt;/h1&gt;
&lt;p&gt;Creating the required folder structure is outlined in Exercise 2: Setting Up the Organization and WorkSpace Folders.&lt;/p&gt;
&lt;p&gt;This is a typical example where the Datasets are located in the Custom Configuration under ...\OBD_Resources\Datasets\; one WorkSpace named ActiveProjects_365 is contained in the WorkSpaces folder.&lt;/p&gt;
&lt;table height="789" width="611"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td rowspan="3"&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635168631491v2.png" /&gt;&lt;/td&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;Datasets:&lt;/p&gt;
&lt;p&gt;Unless configured otherwise the Catalog User Interface will treat the active Dataset as the Organisation level&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/pastedimage1635169877994v3.png" /&gt;&lt;/p&gt;
&lt;p&gt;Organization level Custom content may be stored here depending on the decision discussed above about use of delivered datasets.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;Organization:&lt;/p&gt;
&lt;p&gt;Unless configured otherwise the Organization subfolders contain shared platform or ProStructures content directed to by Standards.cfg and some &lt;span&gt;ProStructures&amp;nbsp;&lt;/span&gt;CFG files. Any content here will be available to all users unless configured otherwise.&lt;/p&gt;
&lt;p&gt;There are no OpenBuildings specific folders.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:left;vertical-align:top;"&gt;
&lt;p&gt;WorkSpaces:&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The Catalog User Interface will recognize the&amp;nbsp;WorkSpaces folder as the WorkSpaces&amp;nbsp;level.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Any content here will be available to&amp;nbsp;only to&amp;nbsp;users of the active WorkSpace.&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Step 4: Create WorkSets&lt;/h1&gt;
&lt;p&gt;The default WorkSet location will be in the WorkSets folder within the Custom Configuration. Obviously project data is not a sub-set of an application. WorkSet folders will need to be in the appropriate project data location. This is covered by&amp;nbsp;Exercise 5: Moving the WorkSets to a Separate Drive, the essential part of which is editing the _USTN_WORKSETROOT path in all WorkSpace CFG files. In this example that file is&amp;nbsp;ActiveProjects_365.cfg and it needs to contain a line defining&amp;nbsp;&lt;span&gt;_USTN_WORKSETROOT as pointing to the project data location, for example P:\ActiveProjects\OBD_AU_Demo\, e.g.:&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;em&gt;_USTN_WORKSETROOT = P:/ActiveProjects/$(_USTN_WORKSETNAME)/&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Create a new WorkSet by copying the appropriate regional WorkSet example, e.g.&amp;nbsp;BuildingTemplate_AU.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The&amp;nbsp;BuildingTemplate_AU folder should be copied to the project data location&lt;/li&gt;
&lt;li&gt;BuildingTemplate_AU.cfg should be copied to the WorkSets folder.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Both must be renamed with the new project name, folder and CFG file names must match, this is what links them together.&lt;/p&gt;
&lt;p&gt;Once the example WorkSet has been copied, but before adding any V8i content or making site specific changes to folder structures, test the new Custom Configuration. Review any messages displayed in the Message Center or elsewhere in the UI taking appropriate action to rectify them.&lt;/p&gt;
&lt;h1&gt;Step 5: Add previous custom content.&lt;/h1&gt;
&lt;p&gt;check against dataset delta documents to see if any V8i files are now obsolete. For instance V8i curtain walls are superseded by the CONNECT Edition tools, earlier content will not work with the new tool.&lt;/p&gt;
&lt;p&gt;Add V8i files in the appropriate locations at&amp;nbsp;&lt;span&gt;Organization, WorkSpace or WorkSet levels.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Test that the&amp;nbsp;content&amp;nbsp;is available&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;Step 6: Modify WorkSet folder names or structure as appropriate to conform with organization standards&lt;/h1&gt;
&lt;p&gt;This step is put at the end of the process so a baseline is established before any site specific changes to&amp;nbsp;folder structures and files names are made. This narrows down the scope of any troubleshooting&amp;nbsp;that may be necessary; when CFG file are being edited even simple typos can cause errors.&lt;/p&gt;
&lt;p&gt;For example,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Test the Custom Configuration to establish that&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Previously identified custom content can be placed in the appropriate folders at Organization, WorkSpace or WorkSet levels.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The&amp;nbsp;decision about how to use delivered dataset content leads to two main scenarios for an upgrade sequence:&lt;/li&gt;
&lt;/ul&gt;
&lt;ol&gt;
&lt;li&gt;Where the delivered dataset has not been modified and all custom families/parts and DataGroup content have been stored in project datasets.&lt;/li&gt;
&lt;li&gt;Where the delivered dataset has been modified by the addition of Company custom families/parts and DataGroup content in addition to those&amp;nbsp;stored in project datasets.&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li&gt;&lt;/li&gt;
&lt;li&gt;Other variations are possible, but the steps to upgrade these two will provide general guidance for similar cases.&lt;/li&gt;
&lt;li&gt;1. Unmodified Delivered Dataset.&lt;/li&gt;
&lt;li&gt;Summary of steps:&lt;/li&gt;
&lt;/ul&gt;
&lt;ol&gt;
&lt;li&gt;....&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Run the Schema Upgrade utility on your project files as described in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479.upgrade-existing-elements-to-current-datagroup-system-properties.aspx"&gt;Upgrade existing elements to current DataGroup System properties&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Run the&amp;nbsp;&lt;/span&gt;&lt;span&gt;Schema&amp;nbsp;&lt;/span&gt;&lt;span&gt;Upgrade utility on existing BB_Floormaster.dgnlib files &amp;lt;link batch script to delete unused contnet&amp;gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Run other Building utilities as required to upgrade project dataset content.&lt;/li&gt;
&lt;li&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li&gt;&lt;/li&gt;
&lt;li&gt;2. Delivered Dataset has Been Modified&lt;/li&gt;
&lt;li&gt;Summary of steps:&lt;/li&gt;
&lt;/ul&gt;
&lt;ol&gt;
&lt;li&gt;Copy existing workspace folders and contents to the new SS6 folder including&amp;nbsp;the Building Dataset(s).&lt;/li&gt;
&lt;li&gt;Copy your Company Dataset (if you have one) folders from SS5 to SS6.&lt;/li&gt;
&lt;li&gt;Follow the steps described in C:\ProgramData\Bentley\AECOsimBuildingDesigner V8i Ss6\WorkSpace\BuildingDatasets\Dataset_&amp;lt;regionCode&amp;gt;\Dataset_&amp;lt;regionCode&amp;gt;_Ss6_delta.pdf to add, delete or modify files in the SS5 dataset to match SS6.&lt;/li&gt;
&lt;li&gt;Run the DataGroup Upgrade utility on your project files as described in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479.upgrade-existing-elements-to-current-datagroup-system-properties.aspx"&gt;Upgrade existing elements to current DataGroup System properties&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Run the&amp;nbsp;&lt;/span&gt;&lt;span&gt;Schema&amp;nbsp;&lt;/span&gt;&lt;span&gt;Upgrade utility on existing BB_Floormaster.dgnlib files&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Run other Building utilities as required to upgrade project dataset content.&lt;/li&gt;
&lt;li&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li&gt;See Also&lt;/li&gt;
&lt;li&gt;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479.upgrade-existing-elements-to-current-datagroup-system-properties.aspx"&gt;Upgrade existing elements to current DataGroup System properties&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/03548.NewLogo.png"&gt;&lt;img style="border-width:0px;" alt=" " height="60" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" width="189" /&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Draft - Content is WiP&lt;/div&gt;
</description></item><item><title>Migrating custom content from AECOsim Building Designer SS6 to a current OpenBuildings Designer version</title><link>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version/revision/3</link><pubDate>Mon, 25 Oct 2021 12:26:06 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:74ea833a-2c67-4860-90b8-05cf1fd96ae0</guid><dc:creator>Marc Thomas</dc:creator><comments>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version#comments</comments><description>Revision 3 posted to OpenBuildings | AECOsim | Speedikon Wiki by Marc Thomas on 10/25/2021 12:26:06 PM&lt;br /&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;" width="30%"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;OpenBuildings Designer&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;CONNECT Edition&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Datasets and content&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Migration/Upgrade&lt;span&gt; &lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2&gt;&lt;em&gt;Draft Wiki.............................................................&lt;/em&gt;&lt;/h2&gt;
&lt;p&gt;This article covers the migration of dataset content.&lt;/p&gt;
&lt;p&gt;Migration of a V8i Workspace to a CONNECT Edition Configuration is&amp;nbsp;covered by training course&amp;nbsp;&lt;a href="https://learn.bentley.com/app/Public/ViewLearningPathDetails?lpId=113058&amp;amp;aftkn=5527c519-bbc7-4890-9a2e-063edc9da5c0" rel="noopener noreferrer" target="_blank"&gt;BIM Management 301: Installation and Upgrade Guide&lt;/a&gt;, we recommend viewing this training prior to embarking on a migration process.&amp;nbsp;This article will refer to exercises contained in this training course.&lt;/p&gt;
&lt;p&gt;A key recommendation is that any &lt;span&gt;CONNECT Edition Configuration should be in a separate folder structure&amp;nbsp;to any existing V8i Workspace; their folder structures&amp;nbsp;and configuration files are significantly different. Using a separate&amp;nbsp;location allows any new Configuration to be tested without affecting&amp;nbsp;an active production Workspace.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The migration of delivered dataset content from SS6 to CONNECT Edition is relatively straightforward as the dataset changes have been minimised for most datasets. Please note the exception to this: due to major changes in British standards the V8i UK/GB dataset is not directly compatible with the CONNECT versions. Please see &lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/35923/connect-edition---british-dataset-migration" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - British Dataset migration&lt;/a&gt;&amp;nbsp;for full details.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Preparation:&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Identify a separate location for the CONNECT Edition configuration, this must be in a separate location to the active V8i Workspace, even if only in a different root folder on a network share.&lt;/span&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Identify custom dataset content, this could be cell libraries, DGNLIBs, XML files, etc. Ideally this content will be in separate folders and files from Bentley&amp;#39;s example dataset, however it may well be&amp;nbsp; mixed in alongside delivered content. This will depend on how the V8i Workspace was organised.&lt;/span&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decide how the example dataset(s) will be used. There are two main options.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Use as is accepting that some of the example content will not suit your situation. This means that when a new dataset is released it can simply replace the existing version without affecting any customisations.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Take ownership of the dataset, modifying it as needed. This requires both a different approach when a new dataset is released and an organised approach to the creation and storage of custom content. Custom content should always be contained in clearly identified files to enable any changed files from Bentley to be added/replaced/deleted. Changes introduced by new versions are listed in the dataset delta document and must be implemented manually.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decide where the dataset(s) will be located. There are two options.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;In the Custom Configuration (recommended) . This is suitable for either of the options 1 or 2 above.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the local machine. This only applies if the delivered dataset is used unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The&amp;nbsp;decision about how to use delivered dataset content leads to two main scenarios for an upgrade sequence:&lt;/li&gt;
&lt;/ul&gt;
&lt;ol&gt;
&lt;li&gt;Where the delivered dataset has not been modified and all custom families/parts and DataGroup content have been stored in project datasets.&lt;/li&gt;
&lt;li&gt;Where the delivered dataset has been modified by the addition of Company custom families/parts and DataGroup content in addition to those&amp;nbsp;stored in project datasets.&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li&gt;&lt;/li&gt;
&lt;li&gt;Other variations are possible, but the steps to upgrade these two will provide general guidance for similar cases.&lt;/li&gt;
&lt;li&gt;1. Unmodified Delivered Dataset.&lt;/li&gt;
&lt;li&gt;Summary of steps:&lt;/li&gt;
&lt;/ul&gt;
&lt;ol&gt;
&lt;li&gt;....&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Run the Schema Upgrade utility on your project files as described in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479.upgrade-existing-elements-to-current-datagroup-system-properties.aspx"&gt;Upgrade existing elements to current DataGroup System properties&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Run the&amp;nbsp;&lt;/span&gt;&lt;span&gt;Schema&amp;nbsp;&lt;/span&gt;&lt;span&gt;Upgrade utility on existing BB_Floormaster.dgnlib files &amp;lt;link batch script to delete unused contnet&amp;gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Run other Building utilities as required to upgrade project dataset content.&lt;/li&gt;
&lt;li&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li&gt;&lt;/li&gt;
&lt;li&gt;2. Delivered Dataset has Been Modified&lt;/li&gt;
&lt;li&gt;Summary of steps:&lt;/li&gt;
&lt;/ul&gt;
&lt;ol&gt;
&lt;li&gt;Copy existing workspace folders and contents to the new SS6 folder including&amp;nbsp;the Building Dataset(s).&lt;/li&gt;
&lt;li&gt;Copy your Company Dataset (if you have one) folders from SS5 to SS6.&lt;/li&gt;
&lt;li&gt;Follow the steps described in C:\ProgramData\Bentley\AECOsimBuildingDesigner V8i Ss6\WorkSpace\BuildingDatasets\Dataset_&amp;lt;regionCode&amp;gt;\Dataset_&amp;lt;regionCode&amp;gt;_Ss6_delta.pdf to add, delete or modify files in the SS5 dataset to match SS6.&lt;/li&gt;
&lt;li&gt;Run the DataGroup Upgrade utility on your project files as described in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479.upgrade-existing-elements-to-current-datagroup-system-properties.aspx"&gt;Upgrade existing elements to current DataGroup System properties&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Run the&amp;nbsp;&lt;/span&gt;&lt;span&gt;Schema&amp;nbsp;&lt;/span&gt;&lt;span&gt;Upgrade utility on existing BB_Floormaster.dgnlib files&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Run other Building utilities as required to upgrade project dataset content.&lt;/li&gt;
&lt;li&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li&gt;See Also&lt;/li&gt;
&lt;li&gt;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479.upgrade-existing-elements-to-current-datagroup-system-properties.aspx"&gt;Upgrade existing elements to current DataGroup System properties&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/03548.NewLogo.png"&gt;&lt;img style="border-width:0px;" alt=" " height="60" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" width="189" /&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Draft - Content is WiP&lt;/div&gt;
</description></item><item><title>Migration from AECOsim Building Designer SS6 to a current OpenBuildings Designer version</title><link>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version/revision/2</link><pubDate>Thu, 21 Oct 2021 15:59:11 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:74ea833a-2c67-4860-90b8-05cf1fd96ae0</guid><dc:creator>Marc Thomas</dc:creator><comments>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version#comments</comments><description>Revision 2 posted to OpenBuildings | AECOsim | Speedikon Wiki by Marc Thomas on 10/21/2021 3:59:11 PM&lt;br /&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;" width="30%"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;OpenBuildings Designer&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;CONNECT Edition&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Datasets and content&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Migration/Upgrade&lt;span&gt; &lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2&gt;&lt;em&gt;Draft Wiki.............................................................&lt;/em&gt;&lt;/h2&gt;
&lt;p&gt;This article covers the migration of dataset content.&lt;/p&gt;
&lt;p&gt;Migration of a V8i Workspace to a CONNECT Edition Configuration is covered by training material &lt;a href="https://learn.bentley.com/app/Public/ViewLearningPathDetails?lpId=113058&amp;amp;aftkn=5527c519-bbc7-4890-9a2e-063edc9da5c0" rel="noopener noreferrer" target="_blank"&gt;BIM Management 301: Installation and Upgrade Guide&lt;/a&gt;, we recommend viewing this training prior to embarking on a migration process.&lt;/p&gt;
&lt;p&gt;A key recommendation is that any &lt;span&gt;CONNECT Edition Configuration should be in a separate folder structure&amp;nbsp;to any existing V8i Workspace; their folder structures&amp;nbsp;and configuration files are significantly different. Using a separate&amp;nbsp;location allows any new Configuration to be tested without affecting&amp;nbsp;an active production Workspace.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The dataset migration from SS6 to CONNECT Edition is relatively straightforward as the dataset changes have been minimised for most datasets. Please note the exception to this, due to major changes in British standards, is the UK/GB dataset. Please see &lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/35923/connect-edition---british-dataset-migration" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - British Dataset migration&lt;/a&gt;&amp;nbsp;for full details.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Preparation:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Identify custom dataset content, this could be cell libraries, DGNLIBs, XML files, etc. Ideally this content will be in separate folders and files from Bentley&amp;#39;s example dataset, however it may well be&amp;nbsp; mixed in alongside delivered content. This will depend on how the V8i Workspace was organised.&lt;/li&gt;
&lt;li&gt;Identify a separate location for the CONNECT Edition configuration, this must be in a separate location to the active V8i Workspace, even if only in a different root folder on a network share.&lt;/li&gt;
&lt;li&gt;Decide how the example dataset(s) will be used. There are two options.
&lt;ol&gt;
&lt;li&gt;Use as is accepting that some of the example content will not suit your situation. This means that when a new dataset is released it can simply replace the existing version without affecting any customisations.&lt;/li&gt;
&lt;li&gt;Take ownership of the dataset modifying it as needed. This requires both a different approach when a new dataset is released and an organised approach to the creation and storage of custom content. Custom content should always be contained in clearly identified files to enable any changed files from Bentley to be added/replaced/deleted. Changes are listed in the dataset delta document and must be implemented manually.&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;There are two main scenarios for an upgrade sequence&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Where the delivered dataset has not been modified and all custom families/parts and DataGroup content have been stored in project datasets.&lt;/li&gt;
&lt;li&gt;Where the delivered dataset has been modified by the addition of Company custom families/parts and DataGroup content in addition to those&amp;nbsp;stored in project datasets.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Other variations are possible, but the steps to upgrade these two will provide general guidance for similar cases.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The following section is in draft................................................................................................................&lt;/em&gt;&lt;/p&gt;
&lt;h1&gt;1. Unmodified Delivered Dataset.&lt;/h1&gt;
&lt;p&gt;Summary of steps:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;....&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Run the Schema Upgrade utility on your project files as described in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479.upgrade-existing-elements-to-current-datagroup-system-properties.aspx"&gt;Upgrade existing elements to current DataGroup System properties&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Run the&amp;nbsp;&lt;/span&gt;&lt;span&gt;Schema&amp;nbsp;&lt;/span&gt;&lt;span&gt;Upgrade utility on existing BB_Floormaster.dgnlib files &amp;lt;link batch script to delete unused contnet&amp;gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Run other Building utilities as required to upgrade project dataset content.&lt;/li&gt;
&lt;li&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;2. Delivered Dataset has Been Modified&lt;/h1&gt;
&lt;p&gt;Summary of steps:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Copy existing workspace folders and contents to the new SS6 folder including&amp;nbsp;the Building Dataset(s).&lt;/li&gt;
&lt;li&gt;Copy your Company Dataset (if you have one) folders from SS5 to SS6.&lt;/li&gt;
&lt;li&gt;Follow the steps described in C:\ProgramData\Bentley\AECOsimBuildingDesigner V8i Ss6\WorkSpace\BuildingDatasets\Dataset_&amp;lt;regionCode&amp;gt;\Dataset_&amp;lt;regionCode&amp;gt;_Ss6_delta.pdf to add, delete or modify files in the SS5 dataset to match SS6.&lt;/li&gt;
&lt;li&gt;Run the DataGroup Upgrade utility on your project files as described in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479.upgrade-existing-elements-to-current-datagroup-system-properties.aspx"&gt;Upgrade existing elements to current DataGroup System properties&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Run the&amp;nbsp;&lt;/span&gt;&lt;span&gt;Schema&amp;nbsp;&lt;/span&gt;&lt;span&gt;Upgrade utility on existing BB_Floormaster.dgnlib files&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Run other Building utilities as required to upgrade project dataset content.&lt;/li&gt;
&lt;li&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479.upgrade-existing-elements-to-current-datagroup-system-properties.aspx"&gt;Upgrade existing elements to current DataGroup System properties&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/03548.NewLogo.png"&gt;&lt;img style="border-width:0px;" alt=" " height="60" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" width="189" /&gt;&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Draft - Content is WiP&lt;/div&gt;
</description></item><item><title>Migration from AECOsim Building Designer SS6 to a current OpenBuildings Designer version</title><link>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version/revision/1</link><pubDate>Fri, 08 Oct 2021 09:06:30 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:74ea833a-2c67-4860-90b8-05cf1fd96ae0</guid><dc:creator>Marc Thomas</dc:creator><comments>https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/56451/migrating-custom-content-from-aecosim-building-designer-ss6-to-a-current-openbuildings-designer-version#comments</comments><description>Revision 1 posted to OpenBuildings | AECOsim | Speedikon Wiki by Marc Thomas on 10/8/2021 9:06:30 AM&lt;br /&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;" width="30%"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;OpenBuildings Designer&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;CONNECT Edition&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Datasets and content&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Migration/Upgrade&lt;span&gt; &lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2&gt;&lt;em&gt;Draft Wiki.............................................................&lt;/em&gt;&lt;/h2&gt;
&lt;p&gt;This article covers the migration of dataset content.&lt;/p&gt;
&lt;p&gt;Migration of a V8i Workspace to a CONNECT Edition Configuration is covered by training material &lt;a href="https://learn.bentley.com/app/Public/ViewLearningPathDetails?lpId=113058&amp;amp;aftkn=5527c519-bbc7-4890-9a2e-063edc9da5c0" rel="noopener noreferrer" target="_blank"&gt;BIM Management 301: Installation and Upgrade Guide&lt;/a&gt;. The&lt;span&gt;&amp;nbsp;CONNECT Edition Configuration should be in a separate folder structure&amp;nbsp;to any existing V8i Workspace. Their folder structures&amp;nbsp;and configuration files are significantly different. Using a separate&amp;nbsp;location allows any new Configuration to be tested without affecting&amp;nbsp;an active production Workspace.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The dataset migration from SS6 to CONNECT Edition is relatively straightforward, the dataset changes have been minimised for most datasets. Please note the exception to this, due to major changes in British standards, is the UK/GB dataset, please see &lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/35923/connect-edition---british-dataset-migration" rel="noopener noreferrer" target="_blank"&gt;CONNECT Edition - British Dataset migration&lt;/a&gt;&amp;nbsp;for full details.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;There are two main scenarios for an upgrade sequence&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Where the delivered dataset has not been modified and all custom families/parts and DataGroup content have been stored in project datasets.&lt;/li&gt;
&lt;li&gt;Where the delivered dataset has been modified by the addition of Company custom families/parts and DataGroup content in addition to those&amp;nbsp;stored in project datasets.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Other variations are possible, but the steps to upgrade these two will provide general guidance for similar cases.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The following section is in draft................................................................................................................&lt;/em&gt;&lt;/p&gt;
&lt;h1&gt;1. Unmodified Delivered Dataset.&lt;/h1&gt;
&lt;p&gt;Summary of steps:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;....&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Run the Schema Upgrade utility on your project files as described in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479.upgrade-existing-elements-to-current-datagroup-system-properties.aspx"&gt;Upgrade existing elements to current DataGroup System properties&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Run the&amp;nbsp;&lt;/span&gt;&lt;span&gt;Schema&amp;nbsp;&lt;/span&gt;&lt;span&gt;Upgrade utility on existing BB_Floormaster.dgnlib files &amp;lt;link batch script to delete unused contnet&amp;gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Run other Building utilities as required to upgrade project dataset content.&lt;/li&gt;
&lt;li&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h1&gt;2. Delivered Dataset has Been Modified&lt;/h1&gt;
&lt;p&gt;Summary of steps:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Copy existing workspace folders and contents to the new SS6 folder including&amp;nbsp;the Building Dataset(s).&lt;/li&gt;
&lt;li&gt;Copy your Company Dataset (if you have one) folders from SS5 to SS6.&lt;/li&gt;
&lt;li&gt;Follow the steps described in C:\ProgramData\Bentley\AECOsimBuildingDesigner V8i Ss6\WorkSpace\BuildingDatasets\Dataset_&amp;lt;regionCode&amp;gt;\Dataset_&amp;lt;regionCode&amp;gt;_Ss6_delta.pdf to add, delete or modify files in the SS5 dataset to match SS6.&lt;/li&gt;
&lt;li&gt;Run the DataGroup Upgrade utility on your project files as described in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479.upgrade-existing-elements-to-current-datagroup-system-properties.aspx"&gt;Upgrade existing elements to current DataGroup System properties&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Run the&amp;nbsp;&lt;/span&gt;&lt;span&gt;Schema&amp;nbsp;&lt;/span&gt;&lt;span&gt;Upgrade utility on existing BB_Floormaster.dgnlib files&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Run other Building utilities as required to upgrade project dataset content.&lt;/li&gt;
&lt;li&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;&lt;a href="/products/building/building_analysis___design/w/building_analysis_and_design__wiki/10479.upgrade-existing-elements-to-current-datagroup-system-properties.aspx"&gt;Upgrade existing elements to current DataGroup System properties&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-17/03548.NewLogo.png"&gt;&lt;img style="border-width:0px;" alt=" " height="60" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" width="189" /&gt;&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Draft - Content is WiP&lt;/div&gt;
</description></item></channel></rss>