Multi-node supply chain system and supply chain workflow execution method using transportable and sustainably traceable storage containers

Through multi-node supply chain systems and intelligent standardized storage containers, the problems of carton waste and inventory management in traditional supply chains are solved, efficient inventory tracking and automated exchange are achieved, and transportation costs and environmental impacts are reduced.

CN119067528APending Publication Date: 2024-12-03LAFAYETTE SYSTEMS CANADA ULC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411175234.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2019-08-26
Filing Date
2020-02-28
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

Traditional supply chain systems have carton waste, chaotic inventory management, high costs, great environmental impact, and lack effective multi-supplier inventory tracking and automated exchange solutions.

Method used

Adopting a multi-node supply chain system, using a transportable and sustainable tracking intelligent standardized storage container, the introduction, storage, distribution and tracking of inventory in the supply chain ecosystem through semi-automated and fully automated systems, realizing the automatic movement and location of storage containers Real-time tracking to reduce carton usage and transportation costs.

Benefits of technology

It significantly reduces carton usage and transportation costs, achieves 100% storage container traceability, improves inventory management efficiency, reduces environmental impact, and optimizes resource utilization in the supply chain.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119067528A_ABST
    Figure CN119067528A_ABST
Patent Text Reader

Abstract

The present invention provides a multi-node supply chain system comprising a plurality of interconnected entities and a method of executing supply chain workflows using a transportable and sustainably traceable standardized storage container. The entities include a network of node facilities distributed throughout a geographic area, inter-node transport vehicles (INTVs), storage containers storable in indexed storage locations in the node facilities and the INTVs, and a computerized system. A computerized system stores a container identifier of a storage container, a location identifier of an indexed storage location, and a location identifier of a dynamic storage location of the storage container. The computerized system may also update the location identifier as the storage container is transferred between the node facility and the INTV. The node facilities, INTVs, and storage containers all communicate with the computerized system and provide a complete traceability of one or more of each of the inventory items from input to the supply chain system to order fulfillment.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application claims priority to the following provisional patent application, the specification of which is incorporated herein by reference in its entirety:

[0002] 1. Provisional application 62 / 812,822, filed on March 1, 2019, for “Supply Chain Facilities and Vehicle Networks, and Delivery and Order Fulfillment Services Using the Same”;

[0003] 2. Provisional application 62 / 818,419, filed on March 14, 2019, for “Replenishing, Tracking, and Handling Storage Containers in a Supply Chain, Distribution, or Order Fulfillment Ecosystem”;

[0004] 3. Provisional application 62 / 818,444, filed on March 14, 2019, for “Bidirectional Logistics Using Transportable Storage Containers in a Supply Chain, Distribution, or Order Fulfillment Ecosystem”;

[0005] 4. Provisional application 62 / 818,506, filed on March 14, 2019, for “Multi-entity inventory management method using multiple storage container assignment and reassignment in supply chain, distribution, and order fulfillment ecosystems”;

[0006] 5. Provisional application “Multi-entity inventory management method using storage containers and product reassignment in a supply chain, distribution or order fulfillment ecosystem”, application number 62 / 836,863, filed at the USPTO on April 22, 2019;

[0007] 6. Provisional Application No. 62 / 846,295, filed on May 10, 2019, for “Space University Order Fulfillment Facility Using ASAR Structure and Workflow Robot Vehicle Therefor Between Service Areas”; and

[0008] 7. Provisional application "Multi-region ASAR structure and automatic introduction process using container merging and container switching technology", application number 62 / 891,549 was applied to the USPTO on August 26, 2019. Technical Field

[0009] In general, embodiments herein relate to supply chain, distribution channels, order fulfillment, and inventory management. More specifically, embodiments herein relate to a multi-node supply chain system including multiple interconnected entities, and a method for executing supply chain workflows using transportable and continuously trackable storage containers. Background Art

[0010] Traditional supply chains include a series of independent trading entities such as manufacturers, producers, vendors, suppliers, warehouses, transportation companies, distribution centers, order fulfillment centers, retailers, etc. Supply chain management allows inventory to be obtained from manufacturers and producers and shipped to end customers and end consumers. Supply chain management usually includes the inventory flow from the source of inventory to the fulfillment of customer orders, as well as the management of the last mile and checkout to the customers and end users. Logistics is a part of the supply chain, including the control of the movement and storage of inventory from the source of inventory to the final destination. Several technologies are now emerging that are changing the traditional way of managing supply chains. Customers are increasingly demanding personalized products and more detailed orders. The digitization of the supply chain allows companies to meet the increasing expectations of customers.

[0011] As e-commerce continues to grow at a significant rate and surpass traditional brick-and-mortar storefront sales practices, many businesses are faced with the challenge of maintaining or gaining relevance in the online market and having to compete with established players in the space. Therefore, the industry needs a solution that allows suppliers to break away from or improve traditional supply chain and distribution management practices to refocus on direct-to-customer order fulfillment. E-commerce has changed the way customers buy things. Although it is common and convenient to order and purchase items online or through the Internet, the items are usually shipped to customers in cartons. These cartons and related dunnage store and protect the ordered items in the cartons as they are shaken violently as they pass through the supply chain system using package sorting devices that shake violently. Freight service companies report that they ship millions of cartons every day. Since the infrastructure cannot manage and recycle the large number of cartons used in e-commerce shipping processes, these cartons are shipped to different countries for recycling. Most of these cartons end up in landfills, thereby creating mountains of garbage and seriously affecting the environment. Therefore, the industry needs to reduce the number of cartons used to transport customer orders from the order fulfillment center to the last mile pickup location.

[0012] Furthermore, to reduce last-mile delivery costs, inventory must be located as close to the end customer as possible in small fulfillment centers. Real estate costs for space in the back of a retail store or behind-the-scenes warehouse close to the end customer are much higher than the rural environment of most distribution centers. To maintain small fulfillment, each facility must offer a wide variety of goods, but not too much, otherwise it will significantly increase storage requirements. Therefore, the industry needs to handle all inventory items sold in the supply chain at a "per piece" level and replenish "just enough" inventory, rather than replenishing at the "box" level in traditional supply chain methods.

[0013] Furthermore, all entities in a traditional supply chain do not include material handling equipment to perform supply chain activities and exchange inventory between entities. Some solutions will lay mats inside a transport vehicle and allow robots to move inside the transport vehicle, but do not have material handling equipment compatible with the storage unit to handle the racks in the transport vehicle. Some solutions will interact and exchange inventory between two entities, but are not aware of other entities in the supply chain. A system and method is needed in which all interconnected entities in the supply chain are configured to handle and transport standardized storage units, such as storage containers, that have a single form factor and structure for connecting with standard and compatible machines and transport vehicles throughout the supply chain.

[0014] To improve inventory management overall, the industry needs to better collaborate with multiple suppliers in the supply chain. Most traditional supply chain systems do not use multi-tenant technology to handle orders from multiple suppliers. The industry needs to combine the inventory of multiple suppliers in a single storage unit while continuously tracking the physical location and ownership of inventory items. In addition, the industry needs to move multi-supplier inventory between network nodes and track multi-supplier inventory in the supply chain.

[0015] Some supply chain systems automate the delivery and receipt of inventory items at the entity level, where independent trading entities continuously receive and release inventory, thus requiring staging areas to check storage units in and out of facilities and transportation vehicles. Tracking the location of inventory items in the supply chain is a tedious operation because storage units containing inventory items must be scanned at each entity all the time. Moreover, since most storage units are randomly stacked on transportation vehicles, it is not easy to track the actual location of the storage units on the transportation vehicles. Storage units containing inventory items are usually checked in and out of facilities to track their whereabouts in the supply chain. The industry needs to continuously and in real time track storage containers without relying on positioning devices, radio frequency identification (RFID) tags on storage containers, etc. In addition, the industry needs to continuously track storage containers containing inventory items in the supply chain to alleviate the need to transport and receive inventory items between facilities and allow storage containers to have complete traceability at all times.

[0016] Traditional supply chain systems often fulfill customer orders from multiple endpoints, which increases costs and leads to chaotic inventory management. The industry needs to fulfill customer orders from the endpoint closest to the destination address. Moreover, these supply chain systems ship and receive goods between entities in a chaotic manner with limited predictability. The industry needs an automatic and clear method to exchange storage units in a one-to-one correspondence at each facility including an endpoint to improve predictability and optimize inventory management. Moreover, traditional solutions use a top-down centralized control approach to manage supply chain actions and control the movement of inventory and storage units in the supply chain. In these solutions, a central server controls all aspects of the storage unit's journey through the facility. Moreover, these centralized approaches cannot effectively respond to changing conditions in the supply chain. The industry needs a multi-agent type of control approach, which is characterized by standardized storage units that define their own actions and control their own journey in the supply chain, and the facility acts as the command enabler for the storage unit.

[0017] Therefore, the industry has long needed: a multi-node supply chain system that includes multiple interconnected entities; and a clear method that uses transportable and continuously trackable storage containers to execute supply chain workflows, both of which can solve the above-mentioned problems of prior arts. Summary of the invention

[0018] The purpose of this summary is to further introduce some concepts disclosed in the embodiments in a simplified manner. The purpose of this summary is not to determine the scope of the claimed subject matter.

[0019] The systems and methods disclosed herein can address the above-mentioned needs of a multi-node supply chain system and a clear method, wherein the multi-node supply chain system includes multiple interconnected entities, and the clear method uses transportable and continuously trackable storage containers to execute supply chain workflows. In various embodiments, the multi-node supply chain system uses semi-automated and fully automated systems and methods to introduce, store, distribute and track inventory from multiple suppliers, and to fulfill, store, distribute and track customer orders. The multi-node supply chain system establishes a supply chain ecosystem, which does not distribute inventory from a central hub, but distributes it throughout the supply chain ecosystem, thereby balancing resources as much as possible and delivering inventory to the place closest to the customer. The multi-node supply chain system disclosed herein is a multi-tenant fulfillment network, in which all entities, such as facilities, transportation vehicles, etc., include specially designed material handling devices, which are configured to receive and move intelligent standardized storage units, referred to as "storage containers" in this article, through the supply chain ecosystem.

[0020] The entities in the multi-node supply chain system include specially configured devices that are compatible with performing various supply chain activities and exchanging inventory storage containers between entities. The interconnected entities in the multi-node supply chain system are configured to handle and transport intelligent standardized storage containers, which have a single form factor and structure for connecting standard and compatible machines and transportation vehicles throughout the supply chain ecosystem. Once the inventory items are loaded into the storage containers, the multi-node supply chain system allows the inventory loaded in the storage containers to move fully automatically throughout the network. Moreover, in one embodiment, the multi-node supply chain system facilitates continuous and real-time tracking of storage containers without relying on positioning devices, radio frequency identification (RFID) tags on storage containers, etc. In the multi-node supply chain system, the continuous tracking of storage containers during all transfers and exchanges can alleviate the need to transport and receive inventory items between facilities and allow storage containers to have complete traceability at all times.

[0021] The interconnected entities of the multi-node supply chain system disclosed herein include a network of node facilities, a fleet of inter-node transport vehicles, multiple storage containers, and a computerized supply chain management system (CSCMS). The network of node facilities is distributed throughout the geographic area. Each of the node facilities includes a facility-type configuration structure that indexes storage locations. The fleet of inter-node transport vehicles will transport multiple inventory items in storage containers between node facilities. Each inter-node transport vehicle includes a vehicle configuration structure that indexes storage locations. In one embodiment, the fleet of inter-node transport vehicles includes multiple dedicated service transport vehicles, which are respectively assigned to serve specific two node facilities, and / or a limited subset of service node facilities, and / or a limited service area including two or more node facilities.

[0022] The storage container can be stored in the node facility network via an inter-node transport vehicle and can be transported between node facilities. Each storage container is of standardized size and is configured to receive more than one of a plurality of inventory items. Moreover, the configuration of each storage container is compatible with the node facility configuration structure that indexes the storage location and the vehicle configuration structure that indexes the storage location, and is used to selectively store and continuously track any storage box in any node facility, in any inter-node transport vehicle, and between any node facility and any inter-node transport vehicle. In one embodiment, each storage container in any node facility, in any inter-node transport vehicle, and between any node facility and any inter-node transport vehicle can be continuously tracked in real time or near real time. In one embodiment, the storage container is configured to hold more than one inventory item owned by more than one supplier.

[0023] In one embodiment, the storage containers can be classified into: a first type of storage container, which contains unmixed inventory items that meet the item type; a second type of storage container, which contains mixed inventory items that do not meet the item type; and a third type of storage container, which is configured as an order container for fulfilling an order. In addition, in one embodiment, the node facility network is a hierarchical network, which includes at least one giant facility, at least one large facility, and at least one small facility. The giant facility is configured to store the first type of storage container. The large facility is configured to receive one or more first type storage containers transported from the giant facility. The giant facility is further configured to load different inventory items of the received first type storage container into a predefined number of second type storage containers to meet the actual inventory demand and / or predicted inventory demand of another or more node facilities. The small facility is configured to receive one or more second type storage containers transported from at least one large facility. The small facility is further configured to load different inventory items of the received second type storage container into a predefined number of order containers to fulfill the order. In one embodiment, the node facility network further includes at least one nano-type facility, which is configured to receive one or more of the order containers containing orders for customers and / or delivery personnel to pick up. In one embodiment, the small facility is configured to fulfill orders based on the distance of the small facility to at least one nano facility and / or at least one nano facility preferred by the customer. In other embodiments, the functions of the macro facility and the large facility are combined into one facility.

[0024] In one embodiment, the order containers include picked order containers, which have standardized sizes and configurations that are the same as storage containers. The picked order containers of the small facility contain one or more inventory items for multiple orders and are introduced into the facility-type configuration structure of the small facility. In another embodiment, the order containers include completed orders. The standardized sizes and configurations of the completed order containers are different from other storage containers, and after being taken from the facility-type configuration structure of at least one small facility, they are filled with one or more inventory items for individual orders. Completed order containers with different standardized sizes and configurations are configured to be compatible with the facility-type configuration structure of indexed storage locations of at least one nano facility, and the vehicle-type configuration structure of indexed storage locations in node-to-terminal transportation vehicles. In one embodiment, inventory items owned by suppliers are packaged into individual packages with supplier brands, such as supplier branded bags, and the individual supplier branded packages are packed into completed order containers. Orders are fulfilled at large facilities and / or small facilities.

[0025] In one embodiment, a mobile data storage device having a computer readable memory is operably coupled to each storage container. The mobile data storage device is configured to store a unique container identifier for an individual storage container, and container data related to inventory items contained in the individual storage container. In another embodiment, at least one sensor is operably coupled to each storage container. The sensor is configured to detect movement of each storage container, and in response to the detected movement, begin tracking the location of each storage container through a multi-node supply chain system. In another embodiment, a mobile internal positioning device is operably coupled to each storage container, and an internal storage system is installed in each node facility. The mobile internal positioning device is configured to operably communicate with the internal positioning system to determine and report the location of each storage container in each node facility, thereby tracking each storage container in real time.

[0026] In one embodiment, at least one node facility includes a plurality of environmentally distinct storage areas distributed in a facility-type configuration structure indexing storage locations. Storage containers may selectively store environmental data in the facility-type configuration structure indexing storage locations in environmentally distinct storage areas based on environmental data. Environmental data is retrieved from storage containers and / or individual mobile data storage devices of the CSCMS.

[0027] The CSCMS is communicatively coupled to the node facility network, the fleet of inter-node transport vehicles, and the storage container. The CSCMS includes at least one processor and a non-transitory computer-readable storage medium communicatively coupled to the processor. The CSCMS includes one or more databases configured to store container data including a container identifier, which is assigned to a storage container. The database of the CSCMS is further configured to store location identifiers of indexed storage locations of storage containers in facility-type configuration structures and vehicle-type configuration structures, as well as location identifiers of dynamic storage locations of storage containers. The CSCMS is further configured to update the location identifier when the storage container is transferred between the indexed storage locations of the facility-type configuration structure and the vehicle-type configuration structure because the storage container moves back and forth between the node facility network and the fleet of inter-node transport vehicles in the multi-node supply chain system. In one embodiment, the multi-node supply chain system further includes one or more machine processing devices that can operate at each node facility. Each machine processing device is configured to go to any storage container through the facility-type configuration structure of the indexed storage location, and then selectively deposit any storage container at the location, and obtain any storage container from the location. In one embodiment, each machine processing device is further configured to provide a dynamic storage location to each storage container. In one embodiment, each machine processing device is assigned a unique identifier that is configured to indicate one of the dynamic storage locations of the storage container and allows real-time tracking of the storage container. The network of node facilities, the fleet of inter-node transportation vehicles, the storage containers, and the machine processing devices in one embodiment can communicate with the CSCMS and are configured to provide full traceability of one or more of each storage container from entry into the supply chain system to completion of order fulfillment.

[0028] The CSCMS also automatically records and connects the container identifier of the storage container to the location identifier of the index storage location in the facility-type configuration structure and the vehicle-type configuration structure, and automatically records and connects the dynamic storage location to the item identifier of the inventory item contained in the storage container, and the supplier identifiers of multiple suppliers whose inventory items are contained in the storage container in the database. In another embodiment, any one or more of the storage containers includes multiple compartments, which are configured to store inventory items of multiple suppliers in one or more storage containers. Each compartment is identified by a compartment identifier and is configured to store one or more inventory items owned by a corresponding supplier. The CSCMS is further configured to automatically record and connect the compartment identifier of an individual compartment to the item identifier of any one or more inventory items, and the supplier identifier of the supplier whose inventory items are contained in any one or more storage containers, wherein the inventory items are contained in any one or more storage containers. The multi-node supply chain system combines multi-supplier inventory in a single storage container while tracking the actual location and ownership of the inventory items. The multi-node supply chain system moves multi-supplier inventory between node facilities and transportation facilities through the supply chain ecosystem and tracks multi-supplier inventory.

[0029] The container data associated with the storage containers includes one of the following: an inventory catalog; inventory item data, including the item identifier, quantity and attributes of each inventory item contained in each storage container; destination data, associated with the destination of the contained inventory items; time data, associated with the time range and urgency of the inventory items contained in each storage container to be transported to the destination through the multi-node supply chain system; inventory customization data, associated with value-added business actions to be performed on the inventory items contained in each storage container; inventory processing data, associated with the distribution scheduling, processing and / or packaging conditions of the inventory items contained in each storage container; and environmental data, associated with the environmental conditions of the inventory items contained in the storage containers.

[0030] The CSCMS receives and processes container data and commands from each storage container, and each storage container moves back and forth in the forward and reverse directions between the network of node facilities and the fleet of inter-node transport vehicles in the multi-node supply chain system. The CSCMS will also generate task-based instructions to assist loading actions and order fulfillment actions at one or more node facilities based on the container data. Moreover, the CSCMS will generate task-based instructions to trigger loading actions and unloading actions at one or more node facilities based on the container data. In one embodiment, the delivery storage container will be unloaded from any inter-node transport vehicle to any node facility, and the delivery storage container will be reloaded from any node facility to any inter-node transport container. The delivery storage container and the delivery storage container will be exchanged between any inter-node transport vehicle and any node facility in a one-to-one (1:1) correspondence to allow storage containers to flow equally in the forward and reverse directions through the multi-node supply chain system. The system reads the unique container identifier of each incoming storage container loaded from any node facility to any inter-node transport vehicle, and updates one or more databases of the CSCMS with the unique container identifier to record the transfer of each outgoing storage container to any inter-node transport vehicle. The system reads the unique container identifier of each incoming storage container unloaded from any inter-node transport vehicle to any node facility, and updates one or more databases of the CSCMS with the unique container identifier to record the transfer of each incoming storage container to any node facility. In one embodiment, at least one outgoing storage container is an empty storage container. In another embodiment, at least one outgoing storage container is a non-empty storage container that contains at least one inventory product. In another embodiment, the non-empty storage containers contain desired inventory items or customer returns. In another embodiment, the standardized sizes and configurations of the incoming storage containers and the outgoing storage containers are the same as the storage containers.

[0031] In one embodiment, the CSCMS further includes a facility management subsystem at the node facility, which are communicatively coupled to each other. The individual facility management subsystem is configured to communicate with the mobile data storage device of the storage container to perform at least one of the following: read the container data stored on the individual mobile data storage device; update the container data stored on the individual mobile data storage device; generate a command for an action to be performed on the storage container based on at least part of the container data; control the processing device of the node facility based on at least part of the generated command; instruct employees how to perform; and transfer the storage container to an environmentally different storage area in the facility-type configuration structure based on environmental data read from the individual mobile data storage device of the storage container. In one embodiment, the CSCMS further includes an individual vehicle management subsystem for inter-node transport vehicles. The individual vehicle management subsystems are all configured to communicate with the individual facility management subsystem at the node facility and the individual mobile data storage device of the storage container to record the bidirectional transfer of the storage container between the node facility and the inter-node transport vehicle.

[0032] In another embodiment, the positioning unit and the wireless communication unit are operably coupled to each inter-node transport vehicle. The positioning unit is configured to determine the position of each of the inter-node transport vehicles and, in turn, determine the position of any storage container transported in the inter-node transport vehicle. The wireless communication unit is configured to communicate the position of each of the inter-node transport vehicles and the position of any storage container when the storage container is transported between node facilities to the CSCMS.

[0033] The multi-node supply chain system disclosed herein reduces the use of cartons, last mile costs, and about 80% of air freight, provides complete traceability, such as 100% traceability of storage containers at all times, and provides inventory to customers within a two-hour to eight-hour time zone. Moreover, the multi-node supply chain system reduces costs for retailers, thereby increasing e-commerce profits and reducing environmental impact. In addition, the multi-node supply chain system disclosed herein can variably transmit the fulfilled customer order from the nearest end point to the end customer. If inventory items from other facilities are required, the multi-node supply chain system will first transmit the request up the hierarchy before transmitting the fulfilled customer order to the nearest facility. The multi-node supply chain system disclosed herein allows multi-supplier inventory in a single storage container to be stored or moved in a single compartment or multiple compartments of the storage container throughout the supply chain ecosystem. The standardized storage container in the multi-node supply chain system disclosed herein determines its own actions, routes and itineraries throughout the supply chain ecosystem, while the facilities, transportation vehicles and machine handling equipment, etc., act as command enablers for individual storage containers.

[0034] In one or more embodiments, the related system includes circuits and / or programming for performing the methods disclosed herein. The circuits and / or programming are any combination of hardware, software and / or firmware, which are configured to perform the methods disclosed herein according to the design choices of the system designer. In one embodiment, various structural elements are used according to the design choices of the system designer. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The foregoing summary and the following embodiments may be more clearly understood when read in conjunction with the accompanying drawings. To illustrate the embodiments herein, exemplary configurations of the embodiments are shown in the accompanying drawings. However, the embodiments herein are not limited to the specific structures, elements, and methods disclosed herein. The description of a structure, component, or method step represented by a number in the accompanying drawings is applicable to the description of a structure, component, or method step represented by the same number in any subsequent drawings.

[0036] Figure 1A According to an embodiment shown herein, the nationwide distribution of giant facilities and large facilities of a multi-node supply chain system is shown.

[0037] Figure 1B According to an embodiment shown herein, the distribution of mega facilities and large facilities of a multi-node supply chain system at a regional level is shown.

[0038] Figure 1C According to an embodiment shown herein, the distribution of large facilities and small facilities of a multi-node supply chain system at the town level is shown.

[0039] Figure 1D According to one embodiment described herein, the distribution of small facilities and nano-facilities of a multi-node supply chain system at a local level is shown.

[0040] Figure 2A According to one embodiment described herein, a functional block diagram of a multi-node supply chain system is shown that uses transportable and continuously trackable storage containers to execute supply chain workflows.

[0041] Figure 2B A functional block diagram is shown according to an embodiment herein, illustrating the configuration and use of storage containers for containing, storing, and transporting inventory and customer orders in a multi-node supply chain system.

[0042] Figure 3A-3B According to one embodiment of the present invention, a central database of a multi-node supply chain system is shown.

[0043] Figure 3C-3D According to an embodiment of the present invention, a local facility database and a local vehicle database of a multi-node supply chain system are displayed.

[0044] Figure 3E-3FAccording to an embodiment of the present invention, local data stored in different types of storage containers are displayed.

[0045] Figure 4A According to one embodiment herein, a storage container showing supply, inventory, and filled order requirements, and a workflow in a forward or downstream direction through a multi-node supply chain system.

[0046] 4B shows the workflow of an empty storage container returned from a client through a multi-node supply chain system in a reverse or upstream direction according to an embodiment of the present invention.

[0047] Figure 5 According to an embodiment of the present invention, a top view of the structure of a giant facility of a multi-node supply chain system is shown.

[0048] Figure 6 According to an embodiment of the present invention, a top view of the structure of a large facility of a multi-node supply chain system is shown.

[0049] Figure 7 According to an embodiment of the present invention, a top view of the structure of a small facility of a multi-node supply chain system is shown.

[0050] Figure 8 According to one embodiment herein, a three-dimensional grid storage structure is displayed that is configured to fully or partially define a three-dimensional configuration structure of indexed storage locations within each giant, large, and small facility of a multi-node supply chain system.

[0051] Figures 9A-9B According to one embodiment herein, a flow chart is shown of a computerized implemented method for managing the unloading of supply freights from an inbound dock of a mega facility and the introduction of inventory items from the inbound dock into storage containers into a multi-node supply chain system.

[0052] Figures 10A-10B According to one embodiment of the present invention, a side front view and a top view of a large transport vehicle are respectively shown, wherein the transport vehicle is used to transport storage containers between giant, large and small facilities in a multi-node supply chain system, and a collaborative loading grid structure at the unloading platform of the facility, wherein the large transport vehicle is assisted in automatic loading and unloading by machine handling equipment on the loading grid structure.

[0053] Fig. 10C According to an embodiment of this invention, it is displayed Figures 10A-10B Rear elevation view of a medium to large transport vehicle.

[0054] Figures 11A-11C A partial rear elevation view, a side view, and a top view are respectively shown of a container transporter for indexing storage containers and order containers in a large transport vehicle according to an embodiment of the present invention.

[0055] Figures 12A-12B According to one embodiment herein, a flow chart is shown of a computerized method for managing the exchange of storage containers between a mega-facility and a transport vehicle arriving at an outbound loading dock of the mega-facility from a downstream mega-facility.

[0056] Figures 13A-13B According to one embodiment herein, a flow chart is shown of a computerized method for managing the exchange of storage containers between a large facility and a transport vehicle arriving at an inbound loading dock of the large facility from an upstream mega facility.

[0057] Fig.14 According to one embodiment herein, a flow chart is shown of a computerized implemented method for managing the performance of value added services on the contents of storage containers of a large facility.

[0058] Figures 15A-15B A flow chart showing a computer-implemented method for managing the compilation of smart container products for a large facility into smart container kits to fulfill downstream product needs of other facilities is shown according to one embodiment of the present invention.

[0059] Figures 16A-16B A flow chart showing a computerized method for managing a small facility placing multiple customer orders from a smart container kit into picked order containers, and individually packaging the customer orders into completed order containers for shipment to one or more nano facilities, according to one embodiment of the present invention.

[0060] Figures 17A-17C Shown are a side view, a top view, and a rear elevation view, respectively, of a small transport vehicle for transporting order containers between small facilities and nano facilities in a multi-node supply chain system according to an embodiment of the present invention.

[0061] Figures 18A-18C A partial rear view, a side elevation view, and a top view are shown, respectively, of a container transporter for indexing storage containers and order containers in a large transport vehicle according to an embodiment of the present invention.

[0062] Figures 19A-19C According to an embodiment of the present invention, a top view, a side elevation view and a rear elevation view are respectively shown, showing the loading order container to Figure 7 The small facility's outbound unloading platform is shown as a small transport vehicle that unloads order containers from different areas of the environment.

[0063] Fig. 20According to one embodiment herein, a flow chart is shown of a computerized method for managing the exchange of storage containers between a small facility and a transport vehicle arriving at an outbound unloading dock at the small facility from a downstream nano facility.

[0064] Figures 21A-21C According to an embodiment of the present invention, a top view, a side elevation view, and a rear elevation view of a nano-sized facility of a multi-node supply chain system are respectively shown.

[0065] Figures 22A-22B According to one embodiment of the present invention, a top view and a side elevation view are respectively shown of a small vehicle parked at a nano-sized facility, wherein the small vehicle transports completed order containers from the small-sized facility to the nano-sized facility and collects empty order containers or return order containers from the nano-sized facility for transport back to the small-sized facility.

[0066] Figures 23A-23B According to one embodiment herein, a flow chart is shown of a computerized method for managing the exchange of order containers between a nano-sized facility and a transport vehicle arriving at the nano-sized facility from a small-sized facility.

[0067] Fig.24 A flow chart is shown of a computerized method for managing the release of storage containers to customers or shipping personnel at a nanoscale facility, according to one embodiment of the present disclosure.

[0068] Fig.25 According to one embodiment described herein, a flow chart of a computerized method for executing a supply chain workflow using a transportable and continuously trackable storage container is shown.

[0069] Fig.26 According to one embodiment described herein, a flow chart is shown of a computerized method for executing a bi-directional logistics supply chain workflow using transportable and continuously trackable storage containers. DETAILED DESCRIPTION

[0070] The various aspects of the present invention may be implemented as a system of components and / or structures, methods and / or non-transitory computer-readable storage media storing one or more computer-readable program codes. Thus, various embodiments of the present invention may take the form of a combination of hardware and software embodiments, including mechanical structures as well as electronic components, computing elements, circuits, microcode, firmware, software, etc.

