# The Role of Multi-Agent Systems in Realizing Asset Administration Shell Type 3
## 4 Agent-Based Reference Model for Realizing AAS Type 3
### Communication Based on VDI/VDE 2193 and FIPA Standards
In the I4.0 context, this information can be contained in individual submodels and should be exchangeable not only within an organization but also across company boundaries. Although these submodels follow a standardized structure defined by the AAS information metamodel, inconsistencies in their semantic interpretation may still arise. To address this, all communication partners must share a common vocabulary. This vocabulary should be based on property-based machine-readable descriptions, i.e., the attributes of an asset in the physical world that denote its characteristics. In this context, the use of standardized dictionaries such as ECLASS [50]and IEC CDD [51] is recommended, as they enable the description of properties in an unambiguous, machine-readable, and industry-independent manner. Finally, to illustrate how agents enable the communication capabilities of an AAS Type 3 solution, Figure 8 presents an example in which agents communicate using the FIPA request interaction protocol, adapted to comply with the I4.0 language guidelines using proper message structures and a shared vocabulary. In this example, an agent-based AAS representing a product requests a drilling operation from another agent-based AAS representing a drilling machine. The drilling machine agent then evaluates the feasibility of the requested operation parameters and responds with its capability to perform the task. If the operation is feasible, the agent executes the drilling process and reports the results back to the product agent. Throughout this interaction, all necessary information, such as product requirements (e.g., drilling depth, diameter, and material), interfacing details (e.g., communication protocol, endpoints, and parameters) for executing the drilling operation, and other relevant production-related information, are stored within the respective submodels of each AAS. In this context, the content of the  
Figure 8: Agent communication capability to enable AAS Type 3 collaboration. \begin{table}
\begin{tabular}{l l l l l} \hline \hline  & & **VDI/VDE 2193-1** & \multicolumn{2}{c}{**FIPA ACL**} \\ \hline \multirow{2}{*}{**Message Area**} & \multirow{2}{*}{**Message Element**} & \multirow{2}{*}{**Description**} & \multirow{2}{*}{**Use**} & **Equivalent msg.** \\  & & & & **Parameter** \\ \hline interaction- & & Content of a message (submodels or another & & O & content \\ Elements & - & data elements) & & \\ type & Purpose, i.e., intention of a message & M & & \\ sender & Sender of a message (AAS ID) & M & & \\ receiver & Receiver of a message (AAS ID) & O & receiver \\ conversationId & ID of a conversation & O & conversation-id \\ frame & messageId & ID of a message & M & - \\ replyTo & Expression referencing the original message & O & reply-with \\ replyBy & Time by which the response must be received & O & reply-by \\ semanticProtocol & Identification of the used semantic protocol & M & protocol \\ role & Role of the sender of the message & O & - \\ \hline \hline \end{tabular}  
* If mandatory; O optional.  
\end{table} 
Table 5: Comparison between the message structure of VDI/VDE 2193-1 and FIPA ACL. exchanged messages (see Table 5) is derived from the information contained within the respective submodels (e.g., requirements), ensuring consistency and accuracy in the communication between agents. The messages are structured according to VDI/VDE 2193-1 message structure and can be exchanged in JSON format over appropriate communication protocol technologies.