Resource management device, resource management method, and resource management program

Abstract

To improve the utilization rate of resources provided to multiple types of systems.SOLUTION: A resource virtualization system 2 includes: a virtual resource capability conversion unit 351 that prepares virtual capability data indicating a capability as a virtual resource that an entity resource 5 provides based on virtualization logic for virtualizing the entity resource 5 from entity resource management data 451A measuring the entity resource 5, which is an energy-related device, and constructs the virtual resource to provide the virtual capability data; and a capability allocation unit 353 that allows a resource operation management system 1 to manage the entity resource 5 by allocating the virtual resource that the virtual resource capability conversion unit 351 has constructed to the resource operation management system 1. The virtualization logics are individually prepared according to resource request content data indicating a capability status of the entity resource 5 that an allocated destination resource operation management system 1 requires.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present invention relates to a resource management device, a resource management method, and a resource management program.

Background Art

[0002] It is known that the output of renewable energy such as solar power generation varies depending on weather conditions and time zones. In order to absorb fluctuations in output and make the most effective use of the electricity generated by renewable energy, it is important to efficiently manage and control facilities related to energy that are widely and massively distributed in the power grid. Patent Document 1 discloses a method for controlling distributed energy devices such as generators, storage batteries, and hydrogen storage devices based on predicted demand values and supply predicted values of energy. According to Patent Document 1, by integrally controlling resources that are a plurality of different types of energy devices, optimal energy operation is made possible in a system powered by solar cells.

[0003] Patent Document 2 discloses a first aggregation device that manages the power balance from predictions of power generation and demand, and a second aggregation device that provides power received from selling power based on a request from the first aggregation device. The second aggregation device discloses a method of transmitting notification information for proceeding with power supply to a moving body equipped with a storage battery. According to Patent Document 2, in order to adjust the supply-demand balance of the power system, it is possible to utilize surplus power of resources that are a plurality of electric vehicles (EVs) equipped with storage batteries.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Summary of the Invention

[0005] Resources are not always limited to just one purpose; some can be used for multiple purposes. In one type of use, for example, when transporting batteries or hydrogen storage devices as cargo, this transport resource plays the role of a power distribution resource through energy transport. In another type of use, for example, when controlling electric vehicles such as passenger buses as energy resources, these buses fulfill both the roles of passenger transport and power transport.

[0006] When providing resources useful for multiple purposes to various systems, it is necessary to define the characteristics of each resource individually in advance to ensure ease of use for each recipient system. However, no means of managing and controlling the same resource across multiple systems with different purposes is disclosed in any of the literature. Furthermore, by having multiple systems manage and control the same resource simultaneously, it is expected that the resource utilization rate will improve as multiple systems can use the same resource. However, conventional technologies assumed that the same resource would be managed and controlled so that only one system would occupy it during the same time period.

[0007] Therefore, the main objective of the present invention is to improve the utilization rate of resources provided to multiple types of systems. [Means for solving the problem]

[0008] To solve the aforementioned problems, the resource management device of the present invention has the following features. The present invention relates to a virtual resource capability conversion unit that, based on virtualization logic that virtualizes physical resources, creates virtual capability data indicating the capabilities that physical resources provide as virtual resources from physical resource measurement data obtained by measuring physical resources, which are equipment related to energy, and constructs a virtual resource that provides that virtual capability data. The system includes a capability allocation unit that assigns the virtual resources constructed by the virtual resource capability conversion unit to a resource operation management system, thereby causing the resource operation management system to manage the actual resources. The virtualization logic is prepared individually according to resource request data indicating the capability state of the physical resource requested by the resource operation management system. And, The virtualization logic converts the physical resource measurement data, which shows the movement history associated with the operation of the physical resource, into virtual capacity data, which shows the cargo transport capacity of the physical resource. It is characterized by the following. Other methods will be described later. [Effects of the Invention]

[0009] According to the present invention, the utilization rate of resources provided to multiple types of systems can be improved. [Brief explanation of the drawing]

[0010] [Figure 1] This is a configuration diagram showing the resource operation management system according to this embodiment. [Figure 2] This is a diagram illustrating the configuration of the resource virtualization system according to this embodiment. [Figure 3] This is a data flow diagram of the resource virtualization process of the resource virtualization system according to this embodiment. [Figure 4] This is a flowchart showing the processing procedure for resource virtualization in the resource virtualization system according to this embodiment. [Figure 5] This is a data flow diagram of the virtual resource capacity conversion unit according to this embodiment. [Figure 6] This table shows an example of the resource request data to be acquired in this embodiment. [Figure 7] This table shows an example of the virtualization definition data obtained in this embodiment. [Figure 8] This table shows an example of resource constraint data related to this embodiment. [Figure 9] This is an explanatory diagram of the processing of the virtualization logic "P0001" placed in the acquired capability conversion unit according to this embodiment. [Figure 10] It is an explanatory diagram in which the virtualization logics of "P0001", "P0002", and "P0003" related to this embodiment are arranged inside the capability conversion unit. [Figure 11] It is an explanatory diagram of the processing of the virtualization logic of "P0004" arranged inside the acquired capability conversion unit related to this embodiment. [Figure 12] It is an explanatory diagram of the processing of the virtualization logics of "P0005", "P0002", and "P0006" arranged inside the acquired capability conversion unit related to this embodiment. [Figure 13] It is a graph showing virtual capability data for specifically explaining "P0001" in FIG. 9 related to this embodiment. [Figure 14] It is a graph for specifically explaining "P0001", "P0002", and "P0003" in FIG. 10 related to this embodiment. [Figure 15] It is a table showing an example of resource relationship data related to this embodiment. [Figure 16] It is a data flow diagram of the capability prediction unit related to this embodiment. [Figure 17] It is a data flow diagram of the capability allocation unit related to this embodiment. [Figure 18] It is a table showing an example of request resource correspondence data related to this embodiment. [Figure 19] It is an explanatory diagram stating that physical resources related to this embodiment are allocated to the system. [Figure 20] It is an explanatory diagram showing an example of the data structure for virtualizing physical resources related to this embodiment. <� [Figure 21] It is a hardware configuration diagram of the resource virtualization system related to this embodiment. [Figure 22] It is a table showing an example of the virtual capability data of each virtual resource related to this embodiment.

Mode for Carrying Out the Invention

[0011] The mode for carrying out the present invention will be described in detail while referring to the drawings.

[0012] First, an overview of this embodiment will be described with reference to Figures 19 and 20. Figure 19 is an explanatory diagram illustrating the allocation of physical resources to the system. The horizontal axis of this diagram represents the time axis. Schedule 1900 shows the mode of resource provision in the conventional method. Schedule 1910 shows the mode of resource provision in this embodiment.

[0013] In Schedule 1900, the resource request period 1901 from Resource Operation Control System A and the resource request period 1902 from Resource Operation Control System B overlap for a portion of the time. Therefore, the physical resources are exclusively provided to the predetermined resource operation control system A only during the resource provision period 1903. In this way, the conventional method has an exclusive recipient for the physical resources, resulting in a low utilization rate of the physical resources. Furthermore, if we were to change the recipient of the physical resources from resource operation control system A to resource operation control system B, we would have to modify the specification data that describes the characteristics of the physical resources to match the resource requirements of resource operation control system B. However, since the resource requirements of resource operation control system A and resource operation control system B are not necessarily the same, changing the recipient was not easy.

[0014] On the other hand, Schedule 1910 converts one physical resource into one or more virtual resources, and each virtual resource is associated with virtual capability data that indicates its capabilities. For example, the following two virtual resources are generated from one physical resource: Virtual resource A is associated with virtual capability data of an actual resource that meets the capabilities required by resource operation control system A. Specifically, since resource operation control system A is a grid monitoring and control system, it requires a power supply capacity of 1915 and a discharge capacity of 1917. Therefore, if the actual resource is an electric vehicle, virtual resource A is constructed in which the power supply capacity of its battery (1915) and the discharge capacity of 1917 are described as virtual capability data. Virtual resource B is associated with virtual capability data of an actual resource that meets the capabilities required by resource operation control system B. Specifically, since resource operation control system B is a transportation system, a transportation capability of 1916 is required. Therefore, if the actual resource is an electric vehicle, virtual resource B is constructed in which its transportation capability of 1916 is described as virtual capability data. Thus, even if the electric vehicles are physically the same, the virtual resources used by the recipient system to manage the electric vehicle are defined individually to satisfy the requirements of that system.

[0015] Furthermore, the differences between Schedule 1900 and Schedule 1910 will be explained from the perspective of managing actual resources. In Schedule 1900, the resource request period 1901 and the resource provision period 1903 corresponded one-to-one, and one physical resource was exclusively provided to one system. In other words, managing a physical resource and using a physical resource were synonymous. In Schedule 1910, the resource request period 1901 from Resource Operation Control System A is replaced by the resource management request period 1911. Similarly, the resource request period 1902 from Resource Operation Control System B is replaced by the resource management request period 1912. As a result, Resource Operation Control System A can continuously manage the managed physical resource via virtual resource A during the resource management request period 1911. On the other hand, Resource Operation Control System B can continuously manage the managed physical resource via virtual resource B during the resource management request period 1912. In other words, one physical resource can be managed in parallel by two systems.

[0016] Management, in this context, involves notifying each system of the measured values ​​of the physical resources related to the virtual capability data that each system requests from the physical resources. For example, resource operation control system A requests power supply capacity 1915 and discharge capacity 1917 as virtual capability data, so virtual resource A is managed by resource operation control system A by constantly notifying it of the current battery level of the electric vehicle. Similarly, since the resource operation control system B obtains the transport capacity 1916 as virtual capacity data, virtual resource A is managed by the resource operation control system B by constantly notifying the resource operation control system B of the electric vehicle's current location and the current number of occupants.

[0017] On the other hand, regarding the use of physical resources, unless the location of use in resource operation control system A and the location of use in resource operation control system B are the same, the same physical resource will be used exclusively by each system. For example, an electric vehicle charges its battery one morning from resource operation control system A at location X with a power supply capacity of 1915. After charging, the electric vehicle is requested by the resource operation control system B at point P to transport the occupants to point Q during the day, and begins transport with a transport capacity of 1916. After dropping off the occupants at point Q, the electric vehicle is requested by the resource operation control system A at point Y at night to discharge the battery power with a discharge capacity of 1917.

[0018] Here, if the distance between points X and P is short, and the distance between points Y and Q is short, the two tasks of supplying power from point X to point Y and transporting personnel from point P to point Q can be executed in parallel in one day. In this way, electric vehicles can improve their utilization rate by having separate systems manage them during overlapping time periods and using different capacities with time differences. In other words, by converting physical resources into one or more virtual capacity data, they can be simultaneously controlled in accordance with the resource requests from each resource operation control system.

