Service selection system and service selection method

Abstract

To provide a service selection system and a service selection method that reduce burdens of selecting services that perform facility control.SOLUTION: A service selection system that selects microservices for facility operation, includes: a tangible service storage unit for storing tangible services that operate an energy-related facility; a facility information storage unit for storing facility data indicating specification information for a target facility; an operation information storage unit for storing operation data indicating a correspondence between a facility operation content and a processing content required to carry out the operation content; an abstract service storage unit for storing abstract services that execute the operation content indicated by the operation data using the facility indicated by the facility data; and an abstract service execution unit for selecting an abstract service stored in the abstract service storage unit for the facility specified in the facility data and the operation specified by the operation data, based on the operation data in the operation information storage unit and the facility data in the facility information storage unit.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a service selection system and a service selection method. [Background technology]

[0002] Power sources such as solar power generation systems and storage batteries are called distributed power sources because they are widely distributed. Distributed Energy Resource Management Systems (DERMS) are known as a technology for comprehensively monitoring and controlling these distributed power sources.

[0003] The operational purposes of distributed power sources are diverse, and the specifications of each distributed power source and the control system are not necessarily standardized. Since building a monitoring, control, and operation system for each distributed power source and its functions to suit each individual specification would be inefficient, it is important to flexibly accommodate the differences in operational purposes and specifications while combining existing functions.

[0004] Microservices technology is known as a technology that reuses existing functions and increases interoperability.

[0005] Patent Document 1 discloses a method in which a system uses microservice information, which is meta-information about a microservice, and model information, which is meta-information about the model of the service, to evaluate whether other services are suitable as alternatives to a given rating source service, and then presents the rating source service and alternative services for the desired service input by the user.

[0006] Patent Document 2 discloses a method in which a type register is provided to describe a data type, each microservice has input and output type information, and each microservice operates its processing logic on the condition that the data type contained in the received message matches its own input data type. [Prior art documents] [Patent documents]

[0007] [Patent Document 1] Patent Publication No. 2021-125150 [Patent Document 2] JP 2018-73400 A Summary of the Invention [Problem to be solved by the invention]

[0008] When attempting to configure a certain system behavior (use case) using a large number of microservices, it is not easy to select a microservice from the large number of microservices to realize the use case and have it execute the processing.

[0009] For example, in the electricity industry, various types of power sources are operated, and the operation methods differ depending on the type of power source, and the planning optimization logic and input data for this also differ, but there is no disclosure of how to select microservices that are suitable for each power source facility and its use case. [Means for solving the problem]

[0010] The above-mentioned problem is achieved by a service selection system that selects microservices for equipment operation, the service selection system including: an entity service memory unit that stores entity services that operate energy-related equipment; an equipment information memory unit that stores equipment data indicating specification information of the target equipment; an operation information memory unit that stores operation data that indicates the correspondence between the operation content of the equipment and the processing content required to carry out the operation content; an abstract service memory unit that stores abstract services that execute the operation content indicated by the operation data using equipment indicated by the equipment data; and an abstract service execution unit that selects an abstract service stored in the abstract service memory unit using the equipment specified in the equipment data and the operation specified by the operation data based on the operation data in the operation information memory unit and the equipment data in the equipment information memory unit. [Effects of the Invention]

[0011] According to the present invention, the load of selecting a service for which facility control is performed can be reduced. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a diagram illustrating an example of a configuration of a service selection system according to a first embodiment of the present invention. [Figure 2] 1 is an example of a hardware configuration of a service control device and a service management device according to a first embodiment of the present invention. [Figure 3] 1 is an example of a software configuration of a service selection system according to a first embodiment of the present invention. [Figure 4] 4 is an example of a flowchart illustrating processing of the service selection system according to the first embodiment of the present invention. [Figure 5] FIG. 2 is a diagram illustrating an operation of the service selection system according to the first embodiment of the present invention. [Figure 6] FIG. 3 is an example of a table diagram showing facility data according to the first embodiment of the present invention. [Figure 7] FIG. 4 is an example of a table diagram showing operation data according to the first embodiment of the present invention. [Figure 8] FIG. 3 is an example of a table diagram showing abstract service data according to the first embodiment of the present invention. [Figure 9] FIG. 2 is a diagram illustrating a hierarchy of software modules according to the first embodiment of the present invention. [Figure 10] FIG. 10 is a diagram illustrating the operation of the service selection system according to the second embodiment of the present invention. [Figure 11] 10 is an example of an input screen according to an embodiment of the present invention. [Figure 12] 10 is an example of an output screen according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0013] An embodiment of the present invention will be described in detail below with reference to the drawings.

