Design Requirement

DR2 - Complete recall traceability path

The system should provide an entire recall traceability path to ensure synchronized communications between multiple organizations.

Design RequirementOpen source resource ↗

Overview

Producer metadata and the represented concept document.

Concept identity

design-knowledge/dissonance-dialogue-recall-dr2

Open concept record

Producer label: DR2
Source paper: From Dissonance to Dialogue: A Token-Based Approach to Bridge the Gap Between Manufacturers and Customers
Timestamp: 2026-07-16T00:00:00+00:00
Bundle path: design-knowledge/dissonance-dialogue-recall-dr2.md

design-requirementdissonance-dialogue-recallerp-integrationrecall-communicationtokenizationtraceability

Design requirement DR2: Complete recall traceability path

The system should provide an entire recall traceability path to ensure synchronized communications between multiple organizations.

Source paper

This design requirement is proposed by From Dissonance to Dialogue: A Token-Based Approach to Bridge the Gap Between Manufacturers and Customers (Norman Pytel, Christian Ziegler, Axel Winkelmann, 2024).

Citations

[1] Norman Pytel, Christian Ziegler, Axel Winkelmann. From Dissonance to Dialogue: A Token-Based Approach to Bridge the Gap Between Manufacturers and Customers. ACM Transactions on Management Information Systems 15(1), Article 3 (2024). https://doi.org/10.1145/3639058 (opens in a new tab) [2] Source document: From Dissonance to Dialogue - A Token-Based Approach.pdf

Linked concepts

Concepts connected by incoming or outgoing native Markdown links.

Design Principle

Design Principle2

Design Principle

design-knowledge/dissonance-dialogue-recall-dp2

DP2 - Multi-enterprise capture and historical owner analysis

Capture multiple enterprise systems and analyze historical owners using blockchain-ERP integration and recall tracing, fostering cross-organizational collaboration in recall processes.

design-principledissonance-dialogue-recallerp-integrationrecall-communication+2

Design Principle

design-knowledge/dissonance-dialogue-recall-dp3

DP3 - Traceability with customer notifications

Enable traceability functions with customer wallet notifications and backward and forward ownership tracing to ensure synchronized communication for all related owners.

design-principledissonance-dialogue-recallerp-integrationrecall-communication+2

Paper

Paper1

Paper

papers/dissonance-dialogue-recall

From Dissonance to Dialogue: A Token-Based Approach to Bridge the Gap Between Manufacturers and Customers

The paper presents a token-based recall-communication system integrating ERP and blockchain, developing six design principles (and supporting design features) that improve recall coordination, traceability and co-value creation between manufacturers and customers.

blockchaindesign-science-researchdissonance-dialogue-recallerp-integration+3

Relationships

Directed links from Markdown. Heading context is displayed as derived metadata, not as a formal OKF predicate.

Outgoing links

From Dissonance to Dialogue: A Token-Based Approach to Bridge the Gap Between Manufacturers and Customers
Paper
Source
DR2 - Complete recall traceability path
Target
From Dissonance to Dialogue: A Token-Based Approach to Bridge the Gap Between Manufacturers and Customers
Link label
From Dissonance to Dialogue: A Token-Based Approach to Bridge the Gap Between Manufacturers and Customers
Status
Resolved
Derived heading context: Source paper

Incoming backlinks

Local graph

One-hop by default, with an optional bounded two-hop view. Nodes are concept files and arrows are Markdown links.

Knowledge graph

4 of 4 concepts · 8 directed relationships

Concept types

Design RequirementSeed

DR2 - Complete recall traceability path

Bundle identity

Concept ID: design-knowledge/dissonance-dialogue-recall-dr2
Markdown path: design-knowledge/dissonance-dialogue-recall-dr2.md
Producer label: DR2
Native type: design-requirement

Markdown summary

Design requirement DR2: Complete recall traceability path The system should provide an entire recall traceability path to ensure synchronized communications between multiple organizations. Source paper This design requirement is proposed by From Dissonance to Dialogue: A Token-Based Approach to Bridge the Gap Between Manufacturers and Customers (Norman Pytel, Christian Ziegler, Axel Winkelmann, 2024). Citations [1] Norman Pytel, Christian Ziegler, Axel Winkelmann. From Dissonance to Dialogue: A Token-Based Approach to Bridge the Gap Between Manufacturers and Customers. ACM Transactions on Management Information Systems 15(1), Article 3 (2024). https://doi.org/10.1145/3639058 [2] Source…

Raw metadata

