Centralized control station model management method and system based on meta-model
By adopting a meta-model-based centralized control station model management method, substation models are automatically created and managed, solving the consistency and interoperability problems in traditional methods, achieving efficient model management and smooth upgrades, and reducing error rates and labor costs.
Patent Information
- Application Number
- CN202511424737.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-09-30
- Publication Date
- 2025-12-30
AI Technical Summary
In traditional substation centralized monitoring systems, model management methods cannot guarantee model consistency and interoperability. Manually adding models is time-consuming, labor-intensive, and prone to errors, and older models cannot be smoothly upgraded.
A meta-model-based centralized control station model management method is adopted. By generating model modification files, new meta-models are automatically created and consistency checks are performed, thereby achieving automated model management and smooth upgrades.
It improves the efficiency of model management, reduces the probability of errors, reduces labor costs, ensures model consistency and interoperability, and supports smooth upgrades of older models.
Smart Images
Figure CN121234603A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of automatic modeling technology for centralized monitoring systems of substations, and in particular to a centralized control station model management method and system based on meta-models. Background Technology
[0002] With the growth of electricity demand, the expansion of power grid, the increase in the number of substations, and the increase in equipment complexity, traditional manual monitoring and decentralized management can no longer meet the needs, and a new generation of substation centralized monitoring systems (central control stations) has emerged.
[0003] Before developing a program, business developers need to abstract the physical model (physical object) of the real world into a digital model that they can use, and then integrate it into a larger system. This is a complex but crucial process.
[0004] Abstracting a physical model of the real world into a digital model for programmers involves multiple steps, including understanding the physical system, building a mathematical model, discretization and digitization, selecting programming tools, implementing the digital model, verification and calibration, integration and application, and continuous optimization. This process requires not only a solid theoretical foundation but also extensive programming experience and engineering practice skills.
[0005] Given the powerful functions, wide range of business areas, and numerous object models of the centralized control station platform, traditional model management methods (such as manually adding object models) can no longer meet the requirements.
[0006] Traditional modeling methods currently suffer from the following problems: The centralized control station platform supports a wide range of applications, and when various applications add models, it is impossible to ensure the consistency and interoperability of the models. Adding models manually is time-consuming, labor-intensive, and prone to errors; Without a checking mechanism, errors during modeling cannot be detected in a timely manner; Older models cannot be smoothly upgraded to newer models. Summary of the Invention
[0007] The purpose of this invention is to solve at least one technical problem in the background art and to provide a centralized control station model management method and system based on meta-model.
[0008] To achieve the above objectives, this invention provides a centralized control station model management method based on a meta-model, comprising: Based on the modeling requirements and in accordance with the rules and structure of the metamodel, a new metamodel is abstracted from the actual physical object. The new metamodel includes attributes, objects and object attributes. Based on the new metamodel and historical metamodel in the centralized control station model management system, a model modification file is generated. The centralized control station model management system loads the model modification file and converts the information of the new metamodel into the corresponding SQL statement. Then, based on the SQL statement, it automatically creates the corresponding new metamodel in the metamodel library, including attributes, objects and object attributes. The system applies the new metamodel created in the metamodel library and checks for errors. If no errors are found, the new metamodel is applied, and a system model is formed based on the applied new metamodel and the previously applied historical metamodels in the metamodel library. The version of the system model is then set. Export the metamodel file of the system model and publish the system model based on the metamodel file; The centralized control station model management system loads historical versions of the meta-model library and newly released system models. Based on the newly released system models, it upgrades the historical versions of the meta-model library to the latest version and makes the changes take effect in real time.
[0009] According to one aspect of the present invention, the model modification file is an Excel file, which records the attributes, objects, and object attributes of the new metamodel and the historical metamodel.
[0010] According to one aspect of the invention, the attributes include: name and data type; The objects include: name, description, level, whether it is a platform model, scope, sorting attribute, grouping mode, icon file, parent object link, and child object link; The object attributes include: name, description, level, data type, scope, object specification, attribute specification, list of matching object types, and attribute type object link.
[0011] According to one aspect of the present invention, the centralized control station model management system traverses the model modification files and compares them with historical meta-models to identify the attributes, objects, and object attributes of the new meta-models. Based on the identified attributes, objects, and object attributes, it generates corresponding SQL statements and then automatically creates new meta-models in the meta-model library based on the SQL statements, including: attributes, objects, and object attributes.
[0012] According to one aspect of the present invention, the execution of the effective operation is as follows: The data structure of the new metamodel created in the metamodel library is synchronized and updated to the physical object instance library. The corresponding objects and object attributes in the physical object instance library are updated according to the data structure of the new metamodel in the metamodel library.
[0013] According to one aspect of the present invention, the verification of whether an error occurs is to verify the consistency of the model, including: whether the names of object attributes are consistent, whether the data types of object attributes are consistent, and whether the parent-child relationship is consistent.
[0014] According to one aspect of the present invention, when upgrading a historical version of the meta-model library based on a newly released system model, a model consistency check is first performed. If the check passes, the upgrade is allowed; if the check fails, the upgrade is not allowed, and the reason for the error is indicated. The model consistency verification includes: whether the number of objects with the same name in the newly released system model is consistent with that in the historical version of the metamodel library; whether the number of attributes with the same name in the newly released system model is consistent with that in the historical version of the metamodel library; and whether the data type of attributes with the same name in the newly released system model is consistent with that in the historical version of the metamodel library.
[0015] To achieve the above objectives, the present invention also provides a centralized control station model management system based on a meta-model, comprising: The model modification file generation module, based on modeling requirements and in accordance with the rules and structure of the metamodel, abstracts a new metamodel from the actual physical object. The new metamodel includes attributes, objects, and object attributes. It generates model modification files based on the new metamodel and historical metamodel in the centralized control station model management system. The new metamodel creation module loads the model modification file from the central control station model management system and converts the information of the new metamodel into corresponding SQL statements. Then, based on the SQL statements, it automatically creates the corresponding new metamodel in the metamodel library, including attributes, objects, and object attributes. The system model formation module performs an activation operation on the new metamodel created in the metamodel library and checks for errors. If no errors are found, the new metamodel is activated, and a system model is formed based on the activated new metamodel and the previously activated historical metamodels in the metamodel library. The version of the system model is then set. The new model release module exports the metamodel file of the system model and releases the system model based on the metamodel file; The historical version model upgrade module loads the historical version metamodel library and the newly released system model into the centralized control station model management system. Based on the newly released system model, it upgrades the historical version metamodel library to the latest version and makes it effective in real time.
[0016] To achieve the above objectives, the present invention also provides an electronic device, including a processor, a memory, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the meta-model-based centralized control station model management method as described above.
[0017] To achieve the above objectives, the present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the meta-model-based centralized control station model management method as described above.
[0018] According to the solution of the present invention, the present invention can automatically create new meta-models and achieve smooth upgrades of old version models (meta-model library). Compared with the traditional manual addition of models, it improves work efficiency, reduces the probability of errors, and reduces labor costs, and has important practical value and application prospects. Attached Figure Description
[0019] Figure 1 The flowchart schematically illustrates a centralized control station model management method based on a meta-model according to an embodiment of the present invention. Detailed Implementation
[0020] The invention will now be discussed with reference to exemplary embodiments. It should be understood that the described embodiments are merely intended to enable those skilled in the art to better understand and thus implement the invention, and are not intended to imply any limitation on the scope of the invention.
[0021] As used herein, the term "comprising" and its variations are to be interpreted as open-ended terms meaning "including but not limited to". The term "based on" is to be interpreted as "at least partially based on". The terms "one embodiment" and "an embodiment" are to be interpreted as "at least one embodiment".
[0022] Figure 1 The flowchart schematically illustrates a centralized control station model management method based on a meta-model according to an embodiment of the present invention. Figure 1 As shown, in this embodiment, the centralized control station model management method based on metamodel includes: Based on the modeling requirements (based on business requirements), and in accordance with the rules and structure of the metamodel, a new metamodel is abstracted from the actual physical objects. The new metamodel includes attributes, objects, and object attributes. Based on the new metamodel and historical metamodel (the metamodel that has already taken effect in the metamodel library) in the centralized control station model management system, a model modification file is generated. The centralized control station model management system loads the model modification file and converts the information of the new metamodel into the corresponding SQL statement. Then, based on the SQL statement, it automatically creates the corresponding new metamodel in the metamodel library, including attributes, objects and object attributes. The system applies the new metamodel created in the metamodel library and checks for errors. If no errors are found, the new metamodel is applied, and a system model is formed based on the applied new metamodel and the previously applied historical metamodels in the metamodel library. The version of the system model is then set. Export the metamodel file of the system model and publish the system model based on the metamodel file; The centralized control station model management system loads historical versions of the meta-model library and newly released system models. Based on the newly released system models, it upgrades the historical versions of the meta-model library to the latest version and makes it effective in real time (the historical versions of the meta-model library are other centralized control station systems that are already in operation, and it is necessary to upgrade the historical version model library of each project site to the new version).
[0023] It's important to note that a metamodel is a language or framework for describing models. It defines the rules and structure for creating models, representing a higher level of abstraction—a model of models. The metamodel is central to model-driven development and domain-specific modeling, significantly improving modeling efficiency and system quality by providing a higher level of abstraction and a standardized framework. Through the metamodel, developers can focus on business logic rather than technical details; it ensures model consistency and interoperability; and it supports automated tools such as code generation and model transformation.
[0024] Furthermore, according to one embodiment of the present invention, the model modification file is an Excel file, which records the attributes, objects, and object attributes of the new metamodel and the historical metamodel. The generated model modification file needs to be clearly marked as belonging to either the platform model or the application model. The platform model is used to construct the most basic functional architecture of the centralized control system; the application model is used for various advanced applications.
[0025] Furthermore, according to one embodiment of the present invention, the attributes include: name and data type; The objects include: name, description, level, whether it is a platform model, scope, sorting attribute, grouping mode, icon file, parent object link, and child object link; Object properties include: name, description, level, data type, scope, object specification, property specification, list of matching object types, and property type object link.
[0026] In this implementation, the "name" of an attribute is mapped from a certain element of a physical device in the real world; the "data type" of the attribute includes Boolean, Short, Long, LongLong, Float, String, Link, Time, Container, Choice, File, etc. When designing the model, the data type of the attribute is determined according to business needs.
[0027] Furthermore, the object's "Name" is mapped from the name of the physical device in the real world; the "Description" is used to fill in the object's descriptive information; the "Level" is the object's unique identifier; different objects in the same model library have different levels, and objects with the same level number should be the same in different model libraries; "Whether it's a platform model" is used to mark whether the model belongs to a general platform model or a specific application model; "Scope" is used to mark whether the object is visible in configuration mode or both configuration and real-time modes; "Sorting attribute" is used to mark which attribute is used to sort the object; in the object instance library, when there are multiple object instances of an object type, they are sorted by attribute values from smallest to largest; "Grouping mode" allows users to choose between grouping and not grouping, facilitating switching between different browsing habits; "Icon file" is used to associate the icon displayed when the object is visualized; "Parent object link" is used to define which objects can be attached to this object; "Child object link" is used to define which objects can be attached to this object; all of the above should be explicitly defined in the model modification file.
[0028] Furthermore, the "Name" of an object attribute is mapped from the name of a physical device in the real world; the "Description" is used to fill in the descriptive information of the object attribute; the "Level" is a unique identifier for the object attribute, and different object attributes have different levels within the same object; the "Data Type" includes Boolean, Short, Long, LongLong, Float, String, Link, Time, Container, Choice, File, etc., and the data type of the object attribute should be determined according to business needs when designing the model; the "Scope" is used to indicate whether the object attribute is visible in the configuration state or both the configuration state and the real state; the "Matching Object Type List" is used for object attributes with the data type Link to specify the object types that can be associated; the "Attribute Type Object Link" is used to associate attributes, and the name and data type of the associated attribute must be consistent with the name and data type of the object attribute, otherwise an error will occur during subsequent consistency checks, and the model will not take effect.
[0029] Furthermore, according to one embodiment of the present invention, the centralized control station model management system traverses the model modification files and compares them with historical meta-models to identify the attributes, objects, and object attributes of the new meta-model. Based on the identified attributes, objects, and object attributes, it generates corresponding SQL statements and then automatically creates corresponding new meta-models in the meta-model library based on the SQL statements, including: attributes, objects, and object attributes.
[0030] Furthermore, according to one embodiment of the present invention, the activation operation is performed as follows: The data structure of the new metamodel created in the metamodel library is synchronized and updated to the physical object instance library. The corresponding objects and object attributes in the physical object instance library are updated according to the data structure of the new metamodel in the metamodel library.
[0031] Furthermore, according to one embodiment of the present invention, the verification of whether an error occurs is to verify the consistency of the model, including: whether the names of object attributes are consistent, whether the data types of object attributes are consistent, and whether the parent-child relationship is consistent.
[0032] Furthermore, according to one embodiment of the present invention, after the model activation operation is successful, the model version needs to be set. The version number is a 6-digit number, where the first 4 digits represent the platform model version and the last 2 digits represent the application model version. Each time the model is modified, the corresponding version number is incremented by 1. When upgrading older versions of the model, the model version number is compared first, allowing only older versions to upgrade to the new version, and disallowing new versions to revert to older versions.
[0033] After the model version is set, the system model is released. Depending on the application scenario, you can choose to release the platform model or the application model separately, or you can release both the platform model and the application model simultaneously. When upgrading the model version of older control stations, you can choose to upgrade either the platform model or the application model separately, or you can upgrade both the platform model and the application model simultaneously, depending on the application scenario. Specifically, the control system uses a platform + application architecture. One platform supports multiple applications, such as power grid applications, power plant applications, rail transit applications, and hydropower applications. If the platform model is upgraded, all application systems must upgrade their models; if the power grid application model is upgraded, only the power grid application system needs to upgrade its model, while other application systems do not need to upgrade their models.
[0034] Furthermore, according to one embodiment of the present invention, when upgrading the metamodel library of a historical version (old version) based on the newly released system model, a model consistency check is first performed. If the check passes, the upgrade is allowed; if the check fails, the upgrade is not allowed, and the reason for the error is indicated to facilitate troubleshooting. Model consistency verification includes: whether the numbering of objects with the same name in the newly released system model is consistent with that in the historical version of the metamodel library; whether the numbering of attributes with the same name in the newly released system model is consistent with that in the historical version of the metamodel library; and whether the data type of attributes with the same name in the newly released system model is consistent with that in the historical version of the metamodel library.
[0035] Furthermore, according to one embodiment of the present invention, after the old version of the metamodel library is upgraded, the newly added model (new metamodel) takes effect in real time, the newly added object and object attributes are updated to the object instance library in real time, and the application can load the newly added object and object attributes in real time to realize the new functions of the central control station system without restarting the system.
[0036] According to the above-described solution of the present invention, the present invention can automatically create new meta-models and achieve smooth upgrades of old version models (meta-model library). Compared with the traditional manual addition of models, it improves work efficiency, reduces the probability of errors, and reduces labor costs, and has important practical value and application prospects.
[0037] Furthermore, to achieve the above objectives, the present invention also provides a centralized control station model management system based on a meta-model, comprising: The model modification file generation module, based on modeling requirements and in accordance with the rules and structure of the metamodel, abstracts a new metamodel from the actual physical object. The new metamodel includes attributes, objects, and object attributes. It generates model modification files based on the new metamodel and historical metamodel in the centralized control station model management system. The new metamodel creation module loads the model modification file from the central control station model management system and converts the information of the new metamodel into corresponding SQL statements. Then, based on the SQL statements, it automatically creates the corresponding new metamodel in the metamodel library, including attributes, objects, and object attributes. The system model formation module performs an activation operation on the new metamodel created in the metamodel library and checks for errors. If no errors are found, the new metamodel is activated, and a system model is formed based on the activated new metamodel and the previously activated historical metamodels in the metamodel library. The version of the system model is then set. The new model release module exports the metamodel file of the system model and releases the system model based on the metamodel file; The historical version model upgrade module loads the historical version metamodel library and the newly released system model into the centralized control station model management system. Based on the newly released system model, it upgrades the historical version metamodel library to the latest version and makes it effective in real time.
[0038] Furthermore, according to one embodiment of the present invention, the model modification file is an Excel file, which records the attributes, objects, and object attributes of the new metamodel and the historical metamodel. The generated model modification file needs to be clearly marked as belonging to the platform model or the application model.
[0039] Furthermore, according to one embodiment of the present invention, the attributes include: name and data type; The objects include: name, description, level, whether it is a platform model, scope, sorting attribute, grouping mode, icon file, parent object link, and child object link; Object properties include: name, description, level, data type, scope, object specification, property specification, list of matching object types, and property type object link.
[0040] In this implementation, the "name" of an attribute is mapped from a certain element of a physical device in the real world; the "data type" of the attribute includes Boolean, Short, Long, LongLong, Float, String, Link, Time, Container, Choice, File, etc. When designing the model, the data type of the attribute is determined according to business needs.
[0041] Furthermore, the object's "Name" is mapped from the name of the physical device in the real world; the "Description" is used to fill in the object's descriptive information; the "Level" is the object's unique identifier; different objects in the same model library have different levels, and objects with the same level number should be the same in different model libraries; "Whether it's a platform model" is used to mark whether the model belongs to a general platform model or a specific application model; "Scope" is used to mark whether the object is visible in configuration mode or both configuration and real-time modes; "Sorting attribute" is used to mark which attribute is used to sort the object; in the object instance library, when there are multiple object instances of an object type, they are sorted by attribute values from smallest to largest; "Grouping mode" allows users to choose between grouping and not grouping, facilitating switching between different browsing habits; "Icon file" is used to associate the icon displayed when the object is visualized; "Parent object link" is used to define which objects can be attached to this object; "Child object link" is used to define which objects can be attached to this object; all of the above should be explicitly defined in the model modification file.
[0042] Furthermore, the "Name" of an object attribute is mapped from the name of a physical device in the real world; the "Description" is used to fill in the descriptive information of the object attribute; the "Level" is a unique identifier for the object attribute, and different object attributes have different levels within the same object; the "Data Type" includes Boolean, Short, Long, LongLong, Float, String, Link, Time, Container, Choice, File, etc., and the data type of the object attribute should be determined according to business needs when designing the model; the "Scope" is used to indicate whether the object attribute is visible in the configuration state or both the configuration state and the real state; the "Matching Object Type List" is used for object attributes with the data type Link to specify the object types that can be associated; the "Attribute Type Object Link" is used to associate attributes, and the name and data type of the associated attribute must be consistent with the name and data type of the object attribute, otherwise an error will occur during subsequent consistency checks, and the model will not take effect.
[0043] Furthermore, according to one embodiment of the present invention, the centralized control station model management system traverses the model modification files and compares them with historical meta-models to identify the attributes, objects, and object attributes of the new meta-model. Based on the identified attributes, objects, and object attributes, it generates corresponding SQL statements and then automatically creates corresponding new meta-models in the meta-model library based on the SQL statements, including: attributes, objects, and object attributes.
[0044] Furthermore, according to one embodiment of the present invention, the activation operation is performed as follows: The data structure of the new metamodel created in the metamodel library is synchronized and updated to the physical object instance library. The corresponding objects and object attributes in the physical object instance library are updated according to the data structure of the new metamodel in the metamodel library.
[0045] Furthermore, according to one embodiment of the present invention, verifying whether an error occurs is to verify the consistency of the model, including: whether the attribute type of the object attribute and the name of the linked attribute are consistent, whether the data type of the object attribute and the linked attribute are consistent, and whether the parent-child relationship is correct.
[0046] Furthermore, according to one embodiment of the present invention, after the model activation operation is successful, the model version needs to be set. The version number is a 6-digit number, where the first 4 digits represent the platform model version and the last 2 digits represent the application model version. Each time the model is modified, the corresponding version number is incremented by 1. When upgrading older versions of the model, the model version number is compared first, allowing only older versions to upgrade to the new version, and disallowing new versions to revert to older versions.
[0047] After setting the model version, the system model is released. Depending on the application scenario, you can choose to release the platform model or the application model separately, or you can choose to release both the platform model and the application model simultaneously. When upgrading the model version of a central control station with an older model version, you can choose to upgrade the platform model or the application model separately, or you can choose to upgrade both the platform model and the application model simultaneously, depending on the application scenario.
[0048] Furthermore, according to one embodiment of the present invention, when upgrading the metamodel library of a historical version (old version) based on the newly released system model, a model consistency check is first performed. If the check passes, the upgrade is allowed; if the check fails, the upgrade is not allowed, and the reason for the error is indicated to facilitate troubleshooting. Model consistency verification includes: whether the numbering of objects with the same name in the newly released system model is consistent with that in the historical version of the metamodel library; whether the numbering of attributes with the same name in the newly released system model is consistent with that in the historical version of the metamodel library; and whether the data type of attributes with the same name in the newly released system model is consistent with that in the historical version of the metamodel library.
[0049] Furthermore, according to one embodiment of the present invention, after the old version of the metamodel library is upgraded, the newly added model (new metamodel) takes effect in real time, the newly added object and object attributes are updated to the object instance library in real time, and the application can load the newly added object and object attributes in real time to realize the new functions of the central control station system without restarting the system.
[0050] According to the above-described solution of the present invention, the present invention can automatically create new meta-models and achieve smooth upgrades of old version models (meta-model library). Compared with the traditional manual addition of models, it improves work efficiency, reduces the probability of errors, and reduces labor costs, and has important practical value and application prospects.
[0051] Furthermore, to achieve the above objectives, the present invention also provides an electronic device, including a processor, a memory, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the meta-model-based centralized control station model management method as described above.
[0052] Furthermore, to achieve the above objectives, the present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the meta-model-based centralized control station model management method described above.
[0053] Those skilled in the art will recognize that the modules and algorithm steps described in conjunction with the embodiments disclosed herein can be implemented using electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.
[0054] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the above-described apparatus and equipment can be referred to the corresponding process in the foregoing method implementation, and will not be repeated here.
[0055] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.
[0056] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the objectives of the embodiments of the present invention, depending on actual needs.
[0057] In addition, the functional modules in the embodiments of the present invention can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module.
[0058] If the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the sending / receiving methods of various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.
[0059] The above description is merely a preferred embodiment of this application and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in this application is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the inventive concept. For example, technical solutions formed by substituting the above-described features with (but not limited to) technical features with similar functions disclosed in this application.
[0060] It should be understood that the sequence number of each step in the invention and its embodiments does not absolutely imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.
Claims
1. A meta-model based centralized station model management method, characterized in that, Comprise: According to the modeling requirements, the new meta-model is abstracted from the actual physical object according to the rules and structure of the meta-model, the new meta-model includes attributes, objects and object attributes, and the model modification file is generated based on the new meta-model and the historical meta-model in the centralized station model management system; The centralized station model management system loads the model modification file and converts the information of the new meta-model in the model modification file into corresponding sql statements, and then automatically creates the corresponding new meta-model in the meta-model library, including attributes, objects and object attributes; The new meta-model created in the meta-model library is executed to take effect, and whether an error occurs is checked, the new meta-model is taken effect when no error occurs, and the system model is formed based on the new meta-model taken effect and the historical meta-model in the meta-model library, and the version of the system model is set; The meta-model file of the system model is exported, and the system model is published based on the meta-model file; The centralized station model management system loads the historical version of the meta-model library and the newly published system model, upgrades the historical version of the meta-model library to the latest version based on the newly published system model, and takes effect in real time.
2. The meta-model based control center model management method according to claim 1, characterized in that, The model modification file is an excel file, which records the attributes, objects and object attributes of the new meta-model and the historical meta-model.
3. The meta-model based control center model management method according to claim 1, characterized in that, The attributes include: name, data type; The objects include: name, description, level, whether platform model, range, sorting attribute, grouping mode, icon file, parent object link, child object link; The object attributes include: name, description, level, data type, range, object specification, attribute specification, matching object type list, attribute type object link.
4. The meta-model based control center model management method according to claim 1, characterized in that, The centralized station model management system traverses the model modification file and compares it with the historical meta-model to identify the attributes, objects and object attributes of the new meta-model, generates corresponding sql statements based on the identified attributes, objects and object attributes, and then automatically creates the new meta-model in the meta-model library, including: attributes, objects and object attributes.
5. The meta-model based control center model management method according to claim 1, characterized in that, The execution of the effect operation is: The data structure of the new meta-model created in the meta-model library is synchronously updated to the physical object instance library, and the corresponding objects and object attributes in the physical object instance library are updated according to the data structure of the corresponding new meta-model in the meta-model library.
6. The meta-model based control center model management method according to claim 1, characterized in that, The check whether an error occurs is to check the consistency of the model, including: whether the object attribute and the attribute name are consistent, whether the object attribute and the attribute data type are consistent, and whether the parent-child relationship is consistent.
7. The meta-model based control center model management method according to any one of claims 1 to 6, characterized in that, When the historical version of the meta-model library is upgraded based on the newly published system model, the model consistency check is performed first, the upgrade is allowed if the check is passed, and the upgrade is not allowed if the check fails, and the error reason is prompted; The model consistency check includes: whether the numbers of the same name objects in the newly published system model and the historical version of the meta-model library are consistent, whether the numbers of the same name attributes in the newly published system model and the historical version of the meta-model library are consistent, and whether the data types of the same name attributes in the newly published system model and the historical version of the meta-model library are consistent.
8. A meta-model based control center model management system, characterized by Comprise: The model modification file generation module abstracts a new meta model from the actual physical object according to the rules and structure of the meta model based on the modeling requirements, the new meta model including attributes, objects and object attributes, and generates a model modification file based on the new meta model and the historical meta model in the centralized station model management system; The new meta model creation module loads the model modification file and converts information of the new meta model in the model modification file into corresponding sql statements, and then automatically creates a corresponding new meta model in the meta model library based on the sql statements, including attributes, objects and object attributes; The system model formation module performs an effective operation on the new meta model created in the meta model library, and checks whether an error occurs, and if no error occurs, the new meta model is effective, and a system model is formed based on the effective new meta model and the historical meta model in the meta model library which has been effective, and the version of the system model is set; The new model publishing module exports a meta model file of the system model, and publishes the system model based on the meta model file; The historical version model upgrade module loads the historical version meta model library and the newly published system model, upgrades the historical version meta model library to the latest version based on the newly published system model, and makes it effective in real time.
9. An electronic device, characterized by The computer readable storage medium stores a computer program, and the computer program is executed by the processor to implement the meta model based centralized station model management method according to any one of claims 1-7.
10. A computer readable storage medium, characterized in that, The computer readable storage medium stores a computer program, and the computer program is executed by the processor to implement the meta model based centralized station model management method according to any one of claims 1-7.