Power grid protection and control planning device and power grid protection and control planning program

Abstract

To provide a power grid protection and control planning device and program that efficiently identifies processes requiring verification, and enables the modification and verification of those processes, in order to formulate a processing plan that meets reliability and performance standards within a predetermined timeframe while the grid conditions are changing. [Solution] In the power system protection control system 1, the power system protection control planning device 2, which formulates a power system protection control plan, includes a modification necessity determination unit 104 that determines whether or not to modify the protection control plan based on an evaluation of the impact on assumed cases due to changes in the system state indicated by system state data that shows the future system state of the power system, and a plan modification setting unit 106 that identifies the processes to be modified in the protection control plan based on an evaluation of the correlation between assumed cases.

Description

TECHNICAL FIELD

[0001] The present invention relates to a technology for creating a protection control plan for protecting an electric power system, and is suitably applied to, for example, an electric power system. BACKGROUND ART

[0002] Conventionally, an entire facility that is composed of power generation facilities, power transmission facilities, substation facilities, distribution facilities, and consumer facilities and performs processes from power generation to power consumption (hereinafter referred to as "electric power system") is known. In the operation of the electric power system, high reliability and efficiency are desired to ensure continuous supply of high-quality electric power not only in normal times with no accidents, but also in the event of a failure or abnormality of the facilities (at the time of fault).

[0003] On the other hand, in recent years, due to the expanded introduction of renewable energy power sources that use sunlight, wind power, etc., uncertain and short-term changes in system conditions such as fluctuations in power flow have been increasing, and countermeasures are required.

[0004] Further, in order to maintain high-quality power supply in the electric power system, protection control systems such as an electric power system monitoring system, an electric power system stabilization system, and a protection relay system are present. The protection control system operates in cooperation with a planning system that is responsible for wide-area cooperative operation in a central control station or the like and drafting of control plans, and an execution system that is responsible for monitoring and controlling system facilities by edge devices such as power plants and substations.

[0005] Examples include an electric power system monitoring and control system that controls power, voltage, and the like flowing in the system based on information such as system power flow, a system stabilization system that controls generators and circuit breakers to prevent the spread of accidents when a failure occurs, and a protection relay system that detects excess current or voltage of facilities and disconnects the target facility.

[0006] For these systems, in order to ensure highly reliable and efficient grid operation, it is crucial that the planning system predicts future grid conditions, formulates and verifies protective control processing plans based on these predictions, and reliably deploys these processing plans to the edge devices of the execution system within the required time.

[0007] In recent years, the increase in distributed power sources such as solar power and grid-mounted batteries, as well as the expansion of coordinated grid operations across wide areas, has led to an increase in the number of variables and constraints that must be considered in protection and control planning (processing plans) within protection and control systems. Therefore, it is necessary to predict and plan future grid conditions in advance (a few minutes to a few hours before the processing plan is executed) to ensure sufficient computation time for the processing plan.

[0008] On the other hand, the expansion of renewable energy causes grid conditions to fluctuate significantly in short periods (a few seconds to a few minutes), making it difficult to predict future grid conditions with sufficient accuracy. This can lead to discrepancies between predictions made during planning and actual grid conditions during processing (prediction errors), potentially resulting in inappropriate processing and damaging the reliability and performance (generation costs, etc.) of the power grid.

[0009] For example, in under-frequency relays (UFRs) that perform load shedding during frequency drops to prevent a decrease in power grid frequency, changes in power flow direction due to increased renewable energy generation can lead to inappropriate control, such as unnecessary load shedding or load shedding that causes frequency deterioration, potentially compromising reliability.

[0010] As a protective control planning technology to respond to short-term system changes due to uncertain elements in power systems, a method of formulating multiple processing plans and switching between them during execution is known. For example, Patent Document 1 discloses a technology that predicts multiple possible system states and determines the control content according to each system state based on a reliability evaluation of combinations of multiple system states and assumed fault cases, so as to satisfy predetermined reliability conditions. [Prior art documents] [Patent Documents]

[0011] [Patent Document 1] Japanese Patent Publication No. 2019-216534 [Overview of the project] [Problems that the invention aims to solve]

[0012] Patent Document 1 states that it is necessary to comprehensively evaluate the combinations of assumed system conditions and fault cases, and considering the evaluation of N-1 fault cases (failure of a single piece of equipment in the power system), it is necessary to evaluate a vast number of combinations of system conditions and fault cases.

[0013] Furthermore, the increase in distributed power sources leads to an increase in the number of system conditions and failure cases that need to be considered. Designing, verifying, and deploying protective controls (processes) for all of them would increase the system's computational and communication load, making it difficult to design and deploy processing of sufficient quality within the required time.

[0014] To address changes in the grid system, one possible approach is to reduce the processing load while keeping the system in sync with the changes by sequentially modifying the processing plan (prediction deviation correction processing) when a change in the future grid state compared to the prior prediction (prediction deviation correction processing) is detected.

[0015] On the other hand, even if a change in the system state occurs, the processing plan (control) does not necessarily become inappropriate. Unnecessary changes can lead to a deterioration in the system's processing efficiency, so it is necessary to accurately detect only the processes that require attention.

[0016] Furthermore, if there are dependencies between the assumed cases being considered (for example, N-1 failures and N-1-1 failures (cases where additional equipment fails after a single piece of equipment in the power system fails)), changing the processing of a specific case may negatively affect the reliability and performance of other cases. Therefore, it is necessary to efficiently carry out corrections and verifications while considering the scope of impact of the changes.

[0017] Furthermore, it is necessary to complete the modification and verification of the process to meet at least a certain level of reliability within the required time and then deploy the process to the edge device. However, if there is sufficient time for modification, it is desirable to modify it to achieve higher reliability and performance.

[0018] This invention has been made in consideration of the above points, and aims to efficiently identify processes that require verification in a protection control plan in response to changes in the power system conditions. [Means for solving the problem]

[0019] To solve these problems, for example, the configuration described in the claims is adopted. That is, a power system protection and control planning device for formulating a power system protection and control plan, comprising: a modification necessity determination unit that determines whether or not to modify the protection and control plan based on an evaluation of the impact of changes in the system state indicated by system state data indicating the future system state of the power system on assumed cases; and a plan modification setting unit that identifies the processes to be modified in the protection and control plan based on an evaluation of the correlation between the assumed cases.

[0020] The present invention also includes a power system protection and control planning program and a storage medium for storing it, which causes a computer, which is a power system protection and control planning device, to function as a correction necessity determination unit that determines whether or not to modify the protection and control plan based on an evaluation of the impact of changes in the system state indicated by system state data indicating the future system state of the power system on assumed cases, and a plan modification setting unit that identifies the processes to be modified in the protection and control plan based on an evaluation of the correlation between the assumed cases. [Effects of the Invention]

[0021] According to one example of the present invention, efficient verification can be performed in response to various changes in the system state of a power grid. Problems, configurations, and effects other than those mentioned above will be clarified by the following embodiments and the description of Example 1. [Brief explanation of the drawing]

[0022] [Figure 1] This is a diagram showing a configuration example of the power system protection control system 1 according to the first embodiment. [Figure 2] This is a diagram showing an example of the environmental state data 211 according to the first embodiment. [Figure 3] This is a diagram showing an example of the device setting data 212 according to the first embodiment. [Figure 4] This is a diagram showing an example of the device state data 213 according to the first embodiment. [Figure 5] This is a diagram showing an example of the system device configuration data 202 according to the first embodiment. [Figure 6] This is a diagram showing an example of the assumed case data 203 according to the first embodiment. [Figure 7] This is a diagram showing an example of the processing plan data 204 according to the first embodiment. [Figure 8] This is a diagram showing an example of the case impact evaluation data 205 according to the first embodiment. [Figure 9] This is a diagram showing an example of the plan evaluation data 206 according to the first embodiment. [Figure 10] This is a diagram showing an example of the case relationship evaluation data 207 according to the first embodiment. [Figure 11] This is a diagram showing an example of the modification condition setting data 208 according to the first embodiment. [Figure 12] This is a diagram showing an example of the processing impact approximation data 209 according to the first embodiment. [Figure 13] This is a diagram showing an example of the modification setting data 210 according to the first embodiment [Figure 14] This is a flowchart showing an example of the protection control plan formulation processing in the first embodiment. [Figure 15] This is a diagram showing an example of the processing plan display screen according to the first embodiment. [Figure 16] This is a diagram showing an example of the plan evaluation display screen according to the first embodiment. [Figure 17] This is a diagram showing an example of the modification setting display screen according to the first embodiment. [Figure 18] This is a diagram for explaining a hardware configuration example of the power system protection control planning device 2 according to the first embodiment. [Modes for carrying out the invention]

[0023] One embodiment of the present invention is described in detail below. In this embodiment, when planning and evaluating an appropriate protection and control plan in response to changes in the power system status, a processing plan that meets reliability and performance standards is formulated within a predetermined time while the system status is changing. To this end, this embodiment efficiently identifies the processing that needs to be evaluated and modifies and evaluates the processing. In this embodiment, the evaluation also includes the concept of so-called verification.

