Hydropower application construction method based on business domain capability model

Abstract

A hydropower application construction method based on a business domain capability model comprises the following steps that S1, a hydropower business is decomposed into three levels of a domain, a sub-domain and a business capability module, and each business capability module independently covers a business scene; s2, for each business capability module, association of various IT capability assets is carried out; and S3, aiming at a business application, carrying out page granularity disassembly, and carrying out business capability module combination on the page granularity to form a concept prototype of the hydroelectric application. S4, for each page, positioning the associated IT capability assets through a service capability module; and S5, combining and processing various assets through a hydropower application construction tool to form a final application page, then constructing a menu framework, and hooking each page to form a final business application.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method for constructing a hydropower application based on a business domain capability model. Background Art

[0002] At present, the hydropower industry generally adopts general low-code development tools, such as general reporting tools (such as Fanruan BI) and general approval flows (editing and approval, etc.) for rapid construction. The problems solved are all point-like problems. For a hydropower business scenario, it is not possible to quickly build an application from a business perspective, and often requires a lot of customized development work to assist. Summary of the invention

[0003] The technical problem to be solved by the present invention is to provide a method for constructing a hydropower application based on a business domain capability model. When constructing a hydropower application, the business requirements are decomposed into various business capability modules in the business domain capability model, and the capability assets on the IT level corresponding to each business capability module are combined at the page interaction level to directly form a usable hydropower application.

[0004] In order to solve the above technical problems, the technical solution adopted by the present invention is: a method for constructing a hydropower application based on a business domain capability model, comprising the following steps: S1. Decompose the hydropower business into three levels: "field, sub-field and business capability module", and each business capability module independently covers a business scenario; S2. For each business capability module, various IT capability assets are associated; IT capability assets include data assets, analytical computing assets, visualization assets, business service assets and workflow assets; a business capability module may only contain certain types of assets among the five types of IT capability assets, and may associate multiple IT capability assets in each type of IT capability assets. The association relationship between each business capability module and IT capability asset has parameter configuration to achieve instantiation operation.

[0005] S3. For a business application, decompose it into page granularity and combine business capability modules at the page granularity to form a conceptual prototype of the hydropower application.

[0006] S4. For each page, locate the associated IT capability assets through the business capability module; S5. Through the hydropower application construction tool, various assets are combined and processed to form the final application page, and then the menu framework is built to connect the various pages to form the final business application.

[0007] Preferably, the data assets are associated in the form of various data views. The IT layer provides external access to various data views through a unified data service. It is highly versatile and can support multiple business areas or sub-areas. As long as the business area or sub-area that needs this data set is associated with this data asset.

[0008] Preferably, the analysis and computing assets are associated in the form of various types of analysis modeling results. The IT layer provides external functions such as model scheduling, model operation status query, and model call to obtain results through a unified model service; its universality depends on the abstraction and universality of the computing process. If the computing process has a certain universality, it can generally support multiple business areas or sub-areas. As long as the business requires this computing process, the business area or sub-area is associated with this analysis and computing asset.

[0009] Preferably, the visualization asset association is in the form of various visualization page construction results, and the IT layer locates the relevant pages by providing a unique access URL to obtain the final display result; it generally provides display services specifically for a certain business field or sub-field, is not highly reusable, and its parameter form is the page URL and dynamic parameters.

[0010] Preferably, the business service assets are associated in the form of various callable service interfaces, and the IT layer provides external capabilities through API interface services. They generally provide business processing logic services specifically for a certain business field or sub-field, and are not highly reusable. The parameter form is the service interface address and related service parameters.

[0011] Preferably, the workflow asset: the form of association is the result of workflow modeling, and the IT layer provides external capabilities for workflow startup, work task query, work task completion and other related operations through a unified workflow service. It generally provides workflow transfer services specifically for a certain business field or sub-field, and is not highly reusable, and its parameter form is the startup parameter of the workflow.

