Aidas Vaiksnoras's Communities Activities

Technical requirements

Aidas Vaiksnoras — Wed, 19 Aug 2020 15:24:26 GMT

The iTwin Synchronizer Portal does not require any client software or plug-in to be installed on your computer. Below you will find information about supported browsers to provide you the best synchronization experience.

Browser Support

iTwin Synchronizer Portal is supported on the latest versions of these browsers.

Chrome
Firefox
Safari
Opera
Edge "New Chromium-based version"

Data Center hosting information

iTwin Synchronizer Portal is supported in these data centers:

East US
UK South
Australia East
Japan East
South East Asie
South Africa North
Canada Central
North Europe

Data center will be chosen based on the ProjectWise project property called "Data Center Locations".

Supported File Formats

Laisvune Valackaite — Mon, 23 Mar 2020 14:25:34 GMT

A wide array of design applications are supported in synchronization workflows, ensuring all your engineering data can be aggregated into a single digital twin environment.

You can find the latest list of supported iTwin Connectors here: https://developer.bentley.com/apis/synchronization/supported-formats/

If you are interested in iTwin Synchronizer Client supported connectors, here are the differences from the main list:

Bentley Design Applications	File Extensions	Connection Type	iTwin Synchronizer Client	Supported Versions
OpenRoads ConceptStation	dgndb	ConceptStation		10.0.15.138 and higher
OpenTower Designer	otxml	OpenTower	not supported
AutoPLANT Modeler	dwg	AutoPlant	not supported
Intergraph Smart 3D Review	vue	VUE	not supported
ESRI File Geodatabase		Geo
Oracle Spatial		Geo		12c, 18c and 19c
PostGIS database		Geo
SQL Spatial Database		Geo		2019
VUE	vue	VUE	not supported

If you do not see required connector, you can fill out the idea in your main design review portal ideas page.

The following table list the applications currently supported and the different ways available to sync the data to an iTwin.

Bentley Design Applications	File Extensions	Connection Type	iTwin Synchronizer		Application	ProjectWise	Supported Versions
Bentley Design Applications	File Extensions	Connection Type	Client	Portal	Application	ProjectWise	Supported Versions
AutoPLANT Modeler	dwg	AutoPlant		•	•	•*	10.01.00.67 and higher
Bentley Raceway and Cable Management	dgn	MicroStation	•	•		•	CONNECT from Update 4
MicroStation CONNECT / V8i Editions	dgn, i.dgn	MicroStation	•	•		•	CONNECT / V8i Editions
OpenBridge Designer	dgn	Civil	•	•			CONNECT Edition
OpenBuildings Designer	dgn	OpenBuildings	•	•**			CONNECT Edition
OpenPlant Modeler	dgn				•		CONNECT from Update 7
OpenPlant PID	dgn				•		CONNECT from Update 7
OpenRail Designer	dgn	Civil	•	•			CONNECT Edition
OpenRoads ConceptStation	dgndb	ConceptStation	•				10.0.15.138 and higher
OpenRoads Designer	dgn	Civil	•	•			CONNECT Edition
OpenSite Designer	dgn	Civil	•	•			CONNECT Edition
OpenTower Designer	otxml	OpenTower		•			CONNECT from Update 2
ProStructures	dgn	ProStructures***	•	•			CONNECT from Update 6

* Note that AutoPlant does not support legacy ProjectWise connections for Portal synchronizations.

**Note because of OpenBuilding Designers' requirement to run with a workspace OpenBuilding Connector is not an available option when using ProjectShare.

***ProStructure is embed inside multiple products like Open Bridge Modeler, OpenPlant Modeler. There is a limitation with connectors that only one connector can process one dgn so if the ProStructure components are inserted inside a dgn with the parent products components then the parent connector will take the ownership. It will publish the ProStructure components graphics but not the properties. So please make sure that ProStructure data is kept in a separate dgn when invoked from OpenBridge or OpenPlant.

3rd Party Design Applications	File Extensions	Connection Type	iTwin Synchronizer		Application	Supported Versions
3rd Party Design Applications	File Extensions	Connection Type	Client	Portal	Application	Supported Versions
3D Studio	3ds	MicroStation	•	•
AutoCAD	dwg, dxf	AutoCAD Dwg	•	•		2015 - 2023
AVEVA E3D	N/A	Open 3D			•	1.x.x - 2.2.x.x
AVEVA PDMS	N/A	Open 3D			•	12.0 and 12.1
Civil 3D	dwg	Civil 3D	•	•		2015 - 2023
Intergraph Smart 3D	N/A	Open 3D			•	2009.1 - 2016
Intergraph Smart 3D Review	vue	VUE		•
Intergraph Smart Instrumentation	N/A	Smart Instrumentation			•	2016
Intergraph Smart P&ID	zip	SmartPlant P&ID	•	•		2014 R1, 2019
Navisworks	nwd, nwc	Navisworks	•	•		2013 - 2023
Revit	rvt	Revit	•	•		2015 -2023
Rhino	3dm	MicroStation	•	•
Sketchup	skp	MicroStation	•	•		2017-2022

