Data acquisition visualization configuration tool for EMS site

Abstract

The invention relates to a data acquisition visualization configuration tool for an EMS site. The method is suitable for the technical field of EMS energy storage and related Internet of Things data acquisition. According to the technical scheme, a site project configuration tool, a site data page making tool and a site data page display tool are included; the site project configuration tool comprises an acquisition protocol management unit which is used for configuring data acquisition protocols of various devices on an EMS site; the equipment configuration management is used for configuring point locations of information acquisition of all equipment on the sites, visual appearances of the equipment and animation processes of the equipment during data acquisition; the alarm type management module is used for defining the grade of each alarm type, the content of alarm information and the corresponding format for each device on the site; the site data page making tool comprises a visual design module which is used for building a data display page based on basic primitives of each device; an attribute setting module; a process design module; and a site data page display module.

Description

Technical Field

[0001] The present invention relates to a data acquisition visualization configuration tool for EMS sites, and is applicable to the fields of EMS energy storage and related Internet of Things data acquisition. Background Art

[0002] With the rapid development of China's new energy industry, the application of the EMS system (Energy Management System) in the field of energy management is becoming more and more extensive. Tools for monitoring the operation data of hardware devices and visualization are important parts of the EMS system.

[0003] In the energy industry, traditional equipment operation monitoring and data visualization tools are regarded as three independent functional processing modules in terms of equipment information acquisition, point information organization, and data visualization appearance. In page production, the appearance of equipment data is regarded as individual independent graphic elements. This process-based design based on functions results in the separation of device-related data, behavior, and appearance, and it is impossible to form modular encapsulation and design based on the concept of devices. In large-scale engineering projects, a large number of devices with the same model and similar point names bring many problems to data management in the project, data display in page production, and user behavior interaction, and also bring great limitations to subsequent function expansion. Summary of the Invention

[0004] The technical problem to be solved by the present invention is: in view of the above problems, to provide a data acquisition visualization configuration tool for EMS sites.

[0005] The technical solution adopted by the present invention is: a data acquisition visualization configuration tool for EMS sites, including a site project configuration tool, a site data page production tool, and a site data page display tool; The site project configuration tool includes: Collection protocol management, used to configure the data collection protocols of various devices on the EMS site; Device configuration management, used to configure the points of the collection information of each device on the site, the visual appearance of the device, and the animation process of the device when collecting data; Alarm type management module, used to define the levels of various alarm types, the content of alarm information, and the corresponding formats for each device on the site; The site data page production tool includes: Visualization design module, used to build a data display page based on the basic graphic elements of each device. The basic graphic elements of the device are associated with the data collection protocol corresponding to the device, the points of the collection information, the visual appearance of the device, the animation process of the device when collecting data, and the alarm type; An attribute setting module, which is used to configure the display content and display attributes of basic graphic elements in the data display page, as well as the physical device address ports of device configuration. A process design module, which is used to configure the interaction behavior between the basic graphic elements and users in the data display page, and this interaction behavior configuration is carried out based on the visual description of the functional process. The site data page display module is used to display the data display page made by the site data page production tool, to listen for the trigger sources of the interaction behaviors of each basic graphic element in the data display page, and to perform interactive display based on the preset interaction behaviors when the trigger sources are monitored.

[0006] The site project configuration tool further includes: A database management module, which is used to implement the functions of storing real-time data collected on the site, storing device alarm information, and querying edit history data and performing SQL script functions for report statistics.

[0007] The site project configuration tool further includes: A front-end machine management module, which is used to support data collection in the way of relaying through the front-end machine.

[0008] The site data page display module includes: A page rendering module, which is used to load the data display page and the basic graphic elements and device configuration information in the page, to control the basic graphic elements to display corresponding content and render corresponding appearances according to the preset display attributes, to control the device configuration to connect to physical devices and collect physical signals of devices using the preset device ports and protocols, and to convert them into final content according to the expressions bound in the configuration, and the device configuration displays corresponding content and renders corresponding appearances using the preset display attributes. A trigger engine module, which is used to load the interaction processes defined in the basic graphic elements during user operations and the animations executed during data collection defined in the configuration, to set the listening of corresponding interaction signals or events according to the graphic element interaction requirements, to set corresponding point interceptors during configuration data collection according to the configuration animation requirements, and to sequentially execute one or more Action operations set in the interaction process after corresponding event signals are monitored during the user interaction process.

