Management method for model parameters and bill of materials based on Teamcenter

Abstract

The invention discloses a Teamcenter-based model parameter and bill of materials (BOM) management method, relates to the field of product life cycle management system application, and aims to realize efficient management of model parameters and a bill of materials (BOM) through the steps of integrated data management, automatic process, authority control, version control, intelligent assistance and the like on the basis of a Teamcenter platform. The uniform storage and integration capability of Teamcenter is utilized to ensure the consistency and integrity of model parameters and BOM data; automatic processes such as automatic consistency checking and automatic PDF generation are designed, and manual intervention is reduced; the data security is guaranteed through an authority management function; a strict version control mechanism is implemented to ensure data traceability; and intelligent assistance is provided for the user by using functions of searching, querying and the like, so that the working efficiency is improved. According to the method, the problems of data updating lagging, high error rate and untimely information sharing in a traditional management mode are effectively solved, and powerful support is provided for intelligent manufacturing and digital transformation of enterprises.

Description

Technical Field

[0001] The present application relates to the application field of product lifecycle management system, and in particular to a management method of model parameters and bill of materials based on Teamcenter. Background Art

[0002] In modern manufacturing, as product complexity continues to increase, the product design and development process needs to process massive amounts of model parameters, design documents, and bill of materials data. The efficient management and collaborative application of these data are of great significance to improving corporate competitiveness and shortening product development cycles.

[0003] In related technologies, enterprises generally use product lifecycle management (PLM) systems to manage product data. These systems store product design data by establishing a database, organize design documents by file management, maintain bill of materials (BOM) information by manual entry, and use basic workflow engines to handle document approval processes. At the same time, the system provides a simple user permission division function to protect data security.

[0004] However, due to the lack of data processing mechanism, designers need to spend a lot of time on repetitive data management and approval. Summary of the invention

[0005] This application provides a Teamcenter-based model parameter and bill of materials management method for improving the efficiency of data management and approval.

[0006] In the first aspect, the present application provides a method for managing model parameters and bills of materials based on Teamcenter, which is applied to a management system, and the method includes: receiving a project generation instruction from a management terminal, and generating a workflow instance based on a preset template of the Teamcenter platform; distributing target tasks to target users according to the implementation process of the workflow instance; the target tasks include data review, data approval, and data release; receiving product source files uploaded by target users, determining model parameters and BOM data based on the product source files, and storing the product source files, model parameters, and BOM data on the Teamcenter platform; the product source files include design drawings, test data, and associated documents; when a data modification request for model parameters or BOM data is detected, determining the requesting user and modification file corresponding to the data modification request, and determining whether the requesting user has modification permission to modify the file based on the user permission table; if the requesting user has modification permission to modify the file, backing up the modification file and generating a modified data version of the modification file; collecting the modification history record of the modification file including the modification content, modification time, and operator information, and storing the modification history record on the Teamcenter platform.

[0007] In the above embodiment, the management system realizes the automation of the entire process from project creation, task distribution to data management by establishing a complete workflow management mechanism, and can perform permission verification, version control and history tracking, effectively avoiding the risk of unauthorized modification of data. At the same time, by completely preserving the modification history records, it ensures the traceability of data changes and improves the standardization and security of data management.

[0008] In combination with some embodiments of the first aspect, in some embodiments, before receiving the project generation instruction from the management terminal and generating a workflow instance based on a preset template of the Teamcenter platform, the method also includes: reading the new user information of the new user, determining the new access rights of the new user according to the permission allocation instruction of the management terminal; and updating the new user information and the new access rights to the user permission table of the Teamcenter platform.

[0009] In the above embodiment, the management system realizes precise control over the access rights of new users through a standardized user authority management process, and establishes a complete user management system by uniformly updating user information and access rights to the authority table, thereby reducing the complexity of authority management and improving system security.

[0010] In combination with some embodiments of the first aspect, in some embodiments, after the steps of receiving the product source file uploaded by the target user, determining the model parameters and BOM data based on the product source file, and storing the product source file, model parameters and BOM data on the Teamcenter platform, the method also includes: receiving a data query request, determining the query user and query file corresponding to the data query request, and determining whether the query user has the query permission for the query file according to the user permission table; if the query user has the query permission for the query file, determining the data query area and query filtering conditions on the Teamcenter platform according to the data query request; determining the query result form according to the data query area and query filtering conditions; determining whether there is a data query area or query filtering conditions in the historical query record; if so, generating a query history prompt according to the historical query record, and displaying the query result form and the query history prompt.

[0011] In the above embodiment, the management system introduces a data query mechanism, which realizes accurate data retrieval through functions such as permission verification, area screening and historical record prompts. It can also provide intelligent prompts based on user historical query records, optimize the user query experience, and improve data retrieval efficiency.

[0012] In combination with some embodiments of the first aspect, in some embodiments, after the steps of generating a query history prompt based on historical query records and displaying a query result form and a query history prompt, the method further includes: determining the corresponding target BOM data in the query result form based on the data selection operation of the query user; receiving a data export instruction from the query user, determining the export configuration parameters, and generating export data corresponding to the target BOM data based on the export configuration parameters.

[0013] In the above embodiment, the management system provides a flexible data export function. Users can select target data and set export parameters according to actual needs, thereby realizing on-demand data export. Through the configurable export mechanism, it meets the data application needs in different scenarios and improves data utilization efficiency.

[0014] In combination with some embodiments of the first aspect, in some embodiments, after the step of distributing the target task to the target user according to the implementation process of the workflow instance, the method also includes: when the target task is a data approval task, determining that the corresponding target user is the approval personnel, and obtaining the file to be approved as the approval target; based on the file to be approved, generating an approval preview file that meets the approval requirements; the approval requirements include digital signatures and PDF file generation; after receiving the approval confirmation information from the approval personnel, using the approval preview file as the approval confirmation file, uploading the approval confirmation file and the process completion information to the Teamcenter platform, so that the workflow instance enters the next implementation process.

[0015] In the above embodiment, the management system constructs a standardized approval process, supports approval requirements such as digital signatures and PDF file generation, realizes the standardization and electronicization of the approval process, generates approval preview files that meet the requirements, improves approval efficiency, and ensures the standardization of the approval process.

[0016] In combination with some embodiments of the first aspect, in some embodiments, the steps of receiving product source files uploaded by target users, determining model parameters and BOM data based on the product source files, and storing the product source files, model parameters and BOM data in the Teamcenter platform specifically include: receiving product source files uploaded by target users, and determining model parameters and BOM data based on the product source files; verifying the model parameters and BOM data based on preset data verification rules, and generating a verification result; when the verification result is verification passed, storing the product source files, model parameters and BOM data in the Teamcenter platform.

[0017] In the above embodiment, the management system automatically verifies the model parameters and BOM data through preset rules, thereby ensuring the accuracy and standardization of the data and reducing the risk of errors in subsequent data applications through strict data quality control.

[0018] In combination with some embodiments of the first aspect, in some embodiments, after the step of verifying model parameters and BOM data based on preset data verification rules and generating verification results, the method also includes: when the verification result is verification failure, determining an error prompt code for verification failure; based on the error prompt code, generating a corresponding data modification prompt; and displaying prompt information including model parameters, BOM data and data modification prompts.

