Page 134 - Kaleidoscope Academic Conference Proceedings 2020

2020 ITU Kaleidoscope Academic Conference

Digital Process Platform beginning of a sprint, we exactly specify which functionalities
Static Geofencing we want to implement during the sprint. At the end of
the sprint, the implemented results are reviewed and the
Site send warning Construction
Manager signal to user Worker progress is discussed and documented. The benefits of
define this agile approach lie in the control and flexibility of the
restricted <<extend>> implementation process. On the one hand, we can focus the
No restricted area defined
area
implementation process on use case relevant functionalities.
<<extend>> On the other hand, the required changes that resulted from
machine position is
within restricted area compare machine false assumptions or changing constraints can be conducted.
position with
restricted area After the implementation phase, the functionalities are
validated based on the requirements defined in the second
detect <<include>> step. If all requirements of a use case are fulfilled, the
machine
position implemented functionalities are tested by applying the use
case. If the implemented system behaves as expected in the
use case, the status of implementation is released. Otherwise,
Figure 1 – Use case diagram for static geofencing.
a new cycle from steps 2 to 4 is executed.
site manager and the construction worker. With the help
of the proposed digital process platform, the construction 3.3 Platform Components and Modules
worker can define a restriction area where specific machines
In this section, we take a closer look at the communication
are not allowed to enter. In case a construction machine
infrastructure, which consists of six system components. On
enters a restricted area, the site manager and the responsible
the one hand, there is on site, where machines send their data
construction worker, receive a warning from the system.
using mounted edge devices. On the other hand, there is
3.2 Software Development Process off site, which consists of multiple modules to semantically
process the machine data. Figure 2 gives an overview about
The use case based development process of our proposed the proposed communication infrastructure.
digital process platform consists of five development steps. The edge devices consist of industrial computers that are
In the first step, we developed use cases as described before connected to the CAN-Bus of the machines. It is also
in Section 3.1. With the definition of the use cases, the main possible to integrate other external sensors on the edge
stakeholders, goals, and functionalities of the platform and device. The CAN-Bus sends data in raw byte code
intended user interactions are specified. This user-centered and needs to be converted into a human-readable form.
approach ensures that the development of the platform focuses Interpretation files such as DataBase CAN (DBC) files,
on the needs of the user and supports him in his role within which are ASCII-based and used for identifying, scaling,
the construction project. and offsetting the CAN-frames are one possible solution to
In the second step, we analyzed the use cases and translate the raw CAN-Data into an understandable format.
derived typical functionalities and sequences of the digital The read and interpreted data are then sent to the off-site
process platform, which leads to a collection of functional side using mobile communication technology to the ingestion
requirements. These requirements are implemented in the component (e.g., via 4G). This component has different
third step. The implementation process is done in an message brokers that ensure the forwarding of the incoming
agile manner in the form of development sprints. At the messages to their corresponding destinations. The proposed

Figure 2 – Communication infrastructure

– 76 –