Webinar Announcement :
Subject Best practices and interconnectivity for tool, holders adapter, catalogs, shop documentation, tool lists , 3rd party potential solutions
Date To Be determined by COE DPC / DS
COOL: There will be multiple speakers
Main Speaker: Mark Chitjian COE DPC
Agenda
(Subject to ideas from you but here is the start )
1. start with a demo of using excel to start a catalog with VB
2. Talk about the 2 different kinds of holders, User representations / and those made with the GUI
3. Talk about the collision checking differences with these 2 different holder types mentioned, a Possible enhancement.
4. Invite any 3rd party tool management system, to describe their solution to us.
A.: I already spoke with (CGTECH), and he can have someone do a short demo on CATIA V5 interface
B: I already spoke with Steve Sullivan (TDM), and he can have someone do a short demo on on the Tool Data Managment package.
I am sure Daniel Pyzak (Dassault Systems), will want to participate, and I will speak with him 12 noon PST tomorrow
This is #8 on PAC-MEN list
This shows a continuing effort on progress with the PAC-MEN & Dassault Systems, & COE working together.
Right now, I think the solution for FMI, is to:
Create a Master Catalog in Excel
Use the Use My Model feature, to use a Catpart, as a user representation.
Use CATIA V5 interface to create tool list for Vericut
We PAC-MEN can discus our requirements, for the BIG PICTURE
I would like to try to Get Dassault Systems to enhance the software to:
1. use the user representation for all collision functionality, and 3-5 axis, etc.
2. Possibly create a new functionality, a linked tool catalog, not slurping tools out of the catalog, and placing them on the resource list
3. Where there is a tool catalog where multiple can users can use the same tool catalog, and there is some kind of live update.
Once again, the best questions are asked by the Beachman
Here it the thread that started it all. slurped from Steve Beaches thread
What's everybody doing for their cutters / adaptors / assemblies ?
The basic question stems from maintaining accurate representations of cutters in their holders, ensuring the latest changes are in the CATProcesses., without duplication of work by having to define the SAME cutters on several software's.
Our dream is to
1) Have a cutter defined somewhere
2) Have an adaptor defined somewhere
3) Have the ability to call up an assembly of cutters / adaptors / secondary adaptors etc. 4) Have the SAME definitions be able to work in Catia, Vericut, and our ERP system. (ie: avoid the duplication of effort !!)
Our ULTIMATE dream would be that if ANY of the component were updated, the next time you entered into a CATProcess, you would be flagged that one or more of the cutters in th CATProcess have been updated since the last save. Then you could decide to update to the newest, or re-create a cutter that will keep the current CATProcess AS-IS.
Example......
1)A Catprocess as a 1" end Mill w/ a 4.500" stick out.
2) We update the stick out on the cutter to 4.4".
3) We want the CATProcess to at LEAST flag us that the cutter has changed and we will need to verify that it still valid....or make an update to our program.
Any ideas guys ?
What's working ?
What' not ?
Are you defining cutters offline in Catia, then using them as NC Representations ? Walter TDM ?
How does all this integrate.
This is anothr BIG subject.......
Regards,
Steve Beach
Supervisor N/C programming GKN Aerospace - Monitor Inc.
Amityville, Long Island, NY
I think links to all the relevant posts should be in one place.
I will work on that
Dave
|