A highway engineering project index data management method and system
By generating and citing indicator data templates for highway engineering projects, configuring mapping rules and matching commercial software data, the management difficulties caused by the diversity of data sources in highway engineering projects are solved, and unified management and complex analysis of indicator data are achieved.
Patent Information
- Application Number
- CN202510100715.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2025-01-22
- Publication Date
- 2025-04-22
- Estimated Expiration
- 2045-01-22
AI Technical Summary
The data sources in existing highway engineering projects are different, making it difficult to manage uniformly, resulting in large differences in indicator data structures and the inability to manage and statistically analyze through unified structured data, which is not conducive to value mining.
Provide a highway engineering project indicator data management method, by generating indicator data templates at different design stages, citing common and special sub-item templates, configuring indicator mapping rules, matching indicator data in commercial software, and calculating structured indicator data.
It realizes unified management and analysis of highway engineering project indicator data, conducts complex query and statistical analysis through structured data, meets the management requirements of different types and design stages, and responds to indicator data exported by different commercial software.
Smart Images

Figure CN119515319B_ABST
Abstract
Description
Technical Field
[0001] The invention relates to the field of highway engineering informatization, and in particular to a highway engineering project index data management method and system. Background Art
[0002] The technical and economic indicator data of highway engineering can provide guidance and reference for the comparison and cost analysis of project plans, and provide a scientific basis for the selection of the final plan. At present, the technical and economic indicator management of highway engineering is mainly completed through relevant commercial software. Due to the different design habits of different design units and the inconsistent index data management methods followed, the index data structures exported by different commercial software in the same project and different bidding sections may also be quite different. It is impossible to manage and statistically analyze through unified structured data, which is not conducive to the value mining of technical and economic indicator data of highway engineering.
[0003] Therefore, a method and system are needed today that can quickly and uniformly manage and analyze the indicator data of highway engineering projects. Summary of the invention
[0004] The purpose of the present invention is to overcome the problem in the prior art that data in existing highway engineering projects have different sources and are difficult to manage, and to provide a highway engineering project indicator data management method and system.
[0005] In order to achieve the above-mentioned object of the invention, the present invention provides the following technical solutions:
[0006] A highway engineering project index data management method comprises the following steps:
[0007] S1: Generate several indicator data templates for different design stages according to preset specifications; the indicator data templates include general sub-item templates and special sub-item templates;
[0008] S2: Reference the general sub-item template corresponding to the current design stage in the highway engineering project to be managed to generate a list of indicators and data of the highway engineering project to be managed;
[0009] S3: configuring an indicator mapping rule for the indicator data template in S1 according to the data structure of the commercial software to be associated; the indicator mapping rule includes a mapping method and a calculation formula;
[0010] S4: traverse each standard sub-item in the list of highway engineering indicator data to be managed, and match the indicator data in the commercial software to be associated for each standard sub-item according to the indicator mapping rule; the indicator data includes engineering quantity, engineering quantity unit, engineering indicator and engineering quantity proportion;
[0011] S5: Based on the matching result in S4, the indicator result is calculated according to the indicator mapping rule, and output as structured indicator data of the highway engineering project to be managed.
[0012] As a preferred solution of the present invention, the design stage includes a feasibility stage, a preliminary design stage and a construction drawing stage;
[0013] The general sub-item template is used to describe the general indicator sub-items applicable to all projects; the general indicator sub-items include the sub-item standard number, sub-item unique number, engineering quantity, engineering quantity unit, engineering indicator and engineering quantity proportion;
[0014] The special sub-item template is used to describe the indicator sub-items that are unique to individual projects.
[0015] As a preferred embodiment of the present invention, S3 comprises the following steps:
[0016] S31: extracting each sub-item data from the indicator data of the commercial software to be associated, performing similarity calculation on the name of each sub-item data and the indicator data template generated in S1 according to a preset data matching rule, and obtaining a corresponding indicator calculation formula;
[0017] S32: matching the corresponding item template according to the similarity calculation result;
[0018] If the matching result is a special item template, it also includes attaching it to the corresponding general item;
[0019] S33: Outputting a preliminary indicator mapping relationship; the preliminary indicator mapping relationship includes a mapping method and an indicator calculation formula.
[0020] As a preferred solution of the present invention, the data matching rule includes a data corresponding relationship and a data matching method;
[0021] The data correspondence relationship includes one-to-one correspondence and one-to-many correspondence;
[0022] The data matching method includes item number matching and logical consistency matching.
[0023] As a preferred embodiment of the present invention, S31 comprises the following steps:
[0024] S311: sequentially matching the standard sub-items of the indicator data template with the indicator data of the commercial software to be associated by sub-item numbers;
[0025] If the match is completed, the matching result of the matched standard item is output as the mapping mode of the standard item;
[0026] If the matching is not completed, the next standard item number matching will be started until all standard items have completed the matching process;
[0027] S312: performing logical consistency matching on the unmatched standard sub-items in the current indicator data template and the indicator data of the commercial software to be associated in sequence, and outputting the matching results of the matched standard sub-items as the mapping mode of the standard sub-items;
[0028] The logical consistency matching is the name similarity matching between the standard sub-items and the indicator data;
[0029] S313: Match the special sub-items in the indicator data template, perform sub-item number matching and / or logic consistency matching within the range corresponding to each special sub-item, and output the matching result of the matched special sub-item as the mapping mode of the special sub-item;
[0030] S314: Construct indicator calculation formula.
[0031] As a preferred solution of the present invention, S3 further includes:
[0032] S34: Adjust the preliminary indicator mapping relationship according to the project situation; the adjustment includes modifying the data matching rules and manually adding project sub-item data.
[0033] As a preferred solution of the present invention, the data matching rule includes a data corresponding relationship and a data matching method;
[0034] The data correspondence relationship includes one-to-one correspondence and one-to-many correspondence;
[0035] The data matching method includes precise matching through unique numbers and matching through keyword similarity.
[0036] As a preferred embodiment of the present invention, S4 comprises the following steps:
[0037] S41: Traversing the standard sub-items in the highway engineering project to be managed according to the number, and matching the corresponding indicator data sub-items in the commercial software according to the indicator mapping rule;
[0038] S42: Calculate the indicator data corresponding to each sub-item according to the indicator calculation formula.
[0039] As a preferred solution of the present invention, the structured indicator data is stored and managed via a relational database.
[0040] As a preferred solution of the present invention, the relational database includes data retrieval, data comparison and data statistics functions;
[0041] The data retrieval is queried according to the index;
[0042] The data comparison displays the structured indicator data in a tree structure;
[0043] The data statistics are used to statistically analyze the indicator data of several sub-items or the whole in the highway engineering project to be managed.
[0044] A highway engineering project indicator data management system includes at least one processor and a memory communicatively connected to the at least one processor; the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute any of the methods described above.
[0045] Compared with the prior art, the present invention has the following beneficial effects:
[0046] The present invention facilitates management based on a relational database through structured indicator data, thereby quickly realizing various complex queries and statistical analyses. At the same time, through configurable indicator data templates, it can meet the indicator data management requirements of projects of different types, different technical levels, and different design stages; and the data matching rules of standard sub-items in the template can be flexibly configured to cope with indicator data exported by different commercial software. In addition, the data structure of indicator data from different sources is unified, and it is realized that the indicator data is managed with unified structured data, and statistical analysis is performed based on the structured data. BRIEF DESCRIPTION OF THE DRAWINGS
[0047] Figure 1 A schematic diagram of a process of managing index data of a highway engineering project according to Embodiment 1 of the present invention;
[0048] Figure 2 A schematic diagram of a process of a highway engineering project index data management method according to Embodiment 2 of the present invention;
[0049] Figure 3 This is a schematic diagram of standard sub-items of structured indicator data in a highway engineering project indicator data management method according to Embodiment 2 of the present invention;
[0050] Figure 4 This is a structural schematic diagram of a highway engineering project index data management system described in Example 3 of the present invention, which utilizes a highway engineering project index data management method described in the above embodiment. DETAILED DESCRIPTION
[0051] The present invention is further described in detail below in conjunction with test examples and specific implementation methods. However, this should not be understood as the scope of the above subject matter of the present invention being limited to the following embodiments, and all technologies realized based on the content of the present invention belong to the scope of the present invention.
[0052] Example 1
[0053] like Figure 1 As shown, a highway engineering project indicator data management method includes the following steps:
[0054] S1: Generate several indicator data templates for different design stages according to preset specifications; the indicator data templates include general sub-item templates and special sub-item templates.
[0055] S2: Reference the general sub-item template corresponding to the current design stage in the highway engineering project to be managed to generate a list of indicator data for the highway engineering project to be managed.
[0056] S3: configuring an indicator mapping rule for the indicator data template in S1 according to the data structure of the commercial software to be associated; the indicator mapping rule includes a mapping method and a calculation formula.
[0057] S4: traverse each standard sub-item in the list of highway engineering indicator data to be managed, and match the indicator data in the commercial software to be associated for each standard sub-item according to the indicator mapping rule; the indicator data includes engineering quantity, engineering quantity unit, engineering indicator and engineering quantity proportion.
[0058] S5: Based on the matching result in S4, the indicator result is calculated according to the indicator mapping rule, and output as structured indicator data of the highway engineering project to be managed.
[0059] The present invention first defines a cost index data template according to relevant standards and specifications for highway engineering. The data template is structured data composed of standard sub-items. Then, when carrying out a specific project, the standard sub-items of the project index data are generated by referencing the index data template, and a mapping rule between the standard sub-items of the project index data and the sub-items of the commercial software index data is established. The rule specifically includes the corresponding relationship between the template standard sub-items and the commercial software index data sub-items, the index calculation formula, and the like. Finally, the conversion of the commercial software index data sub-items to the index data template standard sub-items can be realized, forming structured data composed of standard sub-items, so as to carry out various statistical analyses.
[0060] Example 2
[0061] This embodiment is a specific implementation method of the highway engineering project index data management method described in Example 1. Figure 2 As shown, the following steps are included:
[0062] S1: Generate several indicator data templates for different design stages according to preset specifications; the indicator data templates include general sub-item templates and special sub-item templates, which are expressed in the form of a standard sub-item list.
[0063] The preset specification is a national standard specification, and the indicator data template is kept updated according to the version of the standard specification.
[0064] The design stage includes the feasibility stage, the preliminary design stage and the construction drawing stage; the indicator data template includes a general sub-item template and a special sub-item template.
[0065] The general sub-item template is used to describe the general indicator sub-items applicable to all projects.
[0066] The special sub-item template is used to describe the indicator sub-items unique to individual projects, such as the indicator sub-items of a specific bridge, tunnel, interchange or other structure.
[0067] The indicator sub-item data structure includes sub-item standard number, sub-item unique number, engineering quantity, engineering quantity unit, engineering indicator, engineering quantity proportion, etc. Among them, the special sub-item template does not have a sub-item unique number when it is not referenced in the project.
[0068] S2: Reference the general sub-item template corresponding to the current design stage in the highway engineering project to be managed to generate a list of indicator data for the highway engineering project to be managed.
[0069] Furthermore, the general sub-item templates are defined according to relevant standards and specifications, including general sub-item templates for the feasibility stage, preliminary design stage, and construction drawing stage. The framework structure of different general sub-item template data remains completely consistent. For example, all general sub-items include the four parts specified in the specifications, namely, the first part of building installation engineering, the second part of land use and demolition, the third part of engineering construction, and the fourth part of highway basic engineering quantity. However, if the design stage is different and the level of detail of the sub-items is different, the hierarchical structure of the sub-items will be different. For example, the sub-items in the feasibility stage are numbered up to 103, and the numbering level of the construction drawing stage can be up to 1030105 based on the number 103.
[0070] Furthermore, the sub-item standard number is a number used by the design unit in accordance with design habits, usually including various abbreviation codes, such as LJ (roadbed), LM (pavement), QL (bridge), SD (tunnel), etc., for the purpose of facilitating display and type identification, but there may be duplications and no bias towards data query. The sub-item unique number is based on the unique number of the sub-item in the current structured data. The sub-item unique number is an odd-digit string, each character is an Arabic numeral, and the number after removing the last two digits is the parent number of the sub-item. For example, if the current sub-item number is 10103, its parent number is 101. The sub-item unique number is for the convenience of self-identification and query of data.
[0071] Furthermore, when managing the indicator data of a specific project, standard sub-items of the project indicator data are formed by referencing the corresponding general sub-item templates and special sub-item templates; the sub-items in the special sub-item template can be attached to the sub-items in the general sub-item template, and then all the sub-item unique numbers in the special sub-item template are automatically generated according to the attached parent general sub-items.
[0072] S3: configuring an indicator mapping rule for the indicator data template in S1 according to the data structure of the commercial software to be associated; the indicator mapping rule includes a mapping method and a calculation formula.
[0073] Since the definition of a certain standard item in the commercial software indicator data is different from the definition of the standard item in the indicator data, it is necessary to establish a mapping rule between the standard item in the indicator data and the commercial software indicator data item. The specific bridges, tunnels, and interchanges in the commercial software indicator data item need to be linked to the general item through a special item template. When referencing a special item template, the corresponding special item template is first found through the similarity calculation of the item name. If it is not found, it is manually selected.
[0074] S31: extracting each sub-item data from the indicator data of the commercial software to be associated, and performing similarity calculation on the name of each sub-item data and the indicator data template generated in S1 according to the preset data matching rules, and obtaining the corresponding indicator calculation formula. The structure of the sub-item of the indicator data of the commercial software to be associated mainly includes the sub-item standard number, sub-item name, sub-item unique number, engineering quantity, engineering quantity unit, etc.
[0075] The data matching rules include data corresponding relationship and data matching method;
[0076] The data correspondence relationship includes one-to-one correspondence and one-to-many correspondence;
[0077] The data matching methods include item number matching, logical consistency matching and matching according to special rules, specifically:
[0078] S311: sequentially matching the standard sub-items of the indicator data template with the indicator data of the commercial software to be associated by sub-item numbers;
[0079] If the match is completed, the matching result of the matched standard item is output as the mapping mode of the standard item;
[0080] If the matching is not completed, the next standard item number matching will be entered until all standard items have completed the matching process.
[0081] Since the number is a multi-digit Arabic numeral number, the standard sub-items of the indicator data template and the indicator data of the commercial software to be associated need to comply with relevant industry standards. Some sub-items have consistent numbering and logic. Such sub-items can be matched by number.
[0082] S312: logically matching the unmatched standard sub-items in the current indicator data template with the indicator data of the commercial software to be associated in sequence, and outputting the matching results of the matched standard sub-items as the mapping mode of the standard sub-items.
[0083] When matching by number is not possible, it is necessary to calculate the similarity between the names of the highway engineering indicator data to be managed and the indicator data of the commercial software to be associated, and logically determine whether they describe the same object. The logical consistency matching is the name similarity matching between the standard sub-item and the indicator data. Among them, the similarity matching method includes but is not limited to algorithms such as plain text similarity calculation and AI text similarity matching.
[0084] S313: Match the special sub-items in the indicator data template, and perform sub-item number matching and / or logical consistency matching within the range corresponding to each special sub-item, and output the matching result of the matched special sub-item as the mapping method of the special sub-item.
[0085] For example, a sub-item "hub interconnection" in the highway engineering indicator data to be managed needs to obtain all hub interconnections according to the number and name in a certain range in the commercial software indicator data to be associated, and use it as a matching result.
[0086] S314: Construct indicator calculation formula.
[0087] In this embodiment, the calculation formula is described by a character string.
[0088] For example, 1090203.economyCost / 10000 / 1090203.engineer1, where 1090203 is the current item number, the string economyCost is the cost, and engineer1 is the engineering quantity. The meaning of this formula is: the indicator value of number 1090203 is the cost divided by the engineering quantity.
[0089] S32: matching the corresponding item template according to the similarity calculation result;
[0090] If the matching result is a special item template, it also includes attaching it to the corresponding general item;
[0091] S33: Outputting a preliminary indicator mapping relationship; the preliminary indicator mapping relationship includes a mapping method and an indicator calculation formula.
[0092] Furthermore, the S3 also includes:
[0093] S34: Adjust the preliminary indicator mapping relationship according to the project situation; the adjustment includes modifying the data matching rules and manually adding project sub-item data.
[0094] That is, in addition to the standard sub-items in the general sub-item template and the special sub-item template, in actual projects, sub-items can also be manually added according to the specific circumstances of the project, and they can be specifically marked as manually added.
[0095] Through the data matching rules, each standard sub-item in the indicator data template can be matched to the corresponding commercial software indicator data sub-item. By matching the engineering quantity, engineering quantity unit and other data and the indicator calculation formula of a single or multiple commercial software indicator data sub-items, the engineering quantity, engineering quantity unit, engineering indicator, engineering quantity proportion and other data of the standard sub-item can be calculated.
[0096] S4: traverse each standard sub-item in the list of highway engineering indicator data to be managed, and match the indicator data in the commercial software to be associated for each standard sub-item according to the indicator mapping rule; the indicator data includes engineering quantity, engineering quantity unit, engineering indicator and engineering quantity proportion.
[0097] S41: Traversing the standard sub-items in the highway engineering project to be managed according to the number, and matching the corresponding indicator data sub-items in the commercial software according to the indicator mapping rule;
[0098] S42: Calculate the indicator data corresponding to each sub-item according to the indicator calculation formula.
[0099] S5: Based on the matching result in S4, the indicator result is calculated according to the indicator mapping rule, and output as structured indicator data of the highway engineering project to be managed. The structured indicator data is as follows: Figure 3 shown.
[0100] The structured indicator data is stored and managed via a relational database.
[0101] The relational database includes data retrieval, data comparison and data statistics functions;
[0102] The data retrieval is queried according to the index;
[0103] The data comparison displays the structured indicator data in a tree structure;
[0104] The data statistics are used to statistically analyze the indicator data of several individual or overall sub-items in the highway engineering project to be managed.
[0105] Example 3
[0106] like Figure 4 As shown, a highway engineering project index data management system includes at least one processor, a memory connected to the at least one processor, and at least one input / output interface connected to the at least one processor; the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the highway engineering project index data management method described in the above embodiment. The input / output interface may include a display, a keyboard, a mouse, and a USB interface for inputting and outputting data.
[0107] Those skilled in the art can understand that: all or part of the steps of implementing the above method embodiments can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above method embodiments; and the aforementioned storage medium includes: mobile storage devices, read-only memories (ROM), disks or optical disks, etc. Various media that can store program codes.
[0108] When the above-mentioned integrated unit of the present invention is implemented in the form of a software functional unit and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present invention can be essentially or partly reflected in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the methods described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROMs, magnetic disks, or optical disks.
[0109] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the protection scope of the present invention.
Claims
1. A highway engineering project index data management method, characterized in that: The following steps are involved: S1: Generate several indicator data templates for different design stages according to preset specifications; the indicator data templates include general sub-item templates and special sub-item templates; The design stage includes the feasibility stage, the preliminary design stage and the construction drawing stage; The general sub-item template is used to describe the general indicator sub-items applicable to all projects; the general indicator sub-items include the sub-item standard number, sub-item unique number, engineering quantity, engineering quantity unit, engineering indicator and engineering quantity proportion; The special sub-item template is used to describe the indicator sub-items that are unique to individual projects; S2: Reference the general sub-item template corresponding to the current design stage in the highway engineering project to be managed to generate a list of indicators and data of the highway engineering project to be managed; S3: configuring an indicator mapping rule for the indicator data template in S1 according to the data structure of the commercial software to be associated; the indicator mapping rule includes a mapping method and a calculation formula; S4: traverse each standard sub-item in the list of highway engineering indicator data to be managed, and match the indicator data in the commercial software to be associated for each standard sub-item according to the indicator mapping rule; the indicator data includes engineering quantity, engineering quantity unit, engineering indicator and engineering quantity proportion; S5: Based on the matching result in S4, the indicator result is calculated according to the indicator mapping rule, and output as structured indicator data of the highway engineering project to be managed; The S3 comprises the following steps: S31: extracting each sub-item data from the indicator data of the commercial software to be associated, performing similarity calculation on the name of each sub-item data and the indicator data template generated in S1 according to a preset data matching rule, and obtaining a corresponding indicator calculation formula; S32: matching the corresponding item template according to the similarity calculation result; If the matching result is a special item template, it also includes attaching it to the corresponding general item; S33: Outputting a preliminary indicator mapping relationship; the preliminary indicator mapping relationship includes a mapping method and an indicator calculation formula.
2. A highway engineering project index data management method according to claim 1, characterized in that: The data matching rules include data corresponding relationship and data matching method; The data correspondence relationship includes one-to-one correspondence and one-to-many correspondence; The data matching method includes item number matching and logical consistency matching.
3. A highway engineering project index data management method according to claim 2, characterized in that: The S31 comprises the following steps: S311: sequentially matching the standard sub-items of the indicator data template with the indicator data of the commercial software to be associated by sub-item numbers; If the match is completed, the matching result of the matched standard item is output as the mapping mode of the standard item; If the matching is not completed, the next standard item number matching will be started until all standard items have completed the matching process; S312: performing logical consistency matching on the unmatched standard sub-items in the current indicator data template and the indicator data of the commercial software to be associated in sequence, and outputting the matching results of the matched standard sub-items as the mapping mode of the standard sub-items; The logical consistency matching is the name similarity matching between the standard sub-items and the indicator data; S313: Match the special sub-items in the indicator data template, perform sub-item number matching and / or logic consistency matching within the range corresponding to each special sub-item, and output the matching result of the matched special sub-item as the mapping mode of the special sub-item; S314: Construct indicator calculation formula.
4. A highway engineering project index data management method according to claim 1, characterized in that: The S3 further includes: S34: Adjust the preliminary indicator mapping relationship according to the project situation; the adjustment includes modifying the data matching rules and manually adding project sub-item data.
5. A highway engineering project index data management method according to claim 1, characterized in that: The S4 comprises the following steps: S41: Traversing the standard sub-items in the highway engineering project to be managed according to the number, and matching the corresponding indicator data sub-items in the commercial software according to the indicator mapping rule; S42: Calculate the indicator data corresponding to each sub-item according to the indicator calculation formula.
6. A highway engineering project index data management method according to claim 1, characterized in that: The structured indicator data is stored and managed via a relational database.
7. A highway engineering project index data management method according to claim 6, characterized in that: The relational database includes data retrieval, data comparison and data statistics functions; The data retrieval is queried according to the index; The data comparison displays the structured indicator data in a tree structure; The data statistics are used to statistically analyze the indicator data of several individual or overall sub-items in the highway engineering project to be managed.
8. A highway engineering project index data management system, characterized in that: It includes at least one processor and a memory communicatively connected to the at least one processor; the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the method described in any one of claims 1 to 7.
Citation Information
Patent Citations
Index data processing method and device and computer equipment
CN116401323A
Business system engineering management report generation method, device and system
CN118734824A