A collaborative production system and method for light industry based on industrial internet.
By establishing parent-child mapping relationships and consistency verification on the industrial internet platform, the problem of inconsistent granularity of production node splitting across organizations in collaborative production in the light industry was solved, enabling accurate verification of the status, quantity, and vouchers of sub-process nodes, and improving the accuracy and efficiency of production flow.
Patent Information
- Application Number
- CN202611014144.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-07-08
- Publication Date
- 2026-11-10
AI Technical Summary
In the existing industrial internet-based collaborative production model for light industry, the order placement, order acceptance, node acceptance, status feedback, and voucher upload between upstream and downstream production organizations lack a structured collaborative link within the same application. This results in inconsistent granularity of production node breakdown across organizations, making it difficult to accurately confirm the execution content of sub-processes. This can easily lead to insufficient coverage of sub-processes, inconsistent quantities, and unreliable vouchers, thereby increasing the risk of rework and delivery delays.
By acquiring light industrial orders and upstream production nodes, receiving sub-process nodes submitted by the second production organization, determining the process coverage matching value based on the process route and name, establishing a parent-child mapping relationship, generating sub-completion conditions, performing consistency checks, and ensuring that the status, quantity, and vouchers of the sub-process nodes meet the requirements, the nodes are entered into the node collaboration status, and the affected downstream production nodes are locked.
It improves the accuracy of cross-organizational order node status generation, reduces erroneous completions caused by incomplete sub-processes, insufficient quantities, or mismatched vouchers, prevents downstream production nodes from starting prematurely or being unnecessarily blocked, and improves the flow efficiency of collaborative production of light industrial orders.
Smart Images

