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. Can I do Configured Replace an item1 with item2 and then item2 with item3 within the same Change? If not, then how do I achieve this?
In the 3DEXPERIENCE platform, performing multiple sequential "Configured Replace" operations (e.g., replacing item1 with item2 and then item2 with item3) within a single Change Action is not directly supported. Each "Configured Replace" operation typically requires a separate Change Action to ensure traceability, validation, and proper lifecycle management of the changes.
How to Achieve Sequential Replacements:
Use Multiple Change Actions:
- Create two separate Change Actions within the same Change Order:
- First Change Action: Replace
item1withitem2. - Second Change Action: Replace
item2withitem3.
- First Change Action: Replace
- Group these Change Actions under a single Change Order to maintain their relationship and ensure they are processed sequentially. This approach is supported in the platform, as Change Actions can be grouped under a Change Order for dependencies or related modifications.
- Create two separate Change Actions within the same Change Order:
Leverage Change Action Dependencies:
- Define dependencies between the two Change Actions to enforce the order of execution. For example:
- Set the second Change Action (replacing
item2withitem3) as dependent on the completion of the first Change Action (replacingitem1withitem2).
- Set the second Change Action (replacing
- Define dependencies between the two Change Actions to enforce the order of execution. For example:
Validate and Approve:
- Ensure both Change Actions are reviewed and approved as part of the Change Order workflow to maintain compliance and traceability.
Key Considerations:
- Traceability: Using separate Change Actions ensures that each replacement is documented, auditable, and aligned with the platform's change management best practices.
- Dependencies: Explicitly defining dependencies prevents conflicts and ensures the correct sequence of operations.
- Change Order Grouping: Grouping related Change Actions under a single Change Order simplifies tracking and approval processes.
2. How to set structure as configured?
Open the Product Structure
- Launch the Product Structure Editor
- Open the product structure you want to configure (e.g., a car assembly).
Assign the Configuration Context to the Structure
- Select the root node of your product structure (e.g., the top-level assembly).
- Right-click → Configuration → Edit Configuration Context.
- Alternatively, click the Edit Configuration Context icon in the toolbar:Configuration.
- In the Edit Configuration Context dialog:
- Click Add Context.
- Search for your Model (e.g., Car_Config_Model).
- Select the model and click OK.
- Enable Criteria:
- Check the boxes for the criteria you want to use:
- Variant criteria: Enables Configuration Features (e.g., Market, Trim_Level).
- Evolution criteria: Enables Model Version, Unit, Manufacturing Plan, Date, or Milestones.
Click Close to save.
3. What are the criteria that can be used to define an evolution effectivity?
In Configuration Engineering, defining evolution effectivity ensures that changes to a product or system are applied at the correct time or under the correct conditions. The criteria for defining evolution effectivity can vary based on the context and tools used, but the following are the most common and widely recognized criteria:
1. Date-Based Effectivity
- Date Ranges: Define the start and end dates for when a change or configuration becomes effective. This is useful for tracking product evolution over time, such as design updates or manufacturing changes.
- Example: A new component revision becomes effective from January 1, 2027 .
- Global vs. Context-Specific Dates:
- Global Date Effectivity: Applies universally across all contexts.
- Context Date Effectivity: Applies only to specific models, products, or processes.
2. Model Version
- Assign effectivity based on specific model versions or revisions. This ensures that changes are tied to a particular stage in the product's lifecycle.
- Example: A new design revision (e.g., Revision C) replaces an older one (e.g., Revision B).
3. Unit-Based Effectivity
- Define effectivity based on unit numbers or serial numbers of manufactured products. This is useful for tracking changes in production batches.
- Example: A change applies to all units manufactured after Unit #1000.
4. Manufacturing Plan
- Tie effectivity to stages in the manufacturing plan, such as production milestones or phases.
- Example: A process update becomes effective during Phase 2 of manufacturing.
Best Practices for Evolution Effectivity
- Avoid Blank Effectivity: Always assign a clear effectivity criterion to avoid ambiguity.
- Use "Work Under Evolution" or "Work Under Change": Apply effectivity while working on changes to ensure consistency.
- Leverage Configuration Tools: Use tools like 3DEXPERIENCE or ENOVIA to manage and visualize effectivity across product lifecycles.
4. How do I validate that a configured Product Structure complies with the rules defined in the system? --> in the model version
Key Validation Methods in Configured Product Structures
Validation ensures that a product structure adheres to design rules, effectivity constraints, and configuration logic (e.g., compatibility between variants/options). The sources highlight the following mechanisms:
1. Filtering for Compliance
Configuration filters allow engineers to refine structures using criteria like:
Variant/option effectivity: Ensures only valid combinations are included (e.g., filtering out parts incompatible with selected variants).
Evolution effectivity: Validates configurations against lifecycle states (e.g., ensuring parts are not obsolete).
Change action criteria: Checks if proposed changes (e.g., engineering updates) comply with approved configurations.
Unit criteria: Validates allocations to specific units (e.g., aircraft line numbers).
Example Workflow:
Apply a filter to a 150% configured structure (a template with all possible variants).
The system excludes invalid combinations (e.g., parts with conflicting effectivity).
2. Effectivity Checks
Variant/option effectivity expressions define when a part is valid (e.g., "Part Y is included only if Variant Z is selected").
Inline editing in the Product Structure Editor lets engineers verify or modify these expressions.
Occurrence effectivity displays the active criteria for an instance in multi-level assemblies, helping validate nested configurations.
Step-by-Step Validation Process (Inferred)
Based on the sources, here’s how you might validate a configured structure:
Open the Configured Structure:
Use the Product Structure Editor (with Configuration Engineer or Product Management role) to access the structure.
Apply Configuration Filters:
Create a filter with variant/option, evolution, or change action criteria to isolate the configuration.
Example: Filter by "Variant = Premium" and "Change Action = Approved" to validate a high-end product version.
Verify Effectivity Expressions:
In the Variant/Option column, ensure each part’s effectivity aligns with the configuration (e.g., "Part A is included only if Option 1 is selected").
Use inline editing to correct expressions if needed.
Test with "What-If" Scenarios:
Temporarily turn off rules to simulate edge cases (e.g., "What if Variant X is excluded?").
Reapply filters to confirm the system blocks invalid configurations.
Review Occurrence Effectivity:
For multi-level assemblies, use the Display Effectivity dialog to confirm nested parts comply with top-level criteria.
5. How and when do I use the “Extend Evolution Effectivity” command?
The "Extend Evolution Effectivity" command is a powerful tool for Configuration Engineers working in Dassault Systèmes' Configured Engineering environment. It allows you to extend the evolution effectivity of an instance without evolving it, ensuring that the effectivity defined in the current Evolution scope applies to the selected instances.
When to Use It
Use the "Extend Evolution Effectivity" command in the following scenarios:
- Extending Effectivity Scope: When you need to apply the evolution effectivity of an instance to additional instances in the structure without creating new evolutions.
- Working Under Evolution: When you are actively working in an Evolution context and want to propagate effectivity changes to other instances.
- Simplifying Effectivity Management: When managing effectivities across multiple instances simultaneously, such as applying the same effectivity to a group of instances.
How to Use It
Prerequisites:
- Ensure the instance already has evolution effectivity defined.
- The parent reference of the instance must have a model defined as its Configuration Context.
- The Authoring Context must be set to Evolution.
- You must be working under Evolution in the session.
Steps:
- Select the instances for which you want to extend the evolution effectivity.
- Navigate to the Tools section of the action bar.
Click the Extend Evolution Effectivity icon:
- The extended effectivity will now apply to the selected instances.
Key Benefits
- Efficiency: Apply effectivity changes to multiple instances at once, reducing manual effort.
- Flexibility: Extend effectivity without evolving the instance, preserving the structure.
- Consistency: Ensure uniform effectivity across related instances in the product structure.
Note: If you are working with effectivity-based revisions, the effectivity will be extended based on the evolution effectivity set in the session.
6. Why can’t I revise a Product when I assigned a Model context?
When you assign a Model as a Configuration Context to a Physical Product, you cannot revise the Physical Product directly because it becomes a configured object. This behavior is by design in the 3DEXPERIENCE platform, and the reasons are rooted in how configuration contexts and lifecycle states interact. Below is a detailed explanation:
Why Revision Is Blocked for Configured Objects
When a Physical Product is assigned a Model as its Configuration Context, it is treated as a configured object, which enforces the following constraints:
- A. Lifecycle and Revision Restrictions
- Configured objects are governed by their Model’s lifecycle, not their own.
This means the Physical Product’s revisions and maturity states (e.g., In Work, Frozen, Released) are locked to prevent conflicts with the Model’s evolution.
7. Why is it that I can’t see my Variant/Option group to define for an Instance when I have the Variant/Option group allocated for a Model Version?
The Evolution Effectivity range may contain a Model Version Revision in which the Variants/Option Groups are not allocated. Also check the Variants/Option Groups are in the Available state.
8. What best practices exist for managing large configurable structures with hundreds of options and variants?
1. Modular Design and Hierarchical Structures
Break down into sub-assemblies: Divide the product into logical sub-assemblies (e.g., chassis, interior, electronics) to simplify management and reduce complexity.
Use a 150% BOM approach: Include all possible variants in a single structure, then use effectivity rules to filter configurations dynamically. This avoids duplication and ensures consistency.
2. Optimize Effectivity Rules
Simplify rules: Avoid overly complex nested rules (e.g., IF (A AND (B OR (C AND D)))). Instead, break them into smaller, manageable expressions.
Use matrix rules: For simple dependencies, matrix rules are easier to validate and perform better than expression-based rules.
