Processing procedure collaborative management and control system, method, device and medium

Abstract

The embodiment of the application provides a kind of processing procedure coordination control system, method, equipment and medium, belong to intelligent manufacturing and numerical control processing automation field. Including: permission management unit, program management unit, version control unit, approval management unit, configured to trigger the approval process for processing procedure, and according to the approval result, state switching instruction is output to version control unit, so that it will mark the current version of processing procedure as effective available state or isolated revision state;Data storage tracing unit is configured to store key data of machine tool, and according to the association between the stored version identifier and the processing result data, a mapping model is established. Realize the whole cycle management of processing procedure from creation, approval, call, modification to version rollback.

Description

Technical Field

[0001] This invention relates to the field of intelligent manufacturing and CNC machining automation technology, specifically to a collaborative control system, method, equipment, and medium for machining processes. Background Technology

[0002] In existing CNC machining intelligent manufacturing production scenarios, the machining program is the core basis for machine tool processing, directly determining the product machining accuracy, production efficiency, and production safety. Currently, the machining program management and machine tool data control of small and medium-sized manufacturing enterprises and large intelligent factories generally have many technical deficiencies, making it difficult to adapt to the needs of large-scale, collaborative, and standardized production.

[0003] Existing machining programs mostly employ traditional management methods such as local storage, LAN sharing, and USB drive copying, lacking a unified program storage and control platform. The permissions of programmers, process engineers, operators, and managers are not clearly defined, leading to situations where ordinary operators arbitrarily modify, replace, or delete machining programs. This can easily result in distorted machining parameters, batch product scrap, and even safety accidents such as machine tool collisions and equipment damage. Furthermore, program modifications lack permission verification and operation records, making it impossible to trace responsibility and the source of the operation after quality issues arise. Moreover, traditional management methods lack a robust program version control mechanism. Machining programs undergo multiple modifications based on product iterations, process optimizations, and equipment debugging. The existing model cannot automatically retain historical versions or record version modifications and the personnel responsible for them. Frequent issues of mixing old and new versions, overwriting, and data loss not only increase process debugging costs but also fail to meet the consistency requirements of precision machining and mass production. Summary of the Invention

[0004] The purpose of this invention is to provide a collaborative management system, method, device, and medium for processing programs, enabling controlled management of the entire lifecycle of processing programs, from creation, approval, invocation, modification to version rollback.

[0005] To achieve the above objectives, embodiments of the present invention provide a collaborative control system for processing procedures, comprising: The access control unit is configured to assign operation permissions to different job roles based on a preset role-based access control model and to record user operation behavior. The program management unit is configured to establish a centralized program repository, perform storage, classification and retrieval operations on processing programs, and support multi-terminal collaborative access and invocation; Version control unit, configured to generate version nodes in response to modifications made to the processing program, and retain historical version files and version change information; The approval management unit is configured to trigger the approval process for the processing procedure and output a state switching instruction to the version control unit according to the approval result, so that the version control unit marks the current version of the processing procedure as effective and available or isolated revision according to the state switching instruction. Specifically, in the effective and available state, modification operations on this version are prohibited, while in the isolated revision state, it is allowed to create a new derived version based on this version; and when creating a new derived version, the version control unit will perform a program instruction difference analysis between the new derived version and the currently effective version. If the difference involves preset key process parameters or safety parameters, the new derived version will be prevented from triggering the approval process and a conflict prompt will be output. The data storage traceability unit is configured to store program files, version records, operation logs, approval records, and machine tool operation data, and to establish a mapping model based on the association between the stored version identifier and the processing result data, so that when the version control unit performs a version rollback or version switching operation, the data storage traceability unit can query the historical data of the version in the mapping model with the target version identifier.

[0006] Optionally, the preset role-based access control (RBAC) model is used. Job roles include multiple roles such as super administrator, process programmer, process reviewer, machine tool operator, production administrator, and equipment maintenance worker; The operation permissions include multiple permissions such as program upload, program download, program modification, program deletion, program viewing, program invocation, approval operation, data viewing, and data export.