[0019] In the above embodiment, when data verification fails, the management system can generate specific modification prompts to help users quickly locate and solve problems, thereby improving data processing efficiency and reducing user operation difficulty.

[0020] In the second aspect, an embodiment of the present application provides a management system, which includes: an automated processing module for receiving project generation instructions from a management terminal and generating a workflow instance based on a preset template of a Teamcenter platform; the automated processing module is also used to distribute target tasks to target users according to the implementation process of the workflow instance; the target tasks include data review, data approval and data release; a data storage module is used to receive product source files uploaded by target users, determine model parameters and BOM data based on the product source files, and store the product source files, model parameters and BOM data in the Teamcenter platform; the product source files include design drawings, test data and associated documents; a permission management module is used to determine the requesting user and modified file corresponding to the data modification request when a data modification request for model parameters or BOM data is detected, and determine whether the requesting user has the modification permission to modify the file according to the user permission table; a version control module is used to back up the modified file and generate a modified data version of the modified file when the requesting user has the modification permission to modify the file; the version control module is also used to collect the modification history of the modified file including the modification content, modification time and operator information, and store the modification history to the Teamcenter platform.

[0021] In a third aspect, an embodiment of the present application provides a management system, comprising: one or more processors and a memory; the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code includes computer instructions, and the one or more processors call the computer instructions to enable the management system to execute the method described in the first aspect and any possible implementation method of the first aspect.

[0022] In a fourth aspect, an embodiment of the present application provides a computer program product comprising instructions, which, when executed on a management system, enables the management system to execute the method described in the first aspect and any possible implementation of the first aspect.

[0023] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, comprising instructions, which, when executed on a management system, enables the management system to execute the method described in the first aspect and any possible implementation of the first aspect.

[0024] It is understandable that the management system provided in the second and third aspects, the computer program product provided in the fourth aspect, and the computer storage medium provided in the fifth aspect are all used to execute the method provided in the embodiment of the present application. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method, which will not be repeated here.

[0025] One or more technical solutions provided in the embodiments of the present application have at least the following technical effects or advantages: 1. Due to the use of the workflow instance generation and task distribution mechanism based on the Teamcenter platform, as well as a complete data management and version control system, the full life cycle management and collaborative processing of product data are realized, effectively solving the problems of decentralized data management, lax authority control, and chaotic version management in the existing technology, thereby achieving standardization, automation, and security of data management. The system automatically distributes tasks through workflow instances, combined with strict authority control and version management, to ensure the controllability and traceability of data modification. At the same time, through the complete modification history record, the whole process monitoring of data changes is realized, which significantly improves the efficiency and quality of product data management.

[0026] 2. Due to the adoption of an intelligent export mechanism based on data selection operations and export configuration parameters, combined with the query history prompt function, a flexible and efficient data export system has been established, which effectively solves the problems of single data export function, complex operation and low efficiency in the existing technology, thereby achieving accurate data export and efficient application. The system provides intelligent prompts by recording historical query information and allows users to configure export parameters according to actual needs, which greatly simplifies the data export process, improves data utilization efficiency, and ensures the accuracy and integrity of the exported data.

[0027] 3. Due to the use of preset data verification rules to automatically verify model parameters and BOM data, a strict data quality control system has been established, which effectively solves the problems of uneven data quality and difficulty in timely detection of errors in existing technologies, thereby achieving comprehensive protection of data accuracy and standardization. Through the automated data verification mechanism, the system conducts a comprehensive inspection before data storage, promptly detects and prevents the writing of non-standard data, significantly improves data quality, reduces the risk of errors in subsequent data applications, and provides reliable data support for product development. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 It is a flow chart of a method for managing model parameters and bill of materials based on Teamcenter in an embodiment of the present application; Figure 2 It is a schematic diagram of task release on the Teamcenter platform of the management system in an embodiment of the present application; Figure 3 It is a schematic diagram of the user operation interface on the Teamcenter platform of the management system in the embodiment of the present application; Figure 4 is another flowchart of a method for managing model parameters and bill of materials based on Teamcenter in an embodiment of the present application; Figure 5 (a) is a schematic diagram of a PDF file on the Teamcenter platform of the management system in an embodiment of the present application; Figure 5 (b) is a schematic diagram of BOM comparison on the Teamcenter platform of the management system in the embodiment of the present application; Figure 5 (c) is a schematic diagram of BOM export on the Teamcenter platform of the management system in an embodiment of the present application; Figure 6 This is a schematic diagram of a functional module structure of a management system in an embodiment of the present application; Figure 7 It is a schematic diagram of the structure of a physical device of the management system in an embodiment of the present application. DETAILED DESCRIPTION

[0029] The terms used in the following embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to be used as limitations to the present application. As used in the specification of the present application, the singular expressions "one", "a kind of", "above", "the" and "this" are intended to also include plural expressions, unless there is a clear indication to the contrary in the context. It should also be understood that the term "and / or" used in the present application refers to any or all possible combinations comprising one or more of the listed items.

[0030] In the following, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as suggesting or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features, and in the description of the embodiments of the present application, unless otherwise specified, "plurality" means two or more.

[0031] This application is based on the Teamcenter platform and is developed with Teamcenter software through a series of innovative designs. It covers the functions of Teamcenter and DB Magic, allowing engineering users to complete the properties, modeling, and drawing of parts in the Teamcenter system; complete the properties, assembly, drawing, Bom, Spec., and Model Number of components; complete the import of external electrical and test files (CAD, Excel, Word, PPT, Zip, etc.); and finally complete the release, modification, and query functions of the above operations. This will improve the efficiency, accuracy, and user experience of product development, reduce human errors, and accelerate product time to market.

[0032] For ease of understanding, the following is a description of the process of the method provided by this implementation. Figure 1 , which is a flow chart of a method for managing model parameters and bill of materials based on Teamcenter in an embodiment of the present application.

[0033] S101. Receive a project generation instruction from a management terminal, and generate a workflow instance based on a preset template of the Teamcenter platform.

[0034] Among them, the management terminal refers to the client device used to initiate project creation and management operations; the project generation instruction refers to the operation instruction sent by the user through the management terminal to create a new project; the Teamcenter platform refers to the collaborative platform system used for product lifecycle management; the workflow instance refers to the specific project and its workflow generated based on the preset template.

[0035] When a user creates a new product development project, the management system will execute this step. Specifically, the management system first receives the project generation instruction from the management terminal, and then retrieves the corresponding preset template from the Teamcenter platform according to the project type information contained in the instruction. The system automatically generates a workflow instance suitable for the current project based on the configuration information of the template, including process nodes, task types, processing rules, etc., to achieve standardized initialization of the project.

[0036] See also Figure 2 , Figure 2 It is a schematic diagram of task release on the Teamcenter platform of the management system in an embodiment of the present application; Figure 2This is the interface diagram of a new process. 201 is Process Template, which is a preset process template for users to choose. 202 is Assign All Tasks, which is a selection control for assigning all tasks. 203 is approve, which is a list of personnel at the approval node. 204 is the name of the role to which the task is assigned, which can be obtained by clicking the search icon 205 in the role search box and group search box below. 206 is the member list preview box, which can be used to view the personnel composition of the corresponding node. 207 is the Add button, which can be used to add corresponding tasks and personnel assignments. 208 is the OK confirmation button, which can be clicked to generate a new workflow instance, and the corresponding tasks will be distributed to the workbenches used by the above-mentioned added personnel.

