Shared tray full life cycle supervision method and system

Abstract

The invention relates to the technical field of shared tray systems, in particular to a shared tray full life cycle supervision method and system, and the method comprises the steps: setting supervision nodes, and carrying out the node supervision of each supervision node, so as to obtain node data; obtaining service flows among the supervision nodes, and performing flow supervision on each service flow to obtain flow direction information; the supervision nodes at the two ends are set as an outflow party and an inflow party respectively based on the flow direction of the service flow; comparing the flow direction information with the node data of each inflow party to analyze the bearing capacity corresponding to the inflow party; judging the number of service flows between the supervision nodes and selecting a supervision scheme; selecting the service flow corresponding to the optimal outflow party according to the numerical relationship between the bearing capacity and a preset value in different supervision schemes so as to carry out or send abnormal feedback to the outflow party; and when the service flow proceeds, adjusting node data at two ends of the service flow based on the flow direction information. The method and the device have the effect of intelligently monitoring the whole life cycle of the shared tray.

Description

Technical Field

[0001] The present application relates to the technical field of shared pallet systems, and in particular to a method and system for supervising the full life cycle of shared pallets. Background Art

[0002] Pallets are important load-bearing devices for cargo transportation and are often used as horizontal platform devices for unit loads of goods and products during packaging, stacking, handling and transportation.

[0003] Originally, various manufacturing companies often purchased pallets in one go due to the large number of transportation needs. However, after purchasing the pallets, they were accompanied by a series of problems. For example, the companies needed to recycle the pallets by themselves after transportation, the pallets required additional manpower for regular maintenance and management during storage, and the companies needed to purchase them again if the pallets were damaged during use.

[0004] Therefore, in order to alleviate the above-mentioned pain points of enterprises, the majority of carrier enterprises have launched a shared pallet model, in which pallet manufacturers or supply chain managers store and manage their own pallets. When a customer needs a pallet, the pallet manager rents the pallet according to the order requirements and transports it to the customer in need. After using the rented pallet, the customer in need contacts the pallet manager to recycle the shared pallet. As a result, customers no longer need to purchase a large number of pallets, and also avoid the extra cost of managing and maintaining a large number of pallets. The pallet manager can charge a certain rental fee through the rental of shared pallets, thus achieving a win-win situation.

[0005] However, the biggest problem with the shared pallet model is the management of a large number of shared pallets and a large number of orders. Due to the high mobility of shared pallets, it takes a lot of manpower and energy to manage them throughout their life cycle. The current solution cannot manage the entire process intelligently and simply. It can only manually determine and verify the status and demand information of each order and the inventory information of each warehouse. Summary of the invention

[0006] In order to achieve intelligent supervision of the entire life cycle of a shared pallet, the present application provides a method and system for supervising the entire life cycle of a shared pallet.

[0007] In the first aspect, the present application provides a method for supervising the full life cycle of a shared pallet, which adopts the following technical solutions: A method for supervising the full life cycle of a shared pallet includes the following steps: Setting supervision nodes, and performing node supervision on each of the supervision nodes to obtain node data, wherein the supervision nodes include platforms, warehouses, transport parties, and customers; Acquire the business flows between the supervision nodes, and perform process supervision on each of the business flows to obtain flow direction information; Both ends of the service flow are used to match the supervision node, and the supervision nodes at both ends are respectively set as the outflow side and the inflow side based on the flow direction of the service flow; Comparing the flow direction information with the node data of each inflow party to analyze the corresponding carrying capacity of the inflow party; Determining the number of the service flows between the supervision nodes, and selecting a supervision scheme based on the number; In different supervision schemes, the service flow corresponding to the optimal outflow party is selected according to the numerical relationship between the carrying capacity and the preset value to perform or send abnormal feedback to the outflow party; When the service flow is in progress, the node data at both ends of the service flow are adjusted based on the flow direction information to achieve dynamic supervision.

[0008] In some of the embodiments, setting a supervisory node and performing node supervision on each supervisory node to obtain node data includes: Arrange the plurality of supervision nodes horizontally, from left to right, namely, a platform, a warehouse, a transporter, and a customer body, and there are one or more supervision nodes corresponding to the warehouse, the transporter, and the customer body; The node data corresponding to the platform at least includes total inventory, total request quantity, total dispatched order quantity, total recovered order quantity, and person in charge information; the node data corresponding to the warehouse at least includes pallet type, inventory quantity, dispatched order quantity, recovered order quantity, and manager information; the node data corresponding to the transporter at least includes transport quantity, current location, transport requirements, and driver information; the node data corresponding to the customer body at least includes requested pallet quantity, requested pallet type, recovered pallet quantity, recovered pallet type, current existing pallet quantity, current existing pallet type, and customer contact information.

[0009] In some embodiments, obtaining the service flows between the supervision nodes and performing process supervision on each of the service flows to obtain flow direction information includes the following steps: When there is business data based on the pallet between two of the supervision nodes, the business flow is generated, and each of the business flows corresponds to a change in the supervision node where the pallet is currently located; The flow information includes at least the quantity, type, time, distance, information of both parties and the current state of the business flow of the moved pallets.

[0010] In some embodiments, both ends of the service flow are used to match the supervision node, and the supervision nodes at both ends are respectively set as the outflow side and the inflow side based on the flow direction of the service flow, including: The outflow side is characterized as the supervision node where the tray is currently located, and the inflow side is characterized as the supervision node to which the tray or the corresponding data needs to be moved; Generating corresponding service flow types based on different types of supervision nodes matched by the outgoing party and the incoming party; Among them, when the outflow party is a client and the inflow party is a platform, the business flow type is a request business; when the outflow party is a platform and the inflow party is a warehouse, the business flow type is a scheduling business; when the outflow party is a warehouse and the inflow party is transportation, the business flow type is a front-end transportation business; when the outflow party is transportation and the inflow party is a client, the business flow type is a back-end transportation business; when the outflow party is a client and the inflow party is transportation, the business flow type is a front-end recovery business; when the outflow party is transportation and the inflow party is a warehouse, the business flow type is a back-end recovery business.