[0007] For example, the access control unit is based on the RBAC (Role-Based Access Control) model, with multiple preset roles, including super administrator, process programmer, process reviewer, machine operator, production administrator, and equipment maintenance personnel. It also supports custom addition of roles and permission configurations. Differentiated operation permissions are assigned to different roles, covering all aspects of operations such as uploading, downloading, modifying, deleting, viewing, calling, approving, viewing data, and exporting data. Simultaneously, operator accounts are linked to equipment terminals, and operation logs for all accounts are recorded, ensuring traceability and accountability for every step of program operation and data viewing, thus preventing the risk of unauthorized operations.

[0008] Optionally, the version control unit will perform a program instruction difference analysis between the derived new version and the currently effective version, including: The derived new version and the effective version are compared line by line using G-code instruction sequences to extract the set of differences in instructions; The set of difference instructions is matched with a preset parameter library. When a match is found, the difference analysis result is determined to involve key process parameters or safety parameters. When the difference analysis results do not involve key process parameters or safety parameters, the derived new version is allowed to trigger the approval process normally; if the approval is approved, the derived new version is marked as a new effective and usable state, and the original effective and usable version is archived as a historical retention version; The preset parameter library includes at least one of the following: spindle speed threshold, feed rate threshold, depth of cut threshold, and tool compensation value.

[0009] Optionally, the approval process includes at least one of the following: a program addition and launch approval process, a program modification and change approval process, and a program cancellation and deactivation approval process.

[0010] Optionally, the version control unit further includes: The version locking subunit is configured to lock the version that is in the effective and available state in response to administrator operations or approval results, wherein the version is prohibited from being modified in the locked state; The version control unit stores the derivation relationship between each version node, forming a version tree structure, and provides a version rollback interface and a version comparison interface. The version rollback interface is used to restore the current program to any historical version node, and the version comparison interface is used to visualize the program differences between different version nodes.

[0011] Optionally, the data storage traceability unit is further configured as follows: Establish a relationship graph between program version nodes, operators, machine tools and processed products, and support chain-based traceability queries based on the relationship graph.

[0012] A collaborative control method for machining processes, applied to the aforementioned collaborative control system for machining processes, includes: System initialization includes configuring job roles and corresponding operating permissions, and establishing communication connections for each CNC machine tool; In response to the upload operation of the processing program, the processing program is stored in the centralized program repository, an initial version node is generated, and the approval process is triggered. Once approved, the current version of the machining program will be marked as effective and available, granting the machine tool access to call it; if the approval fails, it will be marked as isolated for revision, and feedback on modifications will be provided. In response to the call operation of a machining program that is in an effective and available state, the machining program is sent to the target machine tool, and machine tool operating parameters and production data are collected in real time during the machining process. The version identifier of the currently called program is bound synchronously during the collection. In response to a modification operation on a processing program in an isolated revision state, a new derived version node is generated, and a program instruction difference analysis is performed between the derived new version and the currently effective version. If the difference involves preset key process parameters or safety parameters, the new derived version is prevented from triggering the approval process and a conflict prompt is output; if the difference does not involve any parameters, the approval process is allowed. The program files, version node records, operation logs, approval records, and machine tool operation data are stored in the database. A mapping model is established based on the relationship between version identifiers and machining result data. When the version control unit performs version rollback or version switching operations, the data storage traceability unit queries the historical data of the target version in the mapping model using the target version identifier.

[0013] Optionally, the program instruction difference analysis includes: The new version is compared line by line with the currently effective version using G-code instructions to extract the set of differences in instructions; The set of difference instructions is matched with a preset parameter library. When a match is found, it is determined that the difference involves key process parameters or safety parameters. When the difference analysis results do not involve key process parameters or safety parameters, the derived new version is allowed to trigger the approval process normally; if the approval is approved, the derived new version is marked as a new effective and usable state, and the original effective and usable version is archived as a historical retention version; The preset parameter library includes at least one of the following: spindle speed threshold, feed rate threshold, depth of cut threshold, and tool compensation value.