[0037] S102: Distribute target tasks to target users according to the implementation process of the workflow instance.

[0038] Among them, the implementation process of the workflow instance represents the standardized work steps in the project execution process; the target task refers to the specific work content that needs to be completed; the target task can be data review, data approval and / or data release; data review refers to the compliance check of uploaded data; data approval represents the formal confirmation process of data; data release refers to the process of putting approved data into use; the target user refers to the system user assigned to perform the task.

[0039] When the workflow instance is created, the management system starts to execute task distribution. Specifically, the system first parses the implementation process defined in the workflow instance to determine the task type and processing requirements that need to be performed at the current stage. Subsequently, the system accurately assigns tasks to target users with corresponding permissions and responsibilities based on the task attributes and user role permissions, and simultaneously sends task notifications to ensure that tasks are carried out in a timely manner.

[0040] In some embodiments, the task distribution process can be implemented in a variety of ways: optionally, analyzing task dependencies; determining the order of task execution; matching user role permissions; generating a task distribution list; and pushing task notifications. Optionally, reading workflow configuration; identifying the current execution node; querying the list of available personnel; executing the task allocation algorithm; and updating the task status. It is understandable that other methods can also be used to complete the task distribution process, which is not limited here.

[0041] When performing task assignment, you can also use a task assignment optimization model; the task assignment optimization model is based on historical task assignment records, task completion status, and user feedback as training data, combined with user role, authority and other attribute information, to train the model to learn the optimal task assignment strategy. The task assignment optimization model uses a reinforcement learning architecture to model task assignment as a sequential decision problem. The task assignment optimization model considers multi-dimensional features such as user workload, professional field, and historical performance, and evaluates the benefits of different assignment plans through a value network. By inputting the task information to be assigned and the current list of available users, the task assignment optimization model comprehensively evaluates various assignment plans, outputs the optimal task-user matching result, and realizes the intelligent distribution of tasks.

[0042] S103, receiving the product source file uploaded by the target user, determining the model parameters and BOM data according to the product source file, and storing the product source file, model parameters and BOM data in the Teamcenter platform.

[0043] Among them, product source files refer to original data files related to product development; the product source files include design drawings, test data and related documents; design drawings refer to the engineering design drawings of the product; test data refer to the data records generated during the product testing process; related documents refer to product-related instruction documents, specifications and other supporting documents; model parameters refer to the key technical parameters in the product design model; BOM data refers to the product bill of materials information.

[0044] When the target user starts to process the assigned task, the management system executes the data processing flow. Specifically, the system receives various product source files uploaded by the user, and automatically extracts the model parameters and BOM data contained in the file through the data parsing engine. The system performs standardized processing and format conversion on the extracted data to ensure that the data complies with the platform storage specifications, and finally stores all the data in the corresponding database of the Teamcenter platform.

[0045] See also Figure 3 , Figure 3 It is a schematic diagram of the user operation interface on the Teamcenter platform of the management system in the embodiment of the present application. Figure 3It is the user's operation interface. 301 is the menu bar, which displays the menu of the current application module, including common operation controls such as File and Edit. 302 is the toolbar, which provides shortcut buttons for commonly used menu options. The toolbar buttons vary with different application modules. 303 is the navigator page, which provides methods for quickly accessing data and application modules, including: Search, My Worklist, My Project, My Links, My Saved Searches, My View / Markup. The application list includes: My Teamcenter, Structure Manager, Lifecycle Viewer, Schedule Manager, etc. 304 is the data structure area, which displays a data storage method in the form of a folder, which is a relatively traditional data organization mode. 305 is the data information display area, which provides Summary, Details, Impact Analysis, Viewer, and JTPreview. Summary: displays the basic information of the object, such as: Name, Owner, Group ID, etc. Details: displays the data contained under the object, such as: ItemRevision, Dataset, Form; Impact Analysis: Displays the Used / Reference relationship of the object; Viewer: Used to view object properties and data sets online, such as Word, PPT, Excel; JTPreview: View the JT model (lightweight model); 306 is the information center, which displays the object's permissions, status and other information in a graphical form.

[0046] It is understandable that by logging in with an account password, users (including developers and administrators) can log in as follows Figure 3 The user operation interface shown. On this user operation interface, the user can quickly find the application module where the corresponding data is located through the navigator page 303, and the stored related data files and folders are displayed in the data structure area 304; after the user selects the corresponding data file in the data structure area 304, the detailed information of the data file will be displayed in the data information display area 305, and the user can view or modify the information.

[0047] S104: When a data modification request for model parameters or BOM data is detected, determine the requesting user and the modification file corresponding to the data modification request. S105: Determine whether the requesting user has the modification authority to modify the file according to the user authority table.

[0048] Among them, the data modification request refers to the data change application submitted by the user; the requesting user refers to the system user who initiates the modification request; the modified file refers to the target file that needs to be changed; and the user permission table refers to the data table that stores the user access permission configuration.

[0049] When the management system detects a data modification request, it starts the permission verification process. Specifically, the system first parses the user information and target file information in the modification request, and then queries the user permission table for the permission configuration corresponding to the user. The system compares the user's actual permissions with the file's required modification permissions to determine whether the user has sufficient permissions to perform the modification operation.

[0050] In some embodiments, permission verification can be implemented in a variety of ways: optionally, parsing request parameters; querying user permissions; obtaining file attributes; performing permission matching; and returning verification results. Optionally, verifying user identity; checking file status; analyzing operation type; determining permission level; and recording verification logs. It is understandable that other methods can also be used to complete the permission verification process, which is not limited here.

[0051] If the requesting user has the modification permission to modify the file, perform the following steps: S106. Back up the modified file and generate a modified data version of the modified file.

[0052] Among them, the modification permission refers to the user's operation permission to change the file; the backup file refers to the original file copy before modification; the modified data version refers to the new version of the data file after modification.

[0053] When the user authority verification is passed, the system performs file version management. Specifically, the system first creates a complete backup of the target modified file to ensure that the original data is traceable. The system then creates a new version identifier for the modification operation, and records the modified content in the new version, while maintaining the association between versions to achieve effective management of file versions. In some embodiments, version management can be implemented in a variety of ways: optionally, creating a file snapshot; generating a version number; establishing a version branch; updating the version status; synchronizing version information. Optionally, copy the original file; initialize a new version; record version attributes; establish a version link; and submit version changes. It is understandable that other methods can also be used to complete version management, which is not limited here.

[0054] S107. Collect the modification history records of the modified files, including the modification content, modification time, and operator information, and store the modification history records in the Teamcenter platform.

[0055] Among them, the modification history record represents a detailed record of the file modification operation; the modification content refers to the specific data change information; the modification time represents the time point when the modification is performed; and the operator information refers to the user information who performs the modification.

[0056] When the file modification operation is completed, the system performs history management. Specifically, the system automatically collects all relevant information generated during the modification process, including the specific content of the modification, the exact time when the modification occurred, the user information who performed the modification, etc. The system organizes this information into a standard format of historical records and stores it in the Teamcenter platform's history database to ensure that all modification operations are traceable and traceable.

