The POD to XMpLant mapping file is mandatory to the export process. Although a sample mapping file is delivered by default to the local machine during setup, it is only intended as a starting point and should be customized to meet your project requirements.
The file consists of two mapping sections: one for component data, and one for attribute data. The Component mapping section consists of the following three sub-sections:
Component-Component maps POD components to XMpLant components. The COMPONENT-COMPONENT sub-section contains all the POD component names that are available. Each POD component name is mapped to an XMpLant component name, as shown in the following line from the SmartPlant Isometrics sample POD to XMpLantP mapping file:
<COMPONENT Value="Ball-Valve" XMPValue="BallValve" />
In this example, COMPONENT Value defines the POD component name, and XMPValue defines the corresponding XMpLant component name.
The XMpLant component name is obtained from the NewValue definition in the Smart 3D-supplied class mapping file, Map_XMpLant_SP3D_Class.xml.
<Attribute Value="Ball Valve" NewValue="BallValve" />
The mapping file is delivered to C:\Program Files\SmartPlant\3D\Translators\ConfigurationFiles\XMpLantSP3DMaps\Piping by default when you install the Smart 3D software.
Those components that have a clear one-to-one map between the POD file and Smart 3D are mapped in the delivered POD to XMpLant sample mapping file. Components that do not have a clear one-to-one map require that you modify the mapping file accordingly using the appropriate Smart 3D value.
SKEY-Component maps components with a specific SKEY to an XMpLant component. In the following example, SKEY Value defines the SKEY to be mapped to the XMpLant component, BallValve, as defined by XMPValue.
<SKEY Value="ABCD" XMPValue="BallValve" />
ItemCode-Component maps components with a specific item code to an XMpLant component. In the following example, ITEMCODEValue defines the item code to be mapped to the XMpLant component, BallValve, as defined by XMPValue.
<ITEMCODE Value="IC1" XMPValue="BallValve" />
For the SKEY and ItemCode maps, only the example syntax is supplied. You will need to modify the map according to your specific project requirements.
During the export of data, the Component map is searched in the following order: ItemCode, SKEY, and Component.
Immediately following the Component mapping section is the Attribute mapping section, which consists of the following two sub-sections:
Pipeline-Attributes maps pipeline attributes to an XMpLant segment attribute.
Component-Attributes maps component attributes to an XMpLant component attribute.
Even though the output generated during export conforms to the XMpLant specification, a customized map is potentially required for each system that will be importing the XMpLant file. The Smart 3D class mapping file, while fairly comprehensive, is by no means complete; as such, it may be necessary to add extra entries to it. In the following example, the NewValue definition adds a new XMpLant component, Comp1, to the Smart 3D class mapping file:
<Attribute Value="SP3DComp1" NewValue="Comp1" />
When you define a component in the Smart 3D class mapping file, you must also add attribute information for that component to the Smart 3D attribute mapping file, AdditionalAttributesMap.xml. The following lines of example code, define five attributes for the new component defined in the previous example:
<Attribute Value=" SP3DComp1">
<NewAttribute Name="GeometryType" Value="1" />
<NewAttribute Name="IsSpecificallyPlaced" Value="1" />
<NewAttribute Name="SP3DGeometryType" Value="15" />
<NewAttribute Name="IsRotationApplicable" Value="1" />
<NewAttribute Name="PortNumber" Value="0" />
You can obtain the values for each of these options, including any others that may be necessary, using Smart 3D catalog information.
Depending on units, it may be necessary to add/modify some entries in the SP3D XMpLantPipingTranslator.ini file. For more information, see the appropriate Smart 3D documentation.