[0014] Thirdly, the present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the above-described collaborative control method for processing programs.

[0015] Fourthly, the present invention also provides a storage medium storing a computer program thereon, wherein the computer program, when executed by a processor, implements the steps of the above-described collaborative control method for processing programs.

[0016] The above technical solution combines version control and approval management to mark program versions as effective and available or in an isolated revision state, thus binding version usage rights with approval results and preventing unapproved programs from being called. When deriving a new version, the program instructions are analyzed for differences, and changes involving key parameters are automatically intercepted and prompted before approval. By establishing a mapping model that associates program version identifiers with processing result data, a decision-making basis for version changes is provided.

[0017] Other features and advantages of the embodiments of the present invention will be described in detail in the following detailed description section. Attached Figure Description

[0018] The accompanying drawings are provided to further illustrate embodiments of the present invention and form part of the specification. They are used together with the following detailed description to explain the embodiments of the present invention, but do not constitute a limitation thereof. In the drawings: Figure 1 This is a schematic diagram of the structure of a collaborative control system for processing procedures provided in an embodiment of the present invention; Figure 2 This is a flowchart of a collaborative control method for a processing procedure provided in an embodiment of the present invention; Figure 3 This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0019] Various embodiments of this disclosure will be described more fully in the following detailed description. This disclosure may have various embodiments, and adjustments and changes may be made therein. However, it should be understood that there is no intention to limit the various embodiments of this disclosure to the specific embodiments disclosed herein, but rather this disclosure should be understood to cover all adjustments, equivalents, and / or alternatives falling within the spirit and scope of the various embodiments of this disclosure.

[0020] In the following, the terms “comprising” or “may include”, which may be used in various embodiments of this disclosure, indicate the presence of the disclosed functions or operations and do not limit the addition of one or more functions or operations. Furthermore, as used in various embodiments of this disclosure, the terms “comprising,” “having,” and their cognates are intended only to indicate a specific feature, number, step, operation, or combination of the foregoing and should not be construed as primarily excluding the presence of one or more other features, numbers, steps, operations, or combinations of the foregoing, or the possibility of adding one or more features, numbers, steps, operations, or combinations of the foregoing.

[0021] In various embodiments of this disclosure, the expression "or" or "at least one of A and / or B" includes any combination or all combinations of the words listed simultaneously. For example, the expression "A or B" or "at least one of A and / or B" may include A, may include B, or may include both A and B.

[0022] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0023] See Figure 1The diagram shown is a structural schematic of a collaborative control system for a processing procedure provided in an embodiment of the present invention, comprising: The access control unit is configured to assign operation permissions to different job roles based on a preset role-based access control model and to record user operation behavior. The program management unit is configured to establish a centralized program repository, perform storage, classification and retrieval operations on processing programs, and support multi-terminal collaborative access and invocation; Version control unit, configured to generate version nodes in response to modifications made to the processing program, and retain historical version files and version change information; The approval management unit is configured to trigger the approval process for the processing procedure and output a state switching instruction to the version control unit according to the approval result, so that the version control unit marks the current version of the processing procedure as effective and available or isolated revision according to the state switching instruction. Specifically, in the effective and available state, modification operations on this version are prohibited, while in the isolated revision state, it is allowed to create a new derived version based on this version; and when creating a new derived version, the version control unit will perform a program instruction difference analysis between the new derived version and the currently effective version. If the difference involves preset key process parameters or safety parameters, the new derived version will be prevented from triggering the approval process and a conflict prompt will be output. The data storage traceability unit is configured to store program files, version records, operation logs, approval records, and machine tool operation data, and to establish a mapping model based on the association between the stored version identifier and the processing result data, so that when the version control unit performs a version rollback or version switching operation, the data storage traceability unit can query the historical data of the version in the mapping model with the target version identifier.