Figure CN123070520A_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the field of industrial internet and light industry production collaboration technology, specifically a light industry collaborative production system and method based on industrial internet. Background Technology
[0002] Light industrial products such as toys, clothing, and bags are typically characterized by numerous order batches, rapid style changes, dispersed outsourcing organizations, and frequent process connections. A single light industrial order often needs to circulate among multiple production organizations. For example, one organization might be responsible for order acceptance, material preparation, and milestone assignment, while another might handle cutting, sewing, printing, assembly, or packaging. Finally, other organizations might handle quality inspection, warehousing, and delivery. While existing industrial internet platforms can achieve order posting, task assignment, and status feedback, they typically focus on order tasks, fixed process names, or milestone completion status as the primary collaboration objects. They primarily focus on whether tasks have been received and milestones have been reported as complete, failing to adequately reflect the actual granularity differences in how different production organizations break down the same production milestone.
[0003] In actual collaborative production, upstream production organizations may issue a certain production process as a whole production node. The production organization undertaking that node will further break down this whole production node into multiple sub-processes based on its own equipment configuration, personnel division of labor, workstation arrangement, and processing habits. Since the process names, splitting order, completion criteria, and voucher types used by different production organizations are not entirely consistent, if the platform only establishes a simple correspondence based on process names, or only judges whether the upstream production node has been completed based on the completion status returned by the undertaking party, problems such as insufficient coverage of actual sub-processes, abnormal execution order of sub-processes, inconsistency between the completed quantity and the order quantity, and mismatch between vouchers and actual sub-processes are likely to occur.
[0004] For example, in a garment order, the upstream production organization assigns "sewing" as a single production node to an external workshop. However, the external workshop actually needs to complete sub-processes such as overlocking, stitching, buttoning, ironing, and verification in sequence. If the external workshop only completes overlocking and stitching and then reports "sewing complete," and the platform cannot confirm whether each sub-process covers the necessary completion content of the overall production node, nor can it verify whether the completed quantity, the order of reports, and the type of voucher correspond, the upstream production organization may arrange for the packaging organization to receive the semi-finished products in advance. Upon arrival, the packaging organization finds that the buttons are missing and the garments are not ironed, forcing them to be returned for rework, resulting in waiting for semi-finished products, repeated transportation, and delivery delays.
[0005] Furthermore, in existing collaborative production within the light industry sector, order placement, order acceptance, node confirmation, status feedback, and voucher return between different production organizations are often scattered across telephone calls, instant messaging tools, spreadsheets, and offline handover forms. Even when multiple production organizations have established connections through instant messaging tools, their communication relationships lack a structured binding with order nodes, sub-process records, completed quantities, and returned vouchers. Consequently, the platform struggles to form a continuous data link spanning order placement, node acceptance, sub-process breakdown, status return, and exception handling, and it also finds it difficult to accurately determine whether the incompleteness of a particular upstream production node will affect different downstream production nodes.
[0006] Therefore, the existing industrial internet-based collaborative production method for light industry has at least the following shortcomings: when the granularity of production nodes across organizations is inconsistent, it is difficult to accurately confirm the coverage relationship between upstream production nodes and the actual sub-process execution content; when the recipient reports the completion status, there is a lack of verification of the correspondence between the reported status, the completed quantity, and the voucher information; when the upstream production node has not yet met the completion requirements, it is difficult to distinguish the specific reasons for non-completion and its impact on different downstream production nodes, which can easily lead to the distortion of order node status, premature start-up or unnecessary blocking of downstream nodes, thereby increasing the risk of rework, repeated handover, and delivery delays. Summary of the Invention
[0007] In addressing the shortcomings of existing industrial internet-based collaborative production methods in light industry, such as the lack of a structured collaborative link within a single application for order placement, order acceptance, node acceptance, status feedback, and voucher uploading between upstream and downstream production organizations, inconsistent process breakdown granularity for the same production node by different production organizations, unreliable correspondence between upstream production nodes and sub-process nodes, and the tendency of platforms to judge node completion solely based on completion status, leading to problems such as insufficient sub-process coverage, inconsistent quantities, unreliable vouchers, premature start-up of downstream production nodes, or excessive overall blockage, this application provides a collaborative production system and method for light industry based on industrial internet.
[0008] To achieve the above objectives, this application adopts the following technical solution: Firstly, this application provides a collaborative production method for light industry based on industrial internet, including: Obtain the light industrial orders and upstream production nodes uploaded by the first production organization. The upstream production nodes include node completion conditions, process routes, and downstream dependencies. Receive sub-process nodes submitted by the second production organization, wherein the sub-process nodes include name, sequence, quantity, status and return voucher; The process coverage matching value of the sub-process node to the upstream production node is determined according to the process route and the name, and a parent-child mapping relationship is established when the preset mapping conditions are met. Based on the parent-child mapping relationship and the node completion conditions, generate the sub-completion conditions for each sub-process node; Receive the status, quantity, and return documents from each of the sub-process nodes in the order stated, and perform a consistency check based on the sub-completion conditions; Sub-process nodes that pass the consistency check are included in the node collaboration status and compared with the node completion conditions. If not satisfied, the node gap type is determined based on the unsatisfied sub-completion conditions, and the affected downstream production nodes are locked based on the node gap type and the downstream dependency relationship. If the conditions are met, the upstream production node is updated to complete and the downstream production node is triggered to start its process.
[0009] In one optional implementation, before obtaining the light industrial orders and upstream production nodes uploaded by the first production organization, the method further includes: establishing an organizational connection relationship between the first production organization and the second production organization within the same industrial interconnection collaborative application; the organizational connection relationship is formed after one of the first production organization or the second production organization initiates an organizational connection request and the other party confirms it; the organizational connection relationship is used to allow both parties to issue light industrial orders, accept nodes, submit sub-process nodes, transmit status, and upload transmission vouchers within the industrial interconnection collaborative application.
[0010] In one optional implementation, the upstream production node is also associated with product category, style identifier, order quantity, and a set of necessary process items; the set of necessary process items is configured by the first production organization based on the process route, or generated by the industrial internet platform based on the qualified flow records of historical light industrial orders and confirmed by the first production organization; the set of necessary process items is used to limit the process content that must be covered by one or more of the sub-process nodes when the upstream production node is determined to be completed.
[0011] In one optional implementation, determining the process coverage matching value of the sub-process node to the upstream production node based on the process route and the name includes: extracting the necessary process items and sequential connection items corresponding to the upstream production node from the process route; matching the name, order, and quantity of each sub-process node with the necessary process items and the sequential connection items respectively to obtain process item coverage results, order coverage results, and quantity coverage results; and determining the process coverage matching value based on the process item coverage results, the order coverage results, and the quantity coverage results.
[0012] In one optional implementation, establishing a parent-child mapping relationship when the preset mapping conditions are met includes: when the process coverage matching value is not lower than the preset coverage threshold, and the sub-process chain formed by the sub-process nodes in the order can cover the necessary process items corresponding to the upstream production node, the upstream production node is taken as the parent node, and each of the sub-process nodes participating in the coverage is taken as the child node, and the parent-child mapping relationship is established; when there are necessary process items that are not covered, a complete mapping relationship is not established, and the necessary process items that are not covered are recorded as unmet sub-completion conditions for subsequent determination of node gap types.
[0013] In one optional implementation, generating sub-completion conditions for each sub-process node based on the parent-child mapping relationship and the node completion conditions includes: determining the upstream production node process content covered by each sub-process node according to the parent-child mapping relationship; decomposing the completion status, completion quantity, and voucher requirements corresponding to the upstream production node process content in the node completion conditions to the corresponding sub-process nodes to obtain the status requirements, quantity requirements, and voucher requirements corresponding to each sub-process node; combining the status requirements, quantity requirements, and voucher requirements corresponding to the same sub-process node to generate the sub-completion conditions for that sub-process node; wherein the status requirements are used to limit the node status that can be counted as completed, the quantity requirements are used to limit the range of return quantities that can be counted as completed, and the voucher requirements are used to limit the return voucher type, voucher time, and voucher source that can be counted as completed.
[0014] In one optional implementation, the consistency check based on the sub-completion conditions includes: checking whether the status returned by the sub-process node is a completed status, a reviewed and approved status, or a quality inspection approved status according to the status requirements; checking whether the quantity returned by the sub-process node reaches the corresponding required quantity according to the quantity requirements; checking whether the type, time, and source of the returned voucher match the corresponding sub-process node according to the voucher requirements; and determining that the sub-process node passes the consistency check when the status, quantity, and returned voucher all meet the corresponding sub-completion conditions.
[0015] In one optional implementation, determining the node gap type based on unmet sub-completion conditions includes: determining the node gap type as sub-process missing when there are unsubmitted sub-process nodes in the parent-child mapping relationship; determining the node gap type as insufficient quantity when the number of feedback documents of the sub-process nodes does not meet the quantity requirement; determining the node gap type as missing document when the feedback documents do not meet the document requirements; and determining the node gap type as sequence abnormality when the order of the sub-process nodes does not meet the process route.
[0016] In one optional implementation, locking the affected downstream production nodes based on the node gap type and the downstream dependency includes: determining the sub-completion conditions that each downstream production node depends on based on the downstream dependency; matching the dependent sub-completion conditions with the unmet sub-completion conditions corresponding to the node gap type to obtain the affected downstream production nodes, and keeping the affected downstream production nodes in a prohibited startup state until the corresponding node gap type is eliminated; for downstream production nodes that are not matched with the node gap type, maintaining their original flow state.
[0017] Secondly, this application provides a collaborative production system for light industry based on industrial internet, comprising: The organization connection module is used to establish organizational connection relationships between a first production organization and a second production organization within the same industrial interconnection collaborative application. The order node acquisition module is used to acquire light industrial orders uploaded by the first production organization and upstream production nodes; The sub-process receiving module is used to receive sub-process nodes submitted by the second production organization; The mapping establishment module is used to determine process coverage matching values and establish parent-child mapping relationships; The condition generation module is used to generate sub-completion conditions; The consistency verification module is used to perform consistency verification on the status, quantity and return vouchers of the returned data according to the sub-completion conditions. The node status generation module is used to include sub-process nodes that have passed the consistency verification into the node collaboration status and compare it with the node completion conditions. The flow control module is used to lock the affected downstream production node when the node collaboration state does not meet the node completion condition, or to trigger the flow of the downstream production node when the node collaboration state meets the node completion condition.
[0018] Compared with related technologies, this application has the following advantages: By acquiring light industrial orders and upstream production nodes, and receiving sub-process nodes submitted by the second production organization, the upstream production nodes defined by the first production organization and the sub-process nodes actually split by the second production organization can enter the same processing chain. Simultaneously, by determining the process coverage matching value of the sub-process node to the upstream production node based on the process route and the name, and establishing a parent-child mapping relationship when preset mapping conditions are met, the platform can determine the correspondence between upstream production nodes and sub-process nodes based on the degree of coverage between the process route and the sub-process content. Therefore, this application no longer relies solely on fixed process names or node names submitted unilaterally by the contractor for correspondence, reducing the risk of erroneous mapping caused by inconsistent granularity of cross-organizational process splitting, and providing a unified data foundation for subsequent sub-completion condition generation, status verification, and node flow control.
[0019] By generating sub-completion conditions for each sub-process node based on the parent-child mapping relationship and the node completion conditions, the completion requirements of the upstream production node can be decomposed into corresponding sub-process nodes. Furthermore, by receiving the status, quantity, and return documents from each sub-process node in the specified order, and performing consistency checks based on the sub-completion conditions, only sub-process nodes that meet the corresponding status, quantity, and document requirements are counted in the node collaboration status. Therefore, whether an upstream production node is completed no longer depends solely on the overall completion status returned by the second production organization, but is jointly determined by the sub-process coverage, return status, completion quantity, and return documents. This reduces the likelihood of erroneous completion of upstream production nodes due to incomplete sub-processes, insufficient completion quantities, or mismatches between documents and sub-processes, thus improving the accuracy of cross-organization order node status generation.
[0020] By including sub-process nodes that pass the consistency check in the node collaboration status and comparing the node collaboration status with the node completion conditions, the platform can determine whether upstream production nodes meet the completion requirements. When the node collaboration status does not meet the node completion conditions, the node gap type is determined based on the unmet sub-completion conditions, and the affected downstream production nodes are locked based on the node gap type and the downstream dependency relationship. When the node collaboration status meets the node completion conditions, the upstream production node is updated to complete, and the downstream production node is triggered to start. Thus, this application can distinguish the impact range of different incompleteness reasons on downstream nodes, preventing affected downstream nodes from starting prematurely while avoiding unnecessary blocking of unaffected downstream production nodes, thereby improving the accuracy of node connection and flow efficiency in cross-organizational collaborative production of light industrial orders. Attached Figure Description
[0021] Figure 1A schematic diagram of a collaborative production method for light industry based on industrial internet provided for an embodiment of this application; Figure 2 This application provides a schematic diagram of an organizational connection and order placement / acceptance process within the same industrial internet collaborative application. Figure 3 A schematic diagram of a process coverage matching value determination process provided in this application embodiment; Figure 4 This application provides a schematic diagram of a parent-child mapping relationship establishment and child completion condition generation process. Figure 5 A schematic diagram of a consistency verification process for status, quantity, and returned credentials provided in this application embodiment; Figure 6 This application provides a schematic diagram of a node collaborative state generation process. Figure 7 A schematic diagram illustrating the process of determining the node gap type and locking the downstream production node, provided in an embodiment of this application; Figure 8 This is a schematic diagram of a collaborative production system for light industry based on industrial interconnection, provided as an embodiment of this application. Detailed Implementation
[0022] The technical solution of this application will be further described below with reference to the accompanying drawings and embodiments. It should be understood that the following embodiments are only used to illustrate this application and are not intended to limit the scope of protection of this application. Where there is no conflict, the technical features in the embodiments of this application can be combined with each other.
[0023] This embodiment provides a collaborative production method for the light industry based on industrial internet. This method can be applied to collaborative production platforms, industrial internet platforms, order collaboration platforms, outsourcing production management platforms, or collaborative management systems between production organizations in the light industry. The first production organization can be an order initiation organization, order receiving organization, material preparation organization, or node distribution organization; the second production organization can be an outsourcing organization, processing organization, or subcontracting production organization that undertakes upstream production nodes. The light industrial order can be a toy order, clothing order, bag order, or other light industrial product order with multiple batches, styles, and processes.
[0024] In this application, the sub-process node can be understood as a dynamic execution record established by the second production organization around the upstream production node. When submitted, the sub-process node may include fields such as name, sequence, quantity, status, and feedback voucher. The quantity may include the quantity to be processed, the inflow quantity, or the completed quantity; the status may include pending execution, in-process, completed, approved, or quality inspection approved status; and the feedback voucher can be uploaded and written to the corresponding fields by the second production organization progressively during the execution of the sub-process node. Therefore, the claim of receiving the sub-process node submitted by the second production organization does not contradict the subsequent receipt of the status, quantity, and feedback voucher returned by each of the sub-process nodes in the stated sequence. The former emphasizes the establishment of the node record, while the latter emphasizes the updating of the node execution information.
[0025] like Figure 1 As shown, the method in this embodiment includes the following steps.
[0026] Step S100: Establish organizational connection between the first production organization and the second production organization within the same industrial interconnection collaborative application.
[0027] In one optional implementation, both the first and second production organizations are registered within the same industrial internet collaboration application. This application can be installed on mobile terminals, tablets, production dashboards, or accessed via a web browser. Each of the first and second production organizations has an organization account, which is associated with the organization name, organization type, available processes, production capacity, contact person, location, and historical collaboration records.
[0028] When establishing a collaborative relationship, the first production organization can send an organizational connection request to the second production organization through the industrial interconnection collaborative application. After the second production organization confirms, an organizational connection relationship is formed between the two parties. Alternatively, the second production organization can proactively send an organizational connection request to the first production organization, which will then confirm and form an organizational connection relationship. This organizational connection process adopts an interactive form where one party initiates a connection request and the other party confirms and establishes the connection. In this application, the connection object is the production organization account, the connection purpose is to establish a data channel for collaborative order production, and the connection content is limited to production collaborative data such as light industrial orders, upstream production nodes, sub-process nodes, status, quantity, feedback vouchers, and anomaly feedback.
[0029] In one optional implementation, the organizational connection relationship may correspond to a collaborative permission scope, which includes the scope of visible orders, the scope of nodes that can accept orders, the scope of data that can be transmitted back, and the scope of vouchers that can be viewed. For a second production organization that has established an organizational connection relationship and accepted light industrial orders, the platform grants access to upstream production nodes, sub-process nodes, and data transmission voucher processing related to the accepted orders. For production organizations that have not established an organizational connection relationship or have not accepted corresponding light industrial orders, the platform restricts their access to the node data, transmitted data, and voucher data of the corresponding light industrial orders.
[0030] In one alternative implementation, a first production organization can establish organizational connections with multiple second production organizations, and a second production organization can also establish organizational connections with multiple first production organizations. Although these multiple production organizations are within the same industrial interconnection collaboration application, the information each organization can view and process is limited to data related to its organizational connection, accepted orders, and collaboration permissions. Therefore, the platform supports rapid connections between multiple upstream and downstream production organizations while avoiding data confusion between different orders and different organizations.
[0031] Step S101: Obtain the light industrial orders and upstream production nodes uploaded by the first production organization; the upstream production nodes include node completion conditions, process routes, and downstream dependencies. The light industrial orders may include order number, product type, style information, specification information, order quantity, delivery time, and information of participating production organizations. The upstream production nodes are production process nodes defined by the first production organization in the light industrial orders, such as cutting nodes, sewing nodes, printing nodes, assembly nodes, packaging nodes, or quality inspection nodes.
[0032] In one alternative implementation, a first production organization can create a light industrial order within the same industrial internet collaborative application and select a second production organization as the recipient from among production organizations with established organizational connections. The light industrial order carries upstream production nodes, node completion conditions, process routes, and downstream dependencies. Upon receiving the light industrial order within the industrial internet collaborative application, the second production organization can either accept or reject the order. When the second production organization accepts the order, the platform associates the light industrial order, upstream production nodes, and subsequent sub-process nodes with the organizational connection between the first and second production organizations.
[0033] In one optional implementation, the upstream production node may also be associated with a node number, node name, product category, style identifier, order quantity, process route number, necessary process item set, and node priority. The necessary process item set represents the process content that must be covered when the upstream production node is completed. The necessary process item set can be configured by the first production organization when establishing a light industrial order, or it can be generated by the industrial internet platform based on historical qualified orders, historical rework records, process template library, or product category rules, and then confirmed by the first production organization.
[0034] The node completion condition refers to the conditions that must be met for an upstream production node to be considered complete, and may include at least one of the following: completion status, completed quantity, necessary documentation, process coverage, sequential continuity, and quality confirmation requirements. The process route refers to the processing path and process connection relationship corresponding to the upstream production node. The downstream dependency relationship refers to the dependency relationship between one or more downstream production nodes and the completion status of the upstream production node or its internal sub-processes.
[0035] In one data acquisition method, the first production organization can upload the light industrial order and upstream production nodes through the order creation interface of the industrial internet platform; in another data acquisition method, the first production organization can upload the light industrial order and upstream production nodes through the ERP system interface, production management system interface, or order import interface. The process route and node completion conditions can be selected by the first production organization from the process template library, or generated based on product category, style identifier, and order quantity and then manually confirmed.
[0036] Step S102: Receive sub-process nodes submitted by the second production organization; the sub-process nodes include name, sequence, quantity, status, and feedback voucher. The sub-process nodes are internal execution nodes formed by the second production organization after breaking down the upstream production node according to its own equipment configuration, personnel division of labor, and processing habits. For example, when the upstream production node is a sewing node, the second production organization can submit sub-process nodes such as overlocking, stitching, button attaching, ironing, and verification.
[0037] The name is used to identify the process content of the sub-process node; the order is used to indicate the sequential execution relationship between sub-process nodes; the quantity is used to indicate the quantity to be processed, the inflow quantity, or the completed quantity corresponding to the sub-process node; the status is used to indicate the execution status of the sub-process node; and the feedback voucher is used to prove the execution status of the sub-process node. The feedback voucher can be an image voucher, a barcode voucher, a handover voucher, a quality inspection voucher, or other vouchers uploaded by the second production organization. The feedback voucher may include voucher type, voucher time, voucher source, and associated sub-process node identifier.
[0038] In one optional implementation, the second production organization can receive the light industrial orders within the industrial internet collaboration application and submit sub-process nodes corresponding to the upstream production nodes within the same system. In other words, the order placement operation of the first production organization, the order acceptance operation of the second production organization, the sub-process splitting operation of the second production organization on the upstream production nodes, and the subsequent status feedback, quantity feedback, and upload of feedback vouchers for each sub-process node are all completed within the same industrial internet collaboration application. This method enables production collaboration information that was originally scattered across telephones, ordinary instant messaging groups, spreadsheets, and offline handover forms to be uniformly recorded as structured node data that can be read and accessed by the platform.
[0039] In another optional implementation, the second production organization can submit the sub-process nodes via mobile terminals, production dashboards, barcode scanning terminals, workstation reporting terminals, or industrial internet platform interfaces. In yet another optional implementation, the second production organization can retrieve sub-process node templates from historical process templates and adjust the names, order, and quantity of the sub-process nodes according to the product category, style identifier, and order quantity of the current light industrial order. Sub-process nodes generated from templates can be submitted after confirmation by the head of the second production organization.
[0040] Through the organizational connections, order placement and acceptance, and sub-process node submission methods within the same application, the platform can establish an order collaboration data link starting from the organizational connection relationship, so that subsequent process coverage matching value determination, parent-child mapping relationship establishment, sub-completion condition generation, consistency verification, node collaboration status generation, and downstream production node locking all have a unified data source.
[0041] Step S103: Determine the process coverage matching value of the sub-process node to the upstream production node according to the process route and the name, and establish a parent-child mapping relationship when the preset mapping conditions are met.
[0042] In one alternative implementation, such as Figure 3 As shown, necessary process items and sequential connection items corresponding to the upstream production nodes can be extracted from the process route. The necessary process items represent the process content that must be covered when the upstream production node is completed, and the sequential connection items represent the order of the process content. Subsequently, the name, order, and quantity of each sub-process node are matched with the necessary process items and the sequential connection items, respectively, to obtain process item coverage results, order coverage results, and quantity coverage results. A process coverage matching value is then determined based on the process item coverage results, the order coverage results, and the quantity coverage results.
[0043] The process coverage matching value indicates the degree to which the sub-process nodes submitted by the second production organization cover the upstream production nodes defined by the first production organization. The process coverage matching value can be represented by a grade value, score, number of satisfied items, or a comprehensive marker. For example, the matching between the name and necessary process items can be used as the process item coverage result; the matching between the sequence of sub-process nodes and the sequential connections of the process route can be used as the sequence coverage result; and the matching between the number of sub-process nodes and the order quantity or node completion quantity can be used as the quantity coverage result. The platform can determine the process coverage matching value based on the combination of the process item coverage result, sequence coverage result, and quantity coverage result.
[0044] When determining the process coverage matching value, the platform first reads the set of necessary process items, the order of process items, and the order quantity from the process route table. Then, it reads the name, sequence number, and required quantity of each sub-process node submitted by the second production organization. For any necessary process item, if at least one sub-process node has the same name as the necessary process item, or if the name of the sub-process node is in the synonym process name table corresponding to the necessary process item, the name matching result of the necessary process item is recorded as matched; otherwise, it is recorded as unmatched. The platform divides the number of matched necessary process items by the total number of necessary process items to obtain the process item coverage ratio. The platform also arranges each sub-process node in ascending order of its sub-process node sequence number and compares the arranged sub-process node order with the process item order in the process route table item by item. If the order of each matched necessary process item matches the process item order, the generated order coverage result is satisfied; otherwise, the generated order coverage result is unsatisfactory. The platform compares the required quantity of each sub-process node with the order quantity or the quantity completed by the corresponding node. If the required quantity of each necessary sub-process node involved in the coverage is not less than the quantity completed by the corresponding node, the quantity coverage result is considered satisfactory; otherwise, the quantity coverage result is considered unsatisfactory. The platform uses the process item coverage ratio as the process coverage matching value and writes the process coverage matching value, the sequence coverage result, and the quantity coverage result into the process coverage matching table for subsequent use when determining whether the preset mapping conditions are met.
[0045] In one optional implementation, before establishing the parent-child mapping relationship, the industrial internet platform first establishes a process coverage matching table. This table records the coverage judgment process and results between the upstream production node and each of the sub-process nodes. The process coverage matching table includes at least the upstream production node identifier, necessary process items, necessary process item order, sub-process node identifier, sub-process node name, sub-process node order, required quantity, name matching result, order matching result, quantity coverage result, voucher type matching result, process item coverage ratio, process coverage matching value, and mapping judgment result. The process coverage matching table can be generated by the industrial internet platform based on the process route table, sub-process node table, and preset synonymous process name table. The process route table is uploaded or confirmed by the first production organization, the sub-process node table is submitted by the second production organization, and the preset synonymous process name table records the name expression relationships of different production organizations for the same process content.
[0046] In one optional implementation, the industrial internet platform reads the set of necessary process items corresponding to the upstream production node and writes each necessary process item into the process coverage matching table according to the order in the process route; it reads each sub-process node submitted by the second production organization and writes it into the process coverage matching table in the order of the sub-process nodes; it compares the name of each sub-process node with the necessary process item. If the name of the sub-process node is the same as the necessary process item, or if the name of the sub-process node falls into the preset synonym process name table corresponding to the necessary process item, the name matching result is recorded as matched; otherwise, it is recorded as unmatched. The industrial internet platform determines the process item coverage ratio based on the ratio of the number of matched necessary process items to the total number of necessary process items, determines the order matching result based on the relationship between the order of the sub-process nodes and the order of the necessary process items, determines the quantity coverage result based on the comparison result between the quantity to be completed of the sub-process node and the quantity completed by the upstream production node, and determines the voucher type matching result based on whether the voucher type corresponding to the sub-process node belongs to the voucher type allowed by the node completion conditions.
[0047] In one optional implementation, the process coverage matching value is determined based on the process item coverage ratio, the sequence matching result, the quantity coverage result, and the voucher type matching result; when the sequence matching result, the quantity coverage result, and the voucher type matching result are all satisfied, the process item coverage ratio is used as the process coverage matching value; when any one of the sequence matching result, the quantity coverage result, or the voucher type matching result is not satisfied, the process item coverage ratio is downweighted to obtain the process coverage matching value. The weight reduction process can be executed according to a preset deduction value, a preset deduction ratio, or a preset level rule. The preset deduction value, preset deduction ratio, or preset level rule is configured by the first production organization based on product category, process complexity, historical rework rate, and historical omission rate, or it can be generated by the industrial internet platform based on historical qualified transfer records and confirmed by the first production organization. When the process coverage matching value is not lower than the preset coverage threshold, and both the sequence matching result and the quantity coverage result are satisfied, the mapping judgment result is recorded as allowing the establishment of a parent-child mapping relationship; otherwise, the mapping judgment result is recorded as not allowing the establishment of a complete mapping relationship, and the unmatched necessary process items, sequence abnormal items, or quantity insufficient items are written into the unsatisfied sub-completion conditions.
[0048] In one optional implementation, the preset mapping conditions may include a process coverage matching value not lower than a preset coverage threshold, and the ability of the sub-process chain formed by the sub-process nodes in sequence to cover the necessary process items corresponding to the upstream production node. When the process coverage matching value meets the preset mapping conditions, the upstream production node is designated as the parent node, and each sub-process node participating in the coverage is designated as the child node, establishing a parent-child mapping relationship. When there are uncovered necessary process items, a complete mapping relationship may not be established, and the uncovered necessary process items are recorded as unmet sub-completion conditions for subsequent determination of node gap types.
[0049] In another optional implementation, the platform can set a process coverage matching table, which includes upstream production nodes, sub-process nodes, name matching results, sequence matching results, quantity coverage results, voucher type matching results, and process coverage matching values. The name matching result is used to determine whether the process content of the sub-process node can cover the necessary process items; the sequence matching result is used to determine whether the sub-process chain conforms to the process route; the quantity coverage result is used to determine whether the processing quantity of the sub-process node covers the order quantity or the node completion quantity; and the voucher type matching result is used to determine whether the sub-process node has a verifiable return voucher type.
[0050] The preset coverage threshold can be set based on product category, process complexity, historical order acceptance results, historical rework rate, stability of outsourcing organizations, or management requirements of the primary production organization. The preset coverage threshold can be preset by the platform or adjusted by the primary production organization based on historical missed work rate, rework rate, and acceptance anomaly rate.
[0051] In one implementation, the platform can configure the preset coverage threshold as a percentage threshold. For upstream production nodes such as sewing, assembly, assembly, and functional testing, if the number of necessary process items corresponding to the node is not less than three, and the historical rework rate is not less than the preset rework rate threshold, then the preset coverage threshold is set to 100%; for nodes with two necessary process items, the preset coverage threshold is set to 80% to 100%; for label printing, simple outer packaging, or single handover nodes, the preset coverage threshold is set to 60% to 80%. When performing mapping judgment, the platform compares the current process coverage matching value with the preset coverage threshold under the corresponding product category and node type. If the process coverage matching value is not less than the preset coverage threshold, and both the sequence coverage result and the quantity coverage result are satisfied, then the preset mapping condition is determined to be met; otherwise, the preset mapping condition is determined not to be met.
[0052] In this way, the platform does not directly regard processes with the same or similar names as corresponding relationships. Instead, it further combines the process route, sub-process names, sub-process order and quantity coverage to determine whether to establish a mapping relationship, thereby reducing the risk of incorrect mapping caused by differences in process granularity across organizations.
[0053] Step S104: Generate the sub-completion conditions for each sub-process node based on the parent-child mapping relationship and the node completion conditions.
[0054] like Figure 4 As shown, after establishing the parent-child mapping relationship, the node completion conditions can be decomposed into each sub-process node according to the parent-child mapping relationship, resulting in the status requirements, quantity requirements, and voucher requirements corresponding to each sub-process node. Specifically, the status requirements limit the node status that can be counted as completed, the quantity requirements limit the range of return quantities that can be counted as completed, and the voucher requirements limit the type, time, and source of the return vouchers that can be counted as completed.
[0055] Specifically, the platform reads the parent node number, child node number, and necessary process items corresponding to each sub-process node from the parent-child mapping relationship. The platform reads the completion status, completion quantity, necessary document type, and quality confirmation requirements from the node completion conditions. For each sub-process node, the platform writes the completion status or quality confirmation status from the node completion conditions into the status requirements of that sub-process node; writes the order quantity, node completion quantity, or the required quantity of the corresponding process item into the quantity requirements; and writes the document type, document time range, and document source corresponding to the sub-process node type into the document requirements. If a sub-process node corresponds to a necessary process item, then that sub-process node is marked as a necessary sub-process; if the sub-process node does not meet the status requirements, quantity requirements, or document requirements, then the corresponding unmet item is written into the node gap type corresponding to the exception. The platform thus generates a sub-completion condition table, which is read during the consistency check in step S105.
[0056] In one optional implementation, the platform can generate a sub-completion condition table, which includes sub-process node number, sub-process node name, status requirements, quantity requirements, voucher requirements, whether it is a necessary sub-process, the node gap type corresponding to an anomaly, and whether it affects downstream production nodes. The sub-completion condition table can be automatically generated by decomposing node completion conditions according to parent-child mapping relationships, or it can be reviewed and adjusted by the first production organization, the second production organization, or the platform administrator.
[0057] For example, when the upstream production node is a sewing node, and its node completion conditions include completing all order quantities and providing verification documents, the sub-completion conditions of the overlock sub-process node may include the overlock completion status and the overlock completion quantity; the sub-completion conditions of the seam splicing sub-process node may include the seam splicing completion status and the seam splicing completion quantity; the sub-completion conditions of the button sewing sub-process node may include the button sewing completion status, the button sewing completion quantity, and the corresponding return document; the sub-completion conditions of the ironing sub-process node may include the ironing completion status, the ironing completion quantity, and the ironing document; and the sub-completion conditions of the verification sub-process node may include the verification passed status and the verification document.
[0058] Step S105: Receive the status, quantity, and return voucher from each of the sub-process nodes in the order stated, and perform a consistency check based on the sub-completion conditions.
[0059] like Figure 5As shown, consistency checks can include status consistency checks, quantity consistency checks, and document consistency checks. Status consistency checks verify whether the status returned by the sub-process node is "completed," "approved," or "quality inspection passed," based on status requirements. Quantity consistency checks verify whether the quantity returned by the sub-process node meets the corresponding required quantity, based on quantity requirements. Document consistency checks verify whether the type, time, and source of the returned documents match the corresponding sub-process node, based on document requirements.
[0060] When the status, quantity, and returned documentation all meet the corresponding sub-completion conditions, the sub-process node is determined to have passed the consistency check. When any of the status, quantity, or returned documentation does not meet the corresponding sub-completion conditions, the sub-process node is determined to have failed the consistency check, and the sub-process node is not included in the node collaboration status used to determine the completion of the upstream production node.
[0061] In one optional implementation, when the status does not meet the status requirements, the platform generates a status review request; when the quantity does not meet the quantity requirements, the platform generates a quantity supplementation request; when the returned voucher does not meet the voucher requirements, the platform generates a supplementary voucher request; when multiple verification items fail, the platform can generate verification feedback information including multiple reasons for the anomalies. The verification feedback information can be sent to the reporting terminal of the second production organization or to the review terminal of the first production organization.
[0062] In another optional implementation, the platform can determine the voucher availability flag based on the voucher type, return time, voucher source, and associated sub-process node. For example, barcode vouchers need to be associated with the workstation or batch of the corresponding sub-process node, image vouchers need to be associated with the return time of the corresponding sub-process node, and quality inspection vouchers need to be associated with the review or quality inspection sub-process node. When the voucher availability flag indicates that the returned voucher does not match the corresponding sub-process node, the corresponding sub-process node is not included in the node collaboration status, and a supplementary voucher request or manual review request is generated.
[0063] The available voucher markers include an available marker, a pending supplement marker, and a manual review marker. The platform reads the voucher type, return time, voucher source, associated sub-process node identifier, and uploading organization identifier from the returned voucher, and reads the voucher requirements in the corresponding sub-completion conditions. If the voucher type is one of the types allowed by the voucher requirements, the return time is after the execution time of the corresponding sub-process node but not later than the preset voucher return time limit, the voucher source is consistent with the second production organization or its authorized reporting terminal, and the associated sub-process node identifier is consistent with the currently verified sub-process node, then an available marker is generated. If any of the voucher type, return time, or associated sub-process node identifier is missing, a pending supplement marker is generated. If the voucher source is inconsistent with the current second production organization, or the same voucher is associated with multiple mutually exclusive sub-process nodes, a manual review marker is generated. The platform only includes sub-process nodes with an available voucher marker in the node collaboration status; for pending supplement markers or manual review markers, a supplementary voucher request or a manual review request is generated.
[0064] In one data collection method, the status and quantity of sub-process nodes can be filled in by the second production organization through the reporting interface when the sub-process is completed. In another data collection method, status and quantity can be collected through barcode handover, workstation reporting, quality inspection record import, or production dashboard confirmation. Return vouchers can be collected by the second production organization through mobile terminal photo upload, barcode terminal collection, quality inspection record import, or handover sheet upload. Each return voucher should at least be associated with the sub-process node identifier, return time, voucher source, and voucher type.
[0065] Step S106: The sub-process nodes that pass the consistency verification are included in the node collaboration status and compared with the node completion conditions.
[0066] like Figure 6 As shown, the platform reads the sub-process nodes that have passed consistency verification according to the parent-child mapping relationship, and determines the completed sub-process chain according to the order. When the sequential continuity, cumulative completion quantity, and integrity of the returned vouchers of the completed sub-process chain all meet the node completion conditions, a node collaboration state indicating that the upstream production node can complete the task is generated. Otherwise, a node collaboration state indicating that the upstream production node cannot complete the task is generated.
[0067] In one optional implementation, the node coordination status may include covered sub-process nodes, unmet sub-completion conditions, a transferable identifier, and a gap reason identifier. Specifically, a covered sub-process node indicates a sub-process node that has passed consistency verification and has been counted as completed by the upstream production node; an unmet sub-completion condition indicates a status requirement, quantity requirement, or document requirement that is still not met; a transferable identifier indicates whether the upstream production node can be updated to complete; and a gap reason identifier indicates the specific reason why the upstream production node cannot be completed.
[0068] The node collaborative status is not a unilateral completion status reported back by the second production organization, but rather a status result jointly generated by the platform based on the parent-child mapping relationship, child completion conditions, consistency verification results, and node completion conditions. This avoids the upstream production node being mistakenly updated to completion when the second production organization reports the overall completion status after completing only a portion of the sub-processes.
[0069] Step S107: If the node collaboration state does not meet the node completion condition, then determine the node gap type based on the unmet sub-completion condition, and lock the affected downstream production node based on the node gap type and the downstream dependency relationship.
[0070] like Figure 7 As shown, when there are unsubmitted sub-process nodes in the parent-child mapping relationship, the node gap type can be determined as sub-process missing. When the number of returned documents for a sub-process node does not meet the quantity requirement, the node gap type can be determined as insufficient quantity. When the returned documents do not meet the document requirements, the node gap type can be determined as document missing. When the order of the sub-process nodes does not meet the process route, the node gap type can be determined as sequence anomaly.
[0071] In one alternative implementation, the platform can generate a downstream dependency table. The downstream dependency table includes downstream production nodes, dependent upstream production nodes, dependent sub-completion conditions, gap impact levels, and locking methods. The downstream dependency table can be set by the first production organization when configuring the process route, or it can be generated by the platform based on the upstream and downstream flow relationships of each node in historical orders and then confirmed by the first production organization.
[0072] After determining the node gap type, the sub-completion conditions that each downstream production node depends on can be determined based on downstream dependencies. These sub-completion conditions are then matched with the unmet sub-completion conditions corresponding to the node gap type to identify the affected downstream production nodes. Affected downstream production nodes are kept in a disabled startup state until the corresponding node gap type is eliminated; downstream production nodes that do not match a node gap type maintain their original operation state.
[0073] The elimination of node gap types refers to the following: for missing sub-processes, the second production organization submits the corresponding sub-process node, and this sub-process node is included in the parent-child mapping relationship; for insufficient quantity, the second production organization supplements the quantity returned, and the cumulative returned quantity is not less than the corresponding quantity requirement; for missing vouchers, the second production organization uploads and returns vouchers, and the returned vouchers are marked as usable; for abnormal order, the second production organization adjusts the order of sub-process nodes, or the first production organization confirms that the order adjustment is acceptable, and the adjusted sub-process chain satisfies the process route. After the above conditions are met, the platform removes the corresponding node gap type from the node collaboration status and re-determines whether the affected downstream production nodes are allowed to flow.
[0074] In one example, in a garment order, if the button-sewing process node fails to meet its sub-completion conditions, and the packaging node depends on the button-sewing process node, then the packaging node is identified as an affected downstream production node and locked. If a downstream node only depends on the order style information and not on the button-sewing process node, then that downstream node can maintain its original workflow. This approach avoids blocking all downstream production nodes and prevents affected downstream production nodes from being prematurely activated.
[0075] Step S108: If the node collaboration status meets the node completion condition, then update the upstream production node to completion and trigger the downstream production node to start working.
[0076] When the platform determines that the node collaboration status meets the node completion conditions, it indicates that the sub-process node participating in the parent-child mapping relationship has passed the consistency check according to the sub-completion conditions and can meet the completion requirements of the upstream production node. At this time, the upstream production node can be updated to complete, and the corresponding downstream production node flow can be triggered according to the downstream dependency relationship. The triggering of the downstream production node flow can include allowing the downstream production node to enter the waiting to receive state, waiting to execute state, waiting to quality inspection state, or other flow states adapted to the order collaboration platform.
[0077] Example 1: Taking a garment order as an example, both the first and second production organizations register and log in to the same industrial internet collaboration application. The first production organization searches for the second production organization within the application and sends a connection request. After the second production organization confirms, the two organizations establish a connection. Once the connection is established, the first production organization can issue light industrial orders to the second production organization within the application, and the second production organization can receive and accept orders within the same application.
[0078] In this garment order, the first production organization sets sewing as the upstream production node, with the completion condition being the completion of sewing 100 garments and uploading verification vouchers. After receiving the order, the second production organization, within the same industrial internet collaborative application, breaks down sewing into five sub-process nodes: overlocking, seaming, buttoning, ironing, and verification. Each sub-process node submits its name, sequence, quantity, status, and feedback voucher fields. The platform, based on the process route, determines that the five sub-process nodes can cover the sewing node, establishes a parent-child mapping relationship, and generates the sub-completion conditions for each sub-process node.
[0079] If the overlocking and seam stitching are both completed and the quantity is 100 pieces, but only 80 pieces of buttons are returned, the ironing process lacks uploaded documentation, and the verification fails, the platform will not update the sewing node to complete. Instead, it will determine the node gap type, including insufficient quantity, missing documentation, and unmet status, and lock the packaging node based on downstream dependencies to prevent the packaging organization from receiving semi-finished products prematurely. If the hangtag printing node only depends on style information and order quantity, and not on the completion conditions of button stitching, ironing, and verification, the platform can maintain the original flow status of the hangtag printing node. Through this embodiment, the order placement of the first production organization, the order acceptance of the second production organization, the breakdown of sub-processes, status feedback, documentation upload, and downstream node control are all completed within the same industrial internet collaborative application.
[0080] Exemplary Description 2 Taking a bag order as an example, the first production organization sets assembly as the upstream production node, while the second production organization breaks it down into sub-process nodes such as zipper installation, shoulder strap installation, hardware fixing, and appearance re-inspection. If zipper installation and shoulder strap installation are completed, but the hardware fixing has not been documented and the appearance re-inspection has failed, the platform can determine that the documentation is missing and the review has failed based on the unmet sub-completion conditions, and lock the packaging node that depends on the appearance re-inspection results. For the label preparation node that does not depend on the hardware fixing and appearance re-inspection results, the platform can maintain its original flow status.
[0081] Example Description 3 Taking a toy order as an example, the first production organization sets assembly as the upstream production node, while the second production organization breaks it down into sub-process nodes such as shell assembly, battery compartment installation, functional testing, and pre-packaging verification. If shell assembly and battery compartment installation are completed, but functional testing has not been documented, the platform can determine that the node gap type is missing documentation and lock the quality inspection node or packaging node that depends on the functional test results, preventing untested toys from entering the subsequent packaging or delivery process.
[0082] Instructions for setting preset conditions, thresholds, and tables. To facilitate implementation, the preset mapping conditions, preset coverage thresholds, sub-completion conditions, and downstream dependencies in this application can be set through platform configuration tables, process template libraries, or manual confirmation results.
[0083] The organizational connection relationship table may include a first production organization identifier, a second production organization identifier, connection status, connection confirmation time, available processes, scope of collaborative permissions, and historical collaborative records. This table records the production organization collaborative relationships formed based on organizational connection requests and confirmation responses, and is used to limit the data scope for subsequent light industrial order issuance, node acceptance, sub-process submission, and voucher return.
[0084] The process route table may include product category, style identifier, upstream production nodes, necessary process items, process item sequence, whether completion is mandatory, and corresponding downstream nodes. The process route table can be derived from process documents uploaded by the first production organization, historical qualified orders, or pre-set process templates on the platform.
[0085] The sub-process node table may include the second production organization identifier, sub-process node name, sequence number, quantity to be completed, return status, return quantity, return voucher identifier, and return time. The sub-process node table can be submitted by the second production organization, or it can be generated by the platform based on the second production organization's historical process template and then confirmed by the second production organization.
[0086] The process coverage matching table may include upstream production nodes, sub-process nodes, name matching results, sequence matching results, quantity coverage results, document type matching results, and process coverage matching values. The process coverage matching values can be determined comprehensively based on the name matching results, sequence matching results, quantity coverage results, and document type matching results.
[0087] The sub-completion condition table may include sub-process nodes, status requirements, quantity requirements, voucher requirements, whether the sub-process is necessary, and the corresponding node gap type in case of anomalies. The sub-completion condition table can be formed by decomposing node completion conditions according to parent-child mapping relationships, or it can be reviewed and adjusted by the first production organization or platform administrator.
[0088] The downstream dependency table may include downstream production nodes, dependent upstream production nodes, dependent sub-completion conditions, gap impact level, and locking method. The downstream dependency table can be configured by the first production organization when creating the process route, or generated by the platform based on the upstream and downstream flow relationships of each node in historical orders and then confirmed by the first production organization.
[0089] The preset coverage threshold can be set based on product category, process complexity, historical order acceptance results, historical rework rate, historical omission rate, and the stability of outsourcing organizations. For example, for upstream production nodes such as sewing, assembly, and assembly, if the number of necessary process items corresponding to the node is no less than three, and the historical rework rate is not less than the preset rework rate threshold, the preset coverage threshold can be set to 100%. For nodes with two necessary process items, the preset coverage threshold can be set to 80% to 100%. For label printing, simple outer packaging, or single handover nodes, the preset coverage threshold can be set to 60% to 80%. When performing mapping judgment, the platform compares the current process coverage matching value with the preset coverage threshold under the corresponding product category and node type. If the process coverage matching value is not less than the preset coverage threshold, and both the sequence coverage result and the quantity coverage result are satisfied, then the preset mapping condition is determined to be met; otherwise, the preset mapping condition is determined not to be met.
[0090] The method in this application can introduce manual confirmation at multiple stages, but manual confirmation is not a replacement for the platform's main data processing chain. Instead, it is used to handle process template configuration, organizational connection confirmation, anomaly verification, and dispute review.
[0091] During the organization connection phase, either the first or second production organization can manually confirm whether to accept the other party's organization connection request. During the order creation phase, the first production organization can configure or confirm upstream production nodes, node completion conditions, process routes, and downstream dependencies. During the sub-process submission phase, the second production organization can submit or confirm sub-process nodes. In cases of insufficient process coverage matching, inconsistent documentation, abnormal quantities, or node gap disputes, the platform can send the anomaly information to the first production organization, the second production organization, or the platform administrator for manual review. The results of the manual review can be used to update process templates, documentation requirements, preset coverage thresholds, organization connection permissions, or downstream dependency tables.
[0092] Through the above methods, this application can achieve automated organizational connection management, node collaborative status generation and downstream flow control, and can also retain a manual review entry when cross-organizational data is incomplete or there are disputes over vouchers, thus adapting to the actual situation of rapid style changes and complex organizational collaborative relationships in light industrial outsourcing production.
[0093] This embodiment also provides a collaborative production system for light industry based on industrial internet, such as... Figure 8 As shown, it includes an organization connection module, an order node acquisition module, a sub-process receiving module, a mapping establishment module, a condition generation module, a consistency verification module, a node status generation module, and a flow control module.
[0094] The organization connection module is used to establish organizational connections between a first production organization and a second production organization within the same industrial interconnection collaborative application. The order node acquisition module is used to acquire light industrial orders uploaded by the first production organization and their upstream production nodes. The sub-process receiving module is used to receive sub-process nodes submitted by the second production organization. The mapping establishment module is used to determine the process coverage matching value of sub-process nodes to upstream production nodes based on the process route and the name, order, and quantity of sub-process nodes, and to establish a parent-child mapping relationship when preset mapping conditions are met. The condition generation module is used to generate sub-completion conditions for each sub-process node based on the parent-child mapping relationship and node completion conditions. The consistency verification module is used to receive the status, quantity, and return documents sequentially from each sub-process node, and to perform consistency verification based on the sub-completion conditions. The node status generation module is used to include sub-process nodes that pass the consistency verification in the node collaboration status and compare it with the node completion conditions. The flow control module is used to determine the node gap type based on the unmet sub-completion conditions when the node collaboration state does not meet the node completion conditions, and to lock the affected downstream production nodes based on the node gap type and downstream dependencies; it is also used to update the upstream production node to completion and trigger the flow of downstream production nodes when the node collaboration state meets the node completion conditions.
[0095] In one optional implementation, the system may further include a table configuration module and a manual review module. The table configuration module is used to configure the organizational connection table, process route table, sub-process node table, process coverage matching table, sub-completion condition table, and downstream dependency table. The manual review module is used to receive manual review results and write them back to the corresponding table or node status record when there is an organizational connection request confirmation, insufficient process coverage matching, returned vouchers not meeting voucher requirements, disputes over node gap types, or disputes over the scope of downstream production node locking.
[0096] The specific execution process of each module in the above system can be referred to the corresponding steps in the aforementioned method embodiments, and will not be repeated here. Each module can be implemented by software programs, hardware circuits, or a combination of software and hardware, as long as it can complete the corresponding data acquisition, organization and connection, matching, verification, state generation, and flow control functions.
[0097] This application also provides an electronic device, which may include a processor, a memory, a communication interface, and a bus. The processor, the memory, and the communication interface are interconnected via the bus. The memory stores a computer program, which, when executed by the processor, implements the aforementioned collaborative production method for light industry based on industrial interconnection.
[0098] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the aforementioned collaborative production method for light industry based on industrial interconnection. The computer-readable storage medium can be a read-only memory, random access memory, magnetic disk, optical disk, flash memory, or other media capable of storing computer programs.
[0099] It should be noted that, in this document, the terms "comprising," "including," and any other variations are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Specific examples have been used in this document to illustrate the principles and implementation methods of the technical solutions of this application. The above examples are only for the purpose of helping to understand the methods and core ideas of this application. The above descriptions are merely preferred embodiments of this application. It should be pointed out that, due to the limitations of written expression and the objective existence of infinite specific structures, those skilled in the art can make several improvements, modifications, or changes without departing from the principles of this application, and can also combine the above technical features in an appropriate manner; these improvements, modifications, changes, or combinations, or the direct application of the concept and technical solutions of this application to other situations without modification, should all be considered within the scope of protection of this application.
Claims
1. A collaborative production method for light industry based on industrial internet, characterized in that, include: Obtain the light industrial orders and upstream production nodes uploaded by the first production organization. The upstream production nodes include node completion conditions, process routes, and downstream dependencies. Receive sub-process nodes submitted by the second production organization, wherein the sub-process nodes include name, sequence, quantity, status and return voucher; The process coverage matching value of the sub-process node to the upstream production node is determined according to the process route and the name, and a parent-child mapping relationship is established when the preset mapping conditions are met. Based on the parent-child mapping relationship and the node completion conditions, generate the sub-completion conditions for each sub-process node; Receive the status, quantity, and return documents from each of the sub-process nodes in the order stated, and perform a consistency check based on the sub-completion conditions; Sub-process nodes that pass the consistency check are included in the node collaboration status and compared with the node completion conditions. If not satisfied, the node gap type is determined based on the unsatisfied sub-completion conditions, and the affected downstream production nodes are locked based on the node gap type and the downstream dependency relationship. If the conditions are met, the upstream production node is updated to complete and the downstream production node is triggered to start its process.
2. The method according to claim 1, characterized in that, Before obtaining the light industrial orders and upstream production nodes uploaded by the first production organization, the process also includes: Establish organizational connections between the first production organization and the second production organization within the same industrial interconnection collaborative application; The organizational connection relationship is formed by one of the first production organization or the second production organization initiating the organizational connection request and the other party confirming it; The organizational connection relationship is used to allow both parties to issue light industrial orders, accept nodes, submit sub-process nodes, send status updates, and upload feedback vouchers within the industrial interconnection collaborative application.
3. The method according to claim 1, characterized in that, Determining the process coverage matching value of the sub-process node to the upstream production node based on the process route and the name includes: Extract the necessary process items and sequential connection items corresponding to the upstream production nodes from the process route; The names, order, and quantity of each sub-process node are matched with the necessary process items and the sequential connection items to obtain process item coverage results, order coverage results, and quantity coverage results. The process coverage matching value is determined based on the process item coverage results, the order coverage results, and the quantity coverage results.
4. The method according to claim 3, characterized in that, Establish parent-child mapping relationships when preset mapping conditions are met, including: When the process coverage matching value is not lower than the preset coverage threshold, and the sub-process chain formed by the sub-process nodes in the order can cover the necessary process items corresponding to the upstream production node, the upstream production node is taken as the parent node, and each of the sub-process nodes participating in the coverage is taken as the child node, and the parent-child mapping relationship is established. When there are necessary process items that are not covered, a complete mapping relationship is not established.
5. The method according to claim 1, characterized in that, Based on the parent-child mapping relationship and the node completion conditions, sub-completion conditions for each sub-process node are generated, including: According to the parent-child mapping relationship, determine the upstream production node process content covered by each of the sub-process nodes; The completion status, completion quantity, and document requirements corresponding to the upstream production node process content in the node completion conditions are decomposed to the corresponding sub-process nodes to obtain the status requirements, quantity requirements, and document requirements corresponding to each sub-process node. The status requirements, quantity requirements, and voucher requirements corresponding to the same sub-process node are combined to generate the sub-completion conditions for that sub-process node; The status requirement is used to limit the node status that can be counted as completed, the quantity requirement is used to limit the range of the number of backhauls that can be counted as completed, and the voucher requirement is used to limit the type, time and source of the backhaul vouchers that can be counted as completed.
6. The method according to claim 5, characterized in that, Perform consistency verification based on the aforementioned sub-completion conditions, including: Verify, according to the status requirements, whether the status returned by the sub-process node is a completed status, a verified status, or a quality inspection passed status; Verify whether the number of data returned by the sub-process node reaches the corresponding required quantity based on the quantity requirements; Verify whether the type, time, and source of the returned voucher match the corresponding sub-process node according to the voucher requirements; When the status, quantity, and returned voucher all meet the corresponding sub-completion conditions, the sub-process node is determined to have passed the consistency check.
7. The method according to claim 6, characterized in that, Sub-process nodes that pass the consistency check will be included in the node collaboration status, including: Read the sub-process nodes that have passed the consistency check according to the parent-child mapping relationship, and determine the completed sub-process chain according to the order; When the sequential continuity, cumulative completed quantity, and integrity of the returned voucher of the completed sub-process chain all meet the node completion conditions, a node collaboration state indicating that the upstream production node can be completed is generated. Otherwise, a node collaboration state is generated indicating that the upstream production node cannot complete the process.
8. The method according to claim 7, characterized in that, The node gap type is determined based on the unmet sub-completion conditions, including: When there are unsubmitted child process nodes in the parent-child mapping relationship, the node gap type is determined to be a missing child process; When the number of feedbacks from the sub-process node does not meet the required number, the node gap type is determined to be insufficient quantity. When the returned voucher does not meet the voucher requirements, the node gap type is determined to be voucher missing; When the order of the sub-process nodes does not meet the process route, the node gap type is determined to be an order anomaly.
9. The method according to claim 8, characterized in that, Based on the node gap type and the downstream dependency, the affected downstream production nodes are identified, including: The sub-completion conditions that each downstream production node depends on are determined based on the downstream dependencies. The dependent sub-completion conditions are matched with the unmet sub-completion conditions corresponding to the node gap type to obtain the affected downstream production nodes, and the affected downstream production nodes are kept in a prohibited startup state until the corresponding node gap type is eliminated. For downstream production nodes that are not matched with the node gap type, maintain their original flow status.
10. A collaborative production system for light industry based on industrial internet, characterized in that, include: The organization connection module is used to establish organizational connection relationships between a first production organization and a second production organization within the same industrial interconnection collaborative application. The order node acquisition module is used to acquire light industrial orders uploaded by the first production organization and upstream production nodes; The sub-process receiving module is used to receive sub-process nodes submitted by the second production organization; The mapping establishment module is used to determine process coverage matching values and establish parent-child mapping relationships; The condition generation module is used to generate sub-completion conditions; The consistency verification module is used to perform consistency verification on the status, quantity and return vouchers of the returned data according to the sub-completion conditions. The node status generation module is used to include sub-process nodes that have passed the consistency verification into the node collaboration status and compare it with the node completion conditions. The flow control module is used to lock the affected downstream production node when the node collaboration state does not meet the node completion condition, or to trigger the flow of the downstream production node when the node collaboration state meets the node completion condition.
