We’re importing CAD simulation results from ANSYS into Aras simulation data management, but the results aren’t correctly linking to their parent CAD models. The simulation files import successfully, but the relationships between simulation results and the source CAD parts are missing, causing complete loss of traceability.
When engineers search for a part’s simulation history, they get no results even though the simulation data exists in the system. We have to manually link each simulation result to its CAD part, which defeats the purpose of automated import. Our import mapping configuration looks correct on the surface, but something isn’t working. The CAD connector mapping rules seem to be ignoring the relationship definitions. Has anyone successfully automated simulation result linking in Aras?
Your simulation result linking failure is caused by incomplete configuration across three critical areas. Here’s how to resolve each:
Import Mapping Configuration:
Your simulation connector’s import mapping isn’t configured to create relationships automatically. You need to add explicit relationship mapping rules. In your connector configuration file, add a relationship mapping section:
First, ensure your mapping includes the relationship ItemType. The connector needs to know that when it imports a simulation result, it should also create a ‘CAD Part Simulation Result’ relationship. Add this to your import mapping:
- Source: Simulation file metadata field containing part reference (usually part_id or source_geometry)
- Target: CAD Part item in Aras
- Relationship: Create ‘Simulation Result’ relationship from Part to Simulation Data
- Matching Criteria: Part Number or CAD File Name
The connector likely has a basic mapping that only imports the simulation file as a Document item but doesn’t process the relationship metadata.
Manual Data Linking Workaround:
While you fix the automated import, you need to resolve your existing unlinked simulation results. Create a server method that:
- Queries all Simulation Data items without parent relationships
- Extracts the part identifier from the simulation file metadata or filename
- Searches for matching CAD Part items using that identifier
- Creates the relationship programmatically
- Logs any unmatched items for manual review
This will establish traceability for your existing data. Run this as a one-time cleanup script after fixing your import configuration.
CAD Connector Mapping Rules:
The root issue is that your CAD connector mapping rules don’t include the simulation relationship definition. You need to modify the connector’s relationship mapping configuration:
- Open your simulation connector configuration (usually an XML file)
- Locate the ItemType mapping section for Simulation Data
- Add a RelationshipMapping element that defines how to create the parent relationship
- Specify the source field in the simulation file that contains the part reference
- Define the query logic to find the matching CAD Part in Aras
- Set the relationship type to ‘CAD Part Simulation Result’
The connector probably has a default configuration that imports simulation files as standalone documents without processing embedded part references. You need to explicitly tell it to parse those references and create relationships.
Also verify that the Simulation Data ItemType has a relationship definition that allows it to be related to CAD Part items. Check ItemType definitions to ensure the relationship exists and has proper permissions.
After making these configuration changes, test with a small batch of simulation results before running a full import. Monitor the import logs to confirm relationships are being created successfully.
Check if your simulation connector is actually configured to import relationships or just the simulation file items themselves. Many connector configs only import the primary item and skip relationships by default.
Are you using the native Aras simulation connector or a custom integration? If it’s custom, the relationship creation logic might be missing entirely. Also check if the CAD Part ItemType has the correct relationship definition for simulation results.
The problem might be in how the simulation files reference the CAD parts. If the simulation result file uses a different part identifier than what Aras expects (like file path vs part number), the connector won’t be able to match them automatically. You need to configure a mapping rule that translates the simulation file’s part reference to an Aras part query.
We had this exact issue. The simulation connector was importing results as standalone items without creating the ‘Simulation Result’ relationship to the CAD Part. We had to modify the connector’s relationship mapping to explicitly create that relationship during import. It’s not automatic - you have to configure it.
Look at your import logs carefully. There might be errors during relationship creation that are being silently ignored. The import might appear successful but actually be failing to create relationships due to permission issues or missing required properties on the relationship ItemType.