Interchange Formats	Connection Type	iTwin Synchronizer		Application	Supported Versions
Interchange Formats	Connection Type	Client	Portal	Application	Supported Versions
ACIS (.sat)	MicroStation (via dgn)	•	•		Up to 25.0
ArcGIS Feature Service	Geo	•	•		10.6 and higher
Autodesk 3DS Max	MicroStation	•	•
CGM	MicroStation (via dgn)	•	•		1.0
Collada (.dae)	MicroStation (via dgn)	•	•
DXF	AutoCAD	•	•		2015-2021
ESRI File Geodatabase	Geo	•
FBX	MicroStation	•	•		Up to and including 2011
Geojson	Geo	•	•
IFC	IFC	•	•		IFC2x3, IFC4, IFC4.3
IGES (.igs)	MicroStation (via dgn)	•	•		2.0, 3.0, 4.0, or 5.0 fixed-length ASCII
i-model	MicroStation	•	•
JT	MicroStation (via dgn)	•	•		8.0 - 10.6
kml / kmz	Geo	•	•
Land XML	MicroStation (via dgn)	•	•
MIF / MID	MicroStation (via dgn)	•	•
OBJ	MicroStation	•	•
Oracle Spatial	Geo	•			12c, 18c and 19c
Parasolid (.x_t)	MicroStation (via dgn)	•	•		Up to 13.0
PostGIS database	Geo	•
Shape files (.SHP)	Geo	•	•
Sketchup (.SKP)	MicroStation	•	•		2017-2022
SQL Spatial Database	Geo	•			2019
STEP (.stp)	MicroStation (via dgn)	•	•
STL	MicroStation (via dgn)	•	•
SVG	MicroStation (via dgn)	•	•
VRML	MicroStation (via dgn)	•	•
VUE	VUE		•
Web Feature Service (WFS)	Geo	•	•

How to work with file types, which use the MicroStation Connector?

Some file types are listed as being supported by "MicroStation" under the connector type and these can be synchronized directly with the MicroStation Connector. Examples of this are FBX, OBJ and SKP. Other file types that are listed as "MicroStation (via dgn)" must first be imported into MicroStation and saved as a dgn, then the MicroStation Connector can be used to synchronize the dgn into an iModel.

Note for .imodel files, they must be referenced into a DGN file and then an i.dgn must be produced in order for the model to be imported with the MicroStation Connector. Support for .imodel 1.5 and 1.6 versions will be dropped with MicroStation CONNECT Edition Update 17.

Reality Data Support

Reality data, like point clouds and reality meshes, can be viewed along with your engineering data. There are no iModel Connectors to sync reality data, instead use Bentley ContextCapture to add real-world digital context to your iTwins.

For more information on how to associate your reality data to an iTwin go to the [[Reality Data with Context Share]] page.

GeoSpatial Data Support

The GeoConnector is being developed to support geospatial data coming from multiple sources.

Presently, Shapefile, PostGIS database, ESRI File Geodatabase, ArcGIS Feature Service, and WFS(Web Feature Service), KML/KMZ, GeoJSON and Oracle Spatial and SQL Spatial database formats are supported.

For more information on how to use the GeoConnector, visit the GeoConnector page.

Autodesk Materials Support

The Autodesk Material Library consists of several sub-libraries and installers (MSI files) can be taken from installers for Revit, 3dMax or AutoCAD.

Or they can be downloaded separately from the Autodesk site: https://knowledge.autodesk.com/support/infraworks/learn-explore/caas/CloudHelp/cloudhelp/ENU/IWGettingStarted/files/Install/IWGettingStarted-Install-ToInstallAutodeskMaterialLibraries-html-html.html (all resolutions packages are necessary but first Common package isn’t).

It is better to install all Base, Low, Middle, and Advanced Image libraries. At least Base, Middle, and Advanced has unique files.

Materials should be exported to i-model automatically if Autodesk Materials are installed on the machine where the iModel Connector job is executing from.

File formats supported by Navisworks

Navisworks can be used to import the additional formats listed below. This of course requires that the source file is first loaded into Navisworks and then saved as a nwd file. Some formats are not listed in this table such as dgn, dwg, or ifc as examples. When a connector exists for a specific format, the best option is to use the native connector for that file format. However, for instances where a native connector does not exist for that format, using Navisworks for one of the formats listed below can be an option. The listed formats below have been tested and successfully imported into an iTwin from Navisworks.

File Format	Source Application
asm	Solidedge Assembly
asm	Pro/ENGINEER Assembly
catpart	CATIA V5 Part document
dri	PDS
dwf	Autodesk
dwfx	Autodesk
iam	Autodesk Inventor
igs	IGES exchange format
ipt	Autodesk Inventor
model	CATIA V4 model
prt	SolidWorks
prt	NX
prt	Pro/ENGINEER
pts	Leica
ptx	Leica
rte	Revit
rvm	RVM
wrl	VRML
x_b	Parasolid binary

