The exemplary 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 the case units 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 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 have a storage and retrieval system for efficiently storing and retrieving individual case units without containing those case units in a carrier or on a pallet.
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 one exemplary embodiment 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 case units not stored in trays, on totes or on pallets, e.g. uncontained). It is noted that the case units may include cases of case units (e.g. case of soup cans, boxes of cereal, etc.) or individual case units that are adapted to be taken off of or placed on a pallet. In accordance with the exemplary embodiments, shipping cases or case units (e.g. cartons, barrels, boxes, crates, jugs, or any other suitable device for holding case units) may have variable sizes and may be used to hold case units in shipping and may be configured so they are capable of being palletized for shipping. It is noted that when, for example, bundles or pallets of case units 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 case units (e.g. each pallet may hold different types of case units—a pallet holds a combination of soup and cereal). In alternate embodiments the storage and retrieval system described herein may be applied to any environment in which case units 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 one exemplary embodiment, the storage and retrieval system may include in-feed and out-feed transfer stations 170, 160, multilevel vertical conveyors 150A, 150B, a storage structure 130, and a number of autonomous vehicular transport robots 110 (referred to herein as “bots”). In alternate embodiments the storage and retrieval system may also include robot or bot transfer stations 140 (
It is noted that the multilevel vertical conveyors may be substantially similar to those described in U.S. patent application Ser. No. 12/757,354, entitled “LIFT INTERFACE FOR STORAGE AND RETRIEVAL SYSTEMS,”, previously incorporated by reference. For example, referring to
Generally, the multilevel vertical conveyors include payload shelves 730 (
Referring also 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.
In one exemplary embodiment 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 this exemplary embodiment, the accumulators 1010A, 1010B are configured to form the uncontained case units 1000 into the individual bot pickfaces 750-753 prior to loading a respective position A-D on the multilevel vertical conveyor 730. In one exemplary embodiment, 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 case units 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 case units flush, etc.) and, for example, abut the case units 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 one exemplary embodiment 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 another exemplary embodiment, 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 alternate 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.
In an alternate embodiment, the bots 110 may interface directly with the multilevel vertical conveyors 150A, 150B while in alternate embodiments the bots 110 may interface indirectly with the multilevel vertical conveyors through, for example, respective bot transfer stations 140 (which may have extendable fingers for interfacing with slatted support shelves of the multi-level vertical conveyors which may be substantially similar to those described in U.S. patent application Ser. No. 12/757,354, entitled “LIFT INTERFACE FOR STORAGE AND RETRIEVAL SYSTEMS”, previously incorporated by reference). 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, entitled “AUTONOMOUS TRANSPORTS FOR STORAGE AND RETRIEVAL SYSTEMS,” (now U.S. Pat. No. 8,425,173), previously incorporated by reference herein 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 alternate 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
The bots may be substantially similar to those described in U.S. patent application Ser. No. 12/757,312, entitled “AUTONOMOUS TRANSPORTS FOR STORAGE AND RETRIEVAL SYSTEMS,”, previously incorporated by reference herein. For example, referring now to
As can be seen in
In one exemplary embodiment, the drive system 1210 may include two drive wheels 1211, 1212 disposed at a drive end 1298 of the bot 110 and two idler wheels 1213, 1214 disposed at a driven end 1299 of the bot 110. The wheels 1211-1214 may be mounted to the frame 1200 in any suitable manner and be constructed of any suitable material, such as for example, low-rolling-resistance polyurethane. In alternate embodiments the bot 110 may have any suitable number of drive and idler wheels. In one exemplary embodiment, the wheels 1211-1214 may be substantially fixed relative to a longitudinal axis 1470 (
Each of the drive wheels 1211, 1212 may be individually driven by a respective motor 1211M, 1212M. The drive motors 1211M, 1212M may be any suitable motors such as, for exemplary purposes only, direct current electric motors. The motors 1211M, 1212M may be powered by any suitable power source such as by, for example, a capacitor 1400 (
As noted above drive wheels 1211, 1212 and idler wheels 1213, 1214 are substantially fixed relative to the frame 1200 for guiding the bot 110 along substantially straight paths while the bot is travelling on, for example, the transfer decks 130B, 330A, 330B (e.g.
In other exemplary embodiments, the idler wheels 1213, 1214 may be replaced by non-retractable casters 1260′, 1261′ (
The bot 110 may also be provided with guide wheels 1250-1253. As can be best seen in
While four guide wheels 1250-1253 are shown and described it should be understood that in alternate embodiments the bot 110 may have any suitable number of guide wheels. The guide wheels 1250-1253 may be mounted to, for example, the frame 1200 of the bot in any suitable manner. In one exemplary embodiment, the guide wheels 1250-1253 may be mounted to the frame 1200, through for example, spring and damper devices so as to provide relative movement between the guide wheels 1250-1253 and the frame 1200. The relative movement between the guide wheels 1250-1253 and the frame may be a dampening movement configured to, for example, cushion the bot 110 and its payload against any change in direction or irregularities (e.g. misaligned joints between track segments, etc.) in the track 1300. In alternate embodiments, the guide wheels 1250-1253 may be rigidly mounted to the frame 1200. The fitment between the guide wheels 1250-1253 and the recessed portion 1300R of the track 1300 may be configured to provide stability (e.g. anti-tipping) to the bot during, for example, cornering and/or extension of the transfer arm 1235 (e.g. to counteract any tipping moments created by a cantilevered load on the transfer arm). In alternate embodiments the bot may be stabilized in any suitable manner during cornering and/or extension of the transfer arm 1235. For example, the bot 110 may include a suitable counterweight system for counteracting any moment that is created on the bot through the extension of the transfer arm 1235.
The transfer arm 1235 may be movably mounted to the frame 1200 within, for example, the payload area 1230. It is noted that the payload area 1230 and transfer arm 1235 may be suitably sized for transporting cases in the storage and retrieval system 100. For example, the width W of the payload area 1230 and transfer arm 1235 may be substantially the same as or larger than a depth D (
Referring also to
In one exemplary embodiment, the fingers 1235A of the transfer arm 1235 may be configured such that the fingers 1235A are extendable and retractable individually or in one or more groups. For example, each finger may include a locking mechanism 1410 that selectively engages each finger 1235A to, for example, the frame 1200 of the bot 110 or a movable member of the transfer arm 1235 such as the pusher bar 1235B. The pusher bar 1235B (and any fingers coupled to the pusher bar), for example, may be driven by any suitable drive such as extension motor 1495. The extension motor 1495 may be connected to, for example, the pusher bar, through any suitable transmission such as, for exemplary purposes only, a belt and pulley system 1495B (
In one exemplary embodiment, the locking mechanism for coupling the fingers 1235A to, for example, the pusher bar 1235B may be, for example, a cam shaft driven by motor 1490 that is configured to cause engagement/disengagement of each finger with either the pusher bar or frame. In alternate embodiments, the locking mechanism may include individual devices, such as solenoid latches associated with corresponding ones of the fingers 1235A. It is noted that the pusher bar may include a drive for moving the pusher bar in the direction of arrows 1471, 1472 for effecting, for example, a change in orientation (e.g. alignment) of a load being carried by the bot 110, gripping a load being carried by the bot 110 or for any other suitable purpose. In one exemplary embodiment, when one or more locking mechanisms 1410 are engaged with, for example, the pusher bar 1235B the respective fingers 1235A extend and retract in the direction of arrows 1471, 1472 substantially in unison with movement of the pusher bar 1235B while the fingers 1235A whose locking mechanisms 1410 are engaged with, for example, the frame 1200 remain substantially stationary relative to the frame 1200.
In another exemplary embodiment, the transfer arm 1235 may include a drive bar 1235D or other suitable drive member. The drive bar 1235D may be configured so that it does not directly contact a load carried on the bot 110. The drive bar 1235D may be driven by a suitable drive so that the drive bar 1235D travels in the direction of arrows 1471, 1472 in a manner substantially similar to that described above with respect to the pusher bar 1235B. In this exemplary embodiment, the locking mechanisms 1410 may be configured to latch on to the drive bar 1235D so that the respective fingers 1235A may be extended and retracted independent of the pusher bar and vice versa. In alternate embodiments the pusher bar 1235B may include a locking mechanism substantially similar to locking mechanism 1410 for selectively locking the pusher bar to either the drive bar 1235D or the frame 1200 where the drive bar is configured to cause movement of the pusher bar 1235B when the pusher bar 1235B is engaged with the drive bar 1235D.
In one exemplary embodiment, the pusher bar 1235B may be a one-piece bar that spans across all of the fingers 1235A. In other exemplary embodiments, the pusher bar 1235B may be a segmented bar having any suitable number of segments 1235B1, 1235B2. Each segment 1235B1, 1235B2 may correspond to the groups of one or more fingers 1235A such that only the portion of the pusher bar 1235B corresponding to the finger(s) 1235A that are to be extended/retracted is moved in the direction of arrows 1471, 1472 while the remaining segments of the pusher bar 1235B remain stationary so as to avoid movement of a load located on the stationary fingers 1235A.
The fingers 1235A of the transfer arm 1235 may be spaced apart from each other by a predetermined distance so that the fingers 1235A are configured to pass through or between corresponding support legs 620L1, 620L2 of the storage shelves 600 (
The transfer arm 1235 may include any suitable lifting device(s) 1235L configured to move the transfer arm 1235 in a direction substantially perpendicular to a plane of extension/retraction of the transfer arm 1235.
Referring also to
As noted above the bot 110 may include a retractable fence 1235F. Referring to
Referring again to
Referring now to
In one exemplary embodiment, the control system 1220 may be divided into a front end 1220F (
The front end 1220F may be configured for any suitable communications (e.g. synchronous or asynchronous communications regarding bot commands, status reports, etc.) with the control server 120. The bot front end 1220F may be configured as a pair of state machines where a first one of the state machines handles communication between the front end 1220F and the control server 120 and a second one of the state machines handles communication between the front end 1220F and the back end 1220B. In alternate embodiments the front end 1220F may have any suitable configuration. The back end 1220B may be configured to effect the functions of the bot described above (e.g. lowering the casters, extending the fingers, driving the motors, etc.) based on, for example, the primitives received from the front end 1220F. In one example, the back end 122B may monitor and update bot parameters including, but not limited to, bot position and velocity and send those parameters to the, bot front end 1220F. The front end 122 OF may use the parameters (and/or any other suitable information) to track the bots 110 movements and determine the progress of the bot task(s). The front end 1220F may send updates to, for example, the bot proxy 2680 so that the control server 120 can track the bot movements and task progress and/or any other suitable bot activities.
The motion control subsystem 1705 may be part of the back end 1220B and configured to effect operation of, for example, the drive motors 1211M, 1212M, 1235L, 1495, 1490, 1610 of the bot 110 as described herein. The motion control subsystem 1705 may operatively connected to the computer 1701 for receiving control instructions for the operation of, for example, servo drives (or any other suitable motor controller) resident in the motion control subsystem 1705 and subsequently their respective drive motors 1211M, 1212M, 1235L, 1495, 1490, 1610. The motion control subsystem 1704 may also include suitable feedback devices, such as for example, encoders, for gathering information pertaining to the drive motor operation for monitoring, for example, movement the transfer arm 1235 and its components (e.g. when the fingers 1235A are latched to the pusher bar, a location of the pusher bar, extension of the fence, etc.) or the bot 110 itself. For example, an encoder for the drive motors 1211M, 1212M may provide wheel odometry information, and encoders for lift motor 1235L and extension motor 1495 may provide information pertaining to a height of the transfer arm 1235 and a distance of extension of the fingers 1235A. The motion control subsystem 1705 may be configured to communicate the drive motor information to the computer 1701 for any suitable purpose including but not limited to adjusting a power level provided to a motor.
The input/output subsystem 1702 may also be part of the back end 1220B and configured to provide an interface between the computer 1701 and one or more sensors 1710-1716 of the bot 110. The sensors may be configured to provide the bot with, for example, awareness of its environment and external objects, as well as the monitor and control of internal subsystems. For example, the sensors may provide guidance information, payload information or any other suitable information for use in operation of the bot 110. For exemplary purposes only, the sensors may include a bar code scanner 1710, slat sensors 1711, line sensors 1712, case overhang sensors 1713, arm proximity sensors 1714, laser sensors 1715 and ultrasonic sensors 1716 as described in U.S. patent application Ser. No. 12/757,312, entitled “AUTONOMOUS TRANSPORTS FOR STORAGE AND RETRIEVAL SYSTEMS,” (now U.S. Pat. No. 8,425,173), previously incorporated herein by reference.
It is noted that the computer 1701 and its subsystems 1702, 1705 may be connected to a power bus for obtaining power from, for example, the capacitor 1400 through any suitable power supply controller 1706. It is noted that the computer 1701 may be configured to monitor the voltage of the capacitor 1400 to determine its state of charge (e.g. its energy content). In one exemplary embodiment, the capacitor may be charged through charging stations located at, for example, one or more transfer stations 140 or at any other suitable location of the storage structure 130 so that the bot is recharged when transferring payloads and remains in substantially continuous use. The charging stations may be configured to charge the capacitor 1400 within the time it takes to transfer the payload of the bot 110. For exemplary purposes only, charging of the capacitor 1400 may take about 15 seconds. In alternate embodiments, charging the capacitor may take more or less than about 15 seconds. During charging of the capacitor 1400 the voltage measurement may be used by the computer 1701 to determine when the capacitor is full and to terminate the charging process. The computer 1701 may be configured to monitor a temperature of the capacitor 1400 for detecting fault conditions of the capacitor 1400.
The computer 1701 may also be connected to a safety module 1707 which includes, for example, an emergency stop device 1311 (
The communication ports of the control system 1220 may be configured for any suitable communications devices such as, for example, a wireless radio frequency communication device 1703 (including one or more antennae 1310) and any suitable optical communication device 1704 such as, for example, an infrared communication device. The wireless radio frequency communication device 1703 may be configured to allow communication between the bot 110 and, for example, the control server 120 and/or other different bots 110 over any suitable wireless protocol. For exemplary purposes only, the wireless protocol for communicating with the control server 120 may be the wireless 802.11 network protocol (or any other suitable wireless protocol). Communications within the bot control system 1220 may be through any suitable communication bus such as, for example, a control network area bus. It is noted that the control server 120 and the bot control system 1220 may be configured to anticipate momentary network communication disruptions. For example, the bot may be configured to maintain operation as long as, for example, the bot 110 can communicate with the control server 120 when the bot 110 transits a predetermined track segment and/or other suitable way point. The optical communication device 1704 may be configured to communicate with, for example, the bot transfer stations for allowing initiation and termination of charging the capacitor 1400. The bot 110 may be configured to communicate with other bots 110 in the storage and retrieval system 100 to form a peer-to-peer collision avoidance system so that bots can travel throughout the storage and retrieval system 100 at predetermined distances from each other in a manner substantially similar to that described in U.S. patent application Ser. No. 12/757,337, entitled “CONTROL SYSTEM FOR STORAGE AND RETRIEVAL SYSTEMS,” (now U.S. Pat. No. 8,594,835), previously incorporated by reference herein.
Referring again to
The storage structure 130 may also include charging stations 130C for replenishing, for example, a battery pack of the bots 110. In one exemplary embodiment, the charging stations 130C may be located at, for example, the transfer areas 295 so that the bots 110 can substantially simultaneously transfer case units, 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, in one exemplary embodiment, 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, which in turn manages the warehouse facility as a whole. The control server 120 may be substantially similar to that described in, for example, U.S. patent application Ser. No. 12/757,337, entitled “CONTROL SYSTEM FOR STORAGE AND RETRIEVAL SYSTEMS,” (now U.S. Pat. No. 8,594,835), previously incorporated by reference herein in its entirety. For example, the control server 120 may include a collection of substantially concurrently running programs that are configured to manage the storage and retrieval system 100 including, for exemplary purposes only, controlling, scheduling, and monitoring the activities of all active system components, managing inventory and pickfaces, and interfacing with a warehouse management system 2500. It is noted that a “pickface” as used herein may be one or more merchandise case units placed one behind the other in a storage space or area of a storage shelf to be used in pick transactions for filling customer orders. In one example, all case units forming a given pickface are of the same stock keeping unit (SKU) and originally from the same pallet. In alternate embodiments, each pickface may include any suitable case units. Each pickface may correspond to all or part of a bot load (e.g. the load carried by each bot 110 to and from the storage areas). Conversely, the bot load may be established based on a pickface determination. As may be realized the determination of the pickfaces may be variable within the storage and retrieval system such that the size and locations of the pickface are dynamically changeable. It is also noted that interfacing with the warehouse management system allows the control server 120 to receive and execute pallet orders and to submit and execute replenishment orders as will be described below. The active system components may be the physical entities that act upon the case units to be stored and retrieved. The active system components may include, as a non-limiting example, the bots, in-feed and out-feed stations, multilevel vertical conveyors, the network and user interface terminals. In alternate embodiments, the active system components may also include transfer stations. 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, such as, for example, when case units are damaged, recalled or an expiration date of the case units has expired. In one exemplary embodiment, the control server 120 may be configured to give preference to case units that are closer to their expiration date when fulfilling orders so those case units are removed from the storage and retrieval system before similar case units (e.g. with the same SKU) having later expiration dates. In the exemplary embodiments, the distribution (e.g. sortation) of case units in the storage and retrieval system is such that the case units in the 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) and then removed from the respective multilevel vertical conveyors 150B in a second predetermined sequence (e.g. a second sortation of case units) so that the case units may be placed on pallets or other suitable shipping containers/devices) in a predetermined order. 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 item are to be delivered to the out-feed transfer station 160. Referring to
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.
Referring also to
As may be realized case units of the same type may be stored in different locations within the storage structure 130 so that at least one of that type of item may be retrieved when other ones of that type of item are inaccessible. The storage and retrieval system may also be configured to provide multiple access paths or routes to each storage location (e.g. pickface) so that bots may reach each storage location using, for example, a secondary path if a primary path to the storage location is obstructed. It is noted that the control server 120 and one or more sensors on the bots 110 may allow for the assignment and reservation of a pickface for putting away an inbound item such as during replenishment of the storage and retrieval system 100. In one exemplary embodiment, when a storage slot/space becomes available in the storage structure 130, the control server 120 may assign a fictitious item (e.g. an empty case) to the empty storage slot. If there are adjacent empty slots in the storage structure the empty cases of the adjacent storage slots may be combined to fill the empty space on the storage shelf. As may be realized, the size of the slots may be variable such as when dynamically allocating shelf space. For example, referring also to
When an order for individual case units is made any bots 110 on the storage level of the requested case units retrieves the corresponding case units from a designated storage area of the storage structure 130 (
Referring now to
The storage and retrieval systems, such as those described above with respect to
The control server 120 may be configured to communicate with the bots 110, multilevel vertical conveyors 150A, 150B, in-feed or out-feed transfer stations 160, 170 and other suitable features/components of the storage and retrieval system in any suitable manner. The bots 110, multilevel vertical conveyors 150A, 150B and transfer stations 160, 170 may each have respective controllers that communicate with the control server 120 for conveying and/or receiving, for example, a respective operational status, location (in the case of the bots 110) or any other suitable information. The control server may record the information sent by the bots 110, multilevel vertical conveyors 150A, 150B and transfer stations 160, 170 for use in, for example, planning order fulfillment or replenishment tasks.
As may be realized any suitable controller of the storage and retrieval system such as for example, control server 120, may be configured to create any suitable number of alternate pathways for retrieving one or more case units from their respective storage locations when a pathway providing access to those case units is restricted or blocked. For example, the control server 120 may include suitable programming, memory and other structure for analyzing the information sent by the bots 110, multilevel vertical conveyors 150A, 150B and transfer stations 160, 170 for planning a bot's 110 primary or preferred route to a predetermined item within the storage structure. The preferred route may be the fastest and/or most direct route that the bot 110 can take to retrieve the item. In alternate embodiments the preferred route may be any suitable route. The control server 120 may also be configured to analyze the information sent by the bots 110, multilevel vertical conveyors 150A, 150B and transfer stations 160, 170 for determining if there are any obstructions along the preferred route. If there are obstructions along the preferred route the control server may determine one or more secondary or alternate routes for retrieving the item so that the obstruction is avoided and the item can be retrieved without any substantial delay in, for example, fulfilling an order. It should be realized that the bot route planning may also occur on the bot 110 itself by, for example, any suitable controller system, such as control system 1220 (
Referring to
The storage and retrieval systems shown in
Referring also to
Each of the storage bays 510, 511 may hold the picking stock on storage shelves 600 that are separated by the picking aisles 130A. It is noted that in one exemplary embodiment the vertical supports 612 and/or horizontal supports 610, 611, 613 may be configured to allow for adjusting the height or elevation of the storage shelves and/or aisle floors 130F relative to, for example, each other and a floor of the facility in which the storage and retrieval system is located. In alternate embodiments the storage shelves and floors may be fixed in elevation. As can be seen in
The storage shelves 600 may include one or more support legs 620L1, 620L2 extending from, for example, the horizontal supports 610, 611, 613. The support legs 620L1, 620L2 may have any suitable configuration and may be part of, for example, a substantially U-shaped channel 620 such that the legs are connected to each other through channel portion 620B. The channel portion 620B may provide an attachment point between the channel 620 and one or more horizontal supports 610, 611, 613. In alternate embodiments, each support leg 620L1, 620L2 may be configured to individually mount to the horizontal supports 610, 611, 613. In this exemplary embodiment, each support leg 620L1, 620L2 includes a bent portion 620H1, 620H2 having a suitable surface area configured to support case units stored on the shelves 600. The bent portions 620H1, 620H2 may be configured to substantially prevent deformation of the case units stored on the shelves. In alternate embodiments the leg portions 620H1, 620H2 may have a suitable thickness or have any other suitable shape and/or configuration for supporting case units stored on the shelves. As can be seen in
Referring again to
The travel lanes of the transfer decks 130B may be wider than the travel lanes within the aisles of the storage structure 130. For exemplary purposes only, travel lanes of the transfer decks 130B may be configured to allow the bots 110 to make different types of turns when, for example, transitioning onto or off of the transfer decks 130B. The different types of turns may correspond to a desired orientation of the bot 110 within the picking aisles 130A or a lane of the transfer deck 130B on which the bot 110 is travelling. For exemplary purposes only, referring to
When traveling in the picking aisles 130A, the bot 110 travels in substantially straight lines. These substantially straight line moves within the picking aisles 130A can be in either direction 1860, 1861 and with either bot orientation (e.g. a forward orientation with the drive end 1298 trailing the direction of travel and a reverse orientation with the drive end 1298 leading the direction of travel). During straight line motion on the transfer deck 130B the bot 110 travels in, for exemplary purposes only, a counterclockwise direction 1863, with a forward bot orientation. In alternate embodiments the bot may travel in any suitable direction with any suitable bot orientation. In still other alternate embodiments, there may be multiple travel lanes allowing bots to travel in multiple directions (e.g. one travel lane has a clockwise direction of travel and another travel lane has a counter-clockwise direction of travel). In one example, the turns to and from the picking aisles 130A and/or transfer areas 295 are about 90 degrees where the center point of rotation P of the bot is located substantially midway between the drive wheels 1211, 1212 such that the bot can rotate clockwise or counterclockwise. In alternate embodiments the bot turns may be more or less than about 90 degrees. In another example, the bot may make a substantially 180 degree turn (i.e. two substantially 90 degree turns made in sequence without a stop).
As described above, the transfer deck 130B may include guidance lines 1810-1817 for guiding the bot 110. The guidance lines 1810-1817 may be any suitable lines adhered to, formed in or otherwise affixed to the transfer deck 130B. For exemplary purposes only, in one example the guidance lines may be a tape affixed to the surface of the transfer deck 130B. In this exemplary embodiment the, transfer deck 130B includes a track 1800 having a first side 1800A and a second side 1800B separated by a wall 1801. The first and second sides 1800A, 1800B of the track 1800 are joined by end track sections 1800E (only one of which is shown in
When the bot 110 moves in substantially straight lines, such as in the picking aisles 130A and/or transfer areas 295, the drives for motors 1211M, 1212M may be configured as torque controllers as described in greater detail in U.S. patent application Ser. No. 12/757,312, entitled “AUTONOMOUS TRANSPORTS FOR STORAGE AND RETRIEVAL SYSTEMS,” (now U.S. Pat. No. 8,425,173), previously incorporated by reference in its entirety. When travelling long distances on, for example, the transfer deck, the bot 110 travels on drive wheels 1211, 1212 and idler wheels 1213, 1214 (or locked casters 1260′, 1261′) so that the bot is deterred from veering off of the straight line trajectory through the fixed nature of the drive wheels 1211, 1212 and idler wheels 1213, 1214 (or locked casters 1260′, 1261′). The computer 1701 may be configured with any suitable line following algorithm to substantially ensure that the bot 110 maintains travel in a straight line. The line following algorithm may also allow for correction of initial line following errors due to, for example, misalignment from turns. In one exemplary embodiment the bot 110 uses line sensors 1712 to estimate its heading and offset from a guidance line 1810-1817. The bot 110 may be configured to use, for example, any suitable algorithm such as a fuzzy logic algorithm to generate corrections in the travel path of the bot 110. The correction may be applied as a differential torque to the wheels as the bot is travelling (e.g. skid steering—rotating one drive wheel slower than the other drive wheel to produce increased drag on one side of the bot for inducing a turning moment on the bot).
For turns, such as for example, substantially right angle turns, the drives for motors 1211M, 1212M may be configured as position controllers. For example the drives may be commanded by the computer 1701 to rotate their respective wheels in opposite directions for a predetermined distance to generate a pivot turn of slightly more than about 90 degrees. When for example, line sensors 1712 detect a stopping guidance line, the turning move is terminated. In alternate embodiments the drives for the motors 1211M, 1212M may be operated in any suitable manner for driving the bot in substantially straight lines or during turns.
Referring again to
In one exemplary embodiment, the storage structure 130 may include personnel floors 280 (which may include the maintenance access gateways 410A-410C) associated with each level of the storage structure. The personnel floors may be located, for example, within or adjacent to the aisles of the storage structure and/or the transfer decks 130B. In alternate embodiments, the personnel floors 280 may be suitably located to provided reach in access to one side of the transfer decks 130B from within the storage structure where the other opposite side of the transfer decks 130B is accessed through work platforms/scaffolding adjacent the workstations 210, 220 and/or multilevel vertical conveyors. In one exemplary embodiment, the personnel floors 280 may run the full length of each aisle 130A or transfer deck 130B. In alternate embodiments the personnel floors 280 may have any suitable length. The personnel floors 280 may be vertically spaced from each other at predetermined intervals where the space between the personnel floors 280 provides a personnel work zone for resolving problems with, as non-limiting examples, the bots 110, case units stored in the storage structure 130 and the storage structure 130 itself. The personnel floors 280 may be configured to provide walking surfaces for, as an example, maintenance technicians or other personnel where the walking zones are distinct from travel lanes of the bots 110. Access to the personnel floors may be provided through the maintenance access gateways 410A-410C or any other suitable access point. Movable barriers or other suitable structures may be provided along the aisles 130A and transfer decks 130B to further separate unintentional interaction between, for example the bots 110 and personnel. In one exemplary embodiment, in normal operation the movable barriers may be in a stowed or retracted position to allow, for example, the bot 110 to pass and access the storage shelves 600. The movable barriers may be placed in an extended position when personnel are located in a predetermined zone or location of the storage structure 130 to block bot 110 access to the aisle(s) or portions of the transfer decks where personnel are located. In one exemplary operation of storage structure maintenance for a predetermined zone of the storage structure 130, all active bots 110 may be removed from the predetermined zone. Bots 110 that require maintenance may be disabled and de-energized within the predetermined zone. The movable barriers may be extended to prevent active bots 110 from entering the predetermined zone and any locks preventing access to the personnel floors may be unlocked or removed. The extension and retraction of the movable barriers, disabling of the bots 110 and removal of bots 110 from the predetermined zone may be controlled in any suitable manner such as by, for example, any suitable control system such as a central controller server 120 and mechanical and/or electromechanical interlocks. It is noted that in alternate embodiments, the storage and retrieval system may include any suitable personnel access not limited to that described above.
The structure, such as structure 130, of the storage and retrieval systems described herein may be configured to sustain predetermined loads placed on the structure by normal service and events such as, for exemplary purposes only, earthquakes as defined by local and federal codes. As an example, these loads may include the dead weight of the structure, inventory stored in and transferred throughout the structure, the bots 110, seismic loads, thermal expansion and sufficient stiffness for bot control and positioning. The structure of the storage and retrieval systems 100 may also be configured for ease of assembly, maintenance access, modularity and efficient and economical material use. Non-limiting examples, of the codes to which the structure may be configured to comply include ASCE7, AISC Manual of Steel Construction, AISC Code of Standard Practice for Steel Buildings and Bridges, RMI (Rack Manufacturers Institute) and Materials Handling Industry of America. The structural components (e.g. vertical/horizontal supports, floors, etc.) of the storage and retrieval systems described herein may also include wear and/or corrosion resistant coatings including surface treatments such as, for example, paints and galvanization. In one example, the coating may include a base coating and a contrasting top coating such that any wearing of the top coating will be readily visible. In alternate embodiments the coatings and surface treatments may have any suitable configurations and colors so that wear is easily identifiable.
The storage structure 130 may be configured to be rapidly assembled and installed in the field in a “bottom up construction” (e.g. each level is constructed sequentially such that lower levels in the sequence are substantially completed before the upper levels in the sequence). For example, the vertical supports 612 and/or horizontal supports 610, 611, 613 (and/or any other components of the storage structure 130) may be predrilled, punched or otherwise preformed with assembly holes. Base plates for supporting each of the vertical supports 612 and for securing the vertical supports 612 to a floor may be preinstalled on the respective vertical supports 612. Templates may be provided for locating anchor bolts in the floor for securing the base plates. The vertical supports 612 may be configured with brackets for receiving and at least partially securing the horizontal supports 610, 611, 613. Preformed holes in the horizontal supports may also be used to, for example, bolt or otherwise fasten the horizontal supports to the vertical supports. The shelves 600 may be field assembled from prefinished components and affixed to, for example, the horizontal supports 610, 611, 613 in any suitable manner. Separate braces such as ties may be also provided for securing the horizontal supports 610, 611, 613. The transfer decks 130B may be installed in a manner substantially similar to that described above. The floors and decking of the storage structure 130 may be affixed to the horizontal supports in any suitable manner, such as for example through fasteners. The floors and decking may be preformed with installation holes to allow for securing the floors and decking to the horizontal supports. The tracking 1300 (
It should be understood that the exemplary 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 present embodiments are intended to embrace all such alternatives, modifications and variances that fall within the scope of the appended claims.
This application is a continuation of U.S. patent application Ser. No. 14/816,804, filed on Aug. 3, 2015 (now U.S. Pat. No. 10,239,691 issued on Mar. 26, 2019), which is a continuation of U.S. patent application Ser. No. 12/757,220, filed on Apr. 9, 2010, (now U.S. Pat. No. 9,096,375 issued on Aug. 4, 2015), which is a non-provisional of and claims the benefit of U.S. Provisional Patent Application No. 61/168,349 filed on Apr. 10, 2009, the disclosures of which are incorporated herein by reference in their entireties. This application is related to U.S. patent application Ser. No. 12/757,381, entitled “STORAGE AND RETRIEVAL SYSTEM”, filed on Apr. 9, 2010 (now U.S. Pat. No. 8,740,538); U.S. patent application Ser. No. 12/757,337, entitled “CONTROL SYSTEM FOR STORAGE AND RETRIEVAL SYSTEMS”, filed on Apr. 9, 2010 (now U.S. Pat. No. 8,594,835); U.S. patent application Ser. No. 12,757,354, entitled “LIFT INTERFACE FOR STORAGE AND RETRIEVAL SYSTEMS” filed on Apr. 9, 2010; and U.S. patent application Ser. No. 12/757,312, entitled “AUTONOMOUS TRANSPORTS FOR STORAGE AND RETRIEVAL SYSTEMS”, filed on Apr. 9, 2010 (now U.S. Pat. No. 8,425,173), the disclosures of which are incorporated by reference herein in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
1845962 | Dorr | Feb 1932 | A |
1887667 | Wheeler | Nov 1932 | A |
2606508 | Van Nes | Aug 1952 | A |
2656995 | Wolf | Oct 1953 | A |
2673689 | Bonanno | Mar 1954 | A |
2792234 | Page | May 1957 | A |
2840248 | Grove et al. | Jun 1958 | A |
2877575 | Stedt | Mar 1959 | A |
2923421 | De Senigon De Roumefort | Feb 1960 | A |
2945604 | Kroll et al. | Jul 1960 | A |
2996621 | Barret, Jr. | Aug 1961 | A |
3016154 | Ugolini et al. | Jan 1962 | A |
3110131 | Jeffress | Nov 1963 | A |
3161303 | Burrows | Dec 1964 | A |
3162459 | Marmorine et al. | Dec 1964 | A |
3175940 | Talmey | Mar 1965 | A |
3269744 | Dobson | Aug 1966 | A |
3369648 | Wentz | Feb 1968 | A |
3370492 | Treff | Feb 1968 | A |
3455468 | Sanford | Jul 1969 | A |
3519149 | Saul | Jul 1970 | A |
3554390 | Saul | Jan 1971 | A |
3581915 | Saul | Jun 1971 | A |
3636586 | Bollinger et al. | Jan 1972 | A |
3677421 | Kintner | Jul 1972 | A |
3719408 | Fullington et al. | Mar 1973 | A |
3737056 | Hathcock, Jr. | Jun 1973 | A |
3738506 | Cornford et al. | Jun 1973 | A |
3744945 | Metrailer | Jul 1973 | A |
3746189 | Burch et al. | Jul 1973 | A |
3751758 | Higbee et al. | Aug 1973 | A |
3782565 | Doran et al. | Jan 1974 | A |
3802580 | Castaldi | Apr 1974 | A |
3845715 | Hochstrasser | Nov 1974 | A |
3850111 | Hansen | Nov 1974 | A |
3876087 | Osta | Apr 1975 | A |
3876095 | Stedt | Apr 1975 | A |
3896955 | Collins et al. | Jul 1975 | A |
3904216 | Metrailer | Sep 1975 | A |
3940105 | Metrailer | Feb 1976 | A |
3970840 | De Bruine | Jul 1976 | A |
3976302 | Hammarstrand | Aug 1976 | A |
3984012 | Ennis et al. | Oct 1976 | A |
4007843 | Lubbers et al. | Feb 1977 | A |
4026365 | Andersson et al. | May 1977 | A |
4037291 | Huempfner et al. | Jul 1977 | A |
4057019 | Shaffer | Nov 1977 | A |
4064986 | Bertovich | Dec 1977 | A |
4072203 | Pierson | Feb 1978 | A |
4079955 | Thorpe et al. | Mar 1978 | A |
4087116 | Morimoto | May 1978 | A |
4174854 | Spicka et al. | Nov 1979 | A |
4183304 | Forster | Jan 1980 | A |
4213396 | Mehren et al. | Jul 1980 | A |
4219296 | Fujii et al. | Aug 1980 | A |
4223611 | Dawson et al. | Sep 1980 | A |
4265582 | Theobald | May 1981 | A |
4268207 | Pipes | May 1981 | A |
4271764 | Braun et al. | Jun 1981 | A |
4273234 | Bourgeois | Jun 1981 | A |
4307988 | Page et al. | Dec 1981 | A |
4346659 | Binder | Aug 1982 | A |
4349937 | Fontana | Sep 1982 | A |
4349938 | Fontana | Sep 1982 | A |
4353572 | McCain | Oct 1982 | A |
4372219 | Gibbs | Feb 1983 | A |
4372724 | Stolzer | Feb 1983 | A |
4394104 | Camerini et al. | Jul 1983 | A |
4395181 | Loomer | Jul 1983 | A |
4406570 | Duncan et al. | Sep 1983 | A |
4415975 | Burt | Nov 1983 | A |
4428708 | Burt | Jan 1984 | A |
4445440 | Geiss | May 1984 | A |
4459078 | Chiantella et al. | Jul 1984 | A |
4470742 | Schindler | Sep 1984 | A |
4492504 | Hainsworth | Jan 1985 | A |
4505630 | Kaschner et al. | Mar 1985 | A |
4527486 | Baird et al. | Jul 1985 | A |
4538950 | Shiomi et al. | Sep 1985 | A |
4678390 | Bonneton et al. | Jul 1987 | A |
4679149 | Merz | Jul 1987 | A |
4715662 | van Zanten et al. | Dec 1987 | A |
4716530 | Ogawa et al. | Dec 1987 | A |
4726725 | Baker et al. | Feb 1988 | A |
4733740 | Bigowsky et al. | Mar 1988 | A |
4750429 | Mordaunt et al. | Jun 1988 | A |
4773807 | Kroll et al. | Sep 1988 | A |
4777416 | George, II et al. | Oct 1988 | A |
4786229 | Henderson | Nov 1988 | A |
4811229 | Wilson | Mar 1989 | A |
4812985 | Hambrick et al. | Mar 1989 | A |
4856263 | Schneider et al. | Aug 1989 | A |
4856956 | Zur | Aug 1989 | A |
4878876 | Ishimoto | Nov 1989 | A |
4883401 | Kavieff | Nov 1989 | A |
4887016 | Malick | Dec 1989 | A |
4905783 | Bober | Mar 1990 | A |
4909697 | Bernard, II et al. | Mar 1990 | A |
4936738 | Brennen | Jun 1990 | A |
4966242 | Baillargeon | Oct 1990 | A |
4966513 | Motoda | Oct 1990 | A |
4967370 | Stern et al. | Oct 1990 | A |
4987992 | Pfleger | Jan 1991 | A |
4993905 | Potocnjak | Feb 1991 | A |
5002449 | Kita | Mar 1991 | A |
5004399 | Sullivan et al. | Apr 1991 | A |
5015145 | Angell et al. | May 1991 | A |
5069592 | Galperin | Dec 1991 | A |
5096355 | Schroder | Mar 1992 | A |
5134353 | Kita et al. | Jul 1992 | A |
5134940 | Fujita et al. | Aug 1992 | A |
5135344 | Kita et al. | Aug 1992 | A |
5140787 | Corcoran | Aug 1992 | A |
5149654 | Gross et al. | Sep 1992 | A |
5156639 | Bostrom | Oct 1992 | A |
5168815 | Comer et al. | Dec 1992 | A |
5174454 | Parkander | Dec 1992 | A |
5179329 | Nishikawa et al. | Jan 1993 | A |
5187664 | Yardley et al. | Feb 1993 | A |
5199840 | Castaldi et al. | Apr 1993 | A |
5213463 | Rothlisberger et al. | May 1993 | A |
5218909 | Ng | Jun 1993 | A |
5219264 | McClure et al. | Jun 1993 | A |
5220263 | Onishi et al. | Jun 1993 | A |
5226782 | Rigling | Jul 1993 | A |
5238100 | Rose et al. | Aug 1993 | A |
5265944 | Gloceri | Nov 1993 | A |
5271703 | Lindqvist et al. | Dec 1993 | A |
5273392 | Bernard, II et al. | Dec 1993 | A |
5281901 | Yardley et al. | Jan 1994 | A |
5286157 | Vainio et al. | Feb 1994 | A |
5307888 | Urvoy | May 1994 | A |
5323098 | Hamaguchi et al. | Jun 1994 | A |
5327354 | Tsujimoto | Jul 1994 | A |
5328316 | Hoffmann | Jul 1994 | A |
5333982 | Tanizawa et al. | Aug 1994 | A |
5333983 | Hatouchi et al. | Aug 1994 | A |
5337880 | Claycomb et al. | Aug 1994 | A |
5350270 | Stallard et al. | Sep 1994 | A |
5362197 | Rigling | Nov 1994 | A |
5370492 | Gleyze et al. | Dec 1994 | A |
5377851 | Asano et al. | Jan 1995 | A |
5379229 | Parson et al. | Jan 1995 | A |
5380139 | Pohjonen et al. | Jan 1995 | A |
5388955 | Schroder | Feb 1995 | A |
5395206 | Cerny, Jr. | Mar 1995 | A |
5397212 | Watanabe et al. | Mar 1995 | A |
5403147 | Tanaka | Apr 1995 | A |
5405232 | Lloyd et al. | Apr 1995 | A |
5418732 | McFadin | May 1995 | A |
5421685 | Elmer et al. | Jun 1995 | A |
5421697 | Ostwald | Jun 1995 | A |
5425612 | Ebstein | Jun 1995 | A |
5434490 | Ishida et al. | Jul 1995 | A |
5445485 | Poulet | Aug 1995 | A |
5450797 | Becker et al. | Sep 1995 | A |
5460476 | Gazza | Oct 1995 | A |
5472309 | Bernard, II | Dec 1995 | A |
5501295 | Muller et al. | Mar 1996 | A |
5509538 | Spindler et al. | Apr 1996 | A |
5525884 | Sugiura et al. | Jun 1996 | A |
5529165 | Shupert | Jun 1996 | A |
5559696 | Borenstein | Sep 1996 | A |
5564880 | Lederer | Oct 1996 | A |
5582497 | Noguchi | Dec 1996 | A |
5588796 | Ricco et al. | Dec 1996 | A |
5601395 | Lichti, Sr. et al. | Feb 1997 | A |
5611422 | Harkonen | Mar 1997 | A |
5615992 | Proske et al. | Apr 1997 | A |
5626362 | Mottola | May 1997 | A |
5632350 | Gauvin | May 1997 | A |
5650703 | Yardley et al. | Jul 1997 | A |
5664688 | Kitanaka et al. | Sep 1997 | A |
5664929 | Esaki et al. | Sep 1997 | A |
5667230 | Riley et al. | Sep 1997 | A |
5668724 | Ehret et al. | Sep 1997 | A |
5707199 | Faller | Jan 1998 | A |
5709291 | Nishino et al. | Jan 1998 | A |
5718322 | Mulhern | Feb 1998 | A |
5718551 | Ebstein | Feb 1998 | A |
5725063 | Ceragioli et al. | Mar 1998 | A |
5743562 | Mottola | Apr 1998 | A |
5764014 | Jakeway et al. | Jun 1998 | A |
5798920 | Crucius et al. | Aug 1998 | A |
5801506 | Netzler | Sep 1998 | A |
5806870 | Hull et al. | Sep 1998 | A |
5810540 | Castaldi | Sep 1998 | A |
5829096 | Perry | Nov 1998 | A |
5833431 | Rosse, II et al. | Nov 1998 | A |
5839872 | Goto et al. | Nov 1998 | A |
5847537 | Parmley, Sr. | Dec 1998 | A |
5857413 | Ward | Jan 1999 | A |
5866469 | Hays | Feb 1999 | A |
5918951 | Rudd, III | Jul 1999 | A |
5927926 | Yagi | Jul 1999 | A |
5928058 | Francis et al. | Jul 1999 | A |
5938710 | Lanza et al. | Aug 1999 | A |
5974348 | Rocks | Oct 1999 | A |
5988306 | Ooishi | Nov 1999 | A |
6000502 | Leasor et al. | Dec 1999 | A |
6021367 | Pilutti et al. | Feb 2000 | A |
6024381 | Mottola | Feb 2000 | A |
6036427 | Kita et al. | Mar 2000 | A |
6038501 | Kawakami | Mar 2000 | A |
6061607 | Bradley et al. | May 2000 | A |
6062942 | Ogihara | May 2000 | A |
6116842 | Harris et al. | Sep 2000 | A |
6149366 | Deandrea | Nov 2000 | A |
6158566 | Pollock | Dec 2000 | A |
6213704 | White et al. | Apr 2001 | B1 |
6220676 | Rudd, III | Apr 2001 | B1 |
6272406 | Alofs et al. | Aug 2001 | B2 |
6289260 | Bradley et al. | Sep 2001 | B1 |
6295922 | Salamone et al. | Oct 2001 | B1 |
6324994 | Glenn | Dec 2001 | B1 |
6325586 | Loy | Dec 2001 | B1 |
6341269 | Dulaney et al. | Jan 2002 | B1 |
6345217 | Zetler et al. | Feb 2002 | B1 |
6352035 | Kashiwase et al. | Mar 2002 | B1 |
6354430 | Oe | Mar 2002 | B1 |
6360673 | Herrin et al. | Mar 2002 | B1 |
6377867 | Bradley et al. | Apr 2002 | B1 |
6389981 | Strothmann et al. | May 2002 | B1 |
6390756 | Isaacs et al. | May 2002 | B1 |
6391226 | Chauvette et al. | May 2002 | B1 |
6394260 | Barth et al. | May 2002 | B1 |
6397990 | Brien et al. | Jun 2002 | B1 |
6425723 | Okada et al. | Jul 2002 | B1 |
6439131 | Higgins | Aug 2002 | B1 |
6439955 | Feketo | Aug 2002 | B1 |
6463360 | Terada et al. | Oct 2002 | B1 |
6496755 | Wallach et al. | Dec 2002 | B2 |
6503043 | Smith et al. | Jan 2003 | B1 |
6508102 | Margolis et al. | Jan 2003 | B1 |
6563128 | Lublin et al. | May 2003 | B2 |
6597143 | Song et al. | Jul 2003 | B2 |
6600418 | Francis et al. | Jul 2003 | B2 |
6601435 | Hong | Aug 2003 | B2 |
6629502 | Matsukawa | Oct 2003 | B2 |
6631321 | Ciprian | Oct 2003 | B1 |
6645355 | Hanson et al. | Nov 2003 | B2 |
6652213 | Mitchell | Nov 2003 | B1 |
6655297 | Kawato et al. | Dec 2003 | B2 |
6663334 | Warhurst et al. | Dec 2003 | B2 |
6692211 | Yuyama et al. | Feb 2004 | B2 |
6695328 | Cope | Feb 2004 | B2 |
6721638 | Zeitler | Apr 2004 | B2 |
6748292 | Mountz | Jun 2004 | B2 |
6763767 | Jackson et al. | Jul 2004 | B2 |
6764373 | Osawa et al. | Jul 2004 | B1 |
6808058 | Shiohara | Oct 2004 | B2 |
6836701 | McKee | Dec 2004 | B2 |
6851921 | Haag | Feb 2005 | B2 |
6859682 | Naka et al. | Feb 2005 | B2 |
6861154 | Olson et al. | Mar 2005 | B2 |
6864489 | Chen et al. | Mar 2005 | B2 |
6880202 | Thompson et al. | Apr 2005 | B2 |
6928336 | Peshkin et al. | Aug 2005 | B2 |
6929440 | Grond | Aug 2005 | B1 |
6948899 | Lee | Sep 2005 | B2 |
6950722 | Mountz | Sep 2005 | B2 |
6988451 | Marcotte et al. | Jan 2006 | B2 |
6997665 | Bouche et al. | Feb 2006 | B2 |
7002698 | Hanson et al. | Feb 2006 | B2 |
7002772 | Yardy | Feb 2006 | B2 |
7003375 | Inui | Feb 2006 | B2 |
7008164 | Rokkaku | Mar 2006 | B2 |
7011487 | Kafka et al. | Mar 2006 | B2 |
7017228 | Silverstein et al. | Mar 2006 | B2 |
7039501 | Freeman et al. | May 2006 | B2 |
7054716 | McKee et al. | May 2006 | B2 |
7058866 | Flanagan et al. | Jun 2006 | B2 |
7066291 | Martins et al. | Jun 2006 | B2 |
7069124 | Whittaker et al. | Jun 2006 | B1 |
7074151 | Thompson | Jul 2006 | B2 |
7085097 | Starr et al. | Aug 2006 | B2 |
7100294 | Goldsobel et al. | Sep 2006 | B1 |
7101139 | Benedict | Sep 2006 | B1 |
7102848 | Kumpon et al. | Sep 2006 | B2 |
7110855 | Leishman | Sep 2006 | B2 |
7119982 | Starr et al. | Oct 2006 | B2 |
7128196 | Oldford et al. | Oct 2006 | B2 |
7128521 | Hansl | Oct 2006 | B2 |
7133746 | Abramson et al. | Nov 2006 | B2 |
7135992 | Karlsson et al. | Nov 2006 | B2 |
7137593 | Baatz | Nov 2006 | B2 |
7145478 | Goncalves et al. | Dec 2006 | B2 |
7145747 | Brace et al. | Dec 2006 | B2 |
7155308 | Jones | Dec 2006 | B2 |
7184855 | Stingel et al. | Feb 2007 | B2 |
7192034 | Radke et al. | Mar 2007 | B2 |
7221998 | Brust et al. | May 2007 | B2 |
7266422 | DeMotte et al. | Sep 2007 | B1 |
7284652 | Zeitler et al. | Oct 2007 | B2 |
7319320 | Kawashima et al. | Jan 2008 | B2 |
7329081 | Baker et al. | Feb 2008 | B2 |
7332890 | Cohen et al. | Feb 2008 | B2 |
7376487 | Kumhyr | May 2008 | B2 |
7381022 | King | Jun 2008 | B1 |
7386379 | Naik et al. | Jun 2008 | B2 |
7397213 | Im et al. | Jul 2008 | B2 |
7402018 | Mountz et al. | Jul 2008 | B2 |
7426970 | Olsen | Sep 2008 | B2 |
7421268 | Steiner et al. | Oct 2008 | B2 |
7433759 | Nangoy | Oct 2008 | B2 |
7456596 | Goodall et al. | Nov 2008 | B2 |
7460462 | Mejia et al. | Dec 2008 | B2 |
7495561 | Bodin et al. | Feb 2009 | B2 |
7499155 | Cappelletti | Mar 2009 | B2 |
7506404 | Block et al. | Mar 2009 | B2 |
7520376 | Bar | Apr 2009 | B2 |
7532947 | Waddington et al. | May 2009 | B2 |
7536283 | Potter et al. | May 2009 | B2 |
7539557 | Yamauchi | May 2009 | B2 |
7568572 | Zeitler et al. | Aug 2009 | B2 |
7575406 | Hofmeister et al. | Aug 2009 | B2 |
7584812 | Radke et al. | Sep 2009 | B2 |
7587260 | Bruemmer et al. | Sep 2009 | B2 |
7591630 | Lert, Jr. | Sep 2009 | B2 |
7615957 | Kim et al. | Nov 2009 | B2 |
7620477 | Bruemmer | Nov 2009 | B2 |
7636982 | Jones et al. | Dec 2009 | B2 |
7641014 | Hu | Jan 2010 | B2 |
7648002 | Easton et al. | Jan 2010 | B2 |
7653457 | Bloom | Jan 2010 | B2 |
7661920 | Kantola et al. | Feb 2010 | B2 |
7668621 | Bruemmer | Feb 2010 | B2 |
7671293 | Fry et al. | Mar 2010 | B2 |
7682122 | Maynard et al. | Mar 2010 | B2 |
7686560 | Laurin et al. | Mar 2010 | B2 |
7689318 | Draper | Mar 2010 | B2 |
7693757 | Zimmerman | Apr 2010 | B2 |
7695235 | Rallis | Apr 2010 | B1 |
7706917 | Chiappetta et al. | Apr 2010 | B1 |
7725253 | Foxlin | May 2010 | B2 |
7729801 | Abramson | Jun 2010 | B2 |
7730781 | Zhang et al. | Jun 2010 | B2 |
7751928 | Antony et al. | Jul 2010 | B1 |
7769513 | Breed et al. | Aug 2010 | B2 |
7771152 | Waltersbacher | Aug 2010 | B2 |
7783383 | Eliuk et al. | Aug 2010 | B2 |
7792350 | Kiley et al. | Sep 2010 | B2 |
7793742 | Donaldson et al. | Sep 2010 | B2 |
7801644 | Bruemmer et al. | Sep 2010 | B2 |
7826919 | D'Andrea et al. | Nov 2010 | B2 |
7826920 | Stevens et al. | Nov 2010 | B2 |
7826926 | Myeong et al. | Nov 2010 | B2 |
7856290 | Kumhyr | Dec 2010 | B2 |
7861844 | Hayduchok et al. | Jan 2011 | B2 |
7866671 | Madler | Jan 2011 | B2 |
7873469 | D'Andrea et al. | Jan 2011 | B2 |
7885750 | Lu | Feb 2011 | B2 |
7894940 | Kumhyr | Feb 2011 | B2 |
7909562 | Mead | Mar 2011 | B2 |
7926145 | Liao | Apr 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 |
7960973 | Zeller et al. | Jun 2011 | B2 |
7963384 | Lafontaine | Jun 2011 | B2 |
7965871 | Ihara et al. | Jun 2011 | B2 |
7967354 | Faulkner et al. | Jun 2011 | B2 |
7972102 | Ward et al. | Jul 2011 | B2 |
7974738 | Bruemmer et al. | Jul 2011 | B2 |
7988398 | Hofmeister et al. | Aug 2011 | B2 |
7991505 | Lert et al. | Aug 2011 | B2 |
8000835 | Friz et al. | Aug 2011 | B2 |
8001837 | Larson et al. | Aug 2011 | B2 |
8006824 | Wada et al. | Aug 2011 | B2 |
8007221 | More et al. | Aug 2011 | B1 |
8024064 | Sanghavi et al. | Sep 2011 | B1 |
8024066 | Reverte et al. | Sep 2011 | B2 |
8028822 | Braunstein | Oct 2011 | B2 |
8031086 | Thacher et al. | Oct 2011 | B2 |
8041456 | Blackwell et al. | Oct 2011 | B1 |
8042627 | Yang et al. | Oct 2011 | B2 |
8046103 | Abramson et al. | Oct 2011 | B2 |
8046160 | Carter et al. | Oct 2011 | B2 |
8047756 | Tuffs et al. | Nov 2011 | B2 |
8060257 | Close et al. | Nov 2011 | B2 |
8136650 | Frich et al. | Mar 2012 | B2 |
8280548 | Zuber et al. | Oct 2012 | B2 |
8364309 | Bailey | Jan 2013 | B1 |
8378825 | Dahms et al. | Feb 2013 | B2 |
8425173 | Lert et al. | Apr 2013 | B2 |
8480347 | Schafer | Jul 2013 | B2 |
8515575 | Pfeiffer | Aug 2013 | B2 |
8594835 | Lert et al. | Nov 2013 | B2 |
9020639 | Bewley et al. | Apr 2015 | B2 |
9037286 | Lert | May 2015 | B2 |
20020037208 | Patrito | Mar 2002 | A1 |
20020076307 | Fallin et al. | Jun 2002 | A1 |
20020124389 | Matson | Sep 2002 | A1 |
20030033217 | Cutlip | Feb 2003 | A1 |
20030074125 | Walenty et al. | Apr 2003 | A1 |
20030200129 | Klaubauf et al. | Oct 2003 | A1 |
20040065523 | Lichti et al. | Apr 2004 | A1 |
20040088081 | Song et al. | May 2004 | A1 |
20040093116 | Mountz | May 2004 | A1 |
20040136821 | Berger et al. | Jul 2004 | A1 |
20040167667 | Goncalves et al. | Aug 2004 | A1 |
20040238326 | Lichti | Dec 2004 | A1 |
20050029029 | Thorne | Feb 2005 | A1 |
20050166787 | Astrom | Aug 2005 | A1 |
20050212478 | Takenaka | Sep 2005 | A1 |
20050217532 | Conneally | Oct 2005 | A1 |
20060018996 | Pollock et al. | Jan 2006 | A1 |
20060058921 | Okamoto | Mar 2006 | A1 |
20060104712 | Bufano et al. | May 2006 | A1 |
20060216137 | Sakata et al. | Sep 2006 | A1 |
20060245862 | Hansl et al. | Nov 2006 | A1 |
20060257236 | Stingel, III et al. | Nov 2006 | A1 |
20070021864 | Mountz et al. | Jan 2007 | A1 |
20070059132 | Akamatsu et al. | Mar 2007 | A1 |
20070061041 | Zweig | Mar 2007 | A1 |
20070065258 | Benedict | Mar 2007 | A1 |
20070065259 | Talley | Mar 2007 | A1 |
20070071585 | Henkel | Mar 2007 | A1 |
20070114975 | Cohen et al. | May 2007 | A1 |
20070134077 | Laurin et al. | Jun 2007 | A1 |
20070177011 | Lewin et al. | Aug 2007 | A1 |
20070267998 | Cohen et al. | Nov 2007 | A1 |
20070276535 | Haag | Nov 2007 | A1 |
20070290040 | Wurman et al. | Dec 2007 | A1 |
20070293978 | Wurman et al. | Dec 2007 | A1 |
20080001372 | Hoffman et al. | Jan 2008 | A1 |
20080025833 | Baker et al. | Jan 2008 | A1 |
20080044262 | Kim et al. | Feb 2008 | A1 |
20080065265 | Ozick et al. | Mar 2008 | A1 |
20080075357 | Yoon et al. | Mar 2008 | A1 |
20080080963 | Bufano et al. | Apr 2008 | A1 |
20080129445 | Kraimer et al. | Jun 2008 | A1 |
20080154429 | Lee et al. | Jun 2008 | A1 |
20080161987 | Breed | Jul 2008 | A1 |
20080166217 | Fontana | Jul 2008 | A1 |
20080174268 | Koo et al. | Jul 2008 | A1 |
20080215180 | Kota | Sep 2008 | A1 |
20080269960 | Kostmann | Oct 2008 | A1 |
20080275609 | Boydell | Nov 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 |
20090099879 | Ouimet | Apr 2009 | A1 |
20090114115 | Minges | May 2009 | A1 |
20090148259 | Shani | Jun 2009 | A1 |
20090185884 | Wurman et al. | Jul 2009 | A1 |
20090188774 | Tsujimoto | Jul 2009 | A1 |
20090224750 | Hosek et al. | Sep 2009 | A1 |
20090255213 | Schwartau | Oct 2009 | A1 |
20090265031 | Tachibana et al. | Oct 2009 | A1 |
20090284245 | Kirby et al. | Nov 2009 | A1 |
20090308000 | Corcoran | Dec 2009 | A1 |
20090315501 | Li et al. | Dec 2009 | A1 |
20100044124 | Radke et al. | Feb 2010 | A1 |
20100044977 | Hughes et al. | Feb 2010 | A1 |
20100086358 | Shani | Apr 2010 | A1 |
20100086385 | Shani | Apr 2010 | A1 |
20100102532 | Timoney et al. | Apr 2010 | A1 |
20100118149 | Levin et al. | May 2010 | A1 |
20100121481 | Talley et al. | May 2010 | A1 |
20100131182 | Deegan et al. | May 2010 | A1 |
20100135759 | Dillon | Jun 2010 | A1 |
20100145507 | Blust et al. | Jun 2010 | A1 |
20100158648 | Schafer | Jun 2010 | A1 |
20100183409 | Checketts et al. | Jul 2010 | A1 |
20100185353 | Barwick et al. | Jul 2010 | A1 |
20100188210 | Howard et al. | Jul 2010 | A1 |
20100234995 | Zini et al. | Sep 2010 | A1 |
20100272546 | Wolkerstorfer | Oct 2010 | A1 |
20100277005 | Karalis et al. | Nov 2010 | A1 |
20100277121 | Hall et al. | Nov 2010 | A1 |
20100286905 | Goncalves et al. | Nov 2010 | A1 |
20100295943 | Cha et al. | Nov 2010 | A1 |
20100305854 | Kammel et al. | Dec 2010 | A1 |
20100308939 | Kurs | Dec 2010 | A1 |
20100324815 | Hiruta et al. | Dec 2010 | A1 |
20110008138 | Yamashita | Jan 2011 | 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 |
20110090064 | Dahms et al. | Apr 2011 | A1 |
20110106295 | Miranda et al. | May 2011 | A1 |
20110106339 | Phillips et al. | May 2011 | A1 |
20110118903 | Kraimer et al. | May 2011 | A1 |
20110125323 | Gutmann et al. | May 2011 | A1 |
20110130974 | Yngve et al. | Jun 2011 | A1 |
20110148364 | Ota | Jun 2011 | A1 |
20110176895 | Kortelainen | Jul 2011 | A1 |
20110182703 | Alan | Jul 2011 | A1 |
20110185975 | van den Berg et al. | Aug 2011 | A1 |
20110202175 | Romanov et al. | Aug 2011 | A1 |
20110216185 | Laws et al. | Sep 2011 | A1 |
20110231016 | Goulding | Sep 2011 | A1 |
20110254503 | Widmer et al. | Oct 2011 | A1 |
20110271469 | Ziegler et al. | Nov 2011 | A1 |
20110285349 | Widmer et al. | Nov 2011 | A1 |
20120189409 | Toebes et al. | Jul 2012 | A1 |
20120277940 | Kumar et al. | Nov 2012 | A1 |
20120299260 | Goertzen et al. | Nov 2012 | A1 |
20130094926 | Olszak et al. | Apr 2013 | A1 |
20150081089 | Kapust et al. | Mar 2015 | A1 |
Number | Date | Country |
---|---|---|
2019669 | Nov 1971 | DE |
2150500 | Apr 1973 | DE |
4104527 | Aug 1992 | DE |
20011661 | Dec 2000 | DE |
10142395 | Nov 2002 | DE |
102011012950 | Sep 2012 | DE |
0282592 | Sep 1988 | EP |
0466004 | Jul 1991 | EP |
0737630 | Oct 1996 | EP |
0847943 | Jun 1998 | EP |
1193195 | Apr 2002 | EP |
1598291 | Feb 2006 | EP |
1627830 | Feb 2006 | EP |
1775240 | Apr 2007 | EP |
2039580 | Mar 2009 | EP |
2730715 | Aug 1996 | FR |
60183405 | Sep 1985 | JP |
01275310 | Jun 1989 | JP |
01303211 | Dec 1989 | JP |
06056223 | Dec 1989 | JP |
02111206 | Apr 1990 | JP |
02008106 | Nov 1990 | JP |
0468014 | Mar 1992 | JP |
06316309 | Nov 1994 | JP |
08113321 | May 1996 | JP |
11011652 | Jan 1999 | JP |
2000085921 | Mar 2000 | JP |
2001171831 | Jun 2001 | JP |
2001225920 | Aug 2001 | JP |
2001344020 | Dec 2001 | JP |
2002356207 | Dec 2002 | JP |
2003012117 | Jan 2003 | JP |
2003012119 | Jan 2003 | JP |
2004131258 | Apr 2004 | JP |
3102245 | Jul 2004 | JP |
2005138956 | Jun 2005 | JP |
2005145578 | Jun 2005 | JP |
2005277049 | Oct 2005 | JP |
2008510673 | Apr 2008 | JP |
4735387 | Jul 2011 | JP |
0187648 | Nov 2001 | WO |
2005009324 | Feb 2005 | WO |
2005056943 | Jun 2005 | WO |
2005071597 | Aug 2005 | WO |
2006095047 | Sep 2006 | WO |
2008125294 | Oct 2008 | WO |
2008152245 | Dec 2008 | WO |
2009106988 | Sep 2009 | WO |
2010080539 | Jul 2010 | WO |
2010118412 | Oct 2010 | WO |
Number | Date | Country | |
---|---|---|---|
20190218034 A1 | Jul 2019 | US |
Number | Date | Country | |
---|---|---|---|
61168349 | Apr 2009 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14816804 | Aug 2015 | US |
Child | 16364711 | US | |
Parent | 12757220 | Apr 2010 | US |
Child | 14816804 | US |