Power system database operation system

Abstract

To provide a database operating system for a power system capable of using for both system planning and system analysis, and handling system installation data and system configuration data in a matching manner.SOLUTION: A database operating system for a power system includes hierarchical type data D1211 having two or more layers that have a relation between upper and lower levels, such as a relation between data D1213 including data for upper-level installations and the data D1213 including lower-level installations that constitute the upper-level installations. Installation parameters used in system planning and system analysis of the power system are stored in the data D1213 and data D1214, and a master ID that uniquely designates the installations in the data D1211 of all power system configurations and an installation ID that uniquely designates the installations in the data D1211 of the power system configurations are stored in association with each of all installations.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a database operation system for a power system. [Background technology]

[0002] Patent Document 1 describes a database operation system for power system analysis. In general, data used for power system facility formation planning is different from data used for operation analysis of the formed facilities. In system facility formation planning based on long-term prediction, geographical information and global information of the facilities are important in order to consider new installation and removal of facilities. On the other hand, system analysis is required when operating the system, so more detailed electrical information is important for operation analysis. Therefore, it is necessary to appropriately manage the granularity differences of these data in a database.

[0003] In addition, power systems are required to be somewhat robust against disturbances such as lightning strikes and system failures. For this reason, when forming future facilities, it is necessary to evaluate the reliability of the system based on multiple scenarios that assume a variety of conditions. In this case, the facility formation and the facility expansion / renewal status also change depending on the scenario, but it is necessary to manage in the database that the same facility and the same time correspond to different conditions in different scenarios. Furthermore, if the facility in question is a boundary facility and there are multiple operators who manage it, there is a possibility that the management name of the facility in question is different between the two operators. These ID differences in data also need to be properly managed in the database. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2013-219853 A Summary of the Invention [Problem to be solved by the invention]

[0005] Incidentally, in the power system analysis database operation system described in Patent Document 1, the equipment layer is divided by role, such as by voltage and by power generation / load model, to manage the system configuration. The database for managing the system configuration is a non-relational database.

[0006] However, non-relational databases generally cannot guarantee the consistency of data contained within the database, and there is a possibility that inconsistencies may occur in the ID management section.In addition, it is assumed that the equipment data contained in the system configuration is time-invariant, which poses the issue that it is difficult to manage according to future predictions or when the relevant equipment is updated or decommissioned in the future.

[0007] In response to this, it is possible to consider adding corresponding scenarios and duration to parameters and managing them, but in this case, since it is a non-relational database, there remains the issue that it is not possible to consistently manage whether the equipment in question is the same equipment as the equipment at any point in time. [Means for solving the problem]

[0008] An embodiment of the present invention provides a database operation system for a power system, which includes a power system equipment database for a power system equipment model including a plurality of power equipment, for a plurality of the power system equipment models, and the power system equipment database is a hierarchical database including two or more layers, each having a relationship between an upper layer including data of a higher-level power equipment and a lower layer including data of a lower-level power equipment that constitutes the higher-level power equipment, and equipment parameters used in system planning and system analysis of the power system are stored in the layers, and a first ID that uniquely specifies the power equipment in all of the power system equipment databases and a second ID that uniquely specifies the power equipment in the power system equipment database in which the power equipment is included are stored in correspondence with each of the power equipment. Effect of the Invention

[0009] According to the present invention, it is possible to use the system for both system planning and system analysis, and to consistently handle system equipment data and system configuration data based on multiple scenarios. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram showing a hardware configuration of a power system database operation system according to the first embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of the configuration of system configuration data. [Diagram 3] FIG. 3 shows an example of a three-layer structure. [Figure 4] FIG. 4 is a diagram showing an example of the data D1221. [Diagram 5] FIG. 5 is a diagram showing an example of the data D1231. [Figure 6] FIG. 6 is a diagram showing an example of the data D1241. [Figure 7] FIG. 7 is a diagram showing an example of the scenario data 125. As shown in FIG. [Figure 8] FIG. 8 is a flowchart illustrating the operation of the power system database operation system. [Figure 9] FIG. 9 is a flowchart showing detailed processing of processing step S2. [Figure 10] FIG. 10 is a diagram showing an outline of the processing in processing steps S202 and S203. [Figure 11] FIG. 11 is a flowchart showing the detailed process of processing step S3. [Figure 12] FIG. 12 is a diagram showing an example of an outline of the processing steps S302 and S303. [Figure 13] FIG. 13 is a flowchart showing the detailed process of processing step S4. [Figure 14] FIG. 14 is a diagram showing an example of the output screen. [Figure 15] FIG. 15 is a diagram showing an example of the system configuration data D1211A of the cross section 311A. [Figure 16] FIG. 16 is a diagram showing an example of the system configuration data D1211B of the cross section 311B. [Figure 17] FIG. 17 is a flowchart showing a processing procedure in the external system. [Figure 18] FIG. 18 is a diagram showing system configuration data before measures are taken. [Figure 19] FIG. 19 is a diagram showing system configuration B of countermeasure candidate 1. [Figure 20] FIG. 20 is a diagram showing system configuration C of countermeasure candidate 2. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. The following description and drawings are examples for explaining the present invention, and some omissions and simplifications have been made for clarity of explanation. The present invention can be implemented in various other forms.

