The Arrivals tab page is used to establish how many containers (and trucks) actually arrive at the gate during any given week. Tab Page Details  Row Buttons- Use these buttons to manipulate the rows in the arrival operations table. Add a new row by clicking the "Add Row" button, or remove a row by clicking the "Delete Row" button. Change the ordering of the rows using the up and down arrow buttons. The arrival operations table lists the set of operations that are to be executed for the gate during the week. Each operation is represented by a row in the table. The following parameters are part of the arrival operations table. Note: The Gate Planner may or may not be the data driver of your model. To get a correct model, it is vital to set up this table correctly. Please read more about the model data driver in the [FlexTerm Modeling Paradigm](Container_Terminal_Modeling_Overview.html). Operation- This value is the type of operation to be executed. Options include "Container Pickup," "Container Dropoff," "Chassis Pickup" and "Chassis Dropoff." A container pickup means that a truck will arrive at the gate, pickup a container from the yard and leave. A container dropoff means that a truck will arrive at the gate with a container, drop off the container in the yard, and leave. A chassis pickup means that a truck will arrive at the gate as a bobtail, pickup a chassis, and leave. A chassis dropoff means that a truck will arrive at the gate with an empty bed, dropoff a chassis, and leave. Chassis pickup and dropoff operations don't have anything to do with containers, but do create extra traffic through the gate. Dual transactions are considered each time a container dropoff operation is scheduled. For each dropoff, FlexTerm uses the [dual transaction %](Arrival_Patterns.html#DualTransaction) of the assigned [pattern](Arrival_Patterns.html)to randomly decide if a dual transaction should be done. If so, FlexTerm checks to see if there are containers scheduled to be picked up in that same hour (for the same pattern) and assigns one of these containers to be part of the dual transaction. If no containers are scheduled for pick up in that hour, no dual transaction is done. Thus, the dual transaction % is really an upper limit and not an exact value. Container Profile -聽The following four parameters define the container profile within the arrival operations table. These parameters are accessible through the drop down menu for each row in the container profile column.  Container Type - This value is the type of container that is to be operated on. Options for this field are determined by the [Container Types window](Container_Types.html). By specifying a container type, only containers of that type will be picked up or dropped off. This field is required for container operations, but has no meaning for a chassis operation. Size - This value is the size of the container that is to be operated on. Options include those container sizes as specified in Container Type such as 20ft, 40ft and 45ft containers. By specifying a size, only containers of that size will be picked up or dropped off. A blank field indicates that the default value of a 40ft container will be used. Equipment Type -聽This value is the equipment type of the container that is to be operated on. Options include General, Open Top, Reefer, Tank, Bulk, Port Hole and Flat Rack equipment types. By specifying an equipment type, only containers of that equipment type will be picked up or dropped off. A blank field indicates that the default value of the container type will be used. Origin- For a dropoff operation, this value is the final destination of the container. For a pickup operation, this value is the origin of the container. Options include Yard, Gate, Default, and None; and may also include Ship if a [Berth Planner object](BerthPlanner.html)is included in your model. Use this field to specify where dropoff containers should go and where pickup operations should come from. A blank field indicates that the default from/to of the container type will be used as specified in the [Container Types window](Container_Types.html). Pattern- This value is the arrival pattern, or distribution, that should be followed for this operation. A blank field means that the default distribution is used, which is always the first distribution in the list. When multiple rows are assigned the same pattern, each row will follow the arrival pattern. The rows are not added together first. For example, a row of 4,000 laden dropoffs and a row of 1,000 empty dropoffs are both assigned to the default pattern. The 4,000 laden dropoffs will occur throughout the week and the 1,000 empty dropoffs will also occur throughout the week. You will not see the 5,000 dropoffs lumped together first, possibly causing all聽the empty dropoffs to end up on the first day of the week. If you want to cause such a behavior, use a variety of arrival patterns. Min and Max聽 - These values are the minimum and maximum number of containers that may be moved during this operation. The actual number of containers moved is a random number between the min and max that is chosen at the start of each week during run time. Note: A value of 0 in both the "Min" and "Max" fields can be used to provide an empty bucket for an undetermined number of containers. This may be used when the gate is the data driver for the model or when another ship is the data driver for the transaction, such as in a transshipment operation. Similarly, a value of -1 in the "Min" field with a positive number in the "Max" field can be used to provide a limited bucket. In this case the number of containers is not allowed to exceed the maximum value. For more information and examples on the model data driver, see the [FlexTerm Modeling Paradigm](Container_Terminal_Modeling_Overview.html).