[0057] In some embodiments, history record management can be implemented in a variety of ways: optionally, collect operation data; organize modification information; generate record documents; establish index relationships; perform record storage. Optionally, extract change content; record timestamps; associate user information; format record data; update history database. It is understandable that other ways can also be used to complete history record management, which is not limited here.

[0058] The following is a more detailed description of the process of the method provided by this implementation. Figure 4 , which is another flow chart of the method for managing model parameters and bill of materials based on Teamcenter in an embodiment of the present application.

[0059] S401 , reading the newly added user information of the newly added user, and determining the newly added access rights of the newly added user according to the permission allocation instruction of the management terminal.

[0060] Among them, the newly added user information refers to the basic data of the user to be added, including user name, department, position and other information; the authority allocation instruction refers to the user authority configuration command issued by the administrator through the management terminal; the newly added access rights refer to the system function and data access authorization granted to the new user; the management terminal refers to the operating device used by the system administrator to manage users.

[0061] When a new user needs to be added to the management system, the management system executes the user information reading and permission configuration process. Specifically, the management system first reads the new user's registration information form, including basic information, organizational structure information, etc. Then, based on the permission allocation instructions sent by the management terminal, combined with the user's job responsibilities and business needs, the specific operation permissions of the user in the system are determined, including functional permissions, data permissions, and approval permissions.

[0062] In some embodiments, user information reading and permission configuration can be implemented in a variety of ways: optionally, parsing the user information form; verifying information integrity; matching permission templates; adjusting permission parameters; generating permission configuration. Optionally, reading the organizational structure; determining user roles; selecting permission policies; setting access levels; creating permission mappings. It is understandable that user information reading and permission configuration can also be accomplished in other ways, which are not limited here.

[0063] S402. Update the newly added user information and newly added access rights to the user permission table of the Teamcenter platform.

[0064] The user permission table represents a database table that stores the permission configurations of all users in the system.

[0065] After completing the new user rights configuration, the management system executes the data update process. Specifically, the system first organizes the basic information and rights configuration data of the new user to form a standardized data structure. Then it connects to the user rights database of the Teamcenter platform, performs data insertion or update operations, ensures that the new user information is correctly recorded in the system, and establishes the corresponding index relationship.

[0066] In some embodiments, permission data update can be implemented in a variety of ways: optionally, organize user data; verify data format; establish data connection; execute data write; update index cache. Optionally, generate update statement; obtain data lock; back up original data; submit update content; release data lock. It is understandable that other ways can also be used to complete the permission data update process, which is not limited here.

[0067] S403: Receive a project generation instruction from the management terminal, and generate a workflow instance based on a preset template of the Teamcenter platform.

[0068] Referring to step S101 , the management system generates a workflow instance.

[0069] S404: Distribute the target task to the target user according to the implementation process of the workflow instance.

[0070] Referring to step S102 , the management system distributes target tasks.

[0071] In some embodiments, when the target task is a data approval task, the management system determines that the corresponding target user is the approver, and obtains the file to be approved as the approval target; based on the file to be approved, generates an approval preview file that meets the approval requirements; the approval requirements include digital signatures and PDF file generation; after receiving the approval confirmation information from the approver, uses the approval preview file as the approval confirmation file, uploads the approval confirmation file and process completion information to the Teamcenter platform, and allows the workflow instance to enter the next implementation process.

[0072] Among them, data approval tasks refer to work items that require data review and confirmation; approvers refer to system users with approval authority; files to be approved refer to target documents that require approval; approval preview files refer to special file formats generated for easy approval; digital signatures refer to electronic approval signature information; PDF files refer to document formats that are easy to view and archive; approval confirmation information refers to the approval decision of the approver; and process completion information refers to the completion status of the current approval link.

[0073] When the system detects that the current task is a data approval task, it starts the approval process management. Specifically, the system first confirms the approval authority of the target user and obtains the file that needs to be approved. Then the system converts the file to be approved into a format suitable for approval, adds a digital signature area, and generates a preview file in PDF format. After receiving the confirmation information from the approver, the system uploads the preview file with the signature as the official approval confirmation file to the platform together with the approval completion status, triggering the advancement of the workflow.

[0074] For example, the subsequent drawing approval process includes the following steps: (1) Login: Users must first log in to the Teamcenter system and ensure that they have the appropriate access rights. After logging in, follow the system navigation to enter the corresponding project workspace. Figure 3 The operation interface shown.

[0075] (2) Submit drawings: In the project workspace, users need to upload the completed drawings (such as DWG, PDF, etc.) to the system. These drawings may be design drawings of parts, assembly drawings, etc., and need to be classified and named according to system requirements.

[0076] (3) Initiate approval: After uploading the drawing, the user needs to initiate approval through the system's built-in approval process. In the approval process, the user can specify the approver, set approval conditions and deadlines, etc. The approval process usually includes multiple stages, such as preliminary review, re-review, and final review. The approver at each stage needs to perform approval operations according to the system prompts.

[0077] (4) Approval process: After the approver logs into the system, he / she will see a list of drawings to be approved in the to-do list. The approver needs to carefully review the contents of the drawings and perform the approval operation in the system after confirming that they are correct. If the approval is not passed, the specific reason needs to be filled in and the document will be returned to the submitter; if the approval is passed, the document will enter the next approval stage or complete the approval process.

[0078] (5) Approval result feedback: The approval result will be promptly fed back to the submitter and other relevant personnel. The submitter needs to modify or improve the drawings according to the approval opinions and resubmit them for approval.

[0079] In some embodiments, the process of creating a project workflow instance can be implemented in a variety of ways: optionally, receiving basic project information; matching a standard template corresponding to the project type; extracting template configuration parameters; generating a workflow instance framework; initializing instance parameters. Optionally, parsing project generation instructions; obtaining user-defined configurations; selecting a basic template; merging customized configurations; and building a workflow instance. It is understandable that other methods can also be used to complete the creation of a workflow instance, which is not limited here.

[0080] In some embodiments, approval process management can be implemented in a variety of ways: optionally, verifying approval authority; preparing approval documents; generating signature areas; converting file formats; and submitting approval results. Optionally, reading task information; obtaining approval documents; processing file formats; recording approval operations; and updating process status. It is understandable that other methods can also be used to complete approval process management, which is not limited here.

[0081] See also Figure 5 , Figure 5 (a) is a schematic diagram of a PDF file on the Teamcenter platform of the management system in the embodiment of the present application; C00002-EO refers to the name of the project process, and the EO (Engineering Order) process is an engineering change order process, which is a standardized workflow for managing product engineering changes in the Teamcenter platform. Released refers to the released version, and C00002-0 is the corresponding generated PDF file, which may contain digital signature information.

[0082] For example, after the drawings are approved, users can convert them into PDF format for archiving or distribution. PDF generation and batch downloading include the following steps: (1) Select drawings: In the Teamcenter system, users can select the drawing version objects for which PDFs need to be generated through modules such as "My Teamcenter" or "Structure Manager". Multiple selection is supported so that multiple drawings can be processed at the same time.

