Patent Grant
11702287
This application relates to inventory management systems (e.g., order distribution or fulfillment systems). For example, this application relates to automated guided vehicles used in inventory management systems.
Some current inventory management systems use drag-along carts on which human agents (pickers) place items they select (pick) to fulfill orders. In a zoneless pick-to-cart system, an agent drags his/her cart from location to location as instructed by the computer system of the facility. The cart can accommodate multiple orders and typically is equipped with dedicated cartons that are keyed to the orders being fulfilled by the agent during that cart load. In some cases, the agent wears a headset and/or is provided a terminal, such as a mobile computing device, via which the agent is provided ordered, item-by-item instructions on which items to pick. As the agent walks around the facility among the different fixed shelving units, he/she drags or pushes his/her cart manually. During a given shift, the agent may end up considerably fatigued from having to propel the cart around the warehouse.
Further, some current inventory management systems divide inventory into a series of zones and assign a human agent to a zone. The systems may use a conveyor belt to move orders across the zones as controlled by the computer system of the facility. In some cases, the agent wears a headset and/or is provided a terminal, such as a mobile computing device, via which the agent is provided ordered, item-by-item instructions on which items to pick. In some cases, pick-to-light systems use light displays to direct operators to product locations. Each product location may have a numeric or alphanumeric display with a light, an acknowledgement button, and a digital readout for indicating quantity.
Further, some current inventory management or distribution systems use a “goods-to-person” approach where the items to be picked by a human agent are brought to a predetermined location to eliminate the amount of walking the human agent must do within a facility and/or expedite the picking of the items by the picker. Once picked, these items are packaged and dispatched.
While these systems may, in certain use cases, adequately maneuver the items to the stations at which they are to be picked, they are less effective for high-volume and/or high-velocity goods because they have to continually return the same goods to the picking stations during the course of a day.
Some current inventory management or distribution systems use a “goods-to-person” approach using robots to retrieve items to be picked from storage. For example, in these systems, robots may retrieve entire shelving units from storage and bring them to agents, who pick items from the shelving units. However, these robots bring many more items in the shelving units to the agents than are actually picked by the agents. Further, each robot can only retrieve items in a single shelving unit at a time because they bring entire shelving units to the agents.
Some current inventory management or distribution systems use forklifts to move pallets of items, however these systems are often not practical when fulfilling small orders, because small orders may include, for instance, only a few items while a pallet may include tens or hundreds of items. Further, traditional forklifts are not able to navigate through narrow aisles to retrieve items on shelves in those aisles, because traditional forklifts require substantial space to turn to face a shelving unit to retrieve a pallet.
An automated guided vehicle (AGV) system can be configured to perform particular operations or actions by virtue of having software, firmware, hardware, or a combination of them installed on the system that in operation causes or cause the system to perform the actions. One general aspect of the AGV includes a drive unit that provides motive force to propel the AGV within an operating environment; a container handling mechanism (CHM) including an extender and a carrying surface, the CHM having three or more degrees of freedom to move the carrying surface along three or more axes, the CHM retrieving an item from a first target shelving unit using the carrying surface and the three or more degrees of freedom and placing the item on a second target shelving unit; and a power source coupled to provide power to the drive unit and the CHM.
Implementations of the AGV may include one or more of the following features. The AGV further including: an item storage rack positioned proximate the CHM, the item storage rack including a plurality of shelves, at least one shelf of the plurality of shelves capable of storing the item during transit of the AGV, the CHM being capable of moving the item between the first target shelving unit, one or more of the shelves from the plurality of shelves of the item storage rack, and the second target shelving unit. The AGV further including: an item storage rack including a plurality of shelves that are vertically arranged on the item storage rack, a first shelf of the plurality of shelves having an adjustable height on the item storage rack, and one or more controllers that determine a current height of the first shelf of the plurality of shelves, and instruct the CHM to place the item on the first shelf of the plurality of shelves at the current height. The AGV where the extender of the CHM includes: a mast; and an extendible arm connecting the carrying surface to the mast, the mast moving the carrying surface vertically, via the extendible arm. The AGV where the item includes a modular container or modular storage unit having a coupling portion, and the carrying surface is compatibly engageable with the coupling portion of the modular carton to lift the modular container from the first target shelving unit, retain the modular container during handling, and place the modular container on the second target shelving unit. The AGV further including: one or more controllers communicatively coupled to the CHM and the drive unit, the one or more controllers signaling the CHM to retrieve the item from the first target shelving unit, signaling the drive unit to propel the AGV from a first location to a second location in the operating environment, the first target shelving unit being located at the first location and the second target shelving unit being located at the second location, and signaling the CHM to place the item on the second target shelving unit. The AGV where the one or more controllers determine a current location of the item within the operating environment, the current location indicating a current placement of the first target shelving unit within the operating environment, and instruct the drive unit to position the CHM adjacent to the first target shelving unit using the current location. The AGV where: the AGV has a front, a rear opposing the front, a left side extending from the front to the rear, and a right side opposing the left side and extending from the front to the rear, the second target shelving unit includes an item storage rack mounted to the AGV, and while the AGV is positioned such that the left side or right side faces a face of the first target shelving unit, one or more controllers instruct the CHM to engage, by the extender, the carrying surface with the item on a first target shelf of the first target shelving unit, lift the item off the first target shelf by the carrying surface and the extender, move the item, by the carrying surface and the extender, from the first target shelf to a second target shelf of the item storage rack, set the item on the second target shelf by the carrying surface and the extender, and disengage, by the extender, the carrying surface from the item. The AGV further including: a guidance system that determines a location of the AGV within the operating environment, the guidance system including one or more sensors that detect and process navigation markers to locate the AGV as the AGV traverses the operating environment. The AGV further including: an optical scanner coupled to the CHM that scans a shelf marker on one or more of the first target shelving unit and the second target shelving unit, the shelf marker indicating a position of the one or more of the first target shelving unit and the second target shelving unit.
Another general aspect includes a method including: navigating an AGV in an operating environment to a location proximate a storage shelving unit having a storage shelf supporting an item; extending a carrying surface of a CHM of the AGV along a second axis relative to a forward direction of travel of the AGV, the CHM having three degrees of freedom corresponding to three axes of movement relative to a housing of the AGV, a first axis of the three axes extending along the forward direction of travel, the second axis of the three axes extending along a horizontal direction perpendicular to the first axis, and a third axis of the three axes extending along a vertical direction perpendicular to both the first axis and the second axis; lifting the carrying surface to lift the item along at least the third axis from the storage shelf, the carrying surface supporting the item; retracting the carrying surface along at least the second axis from the storage shelf; raising the carrying surface along at least the third axis to situate the item proximate to an AGV shelf included on the AGV; moving the carrying surface along at least the first axis until the item is positioned above the AGV shelf; and lowering the carrying surface along at least the third axis to place the item on the AGV shelf.
Implementations of the method may include one or more of the following features. The method further including: determining, by a guidance system, a location of the AGV within the operating environment, the guidance system including one or more sensors that detect and process navigation markers to locate the AGV as the AGV traverses the operating environment; and navigating, using the guidance system, the AGV from the location to a different location in the operating environment using the guidance system. The method further including: determining a location of the storage shelf by scanning a shelf marker on the storage shelf by an optical scanner coupled to the CHM. The method where the AGV includes a storage rack including a plurality of AGV shelves, the plurality of AGV shelves including the AGV shelf. The method further including: extending the carrying surface along the second axis toward a second storage shelf of a second storage unit, the second storage shelf supporting a second item; lifting the carrying surface to lift the second item along at least the third axis from the second storage shelf, the carrying surface supporting the second item; retracting the carrying surface along at least the second axis from the second storage shelf; raising the carrying surface along at least the third axis to situate the second item proximate to a second AGV shelf of the plurality of AGV shelves of the storage rack; moving the carrying surface along at least the first axis until the second item is positioned above the second AGV shelf; and lowering the carrying surface along at least the third axis to place the second item on the second AGV shelf. The method further including: adjusting a height of the AGV shelf to accommodate a height of the item. The method further including navigating the AGV to a different location within the operating environment, the different location within the operating environment including a pick-cell station, the pick-cell station receiving items from a plurality of AGVs; and issuing instructions to a picker at the pick-cell station to place the item in a given carton with one or more other items.
Another general aspect includes a system including: An item handling and storage mechanism for an AGV, including: an item storage rack mountable to a frame of the AGV, the item storage rack including a plurality of shelves, each shelf of the plurality of shelves capable of storing an item; an extender mountable at a proximal end to the frame of an AGV proximate to the item storage rack, the extender having three or more degrees of freedom; and a carrying surface connected at a distal end of the extender, the carrying surface being movable by the extender vertically parallel relative to a face of the item storage rack, perpendicularly relative to the face of the item storage rack, and horizontally parallel relative to the face of the item storage rack, the carrying surface being extendable by the extender using the three or more degrees of freedom to retrieve a certain item from a separate shelving unit located within reaching distance of the extender and retractable using the three or more degrees of freedom to place the certain item on one of the shelves of the item storage rack.
Implementations of the item handling and storage mechanism may include one or more of the following features. The item handling and storage mechanism for AGV further including an optical scanner coupled to the extender that scans a shelf marker on the separate shelving unit, the shelf marker indicating a position of a shelf of the separate shelving unit. The item handling and storage mechanism for AGV where: the item includes a modular container having a coupling portion, and the carrying surface is compatibly engageable with the coupling portion of the modular container to lift the modular container from the separate shelving unit, retain the modular container during handling, and place the modular container on the one of the shelves of the item storage rack.
Other implementations of one or more of these aspects include corresponding systems, apparatus, and computer programs, configured to perform the actions of the methods, encoded on computer storage devices.
It should be understood that the language used in the present disclosure has been principally selected for readability and instructional purposes, and not to limit the scope of the subject matter disclosed herein.
The disclosure is illustrated by way of example, and not by way of limitation in the figures of the accompanying drawings in which like reference numerals are used to refer to similar elements.
Among other benefits, the technology described herein improves upon that described in the Background Section. For instance, the technology provides robotic devices, systems, methods, and other aspects that can more efficiently process goods (e.g., items or items in a distribution facility) based on demand. Further, the technology can reduce the amount of irrelevant items carried simultaneously with relevant items by providing automated guided vehicle(s) (AGV(s)) that are configured to efficiently carry items.
The technology described herein includes example AGVs that efficiently carry items. In some implementations, a cart AGV may autonomously transport a cart loaded with cartons into which items may be picked in a pick-to-cart area. The use of the cart AGV is beneficial, for example, for high velocity items (e.g., having a threshold frequency of being picked) by allowing the cartons, into which the high velocity items are to be placed, to travel to the locations of the items.
In some implementations, a picking AGV may autonomously retrieve items from storage and transport them to a picker, for example, at a pick-cell station. A picking AGV may autonomously retrieve items from shelving units in a high density storage area, transport them (e.g., on a shelf of the picking AGV) to a picker, and, in some instances, place the items on shelves at a pick-cell station for access by the picker. The technologies described in reference to the picking AGV are beneficial over the previous solutions described in the Background Section at least because they allow the picking AGV to retrieve individual items or containers of items from shelving units in a high density storage area rather than having to retrieve entire shelving units.
Features of the technology described herein can be integrated into any logistics system, dispatch system 106, warehouse execution system 102, warehouse management system 104, a robot execution server 132, etc., to coordinate the provision of to-be-picked items in a hybrid modular storage fetching system. This technology beneficially improves productivity and throughput, increases asset utilization, and lowers cycle time and labor costs. These benefits, in turn, lead to shorter delivery times and result in significant savings and business value.
With reference to the figures, reference numbers may be used to refer to components found in any of the figures, regardless whether those reference numbers are shown in the figure being described. Further, where a reference number includes a letter referring to one of multiple similar components (e.g., component 000a, 000b, and 000n), the reference number may be used without the letter to refer to one or all of the similar components.
The WES 102 may, in some implementations, include one or more hardware and/or virtual servers programmed to perform the operations, acts, and/or functionality described herein. The components of the WES 102 may comprise software routines storable in one or more non-transitory memory devices and executable by one or more computer processors of the WES 102 to carry out the operations, acts, and/or functionality described herein. In further implementations, these routines, or a portion thereof, may be embodied in electrical hardware that is operable to carry out the operations, acts, and/or functionality described herein.
The REX 132 may, in some implementations, include one or more hardware and/or virtual servers programmed to perform the operations, acts, and/or functionality described herein. The REX 132 may generate a schedule that defines the route for an AGV during a picking session, as described herein. For a given cart AGV 116a . . . 16n, depending on the items (e.g., identified by stock keeping units or SKUs) to be placed in the cartons of that cart, the REX 132 generates a schedule and transmits it to the dispatch system 106, which in turn deploys a cart AGV 116 according to the schedule, for instance. In some implementations, the dispatch system 106 instructs the AGV to proceed through one or more of the picking zones of the distribution facility according to the schedule. The schedule of each of the AGVs may be coordinated such that an optimal flow can be achieved, as discussed elsewhere herein.
In some implementations, the REX 132 may include or may communicate with a SKU (e.g., a stock keeping unit or unique identifier identifying an item) routing engine. The SKU routing engine is executable to route items into different storage zones depending based on picking profiles of the items, which may be stored and maintained as item data 130. The SKU routing engine dynamically monitors the picking activity in the distribution facility, tracks which items have the highest volume or velocity for a given timeframe, stores the tracking data in the data store 120, and can instruct the REX 132 to have items relocated by AGVs to different storage locations in the distribution facility based on the tracked picking activity.
A picking profile of a given item can change over time as demand for the item changes. The demand for a given item may be random or predicable (e.g., seasonal), and may change based on time of day, week, month, year, etc. The item routing engine may maintain the picking profile in the database as item data 130, and utilize that data to determine in which zone of the distribution facility to store the item.
Advantageously, based on the picking profiles (e.g., velocity and volume), the SKU routing engine may provide a distinct automated application for picking. In some implementations, the SKU routing engine may continually algorithmically evaluate the picking profile of each SKU and instruct the WES 102 and dispatch system 106 to transfer/relocate items to another storage location and/or picking area, swap item locations, etc., when necessary to maintain the most expedient flow in the facility. This advantageously reduces capital associated with fully automated high velocity items and reduces replenishment complexity.
The WES 102 may store productivity information for points in the distribution facility in a database (e.g., a non-transitory data store 120). The productivity information may reflect mechanical capacity of that given point of the AGV system. In some cases, the mechanical capacity may be dynamic based on current conditions (e.g., system health, staffing levels (e.g., number of associates working in zone), stock levels, operational state, etc.).
In some implementations, the WMS 104 and/or WES 102 may algorithmically analyze the configuration of a cart AGV 116 depending on items that are set for distribution/fulfillment in the next picking time window. The WMS 104 and/or WES 102 may generate a stocking list for the cart based on hub, priority, pick density, pick zone demand, and item-to-item affinity, etc. The REX 132 may use the stocking list when generating the schedule for the cart AGV 116.
The dispatch system 106 may be electronically communicatively coupled to a plurality of AGVs. In some implementations, the dispatch system 106, or elements thereof, may be integrated with or communicatively coupled with the REX 132. The dispatch system 106 includes hardware and software configured to dispatch the AGVs, and is coupled for communication the components of the system 100 to receive instructions and provide data. The dispatch system 106 may calculate a route to execute the task considering traffic and resources. In some cases it adjusts the route or the task in order to keep the route optimum.
The AGVs are robotic vehicles including drive units providing motive force for moving the AGVs (and, in some instances, carts, modular storage units 602, AGV racks, AGV shelves, etc.), guidance systems for determining position of the AGVs within the distribution facility, and equipment for carrying items. The equipment for carrying items may include carton holders, AGV shelves, modular storage unit holders, etc., such as carts, shelves, etc., as described in further detail in reference to
A cart AGV 116 is an automated guided vehicle or robot configured to autonomously transport pick-to-cart items from a pick-to-cart area 302 of the distribution facility to a pick-cell station 316 and/or finalizing area 314 (e.g., as described in reference to
A picking AGV 114a . . . 114n is an automated guided vehicle or robot that may be configured to autonomously transport items from a high-density storage area 304 of the distribution facility to a pick-cell station 316, replenishment area 318, and/or finalizing area 314. The picking AGV 114 may include a drive unit adapted to provide motive force to the picking AGV 114, a guidance system adapted to locate the picking AGV 114 in the distribution facility, and a shelving unit, which may be adapted to hold modular storage units 602. The picking AGV 114 may include a container handling mechanism (CHM) 716 (e.g., as shown in
The WMS 104 may, in some implementations, include one or more hardware and/or virtual servers or software routines storable in one or more non-transitory memory devices and executable by one or more processors to perform the operations, acts, and/or functionality described herein. The WMS 104 may be configured to store and maintain carton data 124 in the data store 120. The carton data 124 includes information about cartons and/or containers in the system, such as a unique identifier for each carton or container, a carton or container type, the zones a carton will visit, the number of pick lines a carton proceeds through, and the priority for the carton. Some cartons may have a higher priority relative to other cartons and the system 100 may expedite handling of those cartons with higher priority relative to other cartons by the system 100. The carton data 124 may include a picklist defining the items the carton will contain. The WMS 104 may store data mapping items to the different pick zones (e.g., the pick-to-cart area 302, the high-density storage area 304, a particular modular storage unit 602, a particular location at a particular pick-cell station 316, etc.). In some implementations, the WMS 104 may be configured to communicate the carton data 124 with the WES 102, the picking system 108, and/or dispatch system 106 in real time, in batches, as requested by these components, etc.
The picking system 108 may, in some implementations, include one or more hardware and/or virtual servers or software routines storable in one or more non-transitory memory devices and executable by one or more processors to perform the operations, acts, and/or functionality described herein. The picking system 108 may receive pick confirmations, for example, from pickers or operators (e.g., using barcode scanners, NFC, RFID chips, or other sensors or input methods) working within a pick zone (e.g., a pick-to-cart area 302, pick-cell station 316, etc.) confirming that picks for a given carton have been performed, as described in further detail below. An example picking system 108 may include an available pick-to-voice or a pick-to-light system. The picking system 108 may be configured to communicate the pick confirmation data with the WES 102, WMS 104, or other components of the system in real time, in batches, as requested by the components of the system, etc.
The picking system 108 may receive confirmatory input (e.g., pick confirmations) from pickers working within a pick zone. The confirmatory input confirms that all picks for a given carton have been completed. The picking system 108 transmits the confirmatory input to the WES 102. The confirmatory input may include the time stamp reflecting completion of the picks in the zone, a unique identifier identifying the picker (operator), a unique identifier identifying the pick zone, a unique identifier identifying the AGV, and/or a unique identifier identifying the carton (e.g. a carton number).
The data store 120 is an information source for storing and providing access to data. The data stored by the data store 120 may be organized and queried using various criteria including any type of data stored by it. The data store 120 may include data tables, databases, or other organized collections of data. An example of the types of data stored by the data store 120 may include, but is not limited to map data 122, AGV data 128, carton data 124, order data 126, modular storage unit data, etc. In some instances, the data store 120 may also include, conveying system attributes, picking data, picker attributes, sensor data, etc.
The data store 120 may be included in the WES 102, WMS 104, REX 132, or in another computing system and/or storage system distinct from but coupled to or accessible by the WES 102, WMS 104, REX 132, or other components of the system 100. The WES 102, picking system 108, REX 132, and/or dispatch system 106, for example, may store and maintain map data 122, order data 126, carton data 124, and AGV data 128. The data store 120 can include one or more non-transitory computer-readable mediums for storing the data. In some implementations, the data store 120 may store data associated with a database management system (DBMS) operable on a computing system. For example, the DBMS could include a structured query language (SQL) DBMS, a NoSQL DMBS, various combinations thereof, etc. In some instances, the DBMS may store data in multi-dimensional tables comprised of rows and columns, and manipulate, e.g., insert, query, update and/or delete, rows of data using programmatic operations.
The map data 122 may include data reflecting the 2 or 3 dimensional layout of the facility including the location of modular storage units 602, picking areas, lanes, equipment 110, storage shelving units, items, AGVs, etc. Map data 122 may indicate the attributes of the distribution facility, including attributes of zones (e.g., one or more pick-to-cart areas 302, high-density storage areas 304, induction areas 308, finalizing areas 314, pick-cell stations 316, replenish stations, etc.). For example, attributes of zones may include the number, quantity, and location of shelving units or bays, modular storage units 602, items, guidance system locators or markers, etc.
The order data 126 includes data about picking including orders, items picked, items to be picked, picking performance, picker identities, pick confirmations, locations items are picked from, etc. Order data 126 may indicate the quantity and identity of items in orders, shipping addresses, order priority, progress of order fulfillment, number of cartons in an order, etc.
Item data 130 may describe items available for picking in a distribution facility. The item data 130 may include unique identifiers for these items, the item volume (e.g., the total amount picked in given window (e.g., in an hour, day, etc.)), the item velocity (e.g., number of different times item picked in given window (e.g., per hour, day etc.), the unique location of the items within the distribution facility (aisle, shelf, shelf position, etc.), other attributes of the item (e.g., size, description, weight, quantity of items in a package, color, etc.), item inventory, mapping of items of modular storage units 602, etc. In some implementations, the item data 130 may include the quantity of particular items a modular storage unit 602 contains, the current location of a modular storage unit 602, a preferred storage location of items and/or modular storage units 602, a threshold inventory level of items to be satisfied before autonomously transporting the modular storage unit 602 to a replenishment area 318 by a picking AGV 114 (e.g., to restock the items in the modular storage unit 602).
The AGV data 128 may describe the state of an AGV (operational state, health, location, battery life, storage capacity, items being carried, cartons, etc.), whether picker assigned to it, etc.
The components of the system 100 may be coupled to exchange data via wireless and/or wired data connections. The connections may be made via direct data connections and/or a computer network. The computer network may comprise any number of networks and/or types of networks, such as wide area networks, local area networks, virtual private networks, cellular networks, close or micro proximity networks (e.g., Bluetooth, NFC, etc.), etc. In some implementations, one or more of these components may be coupled via a data communications bus.
The pick-to-cart routing describes routing of a particular cart AGV 116a . . . 116n through a pick-to-cart area 302. For example, the pick-to-cart routing may include a picking list of pick-to-cart items to be picked to the cartons transported by the cart AGV 116. The pick-to-cart routing may indicate the location of the storage units, shelves, or bays in which an item in the picking list is located. In some implementations, the pick-to-cart routing may also include a defined route of a cart AGV 116 through these locations and an indication of locations at which to stop the cart AGV 116, so that a picker can pick items from adjacent storage units, shelves, or bays into the cartons transported by the cart AGV 116. The pick-to-cart routing may also include a schedule indicating when to pick items and when to deliver cartons to a particular pick-cell station 316.
The MSF routing describes routing of a particular picking AGV 114 through a high-density storage area 304. For example, the MSF routing may include a picking list of items stored in modular storage units 602, unique identification codes of the modular storage units 602, and the current locations of the modular storage units 602. In some instances, the current location of the modular storage units 602 may be in the high-density storage area 304, in a replenishment area 318, or at a pick-cell station 316. The MSF routing may also include a defined route of a picking AGV 114 through the distribution facility to retrieve one or more modular storage units 602 including items from one or more orders and deliver those modular storage units 602 to assigned pick-cell stations 316. The defined route may be calculated to most efficiently retrieve one or a series of modular storage units 602, maximize a quantity of modular storage units 602 for the picking AGV 114 to retrieve in a single trip, to avoid traffic of other AGVs, and/or to cause the modular storage unit(s) 602 to arrive at a pick-cell station 316 at a minimized time difference from a carton (e.g., transported by a separate cart AGV 116) arriving at the same pick-cell station 316 to which the item in the modular storage unit 602 is to be placed, for example. The MSF routing may also include a schedule indicating when to retrieve modular storage units 602 and when to deliver the modular storage units 602 to a particular pick-cell station 316.
Pick-cell routing may describe routing of AGVs among pick-cell stations 316. For instance, a modular storage unit 602 may be transferred by a picking AGV 114 from one pick-cell station 316 to another pick-cell station 316, as described elsewhere herein.
In some implementations, the WES 102, or another component of the system 100, may determine, based on load information in one or more of the pick zones, that a particular zone, picker, path, pick-cell station 316, etc., has a high traffic load. In response to such a determination, the WES 102 may dynamically adjust the routing schedule, for example, dictating which cart AGVs 116 or picking AGVs 114 are sent into different zones of the distribution facility. For example, the WES 102 may determine that there is a threshold level of traffic (e.g., by cart AGVs 116) in the pick-to-cart area 302, in response to which determination, the WES 102 may induct AGVs (e.g., cart AGVs 116 with particular orders to be filled) into the hybrid modular storage fetching system that bypass the pick-to-cart area 302 and proceed directly to pick-cell stations 316 to receive items from modular storage units 602. In another example implementation, the WES 102 may determine, for instance, that there is a threshold level of traffic in a staging area 312 or that no picking AGVs 114 are available to retrieve items from high-density storage 304 and may, in response, induct cart AGVs into the system that do not stop at a pick-cell station 316 or that require fewer modular storage units 602 to be retrieved from high-density storage. Accordingly, in some implementations, the WES my dynamically balance the load of various zones, AGVs, pick-cell stations, etc., in the system by adapting the composition (e.g., items from pick-to-cart versus from high-density storage) of orders/cartons on a particular AGV (e.g., a cart AGV), for example.
At 204, the REX 132 may transmit a signal including the picking schedule (or components thereof) to the dispatch system 106.
At 206, the dispatch system 106 may dispatch a cart AGV 116 according to the picking schedule. In some implementations, dispatching a cart AGV 116 may include creating cartons, assigning the cartons to a cart to be transported by a cart AGV 116, placing the cartons on the cart, and, in some instances, coupling the cart AGV 116 with the cart. For instance, the WES 102 may assign orders (or items thereof) to cartons. Labels with unique identification codes identifying the cartons may be printed, placed on cartons, and the cartons may be placed on the cart at an induction area 308. The unique identification codes of the cartons may match, in the data store 120, the carton (and therefor the cart/cart AGV 116) with items to be picked.
At 208, the dispatch system 106 may dispatch a picking AGV 114 according to the MSF routing.
At 210, the cart AGV 116 may autonomously navigate along a path through the pick-to-cart area 302 according to the pick-to-cart routing to retrieve one or more items located in the pick-to-cart area 302. As described elsewhere herein, the cart AGV 116 may follow the guidance system through the pick-to-cart area 302 and stop at designated areas for items stored in those areas to be picked to the designated cartons. In some implementations, the cart, carton, container, cart AGV 116, storage area, or separate computing device (e.g., a mobile device of a picker) may include an output device that provides output indicating items to be picked at a particular location and, in some implementations, the output device may also include an input to receive pick confirmations. Once the pick confirmation has been received, the cart AGV 116 may autonomously move to the next area to pick a subsequent item assigned to a carton on the cart.
Once items in the pick-to-cart storage area have been picked to the cart AGV 116, the cart AGV 116 may autonomously navigate to an assigned pick-cell station 316 or to a finalizing area 314 according to the pick-to-cart routing. In some implementations, the cart AGV 116 may decouple from the cart and leave the cart at the pick-cell station 316 (or at a finalizing area 314) so that the cart AGV 116 may transport another cart while the first cart is being filled with items from modular storage units 602, for example.
At 212, the picking AGV 114 may autonomously navigate to a location of the one or more modular storage units 602 in the high-density storage area 304 (or a replenishment area 318, pick-cell station 316, etc.), the one or more modular storage units 602 containing one or more items in an order, for example, an order with a carton transported by a cart AGV 116, as described above. The picking AGV 114 may autonomously retrieve the one or more modular storage units 602 from the high-density storage area 304, for example. The picking AGV 114 may then autonomously navigate from the location of the modular storage unit(s) 602 to the pick-cell station 316 according to the MSF routing to transport the modular storage unit(s) 602 to the pick-cell station 316. In some implementations, the picking AGV 114 may hold a plurality of modular storage units 602 and may deliver each of the modular storage units 602 to the same pick-cell station 316 or to separate pick-cell stations 316. In some implementations, the picking AGV 114 may also retrieve modular storage units 602 that are no longer needed at a particular pick-cell station either separately or while delivering new modular storage units 602 to the pick-cell station.
At 214, the picking system 108 outputs instructions to an output device (e.g., on the cart, pick-cell station, modular storage unit 602, or separate computing device, etc.), the instructions directing a picker at a pick-cell station to transfer items from modular storage unit(s) 602 at the pick-cell station to carton(s) on the cart.
At 224, the picking AGV 114 may extend a carrying surface 396 of a CHM 716 (e.g., as described in reference to
In some implementations, the picking AGV 114 may determine a presence or location of an item, modular storage unit 602, or storage shelf on the storage shelving unit using a scanner coupled with the CHM 716 (e.g., on the carrying surface 396, on the CHM 716, or elsewhere on the picking AGV 114). For instance, the picking AGV may determine a location of the storage shelf by scanning a shelf marker (e.g., a barcode, QR code, etc.) by an optical scanner coupled with the CHM 716. In some implementations, the picking AGV 114 may use a shelf identifier linked in a database to an item or container to determine a height of the storage shelf and may adjust a height of the carrying surface 396 along at least the third axis to interact with (e.g., slide between the storage shelf and the item) the item in order to lift the item from the storage shelf. In some implementations, the picking AGV 114 may alternatively or additionally use a placement of a handling component of an item or container to determine the coordinates at which to extend the carrying surface 396 in order to interact with the handling component.
At 226, the CHM 716 may lift the carrying surface 396, which in turn lifts the item vertically along at least the third axis from the storage shelf. The carrying surface 396 may support the item directly by engaging with the item (e.g., sliding underneath the item on the storage shelf before lifting it, coupling to the sides or front of the item, etc.). In some instances, the carrying surface 396 may be configured to interact with a container (e.g., a modular storage unit 602 or mini pallet, as described in reference to
At 228, the CHM 716 may retract the carrying surface 396, and thereby the item, along at least the second axis from the storage shelf. For instance, the CHM 716 may retract the carrying surface 396 until the carrying surface 396 is fully retracted or until the item has cleared a front edge of the storage shelving unit. For example, in some implementations, the picking AGV may use a known or determined (e.g., based on an optical sensor and/or attributes stored in the data store 120) size of the item to know a minimum distance at which the carrying surface 396 should be retracted to cause the item and carrying surface 396 to clear the front edge of the storage shelving unit to allow the item and carrying surface 396 to move vertically.
At 230, the CHM 716 may raise the carrying surface 396 along at least the third axis to situate the item proximate to an AGV shelf included (e.g., coupled with) the picking AGV. For example, the CHM 716 may raise the carrying surface 396 to place a bottom surface of the item above a height of the AGV shelf and, in some instances, the CHM 716 may also raise the carrying surface 396, so that the carrying surface 396 is also above the height of the AGV shelf, depending on the implementation.
In some implementations, the picking AGV may include, or have coupled thereto, a storage rack including a plurality of AGV shelves. In some such implementations, the CHM 716 may raise the carrying surface 396 along at least the third axis until the item is above a particular shelf, but below the shelf above the particular shelf to fit the item between the shelves. Upon placing an item on one of multiple shelves in the rack, the picking AGV may store an identifier of the item in association with an identifier of the AGV shelf in order to recall later which item is placed on which AGV shelf of the rack.
In some implementations, the AGV item storage rack of the picking AGV 114 may include a plurality of AGV shelves, one or more of which may have an adjustable height on the rack to accommodate items of various dimensions. The heights and/or widths of the storage shelves may be stored in the data store 120, so that the picking AGV 114, REX 132, or another component of the system 100 may use the available heights of the shelves to determine which picking AGVs 114 and/or shelves of a picking AGV to use to transport a particular item. In some implementations, the adjustable AGV shelf(ves) may be motorized to dynamically adjust their height to accommodate items of various sizes. While various vertical implementations are described, it should be understood that the AGV storage rack may include vertically and/or horizontally arranged slots and/or shelves in which items may be adjacently situated and retained, and from which items may be retrieved.
At 232, the CHM 716 may move the carrying surface 396 along at least the first axis until the item is positioned above the AGV shelf and, at 234, may lower the carrying surface 396 along at least the third axis to place the item on the AGV shelf. For example, the CHM 716 may lower the carrying surface 396 until the weight of item is resting on the AGV shelf. In some implementations, the carrying surface 396 may detach from the item (e.g., release a handling mechanism of the item) or slide out from underneath the item on the AGV shelf, so that the CHM 716 and carrying surface 396 may be used to retrieve another item.
In some implementations, the picking AGV 114 may navigate to a different location within the operating environment, for example, to a pick-cell station 316 which may be configured to receive items from a plurality of AGVs. The REX 132, or another component of the system 100, may issue instructions to a pick cell picker at the pick-cell station 316 instructing the picker to place an item from the picking AGV 114 (e.g., in a container delivered to the pick-cell station 316 by the picking AGV 114) into a given carton with one or more other items (e.g. a carton and/or items delivered by a cart AGV 116).
In some implementations, such as where the picking AGV 114 includes a rack with a plurality of AGV shelves, responsive to a CHM 716 of a picking AGV 114 storing a first item on a first AGV shelf of the picking AGV 114, the picking AGV may retrieve a second item from a second storage unit in the high-density storage area. For example, the picking AGV 114 may navigate to a second location within the operating environment to retrieve the second item. This process may be repeated as appropriate and/or needed for any suitable number of items.
In some implementations, the CHM 716 may extend the carrying surface 396 along at least the second axis toward a second storage shelf of a second storage unit (e.g., at the different location of the operating environment) where a second item is stored. The CHM 716 may lift the carrying surface 396 and thereby lift the second item (the carrying surface 396 supporting the second item) along at least the third axis from the second storage shelf. The CHM 716 may then retract the carrying surface 396 along at least the second axis from the storage shelf. The CHM 716 may then raise the carrying surface 396 along at least the third axis to situate the second item proximate to a second AGV shelf of the plurality of AGV shelves of the AGV storage rack. Once the carrying surface 396 and the item are situated at the correct height along the third axis, the CHM 716 may move the carrying surface 396 along at least the first axis until the second item is positioned above the second AGV shelf. The CHM 716 may then lower the carrying surface 396 along at least the third axis to place the second item on the second AGV shelf. Accordingly, the picking AGV 114 may retrieve a plurality of items from different storage shelving units within the operating environment at the same time and simultaneously transport them to a pick-cell station or other location within the operating environment.
The layout depicted in
The pick-to-cart area 302 is configured for high-velocity and/or volume items and advantageously reduces capital associated to handle this type of item class. Inventory may be stored in high-volume storage in cartons or pallets, for example. High velocity items may be divided into pick zones, each zone may include a plurality of bays (e.g., 4, 5, 6+), which may be balanced by the SKU routing engine based on demand by the SKU routing engine. Cart AGVs 116 may be scheduled by the REX 132 to autonomously visit these zones, and pickers accompanying the cart AGVs 116 may be guided by the picking hardware (e.g., pick-to-voice and/or pick-to-light) controlled by the picking system 108. In an example, a cart AGV 116 is instructed by the REX 132 to stop directly in front of a bay location. The cart AGV 116 may self-locate using a guidance system. For example, the guidance system may include guidance system locators or markers, such as guide tape (magnetic, colored, etc.), laser target navigation, inertial navigation, vision guidance, geolocation, QR codes on the floor of the distribution facility, RFID (radio frequency identification) tags, beacons, etc., that can be used to locate and navigate AGVs in the distribution facility. Further, the AGVs may include guidance system components configured to read the guidance system locators, such as a QR code reader, wireless radio, etc.
After the picker picks the item and confirms the pick with the picking hardware, the cart AGV 116 autonomously moves to the next sequential bay until the picks are complete. As shown in
The picking station area may include pick-cell stations 316a, 316b, and 316c situated along primary path(s) via which the cart AGVs 116 are routed. In
In some implementations, for a given picking session, the REX 132 may establish a single line picking configuration in which the picker and the cart travel through an inventory pick path along a single line until the picks are fulfilled. In further implementations, based on demand, a fast moving area may be established by the REX 132 that includes multiple routes: a higher speed line that includes single line picking for low-demand items and another area for high demand items. This combination can advantageously balance daily labor.
The layout may also include a replenishment area 318 in which modular storage units 602 are replenished with items. For instance, item inventory in a given modular storage unit 602 may be replenished by a picking AGV 114 that picks the modular storage unit 602 from static shelves and transports them to the replenishment area 318 where a case may be opened and items from the case placed directly into the modular storage units 602. One or more items (whether of the same type of item or different types) can be placed in a given modular storage unit 602. In some cases the modular storage unit 602 may be replenished while it is in the static shelf. Having multiple options (manual or AGV) for replenishment has more flexibility to adjust to resource allocation and schedule. Additionally or alternatively, the picking AGV 114 can swap out the modular storage unit 602 with another containing the same SKUs which has been prepared ahead of time and staged for that purpose.
In some implementations, the REX 132 may instruct picking AGVs 114 to replenish and distribute modular storage units 602 in different locations of the high-density storage area 304 based on order history. In these implementations, items with high order frequency orders may be distributed in more locations than items with lower order frequency. The WES 102 may maintain a moving minimum based on order quantity minimizing the need to use inventory from two locations to fulfill an order, and the REX 132 may schedule the AGVs accordingly.
The modular storage units 602 storing items may be moved by picking AGVs 114 from high-density storage area 304 into a staging area 312 and staged for movement into a pick-cell station for an upcoming pick. In some implementations, the storage units of faster-moving items may be moved directed to a pick cell 382 in a given pick-cell station 316.
In further implementations, the REX 132 may instruct a picking AGV 114 to transfer a modular storage unit 602 between cells of a pick-cell station 316, or between pick-cell stations 316 (e.g., 316a and 316b) without having to expend the time to return the modular storage unit 602 to the high-density storage area 304.
Example cart AGV paths are illustrated in
Example picking AGV paths are also illustrated in
One or multiple of the pick cells 382 may be organized into a staging area 312 around a picker in a pick-cell station 316, so that modular storage units 602 can be easily accessed by the picker. In some implementations, a picking AGV 114 may be configured to stage the modular storage units 602 at the staging area 312. For instance, a picking AGV 114 may approach from the rear of a pick cell 382 and stage (e.g., place, deliver, etc.) a modular storage unit 602 on the pick cell 382. In some implementations, a modular storage unit 602 may be associated by the picking system 108 with a particular location in the staging area 312 to more precisely direct a picker to the location of the modular storage unit 602 (e.g., using a pick-to-light or other output system).
At a given pick-cell station 316, a cart AGV 116 may arrive and situate itself on one side of the station with the cartons on the cart AGV 116 facing the picker. On the other sides of the station are pick cells 382 in which modular storage units 602 situated and from which the picker may select items to fulfill the orders associated with the cartons. The modular storage units 602 may contain one or more items, types of items (e.g., represented by different universal product codes or stock keeping units), etc.
In some implementations, a pick cell 382 (e.g., 382d and 382e) may be a device that is mobile and can be transported by an AGV (e.g., a cart AGV 116). A mobile pick cell 382d or 382e can be preconfigured with modular storage units 602 prior to picking and then transported to the pick-cell station 316. For example, a particular pick-cell station 316 may accordingly fulfill orders with the items from the modular storage units 602 preconfigured or staged in one of the pick cells 382a, 382b, and 382c of the pick-cell station 316.
A first picking AGV 114a is illustrated in
For example, the picking AGV 114, may determine which storage shelf on a target storage shelving unit 394 to align a carrying surface 396 of the extender with (based on control instructions received from the REX 132), may elevate the carrying surface 396 to a height based on the height of the storage shelf or a handling mechanism of the container 398. In some instances, the picking AGV 114 may raise the carrying surface 396 toward the storage shelf and stop once a scanner (e.g., coupled with the extender or carrying surface 396) of the picking AGV 114 detects a shelf position marker (e.g., using the marker's unique identification code scanned from the marker and compared to control instructions received from the REX 132, depending on the implementation).
In some implementations, the picking AGV 114 may adjust the extender so that the carrying surface 396 may extend underneath the container 398, as illustrated in
At 404, the WES 102 may analyze the order to determine whether the order includes items in pick-to-cart 302 and/or high-density storage areas 304. For example, a unique identification code of the items in the order may be matched against information in the data store 120 to evaluate the location (e.g., the particular zone, bay, shelf, modular storage unit 602, etc.) and quantity of the item in the inventory of the distribution facility.
At 406, the WES 102 may generate a picking schedule including pick-to-cart, MSF, and/or pick-cell routing, as described above. The generated picking schedule may indicate timing, a particular cart AGV 116 to retrieve pick-to-cart items, a particular picking AGV 114 to retrieve items in high-density storage, and a particular pick-cell station 316 in which the items from each zone may be combined in a carton. In some implementations, the picking schedule may also indicate an induction station, finalizing area 314, particular path through the distribution facility, particular pickers or operators assigned to the orders, etc.
At 408, the dispatch system 106 may transmit a signal identifying pick-to-cart items, item locations, and, in some implementations, identification of a designated pick-cell station 316 and time window for the items to be at the designated pick-cell station 316, to a cart AGV 116. It should be noted that other information, such as routing directions, priority, traffic of other AGVs, etc., may also be provided to the cart AGV 116 and/or a computing device of picker(s) associated with the cart AGV 116 to refine the routing and autonomous navigation of the cart AGV 116.
At 410, the dispatch system 106 may transmit a signal identifying high-density items, corresponding modular storage units 602, locations of the corresponding modular storage units 602, etc., to one or more picking AGVs 114 (e.g., multiple picking AGVs 114 may be employed to distribute the work of modular storage unit 602 transport). Other information such as identification of a designated pick-cell station 316 and time window for the items to be at the designated pick-cell station 316, routing directions, priority, traffic of other AGVs, modular storage unit 602 dimensions, etc., may also be transmitted in the signal to the picking AGV(s) 114.
At 426, the cart AGV 116 may navigate to a bay (e.g., a shelving bay) where a pick-to-cart item is stored. For example, a guidance system coupled with the cart AGV 116 may read navigation markers and follow them until a destination defined by the REX 132 (or another component of the system 100) is reached. For instance, the cart AGV 116 may stop adjacent to the location where the item is stored (e.g., in front of a storage shelving unit).
At 428, the picking system 108 may output an instruction to an output device of a picker identifying the item and quantity to be picked at that location. In some implementations, the picking system 108 may coordinate lights or screens on the cart indicating into which carton an item is to be placed and/or lights on a shelving bay/location of the item in the pick-to-cart area 302 indicating the storage location of the item. Other systems, such as audio (e.g., pick-to-voice), a mobile computing device indicating the location of the item, etc., are possible.
At 430, the picking system 108 and/or cart AGV 116 may determine whether there are additional items in the pick-to-cart area 302 assigned to the cart and, in response to determining that there is an additional item, may return to 426 to navigate to the next location of an item. In some implementations, the order of locations visited by the cart AGV 116 is based on a picking list configured to order the picking according to a designated path through the pick-to-cart area 302. In some implementations, the output, at 428, may indicate that an item at a given location is to be picked into multiple cartons (e.g., which cartons may correspond to separate orders) on the cart.
At 432, in response to a negative determination at 403, the picking system 108 may determine whether there are items in the high-density storage area 304 also assigned to one or more cartons transported by the cart AGV 116 (and/or whether the cart is scheduled to be delivered to a pick-cell station 316). At 434, if there are no items to be added to the cartons from the high-density storage area 304 (or if, for example, these items are to be added at the finalizing area 314), the cart AGV 116 may autonomously navigate to a finalizing area 314. At 436, if, however, there are additional items to be added to one or more of the cartons transported by the cart AGV 116 at a pick-cell station 316, the cart AGV 116 may autonomously navigate to an assigned pick-cell station 316 to receive those items. This may be done according to (e.g., at a time window set by) a picking schedule, in coordination with an availability at the pick-cell station 316, and/or in coordination with one or more picking AGVs 114 delivering items to the assigned pick-cell station 316 to be picked into cartons on the cart AGV 116.
At 442, the WES 102 may identify a location of a first modular storage unit 602 having an appropriate quantity of first items in response to receiving a signal to retrieve those items from high-density storage (or another current location of a modular storage unit 602, such as a pick-cell station 316, replenishment area 318, etc.). As described above, the quantity of particular items stored in a modular storage unit 602 and the current location (and, in some instances, schedule of future locations) of the modular storage unit 602 are stored in the data store 120. In some implementations, a particular carton, order, or plurality of orders assigned to a cart may require multiple of a particular item. The WES 102 may verify that a sufficient quantity of the item is located in a particular modular storage unit 602 prior to signaling a picking AGV 114 to retrieve the particular modular storage unit 602. If a particular modular storage unit 602 does not have a sufficient quantity of an item to fill all designated cartons, the picking AGV 114 may retrieve a different modular storage unit 602 (e.g., having a sufficient quantity of the item), multiple modular storage units 602, or may send an error for a replenishment system/area, a human operator, or other system to remedy the error.
At 444, the WES 102 may identify a location of second modular storage unit(s) 602 having appropriate quantities of second item(s). A set of cartons transported by a cart AGV 116 may include any number of different items to be retrieved from high-density storage by a picking AGV 114.
At 446, the picking AGV(s) 114 (e.g., multiple picking AGVs 114 may be used) may autonomously navigate to a location of a first modular storage unit 602 in a high density storage area, and at 448, the picking AGV 114 may retrieve the first modular storage unit 602 (e.g., as described in reference to
At 450, a picking AGV 114 may then autonomously navigate to a location of a second modular storage unit 602 in the high-density storage area 304 and retrieve a second modular storage unit 602 (e.g., according to the method described in
At 454, the picking AGV 114 may autonomously deliver the first modular storage unit 602 to a pick-cell station assigned for the first modular storage unit 602 and, at 456, the picking AGV 114 may autonomously deliver the second modular storage unit 602 to a pick-cell station 316 assigned for the second modular storage unit 602. In some implementations, the pick-cell station 316 for the first and second modular storage units 602 may be the same pick-cell station 316. In some implementations, the pick-cell stations 316 for the different storage units may be different. For example, a picking AGV 114 may deliver a first modular storage unit 602 to a first pick-cell station 316 and then autonomously navigate to a second pick-cell station 316 to deliver the second modular storage unit 602.
At 464, the picking system 108 determines whether there are additional items from the modular storage units 602 at the pick-cell station 316 assigned to a particular carton. If there are addition items to be picked for a carton, the method may return to 462 for the next item assigned to a carton. If there are no more items to be picked for a particular carton, the picking system 108 may determine, at 466, whether there are additional items from modular storage units 602 assigned to the set of cartons in the cart (e.g., brought by the cart AGV 116 to the particular pick-cell station 316). If there are additional items for additional cartons, the method returns to 462 for those cartons and items and iterates accordingly. It should be noted that the order of the picking, output, confirmation, etc., process, may be changed without departing from the scope of this disclosure.
If the picks for a set of cartons on a cart are complete at the pick-cell station 316, at 468, the cart AGV 116 may autonomously navigate to a finalizing area 314, for instance, where the cart AGV 116 may decouple from the connectable cart and the cartons on the connectable cart may be shipped either manually or by a machine for closing the cartons and removing them from the cart.
A picking AGV 114 may move one or more of the modular storage units 602 from the pick-cell station 316. For example, at 470, a picking system 108 may determine whether additional items from a particular modular storage unit 602 are assigned to the pick-cell station 316 in a subsequent picking window (e.g., for a subsequent cart AGV 116 arriving at the pick-cell station 316). If the modular storage unit 602 (e.g., items remaining in the modular storage unit 602) will be used again at the pick-cell station 316, at 472, the modular storage unit 602 may be left at the pick-cell station 316 for an additional pick window.
At 474, the WES 102 or picking system 108 may determine whether items from a particular modular storage unit 602 are assigned to a different pick-cell station 316 in a subsequent pick window and, if so, at 476, may direct the picking AGV 114 to retrieve the modular storage unit 602 from the current pick-cell station 316 and deliver it to the different pick-cell station 316.
At 478, the picking AGV 114 may retrieve one or more modular storage unit(s) 602 from the pick-cell station 316, autonomously navigate to a location in the high-density storage area 304, and store the modular storage unit 602 at that location. The locations at which the modular storage units 602 are stored may be determined based on availability, proximity to a pick-cell area 310, proximity to frequently co-ordered items, frequency with which the items in the modular storage units 602 are retrieved, or any other schema.
In some implementations, if all of a particular item in a modular storage unit 602 have been picked from the modular storage unit 602 (e.g., it is empty), then the picking AGV 114 may autonomously deliver the modular storage unit 602 to a replenishment area 318.
As illustrated in
In some implementations, the cart AGV 502 may also include a guidance system that may detect, for instance, a human picker associated with the cart AGV 502 (e.g., via a tracking device on the picker, optical recognition, etc.), determine the picker's position, and reposition itself automatically based on the picker's position by comparing the cart AGV's 502 position and the picker's position, and a pre-determined offset (e.g., a distance in front of, behind, and/or next to the picker). This advantageously allows the cart AGV 502 to follow the picker.
A drive unit 520 of the AGV 522 may include one or more turntables 524a and 524b coupled to a bottom surface of the AGV 522 and one or more drive motors coupled to the turntables 524. The turntables 524 may each include wheels 526 coupled to drive motors. For instance, the AGV 522 may include two turntables 524a and 524b each of which include one or more drive motors, each of the drive motors coupled to one or more wheels 526, tracks, treads, etc. In some implementations, the wheels 526 may be located proximate the corners of the frame, etc., to provide stability to the AGV 522 or may include additional casters, for example, to provide additional stability to the AGV 522.
The turntables 524 may be motorized and coupled to a controller of the AGV 522 allowing the wheels 526 to rotate (e.g., 90 degrees, 360 degrees, more than 360 degrees), depending on the implementation. For instance, the wheels 526 may pivot about a center of a turntable 524. Further, the wheels 526 may pivot collaboratively to spin the AGV 522 around the center axis 528 and/or maneuver the AGV 522 along essentially any X, Y trajectory (forward, backward, sideways, etc.).
As illustrated in
In some implementations, a modular storage unit 602 may include supports 612 that hold the modular storage unit 602 on a shelf, so that a carrying surface 396 of the CHM 716 may slide under the modular storage unit 602 to pick the modular storage unit 602 up, as described elsewhere herein. In some implementations, a modular storage unit 602 may include a handling component that interacts with a carrying surface 396 of a picking AGV 114 to remove the modular storage unit 602 from a storage shelf. The handling component may be positioned on bottom, top, side, or front of the modular storage unit 602. For example, a handling component may include a latch, French cleat, slots or arms for receiving prongs of the carrying surface 396 (e.g., a fork 720), a bottom surface, indentation(s), preconfigured channel(s), or other structures or formations that may be used by the carrying surface 396 to support the modular storage unit 602. Accordingly, a carrying surface 396 of a picking AGV 114 may be compatibly engageable with the coupling portion of the modular storage unit 602 to lift the modular storage unit 602 from a first target shelving unit, retain the modular storage unit 602 during handling, and place the modular storage unit 602 on a second target shelving unit.
The body 710 may include a front, a rear opposing the front, a left side extending from the front to the rear, and a right side opposing the left side and extending from the front to the rear. While various shapes and construction materials to the body 710 are possible, the body 710 may be configured to fit between rows of storage shelving in a high-density storage area 304. The body 710 may be configured to house a drive unit 712, power source, controller, and/or other components of the picking AGV 702a.
The drive unit 712 may be coupled to the body 710 and configured to receive power from the power source to provide motive force to the picking AGV 702a and propel the picking AGV 702a within an operating environment. In some implementations, the drive unit 712 may receive instructions from one or more controllers instructing the drive unit 712 to cause the picking AGV 702a to move forward, backward, sideways, turn, or perform another movement. In some implementations, the drive unit 712 may include electric motors and wheels, although other configurations, such as treads are possible. For example, the drive unit 712 may be configured as illustrated in
The drive unit 712 may be wirelessly coupled via a controller to a wireless interface and a wireless communications network to receive control signals from the dispatch system 106 and/or other components of the system 100. In some implementations, the drive unit 712 may be controlled as described in elsewhere herein, which may be executed using a distributed computing system comprising AGVs, servers, controllers, etc., for example, as shown in the system depicted in
The power source may be coupled to the components of the picking AGV 702a to provide power to the components, for example, the power source may provide power to the CHM 716, the drive unit 712, a controller, or another component of the picking AGV 702a. The power source may include a battery, a wire, contact track in the operating environment, induction charger, alternator or gas generator, etc.
Some implementations of the picking AGV 702 may include an AGV item storage rack 706 (also referred to as AGV rack 706), such as illustrated coupled with the example picking AGVs 702a-702c. While the AGV rack 706 is illustrated as coupled to the top of the body 710, other configurations are possible, for example, the AGV rack 706 may be coupled in front of, behind, to the side of, or even towed or pushed by the picking AGV 706. The AGV rack 706 may be positioned proximate to the CHM 716, so that the shelves 714 are within reach of the CHM 716 for the CHM 716 to place items on the shelves 714.
The AGV rack 706 may include a single shelf 714 or a plurality of shelves 714 coupled to a frame. The shelves 714 may include flat surfaces, bays, containers, or other mechanisms for holding a modular storage unit 602 or other item. At least one of the shelves 714, where equipped, is capable of storing the item during transit of the picking AGV 702a.
The plurality of shelves 714 may be vertically arranged and, in some implementations, one or more of the shelves 714 may have an adjustable height (e.g., adjusted manually or automatically using a motor coupled with the picking AGV 702a) on the AGV rack 706. In some implementations, a controller of the picking AGV 702a may determine a current height of a particular shelf of the plurality of shelves 714, for example, using an optical scanner or retrieving a stored height of an the particular shelf from a database (e.g., on the data store 120). For example, one or more of the shelves 714 may include a marker readable by an optical scanner coupled with the CHM 716 or carrying surface 396 to indicate to the CHM 716 a location or identification of the a particular shelf. In some implementations, a controller of the picking AGV 702a may store a shelf identifier for a shelf 714 in association with a height or size of the shelf 714, or an identifier of an item or modular storage unit 602 stored on the shelf 714.
In some implementations, a shelf 714 onto which an item is placed may be selected based on the size, height, weight capacity, or other attributes of the shelf 714. For example, a modular storage unit 602 of a given size may be placed on a shelf 714 having a corresponding size. In another example, a modular storage unit 602 having a threshold weight may be placed on a lower shelf 714 of the AGV rack 706 than a modular storage unit 602 having a lighter weight than the threshold.
The container handling mechanism or CHM 716 may include an extender for extending a carrying surface 396 from a picking AGV 702 to a storage shelving unit that is separate from the picking AGV 702. The CHM 716 may have three or more degrees of freedom to move the carrying surface 396 along three or more axes thereby allowing the CHM 716 to retrieve an item from a first target shelving unit using the carrying surface 396 and the three or more degrees of freedom and place the item on a second target shelving unit, as described in further detail in reference to
In some implementations, the CHM 716 may include a mast having an elevator 708 coupled with the body 710 and/or AGV rack 706. The elevator 708 lifts and lowers a platform 718 supporting a carrying surface 396. The elevator 708 moves the CHM 716 along a Z axis to lift and set down the container.
In some implementations, the platform 718 extends or retracts the carrying surface 396 horizontally between the picking AGV 702a and a storage shelving unit. In some implementations, the platform 718 may also extend or retract the carrying surface 396 into or out of one or more of the AGV shelves 714 to place an item on one of the AGV shelves 714. The CHM 716 includes a moveable platform 718 having a carrying surface 396 capable of translating along a plane in two or more dimensions and/or rotating about a vertical axis. For example, the platform 718 (or other component of the CHM 716, depending on the implementation) may translate the carrying surface 396 along any X and Y coordinates (e.g., sideways/left and right relative to the front of the picking AGV 702a; forward and backward relative to the front of the picking AGV 702a; etc.). This allows the CHM 716 to retrieve an item from a storage shelf and move it to and place it on an AGV shelf 714 supported by the frame, and vice versa. The CHM 716 may be adjustable to translate between an X axis, Y axis, a combination, etc.
In some implementations, the platform 718 may comprise two platforms coupled to one another, a first of which moves along a first horizontal axis and a second of which moves along a second horizontal axis perpendicular to the first horizontal axis. For instance, the first platform may be coupled with the elevator 708 and the second platform, so that the first platform may move the second platform along the first horizontal axis. The second platform may be coupled with the first platform and the carrying surface 396, so that the second platform may move the carrying surface 396 along the second horizontal axis.
The CHM 716 may be capable of moving items between the different shelves 714 in the AGV rack 706, one or more storage shelving units in a high-density storage area 304, one or more pick cells 382 in a pick-cell station 316, and, in some instances, to or from other target shelves (e.g., in an induction area 308, replenishment area 318, etc.).
In some implementations, the picking AGV 702a may include a scanner coupled with the carrying surface 396, platform 718, etc., that can read signatures or markers to determine location. For example, the scanner may be an optical scanner configured to read visual identifiers (e.g., labels including a QR code, bar code, etc.) to determine which shelf 714 the CHM 716 or the carrying surface 396 is aligned with. The optical scanner may scan a shelf marker on one or more of the AGV shelf 714 or a detached storage shelf. The shelf marker may indicate a position and/or identification code of shelves and/or modular storage units 602, for example.
In some implementations, the elevator 708 may include positional sensors to determine the position of CHM 716 and/or align the carrying surface 396 with a target shelf (whether an external or integrated with the picking AGV 702a).
The carrying surface 396 may be coupled to or integrated with the CHM 716 and is configured to support a modular storage unit 602 or other item. In some implementations, the carrying surface 396 is connected at a distal end of the CHM 716 or extender. The carrying surface 396 may be movable by the CHM 716 vertically parallel relative to a face of the AGV rack 706, perpendicularly relative to the face of the AGV rack 706, and horizontally parallel relative to the face of the AGV rack 706. The carrying surface 396 may be extendable by the CHM 716 using the three or more degrees of freedom to retrieve a certain item or modular storage unit 602 from a separate shelving unit located within reaching distance of the CHM 716 and retractable using the three or more degrees of freedom to place the certain item on one of the AGV shelves 714 of the AGV rack 706.
In some implementations, the carrying surface 396 may be adapted to interface with a modular storage unit 602, as described in reference to
In some implementations, the carrying surface 396 may include forks 720, such as those depicted in
The picking AGV 702a may include a guidance system that determines a location of the picking AGV 702a within the operating environment. For instance, the guidance system may include one or more sensors that detect and process navigation markers (e.g., QR codes, RFID labels, etc.) to locate the picking AGV 702a as the picking AGV 702a traverses the operating environment. The guidance system may be coupled to a controller of the picking AGV 702a, which may, in some instances, include local object detection intelligence and processing to avoid collision with other objects (e.g., AGVs, humans, items, storage shelving units, etc.) in the operating environment.
The picking AGV 702a may include one or more controllers coupled with the guidance system, CHM 716, drive unit 712, dispatch system 106, etc., to perform the operations described herein. For instance, the one or more controllers may receive a signal from the REX 132 (e.g., via the dispatch system 106) and signal the drive unit 712 to propel the picking AGV 702a. The one or more controllers may communicate with the guidance system to determine a location of the picking AGV 702a within the operating environment and, using the drive unit 712, navigate through the operating environment. The one or more controllers may receive a signal from the REX 132 indicating to retrieve a particular item from a target storage unit, in response to which, the one or more controllers may instruct the drive unit 712 to position the CHM 716 adjacent to the target shelving unit using the current location determined by the guidance system and then direct the CHM 716 to retrieve the item, for example, as described in reference to
The example picking AGVs 702c and 702d depicted in
In some implementations, the platform 718 may be configured to rotate a carrying surface 396, such as the forks 720 so that the forks 720 may extend or be extended about a horizontal plane, as described above. For instance, the forks 720 may extend and then retract along a first horizontal axis to retrieve a modular storage unit 602, as described above. Once the forks 720 have retracted, the platform 718 may rotate the forks 720, so that they may be extended along a second horizontal axis, for example, to place the modular storage unit 602 on an AGV shelf.
As illustrated in
Although the example picking AGVs 702c-702f, are not illustrated as including AGV shelves, it should be noted that they may include AGV shelves, as described elsewhere herein, depending on the implementation.
In some implementations, the storage shelving unit 802 may include one or more support members 804, such as poles, beams, planks, etc., which are attached to and provide support to partial shelves 806. For instance, the a partial shelf 806 may extend only partially underneath the modular storage units 602, so that a carrying surface 396 may more easily fit under the modular storage unit 602 to lift the modular storage unit 602 from the partial shelf 806, as described elsewhere herein.
In some implementations, the storage shelving unit 802 may include several partial shelves 806 vertically arranged on the support members 804 in order to create a plurality of levels of the storage shelving unit 802 from which modular storage units 602 can be retrieved by a picking AGV 114.
In the depicted implementation, the modular storage unit 602 includes a base member 902. The base member 902 may be attached to or integrated with the modular storage unit 602 and may extend between the partial shelves 806 to support the modular storage unit 602 when the modular storage unit 602 is stored in the storage shelving unit 802.
It should be noted that the components described herein may be further delineated or changed without departing from the techniques described herein. For example, the processes described throughout this disclosure may be performed by fewer, additional, or different components.
It should be understood that the methods described herein are provided by way of example, and that variations and combinations of these methods, as well as other methods, are contemplated. For example, in some implementations, at least a portion of one or more of the methods represent various segments of one or more larger methods and may be concatenated or various steps of these methods may be combined to produce other methods which are encompassed by the present disclosure. Additionally, it should be understood that various operations in the methods are iterative, and thus repeated as many times as necessary generate the results described herein. Further the ordering of the operations in the methods is provided by way of example and it should be understood that various operations may occur earlier and/or later in the method without departing from the scope thereof.
In the above description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. However, it should be understood that the technology described herein can be practiced without these specific details in various cases. Further, various systems, devices, and structures are shown in block diagram form in order to avoid obscuring the description. For instance, various implementations are described as having particular hardware, software, and user interfaces. However, the present disclosure applies to any type of computing device that can receive data and commands, and to any peripheral devices providing services.
In some instances, various implementations may be presented herein in terms of algorithms and symbolic representations of operations on data bits within a computer memory. An algorithm is here, and generally, conceived to be a self-consistent set of operations leading to a desired result. The operations are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.
It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussion, it is appreciated that throughout this disclosure, discussions utilizing terms such as “processing,” “computing,” “calculating,” “determining,” “displaying,” or the like, refer to the action and methods of a computer system that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
A data processing system suitable for storing and/or executing program code, such as the computing system and/or devices discussed herein, may include at least one processor coupled directly or indirectly to memory elements through a system bus. The memory elements can include local memory employed during actual execution of the program code, bulk storage, and cache memories that provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution. Input or I/O devices can be coupled to the system either directly or through intervening I/O controllers. The data processing system may include an apparatus may be specially constructed for the required purposes, or it may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer.
The foregoing description has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the specification to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the disclosure be limited not by this detailed description, but rather by the claims of this application. As will be understood by those familiar with the art, the specification may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. Likewise, the particular naming and division of the modules, routines, features, attributes, methodologies and other aspects may not be mandatory or significant, and the mechanisms that implement the specification or its features may have different names, divisions, and/or formats.
Furthermore, the modules, routines, features, attributes, methodologies and other aspects of the disclosure can be implemented as software, hardware, firmware, or any combination of the foregoing. The technology can also take the form of a computer program product accessible from a computer-usable or computer-readable medium providing program code for use by or in connection with a computer or any instruction execution system. Wherever a component, an example of which is a module or engine, of the specification is implemented as software, the component can be implemented as a standalone program, as part of a larger program, as a plurality of separate programs, as a statically or dynamically linked library, as a kernel loadable module, as firmware, as resident software, as microcode, as a device driver, and/or in every and any other way known now or in the future. Additionally, the disclosure is in no way limited to implementation in any specific programming language, or for any specific operating system or environment. Accordingly, the disclosure is intended to be illustrative, but not limiting, of the scope of the subject matter set forth in the following claims.
This application is a continuation-in-part of U.S. application Ser. No. 15/721,472, entitled “Hybrid Modular Storage Fetching System,” filed Sep. 29, 2017, which claims the benefit under 35 U.S.C. § 119(e) of U.S. Provisional Application No. 62/403,001, entitled “Modular Storage Fetching System (MSFS),” filed on Sep. 30, 2016, the entire contents of each of which are incorporated herein by reference. This application also claims the benefit under 35 U.S.C. § 119(e) of U.S. Provisional Application No. 62/442,891, entitled “Modular Storage Fetching System (MSFS),” filed on Jan. 5, 2017, the entire contents of which are incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3450276 | Ferrari | Jun 1969 | A |
| 3474877 | Wesener | Oct 1969 | A |
| 3563327 | Mier | Feb 1971 | A |
| 3628624 | Wesener | Dec 1971 | A |
| 3970840 | De Bruine | Jul 1976 | A |
| 4010409 | Waites | Mar 1977 | A |
| 4077535 | Oriol | Mar 1978 | A |
| 4215759 | Diaz | Aug 1980 | A |
| 4258813 | Rubel | Mar 1981 | A |
| 4278142 | Kono | Jul 1981 | A |
| 4465155 | Collins | Aug 1984 | A |
| 4496274 | Pipes | Jan 1985 | A |
| 4524314 | Walker | Jun 1985 | A |
| 4530056 | MacKinnon et al. | Jul 1985 | A |
| 4556940 | Katoo et al. | Dec 1985 | A |
| 4562635 | Carter | Jan 1986 | A |
| 4566032 | Hirooka et al. | Jan 1986 | A |
| 4593238 | Yamamoto | Jun 1986 | A |
| 4593239 | Yamamoto | Jun 1986 | A |
| 4652803 | Kamejima et al. | Mar 1987 | A |
| 4653002 | Barry | Mar 1987 | A |
| 4657463 | Pipes | Apr 1987 | A |
| 4678390 | Bonneton et al. | Jul 1987 | A |
| 4700302 | Arakawa et al. | Oct 1987 | A |
| 4711316 | Katou et al. | Dec 1987 | A |
| 4714399 | Olson | Dec 1987 | A |
| 4716530 | Ogawa et al. | Dec 1987 | A |
| 4727492 | Reeve et al. | Feb 1988 | A |
| 4742283 | Bolger et al. | May 1988 | A |
| 4751983 | Leskovec et al. | Jun 1988 | A |
| 4764078 | Neri | Aug 1988 | A |
| 4772832 | Okazaki | Sep 1988 | A |
| 4773018 | Mats | Sep 1988 | A |
| 4777601 | Boegli | Oct 1988 | A |
| 4780817 | Lofgren | Oct 1988 | A |
| 4790402 | Kasper | Dec 1988 | A |
| 4802096 | Hainsworth | Jan 1989 | A |
| 4811227 | Sigvard | Mar 1989 | A |
| 4811229 | Wilson | Mar 1989 | A |
| 4817000 | Eberhardt | Mar 1989 | A |
| 4846297 | Kasper | Jul 1989 | A |
| 4847769 | Reeve | Jul 1989 | A |
| 4847773 | Peteri | Jul 1989 | A |
| 4847774 | Tomikawa | Jul 1989 | A |
| 4852677 | Okazaki | Aug 1989 | A |
| 4857912 | Gilbreath | Aug 1989 | A |
| 4858132 | Holmquist | Aug 1989 | A |
| 4862047 | Mitsuo | Aug 1989 | A |
| 4863335 | Herigstad | Sep 1989 | A |
| 4875172 | Kanayama | Oct 1989 | A |
| 4890233 | Masayuki | Dec 1989 | A |
| 4918607 | Wible | Apr 1990 | A |
| 4924153 | Toru | May 1990 | A |
| 4926544 | Koji | May 1990 | A |
| 4935871 | Grohsmeyer | Jun 1990 | A |
| 4939650 | Nishikawa | Jul 1990 | A |
| 4939651 | Onishi | Jul 1990 | A |
| 4942531 | Hainsworth | Jul 1990 | A |
| 4947324 | Kamimura | Aug 1990 | A |
| 4950118 | Mueller | Aug 1990 | A |
| 4954962 | Weiman | Sep 1990 | A |
| 4982329 | Masanori | Jan 1991 | A |
| 4990841 | Elder | Feb 1991 | A |
| 4993507 | Ohkura | Feb 1991 | A |
| 4994970 | Noji | Feb 1991 | A |
| 4996468 | Kasper | Feb 1991 | A |
| 5000279 | Fumio | Mar 1991 | A |
| 5002145 | Tsuneo | Mar 1991 | A |
| 5005128 | Roberts | Apr 1991 | A |
| 5006988 | Yoram | Apr 1991 | A |
| 5020620 | Field | Jun 1991 | A |
| 5023790 | Luke, Jr. | Jun 1991 | A |
| 5040116 | Weiman | Aug 1991 | A |
| 5052882 | Harding | Oct 1991 | A |
| 5053969 | Booth | Oct 1991 | A |
| 5073749 | Kanayama | Dec 1991 | A |
| 5109940 | Yardley | May 1992 | A |
| 5111401 | Everett, Jr. | May 1992 | A |
| 5125783 | Kawasoe | Jun 1992 | A |
| 5134353 | Kita et al. | Jul 1992 | A |
| 5138560 | Dieter | Aug 1992 | A |
| 5154249 | Yardley | Oct 1992 | A |
| 5164648 | Kita et al. | Nov 1992 | A |
| 5170351 | Nemoto | Dec 1992 | A |
| 5170352 | Sharma | Dec 1992 | A |
| 5179329 | Masanori | Jan 1993 | A |
| 5187664 | Whatcott | Feb 1993 | A |
| 5191528 | Whatcott | Mar 1993 | A |
| 5192903 | Kita et al. | Mar 1993 | A |
| 5199524 | Ivancic | Apr 1993 | A |
| 5202832 | Lisy | Apr 1993 | A |
| 5211523 | Andrada Galan | May 1993 | A |
| 5216605 | Whatcott | Jun 1993 | A |
| 5239249 | Ono | Aug 1993 | A |
| 5249157 | Taylor | Sep 1993 | A |
| 5281901 | Yardley | Jan 1994 | A |
| 5305217 | Tadae | Apr 1994 | A |
| 5341130 | Yardley | Aug 1994 | A |
| 5387853 | Ono | Feb 1995 | A |
| 5488277 | Masanori | Jan 1996 | A |
| 5505473 | Radcliffe | Apr 1996 | A |
| 5510984 | Markin | Apr 1996 | A |
| 5525884 | Tadashi | Jun 1996 | A |
| 5545960 | Ishikawa | Aug 1996 | A |
| 5548512 | Quraishi | Aug 1996 | A |
| 5564890 | Knudsen, Jr. | Oct 1996 | A |
| 5568030 | Masanori | Oct 1996 | A |
| 5650703 | Forman | Jul 1997 | A |
| 5669748 | Knudsen, Jr. | Sep 1997 | A |
| 5875408 | Bendett | Feb 1999 | A |
| 5877962 | Radcliffe | Mar 1999 | A |
| 5911767 | Ilic | Jun 1999 | A |
| 5923270 | Rintanen | Jul 1999 | A |
| 5961559 | Koichi | Oct 1999 | A |
| 6049745 | Douglas | Apr 2000 | A |
| 6058339 | Tatsuya | May 2000 | A |
| 6092010 | Drenth | Jul 2000 | A |
| 6246930 | Hori | Jun 2001 | B1 |
| 6256560 | Kim | Jul 2001 | B1 |
| 6345217 | Arng | Feb 2002 | B1 |
| 6370452 | Pfister | Apr 2002 | B1 |
| 6377888 | Olch | Apr 2002 | B1 |
| 6459966 | Nakano | Oct 2002 | B2 |
| 6477463 | Hamilton | Nov 2002 | B2 |
| 6481521 | Kazunori | Nov 2002 | B2 |
| 6493614 | Jung | Dec 2002 | B1 |
| 6602037 | Winkler | Aug 2003 | B2 |
| 6615108 | Peleg | Sep 2003 | B1 |
| 6629028 | Paromtchik | Sep 2003 | B2 |
| 6654647 | Kal | Nov 2003 | B1 |
| 6694216 | Fujiki | Feb 2004 | B1 |
| 6721638 | Zeitler | Apr 2004 | B2 |
| 6748292 | Mountz | Jun 2004 | B2 |
| 6772062 | Lasky | Aug 2004 | B2 |
| 6882910 | Jeong | Apr 2005 | B2 |
| 6885912 | Peleg | Apr 2005 | B2 |
| 6895301 | Mountz | May 2005 | B2 |
| 6904343 | Kang | Jun 2005 | B2 |
| 6950722 | Mountz | Sep 2005 | B2 |
| 6971464 | Marino | Dec 2005 | B2 |
| 7050891 | Chen | May 2006 | B2 |
| 7110855 | Leishman | Sep 2006 | B2 |
| 7155309 | Peleg | Dec 2006 | B2 |
| 7305287 | Park | Dec 2007 | B2 |
| 7333631 | Park | Feb 2008 | B2 |
| 7349759 | Peleg | Mar 2008 | B2 |
| 7402018 | Amsbury | Jul 2008 | B2 |
| 7403120 | Bridgelall | Jul 2008 | B2 |
| 7437226 | Shim | Oct 2008 | B2 |
| 7460016 | Clott | Dec 2008 | B2 |
| 7500448 | Melhorn | Mar 2009 | B1 |
| 7505849 | Saarikivi | Mar 2009 | B2 |
| 7548166 | Clott | Jun 2009 | B2 |
| 7557714 | Clott | Jul 2009 | B2 |
| 7599777 | Passeri | Oct 2009 | B2 |
| 7609175 | Bonnefoy | Oct 2009 | B2 |
| 7613617 | McElroy | Nov 2009 | B2 |
| 7616127 | Clott | Nov 2009 | B2 |
| 7634332 | McElroy | Dec 2009 | B2 |
| 7639142 | Clott | Dec 2009 | B2 |
| 7648329 | Stevenson | Jan 2010 | B2 |
| 7656296 | Runyon | Feb 2010 | B2 |
| 7681796 | Zimmerman | Mar 2010 | B2 |
| 7689001 | Chul | Mar 2010 | B2 |
| 7693757 | Zimmerman | Apr 2010 | B2 |
| 7765027 | Hong | Jul 2010 | B2 |
| 7826919 | Dingle | Nov 2010 | B2 |
| 7835821 | Kim | Nov 2010 | B2 |
| 7840328 | Baginski | Nov 2010 | B2 |
| 7845560 | Emanuel | Dec 2010 | B2 |
| 7850413 | Fontana | Dec 2010 | B2 |
| 7871234 | Yuyama | Jan 2011 | B2 |
| 7873469 | D Andrea | Jan 2011 | B2 |
| 7890228 | Werner | Feb 2011 | B2 |
| 7894932 | Mountz | Feb 2011 | B2 |
| 7894933 | Mountz | Feb 2011 | B2 |
| 7894939 | Spencer | Feb 2011 | B2 |
| 7894951 | Norris | Feb 2011 | B2 |
| 7912574 | D Andrea | Mar 2011 | B2 |
| 7912633 | Kennedy | Mar 2011 | B1 |
| 7920962 | D Andrea | Apr 2011 | B2 |
| 7925514 | McElroy | Apr 2011 | B2 |
| 7953551 | Park | May 2011 | B2 |
| 7980808 | Chilson | Jul 2011 | B2 |
| 7991521 | Stewart | Aug 2011 | B2 |
| 7996109 | Spencer | Aug 2011 | B2 |
| 8010230 | Spencer | Aug 2011 | B2 |
| 8020657 | Catalfano | Sep 2011 | B2 |
| 8031086 | Dickson | Oct 2011 | B2 |
| 8068978 | D Andrea | Nov 2011 | B2 |
| 8072309 | Duckworth | Dec 2011 | B2 |
| 8075243 | Stevenson | Dec 2011 | B2 |
| 8146702 | Emond | Apr 2012 | B2 |
| 8160728 | Curtis | Apr 2012 | B2 |
| 8170711 | Dingle | May 2012 | B2 |
| 8192137 | Chilson | Jun 2012 | B2 |
| 8193903 | Duckworth | Jun 2012 | B2 |
| 8196835 | Emanuel | Jun 2012 | B2 |
| 8200423 | Kennedy | Jun 2012 | B2 |
| 8204624 | Spencer | Jun 2012 | B2 |
| 8210791 | Chilson | Jul 2012 | B2 |
| 8220710 | D Andrea | Jul 2012 | B2 |
| 8229619 | Shim | Jul 2012 | B2 |
| 8239291 | Verminski | Aug 2012 | B2 |
| 8265873 | D Andrea | Sep 2012 | B2 |
| 8269643 | Chou | Sep 2012 | B2 |
| 8271132 | Walton | Sep 2012 | B2 |
| 8280546 | Dingle | Oct 2012 | B2 |
| 8280547 | Dingle | Oct 2012 | B2 |
| 8311902 | Mountz | Nov 2012 | B2 |
| 8369981 | Spaulding | Feb 2013 | B2 |
| 8381982 | Emanuel | Feb 2013 | B2 |
| 8406949 | Kondo | Mar 2013 | B2 |
| 8412400 | D Andrea | Apr 2013 | B2 |
| 8417444 | Smid | Apr 2013 | B2 |
| 8418919 | Beyda | Apr 2013 | B1 |
| 8425173 | Lert | Apr 2013 | B2 |
| 8433442 | Friedman | Apr 2013 | B2 |
| 8433469 | Day | Apr 2013 | B2 |
| 8444369 | Bragg | May 2013 | B2 |
| 8452464 | Schloemer | May 2013 | B2 |
| 8457978 | McElroy | Jun 2013 | B2 |
| 8473140 | Norris | Jun 2013 | B2 |
| 8483869 | Wurman | Jul 2013 | B2 |
| 8498734 | Dunsker | Jul 2013 | B2 |
| 8515612 | Hideo | Aug 2013 | B2 |
| 8538692 | D Andrea | Sep 2013 | B2 |
| 8571781 | Bernstein | Oct 2013 | B2 |
| 8577551 | Corbett | Nov 2013 | B2 |
| 8587455 | Porte | Nov 2013 | B2 |
| 8594834 | Clark | Nov 2013 | B1 |
| 8594835 | Toebes | Nov 2013 | B2 |
| 8606392 | D Andrea | Dec 2013 | B2 |
| 8626332 | Dunsker | Jan 2014 | B2 |
| 8626335 | Barbehenn | Jan 2014 | B2 |
| 8639382 | Clark | Jan 2014 | B1 |
| 8649899 | Wurman | Feb 2014 | B2 |
| 8653945 | Lee | Feb 2014 | B2 |
| 8670892 | Yang | Mar 2014 | B2 |
| 8676426 | Murphy | Mar 2014 | B1 |
| 8700502 | Mountz | Apr 2014 | B2 |
| 8718814 | Clark | May 2014 | B1 |
| 8718815 | Shimamura | May 2014 | B2 |
| 8725286 | Dingle | May 2014 | B2 |
| 8725317 | Elston | May 2014 | B2 |
| 8725362 | Jensen | May 2014 | B2 |
| 8725363 | Jensen | May 2014 | B2 |
| 8731777 | Schloemer | May 2014 | B2 |
| 8740538 | Lert | Jun 2014 | B2 |
| 8751063 | Wilson | Jun 2014 | B2 |
| 8751147 | Colwell | Jun 2014 | B2 |
| 8755936 | Friedman | Jun 2014 | B2 |
| 8760276 | Yamazato | Jun 2014 | B2 |
| 8761989 | Murphy | Jun 2014 | B1 |
| 8788121 | Klinger | Jul 2014 | B2 |
| 8798784 | Clark | Aug 2014 | B1 |
| 8798786 | Pollak | Aug 2014 | B2 |
| 8798840 | Fong | Aug 2014 | B2 |
| 8805573 | Brunner | Aug 2014 | B2 |
| 8805574 | Watt | Aug 2014 | B2 |
| 8825257 | Ozaki | Sep 2014 | B2 |
| 8825367 | Nagasawa | Sep 2014 | B2 |
| 8831984 | Santini | Sep 2014 | B2 |
| 8862397 | Koji | Oct 2014 | B2 |
| 8874300 | Catalfano | Oct 2014 | B2 |
| 8874360 | Davis | Oct 2014 | B2 |
| 8880416 | McElroy | Nov 2014 | B2 |
| 8886385 | Toshiki | Nov 2014 | B2 |
| 8892240 | Vliet et al. | Nov 2014 | B1 |
| 8892241 | Weiss | Nov 2014 | B2 |
| 8909368 | D Andrea | Dec 2014 | B2 |
| 8930133 | Barbehenn | Jan 2015 | B2 |
| 8948956 | Takahashi | Feb 2015 | B2 |
| 8954188 | Sullivan et al. | Feb 2015 | B2 |
| 8965561 | Jacobus | Feb 2015 | B2 |
| 8965562 | Wurman | Feb 2015 | B1 |
| 8965578 | Ondrej | Feb 2015 | B2 |
| 8970363 | Schumacher | Mar 2015 | B2 |
| 8972045 | Wurman | Mar 2015 | B1 |
| 8983647 | Casteel | Mar 2015 | B1 |
| 8988285 | Smid | Mar 2015 | B2 |
| 8989918 | Sturm | Mar 2015 | B2 |
| 9002506 | Ahmed | Apr 2015 | B1 |
| 9002581 | Wellman | Apr 2015 | B2 |
| 9008827 | Casteel | Apr 2015 | B1 |
| 9008828 | Worsley | Apr 2015 | B2 |
| 9008829 | Worsley | Apr 2015 | B2 |
| 9008830 | Worsley | Apr 2015 | B2 |
| 9009072 | Durham | Apr 2015 | B2 |
| 9014902 | Murphy | Apr 2015 | B1 |
| 9020679 | Spencer | Apr 2015 | B2 |
| 9026301 | Spencer | May 2015 | B2 |
| 9043016 | Schmaltz | May 2015 | B2 |
| 9046893 | Douglas | Jun 2015 | B2 |
| 9051120 | Toebes | Jun 2015 | B2 |
| 9052714 | Creasey | Jun 2015 | B2 |
| 9056719 | Tanahashi | Jun 2015 | B2 |
| 9067317 | Wurman | Jun 2015 | B1 |
| 9073736 | Goyal | Jul 2015 | B1 |
| 9082293 | Wellman | Jul 2015 | B2 |
| 9087314 | D Andrea | Jul 2015 | B2 |
| 9090214 | Wilson | Jul 2015 | B2 |
| 9090400 | Barbehenn | Jul 2015 | B2 |
| 9096375 | Lert et al. | Aug 2015 | B2 |
| 9098080 | Norris et al. | Aug 2015 | B2 |
| 9110464 | Holland et al. | Aug 2015 | B2 |
| 9111251 | Brazeau | Aug 2015 | B1 |
| 9114838 | Bernstein et al. | Aug 2015 | B2 |
| 9120621 | Curlander et al. | Sep 2015 | B1 |
| 9120622 | Elazary et al. | Sep 2015 | B1 |
| 9122276 | Kraimer et al. | Sep 2015 | B2 |
| 9129250 | Sestini et al. | Sep 2015 | B1 |
| 9134734 | Lipkowski et al. | Sep 2015 | B2 |
| 9146559 | Kuss et al. | Sep 2015 | B2 |
| 9147173 | Jones et al. | Sep 2015 | B2 |
| 9150263 | Bernstein et al. | Oct 2015 | B2 |
| 9152149 | Palamarchuk et al. | Oct 2015 | B1 |
| 9185998 | Dwarakanath et al. | Nov 2015 | B1 |
| 9188982 | Thomson | Nov 2015 | B2 |
| 9193404 | Bernstein et al. | Nov 2015 | B2 |
| 9202382 | Klinger et al. | Dec 2015 | B2 |
| 9206023 | Wong et al. | Dec 2015 | B2 |
| 9207673 | Pulskamp et al. | Dec 2015 | B2 |
| 9207676 | Wu et al. | Dec 2015 | B2 |
| 9211920 | Bernstein et al. | Dec 2015 | B1 |
| 9213934 | Versteeg et al. | Dec 2015 | B1 |
| 9216745 | Beardsley et al. | Dec 2015 | B2 |
| 9218003 | Fong et al. | Dec 2015 | B2 |
| 9218316 | Bernstein et al. | Dec 2015 | B2 |
| 9242799 | O'Brien et al. | Jan 2016 | B1 |
| 9244463 | Pfaff et al. | Jan 2016 | B2 |
| 9248973 | Brazeau | Feb 2016 | B1 |
| 9260244 | Cohn | Feb 2016 | B1 |
| 9266236 | Clark et al. | Feb 2016 | B2 |
| 9268334 | Vavrick | Feb 2016 | B1 |
| 9274526 | Murai et al. | Mar 2016 | B2 |
| 9280153 | Palamarchuk et al. | Mar 2016 | B1 |
| 9280157 | Wurman et al. | Mar 2016 | B2 |
| 9286590 | Segawa et al. | Mar 2016 | B2 |
| 9290220 | Bernstein et al. | Mar 2016 | B2 |
| 9304001 | Park et al. | Apr 2016 | B2 |
| 9310802 | Elkins et al. | Apr 2016 | B1 |
| 9317034 | Hoffman et al. | Apr 2016 | B2 |
| 9329078 | Mundhenke et al. | May 2016 | B1 |
| 9329599 | Sun et al. | May 2016 | B1 |
| 9330373 | Mountz et al. | May 2016 | B2 |
| 9341720 | Garin et al. | May 2016 | B2 |
| 9342811 | Mountz et al. | May 2016 | B2 |
| 9346619 | O'Brien et al. | May 2016 | B1 |
| 9346620 | Brunner et al. | May 2016 | B2 |
| 9352745 | Theobald | May 2016 | B1 |
| 9355065 | Donahue | May 2016 | B2 |
| 9365348 | Agarwal et al. | Jun 2016 | B1 |
| 9367827 | Lively et al. | Jun 2016 | B1 |
| 9367831 | Besehanic | Jun 2016 | B1 |
| 9371184 | Dingle et al. | Jun 2016 | B1 |
| 9378482 | Pikler et al. | Jun 2016 | B1 |
| 9389609 | Mountz et al. | Jul 2016 | B1 |
| 9389612 | Bernstein et al. | Jul 2016 | B2 |
| 9389614 | Shani | Jul 2016 | B2 |
| 9394016 | Bernstein et al. | Jul 2016 | B2 |
| 9395725 | Bernstein et al. | Jul 2016 | B2 |
| 9404756 | Fong et al. | Aug 2016 | B2 |
| 9405016 | Yim | Aug 2016 | B2 |
| 9427874 | Rublee | Aug 2016 | B1 |
| 9429940 | Bernstein et al. | Aug 2016 | B2 |
| 9429944 | Filippov et al. | Aug 2016 | B2 |
| 9436184 | D'Andrea et al. | Sep 2016 | B2 |
| 9440790 | Mountz et al. | Sep 2016 | B2 |
| 9448560 | D'Andrea et al. | Sep 2016 | B2 |
| 9451020 | Liu et al. | Sep 2016 | B2 |
| 9452883 | Wurman et al. | Sep 2016 | B1 |
| 9457730 | Bernstein et al. | Oct 2016 | B2 |
| 9463927 | Theobald | Oct 2016 | B1 |
| 9469477 | Palamarchuk et al. | Oct 2016 | B1 |
| 9471894 | Palamarchuk et al. | Oct 2016 | B2 |
| 9481410 | Bernstein et al. | Nov 2016 | B2 |
| 9493184 | Castaneda et al. | Nov 2016 | B2 |
| 9493303 | Wurman et al. | Nov 2016 | B2 |
| 9495656 | Adler et al. | Nov 2016 | B2 |
| 9501756 | Stevens et al. | Nov 2016 | B2 |
| 9511934 | Wurman et al. | Dec 2016 | B2 |
| 9517899 | Watt et al. | Dec 2016 | B2 |
| 9519284 | Wurman et al. | Dec 2016 | B2 |
| 9519880 | Cohn | Dec 2016 | B1 |
| 9522817 | Castaneda et al. | Dec 2016 | B2 |
| 9523582 | Chandrasekar et al. | Dec 2016 | B2 |
| 9527710 | Hussain et al. | Dec 2016 | B1 |
| 9533828 | Dwarakanath et al. | Jan 2017 | B1 |
| 9536767 | Adler et al. | Jan 2017 | B1 |
| 9540171 | Elazary et al. | Jan 2017 | B2 |
| 9547945 | McCabe et al. | Jan 2017 | B2 |
| 9551987 | Mountz et al. | Jan 2017 | B1 |
| 9563206 | Zini et al. | Feb 2017 | B2 |
| 9568917 | Jones et al. | Feb 2017 | B2 |
| 9582783 | Mountz et al. | Feb 2017 | B2 |
| 9592961 | Weiss | Mar 2017 | B2 |
| 9645968 | Elston et al. | May 2017 | B2 |
| 9663295 | Wurman et al. | May 2017 | B1 |
| 9663296 | Dingle et al. | May 2017 | B1 |
| 9676552 | Agarwal et al. | Jun 2017 | B2 |
| 9679270 | Zini et al. | Jun 2017 | B2 |
| 9694975 | Lert et al. | Jul 2017 | B2 |
| 9694976 | Wurman et al. | Jul 2017 | B1 |
| 9725239 | Lert et al. | Aug 2017 | B2 |
| 9731896 | Elazary et al. | Aug 2017 | B2 |
| 9738449 | Palamarchuk et al. | Aug 2017 | B1 |
| 9740212 | D'Andrea et al. | Aug 2017 | B2 |
| 9766620 | Bernstein et al. | Sep 2017 | B2 |
| 9771217 | Lert et al. | Sep 2017 | B2 |
| 9783364 | Worsley | Oct 2017 | B2 |
| 9785152 | Chandrasekar et al. | Oct 2017 | B2 |
| 9792577 | Mountz et al. | Oct 2017 | B2 |
| 9796529 | Hoareau et al. | Oct 2017 | B1 |
| 9802762 | Pikler et al. | Oct 2017 | B1 |
| 9836046 | Wilson et al. | Dec 2017 | B2 |
| 9841758 | Bernstein et al. | Dec 2017 | B2 |
| 9856084 | Palamarchuk et al. | Jan 2018 | B1 |
| 9873561 | Agarwal et al. | Jan 2018 | B2 |
| 20010018637 | Hamilton | Aug 2001 | A1 |
| 20010027360 | Nakano | Oct 2001 | A1 |
| 20020021954 | Winkler | Feb 2002 | A1 |
| 20020027652 | Paromtchik et al. | Mar 2002 | A1 |
| 20020074172 | Sugiyama et al. | Jun 2002 | A1 |
| 20020165648 | Zeitler | Nov 2002 | A1 |
| 20030046021 | Lasky et al. | Mar 2003 | A1 |
| 20030106731 | Marino et al. | Jun 2003 | A1 |
| 20030208304 | Peless et al. | Nov 2003 | A1 |
| 20040006415 | Kang | Jan 2004 | A1 |
| 20040006416 | Jeong | Jan 2004 | A1 |
| 20040010337 | Mountz | Jan 2004 | A1 |
| 20040010339 | Mountz | Jan 2004 | A1 |
| 20040024489 | Fujiki et al. | Feb 2004 | A1 |
| 20040062419 | Roh et al. | Apr 2004 | A1 |
| 20040093116 | Mountz | May 2004 | A1 |
| 20040243278 | Leishman | Dec 2004 | A1 |
| 20050065655 | Hong et al. | Mar 2005 | A1 |
| 20050080524 | Park | Apr 2005 | A1 |
| 20050113990 | Peless et al. | May 2005 | A1 |
| 20050222722 | Chen | Oct 2005 | A1 |
| 20050228555 | Roh et al. | Oct 2005 | A1 |
| 20050244259 | Chilson et al. | Nov 2005 | A1 |
| 20060071790 | Duron | Apr 2006 | A1 |
| 20060149465 | Park et al. | Jul 2006 | A1 |
| 20060184013 | Emanuel et al. | Aug 2006 | A1 |
| 20060210382 | Mountz et al. | Sep 2006 | A1 |
| 20060245893 | Schottke | Nov 2006 | A1 |
| 20060255948 | Runyon et al. | Nov 2006 | A1 |
| 20060255949 | Roeder et al. | Nov 2006 | A1 |
| 20060255950 | Roeder et al. | Nov 2006 | A1 |
| 20060255951 | Roeder et al. | Nov 2006 | A1 |
| 20060255954 | Sorenson, Jr. et al. | Nov 2006 | A1 |
| 20060271274 | Saarikivi | Nov 2006 | A1 |
| 20060280585 | Passeri et al. | Dec 2006 | A1 |
| 20070017984 | Mountz et al. | Jan 2007 | A1 |
| 20070021863 | Mountz et al. | Jan 2007 | A1 |
| 20070021864 | Mountz et al. | Jan 2007 | A1 |
| 20070096922 | Sorenson, Jr. et al. | May 2007 | A1 |
| 20070112461 | Zini et al. | May 2007 | A1 |
| 20070112463 | Roh et al. | May 2007 | A1 |
| 20070123308 | Kim et al. | May 2007 | A1 |
| 20070129849 | Zini et al. | Jun 2007 | A1 |
| 20070136152 | Dunsker et al. | Jun 2007 | A1 |
| 20070150109 | Peless et al. | Jun 2007 | A1 |
| 20070152057 | Cato et al. | Jul 2007 | A1 |
| 20070152845 | Porte et al. | Jul 2007 | A1 |
| 20070179690 | Stewart | Aug 2007 | A1 |
| 20070193798 | Allard et al. | Aug 2007 | A1 |
| 20070198144 | Norris et al. | Aug 2007 | A1 |
| 20070198145 | Norris et al. | Aug 2007 | A1 |
| 20070198174 | Williams et al. | Aug 2007 | A1 |
| 20070198175 | Williams et al. | Aug 2007 | A1 |
| 20070198282 | Williams et al. | Aug 2007 | A1 |
| 20070208477 | Baginski et al. | Sep 2007 | A1 |
| 20070219666 | Filippov et al. | Sep 2007 | A1 |
| 20070269299 | Ross et al. | Nov 2007 | A1 |
| 20070288123 | D'Andrea et al. | Dec 2007 | A1 |
| 20070290040 | Wurman et al. | Dec 2007 | A1 |
| 20070293978 | Wurman et al. | Dec 2007 | A1 |
| 20070294029 | D'Andrea et al. | Dec 2007 | A1 |
| 20070297879 | Yuyama et al. | Dec 2007 | A1 |
| 20080001372 | Hoffman et al. | Jan 2008 | A1 |
| 20080051984 | Wurman et al. | Feb 2008 | A1 |
| 20080051985 | D'Andrea et al. | Feb 2008 | A1 |
| 20080071429 | Kraimer et al. | Mar 2008 | A1 |
| 20080077511 | Zimmerman | Mar 2008 | A1 |
| 20080129445 | Kraimer et al. | Jun 2008 | A1 |
| 20080157972 | Duron et al. | Jul 2008 | A1 |
| 20080166217 | Fontana | Jul 2008 | A1 |
| 20080167753 | Peless et al. | Jul 2008 | A1 |
| 20080167884 | Mountz et al. | Jul 2008 | A1 |
| 20080167933 | Hoffman et al. | Jul 2008 | A1 |
| 20080189005 | Chilson et al. | Aug 2008 | A1 |
| 20080199298 | Chilson et al. | Aug 2008 | A1 |
| 20090099716 | Roh et al. | Apr 2009 | A1 |
| 20090138151 | Smid et al. | May 2009 | A1 |
| 20090185884 | Wurman et al. | Jul 2009 | A1 |
| 20090198376 | Friedman et al. | Aug 2009 | A1 |
| 20090198381 | Friedman et al. | Aug 2009 | A1 |
| 20090234499 | Nielsen et al. | Sep 2009 | A1 |
| 20100039293 | Porte et al. | Feb 2010 | A1 |
| 20100114405 | Elston et al. | May 2010 | A1 |
| 20100127883 | Chou | May 2010 | A1 |
| 20100138095 | Redmann, Jr. et al. | Jun 2010 | A1 |
| 20100141483 | Thacher et al. | Jun 2010 | A1 |
| 20100145551 | Pulskamp et al. | Jun 2010 | A1 |
| 20100234990 | Zini et al. | Sep 2010 | A1 |
| 20100234991 | Zini et al. | Sep 2010 | A1 |
| 20100266381 | Chilson et al. | Oct 2010 | A1 |
| 20100300841 | O'Brien | Dec 2010 | A1 |
| 20100309841 | Conte | Dec 2010 | A1 |
| 20100316468 | Lert et al. | Dec 2010 | A1 |
| 20100316469 | Lert et al. | Dec 2010 | A1 |
| 20100316470 | Lert et al. | Dec 2010 | A1 |
| 20100322746 | Lert et al. | Dec 2010 | A1 |
| 20100322747 | Lert et al. | Dec 2010 | A1 |
| 20110010023 | Kunzig et al. | Jan 2011 | A1 |
| 20110015779 | D'Andrea et al. | Jan 2011 | A1 |
| 20110046813 | Castaneda et al. | Feb 2011 | A1 |
| 20110056760 | Schendel et al. | Mar 2011 | A1 |
| 20110060449 | Wurman et al. | Mar 2011 | A1 |
| 20110066284 | Curtis | Mar 2011 | A1 |
| 20110071718 | Norris et al. | Mar 2011 | A1 |
| 20110103924 | Watt et al. | May 2011 | A1 |
| 20110112758 | D'Andrea et al. | May 2011 | A1 |
| 20110118903 | Kraimer et al. | May 2011 | A1 |
| 20110121068 | Emanuel et al. | May 2011 | A1 |
| 20110125312 | D'Andrea et al. | May 2011 | A1 |
| 20110130866 | D'Andrea et al. | Jun 2011 | A1 |
| 20110130954 | D'Andrea et al. | Jun 2011 | A1 |
| 20110137457 | Zini et al. | Jun 2011 | A1 |
| 20110153063 | Wurman et al. | Jun 2011 | A1 |
| 20110160949 | Kondo | Jun 2011 | A1 |
| 20110163160 | Zini et al. | Jul 2011 | A1 |
| 20110166721 | Castaneda et al. | Jul 2011 | A1 |
| 20110166737 | Tanaka et al. | Jul 2011 | A1 |
| 20110191135 | Williams et al. | Aug 2011 | A1 |
| 20110208745 | Dietsch et al. | Aug 2011 | A1 |
| 20110270438 | Shimamura | Nov 2011 | A1 |
| 20120038455 | Kraimer et al. | Feb 2012 | A1 |
| 20120041677 | D'Andrea et al. | Feb 2012 | A1 |
| 20120046820 | Allard et al. | Feb 2012 | A1 |
| 20120078471 | Siefring et al. | Mar 2012 | A1 |
| 20120139715 | Yamazato | Jun 2012 | A1 |
| 20120143427 | Hoffman et al. | Jun 2012 | A1 |
| 20120168240 | Wilson et al. | Jul 2012 | A1 |
| 20120168241 | Bernstein et al. | Jul 2012 | A1 |
| 20120173047 | Bernstein et al. | Jul 2012 | A1 |
| 20120173048 | Bernstein et al. | Jul 2012 | A1 |
| 20120173049 | Bernstein et al. | Jul 2012 | A1 |
| 20120173050 | Bernstein et al. | Jul 2012 | A1 |
| 20120176222 | Baek et al. | Jul 2012 | A1 |
| 20120176491 | Garin et al. | Jul 2012 | A1 |
| 20120197477 | Colwell | Aug 2012 | A1 |
| 20120232739 | Takahashi et al. | Sep 2012 | A1 |
| 20120239191 | Versteeg et al. | Sep 2012 | A1 |
| 20120239224 | McCabe et al. | Sep 2012 | A1 |
| 20120239238 | Harvey et al. | Sep 2012 | A1 |
| 20120255810 | Yang | Oct 2012 | A1 |
| 20120282070 | D'Andrea et al. | Nov 2012 | A1 |
| 20120321423 | MacKnight et al. | Dec 2012 | A1 |
| 20120323746 | Mountz et al. | Dec 2012 | A1 |
| 20120330458 | Weiss | Dec 2012 | A1 |
| 20120330492 | Douglas et al. | Dec 2012 | A1 |
| 20130006442 | Williams et al. | Jan 2013 | A1 |
| 20130054005 | Stevens et al. | Feb 2013 | A1 |
| 20130058743 | Rebstock | Mar 2013 | A1 |
| 20130103185 | Wurman et al. | Apr 2013 | A1 |
| 20130103552 | Hoffman et al. | Apr 2013 | A1 |
| 20130105570 | Dunsker et al. | May 2013 | A1 |
| 20130110279 | Dunsker et al. | May 2013 | A1 |
| 20130110281 | Jones et al. | May 2013 | A1 |
| 20130124013 | Elston et al. | May 2013 | A1 |
| 20130124014 | Elston et al. | May 2013 | A1 |
| 20130131895 | Elston et al. | May 2013 | A1 |
| 20130131910 | Takahashi et al. | May 2013 | A1 |
| 20130158773 | Wu et al. | Jun 2013 | A1 |
| 20130166108 | Sturm | Jun 2013 | A1 |
| 20130173049 | Brunner et al. | Jul 2013 | A1 |
| 20130173089 | Bernstein et al. | Jul 2013 | A1 |
| 20130190963 | Kuss et al. | Jul 2013 | A1 |
| 20130197720 | Kraimer et al. | Aug 2013 | A1 |
| 20130197760 | Castaneda et al. | Aug 2013 | A1 |
| 20130204429 | D'Andrea et al. | Aug 2013 | A1 |
| 20130204480 | D'Andrea et al. | Aug 2013 | A1 |
| 20130211626 | Nagasawa | Aug 2013 | A1 |
| 20130238170 | Klinger | Sep 2013 | A1 |
| 20130246229 | Mountz et al. | Sep 2013 | A1 |
| 20130251480 | Watt et al. | Sep 2013 | A1 |
| 20130275045 | Tsujimoto et al. | Oct 2013 | A1 |
| 20130282222 | Ozaki et al. | Oct 2013 | A1 |
| 20130297151 | Castaneda et al. | Nov 2013 | A1 |
| 20130302132 | D'Andrea et al. | Nov 2013 | A1 |
| 20130304253 | Wurman et al. | Nov 2013 | A1 |
| 20130312371 | Ambrose | Nov 2013 | A1 |
| 20130325243 | Lipkowski et al. | Dec 2013 | A1 |
| 20130338874 | Donahue | Dec 2013 | A1 |
| 20130338885 | Kirk et al. | Dec 2013 | A1 |
| 20130338886 | Callea et al. | Dec 2013 | A1 |
| 20140005933 | Fong et al. | Jan 2014 | A1 |
| 20140020964 | Bernstein et al. | Jan 2014 | A1 |
| 20140032035 | Thomson | Jan 2014 | A1 |
| 20140067184 | Murphy | Mar 2014 | A1 |
| 20140072392 | Tanahashi | Mar 2014 | A1 |
| 20140081505 | Klinger et al. | Mar 2014 | A1 |
| 20140088758 | Lert et al. | Mar 2014 | A1 |
| 20140100690 | Wurman et al. | Apr 2014 | A1 |
| 20140100715 | Mountz et al. | Apr 2014 | A1 |
| 20140100998 | Mountz et al. | Apr 2014 | A1 |
| 20140100999 | Mountz et al. | Apr 2014 | A1 |
| 20140107833 | Segawa et al. | Apr 2014 | A1 |
| 20140124462 | Yamashita | May 2014 | A1 |
| 20140135977 | Wurman et al. | May 2014 | A1 |
| 20140172223 | Murphy | Jun 2014 | A1 |
| 20140188671 | Mountz et al. | Jul 2014 | A1 |
| 20140195040 | Wurman et al. | Jul 2014 | A1 |
| 20140195121 | Castaneda et al. | Jul 2014 | A1 |
| 20140214195 | Worsley | Jul 2014 | A1 |
| 20140214196 | Worsley | Jul 2014 | A1 |
| 20140214234 | Worsley | Jul 2014 | A1 |
| 20140228999 | D'Andrea et al. | Aug 2014 | A1 |
| 20140236393 | Bernstein et al. | Aug 2014 | A1 |
| 20140236413 | D'Andrea et al. | Aug 2014 | A1 |
| 20140238762 | Berberian et al. | Aug 2014 | A1 |
| 20140244097 | Colwell | Aug 2014 | A1 |
| 20140271063 | Lert et al. | Sep 2014 | A1 |
| 20140277691 | Jacobus et al. | Sep 2014 | A1 |
| 20140297093 | Murai et al. | Oct 2014 | A1 |
| 20140303773 | Wurman et al. | Oct 2014 | A1 |
| 20140330425 | Stevens et al. | Nov 2014 | A1 |
| 20140330426 | Brunner et al. | Nov 2014 | A1 |
| 20140343714 | Clark et al. | Nov 2014 | A1 |
| 20140343758 | Kraimer et al. | Nov 2014 | A1 |
| 20140345957 | Bernstein et al. | Nov 2014 | A1 |
| 20140350768 | Filippov et al. | Nov 2014 | A1 |
| 20140350831 | Hoffman et al. | Nov 2014 | A1 |
| 20140371973 | Pfaff et al. | Dec 2014 | A1 |
| 20150012209 | Park et al. | Jan 2015 | A1 |
| 20150019043 | Creasey et al. | Jan 2015 | A1 |
| 20150022400 | Smid et al. | Jan 2015 | A1 |
| 20150025713 | Klinger et al. | Jan 2015 | A1 |
| 20150057843 | Kraimer et al. | Feb 2015 | A1 |
| 20150066283 | Wurman et al. | Mar 2015 | A1 |
| 20150073586 | Weiss | Mar 2015 | A1 |
| 20150073589 | Khodl et al. | Mar 2015 | A1 |
| 20150088302 | Mountz et al. | Mar 2015 | A1 |
| 20150117995 | D'Andrea et al. | Apr 2015 | A1 |
| 20150142168 | Holland et al. | May 2015 | A1 |
| 20150151912 | Mountz et al. | Jun 2015 | A1 |
| 20150183581 | Worsley | Jul 2015 | A1 |
| 20150224941 | Bernstein et al. | Aug 2015 | A1 |
| 20150226560 | Chandrasekar et al. | Aug 2015 | A1 |
| 20150226561 | Chandrasekar et al. | Aug 2015 | A1 |
| 20150227862 | Chandrasekar et al. | Aug 2015 | A1 |
| 20150227885 | Zini et al. | Aug 2015 | A1 |
| 20150234386 | Zini et al. | Aug 2015 | A1 |
| 20150261223 | Fong et al. | Sep 2015 | A1 |
| 20150266672 | Lert et al. | Sep 2015 | A1 |
| 20150284010 | Beardsley et al. | Oct 2015 | A1 |
| 20150286218 | Shani | Oct 2015 | A1 |
| 20150301532 | Norris et al. | Oct 2015 | A1 |
| 20150307278 | Wickham et al. | Oct 2015 | A1 |
| 20150344085 | Bernstein et al. | Dec 2015 | A1 |
| 20150355639 | Versteeg et al. | Dec 2015 | A1 |
| 20150362919 | Bernstein et al. | Dec 2015 | A1 |
| 20150370257 | Bernstein et al. | Dec 2015 | A1 |
| 20150371181 | Palamarchuk et al. | Dec 2015 | A1 |
| 20160004253 | Bernstein et al. | Jan 2016 | A1 |
| 20160021178 | Liu et al. | Jan 2016 | A1 |
| 20160033967 | Bernstein et al. | Feb 2016 | A1 |
| 20160033971 | Thomson | Feb 2016 | A1 |
| 20160042314 | Mountz et al. | Feb 2016 | A1 |
| 20160048130 | Vavrick | Feb 2016 | A1 |
| 20160054734 | Bernstein et al. | Feb 2016 | A1 |
| 20160069691 | Fong | Mar 2016 | A1 |
| 20160090133 | Bernstein et al. | Mar 2016 | A1 |
| 20160097862 | Yim | Apr 2016 | A1 |
| 20160101741 | Bernstein et al. | Apr 2016 | A1 |
| 20160101937 | Adler et al. | Apr 2016 | A1 |
| 20160103014 | Mundhenke et al. | Apr 2016 | A1 |
| 20160117936 | Klinger et al. | Apr 2016 | A1 |
| 20160147231 | Sun et al. | May 2016 | A1 |
| 20160171441 | Lively et al. | Jun 2016 | A1 |
| 20160176637 | Ackerman et al. | Jun 2016 | A1 |
| 20160185526 | Lert et al. | Jun 2016 | A1 |
| 20160187886 | Jones et al. | Jun 2016 | A1 |
| 20160202696 | Bernstein et al. | Jul 2016 | A1 |
| 20160203543 | Snow | Jul 2016 | A1 |
| 20160232477 | Cortes et al. | Aug 2016 | A1 |
| 20160232490 | Mountz et al. | Aug 2016 | A1 |
| 20160246299 | Berberian et al. | Aug 2016 | A1 |
| 20160264357 | Agarwal et al. | Sep 2016 | A1 |
| 20160282871 | Bernstein et al. | Sep 2016 | A1 |
| 20160291591 | Bernstein et al. | Oct 2016 | A1 |
| 20160304280 | Elazary et al. | Oct 2016 | A1 |
| 20160304281 | Elazary et al. | Oct 2016 | A1 |
| 20160334799 | D'Andrea et al. | Nov 2016 | A1 |
| 20160339587 | Rublee | Nov 2016 | A1 |
| 20160347545 | Lindbo et al. | Dec 2016 | A1 |
| 20160349748 | Bernstein et al. | Dec 2016 | A1 |
| 20160379161 | Adler et al. | Dec 2016 | A1 |
| 20170011336 | Stevens et al. | Jan 2017 | A1 |
| 20170022010 | D'Andrea et al. | Jan 2017 | A1 |
| 20170038770 | Wurman et al. | Feb 2017 | A1 |
| 20170043953 | Battles et al. | Feb 2017 | A1 |
| 20170052033 | Fong et al. | Feb 2017 | A1 |
| 20170057798 | Dues et al. | Mar 2017 | A1 |
| 20170060138 | Chandrasekar et al. | Mar 2017 | A1 |
| 20170080352 | Bernstein et al. | Mar 2017 | A1 |
| 20170174431 | Borders et al. | Jun 2017 | A1 |
| 20170183005 | Elston et al. | Jun 2017 | A1 |
| 20170183159 | Weiss | Jun 2017 | A1 |
| 20170269608 | Chandrasekar et al. | Sep 2017 | A1 |
| 20170286908 | Lively et al. | Oct 2017 | A1 |
| 20170313517 | Agarwal et al. | Nov 2017 | A1 |
| 20170362032 | Sullivan et al. | Dec 2017 | A1 |
| 20180016098 | Lert et al. | Jan 2018 | A1 |
| 20190033837 | Zanger et al. | Jan 2019 | A1 |
| 20200207546 | Borders | Jul 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 1196712 | Nov 1985 | CA |
| 1210367 | Aug 1986 | CA |
| 1228142 | Oct 1987 | CA |
| 1238103 | Jun 1988 | CA |
| 1264490 | Jan 1990 | CA |
| 1267866 | Apr 1990 | CA |
| 1269740 | May 1990 | CA |
| 1271544 | Jul 1990 | CA |
| 1275721 | Oct 1990 | CA |
| 1276264 | Nov 1990 | CA |
| 2029773 | May 1991 | CA |
| 1291725 | Nov 1991 | CA |
| 2036104 | Nov 1991 | CA |
| 2042133 | Jan 1992 | CA |
| 2049578 | Feb 1992 | CA |
| 2296837 | Feb 1992 | CA |
| 2094833 | Apr 1992 | CA |
| 1304043 | Jun 1992 | CA |
| 2095442 | Jun 1992 | CA |
| 1304820 | Jul 1992 | CA |
| 1323084 | Oct 1993 | CA |
| 2189853 | Nov 1995 | CA |
| 2244668 | Mar 1999 | CA |
| 2469652 | Jun 2003 | CA |
| 2514523 | Aug 2004 | CA |
| 2565553 | Nov 2005 | CA |
| 2577346 | Apr 2006 | CA |
| 2613180 | Jan 2007 | CA |
| 2921584 | Jan 2007 | CA |
| 2625885 | Apr 2007 | CA |
| 2625895 | Apr 2007 | CA |
| 2837477 | Apr 2007 | CA |
| 2864027 | Apr 2007 | CA |
| 2636233 | Jul 2007 | CA |
| 2640769 | Aug 2007 | CA |
| 2652114 | Dec 2007 | CA |
| 2654258 | Dec 2007 | CA |
| 2654260 | Dec 2007 | CA |
| 2654263 | Dec 2007 | CA |
| 2654295 | Dec 2007 | CA |
| 2654336 | Dec 2007 | CA |
| 2654471 | Dec 2007 | CA |
| 2748398 | Dec 2007 | CA |
| 2748407 | Dec 2007 | CA |
| 2750043 | Dec 2007 | CA |
| 2781624 | Dec 2007 | CA |
| 2781857 | Dec 2007 | CA |
| 2838044 | Dec 2007 | CA |
| 2866664 | Dec 2007 | CA |
| 2921134 | Dec 2007 | CA |
| 2663578 | Apr 2008 | CA |
| 2860745 | Apr 2008 | CA |
| 2671955 | Jul 2008 | CA |
| 2673025 | Jul 2008 | CA |
| 2674241 | Jul 2008 | CA |
| 2691710 | Dec 2008 | CA |
| 2721345 | Oct 2009 | CA |
| 2760127 | Nov 2009 | CA |
| 2760225 | Nov 2009 | CA |
| 2743706 | Jun 2010 | CA |
| 2754626 | Sep 2010 | CA |
| 2765565 | Jan 2011 | CA |
| 2932535 | Jan 2011 | CA |
| 2932537 | Jan 2011 | CA |
| 2770139 | Feb 2011 | CA |
| 2773963 | Mar 2011 | CA |
| 2778111 | May 2011 | CA |
| 2784874 | Jul 2011 | CA |
| 2868578 | Jul 2011 | CA |
| 2806852 | Feb 2012 | CA |
| 2823715 | Jul 2012 | CA |
| 2827281 | Aug 2012 | CA |
| 2827735 | Aug 2012 | CA |
| 2770715 | Sep 2012 | CA |
| 2770918 | Sep 2012 | CA |
| 2831832 | Oct 2012 | CA |
| 2836933 | Dec 2012 | CA |
| 2851774 | Apr 2013 | CA |
| 2799871 | Jun 2013 | CA |
| 2866708 | Sep 2013 | CA |
| 2938894 | Sep 2013 | CA |
| 2813874 | Dec 2013 | CA |
| 2824189 | Feb 2014 | CA |
| 2870381 | Apr 2014 | CA |
| 2935223 | Apr 2014 | CA |
| 2894546 | Jun 2014 | CA |
| 2845229 | Sep 2014 | CA |
| 2899553 | Oct 2014 | CA |
| 2882452 | Aug 2015 | CA |
| 2886121 | Oct 2015 | CA |
| 2012154872 | Nov 2012 | WO |
| 2016015000 | Jan 2016 | WO |
| Entry |
|---|
| US 9,342,073 B2, 05/2016, Bernstein et al. (withdrawn) |
| US 9,791,858 B2, 10/2017, Wilson et al. (withdrawn) |
| European Search Report and Search Opinion Received for EP Application No. 17857594, dated Apr. 1, 2020, 9 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US17/54627, dated Apr. 11, 2019, 9 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US18/12641, dated Jul. 18, 2019, 10 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US18/12645, dated Jul. 18, 2019, 11 pages. |
| International Search Report and Written Opinion, PCT/US2017/054627, dated Jan. 5, 2018 (15 pages). |
| International Search Report and Written Opinion, PCT/US2018/012645, dated Mar. 7, 2018 (13 pages). |
| International Search Report and Written Opinion, PCT/US2018/012641, dated Mar. 7, 2018 (17 pages). |
| Warehouse Robots at Work, IEEE Spectrum,. Jul. 21, 2008, YouTube https://www.youtube.com/watch?v=lWsMdN7HMuA. |
| Number | Date | Country | |
|---|---|---|---|
| 20210009352 A1 | Jan 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62442891 | Jan 2017 | US | |
| 62403001 | Sep 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15863017 | Jan 2018 | US |
| Child | 16902030 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15721472 | Sep 2017 | US |
| Child | 15863017 | US |
