FAQ - Product Portfolio Management

Please note: This page is for sharing information only; it is not a Q&A space or discussion forum. Any comments, questions, or support requests posted here will not be answered and will be deleted. If you have a question, please post it in the community so your peers and our team can respond.

 

Questions & Answers

1. How do I know when a Model Version is ready to be released for use in product configurations?

To determine when a Model Version in the Model Definition widget is ready to be Released—enabling the creation of Product Configurations—you must verify that it meets specific maturity and structural requirements:

Prerequisites for Releasing a Model Version
Before releasing a Model Version, ensure the following conditions are satisfied:

A. Maturity State of the Model Version

  • The Model Version must be in the "Frozen" state before it can be transitioned to "Released".
  • In Work → Frozen → Released (progression path).
  • Note: Only a Frozen Model Version can be promoted to Released.

B. Completion of Engineering Design

  • The 125% BOM (Bill of Materials) must be fully defined and validated.
  • Configuration Rules (e.g., compatibility constraints) must be finalized and tested.
  • This includes all necessary variants, variability values, option groups, options, and evolution effectivities are set.

C. No Pending Changes or Dependencies

  • All dependent objects (e.g., parts, assemblies, or linked documents) should be in a stable state (e.g., Released or Frozen).
  • Any open change requests or engineering tasks tied to the Model Version should be resolved.

 

2. What governance workflows should be applied before approving and releasing a Model Version?

Workflow Overview
The process involves 5 key phases:

  1. Design Completion & Validation
  2. Variant & Rule Definition
  3. Dependency & Change Management
  4. Maturity State Transition (In Work → Frozen → Released)
  5. Final Review & Approval

Phase 1: Design Completion & Validation
Goal: Ensure the engineering design (CAD, BOM, specifications) is finalized and error-free.

Steps:

  • Verify CAD and BOM Completeness:
    • Confirm the 125% BOM (all possible variants, options, and parts) is fully defined in the Model Definition widget.
    • Use the BOM Editor to check for missing or incomplete components.
  • Validate Design Rules:
    • Run design validation checks (e.g., clash detection, manufacturability analysis).
    • Ensure all engineering constraints (e.g., tolerances, material specifications) are met.
  • Check for Engineering Sign-Off:
    • Confirm that the design team has approved the Model Version as ready for manufacturing.
    • Use the Change Action (CA) process if formal approval is required (e.g., via In Approval state).
       

Phase 2: Variant & Rule Definition
Goal: Define and validate variants, options, and configuration rules to support Product Configurations.

Steps:
Define Variants and Options:

  • Open the Model Definition application.
  • Ensure all variants (e.g., colors, materials) and options (e.g., premium features) are created and assigned to the Model Version.
  • Define Configuration Rules:
    • Create rules to enforce valid combinations (e.g., "Premium Audio requires Leather Seats").
    • Test rules using the Configuration Simulator to ensure no conflicts exist.
  • Verify 125% BOM Resolution:
    • Confirm that the 125% BOM (all possible variants) resolves correctly to a 100% BOM for any valid Product Configuration.


Phase 3: Dependency & Change Management
Goal: Ensure all dependencies (e.g., linked parts, documents) and change requests are resolved.

Steps:

  • Check Dependencies:
    • Open the Dependencies tab in the Model Definition widget.
    • Verify that all child objects (e.g., parts, assemblies, drawings) are in a stable state (Released or Frozen).
    • Resolve any broken links or outdated references.
  • Review Change Actions (CAs):
    • Open the Change Management application.
    • Ensure all pending Change Actions tied to the Model Version are completed or closed.
  • If changes are still In Work, either:
    • Complete them before freezing.
    • Demote the Model Version to In Work to incorporate changes.
  • Collaborate with Stakeholders:
    • Notify manufacturing, procurement, and quality teams to confirm readiness.
    • Use collaborative tasks or comments in the 3DSwym app to gather feedback.


Phase 4: Maturity State Transition
Goal: Progress the Model Version from In Work → Frozen → Released.

Steps:

  • Transition to Frozen:
    • In the Model Definition widget, select the Model Version.
    • Click Actions → Promote to Frozen.
    • Note: This step locks the design for review but allows final validation.
  • Final Validation in Frozen State:
    • Perform a final review of the Model Version, including:
      • BOM accuracy.
      • Variant/rule completeness.
      • Dependency resolution.
    • Use the Where Used tool to confirm no downstream processes rely on an unstable version.
  • Transition to Released:
    • Once validated, select the Model Version and click Actions → Promote to Released.

Critical: This action locks the Model Version for Product Configuration creation.


Phase 5: Final Review & Approval
Goal: Obtain formal approval and document the release.

Steps:

  • Submit for Approval (if required):
    • If your process uses formal approvals, create a Change Action (CA) and send it for review.
    • Approvers (e.g., Lead Engineer, Product Manager) will verify readiness.
  • Document the Release:
    • Add release notes in the Model Version’s Properties or Description field (e.g., "Released for 2026 Product Line").
    • Attach any supporting documents (e.g., validation reports, approval emails).
  • Notify Teams:
    • Use 3DSwym or email notifications to inform stakeholders (e.g., manufacturing, sales) that the Model Version is ready for Product Configurations.

 

3. What is the purpose of a Manufacturing Plan?

The Manufacturing Plan serves as a decoupled evolution mechanism for manufacturing structures, enabling them to progress independently of the engineering structures managed via Model Versions. This separation addresses a critical challenge in product lifecycle management: engineering and manufacturing evolve at different rhythms, with distinct milestones, dependencies, and approval cycles. 

 

4. What methods exist to optimize performance when handling large, highly configurable Models with thousands of features?

A. Partition the Model into Smaller, Manageable Units

Problem: Monolithic models with thousands of variants/options slow down performance due to excessive memory and processing demands.

Solution:

  • Modularize the Product Structure:
    • Break the model into sub-assemblies or logical modules (e.g., "Chassis," "Electronics," "Interior").
  • Use Project Partitioning to split the project into separate files, loading only what is needed.
  • Leverage Out-of-Core (OOC) Processing:
    • For block models (e.g., large CAD assemblies), enable OOC processing in tools like BM Converter.
  • OOC divides the model into smaller units, processes them sequentially, and uses smart buffering/compression to minimize memory overhead.


B. Simplify Variant and Option Group Definitions

Problem: Thousands of variants/options create combinatorial complexity, slowing down configuration resolution.

Solution:

  • Group Related Variants:
    • Use Option Groups to bundle related options (e.g., "Premium Package" instead of individual options for leather seats, premium audio, etc.).
  • Limit Active Variants:
    • Archive or deactivate unused variants to reduce the active configuration space.
  • Use Rule Deduced Criteria:
    • Apply "No Rules Applied" mode during testing/initial setup to bypass rule checks temporarily.
  • Switch to Matrix or Expression-based rules only for final validation.


C. Optimize Configuration Rules

Problem: Complex rules (e.g., nested conditions) increase processing time.

Solution:

  • Prioritize Matrix Rules:
    • Matrix rules (interactive tables) are faster to resolve than expression-based rules for large datasets.
  • Avoid Redundant Rules:
    • Consolidate overlapping or duplicate rules.
  • Pre-Validate Rules:
    • Use the Configuration Simulator to test rules on a subset of variants before applying them globally.

 

Comments 0