Reconciling ENOVIA Data with SmarTeam Documents

Prior to reconciling ENOVIA Data with SmarTeam documents, you must have customized your environment as explained in Customizing your Environment for Reconciling ENOVIA Data.

Concepts

Prior to reconciling ENOVIA data using the ENOVIA SmarTeam - CATIA Supply Chain Engineering Exchange application, you should be familiar with two concepts: Publication Exposed documents and Structured Exposed documents.

Publication Exposed

Used by ENOVIA, this term applies to all document type (CATDrawing, CATPart, CATProduct etc.). The CATIA document information is stored as a document (same as in SmarTeam). For instance, a "Publication Exposed" product will be stored as a CATProduct file in the vault.

As a reminder, SmarTeam - CATIA Integration (CAI) stores CATIA documents as "documents". Therefore, although we do not use the "Publication Exposed" terminology, we can consider that CATIA documents are "publication exposed".

Structure Exposed

Used by ENOVIA V5 VPM, this term applies to product information (CATProduct documents). The product structure information is stored thru database objects and no CATProduct document is stored in the vault. In that case, structure exposed CATProduct documents proceeding from an Open operation in CATIA can be seen as temporary CATIA formats.

In the example below, Skateboard.CATProduct and Board.CATProduct are structure exposed documents.

Extracting Data

When extracting "publication exposed" data coming from ENOVIA, the extraction consists in loading the data from the vault and saving it on the local disk. The document file name is not guaranteed due to file naming conventions based on the document revision.

When opening "structured exposed" data in CATIA, a temporary CATProduct is created. Its internal CATIA identifier is also temporary (it is created during the ENOVIA>CATIA operation).

Reconciling Data Stored in ENOVIA

Documents Stored as "Publication Exposed"

The file name of the document by default incorporates some ENOVIA naming conventions (the document revision value included). It is necessary to use the Part Number as a query criteria (and not the file name). For more information, see Customizing Queries.

Documents Stored as "Structured Exposed"

We recommend you use the Part Number as a query criteria. The CATIA internal identifier (UUID) is not a stable information across various engineering exchanges. This is the reason why such documents cannot override other versions of documents stored in SmarTeam 'different internal identifiers. The application therefore proposes to the end-user either to create a new object or to reload another object from the database.

In the example below, the supplier incorporates all the modifications made by the OEM. He has applied the Overwrite rule to all documents except for the skateboard and the board which proceed from a Structure exposed extraction. For both of these documents, he has applied the New rule .

Methodology To keep the history of the different versions of a product ENOVIA documents, you need to create a fake product. For more information, see Reconciling ENOVIA Data Saved in Structured Exposed Mode.