Skip to content

Identification

One Part, Five Numbers

The article highlights the issue of parts with duplicate numbers obscuring interchangeable parts. It emphasizes the hidden costs of managing duplicates, which can lead to inefficiencies and lost savings. By implementing better identification schemes, organizations can reclaim the value of interchangeable items, potentially saving millions annually. Understanding and managing these duplicates is essential for operational efficiency.

The Regulator Is About to Ask for the Receipts

Starting February 18, 2027, EU regulations will require traceability for every EV battery through the Digital Product Passport, mandating records of production details. Effective configuration management is essential for compliance to avoid false declarations. Organizations must treat this regulation as a critical data discipline rather than merely a sustainability exercise.

Interchangeable Does Not Mean Identical

The debate around the “Part Proxy” concept, introduced by Prof. Dr. Jörg W. Fischer, highlights challenges in managing interchangeable parts across different plants in manufacturing. It emphasizes the need for proper identification and interchangeability criteria, advocating for distinct part numbers when constructions differ, while maintaining a system for equivalent items to ensure clarity in manufacturing processes and documentation.

The Question Your Configuration Management System Can't Answer!

The Question Your Configuration Management System Can’t Answer!

The article examines the concept of Product Memory within the context of configuration management (CM), highlighting the importance of preserving the reasoning behind engineering decisions. It emphasizes that while CM effectively manages the “what” of product data, it often overlooks the critical “why.” This gap can lead to significant risks, particularly in complex systems. The integration of AI could assist in retrieving and recording this reasoning, reinforcing the value of… Read More »The Question Your Configuration Management System Can’t Answer!

Configuration errors don't age out. They compound.

Configuration errors don’t age out. They compound.

The article discusses the concept of configuration debt in product development, highlighting how initial errors in product variant assessments can lead to compounded issues over time. Unlike technical debt, configuration debt manifests in hidden warranty claims and field failures, stemming from unaddressed applicability confirmations that impact subsequent engineering decisions.

Applicability Before Effectivity

Whether Before When / Applicability Before Effectivity

The article discusses the importance of distinguishing between applicability and effectivity in change management. It highlights how confusion arises when both concepts are tackled simultaneously, leading to unresolved issues during meetings. The author advocates for a structured process that separates scope confirmation from effectivity assignment, enhancing productivity and decision-making in organizations.

How Do YOU CM2?

How Do YOU CM2? – Part 3

In case you missed them, you can find the following How do YOU CM2? posts in the 46th edition of the Future of CM newsletter: 1️⃣ What Works Better: One Change Process or Many? 🔀 Is Your Data Model Truly Change-Proof? 🧠 Is Your Organization Truly Model-Based or Does It Still Rely on Tribal Knowledge?

parts don't have revisions

Why Parts Don’t Have Revisions (Only Datasets Do)

This article emphasizes that parts do not have revisions; rather, datasets do. It discusses the confusion and inefficiency created by treating part revisions as part of the part number. Shifting focus to dataset revisions enhances clarity, reduces errors, and streamlines processes within organizations, driving down costs and improving quality in product development.

Engineer struggles to embed software

Software in the Configuration Management Baselines

The article discusses the importance of incorporating Software Bills of Material (BoM) in product configuration management. It highlights the differences between third-party and in-house developed software, emphasizing the need to manage software licenses, dependencies, and options effectively to prevent deployment issues. Proper management is crucial for ensuring product functionality and compliance.