Different models are implemented in this simulator. A new full example has been added in this new release v0.3.0 which demonstrate the use of two of them: messaging and tasking models.
We have treated those two models at the same time because both are the engines of the simulation.
In Symu, agents are task-based. And a task is an action with a cost. Some of them don’t perform task, such as a book or a static website; others can perform task such as workers. You can specify if the agent can perform task on weekends or not, that can be useful when your organization is an enterprise.
There are also two main aspects of the model that you can configure: limit the total number of tasks or the number of simultaneous tasks (to allow multi-tasking or create a pull-system); and define the capacity of the agent.
Messaging is the only way agents communicate to each other. This is one of the means of ensuring the autonomy of agents. A message can have different types: it can be a phone call, a meeting, an email, …
There are two main aspects of the model that you can configure: limit the number of messages and the cost of sending or receiving a message.
You can use this example to discover and understand the impact of all the setups on the agents. That will help you setup you own messaging and tasking models.
Scenario of the simulation
- 1 group agent
- A number of person agents who are members of the group
The persons ask tasks to the group via email every step. They warn the group at the end of every day and every week that they are leaving.
To start playing with this example, download the version v0.3.0. You will find the source code and the executable SymuMessageAndTask.exe.
Subscribe To Our Newsletter
Join our mailing list to receive the latest news, case studies and updates from our team.