[0024] The preset role permission model is the RBAC model; the job roles include multiple roles such as super administrator, process programmer, process reviewer, machine tool operator, production administrator and equipment maintenance personnel; the operation permissions include multiple permissions such as program upload, program download, program modification, program deletion, program viewing, program calling, approval operation, data viewing and data export.

[0025] Specifically, the version control unit will perform a program instruction difference analysis between the derived new version and the currently effective version, including the following steps: S1: Perform a line-by-line comparison of the G-code instruction sequences between the derived new version and the effective version to extract the set of differing instructions.

[0026] S2: Match the set of difference instructions with the preset parameter library. When a match is found, determine that the difference analysis result involves key process parameters or safety parameters.

[0027] S3: When the difference analysis results do not involve key process parameters or safety parameters, the derived new version is allowed to trigger the approval process normally; if the approval is approved, the derived new version is marked as a new effective and usable state, and the original effective and usable version is archived as a historical retention version.

[0028] The preset parameter library includes at least one of the following: spindle speed threshold, feed rate threshold, depth of cut threshold, and tool compensation value.

[0029] Preferably, the approval process includes at least one of the following: a program addition and launch approval process, a program modification and change approval process, and a program cancellation and deactivation approval process.

[0030] Furthermore, the version control unit also includes: The version locking subunit is configured to lock versions that are in the effective and available state in response to administrator operations or approval results, wherein the versions are prohibited from being modified in the locked state.

[0031] The version control unit stores the derivation relationship between each version node, forming a version tree structure, and provides a version rollback interface and a version comparison interface. The version rollback interface is used to restore the current program to any historical version node, and the version comparison interface is used to visualize the program differences between different version nodes.

[0032] The data storage traceability unit is also configured to: Establish a relationship graph between program version nodes, operators, machine tools and processed products, and support chain-based traceability queries based on the relationship graph.

[0033] Through the above technical solutions, the system achieves hierarchical control and behavior traceability of operations through permission management; by combining version control and approval management, program versions are marked as effective and usable or in an isolated revision state, binding version usage rights with approval results to prevent unapproved programs from being called; when deriving new versions, the system performs difference analysis on program instructions, automatically intercepts and prompts changes involving key parameters before approval; and by establishing a mapping model by associating program version identifiers with processing result data, the system provides a basis for decision-making regarding version changes.

[0034] See Figure 2 The diagram shows a flowchart of a collaborative control method for a processing procedure in a specific embodiment, including the following execution steps: Step 100: System initialization.

[0035] Specifically, this includes configuring job roles and corresponding operating permissions, and establishing communication connections between various CNC machine tools.

[0036] In one specific implementation, the system is deployed on a local server in the workshop, establishing a dedicated local area network to connect all CNC machine tools, office terminals, and workshop touch terminals. During system initialization, the super administrator logs into the backend and sets up six core roles based on workshop positions: super administrator, process programmer, process reviewer, front-line operator, production supervisor, and equipment maintenance worker. Exclusive permissions are configured for each role: process programmers only have permissions to upload, edit, view, and iterate programs, but no approval or deletion permissions; process reviewers only have permissions to review, view, and annotate programs; front-line operators only have permissions to retrieve, use, and view approved programs, but no modification or deletion permissions; production supervisors have permissions to view the entire process, perform data statistics, and approve / review; and equipment maintenance workers only have permissions to view machine tool data, perform fault data statistics, and view equipment maintenance records. Simultaneously, all staff account information is entered and bound to terminal devices, completing the permission system setup.

[0037] Step 101: In response to the upload operation of the processing program, the processing program is stored in the centralized program repository, an initial version node is generated, and the approval process is triggered.