[0009] The site data page display module further includes: A script execution engine module, which is used to provide a special type of Action for the trigger engine module, and this type of Action can provide the function for users to write additional scripts.

[0010] A data acquisition visualization configuration method for an EMS site, which is based on the data acquisition visualization configuration tool described above, includes: Based on the site project configuration tool, configure the data acquisition protocol, acquisition information points, visual appearance of devices, animation process during data acquisition, and alarm types of each device on the EMS site to form the basic primitives of each device. Using the site data page production tool, build a data display page based on the basic primitives of the device, and configure the display content, display attributes, physical device address ports of the device configuration, and the interaction behavior between the basic primitive and the user in the data display page based on the site data page production tool. Based on the site data page display module, display the data display page produced by the site data page production tool; listen to the trigger sources of the interaction behaviors of each basic primitive in the data display page, and judge whether to trigger based on the trigger source combined with a preset expression, and display the corresponding interaction content after the judgment triggers.

[0011] The beneficial effects of the present invention are as follows: The present invention adopts a configuration-oriented design concept and fully implements the three stages of site project configuration, data page production, and data page display. For the problem of the separation of data, behavior, and appearance, it encapsulates the acquisition protocol, device points, data visualization, and alarm types with the concept of device configuration. For the problem of displaying large-scale device data, it uses a configuration-oriented visualization design method to build the data display page in a modular way. For the complex user interaction behaviors in the page, it uses trigger-action to listen to the device configuration event signals and intercept the data update operations and execute the corresponding Action operations on the behavior and animation of the device configuration.

[0012] The present invention solves the problem that it is difficult for engineering personnel to distinguish similar points during the process of data management, data page production and display, and user behavior interaction in large-scale engineering projects in the energy industry with a large number of devices of the same model and similar point names, and solves the problem that it is easy to be restricted in the expansion of point data in subsequent engineering projects; it solves the problems of low update efficiency of millions of point data and the customization of data update strategies and data rendering by engineering personnel. Brief Description of the Drawings

[0013] Figure 1 It is a structural block diagram of the data acquisition visualization configuration tool in the embodiment.

[0014] Figure 2 It is a logical relationship diagram of the site data page production tool, page display tool and trigger-action framework in the embodiment.

[0015] Figure 3 It is an architecture structure diagram of the trigger-action framework in the embodiment. Detailed Embodiments

[0016] To better understand the technical solution of this application, the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0017] It should be clear that the described embodiments are only a part of the embodiments of this application, rather than all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in this application without creative efforts belong to the scope of protection of this application.

[0018] The terms used in the embodiments of this application are only for the purpose of describing specific embodiments and are not intended to limit this application. The singular forms "a", "the", and "said" used in the embodiments of this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0019] Embodiment 1: This embodiment provides a data acquisition visualization configuration tool for an EMS site. The visualization configuration tool includes a site project configuration tool, a site data page production tool, a site data page display tool, etc.

[0020] In this embodiment, the site project configuration tool is used to collect basic data such as protocol management, device configuration, and device alarm type settings. The site data page production tool uses the device configuration and basic primitives in the project configuration to visually construct the data display page of the site. The site data page display tool is used to load the page and execute device configuration connection, collect the physical signals of the device, and visualize its own data.

[0021] In this example, the site project configuration tool mainly includes a collection protocol management module, a device configuration management module, an alarm type management module, a database management module, a front-end machine management module, etc.

[0022] In this embodiment, the collection protocol management module is used to configure the protocols for collecting device data on the EMS site, such as Modbus, ICE103 / 104, ICE61850 protocols, etc.

[0023] In this example, the device configuration management module is used to configure the points for collecting information of each device on the site, the visual appearance of the device data, the animation process when the device collects data, and the text information output when the device alarms.

[0024] The alarm type management module is used to define the levels of various alarm types, the content of the alarm information, and the corresponding formats for each device on the site.

