Best practices for CAD integration workflow in Aras 12.0

PLM Aras Innovator
, , , , , , , ,
1

Our team is implementing CAD integration workflows in Aras 12.0 and I’m looking for community insights on best practices. We’re connecting SolidWorks and Creo to Aras, and need to establish solid workflows for check-in, revision control, and design change propagation.

Specifically interested in hearing about:

  • How you handle integration points between CAD systems and Aras workflows
  • Version control strategies when CAD files are updated frequently
  • Documentation practices for maintaining integration configurations

We’ve set up basic CAD import workflows, but I’m concerned about scalability and maintainability as our design team grows. What workflow patterns have worked well for others managing multiple CAD systems? Any pitfalls to avoid in 12.0 specifically?

<Item type="CAD" action="update">
  <check_in_workflow>Standard CAD Review</check_in_workflow>
</Item>

Would appreciate any lessons learned from production deployments.

system 2

CAD Integration Architecture in Aras 12.0 — SolidWorks & Creo

Both ACAD Connector (SolidWorks) and Creo Connector ship as separate installables against Aras Innovator; verify connector version alignment with your 12.0 SP level before anything else — connector mismatches are the single most common source of silent check-in failures.

Integration Point Architecture

Each connector communicates via Aras’s IOM (Item Object Model) layer over HTTP/HTTPS REST calls to the /Server/odata/ or legacy SOAP endpoint. The connector negotiates the session token, then pushes file + metadata as a compound item transaction.

Key config file (SolidWorks connector, verify path for your install):

%ProgramData%\Aras\CAD Integration\SolidWorks\Innovator.ini

Critical Innovator.ini parameters to lock down:

[Innovator]
ServerURL=https://your-aras-host/InnovatorServer
Database=your_db
WorkingDir=C:\ArasWorkingDir
KeepCheckedOut=1
AutoAssociateRevision=1

For Creo, equivalent settings live in aras_creo_integration.xml — ensure <server_url> and <vault_id> are explicit, not defaulting to localhost during scalability testing.

Version Control Strategy

Avoid relying solely on CAD Generation numbers for traceability. Map a deliberate relationship between Aras Revision (A, B, C…) and CAD internal revision using a custom property on the CAD Item type:

<Item type="CAD" action="edit">
  <cad_revision>creo_rev_03</cad_revision>
  <is_current>1</is_current>
  <source_system>Creo 9.0</source_system>
</Item>

For high-frequency updates, implement a lifecycle state gate: keep the item in Preliminary until a deliberate promotion action triggers the Standard CAD Review workflow. This prevents in-progress geometry from polluting released BOM views.

Configure View Only vault access for non-CAD users to prevent accidental check-out collisions across a growing team.

Design Change Propagation

Where-Used relationships in Aras propagate changes up the BOM, but CAD assemblies need explicit effectivity management. On change propagation, use an Action Method to traverse related items:

// Server-side method triggered post check-in
var bomQuery = this.newItem("Part BOM", "get");
bomQuery.setProperty("related_id", cadItemId);
var affected = bomQuery.apply();
// iterate and flag affected parent assemblies for ECO review

Wire this method to the OnAfterAdd or OnAfterUpdate server event on the CAD ItemType — not the workflow activity — to catch both connector-initiated and manual updates.

Documentation & Maintainability

  • Store connector config files in source control (Git), not just on workstations — team growth without this creates configuration drift fast.
  • Maintain a CAD Integration Admin item type or wiki entry per connected system logging: endpoint URL, vault mapping, connector version, last tested SP.
  • Test connector behavior against Aras Upgrade Simulator (verify availability in your 12.0 SP) before any platform patch.

Primary pitfall in 12.0: the default MaxFileSize vault setting throttles large assembly check-ins silently — confirm web.config maxAllowedContentLength and IIS request limits are raised before scaling to full assembly packages.

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.

3

We run SolidWorks and Inventor integration in 12.0. Key lesson: keep your integration points simple and well-documented. We created a dedicated workflow for each CAD system rather than trying to build one universal workflow. This gives us flexibility to handle system-specific quirks without breaking everything when one connector updates.

4

Version control is critical. We implement a strict branching strategy where CAD files in active design phases use minor revisions (A.1, A.2) and only promote to major revisions (B, C) after design review approval. This is managed through workflow activities that automatically increment version numbers based on approval stage. Also, make sure your CAD connector settings preserve the complete version history - we lost some early design iterations by not configuring this properly initially.

5

Documentation is where most teams fail. We maintain a living integration guide that documents every workflow decision point, connector configuration, and custom method. When CAD connectors update or you upgrade Aras, this documentation becomes invaluable. Include screenshots of workflow maps, activity configurations, and especially any custom file property mappings. We review and update this quarterly during our integration health checks.

6

One pattern that works really well: implement a staging workflow between CAD check-in and formal release. This gives designers a workspace to iterate without cluttering the main PLM workflows. The staging workflow validates file integrity, checks for missing references, and runs automated quality checks before the design enters the official review workflow. Saves a lot of rework and keeps your main workflows clean.

7

For integration points, consider implementing event-driven triggers rather than scheduled imports. We use the CAD connector’s event handlers to automatically start workflows when files are saved in CAD. This provides near real-time synchronization and reduces the manual overhead of initiating workflows. Just be careful with file locking - you need clear rules about when designers can continue working in CAD versus when files are locked in Aras workflow.

8

Watch out for the CAD document structure in 12.0. Make sure your workflow properly handles assembly relationships and BOM synchronization.

9

After managing CAD integration workflows across multiple Aras implementations, I can share what consistently works well for scalable, maintainable deployments.

Integration Points Architecture: The most successful pattern is a three-tier integration approach. First tier handles CAD connector events and file transfer - keep this lightweight and focused solely on data movement. Second tier manages validation and transformation - this is where you check file integrity, extract metadata, and prepare data for Aras. Third tier executes business workflows - design reviews, approvals, change management. This separation makes troubleshooting much easier and allows you to update each tier independently.

Version Control Strategy: Implement a dual-versioning system. CAD files maintain their native versioning (managed by CAD system) while Aras manages PLM revisions. Use workflow activities to synchronize these at specific control points - typically at design freeze and release milestones. Create a custom relationship that maps CAD versions to Aras revisions, giving you complete traceability without forcing rigid version lockstep.

For frequent updates during active design, use a working branch concept where designers iterate freely in CAD, and workflow activities periodically snapshot significant milestones into Aras. This reduces workflow noise while maintaining audit trail for important changes.

Documentation Best Practices: Maintain three documentation layers. Configuration documentation covers connector settings, file property mappings, and workflow definitions - this should be exportable from Aras itself. Process documentation explains the business logic and decision flows - why certain paths exist in workflows. Integration documentation maps the data flow between systems with sequence diagrams.

Critically, embed documentation directly in workflow activities using the description fields. When someone opens a workflow map, they should understand each activity’s purpose without external references. This inline documentation survives system migrations and stays current with workflow changes.

12.0-Specific Considerations: In 12.0, leverage the enhanced CAD connector API for better error handling. Implement retry logic in your workflows for transient connector failures. Also, use the improved file checkout mechanisms to prevent conflicts when multiple engineers work on related assemblies. The workflow should explicitly manage checkout scope to avoid designer frustration.

Scalability comes from modular workflow design - create reusable sub-workflows for common operations like file validation, BOM extraction, and notification. As your team grows, you can enhance these modules without touching every workflow definition.