[0024] In other words, this embodiment proposes a power system protection and control planning device for formulating a protection and control plan for a power system, comprising: a future system generation unit that generates "system state data" indicating the future system state of the power system; a modification necessity determination unit that determines whether or not the protection and control plan needs to be modified based on an evaluation of the impact of changes in the system state on assumed cases; and a plan modification setting unit that identifies the processes to be modified from the protection and control plan based on an evaluation of the correlation between assumed cases.

[0025] Here, it is desirable for the correction necessity determination unit to identify impact cases affected by prediction discrepancies as hypothetical cases and generate plan evaluation data to evaluate the reliability of the impact cases.

[0026] Furthermore, this embodiment also includes a program for causing the power system protection and control planning device to function as a computer, a storage medium containing such program, and a power system protection and control planning method executed by the power system protection and control planning device.

[0027] In this embodiment, the assumed case refers to the events that serve as the premise or cause of the processing. Furthermore, the processing plan is composed of a set of processes. Below, we will describe Example 1, a specific example of this embodiment. [Examples]

[0028] Figure 1 shows an example configuration of the power system protection and control system 1 of this embodiment. In Figure 1, the power system protection and control system 1 comprises a power system protection and control planning device 2, a power system protection and control device 5, and a power system electrical device 6. The power system protection and control planning device 2 and the power system protection and control device 5 are communicated to each other via a first communication network 3, and the power system protection and control device 5 and the power system electrical device 6 are communicated to each other via a second communication network 4.

[0029] The power system protection control planning device 2 comprises a processing unit 10, a recording unit 20, a communication unit 31, an input unit 32, and a display unit 33. First, the processing unit 10 comprises a main processing unit 101, a future system generation unit 102, a planning unit 103, a correction necessity determination unit 104, a plan evaluation unit 105, a plan correction setting unit 106, a plan correction unit 107, and a distribution management unit 108.

[0030] Furthermore, the recording unit 20 stores system status data 201, system equipment configuration data 202, assumed case data 203, processing plan data 204, case impact evaluation data 205, plan evaluation data 206, case relationship evaluation data 207, correction condition setting data 208, processing impact approximation data 209, correction setting data 210, environmental status data 211, equipment setting data 212, and equipment status data 213. Note that the environmental status data 211, equipment setting data 212, and equipment status data 213 constitute the system status data 201.

[0031] The processing unit 10 may be implemented by software that performs processing according to various programs stored in the recording unit 20, or by hardware such as circuits.

[0032] Furthermore, these features are not limited to those implemented by a single device, but may be implemented by multiple devices connected to each other in a manner that allows for communication. The recording unit 20 is implemented by a storage device or storage medium.

[0033] Furthermore, the communication unit 31 is implemented by a communication device and connects to the power system protection control device 5 and the power system electrical equipment 6 via the first communication network 3 and the second communication network 4.

[0034] The input unit 32 can be implemented using input devices such as a keyboard, a mouse or other pointing device, a touch panel, or a voice instruction device, and accepts input from the user. The input unit 32 is implemented by including at least one of these devices, such as a pointing device or a touch panel.

[0035] The display unit 33 can be a display device, a printer, an audio output device, etc., and can be implemented by including at least one of these, outputting the processing results of the power system protection control planning device 2, etc. Thus, the display unit 33 is an example of an output unit.

[0036] The input unit 32 and the display unit 33 may be integrated into a single unit, such as a touch panel, or at least one of them may be omitted. Furthermore, the input unit 32 and the display unit 33 may be provided in a terminal device that is configured separately from the power system protection control planning device 2.

[0037] The power system protection control device 5 comprises a management unit 501 that manages the configuration of the protection control modules, a communication unit 502 that communicates via the first communication network 3, and a protection control module 50 that performs protection control processing. The power system protection control device 5 also stores one or more protection control modules 50 that contain the specific details of processing such as acquiring and processing measurement data and operating and changing the settings of electrical equipment, and the management unit 501 can select the module that will actually perform the processing.

[0038] The power system protection control device 5 can be implemented in a way that allows for the replacement of protection control modules using known technologies such as virtual machines or containers, but it may also be implemented using other methods. The power system protection control device 5 is also referred to as a power system edge device or edge device.

[0039] The protection control module 50 includes a module processing unit 551 that performs protection and control operations for the power system electrical equipment 6, a module recording unit 552 that records the contents of the processing, and a module communication unit 553 that communicates with the power system electrical equipment via the second communication network 4.

[0040] The protection control module 50 can acquire measurement data from the measuring instrument 601 via a second communication network 4 connected to the module communication unit 553, based on instructions from the module processing unit 551, and store it in the module recording unit 552. The module processing unit 551 also uses the measurement data and other setting data in the module recording unit 552 to determine the operation to be performed on the electrical equipment 602, and the module communication unit 553 transmits this operation data to the electrical equipment 602 via the second communication network 4, allowing it to change its settings.

[0041] These processes are just examples, and the processes of the protection control module 50 and the module processing unit 551 may be various processes that improve the protection control of the power system, including transmitting information to the power system protection control planning device 2 via the communication unit 502, holding measurement data from the measuring instrument 601, operating the electrical equipment 602, and other useful processes.

[0042] Here, the power system protection and control planning device 2 and the power system protection and control device 5 can be realized as information processing devices (computers) such as circuits, printed circuit boards, or servers, which are equipped with a controller such as a CPU (Central Processing Unit) and a microprocessor, a storage device such as memory, a hard disk, or an SSD (Solid State Drive), and a communication device.

[0043] Therefore, the processing unit 10, the management unit 501, and the module processing unit 551 may be implemented by software that processes according to various programs stored in the storage device, or by hardware such as circuits. Furthermore, at least one of the planning unit 103 to the distribution management unit 108 may be provided in a separate device from the power system protection control planning device 2, such as the power system protection control device 5 or terminal devices.

[0044] Furthermore, these features are not limited to those implemented by a single device, but may be implemented by multiple devices connected to each other in a manner that allows for communication. The module recording unit 552 may also be implemented by a storage device or storage medium.

[0045] The communication unit 502 and the module communication unit 553 are implemented by communication equipment. Here, the communication unit 502 is connected to the power system protection control planning device 2 and the power system electrical equipment 6. The module communication unit 553 is connected to the power system protection control planning device 2 and the power system protection control device 5.

[0046] The power system electrical equipment 6 performs various processes related to power-related equipment. For this purpose, the power system electrical equipment 6 is equipped with measuring instruments 601 and electrical equipment 602.

[0047] Measuring instrument 601 measures the status of power-related equipment or the surrounding environment. Electrical equipment 602 can be implemented as protective control equipment such as protective relays to protect and appropriately control power-related equipment, and performs control over the equipment.

[0048] Furthermore, facilities related to electricity include power generation facilities that generate electricity using power generation equipment (for example, power plants), consumer facilities that consume the electricity generated by power generation facilities, and power distribution facilities that transmit electricity from power generation facilities to consumer facilities (transmission facilities, substations, distribution facilities, etc.).

[0049] Furthermore, while the power generation device is a device that performs thermal power generation, hydroelectric power generation, nuclear power generation, geothermal power generation, solar power generation, wind power generation, etc., it may also be a device that performs power generation using various other methods.

[0050] Power transmission and distribution equipment includes overhead transmission lines, underground transmission lines, transformers, circuit breakers, switches, phase adjustment equipment, and busbars, but may also include various other equipment related to power transmission and distribution. These are integrated to constitute the power system.

[0051] Furthermore, the measuring instrument 601 can be implemented with multiple measuring devices that measure the state at specific measurement points in the power system. Multiple measurement items are included. In this embodiment, weather items, setting and operating state items of electrical equipment 602, and operating state items of equipment are used as measurement items, but various other items can also be measured.

[0052] The power parameters include voltage, phase, and power. The weather parameters include temperature, wind speed, wind direction, precipitation, and solar radiation. The equipment operating status parameters indicate the operating status of equipment that changes the power flow state, such as power distribution equipment and power generation equipment.

[0053] The measurement points include the busbars of power generation facilities, the busbars of substations, power distribution facilities, and consumer facilities, and there may be one or more measuring devices for each measurement point. The values ​​measured by the measuring instrument 601 are transmitted to the power system protection control device 5 via the second communication network 4. They may also be transmitted to the power system protection control planning device 2 via the first communication network 3. Furthermore, there may be multiple power system protection control devices 5 and power system electrical devices 6.

[0054] In Figure 1, the future grid generation unit 102 generates grid state data 201 and / or grid equipment configuration data 202 that have future time. The future grid generation unit 102 may, for example, generate data with future time in response to user input via the input unit 32 and store the data, or it may acquire data from an external server (not shown) via the communication unit 31 and store the data.

[0055] Furthermore, for the grid status data 201 and grid equipment configuration data 202, past time data may be used. For example, average values ​​for the same date and time in the past may be used as grid status data 201 and grid equipment configuration data 202, or data with future time estimates may be generated using known machine learning techniques to obtain more accurate data; the system is not limited to data with the accuracy desired by the user. As an example of machine learning, demand forecasting is known to be achieved by learning weather data and demand data.

[0056] The grid status data 201 is data indicating the future grid status of the power grid, and in this embodiment, it includes environmental status data 211, equipment setting data 212, and equipment status data 213.