[0011] In some of the embodiments, the supervision nodes at both ends are respectively set as the outflow side and the inflow side based on the flow direction of the service flow, and the following steps are also included: Generate a corresponding service flow type based on the supervision nodes of the same type matched by the outgoing party and the incoming party; When both the outflow party and the inflow party are warehouses, the business flow type is warehouse allocation business; when both the outflow party and the inflow party are customers, the business flow type is customer allocation business; When the types of the supervision nodes at both ends of the business flow are the same, the outflow party or the inflow party generates an additional transport business flow whose sending object is the transport party and an additional request business flow whose sending object is the platform.

[0012] In some of the embodiments, comparing the flow direction information with the node data of each of the inflow parties to analyze the corresponding carrying capacity of the inflow party includes the following steps: Verify whether the supervision nodes at both ends of the service flow match the information of both parties and whether the current state of the service flow is a response state. If any result is no, the carrying capacity is 0; Determine whether the node information of the inflow party including a single monitoring node satisfies the quantity, the type and the time in the flow direction information; If satisfied, the bearing capacity is set to 1; Analyzing the node information to satisfy the quantity, type and time in the flow direction information, and generating a first coefficient based on a numerical relationship between the margin value and a preset empirical value; analyzing a transportation distance between the inflow party and the outflow party to generate a second coefficient; A first additional value is calculated based on the first coefficient and / or the second coefficient, and the bearing capacity is adjusted based on the first additional value, wherein the first additional value is less than 1.

[0013] In some of the embodiments, comparing the flow direction information with the node data of each inflow party to analyze the corresponding carrying capacity of the inflow party further includes the following steps: If the node information of the inflow party including a single object does not satisfy the quantity and the type in the flow direction information, select a plurality of monitoring nodes of the same type in order as one inflow party, and numerically accumulate the node information of the plurality of monitoring nodes to obtain a node accumulation value; Determine whether the node cumulative value of the inflow party satisfies the quantity, the type and the time in the flow direction information; If satisfied, the bearing capacity is set to 1; generating a third coefficient based on the number of the monitoring nodes in the inflow side; generating a fourth coefficient based on a total transportation distance between each of the monitoring nodes in the inflow side and the outflow side; A second additional value is calculated based on the third coefficient and / or the fourth coefficient, and the bearing capacity is adjusted based on the second additional value, wherein the second additional value is less than 1.

[0014] In some embodiments, determining the number of the service flows between the supervision nodes of the same type and selecting a supervision scheme based on the number comprises the following steps: When there are multiple service flows between the same type of supervision nodes, the supervision scheme is specifically a selection of optimal supervision scheme; When there is only one service flow between the supervision nodes of the same type, the supervision scheme is specifically a feedback supervision scheme.

[0015] In some of the embodiments, selecting the service flow corresponding to the optimal outflow party according to the numerical relationship between the carrying capacity and the preset value in different supervision schemes to perform or send abnormal feedback to the outflow party includes the following steps: In the above-mentioned optimal supervision scheme, When the carrying capacity is greater than or equal to the preset value, the service flow corresponding to the inflow party with the highest carrying capacity is selected and all remaining service flows are cancelled; When the carrying capacity does not exist and is greater than or equal to the preset value, the inflow parties that partially meet the flow information are selected for processing, and the content that does not meet the flow information is marked and fed back to the platform; In the feedback supervision scheme, If the carrying capacity is not less than a preset value, the service flow is performed; If the carrying capacity is less than a preset value, supply exception information is generated and sent to the outflow party corresponding to the business flow.

[0016] In the second aspect, the present application provides a shared pallet full life cycle supervision system, which adopts the following technical solutions: A shared pallet full life cycle supervision system is used to implement the above method.

[0017] The technical solution provided by the embodiments of the present application has the following technical effects: The entire life cycle of shared pallets is divided into static points and dynamic lines for separate supervision. The static points are the participants in the life cycle, and the dynamic lines are the business interactions between the participants. At the same time, the static pallet status of each participant is bidirectionally verified through the business flow-related data corresponding to the business interaction to determine whether the business recipient of the business flow is capable of responding to and completing the tasks corresponding to the business flow. At the same time, the appropriate supervision scheme is selected based on the number of business flows between the supervision nodes to implement the corresponding supervision actions through the judgment results. The current static data of the supervision node is adjusted through the actions of the business flow. In this way, the complex pallet rental process is decomposed into static and dynamic parts, and the static part is verified and adjusted through the dynamic part. The management party no longer needs to manually supervise and correct a large amount of pallet business data. The system can actively and intelligently supervise the feasibility and data value automatically according to dynamic business actions. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 This is a schematic diagram of the steps of a method for supervising the entire life cycle of a shared pallet provided in this embodiment. DETAILED DESCRIPTION

[0019] To more clearly understand the purpose, technical solutions and advantages of the present application, the present application is described and illustrated below in conjunction with the accompanying drawings and embodiments. However, it should be understood by those of ordinary skill in the art that the present application can be implemented without these details. In some cases, in order to avoid unnecessary descriptions that make various aspects of the present application obscure, well-known methods, processes, systems, components and / or circuits that have been described at a higher level will not be described in detail. For those of ordinary skill in the art, it is obvious that various changes can be made to the embodiments disclosed in the present application, and without departing from the principles and scope of the present application, the general principles defined in the present application can be applied to other embodiments and application scenarios. Therefore, the present application is not limited to the embodiments shown, but conforms to the broadest scope consistent with the scope claimed for protection of the present application.

[0020] It should be noted that the description of these embodiments is used to help understand the present invention, but does not constitute a limitation of the present invention. In addition, the technical features involved in each embodiment of the present invention described below can be combined with each other as long as there is no conflict between them.

