KR20210061233A - Computer implemented systems and methods for efficient distribution of orders based on system parameters - Google Patents

Abstract

Disclosed is a computer-implemented system for efficient distribution of orders based on system parameters. The system includes: a memory storing instructions; and at least one processor configured to execute the instructions. The instructions may comprise: aggregating one or more orders comprising one or more quantities of a plurality of items; assigning a subset of the items to a batch, wherein the items are assigned to one or more batches; determining one or more parameters of a transporting system for the batches; determining at least one of location or orientation of the items in the transporting system based on the parameters of the transporting system; and transmitting, to a user device for display, the parameters of the transporting system.

Description

A computer-implemented system and method for efficiently distributing orders based on system parameters TECHNICAL FIELD [COMPUTER IMPLEMENTED SYSTEMS AND METHODS FOR EFFICIENT DISTRIBUTION OF ORDERS BASED ON SYSTEM PARAMETERS]

The present invention relates generally to a computerized method and system for distributing customer orders based on system configuration and limitations. In particular, embodiments of the present disclosure relate to a unique and unique system that finds and decomposes a set of orders into individual items that need to be retrieved while taking into account limitations such as the system configuration such as the location of items and the weight limit of the transport system. will be.

With the proliferation of the Internet, online shopping has become one of the main means of commerce. Consumers and businesses are buying products from online vendors more often than ever before, and the number of transactions and sales revenue is expected to grow at a tremendous rate each year. As the scope and scale of e-commerce continues to grow, both the number of different products available online and the average number of purchases made over a given period are increasing exponentially. Therefore, it becomes very important to optimize the process of fulfilling orders, starting when a customer places an order and ending when the order is delivered to the customer.

Among various processes related to finding and fetching items included in an order, packaging items, and shipping items, various solutions for finding items already exist to make the process more efficient. However, the existing solution is fundamental in that it controls the retrieving task for each order. That is, under the existing solution, no matter where the items are located in the warehouse, workers are assigned to orders, finding all the items in each order and looking for the items until they have finished fetching. Given the myriad of items and the general size of a large warehouse, existing solutions may not make the most of the worker's time and effort. This is especially true when the different items in the order are far from the warehouse. Also, if, for example, a conveyor belt may have certain weight limitations, the operator in an existing solution may not be aware of certain limitations of the overall system. Since these limits must be calculated based on all products in transit at any given time, it is almost impossible for individual operators to take these limitations into account, and current systems cannot take these limitations into account.

Accordingly, there is a need for improved systems and methods for managing orders in a controlled manner and allocating the orders to workers in order to process orders in an efficient manner.

One aspect of the present disclosure relates to a computer implemented system for efficiently distributing orders based on system parameters. The system includes a memory for storing instructions; And at least one processor configured to execute corresponding instructions. The instructions aggregate one or more orders containing a plurality of items of one or more quantities; Allocating a subset of items to a batch, where items are assigned to one or more batches; Determine one or more parameters of the transport system for batches; Determine at least one of a location or orientation of items in the transportation system based on the parameters of the transportation system; And for display, transmitting parameters of the transportation system to the user device.

Another aspect of the present disclosure relates to a computer-implemented method for efficiently distributing orders based on system parameters. The method includes aggregating one or more orders comprising a plurality of items of one or more quantities; Allocating a subset of items to a batch, the items being assigned to one or more batches; Determining one or more parameters of the transportation system for batches; Determining at least one of a location or orientation of items in the transportation system based on the parameters of the transportation system; And transmitting parameters of the transportation system to the user device for display.

Further, another aspect of the present disclosure relates to a computer implemented system for efficiently distributing orders based on system parameters. The system includes a memory for storing instructions; And at least one processor configured to execute instructions. The instructions aggregate one or more orders containing a plurality of items of one or more quantities; Allocating a first subset of items to a first batch, the items being allocated to one or more batches; Determine one or more parameters of the transport system for the first batch; Determine at least one of a location or orientation of the first set of items in the transportation system based on the parameters of the transportation system; Transmit the parameters of the transportation system to the user device for display; Receive from the user device a first item identifier associated with a first item of the first subset of items; And transmitting at least one of the location or direction of the first item placed in the transportation system to the user device to display in response to the first item identifier.

Other systems, methods, and computer-readable media are also discussed herein.

1A is a schematic block diagram illustrating an exemplary embodiment of a network including a computer system for communication enabling delivery, transportation, and logistics operations, in accordance with the disclosed embodiments.
FIG. 1B is a diagram illustrating a sample of a search result page (SRP) including one or more search results that satisfy a search request according to an interactive user interface element according to the disclosed embodiment.
1C is a diagram illustrating a sample of a single display page (SDP) containing information about products and products according to interactive user interface elements, according to the disclosed embodiment.
FIG. 1D is a diagram illustrating a sample shopping cart page including an item in a virtual shopping cart according to an interactive user interface element, according to the disclosed embodiment.
1E is a diagram illustrating a sample of an order page including items according to information about purchases and delivery from a virtual shopping cart, according to an interactive user interface element, according to a disclosed embodiment.
2 is a schematic diagram of an exemplary full-filment center configured to utilize the disclosed computer system, in accordance with the disclosed embodiments.
3A is a schematic diagram of an exemplary pickup zone, according to a disclosed embodiment.
3B is a schematic diagram of an operator's pickup operation in a pickup area, according to the disclosed embodiment.
4 is a schematic block diagram illustrating an exemplary embodiment of a network environment including a computerized system for efficiently distributing and distributing orders to multiple pickers, in accordance with the disclosed embodiment.
5 is an illustration of an exemplary order distribution process, according to a disclosed embodiment.
6 is a schematic block diagram illustrating an exemplary user device, according to the disclosed embodiment.
7 is a flow diagram of an exemplary computerized process for efficiently distributing orders based on system parameters, in accordance with a disclosed embodiment.

Next, it will be described in detail with reference to the accompanying drawings. If possible, the same reference numerals are used in the drawings to refer to the same or similar parts in the following description. While some exemplary embodiments are described herein, variations, adjustments, and other implementations are possible. For example, replacements, additions, or changes may be made to configurations and steps in the drawings, and the exemplary methods described herein may be changed by replacing, reordering, removing, or adding steps to the disclosed methods. Therefore, the following detailed description is not limited to the disclosed embodiments and examples. Instead, the appropriate scope of the invention is defined by the claims.

An embodiment of the present disclosure is based on system parameters by decomposing orders into individual items, and assigning various combinations of items to workers, taking into account limitations such as the system configuration such as the location of the items and the weight capacity of the transportation system. A computer implemented system and method for distributing orders.

Referring to FIG. 1A, a schematic block diagram 100 is shown illustrating an embodiment of an exemplary system including a computer system for communication that enables delivery, transport and logistics operations. 1A, system 100 may include a variety of systems, each of which may be connected to each other through one or more networks. The systems can be connected to each other via direct connections (eg using cables). The illustrated system includes a shipping authority technology (SAT) system 101, an external front end system 103, an internal front end system 105, a transportation system 107, and a mobile device 107A, 107B, 107C. , Seller portal 109, shipping and order tracking (SOT) system 111, fulfillment optimization (FO) system 113, fulfillment messaging gateway (FMG) ( 115), supply chain management (SCM) system (117), personnel management system (119), mobile devices (119A, 119B, 119C) (fulfillment center (FC) 200) ), a third-party full-fillment system 121A, 121B, 121C, a fulfillment center authorization system (FC Auth) 123, and a labor management system (LMS) 125 ).

