From 300b454662a55c2ff2f2575e3acaabb89341b0c7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jana=20G=C3=B6deke?= Date: Fri, 13 Oct 2023 09:58:28 +0200 Subject: [PATCH] docs(daisi): Clarify intended state of mfdl use --- docs/optimaflow/participants/material_flow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/optimaflow/participants/material_flow.md b/docs/optimaflow/participants/material_flow.md index 62888f9c..76ed8f06 100644 --- a/docs/optimaflow/participants/material_flow.md +++ b/docs/optimaflow/participants/material_flow.md @@ -1,6 +1,6 @@ # 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. +In OptiMaFlow, we intend to use 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.