[0071] Figures 1A-1DAccording to one embodiment of the present invention, a domestic supply chain ecosystem is shown, which includes a four-layer hierarchical network of different types of facilities. The domestic supply chain ecosystem implements a multi-node supply chain system, which includes a network of multiple interconnected entities, and the interconnected entities are configured to execute supply chain workflows using transportable and continuously trackable storage containers. In one embodiment, the multi-node supply chain system is implemented in the form of a continuous and close-range "fulfillment as a service" (FaaS) network. The multi-node supply chain system disclosed in this article is a predictive and prescriptive collaborative network that fulfills inventory items or products from the nearest endpoint to the destination address based on category-based and proximity-based fulfillment. As Figure 2A-2B The embodiment disclosed herein comprises a network of node facilities, a fleet of vehicles for transporting goods between nodes, and a plurality of storage containers that can be stored in the network of node facilities, which can be transported in the node facilities and can be continuously tracked in real time throughout the multi-node supply chain system. The multi-node supply chain system disclosed herein is like a single and continuous organism, with various different, interconnected, and purpose-specific organs or parts, rather than independent trading entities.

[0072] As used herein, "storage container" refers to an intelligent standardized storage unit that is configured to load, store and transport inventory and customer orders through a multi-node supply chain system. For example, storage containers including single compartment storage (SCS) containers, multi-compartment storage (MCS) containers, and order containers that move downstream and upstream are all intelligent storage containers disclosed below; and the order containers include picked order (PO) containers, completed order (FO) containers, etc. The multi-node supply chain system is configured to allow storage containers to be compatible and capable of storage, transportation and movement. The storage containers disclosed herein serve as the main body of other interconnected entities (such as node facilities of a multi-node supply chain system, fleets of inter-node transportation vehicles, machine processing equipment, etc.). The storage containers connect their respective container identifiers to logistics instructions, such as destination locations, and process-level instructions such as environmental conditions and packaging instructions. In one embodiment, the storage containers disclosed herein have a single form factor and structure for connecting standard and compatible machines and inter-node transportation vehicles throughout the multi-node supply chain system. Storage containers can command and control their own movements, routes and journeys through the multi-node supply chain system, while facilities, machine handling equipment and inter-node transport vehicles are responsible for executing the commands of storage containers. That is, all interconnected entities in the multi-node supply chain system include material handling devices that are specifically configured to manage storage containers.

[0073] like Figures 1A-1D As shown, the node facility network includes a mega facility 10 , a large facility 12 , a small facility 14 , and a nano facility 16 . Figure 1AAccording to an embodiment shown herein, a multi-node supply chain system of mega facilities 10 and large facilities 12 is shown distributed across the country. In one embodiment, the multi-node supply chain system is configured as a domestic supply chain network. Figure 1B According to an embodiment shown herein, the regional distribution of mega facilities 10 and large facilities 12 of a multi-node supply chain system is shown. Figure 1C According to an embodiment shown herein, the distribution of large facilities 12 and small facilities 14 in a town-wide manner of a multi-node supply chain system is shown. Figure 1D According to an embodiment shown herein, the distribution of small facilities 14 and nano-type facilities 16 of a multi-node supply chain system at the local level is shown. In this clearly ordered multi-node supply chain system, as you move to the next category, the number of node facilities in each category will increase, while the individual size will decrease. That is, the number of giant facilities 10 is less than that of large facilities 12, the number of large facilities 12 is less than that of small facilities 14, and the number of small facilities 14 is less than that of nano-type facilities 16. Large facilities 12 are smaller than giant facilities 10, small facilities 14 are smaller than large facilities 12, and nano-type facilities 16 are smaller than small facilities 14. In one embodiment, giant facilities 10 form the entry point for inventory items or products to enter the node facility network for the first time from manufacturers or suppliers, while nano-type facilities 16 form the exit point for inventory items or products to leave the node facility network. In other embodiments, inventory items may enter and exit the node facility network at various points. Unless otherwise defined, the terms "inventory items" and "products" are used interchangeably herein.

[0074] The network of nodal facilities and the inter-nodal transportation vehicles used to transport inventory items between nodal facilities together form a supply chain ecosystem, which may be owned and operated by a singular operating entity, under the control and responsibility of which inventory items are initially received from external suppliers and ultimately delivered to customers or last mile / last mile delivery services. In one embodiment, the operating entity enters into contracts to manage inventory or order fulfillment on behalf of other external entities (such as suppliers who sell goods to customers or other businesses). In one embodiment, the supply chain ecosystem of the operating entity is supplemented by similarly equipped supply chain or distribution channel facilities and / or transportation vehicles of one or more large suppliers that have a partnership or contractual relationship with the operating entity to leverage the large joint supply chain ecosystem formed by the cooperation of the two parties.

[0075] For detailed description, the multi-node supply chain system disclosed in this article is based on Figures 1A-1DThe domestic supply chain ecosystem shown is implemented in a manner; however, the distribution of the node facility network of the multi-node supply chain system in a specific geographic area is not limited to the national scope, and can extend beyond the national borders, or it can be limited to a smaller sub-region, whether such sub-region crosses more than one national border. In one embodiment, at least part of the mega-facilities 10 are located in a coastal area near a large shipping port, thereby providing space for manufacturers or supply goods that are about to arrive by sea. In one embodiment, the large facilities 12 are located in or adjacent to large population centers, such as metropolitan areas and / or major shipping hubs, so that each population center or shipping hub has a large facility 12. In one embodiment, these large population centers contain at least one small facility 14; in another embodiment, they contain multiple small facilities 14. Small cities have large facilities 12, although the general ratio is that small cities have one large facility 12, or adjacent cities share a large facility 12. The number of small facilities 14 in each city is greater than the number of large facilities 12 in or near the city, and the number of nano-type facilities 16 is much greater than the number of small facilities 14.

[0076] The giant facility 10, the large facility 12, and the small facility 14 all include at least one unloading platform, and in one embodiment, the giant facility 10 and the large facility 12 in particular include multiple unloading platforms for real-time loading and unloading of multiple transport vehicles, and / or cross-transfer between transport vehicles at the inbound unloading platform and the outbound unloading platform. In the multi-node supply chain system disclosed herein, each node facility in the node facility network from the giant facility 10 to the nano-sized facility 16 includes an independent configuration structure of the index storage location, also referred to herein as an "index storage configuration structure." In one embodiment, at each giant facility 10, the large facility 12, and the small facility 14, the index storage configuration structure is at least partially defined as Figure 8 One or more three-dimensional grid storage structures of the type shown are serviced by a fleet of machine storage and retrieval vehicles, referred to herein as "machine handling equipment," which are operable to move back and forth between the grid storage structures in three dimensions to deposit storage containers in the three-dimensional grid storage structures or to retrieve storage containers from the three-dimensional grid storage structures. Such three-dimensional grid storage structures, machine storage and retrieval vehicles, and compatible storage containers are disclosed in applicant's U.S. patent applications Nos. 15 / 568,646, 16 / 374,123, 16 / 374,143, and 16 / 354,539, all of which are incorporated herein by reference.

[0077] Figure 2AAccording to one embodiment described herein, a functional block diagram of a multi-node supply chain system 200 is shown that uses transportable storage containers to execute supply chain workflows. The multi-node supply chain system 200 includes a computerized supply chain management system (CSCMS) 201, 204, and 216 for monitoring and controlling the movement of storage containers and order containers throughout the multi-node supply chain 200. The CSCMS controls and monitors the introduction, storage, transportation, and tracking of inventory in storage containers in the multi-node supply chain system 200, as well as the fulfillment of customer orders for the inventory. The CSCMS includes multiple computer systems that can be programmed using a high-level computer programming language. In Figure 2A In one embodiment shown, the CSCMS is a combination of a central computing system 201, a computerized facility management subsystem 204 configured at each mega facility 10, large facility 12, small facility 14, and nano facility 16, and a computerized vehicle management subsystem 216 configured at each of the inter-node transport vehicles 215a, 215b, and 215c. The CSCMS is implemented using programmed purpose-built hardware.

[0078] The central computing system 201 includes one or more computers, including: one or more processors, such as a central processing unit (CPU) 202, which is connected to a network interface, and the network interface is coupled to a communication network, such as the Internet or other wide area networks; and one or more data storage devices, which include non-transitory computer-readable storage media or memory, in which executable software is stored for the processor to perform multiple processes disclosed in the present invention. The term "non-transitory computer-readable storage medium" used herein refers to all computer-readable media, such as non-transitory media, non-transitory media, and transmission media, except for temporary propagation signals. For example, non-volatile media include: solid-state drives, optical disks, magnetic disks, flash memory cards, read-only memories (ROMs), etc. For example, volatile media include: register memories, processor caches, random access memories (RAMs), etc. For example, transmission media include coaxial cables, copper wires, optical cables, modems, etc., including wires that constitute a system coupled to a processor. For example, data storage devices include: one or more databases (such as the central database 203 in the other data disclosed below); such as storage Figure 3E-3F and Figures 4A-4BAs shown, the unique container identifiers (Bin_ID) of all storage containers and order containers 224a-224d in the multi-node supply chain system 200; the unique identifiers (Vendor_ID) of a plurality of large suppliers that have contracted or subscribed to the services of the operating entity for the purpose of inventory storage and order fulfillment in the multi-node supply chain system 200; and the individual inventory catalogs of inventory items or products provided by the suppliers to their customers; and the data storage device is stored or can be stored in the multi-node supply chain system 200. The term "central" as used herein is related to the central computing system 201 and the hosted central database 203, and therefore only represents its status as a shared resource, operably connected to each of the node facilities 10, 12, 14 and 16 of the multi-node supply chain system 200, and each of the inter-node transportation vehicles 215a, 215b and 215c, and does not mean that its elements must be located in a common location.

[0079] The term "communication network" as used herein refers to the Internet, wireless networks, technology communications network, implement the Wi-Fi Alliance technology networks, ultra-wideband (UWB) communication networks, wireless universal serial bus (USB) communication networks, and implementation of the ZigBee Alliance The communication network may be a communication network based on a technology such as a general packet radio service (GPRS) network, a mobile communication network (such as a global system for mobile communications (GSM) communication network, a code division multiple access (CDMA) network, a third generation (3G) mobile communication network, a fourth generation (4G) mobile communication network, a fifth generation (5G) mobile communication network, a long term evolution technology (LTE) mobile communication network, a public telephone network, etc.), a local area network, a wide area network, an Internet connection network, an infrared communication network, etc., or a network formed by any combination of the above networks. The communication network enables multiple facility management subsystems 204 to communicate with each other and with the central computing system 201.

[0080] In one embodiment, CSCMS201, 204 and 216 can be implemented in a cloud computing environment. The term "cloud computing environment" used herein refers to a processing environment that includes configurable computing entities and logical resources, such as networks, servers, storage media, virtual machines, applications, services, etc., as well as data distributed in a communication network. The cloud computing environment provides on-demand network access rights to a shared pool of configurable computing entities and logical resources. CSCMS201, 204 and 216 are cloud computing platforms implemented in the form of services, which can use transportable storage containers to execute supply chain workflows in a bidirectional logic. The central computing system 201 and the central database 203 in this embodiment are respectively referred to as a cloud computer platform and a cloud database. In one embodiment, the facility management system 204 is implemented in the form of installed local deployment software and runs on a computer at each location in the node facilities 10, 12, 14 and 16. In one embodiment, the vehicle management subsystem 216 is implemented in the form of installed local deployment software and runs on a computer at each location in the node transportation vehicles 215a, 215b and 215c.

[0081] The computerized facility management subsystem 204 is installed in each of the node facilities 10, 12, 14 and 16 in the multi-node supply chain system 200. Each facility management subsystem 204 includes one or more local computers, which include: one or more processors, such as a central processing unit (CPU) 205, which is connected to a network interface, and the network interface is coupled to a communication network, such as the Internet or other wide area networks; and one or more data storage devices, which include non-transitory computer-readable storage media, in which executable software is stored for one or more processors to perform multiple processes disclosed in the present invention. The data storage device includes one or more databases, such as individual local facility databases 207, which are used to store data related to individual facilities. In addition to the connection to the wide area network, the local computers of the facility management subsystem 204 are installed in one or more local area networks 206 of the facility, such as a local wireless network, wherein at least one local computer can communicate with the automated container handling device of the facility. For example, the automated container handling devices include machine handling equipment 208, various transporters 210 in giant facilities 10, large facilities 12, small facilities 14, and other processing devices disclosed in the selected embodiments below. On the local area network 206, at least one local computer of the facility management subsystem 204 can also communicate with workstations and other devices, such as fixed and / or mobile human-machine interfaces (HMIs) 209, which are used to guide the performance of various tasks of human employees, transporters 210 and storage containers of the multi-node supply chain system 200. In one embodiment, the multi-node supply chain system 200 further includes an internal positioning system 211, which is operably communicated with the management subsystem 204 of each of the node facilities 10, 12, 14 and 16 to track each storage container in real time, such as Figure 2B In one embodiment, the facility management subsystem 204 is operably and communicatively coupled to a container handling device, such as a container conveyor 222c and a door 213, such as an openable delivery door and an openable pickup door, of the nano-sized facility 16. Figures 21A-21C The implementation method disclosed.

[0082] The computerized vehicle management subsystem 216 is installed in each of the inter-node transport vehicles 215a, 215b and 215c of the multi-node supply chain system 200. Each vehicle management subsystem 216 includes one or more local computers, which include: one or more processors, such as a central processing unit (CPU) 217, which is connected to one or more data storage devices, which include non-temporary computer-readable storage media, in which executable software is stored for the processor to execute multiple processes disclosed by the present invention. The data storage device includes a separate local vehicle database 220, which stores data related to a specific transport vehicle and its transport content. In one embodiment, a wireless communication unit is operably coupled to each of the inter-node transport vehicles 215a, 215b and 215c. The wireless communication unit, such as a wide area communication device 218, is configured to communicate the location of each of the inter-node transport vehicles 215a, 215b and 215c, and the location of any one of the storage containers to the CSCMS when the storage containers are transported between the node facilities 10, 12, 14 and 16. For example, the processor of the vehicle management subsystem 216 is connected to a wireless wide area communication device 218 (e.g., a cellular communication device) for mobile communication with the central computing system 201 over a wireless wide area network (e.g., a cellular network). In one embodiment, a positioning unit (e.g., a global positioning system (GPS)) device 219 is operably coupled to each of the inter-node transport vehicles 215a, 215b, and 215c. The positioning unit is configured to determine the location of each of the inter-node transport vehicles 215a, 215b, and 215c, and in turn determine the location of any storage container transported in the inter-node transport vehicles 215a, 215b, and 215c. The GPS device 219 can also be connected to at least one processor of at least one local computer of the transport vehicles 215a, 215b, and 215c to track the movement of the individual transport vehicles 215a, 215b, and 215c via GPS, and share the GPS coordinates calculated by the individual transport vehicles 215a, 215b, and 215c with the individual local computers for communication with the central computing system 201. In one embodiment, the GPS device 219 of each of the transport vehicles 215a, 215b, and 215c communicates directly with the central computing system 201 to report its GPS coordinates, independent of the local computer of the vehicle management subsystem 216. In one embodiment, the local computer of the vehicle management subsystem 216 is installed on the local area network 221, and at least one local computer communicates with the storage container of the multi-node supply chain system 200 via the local area network 221. In one embodiment, the vehicle management subsystem 216 is operably and communicatively coupled to container handling devices, such as container conveyors 222a and 222b installed in transport vehicles 215a, 215b, and 215c.In one embodiment, the vehicle management subsystem 216 is operably and communicatively coupled to one or more automated container handling devices 223 mounted on a small transport vehicle 215c that delivers the order container to the nano-sized facility 16 .

[0083] The processor disclosed above refers to any one or more of a microprocessor, a CPU device, a finite state machine, a computer, a microcontroller, a digital signal processor, a logic, a logic device, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a chip, etc., which can execute a computer program or a series of commands, instructions or state transitions. In one embodiment, each processor is implemented as a processor set, and the processor includes, for example, a program microprocessor and a mathematical or graphic coprocessor. The CSCMS is not limited to using a processor. In one embodiment, the CSCMS uses a controller or a microcontroller.

[0084] For example, the network interface disclosed above is an infrared interface, an implementation of the Wi-Fi Alliance technology interface, wireless USB interface, Apple's Interface, Ethernet interface, frame relay interface, cable interface, digital subscriber line interface, token ring interface, peripheral controller interconnect interface, local area network interface, wide area network interface, interface using serial protocol, interface using parallel protocol, Ethernet communication interface, asynchronous transfer mode interface, high-speed serial interface, fiber distributed data interface, interface based on transmission control protocol / Internet protocol, interface based on wireless communication technology (satellite technology, radio frequency technology, near field communication, etc.).

[0085] The databases of the multi-node supply chain system 200, such as the central database 203, the local facility database 207, and the local vehicle database 220, refer to any storage area or medium that can be used to store data and files. For example, the database can be a structured query language (SQL) data storage or a Not only SQL (NoSQL) data storage, such as SQL Server, MySQL AB Ltd. Database, MongoDB Neo4j graph database from Neo Technology, Cassandra database from Apache Software Foundation, Database, etc. In one embodiment, the database may also be a location of a file system. In another embodiment, CSCMS 201, 204, and 216 may remotely access the database via a communication network. In another embodiment, the database is configured as a cloud database implemented in a cloud computing environment, where computing resources are delivered in the form of a communication network service.

[0086] Figure 2B A functional block diagram according to an embodiment of the present invention is shown, which shows the configuration and use of storage containers 224 for accommodating, storing and transporting inventory and customer orders in a multi-node supply chain system 200. Storage containers 224 are operably communicated with node facilities 10, 12, 14 and 16, and transport vehicles 215a, 215b and 215c to perform a two-way logistics supply chain workflow. In one embodiment, the predetermined size and configuration of storage containers 224 are compatible with the configuration structure of index storage locations of giant facilities 10, large facilities 12 and small facilities 14. Some storage containers 224 are configured as order containers to be compatible with container handling devices, such as container transporters 222a and 222b of transport vehicles 215a, 215b and 215c traveling between node facilities 10, 12, 14 and 16. In one embodiment, the storage containers 224 are divided into the following types: storage containers for storing inventory items from multiple suppliers; picked order containers (PO containers) for storing inventory items for picked orders; and completed order containers (FO containers) for storing completed orders.

[0087] In one embodiment, storage containers 224 are further classified into the following storage container subtypes: single compartment storage containers (SCS containers) and multi-compartment storage containers (MCS containers). Each SCS container includes a single undivided internal storage space, and is thereby configured to retain a singular item or "per" supplier inventory therein, or to store multiple items or "per" supplier inventory of mutually matching item types. The internal storage space of each MCS container is further subdivided into multiple compartments, and is thereby configured to store mixed inventory items of different item types, and selectively arranged on a compartment basis. MCS containers are used to store inventory items of different inventory item types in individual compartments, respectively, or to store inventory items owned by different suppliers in different individual compartments, respectively. In one embodiment, PO containers are multi-compartment containers having subdivided internal spaces, similar to MCS containers, so that each PO container is configured to receive the contents of multiple customer orders therein, and the individual contents of each customer order are placed in different subsets of the compartments of the PO container, so that customer orders are actually kept isolated from each other. For example, for small customer orders, each individual customer order may occupy one compartment of the PO container, while for large customer orders, one customer order may occupy multiple or even all compartments of the PO container.

[0088] In the second type of order container, the FO container has different sizes and can be optionally configured in a different manner than other types of other storage containers. The size and configuration of the second type of order container is particularly suitable for compatibility with the indexed storage configuration structure of each nano facility 16, as well as the indexed storage configuration structure of the transport vehicle 215c; the transport vehicle 215c only travels between the small facility 14 and the nano facility 16. In one embodiment, the FO container is a single compartment container configured to receive only a single completed order, which has been appropriately packaged and packed, and is in a completed state for pickup by a customer or delivery personnel, or can be shipped to the end customer through the last mile.

[0089] The different types of storage containers 224 disclosed above are electronic smart containers that can exchange data with the facility management subsystem 204 and the vehicle management subsystem 216 to perform container-driven smart navigation of the storage containers 224 in the entire multi-node supply chain system 200. Figure 2B In one embodiment shown, each storage container 224 of the multi-node supply chain system 200 includes a mobile data storage device 226, which is operably coupled to each storage container 224. The mobile data storage device 226 includes a non-transitory computer-readable storage medium configured to store a unique container identifier of the individual storage container 224, and container data related to the inventory items contained in the individual storage container 224. For example, the mobile data storage container 226 includes a computer-readable memory configured to store a static Bin_ID of the storage container 224 and other variable data related to the contents contained in the storage container 224 at any predetermined time. In one embodiment, the mobile data storage device 226 of each storage container 224 is part of the wireless communication unit 225. In one embodiment, the wireless communication unit 225 further includes a wireless transceiver 227 and a local computer processor 228, wherein the local computer processor 228 is connected to the mobile data storage device 226 and the wireless transceiver 227, so as to wirelessly read data from the mobile data storage unit 226 of the storage container 224 and write data to the mobile data storage unit 226 of the storage container 224 through the facility management subsystem 204 of any one of the node facilities 10, 12, 14 and 16, or the vehicle management subsystem 216 of any one of the transport vehicles 215a, 215b and 215c; for example, using the local area network 206 of the facility management subsystem 204, or the local area network 221 of the vehicle management subsystem 216.

[0090] In one embodiment, the node facilities 10, 12, and 14 use machine processing devices 208 to serve the individual configuration structures of the index storage locations, and one or more computers of the facility management subsystem 204 use the same wireless network, such as the local area network 206, to wirelessly control the machine processing devices 208. In one embodiment, each storage container 224 further includes an internal positioning device 229, which is connected to the storage container 224. Figure 2A The internal positioning system 211 of each of the node facilities 10, 12, and 14 shown can be cooperatively operated to wirelessly communicate, so as to track the movement and position of the storage container 224 in the node facilities 10, 12, and 14 even if the storage container 224 is located outside the configuration structure of the index storage location, or moves outside the configuration structure of the index storage location. The internal positioning device 229 is operably coupled to each storage container 224, and the indoor positioning system 211 installed in each of the node facilities 10, 12, and 14. The internal positioning device 229 in each storage container 224 is configured to operably communicate with the internal positioning system 211 to determine and report the location of each storage container 224 in each of the node facilities 10, 12, and 14, so as to track each storage container 224 in real time. In one embodiment, at least one sensor 230 is operably coupled to each storage container 224 to detect the movement of the storage container 224, and in response to the detected movement, to begin tracking the location of the storage container 224 through the multi-node supply chain system 200. Sensors 230 operably coupled to storage containers 224 track the contents of storage containers 224, intra-facility transfers of storage containers 224, and allow for determination of processing required of storage containers 224 and their contents. In one embodiment, sensors 230 are active Internet of Things (IoT) sensors that determine their own actions, routes, and itineraries within the supply chain ecosystem 200, while node facilities 10, 12, 14, and 16, machine processing equipment 208, and inter-node transport vehicles 215a, 215b, and 215c, etc., act as command enablers for individual storage containers.

[0091] Figure 3A-3B According to an embodiment of the present invention, it is displayed Figure 2A. In an embodiment of the organizational structure of the central database 203, the central database 203 includes: a supplier table 301, a supplier product table 303, a supplier inventory table 304, a facility table 306, a transport vehicle table 307, a storage container table 308, a storage container content table 309, a storage location table 310, a picked order container table 311, a picked order (PO) container content table 312, a completed order (FO) container table 313, a customer table 314, a customer order table 315, an order line item table 316, a supply goods table 317, and a goods details table 318. The supplier table 301 contains a supplier identifier (Vendor_ID) and other details of the ordering supplier 302, such as their official company name, address, and payment information. For each supplier identified in the supplier table 301, the individual supplier's supplied products table 303 and the supplier inventory table 304 can be operated in conjunction to define the supplier product catalog 305 of the particular supplier in the central database 203. For each product type that the supplier has, the individual records in the supplier product table 303 contain at least one unique product identifier (Product_ID) for the particular product type. For greater clarity in the specific embodiments described below, the unique product identifier includes at least one global product identifier (GlobalProduct_ID), such as a universal product code (UPC); all subscribing suppliers 302 can identify the product type by the identifier. In one embodiment, a vendor-specific product identifier (Vendor Product_ID), such as a stock keeping unit (SKU) code, is stored in each record of the supplier product table 303. In embodiments where shared identifiability of products between different subscribing suppliers 302 is not required, a SKU code or another Vendor Product_ID is used alone without a standardized format Global Product_ID that is readable by other subscribing suppliers 302.

[0092] In one embodiment, each product record in the supplier product table 303 includes one or more product attributes of a specific product, such as size, color, etc.; supplier-specific product processing data, which defines the specific actions and conditions that the product type must meet when the product moves in the multi-node supply chain system 200; supplier-specific custom data, which defines the performance of one or more modifications made by the operating entity according to value-added services (VAS), such as repackaging, labeling, pricing, anti-theft tags, etc.; environmental data about controlled environmental conditions or lack of controlled environmental conditions for specific products, for example, the product may need to be protected from damage, leakage or deterioration due to its own nature, or the hazards caused must be avoided, prevented and / or minimized, etc.

[0093] Examples of product handling data include signs, codes, or instructions regarding: product packaging requirements, such as placing heavier or leaky items at the bottom of a multi-item order, placing lighter or fragile items at the top of a multi-item order, grouping or separating items by product type, etc.; and packaging requirements related to the selection and application of specific packaging types (such as tissue paper, bubble wrap, wrapping paper, or other packaging materials) for specific products; the placement of products in bags, boxes, or other containers; and the selection of packaging materials, bags, boxes, or containers of different brands, styles, sizes, or thicknesses. Other examples of product handling data include signs, codes, or instructions related to the storage and / or handling of items with volatile, flammable, or other hazardous properties in special facilities, facility areas, facility workstations, or transportation vehicles that require specific delivery schedules or transportation; and signs, codes, or instructions for food allergy safe handling to avoid cross contamination. Examples of environmental data include: instructions for frozen storage requirements for frozen foods; instructions for refrigerator storage requirements for refrigerated foods that do not require refrigeration; instructions for ambient storage acceptability for general items that do not require specific controlled environmental conditions, etc. In one embodiment, the CSCMS uses environmental data to determine and control the placement of products within various controlled areas or zones of environmentally distinct or environmentally controlled storage areas within nodal facilities and transportation vehicles of the multi-nodal supply chain system 200.

[0094] One or more of the product handling data, custom data, and environmental data are categorized according to different stages in the multi-node supply chain system 200, and precautions for marking or the aforementioned instructions should be noted or followed in the system to distinguish the actions to be taken on the two when the products are classified with the compliant products and transported in single compartment storage (SCS) containers, so that the same custom tasks or VAS actions are performed on the compliant products before the compliant products are picked from the supplier's inventory to fulfill the order, rather than taking other actions further downstream, such as packaging and packing markings, codes, or instructions, which apply to the final packaging and packaging of the completed customer order.

[0095] In one embodiment, each product record in the supplier product table 303 further includes: a customer selling price, i.e., the price at which the product is intended to be sold to the supplier's customers; a maximum purchase price; and a supplier selling price, i.e., the price at which the product is offered to other suppliers to fulfill their inventory shortages. In one embodiment, each product record in the supplier product table 303 includes time data, which is related to any time restrictions on inventory. The supplier inventory table 304 of each supplier's individual product catalog 305 has sufficient data to identify the specific product quantities and destinations of inventory products currently in the supply chain ecosystem on behalf of the supplier, either directly or through relationships with other tables in the central database 203. Each inventory record in the supplier inventory table 304 includes some or all of the following items: a compartment identifier (Compartment_ID) of a specific compartment of a storage container that stores one or more inventory products currently in stock of the supplier; the individual Bin_ID of the storage container to which the compartment belongs; a unique facility identifier (Facility_ID) of the specific facility in which the storage container is currently located, or a unique vehicle identifier (Vehicle_ID) of the specific transport vehicle in which the storage container is currently located; the supplier and / or global Product_ID of one or more inventory products in the storage container compartment; the quantity of one or more inventory products in the storage container compartment; and a unique location identifier (Location_ID) of a specific storage location, if the storage container is currently stored in a configuration structure of indexed storage locations, then the storage container is located in a configuration structure of indexed storage locations of a facility or transport vehicle. In an embodiment using subdivided multi-compartment storage (MCS) containers, each inventory record in the supplier inventory table 304 includes at least a Product_ID and a Compartment_ID, through Figure 3A-3B The relationship with other tables shown can be derived from other optional record contents disclosed above. In embodiments where the subdivided MCS container is not used, the Compartment_ID field can be omitted and replaced by combining Bin_ID and Product_ID to achieve the same functional purpose.

[0096] exist Figure 3AIn the example, the supplier inventory table 304 includes Facility_ID / Vehicle_ID, Location_ID, and Bin_ID to show the various data that can be pulled from the central database 203 in response to a query for a specific Product_ID. In one embodiment, data can be pulled through relationships with other tables without having to place such data in the supplier inventory table 304. Similarly, those with ordinary knowledge in the art will understand that the redundant data in other tables disclosed herein is for explanation purposes only, and a more standardized database structure can be implemented in practice to reduce such data redundancy.