In some embodiments, the SAT system 101 may be implemented as a computer system that monitors order status and delivery status. For example, the SAT system 101 may determine whether an order has passed a Promised Delivery Date (PDD), initiate a new order, re-deliver the items of the order that have not been delivered, and are not delivered. Appropriate actions can be taken, including canceling unsuccessful orders, initiating contact with the ordering customer, and so on. The SAT system 101 may also monitor other data, including outputs (such as the number of packages delivered over a certain period of time), and inputs (such as the number of empty cardboard boxes received for use in delivery). . The SAT system 101 also enables communication (e.g., using store-and-forward or other technology) between devices such as the external front end system 103 and the FO system 113. It can act as a gateway between different devices within the system 100 to enable.

In some embodiments, external front end system 103 may be implemented as a computer system that allows external users to interact with one or more systems within system 100. For example, in an embodiment where the system 100 enables presentation of the system so that a user can place an order for an item, the external front end system 103 receives the search request, presents the item page, and , It may be implemented as a web server requesting payment information. For example, the external front-end system 103 may be implemented as a computer or computers running software such as Apache HTTP server, Microsoft Internet Information Services (IIS), NGINX, and the like. In other embodiments, external front-end system 103 receives and processes requests from external devices (e.g., mobile device 102A or computer 102B), and based on these requests, database and other data storage devices It can execute custom web server software designed to obtain information from and provide a response to a received request based on the obtained information.

In some embodiments, the external front end system 103 may include one or more of a web caching system, a database, a search system, or a payment system. In one aspect, the external front-end system 103 may include one or more of these systems, while in another aspect, the external front-end system 103 is an interface (e.g., server-to-server) connected to one or more of these systems. Server, database to database, or other network connection).

An exemplary set of steps represented by FIGS. 1B, 1C, 1D and 1E will help explain some operations of the external front end system 103. External front end system 103 may receive information from a system or device within system 100 for presentation and/or display. For example, the external front-end system 103 may include a search result page (SRP) (eg, FIG. 1B), a single detail page (SDP) (eg, FIG. 1C), and One or more web pages may be hosted or provided, including a Cart page (eg, FIG. 1D), or an order page (eg, FIG. 1E). A user device (eg, using mobile device 102A or computer 102B) may request a search by going to the external front-end system 103 and entering information into a search box. External front end system 103 may request information from one or more systems within system 100. For example, the external front end system 103 may request information that satisfies the search request from the FO system 113. The external front-end system 103 may also request and receive a Promised Delivery Date or “PDD” for each product included in the search results (from the FO system 113). In some embodiments, the PDD is an estimate of when the product will arrive at the user's desired location if the package containing the product is ordered within a certain period of time, e.g., by the end of the day (11:59 PM), or where the product is desired by the user. May indicate the promised date to be delivered to (PDD is discussed further below with respect to FO system 113).

The external front-end system 103 may prepare an SRP (eg, FIG. 1B) based on the information. SRP may include information that satisfies the search request. For example, it may include a picture of a product that satisfies the search request. The SRP may also include information about each price for each product, or improved delivery options for each product, PDD, weight, size, offer, discount, and the like. The external front-end system 103 may transmit the SRP (eg, via a network) to the requesting user device.

The user device may select a product from the SRP using, for example, clicking or tapping the user interface, or using another input device to select the product shown in the SRP. The user device may make a request for information about the selected product and transmit it to the external front end system 103. In response, the external front-end system 103 may request information on the selected product. For example, the information may include additional information beyond that presented for the product on each SRP. This may include, for example, expiration date, country of origin, weight, size, number of items in the package, handling instructions, or other information about the product. Information may also include recommendations for similar products (e.g. based on big data and/or machine learning analysis of customers who have purchased this and at least one other product), answers to frequently asked questions, customer reviews, It may include manufacturer information, photos, etc.

The external front-end system 103 may prepare a Single Detail Page (SDP) (eg, FIG. 1C) based on the received product information. The SDP may also include other interactive elements such as a "Buy Now" button, a "Add to Cart" button, a quantity field, an item picture, and the like. The SDP may contain a list of sellers offering the product. This list may be ordered based on the price offered by each seller so that the seller offering the product is at the top of the list by selling the product at the lowest price. This list can also be ordered based on seller rankings, with the top ranked sellers at the top of the list. Seller rankings may be made based on a number of factors, including, for example, a seller's past tracking record of whether the promised PPD was followed. The external front-end system 103 may deliver the SDP (eg, over a network) to the requesting user device.

The requesting user device may receive an SDP listing product information. Upon receiving the SDP, the user device can interact with the SDP. For example, the user of the requesting user device can click or interact with the "Place in Cart" button of the SDP. This will add the product to the shopping cart associated with the user. The user device may send this request to the external front end system 103 to add the product to the shopping cart.

The external front-end system 103 may generate a shopping cart page (eg, FIG. 1D). In some embodiments, the shopping cart page lists products that the user has added to a virtual “shopping cart”. The user device may request a shopping cart page by clicking an icon on the SRP, SDP, or other page, or interacting with each other. In some embodiments, the shopping cart page includes not only all the products the user has added to the shopping cart, but also the quantity of each product, the price per item of each product, the price of each product based on the relevant quantity, information about the PDD, delivery method, shipping cost, User interface elements for modifying products in the shopping cart (e.g., deleting or modifying quantities), options for ordering other products or setting periodic delivery of products, options for setting interest payments, and making purchases. You can list information about the products in the shopping cart, such as user interface elements to proceed. A user of the user device may click on, or interact with, a user interface element (eg, a button labeled “Buy Now”) to initiate a purchase of a product in the shopping cart. In doing so, the user device can send this request to the external front end system 103 to initiate a purchase.

The external front-end system 103 may generate an order page (eg, FIG. 1E) in response to receiving a request to initiate a purchase. In some embodiments, the order page reorders items from the shopping cart and requests entry of payment and shipping information. For example, the order page contains information about the purchaser of an item in the shopping cart (e.g., name, address, email address, phone number), and information about the recipient (e.g., name, address, phone number, delivery information). , Shipping information (e.g., delivery and/or pickup rate/method), payment information (e.g., credit card, bank transfer, check, stored credit), user interface elements that request a cash receipt (e.g., Tax purposes), etc. The external front-end system 103 may transmit an order page to the user device.

The user device may input information on the order page and click or interact with a user interface element that transmits the information to the external front end system 103. From there, the external front-end system 103 transmits the information to other systems within the system 100 so that new orders can be created and processed with products in the shopping cart.

In some embodiments, the external front end system 103 may be further configured to allow the seller to send and receive information related to the order.

In some embodiments, internal front-end system 105 allows internal users (e.g., employees of an organization that owns, operates, or leases system 100) to interact with one or more systems within system 100. It can be implemented as a computer system. For example, in an embodiment where the network 101 enables the presentation of a system that allows a user to place an order for an item, the internal front-end system 105 provides diagnostic and statistical information about the order by the internal user. It can be implemented as a web server that allows viewing, modifying item information, or reviewing statistics on orders. For example, the internal front-end system 105 may be implemented as a computer or computers running software such as Apache HTTP server, Microsoft Internet Information Services (IIS), NGINX, and the like. In another embodiment, the internal front-end system 105 receives and processes requests from systems or devices represented within system 100 (as well as other devices not shown), and based on such requests, a database and other data storage devices. It can obtain information from and provide a response to a received request based on the obtained information (running a custom web server software designed).

