Please describe your proposed solution.
<u>Context.</u>
Due to globalisation, supply chains have evolved from traditional linear supply chains to static supply networks and have further evolved into complex interconnected supply networks.
In addition to the structural complexities of contemporary supply chains, recent trends increasingly put pressure on companies to increase their supply chain visibility and to provide supply chain transparency to maintain their competitiveness.
We can think in supply chain transparency as the extent to which supply chain actors disclose information to all stakeholders, including the public, consumers, and investors. Thus, supply chain visibility enables companies to provide supply chain transparency.
For companies, traceability represents the essential prerequisite for enabling supply chain visibility, which in turn represents the prerequisite for providing supply chain transparency. We can think about traceability “as the ability to access any or all information relating to that which is under consideration, throughout its entire life cycle, by means of recorded identifications".
<u>Traceability system.</u>
Interconnected traceability systems map objects through their object-related supply chain events, also referred to as object-related "visibility events"
At the heart of any traceability system is the identification of traceable objects . The GS1 Global Traceability Standard distinguishes between physical and abstract objects also know as digital objects.
-
Physical objects: Which are handled in physical handling steps of an overall business process involving one or more organisations. This includes objects such as products, items, and physical documents.
-
Abstract objects. Refers to digital objects which participate in business processes involving one or more organisations. This includes objects such as digital trade items, digital documents, and electronic certificates.
Traceability systems must map objects in their information world to enable object traceability , the identification number refers to an object and links to the metadata. The metadata contains all the relevant information to describe an object. On a system level, metadata includes data components, which “may be simple real numbers, text strings, vectors of real numbers and other values. Furthermore, traceability systems typically connect objects’ virtual representations via radio frequency identification (RFID) tags or quick response (QR) codes to their physical counterparts.
The traceability of objects requires mapping data related to the occurred supply chain events, also referred to as object-related ‘visibility events’. An object-related supply chain event “is the record of the completion of a specific business process step acting upon one or more objects.
This are the required core supply chain events: Object creation and deletion, object aggregation and disaggregation, object transformation, and object transaction events:
-
Object event: Iniitially link objects to their identifiers (IDs) on a system level . In addition, object events allow the possibility to create a number of objects of the same object class. In addition allow delete objects, which results in these objects not existing on a system level for further events after their deletion.
-
Aggregation/disaggregation event: Create a new identifiable ‘containing’ entity that contains a set of objects. Until their possible disaggregation, aggregated objects, physically and on a system level, occupy the same location at the same time. Consequently, aggregation events include the possibility of disaggregating previously aggregated objects, whereas the ‘containing’ objects become independent objects again, and the ‘containing’ entity dissolves.
-
Transformation event: Transformation events fully or partially consume objects as inputs and produce outputs of new object classes. Like this, objects can ‘transform’ into new objects without experiencing changes regarding their modular composition.
-
Transaction event: Transaction events associate or disassociate objects with business transactions. Therefore, transaction events enable the mapping of objects’ changes in ownership.
<u>Detailed Solution.</u>
This proposal aims to solve the identified problem by developing a blockchain-based traceability architecture prototype, this comes the following primary research question:
- How can a blockchain-based traceability architecture be constructed which meets the general-purpose requirements of dynamic, interconnected supply networks and ensures the end-to-end traceability of object-related supply chain events?
In addition, the following secondary research questions support answering the question above and prove the architecture.
-
What are the limitations of existing blockchain-based traceability solutions described in the literature?
-
What are the architectural requirements for an end-to-end traceability solution for dynamic, interconnected supply networks?
-
How can the architecture’s components be implemented on Cardano blockchain to enable its practical applicability in a blockchain-based traceability solution?
Therefore, the proposal consists of 4 stages:
1) Research: Provides a theoretical knowledge foundation regarding related works in the supply chain, this stage emphasises the research gap to ensure the proposal´s uniqueness by pointing out the limitations of existing blockchain-based traceability architectures.
2) Architecture Development: An architecture describes “the set of structures needed to reason about the system, which comprise software elements, relations among them, and properties of both. This does not include its implementation in code; its design and logic can lead to code that is correct with respect to the specified architecture.
For the development processes, this proposal adopts the architecture development framework from "Software Architecture: A Comprehensive Framework and Guide for Practitioners" book
As is common in software development, architecture development begins with deriving architectural requirements. Requirements “provide the key input to the software architecture design. This proposal derives the architectural requirements from the fundamental supply chain structures, the characteristics of traceability systems, and the available object-related traceability standards.
3) The developed prototype based on the architecture : This proposal aims to develop a ‘basic prototyping’ representing a fully operational software. Therefore, this proposal evaluates the applicability of all architecture components in Cardano and applies a prototypical implementation in an experimental setting to ensure their implementation ability.
4) Testing: In order to evaluate the architecture components, the evaluation must use an example of a supply chain. I did a little consultation on lidonation , I can see that 65 proposals have been approved in catalyst related to agriculture and food. i will contact them and spread the word in the community for projects that want to participate and test the prototype.
Following, the outcomes derived from the proposal, I will highlighting their distinct contributions by addressing the aforementioned research questions and presenting key findings. To conclude, the existing limitations of the architecture will be summarised, and recommendations for future actions will be proposed.