Continuous Arrival
A continuous arrival keeps the destination activity full at all times. There is nothing to configure: ProcessModel fills the activity to its capacity at the start and replaces each entity the moment a slot frees, so the activity never starves.
Use it to model an effectively unlimited upstream supply, or to study a downstream bottleneck where you want the target always fed.
A continuous arrival has no settings and no Action Logic tab, since its flow is driven entirely by the destination’s capacity.
LegacyHow this worked in the previous version
A continuous arrival causes entities to continuously feed the connected activity whenever processing capacity is available at the activity; any activity input queue is ignored. This type of an arrival should only connect to activities and requires no other information to be defined.
You should be aware of the following operating constraints when using the Continuous arrival:
- DO NOT bring other arrivals into the same activity or storage to which the Continuous arrival is attached.
- Since the input queue is ignored when using the Continuous arrival, any batching activity set to occur before the activity will be ignored as well.