[0019] Figure 20 is an explanatory diagram showing an example of a data structure for virtualizing physical resources. Each entity resource is assigned an entity resource ID "AR001 to AR006". For example, the entity resource for a private car is assigned the entity resource ID "AR001". One or more virtual resources are constructed from a single physical resource. Each virtual resource is assigned a virtual resource ID, "VR001 to VR006". For example, from a physical resource with the ID "AR001", one virtual resource with the virtual resource ID "VR001" is constructed. Each virtual resource is associated with virtual capability data that it provides. The virtual capability data of a virtual resource is defined according to the requirements of the system to which the virtual resource is provided.

[0020] The virtual resource ID "VR003" is constructed from two physical resource IDs, "AR004" and "AR005". In this case, the capabilities provided by the two physical resources are combined to make them available as a single virtual resource. Furthermore, two virtual resources, virtual resource IDs "VR002" and "VR005," are constructed from the physical resource with physical resource ID "AR002." In this case, a single physical resource, a truck equipped with a battery, can be defined as both virtual resource ID "VR002," which provides power transmission capabilities, and virtual resource ID "VR005," which provides adjustable power capabilities.

[0021] A single system issues one or more request IDs "R0001" to "R0005". For example, a system called "Monitoring A" issues request ID "R0001" requesting virtual capability data for power supply, and also requests request ID "R0004" requesting virtual capability data for regulated power supply. Resource allocation is the process of associating one or more virtual resource IDs with a single request ID. For example, in Figure 20, an arrow is connected to the virtual resource ID "VR001" for the request ID "R0001" requested by the "Monitoring A" system. This allows the "Monitoring A" system to manage the virtual capability data, specifically power supply, provided by the virtual resource ID "VR001". In reality, the private car with the physical resource ID "AR001," which corresponds to the virtual resource ID "VR001," provides the capability of power supply to the "Monitoring A" system.

[0022] Furthermore, the passenger bus with physical resource ID "AR003" provides the capability of power transmission to the "Monitoring B" system via virtual resource ID "VR002," while also providing the capability of regulating power to the "Monitoring A" system via virtual resource ID "VR005." In this way, by virtualizing a single physical resource into multiple virtual resources, it becomes possible to manage it simultaneously from multiple systems, as shown in schedule 1910 in Figure 19.

[0023] Figure 1 is a configuration diagram showing the resource operation management system 1. As explained in Figure 19, the resource operation management system 1 enables operation in multiple resource operation control systems, each with different operational objectives, by creating virtual resources from actual resources 5 that are aligned with the operation of each resource operation control system. This enables more efficient operation and control of energy-related resources. Therefore, the resource operation management system 1 consists of a resource virtualization device 3, a data management device 4, physical resources 5, a measurement device 6, a monitoring and control device 7, an information input / output terminal 8, an information distribution device 9, a resource operation control device 10, and controlled equipment 12. The communication path 11 is, for example, a LAN (Local Area Network) or a WAN (Wide Area Network), and is a communication path 11 that connects the various devices and terminals that constitute the resource operation management system 1 so that they can communicate with each other.

[0024] The data management device 4 stores measurement data of the physical resource 5, constraint data such as conditions and constraints related to the operation and control of the physical resource 5, and data on factors that affect the operation of the physical resource 5. The physical resource 5 is, for example, the following equipment. • Generators that use fossil fuels • Generators that utilize renewable energy sources such as solar, geothermal, wind, and hydroelectric power. • Stationary battery storage • Mobile vehicles equipped with batteries, such as electric vehicles and electric buses Substation equipment such as transformers and phase-shifting equipment, and power transmission and distribution equipment. • An individual piece of equipment that produces, consumes, or stores energy, or a collection of two or more such pieces of equipment. Equipment refers to utility-side energy-consuming equipment such as lighting, air conditioning, and power systems.

[0025] The measurement data for physical resource 5 includes at least data recording the operation of physical resource 5 measured over time. The operation of physical resource 5 includes, for example, the amount of power generated, consumed, stored, transmitted and distributed, and movement history of physical resource 5. The constraint data for physical resource 5 includes at least data indicating the conditions and constraints related to the operation and control of physical resource 5. These conditions and constraints related to the operation and control of physical resource 5 include, for example, data indicating the operating range of quantities, times, and locations related to the operation of physical resource 5, such as the location of energy production, consumption, and storage, the possible time, and upper and lower limits on quantities, as well as data indicating the costs related to operation.

[0026] Factor data 453A (Figure 3) acquired from data management device 4 includes, for example, the following data. • Weather data such as temperature, humidity, solar radiation, wind speed, and atmospheric pressure. • Fuel data such as trading volume and price of crude oil and natural gas. • Transmission and distribution line data, such as transmission and distribution line capacity. • Generator operating status data, such as generator operation or maintenance schedules. • Calendar day data including year, month, and day, day of the week, and a flag value indicating the type of day (as arbitrarily set). • Data indicating whether or not sudden events such as typhoons or other events have occurred. • Data showing economic conditions such as the number of energy consumers, industry trends, and business sentiment indices. • Data showing the movement of people and vehicles, such as the occupancy rate of express trains, the number of passengers, the number of reserved seats, or road traffic conditions.

[0027] The data management device 4 stores measurement data and constraint data of the physical resource 5 from a pre-set past date and time to the most recent observation date and time, via one of the measurement device 6, monitoring and control device 7, or information input / output terminal 8. The data management device 4 also searches for and transmits measurement data and constraint data of the physical resource 5 in response to data acquisition requests from other devices.

[0028] Figure 2 is a diagram of the configuration of resource virtualization system (resource management device) 2. Resource virtualization system 2 consists of resource virtualization device 3 and data management device 4. The resource virtualization device 3 uses the data stored in the data management device 4 to convert the data of the physical resource 5 into "virtual resource data" that represents the virtual resource. Therefore, the resource virtualization device 3 has a virtual resource capacity conversion unit 351, a capacity prediction unit 352, a capacity allocation unit 353, and a control planning unit 354.

[0029] The virtual resource capability conversion unit 351 acquires measurement data and constraint data of the physical resource 5 from the data management device 4. The virtual resource capability conversion unit 351 converts the measurement data and constraint data of the physical resource 5 into "virtual capability data" that indicates the capability of the virtual resource, in order to match the resource request received from the resource operation control device 10, and configures the virtual resource based on the virtual capability data. In other words, the virtual resource capability conversion unit 351 creates virtual capability data based on virtualization logic that virtualizes the physical resource 5, which is an energy-related facility, from the physical resource measurement data 451A obtained by measuring the physical resource 5, and constructs a virtual resource that provides that virtual capability data. The virtualization logic is prepared individually according to the resource request data that indicates the capability status of the physical resource 5 requested by each resource operation management system 1 to which it is allocated. The virtualization logic is the logic that performs the conversion process from pre-configured physical resource measurement data 451A to virtual capability data in order to construct a virtual resource. In this specification, an ID starting with P, such as P0001, is assigned as the identifier for the virtualization logic.

[0030] The capacity prediction unit 352 identifies a model for predicting future values ​​of virtual capacity data based on past virtual capacity data output by the virtual resource capacity conversion unit 351 and factor data 453A acquired from the data management device 4. Using the identified model, the capacity prediction unit 352 calculates a predicted value, which is the future value of the virtual capacity data at a predetermined future date and time.

[0031] The capacity allocation unit 353 matches the resource request details obtained from the resource operation control device 10 with the virtual capacity data calculated by the capacity prediction unit 352, and allocates virtual resources to be used by the resource operation control device 10. In other words, the capacity allocation unit 353 assigns each virtual resource constructed by the virtual resource capacity conversion unit 351 to the resource operation management system 1, thereby allowing each resource operation management system 1 to manage the actual resources 5. The capacity allocation unit 353 may also assign each virtual resource constructed by the virtual resource capacity conversion unit 351 to the resource operation management system 1 based on the predicted values ​​calculated by the capacity prediction unit 352.

[0032] The control planning unit 354 generates a plan to control some or all of the physical resources 5 incorporated into the virtual resource. In other words, the control planning unit 354 generates a control plan for the physical resources 5 that constitute the virtual resource allocated by the capacity allocation unit 353, and instructs each allocated resource operation management system 1 to control the physical resources 5 based on that control plan. The virtual resource capacity conversion unit 351 modifies the virtual capacity data based on the control plan generated by the control planning unit 354. The control planning unit 354 may calculate the time change in energy-related virtual capacity data as the physical resource 5 operates, and reflect that time change in the virtual capacity data created by the virtual resource capacity conversion unit 351.

[0033] The resource operation control device 10 is a device that, for example, operates and controls the generation, consumption, transportation, and trading of energy. Based on the virtual capacity data output by the resource virtualization device 3, the resource operation control device 10 combines the controlled equipment 12 and virtual resources that it manages to create and execute a physical equipment operation plan to achieve a predetermined goal. In the energy field, the physical equipment operation plan is, for example, an operation plan for energy production equipment, distribution equipment, consumption equipment, and storage equipment. Specifically, the physical equipment operation plan is the following plan: • Planning the number of generators and batteries to be started and the output distribution of those generators and batteries. • Planning for charging or discharging control of electric vehicle chargers and charging stations. • Planning the distribution of gas and water flow rates and pressures through gas pipelines and water pipes. • Battery charge / discharge control plan to prioritize demand for electricity derived from renewable energy sources. In demand response, which is a form of electricity demand adjustment control, the planning and execution of demand adjustment control involves allocating the amount of demand adjustment to electricity consumers participating in demand response or to the demand facilities of electricity consumers. • In the transportation sector, for example, scheduling of transport vehicles such as buses and trucks for passenger and freight transport.

[0034] Furthermore, the operation plan for the equipment is not limited to direct execution by the entity using the resource operation control device 10, but may also be implemented indirectly. Indirect equipment operation in the power sector refers, for example, to the physical operation of equipment by another party based on a direct bilateral transaction contract or a transaction contract via an exchange. In this case, the execution plan of the transaction contract corresponds to the equipment operation plan.

[0035] The information input / output terminal 8 inputs data to the resource virtualization device 3 and the data management device 4, and displays the data stored or output by these devices. The data observation device 6 periodically measures or collects measurement data related to the operation of the physical resource 5 at predetermined time intervals and transmits it to the data management device 4. The information distribution device 9 transmits the measured and predicted values ​​of factor data 453A that affect the operation of the physical resource 5 to the data management device 4. The monitoring and control device 7 monitors and controls the physical resource 5.

[0036] The data management device 4 consists of a CPU 31 (Central Processing Unit) 41 that comprehensively controls the operation of the data management device 4, an input device 42, an output device 43, a communication device 44, and a storage device 45. The data management device 4 is an information processing device such as a personal computer, a server computer, or a handheld computer. The input device 42 consists of a keyboard or mouse, and the output device 43 consists of a display or printer. The communication device 44 is equipped with a NIC (Network Interface Card) for connecting to a wireless LAN or wired LAN. The storage device 45 is a storage medium such as RAM (Random Access Memory) or ROM (Read Only Memory). Output results and intermediate results from each processing unit may be output as appropriate via the output device 43.