[0021] In the description of this application, "several" means one or more, "more" means more than two, "greater than", "less than", "exceed", etc. are understood to exclude the number itself, and "above", "below", "within", etc. are understood to include the number itself. If there is a description of "first" or "second", it is only used to distinguish the technical features, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features or implicitly indicating the order of the indicated technical features.

[0022] In the description of the present application, the description with reference to the terms "one embodiment", "some embodiments", "illustrative embodiments", "examples", "specific examples", or "some examples" means that the specific features, structures, materials, or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in any one or more embodiments or examples.

[0023] like Figure 1 As shown, the embodiment of the present application discloses a method for supervising the full life cycle of a shared pallet, comprising the following steps: S100, setting supervision nodes, and performing node supervision on each supervision node to obtain node data.

[0024] Supervision nodes include platforms, warehouses, transporters, and customers.

[0025] The platform is a supplier management platform. When obtaining shared pallet demand information from each customer, it is used to allocate and schedule shared pallets stored in the warehouse, and it also comprehensively records and coordinates the data of the entire life cycle of shared pallets.

[0026] The warehouse is a number of shared pallet storage units set up under the platform. After being dispatched by the platform, it selects the corresponding type and quantity of shared pallets for output according to the dispatch requirements.

[0027] The transport parties include transport vehicles of various freight platforms and logistics platforms that cooperate with the platform. The warehouse needs to notify the corresponding transport vehicles to transport the shared platform from the warehouse to the customer. It is also used to recover the pallets from the customer and transport them to the warehouse after the customer has used them.

[0028] The customer entity refers to a customer group that needs to use a shared pallet. The customer group sends a rental request for a shared pallet to the platform and waits for the platform to allocate the shared pallet.

[0029] Several important participants in the entire process of shared pallet leasing are independently set as nodes that need to be supervised, and the node data containing each node's own characteristics is acquired and supervised, so as to first supervise the static node information throughout the entire life cycle.

[0030] S200, obtaining the business flows between the supervision nodes, and performing process supervision on each business flow to obtain flow direction information.

[0031] A business flow is set between monitoring nodes that have direct business dealings with the shared pallet. As long as the business flow exists, it is characterized by the interactive business corresponding to the business flow, and the state of the shared pallet will change to a certain extent.

[0032] Different from the supervision node, the business flow is the dynamic interaction between nodes. By supervising the business flow, we can mine the flow information contained in the dynamic interaction. The flow information constitutes the action supervision result of this step of business operation.

[0033] S300, both ends of the business flow are used to match the supervision nodes, and the supervision nodes at both ends are set as the outflow side and the inflow side respectively based on the flow direction of the business flow.

[0034] Both ends of the service flow are used to match the supervision nodes, that is, each service flow is between two supervision nodes.

[0035] At the same time, business information must have a sending party and a receiving party, so the two ends of the corresponding business flow correspond to the outflow party and the inflow party respectively. The outflow party is represented by a business behavior for the shared pallet sent by the supervision node, and the inflow party is represented by a business behavior for the shared pallet received by the supervision node, and the direction of the business flow is from the outflow party to the inflow party.

[0036] For example, when the platform sends a dispatch order to a warehouse based on a customer's request, the dispatch order is a business flow. The essence of the dispatch order is to change the state of the shared pallet currently in the warehouse. The outflow party of the business flow is the platform, and the inflow party is the warehouse.

[0037] S400, comparing the flow direction information with the node data of each inflow party to analyze the corresponding carrying capacity of the inflow party.

[0038] Each business flow has specific flow direction information based on different business data, including the quantity and type of business actions corresponding to the shared pallet. The flow direction information corresponding to the business flow is then analyzed and compared with the node data of the inflow party of the business flow to determine the carrying capacity of the inflow party for the business.

[0039] The carrying capacity is characterized by the response and bearing capacity of the incoming party to the data required by the business flow. When the carrying capacity is insufficient, it is considered that the incoming party cannot achieve the results required by the business flow.

[0040] S500, determining the number of service flows between supervision nodes, and selecting a supervision scheme based on the number.

[0041] After calculating the inbound carrying capacity of each service flow, it is also necessary to determine the number of service flows between the same type of supervision nodes.

[0042] Because there may be multiple objects of some supervision nodes, such as warehouses and transporters, there may be multiple business flows between the platform and the warehouse, such as the business flow between the platform and warehouse a, the business flow between the platform and warehouse b, the business flow between the platform and warehouse c, etc.

[0043] At the same time, there may be only one business flow between the supervision nodes. For example, when a customer sends a request for a pallet to the platform, there is only one business flow between the customer and the platform.

[0044] Then different supervision schemes need to be selected according to the number of business flows between one type of supervision node and another type of supervision node. S600, selecting the service flow corresponding to the best outflow party in different supervision schemes according to the numerical relationship between the carrying capacity and the preset value to perform or send abnormal feedback to the outflow party.

[0045] The same part in different regulatory schemes is that they all require numerical analysis of the relationship between the carrying capacity and the preset value and obtaining the analysis results.

[0046] The different parts are the effects that different regulatory schemes want to achieve through analysis results.

[0047] When there is only one business flow between the supervision nodes, it is only necessary to determine whether the business flow can be implemented based on the analysis results. Correspondingly, when the business flow cannot be implemented, a feedback exception message is sent to the outflow party to inform the outflow party that the business cannot be carried out, or when the business flow can be implemented, the outflow party can be directly made to respond to the flow direction information of the business flow to take action.

[0048] When there are multiple business flows between supervision nodes, in addition to determining whether the business flow can be realized based on the analysis results, it is more important to select an optimal business flow among several business flows to perform corresponding business actions. For example, if there are multiple warehouses that can provide customers with corresponding quantities and types of pallets, then how to select the best warehouse among these multiple options to meet, for example, the shortest transportation time, minimum surplus, etc. Therefore, in this type of supervision scheme, the optimal business flow is selected based on the analysis results.

[0049] S700, when the service flow is in progress, the node data at both ends of the service flow are adjusted based on the flow direction information to achieve dynamic supervision.

