A method and system for dynamically merging and splitting quality document elements of manufacturing enterprises

Abstract

The present invention provides a method and system for dynamically merging and splitting elements of quality documents of manufacturing enterprises, which relate to the field of data processing technology. The method comprises the following steps: when a user selects multiple elements, an editable merging pop-up window is triggered, the system extracts the attributes of the elements to be merged and determines the independent element codes of the merged elements according to the coding rules; when the user selects a single element, an extensible splitting pop-up window is triggered, the system supports the split-generated elements to inherit some attributes of the elements to be split and allows editing of the key field content of the split-generated elements, and sets codes for the split-generated elements; constructs a triple model, formulates an element blood relationship chain, maintains a version history and a substitution relationship table, solidifies an operation log, and forms a merging and splitting result; and presents the result to the user through a multi-tab architecture of a details page, thereby solving the problems of chaotic data association and difficult tracing in the prior art, improving the processing efficiency and standardization of quality documents, and being suitable for the digital management of the quality system of manufacturing enterprises.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a method and system for dynamically merging and splitting quality document elements of a manufacturing enterprise. Background Art

[0002] In manufacturing companies' quality system management, quality document elements, such as process specifications, technical requirements, and inspection standards, often have complex attributes and relationships. As business expands, users often need to partially modify or consolidate existing data. For example, they can modify only a few data attributes and automatically reuse the remaining attributes to generate new data, or merge multiple data items into a single one or split a single data item into multiple ones.

[0003] However, existing technologies often have significant flaws when handling these operations. For example, merged or split data often lacks an automatic association mechanism, making it difficult to trace the source and evolution of large amounts of data, increasing the complexity of quality system maintenance. Existing methods may also require manual processing of data attribute copying, file merging, and relationship mapping operations, which are error-prone and time-consuming. Furthermore, they cannot intuitively display data version changes, substitution relationships, and merge and split history, hindering root cause analysis of quality issues.

[0004] Therefore, it is necessary to provide a method and system for dynamically merging and splitting quality document elements of manufacturing enterprises to solve the above technical problems. Summary of the Invention

[0005] In order to solve the above technical problems, the present invention provides a method and system for dynamically merging and splitting quality document elements of a manufacturing enterprise, which is used to solve the problems in the existing technology of chaotic data association, difficult traceability, and poor processing efficiency and standardization of quality documents.

[0006] The present invention provides a method for dynamically merging and splitting quality document elements of a manufacturing enterprise, the method comprising:

[0007] When the user selects multiple elements, the editable merge pop-up window is triggered. The system automatically extracts the merged element attributes of the elements to be merged and determines the independent element code corresponding to the merged elements according to the preset coding rules;

[0008] When the user terminal selects a single element, an expandable split pop-up window is triggered. The system supports the split-generated element to inherit the split element attributes of the element to be split and allows editing of the key field content of the split-generated element, and sets the corresponding independent element code for the split-generated element;

[0009] The system constructs a triple model based on the independent element coding, formulates the element lineage relationship chain, maintains the version history table and the substitution relationship table, solidifies the operation log, and forms a dynamic merging and splitting result;

[0010] The system displays the dynamic merging and splitting results to the user terminal through a multi-tab architecture of the details page.

[0011] Preferably, when the user terminal selects multiple elements, an editable merge pop-up window is triggered, and the system automatically extracts the merged element attributes of the elements to be merged and determines the independent element code corresponding to the merged element according to the preset coding rules, specifically including:

[0012] After the user terminal batch-selects multiple elements to be merged in the quality element library that are in a published state and do not have invalid fields, the system performs a quantity check on the elements to be merged. If the check passes, the element merge button is activated. If the check fails, the element merge button is grayed out and an error message is popped up;

[0013] After the user clicks the element merge button, the editable merge pop-up window is triggered, and the system automatically extracts the merge element attributes of the elements to be merged, namely, element content, associated quality process, associated quality requirement document and version number, and fills them into the editable merge pop-up window. At the same time, the user is supported to manually modify the attribute conflicts between the elements to be merged;

[0014] The system determines the independent element code corresponding to the merged element according to the preset coding rule, and unifies the check digits of the independent element code through a hash algorithm;

[0015] After the merging operation is completed, the status of the element to be merged is marked as invalid, and the status of the merged element is marked as pending release;

[0016] After the user terminal confirms to publish the merged element, the state of the merged element is changed to a published state.

[0017] Preferably, the attribute conflict includes, but is not limited to, inconsistency in the content of the elements to be merged, duplication of the associated quality processes, or different version numbers;

[0018] After the user terminal modifies the attribute conflict, the system automatically performs a secondary attribute check on the elements to be merged until the attribute conflict does not exist between the elements to be merged.

[0019] Preferably, when the user terminal selects a single element, an expandable split pop-up window is triggered, and the system supports the split-generated element to inherit the split element attributes of the element to be split and allows editing of the key field content of the split-generated element, and sets the corresponding independent element code for the split-generated element, specifically including:

[0020] After the user terminal selects a single published element to be split, and clicks the element split button, the system automatically pops up the expandable split pop-up window containing one split item, and supports the user terminal to click the item add button to add the split item, and the upper limit of the number of split items is 10;

[0021] The system supports the split generation element to automatically inherit the split element attributes of the element to be split, namely the associated quality process, the associated quality requirement document and the version number. At the same time, the system clears the key field content of the split generation element, namely the item number and element content, and allows the user to customize the key field content;

[0022] The system sets the corresponding independent element code for the split-generated element, and embeds the first 6 digits of the element number of the element to be split into the independent element code as a split parent identifier;

[0023] After the split operation is completed, the status of the element to be split is marked as invalid, and the status of the element generated by the split is marked as to be published;

[0024] After the user terminal confirms the release of the split generation element, the state of the split generation element is changed to a released state.