[0037] The storage device 45 stores databases such as a real resource measurement data storage means 451, a real resource constraint data storage means 452, and a factor data storage means 453. The physical resource measurement data storage means 451 holds the physical resource measurement data 451A. The physical resource measurement data 451A is data that stores past observed values ​​regarding the operation of physical resource 5. Observed values ​​regarding the operation of physical resource 5 include, for example, the amount of power generated by the generator, the amount of charge and discharge of the storage battery, the amount of charge and remaining charge of the electric vehicle, the amount of discharge to the power grid, the movement history of mobile objects indicated by latitude and longitude or location identifiers such as GPS, and the movement history and transport content history of passenger transport and freight transport.

[0038] The physical resource constraint data storage means 452 holds physical resource constraint data 452A (Figure 8). Physical resource constraint data 452A is data that stores conditions and constraints related to the operation of physical resource 5. Conditions and constraints related to the operation of physical resource 5 include, for example, the following data. • Operating time range, including start and end dates and times for power generation, charging, energy storage and discharge, and movement. • Operating volume range including power generation, charging, storage and discharge, movement, etc. • Operating area range, including locations and movement ranges for power generation, charging, and energy storage / discharging. • Response time: The time required for the control response to be completed when accepting the control. • Whether or not it is possible to control whether or not changes to the operation of physical resource 5 can be accepted. • Whether the above conditions can be changed, the costs involved in operation, or the costs incurred as a result of accepting the control or changing the conditions.

[0039] Factor data storage means 453 holds factor data 453A. Factor data 453A is data that stores observed and predicted values ​​of various factors that affect the operation of the physical resource 5. Factors are, for example, the following data. • Weather data such as temperature, humidity, solar radiation, wind speed, and atmospheric pressure. • Energy consumption data such as electricity, gas, and water. • Power generation data from energy sources such as solar and wind power. • Status and planned data regarding generator shutdowns. • Power system data such as available capacity, current, and voltage for each transmission line, distribution line, or substation. • Market data such as trading volume and trading price of energy traded on exchanges. • Calendar day data including year, month, and day, day of the week, and a flag value indicating the type of day (as arbitrarily set). • Data indicating whether or not sudden events such as typhoons or other events have occurred. • Data showing economic conditions such as the number of energy consumers, industry trends, and business sentiment indices. • Data showing the movement of people and vehicles, such as the occupancy rate of express trains, the number of passengers, the number of reserved seats, or road traffic conditions. This also includes past observational data of the subjects of the above predictions, or the prediction result data itself.

[0040] The resource virtualization device 3 consists of a CPU 31 that comprehensively controls the operation of the resource virtualization device 3, an input device 32, an output device 33, a communication device 34, and a storage device 35. The resource virtualization device 3 is an information processing device such as a personal computer, a server computer, or a handheld computer. The storage device 35 stores databases such as a virtualization definition data storage means 357, a virtualization logic pool data storage means 358, and a resource relationship data storage means 359.

[0041] The virtualization definition data storage means 357 holds virtualization definition data 357A (Figure 7). The virtualization definition data 357A is data that shows the correspondence between the resource request content received from the resource operation control device 10 and the virtualization logic for constructing a virtual resource that satisfies the request. The virtualization logic pool data storage means 358 holds the virtualization logic pool 358A. The virtualization logic pool 358A stores one or more pre-configured virtualization logics. Examples of virtualization logic are given below. • Virtualization logic that converts the physical quantities in the actual resource measurement data 451A into virtual capability data representing a different type of physical quantity. • Virtualization logic that generates new virtual capability data from a combination of two or more existing virtual capability data sets. • Virtualization logic that converts the physical resource measurement data 451A, which shows the remaining energy associated with the operation of physical resource 5, into virtual capacity data that shows the positive or negative energy supply capacity of physical resource 5. • Virtualization logic that converts physical resource measurement data 451A, which shows the movement history associated with the operation of physical resource 5, into virtual capacity data that shows the cargo transport capacity of physical resource 5. Virtualization logic that uses physical resource measurement data 451A indicating the positive or negative energy supply capacity of physical resource 5 and physical resource measurement data 451A indicating the cargo transport capacity of physical resource 5 to convert into virtual capacity data indicating the energy transport capacity of physical resource 5.

[0042] The resource-related data storage means 359 holds resource-related data 359A (Figure 15). Resource-related data 359A is data that shows the correspondence between a virtual resource and the actual resource 5 that constitutes the virtual resource. Resource-related data 359A is shown, for example, as an arrow from the private car "AR001" to the virtual resource "VR001" in Figure 20.

[0043] The storage device 35 also stores various computer programs, such as a virtual resource capacity conversion unit 351, a capacity prediction unit 352, a capacity allocation unit 353, and a control planning unit 354. The virtual resource capacity conversion unit 351 executes the following processes in order. Input the actual resource measurement data 451A and the actual resource constraint data 452A. The virtualization logic in the virtualization logic pool 358A is used to convert the measurement data of each physical resource 5 contained in the physical resource measurement data 451A into virtual capability data. Information indicating which virtualization logic to use is stored in the virtualization definition data 357A. The system constructs a virtual resource that satisfies the resource request received from the resource operation control device 10, by combining it with virtual capability data. • Outputs the constructed virtual capability data. • The selection is made based on the correspondence data between the resource request content received from the resource operation control device 10 and the virtualization logic.

[0044] The capacity prediction unit 352 receives the virtual capacity data output by the virtual resource capacity conversion unit 351 and the factor data 453A, identifies a prediction model that calculates a predicted value indicating the capacity at a predetermined future date and time, calculates the predicted value, and outputs the predicted value to the capacity allocation unit 353. The capacity allocation unit 353 compares the predicted value of the virtual capacity data output by the capacity prediction unit 352 with the resource request content obtained from the resource operation control device 10, and determines the virtual resources to be provided to the resource operation control device 10.

[0045] The control planning unit 354 generates and outputs a control plan for the physical resource 5 that constitutes the virtual resource in any of the following cases: - If the capacity allocation unit 353 determines that the predicted value of the virtual capacity data output by the capacity prediction unit 352 does not match the resource request content obtained from the resource operation control device 10, • When the resource request from the resource operation control device 10 is changed The physical resource 5 that constitutes the virtual resource is obtained from resource relationship data 359A.

[0046] The processing and data flow of the resource virtualization system 2 will be described below with reference to Figures 3 and 4. Figure 3 is a data flow diagram of the resource virtualization process in resource virtualization system 2. The data management device 4 receives physical resource measurement data 451A from the measurement device 6 or the monitoring and control device 7 and stores it in the physical resource measurement data storage means 451. The data management device 4 also receives physical resource constraint data 452A from the information input / output terminal 8 and stores it in the physical resource constraint data storage means 452. The data management device 4 also receives factor data 453A from the information distribution device 9 and stores it in the factor data storage means 453.

[0047] The virtual resource capacity conversion unit 351 executes the following processes in order. - Obtain measurement data for one or more physical resources 5 recorded in physical resource measurement data 451A from physical resource measurement data 451A within a predetermined date and time range. • Data regarding constraints and conditions for the operation of acquired physical resource 5 is obtained from physical resource constraint data 452A. - Using the resource request data input from the resource operation control device 10 via the capacity allocation unit 353 as a key, an identifier indicating the virtualization processing logic for converting the measurement data of the physical resource 5 into virtual capacity data is obtained from the virtualization definition data 357A. The virtualization processing logic is retrieved from the virtualization logic pool 358A using an identifier indicating the acquired virtualization processing logic as the key. The acquired virtualization processing logic is then input with the acquired physical resource measurement data 451A and physical resource constraint data 452A for each physical resource 5, and converted into virtual capability data. • Virtual resources are constructed by combining virtual capability data. • Output the identifier indicating the constructed virtual resource and data indicating its capabilities as virtual capability data. The virtual resource capability conversion unit 351 stores resource relationship data 359A, which indicates the correspondence between the virtual resource and the physical resource 5 that constitutes the virtual resource, in the resource relationship data storage means 359.

[0048] The capability prediction unit 352 executes the following processes in order. The virtual resource data output by the virtual resource capacity conversion unit 351 and factor data 453A are acquired from the data management device 4. Identify predictive models for calculating predicted values ​​of virtual capability data. By inputting predetermined future date and time factor data 453A into the identified prediction model, the predicted value of the virtual capability data is calculated. The predicted values ​​of the data indicating capacity and the identifiers indicating virtual resources are combined and output as virtual resource capacity prediction result data.

[0049] The capacity allocation unit 353 executes the following processes in order. The system acquires virtual resource capacity prediction result data from the capacity prediction unit 352 and resource request details from the resource operation control device 10. • Determine whether the predicted values ​​of the virtual resource capacity data shown in the virtual resource capacity prediction result data satisfy the resource requirements. If it is determined that the requirements are met, the virtual resource is registered as one to be used for the control and operation of the resource operation control device 10. If it is determined that the requirement is not met, control plan generation instruction data is output to the control planning unit 354 to initiate the process of generating a control plan that modifies the operation of the physical resource 5 that constitutes the virtual resource.

[0050] The control planning unit 354 executes the following processes in order. • Operation begins upon receipt of control plan generation instruction data from the capacity allocation unit 353. The system acquires resource-related data 359A, generates control plans for one or more physical resources 5 that constitute the virtual resource for which control plan generation is targeted, and outputs them as control plan data. The output control plan data is input to the capacity prediction unit 352, and the capacity prediction unit 352 recalculates and outputs the predicted value of the virtual capacity data after the control plan has been executed.

[0051] Figure 4 is a flowchart showing the processing procedure for resource virtualization in the resource virtualization system 2. This flowchart shows a process that begins when one of the following events occurs, and the resource virtualization device 3 executes the processes from step S401 to step S405. • Resource virtualization device 3 received input from the device user. • The resource operation control device 10 has received a request for resources. • The pre-set execution time has arrived. In practice, processing is performed based on various computer programs stored in the CPU 31 and storage device 35 of the resource virtualization device 3, as well as various computer programs stored in the CPU 41 and storage device 45 of the data management device 4. For the sake of explanation, the processing entities will be described as the resource virtualization device 3 and the various computer programs contained within it.

[0052] The virtual resource capacity conversion unit 351 acquires physical resource measurement data 451A and physical resource constraint data 452A from the data management device 4, and resource request content data (Figure 6) from the capacity allocation unit 353. It then uses the resource request content data and virtualization definition data 357A to acquire virtualization processing logic from the virtualization logic pool 358A, and uses the acquired logic to convert the physical resource measurement data 451A into virtual capacity data. Finally, it combines the virtual capacity data to create a virtual resource (S401).

