Imodel plugin for Revit 2021

Are there any updates to this thread from Bentley representatives? We need this plugin (or something similar) to work with Revit 2021, 2022 and new versions too. 

Hello Will,

I think it's quite clear that Bentley will not develop a new version of the plugin for Revit 2021 or any newer versions.

As explained above there is a method to convert RVT models (from any Revit version) to iModel through the iModel Hub. From there you can reference that model into OBD or export an IFC from the iModel hub, then reference or import that IFC into OBD.

The big benefit - in my opinion - is that this method not only works for Revit models but can also be used for a variety of other file formats. Including NWD (Navisworks), ...

If you have to do regular updates of the Revit model, this can be automated. As long as the new version of the RVT file is uploaded either in PW365 of in the iTwin Share folder, the generation of the iModel can be done automatically for example every week.

Hi Joey,

Thanks for the info. I dont have access to Mstn 2023 (waiting for OBD 2023 to pop).

Some questions:

1. .bim file: Is this a Bentley format or is it based on https://dotbim.net/ ?

2. I note that some users are using the iTwin Snapshot tool to generate .bim files. Will this be rolled into iTwin Synchronizer? It would be great to minimise duplication, UIs.

3. I note that there is an iModel import tool in the OBD 10.1 Backstage. This seems to be incomplete, a place holder. I get an 'unknown command' message when I click on it. Has this function been included in Mstn 2023?

4. Similarly, will there be an .bim import tool?

5. iTwin Synchronizer is a real pain to use. I think one of the problems is that the processing is done remotely on the cloud somewhere. No control or idea how long it will take to process, place in queue. Will there be an option to do the conversions locally in Mstn 2023? I think there was some mention of this as part of the 'Phase 2' work.

Hi Dominic,

Note that you can reference in iTwin Snapshot BIM files into older versions of Microstation (back to U16 I believe) - you just don't see it in the Reference dialog (but can detach in Level dialogs).

Yup. I can 'attach' the .bim file in OBD 10.1. Thanks for the tip.

The .bim attachments do show up in the Hierarchy but not in the main panel.

Tried attaching an example .bim file, which gives me an 'is not in a recognized file format' message so it looks like .bim is a Bentley format, here.

I noticed that the .bim elements can not be copied into the active model, like i.dgn or IFC attachments.. which is a bummer. Hopefully this will added later.

Makes you wonder what the road map for .bim files is and how they are going to used. I can see them being locally stored versions of Ref attachments that would normally be remotely stored, and/or produced by other apps. So instead of Ref attaching / downloading the whole iTwin, Mstn would just load the locally saved .bim files that would be kept synchronised by the iTwin Synchroniser tool in the background? Sort of the way .ism, PW or Revit Server work.

If that is the case, then current functionality like Copy Element from Refs needs to be supported, as well as Merge into Master, Activate, Exchange and Open in New Session.

PS:  RE: What is the road map after Microstation 2023? 

"The iTwin engine will run on the same desktop ‘in process’ with the design applications, synchronizing a local iModel and connecting to cloud services when and as necessary.” 

So, it sounds like there will be an imodel alongside the regular dgns. How would the changes get propagated?

1. Dgn and imodel gets updated simultaneously, and the local imodel synchs to the cloud imodel? Cloud imodel then synchs any .bim files?

2. Cloud imodel gets updated, and synchs to both local dgns and imodels and any associated .bim files simultaneously?

3. ?

Maybe the .bim filles should be the new local iModels? It would be good to keep the number of 'players' down.

Or will the local iModel be embeded into the dgn? Users will be used to moving, copying and renaming dgns using MS Explorer.  Otherwise, we will probably need PW to manage. No working in unmanaged folders?

Or will the local iModel be embeded into the dgn? Users will be used to moving, copying and renaming dgns using MS Explorer.  Otherwise, we will probably need PW to manage. No working in unmanaged folders?