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).
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.
CADD Manager | CADD Department
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
I was under the impression that a workset can only have one Sheet Index and such?
Microstation 08.11.09.919Power GeoPak 08.11.09.918Power InRoads 08.11.09.918
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.
Hey, thank You all! The answers are clear and I feared them. So, I'm closest with Tim in living with and working around the new mandatory config level.
I've been down this path with a lot of clients.
If you're working with DOT's and using their configurations, then the Client will become the WorkSpace, and then each client WorkSpace will have one or more WorkSets. Unless, that is, you're working with North Carolina in which case the discipline area becomes the WorkSpace.
There are pros and cons to the one WorkSet or multiple WorkSet workflows. If you're using ProjectWise you will have multiple WorkSets per WorkSpace, or one WorkSet per project.
Rod WingSenior Systems Analyst