The embodiments generally relate to material handling systems and, more particularly, to automated storage and retrieval systems.
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.
The foregoing aspects and other features of the disclosed embodiments are explained in the following description, taken in connection with the accompanying drawings, wherein:
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.
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, U.S. Provisional Patent Application No. 61/423,340, filed on Dec. 15, 2010, U.S. patent application Ser. No. 13/326,674, filed on Dec. 15, 2011, and U.S. patent application Ser. No. 12/757,381, filed on Apr. 9, 2010 (now U.S. Pat. No. 8,740,538, issued Jun. 3, 2014), 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 transport 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 140 (
As described above, the storage structure 130 may include multiple levels of storage rack modules where, in the embodiments, each level includes respective picking aisles 130A and at least one transfer deck 130B 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 140 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. The storage structure 130 may be substantially similar to the storage structure described in U.S. Provisional Patent Application No. 61/423,340, filed on Dec. 15, 2010, U.S. patent application Ser. No. 13/326,674, filed on Dec. 15, 2011, U.S. patent application Ser. No. 12/757,381, filed on Apr. 9, 2010 (now U.S. Pat. No. 8,740,538, issued Jun. 3, 2014), U.S. patent application Ser. No. 14/089,434, filed on Nov. 25, 2013 (now U.S. Pat. No. 9,051,120, issued Jun. 9, 2015), and U.S. patent application Ser. No. 14/733,341, filed on Jun. 8, 2015 (now U.S. Pat. No. 9,771,217, issued Sep. 26, 2017), the disclosures of which are incorporated herein by reference in their entireties.
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 U.S. patent application Ser. No. 14/757,337, filed on Apr. 9, 2010 (now U.S. Pat. No. 8,594,835, issued Nov. 26, 2013), and U.S. patent application Ser. No. 12/757,220, filed on Apr. 9, 2010 (now U.S. Pat. No. 9,096,375, issued Aug. 4, 2015), 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.
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, U.S. patent application Ser. No. 12/757,354, filed on Apr. 9, 2010 (now U.S. Pat. No. 9,694,975, issued Jul. 4, 2017), and U.S. patent application Ser. No. 12/757,220, filed on Apr. 9, 2010 (now U.S. Pat. No. 9,096,375, issued Aug. 4, 2015), the disclosures of which are incorporated herein by reference in their entireties.
Referring now to
Generally, the multilevel vertical conveyors include payload shelves 730 (
Referring still to
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.
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
Referring now to
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 140. 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.
It is noted that while the interface between the bot transfer stations 140 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 U.S. patent application Ser. No. 12/757,312, filed on Apr. 9, 2010 (now U.S. Pat. No. 8,425,173, issued Apr. 23, 2013), previously incorporated herein by reference in its entirety). For exemplary purposes only, referring now to
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
In operation, referring also to
Referring to
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 140. 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.
As can be seen in
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.
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.
Referring now to
Feed station 141 has driven roller bed 2112 to transfer in the x-axis 2014. Feed station 141 has a set of extendable or retractable fingers and payload bed 2020 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
Referring now to
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
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.
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.
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.
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).
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.
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.
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 (
Referring now to
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.
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.
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.
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.
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.
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 case goods unit as goods units are transferred to the pickface builder from the in-feed conveyor.
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.
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 the pickface builder from the in-feed conveyor.
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.
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.
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.
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.
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 goods unit data is stored in a memory of the system controller.
In accordance with a fourth sub-aspect of the first aspect of the embodiments the pickface is formed from uncontained goods units.
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.
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.
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.
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.
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.
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.
In accordance with a third aspect of the embodiments, a pickface builder for a storage and retrieval system for storing goods unit and having an in-feed conveyor and a picking device is provided. Each goods unit holding at last 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 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.
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.
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.
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.
This application is a continuation of U.S. Non-provisional patent application Ser. No. 15/991,779, filed May 29, 2018, (now U.S. Pat. No. 10,875,722), which is a continuation of U.S. Non-provisional patent application Ser. No. 15/332,997, filed on Oct. 24, 2016, (now U.S. Pat. No. 9,981,808), which is a continuation of U.S. Non-provisional patent application Ser. No. 13/326,869, filed on Dec. 15, 2011, (now U.S. Pat. No. 9,475,649), which claims priority from and the benefit of U.S. Provisional Patent Application No. 61/423,242, filed on Dec. 15, 2010, the disclosures of which are incorporated herein by reference in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
1887667 | Wheeler | Nov 1932 | A |
2877575 | Stedt | Mar 1959 | A |
2945604 | Kroll et al. | Jul 1960 | A |
3016154 | Ugolini et al. | Jan 1962 | A |
3161303 | Burrows | Dec 1964 | A |
3554390 | Saul | Jan 1971 | A |
3581915 | Saul | Jun 1971 | A |
3738506 | Cornford et al. | Jun 1973 | A |
3845715 | Hochstrasser | Nov 1974 | A |
3876095 | Stedt | Apr 1975 | A |
4064986 | Bertovich | Dec 1977 | A |
4307988 | Page et al. | Dec 1981 | A |
4394104 | Camerini et al. | Jul 1983 | A |
4415975 | Burt | Nov 1983 | A |
4428708 | Burt | Jan 1984 | A |
4492504 | Hainsworth | Jan 1985 | A |
4678390 | Bonneton et al. | Jul 1987 | A |
4777416 | George, II et al. | Oct 1988 | A |
4883401 | Kavieff | Nov 1989 | A |
4909697 | Bernard, II et al. | Mar 1990 | A |
4967370 | Stern et al. | Oct 1990 | A |
4987992 | Pfleger | Jan 1991 | A |
5220263 | Onishi et al. | Jun 1993 | A |
5273392 | Bernard, II et al. | Dec 1993 | A |
5323098 | Hamaguchi et al. | Jun 1994 | A |
5337880 | Claycomb et al. | Aug 1994 | A |
5350270 | Stallard et al. | Sep 1994 | A |
5370492 | Gleyze et al. | Dec 1994 | A |
5395206 | Cerny, Jr. | Mar 1995 | A |
5509538 | Spindler et al. | Apr 1996 | A |
5548516 | Gudat et al. | Aug 1996 | A |
5559696 | Borenstein | Sep 1996 | A |
5611422 | Harkonen | Mar 1997 | A |
5615992 | Proske et al. | Apr 1997 | A |
5664929 | Esaki et al. | Sep 1997 | A |
5709291 | Nishino et al. | Jan 1998 | A |
5718322 | Mulhern | Feb 1998 | A |
5798920 | Crucius et al. | Aug 1998 | A |
5801506 | Netzler | Sep 1998 | A |
5810540 | Castaldi | Sep 1998 | A |
5974348 | Rocks | Oct 1999 | A |
6061607 | Bradley et al. | May 2000 | A |
6149366 | Deandrea | Nov 2000 | A |
6164045 | Focke | Dec 2000 | A |
6170635 | Rommelli | Jan 2001 | B1 |
6213704 | White et al. | Apr 2001 | B1 |
6257826 | Neagle et al. | Jul 2001 | B1 |
6289260 | Bradley et al. | Sep 2001 | B1 |
6295922 | Salamone et al. | Oct 2001 | B1 |
6377867 | Bradley et al. | Apr 2002 | B1 |
6394260 | Barth et al. | May 2002 | B1 |
6397990 | Brien et al. | Jun 2002 | B1 |
6463360 | Terada et al. | Oct 2002 | B1 |
6496755 | Wallach et al. | Dec 2002 | B2 |
6503043 | Smith et al. | Jan 2003 | B1 |
6597143 | Song et al. | Jul 2003 | B2 |
6663334 | Warhurst et al. | Dec 2003 | B2 |
6764373 | Osawa et al. | Jul 2004 | B1 |
6836701 | McKee | Dec 2004 | B2 |
6859682 | Naka et al. | Feb 2005 | B2 |
6922632 | Foxlin | Jul 2005 | B2 |
7039501 | Freeman et al. | May 2006 | B2 |
7054716 | McKee et al. | May 2006 | B2 |
7066291 | Martins et al. | Jun 2006 | B2 |
7069124 | Whittaker et al. | Jun 2006 | B1 |
7101139 | Benedict | Sep 2006 | B1 |
7133746 | Abramson et al. | Nov 2006 | B2 |
7137593 | Baatz | Nov 2006 | B2 |
7284652 | Zeitler et al. | Oct 2007 | B2 |
7329081 | Baker et al. | Feb 2008 | B2 |
7332890 | Cohen et al. | Feb 2008 | B2 |
7376487 | Kumhyr | May 2008 | B2 |
7397213 | Im et al. | Jul 2008 | B2 |
7421268 | Steiner et al. | Oct 2008 | B2 |
7456596 | Goodall et al. | Nov 2008 | B2 |
7460462 | Mejia et al. | Dec 2008 | B2 |
7499155 | Cappelletti | Mar 2009 | B2 |
7520376 | Bar | Apr 2009 | B2 |
7532947 | Waddington et al. | May 2009 | B2 |
7568572 | Zeitler | Aug 2009 | B2 |
7575406 | Hofmeister et al. | Aug 2009 | B2 |
7615957 | Kim et al. | Nov 2009 | B2 |
7653457 | Bloom | Jan 2010 | B2 |
7686560 | Laurin et al. | Mar 2010 | B2 |
7693757 | Zimmerman | Apr 2010 | B2 |
7695235 | Rallis | Apr 2010 | B1 |
7706917 | Chiappetta et al. | Apr 2010 | B1 |
7725213 | Hysell | May 2010 | B2 |
7725253 | Foxlin | May 2010 | B2 |
7729801 | Abramson | Jun 2010 | B2 |
7771152 | Waltersbacher | Aug 2010 | B2 |
7783383 | Eliuk et al. | Aug 2010 | B2 |
7826919 | Andrea et al. | Nov 2010 | B2 |
7826920 | Stevens et al. | Nov 2010 | B2 |
7845486 | Spencer et al. | Dec 2010 | B2 |
7856290 | Kumhyr | Dec 2010 | B2 |
7861844 | Hayduchok et al. | Jan 2011 | B2 |
7873469 | Andrea et al. | Jan 2011 | B2 |
7894940 | Kumhyr | Feb 2011 | B2 |
7931431 | Benedict et al. | Apr 2011 | B2 |
7941244 | Somin et al. | May 2011 | B2 |
7944368 | Carter et al. | May 2011 | B2 |
7959395 | Hofmeister et al. | Jun 2011 | B2 |
7963384 | Lafontaine | Jun 2011 | B2 |
7972102 | Ward et al. | Jul 2011 | B2 |
7988398 | Hofmeister et al. | Aug 2011 | B2 |
7991505 | Lert, Jr. et al. | Aug 2011 | B2 |
8006824 | Wada et al. | Aug 2011 | B2 |
8024064 | Sanghavi et al. | Sep 2011 | B1 |
8028822 | Braunstein | Oct 2011 | B2 |
8046103 | Abramson et al. | Oct 2011 | B2 |
8046160 | Carter et al. | Oct 2011 | B2 |
8047756 | Tuffs et al. | Nov 2011 | B2 |
8425173 | Lert et al. | Apr 2013 | B2 |
8467898 | Cardoni | Jun 2013 | B2 |
8695619 | Kissinger | Apr 2014 | B2 |
8696010 | Toebes et al. | Apr 2014 | B2 |
8965619 | Sullivan et al. | Feb 2015 | B2 |
9187244 | Toebes et al. | Nov 2015 | B2 |
9475649 | Toebes et al. | Oct 2016 | B2 |
20020037208 | Patrito | Mar 2002 | A1 |
20020124389 | Matson | Sep 2002 | A1 |
20040088081 | Song et al. | May 2004 | A1 |
20040238326 | Lichti | Dec 2004 | A1 |
20050238455 | Toteff | Oct 2005 | A1 |
20050238465 | Razumov | Oct 2005 | A1 |
20060072988 | Hariki et al. | Apr 2006 | A1 |
20070061041 | Zweig | Mar 2007 | A1 |
20070065258 | Benedict et al. | Mar 2007 | A1 |
20070065259 | Talley | Mar 2007 | A1 |
20070071585 | Henkel | Mar 2007 | A1 |
20070114975 | Cohen et al. | May 2007 | A1 |
20070125727 | Winkler | Jun 2007 | A1 |
20070267998 | Cohen et al. | Nov 2007 | A1 |
20080007203 | Cohen et al. | Jan 2008 | A1 |
20080024274 | Ishida et al. | Jan 2008 | A1 |
20080025833 | Baker et al. | Jan 2008 | A1 |
20080044262 | Kim et al. | Feb 2008 | A1 |
20080075357 | Yoon et al. | Mar 2008 | A1 |
20080080963 | Bufano et al. | Apr 2008 | A1 |
20080129445 | Kraimer et al. | Jun 2008 | A1 |
20080174268 | Koo et al. | Jul 2008 | A1 |
20080281717 | Kortelainen | Nov 2008 | A1 |
20090033316 | Hosek et al. | Feb 2009 | A1 |
20090074545 | Lert, Jr. et al. | Mar 2009 | A1 |
20090085741 | Ravi et al. | Apr 2009 | A1 |
20090148259 | Shani | Jun 2009 | A1 |
20090224750 | Hosek et al. | Sep 2009 | A1 |
20090265031 | Tachibana et al. | Oct 2009 | A1 |
20090284245 | Kirby et al. | Nov 2009 | A1 |
20090315501 | Li et al. | Dec 2009 | A1 |
20100114363 | Cardoni | May 2010 | A1 |
20100118149 | Levin et al. | May 2010 | A1 |
20100121481 | Talley et al. | May 2010 | A1 |
20100183409 | Checketts et al. | Jul 2010 | A1 |
20100185353 | Barwick et al. | Jul 2010 | A1 |
20100188210 | Howard et al. | Jul 2010 | A1 |
20100277005 | Karalis et al. | Nov 2010 | A1 |
20100277121 | Hall et al. | Nov 2010 | A1 |
20100290878 | Ricketts | Nov 2010 | A1 |
20100295943 | Cha et al. | Nov 2010 | A1 |
20100305854 | Kammel et al. | Dec 2010 | A1 |
20100308939 | Kurs | Dec 2010 | A1 |
20100316468 | Lert et al. | Dec 2010 | A1 |
20100322746 | Lert et al. | Dec 2010 | A1 |
20110038692 | Hofmeister et al. | Feb 2011 | A1 |
20110043373 | Best et al. | Feb 2011 | A1 |
20110058926 | Winkler | Mar 2011 | A1 |
20110068943 | Lane, Jr. | Mar 2011 | A1 |
20110082583 | Kumhyr | Apr 2011 | A1 |
20110102144 | Okina et al. | May 2011 | A1 |
20110106295 | Miranda et al. | May 2011 | A1 |
20110118903 | Kraimer et al. | May 2011 | A1 |
20110125323 | Gutmann et al. | May 2011 | A1 |
20110148364 | Ota | Jun 2011 | A1 |
20110182703 | Alan | Jul 2011 | A1 |
20110202175 | Romanov et al. | Aug 2011 | A1 |
20110208350 | Eliuk et al. | Aug 2011 | A1 |
20110216185 | Laws et al. | Sep 2011 | A1 |
20110238206 | Somin et al. | Sep 2011 | A1 |
20110254503 | Widmer et al. | Oct 2011 | A1 |
20110285349 | Widmer et al. | Nov 2011 | A1 |
20110297509 | Taylor | Dec 2011 | A1 |
20120189409 | Toebes et al. | Jun 2012 | A1 |
20120179337 | Doan | Jul 2012 | A1 |
20120185082 | Toebes et al. | Jul 2012 | A1 |
20120189416 | Toebes et al. | Jul 2012 | A1 |
20120195720 | Sullivan et al. | Aug 2012 | A1 |
20150336741 | Ahammer et al. | Nov 2015 | A1 |
Number | Date | Country |
---|---|---|
1480388 | Mar 2004 | CN |
1733579 | Feb 2006 | CN |
101068729 | Nov 2007 | CN |
2150500 | Apr 1973 | DE |
10356563 | Jun 2005 | DE |
102009017556 | Oct 2010 | DE |
0698530 | Feb 1996 | EP |
0285527 | Oct 1998 | EP |
0995704 | Apr 2000 | EP |
1193195 | Apr 2002 | EP |
1818286 | Aug 2007 | EP |
4416419 | Jul 1969 | JP |
60183405 | Sep 1985 | JP |
61094905 | May 1986 | JP |
62166701 | Jul 1987 | JP |
62166710 | Jul 1987 | JP |
311335 | May 1991 | JP |
03111335 | May 1991 | JP |
1991111335 | May 1991 | JP |
03253203 | Nov 1991 | JP |
465211 | Jun 1992 | JP |
07187329 | Jul 1995 | JP |
08009055 | Jan 1996 | JP |
08251716 | Sep 1996 | JP |
2001084037 | Mar 2001 | JP |
2003012119 | Jan 2003 | JP |
2004273283 | Sep 2004 | JP |
2005119332 | May 2005 | JP |
2005138956 | Jun 2005 | JP |
2005154067 | Jun 2005 | JP |
2005154097 | Jun 2005 | JP |
2008100777 | Jan 2008 | JP |
2010520076 | Jun 2010 | JP |
2012184085 | Sep 2012 | JP |
20120211019 | Nov 2012 | JP |
20120013979 | Feb 2012 | KR |
393437 | Jun 2000 | TW |
588712 | May 2004 | TW |
2005071597 | Aug 2005 | WO |
2008107769 | Sep 2008 | WO |
2010118412 | Oct 2010 | WO |
2012044734 | Apr 2012 | WO |
Entry |
---|
International Search Report, Chinese Patent Applicaton for Invention No. 201180067621.6, dated Oct. 28, 2014. |
International Search Report, International Patent Application No. PCT/US2011/065248, dated Mar. 20, 2012. |
International Search Report, International Application No. PCT/US2014/030217, dated Jul. 7, 2014. |
Number | Date | Country | |
---|---|---|---|
20210114816 A1 | Apr 2021 | US |
Number | Date | Country | |
---|---|---|---|
61423242 | Dec 2010 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15991779 | May 2018 | US |
Child | 17136475 | US | |
Parent | 15332997 | Oct 2016 | US |
Child | 15991779 | US | |
Parent | 13326869 | Dec 2011 | US |
Child | 15332997 | US |