PLM platform three-dimensional design verification method and system based on three-dimensional labeling

Abstract

The invention discloses a PLM platform three-dimensional design verification method and system based on three-dimensional labeling, and the method comprises the steps: constructing a verification package data directory structure tree according to a stage-floor-professional directory, and building a verification task template according to different task roles and verification equipment types; selecting a review task template according to a system role and content to be pushed; obtaining a three-dimensional model associated with the verification task, and ensuring that the model and contained three-dimensional labels can be correctly loaded and displayed; performing problem position marking on the three-dimensional model view of the current visual angle, and binding a calibration task to form a calibration problem; acquiring a model object associated with a checking question, and accurately positioning the position of the question under the condition that the three-dimensional model and the three-dimensional label are displayed at the same time; and triggering the monitor according to the time node in the whole life cycle of the verification package to generate a verification record. Three-dimensional labels and three-dimensional digital models can be checked in real time, frequent image cutting and changing of various images are avoided, and the purposes of image-free design and image-free construction are achieved.

Description

Technical Field

[0001] The present invention belongs to the technical field of building structure BIM design, and particularly relates to a three-dimensional design review method and system based on three-dimensional annotation for a PLM platform. Background Art

[0002] The application of Building Information Modeling (BIM) technology in various stages of the building industry, such as design, construction, planning, and operation and maintenance, is becoming more and more extensive. Especially in the planning, design, and construction drawing stages, it is necessary to conduct online reviews and audits of three-dimensional models to ensure that engineering data is accurate and meets design requirements.

[0003] With the development of BIM technology, such as the use of PLM (Product Lifecycle Management), some users choose to use online display of three-dimensional lightweight models for annotation to achieve drawing model review and collaborative work. This real-time two-dimensional and three-dimensional linkage online drawing annotation review work mainly focuses on verifying the consistency between the three-dimensional model and the two-dimensional drawing, and using the three-dimensional model to check the rationality of the three-dimensional space design of pipelines, stairs, etc. in the two-dimensional drawing. In this working mode, the three-dimensional model is still a supplement to the two-dimensional drawing, and a true three-dimensional model-based review has not been achieved.

[0004] Therefore, there is an urgent need for a set of review closed-loop processes for model approval, modification, feedback, and confirmation to achieve digital review based on three-dimensional models and three-dimensional annotations, making the three-dimensional digital model the only basis in the production and manufacturing process, changing the traditional manufacturing method that mainly relies on engineering drawings and supplemented by three-dimensional digital models, and achieving the goal of design without drawings and construction without drawings. Summary of the Invention

[0005] The technical problem to be solved by the present invention is: to provide a three-dimensional design review method and system based on three-dimensional annotation for a PLM platform, which is used to achieve digital review based on three-dimensional models and three-dimensional annotations. Make the three-dimensional digital model the only basis in the production and manufacturing process, change the traditional manufacturing method that mainly relies on engineering drawings and supplemented by three-dimensional digital models, and achieve the goal of design without drawings and construction without drawings.

[0006] The technical solution adopted by the present invention is as follows: A three-dimensional design review method based on three-dimensional annotation for a PLM platform, comprising the following steps: S10: Construct a review package data directory structure tree according to the stage - floor - specialty directory, and configure the environmental part node attributes and review part node attributes in each node position of the directory structure; S20: Combine the data directory structure tree to construct a review data push link, and establish a review task template according to different task roles and review device types; S30: Select a proofreading task template according to the system role and content to be pushed, define the specific task content, and set the task information sending rule structure including the corresponding task completion time and proofreading permission conditions. Form a proofreading task with the task content according to the task information sending rule structure and send it to the message server; S40: Obtain the 3D model associated with the proofreading task to ensure that the model and the included 3D annotations can be correctly loaded and displayed; Mark the problem location in the 3D model view of the current perspective, form a block with the leader line, model, 3D annotation, and problem text description, record the perspective of the current block and generate a slide file, link the block, problem description, path information, and problem positioning point, bind the proofreading task to form a proofreading problem, and store it in the problem list under the current directory structure tree node; S50: Obtain the model object associated with the proofreading problem, reproduce the problem location by activating the slide perspective, and accurately locate the problem location when the 3D model and 3D annotations are displayed simultaneously; S60: Check and update the problem location, and update the proofreading package; Trigger a monitor according to the time node during the entire life cycle of the proofreading package to generate a proofreading record.

[0007] In the above technical solution, in step S10, the proofreading package data directory structure tree includes: Proofreading package name: As the outermost container, it contains all the elements required for the entire proofreading; Proofreading document node: As the second-layer element, it stores specific proofreading documents or proofreading content, and is set to be associated with multiple specific proofreading document model instances. Each proofreading document model instance is associated with different attributes, including: proofreading document number, identification information, used to identify different proofreading objects; Environmental part node: As the second-layer element, it stores environmental part instances related to the proofreading package. The associated attributes include: environmental part number, environmental parameters, specification requirements, background information, number.

[0008] In the above technical solution, in step S10, the attributes of the environmental part node and the proofreading document node in the proofreading package data directory structure tree are associated and configured according to the node hierarchy.

[0009] In the above technical solution, in step S20, the constructed proofreading task template needs to be adapted to at least different terminal platforms such as the desktop, mobile applications, and embedded pages.

[0010] The proofreader views the proofreading task template, opens the proofreading work package associated with the proofreading task, switches different annotation views, conducts proofreading through the approval tool, determines the problem positioning point, and forms a proofreading record.

