Are Worksets really required in Connect

We are currently using V8i SS4 and create our own design files for projects. We do have multiple disciplines: Architectural and Store Planning. Our current drawing folder structure is by Project location which contains each specific disciplines files in one folder.  

It looks like to me creating workspaces as disciplines will create a workset for each discipline. Not quite sure how to make connect worksets work so that it will allow for project location for all files (which is what we would prefer).

Also, we do not want to have Connect stand on it's own with migrating V8i configurations.

My thought was to create cfg files at the workspace (Discipline level) and some how not use or create worksets for each discipline.

Does anyone have an idea how this might be accomplished in Connect? I have read thru multiple V8i to connect migration blogs and items on this forms. So, I would like to have explanation on how to get Connect to work similar to V8i.

Thanks in advance for your comments.

  • Is there away to rename "No Workspace"?

    I don't know, but I guess not. But I prefer to always create own workspace with some meaningfull name, where I have a full control over all settings.

    Regards,

      Jan

  • Thanks Again Jan for your input. My thought to reuse No Workspace may work but, my next question is:

    Is there away to rename "No Workspace"? And it's corresponding cfg file?

    Thank you,

    Roland Cyr

    CE Update 7 - Version 10.07.00.39

  • Hi Roland,

    So, there is no need to use worksets for 200 different projects with multiple disciplines.

    A straightforward, but too naive, configuration can be:

    • Organization: Use to configure everything what is common for all projects
    • Workspace is equal to Location
    • Workset is equal to discipline, so every workspace contains one or more worksets.
    This changes how we have organized our folder structure since 1990s.

    Yes, hiearachical configuration (worksets inside workspace) used now by MicroStation is pretty radical change.

    I was hoping to tame this Connect beast to be configured similarly to the way we work in V8i today.

    I see no problem with such expectation: The configuration cannot be the same, but very similar.

    Breaking our file folder storage structure to use Connect is a non-starter issue for us.

    It requires more detail analysis to decide whether existing structure can be incorporated into standard MicroStation CE configuration or some change is required.

    So, I would be very interested if, there is a way to keep our current folder structure and utilize Connect they way we use V8i today.

    In this blog it's described how worset can be configured to be outside standard structure.

    I don't know details about your current structure, but when I will think about your workspace as about workset (I prefer to use a new structure split to data and standards, but I am quite sure it can be changed back to V8i style), the new CE workspace can be ignored (maybe named by company or something similar), it looks to me pretty similar to how V8i works and probably will not require drastic changes in existing folder structure.

    WIth regards,

      Jan

  • I was thinking that it maybe possible to use no workspace and no workset. Then setup the UCF for our only architect/décor person to load specific dgnlib files. I know its a little more work on my side but, it would allow me to use Connect like V8i. I think this would be possible, any thoughts on this and what kind of issues it may bring down the road.

    We do not use sheets (since we produce about 2 to 4 drawings per project), then provide those drawings to our external consultants to use.

    Any thoughts on this approach.

    Thank you,

    Roland Cyr

    CE Update 7 - Version 10.07.00.39

  • Thank you Jan!

    We are an owner of Multiple Locations and do design for about 200 of our own locations. So, there is no need to use worksets for 200 different projects with multiple disciplines. I could understand this would work very well when doing work for multiple different Organizations. This changes how we have organized our folder structure since 1990s.

    I was hoping to tame this Connect beast to be configured similarly to the way we work in V8i today. Breaking our file folder storage structure to use Connect is a non-starter issue for us.

    So, I would be very interested if, there is a way to keep our current folder structure and utilize Connect they way we use V8i today.

     Any other thoughts would be appreciated.

    Roland

    Thank you,

    Roland Cyr

    CE Update 7 - Version 10.07.00.39