Home
During the Great Lockdown of the last two years, in what has so quickly become a remote-working, online-first-meetings, broadcast only way of doing business. One really striking aspect of the AECO world, away from the Teams, Google Docs, Zoom and the like, was that the manner of Model Analysis and review has not been in the same class of technological delivery.
I've sat through many dozens of streamed Navisworks sessions and engagement amongst teams has definitely waned or defaulted to a broadcast rather than a collaboration. Attention spent managing the remote experience means the analyst is taxed to the point of only making scant notes about issues, and contributors may not all be heard to register their input.
For this professional/social need I introduce Rimshot - Realtime Issue Management with Speckle.
Utilising two aspects that I admire of Speckle:
- Information Hub and low-friction data transfer.
- Bring people to the Model. Speckle is multiplayer.
The XYZ project stream used in the demo
-
Install the addin as a application plugin bundle
-
Launch Navisworks and select plugin
-
Select a project and workshop (already created in the rimshot database)
-
Select an issue to commit to.
-
Elements selected in Navisworks will be committed as Speckle Mesh to the corresponding branch (created new if not existing)
-
Selecting Snapshot adds an image to the existing issue of whatever is visible in the viewport. If no issue is selected, snapshotting ceates a new issue and corresponding branch.
-
The analyst can share a unique secure URL to the workshop record. (https://rimshot.app/issues/{UNIQUE ID})
-
All visitors to that web page can see images and Speckle commits being added.
-
"Follow-mode" scrolls to the issue currently being presented by the Analyst. Selecting a different issue cancels Follow Mode
-
All contributors can comment and edit the descriptive and the metadata fields.
-
The commited model can be viewed in the Rimshot app or the corresponding Speckle Server branch.
-
The workshop record can be downloaded as in CSV file format.
The hackathon submission consists of:
* Model elements selected in Navis will be committed and synced to the app.
* Model elements are converted on the fly while the discussion continues.
* The addin allows for immediate viewport screen capture.
* Structuring the database around a collaborative experience aids quality of Issue resolution.
- Using a real-time database allows for all authenticate users to comment and properly describe and issue and its path to resolution.* The responsive app design scales to full screen to handheld.
- Contributions can be immediate and collaborative.
- Backend webhook and cloud function support to reinforce the Navis<>App interaction and capture events that may fail due to connecttivity issues or lag. Both events may happen without conflict and eventual consistency is assured.
* Each issue is a separate Speckle branch.
* Multiple sub-issues can be made as separate commits to the branch.
* New issue branches are created automatically
- Proper linking with Auth flow and project/stream selection.
- Syncing of Comments between the two databases - near realtime.
- More responsive syncing. Allow Speckle to push to the app (perhaps closing out issues, 3rd party commits)
- Sorting out the 🔥HOT MESS🔥 of the Navisworks geometry translation.
- Integate the Speckle Viewer rather than embed views.
- Responsive Event driven model analysis to push metadata into the issue record.