Skip to content

CM2

The Promise Lives in People’s Heads

The text discusses the critical gap in knowledge retention within manufacturing, particularly as veteran engineers near retirement. It emphasizes that interchangeability assessments rely on historical context often lost when experienced employees leave. Solutions, like capturing decision-making context, are proposed to build “product memory” and ensure continuity for future engineers.

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.

Why Unmanaged Engineering Notes are a Legal Nightmare!

Why Unmanaged Engineering Notes Are a Legal Nightmare!

This article discusses the importance of structured reasoning capture in product design, emphasizing that while documenting decisions can expose liability in court, disorganized records pose even greater risks. Effective governance of documented reasoning creates a defensible narrative, contrasting with unregulated documentation, which can lead to catastrophic legal outcomes, as seen in high-profile cases.

Product Memory and the Security Paradox

Product Memory and the Security Paradox

This article discusses the risks associated with Product Memory in design processes, emphasizing the importance of securing not just product data but also the underlying rationale behind design decisions. It warns that careless handling of this information can create significant competitive risks and calls for stringent access controls and classification to protect sensitive reasoning.

The reasoning most worth capturing is the reasoning your experts can't articulate.

The reasoning most worth capturing is the reasoning your experts can’t articulate. 

The article highlights the challenges of capturing tacit knowledge in engineering design, emphasizing that valuable insights often exist informally within experienced professionals. It advocates for recording reasoning during decision-making processes and acknowledges the importance of mentoring, suggesting a balanced approach between documentation and recognizing human expertise in knowledge management.

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!

Most Organizations Manage One Effectivity Value. The Change Process Requires Three.

Most Organizations Manage One Effectivity Value. The Change Process Requires Three.

This article discusses the complexity of managing effectivity in change requests, emphasizing the need to track three stages: desired, planned, and actual effectivity. Many organizations neglect the first two stages, hindering the understanding of gaps and potential issues. It advocates for comprehensive documentation to enhance process intelligence and compliance.

Don't Forget Applicability Comes First

Don’t Forget, Applicability Comes First.

The article discusses the application of AI in engineering change management (ECM), highlighting two studies that focus on predicting change propagation and adherence to effectivity dates. It emphasizes the importance of confirming the scope before effectivity and the need for documented processes to support AI modeling. Practitioners should consider the quality of process inputs when deploying AI tools.