Design Principle

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.

Overview

Producer metadata and the represented concept document.

Concept identity

design-knowledge/dissonance-dialogue-recall-dp1

Open concept record

Producer label: DP1
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-dp1.md

design-principledissonance-dialogue-recallerp-integrationrecall-communicationtokenizationtraceability

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

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

Implemented by

Linked concepts

Concepts connected by incoming or outgoing native Markdown links.

2 Design Features

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

1 Design Requirement

design-knowledge/dissonance-dialogue-recall-dr1

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-requirementdissonance-dialogue-recallerp-integrationrecall-communication+2

1 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

5 of 5 concepts · 13 directed relationships

Concept types

Raw metadata

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

Show producer frontmatter

{
  "type": "design-principle",
  "title": "DP1 - ERP integration by extending data models",
  "description": "Integrate any ERP system by extending existing data models of required blockchain objects and recall tracing, promoting seamless communication between ERP and blockchain systems.",
  "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": "DP1",
  "tags": [
    "dissonance-dialogue-recall",
    "design-principle",
    "recall-communication",
    "erp-integration",
    "traceability",
    "tokenization"
  ]
}