Synchronization Report Knowledge Base

Aidas Vaiksnoras — Mon, 07 Aug 2023 13:12:51 GMT

Dgn_0214

WIP

Dgn_0199

Duplicate data can be introduced in different situations and can cause duplicated data to appear in the iModel, which is not desired.

The most common reasons are:

- Multiple copies of the same reference file used in different master files connections.

- Multiple copies of the same file configured in different connections.

- If using ProjectShare, a folder name change can lead to the creation of duplicates because the file will be identified with a different GUID and is recognized as a duplicate file by synchronization.

- If using ProjectShare, moving the master file or references to a different folder causes file GUID changes and is recognized as a duplicate file by synchronization.

To avoid duplicates data processing into the iModel, please ensure that:

- Only one version of the file is mapped into the iModel.

- Multiple connector types are not used to synchronize the same file.

- In case multiple versions of the same file have been mapped and processed to the model, please unmap the duplicated files from the connection by selecting the option to remove changes from the iModel and reprocess the files.

- Update the design file to remove duplicates and resynchronize the files.

Dgn_0066

There are inconsistencies in the File Identifiers between the ProjectWise data source and the design file. One cause of this is if documents were migrated to a different data source. Please run a Scan References on the master file and then restart the synchronization. If the duplicates issues cannot be solved, please contact Bentley support to diagnose this kind of error: https://bentleysystems.service-now.com/csp further

Read more about why references scanning is important https://docs.bentley.com/LiveContent/web/ProjectWise%20Explorer%20Help-v11/en/GUID-6C52A09F-420A-484E-0EB4-EED0AEE63575.html

Dgn_0205

Dgn_0215

WIP

Revit_0002

Autodesk material files need to be provided manually for synchronization to be able to use them during the synchronization process. If they are not provided in a way that synchronization can access the material files, there will be a message about a particular file is missing. To fix the missing materials issue, please copy the material files from the Autodesk installation location C:\Program Files (x86)\Common Files\Autodesk Shared\Materials\{year of release} to the design file location. In case the Autodesk material library is not installed with the Autodesk product, or you do not have the materials files, use the Autodesk guidelines to install the materials library from the Autodesk website https://help.autodesk.com/view/INFMDR/ENU/?guid=IWGettingStarted_Install_ToInstallAutodeskMaterialLibraries_html. Once the material library is installed, copy the material files to the same folder as the design file and start the synchronization to the Model.

Dgn_0000

Revit_0025

All non-default Windows fonts need to be provided to synchronization manually in order for those fonts to be used. If fonts are placed in the same location as the design file, they will be picked up by synchronization and the missing fonts messages will no longer be reported. Fonts can be copied from C:\Windows\Fonts. If the fonts are missing, the default system font (Bitstream Vera Sans) will be used for synchronization but this can result in visual fidelity issues such as missing characters or incorrect font display size.

Transfer the ownership

Aidas Vaiksnoras — Thu, 10 Sep 2020 10:41:15 GMT

The connection creator becomes its owner. All scheduled synchronizations are done on their behalf and with their access rights.

The ownership rights could be transferred to or taken by any team member who at least once interacted with that iModel and has iModel Manage permisssion. Once the new owner is set, we recommend that you go to that connection in the portal and start it manually to renew the user token. If that team member has not visited the Synchronization portal in the last 30 days, the token would be expired or unknown, so all scheduled synchronizations will fail.
Read the "Token expiration" paragraph to learn more.

NOTE: The owner can not be changed for synchronization in progress.

Email notifications will be sent to the new owner, or original owner if someone took ownership.

Token expiration

All scheduled synchronizations are running on behalf of the connection owner. Such a user access token is valid for 30 days. In the last remaining 10 days, the token is automatically refreshed when the owner visits iTwin Synchronization Portal.

Suppose you will not visit the iTwin Synchronization Portal. In that case, all your owned scheduled connections will start failing due to user authentication issues.

Email notifications:

The owner will receive an email notification when the token expired.

Improvement coming up: email notification before the token expires.

Delete a connection

Joey — Thu, 04 Feb 2021 09:41:04 GMT

You can delete a connection by using the Delete action.

NOTE: You need to have View/Read/Write/Manage iModelHub permission defined in Role Based Access Control.

Delete a connection and associated changes

At the moment, you can make these edits to an iModel when deleting a connection:

Delete a connection but keep already synchronized changes. This will stop future file synchronization, but will not delete the existing changes from an iModel.
Delete a connection along with synchronized changes from an iModel. This will stop future synchronization and will delete those files' data from an iModel.

Files from deleted connections can be synchronized with other connections.

Integrations

Mindaugas Adomavicius — Fri, 22 May 2020 07:02:16 GMT

Available data sources for integration:

ProjectWise Design Integration
iTwin File Service

ProjectWise Design Integration

You can map design files stored in ProjectWise Design Integration with an iModel and synchronize changes. For that, you need to choose ProjectWise Design Integration as a data source.

