A lightweight model construction and state control method in a PDM system

Abstract

This invention relates to a method for lightweight model construction and state control in a PDM system, comprising: S1 initiating a lightweight conversion task of a digital model from the PDM system; S2 persisting the lightweight conversion task to a database; S3 verifying the rationality of the lightweight conversion task scheduling; S4 checking whether the lightweight conversion task is a scheduled task; S5 the lightweight conversion server parsing the request task message and initiating conversion for each subtask; S6 downloading the original digital model; S7 transmitting lightweight conversion data to the lightweight conversion tool and appending the corresponding request; reporting the heartbeat status to the lightweight conversion server; S8 establishing a JSON file in a predefined format, and the conversion tool server periodically scanning and parsing the data in the JSON file; S9 generating a lightweight model file and uploading it to a file repository, inserting the JSON file scanning and parsing result message into a message queue; S10 the lightweight conversion server receiving the conversion result message asynchronously sent from the message queue and parsing the result message; and S11 implementing unified management and control of the lightweight digital model at the BOM end.

Description

Technical Field

[0001] This invention relates to the field of PDM, and specifically to a lightweight model construction and state control method in a PDM system. Background Technology

[0002] Fully 3D digital models have become indispensable data in aircraft development. Currently, a digital R&D system has been initially established in the field of aircraft design. In the development of multiple aircraft types, the drawing process has achieved full 3D and online collaboration, a closed-loop process for design changes has been established, the aircraft development status has been effectively controlled, and a comprehensive transformation from traditional 2D drawings to a fully 3D digital aircraft development model has been realized.

[0003] However, directly using the original full 3D digital model generated from current designs for design, simulation, and support still has limitations. Specifically, the original design model contains a large amount of design process information, resulting in a large data volume, which computers cannot support simulation applications involving complex sections or systems. Therefore, lightweight processing of the original design model is necessary to effectively support design applications across various disciplines. Traditional lightweight processing methods include:

[0004] 1) When the amount of lightweight data is small, designers process it themselves. However, due to different methods, the processed lightweight model data has inconsistent format, poor compatibility, and low reuse rate.

[0005] 2) When performing lightweighting at the whole machine level, the IT department downloads the design model to the computer using a local batch processing tool and then performs lightweighting batch processing on the entire machine model.

[0006] Both methods employ offline processing, resulting in a lightweight prototype that is separated from the original digital prototype in the PDM. With frequent changes in the design status of various aircraft components, this can easily lead to discrepancies between the lightweight model data status and accuracy in actual applications and the status of the original digital prototype.

[0007] Therefore, adopting an online lightweight processing method can solve the problem of consistency deviation in the digital model design state caused by offline processing. At the same time, using a data scheduling system can improve the real-time performance of data processing and support various complex business models at the time. Summary of the Invention

[0008] The purpose of this invention:

[0009] A method for lightweight model construction and state control in a PDM system is proposed, which realizes the unified management, application and service of lightweight digital prototype models based on the model EBOM, and supports the application requirements of lightweight digital prototype models with unified state in model development.

[0010] The technical solution of the present invention:

[0011] A lightweight model construction and state control method in a PDM system includes the following steps:

[0012] Step S1: Initiate a lightweight manual or scheduled automatic conversion task for the digital model from the PDM system according to the conversion rules;

[0013] Step S2: Persist the lightweight transformation task to the database;

[0014] Step S3: Verify whether the lightweight conversion task scheduling is reasonable according to the unified data access control policy;

[0015] Step S4: Check if the lightweight conversion task is a scheduled task. If it is a scheduled task, send a task message to the message queue after it is triggered at the scheduled time. Otherwise, send a message to the message queue immediately.

[0016] Step S5: The lightweight transformation server receives the transformation request task message sent asynchronously from the message queue, parses the request task message, and splits the task into multiple subtasks according to CI configuration items as the basic unit. Each subtask calls the lightweight transformation tool to initiate the transformation.

[0017] Step S6: Download the original digital model according to the original digital model address;