[0050] When a business flow can proceed after the carrying capacity is determined, it is characterized by a state change of the shared pallet. At this time, the current node data of the incoming and outgoing parties are adjusted according to the flow direction information of the business flow to achieve dynamic supervision of the node information.

[0051] Through the above steps, the entire life cycle based on shared pallets is divided into static points and dynamic lines for separate supervision. The static points are the participants in the life cycle, and the dynamic lines are the business interactions between the participants. At the same time, the static pallet status of each participant is bidirectionally verified through the business flow-related data corresponding to the business interaction to determine whether the business recipient of the business flow is capable of responding to and completing the tasks corresponding to the business flow. At the same time, the appropriate supervision scheme is selected in combination with the number of business flows between the supervision nodes to implement the corresponding supervision actions through the judgment results. The current static data of the supervision node is adjusted through the actions of the business flow. In this way, the complex pallet rental process is decomposed into static and dynamic parts, and the static part is verified and adjusted through the dynamic part. The management party no longer needs to manually supervise and correct a large amount of pallet business data. The system can actively and intelligently supervise the feasibility and data value automatically according to dynamic business actions.

[0052] In some other embodiments, setting a supervisory node and performing node supervision on each supervisory node to obtain node data includes: Arrange several supervision nodes horizontally, from left to right, namely platform, warehouse, transporter, and customer body. There are one or more supervision nodes corresponding to the warehouse, transporter, and customer body.

[0053] According to the order of management convenience and browsing, multiple supervision nodes are sorted according to different objects, preferably from left to right. Generally, the leasing of shared pallets starts with the request of the customer body, and flows through the platform, warehouse, transporter and customer body through the business flow.

[0054] At the same time, depending on the actual situation, there may be one or more supervision nodes of each type. There is generally only one supervision node corresponding to the platform, while there may be one or more warehouses, transporters, and customers depending on the actual situation.

[0055] The node data corresponding to the platform includes at least total inventory, total request quantity, total dispatch order quantity, total recycling order quantity, and person in charge information. The total inventory refers to the inventory quantity and inventory type of pallets in all subordinate warehouses, the total request quantity is represented by the number of request orders issued by all current customers, the total dispatch order quantity is represented by the total amount of all dispatch orders issued to each warehouse, and the total recycling order quantity is represented by the total number of recycling orders accepted by all subordinate warehouses. The person in charge information includes the name, phone number, email address, etc. of the manager.

[0056] The node data corresponding to the warehouse includes at least the type of pallet, inventory, dispatch order quantity, recycling order quantity, and manager information. The type of pallet is represented by the type of pallets in the inventory of each warehouse, the inventory is represented by the number of inventory pallets in each warehouse, the dispatch order quantity is represented by the number of dispatch orders sent by the platform that each warehouse currently obtains and responds to, and the recycling order quantity is represented by the number of recycling orders sent by customers that each warehouse currently obtains. The manager information includes the name, phone number, and email address of the person in charge of each warehouse site.

[0057] The node data corresponding to the transporter includes at least the transport volume, current location, transport requirements, and driver information. The transport volume is represented by the quantity / weight that each transport vehicle can carry, the current location is represented by the current location of the transport vehicle obtained through the Internet of Things module, and the transport requirements are represented by the requirements that each transport vehicle can transport, such as what type of pallets can be transported, the maximum number / weight of pallets that can be transported, etc. The driver information is represented by the driver's name, phone number, etc.

[0058] The node data corresponding to the customer body at least includes the requested pallet quantity, the requested pallet type, the returned pallet quantity, the returned pallet type, the current existing pallet quantity, the current existing pallet type, and customer contact information.

[0059] In some other embodiments, obtaining the service flows between the supervision nodes and performing process supervision on each service flow to obtain flow direction information includes the following steps: S210, when there is business data based on the pallet between two supervision nodes, a business flow is generated, and each business flow corresponds to the change of the supervision node where the pallet is currently located.

[0060] As long as there is business regarding the status change of the pallet between the two supervision nodes, there is a business flow between the two supervision nodes. That is to say, as long as there is a business flow, the status of the pallet needs to be changed between the two supervision nodes according to the business flow. The changed status here includes changes in the physical status of the pallet, such as transportation and recycling, and changes in the virtual status of the pallet, such as pallet requests, pallet scheduling, and pallet allocation.

[0061] The flow information includes at least the number, type, time, distance, information of both parties and the current status of the business flow of the moving pallets.

[0062] The quantity includes the number of pallets that need to change their status, the type includes the type of pallets that need to change their status, the time is represented by the time required for the pallet's status to change from the beginning to the end, the distance is represented by the moving distance required for the pallet to change from one state to another, the information of both parties is represented by the basic information of the corresponding supervision nodes at both ends of the business flow, and the current state of the business flow is represented by the status of the business corresponding to the business flow, such as unfinished, completed, in progress, etc.

[0063] Meanwhile, the above-mentioned flow direction information is represented as relatively general necessary data. After the type of the business flow is subsequently obtained, the specific content represented by the above-mentioned flow direction information will change accordingly according to the different types of the business flow.

[0064] In other embodiments, both ends of the service flow are used to match the supervision node, and the supervision nodes at both ends are respectively set as the outflow side and the inflow side based on the flow direction of the service flow, including: The outflow side is characterized by the supervision node where the pallet is currently located, and the inflow side is characterized by the supervision node to which the pallet or the corresponding data needs to be moved.

[0065] The corresponding service flow types are generated based on the different types of supervision nodes matched by the outgoing and incoming parties.

[0066] in, When the outflow party is the customer and the inflow party is the platform, the business flow type is request business. The request business is represented by the customer sending a pallet request form to the platform. The pallet request includes the requested pallet quantity, requested pallet type, requested pallet demand time, the requesting party's company information, and the person in charge information. At this time, the business flow is in the state of request to be completed.

