3 Replies Latest reply on Mar 18, 2014 12:41 PM by Kevin Bruce

    Enterprise PDM and Parts Derived from Bodies in Other Parts

    Kevin Bruce

      SW and EPDM gurus,

       

      I use bodies in my parts a lot.  Enterprise is fairly new to us so I was curious what strategies or best practices for handling these files are used, what works, what doesn't...  I'll save a body out to a part and that part is what get's tooled / manufactured so it get's a part number, drawing, etc.  But to be able to make future revisions it needs the parent file.  I don't give a part number to that part but I do check it in.  Should it get a "released" revision number and "released" status?  I'm not sure what to do with this thing.  I would like it to be obvious to other users that this part is derived from another part.  Make sense?  Your thoughts are appreciated.

       

      Kevin

        • Re: Enterprise PDM and Parts Derived from Bodies in Other Parts
          Brian McEwen

          Your master part should be stamped as a Revision to protect it.  Ideally it would have some kind of part number - but per best practices it must at least have a unique file name.

           

          I don't have all the answers, but that is another thing for me to test...

           

          Here is an example to think about.

          multibody example.JPG

          Disappointing that if you look at Where Used or Contains on the master multibody part 3-11-14.SLDPRT file it has nothing.  However, on the plus side, if you change the state on one of the parts or on the assy the master part is included. So I think you send them all through the workflow to released state at the same time as the drawings. Also any time you go to check out one of the children the master part shows up as something you can also check out.

          • Re: Enterprise PDM and Parts Derived from Bodies in Other Parts
            Tim Read

            As a general rule we do not allow this type of workflow.

            The Designers / Engineers that what to use this methodology assume that it gives them more control and freedom but it really make for greater risk of unintended changes due to changes in the parent part. In fact, you need to protect that parent part even more so. It needs to be revision controlled and requires strict checking after any change to ensure that only the parts (bodies) that were intended to be changed are and that those parts are being released.

              • Re: Enterprise PDM and Parts Derived from Bodies in Other Parts
                Kevin Bruce

                Tim,  Thanks for you input.  I'm starting to come around to your way.  It's a cool design tool but could cause too much room for error.  After designing this way do you have a best practice for then right as the designs seems pretty solid to break the ties and make the 'saved out body parts' be standalone with all the features included?  I notice under references there's a check box that says include all feature if links are broken (or something like that) but then when you break the links nothing like what is implied happens.  it's just a dummy part now as if it's been iges'd in.  Anyway, thanks.