[0083] (2) Generate PDF: Click [MOOG] → [Merge Print PDF] in the function menu. The system will automatically search and load the corresponding PDF file (if it already exists) based on the version information and attributes of the selected drawing (such as mo6_DesignAuthority, etc.). If the PDF file does not exist, the system may prompt the user to convert or re-upload it. If the value of the attribute mo6_DesignAuthority on revision is 76 or 79, the system will first obtain the first 7 digits of the object ID as the Master ID and search for the component (Master Part) with that number in the system. Then check whether the latest version of the part is consistent with the component family version, and whether there are any published UGPART and PDF files under the latest version of the Master Part. If the value of the attribute mo6_DesignAuthority on revision is not 76 or 79, the system will decide whether to directly obtain the PDF under that version or perform other search operations based on whether the ID contains ".CN".

[0084] (3) Merge and print: The system will merge the PDF files corresponding to all selected drawing versions and open the merged PDF file on the user's computer. The user can directly view, print or save the file.

[0085] (4) Batch download: If you need to batch download PDF files of multiple drawings, you can select multiple part versions in "My Teamcenter" or "Structure Manager" and click [MOOG] → [Batch Download PDF]. The system will merge the published drawings corresponding to all selected versions into one PDF file and prompt the user to download it.

[0086] S405. Receive the product source file uploaded by the target user, determine the model parameters and BOM data according to the product source file, and store the product source file, model parameters and BOM data in the Teamcenter platform.

[0087] Referring to step S103, the management system will store the product source files uploaded by the user.

[0088] In some embodiments, the management system receives product source files uploaded by the target user, and determines model parameters and BOM data based on the product source files; verifies the model parameters and BOM data based on preset data verification rules, and generates verification results; when the verification result is passed, the product source files, model parameters and BOM data are stored in the Teamcenter platform.

[0089] Among them, model parameters refer to the technical parameter information of product design; BOM data refers to the structured data of the product bill of materials; data verification rules refer to the standard specifications used to verify the correctness of data; and verification results indicate the execution status of data verification.

[0090] When users upload product-related files, the management system starts the data processing and verification process. Specifically, the system first receives and parses the product source files uploaded by users, and extracts model parameters and BOM data from them. Subsequently, the system calls the preset data verification rule set to fully verify the extracted data, including data format, value range, association relationship, etc. After the verification is passed, the system stores all data in the platform in a standard format.

[0091] In some embodiments, the verification step can be performed when the BOM data is imported or updated. By verifying the format, integrity, compliance, etc. of the BOM data, the imported or updated BOM data can be ensured to be accurate. In some embodiments, the data verification process can be implemented in a variety of ways: optionally, parsing the source file content; extracting key data; loading verification rules; performing data verification; saving verification results. Optionally, preprocessing file data; classifying data items; applying verification strategies; generating verification reports; and performing data storage. It is understandable that other methods can also be used to complete the data verification process, which is not limited here.

[0092] In some embodiments, the management system will determine an error prompt code for verification failure when the verification result is verification failure; generate a corresponding data modification prompt based on the error prompt code; and display prompt information including model parameters, BOM data and data modification prompts.

[0093] Among them, verification failure means that the data does not meet the verification rule requirements; the error prompt code refers to the code that identifies the specific error type; the data modification prompt refers to the instruction information to guide the user to correct the data; the prompt information refers to the complete feedback content displayed to the user.

[0094] When the data verification result shows that it fails, the management system starts the error handling process. Specifically, the system first determines the specific error type based on the verification result and generates the corresponding error code. Then the system queries the preset prompt information library based on the error code and generates targeted modification suggestions. Finally, the system integrates the erroneous data content and modification suggestions into a complete prompt information and displays it to the user in a clear and easy-to-understand way.

[0095] It should be noted that the verification of data format will use an intelligent verification rule model; the intelligent verification rule model uses historical data modification records and verification results as training sets during training, including model parameters, BOM data and their corresponding correctness annotations. Through statistical learning and rule mining methods, the association rules and constraints between data are learned. The intelligent verification rule model combines decision trees and association rule mining algorithms to build a multi-level data verification rule network. The model contains multiple sub-modules such as parameter validity check, data consistency verification, and correlation analysis, and can dynamically update rule weights. By inputting the model parameters and BOM data to be verified, the intelligent verification rule model can execute each layer of verification rules in turn, check the format standardization, value rationality and association consistency of the data, and output the verification results and specific error prompt codes.

[0096] S406: Receive a data query request, and determine the query user and query file corresponding to the data query request. S407: Determine whether the query user has the query permission to query the file according to the user permission table.

[0097] Among them, the data query request refers to the data retrieval instruction initiated by the user; the query user refers to the system user who initiates the data query; the query file refers to the target data file that needs to be retrieved; the query permission refers to the user's access and viewing permission to specific data; the user permission table refers to the database that stores the user permission configuration.

[0098] When the system receives a data query request from a user, it starts the permission verification process. Specifically, the system first parses the user identity information and target query file information contained in the query request. Then it queries the user permission table to obtain the user's permission configuration and matches it with the access requirements of the target file to determine whether the user has sufficient permissions to access the queried file, thereby ensuring the security of data access.

[0099] In some embodiments, query permission verification can be implemented in a variety of ways: optionally, extract query parameters; verify user identity; obtain permission configuration; check file attributes; perform permission matching. Optionally, parse request content; query user group; read security policy; determine access level; return verification result. It is understandable that other methods can also be used to complete the query permission verification process, which is not limited here.

[0100] If the query user has the query permission to query the file, step S408 is executed to determine the data query area and query screening conditions on the Teamcenter platform according to the data query request.

[0101] The data query area indicates the data scope to be searched in the Teamcenter platform; the query filter condition refers to the data filtering rules set by the user, including parameters such as time range and data type.

[0102] When the user's query permission is verified, the management system executes the query parameter parsing process. Specifically, the system analyzes the search requirements contained in the query request and determines the specific data areas that need to be searched in the platform, such as project libraries, document libraries, etc. At the same time, the system parses the query conditions set by the user, including but not limited to time range, data type, keywords and other screening parameters, to prepare for subsequent precise queries.

[0103] In some embodiments, query parameter parsing can be implemented in a variety of ways: optionally, extracting query scope; parsing screening conditions; standardizing parameters; optimizing query strategies; generating query plans. Optionally, analyzing query statements; determining data domains; processing filtering rules; building query trees; optimizing execution paths. It is understandable that query parameter parsing can also be accomplished in other ways, which are not limited here.

[0104] S409: Determine the query result form according to the data query area and the query screening condition.

[0105] The query result form represents a query result data set organized in a specific format; the data query area represents the scope of the search; and the query filter condition refers to the data filtering rule.

[0106] After the query parameter parsing is completed, the management system executes the data retrieval process. Specifically, the system performs a search operation in the Teamcenter platform database according to the determined query area and screening conditions. The system extracts the data that meets the conditions, organizes and sorts them according to the predefined format, and finally generates a standardized query result form for users to view and use.

[0107] For example, the classification management and query of parts includes the following steps: (1) Log in to the system: The user first needs to log in to the Teamcenter system.

[0108] (2) Access the part classification management interface: On the main interface of Teamcenter, find and click the module entry related to part classification management, such as "Part Classification" or "Catalog Management". The specific name may vary depending on the system configuration.

