Design Requirement

R5 - Delivery history integrity and traceability

A solution must provide delivery history integrity and traceability.

Overview

Producer metadata and the represented concept document.

Concept identity

design-knowledge/decentralized-procurement-logistics-dr5

Open concept record

Producer label: R5
Source paper: Decentralized Procurement Mechanisms for Efficient Logistics Services Mapping - a Design Science Research Approach
Timestamp: 2026-08-08T00:00:00+00:00
Bundle path: design-knowledge/decentralized-procurement-logistics-dr5.md

decentralized-procurement-logisticsdesign-requirementlogisticsprocurementsmart-contractssupply-chain

Design requirement R5: Delivery history integrity and traceability

A solution must provide delivery history integrity and traceability.

Source paper

This design requirement is proposed by Decentralized Procurement Mechanisms for Efficient Logistics Services Mapping - a Design Science Research Approach (Tiphaine Henry, Roman Beck, Nassim Laga, Walid Gaaloul, Shenle Pan, 2022).

Addresses

Design objective P3: Allocation integrity - The paper states "integrity in terms of delivery history and protocol should be considered (cf R5)."

Linked concepts

Concepts connected by incoming or outgoing native Markdown links.

1 Design Objective

design-knowledge/decentralized-procurement-logistics-do3

P3 - Allocation integrity

Allocation integrity should be considered, be it for the allocation process, the record of service rates, and the management of CMR.

decentralized-procurement-logisticsdesign-objectivelogisticsprocurement+2

1 Paper

papers/decentralized-procurement-logistics

Decentralized Procurement Mechanisms for Efficient Logistics Services Mapping - a Design Science Research Approach

The paper designs, implements and evaluates a decentralized blockchain-based logistics procurement system that addresses the carrier-shipper allocation problem, deriving five design requirements, three artifact (design) objectives, and three nascent design principles - understandability, automation and metrics privacy - for decentralized procurement mechanisms.

blockchaindecentralized-procurement-logisticsdesign-science-researchlogistics+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

3 of 3 concepts · 6 directed relationships

Concept types

Raw metadata

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

Show producer frontmatter

{
  "type": "design-requirement",
  "title": "R5 - Delivery history integrity and traceability",
  "description": "A solution must provide delivery history integrity and traceability.",
  "resource": "https://hdl.handle.net/10125/79952",
  "source_paper": "Decentralized Procurement Mechanisms for Efficient Logistics Services Mapping - a Design Science Research Approach",
  "label": "R5",
  "tags": [
    "decentralized-procurement-logistics",
    "design-requirement",
    "logistics",
    "procurement",
    "smart-contracts",
    "supply-chain"
  ]
}

Design Requirement

R5 - Delivery history integrity and traceability

A solution must provide delivery history integrity and traceability.

Overview

Producer metadata and the represented concept document.

Concept identity

design-knowledge/decentralized-procurement-logistics-dr5

Open concept record

Producer label: R5
Source paper: Decentralized Procurement Mechanisms for Efficient Logistics Services Mapping - a Design Science Research Approach
Timestamp: 2026-08-08T00:00:00+00:00
Bundle path: design-knowledge/decentralized-procurement-logistics-dr5.md

decentralized-procurement-logisticsdesign-requirementlogisticsprocurementsmart-contractssupply-chain

Design requirement R5: Delivery history integrity and traceability

A solution must provide delivery history integrity and traceability.

Source paper

Addresses

Design objective P3: Allocation integrity - The paper states "integrity in terms of delivery history and protocol should be considered (cf R5)."

Linked concepts

Concepts connected by incoming or outgoing native Markdown links.

1 Design Objective

design-knowledge/decentralized-procurement-logistics-do3

P3 - Allocation integrity

Allocation integrity should be considered, be it for the allocation process, the record of service rates, and the management of CMR.

decentralized-procurement-logisticsdesign-objectivelogisticsprocurement+2

1 Paper

papers/decentralized-procurement-logistics

Decentralized Procurement Mechanisms for Efficient Logistics Services Mapping - a Design Science Research Approach

blockchaindecentralized-procurement-logisticsdesign-science-researchlogistics+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

3 of 3 concepts · 6 directed relationships

Concept types

Raw metadata

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

Show producer frontmatter

{
  "type": "design-requirement",
  "title": "R5 - Delivery history integrity and traceability",
  "description": "A solution must provide delivery history integrity and traceability.",
  "resource": "https://hdl.handle.net/10125/79952",
  "source_paper": "Decentralized Procurement Mechanisms for Efficient Logistics Services Mapping - a Design Science Research Approach",
  "label": "R5",
  "tags": [
    "decentralized-procurement-logistics",
    "design-requirement",
    "logistics",
    "procurement",
    "smart-contracts",
    "supply-chain"
  ]
}