[0012] -First embodiment- 1 is a diagram showing the hardware configuration of a power system database operation system. The power system database operation system 1 is generally configured with a computer device, and therefore includes a central processing unit 10 configured with a computer or a computer server (CPU: Central Processing Unit), a main memory unit 11 configured with a storage device such as a HDD, an auxiliary memory unit 12 configured with a HDD, a memory, etc., a communication unit 13, an input unit 14, and an output unit 15.

[0013] The central processing unit 10 may be configured as one or more semiconductor chips, or may be configured as a computer device such as a calculation server. The communication unit 13 has a circuit and a communication protocol for connecting to a communication network. The input unit 14 can be configured to include at least one of a keyboard switch, a pointing device such as a mouse, a touch panel, a voice instruction device, etc. The output unit 15 is configured as, for example, a display device, but may also be configured to include at least one of a display device, a printer device, and a voice output device, etc. The output unit 15 outputs data processed by the central processing unit 10 or data recorded in the main memory unit 11 and the auxiliary memory unit 12 in a form suitable for the device. An output example will be described later.

[0014] The external system 20 is a system that cooperates with the power system database operation system 1. There may be no or multiple systems that cooperate with the external system 20. In Fig. 1, the auxiliary storage unit 12 holds system configuration data 121, layer interpolation setting data 122, configuration condition setting data 123, cross-section transition data 124, scenario data 125, a system configuration layer interpolation program 126, a system configuration generation program 127, and a multiple cross-section generation program 128.

[0015] FIG. 2 is a diagram showing an example of the configuration of the system configuration data 121. In the system configuration data 121, for each system configuration, equipment belonging to the system configuration and parameters of the equipment are stored for each layer. The system configuration data 121 is not limited to data D1211 of an actual system configuration, but also includes data D1211 of a model system configuration. In FIG. 2, the data D1211 represents data of a certain specific system configuration. The system configuration data 121 is composed of data D1211 of a plurality of system configurations. The data D1211 is composed of three types of data D1212, D1213, and D1214.

[0016] Data D1212 stores system configuration IDs (=A) assigned to each system configuration, and master IDs (=0001, 0011, ...) that are IDs assigned to equipment included in the system configuration. Data D1213 represents data on equipment of a higher configuration (hereinafter also referred to as a higher layer) among the equipment (master IDs = 0001, 0011, ...) included in the system configuration (system configuration ID = A) shown in data D1211. Data D1214 represents data on equipment of a lower configuration (hereinafter also referred to as a lower layer) among the equipment (master IDs = 0001, 0011, ...) included in the system configuration (system configuration ID = A) shown in data D1211. Upper layers and lower layers will be described later.

[0017] Data D1213 representing data on equipment in an upper layer stores the master ID, equipment ID, various prescribed parameters, and the master ID of equipment in a lower layer, etc. Data D1214 representing data on equipment in a lower layer stores the master ID, equipment ID, prescribed parameters, etc. of equipment in the lower layer. The parameters are parameters of equipment, such as the capacity and reactance of a transformer in a substation.

[0018] Here, the master ID is an ID that is uniquely assigned across all time and all equipment (i.e., the time axis and the space axis), and the equipment ID is an ID that is uniquely assigned to each piece of equipment within each system configuration (i.e., space-time). By specifying the master ID, it is possible to specify which equipment in which system configuration it is. For example, master ID=0001 specifies only the equipment "substation1" stored in data D1211, and no other equipment with the same master ID exists in this data D1211 or in other data D1211.

[0019] Here, the upper layer and lower layer of the equipment included in the system configuration will be explained. The equipment belonging to the upper layer is a facility (facility) composed of smaller power equipment, for example, a substation or a power generation plant. Taking a substation as an example, the substation is generally composed of power equipment such as a transformer, a transmission line, and a busbar. In this case, the equipment in the upper layer is a facility called a substation, and the transformer, the transmission line, and the busbar are equipment belonging to the lower layer. In this way, the lower layer represents a more detailed group of equipment belonging to the facility in the upper layer. In other words, the equipment in the upper layer included in a certain system configuration has a system configuration composed of equipment belonging to the lower layer inside.

[0020] The example shown in Figure 2 shows a layer configuration for a two-layer structure, and for convenience, the two layers are expressed as upper and lower. However, a layer structure with three or more layers is also possible, and in such a case, each layer can be expressed as the first layer, second layer, third layer, and so on.