[0053] The capacity prediction unit 352 identifies a prediction model for calculating predicted values ​​of virtual capacity data from the virtual resource data output by the virtual resource capacity conversion unit 351 and the factor data 453A acquired from the data management device 4. Then, the capacity prediction unit 352 calculates predicted values ​​of virtual capacity data by inputting the factor data 453A for predetermined future dates and times into the identified prediction model (S402). The capability prediction unit 352 may also modify the predicted value of the virtual capability data calculated in S402 using the control plan for the physical resource 5 described later in S404.

[0054] The capacity allocation unit 353 obtains virtual resource capacity prediction result data from the capacity prediction unit 352 and obtains resource request details from the resource operation control device 10 (S403). The capacity allocation unit 353 then determines whether the predicted value of the virtual capacity data shown in the virtual resource capacity prediction result data satisfies the resource request details (S403A). If the answer to S403A is Yes, the capacity allocation unit 353 registers the virtual resources that it determined in the determination in S403 to satisfy the resource request received from the resource operation control device 10 as resources to be used for the control operation of the resource operation control device 10, and transmits them to the resource operation control device 10 (S405).

[0055] If the answer in S403A is No, then control plan generation instruction data is output to the control planning unit 354 to initiate the process of generating a control plan that modifies the operation of the physical resource 5 that constitutes the virtual resource, thereby determining whether or not to issue an instruction to change the resource configuration (S403B). If the answer to S403B is Yes, then return to S401 and perform the resource configuration change, which will alter the calculation result of S402, which will be executed again. If the answer in S403B is No, the control planning unit 354 acquires resource-related data 359A and generates a control plan for one or more physical resources 5 that constitute the virtual resource for which the control plan is to be generated (S404). The generated control plan data is input to the capability prediction unit 352, which changes the calculation result of S402, which is executed again. Thus, regardless of whether the branch result of S403B is Yes or No, the calculation result of S402, which is executed again, will change, so the judgment result of S403A, which is executed again, may change to Yes.

[0056] Furthermore, the capacity allocation unit 353 outputs virtual resource regeneration instruction data to the virtual resource capacity conversion unit 351 to re-execute the virtual resource formation process in any of the following cases. Then, the process is restarted from S401. - If the number of times control plan generation instruction data is output to the control planning unit 354 exceeds a predetermined number. If no change is found in the predicted value of the virtual capability data obtained from the capability prediction unit 352.

[0057] Detailed embodiments of each component will be described below with reference to Figures 5 to 7. Figure 5 is a data flow diagram of the virtual resource capacity conversion unit 351. The virtual resource capability conversion unit 351 converts the actual resource measurement data 451A into virtual capability data. It then constructs a virtual resource by combining the virtual capability data and outputs an identifier indicating the constructed virtual resource and data indicating its capability as virtual capability data.

[0058] The capacity conversion definition extraction unit 351A obtains resource request data from the capacity allocation unit 353. Figure 6 is a table showing an example of the resource request data to be retrieved. The table in Figure 6 stores the following data in each column. • The first column contains a "Request ID" which indicates the identifier of the request. • The second column contains the "Requesting System Name," which indicates the name of the resource operation control system 10 that submitted the request. • The third column shows the name of the requested resource, "Requested Resource Name". • The fourth column shows the "request period" indicating the resource request period. • The fifth column shows the "request amount," indicating the amount of resources requested. • The sixth column shows the requirements for resource quality, labeled "Requirements." • The 7th column shows the "request location," indicating the details of the request to the resource supply location.

[0059] The first row of the table in Figure 6 contains the following data as the request content for request ID "R0001". • The requested system name is a request submitted by "System Monitoring and Control System A". The requested resource is "power supply resource". The application period is one year, from "2020 / 01 / 01 00:00 to 2021 / 12 / 31 23:59". The requested quantity is "more than 100 MW per hour in terms of supply." The required location is "to supply to point A". • The required quality is "-", indicating that there are no quality requirements.

[0060] The second row of the table in Figure 6 contains the following data as the request content for request ID "R0002". • The requested system name is a request submitted by "System Monitoring and Control System B". The requested resource is "power transmission resources". The request period is one day, from 00:00 on 2020 / 01 / 01 to 23:59 on 2021 / 01 / 01. The required quantity is "more than 10 MW per hour in terms of transport volume." The requirements for resource quality are that "the acceptable range for fluctuations in transport volume is within ±3%, and the acceptable range for the start and end times of transport is within ±30 minutes." The requested location is "transport from location A to location B".

[0061] Figure 22 is a table showing an example of virtual capability data for each virtual resource. The table in Figure 22 stores at least the following data in each column: The first column stores data indicating the identifier of the virtual resource formed in the virtual resource capability conversion unit 351. The second column contains data indicating the date and time. The third column contains data showing the virtual capacity value of the virtual resource shown in the first column for each date and time shown in the second column. The fourth column contains data indicating the unit of the virtual capability value shown in the third column. The fifth column contains data showing the operational status of the virtual resource shown in the first column at the date and time shown in the second column. The sixth column contains data indicating the location where the virtual resource shown in the first column was running at the date and time shown in the second column.

[0062] In Figure 22, for the sake of simplicity, all virtual resource identifiers shown in the first column are set to "VR001". Similarly, for the sake of simplicity, the dates and times shown in the second column are set to one-hour intervals, ranging from 0:00 on January 1, 2021 to 23:00 on December 31, 2021. Here, the virtual resource ID "VR001" is the virtual resource associated with request ID "R0001," as shown in Figure 20. Request ID "R0001" is the request received from "System Monitoring and Control System A," as shown in the first line of the resource request data in Figure 6.

[0063] According to the request details in the first row of Figure 6, the request period is "from January 1, 2021, 00:00 to December 31, 2021, 23:59", the request quantity is "a supply of 100 MW / h or more", and the request location is "Location A". The virtual capacity data shown in Figure 22 indicates that virtual resource ID "VR001" has a power supply capacity of 100 MW / h or more at location A from "0:00 on January 1, 2021" to "23:00 on December 31, 2021". Therefore, the requirement satisfaction evaluation unit 353B determines that virtual resource "VR001" satisfies the requirement of requirement ID "R0001".

[0064] Figure 7 is a table showing an example of the acquired virtualization definition data 357A. The capability conversion definition extraction unit 351A acquires the virtualization definition data 357A. The table in Figure 7 stores the following data in each column. The first column stores identifiers for resource requests received from the resource operation control device 10 via the capacity allocation unit 353. The second column stores identifiers for the virtualization logic that are configured and registered to correspond to the resource request. The third column contains data indicating the operational details of the physical resource 5 applied to the processing of the virtualization logic.

[0065] For example, the first line indicates that, in response to the resource request content of "R0001", the virtualization logic of "P0001" is used to configure and register the conversion of the actual resource measurement data 451A of actual resource 5, whose operation content is "discharge or storage / discharge", into virtual capacity data.

[0066] The second line also indicates the following: The resource request for "R0002" utilizes multiple virtualization logics: "P0001", "P0002", and "P0003". First, the processing is performed using "P0001" and "P0002" respectively, and then the processing result data from each is entered into "P0003" and processed there. The system is configured to convert the physical resource measurement data 451A of physical resource 5, whose operation is "discharge or storage / discharge and movement," into virtual capacity data.

[0067] The fourth line also indicates the following: For request ID "R0004", three virtualization logics are used: "P0005", "P0002", and "P0006". The virtualization logic for "P0002" uses the same logic as the virtualization logic used for request ID "R0002". The capacity conversion definition extraction unit 351A uses the identifier of the resource request content obtained from the capacity allocation unit 353 as a key to obtain the identifier of the virtualization logic and processing order information from the virtualization definition data 357A shown in Figure 6, and outputs it to the capacity conversion unit 351B.

[0068] Figure 8 is a table showing an example of the actual resource constraint data 452A. The capacity conversion unit 351B first obtains the actual resource measurement data 451A and the actual resource constraint data 452A from the data management device 4. The table in Figure 8 stores the following data in each column. The first column is the identifier for entity resource 5. The second column contains data indicating the name of the physical resource 5. The data from the third column onward shows the details of the constraints for each entity resource 5. The third column contains data indicating the operational capabilities of each entity resource 5. The fourth column contains data indicating whether control of each entity resource 5 is accepted or not. The fifth column contains data indicating the period and time slots during which each entity resource 5 is operational. The sixth column shows the cost incurred when each of the five physical resources operates as a virtual resource. The 7th column shows whether or not the constraint data for each entity resource 5 can be changed.

[0069] For example, the first row's entity resource ID "AR001" and entity resource name "Private car" for entity resource 5 represent the following: • Capable of both "storage and discharge" and "mobility" operation. • Acceptance of the control is "not possible". The operating hours are from 8:00 AM to 4:00 PM. There are "no" costs incurred when operating as a virtual resource. • Entity resource 5 presents the constraint that "changes to the aforementioned constraints are not permitted".

[0070] Note that a physical resource 5 is not necessarily limited to a single physical device. For example, it may be a collection of physical device enclosures, such as the "factory customer" shown with physical resource ID "AR005," or a collection of multiple physical resources 5, such as the "virtual resource A" shown with physical resource ID "AR007."

[0071] The capability conversion unit 351B then retrieves virtualization logic from the virtualization logic pool 358A using the virtualization logic identifiers "P0001~P0006, etc." obtained from the capability conversion definition extraction unit 351A. The capability conversion unit 351B then processes the virtualization logic according to the processing order obtained from the capability conversion definition extraction unit 351A.

[0072] The specific processing flow of the capability conversion unit 351B will be explained below using Figures 7 to 15. The virtualization logic within the capability conversion unit 351B is complex because the capabilities required of the physical resource 5 vary widely depending on the requesting system. As mentioned above, Figure 7 shows the virtualization definition data 357A obtained from the capability conversion definition extraction unit 351A, which indicates the ID of the virtualization logic to be applied and the processing order of the virtualization logic for each identifier in the request content data. For example, the first row of Figure 7 indicates that the virtualization logic for "P0001" should be applied to the request ID "R0001". Therefore, the capability conversion definition extraction unit 351A obtains the virtualization logic for "P0001" from the virtualization logic pool 358A and places it in the capability conversion unit 351B.

[0073] Figure 9 is an explanatory diagram of the processing of the virtualization logic of "P0001" located within the acquired capability conversion unit 351B. First, the virtualization logic "P0001 (351B1)" located in the capacity conversion unit 351B acquires actual resource measurement data 451A from the data management device 4 in the charge level estimation unit 351B11 and estimates time-series data of the charge level. The acquired actual resource measurement data 451A is indicated as "discharge or charge / discharge" in the "Operation details" section of Figure 7. Therefore, the remaining charge estimation unit 351B11 acquires at least "AR001", "AR002", "AR003", "AR004", "AR005", "AR006", and "AR007", which are indicated as "energy storage or energy storage / discharging" in the "Operational Content" of the actual resource constraint data in Figure 8.

