Java Reference
In-Depth Information
nutSource.attachTo("FULL", drill);
nutSource.attachTo("NOTFULL", drill);
screwSource.attachTo("FULL", cutter);
screwSource.attachTo("NOTFULL", cutter);
sink.attachTo("EMPTY", assembler);
sink.attachTo("NOTEMPTY", assembler);
// the work cell attaches itself to all the events
// raised by the subsystems
attachTo("any", nutSource);
attachTo("any", screwSource);
attachTo("any", drill);
attachTo("any", cutter);
attachTo("any", transport);
attachTo("any", assembler);
attachTo("any", sink);
}
// the work cell delegates the GUI to display the event
// raised by the subsystems
protected void
notifyEvent(DiscreteEvent event) {
gui.display(event);
}
}
9.5.4
Test
The test case consists of the simulation of the work cell behaviour in a
variety of possible configurations. Every configuration differs in the values
of the process data of each subsystem and is characterized by the presence
of a bottleneck corresponding to the slowest subsystem. Table 9.4 reports
the process data of a configuration where the cutter is the slowest subsys-
tem. The rates are expressed in number of pieces per minute while the
move and load times are expressed in number of milliseconds. Accordingly,
Table 9.5 reports two consecutive sequences of events and two GUI screen
shots corresponding to the event raised at instant 3909 and at instant
6109 (both expressed in number of milliseconds since the simulation's
start).
Table 9.4
The subsystems process data of a possible configuration
Nut
Screw
Bolt
source
source
Drill
Cutter
AGV
Assembler
sink
Max
Max
Max
Max
Move
Load
Max
Max
rate
rate
rate
rate
time
time
rate
rate
80
70
40
30
650
300
35
50
