DSR Knowledge LibraryReusable design knowledge and grounded research support
HomeLibraryChatChat accessGive feedback ↗

DSR Knowledge Library

Research prototype · Native Open Knowledge Format

LibraryChatChat accessMethod and limitationsPrivacy noteEvaluation survey ↗
Library/DP3 - Traceability with customer notifications

Design Principle

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 PrincipleOpen source resource ↗
OverviewLinked conceptsRelationshipsGraphRaw metadata

01

Overview

Producer metadata and the represented concept document.

Concept identity

design-knowledge/dissonance-dialogue-recall-dp3
Open concept record
Producer label
DP3
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-dp3.md
design-principledissonance-dialogue-recallerp-integrationrecall-communicationtokenizationtraceability

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

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
  • Design requirement DR3: Intuitive product- and health-state communication

Implemented by

  • Design feature DF1: Customer wallet notification for recall states
  • Design feature DF8: Backward and forward ownership tracing

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 Feature2
Design Feature
design-knowledge/dissonance-dialogue-recall-df1

DF1 - Customer wallet notification for recall states

Customers log in with an Ethereum wallet and receive notifications about recall states of products they own.

design-featuredissonance-dialogue-recallerp-integrationrecall-communication+2
Design Feature
design-knowledge/dissonance-dialogue-recall-df8

DF8 - Backward and forward ownership tracing

Smart-contract token-ownership tracing history enabling backward and forward tracing of previous manufacturers and owners for the recall process.

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

Design Requirement

Design Requirement2
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
Design Requirement
design-knowledge/dissonance-dialogue-recall-dr3

DR3 - Intuitive product- and health-state communication

The system should allow intuitive communication of product- and customer-health states.

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

    DF1 - Customer wallet notification for recall states

    Design Feature
    Source
    DP3 - Traceability with customer notifications
    Target
    DF1 - Customer wallet notification for recall states
    Link label
    Design feature DF1: Customer wallet notification for recall states
    Status
    Resolved

    Derived heading context: Implemented by

  • →

    DF8 - Backward and forward ownership tracing

    Design Feature
    Source
    DP3 - Traceability with customer notifications
    Target
    DF8 - Backward and forward ownership tracing
    Link label
    Design feature DF8: Backward and forward ownership tracing
    Status
    Resolved

    Derived heading context: Implemented by

  • →

    DR2 - Complete recall traceability path

    Design Requirement
    Source
    DP3 - Traceability with customer notifications
    Target
    DR2 - Complete recall traceability path
    Link label
    Design requirement DR2: Complete recall traceability path
    Status
    Resolved

    Derived heading context: Addresses

  • →

    DR3 - Intuitive product- and health-state communication

    Design Requirement
    Source
    DP3 - Traceability with customer notifications
    Target
    DR3 - Intuitive product- and health-state communication
    Link label
    Design requirement DR3: Intuitive product- and health-state communication
    Status
    Resolved

    Derived heading context: Addresses

  • →

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

    Paper
    Source
    DP3 - Traceability with customer notifications
    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

3
  • ←

    DF1 - Customer wallet notification for recall states

    Design Feature
    Source
    DF1 - Customer wallet notification for recall states
    Target
    DP3 - Traceability with customer notifications
    Link label
    Design principle DP3: Traceability with customer notifications
    Status
    Resolved

    Derived heading context: Implements

  • ←

    DF8 - Backward and forward ownership tracing

    Design Feature
    Source
    DF8 - Backward and forward ownership tracing
    Target
    DP3 - Traceability with customer notifications
    Link label
    Design principle DP3: Traceability with customer notifications
    Status
    Resolved

    Derived heading context: Implements

  • ←

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

    Paper
    Source
    From Dissonance to Dialogue: A Token-Based Approach to Bridge the Gap Between Manufacturers and Customers
    Target
    DP3 - Traceability with customer notifications
    Link label
    Design principle DP3: Traceability with customer notifications
    Status
    Resolved

    Derived heading context: Design knowledge

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

Concept types
Press enter or space to select a node.You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.
Design PrincipleSeed

DP3 - Traceability with customer notifications

Bundle identity

Concept ID
design-knowledge/dissonance-dialogue-recall-dp3
Markdown path
design-knowledge/dissonance-dialogue-recall-dp3.md
Producer label
DP3
Native type
design-principle

Markdown summary

Design principle 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. 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 Design requirement DR3: Intuitive product- and health-state communication Implemented by Design feature DF1: Customer wallet notification for recall states Design feature DF8: Backward…

Tags

  • design-principle
  • dissonance-dialogue-recall
  • erp-integration
  • recall-communication
  • tokenization
  • traceability
This bounded preview contains only client-safe native OKF metadata.

05

Raw metadata

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

Show producer frontmatter+
{
  "type": "design-principle",
  "title": "DP3 - Traceability with customer notifications",
  "description": "Enable traceability functions with customer wallet notifications and backward and forward ownership tracing to ensure synchronized communication for all related owners.",
  "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": "DP3",
  "tags": [
    "dissonance-dialogue-recall",
    "design-principle",
    "recall-communication",
    "erp-integration",
    "traceability",
    "tokenization"
  ],
  "timestamp": "2026-07-16T00:00:00+00:00"
}