[0074] Then, the remaining charge estimation unit 351B11 performs the remaining charge estimation process by executing either (estimation method 1) or (estimation method 2) below on the acquired physical resource measurement data 451A of each physical resource 5. (Estimation Method 1) If the acquired actual resource measurement data 451A is the time-series data of the remaining charge itself, it is output as is. (Estimation Method 2) If the acquired physical resource measurement data 451A is time-series data of the charging history of a charger or time-series data of the charging history of each device such as an electric vehicle connected to the charger, the amount of charge from the start to the end of charging is calculated. Then, the amount of charge calculated from the past maximum charge is divided by this value to calculate the remaining charge at the start of charging. The remaining charge during charging is estimated using the amount of charge. From the end of charging until the end of charger connection, the amount of charge is estimated to be the sum of the remaining charge at the start of charging and the amount of charge charged during charging.

[0075] The minimum remaining charge estimation unit 351B12 acquires time-series data of estimated remaining charge values ​​from the past to the latest date and time output by the remaining charge estimation unit 351B11 and the physical resource constraint data 452A, and estimates the minimum allowable remaining charge value of the physical resource 5. Specifically, it estimates the minimum value in the time-series data of estimated remaining charge values ​​from the past to the latest date and time output by the remaining charge estimation unit 351B11 as the minimum allowable remaining charge value of the physical resource 5. Furthermore, if the resource constraint data 452A contains data indicating the minimum allowable charge level of the resource in question, the value of that constraint is estimated as the minimum allowable charge level.

[0076] The power supply capacity calculation unit 351B13 obtains time-series data of estimated remaining charge values ​​from the past to the latest date and time output by the remaining charge estimation unit 351B11, and the minimum allowable remaining charge value output by the minimum remaining charge estimation unit 351B12, and calculates the power supply capacity of the physical resource 5.

[0077] Figure 13 is a graph showing virtual capability data to specifically explain "P0001" in Figure 9. The white (uncolored) bar graph shown on the left side of Figure 13 represents the time-series data of the estimated remaining charge of the physical resource 5 from the past to the most recent date and time, output by the remaining charge estimation unit 351B11. The dotted line (1303) in the figure indicates the minimum allowable remaining charge estimated and output by the minimum remaining charge estimation unit 351B12. Here, the time periods 1301 and 1302, when the device is connected to the charger after charging is complete, are the time periods when power can be supplied (reverse power).

[0078] The gray (filled) bar graph shown on the right side of Figure 13 represents virtual capacity data for power supply capacity. The power supply capacity calculation unit 351B13 converts the data into power supply capacity data shown in 1304 and 1305 of the figure on the right, for the time periods 1301 and 1302 when the device is connected to the charger after charging is complete. When the power supply capacity calculation unit 351B13 calculates the power supply capacity data, for physical resources 5 that have operational constraints in the acquired physical resource constraint data 452A, the data is converted to power supply capacity data after satisfying the constraints. For example, in the physical resource constraint data 452A shown in Figure 8, the operating time period for physical resource "AR001" is indicated as "08:00 to 16:00". Therefore, for time periods other than this, the power supply capacity data converted from the physical resource measurement data 451A for the physical resource 5 is always converted to zero.

[0079] Furthermore, other examples of virtualization logic placement in the capability conversion unit 351B will be explained. Additionally, for the request ID "R0002" shown in the second row of Figure 7, it is shown that three virtualization logics, "P0001," "P0002," and "P0003," are applied. Furthermore, the processing procedure is set to first operate "P0001" and "P0002" respectively, and then operate "P0003" using the resulting data as input to convert it into virtual capability data. Therefore, the capability conversion definition extraction unit 351A acquires the virtualization logics "P0001," "P0002," and "P0003" from the virtualization logic pool 358A and places them in the capability conversion unit 351B according to the set processing order.

[0080] Figure 10 is an explanatory diagram showing the virtualization logics "P0001", "P0002", and "P0003" arranged within the capability conversion unit 351B. The virtualization logic "P0001(351B1)" located in the capacity conversion unit 351B includes a charge level estimation unit 351B11. The charge level estimation unit 351B11 acquires the physical resource measurement data 451A of the physical resource 5 that matches the "discharge or charge / discharge and movement" shown in the third column of the operation content data for request ID "R0002" in Figure 7 from the data management device 4. Then, the charge level estimation unit 351B11 estimates the time-series data of the power supply capacity of each physical resource 5 using the acquired physical resource measurement data 451A. Here, "P0001(351B1)" is the same as the "P0001(351B1)" mentioned above, and the data indicating the power supply capacity is calculated by the processing procedure described above.

[0081] The station location estimation unit 351B21 of the virtualization logic "P0002 (351B2)" acquires physical resource measurement data 451A from the data management device 4 for physical resource 5 that matches the operation content data shown in the third column of request ID "R0002" in Figure 7, which is "discharge or storage / discharge, and movement". Then, the station location estimation unit 351B21 uses the acquired physical resource measurement data 451A to estimate the time-series data of the departure location when each physical resource 5 is moving.

[0082] The method for estimating time-series data is as follows: For example, if the actual resource measurement data 451A is time-series data of latitude and longitude information for each time interval, such as GPS data, then the time periods and locations where the resource is stationary at the same latitude and longitude within a predetermined time range are extracted, and these locations are estimated as stationary locations. Next, the transport capacity calculation unit 351B22 receives the time-series data of the stationary locations of the resource 5 calculated by the stationary location estimation unit 351B21 from the past to the present, and converts it into data indicating the mobility capacity of the resource 5. The stop location estimation unit 351B21 estimates, for example, that a certain estimated stop location has the capacity to "collect" some cargo during the time it is stopped at that stop. The stop location estimation unit 351B21 also estimates that the cargo has the capacity to "arrive" at the next stop, and estimates that the cargo has the capacity to "transport" between the two stops, and converts this into data indicating the aforementioned series of transport capacities.

[0083] Finally, the power transmission capacity calculation unit 351B31 of "P0003 (351B3)" receives the data indicating the power supply capacity, the data indicating the mobility capacity, and the physical resource constraint data 452A calculated by P0001 and P0002, respectively. The power transmission capacity calculation unit 351B31 converts this into data indicating the power transmission capacity of the physical resource 5.

[0084] Figure 14 is a graph that provides a detailed explanation of "P0001," "P0002," and "P0003" in Figure 10. Graph 1401 shows time-series data of the remaining charge of a certain physical resource 5 estimated by the remaining charge estimation unit 351B11 of P0001. The power supply capacity calculation unit 351B13 then takes the estimated time-series data of the remaining charge shown in Graph 1401 as input and calculates the data shown in Graph 1402 as data indicating the power supply capacity of the physical resource 5. For example, the physical resource 5 is being charged with electricity from the charger during time period 1401A in graph 1401. Therefore, the power supply capacity calculation unit 351B13 calculates the negative supply capacity shown in time period 1402A in graph 1402, assuming that the physical resource 5 has "negative supply capacity" during that time period. Then, in time period 1401B of graph 1401, the power supply capacity calculation unit 351B13 estimates that the physical resource 5 is connected to the charger but is not being charged, and estimates that it has the capacity to supply (reverse power) the remaining charge through the charger during this time period. As a result, it calculates a positive supply capacity as shown in time period 1402B of graph 1402.

[0085] Note that power supply capacity decreases over time after power supply begins. Therefore, as shown in time zone 1402B, the positive supply capacity is calculated to decay over time. The degree of decay may be calculated based on the specification information of the hourly power supply amount of the physical resource 5 in question, which has been acquired in advance. Alternatively, it may be calculated based on the specification information of a physical resource 5 of the same type as the physical resource 5 in question, or it may be estimated from past power supply capacity data of the physical resource 5 in question, or it may be calculated according to a predetermined coefficient.

[0086] Next, Graph 1403 shows the time-series data of the stopping location and stopping time of the physical resource 5 estimated by the stopping location estimation unit 351B21 in P0002 (351B2). This means that the physical resource 5 is estimated to have stopped at "location A" in time period 1403A, then moved after some time, and stopped at "location B" in time period 1403B. Then, P0002 (351B2) estimates data indicating the transport capacity of the physical resource 5 from the estimated stopping location result data shown in Graph 1403. Specifically, as shown in Graph 1404, it is estimated that the physical resource 5 has the capacity to "collect" while stopped at location A (time period 1404A). This means that it is presumed to have the capacity to "transport" the next collected cargo (time zone 1404B), and then to have the capacity to "arrive" the cargo at point B (time zone 1404C).

[0087] Finally, the power transmission capacity calculation unit 351B31 of P0003 takes as input the data showing the power supply capacity of the physical resource 5 calculated by P0001 (graph 1402), the data showing the transmission capacity of the physical resource 5 calculated by P0002 (graph 1404), and the physical resource constraint data 452A, and converts them into data showing the power transmission capacity shown in graph 1405. Specifically, 1402A in graph 1402 is estimated to have negative supply capacity (charging) at point A, and at the same time, as shown in time period 1404A in graph 1404, it is estimated to have collection capacity at point A.

[0088] Therefore, the power transmission capacity calculation unit 351B31 estimates that, as shown in time period 1405A of graph 1405, the actual resource 5 has the capacity to load electricity at point A during that time period. Similarly, in time period 1402B of graph 1402, it is estimated that point B has a positive supply capacity (reverse current), and at the same time, as shown in time period 1404C of graph 1404, it is estimated that point B has the capacity to receive electricity.

[0089] Therefore, the power transmission capacity calculation unit 351B31 estimates that the actual resource 5 has the capacity to unload the cargo of electricity at point B during the time period 1405B shown in graph 1405. Based on the estimation result that the resource has the capacity to transport cargo during the time period 1404B shown in graph 1404 when it moves from point A to point B, the power transmission capacity calculation unit 351B31 estimates that the resource has the capacity to load the cargo of electricity at point A, transport it to point B, and unload it at point B.

[0090] Furthermore, other examples of virtualization logic placement in the capacity conversion unit 351B will be described. The request ID "R0003" shown in the third row of Figure 7 is defined to apply the actual resource measurement data 451A of the actual resource 5 whose operation is "discharge or storage / discharge and renewable energy" to the virtualization logic "P0004" and convert it into virtual capacity data.

[0091] Figure 11 is an explanatory diagram of the processing of the virtualization logic of "P0004" located within the acquired capability conversion unit 351B. The renewable energy supply capacity calculation unit 351B41, located at P0004 (351B4), acquires physical resource measurement data 451A and physical resource constraint data 452A from the data management device 4. The renewable energy supply capacity calculation unit 351B41 then takes the acquired physical resource measurement data 451A and physical resource constraint data 452A as input and converts them into data indicating the renewable energy supply capacity of each physical resource 5. For example, if the data stored in the physical resource measurement data 451A is the remaining charge and discharge amount of the physical resource 5 as a battery, the value of the amount of electricity derived from renewable energy is separated from the data of the remaining charge and discharge amount, and the separated value is calculated as data indicating the renewable energy supply capacity. The method for separating the value of electricity derived from renewable energy may be a known method such as traceability of renewable energy generation. If the data stored in the physical resource measurement data 451A is originally actual data on the amount of renewable energy generation, that actual data is output as is.

