WZL x GCX x IOTA — Status Report 03
The full article was originally published by Daniel Trauth on Medium. Read the full article here.
This PoC is about an industrial fineblanking machine type XFT 2500 speed from Feintool AG. It ist used for the mass production of safety-critical components, such as brake carrier plates or belt straps. In the first article we achieved to extract selected data from the machine, converted it from analog to digital, stored it in a .json-file and uploaded it into the official testnet. The following video shows you the machine and the process, just in case you missed it in Status Report 01.
Retrospective 02: Premiere of the Frontend
Premiere of our #WZL x #GCX x #IOTA Web-Frontend to decrypt the #Tangle data during the visit of the #IILA from #AachenerNachrichten. Still work in progress, but we are getting closer. Stay tuned. @grandcentrix @IENofficial @an_topnews @rwth_wzl @RWTH https://t.co/a1gwcGoaCo
Focus of Status Report 03
This article shows the current status of the WZL x GCX x IOTA Web-Frontend. The Frontend ensures access to the tangle and makes it possible to check data integrity for each workpiece data set.
The WZL x GCX x IOTA Web-Frontend
Let’s assume a machine economy in which there are reasons to believe that a machine, a B2B customer or a B2C customer wants access to the production data of one or more safety-critical components. Access to only one data record is conceivable, since IOTA allows feeless micropayments. Let us also assume that the manufacturer operates worldwide, i.e. has several locations and can produce different parts.
The requirements for the WZL x GCX x IOTA Web-Frontend were derived from this scenario.
- A diagram should show the utilization of the production. Even if this was not the intrinsic motivation of IOTA, it is still easily possible: assuming the number of transactions per second (tps) is higher than the number of workpieces per second (wps).
- Another diagram is intended to show how production capacity utilization is distributed across different locations.
- Using a browser it should be possible to find all components using a combination of Tangle x AWS DynamoDB. The use of an additional database like AWS DynamoDB is foreseen, since it is planned that a database entry will exceed 1.5 kB per workpiece in the future.
- For each Workpiece ID, the corresponding data record must be extracted from the tangle and the database. The integrity of the data must be ensured by a signature which has to be stored in the tamper-proof tangle.
- Based on this, it should be possible to view the component information only by making a micropayment (work in progress).
- Based on a Finite Element Analysis, it should also be possible to create a digital twin for each components information. For this purpose, an additional M2M connection to a finite element (FE) server is automatically established when the user requests and pays for it (work in progress).