UDMToAP242ContentDefinitions Configuration

The <UDMToAP242ContentDefinitions> section defines how Altair UDM content types are mapped to AP242 categories and formats during XML transformation. This ensures compatibility when exporting UDM content into AP242-compliant XML structures.

Purpose

The purpose of the <UDMToAP242ContentDefinitions> section is to:
  • Convert UDM content definitions into standardized AP242 file types for downstream interoperability.
  • Ensure correct categorization of representation and file formats when transitioning to AP242.

Structure Overview

Each <UDMToAP242ContentDefinition> block maps a single UDM representation and file type to its corresponding AP242 values.
Table 1.
Element Description
UDMRepresentationCDef UDM content definition for the representation object
UDMFileCDef UDM content definition for the file object
UDMFileType Logical file type within the UDM context (for example, HyperMesh, CATIA V5)
UDMFileExtension Expected file extension used in the UDM model (for example, .hm, .CATProduct)
AP242FileType Standard AP242 representation type (for example, geometry, FE data)
AP242FormatProperty Format identifier used in the AP242 representation.format property

Example Configuration

Table 2. Usecases
UDM Format Maps to AP242 Purpose
HyperMesh (.hm) FE data, HYPERMESH FEA mesh data
CATIA V5 (.CATProduct) geometry, CATIA V5 CAD geometry assembly

Best Practices

  • Ensure that each UDM file type and extension matches the actual exported data.
  • Use AP242-standard terminology for AP242FileType and AP242FormatProperty to remain compliant.
  • Validate your mappings against your target system’s import capabilities for AP242 files.