Catia and working on networks

[thixoguy2]

Hi All,

At work I keep all of my files on the company wide network. I find that I am encountering problems with significant wait times for very simple updates. The CAM guys have similar problems so they routinely copy the file to their own drive and things seem to work a lot quicker and at the end of the day they place the file back on the network, overwrite the original and they are good to go. It should be noted they tend to use individual files.

I would like to do something similar but am afraid I might screw up links with assemblies etc. How do you guys deal with these kinds of problems? I am not really a computer guy and I suppose I should spek with my IT guys but I just want to understand more how others deal with his problem.
I am acutely aware how Catia does not like files simply moved around within windows.

Any insights would be greatly appreciated.

Thanks
thixoguy

 

[Azrael]

Sounds like you are working directly on remote files and if the infrastructure is not good enough then there will be problem. You can try using catias "send to" (file/send to/directory)option to move files.
The thing that amaze me most if why doesn't your company invest in a PDM system, say smarteam, it will do the same as you decribed, when you check out files from the vault it will store them loacally in a work directory until you check them back into the vault.

 

[DBezaire]

Thixoguy - use a directory structure, all parts and products exist from the parent down. Copy the entire Job.Folder to the local machine.

Tools - Options - General - Document. Change the search order to
Relative folder.
Folder of the pointed document
Folder of the link

Job#.folder
Main.Product
Sub.folder.components
Some catparts
Sub.folder.plates
More catparts and products
Sub.folder.mechanisms


Regards,
Derek

 

[thixoguy2]

Azrael,
Smarteam is not an option at this time,thanks anyway

DBezaire,
I don't quite follow your suggestion. I will look into it a bit more and then post some follw up questions.
Would what you are suggesting allow me to copy files to my system and then put them back to the network so they can be backed up? without screwing anything up?

thanks for your help, its been a while

thixoguy

 

[DBezaire]

Thixoguy, this would allow you to copy the files back to the server, but copy only the files that change. If you are not careful you could potentially overwrite another users work, but that still exists with your current method.
Changing the search order to Relative folder first instructs Catia to look at the directory of the product file (job####.folder\...) and then the sub folders for the files. If Catia can not find the files it will then look to method 2 - folder of the pointed document, which i believe is the hard path of the file (K:\data\job####.folder\...)

Regards,
Derek

 

[thixoguy2]

Hi DBezaire,

I have set up my "linked document localization" as you have suggested:
Relative folder
Folder of Pointed Document
Folder of the Link

I now have a few questions

1.In your first post you mentioned
Job#.folder
Main.Product
Sub.folder.components
Some catparts
Sub.folder.plates
More catparts and products
Sub.folder.mechanisms
Is this illustrating how files must now be organized?

2. Lets say I have a product comprised of a few sub-products and catparts already on the company server. How do I transfer the files to my PC? Do I use "send to" or copy/cut paste through windows? What is the proper procedure?

3. More impotantly how do I transfer the files back at the end of the day? Please explain

In the past I have played with moving files around. I have moved files to my desktop and then opened them but they still seem to link back to the original directories. Will the changes you are recommending to the "linked document localization" settings address this?

I apologize if my questions seem a little basic but I just want to make sure I understand. Thanks again for your valuable input

thixoguy

 

[jackk]

A few other suggestions to add to what's already been suggested:

1. Use Publications (Ext References & Asm Constraints)
2. Use Save Management

Both of these will help maintain good links when you start copying files around.

 

[ferdo]

Did you try to work with local cache - cgr files? Loading first time the assy will take a little time to create the cgr files but after that it will be much better...in this way you will not affect others job...maybe somebody use your files to create his own working environment...and switching to Design mode to work on your files its easy....

Anyway, I'm asking myself how do you deal managing your files (as company). Did you create a read only area where only few users have rights to write? Without a PDM system should be strictly rules to be followed...and this is time consuming for everybody because its much easier to manage files under a PDM system...

Keep in mind also UUID.

Regards
Fernando

 

[DBezaire]

Thixoguy -
1) You can have common files (Catalog parts) outside the directory structure. The folder of the linked document will find the files. Drive maps should be the same letter on all computers for that option to work. The directory structure simplifies what to copy, where to find files, offline jobs, revision control... Like Ferdo says, PDM eliminates the need for computer savvy designers. I have SmarTeam, just not installed and configured.
2/3) To transfer files, copy/paste in windows. Send to will change the links inside the file. Search Order of Relative folder allows me to do this. So at the start of the shift, operator copies the entire job folder to the desktop. works locally on Product structure. At this point you can have 2 people working on the assembly at 1 time. They must work on different parts and products from each other. At the end of their shift, copy back to the server only the files that they have modified - this is where your people must be computer savvy and knowledgeable with the assembly structure. I like to make a temporary backup copy before the end of day process. ( 2 minutes of copy vs 20 min restore time) Start up the server copy to verify the assembly. Delete the desktop copy, delete the 2 minute backup copy. Go home.

When you open your desktop copy - search order is pointing back to the server.
Your question is not basic but involves good file management and standards. As Jack says - publish linked and constraint items. I locked the options to force this as corporate standard.

Regards,
Derek

 

[thixoguy2]

jackk,
I use publications as well as save management. Thanks for your input

ferdo,
I am the only person who really needs access to the catia files on the server, there is really no reason that anyone else would need to access them. Thank you as well for your insights

DBezaire,

I am going to start experimenting with your suggestions with some test catparts and products, just to see how everything behaves.

I am curious though,why is it that I must copy back only the files that have changed? why not copy back everything?

Also, do you have any tips on how I can determine only the files that have changed?

As usual, I am indebted for all your help, thank you

thixoguy

 

[DBezaire]

Thixoguy - you can copy everything back if you are the only person working on it. I have a designer and surfacer working on large mold assemblies at the same time using this methodology. Time/date stamp in windows explorer detail list will indicate files changed that day. You could set up a batch file using xcopy to copy only files newer. The smallest item can change the file to changed - example a hide/show of a partbody. Just remember to always master the server copy at the end of the day.

Regards,
Derek

 

[thixoguy2]

DBezaire,
Thanks very much for all your help, it is greatly appreciated.

thixoguy