In the near future, we want to publish information about the states of orders/tasks/material flows and their assignments to AMRs with MQTT Topics.
Then, a backend/web server for the UI can simply subscribe to these topics to receive data for visualisation. (As of now, we don't plan to send new material flows from the UI into our application.)
I would propose the following topics:
(Instead of uuid, the topic string will contain the actual uuid of the order/task/material flow. )
material_flow/order/uuid/state for the state of an order
material_flow/task/uuid/state for the state of a task
material_flow/material_flow/uuid/state for the state of the complete material flow
material_flow/material_flow/uuid/spawn for the MFDL/PFDL program
material_flow/task/uuid/assignment for the assignment of a task to an AMR
With these topics the UI should have access to all information for visualisation about the material flow process. Information about the AMRs/AGVs should come from MARS, which we are not responsible for.
Because the ExecutionState class has information about the states of the tasks/orders, those information should be published from this class.
Information about the material flow states and spawn information, should come from the Material Flow Logical Agent. The MFLA can also directly subscribe to the material_flow/order/uuid/state and material_flow/task/uuid/state topics.
Assignment information should come from the MFLA or Central Optimizer.
In the near future, we want to publish information about the states of orders/tasks/material flows and their assignments to AMRs with MQTT Topics.
Then, a backend/web server for the UI can simply subscribe to these topics to receive data for visualisation. (As of now, we don't plan to send new material flows from the UI into our application.)
I would propose the following topics:
(Instead of
uuid, the topic string will contain the actual uuid of the order/task/material flow. )material_flow/order/uuid/statefor the state of an ordermaterial_flow/task/uuid/statefor the state of a taskmaterial_flow/material_flow/uuid/statefor the state of the complete material flowmaterial_flow/material_flow/uuid/spawnfor the MFDL/PFDL programmaterial_flow/task/uuid/assignmentfor the assignment of a task to an AMRWith these topics the UI should have access to all information for visualisation about the material flow process. Information about the AMRs/AGVs should come from MARS, which we are not responsible for.
Because the ExecutionState class has information about the states of the tasks/orders, those information should be published from this class.
Information about the material flow states and spawn information, should come from the Material Flow Logical Agent. The MFLA can also directly subscribe to the
material_flow/order/uuid/stateandmaterial_flow/task/uuid/statetopics.Assignment information should come from the MFLA or Central Optimizer.