[0011] In the above technical solution, in step S20, the review task template includes the AUDTemplate table, the AUDTemplateDetail table, and the AUDTmpDetailMap table; Among them, the AUDTemplate table is used to configure the basic content of the review task template, including ID, task name, task type, task life cycle, status, start date, due date, task submitter, and whether to configure the attachment document information link; The AUDTemplateDetail table is used to configure the content to be presented by the template, including the 3D model name, 3D annotation, design specification, review annotation, review opinion, problem location picture, and review record text data to be presented in the scenario; and is used to associate and bind the task template and the scenario details link; Bind the content and view to be presented by the task template according to different data types and attributes of the 3D annotation.

[0012] In the above technical solution, in step S20, the task information sending rule structure includes: The rule table is used to configure the entry of the task sending rule. Among them, two associated attributes are set. The tmpId attribute is the id attribute associated with the attachment document information; the ruleName attribute is the name displayed by the sending rule for display in the push console; The target table is used to configure the target types to be pushed, which are divided into roles, users, and groups; The sending condition table configures the review level and review permissions of each role. The associated attributes include: permission level, start time, task submitter, and task status; The target association relationship table is used to configure the target roles in the sending rule, and the configured attributes include role id, user id, or group id; When the user logs in on various terminal devices, according to the role permissions of the logged-in user, the corresponding review tasks are received based on different roles. Completing the review task triggers the binding mechanism to generate review information and form a review record.

[0013] In the above technical solution, in step S50, the process of accurately positioning the problem location is as follows: Parse the review problem location information based on the path information, including coordinates and viewing direction; Use the geometric data of the 3D model and the 3D annotation information to convert the problem location coordinates to the global coordinate system of the model through spatial calculation; In the model view, mark the specific location of the problem according to the calculated global coordinates, and make the problem location clearly visible by adjusting the view angle.

[0014] In the above technical solution, the review work package includes at least a review model, 3D annotations related to the review model, and a reference model.

[0015] In the above technical solution, in step S30, multiple review tasks are gathered in the message server to form a review task list. The configuration attributes of the review task list include: all review tasks to be reviewed by the current reviewer, the life cycle of the review task, the status of the review task, the initiation date of the review task, the expiration date of the review task, the task submitter, and the attachment document information; and the task is set to be filtered according to the attributes.

[0016] In the above technical solution, submitting a review work package forms an association with the review task, and multiple review tasks form a review task list.

[0017] In the above technical solution, the review task is set to be withdrawn and / or deleted by the submitting party for review.

[0018] In the above technical solution, by viewing the review task list, the review work package associated with the review task is opened.

[0019] In the above technical solution, all review tasks to be reviewed by the current reviewer, the life cycle, status, initiation date, expiration date, task submitter, and attachment document information of the task are presented in the review task list and can be filtered.

[0020] In the above technical solution, operations such as opening, approval confirmation, attachment download, and viewing review records are set based on each review task setting model.

[0021] In the above technical solution, after opening the review work package, different 3D annotation views can be switched and displayed through commands, and review can be carried out while the 3D model and 3D annotations are displayed simultaneously.

[0022] In the above technical solution, the text opinions on the problem descriptions of the review are collected to form a review problem list.

[0023] In the above technical solution, when annotating a problem, a lead line, a model, 3D annotations, and the problem text description are combined to form a block to form a picture, the perspective of the current block is recorded, and the block is linked to the problem description in the review problem list; clicking on the problem description to view the current problem picture; selecting the problem and right-clicking to locate the model, and the current model directly switches to the recorded viewpoint position.

[0024] In the above technical solution, upgrade the version of the rejected 3D model, make modifications based on the upgraded 3D model, and synchronously and automatically update the 3D annotations and / or add new 3D annotations.

[0025] In the above technical solution, it is set to upgrade the version of the entire 3D model or individual components as needed, and the upgraded version and the original version model are set to have a link relationship to facilitate historical data traceability.

[0026] In the above technical solution, the review process of each review task forms a review record table associated with the task, including the review model of the current task, the task proposer, the review links of the task, the questions and screenshots raised in each round of review, and the processing history of each question.

[0027] A computer-readable storage medium stores a computer program that can be executed by a computer processor, and the computer program executes the above-mentioned three-dimensional design review method of a PLM platform based on three-dimensional annotation.

[0028] A three-dimensional design review system for a PLM platform based on three-dimensional annotation, the system comprising a processor and a memory, the memory storing computer instructions, the processor being used to execute the computer instructions stored in the memory, and when the computer instructions are executed by the processor, the system implements the steps of the above-mentioned three-dimensional design review method for a PLM platform based on three-dimensional annotation.

[0029] Compared with the prior art, the beneficial effects of the present invention are: 1. The present invention realizes that the review work package includes the review model and the review reference model, realizes a review operation mode of seamless collaboration among multiple disciplines, breaks the limitations of information isolation and poor communication in traditional single-discipline review, and improves the overall efficiency, accuracy and decision-making quality of the review work.

[0030] 2. Reviewers will be able to annotate 3D models based on 3D annotations, without having to rely on traditional measurement tools or manually flipping through model attribute tables to obtain necessary design parameters and detailed information. They can quickly identify and understand every detail in the model directly in a 3D environment through intuitive visual guidance, whether it is a small dimensional deviation or a complex assembly relationship, it can be seen at a glance. This intuitive and accurate review method greatly reduces errors and omissions caused by poor information transmission or misunderstanding, and further improves the quality and reliability of review work.