[0038] Specifically, process programmers write corresponding CNC machining programs based on the part processing requirements. After debugging, the programs are uploaded to the system's cloud-based program resource library, and information such as product model, machine tool, processing material, process parameters, and programmer information is entered simultaneously. The system automatically categorizes and archives the programs. When subsequent processing parameters need to be optimized or processing technology adjusted, programmers retrieve the corresponding programs for modification. The system automatically generates progressive version numbers such as V1.0, V1.1, and V2.0, and records the modification time, content, and the person who made the modification. For mass-production finalized programs, administrators can enable version locking to prevent any modifications. For programs in the R&D and debugging phase, continuous iterative updates are allowed. If the processing effect is unsatisfactory after modification, a one-click rollback to the previous stable version is possible. All version records are retained throughout the process, preventing program loss and version inconsistencies.

[0039] After the program is uploaded or updated, the system automatically triggers an online approval process. The approval nodes are, in sequence, initial process review and production verification. Process auditors log into the system to view the program's process parameters and processing logic, and review them in conjunction with product drawings and process standards. If unreasonable parameters or process loopholes are found, the program is rejected with suggested modifications, and the programmer re-optimizes it. If the review is successful, it is transferred to the production supervisor for a second review. After the review is completed, the program is officially unlocked for machine access, and workshop operators can access the program for processing via terminals. All approval records, annotations, and workflow nodes are automatically saved, forming a standardized approval ledger. The system also supports customized approval processes. For high-precision parts, precision molds, and other high-end products, multiple approval nodes can be added to improve control standards.

[0040] Step 102: After approval, mark the current version of the machining program as effective and available, and grant the machine tool access to call it; if the approval fails, mark it as isolated for revision and provide feedback on the modification.

[0041] Step 103: In response to the call operation of the machining program that is in an effective and available state, the machining program is sent to the target machine tool, and the machine tool operating parameters and production data are collected in real time during the machining process. The version identifier of the currently called program is bound synchronously during the collection.

[0042] Step 104: In response to a modification operation on a processing program in an isolated revision state, a derived new version node is generated, and a program instruction difference analysis is performed between the derived new version and the currently effective version. If the difference involves preset key process parameters or safety parameters, the derived new version is prevented from triggering the approval process and a conflict prompt is output; if the difference does not involve any parameters, the approval process is allowed.

[0043] Specifically, when performing the program instruction difference analysis in step 104, the following steps can be executed: S1040: Perform a line-by-line comparison of the G-code instruction sequences between the new version and the currently effective version to extract the set of differing instructions.

[0044] S1041: Match the set of difference instructions with the preset parameter library. When a match is found, determine that the difference involves key process parameters or safety parameters.

[0045] S1042: When the difference analysis results do not involve key process parameters or safety parameters, the derived new version is allowed to trigger the approval process normally; if the approval is approved, the derived new version is marked as a new effective and usable state, and the original effective and usable version is archived as a historical retention version.

[0046] The preset parameter library includes at least one of the following: spindle speed threshold, feed rate threshold, depth of cut threshold, and tool compensation value.

[0047] Step 105: Analyze and process the collected machine tool operating parameters and production data, generate data analysis reports, and output a warning signal when the data exceeds the preset threshold.

[0048] Specifically, when executing step 105, the following steps can be performed: S1050: The data acquisition and analysis unit acquires raw operating data from each CNC machine tool in real time via industrial Ethernet and machine tool-specific communication protocols. Since the raw data may contain outliers caused by communication interruptions, sensor drift, or momentary machine tool start-ups and shutdowns, the raw data undergoes preprocessing: for missing data points due to momentary communication interruptions, linear interpolation or the average of preceding and following time points is used to fill in the gaps; if consecutive missing data exceeds a preset duration, the data for that period is marked as invalid and a communication anomaly record is generated. For signals susceptible to environmental interference, such as vibration and load signals, moving average filtering or median filtering algorithms are used for smoothing to eliminate high-frequency random noise. Raw data of different dimensions are mapped to a unified numerical range according to their respective measurement ranges.