[0025] Preferably, the split parent identifier occupies the first 6 digits of the independent element code corresponding to the split generation element, and is the same as the first 6 digits of the independent element code corresponding to the element to be split, wherein a coding mapping relationship is formed between the element to be split and the split generation element.

[0026] Preferably, the construction process of the triple model is as follows:

[0027] Based on the independent element coding, constructing the triple model based on element entities, operation types and association relationships, and storing the triple model in a graph element library;

[0028] The graph element library uses an adjacency list to store nodes and edges, the nodes are used to mark the element entities, the edges are used to mark the operation types and the association relationships, and the graph element library supports multi-dimensional association queries.

[0029] Preferably, the process of establishing the element blood relationship chain is as follows:

[0030] Based on the triple model, the element list of the elements to be merged, the number of the elements generated by the merger, the element merging time and the element attribute integration rules are obtained to generate a merge operation record. At the same time, the number of the elements to be split, the element list of the elements generated by the split, the element splitting time and the element attribute inheritance rules are obtained to generate a split operation record. The element blood relationship chain is formulated according to the merge operation record and the split operation record.

[0031] Preferably, the multi-tab architecture of the details page includes an element information tab, a merge and split history tab, a history version tab, and an alternative relationship tab, and adopts a responsive layout design;

[0032] The merge and split history tab displays the element lineage relationship chain in the form of a directed acyclic graph;

[0033] The History Version tab arranges the element version records in the Version History table in reverse chronological order and supports version comparison and version rollback functions;

[0034] The substitution relationship tab is used to display the element substitution relationship in the substitution relationship table, and supports keyword search and export functions.

[0035] Preferably, in the merge and split history tab, based on the form of the directed acyclic graph, each element is regarded as a module, the element status is distinguished by the color of the submodules in each module, and the direction of the element evolution is indicated by the direction of the arrow of the module connection edge, and after the user terminal clicks on any of the modules, the merge and split history tab jumps to the element information tab of the element corresponding to the module;

[0036] The version comparison function highlights the changed parts of feature attributes through a differentiation algorithm, and before the version rollback function is run, the user terminal's authority needs to be successfully verified.

[0037] A system for dynamically merging and splitting quality document elements of a manufacturing enterprise, the system comprising:

[0038] Merge module: When the user selects multiple elements, the editable merge pop-up window is triggered. The system automatically extracts the merged element attributes of the elements to be merged and determines the independent element code corresponding to the merged element according to the preset coding rules;

[0039] A splitting module is used to trigger an expandable splitting pop-up window when the user terminal selects a single element. The system supports the split-generated element to inherit the split element attributes of the element to be split and allows editing of the key field content of the split-generated element, and sets the corresponding independent element code for the split-generated element;

[0040] A result module is used for the system to construct a triple model based on the independent element coding, formulate an element lineage relationship chain, maintain a version history table and a substitution relationship table, solidify the operation log, and form a dynamic merge and split result;

[0041] The display module is used by the system to display the dynamic merging and splitting results to the user terminal through the multi-tab architecture of the details page.

[0042] Compared with related technologies, the method and system for dynamically merging and splitting quality document elements of manufacturing enterprises provided by the present invention have the following beneficial effects:

[0043] When the user terminal selects multiple elements, the present invention triggers an editable merge pop-up window, and the system automatically extracts the merge element attributes of the elements to be merged and determines the independent element code corresponding to the merged element according to the preset coding rules; when the user terminal selects a single element, the extensible split pop-up window is triggered, and the system supports the split generated element to inherit the split element attributes of the elements to be split and allows editing of the key field content of the split generated element, and sets the corresponding independent element code for each split generated element; the system constructs a triple model based on the independent element code, formulates the element blood relationship chain, maintains the version history table and the substitution relationship table, solidifies the operation log, and forms a dynamic merge and split result; the system displays the dynamic merge and split result to the user terminal through the multi-tab architecture of the details page, thereby solving the problems of chaotic data association and difficult tracing in the existing technology, significantly improving the processing efficiency and standardization of quality documents, and is suitable for the digital management of the quality system of manufacturing enterprises.

[0044] The present invention can reduce the number of times users repeatedly input data and significantly improve the efficiency of merge and split operations through dynamic triggering of pop-up windows and automatic inheritance of attributes. The method of the present invention can automatically maintain the hierarchical relationship and version history of data, support tracing the source, evolution process and replacement logic of any data in seconds, and significantly reduce the audit cost of the quality system of manufacturing enterprises. The present invention can avoid the problems of confusing data associations and difficult tracing by unifying factor coding rules and status management mechanisms, and significantly improve the standardization and consistency of quality documents. The method of the present invention can intuitively display data associations through the multi-tab architecture of the details page, assisting users in integrating and optimizing quality factors. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Figure 1 A flowchart of a method for dynamically merging and splitting quality document elements of a manufacturing enterprise provided by an embodiment of the present invention;

[0046] Figure 2 A system block diagram of a system for dynamically merging and splitting quality document elements of a manufacturing enterprise provided by an embodiment of the present invention;

[0047] Figure 3A schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0048] To make the objectives, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts shall fall within the scope of protection of the present invention.

[0049] like Figure 1 FIG. 1 is a flowchart of a method for dynamically merging and splitting quality document elements of a manufacturing enterprise provided by an embodiment of the present invention. Figure 1 The execution subject of the method shown may be a software and / or hardware device. The execution subject of the present application may include but is not limited to at least one of the following: user equipment, network equipment, etc. Among them, user equipment may include but is not limited to computers, smart phones, personal digital assistants (PDAs) and the electronic devices mentioned above. Network equipment may include but is not limited to a single network server, a server group consisting of multiple network servers, or a cloud based on cloud computing consisting of a large number of computers or network servers, wherein cloud computing is a type of distributed computing, a super virtual computer composed of a group of loosely coupled computers. This embodiment does not limit this. It includes steps S1 to S4, as follows:

