Supported CAD Applications, Versions, and Formats¶
aP Pro can cost parts and assemblies from several CAD formats. Customers across a broad range of industries can use MCAD integration regardless of their CAD or PLM systems.
Info:
To learn more about the licensing option that allows users to open CAD models directly to aP Pro or to inquire about integrating with CAD applications that are note currently supported, contact aPriori Customer Support.
aPriori certifies the CAD applications and versions in the following table, subject to these limitations:
-
aPriori can also read CAD files saved in older versions of these CAD applications but does not regularly test older versions. aPriori reserves the right to not address issues which are apparent only in older unsupported CAD versions.
-
aPriori also can be used in environments where the MCAD application is integrated with a PLM system
- aPriori commits to testing and certifying only the most recent three versions of each CAD application.
- aPriori reserves the right to discontinue official support for CAD EOL (end-of-life) versions.
aPriori offers plug-ins for all supported versions of the native CAD systems Creo, CATIA, Inventor, NX, SolidWorks, and SolidEdge, unless otherwise noted in the Notes column.
| Application or File Exchange Format | Version |
Notes |
|---|---|---|
| Creo® Elements/ Parametric |
- 9.0* - 10.0 - 11.0 - 12.0 |
For all versions, for MCAD integration,Creo®Elements/Direct Modeling is not currently supported. In future releases, aPriori will phase out support for Creo versions that have reached End of Life (EOL). A plugin for Creo is provided by aP Design only. aP Pro does not provide one. * If a component that includes a GD&T annotation was created and last saved in a version ofCreo®that is older thanCreo®9, save the model inCreo®9 before opening it via aCreo®direct integration with aP Pro. If the GD&T annotation was not extracted, in the PTC knowledgebase, see How to convert legacy datums and annotations in Creo. For troubleshooting purposes, generates a warning message in the aPriori log file when it detects a legacy annotation in a Creo CAD for production and manufacturing information (PMI). |
| CATIA™ V5 | - V5-6R2023 (R33) - V5-6R2024 (R34) - V5-6R2025 (R35) - V5-6R2026 (R36) |
|
| SOLIDWORKS™ | - 2023 - 2024 - 2025 - 2026 |
aPriori does not generally support Bulk Costing or Deep Costing forSOLIDWORKS™. For more information, contact aPriori Customer Support. |
| NX™ | - 2312 series - 2406 series - 2412 series - 2506 series - 2512 series |
|
| Solid Edge® | - 2023 - 2024 - 2025 - 2026 |
|
| Inventor™ | - 2023 - 2024 - 2025 - 2026 |
|
| JT | - 10.4 - 10.5 - 10.6 - 10.7 |
aPriori supports costing only for JT files that use XT-BREP boundary representation, not the older JT-BREP. aPriori supports only the JT little-endian file format, which is exported from most CAD systems, not the big-endian format. aPriori does not support semantic PMI in JT files. |
| STEP | - AP203 - AP214 - AP242 |
aPriori supports reading semantic PMI from STEP files generated by recent versions of NX, CATIA, SolidWorks, and Inventor. |
| Parasolid | 10.0 - 38.0 | |
| ACIS | R19-R27 | |
| ODB++ | - 7 - 8 |
Supported file formats are: - *.zip - *.tgz - *.tar |
| Gerber | RS-274X | Gerber files must be compressed to a zip file. Gerber files are supported only if they are exported from one of these PCB design applications: - Siemens PADS - Cadence Allegro - Altium Designer - CADSTAR - Eagle - PentaLogix - P-CAD Only these PCB.NC drill formats are supported: - Exellon - Indefinite NC |