3D viewer fails to load external CAD files after integration with PDM system

We integrated our Aras 12.0 instance with an external PDM system to access legacy CAD files. The integration connector successfully retrieves the files and creates references in Aras, but when trying to view these external CAD files in the Aras 3D viewer, we get loading failures. Native Aras CAD files work fine in the viewer.

The error messages are vague - just “Failed to load model” with no specific codec or format information. We’re working with mixed CAD formats (STEP, IGES, Parasolid) coming from the PDM system. It seems like the viewer isn’t properly handling the external file formats or there’s a conversion step missing. Design reviews are completely blocked because engineers can’t visualize the legacy components. Has anyone successfully configured the 3D viewer to work with external CAD files from PDM integration?

I’ll provide a complete solution addressing CAD file conversion, PDM connector configuration, and viewer codec support.

Root Cause Analysis: The Aras 3D viewer doesn’t work with raw CAD files - it requires processed viewer data (tessellated geometry, metadata, structure). When your PDM connector retrieves external CAD files, they’re being stored as generic file attachments without triggering the necessary CAD processing pipeline.

Solution Part 1: CAD File Conversion Configuration

Verify and configure the CAD conversion service:

  1. Check Conversion Task Queue: Navigate to Administration > Conversion Tasks in Aras. Look for failed or pending tasks related to your external CAD files. The logs here will show specific conversion errors.

  2. Enable CAD Processing for External Files: Modify your PDM connector to trigger CAD import workflow when retrieving files. The connector should:

    • Create proper CAD Document items (not just File attachments)
    • Set the appropriate CAD file type classification
    • Trigger the CAD import agent to process the file
  3. Review Conversion Logs: Check [InstallDir]\Innovator\Server\Logs\CADConversion for detailed error messages. Common issues include:

    • Missing translator components
    • Unsupported CAD format versions
    • Insufficient permissions on conversion server
    • Memory/resource limitations during tessellation

Solution Part 2: PDM Connector Configuration

Update your connector’s post-retrieval workflow:


1. File Retrieved from PDM
2. Create CAD Document item (not generic File)
3. Set file_type property to appropriate CAD format
4. Apply CAD Import method
5. Queue for viewer conversion
6. Update relationships (Part-CAD Document)

The key is ensuring external files follow the same processing path as native Aras CAD files. Your connector needs to invoke the CAD Import Server service after file retrieval.

Solution Part 3: Viewer Codec Support Verification

Validate codec availability for your formats:

  1. STEP Files (.stp, .step): Requires STEP translator license. Check Administration > Licenses to verify STEP import is licensed. STEP AP203 and AP214 are most common - ensure your files match supported versions.

  2. IGES Files (.igs, .iges): Usually included in base CAD import license. Verify IGES version compatibility (5.3 is standard).

  3. Parasolid (.x_t, .x_b): Requires specific Parasolid translator license. This is often a separate license component - verify it’s installed and activated.

  4. Codec Testing: Create a simple test by manually importing one external file through Aras’s standard CAD import interface (not through the PDM connector). If this works, the issue is connector configuration. If this fails, it’s a codec/license issue.

Solution Part 4: Implementation Steps

  1. Immediate Workaround: For already-retrieved files that aren’t displaying, manually trigger CAD import:

    • Open the CAD Document item
    • Run the “Import from File” action
    • Monitor conversion task completion
    • Refresh viewer
  2. Permanent Fix: Modify PDM connector workflow:

    • Add CAD document creation step
    • Configure automatic CAD import triggering
    • Set up conversion monitoring
    • Implement retry logic for failed conversions
  3. Validation Process:

    • Test with each CAD format individually
    • Verify conversion tasks complete successfully
    • Confirm viewer data (PVZ files) are generated
    • Test viewer loading for each format

Solution Part 5: Performance Optimization

For large volumes of external CAD files:

  • Configure batch conversion processing
  • Allocate sufficient resources to CAD conversion server
  • Implement conversion priority rules (critical files first)
  • Set up monitoring alerts for conversion failures

Troubleshooting Decision Tree:

  • Viewer fails → Check conversion task status
  • Conversion fails → Review codec/license availability
  • Conversion succeeds but viewer fails → Check viewer data file generation
  • All succeeds but specific formats fail → Verify format version compatibility

This comprehensive approach ensures external CAD files from your PDM integration go through proper Aras CAD processing, generating all necessary viewer data for successful 3D visualization.


This draft is based on general Aras Innovator knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.

The Aras 3D viewer requires files in specific formats - typically it works best with native Aras-processed CAD data that’s been through the CAD import process. External files might not have the necessary tessellation data or viewer metadata. Check if your PDM integration is just copying raw CAD files or if it’s supposed to trigger Aras’s CAD processing pipeline.

Look at the CAD file conversion logs in Aras. When external CAD files are brought in, they should go through Aras’s conversion service to generate viewer-compatible formats (typically PVZ or similar). If the conversion is failing or not happening at all, the viewer won’t be able to display anything. The logs will show exactly which conversion step is failing and why. Check the Conversion Task items in Aras to see the status.

Your PDM connector configuration needs to include CAD processing triggers. When files are retrieved from the external PDM, they should automatically queue for Aras CAD import and conversion. Without this, you’re just getting raw CAD files without the necessary viewer data structures. Review your connector’s post-retrieval actions to ensure CAD processing is enabled. Also verify that the necessary CAD translators are installed and licensed in your Aras environment.

Confirmed this resolves the blank viewer issue — configuring the CAD conversion service to trigger on PDM-sourced file check-ins properly queued tessellation jobs in Aras 11 SP15.

Check the codec support in your Aras installation. Not all CAD formats are supported out of the box - you need specific translator licenses for formats like Parasolid or certain STEP variants. The viewer might be failing because the underlying CAD translator isn’t available or properly configured. Review your Aras license to confirm which CAD formats are included.

We had similar issues when integrating with our legacy PDM. The problem was that the external files weren’t being registered properly in Aras’s CAD document structure. The viewer needs specific metadata and relationships that only get created when files go through proper CAD import, not just file attachment. You might need to implement a custom import process for these external files that mimics the native CAD import workflow.