Traceability matrix report incomplete for requirements management

PLM Windchill
, , , , , , , ,
1

After our recent upgrade to 11.2 M030, traceability matrix reports are showing incomplete relationship data. We’re missing about 40% of the requirement-to-part links that were visible before the upgrade.

The requirements and parts themselves are all present in the system. When I navigate manually through the requirement details, I can see the traced parts in the relationships tab. But when I generate the traceability matrix report, many of these relationships don’t appear.

We have approximately 1,200 requirements traced to 3,400 parts across multiple product lines. The missing relationships are scattered - not isolated to specific requirements or parts. This is creating audit compliance risk because we can’t verify complete traceability for our regulated products.

system 2

Let me address all three aspects of this traceability issue comprehensively.

Relationship Type Mapping: Windchill 11.2 M030 introduced changes to requirements relationship type definitions. The upgrade process should have migrated relationship types, but custom relationships require manual validation.

Steps to verify and fix relationship type mapping:

  1. Audit existing relationship types: Navigate to Type and Attribute Management > Relationship Types

    Look for requirements-related relationship types:

    • ‘Trace’ (standard requirement-to-part)
    • ‘Derive’ (requirement-to-requirement)
    • ‘Satisfy’ (part-to-requirement)
    • Custom types specific to your implementation

  2. Check traceability report configuration: Open the traceability matrix report definition in Analytics Dashboard

    Review the ‘Relationship Filter’ settings

    Ensure all relationship types are included in the query

    11.2 added new relationship subtypes:

    • ‘TraceAllocate’ (allocated requirements)
    • ‘TraceRefine’ (refined requirements)
    • ‘TraceVerify’ (verified by test cases)

    If your report was created in 11.0 or earlier, it won’t include these new types. Edit the report filter to add them.

  3. Validate custom relationship types: If you have custom relationship types, verify they weren’t deprecated in 11.2

    Check the upgrade documentation for ‘Deprecated Relationship Types’

    For deprecated types, you need to migrate to supported equivalents

Report Index Rebuild: You’ve correctly run the relationship index rebuild, but there are additional index components for traceability:

  1. Complete index rebuild procedure: The relationship index is only one part. For complete traceability, rebuild:

    • Relationship indexes (completed)
    • Requirements specification indexes
    • Part structure indexes (if tracing to assemblies)
    • Change activity indexes (if including change traceability)

  2. Verify index completion: After each index rebuild, check the completion status:

    Navigate to Site > Utilities > Index Management > View Index Status

    Look for any objects with ‘Index State: Failed’ or ‘Index State: Pending’

    For your 1,200 requirements and 3,400 parts, verify counts:

    • Requirements indexed: should match total requirement count
    • Relationships indexed: should match your expected relationship count
    • If counts are lower, some objects failed to index

  3. Index rebuild for historical data: The 15% missing links from pre-2023 data suggests partial index coverage. Force a complete reindex:

    Use the Index Management utility with ‘Force Full Rebuild’ option

    This ignores existing index state and reprocesses all objects

    For historical data, also select ‘Include Archived Objects’

    This operation is resource-intensive. Allocate 8-12 hours during maintenance window.

Upgrade Migration Logs: The upgrade log warnings about incomplete index rebuilds indicate the migration process encountered issues. This requires deeper investigation:

  1. Analyze upgrade logs systematically: Review these specific log files from your upgrade:

    • MethodServer-*.log (index rebuild errors)
    • upgrade-*.log (migration warnings)
    • DBUpgrade.log (database schema changes)

    Search for patterns:

    • ‘RelationshipIndex timeout’
    • ‘Failed to migrate relationship’
    • ‘Deprecated relationship type’

  2. Common upgrade issues for requirements:

    Issue A - Relationship cardinality changes:

    11.2 enforces stricter cardinality rules. Relationships that violated these rules may have been skipped during migration.

    Solution: Query the database for orphaned relationships:

    Check for relationship records where source or target objects no longer exist or are in invalid states.

    Issue B - Relationship ACL migration:

    11.2 changed how relationship ACLs inherit from source/target objects. Relationships with complex ACLs may not have migrated properly.

    Solution: Review relationship ACLs and reapply using current ACL templates.

  3. Post-upgrade cleanup utilities: Windchill 11.2 includes post-upgrade cleanup utilities that should have run automatically but may have failed:

    Navigate to Site > Utilities > Upgrade Utilities

    Look for ‘Requirements Migration Cleanup’

    If status shows ‘Not Run’ or ‘Failed’, execute it manually

    This utility:

    • Converts deprecated relationship types to current equivalents
    • Rebuilds relationship indexes for migrated data
    • Validates relationship integrity

