To illustrate how custom and default mapping files work together, we can use an example case in PDMS data with a source class called STRU, which can represent a ladder, a beam, a wall, and so forth. We map this source class to the CR3DGenericStructure class in the PDMS default mapping file. In your custom mapping file, STRU is mapped to CR3DMemberPart, which is listed in SPIOPSchema.xlsx.
Custom mapping (CustomPDMSToR3DMapping.xls):
Source Class |
Target Class |
STRU |
CR3DMemberPart |
Default mapping (PDMSToR3DMapping.xls):
Source Class |
Target Class |
STRU |
CR3DGenericStructure |
STRU has properties A, B, C, and D.
Custom mapping:
Source Property |
Target Interface |
Target Property |
A |
IJR3DDimensionData |
Length |
B |
IJR3DDimensionData |
Height |
Default mapping:
Source Property |
Target Interface |
Target Property |
C |
IJNamedItem |
Name |
When the resulting PDMS Smart Model is translated with the above mapping files, the properties display in the two classes.
Length |
Mapped property from custom |
Height |
Mapped property from custom |
Name |
Mapped property from default |
D |
Unmapped property |