[0021] FIG. 3 is an example showing a layer configuration of a three-layer structure. In FIG. 3, data D1213 indicates data of equipment in the first layer, data D1214 indicates data of equipment in the second layer, and data D1215 indicates data of equipment in the third layer. In the data D1213 of the first layer, for example, data and equipment ID of equipment with master ID=1000 (substation 1) are stored, and in the column of lower equipment, master ID=0001, 0002, 0003 of equipment constituting substation 1 are listed. The data and equipment ID of equipment with master IDs listed in the column of lower equipment of the first layer are stored in data D1214 of the second layer, which is a layer lower than data D1213. For example, data and equipment ID of equipment with master ID=0001, 0002, 0003 of equipment constituting substation 1 are stored in data D1214. The data and equipment IDs of equipment with the master IDs listed in the lower equipment column of the second layer (data D1214) are stored in data D1215 of the third layer, which is the layer below data D1214. For example, the data and equipment IDs of equipment with master IDs=001A and 001B that make up the equipment with master ID=0001 are stored in data D1215.

[0022] In the following, an example of a two-layer structure will be explained. As mentioned above, a relational database is assumed in which the parameters of the upper layer are determined from the equipment group in the lower layer. Therefore, the parameters required for the upper layer must be determined in advance and the database must be constructed. In this case, the parameters and data items of the upper layer do not need to match those of the lower layer. For example, since the location information is the same for both the upper and lower structures, it is possible to adopt a flexible structure in which geographical location information is input to the facilities of the upper structure, but this information can be simplified as it is not important for the equipment of the lower structure.

[0023] Data D1221 shown in FIG. 4 is an example of the layer interpolation setting data 122. The data D1221 stores a method for interpolating the equipment configuration and parameters in each layer of the system configuration data 121. The stored interpolation methods are generated by input from the user or by a preset setting. Each interpolation method is assigned an ID (=B1, B2). The method of using the data D1221 will be described later.

[0024] Data D1231 shown in FIG. 5 is an example of the configuration condition setting data 123 shown in FIG. 1. In the example shown in FIG. 5, data D1231 stores a system configuration generation method according to the user's usage method. These generation methods are generated by input from the user or by a preset setting. An ID (=C1, C2) is assigned to each configuration condition, and the comment field describes the configuration generation method for the equipment in the upper layer specification field. The method of using data D1231 will be described later.

[0025] Data D1241 shown in Fig. 6 is an example of the cross-section transition data 124 shown in Fig. 1. The cross-section transition data 124 stores data on the order in which the system configuration data group (i.e., the group of data D1211) stored in the system configuration data 121 transitions according to time series for each scenario and plan. The data D1241 is generated as a result of calculation as described below, but the data may also be input manually in advance by the user.

[0026] The data shown in Fig. 7 is an example of the scenario data 125 shown in Fig. 1. The scenario data 125 stores time-series scenarios based on various future predictions, such as future power demand and power generation predictions, demographic trends by region, and electrification rates. In the example shown in Fig. 7, a demand scenario, a renewable energy introduction amount scenario, and an electrification rate scenario are stored. The scenarios with scenario IDs = Scenario1 and Scenario2 shown in data D1241 in Fig. 6 are also stored in the scenario data 125, and Fig. 7 shows data related to the scenario with scenario ID = Scenario1.

[0027] Data D1251 stores a master scenario that integrates a demand scenario, a renewable energy introduction amount scenario, and an electrification rate scenario. For a scenario with a scenario ID=Scenario1, the demand scenario ID is "Demand A", the renewable energy introduction amount scenario ID is "RE A", and the electrification rate scenario ID is "Electrification A". Data D1252 stores the ID of the demand scenario, time, and a scenario value (demand value) corresponding to that time. Data D1253 stores the ID of the renewable energy introduction amount scenario, time, and a scenario value (introduction value) corresponding to that time. Data D1254 stores the ID of the electrification rate scenario, time, and a scenario value (electrification rate value) corresponding to that time. In the example shown in FIG. 7, the scenario values ​​(demand value, introduction value, electrification rate value) are set as magnifications relative to the reference values.

[0028] The data shown in Figures 4 to 7 may be data calculated in another system, or the database itself may exist in another system. The system configuration layer interpolation program 126, the system configuration generation program 127, and the multiple cross section generation program 128 shown in Figure 1 will be described later.

[0029] (Operation description) Fig. 8 is a flowchart for explaining the operation of the power system database operation system 1 shown in Fig. 1. This control program is stored in the main memory unit 11 of the power system database operation system 1 and executed by the central processing unit 10.

[0030] In processing step S1, the equipment data input to the main memory unit 11 is read, and an initial system configuration is created based on the read equipment data. This equipment data may be data input by the user via the input unit, or may be data input from another system (for example, the external system 20 in FIG. 1). The system configuration to be created is created with the same data structure as that shown in FIG. 2. At this time, one or more system configurations are created depending on the input equipment data.

[0031] As described later, when generating system configuration data, both the upper layer configuration and the lower layer configuration or only one of them may be used. When generating the system configuration, a unique value is automatically assigned by the system as the master ID, and an ID used within the system used by each operator is used as the facility ID. The system configuration created in processing step S1 is handed over to processing step S2.