[0031] 3. During the review process, each link has a clear person in charge and reviewer. Traceable review information makes it possible to trace responsibilities and helps maintain the authenticity and integrity of information. When problems such as information errors or leaks occur, the relevant person in charge and reviewer can be quickly traced back, and appropriate measures can be taken to remedy the situation and reduce losses.

[0032] 4. 3D review is performed based on the combination of 3D annotation and 3D digital model, which truly makes the 3D depth model the only basis in the production and manufacturing process. 2D engineering drawings are no longer needed, which changes the traditional review and manufacturing method that mainly relies on engineering drawings and supplemented by 3D digital models, and achieves the goal of designing and building without drawings.

[0033] 5. Implement the animation of the problem location tile and the calibration in combination with text on the 3D model, and realize the problem tracking and the stereoscopic reproduction of the same perspective screen based on the PLM system platform. The direct line reproduction positioning from the problem to the problem location enables the review personnel and the design modification personnel to work on the drawing review and modification on the same screen, avoiding the frequent adjustment and switching of the model perspective to find the problem points, thus improving the drawing modification and review efficiency.

[0034] 6. Configure the multi-role linkage through the review task data structure and the directory structure tree to realize that multiple version updates are all bound to the review problems and tasks, and the changes and historical records of the 3D model in each stage can be traced and queried. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The present invention will be further described below in conjunction with the drawings and embodiments. In the drawings: Figure 1 is the flowchart of the 3D design review method based on the 3D annotation PLM platform in Embodiment 1 of the present invention.

[0036] Figure 2 is the schematic diagram of the review process creation in Embodiment 2 of the present invention.

[0037] Figure 3 is the schematic diagram of automatically building the review filing directory according to the 3D model structure in Embodiment 2 of the present invention.

[0038] Figure 4 is the schematic diagram of the review work package structure at the design end in Embodiment 2 of the present invention.

[0039] Figure 5 is the schematic diagram of the list of all review historical tasks of the review personnel in Embodiment 2 of the present invention.

[0040] Figure 6 is the schematic diagram of the 3D annotation view switching in the review environment in Embodiment 2 of the present invention.

[0041] Figure 7 is the schematic diagram of the result of forming the review information on the basis of the 3D annotation in Embodiment 2 of the present invention.

[0042] Figure 8 is the schematic diagram of positioning the problem during the review in Embodiment 2 of the present invention (the blue mark is the problem location positioning point slide mark).

[0043] Figure 9 is to track Figure 8 the schematic diagram of the reproduced problem point of the positioned problem.

[0044] Figure 10 is the schematic diagram of viewing the problem list in Embodiment 2 of the present invention (picture mark).

[0045] Figure 11Schematic diagram of the upgraded version of the review model in Embodiment 2 of the present invention.

[0046] Figure 12 It shows the association and switching view of different version data after the model upgrade in Embodiment 2 of the present invention.

[0047] Figure 13 Schematic diagram of the automatic filing directory in Embodiment 2 of the present invention.

[0048] Figure 14 Schematic diagram of the review record in Embodiment 2 of the present invention.

[0049] Figure 15 Schematic diagram of the review problem list and the problem handling history record in Embodiment 2 of the present invention. Detailed implementation manners

[0050] In order to make the objectives, technical solutions and advantages of the present invention more clear and understandable, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0051] Embodiment 1 As Figure 1 shown, the 3D design review method of the PLM platform based on 3D annotation of the present invention includes the following steps: S1: Create a review process at the project manager port, define the review levels for each specialty and the review personnel for each link; S2: Build a review filing directory at the project manager port; S3: Create a 3D model review work package at the designer port and submit it for review; S4: The reviewer port views the review task list, opens the review work package associated with the review task, switches different annotation views, and conducts reviews through the approval tool; S5: The reviewer port determines whether there are errors in the review model. If so, gives the approval opinion as not passed, rejects the review task, and at the same time sends the problem list formed during the review process to the designer port; S6: After receiving the rejection information, the designer port opens the 3D model to upgrade its version, and modifies it based on the upgraded 3D model, synchronously automatically updates the 3D annotation or adds new 3D annotation; S7: After the designer port finishes modifying the model according to the review opinions, submit it for review again; S8: After the reviewer port determines that there are no errors, it automatically transfers to the next round of review and continues to execute the above steps; S9: When all reviewer ports approve, the review ends, the 3D model and 3D annotation are promoted to the release state, and the review process and data are archived.

[0052] Preferably, in step S1, at the initial stage of the project, the project manager determines the review level, such as secondary review or tertiary review, etc., and determines the review process in combination with the review level and reviewers, so as to avoid the artificial selection by designers during the review process.

[0053] Preferably, in step S2, the review filing directory is automatically generated according to the three-dimensional model structure, and the directory is subdivided into stage - floor - specialty. When the three-dimensional model structure organization changes, the filing directory can be synchronously adjusted with one key.

[0054] Preferably, in step S3, the review work package includes a review model, three-dimensional annotations related to the review model, and a reference model.

[0055] Preferably, in step S3, after the designer submits the review, the review can be withdrawn, and the designer can delete the review task after withdrawal as needed.