Prerequisites

To process ProjectWise documents, these products will need to be installed and configured:

ProjectWise Application server
Web Service Gateway. Version info:
- PW WSG plugin version 3.456 or higher is required.

NOTE: The Web Service Gateway URL should be publicly accessible from the internet. It is required for the Azure service to reach out to it and pull files from it.

The latest version of Design applications must be installed on the same machines as the WSG server. For example, MicroStation should be installed if the workspace is using its files.

The latest released versions of the MicroStation, Open Building Designer, and OpenRoads Designer applications could be downloaded from https://softwaredownloads.bentley.com/en/.

NOTE: It is important to open Design applications at least once in a machine. After opening it, specific required files will be created.

Mapping

Follow these steps to connect to ProjectWise Design Integration server:

Define the WSG Server URL and click Get Datasource button
NOTE: Datasource should be accessible to your user.
Select the required data source from the dropdown list
Select a Work Area from the dropdown list
Click Next button

Once connected, navigate to the design files you would like to use. Follow the usual connection wizard steps.

NOTE: Composite model and all referenced files can be in separate folders.

iTwin File Service

You can map design files stored in iTwin File Service with an iModel and synchronize changes. For that, you need to choose iTwin File Service as a data source.

NOTE: You need to have at least Read Share permission defined in Role Based Access Control.

Mapping

Once connected, navigate to the design files you would like to use. Follow the usual connection wizard steps.

NOTE: Discipline composite model and all reference files must be in the same folder.

NOTE: Open Building Designer connector is not available for iTwin File Service because of the workspace support limitation. Use ProjectWise workflow instead which has support for workspace.

iTwin Synchronizer Client

Sneha Inamdar — Mon, 23 Mar 2020 14:31:51 GMT

Learn about iTwin Synchronizer.

Synchronize work-in-progress with your digital twin

iTwin Synchronizer Client enables you to synchronize design changes from your desktop design tool with an iTwin in the cloud. Both Bentley, as well as non-Bentley products, can successfully utilize this service.

For a full list of supported applications and formats [[Supported File Formats|click here]].

How it works

Your iTwin administrator registers an iTwin, invites team members, and assigns roles. Team members download iTwin Synchronizer Client and connectors to their desktop computer. Itwin models and the timeline of changes are then available for viewing.

To share files associated with an iTwin such as references, POD files, 3mx, rasters, etc. with someone, you only need to push your changes in the design file to an iModel and then share a link to the iModel in the iModelHub with your team members. You can do this using the iTwin Synchronizer Client. The team members you share this link with will be able to view, examine, and analyze the data stored in the iModel from any location.

Non-Bentley products can also benefit from this service, provided, they have the necessary iModel connectors installed on their systems to sync data from drawing files to the iModelHub.

iTwin Synchroniser will allow a user to define a master file, and based on the defined file type, will select a required iModel connector type to process defined files. If the required connector will not be installed, or an older connector version will be installed, iTwin Synchronizer will automatically identify and suggest to download and install the newest version.

Updating the connector version will not change a MicroStation or any other editing application version as iTwin Synchronizer contains its local set of connectors. With the iTwin Synchronizer, you don't even need to have installed MicroStation, Revit, or any other editing application on your machine to run a conversion job.

Advantages of synchronizing design data

Installing the iTwin Synchronizer Client application is quick and will not cause any disruptions to your installed products or existing data.
You can take advantage of this tool while working with both Bentley as well as non-Bentley design tools.
You can open and reference design data from different applications and different file formats.
You can continuously maintain a live digital twin of your asset(s) throughout its lifecycle.
You can view design data and properties in a web browser, without the need to install any desktop application.
You can view the chronology of design changes and compare any versions to see the differences.
You can take advantage of several upcoming iTwin Services that operate on design data and provide useful insights, including cost considerations, about the progress of the iTwin.
You can conduct continuous design reviews to identify and rectify issues while the iTwin is in progress.

Topics of interest

For information about limitations and FAQ, go to Frequently Asked Questions.
For information about the latest release, go to What's New.
Have an idea for a new feature you would like to see added to iTwin Synchronizer client or any other iTwin Service, go to Submit Idea.

Modifying Default Mapping for IFC Exports

Aidas Vaiksnoras — Fri, 27 Aug 2021 20:13:13 GMT

How to modify the Default Mapping for IFC Exports

Class mapping

1. By default, the IFC Exporter uses a default mapping file. The default mapping file can be found here: Schema mapping.

2. This mapping file is a plain text file and can be edited by any text editor such as notepad.

3. Each mapping entry consists of the “Schema Name”, “EC Class Name” & “corresponding IFC Class Name” e.g.

{ "Class": [ "ArchPhys", "Door", "IfcDoor" ] }, OR

{ "Class": [ "ArchPhys", "Window", "IfcWindow" ] }, OR

{ "Class": [ "OpenPlant_3D", "BALL_CONTROL_VALVE", "IfcValve" ] },

The schema and EC Class names are from the iModel.