[0032] In process step S2, the system configuration layer interpolation program 126 in Fig. 1 is executed to interpolate the missing system configuration and data in the system configuration (initial state system configuration) inherited from process step S1. Details of process step S2 will be described later. The equipment data whose configuration has been interpolated in process step S2 is inherited to process step S3.

[0033] In processing step S3, the system configuration generation program 127 is executed to reconstruct the system configuration inherited from processing step S3. By executing the system configuration generation program 127, equipment requiring condition setting is extracted based on the configuration condition setting data 123, and the upper layer configuration or the lower layer configuration is added to the system configuration for each piece of equipment, thereby reconstructing the system configuration data for analysis. The reconstructed system configuration for analysis is stored in the database of the system configuration data 121. Details of processing step S3 will be described later.

[0034] In processing step S4, calculation processing is performed by the multi-cross-section generation program 128 for the system configuration reconstructed in processing step S3. That is, various parameters included in the scenario are reflected in the parameters of the system configuration using the input scenario reflection method, and further, the system configuration is multi-cross-sectioned using the period and time granularity of the scenario. Furthermore, cross-section transition data is created that records the scenario ID and chronological order reflected in the multi-cross-section system configuration. The system configuration group created by multi-cross-sectioning is stored in the database of system configuration data 121 in FIG. 1, and the created cross-section transition data is stored in the database of cross-section transition data 124 in FIG. 1.

[0035] In process step S5, it is determined whether or not process steps S2, S3, and S4 have been executed for all the input system configurations. If the result of process step S5 is NO, the process returns to process step S2, and if the result of process step S5 is YES, the process proceeds to process step S6. In process step S6, the results of process steps S2 to S5 are output. For example, the output unit 15 in FIG. 1 may display an output screen as described below on a display monitor, or output data may be output to the external system 20.

[0036] (Detailed description of processing step S2) Fig. 9 is a flowchart showing the detailed processing of processing step S2. In processing step S201, the equipment included in the system configuration data generated in processing step S1 is searched for, and equipment data consisting of only one of the upper configuration or lower configuration, i.e., equipment data to be interpolated, is extracted. Then, for each extracted piece of equipment, the interpolation processing of the following processing steps S202 and S203 is executed.

[0037] In process step S202, using the equipment extracted in process step S201 and layer interpolation setting data 122 (see data D1221 in FIG. 4), if the extracted equipment does not have equipment data of a lower layer, the configuration of the lower equipment data is interpolated using an interpolation method registered in the layer interpolation setting data 122. In the example of FIG. 4, the interpolation is performed using a template of the lower configuration registered in data D1221. The interpolation method may be a simple method based on a template, or may be generated using a mathematical method such as graph theory according to the type of upper equipment.

[0038] In processing step S203, processing is also performed using the equipment extracted in processing step S201 and the layer interpolation setting data 122. In processing step S203, if the extracted equipment does not have upper layer electrical data, the upper layer electrical data is interpolated using the interpolation method registered in the layer interpolation setting data 122. In the example shown in data D1221 in Fig. 4, the upper layer substation capacity is interpolated with the minimum capacity value of the lower equipment, and for example, when all equipment is connected in series, the capacity of the upper layer is the same as the capacity of the bottleneck equipment.

[0039] Fig. 10 is a diagram showing an overview of the processing in processing steps S202 and S203, and shows a case where the interpolation method shown in data D1221 in Fig. 4 is applied to substation equipment. Here, substation X is equipment (higher-level configuration) specified by the user. In processing step S201, this substation X is extracted as equipment data consisting only of higher-level configuration, i.e., equipment data to be interpolated.

[0040] The process shown on the left side of Fig. 10 shows a specific example of process step S202, and the process shown on the right side shows a specific example of process step S203. In process step S202, before the process shown above the arrow, the equipment of the lower configuration is blank. On the other hand, after the process shown below the arrow, the equipment constituting the substation X is interpolated based on the interpolation method B2 of the data D1221. In process step S203, in the higher-level configuration before the process shown below the arrow, the parameter column is blank. On the other hand, after the process shown above the arrow, the parameter column of the higher-level configuration is interpolated based on the interpolation method B1 of the data D1221.

[0041] In process step S204, it is determined whether or not the interpolation process has been performed for all the interpolation targets extracted in process step S201. If the interpolation process has not been completed for all, the process returns to step S202, whereas if the interpolation process has been completed for all, the series of interpolation processes in Fig. 9, i.e., process step S2 in Fig. 8, is terminated, and the process proceeds to process step S3 in Fig. 8.

