Hi, I'm new to CE and try to migrate our V8i workspaces to CE. It's clear that old site level now is organization. And from my point of view our old project level now should be "Workspace" level, because it contains client resources. It seems that Bentley agrees here.
The issue for me is: We have many small jobs (resp. sets of DGN) for each client (resp. Workspace). Each job needs the same client resources and nothing extra. Though the Workspace/client resources are needed to edit or view the DGN files, none of these DGN files belongs to the Workspace. The design files are stored anywhere on the file system, but never inside microstation's WorkSpace. And that's why the WorkSets seem to be useless in our work flow. Unfortunatly I can't see a way to open a design file with specified Workspace but without a WorkSet. When I use a configured dummy WorkSet, it often stands in the way: The opened files are marked with WorkSet name, causing confirmations about WorkSet mismatch...
Hope, someone could tell me, how to get rid of WorkSets or at least the nasty side effects (I cant imagine that our work flow is that uniqe).
And from my point of view our old project level now should be "Workspace" level, because it contains client resources. It seems that Bentley agrees here.
This is not a correct statement. The project in V8i would be your workset in CONNECT not the workspace.
The CONNECT products as Jan mentions needs a Workspace/Workset - there is not really a way around it.
What I have done with my configuration is since all projects for a specific client will not change (they are always the same set of configurations) is set the workspace up as merely a figurehead. There is no real configurations for this, other than to point to the workset. In the workset is where I put all the configurations. I have a workspace with the client name and then a workset with the client name.It seems like a waste setting the workspace and workset to the same name, but really only the workset contains the needed configurations. So instead of setting up the workspace with the clients resources (as you have done), set up the workset with them and just use the workspace to point to the workset.
CADD Manager | CADD Department
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
Answer Verified By: Robert Schwenn
Why would you not set workspace up by client, then workset by project? Since one client can have many projects that share resources, but each project will have its own set of designs and sheets, and plot sets and sheet indices, and project specific files...If all the projects are in one workset, how do you manage those job specific files?
Microstation 08.11.09.919Power GeoPak 08.11.09.918Power InRoads 08.11.09.918
I am not sure I follow. If I pick a workset and browse to a folder called "ramp 203 rework" and open a DGN file, that workset configuration is used. If I then close the file and keep the same workset and browse to a folder called "route 405 bridge widening" and open a DGN that same workset is used. If both projects are for the same client and the same standards are used, why would I need to create separate worksets ? even though different "working" data is in each project, the standards are the same.
I was under the impression that a workset can only have one Sheet Index and such?
you are correct and I feel there needs to be a lot more development in this area. We currently do not use the sheet index.
There are others that may be project specific like item types, or workset properties that could be leveraged, but we currently do not use these. In the future if we do, then yes, individual worksets will be needed under the client workspace.
Currently any testing we have done has not pushed us to the use of any of these features.