[0097] like Figure 3A As shown, the facility table 306 of the central database 203 includes records, each record includes a static field with Facility_ID of an individual facility, and other important information related to the facility, such as a street address and / or its global positioning system (GPS) coordinates; and in one embodiment, the record includes environmental data, which is used to identify whether the facility has environmental control storage capabilities, such as whether it should be stored in a refrigerated storage area and / or a frozen storage area, or a normal temperature storage area. In one embodiment, if all facilities in the entire multi-node supply chain system 200 are equipped with the same type of environmentally different storage areas, this facility table 306 will omit this environmental data. The transportation vehicle table 307 of the central database 203 includes records, each record includes at least: a static field with Vehicle_ID of an individual transportation vehicle of the multi-node supply chain system 200, and a variable destination field of Facility_ID of the facility to which the transportation vehicle is to go next. In one embodiment, the environmental data field related to the environmental control storage capability of the transportation vehicle. In one embodiment, if all transport vehicles in the entire multi-node supply chain system 200 are equipped with the same type of environmentally distinct storage area, the environmental data is omitted from the transport vehicle table 307. In one embodiment, the transport vehicle table 307 includes: the transport vehicle type, the current or last recorded GPS coordinates of the transport vehicle, and / or the estimated time of arrival (ETA) of the destination facility.

[0098] The storage container table 308 of the central database 203 stores the Bin_ID of all storage containers of the multi-node supply chain system 200. If the storage container is currently located in an indexed storage configuration structure, or a dynamic storage location of a machine processing device or a transporter with a storage container above it, and the storage container is moving in and out of the facility, the Bin_ID in the individual record also includes: the Facility_ID of the facility where the individual storage container is currently located; or the Vehicle_ID of the transport vehicle where the individual storage container is currently located; and the Location_ID of the specific storage location of the indexed storage configuration structure of the facility or transport vehicle where the storage container is located. In one embodiment, the storage container is configured as a multi-compartment storage (MCS) container, and each storage container record also includes a compartment field, which is used to store the individual compartment identifier (Compartment_ID) of each MCS container compartment. In an embodiment using only SCS, the storage container record does not include a compartment field. In one embodiment, the storage container table 308 stores environmental flags that indicate environmental conditions or content requirements of the storage container.

[0099] In one embodiment, the storage container contents table 309 of the central database 203 contains and allows tracking of the contents of each compartment of each storage container. Each record in the storage container contents table 309 includes: the Compartment_ID of a particular storage container compartment; the Bin_ID of the storage container to which the particular compartment belongs; the Product_ID of one or more products in the compartment of the storage container; the number of products in the compartment of the storage container; and the Vendor_ID of the vendor that owns the product. In embodiments where MCS containers are not used and only SCS containers are used, the use of the Compartment_ID field can be omitted. In these embodiments, Figure 3A The remaining data fields of the storage container contents table 309 are shown to be stored directly in the storage container table 308, since each container's Bin_ID can be used to track the location of the supplier's inventory.

[0100] The global storage location table 310 of the central database 203 lists all indexed storage locations of the indexed storage configuration structure of all facilities and transport vehicles. Therefore, each record in this global storage location table 310 includes: Location_ID of an individual storage location in the multi-node supply chain system 200; Facility_ID of the facility where the storage location is located or Vehicle_ID of the transport vehicle where the storage location is located; Environmental status indicator, which reflects the type of environmental control to which the storage location belongs; and Bin_ID of the storage container or order container currently stored in the storage location, if any. The environmental status indicator indicates that the storage location should be located in the normal temperature storage area, refrigerated storage area, or frozen storage area of ​​the predetermined facility or transport vehicle.

[0101] Therefore, the index storage configuration structure of all facilities and all transport vehicles is the index storage configuration structure of the entire multi-node supply chain system 200, because the footprint of the individual index storage locations of the entire multi-node supply chain system 200 has a specific size and shape to place and store individual singular storage containers therein, and has an individual location identifier or address (Location_ID) in the record of the central database 203, through which the exact destination of any storage container at the end of any index storage configuration structure can be identified at any time, even during transportation between facilities, because there is such an index storage configuration structure in the transport vehicle. By combining the supplier inventory table 304, the facility table 306, the transport vehicle table 307, the storage container table 308, the storage container content table 309 and the global storage location table 310, the location of all inventory placed in the storage container and introduced into any index storage configuration structure compatible with the storage container can be recorded and tracked. In one embodiment of the multi-node supply chain system 200 that uses only room temperature storage and no environmentally controlled storage environment (including refrigerated storage areas and / or frozen storage areas), the supplier product table 303 and the facility table 306 will omit environmental data, and the global storage location table 310 will omit environmental status.

[0102] In addition to the storage containers used to store supplier inventory, the PO containers of the multi-node supply chain system 200 also adopt the same standardized size and configuration as the storage containers, so the picked orders in these PO containers can also be stored in the indexed storage locations in the giant facility, the large facility and the small facility, and can also be stored on the transport vehicles traveling between the two places according to the ratio of container location to 1:1. Therefore, the PO container table 311 of the central database 203 is a structure similar to the storage container table 308. Therefore, if the PO container is currently located in an indexed storage configuration structure, or is located in a dynamic storage location on a machine handling device or a conveyor, and the PO container on the machine handling device or the transporter is moving within the facility or moving out of the facility, then each record of the PO container table 311 contains static fields: the Bin_ID of the individual PO container; the Facility_ID of the facility where the individual PO container is currently located, or the Vehicle_ID of the transport vehicle where the individual PO container is currently located; and the Location_ID of the specific storage location of the indexed storage configuration structure of the facility or the transport vehicle where the PO container is located.

[0103] In one embodiment, a PO container is an MCS container that can store multiple customer orders. Therefore, each PO container record in the PO container table 311 includes a static field that contains the Compartment_ID of the individual PO container. In this embodiment, the individual PO container contents table 312 of the central database 203 tracks the contents of each compartment of each PO container. Therefore, each record in the PO container contents table 312 includes: the Compartment_ID of the individual PO container compartment; the Bin_ID of the PO container to which the compartment belongs; the order number of a specific customer order in which one or more ordered products are located in the compartment; the column item number of a specific customer order in the compartment that is fully or partially fulfilled by one or more ordered products; and the quantity of the local products in the compartment. The column items and quantities in the PO container contents table 312 represent the distribution of the contents of a large order across multiple compartments, or even multiple PO containers. In embodiments where the PO container is not subdivided into multiple compartments, the PO container's Compartment_ID is not used because each order container has only a single compartment, in which case the Bin_ID is used to identify the destination of the order in process. In these embodiments, there is no PO container contents table 312 at all, and the order number, column item number and quantity are recorded directly in the PO container table 311.

[0104] The order number recorded in the PO container contents table 312 is retrieved and assigned from the individual customer orders table 315, each order containing: the order number of the individual customer order, the unique identifier of the customer whose customer order is still outstanding (Customer_ID), the unique identifier of the vendor fulfilling the customer order (Vendor_ID), and any shipping preferences used during the creation of the order. In the related order line item table 316, each record contains the line item number, the order number of the customer order to which the line item belongs, the Product_ID of the product type required to fulfill the line item of the customer order, and the quantity of the product type fulfilled for the line item. The Customer_ID for each customer is also stored in the individual customer table 314 along with other customer account information (including each customer's name, address, and payment information).

[0105] In addition to multi-compartment PO containers that hold in-process orders, in one embodiment, the multi-node supply chain system 200 also uses single-compartment FO containers, where multiple orders from a single customer are packed and packaged for pickup or shipped to the customer once they are completed. In one embodiment, the standardized size and storage capacity of the FO container are smaller than the PO container, for example, it may be only about half of other containers. The small FO container is not compatible with the indexed storage configuration structure of giant facilities, large facilities and small facilities, or transportation vehicles traveling between facilities, and its size and configuration are suitable for different types of indexed storage configuration structures used by nano-scale facilities.

[0106] If the FO container is currently located in an indexed storage configuration, or a dynamic storage location of a machine handling device or transporter with a storage container above it, and the storage container is moving in or out of the facility, each record of the FO container table 313 of the database 203 includes static fields, which include: the Bin_ID of the individual FO container; the order number of a specific customer order, and one or more products on the customer order are located in the FO container; the Facility_ID of the facility where the individual FO container is currently located, or the Vehicle_ID of the transport vehicle where the individual FO container is currently located; and the Location_ID of the specific storage location of the indexed storage configuration of the facility or transport vehicle where the FO container is located. In order to accommodate the delivery of large orders of multiple FO containers, in one embodiment, each record in the FO container table 313 further includes: the column item number of the specific customer order that is fully or partially fulfilled by one or more ordered products in the FO container; and the quantity of the ordered products in the FO container. In one embodiment, the FO container table 313 further stores the customer's unique identifier (Customer_ID), and the fulfillment status and / or return status of the customer's order.

[0107] The supply cargo table 317 of the central database 203 has scheduled expected inventory supply shipments to transport new inventory to the multi-node supply chain system 200, especially to a mega facility. Each record of the supply cargo table 317 contains: a unique identifier (Shipment_ID) of the expected supply cargo; a unique identifier (Supplier_ID) of the supplier from which the supply cargo is sourced; a Vendor_ID representing the operating entity of the receiving supplier (i.e., the supplier that owns the inventory that has just arrived); and a Facility_ID of the destination facility to which the cargo has been scheduled to be shipped. The contents of the supply cargo are itemized in the individual cargo details table 318, and each record of the contents includes: a unique identifier (Case_ID) of each box of products in the expected supply cargo; the Shipment_ID of the cargo to which the box belongs; the Product_ID of the product type contained in the box; and the quantity of the product type in the box.

[0108] Figure 3C-3D According to an embodiment of the present invention, it is displayed Figure 2A-2B The local facility database 207 and the local vehicle database 220 of the multi-node supply chain system 200 are shown. In one embodiment of the organizational structure of the local facility database 207 of the multi-node supply chain system 200, the local facility database 207 includes a facility storage table 320a, in which only individual storage locations of the storage configuration structure of a specific facility are indexed, and Figure 3B In contrast, the global storage location table 310 of the central database 203 is shown to provide a global index of all storage locations throughout the multi-node supply chain system 200. Like the global storage location table 310, each record of the facility storage table 320a includes static fields for the following identifiers: Location_ID of the individual storage location; an environmental status indicator reflecting the type of environmental control to which the storage location belongs, such as a room temperature storage area, a refrigerated storage area, or a frozen storage area; and the Bin_ID of the storage container currently stored at the location, if any.

[0109] The local facility database 207 further includes an automatic device information table 320b, which includes a static field unique identifier (Equipment_ID) for each part of the automatic device, such as a machine handling device or a transporter that can operate in a specific facility. The machine handling device can index and define the dynamic storage location of the storage container when it moves within the facility or moves out of the facility. In one embodiment, the transporter also defines the storage location, and the storage container is transferred within the facility or from the facility to the transport vehicle, or from the transport vehicle to the facility. When the machine handling device or transporter inside or outside the facility finds the storage container, it will use the Equipment_ID as the Location_ID of the storage container to continuously track the storage container. The automatic device information table 320b further includes a variable field for the Bin_ID of the storage container, which is currently stored in a specific machine handling device or transporter and is moved within and outside the facility by the specific machine handling device or transporter. The automatic device information table 320b also stores other information such as the type of device, such as the real-time location of the machine handling device or transporter, the automatic device, etc. In another embodiment, a manual operating device (such as a forklift) also corresponds to an Equipment_ID and defines a dynamic storage location. In this embodiment, when a storage container is manually operated by a manual operating device in a facility, the Equipment_ID of the manual operating device is used as the Location_ID of the storage container to continuously track the storage container.

[0110] The local facility database 207 further includes one or more on-site container tables 322 that list the Bin_IDs of all storage containers at a particular facility and / or order containers currently located at a particular facility. In one embodiment, the on-site container tables 322 of the local database 207 include: fields to store the empty / full status of each storage container; environmental flags; Location_ID of the individual storage location; destination Facility_ID; and time data. For facilities with multiple container types, in one embodiment, each container type in the local facility database 207 has its own individual on-site container table 322. The local facility database 207 further includes a workstation information table 321, which contains unique identifiers (Workstation_IDs) of different workstations located in the specific facility; for each such workstation, the workstation type indicates the type of work operation performed at the workstation, such as an introduction workstation, a value-added service (VAS) workstation, a supporting workstation, a picking workstation, a packing workstation, etc.; the location of the workstation in the facility, which is presented in an address format configured to command machine handling equipment to travel to it, and / or to transport or deliver storage containers to it through a transporter or other automated container handling device; the specific work of the inventory in the workstation tools, such as packaging, marking and labeling tools; and in one embodiment, one or more workstation category fields, which specify any special operating characteristics or functions provided by the workstation to distinguish it from other workstations of the same type, such as the category field represents compatibility or incompatibility with specific types of products, for example: food-grade workstations should maintain higher exposed food handling hygiene standards; allergen-safe workstations, which prohibit the use of allergenic products and can be classified by subcategories, such as: potato-free, tree nut-free, gluten-free, shellfish-free, dairy-free, etc.; and dangerous goods workstations, which specialize in handling dangerous goods prohibited by other workstation categories. In one embodiment, classification is based on a mark, and only exclusive workstations are marked as special classifications, while the absence of such a mark indicates that a general cargo workstation can accept any items outside of controlled product categories (such as dangerous goods, exposed foods, etc.), regardless of whether the items may contain allergens. The local facility database 207 further includes a facility information table 319, which is used to store the same or similar content into Figure 3A Individual records in the facility table 306 of the central database 203 are shown. In one embodiment, the facility information table 319 may optionally store container quantity information to identify the number of empty storage containers and filled storage containers currently located in the facility.

[0111] like Figure 3DAs shown, each local vehicle database 220 includes a vehicle storage table 324a, which only indexes the individual storage locations of the storage configuration structure of a specific transport vehicle. Similar to the facility storage table 320a of each local facility database 207, each record of the vehicle storage table 324a includes static fields of the following identifiers: Location_ID of the individual storage location in the indexed storage configuration structure of the transport vehicle; an environmental status indicator reflecting the type of environmental control to which the storage location belongs, such as a normal temperature storage area, a refrigerated storage area, or a frozen storage area; and Bin_ID of the storage container currently stored at the location, if any. In one embodiment, the local vehicle database 220 further includes an automatic device information table 324b, which and Figure 3C The local vehicle database 220 further includes one or more on-vehicle container tables 325, which list the Bin_IDs of all storage containers and / or order containers currently located on a specific transport vehicle. The local vehicle database 220 further includes a vehicle information table 323, which is used to store the same or similar content in Figure 3A Individual records in the transport vehicle table 307 of the central database 203 are shown. In one embodiment, the vehicle information table 323 can selectively store container quantity information to identify the number of empty storage containers and stored storage containers, and / or order containers currently on the transport vehicle.

[0112] Figure 3E-3F According to one embodiment of the present invention, local data stored in different types of storage containers 224a, 224b, 224c, and 224d are shown. The data is stored in the mobile data storage device 226 of the storage containers 224a, 224b, 224c, and 224d, for example, with Figure 2A The central database 203 of the central computing system 201, the local facility database 207 of the facility management subsystem 204, and the local vehicle database 220 of the vehicle management subsystem 216 are stored in a tabular database format similar to that shown. The container information table 326 will store on the mobile data storage device 226 that stores the storage containers 224a and 224b of the supplier's inventory: the static Bin_ID of the storage container; the Compartment_ID of the storage container; the environmental flag that specifies whether the storage container is compatible; and the facilities and transportation vehicles will have different environmentally controlled storage areas, at least in embodiments using specific environmental storage containers, for example, storage containers for low-temperature or normal temperature storage, and / or different types of low-temperature storage (such as refrigeration or freezing), using storage containers of different materials or compositions. In one embodiment, the container information table 326 further includes container processing data, for example, by combining the container processing data and Figure 3AThe comparison of the product handling data of the supplier product table 303 shown helps to select a specific storage container for a predetermined product type to check: whether the storage container meets the product handling conditions; the destination data, which is identified by Figure 2A-2B The multi-node supply chain system 200 shown includes information about a specific facility, geographic region, or other destination to which a storage container is to be transported; and time data regarding any time constraints for transporting the storage container to its intended destination. One example of container handling information in the container information table 326 is the designation of a specific storage container as an allergy-safe storage container that does not contain one or more specific allergenic product types, such as potatoes, tree nuts, gluten, shellfish, dairy products, etc.

[0113] Furthermore, the content table 327 records the variable contents of the storage container at any predetermined time on the mobile data storage device 226 of the storage container 224a and 224b storing the supplier's inventory. Each record of this content table 327 includes: the Compartment_ID of the individual compartment of the storage container; the Product_ID of the product type stored in the compartment of the storage container; the quantity of the product type stored in the compartment of the storage container; and the Vendor_ID of the specific supplier to which the quantity of the individual product type belongs. In an embodiment using a single compartment storage (SCS) container 224a, the container information table 326 and the content table 327 may or may not have the Compartment_ID. Furthermore, on the mobile data storage device 226 of the storage container 224a and 224b storing the supplier's inventory, the fields of the supplier product table 303 of one or more suppliers whose products are stored in one or more compartments of the storage container are written into the product information table 328. Thus, each record in the product information table 328 for storage containers 224a and 224b includes the individual supplier and / or global Product_ID of the contents table 327, and a copy of all or part of the fields of the corresponding product record in the supplier product table 303 for that supplier, including, for example, product handling data, customization data, and environmental data, which will be used to guide handling and customization in one or more facilities, as well as environmental layout in facilities and transport vehicles.

[0114] Furthermore, the contents of the mobile data storage device 226 of the multi-compartment PO container 224c are similar to the contents of the mobile data storage device 226 of the multi-compartment storage (MCS) container 224b, for example, may be completely or substantially similar in terms of the container information table 326 and the product information table 328, although the custom data may be omitted, and are different in terms of the content table 327, because the PO container 224c is used to store picked customer orders, rather than unpicked supplier inventory, so the order content can be identified by the customer order. For the PO container 224c, each record of the content table 327 includes: the Compartment_ID of the individual compartment of the PO container 224c; the order number of the specific customer order of the product type in the compartment; the Customer_ID of the specific customer whose customer order has been fulfilled; the column item number used to identify the individual column item of the customer order fulfilled by the product type in the compartment; the Product_ID of the product type in the compartment; the quantity of the product type in the compartment; and the Vendor_ID of the specific supplier from whose inventory the picked product type was picked. In one embodiment, each record in the content table 327 stored in the mobile data storage device 226 of the PO container 224c includes destination data and order time data.

[0115] Moreover, the contents of the mobile data storage device 226 of the single compartment FO container 224d are similar to the contents of the mobile data storage device 226 of the multi-compartment PO container 224c. For example, although the singular Compartment_ID of the FO container 224d may be omitted, the container information table 326, the container content table 327, and the product information table 328 may be completely or substantially similar. The reader should be able to understand that Figures 3A-3D The central database 203, the local facility database 207 and the local vehicle database 220 are shown, and Figure 3E-3F The specific displayed and described data layout and organization in the mobile data storage device 226 of the various storage containers 224a-224d shown, and the specific selection of specific fields contained in the various records thereof, are provided for example only and are not intended to limit the scope of the embodiments disclosed herein. The specific fields identified are generally particularly related to the operational details of the various embodiments detailed herein, while other embodiments may employ additional data for added or unrelated functions, or omit optional data that is not necessary for other embodiments, which have a subset of the features and functions set forth in the particularly detailed embodiments.

[0116] Figure 4A According to one embodiment of the present invention, storage containers for supply, inventory and filled order requirements are shown, and the workflow in a forward or downstream direction through the multi-node supply chain system 200. Figure 4AA series of inbound and outbound transportation in a mega facility 10, a large facility 12, and a small facility 14 is shown, beginning with the mega facility 10 receiving incoming supply shipments 401a and 401b from manufacturers, vendors, and / or distribution centers, which entities are operated by external entities, cooperative entities, or contracted entities, referred to herein as "vendors." The multi-node supply chain system 200 manages: the individual node facilities 10, 12, 14, and 16 in the system; the workflow between the facilities; the workflow related to supply goods, product inventory, customer orders; and the storage containers and order containers that store and transport supply goods, product inventory, and customer orders throughout the multi-node supply chain system 200. At least a portion of the supply goods delivered to the mega facility 10 will typically be full case shipments 401a, where each case, such as a carton, reusable bag, or other container, contains only one product type, i.e., products that match the Product_ID. The term "Stock Keeping Unit (SKU)" as used herein is used to represent a unique product identifier, either a global product identifier or a vendor-specific product identifier. Thus, a single SKU box or single SKU container refers to a box or container that contains the same type of products, regardless of whether the equivalence of those products is based on a matching SKU, a matching universal product code (UPC), or other matching universal or vendor-specific product identifiers shared by those products. Full case shipments 401a often arrive at the mega facility 10 from the manufacturer in a palletized manner, i.e., on pallets 402. Therefore, each mega facility 10 will include at least one depalletizing station for depalletizing full case shipments 401a. Other full case shipments 401a may arrive already unloaded rather than loaded on pallets, in which case the depalletizing process is not required and the depalletizing stations in the mega facility 10 may be omitted or bypassed.

[0117] In addition to or as an alternative to full case shipments 401a in conventional product packaging, such as in cartons or shipping bags, either palletized or loose, incoming supply shipments may include pre-containerized shipments 401b and 401c, in which products are delivered from the manufacturer using storage containers 224a and 224b, respectively, that are compatible with the indexed storage configurations of the mega facility 10, large facility 12, and small facility 14. In these cases, the storage containers 224a that arrive at the mega facility 10 in a pre-loaded state from the manufacturer may be single compartment storage (SCS) containers 224a, each containing only products of a conforming product type, which may be introduced directly into the indexed storage configuration of the mega facility 10 without the additional step of transferring the products from the SCS containers 224a in which they arrived to other SCS containers 224a.

[0118] The SCS container 224a, which is loaded at the mega facility 10 or received via a pre-containerized shipment 401b (also referred to as a "single SKU container"), is loaded from the mega facility 10 onto a large transport vehicle 215a (e.g., a semi-trailer truck) and transported downstream to one of the mega facilities 12. In the mega facility 12, the SCS container 224a is used to load a multi-compartment storage (DMCS) 224b container that is already loaded and moving downstream. The DMCS container 224b, also referred to as a "multi-SKU container", is loaded from the mega facility 12 onto a large transport vehicle 215b (e.g., a semi-trailer truck) and transported downstream to one of the small facilities 14. In one embodiment, the small facility 14 also receives the DMCS container 224b from the pre-containerized shipment 401c. The storage containers of the small facility 14 include a filled order (FO) container 224d, which is smaller in standardized size and footprint than the other storage containers 224a and 224b. In one embodiment, these FO containers 224d are approximately half the size and area of ​​the other storage containers 224a and 224b, and each only holds a single customer order, so there is no need to subdivide their internal structure like the DMCS container 224b. In this embodiment, these smaller FO containers 224d are Figure 2A-2B The index storage configuration structure and machine processing equipment 208 of the large facility 10, large facility 12 and small facility 14 shown, or Figure 2A-2B While the container transporters 222a of transport vehicles 215a and 215b are not shown to be compatible, these smaller FO containers 224d are sized and configured to be particularly suitable for the different types of indexed storage configurations used on the nano-facility 16 and transport vehicle 215c.

[0119] Figure 4B According to one embodiment of the present invention, the empty storage containers 224a, 224b, and 224d returned from the client are displayed, and the workflow in the reverse or upstream direction of the multi-node supply chain system 200 is shown. The multi-node supply chain system 200 disclosed in this article automatically manages the inventory management workflow step by step, wherein the storage containers 224a, 224b, 224d are exchanged one-to-one (i.e., 1:1) at each of the node facilities 10, 12, 14, 16 including the endpoints to allow the storage containers 224a, 224b, 224d to pass through the multi-node supply chain system 400 in an equivalent and continuous process in the forward and reverse directions. Therefore, the multi-node supply chain system 200 allows each of the node facilities 10, 12, 14, and 16 to conduct 1:1 transactions with the corresponding transport vehicles 215a, 215b, and 215c, allowing Figure 4B The reverse process of the storage containers 224a, 224b and 224d is shown. Figure 4A The forward process shown is the same, allowing the multi-node supply chain system 200 to operate step by step.

[0120] Figure 5 According to an embodiment of the present invention, it is displayed Figure 2A-2B and Figures 4A-4B FIG. 1 is a top view of the structure of the mega facility 10 of the multi-node supply chain system 200 shown in FIG. The mega facility 10 includes an inbound unloading platform 501, an outbound unloading platform 502, and an index storage configuration structure having a grid storage structure 507. In one embodiment, the inbound unloading platform 501 and the outbound unloading platform 502 are located on opposite sides or opposite ends of the mega facility 10. In one embodiment, the grid storage structure 507 is Figure 8 of the type shown and in Figure 8 . In this embodiment, the grid storage structure 507 is subdivided into a plurality of environmentally distinct storage areas, such as a main ambient temperature area 507a, a small refrigerated area 507b, and an even smaller frozen area 507. In one embodiment, the number of environmentally distinct storage areas and their corresponding proportions and locations in the grid storage structure 507 may vary. By subdividing the grid storage structure 507 into environmentally distinct storage areas 507a, 507b, and 507c, the environmentally distinct storage areas 507a, 507b, and 507c of the mega-facility 10 are served by the same shared cluster of machine processing equipment 208 operating on the grid storage structure 507. The structure and operation of this type of subdivided multi-area storage structure are disclosed in U.S. Provisional Patent Application No. 62 / 891,549, which is incorporated herein by reference in its entirety. In another embodiment, smaller independent storage structures are used as an alternative to a single grid storage structure 507 in different environmentally controlled subsections of the mega-facility 10, which are subdivided into environmentally isolated and environmentally distinct storage areas.

[0121] Next to the inbound unloading platform 501 is a series of independent depalletizing stations 503, which are located next to individual infeed conveyors 504. The depalletizing stations 503 allow human employees or robot workers or other automated devices to break down or palletize full case shipments arriving from manufacturers into individual cases. If the goods arriving at the mega facility 10 are bulk rather than palletized, depalletizing is not required and the depalletizing stations 503 can be omitted or skipped. The infeed conveyors 504 feed into a shared inbound conveyor 505 and then proceed to a series of inbound stations 506. Each inbound station 506 is adjacent to the lower track structure of the grid storage structure 507 so that inventory placed in the storage containers of the inbound station 506 is inducted into the index storage structure by the fleet of machine handling equipment 208 operating on the index storage structure 507. In one embodiment, to assist in fully or partially automatically transferring storage containers to the outbound unloading platform 502, and fully or partially automatically loading storage containers onto outbound transport vehicles at the outbound unloading platform 502, the outbound unloading platform 502 is adjacent to a loading grid structure 509, which is directly connected to one of the track structures, such as the lower track structure of the grid storage structure 507, thereby forming an extension of the grid storage structure 507; the same fleet of machine handling equipment 208 can leave the grid storage structure 507 on the extension and travel to any outbound unloading platform 502. In one embodiment, the loading grid structure 509 is a three-dimensional structure including one or more vertical axes, and the machine handling equipment 208 can be raised and lowered on the vertical axes to a suitable height of the outbound unloading platform 502 to deliver or unload goods to the trailer of the outbound transport vehicle parked at that height.

[0122] In one embodiment, the loading grid structure 509 is located in the entire grid storage structure 507 from the introduction workstation 506, and the introduction workstation 506 is as shown in FIG. Figure 5 507, located on the same side of the inbound unloading platform 501 and the depalletizing station 503 relative to the grid storage structure 507. In one embodiment, the mega facility 10 includes additional ejection stations 508, which are similar to the inbound station 506, adjacent to the lower track structure of the grid storage structure 507, which are directly served by the machine handling equipment 208 that moves back and forth in the grid storage structure 507. These ejection stations 508 facilitate the removal of storage containers from the grid storage structure 507 for various purposes, as well as the transport of storage containers to outbound transport vehicles by the machine handling equipment 208 through the cargo grid structure 509.

[0123] In one embodiment, each of the inlet station 506 and ejection station 508 is of a type that allows the machine handling device 208 to carry storage containers through the inlet station 506 and ejection station 508 by traveling on an extended track of the lower track structure of the grid storage structure 507. In this method, the same fleet of machine handling devices 208 is responsible for moving storage containers back and forth between the employee interaction of the inlet station 506 and ejection station 508 and the storage location in the grid storage structure 507, depositing storage containers or removing them. In one embodiment, each workstation 506 and 508 includes an opening 506a and 508a, respectively, which is located on the workbench of the respective workstation 506 and 508, which means that human employees or machine operators at the corresponding workstations 506 and 508 can handle the storage containers transported by the machine to place products into the storage containers or remove products from the storage containers. The open opening 506a of the intake station 506 is referred to herein as a "placement opening" because products are typically placed into storage containers at the intake station 506, and the open opening 508a of the ejection station 508 is referred to herein as a "retrieval opening" because products are typically taken out of storage containers at the ejection station 508. Although each of the intake station 506 and the ejection station 508 has a similar workbench type, which is configured as a horizontal workbench for use by human employees at the workstations 506 and 508 and at the openings of these workbenches to retrieve storage containers delivered under these workbenches, the terms "retrieval opening" and "placement opening" are used herein in a general sense unless otherwise specified, indicating any interaction point of the correct position and orientation of a storage container for human employees or machine workers at the workstations 506 and 508 to retrieve, regardless of whether the retrieval is performed through an opening defined by the workbench or other surrounding structures.

[0124] Figure 6 According to an embodiment of the present invention, it is displayed Figure 2A-2B and Figures 4A-4BA structural top view of a large facility 12 of a multi-node supply chain system 200 shown in FIG. The large facility 12 includes an inbound unloading platform 601, an outbound unloading platform 602, and an index storage configuration structure 603 having a grid storage structure 10, which is similar to the giant facility 10. The inbound unloading platform 601 and the outbound unloading platform 602 are located on opposite sides or opposite ends of the large facility 10. In one embodiment, the scale of the grid storage structure 603 of the large facility 12 is smaller than the scale of the grid storage structure 603 of the giant facility 10. In one embodiment, the grid storage structure 603 of the large facility 12 is a subdivided storage structure, which includes storage areas with different environments, such as a normal temperature area 603a, a refrigerated area 603b, and a frozen area 603c. In one embodiment, there is a cargo grid structure 604 and 605 near the inbound unloading platform 601 and the outbound unloading platform 602. In one embodiment, the cargo grid structures 604 and 605 of the large facility 12 are similar to Figure 5 The cargo grid structure 509 of the outbound unloading platform 502 of the mega facility 10 is shown.

[0125] The large facility 12 is similar to the mega facility 10 and includes two types of workstations that are connected and adjacent to the lower rail structure of the grid storage structure 603 to allow these workstations to be directly serviced by the machine processing equipment 208 of the grid storage structure 603. The large facility 12 includes one or more value-added service (VAS) workstations 606 and one or more supporting workstations 607. In one embodiment, the VAS workstations 606 are multi-functional workstations used for value-added services and other purposes, such as monitoring and processing customer returns. Therefore, these workstations will be referred to herein as VAS / return workstations 606, such as Figure 6As shown. In an embodiment where multi-function is not necessary, these workstations are operated as VAS workstations 606. The VAS / return workstation 606 and the matching workstation 607 include two pick-up openings, namely 606a and 606b and 607a and 607b, respectively, which are located on the work tables of the workstations 606 and 607, and human employees or machine workers at the workstations 606 and 607 can process storage containers from the grid storage structure 603 through the work tables. In one embodiment, at least one of the openings 606a or 606b of the VAS workstation 606 and at least one of the openings 607a or 607b of the supporting workstation 607 are served by the extended rails of the lower rail structure of the grid storage structure 603, so that the machine handling device 208 will travel through the VAS workstation 606 and the supporting workstation 607 to transport storage containers to or from at least one of the openings 606a or 606b and at least one of the openings 607a or 607b. In this embodiment, the other openings are served by the internal transporters of the individual VAS workstations 606 and supporting workstations 607, and the storage containers are placed on the openings by the machine handling device 208 of the grid storage structure 603 and then picked up after being transported to the pick-up location of the individual transporter service openings of the individual VAS workstations 606 and supporting workstations 607. The applicant disclosed the following details in U.S. Provisional Patent Application No. 62 / 846,295 filed on May 10, 2019, which is incorporated herein by reference in its entirety, that such workstations 606 and 607 are served by a combination of machine handling equipment 208, which travels on a track-type drive-through travel path and a conveyor-type travel path passing through one pickup port, and storage containers are transported on the path to another pickup port; the entire text of the application is incorporated herein by reference.

[0126] Figure 7 According to an embodiment of the present invention, it is displayed Figure 2A-2B and Figures 4A-4B The structure of the small facility 14 of the multi-node supply chain system 200 shown in FIG. The small facility 14 includes an inbound unloading platform 701, an outbound unloading platform 702, and an index storage configuration structure having a grid storage structure 703, which is connected to the Figure 6In one embodiment, the inbound unloading platform 701 and the outbound unloading platform 702 are located on opposite sides or ends of the small facility 14. In one embodiment, the scale of the small facility 14 is smaller than that of the large facility 12. In one embodiment, the grid storage structure 703 of the small facility 14 is a subdivided storage structure having storage areas with different environments, such as a normal temperature area 703a, a refrigerated area 703b, and a frozen area 703c. In one embodiment, the inbound unloading platform 701 is adjacent to the cargo grid structure 712, which is the same type as the cargo grid structure 712. Figure 5 The outbound unloading platform 502 of the mega facility 10 shown in the figure adopts the same type of cargo grid structure, which is also the same as Figure 6 The inbound unloading platform 601 and the outbound unloading platform 602 of the large facility 12 shown use the same type of cargo grid structure.

[0127] In one embodiment, the small facility 14 includes different types of workstations located at the connection and adjacent positions of the lower track structure of the grid storage structure 703, and can be directly served by its machine handling equipment 208. The workstations include at least one return workstation 704, at least one picking workstation 705, and at least one packing order workstation 706. The first multi-picking stage of the order preparation process will be carried out at the picking workstation 705, where Figure 4A The multi-compartment storage (MCS) container 224b shown containing the product will be received by the grid storage structure 703 of the index storage structure of the small facility 14 if it is previously introduced into the grid storage structure 703 of the index storage structure of the small facility, or according to Figure 2A-2B The facility management subsystem of the illustrated small facility 14 may decide, for example, based on determining that the product in the arriving MCS container 224b is the last remaining product required to fulfill a customer order, to bypass storage by directly arriving at the inbound unloading platform 701 from the MCS container 224b, which otherwise could be fulfilled by other products already located in the small facility 14. Each order-taking station 705 is also supplied with a picked order (PO) container, which, in one embodiment, is stored in a grid storage structure of an index storage structure of the small facility 14 and is retrieved from the grid storage structure and retrieved through the index storage structure (e.g., through the index storage structure). Figure 8 The type of grid storage structure 703 shown in the figure is an extended track from the grid lower track structure) of the machine processing equipment 208, which is transported to the multi-order processing stage. In one embodiment, the type of picking workstation 705 and packing order workstation 706 is similar to Figure 6The VAS / return workstation 606 and / or supporting workstation 607 of the illustrated large facility 12 are identical. In one embodiment, the picking workstation 705 includes two pick-up openings 705a and 705b, which are located on the workbench of the picking order workstation 705, and the storage containers from the grid storage structure 703 are processed by human employees or machine workers at the picking workstation 705. In one embodiment, the packing order workstation 706 includes a single pick-up opening 706a, which is located on the workbench of the packing order workstation 706, and the storage containers from the grid storage structure 703 are processed by human employees or machine workers at the packing order workstation 706.

