Assembly With Representation

Representations can be created in an XPDMXML file using the Representation3D, Rep3DAggr, Drawing and DrawingAggr elements. Files are associated to representations using the FileRef and File elements.

The FileRef and File elements can also be associated to a Product element. For more information refer, About Assembly With CATProduct.

The Representation3D, Rep3DAggr, Drawing and DrawingAggr elements must have one and only one FileRef. In the following example a single file Part1.CATPart is associated to representation RefRep1 under product Ref1:

<ProductStructure rootRefs="ID_0" updateChildMode="RemoveExistingNotProvided”>
<Product id="ID_0">
  <ID>Ref1</ID> 
…..
</Product>
<Rep3DAggr id="ID_1">
  <ID>RefRep1</ID> 
  <Description /> 
  <Name /> 
  <UniqueID External="XPDM_Authored"/>
…..
  <Owned>ID_0</Owned> 
  <FileRef>ID_2</FileRef> 
</Rep3DAggr>
</ProductStructure>
<File id="ID_2">
  <Name>Part1.CATPart</Name> 
  <Location>Part1.CATPart</Location> 
  <Format>CATPart</Format> 
</File>

The behavior incase an X-PDM owned representation with reference comes in XPDMXML at import is as following:

• If representation does not exist in 3DEXPERIENCE platform, a new representation is created under the reference.
• If representation exists in database and:
  • If XPDMXML has P1-Rep1, which is also in 3DEXPERIENCE platform, the attributes of the existing representation are updated.
  • If XPDMXML has P1-Rep1 but in 3DEXPERIENCE platform we have P1-Rep2, a new RepInstance (P1-Rep1) is created and the existing RepInstance (P1-Rep2) is removed. The Rep2 is not deleted from database.
  • If XPDMXML has P1 but no RepInstance below it and 3DEXPERIENCE platform has P1-Rep1, the existing RepInstance (P1-Rep1) is removed. The Rep1 is not deleted from database.

In the XPDMXML file, for the format declared as STEP, X-PDM to3DEXPERIENCE platform transfer creates corresponding V6 representation including the minimum result geometry (only visible geometry).

<File id="ID_2">
<Name>RefRep_1_7d467b25_106c_4d80c5ca_2821a.stp</Name>
<Location>RefRep_1_7d467b25_106c_4d80c5ca_2821a.stp</Location>
<Format>STEP</Format>
</File>

The XPDMXML file sent by X-PDM adapter can reference CATProduct, CATPart and CATDrawing documents from CATIA V5.

Such documents can contain links referencing other documents. For example, the following categories of links are maintained when a CATPart document is imported in 3DEXPERIENCE platform:

Links in V5	Links in V6
Publications Links
Publication of geometrical elements:	Publication of geometrical elements:
Publication of parameters:	Publication of parameters: they are migrated in V6 only if they belong to a CATPart.
Reference Links
Reference Links of geometrical elements	Reference Links of geometrical elements
Reference Links of a Publication	Reference Links of geometrical elements

To maintain links between two CATIA V5 documents :

• both documents must be imported simultaneously.
• both documents must come from CATIA files, not from ENOVIA V5 VPM or ENOVIAvpm.
• the <Location> tag must contain the name of the referenced document when the link was saved in CATIA V5.

• the <Name> tag must have the same value as the <Location> tag.

The XPDMXML file sent by X-PDM adapter can reference CATDrawing files from CATIA V5, they must be associated to a Drawing or DrawingAggr element.

The CATDrawing of a CATPart and CATDrawing of a CATProduct can be exchanged.

In the following example a single file Drawing1.CATPart is associated to Aggregated Representation DrawAggr:

<DrawingAggr id="ID_4">
  <ID>DrawAggr</ID>
  <Description>aggregated Drawing</Description>
…
  <FileRef>ID_5</FileRef>
</DrawingAggr>
<File id="ID_5">
  <Name>Drawing1.CATDrawing</Name> 
  <Location>Drawing1.CATDrawing</Location> 
  <Format>CATDrawing</Format>
</File>

The CATProduct files can be referenced in an XPDMXML file using the FileRef and Product elements. They are not attached to a representation.

<Product id="LOCALID_2">
      <ID>Ref XPDMXML CATPRODUCT</ID>
      <UniqueID External="1888B22E89E7C5200B0B25B3584C57270B0D68F6"/>
…..
      <FileRef>LOCALID_5</FileRef>
    </Product>

The files with CATProduct format can contain references to CATProduct, CATPart, CATDrawing and CGR documents from CATIA V5, and references to model documents from CATIA V4.

• CATPart documents must be associated to a Representation3D or a Rep3DAggr element
• CATDrawing documents must be associated to a Drawing or a DrawingAggr element
• CGR and model documents must be associated to a Representation3D element to maintain the link from CATProduct to CGR or model. They must not be associated to a Rep3DAggr element.

In the following example a file Part1.CATPart is referenced in File Product1.CATProduct:

<ProductStructure>
	<Product id="LOCALID_20">
      <ID>Ref xpdmxml CATPart</ID>
      <UniqueID External="1888B22E89E7C5200B0B22E3584CBBC60B0D0892"/>
…..
    </Product>
	<Rep3DAggr id="LOCALID_22">
      <ID>Rep CATPART xpdmxml</ID>
      <UniqueID External="1888B22E89E7C5200B0B25B3584C57270B0D78AA"/>
…..
	  <Owned>LOCALID_20</Owned>
      <FileRef>LOCALID_21</FileRef>
    </Rep3DAggr>
	<Product id="LOCALID_2">
      <ID>Ref xPDMXML CATPRODUCT</ID>
      <UniqueID External="1888B22E89E7C5200B0B25B3584C57270B0D68F6"/>
…..
      <FileRef>LOCALID_5</FileRef>
    </Product>
  </ProductStructure>
  <File id="LOCALID_5">
    <Name>Product1.CATProduct</Name>
    <Location>Product1.CATProduct</Location>
    <Format>CATProduct</Format>
  </File>
  <File id="LOCALID_21">
    <Name>Part1.CATPart</Name>
    <Location>Part1.CATPart</Location>
    <Format>CATPart</Format>
  </File>

A File with CATProduct format contains an assembly made of the following:

• A root node
• Internal components
• Nodes from other files (CATProduct or CATPart)
  
  

When importing a File with CATProduct format the information about the root nodes from CATProduct and CATPart is extracted from XPDMXML, overriding their information imbedded in the V5 file.

The behavior is different for internal components and their instances:

• These objects are not governed by XPDMXML but by the V5 CATProduct only.
• The modifications done in 3DEXPERIENCE platform on these objects are overwritten when CATProduct is imported.
• When a CATProduct aggregates external objects like CATPart or CATProduct and if one of those objects is missing the instance is not created and a warning appears in the Transfer Report.

Mapping of V5 internal component's attributes:

• Some attributes are set without any openness.

  For example:

  The version name is automatically generated, the maturity is set to the first state of the 3DEXPERIENCE platform maturity graph.

• Project, Responsible, and Organization are directly propagated from the CATProduct root node, in 3DEXPERIENCE platform. In this case values come from the Product node with FileRef.
• Finally for attributes defined as public (visibility) and user or free (protection) in the 3DEXPERIENCE platform data model, a default mapping exists and can be customized through BL.

XPDMXML structure vs CATProduct structure:

The structure created in 3DEXPERIENCE platform after V5 CATProduct import can also be created with XPDMXML import, hence to avoid conflicts the following behavior is enforced on import of Product node with Fileref:

• Duplication of structure below this node is forbidden and especially duplication of RepInstances fails.
• Instances below this node in XPDMXML are ignored during import