I know that I am probably opening myself up to a load of grief but anyway!!
As part of the CE Bentley have been pushing us the users towards the use of ‘worksets’ and seemingly removing access to parts of the program if we don’t use them. E.g sheet indiexing.
Our company has never used worksets (projects) in all the 25+ years that we have been using MicroStation. The main reason for this is that there doesn’t appear to be any benefit for us to go down this route. This is mainly due to the setup we have. We have, on our server, a copy of the system/standards install folders which include one customised DGNLIB, one customised .upf, one customised seed file and a number of pltcfg files which have been set up to work directly with various printers on the network. We also have a set of company drawing title sheets. At the time of install MicroStation is then pointed to this server folder. There are separate folders for CE and v8i.
These files give us everything (tools, levels, etc) that we need to be able to produce models and drawings for whatever client that we work with. We don’t need or use customised drawing title sheets, unless a particular client wants his logo adding. The logo is added to one sheet and then model copied in one 'drawing sheets' file.
The other item that we have on the server is a standard 'Project folder structure' which includes separate folders for drawings, documents, correspondence, etc. This is the first thing that is copied and renamed for every new job that we have. This means that we have no need to create any additional folders as part of worksets. In fact we are not allowed to create any new folders.
Based on the above, the question to all you workset users is what is the benefit to us? At this time I can’t see one but am open to suggestions!
WOW Stuart... that is an open question.....
1. You can group your worksets by series, year, or client
2. You can force different standards per workset ie seed files, colour tables etc
3. You can force PDF outputs the the project out folder
4. You can have project related preset sheet files (titleblocks)
5. You can have project based Display Rules
6. You can have project related Item Types
There are a lot more.....
Ian. It is an open question, by intent.
Of the six items listed no. 3 is the only one that would help us although we don't have great deal of problem at the moment. As noted we only have one set of standard files, including title blocks so having differing seed files, colour tables is not relevant. We don't use Display Rules or Item Types.
So how do you control the project titleblock text? ie do you manually type the project text
Have you tried Display Rules
Have you tried Item Types
Ian Lapper said:So how do you control the project titleblock text? ie do you manually type the project text
Do it once and then model copy the sheets and then updating title and drawing number.
Ian Lapper said:
Yes and No. Couldn't get DR's to work with our workflow. We use Bylevel symbology through Level Manager.
Ok, lets see if we can get through this again.
stuartw said:As part of the CE Bentley have been pushing us the users towards the use of ‘worksets’ and seemingly removing access to parts of the program if we don’t use them. E.g sheet indiexing.
Sheet indexing is an organization of Sheet data per project. Most people organize their data based on projects (workset in MicroStation), I believe you yourself have described the directory structure on your server is project based. There for it is kind of logical that a sheet index would be project centric. If a user could simply put any sheet into any index or a sheet didn't know that it belonged to an index then how would we keep this data organized/structured? Without the software know what project you are working on how does it how which idex to present you? If there was just a large huge Index for the application then the data would need to be organized within it. How would that be structured. I am not sure exactly your point. How would you like an index to work? Something to consider would be how does the application know what index to use at any given time?
The rest of your setup sound lovely. It sounds like you have exactly the information you need where it belongs. I do have some questions though. For title blocks do you reference them of place them as a cell? Do you reference anything back to the Organization level? How are you archiving the projects? how do you bring the data back from archive? If you referenced from the organization level what about that data is it versioned?
WorkSets can be used for anything that is project specific. That is the biggest benefit to them. I can't imagine that you don't have any data that is project specific, but maybe you do.
Another little benefit to WorkSets is that the Workpage and Back stage both list the last x number of files you opened under any one workset. If you are using no workspace/set you only get the last x number of files you opened. Though this is small eventually I hope you see enough small things to help you want to move. Some times its not about one big get but instead many small ones.
Don't be afraid to question the status quo