[0128] In one embodiment, the small facility 14 includes one or more outbound transporters that transport from the order packaging workstation 706 to the outbound unloading platform 702, rather than the outbound unloading platform 702 of the small facility 14 served by the machine handling equipment 208 on the cargo grid structure. In one embodiment, a shared outbound transporter 709 runs to all outbound unloading platforms 702 and includes an upper outbound transporter 709a, which is set at a higher position above the matching lower outbound transporter 709b. Individual groups of loading and unloading transporters 710a-710d run between the shared outbound transporter 709 and each outbound unloading platform 702. In the group, two upper loading and unloading transporters 710a and 710c are connected to the upper outbound transporter 709a upwardly, and two lower loading and unloading transporters 710b and 710d are connected below the upper loading and unloading transporters 710a and 710c, so that Figure 7 The two upper loading and unloading transporters 710a and 710c are not visible, but Fig.19C It can be seen that two upper loading and unloading conveyors 710a and 710c are connected upwardly to the lower outbound conveyor 709b.

[0129] In one embodiment, one or more return conveyors are also included to move the storage containers moving upstream from the outbound unloading platform 702 in the upstream direction, that is, the opposite direction of the downstream direction, wherein the storage containers moving downstream are transported by the outbound conveyor 709. In one embodiment, the shared inbound conveyor 711 is fed from each group of unloading conveyors 710a-710d, and operates on the outbound conveyor 709 on the side of the outbound unloading platform 702 facing the grid storage structure 703, and similarly includes an upper return conveyor 711a and a lower return conveyor 711b below. At each outbound unloading platform 702, the upper return conveyor 711a is connected to the upper loading and unloading conveyors 710a and 710c, and the lower return conveyor 711b is connected to the lower loading and unloading conveyors 710b and 710d. The upper return conveyor 711a terminates at the vertical lift 711c of the return elevator 711, and the lower return conveyor 711b continues from the return elevator 711 and runs along the adjacent side of the grid storage structure 703 where the return workstation 704, the picking workstation 705 and the packing order workstation 706 are located, that is, the side where the return workstation 704, the picking workstation 705 and the packing order workstation 706 are located. This return conveyor 711 is then connected to the infeed conveyor 708 and then connected to the starting end of the outbound conveyor 709, and the infeed conveyor 708 similarly passes through the return workstation 704, the order picking workstation 705 and the packing order workstation 706, for example, between the workstations 704, 705 and 706 and between the respective sides of the grid storage structure 703. In various embodiments, different workstations are located at different positions on different sides of the grid storage structure 703 and are configured with different output and return transporters to serve the downstream flow of storage containers from the workstations 704, 705 and 706 to the outbound unloading platform 702, as well as the upstream flow of storage containers from the outbound unloading platform 702 to part or all of the various workstations 704, 705 and 706.

[0130] Figure 8 According to one embodiment of the present invention, a three-dimensional grid storage structure 800 is shown, which is configured to fully or partially define Figure 2A-2B and Figures 4A-4B The three-dimensional configuration structure of the index storage location of the multi-node supply chain system 200 is shown. Figure 8As shown, the three-dimensional grid storage structure 800 includes: a grid upper track structure 801, which is located above the higher level of the grid lower track structure 802; and a grid lower track structure 802, which is consistent with and aligned with the grid upper track structure 801 and is located at a lower level close to the ground. Between these aligned grid upper track structures 801 and lower track structures 802, there is a three-dimensional configuration structure of rack storage locations, each of which can store individual storage containers 224. The storage locations are arranged according to vertical columns 803, wherein storage locations of equal square areas are aligned with each other. Each such vertical column 803 is adjacent to a vertical upright axis 804, and any rack and storage container 224 does not have the said vertical upright axis 804 for the machine processing equipment 208 to pass through and travel vertically, so that the machine processing equipment 208 can access the storage location of the adjacent storage column from this open and vertical upright axis 804. The robot handling equipment 208 cluster is configured to: move horizontally back and forth on track structures 801 and 802 in two dimensions; and move vertically back and forth between track structures 801 and 802 via an open and vertical vertical axis 804.

[0131] Each track structure 801 and 802 includes: a set of X-direction tracks on a separate horizontal plane that run in the X direction, and a set of Y-direction tracks on the same horizontal plane that run in the Y direction and intersect perpendicularly with the X-direction tracks. The intersecting tracks define a horizontal reference grid of the storage system, wherein each horizontal grid crossbar is defined between two adjacent X-direction tracks, and each vertical grid straight column is defined between two adjacent Y-direction tracks. Each intersection point between any horizontal grid straight column and any horizontal grid crossbar represents the position of an individual vertical column 803 or an individual vertical axis 804. In other words, an individual vertical column 803 or an individual vertical axis 804 is located at a Cartesian coordinate point of the corresponding grid, which is located in a corresponding area between two X-direction tracks and two Y-direction tracks. Each such area between the four tracks in any track structure is referred to herein as an individual "point" of the track structure. The three-dimensional address of each storage location in the grid storage structure 800 is completed by the predetermined vertical height of the individual storage column where the predetermined storage location is located. That is, the three-dimensional address of each storage location is determined by the horizontal grid column, horizontal grid cross column, and vertical column height of the storage location in the three-dimensional grid storage structure 800. Thus, the grid storage structure 800 defines an indexed three-dimensional configuration of storage locations, each of which can be found by a separate Cartesian address of the grid storage structure 800. In one embodiment, extension rails and other grid structures are coupled to the grid storage structure 800 to access and service other areas (e.g., workstations, loading docks, etc. of the facility) to facilitate the transport of storage containers 224 between the grid storage structure 800 and such other areas, as well as within such other areas.

[0132] In various embodiments, in addition to Figure 5-7 With the use of the particular types of grid storage structures 800 and machine handling equipment 208 shown in the mega facility 10, large facility 12, and small facility 14, other types of indexed storage configuration structures and coordinated machine handling equipment can be used in a similar manner to receive, store, and retrieve standardized storage containers 224 of predetermined size and configuration at each facility in which they are used. As described herein, with respect to the grid storage structure 800 and the corresponding machine handling equipment 208, the predetermined size of the standardized storage container 224 refers to the size and area configured to be mounted above the upper platform of the machine handling equipment 208, and does not exceed the area and limitations of each rack storage location in the grid storage structure 800. The configuration of the storage container 224 refers to the appropriate features above it for engaging the telescopic arm of the machine handling equipment 208, which is operable to grab the storage container 224 from the storage location onto the robotic carrier 208 and push the storage container 224 away from the machine handling equipment 208 to enter the storage location. Where other types of storage configuration structures and machine processing devices are used, the predetermined size and configuration of the standardized storage container 224 are defined by the specific details of the structure / environment of the storage configuration structure and the cooperating machine processing devices operating therein.

[0133] In one embodiment, each facility includes both ambient storage areas at room temperature and one or more environmentally controlled storage areas, including one or more low-temperature storage areas, such as a refrigerated area below ambient temperature and a frozen area at even lower temperatures, suitable for environmentally sensitive inventory. In one embodiment, each of these environmentally different storage areas contains a separate portion of the facility's entire indexed storage configuration structure, such as a separate grid storage structure in each of these environmentally different storage areas to define a corresponding subset of storage locations of the entire configuration structure. In another embodiment, the environmentally different storage areas are environmentally isolated areas that share a single storage structure, as disclosed below, for the embodiments shown herein. In other embodiments, only a subset of the facility has multiple environmentally different storage areas where environmental conditions may vary. For example, Figures 4A-4B All facilities in the larger upper layer of the multi-node supply chain system 200 shown, such as the giant facility 10 and the large facility 12, each include multiple storage areas with different environments, while only the small facility 14 and a portion of the nano facility 16 in the lower layer include environmentally controlled storage areas, and other facilities in these lower layers can selectively be used only for normal temperature storage.

[0134] Figures 9A-9B According to one embodiment of the present invention, a flowchart of a computerized implementation method is shown, wherein the method is used to manage Figure 2A-2B , Figures 4A-4B and Figure 510 and the introduction of inventory items from the inbound unloading platform 501 to the multi-node supply chain system 200. The flowchart includes management steps for receiving the delivered supply goods 401a and the introduction of new inventory in the container into the index storage structure of the mega facility 10. When a transport vehicle such as a truck or other transport vehicle with palletized supply goods arrives (step 901a) at the inbound unloading platform 501 of the mega facility 10, in step 902a, the palletized boxes or pallets of the supply goods 401a are unloaded from the transport vehicle. In step 903, the palletized boxes are de-palletized and transferred to the inbound conveyor 505, regardless of whether the feed conveyor directly places it on the inbound conveyor 505 or feeds the inbound conveyor 505 via the feed conveyor 504. In one embodiment, bulk supply 401a arrives at the inbound unloading platform 501 of the mega facility 10 in step 901b, and in step 902b, the bulk boxes from the transport vehicle are unloaded from the transport vehicle onto the inbound transporter 505. In step 904, the inbound transporter 505 transports the individual boxes to the inbound workstation 506. In step 905, i.e., arriving at the inbound workstation 506, or approaching the inbound workstation 506 on the inbound transporter 505, the boxes from the supply are each provided with a Case_ID, which can be detected or input into the facility management subsystem 204, such as by using an automated scanner or a manual scanner to scan a code, such as a license plate number (LPN) barcode on the box with the Case_ID code. At the same time, the empty single compartment storage (SCS) container 224a passes through one of the machine handling devices 208, from Figure 5 The grid storage structure 507 is shown transported to the storage port 506a of the incoming workstation 506 to receive new product inventory placed therein from the scanned supply bins.

[0135] Moreover, in Fig. 9AIn step 905, the facility management subsystem 204 forwards the scanned Case_ID and Bin_ID of the empty SCS container 224a to the central computing system 201. The central computing system 201 queries the Case_ID in the cargo details table 318 to find out the Shipment_ID of the cargo to which the box belongs, and finds the Vendor_ID of the receiving supplier of the cargo from the supply cargo table 317 based on the identifier. In an embodiment where the multi-compartment storage container (MCS) 224b is stored in the same storage container table 308 with the SCS storage container 224a, the central computing system 201 uses the received Bin_ID to query the storage container table 308 for the single compartment ID of the empty SCS container 224a. The central computing system 201 uses this information in step 906 to update the supplier inventory table 304 for the identified supplier by adding a record in the information containing: the received Bin_ID and / or identified Compartment_ID of the received empty SCS container 224a; the Product_ID of the product type and quantity in the scanned box found from the cargo details table 318 using the scanned Case_ID; and the Facility_ID received from the facility management subsystem 204. Thus, the system automatically updates the supplier inventory table 304 to add the product contents of the box to the inventory table and identify the SCS container 224a that holds those products, as well as the facility where the SCS container 224a is located.

[0136] In one embodiment, before updating the supplier inventory list table 304, an environmental check may be performed to evaluate whether the environmental tag of the SCS container 224a matches the predetermined environmental data associated with the Product_ID, that is, to confirm that the product types in the supply that must be placed in the refrigerated area or the frozen area are only placed in SCS containers compatible with the refrigerated area or the frozen area. In the case of a good environmental match, the facility management subsystem 204 will command, through the robot worker at the introduction workstation 506, to start the automatic transfer of the product from the box to the SCS container 224a, or command the human employee at the introduction workstation 506 to perform the manual transfer, such as by transmitting audio or visual instructions to the human employee through a human-machine interface (HMI) installed at the introduction workstation 506 or worn by the human employee, such as a head-mounted display. If the environmental match between the new inventory product type and the SCS container 224a is poor, the facility management subsystem 204 will: command the machine processing equipment 208 to take out a different SCS container 224a from the grid storage structure 507, whose environmental tag matches the environmental data of the relevant Product_ID; and transport the empty environmentally compatible SCS container 224a to the storage port 506a of the introduction workstation 506, and at the same time command the machine processing equipment 208 that transported the original environmentally incompatible SCS container 224a to leave the storage port 506a.

[0137] In another embodiment, if an empty SCS container 224a is stored outside the machine service grid storage structure 507, the system notifies the environmentally incompatible human employee of the poor environmental match and transmits audio or visual instructions directly to the human employee through the human-machine interface to set the incompatible SCS container 224a aside and retrieve a different SCS container 224a of the correct environmental type that matches the associated product. In contrast to performing an environmental compatibility check on previously acquired empty SCS containers 224a, in one embodiment, the facility management subsystem 204 is configured to command automatic or human selection or retrieval of an environmentally compatible SCS container 224a on demand, wherein only after a box from a supply of goods is scanned and the environmental data of the associated product is retrieved from the central database 203, will the facility management subsystem 204 command automatic retrieval, or human selection and retrieval of an on-site SCS container 224a that is empty and environmentally compatible be performed. In this embodiment, the facility management subsystem 204 queries the on-site container table 322 for empty SCS containers 224s with appropriate environmental labels, and then instructs the machine processing equipment 208 to take out the found empty compatible SCS container 224a from the grid storage structure 507 and transport it to the storage port 506a of the introduction workstation 506.

[0138] In addition to the environmental compatibility check between the product type transferred from the box in which the goods are supplied and the SCS container to which the product type is transferred, in one embodiment, the facility management subsystem 204 also performs a processing compatibility check between the two. In this embodiment, when the central computing system 201 queries the goods details table 318 from the facility management subsystem 204 for the receipt of the Case_ID and Bin_ID, it uses the Product_ID returned from the query result to query the supplier product table 303 and confirm the processing data of the relevant product type to obtain any processing code or flag that represents the condition that the product type can only be placed in a specific compatible storage container. If such container-related processing data is found, the central computing system 201 will send the environmental data together with the container-related processing data back to the facility management subsystem 204, and the facility management subsystem 204 will perform a processing compatibility check in the same manner as the environmental compatibility check. One example of container-related processing data is an allergy code or flag, of which there are multiple categories, such as: potato-free, tree nut-free, gluten-free, shellfish-free, dairy-free, etc., indicating that the product can only be placed in a storage container that has been designated as allergy-safe of the same type, as indicated by a matching flag or code stored in the processing data of the storage container's container information table 326. In one embodiment, this processing compatibility check is performed along with the environmental compatibility check whenever a storage container is selected for placement of a product, and this is true during the processing of all products, orders, and storage containers disclosed herein.

[0139] In addition to updating the vendor's inventory record, step 906 also includes the central computing system 201 using the Product_ID from the goods detail record to look up the corresponding product record in the vendor product table 303. The central computing system 201 forwards the Vendor_ID, a copy of the product record, and the retrieved product quantity to the facility management subsystem 204, which then transmits all of this data to the mobile data storage device 226 of the SCS container 224a located at the incoming workstation 506, such as through the local wireless network 206 of the mega facility 10, in step 907, thereby writing the content table 327 and product information table 328 of the SCS container. Where environmental and / or processing compatibility checks are performed in advance to ensure that the correct compatible SCS container is selected, the central computing system 201 forwards the entire product record from the supplier product table 303 to the facility management subsystem 204 in a single communication in response to receipt of the Case_ID, thereby providing the facility management subsystem 204 with all the data required to complete the environmental and processing compatibility checks for appropriate container selection, and then writing the data to the mobile data storage device 226 of the selected SCS container 224a.

[0140] Other information written to the mobile data storage device 226 of the SCS container 224a in step 907 includes updates to fields in the container information table 326, such as destination data and time data fields, which govern whether the SCS container 224a is to be shipped to another facility, and whether there is a specific time frame or urgency under which such shipping must be carried out. In one embodiment, the destination data is defined based on specific supplier details previously stored in the central database 203, such as the destination specified by the supplier during the provision of the goods order to the manufacturer, and the destination data is stored in the supply goods table 317 or the supply goods details table 318. In one embodiment, the destination data written to the mobile data storage device 226 of the SCS container 224a is evaluated in real time by the computerized supply chain management system of the supplier inventory level of the ordered product at each facility 10, 12 and 14 in the multi-node supply chain system 200, such as from a query result of the supplier inventory list table 304; or based on the pending customer orders in the customer order table 315, which are awaiting the arrival of the product; or based on the predicted customer demand based on the historical order fulfillment records stored in the customer order table 315, or the predicted customer demand based on the individual historical order archives stored elsewhere in the central database 203. In one embodiment, the time data regarding the urgency of the product to be transported through the network to the destination is based on the priority status or target delivery date of the pending customer orders for the product, such as identified from the shipping preferences in the customer order table 315; or based on the nature of the product itself, such as the urgent transportation of consumables with a short expiration date, such as meat, dairy products, etc., or other products with a similarly short shelf life, in which case the supplier product table 303 will include a time data field in which the product with a short expiration date is marked.

[0141] In step 908, whether performed after, during, or before steps 905-907, a human or machine operator at the intake station 506 places the product from the scanned supply case into the empty SCS container 224a through the placement port 506a of the intake station 506. In step 909, a determination is made as to whether more of the same product can be placed in the same SCS container 224a, such as by a human or machine confirming additional remaining space in the SCS container and by scanning another arriving or approaching supply case at the intake station 506 to determine that the other case also contains the same product type from the same receiving supplier, in the same manner as disclosed above using the scanned Case_ID. If there is still space in the SCS container 224a and the same product is available in the next supply shipment, steps 905-908 are repeated. If the result of the reconfirmation of the container capacity or supply is negative, the SCS container 224a is ready to leave the intake station 506 for transport to another destination in the mega facility 10.

[0142] like Fig. 9A As shown, for each single SKU case of off-pallet or bulk shipments, each of the specific products in the single SKU case will be stored in one of the standardized SCS containers 224a, which is compatible with the index configuration structure of the mega facility 10. The above example assumes that the entire contents of a case will be placed in a single SCS container, so the product quantity read from the Case_ID record in the Shipment Details table 318 is used as the quantity added to the supplier inventory table 304 and written to the record in the SCS container's content table 327. In one embodiment, the process defers the assignment of quantity values ​​to the supplier inventory table 304 and the SCS container's load content table 327 until the actual location of the product has actually been changed from the case to the SCS container, reaching the maximum capacity of the storage container, and only then can the actual quantity placed in the SCS container be recorded in the supplier inventory table 304 and the SCS container's load content table 327.

[0143] The SCS containers 224a containing the products are typically stored in the grid storage structure 507 by one of the machine handling devices 208 unless there is a specific reason for an alternate route for the SCS containers, for example, due to an urgent downstream demand for the particular product elsewhere in the multi-node supply chain system 200, in conjunction with a transport vehicle at the outbound unloading dock 502 of the mega facility 10 or an expected imminent arrival of a transport vehicle that is expected to travel downstream, or toward the intended destination of the particular product. In such a case, one or more SCS containers 224a containing the product may be cross-docked for urgent transport to another facility where a waiting transport vehicle 215a or an expected transport vehicle 215a is located. Thus, in step 913, when the SCS container 224a is loaded with product and is ready to be shipped out, for example, by transporting the SCS container 224a to the import workstation 506, and the SCS container 224a is still transported by the same machine processing equipment 208 above, the facility management subsystem 204 will command the machine processing equipment 208 to travel to the correct destination in the mega facility 10 based on the same destination, time, processing and customization data written to the mobile data storage device 226 of the SCS container 224a in the previous step. In one example, if the destination and time data indicate that the contents of the SCS container 224a are urgently needed by another facility, the machine handling equipment 208 will directly transport the SCS container to the outbound unloading platform 502 in step 916, for example, by traveling horizontally through the lower track structure of the grid storage structure 507, from the introduction workstation 506 to the container loading grid structure 509, that is, the machine handling equipment 208 loads the SCS container 224a onto the outbound unloading platform 502 where the waiting transport vehicle 215a or the expected transport vehicle 215a is located.

[0144] On the other hand, if the destination data and the time data do not indicate an urgent need to cross-dock the SCS container 224a in step 913, then in step 914, the facility management subsystem 204 will instruct the machine handling device 208 to deposit the SCS container 224a into an available storage location in the grid storage structure 507. The area of ​​such available storage location will be confirmed, that is, the environmental status indicator recorded for the storage environment in the global storage location table 310 or the facility storage table 320a matches the environmental flag in the container information table 326 of the SCS container 224a, which is based on a previous cross-check of the environmental data of the supplier product table 303 against the environmental flag of the SCS container, indicating that the storage location is compatible with the product type environment placed in the SCS container 224a. After the machine processing device 208 confirms that the SCS storage container 224a is placed in the available storage location, then in step 915, the facility management subsystem 204 records the Bin_ID of the SCS container 224a in the facility storage table 320a of the local facility database 207 and / or records the Location_ID of the storage location in the field container table 322 of the local facility database 207. Moreover, in step 915, the facility management subsystem 204 forwards the same Location_ID and Bin_ID to the central computing system 201 to record the Location_ID in the global storage container table 308 corresponding to the Bin_ID of the stored SCS container 224a, and if there is a duplicate Location_ID field in the supplier inventory table 304, it can also be selectively recorded in the supplier inventory table 304. The database software that responds to the query results of the supplier inventory list table 304 for the product type introduced in the SCS container will use the data of this record to be configured to query the Bin_ID of each SCS container where the found product type is located, the Facility_ID of the facility where the found SCS container is located, and, if the SCS container is stored in the index storage structure of the facility, query the specific storage location of the SCS container in the facility where it is located.

[0145] Regardless of the form of each incoming supply 401a and 401b, such as full cases or mixed cases; palletized or bulk, etc., the mega-facility 10 will perform the same process to transfer the products from the incoming supply cases at the induction station 506 to the SCS containers 224a according to the single SKU principle of only one product type per SCS container. Some or all of the incoming supply 401a and 401b will be sorted for delivery, where each new inventory product is placed in an SCS container 224a and introduced into the index configuration structure of the mega-facility 10. In other cases, if the relative size of the cases and SCS containers allows for delivery at the case level rather than the sort level, the predetermined product type is transferred to the SCS container 224a in one or more full cases rather than dividing the new inventory products. In any case, during the process of loading new inventory products into the SCS containers 224a from the incoming supply 401a, the memory of the mobile data storage device 226 of each SCS container 224a is loaded with data written into its content table 327, such as the Product_ID and quantity of the specific product type placed in the SCS container 224a, and the corresponding record of the product type is written into the product information table 328 of the SCS container from the supplier product table 303. Although in one embodiment, the transportation process and the data of the SCS container 224a are performed at the introduction workstation 506, that is, the place where the loaded SCS container 224a is subsequently introduced into the grid storage structure 507 by the machine handling equipment 208, or the SCS container 224a is directly transported to the loading grid structure 509 of the outbound unloading platform 502, in another embodiment, the transportation process can be performed upstream of the introduction workstation 506, such as at the depalletization workstation 503, or a separate transportation workstation (not shown) between the depalletization workstation 503 and the introduction workstation 506.

[0146] Although the aforementioned example of full-case shipment uses Case_ID to query the goods in the central database 203, and thereby find out the supplier to which the goods inventory belongs, as well as the product types and quantities in the full case; other embodiments of storing mixed case-packed supply goods adopt scanning Case_ID starting from the LPN barcode, and then scanning or entering the supplier or global Product_ID from each product in the mixed case, for example, according to each product placed in the SCS container 224a, scanning the universal product code (UPC) or stock keeping unit (SKU) code above, and updating the content table 327 of the SCS container 224a and the inventory list table 304 in the central database 203 according to the Product_ID of each product scanned and the quantity of each scanned Product_ID, and at the same time, writing the corresponding record from the supplier product table 303 in the central database 203 into the SCS container product information table 328. In any case, the contents of the SCS container 224a are accounted for on-board, and the supplier product catalog 305 in the central database 203 is updated to include the contents and Bin_ID stored in the SCS container, so that in order to obtain any cataloged product shipped from the supply goods in the manner described above, a subsequent query to the supplier inventory list table 304 in the central database 203 will report the Bin_ID of the SCS container 224a storing the product, the quantity of product in each of the SCS containers 224a, the facility in which the SCS container 224a is located, and, if stored in the index storage structure of the mega facility 10, the storage location of the SCS container 224a.

