Automation interface network for warehouse and transportation management systems

Abstract

An interface network is described for a warehouse management system, a transportation management system, and a robotic control system. The interface network includes: (1) a storage device configured to store a plurality of basic unit instructions, one or more of the basic unit instructions having at least one procedure identifier; (2) at least one processor coupled to the storage device and a communication network; and (3) one or more components executable by the at least one processor and collectively configured to: (a) identify a facility location, (b) manage inventory within the facility location by the robotic control system manipulating robotic entities within the facility location under direction of the warehouse management system, and (c) coordinate transportation to and from the facility location with movement of inventory by the robotic entities within the facility location by coordinating between the transportation management system and the warehouse management system.

Description

[0001] AUTOMATION INTERFACE NETWORK FOR WAREHOUSE AND TRANSPORTATION MANAGEMENT SYSTEMS

[0002] CROSS-REFERENCE TO RELATED APPLICATION

[0003] This application claims the benefit under 35 U.S.C. § 119(e) of co-pending U.S. Provisional Patent Application No. 63 / 668,945 titled INTERFACE NETWORK FOR WAREHOUSE AND TRANSPORTATION MANAGEMENT SYSTEMS filed on July 9, 2024, which is herein incorporated by reference in its entirety for all purposes.

[0004] BACKGROUND OF THE DISCLOSURE

[0005] Traditional warehouse and transportation management systems (WMS and TMS) have evolved from manual, spreadsheet-based tracking methods to sophisticated, software-driven platforms. These systems are designed to improve the organization, efficiency, and flow of goods within and between facilities. Core WMS functions include tracking the arrival and departure of goods, maintaining precise inventory levels and locations, optimizing spatial utilization, and coordinating material handling tasks within a facility such as a warehouse. TMS platforms complement these capabilities by managing the routing, scheduling, and execution of goods movement between facilities across land, sea, and air transportation modes. In many cases, WMS and TMS platforms operate as intermediaries, processing directives from higher-level enterprise resource planning (ERP) systems and other business platforms that govern supply chain priorities, orders, and inventory policies. Increasingly, WMS and TMS platforms are integrated, enabling coordinated control over end-to-end logistics operations. Meanwhile, automation management systems responsible for directing robotic platforms have become increasingly common, often receiving task directives from WMS / TMS via human-machine interfaces. However, current approaches lack a unified framework capable of natively orchestrating physical automation across multiple facilities, vehicle types, and robotic platforms in real time.

[0006] SUMMARY OF THE DISCLOSURE

[0007] One aspect of the present disclosure is directed to an interface network that unifies the core functionalities of a warehouse management system (WMS), a transportation management system (TMS), and an automation management and robotic control system. In one embodiment, the interface network comprises a storage device configured to store a plurality of basic unit instructions, one or more of the basic unit instructions having at least one procedure identifier, at least one processor coupled to the storage device and a communication network, and one or more components executable by the at least one processor and collectively configured to enable a user to identify a facility location, manage inventory within the facility location by the robotic control system manipulating robotic entities within the facility location under direction of the warehouse management system, and coordinate transportation to and from the facility location with movement of inventory by the robotic entities within the facility location by coordinating between the transportation management system and the warehouse management system.

[0008] Embodiments of the interface network further may include providing information about the products contained on robotic entities, such as automated pallets, within the facility. This enables a user to manage the products in real-time. The user is presented a discrete 2D plan of the facility, with discrete elements of the facility being referred to as “cells” herein. The at least one processor further may be configured to provide an advanced shipping notice to provide notice of upcoming deliveries sent by the facility location to a receiving facility location. The processor further may be configured to coordinate with inbound and outbound transportation assets such as trucks, trailers, railcars, or other delivery vehicles by scheduling arrival and departure windows, assigning loading or unloading points, and updating routing or delivery status based on real-time facility conditions. When an order is accepted by the receiving facility location, an inbound order generated by the interface network may be processed by the receiving facility location. The at least one processor further may be configured to verify the products being shipped from the facility location to a receiving facility location. Once the products pass verification, the products may be moved to storage cells of the receiving facility location and may be displayed on a warehouse or zone dashboard. The at least one processor further may be configured to retrieve items from the facility location. A user may be provided detailed options to select and retrieve items. An item window may be provided to enable the user to view the selected item or items. The at least one processor further may be configured to identify an item to be positioned near a delivery point to be retrieved. A user may be able to provide an order notification to process the delivery of the item to a receiving party. The at least one processor further may be configured to enable a user to view items stored within the facility in real-time.

[0009] One aspect of the present disclosure is directed to a computer-readable medium including instructions which, when executed by a computing system, cause the computing system to carry out a method of identifying a facility location; managing inventory within a zone of the facility location by a warehouse management system; and manipulating robotic entities to effect the management of inventory by a robotic control system controlled by the warehouse management system in coordination with transportation activities related to inbound and outbound movement of goods by a transportation management system.

[0010] In embodiments of the computer-readable medium, the robotic entities located in discrete cells provide information about the products contained on the robotic entities to manage the products in the facility location.

[0011] In some embodiments, the computing system further is configured to provide an advanced shipping notice and an expected transportation schedule to provide notice of upcoming deliveries sent by the facility location to a receiving facility location. In some of these embodiments, when an order is accepted by the receiving facility location, an inbound order is processed by the receiving facility location and the transportation coordination system may also adjust internal scheduling and dock assignments based on live vehicle tracking data.

[0012] In some embodiments, the computing system further is configured to verify the products being shipped from the facility location to a receiving facility location. In some of these embodiments, once the products pass verification, the products are moved to storage cells of the receiving facility location and may be displayed on a warehouse dashboard.

[0013] In some embodiments, the computing system further is configured to retrieve items from the facility location. In some of these embodiments, a user is provided detailed options to select and retrieve items. In some of these embodiments, an item window is provided to enable the user to view the selected item or items.

[0014] In some embodiments, the computing system further is configured to identify an item to be positioned near a delivery point to be retrieved. In some of these embodiments, a user is able to provide an order notification to process the delivery of the item to a receiving party.

[0015] In some embodiments, the computing system further is configured to enable a user to view items stored within the facility location in real-time.

[0016] In some embodiments, the computing system further is configured to enable a user to manipulate positions of the robotic entities within the facility location and orchestrate the robotic entities interaction with inbound or outbound transport assets.