4. If the IFC Exporter can find an appropriate mapping for the iModel components, then elements will be exported to the correct IFC class as per the mapping. This is how it will look in the generated IFC file when you open it in BIMVision which is a free IFC viewer.

5. But if the IFC Exporter doesn’t find the corresponding mapping, then elements will be exported to a “Building Element Proxy” element in the generated IFC file as can be seen in the below image:

6. In the above image you can see that the Exhaust element is being exported as a “Building Element Proxy”. The source schema for this element in the iModel is “RevitDynamic” and the ECClass name is “M_Centrifugal_Fan___Rooftop___Upblast”. If the user wants to map this ECClass to a proper IFC class instead of just “Building Element Proxy”, it can be mapped (as an example) to “IfcElectricAppliance”. It will look like the following in the SchemaMapping.json file.

7. When you use the modified mapping, you will see results like this:

Property Mapping

1. Similar to class mapping, we can also add Property mapping in the “SchemaMapping.json” file.

2. Please see the image below. There are different Property Sets and under each Property Set there are multiple properties. e.g. Under the “[RevitDynamic].[M_DoorOverheadingRolling]” property set we have a property called “User Label”.

3. Let’s say we need that property to be under a different Property Set, then we can add the following mapping to the “SchemaMapping.json” file.

4. The resulting IFC will show you results like this in BIMVision with the modified mapping file.

5. It is possible to export properties that have Null values by editing this part of the Global Variables section of the mapping file:

/* Process empty properties (without assigned values). Default value is false. */

"ProcessEmptyProperties" : "true"

Using a custom mapping file

1. In order to use your modified SchemaMapping.json, you will need to provide it to the IFC Exporter. How you provide this will vary from where you are exporting the IFC. If you are using itwin.bentley.com you first need to store the modified mapping file somewhere on share for this iTwin. When the Export to IFC interface appears, enable “Select user-defined mapping JSON file” and then browse to your mapping file on share.

If you are using iTwin Design Review, you will need to enable the “Select user-defined mapping JSON file” and then drag it onto the window:

iTwin Portal IFC Exports

Aidas Vaiksnoras — Wed, 15 Sep 2021 19:08:00 GMT

Navigate to https://iTwin.bentley.com

Select your iTwin if you don’t see the iModel you want to export to IFC.

Once you have your iModel, you have two choices for where you can initiate IFC Exports.

Exports from iModel List

Once you see the iModel you want to export, click on the three dots. Select the Export to IFC menu item.

This brings up the Export to IFC dialogue.

Export based on Saved View:

Toggle the "Filter based on Saved View" to create the IFC export based not on the entire iModel, but based on one of the saved views defined in Design Review. This can result in a much smaller IFC file which can be particularly useful on very large models.

Exports from Saved View in Design Review

Alternatively, Exports can be triggered from any saved view. First bring up the Saved Views dialogue and click on the ... of an individual view. This brings up the following view:

Select Export.

In this case, there is no selection of views as the export will be based on the saved view that was selected to bring up the export menu.

Common Options

Optional Log file:

You can also optionally pick to have the log files copied to the same location as the generated IFC file by toggling "Save Logs"

IFC Format:

Select the IFC format. Currently supported formats are IFC 4.3 RC1, IFC 2X3, IFC4 RV 1.2 and IFC 2X3 CV 2.0.

User defined Mapping

Optionally, you can select a custom mapping file to be used for the IFC Export. A base mapping file can be found here:

Schema mapping

Once you click on Export, a message will appear near the top of the window:

You will receive an email once the IFC file has been generated. Go to the Project Share and download the file.

Reality Data

Aidas Vaiksnoras — Mon, 23 Mar 2020 19:59:21 GMT

What permissions are needed to publish reality data? - ProjectWise ContextShare "Create" permission must be enabled for a user to be able to publish the reality data and the "Use" permission must be enabled for a user to able to display the reality data in an iTwin application.

When reality data is published? - When a *.dgn file created in the Design application (Microstation, OpenBuilding Designer, or other) has local Point Cloud or Reality Mesh attachments, those reality data get Published by an iModel Connector.
Where is reality data published? - Reality data are converted to web-ready Tiles and uploaded to the ProjectWise ContextShare Service.
How often is it published? Reality data are static in nature and only published once. If new reality data are attached to a iTwin's *.dgn file, this reality data only will get published.
Are there other ways to publish reality data? - Reality data can also be published to ProjectWise ContextShare using ContextCapture and Orbit 3DM.
How does a reality data show up in the iModel? It is streamed into the iModel at the time we render it? - Visibility of reality data in iTwin applications is controlled by the Reality Data Widget. When visibility of a Reality data is ON, it gets streamed into the iTwin applivation. The Reality Data Widget will list all reality data that have been published to the iModel by a Connector (Attached) as well as all other reality data that are associated to the same iTwin as the iModel and overlap the iModel's geographic location.

What environments are supported for reality data publishing? Reality data can be attached to DGN and published from these environments - Desktop, Cloud storage, ProjectWise