[0050] S1, when the user selects multiple elements, the editable merge pop-up window is triggered, and the system automatically extracts the merged element attributes of the elements to be merged and determines the independent element code corresponding to the merged element according to the preset coding rules;

[0051] The user end refers to the user's terminal. When a user selects multiple data items in the quality factor library, a visual interactive window pops up, which is the editable merge pop-up window. This window dynamically generates editable areas for displaying and adjusting the merged data attributes. It also supports manual modification of conflicting information, such as unifying version numbers and correcting duplicate processes.

[0052] Merged element attributes refer to the core information of the elements to be merged that need to be integrated, including but not limited to: element content, such as the specific requirements of the quality process "This process specifies the planning, implementation, and evaluation management requirements for quality improvement"; related quality processes, such as the name and version of the quality system process to which the element is attached "Improvement Identification Management Process V1.0"; related quality files, such as the name and version of the quality file to which the element belongs "File 1 (V1.0)", "File 2 (V2.0)".

[0053] The preset coding rules are a set of standardized coding generation logic, usually including multiple levels of fields, namely, the enterprise code, such as "HB", representing a certain enterprise; the timestamp, such as "20241012", indicating the operation date; the serial number, such as "001", "002", and "003", indicating the sequential identification in ascending order by day; the operation identifier, such as "M", indicating the merge operation, to distinguish it from the split identifier "S". The independent element code is a unique identifier generated by the above coding rules, such as "HB-20241012-001-M". It has a unified check digit, that is, an anti-counterfeiting code generated by a hash algorithm to ensure the uniqueness, traceability, and tamper-proofness of the code. In addition, based on the preset coding rules, the system can separate the contents of all elements to be merged with semicolons and support users to manually edit these contents.

[0054] This approach significantly improves data processing efficiency, reduces the time and effort associated with manual data collection and organization, and reduces the probability of errors. Furthermore, the automated extraction mechanism avoids information omissions and ensures the integrity of the merged data. Furthermore, the unique and systematic nature of the independent element codes generated based on pre-set coding rules facilitates data classification, retrieval, and management, providing clear and accurate identification for subsequent quality documentation traceability and analysis, thereby enhancing data traceability and standardized management.

[0055] S2: When the user terminal selects a single element, an expandable split pop-up window is triggered. The system supports the split-generated element to inherit the split element attributes of the element to be split and allows editing of the key field content of the split-generated element, and sets the corresponding independent element code for the split-generated element;

[0056] The expandable split pop-up window appears when the user selects a single data item and clicks the Split button. This window contains one split item by default and allows users to add new items by clicking the Add Item button. For example, when splitting a feature into three elements, two more items may be added to meet flexible splitting requirements. Furthermore, the number of split items can be configured by the user, with a maximum limit of 10.

[0057] Split feature attributes refer to the basic attributes associated with the parent data that are automatically inherited by the child data during the split. These include: associated quality processes, such as the "Improved Identification Management Process V1.0" associated with the parent data; associated quality files, such as "File 1 (V1.0)" associated with the parent data; and feature types, such as the type label "Group Requirements." This inheritance mechanism eliminates the need for users to repeatedly enter basic information, thereby improving feature splitting efficiency.

[0058] Key field content refers to the core information defined by the user after splitting. This includes: item number, such as splitting the parent data "1-1" into "1-1-1" and "1-1-2"; element content, which can be adjusted for different application scenarios, such as splitting "This standard applies to the aerospace field" into "This standard applies to space launch vehicles" and "This standard applies to satellite manufacturing." Furthermore, the rules for setting independent element codes for split elements are similar to those for merged elements.

[0059] This approach ensures data consistency and coherence, giving users the flexibility to customize data splits to meet diverse business needs. The attribute inheritance mechanism reduces the need for users to repeatedly enter basic information, improving operational efficiency. Users can customize key field content to accommodate differentiated data requirements in different scenarios. Furthermore, independent element coding provides clear identification for split data, facilitating tracking and management, and ensuring data accuracy and traceability.

[0060] S3, the system constructs a triple model based on the independent element code, formulates the element lineage relationship chain, maintains the version history table and the substitution relationship table, solidifies the operation log, and forms a dynamic merging and splitting result;

[0061] In the field of quality document management for manufacturing enterprises, the triple model is a structured model used to record data relationships. The element lineage chain can record the evolution of quality document elements during merging and splitting, and clearly define the relationships between elements. For example, when multiple elements are merged to form a single element, or when a single element is split into multiple elements, the lineage chain can trace the source and destination of these elements, ensuring data traceability.

[0062] The version history table refers to a table used to record version changes of quality document elements. The table contains information such as version number, modification time, modifier, and modification content, and a new version record is generated every time an element changes. With the help of the version history table, enterprises can view historical versions of elements and conduct comparative analysis to clarify the details of changes, meet audit and backtracking requirements, and improve the efficiency and accuracy of quality control and problem solving. The substitution relationship table refers to a table used to record the substitution relationship between new and old elements. It covers the number of the substitution element, the number of the replaced element, the effective time, and the reason for the substitution. Through the substitution relationship table, enterprises can clearly understand which elements will be replaced, when they will be replaced, and why they will be replaced, thereby effectively avoiding the use of invalid data and ensuring the accuracy and effectiveness of quality documents.

[0063] The operation log records every merge or split of quality document elements in detail, including the operation type, element number, operation time, operation type, and user information. Furthermore, the operation log cannot be tampered with, making it a crucial basis for compliance reviews. The operation log allows you to track the operation process, ensuring security and auditability.

[0064] Dynamic merging and splitting results are the results of merging or splitting quality document elements, including the generated new elements, element codes, and new relationships between elements. This result integrates all of these elements and presents them to users in a visual manner, forming a complete data management closed loop, providing companies with clear and accurate quality document management data.