[0067] When the outflow party is the platform and the inflow party is the warehouse, the business flow type is scheduling business. The scheduling business is characterized by the platform selecting the corresponding warehouse according to the requirements of the pallet request form and generating a scheduling form to schedule the warehouse to prepare the required pallets. The scheduling form includes the number of pallets to be scheduled, the type of pallets to be scheduled, the preparation time of the scheduled pallets, the information of the administrator who issued the scheduling form, and the warehouse information. At this time, the business flow is in a state of scheduling to be determined, and the business flow status in the request business is changed to request completed.

[0068] When the outflow party is a warehouse and the inflow party is transportation, the business flow type is the front-end transportation business. The front-end transportation business is characterized by the warehouse issuing a transportation request to find the corresponding transportation vehicle to go to the warehouse to collect the scheduled pallets. The transportation request at this time includes the number of pallets to be loaded, the type of pallets to be loaded, the specified loading completion time, the information of the person in charge of issuing the transportation request, and the warehouse location. At this time, the business flow is in the state of front-end transportation to be determined, and the business flow status in the scheduling business is changed to scheduling completed.

[0069] When the outflow party is transportation and the inflow party is the client, the business flow type is the back-end transportation business. The back-end transportation business is characterized by the transportation vehicle sending a transportation notification to the client that issued the request to inform that the pallet is being transported to the target location. The transportation notification at this time includes the number of pallets currently loaded, the type of pallets currently loaded, the time to complete the transportation, the driver information of the transportation, and the current vehicle location. At this time, the business flow is in the state of back-end transportation to be determined, and the business flow status in the front-end transportation business is changed to the front-end transportation completed.

[0070] When the outflow party is the customer and the inflow party is the transport, the business flow type is the front-end recycling business. The front-end recycling business is characterized by the customer issuing a recycling request to find the corresponding transport vehicle to go to the customer's location to recycle the pallets. The recycling request at this time includes the number of pallets to be recycled, the type of pallets to be recycled, the specified recycling completion time, the information of the person in charge of issuing the recycling request, and the customer's location. At this time, the business flow is in a state of front-end recycling to be determined.

[0071] When the outflow party is transportation and the inflow party is a warehouse, the business flow type is the back-end recycling business. The back-end recycling business is characterized by the transportation vehicle issuing a recycling notice to inform the warehouse associated with the recycling order. The recycling notice at this time includes the number of pallets currently loaded, the type of pallets currently loaded, the time to complete the transportation, the driver information of the transportation, and the current vehicle location. At this time, the business flow is in the state of back-end recycling to be determined, and the business flow status in the front-end recycling business is changed to front-end recycling completed.

[0072] In some other embodiments, the supervision nodes at both ends are respectively set as the outflow side and the inflow side based on the flow direction of the service flow, and the following steps are also included: S310: Generate a corresponding service flow type based on the supervision nodes of the same type matched by the outgoing party and the incoming party.

[0073] At the same time, both endpoints of the business flow can also be matched with the same type of supervision nodes, such as when both the outflow party and the inflow party are warehouses or when both the outflow party and the inflow party are customers. This situation may occur when shared pallets need to be allocated to each other or when there is business cooperation between multiple customers. For example, after historical scheduling, warehouse a has insufficient inventory or a large number of damaged pallets. In order to avoid the situation where the warehouse cannot match the scheduling requirements due to insufficient inventory of pallets, pallets in other warehouses with more inventory can be allocated to warehouse a with the permission of the platform; for example, a company has two entities, b and c. When entity b rents and uses a pallet, entity c also has the same pallet request. At this time, if the pallets are recovered from entity b to the warehouse and then transported to entity c according to the request of entity c, it will take a lot of time and transportation costs. In this case, the transporter can directly transport the pallets recovered from entity b to entity c with the permission of the platform, eliminating the intermediate in-and-out operations in the warehouse.

[0074] Among them, when the outflow party and the inflow party are both warehouses, the business flow type is warehouse allocation business; when the outflow party and the inflow party are both customers, the business flow type is customer allocation business.

[0075] When the types of supervision nodes at both ends of the business flow are the same, the outflow party or the inflow party generates an additional transportation business flow with the transport party as the sending object and an additional request business flow with the platform as the sending object. At the same time, when the business flow is realized between the same type of supervision nodes, the platform needs to confirm the allocation business. Therefore, before the allocation business flow is carried out, an additional request business flow needs to be generated and sent to the platform. The flow information in the additional request business flow includes the basic information of both parties, the number of allocated pallets, the type of allocated pallets, the time required for allocation, etc. At the same time, it is also necessary to send an additional additional transportation business flow to the transport vehicles carrying the transportation work. The flow information of this business flow includes the number of pallets to be transported, the type of pallets to be transported, the required time for transportation, the contact information of both parties, the location information of both parties, etc.

[0076] In some other embodiments, comparing the flow direction information with the node data of each inflow party to analyze the corresponding carrying capacity of the inflow party includes the following steps: S410, verify whether the supervision nodes at both ends of the service flow match the information of both parties and whether the current state of the service flow is a response state. If any result is no, the carrying capacity is 0.

[0077] First, it is necessary to verify whether the node information of the supervision nodes at both ends of the business flow matches the information of both parties in the flow information. This step is to avoid mismatching of business flows, such as the information of the transport vehicle in the transport request is different from the transport vehicle associated with the business.

[0078] The next step is to verify whether the current business flow is in a responsive state. The responsive state means that both parties of the business flow have received and confirmed the business corresponding to the business flow. For example, if some warehouses are closed or some transport vehicles are out of service, the corresponding monitoring nodes will not be able to respond to the business flow and are therefore in an unresponsive state.

[0079] As long as one of the above two verifications has a negative result, the service flow cannot be carried out and the service flow is invalid, so the bearing capacity is set to 0, indicating that the receiving object based on the service flow cannot carry out the service.

[0080] S411, determining whether the node information of the inflow party including a single monitoring node satisfies the quantity, type and time in the flow direction information.

[0081] S412: If satisfied, the bearing capacity is set to 1.