[0012] Preferably, in step 5, the method for constructing various specific assets is as follows: Data assets: Through the visual page building tool, you can drag and drop graphics to bind data assets according to business needs to form pages, including table pages, analysis graphics pages, and human-computer interaction pages; Analytical computing assets: Instantiate and schedule them through the general analytical computing management page. If necessary, you can configure the manual start and stop functions of the model and related parameters in the visual page building tool. Business service assets: Use visual page building tools to bind services related to configuration through graphic elements, trigger service calls, and obtain service return results; Workflow assets: directly hooked into the menu for reuse through the standard workflow management interface plus configuration parameters.

[0013] The present invention provides a hydropower application construction method based on a business domain capability model, which has the following beneficial effects: 1. Provides a systematic approach to support the hydropower business domain model with five types of IT capability assets, forming a mapping from business capability modules to IT capability assets. This avoids repeated construction of similar business scenarios under new business needs, and directly uses IT capability assets mapped by business capability modules to directly support the construction of hydropower applications, saving a lot of manpower and material resources. 2. Standardize the form and definition of five types of IT capability assets, as well as the ways and methods of combining these IT capability assets into hydropower applications. This will greatly accelerate the accumulation of capability modules in various business fields and form an acceleration effect. The more assets there are, the faster the construction of future hydropower applications will be. BRIEF DESCRIPTION OF THE DRAWINGS The present invention will be further described below in conjunction with the accompanying drawings and embodiments: Figure 1 It is a structural schematic diagram of the present invention; Figure 2 Flowchart constructed for application of the present invention. DETAILED DESCRIPTION

[0014] A method for constructing a hydropower application based on a business domain capability model comprises the following steps: S1. Decompose the hydropower business into three levels: "fields, sub-fields and business capability modules". Each business capability module independently covers a business scenario. For example, for the intelligent operation and maintenance business field, it is divided into two sub-fields: status monitoring and intelligent early warning. Each sub-field is further subdivided into multiple business capability modules. For example, the status monitoring sub-field can be subdivided into turbine monitoring, generator monitoring, etc. The intelligent early warning sub-field can be subdivided into: water guide bearing early warning, upper guide bearing early warning, generator early warning, transformer early warning, etc.

[0015] S2. For each business capability module, various IT capability assets are associated; IT capability assets include data assets, analytical computing assets, visualization assets, business service assets and workflow assets; a business capability module may only contain certain types of assets among the five types of IT capability assets, and may associate multiple IT capability assets in each type of IT capability assets. The association relationship between each business capability module and IT capability asset has parameter configuration to achieve instantiation operation.

[0016] Due to the differences in business domains and business capability modules, the IT capability assets that need to be configured are also different. If the existing IT capability assets do not meet the requirements, it is necessary to continuously build IT capability assets to support the business capability modules. The degree of reuse of IT capability assets depends on their degree of abstraction, the flexibility of parameters, and the particularity of business domains and business capability modules. Some IT capability assets are only adapted to specific business capability models, which is normal. For example, the analytical computing asset <water guide bearing warning algorithm> is only associated with the intelligent operation and maintenance business domain and intelligent warning sub-domain in the hydropower business. The data asset <turbine active power view> can be associated with both the turbine monitoring sub-domain and the generator monitoring sub-domain.

[0017] S3. For a business application, decompose it at the page granularity, and combine the business capability modules at the page granularity to form a conceptual prototype of the hydropower application. For example, when building an application for intelligent early warning of generators, there can be three main pages: generator status monitoring page, generator intelligent early warning result page, and generator intelligent early warning result processing page. For each page, select relevant business capability modules for support according to business needs. For example, the generator status monitoring page corresponds to the generator monitoring business capability module.

[0018] S4. For each page, the business capability module is used to locate the associated IT capability assets; for example, the generator status monitoring page can be directly associated with the generator parameter monitoring page, the generator intelligent warning result page can be associated with the intelligent warning model assets, the data assets for intelligent warning result query, etc., and the generator intelligent warning result processing page is associated with the warning processing business process.

[0019] S5. Through the hydropower application construction tool, various assets are combined and processed to form the final application page, and then the menu framework is built to connect the various pages to form the final business application.