[0065] Through these operations, the system can establish a comprehensive, multi-layered data association network, known as a triplet model. The element lineage chain makes the entire data evolution process clear and explicit. The version history table records the trajectory of data changes, the substitution relationship table clarifies the substitution logic between data, and the operation log provides an audit basis for data operations. This not only facilitates in-depth analysis and management decision-making of quality documents, but also enables enterprises to quickly identify data issues, improve data quality, and meet enterprise requirements for data compliance and auditability.

[0066] S4, the system displays the dynamic merging and splitting results to the user terminal through a multi-tab architecture of the details page.

[0067] The multi-tabbed details page architecture refers to an architecture that sets up multiple tabs within the quality factor details page to display information in different dimensions. This architecture presents complex data in a categorized and clear manner, allowing users to quickly switch pages to view information in different dimensions, such as basic information, merge and split history, version history, and substitution relationships. This visual display method greatly enhances the user experience and improves the readability and comprehensibility of data, helping users quickly grasp the overall data picture, facilitating data comparison, analysis, and decision-making, improving work efficiency, and promoting the digitalization and intelligentization of enterprise quality document management.

[0068] In the specific implementation process, when the user terminal selects multiple elements, the editable merge pop-up window is triggered, and the system automatically extracts the merged element attributes of the elements to be merged and determines the independent element code corresponding to the merged element according to the preset coding rules, specifically including:

[0069] After the user terminal batch-selects multiple elements to be merged in the quality element library that are in a published state and do not have invalid fields, the system performs a quantity check on the elements to be merged. If the check passes, the element merge button is activated. If the check fails, the element merge button is grayed out and an error message is popped up;

[0070] After the user clicks the element merge button, the editable merge pop-up window is triggered, and the system automatically extracts the merge element attributes of the elements to be merged, namely, element content, associated quality process, associated quality requirement document and version number, and fills them into the editable merge pop-up window. At the same time, the user is supported to manually modify the attribute conflicts between the elements to be merged;

[0071] The system determines the independent element code corresponding to the merged element according to the preset coding rule, and unifies the check digits of the independent element code through a hash algorithm;

[0072] After the merging operation is completed, the status of the element to be merged is marked as invalid, and the status of the merged element is marked as pending release;

[0073] After the user terminal confirms to publish the merged element, the state of the merged element is changed to a published state.

[0074] The attribute conflict includes but is not limited to the inconsistency of the element contents between the elements to be merged, the duplication of the associated quality processes, or the different version numbers;

[0075] After the user terminal modifies the attribute conflict, the system automatically performs a secondary attribute check on the elements to be merged until the attribute conflict does not exist between the elements to be merged.

[0076] As you can understand, the quality element library, as the core data storage area for enterprise quality document management, contains numerous critical quality-related information. When performing operations within the quality element library, users must batch-select multiple elements to be merged that are in the published state and do not contain invalid fields. The published state indicates that these elements have passed review and are officially in use, while the absence of invalid fields ensures data availability and reliability.

[0077] Once the user completes their selection, the system immediately initiates a quantity verification process. This verification ensures that the number of selected features meets the minimum requirements for the merge operation, preventing subsequent problems caused by selecting too few or too many features. If the verification passes, the system activates the Merge Feature button, allowing the user to proceed with the merge operation. If the verification fails, the Merge Feature button is grayed out, rendering it inoperable, and an error message appears, informing the user of the specific reason for the verification failure and guiding the user to make the correct selection.

[0078] When the user clicks the Merge Elements button, the system will trigger an editable merge pop-up window. This pop-up window provides users with an intuitive interactive interface for further processing and adjustment of the merged elements. Then, the system will automatically extract the merged element attributes of the elements to be merged. These attributes cover key information such as element content, associated quality processes, associated quality requirements documents, and version numbers. Specifically, the element content is a detailed description of the specific quality requirements in the quality document, the associated quality process and the associated quality requirements document clarify the application scenario and basis of the element in the entire quality system, and the version number records the change history and current status of the element. The system fills these attributes into the editable merge pop-up window for user viewing and modification.

[0079] Furthermore, the features to be merged may originate from different data sources or undergo different editing processes, leading to attribute conflicts. These may include, but are not limited to, inconsistent feature content, duplicate associated quality processes, or different version numbers. For example, different features may have inconsistent requirements for the same quality indicator, multiple features may be associated with the same quality process but with different versions, or the version numbers may be inconsistent. These attribute conflicts may affect the accuracy and consistency of the merged data. In these cases, the system supports users to manually correct these attribute conflicts.

[0080] After the user successfully corrects the attribute conflicts, the system automatically performs a secondary attribute check on the features to be merged. This check uses pre-set algorithms and rules to re-check the consistency of the attributes between the features. Only when there are no attribute conflicts between the features to be merged does the system confirm that the preparation for the merge operation is complete.

[0081] At the same time, the system determines the corresponding independent element codes for the merged elements based on pre-defined coding rules. Pre-defined coding rules are a set of strictly defined code generation logic that ensures the uniqueness and traceability of the generated codes. To further ensure the accuracy and integrity of the codes, the system uses a hashing algorithm to unify the check digits of the independent element codes.

[0082] It should be noted that the hash algorithm is an algorithm that converts data of arbitrary length into a fixed-length hash value. By performing hash calculation on the code to generate a check digit, it is possible to verify whether the code has been tampered with or damaged during transmission or storage.

[0083] When the merge operation is complete, the system marks the element status. Specifically, since the element to be merged has already been involved in the merge, its original status is no longer applicable and is therefore marked as obsolete. The newly generated merged element is in a pending release state until it is confirmed by the user. Only after the user confirms the release of the merged element will its status change to released and officially become valid data in the enterprise's quality document management system. Through such a rigorous status management mechanism, the system can clearly track and manage the lifecycle of quality document elements, ensure data accuracy and reliability, and provide strong support for quality management in manufacturing enterprises.

