Arrivals

An arrival defines how entities enter your model. You create one by connecting an entity to its first activity or queue; the double-headed arrow marks the connection. On the arrival’s General tab, the Type sets how entities arrive.

Arrival types

• Continuous: keep the first activity full at all times
• Periodic: a set quantity every so often (the classic inter-arrival time)
• Scheduled: arrivals at exact times you list or import
• Daily Pattern: a weekly volume shaped across the hours of each day
• Ordered: demand-driven replenishment triggered by a signal

Action logic

Continuous and Scheduled arrivals have no route-level Action Logic tab. Continuous is governed entirely by capacity, and a Scheduled arrival carries action logic on each individual entry instead. The other three types (Periodic, Daily Pattern, Ordered) have an Action Logic tab that runs for every entity they create.

LegacyHow this worked in the previous version

Arrival connections define how entities enter the system to begin processing. Define arrivals by connecting an entity to an activity or storage and entering clarifying information in the properties dialog. The double-headed arrow identifies arrivals.

Create multiple arrivals from an entity to one or more activities.

Type

The “Type” dropdown changes the type of arrival. Options Include:

• Continuous Always available
• Daily Pattern Different pattern for each day of the week
• Ordered Just-in-time, set the trigger to reorder
• Periodic Repeats on a set schedule
• Scheduled Define the time of each arrival

Additionally, see the model objects for arrivals.

• What is a daily pattern model object - Analyze raw data and automatically create patterns
• What is a scheduled arrival model object - Import arrival data with modifiers

There are two tabs common to all arrival dialogs: Action and Name.

Common Tabs

Action

Assign custom behavior to a model when entities arrive in the model. In addition to the arrival information set in the General tab of the arrival properties dialog, assignment Assign custom behavior to a model when entities arrive. In addition to the arrival information set in the General tab of the arrival dialog, assignment statements and IF…THEN’s might use entity attributes, variables, and scenario parameters to enhance the arrival functionality.

Action logic occurs at entity creation but before entering any activity. To learn more about Action Logic, see What is Action Logic?

Name

The Name tab (shown below) allows you to define route names when you are linking hierarchical models. All arrival connections have a Name tab in their properties dialog. For more information, see Hierarchical Modeling.

Connection name This name is used when mapping connections between different charts (main model and submodel). The Name tab is for hierarchical modeling only. See What is a Hierarchical Model?