Solibri and Navisworks coordination, connected to Revit

Coordination normally loses its memory at every handover. A clash test is re-run and last week’s grouping is gone. An issue is republished and the assignee, the due date and a coordinator’s comment are overwritten. The Bridge exists to stop that.

Where it runs

The Bridge is a NexarDocs workspace inside the applications where coordination actually happens: a dockable panel in Autodesk Navisworks Manage 2024 to 2027, and a view alongside Solibri’s own views in Solibri Office. Both are installed by the standard NexarDocs installer when the matching application is already present.

Navisworks and Solibri each need their own licence from their own vendor, exactly as they do without NexarDocs. The Bridge does not supply or replace them.

Issues that keep their identity

Issues published by the Bridge keep their identity between runs, so the same clash is recognisably the same issue next week. The values and comments a coordinator sets by hand are preserved on republish rather than overwritten, which is the difference between a tool that helps and one that quietly deletes a week of triage.

  • Federation overview: what is actually loaded, and whether it matches what you meant to coordinate
  • Issue lineage: whether something has been open since March or is new
  • Decision memory: the values and comments a coordinator owns
  • Meeting mode: decisions recorded with the issue as they are taken
  • Verification: candidate fixes reviewed before a status changes, so issues close against evidence

Open in Revit

Select a checking result or a published issue and press Open in Revit. A running Revit session selects and zooms to the elements the issue refers to, resolving elements that exist only in a linked model through the link.

The handoff is local. Nothing about the issue is sent over the internet to make it work and no network port is opened; the two applications talk over a Windows named pipe that only the signed-in account can use.

IDS validation and BCF

IDS checks requirements against an IFC, and NexarDocs does not pretend to validate a live RVT directly. Solibri runs the IDS 1.0 validation, failed results are published as BCF 2.1, and NexarDocs pulls them back, mapping component IFC GlobalIds to the Revit elements they came from and keeping the IDS specification, requirement and checked IFC filename with each issue.

BIMcollab spaces are supported through a secure browser sign-in for teams whose issue tracking lives there.

Licensing

The Bridge is a separately purchased add-on that activates on the same licence code as NexarDocs. There is no second code, no second activation and no second seat. Adding it takes effect within a few minutes and does not require reinstalling anything.

Common questions

Does the NexarDocs Bridge need a separate licence key?

No. It activates on the same licence code as NexarDocs itself. There is no second code, no second activation and no second seat.

Which versions of Navisworks does the Bridge support?

Autodesk Navisworks Manage 2024, 2025, 2026 and 2027. In Solibri it runs inside Solibri Office.

Can it validate IDS against a Revit model?

IDS checks requirements against an IFC. Solibri runs the IDS 1.0 validation, and NexarDocs pulls the failed results back as BCF 2.1 and maps them to the Revit elements they came from.

Does opening an issue in Revit send data over the internet?

No. The handoff is local to the computer and opens no network port. The applications communicate over a Windows named pipe that only the signed-in account can use.

Related

  • Clash detection
  • Classification, COBie and data standards
  • Automated dimensioning

Nexar Docs | Start a 14-day trial | Contact Nexar Group