[0084] When the user terminal selects a single element, an expandable split pop-up window is triggered. The system supports the split-generated element to inherit the split element attributes of the element to be split and allows editing of the key field content of the split-generated element, and sets the corresponding independent element code for the split-generated element, specifically including:

[0085] After the user terminal selects a single published element to be split, and clicks the element split button, the system automatically pops up the expandable split pop-up window containing one split item, and supports the user terminal to click the item add button to add the split item, and the upper limit of the number of split items is 10;

[0086] The system supports the split generation element to automatically inherit the split element attributes of the element to be split, namely the associated quality process, the associated quality requirement document and the version number. At the same time, the system clears the key field content of the split generation element, namely the item number and element content, and allows the user to customize the key field content;

[0087] The system sets the corresponding independent element code for the split-generated element, and embeds the first 6 digits of the element number of the element to be split into the independent element code as a split parent identifier;

[0088] After the split operation is completed, the status of the element to be split is marked as invalid, and the status of the element generated by the split is marked as to be published;

[0089] After the user terminal confirms the release of the split generation element, the state of the split generation element is changed to a released state.

[0090] The split parent identifier occupies the first 6 digits of the independent element code corresponding to the split generation element, and is the same as the first 6 digits of the independent element code corresponding to the element to be split, wherein a coding mapping relationship is formed between the element to be split and the split generation element.

[0091] In practice, when a user selects a single, published feature to be split, the system's pre-set splitting mechanism is triggered. Clicking the "Split Feature" button automatically displays an expandable splitting pop-up window. This window initially contains one split entry, providing the user with a basic splitting operation unit. The system also boasts a well-designed interactive interface, allowing users to add new split entries by clicking the "Add Entries" button. A maximum number of split entries is also set, ensuring that this limit meets the potential splitting requirements of most business scenarios while preventing data management confusion caused by excessive splitting.

[0092] The system follows pre-defined inheritance and editing rules for attribute handling of split-generated features. Split-generated features automatically inherit the split feature attributes of the feature to be split, including the associated quality process, associated quality requirements document, and version number. This automatic inheritance of these attributes ensures the coherence and consistency of the split data within the quality system.

[0093] At the same time, the system automatically clears key fields of the split elements, such as the item number and element content, allowing users to customize this key information based on specific business needs. Users can flexibly adjust the specific identification and detailed content of the split elements to meet the differentiated requirements of quality document elements in different scenarios.

[0094] In order to ensure the uniqueness and traceability of the split-generated elements, the system will set the corresponding independent element code for it. During the coding setting process, the system can embed the first 6 digits of the number of the element to be split in the independent element code as the split parent identifier. This split parent identifier occupies the first 6 digits of the independent element code corresponding to the split-generated element, and is the same as the first 6 digits of the independent element code corresponding to the element to be split, so that a close coding mapping relationship can be formed between the element to be split and the split-generated element. Through the coding of the split-generated element, the original element to be split can be quickly traced back, which greatly facilitates the management, query and analysis of data, and helps enterprises to fully grasp the evolution process of quality document elements.

[0095] The system also has clear regulations for element status management. Once a split operation is completed, the element to be split is split, and its original status is no longer applicable, so it can be marked as obsolete. However, the newly generated split element remains in a pending release state until it is finally confirmed by the user. Only after the user confirms the release of the split element does its status change to released, officially becoming valid data in the enterprise quality document management system. This status management mechanism helps the system clearly track and manage the lifecycle of quality document elements, avoid interference from invalid data, and ensure data accuracy and reliability.

[0096] Through the above series of operational processes and technical designs, flexible splitting, attribute inheritance, coding management and status control of single elements can be achieved, which provides strong support for enterprises to efficiently manage quality document elements and helps to improve the level of refinement of enterprise quality management and overall operational efficiency.

[0097] The construction process of the triplet model is as follows:

[0098] Based on the independent element coding, constructing the triple model based on element entities, operation types and association relationships, and storing the triple model in a graph element library;

[0099] The graph element library uses an adjacency list to store nodes and edges, the nodes are used to mark the element entities, the edges are used to mark the operation types and the association relationships, and the graph element library supports multi-dimensional association queries.

[0100] It's important to note that independent element codes uniquely identify quality document elements and carry a wealth of information. Based on these codes, a ternary model can be constructed, consisting of three core components: element entities, operation types, and relationships. The element entities, representing the various elements in the quality document, serve as the data backbone of the model; operation types can include merges and splits; and relationships define the connections between element entities and between element entities and operation types, which can range from causal relationships to hierarchical relationships.

[0101] Furthermore, the constructed triple models can be stored in the graph feature library. The graph feature library serves as a database specifically for storing and managing these models, facilitating subsequent data query and analysis. The graph feature library uses adjacency lists to store nodes and edges. Adjacency lists are a commonly used storage method in graph data structures that organize data in an efficient manner. In this application scenario, nodes are used to mark feature entities. Each node represents a specific quality document feature, and the relevant information of the feature can be quickly located and accessed through the nodes. Edges are used to mark operation types and associations. The existence of edges not only connects the nodes but also carries the operation and association information between the nodes, so that the relationship between the elements can be clearly presented.

[0102] In addition, the graph feature library supports multi-dimensional association queries. For example, users can query all operation types and associated elements based on a feature entity. They can also search for all elements that perform that operation and their associated relationships based on the operation type. They can also quickly locate feature entities and their associated operation types through their relationships. This multi-dimensional association query capability greatly improves data utilization efficiency, facilitates comprehensive and in-depth analysis and management of quality document elements, and provides strong data support for enterprise decision-making.

