We are beginning to setup out new CONNECT workspace environment, I'm unclear about the best way to do this. This is a multi-office, multi-disciplinary, multi-client and multi-project environment.
Here is what I need to accommodate:
OpenRoads
OpenBridge Modeler
Microstation
ProStructures
Multiple disciplines (transportation, mechanical)
Multiple clients in each discipline
Multiple projects for each client.
Currently, before CONNECT we have separate environments with separate standards, i'd like to make use of the same files if I can. So I don't know if i can define these at the organization level (can you have more than one?) or at the Role level (how does that even work?)
Workspaces and worksets are easy enough, but im not sure where to define the standards that are specific to each software. OpenBridge and ProStructures use common client dgnlibs and resource files but they also use templates, cells dgnlibs that are specific to the software AND each client.
Trying to keep this simple but also not confusing the users with information they don't need from a software they arent using. I'd also like to make this easily adaptable to new client and projects, ie i don't want to do this at the work-set level.
any advice?
anyone follow up on this topic?
Looking for a best practice setting up Network workspaces that are shared by both MicroStation Connect Edition and Openroads Designer, all of the help I have found has been for one or other.
Please see Marcs much more complete answer below. Mine is written from a fairly simple task flow using a single Organization.
[I can only comment on the most basic aspects. I'm 15 years out of the multi-office multi application environment. But when I left, all the application softwares used the same ustation engine, so you would get your configuration loaded for Microstation, then overlayed with InRoads or whatever.
So a Workspace is a discipline, and each client (or group of clients) is a Workset. Not knowing how many clients, how many projects, you may want something different. Once set-up you can use a Batch Process to add the individual files to each workset.]
Connect r17 10.17.2.61 self-employed-Unpaid Beta tester for Bentley
Hi Michael,
Sorry we didn't pick up on this earlier!
I can't offer an immediate guide to cover all of these applications but can suggest the following:
CONNECT Configuration is designed to have only one Organization.
The WorkSpaces within each Organization are intended to accommodate organizational sub-divisions such as department/discipline/location/Joint Venture/Major Client etc.
Multi-disciplinary implies that WorkSpaces per discipline are not appropriate, the list above suggests that a WorkSpace per Major Client would be appropriate containing that client's WorkSets.
Resources that are common to all WorkSpaces can be stored at the Organization level by pre-pending or appending paths in Organization level CFG files (CFGs placed in a location such as \\SERVER\CONFIGURATIONS\CE\Organization will be read).
WorkSpace CFGs can specify client specific resources.
I'll look into how the Role level might be helpful to your scenario.
Marc
Michael, I've set up similar to what you're looking for. To have a look at how I've built things check out https://communities.bentley.com/other/old_site_member_blogs/peer_blogs/b/bear_blog. I have set this up in CE and will be updating the blogs soon. The basis is easy enough to adapt to suit any needs.
Hello, Has anyone found a solution to this yet? I have the same issue where Microstation CE and OpenRoads CE don't seem to be able to share the same WorkSpace and WorkSets. It would be nice for MicroStation CE users to be able to open Microstation and access .dgn files that are in the OpenRoads WorkSpace. Any help would be appreciated.
Thanks!