[0082] When the above verifications are passed, it is determined whether the node information corresponding to the inflow party of the monitoring node including a platform, a warehouse, a transportation or a customer entity can meet the requirements of quantity, type and time in the flow information.

[0083] For example, if the inflow party is a warehouse, there are 10 pallets in the current warehouse, including 7 FDY pallets and 3 POY pallets. Based on the current personnel and the dispatch order currently being processed, the warehouse predicts that it will take 6 minutes to dispatch a pallet. Then, when the warehouse obtains a dispatch order, it compares the number of pallets, pallet types and dispatch required time required in the dispatch order with the above information. If the requirement is to dispatch 4 FDY pallets within 30 minutes, then it is obvious that the node information of the warehouse can meet the requirements of the dispatch order, so the carrying capacity is set to 1 at this time. However, when the requirement is to dispatch 4 POY pallets within 30 minutes, it cannot be met.

[0084] When the carrying capacity is 1, it corresponds to the basic value that can meet the needs of the business flow. When each monitoring node is used as an inflow point for comparison and analysis with the business flow, the basic value needs to be further accurately revised.

[0085] S413, analyzing the residual value after the node information satisfies the quantity, type and time in the flow direction information, and generating a first coefficient based on a numerical relationship between the residual value and a preset empirical value.

[0086] First, ignore the part of the node information that meets the flow information, and calculate the remaining quantity, type and time. The larger the surplus value, for example, after some pallets are dispatched according to scheduling needs, the more pallets and types of pallets in stock, or the faster the scheduling task is completed, which indicates that the warehouse has a higher probability of meeting the next scheduling demand or responding to the next scheduling demand faster, then the more suitable this warehouse is for the business flow.

[0087] Then, by comparing the margin value with the preset experience value, a first coefficient of the corresponding numerical relationship can be generated, and the larger the margin value, the larger the first coefficient. The experience value represents the ideal margin under the standard scheduling scenario inferred by the system based on the experience of historical data.

[0088] S414, analyzing the transportation distance between the inflow party and the outflow party to generate a second coefficient.

[0089] The transportation distance between the incoming and outgoing parties specifically reflects the completion speed of the business flow where the shared pallet is located. The faster the business flow is completed, the faster the two ends of the business flow can proceed to the next business flow. Therefore, the smaller the transportation distance, the larger the second coefficient.

[0090] It should be noted that the assessment of the second coefficient only corresponds to business flows based on physical pallets such as scheduling, transportation, and recycling.

[0091] S415: Calculate a first additional value based on the first coefficient and / or the second coefficient, and adjust the bearing capacity based on the first additional value, wherein the first additional value is less than 1.

[0092] According to the type of business flow, the first coefficient and / or the second coefficient are selected for weighted calculation to calculate the first additional value. The larger the first coefficient and the second coefficient, the larger the first additional value. Finally, the first additional value is added to the carrying capacity to obtain a more accurate carrying capacity value.

[0093] In some other embodiments, comparing the flow direction information with the node data of each inflow party to analyze the corresponding carrying capacity of the inflow party further includes the following steps: S420, if the node information of the inflow party including a single object does not satisfy the quantity and type in the flow direction information, select multiple monitoring nodes of the same type in sequence as an inflow party, and numerically accumulate the node information of several monitoring nodes to obtain a node accumulation value.

[0094] If the node information of all inflows containing a single object cannot meet the quantity and type in the flow information, this means that the objects corresponding to all inflows cannot independently realize the business requirements corresponding to the business flow, such as a warehouse needs to transport 40 pallets to a customer, but each transport vehicle can only transport a maximum of 20 pallets. At this time, in order to match the business flow, the inflow can be generated by combining multiple objects of the same type, such as using three transport vehicles as the same inflow.

[0095] At this time, the node information of multiple objects is accumulated to obtain the node cumulative value, such as the total number of pallets that can be transported by three freight vehicles, the total types of pallets that can be transported, and the total transportation time required for transportation.

[0096] S421, determining whether the node cumulative value of the inflow party satisfies the quantity, type and time in the flow direction information.

[0097] S422: If satisfied, the bearing capacity is set to 1.

[0098] Compare the node cumulative value with the quantity, type and time in the flow information. If the node cumulative value can meet the requirements of the flow information, then the inflow composed of these objects also corresponds to a carrying capacity of 1. In this way, the requirements of the business flow can be achieved by combining multiple transport vehicles for transportation.

[0099] At the same time, after combining multiple objects, there may be multiple combinations that can satisfy the business flow. At this time, the carrying capacity needs to be further adjusted to facilitate the subsequent system to select the most preferred combination.

[0100] S423: Generate a third coefficient based on the number of monitoring nodes in the inflow side.

[0101] First, determine the number of monitoring nodes in the inflow party. The fewer the number of monitoring nodes, the fewer objects are required to participate in implementing the business content of the business flow. As the number of participating objects increases, the time and manpower costs required will increase. Therefore, under the condition of meeting the requirements, the fewer the number of participating objects, the better the selection, and the larger the corresponding third coefficient.

[0102] S424: Generate a fourth coefficient based on the total transportation distance between each monitoring node in the inflow side and the outflow side.

[0103] When judging whether the incoming party needs to satisfy the business flow, the total transportation distance for transporting pallets between multiple objects in the incoming party and the outgoing party is smaller, which indicates that the business flow composed of multiple monitoring nodes can be completed sooner, and multiple monitoring nodes can enter the selection or action of the next business flow sooner. Therefore, the shorter the total transportation distance is, the larger the fourth coefficient is.

[0104] It should be noted that the selection and determination of the fourth coefficient also only applies to the business flows of scheduling, transportation, and recycling.

[0105] S425, calculating a second additional value based on the third coefficient and / or the fourth coefficient, and adjusting the bearing capacity based on the second additional value, wherein the second additional value is less than 1.

[0106] The calculation process of the first additional value is the same as that of the third coefficient and the fourth coefficient. The second additional value is obtained by weighted calculation, and the second additional value is added to the bearing capacity to obtain a more accurate bearing capacity value.

