MCO release fails because CAD data not updated in BOM, causing sync issues

PLM Windchill
, , , , , , , ,
1

Our MCO release workflow is consistently failing at the final release step in Windchill 11.1 M030. The error indicates that BOM components reference outdated CAD revisions, blocking the MCO from completing.

The workflow automation should synchronize CAD revisions with BOM structure before release, but it’s not happening. Engineers update CAD assemblies in Creo, check them into Windchill with new revisions, but when the MCO tries to release, the BOM still points to the old CAD revisions.

Error from workflow log:


MCO-2024-0892 Release Failed
Reason: BOM item ASSY-4521 references CAD rev A.3
Current CAD revision: A.5

This is stalling our entire change process. We have 15 MCOs currently stuck in this state. The BOM-CAD synchronization should be automatic based on our workflow configuration, but clearly revision control isn’t working as expected. Is there a configuration setting we’re missing, or do we need custom workflow automation to force BOM updates before MCO release?

2

We do have a BOM sync activity in the workflow, but maybe it’s not configured correctly. What should the activity settings look like? And is there a way to force-sync all 15 stuck MCOs without manual intervention?

3

I’ll provide a comprehensive solution covering BOM-CAD synchronization, MCO workflow automation, and revision control to resolve your stuck MCOs and prevent future occurrences.

Root Cause Analysis: Your MCO workflow has three critical gaps:

  1. No validation that CAD check-in processing is complete before BOM sync
  2. BOM sync activity not properly configured to update references
  3. No pre-release validation to catch revision mismatches

Solution Part 1: Fix Workflow Automation

Add these activities to your MCO workflow template in this sequence:

Activity 1: CAD Processing Wait (Robot)


// Pseudocode - Wait for CAD processing completion:
1. Get all CAD documents affected by this MCO
2. For each CAD document, check worker queue status
3. If any workers still processing, wait 60 seconds and recheck
4. Timeout after 30 minutes with error notification
5. Once all processing complete, advance to next activity
// See: Windchill Workflow Guide Section 12.3

Activity 2: BOM-CAD Synchronization (Robot) Configure custom robot that:

  • Queries all WTPart objects on the MCO resulting items
  • For each part, retrieves associated CAD document
  • Checks if BOM references match current CAD revision
  • If mismatch detected, updates BOM link to latest released CAD revision
  • Logs all updates for audit trail

Activity 3: Pre-Release Validation (Robot) Add validation gate that verifies:

  • All BOM items reference current CAD revisions
  • No pending CAD worker jobs exist
  • All affected items are in releasable lifecycle states

If validation fails, workflow returns to previous activity with detailed error report.

Solution Part 2: Revision Control Configuration

Update your preference settings:


wt.part.usesLatestConfig=true
wt.workflow.validateBOMReferences=true
wt.mco.enforceCADSync=true

These settings ensure:

  • BOMs automatically reference latest released revisions
  • Workflow validates references before state transitions
  • MCO release requires explicit CAD synchronization confirmation

Solution Part 3: Fix Your 15 Stuck MCOs

Immediate remediation steps:

  1. Identify Mismatches: Run this query to find all BOM-CAD discrepancies:

SELECT mco.number, part.number, bom_cad.revision, current_cad.revision
FROM mco_affected_items
WHERE bom_cad.revision != current_cad.revision
  1. Bulk Update Script: Create utility to update BOM references for all stuck MCOs:
  • Read MCO list (15 items)
  • For each MCO, get affected BOM items
  • Update BOM links to reference latest CAD revisions
  • Log changes for compliance
  • Restart workflow from sync activity
  1. Verification: After updates, verify each MCO:
  • Open BOM structure view
  • Confirm CAD revision matches latest released version
  • Check workflow can proceed past sync activity
  • Complete release process

Solution Part 4: Prevent Future Issues

Implement CAD Check-in Hooks: Add event listener that triggers when CAD documents are checked in:

  • Identifies associated MCOs
  • Flags MCO for BOM review
  • Sends notification to change manager
  • Updates MCO status to indicate pending BOM sync

Add User Guidance: Create workflow instructions that appear when engineers add CAD to MCO:

  • “Ensure CAD check-in completes before advancing MCO workflow”
  • “Verify BOM references updated after CAD revision”
  • “Contact change management if sync errors occur”

Implement Monitoring: Set up daily reports showing:

  • MCOs with pending CAD processing
  • BOM-CAD revision mismatches
  • Workflow activities waiting on sync
  • Failed synchronization attempts

Best Practices for BOM-CAD Synchronization:

  1. Timing Control: Always wait for CAD worker completion before BOM operations
  2. Revision Policies: Define clear rules for which CAD revision BOMs should reference (latest released vs. latest iteration)
  3. Validation Gates: Add multiple validation checkpoints throughout workflow
  4. Error Handling: Provide clear error messages and recovery procedures
  5. Audit Trail: Log all BOM updates for compliance and troubleshooting

MCO Workflow Automation Recommendations:

  • Use robot activities for all system operations (no manual steps for sync)
  • Implement timeout handling for long-running CAD processing
  • Add rollback capability if sync fails mid-process
  • Create workflow variables to track sync status and attempt count
  • Configure email notifications for sync failures

Revision Control Standards:

  • Establish policy: BOMs always reference latest RELEASED CAD revision
  • Exception handling: If no released revision exists, flag for manual review
  • Version tracking: Maintain history of BOM-CAD linkage changes
  • Lifecycle alignment: Ensure CAD and BOM items progress through states together

This comprehensive solution addresses all three focus areas and will resolve your stuck MCOs while preventing future synchronization failures. Implementation typically takes 3-5 days including testing.

4

This is a common issue with MCO workflows in 11.1. The problem is that BOM synchronization is NOT automatic by default - you need explicit workflow activities to update BOM references when CAD revisions change. The standard MCO template doesn’t include this. You need to add a custom robot activity that iterates through affected items, checks CAD revision status, and updates BOM links before the release gate. Without this, engineers have to manually update BOMs, which they’re clearly not doing.

5

The BOM sync activity needs specific configuration: it must run AFTER all CAD check-ins are complete but BEFORE the release approval gate. Set the activity to query all affected items on the MCO, retrieve latest released CAD revisions, and update BOM structure accordingly. For your stuck MCOs, you’ll need to manually update the BOMs first, then restart the workflow from the sync activity checkpoint. There’s no bulk fix without custom scripting.

6

Check your MCO workflow template configuration. There should be a pre-release activity that triggers BOM synchronization. If that activity is missing or disabled, the BOM won’t update automatically. Also verify that your CAD workers are processing check-ins correctly - sometimes worker failures cause revision mismatches.

7

I’ve dealt with this exact scenario multiple times. The root cause is usually timing - CAD check-ins happen asynchronously, so the MCO workflow proceeds before CAD workers finish processing. You need to add wait conditions in your workflow to ensure CAD processing completes before BOM sync attempts. Also consider adding validation rules that prevent MCO release if BOM-CAD mismatches are detected.