[0057] First, the environmental condition data 211 includes data for a future period that the power system protection and control planning device 2 is planning, and may also include past data for a certain period. For example, the environmental condition data 211 may include items measured by the measuring instrument 601, power information such as active power, reactive power, voltage, and phase flowing through the electrical equipment 602, and weather information such as temperature and wind speed.

[0058] Figure 2 shows an example of the environmental condition data 211 in this embodiment. The environmental condition data 211 is data relating to the status of power-related equipment or the surrounding environment. The environmental condition data 211 is data for a future period that the power system protection control planning device 2 is planning, and may also include past data for a certain period.

[0059] In Figure 2, point A is used as the measurement point. The environmental state data 211 includes information such as state ID 201D, data generation date and time 202D, data serial number No. 203D, target date and time 204D, active power 205D, reactive power 206D, and temperature 207D. These are stored along with the date and time of each item at point A.

[0060] Note that the active power 205D to temperature 207D are just examples of data items related to the point, and will be changed as appropriate depending on changes in the measurement content of measuring instrument 601 or electrical equipment 602.

[0061] Furthermore, the equipment setting data 212 is information indicating the setting status of the electrical equipment 602. The equipment setting data 212 is data for a future period that the power system protection control planning device 2 is planning, and may include past data for a certain period.

[0062] Next, Figure 3 shows an example of the equipment setting data 212 in this embodiment. The equipment setting data 212 includes, for example, status ID 301D, data generation date and time 302D, serial number 303D, target date and time 304D, open / closed state of circuit breaker B1 305D, open / closed state of circuit breaker B2 306D, tap position of transformer T1 307D, and tap position of transformer T2 308D. The equipment setting data 212 also stores information (setting values) indicating the settings of the electrical equipment 602, along with the date and time.

[0063] Furthermore, the switching of circuit breaker B1 305D and the tap position 308D of transformer T2 are items related to the settings of electrical equipment 602, and any combination of items obtainable from measuring instrument 601 can be appropriately adopted.

[0064] The equipment status data 213 is information (operational status information) indicating the operating status of electrical equipment 602, such as power distribution equipment and power generation equipment, that changes the power flow state. The equipment status data 213 is data for a future period that the power system protection control planning device 2 is planning, and may include past data for a certain period.

[0065] Figure 4 shows an example of the equipment status data 213 in this embodiment. The equipment status data 213 in this embodiment indicates the equipment status of electrical equipment 602, but status data for other equipment may also be used. As shown in Figure 4, the equipment status data 213 includes, for example, status ID 401D, data generation date and time 402D, serial number 403D, measurement date and time 404D, operating status of circuit breaker B1 405D, operating status of circuit breaker B2 406D, operating status of transformer T1 407D, and operating status of transformer T2 408D. The equipment status data 213 stores the operating status information of electrical equipment 602 along with the date and time. The operating status of circuit breaker B1 405D to the operating status of transformer T2 408D may include similar items related to electrical equipment 602, such as the open / closed status of switching devices such as circuit breakers and switches, and the power transmission status of the power transmission line.

[0066] Furthermore, the items in the equipment status data 213 may be a combination of items representing the operating status of equipment that changes the power flow state, such as power distribution equipment and power generation equipment, and items representing the operating status of other equipment obtained from the measuring instrument 601.

[0067] Next, the system equipment configuration data 202 is information relating to the electrical circuit aspects and economic aspects of the measuring instruments 601 and electrical equipment 602 that constitute the power system. Here, the system equipment configuration data 202 includes information necessary for the electrical circuit analysis of the power system. In addition, the system equipment configuration data 202 includes the electrical characteristics of the electrical equipment 602, operational conditions such as transmission capacity and voltage range, the electrical connection configuration of the equipment, whether it can withstand remote disconnection, and protection control functions such as overload protection.

[0068] Furthermore, the system equipment configuration data 202 includes information related to measurements by sensors in the power system, such as the measurement target, measurement conditions, and electrical connection configuration of the measuring instrument 601. It also includes information on economic aspects, such as the operating costs of the measuring instrument 601.

[0069] The system equipment configuration data 202 is data for a future period that the power system protection and control planning device 2 is responsible for planning, and may include past data for a certain period.

[0070] Figure 5 shows an example of the system equipment configuration data 202 in this embodiment. In this embodiment, a generator is used as an example of the power system. In Figure 5, the system equipment configuration data 202 includes information such as ID 501D, name 502D, period 503D, rated voltage 504D, minimum output 505D, maximum output 506D, output change rate 507D, remote shutdown capability 508D, and power generation cost 509D for each generator, and is stored for each piece of equipment. Here, the period 503D indicates the period during which the equipment exists in the same state, and if it is shorter than the evaluation period, the equipment will be changed due to plans such as new installation, replacement, or decommissioning.

[0071] Note that while Figure 5 shows the case of a generator, different items may be provided for other electrical equipment 602 such as power transmission lines or measuring instruments 601.

[0072] Next, the assumed case data 203 is information regarding assumed cases (such as failures or accidents) of the electrical equipment 602 that constitute the power system. Figure 6 shows an example of the assumed case data 203 in this embodiment.

[0073] Figure 6 shows hypothetical case data 203, using power transmission lines in a power system as an example. In Figure 6, the hypothetical case data 203 includes information such as case ID 601D, name 602D, faulty equipment 603D, fault type 604D, candidate operation variable 605D, influence dependent variable 606D, and reliability requirement 607D, and is stored for each hypothetical case.

[0074] First, the faulty equipment 603D indicates information such as the name of the electrical equipment 602, as well as the equipment ID and location. The fault pattern 604D indicates information about the expected state of the fault or accident, and may include information such as the number of lines and phases affected. Note that the fault pattern 604D is just one example of data items and will be changed as appropriate depending on the type of equipment specified in the faulty equipment 603D.

[0075] Furthermore, the candidate operation variable 605D may include information about the ID of equipment that may be subject to operation when a failure occurs, and variables related to that equipment (data items such as generator output). The dependent influence variable 606D may include information about the ID of equipment that may change above a certain level due to the occurrence of a failure or a change in the candidate operation variable 605D, and variables related to that equipment (data items such as power flow values ​​of transmission lines).

[0076] Reliability requirement 607D includes requirements for the reliability of the power system that must be met when a hypothetical scenario occurs. Reliability requirements include conditions related to the safety of power system equipment and the stability of supply.

[0077] Reliability requirements may include, for example, conditions such as the power flow value of a specific transmission line being below a predetermined value, or the frequency and voltage at a predetermined point in the power system being within a predetermined range. Furthermore, the predetermined reliability requirements may also include requirements such as the time it takes to disconnect a faulty section from the system in the event of a fault in the power system.

[0078] Furthermore, the hypothetical case data 203 may include items indicating the risk and probability of occurrence of accident cases. In addition, the hypothetical case data 203 may include hypothetical cases not only when a failure occurs, but also when no failure occurs (when all equipment is operating normally).

[0079] Next, the processing plan data 204 is information indicating the protection control plan (also referred to as the processing plan), which is the plan formulated in this embodiment. The processing plan data 204 is data for a future period that the power system protection control planning device 2 is planning, and may include information about protection control modules that are executed to bring the power system to a predetermined state.

[0080] Figure 7 shows an example of the processing plan data 204 in this embodiment. Figure 7 uses a power generator in a power grid as an example. Therefore, the processing plan data 204 includes information such as the plan ID 701D, generation date and time 702D, applicable date and time 703D, module ID 704D, case ID 705D, control content of the controlled equipment 706D, and module data 707D.

[0081] First, the plan ID 701D contains a management number used to identify the processing plan data. The generation date and time 702D contains a timestamp that identifies the date and time the processing plan data was created. The applicable date and time 703D contains time range information that the processing plan applies to, and includes information about the time when the module is actually scheduled to operate.

[0082] Module ID 704D contains a management number to identify the protection control module, thus identifying the protection control module. Case ID 705D contains a management number to identify the assumed case to which the protection control module corresponds, thus identifying the assumed case. Control content 706D contains setting value information indicating the control content for the power generation equipment G001 to G003, which are the controlled facilities.

[0083] In the plan shown in processing plan data 204 in Figure 7, for example, the control content "shutdown" for power generation equipment G001 of module ID "MoN001" in Figure 7 means that when assumed case ID "C001" occurs, the power generation equipment G001 will be shut off from the grid (the power flowing from the power generation equipment into the power grid will be set to 0) in order to prevent overloading of the transmission lines.

[0084] Furthermore, module data 707D includes binary data of the module to be executed by the power system protection control device 5. The equipment to be controlled in the control content 706D of the controlled equipment is equipment included in the electrical equipment 602, and may be, for example, a transformer, storage battery, circuit breaker and switch, or a combination of other equipment.

[0085] In Figure 7, the setting values ​​for the controlled equipment indicate whether or not the generator is shut off, but these could also be the reactive power or voltage settings of the generator, or a combination of multiple setting values. Note that the setting items for the control content 706D of the controlled equipment are just an example of data items and should be changed as appropriate depending on the type of controlled equipment.

[0086] Next, the case impact assessment data 205 contains information regarding the relationship between a predetermined system state change of the power system and the assumed cases that are affected. Figure 8 shows an example of the case impact assessment data 205 in this embodiment. The case impact assessment data 205 in Figure 8 includes information on system state item 801D and affected case 802D.

