Composite iModels - Technical Preview

 

Previously in Infrastructure Cloud, all iModels are created utilizing web (or desktop) tools, and connections are created to synchronize engineering CAD files with a given iModel.  Although this hasn't changed, those (connected) iModels can now be leveraged further.

 

The best way to think about both types of iModels would be to refer to this diagram:

Composite iModels are composed of other iModels whereas Connected iModels are created from engineering CAD files.

 

One of the advantages of Composite iModels is that since they are created from existing iModels, the transformation is very fast.

 

When clicking the Create iModel button there is now an option to create a Composite iModel:

After selecting the Composite iModel option, you are asked to give your iModel a name along with an optional description and image.

At this point, clicking the Create button creates an empty iModel.  You will then be presented with the transformation details page.

 

There are currently 2 transformation types:

 

Filtered

 

 

With the Filtered transformation you can use a Saved View from an existing iModel to create a new iModel. 

 

This requires the user to select an existing iModel from their project, select an optional Named Version (if there are no Named Versions this is greyed out), and then select one Saved View to use as the Filter.

Click on the Transform button to create your Composite iModel.

 

To update the target iModel, go to iModel Manager and click on the iModel tile's Context menu (the 3 dots) and select "Run Transform"

 

 

[Note: When updating the target iModel, the Saved View settings in the source iModel must be set to "Include New Content" (this is the default setting).]

 

 

Combined

You can also Combine existing iModels into a new iModel.  In this case you only need to select the iModels you wish to combine.

 

However, note that the iModels you are combining need to share the same geospatial coordinate system.  Otherwise, the iModel graphics could become corrupted.

 

There are some rare cases where combining iModels can cause schema conflicts (the same objects in 2 different iModels with conflicting definitions).  In these cases, the secondary iModel with the conflict will be discarded and an error message will be written to the “Transform reports”.

 

There could also be duplicate elements when iModels are combined.  By default, the transforms will overwrite any previous elements with subsequent instances to avoid duplicates.  However, if these objects with the same element ids (FederationGuid) are graphically different, only the last version imported will be present.

 

When selecting the iModels, the order that you select them is important.  The first iModel you select will be used as the target iModel’s geospatial location.  Similarly for schema conflicts, the order processed will defined which iModel is “good” and which one contains the conflict.

 

 

Transformation reports

Similar to the Sync reports for connected iModels, selecting the context (3 dot) menu on a Composite iModel, and selecting Manage Content opens a similar UI.  This allows you to re-run the transform, as well as select the report from the context menu for each transformation run.

The Transformation report is laid out in similar fashion to the Synchronization reports.