[0014] (1) First embodiment (1-1) Configuration of the Information Processing System According to the Present Embodiment FIG. 1 is a diagram showing an example of the configuration of a service selection system according to the first embodiment of the present invention.

[0015] The service control device 2 and the service management device 3 hold multiple microservices related to the monitoring, control, and operation of energy-related facilities, and enable the selection, combination, and processing of microservices that are suitable for the configuration of the monitoring, control, and operation.

[0016] The service control device 2 and the service management device 3 may be realized by one computer, or may be realized by independent computers.

[0017] The service selection system 1 comprises a service control device 2, a service management device 3, an information registration device 4, a service registration device 5, a monitoring control device 6, a control facility 7, an information input / output terminal 8, and an external information distribution device 9.

[0018] The communication path 10 is, for example, a LAN (Local Area Network) or a WAN (Wide Area Network), and is a communication path that connects various devices and terminals that make up the service selecting system 1 so that they can communicate with each other.

[0019] The service control device 2 refers to the abstract service data it holds, selects a microservice that conforms to the equipment specification data and operation specification data it holds, and transmits control data to the service management device 3 so that the microservice stored in the service management device 3 can process and operate.

[0020] The control equipment 7 refers to equipment related to the production and consumption of energy, such as energy production equipment such as generators and storage batteries, energy consumption equipment such as air conditioning and lighting, or apparent energy production equipment that reduces the consumption of energy consumption equipment, known as demand response.

[0021] The present invention can be applied to the monitoring and control of not only energy-related control facilities but also various other facilities such as production facilities and transport facilities, but in this embodiment, energy-related facilities will be described as an example.

[0022] The equipment specifications are a description of the specification information of the distributed power generation equipment to be controlled and operated.

[0023] For example, if the control equipment is a distributed power source, the specification information includes at least fixed information such as its type (gas cogeneration, solar power generator, battery, etc.), maximum or minimum output value, speed of output increase or decrease, and fuel or storage capacity of the distributed power source, as well as time-varying information such as the current output value of the distributed power source and remaining fuel or storage capacity, or information on operational constraints such as upper and lower limits for continuous operation of the distributed power source and operating hours.

[0024] Operation specifications are information that indicate specifications related to the operation of the above-mentioned control equipment, and specify, for example, the name (use case) that indicates the content of equipment operation, and the processing content and processing order of predictive calculations that obtain predicted values ​​required for operation execution and operation plan schedule optimization calculations.

[0025] Microservices are various processing units involved in the monitoring, control, and operation of energy-related facilities, and include at least the following processing units: predicted energy demand values; predicted energy production values ​​such as solar power generation amounts; predicted market conditions in energy-related markets such as the electricity trading market; plan optimization to create operation schedules for distributed power sources; market collaboration to send buy / sell bid data to the energy trading market and receive contract results from the market; data collaboration to acquire weather data used for the above-mentioned forecasting processes, public data such as energy trading market data, and demand data held by systems managed and operated by each energy-related business; contract management to manage electricity market contract results and operating contract data with owners of distributed power sources; fee settlement management to calculate and settle fees based on the contract; and equipment data management to acquire specification data and measurement data for distributed power sources.

[0026] Abstract service data is information that associates various processes related to control equipment operation with the microservices that actually execute those processes, depending on the operation content and the equipment used.

[0027] The service management device 3 holds the entity objects of the above microservices, and starts up the microservices and executes the processes based on the control data for calling and executing the microservices received from the service control device 2.

[0028] The user uses the information registration device 4 to create, register, update, and delete the operation specification data and facility specification data stored in the service control device 2 and the service specification data stored in the service management device 3 .