[0103] The process of establishing the element blood relationship chain is as follows:

[0104] Based on the triple model, the element list of the elements to be merged, the number of the elements generated by the merger, the element merging time and the element attribute integration rules are obtained to generate a merge operation record. At the same time, the number of the elements to be split, the element list of the elements generated by the split, the element splitting time and the element attribute inheritance rules are obtained to generate a split operation record. The element blood relationship chain is formulated according to the merge operation record and the split operation record.

[0105] In practical applications, the triple model serves as the core architecture for data association, specifically including key information such as feature entities, operation types, and association relationships. Based on this model, the system can accurately obtain data related to merge and split operations. During a merge operation, the system obtains a list of features consisting of the features to be merged. This list records in detail the various features involved in the merge, which are the basis for constructing new features; obtains the number of the merged feature, which serves as the unique identifier of the new feature and is used for subsequent data identification and tracking; records the time of feature merging, and accurate time information provides a basis for tracing the order of operations; and clarifies the feature attribute integration rules, which stipulate how to integrate the attributes of the features to be merged to form the attributes of the new feature. With this information, the system can generate a merge operation record, which is the key information of the merge operation.

[0106] During a split operation, the system also needs to obtain the ID of the feature to be split to identify the source feature of the split; obtain a list of the features that make up the split, clearly presenting the new feature set generated after the split; record the time the feature split occurred to clearly identify the time the operation occurred; and obtain the feature attribute inheritance rules to determine how the new feature inherits the original feature attributes. Based on this data, the system can generate a split operation record.

[0107] Finally, the system can create a lineage chain of elements based on the resulting merge and split operation records. By integrating these two types of operation records, the system can clearly identify the relationships between elements during the merge and split process, constructing a chain that reflects the complete process of element generation and evolution. In this chain, each element can be traced back to its source element and the operational process it underwent. This provides strong support for enterprises to deeply analyze the evolution history of quality document elements, track data changes, and ensure data accuracy and consistency. This is of great significance in enterprise quality control and data management processes.

[0108] The multi-tab architecture of the details page includes an element information tab, a merge and split history tab, a historical version tab, and an alternative relationship tab, and adopts a responsive layout design;

[0109] The merge and split history tab displays the element lineage relationship chain in the form of a directed acyclic graph;

[0110] The History Version tab arranges the element version records in the Version History table in reverse chronological order and supports version comparison and version rollback functions;

[0111] The substitution relationship tab is used to display the element substitution relationship in the substitution relationship table, and supports keyword search and export functions.

[0112] In the merge and split history tab, based on the form of the directed acyclic graph, each element is treated as a module, the element status is distinguished by the color of the submodules in each module, and the direction of the element evolution is indicated by the direction of the arrow of the module connection edge, and after the user terminal clicks any of the modules, the merge and split history tab jumps to the element information tab of the element corresponding to the module;

[0113] The version comparison function highlights the changed parts of feature attributes through a differentiation algorithm, and before the version rollback function is run, the user terminal's authority needs to be successfully verified.

[0114] Among them, the responsive layout design allows the page to automatically adjust the layout and style according to the screen size and resolution of different terminal devices, ensuring that users can have a good browsing experience on various devices, and improving the compatibility and usability of the system.

[0115] Specifically, the Merge and Split History tab displays the feature lineage chain in the form of a directed acyclic graph. A directed acyclic graph is a data structure in which nodes represent features and edges represent the evolutionary relationships between features, ensuring the clarity and traceability of the data evolution path.

[0116] In this tab, each feature is considered a module, and the feature status is distinguished by the color of the submodules within the module, such as green for "Published" and gray for "Obsolete," making the feature status clear and intuitive. The direction of the arrows connecting the modules clearly indicates the direction of feature evolution, such as from the feature before the merge to the feature after the merge, or from the feature before the split to the feature after the split. When the user clicks on any module, the Merge and Split History tab will jump to the Feature Information tab for the feature corresponding to that module, allowing users to quickly view detailed basic information about the feature. This interactive design enhances the relevance and accessibility of the data.

[0117] The Historical Versions tab arranges feature version records in the version history table in reverse chronological order. This arrangement aligns with users' preference for viewing the latest changes, allowing them to quickly understand a feature's latest status and historical changes. The Historical Versions tab also includes information such as the version number, feature status, modifier, and modification time. This tab supports version comparison and version rollback. The version comparison feature uses a differentiation algorithm to highlight changes to feature attributes. By comparing the attributes of features from different versions, it accurately identifies and highlights the changes, helping users intuitively understand the differences between feature versions and facilitating data analysis and troubleshooting. The version rollback feature requires successful verification of user permissions before running. This mechanism ensures the security and compliance of version rollback operations, preventing unauthorized users from arbitrarily modifying historical data and ensuring data integrity and reliability. Only users with appropriate permissions, such as administrators or authorized personnel, can perform a version rollback and restore a feature to a previous version state.

[0118] The Substitution Relationship tab is used to display the substitution relationships of elements in the substitution relationship table, and supports keyword search and export functions. The substitution relationship tab covers information such as element number, element content, element type, element status, merge and split history, associated quality process name, associated quality requirement document, and substitution relationship. In complex quality document management, the substitution relationship between elements is relatively complex. Through this tab, users can clearly see the original elements that are replaced and the new elements that are replaced. The keyword search function allows users to quickly locate related substitution relationships based on element numbers, names or other key information, thereby improving search efficiency. The export function allows users to export substitution relationship data to other formats for further analysis, organization, or data interaction with other systems.

[0119] In summary, the multi-tab architecture of the details page provides users with comprehensive, in-depth, and convenient data display and interaction functions through the collaborative work of each tab, effectively improving the efficiency and accuracy of quality document management of manufacturing enterprises.