[0056] Preferably, in step S4, the program can automatically collect review information, present information such as all review tasks of the current reviewer, the life cycle, status, initiation date, expiration date, task submitter, attachment documents, etc. of the tasks in the review task list, and can perform filtering. At the same time, based on each task, operations such as model opening, approval confirmation, attachment download, and viewing review records are supported.

[0057] Preferably, in step S4, after opening the review work package, different three-dimensional annotation views can be switched by commands to realize the review under the condition that the three-dimensional model and three-dimensional annotations are displayed simultaneously.

[0058] Since the review has always been based on the three-dimensional model, compared with the existing lightweight technology, it is more intuitive and effective. At the same time, since it is all realized through the PLM platform, there is no need to consider the traffic lag of the existing Web - end review and the lag of complex model diagrams.

[0059] Preferably, in step S4, the program can automatically fill the review opinions into the review problem form.

[0060] Preferably, in step S4, when annotating problems, the program automatically forms a block diagram with the leader line, model, three-dimensional annotation, and problem text description to form a picture, records the perspective of the current block diagram, and links the block diagram with the problem description in the review problem form; clicking on the problem description can view the current problem picture; selecting the problem and right - clicking on the model for positioning, the current model can directly switch to the recorded viewpoint position.

[0061] Preferably, in step S6, the designer can upgrade the entire model or individual components as needed, and there is still a link relationship between the upgraded version and the original version model, which is convenient for historical data traceability.

[0062] During the review process, when reviewers check and designers modify 3D annotations to ensure the accuracy, integrity, and standardization of the annotations, the following steps are taken: Check 3D annotations: Open the model and annotations: Reviewers open the model file containing 3D annotations in the pLM system to ensure that the model annotations can be correctly loaded and displayed.

[0063] Browse annotation content: Use the browsing function of the system to view the annotation text of each component on the 3D model. Check whether the annotations completely and accurately express the relevant information of the components, such as component codes, specifications, dimensions, elevations, etc.

[0064] Check annotation relevance: Check whether the association between the annotations and the components is correct. For example, when selecting a component, check whether its corresponding annotation is highlighted or selected to confirm the relevance between the annotation and the component.

[0065] Check annotation styles: Check whether the styles of the annotations meet the design requirements and relevant standards. Check whether the font, size, color of the text, the style and position of the annotation lines, and the overall layout of the annotations are standardized.

[0066] Modify 3D annotations: Edit annotation content: If errors are found in the annotation content or updates are needed, the annotation text can be directly edited in the pLM system. Locate the annotation to be modified and make corrections or supplements in the text editing box. If the annotation content is associated with the model data, the annotation content should be automatically updated after modifying the model data.

[0067] Adjust annotation styles: Adjust the annotation styles as needed. Select the corresponding annotation style in the annotation style library for modification. After the modification is completed, apply the new style to the corresponding annotations.

[0068] Modify annotation planes: If the position or direction of the annotation plane is not reasonable enough to affect the clarity and readability of the annotations, the annotation plane can be reset. Select the annotation plane to be adjusted and make it reach the appropriate position and direction through operations such as moving and rotating.

[0069] Add or delete annotations: If there is missing annotation information, new annotations need to be added. Conversely, if some annotations are no longer needed, they can be deleted. When adding new annotations, follow the system's annotation process to select the corresponding components, annotation content, and styles for creation.

[0070] Save modifications: During the review process, whenever a modification is completed, save the changes to the annotations in a timely manner to ensure that the modified annotation information is not lost.

[0071] Submit review comments: Organize the problems and modification suggestions found during the review process into a document and submit them to relevant personnel through the review function of the pLM system. The submitted content includes marked error descriptions, modification suggestions, and screenshots of the modified markings, etc., so that designers or marking production personnel can make corresponding adjustments and optimizations.

[0072] The present invention not only uses the common methods of marking problems and recording the problem locations and status information in the existing review technologies, but also focuses on the marking and feedback of review problems through three-dimensional marking and problem viewpoint recording.

[0073] For example, after receiving the rejection information, the designer can view the problem list and locate the model associated with the problem. According to the problem description, upgrade the version of the entire model or individual components as needed. The designer makes modifications or supplements on the upgraded model, and at the same time automatically updates the three-dimensional markings or adds new three-dimensional markings.

[0074] At the same time, there is still a link relationship between the upgraded version and the original version model of the present invention. At the same time, through the archiving function, an index association is established with the three-dimensional review results to realize version management and automatic regulation, which is convenient for historical data traceability. It is completely different from the simple version management technology that realizes the association between two-dimensional drawings and three-dimensional models through coding and databases in the existing technology.

[0075] Preferably, in step S9, the program automatically archives the review task into the review structure built in S2. The project manager can click on the review task to view the review record form, view the review model of the current task, the task proposer, each link of the review of the task, the problems and screenshots raised in each round of review, and the processing history record of each problem.

[0076] Certainly, for the convenience of operation, the present invention can integrate the above method into a computer memory, which stores a computer program executable by a computer processor. The computer program executes a three-dimensional design review method based on three-dimensional marking on a PLM platform.

[0077] Alternatively, for the convenience of operation, the present invention can integrate the above method into a three-dimensional design review system based on three-dimensional marking on a PLM platform (such as an electronic device, a smart phone, a large screen display). The system includes a processor and a memory. The memory stores computer instructions. The processor is used to execute the computer instructions stored in the memory. When the computer instructions are executed by the processor, the system implements the steps of a three-dimensional design review method based on three-dimensional marking on a PLM platform.

