I used to use a command to extract specs and library data files from models using a particular command in 2010. Once I ran the command within a model, all specs and data files would be extracted into a zip file. This was an easy way for me to provide my model and the specific data files and specs that were used within my model to a client.

Does anyone know what this command is and if this command can be used in 2013?

I found my answer in an old 2012 email:

Open each individual model in CADWorx Plant & run the CADWorx command GETALLSPECDATAFILES. This command will copy all specifications and data files used in the model into sub-directories under where the model drawing file is located. Zip the contents of these directories & name the zip files according to the model names.

Don't think that works any more? Even though it's still in the help file. I thought I had asked Himanshu about that but I cant find the email:-(
When I try it all I get is !!SPEC MISSING: W:\Cadworx\Spec\1B1.spc
As far as I'm aware Cadworx doesn't even use spc files any more?
I'm running Cadworx 2015 by the way, but I think 2013 uses the same new file system.
Cheers
Russell

In my tests, I found the same results.

Too bad, that is a great command

Thanks guys. After trying it several times I've realized that the command doesn't work. I wish they would have upgraded the command when they upgraded the specs in 2013...

So if the GETALLSPECDATAFILES command doesn't work anymore, is there a way to extract all project spec data to create a catalog?

I need to find a way to provide a client with the CADWorx specs & catalog data that we used specific to their project without compromising our global catalog.

I *think* you can just provide the PRJ file without a catalog. They won't be able to make any changes to the PRJ contents (since they don't have the catalog), which can be a problem - everyone has their own instruments, supports, and the like and they have to be added to the catalog.

Or, use the catalog inheritance system to create a catalog for that client and build the PRJ off that catalog.

Correct, you can just hand off the PRJ file without the catalog. I actually wish that there was an "edit lock" option on it as well, to protect the integrity when handing the project specs over to a third party.

If you provide the PRJ file without the matching catalog file that it was built from, you are "locking" the file to some extent. While it is possible to still edit the PRJ file for some things, the users cannot add new content to it or modify geometry within it (unless they are willing to crack the file open in a text editor and hack it that way).