[0029] A user uses the service registration device 5 to create, register, update, and delete the programs of the microservices described above in the service storage unit of the service management device 3.

[0030] The monitoring control device 6 receives control data that is created by the processing of the microservices described above and that is held by the service control device 2, and transmits control signals to the control equipment .

[0031] The control equipment 7 refers to equipment related to the production and consumption of energy, such as energy production equipment such as generators and storage batteries, energy consumption equipment such as air conditioning and lighting, or apparent energy production equipment that reduces the consumption of energy consumption equipment, known as demand response.

[0032] The user uses the information input / output terminal 8 to input data to the service control device 2 and the service management device 3, and to display data stored in or output from these devices.

[0033] The external information distribution device 9 transmits to the service management device 3 data held by the service management device 3 that is necessary for the processing operations of the microservices described above.

[0034] (1-2) Service control device and service management device FIG. 2 shows an example of the hardware configuration of the service control device and the service management device in the first embodiment of the present invention.

[0035] The service control device 2 is composed of a CPU (Central Processing Unit) 21 that controls the overall operation of the service control device 2, an input device 22, an output device 23, a communication device 24, and a storage device 25. The service control device 2 is an information processing device such as a personal computer, a server computer, or a handheld computer.

[0036] The input device 22 is a device such as a keyboard or a mouse, and the output device 23 is a device such as a display or a printer.

[0037] The communication device 24 is a NIC (Network Interface Card) or the like for connecting to a wireless LAN or a wired LAN.

[0038] The storage device 25 is a storage medium such as a RAM (Random Access Memory), a ROM (Read Only Memory), an HDD (Hard Disk Drive), or an SSD (Solid State Drive).

[0039] The output results of each processing unit and intermediate results may be output via the output device 23 as appropriate.

[0040] The storage device 25 stores databases such as an abstract service storage unit 253, an operation information storage unit 254, a facility information storage unit 255, and an input information storage unit 256. The abstract service storage unit 253 holds abstract services.

[0041] The operation information storage unit 254 stores operation data. The equipment information storage unit 255 stores equipment data. The input information storage unit 256 stores input data.

[0042] The abstract service memory unit 253 stores abstract services that route to microservices that perform actual processing depending on the operation content and the control equipment used, in order to execute various processes required to operate energy-related control equipment.

[0043] The operation information storage unit 254 stores information indicating the operation details of energy-related control equipment, and stores, for example, operation data that specifies the processing details and processing order of predictive calculations and operation plan schedule optimization calculations required to operate the equipment.

[0044] The equipment information storage unit 255 stores specification information of the distributed power generation equipment to be controlled and operated. For example, if the control equipment is a distributed power generation equipment, the specification information stores equipment data such as the type of power source (thermal power, cogeneration, solar power generator, storage battery, etc.), the maximum or minimum output value, the rate of output increase or decrease, and fixed information such as the fuel and storage capacity of the distributed power generation equipment, time-varying information such as the current output value of the distributed power generation equipment and the remaining fuel and storage capacity, or information on operational constraints such as the upper and lower limits of continuous operation of the distributed power generation equipment and the operating hours during which it can be operated.

[0045] The input information storage unit 256 stores input data for various processes required to operate energy-related control facilities, and for example, in the case of forecasting processing, it includes at least explained variable data such as power demand, market price, and power generation amount, and explanatory variable data such as temperature, solar radiation, calendar information, etc. In the case of plan optimization processing, it also stores input data such as status data for each facility (output value, remaining fuel and power storage amount, operation stop status value).

[0046] The storage device 25 also stores software modules such as a service control unit 251 and an abstract service execution unit 252, which are executed by the CPU 21 by referring to the data stored in the storage device.

[0047] Service control unit 251 inputs operation data and facility data to abstract service execution unit 252 and starts the processing of abstract service execution unit 252 .

[0048] The abstract service execution unit 252 calls the abstract service and causes the abstract service to execute a processing request to a microservice that matches the operation data and facility data input from the service control unit.

[0049] The service management device 3 is made up of a CPU (Central Processing Unit) 31 that controls the overall operation of the service management device 3 , an input device 32 , an output device 33 , a communication device 34 and a storage device 35 .