Supported Reality data formats:

ContextCapture Data (*.3Sm, *,3mx)
PointCloud (*.pod)
Raster attachments
DTM, STM

Below are listed all Methods to create iModels with Reality data.

1. Working with the Geolocated Reality data:

2. Working with the Non-Geolocated Reality data.

Synchronize local changes

Aidas Vaiksnoras — Thu, 10 Sep 2020 16:32:51 GMT

This page is under construction.

Start iTwin Synchronizer.
Select the desired iTwin from the iTwin Name drop-down menu. You will see the iTwins that you are added to by the team coordinator. You can pick the one you wish to synchronize your changes to.

You will see the synchronization listed, along with name of the associated iModels and files.
Click on the Synchronize icon corresponding to the Synchronization.

The Synchronize your changes page opens.
Browse to the location of your file in File Search Paths.
Add any comments you have for the change in Change comment.
(Optional) Optionally you can create a Named Version for the change. Select the Create a Named Version check box. Add a name and description for the change.
Click Synchronize. Synchronization starts. Once Synchronization is complete, select the Go to iModel button to navigate to the corresponding iModel in the CONNECT portal.

Prerequisite for local sync

Aidas Vaiksnoras — Thu, 10 Sep 2020 16:28:24 GMT

To be able to synchronize data to the iModelHub you will need to install the iTwin Synchronizer Client application on your machine. You must be added to a ProjectWise Project, by the Project Administrator or Team Coordinator who has access to "Product Settings Service > Manage Settings" in the CONNECT portal. There should be iModel(s) created in the iModelHub and Synchronizations created by the team coordinator, for your itwin to which you can push your changes.

To be a Team Coordinator you must have the "Product Settings Service > Manage Settings" enabled in the CONNECT portal for your profile. Your organization's IMS (Identity Management Service) administrator can grant you this permission. You must also have access to iModelHub.

The following RBAC permissions are required for a user to synchronize Design and Reality Modeling data:

To Create a connection:
- Product Settings > Manage Settings

To Publish a DGN to iModelHub:
- iModelHub > Modify iModel

To Publish reality data to ProjectWise ContextShare:
- ProjectWise ContextShare > Create

To Create an iModel on the iModelHub:
- iModelHub > Create iModel

You can read more on RBAC roles here

Once the above prerequisites are set you can start synchronizing your changes as needed.

Define local synchronization

Aidas Vaiksnoras — Thu, 10 Sep 2020 16:27:39 GMT

This page is under construction.

Start iTwin Synchronizer.
Select the desired iTwin from the iTwin Name drop-down at the top of the dialog.
Select the New button. The New synchronization page opens.
Specify a name for the synchronization.
Select an iModel to which the synchronization will be mapped.
Browse to the location containing files to be synchronized. You can select multiple folders in a directory.
Add files to the Synchronization from the selected directory using the Add button. The list of files selected is displayed under Files section.
Select a file that defines the Geographic Coordinate System using the corresponding radio button. You can remove a file using the Unmap icon.
Click Next. iTwin Synchronizer will check for required connectors and enable them.
Click Save to save the new synchronization. The newly created Synchronization is listed along with information about the iModel and the files associated with it.

A new Synchronization is created and will be added to the list of synchronizations (if any are created already) in the iTwin. You can now synchronize changes to it, edit it to make any changes or delete it using the Synchronize, Edit and Delete buttons respectively, on the right.

Creating a connection

Joey — Thu, 28 May 2020 12:07:13 GMT

You can get to the iTwin Synchronizer portal from iModel Manager. In iModel context menu choose Connections action.

Setting up a connection

Follow these steps to create a connection:

Find required iModel in iModel Manager page
Choose Connections in a context menu
Click Create connection button, if there are no connections for selected iModel
Or
Click + New button, if there are already other connections created
NOTE: you will be presented with a step-based wizard.
Choose a data source where you store your design files.
You can find the list of available data sources and how to integrate with them on the Integrations page.

Setting up a data mapping

To correctly synchronize changes from the data source, you need to perform data mapping. Follow these steps to map your design files with an iModel:

Select composite models - the data you want to be synchronized with an iModel.
NOTE: You should select only the discipline composite files when creating a connection. All of the reference files will be automatically added to the synchronization. For a data source specific limitations check the Integrations page.
Define the geocoordinate system. Pick a file from a previous step from which we will extract a geographic coordinate system to be used in an iModel.
If you totally skip it, we will use the first found file which geolocation data for an iModel during synchronization, or if none exists iModel will not have any geocoordinate system defined.
NOTE: This step requires to pick a file only for the first iModel connection. For the sequential connections, the same file will be used, so this step will be skipped.
Based on your mapped files define which iModel connector needs to be used. In this step, you can also check which files and their references will be mapped to an iModel.
Check supported iModel connectors here: https://communities.bentley.com/products/digital-twin-cloud-services/itwin-services/w/synchronization-wiki/47595/supported-applications-and-file-formats
NOTE: You can use only one iModel connector type in a connection for all the mapped files. If your files need to be processed by different connector type, please split them into separate connections and associate appropriately. For instance, .rvt and .dwg files should not be mapped together using the Revit connector type as it might lead to missing graphics or properties. Instead, you should create one connection for .rvt (Revit connector) and one for .dwg (AutoCAD connector).

