EmPlant物流仿真系统讲义课件.pptVIP

* * All commands show an identical structure: 1. addressing the object (@) 2. applying the Method (move) to the object. In our case, the object @ is the MU that called the control and thus activated the Method. * * * * * * * * Discuss all menu items. Important: MU-Selection “Constant” and the Interval. A detailled discussion of all tabs will follow later on. * * Important: Proc. Time and activating the statistics feature. * * * * * * As the station “milling” has a longer processing time than the station “saw”, MU′s are blocked and they change their color. This is called blocking behavior. Explanation: An MU intends to move but the next station is still occupied. The intention to move is entered into the blocking list and, as soon as the station is available again, the MU is moved. (default behavior) The Method “reset” deletes all MU′s. Explain basic functions of the EventController (Start, Stop, Reset and Step) and try them out. Save the model under a new name. * * Discuss all menu items and test them with the model. The following features are not discussed in this class: Inherit Position Rearrange * * Explain how Frames are copied. The bottleneck formed by the station “milling” in the first exercise is fixed here by inserting a second station. Important are the processing times of both milling stations. Left mouse button amd shift open the objects and compare the inserted time values: days:hours:minute:sec. Show fast input of times using ‘:’ * * Important: behavior “Percent” of the TableFile as it is required for the next exercise. show successor No. with settings in model * * In the last exercise we tried to remove the bottleneck “milling”. As the basic functionality of the object determines a set sequence of movement, we will introduce the object FlowControl to optimize the distribution of the MU′s to both milling stations. Entry-Control stays on ‘or’ Blocking Mode:OFF: FlowCtrl treys percentage, but if successor is not free, next successor will be the o