Thanks for the replies. My thoughts:-
1) Changing finished parts/assys to read-only seems to be the consenus thing to do, if you don't have a PDM system to do it for you. Does anyone know of or have a system (macro/VB program) to automate this, as finding the right files manually and changing their properties will be a PITA.
2) Kalle wrote:- "You have an assembly with some parts created in it with references to other parts in this assembly. Now all your parts are read only except for the part that you want to modify. You modify it and some other part (set to read only) that has references to the part you change gets changed (due to the read only state only on your harddrive). If you now open the drawing for that second part it will show the changed state because SolidWorks has changed the part in memory (even though you won't be able to save the changes - the part is still read-only). Now you print that drawing and voila you have a wrong drawing that might get into the workshop."
Is this true? - if so, it's a big weakness of SW, and one that presumably applies whether or not you have a PDM system i.e. if SW can rebuild a read-only part in memory because the part driving the in-context relation has changed, then this will happen woth a PDM system too.
Jerry said that using Activault or PrductCenter that the database would remain unchanged - I'm sure that is true, but does not mean that what you see on the screen is valid, if Kalle's sceanrio is correct.
3) Seth wrote:- "Since none of the PDM systems that I looked at had a foolproof way of determining the difference between a model that actually changed, or a model that just got saved more recently, I opted to go the route of making my files read only when I am done with a project."
I was an I-DEAS user, and it had a "part compare" function that compared the surfaces and highlighted what had changed. I think you could also do an "assembly compare" that compared what instances/components it comprised.
4) John Layne wrote:- "I opted to map the PDM Revision not to the standard "Revision" property in SolidWorks but to a property called "PDMRevision". Thus revisions on the drawing are driven from the part files "Revision" property which is manually controlled. "
This sounds dangerous to me - what happens when you change the drawing but not the part? e.g. change the "finish" details, change a dimension tolerance, add a note. The drawing needs up-issuing even though the part has not changed.
5) TOP wrote about versions and revisions, a distinction that I'm comfortable with. However, are you saying that PDMWorks makes no distinction between the two? If so, is it still not possible to create a custom property called "issue" that the user manually assigns when checking parts back in, and then your manufacturing system only looks at the status of this "issue" field? The I-DEAS pdm system prompted to manually assign a revision when checking items in, so if you've only corrected a spelling error on a drawing, you could check it back in with the same revision, even though a new version was created.
6) Len Mar (and others) suggest having a separate folder/database with "released" pdf's of drawings in it, and that this is all that is accessed by non-designers. I have used such a system before, and it has benefits. If your PDM system is smart enough, the creation of the pdf file can be automatically triggered by someone signing-off the item, separate from the act of checking it back in the vault.
A drawback of such a system that only does this with pdf's of drawings, is that there is frequently the need to exchange data with suppliers & customers in many formats such as dwg, dxf and 3D geometry in parasolid, STEP, IGES etc All these other formats may still be uncontrolled, unless the PDM system also handles this well. Can PDMWorks do this? - if not, are there other systems that are affordable for a small company (20 employees, 5 designers)?
Cheers, John Harland