NOTE: Depending on the connection and number of references the files may take some time to populate and is not necessary for it to load to move on to the final step. Once the Connector type is selected "Next" can be used to move on to "Configure Connection".

Scheduling a synchronization

You can schedule automatic synchronization runs during connection setup. There are different options to choose from:

Every 4 hours. This is the shortest available schedule.
Daily. You can set any particular time during the day
Weekly. You can set the day and time.

If you do not want the scheduled synchronization runs, choose Never.

You can always synchronize the connection manually, even if you have created a schedule.

Knowledge base

Laisvune Valackaite — Mon, 10 May 2021 14:31:58 GMT

Here you will be able to find answers to why synchronization failed and how to fix it.

Access to Data Source Denied

You do not have the appropriate permissions to access the data source. Please contact your data source administrator, who can provide you with the required access to resolve this issue.

Another User is Pushing

This indicates that another user is trying to update an iModel with new information from the same file. This is most likely to be because both the cloud-based synchronization and the iTwin Synchronizer Client are being used on the same iModel at the same time. This is not good practice and will most likely lead to errors.

Another possibility is that the cloud-based synchronization is trying to run two different connections at the same time which are competing for the same iModel. This is most likely when there are long running connections taking longer to complete than the time between scheduled synchronizations, and is not an intended method of operation. Please contact support if this is happening regularly.

Connector Lock Errors

At this time, please contact Bentley support to further diagnose this kind of error: https://apps.bentley.com/srmanager/digitaltwins

Datasource Authentication Type Is Not Supported

Authentication type is not supported. IMS or federated login is required for the user to access the PW datasource. Please enable IMS authentication on the ProjectWise datasource.

Document Not Found

A mapped document was not found in the data source. Please make sure the file is not deleted and is in an accessible state to resolve this issue. If a file was deleted, it should be unmapped from the connection.

Drawing File with Wrong Configuration

A 2D file may be used for the root model with other sheets and drawings in a connection, but it does not provide spatial information for a 3D model. If sheets and drawings are disabled for the connection, there is nothing remaining that can be successfully synchronized with the iModel. A file containing a spatial model should be used as the root model to provide the required 3D location and coordinates for the iModel.

Duplicate Models

Please ensure

1. Only one version of the file is mapped into the iModel.

2. Multiple connector types are not used to synchronize the same file.

For other cases, please contact Bentley support to further diagnose this kind of error: https://apps.bentley.com/srmanager/digitaltwins

Failed to Access Data Source

You are not authorized to use the document data source, or too many requests have been made in a short period. Please check if the data source server is accessible.

Failed to orchestrate file processing retry

Synchronization Report shows " "Lock failure since User: User_Name : User_Name@Domain.com owns a lock in briefcase id: 43": "

Resolution: This usually indicates that the same file is being used by more than one connection in the same iModel and that one of the connections failed to complete correctly. Find the other connection and make sure that has run correctly (which should release any locks that it was using), and then repeat the connection that is showing this message. If this still fails for the same reason, contact Bentley support.

Failed to process the file

Synchronization Report shows "Error occurred while downloading the file URLs to the input file location" but has "Unknown" as the filename.

Resolution: Visit https://softwaredownloads.bentley.com/en/ProductDetails/2693 to obtain the latest released versions of the ProjectWise Design Integration Plug-in for WSG CONNECT Edition and dependencies.

Synchronization Report shows "0 file(s) processed" but the Details do not contain useful information.

