AIMMS Multi Agent and Web Services User's Guide - Tutorial

Paragon Decision Technology B.V.

Informations

• Publié par: Mosur
• Nombre de lectures: 29
• Langue: English

Extrait

AIMMS Multi Agent and Web Services User’s Guide - Tutorial
This file contains only one chapter of the book. For a free download of the
complete book in pdf format, please visit www.aimms.com
Aimms 3.11cCopyright 1993–2010 by Paragon Decision Technology B.V. All rights reserved.
Paragon Decision Technology B.V. Paragon Decision Technology Inc. Paragon Decision Technology Pte.
Schipholweg 1 500 108th Avenue NE Ltd.
2034 LS Haarlem Ste. # 1085 80 Raffles Place
The Netherlands Bellevue, WA 98004 UOB Plaza 1, Level 36-01
Tel.: [phone] USA Singapore 048624
Fax: [phone] Tel.: [phone] Tel.: [phone]
Fax: [phone]
Email: [e-mail]
WWW: www.aimms.com
Aimms is a registered trademark of Paragon Decision Technology B.V. IBM ILOG CPLEX and sc CPLEX is
a registered trademark of IBM Corporation. GUROBI is a registered trademark of Gurobi Optimization,
Inc. KNITRO is a registered trademark of Ziena Optimization, Inc. XPRESS-MP is a registered trademark
of FICO Fair Isaac Corporation. Mosek is a registered trademark of Mosek ApS. Windows and Excel are
A Aregistered trademarks of Microsoft Corporation. T X, LT X, andA S-LT X are trademarks of the American
ME E E
Mathematical Society. Lucida is a registered trademark of Bigelow & Holmes Inc. Acrobat is a registered
trademark of Adobe Systems Inc. Other brands and their products are trademarks of their respective
holders.
Information in this document is subject to change without notice and does not represent a commitment on
the part of Paragon Decision Technology B.V. The software described in this document is furnished under
a license agreement and may only be used and copied in accordance with the terms of the agreement. The
documentation may not, in whole or in part, be copied, photocopied, reproduced, translated, or reduced to
any electronic medium or machine-readable form without prior consent, in writing, from Paragon Decision
Technology B.V.
Paragon Decision Technology B.V. makes no representation or warranty with respect to the adequacy
of this documentation or the programs which it describes for any particular purpose or with respect
to its adequacy to produce any particular result. In no event shall Paragon Decision Technology B.V.,
its employees, its contractors or the authors of this documentation be liable for special, direct, indirect
or consequential damages, losses, costs, charges, claims, demands, or claims for lost profits, fees or
expenses of any nature or kind.
In addition to the foregoing, users should recognize that all complex software systems and their doc-
umentation contain errors and omissions. The authors, Paragon Decision Technology B.V. and its em-
ployees,anditscontractorsshallnot beresponsibleunderanycircumstancesforprovidinginformation
or corrections to errors and omissions discovered at any time in this book or the software it describes,
whether or not they are aware of the errors or omissions. The authors, Paragon Decision Technology
B.V. and its employees,and its contractors do not recommend the use of the software described in this
book for applications in which errors or omissions could threaten life, injury or significant loss.
AThis documentation was typeset by Paragon Decision Technology B.V. using LTXandtheLucida fontE
family.Chapter 2
Tutorial
In this chapter there is a small but complete example of a multi-agent appli- This chapter
cation to be built using Aimms. Following the description of the underlying
problem, you will need to specify an agent community, the agent setup for
each of four different agent roles, and the procedures that make up the com-
munication between the agents.
This tutorial focuses purely on the multi-agent features of Aimms.Somebasic Requirements
Aimms knowledge is required but, contrary to what you might expect, the ex-
ample does not include any optimization. This is avoided to keep the example
as simple as possible, allowing you to focus on learning the multi-agent con-
cepts in Aimms. If you lack the necessary Aimms knowledge you are advised to
read one of the Aimms tutorials that come with the Aimms distribution pack-
age.
In order to make this tutorial, or run the completed implementation provided Licensing
with the Aimms distribution, you need a license that allows you to simulta-
neously run the indicated amount of Aimms sessions. If you have a network
license with a sufficient amount of free Aimms licenses, you can use these. If
you only have a single Aimms license, but still want to experiment with the
Aimms multi-agent technology, for instance, by making this tutorial, Paragon
will provide you, on request, with a temporary Aimms license capable of run-
ning the tutorial example.
2.1 Describing the agent application
The example in this chapter concerns the simulation of a help desk. Assume A help desk
that the help desk center has priority customers who request help through simulation...
their dedicated account managers. Each account manager passes the request
to the first available worker to handle the request in its entirety. The overall
performance of the help desk is monitored by a single controller.Figure2.1
illustrates the connections between individual customers, account managers
and workers.Chapter 2. Tutorial 16
C1 C2 C3 C4
A1 A2
W5 W7W1 W2 W3 W4 W6 W8
Figure 2.1: Connections between individual customers (C), account managers
(A) and workers (W)
The simulation is implemented as a multi-agent application with the following ...asa
agent roles multi-agent
application
customer,
account manager,
worker, and
controller.
For convenience, all agents, other than the controller, are started by the con-
troller in the example. In reality, however, agents could also begin, and log
on to the community, independently. Using the functionality described later
in Chapter 3, the example could easily be modified to allow this. The number
of agents that are started is kept small, but this can be enlarged if you wish
so. In total, there will be 4 customers, 2 account managers, 8 workers and 1
controller.
During the simulation, a customer agent sends messages requesting help to its Customer
designated account manager. The time interval between requests varies over
time, and is simulated using an exponential distribution. The corresponding
distribution parameter value is provided as input by the controller.
Once a request for help reaches an account manager, this request is forwarded Account
to the first available worker. If no worker is available, the request is queued. manager
Whenever a worker becomes available, any account manager with a nonempty
queue requests exclusive access to this worker. If exclusive access is granted
by the worker, the account manager forwards the first request on his queue
to this worker. If exclusive access is denied, the account manager waits until
another worker becomes available again.Chapter 2. Tutorial 17
A worker is able to handle a help request forwarded by any account man- Worker
ager. Workers notify all account managers whenever they become available
after having completed a request. Whenever a worker receives a request for
exclusive access from an account manager, and is still available, that access
is granted. The time required to complete the help request by a worker is as-
sumed to be uniformly distributed. The corresponding distribution parameter
values are provided as input by the controller.
The controller is a special agent that manages the community by The controller
starting and stopping agents,
providing input parameters to agents, and
gathering performance statistics from agents.
Once the simulation is started, the controller can influence the performance of
individual agents by modifying their distribution parameters.
2.1.1 Message types and semantics
The functionality described in the previous section can be implemented by Sending
including several message types in the agent application. In the paragraphs messages
below, the message types sent, by all types of agents, will be discussed in more
detail. An agent sends a message by calling a corresponding send procedure,
which relays the message to the underlying agent technology. Here, all relevant
message data are encapsulated, and the message is passed on to the receiving
agent. As we will see later, Aimms can automatically add the appropriate send
procedures to an Aimms project implementing a particular agent role.
Messages sent from one agent to another agent must be either filtered or han- Handling
dled by the receiving agent. The underlying agent technology ensures that messages
any incoming message is correctly filtered or handled. This is accomplished
by calling the designated filtering or handling procedure, within the Aimms
project of the receiving agent, whenever a new message arrives. When setting
up an Aimms project to implement a particular agent role, Aimms can auto-
matically add skeleton filtering and handling procedures to the project. You,
as an agent developer, can then modify these skeleton procedures to take the
actions that you want.
Customer agents send RequestHelp messages to their designated account man- The Request-
agers to simulate a help request. For the sake of simplicity, it is assumed that Help message
these messages do not carry any extra data arguments. Account managers use type