Search the Community
Showing results for tags 'symbol library'.
Hi, I’m looking for any advice and tips people are willing to throw my way. We are a smallish architect practice and Im hoping to streamline our scheduling of things like plumbing fittings, equipment/appliances, lighting, furniture etc. We don’t have a standard way of doing this, and what we do basically involves a lot of callouts and notes that have to be reinvented for each project. We have a good library of standard 2d and 3D symbols for all this stuff. What we don’t have are custom records or data attached to most of it. Nether do we have a decent collection of data tags, or custom worksheets for reporting on this stuff. So I’m now looking to add custom record fields with symbol specific data to the symbols in our library and from this the plan is to be able to drag a symbol into a project, slap a data tag onto it and have some nicely set up worksheets on our drawings available to display the preformatted symbol data. We can then add and edit the data as required for the project from within the worksheet to pretty quickly spit out plumbing, equipment, lighting and furniture schedules on drawings. This is something I have wanted to do for some time but it is quite a leap from how our office has done things in the past so I’ve always thought if I’m going to do it I need to do it really well. I know it is the way forward and wil be a massive time saver, but a half baked system won’t get the uptake I need for it to become established in our office. I’m now taking the dive and would dearly appreciate the advice of people who perhaps have driven this road before. So I know the basics of how all this works and yesterday I thought I’d start out with plumbing fittings. So I spent some time first creating a custom record format for plumbing sanitary fixtures. I thought through what fields I would need and how setting up the correct fields would impact on how the info would be pushed through onto worksheets on drawings. I set up an “ID” field as well as “Fixture Type”, “Style”, “Location”, “Description” fields. So for example a wash hand basin might be: ID: WHB Type: Wash hand basin Style: Wall mounted Location: [project input] Description: Caroma Caravelle 500 Wall basin with methven blah blah mixer, 40mm outlet etc etc. I thought while I’m at it I might as well add some more record fields that may be useful so I stuck in “Manufacturer”, “Model”, “Model No.”, “Finish”, “Size” and “Price”. Though most of this could be covered in the “Description “ field. I then made a Data tag that would attach to objects containing the Plumbing Fixture record. The data tag would display the ID field and help anyone reading the drawing see which schedule item related to which item(s) on the drawing. I then started attaching the record to the many plumbing fitting symbol definitions in our library and one by one editing the field data to suit each symbol. This was very tedious but I kept reminding myself that it would save a lot of time in the long run. This isn’t the first time I have done this, I have managed to do this sort of thing on various specific projects but it is the first time I have set it up as part of a library with the intention for it to be an office standard. So developing a pragmatic, flexible, intuitive system that makes sense and is easily applicable to the various types of projects we do and that everyone in the office can understand and benefit from is the tricky bit! Are there people out there who have “been there done that” before and can offer some great tips? Questions: Do my custom records need anything else? I must have edited and re-edited them a dozen times trying to figure out if they covered everything off. Or should I trim them right back to keep them really simple? Any suggestions appreciated. It would be good to know if there is a quicker way to add data to symbol definitions. That is by far the most time consuming aspect of this. I know there is a command to add a record to all symbols in a selected RM folder. But subsequently editing the data from the record field defaults to something specific about the symbol it is attached to is painfully slow. Can the Data Manager be used for this? I had a look at it and found it more confusing than anything else. Do I need different records for plumbing fixtures, equipment and furniture? They would all have the same type of “ID”, “Type”, “Style”, “Location” and description fields so why not just have one record to cover them all? If they all used the same record I could more easily combine them all into one worksheet which would be useful and they could be all covered off with one type of data tag. I could also use classes to filter stuff in or out of the worksheet schedules. For worksheets is it a good idea to have individual worksheets for each sheet of a project file calling up the data from all the symbol data present just for the viewports present on each sheet? Then also have an “editor” worksheet so that data from all plumbing fixture symbols (or equipment symbols or whatever) in the file could be managed in one place? Or is there a better way this is just creating unnecessary work? Any tips on setting up useful data tags? Could some generous soul please share their own super flash custom data tags? Mine look pretty crap... Well done for making it all the way down here and thanks for even reading all this! Hopefully you are inspired to share you IP!! Cheers.
Good afternoon everyone, first would like to start off by saying happy new years ! I've been playing around a little bit with the callout tool, however i discovered a bug. I've been trying to create a symbol detail library to reference for standard wall details - and i've recently discovered the callout tool (earlier posts) I really like the feature it has where it can generate a legend for a series of callouts - and then just that legend can be modified for that particular element. But i don't think this tool has been fully developed. The callout tool isn't designed to be inserted into symbols, something ive been trying to do. It loses its properties and generates a separate note for every callout every time it's dropped, something that i don't want to keep fixing all the time. Could anyone please confirm this is the case? Does anyone else think this is a bug?