Project problem report generation method and system in Revit modeling process
Through the secondary development technology of the programming language C#, RevitAPI and WPF Microsoft framework, the project problem report during the Revit modeling process is automatically generated, which solves the problem of low manual entry efficiency, realizes efficient and accurate project problem management, and improves construction The level of digitalization of the modular process.
Patent Information
- Application Number
- CN202410845560.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-06-27
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2044-06-27
AI Technical Summary
During the Revit modeling process, the method of generating project problem reports mainly relies on manual recording, which is inefficient and prone to errors, resulting in project progress delays, cost overruns and quality reduction.
Using secondary development technology based on programming languages C#, RevitAPI and WPF Microsoft framework, the development plug-in automatically obtains project engineering records, generates *.docx version problem reports, captures accident types and processing status through RevitAPI, and realizes automatic entry and location of problem reports. , reduce human error.
It improves the efficiency and accuracy of project problem reports, saves organization and entry work, realizes digital management of the modeling process, and enhances the efficiency, accuracy and reliability of the modeling process.
Smart Images

Figure CN119067089A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of secondary development based on programming language C#, Revit API and WPF Microsoft framework, and in particular to a method and system for generating a project problem report during a Revit modeling process. Background Art
[0002] With the development of science and technology, building informatization has been more and more widely used in the construction industry. As an important carrier of building informatization, Building Information Model (BIM) runs through all key links in the entire life cycle of construction projects, guiding the design, construction and operation and maintenance management of construction projects. BIM technology has been actively promoted in the construction field due to its many advantages such as visualization, coordination, simulation, plotting, and comprehensive information, which facilitates communication and coordination of problems. Revit software is a platform-level modeling software designed for BIM, with powerful three-dimensional modeling functions. It has rich functions and can meet the needs of most situations such as parametric modeling, engineering quantity statistics, and drawing drawings. However, various problems are inevitable in the modeling process, such as conflicts between drawings, inconsistent models, parameter errors, etc. If these problems are not discovered and solved in time, they will have a serious impact on the quality and progress of the project. The current method of generating project problem reports in the modeling process mostly requires manual recording, which is not only inefficient but also prone to errors.
[0003] With the increasing popularity of Building Information Modeling (BIM), Revit has become one of the most commonly used modeling software in the construction industry. However, with the continuous increase in project scale and complexity, problems in the Revit modeling process have become increasingly prominent, which may lead to negative impacts such as project schedule delays, cost overruns and reduced quality. Summary of the invention
[0004] To achieve the above objectives, this application provides the following technical solutions:
[0005] According to the first aspect of the present invention, the present invention claims a method for generating a project problem report in a Revit modeling process, which is a secondary development plug-in based on the programming language C# and the Revit API and WPF Microsoft framework, comprising:
[0006] Obtain the project engineering records corresponding to the drawings of the project to be evaluated;
[0007] Input the project engineering records into a *.docx version of the problem report template, wherein the *.docx version of the problem report template is used to generate the importance of the occurrence of at least two man-made accidents corresponding to at least one historical problem strategy for the drawings of the project to be evaluated, the *.docx version of the problem report template includes at least three problem collection RevitAPIs, the problem collection RevitAPIs are used to capture the connection between the project engineering records on different types of man-made accidents, the at least three problem collection RevitAPIs are divided into at least two different problem collection RevitAPI groups during the iteration process of the *.docx version of the problem report template, and the problem collection RevitAPI group includes at least one problem collection RevitAPI among the at least three problem collection RevitAPIs;
[0008] Output the *.docx version of the problem report output by the *.docx version of the problem report template, wherein the *.docx version of the problem report is used to indicate the importance of the drawings of the project to be evaluated to the occurrence of at least two man-made accidents corresponding to at least one historical problem strategy.
[0009] Furthermore, the step of inputting the project engineering records into a *.docx version of the problem report template includes:
[0010] Input the physical indicator metadata corresponding to the project engineering record into the at least three problem collection RevitAPIs, and output the accident handling status identifier output by the at least three problem collection RevitAPIs, wherein the physical indicator metadata is the numerical information of the project engineering record, and the accident handling status identifier is the representation of the physical indicator metadata on the different man-made accident types;
[0011] The accident handling status identifier is input into the problem strategy output layer in the *.docx version problem report template, and the *.docx version problem report is output.
[0012] Furthermore, before inputting the project engineering record into the *.docx version of the problem report template, the method further includes:
[0013] Acquire multiple accident processing projects, wherein the accident processing projects are condition information having the same condition type as the historical problem strategy;
[0014] Iterate the initial generation model using the multiple accident handling projects and the at least two different problem collection Revit API groups, and output the iterated generation model;
[0015] The iterated generation model is decided as the *.docx version of the problem report template.
[0016] Further, the initial generation model is iterated using the multiple accident handling projects and the at least two different problem collection Revit API groups, and the iterated generation model is output, including:
[0017] Repeat the following steps until the iterated generation model is output:
[0018] Determine the problematic man-made project from among the multiple accident handling projects;
[0019] Input the body index metadata corresponding to the problem artificial project into the first problem collection RevitAPI group in the current generation model, and output the first accident handling status identifier output by the first problem collection RevitAPI group, wherein the at least two different problem collection RevitAPI groups include the first problem collection RevitAPI group; and, input the body index metadata corresponding to the problem artificial project into the second problem collection RevitAPI group in the current generation model, and output the second accident handling status identifier output by the second problem collection RevitAPI group, wherein the at least two different problem collection RevitAPI groups include the second problem collection RevitAPI group;
[0020] Inputting the first accident handling status identifier into the problem strategy output layer in the current generation model, and outputting a first *.docx version of the problem report; and, inputting the second accident handling status identifier into the problem strategy output layer, and outputting a second *.docx version of the problem report;
[0021] In the case that the first *.docx version problem report and the second *.docx version problem report do not meet the discharge deadline condition, modifying the model parameters of the currently generated model, and deciding the next item from the multiple accident processing items as the problem artificial item;
[0022] When the first *.docx version problem report and the second *.docx version problem report satisfy the discharge deadline condition, the current generation model is decided as the iterated generation model.
[0023] Further, after inputting the first accident handling status identifier into the problem strategy output layer in the current generation model to output a first *.docx version of the problem report; and inputting the second accident handling status identifier into the problem strategy output layer to output a second *.docx version of the problem report, the method further includes:
[0024] Obtaining a first generation sub-scheme and a second generation sub-scheme in the first *.docx version of the problem report, and a third generation sub-scheme and a fourth generation sub-scheme in the second *.docx version of the problem report, wherein the first generation sub-scheme is used to indicate a first occurrence importance of a first man-made accident corresponding to the problem man-made item, the second generation sub-scheme is used to indicate a second occurrence importance of a second man-made accident corresponding to the problem man-made item, the third generation sub-scheme is used to indicate a third occurrence importance of the first man-made accident corresponding to the problem man-made item, the fourth generation sub-scheme is used to indicate a fourth occurrence importance of the second man-made accident corresponding to the problem man-made item, and the at least two man-made accidents include the first man-made accident and the second man-made accident;
[0025] calculating a first importance difference between the first occurrence importance and the third occurrence importance, and a second importance difference between the second occurrence importance and the fourth occurrence importance;
[0026] When the first importance difference is not greater than a first limit value, and / or the second importance difference is not greater than a second limit value, it is determined that the first *.docx version problem report and the second *.docx version problem report meet the discharge deadline condition.
[0027] Further, after inputting the first accident handling status identifier into the problem strategy output layer in the current generation model to output a first *.docx version of the problem report; and inputting the second accident handling status identifier into the problem strategy output layer to output a second *.docx version of the problem report, the method further includes:
[0028] Obtaining a first generation sub-scheme and a second generation sub-scheme in the first *.docx version of the problem report, and a third generation sub-scheme and a fourth generation sub-scheme in the second *.docx version of the problem report, wherein the first generation sub-scheme is used to indicate a first occurrence importance of a first man-made accident corresponding to the problem man-made item, the second generation sub-scheme is used to indicate a second occurrence importance of a second man-made accident corresponding to the problem man-made item, the third generation sub-scheme is used to indicate a third occurrence importance of the first man-made accident corresponding to the problem man-made item, the fourth generation sub-scheme is used to indicate a fourth occurrence importance of the second man-made accident corresponding to the problem man-made item, and the at least two man-made accidents include the first man-made accident and the second man-made accident;
[0029] Obtain the fifth occurrence importance of the first man-made accident corresponding to the first X items of the problematic man-made items, and the sixth occurrence importance of the second man-made accident corresponding to the first Y items of the problematic man-made items, where X and Y are natural numbers;
[0030] calculating a third importance difference between the first occurrence importance and the fifth occurrence importance, and a fourth importance difference between the second occurrence importance and the sixth occurrence importance;
[0031] When the third importance difference is greater than the third limit value, and / or the fourth importance difference is greater than the fourth limit value, it is determined that the first *.docx version problem report and the second *.docx version problem report meet the discharge deadline condition.
[0032] Furthermore, the modifying of the model parameters of the currently generated model and the decision of the next item from the multiple accident handling items as the problematic artificial item include at least one of the following:
[0033] Correcting a first problem ratio of the at least two different problem collection Revit API groups, wherein the model parameters include the first problem ratio;
[0034] Modifying a second problem ratio of the problem strategy output layer, wherein the model parameters include the second problem ratio.
[0035] Furthermore, before inputting the body index metadata corresponding to the problem artificial project into the first problem collection RevitAPI group in the current generation model and outputting the first accident handling status identifier output by the first problem collection RevitAPI group, the method further includes: deciding Z problem collection RevitAPIs from the at least three problem collection RevitAPIs, and closing the Z problem collection RevitAPIs, wherein Z is a natural number; combining the problem collection RevitAPIs other than the Z problem collection RevitAPIs in the at least three problem collection RevitAPIs, and outputting the first problem collection RevitAPI group;
[0036] Before inputting the body indicator metadata corresponding to the problem artificial item into the second problem collection RevitAPI group in the current generation model and outputting the second accident handling status identifier output by the second problem collection RevitAPI group, the method also includes: deciding K problem collection RevitAPIs from the at least three problem collection RevitAPIs, and closing the K problem collection RevitAPIs, where K is a natural number; combining the problem collection RevitAPIs other than the K problem collection RevitAPIs in the at least three problem collection RevitAPIs, and outputting the second problem collection RevitAPI group.
[0037] Furthermore, the method further includes: clicking on rule settings to enter a custom collision rule interface, where collision rules can be added; after selecting the collision subject and object, clicking [Save Settings] and closing the interface, the rules will be automatically saved to the system, and the set collision rules can be selected by opening a drop-down menu before collision analysis;
[0038] Select a collision rule to start the program, select Start Analysis or Quick Analysis, wait for the analysis to be completed, and the collision analysis results will be generated in a list;
[0039] Each collision result is composed of a subject and an object, the dark color is the collision subject, and the white color is the collision object;
[0040] When the progress is manually interrupted, the analyzed data will be retained;
[0041] Before viewing the collision results, you need to set the view; set the model transparency to 10% to clearly display the intersection view;
[0042] View collision results: Double-click the analysis result you want to view, and the view will automatically navigate to the cut 3D view;
[0043] Collision result coloring description: The plug-in provides a coloring method to display collision components. By default, the component display state is "color intersection" + "display coloring". The coloring method is controlled by the coloring all hidden coloring in the lower right corner.
[0044] Shading Intersections highlights the intersection of two components; Shading All highlights the two colliding components.
[0045] If you click Hide Coloring, the coloring will be canceled regardless of the current coloring state.
[0046] According to a second aspect of the present invention, the present invention claims protection for a system for generating a project problem report in a Revit modeling process, comprising:
[0047] The first acquisition module is used to acquire the project engineering records corresponding to the drawings of the project to be evaluated;
[0048] An input module, used for inputting the project engineering record into a *.docx version problem report template, wherein the *.docx version problem report template is used for generating the importance of the occurrence of at least two man-made accidents corresponding to at least one historical problem strategy for the drawings of the project to be evaluated, the *.docx version problem report template includes at least three problem collection RevitAPIs, the problem collection RevitAPIs are used to capture the connection between the project engineering record on different types of man-made accidents, the at least three problem collection RevitAPIs are divided into at least two different problem collection RevitAPI groups during the iteration process of the *.docx version problem report template, and the problem collection RevitAPI group includes at least one problem collection RevitAPI among the at least three problem collection RevitAPIs;
[0049] A generation module is used to output a *.docx version of the problem report output by the *.docx version of the problem report template, wherein the *.docx version of the problem report is used to indicate the importance of the drawings of the project to be evaluated to the occurrence of at least two man-made accidents corresponding to at least one historical problem strategy.
[0050] The present application relates to the technical field of secondary development based on programming language C#, Revit API and WPF Microsoft framework, and in particular to a method and system for generating a project problem report in the Revit modeling process, which uses programming language C#, Revit API and WPF Microsoft framework programming to realize automatic entry of problem reports, automatically captures the model problem positioning axis network and enters it by box selection, automatically obtains the record date, can recognize the name of the imported drawing in the software and automatically enter the drawing name, can take screenshots of the model problem two-dimensional and three-dimensional models with one click, associates the automatically obtained information with the *.docx version of the problem report template, can export the final *.docx version of the problem report, and realize that the screenshot is automatically centered in the table of the *.docx version of the problem report, is associated and synchronized with the *.docx version of the problem report in the editing state, and can also import the problem report after exporting the *.docx version of the problem report, saving a lot of work such as text entry, image capture, and problem report sorting in arranging project problem reports, and realizing the digital management level of BIM modeling and application. BRIEF DESCRIPTION OF THE DRAWINGS
[0051] Figure 1 A workflow diagram of a method for generating a project problem report in a Revit modeling process as claimed in an embodiment of the present application;
[0052] Figure 2This is a structural diagram of a system for generating a project problem report during a Revit modeling process as claimed in an embodiment of the present application. DETAILED DESCRIPTION
[0053] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0054] According to the first embodiment of the present invention, the present invention claims a method for generating a project problem report in the Revit modeling process, based on the secondary development plug-in of the programming language C# and the Revit API and WPF Microsoft framework, referring to Figure 1 ,include:
[0055] Obtain the project engineering records corresponding to the drawings of the project to be evaluated;
[0056] Input the project engineering records into a *.docx version of the problem report template, wherein the *.docx version of the problem report template is used to generate the importance of the occurrence of at least two man-made accidents corresponding to at least one historical problem strategy for the drawings of the project to be evaluated, the *.docx version of the problem report template includes at least three problem collection RevitAPIs, the problem collection RevitAPIs are used to capture the connection between the project engineering records on different types of man-made accidents, the at least three problem collection RevitAPIs are divided into at least two different problem collection RevitAPI groups during the iteration process of the *.docx version of the problem report template, and the problem collection RevitAPI group includes at least one problem collection RevitAPI among the at least three problem collection RevitAPIs;
[0057] Output the *.docx version of the problem report output by the *.docx version of the problem report template, wherein the *.docx version of the problem report is used to indicate the importance of the drawings of the project to be evaluated to the occurrence of at least two man-made accidents corresponding to at least one historical problem strategy.
[0058] Furthermore, the step of inputting the project engineering records into a *.docx version of the problem report template includes:
[0059] Input the physical indicator metadata corresponding to the project engineering record into the at least three problem collection RevitAPIs, and output the accident handling status identifier output by the at least three problem collection RevitAPIs, wherein the physical indicator metadata is the numerical information of the project engineering record, and the accident handling status identifier is the representation of the physical indicator metadata on the different man-made accident types;
[0060] The accident handling status identifier is input into the problem strategy output layer in the *.docx version problem report template, and the *.docx version problem report is output.
[0061] Furthermore, before inputting the project engineering record into the *.docx version of the problem report template, the method further includes:
[0062] Acquire multiple accident processing projects, wherein the accident processing projects are condition information having the same condition type as the historical problem strategy;
[0063] Iterate the initial generation model using the multiple accident handling projects and the at least two different problem collection Revit API groups, and output the iterated generation model;
[0064] The iterated generation model is decided as the *.docx version of the problem report template.
[0065] Further, the initial generation model is iterated using the multiple accident handling projects and the at least two different problem collection Revit API groups, and the iterated generation model is output, including:
[0066] Repeat the following steps until the iterative generation model is output:
[0067] Determine the problematic man-made project from among the multiple accident handling projects;
[0068] Input the body index metadata corresponding to the problem artificial project into the first problem collection RevitAPI group in the current generation model, and output the first accident handling status identifier output by the first problem collection RevitAPI group, wherein the at least two different problem collection RevitAPI groups include the first problem collection RevitAPI group; and, input the body index metadata corresponding to the problem artificial project into the second problem collection RevitAPI group in the current generation model, and output the second accident handling status identifier output by the second problem collection RevitAPI group, wherein the at least two different problem collection RevitAPI groups include the second problem collection RevitAPI group;
[0069] Inputting the first accident handling status identifier into the problem strategy output layer in the current generation model, and outputting a first *.docx version of the problem report; and, inputting the second accident handling status identifier into the problem strategy output layer, and outputting a second *.docx version of the problem report;
[0070] In the case that the first *.docx version problem report and the second *.docx version problem report do not meet the discharge deadline condition, modifying the model parameters of the currently generated model, and deciding the next item from the multiple accident processing items as the problem artificial item;
[0071] When the first *.docx version problem report and the second *.docx version problem report satisfy the discharge deadline condition, the current generation model is decided as the iterated generation model.
[0072] Further, after inputting the first accident handling status identifier into the problem strategy output layer in the current generation model to output a first *.docx version of the problem report; and inputting the second accident handling status identifier into the problem strategy output layer to output a second *.docx version of the problem report, the method further includes:
[0073] Obtaining a first generation sub-scheme and a second generation sub-scheme in the first *.docx version of the problem report, and a third generation sub-scheme and a fourth generation sub-scheme in the second *.docx version of the problem report, wherein the first generation sub-scheme is used to indicate a first occurrence importance of a first man-made accident corresponding to the problem man-made item, the second generation sub-scheme is used to indicate a second occurrence importance of a second man-made accident corresponding to the problem man-made item, the third generation sub-scheme is used to indicate a third occurrence importance of the first man-made accident corresponding to the problem man-made item, the fourth generation sub-scheme is used to indicate a fourth occurrence importance of the second man-made accident corresponding to the problem man-made item, and the at least two man-made accidents include the first man-made accident and the second man-made accident;
[0074] calculating a first importance difference between the first occurrence importance and the third occurrence importance, and a second importance difference between the second occurrence importance and the fourth occurrence importance;
[0075] When the first importance difference is not greater than a first limit value, and / or the second importance difference is not greater than a second limit value, it is determined that the first *.docx version problem report and the second *.docx version problem report meet the discharge deadline condition.
[0076] Further, after inputting the first accident handling status identifier into the problem strategy output layer in the current generation model to output a first *.docx version of the problem report; and inputting the second accident handling status identifier into the problem strategy output layer to output a second *.docx version of the problem report, the method further includes:
[0077] Obtaining a first generation sub-scheme and a second generation sub-scheme in the first *.docx version of the problem report, and a third generation sub-scheme and a fourth generation sub-scheme in the second *.docx version of the problem report, wherein the first generation sub-scheme is used to indicate a first occurrence importance of a first man-made accident corresponding to the problem man-made item, the second generation sub-scheme is used to indicate a second occurrence importance of a second man-made accident corresponding to the problem man-made item, the third generation sub-scheme is used to indicate a third occurrence importance of the first man-made accident corresponding to the problem man-made item, the fourth generation sub-scheme is used to indicate a fourth occurrence importance of the second man-made accident corresponding to the problem man-made item, and the at least two man-made accidents include the first man-made accident and the second man-made accident;
[0078] Obtain the fifth occurrence importance of the first man-made accident corresponding to the first X items of the problematic man-made items, and the sixth occurrence importance of the second man-made accident corresponding to the first Y items of the problematic man-made items, where X and Y are natural numbers;
[0079] calculating a third importance difference between the first occurrence importance and the fifth occurrence importance, and a fourth importance difference between the second occurrence importance and the sixth occurrence importance;
[0080] When the third importance difference is greater than the third limit value, and / or the fourth importance difference is greater than the fourth limit value, it is determined that the first *.docx version problem report and the second *.docx version problem report meet the discharge deadline condition.
[0081] Furthermore, the modifying of the model parameters of the currently generated model and the decision of the next item from the multiple accident handling items as the problematic artificial item include at least one of the following:
[0082] Correcting a first problem ratio of the at least two different problem collection Revit API groups, wherein the model parameters include the first problem ratio;
[0083] Modifying a second problem ratio of the problem strategy output layer, wherein the model parameters include the second problem ratio.
[0084] Furthermore, before inputting the body index metadata corresponding to the problem artificial project into the first problem collection RevitAPI group in the current generation model and outputting the first accident handling status identifier output by the first problem collection RevitAPI group, the method further includes: deciding Z problem collection RevitAPIs from the at least three problem collection RevitAPIs, and closing the Z problem collection RevitAPIs, wherein Z is a natural number; combining the problem collection RevitAPIs other than the Z problem collection RevitAPIs in the at least three problem collection RevitAPIs, and outputting the first problem collection RevitAPI group;
[0085] Before inputting the body indicator metadata corresponding to the problem artificial item into the second problem collection RevitAPI group in the current generation model and outputting the second accident handling status identifier output by the second problem collection RevitAPI group, the method also includes: deciding K problem collection RevitAPIs from the at least three problem collection RevitAPIs, and closing the K problem collection RevitAPIs, where K is a natural number; combining the problem collection RevitAPIs other than the K problem collection RevitAPIs in the at least three problem collection RevitAPIs, and outputting the second problem collection RevitAPI group.
[0086] Furthermore, the method further includes: clicking on rule settings to enter a custom collision rule interface, where collision rules can be added; after selecting the collision subject and object, clicking [Save Settings] and closing the interface, the rules will be automatically saved to the system, and the set collision rules can be selected by opening a drop-down menu before collision analysis;
[0087] Select a collision rule to start the program, select Start Analysis or Quick Analysis, wait for the analysis to be completed, and the collision analysis results will be generated in a list;
[0088] Each collision result is composed of a subject and an object, the dark color is the collision subject, and the white color is the collision object;
[0089] When the progress is manually interrupted, the analyzed data will be retained;
[0090] Before viewing the collision results, you need to set the view; set the model transparency to 10% to clearly display the intersection view;
[0091] View collision results: Double-click the analysis result you want to view, and the view will automatically navigate to the cut 3D view;
[0092] Collision result coloring description: The plug-in provides a coloring method to display collision components. By default, the component display state is "color intersection" + "display coloring". The coloring method is controlled by the coloring all hidden coloring in the lower right corner.
[0093] Shading Intersections highlights the intersection of two components; Shading All highlights the two colliding components.
[0094] If you click Hide Coloring, the coloring will be canceled regardless of the current coloring state.
[0095] Among them, in this embodiment, the programming language C# and RevitAPI and WPF Microsoft framework programming are used to realize the automatic entry of problem reports, and the model problem positioning axis network is automatically captured and entered by box selection. During the modification process, the two-dimensional plane position and three-dimensional view position of the model can be found by one key, and the modified view range can be saved. At the same time, the record date is automatically obtained, and the name of the imported drawing can be identified in the software to automatically enter the drawing name. The two-dimensional and three-dimensional model screenshots of the model problem are taken with one key, and the above automatically obtained information is associated with the *.docx version of the problem report template. The final *.docx version of the problem report can be exported, and the screenshot can be automatically centered in the table in the *.docx version of the problem report. It is associated and synchronized with the *.docx version of the problem report in the editing state, and the problem report can be imported after the *.docx version of the problem report is exported, thereby saving a lot of work such as text entry, image capture, and problem report sorting in the project problem report, and realizing the digital management level of BIM modeling and application.
[0096] In the development of the plug-in, we analyzed the API interface and data structure of the Revit software, determined the functional requirements and implementation plan of the plug-in, and realized the deep integration of the plug-in and the Revit software through the programming language C#. The plug-in supports stable operation on different versions of Revit software, and ensures that the plug-in occupies less additional computing resources during operation by optimizing algorithms and data structures.
[0097] With the introduction of this plug-in, the Revit modeling process has become more efficient, accurate and reliable. Designers can get real-time feedback during the modeling process and correct errors in a timely manner, thus avoiding rework and delays caused by problems discovered later in the traditional modeling process. This innovation not only provides designers and engineers with a powerful tool, but also opens up new directions for research and application in the field of engineering.
[0098] According to a second embodiment of the present invention, the present invention claims a system for generating a project problem report during a Revit modeling process, referring to Figure 2 ,include:
[0099] The first acquisition module is used to acquire the project engineering records corresponding to the drawings of the project to be evaluated;
[0100] An input module, used for inputting the project engineering record into a *.docx version problem report template, wherein the *.docx version problem report template is used for generating the importance of the occurrence of at least two man-made accidents corresponding to at least one historical problem strategy for the drawings of the project to be evaluated, the *.docx version problem report template includes at least three problem collection RevitAPIs, the problem collection RevitAPIs are used to capture the connection between the project engineering record on different types of man-made accidents, the at least three problem collection RevitAPIs are divided into at least two different problem collection RevitAPI groups during the iteration process of the *.docx version problem report template, and the problem collection RevitAPI group includes at least one problem collection RevitAPI among the at least three problem collection RevitAPIs;
[0101] A generation module is used to output a *.docx version of the problem report output by the *.docx version of the problem report template, wherein the *.docx version of the problem report is used to indicate the importance of the drawings of the project to be evaluated to the occurrence of at least two man-made accidents corresponding to at least one historical problem strategy.
[0102] The specific implementation methods of the invention are described in detail above, but they are only examples, and the present application is not limited to the specific implementation methods described above. For those skilled in the art, any equivalent modification or substitution of the invention is also within the scope of the present application, and therefore, the equalization, modification, and improvement made without departing from the spirit and principle of the present application should be included in the scope of the present application.
Claims
1. A method for generating a project problem report in the Revit modeling process, based on a secondary development plug-in using the programming language C#, Revit API, and WPF Microsoft framework, characterized in that: include: Obtain the project engineering records corresponding to the drawings of the project to be evaluated; Input the project engineering records into a *.docx version of the problem report template, wherein the *.docx version of the problem report template is used to generate the importance of the occurrence of at least two man-made accidents corresponding to at least one historical problem strategy for the drawings of the project to be evaluated, the *.docx version of the problem report template includes at least three problem collection RevitAPIs, the problem collection RevitAPIs are used to capture the connection between the project engineering records on different types of man-made accidents, the at least three problem collection RevitAPIs are divided into at least two different problem collection RevitAPI groups during the iteration process of the *.docx version of the problem report template, and the problem collection RevitAPI group includes at least one problem collection RevitAPI among the at least three problem collection RevitAPIs; Output the *.docx version of the problem report output by the *.docx version of the problem report template, wherein the *.docx version of the problem report is used to indicate the importance of the drawings of the project to be evaluated to the occurrence of at least two man-made accidents corresponding to at least one historical problem strategy.
2. The method according to claim 1, characterized in that The project engineering records are input into the *.docx version of the problem report template, including: Input the physical indicator metadata corresponding to the project engineering record into the at least three problem collection RevitAPIs, and output the accident handling status identifier output by the at least three problem collection RevitAPIs, wherein the physical indicator metadata is the numerical information of the project engineering record, and the accident handling status identifier is the representation of the physical indicator metadata on the different man-made accident types; The accident handling status identifier is input into the problem strategy output layer in the *.docx version problem report template, and the *.docx version problem report is output.
3. The method according to claim 2, characterized in that Before inputting the project engineering record into the *.docx version problem report template, the method further includes: Acquire multiple accident processing projects, wherein the accident processing projects are condition information having the same condition type as the historical problem strategy; Iterate the initial generation model using the multiple accident handling projects and the at least two different problem collection Revit API groups, and output the iterated generation model; The iterated generation model is decided as the *.docx version of the problem report template.
4. The method according to claim 3, characterized in that The method of iterating the initial generation model by using the multiple accident handling projects and the at least two different problem collection Revit API groups, and outputting the iterated generation model, includes: Repeat the following steps until the iterated generation model is output: Determine the problematic man-made project from among the multiple accident handling projects; Input the body index metadata corresponding to the problem artificial project into the first problem collection RevitAPI group in the current generation model, and output the first accident handling status identifier output by the first problem collection RevitAPI group, wherein the at least two different problem collection RevitAPI groups include the first problem collection RevitAPI group; and, input the body index metadata corresponding to the problem artificial project into the second problem collection RevitAPI group in the current generation model, and output the second accident handling status identifier output by the second problem collection RevitAPI group, wherein the at least two different problem collection RevitAPI groups include the second problem collection RevitAPI group; Inputting the first accident handling status identifier into the problem strategy output layer in the current generation model, and outputting a first *.docx version of the problem report; and, inputting the second accident handling status identifier into the problem strategy output layer, and outputting a second *.docx version of the problem report; In the case that the first *.docx version problem report and the second *.docx version problem report do not meet the discharge deadline condition, modifying the model parameters of the currently generated model, and deciding the next item from the multiple accident processing items as the problem artificial item; When the first *.docx version problem report and the second *.docx version problem report satisfy the discharge deadline condition, the current generation model is decided as the iterated generation model.
5. The method according to claim 4, characterized in that In the step of inputting the first accident handling status identifier into the problem strategy output layer in the current generation model, outputting a first *.docx version of the problem report; and, after inputting the second accident handling status identifier into the problem strategy output layer and outputting the second *.docx version of the problem report, the method further comprises: Obtaining a first generation sub-scheme and a second generation sub-scheme in the first *.docx version of the problem report, and a third generation sub-scheme and a fourth generation sub-scheme in the second *.docx version of the problem report, wherein the first generation sub-scheme is used to indicate a first occurrence importance of a first man-made accident corresponding to the problem man-made item, the second generation sub-scheme is used to indicate a second occurrence importance of a second man-made accident corresponding to the problem man-made item, the third generation sub-scheme is used to indicate a third occurrence importance of the first man-made accident corresponding to the problem man-made item, the fourth generation sub-scheme is used to indicate a fourth occurrence importance of the second man-made accident corresponding to the problem man-made item, and the at least two man-made accidents include the first man-made accident and the second man-made accident; calculating a first importance difference between the first occurrence importance and the third occurrence importance, and a second importance difference between the second occurrence importance and the fourth occurrence importance; When the first importance difference is not greater than a first limit value, and / or the second importance difference is not greater than a second limit value, it is determined that the first *.docx version problem report and the second *.docx version problem report meet the discharge deadline condition.
6. The method according to claim 4, characterized in that In the step of inputting the first accident handling status identifier into the problem strategy output layer in the current generation model, outputting a first *.docx version of the problem report; and, after inputting the second accident handling status identifier into the problem strategy output layer and outputting the second *.docx version of the problem report, the method further comprises: Obtaining a first generation sub-scheme and a second generation sub-scheme in the first *.docx version of the problem report, and a third generation sub-scheme and a fourth generation sub-scheme in the second *.docx version of the problem report, wherein the first generation sub-scheme is used to indicate a first occurrence importance of a first man-made accident corresponding to the problem man-made item, the second generation sub-scheme is used to indicate a second occurrence importance of a second man-made accident corresponding to the problem man-made item, the third generation sub-scheme is used to indicate a third occurrence importance of the first man-made accident corresponding to the problem man-made item, the fourth generation sub-scheme is used to indicate a fourth occurrence importance of the second man-made accident corresponding to the problem man-made item, and the at least two man-made accidents include the first man-made accident and the second man-made accident; Obtain the fifth occurrence importance of the first man-made accident corresponding to the first X items of the problematic man-made items, and the sixth occurrence importance of the second man-made accident corresponding to the first Y items of the problematic man-made items, where X and Y are natural numbers; calculating a third importance difference between the first occurrence importance and the fifth occurrence importance, and a fourth importance difference between the second occurrence importance and the sixth occurrence importance; When the third importance difference is greater than the third limit value, and / or the fourth importance difference is greater than the fourth limit value, it is determined that the first *.docx version problem report and the second *.docx version problem report meet the discharge deadline condition.
7. The method according to claim 4, characterized in that The step of modifying the model parameters of the currently generated model and deciding the next item from the multiple accident handling items as the problematic artificial item includes at least one of the following: Correcting a first problem ratio of the at least two different problem collection Revit API groups, wherein the model parameters include the first problem ratio; Modifying a second problem ratio of the problem strategy output layer, wherein the model parameters include the second problem ratio.
8. The method according to claim 4, characterized in that Before inputting the body index metadata corresponding to the problem artificial project into the first problem collection RevitAPI group in the current generation model and outputting the first accident handling status identifier output by the first problem collection RevitAPI group, the method further includes: deciding Z problem collection RevitAPIs from the at least three problem collection RevitAPIs, and closing the Z problem collection RevitAPIs, where Z is a natural number; combining the problem collection RevitAPIs other than the Z problem collection RevitAPIs in the at least three problem collection RevitAPIs, and outputting the first problem collection RevitAPI group; Before inputting the body indicator metadata corresponding to the problem artificial item into the second problem collection RevitAPI group in the current generation model and outputting the second accident handling status identifier output by the second problem collection RevitAPI group, the method also includes: deciding K problem collection RevitAPIs from the at least three problem collection RevitAPIs, and closing the K problem collection RevitAPIs, where K is a natural number; combining the problem collection RevitAPIs other than the K problem collection RevitAPIs in the at least three problem collection RevitAPIs, and outputting the second problem collection RevitAPI group.
9. The method according to any one of claims 1 to 8, characterized in that The method further includes: clicking on rule settings to enter a custom collision rule interface, where collision rules can be added; after selecting the collision subject and object, clicking "save settings" and closing the interface, the rules will be automatically saved to the system, and the set collision rules can be selected by opening a drop-down menu before collision analysis; Select a collision rule to start the program, select Start Analysis or Quick Analysis, wait for the analysis to be completed, and the collision analysis results will be generated in a list; Each collision result is composed of a subject and an object, the dark color is the collision subject, and the white color is the collision object; When the progress is manually interrupted, the analyzed data will be retained; Before viewing the collision results, you need to set the view; set the model transparency to 10% to clearly display the intersection view; View collision results: Double-click the analysis result you want to view, and the view will automatically navigate to the cut 3D view; Collision result coloring description: The plug-in provides a coloring method to display collision components. By default, the component display state is "color intersection" + "display coloring". The coloring method is controlled by the coloring all hidden coloring in the lower right corner. Coloring intersections will highlight the intersection of the two components; Coloring all will highlight the two colliding components; If you click Hide Coloring, the coloring will be canceled regardless of the current coloring state.
10. A system for generating project problem reports during Revit modeling, characterized in that: include: The first acquisition module is used to acquire the project engineering records corresponding to the drawings of the project to be evaluated; An input module, used for inputting the project engineering record into a *.docx version problem report template, wherein the *.docx version problem report template is used for generating the importance of the occurrence of at least two man-made accidents corresponding to at least one historical problem strategy for the drawings of the project to be evaluated, the *.docx version problem report template includes at least three problem collection RevitAPIs, the problem collection RevitAPIs are used to capture the connection between the project engineering record on different types of man-made accidents, the at least three problem collection RevitAPIs are divided into at least two different problem collection RevitAPI groups during the iteration process of the *.docx version problem report template, and the problem collection RevitAPI group includes at least one problem collection RevitAPI among the at least three problem collection RevitAPIs; A generation module is used to output a *.docx version of the problem report output by the *.docx version of the problem report template, wherein the *.docx version of the problem report is used to indicate the importance of the drawings of the project to be evaluated to the occurrence of at least two man-made accidents corresponding to at least one historical problem strategy.
Citation Information
Patent Citations
REVIT-based smoke control and exhaust system rapid calculation type selection method and system
CN116305477A
Method for rapidly completing room information and net height analysis based on Revit software
CN116842619A
Non-functional test problem evaluation method and device
CN117493187A