[0042] (Detailed description of processing step S3) 11 is a flowchart showing the detailed processing of processing step S3. In processing step S301, configuration condition setting data 123 is acquired, and equipment requiring condition setting is extracted. In processing step S302, the equipment extracted in processing step S301 is compared with configuration condition setting data 123 based on user input, and it is determined whether to use the upper layer configuration or the lower layer configuration for each piece of extracted equipment. In processing step S303, for equipment for which it has been determined in processing step S302 that the upper layer configuration should be used, the upper layer configuration is added to the system configuration, and for equipment for which it has been determined in processing step S302 that the lower layer configuration should be used, the lower layer configuration is added to the system configuration, thereby reconstructing the system configuration for analysis.

[0043] If there are no instructions from the user regarding the system configuration conditions, the system configuration is composed of data from the lower layer. On the other hand, if there are instructions regarding the system configuration conditions, the configuration of the upper layer is used. In other words, the lower equipment group included in the upper layer is extracted, and the lower layer equipment group is rounded down and replaced with the upper layer equipment, thereby performing a contraction. By executing the system configuration generation program 127, equipment requiring condition setting is extracted based on the configuration condition setting data 123, and the upper layer configuration or lower layer configuration for each piece of equipment is added to the system configuration, thereby reconstructing the system configuration data for analysis.

[0044] 12 is a diagram showing an example of the processing overview of processing steps S302 and S303, and is an example in which the group of facilities surrounded by dashed line 20 is reconstructed using a higher-level configuration called demand area 21. A higher-level configuration (demand area 21) is set in which the group of facilities surrounded by dashed line 20 is a lower-level configuration, according to an instruction from a user. If an instruction to contract the group of facilities surrounded by dashed line 20 is stored in configuration condition setting data 123, contraction is performed, and the electrical data of the higher-level configuration is used during analysis.

[0045] In process step S304, it is determined whether or not the processes in process steps S302 and S303 have been performed for all of the equipment extracted in process step S301. If the determination in process step S304 is NO, the process returns to process step S302. On the other hand, if the determination in process step S304 is YES, the process proceeds to process step S305, where the reconstructed system configuration for analysis is stored in the database of system configuration data 121. The system configuration reconstructed in process step S3 is handed over to process step S4.

[0046] (Detailed description of processing step S4) FIG. 13 is a flowchart showing the detailed processing of processing step S4, that is, the calculation processing by the multi-cross-section generation program 128. The processing of processing step S4 is executed based on the system configuration reconstructed in processing step S3. In processing step S401, in addition to reading the scenario data 125, various parameters included in the scenario are reflected in the parameters of the system configuration using the input scenario reflection method. In addition, for each system configuration, the system configuration is multi-cross-sectioned in chronological order by reflecting it in the system configuration using the period and time granularity of the scenario. For example, in the case of data D1252 of the demand scenario shown in FIG. 7, the load value included in the system configuration is corrected with the demand value, and if the demand scenario is for 5 years and every hour, each demand value is used to expand one system configuration to a system configuration for 5 years and every hour.

[0047] In process step S402, the scenario ID and chronological order reflected in the system configuration of the multiple cross sections generated in process step S401 are recorded, and cross section transition data as shown in Fig. 6 is created. In process step S403, it is determined whether or not the process of process step S402 has been performed for all cross sections generated in process step S401. If the determination is NO, the process returns to process step S402, and if the determination is YES, the process proceeds to process step S404. In process step S404, data of the group of system configurations obtained by multiplying cross sections by reflecting the scenario, and the cross section transition data are stored in a database. The data of the group of system configurations is stored in the database of system configuration data 121, and the cross section transition data is stored in the database of cross section transition data 124.

[0048] FIG. 14 is a diagram showing an example of an output screen in the above-mentioned processing step S6 (see FIG. 8). A selection screen 30 is displayed on the left side of the screen, and a result display screen 31 is displayed on the right side of the screen. A display area 301 of the selection screen 30 is an area where the system configuration is displayed. When there are multiple user-defined system configurations, one of the multiple system configurations is selected by operating a triangular icon 304 in an operation area 303, and the selected configuration is displayed in the display area 301. In FIG. 14, one of the system configurations input by the user, a configuration A1, is selected and displayed. A display area 302 of the selection screen 30 is an area where the scenario is displayed. When there are multiple scenarios used in the calculation, one of the multiple scenarios is selected by operating a triangular icon 306 in an operation area 305, and the selected scenario is displayed in the display area 302. In FIG. 14, a scenario B1 is selected and displayed.

[0049] A result display screen 31 on the right side of the screen displays results based on the system configuration and scenario selected on the selection screen 30. In the example shown in FIG. 14, results related to system configuration A1 and scenario B1 are displayed. Cross-section transition data according to the selection on the selection screen 30 is referenced, and a time series cross-section group 311 generated is displayed in the upper part of the result display screen 31, and a system configuration (detailed equipment information) 312 of a cross-section 311A ​​selected by the user from the cross-section group is displayed in the middle part of the screen. When equipment 313 (substation 1) of the system configuration 312 is selected, a group of equipment constituting the equipment 313 (substation 1), i.e., equipment information 314 of the equipment 313 (substation 1), is displayed in the lower part of the screen.

