• State Not Answered
  • Replies 6 replies
  • Subscribers 20 subscribers
  • Views 3037 views
  • Users 0 members are here

Are Worksets really required in Connect

Roland Cyr
Offline

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.

Parents
  • 0 Offline

    Hi Roland,

    are worksets really required in Connect? In my opinion yes, they are required. I think at least one workset is mandatory (has to exist) in every workspace. I am not sure whether MicroStation configuration can be changed manually in such way there will be a workspace with no workset. Probably yes, but a question is whether it's wise and what conseqences (incompatibilities) will be.

    More important question is what is the best meaning (purpose / role) of workspaces and worksets. This is completely up to you, there are no restrictions whether workspace will be created per customer, project or whatever else. Worksets role depends on workspace, so when workspace will be e.g. project, workset can equal to discipline or subproject (e.g. by a location when the project is geographically huge). And of course perfectly valid is also a schema with only one workset (maybe named default) in every workspace.

    Roland Cyr said:
    It looks like to me creating workspaces as disciplines will create a workset for each discipline

    I am not sure whether I understand your sentence correctly. From the first paragraph my feeling was that workspace will be equal to projects, so every workspace will contain necessary disciplines (worksets).

    But you can also create a workspace per project, create only one workset and to have more folder per discipline in your "dgn main folder". It makes sense when all disciplines share the same resources (seeds, cells etc.), so there is no reason to split them into own worksets.

    Roland Cyr said:
    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).

    There are two important rules:

    • Everything is hierarchical by default, so Organization resources are shared for all workspaces. And a specific workspace resources are shared over all worksets in this workspace. So whatever you will place (maybe some manuall modification will be required) into Standards folders will be shared over all worksets.
    • They are just standard configuration files, so when not standard configuration is required (e.g. to include a specific folder outside standard structure etc.), it can be done quite easily.

    Marc Thomas wrote a lot of really useful blogs about MicroStation CONNECT Edition configuration. Especially configuration guide series is perfect.

    Roland Cyr said:
    Does anyone have an idea how this might be accomplished in Connect?

    My experience when I have discussed the migration with my customers is that it's better to focus on how data are structured, how ownership works and in what packages they are delivered. Based on such schema, a structure and assignement what should be in workspace and what in workset(s) can be created. To conifgure MicroStation is the last step.

    Roland Cyr said:
    So, I would like to have explanation on how to get Connect to work similar to V8i.

    In my opinion CONNECT Edition works pretty the same way as V8i, there are not so many differences when a new terminology is accepted.

    With regards,

      Jan

    Bentley Accredited Developer: iTwin Platform - Associate
    Labyrinth Technology  |  dev.notes()  |  cad.point

  • 0 Offline in reply to Jan Šlegr

    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

Reply
  • 0 Offline in reply to Jan Šlegr

    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

Children
Communities
Support and Services
Training and Learning
Social Media