[0025] In this embodiment, the database management module is used to provide functions for storing real-time data collected on the site, storing device alarm information, and editing SQL scripts for querying historical data and generating reports. The edited SQL statements will be used as data sources for report controls, providing functions for querying historical data and summarizing data statistics in the site data page production and display tool.

[0026] In this embodiment, the front-end management module is used to support data collection through the front-end transfer method. The transfer protocol supports common communication protocols such as MQTT, HTTP, and WEBSOCKET, and can interface with common IoT gateway data collection devices on the market.

[0027] In this embodiment, the device configuration management adopts a configuration-oriented method to manage the protocols, data points, alarm information, and visual appearance of custom data of the collection devices. Taking the device as a unit, the same type of devices in the engineering project are configured and abstracted, and their collection protocols, point data, data visualization, and alarm types are modeled and encapsulated with the idea of configuration. The data appearance customizes the configuration presentation style in the form of primitive combinations, configures the association between data points and primitive attributes using an attribute editor, and realizes the effect of controlling primitive animations during configuration data collection with the "Graphics View" drawing framework of Qt.

[0028] In this embodiment, the site data page production tool includes a visual design module, an attribute setting module, and a process design module.

[0029] In this example, the visual design module adopts a configuration-oriented visual design method, using device configurations and basic primitives as "building blocks" to build data display pages in a what-you-see-is-what-you-get manner. The visual design module includes basic primitives, device configurations, report controls, page whiteboards, etc. Users first create a blank page, and then drag and drop primitives onto the page in a what-you-see-is-what-you-get manner to build a basic schematic diagram. They can also drag and drop device configurations onto the page and combine them with basic primitives to create complex graphical interfaces. Users can also create multiple pages in this way and plan each device configuration to different pages for display according to the engineering classification requirements.

[0030] In this embodiment, the attribute setting module is used to set the display content and display attributes of the graphic elements that have been dragged and dropped onto the page using an attribute editor. When the page is loaded by the site data page display tool, the corresponding content and appearance will be displayed according to the pre-set attributes. For the device configuration that has been dragged and dropped onto the page, the user can also configure the physical device address ports for configuration collection, set the content and display attributes of the internal graphic elements of the configuration, and bind the expression between the internal graphic element content and the points. When the page is displayed, the device configuration will display the corresponding content and the corresponding appearance using the pre-set attributes, collect the device physical signals according to the device address ports configured in the device configuration, and convert them into the corresponding content for display according to the expressions bound in the configuration.

[0031] In this embodiment, the process design module is used for the user to define the interaction behavior between the graphic elements that have been dragged and dropped onto the page and the user during page display using a trigger editor. This behavior can be visually described using a functional process.

[0032] The following uses a specific example to illustrate the interaction behavior between the graphic elements and the user during page display. This behavior can be visually described using a functional process: Suppose there is a rectangular graphic with a blue background on the page. When the page is displayed, it is desired that when the user moves the mouse over it, the rectangle with the blue background changes to a red background, and when the user presses the left mouse button, the red background changes to a green background again. According to the above interaction requirements, engineers can define two interaction processes in the trigger editor, one is the interaction process triggered when the mouse enters, and the other is the interaction process triggered when the left mouse button is pressed.

[0033] For the device configuration that has been dragged and dropped onto the page, in addition to being able to define the interaction behavior between the internal graphic elements of the configuration and the user during page display using the trigger editor, engineers can also define a series of animation behaviors during the process of the configuration collecting device physical signals. Suppose there is a battery device configuration on the page. When the battery device is in the charging state, the battery configuration displays a battery charging animation, and when the battery device is in the discharging state, the battery configuration displays a battery discharging animation. According to the above animation requirements, engineers can define two animation processes in the trigger editor. One is the discharging animation process triggered by the point data when the battery configuration collects the battery discharging state, and the other is the charging animation process triggered by the point data when the battery configuration collects the battery charging state. The two animation processes may have the same data points collected by the device configuration, but the corresponding conditions when the point data is triggered are different.

[0034] In this example, the process design module visually defines the interaction behavior between the graphic elements and the user in the page display through the trigger-action editor. Specifically, the trigger-action framework is used to sequentially configure the trigger source triggered by the graphic element signal or event and the action chain that responds to the graphic element interaction in the trigger editor, and the process of the interaction between the graphic element and the user is displayed in the form of a flow chart.