[0017] One aspect of the present disclosure is directed to a system having: (1) a cloud computing system, including a plurality of computing devices interconnected by a communications network; (2) a plurality of warehouse facilities; and (3) a transportation network, including a plurality of vehicles and routes between the plurality of warehouse facilities. A transportation management system (TMS) operates within the cloud computing system, the TMS configured to manage shipments between the plurality of warehouse facilities via the transportation network. A warehouse management system (WMS) operates within the cloud computing system. Each warehouse facility includes (a) a plurality of automated devices and (b) both a mission planner and a robotic control system (RCS) operating within a computing system of that warehouse facility, collectively configured to manage the location of products within that warehouse facility. The WMS is configured to interact with the TMS to coordinate shipments to and from a warehouse facility with timing and placement of certain products within that warehouse facility and to communicate high level directions to the mission planner based on that timing and placement. The mission planner is configured to send commands to the RCS to direct exactly where and when to move the products; and The RCS is configured to send commands to the automated devices to implement the commands received from the WMS.

[0018] In some embodiments, the TMS is further configured to coordinate the vehicles and monitor their travel progress across the transportation network and to update the WMS of a destination facility of any changes to an estimated time of arrival.

[0019] BRIEF DESCRIPTION OF DRAWINGS

[0020] The accompanying drawings are not intended to be drawn to scale. In the drawings, each identical or nearly identical component that is illustrated in various figures is represented by a like numeral. For purposes of clarity, not every component may be labeled in every drawing. In the drawings:

[0021] FIG. 1 is a view of a login screen of an interface network of an embodiment of the present disclosure;

[0022] FIG. 2 is a view of a map screen of the interface network;

[0023] FIG. 3 is a view of a warehouse dashboard screen of the interface network;

[0024] FIGS. 4-6 are views of a view of a zone dashboard screens of the interface network;

[0025] FIG. 7 is a view of an advanced shipping notice screen of the interface network;

[0026] FIGS. 8 and 9 are views of an inbound order notification screens of the interface network;

[0027] FIG. 10 is a view of an inventory scan screen of the interface network;

[0028] FIGS 11-13 are views of a put away screens of the interface network;

[0029] FIGS. 14-16 are views of picking instructions screens of the interface network;

[0030] FIGS. 17 and 18 are views of a pallet visualization screens of the interface network; FIG. 19 is a view of an outbound order notification screen of the interface network; FIGS. 20 and 21 are views of warehouse loading screens of the interface network; FIGS. 22-24 are views of three-dimensional warehouse visualization screens of the interface network;

[0031] FIG. 25 is a schematic representation of an interface network of another embodiment of the present disclosure;

[0032] FIG. 26 is a block diagram of one example of a computer system that may be used to perform processes and functions disclosed herein; and

[0033] FIG. 27 is a block diagram of an example system according to an embodiment.

[0034] DETAILED DESCRIPTION

[0035] Embodiments of the present disclosure are directed to an interface network for warehouse management, transportation management, automation management and robotic control systems that is configured with a graphic user interface, sometimes referred to as a “GUI” herein, to enable warehouse, transportation and automation management functions. The GUI provides a user friendly interface that enables a warehouse management professional to efficiently manage a facility. The interface network of the warehouse management system is designed to manage a variety of tasks and functions within the warehouse and further incorporates transportation coordination tasks typically handled by a transportation management system.

[0036] Aspects of the interface network of the warehouse management, transportation management and robotic control systems are directed to enabling a user to select / identify a facility location for management. Upon selection, the user is presented a warehouse dashboard for the selected facility to enable the user to manage day-to-day activities of the facility location. The user is presented with a discrete 2D plan of the facility location with all contained robotic entities and products. The user can manage inventory of products contained within the facility. The user can manipulate robotic entities contained within the facility. The warehouse dashboard is configured to allow the user to fully monitor all activity and provide input when manual intervention is required.

[0037] In one embodiment, the warehouse dashboard provides the user manage aspects of the products contained within the facility location. The interface network of the warehouse management, transportation management and robotic control systems further includes an advanced shipping notice to provide notice of upcoming deliveries sent by a facility to a receiving facility. When an order is accepted by the receiving facility, an inbound order generated by the interface network is processed by the receiving facility. The interface network of the warehouse management, transportation management and robotic control systems enables the user to inspect the products being shipped from one facility to another facility. It should be noted that products stored and transported on automated pallets orchestrated by the interface network are visible at all times and may be viewed by the user on the warehouse dashboard. The interface network further allows users to coordinate scheduling with inbound and outbound vehicles, assign loading and unloading points, and adjust routing or timing based on real-time updates, thereby fulfilling essential transportation management system functionality.

[0038] The interface network of the warehouse management, transportation management and robotic control systems further includes a picking dashboard to enable a user to retrieve items from the facility. The picking dashboard provides the user detailed options to selecting and retrieving items. An item window is provided to enable the user to view the selected item or items. In one embodiment, the system can be configured to select an order in which products are stacked on the automated pallet to ensure an efficient stacking order. This in turn determines an order in which automated pallets are moved from the storage area to the picking area where products are moved between automated pallets. Products can be moved between automated pallets in one of two ways, by a human as instructed by a picking screen of the user interface or by direct control of an articulating arm or gantry fitted with suction or grip hardware for the purpose of picking up boxes of products and moving them between automated pallets. Products can also be moved without the use of automated pallets by other robotic entities, such as humanoid robots. The interface network of the warehouse management, transportation management and robotic control systems further includes an outbound dashboard, such as a pop-up modal within the warehouse dashboard, in which the selected item or items are positioned near a delivery point, such as a loading dock, to be retrieved. The outbound dashboard of the interface network provides an order notification to process the delivery of the item or items to the receiving party. The interface network of the warehouse management, transportation management and robotic control systems further includes a 3D facility visualization to enable the user to view day-to-day activities using augmented or virtual reality technology.

[0039] Aspects of the interface network of the warehouse management, transportation management and robotic control systems are described below with reference to the drawing figures.

[0040] Interface Network

[0041] The interface network is a logistics operating platform designed to manage various interconnected systems tasked with the movement of items through a supply chain.

