I don't like description in my file name. I find I spend toomuch time trying to come up with a good name for a part that I amnot yet even sure what this part's final function may be...and if Iam wrong then I have to rename the file. Though I must admit withthe new virtual components in 2008 this problem is lessening.
Same file name for part and drawing makes things a lot easier.Can you use multiple sheets?
Just bumping this post.
The company I am contracting to are just in the process of evaluating PDMWorks Enterprise. A discussion on this topic would greatly assist our evaluation.
Looking forward to more posts
OK, I'll jump in, but first the caveat: we're just now moving into production with PDMWE so a few things are still undecided.
We have a folder structure used for each development project. All files related to a project are stored within its structure. Non-CAD documents are assigned the project property, but do not receive a part number and are allowed to be any file name.
We have a serial number for .SLD* that assigns what we call experimental part numbers to new files. This part number is used for the file name as well. Then, near the end of the development cycle, official part numbers are assigned from our ERP system, and the .SLD* file names and part number properties are updated.
We have enabled unique file names and part numbers for .SLD*. Of course, that prevents the drawings from having the same part number as the model, so we append a "D" to the drawing part number. The model and its drawing have the same file name, so finding files is easy. We don't allow separate drawing files for other sheets, so this works for us.
Our desire is for the model and its drawing have the same part number. I have considered giving the drawing a different variable for part number so as to allow this, but have yet to try it...
Hi Patrick -
Regarding your desire to have the model and drawing use the same part number, you can do this using a file template. Essentially you create the part and drawing at the same time using the same template variable during the creation.
The attached zip file contains an example (2008).
prtdrwtemplate.zip 120.4 KB
I realize this is an old posting, but I'm presented with a very similar problem. I currently have PDMWE setup so that each new SW model receives a "temporary" part number (format = T#######, ex: T1234567). Then at the time of the release, the file is assigned one of a number of different formats. For example, either a "million" number or a "purchase part" number (format = ####### or ##@##, ex: 1031234 or 24P53).
How can you automate this rename process so that all of the references are correctly updated? I realize that all of the parents of the file being renamed will need to be checked out. This is not a problem.
Also, if anyone could explain to me what is going on when a user does a right click - rename, that would be much appreciated. I cannot find any documentation on this. And I realize I'm going into places I probably shouldn't with this one, but it doesn't appear to update the file name properly in corresponding index.xml file on the server.
Any help here would be appreciated. Let me know if I need to be more clear anywhere. Sorry for the long post.
Vital topic, thanks for raising it. I have just moved from the enormous Ford Motor Company world of Catia/NX/TeamCenter into the world of SolidWorks/Enterprise. At Ford users never saw "filename" unless they really looked, and it took its value from Part Number. Also, Drawings automatically inheritted their part number from the referenced Part or Asy. If the referenced item already had a drawing, the user had to add a secquential number to the Dwg part number.
I will be monitoring this thread as I develop my best practices for Part Numbering - filename - Dwg.
What group did you work with in Ford? I worked in Powertrain (Engine and Transmission)...
You can use Dispatch to do the rename, but, you need to be careful as it may not update files that reference the renamed file. (Also, you will need to be using 2008 SP4 at a minimum as some rename issues in dispatch were fixed in SP4)
[My last assignment at Ford was in PT, in the PDC building, ending a few months ago. I was a TeamCenter guy, but my background is in Engineering. Before that I was in the Alpha building doing QA on TCe, then before that involved in TCe (and metaphase/tdm) training and supplier implimentation. I'll see you in class next month!]
I really want to learn how to get Office docs sensibly integrated. It seems that they really must have embedded in them the meta data from Enterprise, or else people viewing the doc via email or printout will have no idea who/what/where/when, right? One great remedy that Enterprise can, and should, provide, is when users see an Office doc, there should be no more mystery about who wrote the doc, where to find it, what version/rev they're viewing, who has approved it, etc. No more cramming all that info into the (uncontrolled) filename!
Hi Phil -
I worked all around (engine group in dearborn, transmission in Livonia, ACG, and a bit at the research center in the styling dome)- I was with CV then.
TeamCenter - did you work with my buddy John Laryz (sp)?
Anyway, I'll see you in August - the first thing you can utilize if the documents cutom properties - beyond that you can use embedded macros to do other types of mappings within documents.
p.s. this macro is from the admin guide... read the section titled: Mapping variables to file properties and embedded data > Microsoft Office Files
To add a macro to normal.dot:
1. Start Microsoft Word.
2. Select Tools, Macro, Macro (or press Alt +F8).
3. In the Macro name field, name the macro AutoOpen and press the Create button.
4. In the code window, type the following macro code (insert the code between Sub AutoOpen() and
Dim aStory As Range
Dim aField As Field
For Each aStory In ActiveDocument.StoryRanges
For Each aField In aStory.Fields
5. Save and close the code window
Next time you open a document with fields, the fields in the body and header/footer will be automatically
updated. (Note that when the fields are updated, the document is modified and Word will ask if the new
changes should be saved when closing the document.)
So I tried using Dispatch to rename the file. As far as I can tell, all this does is a windows rename. It doesn't appear to take the "where used" or the index.xml file into account. Am I correct here or am I missing something?
That is correct, however, I did get it to work after I had checked an assembly and it's references into the vault. I can't rememebr the exact sequence however.
In any event - I wouldn't count on it if you already created references.
I wasn't sure if you had used the part in an assembly yet or not.
Thanks for the help, but unfortunately, references will have been established by the time the rename is required.