[0035] In this embodiment, the trigger-action framework mainly includes two parts: "the API interface / JS debugging tool of the framework" and the "trigger-response engine". Among them, the API interface and the JS debugging tool provide the configuration interface for the configuration interaction behavior design and the execution interface for the configuration display; the trigger-response engine includes a series of trigger modules, animation modules, and auxiliary plugin modules, etc. In the production of the data page, the trigger-response process can be added to the framework for its device configuration through the API interface of the framework. In the data page display, the trigger-response engine listens to the device configuration signal events or intercepts the data update operations according to the type of the trigger and executes the corresponding Action to operate the interaction behavior and animation process of the device configuration.

[0036] In terms of design, the configured trigger-action framework uses the QT6.5.2 version project development tool and divides the developed configured trigger-action framework into three technical architecture routes: the development interface layer, the trigger-response layer, and the execution engine layer. Among them, the development interface layer defines the warning, page, point, and control API interfaces of the plugin. The basic graphic elements or configuration classes implement the interfaces defined by the framework in an inherited manner. The functions of the trigger-action framework are used through these interfaces in the data page production tool or the data page display tool; the trigger-response layer realizes the trigger-response rule pairing by defining various types of triggers to listen to the device configuration signal events or intercept the data operations and by implementing the configuration of the trigger-response mechanism and the corresponding action behaviors; the execution engine layer realizes the parameter transfer from the trigger to the response and the preparation of the context execution environment and completes the execution of the process from the trigger to the response.

[0037] Implementation details of trigger-response: All basic graphic elements or configurations inherit the base class interface (plugin) specified by the framework and implement the functions specified in the base class. The framework obtains the attributes and events exposed by the plugin through the base class interface and realizes the triggering of plugin data, events, and signals through methods such as application interception and listening.

[0038] Implementation details of the execution engine: It uses the built-in Script engine of QT and supports Mqtt, WebSocket, and Ajax communications. It has built-in global variables such as timers and point data. The framework injects the page and plugin objects such as graphics elements and device configurations in the page into the engine execution environment in the form of an execution context. After the trigger is captured by the trigger, the action behaviors (Actions) in the engine execution process implement the user interaction logic. For example, in the script function, the JS script can control the configuration plugin by setting the properties of the plugin and calling the methods of the plugin to implement the user interaction logic or the data collection animation function.

[0039] In this embodiment, to facilitate the deployment of the data page and the subsequent update and upgrade of the traditional data collection and monitoring software, the data page is displayed in the form of a Web page. This form of page display is restricted by the performance of the browser. Especially when displaying 3D data, it is impossible to fully utilize the hardware acceleration resources, which easily leads to system lag. In this embodiment, the "Graphics View" drawing framework of Qt is used to display the data page. Similar to the HTML description language of the Web page, the XML language is used to describe the data page. In this way, while overcoming the problems of difficult deployment and subsequent update and upgrade of the data page, the data page is still displayed as a local application program, and the OpenGL and other graphics engines can be used to accelerate the 3D data rendering during data display.

[0040] The following is the application of the "Graphics View" drawing framework of Qt in the configuration-oriented visual design. In QT, a basic visual drawing framework is built using scenes, views, and graphics items. The relationship between the three of them is as follows: The QGraphicsScene class provides a drawing scene (Scene). The scene is an abstract container for managing graphics items, providing functions such as adding graphics items to the scene, obtaining the graphics items in the scene, managing the states of the graphics items, and propagating events to the graphics items.

[0041] QGraphicsView provides a drawing view (View). The view is used to display the content in the scene. In principle, a scene can have several views. The view is also used for user interaction and accepts keyboard and mouse events, converting them into scene events, and the scene propagates the events to the graphics items for processing.

[0042] The QGraphicsItem class provides basic graphic components (Item), which are also simply referred to as basic graphics elements. It represents the basic graphic components in a drawing framework, such as Line graphics elements, Ployline graphics elements, Ellipse graphics elements, Rect graphics elements, Image graphics elements, Text graphics elements, group graphics elements, and custom-drawn graphics elements, etc.