[0018] Step S7: The conversion tool server calls the lightweight conversion tool via command line, passes lightweight conversion data with CI configuration items as the basic unit to the lightweight conversion tool, and appends the corresponding request according to the lightweight conversion completion result; the conversion tool server periodically reports the heartbeat status to the lightweight conversion server to realize the status monitoring of the conversion tool server;

[0019] Step S8: The conversion tool server creates a JSON file in a predefined format at the address of the original digital model. The conversion tool server periodically scans and parses the data in the JSON file according to the corresponding scanning configuration for subsequent processing.

[0020] Step S9: Generate a lightweight model file and upload it to the file repository, and insert the JSON file scan parsing result message into the message queue;

[0021] Step S10: The lightweight conversion server receives the conversion result message sent asynchronously by the message queue, parses the result message, writes the conversion result into the lightweight soft attribute table, and stores it back into the PDM system;

[0022] Step S11: Implement unified management and control of the lightweight digital model on the BOM side.

[0023] Furthermore, in step 1, a lightweight manual or scheduled automatic conversion task of the digital model is initiated from the PDM system. The rules for manually initiating a conversion task for a specified time period from the PDM system are as follows:

[0024] (1) The lightweight model of CI node does not need to be converted separately. It can directly initiate the conversion of its associated DSI through validity. Users can choose the conversion format and check multiple default precisions, or input the precision. The lightweight conversion task of the DSI node corresponding to the current CI node is persisted to the database.

[0025] (2) When converting nodes above CI, the user inputs the validity filter PBS structure, selects the conversion format, conversion precision, validity and conversion method: persists the lightweight conversion tasks corresponding to all DSI nodes within the selected node context to the database;

[0026] (3) Low-order lightweight model conversion rules: Low-order lightweight models are generated from high-order lightweight models, that is, new low-order lightweight models are generated by converting existing high-order lightweight models.

[0027] (4) Conversion rules for the converted lightweight model

[0028] Rule 1: If the components under DSI are changed, it is permissible to repeatedly initiate a lightweight conversion with existing accuracy;

[0029] Rule 2: Components under DSI that are in an unreleased state are not allowed to initiate lightweight conversion;

[0030] Rule 3: Within the same sortie interval, the same version of the lightweight model with the same precision within the same sortie interval cannot be manually triggered;

[0031] The rules for automatically initiating a conversion model from the PDM system for a specified time period are as follows:

[0032] (1) Use the database transaction log to capture the rows that have been changed in the current time period, and directly use the parts filtered out in the transaction log as the parts numbers modified within the specified time period;

[0033] (2) Based on the specified time period, modify the set of components associated with the model and recursively search upwards according to the component structure relationship to obtain the set of CI nodes of the components associated with the model modified within the specified time period; if an obsolete or terminated parent node is found during the upward search for CI, and its parent is found to be valid and using the current version of the child component, continue to recursively search upwards until the CI level, and all recursively searched nodes are not obsolete or terminated; filter according to the found CI list, if a CI node is not within the range of models for incremental synchronous conversion, exclude it from the range of incremental synchronous conversion; if a CI item in the CI list is duplicated with a CI item in the top-level structure manually initiated by the user, exclude it from the range of incremental synchronous conversion; if a CI item in the CI list is duplicated, deduplication is performed; after the data is excluded, include all incremental lightweight conversion CIs of the same model into the same lightweight conversion request for lightweight conversion processing.

[0034] (3) Traverse the CI nodes in the CI list one by one: Starting from each CI node level, find the DSI node from the CI node, and traverse the components layer by layer based on the EPM object structure associated with the DSI node to obtain the original digital model; if the DSI is not associated with an EPM object, skip it; if the EPM object status of the component node is obsolete or terminated, obtain the previous valid version.

[0035] For CIs that are manually or automatically initiated from the PDM system for a specified time period, it is necessary to traverse the child nodes to ensure that all components are in an undetected state. Otherwise, the CI data in the undetected state will be recorded in the conversion log and the conversion will be re-initiated during the next incremental synchronization.