The complete producer frontmatter, serialized without server paths or runtime data.

Show producer frontmatter

{
  "type": "design-requirement",
  "title": "DR2 - Complete recall traceability path",
  "description": "The system should provide an entire recall traceability path to ensure synchronized communications between multiple organizations.",
  "resource": "https://doi.org/10.1145/3639058",
  "source_paper": "From Dissonance to Dialogue: A Token-Based Approach to Bridge the Gap Between Manufacturers and Customers",
  "label": "DR2",
  "tags": [
    "dissonance-dialogue-recall",
    "design-requirement",
    "recall-communication",
    "erp-integration",
    "traceability",
    "tokenization"
  ],
  "timestamp": "2026-07-16T00:00:00+00:00"
}

Design Requirement

DR2 - Complete recall traceability path

The system should provide an entire recall traceability path to ensure synchronized communications between multiple organizations.

Design RequirementOpen source resource ↗

Overview

Producer metadata and the represented concept document.

Concept identity

design-knowledge/dissonance-dialogue-recall-dr2

Open concept record

Producer label: DR2
Source paper: From Dissonance to Dialogue: A Token-Based Approach to Bridge the Gap Between Manufacturers and Customers
Timestamp: 2026-07-16T00:00:00+00:00
Bundle path: design-knowledge/dissonance-dialogue-recall-dr2.md

design-requirementdissonance-dialogue-recallerp-integrationrecall-communicationtokenizationtraceability

Design requirement DR2: Complete recall traceability path

The system should provide an entire recall traceability path to ensure synchronized communications between multiple organizations.

Source paper

Citations

Linked concepts

Concepts connected by incoming or outgoing native Markdown links.

Design Principle

Design Principle2

Design Principle

design-knowledge/dissonance-dialogue-recall-dp2

DP2 - Multi-enterprise capture and historical owner analysis

Capture multiple enterprise systems and analyze historical owners using blockchain-ERP integration and recall tracing, fostering cross-organizational collaboration in recall processes.

design-principledissonance-dialogue-recallerp-integrationrecall-communication+2

Design Principle

design-knowledge/dissonance-dialogue-recall-dp3

DP3 - Traceability with customer notifications

Enable traceability functions with customer wallet notifications and backward and forward ownership tracing to ensure synchronized communication for all related owners.

design-principledissonance-dialogue-recallerp-integrationrecall-communication+2

Paper

Paper1

Paper

papers/dissonance-dialogue-recall

From Dissonance to Dialogue: A Token-Based Approach to Bridge the Gap Between Manufacturers and Customers

blockchaindesign-science-researchdissonance-dialogue-recallerp-integration+3

Relationships

Directed links from Markdown. Heading context is displayed as derived metadata, not as a formal OKF predicate.

Outgoing links

From Dissonance to Dialogue: A Token-Based Approach to Bridge the Gap Between Manufacturers and Customers
Paper
Source
DR2 - Complete recall traceability path
Target
From Dissonance to Dialogue: A Token-Based Approach to Bridge the Gap Between Manufacturers and Customers
Link label
From Dissonance to Dialogue: A Token-Based Approach to Bridge the Gap Between Manufacturers and Customers
Status
Resolved
Derived heading context: Source paper

Incoming backlinks

Local graph

One-hop by default, with an optional bounded two-hop view. Nodes are concept files and arrows are Markdown links.

Knowledge graph

4 of 4 concepts · 8 directed relationships

Concept types

Design RequirementSeed

DR2 - Complete recall traceability path

Bundle identity

Concept ID: design-knowledge/dissonance-dialogue-recall-dr2
Markdown path: design-knowledge/dissonance-dialogue-recall-dr2.md
Producer label: DR2
Native type: design-requirement

Markdown summary

Raw metadata

The complete producer frontmatter, serialized without server paths or runtime data.

Show producer frontmatter

{
  "type": "design-requirement",
  "title": "DR2 - Complete recall traceability path",
  "description": "The system should provide an entire recall traceability path to ensure synchronized communications between multiple organizations.",
  "resource": "https://doi.org/10.1145/3639058",
  "source_paper": "From Dissonance to Dialogue: A Token-Based Approach to Bridge the Gap Between Manufacturers and Customers",
  "label": "DR2",
  "tags": [
    "dissonance-dialogue-recall",
    "design-requirement",
    "recall-communication",
    "erp-integration",
    "traceability",
    "tokenization"
  ],
  "timestamp": "2026-07-16T00:00:00+00:00"
}