Why the future of enterprise intelligence depends on knowing what to remember, what to trace, and when to challenge yesterday’s decisions.
AI is reshaping daily PLM and wider enterprise conversations. Beyond connected data and digital threads, attention is shifting towards product memory: preserving the knowledge, decisions and reasoning that explain how products evolve. The proposition is compelling. Enterprises have accumulated decades of engineering and operational information, yet much of the context behind their decisions remains fragmented across systems, documents and people.
AI introduces new possibilities for discovering relationships and recovering context that traditional enterprise software and integrations were not designed to capture. However, remembering more does not necessarily mean understanding more. What should an enterprise remember? What must it retain for traceability? And what should it be prepared to challenge as circumstances change?
These questions take product memory beyond engineering knowledge and into the broader discussion of enterprise cognition.
Product Memory Extends Beyond PLM
PLM preserves important information about product definitions, requirements, configurations, engineering decisions and changes. However, this represents only one perspective of the product lifecycle. ERP manages suppliers, purchasing, materials, costs, manufacturing orders, inventories and financial transactions. MES captures manufacturing execution, while quality, laboratory, regulatory and service systems preserve further evidence of conformity, performance and product history.
Consider a material substitution. PLM may explain why an alternative specification was approved. ERP identifies supplier availability, costs and procurement commitments. MES establishes which production batches used the material, while quality systems provide evidence of conformity. Each system contributes to understanding the decision, yet none provides the complete picture. Equally, decisions do not flow exclusively from engineering into operations. Supplier constraints, production failures, cost pressures and regulatory changes frequently trigger new engineering decisions.
Product memory is therefore distributed across the enterprise, not owned by PLM or any other software platform. The opportunity lies in connecting these perspectives and preserving their relevant decision context, rather than creating another repository claiming to contain the complete product history.
Remembering Everything Is Not the Objective
Enterprises generate thousands of decisions and transactions every day. Some represent valuable knowledge, while others are routine, temporary or relevant only to specific circumstances. Should every engineering discussion, discarded alternative, supplier quotation, production adjustment or AI-generated recommendation become part of permanent product memory? Not necessarily.
Indiscriminate preservation may make valuable knowledge harder to identify, while obsolete assumptions and conflicting interpretations accumulate over time. The challenge is determining which decisions deserve preservation, what evidence must remain traceable and which information continues to have value for future decisions.
Three questions should guide this process:
- What must be retained? Records required for legal, regulatory, contractual, quality or intellectual property purposes.
- What is worth remembering? Decisions, rationale, experience and lessons that may improve future innovation and operations.
- What should be reconsidered? Assumptions and conclusions whose validity may change with technology, competition, regulation or business priorities.
These considerations overlap, but their application depends on the organisation’s operating model and the significance of the decisions involved. A production record may require long-term retention without becoming active knowledge for AI reasoning. Conversely, an engineering lesson may remain valuable even when its supporting records are no longer subject to mandatory retention.
Product memory’s value lies in preserving relevant decision context, not in remembering everything. Appropriate context must reflect the decisions an enterprise makes, the risks it manages, and the obligations it must fulfil.
Product memory cannot be defined solely by the information available for preservation or the technology that can retrieve it. The enterprise must first establish which decisions are material to its operating model, which require demonstrable evidence, and which historical assumptions remain relevant to future decisions. This determines the appropriate depth of decision context, its governance and its lifecycle. Without that business perspective, Product memory risks becoming another exercise in accumulating information rather than improving decisions.
Traceability and Memory Serve Different Purposes
Traceability establishes what happened, when, where, and under whose authority. Decision context explains why it happened, which assumptions influenced the outcome and what the enterprise may learn from it. These capabilities complement each other, but serve different purposes.
This distinction is particularly important for OEMs operating across complex supply chains, manufacturing environments and regulated industries.
| Information domain | Enterprise requirement |
|---|---|
| Engineering and IP | Preserve design rationale, inventions, patents and technical know-how. |
| Regulatory and compliance | Retain submissions, notifications, approvals and conformity evidence. |
| Quality and manufacturing | Trace production genealogy, inspections, deviations and corrective actions. |
| Commercial and supply chain | Understand supplier choices, procurement commitments, costs and constraints. |
| Service and warranty | Maintain relevant product history, warranty evidence and field performance. |
| Organisational knowledge | Preserve selected assumptions, lessons learned and decision rationale for reuse. |
These domains have different owners, retention requirements and levels of criticality. An aerospace manufacturer, automotive OEM and consumer goods company cannot reasonably apply identical traceability and knowledge-retention practices.
Traceability may be mandatory, while organisational memory must be purposeful. This distinction becomes more important as AI enables richer traceability. Traditional integrations generally connect predefined data structures, transactions and workflows. AI can increasingly discover relationships across engineering documents, supplier correspondence, manufacturing records, quality reports and other previously disconnected information. It can help reconstruct decision context and reveal dependencies that conventional integrations may have overlooked.
However, AI-discovered relationships are not automatically verified traceability. Provenance, source authority, evidence, applicability and appropriate validation remain essential, particularly where safety or compliance is involved. The opportunity is to establish richer contextual traceability across systems without compromising the integrity of authoritative records.
Enterprise Context Must Drive Product Memory
What an organisation needs to remember depends fundamentally on how it operates and creates value. Its mission, products, business model, markets and regulatory environment determine which decisions matter, what requires evidence and how much context must be preserved.
An aerospace manufacturer may prioritise configuration integrity and long-term safety evidence. A consumer goods business may focus on formulations, supplier qualifications, regulatory submissions and manufacturing consistency. A software-intensive OEM may require deeper relationships between hardware configurations, software releases and cybersecurity decisions. These differences reflect distinct operating models, not simply different technology architectures.
This is where my earlier cognitive PLM debate becomes particularly relevant. The Product Digital Backbone establishes structural continuity across processes, systems, people and governance. The digital thread connects lifecycle information and supports traceability. The cognitive data thread extends these relationships by preserving decision context, including rationale, assumptions, constraints and human judgment.
The appropriate depth of that context, its retention requirements and its relevance to future decisions must reflect the organisation’s operating model rather than a blanket approach applied across every system and process. Together, these capabilities provide the foundation for enterprise cognition: the ability to interpret information, understand dependencies and support decisions across functional boundaries.
The starting point is therefore not what PLM, ERP or AI can remember, but what the enterprise needs to understand to fulfil its mission and make better decisions.
Intelligence Also Means Challenging What We Remember
One risk of organisational memory is assuming that historical knowledge remains valid. A supplier decision may have been justified by cost and availability, a design may have reflected the best technology available, and a manufacturing process may have been optimal under previous operating conditions. None of these conclusions is necessarily permanent. Markets change, regulations evolve, technologies advance, competitors introduce alternatives, and strategic priorities shift.
An enterprise that retrieves yesterday’s reasoning without reassessing its assumptions may simply become more efficient at repeating obsolete decisions. This is where enterprise cognition must move beyond memory towards learning, adaptation and the ability to unlearn.
Unlearning does not mean deleting historical evidence or rewriting previous decisions. It means recognising when assumptions no longer apply, challenging established conclusions, and superseding knowledge while maintaining the traceability required for accountability. Historical evidence and current decision guidance must remain distinguishable.
AI can support this process by identifying contradictions, revealing dependencies and evaluating alternatives across functions and systems. However, accountable business owners must retain authority over the interpretation of evidence, the validity of decisions and the actions that follow. A genuinely intelligent organisation should understand not only why it made a decision, but whether it would still make that decision today.
From Cognitive PLM to the Enterprise Brain
Memory is one cognitive capability, but it is not intelligence itself. The enterprise brain represents the broader organisational ability to interpret information, reason across constraints, learn from experience, challenge assumptions and coordinate decisions. It is not another software platform, nor a competition between PLM, ERP, MES or other enterprise applications. Rather, it extends cognitive PLM thinking across the enterprise.
AI could significantly enable this evolution. Enterprise software vendors are embedding AI into their platforms, improving information retrieval, automation and decision support within their respective environments. These capabilities create value, but when confined to individual applications, they may also reinforce existing information boundaries.
Cross-platform AI introduces a different possibility: intelligence that can reason across systems of record rather than remaining constrained by the application in which it operates. This could change how organisations discover knowledge, establish contextual relationships, coordinate workflows and support decisions across engineering, manufacturing, operations and commercial functions.
It also raises important questions about the future of enterprise software. Where should intelligence reside? How should applications expose information and capabilities beyond their own boundaries? Who governs AI-generated relationships and cross-platform actions? How can enterprises preserve authority, security and accountability when reasoning spans multiple systems and technology providers?
These questions do not diminish the importance of existing enterprise applications. Their structured information, transactional integrity and domain governance remain essential. Rather, they suggest that the boundaries of enterprise intelligence may increasingly differ from those of enterprise software.
For OEMs, the opportunity is to connect engineering intent with manufacturing reality, supply-chain constraints, commercial priorities and regulatory obligations. Success should ultimately be measured through better decisions and business outcomes: faster innovation, stronger quality, more efficient operations, reduced risk and improved profitability. These contribute directly to return on innovation and return on operations.
Product memory has an important role in preserving and making enterprise knowledge accessible. Yet its value depends on understanding which decisions require context, which information must remain traceable and when previous conclusions should be challenged.
The future is not about enabling enterprises to remember everything about their products. It is about preserving what matters, tracing what is required, discovering what was previously disconnected and applying that knowledge to make better decisions as the business evolves.
That is where product memory contributes to enterprise intelligence.
What are your thoughts?
Disclaimer: articles and thoughts published on v+d do not necessarily represent the views of the company, but solely the views or interpretations of the author(s); reviews, insights and mentions of publications, products, or services do neither constitute endorsement, nor recommendations for purchase or adoption.
About the Author
