jeff_philips
23rd August 2007, 05:23 PM
Hello,
My company is in the process of both implementing a 3D CAD system, SolidWorks, and achieving ISO certification. We send our SolidWorks files to an outside machine shop to machine parts like small housings for our printed circuit boards.
Our QA manager has intrepreted various ISO provisions (I don't know which ones) as requiring that revision information be included in the file names of any files we send to outside vendors like our machine shop. More subtly, he might say that it must not be possible to separate the file name from the revision information. For example, we might send out a file named widget_rev_A.par to indicate that the part to be machined is revision A of the widget part. All our machine shop's customers follow the practice of including a revision letter or number in the file name.
Unfortunately, this practice of including revision information in file names and renaming files with a different revision letter every time the revision changes utterly defeats the file referencing needed by the CAD system's data base; the data base maintains the linkages between parts and their drawings and between assemblies and the parts they contain. Suppose widget_rev_A.par is used in several assemblies for example. If I modify the widget part and rename it widget_rev_B.par, all the assemblies remain linked to widget_rev_A.par--unless I open each assembly and manually tell each one to use widget_rev_B.par. The file names of parts in 3D CAD systems are not supposed to change. The revision property contained inside the file name may change, but the file name referenced by several assemblies must not. By not renaming the file, I may change the part and have it automatically updated in every assembly.
I hope I made this clear. It seems that the 3D CAD system requirement that files not be renamed is in direct conflict with ISO requirements. Following the ISO requirement utterly defeats a 3D CAD system's ability to maintain linkages between files and probably makes it more likely that an outside vendor receives the wrong file, which is exactly opposite the intent of the ISO requirement.
Anyone encounter this before and know what to do about it?
Thank you, Jeff Philips
My company is in the process of both implementing a 3D CAD system, SolidWorks, and achieving ISO certification. We send our SolidWorks files to an outside machine shop to machine parts like small housings for our printed circuit boards.
Our QA manager has intrepreted various ISO provisions (I don't know which ones) as requiring that revision information be included in the file names of any files we send to outside vendors like our machine shop. More subtly, he might say that it must not be possible to separate the file name from the revision information. For example, we might send out a file named widget_rev_A.par to indicate that the part to be machined is revision A of the widget part. All our machine shop's customers follow the practice of including a revision letter or number in the file name.
Unfortunately, this practice of including revision information in file names and renaming files with a different revision letter every time the revision changes utterly defeats the file referencing needed by the CAD system's data base; the data base maintains the linkages between parts and their drawings and between assemblies and the parts they contain. Suppose widget_rev_A.par is used in several assemblies for example. If I modify the widget part and rename it widget_rev_B.par, all the assemblies remain linked to widget_rev_A.par--unless I open each assembly and manually tell each one to use widget_rev_B.par. The file names of parts in 3D CAD systems are not supposed to change. The revision property contained inside the file name may change, but the file name referenced by several assemblies must not. By not renaming the file, I may change the part and have it automatically updated in every assembly.
I hope I made this clear. It seems that the 3D CAD system requirement that files not be renamed is in direct conflict with ISO requirements. Following the ISO requirement utterly defeats a 3D CAD system's ability to maintain linkages between files and probably makes it more likely that an outside vendor receives the wrong file, which is exactly opposite the intent of the ISO requirement.
Anyone encounter this before and know what to do about it?
Thank you, Jeff Philips



