DSR Knowledge LibraryReusable design knowledge and grounded research support
HomeLibraryChatGive feedback โ†—

DSR Knowledge Library

Research prototype ยท Native Open Knowledge Format

LibraryChatImprintPrivacyEvaluation survey โ†—
Library/Papers/From Dissonance to Dialogue: A Token-Based Approach to Bridge the Gap Between Manufacturers and Customers

Research paper

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.

Paper
OverviewDSR gridPaper design mapDesign knowledgePublication metadata

01

Overview

Publication metadata and narrative from the current library record.

Authors
Norman Pytel, Christian Ziegler, Axel Winkelmann
Year
2024
Venue
ACM Transactions on Management Information Systems 15(1), Article 3 (2024)
Methodology
Design science research; three artifact iterations; qualitative evaluation with 14 industry experts.
DOI
10.1145/3639058
Design knowledge
View design knowledge on GitHub
blockchaindesign-science-researchdissonance-dialogue-recallerp-integrationrecall-communicationtokenizationtraceability

Summary

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.

Artifact

A token-based recall-communication system integrating ERP systems with blockchain.

Methodology

Design science research; three artifact iterations; qualitative evaluation with 14 industry experts.

02

DSR grid

Six dimensions represented in the current paper record.

01

Problem description

Recall communication and cooperation between manufacturers and customers is poor, as internal ERP-based traceability rarely extends past product delivery.

02

Input knowledge

Socio-technical systems thinking; ERP traceability; the ANDON visual-management concept; token standards; the anatomy of a design principle (Gregor et al. 2020).

03

Research process

Design science research over three artifact iterations, with a qualitative evaluation involving fourteen industry experts.

04

Key concepts

Blockchain, recall communication, enterprise resource planning system, information system design.

05

Solution description

A token-based recall-communication system integrating ERP systems with a permissionless blockchain. Solution-space representation: Instantiation plus a design theory (requirements, principles and features).

06

Output knowledge

Five design requirements, six design principles and eight design features for interoperable recall communication.

03

Paper design map

The default semantic design map canonicalizes stored design relationships; Raw links retains the complete technical Markdown-link view.

Design-knowledge map

19 stored concepts / 28 canonical semantic relationships

Concept types
Design Requirements
Design Principles
Design Features
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.

04

Design knowledge

Directly linked concepts, grouped by their represented design-knowledge category.

8 Design Features

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-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
design-knowledge/dissonance-dialogue-recall-df4

DF4 - Interorganizational BC-based data storage

Inter-organizational blockchain-based data storage shared between manufacturers and customers.

design-featuredissonance-dialogue-recallerp-integrationrecall-communication+2
design-knowledge/dissonance-dialogue-recall-df5

DF5 - Customer product-defect announcement

A feature allowing customers to announce product defects and voluntarily report their health state.

design-featuredissonance-dialogue-recallerp-integrationrecall-communication+2
design-knowledge/dissonance-dialogue-recall-df6

DF6 - Manufacturer product-defect announcement

A feature allowing manufacturers to announce a defective product, initiating a forward recall that notifies all customers holding the token.

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

6 Design Principles

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-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
design-knowledge/dissonance-dialogue-recall-dp3

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-principledissonance-dialogue-recallerp-integrationrecall-communication+2
design-knowledge/dissonance-dialogue-recall-dp4

DP4 - Interoperability across EVM-supported applications

Provide interoperability between EVM-supported software applications using recall tracing across organizational borders.

design-principledissonance-dialogue-recallerp-integrationrecall-communication+2
design-knowledge/dissonance-dialogue-recall-dp5

DP5 - Customer participation in recall information

Implement mechanisms that allow customers to receive recall information and announce product defects, promoting active customer participation.

design-principledissonance-dialogue-recallerp-integrationrecall-communication+2
design-knowledge/dissonance-dialogue-recall-dp6

DP6 - Co-value creation between manufacturers and customers

Foster co-value creation procedures between manufacturers and customers using inter-organizational data storage, product-defect announcements, recall-state management and ownership tracing.

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

5 Design Requirements

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
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-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
design-knowledge/dissonance-dialogue-recall-dr4

DR4 - Interoperability with permissionless blockchain

The system should allow interoperability between enterprise systems and permissionless blockchain.

design-requirementdissonance-dialogue-recallerp-integrationrecall-communication+2
design-knowledge/dissonance-dialogue-recall-dr5

DR5 - Co-value creation with private customers

The system should allow co-value creation procedures between manufacturers and private customers.

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

05

Publication metadata

Additional metadata represented in the current library record.

Show additional metadata+
{
  "type": "paper",
  "title": "From Dissonance to Dialogue: A Token-Based Approach to Bridge the Gap Between Manufacturers and Customers",
  "description": "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.",
  "resource": "https://doi.org/10.1145/3639058",
  "authors": "Norman Pytel, Christian Ziegler, Axel Winkelmann",
  "year": 2024,
  "venue": "ACM Transactions on Management Information Systems 15(1), Article 3 (2024)",
  "methodology": "Design science research; three artifact iterations; qualitative evaluation with 14 industry experts.",
  "dsr_grid": true,
  "dsr_solution_space": "Instantiation plus a design theory (requirements, principles and features).",
  "tags": [
    "dissonance-dialogue-recall",
    "recall-communication",
    "erp-integration",
    "traceability",
    "tokenization",
    "design-science-research",
    "blockchain"
  ]
}