In some embodiments, the internal front-end system 105 may include one or more of a web caching system, a database, a search system, a payment system, an analytics system, an order monitoring system, and the like. In one aspect, the internal front-end system 105 may include one or more of these systems, while in another aspect the internal front-end system 105 is an interface (e.g., server-to-server) connected to one or more of these systems. Server, database to database, or other network connection).

In some embodiments, transportation system 107 may be implemented as a computer system that enables communication between a system or device within system 100 and mobile devices 107A-107C. In some embodiments, transportation system 107 may receive information from one or more mobile devices 107A-107C (eg, cell phones, smart phones, PDAs, etc.). For example, in some embodiments, mobile devices 107A-107C may include devices operated by a delivery person. Deliverymen, which may be full-time, temporary or shift work, may use mobile devices 107A-107C for delivery of packages containing products ordered by the user. For example, to deliver a package, the deliveryman may receive a notification on the mobile device indicating the package to be delivered and the location to be delivered. Upon arrival at the delivery location, the delivery man can place the package (e.g., in the back of a truck or in a crate of the package) and use a mobile device to identify data associated with the identifier on the package (e.g. RFID tags, etc.) can be scanned, captured, and delivered (e.g., by placing it on a front door, leaving it to a security guard, delivering it to a recipient, etc.). In some embodiments, a delivery person may use a mobile device to take a picture(s) of the package and/or receive a signature. The mobile device transmits information including information on delivery, including, for example, time, date, GPS location, photo(s), an identifier related to a delivery person, an identifier related to a mobile device, and the like, to the transportation system 107. I can. Transportation system 107 may store this information in a database (not shown) for access by other systems within system 100. In some embodiments, transportation system 107 may use this information to prepare and transmit tracking data indicating the location of a particular package to another system.

In some embodiments, certain users may use one type of mobile device (e.g., full-time employees may use professional PDAs with custom hardware such as barcode scanners, stylus and other devices), while other users May use other types of mobile devices (for example, temporary or shift workers may use off-the-shelf mobile phones and/or smartphones).

In some embodiments, transportation system 107 may associate a user with each device. For example, the transportation system 107 may include a user (e.g., represented by a user identifier, an employee identifier, or a telephone number) and a mobile device (e.g., International Mobile Equipment Identity (IMEI), International Mobile Subscription Identifier (e.g. IMSI), a phone number, a Universal Unique Identifier (UUID), or a Globally Unique Identifier (GUID)). The transportation system 107 may use this association with respect to data received at delivery to analyze data stored in the database to determine the operator's location, operator's efficiency, or operator's speed, among others.

In some embodiments, merchant portal 109 may be implemented as a computer system that enables a merchant or other external entity to communicate electronically with one or more systems within system 100. For example, a seller can use a computer system (not shown) that uploads or provides product information, order information, contact information, etc. for a product to be sold through the system 100 using the seller portal 109. have.

In some embodiments, the delivery and order tracking system 111 receives, stores, and stores information about the location of the package containing products ordered by a customer (e.g., a user using devices 102A-102B). It can be implemented as a forwarding computer system. In some embodiments, the delivery and order tracking system 111 may request or store information from a web server (not shown) operated by a delivery company that delivers a package containing products ordered by a customer.

In some embodiments, the delivery and order tracking system 111 may request and store information from the systems presented to the system 100. For example, the delivery and order tracking system 111 may request information from the transportation system 107. As described above, the transportation system 107 may be configured with one or more mobile devices 107A-107C (e.g., mobile phones) associated with one or more of a user (e.g., deliveryman) or a vehicle (e.g., delivery truck). , Smartphone, PDA, etc.). In some embodiments, the delivery and order tracking system 111 also includes a workforce management system (WMS) 119 to determine the location of individual products within a full-filment center (e.g., full-filment center 200). You can request information from The delivery and order tracking system 111 requests data from one or more of the transportation system 107 or WMS 119, processes it, and provides it to a device (e.g., user devices 102A, 102B) upon request. can do.

In some embodiments, the full-filment optimization (FO) system 113 retrieves information about customer orders from other systems (e.g., external front-end systems 103 and/or shipping and order tracking systems 111). It can be implemented as a storage computer system. The FO system 113 may also store information indicating where a particular item is maintained or stored. For example, certain items may be stored in only one full-filment center, while certain other items may be stored in multiple full-filment centers. In yet another embodiment, a specific full-filment center may be configured to store only a specific set of items (eg, fresh produce or frozen products). The FO system 113 stores this information as well as related information (eg, quantity, size, receipt date, expiration date, etc.).

The FO system 113 may also calculate a corresponding PDD (promised delivery date) for each product. In some embodiments, the PDD may be based on one or more elements. For example, the FO system 113 may determine the past demand for a product (e.g., how many times the product has been ordered over a period of time), a predicted demand for a product (e.g., how many customers Are expected to be ordered), historical demand across the network indicating how many products have been ordered over a period of time, predicted demand across the network indicating how many products are expected to be ordered over the coming period, and storing each product. The PDD for a product may be calculated based on the number of one or more products stored in each of the full-filment centers 200, an estimate for the product, or a current order.

In some embodiments, the FO system 113 periodically (e.g., hourly) determines the PDD for each product and retrieves or retrieves another system (e.g., external front end system 103, SAT system (e.g. 101), it may be stored in the database for transmission to the delivery and order tracking system 111). In another embodiment, the FO system 113 receives electronic requests from one or more systems (e.g., external front end system 103, SAT system 101, delivery and order tracking system 111) and responds to the request. PDD can be calculated accordingly.

In some embodiments, full-filament messaging gateway (FMG) 115 receives a request or response in one format or protocol from one or more systems within system 100, such as FO system 113, and sends it to another format or protocol. And forwards the request or response in the converted format or protocol to another system such as WMS 119 or a third-party full-filment system 121A, 121B, or 121C, and vice versa. Can be implemented.

In some embodiments, supply chain management (SCM) system 117 may be implemented as a computer system that performs predictive functions. For example, the SCM system 117 may include, for example, a past demand for a product, a predicted demand for a product, a past demand across the network, a predicted demand across the network, and stored in each full-filment center 200. Based on the number of products, the expected or current order for each product, you can predict the level of demand for a specific product. In response to this predicted level and quantity of each product through all full-filment centers, the SCM system 117 creates one or more purchase orders to purchase and stockpile sufficient quantities to satisfy the predicted demand for a particular product. can do.

In some embodiments, the workforce management system (WMS) 119 may be implemented as a computer system that monitors work flow. For example, WMS 119 may receive event data representing individual events from individual devices (eg, devices 107A-107C or 119A-119C). For example, WMS 119 may receive event data indicating that one of these devices has been used to scan the package. As discussed below with respect to the full-filment center 200 and FIG. 2, during the full-filment process, the package identifier (e.g., barcode or RFID tag data) may be It may be scanned or read by a barcode scanner, RFID reader, high speed camera, tablet 119A, mobile device/PDA 119B, a device such as computer 119C, etc.). The WMS 119 may store each event representing a scan or read of the package identifier in a corresponding database (not shown) along with the package identifier, time, date, location, user identifier, or other information, and store this information to other systems. (For example, delivery and order tracking system 111) can be provided.

In some embodiments, WMS 119 may store information associating one or more devices (eg, devices 107A-107C or 119A-119C) with one or more users associated with system 100. For example, in some situations, a user (such as a part-time or full-time employee) may be associated with a mobile device in that it owns the mobile device (eg, the mobile device is a smartphone). In other situations, in that the user temporarily holds the mobile device (e.g., a user who has rented a mobile device from the beginning of the day, will use it for the day and return it at the end of the day), the mobile device Can be associated with.

In some embodiments, WMS 119 may maintain a job log for each user associated with system 100. For example, WMS 119 may be configured with any assigned process (e.g., unloading a truck, picking up an item in a pickup area, working on a rebin wall, packing an item), user identifier, location ( For example, the floor or area of the full-filment center 200), the number of units moved through the system by the staff (e.g., the number of items picked up, the number of packed items), the device (e.g. , Devices (119A-119C)), including an identifier associated with each employee, and information related to each employee may be stored. In some embodiments, WMS 119 may receive check-in and check-out information from a timing system, such as a timekeeping system operated on devices 119A-119C.

In some embodiments, third-party full-filment (3PL) systems 121A-121C represent computer systems associated with third-party providers of logistics and products. For example, some products are stored in the full-filment center 200 (as described below with respect to FIG. 2), while others may be stored off-site or on demand. It may be produced according to, and otherwise cannot be stored in the full-filment center 200. 3PL systems 121A-121C may be configured to receive orders from FO system 113 (e.g., via FMG 115), and products and/or services (e.g., delivery or Installation) can be provided. In some implementations, one or more 3PL systems 121A-121C may be part of system 100, while in other implementations, one or more 3PL systems 121A-121C may be external to system 100 ( For example, it may be owned or operated by a third party provider).

In some embodiments, the full-filment center authentication system (FC Auth) 123 may be implemented as a computer system having various functions. For example, in some embodiments, FC Auth 123 may act as a single-sign on (SSO) service for one or more other systems in system 100. For example, FC Auth 123 allows the user to log in through the internal front-end system 105, and determines that the user has similar rights to access resources in the delivery and order tracking system 111, and both Allow users to access those privileges without requiring a second login process. In another embodiment, FC Auth 123 allows users (eg, employees) to associate themselves with specific tasks. For example, some employees may not have electronic devices (such as devices 119A-119C) and may instead move between jobs and zones within full-filment center 200 for a day. FC Auth (123) may be configured to indicate the area to which these employees belong and work being performed at different times.

In some embodiments, the labor management system (LMS) 125 may be implemented as a computer system that stores attendance and overtime information for employees (including full-time and part-time employees). For example, LMS 125 may receive information from FC Auth 123, WMA 119, devices 119A-119C, transportation system 107, and/or devices 107A-107C.

The specific configuration shown in Fig. 1A is only an example. For example, while FIG. 1A shows the FC Auth system 123 connected to the FO system 113, not all embodiments require this particular configuration. In fact, in some embodiments, the system within the system 100 is the Internet, an intranet, a wide-area network (WAN), a metropolitan-area network (MAN), a wireless network conforming to the IEEE 802.11a/b/g/n standard, and lease. They may be connected to each other through one or more public or private networks including lines and the like. In some embodiments, one or more of the systems in system 100 may be implemented as one or more virtual servers implemented in a data center, server farm, or the like.

2 shows the full-filment center 200. The full-filment center 200 is an example of a physical place that stores items for delivery to customers when ordering. The full-filment center (FC) 200 may be divided into a number of zones, each of which is shown in FIG. 2. In some embodiments, these “zones” can be thought of as a virtual distinction between different stages of the process of receiving items, storing items, retrieving items, and shipping items. Thus, although “areas” are shown in FIG. 2, in some embodiments, other divisions of areas are possible, and the areas of FIG. 2 may be omitted, duplicated, or modified.

The inbound area 203 represents the area of the FC 200 in which an item is received from a seller who wants to sell a product using the system 100 of FIG. 1A. For example, a seller may use truck 201 to deliver items 202A and 202B. Item 202A may represent a single item large enough to occupy its shipping pallet, and item 202B may represent a set of items stacked together on the same pallet to save space.

The operator may receive the item in the inbound area 203 and, optionally, use a computer system (not shown) to check if the item is damaged and correct. For example, an operator may use a computer system to compare the quantity of items 202A, 202B to the order quantity of the item. If the quantities do not match, the worker may reject one or more of the items 202A and 202B. If the quantities match, the operator can transport the items to the buffer area 205 (eg, by a dolly, handtruck, forklift, or by hand). The buffer area 205 may be a temporary storage area for items that are not currently needed in the pickup area, for example, because there are enough items in the pickup area to meet the predicted demand. In some embodiments, the forklift 206 operates to carry items around the buffer zone 205 and between the inbound zone 203 and the drop zone 207. If items 202A, 202B are needed in the pickup area (eg, due to predicted demand), the forklift may carry items 202A, 202B to the drop area 207.

Drop zone 207 may be an area of FC 200 that stores items prior to being transported to pickup zone 209. An operator ("picker") assigned to a pickup operation accesses items 202A, 202B in the pickup area, scans the barcode for the pickup area, and uses a mobile device (e.g., device 119B). Can be used to scan barcodes associated with items 202A and 202B. The picker may then take the item to the pickup area 209 (eg, by placing it on a cart or carrying it).

The pickup area 209 may be an area of the FC 200 in which the item 208 is stored in the storage unit 310. In some embodiments, the storage unit 310 may include one or more of a physical shelf, a bookshelf, a box, a tote, a refrigerator, a freezer, a cold storage, and the like. In some embodiments, pickup area 209 may be organized into multiple floors. In some embodiments, an operator or machine may pick up items in a variety of ways, including, for example, a forklift, elevator, conveyor belt, cart, hand truck, cart, automated robot or device, or manual operation. Can be transported. For example, a picker may place items 202A, 202B on a hand truck or cart in drop zone 207 and take items 202A, 202B to pickup zone 209.

The picker may receive an instruction to place (or “stow”) an item at a specific spot in the pickup area 209, such as a specific space on the storage unit 310. For example, the picker can scan the item 202A using a mobile device (eg, device 119B). The device can indicate where the item 202A should be loaded, for example, using a system that indicates aisles, shelves, and locations. The device may then have the picker scan the barcode at that location before loading the item 202A at that location. The device may transmit (e.g., over a wireless network) data indicating that the item 202A has been loaded at that location by a user using the device 119B to a computer system, such as WMS 119 in FIG. 1A. .

Once the user places an order, the picker may receive a command to device 119B to retrieve one or more items 208 from storage unit 310. The picker can retrieve the item 208, scan a barcode on the item 208, and place it on the transport mechanism 214. In some embodiments, the transport mechanism 214 is represented as a slide, but the transport mechanism may be implemented as one or more of a conveyor belt, elevator, cart, forklift, hand truck, trolley, cart, and the like. The item 208 can then arrive at the packing area 211.

The packing area 211 may be the area of the FC 200 where items are received from the pickup area 209 and packed into a box or bag for final delivery to a customer. In the packing area 211, a worker assigned to receive the item ("rebin worker") will receive the item 208 from the pickup area 209 and determine which order it corresponds to. For example, a revining worker may use a device such as computer 119C to scan a barcode on item 208. Computer 119C may visually indicate which order item 208 is associated with. This may include, for example, a space or "cell" on the wall 216 corresponding to the order. Once the order is complete (for example, because the cell contains all the items in the order), the rebiner can notify the packing operator (or "packer") that the order is complete. Packers can retrieve items from cells and place them in boxes or bags for shipping. The packer can then send the box or bag to the hub section 213, for example, by forklift, cart, cart, hand truck, conveyor belt, hand or other means.

The hub zone 213 may be an area of the FC 200 that receives all boxes or bags ("packages") from the packing zone 211. Operators and/or machines in the hub zone 213 may retrieve the packages 218, determine to which part of the delivery zone each package is intended to be delivered, and send the packages to the appropriate camp zone 215. For example, if the delivery area has two fewer sub-areas, the package will be sent to one of the two camp areas 215. In some embodiments, an operator or machine may scan the package (eg, using one of the devices 119A-119C) to determine the final destination. Sending the package to the camp area 215 may include, for example, determining the portion of the geographic area to which the package is destined (based on the zip code), and determining the camp area 215 associated with that portion of the geographic area. I can.

In some embodiments, camp area 215 may include one or more buildings, one or more physical spaces, or one or more areas from which packages are received from hub area 213 for classification as a route and/or sub-root. . In some embodiments, the camp zone 215 is physically separate from the FC 200, while in other embodiments the camp zone 215 may form part of the FC 200.

Operators and/or machines of the camp area 215 may, for example, compare destinations with existing routes and/or sub-routes, calculation of workload for each route and/or sub-route, time of day, delivery Based on the method, the cost to deliver the package 220, the PDD associated with the item of the package 220, and the like, it is possible to determine which route and/or sub-root the package 220 should be associated with. In some embodiments, an operator or machine may scan the package (eg, using one of the devices 119A-119C) to determine the final destination. Once the package 220 is assigned to a particular route and/or sub-root, the operator and/or machine may carry the package 220 to be shipped. In exemplary FIG. 2, the camp area 215 includes a truck 222, a vehicle 226, and a delivery man 224A, 224B. In some embodiments, the deliveryman 224A may drive the truck 222, where the deliveryman 224A is a full-time employee delivering a package for the FC 200, and the truck owns the FC 200. , Owned, leased, or operated by the same company that it rents or operates. In some embodiments, the deliveryman 224B may drive the vehicle 226, where the deliveryman 224B is a “flex” or emergency worker delivering on demand (eg, seasonally). to be. The car 226 may be owned, leased or operated by the delivery person 224B.

3A is a schematic diagram of an exemplary pickup zone 300 that may provide similar functionality to the pickup zone 209 of FIG. 2. As shown in FIG. 3A, the pickup area 300 may be in the same warehouse as the FC 200. In the pickup area 300, the item 320 is stored in a storage unit 310, which may include a location identifier 311. In some embodiments, the storage unit 310 may be a physical shelf, a bookshelf, a box, a tote, a refrigerator, a freezer, a cold storage, or the like. In some embodiments, item 320 may be a product for sale, and when a customer places an order for item 320 through a website operated by an external front end system 103, (such as a picker) It can be picked up by the user or by an automated machine.

In some embodiments, the storage unit 310, such as a shelf, may have a location identifier 311 attached to it. The location identifier 311 may be a unique address of a specific location of the storage unit 310 within the pickup area 300. In some embodiments, the location identifier 311 may correspond to a particular item placed at that location. However, in other embodiments, the location identifier 311 may represent a plurality of items placed together or close to each other. The location identifier 311 may be an item barcode, an RFID tag, or a matrix barcode such as a quick response (QR) code. A camera or scanner in a user device, such as mobile device 119B, can scan the location identifier using an input device, such as an imaging device comprising a camera or scanner. The scanned information may be transmitted to the WMS 119. Based on the scanned information, the WMS 119 may determine and confirm whether the picker is at a location designated by the WMS 119.

The arrangement can include one or more items. The picker may pick up items included in the assigned batch in the pickup area 300 until all items belonging to the batch are picked up. The picker can be moved on foot in the pickup area 300, such as a warehouse. In some embodiments, the picker may use other devices to assist movement, such as scooters, robots and/or vehicles.

In some embodiments, a user device (eg, mobile device 119B) may assist the picker in finding a designated location. In some embodiments, the user device may show the picker a map with navigation. For example, the user device may inform the picker to turn left when it reaches a certain location. In some embodiments, the user device may provide signals (including but not limited to maps, sounds, vibrations, or text messages) to assist the picker in finding a designated location.

3B is a schematic diagram of a pickup operation of an operator (ie, picker 350) in the pickup area 300 of FIG. 3A. In some embodiments, item 320 may have an item identifier 321 attached to item 320. However, in another embodiment, the item identifier 321 may be located near the item 320 without being attached to the item 320. The item identifier 321 may include one or more of an item barcode, an RFID tag, and a matrix barcode such as a QR code.

A camera or scanner in a user device, such as mobile device 119B, may scan the item identifier 321. The scanned information may be transmitted to the WMS 119 through a wireless or wired network. Based on the received information, the WMS 119 may check whether the scanned item identifier 321 matches the item identifier information stored in the WMS 119. Upon confirming that the WMS 119 matches, the mobile device 119B may display a command to the picker 350 to pick up the item 320 and place it in the container 330. The picker 350 may continue this pickup operation until the last item belonging to the batch is picked up.

In some embodiments, the container 330 may have a container identifier 311 attached to the container 330. Container 330 may be any storage device configured to store one or more items 320, such as a box, tote, bag, or the like. In some embodiments, container 330 may be a compartment within an automatic pick-up machine. The container identifier 331 may include one or more of an item barcode, an RFID tag, and a matrix barcode such as a QR code. In some embodiments, there may be two or more types of containers 330 having different sizes, shapes, or materials. For example, one type of container 330 may be specially configured for refrigerated items (eg, agricultural products, meat) and may be made of an insulating material. The types of containers that can be used in the FC 200 may be different, and a specific type that can be used in one FC may not be used in another FC.

When items belonging to the batch are picked up, the picker 350 may place the container 330 on the cart 340. In some embodiments, the cart 340 may have a cart identifier 341 attached to the cart 340. Cart 340 may be any vehicle configured to store and transport one or more containers 330, such as a handcart, dolly, drivable cart, or the like. In some embodiments, the cart 340 may be fuel or electricity driven. In some other embodiments, cart 340 may be an automated robot designed to move between storage units 310 and pick up items 320 using a mechanical mechanism such as an articulating arm. The types of carts usable in the FC 200 may be different, and a specific type that can be used in one FC may not be used in another FC.

After the last item belonging to the batch is picked up, the picker 350 uses the cart 340 to move the container 330 to the destination location (e.g., packing area 211) according to the command displayed on the mobile display 119B. ) Or transport mechanism 214). For example, the picker 350 may scan a destination identifier by scanning a destination barcode and transmit the scanned information to the WMS 119. The WMS 119 may share the scanned information with other systems, such as the FO system 113 in the full-filment center, via a wireless or wired network. The sent items are subsequently processed through the process described above with respect to FIG. 2 and finally sent to the customer.

4 is a conceptual block diagram illustrating an exemplary embodiment of a network environment 400 including a computerized system for distributing orders and distributing orders efficiently to multiple users. Environment 400 may include various systems, each of which may be connected to each other through one or more networks. These systems can also be connected to each other via direct connection, for example using cables. The depicted systems include a FO system 113, a full-filment messaging gateway (FMG) 115, a workforce management system (WMS) 119, devices 119A-C, and users 350. The FMG 115, WMS 119, devices 119A-C, and users 350 shown in Fig. 4 respectively correspond to their respective corresponding portions shown in Figs. 1A and 3B, so here again I won't explain.

On the other hand, the FO system 113 is shown in more detail as its component system. In some embodiments, the FO system 113 includes an order database 411, an inventory database 412, an FC configuration database 413, and a batch generator 414. In these embodiments, the components of the FO system 113 (i.e., order database 411, inventory database 412, FC configuration database 413, and batch generator 414) are It may be implemented as one or more functional units performed by one or more processors on the basis of it. Alternatively, the components of the FO system 113 may be implemented as one or more computer systems that communicate with each other over a network. In this embodiment, each of the one or more computer systems may include one or more processors, one or more memories (ie, non-transitory computer readable media), and one or more input/output (I/O) devices. In some embodiments, each of the one or more computer systems may take the form of a server, a general purpose computer, a mainframe computer, a special purpose computing device such as a GPU, a laptop, or any combination of such computing devices.

Order database 411, inventory database 412, and FC configuration database 413, in some embodiments, one or more computers that collect, accumulate, and/or generate various data each accumulated from the other systems described above. It can be implemented as a system. In another embodiment, the order database 411, the inventory database 412, and the FC configuration database 413 may be implemented as a single database system, and their storage space (e.g., a non-transitory readable medium). You can store the information corresponding to the database in different parts of the. In some embodiments, the database may comprise a cloud-based database or an on-premise database including one or more hard disk drives, one or more solid state drives (SSDs), or one or more non-transitory memory. have.

Regardless of the above implementation, each component may each be dedicated to order information, inventory information, and FC configuration information. More specifically, the order database 411 may store order information from the external front end system 103 when a customer orders one or more items in stock. The order information may include, for example, an order identifier, a list of item identifiers 321 ordered by a customer, a quantity ordered for each item, customer contact information, payment information, and the like.

The inventory database 412 may store item information of individual items in the pickup area 209 of FIG. 2. For example, item information includes a list of item identifiers 321 grouped by individual FCs, corresponding quantity of items held by FCs, location identifiers 311 within each FC, dimensions, weight of corresponding items, and Handling instructions (eg, fragile, perishable, refrigerated, frozen), etc. may be included. In some embodiments, when items in pickup area 209 are replenished by receiving items from vendors in inbound area 203 of FIG. 2 and they are picked up by pickers in pickup area 209 and camped. As delivery from zone 215 to a customer, item information may be updated or created. Various aspects of item information may be updated frequently as individual item identifiers are scanned at different locations within FC 200, which information can be used in the network system (e.g., transport system 107, for example, described above with respect to FIG. 1A). It is processed by the SOT system 111 and WMS 119.

In addition, the FC configuration database 413 may store FC configuration information of an individual FC. For example, FC configuration information may include the available types and number of carts 340, the available types and number of containers 330, specifications of the transportation system 214 such as weight limits, and the pickers currently working at each FC ( 350) and the like. In some embodiments, the FC configuration information is changed when a new FC is built or an existing FC is changed, for example to add more types and numbers of carts 340 or containers 330, or a new transport system 214 is When installed, it can be collected and updated from time to time.

Batch generator 414, in some embodiments, aggregates order information from order database 411 and sends order information to picker 350 in batches based on item information from inventory database 412 and FC configuration information. It may include one or more computing devices configured to distribute. The functionality of the batch generator 414 is described in more detail below with respect to FIGS. 5 and 7.

5 is an illustration of an exemplary order distribution process 500 that aggregates multiple orders into batches. In this example, order A (510A), order B (510B), order C (510C), and order D (510D) are aggregated by batch generator 414 and batch A (520A), batch B (520B) and batch It can be distributed to C (520C). In addition to the number of orders and batches, the items illustrated here are merely exemplary, and the batch generator 414 aggregates an arbitrary number of orders in any combination of items, and puts them into an arbitrary number of batches as needed. Can be distributed.

In FIG. 5, the order A 510A may include an item identifier 321 corresponding to each of the lemonade 501 and the tomato sauce 502, each of which has 5 and 3 numbers. The order B 510B may include an item identifier 321 corresponding to each of the grated cheese 504 having one quantity. Order C (510C) is an item identifier corresponding to each of the number of 1, 1, 3 and 2, desktop 504, toy tablet 505, hot sauce 506, and chili sauce 507, respectively. (321) may be included. The order D (510D) may include an item identifier 321 corresponding to each of the number of three and one, the toy car 508 and the toy truck 509, respectively.

Batch generator 414 may combine all item identifiers 321 and distribute them to batch A-C 520A-C based on, for example, individual location identifier 311. For example, batch A 520A may include an item identifier 321 corresponding to a location identifier 311 associated with an area within the pickup area 209 that stores grocery items. Similarly, batch B 520B and batch C 520C may each include an item identifier 321 corresponding to a location identifier 311 associated with areas of the pickup area 209 storing electronic devices and toys. . In some embodiments, where order ADs 510A-D include an amount of items (whether by volume, weight, or quantity) associated with a specific area that exceeds a predetermined maximum batch size, batch generator 414 Can be distributed in more than one batch. In some embodiments, each batch may be associated with a particular type of cart 340 and a maximum batch size may be determined based on the size of the available type of cart 340.

The batch generator 414 may also divide the item identifier 321 assigned to a particular batch into one or more container groups. For example, the item identifier 321 assigned to batch A 520A may be further divided into container group A 521A and container group B 521B; In addition, the item identifier 321 allocated to the batch C 520C may be divided into a container group X (521X) and a container group Y (521Y). Alternatively, all item identifiers 321 of the batch, such as batch B 520B, may be assigned to a single container group, such as container group P 521P.

In some embodiments, the determination of whether to split the item identifier 321 of the batch may be based on a number of factors associated with the item corresponding to the item identifier 321, such as the total weight, total volume, individual shape of the items, and the like. I can. The batch generator 414 may compare the corresponding factors with the dimensions and/or weight capacity of each container 330 and divide the item identifier 321 when a predetermined maximum container group size is reached. For example, the container group A (521A) and the container group B (521B) are each individually lemonade 501 and chili pepper 507; Item identifiers 321 for tomato sauce 502, hot sauce 506, and grated cheese 503 may be included. In another embodiment, where the batch is associated with too many items to reach the maximum number of container groups for a particular cart 340 associated with that batch, the batch generator 414 creates a new batch and the excess item identifier ( 321) can be associated with the new batch. The new batch can likewise be divided into one or more container groups as described above.

6 is a schematic block diagram illustrating an exemplary user device, such as mobile device 119B. The mobile device 119B may include a display 610, an I/O device 620, a processor 630, and a memory 640. While FIG. 6 shows a mobile device 119B, one of ordinary skill in the art will understand that other devices (eg, tablet 119A or computer 119C) may be implemented in a similar manner.

The mobile device 119B may be configured with storage that stores one or more operating systems that, when executed by one or more processors, perform known operating system functions. For example, the operating system may include Microsoft Windows, Unix, Linux, Android, Apple Mac OS, iOS, or other types of operating systems. Thus, examples of the disclosed invention may operate and function as a computer system running any type of operating system. Mobile device 119B may also include communication software, such as web browser software, tablet, or smart handheld device networking software, etc. that, when executed by the processor, provide communication with the network.

Mobile device 119B may include a display 610. The display 610 may include, for example, a liquid crystal display (LCD), a light emitting diode screen (LED), an organic light emitting diode screen (OLED), a touch screen, and other known display devices. The display 610 may display various types of information. For example, the display 610 may display the number of containers and carts required for placement. The display 610 may display touchable or selectable options that the user (eg, the picker 350) can select, and the user selects the option through the I/O device 620 such as a touch screen. Can be received.

I/O device 620 may include one or more devices that enable mobile device 119B to transmit and receive information from a user or other device. The I/O device 620 may include various input/output devices such as a scanner, a camera, a keyboard, a mouse type device, a gesture sensor, a motion sensor, a physical button, an oratory input, a touch screen, and the like. The I/O device 620 may also have one or more components for transmitting and receiving information with other components in the WMS 119, for example by establishing a wired or wireless connection between the mobile device 119B and the WMS 119. It may include a communication module (not shown).

Mobile device 119B may include at least one processor 630, which may be one or more known computing processors, such as those described in connection with FO system 113 of FIG. 4. The processor 630 may, for example, use various commands stored in the mobile device 119B to perform various functions of processing information related to the item 320 or the container 330 received from the I/O device 620. You can run it.

Mobile device 119B may include memory 640, which is a volatile or nonvolatile, magnetic, semiconductor, tape, optical, removable, non-removable or other type of storage device or type (i.e., non-transitory) computer. It may be a readable medium. The memory 640 may store one or more programs 650. The program 650 may include an operating system (not shown) that performs known operating system functions when executed by one or more processors. The disclosed examples can operate and function as a computer system running any type of operating system.

The program 650 may be a workflow management program. The workflow management program can control the pickup operation in the FC 200 by providing commands to the operator. Program 650 may be executed by processor 630 to perform a process related to fulfilling the deployment, which process receives an identifier associated with the deployment from mobile device 119B, mobile device 119B. Displaying the number of containers determined through, receiving a container identifier from the user device, and finding and retrieving a list of one or more items associated with the batch are not limited thereto.

7 is a flow diagram of an exemplary computerized process 700 for efficiently distributing orders based on system parameters. In some embodiments, process 700 may be performed by FO system 113 using information from other network systems such as those described above. More specifically, process 700 may be performed by batch generator 414 using information from order database 411, inventory database 412, and FC configuration database 413. In some embodiments, the scope of the process 700 may be limited to a specific FC, and the FO system 113 may provide the FC configuration information of a specific FC and item information associated with a specific FC (e.g., items stored in that FC). The number and location of) can be used to perform the process 700. The process 700 for different FCs may be performed by the other FO system 113 associated with each FC or the same FO system 113 in a separate instance of the process 700. Further, the FO system 113 may repeat steps 701-706 several times in a given period for each FC 200 when customers place an order through the external front end system 103. The FO system 113 may also perform multiple instances of steps 701-706 for one or more groups of orders, which instances may be individually in various steps at any given moment.

In step 701, batch generator 414 may aggregate one or more orders placed by customers through external front end system 103. In some embodiments, the aggregation involves collecting order information from the order database 411 by its order identifier when new order information is created. When aggregating orders, the batch generator 414 can also decompose the orders until it reaches the product level, in which case the list of item identifiers 321 in each order information is the product identifier along with the individual order quantity for each item. Combined into one master list of 321. Aggregation of orders may continue until a predetermined event, at which point the batch generator 414 may perform step 702 of distributing the item identifier 321 in the master list to one or more batches. The batch generator 414 may also update the set of order information associated with the item identifier 321 in the master list to include one or more batches. In some embodiments, batch generator 414 may also initiate another aggregation with the next set of orders made by the customer while the master list is being processed through steps 702-706.

In some embodiments, the predetermined event may be based on the time at which batch generator 414 stops aggregating order information to the master list at predetermined intervals. In another embodiment, the predetermined event is via an I/O device connected to the FO system 113, by inputting a signal to the batch generator 414 to stop aggregating the current set of orders, a user (e.g. For example, it can be triggered manually by an administrator at FC). Further, in another embodiment, the batch generator 414 may automatically trigger a predetermined event based on FC configuration information, such as the number of available pickers. For example, batch generator 414 may trigger a predetermined event when the master list contains a sufficient quantity of items to generate a sufficient number of batches to be allocated to each picker. In some embodiments, batch generator 414 may trigger a predetermined event when the number of batches that can be generated is greater than the number of available pickers by a predetermined factor (eg, 1.5).

In step 702, the batch generator 414 may distribute the item identifier 3221 in the master list to one or more batches based on the corresponding item information. In some embodiments, the goal of this aggregation and distribution of items (i.e., reorganization) is to efficiently retrieve items from pickup area 209 compared to each picker finding all items in the order without taking into account where the items were stored. It is to make it possible to find it. Assigning batches associated with a specific area within pickup area 209 to specific pickers allows those pickers to become familiar with the position of the item, increasing their speed, and/or the distance the picker must travel to complete the placement. Can be reduced.

In some embodiments, the batch generator 414 may segment the item identifiers based on their individual location identifiers, in which case the item identifiers corresponding to items located close to each other based on the item individual location identifiers 311. 321 are grouped together. In some embodiments, the pickup zone 209 may be divided into one or more zones, each zone being assigned to one or more pickers, and the batch generator 414 based on the zone to which the corresponding location identifier 311 belongs, The item identifier 321 can be divided. As discussed above, in some embodiments, batch generator 414 may divide a batch into two or more batches based on the type of cart 340 available on a particular FC. In another embodiment, the batch generator 414 may also partition the item identifier 321 based on predetermined parameters, such as a minimum batch size, a maximum batch size, and the like, which may be retrieved from the FC structure database 413.

In step 703, the batch generator 414 may determine parameters of the transport system available on the particular FC. In some embodiments, the transport system may include at least one of a cart 340, a container 330, and a transport mechanism 214 described above. Thus, the parameters of the transportation system may include various aspects of each system, such as the available number and type of carts 340, the available number and type of containers 330, and the type of transportation mechanism 214. . Further, the parameter associated with the cart 340 may include at least one of a weight capacity of the cart and a dimension of a compartment or a cargo space of the cart. Similarly, the parameter associated with the container 330 may include at least one of a weight capacity of the container and a dimension of a storage compartment of the container. The parameters of the transport mechanism 214 may include at least the weight capacity of the transport mechanism. In some embodiments, batch generator 414 may retrieve these parameters from FC configuration database 413.

In step 704, using the parameters determined in step 703 described above, the batch generator 414 may divide each batch into one or more container groups or additional batches in the manner described above with respect to FIG. 5. More specifically, the batch generator 414 searches the dimensions and weight of each item corresponding to the item identifier 321 assigned to a specific batch, and the weight capacity or volume capacity of the corresponding container 330 or the transport mechanism 214 Each item identifier 321 may be assigned to a container group until any of the first occurrences of reaching the weight capacity of ). In some embodiments, batch generator 414 may apply a predetermined ratio to each dose. For example, instead of assigning the item identifier 321 to the container group until the weight capacity of the corresponding container 330 is reached, the batch generator 414 Can be assigned. The predetermined ratio may be a uniform ratio applied to each capacity (i.e., the weight capacity of the container 330, the volume capacity of the container 330, and the weight capacity of the transport mechanism 214), or the ratio is operated It can be different for each capacity or type of system.

One or more items of the order may have an irregular shape, which may cause the corresponding container 330 to fill faster than expected when the picker puts the actual items into the container 330. In some embodiments, a heavy item placed over a fragile or soft item contained may destroy the fragile or soft item. Thus, in step 705, the batch generator 414 determines the optimal position or orientation of each item within the container 330 based on the item information retrieved from the inventory database 412, for example, using the considerations identified above. You can decide. Alternatively or additionally, the batch generator 414 may also determine the optimal position or orientation by using conventional methods of packing multiple items as well as other known methods.

Based on the container group determined in step 704 described above, the batch generator 414 may determine the number and type of containers 330 and the type of cart 340 required for a specific batch. This information allows the picker 350 having the correct number and type of transport mechanism required for the arrangement to start the arrangement, so that there is no room for transporting the item 320, the picker 350 is picked up. Avoid moving back and forth within the zone 209 several times. Thus, in step 706, the batch generator 414 may transmit this information associated with the specific batch to the user devices (e.g., devices 119A-C) owned by the WMS 119 and the pickers assigned to the specific batch. have. The user device can then display this information in the manner described above.

While the present disclosure has been shown and described with reference to specific embodiments thereof, it will be understood that the present disclosure may be practiced in other circumstances, without modification. The foregoing description has been presented for purposes of illustration. It is not exhaustive and is not limited to the precise forms or embodiments disclosed. Changes and adjustments will be apparent to those skilled in the art from consideration of the description and implementation of the disclosed embodiments. Additionally, although the forms of the disclosed embodiments have been described as being stored in memory, those of ordinary skill in the art will appreciate these forms as secondary storage devices, e.g., hard disks or CD ROMs, or other types of RAM or ROM, USB media, DVDs. It will be appreciated that other types of computer-readable media may also be stored, such as, Blu-ray, or other optical drive media.

Computer programs based on the above description and disclosed methods are within the skill of an experienced developer. Several programs or program modules may be created using any technology known to a person skilled in the art, or may be designed in connection with existing software. For example, a program section or program module can be a .NET Framework, a .NET Compact Framework (and related languages, such as Visual Basic, C, etc.), Java, C++, Objective C, HTML, HTML/AJAX combinations, XML, or Java applets. These can be designed within or by embedded HTML.

In addition, although exemplary embodiments have been described herein, as those skilled in the art will understand based on the present disclosure, the scope of some or all embodiments is equivalent to elements, changes, omissions, and combinations (e.g., Combinations of forms), adjustments and/or modifications. The limitations within the claims are intended to be broadly understood based on the language applied within the claims, and are not limited to the examples described herein or during the performance of the application. The example is intended to be interpreted non-exclusively. Additionally, the steps of the disclosed method may be modified in any other way, or may include rearranging the steps and/or inserting or deleting steps. Therefore, the description and illustration are to be considered by way of example only, and the true scope and spirit are intended to be indicated by the following claims and their full scope equivalents.

Claims (20)

A computer implemented system for efficiently distributing orders based on system parameters, comprising:
A memory for storing instructions; And
At least one processor configured to execute the instructions,
The above commands are
Aggregate one or more orders comprising a plurality of items of one or more quantities;
Allocating a subset of items to a batch, the items being assigned to one or more batches;
Determine one or more parameters of a transport system for the batches;
Determining at least one of a location or orientation of items in the transportation system based on the parameters of the transportation system; And
And transmitting the parameters of the transportation system to a user device for display.
Computer implemented system. The method according to claim 1,
Aggregating these orders
Aggregating the orders over a predetermined period of time;
Counting the orders until user input is received; or
Aggregating the orders based on the number of workers available
Containing at least one of
Computer implemented system. The method according to claim 1,
Assigning the subset of items to the batch
Allocating the first item to the batch based on at least one of a location of a first item, a dimension of the first item, and a combined weight of the subset of items.
Computer implemented system. The method according to claim 1,
The parameters include a type of container provided in the transport system, and the number of containers provided in the transport system; And at least one of a carrying capacity of the transport system.
Computer implemented system. The method according to claim 1,
The combined weight of the subset of items is less than the carrying capacity of the transport system.
Computer implemented system. The method according to claim 1,
The transport system includes one or more containers, each container having a weight capacity and a volume capacity.
Computer implemented system. The method of claim 6,
Assigning the subset of items to the batch
Allocating a portion of the subset of items to a first container, wherein the subset of items is allocated to one or more containers based on the weight capacity and the volume capacity.
Computer implemented system. The method of claim 7,
The total weight or total volume of the portion of the subset of items allocated to the first container is less than the weight capacity and the volume capacity of the first container by a predetermined ratio
Computer implemented system. The method according to claim 1,
The instructions further comprise transporting the batches from a first location to a second location using an automated transportation system.
Computer implemented system. The method of claim 9,
Allocating the subset of items to the batch is based on the weight capacity of the automated transport system.
Computer implemented system. A computer-implemented method for efficiently distributing orders based on system parameters, comprising:
Aggregating one or more orders including a plurality of items of one or more quantities;
Allocating a subset of items to a batch, the items being assigned to one or more batches;
Determining one or more parameters of a transportation system for the batches;
Determining at least one of a location or orientation of items in the transportation system based on the parameters of the transportation system; And
Transmitting the parameters of the transportation system to a user device for display.
Computer-implemented method. The method of claim 11,
The step of aggregating the orders
Aggregating the orders over a predetermined period of time;
Aggregating the orders until user input is received; or
Aggregating the orders based on the number of available workers
Containing at least one of
Computer-implemented method. The method of claim 11,
Allocating the subset of items to the batch comprises:
Allocating the first item to the batch based on at least one of a location of a first item, a dimension of the first item, and a combined weight of the subset of items.
Computer-implemented method. The method of claim 11,
The parameters include a type of container provided in the transport system, and the number of containers provided in the transport system; And at least one of the transport capacity of the transport system.
Computer-implemented method. The method of claim 11,
The combined weight of the subset of items is less than the carrying capacity of the transport system.
Computer-implemented method. The method of claim 11,
The transport system includes one or more containers, each container having a weight capacity and a volume capacity.
Computer-implemented method. The method of claim 16,
Allocating the subset of items to the batch comprises:
Allocating a portion of the subset of items to a first container, wherein the subset of items is allocated to one or more containers based on the weight capacity and the volume capacity.
Computer-implemented method. The method of claim 17,
The total weight or total volume of the portion of the subset of items allocated to the first container is less than the weight capacity and the volume capacity of the first container by a predetermined ratio
Computer-implemented method. The method of claim 11,
Further comprising transporting the batches from a first location to a second location using an automatic transport system, wherein assigning the subset of items to the batch is based on the weight capacity of the automatic transport system.
Computer-implemented method. A computer implemented system for efficiently distributing orders based on system parameters, comprising:
A memory for storing instructions; And
At least one processor configured to execute the instructions,
The above commands are
Aggregate one or more orders comprising a plurality of items of one or more quantities;
Allocating a first subset of items to a first batch, the items being allocated to one or more batches;
Determine one or more parameters of a transport system for the first deployment;
Determining at least one of a location or orientation of the first set of items in the transportation system based on the parameters of the transportation system;
Transmit the parameters of the transportation system to a user device for display;
Receive from the user device a first item identifier associated with a first item of the first subset of items; And
Transmitting to the user device at least one of the location or the direction of the first item placed in the transportation system for display in response to the first item identifier.
Computer implemented system.

Images