[0078] Embodiment 2 See Figure 1 , the embodiments of the present invention include the following steps: At the initial stage of the project, such as Figure 2As shown, the project manager selects the review level for each review specialty according to the actual situation of the project. If the process selects the third-level review, the project manager then selects the reviewers for each link. Finally, the review process for this specialty can be determined by combining the review level and the reviewers.

[0079] The project manager clicks to automatically build the review filing directory based on the 3D model structure. As Figure 3 shown, the directory structure tree is constructed according to phase - floor - specialty. When the 3D model structure organization changes, different nodes of the directory structure tree can be clicked to update the command to synchronously adjust the filing directory.

[0080] Construct the review package data structure tree, and create a 3D model review work package based on the set data structure tree. As Figure 4 shown, the review work package contains the review model and the environmental model for reference, and is distinguished by the model name. After the review work package is created, it can be submitted for review.

[0081] The structure of the review package data structure tree is constructed as follows: Review package name: As the outermost container, it contains all the elements required for the entire review. Review package name: Specify the basic information of the project, phase, etc. of the review package, such as "XX Project _ Detailed Design Phase _ Structural Specialty _ Structural Column Review 20240619 To Be Reviewed A.1".

[0082] Review item node: As the second-level element, it stores the specific review documents or review contents, and is set to be associated with multiple specific review item instances. Each review item instance is associated with different attributes, including: review item number, identification information, used to identify different review objects. Such as review item 1, review item 2, review item 3, non-review: such as "A - Rectangular Column - Straight.1", etc.

[0083] Review item number: Assign a unique number to each review item for easy tracking and management, such as the number corresponding to "A - Rectangular Column - Straight.1", etc.

[0084] Environmental item node: As the second-level element, it stores the environmental item instances related to the review. The associated attributes include: environmental item number, environmental parameters, specification requirements, or background information, etc., and there are also corresponding number and other information to assist in the development of the review work. Such as environmental item 1, environmental item 2.

[0085] Environmental item number: Assign a unique number to the environmental item, such as "Environmental Item 1(A.1)", etc., for easy association and search.

[0086] Build a data push link for proofreading and auditing, and establish corresponding proofreading and auditing data templates according to different task roles and proofreading and auditing device types. Among them, the built proofreading and auditing data templates need to be adapted to at least different terminal platforms such as desktop applications, mobile applications, and embedded pages (large screen displays); the proofreading and auditing data templates include AUDTemplate table, AUDTemplateDetail table, and AUDTmpDetailMap table; Among them, the AUDTemplate table is used to configure the basic content of the proofreading and auditing data template, including ID, template name, template type, and whether to configure the scenario details link; The AUDTemplateDetail table is used to configure the content that needs to be presented in the data template, including the 3D model name, 3D annotation, design specification, proofreading annotation, proofreading opinion, problem location picture, and proofreading record text data that need to be presented in the scenario; and it is used to configure the association and binding relationship between the scenario template and the scenario details link; according to the definition of different data types of the 3D annotation, bind the content that needs to be presented in the data template. For example, for the plane annotation type, present the plane content, while for the three-dimensional annotation type, present the 3D axonometric view and rotation view; Select a proofreading and auditing task template according to the role object and content to be pushed, define the specific push content, and set push rules including the corresponding push time and push conditions (audit permission conditions). Build a proofreading and auditing task template for the push content according to the relevant push rules and send it to the message server; The push rule structure includes: The rule table is used to configure the entry of the push rule. Among them, two associated attributes are set. The tmpId attribute is the id attribute associated with the scenario template; the ruleName attribute is the name displayed by the push rule, which is used to display in the push console; The target table is used to configure the target types that need to be pushed, which are divided into roles, users, and groups; The push condition table configures the proofreading and auditing level and proofreading and auditing permissions of each role. The associated attributes include: status, start date, task submitter, status; The target association relationship table is used to configure the push target personnel in the push rule. The configured attributes include role id, user id, or group id; When the user logs in on various terminal devices, according to the role permissions of the logged-in user and the corresponding topics received by different roles, receive the corresponding information pushed by the server side and form a proofreading and auditing record.

[0087] The proofreading and auditing personnel view the proofreading and auditing task template, open the proofreading and auditing work package associated with the proofreading and auditing task, switch different annotation views, conduct proofreading and auditing through the approval tool, determine the problem location points, and form a proofreading and auditing record.

[0088] The reviewer logs in to the platform. As shown in Figure 5 , the reviewer can view the list of review tasks presented by the review task template, filter out the tasks that need to be reviewed currently through options such as status, initiation date, task submitter, etc., and open the review work package model.

[0089] As shown in Figure 6 , the reviewer can switch the display to different 3D annotation views through commands to conduct reviews while the 3D model and 3D annotations are displayed simultaneously.

[0090] The review results are as shown in Figure 7 .

[0091] When the designer modifies the model again, the detailed steps for problem tracking and adjustment based on the 3D review problem positioning points are as follows. Refer to Figure 8 and Figure 9 : (1) Information parsing: Annotation data reading: Extract information related to the problem from the 3D annotation record, such as the description of the problem, annotation types (such as planar annotation, solid annotation, etc.), and key data such as the viewing point direction and position of the annotation. These information are the basic basis for subsequent positioning.

[0092] (2) Model positioning Model structure analysis: Conduct a structural analysis of the 3D model associated with the 3D annotation to clarify each component, member included in it and their spatial relationships, and understand the overall layout and hierarchical structure of the model.

