Overview

Producer metadata and the represented concept document.

Concept identity

design-knowledge/dissonance-dialogue-recall-dp2

Producer label: DP2
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-dp2.md

design-principledissonance-dialogue-recallerp-integrationrecall-communicationtokenizationtraceability

Design principle 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.

Source paper

This design principle 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).

Addresses

Design requirement DR2: Complete recall traceability path

Implemented by

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

02

Linked concepts

Concepts connected by incoming or outgoing native Markdown links.

Design Feature

Design Feature3

Design Feature

design-knowledge/dissonance-dialogue-recall-df2

DF2 - BC-ERP integration through objects

Integration of enterprise systems with the blockchain through objects (TokenID, contract address, From/To owner, system) recorded in a movement table.

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

Design Feature

design-knowledge/dissonance-dialogue-recall-df3

DF3 - Recall tracing and product-state extension of the token

A standard token interface that traces recalls and extends the product state as the token moves between organizations and customers.

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

Design Feature

design-knowledge/dissonance-dialogue-recall-df7

DF7 - Manufacturer recall-state management

A feature by which manufacturers set and manage recall states (e.g., 'Checked NOT OK') for affected products.

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

Design Requirement

Design Requirement1

Design Requirement

design-knowledge/dissonance-dialogue-recall-dr2

DR2 - Complete recall traceability path

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

design-requirementdissonance-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

03

Relationships

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

Outgoing links

5

Incoming backlinks

4

04

Local graph

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

Knowledge graph

6 of 6 concepts · 17 directed relationships

Concept types

Design PrincipleSeed

DP2 - Multi-enterprise capture and historical owner analysis

Bundle identity

Concept ID: design-knowledge/dissonance-dialogue-recall-dp2
Markdown path: design-knowledge/dissonance-dialogue-recall-dp2.md
Producer label: DP2
Native type: design-principle

Markdown summary

Design principle 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. Source paper This design principle 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). Addresses Design requirement DR2: Complete recall traceability path Implemented by Design feature DF2: BC-ERP integration through objects Design feature DF3: Recall tracing and product-state extension of the token Design…

Raw metadata

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

Show producer frontmatter

{
  "type": "design-principle",
  "title": "DP2 - Multi-enterprise capture and historical owner analysis",
  "description": "Capture multiple enterprise systems and analyze historical owners using blockchain-ERP integration and recall tracing, fostering cross-organizational collaboration in recall processes.",
  "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": "DP2",
  "tags": [
    "dissonance-dialogue-recall",
    "design-principle",
    "recall-communication",
    "erp-integration",
    "traceability",
    "tokenization"
  ],
  "timestamp": "2026-07-16T00:00:00+00:00"
}