[0107] In some other embodiments, determining the number of service flows between supervision nodes of the same type and selecting a supervision scheme based on the number includes the following steps: S510: When there are multiple service flows between the same type of supervision nodes, the supervision scheme is specifically a selection of optimal supervision scheme.

[0108] In the preferred supervision scheme, the supervision actions required include determining whether there is a feasible business flow among multiple business flows, selecting the optimal business flow among several feasible business flows, and finally supervising the completion of the optimal business flow by the monitoring node.

[0109] S520: When there is only one service flow between the same type of supervision nodes, the supervision scheme is specifically a feedback supervision scheme.

[0110] In the feedback supervision scheme, the supervision actions required include determining whether the only business flow can be implemented, and feeding back corresponding abnormal information when it cannot be implemented, or supervising the completion of the business flow of the monitoring node when it can be implemented.

[0111] In other embodiments, selecting the service flow corresponding to the optimal outflow party according to the numerical relationship between the carrying capacity and the preset value in different supervision schemes to perform or send abnormal feedback to the outflow party includes the following steps: In the optimal regulatory scheme, S610: When there is a carrying capacity greater than or equal to a preset value, select the service flow corresponding to the inflow party with the highest carrying capacity and cancel all remaining service flows.

[0112] When there are multiple business flows between an outflow party of one type and an outflow party of another type, if the inflow party corresponding to these business flows has a carrying capacity greater than or equal to a preset value, it is considered that there is an inflow party that can meet the business flow requirements. At this time, the business flow corresponding to the inflow party with the highest carrying capacity is selected and all other business flows between the outflow party and the inflow party are canceled.

[0113] S620: When there is no carrying capacity greater than or equal to the preset value, some inflow parties that meet the flow information will be selected for processing, and the content that does not meet the flow information will be marked and fed back to the platform.

[0114] If there is no carrying capacity greater than or equal to the preset value, it means that there is no inflow party between a type of outflow party and a type of inflow party that can meet the business flow requirements. In this case, the business flow corresponding to the inflow party that partially meets the flow information is prioritized so that the inflow party responds to the matching part first. The other unsatisfied parts are marked and sent to the platform. The platform chooses to let the inflow party that is partially meeting the flow information wait or select other suitable inflow parties to complete the business requirements that were not met before, depending on the specific situation.

[0115] In the feedback supervision scheme, S630: If the carrying capacity is not less than the preset value, the service flow is performed.

[0116] S640: If the carrying capacity is less than the preset value, supply exception information is generated and sent to the outflow party corresponding to the business flow.

[0117] In the feedback supervision scheme, if the carrying capacity is not less than the preset value, the business corresponding to the business flow will be carried out and the node information at both ends of the process and after the process will be supervised. If the carrying capacity is less than the preset value, it means that the only incoming party cannot implement the actions required by the business flow. At this time, supply exception information is generated and sent to the outgoing party to inform the outgoing party that the business needs of the outgoing party cannot be met at present. At the same time, the supply exception information can also be sent to the platform and wait for subsequent instructions from the platform.

[0118] Among them, the above-mentioned preset values ​​are all 1 in the embodiments of the present application.

[0119] The present application also discloses a shared pallet full life cycle monitoring system for implementing the above method.

[0120] The implementation principle is: The entire life cycle of shared pallets is divided into static points and dynamic lines for separate supervision. The static points are the participants in the life cycle, and the dynamic lines are the business interactions between the participants. At the same time, the static pallet status of each participant is bidirectionally verified through the business flow-related data corresponding to the business interaction to determine whether the business recipient of the business flow is capable of responding to and completing the tasks corresponding to the business flow. At the same time, the appropriate supervision scheme is selected based on the number of business flows between the supervision nodes to implement the corresponding supervision actions through the judgment results. The current static data of the supervision node is adjusted through the actions of the business flow. In this way, the complex pallet rental process is decomposed into static and dynamic parts, and the static part is verified and adjusted through the dynamic part. The management party no longer needs to manually supervise and correct a large amount of pallet business data. The system can actively and intelligently supervise the feasibility and data value automatically according to dynamic business actions.

[0121] It should be understood that although the steps in the flowchart of the accompanying drawings are shown in sequence according to the instructions of the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise clearly stated in this document, the execution of these steps is not strictly limited in order and can be performed in other orders.

[0122] The above are all preferred embodiments of the present application, and the protection scope of the present application is not limited thereto. Therefore, any equivalent changes made according to the structure, shape, and principle of the present application should be included in the protection scope of the present application.

Claims

1. A method for supervising the full life cycle of a shared pallet, characterized in that: The following steps are involved: Setting supervision nodes, and performing node supervision on each of the supervision nodes to obtain node data, wherein the supervision nodes include platforms, warehouses, transport parties, and customers; Acquire the business flows between the supervision nodes, and perform process supervision on each of the business flows to obtain flow direction information; Both ends of the service flow are used to match the supervision node, and the supervision nodes at both ends are respectively set as the outflow side and the inflow side based on the flow direction of the service flow; Comparing the flow direction information with the node data of each inflow party to analyze the corresponding carrying capacity of the inflow party; Determining the number of the service flows between the supervision nodes, and selecting a supervision scheme based on the number; In different supervision schemes, the service flow corresponding to the optimal outflow party is selected according to the numerical relationship between the carrying capacity and the preset value to perform or send abnormal feedback to the outflow party; When the service flow is in progress, the node data at both ends of the service flow are adjusted based on the flow direction information to achieve dynamic supervision.

