The Block Assignments tab page is used to assign containers to blocks (or areas). Assignments are made using a dispatch table, or a set of rules. When an assignment is needed, the dispatch table is searched in order, from top to bottom, to find a rule that matches the current circumstances. As soon as a matching rule is found, it is used to assign the container to its destination. Tab Page Details  Dispatch Selection- This drop-down box selects the dispatch table that you are currently viewing/editing. By default there is one dispatch table named "Main" and it is designated as the "Main Dispatch." Table Buttons- Use these buttons to alter the tables in the dispatch selection drop-down box. Change the name of a table by clicking the Change Name button. Add additional tables by clicking the Add Table button, or remove a table by clicking the Delete Table button. Additional tables can be used as subroutines to the main table, simplifying the structure of the main table. Whichever table appears at the top of the list (when you open the drop-down box) is designated as the "Main Dispatch." This is the first table that will be searched for matching rules during an assignment. Change the ordering of the tables using the Move Table Up and Move Table Down buttons. Rule Buttons- Use these buttons to manipulate the rules in the dispatch table. Add new rules by clicking the Add Rule button, or remove a rule by clicking the Delete Rule button. Change the ordering of the rules using the Move Up and Move Down buttons. Dispatch Table The dispatch table is composed of rules. Each rule is evaluated, beginning with the first row, until a matching rule is found. As an example, in the dispatch shown above, the first rule reads, "All Type2 containers are assigned to the TypeTwoBlock area." The second rule reads, "All 20ft containers are assigned to the TwentyBlock area." The third rule reads, "All containers coming from Ship 1 are assigned to the Ship1Block area." Thus, if a 40ft container of type "Unknown" must be placed, it won't match either of the first two rules. It will match one of the remaining rules. It is important to make sure the dispatch table covers all possible cases. There are several elements available in the table. A rule matches when the current conditions of the model match the elements of the rule. A blank value indicates that everything will match that element. Required elements are designated by an asterisk. Available elements are as follows: - Container Profile - This value is the container profile that you would like to match for the row. Options for this field are determined by the [Container Types window](Container_Types.html). By specifying a container profile, only containers having the specified profile will be assigned to the designated block. Within a Container Profile, the user can specify: - Container Type聽-聽This value is the type of container that is to be dispatched. 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 considered a match for this rule. - Size - This value is the size of the container. Options include 20ft, 40ft and 45ft containers. By specifying a size, only containers of that size will be assigned to the designated block. - Equipment Type -聽This value is the equipment type of the container that is to be dispatched. 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 assigned to the designated block. - Origin - This value is the origin of the container. Options may include Yard, Ship and Gate if a [Berth Planner object](BerthPlanner.html)or [Gate Planner object](GatePlanner.html)are included in your model. By specifying this value, only containers coming from that location will be assigned to the designated block. - Destination - This value is the final destination of the container. Options may include Yard, Ship and Gate if a [Berth Planner object](BerthPlanner.html)or [Gate Planner object](GatePlanner.html)are included in your model. By specifying this value, only containers going to that location will be assigned to the designated block. - Ship - This options only appears if a ship is selected for the origin or destination. This value is the specific ship delivering or receiving the container. Ships that have been added to the [Ship Schedule](Ship_Schedule.html)are candidates for this field. By specifying a ship service, only containers associated with that ship will be assigned to the designated block. - Custom - This value is code that you write that returns either a 1, indicating the rule matches, or a 0, indicating the rule doesn't match. Type code directly into the edit box. - Block\* - This value is the container's assigned destination. It is the only required field in the table. The value may be either a block, area, or another dispatch table. Options for this field come from: a) the blocks added to the model (viewable on the [Blocks tab](Blocks.html)); b) the areas created on the [Areas tab](Areas.html); or c) other dispatch tables created on this tab. If a block or area is used, then the placement strategy field determines the specific cell where the container is placed. If a dispatch table is used, the search continues on the first row of the specified table. If a matching rule is not found in that table, the search algorithm continues with the next row of this table. - Strategy - This value is the search strategy used to find a specific cell in the designated block or area to place the container. Options for this field are defined on the [Container Placement tab](Container_Placement.html). If a suitable cell is not found, the search algorithm continues with the next row of the table. Note: If the search algorithm finishes the last row of the table without finding a matching rule, the model will halt with a "Dispatch Error." Be aware that subroutine tables and placement strategies may not always succeed, which means the search algorithm will continue and could possibly error out. To avoid this, you may want to include a catch-all rule as the final rule (a blank row with only a block assignment), along with using a placement strategy with a catch-all search option (e.g. "[Least full cell](Container_Placement.html#SearchSelection)").