Automatic management method of information model
Through custom management rules and automated processing, the problems of low efficiency and difficult quality of personalized needs in name and hierarchy in information model management are solved, and efficient information model management is achieved.
Patent Information
- Application Number
- CN202510337436.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-03-21
- Publication Date
- 2025-07-01
AI Technical Summary
In the management of information models, especially when dealing with diversified name and hierarchical personalized needs, the prior art has problems such as large workload, low efficiency, poor iterability and difficult to control quality.
Provide an automated management method of information model. Through custom management rules, it automatically handles changes in the hierarchical names and hierarchical relationships of the information model, including obtaining object hierarchies and attributes, sorting management requirements, formulating name and hierarchical rules, and using the information model management automation module to make changes to ensure the automatic completion of management requirements.
It greatly improves the efficiency of information model management, saves coding and testing time, meets diversified management needs, shortens cycles, and improves quality control.
Smart Images
Figure CN120235577A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of information model management, and particularly to an automated management method for information models. Background Art
[0002] To build "one set of models and one set of data" for highway design, construction, maintenance, operation, etc., and basically achieve digitalization throughout the life cycle. For this purpose, supporting policies have been formulated, and a technical guide for BIM result delivery (referred to as the "Delivery Standard") has been developed.
[0003] In the "Delivery Standard", the main body of BIM result delivery is an information model in IFC file format, which includes information objects and the management of information objects. Among them, the management of information objects stipulates that the objects in the information model should have a unified naming rule, and the information models of each specialty have a basic hierarchical structure. The hierarchical structure and name requirements in actual projects are related to project characteristics, application scenarios, management methods, etc., and are customized according to project requirements.
[0004] The management of information models includes the names of objects and the hierarchical structures of objects. In the current technical methods, there are generally two ways to manage information models. The first is to add or modify the code related to information model management according to management requirements. The second is to manually adjust and modify on the basis of the first. At the same time, each management information model in the existing technology requires a set of codes. Therefore, when applied to the management requirements of diverse information models (such as the need to solve the personalized naming and hierarchical personalization requirements), there are often disadvantages such as large workload, low efficiency, poor iterability, and difficult quality control. Summary of the Invention
[0005] To solve the above problems, the present invention provides an automated management method for information models, which provides a method for automatically solving different requirements for hierarchical names and hierarchical relationships in various application scenarios during information model management. When the management requirements of the information model change, it only needs to define the management requirement rules to complete automatically. Compared with the existing technology of one set of codes for one management requirement, it saves a large amount of coding and testing time, greatly improves efficiency and shortens the cycle, and meets the diverse management requirements of projects.
[0006] According to one aspect of the present invention, an automated management method for information models is provided, including the following steps
[0007] A: Obtain the object hierarchy and object attributes of the original information model, where the information model is composed of objects, there are hierarchical relationships between objects, objects have types and attribute sets, and there are multiple instances of each object type, and each instance has a unique identifier;
[0008] B: Sort out the management requirements of the information model, where the management requirements include name requirements and hierarchical requirements;
[0009] C: Convert the management requirements into rules and create templates, including converting the name requirements into name rules according to object types and converting the hierarchical requirements into hierarchical rules according to object types;
[0010] D: Use the information model management automation module to complete the changes to the names and hierarchies of the instances;
[0011] E: Use the names and hierarchies changed in step D to create a changed information model according to the data structure of the original information model;
[0012] Among them, step C also includes the following steps
[0013] S1: Sort out the management requirements in the basic way of making rule templates and prepare the data;
[0014] S2: Formulate name rules, where the name rules include object type, instance name, superior management object type, screening conditions, priority;
[0015] S3: Formulate hierarchical rules, where the hierarchical rules include object type, direct superior object type, direct superior management node name, direct superior same attribute, screening conditions, priority;
[0016] Among them, step D also includes the following steps
[0017] S4: Read the information model and management requirement templates to complete the input of the information model management automation module. Among them, the input content mainly includes hierarchical data, name rules and hierarchical rules;
[0018] S5: Analyze the information model to obtain instance attributes and instance superior attributes;
[0019] S6: Analyze the management requirement template to obtain the object attributes required for management;
[0020] S7: Check the feasibility of the rules and generate a check report when a feasibility exception occurs;
[0021] S8: Calculate the instance name;
[0022] S9: Calculate the instance hierarchy;
[0023] Among them, step E also includes the following steps
[0024] S10: Establish pure management nodes;
[0025] S11: Establish instance management nodes;
[0026] S12: Copy the attributes of the instances in the original information model.
[0027] In some embodiments, in S1, the management requirement rule template includes a name rule and a hierarchy rule. Each rule is formulated according to the object type. The variable content in the rule is expressed using attributes, and the representation method of the attribute is "[object type.attribute index name]". The attribute can use all the attributes of the current object type and the superior object types in the original information model. The superior object type refers to the direct superior and all indirect superior object types. The advantage is that it further describes the specific content of the management requirement template.
[0028] In some embodiments, in S4, each item in the hierarchy structure of the hierarchical data is a node. The node content includes an index name, a parent index name, a node name, an object type, and an attribute set, and all are generated by converting the original information model. The set of name rules corresponds to the name rule table of the management requirement template, and the set of hierarchy rules corresponds to the hierarchy rule table of the management requirement template. The advantage is that it further describes the specific content input by the information model management automation module.
[0029] In some embodiments, in step S5, it includes obtaining root node information, filtering instance nodes, and calculating all the superior object types and superior instances of the instance. The advantage is that it further describes the specific content of parsing the information model.
[0030] In some embodiments, in step S6, it includes parsing the name rule and the hierarchy rule, and respectively obtaining the object type and attribute name required for name management and hierarchy management. The advantage is that it further describes the specific content of parsing the management requirement template and obtaining the attributes required for management.
[0031] In some embodiments, in step S7, it includes traversing the instance nodes in the hierarchical data. Each instance node completes the feasibility calculation of the name rule, the feasibility calculation of the hierarchy rule, and the depth check calculation of the hierarchy rule, and generates an inspection report for all exceptions and warnings. The advantage is that it further describes the specific content of checking the rule feasibility.
[0032] In some embodiments, in step S8, it includes obtaining the name rule used by the instance, obtaining the variable value in the name rule, replacing the variable content in the instance name with the variable value, and keeping the instance name unchanged when the value of the name rule is abnormal. The advantage is that it further describes the specific content of calculating the instance name.
[0033] In some embodiments, in step S9, it includes obtaining the hierarchy rule used by the instance, obtaining the direct superior object instance, obtaining the variable value in the hierarchy rule, replacing the variable content in the name of the direct superior management node with the variable value, and keeping the fixed value unchanged. The advantage is that it further describes the specific content of calculating the instance hierarchy.
[0034] In some embodiments, in step S10, the "direct superior management node name" calculated using step D is used to establish multi-level management nodes according to the original information model data structure. The advantage is that it further describes the specific manner of establishing pure management nodes.
[0035] In some embodiments, in step S11, an instance of the calculated direct superior object type is used, and a management node is established according to the original information model data structure, where the name of the instance management node is the calculated instance name. The advantage is that it further describes the specific manner of establishing an instance management node.
[0036] In some embodiments, in step S12, the index name and attribute set in the original information model data structure are copied to the new information model. The advantage is that it further describes the specific manner of copying the attributes of the instances in the original information model. BRIEF DESCRIPTION OF THE DRAWINGS
[0037] Figure 1 is the general flowchart of an automated management method for an information model according to an embodiment of the present invention;
[0038] Figure 2 is Figure 1 the flowchart implementation step diagram of using the information model management automation module as shown. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0039] The present invention will be further described in detail below with reference to the accompanying drawings.
[0040] For the convenience of narration, the information model in this article uses the IFC delivery format of the "Delivery Guide", and the professional content is exemplified by the bridge profession. In actual application, the content and delivery format of the information model are not limited. It is applicable not only to the BIM information model in the "Delivery Guide" but also to other information models composed of objects.
[0041] As Figure 1 shown, the automated management method includes the following main steps A to E, which are described as follows.
[0042] A: Obtain the object hierarchy and object attributes of the original information model for reference when making a management requirement template: Among them, relevant materials can be obtained (that is, the information model delivered according to the "Delivery Guide", and its object attributes can be found in Appendix B of the "Delivery Guide"), or the information model can be obtained through a viewing software that supports the delivery format, or the delivery file of the information model can be read and output in a common format such as a data table.
[0043] The information model consists of objects with a hierarchical relationship among them. Each object has a type and a set of attributes. There are multiple instances for each object type, and each instance has a unique identifier. Among them, the attribute value is a set of attributes, and an attribute includes an attribute name and an attribute value. The attribute name is related to the object, and the attribute value is related to the instance.
[0044] The information in the information model is hierarchical data of objects, including object type, index name, node name, attribute set, parent node index name, etc. It can also be divided into an instance set of the object type and various superior information (such as various superior object types and instances of the instance).
[0045] B: Organize the management requirements of the information model: Among them, the management requirements are divided into two aspects: name requirements and hierarchical requirements. Organize the requirements of these two aspects according to the object type, and extract the required object attributes from the requirements. For the attributes that do not exist in the first step, add them to the information model.
[0046] C: Convert the management requirements into rules and create templates: Include, according to the object type, convert the name requirements into name rules. The name rules include fixed content and variable content, and the variable content comes from the object attributes in the first step; and convert the hierarchical requirements into hierarchical rules according to the object type. The hierarchical rules include superior object type, hierarchical relationship condition, superior object additional condition, and hierarchical content.
[0047] As Figure 2 shown, making the management rule template based on the management requirements mainly includes several steps such as S1 to S3 described below:
[0048] S1: Sort out the management requirements and prepare data according to the basic method of making the rule template, including the following content.
[0049] 1. The management requirement rule template includes name rules and hierarchical rules. Each rule is formulated according to the corresponding object type, and the variable content in the rule is expressed using attributes.
[0050] 2. The representation method of the attribute is "[object type.attribute index name]". When the object type is itself, it can be simplified to "[attribute index name]". Among them, the information in "[]" is the content that needs to change in the rule, and its value changes automatically according to the instance.
[0051] 3. The attribute can use all attributes of the current object type and the superior object types in the original information model. The superior object type is the object type of the direct superior and all indirect superiors.
[0052] Preferably, a general attribute "_suptype" can be added in this method to represent the superior object type attribute.
[0053] 4. Each instance can only have one supporting rule. When no rule is found or there is more than one rule, it needs to be modified according to the rule check report.
[0054] S2: Formulate name rules, where the name rules include object type, instance name, superior management object type, screening conditions, and priority.
[0055] When formulating a name rule, the "object type" and "instance name" are required, while the "parent object type" and "filter conditions" can be filled in as needed.
[0056] The details of filling in each option are as follows:
[0057] 1. "Object Type": The full set of each specialty is defined in Appendix B of the Delivery Guide. Each object has a unique "Type" value;
[0058] 2. "Instance name": It consists of a variable part and a fixed part. The variable part is the attribute of the object type. The object type can be the current object and the parent object of the original level. For the attributes, refer to S1;
[0059] 3. "Superior object type": fill in the object type of the superior (such as v1). The superior can be a direct superior or an indirect superior. "Superior object type" is a simplified way of "Filter conditions", which is equivalent to filling in the superior object type attribute value condition in "Filter conditions" (such as "[_suptype] == v1"). Generally, "Superior object type" can meet most of the name management requirements. In complex situations, fill in "Filter conditions" as needed;
[0060] 4. "Filter Condition": conditional expression. Multiple conditions are separated by ",". It is true when it is not filled in or all conditions are met. The conditional expression consists of three parts: attribute, relationship symbol, and condition value. There are six types of relationship symbols: value greater than ">", value less than "<", value equal to "==", value not equal to "!=", value greater than or equal to ">=", and value less than or equal to "<=";
[0061] 5. "Priority": fill in a number. If the number is non-positive, it means that the row is ignored, which is equivalent to the row rule not existing. If the number is positive, the smaller the number, the higher the priority. In addition, the number of rows that meet the screening conditions for the same priority and the same object type cannot exceed one.
[0062] The following takes the bridge pile foundation as an example. The names of the bridge pile foundations are as follows: platform 0#1 pile foundation, pier 1#2 pile foundation.
[0063] Upon analysis, the variable part is the number. The number before the '#' sign is the number of the lower pier or abutment, which is also the borehole layout line number. The number after the '#' sign is the pile foundation number. The words 'pier' and 'abutment' are related to the conditions of the higher-level management type to which the pile foundation belongs. 'Pile foundation' can be regarded as fixed content or the value of the 'type' attribute.
[0064] According to the object attributes in Appendix B of the 'Delivery Guide', the 'bridge pier' object has a borehole layout line number, the 'abutment' object has a borehole layout line number, and the 'pile foundation' has a number but no borehole layout line number. If the higher-level management of the pile foundation has a bridge pier or an abutment, the borehole layout line number of its higher level, that is, the bridge pier or the abutment, can be used. The rule filling can be done according to habits as long as the requirements are met. As shown in Table 1, there are slight differences in the name rule filling for Priority 1 and Priority 2, but the results are the same. Only one of them needs to be selected during actual filling.
[0065] Table 1 Example of the name rule for bridge pile foundations
[0066]
[0067] S3: Formulate hierarchical rules, where the hierarchical rules include object type, direct superior object type, direct superior management node name, direct superior same attribute, screening conditions, and priority.
[0068] When formulating hierarchical rules, 'direct superior' refers to the management object of the parent level, and 'indirect superior' refers to management objects such as 'grandparent level' and 'great-grandparent level'. And except for the topmost level, the rest of the instances have and only have one 'direct superior'.
[0069] Among them, the 'direct superior instance screening conditions' are filled in as required, and the other items must be filled in.
[0070] The filling conditions for each option are as follows:
[0071] 1. 'Object type' and 'direct superior object type': The filling method is the same as when formulating the name rules above;
[0072] 2. 'Direct superior management node name': The name can be empty or a multi-level name. When the name is empty, it means there is no management node. When it is a multi-level name, the levels are separated by ' / ', which is equivalent to further subdividing multiple levels within the management node, and the name filling method is the same as when formulating the name rules above;
[0073] 3. 'Direct superior instance same attribute': It is a simplified expression of the screening conditions, which is equivalent to the instance having the same value as the parent-level management instance in the specified attribute. When there are multiple attributes, they are separated by commas in English, and it is true when multiple attribute values all meet the conditions;
[0074] 4. "Direct Superior Instance Screening Criteria": May be used in complex situations, and the filling method is the same as when formulating the above naming rules;
[0075] 5. "Priority": The filling method is the same as when formulating the above naming rules.
[0076] Taking bridge pile foundations as an example again, as shown in Table 2, if it is required to be placed under the pier or abutment object where it is located, and at the same time add two levels of directories, "Foundation" and "Pile Foundation", the hierarchical rules of Priority 1 or Priority 2 below both meet the requirements; while if it is required to be placed under the bridge where it is located and manage by type level, the hierarchical rules of Priority 3 are required to meet the requirements.
[0077] Table 2 Example of Hierarchical Rules for Bridge Pile Foundations
[0078]
[0079] D: Use the information model management automation module to complete the changes of the instance names and hierarchies: Among them, first convert the information model in the first step into the original management information, then check the rules in the third step and generate an inspection report until the inspection passes, and then determine the name for each object instance according to the naming rules, and find the unique superior for each object instance according to the object hierarchical rules and determine the hierarchical content.
[0080] As Figure 2 shown, the operation process of using the information model management automation module mainly includes several steps such as S4 to S9 described below.
[0081] S4: Read the information model and management requirement template to complete the input of the information model management automation module. Among them, the input content mainly includes hierarchical data, naming rules, and hierarchical rules, etc., and the specific input method is described below.
[0082] 1. Hierarchical data: The model data structure of the information model management automation module adopts a flat hierarchical structure. Each content in the hierarchical structure is a node, and the flat hierarchical structure is the set of all nodes; among them, nodes with object types are instance nodes, and nodes without object types are directory nodes for management. The node content includes index name, parent index name, node name, object type, and attribute set, all of which are generated by converting the original information model, such as converting from the information model data structure in IFC format.
[0083] 2. Naming rules: The set of naming rules corresponds to the naming rule table in the management requirement template. Each row in the rule table corresponds to a naming rule. For example, when the management requirement template is in excel format, it is converted from the "Naming Rules" worksheet.
[0084] 3. Hierarchical Rules: The set of hierarchical rules corresponds to the hierarchical rule table of the management requirement template. Each row in the rule table corresponds to a name rule. For example, when the management requirement template is in Excel format, it is converted from the "Hierarchical Rules" worksheet.
[0085] S5: Analyze the information model to obtain instance attributes and the attributes of the instance's superiors.
[0086] Among them, analyzing the information model mainly includes the following content:
[0087] 1. Obtain root node information: For the object type and instance index name, there can only be one root node. If the top nodes of the information model are multiple scattered nodes, a pure management node needs to be added as the root node;
[0088] 2. Filter instance nodes: That is, classify instances according to the object type, and pure management nodes are not counted;
[0089] 3. Calculate all the superior object types and superior instances of the instance. The information of each instance refers to the hierarchical data in the previous steps.
[0090] S6: Analyze the management requirement template to obtain the object attributes required for management.
[0091] Analyzing the management requirement template includes analyzing name rules and hierarchical rules. Among them, analyzing name rules can obtain the object type and attribute name required for name management, while analyzing hierarchical rules can obtain the object type and attribute name required for hierarchical management.
[0092] S7: Check the feasibility of the rules. When a feasibility exception occurs, generate a check report and explain the location and reason of the exception.
[0093] Among them, checking the feasibility of the rules mainly includes the following content:
[0094] 1. Perform feasibility calculations for name rules, feasibility calculations for hierarchical rules, and depth check calculations for hierarchical rules on instance nodes. When calculating, proceed according to the priority of the hierarchical rules. If the calculation meets the requirements, stop the calculation, select this rule, and no longer calculate the rules with lower priority;
[0095] 2. Feasibility calculation of name rules: According to the above name rule requirements, the analyzed information model, and the analyzed name rules, calculate the name rules that each instance meets. If there are multiple matching name rules, the exception needs to be corrected, such as adding filtering conditions, etc. Check the attributes in "[]". If they do not exist, issue a warning and suggest correction;
[0096] 3. Hierarchical rule feasibility calculation: Calculate the hierarchical rules satisfied by each instance according to the above-mentioned name rule requirements, the parsed information model, and the parsed hierarchical rules. Check the attributes in "[]" in the hierarchical rules. If they do not exist, it is an exception and needs to be modified. Add the missing attributes to the information model;
[0097] 4. Hierarchical rule depth check calculation: According to the above-mentioned "same attributes of direct superior instances" and the parsed information model, check the parent instances of the instance nodes under the supporting hierarchical rules in the above-mentioned "hierarchical rule feasibility calculation". If there is more than one parent instance, it is an exception and the hierarchical rules need to be modified, such as adding parent instance conditions; for those without parent instances, if there should be parent instances according to the hierarchical rules, it is an exception and the errors in the hierarchical rules or the information model need to be corrected;
[0098] 5. Traverse all instance nodes in the hierarchical data and generate an inspection report for all exceptions and warnings.
[0099] S8: Calculate the instance name.
[0100] Among them, the items and methods of this calculation mainly include the following:
[0101] 1. Obtain the name rule used by the instance: According to the above-mentioned "name rule feasibility calculation", obtain the matching name rule of the instance;
[0102] 2. Obtain the variable values in the name rule: According to the above-mentioned "parse name rule" and "parse information model", obtain the object type attribute values used in the instance name rule, which are called the variable values in the instance name;
[0103] 3. Replace the content in "[]" in the "instance name" of the instance name rule with the above-mentioned "variable values", and keep the fixed values unchanged.
[0104] 4. If the value of the "name rule" is abnormal, the name remains in its original state.
[0105] S9: Calculate the instance level.
[0106] Among them, the items and methods of this calculation mainly include the following:
[0107] 1. Obtain the hierarchical rule used by the instance: According to the above-mentioned "hierarchical rule feasibility calculation", obtain the matching hierarchical rule of the instance;
[0108] 2. Obtain the instance of the direct superior object type: Obtain the instance of the direct superior object type according to the above-mentioned hierarchical rule depth check calculation;
[0109] 3. Obtain the variable values in the hierarchical rules: According to the above "parsing hierarchical rules" and "parsing information model", obtain the object type attribute values used in the instance hierarchical rules, which are called the variable values at the instance level;
[0110] 4. Name of the superior management node: According to the above "name of the direct superior management node", replace the changed content within "[]" with "variable values", and keep the fixed values unchanged.
[0111] E: Use the information model management automation module in step D to parse the results of the name and hierarchical rules, create a new information model according to the data structure of the original information model, update the hierarchical and instance node names, and copy information such as the attribute set.
[0112] Among them, this step mainly includes the following steps S10 to S12:
[0113] S10: Establish pure management nodes: Use the calculated "name of the direct superior management node" to establish multi-level management nodes according to the data structure of the original information model. Among them, the " / " in the "name of the direct superior management node" represents a hierarchical management;
[0114] S11: Establish instance management nodes: Use the instances of the calculated direct superior object type and establish management nodes according to the data structure format of the original information model. Among them, the name of the instance management node is the calculated instance name;
[0115] S12: Copy the attributes of the instances in the original information model: Copy the other attributes of the instances in the data structure of the original information model except for the hierarchy and name, such as the index name, attribute set, etc., to the new information model.
[0116] The automated management method of an information model in the present invention mainly has the following beneficial effects:
[0117] 1. Provide a method to automatically solve the different requirements of hierarchical names and hierarchical relationships in various application scenarios during information model management through custom management rules;
[0118] 2. When the management requirements of the information model change, customize the name and hierarchical rule templates according to the management requirements, and then use the information model management automation function to automatically complete a new information model that meets the management requirements;
[0119] 3. Compared with the method of one set of code for one management requirement in the prior art, it saves a large amount of coding and testing time, and greatly improves the efficiency and shortens the cycle when meeting the diverse management requirements of the project, and has a wide adaptability.
[0120] The above are only some embodiments of the present invention. For those of ordinary skill in the art, without departing from the inventive concept of the present invention, several modifications and improvements can still be made, and these all belong to the protection scope of the present invention.
Claims
1. An automated management method for an information model, characterized in that: The following steps are included A: Obtain the object hierarchy and object attributes of the original information model, where the information model is composed of objects, there is a hierarchical relationship between objects, objects have types and attribute sets, and each object type has multiple instances, each instance has a unique identifier; B: Organize the management requirements of the information model, where management requirements include name requirements and hierarchy requirements; C: Convert management requirements into rules and create templates, including converting name requirements into name rules by object type, and converting hierarchy requirements into hierarchy rules by object type; D: Use the information model management automation module to complete the name and level change of the instance; E: Use the name and hierarchy changed in step D to create a changed information model according to the data structure of the original information model; Wherein, step C also includes the following steps S1: Sort out management requirements and prepare data according to the basic method of rule template production; S2: Formulate name rules, where the name rules include object type, instance name, parent management object type, screening conditions, and priority; S3: Formulate hierarchical rules, where the hierarchical rules include object type, direct superior object type, direct superior management node name, direct superior same attribute, screening condition, and priority; Wherein, step D also includes the following steps S4: reading the information model and the management requirement template, and completing the input of the information model management automation module, wherein the input content mainly includes hierarchical data, name rules and hierarchical rules; S5: parse the information model to obtain instance attributes and instance parent attributes; S6: parse the management requirement template to obtain the object attributes required for management; S7: Check the feasibility of the rules and issue a check report if the feasibility is abnormal; S8: Calculate and obtain the instance name; S9: Calculate the instance level; Wherein, step E also includes the following steps S10: Establish a pure management node; S11: Establishing an instance management node; S12: Copy the attributes of the instance in the original information model.
2. The method for automatic management of information models according to claim 1, characterized in that: In S1, the management requirement rule template includes name rules and hierarchical rules. Each rule is formulated according to the object type. The changing content in the rule is expressed using attributes. The attribute representation method is "[object type.attribute index name]". The attribute can use all attributes of the object type and the parent object type in the original information model. The parent object type is the object type of the direct parent and all indirect parents.
3. The method for automatic management of information models according to claim 1, characterized in that: In S4, each item in the hierarchical structure of hierarchical data is a node. The node content is the index name, parent index name, node name, object type, and attribute set, and they are all transformed and generated from the original information model. The set of name rules corresponds to the name rule table of the management requirement template, and the set of hierarchical rules corresponds to the hierarchical rule table of the management requirement template.
4. The method for automatic management of information models according to claim 1, characterized in that: In step S5, the process includes obtaining root node information, filtering instance nodes, and calculating all upper-level object types and upper-level instances of the instance.
5. The method for automatic management of information models according to claim 1, characterized in that: In step S6, the name rule and the level rule are parsed, and the object type and attribute name required for name management and level management are obtained respectively.
6. The method for automatic management of information models according to claim 1, characterized in that: In step S7, including traversing the instance nodes in the hierarchical data, each instance node completes the name rule feasibility calculation, the hierarchical rule feasibility calculation, the hierarchical rule depth check calculation, and generates an inspection report for all exceptions and warnings.
7. The method for automatic management of information models according to claim 1, characterized in that: In step S8, it includes obtaining the name rule used by the instance, obtaining the variable value in the name rule, replacing the changed content in the instance name with the variable value, and maintaining the original name when the value of the name rule is abnormal.
8. The method for automatic management of information models according to claim 1, characterized in that: In step S9, the process includes obtaining the hierarchical rules used by the instance, obtaining the directly superior object instance, obtaining the variable value in the hierarchical rules, replacing the changed content in the directly superior management node name with the variable value, and keeping the fixed value unchanged.
9. The method for automatic management of information models according to claim 1, characterized in that: In step S10, the "direct superior management node name" calculated in step D is used to establish a multi-level management node according to the original information model data structure.
10. The method for automatic management of information models according to claim 1, characterized in that: In step S11, the calculated instance of the direct superior object type is used, and a management node is established according to the original information model data structure, wherein the name of the instance management node is the calculated instance name.
11. The method for automatic management of information models according to claim 1, characterized in that: In step S12, the index name and attribute set in the original information model data structure are copied to the new information model.