[0109] (3) Browse or search for part categories: In the part category management interface, users can browse the category tree or use the search function to find a specific part category. Enter keywords or select a category path to narrow the search scope.

[0110] (4) Query part information: After finding the target category, the user can view the list of parts under that category. Click on a specific part to view its detailed information, including properties, drawings, BOM, etc.

[0111] (5) Filter and sort: Users can use the filter and sort functions to further refine the query results as needed. For example, sort or filter by part name, number, status, and other attributes.

[0112] (6) Export or save query results: Users can choose to export query results as files for analysis or sharing in external applications.

[0113] In some embodiments, query result generation can be achieved in a variety of ways: optionally, perform data retrieval; filter query results; sort data items; format output; generate result forms. Optionally, construct query statements; perform data matching; aggregate query results; apply display templates; optimize display effects. It is understandable that other ways can also be used to complete the query result generation process, which is not limited here.

[0114] S410: Determine whether there is a data query area or query screening condition in the historical query record.

[0115] Among them, historical query records refer to the user's past search operation data stored in the system; data query area refers to the range and type of data retrieved; query filter conditions refer to the data filtering parameters set by the user; existence judgment refers to the matching check of similar queries in historical records.

[0116] After obtaining the query results, the management system executes the historical record matching process. Specifically, the system first extracts the query history of the current user from the historical database, and then compares the data query area and filter conditions used in this query with the historical records. The system uses similarity calculation and pattern matching methods to determine whether the current query is similar to the historical query, and prepares for subsequent intelligent prompts.

[0117] Among them, the data similarity matching model is used for the similarity comparison. The data similarity matching model uses historical query records as training data during training, including features such as query area, filtering conditions, user operations, and the relevance annotations of these queries as labels. The model is trained by supervised learning, and the similarity calculation method of feature vectors is optimized so that the model can accurately identify similar query patterns. The data similarity matching model uses a vector space model or a neural network based on an attention mechanism to convert query features into high-dimensional vector representations, and calculates the similarity between queries through metrics such as cosine similarity. The core of the model is the feature extraction layer and the similarity calculation layer, which can handle different types of query features. By inputting the current query area and filtering conditions, the model converts them into feature vectors, performs similarity matching with historical query records, and outputs similarity scores. When the similarity exceeds the preset threshold, the historical prompt generation mechanism is triggered.

[0118] Comparison of BOM data in the management system, which can be manually selected and triggered by the user. See Figure 5 , Figure 5 (b) is a schematic diagram of BOM comparison on the Teamcenter platform of the management system in the embodiment of the present application; Figure 5 The left and right sides of the upper part of (b) list different versions of files. After comparison, different files will be marked with highlighted information. Figure 5 The lower part of (b) is a comparison report, which specifically identifies the different data names, the changed parts of the data before and after, etc.

[0119] It should be noted that the BOM comparison steps include: (1) Log in to the system: The user needs to log in to the Teamcenter system. Make sure that you have the appropriate permissions to access the BOM comparison function.

[0120] (2) Access the BOM management interface: On the main interface of Teamcenter, find and click the "Structure Manager" module entrance to enter the BOM management interface.

[0121] (3) Select BOM version: In the BOM management interface, use the search or browse function to find the BOM version you want to compare. You can select two or more different versions of BOMs for comparison.

[0122] (4) Start BOM comparison: After selecting the BOM version to be compared, find and click "CompareBOMs" or a similar comparison button on the interface. The specific name of this button may vary depending on the system version, but it usually appears after the BOM version is selected.

[0123] (5) View comparison results: After clicking the Compare button, the system will generate a comparison report showing the differences between two or more BOM versions. Users can view which materials, quantities, or levels have changed in the report.

[0124] (6) Export or save comparison results: As needed, users can choose to export the comparison results to Excel, PDF or other formats for further analysis or archiving.

[0125] If it exists, step S411 is executed to generate a query history prompt according to the historical query record, and display the query result form and the query history prompt.

[0126] Among them, the query history prompt refers to the auxiliary information prompt generated based on the historical record; the query result form refers to the data set obtained in this search; the historical query record refers to the user's past search operation record; the display operation refers to the process of presenting information to the user.

[0127] When it is confirmed that there is a matching historical record, the management system executes the prompt generation and result display process. Specifically, the system first analyzes the matched historical records and extracts information such as query frequency, access time, and related operations. Based on this information, the system generates query history prompts containing usage suggestions, related recommendations, etc. Finally, the system lays out the current query result form and the generated historical prompt information and presents them to the user in an optimized manner.

[0128] In some embodiments, the management system determines the corresponding target BOM data in the query result form according to the query user's data selection operation; receives the query user's data export instruction, determines the export configuration parameters, and generates export data corresponding to the target BOM data based on the export configuration parameters.

[0129] Among them, the data selection operation means that the user selects the data items to be exported; the target BOM data refers to the selected bill of materials data; the data export instruction refers to the user command that triggers the export operation; the export configuration parameter refers to the settings that control the export format and content, which can be; the exported data refers to the final generated data file.

[0130] When the user needs to export the query results, the management system starts the data export process. Specifically, the system first records the specific data items selected by the user in the query results and determines the range of BOM data to be exported. Then the system receives the export parameters set by the user, including configuration information such as file format, export fields, sorting method, such as hierarchical export (such as OneLevel and All Level, including data at different levels) and paging export. Finally, the system converts the selected data into the specified format based on these configuration parameters and generates the final export file.

[0131] See also Figure 5 , Figure 5 (c) is a schematic diagram of BOM export on the Teamcenter platform of the management system in an embodiment of the present application; Figure 5 After clicking MOOG Customization in (c), you can use "Export bom" to export the selected BOM data.

[0132] It should be noted that the export operation has different execution steps for different users. Among them, the BOM export for general users includes the following steps: (1) Enter the Structure Manager module: First, make sure you are logged in to the MOOG TC system and navigate to the Structure Manager module.

[0133] (2) Select the data object and send: In Structure Manager, find the data object for which you want to export the BOM. This is usually a product, part, or project. After selecting the object, click Action to send it to the export process.

[0134] (3) Select the export type and level: After the data object is sent to the export interface, click the MOOG menu and select "Export BOM (One Level)" or "Export BOM (All Level)" to export a single-level BOM or a full-level BOM as required.

[0135] (4) Select the export directory and confirm: The system will pop up a dialog box to select the save location of the exported file. After selecting the directory, click "Open" or a similar confirmation button.

[0136] (5) Check the exported BOM file: After the export is completed, go to the selected directory to check the exported BOM file. The file should contain the BOM information of the selected data object, usually in Excel or CSV format, which is convenient for subsequent processing and analysis.

[0137] For Buyer users (i.e. users with special feature subscriptions), in addition to the above general steps, you can also perform the following specific operations: (1) Access Structure Manager and send data objects: First enter the Structure Manager module, find the data object you want to export BOM, and send it to the export process.

[0138] (2) Execute PUR BOM export: Click the MOOG menu and select "PUR BOM (One Level)" or "PUR BOM (All Level)" to export PUR (purchasing) related BOM information. These options provide Buyer users with a BOM view customized for procurement needs.

[0139] (3) Export and confirm: Select the export directory and click the confirm button. The system will export the PUR BOM file according to the set logic and specification. After the export is completed, go to the specified directory to check the file.

