CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application is a non-provisional of and claims the benefit of United States patent application 13/326,869 filed on December 15, 2011 which further claims priority to United States provisional patent application serial number 61/423,242 filed on December 15, 2010, United States patent application number 13/327,088 filed on December 15, 2011 which further claims priority to United States provisional patent application serial number 61/423,298 filed on December 15, 2010 and United States patent application number 13/326,823 filed on December 15, 2011 which further claims priority to United States provisional patent application number 61/423,402 filed on December 15, 2010, the disclosures of which are incorporated herein by reference in their entireties.

BACKGROUND

1. Field

[0002] The embodiments generally relate to material handling systems and, more particularly, to automated storage and retrieval systems.

2. Brief Description of Related Developments

i [0003] Warehouses for storing case units may generally comprise a series of storage racks that are accessible by transport devices such as, for example, fork lifts, carts and elevators that are movable within aisles between or along the storage racks or by other lifting and transporting devices. These transport devices may be automated or manually driven. Generally, where the case units are stored in multilevel racks, case units are placed on the different levels of the racks with a lifting device on the transport device. Where the case units are stored in racks located on different floors or levels of the storage structure the case units are generally transported between the floors while disposed on the transport devices where the transport devices travel up and down ramps spanning between the floors. In other examples the transport device with the case units disposed thereon are raised and lowered between the floors with an elevator. Generally, the case units carried by the transport devices and stored on the storage racks are contained in carriers, for example storage containers such as trays, totes or shipping cases, or on pallets. Generally, incoming pallets to the warehouse (such as from manufacturers) contain shipping containers (e.g. cases) of the same type of goods. Outgoing pallets leaving the warehouse, for example, to retailers have increasingly been made of what may be referred to as mixed pallets. As may be realized, such mixed pallets are made of shipping containers (e.g. totes or cases such as cartons, etc.) containing different types of goods. For example, one case on the mixed pallet may hold grocery products (soup can, soda cans, etc.) and another case on the same pallet may hold cosmetic or household cleaning or electronic products. Indeed some cases may hold different types of products within a single case. Conventional warehousing systems, including conventional automated warehousing systems do not lend themselves to efficient generation of mixed goods pallets. In addition, storing case units in, for example carriers, totes, trays or on pallets generally does not allow for the retrieval of individual case units within those carriers or pallets without transporting the carriers or pallets to a workstation for manual or automated removal of the individual case units.

It would be advantageous to be able to transport uncontained or unpalletized case units between levels of a storage facility independent of transport device movement between the levels. It would also be advantageous for the automated transport vehicle to operate at substantially full utility while transporting items throughout the storage and retrieval system.

BRIEF DESCRIPTION OF THE DRAWINGS

[0004] The foregoing aspects and other features of the disclosed embodiments are explained in the following description, taken in connection with the accompanying drawings, wherein:

[0005] Fig. 1 schematically illustrates an exemplary storage and retrieval system in accordance with the embodiments;

[0006] Figs. 2A, 2B, 2C, 2D, 3A and 3B illustrate schematic views of a conveyor system in accordance with the embodiments; [0007] Fig. 4 illustrates a schematic view of a conveyor shelf in accordance with the embodiments;

[0008] Fig. 5 schematically illustrates a conveyor system in accordance with the embodiments;

[0009] Figs. 6A-6D schematically illustrate a transfer station in accordance with the embodiments;

[00010] Fig. 7 is a schematic illustration of a method in accordance with the embodiments;

[00011] Fig. 8 is a flow diagram of a method in accordance with the embodiments;

[00012] Figs. 9A and 9B illustrate a feed station in accordance with the embodiments;

[00013] Fig. 10 illustrates a pickface builder in accordance with the embodiments;

[00014] Fig. 11 illustrates a pickface builder in accordance with the embodiments;

[00015] Fig. 12 illustrates a pickface builder in accordance with the embodiments;

[00016] Figs. 13A-13H and 14A-14C are schematic illustrations of exemplary operations of a portion of the storage and retrieval system in accordance with the exemplary embodiments;

[00017] Fig. 15 illustrates a platform in accordance with the embodiments ;

[00018] Fig. 16 illustrates platform guides in accordance with the embodiments ;

[00019] Fig. 17 illustrates platform guides in accordance with the embodiments ;

[00020] Fig. 18A illustrates a schematic view of a portion of the storage and retrieval system of Fig. 1 in accordance with the embodiments ;

[00021] Fig. 18B is another schematic illustration of a portion of the storage and retrieval system of Fig. 1 in accordance with the embodiments;

[00022] Fig. 19 illustrates a schematic view of a portion of an autonomous transport vehicle charging system in accordance with the embodiments;

[00023] Fig. 20 illustrates an exemplary graph of an autonomous transport vehicle charging cycle in accordance with the embodiments ;

[00024] Fig. 21 is a schematic illustration of an exemplary topology for an autonomous transport vehicle charging system in accordance with the embodiments;

[00025] Fig. 22 is a schematic representation of service interactions for an autonomous transport vehicle charging system in accordance with the embodiments; [00026] Fig. 23 is a schematic illustration of an autonomous transport vehicle charging sequence in accordance with the embodiments ;

[00027] Fig. 24 is an illustration of an exemplary charger state diagram in accordance with the embodiments;

[00028] Fig. 25 is a schematic illustration of a portion of a communication hierarchy for an autonomous transport vehicle charging system in accordance with the embodiments;

[00029] Fig. 26 illustrates a schematic view of a portion of a storage and retrieval system in accordance with the embodiments;

[00030] Fig. 27 illustrates a schematic waypoint list for an autonomous transport vehicle in accordance with the embodiments;

[00031] Fig. 28 illustrates an exemplary schematic state chart diagram for a portion of an autonomous transport vehicle charging system in accordance with the embodiments; and

[00032] Fig. 29 is a schematic illustration of an exemplary sequence diagram for charging transactions of an autonomous transport vehicle charging system in accordance with the embodiments .

DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENT ( s )

[00033] Fig. 1 generally schematically illustrates an exemplary storage and retrieval system 100 in accordance with the embodiments. Although the disclosed embodiments will be described with reference to the embodiments shown in the drawings, it should be understood that the disclosed embodiments can be embodied in many alternate forms. In addition, any suitable size, shape or type of elements or materials could be used .

[ 00034 ] In accordance with the embodiments the storage and retrieval system 100 may operate in a retail distribution center or warehouse to, for example, fulfill orders received from retail stores for case units (where case units as used herein means items not stored in trays, on totes or on pallets, e.g. uncontained or items stored in trays, totes or on pallets) . It is noted that the case units may include cases of items (e.g. case of soup cans, boxes of cereal, etc.) or individual items that are adapted to be taken off of or placed on a pallet. In accordance with the embodiments, shipping cases or case units (e.g. cartons, barrels, boxes, crates, jugs, or any other suitable device for holding items) may have variable sizes and may be used to hold items in shipping and may be configured so they are capable of being palletized for shipping. It is noted that when, for example, pallets of items arrive at the storage and retrieval system the content of each pallet may be uniform (e.g. each pallet holds a predetermined number of the same item - one pallet holds soup and another pallet holds cereal) and as pallets leave the storage and retrieval system the pallets may contain any suitable number and combination of different items (e.g. each pallet may hold different types of items - a pallet holds a combination of soup and cereal) . In the embodiments the storage and retrieval system described herein may be applied to any environment in which items (e.g. goods units holding at least one product package therein) are stored and retrieved.