[0036] Furthermore, in step 5, the parameters for calling the conversion tool include the address of the original digital model, the unique identifier of the conversion instruction, the organizational relationship file of the original digital model, the conversion format, the conversion precision, and whether it is a top-level file.

[0037] Furthermore, in step 10, the information in the lightweight soft attribute table includes: component ID, validity, failure time, CSV file address link, lightweight model file address link, precision value, and conversion format; the encoding and name identifier of the lightweight model are automatically generated by the lightweight conversion server, and the generation rules, in addition to being related to the encoding of the associated component object, require the addition of a serial number.

[0038] Furthermore, in step 11, the unified management and control of the lightweight digital model at the BOM level includes lightweight model version management.

[0039] Lightweight model version management rules:

[0040] 1) The lightweight model and DSI major versions are kept consistent: When DSI changes to a major version, the lightweight model initiates a conversion and keeps synchronized with the new DSI version;

[0041] 2) Upgrade DSI to a smaller version, and the lightweight model initiates a conversion to the default precision and upgrades the lightweight model to a smaller version;

[0042] 3) Each successful conversion of a DSI minor version generates a lightweight model minor version, and the converted lightweight model minor version corresponds to the current DSI minor version.

[0043] Furthermore, in step S5, when the request task field needs to be expanded, an abstract interface is designed, and a data object class is instantiated from the configuration using a reflection mechanism. The object is then dynamically called to reduce code refactoring and provide the function of verifying the consistency of the data object.

[0044] Further, in step S6: using model library management, when the lightweight conversion server initiates a general scheduling task, it downloads all task-related original digital models in a unified manner, and caches the relevant task original digital models by establishing a shared disk.

[0045] Further, in step S7: Multiple instances of the conversion tool server are deployed, and load balancing is achieved through scheduling weights. The specific load balancing algorithm is as follows:

[0046] (1) Calculate the minimum completion time MinTi for all CI conversion tasks based on the number of parts N and the total size weight under CI;

[0047] (2) Sort all CI conversion tasks in ascending order to form queue L;

[0048] (3) Traverse all CI transformation tasks;

[0049] (4) Select the conversion tool server with the lowest current usage rate;

[0050] (5) Calculate the average completion time ACT and standard deviation SD of all CI conversion tasks based on the minimum completion time MinTi:

[0051]

[0052] Where n represents the total number of CI conversion tasks, and i is the current CI conversion task;

[0053] (6) If ACT < SD, it means that the lengths of all tasks in queue L are within a small range, so the next task is selected and assigned in order from the head of the queue; otherwise, the next task is selected and assigned in order from the tail of the queue.

[0054] (7) Remove the task assigned in (6) from queue L;

[0055] (8) If there are still tasks in queue L, return to (4) until there are no tasks in queue L.

[0056] End the traversal.

[0057] Furthermore, for steps S7 and S10, after the current task scheduling or callback times out, the lightweight conversion server is directly notified of the task timeout. By adding a cluster circuit breaker mechanism, when the current conversion tool server times out or encounters an error, the scheduling weight of the conversion tool server is dynamically reduced until it reaches zero. The circuit breaker node is recorded, and a trial task is sent at certain intervals. If no timeout occurs, the scheduling weight of the conversion tool server is increased or decreased until it is restored to the initial weight.

[0058] Beneficial effects of the present invention

[0059] This invention proposes a lightweight model construction and state control method in a PDM system. By establishing an online lightweight digital model construction and management system, and adopting online lightweight incremental synchronous conversion, manual conversion, and lightweight state control processing methods at the PDM BOM end, the method solves the problem of consistency deviation in digital model design state caused by offline processing. It realizes unified management, application, and service of lightweight digital prototype models based on the model EBOM, and supports the application requirements of lightweight digital prototype models with unified state in model development. Attached Figure Description

