NX Data Management before Teamcenter is Deployed

[BOPdesigner]

Do any of you have some recommended best practices for managing NX data (versions and revisions) without Teamcenter? We do have a document management system, but it is meant for MS Office types of product data.

 

[potrero]

One method is to use Subversion coupled with an SVN client, such as Tortoise SVN.

You basically set up a Repository (can be on a local machine, but most usefully, on the network) which will hold the NX data.

Tortoise SVN (

http://tortoisesvn.tigris.org/)

integrates into the Windows shell (x32 and x64) so that you can Update changed files from or Commit changes to the Repository with a right-click from your local folder copy.

A good, and fast (and simple, painless, etc) way to get going on the Repository side is VisualSVN (

http://www.visualsvn.com/

).

SVN lacks a lot of the nice tools of real PDM systems but it's a good tool if you need at least SOMETHING to:

- handle version control
- provide a shared Repository of part files that multiple people can check out and use

Oh, and it's free.

 

[potrero]

Hmm, I probably should have been more clear about VisualSVN... the SVN server product is actually "VisualSVN Server"; you can read about it at:

http://www.visualsvn.com/server/