Transferring CATIA V5 Catalogs from ENOVIAvpm to 3DEXPERIENCE

To illustrate the relationship between different CATIA V5 objects in the catalog browser, let's take an example of a CATIA V5 catalog stored in ENOVIAvpm:

The catalog shown above has two chapters: "Fitting" and "Tubes". As you can see, each of these chapters has one family, the Fitting chapter has a family named "TestNut" and the Tubes chapter has another chapter named "Tube with bends" which has a subfamily named "TestPipe". Each of these families has 1 through n references:

When you select File > Desk, the view looks like this:

The catalog document points to n number of CATParts where n is equal to the number of families in the catalog.

Each CATPart points to a Design Table for the parameters to be used by these references for CATPart regeneration:

The Document Revision with the catalog file to be transferred will include:

• the pointed generic Parts (the TestNut and TestPipe CATParts in the example above)
• the Design Table documents pointed to by the generic Parts
• the catalog file with the respective chapters, families and items created.

A document-to-document link is mapped from ENOVIAvpm:

to 3DEXPERIENCE:

If you open and expand the catalog that has been created in 3DEXPERIENCE, you should see this:

Important: Catalogs are transferred to 3DEXPERIENCE as a VPMRepReference. Catalogs are exploded using the VPM catalog modeler and the corresponding objects are created in 3DEXPERIENCE. All of the standard Parts pointed to by the catalog are also transferred. The attributes of objects exploded in the catalog modeler cannot be customized using the PLMAttributesMapping opening.