In the era of Model-Based Definition (MBD), Product and Manufacturing Information (PMI) is no longer optional—it’s central to a truly connected Model-Based Enterprise (MBE). For PMI to deliver real value, it must be accurate, standards-compliant, and complete. That’s exactly where Elysium’s PMI Checker plays a key role—verifying PMI quality in accordance with ISO and ASME standards before engineering data moves downstream.
But even with validated PMI data, a key question remains: Is accurate translation enough?
Introducing Intelligence to PMI Translation
In 3D-SUITE EX11, Elysium introduces a powerful new enhancement: PMI Optimized Translation. This feature goes beyond conventional PMI translation, which has historically focused on transferring annotations as-is from one CAD system to another. While this ensures accurate translation, it doesn’t take full advantage of the capabilities available in modern CAD environments.
PMI Optimized Translation adds intelligence to the translation process, adapting PMI to better fit the features and semantics of the target CAD system—whether that’s a different system or a newer version of the same one.
Use Case 1: Modifier Translation Between Systems
Consider a case where a geometric modifier, like “SZ”, is represented only as plain text in the source CAD system. In the example shown in Picture 1, the modifier isn’t natively supported in Creo, so it’s treated as simple text. Under traditional translation, it would remain plain text in the target system.
However, when translating to a system like NX, which supports the “Modifier” entity in newer versions, PMI Optimized Translation automatically upgrades the plain text into a fully functional modifier. This results in more intelligent PMI, aligned with the capabilities of the target environment.
Picture 1: Modifier Upgrade Across CAD Systems:
In the source CAD (Creo), the “SZ” modifier is represented as plain text due to lack of native support. When translated to a newer version of NX with modifier entity support, Elysium’s PMI Optimized Translation upgrades it into a fully functional modifier, enhancing semantic fidelity.
Use Case 2: Intelligent Translation Within the Same CAD System
PMI Optimized Translation also brings value within the same CAD system—for example, between different versions of NX.
As illustrated in Picture 2:
- In NX 2212 or earlier, the “SZ” modifier is not supported, and thus exists only as text.
- In NX 2306 or later, “SZ” is fully supported as a structured modifier.
When upgrading from an older to a newer NX version, PMI Optimized Translation automatically converts the text-based modifier into a fully functional one. Similarly, when downgrading, the structured modifier is reverted to a text-based representation to maintain compatibility with the older version—ensuring semantic consistency in both directions.
Picture 2: Version-Aware Translation Within NX:
PMI Optimized Translation detects version-specific capabilities. When translating from NX 2212 (which lacks support for the “SZ” modifier) to NX 2306, the text-based modifier is upgraded to a structured modifier—and downgraded when going in reverse.
More Intelligent Translations in EX11
This smart adaptation is not limited to modifiers. Here are more examples introduced in 3D-SUITE EX11:
Interpreting Reference Dimensions
In some CAD systems, a dimension enclosed in parentheses implicitly signifies a reference dimension. EX11 recognizes this convention and translates it explicitly as a reference dimension in the target CAD system—turning implicit visual hints into explicit functional semantics.
Picture 3: Reference Dimension Recognition:
A dimension enclosed in parentheses is implicitly treated as a reference dimension in the source CAD. PMI Optimized Translation interprets this convention and explicitly maps it as a reference dimension in the target CAD system.
Converting Common Datum from Text to Entity
In another case, a common datum might be defined as plain text in the source system. EX11 intelligently maps this to a formal common datum entity in the target CAD system, in alignment with its definition methodology. This ensures proper downstream interpretation by both humans and software.
Picture 4 : Common Datum Transformation:
In the source CAD, a common datum is represented as plain text. Through PMI Optimized Translation, it is intelligently converted into a proper common datum entity that aligns with the target system’s definition method.
Why This Matters
With PMI Optimized Translation, Elysium delivers a smarter, context-aware approach to CAD interoperability. By recognizing not just what PMI is, but how it is interpreted and supported in each system, this feature:
- Reduces manual cleanup and rework
- Improves semantic fidelity
- Enhances automation potential
- Ensures consistency across multi-CAD and versioned environments
Conclusion
PMI Optimized Translation in Elysium 3D-SUITE EX11 redefines PMI as a context-aware, intelligent bridge between CAD systems—no longer limited to basic data transfer. By optimizing PMI during translation—whether across CAD platforms or within versioned upgrades—EX11 ensures better alignment with downstream systems and workflows.