[0093] Member identification: Identify the specific member objects in the model according to the member characteristics or names mentioned in the 3D annotation. For example, in a building model, find specific members such as beams and columns based on the annotation.

[0094] (3) Spatial calculation Coordinate system determination: Determine the coordinate system used by the model, clarify parameters such as the origin position, coordinate axis directions, and units to ensure the accuracy of subsequent spatial positioning calculations.

[0095] Position conversion: Convert the problem position information in the 3D annotation from its local coordinate system to the global coordinate system of the model, and calculate the accurate coordinates of the problem in the global coordinate system through corresponding mathematical transformation formulas, such as translation and rotation.

[0096] (4) Viewpoint restoration Viewpoint information restoration: Use the viewpoint direction data recorded in the 3D annotation to restore the viewpoint when the reviewer viewed the problem at that time, which helps to observe the problem position more intuitively.

[0097] Viewpoint adjustment: In the model viewing list, adjust the view according to the restored viewpoint information so that the area where the problem lies is clearly displayed on the screen, facilitating further positioning and analysis.

[0098] (5) Precise positioning Component positioning: Select the previously identified associated component in the model and highlight it or make other visual distinctions to quickly focus on the component where the problem lies.

[0099] Position marking: Based on the previously calculated global coordinates, precisely mark the location where the problem occurs on the component. This can be achieved by adding marker points, marker lines, or marker regions to the model. The marking style should be prominent and easy to identify.

[0100] (6) Verification and adjustment Positioning verification: Compare the problem description in the 3D annotation and relevant screenshots and other materials, check whether the marked position is consistent with the problem position in the annotation, and verify the accuracy of the positioning.

[0101] Adjustment and optimization: If it is found that there is a deviation in the positioning, analyze the reasons according to the deviation situation. It may be due to inaccurate annotation information, incorrect understanding of the model structure, or coordinate conversion errors, etc. Make corresponding adjustments and corrections according to the reasons until the problem position is accurately located.

[0102] After that, modify the model and 3D annotation until the final completion.

[0103] The proofreader judges whether there are errors in the proofreading model. If so, give the approval opinion as not passed, reject the proofreading task, and at the same time send the problem list formed during the proofreading process to the designer; After the designer receives the rejection information, as Figure 10 shown, view the problem list and locate the model associated with the problem. According to the problem description, as Figure 11 shown, upgrade the version of the entire model or individual components as needed. The designer makes modifications or supplements on the upgraded model, and at the same time automatically updates the 3D annotation or adds new 3D annotations. As Figure 12 shown, there is still a link relationship between the upgraded version and the original version model, facilitating historical data traceability.

[0104] After the designer finishes modifying the model according to the proofreading opinions and submits it for proofreading again. In modifying the model, the design annotation update steps are as follows: I. Check the annotation (1) Initialize the check variables Define variables iCheck, iCheck1, and iCheck2 to mark the situations of failed text content acquisition, failed associated text acquisition, and failed annotation type judgment respectively, and their initial values are all 0.

[0105] (2)Traverse the annotated objects Traverse each annotated object spi3DAnnotaExt in the _vecAnnotaExt container.

[0106] For each annotated object, obtain its text pattern strText, and separate the text type strTextType and the quadrant iquadrant.

[0107] (3)Obtain the object to be annotated According to the text type of the annotated object: if it is "diagonal annotation", obtain the list of annotated objects lstAnnotation, and obtain lstCurrentOcc of the current context from it. If lstCurrentOcc is empty, skip the subsequent operations; otherwise, take its first element as the current annotated object spCurrentOcc, and assign it to spObjectFeature. For other types of annotations, directly obtain the text feature object spObjectFeature.

[0108] (4)Process non-empty objects to be annotated If spObjectFeature is not empty: Obtain the instance spOcc in the context object: If listSetObj (the list of annotated objects) is not empty, obtain lstCurrentOcc of the current context from listSetObj, and take its first element as spOcc.

[0109] If spOcc is still empty, obtain Occ through the feature or directly assign spOcc = spiCopyFeaSource (copy feature source).

[0110] If spOcc is empty, skip the subsequent operations; otherwise, obtain the alias object spiAlias, and further obtain the text content strTextContent.

[0111] (5)Obtain the annotation type and text content Call CSAAnnotationCls::GetSelectObjectType to obtain the annotation type iustrType and the type value itype.

[0112] According to iustrType and listTpsName (the list of segmented text content), call CSAAnnotationCls::GetTPSContentFromConfig to obtain listTpsContent (the list of annotation content).

[0113] Convert listTpsContent to the string iustrAnnotationContent.

[0114] Check the text content and attributes: If iustrAnnotationContent is empty, mark iCheck = 1 and skip the subsequent operations. Obtain the TPS text object piTPSText and compare its text content with iustrAnnotationContent. If they are inconsistent, set the annotation status to "modified". Obtain the attributes such as the font name, font size, character spacing, style, and view scale of the annotation object, and compare them with the corresponding attributes of the TPS text object. If they are inconsistent, set the annotation status to "modified".

[0115] (6)Process special annotation types If the annotation type is "diagonal annotation", directly obtain the TPS text object piTPSText from _vecTPS and obtain its text content.

[0116] (7)Update the annotation status Update the status of the annotation object to "modified", "normal", or "deleted" according to the inspection results.