[0147] Product_ID, owner Vendor_ID, product quantity, some or all product information, destination data and time data, collectively referred to herein as "container data", are loaded into the mobile data storage device 226 of the SCS container 224a from the supply goods. This same upload process can be applied to the mega facility 10, as well as any other facility where the newly delivered product inventory will enter the entire supply chain system 200, or anywhere that products are transferred from one storage container to another storage container (whether SCS container or other container), as described below. In one embodiment, container data is uploaded to the storage container regardless of whether the loaded storage container is loaded according to a single SKU or multiple SKUs. In other words, although the SCS container 224a only carries a single product type owned by a single supplier and has only a single record in its content table 327 and a single record in its product information table 328, in one embodiment, the content table 327 and product information table 328 on the mobile data storage device 226 can selectively load multiple records, each record having a data set describing a respective product type stored in the storage container, such as multiple products in the same supplier product catalog 305 having the same final destination or relay point in the multi-node supply chain system 200, as recorded in the destination data field of the container information table 326. Examples of such multi-SKU loading operations are disclosed below at other points in the supply chain workflow, involving placing multiple products of different types in the same storage container.

[0148] like Figure 4A As shown, in addition to or as an alternative to supply goods 401a packaged in conventional product packaging, such as cartons or shipping bags, supply goods may include pre-loaded container goods 401b, whether palletized or bulk, in which products are delivered from manufacturers using smart storage containers 224a and 224b that are compatible with the indexed storage configuration structure of the mega facility 10, large facility 12, and small facility 14, respectively. In one embodiment, the manufacturer arrives at the mega facility 10 in a pre-loaded state. The storage containers SCS containers 224a each contain only products of the corresponding type, which can be directly introduced into the indexed storage configuration structure of the mega facility 10 without the additional step of transferring the products from the storage container in which they arrived to other SCS containers.

[0149] The pre-loaded storage container from the manufacturer may have its own mobile data storage device 226, which is pre-loaded with the aforementioned container data by the manufacturer before being transported to the mega facility 10 of the multi-node supply chain system 200. In one embodiment, the facility management subsystem 204 receives the pre-loaded container data from the delivered pre-loaded storage container of the mega facility 10, for example, after placing the storage container on the inbound transporter 505, it is transported to the import workstation 506, such as Fig. 9A As disclosed in step 911 of . In step 912, after receiving the pre-loaded container data, the system will place the pre-loaded storage container on the machine handling device 208 of the placement port 506a of the import workstation 506, and then follow the step 913 process disclosed above to process the pre-loaded storage container. Therefore, in step 913, the destination and time data of the pre-loaded container data are used to select between the import and cross-transfer operations, wherein the import is to introduce the container into the storage location of the large-scale facility 10 index configuration structure in the appropriate environmental area of ​​the large-scale facility 10 predetermined by the pre-loaded container data, and the cross-transfer operation involves instructing the machine handling device 208 where the pre-loaded storage container was previously placed to directly transport the pre-loaded storage container to the cargo grid structure 509 of the outbound unloading platform 502, so as to urgently transport the pre-loaded storage container to another facility. Thus, whether the container data is retrieved from the central database 203 via the facility management subsystem 204 during the process of new inventory being loaded from an incoming pallet or bulk supply shipment for loading onto the mobile data storage device 226 of a previously empty SCS container 224a, or is retrieved from the mobile data storage device 226 of pre-filled containerized supply shipments 401b, the container data is still used to make automated decisions regarding the correct distribution schedule, such as storage introduction and cross-docking of incoming product within the mega facility 10.

[0150] When storage containers 224a and 224b enter any of the facilities 10, 12, 14 and 16, the wireless communication units 225 on the storage containers 224a and 224b will establish wireless communication with the local area network 206 of the facility and report their Bin_ID to the facility management subsystem 204. The facility management subsystem 204 will in turn communicate with the central computing system 201 to store the Facility_ID of the facility in individual records of the storage container table 308 in the central database 203. If the Facility_ID field is repeated in the inventory table 304, the Facility_ID can also be optionally stored in the inventory table 304 of any supplier that has products in the storage container. In either case, the Facility_ID will be stored in association with the Bin_ID or Compartment_ID stored in the supplier's inventory list table 304 where the products are stored in the storage containers 224a and 224b, so that a query in the supplier's product catalog 305 for a specific product stored in the storage containers 224a and 224b will report the Facility_ID of the facility where the storage containers 224a and 224b are located, as well as the Facility_ID of the product's current location.

[0151] In one embodiment, each storage container 224a and 224b and order container 224c and 224d includes an internal positioning device 229, which is integrated into or connected to a wireless communication unit 225, such as a shared computer readable memory, a wireless transceiver 227 and a local computer processor 228, which is used for the aforementioned wireless communication and data exchange. The internal positioning system 211 of each mega facility 10, large facility 12 and small facility 14 includes components of the internal positioning devices 229 on the storage containers 224a and 224b and the order containers 224c and 224d, respectively, to determine the current coordinate position of any storage container in the mega facility 10, large facility 12 and small facility 14. In one embodiment, sonar buoys are used to find storage containers inside each mega facility 10, large facility 12 and small facility 14. In one embodiment, these facility positioning elements are reference devices, or initiator devices and reference devices. Although these devices use a combination of high-speed radio frequency (RF) signals and low-speed acoustic signals to achieve optimal positioning accuracy, in one embodiment, other internal positioning techniques are used to determine the location of storage containers in facilities 10, 12, 14 and 16 of the multi-node supply chain system 200.

[0152] Through the combination of the wireless communication unit 225 and the internal positioning device 229, each storage container can not only identify itself to the facility management system 204 of the facility where the storage container arrives, but also identify its current location in the facility, thereby tracking the inventory loaded in the storage container in an optimal and high-resolution manner. In one embodiment, the internal positioning device 229 and the wireless communication unit 225 on the storage container are programmed to continuously or periodically determine the location of the storage container and transmit the calculated location to the facility management subsystem 204. The facility management subsystem 204 will in turn update the storage location in the central database 203 of the central computing system 201, which is configured as a cloud computing platform, or in one embodiment, the updated information is only stored locally at the facility until the central computing system 401 queries the Bin_ID.

[0153] In one embodiment, the internal positioning device 229 and the wireless communication unit 225 are configured to default to a reduced functionality sleep mode, or to periodically wake up to re-determine the location of the storage container and report the location to the facility management subsystem 204 or the central computing system 201, such as waking up at time intervals or in response to a status query signal issued by the facility's local area network 206. In one embodiment, the internal positioning device 229 further includes one or more motion sensors, such as accelerometers and gyroscopes, which are operable to detect movement of the storage container in three-dimensional space and wake the storage container's electronics from the above sleep mode. Doing so can reduce the power consumption of the storage container's electronics in a stationary position, such as reducing the power consumption of the storage location of the facility's indexed storage configuration structure, maximize the life of the storage container's data storage, communication and internal positioning components' built-in battery-based power supply, and ensure that the storage container's location is continuously or periodically reported when the storage container is known to pass through the facility, whether by human personnel, machine handling equipment 208 or transporters.

[0154] Figures 10A-10B According to an embodiment of the present invention, a side elevation view and a top view of large transport vehicles 215a and 215b are shown, respectively, wherein the transport vehicles are used to transport goods in Figures 4A-4B The multi-node supply chain system 200 shown transports storage containers between the giant facility 10, the large facility 12, and the small facility 14, and the collaborative loading grid structure 509 at the unloading platform of the facilities 10, 12, and 14, through Figure 5 The machine handling equipment 208 on the loading grid structure 509 is shown to assist in the automated loading and unloading of large transport vehicles 215a and 215b. Fig. 10C According to an embodiment of the present invention, it is displayed Figures 10A-10B The rear elevation view of the medium and large transport vehicles 215a and 215b. Figure 4AAs shown, the SCS container 224a containing the product from the mega facility 10 is loaded onto a large transport vehicle 215a such as a semi-trailer truck for downstream transport to one of the mega facilities 12. Figures 10A-10C As shown, the trailers 1003 or other cargo spaces of transport vehicles 215a and 215b have configurations of indexed storage locations, each of which is sized and configured to be compatible with the same storage containers 224a and 224b of the indexed storage configurations of the mega facility 10, large facility 12, and small facility 14. The terms "facility configuration" and "vehicle configuration" are used herein to distinguish between storage configurations in static facilities 10, 12, 14, 16 and storage configurations of transport vehicles 215a and 215b. Figures 10A-10C As shown, the type of vehicle type configuration structure of the large transport vehicles 215a and 215b is similar to that used in the mega facility mega facility 10, large facility 12 and small facility 14. Figure 8 The robot shown moving back and forth between the grid storage structures 800 is different.

[0155] In one embodiment, Figures 11A-11C One or more container transporters 222a shown in FIG. Figures 10A-10C In the trailer 1003 of the large transport vehicles 215a and 215b shown in FIG. Figures 11A-11C According to an embodiment of the present invention, a partial rear front view, a side view and a top view of a container transporter 222a are shown, respectively, and the container transporter is used for indexing storage of storage containers 224a and 224b and order containers 224c in large transport vehicles 215a and 215b. Each container transporter 222a includes a pair of closed-loop belts or chains 1004a and 1004b, each of which is in a pair of C-channel guide rails 1001a and 1001b, extending longitudinally of the trailer 1003 in a transversely spaced manner; and each container transporter 222a is transported around a pair of pulleys or sprockets 1005, and the positions of the pulleys or sprockets 1005 are respectively Fig. 10BThe front end 1003a and rear end 1003b of the trailer 1003 are shown with guide rails spaced longitudinally from each other. A pulley or sprocket 1005 is rotatably operable to drive belts or chains 1004a and 1004b around the continuous closed loop path represented by the guide rails 1001a and 1001b, respectively, the guide rails 1001a and 1001b having horizontally continuous upper and lower portions, the ends of which are joined together by an arcuate connecting portion, the arcuate connecting portion each having as an axial center the rotation axis of one of the pulley or sprocket 1005. A series of conveyor platforms 1002 are suspended between the two belts or chains 1004a and 1004b at regular intervals along the belts or chains 1004a and 1004b for placing individual single compartment storage (SCS) containers 224a on each conveyor platform 1002. The size and shape of the footprint of each transporter platform 1002 is approximately equal to the size and shape of the SCS container 224a, so the transporter platform 1002 is configured to receive the SCS container 224a in a 1:1 ratio. Therefore, the driving operation between the pair of belts or chains 1004a and 1004b will longitudinally move the transporter platform 1002 in opposite directions relative to the trailer 1003 in the upper and lower halves of the closed loop path of the belts or chains 1004a and 1004b. Although this embodiment is directed to the specific transportation of SCS containers 224a between the mega facility 10 and the large facility 12, the same transport vehicle and transporter type are inherently compatible with multi-compartment storage (MCS) containers 224b and picked order (PO) containers 224c, which have the same footprint, size and configuration, and thus similarly configured transport vehicles 215b will be used to transport other storage containers between other facilities described below.

[0156] To load each container transporter 222a of the transport vehicles 215a and 215b, the SCS container 224a is placed on an empty transporter platform 1002, and the transporter platform 1002 should be located at the loading and unloading position P at the rear end of the container transporter 222a, and the container transporter 222a is located in the loading door of the trailer 1003, and the loading door is located at the rear end 1003b of the trailer 1003. In one embodiment, the container transporter 222a is gradually advanced, each time by a small distance equal to the uniform distance between any two adjacent transporter platforms 1002 along the closed loop path of the belt or chain 1004a and 1004b of the container transporter 222a. Thus, after an SCS container 224a is placed on a transport platform 1002 at the loading position, such gradual movement of the container transporter 222a will not only move the just loaded transport platform 1002 forward toward the opposite front end 1003b of the trailer 1003, but will also bring the next transport platform 1002 back to the loading position P next to the door so that another SCS container 224a can be placed on the next transport platform 1002. Starting from a completely empty container transporter 222a, the process of loading a transport platform 1002 and progressively advancing the container transporter 222a will be repeated again and again until the container transporter 222a is completely loaded, i.e., all transport platforms 1002 are occupied by corresponding SCS containers 224a, or the container transporter 222a is loaded to a partial capacity specified by the total number of SCS containers 224a used for the current transport operation. Figure 2A-2B The vehicle management subsystem 216 shown is connected to the drive of each transporter and monitors the driving operation of each drive, and the storage of the unique Location_ID of each transporter platform 1002 in the vehicle storage table 324a of the local vehicle database 220 allows the vehicle management subsystem 216 to determine and track which transporter platform 1002 is located at the loading and unloading location at any time. This determination and tracking, as well as the record of the Bin_ID corresponding to the Location_ID in the on-board container table 325 of the local vehicle database 220, allows tracking of the SCS containers 224a loaded to and unloaded from any predetermined transporter platform 1002 during any loading and unloading operation, and tracking the location of each loaded SCS container 224a in the vehicle type configuration structure at any time.

[0157] In one embodiment, the SCS container 224a is relatively small compared to the width and height of the trailer 1003, so multiple container transporters 222a can be installed on the trailer 1003 in an orderly configuration. According to one embodiment of the present invention, Figures 10A-10C Three side-by-side rows of container transporters 222a are shown, each row being four container transporters high. According to one embodiment of the present invention, Figures 10A-10BAlso shown is a cargo grid structure 509 of the mega facility 10. The cargo grid structure 509 is a multi-level structure that includes a plurality of levels 509a, 509b, 509c, and 509d, the number of which is at least equal to the number of container transporters 222a in each row of the vehicle-type configuration structure of transport vehicles 215a and 215b. According to one embodiment of the present invention, Figures 10A-10B A four-layer cargo grid structure 509 is shown, which is compatible with four container transporters 222a in each row of the vehicle-type configuration structure of the transport vehicles 215a and 215b. Each level 509a, 509b, 509c and 509d of the cargo grid structure 509 includes the same type of two-dimensional grid track structure, which is deployed in the upper and lower levels of the grid storage structure 507 of the index storage structure of the mega facility 10, so that each level 509a, 509b, 509c and 509d of the cargo grid structure 509 includes multiple sets of intersecting X-direction tracks and Y-direction tracks, and either set of the two sets of tracks, such as the X-direction tracks, is parallel to the longitudinal direction L shared by the trailer 1003 of the transport vehicles 215a and 215b and the container transporters 222a installed in the trailer 1003. Each level 509a, 509b, 509c and 509d of the cargo grid structure 509 corresponds to a respective level in the corresponding vehicle-type configuration structure of the container transporter 222a and has its respective grid track structure located a short distance below the respective level of the container transporter 222a. The width of each container transporter 222a is approximately equal to the width of each point of the cargo grid structure 509, and each container transporter 222a is aligned with a respective row of points that are constrained between respective pairs of X-direction tracks of the cargo grid structure 509 at its respective level.

[0158] Therefore, the machine handling equipment 208 on any predetermined level of the cargo grid structure 509 will move in the X direction to the terminal point at the unloading platform end of any row of the level, thereby arriving at a position adjacent to the transport platform 1002 where the loading and unloading position of the corresponding container transporter 222a is located, thereby allowing the SCS container 224a to be loaded onto the transport platform 1002 of the container transporter 222a or unloaded from the transport platform 1002 of the container transporter 222a by docking the machine handling equipment 208 at the terminal point of the corresponding row of the cargo grid structure 509. In one embodiment, the machine handling equipment 208 operating on the cargo grid structure 509 is a member of the same cluster of machine handling equipment 208 of the grid storage structure 507 of the index storage configuration structure serving the mega facility 10, and can therefore be operated according to wireless commands through the facility management subsystem 204 to perform fully automatic loading and unloading on the transport vehicle 215a of the outbound unloading platform 502 of the mega facility 10.

[0159] Figures 10A-10B This automated loading operation is shown wherein a first machine handling device 208a on the uppermost level 509a of the cargo grid structure 509 is shown parked at the end point of the first row of the uppermost level 509a. The diagram shows the first machine handling device 208a transporting an SCS container 224a for loading onto an empty transporter platform 1002a at a loading and unloading location of a first container transporter of a transport vehicle 215a, such as the uppermost container transporter of the leftmost row of container transporters 222a. Furthermore, the diagram shows a second machine handling device 208b on a second upper level 509b of the cargo grid structure 509 after unloading its respective SCS container 224a onto a loading and unloading location of a second container transporter of a transport vehicle 215a, the previously empty, now loaded transporter platform 1002, and then parked at the end point of the second row of the second upper level 509b without any SCS container 224a being transported; for example, the second container transporter may be the second upper level container transporter of the middle row of container transporters 222a. Furthermore, the diagram shows that the third machine handling device 208c on the second lower level 509c of the cargo grid structure 509 stops at the end point of the third row of the second lower level 509c in the process of unloading its individual SCS container 224a to the loading and unloading position of the third container transporter of the transport vehicle 215a, which is originally an empty transporter platform 1002; for example, the third container transporter may be the second lower level container transporter of the rightmost row of container transporters 222a. Furthermore, the diagram shows that the fourth machine handling device 208d on the lowermost level 509d of the cargo grid structure 509 approaches the end point of the third row of the lowermost level 509d and transports its individual SCS container 224a to be unloaded to the empty transporter platform 1002 at the loading and unloading position of the fourth container transporter of the transport vehicle 215a; for example, the fourth container transporter may be the lowermost level container transporter of the rightmost row of container transporters 222a.

[0160] In summary, any machine handling device 208 parked at the terminal point of any row of any level of the cargo-carrying grid structure 509 can access the loading and unloading position of the individual container transporter 222a of the transport vehicle 215a to load the SCS container 224a to the loading and unloading position. Similarly, any machine handling device 208 parked at the terminal point of any row of any level of the cargo-carrying grid structure 509 can access the loading and unloading position of the individual container transporter 222a of the transport vehicle 215a to unload the SCS container 224a from any container transporter platform 1002 driven to the loading and unloading position P of the container transporter 222a, and transport the SCS container 224a to the connected grid storage structure 507 of the mega facility 10, and store the SCS container 224a in the SCS container 224a at any available storage position in the grid storage structure 507, or transport the SCS container 224a to any workstation connected to the grid storage structure 507.

[0161] At the intersection of the X-direction track and the Y-direction track, the tracks of each level 509a, 509b, 509c, and 509d are interconnected in a vertical manner by rail tooth vertical frame members 510 of a similar type to the rail tooth vertical frame members 510 used in the grid storage structures of the mega facility 10, large facility 12, and small facility 14, but of a shorter height. These shorter vertical frame members 510 include rail teeth that are disposed perpendicularly to the majority of the height of the vertical frame members 510 except at the narrow lower ends of the vertical frame members 510. Thus, the four vertical frame members 510 at the four corners of any combination of alignment points in the levels 509a through 509d define an axis and serve as a vertical track for the machine handling equipment 208 to ascend and descend through the axis to travel between any two levels of the cargo grid structure 509.

[0162] In the same manner as in the cargo grid structure, the raising and lowering is accomplished by engaging the track teeth on these vertical frame members 510 with the toothed pinions of the machine handling equipment 208 when the machine handling equipment 208 is in the shaft travel mode, in which mode the track travel transmission wheels of the machine handling equipment 208 are retracted inwardly relative to the toothed pinions to minimize the footprint of the machine handling equipment 208 through the shaft, to a size smaller than the grid point size of the cargo grid structure 509, thereby traveling through the shaft. In one embodiment, the toothless, narrowed lower neck of the vertical frame member 510 provides spacing for the track travel transmission wheels of the machine handling equipment 208 to travel on the rails, thereby allowing the track travel transmission wheels to travel on the grid track structure when extending outwardly beyond the pinions in the track travel mode in which the handling equipment footprint is larger. In one embodiment, the cargo grid structure 509 uses such track tooth frame members at all track intersections of the cargo grid structure 509, so that Fig. 10A As shown, the machine handling equipment 208 is allowed to rise and fall at all points of the cargo grid structure 509, except for the terminal points where transport vehicles 215a are loaded and unloaded, which lack frame members on their X-direction tracks, which extend and hang from the rest of the cargo grid structure 509.

[0163] In one embodiment, each machine handling device 208 includes an upper platform on which the SCS container 224a is loaded, and a rotatable turntable with a telescopic arm, through which the SCS container 224a is pulled onto the upper platform of the machine handling device 208 and pushed out of the upper platform of the machine handling device 208; each container transporter 1002 of each container transporter 222a on the transport vehicle 215a may have a central longitudinal slot 1002b, such as Figures 11A-11CDuring the process of loading and unloading storage containers onto and from the transport platform 1002 at the loading and unloading position P of the container transporter 222a, the central longitudinal slot 1002b accommodates the extension and retraction of the turntable arm of the robot handling device 208.

[0164] The container transporters 222a of the transport vehicle 215a form a dynamic configuration structure of storage locations, referred to herein as a "dynamic storage configuration structure," in which each transporter platform 1002 represents an individual storage location with a unique Location_ID, which is stored in the vehicle storage table 324a of the local vehicle database 220 and the global storage location table 310 of the central database 203, respectively. However, by operating the container transporter 222a, each storage location in the vehicle configuration structure can be moved to a different location within the trailer 1003 of each transport vehicle 215a. This is different from the static index storage configuration structure of the facilities 10, 12, and 14 of the multi-node supply chain system 200, in which each storage location in the grid storage structure is in a fixed static position, rather than a dynamically movable position. Using the dynamic storage configuration structure in the transport vehicle 215a, the storage container can be conveniently loaded from the rear door of the trailer 1003. In other embodiments, a different type of indexed storage configuration structure is used in the transport vehicle 215a, such as a scaled-down version of the machine-served grid storage structure used in the mega facility 10, large facility 12, and small facility 14, or another human or machine-served storage configuration structure having separate storage locations, such as racks, cubicles, etc., sized specifically to accommodate the standardized size and shape of the storage container 224a, wherein each storage location can be indexed with an individual Location_ID in the local vehicle database 220 and the central database 203. In one embodiment, a dynamic storage location such as the transporter platform 1002 is loaded directly onto the rear end 1003b of the trailer 1003, and an extended track from the grid storage structure in any mega facility 10, large facility 12, and small facility 14 leads to a loading dock for directly loading and unloading cargo from the transport vehicle in an automated manner by the same fleet of machine handling equipment 208 serving the grid storage structure, thereby Figures 10A-10B Whether these extended rails are part of a shared loading grid structure 509 serving multiple docking stations, or distinct rail systems leading to different docking stations at a predetermined facility, storage containers can be prevented from being transferred to other automated handling equipment or personnel during the process.

[0165] In one embodiment, since the transport vehicle 215a is equipped with multiple container transporters 222a, the entire index storage configuration structure of the transport vehicle 215a defined according to this configuration is subdivided into isolated and environmentally different storage areas, characterized by different environmental control parameters, similar to the different areas of the grid storage structure 507 subdivided in the mega facility 10. Therefore, in one embodiment, each transport vehicle 215a includes any one or more of a normal temperature area, a refrigerated area, and a frozen area, each of which includes more than one container transporter 222a. For example, one or more thermal barriers are erected between two adjacent rows of container transporters 222a to insulate the normal temperature area and the temperature control area on one side of the thermal barrier, such as the refrigerated area and the frozen area on the opposite side, or to isolate the temperature control area, such as the refrigerated area, from another environmentally different temperature control area, such as the frozen area. In one embodiment, the thermal barrier is a vertically erected barrier configured to horizontally isolate multiple levels of transporter rows, thereby facilitating personnel to obtain the container transporters 222a in the isolated area to service or repair the transporter devices in each area. In one embodiment, each zone includes individual transporter rows having aisle space on one side for performing the service or repair. In one embodiment, the thermal barrier is a horizontal barrier configured to isolate two vertically adjacent container transporters 222a in any multi-level row, or to isolate entire levels from each other in multiple multi-level transporter rows.

[0166] exist Figures 17A-17C In the detailed description of FIG. 2 , with reference to the trailer 1701 of the transport vehicle 215c between the small facility 14 and the nano facility 16, it is disclosed that the trailer 1003 of the transport vehicle 215a can be selectively subdivided into separate environmentally distinct storage areas. The transport vehicle 215c is a smaller version of the transport vehicle 215a. Since the trailer 1003 may be divided into environmentally distinct storage areas, the environmental status field in each record of the vehicle storage table 324a need not be the same as all other records of the vehicle storage table 324a because a single transport vehicle 215a includes multiple environmentally distinct storage areas. In one embodiment, if each transport vehicle 215a includes only a single environmental area, such as only a normal temperature storage area, a refrigerated storage area, or a frozen storage area, the vehicle storage table 324a omits the environmental status indicator because the environmental data in the vehicle information table 323 of the local vehicle database 220 will represent the common environmental status shared by all storage locations on the transport vehicle 215a.

[0167] like Figure 2AAs shown in the detailed description of FIG. 1 , each vehicle management subsystem 216 includes a local wireless network 221 connected to the wireless communication units 225 of the storage containers 224a, 224b, 224c, and 224d. Thus, the vehicle management subsystem 216 of the transport vehicle 215a can communicate with the wireless communication units 225 of the SCS containers 224a loaded onto the transport vehicle 215a from the mega facility 10 to receive the Bin_IDs of these SCS containers 224a from its mobile data storage device 226 and start recording the transfer process of the identified SCS containers 224a from the mega facility 10 to the transport vehicle 215a in the central database 203, for example by transmitting the Vehicle_ID of the transport vehicle 215a and the Bin_ID received from the loaded SCS container 224a to the central computing system 201. Therefore, the central database 203 is automatically updated to change the current location of the SCS container 224a in the storage container table 308, and optionally change the current location of the SCS container 224a in the inventory list table 304 of the supplier whose product is located in the SCS container 224a, from the Facility_ID of the mega-facility 10 that the SCS container 224a is about to leave, to the Vehicle_ID of the transport vehicle 215a to which the SCS container 224a is about to travel. In one embodiment, the automatic recording is initiated by the facility management subsystem 204, rather than by the vehicle management subsystem 216, to record the transfer of the SCS container 224a from the mega-facility 10 to the transport vehicle 215a, for example, by reading and recording Figure 5 The Vehicle_ID of the transport vehicle 215a of the outbound unloading platform 502 of the mega facility 10 shown in the figure, and the Bin_ID of the SCS container 224a loaded on the transport vehicle 215a are read and recorded, and the central database 203 is updated accordingly. In another embodiment, the transfer record of the SCS container 224a from the mega facility 10 to the transport vehicle 215a is a two-part process, which is performed by the facility management subsystem 204 and the vehicle management subsystem 216 in a collaborative manner, and the facility management subsystem 204 will report to the central computing system 201 that the SCS container 224a leaves the mega facility 10 to clear the Facility_ID of the mega facility 10 from the SCS container 224a in the storage container table 308 and the inventory list table 304, and the vehicle management subsystem 216 will report that it receives the SCS container 224a to replace the just cleared Facility_ID with its Vehicle_ID.

[0168] In one embodiment, at each point in the supply chain workflow where a storage container is transferred from a facility downstream toward a departure vehicle, there is one or more storage containers transferred in the opposite upstream direction. For example, SCS storage container 224a from mega facility 10 and filled with product is transferred upstream. Figure 6 As shown in the inbound unloading platform 601 of the large facility 12, when unloading from the arriving large-scale transport vehicle 215a, the empty SCS containers 224a from the large facility 12 will be loaded onto the same large-scale transport vehicle 215a and returned to the same large facility 10 where the SCS containers 224a that just arrived and filled with products were before arriving for transportation. Therefore, when returning to the large facility 10, the transport vehicle 215a can put down a group of empty SCS containers 224a from the large facility 12 and take the next group of SCS containers 224a filled with products and transport them back to the large facility 12, or transport them to the next destination that the transport vehicle 215a plans to go to. Although in this embodiment, the empty SCS container 224a returns upstream from the large facility 12 that the transport vehicle 215a previously traveled to the same mega facility 10 from which the empty SCS container 224a has been removed, in another embodiment, the transport vehicle 215a departs from this large facility 12 and travels to a different upstream mega facility 10, rather than the mega facility 10 from which the transport vehicle 215a departed. That is, the transport vehicle 215a delivers the empty SCS container from the mega facility 12 to a different mega facility 10 than the mega facility 10 from which the same transport vehicle 215a delivered the SCS container 224a containing the product to the mega facility 12. Therefore, the transfer of the SCS container 224a between any facility and the transport vehicle involves the exchange of the SCS container, i.e., the storage container moving upstream, such as the empty SCS container, and the storage container moving downstream, such as the SCS container containing the product, are exchanged with each other.

