5 Replies Latest reply on May 1, 2008 8:44 PM by dan burmenko

    Part Management

    Jason Capriotti
      PDMWEnterprise and Workgroup both seem to more focus on managing documents. We sort of view it the other way with our existing home built mainframe system of "Parts" with one or more documents attached.

      How does or can PDMWE handle this or rather does anyone have a similar setup? We often have one "Part" represented by several files. Sometimes this may be an Excel file followed by a SolidWorks o Autocad file. Sometimes it may be all 3. Usually they are different sheets of the same drawing.

      We also have situations with very large assembly drawings were we had to break out the drawing into multiple files because its too unmanageable to work on one drawing file. Takes too long to load and too large a file (over 100mb).
        • Part Management
          Patrick Kennedy
          Having come from the Teamcenter  realm, I know exactly what youmean .  What I'maccustomed to does not fit within the Windows way ofworking .  We' re com ing to grips with this, and havedecided to use file nam ingto imply the files are all associated to the same  "part ".   In some cases the difference willsimply be in the file name extension, such as 65432.sldprt and65432.xls.  In other cases, like multi-page drawings, the filename itself will be extended, such as 65432-1.slddrw and65432-2.slddrw.  In our test environment this seems to workfine.
            • Part Management
              Bill Hagen

              Pat,

               

              This is almost completelyirrelevant from the topic

               

              But I am an I-DEAS userand the system admin.  We are looking to go to SW and arelooking for a PDM solution to go along with it.  How doesI-DEAS TDM,and/or TeamCenter stack up to PDMWE? 

               

              If you converted fromI-deas to SW, do you have any info you can share?

               

              Thanks

                • Part Management
                  Patrick Kennedy
                  <div dir="ltr" align="left"><span class="993553214-05092007"><fontface="Arial" size="2" color="#0000ff">Bill,</font></span></div><div dir="ltr" align="left"> </div><div dir="ltr" align="left"><span class="993553214-05092007"><fontface="Arial" size="2" color="#0000ff">Wow.  I have lots to sayabout this!  How much time do you have?</font></span></div><div dir="ltr" align="left"> </div><div dir="ltr" align="left"><span class="993553214-05092007"><fontface="Arial" size="2" color="#0000ff">First let me say we are onlypart way through our transition.  We have had PDMWE inpilot-mode for a few months, and have just started moving our firstusers into the production vault.  Those users are not involvedin workflow and do not create released parts/drawings.  Sowe're still very new at it, and still learning.</font></span></div><div dir="ltr" align="left"> </div><div dir="ltr" align="left"><span class="993553214-05092007"><fontface="Arial" size="2" color="#0000ff">There are different aspectsto the transition, some of which are user acceptance, datamigration, and administration.  In general, user acceptancehas been high.  Data migration is being out-sourced to ourVAR, who has demonstrated to us a 3rd-party tool that seems to do avery good job replicating the I-DEAS history tree but doesn'tsupport assembly configurations.  (For better or worse we'vedecided to not migrate the majority of our data.) Administration so far seems adequate but notextensive.</font></span></div><div dir="ltr" align="left"> </div><div dir="ltr" align="left"><span class="993553214-05092007"><fontface="Arial" size="2" color="#0000ff">I'd place the three systemsalong a single line of TDM, then PDMWE, and then TcE.  Wherethis line shows increasing capability and complexity,but decreasing integration.  TDM is clearly the easiestto install and setup.  With PDMWE and TcE Express in themiddle and full-blown TcE at the far end. </font></span></div><div dir="ltr" align="left"> </div><div dir="ltr" align="left"><span class="993553214-05092007"><fontface="Arial" size="2" color="#0000ff">There's a lot more detail I'dbe happy to go into offline.</font></span></div><div dir="ltr" align="left"> </div><div dir="ltr" align="left"><span class="993553214-05092007"><fontface="Arial" size="2" color="#0000ff">Pat</font></span></div><div dir="ltr" align="left"><br><span class="993553214-05092007"><a href="mailto<img class="jive_macro jive_emote" src="http://solidworks-main.hosted.jivesoftware.com/images/emoticons/silly.gif" jivemacro="emoticon" ___jive_emoticon_name="silly" />kennedy@leupold.com"><font face="Arial" size="2" color="#0000ff">pkennedy@leupold.com</font></a></span></div><div dir="ltr" align="left"> </div>
                    • Part Management
                      Jeff Hallgren
                      We are also implementing PDMWE and have the same situation where multiple files represent one Part Number. We are tying everything together using a variable for "PART_NUMBER". Now, when we search we search on that variable and get all the documents related. (sldprt, sldasm, slddrw, tif, jpg, pdf, etc.)

                      We have also written an add-in to SolidWorks that will allow a user to enter the part number, retrieve the file or files and open them from the task pane.

                      Jeff
                • Part Management
                  dan burmenko
                  Jason,

                  I have some suggestions on this if you want to discuss.

                  You can contact me at dburmenko@solidworks.com
                  Thanks
                  Dan