[0050] As described above, in the power system database operation system 1 of this embodiment, the system configuration database 121 is a hierarchical database having two or more layers, with respect to multiple power facilities included in the system configuration, in which an upper layer including data of upper power facilities and a lower layer including data of lower power facilities constituting the upper power facilities have a relationship as shown in Figures 2 and 3. Furthermore, a master ID that uniquely specifies the power facilities in all system configurations and a facility ID that uniquely specifies the power facilities in the system configuration in which the power facilities are included, i.e., a master ID that is unique on the time axis and the space axis and a facility ID that is unique on the space axis, are assigned to each of the multiple power facilities included in the system configuration.

[0051] For example, consider two cross sections 311A ​​and 311B with different dates and times in the time series cross section group 311 in Fig. 14. Fig. 15 shows an example of system configuration data D1211A for the cross section 311A, and Fig. 16 shows an example of system configuration data D1211B for the cross section 311B. Each of the cross sections 311A ​​and 311B has multiple pieces of equipment, and each piece of equipment is assigned a master ID and a facility ID.

[0052] When comparing the system configuration data D1211A and the system configuration data D1211B, there is no change in the configuration (sub-configuration) of the substation 1, and they are the same. However, even for substations 1 with the same configuration, the dates and times (i.e., positions on the time axis) are different between the system configuration data D1211A and the system configuration data D1211B. Therefore, the values ​​of the master IDs of the substations 1 are different, with ID=1000 in the system configuration data D1211A and ID=2000 in the system configuration data D1211B. Therefore, each piece of equipment can be uniquely specified in terms of time and space in the database of the system configuration data 121 by the master ID.

[0053] On the other hand, equipment IDs are related to management within a section, so for example, the equipment ID of substation 1 is X, but the same equipment ID is not assigned to any equipment within this section. Also, in the case of a master ID, the ID value differs depending on the section even for the same equipment, but as shown in Figures 15 and 16, the equipment ID of substation 1 is assigned X in every section. Therefore, by managing equipment IDs, it is possible to maintain the identity of equipment.

[0054] In this way, the system configuration database 121 uses a multi-layer structure for equipment management, and assigns and manages a master ID and equipment ID to equipment in each layer. Equipment parameters used in system planning and system analysis of the power system are stored in each layer. Therefore, having the same ID management structure in each layer makes it easy to obtain and process data, and by following each layer in order, it becomes possible to comprehensively understand what the equipment in question is made up of.

[0055] As a result, it is possible to generate system configurations with spatial granularity (e.g., the relationship between substations and the transformers inside them) and time granularity (e.g., the relationship between a system configuration for each year in a system plan and a system configuration for each hour in an operation analysis) in accordance with different business purposes such as equipment planning and operation analysis, while appropriately managing data such as facilities and individual equipment from equipment data in a power system. In other words, it is possible to handle long-term, multi-scenario system equipment data that can be used for both equipment planning and operation while maintaining consistency. This allows users of the system configuration to easily extract system configurations that suit their purposes without being aware of differences in data, reducing the amount of work required.

[0056] -Second embodiment- In the second embodiment, a case will be described in which the power system database operation system 1 described in the first embodiment is used for equipment planning and analysis of the system based on the equipment plan. The hardware configuration diagram in the second embodiment is similar to the configuration shown in FIG. 1 of the first embodiment. In the second embodiment, it is assumed that the external system 20 in FIG. 1 is a system planning system. Then, consider the case in which the reliability and operation costs of the system are analyzed for each of the cases of reinforcing a substation in a specified future and building a new substation in a specified future as equipment measures.

[0057] Fig. 17 is a diagram showing a processing procedure in the external system 20. In processing step S21, candidate countermeasures for facilities are created to deal with future demand changes. Any method may be used to create the candidate countermeasures, such as human input, handover from another system, or generation by mathematical processing, and the method of creation is not important. Here, for substations whose utilization rate is expected to increase in the future, candidate countermeasure 1 is created to reinforce the substation, and candidate countermeasure 2 is created to remove the existing substation and build a new substation.

[0058] In processing step S22, data on the system configuration after the equipment countermeasures are taken is created for the created countermeasure candidate 1 and countermeasure candidate 2. Here, the method of creation may be human input, takeover from another system, or automatic generation by the system. First, it is assumed that the current equipment, i.e., the system configuration before the equipment countermeasures are taken, is already stored in the system configuration data 121. FIG. 18 shows the system configuration data before the countermeasures are taken. In the system configuration A before the countermeasures, data on a substation 1 equipped with a transformer 1 with a capacity of 10 MVA is stored. The master IDs of the substation 1 and the transformer 1 are 0001 and 1001, and the equipment IDs are X and Tr1. The system configuration A covers the equipment configuration for the entire cross section, and the substation with equipment ID=X is a part of that configuration.

