PLM and CAD Integration: Connecting Your Design Environment to Product Data

The CAD-PLM integration is where most engineers encounter PLM in their daily work. It's also where most PLM deployments either succeed or fail at the user adoption level. Engineers who experience a fast, transparent checkout-save-check-in loop adopt PLM readily. Engineers who fight through slow connections, broken references, and confusing revision dialogs find workarounds — and those workarounds undermine everything PLM is supposed to deliver.

This guide covers the technical and configuration decisions that determine whether your CAD-PLM integration is the former or the latter.

How CAD-PLM Integration Works

The fundamental model is check-out / modify / check-in:

1. Check-out: Engineer requests a file from PLM vault. PLM marks the file as locked (pessimistic) or creates a working copy (optimistic). File downloads to the local CAD session working directory.
2. Modify: Engineer works in CAD normally. PLM is invisible during this phase.
3. Check-in: Engineer checks the file back into PLM. The connector extracts BOM data, increments the revision, and uploads the file to the vault. PLM unlocks the file.

The connector sits between CAD and PLM, handling the protocol translation — converting CAD file paths and assembly structure to PLM part numbers and BOM relationships.

CAD Application
    ↕ (connector API)
PLM CAD Connector Plugin
    ↕ (PLM REST/SOAP API or native protocol)
PLM Server / Vault

Connector Architecture Options

Native connector (vendor-supplied)

Most PLM vendors supply native connectors for major CAD platforms:

• PTC Windchill: native connectors for Creo, CATIA V5, NX, SolidWorks, Inventor
• Siemens Teamcenter: native connectors for NX, CATIA, SolidWorks, Creo
• Dassault ENOVIA: native CATIA integration (tightest available), connectors for NX/SolidWorks

Native connectors have the best BOM extraction fidelity and the most seamless check-in workflow. They are also version-coupled — a connector certified for CATIA V5-6R2023 may not work for V5-6R2024 without an update.

Third-party middleware

For multi-CAD environments or PLM-CAD combinations not covered by native connectors, third-party middleware (CADLink, CENIT FASTSUITE, Prostep ivip) sits between CAD and PLM:

SolidWorks ──┐
CATIA V5  ──┤── Middleware (normalized BOM/file format) ──── PLM
NX        ──┘

Middleware normalizes the CAD output to a vendor-neutral format (usually JT or STEP + XML BOM) before passing it to PLM. This enables a single PLM BOM view across multiple CAD systems.

Trade-off: Middleware adds latency and introduces a third vendor dependency. It's usually worth it when you have 3+ CAD systems; unnecessary for 1–2.

Cloud CAD (Onshape, Fusion 360)

Cloud-native CAD platforms have PLM integration architectures that look different from traditional connectors:

• Onshape connects to Arena PLM, Propel, and others via REST APIs — no local connector plugin
• Fusion 360 has native Autodesk PLM integration
• Files live in the cloud CAD platform's storage, not a local PLM vault

For teams using cloud CAD, PLM integration is typically through API rather than filesystem connectors. This changes the architecture significantly but eliminates the vault replication and connector version management problems.

BOM Extraction

Automatic BOM extraction from CAD assemblies is the most valuable part of the CAD-PLM integration — and the most configuration-intensive.

What the connector must extract

For each CAD assembly, the connector should extract:

<!-- Example extracted BOM structure (conceptual) -->
<Assembly partNumber="ASM-001" revision="A" description="Main Housing Assembly">
  <Component partNumber="PRT-101" qty="2" findNumber="10" unit="EA"
             description="Housing Top" material="AL6061" weight="0.42kg"/>
  <Component partNumber="PRT-102" qty="1" findNumber="20" unit="EA"
             description="Housing Bottom" material="AL6061" weight="0.38kg"/>
  <Component partNumber="STD-001" qty="8" findNumber="30" unit="EA"
             description="M4x12 Socket Head Cap Screw" category="Standard"/>
  <SubAssembly partNumber="ASM-002" qty="1" findNumber="40">
    <!-- Recursively nested -->
  </SubAssembly>
</Assembly>

The connector must handle:

• Recursive assembly nesting — assemblies within assemblies, to any depth
• Quantity and find number extraction — quantities must come from the CAD assembly definition, not manual entry
• Standard parts recognition — catalog parts and standard hardware often have different attribute sets than custom parts
• Configuration handling — products with design configurations (e.g., "Standard" vs. "Heavy Duty") may need separate BOM extraction per configuration

BOM extraction validation

After configuring BOM extraction, validate against manual count:

# Validation script concept
def validate_bom_extraction(cad_bom, plm_bom):
    """Compare BOM extracted by CAD connector against expected BOM"""
    cad_parts = {row['partNumber']: row['qty'] for row in cad_bom}
    plm_parts = {row['partNumber']: row['qty'] for row in plm_bom}
    
    missing = set(cad_parts.keys()) - set(plm_parts.keys())
    extra = set(plm_parts.keys()) - set(cad_parts.keys())
    qty_mismatch = {p: (cad_parts[p], plm_parts[p]) 
                    for p in cad_parts if p in plm_parts 
                    and cad_parts[p] != plm_parts[p]}
    
    return {
        'missing_from_plm': list(missing),
        'extra_in_plm': list(extra),
        'quantity_mismatches': qty_mismatch,
        'match': not (missing or extra or qty_mismatch)
    }