[0050] The service control device 2 is an information processing device such as a personal computer, a server computer, or a handheld computer.

[0051] The storage device 35 stores databases such as an actual service storage unit 353 and a template service storage unit 354 .

[0052] The input device 32, output device 33, communication device 34 and storage device 35 are realized by the same hardware as the output device 23, communication device 24 and storage device 25 used in the service control device of FIG.

[0053] The entity service storage unit 353 stores one or more entity microservices, which are objects that actually perform processing. The template service storage unit 354 stores template microservices that are used as models when generating microservices.

[0054] The entity microservices and template microservices are various processing units related to the monitoring, control, and operation of energy-related facilities, and include at least the following processing units: predicted energy demand values; predicted energy production volumes such as solar power generation; predicted market conditions in energy-related markets such as the electricity trading market; plan optimization for creating operation schedules for distributed power sources; market collaboration for sending buying and selling bid data to the energy trading market and receiving contract results from the market; data collaboration for acquiring public data such as weather data used for the above-mentioned forecasting processes, energy trading market data, and demand data held by systems managed and operated by each energy-related business; contract management for managing electricity market contract results and operating contract data with owners of distributed power sources; fee settlement management for calculating and settling fees based on the contract; and equipment data management for acquiring specification data and measurement data for distributed power sources.

[0055] (1-3) Overall processing and data flow of the information processing system according to this embodiment 3 shows an example of the software configuration of a service selection system according to the first embodiment of the present invention. The processing and data flow according to this embodiment will be described with reference to FIGS.

[0056] The data flow of the processing in this embodiment will be described with reference to FIG.

[0057] The service management device 3 receives the identifier of the template microservice and the setting values ​​that define the processing operation of the microservice from the service registration device 5, and inputs them to the substance service generation unit 351.

[0058] The entity service generation unit 351 reads the template service from the template service storage unit 354 based on the input template microservice identifier, rewrites the setting values ​​of the read template service to match the input setting values, and stores it in the entity service storage unit 353 as an entity microservice.

[0059] The service control device 2 receives the operation data, facility data and input data from the information registration device 4, and stores them in the operation information storage unit 254, facility information storage unit 255 and input information storage unit 256, respectively.

[0060] Next, the service control device 2 inputs pre-specified operational data, equipment data, and input data into the service control unit 251, and the service control unit 251 sends this data to the abstract service execution unit 252, thereby starting the processing of the abstract service execution unit.

[0061] Next, the service control device 2 starts the abstract service execution unit 252, identifies a compatible entity microservice from the input operational data and equipment data, and sends a request for processing that entity microservice along with the input data to the entity service execution unit 352 of the service management device 3.

[0062] Next, the entity service execution unit 352 in the service management device 3 calls the entity microservice that received the processing request from the entity service storage unit 353, and inputs the received input data into the called entity microservice to perform processing.

[0063] The received result data is then sent to the abstract service execution unit 252 in the service control device 2 .

[0064] Finally, the abstract service execution unit 252 in the service control device 2 transmits an execution command for facility operation to the monitor control device 6 based on the received result data for control.

[0065] FIG. 4 is an example of a flowchart showing the processing of the service selection system according to the first embodiment of the present invention.

[0066] The processing procedure in this embodiment will be described below. This processing is triggered by the service control device 2 receiving an input operation from a device user or by the arrival of a preset execution time, and the service control device 2 and service management device 3 execute the processing from step S401 to step S407.

[0067] In practice, processing is executed based on various computer programs stored in the CPU 21 and storage device 25 of the service control device 2 and various computer programs stored in the CPU 31 and storage device 35 of the service management device 3.

[0068] For convenience of explanation, the processing entities will be described as processing units realized by software provided in the service control device 2 and the service management device 3.

