Start with the export scope
Record the CAD release, translator licence, AP242 edition and whether the export includes parts, assemblies and annotations. Select the required semantic and graphical content where supported. The presence of an AP242 option does not prove that every annotation is transferred.
SOLIDWORKS
The 2026 help documents the Publish to STEP242 PropertyManager for parts and assemblies. Check the licence and publishing options in the installed release. After export, inspect the characteristic inventory as well as the visible annotation views; do not use an ordinary shape-only STEP export as evidence of PMI transfer.
NX
Siemens lists STEP AP242 translation in its NX add-on documentation. Confirm that the required translator is available, then review the application protocol and PMI export choices for your release. Export a small representative part first. Verify semantic content separately from geometry and annotation appearance.
Creo
Review the STEP application protocol and annotation settings in the export profile. PTC documents both graphical and semantic annotation behaviour and release-specific limitations. Its Creo 12 documentation also identifies restrictions on assembly-level AP242 annotations. Check the part and assembly cases separately instead of applying one successful test to both.
CATIA
Dassault Systèmes documents AP242 support, but the cited overview is historical rather than a current settings manual. Confirm the installed release’s protocol, annotation mode and licensing in its help. Where available, request semantic representation as well as graphical presentation. This guide does not claim a verified universal CATIA menu sequence.
Verify the exported file
Reopen the export with an independent inspection tool. Check one dimension, one datum relationship and one geometric control against the source. Record any missing or graphical-only requirement before comparing revisions in PartDatum. These checks establish the tested example’s scope, not general exporter certification.