[0087] First, the grid status item 801D contains information indicating items related to each environmental state at a predetermined point included in the environmental status data 211 (such as power information and weather information). The impact case 802D contains information (such as a case ID) that identifies cases affected when a certain level of change occurs in the grid status item. Multiple case IDs may correspond to a single grid status item in the impact case 802D.

[0088] Next, the plan evaluation data 206 is information regarding the evaluation of a processing plan when a specific processing plan is executed under specific system conditions and specific assumed cases. Figure 9 shows an example of the plan evaluation data 206 in this embodiment.

[0089] The plan evaluation data 206 includes, for example, evaluation ID 901D, evaluation generation date and time 902D, plan ID 903D, evaluation status ID 904D, case ID 905D, evaluation module ID 906D, evaluation result pre-processing execution status 907D, evaluation result post-processing execution status 908D, and violation status 909D.

[0090] The evaluation ID 901D contains a management number to identify the evaluation result of the processing plan, thus identifying the evaluation result. The evaluation generation date and time 902D contains time information to identify the date and time when the evaluation result was generated. The plan ID 903D contains a management number for the processing plan to identify the processing plan that was evaluated in the evaluation result, thus identifying the processing plan.

[0091] The evaluation status ID 904D contains a status ID that identifies the system state that was assumed to be used to evaluate the evaluation result. The case ID 905D contains a management number that identifies the case that was evaluated in the evaluation result from among the cases included in the assumed case data 203. The evaluation module ID 906D contains a management number that identifies the module included in the processing plan that was evaluated in the evaluation result, and identifies the module.

[0092] Furthermore, the pre-processing execution states 907D to 909D (violation status) include information regarding the evaluation results of the processing plan under the circumstances in which the case was applied in that evaluation state. The pre-processing execution state 907D shows the evaluation results immediately after the case was applied in that evaluation state, in the state before the module was applied.

[0093] The post-processing state 908D shows the evaluation result under the condition that the case and module in question were applied in that evaluation state.

[0094] The Violation Status 909D stores the result of determining whether the reliability requirements are met, based on the reliability requirements of the specific case specified by the Case ID and the Post-Processing Status 908D. In addition, the Pre-Processing Status 907D to Post-Processing Status 908D contain information for identifying equipment or locations that do not meet the reliability requirements, information for identifying unfulfilled requirements, and information indicating the degree or amount of deviation from the constraints.

[0095] For example, the evaluation result for evaluation ID 901D "E001" indicates that, in the event of a specific accident case "C001," the equipment that deviates from the reliability requirements, based on the pre-processing state 907D to violation status 909D, is a specific transmission line "L002" in the power system. The deviation is related to an overload condition, resulting in an overload state (load factor 150%) relative to the transmission line's rated capacity (load factor 100%). As a result, executing evaluation module ID "MoN001" changes the transmission line's state to "load factor 120%."

[0096] However, since the rated capacity is exceeded, a violation is indicated as "Yes" in Violation Status 909D. These are just examples, and the data items may be changed as appropriate depending on the content of the constraints and the type of equipment. In addition, the plan evaluation data 206 may include not only the evaluation results regarding reliability requirements, but also other data items for measuring the operational efficiency and economics of the power system, such as the amount of output curtailment of renewable energy sources, the generation cost of generators, and the evaluation results regarding economics and efficiency such as transmission losses caused by power transmission. The pre-processing state 907D to violation status 909D constitute the evaluation results for the processing plan.

[0097] Next, the case relationship evaluation data 207 is information about the dependencies between multiple cases. Figure 10 shows an example of the case relationship evaluation data 207 in this embodiment. The case relationship evaluation data 207 in Figure 10 includes, for example, case ID 1001D and relationship case ID 1002D.

[0098] Case ID 1001D contains a management number to identify the case included in the assumed case data 203, thus identifying the assumed case. Related case ID 1002D contains information to identify case IDs that have a dependency on the case specified by case ID 1001D. A dependency is a relationship in which changing the processing plan for one case affects the system state or evaluation results assumed by other cases. An example of this is the relationship between cases such as N-1 failure and N-1-1 failure.

[0099] Specifically, the case with case ID "C002" in the second row of Figure 10 represents a case where power line "L002" fails (N-1 case), and the case with case ID "C004" represents a case where power line "L002" fails, and then power line "L003" also fails (N-1-1 case).

[0100] In this case, if a change is made to the processing plan executed when "C002" occurs, the system state assumed by "C004" will also change, affecting the evaluation results for the "C004" case. Therefore, "C004" can be said to have a dependency on "C002," and if a change is made to the processing plan for "C002," it becomes necessary to evaluate the processing plan for "C004" as well.

[0101] In Figure 10, the dependency relationships between cases are shown as an example of a two-body relationship, such as "C002" (parent) and "C004" (child), but the dependency relationships between cases may also be defined to include three or more relationships, such as "C002" (parent), "C004" (child), and "C104" (grandchild).

[0102] Here, the dependency relationship has a hierarchical structure, such as a superior-subordinate relationship from one case to another. This dependency relationship is an example of a correlation that shows the reciprocal relationship between cases. For this reason, correlations may be used in this embodiment. In other words, the relationship is not limited to hierarchical relationships such as parent-child-grandchild or one-way relationships, but may also be a bidirectional relationship where each party is equal.

[0103] In this case, each item in the case relationship evaluation data 207 may be a case ID that is correlated with the others, or a case ID and a related case ID may be used as shown in Figure 10.

[0104] Next, the modification condition setting data 208 contains information regarding the correspondence between the conditions and settings at the time of modification when modifying the processing plan. Figure 11 shows an example of the modification condition setting data 208 in this embodiment. The modification condition setting data 208 includes, for example, the available resources 1101D and the scale to be modified 1102D, which indicate the conditions at the time of modification. Furthermore, the modification condition setting data 208 also includes, for example, the variable to be modified 1103D and the additional consideration conditions 1104D, which indicate the modification settings corresponding to the conditions. The variable to be modified 1103D and the additional consideration conditions 1104D constitute the modification settings.

[0105] The modification conditions include information about the circumstances under which the processing plan is modified, such as the status of various computing resources, including the CPU computing resources of the computer environment, communication resources of the communication environment, and time resources available for modifying the processing plan.

[0106] Furthermore, the modification conditions include information about the size and complexity of the processing plan, such as the number of modules in the processing plan designated for modification and the number of variables that are candidates for modification. In this embodiment, available resources 1101D indicates the time (in minutes) available for modifying the processing plan, taking into account the remaining time until deployment completion and the time required for evaluation. Thus, in this embodiment, the modification condition setting data 208, which indicates the time and / or computing resource status in modifying the protection control plan, can be used as the modification condition setting data.

[0107] Furthermore, the target size 1102D represents the sum of the number of candidate operation variables 605D included in the modules of the processing plan designated for modification. Note that the sum of the target size 1102D is just an example; it is sufficient to indicate the size of the modifications, and you may also use the ratio of candidate operation variables 605D to the total number including those not being modified.

[0108] The modification settings include information that specifies the conditions for performing the modification process, corresponding to the conditions for the modification. For example, it includes information that specifies the range of variables to be used as calculation targets in the modification planning process, such as optimization calculations, from among all candidate variables to be modified, and additional conditions to be considered in the modification planning process.

[0109] In this embodiment, the variable to be modified 1103D indicates what percentage of the top variables from all candidate variables will be set as the calculation target, based on a predetermined priority order of variables.

[0110] The priority order of the predetermined variables may be set, for example, based on the approximate values ​​of the relationship between the operational variables and dependent variables in the processing impact approximation data 209, as shown in this embodiment, or it may be set by other methods. In addition, in this embodiment, additional consideration conditions 1104D can be used, which are constraint conditions / objective functions added in the revised planning process. These may include conditions such as the power supply interruption amount deviation being less than or equal to a predetermined value, or conditions that add an objective function that minimizes the cost associated with power supply interruption.

[0111] Here, the power supply interruption amount deviation is the difference between the predetermined required interruption amount and the set value of the interruption amount. Note that the items in Available Resources 1101D to Additional Consideration Conditions 1104D are examples of data items and will be changed as appropriate depending on the system's computing environment, the types of modules included in the processing plan, the types of equipment being controlled, etc.

[0112] Next, the processing effect approximation data 209 is information regarding the relationship between the instrumental variable and the dependent variable affected by the change in the instrumental variable in the modification of the processing plan. Figure 12 shows an example of the processing effect approximation data 209 in this embodiment. In Figure 12, the processing effect approximation data 209 includes, for example, the dependent variable 1201D and the approximate value 1202D of the effect of the instrumental variable on the dependent variable.

[0113] First, the dependent variable 1201D contains a management number for a variable that identifies a quantity representing the state of the grid (such as bus voltage or power flow in transmission lines), and it is sufficient if the variable can be identified. Furthermore, the approximate value of the influence of the controllable variable 1202D contains a quantitative approximation of the effect on each dependent variable when each controllable variable (a quantity that can be adjusted through grid planning and operation, such as generator output) is changed.