[0117] Error prompt: According to the values of iCheck, iCheck1, and iCheck2, display the corresponding error prompts: iCheck1 == 1: Failure to obtain some associated text. Please check whether the associated text of the text has been deleted. iCheck == 1: Failure to obtain some text content. Please update manually. iCheck2 == 1: There are label annotations for which the specific type cannot be determined. Please add the characters "steel" or "concrete" in the attribute title.

[0118] II. Update annotations (1)Initialize update variables Define variables iUpdate, iUpdate1, iUpdate2, and iUpdate3 to mark the situations of failure to obtain text content, failure to obtain the annotated object for diagonal annotation, failure to obtain the copied object for annotation, and failure to obtain associated text respectively, with initial values all being 0.

[0119] Traverse the annotation objects Get the number of rows icout of the annotation list _pMainDlg->GetMultiList(), and iterate through each row.

[0120] (3)Process the annotations to be updated Get the annotation status strStateContent of the current row. If the status is "modified", perform the update operation.

[0121] (4)Get the annotation object Get the current annotation object spi3DAnnotaExt. Get its text mode strText, and separate the text type strTextType and the quadrant iquadrant.

[0122] (5)Get the associated object Get the associated component spComponOcc of the current annotation object.

[0123] (6)According to the text type of the annotation object: If it is a "diagonal annotation", get the annotation object list lstAnnotation, and get lstCurrentOcc of the current context from it. If it is empty, mark iUpdate1 = 1 and skip the subsequent operations; otherwise, take its first element as the current annotation object spCurrentOcc and assign it to spObjectFeature.

[0124] For other types of annotations, directly get the text feature object spObjectFeature.

[0125] Process non-empty associated objects; if spObjectFeature is not empty: get the instance spOcc in the context object: if listSetObj (annotation object list) is not empty, get lstCurrentOcc of the current context from listSetObj, and take its first element as spOcc. If spOcc is still empty, obtain Occ through the feature or directly assign spOcc = spiCopyFeaSource (copy feature source).

[0126] (7)Get the annotation content and attributes Obtain the text content strTextContent of the annotation object. Split the text content to obtain listTpsName. Obtain the annotation type iustrType and the type value itype. According to iustrType and listTpsName, obtain listTpsContent (the annotation content list). Convert listTpsContent to a string iustrAnnotationContent.

[0127] (8) Update the annotation content If iustrAnnotationContent is empty, mark iUpdate = 1 and skip the subsequent operations.

[0128] Obtain the TPS text object piTPSText: If the annotation type is not "diagonal annotation", obtain the associated text object spTPSDftAnnotation2 and get piTPSText from it.

[0129] If the annotation type is "diagonal annotation", directly obtain piTPSText from _vecTPS.

[0130] (9) Set the annotation content and attributes Convert iustrAnnotationContent to a wide character array ptxtChar and set it as the TPS text content. According to the annotation type (such as slant line, straight line, straight slant line, three-segment straight slant line), call the corresponding creation function (such as CSAAnnotationCls::CreateSlantTPS2, CSAAnnotationCls::CreateLineTPS2, etc.) to create a new annotation object.

[0131] (10) Set the alias of the new annotation object.

[0132] Remove the old annotation object (including the arrow, associated text, and text).

[0133] Replace the new annotation object into the _vecTPS container.

[0134] Process special annotation types (such as concrete slab): If the annotation type is concrete slab, hide the newly created annotation object. Hide the arrow. Set the text position of the concrete slab.

[0135] (11) Update the text attributes According to the annotation type, call CSAAnnotationCls::SetTPSFont to set the font attributes of the annotation text.

[0136] Refresh the text display. Update the annotation status and change the status of the annotated object to "Updated".

[0137] Error prompt: Based on the values of iUpdate, iUpdate1, iUpdate2, and iUpdate3, display the corresponding error prompts: iUpdate == 1: Part of the text content acquisition failed. Please update it manually.

[0138] iUpdate1 == 1: Part of the diagonal annotation failed to obtain the annotated object. Please update it manually.

[0139] iUpdate2 == 1: Part of the annotation failed to obtain the copied object. Please update it manually.

[0140] iUpdate3 == 1: Part of the associated text acquisition failed. Please check whether the associated text of the text has been deleted.

[0141] After the designer updates the annotation, submit it for review here.

[0142] After the reviewer confirms that there are no errors, it will automatically transfer to the next round of review and continue to execute the above steps; When all reviewers approve, the review ends, and the 3D model and 3D annotations are promoted to the released state.

[0143] The program automatically archives the review tasks to the established review archive directory, as Figure 13 shown.

[0144] The project manager can click on the review task in the review archive directory to view the review record form, as Figure 14 shown, to view information such as the review process, review model, task submitter, and each link of the task review of the current task. It also supports switching to view different versions of the model before and after the review.

[0145] Furthermore, as Figure 15 shown, the project manager can click to view the problem list for each round and the historical record of each problem from the record form. Finally, it realizes the manageability of the review model data and the traceability of the review task information.

[0146] Thus, an index association is established with the 3D review results to achieve version management and automatic regulation, facilitating the traceability of historical data. It is completely different from the simple version management technology that realizes the association between 2D drawings and 3D models through coding and databases in the existing technology.

[0147] It should be understood that the sequence numbers of the steps in the above embodiments do not indicate the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. According to the needs of implementation, each step / component described in the present application can be split into more steps / components, or two or more steps / components or partial operations of steps / components can be combined into new steps / components to achieve the purpose of the present invention.