[0092] Furthermore, other examples of virtualization logic placement in the capacity conversion unit 351B will be explained. The request ID "R0004" shown in the fourth row of Figure 7 is defined to apply the actual resource measurement data 451A of the actual resource 5 whose operation content is "cargo transport" to the virtualization logic "P0005", "P0002", and "P0006" to convert it into virtual capacity data.

[0093] Figure 12 is an explanatory diagram of the processing of the virtualization logic "P0005", "P0002", and "P0006" located within the acquired capability conversion unit 351B. First, P0005 (351B5), located in the capacity conversion unit 351B, acquires physical resource measurement data 451A from the data management device 4. Based on the "cargo transport" operation shown in the third column of Figure 7, the P0005 acquires at least the physical resource measurement data 451A for the physical resource ID "AR003" whose "operable content" in the participant name of the physical resource constraint data 452A shown in Figure 8 is "cargo transport".

[0094] The available capacity estimation unit 351B51 of P0005 receives the physical resource measurement data 451A as input and estimates the available capacity of each physical resource 5 at each time. For example, if the measurement data content of the physical resource measurement data 451A is the number of passengers measured at each time or at each specific location, the unit calculates the number of passengers that can be accommodated by dividing the number of passengers by the maximum number of passengers for the physical resource 5, and outputs this as the estimated available capacity for each time or location.

[0095] The capacity cargo conversion unit 351B52 of P0005 generates a function for calculating the possible cargo load from the available capacity of the physical resource 5. The method for generating the function may be to pre-set data for the correspondence between available capacity and the possible cargo load, for example, if the available capacity is "10 people", the possible cargo load is "5 items of 80 cm size", and if it is "5 people", the possible cargo load is "2 items of 80 cm size", or to identify a model that calculates the possible cargo load for a given available capacity using a regression model such as a multiple regression model based on past cargo loading history and the available capacity data at that time.

[0096] The cargo load capacity calculation unit 351B53 then inputs the data indicating the available capacity calculated by the available capacity estimation unit 351B51 into a function that calculates the possible cargo load from the available capacity calculated by the capacity cargo conversion unit 351B52, thereby calculating data indicating the possible cargo load capacity of the physical resource 5. In this calculation, during periods when the constraints of the physical resource 5 shown in the physical resource constraint data 452A cannot be satisfied, the possible cargo load is calculated as zero.

[0097] Furthermore, in P0002 (351B2) located in the capacity conversion unit 351B, data indicating the transport capacity of the physical resource 5 is calculated using the method described in Figure 10.

[0098] Then, P0006 (351B6), located in the capacity conversion unit 351B, receives data indicating the cargo load capacity calculated by P0005, data indicating the transport capacity calculated by P0002, and the physical resource constraint data 452A into the cargo transport capacity calculation unit 351B61, and calculates data indicating the cargo transport capacity of each physical resource 5. For example, if the cargo load capacity at time T is "five 80cm-sized cargoes", and the transport capacity at time T is "collection", and the transport capacity at time T+N is "arrival", then the physical resource 5 is calculated to have the cargo transport capacity to transport "five 80cm-sized cargoes" from time T to time T+N.

[0099] Based on the processing operations described above, the capacity conversion unit 351B converts the measurement data of each physical resource 5 stored in the physical resource measurement data 452A into virtual capacity data according to the resource request data obtained from the capacity allocation unit 353. The resource formation unit 351C generates one virtual capability data by summing the virtual capability data of each physical resource 5 output by the capability conversion unit 351B at each given time, and outputs the data, which includes the identifier of the virtual resource, the identifiers of the physical resources 5 that constitute the virtual resource, and the virtual capability data, to the capability prediction unit 352 as virtual resource data. The resource formation unit 351C may select all of the physical resources 5 output by the capability conversion unit 351B, or it may select some of the physical resources 5, as a method for selecting the physical resources 5 to be added to (associated with) the virtual resource.

[0100] For example, in Figure 20, the virtual resource VR001 is composed of only "AR001" selected from the physical resources 5 "AR001~AR006". The resource formation unit 351C selected "AR001" as the physical resource 5 that corresponds to at least one of the following listed items in response to the request content of request R0001 corresponding to the virtual resource VR001. Five physical resources capable of providing the necessary functions to meet the requirements. Five physical resources capable of providing the required capacity within the requested timeframe. • Five physical resources that meet the required cost

[0101] Here, the resource formation unit 351C may select the actual resource 5 to be incorporated into the virtual resource using the predicted value calculated by the capacity prediction unit 352 instead of the measured value calculated by the capacity conversion unit 351B. For example, the resource formation unit 351C may select the actual resource 5 such that the expected value of the predicted virtual capacity data for the virtual resource at any future date and time calculated by the capacity prediction unit 352, the predicted value of quantiles such as the 25th percentile, and the interval estimates such as confidence intervals and prediction intervals satisfy predetermined thresholds and quality conditions specified in the resource request content data. In this case, the resource formation unit 351C outputs control data to the capacity prediction unit 352, instructing it to return the prediction result data. The output of control data continues until the prediction result data of the virtual capacity data exceeds a predetermined threshold or until the difference in the change between the previous and current values ​​of the prediction result data falls below a predetermined value. This makes it possible to create virtual resources that guarantee the quantity and quality of their capabilities.

[0102] Alternatively, the resource formation unit 351C may select the physical resource 5 to be incorporated into the virtual resource such that the interval estimates, such as the confidence interval and prediction interval, of the predicted value of the virtual capacity data for any future date and time of the virtual resource calculated by the capacity prediction unit 352 are minimized. In this case, the resource formation unit 351C outputs control data instructing the capacity prediction unit 352 to return the prediction result data. The output of control data continues until the predicted result data of the virtual capacity data exceeds a predetermined threshold or until the difference in the change between the previous and current values ​​of the prediction result data falls below a predetermined value. Alternatively, the resource formation unit 351C may select the physical resources 5 to be incorporated into the virtual resources such that at least one of the expected value, quantile prediction value, or interval prediction value of the virtual resource's capacity at a predetermined date and time calculated by the capacity prediction unit 352 satisfies a predetermined standard value.

[0103] In this way, the virtual resource capability conversion unit 351 constructs a virtual resource by combining multiple pre-stored virtualization logics to satisfy the capability mode of the physical resource requested by the resource operation management system. Alternatively, the virtual resource capacity conversion unit 351 constructs virtual resources based on the predicted values ​​of the virtual capacity data calculated by the capacity prediction unit 352. Here, the virtual resource capability conversion unit 351 may determine a combination of physical resources 5 that constitute the virtual resources such that the information indicating the attributes of the virtual resources (controllability and cost) generated based on information indicating the constraints of each physical resource 5 satisfies predetermined criteria. This makes it possible to create virtual resources with minimal uncertainty regarding the quantity and quality of their capabilities.

[0104] The resource formation unit 351C outputs data showing the correspondence between the formed virtual resource and the actual resource 5 that constitutes the virtual resource as resource relationship data 359A and stores it in the resource relationship data storage means 359. Figure 15 is a table showing an example of resource relationship data 359A. The table in Figure 15 stores the following data in each column. The first column stores identifier data that identifies each virtual resource created by the resource formation unit 351C. The second column stores the identifier data for the physical resource 5 that makes up the virtual resource. The third and fourth columns store the start and end dates and times to which each entity resource 5 is associated as a component of each virtual resource.

[0105] The table in Figure 15 stores the following data in each row. The first line indicates that the virtual resource ID "VR001" is associated with the physical resource "AR001" as a component, and that the period during which the physical resource "AR001" is a component is from "2021 / 01 / 01 13:24" to "2021 / 01 / 01 14:43". The virtual resource "VR002" in the second line is associated with the physical resource 5 of "AR002" as a component. As shown in the third line, the virtual resource "VR002" is associated with "AR003" as a component, but at a different time point than "AR002". In this manner, the resource formation unit 351C forms a virtual resource such that multiple physical resources 5 become constituent elements of a single virtual resource, either in the same or different time periods.

[0106] Furthermore, the physical resource "AR003" that constitutes the virtual resource "VR002" is also physical resource 5 that constitutes the virtual resource "VR005" shown in row 7. And as shown in the periods in columns 3 and 4, "AR003" is also simultaneously configured in multiple virtual resources, "VR002" and "VR005". Here, the virtual resource "VR002" is a virtual resource created for the purpose of providing the requested resource "power transport resource" shown in the second line of the resource request data in Figure 6, and "VR005" is a virtual resource created for the purpose of providing the "cargo transport resource" shown in the fifth line of the resource request data in Figure 6.

[0107] Here, the physical resource "AR003" is named "Customer Bus" as shown in the third row of the physical resource constraint data 452 in Figure 8, and its operations are "storage and discharge, movement, and cargo transport." In other words, "AR003" is a physical resource 5 that, in the movement state, can simultaneously provide capabilities as two virtual resources: "power transport capacity using rechargeable batteries" and "cargo transport capacity using passenger space." Therefore, the resource formation unit 351C indicates that it is simultaneously configuring the physical resource 5 of "AR003," which has data indicating both "power transport capacity" and "cargo transport capacity" at the same time, into "VR002" and "VR005." This concludes the explanation of the virtual resource capacity conversion unit 351.

[0108] Figure 16 is a data flow diagram of the capacity prediction unit 352. The capacity prediction unit 352 receives the virtual capacity data output by the virtual resource capacity conversion unit 351 and the factor data 453A, and outputs a predicted value of the virtual capacity data for a predetermined future date and time.

[0109] Specifically, the model identification unit 352A first receives the virtual capability data output by the virtual resource capability conversion unit 351 and the factor data 453A, and identifies a predictive model that takes the values ​​of each factor included in the factor data 453A as input and outputs the values ​​of the virtual capability data. A known method may be applied to identify the predictive model. A known method is, for example, one of the following methods. • Methods that assume linearity, such as linear regression models like multiple regression models and generalized linear models like logistic regression. • Methods that assume autoregression, such as the ARX (AutoRegressive with Exogenous) model. • Methods that utilize reduction estimators such as Ridge regression, Lasso regression, and ElasticNet. • Methods that utilize dimensionality degenerators such as partial least squares and principal component regression. • Nonlinear models using polynomials, or nonparametric regression model methods such as support vector regression, regression trees, Gaussian process regression, and neural networks. Furthermore, not only inductive or interpolative methods such as regression models are acceptable, but also deductive or extrapolative methods such as agent simulations.