[0042] The interface network is a combination of a transportation management system, sometimes referred to as “TMS” herein, which manages the flow of items between facilities that manufacture, store and sell them, a warehouse management system, sometimes referred to as “WMS” herein, which manages the flow of items within those facilities, and an automation management system or robotic control system, referred to as “RCS” herein, which manages the communication and command of the robotic entities within those facilities. These functions are not siloed but integrated into a single system architecture, where WMS, TMS, and RCS operate as unified logic through the interface network. The integration of the TMS, WMS, and RCS functions provides an organized task list issued to human workers and robotic entities for execution, with directives from the combined system resulting in physical action by connected hardware without requiring intermediate HMI or API input. The interface network enables functions for specific hardware that execute formerly manual tasks automatically. The referenced hardware includes an autonomous mobile robot, sometimes referred to as an “AMR” herein, in the form of a shipping or automated pallet that carries items and conveys them around the facility and onto vehicles, a picking module that can move items between the AMRs, and supporting robotic entities, such as automated charging docks, stackers, lifts, and the like.

[0043] As mentioned above, the interface network includes a GUI to enable transportation and warehouse management functions. The GUI provides a user-friendly interface that enables the warehouse management professional to efficiently manage a warehouse facility and to coordinate transportation activities. The interface network of the warehouse management, transportation management and robotic control systems is designed to manage a variety of tasks and functions within the warehouse and while transporting products between warehouses.

[0044] Login Page

[0045] Referring to FIG. 1, when the interface network is initiated by the user, the first screen is the login page 10. From this page 10, a user can enter their credentials to access the program or get assistance with their credentials. The login page 10 will also interface with identification (“ID”) hardware, such as fingerprint readers.

[0046] Map Page

[0047] Referring to FIG. 2, a map page 20 shows a map 22 of the particular region the user operates in and the facilities, each indicated at 24, the user operates or interfaces with to perform the functions described herein. The facilities 24 are listed in a left-hand window 26, which shows the facility identifier and full address. The facilities 24 are represented by pins in their geographical location on the regional map 22 on the main screen of the map page 20. Selecting or identifying the facility 24 from the list on the lefthand window 26, which list is not shown but could be provided, or its pin on the map will bring the user to a warehouse dashboard of that particular facility. This unified map interface allows the user to oversee both facility- specific operations and the movement of goods between nodes in the network, further integrating transportation management into the same operational layer as warehouse and robotic functions.

[0048] Warehouse Dashboard

[0049] Referring to FIG. 3, in one embodiment, a warehouse dashboard 30 includes four windows 32a, 32b, 32c, 32d and a header 34. The header 34 shows the facility name and location, matching the information from the map page 20 and allows the user to change color modes. The window 32a on the lefthand side of the screen lists the different primary functions of the system. The functions provided by window 32a may include the following:

[0050] Identity and access management - manages the policies and technologies to ensure that the right users have the appropriate access to interface network resources.

[0051] Inbound - receives advanced shipping notices, sometimes referred to as “ASNs” herein, and manages unloading, inspecting / verification and putting away items that arrive at the selected facility.

[0052] Inventory Management - manages the inventory log of items in a facility and current stock levels. It also connects the items to an item master of the interface network, which is a record of all the key information about a particular item as further described in the item dashboard.

[0053] Outbound - manages the process of building mixed pallets, creating ASNs, inspecting / verifying and loading items onto vehicles to deliver them to another facility.

[0054] Transportation Management - manages the vehicle physically moving goods, both incoming and outgoing.

[0055] Warehouse Visualization - returns the user to the warehouse dashboard view as previously described.

[0056] Log Out - returns the user to the login page.

[0057] The window 32b on the righthand side of the screen shows the queue of upcoming activities in that facility. The window 32c in the upper righthand comer of the screen is the notifications window, where messages are issued to the user. In the center of the screen is the main screen identified by window 32d, which is a 2D plan of the entire selected facility. Zones have different uses designated by the user which determine what functions occur in each area. Zones along the perimeter of the facility have short term storage, interaction and circulation functions. Zones in the middle of the facility are for long term storage. The user can select a zone to access its zone dashboard.

[0058] The warehouse dashboard may be used to coordinate the movement of automated pallets and picking modules within the warehouse.

[0059] Light Mode

[0060] In some embodiments, the interface network of the warehouse management, transportation management and robotic control systems can include a light mode as an example of a different color mode available for all pages of the interface network. The user interface should not be limited by color and can accommodate any color combination.

[0061] Zone Dashboard

[0062] Referring to FIGS. 4-6, a zone dashboard 50, which may be integrated into the warehouse dashboard 30, can include a zoomed in view of a single zone from the warehouse dashboard 30. The facility includes a discrete 2D arrangement of cells, together indicated at 52. A cell 52 is a space used to position the associated hardware controlled by the interface network. Cells 52 can carry different designations, which dictate the functions that can occur in them. Those cell designations may include the following:

[0063] Circulation - pathways where the AMRs can travel between zones.

[0064] Interaction - items can be moved off or added to the AMRs by the picking module, become inspected / verified, and / or loaded and unloaded from a vehicle.

[0065] Storage - the AMRs may be positioned in the facility when not being actively used.

[0066] Vehicle - the AMRs may be positioned within the vehicle while being transported between facilities.

[0067] Picking - a cell designated for occupancy by the picking module or a human picker tasked with moving items from one AMR to another.

[0068] Doors - an opening in the facility where AMRs can load onto or unload from vehicles, such as a loading dock.

[0069] Inaccessible - areas the AMRs cannot occupy or pass through, such as walls, columns or any space designated as such by the user. The zone dashboard 50 allows the user to move around a zone by panning or scrolling, or to view adjacent zones by using the arrows (not shown). The zone dashboard 50 contains a drop-down key in the header. The key identifies the different cell designations stated on the previous page as well as the status of the connected hardware actively in the selected zone. Those and any other statuses may include the following:

[0070] Available - an AMR that is not carrying any items and is available to carry items. Inbound - an AMR that arrives in a facility carrying items to be stored and picked from.

[0071] Empty arriving AMRs are categorized as available.

[0072] Outbound - an AMR that is being loaded with items from the facility or any AMR designated to leave the facility.

[0073] Unavailable - an AMR that is out of service or disabled.

[0074] Advanced Shipping Notice