[0148] It should be understood that those of ordinary skill in the art can make improvements or transformations according to the above description, and all such improvements and transformations should fall within the protection scope of the appended claims of the present invention.

Claims

1. A 3D design review method for a PLM platform based on 3D annotation, characterized in that The following steps are involved: S10: Construct a review package data directory structure tree according to the stage-floor-professional directory, and configure the environment component node attributes and review component node attributes in the review package at each node position of the directory structure; S20: Combine the data directory structure tree to build a review data push link, and establish a review task template according to different task roles and review device types; S30: Select a review task template according to the system role and content to be pushed, define the specific task content and set the task information sending rule structure including the corresponding task completion time and review authority conditions, generate a review task according to the task information sending rule structure and send it to the message server; S40: Acquire a 3D model associated with the review task; mark the problem location in the 3D model view of the current perspective, combine the lead line, model, 3D annotation, and problem text description into a block, record the perspective of the current block and generate a slide file, link the block, problem description, path information, and problem location point, bind the review task to generate a review problem, and store it in the problem list under the current directory structure tree node; S50: Obtaining a model object associated with the review question, reproducing the question location by activating the slide view, and accurately locating the question location when the 3D model and the 3D annotation are displayed simultaneously; S60: Check and update the problem location, and update the review package; trigger the monitor according to the time node in the whole life cycle of the review package to generate the review record.

2. The three-dimensional design review method based on three-dimensional annotation of PLM platform according to claim 1, characterized in that In step S10, the review package data directory structure tree includes: Review package name: As the outermost container, it contains all the elements required for the entire review; Review document node: as the second-level element, it stores specific review documents or review contents and is set to associate with multiple specific review document model instances. Each review document model instance is associated with different attributes, including review document number and identification information, which are used to identify different review objects. Environmental component node: As the second-level element, it stores the environmental component instances related to the review package. The associated attributes include: environmental component number, environmental parameters, specification requirements, background information, and number.

3. The three-dimensional design review method based on three-dimensional annotation on a PLM platform according to claim 1, characterized in that In step S10, the environment component node attributes and the review component node attributes in the review package data directory structure tree are associated and configured according to the node level.

4. The three-dimensional design review method based on three-dimensional annotation on a PLM platform according to claim 1, characterized in that In step S20, the constructed review task template must be adapted to at least different terminal platforms such as desktop, mobile applications and embedded pages.

5. The three-dimensional design review method based on three-dimensional annotation on a PLM platform according to claim 1, characterized in that In step S20, the review task template includes an AUDTemplate table, an AUDTemplateDetail table and an AUDTmpDetailMap table; The AUDTemplate table is used to configure the basic content of the review task template, including ID, task name, task type, task life cycle, status, initiation date, expiration date, task submitter, and whether to configure an attachment document information link; The AUDTemplateDetail table is used to configure the content that the template needs to present, including the 3D model name, 3D annotations, design specifications, review comments, review opinions, problem location pictures, and review record text data that need to be presented in the scene; and is used to link and associate the task template with the scene details; and to bind the content and views that the task template needs to present according to the different data types and attributes of the 3D annotations.

6. The three-dimensional design review method based on three-dimensional annotation on a PLM platform according to claim 1, characterized in that In step S20, the task information sending rule structure includes: The rule table is used to configure the entry of the task sending rules. Two related attributes are set. The tmpId attribute is the id attribute of the associated attachment document information; the ruleName attribute is the name displayed by the sending rule, which is used to display in the push console; The target table is used to configure the target type to be pushed, which is divided into roles, users, and groups; Sending condition table, configure the review level and review authority of each role, and the associated attributes include: authority level, initiation time, task submitter, and task status; Target association table, used to configure the target role in the sending rule. The configured attributes include role ID, user ID or group ID; When a user logs in on various terminal devices, he / she receives corresponding review tasks based on different roles according to the role permissions of the logged-in user. The completion of the review task triggers the binding mechanism to generate review information and form a review record.

7. The three-dimensional design review method based on three-dimensional annotation on a PLM platform according to claim 1, characterized in that In step S50, the process of accurately locating the problem position is as follows: based on the path information, the problem position information, including coordinates and viewpoint direction, is parsed and reviewed; using the geometric data and three-dimensional annotation information of the three-dimensional model, the problem position coordinates are converted to the global coordinate system of the model through spatial calculation; in the model view, the specific location of the problem is marked according to the calculated global coordinates, and the problem location is made clearly visible by adjusting the view angle.

8. The three-dimensional design review method based on three-dimensional annotation on a PLM platform according to claim 1, characterized in that The review work package shall at least include the review model, relevant 3D annotations of the review model and the reference model.

9. The three-dimensional design review method based on three-dimensional annotation on a PLM platform according to claim 1, characterized in that In step S30, multiple review tasks are collected in the message server to form a review task list. The review task list configuration attributes include: all tasks to be reviewed by the current reviewer, the life cycle of the review task, the review task status, the review task initiation date, the review task expiration date, the task submitter, and the attachment document information; and each task is set to be filtered based on the attributes.

10. A 3D design review system for a PLM platform based on 3D annotation, characterized in that The system includes a processor and a memory, wherein the memory stores computer instructions, and the processor is used to execute the computer instructions stored in the memory. When the computer instructions are executed by the processor, the system implements the steps of the above-mentioned three-dimensional design review method of a PLM platform based on three-dimensional annotation.

Images