[CONNECT] What are the advantages of project-based worksets?

RE: [CONNECT] What are the advantages of project-based worksets?

Rod Wing — Fri, 01 Oct 2021 17:05:11 GMT

[quote userid="2436" url="~/products/administration/f/product-administration-forum/220105/connect-what-are-the-advantages-of-project-based-worksets"]Our other option is to have Client Workspaces, and then a single dummy client workset that does essentially nothing. That would miss out if there are some spectacular reasons to have separate worksets, but it would definitely preserve the status quo[/quote]

I would do that at a minimum as your DOT clients will be set up as different WorkSpaces.

I can see where there is reluctance to set up one WorkSet per project. The move to ORD is going to difficult enough without throwing in this extra requirement.

Again, your DOT clients are most likely set up to operate on the one WorkSet per project configuration. As Marc Thomas pointed out, the Sheet Index and ProjectWise are two reasons to go that route, here are some others:

Custom WorkSet properties as text fields - It is becoming a common practice to set up custom/advanced properties for the WorkSet and reference them as text fields in your sheet borders (and elsewhere). You can still use tags, text substitution, or what ever methods you had in V8i, but more and more DOT provided sheet templates have the custom property text fields baked in.
Project specific ORD template .itl files - Many organizations set up one, or more, template(s) per project. By setting up a seed .itl per WorkSet you don't have manually change .itl files when changing projects.

RE: [CONNECT] What are the advantages of project-based worksets?

MaryB — Thu, 30 Sep 2021 12:37:51 GMT

That's what I was thinking. I don't want to lock myself out of anything useful, but I'd prefer to keep things simpler considering all of the other changes going on with the upgrade.

Thank you.

RE: [CONNECT] What are the advantages of project-based worksets?

Marc Thomas — Wed, 29 Sep 2021 16:03:49 GMT

Hi Mary,

From your description above it sounds like having one WorkSet per client would be a good way to go for the time being. The file branding would only arise if someone opened a file from a different WorkSpace, which seems less likely to occur.

WorkSets per project become necessary if one engages with features like:

Sheet Indexing, where the sheet information for each project is stored in each WorkSet's DGNWS
ProjectWise 365 which is designed to use separate cloud hosted projects linked to and synchronised with locally cached WorkSets (think OneDrive for Bentley to get the general idea)