Target: 100% match before declaring the connector production-ready. Any missed component or incorrect quantity is a BOM error waiting to reach manufacturing.

Revision Management

PLM as the system of record for revision

The most important architectural decision: PLM is the system of record for revision state. CAD's own "save as version" functionality is a working-copy mechanism, not the authoritative revision history.

The connector enforces this by:

1. Writing the current PLM revision into the CAD file's revision attribute on checkout
2. Incrementing the revision in PLM (not in CAD) on check-in
3. Blocking engineers from modifying the PLM-managed revision attribute directly in CAD

If engineers can manually change revision numbers in CAD without going through PLM, revision state diverges within weeks.

Revision increment rules

Define the revision increment rules explicitly:

| Change Type | Revision Increment Example | |-------------|---------------------------| | Major redesign (new part shape, material change) | A → B | | Minor change (tolerance, note, non-functional) | A → A1 or A (with internal version) | | Released → In Work | No PLM revision change until release |

These rules need to be enforced by PLM workflow, not by engineering discipline alone.

Multi-CAD Environments

Multi-CAD environments — common in companies that have grown through acquisition — require explicit decisions about BOM ownership.

The multi-CAD BOM challenge

An assembly might reference components from multiple CAD systems:

Top-Level Assembly (CATIA V5)
├── Sub-Assembly A (NX)
│   ├── Part A1 (NX)
│   └── Part A2 (SolidWorks from acquired company)
└── Sub-Assembly B (CATIA)
    └── Standard parts (catalog parts, no native CAD file)

The PLM BOM must be able to represent this structure coherently, even though no single CAD session can open the full assembly natively.

Practical approaches

Neutral file interchange: For cross-CAD assembly verification, generate STEP assemblies that can be loaded in any CAD system for visualization and interference checking. The native files remain in their home CAD systems in PLM.

JT visualization model: Create JT (Siemens' lightweight 3D format) representations of all parts, regardless of native CAD system. Use JT for assembly review, visualization, and supplier sharing. JT can be auto-generated by most PLM connectors on check-in.

Designate one CAD system for new development: Over time, retire the secondary CAD systems by requiring all new product development to use the primary CAD platform. This is a multi-year transition but eliminates the multi-CAD complexity long-term.

Performance Optimization

Checkout performance

Checkout time is the most visible performance metric for engineers. Factors:

• File size: Large assemblies (2GB+) take longer to download from vault. Use vault replication for remote sites.
• Reference resolution: CATIA external references require resolving all referenced files before checkout is complete. Pre-cache frequently accessed reference files.
• Network: As covered in the distributed teams guide, >150ms latency to the vault creates noticeable delays.

Target: <10 seconds for individual parts and small assemblies; <60 seconds for large assemblies (100+ parts).

Concurrent checkout limits

Define concurrent checkout limits per vault server based on server capacity. Most enterprise PLM vaults handle 50–100 concurrent checkouts without performance degradation; above this, queue management becomes necessary.

Common Failure Modes

Connector version mismatch after CAD upgrade. A CATIA V5-6R2023 connector won't work with V5-6R2024 without an update. Coordinate CAD upgrades with connector updates; test in a staging environment before production rollout.

BOM drift because engineers bypass the connector. Engineers who find the connector slow or problematic copy CAD files directly to shared drives and update BOMs manually. Monitor checkout/check-in patterns; outliers indicate connector usability problems.

Broken external references after migration. CATIA external references point to specific vault paths. If those paths change (e.g., during a PLM server migration), assemblies open with broken references. Test reference resolution after any infrastructure change before releasing to engineers.

Standard parts not recognized as purchased. Standard hardware (screws, bearings, seals) should be marked as purchased parts in PLM and not require CAD native files. If the connector treats them as designed parts, engineers get check-in errors for parts that have no CAD file to upload.

Acceptance Criteria for CAD Integration Go-Live

Before releasing the connector to production:

• [ ] Checkout time <10s for 95% of individual parts and small assemblies
• [ ] BOM extraction matches manual count with 0 discrepancies on 10 test assemblies
• [ ] Revision increment works correctly through 3 consecutive check-out/check-in cycles
• [ ] External references resolve correctly after check-in (open the assembly from PLM, confirm no broken links)
• [ ] Standard parts recognized as purchased (no CAD file required)
• [ ] Multi-CAD BOMs display correctly in PLM BOM viewer (if multi-CAD environment)
• [ ] Concurrent checkout performance tested with 20 simultaneous users

Related Resources

• [[PLM for Distributed Teams]] — vault replication for remote engineering sites
• [[PLM Enterprise Rollout]] — multi-CAD environments in multi-site deployments
• [[Engineering BOM vs Manufacturing BOM]] — what PLM does with the EBOM after extraction
• [[Vendor Spotlights]] — how different PLM vendors approach their CAD connector ecosystems