An IIoT-Based Approach to the Integrated Management of Machinery in the Construction Industry

Abstract

In recent years, considerable advances in connecting industrial equipment to the Internet allowed a higher level of operational efficiency, productivity, and automation. Nevertheless, the construction industry still presents challenging requirements, like long-distance wireless communication, interconnection of out-ofcoverage areas, constant mobility of machinery, and support for legacy and proprietary systems. All these requirements pose different challenges when compared with traditional smart factory Industry 4.0 solutions. This paper discusses some of the current key questions regarding fleet management in the construction industry, identifies requirements for heavy-duty machinery, and proposes an Industrial Internet of Things (IIoT)-based solution for the integrated monitoring of such machinery. Also, it proposes and presents an open, innovative solution for the integrated management of non-standardized civil construction vehicle technologies. The developed prototype uses the J1939 protocol to collect machinery status and Long-Range Wide Area Network (LoRaWAN) to communicate the monitored data. The solution was assessed at the construction site of the new port of Sines in Portugal. A detailed description of the proposed system is provided, along with information on trials and evaluation results regarding its performance. Additionally, the paper provides insights into open issues and challenges in this field and how our solution can contribute to overcoming them.

QoS-Aware Federated Crosschain-Based Model-Driven Reference Architecture for IIoT Sensor Networks in Distributed Manufacturing

“…This section provides a subjective literature survey of blockchain-based manufacturing factory solutions relevant to our research objectives. With respect to the popularity of blockchain-based manufacturing factory solutions, we considered blockchain-based patents [23], [24], [25], [26], [27], [28] and literature [29], [30], [31], [32], [33], [34], [35], [36], [37], [38], [39], [40], [41], [42], [43], [44], [45], [46], [47], [48], [49], [50], [51], [52]. 1 Our survey matrix was "studying the blockchain-based manufacturing factory solutions for their top-down software architectural initiatives that facilitated hierarchically federated geodistribution while possessing QoS demands beyond default security and privacy."…”

“…G 1 did not make minimal provision for AMP [23], [24], [25]. G 2 had ad hoc SAs without reasoning [29], [30], [31], [32], [33], [34], [35], [36], [37], [38], [39], [40], [41], [42], [43], [44], [45], [46], [47], [48], [49], [50]. Finally, G 3 possessed a minimal AMP with reasoning [27], [28], [51], [52] and our work.…”

“…In summary, 80% of the works investigated used the onchain technique [23], [24], [25], [32], [33], [34], [35], [36], [37], [38], [39], [40], [41], [42], [43], [44], [45], [46], [47], [48], [49], [50], [51], [52]. Their objectives include improving beyond default QoS requirements, such as privacy and security, and supporting DSM operations.…”

“…Blockchain is one of the most significant techniques available for addressing integrity concerns in the IoT domain, and blockchain-based solutions for smart industry are abundant [23], [24], [25], [26], [27], [28], [29], [30], [31], [32], [33], [34], [35], [36], [37], [38], [39], [40], [41], [42], [43], [44], [45], [46], [47], [48], [49], [50], [51], [52]. According to our survey of blockchain-based DSM solutions, 80% of the solutions are based on the on-chain approach and its variants for their key functional requirements, such as network commissioning and transactions [23], [24], [25], [32], [33], [34], [35], [36], [37], [38], [39], [40], [41], [42], [43], [44], [45]<...…”

“…Moreover, concerning the holistic standpoint, ad hoc architectures for DSM have become a widespread practice. For instance, more than 85% of the selected blockchain-based literature covers ad hoc SAs without adequate AMP, model, or reasoning [23], [24], [25], [26], [29], [30], [31], [32], [33], [34], [35], [36], [37], [38], [39], [40], [41], [42], [43], [44], [45], [46], [47], [48], [49], [50]. Ad hoc solutions exhibit severe constraints on customizability and adaptability with respect to the viewpoint of software engineering and system architects.…”