[0020] Preferably, the data asset association is in the form of various data views. The IT layer provides external access to various data views through a unified data service. It is highly versatile and can support multiple business areas or sub-areas. As long as the business area or sub-area that needs this data set is associated with this data asset. Its parameter form is the query condition of the view. For example, the turbine monitoring sub-area can be associated with the following data assets: (1) Turbine speed view, whose parameters are turbine code; (2) Turbine active power view: Its parameter is the turbine code.

[0021] Preferably, the analysis and computing assets are associated in the form of various analysis and modeling results. The IT layer provides external functions such as model scheduling, model operation status query, and model call to obtain results through a unified model service; its universality depends on the abstractness and universality of the calculation process. If the calculation process has a certain universality, it can generally support multiple business areas or sub-areas. As long as the business needs this calculation process, the business area or sub-area is associated with this analysis and computing asset. Its parameter form is model-related input parameters. For example, the water-guided bearing warning can be associated with the following analysis and computing assets: (1) An intelligent early warning model based on a machine learning algorithm, whose parameters are the codes of the relevant measuring points of the water-guided bearing; (2) Fault warning model based on a certain mechanism: its parameters are the codes of the relevant measuring points of the water-guided bearing.

[0022] Preferably, the visualization asset association is in the form of various visualization page construction results. The IT layer provides a unique access URL to locate the relevant page to obtain the final display result. It generally provides display services specifically for a certain business field or sub-field, and is not very reusable. Its parameter form is the page URL and dynamic parameters. For example, generator monitoring can be associated with the following visualization assets: (1) Generator parameter monitoring page, which provides dynamic monitoring of various important operating parameters of the generator. Its parameters are the access URL and the relevant generator equipment code. (2) Generator 3D view, which provides an overall 3D image of the generator. Its parameters are the access URL and the relevant generator equipment code. Preferably, the business service assets are associated in the form of various callable service interfaces. The IT layer provides external capabilities through API interface services. They generally provide business processing logic services specifically for a certain business field or sub-field and are not highly reusable. The parameter form is the service interface address and related service parameters. For example, economic operation can be associated with the following business service assets: (1) Real-time economic operation information statistics service: Provides real-time statistical results of various economic operation indicators. Its parameters are the service interface and related parameters. (2) Economic operation configuration update service, which provides services for configuring and changing economic operation calculation formulas. Its parameters are the service interface and related parameters. Preferably, the workflow asset: The form of association is the result of workflow modeling. The IT layer provides external capabilities such as workflow initiation, work task query, and work task completion through a unified workflow service. It generally provides workflow transfer services specifically for a certain business field or sub-field, and is not highly reusable. Its parameter form is the startup parameter of the workflow. For example, intelligent warning can be associated with the following workflow assets: (1) Early warning processing business process: Provides a business process for processing early warning results. Starting this process will feedback the early warning results to the relevant person in charge according to the business level, and the person in charge will handle it. Its parameters are relevant information of the early warning results.

[0023] Preferably, in step 5, the method for constructing various specific assets is as follows: Data assets: Through the visual page building tool, you can drag and drop graphics to bind data assets according to business needs to form pages, including table pages, analysis graphics pages, and human-computer interaction pages; Analytical computing assets: Instantiate and schedule them through the general analytical computing management page. If necessary, you can configure the manual start and stop functions of the model and related parameters in the visual page building tool. Business service assets: Use visual page building tools to bind services related to configuration through graphic elements, trigger service calls, and obtain service return results; Workflow assets: directly hooked into the menu for reuse through the standard workflow management interface plus configuration parameters.

[0024] like Figure 1 As shown, the present invention decomposes the hydropower business into three levels: field, sub-field and business capability module, and parameterizes the association with data assets, analytical computing assets, visualization assets, business service assets and workflow assets at the IT level at the granularity of the business capability module. The association relationship is of one-to-many type and is parameterized, ultimately forming a business domain capability model that integrates business capabilities and IT capabilities.