[0169] Figures 12A-12B According to one embodiment of the present invention, a flowchart of a computerized method for managing a mega facility 10 and a transport vehicle 215a ( Figure 5-6 In the method disclosed herein, a single compartment storage (SCS) container 224a containing products and moving downstream from a mega facility 10 is loaded onto an outbound transport vehicle 215a, the destination of which is the mega facility 12, and an empty SCS container 224a moving upstream and arriving at an outbound unloading platform 502 of the mega facility 10 is simultaneously unloaded from the same transport vehicle 215a, as shown. Figures 4A-4BAs shown. Considering a situation, the transport vehicle 215a may have arrived at the mega facility 10 from the same large facility 12, and the mega facility 12 is where the transport vehicle 215a will leave again after loading and unloading. In step 1202, after the transport vehicle 215a arrives at the outbound unloading platform 502 of the mega facility 10 (step 1201), the vehicle management subsystem 216 of the transport vehicle 215a transmits an arrival signal to the central computing system 201 and the facility management subsystem 204 of the mega facility 10; the signal contains the Vehicle_ID of the transport vehicle 215a, and the mega facility 10 is the location where the transport vehicle 215a arrives. In step 1203, the central computing system 201 identifies the Facility_ID of the next destination scheduled for the transport vehicle 215a, and forwards the Facility_ID to the facility management subsystem 204. In one embodiment, the transport vehicle 215a transmits the Facility_ID of the next destination to the facility management subsystem 204 in the form of an arrival signal. In other words, after the transport vehicle 215a arrives, it first updates the destination Facility_ID in its vehicle information table 323 from the Facility_ID of the facility that the transport vehicle 215a has just arrived to the Facility_ID of the next facility that the transport vehicle 215a is about to go to. The facility management subsystem 204 uses the Facility_ID of the next destination to query the field container table 322 of its local facility database 207 to find the SCS container 224a containing the product based on the use of the stored destination Facility_ID relative to the Bin_ID of the field storage container, and the SCS container 224a should be transported to the next destination of the transport vehicle 215a. This query process is configured to return the Facility_ID that matches the next destination of the transport vehicle 215a, and also return the Facility_ID of the facility further downstream on the known travel path, where the next destination of the transport vehicle 215a is a known relay point from the current mega-facility 10. The SCS containers 224a containing products returned by this query are referred to as downstream-moving SCS containers (i.e., DSCS containers) because the purpose of these SCS containers 224a is to travel to another facility in the downstream direction of the multi-node supply chain system 200. In step 1204, if the number of DSCS containers returned by the query exceeds the container capacity of the transport vehicle 215a, the resulting list of DSCS containers is filtered based on the time data of those DSCS containers to retain the DSCS containers with higher priority and remove the DSCS containers with lower priority.

[0170] In step 1205, the facility management subsystem 204 of the mega facility 10 instructs the machine processing device 208 to take out one of the DSCS containers 224a from the grid storage structure 507 and transport the taken out DSCS container 224a to the outbound unloading platform 502, i.e., the location where the transport vehicle 215a arrives. After confirming that the DSCS container 224a is taken out from the original storage location of the grid storage structure 507, the system clears the Bin_ID of the DSCS container 224a from the facility storage table 320a of the mega facility 10 and the storage location table 310 of the central database 203, and the Location_ID of the storage location removed from the DSCS container 224a is cleared from the storage container table 308 of the central database 203 and the field container table 322 of the mega facility 10. Furthermore, after confirming that the machine handling device 208 has taken out the DSCS container 224a from its storage location, the Equipment_ID of the machine handling device 208 is updated to the Location_ID of the storage location of the DSCS container 224a in the storage container table 308 of the central database 203 and the field container table 322 of the mega facility 10, thereby allowing the DSCS container to be associated with the Location_ID that can be tracked in real time. Since the facility management subsystem 204 can detect the location of the machine handling device 208 in the individual facilities 10, 12, and 14 at any time, after the specific machine handling device 208 has taken out the storage container, the system will record the Equipment_ID of the specific machine handling device 208 as the location of the storage container, thereby allowing the storage container to be tracked in the individual facilities 10, 12, and 14 at any time.

[0171] The facility management subsystem 204 transmits the environmental tag from the removed DSCS container 224a to the vehicle management subsystem 216 of the arrived transport vehicle 215a. In step 1206, the transport vehicle 215a uses the environmental tag to find Figures 10A-10BThe unloaded transport platform 1002 of one of the container transporters 222a shown in the figure, the environmental status indicator of the container transporter 222a in the vehicle storage table 324a meets the environmental mark, thereby confirming that the individual storage location represented by the unloaded container transport platform 1002 is located in the environmental zone of the transport vehicle 215a, and the transport vehicle 215a is compatible with the environmental requirements of the product in the removed DSCS container 224a. If the unplaced transporter platform 1002 is not at the position, the vehicle management subsystem 216 activates the container transporter 222a to reposition the unplaced transporter platform 1002 to the rear loading and unloading position P of the container transporter 222a, and transmits the handover designation signal to the facility management subsystem 204; the facility management subsystem 204 identifies a specific terminal point on the cargo grid structure 509 from the handover designation signal, and the machine handling device 208 should receive the command to connect with the identified container transporter 222a, and accordingly command the machine handling device 208 to move to the terminal point. In one example, the transport vehicle 215a includes a configuration structure of twelve container transporters 222a, and the cargo grid structure 509 accordingly has a configuration structure at twelve corresponding terminal points of each outbound unloading platform 502, and the handover designation signal includes one of twelve different unique indicators, and the twelve unique indicators correspond to individual members of each such configuration structure.

[0172] In step 1207, when or after the acquired DSCS container 224a arrives at a specific terminal point of the cargo grid structure 509 through the machine handling equipment 208, the wireless communication unit 225 of the acquired DSCS container 224a wirelessly connects to the local area network 221 of the transport vehicle 215a and transmits its Bin_ID to the vehicle management subsystem 216 of the transport vehicle 215a through the local area network 221; the vehicle management subsystem 216 records the Bin_ID against the Location_ID of the unloaded transport platform 1002, and the unloaded transport platform 1002 advances to the loading and unloading position of the container transporter 222a. In one embodiment, the connection and communication between the DSCS container 224a and the vehicle management subsystem 216 is initiated in response to a command from the facility management subsystem 204 to disconnect from the local area network 206 of the mega facility 10 and connect to the local area network 221 of the transport vehicle 215a. In one embodiment, this instruction is initiated in response to the machine handling device 208 confirming arrival at a specific terminal point of the cargo grid structure 509, and the machine handling device 208 is commanded by the facility management subsystem 204. After confirming arrival at the specific terminal point of the cargo grid structure 509, the machine handling device 208 will then place or transfer the acquired DSCS container 224a to the empty transporter platform 1002 present on the selected container transporter 222a in step 1208 according to the command of the facility management subsystem 204.

[0173] In step 1209, after the machine processing equipment 208 confirms that the obtained DSCS container 224a is placed on the transport platform 1002 appearing at the loading and unloading position P, the facility management subsystem 204 will remove the Bin_ID of the DSCS container 224a from the on-site container table 322 of the giant facility 10, reduce the number of placed storage containers in the facility information table 319 (if this data is recorded in the facility information table 319), and update its record to reflect the transfer of the DSCS container 224a from the giant facility 10 to the transport vehicle 215a. In this step, in one embodiment, the facility management subsystem 204 also sends a container leaving signal with the Bin_ID of the DSCS container 224a to the central computing system 201, and the central computing system 201 responds by removing the Facility_ID of the mega-facility 10 from the record of the DSCS container 224a in the storage container table 308, and if there is duplicate data in the supplier inventory table 304, it also deletes the corresponding record from the supplier inventory table 304. In step 1201, the vehicle management subsystem 216 similarly updates its record by adding the Bin_ID of the DSCS container 224a to the onboard container table 325 of the transport vehicle 215a, and increasing the number of placed storage containers, i.e., the number of storage containers that are not empty and contain products, in the vehicle information table 323 (if there is such data in the vehicle information table 323), thereby reflecting the transfer of the DSCS container 224a from the mega-facility to the transport vehicle 215a. The vehicle management subsystem 216 also records the Bin_ID of the DSCS container 224a corresponding to the Location_ID of the transporter platform 1002, and / or records the Location_ID of the storage location corresponding to the Bin_ID in the on-vehicle container table 325 of the local vehicle database 220; the DSCS container 224a is located on the transporter platform 1002. In this step, in one embodiment, the vehicle management subsystem 216 also sends the container reception signal and the Bin_ID of the DSCS container 224a just received on the transport vehicle 215a to the central computing system 201, and the central computing system 201 responds by adding the Vehicle_ID of the transport vehicle 215a to the DSCS container 224a in the storage container table 308, and if there is duplicate data in the supplier inventory table 304, the corresponding record is also added to the supplier inventory table 304. The container received signal also includes Location_ID, which is used to record the Bin_ID of the DSCS container 224a stored in the global storage container table 308, and if there is duplicate data in the supplier inventory list table 304, it will also be included.

[0174] Steps 1204 to 1210 are related to DSCS container 224a, that is, Figure 4AThe supply chain workflow direction of the multi-node supply chain system 200 shown is an SCS container containing products, and its destination is the large facility 12 located in the downstream direction of the large facility 10. Since the machine handling equipment 208 that dropped off the DSCS container 224a does not carry any storage containers at present, it is necessary to check whether there are any storage containers in the upstream direction, such as empty SCS containers, on the transport vehicle 215a, so that the SCS containers can be unloaded or transported by the available machine handling equipment 208; the purpose of the transport vehicle 215a is to go to the large facility 10 for unloading. In this example, such storage containers moving upstream are called "single compartment storage (USCS) containers moving upstream", although as described below, the storage containers moving upstream do not need to be limited to SCS containers. Therefore, in step 1211, the vehicle management subsystem 216 will query the USCS container whose destination Facility_ID matches the Facility_ID of the large facility 10 arrived by the transport vehicle 215a in its on-board container table 325 to confirm whether there are any such USCS containers on the transport vehicle 215a. If the query result is yes, there are one or more USCS containers destined for the mega facility 10, then steps 1214 to 1218 disclosed below will be performed. If the query result is no, indicating that there is no such USCS container on the transport vehicle 215a, the process directly jumps to step 1212, that is, the vehicle management subsystem 216 notifies the facility management subsystem 204 that there is no USCS container on the vehicle, and the facility management subsystem 204 will respond to confirm whether there are other DSCS containers 224a left in the list generated in step 1204. If there are other DSCS containers 224a, steps 1205-1210 are repeated to transport another such DSCS container 224a to the outbound unloading platform 502, and load the DSCS container 224a onto the transport vehicle 215a, as described above.

[0175] If there is no USCS container at the loading and unloading position of the container transporter 222a, and the query result in step 1211 indicates that there is a USCS container on the transport vehicle 215a, the vehicle management subsystem 216 will find a container transporter 222a with a USCS container in step 1214, and activate the container transporter 222a with the USCS container on it, and transport the transporter platform 1002 loaded with the USCS container to the loading and unloading position of the container transporter 222a. The vehicle management subsystem 216 will send another handover designation signal to the facility management subsystem 204 to identify a specific terminal point of the cargo grid structure 509, and the machine handling equipment 208 of the cargo grid structure 509 needs to receive the USCS container from the container transporter 222a where the USCS container is located. If the handover designation signal designates the same terminal point of the cargo grid structure 509, i.e., the location where the DSCS container was loaded before being loaded by the machine handling device 208 into the transport vehicle 215a, the machine handling device 208 will still stop at the same terminal point. If not, the facility management subsystem 204 will command the machine handling device 208 to be relocated to another terminal point of the cargo grid structure 509 according to the handover designation signal from the vehicle management subsystem 216. In one embodiment, when multiple container transporters 222a are identified to have USCS containers, the vehicle management subsystem 216 will be configured to give priority to any USCS container on the same container transporter 222a loaded with the DSCS container, and give priority to the USCS container on the transporter platform 1002 closest to the loading and unloading position of the container transporter 222a, so as to minimize the movement between the container transporter and the machine handling device, thereby achieving optimal loading and unloading efficiency.

[0176] In step 1215, the wireless communication unit 225 of the USCS container at least transmits its Bin_ID and environmental tag to the facility management subsystem 204 for such communication after receiving, for example, an instruction from the vehicle management subsystem 216 to disconnect from the local area network 221 (e.g., wireless network) of the transport vehicle 215a and connect to the local area network 206 (e.g., wireless network) of the mega-facility 10. Based on the received environmental tag, the facility management subsystem 204 queries the Location_ID of the available storage location of the grid storage structure 507 whose environmental status matches the environmental tag of the USCS container for its facility storage table 320a, thereby confirming that it is located in the correct environmental area of ​​the grid storage structure 507 of the USCS container.

[0177] Therefore, in step 1216, the facility management subsystem 204 will command the machine handling equipment 208 that has stopped at the correct terminal point next to the loading and unloading position of the USCS container to take out the USCS container from the transporter platform 1002 and transport the USCS container to an available environmentally suitable storage location in the correct environmental area of ​​the grid storage structure 507. After confirming that the machine handling equipment 208 has taken out the USCS container from the transporter platform 1002, the Equipment_ID of the machine handling equipment 208 will be updated to the Location_ID of the storage location of the USCS container in the storage container table 308 of the central database 203 and the field container table 322 of the mega facility 10, thereby allowing the USCS container to be associated with the Location_ID that can be tracked in real time. In step 1217, after confirming that the USCS container has been taken from the transport platform 1002 by the machine handling device 208, the vehicle management subsystem 216 will update its record by removing the Bin_ID of the USCS container from the onboard container table 325 of the transport vehicle 215a to reflect the transfer of the USCS container from the transport vehicle 215a to the mega facility 10, and if the USCS container is an empty storage container and there is such data in the vehicle information table 323, it will update its record by reducing the number of empty storage containers in the vehicle information table 323. In this step, in one embodiment, the vehicle management subsystem 216 also sends a container departure signal and the Bin_ID of the USCS container just unloaded from the transport vehicle 215a to the central computing system 201, and the central computing system 201 will respond by clearing the Vehicle_ID of the transport vehicle 215a from the USCS container record in the storage container table 308. In step 1218, the facility management subsystem 204 updates the record of the on-site container table 322 of the mega facility 10 by adding the Bin_ID of the USCS to reflect that the USCS container is transferred from the transport vehicle 215a to the mega facility 10, and in this example, the USCS container is an empty storage container, which can be reflected by increasing the number of empty containers in the facility information table 319 if there is such data in the facility information table 319. In this step, in one embodiment, the facility management subsystem 204 also sends a container reception signal and the Bin_ID of the USCS container just received from the mega facility 10 to the central computing system 201, and the central computing system 201 responds by adding the Facility_ID of the mega facility 10 to the USCS container record in the storage container table 308.

[0178] As commanded by step 1216, the machine processing device 208 will place the USCS container at a specific storage location in the grid storage structure 507 in step 1219. In step 1220, after confirming that the USCS storage container is placed at a specific storage location in the environmentally compatible zone of the grid storage structure 507, the facility management subsystem 204 will record the Bin_ID of the USCS container in the facility storage table 320a of the local facility database 207 against the Location_ID of the storage location, and / or record the Location_ID of the storage location in the field container table 322 of the local facility database 207. Moreover, in step 1220, the facility management subsystem 204 will forward the same Location_ID and Bin_ID to the central computing system 201 to correspond to the Bin_ID of the stored USCS container 224a, record the Location_ID in the global storage container table 308, and if there are duplicate fields in the supplier inventory table 304, record it in the supplier inventory table 304. The empty USCS containers currently stored in and locatable in the grid storage structure 507 are now candidate empty SCS containers for performing subsequent inventory introduction processes, such as Figures 9A-9B Detailed description as described in.

[0179] Therefore, steps 1205 to 1220 will collectively perform a single container exchange, exchanging the SCS container 224a on the outbound transport vehicle 215a, which is moving downstream and leaving the mega facility 10, with the SCS container 224a on the same outbound transport vehicle 215a, which is moving upstream and arriving at the mega facility 10. Next, in step 1212, it will be checked whether there are any additional DSCS containers 224a left in the list generated in step 1204. If there are any additional DSCS containers 224a, steps 1205 to 1211 will be repeated. If there are no additional DSCS containers 224a, then in step 1213, the same check performed in step 1211 is repeated to identify whether there are other USCS containers to be unloaded, and when the result of the determination is yes, steps 1214 to 1212 are repeated until the result of step 1213 is no, thereby confirming that all SCS containers moving upstream have been unloaded from the transport vehicle 215a, received by the mega facility 10, and introduced into its grid storage structure 507; and all SCS containers moving downstream have been loaded onto the transport vehicle 215a to continue to travel to the next large facility 12 to which the transport vehicle 215a is heading.

[0180] Figures 12A-12BThe method disclosed in the embodiment assumes that at step 1206, there is already at least one unloaded transport platform 1002 on the transport vehicle 215a so that the DSCS container 224a transported by the first machine handling device 208 arrives at the outbound unloading platform 502 and can be stored on the transport platform 1002; however, other embodiments may require that steps 1204 to 1220 be performed in advance by another unloaded machine handling device to unload the first USCS container from the fully loaded transport vehicle 215a, leaving no empty transport platform, and then any DSCS container can be loaded onto the transport vehicle 215a. In one embodiment, the loading and unloading processes of the different facilities are configured so that the container transporter 222a is not filled up, so that at least one transport platform 1002 will remain open during transportation to receive the first storage container on the transport vehicle 215a to be loaded to its next destination. To ensure that the transport platform 1002 on the transport vehicle 215a must remain open, step 1204 will ultimately use the effective maximum vehicle capacity, rather than the actual maximum vehicle capacity, where the effective vehicle capacity is the maximum vehicle capacity, i.e., the total number of transport platforms on the transport vehicle minus one. In this way, the maximum number of DSCS containers specified to be loaded onto the transport vehicle 215a in step 1204 will be one less than the actual container capacity of the transport vehicle 215a, so that after loading, there will still be one open transport platform on the transport vehicle 215a.

[0181] As mentioned above, Figures 4A-4B Each of the transport vehicles 215a, 215b, and 215c is shown equipped with: a global positioning system (GPS) device 219 that can track the movement and location of the transport vehicles 215a, 215b, and 215c; and a wide area communication device 218 that can transmit the current location of the transport vehicles 215a, 215b, and 215c to the central computing system 201. Therefore, querying the inventory list table 304 in the central database 203 to find the products currently stored in any storage container 224a and 224b on the transport vehicles 215a and 215b can report the current GPS location of the storage container 224a and 224b based on the GPS coordinates of the transport vehicles 215a and 215b carrying the storage containers 224a and 224b. Therefore, similarly, in the central database 203, the query order number is recorded in the FO container table 313, and as shown Figures 4A-4B As shown, any customer order of the FO container 224d currently traveling on the transport vehicle 215c will report the current GPS location of the FO container 224d based on the GPS coordinates of the transport vehicle 215c carrying the FO container 224d. Therefore, monitoring and tracking of the storage and order containers 224 can be achieved throughout the multi-node supply chain system 200.

[0182] Figures 13A-13B According to an embodiment of this invention, Figures 4A-4B , a flowchart showing a computerized method for managing a large facility 12 and a large facility 10 upstream of the large facility 10. Figure 6 The storage container 224a is exchanged between the transport vehicles 215a of the inbound unloading platform 601 of the large facility 12 shown. The large transport vehicle 215a loaded with the SCS container 224a travels from the mega facility 10 to the Figure 4A One of the large facilities 12 shown in FIG. A transport vehicle 215a from the large facility 10 arrives at the inbound unloading platform 601 of the large facility 12, wherein the DSCS containers from the large facility 10 are unloaded from the arriving transport vehicle 215a, and empty SCS containers destined for the large facility 10 and / or other storage containers moving upstream are loaded onto the same transport vehicle 215a, and Figures 12A-12B The loading and unloading process performed in the outbound unloading platform 502 of the mega facility 10 disclosed in the detailed description is opposite. Figures 10A-10CIf the container transporter 222a of the large transport vehicle 215a shown is nearly full of DSCS containers, it will be driven to move the transporter platform 1002 with containers next to it to the rear end position of the container transporter 222a in a progressive manner, and individual DSCS containers 224a will be extracted from the transporter platform 1002 by, for example, human employees or machine handling equipment 208; and in one embodiment, as part of the container exchange process, the human employees or machine handling equipment 208 that unload the DSCS containers 224a from the arriving inbound transport vehicle 215a are also responsible for placing the USCS containers on the inbound transport vehicle 215a. In this unloading process, the facility management subsystem 204 of the large facility 12 reads the Bin_ID and at least part of the data content of the content table 327 and the product information table 328 from the mobile data storage device 226 of the arrived DSCS container 224a, and then sends a container reception signal to the central database 203 according to the Facility_ID of the large facility 12 where the DSCS container 224a arrives, so as to update the location of each DSCS container 224a. After confirming that the machine handling equipment 208 has retrieved the DSCS container 224a from the arriving inbound transport vehicle 215a, the Location_ID of the storage location of the DSCS container 224a is updated in the storage container table 308 of the central database 203 and the field container table 322 of the large facility 12 with the Equipment_ID of the machine handling equipment 208, so that the DSCS container 224a is associated with the Location_ID that can be tracked in real time. The facility management subsystem 204 receives product information, including processing and custom data, through the local area network 206 of the large facility 12, such as a wireless network, which is used to determine the correct processing and distribution schedule of the DSCS container 224a arriving at the large facility 12, and to control the machine processing equipment 208 and / or other automatic processing devices of the grid storage structure 603, and / or instruct human workers accordingly. At the same time, in one embodiment, the information read from the mobile data storage device 226 of the DSCS container 224a includes the Product_ID and quantity of the product in the content table 327, indicating the quantity of product introduced into the large facility 12, for example, even if the communication with the central computing system 201 is interrupted, resulting in the suspension of access to the storage container content table 309 of the central database 203, so that the facility management subsystem 204 can automatically and accurately track the existing inventory. When normal communication with the central computing system 201 is possible, the transmission of the Facility_ID and Bin_ID of each arriving DSCS container 224a in the above-mentioned received signal is operable to update the central database 203 with respect to the inventory quantity of each catalogued product in the arriving DSCS container 224a at the large facility 12.

[0183] Figures 13A-13B The unloading process of the DSCS container 224a on the transport vehicle 215a arriving at the large facility 12 from the large facility 10 is disclosed, and at the same time, the process of loading the USCS container from the large facility 12 onto the same transport vehicle 215a for transportation to the large facility 10 is disclosed. In one embodiment, the transport vehicle 215a arrives at the same large facility 10. After the transport vehicle 215a arrives at the inbound unloading platform 601 of the large facility 12 (i.e., step 1301), in step 1302, Figure 2A-2B The vehicle management subsystem 216 of the transport vehicle 215a is shown transmitting an arrival signal including its Vehicle_ID to the central computing system 201 and the facility management subsystem 204 of the large facility 12, where the transport vehicle 215a arrives. Next, in step 1303, the central computing system 201 identifies the Facility_ID of the next destination scheduled for the transport vehicle 215a and forwards the Facility_ID to the facility management subsystem 204. In one embodiment, the Facility_ID is transmitted from the transport vehicle 215a itself to the facility management subsystem 204 of the large facility 12 via the arrival signal. The facility management subsystem 204 uses the Facility_ID of the next destination to query the field container table 322 of its local facility database 207 based on the Facility_ID of the destination associated with the Bin_ID of the field container, thereby finding the USCS container therein, which is scheduled to be transferred to the next destination of the transport vehicle 215a. This query may return the Facility_ID of the next destination of the transport vehicle 215a, and / or the Facility_ID of other facilities on the known route of the next destination (also known as a relay point) of the transport vehicle 215a. In step 1305, if the query returns a number of candidate USCS containers that exceeds the container capacity of the transport vehicle 215a, the list of identified USCS containers is filtered based on the time data stored for the identified USCS containers to retain USCS containers with higher priority and remove USCS containers with lower priority. In one embodiment, this step may calculate the effective vehicle capacity as the actual capacity minus one, thereby ensuring that the number of USCS containers specified to be loaded onto the transport vehicle 215a is the actual number of containers on the vehicle minus one, so that after loading, an open transport platform 1002 is left on the transport vehicle 215a, such as Figures 10A-10C shown.

[0184] If one or more USCS containers are identified in step 1303, then in step 1306, the facility management subsystem 204 of the large facility 12 will instruct the machine processing device 208 to retrieve one of the identified USCS containers from the grid storage structure 603 and transport the identified USCS container to the inbound unloading platform 601, i.e., the location where the transport vehicle 215a arrives. After confirming that the USCS container has been retrieved from the storage location in the grid storage structure 603, the Bin_ID of the USCS container will be cleared from the facility storage table 320a of the large facility 12 and the storage location table 310 of the central database 203, and the Location_ID of the storage location where the USCS container was retrieved will also be cleared from the storage container table 308 of the central database 203 and the field container table 322 of the large facility 12. Moreover, after confirming that the machine processing equipment 208 has taken out the USCS container from the grid storage structure 603, the Equipment_ID of the machine processing equipment 208 will be updated to the Location_ID of the storage location of the USCS container in the storage container table 308 of the central database 203 and the on-site container table 322 of the large facility 12, thereby allowing the USCS container to be associated with the Location_ID that can be tracked in real time.

[0185] The facility management subsystem 204 transmits the environmental tag of the USCS container to the vehicle management subsystem 216 that has arrived at the transport vehicle 215a, and the transport vehicle 215a uses the environmental tag to identify the unplaced platform transporter 1002 of one of the container transporters 222a in step 1307, and the environmental tag indicator of the container transporter 222a in the vehicle storage table 324a meets the environmental tag, thereby confirming that the individual storage location represented by the unplaced transporter platform 1002 is located in the environmental zone of the transport vehicle 215a, and the environmental zone is compatible with the environmental tag of the USCS container and, if the USCS container is not an empty container, is also compatible with any contents therein. If the unplaced transporter platform 1002 is not at the location, the vehicle management subsystem 216 activates one of the container transporters 222a of the transport vehicle 215a to relocate the unplaced transporter platform 1002 to Figures 11A-11C, and transmits the handover designation signal to the facility management subsystem 204 to command the machine handling device 208 to go to the correct terminal point of the cargo grid structure 604, which is the container transporter 222a corresponding to the transport vehicle 215a. In step 1308, if or once the taken USCS container arrives at the specific terminal point of the cargo grid structure 604, the wireless communication unit 225 of the USCS container will connect and transmit its Bin_ID to the vehicle management subsystem 216 to record the Location_ID of the transporter platform 1002 corresponding to the Bin_ID, such as Figures 12A-12B In step 1309, after confirming that the machine handling device 208 has arrived at the specific terminal point, the machine handling device 208 will place the obtained USCS container 224a on the empty transporter platform 1002 of the selected container transporter 222a according to the instruction of the facility management subsystem 204.

[0186] In step 1310, after confirming that the USCS container is placed on the transport platform 1002 at the loading and unloading position P, the facility management subsystem 216 will update its record by removing the Bin_ID of the USCS container from the on-site container table 322 of the large facility 12 to reflect the transfer of the USCS container from the large facility 12 to the transport vehicle 215a, and in an embodiment where the USCS container is an empty storage container 224a, if there is such data in the facility information table 319, it will update its record by reducing the number of empty storage containers in the facility information table 319. In this step, in an embodiment, the facility management subsystem 204 also sends a container departure signal and the Bin_ID of the USCS container just unloaded from the large facility 12 to the central computing system 201, and the central computing system 201 will respond by clearing the Facility_ID of the large facility 12 from the USCS container record in the storage container table 308. At the same time, in step 1311, the vehicle management subsystem 216 updates its record by adding the Bin_ID of the USCS to the onboard container table 325 of the transport vehicle 215a to reflect that the USCS container is transferred from the large facility 12 to the transport vehicle 215a, and in one embodiment, the USCS container is an empty storage container 224a, which can be reflected by increasing the number of empty containers in the vehicle information table 323 if there is such data in the vehicle information table 323. The vehicle management subsystem 216 also records that the Bin_ID of the USCS container 224a corresponds to the Location_ID of the transport platform 1002, and / or records that the Location_ID of the storage location corresponds to the Bin_ID of the USCS container 224a in the onboard container table 325 of the local vehicle database 220; the USCS container 224a is located on the transport platform 1002. In this step, in one embodiment, the vehicle management subsystem 216 also sends the container receiving signal and the Bin_ID of the USCS container that has just received the transport vehicle 215a to the central computing system 201, and the central computing system 201 responds by adding the Vehicle_ID of the transport vehicle 215a to the USCS container record in the storage container table 308 of the central database 203. The container receiving signal further includes the Location_ID, which is used to record and compare the Bin_ID of the USCS container stored in the global storage container table 308.

[0187] As described above, steps 1303 to 1311 process USCS containers, which are destined for the mega facility 10 upstream of the mega facility 12 relative to the supply chain workflow direction of the multi-node supply chain system 200. After the USCS container is transferred to the transport vehicle 215a, the next step 1312 is performed to transfer the arriving DSCS container 224a from the transport vehicle 215a to the mega facility 12. In this example, at least one DSCS container 224a is unloaded from the transport vehicle 215a because the travel of the transport vehicle 215a to the mega facility 12 is defined by the demand for transporting storage containers downstream from the mega facility 10, and the transport vehicle 215a will not be scheduled to go to the mega facility 12 alone with an empty vehicle to pick up a storage container, such as a USCS container to be returned upstream to the mega facility 10. In one embodiment, an additional decision step is performed between steps 1311 and 1312 to first query the on-board container table 325 of the local vehicle database 220 of the transport vehicle 215a to confirm whether there are any DSCS containers on the vehicle to be unloaded to the large facility 12.

[0188] If there is no DSCS container at the loading and unloading location, the vehicle management subsystem 216 will find a container transporter 222a with a DSCS container in step 1312, and activate the container transporter 222a with the DSCS container on it, and transport the transporter platform 1002 loaded with the USCS container to the loading and unloading location of the container transporter 222a. At the same time, the vehicle management subsystem 216 will send another handover designation signal to the facility management subsystem 204 to identify a specific terminal point of the cargo grid structure 604, where the machine handling device 208 located in the cargo grid structure 604 needs to receive the DSCS container 224a from the container transporter 222a, and the DSCS container 224a is located on the container transporter 222a. If this handover designation signal specifies the same terminal point of the cargo grid structure 604, that is, the location where the USCS container is loaded before being loaded by the machine handling device 208 to the transport vehicle 215a, the machine handling device 208 will still stop at the same terminal point. If not, the facility management subsystem 204 will command the machine handling equipment 208 to be relocated to another terminal point of the cargo grid structure 604 according to the handover designation signal from the vehicle management subsystem 216. In one embodiment, when multiple container transporters 222a are identified with DSCS containers 224a, the vehicle management subsystem 216 will be configured to give priority to any DSCS container 224a on the same container transporter 222a that has just loaded a USCS container, and give priority to the DSCS container 224a on the transporter platform 1002 closest to the loading and unloading position of the container transporter 222a, so as to minimize the movement between the transporter and the machine handling equipment, thereby achieving optimal loading and unloading efficiency.

[0189] In step 1313, the wireless communication unit 225 of the DSCS container 224a at least transmits its Bin_ID, environmental tag, and part of its container data, including at least its processing data, custom data, destination data, and time data, to the facility management subsystem 204 for such communication after receiving, for example, an instruction from the vehicle management subsystem 216 to disconnect from the local area network 221 (e.g., wireless network) of the transport vehicle 215a and connect to the local area network 206 (e.g., wireless network) of the large facility 12. Based on the received environmental tag, the facility management subsystem 204 queries the Location_ID of the available storage location of the grid storage structure 603 whose environmental status matches the environmental tag of the DSCS container 224a for its facility storage table 320a, thereby confirming that it is located in the correct environmental area of ​​the grid storage structure 603 of the product content of the DSCS container 224a.

[0190] In step 1314, the facility management subsystem 204 instructs the machine handling device 208, which has stopped at the correct terminal point, to obtain the DSCS container 224a from the transport platform 1002 at the loading and unloading position; the terminal point is located next to the loading and unloading position of the container transporter 222a. In step 1315, after confirming that the DSCS container 224a is taken out from the transport platform 1002 by the machine handling device 208, the vehicle management subsystem 216 updates its record by removing the Bin_ID of the DSCS container 224a from the on-board container table 325 of the transport vehicle 215a to reflect the transfer of the DSCS container 224a from the transport vehicle 215a to the large facility 12, and if there is such data in the vehicle information table 323, it will update its record by reducing the number of storage containers in the vehicle information table 323. In this step, in one embodiment, the vehicle management subsystem 216 also sends the container departure signal and the Bin_ID of the DSCS container 224a just unloaded from the transport vehicle 215a to the central computing system 201, and the central computing system 201 responds by clearing the Vehicle_ID of the transport vehicle 215a from the DSCS container record in the storage container table 308. At the same time, in step 1316, the facility management subsystem 204 updates its record by adding the Bin_ID of the DSCS container 224a to the on-site container table 322 of the large facility 12 to reflect the transfer of the DSCS container 224a from the transport vehicle 215a to the large facility 12, and if there is such data in the facility information table 319, it can be reflected by increasing the number of storage containers in the facility information table 319. In this step, in one embodiment, the facility management subsystem 204 also sends the container reception signal and the Bin_ID of the DSCS container 224a that has just received the large facility 12 to the central computing system 201, and the central computing system 201 will respond by adding the Facility_ID of the large facility 12 to the DSCS container 224a record in the storage container table 308.

[0191] After confirming that the machine handling device 208 received the DSCS container 224a from the transport vehicle 215a, the Equipment_ID of the machine handling device 208 is updated to the Location_ID of the storage location of the DSCS container 224a in the storage container table 308 of the central database 203 and the field container table 322 of the large facility 12, thereby allowing the DSCS container 224a to be associated with the Location_ID that can be tracked in real time. After confirming that the machine handling device 208 of the large facility 12 received the DSCS container 224a, the facility management subsystem 204 of the large facility 12 can now evaluate how to schedule the DSCS container 224a within the large facility 12 based on the environmental tag and processing and customization data read from the DSCS container 224a in step 1313, and instruct the machine handling device 208 to travel to the correct destination of the large facility 12 accordingly. In step 1317, the facility management subsystem 204 examines the destination data and time data received in step 1313 and evaluates whether the destination data and time data indicate that the DSCS container 224a is immediately cross-docked for rapid shipment to another facility, such as by comparing the destination data and time data and the location of the container. Figure 6 The transport vehicle 215a of the outbound unloading platform 602 of the large facility 12 shown or the transport vehicle 215a that is scheduled to arrive soon. If the destination data indicates that the target destination of the DSCS container 224a is not the current large facility 12 where the DSCS container 224a has just arrived, the facility management subsystem 204 of the current large facility 12 will generate a distribution scheduling command or instruction for automatic device control and / or human staff navigation to perform or instruct the cross-dock of the DSCS container 224a at the current large facility 12 if the transport vehicle 215a already exists or is about to arrive, or to perform or instruct the DSCS container 224a to be temporarily stored in the index storage configuration structure of the large facility 12 for future transportation to other facilities if the transport vehicle 215a does not exist or has not arrived yet.

[0192] The other facility to which the DSCS container 224a is transported by the transport vehicle 215b is the intended destination facility of the DSCS container 224a, or a relay facility closer to the intended destination facility. In other words, the current facility to which the DSCS container 224a arrives can be used as a relay point, through which the DSCS container 224a can continue to be transported to another facility, whether it is the intended destination facility or another relay point, without any processing or transfer of the contents in the DSCS container, such as value-added service (VAS)-related customization, matching to a multi-compartment storage (MCS) container, etc. In this way, the SCS container 224a packaged in the giant facility 10 at one extreme of the geographical range of the multi-node supply chain system 200 is not directly transported to the large facility 12 at the other extreme of the multi-node supply chain system 200, but is transferred through multiple relay facilities between the original giant facility 10 and the final destination 12. In various embodiments, such same container transfers through facilities may occur at transport stages other than the specific giant to giant transport stage currently under consideration, either across levels, such as giant to giant transport, giant to small transport, and small to nano transport, or at the same level, such as giant to giant transport, giant to giant transport, small to small transport, and nano to nano transport. In one embodiment, some or all transport vehicles have dedicated transport routes between two specific facilities, or have dedicated service areas between a limited group of facilities they travel. In the case of dedicated transport routes, the vehicle management subsystem 216 of each transport vehicle stores two default Facility_IDs, namely the upstream Facility_ID and the downstream Facility_ID, and is configured to automatically switch the value of the individual destination Facility_ID field between these two values ​​when the transport vehicle arrives at either of the two facilities and before the standardized data exchange with the facility management subsystem 204 is performed, and the next destination of the transport vehicle is determined through the facility to query the local container table 322 of the facility to determine those containers scheduled for delivery to the next destination of the transport vehicle.

[0193] If cross-transfer is required in step 1317, in one embodiment, in step 1318, a fully automated cross-transfer of the DSCS container 224a will be performed, in which case the facility management subsystem 204 will command the machine handling equipment 208 that is already carrying the DSCS container 224a to directly transport the DSCS container 224a to the outbound unloading platform 602, for example, by traveling from the inbound loading grid structure 604 to the outbound loading grid structure 605 through the lower track structure of the grid storage structure 603, wherein the machine handling equipment 208 will load the DSCS container 224a onto the waiting or arrived transport vehicle 215b in the outbound unloading platform 602.

[0194] If immediate cross-dock is not required, then in step 1322, the facility management subsystem 204 examines the custom data received from the DSCS container 224a in step 1313 and uses the custom data to evaluate whether the DSCS container 224a should be sent directly to the VAS / return workstation 606 rather than to the indexed storage location of the grid storage structure 603. In one embodiment, this evaluation includes querying the workstation information table 321 of the large facility 12 to determine whether the VAS / return workstation 606 provides appropriate support to fulfill the VAS requirements of the contents of the DSCS container 224a and whether the VAS / return workstation 606 has or will have capacity to receive the DSCS container 224a. If the VAS query in step 1322 is answered positively, then in step 1319, the facility management subsystem 204 instructs the machine handling equipment 208 to deliver or fully deliver the DSCS container 224a to an available VAS / return workstation 606. In one embodiment, the machine handling equipment 208 handles the complete delivery of the DSCS container 224a from the pickup point of the container at the terminal point next to the transporter of the loading grid structure 604 to the VAS / return workstation 606 via the grid under-grid track structure of the grid storage structure 603.

[0195] If the DSCS container 224a does not need to be immediately VAS-processed in step 1322, then in step 1322, the facility management subsystem 204 uses the environmental flag received from the DSCS container 224a in step 1313 to query the facility storage table 320a for the Location_ID of the available storage location whose environmental status of the grid storage structure 603 is consistent with the environmental flag of the DSCS container 224a, and instructs the machine processing device 208 to transport the DSCS container 224a and store the DSCS container 224a in the available environmentally compatible storage location, which is located in the grid storage structure 603. In step 1324, after confirming that the DSCS container 224a is placed in the available environmentally compatible storage location, the execution of the VAS-processing operation with the facility management subsystem 204 is started. Figures 12A-12B The communication and database update process for introducing containers in the giant facility 10 disclosed in the detailed description is the same, and the purpose and positive results are consistent with those described above.

[0196] In one embodiment, after the DSCS container 224a arrives, the delivery scheduling decision steps 1317 and 1322 performed by the facility management subsystem 204 are configured to, by default, command the DSCS container 224a to be shipped to the VAS / return workstation 606 for the DSCS container 224a whose container data has been read and includes custom data; and if the container data does not include custom data, only such schedule for delivery to the VAS / return workstation 606 is skipped. In this case, the system will command the DSCS container 224a in the grid storage structure 603 to be stored, especially in a predetermined environmental area indicated by the environmental flag from the read container data. In one embodiment, the delivery scheduling decision performed by the facility management subsystem 204 further includes a decision whether to bypass the storage in the index storage configuration structure and direct the DSCS container 224a (e.g., a single SKU container) to be sent directly to the kitting workstation 607 by checking whether the facility management subsystem 204 has received a product request for a product type that has arrived in the DSCS container 224a and is waiting for the arrival of the DSCS container 224a because the on-site SCS container in the facility's on-site SCS container table 322 does not have any or a sufficient number of the product type to fulfill the product request. The workflow associated with such a product request in the kitting workstation 607 is as follows.

[0197] therefore, Figures 13A-13B Steps 1306 to 1324 in the above process will collectively perform a single container exchange, wherein a DSCS container 224a arriving at the large facility 12 on an inbound transport vehicle 215a will be exchanged with a USCS container (e.g., an empty SCS container), which will then subsequently depart the large facility 12 on the same transport vehicle 215a. After completing the container exchange, at step 1320, the facility management subsystem 204 will check whether steps 1303 to 1305 have left other USCS containers in the inventory, and if so, repeat steps 1306 to 1324. If not, then in step 1321, the facility management subsystem 204 and the vehicle management subsystem 216 will collaboratively check whether the remaining DSCS containers 224a are still on the transport vehicle 215a, waiting to be unloaded by the machine handling equipment 208, so as to understand that the number of DSCS containers 224a exceeds the number of USCS containers currently located at the large facility 12 and plans to travel to the mega facility 10, which is the location where the transport vehicle 215a will go next. If the result of the confirmation in step 1321 is yes, step 1312 will continue to be repeated until the result of step 1321 is no, thereby confirming that all DSCS containers 224a have been unloaded from the transport vehicle 215a and received at the large facility 12.

[0198] Figures 13A-13BIn the method disclosed in , it is assumed that in step 1307, there is already at least one unloaded transport platform 1002 on the transport vehicle 215a, and the USCS container delivered to the inbound unloading platform 601 by the first machine handling equipment 208 can be stored on the platform; however, other embodiments may require that steps 1312 to 1316 be performed in advance by another unloaded machine handling equipment to unload the first DSCS container 224a from the fully loaded transport vehicle 215a, leaving no empty transport platform, and then any USCS container can be loaded onto the transport vehicle 215a. In various embodiments, the loading and unloading processes of different facilities are configured so that the container transporter 222a is not filled up, so that at least one transport platform 1002 must remain open during transportation to receive the first storage container on the transport vehicle 215a loaded to its next destination.

[0199] As mentioned above, each large facility 12 includes Figure 6 One or more VAS / return workstations 606 are shown, where value-added services are performed on products in DSCS containers received by the mega facility 10. Although some or all of the DSCS containers are introduced directly into the grid storage structure 603 of the mega facility 12 for buffering therein and later retrieval to the VAS / return workstations 606 when needed, in one embodiment, if the capacity of the VAS / return workstations 606 allows, the DSCS containers are stored in the VAS / return workstations 606 according to the VAS / return workstations 606. Figures 13A-13BOptional steps 1322 and 1319 are shown, where VAS services may be selectively performed before the DSCS container is introduced into the index storage configuration structure grid storage structure 603 of the large facility 12, wherein if the container data read from the mobile data storage device 226 of the arriving DSCS container 224a includes VAS custom data, and a suitably configured VAS workstation 606 is currently or will be available, the DSCS container 224a will be directly dispatched to one of the VAS / return workstations 606. Whether extracted from the index storage configuration structure or dispatched directly to the VAS / return workstation 606 upon arrival at the large facility 12, when the VAS / return workstation 606 receives the DSCS container 224a, data exchange will be performed, wherein the facility management subsystem 204 will read the Bin_ID and at least a portion of the product information read from the product information table 328 of the mobile data storage device 226 of the DSCS container 224a, and the DSCS container 224a will perform appropriate VAS actions based on the custom data contained in the read product information. If there is a human employee in the VAS / return workstation 606, in one embodiment, the human-machine interface (HMI) of the VAS / return workstation 606 will display the correct VAS instructions derived from the read custom data to guide the human employee. For example, the VAS will be displayed on the display of the human-machine interface (HMI) of the VAS / return workstation 606, or on a head-mounted display of the human-machine interface worn by the human employee. In one embodiment, if the VAS / return workstation 606 is fully automated, the automated robot worker will perform the actions defined by the read custom data according to the instructions of the facility management subsystem 204.

[0200] Examples of VAS actions / instructions include: removing the original packaging (e.g., plastic bag) of the product; adding a security label, price tag, expiration label, warning label, and / or brand label (e.g., the name or logo of the owner's supplier) if refrigeration is required; and / or repackaging the product in non-original packaging, such as the owner's supplier's brand packaging. In one embodiment, different VAS / return workstations 606 contain supplier-specific goods from different suppliers, wherein the facility management subsystem 204 also reads the owner's Vendor_ID from the mobile data storage device 226 of the SCS container 224a during the above data exchange, and compares the owner's Vendor_ID with the workstation information table 321 stored in the local facility database 207 of the facility management subsystem 204, or in one embodiment, stored as record or additional information in the central database 203, to identify which of the VAS / return workstations 606 of the large facility 12 is equipped with the supplier's specific goods, and thereby determine which VAS / return workstation 606 each SCS container 224a should be routed to.

[0201] Fig.14 According to one embodiment of the present invention, a flowchart of a computerized implementation method is shown, wherein the method is used to manage Figure 6 The performance of a value-added service (VAS) on the contents of a storage container of a large facility 12 is shown. The method disclosed herein includes Figure 6 VAS customization of a single compartment storage (SCS) container 224a of a VAS / return workstation 606 of a large facility 12 is shown. When a SCS container requires VAS processing (i.e., step 1401), in step 1402, the facility management subsystem 204 commands a machine processing device 208 to transport an SCS container 224a containing a product and whose contents have been determined to be VAS processed at one of the VAS / return workstations 606 to the VAS / return workstation 606, and commands another machine processing device 208 of a grid storage structure 603 of the large facility 12 to take out an empty SCS container 224a and transport the empty SCS container 224a to the same VAS / return workstation 606. The system selects the empty SCS container 224a based on a condition, wherein the condition indicates that the environmental label of the empty SCS container 224a meets the environmental label of the SCS container 224a containing the product. Therefore, the empty SCS container 224a is taken out from the specific environment area of ​​the grid storage structure 603, and the product of the empty SCS container 224a is then returned to the empty SCS container 224a after being processed at the VAS / return workstation 606. Figures 13A-13B As disclosed in the detailed description of the invention, in step 1322 of introducing the SCS container into the large-scale facility 12, the comparison and ordering of the container transportation are performed, and the identification of the SCS container 224a containing the product is based on the above comparison, that is, comparing the custom data stored in the SCS container 224a, and Figure 3C6, in which case the SCS container 224a containing the product is directly transported from the inbound loading grid structure 604 to the VAS / return workstation 606; or as an independent subsequent query after the SCS container 224a has been stored in the grid storage structure 603, in which case the SCS container 224a containing the product is retrieved from the grid storage structure 603 by the machine processing device 208 receiving the command. In one embodiment, if all VAS / return workstations 606 have equal goods and configurations, the identification of SCS containers requiring VAS is based on an evaluation that includes significant differences between two types of SCS containers: SCS containers with custom data fields that have been populated with any one or more custom conditions, regardless of the conditions; and SCS containers without any such custom conditions; rather than comparing different goods and configuration information for different workstations with different goods / configurations with the custom data of the SCS containers on site.

[0202] When executing the travel command steps 1403 and 1404 in parallel, the facility management subsystem 204 will command the first machine processing equipment 208 to specifically transport the SCS container 224a containing the product to Figure 6 The VAS / return station 606 is shown with the item pick-up port 606b, and instructs the second machine processing device 208 to specifically transport the empty SCS container 224a to the Figure 6 The storage port 606a of the VAS / return workstation 606 is shown. When the SCS container 224a containing the product arrives at the VAS / return workstation 606, the customized data of the mobile data storage device 226 of the SCS container 224a containing the product is transmitted to the facility management subsystem 204, such as through the local area network 206 such as the wireless network of the large facility 12. Whether using custom data to direct the automated control of the machine operator at the VAS / Returns Station 606 through the Facility Processing Subsystem 204, or visual and / or audible instructions to instruct the human employee at the VAS / Returns Station 606 through a human machine interface (HMI) mounted at the VAS / Returns Station 606 or carried by the human employee, once both SCS containers 224a have successfully arrived at the respective placement ports 606a and access ports 606b of the VAS / Returns Station 606 via the machine handling equipment 208, in step 1405, the contents of the SCS container 224a containing the product are removed through the access ports 606b and processed according to the VAS requirements defined by the custom data received from the SCS container 224a containing the product. Next, the processed product is placed in the initially empty SCS container 224a, which is located at the placement port 606a of the VAS / Returns Station 606.

[0203] After determining that all contents have been removed from the SCS container 224a parked at the take-out port 606b, processed, and placed in the SCS container 224a containing products now parked at the placement port 606a, in step 1406, the facility management subsystem 204 will: Figure 3E The product information table 328 of the mobile data storage device 226 shown copies the Product_ID, the owner's Vendor_ID, the product quantity, the destination data, the time data and all or part of the product information of the empty SCS container 224a which is now parked at the pickup port 606b; and transfers the copied data to the mobile data storage device 226 of the SCS container 224a containing the product which is now parked at the placement port 606a; then the copied data and any other data that does not need to be copied are cleared from the mobile data storage device 226 of the now empty SCS container 224a which is parked at the pickup port 606b; thereby erasing any variable data of any mobile data storage device 226, which will vary depending on the contents of the SCS container 224a, so that the SCS container 224a can appear empty to the facility management subsystem 204 at any time in the future when reading its mobile data storage device 226. In one embodiment, the facility management subsystem 204 may selectively ignore customization data that is no longer needed after performing VAS customization and no longer copy the data to the mobile data storage device 226 of the SCS container 224a that now contains the product. In one embodiment, the facility management subsystem 204 records the empty status of the currently empty SCS container 224a in the local facility database 207 by switching the empty / full status flag in the field container table 322 to the "empty" status in the individual record of the currently empty SCS container 224a.

[0204] In connection with the transfer of product and container data from a first SCS container 224a that originally contained product and is now empty, to a second SCS container 224a that was originally empty and is now filled with product, the facility management subsystem 204 also communicates with the central computing system 201 in step 1406 to locate the record containing the Bin_ID of the SCS container 224a from which the product was transferred in the inventory table 304 of the supplier from which the product was transferred between containers, and rewrite the Bin_ID and Compartment_ID fields of this record to the Bin_ID and Compartment_ID of the SCS container 224a to which the product was transferred. Therefore, a subsequent query in the supplier's inventory table 304 for the type of product that was just transferred between containers will correctly return the Bin_ID of the SCS container 224 that was just filled with the product, i.e., the container to which the product was transferred. In one embodiment, Figure 3CThe field container table 322 of the local facility database 207 shown includes: product presence / absence status identifiers for each Bin_ID; the SCS container from which the product is transferred and the SCS container to which the product is transferred, product presence / absence status identifiers from presence to absence of product and from absence of product to presence of product, respectively.

[0205] Next, in parallel steps 1407 and 1411, the two machine handling devices 208 receive commands to deposit the two SCS containers in the grid storage structure 603. In step 1407, the first machine handling device 208 receives a command to return the now empty SCS container being transported above to any available storage location in the grid storage structure 603, such as an environmental zone in the grid storage structure 603 that matches the environmental signature of the now empty SCS container; in the case where the now empty SCS container was originally loaded with product and was removed from the grid storage structure 603, rather than being redirected from the inbound unloading platform 601 to the large facility 12 during the induction process, the available storage location will generally be the same environmental zone where the now empty SCS container was before it was loaded with product. Now, the SCS container on the first machine processing device 208 is empty. If the SCS container is a refrigerated storage container or a freezer storage container, in one embodiment, the SCS container can be selectively stored in the normal temperature zone when it is empty; on the contrary, a normal temperature storage container that cannot be stored in the refrigerated zone or the freezer zone cannot be selectively stored in the two zones. Therefore, there is an example of such a situation: the empty storage container is installed in an environmental zone, which is different from the environmental zone where the empty storage container was previously taken out and does not meet the environmental mark of the empty storage container. In step 1411, the second machine processing device receives the command and returns the SCS container now filled with products to any available storage position in the grid storage structure 603, especially an available storage position in the environmental zone that meets the environmental mark of the SCS container now filled with products; in this case, the position where the SCS container now filled with products was taken out from the grid storage structure 603 when it was empty before is usually the same environmental zone as the position where the SCS container now filled with products was taken out when it was originally empty. In one embodiment, there may be such a situation: there is no special place for the empty storage container to be stored in the area that meets its environmental mark. In one embodiment, if Figure 6 As shown, the two machine handling devices 208 that transported the two SCS containers to the VAS / return workstation 606 are also the two machine handling devices 208 that transported the two SCS containers away, but this is not necessarily the case; especially when one or both of the workstation ports, namely the pickup port 606b or the placement port 606a, are not fully loaded by the machine handling device 208 and passed through the VAS / return workstation to achieve a drive-through mode service.

[0206] In step 1408, after confirming that the SCS storage container is placed in the available storage location, the facility management subsystem 204 records the Bin_IDs of the two SCS containers against the two Location_IDs of the two storage locations, records the Bin_IDs of the two SCS containers in the facility storage table 320a of the local facility database 207, and / or records the two Location_IDs of the two storage locations in the field SCS container table 322 of the local facility database 207. Moreover, in step 1408, the facility management subsystem 204 forwards the Location_ID and Bin_ID of the two SCS containers to the central computing system 201 to record each Location_ID in the global storage container table 308 against the Bin_ID of the individual SCS containers, and if there are duplicate Location_IDs in the inventory table 304, the Location_ID of the location of the SCS container that currently holds the product is selectively recorded in the inventory table 304. Thus, querying the inventory table 304 for the product that was just transferred between containers will return the Bin_ID of the SCS container that just contained the product, rather than the Bin_ID of the empty SCS container that just contained the product. Based on the updated Bin_ID, the Location_ID of the storage location where the SCS container that just contained the product is currently stored can also be retrieved from the storage container table 308, or in one embodiment, directly from the inventory table 304 if there is a duplicate in the inventory table 304, wherein the Facility_ID of the large facility 12 where the storage location is located can also be retrieved from the global storage location table 310, or directly from the inventory table 304 or the global storage container table 308 if there is a duplicate field. Thus, querying the supplier inventory table 304 will identify the Bin_ID of each SCS container where each product type is located, the number of product types in the SCS container, the Facility_ID of the facility where the SCS container is located, and, if the SCS containers are stored in an index storage structure of the large facility 12, the specific storage location of the SCS container can be identified.

[0207] Once the product contents in the SCS container 224a are labeled, marked, repackaged, or otherwise customized in accordance with the supplier-specific VAS conditions defined by the customization data of the SCS container 224a at the VAS / return workstation 606, the customized product is typically introduced into the indexed storage configuration structure of the large facility 12. In one embodiment, as shown in optional steps 1409 and 1410, the facility management subsystem 204 checks whether the destination data and time data read from the SCS container that originally contained the product and is now empty, and subsequently copied to the SCS container that was originally empty and now filled with the product, indicate an urgent priority or a short delivery time that would dictate immediate outbound inbound shipment after VAS processing is completed, rather than into an indexed storage location. If so, the second machine processing equipment 208 will then receive the command to transport the SCS container now filled with products to the outbound unloading platform 602 of the large facility 12 through the outbound loading grid structure 605, and urgently load the SCS container now filled with products onto the transport vehicle 215b to leave for a facility; the facility matches the Facility_ID of the destination facility of the SCS container, or is a known relay point between the current large facility 12 and the destination facility.

[0208] In the illustrated example, the index storage configuration structure is distributed in different environmental storage areas of the shared grid storage structure 603, that is, where the VAS / return workstation 606 is connected, so that all environmental areas and workstations are served by a single shared cluster of machine processing equipment 208; those skilled in the art will understand that in other embodiments, the different environmental storage areas include individual storage structures that are isolated from each other in a machine manner; the facility management subsystem 204 guides the processed SCS container to a specific environmental storage area of ​​the large facility 12, which is defined by the environmental identification of the SCS container and the corresponding environmental data of the product contained in the SCS container, and the guidance involves other steps in addition to commanding the machine processing equipment 208 to move, such as computer automatic control of the transporter and the relevant delivery schedule of the device to transport the SCS container to the isolated storage environment, or visually and / or audibly instructing human employees through one or more human-machine interfaces to perform such transfers, whether using one or more fixed human-machine interfaces or mobile wearable human-machine interface devices, such as smart phones, tablet computers, watch-type displays, head-mounted displays, headphones, etc.

[0209] Although the illustrated embodiment uses a dual-port VAS / return workstation 606 to perform VAS processing and involves transferring the product from an SCS container 224a to another SCS container 224a when processing the product, those skilled in the art will understand that in other embodiments, a single SCS container and a single-port workstation may be used. In this case, the product is removed from the SCS container, processed according to specific VAS conditions defined by the custom data, and then returned to the same SCS container, which is then sent back to the grid storage structure 603, either to the same storage location from which the SCS container was removed, or to a different available storage location in the same environmental zone in the grid storage structure 603; the system will then record it in the same manner as described in step 1408 of the dual container process.

[0210] In addition to Figure 4A The large transport vehicles 215a shown are transporting arriving SCS containers from one or more mega facilities 10. In one embodiment, each mega facility 12 may also receive SCS containers 224a from other facilities inside or outside the multi-node supply chain system 200, including pre-loaded containerized supply goods 401b from external distribution centers, which are owned and operated or contracted by one or more suppliers and / or external manufacturers. In one embodiment, SCS containers 224a received from such sources outside the mega facility 10 are received at the inbound unloading platform 601 and are referred to as Figures 13A-13B The same method is used to unload from the inbound unloading platform 601, regardless of whether Figures 13A-13B An embodiment of the present invention allows real-time loading of empty SCS containers or other outgoing storage containers in the same manner as USCS containers.

[0211] Apart from Figure 6In the VAS / return workstation 606 disclosed in the embodiment of the invention, the large facility 12 includes one or more kitting workstations 607, i.e., where the SCS containers 224a containing the products are removed, which is usually done after the SCS containers 224a are introduced into the grid storage structure 603 and stored therein for a period of time, and before downstream demand for the single SKU products stored in these SCS containers 224a from one or more small facilities 14 makes it necessary to extract the products from these SCS containers 224a of the index configuration structure to fulfill these downstream demands. In one embodiment, the same automatic machine handling equipment 208 responsible for removing the SCS containers 224a from the grid storage structure 603 transports the SCS containers 224a to these kitting workstations 607, for example, via extension tracks leading from the lower track structure of the grid storage structure 603 to and / or into such kitting workstations 607. Each kitting station 607 is also provided with a supply of multi-compartment storage (MCS) containers 224b which, in one embodiment, have the same footprint, exterior dimensions, and configuration as the SCS containers 224a to be compatible with the types of indexed storage configurations used in the mega facility 10, large facility 12, and small facility 14, as well as in the transport vehicles 215b and 215b that transport the storage containers between the mega facility 10, large facility 12, and small facility 14. The interior space of each MCS container 224b is divided into a plurality of smaller compartments so that different products loaded into the MCS container 224b are separated from each other.

[0212] Although in the detailed embodiment, both types of storage containers 224a and 224b can be distinguished by the degree of compartmentalization (i.e., uncompartmentalized SCS containers and compartmentalized MCS containers), and by the mixed or non-mixed characteristics of the products placed in the containers (i.e., unmixed products of a single product type that conforms to Product_ID in a single-SKU SCS container, and mixed products of multiple product types that do not conform to Product_ID in a multi-SKU MCS container), those skilled in the art will understand that in other embodiments, both types include compartmentalized containers, in which case the difference between the two types lies in any one or more of the following: the number of compartments possessed by the storage containers of each type; the mixed / non-mixed characteristics of the contents received by each type of storage container; and the Figure 2A -2C and Figures 4A-4BThe product workflow of the multi-node supply chain system 200 is shown, with the order in which each type of storage container is loaded with products; in other words, the first type of storage container 224a will be loaded with "manufacturer products" to fulfill the inventory needs of suppliers, and the "manufacturer products" will enter the multi-node supply chain system 200, while the second type of storage container 224b will be loaded with inventory-ready "supplier products" that have been previously introduced into the first type of storage container 224a in the multi-node supply chain system 200 and are ready to be picked during the order fulfillment stage. In one embodiment, the first type of storage container 224a is also a compartmentalized container, which has multiple compartments divided inside, but the number of compartments is less than that of the second type of storage container 224b, so that the same relationship as the detailed embodiment can be retained, in which the number of compartments of the second type MCS container 224b is greater than the number of compartments of the first type SCS container 224a.

[0213] Figures 15A-15B A flowchart showing a computerized implementation method for managing Figure 6 and Figures 4A-4B The smart container products of the large facility 12 shown are compiled into smart container kits to fulfill the downstream product needs of other facilities. In any predetermined large facility 12, the facility management subsystem 204 and Figure 2A-2B The central computing system 201 shown in FIG. 1500 communicates with the central computing system 201, which continuously identifies the forecasted or current inventory requirements of each supplier in each facility of the multi-node supply chain system 200, and thereby identifies the inventory requirements of the small facilities 14 or possibly other large facilities 12 located downstream of the predetermined large facility 12, which can be fulfilled by the existing products of the predetermined large facility 12. This method (step 1501) will begin after such product fulfillment requirements occur. The process will compile the required product types into multi-compartment storage (MCS) containers and guide the MCS containers to the outbound unloading platform 602 of the large facility 12 for upward transportation toward other facilities that need the product types, which are referred to herein as "facilities with demand".

[0214] In step 1502, the central computing system 201 transmits product requirement information including at least one set of container configuration data to the facility management subsystem 204 of the large facility 12. Each container configuration data set includes: the Vendor_ID of the supplier in need who needs more than one product type at the facility in need; the Product_ID of each of the above product types; the quantity of each product type required by the facility in need; the Bin_ID of the SCS container 224a at the large facility 12 that holds the required quantity of the product type; the Facility_ID of the facility in need; and time information related to shipping time constraints or urgency to fulfill the product demand. In the case of using the selected large facility 12 to fulfill the inventory demand of the facility in need, the central computing system 201 has already queried the large facility 12 to fulfill the inventory demand of the facility in need. Figure 3A The in-demand supplier inventory table 304 shown in , identifies that the supplier has sufficient on-hand inventory at the predetermined large facility 12 to fulfill the required quantity of the required product type, and the Bin_ID has been retrieved from the query.

[0215] In one embodiment, if each local facility database 207 maintains Figure 3C The container configuration data sent by the central computing system 201 omits the Bin_ID of the specific SCS container 224a, and the facility management subsystem 204 determines which specific storage bin to extract from the storage space based on a query of the local existing inventory record for the Product_ID of the desired product type. Similarly, in one embodiment, the container configuration data set includes a request for the local existing inventory record for the Product_ID of the desired product type. Figure 3A The environmental tag recorded in the Bin_ID in the storage container table 308 shown, or the environmental data recorded for the required product type in the supplier product table 303. In another embodiment, after the system receives the container configuration data set, the facility management subsystem 204 pulls such environmental tags / data from the local facility database 207.

[0216] After the large facility 12 receives the container configuration data and identifies the Bin_ID of the SCS container of the desired product type contained therein, and the environmental tag / data associated with the container / product type, if not specified in the container configuration data, then in step 1503, the facility management subsystem 204 of the large facility 12 queries its on-site container table 322 to find an empty MCS container that matches the environmental tag, and instructs the first machine processing equipment 208 of the grid storage structure 603 to retrieve the empty MCS container 224b, typically from its environmental area corresponding to the matching environmental tag, and transport the empty MCS container 224b to Figure 6The supporting workstation 607 shown. In one embodiment with a dual-port supporting workstation 607, in step 1504, the first machine handling device 208 is specifically instructed to transport the removed empty MCS container 224b to the access port 607a of the supporting workstation 607. In another embodiment, if the MCS container 224b is stored elsewhere outside the grid storage structure 603, the facility management subsystem 204 will instruct human employees, such as visual and / or auditory instructions transmitted by a human-machine interface (HMI) installed at the supporting workstation 607 or carried by the human employee, to remove and transport the designated empty MCS container 224b, or the undesignated MCS container 224b with a predetermined environmental tag; or through an automatic transporter and related distribution scheduling device, triggering automatic transportation to transport the designated or undesignated empty MCS container 224b to the supporting workstation 607.

[0217] At the same time, in step 1505, the facility management subsystem 204 of the large facility 12 will command the second machine processing equipment 208 to take out the first SCS container 224a of the SCS container 224a identified by Bin_ID from its storage location in the grid storage structure 603, as identified by the Location_ID stored in the field container table 322 of Bin_ID, and command the second machine processing equipment 208 to transport the first SCS container 224a to the same supporting workstation 607, which is where the empty MCS container 224b was placed or is being placed, and the empty MCS container 224b is transported by the first machine processing equipment 208. After confirming that the second machine handling device 208 has removed the first SCS container 224a from the grid storage structure 603, the Equipment_ID of the machine handling device 208 is updated to the Location_ID of the storage location of the first SCS container 224a in the storage container table 308 of the central database 203 and the field container table 322 of the large facility 12, thereby allowing the first SCS container to be associated with the Location_ID that can be tracked in real time. In the illustrated embodiment with a dual-port matching station 607, in step 1506, the second machine handling device 208 is specifically instructed to transport the first SCS container 224a to the access port 607b of the matching station 607.

[0218] Next, in step 1507, the facility management subsystem 204 instructs or commands the human employee or machine worker at the supporting workstation 607 to take out the product quantity from the first SCS container 224a of the access port 607b according to the specified quantity of the product type of the SCS container 224a in the container configuration data set, and place the requested product type quantity into the individual compartments of the MCS container 224b of the placement port 607a. In step 1508, after confirming that the specific product quantity is transferred from the first SCS container 224a of the access port 607b to the MCS container 224b of the placement port 607a, the facility management subsystem 204 transmits a signal to the central computing system 201 to update the inventory record in the central database 203 by reducing the recorded product quantity in the storage container content table 308 of the first SCS container 224a by the quantity transferred to the MCS container 224b; and records the MCS container compartment to which the product is transferred in the storage container content table 309, and writes the Product_ID of the transferred product type and its transferred quantity. Therefore, the supplier inventory list table 304 and the storage container content table 309 will be properly updated to record the reduction in the remaining product quantity (if any) in the SCS container 224a and the newly found product transfer quantity in the MCS container 224b. If the reduction in the SCS container 224a is zero, then in one embodiment, the central computing system 201 will clear the Product_ID and the owner Vendor_ID in the corresponding record of the storage container content table 309 to reflect the empty status of this first SCS container 224a, and the facility management subsystem 204 will similarly record it in the local facility database 207 by switching the empty / full status flag in the field container table 322 to "empty".

[0219] Moreover, in step 1508, the data update at this point further includes updating the mobile data storage device 226 of the first SCS container 224a and the MCS container 224b via the facility management subsystem 204. The product information table 328 of the MCS container 224b has a new record copied over, relating to the product type transferred to the MCS container 224b, either from the product information table 328 on the mobile data storage device 226 of the SCS container 224a or from the supplier product table 303 in the central database 203. The storage container contents table 309 on the mobile data storage device 226 of the MCS container 224b is likewise updated to write the Product_ID and the transferred quantity record for the transferred product type to the container contents record for the specific interval of the MCS container 224b where the transferred product is placed, and in one embodiment, the Vendor_ID is also written, which allows for multi-vendor matching of vendors sharing MCS containers, as further described below. The data written to the mobile data storage device 226 of the MCS container 224b further includes a subset of the container configuration data set received from the central computing system 201, such as: the Facility_ID of the required facility, which is written to the destination data field of the MCS container 224b; and time data, which is written to the time data field of the MCS container 224b.

[0220] At the same time, the facility management subsystem 204 will also deduct the transfer quantity from the quantity field in the storage container content table 327 of the SCS container 224a, and if the reduced quantity becomes zero, the product information table 328 will be cleared, and the Vendor_ID and Product_ID of the owner of the storage container content table 327 will be cleared, thereby reflecting the empty state of the first SCS container 224a, wherein, in one embodiment, the facility management subsystem 204 will switch the empty / full state flag in the field container table 322 to "empty" for the SCS container 224a, thereby recording it in the local facility database 207. In such a case where the first SCS container 224a is empty, in one embodiment, if there is such data in the facility information table 319, the local facility management subsystem 204 will also increase the number of empty SCS containers 224a in the facility information table 319. Likewise, during the first instance of step 1508, the facility management subsystem 204 increases the number of placed MCS containers 224b in the facility information table 319 if such data is present.

[0221] In the case where new content-related data is written to the mobile data storage device 226 of the MCS container 224b, the MCS container 224b contains the static Bin_ID and static environment flags of the MCS container 224b, as well as the Vendor_ID of the owner of the content of the MCS container 224b, the latest destination and time data of the content of the MCS container 224b, and the content-related product information. In ...

Claims

1. A supply chain system comprising a plurality of interconnected entities for executing a supply chain workflow using a plurality of transportable and continuously traceable storage containers, wherein the plurality of interconnected entities include: a network of node facilities distributed throughout a geographic region, wherein each of said node facilities includes a facility-type configuration structure indexing storage locations; a fleet of inter-node transport vehicles for transporting a plurality of inventory items contained in storage containers between said node facilities, wherein each of said inter-node transport vehicles includes a vehicle configuration structure indexing storage locations; a plurality of storage containers storable in the network of node facilities and transportable between the node facilities by the inter-node transport vehicles, wherein each of the storage containers has a standardized size and is configured to receive one or more of a plurality of inventory items, and wherein the configuration of each of the storage containers is compatible with the facility-type configuration structure of the indexed storage locations and the vehicle-type configuration structure of the indexed storage locations to selectively store and continuously track any of the storage containers at any of the node facilities, in any of the inter-node transport vehicles, and between any of the node facilities and any of the inter-node transport vehicles; and A computerized supply chain management system, which is communicatively connected to the node facility network, the fleet of inter-node transportation vehicles, and the storage container, the computerized supply chain management system includes: at least one processor; at least one non-transitory computer-readable storage medium, which is communicatively connected to the at least one processor, wherein the non-transitory computer-readable storage medium includes one or more databases configured to store container data including container identifiers assigned to storage containers, and store location identifiers of the index storage locations of the facility-type configuration structure and the vehicle-type configuration structure, and the location of the dynamic storage location of the storage container, and wherein the non-transitory computer-readable storage medium The structure is configured to store computer program instructions, which, when executed by the at least one processor, will cause the at least one processor to update the location identifier when the storage container moves between the index storage locations of the facility-type configuration structure and the vehicle-type configuration structure when the storage container moves back and forth between the node facility network and the fleet of inter-node transport vehicles in the supply chain system; and wherein the node facility network, the fleet of inter-node transport vehicles and the plurality of storage containers are all in operably communication with a computerized supply chain management system and are configured to provide complete traceability of each of the storage containers, one or more of which, from entry into the supply chain system to completion of order fulfillment.

2. The supply chain system according to claim 1, It is characterized in that The plurality of storage containers are further configured to hold one or more of the plurality of inventory items that are owned by one or more of the plurality of suppliers.

3. The supply chain system according to claim 1, It is characterized in that The non-transitory computer-readable storage medium is further configured to store additional computer program instructions which, when executed by the at least one processor, will cause the at least one processor to receive and process the container data and commands from each storage container as the fleet of vehicles transporting each storage container moves back and forth in forward and reverse directions between the node facility network and the node of the supply chain.

4. The supply chain system according to claim 1, It is characterized in that The non-transitory computer-readable storage medium is further configured to store additional computer program instructions which, when executed by the at least one processor, cause the at least one processor to automatically record and connect the container identifier of the storage container to the indexed storage location and the location identifier of the dynamic storage location in the facility-type configuration structure and the vehicle-type configuration structure in the one or more databases, the item identifier of the inventory items contained in the storage container, and the supplier identifiers of multiple suppliers whose inventory items are contained in the storage container.

5. The supply chain system according to claim 1, It is characterized in that The non-transitory computer-readable storage medium is further configured to store additional computer program instructions which, when executed by the at least one processor, cause the at least one processor to generate task-type instructions that facilitate performing loading actions and order fulfillment actions at one or more of the node facilities based on the container data.

6. The supply chain system according to claim 1, It is characterized in that Further comprising one or more machine processing devices operable in each of the node facilities, wherein the one or more machine processing devices are configured to find any one of the storage containers through the facility-type configuration structure of the indexed storage locations, and to select to leave the storage container in place or to remove it, and wherein each of the one or more machine processing devices is further configured to provide a dynamic storage location for each of the storage containers, and wherein each of the one or more machine processing devices assigns a unique identifier configured to indicate one of the dynamic storage locations of the storage container and to allow real-time tracking of the storage container.

7. The supply chain system according to claim 1, It is characterized in that Any one or more of the storage containers include a plurality of compartments configured to store the inventory items from a plurality of suppliers in any one or more of the storage containers, wherein each of the compartments is identified by a compartment identifier and is configured to store one or more of the inventory items owned by a corresponding one of the suppliers, and wherein the computerized supply chain management system is further configured to record and connect the compartment identifier of an individual one of the compartments to the item identifier of any one or more of the inventory items contained in any one or more of the storage containers, and the supplier identifier of the supplier whose inventory items are contained in any one or more of the storage containers.

8. The supply chain system according to claim 1, It is characterized in that The storage containers are divided into: a first type of storage container, which contains unmixed inventory items of matching item types; a second type of storage container, which contains unmatched mixed inventory items; A third type of storage container configured as an order container for fulfilling an order, and wherein the node facility network is a hierarchical network comprising: at least one mega-facility configured to store said first type of storage container; at least one large facility configured to receive one or more first-type storage containers delivered from the at least one mega facility, and to load different inventory items in the received one or more first-type storage containers into a predefined number of second-type storage containers to meet actual inventory demand or predicted inventory demand of another or more of the node facilities; and At least one small facility is configured to receive one or more of the second type storage containers shipped from the at least one large facility, and to load the one or more different inventory items received from the second type storage containers into a predefined number of order containers to fulfill orders.

9. The supply chain system according to claim 8, It is characterized in that The node facility network further includes at least one nano-facility configured to receive one or more of the order containers containing orders for pickup by a customer or delivery personnel.

10. The supply chain system according to claim 8, It is characterized in that The at least one micro-facility is configured to fulfill orders based on one of: a distance of the at least one micro-facility to the at least one nano-facility; and a customer preference of the at least one nano-facility.

11. The supply chain system according to claim 8, It is characterized in that The order containers include completed order containers, and wherein the standardized size and configuration of the completed order containers are different from other storage containers, and after one or more of the inventory items of a separate order are taken away from the facility-type configuration structure of the at least one small facility, the completed order containers are filled with one or more of the inventory items of a separate order, and wherein the standardized size and configuration of the completed order containers are configured to be compatible with the facility-type configuration structure of the indexed storage location of at least one nano-type facility, and the vehicle-type configuration structure of the indexed storage location in a node-to-terminal transportation vehicle.

12. The supply chain system according to claim 11, It is characterized in that The inventory items owned by the supplier are packaged into individual packages with the supplier's brand, and the individual packages with the supplier's brand are packed into the completed order containers.

13. The supply chain system according to claim 8, It is characterized in that The storage container includes a picked order container, which has the same standardized size and configuration as the storage container and is filled with one or more inventory items for multiple orders of the at least one small facility, and will be introduced into the facility-type configuration structure of the at least one small facility.

14. The supply chain system according to claim 8, It is characterized in that The orders are fulfilled at one or more of the at least one large facility and the at least one small facility.

15. The supply chain system according to claim 1, It is characterized in that Further comprising a mobile data storage device having a computer-readable memory operably connected to each of the storage containers, wherein the mobile data storage device is configured to store a unique container identifier for each of the storage containers and associated container data for the inventory items contained in each of the storage containers.

16. The supply chain system according to claim 1, It is characterized in that The container data includes at least one of the following: - Inventory catalogue; inventory item data including an item identifier, quantity, and attributes for each of said inventory items contained in each of said storage containers; destination data relating to a destination of the inventory items contained in the container; time data associated with a time frame and a level of urgency for each inventory item contained in the storage container to be transported through the supply chain system toward a destination; inventory customization data associated with an action for a value-added service to be performed on the inventory items contained in each of the storage containers; inventory management data relating to delivery scheduling, handling and / or packaging requirements for the inventory items contained in each of the storage containers; as well as Environmental data related to environmental requirements of the inventory items contained in each of the storage containers.

17. The supply chain system according to claim 1, It is characterized in that The non-transitory computer-readable storage medium is further configured to store additional computer program instructions, which, when executed by the at least one processor, cause the at least one processor to generate task-type instructions for triggering loading actions and unloading actions at one or more of the node facilities based on the container data, wherein the loading actions and the unloading actions include: Unloading storage containers delivered from any one of the inter-node transport vehicles to any one of the node facilities, and reloading storage containers to be delivered from any one of the inter-node transport vehicles to any one of the node facilities, wherein the delivered storage containers and the delivered storage containers are exchanged in a one-to-one correspondence between any one of the inter-node transport vehicles and any one of the node facilities to allow the storage containers to flow in a reciprocal manner in both forward and reverse directions through the supply chain system; Reading a unique container identifier for each of the outgoing storage containers loaded from any one of the node facilities onto any one of the inter-node transport vehicles, and updating the one or more databases of the computerized supply chain management system with the unique container identifier to record the transfer of each of the outgoing storage containers to any one of the inter-node transport vehicles; and A unique container identifier of each of the delivered transport containers unloaded from any of the inter-node transport vehicles is read to any of the node facilities, and one or more databases are updated with the unique container identifier to record the transfer of each of the delivered storage containers to any of the node facilities.

18. The supply chain system according to claim 17, It is characterized in that At least one of the send-out storage containers is an empty storage container.

19. The supply chain system according to claim 17, It is characterized in that At least one of the send-out storage containers is a non-empty storage container that contains at least one of the inventory products.

20. The supply chain system according to claim 19, It is characterized in that The non-empty storage container contains one of a desired inventory item and a customer return.

21. The supply chain system according to claim 17, It is characterized in that The standardized size and configuration of the delivery storage container and the delivery storage container are the same as the storage container.

22. The supply chain system according to claim 1, It is characterized in that Further comprising at least one sensor operably connected to each of the storage containers, wherein the at least one sensor is configured to detect movement of the storage containers through a supply chain system, respond to the detected movement, and initiate tracking of each of the storage containers.

23. The supply chain system according to claim 1, It is characterized in that Further comprising a mobile internal positioning device which is operably connected to each of the storage containers, and the internal positioning device is installed in each of the node facilities, wherein the mobile internal positioning device is configured to operably communicate with the internal positioning system to determine and report the position of each of the containers in each of the node facilities to track each of the storage containers in real time.

24. The supply chain system according to claim 1, It is characterized in that Further comprising a positioning unit and a wireless communication unit operably connected to each of the inter-node transport vehicles, wherein the positioning unit is configured to determine the location of each of the inter-node transport vehicles, and then determine the location of each of the storage containers transported to each of the inter-node transport vehicles, and wherein the wireless communication unit is configured to transmit the location of each of the inter-node transport vehicles and the location of any one of the storage containers to the computerized supply chain management system when the transport containers are transported between the node facilities.

25. The supply chain system according to claim 1, It is characterized in that At least one of the node facilities includes multiple environmentally different storage areas, and the facility-type configuration structure of the index storage location is distributed therein, and wherein the storage container selectively remains in the facility-type configuration structure of the index storage location in the environmentally different storage areas based on environmental data, wherein the environmental data is retrieved from the individual mobile data storage devices of the storage container and one of the computerized supply chain management systems.

26. The supply chain system according to claim 1, It is characterized in that The computerized supply chain management system further includes individual facility management subsystems of the node facilities, which are communicatively connected to each other, and wherein the individual facility management subsystems are configured to communicate with the individual mobile data storage devices of the storage containers to perform at least one of the following: reading said container data stored on a respective mobile data storage device; updating said container data stored on a respective mobile data storage device; generating commands for actions to be performed on the storage container based on at least a portion of the container data; controlling a processing device of the node facility based at least in part on the generated command; Instruct employees on how to execute; as well as The storage containers are transferred to environmentally different storage areas in a facility-type configuration structure based on environmental data read from the individual mobile data storage devices of the storage containers.

27. The supply chain system according to claim 26, It is characterized in that The computerized supply chain management system further includes an individual vehicle management subsystem for inter-node transport vehicles, and wherein the individual vehicle management subsystem is configured to communicate with the individual facility management subsystem of the node and the individual mobile data storage device of the storage container to record the bidirectional transfer of the storage container between the node facility and the inter-node transport vehicle.

28. The supply chain system according to claim 1, It is characterized in that The fleet of inter-node transport vehicles includes dedicated service transport vehicles, each of which is assigned to serve at least one of the following: specific two of the node facilities; a limited portion of the node facilities; and a limited service area including more than two of the node facilities.

29. A method for executing supply chain workflow using a transportable and continuously traceable storage container, the method include: A plurality of entities in a supply chain system are communicatively connected, the plurality of entities comprising: a network of node facilities distributed throughout a geographic region, wherein each of said node facilities includes a facility-type configuration structure indexing storage locations; a fleet of inter-node transport vehicles for transporting a plurality of inventory items contained in storage containers between said node facilities, wherein each of said inter-node transport vehicles includes a vehicle configuration structure indexing storage locations; a plurality of storage containers storable in the network of node facilities and transportable between the node facilities by the inter-node transport vehicles, wherein each of the storage containers has a standardized size and is configured to receive one or more of a plurality of the inventory items; and a computerized supply chain management system communicatively coupled to the network of nodal facilities, the fleet of inter-nodal transport vehicles, and the storage containers; assigning, by the computerized supply chain management system, a unique container identifier to each of the storage containers; storing container data and said unique container identifier for each of said containers in one or more databases of said computerized supply chain management system; storing location identifiers of the indexed storage locations of the storage containers in the facility-based configuration and the vehicle-based configuration, and location identifiers of dynamic storage locations of the storage containers, in the one or more databases of the computerized supply chain management system; and When the storage container is transferred between the indexed storage locations of the facility-type configuration structure and the vehicle-type configuration structure, the location identifier in the one or more databases of the computerized supply chain management system is updated, and at the same time, the node facility network and the fleet of inter-node transportation vehicles in the supply chain system move back and forth, wherein the node facility network, the fleet of inter-node transportation vehicles and the multiple storage containers are all operably communicated with the computerized supply chain management system and configured to provide complete traceability of one or more of the storage containers from their input into the supply chain system to order fulfillment.

30. The method according to claim 29, It is characterized in that The plurality of storage containers are further configured to hold one or more of the plurality of inventory items that are owned by one or more of the plurality of suppliers.

31. The method according to claim 29, It is characterized in that Further including receiving and processing the container data and commands from each of the storage containers, while each of the storage containers moves back and forth in forward and reverse directions in the node facility network and the fleet of transportation vehicles between the nodes of the supply chain system.

32. The method according to claim 29, It is characterized in that Further including connecting, through the computerized supply chain system, the container identifier record of the storage container to: the index storage location and the dynamic storage location of the facility-type configuration structure and the vehicle-type configuration structure; the item identifiers of the corresponding inventory items contained in the storage container in the one or more databases, and the supplier identifiers of multiple suppliers whose inventory items are contained in the storage container.

33. The method according to claim 29, It is characterized in that Further comprising generating task-type instructions through a computerized supply chain system to assist loading actions and order fulfillment actions at one or more of the node facilities based on the container data, wherein the one or more task-type instructions are configured to activate one or more machine processing devices, and the one or more machine processing devices can operate at each of the node facilities; and wherein each of the one or more machine processing devices is configured to go to any one of the storage containers through the facility-type configuration structure that indexes the storage location, and choose to leave the storage container in place or remove it, and wherein each of the one or more machine processing devices is further configured to provide a dynamic storage location to each of the storage containers, and wherein each of the one or more machine processing devices assigns a unique identifier, which is configured to indicate one of the dynamic storage locations of the storage container and allow real-time tracking of the storage container.

34. The method according to claim 29, It is characterized in that Any one or more of the storage containers include a plurality of compartments configured to store the inventory items from a plurality of suppliers in any one or more of the storage containers, wherein each of the compartments is identified by a compartment identifier and is configured to store one or more of the inventory items owned by a corresponding one of the suppliers, and wherein the computerized supply chain management system is further configured to record and connect the compartment identifier of an individual one of the compartments in the one or more databases to the item identifier of any one or more of the inventory items contained in any one or more of the storage containers, and the supplier identifier of the supplier whose inventory items are contained in any one or more of the storage containers.

35. The method according to claim 29, It is characterized in that Further including storing the unique container identifier of each of the storage containers and the inventory data associated with the inventory items contained in each of the storage containers in a mobile data storage device having a computer readable memory operably connected to each of the storage containers.

36. The method according to claim 29, It is characterized in that The container data includes at least one of the following: - Inventory catalogue; inventory item data including an item identifier, quantity, and attributes for each of said inventory items contained in each of said storage containers; destination data relating to a destination of the inventory items contained in the container; time data associated with a time frame and a level of urgency for each inventory item contained in the storage container to be transported through the supply chain system toward a destination; inventory customization data associated with an action for a value-added service to be performed on the inventory items contained in each of the storage containers; inventory management data relating to delivery scheduling, handling and / or packaging requirements for the inventory items contained in each of the storage containers; as well as Environmental data related to environmental requirements of the inventory items contained in each of the storage containers.

37. The method according to claim 29, It is characterized in that Further including: Unloading storage containers delivered from any one of the inter-node transport vehicles to any one of the node facilities, and reloading storage containers to be delivered from any one of the inter-node transport vehicles to any one of the node facilities, wherein the delivered storage containers and the delivered storage containers are exchanged in a one-to-one correspondence between any one of the inter-node transport vehicles and any one of the node facilities to allow the storage containers to flow in a reciprocal manner in both forward and reverse directions through the supply chain system; Reading a unique container identifier for each of the outgoing storage containers loaded from any one of the node facilities onto any one of the inter-node transport vehicles, and updating the one or more databases of the computerized supply chain management system with the unique container identifier to record the transfer of each of the outgoing storage containers to any one of the inter-node transport vehicles; and A unique container identifier of each of the delivered transport containers unloaded from any of the inter-node transport vehicles is read to any of the node facilities, and one or more databases are updated with the unique container identifier to record the transfer of each of the delivered storage containers to any of the node facilities.

38. The method according to claim 29, It is characterized in that Further comprising detecting movement of each of the storage containers via at least one sensor operably connected to each of the storage containers, and initiating tracking of the location of each of the storage containers via the supply chain system in response to the detected movement.

39. The method according to claim 29, It is characterized in that Further including determining and reporting the location of each of the storage containers in each of the node facilities through an internal positioning device that is operably connected to each of the storage containers, and the storage container is operably communicating with the internal positioning system installed in each of the node facilities to track each of the storage containers in real time.

40. The method according to claim 29, It is characterized in that Further including: Determining a position of each of the inter-node transport vehicles by a positioning unit operably connected to each of the inter-node transport vehicles, and then determining a position of the storage container transported in each of the inter-node transport vehicles; and When the storage containers are transported between the node facilities, the location of each of the inter-node transport vehicles and the location of each of the storage containers are transmitted to the computerized supply chain management system via a wireless communication unit operably connected to each of the inter-node transport vehicles.

41. The method according to claim 29, It is characterized in that The computerized supply chain management system further includes individual facility management subsystems of the node facilities, which are communicatively connected to each other, and wherein the individual facility management subsystems are configured to communicate with the individual mobile data storage devices of the storage containers to perform at least one of the following: reading said container data stored on a respective mobile data storage device; updating said container data stored on a respective mobile data storage device; generating commands for actions to be performed on the storage container based on at least a portion of the container data; controlling a processing device of the node facility based at least in part on the generated command; Instruct employees on how to execute; as well as The storage containers are transferred to environmentally different storage areas in a facility-type configuration structure based on environmental data read from the individual mobile data storage devices of the storage containers.

42. The method according to claim 41, It is characterized in that The computerized supply chain management system further includes an individual vehicle management subsystem for inter-node transport vehicles, and wherein the individual vehicle management subsystem is configured to communicate with the individual facility management subsystem of the node and the individual mobile data storage device of the storage container to record the bidirectional transfer of the storage container between the node facility and the inter-node transport vehicle.