Skip to content

Implementation guide

Jump to bottom
savicsava edited this page Jul 3, 2018 · 17 revisions

For more information please take a look at:

Purpose of this guide

This guide illustrates how to connect ERP system of one entity and the supply chain made of many entities to OriginTrail protocol. The primary focus is to elaborate whole implementation process based on best practice in several implementations of the pilots for Alpha version of the OriginTrail Distributed Network (ODN). Target audience for this text are solution providers that are going to implement OriginTrail protocol. Data creators (business entities that will use protocol on top of their ERP) are also welcome to review this guide to get deeper insight of whole process. This guide will be updated regularly. OriginTrail business development team and tech team are actively working on transfer of knowledge to third party companies and individuals so they can successfully fit into the stakeholder rolls defined below. One of the main long-term goals is that whole implementation process is executed without OriginTrail as active participant where solutions providers and developers will be compensated for their services to data creators and data consumers.

Stakeholders in implementation process

OriginTrail (OT) is creator of OriginTrail protocol. Our main focus is to develop and improve protocol as our main product. Also, OriginTrail is creating the Trace Alliance - a collaboration partnership hub connecting businesses, startups, academics, business leaders and technology vendors with supply chain subject matter experts.

Data creators (DC) are business that are going to utilize protocol by integrating their ERP with ODN. Data stored on ODN is foundation for various supply chain business process that involve multiple business entities (that can also be data creators).

Data consumers (CN) are entities that are going to utilize the data stored on ODN. That can be data creators also, but it is mainly considered that data consumers are users outside supply chain that are consuming (using) the data through decentralized Applications (dApps).

Service providers (SP) are business oriented multidisciplinary teams that are working on integration of OriginTrail protocol and data source for data creators (their ERPs). One team usually consists of consultants, developers, project managers, business analysts, testers… Their main focus is to integrate data consumers and ODN. The end result is getting their data to ODN. If data consumers have their own qualified resources (in-house IT department), they can also be service providers.

Developers (DE) are tech savvy enthusiasts that are working on improvement of the protocol and creation of dApps. Their main role is to utilize data on ODN and make it usable for data consumers. Service providers can also have this role if they have interest and knowledge.

Implementation milestones

The OriginTrail team has performed several pilots in the role of a service provider and developer. Based on the experiences we have gained so far we have identified this crucial milestones for a successful implementation. Next to each milestone is stakeholder that is involved in that phase. Each milestone is elaborated on the separate page.

  1. Reading and evaluating the OriginTrail documentation. Understanding the protocol and defining the scope of the project. DC,SP,DE
  2. Assembling the team that will be involved in the project. DC,SP
  3. Analyzing the implementation kit and the technical requirements. DC,SP,DE
  4. Agreeing with supply chain entities about conducting the project based on the OriginTrail protocol. DC
  5. Deciding on how to conduct the project implementation (choosing the service provider). DC
  6. Defining the use cases (one as a primary for the prototype). DC,SP
  7. Defining the process flow and writing the functional requirements documentation. DC,SP
  8. Defining the data structure of the XML file that will be used in the ODN. SP
  9. Creating XML exporters and web service call from the ERP. SP
  10. Setting up nodes. SP,DE
  11. Data synchronization on the ODN for each involved entity of the supply chain. DC,SP
  12. Testing the consensus check and other ODN features. DC,SP
  13. Evaluating the prototype. DC
  14. Creating dApps that will read and process the data from the ODN. DE
  15. Final testing and evaluation. DC,DE
  16. Deployment. DE
  17. Expansion to other use cases. DC,SP,DE
Clone this wiki locally