[0120] like Figure 2 FIG. 1 is a block diagram of a system for dynamically merging and splitting quality document elements of a manufacturing enterprise provided by an embodiment of the present invention. The system includes:

[0121] Merge module: When the user selects multiple elements, the editable merge pop-up window is triggered. The system automatically extracts the merged element attributes of the elements to be merged and determines the independent element code corresponding to the merged element according to the preset coding rules;

[0122] A splitting module is used to trigger an expandable splitting pop-up window when the user terminal selects a single element. The system supports the split-generated element to inherit the split element attributes of the element to be split and allows editing of the key field content of the split-generated element, and sets the corresponding independent element code for the split-generated element;

[0123] A result module is used for the system to construct a triple model based on the independent element coding, formulate an element lineage relationship chain, maintain a version history table and a substitution relationship table, solidify the operation log, and form a dynamic merge and split result;

[0124] The display module is used by the system to display the dynamic merging and splitting results to the user terminal through the multi-tab architecture of the details page.

[0125] Figure 2 The apparatus of the embodiment shown can be used to perform Figure 1 The implementation principles and technical effects of the steps in the method embodiment shown are similar and will not be repeated here.

[0126] An electronic device includes a memory and a processor, wherein a computer program is stored in the memory. When the processor runs the computer program stored in the memory, the processor executes the steps of a method for dynamically merging and splitting quality document elements of a manufacturing enterprise as described in any one of the above.

[0127] like Figure 3 FIG. 1 is a schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present invention. The electronic device 30 includes: a processor 31, a memory 32 and a computer program;

[0128] The memory 32 is used to store the computer program, which may also be a flash memory. The computer program is, for example, an application program or a functional module for implementing the above method.

[0129] The processor 31 is configured to execute the computer program stored in the memory to implement the various steps performed by the device in the above method. For details, please refer to the relevant description in the above method embodiment.

[0130] Optionally, the memory 32 may be independent or integrated with the processor 31 .

[0131] When the memory 32 is a device independent of the processor 31, the device may further include:

[0132] The bus 33 is used to connect the memory 32 and the processor 31 .

[0133] A readable storage medium stores a computer program, which, when executed by a processor, is used to implement the steps of a method for dynamically merging and splitting quality document elements of a manufacturing enterprise as described in any one of the above.

[0134] The readable storage medium may be a computer storage medium or a communication medium. Communication media include any medium that facilitates the transfer of computer programs from one location to another. Computer storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer. For example, a readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium may also be an integral part of the processor. The processor and the readable storage medium may be located in an application-specific integrated circuit (ASIC). In addition, the ASIC may be located in a user device. Of course, the processor and the readable storage medium may also exist as discrete components in a communication device. The readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

[0135] The present invention also provides a program product, which includes execution instructions stored in a readable storage medium. At least one processor of a device can read the execution instructions from the readable storage medium, and at least one processor executes the execution instructions so that the device implements the methods provided in the various embodiments described above.

[0136] In the embodiments of the above-mentioned devices, it should be understood that the processor may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASICs), etc. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the present invention may be directly executed by a hardware processor or by a combination of hardware and software modules within the processor.

[0137] Through the introduction of the above embodiments, the present invention provides a method and system for dynamically merging and splitting elements of quality documents of manufacturing enterprises. When the user terminal selects multiple elements, an editable merging pop-up window is triggered, and the system automatically extracts the merged element attributes of the elements to be merged and determines the independent element code corresponding to the merged generated element according to the preset coding rules; when the user terminal selects a single element, an extensible splitting pop-up window is triggered, and the system supports the split generated element to inherit the split element attributes of the elements to be split and allows editing of the key field content of the split generated element, and sets the corresponding independent element code for each split generated element; the system constructs a triple model based on the independent element code, formulates the element blood relationship chain, maintains the version history table and the substitution relationship table, solidifies the operation log, and forms a dynamic merging and splitting result; the system displays the dynamic merging and splitting results to the user terminal through the multi-tab architecture of the details page, thereby solving the problems of chaotic data association and difficult tracing in the existing technology, significantly improving the processing efficiency and standardization of quality documents, and is suitable for the digital management of the quality system of manufacturing enterprises.

[0138] The present invention can reduce the number of times users repeatedly input data and significantly improve the efficiency of merge and split operations through dynamic triggering of pop-up windows and automatic inheritance of attributes. The method of the present invention can automatically maintain the hierarchical relationship and version history of data, support tracing the source, evolution process and replacement logic of any data in seconds, and significantly reduce the audit cost of the quality system of manufacturing enterprises. The present invention can avoid the problems of confusing data associations and difficult tracing by unifying factor coding rules and status management mechanisms, and significantly improve the standardization and consistency of quality documents. The method of the present invention can intuitively display data associations through the multi-tab architecture of the details page, assisting users in integrating and optimizing quality factors.

[0139] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for dynamically merging and splitting quality document elements of a manufacturing enterprise, characterized in that: The method comprises: When the user selects multiple elements, the editable merge pop-up window is triggered. The system automatically extracts the merged element attributes of the elements to be merged and determines the independent element code corresponding to the merged elements according to the preset coding rules; When the user terminal selects a single element, an expandable split pop-up window is triggered. The system supports the split-generated element to inherit the split element attributes of the element to be split and allows editing of the key field content of the split-generated element, and sets the corresponding independent element code for the split-generated element; The system constructs a triple model based on the independent element coding, formulates the element lineage relationship chain, maintains the version history table and the substitution relationship table, solidifies the operation log, and forms a dynamic merging and splitting result; The system displays the dynamic merging and splitting results to the user terminal through a multi-tab architecture of the detail page; The construction process of the triplet model is as follows: Based on the independent element coding, constructing the triple model based on element entities, operation types and association relationships, and storing the triple model in a graph element library; The graph element library uses an adjacency table to store nodes and edges, wherein the nodes are used to mark the element entities, and the edges are used to mark the operation types and the association relationships, and the graph element library supports multi-dimensional association queries; The process of establishing the element blood relationship chain is as follows: Based on the triple model, the element list of the elements to be merged, the number of the elements generated by the merger, the element merging time and the element attribute integration rules are obtained to generate a merge operation record. At the same time, the number of the elements to be split, the element list of the elements generated by the split, the element splitting time and the element attribute inheritance rules are obtained to generate a split operation record. The element blood relationship chain is formulated according to the merge operation record and the split operation record.

