Christiaan Posted November 23, 2007 Share Posted November 23, 2007 Historically we've organised the root level of our Symbol Folders in the Resource Browser roughly into object-based categories: Detail components Draughting graphics Elevation components Feasibility Furniture and fittings Groundworks Layouts Openings external Openings internal Presentation graphics Section components Services Shell components Structural Engineer Services Engineer Survey data The problem I found with this is that it doesn't gel well with the way we actually work: i.e. generally in Plan, Elevation, or Section. When the symbols are organised roughly by object-based category, as above, the organisation of new symbols as they're created created in plans, elevations and sections can quickly become chaotic. And when you're working on an elevation, for instance, you're not concerned about the window plan symbols, you're only concerned with elevation symbols. So my thought was to reorganise the main folders into groups based on our main workflows: 3D Annotation Detail Elevation Plan Section The problem with this, however, is, say you're working on some large scale bathroom plans and elevations. You're now faced with the plan symbols being in one section and the elevation symbols being in another, whereas in our previous organisation we had all such symbols in one root-level folder (Furniture and fittings). So I'm curious how others organise their symbol folders? Maybe I need a mixture of both methods of organisation? While I'm sure there's no magic formula I'm sure there're others out there doing it better than I am. Quote Link to comment
Christiaan Posted November 28, 2007 Author Share Posted November 28, 2007 Anyone got any advice on this one (got buried after I posted it on a weekend)? Quote Link to comment
brudgers Posted November 28, 2007 Share Posted November 28, 2007 A third option is to organize the components by the sheet where they are used - which is a little more CAD oriented than BIM oriented. Any system will be somewhat arbitrary, but the development of projects often correlates with the production of sheets and sheets are ultimately how the project requirements are communicated in most cases. Your milage may vary, of course. Quote Link to comment
Chris D Posted November 29, 2007 Share Posted November 29, 2007 Attached is a VW13 file with our standard symbol folders if you're looking for examples Folder names are coded for BS/Uniclass (UK specific). This is fairly new and I haven't used it myself yet so can't offer much in the way of feedback on how it works. Quote Link to comment
Petri Posted November 29, 2007 Share Posted November 29, 2007 This is indeed interesting. The UK-based dissidents seem to have a very clear and relevant view on The Structure of the CAD Model, but the Home Team has, once again, dropped the ball. Apart from CAD-operator point of view and unless one is into Heavy Scripting, symbol folders are pointless. Purely a cosmetic feature: in a report of symbols, you can't have a column for the folder in which their definitions reside. Now, someone like yours truly could use symbol folders in reporting and such, but... (I'll reveal all my Trade Secrets immediately after NNA releases its objects and commands without encryption.) Quote Link to comment
Christiaan Posted November 29, 2007 Author Share Posted November 29, 2007 Yes, or as I put it some time a go, the Resource Browser is an dog. It did I say it sucks. I can't remember which. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.