[0069] First, the abstract service execution unit 252 of the service control device 2 selects an entity microservice that matches the operation data and facility data input from the service control unit 251 from the abstract service storage unit 253 (S401). The abstract service execution unit 252 then determines whether or not the selection of a suitable entity microservice has been successful (S403). If the selection is successful, the abstract service execution unit 252 sends a processing request for the selected entity microservice to the entity service execution unit 352 of the service management device 3 (S404). Then, the abstract service execution unit 252 executes the entity microservice received from the entity service execution unit 352, and transmits the obtained processing result to the monitoring control device 6 as a control signal for facility operation (S405). If a suitable entity microservice cannot be selected in step 403, the service control device 2 transmits a request for generating a suitable entity microservice to the entity service generation unit 351 of the service management device 3 (S402). The entity service generation unit 351 then determines whether the entity microservice generation was successful (S407), and if the generation was successful, resumes the processing from S401. If the generation was not successful, an error is output and the processing ends.

[0070] (1-4) Details of each component (1-4-1) Abstract Service Execution Unit and Substantial Service Execution Unit FIG. 5 is a diagram showing the operation of the service selection system in the first embodiment of the present invention.

[0071] The data flow and processing operation of the abstract service execution unit 252 in this embodiment will be described.

[0072] The abstract service execution unit 252 in this embodiment refers to the equipment data stored in the equipment information storage unit 255 specified by the service control unit 251 and the operation data stored in the operation information storage unit 254, and selects and executes the necessary entity microservices stored in the abstract service storage unit 253 so that the control equipment indicated in the equipment data can perform the operation indicated in the operation data.

[0073] Specifically, abstract service calling unit 2521 calls an abstract service and identifies the operation details and processing details indicated in the operation data, which will be explained in more detail with reference to FIGS.

[0074] FIG. 6 is an example of a table diagram showing facility data in the first embodiment of the present invention.

[0075] The facility data is stored in the facility information storage unit 255, with the first column indicating the user identifier and the second column indicating the name of the facility used by the user.

[0076] For example, the user "U1" in the first line indicates that he will use a generator (PV: solar power generator) and a storage battery.

[0077] FIG. 7 is an example of a table showing operation data in the first embodiment of the present invention.

[0078] The operation data is stored in the operation information storage unit 254, and the first column indicates the identifier of the operation content, the second column indicates the name of the operation content, and the third column indicates the processing order required to execute the operation.

[0079] For example, the operation "O1" in the first line indicates that this is an operation to conduct day-ahead market transactions in the wholesale market, and the processes required to execute this operation are, in order, demand forecast, renewable energy power generation forecast, market price forecast, market transaction plan creation, and market bidding processing.

[0080] FIG. 8 is an example of a table showing abstract service data in the first embodiment of the present invention.

[0081] Abstract services are stored in the abstract service memory unit 253, with the first column indicating the name of the abstract service, the second column indicating the operation name, the third column indicating the equipment name of the equipment that is the target of the operation, and the fourth column indicating the entity service name, which is the name of the corresponding entity microservice.

[0082] For example, the abstract service “Renewable energy forecast” in the first line is an abstract service used in the operations with the operation names “Day-ahead market trading” and “Self-consignment.”

[0083] It is shown that when using the facility "Power Generator (PV)" in the operation of "Day-Ahead Market Trading," it is specified that the actual microservices to be used are "Area Renewable Energy Forecast" and "Site Renewable Energy Forecast."

[0084] For example, it is assumed that the operation data with the operation name "day-ahead market trading" among the operation data shown in FIG.

[0085] The five processes required in this case are "demand forecast," "renewable energy forecast," "market price forecast," "market transaction plan," and "market bidding," as shown in Figure 7.

[0086] Then, abstract service calling unit 2521 selects the entity services that will perform these processes using the abstract services shown in FIG.

[0087] For example, in the abstract service "Demand Forecast," it is indicated that when the operation name "Day-ahead market trading" is performed, the actual service "Area Demand Forecast" is designated to be selected regardless of the facility.

[0088] Next, in the abstract service "Renewable Energy Forecast", when the facility "Power Generator (PV)" is used in the operation name "Day-Ahead Market Trading", it is shown that two entity microservices, "Area Renewable Energy Forecast" and "Site Renewable Energy Forecast", are specified to be used.

[0089] The area renewable energy forecasting entity service is an entity microservice for forecasting the total renewable energy power generation in a wide area, for example, spanning multiple prefectures.

[0090] The site renewable energy prediction service is a microservice that predicts the amount of renewable energy generated by a single facility, for example, a "power generator (PV)" of user "U1."