2. The method for monitoring the full life cycle of a shared pallet according to claim 1 is characterized in that: Setting supervision nodes, and performing node supervision on each of the supervision nodes to obtain node data, including: Arrange the plurality of supervision nodes horizontally, from left to right, namely, a platform, a warehouse, a transporter, and a customer body, and there are one or more supervision nodes corresponding to the warehouse, the transporter, and the customer body; The node data corresponding to the platform at least includes total inventory, total request quantity, total dispatched order quantity, total recovered order quantity, and person in charge information; the node data corresponding to the warehouse at least includes pallet type, inventory quantity, dispatched order quantity, recovered order quantity, and manager information; the node data corresponding to the transporter at least includes transport quantity, current location, transport requirements, and driver information; the node data corresponding to the customer body at least includes requested pallet quantity, requested pallet type, recovered pallet quantity, recovered pallet type, current existing pallet quantity, current existing pallet type, and customer contact information.

3. The method for monitoring the full life cycle of a shared pallet according to claim 2 is characterized in that: Acquiring the service flows between the supervision nodes and performing process supervision on each of the service flows to obtain flow direction information includes the following steps: When there is business data based on the pallet between two of the supervision nodes, the business flow is generated, and each of the business flows corresponds to a change in the supervision node where the pallet is currently located; The flow information includes at least the quantity, type, time, distance, information of both parties and the current state of the business flow of the moved pallets.

4. The method for monitoring the full life cycle of a shared pallet according to claim 3 is characterized in that: Both ends of the service flow are used to match the supervision node, and the supervision nodes at both ends are respectively set as the outflow side and the inflow side based on the flow direction of the service flow, including: The outflow side is characterized as the supervision node where the tray is currently located, and the inflow side is characterized as the supervision node to which the tray or the corresponding data needs to be moved; Generating corresponding service flow types based on different types of supervision nodes matched by the outgoing party and the incoming party; Among them, when the outflow party is a client and the inflow party is a platform, the business flow type is a request business; when the outflow party is a platform and the inflow party is a warehouse, the business flow type is a scheduling business; when the outflow party is a warehouse and the inflow party is transportation, the business flow type is a front-end transportation business; when the outflow party is transportation and the inflow party is a client, the business flow type is a back-end transportation business; when the outflow party is a client and the inflow party is transportation, the business flow type is a front-end recovery business; when the outflow party is transportation and the inflow party is a warehouse, the business flow type is a back-end recovery business.

5. The method for monitoring the full life cycle of a shared pallet according to claim 3 is characterized in that: The method further includes setting the supervision nodes at both ends as the outflow side and the inflow side respectively based on the flow direction of the service flow, and further comprising the following steps: Generate a corresponding service flow type based on the supervision nodes of the same type matched by the outgoing party and the incoming party; When both the outflow party and the inflow party are warehouses, the business flow type is warehouse allocation business; when both the outflow party and the inflow party are customers, the business flow type is customer allocation business; When the types of the supervision nodes at both ends of the business flow are the same, the outflow party or the inflow party generates an additional transport business flow whose sending object is the transport party and an additional request business flow whose sending object is the platform.

6. The method for monitoring the full life cycle of a shared pallet according to claim 3 is characterized in that: Comparing the flow direction information with the node data of each inflow party to analyze the corresponding carrying capacity of the inflow party includes the following steps: Verify whether the supervision nodes at both ends of the service flow match the information of both parties and whether the current state of the service flow is a response state. If any result is no, the carrying capacity is 0; Determine whether the node information of the inflow party including a single monitoring node satisfies the quantity, the type and the time in the flow direction information; If satisfied, the bearing capacity is set to 1; Analyzing the node information to satisfy the quantity, type and time in the flow direction information, and generating a first coefficient based on a numerical relationship between the margin value and a preset empirical value; analyzing a transportation distance between the inflow party and the outflow party to generate a second coefficient; A first additional value is calculated based on the first coefficient and / or the second coefficient, and the bearing capacity is adjusted based on the first additional value, wherein the first additional value is less than 1.

7. The method for monitoring the full life cycle of a shared pallet according to claim 6 is characterized in that: Based on the flow direction information, the node data of each inflow party is compared to analyze the corresponding carrying capacity of the inflow party, and the following steps are also included: If the node information of the inflow party including a single object does not satisfy the quantity and the type in the flow direction information, select a plurality of monitoring nodes of the same type in order as one inflow party, and numerically accumulate the node information of the plurality of monitoring nodes to obtain a node accumulation value; Determine whether the node cumulative value of the inflow party satisfies the quantity, the type and the time in the flow direction information; If satisfied, the bearing capacity is set to 1; generating a third coefficient based on the number of the monitoring nodes in the inflow side; generating a fourth coefficient based on a total transportation distance between each of the monitoring nodes in the inflow side and the outflow side; A second additional value is calculated based on the third coefficient and / or the fourth coefficient, and the bearing capacity is adjusted based on the second additional value, wherein the second additional value is less than 1.

8. The method for monitoring the full life cycle of a shared pallet according to claim 1 is characterized in that: Determining the number of the service flows between the supervision nodes of the same type and selecting a supervision scheme based on the number comprises the following steps: When there are multiple service flows between the same type of supervision nodes, the supervision scheme is specifically a selection of optimal supervision scheme; When there is only one service flow between the supervision nodes of the same type, the supervision scheme is specifically a feedback supervision scheme.

9. The method for monitoring the full life cycle of a shared pallet according to claim 8 is characterized in that: In different supervision schemes, selecting the service flow corresponding to the optimal outflow party according to the numerical relationship between the carrying capacity and the preset value to perform or send abnormal feedback to the outflow party includes the following steps: In the above-mentioned optimal supervision scheme, When the carrying capacity is greater than or equal to the preset value, the service flow corresponding to the inflow party with the highest carrying capacity is selected and all remaining service flows are cancelled; When the carrying capacity does not exist and is greater than or equal to the preset value, the inflow parties that partially meet the flow information are selected for processing, and the content that does not meet the flow information is marked and fed back to the platform; In the feedback supervision scheme, If the carrying capacity is not less than a preset value, the service flow is performed; If the carrying capacity is less than a preset value, supply exception information is generated and sent to the outflow party corresponding to the business flow.

10. A shared pallet full life cycle supervision system, characterized in that: Used to implement the method according to any one of claims 1 to 9.

Images