[0059] The system configurations for countermeasure candidate 1 and countermeasure candidate 2 created in processing step S22 are data related to substations that are part of system configuration A. In the case of countermeasure candidate 1, the expansion of the substation does not change the management name of the substation, and only the capacity of the transformer is changed from 10MVA to 15MVA due to the expansion. In the case of countermeasure candidate 2, the internal configuration of the substation does not matter, and a new substation is built with only the specifications defined, and the capacity is set to 20MVA. Together with this data, data on the scenario reflection method is created in processing step S22.

[0060] In process step S23, the data created in process step S22 is input to the power system database operation system 1 shown in Fig. 1 via communication. Then, process step S0 is executed. This process step S0 is a process executed by the power system database operation system 1, and the process of Fig. 8 explained in the first embodiment is executed based on the data of countermeasure candidate 1 and 2 input from the external system 20.

[0061] In the following, detailed explanation of the process in Fig. 8 will be omitted, and only the main points will be described. In process step S1 in Fig. 8, a system configuration for countermeasure candidate 1 and a system configuration for countermeasure candidate 2 are generated based on the input data for countermeasure candidate 1 and 2. Then, processes from process step S2 to process step S4 are executed for each system configuration. Fig. 19 is a diagram showing system configuration B for countermeasure candidate 1, and Fig. 20 is a diagram showing system configuration C for countermeasure candidate 2.

[0062] In processing step S2 of FIG. 8, a system configuration layer interpolation program 126 is executed. In the case of system configuration C of countermeasure candidate 2, the lower layer related to substation 2 (newly constructed substation) of system configuration C of FIG. 20 is interpolated, and a system configuration based on a template is temporarily input. In processing step S3 of FIG. 8, a system configuration generation program 127 is executed. Since the equipment in question is a substation this time, it is assumed that detailed analysis of the surroundings is unnecessary, and the surrounding system configuration is rounded down to the facilities of the upper layer. In processing step S4 of FIG. 8, a multi-section generation program 128 is executed, and a group of sections of the system configuration reflecting a scenario of a predetermined period and a predetermined granularity is obtained. Then, in processing step S6 of FIG. 8, the processing result is registered in a database and is output to an external system 20 via communication.

[0063] In process step S24, predetermined KPIs (Key Performance Indicators) such as predetermined reliability analysis costs and utilization rates, such as voltage and heat capacity, are calculated for each generated section. At this time, it is possible to perform analysis up to the year in which measures are taken for the substation, for example, and by extending the scenario reflected in process step S0, the obtained section will also be a long-term one, making it possible to perform reliability and KPI evaluations based on longer-term facility measures.

[0064] In addition, because the upper and lower layers of the system configuration are consistent at this stage, it is possible to perform analysis targeting both and provide feedback to facility measures. For example, if there is no problem with reliability in system configuration C, which involves the construction of a new substation, but reliability is affected in system configuration B, which involves the implementation of reinforcement at the substation, the analyst can provide feedback to the person taking the facility measures, such as increasing the reinforcement value of the substation transformer or strengthening other equipment as well. In this case, there is no need to recreate data between the different industries of facility planning and system analysis, which facilitates collaboration between different industries.

[0065] As described above, according to the second embodiment, when the power system database operation system 1 is used for facility planning and system analysis based on the facility planning, it is possible to smoothly use common data between different businesses. In addition, it is expected that the integrated management of data will strengthen cooperation between businesses and simplify the work of archiving past system configurations. Furthermore, by using the power system database operation system 1, even if the granularity of the boundary facilities between different businesses or the management methods are different, it is possible to generate a common system configuration by classifying by layer or adding new facilities to a higher layer.

[0066] According to the embodiment of the present invention described above, the following advantageous effects are achieved.

[0067] (1) As shown in Figs. 1 and 2, the power system database operation system 1 includes a power system equipment database of a system configuration, which is a power system equipment model including a plurality of power facilities, for a plurality of power system equipment models. Data D1211 shown in Fig. 2 is a power system equipment database for a system configuration A. Data D1211 is a hierarchical database including two or more layers having a relationship between data D1213, which is an upper layer including data of upper power equipment, and data D1214, which is a lower layer including data of lower power equipment constituting the upper power equipment. In data D1211, equipment parameters used in system planning and system analysis of the power system are stored in data D1213 and D1214, and a master ID that uniquely specifies a power facility (e.g., substation 1) in all data D1211 and an equipment ID that uniquely specifies a power facility (substation 1) in substation 1 including the power facility are stored in association with each of all power facilities.

[0068] By assigning a master ID that uniquely specifies the power equipment to each piece of data D1211 in the system configuration data 121 shown in FIG. 2, it is possible to identify which piece of equipment belongs to which section among the sections arranged in chronological order by the master ID. Furthermore, if the forecast scenario is different, the master ID will be different even for sections that are parallel in time at the same date and time, so long-term or multi-scenario system equipment data can be handled with consistency. Furthermore, by managing the equipment configuration within a section with the equipment ID, the identity of the equipment is maintained. Therefore, long-term and multi-scenario system equipment data that can be used for both equipment planning and operation can be handled with consistency.