[0060] Figure 1 This invention provides a schematic diagram of unified data management for the integration of lightweight digital models with EBOM in PDM. Figure 1 ;

[0061] Figure 2 This invention provides a schematic diagram of unified data management for the integration of lightweight digital models with EBOM in PDM. Figure 2 ;

[0062] like Figure 1 , 2 As shown, unified management of digital models is achieved on the BOM side. The lightweight digital model major version and the DSI major version are consistent. Each successful conversion of a DSI minor version generates a lightweight digital model minor version, and the converted lightweight digital model minor version corresponds to the current DSI minor version.

[0063] Figure 3 A schematic diagram of a model conversion process provided in an embodiment of the present invention. Figure 1 .like Figure 3 As shown, this indicates that the model conversion is initiated from CI;

[0064] Figure 4 A schematic diagram of a model conversion process provided in an embodiment of the present invention. Figure 2 .like Figure 4 As shown, this indicates that the model conversion is initiated from the system;

[0065] Figure 5 A schematic diagram of a model conversion process provided in an embodiment of the present invention. Figure 3 .like Figure 5 As shown, this indicates that the model conversion is initiated from the cabin.

[0066] Figure 6 This is a schematic diagram illustrating the entire lightweight conversion process provided in an embodiment of the present invention. Figure 6 As shown, when a user requests the sending end to check in a dedicated component in the PDM system, the PDM system automatically calls the automatic conversion interface, or manually triggers the conversion for a certain node (such as machine type, system, subsystem, CI); the PDM system receives the conversion request and performs a series of operations.

[0067] Figure 7 This is a schematic diagram illustrating how to obtain an updated component CI node set according to an embodiment of the present invention. Figure 7 As shown, the set of components associated with the model is modified according to the specified synchronization time period, and the process is recursively performed. The model searches upwards according to the component structure relationship to obtain the set of CI nodes that have used the updated component.

[0068] Figure 8 Lightweight scheduling illustration provided for embodiments of the present invention Figure 1 .like Figure 8 As shown, this illustrates the conversion rules for low-order lightweight models when a corresponding high-order lightweight model of CI already exists.

[0069] Figure 9 Lightweight scheduling illustration provided for embodiments of the present invention Figure 2 .like Figure 9 As shown, the conversion rules for the converted lightweight model are displayed.

[0070] Figure 10 This is a schematic diagram of the coding serial number generation rule provided in an embodiment of the present invention. Detailed Implementation

[0071] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0072] One embodiment of the present invention is a lightweight model construction and state control method in a PDM system, to solve the technical problem of the lack of a data lightweight system in the prior art that supports near real-time lightweight model construction and state control in heterogeneous PDM systems. It includes the following steps:

[0073] Step 1: Initiate a lightweight manual or scheduled automatic conversion task for the digital model from the PDM system according to the conversion rules;

[0074] Step 2: Send the lightweight transformation task to the message queue;

[0075] Step 3: The lightweight transformation server receives the transformation request task message sent asynchronously from the message queue, parses the request task message, and splits the task into multiple subtasks according to CI configuration items as the basic unit. Each subtask calls the lightweight transformation tool to initiate the transformation.

[0076] Step 4: Download the original digital model from the original digital model address;

[0077] Step 5: The conversion tool server calls the lightweight conversion tool via command line, passes lightweight conversion data with CI configuration items as the basic unit to the lightweight conversion tool, and appends the corresponding request according to the lightweight conversion result;

[0078] Step 6: The conversion tool server creates a JSON file in a predefined format at the address of the original digital model. The conversion tool server periodically scans and parses the data in the JSON file according to the corresponding scanning configuration and sends it to the lightweight conversion server.

[0079] Step 7: The lightweight conversion server receives the conversion result message sent asynchronously from the message queue, parses the result message, writes the conversion result into the lightweight soft attribute table, and stores it back into the PDM system;

[0080] Step 8: Implement unified management and control of the lightweight digital model on the PDM BOM side.

[0081] The second embodiment of the present invention provides a lightweight model construction and state control method in a PDM system, comprising the following steps:

