Coordination Issues
Select a clash - or a native Clash Detective group - right inside Navisworks and create a linked, duplicate-protected issue on the web. The link survives a re-import too, so a renumbered clash doesn't lose its history.
A clash goes stale the moment it leaves Navisworks as a screenshot in someone's inbox. JAED Collision Suite pushes the live session straight to a shared dashboard instead - every trade partner sees the same real-time status, with no per-seat license to bring them into it and nobody but you needing Navisworks installed.
Navisworks already finds the clashes. The expensive part is everything downstream - a report gets exported, emailed, and opened by everyone once; a week later nobody's sure which screenshot is current, who owns what, or whether it got fixed at all.
A clash caught during coordination costs a few hundred dollars to fix. The same clash found on-site can run into the thousands - so the report it's logged in is worth keeping current, not filing away.
An issue that's logged but never assigned is the same as an issue that was never logged. Every clash pushed here gets a status, an owner, and a history - not a screenshot that goes stale.
Every trade partner on a project - GC, sub, owner's rep - needs a seat at the coordination table, not a line item on a per-seat invoice. Licensing shouldn't decide who finds out about a clash and who doesn't.
Real screens from the actual app - not mockups.
The rest of what's actually built - not a roadmap.
Select a clash - or a native Clash Detective group - right inside Navisworks and create a linked, duplicate-protected issue on the web. The link survives a re-import too, so a renumbered clash doesn't lose its history.
Generate a coordination-meeting agenda straight from open issues, capture decisions and action items, then print the minutes.
Import a construction schedule and track it on a Gantt-style view - Week/Month zoom, an Auto/Behind/At Risk status per activity, and a PDF export.
Keep trade submittals, drawings, and uploaded NWC models in one place per project, visible to everyone who's actually assigned to it.
Viewport captures pushed live from the Navisworks plugin - section cuts and redline markups included, not just a plain screenshot.
A weekly coordination report and a full CSV export, generated straight from live clash data - nothing to compile by hand for the next status meeting.
Users, roles, invites, and an audit log. Organizations sit above Projects, so a firm only ever sees what it's actually been assigned to.
Upload, translate, and view a real NWD via Autodesk's own Platform Services pipeline and official WebGL Viewer.
The desktop side isn't a separate export/import step - it's a dock pane inside Navisworks itself, connected live to whatever project you're working on. One account works in both places, so nobody's juggling a second login. Connect once, then use any of the three below as often as you need to.
Sign in once from the dock pane, link the open document to a project, and stay connected across sessions - no re-authenticating every time you reopen the model.
Send the live clash set from Clash Detective straight to the linked project's Clash Coordination tab - the whole team sees it without waiting on an exported report.
Select a clash - or a native Clash Detective group - right in the 3D view and create a linked web issue on the spot, then jump straight back to it from the desktop.
Capture exactly what's on screen - section cuts and redline markups included - and push it straight to the project's Snapshots tab.
No - the web dashboard runs entirely in a browser. Navisworks is only needed on whichever machine is actually running the live clash session and pushing it to the web.
Yes - click "Explore as Guest" for full read-only access to a sample project, no signup required.
Two ways: push it live from the plugin's dock pane - "Push to Website" sends whatever Clash Detective is showing straight to the project's Clash Coordination tab - or export a Clash Detective report from Navisworks and upload the HTML/zip file directly on the web app, no plugin required for that path.
No - re-importing the same test replaces its clashes, not duplicates them, and everything your team already did to a clash - status, assignment, priority, due date, comments, history - carries forward automatically, matched by that clash's own label. It's only lost if the label itself changes between imports.
Yes - export the full clash list to CSV, generate a weekly HTML coordination report, or print a meeting's minutes, all without giving that person a login.
Admin, BIM Coordinator, Project Manager, General Contractor, Consultant, and a read-only Guest session - an Admin assigns each real account to the Organizations and Projects it should see.
Nothing metered - an Admin creates an account and assigns it to the right Organization/Project. There's no per-seat subscription tier standing between "we should get this sub looking at the model" and actually doing it.
Every request is authorized server-side and passwords are PBKDF2-hashed with a per-user salt, all running on infrastructure you control - a self-hosted deployment with local storage. Nothing goes to a third party except optional Autodesk Platform Services calls for the 3D Viewer tab, if that's configured.