Complete solution for your 1,200 requirements:

Phase 1 - Immediate (Day 1-2):

  1. Run Requirements Migration Cleanup utility if not completed
  2. Update traceability report to include new 11.2 relationship types
  3. Force full index rebuild with ‘Include Archived Objects’ option
  4. Monitor rebuild completion and verify counts

Phase 2 - Validation (Day 3-5):

  1. Generate sample traceability reports for different product lines
  2. Compare against pre-upgrade baseline if available
  3. Identify patterns in still-missing relationships (date ranges, specific requirements, relationship types)
  4. Query database directly to verify relationship records exist

Phase 3 - Remediation (Week 2):

  1. For confirmed missing relationships in database:

    • Check relationship type validity (not deprecated)
    • Verify source and target objects exist and are accessible
    • Validate ACLs on relationship objects

  2. For relationships present in database but not in reports:

    • Verify report query includes those relationship types
    • Check if relationship direction matters (source-to-target vs target-to-source)
    • Validate report ACL allows access to relationship data

  3. For relationships truly lost during upgrade:

    • Restore from pre-upgrade backup if necessary
    • Use relationship import utility to recreate from export
    • Document lost relationships for audit trail

Long-term monitoring:

  1. Schedule weekly traceability report validation
  2. Compare relationship counts against baseline
  3. Set up alerts for index failures
  4. Document all custom relationship types and their mapping to 11.2 equivalents

For your audit compliance needs, document the upgrade issue, remediation steps taken, and validation results. This demonstrates due diligence even if some historical relationships couldn’t be fully recovered.

The combination of proper relationship type mapping, complete index rebuild, and upgrade log analysis will resolve the majority of your missing traceability links.

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

3

Upgrade-related traceability issues usually come from relationship index problems. The traceability matrix report relies on indexed relationship data, and sometimes the upgrade doesn’t properly rebuild these indexes. Check if there are any errors in the upgrade logs related to relationship indexing.

4

I reviewed the upgrade logs and found several warnings about relationship indexes timing out during the migration. The logs show ‘Index rebuild incomplete’ messages for the Requirements module. Should I manually trigger a reindex?

nicknelson 5

Tested this on Windchill 11.2 M030 and auditing the ‘Trace’ and ‘Derive’ relationship types in Type and Attribute Management immediately revealed three unmapped custom relationships causing our incomplete traceability matrix.

6

Yes, definitely run a manual reindex for requirements relationships. Navigate to Site > Utilities > Index Management. Select ‘Requirements’ and ‘Part’ object types, then choose ‘Rebuild Relationship Indexes’. This can take several hours for 1,200 requirements with 3,400 traced parts. Schedule it during off-hours and monitor the Method Server memory usage during the rebuild.

7

Before reindexing, verify your relationship type mappings. Windchill 11.2 changed how some requirement relationship types are stored. Custom relationship types may need remapping in the traceability report configuration. Check the report definition to ensure it’s querying all relevant relationship types - the upgrade may have added new types that aren’t included in your existing reports.

8

I ran the relationship reindex overnight. It completed after 6 hours. The traceability report now shows more relationships, but we’re still missing about 15% of the links. The missing ones seem to be older relationships created before 2023. Could there be a migration issue with historical data?

9

Historical relationships created in older Windchill versions sometimes use deprecated relationship types that aren’t automatically migrated. Check the relationship types on your missing links - they might be using old type names that the 11.2 traceability report doesn’t recognize. You may need to run a relationship type conversion utility to update them to the current schema.