[0110] Furthermore, when the model identification unit 352A receives input of control plan data for the physical resource 5 created by the control planning unit 354, which has received a start signal from the capacity allocation unit 353, it also uses the control plan data for the physical resource 5 in the prediction model identification process. For example, consider a scenario where the initial operation state at time T of the physical resource "AR00X", which has a control acceptance status of "acceptable", is "not operating", and therefore the value of the virtual capacity data is initially zero. In this scenario, if the control planning unit 354 generates control planning data that changes the operation of "AR00X" at time T to "operate", the model identification unit 352A changes the value of the virtual capability data of the actual resource "AR00X" at time T to a value greater than zero, and then executes the predictive model identification process. The method for changing the value of the virtual capability data is, for example, the following method. • A method to change the virtual capability data to the same value as the value at the time immediately preceding time T. • Method of changing to a predetermined value • How to change the time and factor data 453A values ​​to the same value or average value as similar past date and time values.

[0111] The prediction value calculation unit 352B calculates predicted result data for virtual capability data values ​​by inputting observed or predicted values ​​of factor data 453A for the target date and time to the prediction model output by the model identification unit 352A. The form of the calculated prediction result data is expected value, predicted values ​​of quantiles such as the 25th percentile, interval estimates such as confidence intervals and prediction intervals. The calculated prediction result data is output to the capability allocation unit 353.

[0112] If control data indicating an instruction to return prediction result data is input from the virtual resource capacity conversion unit 351, the prediction result data is output to the virtual resource capacity conversion unit 351, not to the capacity allocation unit 353. Upon receiving the prediction result data, the virtual resource capacity conversion unit 351 modifies the configuration of the physical resource 5 associated with the virtual resource using the prediction result data, as described in the resource formation unit 351C. If there is no longer any input of control data indicating an instruction to return prediction result data from the virtual resource capacity conversion unit 351, the prediction result data is output to the capacity allocation unit 353. This concludes the operation of the capability prediction unit 352.

[0113] Figure 17 is a data flow diagram of the capacity allocation unit 353. The capacity allocation unit 353 receives data indicating the resource request from the resource operation control device 10 and outputs resource request data to the virtual resource capacity conversion unit 351. Subsequently, the capacity allocation unit 353 receives prediction result data of virtual capacity data from the capacity prediction unit 352 and outputs data indicating that the virtual resources have been set up for use in the operation control of the resource operation control device 10.

[0114] Specifically, the resource request data generation unit 353A first obtains data indicating the resource request from the resource operation control device 10 and generates resource request data as shown in Figure 6. The generated resource request data is output to the virtual resource capacity conversion unit 351, and thereafter, as explained above, the virtual resource capacity conversion unit 351 outputs virtual capacity data, and then the capacity prediction unit 352 outputs prediction result data for the virtual capacity data.

[0115] Next, the request satisfaction evaluation unit 353B takes the predicted result data of virtual capacity data output by the capacity prediction unit 352 and the resource request content data output by the resource request data generation unit 353A as input and determines whether the predicted result data of virtual capacity data satisfies the resource request content. For example, the resource request content for request ID "R0001" shown in the first row of Figure 6 is a request period of "2021 / 01 / 01 00:00 to 2021 / 12 / 31 23:59", a request amount of "supply amount of 100MW or more per hour", and a request location of "supply to location A", and determines whether the predicted result data of virtual capacity data output by the capacity prediction unit 352 satisfies each request. If it is determined that the requests are satisfied, the request satisfaction evaluation unit 353B generates request resource correspondence data (Figure 18) that shows the correspondence between the resource requests received from each resource operation control device 10 and the virtual resources. The requested resource correspondence data is, for example, the data that associates the virtual resource "VR001" in Figure 20 with the request ID "R0001".

[0116] Figure 18 is a table showing an example of requested resource correspondence data. The table in Figure 18 stores the following data in each column. The first column stores data indicating the identifier of the virtual resource formed in the virtual resource capability conversion unit 351. The second and third columns contain data indicating the start and end dates and times when each virtual resource becomes available. The fourth column contains data indicating whether or not the virtual resource is eligible for control. The fifth column stores data indicating the identifier of the request from the resource operation control device 10, which has been set by the request satisfaction evaluation unit 353B to provide each virtual resource. The sixth column stores data indicating the characteristics of the virtual resource. In the example in Figure 18, it shows the response time, which is the time from receiving the control signal to reaching a predetermined control value.

[0117] The first row of the table in Figure 18 indicates that the virtual resource ID "VR001" is available for the period from "2021 / 01 / 01 00:00 to 2021 / 12 / 31 23:59" and that control acceptance is "not possible". This virtual resource has been determined to satisfy the request for request ID "R0001" as a result of the determination process of the request satisfaction evaluation unit 353B, and therefore, as shown in the fifth column, it is set to be associated with the corresponding request "R0001". The seventh row of the table in Figure 18 indicates that the virtual resource ID "VR007" is not associated with any response request, meaning it is an idle virtual resource.

[0118] As illustrated in other rows of Figure 18, the request satisfaction evaluation unit 353B determines whether the predicted result data of each virtual capability data satisfies each resource request, and if it does, it associates and sets the ID of each resource request data. The set request resource correspondence data is sent to the resource operation control device 10, which determines whether or not to operate the virtual resource it has received, and if it does, it sends signal data to the resource virtualization device 3 to execute operation control. The resource virtualization device 3 then sends a control signal to the physical resource 5 that constitutes the virtual resource via the control planning unit 354 if the virtual resource is controllable and requires control.

[0119] If the requirement satisfaction evaluation unit 353B determines that the predicted result data of the virtual capacity data does not satisfy the requirements of the resource indicated in the resource request content data, and the virtual resource is a controllable virtual resource, it outputs data indicating the details of the satisfaction violation and data indicating an instruction to create a control plan for the virtual resource to the control planning unit 354. Upon receiving the data indicating an instruction to create a control plan, the control planning unit 354 generates controllable physical resources 5 among the physical resources 5 that constitute the virtual resource in order to resolve the satisfaction violation. The created control plan data is input to the capacity prediction unit 352 as described above, and the capacity prediction unit 352 recalculates the predicted result data of the virtual capacity data. Then, using the recalculated predicted result data, the requirement satisfaction evaluation unit 353B makes another determination. The above operations are repeated until the requirement satisfaction evaluation unit 353B determines that the resource request content is satisfied or until a predetermined number of times has been exceeded.

[0120] Furthermore, if the aforementioned operations exceed a predetermined number of times, or if the virtual resource that the request content is determined not to be satisfied is an uncontrollable virtual resource, the request satisfaction evaluation unit 353B outputs data indicating the content of the satisfaction violation and data indicating an instruction to create a control plan for the virtual resource to the control planning unit 354. Upon receiving the data indicating an instruction to change the configuration of the physical resource 5, the virtual resource capacity conversion unit 351 modifies the physical resource 5 that constitutes the virtual resource to resolve the request violation. The virtual capacity data with the modified configuration of the physical resource 5 is then input to the capacity prediction unit 352 to recalculate the prediction result data for the virtual capacity data, and the request satisfaction evaluation unit 353B makes another determination using the recalculated prediction result data. The above operations are repeated until the request satisfaction evaluation unit 353B determines that the resource request content is satisfied or until a predetermined number of times is exceeded. This concludes the operation of the capacity allocation unit 353.

[0121] The data flow and processing operation of the control planning unit 354 will be explained. The control planning unit 354 starts operation upon receiving data from the capacity allocation unit 353 indicating support for the generation of a control plan. The control planning unit 354 receives data from the capacity allocation unit 353 indicating the identifier of the virtual resource for which the control plan is to be generated, data indicating the content of the resource request content satisfaction violation, resource relationship data 359A, and physical resource constraint data 452A, and outputs control plan data for physical resource 5.

[0122] Specifically, the control planning unit 354 first receives the identifier of the virtual resource to be used for control plan generation and resource relationship data 359A from the capacity allocation unit 353. Then, using the identifier of the virtual resource to be used for control plan generation as a key, it obtains the identifiers of the physical resources 5 that constitute the virtual resource from the resource relationship data 359A. Next, the control planning unit 354 receives the physical resource constraint data 452A and obtains data indicating the constraint conditions of each physical resource 5 from the physical resource constraint data 452A using the identifiers of the physical resources 5 obtained in the above operation as a key. Then, from the constraints of the physical resources 5, the control plan unit 354 extracts the physical resources 5 for which control is possible. The control plan unit 354 then generates and outputs a control plan for each of the extracted physical resources 5 so as to resolve any violations of the resource request content output by the capacity allocation unit 353.

[0123] Let's explain with a specific example. We will explain with the example where the virtual resource to be used for control plan generation, input from the capacity allocation unit 353, is "VR002", and the data indicating the content of the sufficiency violation is "insufficient predicted value of the data indicating capacity at time 17:00". First, the control planning unit 354 obtains "AR002" and "AR003," which are identifiers for the physical resources 5 that constitute the virtual resource "VR002," from the resource relationship data 359A shown in Figure 15. Next, the control planning unit 354 obtains data showing the constraint conditions for the physical resources "AR002" and "AR003" from the physical resource constraint data 452A shown in Figure 8, and extracts "AR002," which is the physical resource 5 for which the controllability of the constraint conditions is "possible."

[0124] Here, the actual resource "AR002" shown in the second row of resource relationship data 359A in Figure 15 has an operation termination date and time of "2021 / 01 / 01 16:21", indicating that it was not operational at the time "17:00" shown in the data indicating the content of the satisfaction violation. On the other hand, the operating time for the entity resource "AR002" shown in the second row of the entity resource constraint data 452A in Figure 8 is "09:00 to 23:00", and operation at "17:00" as shown in the data indicating the content of the satisfaction violation satisfies the constraint for the entity resource "AR002".

[0125] Therefore, the control planning unit 354 generates control plan data to operate the physical resource "AR002" at "time 17:00" as indicated in the data indicating the content of the sufficiency violation, in order to resolve the "insufficient predicted value of the data indicating capacity" as indicated in the data indicating the content of the sufficiency violation. The generated control plan data is input to the capacity prediction unit 352. The operations described above are then performed. Furthermore, when the resource operation control device 10 inputs data to the resource virtualization device 3 indicating the execution of operation control of a virtual resource, the control plan unit 354 transmits a control signal to the control device of the physical resource 5 based on the aforementioned control plan data.

[0126] With the above steps completed, the operation of the control planning unit 354 ends, and simultaneously, the computational processing of the resource virtualization system 2 in this embodiment is completed.

[0127] In the above embodiment, the virtual resource capability conversion unit 351 was described as determining the physical resources 5 that constitute the virtual resources based on the prediction result data of the virtual capability data output by the capability prediction unit 352. However, the determination may not be limited to this description, and may be made according to the state of the virtual capability data from the past to the latest date and time. For example, when the time-series data of the virtual capability data of each physical resource 5 from the past to the latest date and time is aggregated, the time-series data representing the aggregated capability of the virtual resource may be configured to be stationary data. By configuring it in this way, the stationarity of the virtual capability data is ensured, and the prediction accuracy of the virtual capability data in the capability prediction unit 352 is improved or stabilized.