[0075] Referring to FIG. 7, an advanced shipping notice or ASN is a message of pending upcoming deliveries sent by a facility where one or more items are shipping from the facility to the receiving facility prior to shipment. This allows the receiving facility to review for errors, make last-minute changes and / or prepare for the arrival of the item(s). The ASN may be first received by the receiving facility through the notifications window in the upper righthand corner of the screen, e.g., window 32c in FIG. 3, which shows a preview to the user. Once selected, the full ASN pops up in a window 80 overlayed on the main screen of the zone dashboard 50. The user may request changes in a different menu or approve it to leave the shipping facility as is. The ASN also contains information on shipping times from the outbound facility and receiving times at the inbound facility and product information, such as manufacturer, quantity and weight, as well as the identity of the AMR the items are loaded on.

[0076] Inbound Order

[0077] Referring to FIGS. 8 and 9, when an order is accepted by the receiving facility through an ASN, it is scheduled to depart the outbound facility and the AMRs are loaded onto a vehicle for transportation to the receiving or outbound facility. The TMS function coordinates the transport vehicles and monitors their travel progress while the vehicle is enroute and updates the WMS of the receiving facility of any changes to the estimated time of arrival. The TMS function also controls the routes the vehicles travel, e.g., selecting highways and roads for trucks, assigning tracks for trains, navigating waterways for ships, and selecting airspace lanes for unmanned aerial vehicles. Travel progress data can be sent from the vehicle or the automated pallet, with other information, such as temperature data of an enclosed automated pallet, being sent as well. The receiving facility receives notifications on changes to the estimated arrival time of the vehicle, which allows it to reorganize facility activities to mitigate the impact of such changes. When the vehicle arrives, a notification appears in the notifications window and when that notification is selected a receiving window 90 (FIG. 8) pops up over the main screen. The receiving window 90 first runs through every AMR on the arriving vehicle, confirming the manifest from the TMS matches the ASN and also allows the user to review the list of items on each AMR. The user can approve the order, which permits the AMRs to unload themselves from the vehicle into designated facility interaction cells and puts the AMRs under the control of the WMS function of the receiving facility. The user can edit the order as shown on window 100 (FIG. 10).

[0078] Item Inspection / Verification

[0079] Referring to FIG. 10, the AMRs entering the receiving facility will position themselves in designated interaction cells in which the AMRs are inspected / verified through a 3-step process, which may include the following:

[0080] The expected weight of each AMR is measured against its actual weight as sensed by the onboard load cell of the AMR.

[0081] The items are scanned with the camera of the device running the interface network or the picking module and matched against an image of what the items should look like after a successful shipment on window 110.

[0082] Items are visually inspected by the user for damage or other defects.

[0083] Put Away

[0084] Referring to FIGS. 11-13, AMRs that pass inspection / verification are permitted to put themselves away by the user and they move to a designated storage cell. The interface network selects the storage position as shown in window 120 (FIG. 11) based on upcoming missions and moves other AMRs to accommodate access to the desired storage cell. The system shows the movements of all AMRs in real-time (FIGS. 12 and 13).

[0085] AMRs that do not pass inspection / verification may be positioned in a holding area or other location within the facility for future actions. Picking Dashboard

[0086] The process of taking one or more items off of one AMR and placing it on another AMR for the purposes of making a specific mix of items to fulfill a multi-item order may be referred to as picking. When a multi-item order is created, the interface network creates a group of items, which may be referred to as a stack, that ship well together based on predetermined criteria, such as the weight and dimensions of the item or the strength of its packaging. The interface network then assigns a picker (e.g., the robotic picking module) and designates a location for the pick to occur within the interaction area.

[0087] Referring to FIGS. 14 and 15, the interface network then sends the inbound AMR (depicted within the window labeled LP00625) with the items that need to be picked and an available AMR (depicted within the window labeled LP26673) to the designated interaction cells. As items, indicated at 160 in FIG. 14, are added to the available AMR, it becomes an outbound AMR. Inbound AMRs are sent to the newly formed outbound AMR with the required items in the order in which they need to be stacked, which is shown in window 170 in FIG. 15. In some embodiments, the interface network may provide a visual for the picker that shows the picker which item to move from the inbound AMR and where to place the item on the outbound AMR. The AMR can sense the load and load position and confirm the picker moves the correct item to the correct location. FIG. 16 shows a picking station window 180.

[0088] Item Window

[0089] Referring to FIGS. 17 and 18, when a cell containing an AMR is selected, the user interface brings up the item window 190 for that AMR. Items are stacked on the AMR purposefully and stacks are confirmed through a three-step inspection / verification process. In one embodiment, items can be stacked pursuant to a stacking system or process. Since the item stack is known, the interface network can find specific items anywhere in the stack when selected. Every item managed by the interface network has a digital record in the item master of the interface network, which includes an image of the item and all of the information listed in a case view.

[0090] Outbound Dashboard

[0091] Referring to FIGS. 19-21, a user can approve a new outbound order on window 210 (FIG. 19). As outbound AMRs are completed, the AMRs stage themselves near a predetermined location, e.g., the loading dock, that the AMRs are assigned to be picked up from for future use. Completed outbound AMRs go through the same inspection / verification process as inbound AMRs. Once the AMRs pass inspection / verification, they are approved to load on the vehicle and they are passed off to be managed by the embedded TMS. With the same system managing dock assignments, vehicle arrival timing, and route readiness, the process is seamless and does not require separate software or integration layers.

[0092] In one embodiment, when an automated pallet arrives carrying items and unloads from the vehicle, the WMS calls for the current weight and weight distribution from the load cells of the automated pallet and compares it to the known weight and weight distribution sensed at the inspection point at the preceding facility just before the automated pallet is loaded on the vehicle. In addition, the items can be visually scanned to sec if the image of the stacked items on arrival matches an image of the stacked items when it departed the preceding facility, much in the same manner the inspection process can scan barcodes or sense RFID of individual items in the stack on the outbound or inbound automated pallet for a more detailed comparison when required by the user. The images / scans can be captured by a mobile device (such as a cell phone) running the interface network, carried by a user, or with the cameras and scanners embedded in the robotic picking module.

[0093] Facility Visualization Dashboard

[0094] Referring to FIGS. 22-24, the interface network has the ability to show the real-time facility activities in a 3-dimensional (3D) rendered view by selecting the “Warehouse Visualization” button or tab. The same interaction points, meaning the ability to select cells and AMR avatars, can occur from the 3D view. The interface network is also able to leverage augmented and virtual reality technology to display a 3D rendered view.