[0114] For example, a value of "0.7" for the instrumental variable "G001" with respect to the dependent variable "transmission line L001" in the first row indicates that when the output active power of "G001" is increased by one unit, the power flow through "transmission line L001" increases by "0.7".

[0115] Furthermore, the processing impact approximation data 209 is one of the analytical tools used in the operation and planning of power systems. For this reason, it may be created using known techniques that model the relationship between instrumental variables and dependent variables, such as a sensitivity matrix, which is a linear approximation model of the relationship between a certain variable (e.g., power generation amount or load) and a system state variable (e.g., voltage or power flow), or the power flow transfer distribution factor (PTDF), which shows the line power flow sensitivity of the transmission line to the active power change of each busbar. Also, the data items are just an example and should be changed as appropriate depending on the type and items of the dependent and instrumental variables.

[0116] Next, the modification setting data 210 contains information regarding the cases to be modified and the conditions for modification, which are necessary when modifying the plan in the plan modification unit 107. Figure 13 shows an example of the modification setting data 210 in this embodiment.

[0117] In Figure 13, the modified setting data 210 includes, for example, the plan ID 1301D, case group ID 1302D, case ID 1303D, module ID 1304D, the variable to be modified setting 1305D, and the additional consideration condition setting 1306D. Note that the variable to be modified setting 1305D and the additional consideration condition setting 1306D constitute the settings at the time of modification.

[0118] Case group ID 1302D has dependencies among the cases to be modified, based on case relationship evaluation data 207. Therefore, it includes a management number to identify a case group that comprises one or more cases that need to be planned and evaluated together.

[0119] Case ID 1303D contains a management number to identify cases belonging to a specific case group, and should serve to identify the case. Module ID 1304D contains a management number to identify the module of the processing plan corresponding to the case, and should identify the module.

[0120] The modification settings, specifically the modification target variable settings 1305D and the additional consideration condition settings 1306D, contain information on the specific modification target variables and additional consideration conditions 1104D set based on the modification condition setting data 208. For example, the first row, D1305, stores the value "G001~G003", which specifies the variables representing the output of a particular generator from among the operation candidate variables 605D.

[0121] Next, the process for formulating a protection control plan in this embodiment will be described. Figure 14 shows a flowchart illustrating an example of the protection control plan formulating process in this embodiment. This formulating process is an example of the process for calculating a protection control processing plan for a predetermined time range, modifying / evaluating the processing plan, and deploying it to the power system protection control device 5. This formulating process flowchart is executed by the power system protection control planning device 2.

[0122] First, the main processing unit 101 sets a predetermined time range for planning, either periodically or triggered by user instructions (step S101). For this purpose, the main processing unit 101 may use a time range for planning specified by the user in the input unit 32, or it may use a time range for planning that has been set in advance.

[0123] Furthermore, the future grid generation unit 102 constructs a simulated power grid environment for the time range to be planned from the grid status data 201 and grid equipment configuration data 202 for the time range to be planned set in step S101 (step S102).

[0124] Furthermore, the planning unit 103 generates processing plan data 204 corresponding to each case included in the assumed case data 203 occurring in the power system simulation environment constructed in step S102. To this end, the planning unit 103 determines the operation of the protection control module that satisfies the reliability requirements for each case in the power system simulation environment constructed in step S102, and generates processing plan data 204 including this. In other words, the planning unit 103 formulates a processing plan indicated by the processing plan data 204 (step S103).

[0125] Furthermore, the future grid generation unit 102 constructs a simulated power grid environment for a predetermined time range from new grid state data 201' and grid equipment configuration data 202' for a predetermined time range that reflects the latest measurement information and prediction data (step S104).

[0126] Furthermore, the correction necessity determination unit 104 identifies the difference (prediction discrepancy) between the power system simulation environment constructed in step S102 and the system status data (of the power system simulation environment') included in the processing plan data 204 (of the power system simulation environment') generated in step S103. Then, the correction necessity determination unit 104 identifies the cases affected by the prediction discrepancy (affected cases) from the prediction discrepancy and the case impact evaluation data 205.

[0127] Furthermore, the correction necessity determination unit 104 generates plan evaluation data 206 that evaluates the reliability of the impact case when it is executed in the system simulation environment' from the processing plan data 204 generated using the plan evaluation unit 105 (step S105). Note that the generation of the plan evaluation data 206 may be performed by the plan evaluation unit 105 on its own, or by the correction necessity determination unit 104 itself.

[0128] Furthermore, the correction necessity determination unit 104 determines whether corrections are necessary due to prediction discrepancies. To this end, the correction necessity determination unit 104 refers to the violation status 909D in the evaluation results of the plan evaluation data 206 and determines whether there are any modules (processes) that require correction (step S106). If, as a result, all modules do not require correction, the process proceeds to step S110. If there are modules that require correction, the process proceeds to step S107.

[0129] Furthermore, the plan modification setting unit 106 generates modification setting data 210 for making modifications to modules that require modification (step S107). To this end, the plan modification setting unit 106 extracts assumed cases to be modified based on the plan evaluation data 206 and predetermined case relationship evaluation data 207. The plan modification setting unit 106 then classifies the assumed cases into case groups according to the presence or absence of dependencies, and generates modification setting data 210 for each case group based on the assumed cases and modification condition setting data 208 (step S107). At this time, the plan modification setting unit 106 may also set modification condition setting data 208, which are the conditions for modifying each process in each group.

[0130] Next, the plan modification unit 107 generates plan evaluation data 206' corresponding to the reliability when executed in the "system simulation environment'" based on the generated modification setting data 210. To this end, the plan modification unit 107 determines the operation content of each protection control module of the processing plan to be modified based on the modification settings in the modification setting data 210 generated in step S107, modifies the processing plan data 204, and generates processing plan data 204' (step S108). In other words, the planning unit 103 modifies the processing plan data 204 based on the generated modification setting data 210 to formulate the processing plan shown in processing plan data 204'. Thus, processing plan data 204 is the processing plan data before modification for processing plan data 204'.

[0131] Furthermore, the planning and evaluation unit 105 evaluates the reliability of the protection control module for the impact cases included in the generated processing plan data 204' when executed in the "system simulation environment'" (step S109).

[0132] Therefore, the planning evaluation unit 105 generates planning evaluation data 206' to evaluate reliability. The planning evaluation unit 105 then refers to the violation status 909D of the evaluation result of the planning evaluation data 206' and determines whether the evaluation is OK, that is, whether there are any violations. If there are no violations and the evaluation is OK, the process proceeds to step S110. If there is one or more violations, the process returns to step S107, where the conditions for correction are changed, and then the processes in steps S107 to S109 are executed again. These repeated processes are executed repeatedly until the evaluation result meets the criteria in step S109 or until the predetermined end time is reached.

[0133] Furthermore, the distribution management unit 110 creates processing plan data 204'' by integrating processing plan data 204 and processing plan data 204' via the communication unit 31, and distributes the processing plan data 204'' to the power system protection control device 5 at a predetermined distribution timing (step S110).

[0134] This concludes the overview of the protection and control plan development process. Below, we will explain in detail a specific example of the protection and control plan development process.

[0135] First, we will describe the power grid simulation environment that simulates the electrical circuit characteristics generated by the future grid generation unit 102 in steps S102 and S104. This can be generated, for example, by integrating the equipment listed in the grid equipment configuration data 202 to generate an electrical circuit for each target time within the specified time range for planning, and by extracting and adding power generation amount, load amount, equipment settings, operating status, etc. from the grid status data 201.

[0136] These simulated power system environments can be used to simulate the characteristics of power flow on electrical circuits, for example, through power flow calculations. Furthermore, by constructing models that can simulate more advanced characteristics, such as transient analysis and the reflection of fault effects on electrical circuits, more accurate evaluation metrics can be added.

[0137] Furthermore, in step S104, the future grid generation unit 102 generates a simulated power grid environment ' based on the new grid state data 201'. However, the simulated power grid environment ' is generated based on the grid state data being updated to grid state data 201' based on new measured values ​​of solar power generation and electricity demand, or the latest predicted power generation and demand data based on new weather data.

[0138] The system status data 201 and system status data 201' may be prepared in advance and stored in the recording unit. In this case, the future system generation unit 102 can be omitted. Alternatively, the future system generation unit 102 may be provided in a separate device from the power system protection control planning device 2, and the power system protection control planning device 2 may receive the data.

[0139] Grid status data 201' is data in which some of the values ​​of the grid status data shown in Figure 2 have changed, for example, a status ID of "S002", a data generation date and time of "2001 / 01 / 01 00:9:25", and an active power of "20" for point A with No. "1".

[0140] In step S103, the planning unit 103 generates processing plan data 204 using the generated power system simulation environment. To this end, the planning unit 103 first performs power flow calculations and transient calculations. Then, using a predetermined algorithm, the planning unit 103 identifies the protection control settings that satisfy the reliability requirements and predetermined constraints of the assumed case data 203 and that yield the best results according to predetermined evaluation criteria, thereby generating the processing plan data 204.

[0141] The specified algorithm may be, for example, a complete enumeration of all possible combinations of protection control settings, a deterministic algorithm such as a greedy algorithm, or an algorithm that utilizes metaheuristics such as simulated annealing or a genetic algorithm.

