Requirements for automated L/UL identified in the three cases
| Type of function | |||||
|---|---|---|---|---|---|
| Information acquisition | Information analysis | Decision and action selection | Action implementation | ||
| Layer of interoperability | Organisational | It is necessary to acquire data about the unit loads being moved, potential complications in the execution of L/UL, trailer–loading bay alignment, confirmations when deliveries are completed, the sequence of goods, and the need for maintenance | It is necessary to combine and analyse data to ensure that L/UL is not obstructed (e.g. by poorly placed unit loads), to verify the correct sequence of goods in the L/UL process, to analyse trailer–loading bay alignment, to assess the need for maintenance, and to compare unit loads received with the unit loads ordered | It is necessary to make decisions about whether the sequence is correct, whether trailer–loading bay alignment is sufficient, when is it time to depart, whether maintenance is needed, whether all required activities have been performed so that next activity can be performed, and whether the loading or unloading process is complete. It may also be necessary to select the correct loading bay | It is necessary to perform actions for managing goods that are out of sequence, opening and closing gates, stacking and unstacking unit loads, activating and deactivating L/UL, signalling when maintenance is needed, and sending signals between different systems. For the conveyor equipment, the trailer needs to be connected to the power grid, and its suspension needs to be adjusted. For AGVs, a dock lip between the loading bay and truck may need to be put in place |
| Legal | It is necessary to acquire data about legal compliance and potential liability issues as well as for performance follow-up. Data also need to be collected about what goods are delivered in what sequence, damaged goods, the timeliness of deliveries, and the load securing in order to verify the events that happened | It is necessary to combine and analyse data to detect potential liability issues and for follow-up on performance to compare the delivered goods with the ordered goods, confirm the sequence, gauge the timeliness of deliveries, and ensure the load securing | It is necessary to make decisions about potential liability issues and the level of performance, that is, whether there is a liability issue, whether performance is subpar, which party is responsible, what the consequences are, and how the responsible party should compensate the others. It is also necessary to determine responsibility for securing loads | It is necessary to perform actions to secure loads. The cargo needs to be secured on the truck or trailer | |
| Semantic | It is necessary to acquire data that are understandable and that have a clear meaning for all parties. It is also necessary that the subprocesses in L/UL can be understood and performed considering incoming signals. Signals need to be transferrable and understandable between the IT systems used by the sender, transport provider, and recipient | It is necessary to combine and analyse data from different sensors in L/UL in order to allow combining and understanding sensor data from different subprocesses in the L/UL process as a means to ensure that the activities in L/UL can be performed | It is necessary to make decisions based on an understanding and agreement between all parties involved about what decisions in L/UL should be made in different situations and what data the system requires in order to make certain decisions regarding, for instance, the criteria for determining whether a delivery has been confirmed | It is necessary to have an understanding and agreement about the actions performed in the L/UL process between the sender, transport provider, and recipient. The signals between subprocesses in the L/UL process need to be actionable, including the L/UL equipment, the gates of the loading bays, the truck, the power grid’s connectivity, the dock lip, and the trailer’s suspension | |
| Technical | It is necessary to have sensors to acquire data for monitoring the activities in L/UL | It is necessary to be able to combine and analyse data from the different sensors in the L/UL system in order to ensure that the activities in L/UL can be performed (e.g. combining signals from the gates of the loading bays and trailer–loading bay alignment). Connectivity is needed between the subprocesses involved in the L/UL to enable sending and receiving signals | It is necessary to make decisions based on the sensor data analysed in order to determine whether the next activity in the process can be performed. A L/UL control system is needed to make decisions about the incoming sensor data | It is necessary for different subprocesses in L/UL to be connected, including the L/UL equipment, the gates of the loading bays, the power grid connection, and the truck’s suspension, so that those processes can be performed without human involvement. It is also necessary for the truck to be connected and able to perform actions (e.g. opening the trailer door) | |
| Type of function | |||||
|---|---|---|---|---|---|
| Information acquisition | Information analysis | Decision and action selection | Action implementation | ||
| Layer of interoperability | Organisational | It is necessary to acquire data about the unit loads being moved, potential complications in the execution of L/UL, trailer–loading bay alignment, confirmations when deliveries are completed, the sequence of goods, and the need for maintenance | It is necessary to combine and analyse data to ensure that L/UL is not obstructed (e.g. by poorly placed unit loads), to verify the correct sequence of goods in the L/UL process, to analyse trailer–loading bay alignment, to assess the need for maintenance, and to compare unit loads received with the unit loads ordered | It is necessary to make decisions about whether the sequence is correct, whether trailer–loading bay alignment is sufficient, when is it time to depart, whether maintenance is needed, whether all required activities have been performed so that next activity can be performed, and whether the loading or unloading process is complete. It may also be necessary to select the correct loading bay | It is necessary to perform actions for managing goods that are out of sequence, opening and closing gates, stacking and unstacking unit loads, activating and deactivating L/UL, signalling when maintenance is needed, and sending signals between different systems. For the conveyor equipment, the trailer needs to be connected to the power grid, and its suspension needs to be adjusted. For AGVs, a dock lip between the loading bay and truck may need to be put in place |
| Legal | It is necessary to acquire data about legal compliance and potential liability issues as well as for performance follow-up. Data also need to be collected about what goods are delivered in what sequence, damaged goods, the timeliness of deliveries, and the load securing in order to verify the events that happened | It is necessary to combine and analyse data to detect potential liability issues and for follow-up on performance to compare the delivered goods with the ordered goods, confirm the sequence, gauge the timeliness of deliveries, and ensure the load securing | It is necessary to make decisions about potential liability issues and the level of performance, that is, whether there is a liability issue, whether performance is subpar, which party is responsible, what the consequences are, and how the responsible party should compensate the others. It is also necessary to determine responsibility for securing loads | It is necessary to perform actions to secure loads. The cargo needs to be secured on the truck or trailer | |
| Semantic | It is necessary to acquire data that are understandable and that have a clear meaning for all parties. It is also necessary that the subprocesses in L/UL can be understood and performed considering incoming signals. Signals need to be transferrable and understandable between the IT systems used by the sender, transport provider, and recipient | It is necessary to combine and analyse data from different sensors in L/UL in order to allow combining and understanding sensor data from different subprocesses in the L/UL process as a means to ensure that the activities in L/UL can be performed | It is necessary to make decisions based on an understanding and agreement between all parties involved about what decisions in L/UL should be made in different situations and what data the system requires in order to make certain decisions regarding, for instance, the criteria for determining whether a delivery has been confirmed | It is necessary to have an understanding and agreement about the actions performed in the L/UL process between the sender, transport provider, and recipient. The signals between subprocesses in the L/UL process need to be actionable, including the L/UL equipment, the gates of the loading bays, the truck, the power grid’s connectivity, the dock lip, and the trailer’s suspension | |
| Technical | It is necessary to have sensors to acquire data for monitoring the activities in L/UL | It is necessary to be able to combine and analyse data from the different sensors in the L/UL system in order to ensure that the activities in L/UL can be performed (e.g. combining signals from the gates of the loading bays and trailer–loading bay alignment). Connectivity is needed between the subprocesses involved in the L/UL to enable sending and receiving signals | It is necessary to make decisions based on the sensor data analysed in order to determine whether the next activity in the process can be performed. A L/UL control system is needed to make decisions about the incoming sensor data | It is necessary for different subprocesses in L/UL to be connected, including the L/UL equipment, the gates of the loading bays, the power grid connection, and the truck’s suspension, so that those processes can be performed without human involvement. It is also necessary for the truck to be connected and able to perform actions (e.g. opening the trailer door) | |
Source(s): Table by authors
Sharing content requires targeting cookies to be enabled. Please update your cookie preferences to use this feature.