[0043] The configuration display appearance is based on the "Graphics View" drawing framework of Qt. Complex configuration appearances are composed of basic graphics primitives provided in the drawing framework, and the trigger-action framework is used to define the interaction behavior between the configuration and the user. The "action behavior" Action provided by the trigger-action framework is used to implement the actions of configuration interaction and the animation of data acquisition.

[0044] The page production tool implements the function of the page whiteboard based on the "Graphics View" drawing framework of Qt. When the user creates a new page on the whiteboard, it is equivalent to creating a drawing scene (Scene) object in the drawing framework. The user drags and drops graphics primitives onto the page in a what-you-see-is-what-you-get manner to construct a basic schematic diagram, which is equivalent to adding graphic components (Items) to the scene object and using the drawing view (View) to display the scene content in real time. When the user drags and drops the device configuration onto the page or combines basic graphics primitives, etc., to create a complex graphical interface, it is equivalent to adding a group graphic primitive to the scene object or combining some basic graphics primitives into a group graphic primitive. In this way, the user can divide multiple scenes according to the engineering requirements, and then organize and plan each device configuration into each page in a grouped form for display within the scene.

[0045] In this embodiment, the site data page display module applies the trigger-action framework in the configuration-user interaction and data acquisition processes. The trigger-action framework mainly includes two parts: the API interface / JS debugging tool of the framework and the trigger-response engine. Among them, the API and JS debugging tools provide the configuration interface for the design of configuration interaction behavior and the execution debugging interface for configuration display; the trigger-response engine includes a series of trigger modules, animation modules, and auxiliary function modules.

[0046] In the production of the data page, the trigger-response process of adding interaction behavior to the device configuration can be achieved through the API interface of the framework. When the data page is displayed, the trigger-response engine listens for device configuration signal events or intercepts data update operations according to the type of trigger, and responds and controls the Action in the process to execute the interaction behavior and animation process of the device configuration.

[0047] In this example, the site data page display module includes a page rendering module, a trigger engine module, and a script execution engine module.

[0048] In this example, the page rendering module is used to first load the data page with the basic graphic elements and device configuration information in the page. Secondly, it controls the basic graphic elements to display the corresponding content and render the corresponding appearance according to the pre-set attributes. It controls the device configuration to connect to physical devices and collect physical signals of the devices using pre-configured device ports and protocols, and converts them into the final content according to the expressions bound in the configuration. The device configuration uses the preset attributes to display the corresponding content and render the corresponding appearance. In this embodiment, the trigger engine module is used to first load the interaction process defined in the graphic elements during user operations and the animations executed during data collection defined in the configuration. Secondly, it sets the listening of corresponding interaction signals or events according to the graphic element interaction requirements, and sets the corresponding point interceptors during configuration data collection according to the configuration animation requirements. Then, when a corresponding event signal is monitored during the user interaction process, one or more Action operations set in the interaction process are sequentially executed. When corresponding point data updates are intercepted during the data collection process, one or more Action operations set in the configuration execution process are sequentially executed (here, Action generally refers to operations such as acquisition animations).

[0049] In this embodiment, the script execution engine module provides a special type of Action for the trigger engine module (several types of Action are predefined in the trigger engine module. For example, script Action and animation Action are two of them. Multiple Action can be set in a trigger workflow, and these Action will be sequentially executed during the trigger process). This type of Action can provide the function for users to write additional scripts. When the script Action is run during the trigger process, the script code of the script Action is executed through the JavaScript engine. In this way, the script Action can not only control the graphic element attributes through JavaScript but also communicate with external servers or interact with databases with the help of plugins. In addition, the script execution engine module not only provides the environment for script execution including the corresponding plugin functions but also provides the function for script code debugging.