[0142] Furthermore, the prescribed evaluation criteria include criteria such as the amount of change in power generation and frequency of the power grid due to the implementation of protective control, the cost of implementing protective control, and the amount of improvement in reliability constraints due to the implementation of protective control. In addition, the prescribed evaluation criteria may include importance based on the risk and probability of occurrence of the assumed cases to be addressed, and the ease of restoring the grid state to a normal state after the implementation of protective control. Moreover, the prescribed evaluation criteria may include evaluation criteria that combine multiple evaluation criteria by weighting them.

[0143] To explain the specific planning of protection control settings, we will use the example of planning the settings of a protection control module that shuts off a generator in the event of an overload on the transmission line "L00" in the case of case ID "C001". In this example, all combinations of generator shutdowns are listed for all generators (power generation equipment G001~G005) specified in the operation candidate variable 605D of assumed case data 203. Then, one possible approach is to plan a protection control module that sets the generator shutdown combination that brings the load factor of transmission line B closest to 100%.

[0144] The specified constraints are those related to the stability of power supply and the safety of equipment. For example, these include constraints on the balance between power demand and power generation, constraints on equipment overload, and constraints on whether the busbar voltage is outside the specified range or whether the generator output is outside the specified range. The algorithm, evaluation criteria, and constraints for the combination of protection control settings may be modified as appropriate depending on the assumed case and the type of protection control function being considered.

[0145] Furthermore, in step S105, the correction necessity determination unit 104 identifies the amount of prediction deviation from the power system simulation environment and the power system simulation environment'. Then, the correction necessity determination unit 104 identifies the cases affected by the prediction deviation (affected cases) from the amount of prediction deviation and the case impact evaluation data 205.

[0146] Let's explain a specific example of the amount of prediction discrepancy. Here, we take the example where the active power at point A at a predetermined time shown in Figure 2 is "5.0" in the power system simulation environment's system state data 201, and the corresponding value in the power system simulation environment's system state data 201' is "20.0".

[0147] In this case, the correction necessity determination unit 104 calculates the predicted deviation amount for point A as "20.0 - 5.0 = +15.0". Thus, in this embodiment, the predicted deviation amount is identified as the difference between the corresponding value in the power system state data 201 of the power system simulation environment and the active power.

[0148] Furthermore, as a specific example of identifying an impact case, if the item in which the predicted deviation amount exceeds a predetermined standard value is "Point A Active Power," then by referring to the case impact evaluation data 205 in Figure 8, the corresponding impact cases are identified as "C001, C002."

[0149] Furthermore, in step S105, the planning evaluation unit 105 evaluates the reliability of the generated processing plan data 204. The reliability simulates the power system state (post-execution system state) when the corresponding protection control module included in the processing plan data 204 is executed in the power system simulation environment when each assumed case included in the assumed case data 203 occurs. As a result, the planning evaluation unit 105 evaluates the amount of violation and whether or not there is a violation of the predetermined reliability requirements.

[0150] Furthermore, the evaluation of reliability is not limited to a binary determination of whether or not the constraints are met. Reliability may also be evaluated by calculating a reliability index using a continuous numerical value based on the degree of constraint violation, the risk and probability of the occurrence of assumed accident cases, etc. Alternatively, the reliability evaluation may also be calculated by comparing the reliability index with a predetermined reliability standard value.

[0151] Furthermore, the planning and evaluation unit 105 may not only evaluate reliability but also evaluate indicators that show the performance of the processing plan, such as operating costs and transmission losses, and output them in addition to the planning and evaluation data. As a specific example of reliability evaluation, the case where evaluation module "MoN001" corresponding to case ID "C001" is evaluated is shown.

[0152] Figure 9 shows that, prior to execution of the evaluation module "MoN001," the load rate of "transmission line L002" is 150%, indicating an overload condition. Furthermore, after execution of the evaluation module "MoN001," the load rate remains at 120%, indicating a violation of the reliability requirements for the assumed case.

[0153] This is because, due to a prediction discrepancy at point A in the simulated power grid environment, the power flow through transmission line L002 increases more than expected when the assumed scenario occurs. Furthermore, in the evaluation module "MoN001" of the processing plan data 204 calculated based on the simulated power grid environment, a state occurs where the overload cannot be resolved.

[0154] Furthermore, in step S106, the correction necessity determination unit 104 determines whether there are any modules that need correction based on the violation status 909D of the evaluation result of the plan evaluation data 206 generated by the plan evaluation unit 105, and branches the processing conditions according to the determination result. Note that the evaluation and verification of modules other than impact cases for which reliability evaluation was not performed in step S105 are not shown in the flowchart of Figure 14.

[0155] As described above, the correction necessity determination unit 104 identifies affected cases that are impacted by changes in active power, and the plan evaluation unit 105 performs simulations on the affected cases to determine whether corrections are necessary, that is, it determines whether the plan needs to be revised for each case.

[0156] However, additional processing may be added to steps after step S103, such as processing between steps S106 and S110, processing in parallel with steps S107 and S109, and processing immediately after step S103. Furthermore, in situations where the time available for planning is limited, and in a computer environment capable of parallel processing, performing this processing in parallel with steps S107 to S109 allows for efficient evaluation and verification of numerous modules that require parallel processing time with the revised planning process. As a result, a plan that meets the reliability criteria can be created and deployed within the limited time.

[0157] In step S107, the plan modification setting unit 106 extracts hypothetical cases to be modified, taking into account the dependencies between cases based on the plan evaluation data 206 and predetermined case relationship evaluation data 207. To this end, the plan modification setting unit 106 extracts hypothetical cases that are dependent on the affected cases, which is an example of a correlation. The plan modification setting unit 106 then realizes the processing associated with the affected cases and the hypothetical cases that are dependent on them by identifying them from the processing plan data 204. The plan modification setting unit 106 then classifies the extracted hypothetical cases into case groups according to the presence or absence of dependencies.

[0158] Here, we will show a concrete example of extracting hypothetical cases and classifying them into case groups. Let's consider the case where the hypothetical case with a violation in the plan evaluation data 206 is "C002". Based on the case relationship evaluation data 207 shown in Figure 10, case "C004", which has a dependency on "C002", is extracted. Furthermore, as shown in Figure 13, cases "C002" and "C004" are classified as the case group with case group ID "CG002".

[0159] As a result, the cases "C002" and "C004" and their corresponding protection control module IDs are stored. If the assumed cases of violations are "C002" and "C001", then only the case "C001" will be classified as case group ID "CG001" and stored as a different case group.

[0160] Furthermore, the plan modification setting unit 106 calculates the setting conditions for modification for each case group based on the modification condition setting data 208 and generates modification setting data 210. As a specific example, an example of calculating the modification settings for case group ID "CG001" in Figure 13 is shown.

[0161] In the correction condition setting data in Figure 11, let's assume that the available resources for the correction condition are "4 min" for the time available for correction, and that the scale of the correction target is 5 variables (5 variables for the operation candidate variable 605D of "C001"). In this case, the correction condition corresponds to the first row of Figure 11.

[0162] Furthermore, the corresponding correction settings are "Top 60%" for the variable to be corrected and "-" for the additional consideration condition 1104D. As shown in Figure 6, the dependent variable included in the reliability requirement for case ID "C001" is "Transmission Line L002", and the candidate variables for operation 605D are "G001~G005".

[0163] Furthermore, the values ​​of the control variables "G001~G005" in the row for "Transmission Line L002" in Figure 12 are "0.7, 0.3, 0.2, -0.1, -0.4," and each value represents the coefficient of effectiveness in eliminating overload caused by the disconnection and output changes of each generator to "Transmission Line L002."

[0164] Of these, the "G001~G003" operating variables (operating variables with values ​​of "0.7, 0.3, 0.2") of the "Top 60%" setting applied during modification this time are stored in the corresponding column in the first row of Figure 13 as the variable settings to be modified. Similarly, "-" is stored in the additional consideration condition setting 1306D.

[0165] Furthermore, in step S108, the plan modification unit 107 plans and evaluates the operation of each protection control module of each group to be modified based on the modification settings specified in the modification setting data 210, and generates processing plan data 204'.

[0166] Furthermore, the plan modification unit 107 can independently plan and evaluate processing plans for each group because there are no dependencies between the groups in formulating the modifications to the processing plan. In a computer environment capable of parallel processing, this allows for efficient evaluation and assessment of modules by performing the calculations for planning and evaluation for each group in parallel. As a result, plans that meet the reliability criteria can be generated and deployed within a limited time.

[0167] Furthermore, regarding the planning of the operation of each protection control module, the plan modification unit 107 performs power flow calculations and transient calculations using the generated power system simulation environment', similar to the processing of the planning unit 103. Then, using a predetermined algorithm, it plans a protection control setting that satisfies the reliability requirements and predetermined constraints and best meets predetermined evaluation criteria, and generates processing plan data 204'.

[0168] For the initial planning settings, the settings specified in the modification setting data 210 for each group are used. As a specific example, Figure 13 shows an example in which the plan modification unit 107 calculates a proposed modification for the protection control module "MoN001" of case group ID "CG001" "C001". The plan modification unit 107 also determines which generators from "G001 to G003" will be shut off using a predetermined algorithm based on the modification setting data 210.

