A big redundancy in the tool currently is managing search sets, appearance templates, viewports, stamp templates, and clash tests separately from one another. It would be much more efficient to be able to dictate who has "edit" access to which viewports, appearance templates, search set folders, stamp template folders, and clash tests through user tags or groups which could be setup once in each tool for the project.
Setting up permissions by User Company or even a project-internal "group" or user "tags" similar to how other collaborative task management platforms work, would allow us to increase our collaboration with external teams without having to add new people to each individual clash test they're a part of, or make sure they don't touch certain search set/viewport folders.
Especially with the sell of this being a project life-cycle tool, having multiple buildings in one model with different stamp templates for review of different milestone deliverables vs. clash stamps for the BIM group creates a spiderweb of circular dependencies in our workflow. There are times where we have Design Development drawings being reviewed at the same time we have Schematic Design drawings being reviewed. We end up having to do a lot of training and spending a lot of time QC-ing that the proper stamps are used for the proper deliverable/clash to make sure we can report the data properly back to the team/owner.
If we were able to add individuals to a Design Structural group or tag and setup permissions for the individual tools based on that distinction, we would divide our workload by 5 at least due to how long it takes to properly onboard individuals into the workflows for what and what not to use.
There is a lot of upkeep that takes place making sure our viewport folders are clean and contain named/relevant viewports as to not be exhausting to pour through. Assigning each group a viewport folder from the start would solve this.
SEARCH SETS/APPEARANCE TEMPLATES:
Our design teams love the tool but lack the ability to fully control their own little worlds inside the tool. This starts and ends with search sets. They need to be able to jump in and create their own search sets and appearance templates. Having the ability to assign them an overall folder for their company (as well as other folders/appearance templates that apply to the whole team) would give them the freedom they need to run quantity take-offs, clash, and reviews the way they need to for their internal processes.
DEPENDENCY FOR ROLLOUT:
A massive indirect dependency for this is being able to break-out appearance templates into folders, as well as making sure that all other tools can have folder separation as well.
ADDITIONAL FUTURE USE:
If we were able to do the same with project models (Load/Unload Models tool) that we are able to do with the other tools for sharing/not sharing MODELS, our teams would have the ability to upload bits and peices for coordination without overriding their entire model or creating duplicate content for the rest of the team.
If the tool was built off of this type of permissioning structure, there would be ways to customize the Revizto tools to show only what those teams should be using at that point in the project. Management would become shuffling instead of the exhausting task of training and onboarding with new content as the project progresses.
Please sign in to leave a comment.