[0049] S1051: For continuously varying parameters such as spindle speed, feed rate, cutting load, and temperature, extract statistical characteristics such as mean, maximum, minimum, standard deviation, and root mean square value within a unit time window. For vibration data, convert the time-domain signal to a frequency-domain signal using Fast Fourier Transform, and extract frequency-domain features such as frequency peak value and dominant frequency energy percentage to identify precursors of periodic faults such as bearing wear and tool imbalance. For cumulative data such as machining output, runtime, and number of faults, perform cumulative statistics at time granularities such as shift, day, and week to form trend data.

[0050] S1052: The system has a built-in preset key parameter library, which includes at least one safety parameter such as spindle speed threshold, feed rate threshold, depth of cut threshold, and tool compensation value. The extracted feature data enters the threshold matching process.

[0051] Specifically, the real-time collected parameters such as spindle speed, feed rate, and cutting load are compared with corresponding preset thresholds. For example, if the spindle load continuously exceeds the preset load threshold for a set duration, it is determined to be an overload abnormality.

[0052] For cases where a single parameter does not exceed the threshold but multiple parameter combinations are abnormal, a weighted comprehensive evaluation method is used to assign weight coefficients to each parameter and calculate the weighted deviation. When the comprehensive deviation exceeds the preset threshold, an early warning is triggered.

[0053] It should be understood that the preset threshold is an empirical value and can be set according to the specific application scenario; no restrictions are imposed here.

[0054] S1053: Based on the severity of exceeding the threshold, the warning is divided into multiple levels: a slight deviation triggers a level 1 warning, which displays a reminder message on the operation panel; a moderate deviation triggers a level 2 warning, which automatically reduces the feed rate or limits the upper limit of the spindle speed; a severe deviation triggers a level 3 emergency warning, which immediately outputs an emergency stop signal and locks the machine tool.

[0055] Step 106: Store program files, version node records, operation logs, approval records, and machine tool operation data in the database.

[0056] Specifically, the process of constructing the mapping model includes the following steps: S1060: When a program version has accumulated at least N valid processing records, the average pass rate, average dimensional deviation, and average surface roughness of that version shall be used as the benchmark quality data for that version.

[0057] S1061: Using the version identifier as the unique primary key, associate the instruction characteristics of each version with its baseline quality data to establish a mapping table between program instruction characteristics and processing quality.

[0058] The mapping relationship is stored using a lookup table to capture the quantitative relationship between changes in instruction parameters and quality indicators.

[0059] For example, the mapping relationship table is shown in Table 1: Table 1: Mapping Relationship Table

[0060] S1062: When the version control unit performs a version rollback or version switch operation, the system uses the version identifier of the target version as an index to query the historical quality evaluation indicators of the version in the mapping model, compares the above indicators with the corresponding indicators of the currently effective version, and generates an impact prediction report.

[0061] The report includes historical quality performance data of the target version and comparisons with the current version, providing operators with a quantitative basis for version change decisions.

[0062] In this embodiment, role permission configuration and machine tool communication connection are completed through system initialization, enabling personnel in multiple positions to perform corresponding operations within their respective permission scopes. Approval is triggered when a program is uploaded to the database, preventing newly added programs from being called and deployed before approval, thus avoiding unverified programs entering the production process. After approval, programs are marked as effective and usable; if approval fails, they are marked as isolated for revision, directly linking program usage permissions to the approval result and blocking the deployment of unapproved programs. Version difference analysis is performed during modifications in the isolated revision state, intercepting and alerting personnel regarding modifications to key parameters before triggering approval. Data storage and the establishment of a version-quality mapping model provide historical data for version change decisions.

[0063] Figure 3 This is a schematic diagram of a terminal 300 provided in an embodiment of the present invention. The terminal 300 can be used to execute the method for updating heat dissipation strategy parameters provided in the embodiment of the present invention.

[0064] The terminal 300 may include a processor 310, a memory 320, and a communication module 330. These components communicate via one or more buses. Those skilled in the art will understand that the server structure shown in the figure does not constitute a limitation of the present invention. It may be a bus topology or a star topology, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0065] The memory 320 can be used to store the execution instructions of the processor 310. The memory 320 can be implemented by any type of volatile or non-volatile memory terminal or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. When the execution instructions in the memory 320 are executed by the processor 310, the terminal 300 is able to perform some or all of the steps in the above method embodiments.