[0091] In addition, an entity service that creates an optimization model that optimizes the power generation amount of a generator, and an entity service that optimizes the operation plan of a generator using the created optimization model may also be stored in the abstract service.

[0092] Thereafter, abstract service calling unit 2521 similarly selects the entity service that will perform each process using the abstract service shown in FIG.

[0093] Next, the entity service calling unit 2522 sends a processing request for the entity microservice selected by the abstract service calling unit 2521 to the entity service execution unit 352 together with the input data.

[0094] The transmission of a processing request is, for example, in the form of transmitting data of a uniform resource identifier (URI) of a microservice.

[0095] Upon receiving the request, the entity service execution unit 352 sends the input data to the specified entity microservice, causes it to process the data, and receives the processing results.

[0096] Then, the entity service execution unit 352 transmits the processing result data to the entity service calling unit 2522 .

[0097] Finally, the entity service calling unit 2522 transmits a facility operation execution signal to the monitoring control device 6 based on the received result data.

[0098] This completes the operation of abstract service execution unit 252.

[0099] (1-4-2) Entity Service Generation Unit The data flow and processing operation of the service generation unit 351 in this embodiment will be described.

[0100] In this embodiment, the service generation unit 351 receives input of the name of the entity service to be generated and its setting data from the service registration device 5, reads the template service corresponding to the name of the entity service from the template service storage unit 354, modifies the template service based on the input setting data, and stores it in the entity service storage unit 353 as a new entity microservice.

[0101] More specifically, suppose there is a template service called "Day-ahead Market Trading Plan - Storage Battery." The planned equipment for this template service is a storage battery, the planning time granularity is hourly, and the planning period is 24 hours.

[0102] Furthermore, this template microservice is parameterized so that the time granularity and planning period can be changed externally.

[0103] Here, it is assumed that the service registration device 5 inputs setting data for a new entity microservice of the service "day-ahead market trading plan" in which the target facility is a storage battery, the time granularity is 15 minutes, and the planning period is 48 hours.

[0104] The service generation unit 351 reads the template service “Day-ahead market trading plan_battery”, sets its parameters, time granularity and planning period, to 15 minutes and 48 hours, respectively, and stores this as a new entity microservice in the entity service storage unit 353.

[0105] (1-4-2) Service Control Unit The data flow and processing operation of the service control unit 251 in this embodiment will be described. The service control unit 251 according to this embodiment transmits operation data, equipment data, and input data to the abstract service execution unit 252, and triggers the start of an abstract service.

[0106] (1-5) Software module hierarchy FIG. 9 is a diagram illustrating the hierarchy of software modules in the first embodiment of the present invention.

[0107] The left half of Figure 9 shows a conventional microservice-based information processing device for operating energy-related facilities.

[0108] In conventional information processing devices, microservices for performing necessary processing are fixedly associated in advance with equipment operation cases (App1 and App2 in the figure).

[0109] However, in this configuration, when attempting to carry out new operations using a large number of microservices, it is not easy to select a microservice from the large number of microservices to realize a use case and have it execute the processing.

[0110] For example, power systems operate various types of power sources, and the operation methods differ depending on the type of power source. As a result, the planning optimization logic and input data also differ, and it is not easy to select microservices that are suitable for each power source facility and its use case.

[0111] The right half of the figure shows the software module hierarchy in this embodiment. In the information processing device in this embodiment, by introducing abstract services, it is possible to associate microservices and applications that match the operational purpose and the equipment used.

[0112] (2) Other embodiments (2-1) Modified example of information processing device FIG. 10 is a diagram showing the operation of the service selection system in the second embodiment of the present invention.

[0113] In this embodiment, an embodiment of a bidding process in electricity market transactions will be described.

[0114] Fig. 10 shows a modified example in which the abstract service execution unit 252 and the substance service execution unit 352 described in Fig. 5 are implemented in the bidding process. Operation data, facility information, and input data are input as input data in the same manner as described in Fig. 5.

[0115] However, the input data is the result data output from a service that performs the trading plan creation process, such as the actual microservice "Day-ahead Market Trading Plan."

