Securing SolidWorks Files
Securing SolidWorks Files
(OP)
After I release a design to manufacturing my design goes to our CNC programmers. Since they use CAMWorks they have read/write permissions to the released design. In doing their work they make several changes to the files that make it very difficult to revise the design.
How do others handle this situation?
My thought is that the CNC programmer should only have read permissions to released designs. But since their program is written on top of SolidWorks I'm not sure this will work for them.
Any suggestions will be appreciated.
How do others handle this situation?
My thought is that the CNC programmer should only have read permissions to released designs. But since their program is written on top of SolidWorks I'm not sure this will work for them.
Any suggestions will be appreciated.






RE: Securing SolidWorks Files
RE: Securing SolidWorks Files
One thing that works the best for me is a complete understanding of the manufacturing process I'm sending my parts into. That way, any changes made downstream need to be justified by the manufacturer--particularly for building expensive injection mold tools, dies, etc. So I try to make sure the design of my parts won't tempt my vendor to make any changes and that works the best for me--apart from sending in parasolid format.
Jeff Mowry
www.industrialdesignhaus.com
Reason trumps all. And awe trumps reason.
RE: Securing SolidWorks Files
Our manufacturing department can copy the parts from the design server and then they save them to their own server.
The they can do whatever they need to.
Afetr a revision change, the ECO process dictates they copy the new version of the part so they can determine what the change requires from their side. (If any.)
Remember...
"If you don't use your head,
your going to have to use your feet."
RE: Securing SolidWorks Files
RE: Securing SolidWorks Files
Pete
RE: Securing SolidWorks Files
Chris
Systems Analyst, I.S.
SolidWorks 06 4.1/PDMWorks 06
AutoCAD 06
ctopher's home (updated 10-27-06)
RE: Securing SolidWorks Files
We use MasterCAM X which reads in native files from all major MCAD programs thus eliminating the need to create a secondary file format. As a side note a lot of FEA programs are doing it this way now. ANSYS will read in native files. Does anyone know why the Kernal devolopers are opening up a little with this issue?
Chris - you keep it up with these snappy replys we will get you over a hundo by weeks end!
Best Regards,
Heckler
Sr. Mechanical Engineer
SW2005 SP 5.0 & Pro/E 2001
Dell Precision 370
P4 3.6 GHz, 1GB RAM
XP Pro SP2.0
NVIDIA Quadro FX 1400
o
_`\(,_
(_)/ (_)
Never argue with an idiot. They'll bring you down to their level and beat you with experience every time.
RE: Securing SolidWorks Files
Funny Heckler.
CAMWorks stores the code along with the part file when saved. I can't remember exactly the setup. But, within CAMworks, you can export the code. When a designer or engineer changes the part, they can send it to the shop, then the shop opens it and imports back the code. The shop can save their codes in their own folder.
The code will recognize the parts features, but if changed I think it will prompt you. Then you add code to additional features as needed.
Chris
Systems Analyst, I.S.
SolidWorks 06 4.1/PDMWorks 06
AutoCAD 06
ctopher's home (updated 10-27-06)
RE: Securing SolidWorks Files
For instance: you give the CNC shop permission to include their cam data, but you deny permission to model parameters... Like the current drm music files, you have to request permission from the publisher.
Stefan Hamminga
EngIT Solutions
CSWP/Mechanical designer/AI student
RE: Securing SolidWorks Files
Pete Yodis
RE: Securing SolidWorks Files
As a business we are trying to shorten the pre-manufacturing time frame by working on projects concurrently. We model the product in SolidWorks, release the models to CNC, work on the drawings, release the drawings to the shop, and then machine the parts. But sometimes we discover a problem with the model while we are creating the drawing and revise the model. If CNC is storing their machining knowledge in the SolidWorks part file their effort to revise the part is minimualized. If they are working with a Parasolid or read-only SolidWorks file they have to recreate the machining knowledge. There are definately pros and cons to both methods.
But the question still is; what is the most cost effective way to operate while providing for the needs and wants of both Engineering and CNC.
RE: Securing SolidWorks Files
Regardless of the CAD system used or the excuses given, once a part file is released it should NOT be changed without a revision documenting the changes. This was true of board drawings and it is just as true with CAD files. There should be an accountability trail documenting any and all changes. If the CAM programmers have to change something to a released file, up rev the file. To remain competitive, you have to be able to account for any and every change in processes and data to ensure your customers that they are receiving what they expect. The large aircraft manufacturers are now seeking sub-contractors with NADCAP certification, and letting data be changed without documentation will doom that certification.
RE: Securing SolidWorks Files
Jason
UG NX2.02.2 on Win2000 SP3
SolidWorks 2006 SP5.0 on WinXP SP2
RE: Securing SolidWorks Files
Not sure if CAMWorks functions within assembly files, that might be the dealmaker/breaker in your scenario.
Pete
RE: Securing SolidWorks Files
Chris
Systems Analyst, I.S.
SolidWorks 06 4.1/PDMWorks 06
AutoCAD 06
ctopher's home (updated 10-27-06)
RE: Securing SolidWorks Files
Just my 2 cents.
RE: Securing SolidWorks Files
I am going to propose a change in the file/folder permissions for the CNC department so Engineering can maintain control of the designs.
I will then propose the following solutions to CNC for working with the models;
1. Import the models as a Parasolid each time a model is revised.
2. Bring all SolidWorks part model into assemblies or bring them in as derived parts, then save the new file in their own directories.
Are there any other valid options?
RE: Securing SolidWorks Files
Jason
UG NX2.02.2 on Win2000 SP3
SolidWorks 2006 SP5.0 on WinXP SP2
RE: Securing SolidWorks Files
But as an organization grows, the need for greater control become necessary. I am trying to come up with a solution that satisfies the engineering department's need to control the design while taking advantage of the ability to store the machining knowing generated by CAMWorks in the SolidWorks files. Thus, making the organization more efficient.
RE: Securing SolidWorks Files
http://www.teksoft.com/camworks/camworks_mill.htm
Read the section on "Assembly Mode". Looks like it would support the workflow you described...
Pete
RE: Securing SolidWorks Files
No arguement here regarding your position. Your type of product is a different situation, as control really isn't needed until it ships to the customer. They should document what they have received (or require an inspection report)and any changes made to it from then on.
Once you sign on to make multiple lots of the same part you will need to establish that control.