Table 2

BC system configuration

Feeding/ReadingOptions and issues
FeedingData collected and uploaded manually, prone to unintentional human errors, intentional dishonest behaviours and delays (Galvez et al., 2018; Azzi et al., 2019; Creydt and Fischer, 2019; Kamble et al., 2019; Kamilaris et al., 2019; Montecchi et al., 2019; Schmidt and Wagner, 2019; van Hoek, 2019; Zelbst et al., 2019; Bumblauskas et al., 2020). Complementary measures are
  1. AI to cross-check data (Kshetri, 2018; Montecchi et al., 2019; van Hoek, 2019; Bumblauskas et al., 2020; Roeck et al., 2020)

  2. Neutral third-party bodies to verify data quality (Creydt and Fischer, 2019)

Data automatically captured and uploaded on BC by IoT sensors, lowering the risk of input error, unethical behaviours and delays (Azzi et al., 2019; Creydt and Fischer, 2019; Kamble et al., 2019; Lo et al., 2019; Zelbst et al., 2019; Bumblauskas et al., 2020)
ReadingConnection between physical products and related information on BC through: common tagging techniques (barcodes, serial numbers, QR codes, RFID) vulnerable to cloning (Azzi et al., 2019; Lo et al., 2019), or more sophisticated tagging techniques – such as NFC with data encryption – that prevent cloning (Alzahrani and Bulusu, 2018, 2019)
Communication to customers: information can be read through websites or mobile applications (Creydt and Fischer, 2019; Montecchi et al., 2019)
Information presented to customers can be stored off-chain on a centralized server (Singhal et al., 2018). Customers can access the associated BC transaction (Montecchi et al., 2019)

or Create an Account

Close Modal
Close Modal