[0116] The result data is data that includes at least, for example, the planned amount of electric power sold for each unit of time of each power supply facility and cost information of each power supply facility.

[0117] The abstract services are also assumed to include, for example, abstract services with the abstract service name "Market Bidding", operation name "Day-Ahead Market", equipment "Storage Battery", and actual service names "Ticket Creation Service - Current Split", "Ticket Creation Service - By Power Source", and "Ticket Creation Service - Bulk".

[0118] The "bid creation service - division" is, for example, a process of dividing the input planned sales volume into a specified number of divisions and creating bidding bids for each divided sales volume.

[0119] The "bid creation service - by power source" is a service that creates bid bids for each input planned sales volume for each power source. The "bid creation service - all at once" is a service that creates a single bid for the entire input planned sales volume.

[0120] Here, "day-ahead market transactions" is input as operational data, and "storage battery" is input as facility data.

[0121] Based on the operational data shown in Figure 7, the processes required for "day-ahead market trading" are "demand forecast," "renewable energy forecast," "market price forecast," "market trading plan," and "market bidding," so the abstract service invocation unit 2521 that receives the input selects each entity microservice from the abstract service.

[0122] Here, for "market bidding," based on the aforementioned abstract service name "market bidding," operation name "day-ahead market," equipment "storage battery," and actual service names "ticket creation service_lump sum," "ticket creation service_current split," and "ticket creation service_by power source," three actual service selection candidates are extracted: "ticket creation service_lump sum," "ticket creation service_current split," and "ticket creation service_by power source."

[0123] The process of selecting one actual service from three actual services may be, for example, a process of selecting a preset actual service, or a process of presenting three candidates to the user and allowing the user to select. Here, the explanation will proceed assuming that "Tag Creation Service - Current Division" has been selected.

[0124] Next, the abstract service execution unit 252 performs preprocessing of the input data in the preprocessing unit 2523 .

[0125] Pre-processing involves, for example, accumulating planned sales volumes in order of lowest cost based on the planned sales volumes and cost data of each power source, which are the input plan optimization results (generation of marginal cost curves). This is performed for each time granularity of the input plan optimization results.

[0126] Next, the abstract service storage unit 253 transmits a processing request signal to the entity microservice selected by the abstract service calling unit 2521 to the entity service execution unit 352. Furthermore, the data output by the preprocessing unit 2523 is also transmitted.

[0127] Next, the entity service execution unit 352 causes the specified entity service "Ticket Creation Service_Current Division" to execute processing and generate tag data. The entity service execution unit 352 then transmits the generated tag data to the entity service calling unit 2522. The entity service calling unit 2522, which has received the tag data, transmits the tag data to the tag sending unit 2524.

[0128] The bidding transmitter 2524 converts the input bidding data into a bidding format or a telegram format specified for each market, and transmits it to the market management device, which is the monitoring and control device 6.

[0129] The process of creating bids to be submitted to the market varies depending on each user's bidding strategy and the type of power source used, as well as the regulations of the market in which the bid is being submitted, resulting in a wide variety of processing services.

[0130] According to this embodiment, a suitable bill creation service can be automatically selected from a large number of actual microservices based on operational data such as the power source to be used and the market in which the transaction will be conducted.

[0131] (2-2) Modified example of pre-processing unit In the above-described embodiment, we have described a preprocessing unit that formats input data to be input to an entity microservice. In this description, the preprocessing was described as limit table curve generation processing for input to a tag creation service, but the preprocessing may also be processing for standardizing input to other types of entity microservices.

[0132] For example, as preprocessing for the actual microservice that performs the prediction processing, the input data may be converted into a table or matrix format indicating the explanatory variables and a table or matrix format indicating the explained variables.

[0133] By standardizing the input to the entity microservice that performs the prediction process in this way, the entity microservice can be adapted to the operational data and equipment data even when there are multiple separate entity microservices with different prediction models.

[0134] Furthermore, as a preprocessing step for the actual microservice that performs the plan optimization, the optimization variables, objective function, and constraints may be standardized into a predetermined format or notation. Standardizing the input to the actual microservice that performs the plan optimization in this way makes it possible to switch the algorithm for solving the optimization problem.