[0169] As shown in Figure 7, in the processing plan data 204, only "G001" was to be blocked. However, suppose, for example, "G001 and G002" are now determined to be blocked. In this case, the processing plan is modified to generate processing plan data 204' which stores data rows with plan ID "P001'", generation date and time "2001 / 01 / 01 00:9:35", module ID "MoN001'", and control content "G001 and G002". Furthermore, the plan modification unit 107 evaluates the reliability of the newly generated processing plan data 204' in the power system simulation environment' using the plan evaluation unit 105.

[0170] Furthermore, the reliability evaluation in the planning evaluation unit 105 is performed in the same manner as in step S105. Here, as a specific example of reliability evaluation, we show the case where the evaluation module "MoN001'" corresponding to case ID "C001" is evaluated. As shown in Figure 9, the evaluation module "MoN001" violates the reliability requirements of the assumed case. However, the control content of the evaluation module "MoN001'" has changed to the interruption of "G001 and G002". Therefore, if we assume that the overload of transmission line L002 decreases by 30% each due to the interruption of "G001" and "G001", the state after processing of the evaluation module "MoN001'" will be "Transmission line L002 overload (90%)".

[0171] Furthermore, the corresponding violation status will be "-". In this way, when the control content of the module is modified, the post-processing state and the evaluation result of whether or not a violation has occurred also change.

[0172] Furthermore, in step S110, the distribution management unit 108 creates processing plan data 204'' by integrating processing plan data 204 and processing plan data 204'. If "No" is determined in step S106 and processing plan data 204' does not exist, processing plan data 204 is used as processing plan data 204''.

[0173] In generating processing plan data 204'', all cases and corresponding modules included in processing plan data 204' are extracted. Then, cases and corresponding modules not included in processing plan data 204' are extracted from processing plan data 204, and both are merged to create processing plan data 204''.

[0174] As a concrete example of generating processing plan data 204'', we will explain the case where processing plan data 204'' includes a module corresponding to case "C001". In this case, the module corresponding to case "C001" in processing plan data 204'' is stored in processing plan data 204''. For all cases other than case "C001", the corresponding modules are extracted from processing plan data 204 and stored in processing plan data 204''.

[0175] Furthermore, the distribution management unit 108 transmits either the processing plan data 204'' or the internal module data 707D to the power system protection control device 5 at a predetermined distribution time. In this case, only the processing plan data 204'' or the internal module data 707D may be transmitted. This completes the deployment from the planning side to the edge side, the power system protection control device 5.

[0176] In this manner, in response to changes in the power system status, the correction necessity determination unit 104 performs the following processing on the assumed cases and corresponding protection control modules included in the assumed case data 203 that it has determined require correction based on the evaluation results of the plan evaluation unit 105. First, the plan correction setting unit 106 generates correction condition setting data 208 in which correction conditions are set after considering the time until deployment. Then, based on the correction conditions, the plan correction unit 107 formulates a correction plan for the protection control module, and the distribution management unit 108 deploys the corrected processing plan to the power system protection control device 5 by the deployment completion time.

[0177] This eliminates the need to comprehensively evaluate multiple combinations of assumed system conditions and fault scenarios, even in the event of short-term changes in the power system that could lead to a deterioration in reliability or performance. Therefore, the evaluation will focus only on the protection control processing plans that are most likely to require modification due to short-term changes in conditions.

[0178] Furthermore, only when modifications are necessary, cases may be classified into groups, taking into account the interdependencies between cases, and only the minimum necessary processing plans may be considered. Modification proposals may then be formulated and evaluated independently and in parallel for each classified group. This allows for efficient modification and evaluation of processing. As a result, processing plans that meet reliability and performance standards can be formulated within the required time.

[0179] This allows the processing plan to be deployed to edge devices, enabling the preparation of a processing plan to address anticipated changes in the power grid before those changes actually occur. As a result, it becomes possible to avoid failures and accidents in the power grid, such as transmission line overloads.

[0180] With the above steps completed, the planning and deployment process of the protection and control plan of the power system protection and control planning device 2 is finished. Next, the protection and control module is executed in the power system protection and control device 5, which performs physical operations on the electrical equipment 602, such as shutting off generators, controlling output, opening and closing circuit breakers, and changing transformer taps.

[0181] In this embodiment, the correction necessity determination unit 104 made a determination in step S106 based on the evaluation result by the plan evaluation unit 105 regarding whether correction of the impact case is necessary. However, the correction necessity determination unit 104 may also compare the amount of predicted deviation calculated based on the power system simulation environment and the power system simulation environment' with a predetermined standard value. The correction necessity determination unit 104 then determines whether the amount of predicted deviation exceeds the predetermined standard value (first determination process).

[0182] If the result exceeds this, the planning evaluation unit 105 may perform a determination of whether or not the impact case needs to be modified (second determination process). By performing the first determination process with a simple process, the frequency of the second determination process, which involves a computationally intensive evaluation, can be reduced, and the determination of whether or not modifications are necessary can be performed efficiently.

[0183] In this embodiment, there are no particular restrictions on the control content of the protection control module for the processing plan formulated by the planning unit 103 and the plan modification unit 107. However, the control content of the protection control module may be pre-configured on the edge device side, i.e., the power system protection control device 5, and used.

[0184] In other words, the control content of the control module deployed from the planning system may be selected from the aforementioned pre-configured combinations. This limits the control changes from the planning system to a range pre-configured on the edge device side, thereby preventing unexpected control operations and ensuring safety.

[0185] Furthermore, in this embodiment, the case impact evaluation data 205, case relationship evaluation data 207, modification condition setting data 208, and processing impact approximation data 209 were pre-created by the operator. However, this is not limited to this; the main processing unit or other data generation processing unit may be prepared to generate the data periodically or dynamically according to the computer status of the power system or system.

[0186] In this embodiment, the plan modification setting unit 106 generates modification setting data 210 containing a single modification setting for each assumed case. However, the system is not limited to this; the plan modification unit 107 may generate modification setting data 210 containing multiple modification settings that are executed in stages for each assumed case, and the plan modification unit 107 may apply the multiple modification settings in stages.

[0187] For example, in Figure 13, for module ID "MoN001", the first stage modification setting may be set to "-" for additional consideration condition setting 1306D, and the second stage modification setting may be set to "Minimize blocking costs" for additional consideration condition setting 1306D. If there are multiple modification settings, the plan modification unit 107 first searches for and verifies modification proposals for the module with the first stage modification settings applied, and holds them as provisional solutions. Then, the plan modification unit 107 applies the modification settings for the second stage and beyond. If a new solution is obtained as a result, the plan modification unit 107 updates the new solution as a provisional solution.

[0188] The processing of the plan modification unit 107 ends when a predetermined time has elapsed or when the application of all modification settings at each stage has been completed. The plan modification unit 107 then outputs the latest provisional solution as the solution for the module to the distribution management unit 108.

[0189] Thus, in the first stage, a solution that satisfies only the reliability requirement is searched for, and in the second stage and beyond, performance-related conditions are added to search for a better-performing solution. This makes it possible to search for a good-performing solution while more reliably ensuring a certain level of reliability within the time required for deployment.

[0190] In this embodiment, the plan correction setting unit 106 generates correction setting data 210 based on predetermined correction condition setting data 208. However, the plan correction setting unit 106 may also generate an estimation model that estimates the time required for correction based on past historical data (target variable size, conditions, required time, etc.) related to the processing performed by the plan correction unit 107, for the condition setting when correcting the prediction deviation.

[0191] The plan modification setting unit 106 may then use an estimation model to generate modification setting data 210 so that the modification is completed within a predetermined time. This makes it possible to generate more efficient modification setting data and to formulate high-quality modification proposals. This concludes the explanation of the protection control plan formulation process in this embodiment, and next, the display screen of the display unit 33 in this embodiment will be described.

[0192] Figure 15 shows an example of the processing plan display screen in this embodiment. The processing plan display screen in Figure 15 is called up from the menu screen in response to user operations on the input unit 32, and the display unit 33 displays the contents of the processing plan data 204 to 204''. The contents of the processing plan data 204 to 204'' displayed on this processing plan display screen are the same as those described in Figure 7, so a detailed explanation is omitted. The menu screen is initially displayed by the display unit 33.

[0193] Furthermore, this processing plan display screen may display only a portion of the processing plan data 204~204'', or it may also display data not included in the processing plan data 204~204''. The processing plan display screen may also include a change button for the user to modify a portion of the processing plan display screen, and a back button to close the screen and return to the calling menu screen.

[0194] Figure 16 shows an example of the plan evaluation display screen of this embodiment. This plan evaluation display screen is called up from the menu screen in response to user operations on the input unit 32, and the display unit 33 displays the contents of the plan evaluation data 206 and / or plan evaluation data 206'.

[0195] The contents of the plan evaluation data 206 and / or plan evaluation data 206' displayed on this plan evaluation display screen are the same as those described in Figure 9, so a detailed explanation is omitted. Furthermore, this plan evaluation display screen may display only a portion of the plan evaluation data 206 or plan evaluation data 206', or it may also display data not included in the plan evaluation data 206 or plan evaluation data 206 and / or plan evaluation data 206'. The plan evaluation display screen may also include a change button for the user to modify a portion of the plan evaluation display screen, and a back button to close the screen and return to the calling menu screen.

