Design Feature

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 FeatureOpen source resource ↗

Overview

Producer metadata and the represented concept document.

Concept identity

design-knowledge/dissonance-dialogue-recall-df2

Open concept record

Producer label: DF2
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-df2.md

design-featuredissonance-dialogue-recallerp-integrationrecall-communicationtokenizationtraceability

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

Source paper

This design feature is a technology-specific realization 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).

Implements

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

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

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

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 · 10 directed relationships

Concept types

Design FeatureSeed

DF2 - BC-ERP integration through objects

Bundle identity

Concept ID: design-knowledge/dissonance-dialogue-recall-df2
Markdown path: design-knowledge/dissonance-dialogue-recall-df2.md
Producer label: DF2
Native type: design-feature

Markdown summary

Design feature 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. Source paper This design feature is a technology-specific realization 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). Implements Design principle DP1: ERP integration by extending data models Design principle DP2: Multi-enterprise capture and historical owner analysis Citations [1] Norman Pytel, Christian Ziegler, Axel Winkelmann. From Dissonance to Dialogue: A…

Raw metadata

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

Show producer frontmatter

{
  "type": "design-feature",
  "title": "DF2 - BC-ERP integration through objects",
  "description": "Integration of enterprise systems with the blockchain through objects (TokenID, contract address, From/To owner, system) recorded in a movement table.",
  "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": "DF2",
  "tags": [
    "dissonance-dialogue-recall",
    "design-feature",
    "recall-communication",
    "erp-integration",
    "traceability",
    "tokenization"
  ],
  "timestamp": "2026-07-16T00:00:00+00:00"
}

Design Feature

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 FeatureOpen source resource ↗

Overview

Producer metadata and the represented concept document.

Concept identity

design-knowledge/dissonance-dialogue-recall-df2

Open concept record

Producer label: DF2
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-df2.md

design-featuredissonance-dialogue-recallerp-integrationrecall-communicationtokenizationtraceability

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

Source paper

Implements

Citations

Linked concepts

Concepts connected by incoming or outgoing native Markdown links.

Design Principle

Design Principle2

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

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

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

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 · 10 directed relationships

Concept types

Design FeatureSeed

DF2 - BC-ERP integration through objects

Bundle identity

Concept ID: design-knowledge/dissonance-dialogue-recall-df2
Markdown path: design-knowledge/dissonance-dialogue-recall-df2.md
Producer label: DF2
Native type: design-feature

Markdown summary

Raw metadata

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

Show producer frontmatter

{
  "type": "design-feature",
  "title": "DF2 - BC-ERP integration through objects",
  "description": "Integration of enterprise systems with the blockchain through objects (TokenID, contract address, From/To owner, system) recorded in a movement table.",
  "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": "DF2",
  "tags": [
    "dissonance-dialogue-recall",
    "design-feature",
    "recall-communication",
    "erp-integration",
    "traceability",
    "tokenization"
  ],
  "timestamp": "2026-07-16T00:00:00+00:00"
}