[0140] S412: When a data modification request for model parameters or BOM data is detected, determine the requesting user and the modification file corresponding to the data modification request. S413: Determine whether the requesting user has the modification authority to modify the file according to the user authority table.

[0141] Referring to step S104 and step S105 , the management system determines whether the requesting user has modification authority.

[0142] If the requesting user has the modification authority to modify the file, step S414 is executed to back up the modified file and generate a modified data version of the modified file.

[0143] Referring to step S106, the management system generates a modified data version.

[0144] S415. Collect the modification history records of the modified files, including the modification content, modification time, and operator information, and store the modification history records in the Teamcenter platform.

[0145] Referring to step S107, the management system stores the modification history record.

[0146] In the embodiment of the present application, due to the use of the Teamcenter-based model parameter and bill of materials management method, innovations are made in the following aspects: 1. Integrated design environment: Teamcenter provides an integrated design environment that seamlessly integrates multiple design links such as CAD (computer-aided design), CAE (computer-aided engineering), and CAM (computer-aided manufacturing), allowing designers, engineers, and production personnel to collaborate on a unified platform to achieve data sharing and synchronization. In this integrated environment, model parameters (such as dimensions, materials, tolerances, etc.) are closely associated with BOM information, and any design changes can be immediately reflected in the BOM, reducing the problem of data inconsistency.

[0147] 2. Process-driven data management: The method uses a process-driven approach to manage data, and by defining a series of process nodes (such as approval, signature, and release), ensures that the flow of product design data complies with established business processes. For example, after the approval of the NX design drawing is completed, the system can automatically trigger the pre-developed corresponding processing program to convert the drawing into a signed PDF file and upload it back to Teamcenter. This process is completely controlled by the process without manual intervention.

[0148] 3. Automated data processing and verification: The system has newly developed a variety of built-in automated data processing and verification mechanisms, such as the check_part_family_revision handler, which is used to check the consistency of the main model version and the component family version to ensure the accuracy of the design data. When importing or modifying data, the system will automatically verify the legitimacy of the data (such as determining whether the value before the colon in the first line of data in the imported file is an allowed parameter type), and give clear prompts when errors are found to guide users to make corrections.

[0149] 4. Flexible template and configuration management: For frequently used operations, such as generating PDF files with signatures, the system provides flexible template configuration functions. Users can define attribute domains and positions in templates as needed, and then automatically apply these templates in the process. The flexibility of templates and configurations not only improves work efficiency, but also ensures the standardization and consistency of output documents.

[0150] 5. Intelligent BOM management: As one of the core data of product design, BOM is managed intelligently in Teamcenter. The system supports the display and query of multi-level BOM, and users can easily view the composition of each level of the product. At the same time, the system also provides a BOM comparison function, allowing users to compare different versions of BOM to identify differences. This function is particularly important in scenarios such as product design changes and version upgrades, and helps reduce production problems caused by inconsistent data.

[0151] 6. Fine control of data and permissions: Teamcenter supports fine control of data and permissions, ensuring that only users with corresponding permissions can access or modify specific data. This control mechanism not only protects the security of design data, but also promotes the smooth progress of team collaboration. In terms of data query, the system supports functions such as part classification management query, and users can quickly locate the required data according to different classification standards.

[0152] The following describes the management system in the embodiment of the present application from the perspective of modules. Figure 6, which is a schematic diagram of a functional module structure of a management system in an embodiment of the present application.

[0153] The management system includes: The automation processing module 601 is used to receive the project generation instruction from the management terminal and generate a workflow instance based on the preset template of the Teamcenter platform; the automation processing module is also used to distribute the target tasks to the target users according to the implementation process of the workflow instance; the target tasks include data review, data approval and data release; The data storage module 602 is used to receive the product source files uploaded by the target user, determine the model parameters and BOM data according to the product source files, and store the product source files, model parameters and BOM data in the Teamcenter platform; the product source files include design drawings, test data and related documents; The authority management module 603 is used to determine the requesting user and the modification file corresponding to the data modification request when a data modification request for model parameters or BOM data is detected, and determine whether the requesting user has the modification authority to modify the file according to the user authority table; The version control module 604 is used to back up the modified file and generate a modified data version of the modified file when the requesting user has the modification permission to modify the file; the version control module is also used to collect the modification history of the modified file including the modification content, modification time and operator information, and store the modification history to the Teamcenter platform.

[0154] In some embodiments, the management system permission management module 603 is also used to: read the new user information of the new user, determine the new access rights of the new user according to the permission allocation instructions of the management terminal; and update the new user information and new access rights to the user permission table of the Teamcenter platform.

[0155] In some embodiments, the management system also includes an intelligent assistance module 605, which is used to: receive a data query request, determine the query user and query file corresponding to the data query request, and determine whether the query user has the query permission for the query file according to the user permission table; if the query user has the query permission for the query file, the intelligent assistance module 605 determines the data query area and query filter conditions on the Teamcenter platform according to the data query request; determines the query result form according to the data query area and query filter conditions; determines whether there is a data query area or query filter conditions in the historical query record; if so, the intelligent assistance module 605 generates a query history prompt according to the historical query record, and displays the query result form and the query history prompt.

[0156] In some embodiments, the management system also includes a data export module 606, which is used to: determine the corresponding target BOM data in the query result form according to the data selection operation of the query user; receive the data export instruction of the query user, determine the export configuration parameters, and generate export data corresponding to the target BOM data based on the export configuration parameters.

[0157] In some embodiments, the automated processing module 601 of the management system is also used to: when the target task is a data approval task, determine the corresponding target user as the approval personnel, and obtain the pending approval file as the approval target; based on the pending approval file, generate an approval preview file that meets the approval requirements; the approval requirements include digital signatures and PDF file generation; after receiving the approval confirmation information from the approval personnel, use the approval preview file as the approval confirmation file, upload the approval confirmation file and process completion information to the Teamcenter platform, so that the workflow instance enters the next implementation process.

[0158] In some embodiments, the management system also includes a data verification module 607, which is used to: receive product source files uploaded by target users, and determine model parameters and BOM data based on the product source files; verify model parameters and BOM data based on preset data verification rules, and generate verification results; when the verification result is passed, the data verification module 607 stores the product source files, model parameters and BOM data to the Teamcenter platform.

[0159] In some embodiments, the data verification module 607 of the management system is also used to: determine the error prompt code for verification failure when the verification result is verification failure; generate corresponding data modification prompts based on the error prompt code; and display prompt information including model parameters, BOM data and data modification prompts.

[0160] The above describes the management system in the embodiment of the present application from the perspective of modular functional entities. The following describes the management system in the embodiment of the present application from the perspective of hardware processing. Figure 7 , which is a schematic diagram of the structure of a physical device of the management system in an embodiment of the present application.

[0161] It should be noted that Figure 7 The structure of the management system shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0162] like Figure 7As shown, the management system includes a central processing unit (CPU) 701, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 702 or the program loaded from the storage part 708 to the random access memory (RAM) 703, such as executing the method described in the above embodiment. In the RAM 703, various programs and data required for system operation are also stored. The CPU 701, the ROM 702 and the RAM 703 are connected to each other through the bus 704. The input / output (I / O) interface 705 is also connected to the bus 704.