Resolution: Please inform Bentley Support if this occurs. They will need the details of the connection (from the "Report an issue" menu item available via the 3 dots on the end of the connection run status line. They may ask for access to the data in order to determine the nature of the problem.

File is Protected

The file is protected. Ensure that you have permission to both access and export the file.

Geodetic coordinate system not supported

When creating a connection to a non geo located iModel, the user can select a geo located input file to set the iModel geographical coordinate system. If no file is selected, the first geo located input file encountered will be used to set the iModel geographical coordinate system. The coordinate system units must be meters. You cannot select a file which has a Geodetic coordinate systems (i.e. using degree units).

Note that the other subsequent files added to the connection can be in meters or degrees.

iModel Access was Forbidden

The Connection owner does not have permission to synchronize files to the iModel. Please check project and iModel level permissions.

iModel Not Found

The iModel that the connection is trying to synchronize changes to may no longer exist or is not accessible by the connection owner.

Missing Workspace

The source .dgn file for this connection could not be synchronized since the workspace for this source could not be found.
Open Buildings Designer (OBD) files are federated and not self-contained.
That is to interpret (or synchronize) an OBD.dgn file, a workspace must be present.

Desktop Scenario:
When running on the desktop, OBD and Open Buildings Connector (OBC) try to resolve the workspace from the local file system.
If OBC discovers that an obd.dgn file was authored with a workspace not available locally, the user-interface will prompt for a substitute.
The substitute-workspace is a fallback option to synchronize a file while retaining most of it's properties, materials etc.
Typically a regional Bentley supplied workspace (like BuildingTemplate_UK) is used as a substitute.

ProjectWise Scenario:
When dgn-file-persistence in the Bentley ProjectWise-document-management-system is used, design files should be properly connected to a ProjectWise managed workspace (PMW). OBC will fail and notify when a PMW cannot be resolved for a given connection. In that case a good first troubleshooting strategy is to open up the same pw URL from ProjectWise-Explorer using OBD on the desktop. Detailed PMW issues might reveal themselves in the OBD message-center or the configuration variables dialog. If resolving the PMW problem fails, Bentley OBD support can be contacted for help. Alternatively (for instance when an obd.dgn file was obtained from a subcontractor without a workspace) a substitute workspace may be specified. This may also help processing ABD-v8i files that pre-date workspaces. V8i files can best be synchronized by first converting them to .i.dgn files.
A substitute can be specified by supplying a plain text asci file in the spatial-root folder (or any of its parent folders) with the name “__iModelHubPublishSettings__.txt”.
The first line should read “WorkSetOverride=BuildingTemplate_UK” in case UK region is desired. Other regions available are US, AU, NM. More can be requested.

Material could not be located or could not be loaded

The file has configured materials, that can not be located. Please check if the path to Materials is located in ProjectWise and is accessible.

In Bentley Civil product files, this can be checked by opening a dataset with materials and textures from ProjectWise. In opened file first, check if there are any errors in the Message center.

If you see an error coming for missing materials then open "Search Ribbon" and type "ConfigurationVariable"

Now visit the same path in the ProjectWise location and check whether you have a materials folder available. NOTE: Materials located in the local machine path are not supported by the cloud Synchronization solution.

If you don’t see the materials folder in a specific path (under workspace configuration) > Open the locally available workspace folder deliverable with Civil product which is under
C:\ProgramData\Bentley\OpenRoads Designer CE\Configuration\Organization-Civil and copy materials folder under the required ProjectWise path.

Non-linear units specified

The Unit Type is an unsupported type. Only 'Distance' is supported. Please change the type in the Advanced Unit Settings for the design file.

Product Installation Path Not Found

Could not get a path to product installation. Please check the product is installed correctly on the PW server. For PW WSG, if the WSG plugin is installed on a different machine than the PW Server machine, please install the product on the WSG plugin machine.

Product Setting Permission Missing

The Connection owner does not have Product Setting Service "Manage Settings" permission. Please check project-level permissions.

Manage Project Team Members -> Project Role Management -> Service Access and Permissions -> Product Settings Service -> Manage Settings

Project Share Permission Missing

The Connection owner does not have enough Project Share permissions. Please check project-level permissions.

Manage Project Team Members -> Project Role Management -> Service Access and Permissions -> Share -> Read

Root Model Is Not a Spatial Model

When attaching a sheet model to a 3d model, the root model must also be a spatial model. Please fix your model hierarchy to ensure the root model is also a spatial model.

Schema Upgrade Failure

When a Connector opens an existing iModel, it must first ensure that the schemas stored in the iModel match the current version in the connector. If not, the connector will attempt to upgrade the schemas stored in the iModel. If this process fails for any reason, the connection attempt will terminate. Please contact Bentley Support for further assistance. https://apps.bentley.com/srmanager/digitaltwins

Unmap Input File

The connector is unable to unmap the given file. There are several reasons that this could happen.

The given FileId does not exist in this iModel. Double-check that you have the correct value.
The given file is not the master model. Please try unmapping with this file's master model.
The iModel has been damaged. Please talk to your administrator on how to fix it.
This file was mapped using a different connector. Please try again with the correct connector.

Unrecognized Format

The connector assigned to this file does not recognize the file format.

Resolution:

Please change the connection definition to use the correct connector for this file.
If it's already done, please open the file in the original application and try to re-save and upload this file again - perhaps the file was corrupted during the initial transfer.
If possible, please try to upgrade the file format to a recent one in a newer application version.
Please look at Synchronization Report - it could display additional details and suggestions.

User Not Authenticated

The connection owner's access token has expired. To resolve this issue, please re-authorize scheduled synchronizations by running a connection manually or by clicking here.

Source file pre-authenticated URL is expired

The source file URL provided expired before downloading it. Please re-generate the source file URL with a minimum of an hour expiry time for synchronization.

Source file is not accessible.

The source file URL provided is forbidden. Check if read permissions are assigned for the source file.

Source file not found at location

The source file was not found at the given URL location. Please check that the URL is well formed, and the given location is correct.

Source file is likely corrupted

The source file exists and is mapped to a connector, but the connector has failed to open this file. The file is likely corrupted. Please try opening it in the product that has created this file. The product may have utilities that can audit and fix the errors.