2. A method for dynamically merging and splitting quality document elements of a manufacturing enterprise according to claim 1, characterized in that: When the user selects multiple elements, the editable merge pop-up window is triggered. The system automatically extracts the merged element attributes of the elements to be merged and determines the independent element codes corresponding to the merged elements according to the preset coding rules, including: After the user terminal batch-selects multiple elements to be merged in the quality element library that are in a published state and do not have invalid fields, the system performs a quantity check on the elements to be merged. If the check passes, the element merge button is activated. If the check fails, the element merge button is grayed out and an error message is popped up; After the user clicks the element merge button, the editable merge pop-up window is triggered, and the system automatically extracts the merge element attributes of the elements to be merged, namely, element content, associated quality process, associated quality requirement document and version number, and fills them into the editable merge pop-up window. At the same time, the user is supported to manually modify the attribute conflicts between the elements to be merged; The system determines the independent element code corresponding to the merged element according to the preset coding rule, and unifies the check digits of the independent element code through a hash algorithm; After the merge operation is completed, the status of the element to be merged is marked as invalid, and the status of the merged element is marked as pending release; After the user terminal confirms to publish the merged element, the state of the merged element is changed to a published state.

3. A method for dynamically merging and splitting quality document elements of a manufacturing enterprise according to claim 2, characterized in that: The attribute conflict includes but is not limited to the inconsistency of the element contents between the elements to be merged, the duplication of the associated quality processes, or the different version numbers; After the user terminal modifies the attribute conflict, the system automatically performs a secondary attribute check on the elements to be merged until the attribute conflict does not exist between the elements to be merged.

4. A method for dynamically merging and splitting quality document elements of a manufacturing enterprise according to claim 1 or 2, characterized in that: When the user terminal selects a single element, an expandable split pop-up window is triggered. The system supports the split-generated element to inherit the split element attributes of the element to be split and allows editing of the key field content of the split-generated element, and sets the corresponding independent element code for the split-generated element, specifically including: After the user terminal selects a single published element to be split, and clicks the element split button, the system automatically pops up the expandable split pop-up window containing one split item, and supports the user terminal to click the item add button to add the split item, and the upper limit of the number of split items is 10; The system supports the split generation element to automatically inherit the split element attributes of the element to be split, namely the associated quality process, the associated quality requirement document and the version number. At the same time, the system clears the key field content of the split generation element, namely the item number and element content, and allows the user to customize the key field content; The system sets the corresponding independent element code for the split-generated element, and embeds the first 6 digits of the element number of the element to be split into the independent element code as a split parent identifier; After the split operation is completed, the status of the element to be split is marked as invalid, and the status of the element generated by the split is marked as to be published; After the user terminal confirms the release of the split generation element, the state of the split generation element is changed to a released state.

5. A method for dynamically merging and splitting quality document elements of a manufacturing enterprise according to claim 4, characterized in that: The split parent identifier occupies the first 6 digits of the independent element code corresponding to the split generation element, and is the same as the first 6 digits of the independent element code corresponding to the element to be split, wherein a coding mapping relationship is formed between the element to be split and the split generation element.

6. A method for dynamically merging and splitting quality document elements of a manufacturing enterprise according to claim 1, characterized in that: The multi-tab architecture of the details page includes an element information tab, a merge and split history tab, a historical version tab, and an alternative relationship tab, and adopts a responsive layout design; The merge and split history tab displays the element lineage relationship chain in the form of a directed acyclic graph; The History Version tab arranges the element version records in the Version History table in reverse chronological order and supports version comparison and version rollback functions; The substitution relationship tab is used to display the element substitution relationship in the substitution relationship table, and supports keyword search and export functions.

7. A method for dynamically merging and splitting quality document elements of a manufacturing enterprise according to claim 6, characterized in that: In the merge and split history tab, based on the form of the directed acyclic graph, each element is treated as a module, the element status is distinguished by the color of the submodules in each module, and the direction of the element evolution is indicated by the direction of the arrow of the module connection edge, and after the user terminal clicks any of the modules, the merge and split history tab jumps to the element information tab of the element corresponding to the module; The version comparison function highlights the changed parts of feature attributes through a differentiation algorithm, and before the version rollback function is run, the user terminal's authority needs to be successfully verified.

8. A system for dynamically merging and splitting quality document elements of a manufacturing enterprise, applied to a method for dynamically merging and splitting quality document elements of a manufacturing enterprise as claimed in any one of claims 1 to 7, characterized in that: The system comprises: Merge module: When the user selects multiple elements, the editable merge pop-up window is triggered. The system automatically extracts the merged element attributes of the elements to be merged and determines the independent element code corresponding to the merged element according to the preset coding rules; A splitting module is used to trigger an expandable splitting pop-up window when the user terminal selects a single element. The system supports the split-generated element to inherit the split element attributes of the element to be split and allows editing of the key field content of the split-generated element, and sets the corresponding independent element code for the split-generated element; A result module is used for the system to construct a triple model based on the independent element coding, formulate an element lineage relationship chain, maintain a version history table and a substitution relationship table, solidify the operation log, and form a dynamic merge and split result; The display module is used by the system to display the dynamic merging and splitting results to the user terminal through the multi-tab architecture of the details page.

Images