[0163] The following components are connected to the I / O interface 705: an input section 706 including an audio input device, a button switch, etc.; an output section 707 including a liquid crystal display (LCD) and an audio output device, an indicator light, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 710 as needed so that a computer program read therefrom is installed into the storage section 708 as needed.

[0164] In particular, according to an embodiment of the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present invention includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication part 709, and / or installed from a removable medium 711. When the computer program is executed by the central processing unit (CPU) 701, various functions defined in the present invention are performed.

[0165] It should be noted that specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, apparatus, or device.

[0166] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present invention. Each box in the flowchart or block diagram may represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions marked in the box may also occur in an order different from that marked in the accompanying drawings.

[0167] Specifically, the management system of this embodiment includes a processor and a memory. The memory stores a computer program. When the computer program is executed by the processor, the Teamcenter-based model parameter and bill of materials management method provided in the above embodiment is implemented.

[0168] As another aspect, the present invention further provides a computer-readable storage medium, which may be included in the management system described in the above embodiment; or may exist independently without being assembled into the management system. The above storage medium carries one or more computer programs, and when the above one or more computer programs are executed by a processor of the management system, the management system implements the Teamcenter-based model parameter and bill of materials management method provided in the above embodiment.

[0169] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. 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 application.

[0170] As used in the above embodiments, the term "when..." may be interpreted to mean "if..." or "after..." or "in response to determining..." or "in response to detecting...", depending on the context. Similarly, the phrases "upon determining..." or "if (the stated condition or event) is detected" may be interpreted to mean "if determining..." or "in response to determining..." or "upon detecting (the stated condition or event)" or "in response to detecting (the stated condition or event)", depending on the context.

[0171] Those skilled in the art can understand that to implement all or part of the processes in the above-mentioned embodiments, the processes can be completed by computer programs to instruct related hardware, and the programs can be stored in computer-readable storage media. When the programs are executed, they can include the processes of the above-mentioned method embodiments. The aforementioned storage media include: ROM or random access memory RAM, magnetic disk or optical disk and other media that can store program codes.

Claims

1. A method for managing model parameters and bill of materials based on Teamcenter, characterized in that: Applied to a management system, the method comprises: Receive project generation instructions from the management terminal and generate workflow instances based on preset templates on the Teamcenter platform; Distribute target tasks to target users according to the implementation process of the workflow instance; the target tasks include data review, data approval and data release; Receive the product source file uploaded by the target user, determine the model parameters and BOM data according to the product source file, and store the product source file, the model parameters and the BOM data in the Teamcenter platform; the product source file includes design drawings, test data and related documents; When a data modification request for the model parameter or the BOM data is detected, determining a requesting user and a modification file corresponding to the data modification request, and determining whether the requesting user has modification authority for the modification file according to a user authority table; If the requesting user has the modification authority for the modified file, backing up the modified file and generating a modified data version of the modified file; The modification history records of the modified files, including the modification content, modification time and operator information, are collected, and the modification history records are stored in the Teamcenter platform.

2. The method according to claim 1, characterized in that Before the step of receiving the project generation instruction from the management terminal and generating a workflow instance based on a preset template of the Teamcenter platform, the method further includes: Read the newly added user information of the newly added user, and determine the newly added access rights of the newly added user according to the permission allocation instruction of the management terminal; Update the newly added user information and the newly added access rights to the user permission table of the Teamcenter platform.

3. The method according to claim 1, characterized in that After the steps of receiving the product source file uploaded by the target user, determining the model parameters and BOM data according to the product source file, and storing the product source file, the model parameters and the BOM data in the Teamcenter platform, the method further includes: Receive a data query request, determine a query user and a query file corresponding to the data query request, and determine whether the query user has query authority for the query file according to the user authority table; If the query user has the query permission for the query file, determining the data query area and query screening conditions on the Teamcenter platform according to the data query request; Determine a query result form according to the data query area and the query screening condition; Determine whether the data query area or the query screening condition exists in the historical query record; If it exists, a query history prompt is generated according to the historical query record, and the query result form and the query history prompt are displayed.

4. The method according to claim 3, characterized in that After the steps of generating a query history prompt according to the historical query record and displaying the query result form and the query history prompt, the method further comprises: According to the data selection operation of the query user, determining the corresponding target BOM data in the query result form; A data export instruction from the querying user is received, export configuration parameters are determined, and export data corresponding to the target BOM data is generated based on the export configuration parameters.

5. The method according to claim 1, characterized in that After the step of distributing the target task to the target user according to the implementation process of the workflow instance, the method further includes: When the target task is a data approval task, the corresponding target user is determined to be an approval person, and the to-be-approved document as the approval target is obtained; Based on the document to be approved, generate an approval preview file that meets the approval requirements; the approval requirements include digital signature and PDF file generation; After receiving the approval confirmation information from the approver, the approval preview file is used as the approval confirmation file, and the approval confirmation file and process completion information are uploaded to the Teamcenter platform, so that the workflow instance enters the next implementation process.

6. The method according to claim 1, characterized in that The step of receiving the product source file uploaded by the target user, determining the model parameters and BOM data according to the product source file, and storing the product source file, the model parameters and the BOM data in the Teamcenter platform specifically includes: Receive the product source file uploaded by the target user, and determine the model parameters and BOM data according to the product source file; Based on preset data verification rules, verify the model parameters and the BOM data to generate a verification result; When the verification result is verification passed, the product source file, the model parameters and the BOM data are stored in the Teamcenter platform.

7. The method according to claim 6, characterized in that After the step of verifying the model parameters and the BOM data based on the preset data verification rules and generating the verification results, the method further includes: When the verification result is that the verification fails, an error prompt code for the verification failure is determined; Generate a corresponding data modification prompt according to the error prompt code; Prompt information including the model parameters, the BOM data and the data modification prompt is displayed.

8. A management system, characterized in that: include: The automation processing module is used to receive the project generation instructions from the management terminal and generate workflow instances based on the preset templates of the Teamcenter platform; The automation processing module is also used to distribute target tasks to target users according to the implementation process of the workflow instance; the target tasks include data review, data approval and data release; A data storage module, used for receiving the product source file uploaded by the target user, determining the model parameters and BOM data according to the product source file, and storing the product source file, the model parameters and the BOM data in the Teamcenter platform; The product source files include design drawings, test data and related documents; A rights management module, for determining, when a data modification request for the model parameter or the BOM data is detected, a requesting user and a modification file corresponding to the data modification request, and determining, according to a user rights table, whether the requesting user has the modification rights for the modification file; A version control module, used to back up the modified file and generate a modified data version of the modified file when the requesting user has the modification authority of the modified file; The version control module is also used to collect the modification history records of the modified files, including the modification content, modification time and operator information, and store the modification history records in the Teamcenter platform.

9. A management system, characterized in that: include: one or more processors and memory; The memory is coupled to the one or more processors, and the memory is used to store computer program codes, wherein the computer program codes include computer instructions, and the one or more processors call the computer instructions to enable the management system to execute the method according to any one of claims 1 to 7.

10. A computer-readable storage medium comprising instructions, characterized in that: When the instruction is executed on a management system, the management system is caused to execute the method according to any one of claims 1 to 7.

Images