[0066] The processor 310 serves as the control center of the storage terminal, connecting various parts of the electronic terminal via various interfaces and lines. It executes software programs and / or modules stored in the memory 320, and calls data stored in the memory to perform various functions of the electronic terminal and / or process data. The processor can be composed of integrated circuits (ICs), such as a single packaged IC or multiple packaged ICs with the same or different functions connected together. For example, the processor 310 may consist only of a central processing unit (CPU). In this embodiment of the invention, the CPU may have a single processing core or include multiple processing cores.

[0067] The communication module 330 is used to establish a communication channel, enabling the storage terminal to communicate with other terminals. It receives user data sent by other terminals or sends user data to other terminals.

[0068] The present invention also provides a computer storage medium, wherein the computer storage medium may store a program, which, when executed, may include some or all of the steps provided in the embodiments of the present invention. The storage medium may be a magnetic disk, an optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0069] Those skilled in the art will clearly understand that the techniques in the embodiments of the present invention can be implemented using software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solutions in the embodiments of the present invention, or the parts that contribute to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium such as a USB flash drive, mobile hard drive, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk, or other media capable of storing program code. It includes several instructions to cause a computer terminal (which may be a personal computer, server, or a second terminal, network terminal, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention.

[0070] The same or similar parts between the various embodiments in this specification can be referred to mutually. In particular, the terminal embodiments are basically similar to the method embodiments, so the description is relatively simple, and the relevant parts can be referred to the description in the method embodiments.

[0071] In the embodiments provided by this invention, it should be understood that the disclosed systems and methods can be implemented in other ways. For example, the system embodiments described above are merely illustrative. For instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between systems or modules may be electrical, mechanical, or other forms.

[0072] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0073] In addition, the functional modules in the various embodiments of the present invention can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module.

[0074] Although the present invention has been described in detail with reference to the accompanying drawings and preferred embodiments, the present invention is not limited thereto. Various equivalent modifications or substitutions can be made to the embodiments of the present invention by those skilled in the art without departing from the spirit and essence of the invention, and such modifications or substitutions should all be within the scope of the present invention. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should also be covered within the protection scope of the present invention.

Claims

1. A collaborative control system for a processing procedure, characterized in that, include: The access control unit is configured to assign operation permissions to different job roles based on a preset role-based access control model and to record user operation behavior. The program management unit is configured to establish a centralized program repository, perform storage, classification and retrieval operations on processing programs, and support multi-terminal collaborative access and invocation; Version control unit, configured to generate version nodes in response to modifications made to the processing program, and retain historical version files and version change information; The approval management unit is configured to trigger the approval process for the processing procedure and output a state switching instruction to the version control unit according to the approval result, so that the version control unit marks the current version of the processing procedure as effective and available or isolated revision according to the state switching instruction. Specifically, in the effective and available state, modification operations on this version are prohibited, while in the isolated revision state, it is allowed to create a new derived version based on this version; and when creating a new derived version, the version control unit will perform a program instruction difference analysis between the new derived version and the currently effective version. If the difference involves preset key process parameters or safety parameters, the new derived version will be prevented from triggering the approval process and a conflict prompt will be output. The data storage traceability unit is configured to store program files, version records, operation logs, approval records, and machine tool operation data, and to establish a mapping model based on the association between the stored version identifier and the processing result data, so that when the version control unit performs a version rollback or version switching operation, the data storage traceability unit can query the historical data of the version in the mapping model with the target version identifier.

2. The collaborative control system for processing procedures according to claim 1, characterized in that, The preset role-based access control model is the RBAC model. Job roles include multiple roles such as super administrator, process programmer, process reviewer, machine tool operator, production administrator, and equipment maintenance worker; The operation permissions include multiple permissions such as program upload, program download, program modification, program deletion, program viewing, program invocation, approval operation, data viewing, and data export.