[0082] Step S1: Initiate a lightweight manual or scheduled automatic conversion task for the digital model from the PDM system. The rules for manually initiating a conversion task for a specified time period from the PDM system are as follows:

[0083] (1) The lightweight model of CI node does not need to be converted separately. It can directly initiate the conversion of its associated DSI through validity. Users can choose the conversion format and check multiple default precisions, or input the precision. The lightweight conversion task of the DSI node corresponding to the current CI node is persisted to the database. CI is the configuration item, DSI is the design instance, and PDM system is the product data management system.

[0084] (2) When converting nodes above CI, the user inputs a valid filter PBS structure and selects the conversion format, conversion precision, validity and conversion method: the lightweight conversion tasks corresponding to all DSI nodes in the selected node context are persisted to the database; where PBS is a structure tree composed of CI configuration items.

[0085] (3) Low-order lightweight model conversion rules: Low-order lightweight models are generated from high-order lightweight models, that is, new low-order lightweight models are generated by converting existing high-order lightweight models.

[0086] (4) Conversion rules for the converted lightweight model

[0087] Rule 1: If the components under DSI are changed, it is permissible to repeatedly initiate a lightweight conversion with existing accuracy;

[0088] Rule 2: Components under DSI that are in an unreleased state are not allowed to initiate lightweight conversion;

[0089] Rule 3: Within the same sortie interval, the same version of the lightweight model with the same precision within the same sortie interval cannot be manually triggered;

[0090] The rules for automatically initiating a conversion model from the PDM system for a specified time period are as follows:

[0091] (1) Use the database transaction log to capture the rows that have been changed in the current time period, and directly use the parts filtered out in the transaction log as the parts numbers modified within the specified time period;

[0092] (2) Based on the specified time period, modify the set of components associated with the model and recursively search upwards according to the component structure relationship to obtain the set of CI nodes of the components associated with the model modified within the specified time period; if an obsolete or terminated parent node is found during the upward search for CI, and its parent is found to be valid and using the current version of the child component, continue to recursively search upwards until the CI level, and all recursively searched nodes are not obsolete or terminated; filter according to the found CI list, if a CI node is not within the range of models for incremental synchronous conversion, exclude it from the range of incremental synchronous conversion; if a CI item in the CI list is duplicated with a CI item in the top-level structure manually initiated by the user, exclude it from the range of incremental synchronous conversion; if a CI item in the CI list is duplicated, deduplication is performed; after the data is excluded, include all incremental lightweight conversion CIs of the same model into the same lightweight conversion request for lightweight conversion processing.

[0093] (3) Traverse the CI nodes in the CI list one by one: Starting from each CI node level, find the DSI node from the CI node, and traverse the components layer by layer based on the EPM object structure associated with the DSI node to obtain the original digital model; if the DSI is not associated with an EPM object, skip it; if the EPM object status of the component node is obsolete or terminated, obtain the previous valid version.

[0094] Step S2: Persist the lightweight transformation task to the database;

[0095] Step S3: Verify whether the lightweight conversion task scheduling is reasonable according to the unified data access control policy;

[0096] Step S4: Check if the lightweight conversion task is a scheduled task. If it is a scheduled task, send a task message to the message queue after it is triggered at the scheduled time. Otherwise, send a message to the message queue immediately.

[0097] Step S5: The lightweight transformation server receives the transformation request task message sent asynchronously from the message queue, parses the request task message, and splits the task into multiple subtasks according to CI configuration items as the basic unit. Each subtask calls the lightweight transformation tool to initiate the transformation.

[0098] Step S6: Download the original digital model according to the original digital model address;

[0099] Step S7: The conversion tool server calls the lightweight conversion tool via command line, passes lightweight conversion data with CI configuration items as the basic unit to the lightweight conversion tool, and appends the corresponding request according to the lightweight conversion completion result; the conversion tool server periodically reports the heartbeat status to the lightweight conversion server to realize the status monitoring of the conversion tool server;