[0095] FIG. 25 illustrates an example of an interface network, which is generally indicated at 220. As shown, a global cloud 222 embodies a cloud-based data storage and processing system. The global cloud includes a cloud user interface 224, which provides a point of human-computer interaction and communication for operators of the system to monitor and operate connected hardware facilities and data lakes and data mesh. The global cloud 222 further includes hardware module 226, which refers to a module that manages agents or robots, such as automated pallets, robot arms, chargers, stackers and lifts, and maintains their operational state, current facility / customer association, firmware version and maintenance schedule. The global cloud 222 further includes a facilities module 228, which refers to a module that manages facility data, such as contact information, maps and other related information. The global cloud 222 further includes an item master 230, which is a data architecture that maintains the collective item data of all enabled commercial facilities including weight, dimensions, carton types, and universal codes.

[0096] A tenant cloud 232 embodies a cloud-based data storage and processing for the customer. The tenant cloud 232 includes a workflow engine 234, which facilitates a flow of information, tasks, and events from the cloud to an onsite node 250. The tenant cloud 232 further includes a cloud user interface 236, which provides a point of human-computer interaction and communication for the customer to monitor and operate their connected hardware within the facility. The tenant cloud 232 further includes an embedded transportation management system function 238, which provides a global positioning system (GPS) interface for automated pallets or vehicles on the road as part of the unified interface network architecture. The embedded transportation management system function 238 can be configured to provide traffic route estimation and be expandable to include fleet scheduling, route planning and dock assignments for vehicles. These capabilities are natively coordinated with warehouse and robotic operations via the interface network, eliminating the need for external TMS integrations. The tenant cloud 232 further includes an external enterprise resource planning (ERP) or WMS 239, which offers an external parent system that can be configured to handle order management and business functions. The global cloud 222 is configured to push or pull data from the external parent system to determine actions that need to be processed for the facility it operates. The tenant cloud 232 further includes management of an integrated cold enclosure (ICE) 242 that may be configured to monitor passively cooled containers that attach to automatic pallets to transport refrigerated cargo. The ICE 242 can be configured to communicate temperature to the user interface 236 via the TMS 238 when in transport. The tenant cloud 232 further may include a vehicle 244 or any suitable means of transportation to move automated pallets (empty and stacked, or conveying items).

[0097] An onsite node 250 is a computer that sits locally in the facility and runs the listed modules. The onsite node 250 includes a mission planner 252, which is configured to pull data from the cloud and convert high-level abstract tasks into specific actions to be performed. The mission planner 252 further can be configured to process orders that require the consolidation of items into mixed loads, and configured to orchestrate mixed pallet building. The mission planner 252 also maintains overall schedules and provides commands to personnel and robotic entities. These schedules incorporate transportation constraints and delivery milestones, ensuring that WMS and TMS directives are processed simultaneously by the same orchestration logic and translated into executable actions by robotic hardware. The onsite node 250 further includes a path planner 254, which is configured to convert motion actions into precise robot control commands and to provide estimate times that the mission planner uses to create a comprehensive schedule. The onsite node 250 further includes a robotic control system (RCS) or hardware controller 256 to provide an interface between the mission planner 252 and the connected hardware, e.g., automated pallets, robot arms or picking modules, chargers, stackers, lifts, humanoids, etc. The onsite node 250 further includes a load triangulation system 258, which uses a two-dimensional array of loadcell weight modules, a calibration method, and an augmented finite element algorithm to determine whether the correct item has been moved based on the known mass as stored in the item master to the correct place on an automated pallet’s surface, and exactly where that load has been placed in the three-dimensional volume that resides directly above the surface of the automated pallet. The facility includes one or more automated pallet 260 or a variant of the automated pallet, and the onsite node 250 is configured to provide commands to move items through the facility. The facility further includes robotic entities, indicated at 262, including robot arms, and the onsite node 250 further is configured to provide commands to move items on and off, and between automated pallets. The facility further includes at least one of a charger, stacker or lift, indicated at 264, which function as supporting hardware for the automated pallets 260, and the onsite node 250 further is configured to provide commands to move them vertically so they can reach upper levels or stack themselves onto one another when not loaded with items for condensed storage and transport.

[0098] The charger includes a docking station for recharging the automated pallets 260. The stacker is configured to vertically stack unloaded automated pallets, similar to how empty shipping pallets are nested, to enable space-efficient storage and transport. The lift serves as an elevator mechanism that moves automated pallets vertically between different facility levels. The onsite node 250 further is configured to coordinate these components by issuing commands for docking procedures, stacking operations, and vertical movement, thereby enabling continuous operation, seamless multi-level accessibility and compact staging of the automated pallets when not in active use.

[0099] Various controllers may execute various operations discussed above. Using data stored in associated memory and / or storage, the controller also executes one or more instructions stored on one or more non-transitory computer-readable media, which the controller may include and / or be coupled to, that may result in manipulated data. In some examples, the controller may include one or more processors or other types of controllers. In one example, the controller is or includes at least one processor. In another example, the controller performs at least a portion of the operations discussed above using an application-specific integrated circuit tailored to perform particular operations in addition to, or in lieu of, a general-purpose processor. Examples of the disclosure may include a computer-program product configured to execute methods, processes, and / or operations discussed above. The computer-program product may be, or include, one or more controllers and / or processors configured to execute instructions to perform methods, processes, and / or operations discussed above.

[0100] In one example, referring to FIG. 26, an exemplary computer system is generally indicated at 280. As shown, the computer system 280 includes one or more computers that exchange information. More specifically, the computer system 280 includes computers and / or devices 282, 284, 286. As shown, the computers and / or devices 282, 284, 286 are interconnected by, and may exchange data through, a communication network 288. The network 288 may include any communication network through which computer systems may exchange data. To exchange data using the network 288, the computers and / or devices 282, 284, 286 and the network 288 may use various methods, protocols and standards. To ensure data transfer is secure, the computers and / or device 282, 284, 286 may transmit data via the network 288 using a variety of security measures including, for example, TLS, SSL or VPN. While the computer system 280 illustrates three networked computers and / or device 282, 284, 286, the computer system 280 is not so limited and may include any number of computers and / or device, networked using any medium and communication protocol.

