Design Requirement

DR1 - Straightforward ERP mapping with essential on-chain data

The enterprise systems should be mapped straightforwardly, and only essential recall-communication data must be stored in the blockchain.

Design RequirementOpen source resource ↗

Overview

Producer metadata and the represented concept document.

Concept identity

design-knowledge/dissonance-dialogue-recall-dr1

Open concept record

Producer label: DR1
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-dr1.md

design-requirementdissonance-dialogue-recallerp-integrationrecall-communicationtokenizationtraceability

Design requirement DR1: Straightforward ERP mapping with essential on-chain data

The enterprise systems should be mapped straightforwardly, and only essential recall-communication data must be stored in the blockchain.

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 Principle1

Design Principle

design-knowledge/dissonance-dialogue-recall-dp1

DP1 - ERP integration by extending data models

Integrate any ERP system by extending existing data models of required blockchain objects and recall tracing, promoting seamless communication between ERP and blockchain systems.

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
DR1 - Straightforward ERP mapping with essential on-chain data
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

3 of 3 concepts · 5 directed relationships

Concept types

Design RequirementSeed

DR1 - Straightforward ERP mapping with essential on-chain data

Bundle identity

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

Markdown summary

Design requirement DR1: Straightforward ERP mapping with essential on-chain data The enterprise systems should be mapped straightforwardly, and only essential recall-communication data must be stored in the blockchain. 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).…

Raw metadata

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

Show producer frontmatter

{
  "type": "design-requirement",
  "title": "DR1 - Straightforward ERP mapping with essential on-chain data",
  "description": "The enterprise systems should be mapped straightforwardly, and only essential recall-communication data must be stored in the blockchain.",
  "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": "DR1",
  "tags": [
    "dissonance-dialogue-recall",
    "design-requirement",
    "recall-communication",
    "erp-integration",
    "traceability",
    "tokenization"
  ],
  "timestamp": "2026-07-16T00:00:00+00:00"
}

Design Requirement

DR1 - Straightforward ERP mapping with essential on-chain data

The enterprise systems should be mapped straightforwardly, and only essential recall-communication data must be stored in the blockchain.

Design RequirementOpen source resource ↗

Overview

Producer metadata and the represented concept document.

Concept identity

design-knowledge/dissonance-dialogue-recall-dr1

Open concept record

Producer label: DR1
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-dr1.md

design-requirementdissonance-dialogue-recallerp-integrationrecall-communicationtokenizationtraceability

Design requirement DR1: Straightforward ERP mapping with essential on-chain data

The enterprise systems should be mapped straightforwardly, and only essential recall-communication data must be stored in the blockchain.

Source paper

Citations

Linked concepts

Concepts connected by incoming or outgoing native Markdown links.

Design Principle

Design Principle1

Design Principle

design-knowledge/dissonance-dialogue-recall-dp1

DP1 - ERP integration by extending data models

Integrate any ERP system by extending existing data models of required blockchain objects and recall tracing, promoting seamless communication between ERP and blockchain systems.

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
DR1 - Straightforward ERP mapping with essential on-chain data
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

3 of 3 concepts · 5 directed relationships

Concept types

Design RequirementSeed

DR1 - Straightforward ERP mapping with essential on-chain data

Bundle identity

Concept ID: design-knowledge/dissonance-dialogue-recall-dr1
Markdown path: design-knowledge/dissonance-dialogue-recall-dr1.md
Producer label: DR1
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": "DR1 - Straightforward ERP mapping with essential on-chain data",
  "description": "The enterprise systems should be mapped straightforwardly, and only essential recall-communication data must be stored in the blockchain.",
  "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": "DR1",
  "tags": [
    "dissonance-dialogue-recall",
    "design-requirement",
    "recall-communication",
    "erp-integration",
    "traceability",
    "tokenization"
  ],
  "timestamp": "2026-07-16T00:00:00+00:00"
}