[0050] Embodiment 2: This embodiment is a data collection visualization configuration method for an EMS site. This method is implemented based on the data collection visualization configuration tool in Embodiment 1 and specifically includes the following steps: Based on the site project configuration tool, configure the data collection protocols, collection information points, visual appearances of devices, animation processes of devices during data collection, and alarm types for each device on the EMS site to form the basic graphic elements of each device. Using the site data page production tool, build a data display page based on the basic primitives of the device, and configure the display content, display attributes, physical device address ports of the device configuration, and the interaction behavior between the basic primitives and the user in the data display page based on the site data page production tool; Based on the site data page display module, display the data display page produced by the site data page production tool; listen to the trigger sources of the interaction behaviors of each basic primitive in the data display page, and judge whether to trigger based on the trigger sources combined with the preset expressions corresponding to the basic primitive, and display the corresponding interaction content after the judgment of triggering.

Claims

1. A data acquisition visualization configuration tool for EMS sites, characterized in that: It includes a site project configuration tool, a site data page production tool, and a site data page display tool; The site project configuration tool includes: Collection protocol management, which is used to configure the data collection protocols of various devices on the EMS site; Device configuration management, which is used to configure the points for collecting information of each device on the site, the visual appearance of the device, and the animation process of the device when collecting data; Alarm type management module, which is used to define the levels of various alarm types, the content of alarm information, and the corresponding formats for each device on the site; The site data page production tool includes: Visual design module, which is used to build a data display page based on the basic primitives of each device. The basic primitives of the device are associated with the corresponding data collection protocol, the points for collecting information, the visual appearance of the device, the animation process of the device when collecting data, and the alarm type; Attribute setting module, which is used to configure the display content and display attributes of the basic primitives in the data display page, and the physical device address ports of the device configuration; Process design module, which is used to configure the interaction behavior between the basic primitives in the data display page and the user. This interaction behavior configuration is carried out based on the visual description of the functional process; The site data page display module is used to display the data display page produced by the site data page production tool, to monitor the trigger sources of the interaction behaviors of each basic primitive in the data display page, and to display the corresponding interaction content based on the preset interaction behaviors when the trigger sources are monitored.

2. The data acquisition visualization configuration tool for an EMS site according to claim 1, wherein The site project configuration tool further includes: Database management module, which is used to implement the functions of storing real-time data collected on the site, storing device alarm information, and querying SQL scripts for editing historical data and generating reports; 3. The data acquisition visualization configuration tool for an EMS site according to claim 1, wherein The site project configuration tool further includes: Front-end computer management module, which is used to support data collection through the method of relaying by the front-end computer; 4. The data acquisition visualization configuration tool for an EMS site according to claim 1, wherein The site data page display module includes: Page rendering module, which is used to load the data display page, the basic primitives in the page, and the device configuration information, to control the basic primitives to display the corresponding content and render the corresponding appearance according to the pre-set display attributes, to control the device configuration to connect to the physical device and collect the physical signals of the device using the pre-configured device ports and protocols, and to convert them into the final content according to the expressions bound in the configuration. The device configuration displays the corresponding content and renders the corresponding appearance using the preset display attributes; Trigger engine module, which is used to load the interaction process during user operations defined in the basic primitives and the animations executed during data collection defined in the configuration, to set the listening of the corresponding interaction signals or events according to the interaction requirements of the primitives, to set the point interceptors during the data collection of the configuration according to the animation requirements of the configuration, and to sequentially execute one or more Action operations set in the interaction process after the corresponding event signals are monitored during the user interaction process.

5. The data acquisition visualization configuration tool for an EMS site according to claim 4, wherein The site data page display module further includes: Script execution engine module, which is used to provide a special type of Action for the trigger engine module. This type of Action can provide the function for users to write additional scripts.

6. A data acquisition and visualization configuration method for an EMS site, characterized in that, The method is based on the data acquisition visualization configuration tool described in any one of claims 1 to 5, and includes: Based on the site project configuration tool, configure the data acquisition protocol, acquisition information points, visual appearance of devices, animation process of devices during data acquisition, and alarm types for each device on the EMS site to form basic primitives of each device; Use the site data page production tool to build a data display page based on the basic primitives of the device, and configure the display content, display attributes, physical device address ports of device configuration, and interaction behaviors between basic primitives and users in the data display page based on the site data page production tool; Based on the site data page display module, display the data display page produced by the site data page production tool; monitor the trigger sources of the interaction behaviors of each basic primitive in the data display page, and judge whether to trigger based on the trigger sources combined with preset expressions, and display corresponding interaction content after judging the trigger.

Images