[0101] As shown, a computer 282 of the computer system 280 includes a processor 290, memory 292, an interface 296, such as a user interface or screen, and a data storage element 298. To implement at least some of the aspects, functions and processes disclosed herein, the processor 290 performs a series of instructions that result in manipulated data. The processor 290 may be any type of processor, multiprocessor or controller. The processor 290 may be connected to other system components, including one or more memory devices 292, by an interconnection element 294. The memory 292 stores programs and data during operation of the computer system 280. The interconnection element 294 may include one or more physical busses, for example, busses between components that are integrated within a same machine, but may include any communication coupling between system elements including specialized or standard computing bus technologies. The interconnection element 294 enables communications, such as data and instructions, to be exchanged between system components of the computer system 250. The interface device 296 may receive input or provide output. More particularly, output devices may render information for external presentation. Input devices may accept information from external sources. Examples of the interface device 296 include keyboards, mouse devices, trackballs, microphones, touch screens, printing devices, display screens, speakers, network interface cards, etc. The interface device 296 allows the computer 282 to exchange information and to communicate with external entities, such as users and other systems. The data storage element 298 includes a computer-readable and writeable nonvolatile, or non-transitory, data storage medium in which instructions are stored that define a program or other object that is executed by the processor 290. The data storage element 298 also may include information that is recorded, on or in, the medium, and that is processed by the processor 290 during execution of the program. More specifically, the information may be stored in one or more data structures specifically configured to conserve storage space or increase data exchange performance. The instructions may be persistently stored as encoded signals, and the instructions may cause the processor 290 to perform any of the functions described herein.

[0102] In operation, the processor 290 or some other controller causes data to be read from the nonvolatile recording medium into another memory, such as the memory 292, that allows for faster access to the information by the processor 290 than does the storage medium included in the data storage element 298. The processor 290 manipulates the data within the memory 292, and then may copy the data to the storage medium associated with the data storage element 298 after processing is completed. A variety of components may manage data movement between the storage medium and other memory elements and examples are not limited to particular data management components. Further, examples are not limited to a particular memory system or data storage system.

[0103] In some embodiments, the interface network of the warehouse management, transportation management and robotic control systems is configured to enable a user to control and track the movement of the automated pallets, which sometimes may be referred to as automated guided robots (AGRs) or automated guided vehicles (AGVs). In one embodiment, each automated pallet 260 includes a controller that is adapted to control the operation of the automated pallet 260 based on operational parameters obtained by the controller. This controller can be configured to communicate with the controller associated with the interface network, on the onsite node, of the warehouse management, transportation management, and robotic control systems. In one embodiment having multiple automated pallets, the controller may embody a plurality of controllers provided in each automated pallet that communicate with one another over a controller area network (CAN) Bus or other type of network. In other embodiments, a master controller of the interface network of the warehouse management, transportation management and robotic control systems may be provided to control the operation of the controllers of the automated pallet 260.

[0104] In some embodiments, the controller is configured to create a digital twin of the facility to control the movement of automated pallets within the facility. In some embodiments, the interface network of the warehouse management system may include one or more displays, which are operably coupled to the controller. Each display is adapted to display the operational parameters of the described herein. Suitable monitors may be provided to acquire such information.

[0105] In one embodiment, a barcode to identify the products on the automated pallet 260 can be implemented for monitoring inventory on the interface network of the warehouse management, transportation management and robotic control systems 239, 238, 256. For example, the barcode can include a ID scanner for UPC codes, a 2D scanner for QRC codes, a printed label applied on the item or a laser etched label etched on the item. In another embodiment, an RFID system to identify the products can be implemented. For example, the RFID system can include an RFID tag applied to the product and an RFID reader associated with the automated pallet 260 or the facility. With an RFID system, line-of-site between the reader and the item is not required. For example, scanning may be achieved by a handheld device operated by a user who is overseeing the interface network or by hardware embedded in the robotic picking module. Moreover, scanning is not required to identify all products within the automated pallet 260.

[0106] In some embodiments, the controller of the warehouse management system 239 and / or the transportation management system 238 includes one or more databases to keep track of inventory within the system. In one embodiment, the database may include an open application (App) architecture and be configured to push data about the facility, for example. The database can include product information. In one embodiment, the database further can communicate with a system configured to control the transport of products on the automated pallets.

[0107] The database further can be configured to retrieve information about products based on identification, e.g., a barcode number. In one embodiment, the automated pallet 260 can be programmed to accept material stored on the automated pallet 260. The automated pallet 260 can be programmed to update the database to identify the materials on the automated pallet 260, load information into the database associated with the automated pallet 260 from a network 288, which is tied back to the system. Other systems can be provided, such as weight sensors, to provide additional information to the database.

[0108] The database further can be configured to store additional information, such as location, stock information, and usage and consumption. The database can be configured to store information locally or remotely, and can be configured to store data associated with one or more production runs. For example, the database can be configured to obtain and store data including but not limited to traceability of products provided within the warehouse.

[0109] The database can be configured to share prediction data, such as the real-time locations and time of arrival of inventory on automated pallets. The database can be configured to share prediction data with other systems.

[0110] The database can be configured to store data associated with lot traceability of products within the warehouse. In addition, RFID or mechanical keying of a product is provided to ensure correct product location. This information can be used to verify that the correct product is provided to be transported from a warehouse to a destination location. A low-cost reader can perform this function, which can be embedded in the robotic picking module or on the handheld device running the interface network.

[0111] In some embodiments, the warehouse management system can be configured to perform inventory control. Specifically, the warehouse management system can be configured to identify where products are located, how many products have been removed, tie the products and information about the products to a customer inventory control system, and track the products during transport.

[0112] In some embodiments, the warehouse management system can be configured to organize products stored within the warehouse.

[0113] In some embodiments, timing associated with performing transportation functions within the warehouse by the warehouse management system can be programmed to account for devices configured to move the inventory provided on the automated pallets.

[0114] In some embodiments, as described above, the warehouse management system is configured to perform inspection of products contained within the warehouse. In one embodiment, a scanner can be configured to scan bar codes, for example, associated with the products. In another embodiment, a vision system can be configured to obtain images of the products. The vision system in conjunction with the controller, can be configured to inspect for cleanliness, damage, wear, and identification readability, e.g., is the barcode label worn, dirty or tom. The vision system can embody any type of 2D, 3D or color camera. Other systems are contemplated, such as a light detection and ranging (LIDAR) camera configured to scan a space, collect data on the space, and use this information to improve efficiency within the warehouse.