[0100] Step S8: The conversion tool server creates a JSON file in a predefined format at the address of the original digital model. The conversion tool server periodically scans and parses the data in the JSON file according to the corresponding scanning configuration for subsequent processing.

[0101] Step S9: Generate a lightweight model file and upload it to the file repository, and insert the JSON file scan parsing result message into the message queue;

[0102] Step S10: The lightweight conversion server receives the conversion result message sent asynchronously by the message queue, parses the result message, writes the conversion result into the lightweight soft attribute table, and stores it back into the PDM system;

[0103] Step S11: Implement unified management and control of the lightweight digital model on the PDM BOM side.

[0104] In this embodiment, for step S1: For CI of the conversion model initiated manually or automatically at regular intervals from the PDM system for a specified period of time, it is necessary to traverse the child nodes to ensure that all components are in an undetected state. Otherwise, the CI data in the undetected state is recorded in the conversion log and the conversion is re-initiated during the next incremental synchronization.

[0105] In this embodiment, for step S5, the parameters for calling the conversion tool include the address of the original digital model, the unique identifier of the conversion instruction, the organizational relationship file of the original digital model, the conversion format, the conversion precision, and whether it is top-level. When the request task field needs to be expanded, an abstract interface is designed, and a reflection mechanism is used to instantiate the data object class from the configuration, dynamically call the object, reduce code refactoring, and provide the function of verifying the consistency of the data object.

[0106] In this embodiment, for step S6, when the lightweight conversion server initiates a general scheduling task using model library management, it downloads all original digital models related to the task in a unified manner and caches the original digital models of the relevant tasks by establishing a shared disk.

[0107] In this embodiment, for step S7, load balancing is achieved by deploying multiple instances of the conversion tool server and scheduling weights. The specific load balancing algorithm is as follows:

[0108] (9) Calculate the minimum completion time MinTi for all CI conversion tasks based on the number of parts N and the total size weight under CI;

[0109] (10) Sort all CI conversion tasks in ascending order to form queue L;

[0110] (11) Iterate through all CI transformation tasks;

[0111] (12) Select the conversion tool server with the lowest current usage rate;

[0112] (13) Calculate the average completion time ACT and standard deviation SD of all CI conversion tasks based on the minimum completion time MinTi:

[0113]

[0114] Where n represents the total number of CI conversion tasks, and i is the current CI conversion task;

[0115] (14) If ACT < SD, it means that the lengths of all tasks in queue L are within a small range, so the next task is selected and assigned in order from the head of the queue; otherwise, the next task is selected and assigned in order from the tail of the queue.

[0116] (15) Remove the task assigned in (6) from queue L;

[0117] (16) If there are still tasks in queue L, return to (4) until there are no more tasks in queue L, then end the traversal.

[0118] In this embodiment, for steps S7 and S10, after the current task scheduling or callback times out, the lightweight conversion server is directly notified of the task timeout. By adding a cluster circuit breaker mechanism, when the current conversion tool server times out or encounters an error, the scheduling weight of the conversion tool server is dynamically reduced until it reaches zero. The circuit breaker node is recorded, and a trial task is sent at certain intervals. If no timeout occurs, the scheduling weight of the conversion tool server is increased or decreased until it is restored to the initial weight.

[0119] The above description is merely a detailed description of specific embodiments of the present invention. Any unspecified portions are conventional techniques. However, the scope of the present invention is not limited thereto. Any changes or substitutions that can be readily conceived by a person skilled in the art within the technical scope disclosed in the present invention are intended to be encompassed within the scope of the present invention. The scope of the present invention shall be determined by the scope of the claims.

Claims