[0025] like Figure 2 As shown, business capability modules are combined at the page granularity to form a hydropower application concept prototype. Then, through the parameterized association relationship between business capability modules and IT capability assets, IT capability assets are instantiated and assembled in the hydropower application construction tool. The parameters of the association relationship can be modified during the instantiation process. Finally, the various pages are connected through the menu framework tool to quickly build a hydropower application.

[0026] The above embodiments are only preferred technical solutions of the present invention and should not be regarded as limiting the present invention. The protection scope of the present invention shall be the technical solutions recorded in the claims, including equivalent replacement solutions of the technical features in the technical solutions recorded in the claims. That is, equivalent replacement improvements within this scope are also within the protection scope of the present invention.

Claims

1. A method for constructing a hydropower application based on a business domain capability model, characterized in that: The following steps are involved: S1. Decompose the hydropower business into three levels: "field, sub-field and business capability module", and each business capability module independently covers a business scenario; S2. For each business capability module, various IT capability assets are associated; IT capability assets include data assets, analytical computing assets, visualization assets, business service assets and workflow assets; a business capability module may only contain certain types of assets among the five types of IT capability assets, and may associate multiple IT capability assets in each type of IT capability assets. The association relationship between each business capability module and IT capability asset has parameter configuration to realize instantiation operation; S3. For a business application, decompose it into page granularity and combine business capability modules at the page granularity to form a conceptual prototype of the hydropower application; S4. For each page, locate the associated IT capability assets through the business capability module; S5. Through the hydropower application construction tool, various assets are combined and processed to form the final application page, and then the menu framework is built to connect the various pages to form the final business application.

2. A method for constructing a hydropower application based on a business domain capability model according to claim 1, characterized in that: The data assets are associated in the form of various data views. The IT layer provides external access to various data views through unified data services. It is highly versatile and can support multiple business areas or sub-areas. As long as the business area or sub-area that needs this data set is associated with this data asset.

3. A method for constructing hydropower applications based on a business domain capability model according to claim 1, characterized in that: The analysis and computing assets are associated in the form of various analysis modeling results. The IT layer provides external functions such as model scheduling, model operation status query, and model call to obtain results through a unified model service. Its universality depends on the abstraction and universality of the computing process. If the computing process has a certain universality, it can generally support multiple business areas or sub-areas. As long as the business requires this computing process, the business area or sub-area is associated with this analysis and computing asset.

4. The method for constructing a hydropower application based on a business domain capability model according to claim 1, characterized in that: The form of the visualization asset association is the result of building various visualization pages. The IT layer locates the relevant pages by providing a unique access URL to obtain the final display result. It generally provides presentation services specifically for a certain business field or sub-field and is not very reusable. Its parameters are in the form of page URLs and dynamic parameters.

5. The method for constructing a hydropower application based on a business domain capability model according to claim 1, characterized in that: The business service assets are associated in the form of various callable service interfaces. The IT layer provides external capabilities through API interface services. They generally provide business processing logic services specifically for a certain business field or sub-field and are not highly reusable. The parameters are in the form of service interface addresses and related service parameters.

6. The method for constructing a hydropower application based on a business domain capability model according to claim 1, characterized in that: The workflow asset: The form of association is the result of workflow modeling. The IT layer provides the ability to start workflows, query work tasks, complete work tasks and other related operations through a unified workflow service. It generally provides workflow flow services specifically for a certain business field or sub-field, and is not very reusable. Its parameter form is the startup parameters of the workflow.

7. The method for constructing a hydropower application based on a business domain capability model according to claim 1, characterized in that: In step 5, the methods for constructing various specific assets are as follows: Data assets: Through the visual page building tool, you can drag and drop graphics to bind data assets according to business needs to form pages, including table pages, analysis graphics pages, and human-computer interaction pages; Analytical computing assets: Instantiate and schedule them through the general analytical computing management page. If necessary, you can configure the manual start and stop functions of the model and related parameters in the visual page building tool. Business service assets: Use visual page building tools to bind services related to configuration through graphic elements, trigger service calls, and obtain service return results; Workflow assets: directly hooked into the menu for reuse through the standard workflow management interface plus configuration parameters.

Images