[0115] In some embodiments, the warehouse management system can be configured to communicate with other systems within the warehouse. Communication systems can include a wired system, a wireless system (through a common network, mesh, Bluetooth, Wi-Fi, Zigbee, WAN, Nodes, Li-Fi, etc.), a combination of wired and wireless systems, and infrared (IR) system.

[0116] In some embodiments, the warehouse management system can be configured to address errors associated with handling and recovering products within the warehouse. For example, the warehouse management system can be configured to detect an incomplete action, an incomplete transfer of a product or merchandise, a dropped transfer of a product or merchandise, and a manual intervention or override. In one embodiment, a controller associated with the warehouse management system can be configured to perform static discharge control, data recovery and / or security.

[0117] In some embodiments, the interface network is configured to process directives from higher- level ERP systems and other business platforms that govern the supply chain. The interface network may be configured to invoke the TMS to bring required items to the facility for processing and / or pick up processed items from the facility. The interface network may then invoke the mission planner to schedule required activities to complete the task from the ERP, e.g., to fulfill orders within the facility, which in turn may invoke the path planner to schedule the coordinated movements of robots in the facility to execute the tasks. Then the mission planner may invoke the robotic controller to move the robots per the plan defined by the path planner. In some aspects, the user has override capability, with the interface system being configured to perform the tasks as directed.

[0118] In some embodiments, the warehouse management system and / or the transportation management system can be configured to track products contained within the warehouse, and to communicate information to other entities, such as vehicles and other facilities. For example, the warehouse management system and / or the transportation management system may include a global positioning system (GPS) to assist in tracking products and / or automated pallets.

[0119] As used herein, a “conveyance” describes a forklift, pallet jack, front loader jacking device or crane used to move shipping pallets and / or intermodal containers from place to place in or around a building or facility or on and off a vehicle, etc.

[0120] As used herein, a “facility” describes a space where conveyances operate and the specific activities of manufacturing, storing, sorting and organizing items, loading and unloading those items on and off shipping pallets, loading and unloading shipping pallets carrying items in an out of intermodal containers and loading and unloading intermodal containers carrying shipping pallets with Items to and from vehicles occur.

[0121] As used herein, a “container” or “intermodal container” describes a standardized shipping container, designed and built for intermodal freight transport, meaning the container and / or intermodal container can be used across different vehicles without unloading and reloading their cargo; which is typically shipping pallets loaded with items, including but not limited to the types of containers disclosed in U.S. Patent Application Serial No. 17 / 783,107, now U.S. Patent No. 12,030,419, which is incorporated herein in its entirety.

[0122] As used herein, an “item” or “product” describes any type of object or product or goods that are produced and shipped between buildings and facilities, typically utilizing a shipping pallet and intermodal container on some or all of its journey.

[0123] As used herein a “pallet” or “shipping pallet” describes a flat transport structure, which supports one or more items in a stable fashion while being moved by a conveyance or within an intermodal container. A pallet is the structural foundation of a load of items. Items placed on a pallet are secured with various wrapping for lateral stability and prevention of items falling off the pallet. Loaded pallets are typically loaded into and unloaded from intermodal containers by conveyances.

[0124] As used herein, a “vehicle” describes any mechanism used to transport items and products and may refer to but not limited to airplanes, helicopters, drones, ships, rail cars, trucks, tractor trailers, busses and cars together or individually.

[0125] FIG. 27 depicts an example system 300 implementing an interface network according to an embodiment. System 300 includes a cloud computing system 310 that includes a plurality of computing devices 310 connected together by a communications network 314. One or more of the computing devices 310 implements TMS 238 that operates within the cloud computing system 310. One or more of the computing devices 310 implements WMS 239 that operates within the cloud computing system 310.

[0126] System 300 also includes a plurality of warehouse facilities 320 as well as a transportation network 330.

[0127] Each warehouse facility 320 includes a computing system comprising at least one onsite computing device 250 that executes a Mission Planner 252, Path Planner 254, and an RCS 256 as well as a plurality of automated devices 324 (e.g., one or more of an automated pallet 260, a robotic entity 262, and a charger, stacker or lift 264) configured to store and / or move around products 326 within the warehouse facility 320. Mission Planner 252 is configured to send commands 340 to RCS 256 to direct where and when to move the products 326. RCS 256 is configured to send commands 342 to the automated devices 324 to implement the commands 342 received from the Mission Planner 252. Transportation network 330 includes a plurality of routes 332 and vehicles 244 that allow transportation of products between warehouse facilities 320. TMS 238 directs 344 shipments across transportation network 330 on vehicles 244 traveling along routes 334.

[0128] WMS 239 is configured to interact (step 346) with the TMS 238 to coordinate and schedule movement (at a high level) of products 326 within a warehouse facility 320 with shipments to and from that warehouse facility 320 over the transportation network 330. WMS 239 does not directly control movement of products 326 within a warehouse facility 320; rather WMS 239 communicates (possibly through various intermediary devices) high level directions 348 (e.g., certain products 326 need to be available to be loaded onto or unloaded from a vehicle 244 by a certain time) to mission planner 252. Mission planner 252 is able to interpret the high level directions 348 in conjunction with path planner 254 to create a more detailed plan of exactly when and where the products 326 should be moved, allowing the commands 340 to be created to send to RCS 256.

[0129] In some embodiments, TMS 238 is further configured to coordinate the vehicles 244 and monitor their travel progress across the transportation network 330 and to update the WMS 239 of any changes to an estimated time of arrival at a destination facility 320. WMS 239 can then use that information to schedule when particular products 326 need to be moved into convenient locations for loading onto or unloading from vehicles 244 at the appropriate times, e.g., by mission planner 252 scheduling those products 326 to be moved onto particular automated pallets 260 and particular automated pallets 260 to be moved into particular locations.

[0130] The aspects disclosed herein in accordance with the present disclosure, are not limited in their application to the details of construction and the arrangement of components set forth in the following description or illustrated in the accompanying drawings. These aspects are capable of assuming other embodiments and of being practiced or of being carried out in various ways. Examples of specific implementations are provided herein for illustrative purposes only and are not intended to be limiting. In particular, acts, components, elements, and features discussed in connection with any one or more embodiments arc not intended to be excluded from a similar role in any other embodiments.

