I am excited to announce the first beta release of the Speckle Connector for Navisworks! Based on feedback from our v2-alpha connector, we’ve focused on what we’ve learned matters most to our users: robust geometry extraction and data analysis capabilities.
Current Features
High-Fidelity Geometry: Precise geometry extraction from leaf nodes (selectable objects in Navisworks)
Comprehensive Data Transfer:
Model properties
Element properties
Custom properties
Visual Data: Preserves materials, colours, and transparency settings
Flexible Selection: Select specific elements for targeted data extraction
Note: While model hierarchy support is not included in this initial beta, we’re open to reintroducing it based on user feedback and needs in future releases.
Use Cases
This initial release is particularly suited for:
Data extraction and analysis workflows
Property and metadata collection
Geometry extraction for downstream processing
Integration with data analytics platforms
Getting Started
The connector supports Navisworks Simulate and Manage versions 2020-2025:
Install the latest Speckle Desktop
Install the Navisworks connector through Speckle Manager
Launch Navisworks and find the Speckle ribbon tab
We Need Your Feedback!
This is a beta release. Download it here and let us know your thoughts!
Test the connector with your data analysis workflows
I have tried the next gen navisworks connector and it works well! The synch function is great !
The full model hierachy would be really helpful for me, so this information can be used in PBI for filtering and reporting.
That does exist - it’s how we structure data being sent out (and you can see it in the model explorer on app.speckle.systems), but i guess this does not come in as a property on the element, which is how you’d use it in powerbi… Something for @jonathon once he’s back; or it might be something we can do on the powerbi end, though unsure.
Actually @D.S_Bosma is reporting correctly the first release of next gen Navisworks focussed on data and properties of the selectable objects and not the full tree processing. Indeed as most users use cases ignored that structure, hierarchy was moved as an option to improve performance for the majority.
The next release will enable this option.
I’m interested to know @D.S_Bosma if the hierarchy as a property is enough I.e full path for an object or if you truly need the hierarchy fully respected as a data structure. I’d like to err on the side of usefulness + performance than purity that needs to be undone/ pivoted in use. Please let me know where/how you are using this Navisworks speckle data.
Happy to hear data tree properties will be available in the next release of the connector ! For most projects the hierarchy as a property will be enough, so e.g., the aspectmodel name (.nwc or .ifc) can be used for filtering in PBI. But for 2 specific projects, we need to deliver information which is nested in the hierarchy. So e.g. for the projectlevel in the hierarchy, the IfcName and Projectnumber are needed / for the location level in the hierarchy, the Longitude, Latitude and Elevation / etc. Within the PBI information delivery report all these (missing) codes can be checked by the modellers, before a delivery to the client is made.
Below some additional comments for the v3 connector:
After selecting the project and model clicking on publish, the screen does not change. The button Publish remains visible some time (seconds) before the publications starts. First, I thought nothing happened, and clicked again on publish
When be message below appears, it cannot directly be closed. First you need to go back, close it, and go forward.
When opening the geometry published with Navisworks connector v3, and visulize the objects in v2 PBI, the object appear default in grey. In the v3 pbi connector this may not be the case, but so you know.
Announcing Speckle for Navisworks Beta Release
High-Fidelity Geometry: Precise geometry extraction from leaf nodes (selectable objects in Navisworks)
Comprehensive Data Transfer:
Visual Data: Preserves materials, colours, and transparency settings
Flexible Selection: Select specific elements for targeted data extraction
!
! For most projects the hierarchy as a property will be enough, so e.g., the aspectmodel name (.nwc or .ifc) can be used for filtering in PBI. But for 2 specific projects, we need to deliver information which is nested in the hierarchy. So e.g. for the projectlevel in the hierarchy, the IfcName and Projectnumber are needed / for the location level in the hierarchy, the Longitude, Latitude and Elevation / etc. Within the PBI information delivery report all these (missing) codes can be checked by the modellers, before a delivery to the client is made.
