Building & Civil Data Exchange Resources

A resource is a PLM object (for example, a catalog or a business rule) or another type of file (for example, a bitmap or a spreadsheet). In Data Setup, resources are grouped in resource sets. A resource set is a PLM object that implements a single resource table. This topic lists available resources in Building & Civil Data Exchange. These resources are used in export operations.

This page discusses:

Logical Name Resource Type Mandatory Criteria Description
Object Mapping Definition XML document*

available in win_b64\resources\standard\xcad\AECDataExchange.xml

 No –

Gives for each Building & Civil business object the corresponding neutral object to be used during export operation when it cannot be deduced from the applied extensions.

Gives for each IFC entity the corresponding neutral object to be used during the import operation.
IFC Custom Attribute Mapping Definition XML document*

available in win_b64\resources\standard\ifcCustomMapping\ifcCustomMapping.xml

 No – Defines the mapping between IFC custom attributes and ENOVIA attributes.
* These xml files from the directories indicated above are used when there are no files referenced in Data Setup.

AECDataExchange XML File Example 

<?xml version="1.0"?>
<AECDataExchange>
  <NeutralID Name="BUILDING">
    <IFC Name="IfcBuilding"/>
    <ENOVIA Name="Building"/>
  </NeutralID>
  <NeutralID Name="BRIDGE">
    <IFC Name="IfcBuilding" Priority="1">
      <Condition Attribute="ObjectType" Value="BRIDGE"/>
      <Valuate Attribute="ObjectType" Value="BRIDGE"/>
    </IFC>
    <ENOVIA Name="Bridge"/>
  </NeutralID>
  <NeutralID Name="BRIDGEABUTMENT">
    <IFC Name="IfcBuilding" Priority="1">
      <Condition Attribute="ObjectType" Value="BRIDGEABUTMENT"/>
      <Valuate Attribute="ObjectType" Value="BRIDGEABUTMENT"/>
    </IFC>
    <ENOVIA Name="BridgeAbutment"/>
  </NeutralID>
</AECDataExchange>

ifcCustomMapping XML File Example 

<?xml version="1.0" encoding="utf-8"?>
<IfcMapping>
<StandardMapping fromEntity="Dimension" fromProperty="Thickness" toEntity="Qto_BeamBaseQuantities" toProperty="Length" scope="AecBeam"/>
</IfcMapping>

The tables below describe elements and their possible attributes.

AECDataExchange.xml
ElementAttribute (s)Description
NeutralIDNameRepresents a business object independently of any format. It is used in a data exchange operation to map entities of a given format to entities of another format.
IFC

ENOVIA

Name
  • Name
  • Priority
Formats supported by Building & Civil Data Exchange (under a NeutralID node).
Priority Gives the priority order to evaluate the condition The highest priority is evaluated first. If this attribute is not specified, the default value is 0.
Valuate
  • Attribute
  • Value
A node that ensures the nature of an object is kept during export.
Condition
  • Attribute
  • Value
Allows you to assign a condition to an entity attribute to determine its nature regardless from any format.

For example, an IfcBuilding which ObjectType attribute is valuated to BRIDGE will be considered as a BRIDGE (NeutralID sense). However an IfcBuilding which ObjectType attribute is not valuated will be considered as a BUILDING.

ifcCustomMapping.xml
ElementAttribute (s)Description
StandardMapping
  • toProperty
  • fromProperty
  • toEntity
  • fromEntity
Describes the mapping between an Ifc attribute to an ENOVIA attribute for import and export operations.
toProperty Gives the name of an ENOVIA attribute.
fromPropertyGives the name of an IFC attribute.
fromEntityGives the name of an IFC entity.
toEntityGives the name of an ENOVIA extension.
scopeGives the type of ENOVIA objects that are targeted by the mapping operation.