Professional Documents
Culture Documents
3 First model :
Figure 2: Software architecture of an agent
AEIO specification
In this article, we are located in the extension of the The figure 2 illustrates the operating mode of an agent.
work initiated by (Galland et al. 1999) allowing to an- This last is composed of four autonomous entities:
swer the problems of the distributed simulation through
multi-agent concepts. 1 Agent, Environment, Interaction et Organization
• the Sending module is launched each time that a call
of a sending method is carried out by the simulation agent agent
software; its role is to correctly format messages (re-
ceiver, standard agent message, etc.), and to trans- agent
mit them to the communication module; agent agent
• the receiving module generates an event in the sim-
ulation software; this module uses informations con-
tained in the message stored at the head of the re- facil. facil.
ception queue;
Message sent
Main flow
WINSOCK
Communication
Error
Cognitive agent Activity center error
Generating a event
Internal agent
3.5 Synchronization Method or event
3.6.2 Decisional modulesThe implementation of deci- We wish to implement teaching tools, which illustrate the
sional modules, which represent decision-making centers production system behaviour. Taking into account the
of simulation models, is application-dependent. These current state of our model, we limit the teaching cases to
modules are associated with agents, such as we define in systems without cycle and junction point. These last two
the previous section. They allow a better integration with cases require a more advanced synchronization technic.
simulation models.
We initially expose the teaching contributions of our Figure 6: Teaching application of the Industrial Manage-
model. Then we describe an instance of it. We finish ment
on the synchronization technic behavior on the teaching
case example.
Figure 6 illustrates a generalized teaching model made up
4.1 Contribution for pedagogy of physical device models and decisional systems, which
can influence the simulation strategy. All these elements
are connected by physical and decisional flows. The first
Our teaching model highlights three interesting aspects correspond to the entity movements between the vari-
for the decision-making training within an industrial sys- ous physical models. The second ones are composed of
tem. production orders (compound of a date and a number of
Learner models represent some production lines in inter- entities to produce), and flow of information contains the
action, learners must implement a local decision-making running state of the production.
policy and thus try to react vis-a-vis unverifiable vari- Models of the physical subsystem are elaborated a priori
ations of enter and outgoing flows. Learners have the by learners according to constraints given by the supervi-
role to conceive and modify a system to respond to these sor. Indeed the existing simulation tools (Arena, etc.)
problems. Moreover they will have to dynamically adapt do not allow structural changes of models when the sim-
themselves to interactions existing between there models ulation is running.
and other ones.
Within the checking and instancing framework of our
The second interesting aspect is the possibility to put teaching model, we consider the production system of fig-
learners in situations, whish have not the same level of ure 7.
decision-making.
This model is composed of four machines M1, M2, M3
Our teaching model enables to confront learners to var- and M4. Each one is dealt with sub-models that are
ious production line risks. Moreover some simulation simulated in “parallel”. As requires in our current ap-
proach presented in section 3, entity flows cause neither
2 in the context of production system simulation cycle, nor junction point. Decisional systems D1, D2 and
3 Production Order D3 are autonomous software entities, which are manag-
behavior. Figure 8 illustrates the message arrivals e.g.,
D1 P1(4) meaning that entity P1 is arrived at the simulation
Ag date 4. It shows simulation date ts(M1 ), the state of M1
and his queue.
P2(2) P5(7)
Ag Messages P1(1) P3(6) P4(6) P6(9) End
M2 t
S Ag ts(M1) 0 1 1 2 2 6 6 7 7 9 9 End
M1 M3
Ag
M4
Ag Q(M1)
2
4 4 5 5
6
t
1 2 3 4 5
t
Ag
M1 1 1 1 2 2 3 4 4 5 6 6 6
D3
t
n Proceeding of part n
Ag n
a b
Entity flows Simulation from date a to date b Part n into the queue
D2 n
Production order flows Waiting time of simulation
Information flows about produced entities
Figure 8: Simulation on M1
Ag Communication agents
REFERENCES