Agent Modifications Sample Clauses

Agent Modifications. In work package 1 eight different agent types were defined. These were based on the common needs of different use cases where each of the types fulfils distinct functionalities which collaboratively can achieve the desired use case’s business function. However, when the details of the agents were further explored with the use cases it appeared that this ideal situation does not necessarily hold up in practice. In some cases conceptual agents may be combined into single technical implementations. For example, an agent which combines the planning and process orchestration capabilities within one system. Especially in the situation, when the planning is done on a smaller scale with less resources, this can provide a more concise algorithm. This combination does not compromise either of the capabilities, but instead creates an agent which is able to handle more specific tasks. This consideration on the scoping of components is broader than the MAS4AI project, as can be seen in discussions on planning and control systems for example. Another possible direction is simplification of an agent. In certain cases, it may not be needed to have for example a complete resource agent, as the actual resource does not possess any specific smart capabilities or does not require any pre/post processing. In such a case the active AAS of the agent can be simplified to the form of a passive AAS containing only the relevant resource data and omitting the agent specific models. This would still enable the other agents to keep the same references as if there was an actual resource agent, since the AAS elements holding the resource information are still going to be present.