[0131] Also, the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. Any references to examples, embodiments, components, elements or acts of the systems and methods herein referred to in the singular may also embrace embodiments including a plurality, and any references in plural to any embodiment, component, element or act herein may also embrace embodiments including only a singularity. References in the singular or plural form are not intended to limit the presently disclosed systems or methods, their components, acts, or elements. The use herein of “including,” “comprising,” “having,” “containing,” “involving,” and variations thereof is meant to encompass the items listed thereafter and equivalents thereof as well as additional items. References to “or” may be construed as inclusive so that any terms described using “or” may indicate any of a single, more than one, and all of the described terms. In addition, in the event of inconsistent usages of terms between this document and documents incorporated herein by reference, the term usage in the incorporated reference is supplementary to that of this document; for irreconcilable inconsistencies, the term usage in this document controls.

[0132] Having thus described several aspects of at least one example, it is to be appreciated that various alterations, modifications, and improvements will readily occur to those skilled in the art. For instance, examples disclosed herein may also be used in other contexts. Such alterations, modifications, and improvements are intended to be part of this disclosure, and are intended to be within the scope of the examples discussed herein. Accordingly, the foregoing description and drawings are by way of example only.

[0133] What is claimed is:

Claims

CLAIMS1. An interface network for a warehouse management system, a transportation management system, and a robotic control system, the interface network comprising: a storage device configured to store a plurality of basic unit instructions, one or more of the basic unit instructions having at least one procedure identifier; at least one processor coupled to the storage device and a communication network; and one or more components executable by the at least one processor and collectively configured to: identify a facility location, manage inventory within the facility location by the robotic control system manipulating robotic entities within the facility location under direction of the warehouse management system, and coordinate transportation to and from the facility location with movement of inventory by the robotic entities within the facility location by coordinating between the transportation management system and the warehouse management system.

2. The interface network of claim 1, wherein the robotic entities located in the facility location provide information about the products contained on robotic entities in the facility location to manage the products in the facility location.

3. The interface network of claim 1, wherein the at least one processor further is configured to provide an advanced shipping notice and transportation schedule to provide notice of upcoming deliveries and expected vehicle arrivals sent by the facility location to a receiving facility location.

4. The interface network of claim 3, wherein when an order is accepted by the receiving facility location, an inbound order generated by the interface network is processed by the receiving facility location, the at least one process further being configured to coordinate unloading times, vehicle docking assignments, and route adjustments in response to real-time conditions.

5. The interface network of claim 1 , wherein the at least one processor further is configured to verify the products being shipped from the facility location to a receiving facility location.

6. The interface network of claim 5, wherein once the products pass verification, the products are moved to storage cells of the receiving facility location and may be displayed on a warehouse dashboard.

7. The interface network of claim 1, wherein the at least one processor further is configured to retrieve items from the facility location.

8. The interface network of claim 7, wherein a user is provided detailed options to select and retrieve items.

9. The interface network of claim 8, wherein an item window is provided to enable the user to view the selected item or items.

10. The interface network of claim 1, wherein the at least one processor further is configured to identify an item to be positioned near a delivery point to be retrieved.

11. The interface network of claim 10, wherein a user is able to provide an order notification to process the delivery of the item to a receiving party.

12. The interface network of claim 1, wherein the at least one processor further is configured to enable a user to view items stored within the facility location in real-time.

13. A computer-readable medium comprising instructions which, when executed by a computing system, cause the computing system to carry out a method of: identifying a facility location; managing inventory within a zone of the facility location by a warehouse management system; andmanipulating robotic entities to effect the management of inventory by a robotic control system controlled by the warehouse management system in coordination with transportation activities related to inbound and outbound movement of goods by a transportation management system.

14. The computer-readable medium of claim 13, wherein the robotic entities located in discrete cells provide information about the products contained on the robotic entities to manage the products in the facility location.

15. The computer-readable medium of claim 13, wherein the computing system further is configured to provide an advanced shipping notice and an expected transportation schedule to provide notice of upcoming deliveries sent by the facility location to a receiving facility location.

16. The computer-readable medium of claim 15, wherein when an order is accepted by the receiving facility location, an inbound order is processed by the receiving facility location and where the transportation coordination system may also adjust internal scheduling and dock assignments based on live vehicle tracking data.

17. The computer-readable medium of claim 13, wherein the computing system further is configured to verify the products being shipped from the facility location to a receiving facility location.

18. The computer-readable medium of claim 17, wherein once the products pass verification, the products are moved to storage cells of the receiving facility location and may be displayed on a warehouse dashboard.

19. The computer-readable medium of claim 13, wherein the computing system further is configured to retrieve items from the facility location.

20. The computer-readable medium of claim 19, wherein a user is provided detailed options to select and retrieve items.

21. The computer-readable medium of claim 20, wherein an item window is provided to enable the user to view the selected item or items.

22. The computer-readable medium of claim 13, wherein the computing system further is configured to identify an item to be positioned near a delivery point to be retrieved.

23. The computer-readable medium of claim 22, wherein a user is able to provide an order notification to process the delivery of the item to a receiving party.

24. The computer-readable medium of claim 13, wherein the computing system further is configured to enable a user to view items stored within the facility location in realtime.

25. The computer-readable medium of claim 13, wherein the computing system further is configured to enable a user to manipulate positions of the robotic entities within the facility location and orchestrate the robotic entities interaction with inbound or outbound transport assets.

26. A system comprising: a cloud computing system, including a plurality of computing devices interconnected by a communications network; a plurality of warehouse facilities; and a transportation network, including a plurality of vehicles and routes between the plurality of warehouse facilities; wherein a transportation management system (TMS) operates within the cloud computing system, the TMS configured to manage shipments between the plurality of warehouse facilities via the transportation network;wherein a warehouse management system (WMS) operates within the cloud computing system; wherein each warehouse facility includes (a) a plurality of automated devices and (b) both a mission planner and a robotic control system (RCS) operating within a computing system of that warehouse facility, collectively configured to manage the location of products within that warehouse facility; wherein the WMS is configured to interact with the TMS to coordinate shipments to and from a warehouse facility with timing and placement of certain products within that warehouse facility and to communicate high level directions to the mission planner based on that timing and placement; wherein the mission planner is configured to send commands to the RCS to direct exactly where and when to move the products; and wherein the RCS is configured to send commands to the automated devices to implement the commands received from the mission planner.

27. The system of claim 26 wherein the TMS is further configured to coordinate the vehicles and monitor their travel progress across the transportation network and to update the WMS of any changes to an estimated time of arrival to the destination facilities.

Images