[0196] Figure 17 shows an example of the modification settings display screen of this embodiment. This modification settings display screen is called up from the menu screen in response to user operations on the input unit 32 and displays the contents of the modification settings data 210. The contents of the modification settings data 210 displayed on the modification settings display screen are the same as those described in Figure 13, so a detailed explanation is omitted.

[0197] Furthermore, this modification settings display screen may display only a portion of the modification settings data 210, or it may also display data not included in the modification settings data 210. The modification settings display screen may also include a change button for the user to modify a portion of the modification settings display screen, and a back button to close the screen and return to the calling menu screen. This concludes the description of the display screen in this embodiment.

[0198] Next, the hardware configuration of the power system protection and control planning device 2 in this embodiment will be described. Figure 18 is a diagram illustrating an example of the hardware configuration of the power system protection and control planning device 2 in this embodiment.

[0199] In Figure 18, the power system protection and control planning device 2 constitutes the power system protection and control system 1 in the same manner as in Figure 1, and connects to the power system protection and control device 5 and the power system electrical equipment 6 via the first communication network 3 and the second communication network 4.

[0200] Furthermore, in Figure 18, a terminal device 7 is added compared to Figure 1. The terminal device 7 is operated by the user, receiving various instructions and displaying a screen. Thus, the terminal device 7 has the functions of the input unit 32 and display unit 33 in Figure 1. For this reason, the terminal device 7 has an input device such as a keyboard that receives input from the user and a display device such as a display monitor. Therefore, the input unit 32 and display unit 33 can be omitted from the power system protection control planning device 2. Note that the input device and display device may be configured as an integrated unit, such as a touch panel.

[0201] Furthermore, the terminal device 7 can be implemented using various computers such as PCs, smartphones, and tablets. There may be multiple terminal devices 7. Additionally, the terminal device 7 may be connected to the power system protection and control planning device 2 via a communication path other than the first communication network 3.

[0202] Next, the power system protection and control planning device 2 can be implemented using a computer such as a server, and includes a processing unit 2a, a communication device 2b, a main memory 2c, and an auxiliary memory 2d, which are connected to each other via a communication path.

[0203] The processing unit 2a can be implemented with a processor such as a CPU and performs calculations according to the power system protection control plan program 2e stored in the auxiliary storage device 2d, which will be described later. The communication device 2b connects to the power system protection control device 5 and the terminal device 7 via the first communication network 3.

[0204] The first communication network 3 may be implemented using a combination of multiple networks. For example, the power system protection and control planning device 2 and the terminal device 7 may be connected via a dedicated line such as an intranet, while other devices may be connected via the internet or similar.

[0205] The communication device 2b receives operations and information from the terminal device 7 and outputs processing results to the terminal device 7. Therefore, the communication device 2b also performs the functions of the input unit 11 and output unit 15 in Figure 1. As a result, the terminal device 7 can display the display screens shown in Figures 15 to 17 in accordance with the information transmitted from the power system protection control planning device 2.

[0206] Furthermore, the main memory 2c and auxiliary memory 2d can be implemented using storage media and correspond to the recording unit 20 in Figure 1. The main memory 2c is where the power system protection control planning program 2e and information used for processing by the processing unit 2a, which are stored in the auxiliary memory 2d, are loaded. The auxiliary memory 2d can be implemented using so-called storage.

[0207] The auxiliary storage device 2d stores the power system protection control plan program 2e and the system status data 201 to the equipment status data 213.

[0208] Furthermore, the auxiliary storage device 2d may be implemented using various storage media such as an external HDD (Hard Disk Drive), SSD (Solid State Drive), or main memory card, or it may be implemented as a separate device from the power system protection control planning device 2, such as a file server.

[0209] Here, the processing unit 2a executes the processing of each part from the main processing unit 101 to the distribution management unit 108 according to the power system protection control planning program 2e. Also, the system status data 201 to the equipment status data 213 have already been explained, so their explanation is omitted here.

[0210] Note that the power system protection control device 5 and the power system electrical device 6 have already been explained in Figure 1, so their explanation here will be omitted.

[0211] This concludes the description of Example 1. In the embodiments of the present invention and Example 1, by efficiently identifying processes that require evaluation in response to various changes in the power system state, and by modifying and evaluating those processes, it is possible to formulate a processing plan that meets reliability and performance standards within the required predetermined time.

[0212] The processing plan can then be deployed to the power system protection control device 5, which is an edge device. In other words, the power system protection control device 5 can control the power system electrical equipment 6, particularly the electrical equipment 602, according to the processing plan data that shows the formulated processing plan.

[0213] It should be noted that the present invention is not limited to these embodiments and examples. For example, a causal relationship other than a dependency relationship may be used as the correlation. Furthermore, the presence or absence of a correlation can be determined using various correlation coefficients. [Explanation of Symbols]

[0214] 1...Power system protection control system, 2...Power system protection control planning device, 3...First communication network, 4...Second communication network, 5...Power system protection control device, 6...Power system electrical equipment, 7...Terminal device, 10...Processing unit, 20...Recording unit, 31...Communication unit, 32...Input unit, 33...Display unit, 50...Protection control module, 101...Main processing unit, 102...Future system generation unit, 103...Planning unit, 104...Modification necessity determination unit, 105...Plan evaluation unit, 106...Plan modification setting unit, 107...Plan modification unit, 108...Distribution management unit, 201...System status data Data, 202...System equipment configuration data, 203...Assumed case data, 204...Processing plan data, 205...Case impact evaluation data, 206...Plan evaluation data, 207...Case relationship evaluation data, 208...Modification condition setting data, 209...Processing impact approximation data, 210...Modification setting data, 211...Environmental status data, 212...Equipment setting data, 213...Equipment status data, 501...Management unit, 502...Communication unit, 551...Module processing unit, 552...Module recording unit, 553...Module communication unit, 601...Measuring instruments, 602...Electrical equipment

Claims

1. A power system protection and control planning device for formulating a power system protection and control plan, A modification necessity determination unit determines whether or not the protection control plan needs to be modified based on an assessment of the impact on assumed cases due to changes in the grid state indicated by grid state data showing the future grid state of the power system, A power system protection control planning device having a plan modification setting unit that identifies the processes to be modified from the protection control plan based on an evaluation of the correlation between the assumed cases.

2. A power system protection control planning device according to claim 1, The aforementioned plan modification setting unit generates modification setting data for making modifications to the identified process, Furthermore, a power system protection control planning device having a plan modification unit that modifies the protection control plan based on the modified setting data.

3. A power system protection control planning device according to claim 2, The aforementioned correlation is the dependency relationship between the assumed cases in the power system protection control planning device.

4. A power system protection control planning device according to claim 3, The plan modification setting unit is a power system protection control planning device that classifies the assumed cases into a plurality of groups according to whether or not there are dependencies between the assumed cases, and generates the modification setting data for each group.

5. A power system protection control planning device according to claim 3, The plan modification setting unit is a power system protection control planning device that generates modification setting data indicating the time and / or computing resource status in modifying the protection control plan.

6. A power system protection control planning device according to claim 3, The aforementioned plan modification unit is a power system protection and control planning device that utilizes control options pre-configured in a power system protection and control device connected to the power system protection and control planning device.

7. A power system protection control planning device according to claim 3, The power system protection and control planning device, which determines whether or not a correction is necessary, identifies a predicted discrepancy indicating the difference between the grid state data included in the protection and control plan and the grid state data indicating the future grid state, based on an assessment of the impact of the changes before the correction on the assumed case, and identifies an assessment of the impact on the assumed case based on the predicted discrepancy.

8. A power system protection control planning device according to claim 7, The plan modification setting unit generates an estimation model for estimating the time required for modification based on the conditions set at the time of modification, and the power system protection control planning device generates the modification setting data based on the estimation model.

9. A power system protection control planning device according to claim 7, The aforementioned correction necessity determination unit identifies impact cases that indicate assumed cases affected by the prediction deviation, The correction necessity determination unit determines whether the predicted deviation exceeds a predetermined standard value, Furthermore, the power system protection control planning device has a planning evaluation unit that determines whether or not the impact case needs to be modified if the prediction deviation exceeds a predetermined standard value, and modifies the impact case.

10. A power system protection control planning device according to claim 3, The plan modification setting unit is a power system protection control planning device that generates modification setting data including a plurality of modification settings that are executed in stages for each assumed case.

11. A computer that is a power system protection and control planning device that formulates a power system protection and control plan, A modification necessity determination unit determines whether or not the protection control plan needs to be modified based on an assessment of the impact on assumed cases due to changes in the grid state indicated by grid state data showing the future grid state of the power system, A power system protection control planning program that functions as a plan modification setting unit to identify the processes to be modified among the protection control plans based on an evaluation of the correlation between the assumed cases.

12. A power system protection control planning program according to claim 11, The plan modification setting unit is instructed to generate modification setting data for making modifications to the specified process. A power system protection control planning program that causes the computer to function as a planning modification unit that modifies the protection control plan based on the modified setting data.

13. A power system protection control planning program according to claim 12, The aforementioned correlation is a power grid protection and control planning program that represents the dependency relationship between the assumed cases.

Images