3. The collaborative control system for processing procedures according to claim 1, characterized in that, The version control unit will perform a program instruction difference analysis between the derived new version and the currently effective version, including: The derived new version and the effective version are compared line by line using G-code instruction sequences to extract the set of differences in instructions; The set of difference instructions is matched with a preset parameter library. When a match is found, the difference analysis result is determined to involve key process parameters or safety parameters. When the difference analysis results do not involve key process parameters or safety parameters, the derived new version is allowed to trigger the approval process normally; if the approval is approved, the derived new version is marked as a new effective and usable state, and the original effective and usable version is archived as a historical retention version; The preset parameter library includes at least one of the following: spindle speed threshold, feed rate threshold, depth of cut threshold, and tool compensation value.

4. The collaborative control system for processing procedures according to claim 1, characterized in that, The approval process includes at least one of the following: approval process for adding and launching a new program, approval process for modifying or changing a program, and approval process for canceling or deactivating a program.

5. The collaborative control system for processing procedures according to claim 1, characterized in that, The version control unit also includes: The version locking subunit is configured to lock the version that is in the effective and available state in response to administrator operations or approval results, wherein the version is prohibited from being modified in the locked state; The version control unit stores the derivation relationship between each version node, forming a version tree structure, and provides a version rollback interface and a version comparison interface. The version rollback interface is used to restore the current program to any historical version node, and the version comparison interface is used to visualize the program differences between different version nodes.

6. The collaborative control system for processing procedures according to claim 1, characterized in that, The data storage traceability unit is also configured to: Establish a relationship graph between program version nodes, operators, machine tools and processed products, and support chain-based traceability queries based on the relationship graph.

7. A method for collaborative control of a processing procedure, characterized in that, The processing procedure collaborative control system applied to any one of claims 1 to 6 includes: System initialization includes configuring job roles and corresponding operating permissions, and establishing communication connections for each CNC machine tool; In response to the upload operation of the processing program, the processing program is stored in the centralized program repository, an initial version node is generated, and the approval process is triggered. Once approved, the current version of the machining program will be marked as effective and available, granting the machine tool access to call it; if the approval fails, it will be marked as isolated for revision, and feedback on modifications will be provided. In response to the call operation of a machining program that is in an effective and available state, the machining program is sent to the target machine tool, and machine tool operating parameters and production data are collected in real time during the machining process. The version identifier of the currently called program is bound synchronously during the collection. In response to a modification operation on a processing program in an isolated revision state, a new derived version node is generated, and a program instruction difference analysis is performed between the derived new version and the currently effective version. If the difference involves preset key process parameters or safety parameters, the new derived version is prevented from triggering the approval process and a conflict prompt is output; if the difference does not involve any parameters, the approval process is allowed. The program files, version node records, operation logs, approval records, and machine tool operation data are stored in the database. A mapping model is established based on the relationship between version identifiers and machining result data. When the version control unit performs version rollback or version switching operations, the data storage traceability unit queries the historical data of the target version in the mapping model using the target version identifier.

8. The collaborative control method for processing procedures according to claim 7, characterized in that, The program instruction difference analysis includes: The new version is compared line by line with the currently effective version using G-code instructions to extract the set of differences in instructions; The set of difference instructions is matched with a preset parameter library. When a match is found, it is determined that the difference involves key process parameters or safety parameters. When the difference analysis results do not involve key process parameters or safety parameters, the derived new version is allowed to trigger the approval process normally; if the approval is approved, the derived new version is marked as a new effective and usable state, and the original effective and usable version is archived as a historical retention version; The preset parameter library includes at least one of the following: spindle speed threshold, feed rate threshold, depth of cut threshold, and tool compensation value.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps of the collaborative control method for the processing program as described in claim 7 or 8.

10. A storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the collaborative control method for the processing program as described in claim 7 or 8.

Images