1 Reply Latest reply on May 17, 2011 10:09 AM by John Burrill

    Drawings Functionality

    Dean Baragar

      I'm wondering if anyone thinks it would be beneficial to have a "parent" or "master" drawing file that would have the same concept as an assembly in a model in that it would be a collection of smaller files ordered in a certain way. It would make the creation of production documents very easy as the files could be larger, run faster as not all the files would need to be loaded...only previewed unless editing were to take place) and still allow access to induvidual files and searches for induvidual part drawings to be possible.


      As an ever so simple example if I had a pair of sunglasses (it's just what's sitting in front of me at the moment) I would want to have a "parent" drawing which would (roughly) consist of the following pages: <1> Assembly drawing/BOM <2> Hardware List <3> Parts List <4> Left Hinge Part Drawing <5> Right Hinge Part Drawing <6> Main Frame Part Drawing <7> Lense Part Drawing (my sunglasses consist of one lense).


      In the event that this lense is used in frames of other finishs there is no point to creating and maintaining a new drawing of the same part in a file that contains multiple drawings as I believe a file containing multiple drawings would be more useful than our current process of creating single page drawings for everything.


      Ultimate Goal: Have a single file that draws from seven other files (refer to example above) to create a "parent" drawing while still having single part drawings that exist and can be used in other production documents and also be found by doing a search in Windows or SW Explorer.

        • Re: Drawings Functionality
          John Burrill

          Sounds conceptually like an Acrobat portfolio-Or Autodesks Sheet Set Manager for AutoCAD

          On the one hand it could be good to have another heirarchal level to kind of hang things off of-especially if it presented itself as a drawing Tree.  It might make preparing a tech-data package a lot simpler.

          Couple problems I forsee:

          1) reference management becomes more complex: To rename a drawing, you now have all of the same considerations that you do renaming a model.

          2) file management becomes more complex.  You now have all of the same headaches of missing references that you do with assemblies

          3) OK, in my industry and the last three companies where I've worked,   the top-level assembly with a BOM is about as top-down as a product gets.  All of the other master informat like routers, work insturctions and stuff like that is managed in the ERP system.  When you introduce a file type that doesn't have an analog document type in your organization, your bound to have one inadvertantly constrain the other.  This is one of the reasons Sheet Set manager doesn't get used too often

          Still, I like the idea.  As with most new tools in Solidworks, it's success or failure would be determined by how well it's integrated with the rest of the solidworks functionality.