1. A lightweight model construction and state control method in a PDM system, characterized in that, Includes the following steps: Step S1: Initiate a lightweight manual or scheduled automatic conversion task for the digital model from the PDM system according to the conversion rules; Step S2: Persist the lightweight transformation task to the database; Step S3: Verify whether the lightweight conversion task scheduling is reasonable according to the unified data access control policy; Step S4: Check if the lightweight conversion task is a scheduled task. If it is a scheduled task, send a task message to the message queue after it is triggered at the scheduled time. Otherwise, send a message to the message queue immediately. Step S5: The lightweight transformation server receives the transformation request task message sent asynchronously from the message queue, parses the request task message, and splits the task into multiple subtasks according to CI configuration items as the basic unit. Each subtask calls the lightweight transformation tool to initiate the transformation. Step S6: Download the original digital model according to the original digital model address; Step S7: The conversion tool server calls the lightweight conversion tool via command line, passes lightweight conversion data with CI configuration items as the basic unit to the lightweight conversion tool, and appends the corresponding request according to the lightweight conversion completion result; the conversion tool server periodically reports the heartbeat status to the lightweight conversion server to realize the status monitoring of the conversion tool server; Step S8: The conversion tool server creates a JSON file in a predefined format at the address of the original digital model. The conversion tool server periodically scans and parses the data in the JSON file according to the corresponding scanning configuration for subsequent processing. Step S9: Generate a lightweight model file and upload it to the file repository, and insert the JSON file scan parsing result message into the message queue; Step S10: The lightweight conversion server receives the conversion result message sent asynchronously by the message queue, parses the result message, writes the conversion result into the lightweight soft attribute table, and stores it back into the PDM system; Step S11: Implement unified management and control of the lightweight digital model on the BOM side.

2. The lightweight model construction and state control method in the PDM system according to claim 1, characterized in that, In step 1, a lightweight manual or scheduled automatic conversion task for the digital model is initiated from the PDM system. The rules for manually initiating a conversion task for a specified time period from the PDM system are as follows: (1) The lightweight model of CI node does not need to be converted separately. It can directly initiate the conversion of its associated DSI through validity. Users can choose the conversion format and check multiple default precisions, or input the precision. The lightweight conversion task of the DSI node corresponding to the current CI node is persisted to the database. (2) When converting nodes above CI, the user inputs the validity filter PBS structure, selects the conversion format, conversion precision, validity and conversion method: persists the lightweight conversion tasks corresponding to all DSI nodes within the selected node context to the database; (3) Low-order lightweight model conversion rules: Low-order lightweight models are generated from high-order lightweight models, that is, new low-order lightweight models are generated by converting existing high-order lightweight models. (4) Conversion rules for the converted lightweight model Rule 1: If the components under DSI are changed, it is permissible to repeatedly initiate a lightweight conversion with existing accuracy; Rule 2: Components under DSI that are in an unreleased state are not allowed to initiate lightweight conversion; Rule 3: Within the same sortie interval, the same version of the lightweight model with the same precision within the same sortie interval cannot be manually triggered; The rules for automatically initiating a conversion model from the PDM system for a specified time period are as follows: (1) Use the database transaction log to capture the rows that have been changed in the current time period, and directly use the parts filtered out in the transaction log as the parts numbers modified within the specified time period; (2) Based on the specified time period, modify the set of components associated with the model and recursively search upwards according to the component structure relationship to obtain the set of CI nodes of the components associated with the model modified within the specified time period; if an obsolete or terminated parent node is found during the upward search for CI, and its parent is found to be valid and using the current version of the child component, continue to recursively search upwards until the CI level, and all recursively searched nodes are not obsolete or terminated; filter according to the found CI list, if a CI node is not within the range of models for incremental synchronous conversion, exclude it from the range of incremental synchronous conversion; if a CI item in the CI list is duplicated with a CI item in the top-level structure manually initiated by the user, exclude it from the range of incremental synchronous conversion; if a CI item in the CI list is duplicated, deduplication is performed; after the data is excluded, include all incremental lightweight conversion CIs of the same model into the same lightweight conversion request for lightweight conversion processing. (3) Traverse the CI nodes in the CI list one by one: Starting from each CI node level, find the DSI node from the CI node, and traverse the components layer by layer based on the EPM object structure associated with the DSI node to obtain the original digital model; if the DSI is not associated with an EPM object, skip it; if the EPM object status of the component node is obsolete or terminated, obtain the previous valid version. For CIs that are manually or automatically initiated from the PDM system for a specified time period, it is necessary to traverse the child nodes to ensure that all components are in an undetected state. Otherwise, the CI data in the undetected state will be recorded in the conversion log and the conversion will be re-initiated during the next incremental synchronization.