[0128] Furthermore, the determination may be based not only on virtual capability data, but also on data indicating the attributes of virtual resources. For example, the controllability conditions described in the physical resource constraint data 452A may be referenced, and the configuration may consist only of physical resources 5 that are "controllable" or only of physical resources 5 that are "uncontrollable". This configuration allows for the management of virtual resources by separating the certainty and uncertainty of the quantity and quality of the virtual resources' capabilities. Alternatively, the configuration may be made by referring to the "cost" constraints for each resource shown in the physical resource constraint data 452A, so as to minimize the sum of the costs of each physical resource 5 that constitute the virtual resource. This configuration makes it possible to minimize the costs associated with the operation of virtual resources.

[0129] In the above embodiment, the capacity allocation unit 353 was described as always corresponding to one of the resource requests. However, the explanation is not limited to this, and a virtual resource may exist even if there is no corresponding resource request. For example, a virtual resource that satisfies currently existing resource requests or past resource requests can be formed using the virtual resource capacity conversion unit 351, capacity prediction unit 352, and control planning unit 354, although the capacity allocation unit 353 may set the resource requests to be allocated to "none". This makes it possible to immediately provide virtual resources when a similar resource request is newly input from the resource operation control device 10, thereby improving the control response of the resource operation control device 10.

[0130] In the above embodiment, the control planning unit 354 was described as generating a control plan for a physical resource. However, it may also generate a control plan for a virtual resource. For example, the control planning unit 354 starts operation upon receiving control plan generation instruction data from the capacity allocation unit 353. The control planning unit 354 extracts virtual resources from the requested resource correspondence data shown in Figure 18 that are not allocated to the request and are not scheduled to be operational, or virtual resources that have already been allocated and can simultaneously satisfy the request currently being satisfied. The control planning unit 354 then incorporates the extracted virtual resources into the virtual resources corresponding to the request currently being satisfied. This allows for improved utilization of already configured virtual resources while also increasing the likelihood of fulfilling requests.

[0131] In the above embodiment, the capability prediction unit 352 was described as performing prediction processing using the virtual capability data output by the virtual resource capability conversion unit 351 as is. However, the capability prediction unit 352 may separate the virtual capability data into virtual capability data corresponding to controllable physical resources and virtual capability data corresponding to uncontrollable physical resources, and perform prediction processing using the virtual capability data corresponding to uncontrollable physical resources. In this case, the predicted virtual capacity data corresponding to the controllable physical resources is calculated as the planned control amount based on the control plan for the physical resources generated in the control planning unit 354, and is added to the predicted result data of the virtual capacity data corresponding to the uncontrollable physical resources to calculate the final predicted result data. This allows us to prevent a decrease in the modeling accuracy of prediction models for virtual capability data by pre-separating virtual capability data that corresponds to controllable physical resources.

[0132] Figure 21 is a hardware configuration diagram of resource virtualization system 2. Each device in the resource virtualization system 2 is configured as a computer 900 having a CPU 901, RAM 902, ROM 903, HDD 904, communication I / F 905, input / output I / F 906, and media I / F 907. The communication interface 905 is connected to an external communication device 915. The input / output interface 906 is connected to the input / output device 916. The media interface 907 reads and writes data to the recording medium 917. Furthermore, the CPU 901 controls each processing unit by executing a program (also called an application or app) loaded into the RAM 902. This program can also be distributed via a communication line or by recording it on a recording medium 917 such as a CD-ROM.

[0133] Although embodiments of the present invention have been described above, the present invention is not limited to the embodiments described above, and various modifications can be made without departing from the scope of the claims. For example, the embodiments described above illustrate the present invention in detail, and it is not necessary to have all the configurations described. It is also possible to add configurations from other embodiments to the configuration. In addition, some parts of the configuration can be added, deleted, or replaced.

[0134] Furthermore, it is possible to add, delete, or replace some of the configurations in each embodiment with other configurations. In addition, some or all of the above configurations, functions, processing units, processing means, etc., may be implemented in hardware, for example, by designing them as integrated circuits. Furthermore, each of the aforementioned configurations and functions may be implemented in software by the processor interpreting and executing programs that realize each of these functions.

[0135] The information such as programs, tables, and files that implement each function can be stored in memory, storage devices such as hard disks and SSDs (Solid State Drives), or recording media such as IC (Integrated Circuit) cards, SD cards, and DVDs (Digital Versatile Discs). Cloud computing can also be utilized. Furthermore, the control lines and information lines shown are those deemed necessary for explanatory purposes, and not all control lines and information lines are necessarily shown in the actual product. In practice, it can be assumed that almost all components are interconnected. In addition, the communication means connecting each device is not limited to wireless LAN, but may be changed to wired LAN or other communication methods. [Explanation of Symbols]

[0136] 1. Resource Management System 2. Resource virtualization system (resource management device) 3. Resource Virtualization Device 4. Data Management Device 5. Entity Resources 6. Measuring device 7. Monitoring and Control Device 8. Information Input / Output Terminals 9. Information distribution device 10 Resource Operation Control System 11 Communication Path 12. Controlled Equipment 31 CPU 32 Input devices 33 Output device 34 Communication equipment 35 Storage device 41 CPU 42 Input devices 43 Output device 44 Communication equipment 45 Storage device 351 Virtual Resource Capability Conversion Unit 352 Capability Prediction Department 353 Capacity Allocation Department 354 Control Planning Department 451A Physical Resource Measurement Data

Claims

1. A virtual resource capability conversion unit creates virtual capability data indicating the capabilities that the physical resources provide as virtual resources, based on virtualization logic that virtualizes the physical resources, from physical resource measurement data obtained by measuring physical resources, which are equipment related to energy, and constructs virtual resources that provide that virtual capability data. The system includes a capability allocation unit that assigns the virtual resources constructed by the virtual resource capability conversion unit to a resource operation management system, thereby causing the resource operation management system to manage the actual resources. The virtualization logic is prepared individually according to the resource request data indicating the capability mode of the physical resource requested by the resource operation management system. The virtualization logic is characterized by converting the physical resource measurement data, which shows the movement history associated with the operation of the physical resource, into virtual capacity data, which shows the cargo transport capacity of the physical resource. Resource management device.

2. A virtual resource capability conversion unit creates virtual capability data indicating the capabilities that the physical resources provide as virtual resources, based on virtualization logic that virtualizes the physical resources, from physical resource measurement data obtained by measuring physical resources, which are equipment related to energy, and constructs virtual resources that provide that virtual capability data. The system includes a capability allocation unit that assigns the virtual resources constructed by the virtual resource capability conversion unit to a resource operation management system, thereby causing the resource operation management system to manage the actual resources. The virtualization logic is prepared individually according to the resource request data indicating the capability mode of the physical resource requested by the resource operation management system. The virtualization logic is characterized by using the physical resource measurement data indicating the positive or negative energy supply capacity of the physical resource and the physical resource measurement data indicating the cargo transport capacity of the physical resource to convert it into virtual capacity data indicating the energy transport capacity of the physical resource. Resource management device.

3. The resource management device further includes a capacity prediction unit that calculates predicted values, which are future values ​​of the virtual capacity data. The capacity allocation unit is characterized by allocating the virtual resources constructed by the virtual resource capacity conversion unit to the resource operation management system based on the predicted values ​​calculated by the capacity prediction unit. The resource management device according to claim 1 or claim 2.

4. The resource management device further includes a control planning unit, The control planning unit generates a control plan for the physical resources that constitute the virtual resources allocated by the capacity allocation unit, and causes the resource operation management systems to which the resources are allocated to control the physical resources based on that control plan. The virtual resource capacity conversion unit is characterized by modifying the virtual capacity data based on the control plan generated by the control planning unit. The resource management device according to claim 1 or claim 2.

5. The virtual resource capability conversion unit is characterized by constructing the virtual resource by combining a plurality of pre-stored virtualization logics in such a way as to satisfy the capability mode of the physical resource requested by the resource operation management system. The resource management device according to claim 1 or claim 2.

6. The virtual resource capacity conversion unit is characterized by constructing the virtual resource based on the predicted value of the virtual capacity data calculated by the capacity prediction unit. The resource management device according to claim 3.

7. The virtual resource capability conversion unit is characterized in that, in the process of combining a plurality of virtualization logics stored in advance, it determines the combination of physical resources that constitute the virtual resource such that the information indicating the attributes of the virtual resource, generated based on information indicating the constraints of each physical resource, satisfies predetermined criteria. The resource management device according to claim 5.

8. The control planning unit calculates the time change of the virtual capacity data related to energy in conjunction with the operation of the physical resource, and reflects this time change in the virtual capacity data created by the virtual resource capacity conversion unit. The resource management device according to claim 4.

9. The virtualization logic is characterized by converting the physical quantities of the actual resource measurement data into virtual capability data that represent different types of physical quantities. The resource management device according to claim 1 or claim 2.

10. The virtualization logic is characterized by generating new virtual capability data from a combination of two or more types of virtual capability data. The resource management device according to claim 1 or claim 2.

11. The virtualization logic is characterized by converting the physical resource measurement data, which shows the remaining amount of energy associated with the operation of the physical resource, into virtual capacity data, which shows the positive or negative energy supply capacity of the physical resource. The resource management device according to claim 1 or claim 2.

12. The resource management device has a virtual resource capacity conversion unit and a capacity allocation unit. The virtual resource capability conversion unit creates virtual capability data indicating the capability that the physical resource provides as a virtual resource, based on virtualization logic that virtualizes the physical resource, from physical resource measurement data obtained by measuring the physical resource, which is equipment related to energy, and constructs a virtual resource that provides that virtual capability data. The capacity allocation unit assigns the virtual resources constructed by the virtual resource capacity conversion unit to the resource operation management system, thereby allowing the resource operation management system to manage the actual resources. The virtualization logic is prepared individually according to the resource request data indicating the capability mode of the physical resource requested by the resource operation management system. The virtualization logic is characterized by converting the physical resource measurement data, which shows the movement history associated with the operation of the physical resource, into virtual capacity data, which shows the cargo transport capacity of the physical resource. Resource management methods.

13. The resource management device has a virtual resource capacity conversion unit and a capacity allocation unit. The virtual resource capability conversion unit creates virtual capability data indicating the capability that the physical resource provides as a virtual resource, based on virtualization logic that virtualizes the physical resource, from physical resource measurement data obtained by measuring the physical resource, which is equipment related to energy, and constructs a virtual resource that provides that virtual capability data. The capacity allocation unit assigns the virtual resources constructed by the virtual resource capacity conversion unit to the resource operation management system, thereby allowing the resource operation management system to manage the actual resources. The virtualization logic is prepared individually according to the resource request data indicating the capability mode of the physical resource requested by the resource operation management system. The virtualization logic is characterized by using the physical resource measurement data indicating the positive or negative energy supply capacity of the physical resource and the physical resource measurement data indicating the cargo transport capacity of the physical resource to convert it into virtual capacity data indicating the energy transport capacity of the physical resource. Resource management methods.

14. A resource management program for causing a computer to function as a resource management device according to claim 1 or claim 2.

Images