|
This section illustrates how to exchange only
the documents which have been modified since the previous exchange. We
recommend this data exchange method for optimizing all exchanges (bandwith
optimization).
The methodology for extracting only a subset of data from SmarTeam consists
in:
- opening documents in CATIA
- launching the Send To functionality
- defining only the documents which need to be extracted.
The extraction methodology is equivalent to the one used for I.P.
protection. For more information, see Exporting
Data.
In the following example, as a supplier you need to re-integrate
documents which have been modified since the last exchange with your OEM.
In this scenario, we assume that not all the documents were sent back to
you. |
|
-
Open the assembly sent by the OEM.
This assembly constitutes a skateboard. As the wheel has
not been sent by the OEM, CATIA displays a broken link in the
specification tree.
-
Click Launch Reconciliation
.
In the Reconcile Window, the CATIA 3D View is empty as the
wheel is not present in the CATIA session.
-
Perform the necessary query
for the documents.
Note that in case you are handling a document stored in ENOVIA, as the
part number is not known by the CATIA session, you must use
Interactive-Latest available revision to identify the appropriate
SmarTeam document.
-
To set a reconciliation rule for the missing wheel, you
need to choose between two possible rules which are Reload
and Keep as External
.
When applying the Reload rule, the SmarTeam object is kept.
The Keep as External rule allows you to keep temporary the
broken link in the CATIA session so that
next time you will open the assembly from SmarTeam, the wheel will be
found.
You decide to reload the wheel from SmarTeam.
Once the reconciliation is done, the wheel is reloaded.
The transfer of incomplete data has not affected the CATIA consistency of
your data.
ENOVIA Data
In case of a broken link to a CATPart or CATProduct inside a CATProduct,
the Part Number of the missing file is not known. If the document comes
from ENOVIA, the file name is not stable (due to ENOVIA revision mechanism)
and cannot be used for the identification phase. As there is no accessible
information allowing you to identify the missing part or product, you must
perform an interactive query. |