3. The lightweight model construction and state control method in the PDM system according to claim 1, characterized in that, In step 5, the parameters for calling the conversion tool include the address of the original digital model, the unique identifier of the conversion instruction, the organizational relationship file of the original digital model, the conversion format, the conversion precision, and whether it is a top-level file.

4. The lightweight model construction and state control method in the PDM system according to claim 1, characterized in that, In step 10, the information in the lightweight soft attribute table includes: component ID, validity, failure time, CSV file address link, lightweight model file address link, precision value, and conversion format; the code and name identifier of the lightweight model are automatically generated by the lightweight conversion server. In addition to being related to the code of the associated component object, the generation rules require the addition of a serial number.

5. The lightweight model construction and state control method in the PDM system according to claim 1, characterized in that, In step 11, the unified management and control of the lightweight digital model is implemented on the BOM side, including lightweight model version management. Lightweight model version management rules: 1) The lightweight model and DSI major versions are kept consistent: When DSI changes to a major version, the lightweight model initiates a conversion and keeps synchronized with the new DSI version; 2) Upgrade DSI to a smaller version, and the lightweight model initiates a conversion to the default precision and upgrades the lightweight model to a smaller version; 3) Each successful conversion of a DSI minor version generates a lightweight model minor version, and the converted lightweight model minor version corresponds to the current DSI minor version.

6. The lightweight model construction and state control method in the PDM system according to claim 1, characterized in that, In step S5, when the request task field needs to be expanded, an abstract interface is designed, and a data object class is instantiated from the configuration using reflection mechanism. The object is dynamically called to reduce code refactoring and provide the function of verifying the consistency of the data object.

7. The lightweight model construction and state control method in the PDM system according to claim 1, characterized in that, Step S6: Using model library management, when the lightweight conversion server initiates a general scheduling task, it downloads all task-related original digital models in a unified manner and caches the relevant task original digital models by establishing a shared disk.

8. The lightweight model construction and state control method in the PDM system according to claim 1, characterized in that, Step S7: Deploy multiple instances of the conversion tool server and use scheduling weights to achieve load balancing. The specific load balancing algorithm is as follows: (1) Calculate the minimum completion time MinTi for all CI conversion tasks based on the number of parts N and the total size weight under CI; (2) Sort all CI conversion tasks in ascending order to form queue L; (3) Traverse all CI transformation tasks; (4) Select the conversion tool server with the lowest current usage rate; (5) Calculate the average completion time ACT and standard deviation SD of all CI conversion tasks based on the minimum completion time MinTi: Where n represents the total number of CI conversion tasks, and i is the current CI conversion task; (6) If ACT < SD, it means that the lengths of all tasks in queue L are within a small range, so the next task is selected and assigned in order from the head of the queue; otherwise, the next task is selected and assigned in order from the tail of the queue. (7) Remove the task assigned in (6) from queue L; (8) If there are still tasks in queue L, return to (4) until there are no tasks in queue L. End the traversal.

9. The lightweight model construction and state control method in the PDM system according to claim 1, characterized in that, For steps S7 and S10, after the current task scheduling or callback times out, the lightweight conversion server is directly notified of the task timeout. By adding a cluster circuit breaker mechanism, when the current conversion tool server times out or encounters an error, the scheduling weight of the conversion tool server is dynamically reduced until it reaches zero. The circuit breaker node is recorded, and a trial task is sent at certain intervals. If no timeout occurs, the scheduling weight of the conversion tool server is increased or decreased until it is restored to the initial weight.

Images