[0135] (2-3) Variations of entity microservices In this embodiment, the entity that performs the processing required for equipment operation has been described as a microservice, but it may also be in the form of a library module, etc. By using a library module instead of a microservice, it is possible to reduce memory and storage space.

[0136] 11 is an example of an input screen in an embodiment of the present invention. To explain the input screen 501 using an example of a microservice for energy trading, select day-ahead market trading operation in the operation information input area 502, select a storage battery and a power generator (PV) in the facility information input area 503, and press the microservice configuration execution button 505 to output the microservice configuration results.

[0137] Figure 12 is an example of an output screen in an embodiment of the present invention. This output screen 510 displays selected operation information 511 and selected facility information 512, as well as the created entity service configuration 513. The hexagonal shapes represent the entities of the microservices, and the processing content is set when defining and registering the abstract service shown in Figure 7. [Explanation of symbols]

[0138] 1: Service selection system 2: Service control device 3: Service management device 4: Information registration device 5: Service registration device 6: Monitoring and control equipment 7: Control equipment 8: Information input / output terminal 9: External information distribution device 10: Communication path 251: Service control section 252: Abstract Service Execution Department 253: Abstract Service Memory 254: Operation information storage unit 255: Equipment information storage section 256: Input information storage unit 351: Entity service generation unit 352: Entity Service Execution Unit 353: Entity service storage unit 354: Template service storage unit

Claims

1. A service selection system that selects microservices for facility operation, an entity service storage unit that stores entity services that operate energy-related facilities; an equipment information storage unit that stores equipment data indicating specification information of the target equipment; an operation information storage unit that stores operation data indicating correspondence between operation details of the equipment and processing details required to perform the operation details; an abstract service storage unit that stores an abstract service that executes the operation content indicated by the operation data using the equipment indicated by the equipment data; A service selection system comprising an abstract service execution unit that selects an abstract service stored in the abstract service storage unit using the operation data of the operation information storage unit and the equipment data of the equipment information storage unit, based on the equipment specified in the equipment data and the operation specified in the operation data.

2. 2. The service selection system according to claim 1, When the abstract service execution unit cannot select an abstract service from the abstract services stored in the abstract service storage unit based on the facility data and operation data, A service selection system that receives input of a template microservice stored in a template service storage unit and setting values ​​for a new service input from a service registration device, and generates an actual service.

3. 2. The service selection system according to claim 1, an entity service execution unit that receives a specification of an entity service included in the abstract service selected by said abstract service execution unit, executes the specified entity service, and returns a processing result of the entity service to said abstract service execution unit; The abstract service execution unit sends the processing results of the actual service to a monitoring and control device.

4. 2. The service selection system according to claim 1, When the abstract service execution unit selects an entity service, A service selection system that selects an entity service stored in an abstract service storage unit in which a generator that matches a generator stored in facility data is registered in the facility name.

5. 2. The service selection system according to claim 1, The abstract service is a service selection system that stores the actual service for which a prediction value is sought.

6. 2. The service selection system according to claim 1, The abstract service is a service selection system including an entity service that constructs an optimization model for the operation plan of the control equipment, and an entity service that reads the constructed optimization model and performs optimization processing.

7. 2. The service selection system according to claim 1, The abstract service is a service selection system that includes at least one substantive service that creates bids to sell electricity generated by a generator on an electricity market, transmits the bids to the electricity market, and determines the amount to be sold.

8. 2. The service selection system according to claim 1, The abstract service is a service selection system that provides at least one of a microservice and a library.

9. A service selection method for selecting a microservice for equipment operation, comprising: The entity service storage unit stores entity services that operate energy-related facilities; The equipment information storage unit stores equipment data indicating specification information of the target equipment, an operation information storage unit stores operation data indicating correspondence between operation details of the equipment and processing details required to perform the operation details; an abstract service storage unit stores an abstract service that executes the operation content indicated by the operation data using the equipment indicated by the equipment data; A service selection method in which an abstract service execution unit selects an abstract service stored in the abstract service storage unit based on the operation data in the operation information storage unit and the equipment data in the equipment information storage unit, using the equipment specified in the equipment data and the operation specified in the operation data.

Images