-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs(daisi): Finishing OptiMaFlow Docu
- Loading branch information
Showing
9 changed files
with
70 additions
and
55 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,29 +1,45 @@ | ||
!!!danger "This is work in progress!" | ||
|
||
# Introduction | ||
|
||
## Getting started | ||
|
||
To run OptiMaFlow please download and build the repository as described [here](../getting_started.md). | ||
Afterwards, follow the instructions for [OptiMaFlow](../daisi/using.md) in the ns-3 Integration tab. | ||
|
||
### Intralogistics | ||
## Intralogistics | ||
|
||
In recent years, the domain of intralogistics has experienced rapid advancements in technology, driven by the fourth industrial revolution, also known as Industry 4.0 [[1]](#references). | ||
Industry 4.0 includes the convergence of physical hardware with cyber-applications, creating a new possible paradigm for warehouse logistics [[2]](#references). | ||
In a *cyber space*, entities have representations as virtual objects enabling | ||
self-organization, synergy, and emergence. | ||
This paradigm is built on design principles such as interconnectivity, information transparency, and decentralized decision-making [[1]](#references). | ||
Autonomous mobile robots (AMRs) have emerged as a key component in this shift towards decentralized decision-making, enabling them to operate autonomously and adapt to changing conditions without centralized control. | ||
|
||
Industry 4.0 (I4.0), the fourth industrial revolution, is the unification of the physical (hardware) world with cyber-applications (software) [[1]](#references). | ||
New technologies and applications emerge in the intelligent manufacturing environment, also known as smart factories or cyber-physical production systems (CPPSs) [[2]](#references). | ||
These I4.0-scenarios are built on the design principles such as interconnectivity, information transparency (open interfaces and standards), decentralized decision-making, and technical assistance [[3]](#references). | ||
For instance, a production order (PO) becomes digital and gains access to information of all devices and services of the CPPS. | ||
AMRs utilize a decentralized decision-making process for collision-free navigation, making them highly flexible [[3]](#references). | ||
This flexibility is crucial in addressing the growing need for adaptable and reconfigurable warehouse logistics solutions, particularly in dynamic production lines and in response to disruptions in the supply chain. | ||
AMRs, with their ability to independently make decisions and navigate in a decentralized manner, offer significant advantages in meeting these evolving demands. | ||
|
||
### Entities within a CPPS, Agent-based Approach, Participants Overview | ||
|
||
## What is OptiMaFlow? | ||
|
||
## Interfaces are important | ||
A material flow in OptiMaFlow is a declarative description of the transport of materials. | ||
OptiMaFlow, short for **Opti**mization of **Ma**terial **Flow**s, is responsible for intelligently assigning tasks of a [Material Flow](./participants//material_flow.md) to [Autonomous mobile robots (AMRs)](./participants/amr.md). | ||
Managing the task assignment of an AMR presents challenges, as these problems are typically NP-hard. | ||
The complexity makes finding efficient solutions difficult and computationally expensive. | ||
|
||
In OptiMaFlow, the cyber-space consists of Logical Agents [[4]](#references). | ||
Each AMR has its own Logical Agent responsible for managing its physical assets. | ||
Additionally, there are Material Flow Logical Agents, which have no representation in the physical environment. | ||
A Material Flow Logical Agent exists purely in the cyber-space and is responsible for securing the successful allocation and execution of a set of tasks. | ||
All together, these Logical Agent communicate with each other to complete the material flow in a self-organized manner. | ||
To address the task assignment challenge, we have implemented both centralized and decentralized algorithms within OptiMaFlow. | ||
|
||
|
||
## References | ||
|
||
[1] L. Monostori, “Cyber-physical Production Systems: Roots, Expectations and R&D Challenges”, Procedia CIRP, vol. 17, pp. 9–13, Jan. 2014. | ||
[1] M. Hermann, T. Pentek, and B. Otto, “Design Principles for Industrie 4.0 Scenarios”, in 2016 49th Hawaii International Conference on System Sciences (HICSS), pp. 3928–3937, Jan. 2016. | ||
|
||
[2] L. Monostori, “Cyber-physical Production Systems: Roots, Expectations and R&D Challenges”, Procedia CIRP, vol. 17, pp. 9–13, Jan. 2014. | ||
|
||
[2] R. Heidel, M. Hoffmeister, M. Hankel, and U. Döbrich, ”The Reference Architecture Model RAMI 4.0 and the Industrie 4.0 component”, VDE Verlag, 2019. | ||
[3] G. Fragapane, R. de Koster, F. Sgarbossa, and J. O. Strandhagen, “Planning and control of autonomous mobile robots for intralogistics: Literature review and research agenda,” European Journal of Operational Research, vol. 294, no. 2, pp. 405–426, Oct. 2021. | ||
|
||
[3] M. Hermann, T. Pentek, and B. Otto, “Design Principles for Industrie 4.0 Scenarios”, in 2016 49th Hawaii International Conference on System Sciences (HICSS), pp. 3928–3937, Jan. 2016. | ||
[4] D. Lünsch, P. Detzner, A. Ebner, and S. Kerner, “SWAP-IT: A Scalable and Lightweight Industry 4.0 Architecture for Cyber-Physical Production Systems,” in 2022 IEEE 18th International Conference on Automation Science and Engineering (CASE), Aug. 2022, pp. 312–318. |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,30 @@ | ||
!!!danger "This is work in progress!" | ||
|
||
# Material Flow | ||
|
||
In OptiMaFlow, we utilize the [Material Flow Description Language (MFDL)](https://git.openlogisticsfoundation.org/silicon-economy/libraries/mfdl) to describe material flows in a declarative manner. | ||
A material flow is composed of a set of tasks. Each task consists of multiple orders that are assigned to a single AMR. | ||
The transport order represents the process of picking up an item from location A and transporting it to a designated delivery location B. | ||
Additionally, there are move orders that specify the movement of the AMR within the warehouse, and action orders that describe specific actions such as loading and unloading. | ||
|
||
## Material Flow Logical Agent | ||
|
||
Material Flow (MF) Logical Agents play a crucial role in coordinating and managing the assignment and execution of tasks within the cyber space. | ||
Unlike [AMR Logical Agents](./amr.md#amr-logical-agent) that represent physical assets, MF Logical Agents solely exist in the [cyber space](../introduction.md#intralogistics). | ||
Their primary responsibility is to ensure the successful assignment and execution of a specific set of tasks. | ||
|
||
To achieve this, MF Logical Agents can communicate with other MF Logical Agents and AMR Logical Agents. | ||
This allows them to assign tasks from their material flow to the appropriate AMRs, considering factors such as availability and efficiency. | ||
|
||
In a decentralized architecture, multiple MF Logical Agents can coexist in the cyber space simultaneously, each managing its own set of tasks. | ||
|
||
|
||
### Algorithms | ||
|
||
Different algorithms can be applied to assign tasks to an AMR using [centralized](../task_assignment/centralized.md) or [decentralized](../task_assignment/decentralized.md) Task Assignment Algorithms. | ||
Some Task Assignment Algorithms require cost calculations that are delegated to the [Task Management](./amr.md#algorithms-and-task-management) of the AMR Logical Agent. | ||
It is necessary to select an Algorithm to give the agent functionality. | ||
|
||
|
||
### SOLA Connection | ||
|
||
The SOLA Connection is a socket enabling the Material Flow Logical Agent to send and receive messages through the SOLA Network. | ||
All sent messages are generated by the Algorithms components and forwarded to those accordingly. |
This file was deleted.
Oops, something went wrong.
2 changes: 0 additions & 2 deletions
2
...optimaflow/task_assignment/round_robin.md → ...optimaflow/task_assignment/centralized.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters