Computer-implemented system and method for centralized logistics monitoring

Abstract

The disclosed embodiments provide systems and methods related to monitoring logistics. A method for monitoring logistics includes: capturing attendance data and timing data of a first plurality of workers from a first management system; capturing data identifying work performed by a second plurality of workers from a second management system, the data including: the location of the work performed, related scanning events, or check-in information related to each of the second plurality of workers; capturing work data related to a third plurality of workers from a third management system. The method also includes: merging the captured data about the workers with corresponding data into one of the captured plurality of data sets; receiving a request from a user device to obtain a visualization including analyzing the merged data; and providing the visualization to the user device, wherein the visualization is generated by analyzing the merged data.

Description

Technical Field

[0001] The present disclosure generally relates to computerized systems and methods for monitoring logistics. In particular, embodiments of the present disclosure relate to inventive and unconventional systems involving computer-implemented systems, methods, and user interfaces for efficiently monitoring human labor in a fulfillment center location. Background Art

[0002] Many retailers that prepare and ship goods from warehouses rely on lean manufacturing and other methods to minimize wasted labor while monitoring labor to increase speed, efficiency, and improve quality. While existing warehouses and the systems used to monitor human labor in such warehouses are configured to handle the process efficiently, common problems arise when the systems fail to identify poorly performing workers or fail to monitor every task occurring in the warehouse.

[0003] To alleviate such problems, conventional systems receive data from various sources and present the received data to managers associated with the warehouse. Although these systems attempt to monitor human labor in FCs, manual operations are required to manage worker attendance and performance and determine statistics and other information from the received data. In addition, the data transmitted from various sources use different metrics, and data delays make it difficult for users to easily perceive the status of FCs.

[0004] Therefore, there is a need to improve the logistics monitoring methods and systems used in fulfillment centers. Summary of the invention

[0005] One aspect of the present disclosure relates to a method for monitoring logistics. The method may include operations. The operations include: capturing attendance data and timing data of a first plurality of workers from a first management system; capturing data identifying work performed by a second plurality of workers from a second management system. The data may include: the location of the work performed, the associated scanning event, or clock-in information associated with each of the second plurality of workers. The operations also include: capturing work data associated with a third plurality of workers from a third management system; merging the captured data about workers with corresponding data into one of the captured plurality of data sets; and receiving a first request for monitoring logistics from a user device based on a specific criterion (e.g., the usage of each search); determining the usage of each search by the user device using a processor that tracks the amount of memory allocated to each search associated with a parameter within a predetermined time; automatically selecting the parameter with the largest usage to the first parameter based on the determined usage; merging the captured data about workers with corresponding data into one of the captured plurality of data sets based on the selected first parameter; and providing visualization to the user device, wherein the visualization is generated by analyzing the merged data.

[0006] Another aspect of the present disclosure relates to a computer-implemented system for monitoring logistics. The computer-implemented system may include one or more storage devices storing instructions. The computer-implemented system may also include one or more processors configured to execute instructions to perform the operations described above.

[0007] Yet another aspect of the present disclosure relates to a computer-implemented system for monitoring logistics. The computer-implemented system may include one or more memory devices storing instructions. The computer-implemented system may also include one or more processors configured to execute instructions to perform the operations described above. The operations also include providing visualization to a user device, wherein the visualization includes displaying the distribution of jobs assigned to workers on each allocation process based on the merged data.

[0008] Other systems, methods, and computer-readable media are also discussed herein. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1A is a schematic block diagram illustrating an exemplary embodiment of a network including a computerized system for communicating that implements shipping, transportation, and logistics operations consistent with the disclosed embodiments.

[0010] Figure 1BA sample search result page (SRP) including one or more search results that satisfy a search request and interactive user interface elements consistent with the disclosed embodiments is described.

[0011] Figure 1C A sample Single Display Page (SDP) including a product and information about the product and interactive user interface elements consistent with the disclosed embodiments is described.

[0012] Figure 1D A sample shopping cart page including items in a virtual shopping cart and interactive user interface elements consistent with the disclosed embodiments is described.

[0013] Figure 1E A sample order page including items from a virtual shopping cart, information about purchase and shipping, and interactive user interface elements consistent with the disclosed embodiments is described.

[0014] Figure 2 is an illustration of an exemplary fulfillment center configured to utilize the disclosed computerized system consistent with the disclosed embodiments.

[0015] Figure 3 is a schematic block diagram illustrating an exemplary embodiment of a network including a computerized system for monitoring logistics consistent with the disclosed embodiments.

[0016] Figure 4 is an exemplary flow chart for processing data to monitor logistics consistent with the disclosed embodiments.

[0017] FIG. 5A to FIG. 5O An exemplary user interface for monitoring a logistics tool consistent with the disclosed embodiments is described. Specific embodiments

[0018] The following detailed description refers to the accompanying drawings. Whenever possible, the same reference numerals are used in the drawings and the following description to refer to the same or similar parts. Although several illustrative embodiments are described herein, modifications, adaptations and other embodiments are possible. For example, the components and steps shown in the drawings may be replaced, added or modified, and the illustrative methods described herein may be modified 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. On the contrary, the proper scope of the invention is defined by the appended claims.

[0019] Embodiments of the present disclosure relate to systems and methods configured for monitoring logistics. The disclosed embodiments provide innovative technical features that allow monitoring of individual workers associated with a fulfillment center and the performance of each worker. For example, the disclosed embodiments are capable of capturing data associated with workers in a fulfillment center from various management systems, merging the captured data about workers with corresponding data into a captured data set, and effectively providing visualizations of the status of the workers and the performance of the workers to a user device in real time.

[0020] refer to Figure 1A , shows a schematic block diagram illustrating an exemplary embodiment of a system including a computerized system for communication that implements shipping, transportation, and logistics operations. Figure 1A As shown, system 100 may include various systems, each of which may be connected to each other via one or more networks. Systems may also be connected to each other via direct connections (eg, using cables). The described systems include: a Shipment Authority Technology (SAT) system 101, an external front-end system 103, an internal front-end system 105, a transportation system 107, a mobile device 107A, a mobile device 107B, and a mobile device 107C, a seller portal 109, a Shipment and Order Tracking (SOT) system 111, a Fulfillment Optimization (FO) system 113, a Fulfillment Messaging Gateway (FMG) 115, a Supply Chain Management (SCM) system 117, a Warehouse Management System 119, mobile devices 119A, 119B, and 119C (described as being inside a Fulfillment Center (FC) 200), a third-party fulfillment system 121A, 121B, and 121C, a Fulfillment Center Authorization System (FC) 200, and a third-party fulfillment system 121A. Auth)123 and Labor Management System (LMS)125.

[0021] In some embodiments, the SAT system 101 can be implemented as a computer system that monitors order status and delivery status. For example, the SAT system 101 can determine whether an order exceeds its promised delivery date (Promised Delivery Date, PDD), and can take appropriate actions, including: initiating a new order, reshipping items in an undelivered order, canceling an undelivered order, initiating contact with the ordered customer, etc. The SAT system 101 can also monitor other data, including output (e.g., the number of packages shipped within a specific time period) and input (e.g., the number of empty cardboard boxes received for use in shipping). The SAT system 101 can also act as a gateway between different devices in the system 100, enabling communication between devices (e.g., using storage and forwarding or other technologies) (e.g., using external front-end system 103 and FO system 113).

[0022] In some embodiments, the external front-end system 103 can be implemented as a computer system that enables external users to interact with one or more systems in the system 100. For example, in an embodiment where the system 100 enables the presentation of the system to allow users to place orders for items, the external front-end system 103 can be implemented as a web server that receives search requests, presents item pages, and requests payment information. For example, the external front-end system 103 can be implemented as a computer or multiple computers running software (e.g., Apache HTTP server, Microsoft Internet Information Service (IIS), NGINX, etc.). In other embodiments, the external front-end system 103 can run customized web server software that is designed to: receive and process requests from external devices (e.g., mobile device 102A or computer 102B), obtain information from databases and other data stores based on those requests, and provide responses to the received requests based on the information obtained.

[0023] In some embodiments, the external front-end system 103 may include one or more of a network cache 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, and in another aspect, the external front-end system 103 may include an interface (e.g., server-to-server, database-to-database, or other network connection) connected to one or more of these systems.

[0024] Depend on Figure 1B , Figure 1C , Figure 1D and Figure 1EA set of illustrative steps are shown to help describe some operations of the external front-end system 103. The external front-end system 103 can receive information from systems or devices in the system 100 for presentation and / or display. For example, the external front-end system 103 can host or provide one or more web pages, including: a search result page (Search Result Page, SRP) (e.g., Figure 1B ), Single Detail Page (SDP) (e.g., Figure 1C ), shopping cart pages (e.g. Figure 1D ) or order pages (e.g. Figure 1E ). A user device (e.g., using mobile device 102A or computer 102B) can navigate to the external front-end system 103 and request a search by entering information into a search box. The external front-end system 103 can request information from one or more systems in the system 100. For example, the external front-end system 103 can request information that satisfies the search request from the FO system 113. The external front-end system 103 can 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 can represent an estimate of when a package containing the product will arrive at the user's desired location, or if the product is ordered within a specific time period (e.g., by the end of the day (11:59 p.m.)), the date the product is promised to be delivered to the user's desired location (the PDD will be discussed further below with respect to the FO system 113).

[0025] The external headend system 103 may prepare an SRP based on this information (e.g., Figure 1B ). The SRP may include information that satisfies the search request. For example, this may include pictures of products that satisfy the search request. The SRP may also include the respective price of each product, or information related to enhanced delivery options for each product, PDD, weight, size, quotes, discounts, etc. The external front-end system 103 may send the SRP to the requesting user device (e.g., via a network).

[0026] The user device may then select a product from the SRP, for example, by clicking or tapping a user interface, or using another input device, to select a product presented on the SRP. The user device may formulate an information request for the selected product and send the request to the external front-end system 103. In response, the external front-end system 103 may request information related to the selected product. For example, the information may include additional information beyond the information presented for the product on the respective SRP. This may include, for example, a shelf life, country of origin, weight, size, number of items in a package, instructions for use, or other information about the product. The information may also include recommendations for similar products (e.g., based on big data and / or machine learning analysis of customers who purchased the product and at least one other product), answers to common questions, reviews from customers, manufacturer information, pictures, etc.

[0027] The external front-end system 103 may prepare an SDP (Single Detail Page) based on the received product information (e.g., Figure 1C ). The SDP may also include other interactive elements, such as a "Buy Now" button, an "Add to Cart" button, a quantity field, a picture of the item, etc. The SDP may also include a list of sellers offering the product. The list may be sorted based on the price offered by each seller, so that the seller offering the product for sale at the lowest price may be listed at the top. The list may also be sorted based on the seller ranking, so that the highest ranked seller may be listed at the top. The seller ranking may be formulated based on multiple factors, including, for example, the seller's past track record of meeting the promised PDD. The external front-end system 103 may deliver the SDP to the requesting user device (e.g., via a network).

[0028] The requesting user device may receive an SDP listing product information. After receiving the SDP, the user device may then interact with the SDP. For example, a user of the requesting user device may click or otherwise interact with a "Place in Cart" button on the SDP. This will add the product to a shopping cart associated with the user. The user device may transmit the request to the external front-end system 103 to add the product to the shopping cart.

[0029] The external front-end system 103 may generate a shopping cart page (e.g., Figure 1D). In some embodiments, the shopping cart page lists the products that the user has added to the virtual "shopping cart". The user device can request the shopping cart page by clicking on an icon on the SRP, SDP or other page or otherwise interacting with an icon on the SRP, SDP or other page. In some embodiments, the shopping cart page can list all the products that the user has added to the shopping cart, as well as information about the products in the shopping cart, such as the quantity of each product, the price of each item of each product, the price of each product based on the associated quantity, information about the PDD, the delivery method, the shipping cost, the user interface elements for modifying the products in the shopping cart (e.g., deleting or modifying the quantity), the option to order other products or set up regular delivery of products, the option to set up interest payments, the user interface elements for continuing to purchase, etc. The user at the user device can click on the user interface element (e.g., a button that reads "Buy Now") or otherwise interact with the user interface element to initiate the purchase of the products in the shopping cart. After doing so, the user device can send the request to the external front-end system 103 to initiate the purchase.

[0030] The external front-end system 103 may generate an order page (eg, Figure 1E ). In some embodiments, the order page re-lists the items from the shopping cart and requests entry of payment and shipping information. For example, the order page may include portions requesting information about the purchaser of the items in the shopping cart (e.g., name, address, email address, phone number), information about the recipient (e.g., name, address, phone number, delivery information), shipping information (e.g., speed / method of delivery and / or pickup), payment information (e.g., credit card, bank transfer, check, stored credit), and user interface elements requesting a cash receipt (e.g., for tax purposes), etc. The external front-end system 103 may send the order page to the user device.

[0031] The user device may enter information on the order page and click or otherwise interact with user interface elements that send information to the external front end system 103. From there, the external front end system 103 may send information to different systems in the system 100 to initiate the creation and processing of a new order with the products in the shopping cart.

[0032] In some embodiments, external front-end system 103 may also be configured to enable the seller to send and receive information related to the order.

[0033] In some embodiments, the internal front-end system 105 can be implemented as a computer system that enables internal users (e.g., employees of an organization that owns, operates, or leases the system 100) to interact with one or more systems in the system 100. For example, in an embodiment where the system 100 enables the presentation of the system to allow users to place orders for items, the internal front-end system 105 can be implemented as a web server that enables internal users to: view diagnostic and statistical information about orders, modify item information, or check statistics related to orders. For example, the internal front-end system 105 can be implemented as a computer or multiple computers running software (e.g., Apache HTTP Server, Microsoft Internet Information Services (IIS), NGINX, etc.). In other embodiments, the internal front-end system 105 can run customized web server software that is designed to: receive and process requests from systems or devices described in the system 100 (as well as other devices not described), obtain information from databases and other data stores based on those requests, and provide responses to the received requests based on the information obtained.

[0034] In some embodiments, the internal front-end system 105 may include one or more of a network cache system, a database, a search system, a payment system, an analysis system, an order monitoring system, etc. 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 may include an interface (e.g., server-to-server, database-to-database, or other network connection) connected to one or more of these systems.

[0035] In some embodiments, the transportation system 107 can be implemented as a computer system capable of communicating between the systems or devices in the system 100 and the mobile devices 107A-107C. In some embodiments, the transportation system 107 can receive information from one or more mobile devices 107A-107C (e.g., mobile phones, smart phones, personal digital assistants (PDAs), etc.). For example, in some embodiments, the mobile devices 107A-107C can include devices operated by delivery workers. Delivery workers (who can be permanent, temporary, or shift employees) can use mobile devices 107A-107C to implement the delivery of packages containing products ordered by users. For example, in order to deliver a package, the delivery worker can receive a notification on the mobile device indicating which package to deliver and where to deliver it. After arriving at the delivery location, the delivery worker can locate the package (e.g., in the back of a truck or in a crate of the package), scan or otherwise capture data associated with an identifier on the package (e.g., a barcode, an image, a text string, a radio frequency identification (RFID) tag, etc.) using a mobile device, and deliver the package (e.g., by leaving the package at the front door, handing the package to a security guard, handing the package to the recipient, etc.). In some embodiments, the delivery worker can use the mobile device to capture one or more photos of the package and / or can obtain a signature. The mobile device can send a communication including information about the delivery (including, for example, the time, date, GPS location, photos, an identifier associated with the delivery worker, an identifier associated with the mobile device, etc.) to the transportation system 107. The transportation system 107 can store this information in a database (not shown) for access by other systems in the system 100. In some embodiments, the transportation system 107 can use this information to prepare and send tracking data to other systems, the tracking data indicating the location of a particular package.

[0036] In some embodiments, certain users may use one type of mobile device (e.g., a permanent worker may use a specialized PDA with customized hardware (e.g., a bar code scanner, stylus, and other devices)) while other users may use other types of mobile devices (e.g., temporary or shift workers may utilize off-the-shelf mobile phones and / or smartphones).

[0037] In some embodiments, the transportation system 107 may associate a user with each device. For example, the transportation system 107 may store an association between a user (represented by, for example, a user identifier, an employee identifier, or a phone number) and a mobile device (represented by, for example, an International Mobile Equipment Identity (IMEI), an International Mobile Subscription Identifier (IMSI), a phone number, a Universal Unique Identifier (UUID), or a Globally Unique Identifier (GUID)). The transportation system 107 may use this association in conjunction with data received at the time of delivery to analyze the data stored in the database to determine, among other things, the location of the worker, the efficiency of the worker, or the speed of the worker.

[0038] In some embodiments, seller portal 109 may be implemented as a computer system that enables sellers or other external entities to electronically communicate with one or more systems in system 100. For example, a seller may utilize a computer system (not shown) to upload or provide product information, order information, contact information, etc. for products that the seller wishes to sell through system 100 using seller portal 109.

[0039] In some embodiments, the shipping and order tracking system 111 may be implemented as a computer system that receives, stores, and forwards information about the location of a package containing products ordered by a customer (e.g., by a mobile device 102A or computer 102B). In some embodiments, the shipping and order tracking system 111 may request or store information from a network server (not shown) operated by a shipping company that delivers the package containing the products ordered by the customer.

[0040] In some embodiments, the shipping and order tracking system 111 can request and store information from the systems described in the system 100. For example, the shipping and order tracking system 111 can request information from the transportation system 107. As described above, the transportation system 107 can receive information from one or more mobile devices 107A-107C (e.g., mobile phones, smart phones, PDAs, etc.) associated with one or more users (e.g., delivery workers) or vehicles (e.g., delivery trucks). In some embodiments, the shipping and order tracking system 111 can also request information from a warehouse management system (WMS) 119 to determine the location of various products within a fulfillment center (e.g., fulfillment center 200). The shipping and order tracking system 111 can request data from one or more of the transportation system 107 or the WMS 119, process the data, and present the data to the device (e.g., mobile device 102A and computer 102B) upon request.

[0041] In some embodiments, fulfillment optimization (FO) system 113 may be implemented as a computer system that stores information about customer orders from other systems (e.g., external front-end system 103 and / or shipping and order tracking system 111). FO system 113 may also store information describing where specific items are held or stored. For example, certain items ordered by customers may be stored in only one fulfillment center, while certain other items may be stored in multiple fulfillment centers. In other embodiments, certain fulfillment centers may be designed to store only a specific set of items (e.g., fresh produce or frozen products). FO system 113 stores this information as well as associated information (e.g., quantity, size, receipt date, expiration date, etc.).

[0042] 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 factors. For example, the FO system 113 may calculate the PDD of a product based on past demand for the product (e.g., how many times the product was ordered in a period of time), expected demand for the product (e.g., how many customers are predicted to order the product in an upcoming period of time), past demand for the entire network indicating how many products were ordered in a period of time, expected demand for the entire network indicating how many products are expected to be ordered in an upcoming period of time, one or more counts of products stored in each fulfillment center 200, which fulfillment center each product is stored in, expected orders or current orders for the product, etc.

[0043] In some embodiments, the FO system 113 may determine the PDD for each product periodically (e.g., hourly) and store the PDD in a database for retrieval or transmission to other systems (e.g., external front-end system 103, SAT system 101, shipping and order tracking system 111). In other embodiments, the FO system 113 may receive electronic requests from one or more systems (e.g., external front-end system 103, SAT system 101, shipping and order tracking system 111) and calculate the PDD as needed.

[0044] In some embodiments, fulfillment messaging gateway (FMG) 115 may be implemented as a computer system that receives a request or response from one or more systems in system 100 (e.g., FO system 113) in one format or protocol, converts the request or response to another format or protocol, and forwards the request or response to other systems (e.g., WMS 119 or third-party fulfillment systems 121A, 121B, or 121C) in the converted format or protocol, or vice versa.

[0045] In some embodiments, supply chain management (SCM) system 117 may be implemented as a computer system that performs forecasting functions. For example, SCM system 117 may forecast the level of demand for a particular product based on, for example, past demand for the product, expected demand for the product, past demand across the network, expected demand across the network, count products stored in each fulfillment center 200, expected orders or current orders for each product, etc. In response to the forecasted level and the quantity of each product across all fulfillment centers, SCM system 117 may generate one or more purchase orders to purchase and restock sufficient quantities to meet the forecasted demand for the particular product.

[0046] In some embodiments, warehouse management system (WMS) 119 may be implemented as a computer system that monitors workflow. For example, WMS 119 may receive event data indicating discrete events from various devices (e.g., devices 107A-107C or devices 119A-119C). For example, WMS 119 may receive event data indicating that a package was scanned using one of these devices. As described below with respect to fulfillment center 200 and Figure 2As discussed, during the fulfillment process, a package identifier (e.g., barcode or RFID tag data) may be scanned or read by a machine at a particular stage (e.g., an automatic or handheld barcode scanner, RFID reader, high-speed camera, device (e.g., tablet 119A), mobile device / PDA 119B, computer 119C, etc.). The WMS 119 may store each event indicating a scan or read of a package identifier in a corresponding database (not shown) along with the package identifier, time, date, location, user identifier, or other information, and may provide this information to other systems (e.g., shipping and order tracking system 111).

[0047] In some embodiments, the WMS 119 may store information associating one or more devices (e.g., devices 107A-107C or devices 119A-119C) with one or more users associated with the system 100. For example, in some cases, a user (e.g., a part-time or full-time employee) may be associated with a mobile device because the user owns the mobile device (e.g., the mobile device is a smartphone). In other cases, a user may be associated with a mobile device because the user temporarily keeps the mobile device (e.g., the user checks in the mobile device at the beginning of the day, will use it during the day, and will return it at the end of the day).

[0048] In some embodiments, the WMS 119 can maintain a work log for each user associated with the system 100. For example, the WMS 119 can store information associated with each employee, including any specified process (e.g., unloading a truck, picking items from a picking area, rebin wall work, packaging items), a user identifier, a location (e.g., a floor or zone in a fulfillment center 200), a number of units moved through the system by the employee (e.g., number of items picked, number of items packaged), an identifier associated with an appliance (e.g., appliances 119A-119C), etc. In some embodiments, the WMS 119 can receive check-in and check-out information from a timekeeping system (e.g., a timekeeping system operating on appliances 119A-119C).

[0049] In some embodiments, third-party fulfillment (3PL) systems 121A-121C represent computer systems associated with third-party suppliers of logistics and products. For example, while some products are stored in fulfillment center 200 (as described below with reference to Figure 2), but other products may be stored off-site, may be produced on demand, or may not otherwise be stored in fulfillment center 200. 3PL systems 121A-121C may be configured to receive orders from FO system 113 (e.g., via FMG 115) and may provide products and / or services (e.g., delivery or installation) directly to customers. In some embodiments, one or more of 3PL systems 121A-121C may be part of system 100, while in other embodiments, one or more of 3PL systems 121A-121C may be external to system 100 (e.g., owned or operated by a third-party provider).

[0050] In some embodiments, the fulfillment center authorization system (FC authorization) 123 can be implemented as a computer system with various functions. For example, in some embodiments, the FC authorization 123 can act as a single sign-on (SSO) service for one or more other systems in the system 100. For example, the FC authorization 123 can enable a user to log in via the internal front-end system 105, determine that the user has similar privileges to access resources at the shipping and order tracking system 111, and enable the user to access these privileges without a second login process. In other embodiments, the FC authorization 123 can enable users (e.g., employees) to associate themselves with specific tasks. For example, some employees may not have electronic devices (e.g., devices 119A-119C), but can instead move from one task to another and from one zone to another in the fulfillment center 200 during the course of a day. The FC authorization 123 can be configured to enable these employees to indicate what tasks they are performing and what zones they are in at different times of the day.

[0051] In some embodiments, a 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, the LMS 125 may receive information from the FC authority 123, the WMA 119, the devices 119A-119C, the transportation system 107, and / or the devices 107A-107C.

[0052] Figure 1A The specific configurations described in are examples only. Figure 1AThe FC authorization system 123 connected to the FO system 113 is described, but not all embodiments require this particular configuration. In fact, in some embodiments, the systems in the system 100 can be connected to each other through one or more public or private networks, including the Internet, an intranet, a WAN (wide area network), a MAN (metropolitan area network), a wireless network compliant with the IEEE 802.11a / b / g / n standard, a leased line, etc. In some embodiments, one or more systems in the system 100 can be implemented as one or more virtual servers implemented in a data center, a server farm, etc.

[0053] Figure 2 A fulfillment center 200 is depicted. A fulfillment center 200 is an example of a physical location where items are stored for shipment to customers when they are ordered. A fulfillment center (FC) 200 may be divided into multiple zones, where each zone has a Figure 2 In some embodiments, these "zones" can be thought of as virtual divisions between different stages of the process of receiving items, storing items, retrieving items, and shipping items. Figure 2 "Zones" are described in , but other divisions of zones are possible, and in some embodiments, Figure 2 The fields in may be omitted, repeated, or modified.

[0054] Inbound zone 203 indicates that you wish to use Figure 1A A seller of a product sold by system 100 receives items at an area of ​​FC 200. For example, a seller may deliver items 202A and 202B using truck 201. Item 202A may represent a single item that is large enough to occupy its own shipping pallet, while item 202B may represent a group of items that are stacked together on the same pallet to save space.

[0055] Workers will receive items in the inbound area 203, and can use a computer system (not shown) to optionally check the damage and correctness of the items. For example, workers can use a computer system to compare the quantity of items 202A and 202B with the order quantity of the items. If the quantity does not match, the worker can reject one or more of the items 202A or 202B. If the quantity matches, the worker can move these items to the buffer 205 (using, for example, a trolley, a hand truck, a forklift, or manually). For example, the buffer 205 can be a temporary storage area for items that are not currently needed in the picking area because there is a high enough number of these items in the picking area to meet the predicted demand. In some embodiments, the forklift 206 operates to move the items around the buffer 205 and between the inbound area 203 and the unloading area 207. If the items 202A or 202B are needed in the picking area (for example, due to predicted demand), the forklift can move the items 202A or 202B to the unloading area 207.

[0056] Drop-off area 207 may be an area of ​​FC 200 where items are stored before being moved to picking area 209. A worker assigned to a picking task (a "picker") may approach items 202A and 202B in the picking area, scan a barcode of the picking area using a mobile device (e.g., device 119B), and scan barcodes associated with items 202A and 202B. The picker may then bring the items to picking area 209 (e.g., by placing the items on a cart or carrying the items).

[0057] The picking area 209 may be an area of ​​the FC 200 where the items 208 are stored on the storage unit 210. In some embodiments, the storage unit 210 may include one or more of physical shelves, bookcases, boxes, totes, refrigerators, freezers, cold storage, etc. In some embodiments, the picking area 209 may be organized into multiple layers. In some embodiments, workers or machines may move items into the picking area 209 in a variety of ways, including, for example, forklifts, elevators, conveyor belts, carts, hand trucks, dollies, automatic robots or devices, or manually. For example, a picker may place the items 202A and 202B on a hand truck or cart in the drop-off area 207 and walk to load the items 202A and 202B to the picking area 209.

[0058] The picker may receive instructions to place (or "stack") an item at a specific point in the picking area 209 (e.g., a specific space on the storage unit 210). For example, the picker may use a mobile device (e.g., device 119B) to scan the item 202A. The device may indicate (e.g., using a system indicating aisles, shelves, and locations) where the picker should stack the item 202A. The device may then prompt the picker to scan a barcode at the location before stacking the item 202A at that location. The device may send data to a computer system (e.g., WMS 119 in FIG. 1 ) (e.g., via a wireless network) indicating that a user using the device 119B has stacked the item 202A at that location.

[0059] Once the user places an order, the picker can receive instructions on the device 119B to retrieve one or more items 208 from the storage unit 210. The picker can retrieve the items 208, scan the barcodes on the items 208, and place the items 208 on the transport device 214. In some embodiments, although the transport device 214 is shown as a slide, the transport device can be implemented as one or more of a conveyor belt, an elevator, a cart, a forklift, a hand truck, a dolly, a cart, etc. Then, the items 208 can arrive at the packaging area 211.

[0060] The packing area 211 may be an area of ​​the FC200 that receives items from the picking area 209 and packs the items into boxes or bags for final shipment to customers. In the packing area 211, a worker assigned to receive items ("merge worker") will receive items 208 from the picking area 209 and determine the order to which the items 208 correspond. For example, the merge worker may use a device (e.g., computer 119C) to scan a barcode on the item 208. The computer 119C may visually indicate which order the 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 (e.g., because the cell contains all the items of the order), the merge worker may indicate to the packing worker (or "packer") that the order is complete. The packing worker may retrieve the items from the cell and place the items in a box or bag for shipment. The packing worker may then send the box or bag to the hub area 213 (e.g., via a forklift, cart, trolley, hand truck, conveyor, manually, or otherwise).

[0061] Hub area 213 may be the area of ​​FC 200 that receives all boxes or bags ("parcels") from packaging area 211. Workers and / or machines in hub area 213 may retrieve parcels 218 and determine which portion of the delivery area each parcel is intended for, and route the parcels to the appropriate camp zone 215. For example, if the delivery area has two smaller sub-areas, the parcels will go to one of the two camp zones 215. In some embodiments, a worker or machine may scan the parcel (e.g., using one of devices 119A-119C) to determine the final destination of the parcel. Routing the parcel to a camp zone 215 may include, for example, determining (e.g., based on a zip code) a portion of a geographic area to which the parcel is destined and determining a camp zone 215 associated with that portion of the geographic area.

[0062] In some embodiments, camp area 215 may include one or more buildings, one or more physical spaces, or one or more areas where packages are received from hub area 213 for sorting packages into routes and / or sub-routes. In some embodiments, camp area 215 is physically separate from FC 200, while in other embodiments, camp area 215 may form part of FC 200.

[0063] Workers and / or machines in camp area 215 may determine which route and / or sub-route a package 220 should be associated with (e.g., based on a comparison of the destination to existing routes and / or sub-routes, a calculation of the workload for each route and / or sub-route, the time of day, the method of shipment, the cost of shipping package 220, the PDD associated with the items in package 220, etc.). In some embodiments, a worker or machine may scan a package (e.g., using one of devices 119A-119C) to determine the final destination of the package. Once a package 220 is assigned to a particular route and / or sub-route, the worker and / or machine may move the package 220 to be shipped. In an exemplary embodiment, a worker or machine may scan a package (e.g., using one of devices 119A-119C) to determine the final destination of the package. Once a package 220 is assigned to a particular route and / or sub-route, the worker and / or machine may move the package 220 to be shipped. Figure 2 2, camp area 215 includes trucks 222, cars 226, and delivery workers 224A and 224B. In some embodiments, truck 222 may be driven by delivery worker 224A, where delivery worker 224A is a full-time employee delivering packages for FC 200, and truck 222 is owned, leased, or operated by the same company that owns, leases, or operates FC 200. In some embodiments, car 226 may be driven by delivery worker 224B, where delivery worker 224B is a "flexible" or temporary worker who makes deliveries on an as-needed basis (e.g., seasonally). Car 226 may be owned, leased, or operated by delivery worker 224B.

[0064] Workers in FC 200 can include direct workers and indirect workers. Direct workers can handle the above Figure 2 The indirect workers may perform miscellaneous tasks that do not involve handling items. For example, the indirect workers may perform safety checks on machines associated with FC 200. Both workers punch in when they arrive at FC 200 and punch out when they leave FC 200. LMS 125 may be configured as described above with respect to Figure 1A As described, attendance information associated with clocking in and clocking out is received and stored. Although both workers clock in / out, in some embodiments, only the direct worker scans the item.

[0065] Figure 3 is a schematic block diagram illustrating an exemplary embodiment of a network including a computerized system for monitoring logistics. Figure 3 As shown, system 300 may include various systems, each of which may be connected to each other via one or more networks. These systems may also be connected to each other via direct connections (e.g., using cables). The described systems include management optimization system (MOS) 301, fulfillment optimization (FO) system 113, warehouse management system 119, mobile devices 119A, 119B and 119C (described as being inside fulfillment center (FC) 200), fulfillment center authorization system (FC Auth) 123 and labor management system (LMS) 125.

[0066] In some embodiments, system 300 can implement LMS 125 to capture attendance and overtime information about the first plurality of workers. Figure 1A As discussed, LMS 125 may be implemented as a computer system that stores attendance and overtime information for employees (including full-time and part-time employees). LMS 125 may provide information to MOS 301 in the form of data.

[0067] Similarly, system 300 can implement WMS 119 to capture data identifying work performed by a second plurality of workers. The data may include, but is not limited to: the location where the work was performed; associated scanning events; or check-in information associated with each of the second plurality of workers. For example, as described above with respect to Figure 1AAs discussed, the WMS 119 may be implemented as a computer system that monitors the workflow. The WMS 119 may receive event data indicating discrete events from various devices (e.g., devices 107A-107C or 119A-119C), and store each event indicating scanning or reading a package identifier in a corresponding database (not shown) together with the package identifier, time, date, location, user identifier, or other information, and may provide this information to the MOS 301 in the form of data.

[0068] As mentioned above Figure 1A As discussed, the WMS 119 can store information associating one or more devices with one or more users associated with the system 100 and maintain a work log for each user associated with the system 100. In some embodiments, the WMS 119 can also receive sign-in and sign-out information from a timekeeping system (e.g., a timekeeping system operating on the devices 119A-119C). The WMS 119 can provide the stored information, the maintained work log, and the information from the timekeeping system to the MOS 301 in the form of data.

[0069] Additionally, in some embodiments, the system 300 may implement FC Auth 123 to capture work data associated with a third plurality of workers. Figure 1A As discussed, FC Auth 123 may be implemented as a computer system with a single sign-on (SSO) service that enables users (e.g., employees) to associate themselves with specific tasks, and is configured to enable these employees to indicate what tasks they are performing at different times of the day and what areas they are in. FC Auth 123 may aggregate the information about the employees discussed above and provide the information to MOS 301 in the form of data.

[0070] In some embodiments, system 300 may implement FO 113 to capture order data and fulfillment center data. Figure 1A As discussed, FO 113 may be implemented as a computer system that stores information about customer orders from other systems and information describing where specific items are held or stored. FO 113 may provide the stored information to MOS 301 in the form of data.

[0071] In some embodiments, system 300 may implement MOS 301. MOS 301 may merge received data about workers with corresponding data provided by at least one of LMS 125, WMS 119, FCAuth 123, and FO 113 into one of the received multiple data sets. For example, MOS 301 may combine the received data, parse the combined data about the workers, and sort the data into a profile of a single worker or a group of workers.

[0072] MOS 301 can operate on the merged data to realize a monitoring logistics tool. MOS 301 can provide: work performance; work status; number of workers in each process; reallocation progress of items within the fulfillment center; attendance status showing abnormal attendance; job distribution; worker activity history; inventory transfer status; product order status; reports and details on shipment summary, fulfillment center, PDD missing details and order tracking details; and delivery status in FC, and identify trends in work performance, underperforming workers and underperforming jobs.

[0073] In some embodiments, MOS 301 may be configured to generate an interface for presentation to a user via a display device (e.g., user device 302). MOS 301 may render data into a form ready for presentation and manipulation. MOS 301 may employ any component or subsystem suitable for user interface generation, such as Java Script. In some embodiments, MOS 301 may employ AngularJS, Node.js as a middleware HTTP server, D3.js for highly customized, interactive visualization, and / or any of various other open source UI / UX engineering components (e.g., Bootstrap, SASS, and Grunt.js).

[0074] The user device 302 may be a tablet, a computer, or any suitable device with computing capabilities that enables the user device 302 to communicate with the MOS 301. The user device 302 may transmit a visualization request including an analysis of the merged data to the MOS 301. Upon receiving the request from the user device 302, the MOS 301 may provide the generated interface to the user device 302, wherein the interface is generated by analyzing the merged data.

[0075] Figure 4 is a flow chart of an exemplary process 600 for processing data to monitor logistics consistent with the disclosed embodiments. Figure 4, in step 410, MOS 301 can capture attendance data and timing data for the first plurality of workers. MOS 301 can receive these data from LMS 126. In step 420, MOS 301 can also capture data identifying work performed by a second plurality of workers from WMS 119. The data can include, but is not limited to, the location where the work is performed, associated scanning events, or sign-in information associated with each of the second plurality of workers. The work performed can include unloading inbound items from a delivery truck, picking inbound items, stacking items, redistributing items, and packaging at least one delivery package within the fulfillment center. The location of the work performed is determined by receiving a location sent from an automatic or handheld barcode scanner, an RFID reader, a high-speed camera, or a device with communication capabilities.

[0076] In step 430, MOS 301 may capture work data associated with the third plurality of workers from FC Auth 123. The data may include: single sign-on (SSO) service information indicating the association between a user and a particular task; and tracking and check-in information for temporary workers who do not scan any items and float from one task to another. In step 440, MOS 301 may also capture order data and fulfillment center 200 related data from FO 113. The data may include customer order information and information describing the location where a particular item is held or stored.

[0077] In step 450, MOS 301 may receive a user request for a visualization of analytics of any captured data obtained by MOS 301 from user device 302. The request may include parameters identifying one or more categories of one or more workers. For example, a manager in fulfillment center 200 using user device 302 may provide a request to MOS 301 to provide a visualization of analytics extracted from captured data. The request may include parameters including attendance associated with the worker and scan events associated with the worker.

[0078] In step 460, MOS 301 may merge the captured data about the workers with corresponding data from steps 410, 420, 430, and 440 into one of the captured multiple data sets based on the parameters provided in step 450. For example, MOS 301 may combine the captured data based on the parameters provided by the user device. The parameters may include, but are not limited to, attendance data associated with the workers and scanning events associated with the workers as described above. MOS 301 may parse the captured data about the workers and sort the data into profiles for individual workers or groups of workers.

[0079] In step 470, MOS 301 may generate user visualizations. MOS 301 may first operate the merged data to generate work performance; work status; number of workers in each process; reallocation progress of items within the fulfillment center; attendance status showing abnormal attendance; job distribution; worker activity history; inventory transfer status; product order status; reports and details on shipping summaries, fulfillment centers, PDD missing details, and order tracking details; and delivery status in FC, identifying work performance, underperforming workers, and underperforming trends, and making inferences. MOS 301 may present the results of the analysis to the user in the form of a presentation via a display device (e.g., user device 302).

[0080] In step 480 , MOS 301 may provide the visualization to user device 302 for display. Figure 5A-Figure 5O An exemplary visualization is described in . Upon receiving the parameters for merging the captured data, MOS 301 may provide a user interface screen displaying the analysis results of the merged data. The user may select different views of the merged data (e.g., Figure 5A The units processed per hour by the workers associated with each production line in Figure 5B The user can also provide different parameters to MOS 301 to merge different types of data and provide analysis results of the merged data.

[0081] Figure 5A-Figure 5O An exemplary user interface for monitoring a logistics tool is described. Figure 5A-Figure 5O In some embodiments, the user device 302 may execute a browser application capable of presenting various types of interactive content to the user. MOS 301 may be configured to generate Figure 5A-Figure 5O , as part of step 470 of process 400.

[0082] like Figure 5A As shown, interface 500 can provide the performance of each production line within fulfillment center 200 by displaying the units processed per hour (UPH) per production line, where a production line is composed of a group of workers performing the same task. For example, indicator 501 can present a production line that exceeds target 503 through a graphical presentation, while indicator 502 can present a production line that fails to reach target 503 through a graphical presentation. The tasks may include packing, picking, and re-sorting (reallocating) items within fulfillment center 200.

[0083] In some embodiments, the exemplary interface 500 enables the user device 302 to provide parameters by using the search bar 504 of the MOS 301 to merge data associated with the provided parameters and provide analysis results of the merged data. The search bar 504 enables the user device 302 to configure the fulfillment center, date, production line, and operating hours for merging associated data.

[0084] Figure 5B Another interface 510 is described that provides the current status of worker assignments for each production line, UPH trends by time, and detailed status for packing stations. The current status provides the total number of workers for the production line, the number of temporary workers, the number of permanent workers, the target UPH, and the current UPH. The trend of UPH is presented in the form of a chart. The detailed status of the packing station provides the workers assigned to the packing station, the status of each worker, the performance of each worker, the UPH of each worker, the time when the worker last scanned an item, and the time elapsed since the worker last scanned an item. Figure 5B The description is made with respect to packaging, but one of ordinary skill will appreciate that similar interfaces can be generated for other tasks (eg, picking).

[0085] In some embodiments, the exemplary interface 510 enables the user device 302 to provide parameters by using the filter 511 of the MOS 301 to merge data related to the provided parameters and provide analysis results of the merged data. The filter 511 enables the user device 302 to configure tasks (e.g., packaging or sorting), fulfillment centers, and production lines within the fulfillment center. For example, the exemplary interface 510 depicts the current status and detailed status of packaging by production line 2 within FC2.

[0086] In some embodiments, the exemplary interface 510 can enable the user device 302 to filter the workers in the production line according to their status by using a drop-down box 512 for MOS 301 to merge the data associated with the filtered workers. The drop-down box 512 can provide the status of Moved, WIP, and ALL for the worker to select from the user device 302. The Moved state represents a worker who previously worked in the current station (e.g., the Pack Station in the exemplary interface 510) but is currently working in another station or other tasks. The WIP state represents a worker who is currently working in the current station (e.g., the Pack Station in the exemplary interface 510), and the ALL state includes workers with WIP or Moved status. When MOS 301 receives the status of the worker, MOS 301 can merge the data associated with the selected status of the worker (e.g., WIP in the exemplary interface 510), for example, MOS 301 can determine the status of the worker based on the punch-in information associated with the worker.

[0087] In some embodiments, the exemplary interface 510 can enable the user device 302 to filter the workers in the production line according to their performance levels by merging the data associated with the filtered workers using a drop-down box 513 for the MOS 301. The drop-down box 513 can provide the workers with performance levels of low performance and ALL for the user device 302 to select. Low performance represents workers whose UPH is below the target UPH (e.g., workers B, C, and D in the exemplary interface 510), while ALL represents all workers in the production line, regardless of their performance level (e.g., workers A, B, C, and D). When the MOS 301 receives the performance level of the workers for filtering, the MOS 301 can merge the data associated with the performance level of the selected workers (e.g., ALL in the exemplary interface 510).

[0088] Figure 5C Describes the average UPH of workers per hour, Figure 5D Describes the worker's UPH over the past two weeks. Figure 5C and Figure 5D The UPH provided in the can provide managers associated with a worker with information about the worker's performance on a particular date ( Figure 5C ) or the past two weeks ( Figure 5D ) performance. In some embodiments, MOS 301 may be Figure 5C-5D The same manner of presentation provides the user device 302 with one or more UPHs associated with one or more workers.

[0089] Figure 5EAnother interface 520 is described which provides the current status of the picking process within the FC 200 (described above with respect to Figure 2 The interface 520 provides worker allocations for each process within a location in the FC. For example, if too many workers are assigned to a process, the interface 520 can alert the user by presenting a different colored indicator on a process and its exact location. The interface 520 is updated based on real-time data. For example, when a worker scans an item in a sorting area, the WMS 119 can transmit data associated with the scanning event to the MOS 301, and the MOS 301 can update the interface 520 accordingly.

[0090] Fig. 5F Another interface 530 is described that provides the current status of the reallocation of items (Rebins) stored in the FC. The interface 530 can present the ratio of completed reallocations, ongoing reallocations, and backlogged reallocations. The interface 530 can also present the time progress of the reallocations in the form of a chart. The interface 530 is updated based on real-time data. For example, when a worker scans an item in the FC 200 to rebin the item, the WMS 119 can transmit data associated with the scanning event to the MOS 301, and the MOS 301 can update the interface 530 accordingly. The interface 530 can also provide filters for the user device 302 to configure parameters for the MOS 301 to merge data according to the configuration.

[0091] Figure 5G Another interface 540 is described that provides a log of the worker's work progress during a predefined time period. MOS 301 can generate interface 540 by combining attendance data with data associated with at least one scan event. The log provides a complete history of the worker, including employee ID, name, clock-in / clock-out time, scan events, work type (process), location, start time and end time of each event, and the number of units associated with each event. Interface 540 can also provide filters for user device 302 to configure parameters for MOS 301 to merge data according to the configuration.

[0092] Figure 5H Another interface 541 is described that provides open space ratio (OSR) progress status. The OSR progress status can trigger monitoring and control of reallocation and backlog. Based on this status, workers associated with user devices 302 can manually increase the number of reassignment slots and assign more workers to increase throughput. Interface 541 can also provide filters for user devices 302 to configure parameters for MOS 301 to merge data according to the configuration.

[0093] Fig.5I Another interface 545 is described that provides a breakdown of PDD absences in a camp. The breakdown may include reasons for PDD absences and the number of absences over time. Interface 545 may also provide filters for user device 302 to configure parameters for MOS 301 to merge data according to the configuration.

[0094] Figure 5J Another interface 546 is described that provides the status of deliveries in the camp. The status shows how delivery tasks are distributed between permanent workers (CDM) and temporary workers (FLEX) in the camp, and provides progress, the number of undelivered items, the number of delivered items, the number of items to be delivered, and the number of items that cannot be delivered (N / A). For permanent workers, interface 508 can present the expected delivery completion time.

[0095] Figure 5K Another interface 550 is described that provides a breakdown of attendance status and abnormal attendance status in FC 200. MOS 301 can generate interface 550 by combining attendance data with data associated with at least one scan event. MOS 301 can also use information associated with clocking in or information associated with workers provided by LMS 125. The status can provide the exact number of abnormal attendance status cases and the corresponding employees. An abnormal attendance status case is determined when a worker is associated with no work log and no clocking in. For example, when a worker is not associated with clocking in time, it is expected that the worker has no clocking out time.

[0096] Figure 5L Another interface 560 is described that provides job distribution in FC 200. Job distribution can provide how many workers are currently assigned to each process, which will lead to better labor planning. MOS 301 can generate interface 560 by using at least one of data associated with at least one scan event, information associated with punching in, or information associated with a worker provided by LMS 125.

[0097] Figure 5M Another interface 570 is described, which monitors the production lines associated with the packaged items. The interface 570 can provide the current number of packaging personnel in each production line, the manager of each production line, the gross UPH trend of the production line per hour, and the underperforming production lines determined by comparison with the target UPH.

[0098] Figure 5NAnother interface 580 is described, which monitors the workers in the production line associated with the packaged items. The interface 580 can provide the total number of workers assigned to the production line, the number of workers on call, and the performance of the workers in each production line. The interface 580 can also highlight the workers who are not working or the workers who are performing poorly, and notify the managers associated with the highlighted workers.

[0099] Fig.5O Another interface 590 is described that provides a total UPH trend and work status for the day. The total UPH trend report helps the user easily determine the current status of the FC 200. These metrics are based on unified standards, and the FC 200 and the financial team associated with the FC 200 can rely on the report. The work status report for the day can provide real-time information on the percentage of work completed on time, work completed but not completed at one time, and work not completed. The report can provide signals to reallocate workers during the day. For example, if a task is heavy with uncompleted work when compared to other tasks, then MOS 301 can provide signals to reallocate workers to relieve the heavy tasks.

[0100] Although the present disclosure has been shown and described with reference to the specific embodiments of the present disclosure, it should be understood that the present disclosure can be implemented in other environments without modification. The foregoing description is presented for the purpose of illustration. This is not exhaustive and is not limited to the precise form or embodiment disclosed. By considering the specification and practice of the disclosed embodiments, modifications and adjustments will be apparent to those skilled in the art. In addition, although the various aspects of the disclosed embodiments are described as being stored in a memory, it will be understood by those skilled in the art that these aspects may also be stored in other types of computer-readable media, such as auxiliary storage devices (such as hard disks or CD ROMs), or other forms of RAM or ROM, USB media, DVDs, Blu-ray discs or other optical drive media.

[0101] Computer programs based on written description and open methods are within the skill range of experienced developers. Any technology known to those skilled in the art can be used to create various programs or program modules, or various programs or program modules can be designed in conjunction with existing software. For example, program parts or program modules can be designed in the following methods or by the following methods: .Net Framework, .Net Compact Framework (and related languages, such as VisualBasic, C etc.), Java, C++, Objective-C, HTML, HTML / AJAX combination, XML or HTML comprising Javaapplet.

[0102] In addition, although illustrative embodiments have been described herein, the scope of any and all embodiments with equivalent elements, modifications, omissions, combinations (e.g., aspects across multiple embodiments), adaptations and / or changes will be understood by those skilled in the art based on the content of this disclosure. The limitations in the claims will be broadly interpreted based on the language used in the claims and are not limited to the examples described in this specification or during the application of this application. These examples should be interpreted as non-exclusive. In addition, the steps of the disclosed method can be modified in any way, including by reordering steps and / or inserting or deleting steps. Therefore, the description and examples are considered illustrative only, and their true scope and spirit are indicated by the full scope of the attached claims and their equivalents.

Claims

1. A computer-implemented system for monitoring logistics, the system comprising: a memory for storing instructions; and At least one processor configured to execute the following instructions: capturing attendance data and timekeeping data for a first plurality of workers from a first management system; capturing data identifying work performed by a second plurality of workers from a second management system, the data comprising: the location of the work performed, the associated scan event, or the check-in information associated with each worker of the second plurality of workers; capturing work data associated with a third plurality of workers from a third management system; receiving a first request for monitoring logistics from a user device based on a specific criterion, wherein the specific criterion is a usage amount for each search; determining usage of each search by the user device using a processor, the processor tracking how much storage is allocated for each search associated with a parameter within a predetermined time; Based on the determined usage, automatically selecting the parameter with the largest usage as the first parameter; merging the captured data about the worker having corresponding data into one of the captured plurality of data sets based on the selected first parameter; and A visualization is provided to the user device, wherein the visualization is generated by analyzing the merged data.

2. The computer-implemented system of claim 1 , wherein: The instructions also include notifying a mobile device associated with a manager of an underperforming worker based on the merged data.

3. The computer-implemented system of claim 1 , wherein: Work performed includes unloading inbound items from a delivery truck, picking inbound items, stowing items, redistributing items, and packing at least one delivery package within the fulfillment center.

4. The computer-implemented system of claim 1 , wherein: The location of work being performed is determined by receiving a location transmitted from an automated or handheld barcode scanner, RFID reader, high-speed camera, or device with communications capabilities.

5. The computer-implemented system of claim 1 , wherein: Providing visualization also includes providing an activity history associated with the worker by analyzing the merged data.

6. The computer-implemented system of claim 1 , wherein: The instructions also include: capturing order data and fulfillment center data from a fourth management system; receiving a second request from a user device, the second request including a second parameter identifying one or more categories of one or more workers; merging the captured data about the worker having corresponding data into one of the captured plurality of data sets according to the second parameter; Underperforming tasks including packing and shipping are reassigned to workers, each underperforming task being identified by reassignment data generated from the merged data.

7. The computer-implemented system of claim 1 , wherein: Visualization also includes: determining an abnormal attendance status by combining an identity of a worker associated with the work data with an associated scan event from the merged data; and Provides the identity of the worker whose attendance status is abnormal.

8. The computer-implemented system of claim 1 , wherein providing visualization further comprises providing performance of each fulfillment center, wherein the performance is determined by combining a number of scanning events, attendance data, and timing data from the merged data and is defined by how many units are processed by a worker associated with each fulfillment center in an hour.

9. The computer implemented system of claim 8, wherein the performance of each fulfillment center provided presents a trend of performance over time.

10. The computer implemented system of claim 1, wherein providing the visualization is performed in real time.

11. A computer-implemented method for monitoring logistics, the method comprising: capturing attendance data and timekeeping data for a first plurality of workers from a first management system; capturing data identifying work performed by a second plurality of workers from a second management system, the data comprising: the location of the work performed, the associated scan event, or the check-in information associated with each worker of the second plurality of workers; capturing work data associated with a third plurality of workers from a third management system; receiving a first request for monitoring logistics from a user device based on a specific criterion, wherein the specific criterion is a usage amount for each search; determining usage of each search by the user device using a processor, the processor tracking how much storage is allocated for each search associated with a parameter within a predetermined time; Based on the determined usage, automatically selecting the parameter with the largest usage as the first parameter; merging the captured data about the worker having corresponding data into one of the captured plurality of data sets based on the selected first parameter; and A visualization is provided to the user device, wherein the visualization is generated by analyzing the merged data.

12. The method of claim 11, further comprising notifying a mobile device associated with a manager of an underperforming worker based on the merged data.

13. The method according to claim 11, wherein: Work performed includes unloading inbound items from a delivery truck, picking inbound items, stowing items, redistributing items, and packing at least one delivery package within the fulfillment center.

14. The method according to claim 11, wherein: The location of work being performed is determined by receiving a location transmitted from an automated or handheld barcode scanner, RFID reader, high-speed camera, or device with communications capabilities.

15. The method according to claim 11, wherein: Providing visualization also includes providing an activity history associated with the worker by analyzing the merged data.

16. The method according to claim 11, further comprising: capturing order data and shipping data for the first plurality of workers from a fourth management system; receiving a second request from a user device, the second request including a second parameter identifying one or more categories of one or more workers; merging the captured data about the worker having corresponding data into one of the captured plurality of data sets according to the second parameter; Underperforming tasks are reassigned to workers, each underperforming task being identified by reassignment data generated from the merged data.

17. The method according to claim 11, wherein: Visualization also includes: determining an abnormal attendance status by combining an identity of a worker associated with the work data with an associated scan event from the merged data; and Provides the identity of the worker whose attendance status is abnormal.

18. The method of claim 11, wherein providing visualization further comprises providing performance of each fulfillment center, wherein the performance is determined by combining a number of scanning events, attendance data, and timing data from the combined data and is defined by how many units are processed by workers associated with each fulfillment center in one hour.

19. The method of claim 18, wherein the performance of each fulfillment center provided presents a trend of performance over time.

20. A computer-implemented system for monitoring logistics, the system comprising: a memory for storing instructions; and At least one processor configured to execute the following instructions: capturing attendance data and timekeeping data for a first plurality of workers from a first management system; capturing, from a second management system, data identifying work performed by a second plurality of workers, the data comprising: a location of the work performed, an associated scanning event, or check-in information associated with each of the second plurality of workers; capturing work data associated with a third plurality of workers from a third management system; receiving a first request for monitoring logistics from a user device based on a specific criterion, wherein the specific criterion is a usage amount for each search; determining usage of each search by the user device using a processor, the processor tracking how much storage is allocated for each search associated with a parameter within a predetermined time; Based on the determined usage, automatically selecting the parameter with the largest usage as the first parameter; In accordance with the selected first parameter, merging the captured data about the worker having corresponding data into one of the captured plurality of data sets; and A visualization is provided to the user device, wherein the visualization includes a job distribution showing worker allocations on each allocation flow based on the merged data.

Images