[0069] (2) Also, as shown in Fig. 1, 4 and 10, the system includes layer interpolation setting data 122, which is a database storing data D1221 that is information for interpolating the configuration and / or equipment parameters of power equipment in a layer, and a central processing unit 10 and a system configuration layer interpolation program that function as a layer interpolator that interpolates the configuration and / or equipment parameters of power equipment that are insufficient in a layer based on the data D1221. As a result, even if there is a shortage in the input system configuration data, it is interpolated to an appropriate data configuration, and it is possible to handle both geographical and global equipment information in equipment planning and detailed electrical information in system analysis.

[0070] (3) As shown in Figs. 1, 5, 11 and 12, data D1231, which is information for generating an equipment configuration according to the usage method of the power system database operation system, is stored in the database of configuration condition setting data 123. The central processing unit 10 and a system configuration generation program are provided as a reconstruction unit that reconstructs the system configuration to a granularity according to the operation purpose based on the data D1231. As a result, the system configuration is reconstructed according to the operation purpose, and it becomes possible to handle both geographical and global equipment information in the facility plan and detailed electrical information in the system analysis.

[0071] (4) Further, as shown in Fig. 1, 7 and 13, the system includes scenario data 125, which is a database storing scenario data D1251, which is a future assumption scenario based on future forecast information, and a central processing unit 10 and a multiple cross-section generation program 128 functioning as a first generation unit that generates a plurality of new system configurations in a time series based on the scenario data D1251 and a system configuration, which is a reconstructed system equipment database. A time series cross-section group according to the future assumption scenario is generated based on input data.

[0072] (5) Furthermore, as shown in Figures 1, 6, 13 and 14, the central processing unit 10 and the multi-section generation program 128 also function as a second generation unit that generates transition data that records the chronological transition order of the generated multiple system configurations, and cross-section transition data such as that shown in Figure 6 is automatically generated.

[0073] (6) Furthermore, as shown in Fig. 1, the power system database operation system 1 includes an input unit 14 and a communication unit 13 that function as input units for data for configuring the power system configuration A shown in Fig. 2, which is a power system equipment model, i.e., data related to the power equipment included in the power system configuration A, and a central processing unit 10 that functions as a conversion unit that converts the input data into data D1211 for the power system configuration A. Regardless of the purpose of using the power system database operation system 1, the efficiency of data input can be improved.

[0074] The above-described embodiments are merely examples, and the present invention is not limited to these embodiments as long as the characteristics of the invention are not impaired. Other embodiments that are conceivable within the scope of the technical idea of ​​the present invention are also included in the scope of the present invention. [Explanation of symbols]

[0075] 1 ... power system database operation system, 10 ... central processing unit, 11 ... main memory unit, 12 ... auxiliary memory unit, 13 ... communication unit, 14 ... input unit, 15 ... output unit, 20 ... external system, 121...system configuration data, 122...layer interpolation setting data, 123...configuration condition setting data, 124...section transition data, 125...scenario data, 126...system configuration layer interpolation program, 127...system configuration generation program, 128...multi-section generation program

Claims

1. A power system database operation system including a power system equipment database for a power system equipment model including a plurality of power facilities, the power system equipment database including a plurality of the power system equipment models, The system equipment database includes: A hierarchical database having two or more layers, each layer having a relationship between an upper layer including data of a higher-level electric power equipment and a lower layer including data of a lower-level electric power equipment constituting the higher-level electric power equipment, Equipment parameters used in system planning and system analysis of the power system are stored in the layer; a first ID that uniquely specifies the power equipment in all of the power equipment databases, and a second ID that uniquely specifies the power equipment in the power equipment database in which the power equipment is included, are stored in correspondence with each of all of the power equipment.

2. 2. The power system database operation system according to claim 1, a first information database in which first information for interpolating the configuration of the power equipment and / or the equipment parameters in the layer is stored; A layer interpolation unit that interpolates configurations and / or equipment parameters of the power equipment that are missing in the layer based on the first information.

3. 2. The power system database operation system according to claim 1, A second information database in which second information for generating an equipment configuration according to a usage method of the power system database operation system is stored; A power system database operation system comprising: a reconstruction unit that reconstructs the power system equipment database to a granularity according to an operation purpose based on the second information.

4. In the power system database operation system according to claim 3, a scenario database storing future scenarios based on future forecast information; a first generation unit that generates a plurality of new power system equipment databases in time series based on the future assumption scenario and the reconstructed power system equipment database.

5. In the power system database operation system according to claim 4, A power system database operation system comprising: a second generation unit that generates transition data that records a chronological transition order of the generated plurality of power system equipment databases.

6. 2. The power system database operation system according to claim 1, an input unit to which third information regarding power equipment included in the power system equipment model is input; a conversion unit that converts the input third information into the power system equipment database.

Images