![]() The End event triggers after the source site inventory review of the product on order and various statistics are calculated. The Begin event triggers when the order initially arrives. ![]() This can come from downstream customers through demand or downstream sites through replenishment calls, as well as from pushed shipments in the Shipments table. This event script is triggered any time a site receives an order for product after being chosen as the source. There is no expected return from the script. Typical uses include looping through all the sites in a model to set a particular attribute, initializing the data in a global array, and reporting certain information at the end of a simulation run that may not be captured by the standard output. This event script is triggered at the very beginning and very end of a simulation run. The script is triggered regardless of arrival location so your first few lines of code should check the type of the arrival location and exit if the arrival location is not a customer type. You may only be interested in arrivals at customers, or even a subset of customers. Event scripts give you the opportunity to review the state of certain attributes in the model or to set attributes based on conditions, although no action is required.įor example, the On Shipment Arrival event is triggered for any shipment that arrives at a site or a customer. It is up to you to decide in code if there are other conditions (location of the event, timing of the event, cause of the event) that determine whether to continue processing the script. They are accessed at any time the event occurs. Event scripts are triggered by certain activities during a simulation run.
0 Comments
Leave a Reply. |