[00035] The storage and retrieval system 100 may be configured for installation in, for example, existing warehouse structures or adapted to new warehouse structures. In the embodiments, the storage and retrieval system 100 may be substantially similar to that described in, for example, United States Provisional Patent Application entitled "WAREHOUSING SCALABLE STORAGE STRUCTURE" with Attorney Docket Number 1127P014551-US (-#1) (Ser. No. 61/423,340) and filed on December 15, 2010 (now US Pat. App . No. 13/326,674 with Attorney Docket Number 1127P014551-US (PAR) filed on December 15, 2011), and United States Patent Application Number 12/757,381, entitled "STORAGE AND RETRIEVAL SYSTEM" filed on April 9, 2010 the disclosures of which are incorporated herein by reference in their entireties. In one example, the storage and retrieval system 100 may include in- feed and out-feed transfer devices, such as stations 170, 160, multilevel vertical conveyors or picking devices 150A, 150B (MVCs), a storage structure 130, and a number of autonomous vehicular transports or robots 110 (referred to herein as "bots") that may also operate as transfer devices. In the embodiments the storage and retrieval system may also include transfer devices including robot or bot transfer stations 6140 (Figs. 6A-6D) which may be located at, for example bot stations 140A, 140B that may provide an interface between the bots 110 and the multilevel vertical conveyors 150A, 150B. In the embodiments, any suitable transfer device may be provided at any location and on either side or level of MVC 150A, 150B to remove or pick material from or replace or place material to MVC 150A, 150B at any shelf or platform level or location or otherwise. The in-feed transfer stations 170 and out-feed transfer stations 160 may operate together with their respective multilevel vertical conveyors 150A, 150B for bi-directionally transferring items to and from one or more levels of a multi-level storage structure 130. It is noted that while the multilevel vertical conveyors are described herein as being dedicated inbound conveyors 150A and outbound conveyors 150B, in the embodiments each of the conveyors 150A, 150B may be used for both inbound and outbound transfer of case units/items from the storage and retrieval system. The multilevel vertical conveyors 150 may be any suitable lifting devices for transporting case units between levels of the storage and retrieval system. Some non-limiting suitable examples of multilevel vertical conveyors can be found in, for example, United States Provisional Patent Application entitled "LIFT INTERFACE FOR STORAGE AND RETRIEVAL SYSTEMS" with Attorney Docket Number 1127P014525-US (PAR) and filed on December 15, 2010, and United States Patent Application Number 12/757,354, entitled "LIFT INTERFACE FOR STORAGE AND RETRIEVAL SYSTEMS" and filed on April 9, 2010 (the disclosures of which are incorporated by reference herein in their entireties) and United States Patent Application Number 12/757,220, entitled "STORAGE AND RETRIEVAL SYSTEM," (previously incorporated by reference) . For example, the multilevel vertical conveyors 150A, 150B may have any suitable number of support shelves 250 (Figs. 18A, 18B) for transporting the case units to a predetermined level 261-264 (Fig. 2) of the storage and retrieval system 100. The support shelves 250 may have slatted supports configured to allow, for example, fingers of a transfer arm 110A (Fig. 18A) of the bots 110 to pass between the slats for transferring case units 101 (Fig. 18A) to and from the conveyor. In alternate embodiments, case units may be indirectly transferred between the bots 110 and the multilevel vertical conveyors 150A, 150B as described in, for example, United States Patent Application Number 12/757,220, entitled "STORAGE AND RETRIEVAL SYSTEM," (previously incorporated by reference) . It is noted that in the embodiments transfer of case units between the bots 110 and multilevel vertical conveyors may occur in any suitable manner. It is noted that while multilevel vertical conveyors are described herein in other aspects the conveyors may be any suitable conveyors or transfer/picking devices or transfer/picking devices having any suitable transport path orientation.

[00036] As may be realized, the storage and retrieval system 100 may include multiple in-feed and out-feed multilevel vertical conveyors 150A, 150B that are accessible by, for example, bots 110 that may be disposed on each level of the multi-level storage structure 130 so that the bots 110 on a respective level can traverse an entirety of that level for transferring one or more case unit(s) can be transferred from a multilevel vertical conveyor 150A, 150B to each storage space on a respective level and from each storage space to any one of the multilevel vertical conveyors 150A, 150B on a respective level. The bots 110 may be configured to transfer the case units between the storage spaces on storage racks 600 (Fig. 18B) and the multilevel vertical conveyors with one pick (e.g. substantially directly between the storage spaces and the multilevel vertical conveyors) . By way of further example, the designated bot 110 picks the case unit(s) from a shelf of a multilevel vertical conveyor, transports the case unit(s) to a predetermined storage area of the storage structure 130 and places the case unit(s) in the predetermined storage area (and vice versa) .

[ 00037 ] The bots 110 may be configured to place items, such as the above described retail merchandise, into picking stock in the one or more levels of the storage structure 130 and then selectively retrieve ordered items for shipping the ordered items to, for example, a store or other suitable location as described in United States Patent Application Number 12/757,312, entitled "AUTONOMOUS TRANSPORTS FOR STORAGE AND RETRIEVAL SYSTEMS" filed on April 9, 2010, the disclosure of which is incorporated by reference herein in its entirety. Other suitable examples of bots are described in, for example, United States Provisional Patent Application entitled "BOT PAYLOAD ALIGNMENT AND SENSING" with Attorney Docket Number 1127P014263- US (-#1) (Ser. No. 61/423, 220) and filed on December 15, 2010 (now Attorney Docket Number 1127P014263-US (PAR) with U.S. serial number 13/327,040 filed on December 15, 2011), United States Provisional Patent Application entitled "AUTOMATED BOT WITH TRANSFER ARM" with Attorney Docket Number 1127P014264-US (- #1) (Ser. No. 61/423, 365) and filed on December 15, 2010 (now Attorney Docket Number 1127P014264-US (PAR) with U.S. serial number 13/326,952 filed on December 15, 2011), United States Provisional Patent Application entitled "BOT HAVING HIGH SPEED STABILITY" with Attorney Docket Number 1127P014266-US (-#1) (Ser. No. 61/423,359) and filed on December 15, 2010 (now Attorney Docket Number 1127P014266-US (PAR) with U.S. serial number 13/326,447 filed on December 15, 2011), and United States Provisional Patent Application entitled "AUTOMATED BOT TRANSFER ARM DRIVE SYSTEM" with Attorney Docket Number 1127P014265-US (- #1) (Ser. No. 61/423, 388) and filed on December 15, 2010 (now Attorney Docket Number 1127P014265-US (PAR) with U.S. serial number 13/326,993 filed on December 15, 2011), the disclosures of which are incorporated by reference herein in their entireties. As described above, the bots 110 may interface in any suitable manner with the multilevel vertical conveyors 150A, 150B. In the embodiments, the bots 110 may be configured to interface directly with the shelves of the multilevel vertical conveyors 150A, 150B such as through, for example, extension of a transfer arm 110A (Fig. 18A) of the bot (which may have fingers for interfacing with slatted support shelves of the multi-level vertical conveyors) relative to a frame of the bot. In the embodiments the bots 110 may interface indirectly with the multilevel vertical conveyors 150A, 150B in any other suitable manner such as through, for example, bot transfer stations 6140 disposed on a respective level of the multi-level storage structure 130. [00038] As described above, the storage structure 130 may include multiple levels of storage rack modules 600 (Fig. 18B) where, in the embodiments, each level includes an array of storage spaces (arrayed on the multiple levels and in multiple rows on each level) respective picking aisles 130A formed between the rows of storage spaces and at least one transfer deck 130B. In the embodiments, the picking aisles 130A and transfer decks 130B may be arranged for allowing the bots 110 to traverse for allowing the bots 110 to traverse respective levels of the storage structure 130 for transferring case units between any of the storage areas of the storage structure 130 and any shelf of any multilevel vertical conveyor 150A, 150B. The picking aisles 130A, and transfer decks 130B also allow the bots 110 to place case units into picking stock and to retrieve ordered case units. In the embodiments each level may include bot transfer stations 6140 for allowing the exchange of items between the multilevel vertical conveyors 150A, 150B and a bot on a respective storage level of the storage structure 130. As may be realized, the storage and retrieval system may be configured to allow random accessibility to the storage spaces. For example, all storage spaces in the storage structure 130 may be treated substantially equally when determining which storage spaces are to be used when picking and placing case units from/to the storage structure 130 such that any storage space of sufficient size can be used to store items. The storage structure 130 may also be arranged such that there is no vertical or horizontal array partitioning of the storage structure. For example, each multilevel vertical conveyor 150A, 150B is common to all storage spaces (e.g. the array of storage spaces) in the storage structure 130 such that any bot 110 can access each storage space and any multilevel vertical conveyor 150A, 150B can receive case units from any storage space on any level so that the multiple levels in the array of storage spaces substantially act as a single level (e.g. no vertical partitioning) . The multilevel vertical conveyors 150A, 150B can also receive case units from any storage space on any level of the storage structure 130 (e.g. no horizontal partitioning) . It is noted that in the embodiments the storage and retrieval system may be configured so that each multilevel vertical conveyor serves a predetermined area of the array of storage spaces. The storage structure 130 may be substantially similar to the storage structure described in United States Provisional Patent Application "WAREHOUSING SCALABLE STORAGE STRUCTURE" with Attorney Docket Number 1127P014551-US (-#1) (Ser. No. 61/423,340) and filed on December 15, 2010 (now Attorney Docket Number 1127P014551-US (PAR) with U.S. serial number 13/326,674 filed on December 15, 2011), and United States Patent Application Number 12/757,381, entitled "STORAGE AND RETRIEVAL SYSTEM, " previously incorporated by reference in their entireties .

[00039] One or more central system control computers (e.g. control server) 120 may coordinate or otherwise control the operation of the multilevel vertical conveyors 150A, 150B with other suitable features of the storage and retrieval system 100 in a manner substantially similar to that described in United States Patent Application Number 12/757,337, entitled "CONTROL SYSTEM FOR STORAGE AND RETRIEVAL SYSTEMS," and United States Patent Application Number 12/757,220, entitled "STORAGE AND RETRIEVAL SYSTEM," both filed on April 9, 2010, the disclosures of which are incorporated herein by reference in their entireties. For example, the control server 120 may control the operation of the storage and retrieval system 100 through, for example, any suitable communications network 180.

[00040] The storage structure 130 of the embodiments may be arranged such that if desired there is substantially no vertical or horizontal array partitioning of the storage structure. For example, each multilevel vertical conveyor 150A, 150B may be common to all or substantially all storage spaces (e.g. the array of storage spaces) in the storage structure 130 such that any bot 110 can access each storage space and any multilevel vertical conveyor 150A, 150B can receive case units from any storage space on any level so that the multiple levels in the array of storage spaces substantially act as a single level (e.g. no vertical partitioning) . Conversely case units from any shelf of each multilevel vertical conveyor 150A, 150B can be transferred to any or each storage space throughout the storage structure or to each storage space of any level of the storage structure. The multilevel vertical conveyors 150A, 150B can also receive case units from any storage space on any level of the storage structure 130 (e.g. no horizontal partitioning). Suitable examples of multilevel vertical conveyors can be found in, for non-limiting exemplary purposes, United States Patent Application Number 12/757,354, entitled "LIFT INTERFACE FOR STORAGE AND RETRIEVAL SYSTEMS," and United States Patent Application Number 12/757,220, entitled "STORAGE AND RETRIEVAL SYSTEM, " the disclosures of which are incorporated by reference herein in their entireties.

[ 00041 ] Referring now to Fig. 2A, the multilevel vertical conveyors will be described in greater detail. It is noted that the input multilevel vertical conveyor 150A and associated in- feed transfer stations 170 are described, however, the out-feed multilevel vertical conveyors 150B, bot transfer stations 6140 and out-feed transfer stations 160 may be substantially similar to that described below for their in-feed counterparts but for the direction of material flow out of the storage and retrieval system 100 rather than into the storage and retrieval system 100. As may be realized, the storage and retrieval system 100 may include multiple in-feed and out-feed multilevel vertical conveyors 150A, 150B that are accessible by, for example, bots 110 on each level of the storage and retrieval system 100 so that one or more case unit(s) can be transferred from a multilevel vertical conveyor 150A, 150B to each storage space on a respective level and from each storage space to any one of the multilevel vertical conveyors 150A, 150B on a respective level. The bots 110 may be configured to transfer the case units (alone or in combinations) between the storage spaces and the multilevel vertical conveyors with one pick (e.g. substantially directly between the storage spaces and the multilevel vertical conveyors). The case unit(s) (which may be uncontained) being so transferred at one time (e.g. as a unit) may be referred to generally as a pickface. By way of further example, the designated bot 110 picks the case unit(s) or pickface from a shelf of a multilevel vertical conveyor, transports the case unit(s) to a predetermined storage area of the storage structure 130 and places the case unit(s) or pickface in the predetermined storage area (and vice versa) .

[00042] Generally, the multilevel vertical conveyors include payload shelves 730 (Figs. 2A-4) attached to chains or belts that form continuously moving or circulating vertical loops (the shape of the loop shown in the Figs, is merely exemplary and in the embodiments the loop may have any suitable shape including rectangular and serpentine) that move at a substantially constant rate, so that the shelves 730 use what may be referred to as the "paternoster" principle of continuous conveyance, with loading and unloading performed at any point in the loop without slowing or stopping. In the embodiments, it should be understood that the payload shelves 730 can be driven by any suitable drive mechanism such as tracks, gears, etc. The multilevel vertical conveyors 150A, 150B may be controlled by a server, such as for example, control server 120, or any other suitable controller. One or more suitable computer workstations 700 may be connected to the multilevel vertical conveyors 150A, 150B and the server 120 in any suitable manner (e.g. wired or wireless connection) for providing, as an example, inventory management, multilevel vertical conveyor functionality and control, and customer order fulfillment. As may be realized, the computer workstations 700 and/or server 120 may be programmed to control the in-feed and/or out-feed conveyor systems. In the embodiments, the computer workstations 700 and/or server 120 may also be programmed to control the transfer stations 140. In the embodiments, one or more of the workstations 700 and control server 120 may include a control cabinet, a programmable logic controller and variable frequency drives for driving the multilevel vertical conveyors 150A, 150B. In the embodiments the workstations 700 and/or control server 120 may have any suitable components and configuration. In the embodiments, the workstations 700 may be configured to substantially remedy any exceptions or faults in the in-feed and/or out-feed conveyor systems substantially without operator assistance and communicate fault recovery scenarios with the control server 120 and/or vice versa.

[ 00043 ] Referring still to Fig. 2A and also to Fig. 4, in the embodiments, the multilevel vertical conveyors 150A may include a frame 710 configured to support driven members such as, for example, chains 720. The chains 720 may be coupled to the shelves 730, which are movably mounted to the frame 710 such that the chains 720 effect substantially continuous movement of the shelves 730 around the frame 710. In the embodiments, any suitable drive link, such as for example, belts or cables may be used to drive the shelves 730. Each shelf 730 may include, for example, supports 930 and a platform 900. The supports 930 may extend from the platform 900 and be configured for attaching and mounting the shelf 730 to, for example, one or more drive chains 720. The platform 900 may include, for example, any suitably shaped frame 911, which in this example is generally "U" shaped (e.g. having lateral members connected by a span member at one end), and a payload or pickface support surface (e.g. in one aspect of the embodiments formed of any suitable number of spaced apart fingers 910 extending from the frame 911) . In other aspects, the support surface of the multilevel vertical conveyor may have any suitable configuration, with or without spaced fingers or slats. The fingers 910 may be configured for supporting the pickfaces 750, 752 (Fig. 2B) where each pickface comprises at least one uncontained case unit. In the embodiments, each of the fingers 910 may be removably fastened to a frame 911 for facilitating replacement or repair of individual fingers 910. The fingers 910, frame 911 (and supports 930) may form an integral structure or platform that defines the seating surface that contacts and supports the uncontained case units. It is noted that the shelf 730 illustrates only a representative structure and in the embodiments, the shelves 730 may have any suitable configuration and size for transporting pickfaces 750, 752 as will be described further below. As maybe realized the fingers 910 of each of the one or more pickface support stations A-D, define the seating surface against which the one or more uncontained cases of each pickface are gated. As seen in Fig. 5, the pickfaces on the support station may have constraints to prevent movement of the pickface (s) relative to the support stations (A-D) . The spaced apart fingers 910 are configured to interface with, for example, a transfer arm or effector of the bots 110 and the in-feed transfer stations 170 for transferring the loads 750, 752 between the multilevel vertical conveyor 150A and one or more of the transfer stations 170 and bots 110. In the embodiments, the spaced apart fingers 900 may be configured to interface with bot transfer stations 6140 as described below.

[00044] The multilevel vertical conveyors 150A may also include a suitable stabilizing device (s), such as for example, driven stabilizing chains for stabilizing the shelves 730 during vertical travel. In one example, the stabilizing devices may include chain driven dogs that are engaged to the shelves in both the upward and downward directions to form, for example, a three point engagement with the shelf supports 930. The drive chains 720 for the shelves 730 and stabilizing devices may be drivingly coupled to for example, any suitable number of drive motors under the control of, for example, one or more of the computer workstations 700 and control server 120. Further examples for effecting stability of the conveyor shelves 730 in the embodiments are described later in the specification.

[00045] In the embodiments there may be any suitable number of shelves 730 mounted and attached to the drive chains 720. As can be seen in Fig. 2B each shelf 730 may be configured to carry, for exemplary purposes only, at least two separate pickfaces 750, 752 in corresponding positions A, C on the shelf 730 (e.g. a single vertical conveyor is functionally equivalent to multiple individually operated conveyors arranged adjacent one another) . In the embodiments, as can be seen in Fig. 5 the shelves 730' may be configured to carry, for exemplary purposes only, four separate pickfaces 750-753 in corresponding positions A-D. In the embodiments, each shelf may be configured to carry more or less than four separate loads. As described above, each pickface may comprise one or more uncontained case units and may correspond to the load of a single bot 110. As may be realized, the space envelope or area platform of each pickface may be different. By way of example, uncontained cases, such as those directly transported by the multilevel vertical conveyors have various different sizes (e.g. differing dimensions) . Also, as noted each pickface may include one or more uncontained cases. Thus, the length and width of each pickface carried by the multilevel vertical conveyors may be different. In the embodiments each pickface may be broken between, for example, bots 110 where different portions of the pickface are transported by more than one bot 110 on, for example, different levels of the storage structure 130. As may be realized when a pickface is broken each portion of the broken pickface may be considered as a new pickface by the storage and retrieval system 100. For exemplary purposes only, referring to Figs. 3A, 3B the shelves 730 of the multilevel vertical conveyors 150A, 150B may be spaced from each other by a predetermined pitch P to allow for placement or removal of loads 810, 820 from the substantially continuously moving shelves 730 as will be described below.

[00046] Referring now to Fig. 5, and as described above, the multilevel vertical conveyors, such as conveyor 150A are supplied with case units 1000 from in-feed transfer stations 170 (Fig. 1) . As described above, the in-feed transfer stations 170 may include one or more of depalletizing workstations, conveyors 240, conveyor interfaces/bot load accumulators 1010A, 1010B and conveyor mechanisms 1030. As can be seen in Fig. 5, case units 1000 are moved from, for example depalletizing workstations by conveyors 240. In this example, each of the positions A-D is supplied by a respective in-feed transfer station. As may be realized, while the transfer of case units is being described with respect to shelves 730' it should be understood that transfer of case units to shelves 730 occurs in substantially the same manner. For example, position A may be supplied by in- feed transfer station 170A and position C may be supplied by in- feed transfer station 170B. Referring also to Fig. 2A the in- feed transfer stations 170A, 170B, for supplying similar sides of the shelf 730 (in this example positions A and C, which are disposed side by side, form a first side 1050 of the shelf 730 and positions B and D, which are disposed side by side, form a second side 1051 of the shelf 730), may be located one above the other in a horizontally staggered stacked arrangement (an exemplary stacked arrangement is shown in Fig. 2A) . In the embodiments, the stacked arrangement may be configured so that the in-feed transfer stations are disposed vertically in-line one above the other and extend into the multilevel vertical conveyors by different amounts for supplying, for example, positions A and B or positions C and D where positions A and B (and positions C and D) are disposed one in front of the other, rather than side by side. In the embodiments, the in-feed transfer stations may have any suitable configuration and positional arrangement. As can be seen in Fig. 5, the first side 1050 and second side 1051 of the shelf 730 are loaded (and unloaded) in opposing directions such that each multilevel vertical conveyor 150A is located between respective transfer areas 295A, 295B where the first side 1050 interfaces with a transfer area 295B and the second side 1051 interfaces with transfer area 295A.

[00047] In the embodiments, the accumulators 1010A, 1010B may be configured to form the case units 1000 into the individual pickfaces 750-753 prior to loading a respective position A-D on the multilevel vertical conveyor 730. In the embodiments, the computer workstation 700 and/or control server 120 may provide instructions or suitably control the accumulators 1010A, 1010B (and/or other components of the in-feed transfer stations 170) for accumulating a predetermined number of items to form the pickfaces 750-753. The accumulators 1010A, 1010B may align the case units in any suitable manner (e.g. making one or more sides of the items flush, etc.) and, for example, abut the items together. The accumulators 1010A, 1010B may be configured to transfer the pickfaces 750-753 to respective conveyor mechanisms 1030 for transferring the pickfaces 750-753 to a respective shelf position A-D. In the embodiments the conveyor mechanisms 1030 may include belts or other suitable feed devices for moving the pickfaces 750-753 onto transfer platforms 1060. The transfer platforms 1060 may include spaced apart fingers for supporting the pickfaces 750-753 where the fingers 910 of the shelves 730 are configured to pass between the fingers of the transfer platforms 1060 for lifting (or placing) the pickfaces 750-753 from the transfer platforms 1060. In the embodiments, the fingers of the transfer platforms 1060 may be movable and serve to insert the pickfaces 750-753 into the path of the shelves 730 in a manner similar to that described below with respect to the bot transfer stations 6140. In the embodiments the in-feed transfer stations 170 (and out-feed transfer stations 160) may be configured in any suitable manner for transferring case units (e.g. the pickfaces formed by the case units) onto or from respective multilevel vertical conveyors 150A, 150B.

[ 00048 ] It is noted that while the interface between the bot transfer stations 6140 and the multilevel vertical conveyors 150A, 150B are described it should be understood that interfacing between the bots 110 and the multilevel vertical conveyors 150A, 150B occurs in a substantially similar manner (e.g. as described in United States Patent Application Number 12/757,312, entitled "AUTONOMOUS TRANSPORTS FOR STORAGE AND RETRIEVAL SYSTEMS," previously incorporated by reference herein in its entirety) . For exemplary purposes only, referring now to Figs. 2B and 6A-6D, the multilevel vertical conveyors 150A transfer pickfaces 750, 752 from, for example, the in-feed transfer stations 170 (or any other suitable device or loading system) to, for example, the bot transfer stations 6140 associated with each of the levels in the storage structure 130. In other examples, the pickfaces 750, 752 may be transferred directly from the multilevel vertical conveyors 150A to the bots 110 as described below. As may be realized, the bot transfer stations 6140 are disposed on respective levels of the storage structure adjacent the path of travel of the shelves 730 of a respective multilevel vertical conveyor 150A. In the embodiments, there may be a bot transfer station 140 corresponding to each of the positions A and C on the shelves 730 (and positions A-D with respect to shelf 730') . For example, a first bot transfer station 140 may remove load 750 from position A on shelf 730 while another bot transfer station 140 may remove pickface 752 from position C on shelf 730 and so on. In the embodiments, one bot transfer station 140 may serve to remove or place case units in more than one position A, C on the shelves 730. For example, one bot transfer station 140 may be configured for removing pickfaces 750, 752 from one or more of positions A, C of shelf 730. In the embodiments, referring also to Fig. 5, one bot transfer station 140 may be configured for removing pickfaces 750, 752 from one or more of positions A, C on a first side 1050 of the shelf 730' while another bot transfer station 140 may be configured to remove pickfaces 751, 753 from one or more positions B, D on a second side 1051 of the shelf 730'. In the embodiments the bot transfer stations 6140 may have any suitable configuration for accessing any suitable number of positions A-D of the shelves 730, 730'.

[00049] Each bot transfer station 140 may include a frame 1100, one or more drive motors 1110 and a carriage system 1130. The frame 1100 may have any suitable configuration for coupling the bot transfer station 140 to, for example, any suitable supporting feature of the storage structure 130, such as a horizontal or vertical support. The carriage system 1130 may be movably mounted to the frame 1100 through, for example, rails 1120 that are configured to allow the carriage system 1130 to move between retracted and extended positions as shown in Figs. 6A and 6B. The carriage system 1130 may include a carriage base 1132 and fingers 1135. The fingers 1135 may be mounted to the carriage base 1132 in a spaced apart arrangement so that the fingers 1135 extend from the carriage base 1132 in a cantilevered fashion. It is noted that each finger 1135 may be removably mounted to the carriage base 1132 for facilitating replacement or repair of individual fingers 1135. In the embodiments the fingers and carriage base may be of unitary one- piece construction. The fingers 1135 of the bot transfer stations 6140 may be configured to pass between the fingers 910 (Fig. 4) of the shelves 730 of the multilevel vertical conveyors 150A (Fig. 1) for removing pickfaces such as pickfaces 1150 (which may be substantially similar to pickfaces 750-753) from the shelves 730. The bot transfer station 140 may also include a load positioning device 1140 that retractably extends between, for example, the spaced apart fingers 1135 in the direction of arrow 1181 for effecting positioning of the pickfaces 1150 in a predetermined orientation relative to the bot transfer station 140. In the embodiments the carriage system 1130 may have any suitable configuration and/or components. The one or more drive motors 1110 may be any suitable motors mounted to the frame 1100 for causing the extension/retraction of the carriage system 1130 and the extension/retraction of the positioning device 1140 in any suitable manner such as by, for exemplary purposes only, drive belts or chains. In the embodiments, the carriage system and positioning device may be extended and retracted in any suitable manner.

[00050] In operation, referring also to Figs. 2C, 2D, 3A and 3B, inbound pickfaces (e.g. pickfaces, which include one or more case units, that are being transferred into the storage and retrieval system) such as pickface 1150 are loaded on and will circulate around the multilevel vertical conveyor 150A and be removed from a respective conveyor by, for example, one or more bots 110 for placement in a storage area of the storage structure (Fig. 8, Blocks 8000 and 8010) . As will be described further below, in the embodiments the input loading sequencing of case units onto the multilevel vertical conveyors 150A, 150B (e.g. such as at corresponding feeder input sides of transfer stations 170 and bot transfer locations on respective storage levels) may be substantially independent from the output or unloading sequence of the multilevel vertical conveyors 150A, 150B (e.g. such as at corresponding output sides of transfer stations 160 and bot transfer locations on respective storage levels) and vice versa. In one example, the pickface 1150 may be loaded onto the shelves 730 during an upward travel of the multilevel vertical conveyor 150A and off loaded from the shelves 730 during downward travel of the multilevel vertical conveyor 150A. By way of example, multilevel vertical conveyor shelves 730i and 730ii (Fig. 2D) may be loaded sequentially, but when unloaded, shelf 730ii may be unloaded before shelf 730i. It is noted that the shelves 730 may be loaded through one or more cycles of the multilevel vertical conveyor. In the embodiments the pickfaces may be loaded or off loaded from the shelves 730 in any suitable manner. As may be realized, the position of the case units on the multilevel vertical conveyor shelf 730 defines the pickface position that the bot 110 picks from. Accordingly, as may be realized, shudder of the pickface conveyor is highly undesired, especially in that a pickface (s) may remain on the conveyor for more than one cycle after being loaded. The bot may be configured to pick any suitable load or pickface from the shelf 730 regardless of the pickface position on the shelf 730 or the size of the pickface. In the embodiments, the storage and retrieval system 100 may include a bot positioning system for positioning the bot adjacent the shelves 730 for picking a desired pickface from a predetermined one of the shelves 730 (e.g. the bot 110 is positioned so as to be aligned with the pickface) . The bot positioning system may also be configured to correlate the extension of a bot transfer arm with the movement (e.g. speed and location) of the shelves 730 so that the transfer arm is extended and retracted to remove (or place) pickfaces from predetermined shelves 730 of the multilevel vertical conveyors 150A, 150B. For exemplary purposes only, the bot 110 may be instructed by, for example, the computer workstation 700 or control server 120 (Fig. 2A) to extend the transfer arm into the path of travel of the pickface 1150. As the pickface 1150 is carried by the multilevel vertical conveyor 150A in the direction of arrow 860 fingers of the bot transfer arm (which may be substantially similar to fingers 1135 of the bot transfer station 140) pass through the fingers 910 of the shelf 730 for transferring the pickface 1150 from the shelf 730 to the carriage system 1135 (e.g. the pickface 1150 is lifted from the fingers 910 via relative movement of the shelf 730 and the bot transfer arm) . As may be realized, the pitch P between shelves may be any suitable distance for allowing the transfer of pickfaces between the multilevel vertical conveyor and the bots 110 while the shelves 730 are circulating around the multilevel vertical conveyor at a substantially continuous rate. The bot transfer arm may be retracted (in a manner substantially similar to that shown in Figs. 6C, 6D with respect to the bot transfer station 140) so that the pickface 1150 is no longer located in the path of travel of the shelves 730 of the multilevel vertical conveyor 150A. It is noted that in the embodiments, where the bot transfer stations 6140 are used, the positioning device 1140 may be extended through the fingers 1135 and the carriage system 1130 (Figs. 6A-6D) may be moved in the direction of arrow 1180 for abutting the pickface 1150 against the positioning device 1140 effecting positioning of the pickface 1150 in a predetermined orientation relative to, for example, the bot transfer station 140. The carriage system 1130 may be fully retracted as shown in Fig. 6D for transfer of the pickface 1150 to a bot 110.

[00051] Referring to Figs. 2D and 3B, for transferring loads in the outbound direction (e.g. moving pickfaces from or out of the storage and retrieval system) the bots 110 pick one or more pickface, such as pickface 1150, from a respective predetermined storage area of the storage structure (Fig. 8, Block 8020) . The pickfaces may be extended into the path of the shelves 730 of the multilevel vertical conveyor 150B (which is substantially similar to conveyor 150A) by the transfer arm of bot 110 through an extension of the bot transfer arm relative to a frame of the bot 110. It is noted that the pickfaces, such as pickface 1150, may be placed on the multilevel vertical conveyor 150 in a first predetermined order sequence (Fig.8, Block 8030). The first predetermined order may be any suitable order. The substantially continuous rate of movement of the shelves 730 in the direction of arrow 870 cause the fingers 910 of the shelf 730 to pass through the fingers of the bot transfer arm such that the movement of the shelf 730 effects lifting the pickface 1150 from the fingers of the bot transfer arm. The pickface 1150 travels around the multilevel vertical conveyor 150B to an out- feed transfer station 160 (which is substantially similar to in- feed transfer station 170) where it is removed from the shelf 730 by a conveyor mechanism 1030 in a manner substantially similar to that described above. The pickfaces may be removed from the multilevel vertical conveyor 150B by, for example the out-feed transfer stations 160 in a second predetermined order sequence that may be different and independent from the first predetermined order sequence (Fig. 8, Block 8040) . The second predetermined order sequence may depend on any suitable factors such as, for example, the store plan rules described below. As noted before, to effect transfer of pickface (s) between conveyor stations and bot transfer arm or transfer station in a robot repeatable manner where pickface size and shape may vary with each transfer it is desired that the motion of the pickface (s) on the conveyor be substantially free of shudder or judder. [00052] It is noted that the respective transfer of pickfaces between the multilevel vertical conveyors 150A, 150B and the in- feed and out-feed transfer stations 170, 160 may occur in a manner substantially similar to that described above with respect to the bots 110 and bot transfer stations 6140. In the embodiments transfer of pickfaces between the multilevel vertical conveyors 150A, 150B and the in-feed and out-feed transfer stations 170, 160 may occur in any suitable manner.

[00053] As can be seen in Figs. 2C and 2D the shelves 730 of the multilevel vertical conveyors 150A, 150B are loaded and unloaded by the in-feed and out-feed transfer stations 170, 160 and the bots 110 from a common side of the shelf 730. For example, the shelves are loaded and unloaded in the common direction 999 (e.g. from only one side of the shelf 730) . In this example, to facilitate loading the multilevel vertical conveyor from only one side of the shelf, the multilevel vertical conveyors 150A, 150B circumscribe a respective one of the in-feed and out-feed transfer stations 170, 160 so that the pickfaces 1150 travel around the in-feed and out-feed transfer stations 170, 160. This allows the in-feed and out-feed transfer stations 170, 160 to be placed on the same side of the shelves 730 as the bots 110 for transferring pickfaces (and the case units therein) to and from the multilevel vertical conveyors 150A, 150B.

[00054] It is noted that the control server 120 may be configured to order the removal of case units from the storage and retrieval system for any suitable purpose, in addition to order fulfillment. In the embodiments, the distribution (e.g. sortation) of case units in the storage and retrieval system is such that the case units in the conveyor can be provided for delivery to a palletizing station in any suitable order at any desired rate using only two sortation sequences. The control server 120 may also be configured to incorporate, for example, store plan rules when fulfilling orders so that the cases are provided by the bots 110 to respective multilevel vertical conveyors 150B in a first predetermined sequence (e.g. a first sortation of case units for optimizing the utilization and throughputs of the bots) and then removed from the respective multilevel vertical conveyors 150B in a second predetermined sequence (e.g. a second sortation of case units for optimizing the utilization and throughput of a palletizing device and to permit arrangement of cases within the pallet in a manner optimized for facilitating unloading and distribution at a retail delivery point or facility) so that the case units may be placed on pallets or other suitable shipping containers/devices) in a predetermined order for building mixed pallets (see e.g. Fig. 8 described above) . For example, in the first sortation of case units the bots 110 may pick respective case units (e.g. case unit) in any order. The bots 110 may traverse the picking aisles and transfer deck (e.g. circulate around the transfer deck) with the picked item until a predetermined time when the item is to be delivered to a predetermined multilevel vertical conveyor 150B. In the second sortation of case units, once the case units are on the multilevel vertical conveyor 150B the case units may circulate around the conveyor until a predetermined time when the items are to be delivered to the out-feed transfer station 160. Referring to Fig. 7, it is noted that the order of case units delivered to the pallets may correspond to, for example, store plan rules 9000. The store plan rules 9000 may incorporate, for example, an aisle layout in the customer's store or a family group of case units corresponding to, for example, a particular location in the store where the pallet will be unloaded or a type of goods. The order of case units delivered to the pallets may also correspond to characteristics 9001 of the case units such as, for example, compatibility with other case units, dimensions, weight and a durability of the case units. For example, crushable case units may be delivered to the pallet after heavier more durable case units are delivered to the pallet. The first and second sortations of the case units allow for the building of mixed pallets 9002 as described below.

[00055] The control server 120 in combination with the structural/mechanical architecture of the storage and retrieval system enables maximum load balancing. As described herein, the storage spaces/storage locations are decoupled from the transport of the case units through the storage and retrieval system. For example, the storage volume (e.g. the distribution of case units in storage) is independent of and does not affect throughput of the case units through the storage and retrieval system. The storage array space may be substantially uniformly distributed with respect to output. The horizontal sortation (at each level) and high speed bots 110 and the vertical sortation by the multilevel vertical conveyors 150B substantially creates a storage array space that is substantially uniformly distributed relative to an output location from the storage array (e.g. an out-feed transfer station 160 of a multilevel vertical conveyor 150B) . The substantially uniformly distributed storage space array also allows case units to be output at a desired substantially constant rate from each out-feed transfer station 160 such that the case units are provided in any desired order. To effect the maximum load balancing, the control architecture of the control server 120 may be such that the control server 120 does not relate the storage spaces within the storage structure 130 (e.g. the storage array) to the multilevel vertical conveyors 150B based on a geographical location of the storage spaces (which would result in a virtual partitioning of the storage spaces) relative to the multilevel vertical conveyors 150B (e.g. the closest storage spaces to the multilevel vertical conveyor are not allocated to cases moving from/to that multilevel vertical conveyor). Rather, the control server 120 may map the storage spaces uniformly to each multilevel vertical conveyor 150B and then select bots 110, storage locations and output multilevel vertical conveyor 150B shelf placement so that case units from any location in the storage structure come out from any desired multilevel vertical conveyor output (e.g. at the out-feed transfer stations) at a predetermined substantially constant rate in a desired order for building the mixed pallets 9002.

[00056] Referring now to Figs. 9A and 9B, there is shown feed station 141 in accordance with the embodiments. In addition to the features described below, station 141 may be substantially similar to out-feed and in-feed stations 160, 170. Feed station 141 may be an automated device that can be configured to either transfer payloads referred to as pickfaces, cases or otherwise into an MVC and onto a platform or out of an MVC from the platform. In one example, the feed station 141 interfaces, for example, the pickface builder 2010 (Figs. 10-12) to the shelves 731 (Fig. 13) of the multilevel vertical conveyor(s) 150 (Fig. 10) . In the embodiments, feed station 141 may be used to transfer material to or from any suitable device, station or otherwise. In one example, the feed station 141 receives a pickface from the pickface builder 2010. The feed station may have any suitable pickface positioning features that position a reference datum (e.g. pickface datum) of the pickface (relative to a transfer device of the feed station) at a predetermined position on the multilevel vertical conveyor shelf 731 so that the bots 110 (Fig. 1) can pick the pickfaces from the shelf 731. It is noted that the pickface datum relates the pickface to a placement position of the cases that form the pickface along a storage surface, such as e.g. the storage shelves 600, of the storage and retrieval system. The transfer device of the feed station 141 may translate to effect the handoff of the pickface to the shelf 731. In the embodiments the handoff may occur in any suitable manner. The feed station 141 may have any suitable controller to operate the transfer device in a predetermined sequence with the multilevel vertical conveyor 150 and interact with the pickface builder 2010.

[00057] In one aspect of the disclosed embodiment, feed station 141 may have driven roller bed 2012 to transfer in the x-axis 2014. Feed station 141 may have a set of extendable or retractable fingers and payload bed 2020 (or other suitable effector for picking/placing pickfaces on/off the multilevel vertical conveyor) that traverses in the y-axis 2022 and PLC with controls 2030. Rollers 2012 may be selectively driven by drive motor and transmission 2040 where sensors may be provided to detect the presence, edges or otherwise of the payload to be transported and used in conjunction with encoders or otherwise with controller 2030 to position the payload as desired. Gear motor 2050 may be provided to selectively traverse bed 2020 in the y direction 2022. A z axis drive (not shown) may be provided to move bed 2020 in the z direction 2024 to effect a pick or place to rollers 2012. Feed station's 141 y-axis motion may be coordinated to transfer loads, for example, payloads, cases or otherwise from or onto the MVC platforms 730, 731 by positioning feed station fingers 2020 to accept or pass off the payload to or from the platform 730, 731. Feed station 141 transfers the payload between x and y-axis 2014, 2022 through a z-axis 2024 lift of the fingers 2020. With a pickface payload on rollers 2012, once fingers 2020 are lifted, a y-axis move in direction 2022, that may extend fingers 2020, may take place to allow the payload to be transported to the appropriate MVC (in a manner similar to that shown in Fig. 5) . An opposite sequence may take place when transferring a payload from an MVC platform, for example, platform 730 or 731 as will be described, to feed station 141 where fingers 2020 retract in the y-axis direction 2022 and then lower in the z-axis direction 2024 to transfer a pickface payload to the roller bed 2012 for removal. As such, feed station 141 provides for an automated device that can be configured to either transfer payloads or cases into an MVC and onto a platform or out of an MVC from the platform. As may be realized, the pickface payload being output by an output MVC from the storage and retrieval system different than the input pickface payload. For example, as input pickface transported and loaded to a corresponding storage space in the storage structure and comprising more than one case(s) may be portioned during retrieval so that a sub-set of the input pickface are retrieved, and the retrieved pickface is different than the input pickface.

[00058] Referring now to Figs. 10-14C there is shown pickface builder arrangement 2002 having pickface builder 2010 and feed station 141. Pickface builder 2010, which may hereinafter be referred to as PFB may be an automated device to align a single or multiple cases or pickface units to form the single or multiple pickface payload for picking, placing or otherwise to be transferred in any suitable direction or otherwise and to be used in conjunction with any suitable conveyance, transport device or otherwise. Although pickface builder 2010 may be described with respect to transfer station 141, pickface builder 2010 may be utilized with or without any transfer station, transport system or otherwise. Further, more or less features may be provided with pickface builder 2010. For example, transport features such as associated with transfer station 141 or otherwise may be incorporated into pickface builder 2010 and more or less sensing, alignment or other suitable features may be provided.

[00059] The pickface builder 2002 may be located in any suitable area of the storage and retrieval system 100 in-feed conveyance system. In one example, the pickface builder 2010 may be located between the conveyor 240 (see also Fig. 5) and the multilevel vertical conveyor 150. For example, in the embodiments the pickface builder 2010 may be arranged downstream from (e.g. adjacent to or offset from) a turn in elbow 240E of the conveyor 240 (e.g. to change a direction of the flow of cases for interfacing with the multilevel vertical conveyor 150) and upstream of the feed station 141. In the embodiments, the conveyor 150 may not have a turn in elbow in which case the pickface builder may interface with a substantially straight conveyor. In the embodiments the pickface builder may be located downstream the multilevel vertical conveyors and upstream of a bot interface where the pickfaces are transferred to the bots. The pickface builder 2010 may be configured to arrange and compile a set (e.g. one or more) of cases to build a pickface of cases (e.g. contained or uncontained cases) . Each pickface is picked (as a unit) by bots 110 for placement and retrieval in the storage racks of the storage structure 130 and/or the shelves 731 of the multilevel vertical conveyors 150. In the embodiments shown in the figures the pickface builder 2010 communicates with the multilevel vertical conveyors 150 through the feed station 141 so that pickfaces are transferred (as a unit) to the multilevel vertical conveyors 150 after the pickface is built. In the embodiments, each pickface builder 2010 may be linked to a dedicated position of the multilevel vertical conveyor shelves 731, such as where the shelves 731 have more than one pickface holding location 2280, 2290 (Fig. 13) . In the embodiments each pickface builder may be configured to selectively feed cases to each pickface holding location 2280, 2290 of the shelves 731 (e.g. a common pickface builder for one or more shelf positions) . In the embodiments, the pickface builder 2010 may adjoin a side of a respective feed station 141 and be disposed so that cases of the pickface exit the pickface builder, through any suitable drive unit, and enter the feed station 141 in a direction that is angled (e.g. substantially orthogonal) relative to the direction in which the feed station transfers the pickface to the multilevel vertical conveyor. In the embodiments, the cases may be arranged at any suitable angle relative to the direction or travel of the pickface from the feed station 141 to the multilevel vertical conveyor 150. The pickface builder 2010 transfers to and collates the aligned cases (e.g. pickfaces) on the feed station 141 for subsequent transfer to the multilevel vertical conveyor 150.

[00060] Pickface builder 2010 may have x-y axis pusher 2100 (or a single axis, e.g. y axis, pusher), y-axis snugger 2120, roller bed 2140 and PLC controls 2160. In one example, the pusher 2100 may have any suitable type and number of pusher plates 2100P for pushing cases across a support surface (which may be movable) of the pickface builder 2010. The pusher plate (s) 2100P may be resilient and may be positioned to engage cases such that the cases can be pushed as they move along the direction of travel on the conveyor 240 (e.g. the pusher 2100 is configured to drive the pusher plates 2100P along the x and y directions) for positioning cases on the pickface builder 2010 for building the pickface. The x-y axis pusher 2100 may be located to receive cases such that the direction of the flow of cases from the conveyor 240 is towards the pusher (e.g. the conveyor discharges cases substantially in front of or adjacent the pusher) . In one example, the case configuration upon receipt by the pusher 2100 may be such that a long axis of the cases is oriented to interface with the pusher 2100. In another example, the short axis of the cases may be oriented to interface with the pusher 2100 (e.g. the cases may have any suitable orientation relative to the pusher 2100) . In still other examples, the cases may have mixed orientations when interfacing with the pusher 2100 (e.g. some cases interface the pusher via a long axis of the case and other cases interface with the pusher via the short axis of the case) . The x-y axis pusher 2100 directs cases from the conveyor 240 towards the snugger 2120.

[00061] The snugger 2120 includes any suitable type and number of snugger plates 2120P that are positioned substantially opposite the pusher 2100 and substantially transverse to the direction of case travel between, for example, feed station 141 and the multilevel vertical conveyor 150. In one example, the snugger establishes a pickface pick datum. For example, the snugger 2120 may be movable in at least the y direction (e.g. towards the pusher plate 2100P) to establish a pickface datum reference when, for example, the pusher 2100 pushes cases up against the snugger 2120 (or vice versa) for substantially aligning and snugging the cases (that form a pickface) together. In one example, the snugger 2120 may be spring loaded in any suitable manner. In the embodiments the snugger may not be spring loaded. The pickface builder 2010 transfers to and collates the aligned cases (e.g. pickfaces) on the feed station 141 for subsequent transfer to the multilevel vertical conveyor 150. In one example, the pickface builder operates so that the snugger 2120 receives an initial case of the pickface and other cases of the pickface are abutted against the initial case as will be described below. In the embodiments the cases of the pickface may be arranged so that one or more cases of the pickface are in substantial contact with the snugger plate 2120P for establishing the pickface datum reference.

[00062] Pickface builder pusher 2100 and snugger 2120 have linear actuators 2162, 2164, 2166 driven by servo motors. In the embodiments, any suitable actuator, linear or otherwise may be provided, for example, any suitable other linear motion technologies. In the embodiments, PFB motion is triggered by a sensor 2170 in the pusher 2100, which follows a payload or case throughout travel of pusher 2100 to provide positive presence detection throughout the x-y motion of pusher 2100. PFB 2010 uses gate 2180 to halt x-axis motion of the payload until the full pickface has been built and snugged where the pickface may consist of one or more cases or payloads and where the snugging may consist of positioning cases or payloads adjacent one another or at any suitable location with respect to each other. Here, pickface builder 2010 pusher 2100 moves in an x-y motion profile that varies (depending on physical characteristics of the payload including, but not limited to, case dimensions, mass, packaging materials and fragility) and the PFB snugger 2120 moves in a y-axis profile which may be normal to the direction of payload travel or otherwise that varies depending on an aggregate of all payload or case dimensions in a given pickface. PFB snugger 2120 may compress all payloads or as is in the pickface in the y-axis to present a compact aggregate of payloads for picking, placing or subsequent transport. PFB roller bed 2140 may be a motor driven conveyor that provides payload or case motion in the x-axis. In the embodiments, any suitable form of conveyor such as belt, or a static bed with other means of x-axis conveyance may be provided for use in conjunction with pusher 2100 and/or snugger 2120. As such, pickface builder 2010 may provide an automated device to align multiple payloads or cases to present the aggregate for picking, placing or otherwise transferring to or from MVC 150A, B or C or other suitable transport device.

[00063] The pickface builder 2010 may be connected to, for example, any suitable controller such as a programmable logic controller, micro-controller or control server 120 in any suitable manner. In the embodiments, information from, for example, the control server 120 identifies any suitable ID (identification) data (e.g. SKU numbers, case dimensions, etc.) for each of the incoming cases (e.g. cases being placed on and travelling on conveyor 240) . For exemplary purposes only, the ID data may be case specific (such as with the SKU numbers) and may also relate to storage parameters such as for example, a storage location within the storage and retrieval system the cases are to be stored and/or particulars for the pickface (e.g. case orientation, contents of a pickface, pickface configuration, etc.) . In the embodiments the case ID data may be any suitable data related to the cases and/or the storage of the cases within the storage and retrieval system. The case ID data (including, but not limited to, SKU numbers, storage parameters, pickface contents, case dimensions etc.) may be stored locally such as within a memory of the pickface builder 2010 or within a memory of, for example, the control server 120 or any other suitable controller. The case ID data may be stored in any suitable format such as in lookup tables. The controller, such as controller 120 or any other suitable controller, generates, for example, an x, y movement profile of the pusher 2100 and/or a y offset of the snugger 2120 to, for example, establish the datum of the pickface based on any suitable data such as the case ID data or updated data from any suitable sensors (such as infeed resolver 2999) placed along the infeed path of the cases (e.g. along conveyor 240 or any other suitable area of the storage and retrieval system) .

[00064] In one example, the infeed resolver 2999 may be configured to confirm the ID data of the incoming cases. The data obtained from, for example, the infeed resolver (such as, for example, the case dimensions and/or any other suitable case information) may be transmitted in any suitable manner to the pickface builder 2010 (e.g. directly to the pickface builder or through, for example, control server 120) so that the motion profiles of the pusher 2100 and snugger 2120 are updated to correspond to any observed variances of the cases (with respect to, for example, predetermined case values stored in, for example, the control server or any other suitable controller) as determined by the infeed resolver 2999. In the embodiments, the pickface builder 2010 may be configured in any suitable manner to redirect or discard cases that are determined to be erroneous based on predetermined case data (e.g. expected case data) and, for example, actual case data obtained from the resolver 2999. In the embodiments a separate case inspection station may be provided adjacent the pickface builder 2010 for redirecting and discarding cases. In one example, the pickface builder 2010 may have a gate or other selectably operable unit for removing the erroneous cases from the pickface builder 2010.

[00065] As described above, the pickface builder 2010 may be configured to communicate in any suitable manner with, for example, the control server 120 and also a controller 150PLC of an associated multilevel vertical conveyor (s) 150. The pickface builder 2010 may obtain information from the controller 150PLC and/or the control server 120 as to which shelves 731 (see e.g. Fig. 13) of the multilevel vertical conveyor 150 are occupied (e.g. have pickfaces located on the shelves) . The pickface builder 2010 may be configured so that pickfaces are not fed to feed station 141 unless an empty shelf 731 is provided on the multilevel vertical conveyor to which the pickface will be transferred. In the embodiments, the pickface builder may be in communication with the feed station 141 so that when a pickface is transferred from the pickface builder 2010 to the feed station 141 the feed station 141 will not transfer the pickface to the multilevel vertical conveyor unless instructed to by the pickface builder 2010. In one example, the pickface builder may be configured to receive data from, for example, the multilevel vertical conveyor 150 and or control server 120 for tracking pickfaces that are transferred to the multilevel vertical conveyor 150. For example, when a pickface is transferred to the multilevel vertical conveyor 150 an identification of the shelf 731 to which the pickface is transferred may be communicated to the pickface builder 2010 so that the pickface builder knows where each pickface is on the multilevel vertical conveyor 150 and which shelves 731 are empty. As another example, in addition to or in lieu of communicating the identification of the shelf to the pickface builder, an identification of the pickface is communicated to the conveyor so that the conveyor knows which pickface, if any, is on each conveyor shelf. As each pickface is removed from the multilevel vertical conveyor 150 the pickface builder 2010 and/or the multilevel vertical conveyor 150 may receive data that indicates the shelf from which the pickface was taken is now empty and available to receive another pickface (s). In the embodiments, the status of the multilevel vertical conveyor shelves may be tracked in any suitable manner (such as with, e.g. any suitable sensing devices disposed along a path of the conveyor shelves 731) .

[00066] In one exemplary operation of the pickface builder (and in-feed conveyor system) cases such as cases 1301, 1302 travel along conveyor 240 in the direction of arrow 1399 towards the pickface builder 2010 (Fig. 13A) . The pusher 2100 pushes, for example, a first case 1301 of a pickface towards the snugger 2120 so that the case 1301 is in substantial contact with the snugger 2120 (Fig. 13B) . The snugger may also move towards the pusher 2100 to, for example, establish the pickface reference datum. The pusher retracts in the direction of arrows 1388, 1389 away from the case 1301 and returns to its initial position (Fig. 13C and 13D) so that a second case 1302 of the pickface can be pushed up against (e.g. snugged) against case 1301 (Figs. 13E and 13D) . As may be realized, as the cases are pushed by the pusher 2100 the pusher may move two-dimensionally so that the cases being pushed are also travelling in the direction of travel along the conveyor 240 (e.g. in the direction of arrow 1399) . In this example cases 1301, 1302 form pickface 1350 (Fig. 13G) which is held on the pickface builder by gate 2180 until an open shelf of the multilevel vertical conveyor 150 is available. The gate 2180 may be lowered or otherwise moved so that the pickface 1350 is driven off of the pickface builder 2010 in any suitable manner and onto the feed station 141. The feed station may be arranged to transfer the pickface in one or more directions A13, B13 (Fig. 13H) , depending on a location of one or more multilevel vertical conveyors 150 for transferring the pickface 1350 to a desired shelf 731 (Fig. 15) . As may be realized, as the pickface 1350 is being moved off of the pickface builder another pickface may start to form such that case 1303 (the next case in the line of cases moving along the conveyor 240) is moved adjacent the pusher 2100 so that pickfaces are substantially continuously being built.

[00067] Figs. 14A-14C illustrate another exemplary formation of a pickface but with smaller cases 1401-1402. In this example cases 1401-1403 are shown moving along the conveyor 240. The formation of the pickface of Figs. 14A-14C occurs in substantially the same manner as that described above with respect to Figs. 13A-13H. It is noted that all dimensions and time information shown in Figs. 13A-14C are exemplary only and that any suitable dimensions and time values can be used.

[00068] Referring now to Fig. 15, there is shown an exemplary platform 731 of the MVC . In addition to the features described below, platform 731 may have similar features as described previously with respect to shelf or platform 730. Referring also to Figs. 16 and 17, there is shown MVC 150C having platform guides 2200. In addition to the features described below, MVC 150C may have similar features as described with respect to MVC 150A or MVC 150B. In the embodiments platform 731 has guide wheels 2210, 2220, 2230 and 2240 mounted to frame 2250. In the embodiments, any suitable guide interface (e.g. single or multiple rollers, bearings), may be used in place of wheels. Chain couplers 2260 and 2270 are provided between rollers 2210, 2230 and frame 2250 respectively. Payload support surfaces 2280 and 2290 are provided coupled to frame 2250. Though the payload support surfaces or stations are shown, the platform may have more or fewer in the embodiments. MVC 150C has suitable motor drive 2300 which drives chain drives 2310 and 2320 (through shaft 2330 which in turn drive chain systems 2335 and 2340 respectively) . Platform 731 may be coupled to chain systems 2335 and 2340 with couplings 2270 and 2260 respectively. Although guides 2200 are shown for the upper portion of MVC 150C, similar features may be provided on a lower portion of MVC 150C to provided continuous guidance of platform 731. Although a single platform 731 is shown on MVC 150C, multiple platforms may be provided at a common or multiple intervals. Guides 2200 are shown having generally four guide portions 2350, 2360, 2370 and 2380 corresponding to guide rollers 22210, 2220, 2230 and 2240 respectively and coupled to frame 2205 of MVC 150C. It is noted that the vertical portions of the guides 2350V1, 2350V2, 2360V1, 2360V2, 2370V1, 2370V2, 2380V1, 2380V2 are arranged to provide a space DC between the vertical portions of the guides to allow for picking and placing case units to the shelves 731 (730' - see Fig. 5) from both sides of the shelves. In one aspect, referring also to Fig. 5 (which illustrates one side of a multilevel vertical conveyor with transfer stations 290A, 290B disposed on opposite sides of the shelf 730 '), one or more transfer areas 295A, 295B may be disposed between the vertical portions of the guides (e.g. within distance DC) for transferring case units to the shelves 731, 730 ' in a manner substantially similar to that described above. Guides 2350 and 2370 are provided offset at a wider stance with respect to guides 2360 and 2380. Guides 2350 and 2370 provide substantially continuous guidance of rollers 2210 and 2230 throughout the path of travel through MVC 150C and with breaks at the corners (e.g. the guides are discontinuous) where sprockets in combination with chain couplings 2260 and 2270 provide continued guidance of platform 731 and where the breaks prevent an over constraint. Guides 2360 and 2380 provide substantially continuous guidance of rollers 2220 and 2240 throughout the path of travel through MVC 150C and with breaks (e.g. the guides are discontinuous) where couplings 2260 and 2270 would interfere with guides 2360 and 2380 during passage and where guides 2360 and 2380 provide continued guidance of platform 731 and where the breaks prevent interference but also where guide wheel 2220 (see Fig. 15) is actively guided when guide wheel 2240 passes a break and where guide wheel 2240 is actively guided when guide wheel 2220 passes a break. As such, a substantially continuous three-point guidance is accomplished during the entire path of travel. In the embodiments, one or more of the motor 2300 chain drives 2310, 2320 and chain systems 2335, 2340 may include an active braking mechanism and velocity control. It is noted that the chain systems 2335, 2340 and the platforms generally revolve around the conveyor path at a substantially constant velocity to, for example, allow the bots to rendezvous with a platform. The braking mechanism and/or velocity control may substantially prevent the platforms from "free-wheeling" (e.g. moving without being driven by the motor 2300 and drive chains) if power is lost when a number of platforms are heavily loaded while others are substantially empty. Here, platform 731 travel may be guided by two sets of guide wheels 2210, 2220 and 2230, 2240 that travel within channels 2350, 2360 and 2370, 2380 on a predetermined path defined by the channels and drive system. Hence, the guide wheels 2210, 2220, 2230, 2240 and correspondingly the platform (and pickface(s) supported thereby) traveling along the path resist binding due to a balanced cantilevered arrangement and where transitions through corners are made by substantially continuously having three points (wheels) of contact within the roller guides 2350, 2360, 2370, 2380, providing smooth (substantially shudder/ udder free) transition of platform 731 through the entire path of travel within MVC 150C. In the embodiments, one or more MVC(s) 150C enable loading and unloading of payloads, cases or pickfaces in storage racks of storage levels.

[00069] As noted before, MVC platforms 731 may have more than one pickface station, for example, for pickfaces of at least one case(s) . Platforms 731 are cycled by chain drive 2335, 2340 and use guides 2200 such that the stations maintain stability capable of desired positioning of pickfaces through substantially the full motion cycle within MVC 150C and without over constraints that may cause shuddering, jamming or other unsuitable or undesired motions of the pickface (s) to occur. Here, the MVC platform connection to MVC drive system 2260, 2270, and MVC platform guides 2200 are configured to effect three (3) point contact between platform 731 and MVC structure through full motion cycle and without over constraints. The platform supports, formed by the guides 220 and drive system coupling 2260, 2270 form what may be referred to as a guided cantilever restraint that is movable through complete cycle without over-constraints, and, as a result without undesirable motion, such as shudder or judder through cycle motion. Accordingly a smooth and effective load and unload MVC cycle (e.g. infeed to off load for infeed MVC and vice versa for outfeed MVC) as well as MVC sorter (e.g. pickface payload moves through more than one cycle) may be provided. In the embodiments, MVC 150C has frame 2205, drive system 2300 and platforms 731 that are mounted to the frame and coupled to the drive system 2300 so the platforms 731 are cycled vertically in a closed loop. Platform(s) 731 may have one or more pickface payload holding stations (e.g. two 2280, 2290) that are located offset from each other, for example, positionally distributed on platform. In the embodiments, more or less locations may be provided. Each holding station may be configured for holding pickface of (one or more) uncontained cases (s) . Each holding station may independently fed and offloaded. Independent feeds may have pickface builders that may be accommodated by MVC structure and motion path profile (s) . Further, MVC 150C may be both a multilevel loader/unloader and sorter. In the embodiments, frame 2205 and drive 2300 may be configured to effect platform 731 motion that results in a vertical or horizontal cycle component in a same direction as load/unload transfer axis for a given pickface, for example, front-back. In the embodiments, the interface may be to warehouse conveyors, for example, a load station for infeed to MVC 150C or an unload station for outfeed from MVC 150C as may be located interior to frame 2205 and transport loop path of platforms 731 of MVC 150C. Interface with rack storage and retrieval system, for example, bot to MVC transfer locations may be provided on an outside of the transport loop path of platforms 731 of MVC 150C. In the embodiments, any suitable in feed or out feed may be provided on the inside, outside or otherwise of the transport path of platforms 731 of MVC 150C.

[ 00070 ] The storage structure 130 may also include charging stations 290 for replenishing, for example, a battery pack, capacitor, ultra-capacitor or other electricity storage device of the bots 110 as will be described in greater detail below. The charging stations 290 may be located at, for example, bot stations 140A, 140B (generally 140) of the transfer deck 130B so that the bots 110 can substantially simultaneously transfer items, for example, to and from a multilevel vertical conveyor 150A, 150B while being charged. The bots 110 and other suitable features of the storage and retrieval system 100 may be controlled by, for example, one or more central system control computers (e.g. control server) 120 through, for example, any suitable network 180. The network 180 may be a wired network, a wireless network or a combination of a wireless and wired network using any suitable type and/or number of communication protocols. It is noted that, the system control server 120 may be configured to manage and coordinate the overall operation of the storage and retrieval system 100 and interface with, for example, a warehouse management system 125, which in turn manages the warehouse facility as a whole. The control server 120 may be substantially similar to that described in, for example, United States Patent Application Number 12/757,337, entitled "CONTROL SYSTEM FOR STORAGE AND RETRIEVAL SYSTEMS" and filed on April 9, 2010, the disclosure of which is incorporated by reference herein in its entirety.

[00071] Referring now to Figs. 18A and 18B, each of the bots 110 in the storage and retrieval system 100 include one or more suitable electricity storage devices for powering the bot 110. In the embodiments the one or more electricity storage devices may be one or more suitable capacitors or ultra-capacitors (referred to herein generally as capacitor HOC) . While the embodiments are described with respect to capacitors it should be understood that the electrical storage devices, in alternate embodiments, may be any suitable solid state, chemical, or other electricity storage system. Still, the bots may be powered by fossil fuels the replenishing of which may be substantially similar to that described herein.

[00072] To enable substantially full (about 100%) bot utility during normal operation (e.g. when the bot is actively transferring items in the storage and retrieval system) or during extended idle time, the bots on each storage level 261- 264 of the storage and retrieval system 100 may recharge or replenish their power supplies, such as the one or more capacitors HOC, at charging locations or stations 290 at the multilevel vertical conveyor 150 exchange areas (e.g. bot/transfer stations 140) . The bots may access the bot stations 140 by, for example, following lines or other suitable guides, such as conveyor access guide lines 130C1-130C3 on the transfer deck 130B. For example, the transfer deck 130B may have any suitable number of travel guide lines 130L1-130L4 and any suitable number of shunt or bypass guide lines 130S1-130S7 that form one or more travel paths or lanes for the bots 110 to traverse. For example, guide lines 130L1, 130L2 allow travel in a first direction and guide lines 130L3, 130L4 allow travel in a second direction substantially opposite the first direction. The shunt guide lines 130S1-130S7 may be oriented substantially transverse to the travel guide lines 130L1-130L4 but in other aspects they may have any suitable orientation relative to the travel guide lines. The shunt guide lines 130S1-130S7 allow bidirectional travel of the bots 110 for switching between travel guide lines 130L1-130L4 so that the bots can access, for example, the picking aisles 130A or the bot stations 140 without traversing an entire length of the travel guide lines 130L1- 130L4. In the embodiments, the shunt guide lines may be aligned with the picking aisles 130A1-130A7 or any other suitable ingress or egress location of the storage and retrieval system allowing the bot to turn down a corresponding picking aisle while travelling along any one of the travel guide lines 130L1- 130L4. The shunt guide lines 130S1-130S7 may also be located at ends of the transfer deck 130B or at any other suitable locations of the transfer deck 130B. As an example, a bot 110 travelling along a path corresponding to guide line 130L1 may be instructed to transfer an item to a storage location in picking aisle 130A4. However, the bot 110 may have already passed the shunt guide line 130S4 corresponding to picking aisle 130A4. The bot may continue to travel along guide line 130L1 until it encounters the next available shunt (e.g. a shunt not being used by another bot) such as shunt guide line 130S5. The bot may turn onto shunt guide line 130S5 and then turn onto one of the guide lines 130L3, 130L4 so that the bot 110 is travelling in substantially the opposite direction towards the picking aisle 130A4. The bot may continue to travel along one of the guide lines 130L3, 130L4 until it encounters shunt guide line 130S4, corresponding to picking aisle 130A4, where the bot turns onto shunt guide line 130S4 for transitioning into or otherwise entering the picking aisle 130A4 guide way (such as, for example, a rail guidance system) . The conveyor access guide lines 130C1-130C3 may be substantially similar to the shunt guide lines 130S1-130S2 however, in the embodiments the conveyor access guide lines may only allow unidirectional travel of the bots 110 through the bot station 140. For example, conveyor access guide line 130C1 may provide an entrance path into the bot station. Conveyor access guide line 130C2 may provide a pathway for charging the bots 110 and allowing the bots to interface with the multilevel vertical conveyor shelves 250. Conveyor access guide line 130C3 may provide an exit path into the bot station. The conveyor access guide lines 130C1-130C3 may also provide bidirectional travel of the bots so that the bots 110 can enter and/or leave the bot station using either of guide lines 130C1 or 130C3. The conveyor access guide lines 130C1, 130C3 may extend across the transfer deck 130B so that the bots can access the bot station 140 from any one of the travel guide lines 130L1-130L4 and exit onto any one of the travel guide lines 130L1-130L4 from the bot station 140. It is noted that while the embodiments of the transfer deck 130B and bot stations 140 are described herein with respect to line following, the transfer deck 130B and bot stations 140 may be configured so that the bots are guided by any suitable rail system. In one example, the bots 110 may enter and exit the picking aisles 130A and the bot stations 140 with either a front end of the bot leading the direction of travel or a back end of the bot leading the direction of travel as described in for example, United States Provisional Patent Application serial number 61/423,409 entitled "AUTONOMOUS TRANSPORT VEHICLE" with Attorney Docket Number 1127P014258-US (-#1) and filed on December 15, 2010 (now U.S. Pat. App . No. 13/326,423 with Attorney Docket Number 1127P014258-US (PAR) filed on December 15, 2011), the disclosures of which are incorporated herein by reference in their entireties.

[ 00073 ] In the embodiments, the travel guide lines 130L1-130L4 and shunt guide lines 130S1-130S7 (including guide lines 130C1, 130C3) are arranged so that the bots 110 travel in a substantially counterclockwise direction but it should be realized that the guide lines may be arranged so that the bots travel in a substantially clockwise direction. When traversing the guide lines 130L1-130L4, 130S1-130S7 collisions between the bots 110 may be avoided in any suitable manner such as through bot-to-bot communications or bot location tracking and management through, for example, control server 120 or other suitable bot controller. A suitable example, of bot collision avoidance may be found in, for example, United States Patent Application Number 12/257,337 entitled "CONTROL SYSTEM FOR STORAGE AND RETRIEVAL SYSTEMS" and filed on April 9, 2010, the disclosure of which is incorporated by reference herein in its entirety .

[00074] In the embodiments the bot station 140 may be in the form of a vestibule 130V that extends between the transfer deck 130B and the multilevel vertical conveyor 150. Each vestibule 130V may be configured with more than one charging station 290A, 290B (each of which may also serve as a transfer location for accessing a respective portion of the multilevel vertical conveyor shelf 250) arranged in, for example, a linear array, along guide line 130C2. In this example, there are two charging stations 290A, 290B corresponding with two item holding locations on the multilevel vertical conveyor shelf 250. It is noted that in the embodiments there may be any suitable number of charging stations, which may correspond with a respective number of item holding locations on the multilevel vertical conveyor storage shelf 250.

[00075] The charging stations 290A, 290B of each vestibule 130V may be connected to a common power supply 290P as will be described in greater detail below. The common power supply 290P may power the charging stations 290 of multiple bot stations 140. For example, the bot stations 140 may be disposed one above the other in a vertical array or stack so that the bots 110 of each pick floor level 261-264 travel along substantially parallel paths while in the bot stations 140. The storage and retrieval system may include one or more power supplies 290P each of which may be connected to the charging stations 290 of one or more pick floor levels 261-264. Bot 110 ingress and egress to/from the vestibule 130V of the bot station 140 and to the charging stations 290 along, for example, the guide line 130C2 may be synchronized with other bots 110 destined for, leaving, or charging at the charging stations 290 by an access- charge-depart protocol, hosted in any suitable controller of the storage and retrieval system, to maximize substantially full utility of all charging stations 290 of a given vestibule 130V (e.g. to substantially avoid a case where the charging of bots 110 interferes with the ingress/egress process or other bots 110 designated to travel to the same vestibule 130V) . Each multilevel vertical conveyor may have any suitable controller 150C, such as a programmable logic controller, for controlling the operations of the respective multilevel vertical conveyor 150 as well as controlling the power supply or supplies of the charging stations 290 disposed on the vestibules 130V providing access to the shelves 250 of the respective multilevel vertical conveyor 150.

[00076] The ingress and egress of the bots 110 to the vestibules 130V may be managed by, for example a level manager 297 a portion of which may include a vestibule manager 296 (Fig. 26) . The level manager 297 may have any suitable organization so as to, for example, manage bot operations on one or more pick floor levels, in one or more stacks of bot stations 140 (e.g. bot stations 140 located one above the other) , or in geographical regions of the storage and retrieval system. The level manager 297 may be in communication with the bots 110 in any suitable manner using any suitable communication protocol. For example the communication between the bots 110 and the level manager 297 may be a wired or wireless bidirectional and/or unidirectional communications, Linux based communications, etc. In the embodiments each pick floor level 261-264 may have its own respective level manager 297 for controlling or otherwise managing movement of the bots 110 on the respective level and/or, one level manager may manage more than one pick floor level 261-264. The level manager 297 may be configured such that it tracks the location of operative bot charging stations 290 and communicates with a gang manager 290G (Fig. 18B described below) for obtaining access to the chargers and the status of bot 110 charges. The vestibule manager 296 may manage the areas in which the charging stations 290 are located for determining if access is available before, for example, the gang manager 290G requests access to the charging stations. As will be described below, if one or more charging station 290 in a vestibule is inoperative the vestibule manager 296 may, in the embodiments, close the vestibule (e.g. deny access so that bots are directed to other vestibules) with the inoperative charging station(s) 290.

[ 00077 ] Each bot 110, through any suitable onboard controller or manager, may communicate with the level manager to effect a charge cycle on the bot 110 in combination with a case unit 101 exchange with a multilevel vertical conveyor 150 on the pick floor level 261-264 on which the bot 110 is located. Each charging station 290A, 290B includes contacts 290C for interfacing with corresponding contacts HOD (e.g. such as a charger pad) on the bot 110 for charging, for example, the bot's capacitor (s) HOC. The contacts 290C may be any suitable contacts such as spring loaded or other actuable contacts that are configured to engage the contacts HOD of the bot 110 when the bot is positioned substantially over the charging station 290A, 290B. These charging station contacts 290C may be positioned at the charging stations 290A, 290B such that they interface with the contacts HOD of a bot 110 when the bot 110 is positioned for interface and exchange with one of the holding locations of the multilevel vertical conveyor shelf 250. As described above the bots access the vestibules 130V of the bot stations 140 through an access-charge-depart protocol that may include getting permission to travel on to the charger contacts 290C (prior to item exchange with the multilevel vertical conveyor), initiating charge, and getting permission to leave (after item exchange with the multilevel vertical conveyor) . The level manager 297 may be configured to manage the requests for access to the vestibules 130V and charging stations 290A, 290B and make decisions on whether to allow bots 110 to enter, leave and initiate/terminate charging accordingly. A charge can be initiated once the bot 110 has gained access and stops on one of the charging stations 290A, 290B corresponding to a location on the shelf 250 the bot 110 is to pick/place an item. The charging of the bot 110 may occur during the time it takes to transfer an item between the bot 110 and the shelf 250 or after the transfer has completed. In addition, the bot 110 may charge at the nearest available (e.g. unallocated) vestibule 130V without interfering with other transfers (non-determinative, opportunity charging) .

[00078] In the embodiments, the bots 110 may perform a quick charge before leaving the multilevel vertical conveyor vestibule 130V, at which point the multilevel vertical conveyor controller 150C may inform a gang manager 290G (Fig. 18B) that a quick charge has been achieved. The quick charge of the bot 110 may be a charge that terminates (or signals ready for termination) at the point where the power supply 290P switches from a constant current mode (e.g. the power supply is delivering maximum current output with variable voltage) to a constant voltage mode (e.g. where the power supply has reached the maximum voltage output set point with a variable current) . It is noted that the bot 110 may remain at the charging station 290A, 290B and continue to charge (e.g. to achieve a top off or full charge) until, for example the control server 120 or other suitable controller of the storage and retrieval system deems necessary to move the bot 110, such as to allow another bot 110 access to the charging stations 290A, 290B.

[00079] During a quick charge the capacitor HOC of the bot 110 may be at a voltage that does not take into account losses from the power supply 290P to the capacitor HOC. During a top off or full charge the extended period for the capacitor to reach the applied voltage level (Tau = R*C, 5*Tau ~ 99.3% of final voltage, where R is the combined ESR of the capacitor and any resistance between the power supply sense lines (Fig. 19) and the capacitor) . The gang manager 290G may be a collection of cooperating interfaces that manages gang charging of bots 110 (e.g. charging more than one bot at a time where a gang is a group of bots that are charged by the same power supply) on multiple pick floor levels 261-264 that share a power supply. In the embodiments there may be one gang manager 290G per power supply 290 or each gang manager may serve multiple power supplies. In the embodiments, the bots 110 may not have access to a charging station 290 if the power supply 290P is enabled and operational (e.g. power is being transferred to the charging station waiting to be accessed) . In the embodiments, after charging and the power supply 290P stops transmitting power to the charging station 290 the gang manager 290G, for example, may cause the bot 110 to remain at the charging station 290 for a predetermined amount of time, which in one example, may be about 280 milliseconds. In other examples, the amount of time the bot 110 remains at the charging station 290 after the power is turned off may be any suitable time period.

[00080] Referring to Figs. 19 and 20, there may be, for example, four charging stations 290A, 290B, 290A2, 290B2 per power supply 290P. The charging stations 290A, 290B, 290A2, 290B2 may be vertically placed within a single multilevel vertical conveyor 150 area and disposed in a rectangular configuration with two charging stations 290A, 290B on one pick floor level and two charging stations 290A2, 290B2 on another different pick floor level, where the pick floor levels may be adjacent to one another. As an example, referring back to Fig. 18A, in this power supply configuration the charging stations of pick floor levels 261, 262 would share a power supply, the charging stations of pick floor levels 263, 264 would share a power supply, etc. It is noted that in the embodiments there may be any suitable number of charging stations on each pick floor level that share a power supply with any suitable number of charging stations from one or more other pick floor levels. Each power supply 290P may be located within a predetermined distance to the charging stations 290 that it serves. For example, power supply 290P may be located less than about 18 feet from the charging stations 290A, 290B, 290A2, 290B2 to, for example, reduce wiring loss and increase charging throughput. It is noted that in the embodiments, the power supplies 290P may be located any suitable distance from their respective charging stations 290.

[00081] As described above, each power supply may be controlled by, for example, a controller 150C of a respective multilevel vertical conveyor 150, or any other suitable controller. In the embodiments there can be up to about sixteen power supplies 290 and up to about sixty-four charging stations 290 associated with a single multilevel vertical conveyor 150 where the charging stations are located on different pick floor levels. In the embodiments, the controller 150C may be configured such that when the multilevel vertical conveyor is stopped (e.g. power is shut off to the conveyor) the charging stations 290 will remain operational. Power to the charging stations 290 and the multilevel vertical conveyor may be individually disabled/enabled .

[00082] Referring to Figs. 18B and 19, and with respect to pick floor level 262 for exemplary purposes, the bot charging process may initiated before the bot 110 enters the multilevel vertical conveyor area (e.g. the bot station 140) . The bot may initiate communication with the gang manager 290G to request permission to drive on to a particular charging station 290A, 290B. In the embodiments, the decision on which charging station 290A, 290B the bot is to interface with may be dependent on which multilevel vertical conveyor shelf 250 is the intended target and in which location of the shelf 250 the item to be transferred is to be picked from or placed to.

[00083] The Bot may remain out of the charging station 290A, 290B area (e.g. the load/unload area of the multilevel vertical conveyor) until it receives permission from, for example, the control server 120 (or other suitable controller such as the vestibule manager of the level manager) that it is safe to enter the charging station 290A, 290B. In one example, the gang manager 290G may have knowledge of any other bots 110 on the pick floor level (which in this example is pick floor 262) that may access the charging station 290A, 290B and may command controller 150C to turn off the power supply 290P for allowing a bot 110 to enter the charging station 290A, 290B. In one example, the gang manager 290G may have the discretion to decide when to turn off the power supply 290P and when to allow the bot 110 on to the charging station 290A, 290B. [00084] Once the Bot has permission to move in to the charging station 290A, 290B (e.g. the multilevel vertical conveyor load/unload area), the bot 110 may maneuver to the intended charging station 290A, 290B and report its position accordingly. Once the bot 110 is located at the intended charging station 290A, 290B, the gang manager 290G may communicate to the controller 150C to re-enable the power supply 290P, at which point the bot 110 will begin charging. This charging of the bot 110 may overlap with charging of other bots 110 that are on the same shared charging system network (e.g. if bot 110 is charging at charging station 290A, other bots 110 may be also be charging at one or more of charging stations 290B, 290A2, 290B2) . In the embodiments, the charging process is open ended and may not terminate until commanded to do so by, for example, the gang manager 290G or other suitable controller of the storage and retrieval system 100.

[00085] The controller 150C may control the power supply 290P and monitor a status of the power supply 290P. The controller 150 may monitor the status of the power supply 290P and report to, for example, the gang manager 290G when the power supply 290P has reached a constant voltage mode and measures a current output falling below about 75% of its maximum value. It is noted that in the embodiments, the controller 150C may report to, for example, the gang manager 290G at any suitable time such as when the current output is above or below about 75%. At this point, the bot 110 has been "Quick Charged" and can be ready to perform tasks as needed. The gang manager 290G may send a command to terminate the charge cycle if the bot 110 is needed to transport items within the storage and retrieval system 100. If the Bot is not needed, charging may continue and the charger supply may remain on indefinitely. It is noted that in the embodiments the power to the charging station being used may be shut off upon a predetermined condition such as when, for example, the bot reaches a "full charge." A full charge may be accomplished if the Bot remains charging for about five R*C time constants. The time to reach a full charge may be dependent on, for example, such factors including the resistance between the charger station contact 290C and the contacts HOD of the bot 110, the wiring on the bot 110 as well as the resistance inside the capacitor HOC. In one example, a bot 110 may leave the charging station 290A, 290B any time after a quick charge.

[00086] In the embodiments there may be N number of gang managers 290G controlling N number of power supplies 290P. For example, the controller 150C of each multilevel vertical conveyor 150 may have addressable ports unique to each power supply 290P. The bot 110 when requesting a charge may communicate, through for example, level manager 297 (Fig. 18B) , with a gang manager 290G controlling a power supply 290P for a charging station to which the bot 110 will travel. As described above, the communication between the bots 110 and the level manager 297 as well as the gang manager 290G, controller 150C and power supply 290P (and other suitable components of the storage and retrieval system) may be any suitable communication protocol and methods such as, for example, wired or wireless bidirectional and/or unidirectional communications, Linux based communications, or other suitable communications.

[00087] Referring to Fig. 22, in the embodiments the level manager 297 may manage the bots 110 on a level (or more than one level) to which the level manager 297 is assigned. The level manager 297 may include a bot controller 298 for use by the bots 110, and conversely each bot 110 may include a controller 118 for use by the bot controller 298. There may be, for example, a one to one mapping between the bot controller 298 and each bot 110 (e.g. the level manager 297 includes one bot controller for each bot) or, one bot controller may be mapped to more than one bot. The level manager 297 may also include a charge manager 299 that may act as an intermediary between the bot controller 298 and the gang manager 290G to manage charging.

[00088] Each bot controller 298 may communicate with the gang manager 290G via the charge manager 299 to effect charging of the bot 110. In the embodiments there may be, for example, ten multilevel vertical conveyors that intersect the pick floor levels 261-264 (e.g. with twenty charging stations 290 disposed at each pick floor level - e.g. two charging stations per multilevel vertical conveyor intersection) . It is noted that in the embodiments there may be any suitable number of multilevel vertical conveyors and charging stations per pick floor level. The charge manager 299 may choose the appropriate charging station 290 to converse with for a given charge cycle. Since bot gangs (e.g. groups of bots charged using the same power supply) span adjacent levels, two level managers 297 may each establish communication connections with the charging stations 290 of their respective levels (which in this example, is twenty charging stations per level) .

[00089] Conversely, each charge manager 299 may include a charging station status server 299S for each charging station 290, that the gang manager 290G uses to relay power supply status information sent to it by a charging communication service 620. It is noted that the charging communication service 620 may handle status requests from, for example, the controller 150C, on/off requests for, as an example, controller 150C, and requests to enter/leave a charging station 290. Since each gang manager 290G may manage two pick floor levels, it may have connections to, for exemplary purposes only, about four such charging station status server objects, e.g. two for each pick floor level. There may be as many named instances for requests to enter/leave a charging station 290 (e.g. a request instance) as there are charger stations 290. In one example, each group of four request instances maps to a portion of the charging communication service that handles on/off requests, and hosts a portion of the charging communication service that handles charging station status requests.

[00090] In an exemplary operation, the bot controller 298 may issue tasks for the bot 110. It is noted that when issuing tasks for the 110, the bot controller 298 may allow for an efficient exchange of items between the bots 110 and the multilevel vertical conveyors. When issuing these tasks the bot controller 298 may do so such that bots 110 are not held up from entering the bot stations 140 (and charging areas 290) for commencing item transfer with the multilevel vertical conveyor 150. Also, when issuing tasks the bot controller may not prevent egress of bots from the charging areas 290 because of bots 110 that have not finished charging or have not received a minimum amount of charge. It is also noted that if a first bot 110 has not completed a case unit 101 transfer with the multilevel vertical conveyor 150 any bots located in charging stations 290 behind the first bot 110 may remain in their charging stations to continue receiving a charge.

[00091] Referring to Fig. 23, when issuing tasks the bot controller may be aware of when the bot 110 needs to enter the charging station 290, and when the bot 110 is at the charging station 290. However, the bot controller 298 may not be aware of exactly when in time the bot 110 clears or leaves the charging station 290. The bot controller 298 and the bot 110 may cooperate with each other to create a charging cycle. In an exemplary charging cycle, the bot controller may identify the appropriate charging station 290 to communicate with. The bot controller 298 may request (e.g. a "can bot enter" message) that the charge manager 299 send a "bot can enter" message to the charging station 290. The gang manager 290G may verify that the charging station 290 is turned off and waiting for a charger status to reflect the off status. The gang manager 290G may send a charger status and "bot can enter" message to the charge manager 299, which relays it to the bot controller 298. The bot controller 298 may issue other tasks to the bot 110 via the controller 118. When the bot 110 reaches the charging station 290, the bot controller 298 may wait for a "bot is at charging station" message in order to read a simulated bot voltage and ask the charge manager 299 to send a "bot is at charging station" message to, for example the gang manager 290G. The charge manager may send a "bot has quick charge" message when the bot 110 has received a quick charge. This allows the level manager 297 to mark the bot 110 as available for other tasks, when it finishes any current job, such as the transfer of items between the bot 110 and the multilevel vertical conveyor. When the bot controller 298 deems that the bot 110 should move out of the charging station 290, it asks the charge manager to send a "can bot leave" message, to for example, the gang manager 290G. The gang manager 290G verifies that at least a quick charge has been delivered to the bot 110, turns off the charging station 290 if necessary, and sends a "bot can leave" message, which gets relayed to the bot controller 298 and then to the controller 118. This allows the simulated bot to update its voltage at the end of a charge cycle. It is noted that the simulate bot may exist in the any suitable memory of any suitable controller of the storage and retrieval system such that based on the tasks sent to the bot, the controller can determine how much of a charge remains in the bot. It is noted that in the embodiments, the bots 110 may periodically send a message to the controller indicating a charge status of the bots 110 or that the bots 110 need to be charged. The bot controller 298 may send the next set of tasks to the bot 110. When the bot 110 deems that it is safely out of the charging area, the bot 110 may send a "bot has left" message, which causes the bot controller 298 to send a "bot has left" message via the charge manager 299. The bot 110 need not wait for an acknowledgement or stop its motion to send this message. The power supply 290P gets re-enabled by the gang manager 290G if necessary for other bots remaining at the charger stations 290.

[00092] In the embodiments, separately from any ongoing charge cycle interactions, the gang manager 290G may relay power supply status information to, for example, the level manager 297 so that the level manager may route bots 110 away from unavailable chargers. It is noted that the level manager 297 may establish, through for example, the gang manager 290G the operational status of each of the charging stations 290 and whether the charging stations 290 are available.

[00093] It is noted that each bot goes through the same charging sequence described above. In the embodiments, the gang manager 290G may be configured to reconcile multiple pending charge requests by turning each of the charging stations on and off, individually or in groups, as needed. The gang manager may also be configured to collectively turn off the charging stations by, for example, turning off the power supply 290P. This is done by keeping track of the number of bots 110 moving to/from the charging stations 290, and the number of bots at the charging stations 290. One non-limiting example, of keeping tracking of bots 110 is as follows: Request Actions

Can Bot Enter If necessary, the charger is turned OFF

When the charger is confirmed to be OFF: iNumMoving++

Send botCanEnter

Bot Is At Contact iNumMoving—

iNumAt++

if ( ! iNumMoving && iNumAt ) turn_charger_on ( )

Can Bot Leave If bot has not received one charge cycle, defer request until such charge is

received or power supply fails or is disabled .

Charger is turned OFF if necessary

When the charger is confirmed to be OFF: iNumMoving++

Send botCanLeave

Bot Has Left iNumMoving—

if ( ! iNumMoving && iNumAt) turnChargerOn ( )

Charger Status If charger passed the quick charge mark, mark all bots at charger to have received a quick charge so they can leave if

desired. Send the botHasQuickCharge ( ) message .

If charger turned off as a result of having been turned off, update all bot states as outlined previously so bots can enter or leave the charger contact.

If the charger had an error, send

notification on appropriate

ChargerContactStatus : : isAvailable ( ) interfaces .

[00094] The term "Comm Failure" may be used to indicate that the two sides of a communication connection get an "unbind" indication. Conversely, the "bind" indication indicates a (re) connection between the two sides. The following outlines non-limiting exemplary charging specific actions that may be done upon various failures.

capacitance 181.5F nominally about 165F, allow 10% variation

Maximum charge time About 305 Largest voltage delta to quick for a bot seconds charge

= MaxPowerSupplyCutoff - 0V

= about 46.3V

Smallest current while charging

= Power supply minimum current

/ MaxContactsPerSupply

= 111 / 4

= about 27.25A

Worst case time to charge

= max_capacitance * max_delta_V / min_current

= 181.5 * 46.3 / 27.25

= about 303 seconds

Additional about 2 seconds to turn off supply at end.

Time for bot to move X seconds Allowance for bot

to contact after

having received

permission to do so

Time for bot to move Y seconds Allowance for bot

away from contact

after having

received permission

to do so

Overall margin About 10%, Additional margin for all timeout minimum, calculations

about 1

second

[00095] The following are non-limiting exemplary timeout values that may be used to deem a transaction to be a failure.

botCanEnte

r

botCanEnte About 8 Gang Manager About 2 comm transactions r -> move bot

bot IsAtCon

tact

bot IsAtCon About 338 Charge Manager About 2 comm transactions tact -> to gang manager

botHasQuic Max charge time = N kCharge seconds canBotLeav About 7 Charge Manager About 4 comm transactions e -> turn charger off

botCanLeav

e

botCanLeav About 6 Gang Manager Move bot

e ->

botHasLeft

Time to About 5 Gang Manager off cycle

turn off a About 1 each for comm bot

Time to About 338 Gang Manager About 2 comm transactions charge a max charge time = N bot seconds

[00096] When there is a power supply failure a message may be relayed from the gang manager 290G. During a power supply failure the bots 110 may be allowed to leave the charging stations 290 even if the bots have not received a minimum amount of charge. The charge manager 299 may use the information from the gang manager 290G in conjunction with, for example, the state of the bot 110 or bot controller's 298 conversation with the gang manager 290G to complete any pending charging cycles, and mark the charging station (s) 290 connected to the failed power supply as inoperable. In this case the gang manager 290G and or charger manager 299 may find other available charging stations 290 and communicate with the level manager 297 for routing the bots 110 that did not receive the minimum amount of charge to these available charging stations 290 (e.g. without impeding ingress/egress to the respective multilevel vertical conveyors 150 at the locations of the available charging stations 290.

[00097] With respect to other exemplary communications within the bot charging system, the bots 110 may communicate with a respective bot controller 298 to indicate a simulated bot's voltage and that the bot has left (or arrived at) a charging station 290. The bot controller 298 may communicate with a respective bot 110 a post-charge voltage that may be valid only during a simulation. The charge manager 299 may communicate with the charging stations 290 to ensure the charging station is off so a bot 110 can enter or leave the charging station 290. The charge manager 299 may also indicate when gang charging can start or resume, indicate that a bot has left a charging station and to resume charging and to enable/disable one or more charging stations. The gang manager 290G may indicate the charging station is off so that the bot can move on to or off the charging station, that the bot has received a quick charge, and a state of the charging station 290 (e.g. whether the charging station is inoperable, off, in constant current mode, in constant voltage mode, etc.).

[00098] In the embodiments, the bot controller 298 may be configured to allocate the charging stations 290 using reservations (e.g. each bot that is to access a particular charging station "reserves" or allocates that charging station so no other bots are able to access it during the reservation period) . When a bot 110 with a reservation accesses a charging station 290 it receives a charge and when complete the bot 110 requests to release (e.g. un-reserve) the charging station 290 so that the charging station 290 can be reserved for other bots 110. Fig. 24 illustrates a transaction state diagram for a charging sequence in which a reservation is held. For example, before the bot enters the charging station 290 a request is made for the bot to enter the charging station. If there is no bot present at the charging station 290 the request may be granted and the bot enters the charging station 290. If only a transfer of items to/from a multilevel vertical conveyor 150 is being made, the transfer may take place and a request for release of the charging station 290 may be sent by the bot 110 and after the release a notification that the bot 110 has left may be made. Where charging is to occur (in addition to or in lieu of a transfer of items to/from the multilevel vertical conveyor 150) charging may occur when the bot 110 is in the charging station 290. A check may be made as to whether the bot 110 has received a quick charge. If the bot 110 has received a quick charge the bot 110 is able to leave the charging station 290 and makes a request to release the charging station 290. Once the charging station 290 is released the bot 110 exits the charging station 290 and an indication that the bot 110 has left is made. [00099] Fig. 25 illustrates exemplary class hierarchies and dependencies with respect to communication between the charge manager 299 and the bots 110.

[000100] In the embodiments the operational state of the charging station within a vestibule 130V may be linked in any suitable manner to an operational state of a corresponding multilevel vertical conveyor 150. Referring to Fig. 26, for exemplary purposes only four vestibules 130V1-130V4 of a single pick floor level are shown where each vestibule 130V1-130V4 has two charging stations 290. It is noted that in the embodiments the storage and retrieval system may have any suitable number of vestibules each having any suitable number of charging stations. Each vestibule is served by a respective multilevel vertical conveyor 150-1, 150-2, 150-3, 150-4. Each of these multilevel vertical conveyors also serves other vestibules vertically stacked above and/or below a respective one of the vestibules 130V1-130V4.

[000101] Upon startup of the level manager 297, with respect to charging operations of the bots 110, the charge manager 299 knows the structural information about each charging station 290 (e.g. where they are located and which multilevel vertical conveyor is associated with the respective charging stations). The charge manager 299 may communicate with each charging station 290 to obtain, for example, an operational status of the charging stations 290. The bot controller 298 of the level manager 297 may communicate with the bots 110 for issuing commands or jobs (e.g. to transfer case units 101) to the bots 110.

[000102] When a bot, such as bot 110X, needs to be charged, whether in conjunction with the transfer of a case unit 101 to/from a multilevel vertical conveyor 150-1, 150-2, 150-3, 150- 4 or not, the bot may send a message to a vestibule manager 296 for determining which vestibule 130V1-130V4 the bot is to be directed to. In the embodiments the vestibule manager 296 may be part of the level manager 297 or, the vestibule manager 296 may be included in any suitable controller of the storage and retrieval system. If the charging of bot 110X is not in connection with a case unit 101 transfer, the vestibule manager 296 may direct the bot 110X to a vacant or unallocated operational charging station 290 in a nearest "online" or operational vestibule 130V1-130V4. If the charge of the bot 110X is in conjunction with a transfer of case units 101 to/from a multilevel vertical conveyor 150-1, 150-2, 150-3, 150-4, the vestibule manager 296 may communicate with the vestibule (which for exemplary purposes may be vestibule 150-3) at which the bot 110X is to transfer the case units 101 to verify that the charging stations 290 of that vestibule are operational. At least one of the charging stations at, for example, vestibule 150-3 may be reserved for the bot 110X as described above. If however, one or more of the charging stations for the vestibule 150-3 is determined as being inoperable a suitable controller of the storage and retrieval system such as control server 120 may inform the level manager 297 and/or the vestibule manager 296 that the vestibule 150-3 is "offline" or inoperable such that no case units 101 can be transferred to the multilevel vertical conveyor 150-3 nor can bots 110 be charged at other operational charging stations 290 of offline vestibule 130V3. The level manager 297, with information provided by the vestibule manager 296, may communicate with bot 110X and direct the bot 110X to an available charging station 290 of the next available vestibule 130V1-130V4 for transferring the item 101 while simultaneously charging the bot 110X.

[000103] In the embodiments, vestibules vertically stacked above and/or below vestibule 130V3 may still be able to charge bots 110 and transfer case units 101 to the multilevel vertical conveyor 150-3. In the embodiments, because the charging stations 290 of vestibule 130V3 may be powered by the same power supply 290P (Fig. 19) as charging stations of vestibules stacked above and/or below vestibule 130V3, all of the vestibules associated with the power supply of vestibule 130V3 may be designated as offline for charging and item 101 transfers. Still, the vestibule 130V3 may remain "online" so that bots can charge and transfer case units 101 at the remaining operational charging station (s) 290 of the vestibule 130V3. The vestibule 130V3 may also remain online with respect to item transfers such that, if bot 110X has a sufficient charge, the bot 110X can transfer items at a location of the inoperable charging station 290 and then move on to be charged at a next available charging station 290 at the same vestibule 130V3 or different vestibule 130V1, 130V2, 130V4. [000104] Referring to Figs. 27-29 and also to Figs. 18B and 22 the bot controller 298 and charge manager 299 may interact with each other for reserving resources within the storage and retrieval system 100. It is noted that Fig. 28 illustrates a state chart diagram for bot controller 298 interaction for reserving resources of the storage and retrieval system and Fig. 29 illustrates a sequence diagram of how each reservation request for a charging station translates into a reservation of the charging station. As an example, bot 110X may be designated by bot controller 298 for charging at charging station 290B of vestibule 130V. Travel of the bot 110X may be defined by waypoints 1101-1108 within the storage and retrieval system 100. As the bot travels the bot controller 298 of level manager 297 may look to each waypoint for reserving a resource of the storage and retrieval system to allow the bot 110X to travel along a predetermined course. Prior to or during reservation of the resources by the bot controller 298 the charge manager may confirm that a desired charging resource and any intervening charging resources are available or will be available at the time they are needed by the bot 110X. If the charging resources are available the bot controller 298 continues with planning the predetermined route, which in this example, is charging station 290B. If one or more of the charging resources and intervening charging resources are not or will not be available the route of the bot 110X may be re-routed to an available charging resource (and corresponding multilevel vertical conveyor) . In this example, the bot 110X may start in picking aisle 130A7 for picking a case unit 101. Picking aisle 103A7 may be reserved by the bot 110X while the bot 110 is located within the aisle 130A7. As the bot is travelling out of the picking aisle 130A7 a request to reserve an entrance onto guide line or travel path 130L4 is made and granted. Once on the guide line 130L4 a reservation is requested for travelling along vestibule 13 OV/multilevel vertical conveyor 150 entrance guide line or path 130C1 and is granted. The bot controller looks to the next waypoint 1107 and requests a reservation for the multilevel vertical conveyor transfer location 290T1 and if the availability of the transfer location 290T1 is verified the request is granted. The bot controller may check to see of the transfer location 290T1 is also a charging resource, which it is, and requests a reservation for charging station 290A and if the charging station is available the request is granted. Even though the bot 110X will not transfer case units 101 or charge at transfer location 290T1 /charging station 290A, the bot 110X passes through these areas on its way to charging station 290B and reserves transfer location 290T1 /charging station 290A to ensure passage to charging station 290B. The bot controller also looks to waypoint 1108 to reserve multilevel vertical conveyor transfer location 290T2 and if the availability of the transfer location 290T2 is verified the request is granted. The bot controller 298 may check to see of the transfer location 290T2 is also a charging resource, which it is, and requests a reservation for charging station 290B and if the charging station is available the request is granted. After the bot passes through transfer location 290T1 and charging station 290A the bot controller releases transfer location 290T1 and charging station 290A so these resources are available to other bots 110. While the bot 110X is at the transfer location 290T2, the bot 110X may transfer case units 101 between the bot 110X and the conveyor shelf 250 while simultaneously receiving a charge from charging station 290B. Upon reaching a quick charge level the bot 110X the bot controller 298 is notified of the quick charge being substantially complete and requests that the bot 110X leave the transfer location 290T2 and charging station 290B. The bot 110X verifies that it has left the transfer location 290T2 and charging station 290B and the bot controller releases the transfer location 290T2 and charging station 290B so they become available resources for other bots 110.

[000105] Referring again to Figs. 22 and 26, as described above, when a charging station 290 becomes inoperable the storage and retrieval system is configured to re-route a bot 110 to another operable charging station 290. In one exemplary embodiment when a charging station 290 becomes inoperable all affected bot controllers 298 are notified for taking appropriate action such as, for example, canceling jobs directed to the inoperable charging station. It is noted that in one exemplary embodiment the affected bot controller 298 may be bot controller for pick floor levels having charging stations powered by the same power supply as the inoperable charging station. Any bot jobs not yet scheduled (e.g. that have already been re-routed) may not be allocated to the inoperable charging stations 290 or their corresponding multilevel vertical conveyors 150 for at least the pick floor level on which the inoperable charging station 290 is located.

[000106] Referring again to Fig. 18B in the embodiments the controller 150C may be used to initiate and monitor charging of the bots 110. In one example the gang manager 290G may start the power supply 290P and the controller 150C may enable the power supply output. The controller 150C may monitor an operational status of the power supply and alert the gang manager 290G if there is any inoperability of the power supply 290P. The controller 150C may wait a predetermined amount of time before monitoring the power supply 290P (e.g. to avoid any inrush power spikes) and maintain a record of the current of the power supply and monitors the current for a condition where the current drops below a predetermined level. The gang manager 290G may turn off the power supply for any suitable reason (such as e.g. when a bot wants to enter or leave a charging station) and the controller 150C may turn off the power to the chargers and direct the bots 110 accordingly.

[000107] In a first aspect of the embodiments a pickface builder for a storage and retrieval system for storing goods units and having an in-feed conveyor and a picking device is provided. Each goods unit holds at least one product package therein. The pickface builder includes a frame, a pusher member movably coupled to the frame, and a snugger member movably coupled to the frame, wherein the pickface builder is configured to receive goods units from the in-feed conveyor and the pusher member and snugger member are movable at least in a direction transverse to a direction of goods unit travel on the in-feed conveyor and configured to form the goods units into a pickface picked by the picking device as a unit and having a predetermined reference datum relating the pickface to a placement position of goods units forming the pickface along a storage surface of the storage and retrieval system.

[000108] In accordance with a first sub-aspect of the first aspect of the embodiments the pusher member may be movable in at least two orthogonal directions for pushing the goods units towards the snugger member.

[000109] In accordance with the first sub-aspect of the first aspect of the embodiments, the snugger member is positioned to create the predetermined reference datum as the pusher member pushes goods units towards the snugger member.

[000110] In accordance with the first aspect of the embodiments, the pickface builder further includes a movable gate disposed adjacent the snugger member for retaining at least one goods unit as a pickface is formed from the at least one goods unit .

[000111] In accordance with a second sub-aspect of the first aspect of the embodiments, the pickface builder further includes a resolver member configured to obtain goods unit data as goods units are transferred to the pickface builder from the in-feed conveyor . [000112] In accordance with the second sub-aspect of the first aspect of the embodiments, the pickface builder is configured to form pickfaces based on at least the goods unit data obtained from the resolver member.

[000113] In accordance with the second sub-aspect of the first aspect of the embodiments, the resolver member is configured to confirm an identity of the goods units being transferred to pickface builder form the in-feed conveyor.

[000114] In accordance with the second sub-aspect of the first aspect of the embodiments, the pickface builder is configured to modify motion profiles of at least one of the pusher member and snugger member based on the goods unit data from the resolver member .

[000115] In accordance with the first aspect of the embodiments, the pickface builder further comprises a controller in communication with a controller of the picking device, the controller being configured to associate pickfaces with shelves of the picking device for tracking a position of the pickfaces on the picking device.

[000116] In accordance with a third sub-aspect of the first aspect of the embodiments, the pickface builder includes a controller configured to create motion profiles for the pusher member and snugger member based at least on predetermined goods unit data accessible by the controller.

[000117] In accordance with the third sub-aspect of the first aspect of the embodiments, wherein the controller includes a memory configured to store the predetermined goods unit data.

[000118] In accordance with the third sub-aspect of the first aspect of the embodiments the storage and retrieval system includes a system controller wherein the pickface builder is in direct or indirect communication with the system controller and the predetermined case goods unit is stored in a memory of the system controller.

[000119] In accordance with a fourth sub-aspect of the first aspect of the embodiments the pickface is formed from uncontained goods units.

[000120] In accordance with the fourth sub-aspect of the first aspect of the embodiments the pickface is a surface of the uncontained goods units forming the pickface.

[000121] In a second aspect of the aspect of the embodiments a storage and retrieval system is provided. The storage and retrieval system includes an in-feed conveyor, an in-feed station, a pickface builder disposed between the in-feed conveyor and in-feed station, and picking device connected to the in-feed station, the in-feed station being configured to transfer goods units to the picking device where each goods unit holds at least one product package therein. The pickface builder includes a frame, a pusher member movably coupled to the frame, and a snugger member movable coupled to the frame, wherein the pickface builder is configured to receive goods units from the in-feed conveyor and the pusher member and snugger member are movable at least in a direction transverse to a direction of goods unit travel on the in-feed conveyor and configured to form the goods units picked by the picking device as a unit into a pickface having a predetermined reference datum relating the pickface to a placement position of goods units forming the pickface along a storage surface of the storage and retrieval system.

[000122] In accordance with the second aspect of the embodiments, the pickface builder is located downstream of an elbow in the in-feed conveyor so that the pusher member and snugger member are substantially transverse to a direction of travel of the goods units from the in-feed station to the picking device.

[000123] In accordance with a first sub-aspect of the second aspect of the embodiments, the pickface builder further includes a controller configured to create motion profiles for the pusher member and snugger member based at least on predetermined goods unit data accessible by the controller.

[000124] In accordance with the first sub-aspect of the second aspect of the embodiments the controller includes a memory configured to store the predetermined goods unit data.

[000125] In accordance with the first sub-aspect of the second aspect of the embodiments the storage and retrieval system includes a system controller wherein the pickface builder is in direct or indirect communication with the system controller and the predetermined goods unit data is stored in a memory of the system controller.

[000126] In accordance with a third aspect of the embodiments, a pickface builder for a storage and retrieval system for storing goods units and having an in-feed conveyor and a picking device is provided. The pickface builder includes a frame, a pusher member movably coupled to the frame, and a snugger member movably coupled to the frame, wherein the pickface builder is configured to receive goods units from the in-feed conveyor and the pusher member and snugger member are configured to form the goods units into a pickface picked by the picking device as a unit and having a predetermined reference datum where the predetermined reference datum depends on at least one predetermined pickface characteristic and relates the pickface to a placement position of goods units forming the pickface along a storage surface of the storage and retrieval system.

[000127] In accordance with a first sub-aspect of the third aspect of the embodiments the pickface builder further includes a controller configured to create motion profiles for the pusher member and snugger member based on the at least one predetermined pickface characteristic.

[000128] In accordance with the first sub-aspect of the third aspect of the embodiments the controller is in direct or indirect communication with a system controller of a storage and retrieval system and is configured to access the at least one predetermined pickface characteristic from a memory of the system controller. [000129] In a fourth aspect of the embodiments, a multilevel vertical conveyor system for transporting uncontained case units to and from a multilevel storage structure having an array of vertically stacked storage levels is provided. The multilevel vertical conveyor includes a frame having discontinuous platform guide members, a drive member connected to the frame, and support platforms coupled to the drive member, each of the support platforms having support members and at least two follower members configured to engage the discontinuous platform guide members. The drive member is configured to move the support platforms relative to the frame in a substantially continuous vertical loop, each of the support platforms being configured to support multiple uncontained case units where each of the multiple uncontained case units is disposed at a respective predetermined area of a respective support shelf. The support members are guided by the discontinuous platform guide members substantially throughout a path of the substantially continuous vertical loop, where the support members are guided in three point contact substantially throughout the path through engagement of the at least two follower members with the discontinuous platform guide members where the three point contact is effected by one of the at least two follower members engaging a respective discontinuous platform guide member when another of the at least two follower members passes a discontinuity in the respective guide member.

[000130] In accordance with the fourth aspect of the embodiments, the multiple uncontained case units are cantilevered on the support platforms.

[000131] In accordance with the fourth aspect of the embodiments, the respective predetermined area of the respective support platform comprises an array of predetermined areas.

[000132] In accordance with a first sub-aspect of the fourth aspect of the embodiments, at least one transfer device extends into a path of the support platforms, the at least one transfer device being configured to load or unload the uncontained case units from a respective predetermined area of a support platform.

[000133] In accordance with the first sub-aspect of the fourth aspect of the embodiments, at least one of the uncontained case units are placed in or removed from the respective predetermined area of the respective support platform substantially independent of other uncontained case units disposed in another different respective predetermined area of the respective support platform.

[000134] In accordance with the first sub-aspect of the fourth aspect of the embodiments, the at least one transfer device comprises at least one in-feed transfer station extending into a path of the support platforms, the support platforms being configured to interface with the at least one in-feed transfer station to receive the uncontained case units, from the at least one in-feed transfer station, in at least one predetermined area of an inbound support platform, the at least one predetermined area of the inbound support platform corresponding to a location of the at least one in-feed transfer station. In a further aspect the at least one in-feed transfer station comprises an accumulator configured to form individual bot loads or uncontained case units for placement into the respective predetermined area of the inbound support platform, where the uncontained case units include at least one uncontained case unit. In another aspect the at least one in-feed transfer station comprises a depalletizer for removing the uncontained case units from a container.

[000135] In accordance with the first sub-aspect of the fourth aspect of the embodiments, the at least one transfer device comprises at least one out-feed transfer station extending into the path of the support platforms, the support shelves being configured to interface with the at least one out-feed transfer station to remove the uncontained case units, with the at least one out-feed transfer station, from at least one predetermined area of an outbound support platform, the predetermined area of the outbound support platform corresponding to a location of the at least one out-feed transfer station. In a further aspect the at least one out-feed transfer station comprises a palletizer for placing the uncontained case units to a container. In yet another aspect the support platforms and the at least one out- feed transfer station are configured such that uncontained case units are removed from the support platforms in a predetermined order .

[000136] In accordance with the first sub-aspect of the fourth aspect of the embodiments, each support platform comprises first elongated fingers and the at least one transfer device comprises second elongated fingers, the first and second elongated fingers being configured to allow the support platforms to pass through each of the at least one transfer device for effecting a transfer of the multiple uncontained case units.

[000137] In accordance with the first sub-aspect of the first aspect of the embodiments, wherein the at least one transfer device comprises more than one transfer device disposed in a horizontally staggered vertical stack on respective inbound and outbound sides of the vertical conveyor system.

[000138] In accordance with the first sub-aspect of the fourth aspect of the embodiments, wherein the at least one transfer device comprises more than one transfer device disposed in vertical stacks one above the other on respective inbound and outbound sides of the vertical conveyor system such that at least one of the more than one transfer device extends into respective inbound and outbound support platforms by different amounts than other ones of the at least one transfer device.

[000139] In accordance with the first sub-aspect of the fourth aspect of the embodiments, the at least one transfer device comprises bot transfer locations disposed on each level of the multilevel storage structure for allowing transport vehicles to transfer the uncontained case units between storage modules disposed on each level and the support platforms.

[000140] In accordance with the fourth aspect of the embodiments, the multilevel vertical conveyor system further comprises transport vehicles configured to interface directly with the support platforms, each of the transport vehicles being configured to transport at least one uncontained case unit between the support platforms and storage modules of a respective storage level with substantially one picking operation .

[000141] In a fifth aspect of the embodiments, a transport system for a storage and retrieval system having an array of storage levels where each storage level having respective storage areas is provided. The transport system has a vertical conveyor having a frame with discontinuous platform guide members and support platforms movably coupled to the frame, the support platforms having at least two follower members configured to engage the discontinuous platform guide members and being connected to the frame through a three point of contact connection effected by one of the at least two follower members engaging a respective discontinuous platform guide member when another of the at least two follower members passes a discontinuity in the respective guide member. The transport system also includes a transfer device located on respective ones of the storage levels. Each support platform is configured to hold one or more uncontained case units in predetermined areas of the support platform. The vertical conveyor is configured to transport the one or more uncontained cases to or from more than one of the storage levels where the one or more uncontained cases may be selectably placed on or removed from the vertical conveyor by the transfer device, the vertical conveyor having a conveyor to transfer device interface configured to transfer the uncontained case units substantially directly between each support platform and the transfer device for transport to or from the storage areas.

[000142] In accordance with the fifth aspect of the embodiments, the predetermined areas comprise an array of areas, and the one more uncontained cases may be selectably placed on or removed from a platform with more than one transfer device interfacing to different portions of the predetermined areas.

[000143] In accordance with the fifth aspect of the embodiments, the support platforms include first elongated fingers and the transfer device includes second elongated fingers, the first and second elongated fingers being configured to pass between one another for transferring uncontained case units between each support platform and the transfer device.

[000144] In a sixth aspect of the embodiments a charging system for autonomous transport vehicles in a warehouse storage and retrieval system is provided. The charging system includes at least one charging contact disposed on each pick floor level of the storage and retrieval system, each of the at least one charging contact being located at a transfer station, at least one power supply configured to supply power to the at least one charging contact and a first controller in communication with the transfer station and being configured to communicate information relating to a transfer of items between the transfer station and a predetermined one of the autonomous transport vehicles and to apply power from the power supply to the at least one charging contact for charging the predetermined autonomous transport vehicle corresponding to the transfer and located at the multilevel vertical conveyor transfer station, wherein the first controller is configured to supply power to the charging contacts for charging the predetermined autonomous transport vehicle simultaneously with the predetermined autonomous transport vehicle exchanging items at the transfer station .

[000145] In accordance with a first sub-aspect of the sixth aspect of the embodiments, the charging system further comprising a capacitor disposed on the autonomous transport vehicle and a receptacle configured to interface with the at least one charging contact where the engagement is configured to transfer power to the capacitor.

[000146] In accordance with the first sub-aspect of the sixth aspect of the embodiments, the receptacle includes a contact pad and the at least one charging contact includes actuable members configured to engage the contact pad.

[000147] In accordance with the sixth aspect of the embodiments, each pick floor of the storage and retrieval system includes at least one vestibule extending from a transfer deck and located adjacent a respective multilevel vertical conveyor, wherein at least one charging contact is located in each of the at least one vestibule.

[000148] In accordance with the sixth aspect of the embodiments, the transfer station includes a multilevel vertical conveyors and the operation of the at least one charging contact and an associated multilevel vertical conveyor are linked such that when the at least one charging contact is inoperable the controller deems the multilevel vertical conveyor inoperable at least for the pick floor level on which the at least one charging contact is located.

[000149] In accordance with the sixth aspect of the embodiments, the first controller is configured to control operations of the power supply and the multilevel vertical conveyor .

[000150] In accordance with a second sub-aspect of the sixth aspect of the embodiments, the charging system further comprises a second controller configured to effect a charge cycle of each autonomous transport vehicle located on at least one pick floor level simultaneously with the exchange of items with the multilevel vertical conveyor.

[000151] In accordance with a seventh aspect of the embodiments, a storage and retrieval system is provided. The storage and retrieval system includes, at least one autonomous transport vehicle, at least one transfer station having an operable and inoperable state where in the operable state the at least one transfer station is configured to allow transfer of items from and to the at least one autonomous transport vehicle, at least one charging station disposed on each pick floor level of the storage and retrieval system, each of the at least one charging contact being located at a respective one of the at least one transfer station, at least one power supply configured to supply power to the at least one charging contact, and a controller in communication with the transfer station and being configured to communicate information relating to a transfer of items between the transfer station and a predetermined one of the autonomous transport vehicles and to apply power from the power supply to the at least one charging station for charging the at least one autonomous transport vehicle located at the transfer station, wherein the controller is configured to supply power to the charging station for charging a predetermined autonomous transport vehicle corresponding to the transfer of items simultaneously with the predetermined autonomous transport vehicle exchanging items related to the transfer at a predetermined transfer station when the predetermined transfer station is in the operative state and to supply power to the charging station for charging another of the at least one autonomous vehicles located at the predetermined transfer station when the predetermined transfer station is in the inoperative state.

[000152] In accordance with the seventh aspect of the embodiments, the storage and retrieval system further includes at least one multilevel conveyor and at least one pickfloor level having storage locations, atleast one vestibule and a transfer deck connecting the storage locations with the at least one vestibule, each of the at least one vestibules having at least one of the at least one transfer station configured to provide access to a respective one of the at least one multilevel vertical conveyor, wherein the controller is configured to control operations of at least one of the at least one multilevel vertical conveyors and operations of at least one charging station located in vestibules associated with the respective multilevel vertical conveyor.

[000153] In accordance with the seventh aspect of the embodiments, a level controller is connected to each pick floor level and configured to control storage and retrieval operations of the respective level, the level controller being further configured to link operations of the at least one multilevel vertical conveyors with associated charging stations such that access to the at least one multilevel vertical conveyor is prevented when one or more of the associated charging stations is inoperable.

[000154] In accordance with a first sub-aspect of the seventh aspect of the embodiments, the storage and retrieval system includes at least one power supply, the at least one power supply being commonly connected to charging stations of vertically adjacent ones of the at least one pick floor level.

[000155] In accordance with the first sub-aspect of the seventh aspect of the embodiments, the charging stations commonly connected to the at least one power supply comprising a two by two array of charging stations where a first two of the charging stations in the array are located on a first pick floor level and a second two of the charging stations in the array are located on a second pick floor level, the first two of the charging stations and the second two of the charging stations being vertically stacked one above the other.

[000156] In accordance with the first sub-aspect of the seventh aspect of the embodiments, each vestibule includes at least two charging stations arranged on a common linear path.

[000157] In accordance with the first sub-aspect of the second aspect of the embodiments, the transfer deck includes an array of autonomous transport vehicle travel paths, the array including longitudinal travel paths providing access to the storage locations and the at least one vestibule and transverse travel paths providing shunts between the longitudinal travel paths .

[000158] In accordance with the second sub-aspect of the seventh aspect of the embodiments, the controller is configured to reserve one or more of the charging stations for allowing an autonomous transport vehicle access to the one or more of the at least two charging stations.

[000159] In accordance with the seventh aspect of the embodiments, the controller is configured to re-route an autonomous transport vehicle destined for a charging station at a first vestibule to a charging station at another vestibule when the charging station at the first vestibule is inoperable.

[000160] In accordance with the seventh aspect of the embodiments, when in the unallocated state the transfer station is not configured to allow transfer of items from and to the at least one autonomous transport vehicle.

[000161] It should be understood that the embodiments described herein may be used individually or in any suitable combination thereof. It should also be understood that the foregoing description is only illustrative of the embodiments. Various alternatives and modifications can be devised by those skilled in the art without departing from the embodiments. Accordingly, the embodiments are intended to embrace all such alternatives, modifications and variances within the scope of the appended claims .

[000162] What is claimed