Table A2 Design guide for integrating... | Emerald Publishing

Table A2

Design guide for integrating reuse logic into product configuration systems

Dimension	Step 1: Model reused components in configuration structure	Step 2: Define conditional rules for reuse eligibility	Step 3: Link configuration to verification and inventory data	Step 4: Update and maintain reuse logic over time
Why this is relevant	Enables reused parts to be selectable in the configurator and modeled consistently across variants	Ensures reused components are only used when quality, compatibility, and availability are confirmed	Connects design logic to real-world data and workflows, enabling reliable and traceable reuse	Keeps reuse logic relevant and aligned with changes in product design, systems and strategy
Key questions to ask	- Are reused parts currently represented in the configuration structure? - Do reused parts follow the same modeling logic as new parts? - Are they stored as alternatives, variants, or separate modules?	- What conditions must be met for a reused part to be used? - Are there configuration rules already in place that could support this logic? - How does quality status or batch data influence part selection?	- Is there a link between the configurator and systems like PLM and ERP? - Can data on reuse eligibility or inventory status be accessed in real time? - Who validates this information?	- Who updates reuse logic when components or design rules change? - How often is reuse eligibility reviewed? - Is there version control and traceability for reuse rules?
How to apply it	- Represent reused parts in the bill of materials and configuration model - Use the same component ID with reuse metadata or flags - Ensure compatibility with design variants	- Define logic that limits reuse to certain quality levels, use cases, or customer types - Use rule-based filtering or attribute logic in the configurator - Ensure logic is transparent to users and maintainable	- Create system connections to reuse verification and inventory systems - Link reuse metadata to configuration rules - Automate updates where possible	- Assign responsibility for reuse logic ownership - Review reuse pathways during design updates - Align reuse rules with system upgrades and supply chain changes
Expected outcomes	- Reused parts are embedded in the configuration model - Customers and engineers can select reused parts like any other variant - System behavior is consistent across configurations	- Only viable reused parts are selectable in configurations - Reduced risk of quality or delivery issues - Easier governance of reuse rules	- Real-time availability and quality info supports decision-making - Improved alignment between engineering and operations - Traceable reuse decisions	- Reuse logic stays valid and evolves with product architecture - Reduces the risk of outdated or incorrect configurations - Improves governance and long-term scalability
Challenges to anticipate	- Configuration models may lack flexibility to represent reused parts - Variant logic may become overly complex - Lack of agreement on how reused parts should be named or tracked	- Defining reuse logic may require new attributes or data structures - Risk of hardcoding rules that are difficult to maintain - User-facing logic may be too technical or unclear	- System integration is often fragmented or manual - Data may be delayed or incomplete - Inventory and quality systems may not be aligned with reuse needs	- Reuse logic may not be prioritized during system updates - Responsibility for maintaining logic may be unclear - Versioning and traceability may not be consistently enforced

Dimension	Step 1: Model reused components in configuration structure	Step 2: Define conditional rules for reuse eligibility	Step 3: Link configuration to verification and inventory data	Step 4: Update and maintain reuse logic over time
Why this is relevant	Enables reused parts to be selectable in the configurator and modeled consistently across variants	Ensures reused components are only used when quality, compatibility, and availability are confirmed	Connects design logic to real-world data and workflows, enabling reliable and traceable reuse	Keeps reuse logic relevant and aligned with changes in product design, systems and strategy
Key questions to ask	- Are reused parts currently represented in the configuration structure? - Do reused parts follow the same modeling logic as new parts? - Are they stored as alternatives, variants, or separate modules?	- What conditions must be met for a reused part to be used? - Are there configuration rules already in place that could support this logic? - How does quality status or batch data influence part selection?	- Is there a link between the configurator and systems like PLM and ERP? - Can data on reuse eligibility or inventory status be accessed in real time? - Who validates this information?	- Who updates reuse logic when components or design rules change? - How often is reuse eligibility reviewed? - Is there version control and traceability for reuse rules?
How to apply it	- Represent reused parts in the bill of materials and configuration model - Use the same component ID with reuse metadata or flags - Ensure compatibility with design variants	- Define logic that limits reuse to certain quality levels, use cases, or customer types - Use rule-based filtering or attribute logic in the configurator - Ensure logic is transparent to users and maintainable	- Create system connections to reuse verification and inventory systems - Link reuse metadata to configuration rules - Automate updates where possible	- Assign responsibility for reuse logic ownership - Review reuse pathways during design updates - Align reuse rules with system upgrades and supply chain changes
Expected outcomes	- Reused parts are embedded in the configuration model - Customers and engineers can select reused parts like any other variant - System behavior is consistent across configurations	- Only viable reused parts are selectable in configurations - Reduced risk of quality or delivery issues - Easier governance of reuse rules	- Real-time availability and quality info supports decision-making - Improved alignment between engineering and operations - Traceable reuse decisions	- Reuse logic stays valid and evolves with product architecture - Reduces the risk of outdated or incorrect configurations - Improves governance and long-term scalability
Challenges to anticipate	- Configuration models may lack flexibility to represent reused parts - Variant logic may become overly complex - Lack of agreement on how reused parts should be named or tracked	- Defining reuse logic may require new attributes or data structures - Risk of hardcoding rules that are difficult to maintain - User-facing logic may be too technical or unclear	- System integration is often fragmented or manual - Data may be delayed or incomplete - Inventory and quality systems may not be aligned with reuse needs	- Reuse logic may not be prioritized during system updates - Responsibility for maintaining logic may be unclear - Versioning and traceability may not be consistently enforced